From xen-users-bounces@lists.xen.org Fri Feb 01 00:32:42 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 01 Feb 2013 00:32: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 1U14XD-0002M7-AC; Fri, 01 Feb 2013 00:31:15 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U14XC-0002M2-97 for Xen-users@lists.xen.org; Fri, 01 Feb 2013 00:31:14 +0000 Received: from [193.109.254.147:18853] by server-6.bemta-14.messagelabs.com id D1/FC-12010-1DC0B015; Fri, 01 Feb 2013 00:31:13 +0000 X-Env-Sender: min.lee@gatech.edu X-Msg-Ref: server-12.tower-27.messagelabs.com!1359678672!8837948!1 X-Originating-IP: [130.207.160.71] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 8702 invoked from network); 1 Feb 2013 00:31:12 -0000 Received: from deliverator6.gatech.edu (HELO deliverator6.gatech.edu) (130.207.160.71) by server-12.tower-27.messagelabs.com with SMTP; 1 Feb 2013 00:31:12 -0000 Received: from deliverator6.gatech.edu (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id 6A073BDD3CA for ; Thu, 31 Jan 2013 19:31:11 -0500 (EST) Received: from mail4.gatech.edu (mail4.gatech.edu [130.207.185.164]) by deliverator6.gatech.edu (Postfix) with ESMTP id 22C78BDD0BE for ; Thu, 31 Jan 2013 19:31:11 -0500 (EST) Received: from [143.215.207.70] (lawn-143-215-207-70.lawn.gatech.edu [143.215.207.70]) (Authenticated sender: mlee7) by mail4.gatech.edu (Postfix) with ESMTPSA id 105E14FE24 for ; Thu, 31 Jan 2013 19:31:11 -0500 (EST) Message-ID: <510B0CD5.3060905@gatech.edu> Date: Thu, 31 Jan 2013 19:31:17 -0500 From: Min Lee User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130107 Thunderbird/17.0.2 MIME-Version: 1.0 To: Xen-users@lists.xen.org X-GT-AVAS-Version: 5.6.1.2065439, Antispam-Engine: 2.7.2.376379, Antispam-Data: 2013.2.1.1817 X-GT-Spam-Details: Internal Mail X-GT-Spam-Rating: (0%) X-GT-True-Rating: (8%) Subject: [Xen-users] dom0's layout on physical 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-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, all I thought dom0 is layed out on physical memory starting 0, linearly, but this message, (XEN) *** LOADING DOMAIN 0 *** (XEN) Xen kernel: 64-bit, lsb, compat32 (XEN) Dom0 kernel: 64-bit, PAE, lsb, paddr 0x1000000 -> 0x1d87000 (XEN) PHYSICAL MEMORY ARRANGEMENT: (XEN) Dom0 alloc.: 0000000c14000000->0000000c18000000 (498514 pages to be allocated) shows the address range 0000000c14000000->0000000c18000000 , what is this? it's 64MB range and why 64MB from Dom0 is located here? I think 498514 pages will be allocated later, but where, exactly?? if dom0's memory is partitioned into several places, then, what happens to their GPFN?? thanks Min _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Fri Feb 01 00:32:42 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 01 Feb 2013 00:32: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 1U14XD-0002M7-AC; Fri, 01 Feb 2013 00:31:15 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U14XC-0002M2-97 for Xen-users@lists.xen.org; Fri, 01 Feb 2013 00:31:14 +0000 Received: from [193.109.254.147:18853] by server-6.bemta-14.messagelabs.com id D1/FC-12010-1DC0B015; Fri, 01 Feb 2013 00:31:13 +0000 X-Env-Sender: min.lee@gatech.edu X-Msg-Ref: server-12.tower-27.messagelabs.com!1359678672!8837948!1 X-Originating-IP: [130.207.160.71] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 8702 invoked from network); 1 Feb 2013 00:31:12 -0000 Received: from deliverator6.gatech.edu (HELO deliverator6.gatech.edu) (130.207.160.71) by server-12.tower-27.messagelabs.com with SMTP; 1 Feb 2013 00:31:12 -0000 Received: from deliverator6.gatech.edu (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id 6A073BDD3CA for ; Thu, 31 Jan 2013 19:31:11 -0500 (EST) Received: from mail4.gatech.edu (mail4.gatech.edu [130.207.185.164]) by deliverator6.gatech.edu (Postfix) with ESMTP id 22C78BDD0BE for ; Thu, 31 Jan 2013 19:31:11 -0500 (EST) Received: from [143.215.207.70] (lawn-143-215-207-70.lawn.gatech.edu [143.215.207.70]) (Authenticated sender: mlee7) by mail4.gatech.edu (Postfix) with ESMTPSA id 105E14FE24 for ; Thu, 31 Jan 2013 19:31:11 -0500 (EST) Message-ID: <510B0CD5.3060905@gatech.edu> Date: Thu, 31 Jan 2013 19:31:17 -0500 From: Min Lee User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130107 Thunderbird/17.0.2 MIME-Version: 1.0 To: Xen-users@lists.xen.org X-GT-AVAS-Version: 5.6.1.2065439, Antispam-Engine: 2.7.2.376379, Antispam-Data: 2013.2.1.1817 X-GT-Spam-Details: Internal Mail X-GT-Spam-Rating: (0%) X-GT-True-Rating: (8%) Subject: [Xen-users] dom0's layout on physical 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-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, all I thought dom0 is layed out on physical memory starting 0, linearly, but this message, (XEN) *** LOADING DOMAIN 0 *** (XEN) Xen kernel: 64-bit, lsb, compat32 (XEN) Dom0 kernel: 64-bit, PAE, lsb, paddr 0x1000000 -> 0x1d87000 (XEN) PHYSICAL MEMORY ARRANGEMENT: (XEN) Dom0 alloc.: 0000000c14000000->0000000c18000000 (498514 pages to be allocated) shows the address range 0000000c14000000->0000000c18000000 , what is this? it's 64MB range and why 64MB from Dom0 is located here? I think 498514 pages will be allocated later, but where, exactly?? if dom0's memory is partitioned into several places, then, what happens to their GPFN?? thanks Min _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Fri Feb 01 01:33:21 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 01 Feb 2013 01:33: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 1U15U2-0006ag-RO; Fri, 01 Feb 2013 01:32:02 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U15U0-0006aS-Rn; Fri, 01 Feb 2013 01:32:00 +0000 Received: from [193.109.254.147:53618] by server-16.bemta-14.messagelabs.com id 94/89-25906-F0B1B015; Fri, 01 Feb 2013 01:31:59 +0000 X-Env-Sender: eneal@businessgrade.com X-Msg-Ref: server-11.tower-27.messagelabs.com!1359682317!2381992!1 X-Originating-IP: [66.151.104.17] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 1070 invoked from network); 1 Feb 2013 01:31:58 -0000 Received: from smtp1.businessgrade.com (HELO smtp1.businessgrade.com) (66.151.104.17) by server-11.tower-27.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 1 Feb 2013 01:31:58 -0000 Received: from ashslvha1.businessgrade.local (127.0.0.1) by ashslvha1.businessgrade.local (Axigen) with ESMTPSA id 112B99; Thu, 31 Jan 2013 20:34:27 -0500 Received: from [70.197.129.126] by businessgrade.com with HTTP; Thu, 31 Jan 2013 20:34:27 -0500 From: Errol Neal Date: Thu, 31 Jan 2013 20:34:27 -0500 X-Mailer: Axigen WebMail To: xen-api , "xen-users@lists.xensource.com" Message-ID: <1359682467321281500@businessgrade.com> Importance: Normal MIME-Version: 1.0 Content-Disposition: inline Subject: [Xen-users] [XCP] xe vdi-create and sharable=true flag X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: eneal@businessgrade.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 folks. I'm trying to figure out what has changed about XCP 1.6 vs XCP 1.1 that is seemingly preventing me from creating a VDI that can be attached to multiple VMs. I maintain a small blog about virtualization and high availability and I documented the necessary steps here: http://www.ha-guru.com/sharing-virtual-disks-between-xenserver-xcp-vms/ This was done on a stand alone Dell R610 server using local storage and the server is running XCP 1.1 and using this, I was able to build a 3-node NAS cluster on XCP. Trying to execute these same steps on a similar server running XCP 1.6, the results are not the same. Essentially, the sharable flag for the VDI stays false. Now the conditions have somewhat changed because I'm testing on a server in a pool. Would that have any impact? Can anyone think of any other reasons why this was working for me and is now seemingly not working? 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 Fri Feb 01 01:33:21 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 01 Feb 2013 01:33: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 1U15U2-0006ag-RO; Fri, 01 Feb 2013 01:32:02 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U15U0-0006aS-Rn; Fri, 01 Feb 2013 01:32:00 +0000 Received: from [193.109.254.147:53618] by server-16.bemta-14.messagelabs.com id 94/89-25906-F0B1B015; Fri, 01 Feb 2013 01:31:59 +0000 X-Env-Sender: eneal@businessgrade.com X-Msg-Ref: server-11.tower-27.messagelabs.com!1359682317!2381992!1 X-Originating-IP: [66.151.104.17] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 1070 invoked from network); 1 Feb 2013 01:31:58 -0000 Received: from smtp1.businessgrade.com (HELO smtp1.businessgrade.com) (66.151.104.17) by server-11.tower-27.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 1 Feb 2013 01:31:58 -0000 Received: from ashslvha1.businessgrade.local (127.0.0.1) by ashslvha1.businessgrade.local (Axigen) with ESMTPSA id 112B99; Thu, 31 Jan 2013 20:34:27 -0500 Received: from [70.197.129.126] by businessgrade.com with HTTP; Thu, 31 Jan 2013 20:34:27 -0500 From: Errol Neal Date: Thu, 31 Jan 2013 20:34:27 -0500 X-Mailer: Axigen WebMail To: xen-api , "xen-users@lists.xensource.com" Message-ID: <1359682467321281500@businessgrade.com> Importance: Normal MIME-Version: 1.0 Content-Disposition: inline Subject: [Xen-users] [XCP] xe vdi-create and sharable=true flag X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: eneal@businessgrade.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 folks. I'm trying to figure out what has changed about XCP 1.6 vs XCP 1.1 that is seemingly preventing me from creating a VDI that can be attached to multiple VMs. I maintain a small blog about virtualization and high availability and I documented the necessary steps here: http://www.ha-guru.com/sharing-virtual-disks-between-xenserver-xcp-vms/ This was done on a stand alone Dell R610 server using local storage and the server is running XCP 1.1 and using this, I was able to build a 3-node NAS cluster on XCP. Trying to execute these same steps on a similar server running XCP 1.6, the results are not the same. Essentially, the sharable flag for the VDI stays false. Now the conditions have somewhat changed because I'm testing on a server in a pool. Would that have any impact? Can anyone think of any other reasons why this was working for me and is now seemingly not working? 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 Fri Feb 01 07:21:00 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 01 Feb 2013 07:21: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 1U1AuS-0008IJ-45; Fri, 01 Feb 2013 07:19:40 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U1AuP-0008IE-UZ for xen-users@lists.xensource.com; Fri, 01 Feb 2013 07:19:38 +0000 Received: from [85.158.137.99:28700] by server-11.bemta-3.messagelabs.com id 3F/94-10249-88C6B015; Fri, 01 Feb 2013 07:19:36 +0000 X-Env-Sender: pigeon@pigeond.net X-Msg-Ref: server-15.tower-217.messagelabs.com!1359703174!17152408!1 X-Originating-IP: [203.59.1.218] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogMjAzLjU5LjEuMjE4ID0+IDE5MTA0\n X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 23195 invoked from network); 1 Feb 2013 07:19:36 -0000 Received: from icp-osb-irony-out2.external.iinet.net.au (HELO icp-osb-irony-out2.external.iinet.net.au) (203.59.1.218) by server-15.tower-217.messagelabs.com with SMTP; 1 Feb 2013 07:19:36 -0000 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AsgXAIZrC1F8lWUl/2dsb2JhbABFuRiFCwOBABZzgl9nFDROiCOhBKElFY03F4MpA5YThhOKPIMP X-IronPort-AV: E=Sophos;i="4.84,579,1355068800"; d="scan'208";a="82679431" Received: from unknown (HELO torankusu.pigeond.net) ([124.149.101.37]) by icp-osb-irony-out2.iinet.net.au with ESMTP; 01 Feb 2013 15:19:33 +0800 Received: from furiza.pigeond.net ([192.168.42.20]:45034 helo=furiza) by torankusu.pigeond.net with esmtp (Exim 4.72) (envelope-from ) id 1U1AuK-0006p0-5L for xen-users@lists.xensource.com; Fri, 01 Feb 2013 18:19:32 +1100 Date: Fri, 1 Feb 2013 18:19:30 +1100 From: Howell Tam To: Message-ID: <20130201181930.262fa02b@furiza> Organization: pigeond.net X-Mailer: Claws Mail 3.8.1 (GTK+ 2.24.13; x86_64-pc-linux-gnu) Mime-Version: 1.0 Subject: [Xen-users] Intel HD 4000 VGA passthrough not working X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: 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 have an i7-3770 which has the Intel HD 4000 graphics. I've been trying to pass it through to DomU with no success. With a Linux DomU, the i915 module simply will not load because intel_agp is not loaded properly when it cannot find the AGP bridge. ( With a Win7 DomU, it BSODs straight away during the boot with SYSTEM_SERVICE_EXCEPTION. With a WinXP DomU, it got further but the card is not working as described in the Device Manager, saying there is not enough memory to use the device. Is there any pointers on where i should trace and debug this? Thanks! Regards, Howell. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Fri Feb 01 07:21:00 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 01 Feb 2013 07:21: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 1U1AuS-0008IJ-45; Fri, 01 Feb 2013 07:19:40 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U1AuP-0008IE-UZ for xen-users@lists.xensource.com; Fri, 01 Feb 2013 07:19:38 +0000 Received: from [85.158.137.99:28700] by server-11.bemta-3.messagelabs.com id 3F/94-10249-88C6B015; Fri, 01 Feb 2013 07:19:36 +0000 X-Env-Sender: pigeon@pigeond.net X-Msg-Ref: server-15.tower-217.messagelabs.com!1359703174!17152408!1 X-Originating-IP: [203.59.1.218] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogMjAzLjU5LjEuMjE4ID0+IDE5MTA0\n X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 23195 invoked from network); 1 Feb 2013 07:19:36 -0000 Received: from icp-osb-irony-out2.external.iinet.net.au (HELO icp-osb-irony-out2.external.iinet.net.au) (203.59.1.218) by server-15.tower-217.messagelabs.com with SMTP; 1 Feb 2013 07:19:36 -0000 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AsgXAIZrC1F8lWUl/2dsb2JhbABFuRiFCwOBABZzgl9nFDROiCOhBKElFY03F4MpA5YThhOKPIMP X-IronPort-AV: E=Sophos;i="4.84,579,1355068800"; d="scan'208";a="82679431" Received: from unknown (HELO torankusu.pigeond.net) ([124.149.101.37]) by icp-osb-irony-out2.iinet.net.au with ESMTP; 01 Feb 2013 15:19:33 +0800 Received: from furiza.pigeond.net ([192.168.42.20]:45034 helo=furiza) by torankusu.pigeond.net with esmtp (Exim 4.72) (envelope-from ) id 1U1AuK-0006p0-5L for xen-users@lists.xensource.com; Fri, 01 Feb 2013 18:19:32 +1100 Date: Fri, 1 Feb 2013 18:19:30 +1100 From: Howell Tam To: Message-ID: <20130201181930.262fa02b@furiza> Organization: pigeond.net X-Mailer: Claws Mail 3.8.1 (GTK+ 2.24.13; x86_64-pc-linux-gnu) Mime-Version: 1.0 Subject: [Xen-users] Intel HD 4000 VGA passthrough not working X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: 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 have an i7-3770 which has the Intel HD 4000 graphics. I've been trying to pass it through to DomU with no success. With a Linux DomU, the i915 module simply will not load because intel_agp is not loaded properly when it cannot find the AGP bridge. ( With a Win7 DomU, it BSODs straight away during the boot with SYSTEM_SERVICE_EXCEPTION. With a WinXP DomU, it got further but the card is not working as described in the Device Manager, saying there is not enough memory to use the device. Is there any pointers on where i should trace and debug this? Thanks! Regards, Howell. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Fri Feb 01 08:25:05 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 01 Feb 2013 08:25: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 1U1BuX-0000os-KV; Fri, 01 Feb 2013 08:23:49 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U1BuW-0000on-AM for xen-users@lists.xensource.com; Fri, 01 Feb 2013 08:23:48 +0000 Received: from [85.158.138.51:4267] by server-4.bemta-3.messagelabs.com id BD/88-12802-39B7B015; Fri, 01 Feb 2013 08:23:47 +0000 X-Env-Sender: borodkin.sergey@gmail.com X-Msg-Ref: server-14.tower-174.messagelabs.com!1359707025!22420417!1 X-Originating-IP: [209.85.220.182] 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.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 20462 invoked from network); 1 Feb 2013 08:23:46 -0000 Received: from mail-vc0-f182.google.com (HELO mail-vc0-f182.google.com) (209.85.220.182) by server-14.tower-174.messagelabs.com with RC4-SHA encrypted SMTP; 1 Feb 2013 08:23:46 -0000 Received: by mail-vc0-f182.google.com with SMTP id fl17so2320505vcb.13 for ; Fri, 01 Feb 2013 00:23:45 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=3OZvYNp2TsFrBWLqpk+CbgDcAVE+KqYnAhOIIEvyw94=; b=IvSdyUulge6tjpSZH3WNj4h4kqbn9jT0KNeT8UQCHF6cH+bFa6lPEe7yGMEq/oqkYd 8+W7DiaLNMimX2J88xLfqBfa5pEGuc/nRId1yogqjh3Cy1qBXeM7/rRykdniWkYH4uWA OTkQO/N0G8816G2CyEXL/IR9wkAVYRnBo6lUlW+fVNHW877vWbISZO65IgbpZXJD+SuN zPVcjmHHkfdY+zVofh7yHiIgKb6P6+n2mFl7a0+n9COT+/JnpSMd0Bmri2A5JZk+GZfp GBjf6r4NWAr+wkgfz5dKZAqKIpxRL9MBAMRvv1uD0Zgxk77y6TvSc12WOQ8l9iF/YHjj JYqQ== MIME-Version: 1.0 X-Received: by 10.58.6.177 with SMTP id c17mr6381195vea.60.1359707025417; Fri, 01 Feb 2013 00:23:45 -0800 (PST) Received: by 10.58.210.68 with HTTP; Fri, 1 Feb 2013 00:23:45 -0800 (PST) In-Reply-To: <20130201181930.262fa02b@furiza> References: <20130201181930.262fa02b@furiza> Date: Fri, 1 Feb 2013 12:23:45 +0400 Message-ID: From: Borodkin Sergey To: Howell Tam Cc: xen-users@lists.xensource.com Subject: Re: [Xen-users] Intel HD 4000 VGA passthrough not working X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: 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. I have success with Intel HD 3000 pass throught in hvm guest. But guest system is quite unstable. Can you provide me hvm guest config file? On Fri, Feb 1, 2013 at 11:19 AM, Howell Tam wrote: > > > Hi all, > > I have an i7-3770 which has the Intel HD 4000 graphics. I've been trying to pass it through to DomU with no success. > > With a Linux DomU, the i915 module simply will not load because intel_agp is not loaded properly when it cannot find the AGP bridge. ( > > With a Win7 DomU, it BSODs straight away during the boot with SYSTEM_SERVICE_EXCEPTION. > > With a WinXP DomU, it got further but the card is not working as described in the Device Manager, saying there is not enough memory to use the device. > > Is there any pointers on where i should trace and debug this? > > Thanks! > > > Regards, > Howell. > > > _______________________________________________ > 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 Feb 01 08:25:05 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 01 Feb 2013 08:25: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 1U1BuX-0000os-KV; Fri, 01 Feb 2013 08:23:49 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U1BuW-0000on-AM for xen-users@lists.xensource.com; Fri, 01 Feb 2013 08:23:48 +0000 Received: from [85.158.138.51:4267] by server-4.bemta-3.messagelabs.com id BD/88-12802-39B7B015; Fri, 01 Feb 2013 08:23:47 +0000 X-Env-Sender: borodkin.sergey@gmail.com X-Msg-Ref: server-14.tower-174.messagelabs.com!1359707025!22420417!1 X-Originating-IP: [209.85.220.182] 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.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 20462 invoked from network); 1 Feb 2013 08:23:46 -0000 Received: from mail-vc0-f182.google.com (HELO mail-vc0-f182.google.com) (209.85.220.182) by server-14.tower-174.messagelabs.com with RC4-SHA encrypted SMTP; 1 Feb 2013 08:23:46 -0000 Received: by mail-vc0-f182.google.com with SMTP id fl17so2320505vcb.13 for ; Fri, 01 Feb 2013 00:23:45 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=3OZvYNp2TsFrBWLqpk+CbgDcAVE+KqYnAhOIIEvyw94=; b=IvSdyUulge6tjpSZH3WNj4h4kqbn9jT0KNeT8UQCHF6cH+bFa6lPEe7yGMEq/oqkYd 8+W7DiaLNMimX2J88xLfqBfa5pEGuc/nRId1yogqjh3Cy1qBXeM7/rRykdniWkYH4uWA OTkQO/N0G8816G2CyEXL/IR9wkAVYRnBo6lUlW+fVNHW877vWbISZO65IgbpZXJD+SuN zPVcjmHHkfdY+zVofh7yHiIgKb6P6+n2mFl7a0+n9COT+/JnpSMd0Bmri2A5JZk+GZfp GBjf6r4NWAr+wkgfz5dKZAqKIpxRL9MBAMRvv1uD0Zgxk77y6TvSc12WOQ8l9iF/YHjj JYqQ== MIME-Version: 1.0 X-Received: by 10.58.6.177 with SMTP id c17mr6381195vea.60.1359707025417; Fri, 01 Feb 2013 00:23:45 -0800 (PST) Received: by 10.58.210.68 with HTTP; Fri, 1 Feb 2013 00:23:45 -0800 (PST) In-Reply-To: <20130201181930.262fa02b@furiza> References: <20130201181930.262fa02b@furiza> Date: Fri, 1 Feb 2013 12:23:45 +0400 Message-ID: From: Borodkin Sergey To: Howell Tam Cc: xen-users@lists.xensource.com Subject: Re: [Xen-users] Intel HD 4000 VGA passthrough not working X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: 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. I have success with Intel HD 3000 pass throught in hvm guest. But guest system is quite unstable. Can you provide me hvm guest config file? On Fri, Feb 1, 2013 at 11:19 AM, Howell Tam wrote: > > > Hi all, > > I have an i7-3770 which has the Intel HD 4000 graphics. I've been trying to pass it through to DomU with no success. > > With a Linux DomU, the i915 module simply will not load because intel_agp is not loaded properly when it cannot find the AGP bridge. ( > > With a Win7 DomU, it BSODs straight away during the boot with SYSTEM_SERVICE_EXCEPTION. > > With a WinXP DomU, it got further but the card is not working as described in the Device Manager, saying there is not enough memory to use the device. > > Is there any pointers on where i should trace and debug this? > > Thanks! > > > Regards, > Howell. > > > _______________________________________________ > 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 Feb 01 08:26:57 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 01 Feb 2013 08:26: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 1U1BwZ-0000va-El; Fri, 01 Feb 2013 08:25:55 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U1BwX-0000vN-D8 for xen-users@lists.xensource.com; Fri, 01 Feb 2013 08:25:53 +0000 Received: from [85.158.137.99:53703] by server-11.bemta-3.messagelabs.com id CC/63-10249-01C7B015; Fri, 01 Feb 2013 08:25:52 +0000 X-Env-Sender: kristian@hagsted.dk X-Msg-Ref: server-9.tower-217.messagelabs.com!1359707151!16320133!1 X-Originating-IP: [80.160.77.98] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogODAuMTYwLjc3Ljk4ID0+IDE1MDM1Mg==\n X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 11054 invoked from network); 1 Feb 2013 08:25:52 -0000 Received: from pasmtpb.tele.dk (HELO pasmtpB.tele.dk) (80.160.77.98) by server-9.tower-217.messagelabs.com with SMTP; 1 Feb 2013 08:25:52 -0000 Received: from hagsted.dk (2-108-99-186-static.dk.customer.tdc.net [2.108.99.186]) by pasmtpB.tele.dk (Postfix) with ESMTP id 05AE7D801D; Fri, 1 Feb 2013 09:25:50 +0100 (CET) Received: from HAGSTED-BSERVER.hagsted.dk ([fe80::91b7:737e:e057:7c8b]) by hagsted-bserver.hagsted.dk ([fe80::91b7:737e:e057:7c8b%10]) with mapi id 14.02.0328.009; Fri, 1 Feb 2013 09:25:47 +0100 From: Kristian Hagsted Rasmussen To: Howell Tam , "xen-users@lists.xensource.com" Thread-Topic: [Xen-users] Intel HD 4000 VGA passthrough not working Thread-Index: AQHOAE56LrKyRr7TIEaq7EhZZ6rtE5hkqtUA Date: Fri, 1 Feb 2013 08:25:46 +0000 Message-ID: <19EF9FEB5AF86243A3F18E5CE75971640C945735@hagsted-bserver.hagsted.dk> References: <20130201181930.262fa02b@furiza> In-Reply-To: <20130201181930.262fa02b@furiza> Accept-Language: da-DK, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [192.38.90.11] MIME-Version: 1.0 Subject: Re: [Xen-users] Intel HD 4000 VGA passthrough not working X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: 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: xen-users-bounces@lists.xen.org [mailto:xen-users- > bounces@lists.xen.org] On Behalf Of Howell Tam > Sent: 1. februar 2013 08:20 > To: xen-users@lists.xensource.com > Subject: [Xen-users] Intel HD 4000 VGA passthrough not working > > Hi all, > > I have an i7-3770 which has the Intel HD 4000 graphics. I've > been trying to pass it through to DomU with no success. I have a i7-3770t, with HD4000 graphics. > > With a Linux DomU, the i915 module simply will not load > because intel_agp is not loaded properly when it cannot find the AGP bridge. > ( > > With a Win7 DomU, it BSODs straight away during the boot > with SYSTEM_SERVICE_EXCEPTION. For me it works fine in win7, if I use less the 3G of memory in the DomU and of course qemu-xen-traditional as device model. I have not tried winXP or Linux. It should be said that it will not work if you boot in EFI mode, since the VGA-bios is not available to the linux kernel. Best regards Kristian Hagsted Rasmussen _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Fri Feb 01 08:26:57 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 01 Feb 2013 08:26: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 1U1BwZ-0000va-El; Fri, 01 Feb 2013 08:25:55 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U1BwX-0000vN-D8 for xen-users@lists.xensource.com; Fri, 01 Feb 2013 08:25:53 +0000 Received: from [85.158.137.99:53703] by server-11.bemta-3.messagelabs.com id CC/63-10249-01C7B015; Fri, 01 Feb 2013 08:25:52 +0000 X-Env-Sender: kristian@hagsted.dk X-Msg-Ref: server-9.tower-217.messagelabs.com!1359707151!16320133!1 X-Originating-IP: [80.160.77.98] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogODAuMTYwLjc3Ljk4ID0+IDE1MDM1Mg==\n X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 11054 invoked from network); 1 Feb 2013 08:25:52 -0000 Received: from pasmtpb.tele.dk (HELO pasmtpB.tele.dk) (80.160.77.98) by server-9.tower-217.messagelabs.com with SMTP; 1 Feb 2013 08:25:52 -0000 Received: from hagsted.dk (2-108-99-186-static.dk.customer.tdc.net [2.108.99.186]) by pasmtpB.tele.dk (Postfix) with ESMTP id 05AE7D801D; Fri, 1 Feb 2013 09:25:50 +0100 (CET) Received: from HAGSTED-BSERVER.hagsted.dk ([fe80::91b7:737e:e057:7c8b]) by hagsted-bserver.hagsted.dk ([fe80::91b7:737e:e057:7c8b%10]) with mapi id 14.02.0328.009; Fri, 1 Feb 2013 09:25:47 +0100 From: Kristian Hagsted Rasmussen To: Howell Tam , "xen-users@lists.xensource.com" Thread-Topic: [Xen-users] Intel HD 4000 VGA passthrough not working Thread-Index: AQHOAE56LrKyRr7TIEaq7EhZZ6rtE5hkqtUA Date: Fri, 1 Feb 2013 08:25:46 +0000 Message-ID: <19EF9FEB5AF86243A3F18E5CE75971640C945735@hagsted-bserver.hagsted.dk> References: <20130201181930.262fa02b@furiza> In-Reply-To: <20130201181930.262fa02b@furiza> Accept-Language: da-DK, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [192.38.90.11] MIME-Version: 1.0 Subject: Re: [Xen-users] Intel HD 4000 VGA passthrough not working X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: 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: xen-users-bounces@lists.xen.org [mailto:xen-users- > bounces@lists.xen.org] On Behalf Of Howell Tam > Sent: 1. februar 2013 08:20 > To: xen-users@lists.xensource.com > Subject: [Xen-users] Intel HD 4000 VGA passthrough not working > > Hi all, > > I have an i7-3770 which has the Intel HD 4000 graphics. I've > been trying to pass it through to DomU with no success. I have a i7-3770t, with HD4000 graphics. > > With a Linux DomU, the i915 module simply will not load > because intel_agp is not loaded properly when it cannot find the AGP bridge. > ( > > With a Win7 DomU, it BSODs straight away during the boot > with SYSTEM_SERVICE_EXCEPTION. For me it works fine in win7, if I use less the 3G of memory in the DomU and of course qemu-xen-traditional as device model. I have not tried winXP or Linux. It should be said that it will not work if you boot in EFI mode, since the VGA-bios is not available to the linux kernel. Best regards Kristian Hagsted Rasmussen _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Fri Feb 01 08:58:05 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 01 Feb 2013 08:58: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 1U1CQR-0001VF-DU; Fri, 01 Feb 2013 08:56:47 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U1CQP-0001VA-Nx for xen-users@lists.xensource.com; Fri, 01 Feb 2013 08:56:45 +0000 Received: from [85.158.137.99:26973] by server-11.bemta-3.messagelabs.com id 85/D0-10249-8438B015; Fri, 01 Feb 2013 08:56:40 +0000 X-Env-Sender: Ian.Campbell@citrix.com X-Msg-Ref: server-9.tower-217.messagelabs.com!1359708996!16324901!1 X-Originating-IP: [46.33.159.39] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNDYuMzMuMTU5LjM5ID0+IDIwMDQw\n X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 4132 invoked from network); 1 Feb 2013 08:56:36 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (46.33.159.39) by server-9.tower-217.messagelabs.com with RC4-SHA encrypted SMTP; 1 Feb 2013 08:56:36 -0000 X-IronPort-AV: E=Sophos;i="4.84,579,1355097600"; d="scan'208";a="1055160" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 01 Feb 2013 08:56: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.297.1; Fri, 1 Feb 2013 08:56:35 +0000 Message-ID: <1359708995.9063.3.camel@dagon.hellion.org.uk> From: Ian Campbell To: Markus Hochholdinger Date: Fri, 1 Feb 2013 08:56:35 +0000 In-Reply-To: <201301312044.17684.Markus@hochholdinger.net> References: <201301291646.43567.Markus@hochholdinger.net> <201301301635.25005.Markus@hochholdinger.net> <1359631341.12252.289.camel@zakaz.uk.xensource.com> <201301312044.17684.Markus@hochholdinger.net> Organization: Citrix Systems, Inc. X-Mailer: Evolution 3.4.4-1 MIME-Version: 1.0 Cc: "xen-users@lists.xensource.com" Subject: Re: [Xen-users] linux stubdom X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org > > > Am I missing something? > > Migration is a staged process. > > 1. First an empty shell domain (with no devices) is created on the > > target host. > > 2. Then we copy the memory over, in several iterations, while the > > domain is running on the source host (iterations happen to > > handle the guest dirtying memory as we copy, this is the "live" > > aspect of the migration). > > 3. After some iterations of live migration we pause the source > > guest > > 4. Now we copy the remaining dirty RAM > > 5. Tear down devices on the source host > > 6. Setup devices on the target host for the incoming domain > > 7. Resume the guest on the target domain > > 8. Guest reconnects to new backend > > The key point is that the devices are only ever active on either the > > source or the target host and never both. The domain is paused during > > this final transfer (from #3 until #7) and therefore guest I/O is > > quiesced. > > At what point are scripts like > disk = [ ".., script=myblockscript.sh" ] > executed? Would this be between #3 and #7? It is part of the device teardown and setup, so it is during #5 and #6 (strictly I think it is just after #5 and just before #6). On xen-devel at the minute there is a patch series under discussion to make the script hooks more flexible, in particular adding pre and post migrate hooks (called something like #1-#3 and #7-#7) which can pre setup bits of the storage stack which are safe to do with the guest running but might be slow to initialise (e.g. iSCSI login, but not opening the device). I don't think this needs to affect you though. > > > > ensure that the block device is only ever active on one end of the > > > > other and never on both -- otherwise you would get potential > > > > corruption. > > > Yeah, this is the problem! If I migrate the active raid1 logic within the > > > domU (aka linux software raid1) I don't have to care. I'll try to > > > accomplish the same with a "helper" domU very near to the normal domU > > > and which is live migrated while the normal domU is migrated. > > This might be possible but as I say the more normal approach would be to > > have a "RAID" domain on both hosts and dynamically map and unmap the > > backing guest disks at steps #5 and #6 above. > > With the above info, that block devices are removed and added in the right > order while doing live migration, I'm thinking more and more about a driver > domain. > > But in the first place I'll test the stopping and assembling of md devices in > the dom0s while migrating. If this works I could put this job into a driver > domain. Wow, this gives me a new view of the setup. Excellent ;-) Ian. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Fri Feb 01 08:58:05 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 01 Feb 2013 08:58: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 1U1CQR-0001VF-DU; Fri, 01 Feb 2013 08:56:47 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U1CQP-0001VA-Nx for xen-users@lists.xensource.com; Fri, 01 Feb 2013 08:56:45 +0000 Received: from [85.158.137.99:26973] by server-11.bemta-3.messagelabs.com id 85/D0-10249-8438B015; Fri, 01 Feb 2013 08:56:40 +0000 X-Env-Sender: Ian.Campbell@citrix.com X-Msg-Ref: server-9.tower-217.messagelabs.com!1359708996!16324901!1 X-Originating-IP: [46.33.159.39] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNDYuMzMuMTU5LjM5ID0+IDIwMDQw\n X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 4132 invoked from network); 1 Feb 2013 08:56:36 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (46.33.159.39) by server-9.tower-217.messagelabs.com with RC4-SHA encrypted SMTP; 1 Feb 2013 08:56:36 -0000 X-IronPort-AV: E=Sophos;i="4.84,579,1355097600"; d="scan'208";a="1055160" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 01 Feb 2013 08:56: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.297.1; Fri, 1 Feb 2013 08:56:35 +0000 Message-ID: <1359708995.9063.3.camel@dagon.hellion.org.uk> From: Ian Campbell To: Markus Hochholdinger Date: Fri, 1 Feb 2013 08:56:35 +0000 In-Reply-To: <201301312044.17684.Markus@hochholdinger.net> References: <201301291646.43567.Markus@hochholdinger.net> <201301301635.25005.Markus@hochholdinger.net> <1359631341.12252.289.camel@zakaz.uk.xensource.com> <201301312044.17684.Markus@hochholdinger.net> Organization: Citrix Systems, Inc. X-Mailer: Evolution 3.4.4-1 MIME-Version: 1.0 Cc: "xen-users@lists.xensource.com" Subject: Re: [Xen-users] linux stubdom X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org > > > Am I missing something? > > Migration is a staged process. > > 1. First an empty shell domain (with no devices) is created on the > > target host. > > 2. Then we copy the memory over, in several iterations, while the > > domain is running on the source host (iterations happen to > > handle the guest dirtying memory as we copy, this is the "live" > > aspect of the migration). > > 3. After some iterations of live migration we pause the source > > guest > > 4. Now we copy the remaining dirty RAM > > 5. Tear down devices on the source host > > 6. Setup devices on the target host for the incoming domain > > 7. Resume the guest on the target domain > > 8. Guest reconnects to new backend > > The key point is that the devices are only ever active on either the > > source or the target host and never both. The domain is paused during > > this final transfer (from #3 until #7) and therefore guest I/O is > > quiesced. > > At what point are scripts like > disk = [ ".., script=myblockscript.sh" ] > executed? Would this be between #3 and #7? It is part of the device teardown and setup, so it is during #5 and #6 (strictly I think it is just after #5 and just before #6). On xen-devel at the minute there is a patch series under discussion to make the script hooks more flexible, in particular adding pre and post migrate hooks (called something like #1-#3 and #7-#7) which can pre setup bits of the storage stack which are safe to do with the guest running but might be slow to initialise (e.g. iSCSI login, but not opening the device). I don't think this needs to affect you though. > > > > ensure that the block device is only ever active on one end of the > > > > other and never on both -- otherwise you would get potential > > > > corruption. > > > Yeah, this is the problem! If I migrate the active raid1 logic within the > > > domU (aka linux software raid1) I don't have to care. I'll try to > > > accomplish the same with a "helper" domU very near to the normal domU > > > and which is live migrated while the normal domU is migrated. > > This might be possible but as I say the more normal approach would be to > > have a "RAID" domain on both hosts and dynamically map and unmap the > > backing guest disks at steps #5 and #6 above. > > With the above info, that block devices are removed and added in the right > order while doing live migration, I'm thinking more and more about a driver > domain. > > But in the first place I'll test the stopping and assembling of md devices in > the dom0s while migrating. If this works I could put this job into a driver > domain. Wow, this gives me a new view of the setup. Excellent ;-) Ian. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Fri Feb 01 09:46:29 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 01 Feb 2013 09:46: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 1U1DBM-000235-S2; Fri, 01 Feb 2013 09:45:16 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U1DBL-00022v-3T for xen-users@lists.xensource.com; Fri, 01 Feb 2013 09:45:15 +0000 Received: from [85.158.139.211:29716] by server-9.bemta-5.messagelabs.com id 78/AB-24440-AAE8B015; Fri, 01 Feb 2013 09:45:14 +0000 X-Env-Sender: pigeon@pigeond.net X-Msg-Ref: server-14.tower-206.messagelabs.com!1359711911!20594080!1 X-Originating-IP: [203.59.1.222] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogMjAzLjU5LjEuMjIyID0+IDE3NTk2\n X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 14493 invoked from network); 1 Feb 2013 09:45:13 -0000 Received: from icp-osb-irony-out6.external.iinet.net.au (HELO icp-osb-irony-out6.external.iinet.net.au) (203.59.1.222) by server-14.tower-206.messagelabs.com with SMTP; 1 Feb 2013 09:45:13 -0000 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AioMACaOC1F8lWUl/2dsb2JhbABFuRaGDhZzgh4BAQQBOkQLCw0UJQ9IBogeBcJIFZB3A5YThhOKPIMP X-IronPort-AV: E=Sophos;i="4.84,579,1355068800"; d="scan'208";a="82650298" Received: from unknown (HELO torankusu.pigeond.net) ([124.149.101.37]) by icp-osb-irony-out6.iinet.net.au with ESMTP; 01 Feb 2013 17:45:09 +0800 Received: from furiza.pigeond.net ([192.168.42.20]:45362 helo=furiza) by torankusu.pigeond.net with esmtp (Exim 4.72) (envelope-from ) id 1U1DBE-0007An-N9 for xen-users@lists.xensource.com; Fri, 01 Feb 2013 20:45:09 +1100 Date: Fri, 1 Feb 2013 20:45:07 +1100 From: Howell Tam To: "xen-users@lists.xensource.com" Message-ID: <20130201204507.45c74f94@furiza> In-Reply-To: <19EF9FEB5AF86243A3F18E5CE75971640C945735@hagsted-bserver.hagsted.dk> References: <20130201181930.262fa02b@furiza> <19EF9FEB5AF86243A3F18E5CE75971640C945735@hagsted-bserver.hagsted.dk> Organization: pigeond.net X-Mailer: Claws Mail 3.8.1 (GTK+ 2.24.13; x86_64-pc-linux-gnu) Mime-Version: 1.0 Subject: Re: [Xen-users] Intel HD 4000 VGA passthrough not working X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org > For me it works fine in win7, if I use less the 3G of memory in the > DomU and of course qemu-xen-traditional as device model. I have not > tried winXP or Linux. It should be said that it will not work if you > boot in EFI mode, since the VGA-bios is not available to the linux > kernel. Thanks for your info. So it is a known issue to use more than 3G of memory? How do I make sure I'm not booting the EFI mode? I noticed my bios has several settings about UEFI or legacy, and so I should set them all to legacy? Is there any other things i should make sure? Thanks! Regards, Howell. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Fri Feb 01 09:46:29 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 01 Feb 2013 09:46: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 1U1DBM-000235-S2; Fri, 01 Feb 2013 09:45:16 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U1DBL-00022v-3T for xen-users@lists.xensource.com; Fri, 01 Feb 2013 09:45:15 +0000 Received: from [85.158.139.211:29716] by server-9.bemta-5.messagelabs.com id 78/AB-24440-AAE8B015; Fri, 01 Feb 2013 09:45:14 +0000 X-Env-Sender: pigeon@pigeond.net X-Msg-Ref: server-14.tower-206.messagelabs.com!1359711911!20594080!1 X-Originating-IP: [203.59.1.222] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogMjAzLjU5LjEuMjIyID0+IDE3NTk2\n X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 14493 invoked from network); 1 Feb 2013 09:45:13 -0000 Received: from icp-osb-irony-out6.external.iinet.net.au (HELO icp-osb-irony-out6.external.iinet.net.au) (203.59.1.222) by server-14.tower-206.messagelabs.com with SMTP; 1 Feb 2013 09:45:13 -0000 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AioMACaOC1F8lWUl/2dsb2JhbABFuRaGDhZzgh4BAQQBOkQLCw0UJQ9IBogeBcJIFZB3A5YThhOKPIMP X-IronPort-AV: E=Sophos;i="4.84,579,1355068800"; d="scan'208";a="82650298" Received: from unknown (HELO torankusu.pigeond.net) ([124.149.101.37]) by icp-osb-irony-out6.iinet.net.au with ESMTP; 01 Feb 2013 17:45:09 +0800 Received: from furiza.pigeond.net ([192.168.42.20]:45362 helo=furiza) by torankusu.pigeond.net with esmtp (Exim 4.72) (envelope-from ) id 1U1DBE-0007An-N9 for xen-users@lists.xensource.com; Fri, 01 Feb 2013 20:45:09 +1100 Date: Fri, 1 Feb 2013 20:45:07 +1100 From: Howell Tam To: "xen-users@lists.xensource.com" Message-ID: <20130201204507.45c74f94@furiza> In-Reply-To: <19EF9FEB5AF86243A3F18E5CE75971640C945735@hagsted-bserver.hagsted.dk> References: <20130201181930.262fa02b@furiza> <19EF9FEB5AF86243A3F18E5CE75971640C945735@hagsted-bserver.hagsted.dk> Organization: pigeond.net X-Mailer: Claws Mail 3.8.1 (GTK+ 2.24.13; x86_64-pc-linux-gnu) Mime-Version: 1.0 Subject: Re: [Xen-users] Intel HD 4000 VGA passthrough not working X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org > For me it works fine in win7, if I use less the 3G of memory in the > DomU and of course qemu-xen-traditional as device model. I have not > tried winXP or Linux. It should be said that it will not work if you > boot in EFI mode, since the VGA-bios is not available to the linux > kernel. Thanks for your info. So it is a known issue to use more than 3G of memory? How do I make sure I'm not booting the EFI mode? I noticed my bios has several settings about UEFI or legacy, and so I should set them all to legacy? Is there any other things i should make sure? Thanks! Regards, Howell. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Fri Feb 01 09:54:17 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 01 Feb 2013 09:54: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 1U1DJ9-0002I9-6w; Fri, 01 Feb 2013 09:53:19 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U1DJ7-0002I4-Qt for xen-users@lists.xensource.com; Fri, 01 Feb 2013 09:53:17 +0000 Received: from [85.158.137.99:32386] by server-12.bemta-3.messagelabs.com id 61/1A-05889-8809B015; Fri, 01 Feb 2013 09:53:12 +0000 X-Env-Sender: pigeon@pigeond.net X-Msg-Ref: server-15.tower-217.messagelabs.com!1359712390!17177736!1 X-Originating-IP: [203.59.1.222] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogMjAzLjU5LjEuMjIyID0+IDE3NTk2\n X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 22370 invoked from network); 1 Feb 2013 09:53:12 -0000 Received: from icp-osb-irony-out6.external.iinet.net.au (HELO icp-osb-irony-out6.external.iinet.net.au) (203.59.1.222) by server-15.tower-217.messagelabs.com with SMTP; 1 Feb 2013 09:53:12 -0000 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AioMAGKPC1F8lWUl/2dsb2JhbABFuRaGDxZzgh4BAQQBOkQLCw0UJQ9IiCQFwkkVjU6DKQOWE4YTijyDDw X-IronPort-AV: E=Sophos;i="4.84,579,1355068800"; d="scan'208";a="82651654" Received: from unknown (HELO torankusu.pigeond.net) ([124.149.101.37]) by icp-osb-irony-out6.iinet.net.au with ESMTP; 01 Feb 2013 17:53:05 +0800 Received: from furiza.pigeond.net ([192.168.42.20]:45384 helo=furiza) by torankusu.pigeond.net with esmtp (Exim 4.72) (envelope-from ) id 1U1DIu-0007CP-NN for xen-users@lists.xensource.com; Fri, 01 Feb 2013 20:53:05 +1100 Date: Fri, 1 Feb 2013 20:53:03 +1100 From: Howell Tam To: xen-users@lists.xensource.com Message-ID: <20130201205303.646ac7f3@furiza> In-Reply-To: References: <20130201181930.262fa02b@furiza> Organization: pigeond.net X-Mailer: Claws Mail 3.8.1 (GTK+ 2.24.13; x86_64-pc-linux-gnu) Mime-Version: 1.0 Subject: Re: [Xen-users] Intel HD 4000 VGA passthrough not working X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: 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 success with Intel HD 3000 pass throught in hvm guest. But > guest system is quite unstable. > Can you provide me hvm guest config file? My hvm guest config file is quite straight forward. I guess the important ones are: name="domu-win7" builder="hvm" memory=8192 acpi=1 apic=1 viridian=1 pci_msitranslate=0 pci_power_mgmt=0 gfx_passthru=1 xen_platform_pci=1 disk=[ 'phy:/dev/xen/domu-win7,hda,w' ] # 00:02.0 is Intel HD 4000, 00:1d.0 is a usb bus pci = [ '00:02.0', '00:1d.0' ] I have also tried switching things like pci_mistranslate and gfx_passthru but it's the same. And btw I have tried Xen 4.2.x and 4.3 upstream hg tree and results are the same. Thanks! Regards, Howell. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Fri Feb 01 09:54:17 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 01 Feb 2013 09:54: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 1U1DJ9-0002I9-6w; Fri, 01 Feb 2013 09:53:19 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U1DJ7-0002I4-Qt for xen-users@lists.xensource.com; Fri, 01 Feb 2013 09:53:17 +0000 Received: from [85.158.137.99:32386] by server-12.bemta-3.messagelabs.com id 61/1A-05889-8809B015; Fri, 01 Feb 2013 09:53:12 +0000 X-Env-Sender: pigeon@pigeond.net X-Msg-Ref: server-15.tower-217.messagelabs.com!1359712390!17177736!1 X-Originating-IP: [203.59.1.222] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogMjAzLjU5LjEuMjIyID0+IDE3NTk2\n X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 22370 invoked from network); 1 Feb 2013 09:53:12 -0000 Received: from icp-osb-irony-out6.external.iinet.net.au (HELO icp-osb-irony-out6.external.iinet.net.au) (203.59.1.222) by server-15.tower-217.messagelabs.com with SMTP; 1 Feb 2013 09:53:12 -0000 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AioMAGKPC1F8lWUl/2dsb2JhbABFuRaGDxZzgh4BAQQBOkQLCw0UJQ9IiCQFwkkVjU6DKQOWE4YTijyDDw X-IronPort-AV: E=Sophos;i="4.84,579,1355068800"; d="scan'208";a="82651654" Received: from unknown (HELO torankusu.pigeond.net) ([124.149.101.37]) by icp-osb-irony-out6.iinet.net.au with ESMTP; 01 Feb 2013 17:53:05 +0800 Received: from furiza.pigeond.net ([192.168.42.20]:45384 helo=furiza) by torankusu.pigeond.net with esmtp (Exim 4.72) (envelope-from ) id 1U1DIu-0007CP-NN for xen-users@lists.xensource.com; Fri, 01 Feb 2013 20:53:05 +1100 Date: Fri, 1 Feb 2013 20:53:03 +1100 From: Howell Tam To: xen-users@lists.xensource.com Message-ID: <20130201205303.646ac7f3@furiza> In-Reply-To: References: <20130201181930.262fa02b@furiza> Organization: pigeond.net X-Mailer: Claws Mail 3.8.1 (GTK+ 2.24.13; x86_64-pc-linux-gnu) Mime-Version: 1.0 Subject: Re: [Xen-users] Intel HD 4000 VGA passthrough not working X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: 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 success with Intel HD 3000 pass throught in hvm guest. But > guest system is quite unstable. > Can you provide me hvm guest config file? My hvm guest config file is quite straight forward. I guess the important ones are: name="domu-win7" builder="hvm" memory=8192 acpi=1 apic=1 viridian=1 pci_msitranslate=0 pci_power_mgmt=0 gfx_passthru=1 xen_platform_pci=1 disk=[ 'phy:/dev/xen/domu-win7,hda,w' ] # 00:02.0 is Intel HD 4000, 00:1d.0 is a usb bus pci = [ '00:02.0', '00:1d.0' ] I have also tried switching things like pci_mistranslate and gfx_passthru but it's the same. And btw I have tried Xen 4.2.x and 4.3 upstream hg tree and results are the same. Thanks! Regards, Howell. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Fri Feb 01 10:13:37 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 01 Feb 2013 10:13: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 1U1Dby-0002nf-Pa; Fri, 01 Feb 2013 10:12:46 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U1Dbw-0002nQ-Sl; Fri, 01 Feb 2013 10:12:45 +0000 Received: from [85.158.143.35:45163] by server-3.bemta-4.messagelabs.com id 1F/75-08920-C159B015; Fri, 01 Feb 2013 10:12:44 +0000 X-Env-Sender: mailinglists.tech@gmail.com X-Msg-Ref: server-3.tower-21.messagelabs.com!1359713142!13347088!1 X-Originating-IP: [209.85.212.179] 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.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 26586 invoked from network); 1 Feb 2013 10:05:46 -0000 Received: from mail-wi0-f179.google.com (HELO mail-wi0-f179.google.com) (209.85.212.179) by server-3.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 1 Feb 2013 10:05:46 -0000 Received: by mail-wi0-f179.google.com with SMTP id ez12so370915wid.12 for ; Fri, 01 Feb 2013 02:05:42 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:date:message-id:subject:from:to :content-type; bh=4BGPjfra0VX/mv+hjsIIPbwONDtwdbZqVQPmBkL6hUQ=; b=IMCiPp6JkRL3pZysMnsqTP5rYH+/YE8PpEswYnKB3t+xAexHykBh8SK0XpCEX0Zh8E /osb2rEfaTRGn93Lp41PG25y7hT32l9tK+3lxeCjza6wfkwj5fivfKtzQSB0bjPJVW8z IuVeTCqndT0OFEt3ZVPHVp+MpRiIO6XuetWrn5W4r2d/Jou5R/5K5yd0t98i84uiO2EY hRf0qd7U8fje52zK4S++G4oSZZlsoz+TtJqgnlrAIfy8Gb7ZShutxZxXWHlSSHTRyDxt F8J5X2+RSRFhCFh7Qnr/5RmyBobNafcYCtJa4wQAq7wfhtB6DSypMkVIlysflhsQozyc w9Tw== MIME-Version: 1.0 X-Received: by 10.194.76.7 with SMTP id g7mr20550532wjw.50.1359713140241; Fri, 01 Feb 2013 02:05:40 -0800 (PST) Received: by 10.227.203.18 with HTTP; Fri, 1 Feb 2013 02:05:40 -0800 (PST) Date: Fri, 1 Feb 2013 11:05:40 +0100 Message-ID: From: tech mailinglists To: xen-users , "xen-devel@lists.xen.org" Subject: [Xen-users] xenstore stubdom on Xen 4.2.1 (XSM/FLASK problem) X-BeenThere: xen-users@lists.xen.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="===============8493089107909685972==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============8493089107909685972== Content-Type: multipart/alternative; boundary=047d7beba202b8732d04d4a6e213 --047d7beba202b8732d04d4a6e213 Content-Type: text/plain; charset=ISO-8859-1 Hello all, I am trying to get a xenstore/oxenstore (oxenstore is mirage based) stubdom to get to work on Xen 4.2.1. I know that I need to set XSM/FLASK rules and so I have compiled 4.2.1 with XSM and FLASK. I already talked with Daniel de Graaf (on the mailinglists) and Steven Maresca on IRC about this thing. Daniel already wrote a XSM/FLASK ruleset in this thread: http://lists.xen.org/archives/html/xen-devel/2013-01/msg00956.html So he said that this rule is incompatible with 4.2.1 and only works on 4.3 unstable. I know that there are more or less just sysctl hypercalls are support in XSM/FLASK on 4.2.1 and no domctl hypercalls. Is it possible to write a ruleset (or modifying the existing one) so that it is compatible with 4.2.1? Hope that someone could help me. Best Regards --047d7beba202b8732d04d4a6e213 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Hello all,

I am trying to get a= xenstore/oxenstore (oxenstore is mirage based) stubdom to get to work on X= en 4.2.1.

I know that I need to set XSM/FLASK rules and so I have co= mpiled 4.2.1 with XSM and FLASK.

I already talked with Daniel de Graaf (on the mailinglists) and S= teven Maresca on IRC about this thing. Daniel already wrote a XSM/FLASK rul= eset in this thread: http://lists.xen.org/archives/html/xen-devel/2013-= 01/msg00956.html

So he said that this rule is incompatible with 4.2.1 and only wor= ks on 4.3 unstable. I know that there are more or less just sysctl hypercal= ls are support in XSM/FLASK on 4.2.1 and no domctl hypercalls.

Is it possible to write a ruleset (or modifying the existing one) so that i= t is compatible with 4.2.1?

Hope that someone could help me.
Best Regards
--047d7beba202b8732d04d4a6e213-- --===============8493089107909685972== 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 --===============8493089107909685972==-- From xen-users-bounces@lists.xen.org Fri Feb 01 10:13:37 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 01 Feb 2013 10:13: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 1U1Dby-0002nf-Pa; Fri, 01 Feb 2013 10:12:46 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U1Dbw-0002nQ-Sl; Fri, 01 Feb 2013 10:12:45 +0000 Received: from [85.158.143.35:45163] by server-3.bemta-4.messagelabs.com id 1F/75-08920-C159B015; Fri, 01 Feb 2013 10:12:44 +0000 X-Env-Sender: mailinglists.tech@gmail.com X-Msg-Ref: server-3.tower-21.messagelabs.com!1359713142!13347088!1 X-Originating-IP: [209.85.212.179] 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.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 26586 invoked from network); 1 Feb 2013 10:05:46 -0000 Received: from mail-wi0-f179.google.com (HELO mail-wi0-f179.google.com) (209.85.212.179) by server-3.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 1 Feb 2013 10:05:46 -0000 Received: by mail-wi0-f179.google.com with SMTP id ez12so370915wid.12 for ; Fri, 01 Feb 2013 02:05:42 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:date:message-id:subject:from:to :content-type; bh=4BGPjfra0VX/mv+hjsIIPbwONDtwdbZqVQPmBkL6hUQ=; b=IMCiPp6JkRL3pZysMnsqTP5rYH+/YE8PpEswYnKB3t+xAexHykBh8SK0XpCEX0Zh8E /osb2rEfaTRGn93Lp41PG25y7hT32l9tK+3lxeCjza6wfkwj5fivfKtzQSB0bjPJVW8z IuVeTCqndT0OFEt3ZVPHVp+MpRiIO6XuetWrn5W4r2d/Jou5R/5K5yd0t98i84uiO2EY hRf0qd7U8fje52zK4S++G4oSZZlsoz+TtJqgnlrAIfy8Gb7ZShutxZxXWHlSSHTRyDxt F8J5X2+RSRFhCFh7Qnr/5RmyBobNafcYCtJa4wQAq7wfhtB6DSypMkVIlysflhsQozyc w9Tw== MIME-Version: 1.0 X-Received: by 10.194.76.7 with SMTP id g7mr20550532wjw.50.1359713140241; Fri, 01 Feb 2013 02:05:40 -0800 (PST) Received: by 10.227.203.18 with HTTP; Fri, 1 Feb 2013 02:05:40 -0800 (PST) Date: Fri, 1 Feb 2013 11:05:40 +0100 Message-ID: From: tech mailinglists To: xen-users , "xen-devel@lists.xen.org" Subject: [Xen-users] xenstore stubdom on Xen 4.2.1 (XSM/FLASK problem) X-BeenThere: xen-users@lists.xen.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="===============8493089107909685972==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============8493089107909685972== Content-Type: multipart/alternative; boundary=047d7beba202b8732d04d4a6e213 --047d7beba202b8732d04d4a6e213 Content-Type: text/plain; charset=ISO-8859-1 Hello all, I am trying to get a xenstore/oxenstore (oxenstore is mirage based) stubdom to get to work on Xen 4.2.1. I know that I need to set XSM/FLASK rules and so I have compiled 4.2.1 with XSM and FLASK. I already talked with Daniel de Graaf (on the mailinglists) and Steven Maresca on IRC about this thing. Daniel already wrote a XSM/FLASK ruleset in this thread: http://lists.xen.org/archives/html/xen-devel/2013-01/msg00956.html So he said that this rule is incompatible with 4.2.1 and only works on 4.3 unstable. I know that there are more or less just sysctl hypercalls are support in XSM/FLASK on 4.2.1 and no domctl hypercalls. Is it possible to write a ruleset (or modifying the existing one) so that it is compatible with 4.2.1? Hope that someone could help me. Best Regards --047d7beba202b8732d04d4a6e213 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Hello all,

I am trying to get a= xenstore/oxenstore (oxenstore is mirage based) stubdom to get to work on X= en 4.2.1.

I know that I need to set XSM/FLASK rules and so I have co= mpiled 4.2.1 with XSM and FLASK.

I already talked with Daniel de Graaf (on the mailinglists) and S= teven Maresca on IRC about this thing. Daniel already wrote a XSM/FLASK rul= eset in this thread: http://lists.xen.org/archives/html/xen-devel/2013-= 01/msg00956.html

So he said that this rule is incompatible with 4.2.1 and only wor= ks on 4.3 unstable. I know that there are more or less just sysctl hypercal= ls are support in XSM/FLASK on 4.2.1 and no domctl hypercalls.

Is it possible to write a ruleset (or modifying the existing one) so that i= t is compatible with 4.2.1?

Hope that someone could help me.
Best Regards
--047d7beba202b8732d04d4a6e213-- --===============8493089107909685972== 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 --===============8493089107909685972==-- From xen-users-bounces@lists.xen.org Fri Feb 01 10:21:53 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 01 Feb 2013 10:21: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 1U1Dk7-0003Cl-1r; Fri, 01 Feb 2013 10:21:11 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U1Dk4-0003Cf-Rp for xen-users@lists.xensource.com; Fri, 01 Feb 2013 10:21:09 +0000 Received: from [85.158.139.83:13076] by server-16.bemta-5.messagelabs.com id 4B/75-14948-4179B015; Fri, 01 Feb 2013 10:21:08 +0000 X-Env-Sender: kristian@hagsted.dk X-Msg-Ref: server-13.tower-182.messagelabs.com!1359714066!29537544!1 X-Originating-IP: [80.160.77.98] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogODAuMTYwLjc3Ljk4ID0+IDE1MTEzNw==\n X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 2798 invoked from network); 1 Feb 2013 10:21:07 -0000 Received: from pasmtpb.tele.dk (HELO pasmtpB.tele.dk) (80.160.77.98) by server-13.tower-182.messagelabs.com with SMTP; 1 Feb 2013 10:21:07 -0000 Received: from hagsted.dk (2-108-99-186-static.dk.customer.tdc.net [2.108.99.186]) by pasmtpB.tele.dk (Postfix) with ESMTP id 14D84D813E; Fri, 1 Feb 2013 11:21:06 +0100 (CET) Received: from HAGSTED-BSERVER.hagsted.dk ([fe80::91b7:737e:e057:7c8b]) by hagsted-bserver.hagsted.dk ([fe80::91b7:737e:e057:7c8b%10]) with mapi id 14.02.0328.009; Fri, 1 Feb 2013 11:21:02 +0100 From: Kristian Hagsted Rasmussen To: Howell Tam , "xen-users@lists.xensource.com" Thread-Topic: [Xen-users] Intel HD 4000 VGA passthrough not working Thread-Index: AQHOAE56LrKyRr7TIEaq7EhZZ6rtE5hkqtUAgAAFbYCAABh9IA== Date: Fri, 1 Feb 2013 10:21:02 +0000 Message-ID: <19EF9FEB5AF86243A3F18E5CE75971640C945789@hagsted-bserver.hagsted.dk> References: <20130201181930.262fa02b@furiza> <19EF9FEB5AF86243A3F18E5CE75971640C945735@hagsted-bserver.hagsted.dk> <20130201204507.45c74f94@furiza> In-Reply-To: <20130201204507.45c74f94@furiza> Accept-Language: da-DK, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [192.38.90.11] MIME-Version: 1.0 Subject: Re: [Xen-users] Intel HD 4000 VGA passthrough not working X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: 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: xen-users-bounces@lists.xen.org [mailto:xen-users- > bounces@lists.xen.org] On Behalf Of Howell Tam > Sent: 1. februar 2013 10:45 > To: xen-users@lists.xensource.com > Subject: Re: [Xen-users] Intel HD 4000 VGA passthrough not working > > > > > For me it works fine in win7, if I use less the 3G of memory in the > > DomU and of course qemu-xen-traditional as device model. I have not > > tried winXP or Linux. It should be said that it will not work if you > > boot in EFI mode, since the VGA-bios is not available to the linux > > kernel. > > Thanks for your info. > > So it is a known issue to use more than 3G of memory? I seem to remember that another user mentioned problems with 4G of memory. I am not sure of the amount at which this problem is solved, but you could try with more than 3GB to check if it works. > > How do I make sure I'm not booting the EFI mode? I noticed > my bios has several settings about UEFI or legacy, and so I should set them all > to legacy? Is there any other things i should make sure? Which distro's do you use as dom0? Most distros will not use EFI as default, as far as I'm aware. For a command I cannot remember, but you could check which bootloader you have installed, the EFI versions are called something as grub-efi and elilo. Kind regards Kristian Hagsted Rasmussen _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Fri Feb 01 10:21:53 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 01 Feb 2013 10:21: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 1U1Dk7-0003Cl-1r; Fri, 01 Feb 2013 10:21:11 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U1Dk4-0003Cf-Rp for xen-users@lists.xensource.com; Fri, 01 Feb 2013 10:21:09 +0000 Received: from [85.158.139.83:13076] by server-16.bemta-5.messagelabs.com id 4B/75-14948-4179B015; Fri, 01 Feb 2013 10:21:08 +0000 X-Env-Sender: kristian@hagsted.dk X-Msg-Ref: server-13.tower-182.messagelabs.com!1359714066!29537544!1 X-Originating-IP: [80.160.77.98] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogODAuMTYwLjc3Ljk4ID0+IDE1MTEzNw==\n X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 2798 invoked from network); 1 Feb 2013 10:21:07 -0000 Received: from pasmtpb.tele.dk (HELO pasmtpB.tele.dk) (80.160.77.98) by server-13.tower-182.messagelabs.com with SMTP; 1 Feb 2013 10:21:07 -0000 Received: from hagsted.dk (2-108-99-186-static.dk.customer.tdc.net [2.108.99.186]) by pasmtpB.tele.dk (Postfix) with ESMTP id 14D84D813E; Fri, 1 Feb 2013 11:21:06 +0100 (CET) Received: from HAGSTED-BSERVER.hagsted.dk ([fe80::91b7:737e:e057:7c8b]) by hagsted-bserver.hagsted.dk ([fe80::91b7:737e:e057:7c8b%10]) with mapi id 14.02.0328.009; Fri, 1 Feb 2013 11:21:02 +0100 From: Kristian Hagsted Rasmussen To: Howell Tam , "xen-users@lists.xensource.com" Thread-Topic: [Xen-users] Intel HD 4000 VGA passthrough not working Thread-Index: AQHOAE56LrKyRr7TIEaq7EhZZ6rtE5hkqtUAgAAFbYCAABh9IA== Date: Fri, 1 Feb 2013 10:21:02 +0000 Message-ID: <19EF9FEB5AF86243A3F18E5CE75971640C945789@hagsted-bserver.hagsted.dk> References: <20130201181930.262fa02b@furiza> <19EF9FEB5AF86243A3F18E5CE75971640C945735@hagsted-bserver.hagsted.dk> <20130201204507.45c74f94@furiza> In-Reply-To: <20130201204507.45c74f94@furiza> Accept-Language: da-DK, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [192.38.90.11] MIME-Version: 1.0 Subject: Re: [Xen-users] Intel HD 4000 VGA passthrough not working X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: 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: xen-users-bounces@lists.xen.org [mailto:xen-users- > bounces@lists.xen.org] On Behalf Of Howell Tam > Sent: 1. februar 2013 10:45 > To: xen-users@lists.xensource.com > Subject: Re: [Xen-users] Intel HD 4000 VGA passthrough not working > > > > > For me it works fine in win7, if I use less the 3G of memory in the > > DomU and of course qemu-xen-traditional as device model. I have not > > tried winXP or Linux. It should be said that it will not work if you > > boot in EFI mode, since the VGA-bios is not available to the linux > > kernel. > > Thanks for your info. > > So it is a known issue to use more than 3G of memory? I seem to remember that another user mentioned problems with 4G of memory. I am not sure of the amount at which this problem is solved, but you could try with more than 3GB to check if it works. > > How do I make sure I'm not booting the EFI mode? I noticed > my bios has several settings about UEFI or legacy, and so I should set them all > to legacy? Is there any other things i should make sure? Which distro's do you use as dom0? Most distros will not use EFI as default, as far as I'm aware. For a command I cannot remember, but you could check which bootloader you have installed, the EFI versions are called something as grub-efi and elilo. Kind regards Kristian Hagsted Rasmussen _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Fri Feb 01 10:34:58 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 01 Feb 2013 10:34: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 1U1Dwh-0003ap-K8; Fri, 01 Feb 2013 10:34:11 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U1Dwg-0003ak-Dl for xen-users@lists.xensource.com; Fri, 01 Feb 2013 10:34:10 +0000 Received: from [193.109.254.147:56342] by server-8.bemta-14.messagelabs.com id 36/B6-17325-12A9B015; Fri, 01 Feb 2013 10:34:09 +0000 X-Env-Sender: kclo2000@gmail.com X-Msg-Ref: server-3.tower-27.messagelabs.com!1359714847!8868211!1 X-Originating-IP: [209.85.216.44] X-SpamReason: No, hits=2.3 required=7.0 tests=HTML_40_50,HTML_MESSAGE, INFO_TLD,ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 30931 invoked from network); 1 Feb 2013 10:34:08 -0000 Received: from mail-qa0-f44.google.com (HELO mail-qa0-f44.google.com) (209.85.216.44) by server-3.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 1 Feb 2013 10:34:08 -0000 Received: by mail-qa0-f44.google.com with SMTP id bv4so201326qab.3 for ; Fri, 01 Feb 2013 02:34:07 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:date:message-id:subject:from:to :content-type; bh=96Lc//RTlixg6V5XZXGhaGgvNscPk4JzfePEDwAiw1c=; b=beyj8uAV2zVNvLN0v+igab+bFaUdThYZMa0nYtaUkUh8800WiADY+xs0XI0HUJygcM qopxJaR0/3B+pD1CH2kIVBR4CsL02iVjwiO9f9N4QzCsyEkCf3/rFx8ulQaONULX/eKB 6RpUR4P7jg6vp3hsciwylXDncgWlDezXY6bgBZ7Hnn9lCt/6J/tuYn48JpQmEeJx7pAv 4CrZ2XvDn/G2UFKg4ZAqR4wXDUwrSLeWLm8mYSbyGtN+BqRBsbLkx04SVZHTYZGdi0sZ 4K4/FDm31mMUORDXD1h9CpUNDcCov/oYM0dLOBSCq7Y8M/RuO+pxjwkrS/gRseUWM52F 5fig== MIME-Version: 1.0 X-Received: by 10.229.115.30 with SMTP id g30mr3000170qcq.100.1359714847518; Fri, 01 Feb 2013 02:34:07 -0800 (PST) Received: by 10.49.83.199 with HTTP; Fri, 1 Feb 2013 02:34:07 -0800 (PST) Date: Fri, 1 Feb 2013 18:34:07 +0800 Message-ID: From: KC LO To: xen-users@lists.xensource.com Subject: [Xen-users] Unable to start VM guest 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="===============5198139577673336841==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============5198139577673336841== Content-Type: multipart/alternative; boundary=0023543338367b722604d4a748d9 --0023543338367b722604d4a748d9 Content-Type: text/plain; charset=ISO-8859-1 Hi all, I have create a PV image of CentOS under Xen 4.x version. When I start the VM guest, I can see the guest GRUB menu. When it continues to boot, it reports error prompt as Error : 'Serial'. >From /var/log/xen/xend.log, it shows File "usr/lib64/python2.6/site-packages/xen/xend/XendDomainInfo.py", line 3267, in ifHaveSerialPipe serial_devs_tmp = self.info['platform']['serial'] KeyError: 'serial' Any idea on it? Thanks! --0023543338367b722604d4a748d9 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Hi all,

I have create a PV image = of CentOS under Xen 4.x version. =A0When I start the VM guest, I can see th= e guest GRUB menu. =A0When it continues to boot, it reports error prompt as= Error : 'Serial'.


From /var/log/xen/xend= .log, it shows=A0

=A0 File "= usr/lib64/python2.6/site-packages/xen/xend/XendDomainInfo.py", line 32= 67, in ifHaveSerialPipe
=A0 =A0 serial_devs_tmp =3D self.info= ['platform']['serial']
KeyError: 'serial'=

Any idea on it?

<= div style> Thanks!
--0023543338367b722604d4a748d9-- --===============5198139577673336841== 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 --===============5198139577673336841==-- From xen-users-bounces@lists.xen.org Fri Feb 01 10:34:58 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 01 Feb 2013 10:34: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 1U1Dwh-0003ap-K8; Fri, 01 Feb 2013 10:34:11 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U1Dwg-0003ak-Dl for xen-users@lists.xensource.com; Fri, 01 Feb 2013 10:34:10 +0000 Received: from [193.109.254.147:56342] by server-8.bemta-14.messagelabs.com id 36/B6-17325-12A9B015; Fri, 01 Feb 2013 10:34:09 +0000 X-Env-Sender: kclo2000@gmail.com X-Msg-Ref: server-3.tower-27.messagelabs.com!1359714847!8868211!1 X-Originating-IP: [209.85.216.44] X-SpamReason: No, hits=2.3 required=7.0 tests=HTML_40_50,HTML_MESSAGE, INFO_TLD,ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 30931 invoked from network); 1 Feb 2013 10:34:08 -0000 Received: from mail-qa0-f44.google.com (HELO mail-qa0-f44.google.com) (209.85.216.44) by server-3.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 1 Feb 2013 10:34:08 -0000 Received: by mail-qa0-f44.google.com with SMTP id bv4so201326qab.3 for ; Fri, 01 Feb 2013 02:34:07 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:date:message-id:subject:from:to :content-type; bh=96Lc//RTlixg6V5XZXGhaGgvNscPk4JzfePEDwAiw1c=; b=beyj8uAV2zVNvLN0v+igab+bFaUdThYZMa0nYtaUkUh8800WiADY+xs0XI0HUJygcM qopxJaR0/3B+pD1CH2kIVBR4CsL02iVjwiO9f9N4QzCsyEkCf3/rFx8ulQaONULX/eKB 6RpUR4P7jg6vp3hsciwylXDncgWlDezXY6bgBZ7Hnn9lCt/6J/tuYn48JpQmEeJx7pAv 4CrZ2XvDn/G2UFKg4ZAqR4wXDUwrSLeWLm8mYSbyGtN+BqRBsbLkx04SVZHTYZGdi0sZ 4K4/FDm31mMUORDXD1h9CpUNDcCov/oYM0dLOBSCq7Y8M/RuO+pxjwkrS/gRseUWM52F 5fig== MIME-Version: 1.0 X-Received: by 10.229.115.30 with SMTP id g30mr3000170qcq.100.1359714847518; Fri, 01 Feb 2013 02:34:07 -0800 (PST) Received: by 10.49.83.199 with HTTP; Fri, 1 Feb 2013 02:34:07 -0800 (PST) Date: Fri, 1 Feb 2013 18:34:07 +0800 Message-ID: From: KC LO To: xen-users@lists.xensource.com Subject: [Xen-users] Unable to start VM guest 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="===============5198139577673336841==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============5198139577673336841== Content-Type: multipart/alternative; boundary=0023543338367b722604d4a748d9 --0023543338367b722604d4a748d9 Content-Type: text/plain; charset=ISO-8859-1 Hi all, I have create a PV image of CentOS under Xen 4.x version. When I start the VM guest, I can see the guest GRUB menu. When it continues to boot, it reports error prompt as Error : 'Serial'. >From /var/log/xen/xend.log, it shows File "usr/lib64/python2.6/site-packages/xen/xend/XendDomainInfo.py", line 3267, in ifHaveSerialPipe serial_devs_tmp = self.info['platform']['serial'] KeyError: 'serial' Any idea on it? Thanks! --0023543338367b722604d4a748d9 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Hi all,

I have create a PV image = of CentOS under Xen 4.x version. =A0When I start the VM guest, I can see th= e guest GRUB menu. =A0When it continues to boot, it reports error prompt as= Error : 'Serial'.


From /var/log/xen/xend= .log, it shows=A0

=A0 File "= usr/lib64/python2.6/site-packages/xen/xend/XendDomainInfo.py", line 32= 67, in ifHaveSerialPipe
=A0 =A0 serial_devs_tmp =3D self.info= ['platform']['serial']
KeyError: 'serial'=

Any idea on it?

<= div style> Thanks!
--0023543338367b722604d4a748d9-- --===============5198139577673336841== 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 --===============5198139577673336841==-- From xen-users-bounces@lists.xen.org Fri Feb 01 10:39:25 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 01 Feb 2013 10:39: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 1U1E17-0003oE-JJ; Fri, 01 Feb 2013 10:38:45 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U1E16-0003o5-12 for xen-users@lists.xensource.com; Fri, 01 Feb 2013 10:38:44 +0000 Received: from [85.158.139.83:53604] by server-3.bemta-5.messagelabs.com id 8D/4D-07037-33B9B015; Fri, 01 Feb 2013 10:38:43 +0000 X-Env-Sender: pigeon@pigeond.net X-Msg-Ref: server-3.tower-182.messagelabs.com!1359715120!30425762!1 X-Originating-IP: [203.59.1.219] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogMjAzLjU5LjEuMjE5ID0+IDE4MDEw\n X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 13372 invoked from network); 1 Feb 2013 10:38:42 -0000 Received: from icp-osb-irony-out3.external.iinet.net.au (HELO icp-osb-irony-out3.external.iinet.net.au) (203.59.1.219) by server-3.tower-182.messagelabs.com with SMTP; 1 Feb 2013 10:38:42 -0000 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AioMALuaC1F8lWUl/2dsb2JhbABFuRaGDxZzgh4BAQQBOkQLCw0UJQ9IBogeBcJTFZB3A5YThhOKPIMP X-IronPort-AV: E=Sophos;i="4.84,579,1355068800"; d="scan'208";a="93202147" Received: from unknown (HELO torankusu.pigeond.net) ([124.149.101.37]) by icp-osb-irony-out3.iinet.net.au with ESMTP; 01 Feb 2013 18:38:39 +0800 Received: from furiza.pigeond.net ([192.168.42.20]:46024 helo=furiza) by torankusu.pigeond.net with esmtp (Exim 4.72) (envelope-from ) id 1U1E10-0007My-KY for xen-users@lists.xensource.com; Fri, 01 Feb 2013 21:38:38 +1100 Date: Fri, 1 Feb 2013 21:38:37 +1100 From: Howell Tam To: "xen-users@lists.xensource.com" Message-ID: <20130201213837.30db4acf@furiza> In-Reply-To: <19EF9FEB5AF86243A3F18E5CE75971640C945789@hagsted-bserver.hagsted.dk> References: <20130201181930.262fa02b@furiza> <19EF9FEB5AF86243A3F18E5CE75971640C945735@hagsted-bserver.hagsted.dk> <20130201204507.45c74f94@furiza> <19EF9FEB5AF86243A3F18E5CE75971640C945789@hagsted-bserver.hagsted.dk> Organization: pigeond.net X-Mailer: Claws Mail 3.8.1 (GTK+ 2.24.13; x86_64-pc-linux-gnu) Mime-Version: 1.0 Subject: Re: [Xen-users] Intel HD 4000 VGA passthrough not working X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: 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 seem to remember that another user mentioned problems with 4G of > memory. I am not sure of the amount at which this problem is solved, > but you could try with more than 3GB to check if it works. I used to get this problem when the win7 hvm wouldn't even boot properly when i set the memory to more than 3600. But it turned out it was only when i was trying to do vga passthrough with an nvidia card with the nvidia patches to xen. I had tried using 8G of memory for a both win7 and linux hvm, with an ati card vga passthrough and they seem to work well. > Which distro's do you use as dom0? Most distros will not use EFI as > default, as far as I'm aware. For a command I cannot remember, but > you could check which bootloader you have installed, the EFI versions > are called something as grub-efi and elilo. Debian (testing). grub-efi is not installed, only grub-pc. I have also tried switching all the uefi settings in the bios to legacy, but it doesn't fix the intel hd4000 problem. Regards, Howell. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Fri Feb 01 10:39:25 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 01 Feb 2013 10:39: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 1U1E17-0003oE-JJ; Fri, 01 Feb 2013 10:38:45 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U1E16-0003o5-12 for xen-users@lists.xensource.com; Fri, 01 Feb 2013 10:38:44 +0000 Received: from [85.158.139.83:53604] by server-3.bemta-5.messagelabs.com id 8D/4D-07037-33B9B015; Fri, 01 Feb 2013 10:38:43 +0000 X-Env-Sender: pigeon@pigeond.net X-Msg-Ref: server-3.tower-182.messagelabs.com!1359715120!30425762!1 X-Originating-IP: [203.59.1.219] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogMjAzLjU5LjEuMjE5ID0+IDE4MDEw\n X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 13372 invoked from network); 1 Feb 2013 10:38:42 -0000 Received: from icp-osb-irony-out3.external.iinet.net.au (HELO icp-osb-irony-out3.external.iinet.net.au) (203.59.1.219) by server-3.tower-182.messagelabs.com with SMTP; 1 Feb 2013 10:38:42 -0000 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AioMALuaC1F8lWUl/2dsb2JhbABFuRaGDxZzgh4BAQQBOkQLCw0UJQ9IBogeBcJTFZB3A5YThhOKPIMP X-IronPort-AV: E=Sophos;i="4.84,579,1355068800"; d="scan'208";a="93202147" Received: from unknown (HELO torankusu.pigeond.net) ([124.149.101.37]) by icp-osb-irony-out3.iinet.net.au with ESMTP; 01 Feb 2013 18:38:39 +0800 Received: from furiza.pigeond.net ([192.168.42.20]:46024 helo=furiza) by torankusu.pigeond.net with esmtp (Exim 4.72) (envelope-from ) id 1U1E10-0007My-KY for xen-users@lists.xensource.com; Fri, 01 Feb 2013 21:38:38 +1100 Date: Fri, 1 Feb 2013 21:38:37 +1100 From: Howell Tam To: "xen-users@lists.xensource.com" Message-ID: <20130201213837.30db4acf@furiza> In-Reply-To: <19EF9FEB5AF86243A3F18E5CE75971640C945789@hagsted-bserver.hagsted.dk> References: <20130201181930.262fa02b@furiza> <19EF9FEB5AF86243A3F18E5CE75971640C945735@hagsted-bserver.hagsted.dk> <20130201204507.45c74f94@furiza> <19EF9FEB5AF86243A3F18E5CE75971640C945789@hagsted-bserver.hagsted.dk> Organization: pigeond.net X-Mailer: Claws Mail 3.8.1 (GTK+ 2.24.13; x86_64-pc-linux-gnu) Mime-Version: 1.0 Subject: Re: [Xen-users] Intel HD 4000 VGA passthrough not working X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: 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 seem to remember that another user mentioned problems with 4G of > memory. I am not sure of the amount at which this problem is solved, > but you could try with more than 3GB to check if it works. I used to get this problem when the win7 hvm wouldn't even boot properly when i set the memory to more than 3600. But it turned out it was only when i was trying to do vga passthrough with an nvidia card with the nvidia patches to xen. I had tried using 8G of memory for a both win7 and linux hvm, with an ati card vga passthrough and they seem to work well. > Which distro's do you use as dom0? Most distros will not use EFI as > default, as far as I'm aware. For a command I cannot remember, but > you could check which bootloader you have installed, the EFI versions > are called something as grub-efi and elilo. Debian (testing). grub-efi is not installed, only grub-pc. I have also tried switching all the uefi settings in the bios to legacy, but it doesn't fix the intel hd4000 problem. Regards, Howell. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Fri Feb 01 11:37:36 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 01 Feb 2013 11:37: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 1U1EvH-0007Om-7L; Fri, 01 Feb 2013 11:36:47 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U1EvF-0007Og-QH for xen-users@lists.xensource.com; Fri, 01 Feb 2013 11:36:45 +0000 Received: from [85.158.139.83:31832] by server-7.bemta-5.messagelabs.com id FF/B2-11121-CC8AB015; Fri, 01 Feb 2013 11:36:44 +0000 X-Env-Sender: pigeon@pigeond.net X-Msg-Ref: server-12.tower-182.messagelabs.com!1359718598!30396793!1 X-Originating-IP: [203.59.1.210] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogMjAzLjU5LjEuMjEwID0+IDE2ODkw\n X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 17433 invoked from network); 1 Feb 2013 11:36:40 -0000 Received: from icp-osb-irony-out1.external.iinet.net.au (HELO icp-osb-irony-out1.external.iinet.net.au) (203.59.1.210) by server-12.tower-182.messagelabs.com with SMTP; 1 Feb 2013 11:36:40 -0000 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: Av4EAOGmC1F8lWUl/2dsb2JhbABFvyUWc4IfAQU6TwsNFCUPSAaII8JakQwDlhOGE4o8gw8 X-IronPort-AV: E=Sophos;i="4.84,579,1355068800"; d="scan'208";a="83949754" Received: from unknown (HELO torankusu.pigeond.net) ([124.149.101.37]) by icp-osb-irony-out1.iinet.net.au with ESMTP; 01 Feb 2013 19:36:36 +0800 Received: from furiza.pigeond.net ([192.168.42.20]:46195 helo=pigeond.net) by torankusu.pigeond.net with esmtp (Exim 4.72) (envelope-from ) id 1U1Ev3-0007c1-Rz for xen-users@lists.xensource.com; Fri, 01 Feb 2013 22:36:34 +1100 Date: Fri, 1 Feb 2013 22:36:30 +1100 From: Howell Tam To: "xen-users@lists.xensource.com" Message-ID: <20130201223630.49944ca1@pigeond.net> In-Reply-To: <20130201213837.30db4acf@furiza> References: <20130201181930.262fa02b@furiza> <19EF9FEB5AF86243A3F18E5CE75971640C945735@hagsted-bserver.hagsted.dk> <20130201204507.45c74f94@furiza> <19EF9FEB5AF86243A3F18E5CE75971640C945789@hagsted-bserver.hagsted.dk> <20130201213837.30db4acf@furiza> Organization: pigeond.net X-Mailer: Claws Mail 3.8.1 (GTK+ 2.24.13; x86_64-pc-linux-gnu) Mime-Version: 1.0 Subject: Re: [Xen-users] Intel HD 4000 VGA passthrough not working X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: 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 have just done a test with a win7 hvm installation from scratch, with 2G of memory. It all works, until I install the Intel HD 4000 driver, and then reboot, then it won't boot anymore with the BSOD of SYSTEM_SERVICE_EXCEPTION. -- Regards, Howell. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Fri Feb 01 11:37:36 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 01 Feb 2013 11:37: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 1U1EvH-0007Om-7L; Fri, 01 Feb 2013 11:36:47 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U1EvF-0007Og-QH for xen-users@lists.xensource.com; Fri, 01 Feb 2013 11:36:45 +0000 Received: from [85.158.139.83:31832] by server-7.bemta-5.messagelabs.com id FF/B2-11121-CC8AB015; Fri, 01 Feb 2013 11:36:44 +0000 X-Env-Sender: pigeon@pigeond.net X-Msg-Ref: server-12.tower-182.messagelabs.com!1359718598!30396793!1 X-Originating-IP: [203.59.1.210] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogMjAzLjU5LjEuMjEwID0+IDE2ODkw\n X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 17433 invoked from network); 1 Feb 2013 11:36:40 -0000 Received: from icp-osb-irony-out1.external.iinet.net.au (HELO icp-osb-irony-out1.external.iinet.net.au) (203.59.1.210) by server-12.tower-182.messagelabs.com with SMTP; 1 Feb 2013 11:36:40 -0000 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: Av4EAOGmC1F8lWUl/2dsb2JhbABFvyUWc4IfAQU6TwsNFCUPSAaII8JakQwDlhOGE4o8gw8 X-IronPort-AV: E=Sophos;i="4.84,579,1355068800"; d="scan'208";a="83949754" Received: from unknown (HELO torankusu.pigeond.net) ([124.149.101.37]) by icp-osb-irony-out1.iinet.net.au with ESMTP; 01 Feb 2013 19:36:36 +0800 Received: from furiza.pigeond.net ([192.168.42.20]:46195 helo=pigeond.net) by torankusu.pigeond.net with esmtp (Exim 4.72) (envelope-from ) id 1U1Ev3-0007c1-Rz for xen-users@lists.xensource.com; Fri, 01 Feb 2013 22:36:34 +1100 Date: Fri, 1 Feb 2013 22:36:30 +1100 From: Howell Tam To: "xen-users@lists.xensource.com" Message-ID: <20130201223630.49944ca1@pigeond.net> In-Reply-To: <20130201213837.30db4acf@furiza> References: <20130201181930.262fa02b@furiza> <19EF9FEB5AF86243A3F18E5CE75971640C945735@hagsted-bserver.hagsted.dk> <20130201204507.45c74f94@furiza> <19EF9FEB5AF86243A3F18E5CE75971640C945789@hagsted-bserver.hagsted.dk> <20130201213837.30db4acf@furiza> Organization: pigeond.net X-Mailer: Claws Mail 3.8.1 (GTK+ 2.24.13; x86_64-pc-linux-gnu) Mime-Version: 1.0 Subject: Re: [Xen-users] Intel HD 4000 VGA passthrough not working X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: 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 have just done a test with a win7 hvm installation from scratch, with 2G of memory. It all works, until I install the Intel HD 4000 driver, and then reboot, then it won't boot anymore with the BSOD of SYSTEM_SERVICE_EXCEPTION. -- Regards, Howell. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Fri Feb 01 12:18:02 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 01 Feb 2013 12:18: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 1U1FYD-0000Hy-5k; Fri, 01 Feb 2013 12:17:01 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U1FYC-0000Ht-1O for xen-users@lists.xensource.com; Fri, 01 Feb 2013 12:17:00 +0000 Received: from [85.158.139.211:21083] by server-16.bemta-5.messagelabs.com id 01/B2-14948-B32BB015; Fri, 01 Feb 2013 12:16:59 +0000 X-Env-Sender: kristian@hagsted.dk X-Msg-Ref: server-14.tower-206.messagelabs.com!1359721017!20621662!1 X-Originating-IP: [80.160.77.98] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogODAuMTYwLjc3Ljk4ID0+IDE1MTEzNw==\n X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 17458 invoked from network); 1 Feb 2013 12:16:58 -0000 Received: from pasmtpb.tele.dk (HELO pasmtpB.tele.dk) (80.160.77.98) by server-14.tower-206.messagelabs.com with SMTP; 1 Feb 2013 12:16:58 -0000 Received: from hagsted.dk (2-108-99-186-static.dk.customer.tdc.net [2.108.99.186]) by pasmtpB.tele.dk (Postfix) with ESMTP id 10EBFD80DC; Fri, 1 Feb 2013 13:16:57 +0100 (CET) Received: from HAGSTED-BSERVER.hagsted.dk ([fe80::91b7:737e:e057:7c8b]) by hagsted-bserver.hagsted.dk ([fe80::91b7:737e:e057:7c8b%10]) with mapi id 14.02.0328.009; Fri, 1 Feb 2013 13:16:47 +0100 From: Kristian Hagsted Rasmussen To: Howell Tam , "xen-users@lists.xensource.com" Thread-Topic: [Xen-users] Intel HD 4000 VGA passthrough not working Thread-Index: AQHOAE56LrKyRr7TIEaq7EhZZ6rtE5hkqtUAgAAFbYCAABh9IP//9nWAgAAQLQCAABt/0A== Date: Fri, 1 Feb 2013 12:16:47 +0000 Message-ID: <19EF9FEB5AF86243A3F18E5CE75971640C9458A5@hagsted-bserver.hagsted.dk> References: <20130201181930.262fa02b@furiza> <19EF9FEB5AF86243A3F18E5CE75971640C945735@hagsted-bserver.hagsted.dk> <20130201204507.45c74f94@furiza> <19EF9FEB5AF86243A3F18E5CE75971640C945789@hagsted-bserver.hagsted.dk> <20130201213837.30db4acf@furiza> <20130201223630.49944ca1@pigeond.net> In-Reply-To: <20130201223630.49944ca1@pigeond.net> Accept-Language: da-DK, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [192.38.90.11] MIME-Version: 1.0 Subject: Re: [Xen-users] Intel HD 4000 VGA passthrough not working X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: 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: xen-users-bounces@lists.xen.org [mailto:xen-users- > bounces@lists.xen.org] On Behalf Of Howell Tam > Sent: 1. februar 2013 12:37 > To: xen-users@lists.xensource.com > Subject: Re: [Xen-users] Intel HD 4000 VGA passthrough not working > > > Hi all, > > I have just done a test with a win7 hvm installation from > scratch, with 2G of memory. > > It all works, until I install the Intel HD 4000 driver, and then > reboot, then it won't boot anymore with the BSOD of > SYSTEM_SERVICE_EXCEPTION. I now get in doubt if I have installed the intel driver, can check it when I get home. But a discussion on this subject is taking place at the xen-devel list, see her http://www.gossamer-threads.com/lists/xen/devel/265109 > > > -- > Regards, > Howell. > > > _______________________________________________ > 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 Feb 01 12:18:02 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 01 Feb 2013 12:18: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 1U1FYD-0000Hy-5k; Fri, 01 Feb 2013 12:17:01 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U1FYC-0000Ht-1O for xen-users@lists.xensource.com; Fri, 01 Feb 2013 12:17:00 +0000 Received: from [85.158.139.211:21083] by server-16.bemta-5.messagelabs.com id 01/B2-14948-B32BB015; Fri, 01 Feb 2013 12:16:59 +0000 X-Env-Sender: kristian@hagsted.dk X-Msg-Ref: server-14.tower-206.messagelabs.com!1359721017!20621662!1 X-Originating-IP: [80.160.77.98] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogODAuMTYwLjc3Ljk4ID0+IDE1MTEzNw==\n X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 17458 invoked from network); 1 Feb 2013 12:16:58 -0000 Received: from pasmtpb.tele.dk (HELO pasmtpB.tele.dk) (80.160.77.98) by server-14.tower-206.messagelabs.com with SMTP; 1 Feb 2013 12:16:58 -0000 Received: from hagsted.dk (2-108-99-186-static.dk.customer.tdc.net [2.108.99.186]) by pasmtpB.tele.dk (Postfix) with ESMTP id 10EBFD80DC; Fri, 1 Feb 2013 13:16:57 +0100 (CET) Received: from HAGSTED-BSERVER.hagsted.dk ([fe80::91b7:737e:e057:7c8b]) by hagsted-bserver.hagsted.dk ([fe80::91b7:737e:e057:7c8b%10]) with mapi id 14.02.0328.009; Fri, 1 Feb 2013 13:16:47 +0100 From: Kristian Hagsted Rasmussen To: Howell Tam , "xen-users@lists.xensource.com" Thread-Topic: [Xen-users] Intel HD 4000 VGA passthrough not working Thread-Index: AQHOAE56LrKyRr7TIEaq7EhZZ6rtE5hkqtUAgAAFbYCAABh9IP//9nWAgAAQLQCAABt/0A== Date: Fri, 1 Feb 2013 12:16:47 +0000 Message-ID: <19EF9FEB5AF86243A3F18E5CE75971640C9458A5@hagsted-bserver.hagsted.dk> References: <20130201181930.262fa02b@furiza> <19EF9FEB5AF86243A3F18E5CE75971640C945735@hagsted-bserver.hagsted.dk> <20130201204507.45c74f94@furiza> <19EF9FEB5AF86243A3F18E5CE75971640C945789@hagsted-bserver.hagsted.dk> <20130201213837.30db4acf@furiza> <20130201223630.49944ca1@pigeond.net> In-Reply-To: <20130201223630.49944ca1@pigeond.net> Accept-Language: da-DK, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [192.38.90.11] MIME-Version: 1.0 Subject: Re: [Xen-users] Intel HD 4000 VGA passthrough not working X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: 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: xen-users-bounces@lists.xen.org [mailto:xen-users- > bounces@lists.xen.org] On Behalf Of Howell Tam > Sent: 1. februar 2013 12:37 > To: xen-users@lists.xensource.com > Subject: Re: [Xen-users] Intel HD 4000 VGA passthrough not working > > > Hi all, > > I have just done a test with a win7 hvm installation from > scratch, with 2G of memory. > > It all works, until I install the Intel HD 4000 driver, and then > reboot, then it won't boot anymore with the BSOD of > SYSTEM_SERVICE_EXCEPTION. I now get in doubt if I have installed the intel driver, can check it when I get home. But a discussion on this subject is taking place at the xen-devel list, see her http://www.gossamer-threads.com/lists/xen/devel/265109 > > > -- > Regards, > Howell. > > > _______________________________________________ > 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 Feb 01 12:35:22 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 01 Feb 2013 12:35: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 1U1FpB-0000ld-5d; Fri, 01 Feb 2013 12:34:33 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U17yZ-00071o-OH for xen-users@lists.xen.org; Fri, 01 Feb 2013 04:11:43 +0000 Received: from [85.158.139.211:51413] by server-13.bemta-5.messagelabs.com id 9C/63-06769-E704B015; Fri, 01 Feb 2013 04:11:42 +0000 X-Env-Sender: linuxhack2012@gmail.com X-Msg-Ref: server-16.tower-206.messagelabs.com!1359691901!19479931!1 X-Originating-IP: [209.85.128.46] 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.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 27911 invoked from network); 1 Feb 2013 04:11:42 -0000 Received: from mail-qe0-f46.google.com (HELO mail-qe0-f46.google.com) (209.85.128.46) by server-16.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 1 Feb 2013 04:11:42 -0000 Received: by mail-qe0-f46.google.com with SMTP id 1so1658203qec.33 for ; Thu, 31 Jan 2013 20:11:41 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:date:message-id:subject:from:to :content-type; bh=xWZbuuM9MQerTsc7VcsJdrfBHAqdgbpJfhFFSy2zrb0=; b=OBSgOCrYP6XsKN1F0hTmcL9mJWlzw9GhAwZVjQu0nzChYPj4ArjiGOdekfzxaHJGpz eiMF8/IikMv3XUBHB6wN4U5lAmPBS1HQ+XrWUluYESZV7sWLwV/8btb4+GpxCxALLb1a YJdDKF7x4dpV5KIxGvoPQ39n2oqLZ0exgVYmC4mipbuZtyUGXDPiaeYrchPFOsYavLpy 2seCqxovejotKl91UrWO1QRFJUOrys+swlwzN6vuTUcdneEzyZ9e0J+s8pIlY+l132Cj WRBJlTh3Xn7cQmDpRo/Fts9Oy4nzQWwvQy8pX7W+KKDa517PhXm6N7BIBJGkROtv7fqI B/Yw== MIME-Version: 1.0 X-Received: by 10.224.182.70 with SMTP id cb6mr11210977qab.80.1359691901148; Thu, 31 Jan 2013 20:11:41 -0800 (PST) Received: by 10.49.52.66 with HTTP; Thu, 31 Jan 2013 20:11:41 -0800 (PST) Date: Fri, 1 Feb 2013 09:41:41 +0530 Message-ID: From: Linux Hack To: xen-users@lists.xen.org X-Mailman-Approved-At: Fri, 01 Feb 2013 12:34:30 +0000 Subject: [Xen-users] Troubleshooting Xen HVM boot issues X-BeenThere: xen-users@lists.xen.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="===============1322374575367751579==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============1322374575367751579== Content-Type: multipart/alternative; boundary=20cf303b4183c59d5b04d4a1f054 --20cf303b4183c59d5b04d4a1f054 Content-Type: text/plain; charset=ISO-8859-1 Hi, For Xen PV we can boot xm create -c /etc/xen/domu.cfg which entered into console immediately which is useful for us to troubleshooting the booting issue. Is there any such options available for Xen HVM too? --20cf303b4183c59d5b04d4a1f054 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Hi,

For Xen PV we can boot xm cre= ate -c /etc/xen/domu.cfg which entered into console immediately which is us= eful for us to troubleshooting the booting issue.

Is there any such options=A0available=A0for Xen HVM too?

--20cf303b4183c59d5b04d4a1f054-- --===============1322374575367751579== 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 --===============1322374575367751579==-- From xen-users-bounces@lists.xen.org Fri Feb 01 12:35:22 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 01 Feb 2013 12:35: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 1U1FpB-0000ld-5d; Fri, 01 Feb 2013 12:34:33 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U17yZ-00071o-OH for xen-users@lists.xen.org; Fri, 01 Feb 2013 04:11:43 +0000 Received: from [85.158.139.211:51413] by server-13.bemta-5.messagelabs.com id 9C/63-06769-E704B015; Fri, 01 Feb 2013 04:11:42 +0000 X-Env-Sender: linuxhack2012@gmail.com X-Msg-Ref: server-16.tower-206.messagelabs.com!1359691901!19479931!1 X-Originating-IP: [209.85.128.46] 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.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 27911 invoked from network); 1 Feb 2013 04:11:42 -0000 Received: from mail-qe0-f46.google.com (HELO mail-qe0-f46.google.com) (209.85.128.46) by server-16.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 1 Feb 2013 04:11:42 -0000 Received: by mail-qe0-f46.google.com with SMTP id 1so1658203qec.33 for ; Thu, 31 Jan 2013 20:11:41 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:date:message-id:subject:from:to :content-type; bh=xWZbuuM9MQerTsc7VcsJdrfBHAqdgbpJfhFFSy2zrb0=; b=OBSgOCrYP6XsKN1F0hTmcL9mJWlzw9GhAwZVjQu0nzChYPj4ArjiGOdekfzxaHJGpz eiMF8/IikMv3XUBHB6wN4U5lAmPBS1HQ+XrWUluYESZV7sWLwV/8btb4+GpxCxALLb1a YJdDKF7x4dpV5KIxGvoPQ39n2oqLZ0exgVYmC4mipbuZtyUGXDPiaeYrchPFOsYavLpy 2seCqxovejotKl91UrWO1QRFJUOrys+swlwzN6vuTUcdneEzyZ9e0J+s8pIlY+l132Cj WRBJlTh3Xn7cQmDpRo/Fts9Oy4nzQWwvQy8pX7W+KKDa517PhXm6N7BIBJGkROtv7fqI B/Yw== MIME-Version: 1.0 X-Received: by 10.224.182.70 with SMTP id cb6mr11210977qab.80.1359691901148; Thu, 31 Jan 2013 20:11:41 -0800 (PST) Received: by 10.49.52.66 with HTTP; Thu, 31 Jan 2013 20:11:41 -0800 (PST) Date: Fri, 1 Feb 2013 09:41:41 +0530 Message-ID: From: Linux Hack To: xen-users@lists.xen.org X-Mailman-Approved-At: Fri, 01 Feb 2013 12:34:30 +0000 Subject: [Xen-users] Troubleshooting Xen HVM boot issues X-BeenThere: xen-users@lists.xen.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="===============1322374575367751579==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============1322374575367751579== Content-Type: multipart/alternative; boundary=20cf303b4183c59d5b04d4a1f054 --20cf303b4183c59d5b04d4a1f054 Content-Type: text/plain; charset=ISO-8859-1 Hi, For Xen PV we can boot xm create -c /etc/xen/domu.cfg which entered into console immediately which is useful for us to troubleshooting the booting issue. Is there any such options available for Xen HVM too? --20cf303b4183c59d5b04d4a1f054 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Hi,

For Xen PV we can boot xm cre= ate -c /etc/xen/domu.cfg which entered into console immediately which is us= eful for us to troubleshooting the booting issue.

Is there any such options=A0available=A0for Xen HVM too?

--20cf303b4183c59d5b04d4a1f054-- --===============1322374575367751579== 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 --===============1322374575367751579==-- From xen-users-bounces@lists.xen.org Fri Feb 01 12:35:25 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 01 Feb 2013 12:35: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 1U1FpA-0000lT-It; Fri, 01 Feb 2013 12:34:32 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U17lh-0006wF-P2 for xen-users@lists.xen.org; Fri, 01 Feb 2013 03:58:26 +0000 Received: from [85.158.139.83:19827] by server-12.bemta-5.messagelabs.com id B3/0E-20195-06D3B015; Fri, 01 Feb 2013 03:58:24 +0000 X-Env-Sender: linuxhack2012@gmail.com X-Msg-Ref: server-2.tower-182.messagelabs.com!1359691102!29927275!1 X-Originating-IP: [209.85.216.182] X-SpamReason: No, hits=2.5 required=7.0 tests=HTML_40_50,HTML_MESSAGE, HTML_SHORT_LENGTH,ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 9567 invoked from network); 1 Feb 2013 03:58:24 -0000 Received: from mail-qc0-f182.google.com (HELO mail-qc0-f182.google.com) (209.85.216.182) by server-2.tower-182.messagelabs.com with RC4-SHA encrypted SMTP; 1 Feb 2013 03:58:24 -0000 Received: by mail-qc0-f182.google.com with SMTP id k19so1607261qcs.27 for ; Thu, 31 Jan 2013 19:58:22 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:date:message-id:subject:from:to :content-type; bh=hodGtmSUKscelu6BQBmWc/xSFoj8aizL0ht+i64TnsA=; b=xed4h7mnAieR58mONRaljF5JUWqY5arKKWTVVyLJb9FLkhP7lW+RRjm7e2EkpIJY6I kAfqDuHShY66diTDFAuy3FPCDVF84yYmhkB8iE70M+aP9Po4FK7A1b3I6HPE5LBdhz9c aRPCrv9c2ZvwmkZXpw3VXkEyG7zeEMD+LbjC7OHX2sNTpfUwgpa4OxiD+4CFO52L3W3p jh6FERKSoRCxa93QfdXQWkpdsNoAWiFXXJ2cvsEErgsFIjSlL9Y+djpfWPq3Kg7x4erZ OAQYt3M1Yi6AvMpReBa8O4CRYFCmGujTlLOgWmx3LIin3epG/RbWATBpgcwJLoTuFrOW DNJg== MIME-Version: 1.0 X-Received: by 10.224.27.77 with SMTP id h13mr11356019qac.23.1359691102483; Thu, 31 Jan 2013 19:58:22 -0800 (PST) Received: by 10.49.52.66 with HTTP; Thu, 31 Jan 2013 19:58:22 -0800 (PST) Date: Fri, 1 Feb 2013 09:28:22 +0530 Message-ID: From: Linux Hack To: xen-users@lists.xen.org X-Mailman-Approved-At: Fri, 01 Feb 2013 12:34:30 +0000 Subject: [Xen-users] Regarding sched-credit weight and caps X-BeenThere: xen-users@lists.xen.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="===============7956310672857052916==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============7956310672857052916== Content-Type: multipart/alternative; boundary=bcaec51b9fd32af5f604d4a1c1fd --bcaec51b9fd32af5f604d4a1c1fd Content-Type: text/plain; charset=ISO-8859-1 Hi, Is there any specific good weight and cap value for Dom-0 which keep more stable the Dom-0? --bcaec51b9fd32af5f604d4a1c1fd Content-Type: text/html; charset=ISO-8859-1
Hi,

Is there any specific good weight and cap value for Dom-0 which keep more stable the Dom-0?

--bcaec51b9fd32af5f604d4a1c1fd-- --===============7956310672857052916== 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 --===============7956310672857052916==-- From xen-users-bounces@lists.xen.org Fri Feb 01 12:35:25 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 01 Feb 2013 12:35: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 1U1FpA-0000lT-It; Fri, 01 Feb 2013 12:34:32 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U17lh-0006wF-P2 for xen-users@lists.xen.org; Fri, 01 Feb 2013 03:58:26 +0000 Received: from [85.158.139.83:19827] by server-12.bemta-5.messagelabs.com id B3/0E-20195-06D3B015; Fri, 01 Feb 2013 03:58:24 +0000 X-Env-Sender: linuxhack2012@gmail.com X-Msg-Ref: server-2.tower-182.messagelabs.com!1359691102!29927275!1 X-Originating-IP: [209.85.216.182] X-SpamReason: No, hits=2.5 required=7.0 tests=HTML_40_50,HTML_MESSAGE, HTML_SHORT_LENGTH,ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 9567 invoked from network); 1 Feb 2013 03:58:24 -0000 Received: from mail-qc0-f182.google.com (HELO mail-qc0-f182.google.com) (209.85.216.182) by server-2.tower-182.messagelabs.com with RC4-SHA encrypted SMTP; 1 Feb 2013 03:58:24 -0000 Received: by mail-qc0-f182.google.com with SMTP id k19so1607261qcs.27 for ; Thu, 31 Jan 2013 19:58:22 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:date:message-id:subject:from:to :content-type; bh=hodGtmSUKscelu6BQBmWc/xSFoj8aizL0ht+i64TnsA=; b=xed4h7mnAieR58mONRaljF5JUWqY5arKKWTVVyLJb9FLkhP7lW+RRjm7e2EkpIJY6I kAfqDuHShY66diTDFAuy3FPCDVF84yYmhkB8iE70M+aP9Po4FK7A1b3I6HPE5LBdhz9c aRPCrv9c2ZvwmkZXpw3VXkEyG7zeEMD+LbjC7OHX2sNTpfUwgpa4OxiD+4CFO52L3W3p jh6FERKSoRCxa93QfdXQWkpdsNoAWiFXXJ2cvsEErgsFIjSlL9Y+djpfWPq3Kg7x4erZ OAQYt3M1Yi6AvMpReBa8O4CRYFCmGujTlLOgWmx3LIin3epG/RbWATBpgcwJLoTuFrOW DNJg== MIME-Version: 1.0 X-Received: by 10.224.27.77 with SMTP id h13mr11356019qac.23.1359691102483; Thu, 31 Jan 2013 19:58:22 -0800 (PST) Received: by 10.49.52.66 with HTTP; Thu, 31 Jan 2013 19:58:22 -0800 (PST) Date: Fri, 1 Feb 2013 09:28:22 +0530 Message-ID: From: Linux Hack To: xen-users@lists.xen.org X-Mailman-Approved-At: Fri, 01 Feb 2013 12:34:30 +0000 Subject: [Xen-users] Regarding sched-credit weight and caps X-BeenThere: xen-users@lists.xen.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="===============7956310672857052916==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============7956310672857052916== Content-Type: multipart/alternative; boundary=bcaec51b9fd32af5f604d4a1c1fd --bcaec51b9fd32af5f604d4a1c1fd Content-Type: text/plain; charset=ISO-8859-1 Hi, Is there any specific good weight and cap value for Dom-0 which keep more stable the Dom-0? --bcaec51b9fd32af5f604d4a1c1fd Content-Type: text/html; charset=ISO-8859-1
Hi,

Is there any specific good weight and cap value for Dom-0 which keep more stable the Dom-0?

--bcaec51b9fd32af5f604d4a1c1fd-- --===============7956310672857052916== 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 --===============7956310672857052916==-- From xen-users-bounces@lists.xen.org Fri Feb 01 13:03:13 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 01 Feb 2013 13:03: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 1U1GG9-0001z8-Sy; Fri, 01 Feb 2013 13:02:25 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U1GG8-0001z3-SY for xen-users@lists.xen.org; Fri, 01 Feb 2013 13:02:25 +0000 Received: from [85.158.138.51:30331] by server-3.bemta-3.messagelabs.com id 35/8A-31070-0ECBB015; Fri, 01 Feb 2013 13:02:24 +0000 X-Env-Sender: dietmar.hahn@ts.fujitsu.com X-Msg-Ref: server-15.tower-174.messagelabs.com!1359723743!28797976!1 X-Originating-IP: [80.70.172.51] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogODAuNzAuMTcyLjUxID0+IDE5NzY4Nw==\n X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 13292 invoked from network); 1 Feb 2013 13:02:23 -0000 Received: from dgate20.ts.fujitsu.com (HELO dgate20.ts.fujitsu.com) (80.70.172.51) by server-15.tower-174.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 1 Feb 2013 13:02:23 -0000 DomainKey-Signature: s=s1536a; d=ts.fujitsu.com; c=nofws; q=dns; h=X-SBRSScore:X-IronPort-AV:Received:X-IronPort-AV: Received:Received:From:To:Cc:Subject:Date:Message-ID: User-Agent:In-Reply-To:References:MIME-Version: Content-Transfer-Encoding:Content-Type; b=opVeDqq11NLkUB7WIds58NBg0orJrCgY1Uhd+pE5xQShV0EkuE/+8OFg kWDGxrUudkZXYMVlPUElPO13aVDmvezK3LYDTOmmFb4YhTje0Ojc/qVAP pvoqZ4OADG85oe5ZvfILshvHc3UUKXKFO7Y4yFY4+uPxC+j5iMmXa+90C RQmR7tTWmGK6KZbVv7LEQXnqyNQdEcMWrFPEr1zjxeQ66RPKKbHJwOlkZ cvujt6eDgFUGoVestACDoe0UsbscS; DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=ts.fujitsu.com; i=@ts.fujitsu.com; q=dns/txt; s=s1536b; t=1359723743; x=1391259743; h=from:to:cc:subject:date:message-id:in-reply-to: references:mime-version:content-transfer-encoding; bh=G+Ni+sC1hMquQLH31sbBB9bQZyZBQRM1LccONO2McYM=; b=FdYks7A5/3nHS1W2RjeSJT12fUoX7U7dSs0+cAeIQRGtzbFOxhpqrPlc 7r1Ajs5BUUjg182fHIaA7JCwexLkieiqeP8FXA225y55Fy83fesEMYo9P gWfaMNUl2xwuCJXKYXShckU/v0HActgo34Ws8p9HGqmj0kYrAnMqb8GX7 KExV+iewpFLiLI2aFazdKFZQ3mVqiW6pfgT4KZVnDril+xqaWczhJbhLU 7pSJuDnQZ7LiNWSGzHyyEtQbihFEa; X-SBRSScore: None X-IronPort-AV: E=Sophos;i="4.84,579,1355094000"; d="scan'208";a="114884663" Received: from abgdgate40u.abg.fsc.net ([172.25.138.90]) by dgate20u.abg.fsc.net with ESMTP; 01 Feb 2013 14:02:23 +0100 X-IronPort-AV: E=Sophos;i="4.84,579,1355094000"; d="scan'208";a="158056151" Received: from sanpedro.mch.fsc.net ([172.17.20.6]) by abgdgate40u.abg.fsc.net with SMTP; 01 Feb 2013 14:02:22 +0100 Received: from amur.localnet (amur.mch.fsc.net [10.172.102.75]) by sanpedro.mch.fsc.net (Postfix) with ESMTP id CBACC97115F; Fri, 1 Feb 2013 14:02:22 +0100 (CET) From: Dietmar Hahn To: xen-users@lists.xen.org Date: Fri, 01 Feb 2013 14:02:22 +0100 Message-ID: <4618803.UXl2YtJGu7@amur> User-Agent: KMail/4.8.5 (Linux/3.4.11-2.16-xen; KDE/4.8.5; x86_64; ; ) In-Reply-To: References: MIME-Version: 1.0 Cc: Linux Hack Subject: Re: [Xen-users] Troubleshooting Xen HVM boot issues X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org Am Freitag 01 Februar 2013, 09:41:41 schrieb Linux Hack: > Hi, > > For Xen PV we can boot xm create -c /etc/xen/domu.cfg which entered into > console immediately which is useful for us to troubleshooting the booting > issue. > > Is there any such options available for Xen HVM too? You have to configure a console in your /etc/xen/domu.cfg. See 'sdl' or 'vnc' in /etc/xen/examples/xmexample* Or after creating the HVM domU you can use 'xm console ...' to connect to the console. Dietmar. -- Company details: http://ts.fujitsu.com/imprint.html _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Fri Feb 01 13:03:13 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 01 Feb 2013 13:03: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 1U1GG9-0001z8-Sy; Fri, 01 Feb 2013 13:02:25 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U1GG8-0001z3-SY for xen-users@lists.xen.org; Fri, 01 Feb 2013 13:02:25 +0000 Received: from [85.158.138.51:30331] by server-3.bemta-3.messagelabs.com id 35/8A-31070-0ECBB015; Fri, 01 Feb 2013 13:02:24 +0000 X-Env-Sender: dietmar.hahn@ts.fujitsu.com X-Msg-Ref: server-15.tower-174.messagelabs.com!1359723743!28797976!1 X-Originating-IP: [80.70.172.51] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogODAuNzAuMTcyLjUxID0+IDE5NzY4Nw==\n X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 13292 invoked from network); 1 Feb 2013 13:02:23 -0000 Received: from dgate20.ts.fujitsu.com (HELO dgate20.ts.fujitsu.com) (80.70.172.51) by server-15.tower-174.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 1 Feb 2013 13:02:23 -0000 DomainKey-Signature: s=s1536a; d=ts.fujitsu.com; c=nofws; q=dns; h=X-SBRSScore:X-IronPort-AV:Received:X-IronPort-AV: Received:Received:From:To:Cc:Subject:Date:Message-ID: User-Agent:In-Reply-To:References:MIME-Version: Content-Transfer-Encoding:Content-Type; b=opVeDqq11NLkUB7WIds58NBg0orJrCgY1Uhd+pE5xQShV0EkuE/+8OFg kWDGxrUudkZXYMVlPUElPO13aVDmvezK3LYDTOmmFb4YhTje0Ojc/qVAP pvoqZ4OADG85oe5ZvfILshvHc3UUKXKFO7Y4yFY4+uPxC+j5iMmXa+90C RQmR7tTWmGK6KZbVv7LEQXnqyNQdEcMWrFPEr1zjxeQ66RPKKbHJwOlkZ cvujt6eDgFUGoVestACDoe0UsbscS; DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=ts.fujitsu.com; i=@ts.fujitsu.com; q=dns/txt; s=s1536b; t=1359723743; x=1391259743; h=from:to:cc:subject:date:message-id:in-reply-to: references:mime-version:content-transfer-encoding; bh=G+Ni+sC1hMquQLH31sbBB9bQZyZBQRM1LccONO2McYM=; b=FdYks7A5/3nHS1W2RjeSJT12fUoX7U7dSs0+cAeIQRGtzbFOxhpqrPlc 7r1Ajs5BUUjg182fHIaA7JCwexLkieiqeP8FXA225y55Fy83fesEMYo9P gWfaMNUl2xwuCJXKYXShckU/v0HActgo34Ws8p9HGqmj0kYrAnMqb8GX7 KExV+iewpFLiLI2aFazdKFZQ3mVqiW6pfgT4KZVnDril+xqaWczhJbhLU 7pSJuDnQZ7LiNWSGzHyyEtQbihFEa; X-SBRSScore: None X-IronPort-AV: E=Sophos;i="4.84,579,1355094000"; d="scan'208";a="114884663" Received: from abgdgate40u.abg.fsc.net ([172.25.138.90]) by dgate20u.abg.fsc.net with ESMTP; 01 Feb 2013 14:02:23 +0100 X-IronPort-AV: E=Sophos;i="4.84,579,1355094000"; d="scan'208";a="158056151" Received: from sanpedro.mch.fsc.net ([172.17.20.6]) by abgdgate40u.abg.fsc.net with SMTP; 01 Feb 2013 14:02:22 +0100 Received: from amur.localnet (amur.mch.fsc.net [10.172.102.75]) by sanpedro.mch.fsc.net (Postfix) with ESMTP id CBACC97115F; Fri, 1 Feb 2013 14:02:22 +0100 (CET) From: Dietmar Hahn To: xen-users@lists.xen.org Date: Fri, 01 Feb 2013 14:02:22 +0100 Message-ID: <4618803.UXl2YtJGu7@amur> User-Agent: KMail/4.8.5 (Linux/3.4.11-2.16-xen; KDE/4.8.5; x86_64; ; ) In-Reply-To: References: MIME-Version: 1.0 Cc: Linux Hack Subject: Re: [Xen-users] Troubleshooting Xen HVM boot issues X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org Am Freitag 01 Februar 2013, 09:41:41 schrieb Linux Hack: > Hi, > > For Xen PV we can boot xm create -c /etc/xen/domu.cfg which entered into > console immediately which is useful for us to troubleshooting the booting > issue. > > Is there any such options available for Xen HVM too? You have to configure a console in your /etc/xen/domu.cfg. See 'sdl' or 'vnc' in /etc/xen/examples/xmexample* Or after creating the HVM domU you can use 'xm console ...' to connect to the console. Dietmar. -- Company details: http://ts.fujitsu.com/imprint.html _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Fri Feb 01 14:19:50 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 01 Feb 2013 14:19: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 1U1HS8-0003LN-43; Fri, 01 Feb 2013 14:18:52 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U1HS5-0003L8-RO for xen-users@lists.xen.org; Fri, 01 Feb 2013 14:18:49 +0000 Received: from [85.158.138.51:7636] by server-1.bemta-3.messagelabs.com id B3/8A-08955-9CECB015; Fri, 01 Feb 2013 14:18:49 +0000 X-Env-Sender: digvijaych@gmail.com X-Msg-Ref: server-2.tower-174.messagelabs.com!1359728298!28828017!1 X-Originating-IP: [209.85.217.177] 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.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 29601 invoked from network); 1 Feb 2013 14:18:19 -0000 Received: from mail-lb0-f177.google.com (HELO mail-lb0-f177.google.com) (209.85.217.177) by server-2.tower-174.messagelabs.com with RC4-SHA encrypted SMTP; 1 Feb 2013 14:18:19 -0000 Received: by mail-lb0-f177.google.com with SMTP id go11so4505840lbb.8 for ; Fri, 01 Feb 2013 06:18:18 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:date:message-id:subject:from:to :content-type; bh=HFCfntkWU35LWM/dwQ+jVlkLCkoWt+9st+5iAYXQvkQ=; b=QFpAQR8Xu8EpkMkFcTvGqYGDIGZ8Lw3fblbJpYeVDGMH6tdQj6+N1QOvpdMP1hL6bJ TG8uCNEaPFLHzIGg2UlsdJuNpf4bKqNyqkKeQRALrtYRgbPrzNVJebXcvZYFqGRFl4mj ujLCUDjlTPMfTTFAl7EwdzfY/Uyx5S1pQE4TcerzBBoR+xS7nsbUqukjOmpJEKK8J3aY 0DJPfAbka+4SUC/6ftWv0oOSwsv07R/wszxjP7bRTH3ZKyJWaTUNsBX4Pt0T57/4/TyO oYdWzar3lTkc6s7J/7k4sfgTKeaVRsUfiMhMy1QVXbqXJLYmWXwHb/xTLlVqS2e66Vfo KZog== MIME-Version: 1.0 X-Received: by 10.112.47.168 with SMTP id e8mr4853989lbn.46.1359728298551; Fri, 01 Feb 2013 06:18:18 -0800 (PST) Received: by 10.112.79.37 with HTTP; Fri, 1 Feb 2013 06:18:18 -0800 (PST) Date: Fri, 1 Feb 2013 19:48:18 +0530 Message-ID: From: digvijay chauhan To: xen-users@lists.xen.org, xen-devel@lists.xensource.com Subject: [Xen-users] how to use sctp during live migration of vm with 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="===============8852790117604236288==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============8852790117604236288== Content-Type: multipart/alternative; boundary=bcaec553fde039e9bd04d4aa6a02 --bcaec553fde039e9bd04d4aa6a02 Content-Type: text/plain; charset=ISO-8859-1 Hello, I want to carry out the performance analysis of transport protocol i.e sctp so how can we achieve it.Instead of using tcp if we have to use sctp how to do that? regards, DigvijaySingh --bcaec553fde039e9bd04d4aa6a02 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Hello,
=A0=A0=A0=A0=A0=A0=A0=A0 I want to carry out the performance ana= lysis of transport protocol i.e sctp so how can we achieve it.Instead of us= ing tcp if we have to use sctp how to do that?



regards,
D= igvijaySingh
--bcaec553fde039e9bd04d4aa6a02-- --===============8852790117604236288== 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 --===============8852790117604236288==-- From xen-users-bounces@lists.xen.org Fri Feb 01 14:19:50 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 01 Feb 2013 14:19: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 1U1HS8-0003LN-43; Fri, 01 Feb 2013 14:18:52 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U1HS5-0003L8-RO for xen-users@lists.xen.org; Fri, 01 Feb 2013 14:18:49 +0000 Received: from [85.158.138.51:7636] by server-1.bemta-3.messagelabs.com id B3/8A-08955-9CECB015; Fri, 01 Feb 2013 14:18:49 +0000 X-Env-Sender: digvijaych@gmail.com X-Msg-Ref: server-2.tower-174.messagelabs.com!1359728298!28828017!1 X-Originating-IP: [209.85.217.177] 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.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 29601 invoked from network); 1 Feb 2013 14:18:19 -0000 Received: from mail-lb0-f177.google.com (HELO mail-lb0-f177.google.com) (209.85.217.177) by server-2.tower-174.messagelabs.com with RC4-SHA encrypted SMTP; 1 Feb 2013 14:18:19 -0000 Received: by mail-lb0-f177.google.com with SMTP id go11so4505840lbb.8 for ; Fri, 01 Feb 2013 06:18:18 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:date:message-id:subject:from:to :content-type; bh=HFCfntkWU35LWM/dwQ+jVlkLCkoWt+9st+5iAYXQvkQ=; b=QFpAQR8Xu8EpkMkFcTvGqYGDIGZ8Lw3fblbJpYeVDGMH6tdQj6+N1QOvpdMP1hL6bJ TG8uCNEaPFLHzIGg2UlsdJuNpf4bKqNyqkKeQRALrtYRgbPrzNVJebXcvZYFqGRFl4mj ujLCUDjlTPMfTTFAl7EwdzfY/Uyx5S1pQE4TcerzBBoR+xS7nsbUqukjOmpJEKK8J3aY 0DJPfAbka+4SUC/6ftWv0oOSwsv07R/wszxjP7bRTH3ZKyJWaTUNsBX4Pt0T57/4/TyO oYdWzar3lTkc6s7J/7k4sfgTKeaVRsUfiMhMy1QVXbqXJLYmWXwHb/xTLlVqS2e66Vfo KZog== MIME-Version: 1.0 X-Received: by 10.112.47.168 with SMTP id e8mr4853989lbn.46.1359728298551; Fri, 01 Feb 2013 06:18:18 -0800 (PST) Received: by 10.112.79.37 with HTTP; Fri, 1 Feb 2013 06:18:18 -0800 (PST) Date: Fri, 1 Feb 2013 19:48:18 +0530 Message-ID: From: digvijay chauhan To: xen-users@lists.xen.org, xen-devel@lists.xensource.com Subject: [Xen-users] how to use sctp during live migration of vm with 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="===============8852790117604236288==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============8852790117604236288== Content-Type: multipart/alternative; boundary=bcaec553fde039e9bd04d4aa6a02 --bcaec553fde039e9bd04d4aa6a02 Content-Type: text/plain; charset=ISO-8859-1 Hello, I want to carry out the performance analysis of transport protocol i.e sctp so how can we achieve it.Instead of using tcp if we have to use sctp how to do that? regards, DigvijaySingh --bcaec553fde039e9bd04d4aa6a02 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Hello,
=A0=A0=A0=A0=A0=A0=A0=A0 I want to carry out the performance ana= lysis of transport protocol i.e sctp so how can we achieve it.Instead of us= ing tcp if we have to use sctp how to do that?



regards,
D= igvijaySingh
--bcaec553fde039e9bd04d4aa6a02-- --===============8852790117604236288== 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 --===============8852790117604236288==-- From xen-users-bounces@lists.xen.org Fri Feb 01 14:47:50 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 01 Feb 2013 14:47: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 1U1HtE-0004nz-Io; Fri, 01 Feb 2013 14:46:52 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U1HtC-0004na-F0 for xen-users@lists.xen.org; Fri, 01 Feb 2013 14:46:50 +0000 Received: from [85.158.138.51:33433] by server-11.bemta-3.messagelabs.com id 60/2D-10249-955DB015; Fri, 01 Feb 2013 14:46:49 +0000 X-Env-Sender: wei.liu2@citrix.com X-Msg-Ref: server-8.tower-174.messagelabs.com!1359730007!28824148!1 X-Originating-IP: [66.165.176.63] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjYuMTY1LjE3Ni42MyA9PiAzMDA5NDY=\n X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 6750 invoked from network); 1 Feb 2013 14:46:49 -0000 Received: from smtp02.citrix.com (HELO SMTP02.CITRIX.COM) (66.165.176.63) by server-8.tower-174.messagelabs.com with RC4-SHA encrypted SMTP; 1 Feb 2013 14:46:49 -0000 X-IronPort-AV: E=Sophos;i="4.84,579,1355097600"; d="scan'208";a="5665255" Received: from accessns.citrite.net (HELO FTLPEX01CL01.citrite.net) ([10.9.154.239]) by FTLPIPO02.CITRIX.COM with ESMTP/TLS/AES128-SHA; 01 Feb 2013 14:46:47 +0000 Received: from ukmail1.uk.xensource.com (10.80.16.128) by smtprelay.citrix.com (10.13.107.78) with Microsoft SMTP Server id 14.2.318.1; Fri, 1 Feb 2013 09:46:46 -0500 Received: from zion.uk.xensource.com ([10.80.2.73]) by ukmail1.uk.xensource.com with esmtp (Exim 4.69) (envelope-from ) id 1U1Ht8-0002Ws-Hl; Fri, 01 Feb 2013 14:46:46 +0000 Message-ID: <1359730006.23229.118.camel@zion.uk.xensource.com> From: Wei Liu To: Linux Hack Date: Fri, 1 Feb 2013 14:46:46 +0000 In-Reply-To: References: X-Mailer: Evolution 3.6.2 (3.6.2-3.fc18) MIME-Version: 1.0 Cc: "xen-users@lists.xen.org" , wei.liu2@citrix.com Subject: Re: [Xen-users] Troubleshooting Xen HVM boot issues X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: 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, 2013-02-01 at 04:11 +0000, Linux Hack wrote: > Hi, > > > For Xen PV we can boot xm create -c /etc/xen/domu.cfg which entered > into console immediately which is useful for us to troubleshooting the > booting issue. > You can configure serial console for HVM as well - if that helps you troubleshoot your issues. Wei. > > Is there any such options available for Xen HVM too? > > _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Fri Feb 01 14:47:50 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 01 Feb 2013 14:47: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 1U1HtE-0004nz-Io; Fri, 01 Feb 2013 14:46:52 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U1HtC-0004na-F0 for xen-users@lists.xen.org; Fri, 01 Feb 2013 14:46:50 +0000 Received: from [85.158.138.51:33433] by server-11.bemta-3.messagelabs.com id 60/2D-10249-955DB015; Fri, 01 Feb 2013 14:46:49 +0000 X-Env-Sender: wei.liu2@citrix.com X-Msg-Ref: server-8.tower-174.messagelabs.com!1359730007!28824148!1 X-Originating-IP: [66.165.176.63] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjYuMTY1LjE3Ni42MyA9PiAzMDA5NDY=\n X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 6750 invoked from network); 1 Feb 2013 14:46:49 -0000 Received: from smtp02.citrix.com (HELO SMTP02.CITRIX.COM) (66.165.176.63) by server-8.tower-174.messagelabs.com with RC4-SHA encrypted SMTP; 1 Feb 2013 14:46:49 -0000 X-IronPort-AV: E=Sophos;i="4.84,579,1355097600"; d="scan'208";a="5665255" Received: from accessns.citrite.net (HELO FTLPEX01CL01.citrite.net) ([10.9.154.239]) by FTLPIPO02.CITRIX.COM with ESMTP/TLS/AES128-SHA; 01 Feb 2013 14:46:47 +0000 Received: from ukmail1.uk.xensource.com (10.80.16.128) by smtprelay.citrix.com (10.13.107.78) with Microsoft SMTP Server id 14.2.318.1; Fri, 1 Feb 2013 09:46:46 -0500 Received: from zion.uk.xensource.com ([10.80.2.73]) by ukmail1.uk.xensource.com with esmtp (Exim 4.69) (envelope-from ) id 1U1Ht8-0002Ws-Hl; Fri, 01 Feb 2013 14:46:46 +0000 Message-ID: <1359730006.23229.118.camel@zion.uk.xensource.com> From: Wei Liu To: Linux Hack Date: Fri, 1 Feb 2013 14:46:46 +0000 In-Reply-To: References: X-Mailer: Evolution 3.6.2 (3.6.2-3.fc18) MIME-Version: 1.0 Cc: "xen-users@lists.xen.org" , wei.liu2@citrix.com Subject: Re: [Xen-users] Troubleshooting Xen HVM boot issues X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: 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, 2013-02-01 at 04:11 +0000, Linux Hack wrote: > Hi, > > > For Xen PV we can boot xm create -c /etc/xen/domu.cfg which entered > into console immediately which is useful for us to troubleshooting the > booting issue. > You can configure serial console for HVM as well - if that helps you troubleshoot your issues. Wei. > > Is there any such options available for Xen HVM too? > > _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Fri Feb 01 16:11:01 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 01 Feb 2013 16: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 1U1JBZ-0007PW-BS; Fri, 01 Feb 2013 16:09:53 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U1JBY-0007PR-0T for xen-users@lists.xen.org; Fri, 01 Feb 2013 16:09:52 +0000 Received: from [85.158.139.83:39729] by server-7.bemta-5.messagelabs.com id 0A/B7-11121-FC8EB015; Fri, 01 Feb 2013 16:09:51 +0000 X-Env-Sender: borodkin.sergey@gmail.com X-Msg-Ref: server-8.tower-182.messagelabs.com!1359734990!19179226!1 X-Originating-IP: [209.85.217.182] X-SpamReason: No, hits=0.0 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, spamassassin: X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 9657 invoked from network); 1 Feb 2013 16:09:50 -0000 Received: from mail-lb0-f182.google.com (HELO mail-lb0-f182.google.com) (209.85.217.182) by server-8.tower-182.messagelabs.com with RC4-SHA encrypted SMTP; 1 Feb 2013 16:09:50 -0000 Received: by mail-lb0-f182.google.com with SMTP id gg6so4730338lbb.13 for ; Fri, 01 Feb 2013 08:09:49 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:from:to:subject:date:message-id:user-agent:in-reply-to :references:mime-version:content-transfer-encoding:content-type; bh=/b2mkrtoNdO3XDS0Gra6W3u/n0Brbi0kQWgZrHie63I=; b=dA3OHwosTvYwVs8G3hIIs/h2aEzG3OIR4UINTTc0r4wJX4YNRJKwk+cSsGpGCAnBQx /uS5CzQS09WBPkRBl4TFhCJeBA2z/MCUJcv223iBLernXe6QpzcEtqjjK2kQHlM7ev7n wjZc3coEDJM+WEVc1rg9p4/s/eSJFdYjCWc8c2cRfR2jexl6l+/qIYTKqRZySsnPaVsZ 49wuIjM5DUAcy87cyoJK2K62VuWljLb3QSz6rFJe5f24DFYPFc+Wzzz/UjCMHq/W6HFk Kknt5PPNtzUOEFhXn+mPB18/BBTtpFflEcTzwcKSOfEJzQOeBIkfhsvRCQ4GWWQzm/5Z STZQ== X-Received: by 10.112.103.196 with SMTP id fy4mr4895321lbb.125.1359734989699; Fri, 01 Feb 2013 08:09:49 -0800 (PST) Received: from zeus.localnet ([93.94.152.79]) by mx.google.com with ESMTPS id iw6sm4358448lab.2.2013.02.01.08.09.47 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 01 Feb 2013 08:09:48 -0800 (PST) From: =?utf-8?B?0JHQvtGA0L7QtNC60LjQvSDQodC10YDQs9C10Lk=?= To: Kristian Hagsted Rasmussen , xen-users Date: Fri, 01 Feb 2013 20:07:40 +0400 Message-ID: <7393629.KEJ18muGpx@zeus> User-Agent: KMail/4.9.5 (Linux/3.6.11-gentoo; KDE/4.9.5; x86_64; ; ) In-Reply-To: <19EF9FEB5AF86243A3F18E5CE75971640C943F8F@hagsted-bserver.hagsted.dk> References: <1655605.ZAW1kWyVl3@zeus> <19EF9FEB5AF86243A3F18E5CE75971640C943F8F@hagsted-bserver.hagsted.dk> MIME-Version: 1.0 Subject: Re: [Xen-users] Xen 4.2.1. BSOD in Windows guests with 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="utf-8" Content-Transfer-Encoding: base64 Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org SGVsbG8sCgpPbiBXZWRuZXNkYXkgMzAgSmFudWFyeSAyMDEzIDE0OjQ0OjQ2IEtyaXN0aWFuIEhh Z3N0ZWQgUmFzbXVzc2VuIHdyb3RlOgo+ID4gLS0tLS1PcmlnaW5hbCBNZXNzYWdlLS0tLS0KPiA+ IEZyb206IHhlbi11c2Vycy1ib3VuY2VzQGxpc3RzLnhlbi5vcmcgW21haWx0bzp4ZW4tdXNlcnMt Cj4gPiBib3VuY2VzQGxpc3RzLnhlbi5vcmddIE9uIEJlaGFsZiBPZiA/Pz8/Pz8/PyA/Pz8/Pz8K PiA+IFNlbnQ6IDI5LiBqYW51YXIgMjAxMyAxOTo0OAo+ID4gVG86IHhlbi11c2Vyc0BsaXN0cy54 ZW4ub3JnCj4gPiBTdWJqZWN0OiBbWGVuLXVzZXJzXSBYZW4gNC4yLjEuIEJTT0QgaW4gV2luZG93 cyBndWVzdHMgd2l0aCBWR0EKPiA+IHBhc3N0aHJvdWdoCj4gPiAKPiA+IEhlbGxvLAo+ID4gCj4g PiBJIGNvbmZpZ3VyZWQgeGVuIHdpdGggZW5hYmxlZCBwYXNzdGhyb3VnaCBwcmltYXJ5IFZHQSBj YXJkIChJbnRlbAo+ID4gSW50ZWdyYXRlZCBncmFmcGhpYyBjb250cm9sbGVyIEhEIDMwMDApIGFu ZCBhdWRpbyBjb250cm9sbGVyIChJbnRlbCBIRAo+ID4gYXVkaW8pIHRvIGh2bSBndWVzdC4KPiA+ IEkgYWxzbyBpbnN0YWxsZWQgR1BMUFYgZHJpdmVycyB0byBpbXByb3ZlIHBlcmZvcm1hbmNlLgo+ IAo+IFdoaWNoIHZlcnNpb24gb2YgR1BMUFY/IEkgYW5kIG1hbnkgb3RoZXJzIGhhdmUgbmV0d29y ayBwcm9ibGVtcyB3aXRoIHRoZQo+IHNpZ25lZCBkcml2ZXJzIGZyb20gdW5pdmVudGlvbiwgdGhp cyBzaG91bGQgYmUgc29sdmVkIGluIHRoZSAzNTcgcmVsZWFzZSwKPiBidXQgdGhlc2UgYXJlIG9u bHkgdGVzdCBzaWduZWQuCgpJIGN1cnJlbnRybHkgdXNlIEdQTFBWIDM1NiB2ZXJzaW9uLgoKPiA+ IEFuZCBpdCB3b3JrcyBmb3IgV2luZG93cyBYUCAoeDg2KSBhbmQgV2luZG93cyA3ICh4ODZfNjQp Lgo+ID4gCj4gPiBCdXQgSSBnZXQgYSBCU09ELCB3aGVuIEkgdHJ5IHRvIGxvYWQgYSBkaXNrIG9y IG5ldHdvcmsgc3Vic3lzdGVtIG9yIHN0YXJ0Cj4gPiBXaW5kb3dzIDcgcGVyZm9ybWFuY2UgdGVz dC4KPiA+IFN0ZXBzIHRvIHJlcHJvZHVjZQo+ID4gMSkgZW5hYmxlIFBDSSBwYXNzdGhyb3VnaCBh bmQgcGFzcyBwcmltYXJ5IFZHQSBjYXJkCj4gPiAyKSBUcnkgdG8gY29weSBhIGxhcmdlIGZpbGUg KDNHIGZvciBleGFtcGxlKSBvdmVyIHRoZSBuZXR3b3JrIGludG8gZ3Vlc3QuCj4gPiAoIG9yIHRy eSB0byBpbnN0YWxsIGxhcmdlIGFwcGxpY2F0aW9uKQo+ID4gU3ltcHRvbXM6Cj4gPiAxKSBBIGdy YXBoaWNhbCBhcnRpZmFjdHMgYXBwZWFycwo+IAo+IEhvdyBtdWNoIG1lbW9yeSBkb2VzIHlvdXIg RG9tVSBoYXZlLCBJIGhhdmUgc2VlbiBhcnRpZmFjdHMgbGlrZSB0aGlzIGlmIEkKPiB1c2VkIDRH IG9mIHJhbS4gSSByZWR1Y2VkIHRoZSBhbW91bnQgdG8gMkcgYW5kIGV2ZXJ5dGhpbmcgaXMgd29y a2luZyBmaW5lLgoKVGhhbmsgeW91IGZvciBhZHZpY2UuCkkgY2hhbmdlZCBndWVzdCBtZW1vcnkg dG8gM0cgYW5kIGdvdCBtb3JlIHN0YWJpbGl0eSwgQnV0IEJTT0QgY29tZXMgYWdhaW4gOi0pCkkg Y2hhbmdlZCBndWVzdCBtZW1vcnkgdG8gMkcgYW5kIGV2ZXJ0aGluZyBiZWNvbWUgT0ssIGV2ZW4g d2luZG93cyBwZXJmb21hbmNlIAp0ZXN0LgpJdCBzZWVtcyB0aGUgbGVzcyBtZW1vcnkgSSBwcm92 aWRlIHRvIGd1ZXN0LCB0aGUgbW9yZSBzdGFiaWxpdHkgSSBvYnRhaW4uCgpJdCBpcyBwYWluZnVs IGZvciBtZSB0byBoYXZlIDE2RyBSQU0gYW5kIHVzZSBvbmx5IDJHLiBEbyB5b3Uga25vdyBhbnkg c29sdXRpb24gCnRvIGZpeCB0aGlzIGlzc3VlPwo+ID4gMikgVGhlbiBjb21lcyB0aGUgQlNPRCBh bmQgZWFjaCB0aW1lIHdpdGggZGlmZmVyZW50IG1lc3NhZ2VzLgo+ID4gCj4gPiBJZiBWR0EgcGFz c3Rocm91Z2ggaXMgb2ZmLCB0aGVyZSBpcyBubyBzdWNoIHByb2JsZW1zLgo+ID4gCj4gPiBBbnkg aWRlYXM/Cj4gPiAKPiA+IE15IHhsIGluZm8gaW4geGxfaW5mby50eHQgaW4gYXR0YWNobWVudC4K PiA+IAo+ID4gTXkgeGwgZG1lc2cgaW4geGxfZG1lc2cudHh0IGluIGF0dGFjaG1lbnQuCj4gPiAK PiA+IERvbWFpbiAwIGtlcm5lbCBjb25maWd1cmF0b24gaW4gZG9tMC5jb25maWcuCj4gPiAKPiA+ IEd1ZXN0IGNmZyBpcyB4bF9odm0uY2ZnIGluIGF0dGFjaG1lbnQuCj4gPiBCeSB0aGUgd2F5IC9k ZXYvbWFwcGVyL294ZW4wIGlzIG9wZW5lZCBMVUtTIHBhcnRpdGlvbgo+ID4gCj4gPiBUaGFuayB5 b3UuCi0tIArQoSDRg9Cy0LDQttC10L3QuNC10LwsINCR0L7RgNC+0LTQutC40L0g0KHQtdGA0LPQ tdC5LgoKCl9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fClhl bi11c2VycyBtYWlsaW5nIGxpc3QKWGVuLXVzZXJzQGxpc3RzLnhlbi5vcmcKaHR0cDovL2xpc3Rz Lnhlbi5vcmcveGVuLXVzZXJz From xen-users-bounces@lists.xen.org Fri Feb 01 16:11:01 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 01 Feb 2013 16: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 1U1JBZ-0007PW-BS; Fri, 01 Feb 2013 16:09:53 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U1JBY-0007PR-0T for xen-users@lists.xen.org; Fri, 01 Feb 2013 16:09:52 +0000 Received: from [85.158.139.83:39729] by server-7.bemta-5.messagelabs.com id 0A/B7-11121-FC8EB015; Fri, 01 Feb 2013 16:09:51 +0000 X-Env-Sender: borodkin.sergey@gmail.com X-Msg-Ref: server-8.tower-182.messagelabs.com!1359734990!19179226!1 X-Originating-IP: [209.85.217.182] X-SpamReason: No, hits=0.0 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, spamassassin: X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 9657 invoked from network); 1 Feb 2013 16:09:50 -0000 Received: from mail-lb0-f182.google.com (HELO mail-lb0-f182.google.com) (209.85.217.182) by server-8.tower-182.messagelabs.com with RC4-SHA encrypted SMTP; 1 Feb 2013 16:09:50 -0000 Received: by mail-lb0-f182.google.com with SMTP id gg6so4730338lbb.13 for ; Fri, 01 Feb 2013 08:09:49 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:from:to:subject:date:message-id:user-agent:in-reply-to :references:mime-version:content-transfer-encoding:content-type; bh=/b2mkrtoNdO3XDS0Gra6W3u/n0Brbi0kQWgZrHie63I=; b=dA3OHwosTvYwVs8G3hIIs/h2aEzG3OIR4UINTTc0r4wJX4YNRJKwk+cSsGpGCAnBQx /uS5CzQS09WBPkRBl4TFhCJeBA2z/MCUJcv223iBLernXe6QpzcEtqjjK2kQHlM7ev7n wjZc3coEDJM+WEVc1rg9p4/s/eSJFdYjCWc8c2cRfR2jexl6l+/qIYTKqRZySsnPaVsZ 49wuIjM5DUAcy87cyoJK2K62VuWljLb3QSz6rFJe5f24DFYPFc+Wzzz/UjCMHq/W6HFk Kknt5PPNtzUOEFhXn+mPB18/BBTtpFflEcTzwcKSOfEJzQOeBIkfhsvRCQ4GWWQzm/5Z STZQ== X-Received: by 10.112.103.196 with SMTP id fy4mr4895321lbb.125.1359734989699; Fri, 01 Feb 2013 08:09:49 -0800 (PST) Received: from zeus.localnet ([93.94.152.79]) by mx.google.com with ESMTPS id iw6sm4358448lab.2.2013.02.01.08.09.47 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 01 Feb 2013 08:09:48 -0800 (PST) From: =?utf-8?B?0JHQvtGA0L7QtNC60LjQvSDQodC10YDQs9C10Lk=?= To: Kristian Hagsted Rasmussen , xen-users Date: Fri, 01 Feb 2013 20:07:40 +0400 Message-ID: <7393629.KEJ18muGpx@zeus> User-Agent: KMail/4.9.5 (Linux/3.6.11-gentoo; KDE/4.9.5; x86_64; ; ) In-Reply-To: <19EF9FEB5AF86243A3F18E5CE75971640C943F8F@hagsted-bserver.hagsted.dk> References: <1655605.ZAW1kWyVl3@zeus> <19EF9FEB5AF86243A3F18E5CE75971640C943F8F@hagsted-bserver.hagsted.dk> MIME-Version: 1.0 Subject: Re: [Xen-users] Xen 4.2.1. BSOD in Windows guests with 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="utf-8" Content-Transfer-Encoding: base64 Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org SGVsbG8sCgpPbiBXZWRuZXNkYXkgMzAgSmFudWFyeSAyMDEzIDE0OjQ0OjQ2IEtyaXN0aWFuIEhh Z3N0ZWQgUmFzbXVzc2VuIHdyb3RlOgo+ID4gLS0tLS1PcmlnaW5hbCBNZXNzYWdlLS0tLS0KPiA+ IEZyb206IHhlbi11c2Vycy1ib3VuY2VzQGxpc3RzLnhlbi5vcmcgW21haWx0bzp4ZW4tdXNlcnMt Cj4gPiBib3VuY2VzQGxpc3RzLnhlbi5vcmddIE9uIEJlaGFsZiBPZiA/Pz8/Pz8/PyA/Pz8/Pz8K PiA+IFNlbnQ6IDI5LiBqYW51YXIgMjAxMyAxOTo0OAo+ID4gVG86IHhlbi11c2Vyc0BsaXN0cy54 ZW4ub3JnCj4gPiBTdWJqZWN0OiBbWGVuLXVzZXJzXSBYZW4gNC4yLjEuIEJTT0QgaW4gV2luZG93 cyBndWVzdHMgd2l0aCBWR0EKPiA+IHBhc3N0aHJvdWdoCj4gPiAKPiA+IEhlbGxvLAo+ID4gCj4g PiBJIGNvbmZpZ3VyZWQgeGVuIHdpdGggZW5hYmxlZCBwYXNzdGhyb3VnaCBwcmltYXJ5IFZHQSBj YXJkIChJbnRlbAo+ID4gSW50ZWdyYXRlZCBncmFmcGhpYyBjb250cm9sbGVyIEhEIDMwMDApIGFu ZCBhdWRpbyBjb250cm9sbGVyIChJbnRlbCBIRAo+ID4gYXVkaW8pIHRvIGh2bSBndWVzdC4KPiA+ IEkgYWxzbyBpbnN0YWxsZWQgR1BMUFYgZHJpdmVycyB0byBpbXByb3ZlIHBlcmZvcm1hbmNlLgo+ IAo+IFdoaWNoIHZlcnNpb24gb2YgR1BMUFY/IEkgYW5kIG1hbnkgb3RoZXJzIGhhdmUgbmV0d29y ayBwcm9ibGVtcyB3aXRoIHRoZQo+IHNpZ25lZCBkcml2ZXJzIGZyb20gdW5pdmVudGlvbiwgdGhp cyBzaG91bGQgYmUgc29sdmVkIGluIHRoZSAzNTcgcmVsZWFzZSwKPiBidXQgdGhlc2UgYXJlIG9u bHkgdGVzdCBzaWduZWQuCgpJIGN1cnJlbnRybHkgdXNlIEdQTFBWIDM1NiB2ZXJzaW9uLgoKPiA+ IEFuZCBpdCB3b3JrcyBmb3IgV2luZG93cyBYUCAoeDg2KSBhbmQgV2luZG93cyA3ICh4ODZfNjQp Lgo+ID4gCj4gPiBCdXQgSSBnZXQgYSBCU09ELCB3aGVuIEkgdHJ5IHRvIGxvYWQgYSBkaXNrIG9y IG5ldHdvcmsgc3Vic3lzdGVtIG9yIHN0YXJ0Cj4gPiBXaW5kb3dzIDcgcGVyZm9ybWFuY2UgdGVz dC4KPiA+IFN0ZXBzIHRvIHJlcHJvZHVjZQo+ID4gMSkgZW5hYmxlIFBDSSBwYXNzdGhyb3VnaCBh bmQgcGFzcyBwcmltYXJ5IFZHQSBjYXJkCj4gPiAyKSBUcnkgdG8gY29weSBhIGxhcmdlIGZpbGUg KDNHIGZvciBleGFtcGxlKSBvdmVyIHRoZSBuZXR3b3JrIGludG8gZ3Vlc3QuCj4gPiAoIG9yIHRy eSB0byBpbnN0YWxsIGxhcmdlIGFwcGxpY2F0aW9uKQo+ID4gU3ltcHRvbXM6Cj4gPiAxKSBBIGdy YXBoaWNhbCBhcnRpZmFjdHMgYXBwZWFycwo+IAo+IEhvdyBtdWNoIG1lbW9yeSBkb2VzIHlvdXIg RG9tVSBoYXZlLCBJIGhhdmUgc2VlbiBhcnRpZmFjdHMgbGlrZSB0aGlzIGlmIEkKPiB1c2VkIDRH IG9mIHJhbS4gSSByZWR1Y2VkIHRoZSBhbW91bnQgdG8gMkcgYW5kIGV2ZXJ5dGhpbmcgaXMgd29y a2luZyBmaW5lLgoKVGhhbmsgeW91IGZvciBhZHZpY2UuCkkgY2hhbmdlZCBndWVzdCBtZW1vcnkg dG8gM0cgYW5kIGdvdCBtb3JlIHN0YWJpbGl0eSwgQnV0IEJTT0QgY29tZXMgYWdhaW4gOi0pCkkg Y2hhbmdlZCBndWVzdCBtZW1vcnkgdG8gMkcgYW5kIGV2ZXJ0aGluZyBiZWNvbWUgT0ssIGV2ZW4g d2luZG93cyBwZXJmb21hbmNlIAp0ZXN0LgpJdCBzZWVtcyB0aGUgbGVzcyBtZW1vcnkgSSBwcm92 aWRlIHRvIGd1ZXN0LCB0aGUgbW9yZSBzdGFiaWxpdHkgSSBvYnRhaW4uCgpJdCBpcyBwYWluZnVs IGZvciBtZSB0byBoYXZlIDE2RyBSQU0gYW5kIHVzZSBvbmx5IDJHLiBEbyB5b3Uga25vdyBhbnkg c29sdXRpb24gCnRvIGZpeCB0aGlzIGlzc3VlPwo+ID4gMikgVGhlbiBjb21lcyB0aGUgQlNPRCBh bmQgZWFjaCB0aW1lIHdpdGggZGlmZmVyZW50IG1lc3NhZ2VzLgo+ID4gCj4gPiBJZiBWR0EgcGFz c3Rocm91Z2ggaXMgb2ZmLCB0aGVyZSBpcyBubyBzdWNoIHByb2JsZW1zLgo+ID4gCj4gPiBBbnkg aWRlYXM/Cj4gPiAKPiA+IE15IHhsIGluZm8gaW4geGxfaW5mby50eHQgaW4gYXR0YWNobWVudC4K PiA+IAo+ID4gTXkgeGwgZG1lc2cgaW4geGxfZG1lc2cudHh0IGluIGF0dGFjaG1lbnQuCj4gPiAK PiA+IERvbWFpbiAwIGtlcm5lbCBjb25maWd1cmF0b24gaW4gZG9tMC5jb25maWcuCj4gPiAKPiA+ IEd1ZXN0IGNmZyBpcyB4bF9odm0uY2ZnIGluIGF0dGFjaG1lbnQuCj4gPiBCeSB0aGUgd2F5IC9k ZXYvbWFwcGVyL294ZW4wIGlzIG9wZW5lZCBMVUtTIHBhcnRpdGlvbgo+ID4gCj4gPiBUaGFuayB5 b3UuCi0tIArQoSDRg9Cy0LDQttC10L3QuNC10LwsINCR0L7RgNC+0LTQutC40L0g0KHQtdGA0LPQ tdC5LgoKCl9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fClhl bi11c2VycyBtYWlsaW5nIGxpc3QKWGVuLXVzZXJzQGxpc3RzLnhlbi5vcmcKaHR0cDovL2xpc3Rz Lnhlbi5vcmcveGVuLXVzZXJz From xen-users-bounces@lists.xen.org Fri Feb 01 17:15:58 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 01 Feb 2013 17:15: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 1U1KCR-0008GY-3u; Fri, 01 Feb 2013 17:14:51 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U1KCP-0008GT-AE for xen-users@lists.xen.org; Fri, 01 Feb 2013 17:14:49 +0000 Received: from [85.158.139.211:20748] by server-13.bemta-5.messagelabs.com id EF/78-06769-808FB015; Fri, 01 Feb 2013 17:14:48 +0000 X-Env-Sender: paul@stimpsonfamily.co.uk X-Msg-Ref: server-9.tower-206.messagelabs.com!1359738887!19217502!1 X-Originating-IP: [94.136.40.61] X-SpamReason: No, hits=1.4 required=7.0 tests=sa_preprocessor: QmFkIElQOiA5NC4xMzYuNDAuNjEgPT4gNTU4MTk=\n,sa_preprocessor: QmFkIElQOiA5NC4xMzYuNDAuNjEgPT4gNTU4MTk=\n, BODY_RANDOM_LONG, HTML_10_20, HTML_MESSAGE X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 8739 invoked from network); 1 Feb 2013 17:14:47 -0000 Received: from mailex.mailcore.me (HELO mailex.mailcore.me) (94.136.40.61) by server-9.tower-206.messagelabs.com with SMTP; 1 Feb 2013 17:14:47 -0000 Received: from [192.165.210.4] (helo=[192.168.225.223]) by mail11.atlas.pipex.net with esmtpa (Exim 4.71) (envelope-from ) id 1U1KCM-0004Bi-Ei for xen-users@lists.xen.org; Fri, 01 Feb 2013 17:14:46 +0000 Message-ID: <510BF806.2010504@stimpsonfamily.co.uk> Date: Fri, 01 Feb 2013 17:14:46 +0000 From: Paul Stimpson User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130106 Thunderbird/17.0.2 MIME-Version: 1.0 To: xen-users@lists.xen.org X-Mailcore-Auth: 8324857 X-Mailcore-Domain: 844183 Subject: [Xen-users] Guest not starting after hardware migration X-BeenThere: xen-users@lists.xen.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="===============4732549711924169466==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org This is a multi-part message in MIME format. --===============4732549711924169466== Content-Type: multipart/alternative; boundary="------------020704050204080705080004" This is a multi-part message in MIME format. --------------020704050204080705080004 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Hi, I've suddenly been told I need to qualify the current Xen platform I'm building on some other hardware for our internal use and I'm having a hard time. I'd really appreciate your help. The platform is an HP DL-180 server (Quad core Xeon E5620 @2.4GHz) and the machine I've been asked to show-horn the install into is a Dell R210 (Quad core Xeon X3430 @2.4GHz). I know the X3430 isn't as hot as the E5620 particularly in the cache department. They both appear to have VT-x and VT-d but I don't think the X3430 has Vpro. I'm not sure if the chipset on the Dell is likely to be deficient in any other way. The install is an Ubuntu 12.04 64-bit Xen 4.2 hypervisor with a 12.04 64-bit guest and a Windows Server 2008 R2-64 guest. There is a single ext2 partition (sda1) on the main drive that contains the host's /boot and all the other partitions are contained in an LVM VG (sda5). A single PCI card is passed through to the Windows guest using VT-d. The first of my woes was that I couldn't put the Clonezilla image onto the Dell as it contains an LVM volume group, drive on the Dell is smaller than the HP and Clonezilla says it can't resize the volume. I did a dd copy of each of the individual partitions and LVM volumes on one of the HP boxes. I created a partition table on the Dell and made an sda1 and sda5. I created all the LVs and dd'd the contents into them. I did find I'd miscalculated the size of sda1 and had trimmed off the end (which should have been empty) so used cp -a to move the files out, reformatted the FS then put them back. I booted the machine on a boot cd, chroot mounted the host fs and installed grub. The machine booted but I found I had to play with the udev network rules and grub.cfg to make everything mount and for the network devices to be recognised. I also doctored all the guest conf files to reference the correct PCI card and remove any references to individual CPU bindings. The machine looks like it boots OK and the host and Linux guest start fine. The Windows VM steadfastly refuses to boot and if I do an xl create on it, I get the following messages: libxl: error: libxl_create.c:420:libxl_domain_make: domain creation fail libxl: error: libxl_create.c:646:initiate_domain_create: cannot make domain: -3 libxl: error: libxl.c:1392:libxl__destroy_domid: non-existant domain -1 libxl: error: libxl.c:1356:domain_destrpy_callback: unable to destroy guest with domid 4294967295 libxl: error: libxl_create.c:1152:domcreate_destruction_cb: unable to destroy domain 4294967295 following failed creation These errors don't seem to contain any useful information to me (the original error displayed concerned failing to allocate memory but I put more RAM in the Dell and that went away) I can't find any /var/log/xen entries for the Windows guest indicating why it was destroyed. There's nothing in kern.log either indicating a problem. I can mount the Windows guest's file system on the host. I see files and I don't see anything that is obviously corrupt. Has anyone else tried to move installs between hardware please? I'd really appreciate any help you could give me in working out why this isn't working. Thanks, Paul. --------------020704050204080705080004 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Hi,

I've suddenly been told I need to qualify the current Xen platform I'm building on some other hardware for our internal use and I'm having a hard time. I'd really appreciate your help.

The platform is an HP DL-180 server (Quad core Xeon E5620 @2.4GHz) and the machine I've been asked to show-horn the install into is a Dell R210 (Quad core Xeon X3430 @2.4GHz). I know the X3430 isn't as hot as the E5620 particularly in the cache department. They both appear to have VT-x and VT-d but I don't think the X3430 has Vpro. I'm not sure if the chipset on the Dell is likely to be deficient in any other way.

The install is an Ubuntu 12.04 64-bit Xen 4.2 hypervisor with a 12.04 64-bit guest and a Windows Server 2008 R2-64 guest. There is a single ext2 partition (sda1) on the main drive that contains the host's /boot and all the other partitions are contained in an LVM VG (sda5). A single PCI card is passed through to the Windows guest using VT-d.

The first of my woes was that I couldn't put the Clonezilla image onto the Dell as it contains an LVM volume group, drive on the Dell is smaller than the HP and Clonezilla says it can't resize the volume. I did a dd copy of each of the individual partitions and LVM volumes on one of the HP boxes. I created a partition table on the Dell and made an sda1 and sda5. I created all the LVs and dd'd the contents into them.

I did find I'd miscalculated the size of sda1 and had trimmed off the end (which should have been empty) so used cp -a to move the files out, reformatted the FS then put them back. I booted the machine on a boot cd, chroot mounted the host fs and installed grub. The machine booted but I found I had to play with the udev network rules and grub.cfg to make everything mount and for the network devices to be recognised. I also doctored all the guest conf files to reference the correct PCI card and remove any references to individual CPU bindings.

The machine looks like it boots OK and the host and Linux guest start fine. The Windows VM steadfastly refuses to boot and if I do an xl create on it, I get the following messages:

libxl: error: libxl_create.c:420:libxl_domain_make: domain creation fail
libxl: error: libxl_create.c:646:initiate_domain_create: cannot make domain: -3
libxl: error: libxl.c:1392:libxl__destroy_domid: non-existant domain -1
libxl: error: libxl.c:1356:domain_destrpy_callback: unable to destroy guest with domid 4294967295
libxl: error: libxl_create.c:1152:domcreate_destruction_cb: unable to destroy domain 4294967295 following failed creation

These errors don't seem to contain any useful information to me (the original error displayed concerned failing to allocate memory but I put more RAM in the Dell and that went away)

I can't find any /var/log/xen entries for the Windows guest indicating why it was destroyed. There's nothing in kern.log either indicating a problem. I can mount the Windows guest's file system on the host. I see files and I don't see anything that is obviously corrupt.

Has anyone else tried to move installs between hardware please? I'd really appreciate any help you could give me in working out why this isn't working.

Thanks,
Paul.
--------------020704050204080705080004-- --===============4732549711924169466== 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 --===============4732549711924169466==-- From xen-users-bounces@lists.xen.org Fri Feb 01 17:15:58 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 01 Feb 2013 17:15: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 1U1KCR-0008GY-3u; Fri, 01 Feb 2013 17:14:51 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U1KCP-0008GT-AE for xen-users@lists.xen.org; Fri, 01 Feb 2013 17:14:49 +0000 Received: from [85.158.139.211:20748] by server-13.bemta-5.messagelabs.com id EF/78-06769-808FB015; Fri, 01 Feb 2013 17:14:48 +0000 X-Env-Sender: paul@stimpsonfamily.co.uk X-Msg-Ref: server-9.tower-206.messagelabs.com!1359738887!19217502!1 X-Originating-IP: [94.136.40.61] X-SpamReason: No, hits=1.4 required=7.0 tests=sa_preprocessor: QmFkIElQOiA5NC4xMzYuNDAuNjEgPT4gNTU4MTk=\n,sa_preprocessor: QmFkIElQOiA5NC4xMzYuNDAuNjEgPT4gNTU4MTk=\n, BODY_RANDOM_LONG, HTML_10_20, HTML_MESSAGE X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 8739 invoked from network); 1 Feb 2013 17:14:47 -0000 Received: from mailex.mailcore.me (HELO mailex.mailcore.me) (94.136.40.61) by server-9.tower-206.messagelabs.com with SMTP; 1 Feb 2013 17:14:47 -0000 Received: from [192.165.210.4] (helo=[192.168.225.223]) by mail11.atlas.pipex.net with esmtpa (Exim 4.71) (envelope-from ) id 1U1KCM-0004Bi-Ei for xen-users@lists.xen.org; Fri, 01 Feb 2013 17:14:46 +0000 Message-ID: <510BF806.2010504@stimpsonfamily.co.uk> Date: Fri, 01 Feb 2013 17:14:46 +0000 From: Paul Stimpson User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130106 Thunderbird/17.0.2 MIME-Version: 1.0 To: xen-users@lists.xen.org X-Mailcore-Auth: 8324857 X-Mailcore-Domain: 844183 Subject: [Xen-users] Guest not starting after hardware migration X-BeenThere: xen-users@lists.xen.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="===============4732549711924169466==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org This is a multi-part message in MIME format. --===============4732549711924169466== Content-Type: multipart/alternative; boundary="------------020704050204080705080004" This is a multi-part message in MIME format. --------------020704050204080705080004 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Hi, I've suddenly been told I need to qualify the current Xen platform I'm building on some other hardware for our internal use and I'm having a hard time. I'd really appreciate your help. The platform is an HP DL-180 server (Quad core Xeon E5620 @2.4GHz) and the machine I've been asked to show-horn the install into is a Dell R210 (Quad core Xeon X3430 @2.4GHz). I know the X3430 isn't as hot as the E5620 particularly in the cache department. They both appear to have VT-x and VT-d but I don't think the X3430 has Vpro. I'm not sure if the chipset on the Dell is likely to be deficient in any other way. The install is an Ubuntu 12.04 64-bit Xen 4.2 hypervisor with a 12.04 64-bit guest and a Windows Server 2008 R2-64 guest. There is a single ext2 partition (sda1) on the main drive that contains the host's /boot and all the other partitions are contained in an LVM VG (sda5). A single PCI card is passed through to the Windows guest using VT-d. The first of my woes was that I couldn't put the Clonezilla image onto the Dell as it contains an LVM volume group, drive on the Dell is smaller than the HP and Clonezilla says it can't resize the volume. I did a dd copy of each of the individual partitions and LVM volumes on one of the HP boxes. I created a partition table on the Dell and made an sda1 and sda5. I created all the LVs and dd'd the contents into them. I did find I'd miscalculated the size of sda1 and had trimmed off the end (which should have been empty) so used cp -a to move the files out, reformatted the FS then put them back. I booted the machine on a boot cd, chroot mounted the host fs and installed grub. The machine booted but I found I had to play with the udev network rules and grub.cfg to make everything mount and for the network devices to be recognised. I also doctored all the guest conf files to reference the correct PCI card and remove any references to individual CPU bindings. The machine looks like it boots OK and the host and Linux guest start fine. The Windows VM steadfastly refuses to boot and if I do an xl create on it, I get the following messages: libxl: error: libxl_create.c:420:libxl_domain_make: domain creation fail libxl: error: libxl_create.c:646:initiate_domain_create: cannot make domain: -3 libxl: error: libxl.c:1392:libxl__destroy_domid: non-existant domain -1 libxl: error: libxl.c:1356:domain_destrpy_callback: unable to destroy guest with domid 4294967295 libxl: error: libxl_create.c:1152:domcreate_destruction_cb: unable to destroy domain 4294967295 following failed creation These errors don't seem to contain any useful information to me (the original error displayed concerned failing to allocate memory but I put more RAM in the Dell and that went away) I can't find any /var/log/xen entries for the Windows guest indicating why it was destroyed. There's nothing in kern.log either indicating a problem. I can mount the Windows guest's file system on the host. I see files and I don't see anything that is obviously corrupt. Has anyone else tried to move installs between hardware please? I'd really appreciate any help you could give me in working out why this isn't working. Thanks, Paul. --------------020704050204080705080004 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Hi,

I've suddenly been told I need to qualify the current Xen platform I'm building on some other hardware for our internal use and I'm having a hard time. I'd really appreciate your help.

The platform is an HP DL-180 server (Quad core Xeon E5620 @2.4GHz) and the machine I've been asked to show-horn the install into is a Dell R210 (Quad core Xeon X3430 @2.4GHz). I know the X3430 isn't as hot as the E5620 particularly in the cache department. They both appear to have VT-x and VT-d but I don't think the X3430 has Vpro. I'm not sure if the chipset on the Dell is likely to be deficient in any other way.

The install is an Ubuntu 12.04 64-bit Xen 4.2 hypervisor with a 12.04 64-bit guest and a Windows Server 2008 R2-64 guest. There is a single ext2 partition (sda1) on the main drive that contains the host's /boot and all the other partitions are contained in an LVM VG (sda5). A single PCI card is passed through to the Windows guest using VT-d.

The first of my woes was that I couldn't put the Clonezilla image onto the Dell as it contains an LVM volume group, drive on the Dell is smaller than the HP and Clonezilla says it can't resize the volume. I did a dd copy of each of the individual partitions and LVM volumes on one of the HP boxes. I created a partition table on the Dell and made an sda1 and sda5. I created all the LVs and dd'd the contents into them.

I did find I'd miscalculated the size of sda1 and had trimmed off the end (which should have been empty) so used cp -a to move the files out, reformatted the FS then put them back. I booted the machine on a boot cd, chroot mounted the host fs and installed grub. The machine booted but I found I had to play with the udev network rules and grub.cfg to make everything mount and for the network devices to be recognised. I also doctored all the guest conf files to reference the correct PCI card and remove any references to individual CPU bindings.

The machine looks like it boots OK and the host and Linux guest start fine. The Windows VM steadfastly refuses to boot and if I do an xl create on it, I get the following messages:

libxl: error: libxl_create.c:420:libxl_domain_make: domain creation fail
libxl: error: libxl_create.c:646:initiate_domain_create: cannot make domain: -3
libxl: error: libxl.c:1392:libxl__destroy_domid: non-existant domain -1
libxl: error: libxl.c:1356:domain_destrpy_callback: unable to destroy guest with domid 4294967295
libxl: error: libxl_create.c:1152:domcreate_destruction_cb: unable to destroy domain 4294967295 following failed creation

These errors don't seem to contain any useful information to me (the original error displayed concerned failing to allocate memory but I put more RAM in the Dell and that went away)

I can't find any /var/log/xen entries for the Windows guest indicating why it was destroyed. There's nothing in kern.log either indicating a problem. I can mount the Windows guest's file system on the host. I see files and I don't see anything that is obviously corrupt.

Has anyone else tried to move installs between hardware please? I'd really appreciate any help you could give me in working out why this isn't working.

Thanks,
Paul.
--------------020704050204080705080004-- --===============4732549711924169466== 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 --===============4732549711924169466==-- From xen-users-bounces@lists.xen.org Fri Feb 01 19:27:25 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 01 Feb 2013 19:27: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 1U1MFd-00017Q-5d; Fri, 01 Feb 2013 19:26:17 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U1MFb-00017L-JV for xen-users@lists.xen.org; Fri, 01 Feb 2013 19:26:15 +0000 Received: from [193.109.254.147:3909] by server-1.bemta-14.messagelabs.com id A7/2C-29874-6D61C015; Fri, 01 Feb 2013 19:26:14 +0000 X-Env-Sender: alk@ondore.com X-Msg-Ref: server-2.tower-27.messagelabs.com!1359746771!8718836!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.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 29147 invoked from network); 1 Feb 2013 19:26:12 -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; 1 Feb 2013 19:26:12 -0000 Received: from [201.122.115.101] (port=49338 helo=mail.ondore.i) by host0a.ondore-systems.com with esmtpsa (TLSv1:DHE-RSA-AES256-SHA:256) (Exim 4.80) (envelope-from ) id 1U1MFW-0006f9-Pv for xen-users@lists.xen.org; Fri, 01 Feb 2013 13:26:10 -0600 Received: from [10.13.34.96] (alk-desktop.sys.ondore.i [10.13.34.96]) by mail.ondore.i (Postfix) with ESMTPSA id 41664A209 for ; Fri, 1 Feb 2013 13:22:30 -0600 (CST) Message-ID: <510C16D1.2090207@ondore.com> Date: Fri, 01 Feb 2013 13:26:09 -0600 From: Alexandre Kouznetsov User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130106 Thunderbird/17.0.2 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 X-Get-Message-Sender-Via: host0a.ondore-systems.com: authenticated_id: sys.intranet@ondore.com Subject: Re: [Xen-users] Unable to start VM guest 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-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. El 01/02/13 04:34, KC LO escribi=F3: > I have create a PV image of CentOS under Xen 4.x version. When I start > the VM guest, I can see the guest GRUB menu. When it continues to boot, > it reports error prompt as Error : 'Serial'. Could you please post the contents of your Grub's menu.list file, and = your DomU's config file? -- = Alexandre Kouznetsov _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Fri Feb 01 19:27:25 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 01 Feb 2013 19:27: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 1U1MFd-00017Q-5d; Fri, 01 Feb 2013 19:26:17 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U1MFb-00017L-JV for xen-users@lists.xen.org; Fri, 01 Feb 2013 19:26:15 +0000 Received: from [193.109.254.147:3909] by server-1.bemta-14.messagelabs.com id A7/2C-29874-6D61C015; Fri, 01 Feb 2013 19:26:14 +0000 X-Env-Sender: alk@ondore.com X-Msg-Ref: server-2.tower-27.messagelabs.com!1359746771!8718836!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.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 29147 invoked from network); 1 Feb 2013 19:26:12 -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; 1 Feb 2013 19:26:12 -0000 Received: from [201.122.115.101] (port=49338 helo=mail.ondore.i) by host0a.ondore-systems.com with esmtpsa (TLSv1:DHE-RSA-AES256-SHA:256) (Exim 4.80) (envelope-from ) id 1U1MFW-0006f9-Pv for xen-users@lists.xen.org; Fri, 01 Feb 2013 13:26:10 -0600 Received: from [10.13.34.96] (alk-desktop.sys.ondore.i [10.13.34.96]) by mail.ondore.i (Postfix) with ESMTPSA id 41664A209 for ; Fri, 1 Feb 2013 13:22:30 -0600 (CST) Message-ID: <510C16D1.2090207@ondore.com> Date: Fri, 01 Feb 2013 13:26:09 -0600 From: Alexandre Kouznetsov User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130106 Thunderbird/17.0.2 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 X-Get-Message-Sender-Via: host0a.ondore-systems.com: authenticated_id: sys.intranet@ondore.com Subject: Re: [Xen-users] Unable to start VM guest 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-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. El 01/02/13 04:34, KC LO escribi=F3: > I have create a PV image of CentOS under Xen 4.x version. When I start > the VM guest, I can see the guest GRUB menu. When it continues to boot, > it reports error prompt as Error : 'Serial'. Could you please post the contents of your Grub's menu.list file, and = your DomU's config file? -- = Alexandre Kouznetsov _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Fri Feb 01 22:12:58 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 01 Feb 2013 22: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 1U1Oph-0003lW-73; Fri, 01 Feb 2013 22:11:41 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U1Opf-0003lK-4l for xen-users@lists.xen.org; Fri, 01 Feb 2013 22:11:39 +0000 Received: from [85.158.139.83:44391] by server-12.bemta-5.messagelabs.com id C1/A5-20195-A9D3C015; Fri, 01 Feb 2013 22:11:38 +0000 X-Env-Sender: foresterlv@gmail.com X-Msg-Ref: server-9.tower-182.messagelabs.com!1359756695!27399563!1 X-Originating-IP: [209.85.219.46] X-SpamReason: No, hits=1.7 required=7.0 tests=BODY_RANDOM_LONG, HTML_10_20,HTML_MESSAGE,RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 16939 invoked from network); 1 Feb 2013 22:11:36 -0000 Received: from mail-oa0-f46.google.com (HELO mail-oa0-f46.google.com) (209.85.219.46) by server-9.tower-182.messagelabs.com with RC4-SHA encrypted SMTP; 1 Feb 2013 22:11:36 -0000 Received: by mail-oa0-f46.google.com with SMTP id k1so4758578oag.19 for ; Fri, 01 Feb 2013 14:11:34 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:sender:date:x-google-sender-auth:message-id :subject:from:to:content-type; bh=pZ8JDt5lyMkZIGEMU1AssHl+uV4a05ReCjlEx1pyypM=; b=I1uqnDxDnxtcB6UtTDDNmXYvt10y8ID0bJlBMQVp/ZKQEaShQPGsi1JChPcE0wNvNj EsMEKEzoiOSlzyIq34xrJMpgMp+fZjbliItb62VBLkqt5YUGEJPmwIYb/Sj1+gjk+/Z8 kVI/xfSK4iLj3lwdWGAZbXCsK9x6qvhM0xx4TqASseAgK+U2jbQLEETVAnuOBgCXheEc o4ztbD73Y+lusBW8TLzAWxDD34ACQlU3SKQfu54otL537vO1clo8io32ZuM0tm4tsW2d GmusW21+ZfVOoD78Ui8UXsjMkBQ87OL1Th2LLuX9TdOlljezLH+Rldpzu34SNotk9yqW bEZA== MIME-Version: 1.0 X-Received: by 10.182.49.102 with SMTP id t6mr9808889obn.75.1359756694753; Fri, 01 Feb 2013 14:11:34 -0800 (PST) Received: by 10.76.79.98 with HTTP; Fri, 1 Feb 2013 14:11:34 -0800 (PST) Date: Fri, 1 Feb 2013 14:11:34 -0800 X-Google-Sender-Auth: IELFAwxMBJQAXtQmvdh-JMV2stc Message-ID: From: Eriks Latosheks To: xen-users@lists.xen.org Subject: [Xen-users] VGA passthrough Catalyst 13.1 crash/BSOD and workaround X-BeenThere: xen-users@lists.xen.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="===============8494002834914169065==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============8494002834914169065== Content-Type: multipart/alternative; boundary=f46d04479f77c5904b04d4b10656 --f46d04479f77c5904b04d4b10656 Content-Type: text/plain; charset=ISO-8859-1 I was able to successfully pass AMD HD7950 to Win8 x64 domU as secondary adapter using Xen 4.2.1 (dom0 is Gentoo x64). Passing as primary one does not work, probably because my system uses UEFI boot, or this is simply not supported by Xen. However when trying to install Catalyst 13.1 (latest stable driver from AMD), domU hangs on the screen where Catalyst installer performs "detecting video adapter". CPU usage drops to 0 and basically nothing happens (mouse pointer stops updating too). As I found out there is a trick how to avoid this crash: 1) boot windows domU without attaching GPU 2) attach video card using xl pci-attach when domU is fully initialized (i.e. user logged to desktop) 3) run Catalyst installation. Catalyst will detect video card and install latest driver without crashing the system. 4) reboot domU with attached GPU Win8 domU works rock-stable for me so far and performance is near live installation (well except hdd, unfortunately GPLPV driver do not work for me but this is another story). --f46d04479f77c5904b04d4b10656 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable I was able to successfully pass AMD HD7950 to Win8 x64 domU as secondary ad= apter using Xen 4.2.1 (dom0 is Gentoo x64). Passing as primary one does not= work, probably because my system uses UEFI boot, or this is simply not sup= ported by Xen.=A0

However when trying to install Catalyst 13.1 (latest stable = driver from AMD), domU hangs on the screen where Catalyst installer perform= s "detecting video adapter". CPU usage drops to 0 and basically n= othing happens (mouse pointer stops updating too).
As I found out there is a trick how to avoid this crash:
1) = boot windows domU without attaching GPU
2) attach video card usin= g xl pci-attach when domU is fully initialized (i.e. user logged to desktop= )
3) run Catalyst installation. Catalyst will detect video card and inst= all latest driver without crashing the system.
4) reboot domU wit= h attached GPU

Win8 domU works rock-stable for me = so far and performance is near live installation (well except hdd, unfortun= ately GPLPV driver do not work for me but this is another story).





=



--f46d04479f77c5904b04d4b10656-- --===============8494002834914169065== 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 --===============8494002834914169065==-- From xen-users-bounces@lists.xen.org Fri Feb 01 22:12:58 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 01 Feb 2013 22: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 1U1Oph-0003lW-73; Fri, 01 Feb 2013 22:11:41 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U1Opf-0003lK-4l for xen-users@lists.xen.org; Fri, 01 Feb 2013 22:11:39 +0000 Received: from [85.158.139.83:44391] by server-12.bemta-5.messagelabs.com id C1/A5-20195-A9D3C015; Fri, 01 Feb 2013 22:11:38 +0000 X-Env-Sender: foresterlv@gmail.com X-Msg-Ref: server-9.tower-182.messagelabs.com!1359756695!27399563!1 X-Originating-IP: [209.85.219.46] X-SpamReason: No, hits=1.7 required=7.0 tests=BODY_RANDOM_LONG, HTML_10_20,HTML_MESSAGE,RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 16939 invoked from network); 1 Feb 2013 22:11:36 -0000 Received: from mail-oa0-f46.google.com (HELO mail-oa0-f46.google.com) (209.85.219.46) by server-9.tower-182.messagelabs.com with RC4-SHA encrypted SMTP; 1 Feb 2013 22:11:36 -0000 Received: by mail-oa0-f46.google.com with SMTP id k1so4758578oag.19 for ; Fri, 01 Feb 2013 14:11:34 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:sender:date:x-google-sender-auth:message-id :subject:from:to:content-type; bh=pZ8JDt5lyMkZIGEMU1AssHl+uV4a05ReCjlEx1pyypM=; b=I1uqnDxDnxtcB6UtTDDNmXYvt10y8ID0bJlBMQVp/ZKQEaShQPGsi1JChPcE0wNvNj EsMEKEzoiOSlzyIq34xrJMpgMp+fZjbliItb62VBLkqt5YUGEJPmwIYb/Sj1+gjk+/Z8 kVI/xfSK4iLj3lwdWGAZbXCsK9x6qvhM0xx4TqASseAgK+U2jbQLEETVAnuOBgCXheEc o4ztbD73Y+lusBW8TLzAWxDD34ACQlU3SKQfu54otL537vO1clo8io32ZuM0tm4tsW2d GmusW21+ZfVOoD78Ui8UXsjMkBQ87OL1Th2LLuX9TdOlljezLH+Rldpzu34SNotk9yqW bEZA== MIME-Version: 1.0 X-Received: by 10.182.49.102 with SMTP id t6mr9808889obn.75.1359756694753; Fri, 01 Feb 2013 14:11:34 -0800 (PST) Received: by 10.76.79.98 with HTTP; Fri, 1 Feb 2013 14:11:34 -0800 (PST) Date: Fri, 1 Feb 2013 14:11:34 -0800 X-Google-Sender-Auth: IELFAwxMBJQAXtQmvdh-JMV2stc Message-ID: From: Eriks Latosheks To: xen-users@lists.xen.org Subject: [Xen-users] VGA passthrough Catalyst 13.1 crash/BSOD and workaround X-BeenThere: xen-users@lists.xen.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="===============8494002834914169065==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============8494002834914169065== Content-Type: multipart/alternative; boundary=f46d04479f77c5904b04d4b10656 --f46d04479f77c5904b04d4b10656 Content-Type: text/plain; charset=ISO-8859-1 I was able to successfully pass AMD HD7950 to Win8 x64 domU as secondary adapter using Xen 4.2.1 (dom0 is Gentoo x64). Passing as primary one does not work, probably because my system uses UEFI boot, or this is simply not supported by Xen. However when trying to install Catalyst 13.1 (latest stable driver from AMD), domU hangs on the screen where Catalyst installer performs "detecting video adapter". CPU usage drops to 0 and basically nothing happens (mouse pointer stops updating too). As I found out there is a trick how to avoid this crash: 1) boot windows domU without attaching GPU 2) attach video card using xl pci-attach when domU is fully initialized (i.e. user logged to desktop) 3) run Catalyst installation. Catalyst will detect video card and install latest driver without crashing the system. 4) reboot domU with attached GPU Win8 domU works rock-stable for me so far and performance is near live installation (well except hdd, unfortunately GPLPV driver do not work for me but this is another story). --f46d04479f77c5904b04d4b10656 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable I was able to successfully pass AMD HD7950 to Win8 x64 domU as secondary ad= apter using Xen 4.2.1 (dom0 is Gentoo x64). Passing as primary one does not= work, probably because my system uses UEFI boot, or this is simply not sup= ported by Xen.=A0

However when trying to install Catalyst 13.1 (latest stable = driver from AMD), domU hangs on the screen where Catalyst installer perform= s "detecting video adapter". CPU usage drops to 0 and basically n= othing happens (mouse pointer stops updating too).
As I found out there is a trick how to avoid this crash:
1) = boot windows domU without attaching GPU
2) attach video card usin= g xl pci-attach when domU is fully initialized (i.e. user logged to desktop= )
3) run Catalyst installation. Catalyst will detect video card and inst= all latest driver without crashing the system.
4) reboot domU wit= h attached GPU

Win8 domU works rock-stable for me = so far and performance is near live installation (well except hdd, unfortun= ately GPLPV driver do not work for me but this is another story).





=



--f46d04479f77c5904b04d4b10656-- --===============8494002834914169065== 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 --===============8494002834914169065==-- From xen-users-bounces@lists.xen.org Fri Feb 01 23:47:32 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 01 Feb 2013 23: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 1U1QJB-0004hQ-Fr; Fri, 01 Feb 2013 23:46:13 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U1QJ9-0004hL-SV for xen-users@lists.xensource.com; Fri, 01 Feb 2013 23:46:11 +0000 Received: from [85.158.143.35:13600] by server-2.bemta-4.messagelabs.com id C2/71-01597-3C35C015; Fri, 01 Feb 2013 23:46:11 +0000 X-Env-Sender: pigeon@pigeond.net X-Msg-Ref: server-11.tower-21.messagelabs.com!1359762367!11409830!1 X-Originating-IP: [203.59.1.219] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogMjAzLjU5LjEuMjE5ID0+IDE4MDEw\n X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 7958 invoked from network); 1 Feb 2013 23:46:09 -0000 Received: from icp-osb-irony-out3.external.iinet.net.au (HELO icp-osb-irony-out3.external.iinet.net.au) (203.59.1.219) by server-11.tower-21.messagelabs.com with SMTP; 1 Feb 2013 23:46:09 -0000 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AlgFABtTDFF8lWUl/2dsb2JhbABFhgG5LhZzgh4BAQEDAQECN0QLCw0UJQ8ZL4gkBQ3CcY4lgykDk2iCLoYTij6DEA X-IronPort-AV: E=Sophos;i="4.84,579,1355068800"; d="scan'208";a="93287381" Received: from unknown (HELO torankusu.pigeond.net) ([124.149.101.37]) by icp-osb-irony-out3.iinet.net.au with ESMTP; 02 Feb 2013 07:46:06 +0800 Received: from furiza.pigeond.net ([192.168.42.20]:48035 helo=pigeond.net) by torankusu.pigeond.net with esmtp (Exim 4.72) (envelope-from ) id 1U1QJ1-00018z-Sp for xen-users@lists.xensource.com; Sat, 02 Feb 2013 10:46:04 +1100 Date: Sat, 2 Feb 2013 10:46:02 +1100 From: Howell Tam To: xen-users@lists.xensource.com Message-ID: <20130202104602.574db75d@pigeond.net> In-Reply-To: <19EF9FEB5AF86243A3F18E5CE75971640C9458A5@hagsted-bserver.hagsted.dk> References: <20130201181930.262fa02b@furiza> <19EF9FEB5AF86243A3F18E5CE75971640C945735@hagsted-bserver.hagsted.dk> <20130201204507.45c74f94@furiza> <19EF9FEB5AF86243A3F18E5CE75971640C945789@hagsted-bserver.hagsted.dk> <20130201213837.30db4acf@furiza> <20130201223630.49944ca1@pigeond.net> <19EF9FEB5AF86243A3F18E5CE75971640C9458A5@hagsted-bserver.hagsted.dk> Organization: pigeond.net X-Mailer: Claws Mail 3.8.1 (GTK+ 2.24.13; x86_64-pc-linux-gnu) Mime-Version: 1.0 Subject: Re: [Xen-users] Intel HD 4000 VGA passthrough not working X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: 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 now get in doubt if I have installed the intel driver, can check it > when I get home. But a discussion on this subject is taking place at > the xen-devel list, see her > http://www.gossamer-threads.com/lists/xen/devel/265109 Thanks, looks like something is happening for the issue. That's good to hear. Guess we'll just have to watch that thread then. -- Regards, Howell. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Fri Feb 01 23:47:32 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 01 Feb 2013 23: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 1U1QJB-0004hQ-Fr; Fri, 01 Feb 2013 23:46:13 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U1QJ9-0004hL-SV for xen-users@lists.xensource.com; Fri, 01 Feb 2013 23:46:11 +0000 Received: from [85.158.143.35:13600] by server-2.bemta-4.messagelabs.com id C2/71-01597-3C35C015; Fri, 01 Feb 2013 23:46:11 +0000 X-Env-Sender: pigeon@pigeond.net X-Msg-Ref: server-11.tower-21.messagelabs.com!1359762367!11409830!1 X-Originating-IP: [203.59.1.219] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogMjAzLjU5LjEuMjE5ID0+IDE4MDEw\n X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 7958 invoked from network); 1 Feb 2013 23:46:09 -0000 Received: from icp-osb-irony-out3.external.iinet.net.au (HELO icp-osb-irony-out3.external.iinet.net.au) (203.59.1.219) by server-11.tower-21.messagelabs.com with SMTP; 1 Feb 2013 23:46:09 -0000 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AlgFABtTDFF8lWUl/2dsb2JhbABFhgG5LhZzgh4BAQEDAQECN0QLCw0UJQ8ZL4gkBQ3CcY4lgykDk2iCLoYTij6DEA X-IronPort-AV: E=Sophos;i="4.84,579,1355068800"; d="scan'208";a="93287381" Received: from unknown (HELO torankusu.pigeond.net) ([124.149.101.37]) by icp-osb-irony-out3.iinet.net.au with ESMTP; 02 Feb 2013 07:46:06 +0800 Received: from furiza.pigeond.net ([192.168.42.20]:48035 helo=pigeond.net) by torankusu.pigeond.net with esmtp (Exim 4.72) (envelope-from ) id 1U1QJ1-00018z-Sp for xen-users@lists.xensource.com; Sat, 02 Feb 2013 10:46:04 +1100 Date: Sat, 2 Feb 2013 10:46:02 +1100 From: Howell Tam To: xen-users@lists.xensource.com Message-ID: <20130202104602.574db75d@pigeond.net> In-Reply-To: <19EF9FEB5AF86243A3F18E5CE75971640C9458A5@hagsted-bserver.hagsted.dk> References: <20130201181930.262fa02b@furiza> <19EF9FEB5AF86243A3F18E5CE75971640C945735@hagsted-bserver.hagsted.dk> <20130201204507.45c74f94@furiza> <19EF9FEB5AF86243A3F18E5CE75971640C945789@hagsted-bserver.hagsted.dk> <20130201213837.30db4acf@furiza> <20130201223630.49944ca1@pigeond.net> <19EF9FEB5AF86243A3F18E5CE75971640C9458A5@hagsted-bserver.hagsted.dk> Organization: pigeond.net X-Mailer: Claws Mail 3.8.1 (GTK+ 2.24.13; x86_64-pc-linux-gnu) Mime-Version: 1.0 Subject: Re: [Xen-users] Intel HD 4000 VGA passthrough not working X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: 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 now get in doubt if I have installed the intel driver, can check it > when I get home. But a discussion on this subject is taking place at > the xen-devel list, see her > http://www.gossamer-threads.com/lists/xen/devel/265109 Thanks, looks like something is happening for the issue. That's good to hear. Guess we'll just have to watch that thread then. -- Regards, Howell. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Sat Feb 02 01:42:34 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sat, 02 Feb 2013 01:42: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 1U1S6W-0003fk-0F; Sat, 02 Feb 2013 01:41:16 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U1S6U-0003ff-Gi for xen-users@lists.xen.org; Sat, 02 Feb 2013 01:41:14 +0000 Received: from [193.109.254.147:55695] by server-15.bemta-14.messagelabs.com id 4E/85-24599-9BE6C015; Sat, 02 Feb 2013 01:41:13 +0000 X-Env-Sender: wei.liu2@citrix.com X-Msg-Ref: server-11.tower-27.messagelabs.com!1359769270!1729603!1 X-Originating-IP: [66.165.176.89] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjYuMTY1LjE3Ni44OSA9PiAxOTk3ODM=\n X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 6269 invoked from network); 2 Feb 2013 01:41:12 -0000 Received: from smtp.citrix.com (HELO SMTP.CITRIX.COM) (66.165.176.89) by server-11.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 2 Feb 2013 01:41:12 -0000 X-IronPort-AV: E=Sophos;i="4.84,588,1355097600"; d="scan'208";a="6032494" Received: from accessns.citrite.net (HELO FTLPEX01CL02.citrite.net) ([10.9.154.239]) by FTLPIPO01.CITRIX.COM with ESMTP/TLS/AES128-SHA; 02 Feb 2013 01:41:09 +0000 Received: from ukmail1.uk.xensource.com (10.80.16.128) by smtprelay.citrix.com (10.13.107.79) with Microsoft SMTP Server id 14.2.318.1; Fri, 1 Feb 2013 20:41:09 -0500 Received: from zion.uk.xensource.com ([10.80.2.73]) by ukmail1.uk.xensource.com with esmtp (Exim 4.69) (envelope-from ) id 1U1S6P-0004dU-81; Sat, 02 Feb 2013 01:41:09 +0000 Message-ID: <1359769269.7477.6.camel@zion.uk.xensource.com> From: Wei Liu To: Linux Hack Date: Sat, 2 Feb 2013 01:41:09 +0000 In-Reply-To: References: <1359730006.23229.118.camel@zion.uk.xensource.com> X-Mailer: Evolution 3.6.2 (3.6.2-3.fc18) MIME-Version: 1.0 Cc: "xen-users@lists.xen.org" , wei.liu2@citrix.com Subject: Re: [Xen-users] Troubleshooting Xen HVM boot issues X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: 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, 2013-02-01 at 23:51 +0000, Linux Hack wrote: > Hi > > > Interesting. Would this serial console work for Xen HVM Windows too? > > TBH I have no idea. Wei. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Sat Feb 02 01:42:34 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sat, 02 Feb 2013 01:42: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 1U1S6W-0003fk-0F; Sat, 02 Feb 2013 01:41:16 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U1S6U-0003ff-Gi for xen-users@lists.xen.org; Sat, 02 Feb 2013 01:41:14 +0000 Received: from [193.109.254.147:55695] by server-15.bemta-14.messagelabs.com id 4E/85-24599-9BE6C015; Sat, 02 Feb 2013 01:41:13 +0000 X-Env-Sender: wei.liu2@citrix.com X-Msg-Ref: server-11.tower-27.messagelabs.com!1359769270!1729603!1 X-Originating-IP: [66.165.176.89] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjYuMTY1LjE3Ni44OSA9PiAxOTk3ODM=\n X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 6269 invoked from network); 2 Feb 2013 01:41:12 -0000 Received: from smtp.citrix.com (HELO SMTP.CITRIX.COM) (66.165.176.89) by server-11.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 2 Feb 2013 01:41:12 -0000 X-IronPort-AV: E=Sophos;i="4.84,588,1355097600"; d="scan'208";a="6032494" Received: from accessns.citrite.net (HELO FTLPEX01CL02.citrite.net) ([10.9.154.239]) by FTLPIPO01.CITRIX.COM with ESMTP/TLS/AES128-SHA; 02 Feb 2013 01:41:09 +0000 Received: from ukmail1.uk.xensource.com (10.80.16.128) by smtprelay.citrix.com (10.13.107.79) with Microsoft SMTP Server id 14.2.318.1; Fri, 1 Feb 2013 20:41:09 -0500 Received: from zion.uk.xensource.com ([10.80.2.73]) by ukmail1.uk.xensource.com with esmtp (Exim 4.69) (envelope-from ) id 1U1S6P-0004dU-81; Sat, 02 Feb 2013 01:41:09 +0000 Message-ID: <1359769269.7477.6.camel@zion.uk.xensource.com> From: Wei Liu To: Linux Hack Date: Sat, 2 Feb 2013 01:41:09 +0000 In-Reply-To: References: <1359730006.23229.118.camel@zion.uk.xensource.com> X-Mailer: Evolution 3.6.2 (3.6.2-3.fc18) MIME-Version: 1.0 Cc: "xen-users@lists.xen.org" , wei.liu2@citrix.com Subject: Re: [Xen-users] Troubleshooting Xen HVM boot issues X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: 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, 2013-02-01 at 23:51 +0000, Linux Hack wrote: > Hi > > > Interesting. Would this serial console work for Xen HVM Windows too? > > TBH I have no idea. Wei. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Sat Feb 02 13:14:00 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sat, 02 Feb 2013 13:14: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 1U1ctm-0008Iv-Lu; Sat, 02 Feb 2013 13:12:50 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U1RGz-0005oA-Qn for xen-users@lists.xensource.com; Sat, 02 Feb 2013 00:48:02 +0000 Received: from [193.109.254.147:61107] by server-4.bemta-14.messagelabs.com id 05/29-20719-1426C015; Sat, 02 Feb 2013 00:48:01 +0000 X-Env-Sender: mgiammarco@gmail.com X-Msg-Ref: server-12.tower-27.messagelabs.com!1359766079!8963328!1 X-Originating-IP: [209.85.220.178] 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.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 13924 invoked from network); 2 Feb 2013 00:48:00 -0000 Received: from mail-vc0-f178.google.com (HELO mail-vc0-f178.google.com) (209.85.220.178) by server-12.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 2 Feb 2013 00:48:00 -0000 Received: by mail-vc0-f178.google.com with SMTP id m8so2832451vcd.9 for ; Fri, 01 Feb 2013 16:47:57 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=Lz6RO0rQT2K95EN2ltcbQi6beuEek8emhcth4MUBSXs=; b=lJEAKeApaQ+3vfDcJPsOfXDQlHFZwcy4t4mxRY06DaDuqVmTwSx3GgUKR1dSt/1PC/ UAwDrmJcDjvhGC4jO3+0epigD2xeypL57FAKDhGm0VobFPL8qQ8Erq3e8lOhlXjfKoz2 0ITnL7jd1wWKw4idlvJM0BCxx1EIF/gX/PKIRkNNE2hTiOH12O2zbHCQSJw2+DAqwlOR pHO0v2AkKoFUFScfI5nFxPj6+fPdLvlQs9a7T0qnJHJu0HzKjTUWgwDxIixsQaZg4hqs wHiejVQQ0CA5ydPP93gWcT3+nnE++BAhDXGHG4ePGeTfKfPlu9AnyrWfoAeD8j5U+utl E0jg== MIME-Version: 1.0 X-Received: by 10.58.45.168 with SMTP id o8mr8970572vem.3.1359766077547; Fri, 01 Feb 2013 16:47:57 -0800 (PST) Received: by 10.52.69.11 with HTTP; Fri, 1 Feb 2013 16:47:57 -0800 (PST) In-Reply-To: <20130131141950.9CA7821C879@mx4-out.mindef.nl> References: <20130116090224.9B73019331F@jmr5021.mindef.local> <20130131141950.9CA7821C879@mx4-out.mindef.nl> Date: Sat, 2 Feb 2013 01:47:57 +0100 Message-ID: From: Mario Giammarco To: J.Witvliet@mindef.nl X-Mailman-Approved-At: Sat, 02 Feb 2013 13:12:47 +0000 Cc: xen-users@lists.xensource.com Subject: Re: [Xen-users] Max hard disks supported by XCP 1.6 X-BeenThere: xen-users@lists.xen.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="===============8622072258159502760==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============8622072258159502760== Content-Type: multipart/alternative; boundary=089e01182a5807a45604d4b33668 --089e01182a5807a45604d4b33668 Content-Type: text/plain; charset=ISO-8859-1 I suppose I cannot do pci-forwarding of sata controller if I do not have hardware IOMMU/vt-d. Anyway I need a custom compiled nas4free to use pv drivers. Any help for this? Thanks, Mario 2013/1/31 > -----Original Message----- > From: xen-users-bounces@lists.xen.org [mailto: > xen-users-bounces@lists.xen.org] On Behalf Of Mario Giammarco > Sent: Wednesday, January 16, 2013 9:49 AM > To: xen-users@lists.xensource.com > Subject: [Xen-users] Max hard disks supported by XCP 1.6 > > Hello, > I would like to use nas4free under xcp 1.6. > I install it under full HVM using "other install media". > Now I am attaching 4 hdds as external disks. > The vm sees at most two hdds, I suppose because of bios > support (1 boot + 1 cdrom + 2 hdds= 4 hdds). > > I need to use more disks, is it possible? > > If not, it seems to me a serious limit. > > Mario > -----Original Message----- > Thought so as well, initially. > > It is just how you look at it.... > Do you need _all_ of your disks during installation? > I mean, after installation you don't need the cd/dvd-rom anymore. > > Other storage area's (/srv, /home) can always be added by means of > NFS/SMB/iSCSI later on. > > If you really need to give to domU a large number of raw devices, one > might do pci-forwarding of a sata/scsi-card. > > Hw > > ______________________________________________________________________ > Dit bericht kan informatie bevatten die niet voor u is bestemd. Indien u > niet de geadresseerde bent of dit bericht abusievelijk aan u is > toegezonden, wordt u verzocht dat aan de afzender te melden en het bericht > te verwijderen. De Staat aanvaardt geen aansprakelijkheid voor schade, van > welke aard ook, die verband houdt met risico's verbonden aan het > elektronisch verzenden van berichten. > > This message may contain information that is not intended for you. If you > are not the addressee or if this message was sent to you by mistake, you > are requested to inform the sender and delete the message. The State > accepts no liability for damage of any kind resulting from the risks > inherent in the electronic transmission of messages. > --089e01182a5807a45604d4b33668 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
I suppose I cannot do pci-forwarding of sata controller if= I do not have hardware IOMMU/vt-d. Anyway I need a custom compiled nas4fre= e to use pv drivers. Any help for this?

Thanks,
Mario


2013/1/31 <J.Witvliet@mindef.nl>
-----Original Message-----
From: xen-users-bounces@= lists.xen.org [mailto:xen-users-bounces@lists.xen.org] On Behalf Of Mario Giammarco
Sent: Wednesday, January 16, 2013 9:49 AM
To: xen-users@lists.xensou= rce.com
Subject: [Xen-users] Max hard disks supported by XCP 1.6

Hello,
I would like to use nas4free under xcp 1.6.
I install it under full HVM using "other install media".
Now I am attaching 4 hdds as external disks.
The vm sees at most two hdds, I suppose because of bios
support (1 boot + 1 cdrom + 2 hdds=3D 4 hdds).

I need to use more disks, is it possible?

If not, it seems to me a serious limit.

Mario
-----Original Message-----
Thought so as well, initially.

It is just how you look at it....
Do you need _all_ of your disks during installation?
I mean, after installation you don't need the cd/dvd-rom anymore.

Other storage area's (/srv, /home) can always be added by means of NFS/= SMB/iSCSI later on.

If you really need to give to domU a large number of raw devices, one might= do pci-forwarding of a sata/scsi-card.

Hw

______________________________________________________________________
Dit bericht kan informatie bevatten die niet voor u is bestemd. Indien u ni= et de geadresseerde bent of dit bericht abusievelijk aan u is toegezonden, = wordt u verzocht dat aan de afzender te melden en het bericht te verwijdere= n. De Staat aanvaardt geen aansprakelijkheid voor schade, van welke aard oo= k, die verband houdt met risico's verbonden aan het elektronisch verzen= den van berichten.

This message may contain information that is not intended for you. If you a= re not the addressee or if this message was sent to you by mistake, you are= requested to inform the sender and delete the message. The State accepts n= o liability for damage of any kind resulting from the risks inherent in the= electronic transmission of messages.

--089e01182a5807a45604d4b33668-- --===============8622072258159502760== 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 --===============8622072258159502760==-- From xen-users-bounces@lists.xen.org Sat Feb 02 13:14:00 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sat, 02 Feb 2013 13:14: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 1U1ctm-0008Iv-Lu; Sat, 02 Feb 2013 13:12:50 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U1RGz-0005oA-Qn for xen-users@lists.xensource.com; Sat, 02 Feb 2013 00:48:02 +0000 Received: from [193.109.254.147:61107] by server-4.bemta-14.messagelabs.com id 05/29-20719-1426C015; Sat, 02 Feb 2013 00:48:01 +0000 X-Env-Sender: mgiammarco@gmail.com X-Msg-Ref: server-12.tower-27.messagelabs.com!1359766079!8963328!1 X-Originating-IP: [209.85.220.178] 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.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 13924 invoked from network); 2 Feb 2013 00:48:00 -0000 Received: from mail-vc0-f178.google.com (HELO mail-vc0-f178.google.com) (209.85.220.178) by server-12.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 2 Feb 2013 00:48:00 -0000 Received: by mail-vc0-f178.google.com with SMTP id m8so2832451vcd.9 for ; Fri, 01 Feb 2013 16:47:57 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=Lz6RO0rQT2K95EN2ltcbQi6beuEek8emhcth4MUBSXs=; b=lJEAKeApaQ+3vfDcJPsOfXDQlHFZwcy4t4mxRY06DaDuqVmTwSx3GgUKR1dSt/1PC/ UAwDrmJcDjvhGC4jO3+0epigD2xeypL57FAKDhGm0VobFPL8qQ8Erq3e8lOhlXjfKoz2 0ITnL7jd1wWKw4idlvJM0BCxx1EIF/gX/PKIRkNNE2hTiOH12O2zbHCQSJw2+DAqwlOR pHO0v2AkKoFUFScfI5nFxPj6+fPdLvlQs9a7T0qnJHJu0HzKjTUWgwDxIixsQaZg4hqs wHiejVQQ0CA5ydPP93gWcT3+nnE++BAhDXGHG4ePGeTfKfPlu9AnyrWfoAeD8j5U+utl E0jg== MIME-Version: 1.0 X-Received: by 10.58.45.168 with SMTP id o8mr8970572vem.3.1359766077547; Fri, 01 Feb 2013 16:47:57 -0800 (PST) Received: by 10.52.69.11 with HTTP; Fri, 1 Feb 2013 16:47:57 -0800 (PST) In-Reply-To: <20130131141950.9CA7821C879@mx4-out.mindef.nl> References: <20130116090224.9B73019331F@jmr5021.mindef.local> <20130131141950.9CA7821C879@mx4-out.mindef.nl> Date: Sat, 2 Feb 2013 01:47:57 +0100 Message-ID: From: Mario Giammarco To: J.Witvliet@mindef.nl X-Mailman-Approved-At: Sat, 02 Feb 2013 13:12:47 +0000 Cc: xen-users@lists.xensource.com Subject: Re: [Xen-users] Max hard disks supported by XCP 1.6 X-BeenThere: xen-users@lists.xen.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="===============8622072258159502760==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============8622072258159502760== Content-Type: multipart/alternative; boundary=089e01182a5807a45604d4b33668 --089e01182a5807a45604d4b33668 Content-Type: text/plain; charset=ISO-8859-1 I suppose I cannot do pci-forwarding of sata controller if I do not have hardware IOMMU/vt-d. Anyway I need a custom compiled nas4free to use pv drivers. Any help for this? Thanks, Mario 2013/1/31 > -----Original Message----- > From: xen-users-bounces@lists.xen.org [mailto: > xen-users-bounces@lists.xen.org] On Behalf Of Mario Giammarco > Sent: Wednesday, January 16, 2013 9:49 AM > To: xen-users@lists.xensource.com > Subject: [Xen-users] Max hard disks supported by XCP 1.6 > > Hello, > I would like to use nas4free under xcp 1.6. > I install it under full HVM using "other install media". > Now I am attaching 4 hdds as external disks. > The vm sees at most two hdds, I suppose because of bios > support (1 boot + 1 cdrom + 2 hdds= 4 hdds). > > I need to use more disks, is it possible? > > If not, it seems to me a serious limit. > > Mario > -----Original Message----- > Thought so as well, initially. > > It is just how you look at it.... > Do you need _all_ of your disks during installation? > I mean, after installation you don't need the cd/dvd-rom anymore. > > Other storage area's (/srv, /home) can always be added by means of > NFS/SMB/iSCSI later on. > > If you really need to give to domU a large number of raw devices, one > might do pci-forwarding of a sata/scsi-card. > > Hw > > ______________________________________________________________________ > Dit bericht kan informatie bevatten die niet voor u is bestemd. Indien u > niet de geadresseerde bent of dit bericht abusievelijk aan u is > toegezonden, wordt u verzocht dat aan de afzender te melden en het bericht > te verwijderen. De Staat aanvaardt geen aansprakelijkheid voor schade, van > welke aard ook, die verband houdt met risico's verbonden aan het > elektronisch verzenden van berichten. > > This message may contain information that is not intended for you. If you > are not the addressee or if this message was sent to you by mistake, you > are requested to inform the sender and delete the message. The State > accepts no liability for damage of any kind resulting from the risks > inherent in the electronic transmission of messages. > --089e01182a5807a45604d4b33668 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
I suppose I cannot do pci-forwarding of sata controller if= I do not have hardware IOMMU/vt-d. Anyway I need a custom compiled nas4fre= e to use pv drivers. Any help for this?

Thanks,
Mario


2013/1/31 <J.Witvliet@mindef.nl>
-----Original Message-----
From: xen-users-bounces@= lists.xen.org [mailto:xen-users-bounces@lists.xen.org] On Behalf Of Mario Giammarco
Sent: Wednesday, January 16, 2013 9:49 AM
To: xen-users@lists.xensou= rce.com
Subject: [Xen-users] Max hard disks supported by XCP 1.6

Hello,
I would like to use nas4free under xcp 1.6.
I install it under full HVM using "other install media".
Now I am attaching 4 hdds as external disks.
The vm sees at most two hdds, I suppose because of bios
support (1 boot + 1 cdrom + 2 hdds=3D 4 hdds).

I need to use more disks, is it possible?

If not, it seems to me a serious limit.

Mario
-----Original Message-----
Thought so as well, initially.

It is just how you look at it....
Do you need _all_ of your disks during installation?
I mean, after installation you don't need the cd/dvd-rom anymore.

Other storage area's (/srv, /home) can always be added by means of NFS/= SMB/iSCSI later on.

If you really need to give to domU a large number of raw devices, one might= do pci-forwarding of a sata/scsi-card.

Hw

______________________________________________________________________
Dit bericht kan informatie bevatten die niet voor u is bestemd. Indien u ni= et de geadresseerde bent of dit bericht abusievelijk aan u is toegezonden, = wordt u verzocht dat aan de afzender te melden en het bericht te verwijdere= n. De Staat aanvaardt geen aansprakelijkheid voor schade, van welke aard oo= k, die verband houdt met risico's verbonden aan het elektronisch verzen= den van berichten.

This message may contain information that is not intended for you. If you a= re not the addressee or if this message was sent to you by mistake, you are= requested to inform the sender and delete the message. The State accepts n= o liability for damage of any kind resulting from the risks inherent in the= electronic transmission of messages.

--089e01182a5807a45604d4b33668-- --===============8622072258159502760== 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 --===============8622072258159502760==-- From xen-users-bounces@lists.xen.org Sat Feb 02 13:14:00 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sat, 02 Feb 2013 13:14: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 1U1ctl-0008Id-EN; Sat, 02 Feb 2013 13:12:49 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U1QQF-000514-To for xen-users@lists.xen.org; Fri, 01 Feb 2013 23:53:32 +0000 Received: from [85.158.143.99:5136] by server-2.bemta-4.messagelabs.com id 39/93-01597-B755C015; Fri, 01 Feb 2013 23:53:31 +0000 X-Env-Sender: linuxhack2012@gmail.com X-Msg-Ref: server-4.tower-216.messagelabs.com!1359762809!24108113!1 X-Originating-IP: [209.85.216.48] 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.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 7375 invoked from network); 1 Feb 2013 23:53:30 -0000 Received: from mail-qa0-f48.google.com (HELO mail-qa0-f48.google.com) (209.85.216.48) by server-4.tower-216.messagelabs.com with RC4-SHA encrypted SMTP; 1 Feb 2013 23:53:30 -0000 Received: by mail-qa0-f48.google.com with SMTP id j8so570792qah.7 for ; Fri, 01 Feb 2013 15:53:29 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:date:message-id:subject:from:to :content-type; bh=ZyqZmDgIxTFLpVuVjdDxOkHv5OUCKvur7RGoX4ukfeE=; b=HMhXQFSHHDyeyh5dT/G58rs/+bpAIzEEgxyT1TC2W9eyRk1sYVSsmv6LWFEo8J+lhy xT9EuaqUeXOz/e19g9zopexj2/E7RgVIihsVhTw2MQ1OhFl1lDT+silF+b/TzYpDU++F Gir4ets52fDIH47PBkIaJ3bzsS4l9qUoUqo90AFZ9BvLj96KS3GhnVEfKN+R0RjJRSW+ wt7HLU66lVvloATEoIpliJJOj0D49HpYDIewbnCf1TnBDjdOrDUwy/935pv67QmDnZJV NQtqzdkvurnkTKF5AX5o/pMxZ3zDeQrUxFLvwOx5MaZ2Jggkijn3lEbfnUABA7JG8/JD xn/w== MIME-Version: 1.0 X-Received: by 10.49.48.43 with SMTP id i11mr17400237qen.3.1359762809436; Fri, 01 Feb 2013 15:53:29 -0800 (PST) Received: by 10.49.52.66 with HTTP; Fri, 1 Feb 2013 15:53:29 -0800 (PST) Date: Sat, 2 Feb 2013 05:23:29 +0530 Message-ID: From: Linux Hack To: "xen-users@lists.xen.org" X-Mailman-Approved-At: Sat, 02 Feb 2013 13:12:47 +0000 Subject: [Xen-users] xl cpupool X-BeenThere: xen-users@lists.xen.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="===============4846479028805347594==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============4846479028805347594== Content-Type: multipart/alternative; boundary=047d7b6d89c23c3c1f04d4b273e5 --047d7b6d89c23c3c1f04d4b273e5 Content-Type: text/plain; charset=ISO-8859-1 Hi, Would it possible to create cpupools with xl after the server boot and then assign one cpu-pool to dom0 and another one for dom-u's? Also is there any change to make this work on server startup? --047d7b6d89c23c3c1f04d4b273e5 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Hi,

Would it possible to create cpupool= s with xl after the server boot and then assign one cpu-pool to dom0 and an= other one for dom-u's?

Also is there any chang= e to make this work on server startup?

--047d7b6d89c23c3c1f04d4b273e5-- --===============4846479028805347594== 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 --===============4846479028805347594==-- From xen-users-bounces@lists.xen.org Sat Feb 02 13:14:00 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sat, 02 Feb 2013 13:14: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 1U1ctl-0008Id-EN; Sat, 02 Feb 2013 13:12:49 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U1QQF-000514-To for xen-users@lists.xen.org; Fri, 01 Feb 2013 23:53:32 +0000 Received: from [85.158.143.99:5136] by server-2.bemta-4.messagelabs.com id 39/93-01597-B755C015; Fri, 01 Feb 2013 23:53:31 +0000 X-Env-Sender: linuxhack2012@gmail.com X-Msg-Ref: server-4.tower-216.messagelabs.com!1359762809!24108113!1 X-Originating-IP: [209.85.216.48] 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.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 7375 invoked from network); 1 Feb 2013 23:53:30 -0000 Received: from mail-qa0-f48.google.com (HELO mail-qa0-f48.google.com) (209.85.216.48) by server-4.tower-216.messagelabs.com with RC4-SHA encrypted SMTP; 1 Feb 2013 23:53:30 -0000 Received: by mail-qa0-f48.google.com with SMTP id j8so570792qah.7 for ; Fri, 01 Feb 2013 15:53:29 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:date:message-id:subject:from:to :content-type; bh=ZyqZmDgIxTFLpVuVjdDxOkHv5OUCKvur7RGoX4ukfeE=; b=HMhXQFSHHDyeyh5dT/G58rs/+bpAIzEEgxyT1TC2W9eyRk1sYVSsmv6LWFEo8J+lhy xT9EuaqUeXOz/e19g9zopexj2/E7RgVIihsVhTw2MQ1OhFl1lDT+silF+b/TzYpDU++F Gir4ets52fDIH47PBkIaJ3bzsS4l9qUoUqo90AFZ9BvLj96KS3GhnVEfKN+R0RjJRSW+ wt7HLU66lVvloATEoIpliJJOj0D49HpYDIewbnCf1TnBDjdOrDUwy/935pv67QmDnZJV NQtqzdkvurnkTKF5AX5o/pMxZ3zDeQrUxFLvwOx5MaZ2Jggkijn3lEbfnUABA7JG8/JD xn/w== MIME-Version: 1.0 X-Received: by 10.49.48.43 with SMTP id i11mr17400237qen.3.1359762809436; Fri, 01 Feb 2013 15:53:29 -0800 (PST) Received: by 10.49.52.66 with HTTP; Fri, 1 Feb 2013 15:53:29 -0800 (PST) Date: Sat, 2 Feb 2013 05:23:29 +0530 Message-ID: From: Linux Hack To: "xen-users@lists.xen.org" X-Mailman-Approved-At: Sat, 02 Feb 2013 13:12:47 +0000 Subject: [Xen-users] xl cpupool X-BeenThere: xen-users@lists.xen.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="===============4846479028805347594==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============4846479028805347594== Content-Type: multipart/alternative; boundary=047d7b6d89c23c3c1f04d4b273e5 --047d7b6d89c23c3c1f04d4b273e5 Content-Type: text/plain; charset=ISO-8859-1 Hi, Would it possible to create cpupools with xl after the server boot and then assign one cpu-pool to dom0 and another one for dom-u's? Also is there any change to make this work on server startup? --047d7b6d89c23c3c1f04d4b273e5 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Hi,

Would it possible to create cpupool= s with xl after the server boot and then assign one cpu-pool to dom0 and an= other one for dom-u's?

Also is there any chang= e to make this work on server startup?

--047d7b6d89c23c3c1f04d4b273e5-- --===============4846479028805347594== 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 --===============4846479028805347594==-- From xen-users-bounces@lists.xen.org Sat Feb 02 13:14:00 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sat, 02 Feb 2013 13:14: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 1U1ctk-0008IL-6s; Sat, 02 Feb 2013 13:12:48 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U1Hsy-0004lz-2T; Fri, 01 Feb 2013 14:46:36 +0000 Received: from [85.158.138.51:32437] by server-11.bemta-3.messagelabs.com id 94/AC-10249-B45DB015; Fri, 01 Feb 2013 14:46:35 +0000 X-Env-Sender: ulf.kreutzberg@hosteurope.de X-Msg-Ref: server-9.tower-174.messagelabs.com!1359729994!30637509!1 X-Originating-IP: [92.51.170.72] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 27242 invoked from network); 1 Feb 2013 14:46:34 -0000 Received: from server01.mc0.hosteurope.de (HELO server01.mc0.hosteurope.de) (92.51.170.72) by server-9.tower-174.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 1 Feb 2013 14:46:34 -0000 Received: from uk.bk.hosteurope.de ([10.20.3.20]); authenticated by mailout.hosteurope.de (server01.mc0.hosteurope.de) running EXperimental Internet Mailer with esmtpsa (TLSv1:AES256-SHA:256) id 1U1Hsu-0007KY-EQ; Fri, 01 Feb 2013 15:46:32 +0100 Message-ID: <510BD542.10602@hosteurope.de> Date: Fri, 01 Feb 2013 15:46:26 +0100 From: Ulf Kreutzberg User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130106 Thunderbird/17.0.2 MIME-Version: 1.0 To: Ian Campbell References: <20121026072821.GA9853@intersect> <1351237241.8558.9.camel@dagon.hellion.org.uk> <20121026121544.GA14662@intersect> <1351255054.15162.66.camel@zakaz.uk.xensource.com> <20121026170920.GA4835@intersect> <1351276218.11876.0.camel@dagon.hellion.org.uk> <51015DB8.40107@hosteurope.de> <1359105618.32057.58.camel@zakaz.uk.xensource.com> <51028DDE.9070907@citrix.com> <510680E6.6050406@hosteurope.de> <1359381541.12252.0.camel@zakaz.uk.xensource.com> In-Reply-To: <1359381541.12252.0.camel@zakaz.uk.xensource.com> X-Enigmail-Version: 1.5 X-Mailman-Approved-At: Sat, 02 Feb 2013 13:12:47 +0000 Cc: "xen-users@lists.xen.org" , xen-devel , Roger Pau Monne Subject: Re: [Xen-users] Problemi using vif-route script X-BeenThere: xen-users@lists.xen.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="===============0808396605630324926==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --===============0808396605630324926== Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="----enig2SXNRDBCVDEFVEEKURTHK" This is an OpenPGP/MIME signed message (RFC 4880 and 3156) ------enig2SXNRDBCVDEFVEEKURTHK Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On 28.01.2013 14:59, Ian Campbell wrote: > On Mon, 2013-01-28 at 13:45 +0000, Ulf Kreutzberg wrote: >> The mac address is not parsed correctly if not padded with leading >> zeros (and no error reported, though):=20 >=20 > Ick, well spotted. It is a bug in xl that it doesn't Do The Right Thing= > here, even if stripping the leading zeroes is somewhat unconventional > IMHO. >=20 > Ian. How shall I proceed here? Shall I open a bug report or did some of you already open one? Thanks and regards, Ulf ------enig2SXNRDBCVDEFVEEKURTHK Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iEYEARECAAYFAlEL1UgACgkQhHSVerqjg04j2wCfVEiYbgBMkSA30WSAJe6rJ2u2 xJ0AnjdrKMwY0LWMJSTPyAgDAjJdye3b =C/MT -----END PGP SIGNATURE----- ------enig2SXNRDBCVDEFVEEKURTHK-- --===============0808396605630324926== 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 --===============0808396605630324926==-- From xen-users-bounces@lists.xen.org Sat Feb 02 13:14:00 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sat, 02 Feb 2013 13:14: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 1U1ctk-0008IL-6s; Sat, 02 Feb 2013 13:12:48 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U1Hsy-0004lz-2T; Fri, 01 Feb 2013 14:46:36 +0000 Received: from [85.158.138.51:32437] by server-11.bemta-3.messagelabs.com id 94/AC-10249-B45DB015; Fri, 01 Feb 2013 14:46:35 +0000 X-Env-Sender: ulf.kreutzberg@hosteurope.de X-Msg-Ref: server-9.tower-174.messagelabs.com!1359729994!30637509!1 X-Originating-IP: [92.51.170.72] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 27242 invoked from network); 1 Feb 2013 14:46:34 -0000 Received: from server01.mc0.hosteurope.de (HELO server01.mc0.hosteurope.de) (92.51.170.72) by server-9.tower-174.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 1 Feb 2013 14:46:34 -0000 Received: from uk.bk.hosteurope.de ([10.20.3.20]); authenticated by mailout.hosteurope.de (server01.mc0.hosteurope.de) running EXperimental Internet Mailer with esmtpsa (TLSv1:AES256-SHA:256) id 1U1Hsu-0007KY-EQ; Fri, 01 Feb 2013 15:46:32 +0100 Message-ID: <510BD542.10602@hosteurope.de> Date: Fri, 01 Feb 2013 15:46:26 +0100 From: Ulf Kreutzberg User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130106 Thunderbird/17.0.2 MIME-Version: 1.0 To: Ian Campbell References: <20121026072821.GA9853@intersect> <1351237241.8558.9.camel@dagon.hellion.org.uk> <20121026121544.GA14662@intersect> <1351255054.15162.66.camel@zakaz.uk.xensource.com> <20121026170920.GA4835@intersect> <1351276218.11876.0.camel@dagon.hellion.org.uk> <51015DB8.40107@hosteurope.de> <1359105618.32057.58.camel@zakaz.uk.xensource.com> <51028DDE.9070907@citrix.com> <510680E6.6050406@hosteurope.de> <1359381541.12252.0.camel@zakaz.uk.xensource.com> In-Reply-To: <1359381541.12252.0.camel@zakaz.uk.xensource.com> X-Enigmail-Version: 1.5 X-Mailman-Approved-At: Sat, 02 Feb 2013 13:12:47 +0000 Cc: "xen-users@lists.xen.org" , xen-devel , Roger Pau Monne Subject: Re: [Xen-users] Problemi using vif-route script X-BeenThere: xen-users@lists.xen.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="===============0808396605630324926==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --===============0808396605630324926== Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="----enig2SXNRDBCVDEFVEEKURTHK" This is an OpenPGP/MIME signed message (RFC 4880 and 3156) ------enig2SXNRDBCVDEFVEEKURTHK Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On 28.01.2013 14:59, Ian Campbell wrote: > On Mon, 2013-01-28 at 13:45 +0000, Ulf Kreutzberg wrote: >> The mac address is not parsed correctly if not padded with leading >> zeros (and no error reported, though):=20 >=20 > Ick, well spotted. It is a bug in xl that it doesn't Do The Right Thing= > here, even if stripping the leading zeroes is somewhat unconventional > IMHO. >=20 > Ian. How shall I proceed here? Shall I open a bug report or did some of you already open one? Thanks and regards, Ulf ------enig2SXNRDBCVDEFVEEKURTHK Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iEYEARECAAYFAlEL1UgACgkQhHSVerqjg04j2wCfVEiYbgBMkSA30WSAJe6rJ2u2 xJ0AnjdrKMwY0LWMJSTPyAgDAjJdye3b =C/MT -----END PGP SIGNATURE----- ------enig2SXNRDBCVDEFVEEKURTHK-- --===============0808396605630324926== 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 --===============0808396605630324926==-- From xen-users-bounces@lists.xen.org Sat Feb 02 13:14:01 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sat, 02 Feb 2013 13:14: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 1U1ctm-0008Im-24; Sat, 02 Feb 2013 13:12:50 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U1QRe-00053L-05 for xen-users@lists.xen.org; Fri, 01 Feb 2013 23:54:58 +0000 Received: from [85.158.139.211:50093] by server-6.bemta-5.messagelabs.com id 9A/63-01489-1D55C015; Fri, 01 Feb 2013 23:54:57 +0000 X-Env-Sender: linuxhack2012@gmail.com X-Msg-Ref: server-6.tower-206.messagelabs.com!1359762895!20771862!1 X-Originating-IP: [209.85.216.176] 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.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 19545 invoked from network); 1 Feb 2013 23:54:56 -0000 Received: from mail-qc0-f176.google.com (HELO mail-qc0-f176.google.com) (209.85.216.176) by server-6.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 1 Feb 2013 23:54:56 -0000 Received: by mail-qc0-f176.google.com with SMTP id n41so2002223qco.35 for ; Fri, 01 Feb 2013 15:54:55 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:date:message-id:subject:from:to :content-type; bh=59Uc1EmO0JPJaGzu7xFsWqc0IgplHgrKsCtdBriuzAE=; b=VYCaZUNin1lPQglC7zO7xGC6tS5tNDTJz18HWNwPA3Ei6lue/Rv5TvYoBE6cN1BGSP J1YV0g9IZn8Zmepq+Qv2uecXl1bDTCiKAMrnmOEL1znXkwfJ+lAiw4gCmq5o97lvvaX8 Z4MiJBUmCT5onxWS/fON6zW/tnRbkaf+nFZHVaxjmrMnulJxAwwJTwcLW+DvM7jY9WfA C652YydE+yTaVdWoPu5UVT3hTZlkbFlTNszYAa+t/NktKFz7ABR4AI9x29uDdkbh/urr Ra+aSDfMvtzMCYSbzRLRUZWCvonf0BT7p+gDP6q/41Ss1cLroMIFp58ip8EkIMvEhp9x pBNA== MIME-Version: 1.0 X-Received: by 10.49.127.101 with SMTP id nf5mr17375320qeb.20.1359762895482; Fri, 01 Feb 2013 15:54:55 -0800 (PST) Received: by 10.49.52.66 with HTTP; Fri, 1 Feb 2013 15:54:55 -0800 (PST) Date: Sat, 2 Feb 2013 05:24:55 +0530 Message-ID: From: Linux Hack To: "xen-users@lists.xen.org" X-Mailman-Approved-At: Sat, 02 Feb 2013 13:12:47 +0000 Subject: [Xen-users] high cpu usage on steal time X-BeenThere: xen-users@lists.xen.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="===============4987752628645609434==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============4987752628645609434== Content-Type: multipart/alternative; boundary=047d7b6dc0bc5d306d04d4b2788d --047d7b6dc0bc5d306d04d4b2788d Content-Type: text/plain; charset=ISO-8859-1 Hi, One of the server is under high cpu usage and when checked steal time is causing the high cpu usage. However I have pinned the vcpu's for dom0 dedicatedly but still no luck. Any thought's that would be great? --047d7b6dc0bc5d306d04d4b2788d Content-Type: text/html; charset=ISO-8859-1
Hi,

One of the server is under high cpu usage and when checked steal time is causing the high cpu usage. However I have pinned the vcpu's for dom0 dedicatedly but still no luck.

Any thought's that would be great?

--047d7b6dc0bc5d306d04d4b2788d-- --===============4987752628645609434== 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 --===============4987752628645609434==-- From xen-users-bounces@lists.xen.org Sat Feb 02 13:14:01 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sat, 02 Feb 2013 13:14: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 1U1ctm-0008Im-24; Sat, 02 Feb 2013 13:12:50 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U1QRe-00053L-05 for xen-users@lists.xen.org; Fri, 01 Feb 2013 23:54:58 +0000 Received: from [85.158.139.211:50093] by server-6.bemta-5.messagelabs.com id 9A/63-01489-1D55C015; Fri, 01 Feb 2013 23:54:57 +0000 X-Env-Sender: linuxhack2012@gmail.com X-Msg-Ref: server-6.tower-206.messagelabs.com!1359762895!20771862!1 X-Originating-IP: [209.85.216.176] 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.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 19545 invoked from network); 1 Feb 2013 23:54:56 -0000 Received: from mail-qc0-f176.google.com (HELO mail-qc0-f176.google.com) (209.85.216.176) by server-6.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 1 Feb 2013 23:54:56 -0000 Received: by mail-qc0-f176.google.com with SMTP id n41so2002223qco.35 for ; Fri, 01 Feb 2013 15:54:55 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:date:message-id:subject:from:to :content-type; bh=59Uc1EmO0JPJaGzu7xFsWqc0IgplHgrKsCtdBriuzAE=; b=VYCaZUNin1lPQglC7zO7xGC6tS5tNDTJz18HWNwPA3Ei6lue/Rv5TvYoBE6cN1BGSP J1YV0g9IZn8Zmepq+Qv2uecXl1bDTCiKAMrnmOEL1znXkwfJ+lAiw4gCmq5o97lvvaX8 Z4MiJBUmCT5onxWS/fON6zW/tnRbkaf+nFZHVaxjmrMnulJxAwwJTwcLW+DvM7jY9WfA C652YydE+yTaVdWoPu5UVT3hTZlkbFlTNszYAa+t/NktKFz7ABR4AI9x29uDdkbh/urr Ra+aSDfMvtzMCYSbzRLRUZWCvonf0BT7p+gDP6q/41Ss1cLroMIFp58ip8EkIMvEhp9x pBNA== MIME-Version: 1.0 X-Received: by 10.49.127.101 with SMTP id nf5mr17375320qeb.20.1359762895482; Fri, 01 Feb 2013 15:54:55 -0800 (PST) Received: by 10.49.52.66 with HTTP; Fri, 1 Feb 2013 15:54:55 -0800 (PST) Date: Sat, 2 Feb 2013 05:24:55 +0530 Message-ID: From: Linux Hack To: "xen-users@lists.xen.org" X-Mailman-Approved-At: Sat, 02 Feb 2013 13:12:47 +0000 Subject: [Xen-users] high cpu usage on steal time X-BeenThere: xen-users@lists.xen.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="===============4987752628645609434==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============4987752628645609434== Content-Type: multipart/alternative; boundary=047d7b6dc0bc5d306d04d4b2788d --047d7b6dc0bc5d306d04d4b2788d Content-Type: text/plain; charset=ISO-8859-1 Hi, One of the server is under high cpu usage and when checked steal time is causing the high cpu usage. However I have pinned the vcpu's for dom0 dedicatedly but still no luck. Any thought's that would be great? --047d7b6dc0bc5d306d04d4b2788d Content-Type: text/html; charset=ISO-8859-1
Hi,

One of the server is under high cpu usage and when checked steal time is causing the high cpu usage. However I have pinned the vcpu's for dom0 dedicatedly but still no luck.

Any thought's that would be great?

--047d7b6dc0bc5d306d04d4b2788d-- --===============4987752628645609434== 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 --===============4987752628645609434==-- From xen-users-bounces@lists.xen.org Sat Feb 02 13:14:01 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sat, 02 Feb 2013 13:14: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 1U1ctk-0008IU-Qf; Sat, 02 Feb 2013 13:12:48 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U1QO5-0004uI-AO for xen-users@lists.xen.org; Fri, 01 Feb 2013 23:51:17 +0000 Received: from [85.158.137.99:63198] by server-3.bemta-3.messagelabs.com id A5/A6-31070-4F45C015; Fri, 01 Feb 2013 23:51:16 +0000 X-Env-Sender: linuxhack2012@gmail.com X-Msg-Ref: server-14.tower-217.messagelabs.com!1359762674!18563248!1 X-Originating-IP: [209.85.216.176] 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.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 16187 invoked from network); 1 Feb 2013 23:51:15 -0000 Received: from mail-qc0-f176.google.com (HELO mail-qc0-f176.google.com) (209.85.216.176) by server-14.tower-217.messagelabs.com with RC4-SHA encrypted SMTP; 1 Feb 2013 23:51:15 -0000 Received: by mail-qc0-f176.google.com with SMTP id n41so1980856qco.7 for ; Fri, 01 Feb 2013 15:51:14 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=ut/3NYHsHWgxe7xk4Ax5Q7F/qyjArdEpYtQFSBtGg0M=; b=CIF6XoLOT+Po0vmxA1alNr+hpHcZtCvEIYd6tF2paK2EClQi8SUstpQs1vAFQwWKu6 Q0/Dye23HcwgE1UO/oF5nwP82aqgA/aRowIP+afGVVMW0tI/r8KICN8DRkfs7yKNXVHm WGgsqBTZSkIHSOhYyac8JuEdC1qpgUYMxsHkKsAZMlqNiqoe2jtJYrFfNcaGNzdweEc5 fq1uke5hd+K4zWKyHx+Y9SMD3kr0c36Kb4jn5DNCJpau2wF8q7Iq9Mugk1naMG23aO4U A7UW251UqBriCxoHhpNwfN0Ed1BBedJlZFAXBSf7QCHq9enTgxaopcgGct90u/h3PMiI oSqA== MIME-Version: 1.0 X-Received: by 10.49.133.68 with SMTP id pa4mr17250035qeb.50.1359762674323; Fri, 01 Feb 2013 15:51:14 -0800 (PST) Received: by 10.49.52.66 with HTTP; Fri, 1 Feb 2013 15:51:14 -0800 (PST) In-Reply-To: <1359730006.23229.118.camel@zion.uk.xensource.com> References: <1359730006.23229.118.camel@zion.uk.xensource.com> Date: Sat, 2 Feb 2013 05:21:14 +0530 Message-ID: From: Linux Hack To: Wei Liu X-Mailman-Approved-At: Sat, 02 Feb 2013 13:12:47 +0000 Cc: "xen-users@lists.xen.org" Subject: Re: [Xen-users] Troubleshooting Xen HVM boot issues X-BeenThere: xen-users@lists.xen.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="===============4938909426830927302==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============4938909426830927302== Content-Type: multipart/alternative; boundary=047d7bd6b99c2e907804d4b26b47 --047d7bd6b99c2e907804d4b26b47 Content-Type: text/plain; charset=ISO-8859-1 Hi Interesting. Would this serial console work for Xen HVM Windows too? On Fri, Feb 1, 2013 at 8:16 PM, Wei Liu wrote: > On Fri, 2013-02-01 at 04:11 +0000, Linux Hack wrote: > > Hi, > > > > > > For Xen PV we can boot xm create -c /etc/xen/domu.cfg which entered > > into console immediately which is useful for us to troubleshooting the > > booting issue. > > > > You can configure serial console for HVM as well - if that helps you > troubleshoot your issues. > > > Wei. > > > > > Is there any such options available for Xen HVM too? > > > > > > > --047d7bd6b99c2e907804d4b26b47 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Hi

Interesting. Would this serial conso= le work for Xen HVM Windows too?



On Fri, Feb 1, 2013 at 8:16 P= M, Wei Liu <wei.liu2@citrix.com> wrote:
On Fri, 2013-02-01 at 04:1= 1 +0000, Linux Hack wrote:
> Hi,
>
>
> For Xen PV we can boot xm create -c /etc/xen/domu.cfg which entered > into console immediately which is useful for us to troubleshooting the=
> booting issue.
>

You can configure serial console for HVM as well - if that helps you<= br> troubleshoot your issues.


Wei.

>
> Is there any such options available for Xen HVM too?
>
>



--047d7bd6b99c2e907804d4b26b47-- --===============4938909426830927302== 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 --===============4938909426830927302==-- From xen-users-bounces@lists.xen.org Sat Feb 02 13:14:01 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sat, 02 Feb 2013 13:14: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 1U1ctk-0008IU-Qf; Sat, 02 Feb 2013 13:12:48 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U1QO5-0004uI-AO for xen-users@lists.xen.org; Fri, 01 Feb 2013 23:51:17 +0000 Received: from [85.158.137.99:63198] by server-3.bemta-3.messagelabs.com id A5/A6-31070-4F45C015; Fri, 01 Feb 2013 23:51:16 +0000 X-Env-Sender: linuxhack2012@gmail.com X-Msg-Ref: server-14.tower-217.messagelabs.com!1359762674!18563248!1 X-Originating-IP: [209.85.216.176] 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.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 16187 invoked from network); 1 Feb 2013 23:51:15 -0000 Received: from mail-qc0-f176.google.com (HELO mail-qc0-f176.google.com) (209.85.216.176) by server-14.tower-217.messagelabs.com with RC4-SHA encrypted SMTP; 1 Feb 2013 23:51:15 -0000 Received: by mail-qc0-f176.google.com with SMTP id n41so1980856qco.7 for ; Fri, 01 Feb 2013 15:51:14 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=ut/3NYHsHWgxe7xk4Ax5Q7F/qyjArdEpYtQFSBtGg0M=; b=CIF6XoLOT+Po0vmxA1alNr+hpHcZtCvEIYd6tF2paK2EClQi8SUstpQs1vAFQwWKu6 Q0/Dye23HcwgE1UO/oF5nwP82aqgA/aRowIP+afGVVMW0tI/r8KICN8DRkfs7yKNXVHm WGgsqBTZSkIHSOhYyac8JuEdC1qpgUYMxsHkKsAZMlqNiqoe2jtJYrFfNcaGNzdweEc5 fq1uke5hd+K4zWKyHx+Y9SMD3kr0c36Kb4jn5DNCJpau2wF8q7Iq9Mugk1naMG23aO4U A7UW251UqBriCxoHhpNwfN0Ed1BBedJlZFAXBSf7QCHq9enTgxaopcgGct90u/h3PMiI oSqA== MIME-Version: 1.0 X-Received: by 10.49.133.68 with SMTP id pa4mr17250035qeb.50.1359762674323; Fri, 01 Feb 2013 15:51:14 -0800 (PST) Received: by 10.49.52.66 with HTTP; Fri, 1 Feb 2013 15:51:14 -0800 (PST) In-Reply-To: <1359730006.23229.118.camel@zion.uk.xensource.com> References: <1359730006.23229.118.camel@zion.uk.xensource.com> Date: Sat, 2 Feb 2013 05:21:14 +0530 Message-ID: From: Linux Hack To: Wei Liu X-Mailman-Approved-At: Sat, 02 Feb 2013 13:12:47 +0000 Cc: "xen-users@lists.xen.org" Subject: Re: [Xen-users] Troubleshooting Xen HVM boot issues X-BeenThere: xen-users@lists.xen.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="===============4938909426830927302==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============4938909426830927302== Content-Type: multipart/alternative; boundary=047d7bd6b99c2e907804d4b26b47 --047d7bd6b99c2e907804d4b26b47 Content-Type: text/plain; charset=ISO-8859-1 Hi Interesting. Would this serial console work for Xen HVM Windows too? On Fri, Feb 1, 2013 at 8:16 PM, Wei Liu wrote: > On Fri, 2013-02-01 at 04:11 +0000, Linux Hack wrote: > > Hi, > > > > > > For Xen PV we can boot xm create -c /etc/xen/domu.cfg which entered > > into console immediately which is useful for us to troubleshooting the > > booting issue. > > > > You can configure serial console for HVM as well - if that helps you > troubleshoot your issues. > > > Wei. > > > > > Is there any such options available for Xen HVM too? > > > > > > > --047d7bd6b99c2e907804d4b26b47 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Hi

Interesting. Would this serial conso= le work for Xen HVM Windows too?



On Fri, Feb 1, 2013 at 8:16 P= M, Wei Liu <wei.liu2@citrix.com> wrote:
On Fri, 2013-02-01 at 04:1= 1 +0000, Linux Hack wrote:
> Hi,
>
>
> For Xen PV we can boot xm create -c /etc/xen/domu.cfg which entered > into console immediately which is useful for us to troubleshooting the=
> booting issue.
>

You can configure serial console for HVM as well - if that helps you<= br> troubleshoot your issues.


Wei.

>
> Is there any such options available for Xen HVM too?
>
>



--047d7bd6b99c2e907804d4b26b47-- --===============4938909426830927302== 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 --===============4938909426830927302==-- From xen-users-bounces@lists.xen.org Sat Feb 02 14:09:54 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sat, 02 Feb 2013 14:09: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 1U1dm7-0001be-OQ; Sat, 02 Feb 2013 14:08:59 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U1dm6-0001bR-3E; Sat, 02 Feb 2013 14:08:58 +0000 Received: from [85.158.139.211:23468] by server-5.bemta-5.messagelabs.com id 55/BE-11945-9FD1D015; Sat, 02 Feb 2013 14:08:57 +0000 X-Env-Sender: eneal@businessgrade.com X-Msg-Ref: server-16.tower-206.messagelabs.com!1359814136!19672841!1 X-Originating-IP: [66.151.104.17] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 15559 invoked from network); 2 Feb 2013 14:08:56 -0000 Received: from smtp1.businessgrade.com (HELO smtp1.businessgrade.com) (66.151.104.17) by server-16.tower-206.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 2 Feb 2013 14:08:56 -0000 Received: from ashslvha1.businessgrade.local (127.0.0.1) by ashslvha1.businessgrade.local (Axigen) with ESMTPSA id 33546A; Sat, 2 Feb 2013 09:11:26 -0500 Received: from [70.197.136.216] by businessgrade.com with HTTP; Sat, 2 Feb 2013 09:11:26 -0500 From: Errol Neal Date: Sat, 2 Feb 2013 09:11:26 -0500 X-Mailer: Axigen WebMail To: xen-api , "xen-users@lists.xensource.com" Message-ID: <1359814286844364500@businessgrade.com> In-Reply-To: <1359682467321281500@businessgrade.com> References: <1359682467321281500@businessgrade.com> Importance: Normal MIME-Version: 1.0 Content-Disposition: inline Subject: Re: [Xen-users] [XCP] xe vdi-create and sharable=true flag X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: eneal@businessgrade.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 Thu, 01/31/2013 08:34 PM, Errol Neal wrote: > Hi folks. > I'm trying to figure out what has changed about XCP 1.6 vs XCP 1.1 that is seemingly preventing me from creating a VDI that can be attached to multiple VMs. > I maintain a small blog about virtualization and high availability and I documented the necessary steps here: > > http://www.ha-guru.com/sharing-virtual-disks-between-xenserver-xcp-vms/ > > This was done on a stand alone Dell R610 server using local storage and the server is running XCP 1.1 and using this, I was able to build a 3-node NAS cluster on XCP. > Trying to execute these same steps on a similar server running XCP 1.6, the results are not the same. Essentially, the sharable flag for the VDI stays false. > > Now the conditions have somewhat changed because I'm testing on a server in a pool. Would that have any impact? Can anyone think of any other reasons why this was working for me and is now seemingly not working? > Anybody? Anyone? I opened an issue at git hub but its getting no love lol (up to this point) . Any help would be really appreciated.. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Sat Feb 02 14:09:54 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sat, 02 Feb 2013 14:09: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 1U1dm7-0001be-OQ; Sat, 02 Feb 2013 14:08:59 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U1dm6-0001bR-3E; Sat, 02 Feb 2013 14:08:58 +0000 Received: from [85.158.139.211:23468] by server-5.bemta-5.messagelabs.com id 55/BE-11945-9FD1D015; Sat, 02 Feb 2013 14:08:57 +0000 X-Env-Sender: eneal@businessgrade.com X-Msg-Ref: server-16.tower-206.messagelabs.com!1359814136!19672841!1 X-Originating-IP: [66.151.104.17] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 15559 invoked from network); 2 Feb 2013 14:08:56 -0000 Received: from smtp1.businessgrade.com (HELO smtp1.businessgrade.com) (66.151.104.17) by server-16.tower-206.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 2 Feb 2013 14:08:56 -0000 Received: from ashslvha1.businessgrade.local (127.0.0.1) by ashslvha1.businessgrade.local (Axigen) with ESMTPSA id 33546A; Sat, 2 Feb 2013 09:11:26 -0500 Received: from [70.197.136.216] by businessgrade.com with HTTP; Sat, 2 Feb 2013 09:11:26 -0500 From: Errol Neal Date: Sat, 2 Feb 2013 09:11:26 -0500 X-Mailer: Axigen WebMail To: xen-api , "xen-users@lists.xensource.com" Message-ID: <1359814286844364500@businessgrade.com> In-Reply-To: <1359682467321281500@businessgrade.com> References: <1359682467321281500@businessgrade.com> Importance: Normal MIME-Version: 1.0 Content-Disposition: inline Subject: Re: [Xen-users] [XCP] xe vdi-create and sharable=true flag X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: eneal@businessgrade.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 Thu, 01/31/2013 08:34 PM, Errol Neal wrote: > Hi folks. > I'm trying to figure out what has changed about XCP 1.6 vs XCP 1.1 that is seemingly preventing me from creating a VDI that can be attached to multiple VMs. > I maintain a small blog about virtualization and high availability and I documented the necessary steps here: > > http://www.ha-guru.com/sharing-virtual-disks-between-xenserver-xcp-vms/ > > This was done on a stand alone Dell R610 server using local storage and the server is running XCP 1.1 and using this, I was able to build a 3-node NAS cluster on XCP. > Trying to execute these same steps on a similar server running XCP 1.6, the results are not the same. Essentially, the sharable flag for the VDI stays false. > > Now the conditions have somewhat changed because I'm testing on a server in a pool. Would that have any impact? Can anyone think of any other reasons why this was working for me and is now seemingly not working? > Anybody? Anyone? I opened an issue at git hub but its getting no love lol (up to this point) . Any help would be really appreciated.. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Sat Feb 02 15:52:54 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sat, 02 Feb 2013 15:52: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 1U1fNT-0002Qi-Ms; Sat, 02 Feb 2013 15:51:39 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U1fNR-0002QT-Co; Sat, 02 Feb 2013 15:51:37 +0000 Received: from [85.158.143.99:12337] by server-2.bemta-4.messagelabs.com id CB/F7-01597-8063D015; Sat, 02 Feb 2013 15:51:36 +0000 X-Env-Sender: roger.pau@citrix.com X-Msg-Ref: server-15.tower-216.messagelabs.com!1359820295!30537638!1 X-Originating-IP: [46.33.159.39] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNDYuMzMuMTU5LjM5ID0+IDIwNTY3\n X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 746 invoked from network); 2 Feb 2013 15:51:36 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (46.33.159.39) by server-15.tower-216.messagelabs.com with RC4-SHA encrypted SMTP; 2 Feb 2013 15:51:36 -0000 X-IronPort-AV: E=Sophos;i="4.84,591,1355097600"; d="scan'208";a="1093448" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 02 Feb 2013 15:51:35 +0000 Received: from Roger-2.local (10.30.249.242) by LONPMAILMX01.citrite.net (10.30.203.162) with Microsoft SMTP Server id 8.3.297.1; Sat, 2 Feb 2013 15:51:35 +0000 Message-ID: <510D3609.80301@citrix.com> Date: Sat, 2 Feb 2013 16:51:37 +0100 From: =?UTF-8?B?Um9nZXIgUGF1IE1vbm7DqQ==?= User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130107 Thunderbird/17.0.2 MIME-Version: 1.0 To: Ulf Kreutzberg References: <20121026072821.GA9853@intersect> <1351237241.8558.9.camel@dagon.hellion.org.uk> <20121026121544.GA14662@intersect> <1351255054.15162.66.camel@zakaz.uk.xensource.com> <20121026170920.GA4835@intersect> <1351276218.11876.0.camel@dagon.hellion.org.uk> <51015DB8.40107@hosteurope.de> <1359105618.32057.58.camel@zakaz.uk.xensource.com> <51028DDE.9070907@citrix.com> <510680E6.6050406@hosteurope.de> <1359381541.12252.0.camel@zakaz.uk.xensource.com> <510BD542.10602@hosteurope.de> In-Reply-To: <510BD542.10602@hosteurope.de> Cc: "xen-users@lists.xen.org" , Ian Campbell , xen-devel Subject: Re: [Xen-users] Problemi using vif-route script X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: 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 01/02/13 15:46, Ulf Kreutzberg wrote: > > On 28.01.2013 14:59, Ian Campbell wrote: >> On Mon, 2013-01-28 at 13:45 +0000, Ulf Kreutzberg wrote: >>> The mac address is not parsed correctly if not padded with leading >>> zeros (and no error reported, though): >> >> Ick, well spotted. It is a bug in xl that it doesn't Do The Right Thing >> here, even if stripping the leading zeroes is somewhat unconventional >> IMHO. >> >> Ian. > > How shall I proceed here? Shall I open a bug report or did some of you > already open one? Hello, I've send a patch series that I think should fix your issues, could you please try them and report back? http://lists.xen.org/archives/html/xen-devel/2013-01/msg02217.html Thanks, Roger. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Sat Feb 02 15:52:54 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sat, 02 Feb 2013 15:52: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 1U1fNT-0002Qi-Ms; Sat, 02 Feb 2013 15:51:39 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U1fNR-0002QT-Co; Sat, 02 Feb 2013 15:51:37 +0000 Received: from [85.158.143.99:12337] by server-2.bemta-4.messagelabs.com id CB/F7-01597-8063D015; Sat, 02 Feb 2013 15:51:36 +0000 X-Env-Sender: roger.pau@citrix.com X-Msg-Ref: server-15.tower-216.messagelabs.com!1359820295!30537638!1 X-Originating-IP: [46.33.159.39] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNDYuMzMuMTU5LjM5ID0+IDIwNTY3\n X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 746 invoked from network); 2 Feb 2013 15:51:36 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (46.33.159.39) by server-15.tower-216.messagelabs.com with RC4-SHA encrypted SMTP; 2 Feb 2013 15:51:36 -0000 X-IronPort-AV: E=Sophos;i="4.84,591,1355097600"; d="scan'208";a="1093448" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 02 Feb 2013 15:51:35 +0000 Received: from Roger-2.local (10.30.249.242) by LONPMAILMX01.citrite.net (10.30.203.162) with Microsoft SMTP Server id 8.3.297.1; Sat, 2 Feb 2013 15:51:35 +0000 Message-ID: <510D3609.80301@citrix.com> Date: Sat, 2 Feb 2013 16:51:37 +0100 From: =?UTF-8?B?Um9nZXIgUGF1IE1vbm7DqQ==?= User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130107 Thunderbird/17.0.2 MIME-Version: 1.0 To: Ulf Kreutzberg References: <20121026072821.GA9853@intersect> <1351237241.8558.9.camel@dagon.hellion.org.uk> <20121026121544.GA14662@intersect> <1351255054.15162.66.camel@zakaz.uk.xensource.com> <20121026170920.GA4835@intersect> <1351276218.11876.0.camel@dagon.hellion.org.uk> <51015DB8.40107@hosteurope.de> <1359105618.32057.58.camel@zakaz.uk.xensource.com> <51028DDE.9070907@citrix.com> <510680E6.6050406@hosteurope.de> <1359381541.12252.0.camel@zakaz.uk.xensource.com> <510BD542.10602@hosteurope.de> In-Reply-To: <510BD542.10602@hosteurope.de> Cc: "xen-users@lists.xen.org" , Ian Campbell , xen-devel Subject: Re: [Xen-users] Problemi using vif-route script X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: 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 01/02/13 15:46, Ulf Kreutzberg wrote: > > On 28.01.2013 14:59, Ian Campbell wrote: >> On Mon, 2013-01-28 at 13:45 +0000, Ulf Kreutzberg wrote: >>> The mac address is not parsed correctly if not padded with leading >>> zeros (and no error reported, though): >> >> Ick, well spotted. It is a bug in xl that it doesn't Do The Right Thing >> here, even if stripping the leading zeroes is somewhat unconventional >> IMHO. >> >> Ian. > > How shall I proceed here? Shall I open a bug report or did some of you > already open one? Hello, I've send a patch series that I think should fix your issues, could you please try them and report back? http://lists.xen.org/archives/html/xen-devel/2013-01/msg02217.html Thanks, Roger. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Sat Feb 02 22:38:41 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sat, 02 Feb 2013 22:38: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 1U1li1-0004ti-TY; Sat, 02 Feb 2013 22:37:17 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U1li0-0004td-PJ for xen-users@lists.xen.org; Sat, 02 Feb 2013 22:37:17 +0000 Received: from [85.158.138.51:8120] by server-6.bemta-3.messagelabs.com id 6A/0D-29959-7159D015; Sat, 02 Feb 2013 22:37:11 +0000 X-Env-Sender: agya.naila@gmail.com X-Msg-Ref: server-12.tower-174.messagelabs.com!1359844630!21853586!1 X-Originating-IP: [209.85.212.175] 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.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 5144 invoked from network); 2 Feb 2013 22:37:10 -0000 Received: from mail-wi0-f175.google.com (HELO mail-wi0-f175.google.com) (209.85.212.175) by server-12.tower-174.messagelabs.com with RC4-SHA encrypted SMTP; 2 Feb 2013 22:37:10 -0000 Received: by mail-wi0-f175.google.com with SMTP id l13so1245260wie.2 for ; Sat, 02 Feb 2013 14:37:10 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:date:message-id:subject:from:to :content-type; bh=8er7A6nTMnT0q5rz+Fmf6P7yEqRq0oB/l8s3GHbvHhI=; b=kq1yT9m4RTAq+S3+NuTQjoG9iOBV07uPxy33ZQpwrIsMrADz3ZKArBAvFHnvaEaEii 9bDrBmJatrRiMeo8DRS3iiq1uGAt4d+1mbmN8P4uNuG+O3gA40QtBC80cwuWIeBBXxO7 0VnX5ZP+rcoiNXcImSrhYlFzpuCzj8xN6CbX+66REgANKf2hJ6QQVdYsxpRsIAunvpj/ sWEtef823FP5SsSVoE4uJFZn5CCOSA4MkJFvrDOnB/0A8QfdzlqVW3HWl4M7RYLgtqyZ ahM+o0+HGSqmcwTwRRU9xrqf7Q5bj7QCsE5shBkv92GyVrKD5ztWf+EJ1kbSWYeoOzmP bV+g== MIME-Version: 1.0 X-Received: by 10.180.102.7 with SMTP id fk7mr3815203wib.27.1359844630394; Sat, 02 Feb 2013 14:37:10 -0800 (PST) Received: by 10.216.236.13 with HTTP; Sat, 2 Feb 2013 14:37:10 -0800 (PST) Date: Sat, 2 Feb 2013 23:37:10 +0100 Message-ID: From: agya naila To: xen-users@lists.xen.org Subject: [Xen-users] Running XEN 4.1 64 bit on Ubuntu desktop without VTx X-BeenThere: xen-users@lists.xen.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="===============7427730255233175069==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============7427730255233175069== Content-Type: multipart/alternative; boundary=f46d0444e7d724f56d04d4c58080 --f46d0444e7d724f56d04d4c58080 Content-Type: text/plain; charset=ISO-8859-1 Dear all, I am quite new in this virtualization area. I am want to do some experiment with live migration using xen. However, I got problem since my server didn't support VTx. I am using Ubuntu desktop 12.04 64 bit with Xen 4.1 Amd64. But when I reload the machine it wont start, since the XEN website its doesn't matter using Paravirtualization without VTx support I dont know what is the problem since I didn't start to install para virtualized guest yet. I juts install the XEN and reload the maschine and its failed. Does any body now the problem and solution, I would appreciate that. Regards, Agya --f46d0444e7d724f56d04d4c58080 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Dear all,

I am quite new in this virtualization area. I = am want to do some experiment with live migration using xen. However, I got= problem since my server didn't support VTx. I am using Ubuntu desktop = 12.04 64 bit with Xen 4.1 Amd64. But when I reload the machine it wont star= t, since the XEN website its doesn't matter using Paravirtualization wi= thout VTx support I dont know what is the problem since I didn't start = to install para virtualized guest yet. I juts install the XEN and reload th= e maschine and its failed. Does any body now the problem and solution, I wo= uld appreciate that.

Regards,

Agya
--f46d0444e7d724f56d04d4c58080-- --===============7427730255233175069== 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 --===============7427730255233175069==-- From xen-users-bounces@lists.xen.org Sat Feb 02 22:38:41 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sat, 02 Feb 2013 22:38: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 1U1li1-0004ti-TY; Sat, 02 Feb 2013 22:37:17 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U1li0-0004td-PJ for xen-users@lists.xen.org; Sat, 02 Feb 2013 22:37:17 +0000 Received: from [85.158.138.51:8120] by server-6.bemta-3.messagelabs.com id 6A/0D-29959-7159D015; Sat, 02 Feb 2013 22:37:11 +0000 X-Env-Sender: agya.naila@gmail.com X-Msg-Ref: server-12.tower-174.messagelabs.com!1359844630!21853586!1 X-Originating-IP: [209.85.212.175] 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.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 5144 invoked from network); 2 Feb 2013 22:37:10 -0000 Received: from mail-wi0-f175.google.com (HELO mail-wi0-f175.google.com) (209.85.212.175) by server-12.tower-174.messagelabs.com with RC4-SHA encrypted SMTP; 2 Feb 2013 22:37:10 -0000 Received: by mail-wi0-f175.google.com with SMTP id l13so1245260wie.2 for ; Sat, 02 Feb 2013 14:37:10 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:date:message-id:subject:from:to :content-type; bh=8er7A6nTMnT0q5rz+Fmf6P7yEqRq0oB/l8s3GHbvHhI=; b=kq1yT9m4RTAq+S3+NuTQjoG9iOBV07uPxy33ZQpwrIsMrADz3ZKArBAvFHnvaEaEii 9bDrBmJatrRiMeo8DRS3iiq1uGAt4d+1mbmN8P4uNuG+O3gA40QtBC80cwuWIeBBXxO7 0VnX5ZP+rcoiNXcImSrhYlFzpuCzj8xN6CbX+66REgANKf2hJ6QQVdYsxpRsIAunvpj/ sWEtef823FP5SsSVoE4uJFZn5CCOSA4MkJFvrDOnB/0A8QfdzlqVW3HWl4M7RYLgtqyZ ahM+o0+HGSqmcwTwRRU9xrqf7Q5bj7QCsE5shBkv92GyVrKD5ztWf+EJ1kbSWYeoOzmP bV+g== MIME-Version: 1.0 X-Received: by 10.180.102.7 with SMTP id fk7mr3815203wib.27.1359844630394; Sat, 02 Feb 2013 14:37:10 -0800 (PST) Received: by 10.216.236.13 with HTTP; Sat, 2 Feb 2013 14:37:10 -0800 (PST) Date: Sat, 2 Feb 2013 23:37:10 +0100 Message-ID: From: agya naila To: xen-users@lists.xen.org Subject: [Xen-users] Running XEN 4.1 64 bit on Ubuntu desktop without VTx X-BeenThere: xen-users@lists.xen.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="===============7427730255233175069==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============7427730255233175069== Content-Type: multipart/alternative; boundary=f46d0444e7d724f56d04d4c58080 --f46d0444e7d724f56d04d4c58080 Content-Type: text/plain; charset=ISO-8859-1 Dear all, I am quite new in this virtualization area. I am want to do some experiment with live migration using xen. However, I got problem since my server didn't support VTx. I am using Ubuntu desktop 12.04 64 bit with Xen 4.1 Amd64. But when I reload the machine it wont start, since the XEN website its doesn't matter using Paravirtualization without VTx support I dont know what is the problem since I didn't start to install para virtualized guest yet. I juts install the XEN and reload the maschine and its failed. Does any body now the problem and solution, I would appreciate that. Regards, Agya --f46d0444e7d724f56d04d4c58080 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Dear all,

I am quite new in this virtualization area. I = am want to do some experiment with live migration using xen. However, I got= problem since my server didn't support VTx. I am using Ubuntu desktop = 12.04 64 bit with Xen 4.1 Amd64. But when I reload the machine it wont star= t, since the XEN website its doesn't matter using Paravirtualization wi= thout VTx support I dont know what is the problem since I didn't start = to install para virtualized guest yet. I juts install the XEN and reload th= e maschine and its failed. Does any body now the problem and solution, I wo= uld appreciate that.

Regards,

Agya
--f46d0444e7d724f56d04d4c58080-- --===============7427730255233175069== 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 --===============7427730255233175069==-- From xen-users-bounces@lists.xen.org Sat Feb 02 23:33:19 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sat, 02 Feb 2013 23: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 1U1mZA-0005SS-Up; Sat, 02 Feb 2013 23:32:12 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U1mZ9-0005SN-NV for xen-users@lists.xen.org; Sat, 02 Feb 2013 23:32:11 +0000 Received: from [85.158.139.83:50119] by server-5.bemta-5.messagelabs.com id 32/40-11945-AF1AD015; Sat, 02 Feb 2013 23:32:10 +0000 X-Env-Sender: mailinglists.tech@gmail.com X-Msg-Ref: server-3.tower-182.messagelabs.com!1359847929!30595993!1 X-Originating-IP: [74.125.82.175] 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.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 17053 invoked from network); 2 Feb 2013 23:32:10 -0000 Received: from mail-we0-f175.google.com (HELO mail-we0-f175.google.com) (74.125.82.175) by server-3.tower-182.messagelabs.com with RC4-SHA encrypted SMTP; 2 Feb 2013 23:32:10 -0000 Received: by mail-we0-f175.google.com with SMTP id x8so3952695wey.6 for ; Sat, 02 Feb 2013 15:32:09 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=iWTewO0tKHBsA//GoUuY15vNHuAAbqykKUCSmtOpj94=; b=JSDEav0DnZgmsDl5rmu9Q2oBPJjc+/0XSz7Q8UQAdMzg9MpvsB49xgz9abXWgEHLTW C5q1yxxHFggEg2w5Km2B1+h+3FoRIfA3hNGduJ/KYddudgZWLWkcaIUr3PxVzWPbCiAK dXjW5KnFKPuvq0dXXDdUwU18t4rtUP4HUqqCYQ7zICegaRP1xIN042Lcf7bNDz9hMmaG x0F9WuQUfbhVHmKawcQCyKxn6hqm+aZgqdvgl9o1QkQk3DJjXMOgvJCquf7wWNsqVlit zh0W0ctN6oAoxNiXP7UyKuoINwSWSg5e7K2arIFom6XVsMnqfo6H8PUMEcHwi7m1P2Yf IAmw== MIME-Version: 1.0 X-Received: by 10.180.90.147 with SMTP id bw19mr3969448wib.28.1359847929592; Sat, 02 Feb 2013 15:32:09 -0800 (PST) Received: by 10.227.203.18 with HTTP; Sat, 2 Feb 2013 15:32:09 -0800 (PST) In-Reply-To: References: Date: Sun, 3 Feb 2013 00:32:09 +0100 Message-ID: From: tech mailinglists To: agya naila Cc: xen-users Subject: Re: [Xen-users] Running XEN 4.1 64 bit on Ubuntu desktop without VTx X-BeenThere: xen-users@lists.xen.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="===============7951096744308016444==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============7951096744308016444== Content-Type: multipart/alternative; boundary=f46d04389251cabab804d4c6443d --f46d04389251cabab804d4c6443d Content-Type: text/plain; charset=ISO-8859-1 Hello Agya, so normally it shouldn't be a problem to run Xen with Ubuntu Desktop. Do you get any error messages and on which way you installed Xen? Via the package repositorys of Ubuntu or do you compiled it by yourself? Best Regards 2013/2/2 agya naila > Dear all, > > I am quite new in this virtualization area. I am want to do some > experiment with live migration using xen. However, I got problem since my > server didn't support VTx. I am using Ubuntu desktop 12.04 64 bit with Xen > 4.1 Amd64. But when I reload the machine it wont start, since the XEN > website its doesn't matter using Paravirtualization without VTx support I > dont know what is the problem since I didn't start to install para > virtualized guest yet. I juts install the XEN and reload the maschine and > its failed. Does any body now the problem and solution, I would appreciate > that. > > Regards, > > Agya > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xen.org > http://lists.xen.org/xen-users > --f46d04389251cabab804d4c6443d Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Hello Agya,

so normally it shouldn&= #39;t be a problem to run Xen with Ubuntu Desktop. Do you get any error mes= sages and on which way you installed Xen? Via the package repositorys of Ub= untu or do you compiled it by yourself?

Best Regards


2013/2/2 agya naila <agya.naila@gmail.com>
Dear all,

I am quite new = in this virtualization area. I am want to do some experiment with live migr= ation using xen. However, I got problem since my server didn't support = VTx. I am using Ubuntu desktop 12.04 64 bit with Xen 4.1 Amd64. But when I = reload the machine it wont start, since the XEN website its doesn't mat= ter using Paravirtualization without VTx support I dont know what is the pr= oblem since I didn't start to install para virtualized guest yet. I jut= s install the XEN and reload the maschine and its failed. Does any body now= the problem and solution, I would appreciate that.

Regards,

Agya

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

--f46d04389251cabab804d4c6443d-- --===============7951096744308016444== 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 --===============7951096744308016444==-- From xen-users-bounces@lists.xen.org Sat Feb 02 23:33:19 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sat, 02 Feb 2013 23: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 1U1mZA-0005SS-Up; Sat, 02 Feb 2013 23:32:12 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U1mZ9-0005SN-NV for xen-users@lists.xen.org; Sat, 02 Feb 2013 23:32:11 +0000 Received: from [85.158.139.83:50119] by server-5.bemta-5.messagelabs.com id 32/40-11945-AF1AD015; Sat, 02 Feb 2013 23:32:10 +0000 X-Env-Sender: mailinglists.tech@gmail.com X-Msg-Ref: server-3.tower-182.messagelabs.com!1359847929!30595993!1 X-Originating-IP: [74.125.82.175] 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.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 17053 invoked from network); 2 Feb 2013 23:32:10 -0000 Received: from mail-we0-f175.google.com (HELO mail-we0-f175.google.com) (74.125.82.175) by server-3.tower-182.messagelabs.com with RC4-SHA encrypted SMTP; 2 Feb 2013 23:32:10 -0000 Received: by mail-we0-f175.google.com with SMTP id x8so3952695wey.6 for ; Sat, 02 Feb 2013 15:32:09 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=iWTewO0tKHBsA//GoUuY15vNHuAAbqykKUCSmtOpj94=; b=JSDEav0DnZgmsDl5rmu9Q2oBPJjc+/0XSz7Q8UQAdMzg9MpvsB49xgz9abXWgEHLTW C5q1yxxHFggEg2w5Km2B1+h+3FoRIfA3hNGduJ/KYddudgZWLWkcaIUr3PxVzWPbCiAK dXjW5KnFKPuvq0dXXDdUwU18t4rtUP4HUqqCYQ7zICegaRP1xIN042Lcf7bNDz9hMmaG x0F9WuQUfbhVHmKawcQCyKxn6hqm+aZgqdvgl9o1QkQk3DJjXMOgvJCquf7wWNsqVlit zh0W0ctN6oAoxNiXP7UyKuoINwSWSg5e7K2arIFom6XVsMnqfo6H8PUMEcHwi7m1P2Yf IAmw== MIME-Version: 1.0 X-Received: by 10.180.90.147 with SMTP id bw19mr3969448wib.28.1359847929592; Sat, 02 Feb 2013 15:32:09 -0800 (PST) Received: by 10.227.203.18 with HTTP; Sat, 2 Feb 2013 15:32:09 -0800 (PST) In-Reply-To: References: Date: Sun, 3 Feb 2013 00:32:09 +0100 Message-ID: From: tech mailinglists To: agya naila Cc: xen-users Subject: Re: [Xen-users] Running XEN 4.1 64 bit on Ubuntu desktop without VTx X-BeenThere: xen-users@lists.xen.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="===============7951096744308016444==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============7951096744308016444== Content-Type: multipart/alternative; boundary=f46d04389251cabab804d4c6443d --f46d04389251cabab804d4c6443d Content-Type: text/plain; charset=ISO-8859-1 Hello Agya, so normally it shouldn't be a problem to run Xen with Ubuntu Desktop. Do you get any error messages and on which way you installed Xen? Via the package repositorys of Ubuntu or do you compiled it by yourself? Best Regards 2013/2/2 agya naila > Dear all, > > I am quite new in this virtualization area. I am want to do some > experiment with live migration using xen. However, I got problem since my > server didn't support VTx. I am using Ubuntu desktop 12.04 64 bit with Xen > 4.1 Amd64. But when I reload the machine it wont start, since the XEN > website its doesn't matter using Paravirtualization without VTx support I > dont know what is the problem since I didn't start to install para > virtualized guest yet. I juts install the XEN and reload the maschine and > its failed. Does any body now the problem and solution, I would appreciate > that. > > Regards, > > Agya > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xen.org > http://lists.xen.org/xen-users > --f46d04389251cabab804d4c6443d Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Hello Agya,

so normally it shouldn&= #39;t be a problem to run Xen with Ubuntu Desktop. Do you get any error mes= sages and on which way you installed Xen? Via the package repositorys of Ub= untu or do you compiled it by yourself?

Best Regards


2013/2/2 agya naila <agya.naila@gmail.com>
Dear all,

I am quite new = in this virtualization area. I am want to do some experiment with live migr= ation using xen. However, I got problem since my server didn't support = VTx. I am using Ubuntu desktop 12.04 64 bit with Xen 4.1 Amd64. But when I = reload the machine it wont start, since the XEN website its doesn't mat= ter using Paravirtualization without VTx support I dont know what is the pr= oblem since I didn't start to install para virtualized guest yet. I jut= s install the XEN and reload the maschine and its failed. Does any body now= the problem and solution, I would appreciate that.

Regards,

Agya

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

--f46d04389251cabab804d4c6443d-- --===============7951096744308016444== 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 --===============7951096744308016444==-- From xen-users-bounces@lists.xen.org Sun Feb 03 05:02:16 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sun, 03 Feb 2013 05:02: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 1U1rhI-00038U-7K; Sun, 03 Feb 2013 05:00:56 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U1pav-0002OW-Ru for xen-users@lists.xen.org; Sun, 03 Feb 2013 02:46:14 +0000 Received: from [85.158.139.211:41358] by server-14.bemta-5.messagelabs.com id D3/B9-06967-57FCD015; Sun, 03 Feb 2013 02:46:13 +0000 X-Env-Sender: linuxhack2012@gmail.com X-Msg-Ref: server-6.tower-206.messagelabs.com!1359859571!20860366!1 X-Originating-IP: [209.85.216.175] 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.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 15203 invoked from network); 3 Feb 2013 02:46:12 -0000 Received: from mail-qc0-f175.google.com (HELO mail-qc0-f175.google.com) (209.85.216.175) by server-6.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 3 Feb 2013 02:46:12 -0000 Received: by mail-qc0-f175.google.com with SMTP id j3so2286178qcs.34 for ; Sat, 02 Feb 2013 18:46:11 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:date:message-id:subject:from:to :content-type; bh=ukkobLsNL4Qvac63RL+RvOBDH2pnhOmr8RSKKINGGRo=; b=ucJah2iM3T68YS4POF7YawYEh/rR9pNZqa6dRLLma/U+AutfcV8EgiZOxFe+LHkUUs ABaGGNS+IXgd6Bt89Dif16hbB++kSOMeah2gh1ByZcsXfzbf/DoFFvtlvo3iEdgQpFYy XbuvNIMf5td2CRlphPDW1ebyDpQJjAqc1gJkcsb5xhLrbK4BCFVnIhenNVGws++sksE5 jTQuG9pKpvQhFFadKftL3DkcInqG49V/tqBK1eh5QVL9F7V3oYIhNPg+rO4CrrDadNJr jl7bL8HPa/YD3c9i271G6FnrqDmA8vgLz6b6FCQn/Qm10iyOb4Q8HkxeYCpb+MApXeGI w4FQ== MIME-Version: 1.0 X-Received: by 10.224.44.197 with SMTP id b5mr16597979qaf.65.1359859571042; Sat, 02 Feb 2013 18:46:11 -0800 (PST) Received: by 10.49.52.66 with HTTP; Sat, 2 Feb 2013 18:46:10 -0800 (PST) Date: Sun, 3 Feb 2013 08:16:10 +0530 Message-ID: From: Linux Hack To: "xen-users@lists.xen.org" X-Mailman-Approved-At: Sun, 03 Feb 2013 05:00:54 +0000 Subject: [Xen-users] network offloading X-BeenThere: xen-users@lists.xen.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="===============0250733062460918322==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============0250733062460918322== Content-Type: multipart/alternative; boundary=20cf3074ba9cad27d204d4c8facb --20cf3074ba9cad27d204d4c8facb Content-Type: text/plain; charset=ISO-8859-1 Hi, One of my Xen HVM vm is utilized the vcpu completely that I allocated. I found on http://wiki.xen.org/wiki/Network_Throughput_and_Performance_Guide#Offloading_some_network_processing_to_NICswhich giving the solution to enable network offloading. So I want to know is it possible to make it work on Xen on CentOS like on XenServer? And how can I check whether my NIC supports offloading? --20cf3074ba9cad27d204d4c8facb Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Hi,

One of my Xen HVM vm is utili= zed the vcpu completely that I allocated. I found on=A0http://wiki.xen.org/wiki/Network_Throughput_and_P= erformance_Guide#Offloading_some_network_processing_to_NICs which givin= g the solution to enable network offloading.

So I want to know is it possible to make it= work on Xen on CentOS like on XenServer?=A0

And how can I check whether my NIC supports offloading?

--20cf3074ba9cad27d204d4c8facb-- --===============0250733062460918322== 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 --===============0250733062460918322==-- From xen-users-bounces@lists.xen.org Sun Feb 03 05:02:16 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sun, 03 Feb 2013 05:02: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 1U1rhH-00038L-Kg; Sun, 03 Feb 2013 05:00:55 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U1ozU-0002In-Jk for xen-users@lists.xen.org; Sun, 03 Feb 2013 02:07:32 +0000 Received: from [85.158.137.99:61646] by server-15.bemta-3.messagelabs.com id 9D/0B-25405-366CD015; Sun, 03 Feb 2013 02:07:31 +0000 X-Env-Sender: ydev@cs.utah.edu X-Msg-Ref: server-3.tower-217.messagelabs.com!1359857250!12793274!1 X-Originating-IP: [155.98.64.241] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 27058 invoked from network); 3 Feb 2013 02:07:30 -0000 Received: from rio.cs.utah.edu (HELO mail-svr1.cs.utah.edu) (155.98.64.241) by server-3.tower-217.messagelabs.com with SMTP; 3 Feb 2013 02:07:30 -0000 Received: from localhost (localhost [127.0.0.1]) by mail-svr1.cs.utah.edu (Postfix) with ESMTP id 525196500C8 for ; Sat, 2 Feb 2013 19:07:29 -0700 (MST) X-Virus-Scanned: amavisd-new at cs.utah.edu Received: from mail-svr1.cs.utah.edu ([127.0.0.1]) by localhost (mail-svr1.cs.utah.edu [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1y6bus2vjoJt; Sat, 2 Feb 2013 19:07:28 -0700 (MST) Received: from [192.168.1.12] (c-76-23-15-81.hsd1.ut.comcast.net [76.23.15.81]) by smtps.cs.utah.edu (Postfix) with ESMTPSA id 624386500C3; Sat, 2 Feb 2013 19:07:28 -0700 (MST) Message-ID: <510DC655.5060205@cs.utah.edu> Date: Sat, 02 Feb 2013 19:07:17 -0700 From: Yathindra User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130107 Thunderbird/17.0.2 MIME-Version: 1.0 To: "xen-users@lists.xen.org" X-Mailman-Approved-At: Sun, 03 Feb 2013 05:00:54 +0000 Cc: Yathindra Naik Subject: [Xen-users] xen_blkbk times out before getting connected X-BeenThere: xen-users@lists.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, When ever I start a guest domain, backend driver times out since state is not being connected. How do we debug such issues ? I instrumented the backend drivers, specifically xen/xenbus/xenbus_probe.c and xen/xenbus/xenbus_probe_backend.c to see if the backend fails to probe the device. But I never saw any of the messages I added in syslog or dmesg. I'm stuck on this problem for weeks now. I'm not understanding why the backend fails to switch the state. Heres the libxl log: libxl: debug: libxl_device.c:313:libxl__device_disk_set_backend: Disk vdev=sda1 spec.backend=unknown libxl: debug: libxl_device.c:349:libxl__device_disk_set_backend: Disk vdev=sda1, using backend phy libxl: debug: libxl_create.c:821:initiate_domain_create: running bootloader libxl: debug: libxl_bootloader.c:327:libxl__bootloader_run: no bootloader configured, using user supplied kernel libxl: debug: libxl_event.c:561:libxl__ev_xswatch_deregister: watch w=0xc3a5e0: deregister unregistered libxl: debug: libxl_numa.c:435:libxl__get_numa_candidate: New best NUMA placement candidate found: nr_nodes=1, nr_cpus=2, nr_vcpus=3, free_memkb=997 libxl: detail: libxl_dom.c:192:numa_place_domain: NUMA placement candidate with 1 nodes, 2 cpus and 997 KB free selected domainbuilder: detail: xc_dom_allocate: cmdline="root=/dev/disk/by-path/xen-vbd-2049 ro xencons=tty", features="(null)" libxl: debug: libxl_dom.c:393:libxl__build_pv: pv kernel mapped 0 path /boot/vmlinuz-3.2.16 ... ... libxl: debug: libxl_event.c:512:libxl__ev_xswatch_register: watch w=0xc3bd98 wpath=/local/domain/0/backend/vbd/1/2049/state token=3/0: register slotnum=3 libxl: debug: libxl_create.c:1330:do_domain_create: ao 0xc39880: inprogress: poller=0xc398e0, flags=i libxl: debug: libxl_event.c:457:watchfd_callback: watch w=0xc3bd98 wpath=/local/domain/0/backend/vbd/1/2049/state token=3/0: event epath=/local/domain/0/backend/vbd/1/2049/state libxl: debug: libxl_event.c:600:devstate_watch_callback: backend /local/domain/0/backend/vbd/1/2049/state wanted state 2 still waiting state 1 libxl: debug: libxl_event.c:614:devstate_timeout: backend /local/domain/0/backend/vbd/1/2049/state wanted state 2 timed out libxl: debug: libxl_event.c:549:libxl__ev_xswatch_deregister: watch w=0xc3bd98 wpath=/local/domain/0/backend/vbd/1/2049/state token=3/0: deregister slotnum=3 libxl: debug: libxl_event.c:561:libxl__ev_xswatch_deregister: watch w=0xc3bd98: deregister unregistered libxl: error: libxl_device.c:943:device_backend_callback: unable to connect device with path /local/domain/0/backend/vbd/1/2049 libxl: error: libxl_create.c:1077:domcreate_launch_dm: unable to add disk devices libxl: debug: libxl_event.c:512:libxl__ev_xswatch_register: watch w=0xc3d868 wpath=/local/domain/0/backend/vbd/1/2049/state token=3/1: register slotnum=3 libxl: debug: libxl_event.c:457:watchfd_callback: watch w=0xc3d868 wpath=/local/domain/0/backend/vbd/1/2049/state token=3/1: event epath=/local/domain/0/backend/vbd/1/2049/state libxl: debug: libxl_event.c:600:devstate_watch_callback: backend /local/domain/0/backend/vbd/1/2049/state wanted state 6 still waiting state 5 libxl: debug: libxl_event.c:614:devstate_timeout: backend /local/domain/0/backend/vbd/1/2049/state wanted state 6 timed out libxl: debug: libxl_event.c:549:libxl__ev_xswatch_deregister: watch w=0xc3d868 wpath=/local/domain/0/backend/vbd/1/2049/state token=3/1: deregister slotnum=3 libxl: debug: libxl_event.c:561:libxl__ev_xswatch_deregister: watch w=0xc3d868: deregister unregistered libxl: error: libxl_device.c:943:device_backend_callback: unable to disconnect device with path /local/domain/0/backend/vbd/1/2049 libxl: error: libxl.c:1725:devices_destroy_cb: libxl__devices_destroy failed for 1 libxl: debug: libxl_event.c:1497:libxl__ao_complete: ao 0xc39880: complete, rc=-3 libxl: debug: libxl_event.c:1469:libxl__ao__destroy: ao 0xc39880: destroy xc: debug: hypercall buffer: total allocations:366 total releases:366 xc: debug: hypercall buffer: current allocations:0 maximum allocations:4 xc: debug: hypercall buffer: cache current size:4 xc: debug: hypercall buffer: cache hits:356 misses:4 toobig:6 Thanks, Yathi _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Sun Feb 03 05:02:16 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sun, 03 Feb 2013 05:02: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 1U1rhH-00038L-Kg; Sun, 03 Feb 2013 05:00:55 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U1ozU-0002In-Jk for xen-users@lists.xen.org; Sun, 03 Feb 2013 02:07:32 +0000 Received: from [85.158.137.99:61646] by server-15.bemta-3.messagelabs.com id 9D/0B-25405-366CD015; Sun, 03 Feb 2013 02:07:31 +0000 X-Env-Sender: ydev@cs.utah.edu X-Msg-Ref: server-3.tower-217.messagelabs.com!1359857250!12793274!1 X-Originating-IP: [155.98.64.241] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 27058 invoked from network); 3 Feb 2013 02:07:30 -0000 Received: from rio.cs.utah.edu (HELO mail-svr1.cs.utah.edu) (155.98.64.241) by server-3.tower-217.messagelabs.com with SMTP; 3 Feb 2013 02:07:30 -0000 Received: from localhost (localhost [127.0.0.1]) by mail-svr1.cs.utah.edu (Postfix) with ESMTP id 525196500C8 for ; Sat, 2 Feb 2013 19:07:29 -0700 (MST) X-Virus-Scanned: amavisd-new at cs.utah.edu Received: from mail-svr1.cs.utah.edu ([127.0.0.1]) by localhost (mail-svr1.cs.utah.edu [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1y6bus2vjoJt; Sat, 2 Feb 2013 19:07:28 -0700 (MST) Received: from [192.168.1.12] (c-76-23-15-81.hsd1.ut.comcast.net [76.23.15.81]) by smtps.cs.utah.edu (Postfix) with ESMTPSA id 624386500C3; Sat, 2 Feb 2013 19:07:28 -0700 (MST) Message-ID: <510DC655.5060205@cs.utah.edu> Date: Sat, 02 Feb 2013 19:07:17 -0700 From: Yathindra User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130107 Thunderbird/17.0.2 MIME-Version: 1.0 To: "xen-users@lists.xen.org" X-Mailman-Approved-At: Sun, 03 Feb 2013 05:00:54 +0000 Cc: Yathindra Naik Subject: [Xen-users] xen_blkbk times out before getting connected X-BeenThere: xen-users@lists.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, When ever I start a guest domain, backend driver times out since state is not being connected. How do we debug such issues ? I instrumented the backend drivers, specifically xen/xenbus/xenbus_probe.c and xen/xenbus/xenbus_probe_backend.c to see if the backend fails to probe the device. But I never saw any of the messages I added in syslog or dmesg. I'm stuck on this problem for weeks now. I'm not understanding why the backend fails to switch the state. Heres the libxl log: libxl: debug: libxl_device.c:313:libxl__device_disk_set_backend: Disk vdev=sda1 spec.backend=unknown libxl: debug: libxl_device.c:349:libxl__device_disk_set_backend: Disk vdev=sda1, using backend phy libxl: debug: libxl_create.c:821:initiate_domain_create: running bootloader libxl: debug: libxl_bootloader.c:327:libxl__bootloader_run: no bootloader configured, using user supplied kernel libxl: debug: libxl_event.c:561:libxl__ev_xswatch_deregister: watch w=0xc3a5e0: deregister unregistered libxl: debug: libxl_numa.c:435:libxl__get_numa_candidate: New best NUMA placement candidate found: nr_nodes=1, nr_cpus=2, nr_vcpus=3, free_memkb=997 libxl: detail: libxl_dom.c:192:numa_place_domain: NUMA placement candidate with 1 nodes, 2 cpus and 997 KB free selected domainbuilder: detail: xc_dom_allocate: cmdline="root=/dev/disk/by-path/xen-vbd-2049 ro xencons=tty", features="(null)" libxl: debug: libxl_dom.c:393:libxl__build_pv: pv kernel mapped 0 path /boot/vmlinuz-3.2.16 ... ... libxl: debug: libxl_event.c:512:libxl__ev_xswatch_register: watch w=0xc3bd98 wpath=/local/domain/0/backend/vbd/1/2049/state token=3/0: register slotnum=3 libxl: debug: libxl_create.c:1330:do_domain_create: ao 0xc39880: inprogress: poller=0xc398e0, flags=i libxl: debug: libxl_event.c:457:watchfd_callback: watch w=0xc3bd98 wpath=/local/domain/0/backend/vbd/1/2049/state token=3/0: event epath=/local/domain/0/backend/vbd/1/2049/state libxl: debug: libxl_event.c:600:devstate_watch_callback: backend /local/domain/0/backend/vbd/1/2049/state wanted state 2 still waiting state 1 libxl: debug: libxl_event.c:614:devstate_timeout: backend /local/domain/0/backend/vbd/1/2049/state wanted state 2 timed out libxl: debug: libxl_event.c:549:libxl__ev_xswatch_deregister: watch w=0xc3bd98 wpath=/local/domain/0/backend/vbd/1/2049/state token=3/0: deregister slotnum=3 libxl: debug: libxl_event.c:561:libxl__ev_xswatch_deregister: watch w=0xc3bd98: deregister unregistered libxl: error: libxl_device.c:943:device_backend_callback: unable to connect device with path /local/domain/0/backend/vbd/1/2049 libxl: error: libxl_create.c:1077:domcreate_launch_dm: unable to add disk devices libxl: debug: libxl_event.c:512:libxl__ev_xswatch_register: watch w=0xc3d868 wpath=/local/domain/0/backend/vbd/1/2049/state token=3/1: register slotnum=3 libxl: debug: libxl_event.c:457:watchfd_callback: watch w=0xc3d868 wpath=/local/domain/0/backend/vbd/1/2049/state token=3/1: event epath=/local/domain/0/backend/vbd/1/2049/state libxl: debug: libxl_event.c:600:devstate_watch_callback: backend /local/domain/0/backend/vbd/1/2049/state wanted state 6 still waiting state 5 libxl: debug: libxl_event.c:614:devstate_timeout: backend /local/domain/0/backend/vbd/1/2049/state wanted state 6 timed out libxl: debug: libxl_event.c:549:libxl__ev_xswatch_deregister: watch w=0xc3d868 wpath=/local/domain/0/backend/vbd/1/2049/state token=3/1: deregister slotnum=3 libxl: debug: libxl_event.c:561:libxl__ev_xswatch_deregister: watch w=0xc3d868: deregister unregistered libxl: error: libxl_device.c:943:device_backend_callback: unable to disconnect device with path /local/domain/0/backend/vbd/1/2049 libxl: error: libxl.c:1725:devices_destroy_cb: libxl__devices_destroy failed for 1 libxl: debug: libxl_event.c:1497:libxl__ao_complete: ao 0xc39880: complete, rc=-3 libxl: debug: libxl_event.c:1469:libxl__ao__destroy: ao 0xc39880: destroy xc: debug: hypercall buffer: total allocations:366 total releases:366 xc: debug: hypercall buffer: current allocations:0 maximum allocations:4 xc: debug: hypercall buffer: cache current size:4 xc: debug: hypercall buffer: cache hits:356 misses:4 toobig:6 Thanks, Yathi _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Sun Feb 03 05:02:16 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sun, 03 Feb 2013 05:02: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 1U1rhI-00038U-7K; Sun, 03 Feb 2013 05:00:56 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U1pav-0002OW-Ru for xen-users@lists.xen.org; Sun, 03 Feb 2013 02:46:14 +0000 Received: from [85.158.139.211:41358] by server-14.bemta-5.messagelabs.com id D3/B9-06967-57FCD015; Sun, 03 Feb 2013 02:46:13 +0000 X-Env-Sender: linuxhack2012@gmail.com X-Msg-Ref: server-6.tower-206.messagelabs.com!1359859571!20860366!1 X-Originating-IP: [209.85.216.175] 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.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 15203 invoked from network); 3 Feb 2013 02:46:12 -0000 Received: from mail-qc0-f175.google.com (HELO mail-qc0-f175.google.com) (209.85.216.175) by server-6.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 3 Feb 2013 02:46:12 -0000 Received: by mail-qc0-f175.google.com with SMTP id j3so2286178qcs.34 for ; Sat, 02 Feb 2013 18:46:11 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:date:message-id:subject:from:to :content-type; bh=ukkobLsNL4Qvac63RL+RvOBDH2pnhOmr8RSKKINGGRo=; b=ucJah2iM3T68YS4POF7YawYEh/rR9pNZqa6dRLLma/U+AutfcV8EgiZOxFe+LHkUUs ABaGGNS+IXgd6Bt89Dif16hbB++kSOMeah2gh1ByZcsXfzbf/DoFFvtlvo3iEdgQpFYy XbuvNIMf5td2CRlphPDW1ebyDpQJjAqc1gJkcsb5xhLrbK4BCFVnIhenNVGws++sksE5 jTQuG9pKpvQhFFadKftL3DkcInqG49V/tqBK1eh5QVL9F7V3oYIhNPg+rO4CrrDadNJr jl7bL8HPa/YD3c9i271G6FnrqDmA8vgLz6b6FCQn/Qm10iyOb4Q8HkxeYCpb+MApXeGI w4FQ== MIME-Version: 1.0 X-Received: by 10.224.44.197 with SMTP id b5mr16597979qaf.65.1359859571042; Sat, 02 Feb 2013 18:46:11 -0800 (PST) Received: by 10.49.52.66 with HTTP; Sat, 2 Feb 2013 18:46:10 -0800 (PST) Date: Sun, 3 Feb 2013 08:16:10 +0530 Message-ID: From: Linux Hack To: "xen-users@lists.xen.org" X-Mailman-Approved-At: Sun, 03 Feb 2013 05:00:54 +0000 Subject: [Xen-users] network offloading X-BeenThere: xen-users@lists.xen.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="===============0250733062460918322==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============0250733062460918322== Content-Type: multipart/alternative; boundary=20cf3074ba9cad27d204d4c8facb --20cf3074ba9cad27d204d4c8facb Content-Type: text/plain; charset=ISO-8859-1 Hi, One of my Xen HVM vm is utilized the vcpu completely that I allocated. I found on http://wiki.xen.org/wiki/Network_Throughput_and_Performance_Guide#Offloading_some_network_processing_to_NICswhich giving the solution to enable network offloading. So I want to know is it possible to make it work on Xen on CentOS like on XenServer? And how can I check whether my NIC supports offloading? --20cf3074ba9cad27d204d4c8facb Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Hi,

One of my Xen HVM vm is utili= zed the vcpu completely that I allocated. I found on=A0http://wiki.xen.org/wiki/Network_Throughput_and_P= erformance_Guide#Offloading_some_network_processing_to_NICs which givin= g the solution to enable network offloading.

So I want to know is it possible to make it= work on Xen on CentOS like on XenServer?=A0

And how can I check whether my NIC supports offloading?

--20cf3074ba9cad27d204d4c8facb-- --===============0250733062460918322== 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 --===============0250733062460918322==-- From xen-users-bounces@lists.xen.org Sun Feb 03 05:02:17 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sun, 03 Feb 2013 05:02: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 1U1rhI-00038d-R5; Sun, 03 Feb 2013 05:00:56 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U1pr7-0002Sb-SM for xen-users@lists.xen.org; Sun, 03 Feb 2013 03:02:58 +0000 Received: from [85.158.138.51:23814] by server-9.bemta-3.messagelabs.com id 81/37-09484-063DD015; Sun, 03 Feb 2013 03:02:56 +0000 X-Env-Sender: linuxhack2012@gmail.com X-Msg-Ref: server-11.tower-174.messagelabs.com!1359860575!30716751!1 X-Originating-IP: [209.85.128.51] 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.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 5465 invoked from network); 3 Feb 2013 03:02:56 -0000 Received: from mail-qe0-f51.google.com (HELO mail-qe0-f51.google.com) (209.85.128.51) by server-11.tower-174.messagelabs.com with RC4-SHA encrypted SMTP; 3 Feb 2013 03:02:56 -0000 Received: by mail-qe0-f51.google.com with SMTP id 6so2393730qea.38 for ; Sat, 02 Feb 2013 19:02:55 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:date:message-id:subject:from:to :content-type; bh=N86ipnQZtTTEhzOShEbyIGmUAW+VfEa4ZOxqoUTK4WM=; b=nOgjivvXePt/lSyo/69qfnj3ywR5MkBlyVrB3b5l42/DqPffSVSNlIw8IBIKVgqaTt rHmtogbviDBzHNUDQ5Kmntn8KvHn7hFwMpHENlnOB+Azr0HGKHxvGwnQZ09qh7+A5L1i vxy2Wx7gcKPWrUPESM+eOuUqQu3EutrL8uKtXtTY+4CC8+RSKc493xi9JoLo3LqUjEWX dSoD7Mfxd7G7EMl6XP9cLnpajp2t0Z/eLDUlNy51+VlmHE7nSyB73pfu5aLlRkVmz1n/ F3h423+GVHLN7Zdym0DLTaX/pA0hGVXlm6dvyCRPI6CnPOzwRaJaCu1fjSMRIpwPnHUm QcOA== MIME-Version: 1.0 X-Received: by 10.224.31.16 with SMTP id w16mr16196823qac.52.1359860574942; Sat, 02 Feb 2013 19:02:54 -0800 (PST) Received: by 10.49.52.66 with HTTP; Sat, 2 Feb 2013 19:02:54 -0800 (PST) Date: Sun, 3 Feb 2013 08:32:54 +0530 Message-ID: From: Linux Hack To: "xen-users@lists.xen.org" X-Mailman-Approved-At: Sun, 03 Feb 2013 05:00:54 +0000 Subject: [Xen-users] I/O Scheduler X-BeenThere: xen-users@lists.xen.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="===============7211022375186649059==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============7211022375186649059== Content-Type: multipart/alternative; boundary=20cf3074b4568375d104d4c936a7 --20cf3074b4568375d104d4c936a7 Content-Type: text/plain; charset=ISO-8859-1 Hi, I noticed on one of the discussion that both Dom0 and DomU have the same scheduler will cause I/O issues and changing the I/O scheduler to noop for Xen VPS will give better performance. Is it correct? If its correct then how can we set the default I/O scheduler as noop for Xen VM's without getting inside of them? I mean is there any option that we can declare on DomU config itself? --20cf3074b4568375d104d4c936a7 Content-Type: text/html; charset=ISO-8859-1
Hi,

I noticed on one of the discussion that both Dom0 and DomU have the same scheduler will cause I/O issues and changing the I/O scheduler to noop for Xen VPS will give better performance. Is it correct?

If its correct then how can we set the default I/O scheduler as noop for Xen VM's without getting inside of them? I mean is there any option that we can declare on DomU config itself?

--20cf3074b4568375d104d4c936a7-- --===============7211022375186649059== 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 --===============7211022375186649059==-- From xen-users-bounces@lists.xen.org Sun Feb 03 05:02:17 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sun, 03 Feb 2013 05:02: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 1U1rhI-00038d-R5; Sun, 03 Feb 2013 05:00:56 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U1pr7-0002Sb-SM for xen-users@lists.xen.org; Sun, 03 Feb 2013 03:02:58 +0000 Received: from [85.158.138.51:23814] by server-9.bemta-3.messagelabs.com id 81/37-09484-063DD015; Sun, 03 Feb 2013 03:02:56 +0000 X-Env-Sender: linuxhack2012@gmail.com X-Msg-Ref: server-11.tower-174.messagelabs.com!1359860575!30716751!1 X-Originating-IP: [209.85.128.51] 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.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 5465 invoked from network); 3 Feb 2013 03:02:56 -0000 Received: from mail-qe0-f51.google.com (HELO mail-qe0-f51.google.com) (209.85.128.51) by server-11.tower-174.messagelabs.com with RC4-SHA encrypted SMTP; 3 Feb 2013 03:02:56 -0000 Received: by mail-qe0-f51.google.com with SMTP id 6so2393730qea.38 for ; Sat, 02 Feb 2013 19:02:55 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:date:message-id:subject:from:to :content-type; bh=N86ipnQZtTTEhzOShEbyIGmUAW+VfEa4ZOxqoUTK4WM=; b=nOgjivvXePt/lSyo/69qfnj3ywR5MkBlyVrB3b5l42/DqPffSVSNlIw8IBIKVgqaTt rHmtogbviDBzHNUDQ5Kmntn8KvHn7hFwMpHENlnOB+Azr0HGKHxvGwnQZ09qh7+A5L1i vxy2Wx7gcKPWrUPESM+eOuUqQu3EutrL8uKtXtTY+4CC8+RSKc493xi9JoLo3LqUjEWX dSoD7Mfxd7G7EMl6XP9cLnpajp2t0Z/eLDUlNy51+VlmHE7nSyB73pfu5aLlRkVmz1n/ F3h423+GVHLN7Zdym0DLTaX/pA0hGVXlm6dvyCRPI6CnPOzwRaJaCu1fjSMRIpwPnHUm QcOA== MIME-Version: 1.0 X-Received: by 10.224.31.16 with SMTP id w16mr16196823qac.52.1359860574942; Sat, 02 Feb 2013 19:02:54 -0800 (PST) Received: by 10.49.52.66 with HTTP; Sat, 2 Feb 2013 19:02:54 -0800 (PST) Date: Sun, 3 Feb 2013 08:32:54 +0530 Message-ID: From: Linux Hack To: "xen-users@lists.xen.org" X-Mailman-Approved-At: Sun, 03 Feb 2013 05:00:54 +0000 Subject: [Xen-users] I/O Scheduler X-BeenThere: xen-users@lists.xen.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="===============7211022375186649059==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============7211022375186649059== Content-Type: multipart/alternative; boundary=20cf3074b4568375d104d4c936a7 --20cf3074b4568375d104d4c936a7 Content-Type: text/plain; charset=ISO-8859-1 Hi, I noticed on one of the discussion that both Dom0 and DomU have the same scheduler will cause I/O issues and changing the I/O scheduler to noop for Xen VPS will give better performance. Is it correct? If its correct then how can we set the default I/O scheduler as noop for Xen VM's without getting inside of them? I mean is there any option that we can declare on DomU config itself? --20cf3074b4568375d104d4c936a7 Content-Type: text/html; charset=ISO-8859-1
Hi,

I noticed on one of the discussion that both Dom0 and DomU have the same scheduler will cause I/O issues and changing the I/O scheduler to noop for Xen VPS will give better performance. Is it correct?

If its correct then how can we set the default I/O scheduler as noop for Xen VM's without getting inside of them? I mean is there any option that we can declare on DomU config itself?

--20cf3074b4568375d104d4c936a7-- --===============7211022375186649059== 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 --===============7211022375186649059==-- From xen-users-bounces@lists.xen.org Sun Feb 03 07:05:12 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sun, 03 Feb 2013 07:05: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 1U1tcN-0004gM-3w; Sun, 03 Feb 2013 07:03:59 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U1tcK-0004gH-JY for xen-users@lists.xen.org; Sun, 03 Feb 2013 07:03:56 +0000 Received: from [193.109.254.147:22879] by server-11.bemta-14.messagelabs.com id ED/54-30685-BDB0E015; Sun, 03 Feb 2013 07:03:55 +0000 X-Env-Sender: herydians@gmail.com X-Msg-Ref: server-9.tower-27.messagelabs.com!1359875033!9371090!1 X-Originating-IP: [209.85.214.177] 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.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 1654 invoked from network); 3 Feb 2013 07:03:54 -0000 Received: from mail-ob0-f177.google.com (HELO mail-ob0-f177.google.com) (209.85.214.177) by server-9.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 3 Feb 2013 07:03:54 -0000 Received: by mail-ob0-f177.google.com with SMTP id wc18so5472411obb.36 for ; Sat, 02 Feb 2013 23:03:53 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=rUBp6ARAc0L46bKQPOUz4xE3fJAWfQKZLaKgTNWgLPo=; b=tM21FQUn0R1wsglYGYo+skM7UJYXBocuM/HfmctUJVvk0L6Mk1dG1I5tPgDxhroAL9 EXI/Pz/pqht0n4a/4QVaoQqFW6xsjK621vknnlFSJCfSrozAlyCCq3I9QGdNPaksjKi9 W22/rhL0CdmO2HEXyeXw3dekNHNxYAyRZ3eJA/+z3YQKyS3qCv9ywO0SbHuwk2XNigJN VZpzipS63EBCuFZH9dxh4yJfPNeNIGkI9Htcvxeggn0WuPWXIKc+z6IudtjiwxhSZbdx BJWqfIKwWGgnVj72dSmwJ+5+LczYJFDcAcQ4bnVSYC6s71XVtRUblvBBrtsQoHCsIqXU Lt8w== MIME-Version: 1.0 X-Received: by 10.182.112.34 with SMTP id in2mr12752884obb.80.1359875033028; Sat, 02 Feb 2013 23:03:53 -0800 (PST) Received: by 10.182.169.102 with HTTP; Sat, 2 Feb 2013 23:03:52 -0800 (PST) In-Reply-To: References: Date: Sun, 3 Feb 2013 08:03:52 +0100 Message-ID: From: Hery Dian Septama To: tech mailinglists Cc: xen-users , agya naila Subject: Re: [Xen-users] Running XEN 4.1 64 bit on Ubuntu desktop without VTx X-BeenThere: xen-users@lists.xen.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="===============5518082920531786851==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============5518082920531786851== Content-Type: multipart/alternative; boundary=14dae93998934857de04d4cc94b5 --14dae93998934857de04d4cc94b5 Content-Type: text/plain; charset=UTF-8 Hi, I tried to installed it using step that given by https://help.ubuntu.com/community/XenProposed, using ubuntu repository. When I try it on my Laptop with VTx support its running perfectly even when I installed DomU. However, when I tried to installed on my server IBM Blade server Intel Xeon 3,2 Ghz, I know that this server series didn't have VTx support. After installed the XEN and reboot the machine as tutorial told my server won't running, it keep restarting. As I saw, it's can boot to Xen and after try to reloading configuration its fail, so my server restarting over and over. Since the message was running fast on my screen I can't see the message clearly but the first line said that hardware acceleration disabled or something. Since there is no VTx, firstly I assumed that its because the VTx. But, it should run I guess because the XEN website said it so. Regards, Agya On Sun, Feb 3, 2013 at 12:32 AM, tech mailinglists < mailinglists.tech@gmail.com> wrote: > Hello Agya, > > so normally it shouldn't be a problem to run Xen with Ubuntu Desktop. Do > you get any error messages and on which way you installed Xen? Via the > package repositorys of Ubuntu or do you compiled it by yourself? > > Best Regards > > > 2013/2/2 agya naila > >> Dear all, >> >> I am quite new in this virtualization area. I am want to do some >> experiment with live migration using xen. However, I got problem since my >> server didn't support VTx. I am using Ubuntu desktop 12.04 64 bit with Xen >> 4.1 Amd64. But when I reload the machine it wont start, since the XEN >> website its doesn't matter using Paravirtualization without VTx support I >> dont know what is the problem since I didn't start to install para >> virtualized guest yet. I juts install the XEN and reload the maschine and >> its failed. Does any body now the problem and solution, I would appreciate >> that. >> >> Regards, >> >> Agya >> >> _______________________________________________ >> 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 > --14dae93998934857de04d4cc94b5 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Hi,

I tried to installed it using step that given by=C2= =A0https://help.u= buntu.com/community/XenProposed, using ubuntu repository. When I try it= on my Laptop with VTx support its running perfectly even when I installed = DomU. However, when I tried to installed on my server IBM Blade server Inte= l Xeon 3,2 Ghz, I know that this server series didn't have VTx support.= After installed the XEN and reboot the machine as tutorial told my server = won't running, it keep restarting.


As I saw, it's can boot to Xen and a= fter try to reloading configuration its fail, so my server restarting over = and over. Since the message was running fast on my screen I can't see t= he message clearly but the first line said that hardware acceleration disab= led or something. Since there is no VTx, firstly I assumed that its because= the VTx. But, it should run I guess because the XEN website said it so.


Regards,

Agya


On Sun, Feb 3, 2013 at 12:32 AM= , tech mailinglists <mailinglists.tech@gmail.com> = wrote:
Hello Agya,
so normally it shouldn't be a problem to run Xen with Ubuntu De= sktop. Do you get any error messages and on which way you installed Xen? Vi= a the package repositorys of Ubuntu or do you compiled it by yourself?

Best Regards


2013/2/2 agya naila <agya.naila@gmail.com>
Dear all,

I am quite new in this virtualization area. I am want to do some ex= periment with live migration using xen. However, I got problem since my ser= ver didn't support VTx. I am using Ubuntu desktop 12.04 64 bit with Xen= 4.1 Amd64. But when I reload the machine it wont start, since the XEN webs= ite its doesn't matter using Paravirtualization without VTx support I d= ont know what is the problem since I didn't start to install para virtu= alized guest yet. I juts install the XEN and reload the maschine and its fa= iled. Does any body now the problem and solution, I would appreciate that.<= /div>

Regards,

Agya

_______________________________________________
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

--14dae93998934857de04d4cc94b5-- --===============5518082920531786851== 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 --===============5518082920531786851==-- From xen-users-bounces@lists.xen.org Sun Feb 03 07:05:12 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sun, 03 Feb 2013 07:05: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 1U1tcN-0004gM-3w; Sun, 03 Feb 2013 07:03:59 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U1tcK-0004gH-JY for xen-users@lists.xen.org; Sun, 03 Feb 2013 07:03:56 +0000 Received: from [193.109.254.147:22879] by server-11.bemta-14.messagelabs.com id ED/54-30685-BDB0E015; Sun, 03 Feb 2013 07:03:55 +0000 X-Env-Sender: herydians@gmail.com X-Msg-Ref: server-9.tower-27.messagelabs.com!1359875033!9371090!1 X-Originating-IP: [209.85.214.177] 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.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 1654 invoked from network); 3 Feb 2013 07:03:54 -0000 Received: from mail-ob0-f177.google.com (HELO mail-ob0-f177.google.com) (209.85.214.177) by server-9.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 3 Feb 2013 07:03:54 -0000 Received: by mail-ob0-f177.google.com with SMTP id wc18so5472411obb.36 for ; Sat, 02 Feb 2013 23:03:53 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=rUBp6ARAc0L46bKQPOUz4xE3fJAWfQKZLaKgTNWgLPo=; b=tM21FQUn0R1wsglYGYo+skM7UJYXBocuM/HfmctUJVvk0L6Mk1dG1I5tPgDxhroAL9 EXI/Pz/pqht0n4a/4QVaoQqFW6xsjK621vknnlFSJCfSrozAlyCCq3I9QGdNPaksjKi9 W22/rhL0CdmO2HEXyeXw3dekNHNxYAyRZ3eJA/+z3YQKyS3qCv9ywO0SbHuwk2XNigJN VZpzipS63EBCuFZH9dxh4yJfPNeNIGkI9Htcvxeggn0WuPWXIKc+z6IudtjiwxhSZbdx BJWqfIKwWGgnVj72dSmwJ+5+LczYJFDcAcQ4bnVSYC6s71XVtRUblvBBrtsQoHCsIqXU Lt8w== MIME-Version: 1.0 X-Received: by 10.182.112.34 with SMTP id in2mr12752884obb.80.1359875033028; Sat, 02 Feb 2013 23:03:53 -0800 (PST) Received: by 10.182.169.102 with HTTP; Sat, 2 Feb 2013 23:03:52 -0800 (PST) In-Reply-To: References: Date: Sun, 3 Feb 2013 08:03:52 +0100 Message-ID: From: Hery Dian Septama To: tech mailinglists Cc: xen-users , agya naila Subject: Re: [Xen-users] Running XEN 4.1 64 bit on Ubuntu desktop without VTx X-BeenThere: xen-users@lists.xen.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="===============5518082920531786851==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============5518082920531786851== Content-Type: multipart/alternative; boundary=14dae93998934857de04d4cc94b5 --14dae93998934857de04d4cc94b5 Content-Type: text/plain; charset=UTF-8 Hi, I tried to installed it using step that given by https://help.ubuntu.com/community/XenProposed, using ubuntu repository. When I try it on my Laptop with VTx support its running perfectly even when I installed DomU. However, when I tried to installed on my server IBM Blade server Intel Xeon 3,2 Ghz, I know that this server series didn't have VTx support. After installed the XEN and reboot the machine as tutorial told my server won't running, it keep restarting. As I saw, it's can boot to Xen and after try to reloading configuration its fail, so my server restarting over and over. Since the message was running fast on my screen I can't see the message clearly but the first line said that hardware acceleration disabled or something. Since there is no VTx, firstly I assumed that its because the VTx. But, it should run I guess because the XEN website said it so. Regards, Agya On Sun, Feb 3, 2013 at 12:32 AM, tech mailinglists < mailinglists.tech@gmail.com> wrote: > Hello Agya, > > so normally it shouldn't be a problem to run Xen with Ubuntu Desktop. Do > you get any error messages and on which way you installed Xen? Via the > package repositorys of Ubuntu or do you compiled it by yourself? > > Best Regards > > > 2013/2/2 agya naila > >> Dear all, >> >> I am quite new in this virtualization area. I am want to do some >> experiment with live migration using xen. However, I got problem since my >> server didn't support VTx. I am using Ubuntu desktop 12.04 64 bit with Xen >> 4.1 Amd64. But when I reload the machine it wont start, since the XEN >> website its doesn't matter using Paravirtualization without VTx support I >> dont know what is the problem since I didn't start to install para >> virtualized guest yet. I juts install the XEN and reload the maschine and >> its failed. Does any body now the problem and solution, I would appreciate >> that. >> >> Regards, >> >> Agya >> >> _______________________________________________ >> 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 > --14dae93998934857de04d4cc94b5 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Hi,

I tried to installed it using step that given by=C2= =A0https://help.u= buntu.com/community/XenProposed, using ubuntu repository. When I try it= on my Laptop with VTx support its running perfectly even when I installed = DomU. However, when I tried to installed on my server IBM Blade server Inte= l Xeon 3,2 Ghz, I know that this server series didn't have VTx support.= After installed the XEN and reboot the machine as tutorial told my server = won't running, it keep restarting.


As I saw, it's can boot to Xen and a= fter try to reloading configuration its fail, so my server restarting over = and over. Since the message was running fast on my screen I can't see t= he message clearly but the first line said that hardware acceleration disab= led or something. Since there is no VTx, firstly I assumed that its because= the VTx. But, it should run I guess because the XEN website said it so.


Regards,

Agya


On Sun, Feb 3, 2013 at 12:32 AM= , tech mailinglists <mailinglists.tech@gmail.com> = wrote:
Hello Agya,
so normally it shouldn't be a problem to run Xen with Ubuntu De= sktop. Do you get any error messages and on which way you installed Xen? Vi= a the package repositorys of Ubuntu or do you compiled it by yourself?

Best Regards


2013/2/2 agya naila <agya.naila@gmail.com>
Dear all,

I am quite new in this virtualization area. I am want to do some ex= periment with live migration using xen. However, I got problem since my ser= ver didn't support VTx. I am using Ubuntu desktop 12.04 64 bit with Xen= 4.1 Amd64. But when I reload the machine it wont start, since the XEN webs= ite its doesn't matter using Paravirtualization without VTx support I d= ont know what is the problem since I didn't start to install para virtu= alized guest yet. I juts install the XEN and reload the maschine and its fa= iled. Does any body now the problem and solution, I would appreciate that.<= /div>

Regards,

Agya

_______________________________________________
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

--14dae93998934857de04d4cc94b5-- --===============5518082920531786851== 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 --===============5518082920531786851==-- From xen-users-bounces@lists.xen.org Sun Feb 03 07:51:31 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sun, 03 Feb 2013 07:51: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 1U1uL7-00056t-4J; Sun, 03 Feb 2013 07:50:13 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U1uL6-00056o-1K for xen-users@lists.xen.org; Sun, 03 Feb 2013 07:50:12 +0000 Received: from [85.158.143.35:34249] by server-1.bemta-4.messagelabs.com id 93/68-08839-3B61E015; Sun, 03 Feb 2013 07:50:11 +0000 X-Env-Sender: wei.liu2@citrix.com X-Msg-Ref: server-15.tower-21.messagelabs.com!1359877808!13892899!1 X-Originating-IP: [66.165.176.63] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjYuMTY1LjE3Ni42MyA9PiAzMDEzMjQ=\n X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 18220 invoked from network); 3 Feb 2013 07:50:09 -0000 Received: from smtp02.citrix.com (HELO SMTP02.CITRIX.COM) (66.165.176.63) by server-15.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 3 Feb 2013 07:50:09 -0000 X-IronPort-AV: E=Sophos;i="4.84,592,1355097600"; d="scan'208";a="5787432" Received: from accessns.citrite.net (HELO FTLPEX01CL02.citrite.net) ([10.9.154.239]) by FTLPIPO02.CITRIX.COM with ESMTP/TLS/AES128-SHA; 03 Feb 2013 07:50:02 +0000 Received: from ukmail1.uk.xensource.com (10.80.16.128) by smtprelay.citrix.com (10.13.107.79) with Microsoft SMTP Server id 14.2.318.1; Sun, 3 Feb 2013 02:50:02 -0500 Received: from zion.uk.xensource.com ([10.80.2.73]) by ukmail1.uk.xensource.com with esmtp (Exim 4.69) (envelope-from ) id 1U1uKw-00061V-4f; Sun, 03 Feb 2013 07:50:02 +0000 Message-ID: <1359877802.7477.8.camel@zion.uk.xensource.com> From: Wei Liu To: Hery Dian Septama Date: Sun, 3 Feb 2013 07:50:02 +0000 In-Reply-To: References: X-Mailer: Evolution 3.6.2 (3.6.2-3.fc18) MIME-Version: 1.0 Cc: tech mailinglists , xen-users , wei.liu2@citrix.com, agya naila Subject: Re: [Xen-users] Running XEN 4.1 64 bit on Ubuntu desktop without VTx X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: 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, 2013-02-03 at 07:03 +0000, Hery Dian Septama wrote: > As I saw, it's can boot to Xen and after try to reloading > configuration its fail, so my server restarting over and over. Since > the message was running fast on my screen I can't see the message You can try to add "noreboot" in Xen command line to stop it from rebooting automatically, so that you have a chance to know the exact error messages. Wei. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Sun Feb 03 07:51:31 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sun, 03 Feb 2013 07:51: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 1U1uL7-00056t-4J; Sun, 03 Feb 2013 07:50:13 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U1uL6-00056o-1K for xen-users@lists.xen.org; Sun, 03 Feb 2013 07:50:12 +0000 Received: from [85.158.143.35:34249] by server-1.bemta-4.messagelabs.com id 93/68-08839-3B61E015; Sun, 03 Feb 2013 07:50:11 +0000 X-Env-Sender: wei.liu2@citrix.com X-Msg-Ref: server-15.tower-21.messagelabs.com!1359877808!13892899!1 X-Originating-IP: [66.165.176.63] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjYuMTY1LjE3Ni42MyA9PiAzMDEzMjQ=\n X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 18220 invoked from network); 3 Feb 2013 07:50:09 -0000 Received: from smtp02.citrix.com (HELO SMTP02.CITRIX.COM) (66.165.176.63) by server-15.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 3 Feb 2013 07:50:09 -0000 X-IronPort-AV: E=Sophos;i="4.84,592,1355097600"; d="scan'208";a="5787432" Received: from accessns.citrite.net (HELO FTLPEX01CL02.citrite.net) ([10.9.154.239]) by FTLPIPO02.CITRIX.COM with ESMTP/TLS/AES128-SHA; 03 Feb 2013 07:50:02 +0000 Received: from ukmail1.uk.xensource.com (10.80.16.128) by smtprelay.citrix.com (10.13.107.79) with Microsoft SMTP Server id 14.2.318.1; Sun, 3 Feb 2013 02:50:02 -0500 Received: from zion.uk.xensource.com ([10.80.2.73]) by ukmail1.uk.xensource.com with esmtp (Exim 4.69) (envelope-from ) id 1U1uKw-00061V-4f; Sun, 03 Feb 2013 07:50:02 +0000 Message-ID: <1359877802.7477.8.camel@zion.uk.xensource.com> From: Wei Liu To: Hery Dian Septama Date: Sun, 3 Feb 2013 07:50:02 +0000 In-Reply-To: References: X-Mailer: Evolution 3.6.2 (3.6.2-3.fc18) MIME-Version: 1.0 Cc: tech mailinglists , xen-users , wei.liu2@citrix.com, agya naila Subject: Re: [Xen-users] Running XEN 4.1 64 bit on Ubuntu desktop without VTx X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: 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, 2013-02-03 at 07:03 +0000, Hery Dian Septama wrote: > As I saw, it's can boot to Xen and after try to reloading > configuration its fail, so my server restarting over and over. Since > the message was running fast on my screen I can't see the message You can try to add "noreboot" in Xen command line to stop it from rebooting automatically, so that you have a chance to know the exact error messages. Wei. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Sun Feb 03 09:46:13 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sun, 03 Feb 2013 09:46: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 1U1w87-0006CH-0U; Sun, 03 Feb 2013 09:44:55 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U1w85-0006CC-In for xen-users@lists.xen.org; Sun, 03 Feb 2013 09:44:53 +0000 Received: from [193.109.254.147:12612] by server-1.bemta-14.messagelabs.com id 8C/C4-29874-4913E015; Sun, 03 Feb 2013 09:44:52 +0000 X-Env-Sender: roger.pau@citrix.com X-Msg-Ref: server-12.tower-27.messagelabs.com!1359884690!9052082!1 X-Originating-IP: [46.33.159.39] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNDYuMzMuMTU5LjM5ID0+IDIwNTcw\n X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 29139 invoked from network); 3 Feb 2013 09:44:51 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (46.33.159.39) by server-12.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 3 Feb 2013 09:44:51 -0000 X-IronPort-AV: E=Sophos;i="4.84,593,1355097600"; d="scan'208";a="1098476" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 03 Feb 2013 09:44:50 +0000 Received: from Roger-2.local (10.30.249.242) by LONPMAILMX01.citrite.net (10.30.203.162) with Microsoft SMTP Server id 8.3.297.1; Sun, 3 Feb 2013 09:44:50 +0000 Message-ID: <510E3195.1010004@citrix.com> Date: Sun, 3 Feb 2013 10:44:53 +0100 From: =?ISO-8859-1?Q?Roger_Pau_Monn=E9?= User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130107 Thunderbird/17.0.2 MIME-Version: 1.0 To: Yathindra References: <510DC655.5060205@cs.utah.edu> In-Reply-To: <510DC655.5060205@cs.utah.edu> Cc: "xen-users@lists.xen.org" Subject: Re: [Xen-users] xen_blkbk times out before getting connected X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: 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 03/02/13 03:07, Yathindra wrote: > Hi, > > When ever I start a guest domain, backend driver times out since state > is not being connected. How do we debug such issues ? > I instrumented the backend drivers, specifically > xen/xenbus/xenbus_probe.c and xen/xenbus/xenbus_probe_backend.c to see > if the backend fails to probe the device. But I never saw any of the > messages I added in syslog or dmesg. I'm stuck on this problem > for weeks now. I'm not understanding why the backend fails to switch the > state. Are you restarting the xenstore daemon? Also could you please post your kernel version? Did you get any messages from the kernel when you try to plug the device? > Heres the libxl log: > > libxl: debug: libxl_device.c:313:libxl__device_disk_set_backend: Disk > vdev=sda1 spec.backend=unknown > libxl: debug: libxl_device.c:349:libxl__device_disk_set_backend: Disk > vdev=sda1, using backend phy > libxl: debug: libxl_create.c:821:initiate_domain_create: running bootloader > libxl: debug: libxl_bootloader.c:327:libxl__bootloader_run: no > bootloader configured, using user supplied kernel > libxl: debug: libxl_event.c:561:libxl__ev_xswatch_deregister: watch > w=0xc3a5e0: deregister unregistered > libxl: debug: libxl_numa.c:435:libxl__get_numa_candidate: New best NUMA > placement candidate found: nr_nodes=1, nr_cpus=2, nr_vcpus=3, free_memkb=997 > libxl: detail: libxl_dom.c:192:numa_place_domain: NUMA placement > candidate with 1 nodes, 2 cpus and 997 KB free selected > domainbuilder: detail: xc_dom_allocate: > cmdline="root=/dev/disk/by-path/xen-vbd-2049 ro xencons=tty", > features="(null)" > libxl: debug: libxl_dom.c:393:libxl__build_pv: pv kernel mapped 0 path > /boot/vmlinuz-3.2.16 > ... > ... > libxl: debug: libxl_event.c:512:libxl__ev_xswatch_register: watch > w=0xc3bd98 wpath=/local/domain/0/backend/vbd/1/2049/state token=3/0: > register slotnum=3 > libxl: debug: libxl_create.c:1330:do_domain_create: ao 0xc39880: > inprogress: poller=0xc398e0, flags=i > libxl: debug: libxl_event.c:457:watchfd_callback: watch w=0xc3bd98 > wpath=/local/domain/0/backend/vbd/1/2049/state token=3/0: event > epath=/local/domain/0/backend/vbd/1/2049/state > libxl: debug: libxl_event.c:600:devstate_watch_callback: backend > /local/domain/0/backend/vbd/1/2049/state wanted state 2 still waiting > state 1 > libxl: debug: libxl_event.c:614:devstate_timeout: backend > /local/domain/0/backend/vbd/1/2049/state wanted state 2 timed out > libxl: debug: libxl_event.c:549:libxl__ev_xswatch_deregister: watch > w=0xc3bd98 wpath=/local/domain/0/backend/vbd/1/2049/state token=3/0: > deregister slotnum=3 > libxl: debug: libxl_event.c:561:libxl__ev_xswatch_deregister: watch > w=0xc3bd98: deregister unregistered > libxl: error: libxl_device.c:943:device_backend_callback: unable to > connect device with path /local/domain/0/backend/vbd/1/2049 > libxl: error: libxl_create.c:1077:domcreate_launch_dm: unable to add > disk devices > libxl: debug: libxl_event.c:512:libxl__ev_xswatch_register: watch > w=0xc3d868 wpath=/local/domain/0/backend/vbd/1/2049/state token=3/1: > register slotnum=3 > libxl: debug: libxl_event.c:457:watchfd_callback: watch w=0xc3d868 > wpath=/local/domain/0/backend/vbd/1/2049/state token=3/1: event > epath=/local/domain/0/backend/vbd/1/2049/state > libxl: debug: libxl_event.c:600:devstate_watch_callback: backend > /local/domain/0/backend/vbd/1/2049/state wanted state 6 still waiting > state 5 > libxl: debug: libxl_event.c:614:devstate_timeout: backend > /local/domain/0/backend/vbd/1/2049/state wanted state 6 timed out > libxl: debug: libxl_event.c:549:libxl__ev_xswatch_deregister: watch > w=0xc3d868 wpath=/local/domain/0/backend/vbd/1/2049/state token=3/1: > deregister slotnum=3 > libxl: debug: libxl_event.c:561:libxl__ev_xswatch_deregister: watch > w=0xc3d868: deregister unregistered > libxl: error: libxl_device.c:943:device_backend_callback: unable to > disconnect device with path /local/domain/0/backend/vbd/1/2049 > libxl: error: libxl.c:1725:devices_destroy_cb: libxl__devices_destroy > failed for 1 > libxl: debug: libxl_event.c:1497:libxl__ao_complete: ao 0xc39880: > complete, rc=-3 > libxl: debug: libxl_event.c:1469:libxl__ao__destroy: ao 0xc39880: destroy > xc: debug: hypercall buffer: total allocations:366 total releases:366 > xc: debug: hypercall buffer: current allocations:0 maximum allocations:4 > xc: debug: hypercall buffer: cache current size:4 > xc: debug: hypercall buffer: cache hits:356 misses:4 toobig:6 > > Thanks, > Yathi > > _______________________________________________ > 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 Feb 03 09:46:13 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sun, 03 Feb 2013 09:46: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 1U1w87-0006CH-0U; Sun, 03 Feb 2013 09:44:55 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U1w85-0006CC-In for xen-users@lists.xen.org; Sun, 03 Feb 2013 09:44:53 +0000 Received: from [193.109.254.147:12612] by server-1.bemta-14.messagelabs.com id 8C/C4-29874-4913E015; Sun, 03 Feb 2013 09:44:52 +0000 X-Env-Sender: roger.pau@citrix.com X-Msg-Ref: server-12.tower-27.messagelabs.com!1359884690!9052082!1 X-Originating-IP: [46.33.159.39] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNDYuMzMuMTU5LjM5ID0+IDIwNTcw\n X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 29139 invoked from network); 3 Feb 2013 09:44:51 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (46.33.159.39) by server-12.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 3 Feb 2013 09:44:51 -0000 X-IronPort-AV: E=Sophos;i="4.84,593,1355097600"; d="scan'208";a="1098476" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 03 Feb 2013 09:44:50 +0000 Received: from Roger-2.local (10.30.249.242) by LONPMAILMX01.citrite.net (10.30.203.162) with Microsoft SMTP Server id 8.3.297.1; Sun, 3 Feb 2013 09:44:50 +0000 Message-ID: <510E3195.1010004@citrix.com> Date: Sun, 3 Feb 2013 10:44:53 +0100 From: =?ISO-8859-1?Q?Roger_Pau_Monn=E9?= User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130107 Thunderbird/17.0.2 MIME-Version: 1.0 To: Yathindra References: <510DC655.5060205@cs.utah.edu> In-Reply-To: <510DC655.5060205@cs.utah.edu> Cc: "xen-users@lists.xen.org" Subject: Re: [Xen-users] xen_blkbk times out before getting connected X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: 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 03/02/13 03:07, Yathindra wrote: > Hi, > > When ever I start a guest domain, backend driver times out since state > is not being connected. How do we debug such issues ? > I instrumented the backend drivers, specifically > xen/xenbus/xenbus_probe.c and xen/xenbus/xenbus_probe_backend.c to see > if the backend fails to probe the device. But I never saw any of the > messages I added in syslog or dmesg. I'm stuck on this problem > for weeks now. I'm not understanding why the backend fails to switch the > state. Are you restarting the xenstore daemon? Also could you please post your kernel version? Did you get any messages from the kernel when you try to plug the device? > Heres the libxl log: > > libxl: debug: libxl_device.c:313:libxl__device_disk_set_backend: Disk > vdev=sda1 spec.backend=unknown > libxl: debug: libxl_device.c:349:libxl__device_disk_set_backend: Disk > vdev=sda1, using backend phy > libxl: debug: libxl_create.c:821:initiate_domain_create: running bootloader > libxl: debug: libxl_bootloader.c:327:libxl__bootloader_run: no > bootloader configured, using user supplied kernel > libxl: debug: libxl_event.c:561:libxl__ev_xswatch_deregister: watch > w=0xc3a5e0: deregister unregistered > libxl: debug: libxl_numa.c:435:libxl__get_numa_candidate: New best NUMA > placement candidate found: nr_nodes=1, nr_cpus=2, nr_vcpus=3, free_memkb=997 > libxl: detail: libxl_dom.c:192:numa_place_domain: NUMA placement > candidate with 1 nodes, 2 cpus and 997 KB free selected > domainbuilder: detail: xc_dom_allocate: > cmdline="root=/dev/disk/by-path/xen-vbd-2049 ro xencons=tty", > features="(null)" > libxl: debug: libxl_dom.c:393:libxl__build_pv: pv kernel mapped 0 path > /boot/vmlinuz-3.2.16 > ... > ... > libxl: debug: libxl_event.c:512:libxl__ev_xswatch_register: watch > w=0xc3bd98 wpath=/local/domain/0/backend/vbd/1/2049/state token=3/0: > register slotnum=3 > libxl: debug: libxl_create.c:1330:do_domain_create: ao 0xc39880: > inprogress: poller=0xc398e0, flags=i > libxl: debug: libxl_event.c:457:watchfd_callback: watch w=0xc3bd98 > wpath=/local/domain/0/backend/vbd/1/2049/state token=3/0: event > epath=/local/domain/0/backend/vbd/1/2049/state > libxl: debug: libxl_event.c:600:devstate_watch_callback: backend > /local/domain/0/backend/vbd/1/2049/state wanted state 2 still waiting > state 1 > libxl: debug: libxl_event.c:614:devstate_timeout: backend > /local/domain/0/backend/vbd/1/2049/state wanted state 2 timed out > libxl: debug: libxl_event.c:549:libxl__ev_xswatch_deregister: watch > w=0xc3bd98 wpath=/local/domain/0/backend/vbd/1/2049/state token=3/0: > deregister slotnum=3 > libxl: debug: libxl_event.c:561:libxl__ev_xswatch_deregister: watch > w=0xc3bd98: deregister unregistered > libxl: error: libxl_device.c:943:device_backend_callback: unable to > connect device with path /local/domain/0/backend/vbd/1/2049 > libxl: error: libxl_create.c:1077:domcreate_launch_dm: unable to add > disk devices > libxl: debug: libxl_event.c:512:libxl__ev_xswatch_register: watch > w=0xc3d868 wpath=/local/domain/0/backend/vbd/1/2049/state token=3/1: > register slotnum=3 > libxl: debug: libxl_event.c:457:watchfd_callback: watch w=0xc3d868 > wpath=/local/domain/0/backend/vbd/1/2049/state token=3/1: event > epath=/local/domain/0/backend/vbd/1/2049/state > libxl: debug: libxl_event.c:600:devstate_watch_callback: backend > /local/domain/0/backend/vbd/1/2049/state wanted state 6 still waiting > state 5 > libxl: debug: libxl_event.c:614:devstate_timeout: backend > /local/domain/0/backend/vbd/1/2049/state wanted state 6 timed out > libxl: debug: libxl_event.c:549:libxl__ev_xswatch_deregister: watch > w=0xc3d868 wpath=/local/domain/0/backend/vbd/1/2049/state token=3/1: > deregister slotnum=3 > libxl: debug: libxl_event.c:561:libxl__ev_xswatch_deregister: watch > w=0xc3d868: deregister unregistered > libxl: error: libxl_device.c:943:device_backend_callback: unable to > disconnect device with path /local/domain/0/backend/vbd/1/2049 > libxl: error: libxl.c:1725:devices_destroy_cb: libxl__devices_destroy > failed for 1 > libxl: debug: libxl_event.c:1497:libxl__ao_complete: ao 0xc39880: > complete, rc=-3 > libxl: debug: libxl_event.c:1469:libxl__ao__destroy: ao 0xc39880: destroy > xc: debug: hypercall buffer: total allocations:366 total releases:366 > xc: debug: hypercall buffer: current allocations:0 maximum allocations:4 > xc: debug: hypercall buffer: cache current size:4 > xc: debug: hypercall buffer: cache hits:356 misses:4 toobig:6 > > Thanks, > Yathi > > _______________________________________________ > 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 Feb 03 09:59:59 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sun, 03 Feb 2013 09:59: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 1U1wLf-0006VD-Il; Sun, 03 Feb 2013 09:58:55 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U1wLd-0006V7-EI for xen-users@lists.xen.org; Sun, 03 Feb 2013 09:58:53 +0000 Received: from [85.158.139.83:48987] by server-7.bemta-5.messagelabs.com id 26/F5-11121-CD43E015; Sun, 03 Feb 2013 09:58:52 +0000 X-Env-Sender: xen-users@morten.bogeskov.dk X-Msg-Ref: server-2.tower-182.messagelabs.com!1359885532!30178376!1 X-Originating-IP: [46.4.206.42] X-SpamReason: No, hits=0.5 required=7.0 tests=BODY_RANDOM_LONG X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 12451 invoked from network); 3 Feb 2013 09:58:52 -0000 Received: from static.42.206.4.46.clients.your-server.de (HELO whitelist.dk) (46.4.206.42) by server-2.tower-182.messagelabs.com with SMTP; 3 Feb 2013 09:58:52 -0000 Received: from localhost (localhost.localdomain [127.0.0.1]) by whitelist.dk (Postfix) with ESMTP id EF5DA16042A for ; Sun, 3 Feb 2013 10:50:45 +0100 (CET) Received: from whitelist.dk (whitelist.dk [46.4.206.41]) by whitelist.dk (Horde Framework) with HTTP; Sun, 03 Feb 2013 10:50:45 +0100 Message-ID: <20130203105045.98426hqtlvaj581h@whitelist.dk> Date: Sun, 03 Feb 2013 10:50:45 +0100 From: Morten =?utf-8?b?QsO4Z2Vza292?= To: "xen-users@lists.xen.org" MIME-Version: 1.0 Content-Disposition: inline User-Agent: Internet Messaging Program (IMP) H3 (4.3.7) Subject: [Xen-users] Memory allocation for PV regarding iommu X-BeenThere: xen-users@lists.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"; DelSp="Yes" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org Hello I'm trying to run a Dom0 with a couple of PV debians (and one HVM) which do PCI passthrough, and a couple that don't. Depending on the order that the DomU's are created in I might get the infamous: "Kernel panic - not syncing: Failed to get contiguous memory for DMA from Xen!" I can reorder them (in /etc/xen/auto/) to start the PCI passthrough ones first then I can get the DMA memory that I need, however... I don't want to start for instance the HVM first, since it steals my graphics card, and in turn my console... since I'm in a habit of messing up my system, that is a bad idea, to run that one first. Actually I don't want to run the HVM of one of the PV's all the time. So my question is: Running xen 4.1 (from debian wheezy) and linux 3.7.4, is there a way to indicate that the memory for some PV's should be taken from the "far" end on the memory, since they don't have the iommu memory need. Alternatively is there a way of reclaiming the graphicscard/console in Dom0 when it has been in a DomU? I've tried the remove_slot,unbind,modprobe i915 - but that results in a: WARNING: at drivers/gpu/drm/i915/intel_display.c:1303 ironlake_crtc_enable+0x2f7/0xcee [i915]() Hardware name: transcoder assertion failed, should be off on pipe A but is still active ---8<--- Console: switching to colour frame buffer device 160x64 But nothing on the console (tried to switch vt) Yours Morten _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Sun Feb 03 09:59:59 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sun, 03 Feb 2013 09:59: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 1U1wLf-0006VD-Il; Sun, 03 Feb 2013 09:58:55 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U1wLd-0006V7-EI for xen-users@lists.xen.org; Sun, 03 Feb 2013 09:58:53 +0000 Received: from [85.158.139.83:48987] by server-7.bemta-5.messagelabs.com id 26/F5-11121-CD43E015; Sun, 03 Feb 2013 09:58:52 +0000 X-Env-Sender: xen-users@morten.bogeskov.dk X-Msg-Ref: server-2.tower-182.messagelabs.com!1359885532!30178376!1 X-Originating-IP: [46.4.206.42] X-SpamReason: No, hits=0.5 required=7.0 tests=BODY_RANDOM_LONG X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 12451 invoked from network); 3 Feb 2013 09:58:52 -0000 Received: from static.42.206.4.46.clients.your-server.de (HELO whitelist.dk) (46.4.206.42) by server-2.tower-182.messagelabs.com with SMTP; 3 Feb 2013 09:58:52 -0000 Received: from localhost (localhost.localdomain [127.0.0.1]) by whitelist.dk (Postfix) with ESMTP id EF5DA16042A for ; Sun, 3 Feb 2013 10:50:45 +0100 (CET) Received: from whitelist.dk (whitelist.dk [46.4.206.41]) by whitelist.dk (Horde Framework) with HTTP; Sun, 03 Feb 2013 10:50:45 +0100 Message-ID: <20130203105045.98426hqtlvaj581h@whitelist.dk> Date: Sun, 03 Feb 2013 10:50:45 +0100 From: Morten =?utf-8?b?QsO4Z2Vza292?= To: "xen-users@lists.xen.org" MIME-Version: 1.0 Content-Disposition: inline User-Agent: Internet Messaging Program (IMP) H3 (4.3.7) Subject: [Xen-users] Memory allocation for PV regarding iommu X-BeenThere: xen-users@lists.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"; DelSp="Yes" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org Hello I'm trying to run a Dom0 with a couple of PV debians (and one HVM) which do PCI passthrough, and a couple that don't. Depending on the order that the DomU's are created in I might get the infamous: "Kernel panic - not syncing: Failed to get contiguous memory for DMA from Xen!" I can reorder them (in /etc/xen/auto/) to start the PCI passthrough ones first then I can get the DMA memory that I need, however... I don't want to start for instance the HVM first, since it steals my graphics card, and in turn my console... since I'm in a habit of messing up my system, that is a bad idea, to run that one first. Actually I don't want to run the HVM of one of the PV's all the time. So my question is: Running xen 4.1 (from debian wheezy) and linux 3.7.4, is there a way to indicate that the memory for some PV's should be taken from the "far" end on the memory, since they don't have the iommu memory need. Alternatively is there a way of reclaiming the graphicscard/console in Dom0 when it has been in a DomU? I've tried the remove_slot,unbind,modprobe i915 - but that results in a: WARNING: at drivers/gpu/drm/i915/intel_display.c:1303 ironlake_crtc_enable+0x2f7/0xcee [i915]() Hardware name: transcoder assertion failed, should be off on pipe A but is still active ---8<--- Console: switching to colour frame buffer device 160x64 But nothing on the console (tried to switch vt) Yours Morten _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Sun Feb 03 16:33:15 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sun, 03 Feb 2013 16:33: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 1U22Tc-0000QV-6N; Sun, 03 Feb 2013 16:31:32 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U22TZ-0000QQ-Vg for xen-users@lists.xen.org; Sun, 03 Feb 2013 16:31:30 +0000 Received: from [85.158.139.211:10101] by server-2.bemta-5.messagelabs.com id 41/06-16911-1E09E015; Sun, 03 Feb 2013 16:31:29 +0000 X-Env-Sender: skupko.sk@gmail.com X-Msg-Ref: server-15.tower-206.messagelabs.com!1359909088!20560778!1 X-Originating-IP: [74.125.82.54] X-SpamReason: No, hits=0.0 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, spamassassin: X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 11453 invoked from network); 3 Feb 2013 16:31:28 -0000 Received: from mail-wg0-f54.google.com (HELO mail-wg0-f54.google.com) (74.125.82.54) by server-15.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 3 Feb 2013 16:31:28 -0000 Received: by mail-wg0-f54.google.com with SMTP id fm10so4228925wgb.9 for ; Sun, 03 Feb 2013 08:31:28 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=j5egv6hc71oMTGafvomLLuc3HAd8p5Os4AgtiAmTufc=; b=CI1vNKzOu7/SQcWAbIeD/ZQ0T+kXf/8e2PL6fiT17EvJQMKdtqVY/bCRfC23bIqZs7 9d+NSJSgbNIuLHWwrNb5mV02G0uqazqreFJBgy2E3P9xlG7RZRmvUO2+NCb+7NWFnWKG C63SX2FyFsEV9vB4UPalZrTo/ptfR9SmXTyzL2SqESgHlNwKoKcdmxvQ/wSH8bV6ub3A u4UjLPh+I5WCdMcrN6Liw9Rw6GSpmMvcp3q8O64WrxaQk4T3VI/B3DmTCplZ3NwE0x7M XsVZKQU0blAs7huFOgJSM/VGCUeyq4M2wrJW1fgVA3c1En5GzNet2JKIN69S7YOIV2G7 ZAnQ== X-Received: by 10.180.90.147 with SMTP id bw19mr6271190wib.28.1359909088277; Sun, 03 Feb 2013 08:31:28 -0800 (PST) Received: from [192.168.30.208] (chello089173144208.chello.sk. [89.173.144.208]) by mx.google.com with ESMTPS id cu7sm15217271wib.8.2013.02.03.08.31.26 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sun, 03 Feb 2013 08:31:27 -0800 (PST) Message-ID: <510E90DA.9090601@gmail.com> Date: Sun, 03 Feb 2013 17:31:22 +0100 From: Peter Viskup User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:10.0.11) Gecko/20121122 Icedove/10.0.11 MIME-Version: 1.0 To: Linux Hack References: In-Reply-To: Cc: "xen-users@lists.xen.org" Subject: Re: [Xen-users] network offloading X-BeenThere: xen-users@lists.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 02/03/2013 03:46 AM, Linux Hack wrote: > Hi, > > One of my Xen HVM vm is utilized the vcpu completely that I allocated. > I found on > http://wiki.xen.org/wiki/Network_Throughput_and_Performance_Guide#Offloading_some_network_processing_to_NICs > which giving the solution to enable network offloading. > > So I want to know is it possible to make it work on Xen on CentOS like > on XenServer? > > And how can I check whether my NIC supports offloading? > Hi, most of toady's (if not all) server adapters support the offloading. You can check the support with ethtool. server1:~# ethtool -k eth1 Offload parameters for eth1: rx-checksumming: on tx-checksumming: on scatter-gather: on tcp-segmentation-offload: on udp-fragmentation-offload: off generic-segmentation-offload: on generic-receive-offload: off large-receive-offload: off ntuple-filters: off receive-hashing: off server1:~# ethtool -i eth1 driver: e1000e version: 1.2.20-k2 firmware-version: 1.3-0 bus-info: 0000:00:19.0 I am not sure about the support of this feature trough the PCI-passtrough (do not see any reason for any issues with that - based on my limited knowledge). Make sure if the network load is the reason of the high load on your HVM machine before playing with these adapter settings (looks like you are not sure about the root cause). Best regards, -- Peter Viskup _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Sun Feb 03 16:33:15 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sun, 03 Feb 2013 16:33: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 1U22Tc-0000QV-6N; Sun, 03 Feb 2013 16:31:32 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U22TZ-0000QQ-Vg for xen-users@lists.xen.org; Sun, 03 Feb 2013 16:31:30 +0000 Received: from [85.158.139.211:10101] by server-2.bemta-5.messagelabs.com id 41/06-16911-1E09E015; Sun, 03 Feb 2013 16:31:29 +0000 X-Env-Sender: skupko.sk@gmail.com X-Msg-Ref: server-15.tower-206.messagelabs.com!1359909088!20560778!1 X-Originating-IP: [74.125.82.54] X-SpamReason: No, hits=0.0 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, spamassassin: X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 11453 invoked from network); 3 Feb 2013 16:31:28 -0000 Received: from mail-wg0-f54.google.com (HELO mail-wg0-f54.google.com) (74.125.82.54) by server-15.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 3 Feb 2013 16:31:28 -0000 Received: by mail-wg0-f54.google.com with SMTP id fm10so4228925wgb.9 for ; Sun, 03 Feb 2013 08:31:28 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=j5egv6hc71oMTGafvomLLuc3HAd8p5Os4AgtiAmTufc=; b=CI1vNKzOu7/SQcWAbIeD/ZQ0T+kXf/8e2PL6fiT17EvJQMKdtqVY/bCRfC23bIqZs7 9d+NSJSgbNIuLHWwrNb5mV02G0uqazqreFJBgy2E3P9xlG7RZRmvUO2+NCb+7NWFnWKG C63SX2FyFsEV9vB4UPalZrTo/ptfR9SmXTyzL2SqESgHlNwKoKcdmxvQ/wSH8bV6ub3A u4UjLPh+I5WCdMcrN6Liw9Rw6GSpmMvcp3q8O64WrxaQk4T3VI/B3DmTCplZ3NwE0x7M XsVZKQU0blAs7huFOgJSM/VGCUeyq4M2wrJW1fgVA3c1En5GzNet2JKIN69S7YOIV2G7 ZAnQ== X-Received: by 10.180.90.147 with SMTP id bw19mr6271190wib.28.1359909088277; Sun, 03 Feb 2013 08:31:28 -0800 (PST) Received: from [192.168.30.208] (chello089173144208.chello.sk. [89.173.144.208]) by mx.google.com with ESMTPS id cu7sm15217271wib.8.2013.02.03.08.31.26 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sun, 03 Feb 2013 08:31:27 -0800 (PST) Message-ID: <510E90DA.9090601@gmail.com> Date: Sun, 03 Feb 2013 17:31:22 +0100 From: Peter Viskup User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:10.0.11) Gecko/20121122 Icedove/10.0.11 MIME-Version: 1.0 To: Linux Hack References: In-Reply-To: Cc: "xen-users@lists.xen.org" Subject: Re: [Xen-users] network offloading X-BeenThere: xen-users@lists.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 02/03/2013 03:46 AM, Linux Hack wrote: > Hi, > > One of my Xen HVM vm is utilized the vcpu completely that I allocated. > I found on > http://wiki.xen.org/wiki/Network_Throughput_and_Performance_Guide#Offloading_some_network_processing_to_NICs > which giving the solution to enable network offloading. > > So I want to know is it possible to make it work on Xen on CentOS like > on XenServer? > > And how can I check whether my NIC supports offloading? > Hi, most of toady's (if not all) server adapters support the offloading. You can check the support with ethtool. server1:~# ethtool -k eth1 Offload parameters for eth1: rx-checksumming: on tx-checksumming: on scatter-gather: on tcp-segmentation-offload: on udp-fragmentation-offload: off generic-segmentation-offload: on generic-receive-offload: off large-receive-offload: off ntuple-filters: off receive-hashing: off server1:~# ethtool -i eth1 driver: e1000e version: 1.2.20-k2 firmware-version: 1.3-0 bus-info: 0000:00:19.0 I am not sure about the support of this feature trough the PCI-passtrough (do not see any reason for any issues with that - based on my limited knowledge). Make sure if the network load is the reason of the high load on your HVM machine before playing with these adapter settings (looks like you are not sure about the root cause). Best regards, -- Peter Viskup _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Sun Feb 03 16:45:22 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sun, 03 Feb 2013 16:45: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 1U22fW-0000hl-Mg; Sun, 03 Feb 2013 16:43:50 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U22fV-0000hf-Gg for xen-users@lists.xen.org; Sun, 03 Feb 2013 16:43:49 +0000 Received: from [85.158.138.51:43333] by server-7.bemta-3.messagelabs.com id F6/8C-10367-4C39E015; Sun, 03 Feb 2013 16:43:48 +0000 X-Env-Sender: skupko.sk@gmail.com X-Msg-Ref: server-2.tower-174.messagelabs.com!1359909827!29013933!1 X-Originating-IP: [74.125.82.178] X-SpamReason: No, hits=0.0 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, spamassassin: X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 16669 invoked from network); 3 Feb 2013 16:43:47 -0000 Received: from mail-we0-f178.google.com (HELO mail-we0-f178.google.com) (74.125.82.178) by server-2.tower-174.messagelabs.com with RC4-SHA encrypted SMTP; 3 Feb 2013 16:43:47 -0000 Received: by mail-we0-f178.google.com with SMTP id x48so4203798wey.37 for ; Sun, 03 Feb 2013 08:43:46 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=1pMqKlsayd3CHLJUs+eW0rp2pcuI2tifopQoV8DwTeU=; b=b+dQI4e1EU8onXbsZlxs9zNKDZ/0XW6ptSf4YSplYR4wSgTeZ8G0PT0+qT6xj8w5iK G0X4XBEYXbcLx75LuIZcPoyxgMxk6o/CMMJ/xoqXF1ItiFX2Yrz6ILNZDFXLYkoktIx6 sE409bSlsi7sT/M375hLENrIl/MzzPgzLzGWg2GMNxfkDqe0yWcnO2ASipLricaHoUNT qfiogsk3ic1/7VwnS4zCtGf8C0ez2jit9TuMjaVudiL31ynTCdsxyUd6OTQ/8FPOwVib ZKBvfgICQB3P6ktF6iQJ2+l20RQlB07h2N21yRJctMiglA1BQpCaTBMnKj2tAt0ISpt3 e/1A== X-Received: by 10.180.93.40 with SMTP id cr8mr6349492wib.15.1359909826877; Sun, 03 Feb 2013 08:43:46 -0800 (PST) Received: from [192.168.30.208] (chello089173144208.chello.sk. [89.173.144.208]) by mx.google.com with ESMTPS id eo10sm16501707wib.9.2013.02.03.08.43.45 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sun, 03 Feb 2013 08:43:46 -0800 (PST) Message-ID: <510E93C1.6090905@gmail.com> Date: Sun, 03 Feb 2013 17:43:45 +0100 From: Peter Viskup User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:10.0.11) Gecko/20121122 Icedove/10.0.11 MIME-Version: 1.0 To: Linux Hack References: In-Reply-To: Cc: "xen-users@lists.xen.org" Subject: Re: [Xen-users] high cpu usage on steal time X-BeenThere: xen-users@lists.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 02/02/2013 12:54 AM, Linux Hack wrote: > Hi, > > One of the server is under high cpu usage and when checked steal time > is causing the high cpu usage. However I have pinned the vcpu's for > dom0 dedicatedly but still no luck. > > Any thought's that would be great? > I had the same issue. Looks like things changed with newer PvOPs kernels (2.6.32+) and now the old fashioned setup of dedication of one CPU for dom0 (xm vcpu-pin 0 all 0) is causing performance issues and very high steal time on dom0. In my case I wasn't able to start any domU as the dom0 had not enough CPU time and it just ended with error (due to some timeout). Unfortunately nor Ian Campbell was able to tell me what is the reason of this behavior and what was changed. Best regards, -- Peter Viskup _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Sun Feb 03 16:45:22 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sun, 03 Feb 2013 16:45: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 1U22fW-0000hl-Mg; Sun, 03 Feb 2013 16:43:50 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U22fV-0000hf-Gg for xen-users@lists.xen.org; Sun, 03 Feb 2013 16:43:49 +0000 Received: from [85.158.138.51:43333] by server-7.bemta-3.messagelabs.com id F6/8C-10367-4C39E015; Sun, 03 Feb 2013 16:43:48 +0000 X-Env-Sender: skupko.sk@gmail.com X-Msg-Ref: server-2.tower-174.messagelabs.com!1359909827!29013933!1 X-Originating-IP: [74.125.82.178] X-SpamReason: No, hits=0.0 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, spamassassin: X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 16669 invoked from network); 3 Feb 2013 16:43:47 -0000 Received: from mail-we0-f178.google.com (HELO mail-we0-f178.google.com) (74.125.82.178) by server-2.tower-174.messagelabs.com with RC4-SHA encrypted SMTP; 3 Feb 2013 16:43:47 -0000 Received: by mail-we0-f178.google.com with SMTP id x48so4203798wey.37 for ; Sun, 03 Feb 2013 08:43:46 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=1pMqKlsayd3CHLJUs+eW0rp2pcuI2tifopQoV8DwTeU=; b=b+dQI4e1EU8onXbsZlxs9zNKDZ/0XW6ptSf4YSplYR4wSgTeZ8G0PT0+qT6xj8w5iK G0X4XBEYXbcLx75LuIZcPoyxgMxk6o/CMMJ/xoqXF1ItiFX2Yrz6ILNZDFXLYkoktIx6 sE409bSlsi7sT/M375hLENrIl/MzzPgzLzGWg2GMNxfkDqe0yWcnO2ASipLricaHoUNT qfiogsk3ic1/7VwnS4zCtGf8C0ez2jit9TuMjaVudiL31ynTCdsxyUd6OTQ/8FPOwVib ZKBvfgICQB3P6ktF6iQJ2+l20RQlB07h2N21yRJctMiglA1BQpCaTBMnKj2tAt0ISpt3 e/1A== X-Received: by 10.180.93.40 with SMTP id cr8mr6349492wib.15.1359909826877; Sun, 03 Feb 2013 08:43:46 -0800 (PST) Received: from [192.168.30.208] (chello089173144208.chello.sk. [89.173.144.208]) by mx.google.com with ESMTPS id eo10sm16501707wib.9.2013.02.03.08.43.45 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sun, 03 Feb 2013 08:43:46 -0800 (PST) Message-ID: <510E93C1.6090905@gmail.com> Date: Sun, 03 Feb 2013 17:43:45 +0100 From: Peter Viskup User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:10.0.11) Gecko/20121122 Icedove/10.0.11 MIME-Version: 1.0 To: Linux Hack References: In-Reply-To: Cc: "xen-users@lists.xen.org" Subject: Re: [Xen-users] high cpu usage on steal time X-BeenThere: xen-users@lists.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 02/02/2013 12:54 AM, Linux Hack wrote: > Hi, > > One of the server is under high cpu usage and when checked steal time > is causing the high cpu usage. However I have pinned the vcpu's for > dom0 dedicatedly but still no luck. > > Any thought's that would be great? > I had the same issue. Looks like things changed with newer PvOPs kernels (2.6.32+) and now the old fashioned setup of dedication of one CPU for dom0 (xm vcpu-pin 0 all 0) is causing performance issues and very high steal time on dom0. In my case I wasn't able to start any domU as the dom0 had not enough CPU time and it just ended with error (due to some timeout). Unfortunately nor Ian Campbell was able to tell me what is the reason of this behavior and what was changed. Best regards, -- Peter Viskup _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Sun Feb 03 18:23:54 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sun, 03 Feb 2013 18: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 1U24Cm-0001Xb-5F; Sun, 03 Feb 2013 18:22:16 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U23iN-0001GV-2i for xen-users@lists.xen.org; Sun, 03 Feb 2013 17:50:51 +0000 Received: from [85.158.139.211:30587] by server-1.bemta-5.messagelabs.com id D4/B3-29263-A73AE015; Sun, 03 Feb 2013 17:50:50 +0000 X-Env-Sender: ydev@cs.utah.edu X-Msg-Ref: server-7.tower-206.messagelabs.com!1359913847!20471119!1 X-Originating-IP: [155.98.64.241] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 18884 invoked from network); 3 Feb 2013 17:50:48 -0000 Received: from rio.cs.utah.edu (HELO mail-svr1.cs.utah.edu) (155.98.64.241) by server-7.tower-206.messagelabs.com with SMTP; 3 Feb 2013 17:50:48 -0000 Received: from localhost (localhost [127.0.0.1]) by mail-svr1.cs.utah.edu (Postfix) with ESMTP id D72E56500B7; Sun, 3 Feb 2013 10:50:46 -0700 (MST) X-Virus-Scanned: amavisd-new at cs.utah.edu Received: from mail-svr1.cs.utah.edu ([127.0.0.1]) by localhost (mail-svr1.cs.utah.edu [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id swOrQpAoAVpT; Sun, 3 Feb 2013 10:50:45 -0700 (MST) Received: from [192.168.1.16] (c-76-23-15-81.hsd1.ut.comcast.net [76.23.15.81]) by smtps.cs.utah.edu (Postfix) with ESMTPSA id 1DE4C6500AF; Sun, 3 Feb 2013 10:50:45 -0700 (MST) Message-ID: <510EA374.6060509@cs.utah.edu> Date: Sun, 03 Feb 2013 10:50:44 -0700 From: Yathindra User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130107 Thunderbird/17.0.2 MIME-Version: 1.0 To: =?ISO-8859-1?Q?Roger_Pau_Monn=E9?= References: <510DC655.5060205@cs.utah.edu> <510E3195.1010004@citrix.com> In-Reply-To: <510E3195.1010004@citrix.com> X-Mailman-Approved-At: Sun, 03 Feb 2013 18:22:15 +0000 Cc: "xen-users@lists.xen.org" Subject: Re: [Xen-users] xen_blkbk times out before getting connected X-BeenThere: xen-users@lists.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 I'm using the latest linux kernel 3.8.0 with Xen 4.3-unstable. Xenstored = is being started at boot time. I did not see any message (dmesg/syslog/console) about device being = plugged in but xenstore-ls shows me all the entries backend and frontend. Here are some details ------------------------------ From /var/log/syslog: Feb 3 10:37:31 localhost kernel: [ 36.466359] Event-channel device = installed. Feb 3 10:37:31 localhost kernel: [ 36.636358] Register = xen_blkbk_driver <<< custom debug message I added Feb 3 10:37:31 localhost kernel: [ 36.636367] = xenbus_register_backend <<< custom debug message I added Feb 3 10:37:31 localhost kernel: [ 36.683533] xenbus_register_backend Feb 3 10:37:31 localhost kernel: [ 36.830115] xen-pciback: backend is = vpci <<< custom debug message I added Feb 3 10:37:31 localhost kernel: [ 36.830123] = xenbus_register_backend <<< custom debug message I added Feb 3 10:37:32 localhost xenstored: Checking store ... Feb 3 10:37:32 localhost xenstored: Checking store complete. Feb 3 10:37:32 localhost kernel: [ 37.075217] xenbus_probe: xenstored = is ready <<< custom debug message I added Feb 3 10:37:32 localhost kernel: [ 37.075230] watching node = FFFFFFFF81C7D1A0 Feb 3 10:37:32 localhost kernel: [ 37.081309] xenbus_scanf for node cpu/0 Feb 3 10:37:32 localhost kernel: [ 37.081327] XENBUS xen store gave: = unknown error cpu Feb 3 10:37:32 localhost kernel: [ 37.081333] xenbus_scanf for node cpu/1 Feb 3 10:37:32 localhost kernel: [ 37.085327] XENBUS unexpected type = [17], expected [2] Feb 3 10:37:32 localhost kernel: [ 37.085342] watching node = FFFFFFFF81C7D0C0 Feb 3 10:37:32 localhost kernel: [ 37.086857] XENBUS unexpected type = [17], expected [4] Feb 3 10:37:32 localhost kernel: [ 37.086865] Failed to set shutdown = watcher Feb 3 10:37:32 localhost kernel: [ 37.086880] backend_probe_and_watch = - enumerates devices in xenstore and watches for changes <<< custom = debug message I added Feb 3 10:37:32 localhost kernel: [ 37.089401] XENBUS unexpected type = [4], expected [1] Feb 3 10:37:32 localhost kernel: [ 37.089411] watching node = FFFFFFFF81C7D660 Feb 3 10:37:32 localhost kernel: [ 37.090715] XENBUS xen store gave: = unknown error control/shutdown Feb 3 10:37:32 localhost kernel: [ 37.090725] = frontend_probe_and_watch: calling xenbus_probe_devices <<< custom debug = message I added Feb 3 10:37:32 localhost kernel: [ 37.092362] XENBUS unexpected type = [17], expected [1] Feb 3 10:37:32 localhost kernel: [ 37.092376] watching node = FFFFFFFF81C7D820 Feb 3 10:37:32 localhost kernel: [ 37.093334] watching node = FFFFFFFF81C7DB20 Feb 3 10:37:32 localhost kernel: [ 37.094454] XENBUS xen store gave: = unknown error backend <<< still not sure how critical this is Feb 3 10:37:32 localhost kernel: [ 37.094463] Failed to set balloon = watcher <<< still not sure how = critical this is > xenstore-ls tool =3D "" xenstored =3D "" local =3D "" domain =3D "" 0 =3D "" data =3D "" meminfo_total =3D "930680" meminfo_free =3D "691868" os_name =3D "Ubuntu 12.04.1 LTS" os_majorver =3D "12" os_minorver =3D "04" os_uname =3D "3.8.0-rc5+" os_distro =3D "ubuntu" updated =3D "Sun Feb 3 10:43:32 MST 2013" name =3D "Domain-0" attr =3D "" xenbr0 =3D "" ip =3D "155.98.39.2" PVAddons =3D "" MajorVersion =3D "5" MinorVersion =3D "5" MicroVersion =3D "0" BuildVersion =3D "17913" Installed =3D "1" device-model =3D "" 0 =3D "" state =3D "running" After this I start the guest domain, here's the xenstore entries, nodea:~> sudo xenstore-ls tool =3D "" xenstored =3D "" local =3D "" domain =3D "" 0 =3D "" data =3D "" meminfo_total =3D "930680" meminfo_free =3D "695408" os_name =3D "Ubuntu 12.04.1 LTS" os_majorver =3D "12" os_minorver =3D "04" os_uname =3D "3.8.0-rc5+" os_distro =3D "ubuntu" updated =3D "Sun Feb 3 10:45:32 MST 2013" name =3D "Domain-0" attr =3D "" xenbr0 =3D "" ip =3D "155.98.39.2" PVAddons =3D "" MajorVersion =3D "5" MinorVersion =3D "5" MicroVersion =3D "0" BuildVersion =3D "17913" Installed =3D "1" device-model =3D "" 0 =3D "" state =3D "running" memory =3D "" target =3D "1048576" static-max =3D "4294967292" freemem-slack =3D "314476" libxl =3D "" disable_udev =3D "1" backend =3D "" vbd =3D "" 1 =3D "" 2049 =3D "" frontend =3D "/local/domain/1/device/vbd/2049" <<<< everything = seems to be enumerated params =3D "/dev/loop0" script =3D "/etc/xen/scripts/block" physical-device =3D "7:0" frontend-id =3D "1" online =3D "1" removable =3D "0" bootable =3D "1" state =3D "1" dev =3D "sda1" type =3D "phy" mode =3D "w" device-type =3D "disk" 1 =3D "" vm =3D "/vm/9b0dfb10-f69d-4e22-9158-bb70456ece2e" name =3D "guest2" cpu =3D "" 0 =3D "" availability =3D "online" memory =3D "" static-max =3D "512000" target =3D "512001" videoram =3D "-1" device =3D "" suspend =3D "" event-channel =3D "" vbd =3D "" 2049 =3D "" backend =3D "/local/domain/0/backend/vbd/1/2049" backend-id =3D "0" state =3D "1" <<<<< state changes to 5 and then after 5 secs it = times out virtual-device =3D "2049" device-type =3D "disk" control =3D "" shutdown =3D "" platform-feature-multiprocessor-suspend =3D "1" platform-feature-xs_reset_watches =3D "1" data =3D "" domid =3D "1" store =3D "" port =3D "1" ring-ref =3D "156845" vm =3D "" 9b0dfb10-f69d-4e22-9158-bb70456ece2e =3D "" uuid =3D "9b0dfb10-f69d-4e22-9158-bb70456ece2e" name =3D "guest2" image =3D "" ostype =3D "linux" kernel =3D "/boot/vmlinuz-3.8.0-rc5+" ramdisk =3D "/boot/initrd.img-3.8.0-rc5+" cmdline =3D "root=3D/dev/disk/by-path/xen-vbd-2049 ro xencons=3Dtty" start_time =3D "1359913591.67" libxl =3D "" 1 =3D "" dm-version =3D "qemu_xen" Thanks, Yathi On 2/3/2013 2:44 AM, Roger Pau Monn=E9 wrote: > On 03/02/13 03:07, Yathindra wrote: >> Hi, >> >> When ever I start a guest domain, backend driver times out since state >> is not being connected. How do we debug such issues ? >> I instrumented the backend drivers, specifically >> xen/xenbus/xenbus_probe.c and xen/xenbus/xenbus_probe_backend.c to see >> if the backend fails to probe the device. But I never saw any of the >> messages I added in syslog or dmesg. I'm stuck on this problem >> for weeks now. I'm not understanding why the backend fails to switch the >> state. > Are you restarting the xenstore daemon? Also could you please post your > kernel version? > > Did you get any messages from the kernel when you try to plug the device? > >> Heres the libxl log: >> >> libxl: debug: libxl_device.c:313:libxl__device_disk_set_backend: Disk >> vdev=3Dsda1 spec.backend=3Dunknown >> libxl: debug: libxl_device.c:349:libxl__device_disk_set_backend: Disk >> vdev=3Dsda1, using backend phy >> libxl: debug: libxl_create.c:821:initiate_domain_create: running bootloa= der >> libxl: debug: libxl_bootloader.c:327:libxl__bootloader_run: no >> bootloader configured, using user supplied kernel >> libxl: debug: libxl_event.c:561:libxl__ev_xswatch_deregister: watch >> w=3D0xc3a5e0: deregister unregistered >> libxl: debug: libxl_numa.c:435:libxl__get_numa_candidate: New best NUMA >> placement candidate found: nr_nodes=3D1, nr_cpus=3D2, nr_vcpus=3D3, free= _memkb=3D997 >> libxl: detail: libxl_dom.c:192:numa_place_domain: NUMA placement >> candidate with 1 nodes, 2 cpus and 997 KB free selected >> domainbuilder: detail: xc_dom_allocate: >> cmdline=3D"root=3D/dev/disk/by-path/xen-vbd-2049 ro xencons=3Dtty", >> features=3D"(null)" >> libxl: debug: libxl_dom.c:393:libxl__build_pv: pv kernel mapped 0 path >> /boot/vmlinuz-3.2.16 >> ... >> ... >> libxl: debug: libxl_event.c:512:libxl__ev_xswatch_register: watch >> w=3D0xc3bd98 wpath=3D/local/domain/0/backend/vbd/1/2049/state token=3D3/= 0: >> register slotnum=3D3 >> libxl: debug: libxl_create.c:1330:do_domain_create: ao 0xc39880: >> inprogress: poller=3D0xc398e0, flags=3Di >> libxl: debug: libxl_event.c:457:watchfd_callback: watch w=3D0xc3bd98 >> wpath=3D/local/domain/0/backend/vbd/1/2049/state token=3D3/0: event >> epath=3D/local/domain/0/backend/vbd/1/2049/state >> libxl: debug: libxl_event.c:600:devstate_watch_callback: backend >> /local/domain/0/backend/vbd/1/2049/state wanted state 2 still waiting >> state 1 >> libxl: debug: libxl_event.c:614:devstate_timeout: backend >> /local/domain/0/backend/vbd/1/2049/state wanted state 2 timed out >> libxl: debug: libxl_event.c:549:libxl__ev_xswatch_deregister: watch >> w=3D0xc3bd98 wpath=3D/local/domain/0/backend/vbd/1/2049/state token=3D3/= 0: >> deregister slotnum=3D3 >> libxl: debug: libxl_event.c:561:libxl__ev_xswatch_deregister: watch >> w=3D0xc3bd98: deregister unregistered >> libxl: error: libxl_device.c:943:device_backend_callback: unable to >> connect device with path /local/domain/0/backend/vbd/1/2049 >> libxl: error: libxl_create.c:1077:domcreate_launch_dm: unable to add >> disk devices >> libxl: debug: libxl_event.c:512:libxl__ev_xswatch_register: watch >> w=3D0xc3d868 wpath=3D/local/domain/0/backend/vbd/1/2049/state token=3D3/= 1: >> register slotnum=3D3 >> libxl: debug: libxl_event.c:457:watchfd_callback: watch w=3D0xc3d868 >> wpath=3D/local/domain/0/backend/vbd/1/2049/state token=3D3/1: event >> epath=3D/local/domain/0/backend/vbd/1/2049/state >> libxl: debug: libxl_event.c:600:devstate_watch_callback: backend >> /local/domain/0/backend/vbd/1/2049/state wanted state 6 still waiting >> state 5 >> libxl: debug: libxl_event.c:614:devstate_timeout: backend >> /local/domain/0/backend/vbd/1/2049/state wanted state 6 timed out >> libxl: debug: libxl_event.c:549:libxl__ev_xswatch_deregister: watch >> w=3D0xc3d868 wpath=3D/local/domain/0/backend/vbd/1/2049/state token=3D3/= 1: >> deregister slotnum=3D3 >> libxl: debug: libxl_event.c:561:libxl__ev_xswatch_deregister: watch >> w=3D0xc3d868: deregister unregistered >> libxl: error: libxl_device.c:943:device_backend_callback: unable to >> disconnect device with path /local/domain/0/backend/vbd/1/2049 >> libxl: error: libxl.c:1725:devices_destroy_cb: libxl__devices_destroy >> failed for 1 >> libxl: debug: libxl_event.c:1497:libxl__ao_complete: ao 0xc39880: >> complete, rc=3D-3 >> libxl: debug: libxl_event.c:1469:libxl__ao__destroy: ao 0xc39880: destroy >> xc: debug: hypercall buffer: total allocations:366 total releases:366 >> xc: debug: hypercall buffer: current allocations:0 maximum allocations:4 >> xc: debug: hypercall buffer: cache current size:4 >> xc: debug: hypercall buffer: cache hits:356 misses:4 toobig:6 >> >> Thanks, >> Yathi >> >> _______________________________________________ >> 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 Feb 03 18:23:54 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sun, 03 Feb 2013 18: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 1U24Cm-0001Xb-5F; Sun, 03 Feb 2013 18:22:16 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U23iN-0001GV-2i for xen-users@lists.xen.org; Sun, 03 Feb 2013 17:50:51 +0000 Received: from [85.158.139.211:30587] by server-1.bemta-5.messagelabs.com id D4/B3-29263-A73AE015; Sun, 03 Feb 2013 17:50:50 +0000 X-Env-Sender: ydev@cs.utah.edu X-Msg-Ref: server-7.tower-206.messagelabs.com!1359913847!20471119!1 X-Originating-IP: [155.98.64.241] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 18884 invoked from network); 3 Feb 2013 17:50:48 -0000 Received: from rio.cs.utah.edu (HELO mail-svr1.cs.utah.edu) (155.98.64.241) by server-7.tower-206.messagelabs.com with SMTP; 3 Feb 2013 17:50:48 -0000 Received: from localhost (localhost [127.0.0.1]) by mail-svr1.cs.utah.edu (Postfix) with ESMTP id D72E56500B7; Sun, 3 Feb 2013 10:50:46 -0700 (MST) X-Virus-Scanned: amavisd-new at cs.utah.edu Received: from mail-svr1.cs.utah.edu ([127.0.0.1]) by localhost (mail-svr1.cs.utah.edu [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id swOrQpAoAVpT; Sun, 3 Feb 2013 10:50:45 -0700 (MST) Received: from [192.168.1.16] (c-76-23-15-81.hsd1.ut.comcast.net [76.23.15.81]) by smtps.cs.utah.edu (Postfix) with ESMTPSA id 1DE4C6500AF; Sun, 3 Feb 2013 10:50:45 -0700 (MST) Message-ID: <510EA374.6060509@cs.utah.edu> Date: Sun, 03 Feb 2013 10:50:44 -0700 From: Yathindra User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130107 Thunderbird/17.0.2 MIME-Version: 1.0 To: =?ISO-8859-1?Q?Roger_Pau_Monn=E9?= References: <510DC655.5060205@cs.utah.edu> <510E3195.1010004@citrix.com> In-Reply-To: <510E3195.1010004@citrix.com> X-Mailman-Approved-At: Sun, 03 Feb 2013 18:22:15 +0000 Cc: "xen-users@lists.xen.org" Subject: Re: [Xen-users] xen_blkbk times out before getting connected X-BeenThere: xen-users@lists.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 I'm using the latest linux kernel 3.8.0 with Xen 4.3-unstable. Xenstored = is being started at boot time. I did not see any message (dmesg/syslog/console) about device being = plugged in but xenstore-ls shows me all the entries backend and frontend. Here are some details ------------------------------ From /var/log/syslog: Feb 3 10:37:31 localhost kernel: [ 36.466359] Event-channel device = installed. Feb 3 10:37:31 localhost kernel: [ 36.636358] Register = xen_blkbk_driver <<< custom debug message I added Feb 3 10:37:31 localhost kernel: [ 36.636367] = xenbus_register_backend <<< custom debug message I added Feb 3 10:37:31 localhost kernel: [ 36.683533] xenbus_register_backend Feb 3 10:37:31 localhost kernel: [ 36.830115] xen-pciback: backend is = vpci <<< custom debug message I added Feb 3 10:37:31 localhost kernel: [ 36.830123] = xenbus_register_backend <<< custom debug message I added Feb 3 10:37:32 localhost xenstored: Checking store ... Feb 3 10:37:32 localhost xenstored: Checking store complete. Feb 3 10:37:32 localhost kernel: [ 37.075217] xenbus_probe: xenstored = is ready <<< custom debug message I added Feb 3 10:37:32 localhost kernel: [ 37.075230] watching node = FFFFFFFF81C7D1A0 Feb 3 10:37:32 localhost kernel: [ 37.081309] xenbus_scanf for node cpu/0 Feb 3 10:37:32 localhost kernel: [ 37.081327] XENBUS xen store gave: = unknown error cpu Feb 3 10:37:32 localhost kernel: [ 37.081333] xenbus_scanf for node cpu/1 Feb 3 10:37:32 localhost kernel: [ 37.085327] XENBUS unexpected type = [17], expected [2] Feb 3 10:37:32 localhost kernel: [ 37.085342] watching node = FFFFFFFF81C7D0C0 Feb 3 10:37:32 localhost kernel: [ 37.086857] XENBUS unexpected type = [17], expected [4] Feb 3 10:37:32 localhost kernel: [ 37.086865] Failed to set shutdown = watcher Feb 3 10:37:32 localhost kernel: [ 37.086880] backend_probe_and_watch = - enumerates devices in xenstore and watches for changes <<< custom = debug message I added Feb 3 10:37:32 localhost kernel: [ 37.089401] XENBUS unexpected type = [4], expected [1] Feb 3 10:37:32 localhost kernel: [ 37.089411] watching node = FFFFFFFF81C7D660 Feb 3 10:37:32 localhost kernel: [ 37.090715] XENBUS xen store gave: = unknown error control/shutdown Feb 3 10:37:32 localhost kernel: [ 37.090725] = frontend_probe_and_watch: calling xenbus_probe_devices <<< custom debug = message I added Feb 3 10:37:32 localhost kernel: [ 37.092362] XENBUS unexpected type = [17], expected [1] Feb 3 10:37:32 localhost kernel: [ 37.092376] watching node = FFFFFFFF81C7D820 Feb 3 10:37:32 localhost kernel: [ 37.093334] watching node = FFFFFFFF81C7DB20 Feb 3 10:37:32 localhost kernel: [ 37.094454] XENBUS xen store gave: = unknown error backend <<< still not sure how critical this is Feb 3 10:37:32 localhost kernel: [ 37.094463] Failed to set balloon = watcher <<< still not sure how = critical this is > xenstore-ls tool =3D "" xenstored =3D "" local =3D "" domain =3D "" 0 =3D "" data =3D "" meminfo_total =3D "930680" meminfo_free =3D "691868" os_name =3D "Ubuntu 12.04.1 LTS" os_majorver =3D "12" os_minorver =3D "04" os_uname =3D "3.8.0-rc5+" os_distro =3D "ubuntu" updated =3D "Sun Feb 3 10:43:32 MST 2013" name =3D "Domain-0" attr =3D "" xenbr0 =3D "" ip =3D "155.98.39.2" PVAddons =3D "" MajorVersion =3D "5" MinorVersion =3D "5" MicroVersion =3D "0" BuildVersion =3D "17913" Installed =3D "1" device-model =3D "" 0 =3D "" state =3D "running" After this I start the guest domain, here's the xenstore entries, nodea:~> sudo xenstore-ls tool =3D "" xenstored =3D "" local =3D "" domain =3D "" 0 =3D "" data =3D "" meminfo_total =3D "930680" meminfo_free =3D "695408" os_name =3D "Ubuntu 12.04.1 LTS" os_majorver =3D "12" os_minorver =3D "04" os_uname =3D "3.8.0-rc5+" os_distro =3D "ubuntu" updated =3D "Sun Feb 3 10:45:32 MST 2013" name =3D "Domain-0" attr =3D "" xenbr0 =3D "" ip =3D "155.98.39.2" PVAddons =3D "" MajorVersion =3D "5" MinorVersion =3D "5" MicroVersion =3D "0" BuildVersion =3D "17913" Installed =3D "1" device-model =3D "" 0 =3D "" state =3D "running" memory =3D "" target =3D "1048576" static-max =3D "4294967292" freemem-slack =3D "314476" libxl =3D "" disable_udev =3D "1" backend =3D "" vbd =3D "" 1 =3D "" 2049 =3D "" frontend =3D "/local/domain/1/device/vbd/2049" <<<< everything = seems to be enumerated params =3D "/dev/loop0" script =3D "/etc/xen/scripts/block" physical-device =3D "7:0" frontend-id =3D "1" online =3D "1" removable =3D "0" bootable =3D "1" state =3D "1" dev =3D "sda1" type =3D "phy" mode =3D "w" device-type =3D "disk" 1 =3D "" vm =3D "/vm/9b0dfb10-f69d-4e22-9158-bb70456ece2e" name =3D "guest2" cpu =3D "" 0 =3D "" availability =3D "online" memory =3D "" static-max =3D "512000" target =3D "512001" videoram =3D "-1" device =3D "" suspend =3D "" event-channel =3D "" vbd =3D "" 2049 =3D "" backend =3D "/local/domain/0/backend/vbd/1/2049" backend-id =3D "0" state =3D "1" <<<<< state changes to 5 and then after 5 secs it = times out virtual-device =3D "2049" device-type =3D "disk" control =3D "" shutdown =3D "" platform-feature-multiprocessor-suspend =3D "1" platform-feature-xs_reset_watches =3D "1" data =3D "" domid =3D "1" store =3D "" port =3D "1" ring-ref =3D "156845" vm =3D "" 9b0dfb10-f69d-4e22-9158-bb70456ece2e =3D "" uuid =3D "9b0dfb10-f69d-4e22-9158-bb70456ece2e" name =3D "guest2" image =3D "" ostype =3D "linux" kernel =3D "/boot/vmlinuz-3.8.0-rc5+" ramdisk =3D "/boot/initrd.img-3.8.0-rc5+" cmdline =3D "root=3D/dev/disk/by-path/xen-vbd-2049 ro xencons=3Dtty" start_time =3D "1359913591.67" libxl =3D "" 1 =3D "" dm-version =3D "qemu_xen" Thanks, Yathi On 2/3/2013 2:44 AM, Roger Pau Monn=E9 wrote: > On 03/02/13 03:07, Yathindra wrote: >> Hi, >> >> When ever I start a guest domain, backend driver times out since state >> is not being connected. How do we debug such issues ? >> I instrumented the backend drivers, specifically >> xen/xenbus/xenbus_probe.c and xen/xenbus/xenbus_probe_backend.c to see >> if the backend fails to probe the device. But I never saw any of the >> messages I added in syslog or dmesg. I'm stuck on this problem >> for weeks now. I'm not understanding why the backend fails to switch the >> state. > Are you restarting the xenstore daemon? Also could you please post your > kernel version? > > Did you get any messages from the kernel when you try to plug the device? > >> Heres the libxl log: >> >> libxl: debug: libxl_device.c:313:libxl__device_disk_set_backend: Disk >> vdev=3Dsda1 spec.backend=3Dunknown >> libxl: debug: libxl_device.c:349:libxl__device_disk_set_backend: Disk >> vdev=3Dsda1, using backend phy >> libxl: debug: libxl_create.c:821:initiate_domain_create: running bootloa= der >> libxl: debug: libxl_bootloader.c:327:libxl__bootloader_run: no >> bootloader configured, using user supplied kernel >> libxl: debug: libxl_event.c:561:libxl__ev_xswatch_deregister: watch >> w=3D0xc3a5e0: deregister unregistered >> libxl: debug: libxl_numa.c:435:libxl__get_numa_candidate: New best NUMA >> placement candidate found: nr_nodes=3D1, nr_cpus=3D2, nr_vcpus=3D3, free= _memkb=3D997 >> libxl: detail: libxl_dom.c:192:numa_place_domain: NUMA placement >> candidate with 1 nodes, 2 cpus and 997 KB free selected >> domainbuilder: detail: xc_dom_allocate: >> cmdline=3D"root=3D/dev/disk/by-path/xen-vbd-2049 ro xencons=3Dtty", >> features=3D"(null)" >> libxl: debug: libxl_dom.c:393:libxl__build_pv: pv kernel mapped 0 path >> /boot/vmlinuz-3.2.16 >> ... >> ... >> libxl: debug: libxl_event.c:512:libxl__ev_xswatch_register: watch >> w=3D0xc3bd98 wpath=3D/local/domain/0/backend/vbd/1/2049/state token=3D3/= 0: >> register slotnum=3D3 >> libxl: debug: libxl_create.c:1330:do_domain_create: ao 0xc39880: >> inprogress: poller=3D0xc398e0, flags=3Di >> libxl: debug: libxl_event.c:457:watchfd_callback: watch w=3D0xc3bd98 >> wpath=3D/local/domain/0/backend/vbd/1/2049/state token=3D3/0: event >> epath=3D/local/domain/0/backend/vbd/1/2049/state >> libxl: debug: libxl_event.c:600:devstate_watch_callback: backend >> /local/domain/0/backend/vbd/1/2049/state wanted state 2 still waiting >> state 1 >> libxl: debug: libxl_event.c:614:devstate_timeout: backend >> /local/domain/0/backend/vbd/1/2049/state wanted state 2 timed out >> libxl: debug: libxl_event.c:549:libxl__ev_xswatch_deregister: watch >> w=3D0xc3bd98 wpath=3D/local/domain/0/backend/vbd/1/2049/state token=3D3/= 0: >> deregister slotnum=3D3 >> libxl: debug: libxl_event.c:561:libxl__ev_xswatch_deregister: watch >> w=3D0xc3bd98: deregister unregistered >> libxl: error: libxl_device.c:943:device_backend_callback: unable to >> connect device with path /local/domain/0/backend/vbd/1/2049 >> libxl: error: libxl_create.c:1077:domcreate_launch_dm: unable to add >> disk devices >> libxl: debug: libxl_event.c:512:libxl__ev_xswatch_register: watch >> w=3D0xc3d868 wpath=3D/local/domain/0/backend/vbd/1/2049/state token=3D3/= 1: >> register slotnum=3D3 >> libxl: debug: libxl_event.c:457:watchfd_callback: watch w=3D0xc3d868 >> wpath=3D/local/domain/0/backend/vbd/1/2049/state token=3D3/1: event >> epath=3D/local/domain/0/backend/vbd/1/2049/state >> libxl: debug: libxl_event.c:600:devstate_watch_callback: backend >> /local/domain/0/backend/vbd/1/2049/state wanted state 6 still waiting >> state 5 >> libxl: debug: libxl_event.c:614:devstate_timeout: backend >> /local/domain/0/backend/vbd/1/2049/state wanted state 6 timed out >> libxl: debug: libxl_event.c:549:libxl__ev_xswatch_deregister: watch >> w=3D0xc3d868 wpath=3D/local/domain/0/backend/vbd/1/2049/state token=3D3/= 1: >> deregister slotnum=3D3 >> libxl: debug: libxl_event.c:561:libxl__ev_xswatch_deregister: watch >> w=3D0xc3d868: deregister unregistered >> libxl: error: libxl_device.c:943:device_backend_callback: unable to >> disconnect device with path /local/domain/0/backend/vbd/1/2049 >> libxl: error: libxl.c:1725:devices_destroy_cb: libxl__devices_destroy >> failed for 1 >> libxl: debug: libxl_event.c:1497:libxl__ao_complete: ao 0xc39880: >> complete, rc=3D-3 >> libxl: debug: libxl_event.c:1469:libxl__ao__destroy: ao 0xc39880: destroy >> xc: debug: hypercall buffer: total allocations:366 total releases:366 >> xc: debug: hypercall buffer: current allocations:0 maximum allocations:4 >> xc: debug: hypercall buffer: cache current size:4 >> xc: debug: hypercall buffer: cache hits:356 misses:4 toobig:6 >> >> Thanks, >> Yathi >> >> _______________________________________________ >> 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 Feb 03 19:52:24 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sun, 03 Feb 2013 19: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 1U25aP-00029G-I8; Sun, 03 Feb 2013 19:50:45 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U25aO-000299-0o for xen-users@lists.xen.org; Sun, 03 Feb 2013 19:50:44 +0000 Received: from [85.158.143.99:34812] by server-1.bemta-4.messagelabs.com id D4/E0-08839-39FBE015; Sun, 03 Feb 2013 19:50:43 +0000 X-Env-Sender: alvaro.ortiz.ga@gmail.com X-Msg-Ref: server-13.tower-216.messagelabs.com!1359921042!29746113!1 X-Originating-IP: [74.125.82.44] X-SpamReason: No, hits=0.3 required=7.0 tests=RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 32034 invoked from network); 3 Feb 2013 19:50:42 -0000 Received: from mail-wg0-f44.google.com (HELO mail-wg0-f44.google.com) (74.125.82.44) by server-13.tower-216.messagelabs.com with RC4-SHA encrypted SMTP; 3 Feb 2013 19:50:42 -0000 Received: by mail-wg0-f44.google.com with SMTP id dr12so4119996wgb.23 for ; Sun, 03 Feb 2013 11:50:42 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:content-type; bh=gTFKVGCaOMfc/6LorR/dHMizRf4kqupj1vm6ZX5fC2s=; b=byYfGkMtBz/RVmxAvyqj5if//3dP8CGHdAlmhyLHWe4iEZF6GFI0fW1mImjMitDtAF rxhOxbCpynWrprxmDGvQYYBA5qs6gGaFyTRcRxRNtOfHhrZ2nTSBXmXJAxNsgoyYmo/T Fb4r/Jop/0Jo2uj6E/uE0c6pr5b2yw4Aelbi6O/Ypd46aByczDBPVTAZy2U8AWoXf/Cn ubcbU2hdWGah3Luz/PTsI0DvHnkVAsyBg9q80ZBPAyAJdaMhfniLtgEsUkafzSel3ue6 KA/eeroZpntP+ev4HIMQMrwBSEnldXaSJoSlapjDPBmnaKJ43Q9+ZazAX42GnTQxAW4D SO5A== MIME-Version: 1.0 X-Received: by 10.194.85.234 with SMTP id k10mr31261789wjz.53.1359921042244; Sun, 03 Feb 2013 11:50:42 -0800 (PST) Received: by 10.216.111.199 with HTTP; Sun, 3 Feb 2013 11:50:42 -0800 (PST) In-Reply-To: References: Date: Sun, 3 Feb 2013 20:50:42 +0100 X-Google-Sender-Auth: hNcZVgC0m88IWbFFLOnF8cOEwCo Message-ID: From: Alvaro To: xen-users@lists.xen.org Subject: Re: [Xen-users] slow or freeze execution in debian wheezy with xen 4.1.3 X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org Solved: I deleted the parameter "sync" in the root of the guest system and the problem has been resolved. I know because the parameter "sync" appears by default in the guest system template: /etc/xen-tools/partitions.d/sample-server Best regards, Alvaro 2013/1/31 Alvaro : > Hello, > > This is my first post to the list, thanks in advance for the help. I > started with xen recently and I have some problems. > > I have installed version xen 4.3.1 on debian wheezy. > I have a problem of execution time between two guests. One of them > takes longer to execute commands. And sometimes it seems that it > freezes. > Both machines are installed with LVM. The difference between them is > that one only has the default installation (root-lvm-lvm & swap) and > the other has four lvm in total. > > Both machines are created with the same command, and identical > characteristics except lvm volumes. > > user1@deckard:~$ time sudo apt-get install apache2 -y > Results: > real 0m26.150s > user 0m1.424s > sys 0m0.868s > > user1@pris:~$ sudo apt-get install apache2 -y > Results: > real 6m42.202s > user 0m2.052s > sys 0m1.768s > > I have tried to do this test drive, but the results are the same. It > seems it has to do with the execution: > user1@deckard:~$ time dd if=/dev/zero of=./test bs=1024k count=5120 conv=fsync > 5120+0 records in > 5120+0 records out > 5368709120 bytes (5.4 GB) copied, 122.405 s, 43.9 MB/s > real 2m2.408s > user 0m0.000s > sys 0m6.968s > > user1@pris:~$ time dd if=/dev/zero of=./test bs=1024k count=5120 conv=fsync > 5120+0 records in > 5120+0 records out > 5368709120 bytes (5.4 GB) copied, 122.234 s, 43.9 MB/s > real 2m2.253s > user 0m0.008s > sys 0m7.148s > > I've also tried to recreate the machine has problems, but the problem persists. > > Is there anyone who has thought something similar? In the domain logs > xen and guests can not find anything. > > May be scheduler? I've "noop deadline [cfq]" in both. > > 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 Sun Feb 03 19:52:24 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sun, 03 Feb 2013 19: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 1U25aP-00029G-I8; Sun, 03 Feb 2013 19:50:45 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U25aO-000299-0o for xen-users@lists.xen.org; Sun, 03 Feb 2013 19:50:44 +0000 Received: from [85.158.143.99:34812] by server-1.bemta-4.messagelabs.com id D4/E0-08839-39FBE015; Sun, 03 Feb 2013 19:50:43 +0000 X-Env-Sender: alvaro.ortiz.ga@gmail.com X-Msg-Ref: server-13.tower-216.messagelabs.com!1359921042!29746113!1 X-Originating-IP: [74.125.82.44] X-SpamReason: No, hits=0.3 required=7.0 tests=RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 32034 invoked from network); 3 Feb 2013 19:50:42 -0000 Received: from mail-wg0-f44.google.com (HELO mail-wg0-f44.google.com) (74.125.82.44) by server-13.tower-216.messagelabs.com with RC4-SHA encrypted SMTP; 3 Feb 2013 19:50:42 -0000 Received: by mail-wg0-f44.google.com with SMTP id dr12so4119996wgb.23 for ; Sun, 03 Feb 2013 11:50:42 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:content-type; bh=gTFKVGCaOMfc/6LorR/dHMizRf4kqupj1vm6ZX5fC2s=; b=byYfGkMtBz/RVmxAvyqj5if//3dP8CGHdAlmhyLHWe4iEZF6GFI0fW1mImjMitDtAF rxhOxbCpynWrprxmDGvQYYBA5qs6gGaFyTRcRxRNtOfHhrZ2nTSBXmXJAxNsgoyYmo/T Fb4r/Jop/0Jo2uj6E/uE0c6pr5b2yw4Aelbi6O/Ypd46aByczDBPVTAZy2U8AWoXf/Cn ubcbU2hdWGah3Luz/PTsI0DvHnkVAsyBg9q80ZBPAyAJdaMhfniLtgEsUkafzSel3ue6 KA/eeroZpntP+ev4HIMQMrwBSEnldXaSJoSlapjDPBmnaKJ43Q9+ZazAX42GnTQxAW4D SO5A== MIME-Version: 1.0 X-Received: by 10.194.85.234 with SMTP id k10mr31261789wjz.53.1359921042244; Sun, 03 Feb 2013 11:50:42 -0800 (PST) Received: by 10.216.111.199 with HTTP; Sun, 3 Feb 2013 11:50:42 -0800 (PST) In-Reply-To: References: Date: Sun, 3 Feb 2013 20:50:42 +0100 X-Google-Sender-Auth: hNcZVgC0m88IWbFFLOnF8cOEwCo Message-ID: From: Alvaro To: xen-users@lists.xen.org Subject: Re: [Xen-users] slow or freeze execution in debian wheezy with xen 4.1.3 X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org Solved: I deleted the parameter "sync" in the root of the guest system and the problem has been resolved. I know because the parameter "sync" appears by default in the guest system template: /etc/xen-tools/partitions.d/sample-server Best regards, Alvaro 2013/1/31 Alvaro : > Hello, > > This is my first post to the list, thanks in advance for the help. I > started with xen recently and I have some problems. > > I have installed version xen 4.3.1 on debian wheezy. > I have a problem of execution time between two guests. One of them > takes longer to execute commands. And sometimes it seems that it > freezes. > Both machines are installed with LVM. The difference between them is > that one only has the default installation (root-lvm-lvm & swap) and > the other has four lvm in total. > > Both machines are created with the same command, and identical > characteristics except lvm volumes. > > user1@deckard:~$ time sudo apt-get install apache2 -y > Results: > real 0m26.150s > user 0m1.424s > sys 0m0.868s > > user1@pris:~$ sudo apt-get install apache2 -y > Results: > real 6m42.202s > user 0m2.052s > sys 0m1.768s > > I have tried to do this test drive, but the results are the same. It > seems it has to do with the execution: > user1@deckard:~$ time dd if=/dev/zero of=./test bs=1024k count=5120 conv=fsync > 5120+0 records in > 5120+0 records out > 5368709120 bytes (5.4 GB) copied, 122.405 s, 43.9 MB/s > real 2m2.408s > user 0m0.000s > sys 0m6.968s > > user1@pris:~$ time dd if=/dev/zero of=./test bs=1024k count=5120 conv=fsync > 5120+0 records in > 5120+0 records out > 5368709120 bytes (5.4 GB) copied, 122.234 s, 43.9 MB/s > real 2m2.253s > user 0m0.008s > sys 0m7.148s > > I've also tried to recreate the machine has problems, but the problem persists. > > Is there anyone who has thought something similar? In the domain logs > xen and guests can not find anything. > > May be scheduler? I've "noop deadline [cfq]" in both. > > 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 Sun Feb 03 21:31:58 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sun, 03 Feb 2013 21:31: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 1U278n-0002qp-JN; Sun, 03 Feb 2013 21:30:21 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U278m-0002qk-1e for xen-users@lists.xen.org; Sun, 03 Feb 2013 21:30:20 +0000 Received: from [85.158.143.35:64488] by server-1.bemta-4.messagelabs.com id E2/54-08839-BE6DE015; Sun, 03 Feb 2013 21:30:19 +0000 X-Env-Sender: matthias.kannenberg@googlemail.com X-Msg-Ref: server-2.tower-21.messagelabs.com!1359927017!5421316!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.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 18946 invoked from network); 3 Feb 2013 21:30:17 -0000 Received: from mail-we0-f173.google.com (HELO mail-we0-f173.google.com) (74.125.82.173) by server-2.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 3 Feb 2013 21:30:17 -0000 Received: by mail-we0-f173.google.com with SMTP id r5so4222759wey.4 for ; Sun, 03 Feb 2013 13:30:17 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=20120113; h=x-received:mime-version:in-reply-to:references:from:date:message-id :subject:to:cc:content-type; bh=nZS3vrSR1Z+nIHuP2wanYlgRG7lC+vdDRZPXAsT7jsA=; b=03tb8bcQmVhkAoqC6TMXcbM8p1FmiMPpPCPcidz4IHbBRwTBNrRKfxwqIVHfPFNn3f 3aQ2y8uo6/prsZ/tTHIRyNAKhC4XzDNgw1hbzx4c2ZYDqhTiIJyvnJWjTjuaZhDcRf96 nXKcpdWLd5qUIIh5zVzUaku5JsUjKFW6P4dcteyy3ckbsJUVMK2yStgEAbA6orZTQ+4m Vx14e545KqSgv5tewxzSxrw6GL3MXjMMcWmWMrPAkbF6ejkvP4h6iimRS1J2qTYY2U9i mvFLXKJHCb1NwvC6/x5x0lwr7yqjSrfkZz0aZrtNk889HClrIAAMB31naxoFUGPHcXQt 84FQ== X-Received: by 10.180.84.162 with SMTP id a2mr6969138wiz.14.1359927017443; Sun, 03 Feb 2013 13:30:17 -0800 (PST) MIME-Version: 1.0 Received: by 10.194.80.68 with HTTP; Sun, 3 Feb 2013 13:29:56 -0800 (PST) In-Reply-To: <1359369167.6559.46.camel@zakaz.uk.xensource.com> References: <1359369167.6559.46.camel@zakaz.uk.xensource.com> From: Matthias Date: Sun, 3 Feb 2013 22:29:56 +0100 Message-ID: To: Ian Campbell Cc: "xen-users@lists.xen.org" Subject: Re: [Xen-users] xl nat and wrong IPs X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: 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 finally got the chance to do the testing.. You were right, the issue was due to routing_ip or better why the calculated ($ip + 127) is used later here: do_or_die ip addr add "$router_ip" dev "${dev}" do_or_die ip route add "$vif_ip" dev "${dev}" src "$router_ip" I don't really see any point in creating a dedicated router-IP and using it this way and i dont' see why this worked for me when using xm earlier, but I might did some hacking before to fix this in my xm installation, i can't really remember.. At the end of the day, I did the following to fix the behavior for my installation: (it's only exchanging router_ip to vif_ip) diff vif-nat vif-nat_backup 174,177c174,175 < #do_or_die ip addr add "$router_ip" dev "${dev}" < do_or_die ip addr add "$vif_ip" dev "${dev}" < #do_or_die ip route add "$vif_ip" dev "${dev}" src "$router_ip" < do_or_die ip route add "$vif_ip" dev "${dev}" src "$vif_ip" --- > do_or_die ip addr add "$router_ip" dev "${dev}" > do_or_die ip route add "$vif_ip" dev "${dev}" src "$router_ip" This way i get correctly named interfaces with the right IPs to use in iptables and policy based routing tables.. 2013/1/28 Ian Campbell : > On Mon, 2013-01-28 at 01:28 +0000, Matthias wrote: >> Hi, >> >> I'm currently switching from toolstacks from xm to xl. Because I have >> a rather complex network setup with my domUs, I use xen's nat >> capabilities. But what works fine with xm behaves slightly strange in >> xl: >> >> I use something like the following to establish a domU interface >> within my vif part: >> >> 'type=vif, mac=00:16:3E:06:DA:B2, ip=192.168.2.1, vifname=fw11, >> model=e1000, script=vif-nat' >> >> Now xm would create an interface called 'fw11' with ip 192.168.2.1 and >> netmask 255.255.255.0. I don't really care about the rest (iptables, >> routes) because I overwrite this from other places anyway.. >> >> But xl creates an interface 'fw11' with ip 192.168.2.128 and netmask >> 255.255.255.255 which is defenetly not what I was expecting. > > Absolutely! > > At one point xl had a bug with handling spaces in the vif specification, > which might cause ip= to not take affect. I thought it was fixed, but > perhaps not? > > Do you see an "ip" node under the vif backend device in xenstore? > > Can you try dropping the spaces in your configuration file? > >> Can somebody explain why xl behaves the way it does and how can I >> change this? I could only find vif-nat setting routes but nothing >> about netmasks and IPs so I guess i'm missing something here.. > > I expect that the .2.128 comes from routing_ip() in the vif-nat script. > However this hasn't changed recently and should behave the same under xl > as it did under xm so obviously something is up. > > If it's not the problem above then you might need to add some additional > logging to the vif-nat script to figure out why it isn't accepting your > ip setting. > > Ian. > _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Sun Feb 03 21:31:58 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sun, 03 Feb 2013 21:31: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 1U278n-0002qp-JN; Sun, 03 Feb 2013 21:30:21 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U278m-0002qk-1e for xen-users@lists.xen.org; Sun, 03 Feb 2013 21:30:20 +0000 Received: from [85.158.143.35:64488] by server-1.bemta-4.messagelabs.com id E2/54-08839-BE6DE015; Sun, 03 Feb 2013 21:30:19 +0000 X-Env-Sender: matthias.kannenberg@googlemail.com X-Msg-Ref: server-2.tower-21.messagelabs.com!1359927017!5421316!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.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 18946 invoked from network); 3 Feb 2013 21:30:17 -0000 Received: from mail-we0-f173.google.com (HELO mail-we0-f173.google.com) (74.125.82.173) by server-2.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 3 Feb 2013 21:30:17 -0000 Received: by mail-we0-f173.google.com with SMTP id r5so4222759wey.4 for ; Sun, 03 Feb 2013 13:30:17 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=20120113; h=x-received:mime-version:in-reply-to:references:from:date:message-id :subject:to:cc:content-type; bh=nZS3vrSR1Z+nIHuP2wanYlgRG7lC+vdDRZPXAsT7jsA=; b=03tb8bcQmVhkAoqC6TMXcbM8p1FmiMPpPCPcidz4IHbBRwTBNrRKfxwqIVHfPFNn3f 3aQ2y8uo6/prsZ/tTHIRyNAKhC4XzDNgw1hbzx4c2ZYDqhTiIJyvnJWjTjuaZhDcRf96 nXKcpdWLd5qUIIh5zVzUaku5JsUjKFW6P4dcteyy3ckbsJUVMK2yStgEAbA6orZTQ+4m Vx14e545KqSgv5tewxzSxrw6GL3MXjMMcWmWMrPAkbF6ejkvP4h6iimRS1J2qTYY2U9i mvFLXKJHCb1NwvC6/x5x0lwr7yqjSrfkZz0aZrtNk889HClrIAAMB31naxoFUGPHcXQt 84FQ== X-Received: by 10.180.84.162 with SMTP id a2mr6969138wiz.14.1359927017443; Sun, 03 Feb 2013 13:30:17 -0800 (PST) MIME-Version: 1.0 Received: by 10.194.80.68 with HTTP; Sun, 3 Feb 2013 13:29:56 -0800 (PST) In-Reply-To: <1359369167.6559.46.camel@zakaz.uk.xensource.com> References: <1359369167.6559.46.camel@zakaz.uk.xensource.com> From: Matthias Date: Sun, 3 Feb 2013 22:29:56 +0100 Message-ID: To: Ian Campbell Cc: "xen-users@lists.xen.org" Subject: Re: [Xen-users] xl nat and wrong IPs X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: 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 finally got the chance to do the testing.. You were right, the issue was due to routing_ip or better why the calculated ($ip + 127) is used later here: do_or_die ip addr add "$router_ip" dev "${dev}" do_or_die ip route add "$vif_ip" dev "${dev}" src "$router_ip" I don't really see any point in creating a dedicated router-IP and using it this way and i dont' see why this worked for me when using xm earlier, but I might did some hacking before to fix this in my xm installation, i can't really remember.. At the end of the day, I did the following to fix the behavior for my installation: (it's only exchanging router_ip to vif_ip) diff vif-nat vif-nat_backup 174,177c174,175 < #do_or_die ip addr add "$router_ip" dev "${dev}" < do_or_die ip addr add "$vif_ip" dev "${dev}" < #do_or_die ip route add "$vif_ip" dev "${dev}" src "$router_ip" < do_or_die ip route add "$vif_ip" dev "${dev}" src "$vif_ip" --- > do_or_die ip addr add "$router_ip" dev "${dev}" > do_or_die ip route add "$vif_ip" dev "${dev}" src "$router_ip" This way i get correctly named interfaces with the right IPs to use in iptables and policy based routing tables.. 2013/1/28 Ian Campbell : > On Mon, 2013-01-28 at 01:28 +0000, Matthias wrote: >> Hi, >> >> I'm currently switching from toolstacks from xm to xl. Because I have >> a rather complex network setup with my domUs, I use xen's nat >> capabilities. But what works fine with xm behaves slightly strange in >> xl: >> >> I use something like the following to establish a domU interface >> within my vif part: >> >> 'type=vif, mac=00:16:3E:06:DA:B2, ip=192.168.2.1, vifname=fw11, >> model=e1000, script=vif-nat' >> >> Now xm would create an interface called 'fw11' with ip 192.168.2.1 and >> netmask 255.255.255.0. I don't really care about the rest (iptables, >> routes) because I overwrite this from other places anyway.. >> >> But xl creates an interface 'fw11' with ip 192.168.2.128 and netmask >> 255.255.255.255 which is defenetly not what I was expecting. > > Absolutely! > > At one point xl had a bug with handling spaces in the vif specification, > which might cause ip= to not take affect. I thought it was fixed, but > perhaps not? > > Do you see an "ip" node under the vif backend device in xenstore? > > Can you try dropping the spaces in your configuration file? > >> Can somebody explain why xl behaves the way it does and how can I >> change this? I could only find vif-nat setting routes but nothing >> about netmasks and IPs so I guess i'm missing something here.. > > I expect that the .2.128 comes from routing_ip() in the vif-nat script. > However this hasn't changed recently and should behave the same under xl > as it did under xm so obviously something is up. > > If it's not the problem above then you might need to add some additional > logging to the vif-nat script to figure out why it isn't accepting your > ip setting. > > Ian. > _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Sun Feb 03 23:07:34 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sun, 03 Feb 2013 23:07: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 1U28dD-0003WY-5t; Sun, 03 Feb 2013 23:05:51 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U28dB-0003WT-5p for xen-users@lists.xensource.com; Sun, 03 Feb 2013 23:05:49 +0000 Received: from [85.158.138.51:16571] by server-3.bemta-3.messagelabs.com id 20/0E-31070-C4DEE015; Sun, 03 Feb 2013 23:05:48 +0000 X-Env-Sender: romihs.forums@gmail.com X-Msg-Ref: server-11.tower-174.messagelabs.com!1359932746!30784827!1 X-Originating-IP: [209.85.219.50] 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.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 5564 invoked from network); 3 Feb 2013 23:05:47 -0000 Received: from mail-oa0-f50.google.com (HELO mail-oa0-f50.google.com) (209.85.219.50) by server-11.tower-174.messagelabs.com with RC4-SHA encrypted SMTP; 3 Feb 2013 23:05:47 -0000 Received: by mail-oa0-f50.google.com with SMTP id l20so2518860oag.37 for ; Sun, 03 Feb 2013 15:05:45 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:date:message-id:subject:from:to :content-type; bh=QqAXFjgOZkDetx7qYTu2i4m1X+HQ9RfSyfV6v1HFg9Q=; b=GjDsIU/xygsQAXuehOUC/S4v24CKnWx7rkVCRNxWvh9g1TETQ8uEZ17gsntBs8xhS1 Ll4oRZPElKGNbuw7XHqTkDwlei5Ae08DZ7axwM9puotDaH0tfZVE62hrEVp+q/Xox5J+ dABkrgM6HvdX9c0gb13iERQv0N49w8vx0OAyG6CKPTD6CecGyjlXyFMDMBwcFTpUaioB 8i3KGTQZSdEPFLN546YCpW/Ywh8l3ZfvALJ853UZ1lTyfeNXjtE3fMA334MoPXAnMQcJ B3ltzQaVuKiXATJQpiKwd7cTgj98HAbQ5mE6GQG1PjfhH9yzozdtGKbU3OyBuZpmGoAu u98g== MIME-Version: 1.0 X-Received: by 10.60.13.162 with SMTP id i2mr6253937oec.121.1359932745756; Sun, 03 Feb 2013 15:05:45 -0800 (PST) Received: by 10.76.98.113 with HTTP; Sun, 3 Feb 2013 15:05:45 -0800 (PST) Date: Mon, 4 Feb 2013 00:05:45 +0100 Message-ID: From: Sandi Romih To: "xen-users@lists.xensource.com" Subject: [Xen-users] Recommended linux kernel for xen 4.2.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="===============7146158122693384520==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============7146158122693384520== Content-Type: multipart/alternative; boundary=e89a8fb201183ab15a04d4da044f --e89a8fb201183ab15a04d4da044f Content-Type: text/plain; charset=ISO-8859-1 Hello, Which linux kernel is best suited for the dom0? According to this http://wiki.xen.org/wiki/XenKernelFeatures, linux 3.1.0 is the latest version supported, but this page was last updated Oct 2011. Thanks --e89a8fb201183ab15a04d4da044f Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Hello,

Which linux kernel is best= suited for the dom0?

According to thi= s=A0http://wiki.xen.= org/wiki/XenKernelFeatures, linux 3.1.0 is the latest version supported= , but this page was last updated Oct 2011.

Thanks
--e89a8fb201183ab15a04d4da044f-- --===============7146158122693384520== 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 --===============7146158122693384520==-- From xen-users-bounces@lists.xen.org Sun Feb 03 23:07:34 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sun, 03 Feb 2013 23:07: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 1U28dD-0003WY-5t; Sun, 03 Feb 2013 23:05:51 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U28dB-0003WT-5p for xen-users@lists.xensource.com; Sun, 03 Feb 2013 23:05:49 +0000 Received: from [85.158.138.51:16571] by server-3.bemta-3.messagelabs.com id 20/0E-31070-C4DEE015; Sun, 03 Feb 2013 23:05:48 +0000 X-Env-Sender: romihs.forums@gmail.com X-Msg-Ref: server-11.tower-174.messagelabs.com!1359932746!30784827!1 X-Originating-IP: [209.85.219.50] 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.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 5564 invoked from network); 3 Feb 2013 23:05:47 -0000 Received: from mail-oa0-f50.google.com (HELO mail-oa0-f50.google.com) (209.85.219.50) by server-11.tower-174.messagelabs.com with RC4-SHA encrypted SMTP; 3 Feb 2013 23:05:47 -0000 Received: by mail-oa0-f50.google.com with SMTP id l20so2518860oag.37 for ; Sun, 03 Feb 2013 15:05:45 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:date:message-id:subject:from:to :content-type; bh=QqAXFjgOZkDetx7qYTu2i4m1X+HQ9RfSyfV6v1HFg9Q=; b=GjDsIU/xygsQAXuehOUC/S4v24CKnWx7rkVCRNxWvh9g1TETQ8uEZ17gsntBs8xhS1 Ll4oRZPElKGNbuw7XHqTkDwlei5Ae08DZ7axwM9puotDaH0tfZVE62hrEVp+q/Xox5J+ dABkrgM6HvdX9c0gb13iERQv0N49w8vx0OAyG6CKPTD6CecGyjlXyFMDMBwcFTpUaioB 8i3KGTQZSdEPFLN546YCpW/Ywh8l3ZfvALJ853UZ1lTyfeNXjtE3fMA334MoPXAnMQcJ B3ltzQaVuKiXATJQpiKwd7cTgj98HAbQ5mE6GQG1PjfhH9yzozdtGKbU3OyBuZpmGoAu u98g== MIME-Version: 1.0 X-Received: by 10.60.13.162 with SMTP id i2mr6253937oec.121.1359932745756; Sun, 03 Feb 2013 15:05:45 -0800 (PST) Received: by 10.76.98.113 with HTTP; Sun, 3 Feb 2013 15:05:45 -0800 (PST) Date: Mon, 4 Feb 2013 00:05:45 +0100 Message-ID: From: Sandi Romih To: "xen-users@lists.xensource.com" Subject: [Xen-users] Recommended linux kernel for xen 4.2.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="===============7146158122693384520==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============7146158122693384520== Content-Type: multipart/alternative; boundary=e89a8fb201183ab15a04d4da044f --e89a8fb201183ab15a04d4da044f Content-Type: text/plain; charset=ISO-8859-1 Hello, Which linux kernel is best suited for the dom0? According to this http://wiki.xen.org/wiki/XenKernelFeatures, linux 3.1.0 is the latest version supported, but this page was last updated Oct 2011. Thanks --e89a8fb201183ab15a04d4da044f Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Hello,

Which linux kernel is best= suited for the dom0?

According to thi= s=A0http://wiki.xen.= org/wiki/XenKernelFeatures, linux 3.1.0 is the latest version supported= , but this page was last updated Oct 2011.

Thanks
--e89a8fb201183ab15a04d4da044f-- --===============7146158122693384520== 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 --===============7146158122693384520==-- From xen-users-bounces@lists.xen.org Sun Feb 03 23:36:21 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sun, 03 Feb 2013 23:36: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 1U295K-0003uz-TF; Sun, 03 Feb 2013 23: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 1U295J-0003ut-A2 for xen-users@lists.xensource.com; Sun, 03 Feb 2013 23:34:53 +0000 Received: from [85.158.143.35:32395] by server-1.bemta-4.messagelabs.com id 57/5C-08839-C14FE015; Sun, 03 Feb 2013 23:34:52 +0000 X-Env-Sender: nunomagalhaes@eu.ipp.pt X-Msg-Ref: server-5.tower-21.messagelabs.com!1359934491!4779230!1 X-Originating-IP: [209.85.216.41] X-SpamReason: No, hits=0.3 required=7.0 tests=RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 29467 invoked from network); 3 Feb 2013 23:34:52 -0000 Received: from mail-qa0-f41.google.com (HELO mail-qa0-f41.google.com) (209.85.216.41) by server-5.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 3 Feb 2013 23:34:52 -0000 Received: by mail-qa0-f41.google.com with SMTP id hy16so1027095qab.7 for ; Sun, 03 Feb 2013 15:34:50 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=x-received:mime-version:in-reply-to:references:from:date:message-id :subject:to:content-type:x-gm-message-state; bh=eyYzpDd0optwo3m/lyPWhmB8wSAVaJZO7l4iIeuHl2Y=; b=EaAhsOhStd1RxoX/MXrrStGQjYWaOMM1m5KcWHwgN4xKcfU5hWKh/Wo7xV/Gzwq6/b sqJd7vUnEDVKbKYEfDS5c1tpGTrbrCf975J0nraJxVFMGbLb8eoyet4fz7jD/B5WZerC jK1yDsLNM0L+0VuTP30Ttij4/LG+7rxegzgIxpSKW/KENRfdiyibuWEycdS/l7/TzbF4 Ehyxit/QB8VskvEdOy01Kklt2Lscv/6NuY79tH2HwhUBCueT8Z2bqCS/MJuLUBOcBycD vOJlMfwroeH8ycodLEbMUcYRSUjB1UdSbYEGKQ0Xn6mp/U5RMsUlg6CN6+lbJPHJzVDe vMSg== X-Received: by 10.224.180.69 with SMTP id bt5mr17583545qab.36.1359934490794; Sun, 03 Feb 2013 15:34:50 -0800 (PST) MIME-Version: 1.0 Received: by 10.49.1.49 with HTTP; Sun, 3 Feb 2013 15:34:30 -0800 (PST) In-Reply-To: References: From: =?UTF-8?Q?Nuno_Magalh=C3=A3es?= Date: Sun, 3 Feb 2013 23:34:30 +0000 Message-ID: To: xen-users@lists.xensource.com X-Gm-Message-State: ALoCoQn1liy0nWa+1PI58Kvg4RxUmWif4saWHzE80bz40kH+6P5B7ozApv4uKV7vP6pObK/kX5Jx Subject: Re: [Xen-users] Recommended linux kernel for xen 4.2.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 Sun, Feb 3, 2013 at 11:05 PM, Sandi Romih wrote: > Hello, > > Which linux kernel is best suited for the dom0? Mine's a recent Debian stable: Xen 4.0.1-5.5 Linux 2.6.32 I'd say a 2.6.* would be a safe bet; not sure on the 3.* yet... YMMV. HTH, Nuno _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Sun Feb 03 23:36:21 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sun, 03 Feb 2013 23:36: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 1U295K-0003uz-TF; Sun, 03 Feb 2013 23: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 1U295J-0003ut-A2 for xen-users@lists.xensource.com; Sun, 03 Feb 2013 23:34:53 +0000 Received: from [85.158.143.35:32395] by server-1.bemta-4.messagelabs.com id 57/5C-08839-C14FE015; Sun, 03 Feb 2013 23:34:52 +0000 X-Env-Sender: nunomagalhaes@eu.ipp.pt X-Msg-Ref: server-5.tower-21.messagelabs.com!1359934491!4779230!1 X-Originating-IP: [209.85.216.41] X-SpamReason: No, hits=0.3 required=7.0 tests=RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 29467 invoked from network); 3 Feb 2013 23:34:52 -0000 Received: from mail-qa0-f41.google.com (HELO mail-qa0-f41.google.com) (209.85.216.41) by server-5.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 3 Feb 2013 23:34:52 -0000 Received: by mail-qa0-f41.google.com with SMTP id hy16so1027095qab.7 for ; Sun, 03 Feb 2013 15:34:50 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=x-received:mime-version:in-reply-to:references:from:date:message-id :subject:to:content-type:x-gm-message-state; bh=eyYzpDd0optwo3m/lyPWhmB8wSAVaJZO7l4iIeuHl2Y=; b=EaAhsOhStd1RxoX/MXrrStGQjYWaOMM1m5KcWHwgN4xKcfU5hWKh/Wo7xV/Gzwq6/b sqJd7vUnEDVKbKYEfDS5c1tpGTrbrCf975J0nraJxVFMGbLb8eoyet4fz7jD/B5WZerC jK1yDsLNM0L+0VuTP30Ttij4/LG+7rxegzgIxpSKW/KENRfdiyibuWEycdS/l7/TzbF4 Ehyxit/QB8VskvEdOy01Kklt2Lscv/6NuY79tH2HwhUBCueT8Z2bqCS/MJuLUBOcBycD vOJlMfwroeH8ycodLEbMUcYRSUjB1UdSbYEGKQ0Xn6mp/U5RMsUlg6CN6+lbJPHJzVDe vMSg== X-Received: by 10.224.180.69 with SMTP id bt5mr17583545qab.36.1359934490794; Sun, 03 Feb 2013 15:34:50 -0800 (PST) MIME-Version: 1.0 Received: by 10.49.1.49 with HTTP; Sun, 3 Feb 2013 15:34:30 -0800 (PST) In-Reply-To: References: From: =?UTF-8?Q?Nuno_Magalh=C3=A3es?= Date: Sun, 3 Feb 2013 23:34:30 +0000 Message-ID: To: xen-users@lists.xensource.com X-Gm-Message-State: ALoCoQn1liy0nWa+1PI58Kvg4RxUmWif4saWHzE80bz40kH+6P5B7ozApv4uKV7vP6pObK/kX5Jx Subject: Re: [Xen-users] Recommended linux kernel for xen 4.2.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 Sun, Feb 3, 2013 at 11:05 PM, Sandi Romih wrote: > Hello, > > Which linux kernel is best suited for the dom0? Mine's a recent Debian stable: Xen 4.0.1-5.5 Linux 2.6.32 I'd say a 2.6.* would be a safe bet; not sure on the 3.* yet... YMMV. HTH, Nuno _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Mon Feb 04 02:51:54 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 04 Feb 2013 02:51: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 1U2C8N-0001To-Hv; Mon, 04 Feb 2013 02:50:15 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U2C8M-0001Tj-0x for xen-users@lists.xen.org; Mon, 04 Feb 2013 02:50:14 +0000 Received: from [85.158.137.99:33370] by server-9.bemta-3.messagelabs.com id BE/2B-09484-5E12F015; Mon, 04 Feb 2013 02:50:13 +0000 X-Env-Sender: skupko.sk@gmail.com X-Msg-Ref: server-8.tower-217.messagelabs.com!1359946211!14407089!1 X-Originating-IP: [74.125.82.170] X-SpamReason: No, hits=0.1 required=7.0 tests=HTML_50_60,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 23894 invoked from network); 4 Feb 2013 02:50:12 -0000 Received: from mail-we0-f170.google.com (HELO mail-we0-f170.google.com) (74.125.82.170) by server-8.tower-217.messagelabs.com with RC4-SHA encrypted SMTP; 4 Feb 2013 02:50:12 -0000 Received: by mail-we0-f170.google.com with SMTP id z53so4568054wey.29 for ; Sun, 03 Feb 2013 18:50:11 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type; bh=FpJb6Y2He/HGrrJUkgHd1fGOTh0gFpOJQs8TQbg8Ppw=; b=idqQ5Zbq9HaY9JY7DYFEzyJOE8fix3YQgTXNNaigVot9lT0nDfye3d2FADnASYtGVr g+kzHy1Xx+HR4bahIqLhYkw/gxdM3vsZR+QgDqgIyLsxvfT1SDFEBoYMg/Dm8/FID8JR A49wck1rFYHwR8pAG5sXo5atuL9IXPIi0RynxbWWAXen+9BEwcbHUC2QbmOy8m+7/OeR LLsoffAQh6IySLIEcueOFLFME4nlaHYKmT7IVVQAopCbK9g02hNCKnTKnOcCtrYQtRaS LEFgjDqRfI58p/emq/YLpAhrFwzaXbl+u5/QN1moGe0+H+zNz9Zciea44Q0BE5xp9dvN Og0g== X-Received: by 10.180.95.166 with SMTP id dl6mr7833025wib.9.1359946211450; Sun, 03 Feb 2013 18:50:11 -0800 (PST) Received: from [192.168.30.208] (chello089173144208.chello.sk. [89.173.144.208]) by mx.google.com with ESMTPS id s10sm18868047wiw.4.2013.02.03.18.50.09 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sun, 03 Feb 2013 18:50:10 -0800 (PST) Message-ID: <510F21DC.5040609@gmail.com> Date: Mon, 04 Feb 2013 03:50:04 +0100 From: Peter Viskup User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:10.0.11) Gecko/20121122 Icedove/10.0.11 MIME-Version: 1.0 To: Linux Hack References: <510E93C1.6090905@gmail.com> In-Reply-To: Cc: "xen-users@lists.xen.org" Subject: Re: [Xen-users] high cpu usage on steal time X-BeenThere: xen-users@lists.xen.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="===============2792574078173545958==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org This is a multi-part message in MIME format. --===============2792574078173545958== Content-Type: multipart/alternative; boundary="------------090404050205050008090005" This is a multi-part message in MIME format. --------------090404050205050008090005 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit I don't want to step into discussion about my setup as I already discussed this here just some weeks before. Do you still experience the issue with higher steal time or we can disregard this your request for support? Do you see the steal time on dom0 or some domU? On 02/04/2013 01:44 AM, Linux Hack wrote: > Hi Peter, > > Seems things are going fine with minimum steal time cpu usage (vary > between 5-20) with Xen 4.1.4 and latest centos 5.9 xen kernel. > > What is the kernel you are running on your server? > > > > On Sun, Feb 3, 2013 at 10:13 PM, Peter Viskup > wrote: > > On 02/02/2013 12:54 AM, Linux Hack wrote: > > Hi, > > One of the server is under high cpu usage and when checked > steal time is causing the high cpu usage. However I have > pinned the vcpu's for dom0 dedicatedly but still no luck. > > Any thought's that would be great? > > > I had the same issue. Looks like things changed with newer PvOPs > kernels (2.6.32+) and now the old fashioned setup of dedication of > one CPU for dom0 (xm vcpu-pin 0 all 0) is causing performance > issues and very high steal time on dom0. In my case I wasn't able > to start any domU as the dom0 had not enough CPU time and it just > ended with error (due to some timeout). Unfortunately nor Ian > Campbell was able to tell me what is the reason of this behavior > and what was changed. > > Best regards, > -- > Peter Viskup > > --------------090404050205050008090005 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit I don't want to step into discussion about my setup as I already discussed this here just some weeks before.
Do you still experience the issue with higher steal time or we can disregard this your request for support?
Do you see the steal time on dom0 or some domU?

On 02/04/2013 01:44 AM, Linux Hack wrote:
Hi Peter,

Seems things are going fine with minimum steal time cpu usage (vary between 5-20) with Xen 4.1.4 and latest centos 5.9 xen kernel.

What is the kernel you are running on your server?



On Sun, Feb 3, 2013 at 10:13 PM, Peter Viskup <skupko.sk@gmail.com> wrote:
On 02/02/2013 12:54 AM, Linux Hack wrote:
Hi,

One of the server is under high cpu usage and when checked steal time is causing the high cpu usage. However I have pinned the vcpu's for dom0 dedicatedly but still no luck.

Any thought's that would be great?


I had the same issue. Looks like things changed with newer PvOPs kernels (2.6.32+) and now the old fashioned setup of dedication of one CPU for dom0 (xm vcpu-pin 0 all 0) is causing performance issues and very high steal time on dom0. In my case I wasn't able to start any domU as the dom0 had not enough CPU time and it just ended with error (due to some timeout). Unfortunately nor Ian Campbell was able to tell me what is the reason of this behavior and what was changed.

Best regards,
--
Peter Viskup


--------------090404050205050008090005-- --===============2792574078173545958== 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 --===============2792574078173545958==-- From xen-users-bounces@lists.xen.org Mon Feb 04 02:51:54 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 04 Feb 2013 02:51: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 1U2C8N-0001To-Hv; Mon, 04 Feb 2013 02:50:15 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U2C8M-0001Tj-0x for xen-users@lists.xen.org; Mon, 04 Feb 2013 02:50:14 +0000 Received: from [85.158.137.99:33370] by server-9.bemta-3.messagelabs.com id BE/2B-09484-5E12F015; Mon, 04 Feb 2013 02:50:13 +0000 X-Env-Sender: skupko.sk@gmail.com X-Msg-Ref: server-8.tower-217.messagelabs.com!1359946211!14407089!1 X-Originating-IP: [74.125.82.170] X-SpamReason: No, hits=0.1 required=7.0 tests=HTML_50_60,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 23894 invoked from network); 4 Feb 2013 02:50:12 -0000 Received: from mail-we0-f170.google.com (HELO mail-we0-f170.google.com) (74.125.82.170) by server-8.tower-217.messagelabs.com with RC4-SHA encrypted SMTP; 4 Feb 2013 02:50:12 -0000 Received: by mail-we0-f170.google.com with SMTP id z53so4568054wey.29 for ; Sun, 03 Feb 2013 18:50:11 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type; bh=FpJb6Y2He/HGrrJUkgHd1fGOTh0gFpOJQs8TQbg8Ppw=; b=idqQ5Zbq9HaY9JY7DYFEzyJOE8fix3YQgTXNNaigVot9lT0nDfye3d2FADnASYtGVr g+kzHy1Xx+HR4bahIqLhYkw/gxdM3vsZR+QgDqgIyLsxvfT1SDFEBoYMg/Dm8/FID8JR A49wck1rFYHwR8pAG5sXo5atuL9IXPIi0RynxbWWAXen+9BEwcbHUC2QbmOy8m+7/OeR LLsoffAQh6IySLIEcueOFLFME4nlaHYKmT7IVVQAopCbK9g02hNCKnTKnOcCtrYQtRaS LEFgjDqRfI58p/emq/YLpAhrFwzaXbl+u5/QN1moGe0+H+zNz9Zciea44Q0BE5xp9dvN Og0g== X-Received: by 10.180.95.166 with SMTP id dl6mr7833025wib.9.1359946211450; Sun, 03 Feb 2013 18:50:11 -0800 (PST) Received: from [192.168.30.208] (chello089173144208.chello.sk. [89.173.144.208]) by mx.google.com with ESMTPS id s10sm18868047wiw.4.2013.02.03.18.50.09 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sun, 03 Feb 2013 18:50:10 -0800 (PST) Message-ID: <510F21DC.5040609@gmail.com> Date: Mon, 04 Feb 2013 03:50:04 +0100 From: Peter Viskup User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:10.0.11) Gecko/20121122 Icedove/10.0.11 MIME-Version: 1.0 To: Linux Hack References: <510E93C1.6090905@gmail.com> In-Reply-To: Cc: "xen-users@lists.xen.org" Subject: Re: [Xen-users] high cpu usage on steal time X-BeenThere: xen-users@lists.xen.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="===============2792574078173545958==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org This is a multi-part message in MIME format. --===============2792574078173545958== Content-Type: multipart/alternative; boundary="------------090404050205050008090005" This is a multi-part message in MIME format. --------------090404050205050008090005 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit I don't want to step into discussion about my setup as I already discussed this here just some weeks before. Do you still experience the issue with higher steal time or we can disregard this your request for support? Do you see the steal time on dom0 or some domU? On 02/04/2013 01:44 AM, Linux Hack wrote: > Hi Peter, > > Seems things are going fine with minimum steal time cpu usage (vary > between 5-20) with Xen 4.1.4 and latest centos 5.9 xen kernel. > > What is the kernel you are running on your server? > > > > On Sun, Feb 3, 2013 at 10:13 PM, Peter Viskup > wrote: > > On 02/02/2013 12:54 AM, Linux Hack wrote: > > Hi, > > One of the server is under high cpu usage and when checked > steal time is causing the high cpu usage. However I have > pinned the vcpu's for dom0 dedicatedly but still no luck. > > Any thought's that would be great? > > > I had the same issue. Looks like things changed with newer PvOPs > kernels (2.6.32+) and now the old fashioned setup of dedication of > one CPU for dom0 (xm vcpu-pin 0 all 0) is causing performance > issues and very high steal time on dom0. In my case I wasn't able > to start any domU as the dom0 had not enough CPU time and it just > ended with error (due to some timeout). Unfortunately nor Ian > Campbell was able to tell me what is the reason of this behavior > and what was changed. > > Best regards, > -- > Peter Viskup > > --------------090404050205050008090005 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit I don't want to step into discussion about my setup as I already discussed this here just some weeks before.
Do you still experience the issue with higher steal time or we can disregard this your request for support?
Do you see the steal time on dom0 or some domU?

On 02/04/2013 01:44 AM, Linux Hack wrote:
Hi Peter,

Seems things are going fine with minimum steal time cpu usage (vary between 5-20) with Xen 4.1.4 and latest centos 5.9 xen kernel.

What is the kernel you are running on your server?



On Sun, Feb 3, 2013 at 10:13 PM, Peter Viskup <skupko.sk@gmail.com> wrote:
On 02/02/2013 12:54 AM, Linux Hack wrote:
Hi,

One of the server is under high cpu usage and when checked steal time is causing the high cpu usage. However I have pinned the vcpu's for dom0 dedicatedly but still no luck.

Any thought's that would be great?


I had the same issue. Looks like things changed with newer PvOPs kernels (2.6.32+) and now the old fashioned setup of dedication of one CPU for dom0 (xm vcpu-pin 0 all 0) is causing performance issues and very high steal time on dom0. In my case I wasn't able to start any domU as the dom0 had not enough CPU time and it just ended with error (due to some timeout). Unfortunately nor Ian Campbell was able to tell me what is the reason of this behavior and what was changed.

Best regards,
--
Peter Viskup


--------------090404050205050008090005-- --===============2792574078173545958== 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 --===============2792574078173545958==-- From xen-users-bounces@lists.xen.org Mon Feb 04 05:09:43 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 04 Feb 2013 05:09: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 1U2EHn-0002zS-Nw; Mon, 04 Feb 2013 05:08:07 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U2EHm-0002zK-S8 for xen-users@lists.xen.org; Mon, 04 Feb 2013 05:08:07 +0000 Received: from [85.158.143.35:24535] by server-1.bemta-4.messagelabs.com id BC/3F-08839-5324F015; Mon, 04 Feb 2013 05:08:05 +0000 X-Env-Sender: basketboy@bk.ru X-Msg-Ref: server-4.tower-21.messagelabs.com!1359954484!5261367!1 X-Originating-IP: [94.100.177.100] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 23211 invoked from network); 4 Feb 2013 05:08:05 -0000 Received: from smtp40.i.mail.ru (HELO smtp40.i.mail.ru) (94.100.177.100) by server-4.tower-21.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 4 Feb 2013 05:08:05 -0000 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=bk.ru; s=mail; h=Content-Transfer-Encoding:Content-Type:Subject:To:MIME-Version:From:Date:Message-ID; bh=wPigSvWQj3RqXOnZdLYradf9aQ+QZlwLxo/ViGxgs38=; b=gNS43OkY+tbiIFby+56lgPCpxDSiSvgcd2gqom68YSo4E4a1NnTRu19+FpJHCnPrJEbJFWZDme7yErWacyF7RKX8iXEAWrxm71qHl397YUqzGZcIJ98In+daQ1rq3L6pUxIoKVtuGcvieoyvO3cG4GvPD95MI7UOLnhAkoTOHX0=; Received: from [78.36.60.25] (port=12983 helo=[10.168.2.113]) by smtp40.i.mail.ru with esmtpa (envelope-from ) id 1U2EHj-0006vl-34 for xen-users@lists.xen.org; Mon, 04 Feb 2013 09:08:03 +0400 Message-ID: <510F422D.5040501@bk.ru> Date: Mon, 04 Feb 2013 09:07:57 +0400 From: Andrey User-Agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/20130106 Thunderbird/17.0.2 MIME-Version: 1.0 To: "xen-users@lists.xen.org" X-Spam: Not detected X-Mras: Ok Subject: [Xen-users] domU with swap partition inside or outside X-BeenThere: xen-users@lists.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, What is the better way to organize domUs images and corresponding swap partition? Create one image file containing swap image inside or create separate partition as xen-create-image do (xvda1 for example). In this way grub should be written in xvda1 then (say if domU is updating or any grub install operations) in case of using pygrub and it can cause some problems for domU users. I guess in this case it's not possible to use pv-grub also as it requires full image file (xvda). With regards, Andrey. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Mon Feb 04 05:09:43 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 04 Feb 2013 05:09: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 1U2EHn-0002zS-Nw; Mon, 04 Feb 2013 05:08:07 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U2EHm-0002zK-S8 for xen-users@lists.xen.org; Mon, 04 Feb 2013 05:08:07 +0000 Received: from [85.158.143.35:24535] by server-1.bemta-4.messagelabs.com id BC/3F-08839-5324F015; Mon, 04 Feb 2013 05:08:05 +0000 X-Env-Sender: basketboy@bk.ru X-Msg-Ref: server-4.tower-21.messagelabs.com!1359954484!5261367!1 X-Originating-IP: [94.100.177.100] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 23211 invoked from network); 4 Feb 2013 05:08:05 -0000 Received: from smtp40.i.mail.ru (HELO smtp40.i.mail.ru) (94.100.177.100) by server-4.tower-21.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 4 Feb 2013 05:08:05 -0000 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=bk.ru; s=mail; h=Content-Transfer-Encoding:Content-Type:Subject:To:MIME-Version:From:Date:Message-ID; bh=wPigSvWQj3RqXOnZdLYradf9aQ+QZlwLxo/ViGxgs38=; b=gNS43OkY+tbiIFby+56lgPCpxDSiSvgcd2gqom68YSo4E4a1NnTRu19+FpJHCnPrJEbJFWZDme7yErWacyF7RKX8iXEAWrxm71qHl397YUqzGZcIJ98In+daQ1rq3L6pUxIoKVtuGcvieoyvO3cG4GvPD95MI7UOLnhAkoTOHX0=; Received: from [78.36.60.25] (port=12983 helo=[10.168.2.113]) by smtp40.i.mail.ru with esmtpa (envelope-from ) id 1U2EHj-0006vl-34 for xen-users@lists.xen.org; Mon, 04 Feb 2013 09:08:03 +0400 Message-ID: <510F422D.5040501@bk.ru> Date: Mon, 04 Feb 2013 09:07:57 +0400 From: Andrey User-Agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/20130106 Thunderbird/17.0.2 MIME-Version: 1.0 To: "xen-users@lists.xen.org" X-Spam: Not detected X-Mras: Ok Subject: [Xen-users] domU with swap partition inside or outside X-BeenThere: xen-users@lists.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, What is the better way to organize domUs images and corresponding swap partition? Create one image file containing swap image inside or create separate partition as xen-create-image do (xvda1 for example). In this way grub should be written in xvda1 then (say if domU is updating or any grub install operations) in case of using pygrub and it can cause some problems for domU users. I guess in this case it's not possible to use pv-grub also as it requires full image file (xvda). With regards, Andrey. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Mon Feb 04 07:00:55 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 04 Feb 2013 07:00: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 1U2G1R-0003m3-KW; Mon, 04 Feb 2013 06:59:21 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U2G1Q-0003ly-2X for xen-users@lists.xen.org; Mon, 04 Feb 2013 06:59:20 +0000 Received: from [85.158.143.99:18580] by server-2.bemta-4.messagelabs.com id 40/80-01597-74C5F015; Mon, 04 Feb 2013 06:59:19 +0000 X-Env-Sender: christian@holpert.de X-Msg-Ref: server-6.tower-216.messagelabs.com!1359961158!23696313!1 X-Originating-IP: [80.67.31.32] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogODAuNjcuMzEuMzIgPT4gNjA1Njc=\n X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 10229 invoked from network); 4 Feb 2013 06:59:18 -0000 Received: from smtprelay04.ispgateway.de (HELO smtprelay04.ispgateway.de) (80.67.31.32) by server-6.tower-216.messagelabs.com with SMTP; 4 Feb 2013 06:59:18 -0000 Received: from [217.83.80.98] (helo=colin.holpert.de) by smtprelay04.ispgateway.de with esmtpa (Exim 4.68) (envelope-from ) id 1U2G0Q-00042h-Mk for xen-users@lists.xen.org; Mon, 04 Feb 2013 07:58:18 +0100 Received: from PRO43287A006.holpert.de (unknown [10.75.157.20]) by colin.holpert.de (Postfix) with ESMTP id 639237FF3 for ; Mon, 4 Feb 2013 07:58:18 +0100 (CET) X-PGP-Fingerprint: D092 371C 931D 8F21 D71B 7A11 DC07 0F36 [RSA] X-PGP-Fingerprint: 8E3B 2F47 6673 B936 9EAE 52F3 4C8B C713 58C5 FFD6 [DH/DSS] X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9 Date: Mon, 04 Feb 2013 07:58:19 +0100 To: xen-users@lists.xen.org From: Christian Holpert In-Reply-To: References: Mime-Version: 1.0 Message-Id: X-Df-Sender: Y2hyaXN0aWFuQGhvbHBlcnQuZGU= Subject: Re: [Xen-users] I/O Scheduler X-BeenThere: xen-users@lists.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 At 04:02 03.02.2013, you wrote: >If its correct then how can we set the default I/O scheduler as noop = >for Xen VM's without getting inside of them? I mean is there any = >option that we can declare on DomU config itself? 1) compile domU kernel accordingly. 2) domU-config: extra =3D "elevator=3Dnoop" Regards, Christian -- = Markt-Apotheke Christian Holpert e.K., M=F6mbris http://www.marktapotheke.org - info@marktapotheke.org http://www.blue-essentials-shop.de - info@blue-essentials-shop.de Apotheker Christian Holpert Im Markthof 5 63776 M=F6mbris Tel.: 06029-1379 Fax: 9986589 Amtsgericht Aschaffenburg, HR.A, Registernummer 2165 _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Mon Feb 04 07:00:55 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 04 Feb 2013 07:00: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 1U2G1R-0003m3-KW; Mon, 04 Feb 2013 06:59:21 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U2G1Q-0003ly-2X for xen-users@lists.xen.org; Mon, 04 Feb 2013 06:59:20 +0000 Received: from [85.158.143.99:18580] by server-2.bemta-4.messagelabs.com id 40/80-01597-74C5F015; Mon, 04 Feb 2013 06:59:19 +0000 X-Env-Sender: christian@holpert.de X-Msg-Ref: server-6.tower-216.messagelabs.com!1359961158!23696313!1 X-Originating-IP: [80.67.31.32] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogODAuNjcuMzEuMzIgPT4gNjA1Njc=\n X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 10229 invoked from network); 4 Feb 2013 06:59:18 -0000 Received: from smtprelay04.ispgateway.de (HELO smtprelay04.ispgateway.de) (80.67.31.32) by server-6.tower-216.messagelabs.com with SMTP; 4 Feb 2013 06:59:18 -0000 Received: from [217.83.80.98] (helo=colin.holpert.de) by smtprelay04.ispgateway.de with esmtpa (Exim 4.68) (envelope-from ) id 1U2G0Q-00042h-Mk for xen-users@lists.xen.org; Mon, 04 Feb 2013 07:58:18 +0100 Received: from PRO43287A006.holpert.de (unknown [10.75.157.20]) by colin.holpert.de (Postfix) with ESMTP id 639237FF3 for ; Mon, 4 Feb 2013 07:58:18 +0100 (CET) X-PGP-Fingerprint: D092 371C 931D 8F21 D71B 7A11 DC07 0F36 [RSA] X-PGP-Fingerprint: 8E3B 2F47 6673 B936 9EAE 52F3 4C8B C713 58C5 FFD6 [DH/DSS] X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9 Date: Mon, 04 Feb 2013 07:58:19 +0100 To: xen-users@lists.xen.org From: Christian Holpert In-Reply-To: References: Mime-Version: 1.0 Message-Id: X-Df-Sender: Y2hyaXN0aWFuQGhvbHBlcnQuZGU= Subject: Re: [Xen-users] I/O Scheduler X-BeenThere: xen-users@lists.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 At 04:02 03.02.2013, you wrote: >If its correct then how can we set the default I/O scheduler as noop = >for Xen VM's without getting inside of them? I mean is there any = >option that we can declare on DomU config itself? 1) compile domU kernel accordingly. 2) domU-config: extra =3D "elevator=3Dnoop" Regards, Christian -- = Markt-Apotheke Christian Holpert e.K., M=F6mbris http://www.marktapotheke.org - info@marktapotheke.org http://www.blue-essentials-shop.de - info@blue-essentials-shop.de Apotheker Christian Holpert Im Markthof 5 63776 M=F6mbris Tel.: 06029-1379 Fax: 9986589 Amtsgericht Aschaffenburg, HR.A, Registernummer 2165 _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Mon Feb 04 07:22:37 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 04 Feb 2013 07:22: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 1U2GMa-0004RM-7s; Mon, 04 Feb 2013 07: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 1U2GMZ-0004RF-2q for xen-users@lists.xen.org; Mon, 04 Feb 2013 07:21:11 +0000 Received: from [85.158.139.83:56287] by server-14.bemta-5.messagelabs.com id 0F/D7-06967-6616F015; Mon, 04 Feb 2013 07:21:10 +0000 X-Env-Sender: juergen.gross@ts.fujitsu.com X-Msg-Ref: server-7.tower-182.messagelabs.com!1359962469!26711865!1 X-Originating-IP: [80.70.172.51] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogODAuNzAuMTcyLjUxID0+IDE5Nzk3MQ==\n X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 18992 invoked from network); 4 Feb 2013 07:21:09 -0000 Received: from dgate20.ts.fujitsu.com (HELO dgate20.ts.fujitsu.com) (80.70.172.51) by server-7.tower-182.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 4 Feb 2013 07:21:09 -0000 DomainKey-Signature: s=s1536a; d=ts.fujitsu.com; c=nofws; q=dns; h=X-SBRSScore:X-IronPort-AV:Received:X-IronPort-AV: Received:Received:Message-ID:Date:From:Organization: User-Agent:MIME-Version:To:CC:Subject:References: In-Reply-To:Content-Type:Content-Transfer-Encoding; b=biwKZwHHTsJVkz1cEXMljVbvnvzQpKEjIBzCUTJtaIeqrpI7vaM/x79L SYdX01sh8hNDkmirkBeOxN0MXVNgO7dBlLz8wyfKMWE5gqtpy3mlPFtTV AiG5hcof8qDuYWLEYYh+qLbUWsA32vfUrIGG2g92HMp0DEtvgsVfQQSYT pPTju7t2SukDRXLDAY06NOiI9GJv6QoDBxRPU4jP+Wui5Zaz8IR1BoP7W Ydpt/zOtGBT9RlCnN9DbIk6Sni+je; DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=ts.fujitsu.com; i=@ts.fujitsu.com; q=dns/txt; s=s1536b; t=1359962470; x=1391498470; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=7jZdBP52fDQd7hEkurdIFb/4mNc3fOncEzQOEqtISdU=; b=MsSVtDrsCeteQ37Y+dmrq7juvDGpOYY36ZLW+Rr6mjcqHHkczpsR9eaq Qs4zqclN/zvVzkzpmCGcxqaHNw0khFIeMgyXLBw5WA5+3vL66j9fWfiTO aIt3n8mvXu0e5E5idJ3NjMsgZA+eb+EXrWhr9ash+CfTPNkwqcLVqx2sq Q8I0QvUdbb9hvLRgV3+brJ3hKSuk5JL5hkTwfM6tTr10zIrCThNTqnGSy x84dGIUSDRNBGQ0/Q22mA1B7OAMt9; X-SBRSScore: None X-IronPort-AV: E=Sophos;i="4.84,597,1355094000"; d="scan'208";a="114976470" Received: from abgdgate30u.abg.fsc.net ([172.25.138.66]) by dgate20u.abg.fsc.net with ESMTP; 04 Feb 2013 08:21:09 +0100 X-IronPort-AV: E=Sophos;i="4.84,597,1355094000"; d="scan'208";a="157198798" Received: from sanpedro.mch.fsc.net ([172.17.20.6]) by abgdgate30u.abg.fsc.net with SMTP; 04 Feb 2013 08:21:09 +0100 Received: from [172.17.21.50] (verdon.osd.mch.fsc.net [172.17.21.50]) by sanpedro.mch.fsc.net (Postfix) with ESMTP id 4E7DF9703C6; Mon, 4 Feb 2013 08:21:09 +0100 (CET) Message-ID: <510F6165.9010908@ts.fujitsu.com> Date: Mon, 04 Feb 2013 08:21:09 +0100 From: Juergen Gross Organization: Fujitsu Technology Solutions GmbH User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.16) Gecko/20121215 Iceowl/1.0b1 Icedove/3.0.11 MIME-Version: 1.0 To: Linux Hack References: In-Reply-To: Cc: "xen-users@lists.xen.org" Subject: Re: [Xen-users] xl cpupool X-BeenThere: xen-users@lists.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, Am 02.02.2013 00:53, schrieb Linux Hack: > Hi, > > Would it possible to create cpupools with xl after the server boot and > then assign one cpu-pool to dom0 and another one for dom-u's? Yes. You have to (assuming Xen 4.2): 1. remove cpus from Pool-0 with "xl cpupool-cpu-remove" 2. reduce number of dom0 cpus to fit to reduced Pool-0 with "xl vcpu-set" 3. create the domU cpupool with "xl cpupool-create" 4. assign the free cpus to the new cpupool ("xl cpupool-cpu-add") 5. create the domUs with "pool=" to start them in the new cpupool (either in the config files of the domUs or as parameter of "xl create" > Also is there any change to make this work on server startup? You would have to add an init script in dom0. Juergen -- Juergen Gross Principal Developer Operating Systems PBG PDG ES&S SWE OS6 Telephone: +49 (0) 89 3222 2967 Fujitsu Technology Solutions e-mail: juergen.gross@ts.fujitsu.com Domagkstr. 28 Internet: ts.fujitsu.com D-80807 Muenchen Company details: ts.fujitsu.com/imprint.html _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Mon Feb 04 07:22:37 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 04 Feb 2013 07:22: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 1U2GMa-0004RM-7s; Mon, 04 Feb 2013 07: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 1U2GMZ-0004RF-2q for xen-users@lists.xen.org; Mon, 04 Feb 2013 07:21:11 +0000 Received: from [85.158.139.83:56287] by server-14.bemta-5.messagelabs.com id 0F/D7-06967-6616F015; Mon, 04 Feb 2013 07:21:10 +0000 X-Env-Sender: juergen.gross@ts.fujitsu.com X-Msg-Ref: server-7.tower-182.messagelabs.com!1359962469!26711865!1 X-Originating-IP: [80.70.172.51] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogODAuNzAuMTcyLjUxID0+IDE5Nzk3MQ==\n X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 18992 invoked from network); 4 Feb 2013 07:21:09 -0000 Received: from dgate20.ts.fujitsu.com (HELO dgate20.ts.fujitsu.com) (80.70.172.51) by server-7.tower-182.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 4 Feb 2013 07:21:09 -0000 DomainKey-Signature: s=s1536a; d=ts.fujitsu.com; c=nofws; q=dns; h=X-SBRSScore:X-IronPort-AV:Received:X-IronPort-AV: Received:Received:Message-ID:Date:From:Organization: User-Agent:MIME-Version:To:CC:Subject:References: In-Reply-To:Content-Type:Content-Transfer-Encoding; b=biwKZwHHTsJVkz1cEXMljVbvnvzQpKEjIBzCUTJtaIeqrpI7vaM/x79L SYdX01sh8hNDkmirkBeOxN0MXVNgO7dBlLz8wyfKMWE5gqtpy3mlPFtTV AiG5hcof8qDuYWLEYYh+qLbUWsA32vfUrIGG2g92HMp0DEtvgsVfQQSYT pPTju7t2SukDRXLDAY06NOiI9GJv6QoDBxRPU4jP+Wui5Zaz8IR1BoP7W Ydpt/zOtGBT9RlCnN9DbIk6Sni+je; DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=ts.fujitsu.com; i=@ts.fujitsu.com; q=dns/txt; s=s1536b; t=1359962470; x=1391498470; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=7jZdBP52fDQd7hEkurdIFb/4mNc3fOncEzQOEqtISdU=; b=MsSVtDrsCeteQ37Y+dmrq7juvDGpOYY36ZLW+Rr6mjcqHHkczpsR9eaq Qs4zqclN/zvVzkzpmCGcxqaHNw0khFIeMgyXLBw5WA5+3vL66j9fWfiTO aIt3n8mvXu0e5E5idJ3NjMsgZA+eb+EXrWhr9ash+CfTPNkwqcLVqx2sq Q8I0QvUdbb9hvLRgV3+brJ3hKSuk5JL5hkTwfM6tTr10zIrCThNTqnGSy x84dGIUSDRNBGQ0/Q22mA1B7OAMt9; X-SBRSScore: None X-IronPort-AV: E=Sophos;i="4.84,597,1355094000"; d="scan'208";a="114976470" Received: from abgdgate30u.abg.fsc.net ([172.25.138.66]) by dgate20u.abg.fsc.net with ESMTP; 04 Feb 2013 08:21:09 +0100 X-IronPort-AV: E=Sophos;i="4.84,597,1355094000"; d="scan'208";a="157198798" Received: from sanpedro.mch.fsc.net ([172.17.20.6]) by abgdgate30u.abg.fsc.net with SMTP; 04 Feb 2013 08:21:09 +0100 Received: from [172.17.21.50] (verdon.osd.mch.fsc.net [172.17.21.50]) by sanpedro.mch.fsc.net (Postfix) with ESMTP id 4E7DF9703C6; Mon, 4 Feb 2013 08:21:09 +0100 (CET) Message-ID: <510F6165.9010908@ts.fujitsu.com> Date: Mon, 04 Feb 2013 08:21:09 +0100 From: Juergen Gross Organization: Fujitsu Technology Solutions GmbH User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.16) Gecko/20121215 Iceowl/1.0b1 Icedove/3.0.11 MIME-Version: 1.0 To: Linux Hack References: In-Reply-To: Cc: "xen-users@lists.xen.org" Subject: Re: [Xen-users] xl cpupool X-BeenThere: xen-users@lists.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, Am 02.02.2013 00:53, schrieb Linux Hack: > Hi, > > Would it possible to create cpupools with xl after the server boot and > then assign one cpu-pool to dom0 and another one for dom-u's? Yes. You have to (assuming Xen 4.2): 1. remove cpus from Pool-0 with "xl cpupool-cpu-remove" 2. reduce number of dom0 cpus to fit to reduced Pool-0 with "xl vcpu-set" 3. create the domU cpupool with "xl cpupool-create" 4. assign the free cpus to the new cpupool ("xl cpupool-cpu-add") 5. create the domUs with "pool=" to start them in the new cpupool (either in the config files of the domUs or as parameter of "xl create" > Also is there any change to make this work on server startup? You would have to add an init script in dom0. Juergen -- Juergen Gross Principal Developer Operating Systems PBG PDG ES&S SWE OS6 Telephone: +49 (0) 89 3222 2967 Fujitsu Technology Solutions e-mail: juergen.gross@ts.fujitsu.com Domagkstr. 28 Internet: ts.fujitsu.com D-80807 Muenchen Company details: ts.fujitsu.com/imprint.html _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Mon Feb 04 09:40:46 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 04 Feb 2013 09:40: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 1U2IWI-000775-35; Mon, 04 Feb 2013 09:39:22 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U2IWH-000770-DN for Xen-users@lists.xen.org; Mon, 04 Feb 2013 09:39:21 +0000 Received: from [85.158.143.99:30900] by server-3.bemta-4.messagelabs.com id 6B/EB-08920-8C18F015; Mon, 04 Feb 2013 09:39:20 +0000 X-Env-Sender: Ian.Campbell@citrix.com X-Msg-Ref: server-5.tower-216.messagelabs.com!1359970740!29155464!1 X-Originating-IP: [46.33.159.39] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNDYuMzMuMTU5LjM5ID0+IDIwNTkz\n X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 15277 invoked from network); 4 Feb 2013 09:39:00 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (46.33.159.39) by server-5.tower-216.messagelabs.com with RC4-SHA encrypted SMTP; 4 Feb 2013 09:39:00 -0000 X-IronPort-AV: E=Sophos;i="4.84,598,1355097600"; d="scan'208";a="1110522" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 04 Feb 2013 09:39:01 +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.297.1; Mon, 4 Feb 2013 09:39:00 +0000 Message-ID: <1359970738.5281.5.camel@zakaz.uk.xensource.com> From: Ian Campbell To: Min Lee Date: Mon, 4 Feb 2013 09:38:58 +0000 In-Reply-To: <510B0CD5.3060905@gatech.edu> References: <510B0CD5.3060905@gatech.edu> Organization: Citrix Systems, Inc. X-Mailer: Evolution 3.4.4-1 MIME-Version: 1.0 Cc: "Xen-users@lists.xen.org" Subject: Re: [Xen-users] dom0's layout on physical 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 Fri, 2013-02-01 at 00:31 +0000, Min Lee wrote: > Hello, all > I thought dom0 is layed out on physical memory starting 0, linearly, but > this message, > > (XEN) *** LOADING DOMAIN 0 *** > (XEN) Xen kernel: 64-bit, lsb, compat32 > (XEN) Dom0 kernel: 64-bit, PAE, lsb, paddr 0x1000000 -> 0x1d87000 > (XEN) PHYSICAL MEMORY ARRANGEMENT: > (XEN) Dom0 alloc.: 0000000c14000000->0000000c18000000 (498514 pages to > be allocated) > > shows the address range 0000000c14000000->0000000c18000000 , > what is this? That is the virtual address range. The start of day memory layout is described in http://xenbits.xen.org/docs/unstable/hypercall/include,public,xen.h.html#incontents_startofday > it's 64MB range and why 64MB from Dom0 is located here? This is the size of the initial mapping given your kenrel and initrd size etc. > I think 498514 pages will be allocated later, but where, exactly?? IIRC the kernel will map it as part of its initialisation, init_memory_mapping() in Linux perhaps? > if dom0's memory is partitioned into several places, > then, what happens to their GPFN?? I'm not sure I understand this question. Ian. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Mon Feb 04 09:40:46 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 04 Feb 2013 09:40: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 1U2IWI-000775-35; Mon, 04 Feb 2013 09:39:22 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U2IWH-000770-DN for Xen-users@lists.xen.org; Mon, 04 Feb 2013 09:39:21 +0000 Received: from [85.158.143.99:30900] by server-3.bemta-4.messagelabs.com id 6B/EB-08920-8C18F015; Mon, 04 Feb 2013 09:39:20 +0000 X-Env-Sender: Ian.Campbell@citrix.com X-Msg-Ref: server-5.tower-216.messagelabs.com!1359970740!29155464!1 X-Originating-IP: [46.33.159.39] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNDYuMzMuMTU5LjM5ID0+IDIwNTkz\n X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 15277 invoked from network); 4 Feb 2013 09:39:00 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (46.33.159.39) by server-5.tower-216.messagelabs.com with RC4-SHA encrypted SMTP; 4 Feb 2013 09:39:00 -0000 X-IronPort-AV: E=Sophos;i="4.84,598,1355097600"; d="scan'208";a="1110522" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 04 Feb 2013 09:39:01 +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.297.1; Mon, 4 Feb 2013 09:39:00 +0000 Message-ID: <1359970738.5281.5.camel@zakaz.uk.xensource.com> From: Ian Campbell To: Min Lee Date: Mon, 4 Feb 2013 09:38:58 +0000 In-Reply-To: <510B0CD5.3060905@gatech.edu> References: <510B0CD5.3060905@gatech.edu> Organization: Citrix Systems, Inc. X-Mailer: Evolution 3.4.4-1 MIME-Version: 1.0 Cc: "Xen-users@lists.xen.org" Subject: Re: [Xen-users] dom0's layout on physical 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 Fri, 2013-02-01 at 00:31 +0000, Min Lee wrote: > Hello, all > I thought dom0 is layed out on physical memory starting 0, linearly, but > this message, > > (XEN) *** LOADING DOMAIN 0 *** > (XEN) Xen kernel: 64-bit, lsb, compat32 > (XEN) Dom0 kernel: 64-bit, PAE, lsb, paddr 0x1000000 -> 0x1d87000 > (XEN) PHYSICAL MEMORY ARRANGEMENT: > (XEN) Dom0 alloc.: 0000000c14000000->0000000c18000000 (498514 pages to > be allocated) > > shows the address range 0000000c14000000->0000000c18000000 , > what is this? That is the virtual address range. The start of day memory layout is described in http://xenbits.xen.org/docs/unstable/hypercall/include,public,xen.h.html#incontents_startofday > it's 64MB range and why 64MB from Dom0 is located here? This is the size of the initial mapping given your kenrel and initrd size etc. > I think 498514 pages will be allocated later, but where, exactly?? IIRC the kernel will map it as part of its initialisation, init_memory_mapping() in Linux perhaps? > if dom0's memory is partitioned into several places, > then, what happens to their GPFN?? I'm not sure I understand this question. Ian. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Mon Feb 04 09:42:09 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 04 Feb 2013 09:42: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 1U2IXv-0007H1-7I; Mon, 04 Feb 2013 09:41:03 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U2IXt-0007Gk-Iw for xen-users@lists.xen.org; Mon, 04 Feb 2013 09:41:01 +0000 Received: from [85.158.139.83:9151] by server-4.bemta-5.messagelabs.com id 05/09-29496-C228F015; Mon, 04 Feb 2013 09:41:00 +0000 X-Env-Sender: Ian.Campbell@citrix.com X-Msg-Ref: server-12.tower-182.messagelabs.com!1359970860!30692758!1 X-Originating-IP: [46.33.159.39] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNDYuMzMuMTU5LjM5ID0+IDIwNTkz\n X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 5274 invoked from network); 4 Feb 2013 09:41:00 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (46.33.159.39) by server-12.tower-182.messagelabs.com with RC4-SHA encrypted SMTP; 4 Feb 2013 09:41:00 -0000 X-IronPort-AV: E=Sophos;i="4.84,598,1355097600"; d="scan'208";a="1110587" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 04 Feb 2013 09:41:01 +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.297.1; Mon, 4 Feb 2013 09:40:59 +0000 Message-ID: <1359970858.5281.6.camel@zakaz.uk.xensource.com> From: Ian Campbell To: Linux Hack Date: Mon, 4 Feb 2013 09:40:58 +0000 In-Reply-To: References: Organization: Citrix Systems, Inc. X-Mailer: Evolution 3.4.4-1 MIME-Version: 1.0 Cc: "xen-users@lists.xen.org" Subject: Re: [Xen-users] Regarding sched-credit weight and caps X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: 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, 2013-02-01 at 03:58 +0000, Linux Hack wrote: > Is there any specific good weight and cap value for Dom-0 which keep > more stable the Dom-0? There are some hints about this on the wiki (which was the first hit on google for "xen dom0 weight"): http://wiki.xensource.com/wiki/XenBestPractices#Xen_credit_scheduler_domain_weights_and_making_sure_dom0_gets_enough_CPU_time_to_serve_IO_requests_.28disk.2Fnet.29 Ian. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Mon Feb 04 09:42:09 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 04 Feb 2013 09:42: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 1U2IXv-0007H1-7I; Mon, 04 Feb 2013 09:41:03 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U2IXt-0007Gk-Iw for xen-users@lists.xen.org; Mon, 04 Feb 2013 09:41:01 +0000 Received: from [85.158.139.83:9151] by server-4.bemta-5.messagelabs.com id 05/09-29496-C228F015; Mon, 04 Feb 2013 09:41:00 +0000 X-Env-Sender: Ian.Campbell@citrix.com X-Msg-Ref: server-12.tower-182.messagelabs.com!1359970860!30692758!1 X-Originating-IP: [46.33.159.39] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNDYuMzMuMTU5LjM5ID0+IDIwNTkz\n X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 5274 invoked from network); 4 Feb 2013 09:41:00 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (46.33.159.39) by server-12.tower-182.messagelabs.com with RC4-SHA encrypted SMTP; 4 Feb 2013 09:41:00 -0000 X-IronPort-AV: E=Sophos;i="4.84,598,1355097600"; d="scan'208";a="1110587" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 04 Feb 2013 09:41:01 +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.297.1; Mon, 4 Feb 2013 09:40:59 +0000 Message-ID: <1359970858.5281.6.camel@zakaz.uk.xensource.com> From: Ian Campbell To: Linux Hack Date: Mon, 4 Feb 2013 09:40:58 +0000 In-Reply-To: References: Organization: Citrix Systems, Inc. X-Mailer: Evolution 3.4.4-1 MIME-Version: 1.0 Cc: "xen-users@lists.xen.org" Subject: Re: [Xen-users] Regarding sched-credit weight and caps X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: 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, 2013-02-01 at 03:58 +0000, Linux Hack wrote: > Is there any specific good weight and cap value for Dom-0 which keep > more stable the Dom-0? There are some hints about this on the wiki (which was the first hit on google for "xen dom0 weight"): http://wiki.xensource.com/wiki/XenBestPractices#Xen_credit_scheduler_domain_weights_and_making_sure_dom0_gets_enough_CPU_time_to_serve_IO_requests_.28disk.2Fnet.29 Ian. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Mon Feb 04 09:54:19 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 04 Feb 2013 09:54: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 1U2Ija-00086P-M7; Mon, 04 Feb 2013 09:53:06 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U2IjZ-00086I-Ve for xen-users@lists.xen.org; Mon, 04 Feb 2013 09:53:06 +0000 Received: from [85.158.139.83:29902] by server-2.bemta-5.messagelabs.com id F4/35-16911-1058F015; Mon, 04 Feb 2013 09:53:05 +0000 X-Env-Sender: Ian.Campbell@citrix.com X-Msg-Ref: server-10.tower-182.messagelabs.com!1359971584!30953213!1 X-Originating-IP: [46.33.159.39] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNDYuMzMuMTU5LjM5ID0+IDIwNTkz\n X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 3675 invoked from network); 4 Feb 2013 09:53:04 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (46.33.159.39) by server-10.tower-182.messagelabs.com with RC4-SHA encrypted SMTP; 4 Feb 2013 09:53:04 -0000 X-IronPort-AV: E=Sophos;i="4.84,598,1355097600"; d="scan'208";a="1111146" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 04 Feb 2013 09:53:04 +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.297.1; Mon, 4 Feb 2013 09:53:04 +0000 Message-ID: <1359971583.5281.11.camel@zakaz.uk.xensource.com> From: Ian Campbell To: digvijay chauhan Date: Mon, 4 Feb 2013 09:53:03 +0000 In-Reply-To: References: Organization: Citrix Systems, Inc. X-Mailer: Evolution 3.4.4-1 MIME-Version: 1.0 Cc: "xen-users@lists.xen.org" Subject: Re: [Xen-users] how to use sctp during live migration of vm with 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 Please do not cross post, http://wiki.xen.org/wiki/Asking_Xen_Devel_Questions and http://wiki.xen.org/wiki/Xen_Users_Netiquette both ask you not to. Since this is a users question I've moved devel to Bcc On Fri, 2013-02-01 at 14:18 +0000, digvijay chauhan wrote: > I want to carry out the performance analysis of transport > protocol i.e sctp so how can we achieve it.Instead of using tcp if we > have to use sctp how to do that? The xl migrate command takes a -s option which specifies the command to run to connect to the target, the default is to use ssh but you can supply any script you like. The script should take its stdin/stdout and connect them, via whatever means, to the stdin/stdout of "xl migrate-receive" running on the remote host. So you just need to arrange for "whatever means" to mean SCTP. If you have a netcat type utility for SCTP then it ought to be relatively straightforward. Ian. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Mon Feb 04 09:54:19 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 04 Feb 2013 09:54: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 1U2Ija-00086P-M7; Mon, 04 Feb 2013 09:53:06 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U2IjZ-00086I-Ve for xen-users@lists.xen.org; Mon, 04 Feb 2013 09:53:06 +0000 Received: from [85.158.139.83:29902] by server-2.bemta-5.messagelabs.com id F4/35-16911-1058F015; Mon, 04 Feb 2013 09:53:05 +0000 X-Env-Sender: Ian.Campbell@citrix.com X-Msg-Ref: server-10.tower-182.messagelabs.com!1359971584!30953213!1 X-Originating-IP: [46.33.159.39] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNDYuMzMuMTU5LjM5ID0+IDIwNTkz\n X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 3675 invoked from network); 4 Feb 2013 09:53:04 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (46.33.159.39) by server-10.tower-182.messagelabs.com with RC4-SHA encrypted SMTP; 4 Feb 2013 09:53:04 -0000 X-IronPort-AV: E=Sophos;i="4.84,598,1355097600"; d="scan'208";a="1111146" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 04 Feb 2013 09:53:04 +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.297.1; Mon, 4 Feb 2013 09:53:04 +0000 Message-ID: <1359971583.5281.11.camel@zakaz.uk.xensource.com> From: Ian Campbell To: digvijay chauhan Date: Mon, 4 Feb 2013 09:53:03 +0000 In-Reply-To: References: Organization: Citrix Systems, Inc. X-Mailer: Evolution 3.4.4-1 MIME-Version: 1.0 Cc: "xen-users@lists.xen.org" Subject: Re: [Xen-users] how to use sctp during live migration of vm with 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 Please do not cross post, http://wiki.xen.org/wiki/Asking_Xen_Devel_Questions and http://wiki.xen.org/wiki/Xen_Users_Netiquette both ask you not to. Since this is a users question I've moved devel to Bcc On Fri, 2013-02-01 at 14:18 +0000, digvijay chauhan wrote: > I want to carry out the performance analysis of transport > protocol i.e sctp so how can we achieve it.Instead of using tcp if we > have to use sctp how to do that? The xl migrate command takes a -s option which specifies the command to run to connect to the target, the default is to use ssh but you can supply any script you like. The script should take its stdin/stdout and connect them, via whatever means, to the stdin/stdout of "xl migrate-receive" running on the remote host. So you just need to arrange for "whatever means" to mean SCTP. If you have a netcat type utility for SCTP then it ought to be relatively straightforward. Ian. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Mon Feb 04 10:03:06 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 04 Feb 2013 10:03: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 1U2IsG-0000Er-DC; Mon, 04 Feb 2013 10:02:04 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U2IsE-0000El-LF for xen-users@lists.xen.org; Mon, 04 Feb 2013 10:02:02 +0000 Received: from [193.109.254.147:7364] by server-8.bemta-14.messagelabs.com id BF/69-17325-9178F015; Mon, 04 Feb 2013 10:02:01 +0000 X-Env-Sender: pigeon@pigeond.net X-Msg-Ref: server-10.tower-27.messagelabs.com!1359972062!3592429!1 X-Originating-IP: [203.59.1.224] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogMjAzLjU5LjEuMjI0ID0+IDE3MzEz\n, ML_RADAR_SPEW_LINKS_18, spamassassin: X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 7528 invoked from network); 4 Feb 2013 10:01:04 -0000 Received: from icp-osb-irony-out7.external.iinet.net.au (HELO icp-osb-irony-out7.external.iinet.net.au) (203.59.1.224) by server-10.tower-27.messagelabs.com with SMTP; 4 Feb 2013 10:01:04 -0000 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AqoFAESGD1F8lWUl/2dsb2JhbAAqGoYBuTgWc4JgZxQ0iHENLJ0PoD2OKYMpA5YehhOFKIUXgxA X-IronPort-AV: E=Sophos;i="4.84,598,1355068800"; d="scan'208";a="92257672" Received: from unknown (HELO torankusu.pigeond.net) ([124.149.101.37]) by icp-osb-irony-out7.iinet.net.au with ESMTP; 04 Feb 2013 18:01:00 +0800 Received: from furiza.pigeond.net ([192.168.42.20]:40083 helo=pigeond.net) by torankusu.pigeond.net with esmtp (Exim 4.72) (envelope-from ) id 1U2IrD-0000xp-Cw for xen-users@lists.xen.org; Mon, 04 Feb 2013 21:00:59 +1100 Date: Mon, 4 Feb 2013 21:00:50 +1100 From: Howell Tam To: xen-users@lists.xen.org Message-ID: <20130204210050.5cea3436@pigeond.net> Organization: pigeond.net X-Mailer: Claws Mail 3.8.1 (GTK+ 2.24.13; x86_64-pc-linux-gnu) Mime-Version: 1.0 Subject: [Xen-users] Radeon 7770 fglrx Dom0 GL glitches X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: 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 using a Radeon HD 7770 on a Linux Dom0, using the closed source fglrx driver (13.1). For certain 3d games, I'm seeing this weird glitches. It feels like the alpha channel for certain textures are not working properly. Screenshots: Normal Linux: http://en.zimagez.com/zimage/screenshot-280113-185031.php Dom0: http://en.zimagez.com/zimage/screenshot-280113-211459.php The normal linux host and the dom0 are running the same system, i.e. same kernel, debian, same fglrx driver, etc. Although of course Dom0 was setup to have less memory and cpu than when running as the normal host. Mind you, this could well be an fglrx bug, and, this bug only happens with my Radeon HD 7770. I also have an HD 6770 and it does not have the same problem. But since the problem only occurs with Xen Dom0, maybe this has exposed some weird bug? And FWIW, the card under domU with VGA passthrough is fine too. Thanks. -- Regards, Howell. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Mon Feb 04 10:03:06 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 04 Feb 2013 10:03: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 1U2IsG-0000Er-DC; Mon, 04 Feb 2013 10:02:04 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U2IsE-0000El-LF for xen-users@lists.xen.org; Mon, 04 Feb 2013 10:02:02 +0000 Received: from [193.109.254.147:7364] by server-8.bemta-14.messagelabs.com id BF/69-17325-9178F015; Mon, 04 Feb 2013 10:02:01 +0000 X-Env-Sender: pigeon@pigeond.net X-Msg-Ref: server-10.tower-27.messagelabs.com!1359972062!3592429!1 X-Originating-IP: [203.59.1.224] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogMjAzLjU5LjEuMjI0ID0+IDE3MzEz\n, ML_RADAR_SPEW_LINKS_18, spamassassin: X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 7528 invoked from network); 4 Feb 2013 10:01:04 -0000 Received: from icp-osb-irony-out7.external.iinet.net.au (HELO icp-osb-irony-out7.external.iinet.net.au) (203.59.1.224) by server-10.tower-27.messagelabs.com with SMTP; 4 Feb 2013 10:01:04 -0000 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AqoFAESGD1F8lWUl/2dsb2JhbAAqGoYBuTgWc4JgZxQ0iHENLJ0PoD2OKYMpA5YehhOFKIUXgxA X-IronPort-AV: E=Sophos;i="4.84,598,1355068800"; d="scan'208";a="92257672" Received: from unknown (HELO torankusu.pigeond.net) ([124.149.101.37]) by icp-osb-irony-out7.iinet.net.au with ESMTP; 04 Feb 2013 18:01:00 +0800 Received: from furiza.pigeond.net ([192.168.42.20]:40083 helo=pigeond.net) by torankusu.pigeond.net with esmtp (Exim 4.72) (envelope-from ) id 1U2IrD-0000xp-Cw for xen-users@lists.xen.org; Mon, 04 Feb 2013 21:00:59 +1100 Date: Mon, 4 Feb 2013 21:00:50 +1100 From: Howell Tam To: xen-users@lists.xen.org Message-ID: <20130204210050.5cea3436@pigeond.net> Organization: pigeond.net X-Mailer: Claws Mail 3.8.1 (GTK+ 2.24.13; x86_64-pc-linux-gnu) Mime-Version: 1.0 Subject: [Xen-users] Radeon 7770 fglrx Dom0 GL glitches X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: 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 using a Radeon HD 7770 on a Linux Dom0, using the closed source fglrx driver (13.1). For certain 3d games, I'm seeing this weird glitches. It feels like the alpha channel for certain textures are not working properly. Screenshots: Normal Linux: http://en.zimagez.com/zimage/screenshot-280113-185031.php Dom0: http://en.zimagez.com/zimage/screenshot-280113-211459.php The normal linux host and the dom0 are running the same system, i.e. same kernel, debian, same fglrx driver, etc. Although of course Dom0 was setup to have less memory and cpu than when running as the normal host. Mind you, this could well be an fglrx bug, and, this bug only happens with my Radeon HD 7770. I also have an HD 6770 and it does not have the same problem. But since the problem only occurs with Xen Dom0, maybe this has exposed some weird bug? And FWIW, the card under domU with VGA passthrough is fine too. Thanks. -- Regards, Howell. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Mon Feb 04 10:08:44 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 04 Feb 2013 10:08: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 1U2Ixn-0000cm-6T; Mon, 04 Feb 2013 10:07:47 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U2Ixl-0000cW-0W for xen-users@lists.xen.org; Mon, 04 Feb 2013 10:07:45 +0000 Received: from [193.109.254.147:8662] by server-6.bemta-14.messagelabs.com id 9A/2B-12010-0788F015; Mon, 04 Feb 2013 10:07:44 +0000 X-Env-Sender: Ian.Campbell@citrix.com X-Msg-Ref: server-9.tower-27.messagelabs.com!1359972463!9464640!1 X-Originating-IP: [46.33.159.39] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNDYuMzMuMTU5LjM5ID0+IDIwNTkz\n X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 9360 invoked from network); 4 Feb 2013 10:07:43 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (46.33.159.39) by server-9.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 4 Feb 2013 10:07:43 -0000 X-IronPort-AV: E=Sophos;i="4.84,598,1355097600"; d="scan'208";a="1111785" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 04 Feb 2013 10:07: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.297.1; Mon, 4 Feb 2013 10:07:43 +0000 Message-ID: <1359972462.5281.17.camel@zakaz.uk.xensource.com> From: Ian Campbell To: Paul Stimpson Date: Mon, 4 Feb 2013 10:07:42 +0000 In-Reply-To: <510BF806.2010504@stimpsonfamily.co.uk> References: <510BF806.2010504@stimpsonfamily.co.uk> Organization: Citrix Systems, Inc. X-Mailer: Evolution 3.4.4-1 MIME-Version: 1.0 Cc: "xen-users@lists.xen.org" Subject: Re: [Xen-users] Guest not starting after hardware migration X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: 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, 2013-02-01 at 17:14 +0000, Paul Stimpson wrote: > The machine looks like it boots OK and the host and Linux guest start > fine. The Windows VM steadfastly refuses to boot and if I do an xl > create on it, I get the following messages: > > libxl: error: libxl_create.c:420:libxl_domain_make: domain creation fail > libxl: error: libxl_create.c:646:initiate_domain_create: cannot make domain: -3 This seems to correspond to -ESRCH from xc_domain_create. > libxl: error: libxl.c:1392:libxl__destroy_domid: non-existant domain -1 > libxl: error: libxl.c:1356:domain_destrpy_callback: unable to destroy guest with domid 4294967295 > libxl: error: libxl_create.c:1152:domcreate_destruction_cb: unable to destroy domain 4294967295 following failed creation > > These errors don't seem to contain any useful information to me "xl -vvv create ..." might give you some more information, or you might see some useful messages in "xl dmesg". It might be useful to see the complete logs in case something interesting is hidden there. What does your guest configuration file contain? Ian. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Mon Feb 04 10:08:44 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 04 Feb 2013 10:08: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 1U2Ixn-0000cm-6T; Mon, 04 Feb 2013 10:07:47 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U2Ixl-0000cW-0W for xen-users@lists.xen.org; Mon, 04 Feb 2013 10:07:45 +0000 Received: from [193.109.254.147:8662] by server-6.bemta-14.messagelabs.com id 9A/2B-12010-0788F015; Mon, 04 Feb 2013 10:07:44 +0000 X-Env-Sender: Ian.Campbell@citrix.com X-Msg-Ref: server-9.tower-27.messagelabs.com!1359972463!9464640!1 X-Originating-IP: [46.33.159.39] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNDYuMzMuMTU5LjM5ID0+IDIwNTkz\n X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 9360 invoked from network); 4 Feb 2013 10:07:43 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (46.33.159.39) by server-9.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 4 Feb 2013 10:07:43 -0000 X-IronPort-AV: E=Sophos;i="4.84,598,1355097600"; d="scan'208";a="1111785" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 04 Feb 2013 10:07: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.297.1; Mon, 4 Feb 2013 10:07:43 +0000 Message-ID: <1359972462.5281.17.camel@zakaz.uk.xensource.com> From: Ian Campbell To: Paul Stimpson Date: Mon, 4 Feb 2013 10:07:42 +0000 In-Reply-To: <510BF806.2010504@stimpsonfamily.co.uk> References: <510BF806.2010504@stimpsonfamily.co.uk> Organization: Citrix Systems, Inc. X-Mailer: Evolution 3.4.4-1 MIME-Version: 1.0 Cc: "xen-users@lists.xen.org" Subject: Re: [Xen-users] Guest not starting after hardware migration X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: 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, 2013-02-01 at 17:14 +0000, Paul Stimpson wrote: > The machine looks like it boots OK and the host and Linux guest start > fine. The Windows VM steadfastly refuses to boot and if I do an xl > create on it, I get the following messages: > > libxl: error: libxl_create.c:420:libxl_domain_make: domain creation fail > libxl: error: libxl_create.c:646:initiate_domain_create: cannot make domain: -3 This seems to correspond to -ESRCH from xc_domain_create. > libxl: error: libxl.c:1392:libxl__destroy_domid: non-existant domain -1 > libxl: error: libxl.c:1356:domain_destrpy_callback: unable to destroy guest with domid 4294967295 > libxl: error: libxl_create.c:1152:domcreate_destruction_cb: unable to destroy domain 4294967295 following failed creation > > These errors don't seem to contain any useful information to me "xl -vvv create ..." might give you some more information, or you might see some useful messages in "xl dmesg". It might be useful to see the complete logs in case something interesting is hidden there. What does your guest configuration file contain? Ian. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Mon Feb 04 12:24:31 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 04 Feb 2013 12:24: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 1U2L4g-00051W-Ow; Mon, 04 Feb 2013 12:23:02 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U2L4e-00051R-RG for xen-users@lists.xen.org; Mon, 04 Feb 2013 12:23:00 +0000 Received: from [85.158.143.35:51610] by server-2.bemta-4.messagelabs.com id B1/26-01597-428AF015; Mon, 04 Feb 2013 12:23:00 +0000 X-Env-Sender: Ian.Campbell@citrix.com X-Msg-Ref: server-3.tower-21.messagelabs.com!1359980576!13629651!1 X-Originating-IP: [46.33.159.39] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNDYuMzMuMTU5LjM5ID0+IDIwNTkz\n X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 15865 invoked from network); 4 Feb 2013 12:22:56 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (46.33.159.39) by server-3.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 4 Feb 2013 12:22:56 -0000 X-IronPort-AV: E=Sophos;i="4.84,598,1355097600"; d="scan'208";a="1117528" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 04 Feb 2013 12:22:57 +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.297.1; Mon, 4 Feb 2013 12:22:56 +0000 Message-ID: <1359980575.7466.5.camel@zakaz.uk.xensource.com> From: Ian Campbell To: Matthias Date: Mon, 4 Feb 2013 12:22:55 +0000 In-Reply-To: References: <1359369167.6559.46.camel@zakaz.uk.xensource.com> Organization: Citrix Systems, Inc. X-Mailer: Evolution 3.4.4-1 MIME-Version: 1.0 Cc: "xen-users@lists.xen.org" Subject: Re: [Xen-users] xl nat and wrong IPs X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: 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, 2013-02-03 at 21:29 +0000, Matthias wrote: > Hi, > > I finally got the chance to do the testing.. > > You were right, the issue was due to routing_ip or better why the > calculated ($ip + 127) is used later here: > > do_or_die ip addr add "$router_ip" dev "${dev}" > do_or_die ip route add "$vif_ip" dev "${dev}" src "$router_ip" > > I don't really see any point in creating a dedicated router-IP and Glad you've got it sorted, I don't understand this stuff either though I'm afraid. (Perhaps they form two ends of a point-to-point /31 network? Total guess) > using it this way and i dont' see why this worked for me when using xm > earlier, but I might did some hacking before to fix this in my xm > installation, i can't really remember.. FWIW this script doesn't appear to have changed in hg for many years. Ian. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Mon Feb 04 12:24:31 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 04 Feb 2013 12:24: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 1U2L4g-00051W-Ow; Mon, 04 Feb 2013 12:23:02 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U2L4e-00051R-RG for xen-users@lists.xen.org; Mon, 04 Feb 2013 12:23:00 +0000 Received: from [85.158.143.35:51610] by server-2.bemta-4.messagelabs.com id B1/26-01597-428AF015; Mon, 04 Feb 2013 12:23:00 +0000 X-Env-Sender: Ian.Campbell@citrix.com X-Msg-Ref: server-3.tower-21.messagelabs.com!1359980576!13629651!1 X-Originating-IP: [46.33.159.39] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNDYuMzMuMTU5LjM5ID0+IDIwNTkz\n X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 15865 invoked from network); 4 Feb 2013 12:22:56 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (46.33.159.39) by server-3.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 4 Feb 2013 12:22:56 -0000 X-IronPort-AV: E=Sophos;i="4.84,598,1355097600"; d="scan'208";a="1117528" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 04 Feb 2013 12:22:57 +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.297.1; Mon, 4 Feb 2013 12:22:56 +0000 Message-ID: <1359980575.7466.5.camel@zakaz.uk.xensource.com> From: Ian Campbell To: Matthias Date: Mon, 4 Feb 2013 12:22:55 +0000 In-Reply-To: References: <1359369167.6559.46.camel@zakaz.uk.xensource.com> Organization: Citrix Systems, Inc. X-Mailer: Evolution 3.4.4-1 MIME-Version: 1.0 Cc: "xen-users@lists.xen.org" Subject: Re: [Xen-users] xl nat and wrong IPs X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: 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, 2013-02-03 at 21:29 +0000, Matthias wrote: > Hi, > > I finally got the chance to do the testing.. > > You were right, the issue was due to routing_ip or better why the > calculated ($ip + 127) is used later here: > > do_or_die ip addr add "$router_ip" dev "${dev}" > do_or_die ip route add "$vif_ip" dev "${dev}" src "$router_ip" > > I don't really see any point in creating a dedicated router-IP and Glad you've got it sorted, I don't understand this stuff either though I'm afraid. (Perhaps they form two ends of a point-to-point /31 network? Total guess) > using it this way and i dont' see why this worked for me when using xm > earlier, but I might did some hacking before to fix this in my xm > installation, i can't really remember.. FWIW this script doesn't appear to have changed in hg for many years. Ian. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Mon Feb 04 12:40:44 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 04 Feb 2013 12:40: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 1U2LKi-0005O8-Rw; Mon, 04 Feb 2013 12:39:36 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U2DJs-0002Yo-3t for xen-users@lists.xen.org; Mon, 04 Feb 2013 04:06:12 +0000 Received: from [85.158.143.35:20122] by server-1.bemta-4.messagelabs.com id F0/2E-08839-3B33F015; Mon, 04 Feb 2013 04:06:11 +0000 X-Env-Sender: linuxhack2012@gmail.com X-Msg-Ref: server-5.tower-21.messagelabs.com!1359950764!4794314!1 X-Originating-IP: [209.85.216.53] X-SpamReason: No, hits=0.9 required=7.0 tests=HTML_60_70,HTML_MESSAGE, MAILTO_TO_SPAM_ADDR,ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 9760 invoked from network); 4 Feb 2013 04:06:06 -0000 Received: from mail-qa0-f53.google.com (HELO mail-qa0-f53.google.com) (209.85.216.53) by server-5.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 4 Feb 2013 04:06:06 -0000 Received: by mail-qa0-f53.google.com with SMTP id z4so1095885qan.5 for ; Sun, 03 Feb 2013 20:06:04 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:content-type; bh=tWSGOZFzCuHhIX46g2+AFOFmXue0oeU+HnZOu1dc1sU=; b=ZitC79M5DugmYAiePzb3p9FKPlGquWcYDBg8a+vIkI0KeB/jCfVvkoP5fM7wXLj/m2 4RoDXCLAGMPWQ0zobrUlAagGs98+AGV2aYRpjtdiVdq2vezAVOGblgd9MxQOsy291i3n Jngs3FdNZztREUC5dGjOeamaPUQBjRWV/PMKfXsJbhSZYFy4ba74TE4rOaAlSuRsl9rz hPp+dPnC+CtSHeXp82JkeV5PswtCqu1MeiPAkUMnbNChLHiSqtmjoPqSA4CIn8vpS2hC tLe9AqRzI0UPl/xaSke798fmmZR/IkgiXQAChBt1nn22EOdDhUX5DTi1PZueYvRhtutR 4aug== MIME-Version: 1.0 X-Received: by 10.229.136.129 with SMTP id r1mr4164052qct.54.1359950764149; Sun, 03 Feb 2013 20:06:04 -0800 (PST) Received: by 10.49.52.66 with HTTP; Sun, 3 Feb 2013 20:06:04 -0800 (PST) In-Reply-To: References: Date: Mon, 4 Feb 2013 09:36:04 +0530 Message-ID: From: Linux Hack To: "xen-users@lists.xen.org" X-Mailman-Approved-At: Mon, 04 Feb 2013 12:39:34 +0000 Subject: Re: [Xen-users] I/O Scheduler X-BeenThere: xen-users@lists.xen.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="===============4618266122760871689==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============4618266122760871689== Content-Type: multipart/alternative; boundary=00248c768f5a358c4f04d4de36f9 --00248c768f5a358c4f04d4de36f9 Content-Type: text/plain; charset=ISO-8859-1 Hi, I think I may found but unsure would it work. Shall we add "extra='elevator=noop'" on domU config? On Sun, Feb 3, 2013 at 8:32 AM, Linux Hack wrote: > Hi, > > I noticed on one of the discussion that both Dom0 and DomU have the same > scheduler will cause I/O issues and changing the I/O scheduler to noop for > Xen VPS will give better performance. Is it correct? > > If its correct then how can we set the default I/O scheduler as noop for > Xen VM's without getting inside of them? I mean is there any option that we > can declare on DomU config itself? > > --00248c768f5a358c4f04d4de36f9 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Hi,

I think I may found but unsur= e would it work.

Shall we add=A0"extra=3D'elevator=3Dn= oop'" on domU config?


On Sun,= Feb 3, 2013 at 8:32 AM, Linux Hack <linuxhack2012@gmail.com>= wrote:
Hi,

I no= ticed on one of the discussion that both Dom0 and DomU have the same schedu= ler will cause I/O issues and changing the I/O scheduler to noop for Xen VP= S will give better performance. Is it correct?

If its correct then how can we set the default I/O sche= duler as noop for Xen VM's without getting inside of them? I mean is th= ere any option that we can declare on DomU config itself?


--00248c768f5a358c4f04d4de36f9-- --===============4618266122760871689== 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 --===============4618266122760871689==-- From xen-users-bounces@lists.xen.org Mon Feb 04 12:40:44 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 04 Feb 2013 12:40: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 1U2LKi-0005O8-Rw; Mon, 04 Feb 2013 12:39:36 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U2DJs-0002Yo-3t for xen-users@lists.xen.org; Mon, 04 Feb 2013 04:06:12 +0000 Received: from [85.158.143.35:20122] by server-1.bemta-4.messagelabs.com id F0/2E-08839-3B33F015; Mon, 04 Feb 2013 04:06:11 +0000 X-Env-Sender: linuxhack2012@gmail.com X-Msg-Ref: server-5.tower-21.messagelabs.com!1359950764!4794314!1 X-Originating-IP: [209.85.216.53] X-SpamReason: No, hits=0.9 required=7.0 tests=HTML_60_70,HTML_MESSAGE, MAILTO_TO_SPAM_ADDR,ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 9760 invoked from network); 4 Feb 2013 04:06:06 -0000 Received: from mail-qa0-f53.google.com (HELO mail-qa0-f53.google.com) (209.85.216.53) by server-5.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 4 Feb 2013 04:06:06 -0000 Received: by mail-qa0-f53.google.com with SMTP id z4so1095885qan.5 for ; Sun, 03 Feb 2013 20:06:04 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:content-type; bh=tWSGOZFzCuHhIX46g2+AFOFmXue0oeU+HnZOu1dc1sU=; b=ZitC79M5DugmYAiePzb3p9FKPlGquWcYDBg8a+vIkI0KeB/jCfVvkoP5fM7wXLj/m2 4RoDXCLAGMPWQ0zobrUlAagGs98+AGV2aYRpjtdiVdq2vezAVOGblgd9MxQOsy291i3n Jngs3FdNZztREUC5dGjOeamaPUQBjRWV/PMKfXsJbhSZYFy4ba74TE4rOaAlSuRsl9rz hPp+dPnC+CtSHeXp82JkeV5PswtCqu1MeiPAkUMnbNChLHiSqtmjoPqSA4CIn8vpS2hC tLe9AqRzI0UPl/xaSke798fmmZR/IkgiXQAChBt1nn22EOdDhUX5DTi1PZueYvRhtutR 4aug== MIME-Version: 1.0 X-Received: by 10.229.136.129 with SMTP id r1mr4164052qct.54.1359950764149; Sun, 03 Feb 2013 20:06:04 -0800 (PST) Received: by 10.49.52.66 with HTTP; Sun, 3 Feb 2013 20:06:04 -0800 (PST) In-Reply-To: References: Date: Mon, 4 Feb 2013 09:36:04 +0530 Message-ID: From: Linux Hack To: "xen-users@lists.xen.org" X-Mailman-Approved-At: Mon, 04 Feb 2013 12:39:34 +0000 Subject: Re: [Xen-users] I/O Scheduler X-BeenThere: xen-users@lists.xen.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="===============4618266122760871689==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============4618266122760871689== Content-Type: multipart/alternative; boundary=00248c768f5a358c4f04d4de36f9 --00248c768f5a358c4f04d4de36f9 Content-Type: text/plain; charset=ISO-8859-1 Hi, I think I may found but unsure would it work. Shall we add "extra='elevator=noop'" on domU config? On Sun, Feb 3, 2013 at 8:32 AM, Linux Hack wrote: > Hi, > > I noticed on one of the discussion that both Dom0 and DomU have the same > scheduler will cause I/O issues and changing the I/O scheduler to noop for > Xen VPS will give better performance. Is it correct? > > If its correct then how can we set the default I/O scheduler as noop for > Xen VM's without getting inside of them? I mean is there any option that we > can declare on DomU config itself? > > --00248c768f5a358c4f04d4de36f9 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Hi,

I think I may found but unsur= e would it work.

Shall we add=A0"extra=3D'elevator=3Dn= oop'" on domU config?


On Sun,= Feb 3, 2013 at 8:32 AM, Linux Hack <linuxhack2012@gmail.com>= wrote:
Hi,

I no= ticed on one of the discussion that both Dom0 and DomU have the same schedu= ler will cause I/O issues and changing the I/O scheduler to noop for Xen VP= S will give better performance. Is it correct?

If its correct then how can we set the default I/O sche= duler as noop for Xen VM's without getting inside of them? I mean is th= ere any option that we can declare on DomU config itself?


--00248c768f5a358c4f04d4de36f9-- --===============4618266122760871689== 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 --===============4618266122760871689==-- From xen-users-bounces@lists.xen.org Mon Feb 04 12:40:44 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 04 Feb 2013 12:40: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 1U2LKj-0005OH-GA; Mon, 04 Feb 2013 12:39:37 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U2GiE-0004vj-09 for xen-users@lists.xen.org; Mon, 04 Feb 2013 07:43:34 +0000 Received: from [85.158.139.83:31163] by server-4.bemta-5.messagelabs.com id 93/7F-29496-5A66F015; Mon, 04 Feb 2013 07:43:33 +0000 X-Env-Sender: linuxhack2012@gmail.com X-Msg-Ref: server-11.tower-182.messagelabs.com!1359963810!23483244!1 X-Originating-IP: [209.85.216.41] 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.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 7109 invoked from network); 4 Feb 2013 07:43:31 -0000 Received: from mail-qa0-f41.google.com (HELO mail-qa0-f41.google.com) (209.85.216.41) by server-11.tower-182.messagelabs.com with RC4-SHA encrypted SMTP; 4 Feb 2013 07:43:31 -0000 Received: by mail-qa0-f41.google.com with SMTP id hy16so1131069qab.14 for ; Sun, 03 Feb 2013 23:43:30 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=KUTjKcg/A1ZDptw6KpuCJNkeEDtzYeJAV91DSrJl5ZU=; b=K3eKDJue0jYd8h2D1jEIk04MLDswGwM2GQosqEpaeChFqiHIjzKQ+BvynDvJyDGUTR o4YmAIV0KM1alzDmX36HKxMx11WpYoUpu6ui/A+Lm1FyzzCRM97/cay2VAbzyK0OF+4f kliOIaPzSYxs0lVfbMww1TaArI4B25oPKLLDQV5MJSjmGNr7ygOh8+h3r+udMJdtqxW/ xEasuaCVF9QaSCIZXanmB0N2JJACGnyNuTvkxVticG09DpgYEfKYmB3dE0+JBfh9Uu91 kZv+4NNoSY27wwpUez4SiEk7PfevImEZRSy0YDTQNqh5biwlK2HDi0FXTXNQr4LCe+8N 9LEw== MIME-Version: 1.0 X-Received: by 10.49.127.101 with SMTP id nf5mr21176535qeb.20.1359963810375; Sun, 03 Feb 2013 23:43:30 -0800 (PST) Received: by 10.49.52.66 with HTTP; Sun, 3 Feb 2013 23:43:30 -0800 (PST) In-Reply-To: <510F6165.9010908@ts.fujitsu.com> References: <510F6165.9010908@ts.fujitsu.com> Date: Mon, 4 Feb 2013 13:13:30 +0530 Message-ID: From: Linux Hack To: Juergen Gross X-Mailman-Approved-At: Mon, 04 Feb 2013 12:39:34 +0000 Cc: "xen-users@lists.xen.org" Subject: Re: [Xen-users] xl cpupool X-BeenThere: xen-users@lists.xen.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="===============1304385373430986064==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============1304385373430986064== Content-Type: multipart/alternative; boundary=047d7b6dc0bcd3284f04d4e13f24 --047d7b6dc0bcd3284f04d4e13f24 Content-Type: text/plain; charset=ISO-8859-1 Hi That's something interesting. Would it possible to make this work on xm or xl tool stack on xen version 3.4.4/4.1.4? On Monday, February 4, 2013, Juergen Gross wrote: > Hi, > > Am 02.02.2013 00:53, schrieb Linux Hack: >> >> Hi, >> >> Would it possible to create cpupools with xl after the server boot and >> then assign one cpu-pool to dom0 and another one for dom-u's? > > Yes. > > You have to (assuming Xen 4.2): > > 1. remove cpus from Pool-0 with "xl cpupool-cpu-remove" > 2. reduce number of dom0 cpus to fit to reduced Pool-0 with "xl vcpu-set" > 3. create the domU cpupool with "xl cpupool-create" > 4. assign the free cpus to the new cpupool ("xl cpupool-cpu-add") > 5. create the domUs with "pool=" to start them in the new cpupool > (either in the config files of the domUs or as parameter of "xl create" > >> Also is there any change to make this work on server startup? > > You would have to add an init script in dom0. > > > Juergen > > -- > Juergen Gross Principal Developer Operating Systems > PBG PDG ES&S SWE OS6 Telephone: +49 (0) 89 3222 2967 > Fujitsu Technology Solutions e-mail: juergen.gross@ts.fujitsu.com > Domagkstr. 28 Internet: ts.fujitsu.com > D-80807 Muenchen Company details: ts.fujitsu.com/imprint.html > --047d7b6dc0bcd3284f04d4e13f24 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Hi

That's something interesting. Would it possible to make this = work on xm or xl tool stack on xen version 3.4.4/4.1.4?

On Monday, F= ebruary 4, 2013, Juergen Gross <juergen.gross@ts.fujitsu.com> wrote:
> Hi,
>
> Am 02.02.2013 00:53, schrieb Linux Hack:
>&g= t;
>> Hi,
>>
>> Would it possible to create cpup= ools with xl after the server boot and
>> then assign one cpu-pool= to dom0 and another one for dom-u's?
>
> Yes.
>
> You have to (assuming Xen 4.2):
>> 1. remove cpus from Pool-0 with "xl cpupool-cpu-remove"> 2. reduce number of dom0 cpus to fit to reduced Pool-0 with "xl = vcpu-set"
> 3. create the domU cpupool with "xl cpupool-create"
> = 4. assign the free cpus to the new cpupool ("xl cpupool-cpu-add")=
> 5. create the domUs with "pool=3D<cpupool>" to sta= rt them in the new cpupool
> =A0 =A0(either in the config files of the domUs or as parameter of &qu= ot;xl create"
>
>> Also is there any change to make thi= s work on server startup?
>
> You would have to add an init scr= ipt in dom0.
>
>
> Juergen
>
> --
> Juergen Gross =A0 = =A0 =A0 =A0 =A0 =A0 =A0 =A0 Principal Developer Operating Systems
> P= BG PDG ES&S SWE OS6 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 Telephone: +49 = (0) 89 3222 2967
> Fujitsu Technology Solutions =A0 =A0 =A0 =A0 =A0 = =A0 =A0e-mail: juergen.gros= s@ts.fujitsu.com
> Domagkstr. 28 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 Inte= rnet: ts.fujitsu.com
> D-80807 = Muenchen =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 Company details: ts.fujitsu.com/imprint.html
> --047d7b6dc0bcd3284f04d4e13f24-- --===============1304385373430986064== 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 --===============1304385373430986064==-- From xen-users-bounces@lists.xen.org Mon Feb 04 12:40:44 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 04 Feb 2013 12:40: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 1U2LKj-0005OH-GA; Mon, 04 Feb 2013 12:39:37 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U2GiE-0004vj-09 for xen-users@lists.xen.org; Mon, 04 Feb 2013 07:43:34 +0000 Received: from [85.158.139.83:31163] by server-4.bemta-5.messagelabs.com id 93/7F-29496-5A66F015; Mon, 04 Feb 2013 07:43:33 +0000 X-Env-Sender: linuxhack2012@gmail.com X-Msg-Ref: server-11.tower-182.messagelabs.com!1359963810!23483244!1 X-Originating-IP: [209.85.216.41] 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.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 7109 invoked from network); 4 Feb 2013 07:43:31 -0000 Received: from mail-qa0-f41.google.com (HELO mail-qa0-f41.google.com) (209.85.216.41) by server-11.tower-182.messagelabs.com with RC4-SHA encrypted SMTP; 4 Feb 2013 07:43:31 -0000 Received: by mail-qa0-f41.google.com with SMTP id hy16so1131069qab.14 for ; Sun, 03 Feb 2013 23:43:30 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=KUTjKcg/A1ZDptw6KpuCJNkeEDtzYeJAV91DSrJl5ZU=; b=K3eKDJue0jYd8h2D1jEIk04MLDswGwM2GQosqEpaeChFqiHIjzKQ+BvynDvJyDGUTR o4YmAIV0KM1alzDmX36HKxMx11WpYoUpu6ui/A+Lm1FyzzCRM97/cay2VAbzyK0OF+4f kliOIaPzSYxs0lVfbMww1TaArI4B25oPKLLDQV5MJSjmGNr7ygOh8+h3r+udMJdtqxW/ xEasuaCVF9QaSCIZXanmB0N2JJACGnyNuTvkxVticG09DpgYEfKYmB3dE0+JBfh9Uu91 kZv+4NNoSY27wwpUez4SiEk7PfevImEZRSy0YDTQNqh5biwlK2HDi0FXTXNQr4LCe+8N 9LEw== MIME-Version: 1.0 X-Received: by 10.49.127.101 with SMTP id nf5mr21176535qeb.20.1359963810375; Sun, 03 Feb 2013 23:43:30 -0800 (PST) Received: by 10.49.52.66 with HTTP; Sun, 3 Feb 2013 23:43:30 -0800 (PST) In-Reply-To: <510F6165.9010908@ts.fujitsu.com> References: <510F6165.9010908@ts.fujitsu.com> Date: Mon, 4 Feb 2013 13:13:30 +0530 Message-ID: From: Linux Hack To: Juergen Gross X-Mailman-Approved-At: Mon, 04 Feb 2013 12:39:34 +0000 Cc: "xen-users@lists.xen.org" Subject: Re: [Xen-users] xl cpupool X-BeenThere: xen-users@lists.xen.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="===============1304385373430986064==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============1304385373430986064== Content-Type: multipart/alternative; boundary=047d7b6dc0bcd3284f04d4e13f24 --047d7b6dc0bcd3284f04d4e13f24 Content-Type: text/plain; charset=ISO-8859-1 Hi That's something interesting. Would it possible to make this work on xm or xl tool stack on xen version 3.4.4/4.1.4? On Monday, February 4, 2013, Juergen Gross wrote: > Hi, > > Am 02.02.2013 00:53, schrieb Linux Hack: >> >> Hi, >> >> Would it possible to create cpupools with xl after the server boot and >> then assign one cpu-pool to dom0 and another one for dom-u's? > > Yes. > > You have to (assuming Xen 4.2): > > 1. remove cpus from Pool-0 with "xl cpupool-cpu-remove" > 2. reduce number of dom0 cpus to fit to reduced Pool-0 with "xl vcpu-set" > 3. create the domU cpupool with "xl cpupool-create" > 4. assign the free cpus to the new cpupool ("xl cpupool-cpu-add") > 5. create the domUs with "pool=" to start them in the new cpupool > (either in the config files of the domUs or as parameter of "xl create" > >> Also is there any change to make this work on server startup? > > You would have to add an init script in dom0. > > > Juergen > > -- > Juergen Gross Principal Developer Operating Systems > PBG PDG ES&S SWE OS6 Telephone: +49 (0) 89 3222 2967 > Fujitsu Technology Solutions e-mail: juergen.gross@ts.fujitsu.com > Domagkstr. 28 Internet: ts.fujitsu.com > D-80807 Muenchen Company details: ts.fujitsu.com/imprint.html > --047d7b6dc0bcd3284f04d4e13f24 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Hi

That's something interesting. Would it possible to make this = work on xm or xl tool stack on xen version 3.4.4/4.1.4?

On Monday, F= ebruary 4, 2013, Juergen Gross <juergen.gross@ts.fujitsu.com> wrote:
> Hi,
>
> Am 02.02.2013 00:53, schrieb Linux Hack:
>&g= t;
>> Hi,
>>
>> Would it possible to create cpup= ools with xl after the server boot and
>> then assign one cpu-pool= to dom0 and another one for dom-u's?
>
> Yes.
>
> You have to (assuming Xen 4.2):
>> 1. remove cpus from Pool-0 with "xl cpupool-cpu-remove"> 2. reduce number of dom0 cpus to fit to reduced Pool-0 with "xl = vcpu-set"
> 3. create the domU cpupool with "xl cpupool-create"
> = 4. assign the free cpus to the new cpupool ("xl cpupool-cpu-add")=
> 5. create the domUs with "pool=3D<cpupool>" to sta= rt them in the new cpupool
> =A0 =A0(either in the config files of the domUs or as parameter of &qu= ot;xl create"
>
>> Also is there any change to make thi= s work on server startup?
>
> You would have to add an init scr= ipt in dom0.
>
>
> Juergen
>
> --
> Juergen Gross =A0 = =A0 =A0 =A0 =A0 =A0 =A0 =A0 Principal Developer Operating Systems
> P= BG PDG ES&S SWE OS6 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 Telephone: +49 = (0) 89 3222 2967
> Fujitsu Technology Solutions =A0 =A0 =A0 =A0 =A0 = =A0 =A0e-mail: juergen.gros= s@ts.fujitsu.com
> Domagkstr. 28 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 Inte= rnet: ts.fujitsu.com
> D-80807 = Muenchen =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 Company details: ts.fujitsu.com/imprint.html
> --047d7b6dc0bcd3284f04d4e13f24-- --===============1304385373430986064== 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 --===============1304385373430986064==-- From xen-users-bounces@lists.xen.org Mon Feb 04 12:40:45 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 04 Feb 2013 12:40: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 1U2LKi-0005Nz-8S; Mon, 04 Feb 2013 12:39:36 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U2D0m-0002Pq-QK for xen-users@lists.xen.org; Mon, 04 Feb 2013 03:46:29 +0000 Received: from [193.109.254.147:26705] by server-2.bemta-14.messagelabs.com id 14/B7-16277-31F2F015; Mon, 04 Feb 2013 03:46:27 +0000 X-Env-Sender: linuxhack2012@gmail.com X-Msg-Ref: server-13.tower-27.messagelabs.com!1359949584!9966121!1 X-Originating-IP: [209.85.128.42] 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.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 20899 invoked from network); 4 Feb 2013 03:46:26 -0000 Received: from mail-qe0-f42.google.com (HELO mail-qe0-f42.google.com) (209.85.128.42) by server-13.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 4 Feb 2013 03:46:26 -0000 Received: by mail-qe0-f42.google.com with SMTP id 2so2298363qeb.29 for ; Sun, 03 Feb 2013 19:46:24 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=EelIrEwkcbGbXfhDtcHrszn6gwLtux9yi0m2k2a0dkU=; b=P1VLJGNHMEO3m3LAfnp6hYFzTkJz1eX7BHYn3ZqIi+/k8EGScjQGOxPV0v/54fQZf2 r4ztxbv18KilrseRLSTI2xHFoih9tAlhFYd1H+9RhWCAoZQtciNk7iLe7/bu47yxDcei /SVbzhF9UTib011O6wboOum07r2vRl0FO9aSt2zf5lY4mJh/rhXD2yL+Njqw5bmFoE/H GQCnegaxk9VgzL4Ys6TVHlUGuFm1/Wa62gjJfSoXbXf47T3Vcv9Ac+EIWluR7cSENGBb odLln92X1nqgysrv/nX8++yRWdpkzZYPY9jP6TO/lA77rQ1nWG+jCnGHvk2BwhsCk+ge 5gyQ== MIME-Version: 1.0 X-Received: by 10.229.137.1 with SMTP id u1mr4238060qct.86.1359949584278; Sun, 03 Feb 2013 19:46:24 -0800 (PST) Received: by 10.49.52.66 with HTTP; Sun, 3 Feb 2013 19:46:24 -0800 (PST) In-Reply-To: <510F21DC.5040609@gmail.com> References: <510E93C1.6090905@gmail.com> <510F21DC.5040609@gmail.com> Date: Mon, 4 Feb 2013 09:16:24 +0530 Message-ID: From: Linux Hack To: Peter Viskup X-Mailman-Approved-At: Mon, 04 Feb 2013 12:39:34 +0000 Cc: "xen-users@lists.xen.org" Subject: Re: [Xen-users] high cpu usage on steal time X-BeenThere: xen-users@lists.xen.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="===============5742772199817222593==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============5742772199817222593== Content-Type: multipart/alternative; boundary=00235452ea58e226e704d4ddefde --00235452ea58e226e704d4ddefde Content-Type: text/plain; charset=ISO-8859-1 Hi, I dont have higher steal at the moment and things are going well. I always checking using top on Dom0. Is there any way to check CPU steal time for each Dom-U from Dom0 itself? On Mon, Feb 4, 2013 at 8:20 AM, Peter Viskup wrote: > I don't want to step into discussion about my setup as I already > discussed this here just some weeks before. > Do you still experience the issue with higher steal time or we can > disregard this your request for support? > Do you see the steal time on dom0 or some domU? > > > On 02/04/2013 01:44 AM, Linux Hack wrote: > > Hi Peter, > > Seems things are going fine with minimum steal time cpu usage (vary > between 5-20) with Xen 4.1.4 and latest centos 5.9 xen kernel. > > What is the kernel you are running on your server? > > > > On Sun, Feb 3, 2013 at 10:13 PM, Peter Viskup wrote: > >> On 02/02/2013 12:54 AM, Linux Hack wrote: >> >>> Hi, >>> >>> One of the server is under high cpu usage and when checked steal time is >>> causing the high cpu usage. However I have pinned the vcpu's for dom0 >>> dedicatedly but still no luck. >>> >>> Any thought's that would be great? >>> >>> >> I had the same issue. Looks like things changed with newer PvOPs >> kernels (2.6.32+) and now the old fashioned setup of dedication of one CPU >> for dom0 (xm vcpu-pin 0 all 0) is causing performance issues and very high >> steal time on dom0. In my case I wasn't able to start any domU as the dom0 >> had not enough CPU time and it just ended with error (due to some timeout). >> Unfortunately nor Ian Campbell was able to tell me what is the reason of >> this behavior and what was changed. >> >> Best regards, >> -- >> Peter Viskup >> > > > --00235452ea58e226e704d4ddefde Content-Type: text/html; charset=ISO-8859-1
Hi,

I dont have higher steal at the moment and things are going well. I always checking using top on Dom0.

Is there any way to check CPU steal time for each Dom-U from Dom0 itself?



On Mon, Feb 4, 2013 at 8:20 AM, Peter Viskup <skupko.sk@gmail.com> wrote:
I don't want to step into discussion about my setup as I already discussed this here just some weeks before.
Do you still experience the issue with higher steal time or we can disregard this your request for support?
Do you see the steal time on dom0 or some domU?


On 02/04/2013 01:44 AM, Linux Hack wrote:
Hi Peter,

Seems things are going fine with minimum steal time cpu usage (vary between 5-20) with Xen 4.1.4 and latest centos 5.9 xen kernel.

What is the kernel you are running on your server?



On Sun, Feb 3, 2013 at 10:13 PM, Peter Viskup <skupko.sk@gmail.com> wrote:
On 02/02/2013 12:54 AM, Linux Hack wrote:
Hi,

One of the server is under high cpu usage and when checked steal time is causing the high cpu usage. However I have pinned the vcpu's for dom0 dedicatedly but still no luck.

Any thought's that would be great?


I had the same issue. Looks like things changed with newer PvOPs kernels (2.6.32+) and now the old fashioned setup of dedication of one CPU for dom0 (xm vcpu-pin 0 all 0) is causing performance issues and very high steal time on dom0. In my case I wasn't able to start any domU as the dom0 had not enough CPU time and it just ended with error (due to some timeout). Unfortunately nor Ian Campbell was able to tell me what is the reason of this behavior and what was changed.

Best regards,
--
Peter Viskup



--00235452ea58e226e704d4ddefde-- --===============5742772199817222593== 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 --===============5742772199817222593==-- From xen-users-bounces@lists.xen.org Mon Feb 04 12:40:45 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 04 Feb 2013 12:40: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 1U2LKi-0005Nz-8S; Mon, 04 Feb 2013 12:39:36 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U2D0m-0002Pq-QK for xen-users@lists.xen.org; Mon, 04 Feb 2013 03:46:29 +0000 Received: from [193.109.254.147:26705] by server-2.bemta-14.messagelabs.com id 14/B7-16277-31F2F015; Mon, 04 Feb 2013 03:46:27 +0000 X-Env-Sender: linuxhack2012@gmail.com X-Msg-Ref: server-13.tower-27.messagelabs.com!1359949584!9966121!1 X-Originating-IP: [209.85.128.42] 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.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 20899 invoked from network); 4 Feb 2013 03:46:26 -0000 Received: from mail-qe0-f42.google.com (HELO mail-qe0-f42.google.com) (209.85.128.42) by server-13.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 4 Feb 2013 03:46:26 -0000 Received: by mail-qe0-f42.google.com with SMTP id 2so2298363qeb.29 for ; Sun, 03 Feb 2013 19:46:24 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=EelIrEwkcbGbXfhDtcHrszn6gwLtux9yi0m2k2a0dkU=; b=P1VLJGNHMEO3m3LAfnp6hYFzTkJz1eX7BHYn3ZqIi+/k8EGScjQGOxPV0v/54fQZf2 r4ztxbv18KilrseRLSTI2xHFoih9tAlhFYd1H+9RhWCAoZQtciNk7iLe7/bu47yxDcei /SVbzhF9UTib011O6wboOum07r2vRl0FO9aSt2zf5lY4mJh/rhXD2yL+Njqw5bmFoE/H GQCnegaxk9VgzL4Ys6TVHlUGuFm1/Wa62gjJfSoXbXf47T3Vcv9Ac+EIWluR7cSENGBb odLln92X1nqgysrv/nX8++yRWdpkzZYPY9jP6TO/lA77rQ1nWG+jCnGHvk2BwhsCk+ge 5gyQ== MIME-Version: 1.0 X-Received: by 10.229.137.1 with SMTP id u1mr4238060qct.86.1359949584278; Sun, 03 Feb 2013 19:46:24 -0800 (PST) Received: by 10.49.52.66 with HTTP; Sun, 3 Feb 2013 19:46:24 -0800 (PST) In-Reply-To: <510F21DC.5040609@gmail.com> References: <510E93C1.6090905@gmail.com> <510F21DC.5040609@gmail.com> Date: Mon, 4 Feb 2013 09:16:24 +0530 Message-ID: From: Linux Hack To: Peter Viskup X-Mailman-Approved-At: Mon, 04 Feb 2013 12:39:34 +0000 Cc: "xen-users@lists.xen.org" Subject: Re: [Xen-users] high cpu usage on steal time X-BeenThere: xen-users@lists.xen.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="===============5742772199817222593==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============5742772199817222593== Content-Type: multipart/alternative; boundary=00235452ea58e226e704d4ddefde --00235452ea58e226e704d4ddefde Content-Type: text/plain; charset=ISO-8859-1 Hi, I dont have higher steal at the moment and things are going well. I always checking using top on Dom0. Is there any way to check CPU steal time for each Dom-U from Dom0 itself? On Mon, Feb 4, 2013 at 8:20 AM, Peter Viskup wrote: > I don't want to step into discussion about my setup as I already > discussed this here just some weeks before. > Do you still experience the issue with higher steal time or we can > disregard this your request for support? > Do you see the steal time on dom0 or some domU? > > > On 02/04/2013 01:44 AM, Linux Hack wrote: > > Hi Peter, > > Seems things are going fine with minimum steal time cpu usage (vary > between 5-20) with Xen 4.1.4 and latest centos 5.9 xen kernel. > > What is the kernel you are running on your server? > > > > On Sun, Feb 3, 2013 at 10:13 PM, Peter Viskup wrote: > >> On 02/02/2013 12:54 AM, Linux Hack wrote: >> >>> Hi, >>> >>> One of the server is under high cpu usage and when checked steal time is >>> causing the high cpu usage. However I have pinned the vcpu's for dom0 >>> dedicatedly but still no luck. >>> >>> Any thought's that would be great? >>> >>> >> I had the same issue. Looks like things changed with newer PvOPs >> kernels (2.6.32+) and now the old fashioned setup of dedication of one CPU >> for dom0 (xm vcpu-pin 0 all 0) is causing performance issues and very high >> steal time on dom0. In my case I wasn't able to start any domU as the dom0 >> had not enough CPU time and it just ended with error (due to some timeout). >> Unfortunately nor Ian Campbell was able to tell me what is the reason of >> this behavior and what was changed. >> >> Best regards, >> -- >> Peter Viskup >> > > > --00235452ea58e226e704d4ddefde Content-Type: text/html; charset=ISO-8859-1
Hi,

I dont have higher steal at the moment and things are going well. I always checking using top on Dom0.

Is there any way to check CPU steal time for each Dom-U from Dom0 itself?



On Mon, Feb 4, 2013 at 8:20 AM, Peter Viskup <skupko.sk@gmail.com> wrote:
I don't want to step into discussion about my setup as I already discussed this here just some weeks before.
Do you still experience the issue with higher steal time or we can disregard this your request for support?
Do you see the steal time on dom0 or some domU?


On 02/04/2013 01:44 AM, Linux Hack wrote:
Hi Peter,

Seems things are going fine with minimum steal time cpu usage (vary between 5-20) with Xen 4.1.4 and latest centos 5.9 xen kernel.

What is the kernel you are running on your server?



On Sun, Feb 3, 2013 at 10:13 PM, Peter Viskup <skupko.sk@gmail.com> wrote:
On 02/02/2013 12:54 AM, Linux Hack wrote:
Hi,

One of the server is under high cpu usage and when checked steal time is causing the high cpu usage. However I have pinned the vcpu's for dom0 dedicatedly but still no luck.

Any thought's that would be great?


I had the same issue. Looks like things changed with newer PvOPs kernels (2.6.32+) and now the old fashioned setup of dedication of one CPU for dom0 (xm vcpu-pin 0 all 0) is causing performance issues and very high steal time on dom0. In my case I wasn't able to start any domU as the dom0 had not enough CPU time and it just ended with error (due to some timeout). Unfortunately nor Ian Campbell was able to tell me what is the reason of this behavior and what was changed.

Best regards,
--
Peter Viskup



--00235452ea58e226e704d4ddefde-- --===============5742772199817222593== 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 --===============5742772199817222593==-- From xen-users-bounces@lists.xen.org Mon Feb 04 12:40:45 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 04 Feb 2013 12:40: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 1U2LKh-0005Nq-Jl; Mon, 04 Feb 2013 12:39:35 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U2AAK-0004uo-Q4 for xen-users@lists.xen.org; Mon, 04 Feb 2013 00:44:09 +0000 Received: from [85.158.139.83:28691] by server-7.bemta-5.messagelabs.com id 52/91-11121-7540F015; Mon, 04 Feb 2013 00:44:07 +0000 X-Env-Sender: linuxhack2012@gmail.com X-Msg-Ref: server-9.tower-182.messagelabs.com!1359938646!27569424!1 X-Originating-IP: [209.85.216.54] 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.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 16968 invoked from network); 4 Feb 2013 00:44:07 -0000 Received: from mail-qa0-f54.google.com (HELO mail-qa0-f54.google.com) (209.85.216.54) by server-9.tower-182.messagelabs.com with RC4-SHA encrypted SMTP; 4 Feb 2013 00:44:07 -0000 Received: by mail-qa0-f54.google.com with SMTP id hg5so1050054qab.6 for ; Sun, 03 Feb 2013 16:44:06 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=zv1dFANuUDFSFEkVrKWCR26QskdEhjmXoYoI+4AZ3IE=; b=o/WpPpGGHwQkwwbROkd66JLEsVs+a+QCMT7C7xfaI1u7xBoEkFQ3S/XTazrcZB4+fT mYk+x+NN8jO4kUPEjjVP4JbNqByPbLNKZrDSZVox+As5OQS6weu+s3Dy4L2wSe0+6AiG 1TFyHkCEARaaXqfId6RAWgJ4VvAiPuNDKE4PundXx2D5A5n7I9g9AVWiX4z2wrrrPIM6 LA3oIJW354nDyi78k8fg6hPpEUY2AXoz05ycD/nCh2EtQ33D/0ah+rlfeHAFK2Ymhg7o bmnQLlNWJySu1edIYzRnx7CX4JlMQnBpNCWOIMKAIi8z9vfR7q+/Eh3DAKxawCuPujBC TtVw== MIME-Version: 1.0 X-Received: by 10.224.182.70 with SMTP id cb6mr17312721qab.80.1359938645828; Sun, 03 Feb 2013 16:44:05 -0800 (PST) Received: by 10.49.52.66 with HTTP; Sun, 3 Feb 2013 16:44:05 -0800 (PST) In-Reply-To: <510E93C1.6090905@gmail.com> References: <510E93C1.6090905@gmail.com> Date: Mon, 4 Feb 2013 06:14:05 +0530 Message-ID: From: Linux Hack To: Peter Viskup X-Mailman-Approved-At: Mon, 04 Feb 2013 12:39:34 +0000 Cc: "xen-users@lists.xen.org" Subject: Re: [Xen-users] high cpu usage on steal time X-BeenThere: xen-users@lists.xen.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="===============5586204410203836130==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============5586204410203836130== Content-Type: multipart/alternative; boundary=20cf303b4183e6a63e04d4db63e3 --20cf303b4183e6a63e04d4db63e3 Content-Type: text/plain; charset=ISO-8859-1 Hi Peter, Seems things are going fine with minimum steal time cpu usage (vary between 5-20) with Xen 4.1.4 and latest centos 5.9 xen kernel. What is the kernel you are running on your server? On Sun, Feb 3, 2013 at 10:13 PM, Peter Viskup wrote: > On 02/02/2013 12:54 AM, Linux Hack wrote: > >> Hi, >> >> One of the server is under high cpu usage and when checked steal time is >> causing the high cpu usage. However I have pinned the vcpu's for dom0 >> dedicatedly but still no luck. >> >> Any thought's that would be great? >> >> > I had the same issue. Looks like things changed with newer PvOPs kernels > (2.6.32+) and now the old fashioned setup of dedication of one CPU for dom0 > (xm vcpu-pin 0 all 0) is causing performance issues and very high steal > time on dom0. In my case I wasn't able to start any domU as the dom0 had > not enough CPU time and it just ended with error (due to some timeout). > Unfortunately nor Ian Campbell was able to tell me what is the reason of > this behavior and what was changed. > > Best regards, > -- > Peter Viskup > --20cf303b4183e6a63e04d4db63e3 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Hi Peter,

Seems things are going fine w= ith minimum steal time cpu usage (vary between 5-20) with Xen 4.1.4 and lat= est centos 5.9 xen kernel.

What is the kernel you = are running on your server?



On Sun, Feb 3, 2013 at 10:13 PM, Peter Viskup <= ;skupko.sk@gmail.c= om> wrote:
On 0= 2/02/2013 12:54 AM, Linux Hack wrote:
Hi,

One of the server is under high cpu usage and when checked steal time is ca= using the high cpu usage. However I have pinned the vcpu's for dom0 ded= icatedly but still no luck.

Any thought's that would be great?


I had the same issue. Looks like things changed with newer PvOPs kernels (2= .6.32+) and now the old fashioned setup of dedication of one CPU for dom0 (= xm vcpu-pin 0 all 0) is causing performance issues and very high steal time= on dom0. In my case I wasn't able to start any domU as the dom0 had no= t enough CPU time and it just ended with error (due to some timeout). Unfor= tunately nor Ian Campbell was able to tell me what is the reason of this be= havior and what was changed.

Best regards,
--
Peter Viskup

--20cf303b4183e6a63e04d4db63e3-- --===============5586204410203836130== 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 --===============5586204410203836130==-- From xen-users-bounces@lists.xen.org Mon Feb 04 12:40:45 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 04 Feb 2013 12:40: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 1U2LKh-0005Nq-Jl; Mon, 04 Feb 2013 12:39:35 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U2AAK-0004uo-Q4 for xen-users@lists.xen.org; Mon, 04 Feb 2013 00:44:09 +0000 Received: from [85.158.139.83:28691] by server-7.bemta-5.messagelabs.com id 52/91-11121-7540F015; Mon, 04 Feb 2013 00:44:07 +0000 X-Env-Sender: linuxhack2012@gmail.com X-Msg-Ref: server-9.tower-182.messagelabs.com!1359938646!27569424!1 X-Originating-IP: [209.85.216.54] 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.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 16968 invoked from network); 4 Feb 2013 00:44:07 -0000 Received: from mail-qa0-f54.google.com (HELO mail-qa0-f54.google.com) (209.85.216.54) by server-9.tower-182.messagelabs.com with RC4-SHA encrypted SMTP; 4 Feb 2013 00:44:07 -0000 Received: by mail-qa0-f54.google.com with SMTP id hg5so1050054qab.6 for ; Sun, 03 Feb 2013 16:44:06 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=zv1dFANuUDFSFEkVrKWCR26QskdEhjmXoYoI+4AZ3IE=; b=o/WpPpGGHwQkwwbROkd66JLEsVs+a+QCMT7C7xfaI1u7xBoEkFQ3S/XTazrcZB4+fT mYk+x+NN8jO4kUPEjjVP4JbNqByPbLNKZrDSZVox+As5OQS6weu+s3Dy4L2wSe0+6AiG 1TFyHkCEARaaXqfId6RAWgJ4VvAiPuNDKE4PundXx2D5A5n7I9g9AVWiX4z2wrrrPIM6 LA3oIJW354nDyi78k8fg6hPpEUY2AXoz05ycD/nCh2EtQ33D/0ah+rlfeHAFK2Ymhg7o bmnQLlNWJySu1edIYzRnx7CX4JlMQnBpNCWOIMKAIi8z9vfR7q+/Eh3DAKxawCuPujBC TtVw== MIME-Version: 1.0 X-Received: by 10.224.182.70 with SMTP id cb6mr17312721qab.80.1359938645828; Sun, 03 Feb 2013 16:44:05 -0800 (PST) Received: by 10.49.52.66 with HTTP; Sun, 3 Feb 2013 16:44:05 -0800 (PST) In-Reply-To: <510E93C1.6090905@gmail.com> References: <510E93C1.6090905@gmail.com> Date: Mon, 4 Feb 2013 06:14:05 +0530 Message-ID: From: Linux Hack To: Peter Viskup X-Mailman-Approved-At: Mon, 04 Feb 2013 12:39:34 +0000 Cc: "xen-users@lists.xen.org" Subject: Re: [Xen-users] high cpu usage on steal time X-BeenThere: xen-users@lists.xen.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="===============5586204410203836130==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============5586204410203836130== Content-Type: multipart/alternative; boundary=20cf303b4183e6a63e04d4db63e3 --20cf303b4183e6a63e04d4db63e3 Content-Type: text/plain; charset=ISO-8859-1 Hi Peter, Seems things are going fine with minimum steal time cpu usage (vary between 5-20) with Xen 4.1.4 and latest centos 5.9 xen kernel. What is the kernel you are running on your server? On Sun, Feb 3, 2013 at 10:13 PM, Peter Viskup wrote: > On 02/02/2013 12:54 AM, Linux Hack wrote: > >> Hi, >> >> One of the server is under high cpu usage and when checked steal time is >> causing the high cpu usage. However I have pinned the vcpu's for dom0 >> dedicatedly but still no luck. >> >> Any thought's that would be great? >> >> > I had the same issue. Looks like things changed with newer PvOPs kernels > (2.6.32+) and now the old fashioned setup of dedication of one CPU for dom0 > (xm vcpu-pin 0 all 0) is causing performance issues and very high steal > time on dom0. In my case I wasn't able to start any domU as the dom0 had > not enough CPU time and it just ended with error (due to some timeout). > Unfortunately nor Ian Campbell was able to tell me what is the reason of > this behavior and what was changed. > > Best regards, > -- > Peter Viskup > --20cf303b4183e6a63e04d4db63e3 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Hi Peter,

Seems things are going fine w= ith minimum steal time cpu usage (vary between 5-20) with Xen 4.1.4 and lat= est centos 5.9 xen kernel.

What is the kernel you = are running on your server?



On Sun, Feb 3, 2013 at 10:13 PM, Peter Viskup <= ;skupko.sk@gmail.c= om> wrote:
On 0= 2/02/2013 12:54 AM, Linux Hack wrote:
Hi,

One of the server is under high cpu usage and when checked steal time is ca= using the high cpu usage. However I have pinned the vcpu's for dom0 ded= icatedly but still no luck.

Any thought's that would be great?


I had the same issue. Looks like things changed with newer PvOPs kernels (2= .6.32+) and now the old fashioned setup of dedication of one CPU for dom0 (= xm vcpu-pin 0 all 0) is causing performance issues and very high steal time= on dom0. In my case I wasn't able to start any domU as the dom0 had no= t enough CPU time and it just ended with error (due to some timeout). Unfor= tunately nor Ian Campbell was able to tell me what is the reason of this be= havior and what was changed.

Best regards,
--
Peter Viskup

--20cf303b4183e6a63e04d4db63e3-- --===============5586204410203836130== 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 --===============5586204410203836130==-- From xen-users-bounces@lists.xen.org Mon Feb 04 12:43:14 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 04 Feb 2013 12:43: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 1U2LNO-00060Y-Cj; Mon, 04 Feb 2013 12:42:22 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U2LNN-00060A-9R for xen-users@lists.xensource.com; Mon, 04 Feb 2013 12:42:21 +0000 Received: from [85.158.138.51:62389] by server-10.bemta-3.messagelabs.com id 7A/14-10609-CACAF015; Mon, 04 Feb 2013 12:42:20 +0000 X-Env-Sender: Ian.Campbell@citrix.com X-Msg-Ref: server-2.tower-174.messagelabs.com!1359981738!29126012!1 X-Originating-IP: [46.33.159.39] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNDYuMzMuMTU5LjM5ID0+IDIwNTkz\n X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 25567 invoked from network); 4 Feb 2013 12:42:18 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (46.33.159.39) by server-2.tower-174.messagelabs.com with RC4-SHA encrypted SMTP; 4 Feb 2013 12:42:18 -0000 X-IronPort-AV: E=Sophos;i="4.84,598,1355097600"; d="scan'208";a="1118339" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 04 Feb 2013 12:42: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.297.1; Mon, 4 Feb 2013 12:42:18 +0000 Message-ID: <1359981737.7743.5.camel@zakaz.uk.xensource.com> From: Ian Campbell To: Sandi Romih Date: Mon, 4 Feb 2013 12:42:17 +0000 In-Reply-To: References: Organization: Citrix Systems, Inc. X-Mailer: Evolution 3.4.4-1 MIME-Version: 1.0 Cc: "xen-users@lists.xensource.com" Subject: Re: [Xen-users] Recommended linux kernel for xen 4.2.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 Sun, 2013-02-03 at 23:05 +0000, Sandi Romih wrote: > Which linux kernel is best suited for the dom0? The best option is the kernel provided by your distro, assuming it has one (most do these days). Unless you have very specific requirements there's not really much reason to build you own. > According to this http://wiki.xen.org/wiki/XenKernelFeatures, linux > 3.1.0 is the latest version supported, but this page was last updated > Oct 2011. Any recent mainline kernel (from 3.0 onwards) should work as a domain 0. If you don't want to use your distro kernel then it's up to you, but it would be wise to either pick an actively maintained (by kernel.org) stable branch or to latest mainline release. I suppose that wiki page stops at 3.1.0 because after then it's all mainline... Ian. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Mon Feb 04 12:43:14 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 04 Feb 2013 12:43: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 1U2LNO-00060Y-Cj; Mon, 04 Feb 2013 12:42:22 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U2LNN-00060A-9R for xen-users@lists.xensource.com; Mon, 04 Feb 2013 12:42:21 +0000 Received: from [85.158.138.51:62389] by server-10.bemta-3.messagelabs.com id 7A/14-10609-CACAF015; Mon, 04 Feb 2013 12:42:20 +0000 X-Env-Sender: Ian.Campbell@citrix.com X-Msg-Ref: server-2.tower-174.messagelabs.com!1359981738!29126012!1 X-Originating-IP: [46.33.159.39] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNDYuMzMuMTU5LjM5ID0+IDIwNTkz\n X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 25567 invoked from network); 4 Feb 2013 12:42:18 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (46.33.159.39) by server-2.tower-174.messagelabs.com with RC4-SHA encrypted SMTP; 4 Feb 2013 12:42:18 -0000 X-IronPort-AV: E=Sophos;i="4.84,598,1355097600"; d="scan'208";a="1118339" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 04 Feb 2013 12:42: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.297.1; Mon, 4 Feb 2013 12:42:18 +0000 Message-ID: <1359981737.7743.5.camel@zakaz.uk.xensource.com> From: Ian Campbell To: Sandi Romih Date: Mon, 4 Feb 2013 12:42:17 +0000 In-Reply-To: References: Organization: Citrix Systems, Inc. X-Mailer: Evolution 3.4.4-1 MIME-Version: 1.0 Cc: "xen-users@lists.xensource.com" Subject: Re: [Xen-users] Recommended linux kernel for xen 4.2.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 Sun, 2013-02-03 at 23:05 +0000, Sandi Romih wrote: > Which linux kernel is best suited for the dom0? The best option is the kernel provided by your distro, assuming it has one (most do these days). Unless you have very specific requirements there's not really much reason to build you own. > According to this http://wiki.xen.org/wiki/XenKernelFeatures, linux > 3.1.0 is the latest version supported, but this page was last updated > Oct 2011. Any recent mainline kernel (from 3.0 onwards) should work as a domain 0. If you don't want to use your distro kernel then it's up to you, but it would be wise to either pick an actively maintained (by kernel.org) stable branch or to latest mainline release. I suppose that wiki page stops at 3.1.0 because after then it's all mainline... Ian. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Mon Feb 04 12:57:46 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 04 Feb 2013 12:57: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 1U2LbV-0007JB-Ab; Mon, 04 Feb 2013 12:56:57 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U2LbT-0007J3-NA for xen-users@lists.xen.org; Mon, 04 Feb 2013 12:56:56 +0000 Received: from [85.158.139.83:7729] by server-6.bemta-5.messagelabs.com id B3/6D-01489-610BF015; Mon, 04 Feb 2013 12:56:54 +0000 X-Env-Sender: juergen.gross@ts.fujitsu.com X-Msg-Ref: server-4.tower-182.messagelabs.com!1359982575!25337503!1 X-Originating-IP: [80.70.172.49] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogODAuNzAuMTcyLjQ5ID0+IDI4MTMwMg==\n X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 17765 invoked from network); 4 Feb 2013 12:56:15 -0000 Received: from dgate10.ts.fujitsu.com (HELO dgate10.ts.fujitsu.com) (80.70.172.49) by server-4.tower-182.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 4 Feb 2013 12:56:15 -0000 DomainKey-Signature: s=s1536a; d=ts.fujitsu.com; c=nofws; q=dns; h=X-SBRSScore:X-IronPort-AV:Received:X-IronPort-AV: Received:Received:Message-ID:Date:From:Organization: User-Agent:MIME-Version:To:CC:Subject:References: In-Reply-To:Content-Type:Content-Transfer-Encoding; b=TmlWuRrQliFT2aNaO5uUDToxx2Sq3SgDs6pfA4H5aUkukqLnwcNHooZ5 7EiDMfgDJNy7LAzMNqEDryDMs05e+xOJSxbMwOBVa0f0MUDrD8v/WUlIM 9P06Cx0Jr5jbogQvnEgpYBBBYNTPzoTSBCM++nNuy6/MlAu9RJUALhM64 I9eh0KnhZp22qeuvE6nv/dbe4wUa1Y8t7GluP7yaHxrRjToeLD48cxm0W gR1QLdkYqZ+Zb+wzUHQlbpgRH+XSz; DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=ts.fujitsu.com; i=@ts.fujitsu.com; q=dns/txt; s=s1536b; t=1359982575; x=1391518575; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=ggVTHf5eTUJyqfyBpcdN4Mvdc9IM2jRV0GhBiy1w3Ds=; b=nA8ihCB22b3wMN1YXSoPEJGkpLkCi1N0Th8+O3+Lw6ZZTpzQbD+DBboT m2+jIzBqrnFMobvKocLVMDi0b2aUBTkS379cWV9+JrRjc/kb7vMgyBiIR KtOhWEAlmAmnsyYAkLLup/fsGn4tAbln6oFHRbccONZvu24OX4dQ1EYiI LBnhQztFwpYCie8bYUvWhiVQhaCh/0Ua0Q9OTdTArEwiEYj/7aJ7pWjWd c4JiG8/Et0OQRyVhD08bvdnmfLFIU; X-SBRSScore: None X-IronPort-AV: E=Sophos;i="4.84,600,1355094000"; d="scan'208";a="135687953" Received: from abgdgate40u.abg.fsc.net ([172.25.138.90]) by dgate10u.abg.fsc.net with ESMTP; 04 Feb 2013 13:56:14 +0100 X-IronPort-AV: E=Sophos;i="4.84,600,1355094000"; d="scan'208";a="158201034" Received: from sanpedro.mch.fsc.net ([172.17.20.6]) by abgdgate40u.abg.fsc.net with SMTP; 04 Feb 2013 13:56:13 +0100 Received: from [172.17.21.50] (verdon.osd.mch.fsc.net [172.17.21.50]) by sanpedro.mch.fsc.net (Postfix) with ESMTP id D8EB79669F9; Mon, 4 Feb 2013 13:56:13 +0100 (CET) Message-ID: <510FAFED.2010503@ts.fujitsu.com> Date: Mon, 04 Feb 2013 13:56:13 +0100 From: Juergen Gross Organization: Fujitsu Technology Solutions GmbH User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.16) Gecko/20121215 Iceowl/1.0b1 Icedove/3.0.11 MIME-Version: 1.0 To: Linux Hack References: <510F6165.9010908@ts.fujitsu.com> In-Reply-To: Cc: "xen-users@lists.xen.org" Subject: Re: [Xen-users] xl cpupool X-BeenThere: xen-users@lists.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 Am 04.02.2013 08:43, schrieb Linux Hack: > Hi > > That's something interesting. Would it possible to make this work on xm > or xl tool stack on xen version 3.4.4/4.1.4? 3.4.4: no (cpupools were introduced in 4.1) 4.1.4: yes. Please note, that xl is marked as "experimental" in 4.1. xm should work. Juergen > > On Monday, February 4, 2013, Juergen Gross > wrote: > > Hi, > > > > Am 02.02.2013 00:53, schrieb Linux Hack: > >> > >> Hi, > >> > >> Would it possible to create cpupools with xl after the server boot and > >> then assign one cpu-pool to dom0 and another one for dom-u's? > > > > Yes. > > > > You have to (assuming Xen 4.2): > > > > 1. remove cpus from Pool-0 with "xl cpupool-cpu-remove" > > 2. reduce number of dom0 cpus to fit to reduced Pool-0 with "xl vcpu-set" > > 3. create the domU cpupool with "xl cpupool-create" > > 4. assign the free cpus to the new cpupool ("xl cpupool-cpu-add") > > 5. create the domUs with "pool=" to start them in the new > cpupool > > (either in the config files of the domUs or as parameter of "xl > create" > > > >> Also is there any change to make this work on server startup? > > > > You would have to add an init script in dom0. -- Juergen Gross Principal Developer Operating Systems PBG PDG ES&S SWE OS6 Telephone: +49 (0) 89 3222 2967 Fujitsu Technology Solutions e-mail: juergen.gross@ts.fujitsu.com Domagkstr. 28 Internet: ts.fujitsu.com D-80807 Muenchen Company details: ts.fujitsu.com/imprint.html _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Mon Feb 04 12:57:46 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 04 Feb 2013 12:57: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 1U2LbV-0007JB-Ab; Mon, 04 Feb 2013 12:56:57 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U2LbT-0007J3-NA for xen-users@lists.xen.org; Mon, 04 Feb 2013 12:56:56 +0000 Received: from [85.158.139.83:7729] by server-6.bemta-5.messagelabs.com id B3/6D-01489-610BF015; Mon, 04 Feb 2013 12:56:54 +0000 X-Env-Sender: juergen.gross@ts.fujitsu.com X-Msg-Ref: server-4.tower-182.messagelabs.com!1359982575!25337503!1 X-Originating-IP: [80.70.172.49] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogODAuNzAuMTcyLjQ5ID0+IDI4MTMwMg==\n X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 17765 invoked from network); 4 Feb 2013 12:56:15 -0000 Received: from dgate10.ts.fujitsu.com (HELO dgate10.ts.fujitsu.com) (80.70.172.49) by server-4.tower-182.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 4 Feb 2013 12:56:15 -0000 DomainKey-Signature: s=s1536a; d=ts.fujitsu.com; c=nofws; q=dns; h=X-SBRSScore:X-IronPort-AV:Received:X-IronPort-AV: Received:Received:Message-ID:Date:From:Organization: User-Agent:MIME-Version:To:CC:Subject:References: In-Reply-To:Content-Type:Content-Transfer-Encoding; b=TmlWuRrQliFT2aNaO5uUDToxx2Sq3SgDs6pfA4H5aUkukqLnwcNHooZ5 7EiDMfgDJNy7LAzMNqEDryDMs05e+xOJSxbMwOBVa0f0MUDrD8v/WUlIM 9P06Cx0Jr5jbogQvnEgpYBBBYNTPzoTSBCM++nNuy6/MlAu9RJUALhM64 I9eh0KnhZp22qeuvE6nv/dbe4wUa1Y8t7GluP7yaHxrRjToeLD48cxm0W gR1QLdkYqZ+Zb+wzUHQlbpgRH+XSz; DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=ts.fujitsu.com; i=@ts.fujitsu.com; q=dns/txt; s=s1536b; t=1359982575; x=1391518575; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=ggVTHf5eTUJyqfyBpcdN4Mvdc9IM2jRV0GhBiy1w3Ds=; b=nA8ihCB22b3wMN1YXSoPEJGkpLkCi1N0Th8+O3+Lw6ZZTpzQbD+DBboT m2+jIzBqrnFMobvKocLVMDi0b2aUBTkS379cWV9+JrRjc/kb7vMgyBiIR KtOhWEAlmAmnsyYAkLLup/fsGn4tAbln6oFHRbccONZvu24OX4dQ1EYiI LBnhQztFwpYCie8bYUvWhiVQhaCh/0Ua0Q9OTdTArEwiEYj/7aJ7pWjWd c4JiG8/Et0OQRyVhD08bvdnmfLFIU; X-SBRSScore: None X-IronPort-AV: E=Sophos;i="4.84,600,1355094000"; d="scan'208";a="135687953" Received: from abgdgate40u.abg.fsc.net ([172.25.138.90]) by dgate10u.abg.fsc.net with ESMTP; 04 Feb 2013 13:56:14 +0100 X-IronPort-AV: E=Sophos;i="4.84,600,1355094000"; d="scan'208";a="158201034" Received: from sanpedro.mch.fsc.net ([172.17.20.6]) by abgdgate40u.abg.fsc.net with SMTP; 04 Feb 2013 13:56:13 +0100 Received: from [172.17.21.50] (verdon.osd.mch.fsc.net [172.17.21.50]) by sanpedro.mch.fsc.net (Postfix) with ESMTP id D8EB79669F9; Mon, 4 Feb 2013 13:56:13 +0100 (CET) Message-ID: <510FAFED.2010503@ts.fujitsu.com> Date: Mon, 04 Feb 2013 13:56:13 +0100 From: Juergen Gross Organization: Fujitsu Technology Solutions GmbH User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.16) Gecko/20121215 Iceowl/1.0b1 Icedove/3.0.11 MIME-Version: 1.0 To: Linux Hack References: <510F6165.9010908@ts.fujitsu.com> In-Reply-To: Cc: "xen-users@lists.xen.org" Subject: Re: [Xen-users] xl cpupool X-BeenThere: xen-users@lists.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 Am 04.02.2013 08:43, schrieb Linux Hack: > Hi > > That's something interesting. Would it possible to make this work on xm > or xl tool stack on xen version 3.4.4/4.1.4? 3.4.4: no (cpupools were introduced in 4.1) 4.1.4: yes. Please note, that xl is marked as "experimental" in 4.1. xm should work. Juergen > > On Monday, February 4, 2013, Juergen Gross > wrote: > > Hi, > > > > Am 02.02.2013 00:53, schrieb Linux Hack: > >> > >> Hi, > >> > >> Would it possible to create cpupools with xl after the server boot and > >> then assign one cpu-pool to dom0 and another one for dom-u's? > > > > Yes. > > > > You have to (assuming Xen 4.2): > > > > 1. remove cpus from Pool-0 with "xl cpupool-cpu-remove" > > 2. reduce number of dom0 cpus to fit to reduced Pool-0 with "xl vcpu-set" > > 3. create the domU cpupool with "xl cpupool-create" > > 4. assign the free cpus to the new cpupool ("xl cpupool-cpu-add") > > 5. create the domUs with "pool=" to start them in the new > cpupool > > (either in the config files of the domUs or as parameter of "xl > create" > > > >> Also is there any change to make this work on server startup? > > > > You would have to add an init script in dom0. -- Juergen Gross Principal Developer Operating Systems PBG PDG ES&S SWE OS6 Telephone: +49 (0) 89 3222 2967 Fujitsu Technology Solutions e-mail: juergen.gross@ts.fujitsu.com Domagkstr. 28 Internet: ts.fujitsu.com D-80807 Muenchen Company details: ts.fujitsu.com/imprint.html _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Mon Feb 04 14:18:22 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 04 Feb 2013 14:18: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 1U2MrA-0002cV-D7; Mon, 04 Feb 2013 14:17:12 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U2Mr8-0002cL-Ga for xen-users@lists.xen.org; Mon, 04 Feb 2013 14:17:10 +0000 Received: from [85.158.138.51:42121] by server-11.bemta-3.messagelabs.com id 2F/BF-10249-5E2CF015; Mon, 04 Feb 2013 14:17:09 +0000 X-Env-Sender: digvijaych@gmail.com X-Msg-Ref: server-7.tower-174.messagelabs.com!1359987427!21962173!1 X-Originating-IP: [209.85.217.172] 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.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 21498 invoked from network); 4 Feb 2013 14:17:07 -0000 Received: from mail-lb0-f172.google.com (HELO mail-lb0-f172.google.com) (209.85.217.172) by server-7.tower-174.messagelabs.com with RC4-SHA encrypted SMTP; 4 Feb 2013 14:17:07 -0000 Received: by mail-lb0-f172.google.com with SMTP id n8so6729967lbj.17 for ; Mon, 04 Feb 2013 06:17:07 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=WHHFxRRAKB6LX/EdX9PfUTaXvgzE8ihHynguAWKeqao=; b=sOzbWahLqBegSIwiPHFZpyuirDBTVK+PB5a3E0n9zEZgdgxH9LwegIPEz75LtODZG2 jbC5FvzwlgIdfhi3PLSDnvdrDdTT90EmSgF1BDkpc/EtuGKxw5Ds+fv8+UvXmU1abTOj bYydUzAAdiIXGkIHFlmGYttBs1X32TgSmJM2xvFBzTHBtwSqe1FL7tJ5nzsCL7Sv21tg hXKVMNTHWHfjxpnOZlgtCyeuuwyEKwuns1Nj70HzmuXMalJoQlcDN6v8N0HX20q3kuye 1oUyIOGefhEQkOlJwbiM9J+w7i8NhBF0AEjhVQH/Ororzfetu/KMmFZUmpIEVTP+pFRG DIlw== MIME-Version: 1.0 X-Received: by 10.152.104.199 with SMTP id gg7mr19228726lab.14.1359987426882; Mon, 04 Feb 2013 06:17:06 -0800 (PST) Received: by 10.112.79.37 with HTTP; Mon, 4 Feb 2013 06:17:06 -0800 (PST) In-Reply-To: <1359971583.5281.11.camel@zakaz.uk.xensource.com> References: <1359971583.5281.11.camel@zakaz.uk.xensource.com> Date: Mon, 4 Feb 2013 19:47:06 +0530 Message-ID: From: digvijay chauhan To: Ian Campbell Cc: "xen-users@lists.xen.org" Subject: Re: [Xen-users] how to use sctp during live migration of vm with 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="===============8371273538723736833==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============8371273538723736833== Content-Type: multipart/alternative; boundary=f46d040890c17a745f04d4e6bfee --f46d040890c17a745f04d4e6bfee Content-Type: text/plain; charset=ISO-8859-1 Thank you. On Mon, Feb 4, 2013 at 3:23 PM, Ian Campbell wrote: > Please do not cross post, > http://wiki.xen.org/wiki/Asking_Xen_Devel_Questions and > http://wiki.xen.org/wiki/Xen_Users_Netiquette both ask you not to. > > Since this is a users question I've moved devel to Bcc > > On Fri, 2013-02-01 at 14:18 +0000, digvijay chauhan wrote: > > I want to carry out the performance analysis of transport > > protocol i.e sctp so how can we achieve it.Instead of using tcp if we > > have to use sctp how to do that? > > The xl migrate command takes a -s option which specifies the command to > run to connect to the target, the default is to use ssh but you can > supply any script you like. > > The script should take its stdin/stdout and connect them, via whatever > means, to the stdin/stdout of "xl migrate-receive" running on the remote > host. > > So you just need to arrange for "whatever means" to mean SCTP. If you > have a netcat type utility for SCTP then it ought to be relatively > straightforward. > > Ian. > > --f46d040890c17a745f04d4e6bfee Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Thank you.

On Mon, Feb 4, 2013 at 3:23 PM= , Ian Campbell <Ian.Campbell@citrix.com> wrote:
Please do not cross post,
http://wiki.xen.org/wiki/Asking_Xen_Devel_Questions and
http://wiki.xen.org/wiki/Xen_Users_Netiquette both ask you not to.

Since this is a users question I've moved devel to Bcc

On Fri, 2013-02-01 at 14:18 +0000, digvijay chauhan wrote:
> =A0 =A0 =A0 =A0 =A0I want to carry out the performance analysis of tra= nsport
> protocol i.e sctp so how can we achieve it.Instead of using tcp if we<= br> > have to use sctp how to do that?

The xl migrate command takes a -s option which specifies the command = to
run to connect to the target, the default is to use ssh but you can
supply any script you like.

The script should take its stdin/stdout and connect them, via whatever
means, to the stdin/stdout of "xl migrate-receive" running on the= remote
host.

So you just need to arrange for "whatever means" to mean SCTP. If= you
have a netcat type utility for SCTP then it ought to be relatively
straightforward.

Ian.


--f46d040890c17a745f04d4e6bfee-- --===============8371273538723736833== 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 --===============8371273538723736833==-- From xen-users-bounces@lists.xen.org Mon Feb 04 14:18:22 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 04 Feb 2013 14:18: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 1U2MrA-0002cV-D7; Mon, 04 Feb 2013 14:17:12 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U2Mr8-0002cL-Ga for xen-users@lists.xen.org; Mon, 04 Feb 2013 14:17:10 +0000 Received: from [85.158.138.51:42121] by server-11.bemta-3.messagelabs.com id 2F/BF-10249-5E2CF015; Mon, 04 Feb 2013 14:17:09 +0000 X-Env-Sender: digvijaych@gmail.com X-Msg-Ref: server-7.tower-174.messagelabs.com!1359987427!21962173!1 X-Originating-IP: [209.85.217.172] 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.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 21498 invoked from network); 4 Feb 2013 14:17:07 -0000 Received: from mail-lb0-f172.google.com (HELO mail-lb0-f172.google.com) (209.85.217.172) by server-7.tower-174.messagelabs.com with RC4-SHA encrypted SMTP; 4 Feb 2013 14:17:07 -0000 Received: by mail-lb0-f172.google.com with SMTP id n8so6729967lbj.17 for ; Mon, 04 Feb 2013 06:17:07 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=WHHFxRRAKB6LX/EdX9PfUTaXvgzE8ihHynguAWKeqao=; b=sOzbWahLqBegSIwiPHFZpyuirDBTVK+PB5a3E0n9zEZgdgxH9LwegIPEz75LtODZG2 jbC5FvzwlgIdfhi3PLSDnvdrDdTT90EmSgF1BDkpc/EtuGKxw5Ds+fv8+UvXmU1abTOj bYydUzAAdiIXGkIHFlmGYttBs1X32TgSmJM2xvFBzTHBtwSqe1FL7tJ5nzsCL7Sv21tg hXKVMNTHWHfjxpnOZlgtCyeuuwyEKwuns1Nj70HzmuXMalJoQlcDN6v8N0HX20q3kuye 1oUyIOGefhEQkOlJwbiM9J+w7i8NhBF0AEjhVQH/Ororzfetu/KMmFZUmpIEVTP+pFRG DIlw== MIME-Version: 1.0 X-Received: by 10.152.104.199 with SMTP id gg7mr19228726lab.14.1359987426882; Mon, 04 Feb 2013 06:17:06 -0800 (PST) Received: by 10.112.79.37 with HTTP; Mon, 4 Feb 2013 06:17:06 -0800 (PST) In-Reply-To: <1359971583.5281.11.camel@zakaz.uk.xensource.com> References: <1359971583.5281.11.camel@zakaz.uk.xensource.com> Date: Mon, 4 Feb 2013 19:47:06 +0530 Message-ID: From: digvijay chauhan To: Ian Campbell Cc: "xen-users@lists.xen.org" Subject: Re: [Xen-users] how to use sctp during live migration of vm with 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="===============8371273538723736833==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============8371273538723736833== Content-Type: multipart/alternative; boundary=f46d040890c17a745f04d4e6bfee --f46d040890c17a745f04d4e6bfee Content-Type: text/plain; charset=ISO-8859-1 Thank you. On Mon, Feb 4, 2013 at 3:23 PM, Ian Campbell wrote: > Please do not cross post, > http://wiki.xen.org/wiki/Asking_Xen_Devel_Questions and > http://wiki.xen.org/wiki/Xen_Users_Netiquette both ask you not to. > > Since this is a users question I've moved devel to Bcc > > On Fri, 2013-02-01 at 14:18 +0000, digvijay chauhan wrote: > > I want to carry out the performance analysis of transport > > protocol i.e sctp so how can we achieve it.Instead of using tcp if we > > have to use sctp how to do that? > > The xl migrate command takes a -s option which specifies the command to > run to connect to the target, the default is to use ssh but you can > supply any script you like. > > The script should take its stdin/stdout and connect them, via whatever > means, to the stdin/stdout of "xl migrate-receive" running on the remote > host. > > So you just need to arrange for "whatever means" to mean SCTP. If you > have a netcat type utility for SCTP then it ought to be relatively > straightforward. > > Ian. > > --f46d040890c17a745f04d4e6bfee Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Thank you.

On Mon, Feb 4, 2013 at 3:23 PM= , Ian Campbell <Ian.Campbell@citrix.com> wrote:
Please do not cross post,
http://wiki.xen.org/wiki/Asking_Xen_Devel_Questions and
http://wiki.xen.org/wiki/Xen_Users_Netiquette both ask you not to.

Since this is a users question I've moved devel to Bcc

On Fri, 2013-02-01 at 14:18 +0000, digvijay chauhan wrote:
> =A0 =A0 =A0 =A0 =A0I want to carry out the performance analysis of tra= nsport
> protocol i.e sctp so how can we achieve it.Instead of using tcp if we<= br> > have to use sctp how to do that?

The xl migrate command takes a -s option which specifies the command = to
run to connect to the target, the default is to use ssh but you can
supply any script you like.

The script should take its stdin/stdout and connect them, via whatever
means, to the stdin/stdout of "xl migrate-receive" running on the= remote
host.

So you just need to arrange for "whatever means" to mean SCTP. If= you
have a netcat type utility for SCTP then it ought to be relatively
straightforward.

Ian.


--f46d040890c17a745f04d4e6bfee-- --===============8371273538723736833== 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 --===============8371273538723736833==-- From xen-users-bounces@lists.xen.org Mon Feb 04 18:31:55 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 04 Feb 2013 18:31: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 1U2QoK-0002UM-Fx; Mon, 04 Feb 2013 18:30:32 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U2QoJ-0002UH-2N for xen-users@lists.xen.org; Mon, 04 Feb 2013 18:30:31 +0000 Received: from [193.109.254.147:58873] by server-13.bemta-14.messagelabs.com id 73/D3-30639-64EFF015; Mon, 04 Feb 2013 18:30:30 +0000 X-Env-Sender: smkent@smkent.net X-Msg-Ref: server-15.tower-27.messagelabs.com!1360002626!2752730!1 X-Originating-IP: [209.85.215.45] 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.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 4336 invoked from network); 4 Feb 2013 18:30:27 -0000 Received: from mail-la0-f45.google.com (HELO mail-la0-f45.google.com) (209.85.215.45) by server-15.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 4 Feb 2013 18:30:27 -0000 Received: by mail-la0-f45.google.com with SMTP id er20so4936858lab.18 for ; Mon, 04 Feb 2013 10:30:26 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-received:x-originating-ip:date:message-id:subject :from:to:content-type:x-gm-message-state; bh=4isv9toBl7WCZ4vN4Nzbu4VTfOM5J/1R+mAAzAjXnxk=; b=CUVSKoNKGdneQwIhBBB+TrPd5S566Bx39fad9+Au9eqQ2mEeYdG3bffTnmJMNfrPTp bsmi+qMRt1mXu8htSg3M+9NrMIZCXdnW2vjJnAAtUlzmQ8yorpXcbWthqZGU/XILx6gy o+KJYWYU2rnsHLMBYl1HDW01bHwcslrftMdt2+UTmBnhbWYqCvlQCNy/Kl0+fvHNY3rJ GGVzAJ7LBqbiEdht5npKLwX0ArEhoSuwws2hMoBIQ3Uubo2++xUi/avfIaoRE6WG5tFz ImLIZSrtp8pm82BTl/yWFAAFriZy/1dD36oQFJRw8jJj/+QnKXCQW3EMj+qWDPSiKZ00 tfYQ== MIME-Version: 1.0 X-Received: by 10.112.41.202 with SMTP id h10mr8563005lbl.20.1360002625996; Mon, 04 Feb 2013 10:30:25 -0800 (PST) Received: by 10.112.131.137 with HTTP; Mon, 4 Feb 2013 10:30:25 -0800 (PST) X-Originating-IP: [208.79.144.52] Date: Mon, 4 Feb 2013 10:30:25 -0800 Message-ID: From: Stephen Kent To: xen-users@lists.xen.org X-Gm-Message-State: ALoCoQkYGcp52T6/BJW6xn9+dK0eDpKOKY6qvGzYEjLj7qNbQKRyf5gyK796H8f5apG7SAiQRDDO Subject: [Xen-users] XENBUS: Timeout connecting to device: device/vbd/51712 (local state 3, remote state 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="===============4148582915027399298==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============4148582915027399298== Content-Type: multipart/alternative; boundary=e0cb4efa6dfc6a88a404d4ea49ad --e0cb4efa6dfc6a88a404d4ea49ad Content-Type: text/plain; charset=UTF-8 I just upgraded my computer from an old kernel (2.6.34-xen) to 3.6.11, and upgraded Xen to 4.2.0. I can't seem to get my domU to boot, as it can't find the root filesystem. I've compiled a domU kernel (also 3.6.11) with xen-blkfront built-in and set the domU config file with this disk configuration: disk = [ 'file:/home/data/xen/megatron/root.img,xvda,w' ] (The disk is just a file with an ext3 filesystem, I can mount it on loopback in dom0) After I xl start my domU, xl block-list in dom0 shows the device connected to the domU but the domU kernel (with root=/dev/xvda) can't find the root filesystem: [...] XENBUS: Timeout connecting to device: device/vbd/51712 (local state 3, remote state 1) console [netcon0] enabled netconsole: network logging started ALSA device list: No soundcards found. md: Waiting for all devices to be available before autodetect md: If you don't use raid, use raid=noautodetect md: Autodetecting RAID arrays. md: Scanned 0 and added 0 devices. md: autorun ... md: ... autorun DONE. VFS: Cannot open root device "xvda" or unknown-block(0,0): error -6 Please append a correct "root=" boot option; here are the available partitions: Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) Pid: 1, comm: swapper/0 Not tainted 3.6.11-gentoo #8 Call Trace: [] ? panic+0xc5/0x1cc [] ? printk+0x4c/0x51 [] ? mount_block_root+0x1d4/0x1f2 [] ? lg_local_lock+0x11/0x14 [] ? kvm_io_bus_sort_cmp+0x1c/0x27 [] ? sys_mknodat+0x12c/0x140 [] ? mount_root+0x124/0x12b [] ? initrd_load+0x303/0x309 [] ? prepare_namespace+0x168/0x19e [] ? kernel_init+0x17f/0x191 [] ? parse_early_options+0x2a/0x2a [] ? kernel_thread_helper+0x4/0x10 [] ? retint_restore_args+0x5/0x6 [] ? gs_change+0x13/0x13 I don't see any earlier kernel messages about the Xen block frontend driver loading. Am I missing a kernel option or something? I'm not sure what else to try. Thanks! --e0cb4efa6dfc6a88a404d4ea49ad Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
I just upgraded my computer from an old kernel (2.6.34-xen) to 3.6.11,= and upgraded Xen to 4.2.0. I can't seem to get my domU to boot, as it = can't find the root filesystem.

I've compi= led a domU kernel (also 3.6.11) with xen-blkfront built-in and set the domU= config file with this disk configuration:

disk =3D [ 'file:/home/data/xen/megatron/root.img,x= vda,w' ]

(The disk is just a file with an ext3= filesystem, I can mount it on loopback in dom0)

After I xl start my domU, xl block-list in dom0 shows the device connected = to the domU but the domU kernel (with root=3D/dev/xvda) can't find the = root filesystem:


[...]
XENBUS: Timeout connecting to device: device/vbd/51712 (local state 3, remo= te state 1)
console [netcon0] enabled
netconsole: netwo= rk logging started
ALSA device list:
=C2=A0 No soundcar= ds found.
md: Waiting for all devices to be available before autodetect
md: If you don't use raid, use raid=3Dnoautodetect
md: Auto= detecting RAID arrays.
md: Scanned 0 and added 0 devices.
md: autorun ...
md: ... autorun DONE.
VFS: Cannot = open root device "xvda" or unknown-block(0,0): error -6
Please append a correct "root=3D" boot option; here are the avai= lable partitions:
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-bl= ock(0,0)
Pid: 1, comm: swapper/0 Not tainted 3.6.11-gentoo #8
Call Trace:
=C2=A0[<ffffffff815c59ff>] ? panic+0xc5/= 0x1cc
=C2=A0[<ffffffff815c5bd9>] ? printk+0x4c/0x51
=C2=A0[&= lt;ffffffff819990cd>] ? mount_block_root+0x1d4/0x1f2
=C2=A0[&l= t;ffffffff8108ebaa>] ? lg_local_lock+0x11/0x14
=C2=A0[<ffff= ffff81002930>] ? kvm_io_bus_sort_cmp+0x1c/0x27
=C2=A0[<ffffffff8110fcf8>] ? sys_mknodat+0x12c/0x140
= =C2=A0[<ffffffff8199920f>] ? mount_root+0x124/0x12b
=C2=A0[= <ffffffff81999d8f>] ? initrd_load+0x303/0x309
=C2=A0[<ff= ffffff8199937e>] ? prepare_namespace+0x168/0x19e
=C2=A0[<ffffffff81998702>] ? kernel_init+0x17f/0x191
= =C2=A0[<ffffffff8199852b>] ? parse_early_options+0x2a/0x2a
= =C2=A0[<ffffffff815cf644>] ? kernel_thread_helper+0x4/0x10
= =C2=A0[<ffffffff815c8338>] ? retint_restore_args+0x5/0x6
=C2=A0[<ffffffff815cf640>] ? gs_change+0x13/0x13

<= /div>

I don't see any earlier kernel messages about = the Xen block frontend driver loading. Am I missing a kernel option or some= thing? I'm not sure what else to try.

Thanks!
--e0cb4efa6dfc6a88a404d4ea49ad-- --===============4148582915027399298== 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 --===============4148582915027399298==-- From xen-users-bounces@lists.xen.org Mon Feb 04 18:31:55 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 04 Feb 2013 18:31: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 1U2QoK-0002UM-Fx; Mon, 04 Feb 2013 18:30:32 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U2QoJ-0002UH-2N for xen-users@lists.xen.org; Mon, 04 Feb 2013 18:30:31 +0000 Received: from [193.109.254.147:58873] by server-13.bemta-14.messagelabs.com id 73/D3-30639-64EFF015; Mon, 04 Feb 2013 18:30:30 +0000 X-Env-Sender: smkent@smkent.net X-Msg-Ref: server-15.tower-27.messagelabs.com!1360002626!2752730!1 X-Originating-IP: [209.85.215.45] 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.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 4336 invoked from network); 4 Feb 2013 18:30:27 -0000 Received: from mail-la0-f45.google.com (HELO mail-la0-f45.google.com) (209.85.215.45) by server-15.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 4 Feb 2013 18:30:27 -0000 Received: by mail-la0-f45.google.com with SMTP id er20so4936858lab.18 for ; Mon, 04 Feb 2013 10:30:26 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-received:x-originating-ip:date:message-id:subject :from:to:content-type:x-gm-message-state; bh=4isv9toBl7WCZ4vN4Nzbu4VTfOM5J/1R+mAAzAjXnxk=; b=CUVSKoNKGdneQwIhBBB+TrPd5S566Bx39fad9+Au9eqQ2mEeYdG3bffTnmJMNfrPTp bsmi+qMRt1mXu8htSg3M+9NrMIZCXdnW2vjJnAAtUlzmQ8yorpXcbWthqZGU/XILx6gy o+KJYWYU2rnsHLMBYl1HDW01bHwcslrftMdt2+UTmBnhbWYqCvlQCNy/Kl0+fvHNY3rJ GGVzAJ7LBqbiEdht5npKLwX0ArEhoSuwws2hMoBIQ3Uubo2++xUi/avfIaoRE6WG5tFz ImLIZSrtp8pm82BTl/yWFAAFriZy/1dD36oQFJRw8jJj/+QnKXCQW3EMj+qWDPSiKZ00 tfYQ== MIME-Version: 1.0 X-Received: by 10.112.41.202 with SMTP id h10mr8563005lbl.20.1360002625996; Mon, 04 Feb 2013 10:30:25 -0800 (PST) Received: by 10.112.131.137 with HTTP; Mon, 4 Feb 2013 10:30:25 -0800 (PST) X-Originating-IP: [208.79.144.52] Date: Mon, 4 Feb 2013 10:30:25 -0800 Message-ID: From: Stephen Kent To: xen-users@lists.xen.org X-Gm-Message-State: ALoCoQkYGcp52T6/BJW6xn9+dK0eDpKOKY6qvGzYEjLj7qNbQKRyf5gyK796H8f5apG7SAiQRDDO Subject: [Xen-users] XENBUS: Timeout connecting to device: device/vbd/51712 (local state 3, remote state 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="===============4148582915027399298==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============4148582915027399298== Content-Type: multipart/alternative; boundary=e0cb4efa6dfc6a88a404d4ea49ad --e0cb4efa6dfc6a88a404d4ea49ad Content-Type: text/plain; charset=UTF-8 I just upgraded my computer from an old kernel (2.6.34-xen) to 3.6.11, and upgraded Xen to 4.2.0. I can't seem to get my domU to boot, as it can't find the root filesystem. I've compiled a domU kernel (also 3.6.11) with xen-blkfront built-in and set the domU config file with this disk configuration: disk = [ 'file:/home/data/xen/megatron/root.img,xvda,w' ] (The disk is just a file with an ext3 filesystem, I can mount it on loopback in dom0) After I xl start my domU, xl block-list in dom0 shows the device connected to the domU but the domU kernel (with root=/dev/xvda) can't find the root filesystem: [...] XENBUS: Timeout connecting to device: device/vbd/51712 (local state 3, remote state 1) console [netcon0] enabled netconsole: network logging started ALSA device list: No soundcards found. md: Waiting for all devices to be available before autodetect md: If you don't use raid, use raid=noautodetect md: Autodetecting RAID arrays. md: Scanned 0 and added 0 devices. md: autorun ... md: ... autorun DONE. VFS: Cannot open root device "xvda" or unknown-block(0,0): error -6 Please append a correct "root=" boot option; here are the available partitions: Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) Pid: 1, comm: swapper/0 Not tainted 3.6.11-gentoo #8 Call Trace: [] ? panic+0xc5/0x1cc [] ? printk+0x4c/0x51 [] ? mount_block_root+0x1d4/0x1f2 [] ? lg_local_lock+0x11/0x14 [] ? kvm_io_bus_sort_cmp+0x1c/0x27 [] ? sys_mknodat+0x12c/0x140 [] ? mount_root+0x124/0x12b [] ? initrd_load+0x303/0x309 [] ? prepare_namespace+0x168/0x19e [] ? kernel_init+0x17f/0x191 [] ? parse_early_options+0x2a/0x2a [] ? kernel_thread_helper+0x4/0x10 [] ? retint_restore_args+0x5/0x6 [] ? gs_change+0x13/0x13 I don't see any earlier kernel messages about the Xen block frontend driver loading. Am I missing a kernel option or something? I'm not sure what else to try. Thanks! --e0cb4efa6dfc6a88a404d4ea49ad Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
I just upgraded my computer from an old kernel (2.6.34-xen) to 3.6.11,= and upgraded Xen to 4.2.0. I can't seem to get my domU to boot, as it = can't find the root filesystem.

I've compi= led a domU kernel (also 3.6.11) with xen-blkfront built-in and set the domU= config file with this disk configuration:

disk =3D [ 'file:/home/data/xen/megatron/root.img,x= vda,w' ]

(The disk is just a file with an ext3= filesystem, I can mount it on loopback in dom0)

After I xl start my domU, xl block-list in dom0 shows the device connected = to the domU but the domU kernel (with root=3D/dev/xvda) can't find the = root filesystem:


[...]
XENBUS: Timeout connecting to device: device/vbd/51712 (local state 3, remo= te state 1)
console [netcon0] enabled
netconsole: netwo= rk logging started
ALSA device list:
=C2=A0 No soundcar= ds found.
md: Waiting for all devices to be available before autodetect
md: If you don't use raid, use raid=3Dnoautodetect
md: Auto= detecting RAID arrays.
md: Scanned 0 and added 0 devices.
md: autorun ...
md: ... autorun DONE.
VFS: Cannot = open root device "xvda" or unknown-block(0,0): error -6
Please append a correct "root=3D" boot option; here are the avai= lable partitions:
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-bl= ock(0,0)
Pid: 1, comm: swapper/0 Not tainted 3.6.11-gentoo #8
Call Trace:
=C2=A0[<ffffffff815c59ff>] ? panic+0xc5/= 0x1cc
=C2=A0[<ffffffff815c5bd9>] ? printk+0x4c/0x51
=C2=A0[&= lt;ffffffff819990cd>] ? mount_block_root+0x1d4/0x1f2
=C2=A0[&l= t;ffffffff8108ebaa>] ? lg_local_lock+0x11/0x14
=C2=A0[<ffff= ffff81002930>] ? kvm_io_bus_sort_cmp+0x1c/0x27
=C2=A0[<ffffffff8110fcf8>] ? sys_mknodat+0x12c/0x140
= =C2=A0[<ffffffff8199920f>] ? mount_root+0x124/0x12b
=C2=A0[= <ffffffff81999d8f>] ? initrd_load+0x303/0x309
=C2=A0[<ff= ffffff8199937e>] ? prepare_namespace+0x168/0x19e
=C2=A0[<ffffffff81998702>] ? kernel_init+0x17f/0x191
= =C2=A0[<ffffffff8199852b>] ? parse_early_options+0x2a/0x2a
= =C2=A0[<ffffffff815cf644>] ? kernel_thread_helper+0x4/0x10
= =C2=A0[<ffffffff815c8338>] ? retint_restore_args+0x5/0x6
=C2=A0[<ffffffff815cf640>] ? gs_change+0x13/0x13

<= /div>

I don't see any earlier kernel messages about = the Xen block frontend driver loading. Am I missing a kernel option or some= thing? I'm not sure what else to try.

Thanks!
--e0cb4efa6dfc6a88a404d4ea49ad-- --===============4148582915027399298== 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 --===============4148582915027399298==-- From xen-users-bounces@lists.xen.org Mon Feb 04 19:01:59 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 04 Feb 2013 19:01: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 1U2RHV-0003oh-ML; Mon, 04 Feb 2013 19:00:41 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from <2rushikeshj@gmail.com>) id 1U2RHT-0003oJ-T9; Mon, 04 Feb 2013 19:00:40 +0000 Received: from [85.158.139.83:51678] by server-13.bemta-5.messagelabs.com id 8F/19-06769-75500115; Mon, 04 Feb 2013 19:00:39 +0000 X-Env-Sender: 2rushikeshj@gmail.com X-Msg-Ref: server-6.tower-182.messagelabs.com!1360004437!23796219!1 X-Originating-IP: [209.85.216.42] 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.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 12952 invoked from network); 4 Feb 2013 19:00:38 -0000 Received: from mail-qa0-f42.google.com (HELO mail-qa0-f42.google.com) (209.85.216.42) by server-6.tower-182.messagelabs.com with RC4-SHA encrypted SMTP; 4 Feb 2013 19:00:38 -0000 Received: by mail-qa0-f42.google.com with SMTP id cr7so1407654qab.8 for ; Mon, 04 Feb 2013 10:59:37 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:date:message-id:subject:from:to :content-type; bh=ZzuUDlAVySpIrGXZT5zopTUsuhaYGdnXXgAQpjLLZOQ=; b=faAAQ5fd2sS5Hz3NfS0NAbKrVKlNHCy7mg4P6qVK7YK008WFDKWY97QHtsEDdOk0Pm vK/KXLhPjgP5s5vyhlSZFbpWFl3TIKsFuOASDmohLpeEur3Ze93SpzcmMKo6VFuj27Aw 8PmUsN/w8vfwArrGEe/m+srJFXT3SO/c/RXCeQp+2kxqlYE56AlVeBXbi93ST36oPTQh nv8UC8mk2XtLajnRtXAGUPA7+k6Khp5BsRUgPefOZTXK6pCJUe8+Z+1TLw6+Xm4QkpP8 FMn8+Jdf4CUa0ZoX1kEHHCJivld1/PLisOT7GhtSanx7JyySDgIAv8RJ3n5D4+9FGvKx PyHw== MIME-Version: 1.0 X-Received: by 10.224.30.203 with SMTP id v11mr18977288qac.31.1360004377641; Mon, 04 Feb 2013 10:59:37 -0800 (PST) Received: by 10.229.131.81 with HTTP; Mon, 4 Feb 2013 10:59:37 -0800 (PST) Date: Tue, 5 Feb 2013 00:29:37 +0530 Message-ID: From: Rushikesh Jadhav <2rushikeshj@gmail.com> To: xen-users@lists.xen.org, xen-api@lists.xen.org Subject: [Xen-users] CentOS6 & Ubuntu12 PV domU 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: multipart/mixed; boundary="===============7845671993858379148==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============7845671993858379148== Content-Type: multipart/alternative; boundary=20cf3074d594d280d604d4eab103 --20cf3074d594d280d604d4eab103 Content-Type: text/plain; charset=ISO-8859-1 Hi Everyone, I'm not sure if I'm the only one facing it or is it a known issue. CentOS6 and Ubuntu12.04 domU report less memory than they actually have. Example, a CentOS6 VM with 512MB shows only 484 as total in free -m. A Ubuntu domU shows 284M as total if the static max is 8GB and target memory is 512MB. Both domUs are 64bit. CentOS5 reports the exact same memory as its target. I would be thankful if someone can share a reason or their domU # free -m Regards, Rushikesh --20cf3074d594d280d604d4eab103 Content-Type: text/html; charset=ISO-8859-1 Hi Everyone,

I'm not sure if I'm the only one facing it or is it a known issue.
CentOS6 and Ubuntu12.04 domU report less memory than they actually have.

Example, a CentOS6 VM with 512MB shows only 484 as total in free -m.
A Ubuntu domU shows 284M as total if the static max is 8GB and target memory is 512MB.

Both domUs are 64bit.

CentOS5 reports the exact same memory as its target.
I would be thankful if someone can share a reason or their domU # free -m

Regards,
Rushikesh

--20cf3074d594d280d604d4eab103-- --===============7845671993858379148== 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 --===============7845671993858379148==-- From xen-users-bounces@lists.xen.org Mon Feb 04 19:01:59 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 04 Feb 2013 19:01: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 1U2RHV-0003oh-ML; Mon, 04 Feb 2013 19:00:41 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from <2rushikeshj@gmail.com>) id 1U2RHT-0003oJ-T9; Mon, 04 Feb 2013 19:00:40 +0000 Received: from [85.158.139.83:51678] by server-13.bemta-5.messagelabs.com id 8F/19-06769-75500115; Mon, 04 Feb 2013 19:00:39 +0000 X-Env-Sender: 2rushikeshj@gmail.com X-Msg-Ref: server-6.tower-182.messagelabs.com!1360004437!23796219!1 X-Originating-IP: [209.85.216.42] 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.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 12952 invoked from network); 4 Feb 2013 19:00:38 -0000 Received: from mail-qa0-f42.google.com (HELO mail-qa0-f42.google.com) (209.85.216.42) by server-6.tower-182.messagelabs.com with RC4-SHA encrypted SMTP; 4 Feb 2013 19:00:38 -0000 Received: by mail-qa0-f42.google.com with SMTP id cr7so1407654qab.8 for ; Mon, 04 Feb 2013 10:59:37 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:date:message-id:subject:from:to :content-type; bh=ZzuUDlAVySpIrGXZT5zopTUsuhaYGdnXXgAQpjLLZOQ=; b=faAAQ5fd2sS5Hz3NfS0NAbKrVKlNHCy7mg4P6qVK7YK008WFDKWY97QHtsEDdOk0Pm vK/KXLhPjgP5s5vyhlSZFbpWFl3TIKsFuOASDmohLpeEur3Ze93SpzcmMKo6VFuj27Aw 8PmUsN/w8vfwArrGEe/m+srJFXT3SO/c/RXCeQp+2kxqlYE56AlVeBXbi93ST36oPTQh nv8UC8mk2XtLajnRtXAGUPA7+k6Khp5BsRUgPefOZTXK6pCJUe8+Z+1TLw6+Xm4QkpP8 FMn8+Jdf4CUa0ZoX1kEHHCJivld1/PLisOT7GhtSanx7JyySDgIAv8RJ3n5D4+9FGvKx PyHw== MIME-Version: 1.0 X-Received: by 10.224.30.203 with SMTP id v11mr18977288qac.31.1360004377641; Mon, 04 Feb 2013 10:59:37 -0800 (PST) Received: by 10.229.131.81 with HTTP; Mon, 4 Feb 2013 10:59:37 -0800 (PST) Date: Tue, 5 Feb 2013 00:29:37 +0530 Message-ID: From: Rushikesh Jadhav <2rushikeshj@gmail.com> To: xen-users@lists.xen.org, xen-api@lists.xen.org Subject: [Xen-users] CentOS6 & Ubuntu12 PV domU 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: multipart/mixed; boundary="===============7845671993858379148==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============7845671993858379148== Content-Type: multipart/alternative; boundary=20cf3074d594d280d604d4eab103 --20cf3074d594d280d604d4eab103 Content-Type: text/plain; charset=ISO-8859-1 Hi Everyone, I'm not sure if I'm the only one facing it or is it a known issue. CentOS6 and Ubuntu12.04 domU report less memory than they actually have. Example, a CentOS6 VM with 512MB shows only 484 as total in free -m. A Ubuntu domU shows 284M as total if the static max is 8GB and target memory is 512MB. Both domUs are 64bit. CentOS5 reports the exact same memory as its target. I would be thankful if someone can share a reason or their domU # free -m Regards, Rushikesh --20cf3074d594d280d604d4eab103 Content-Type: text/html; charset=ISO-8859-1 Hi Everyone,

I'm not sure if I'm the only one facing it or is it a known issue.
CentOS6 and Ubuntu12.04 domU report less memory than they actually have.

Example, a CentOS6 VM with 512MB shows only 484 as total in free -m.
A Ubuntu domU shows 284M as total if the static max is 8GB and target memory is 512MB.

Both domUs are 64bit.

CentOS5 reports the exact same memory as its target.
I would be thankful if someone can share a reason or their domU # free -m

Regards,
Rushikesh

--20cf3074d594d280d604d4eab103-- --===============7845671993858379148== 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 --===============7845671993858379148==-- From xen-users-bounces@lists.xen.org Mon Feb 04 19:46:48 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 04 Feb 2013 19:46: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 1U2Ryw-00053g-EY; Mon, 04 Feb 2013 19:45:34 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from <2rushikeshj@gmail.com>) id 1U2Ryv-00053b-34 for xen-users@lists.xen.org; Mon, 04 Feb 2013 19:45:33 +0000 Received: from [193.109.254.147:4371] by server-15.bemta-14.messagelabs.com id 76/0C-24599-CDF00115; Mon, 04 Feb 2013 19:45:32 +0000 X-Env-Sender: 2rushikeshj@gmail.com X-Msg-Ref: server-13.tower-27.messagelabs.com!1360007130!10065994!1 X-Originating-IP: [209.85.128.43] 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.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 5981 invoked from network); 4 Feb 2013 19:45:31 -0000 Received: from mail-qe0-f43.google.com (HELO mail-qe0-f43.google.com) (209.85.128.43) by server-13.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 4 Feb 2013 19:45:31 -0000 Received: by mail-qe0-f43.google.com with SMTP id 3so2455092qeb.2 for ; Mon, 04 Feb 2013 11:45:29 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=/Suum+jElVNxVoWxOzzfGtEE7CqmQgfyTegvzALfu5A=; b=qWbNPC9V4dHVtkQZkWO5A4AQgp1Fj7YdEoQ6PHmQlE4y5JvBrOrwz6tOJKCFjxL7BI F1efyI8hQ93UKxHDZ9hrSH3odEXsL9sNIT4gZWoRvAcvOqSbYf/MNrMfZjJvsZNGFEmo W5v533iX0FZW7bw1pl2anSdH90REJHKXrCwOOwBZD32TFSrFX/cimO9nyvMTmYMjWE+C zb8fhnQyC2yfheegTAD8Xr8WP8EbXgYQ7xubdjESyk2u1BUmig2qcNCKs36SR5txk5pE l+YY7v8vp5f4gu6mpf2Wd5FFR8Qe0pwqEU+/afE6n2Azft5e7Q/d+PXVzLBAJa1n37u8 w9HA== MIME-Version: 1.0 X-Received: by 10.224.178.77 with SMTP id bl13mr18704242qab.13.1360007129729; Mon, 04 Feb 2013 11:45:29 -0800 (PST) Received: by 10.229.131.81 with HTTP; Mon, 4 Feb 2013 11:45:29 -0800 (PST) In-Reply-To: References: Date: Tue, 5 Feb 2013 01:15:29 +0530 Message-ID: From: Rushikesh Jadhav <2rushikeshj@gmail.com> To: Stephen Kent Cc: xen-users@lists.xen.org Subject: Re: [Xen-users] XENBUS: Timeout connecting to device: device/vbd/51712 (local state 3, remote state 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="===============2436142667443675490==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============2436142667443675490== Content-Type: multipart/alternative; boundary=20cf302ef79edc09a404d4eb55b5 --20cf302ef79edc09a404d4eb55b5 Content-Type: text/plain; charset=ISO-8859-1 On Tue, Feb 5, 2013 at 12:00 AM, Stephen Kent wrote: > I just upgraded my computer from an old kernel (2.6.34-xen) to 3.6.11, and > upgraded Xen to 4.2.0. I can't seem to get my domU to boot, as it can't > find the root filesystem. > > I've compiled a domU kernel (also 3.6.11) with xen-blkfront built-in and > set the domU config file with this disk configuration: > > disk = [ 'file:/home/data/xen/megatron/root.img,xvda,w' ] > > (The disk is just a file with an ext3 filesystem, I can mount it on > loopback in dom0) > > After I xl start my domU, xl block-list in dom0 shows the device connected > to the domU but the domU kernel (with root=/dev/xvda) can't find the root > filesystem: > > > [...] > XENBUS: Timeout connecting to device: device/vbd/51712 (local state 3, > remote state 1) > console [netcon0] enabled > netconsole: network logging started > ALSA device list: > No soundcards found. > md: Waiting for all devices to be available before autodetect > md: If you don't use raid, use raid=noautodetect > md: Autodetecting RAID arrays. > md: Scanned 0 and added 0 devices. > md: autorun ... > md: ... autorun DONE. > VFS: Cannot open root device "xvda" or unknown-block(0,0): error -6 > Please append a correct "root=" boot option; here are the available > partitions: > Kernel panic - not syncing: VFS: Unable to mount root fs on > unknown-block(0,0) > Pid: 1, comm: swapper/0 Not tainted 3.6.11-gentoo #8 > Call Trace: > [] ? panic+0xc5/0x1cc > [] ? printk+0x4c/0x51 > [] ? mount_block_root+0x1d4/0x1f2 > [] ? lg_local_lock+0x11/0x14 > [] ? kvm_io_bus_sort_cmp+0x1c/0x27 > [] ? sys_mknodat+0x12c/0x140 > [] ? mount_root+0x124/0x12b > [] ? initrd_load+0x303/0x309 > [] ? prepare_namespace+0x168/0x19e > [] ? kernel_init+0x17f/0x191 > [] ? parse_early_options+0x2a/0x2a > [] ? kernel_thread_helper+0x4/0x10 > [] ? retint_restore_args+0x5/0x6 > [] ? gs_change+0x13/0x13 > > Check if you have PCI enabled in domU kernel. Select the PCI options while you do # make menuconfig > > I don't see any earlier kernel messages about the Xen block frontend > driver loading. Am I missing a kernel option or something? I'm not sure > what else to try. > > Thanks! > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xen.org > http://lists.xen.org/xen-users > --20cf302ef79edc09a404d4eb55b5 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
On Tue, Feb 5, 2013 at 12:00 AM, Stephen Kent <= smkent@smkent.net> wrote:
I just upgraded my computer from an old kernel (2.6.34-xen) to 3.6.11,= and upgraded Xen to 4.2.0. I can't seem to get my domU to boot, as it = can't find the root filesystem.

I've compi= led a domU kernel (also 3.6.11) with xen-blkfront built-in and set the domU= config file with this disk configuration:

disk =3D [ 'file:/home/data/xen/megatron/root.img,x= vda,w' ]

(The disk is just a file with an ext3= filesystem, I can mount it on loopback in dom0)

After I xl start my domU, xl block-list in dom0 shows the device connected = to the domU but the domU kernel (with root=3D/dev/xvda) can't find the = root filesystem:


[...]
XENBUS: Timeout connecting to device: device/vbd/51712 (local state 3, remo= te state 1)
console [netcon0] enabled
netconsole: netwo= rk logging started
ALSA device list:
=A0 No soundcards = found.
md: Waiting for all devices to be available before autodetect
md: If you don't use raid, use raid=3Dnoautodetect
md: Auto= detecting RAID arrays.
md: Scanned 0 and added 0 devices.
md: autorun ...
md: ... autorun DONE.
VFS: Cannot = open root device "xvda" or unknown-block(0,0): error -6
Please append a correct "root=3D" boot option; here are the avai= lable partitions:
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-bl= ock(0,0)
Pid: 1, comm: swapper/0 Not tainted 3.6.11-gentoo #8
Call Trace:
=A0[<ffffffff815c59ff>] ? panic+0xc5/0x1= cc
=A0[<ffffffff815c5bd9>] ? printk+0x4c/0x51
=A0[<fff= fffff819990cd>] ? mount_block_root+0x1d4/0x1f2
=A0[<fffffff= f8108ebaa>] ? lg_local_lock+0x11/0x14
=A0[<ffffffff81002930= >] ? kvm_io_bus_sort_cmp+0x1c/0x27
=A0[<ffffffff8110fcf8>] ? sys_mknodat+0x12c/0x140
=A0[= <ffffffff8199920f>] ? mount_root+0x124/0x12b
=A0[<ffffff= ff81999d8f>] ? initrd_load+0x303/0x309
=A0[<ffffffff8199937= e>] ? prepare_namespace+0x168/0x19e
=A0[<ffffffff81998702>] ? kernel_init+0x17f/0x191
=A0[= <ffffffff8199852b>] ? parse_early_options+0x2a/0x2a
=A0[<= ;ffffffff815cf644>] ? kernel_thread_helper+0x4/0x10
=A0[<ff= ffffff815c8338>] ? retint_restore_args+0x5/0x6
=A0[<ffffffff815cf640>] ? gs_change+0x13/0x13


Check if you have PCI enabled in domU kernel.
Se= lect the PCI options while you do # make menuconfig

=A0

I don't see any earlier kernel messages = about the Xen block frontend driver loading. Am I missing a kernel option o= r something? I'm not sure what else to try.

Thanks!

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

--20cf302ef79edc09a404d4eb55b5-- --===============2436142667443675490== 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 --===============2436142667443675490==-- From xen-users-bounces@lists.xen.org Mon Feb 04 19:46:48 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 04 Feb 2013 19:46: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 1U2Ryw-00053g-EY; Mon, 04 Feb 2013 19:45:34 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from <2rushikeshj@gmail.com>) id 1U2Ryv-00053b-34 for xen-users@lists.xen.org; Mon, 04 Feb 2013 19:45:33 +0000 Received: from [193.109.254.147:4371] by server-15.bemta-14.messagelabs.com id 76/0C-24599-CDF00115; Mon, 04 Feb 2013 19:45:32 +0000 X-Env-Sender: 2rushikeshj@gmail.com X-Msg-Ref: server-13.tower-27.messagelabs.com!1360007130!10065994!1 X-Originating-IP: [209.85.128.43] 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.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 5981 invoked from network); 4 Feb 2013 19:45:31 -0000 Received: from mail-qe0-f43.google.com (HELO mail-qe0-f43.google.com) (209.85.128.43) by server-13.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 4 Feb 2013 19:45:31 -0000 Received: by mail-qe0-f43.google.com with SMTP id 3so2455092qeb.2 for ; Mon, 04 Feb 2013 11:45:29 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=/Suum+jElVNxVoWxOzzfGtEE7CqmQgfyTegvzALfu5A=; b=qWbNPC9V4dHVtkQZkWO5A4AQgp1Fj7YdEoQ6PHmQlE4y5JvBrOrwz6tOJKCFjxL7BI F1efyI8hQ93UKxHDZ9hrSH3odEXsL9sNIT4gZWoRvAcvOqSbYf/MNrMfZjJvsZNGFEmo W5v533iX0FZW7bw1pl2anSdH90REJHKXrCwOOwBZD32TFSrFX/cimO9nyvMTmYMjWE+C zb8fhnQyC2yfheegTAD8Xr8WP8EbXgYQ7xubdjESyk2u1BUmig2qcNCKs36SR5txk5pE l+YY7v8vp5f4gu6mpf2Wd5FFR8Qe0pwqEU+/afE6n2Azft5e7Q/d+PXVzLBAJa1n37u8 w9HA== MIME-Version: 1.0 X-Received: by 10.224.178.77 with SMTP id bl13mr18704242qab.13.1360007129729; Mon, 04 Feb 2013 11:45:29 -0800 (PST) Received: by 10.229.131.81 with HTTP; Mon, 4 Feb 2013 11:45:29 -0800 (PST) In-Reply-To: References: Date: Tue, 5 Feb 2013 01:15:29 +0530 Message-ID: From: Rushikesh Jadhav <2rushikeshj@gmail.com> To: Stephen Kent Cc: xen-users@lists.xen.org Subject: Re: [Xen-users] XENBUS: Timeout connecting to device: device/vbd/51712 (local state 3, remote state 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="===============2436142667443675490==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============2436142667443675490== Content-Type: multipart/alternative; boundary=20cf302ef79edc09a404d4eb55b5 --20cf302ef79edc09a404d4eb55b5 Content-Type: text/plain; charset=ISO-8859-1 On Tue, Feb 5, 2013 at 12:00 AM, Stephen Kent wrote: > I just upgraded my computer from an old kernel (2.6.34-xen) to 3.6.11, and > upgraded Xen to 4.2.0. I can't seem to get my domU to boot, as it can't > find the root filesystem. > > I've compiled a domU kernel (also 3.6.11) with xen-blkfront built-in and > set the domU config file with this disk configuration: > > disk = [ 'file:/home/data/xen/megatron/root.img,xvda,w' ] > > (The disk is just a file with an ext3 filesystem, I can mount it on > loopback in dom0) > > After I xl start my domU, xl block-list in dom0 shows the device connected > to the domU but the domU kernel (with root=/dev/xvda) can't find the root > filesystem: > > > [...] > XENBUS: Timeout connecting to device: device/vbd/51712 (local state 3, > remote state 1) > console [netcon0] enabled > netconsole: network logging started > ALSA device list: > No soundcards found. > md: Waiting for all devices to be available before autodetect > md: If you don't use raid, use raid=noautodetect > md: Autodetecting RAID arrays. > md: Scanned 0 and added 0 devices. > md: autorun ... > md: ... autorun DONE. > VFS: Cannot open root device "xvda" or unknown-block(0,0): error -6 > Please append a correct "root=" boot option; here are the available > partitions: > Kernel panic - not syncing: VFS: Unable to mount root fs on > unknown-block(0,0) > Pid: 1, comm: swapper/0 Not tainted 3.6.11-gentoo #8 > Call Trace: > [] ? panic+0xc5/0x1cc > [] ? printk+0x4c/0x51 > [] ? mount_block_root+0x1d4/0x1f2 > [] ? lg_local_lock+0x11/0x14 > [] ? kvm_io_bus_sort_cmp+0x1c/0x27 > [] ? sys_mknodat+0x12c/0x140 > [] ? mount_root+0x124/0x12b > [] ? initrd_load+0x303/0x309 > [] ? prepare_namespace+0x168/0x19e > [] ? kernel_init+0x17f/0x191 > [] ? parse_early_options+0x2a/0x2a > [] ? kernel_thread_helper+0x4/0x10 > [] ? retint_restore_args+0x5/0x6 > [] ? gs_change+0x13/0x13 > > Check if you have PCI enabled in domU kernel. Select the PCI options while you do # make menuconfig > > I don't see any earlier kernel messages about the Xen block frontend > driver loading. Am I missing a kernel option or something? I'm not sure > what else to try. > > Thanks! > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xen.org > http://lists.xen.org/xen-users > --20cf302ef79edc09a404d4eb55b5 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
On Tue, Feb 5, 2013 at 12:00 AM, Stephen Kent <= smkent@smkent.net> wrote:
I just upgraded my computer from an old kernel (2.6.34-xen) to 3.6.11,= and upgraded Xen to 4.2.0. I can't seem to get my domU to boot, as it = can't find the root filesystem.

I've compi= led a domU kernel (also 3.6.11) with xen-blkfront built-in and set the domU= config file with this disk configuration:

disk =3D [ 'file:/home/data/xen/megatron/root.img,x= vda,w' ]

(The disk is just a file with an ext3= filesystem, I can mount it on loopback in dom0)

After I xl start my domU, xl block-list in dom0 shows the device connected = to the domU but the domU kernel (with root=3D/dev/xvda) can't find the = root filesystem:


[...]
XENBUS: Timeout connecting to device: device/vbd/51712 (local state 3, remo= te state 1)
console [netcon0] enabled
netconsole: netwo= rk logging started
ALSA device list:
=A0 No soundcards = found.
md: Waiting for all devices to be available before autodetect
md: If you don't use raid, use raid=3Dnoautodetect
md: Auto= detecting RAID arrays.
md: Scanned 0 and added 0 devices.
md: autorun ...
md: ... autorun DONE.
VFS: Cannot = open root device "xvda" or unknown-block(0,0): error -6
Please append a correct "root=3D" boot option; here are the avai= lable partitions:
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-bl= ock(0,0)
Pid: 1, comm: swapper/0 Not tainted 3.6.11-gentoo #8
Call Trace:
=A0[<ffffffff815c59ff>] ? panic+0xc5/0x1= cc
=A0[<ffffffff815c5bd9>] ? printk+0x4c/0x51
=A0[<fff= fffff819990cd>] ? mount_block_root+0x1d4/0x1f2
=A0[<fffffff= f8108ebaa>] ? lg_local_lock+0x11/0x14
=A0[<ffffffff81002930= >] ? kvm_io_bus_sort_cmp+0x1c/0x27
=A0[<ffffffff8110fcf8>] ? sys_mknodat+0x12c/0x140
=A0[= <ffffffff8199920f>] ? mount_root+0x124/0x12b
=A0[<ffffff= ff81999d8f>] ? initrd_load+0x303/0x309
=A0[<ffffffff8199937= e>] ? prepare_namespace+0x168/0x19e
=A0[<ffffffff81998702>] ? kernel_init+0x17f/0x191
=A0[= <ffffffff8199852b>] ? parse_early_options+0x2a/0x2a
=A0[<= ;ffffffff815cf644>] ? kernel_thread_helper+0x4/0x10
=A0[<ff= ffffff815c8338>] ? retint_restore_args+0x5/0x6
=A0[<ffffffff815cf640>] ? gs_change+0x13/0x13


Check if you have PCI enabled in domU kernel.
Se= lect the PCI options while you do # make menuconfig

=A0

I don't see any earlier kernel messages = about the Xen block frontend driver loading. Am I missing a kernel option o= r something? I'm not sure what else to try.

Thanks!

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

--20cf302ef79edc09a404d4eb55b5-- --===============2436142667443675490== 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 --===============2436142667443675490==-- From xen-users-bounces@lists.xen.org Mon Feb 04 20:36:56 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 04 Feb 2013 20:36: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 1U2SlI-0006AD-CC; Mon, 04 Feb 2013 20:35:32 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U2SlG-0006A8-7y for xen-users@lists.xen.org; Mon, 04 Feb 2013 20:35:30 +0000 Received: from [85.158.138.51:20408] by server-6.bemta-3.messagelabs.com id 68/C2-29959-19B10115; Mon, 04 Feb 2013 20:35:29 +0000 X-Env-Sender: george.shuklin@gmail.com X-Msg-Ref: server-4.tower-174.messagelabs.com!1360010128!27590573!1 X-Originating-IP: [209.85.215.42] X-SpamReason: No, hits=0.0 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, spamassassin: X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 3649 invoked from network); 4 Feb 2013 20:35:28 -0000 Received: from mail-la0-f42.google.com (HELO mail-la0-f42.google.com) (209.85.215.42) by server-4.tower-174.messagelabs.com with RC4-SHA encrypted SMTP; 4 Feb 2013 20:35:28 -0000 Received: by mail-la0-f42.google.com with SMTP id fe20so5065681lab.1 for ; Mon, 04 Feb 2013 12:35:27 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:user-agent:mime-version:to:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=5BkSc5a0FA03gb0XioWiBACtbXZLrSQHYZ8ZyAYnAvM=; b=jlASIimwxN1qjiIMCeqggCSbaBbnueH5eDp2Zjjq3DKXNzug5xqHUUWG7GhkSbb5kT yi7e9Hxwyzy5a42oUWAMlFZ2j45vSKXgLnnWdJmmt2c1brviZq1USMCHz3BGeuYcQYZM sCLXe6VwI2zXg80OuQX54EfoSBvTUCpkatEgRNfkQMXYgBfYOXzwtqQn1MqRkYeBjE6L Px6XQpWTvss7E15XNwCiyqg7GPwuG2HUKpux5VfIOaEREc2qmIdw9qlPa5nR56CpeLZm yT/7e+zCQDT36IwTEgiXwXI578QujTJ9pgWKkbDbQf6maabYvh6H0YQNkGUr7jHCAhs0 xO5Q== X-Received: by 10.112.49.106 with SMTP id t10mr3496159lbn.6.1360010127705; Mon, 04 Feb 2013 12:35:27 -0800 (PST) Received: from home.desunote.ru ([2a00:11d8:1201:0:962b:18:e716:fb97]) by mx.google.com with ESMTPS id i4sm3474691lbd.5.2013.02.04.12.35.26 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 04 Feb 2013 12:35:27 -0800 (PST) Message-ID: <51101B8E.4050206@gmail.com> Date: Tue, 05 Feb 2013 00:35:26 +0400 From: George Shuklin User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:10.0.12) Gecko/20130116 Icedove/10.0.12 MIME-Version: 1.0 To: xen-users@lists.xen.org References: In-Reply-To: Subject: Re: [Xen-users] CentOS6 & Ubuntu12 PV domU 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-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 04.02.2013 22:59, Rushikesh Jadhav wrote: > Hi Everyone, > > I'm not sure if I'm the only one facing it or is it a known issue. > CentOS6 and Ubuntu12.04 domU report less memory than they actually have. > > Example, a CentOS6 VM with 512MB shows only 484 as total in free -m. > A Ubuntu domU shows 284M as total if the static max is 8GB and target > memory is 512MB. > > Both domUs are 64bit. > > CentOS5 reports the exact same memory as its target. > I would be thankful if someone can share a reason or their domU # free -m > User-friendly answer: linux specific. Not XCP issue. Technical stuff: pv-ops version of linux kernel marks some used areas as reserved (you can see this in dmesg output in Memory: line). AFAIK (I'm not sure) -xen version of linux mark those areas as 'available', but 'busy'. PV-ops kernel simply mark it as 'reserved'. You can compare 'free' memory for -xen and pv-ops kernels - it same. But for -xen kernel TotalMem higher and Used is higher too, and for pv-ops TotalMem is lower, but used is lower too. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Mon Feb 04 20:36:56 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 04 Feb 2013 20:36: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 1U2SlI-0006AD-CC; Mon, 04 Feb 2013 20:35:32 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U2SlG-0006A8-7y for xen-users@lists.xen.org; Mon, 04 Feb 2013 20:35:30 +0000 Received: from [85.158.138.51:20408] by server-6.bemta-3.messagelabs.com id 68/C2-29959-19B10115; Mon, 04 Feb 2013 20:35:29 +0000 X-Env-Sender: george.shuklin@gmail.com X-Msg-Ref: server-4.tower-174.messagelabs.com!1360010128!27590573!1 X-Originating-IP: [209.85.215.42] X-SpamReason: No, hits=0.0 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, spamassassin: X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 3649 invoked from network); 4 Feb 2013 20:35:28 -0000 Received: from mail-la0-f42.google.com (HELO mail-la0-f42.google.com) (209.85.215.42) by server-4.tower-174.messagelabs.com with RC4-SHA encrypted SMTP; 4 Feb 2013 20:35:28 -0000 Received: by mail-la0-f42.google.com with SMTP id fe20so5065681lab.1 for ; Mon, 04 Feb 2013 12:35:27 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:user-agent:mime-version:to:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=5BkSc5a0FA03gb0XioWiBACtbXZLrSQHYZ8ZyAYnAvM=; b=jlASIimwxN1qjiIMCeqggCSbaBbnueH5eDp2Zjjq3DKXNzug5xqHUUWG7GhkSbb5kT yi7e9Hxwyzy5a42oUWAMlFZ2j45vSKXgLnnWdJmmt2c1brviZq1USMCHz3BGeuYcQYZM sCLXe6VwI2zXg80OuQX54EfoSBvTUCpkatEgRNfkQMXYgBfYOXzwtqQn1MqRkYeBjE6L Px6XQpWTvss7E15XNwCiyqg7GPwuG2HUKpux5VfIOaEREc2qmIdw9qlPa5nR56CpeLZm yT/7e+zCQDT36IwTEgiXwXI578QujTJ9pgWKkbDbQf6maabYvh6H0YQNkGUr7jHCAhs0 xO5Q== X-Received: by 10.112.49.106 with SMTP id t10mr3496159lbn.6.1360010127705; Mon, 04 Feb 2013 12:35:27 -0800 (PST) Received: from home.desunote.ru ([2a00:11d8:1201:0:962b:18:e716:fb97]) by mx.google.com with ESMTPS id i4sm3474691lbd.5.2013.02.04.12.35.26 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 04 Feb 2013 12:35:27 -0800 (PST) Message-ID: <51101B8E.4050206@gmail.com> Date: Tue, 05 Feb 2013 00:35:26 +0400 From: George Shuklin User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:10.0.12) Gecko/20130116 Icedove/10.0.12 MIME-Version: 1.0 To: xen-users@lists.xen.org References: In-Reply-To: Subject: Re: [Xen-users] CentOS6 & Ubuntu12 PV domU 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-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 04.02.2013 22:59, Rushikesh Jadhav wrote: > Hi Everyone, > > I'm not sure if I'm the only one facing it or is it a known issue. > CentOS6 and Ubuntu12.04 domU report less memory than they actually have. > > Example, a CentOS6 VM with 512MB shows only 484 as total in free -m. > A Ubuntu domU shows 284M as total if the static max is 8GB and target > memory is 512MB. > > Both domUs are 64bit. > > CentOS5 reports the exact same memory as its target. > I would be thankful if someone can share a reason or their domU # free -m > User-friendly answer: linux specific. Not XCP issue. Technical stuff: pv-ops version of linux kernel marks some used areas as reserved (you can see this in dmesg output in Memory: line). AFAIK (I'm not sure) -xen version of linux mark those areas as 'available', but 'busy'. PV-ops kernel simply mark it as 'reserved'. You can compare 'free' memory for -xen and pv-ops kernels - it same. But for -xen kernel TotalMem higher and Used is higher too, and for pv-ops TotalMem is lower, but used is lower too. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Mon Feb 04 21:30:23 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 04 Feb 2013 21:30: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 1U2TbC-0007H2-1v; Mon, 04 Feb 2013 21:29:10 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U2TbB-0007Gw-0P for xen-users@lists.xen.org; Mon, 04 Feb 2013 21:29:09 +0000 Received: from [85.158.138.51:55928] by server-5.bemta-3.messagelabs.com id 65/70-04457-F1820115; Mon, 04 Feb 2013 21:29:03 +0000 X-Env-Sender: matthias.kannenberg@googlemail.com X-Msg-Ref: server-7.tower-174.messagelabs.com!1360013340!22018164!1 X-Originating-IP: [209.85.212.178] X-SpamReason: No, hits=0.3 required=7.0 tests=RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 7740 invoked from network); 4 Feb 2013 21:29:00 -0000 Received: from mail-wi0-f178.google.com (HELO mail-wi0-f178.google.com) (209.85.212.178) by server-7.tower-174.messagelabs.com with RC4-SHA encrypted SMTP; 4 Feb 2013 21:29:00 -0000 Received: by mail-wi0-f178.google.com with SMTP id o1so3513740wic.11 for ; Mon, 04 Feb 2013 13:29:00 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=20120113; h=x-received:mime-version:in-reply-to:references:from:date:message-id :subject:to:cc:content-type; bh=8/Q5p5CsN6Ha6HO4VKmNq/SeAHJlO7CMcKF8pwRHiPg=; b=mv9b7G6MW0otnatROeF+EC0wIFCiSg0tVzUmUChrufRpKqLQqKo3y4hIG4UTffaHWi IzQvF/FeX1xtL0YuzvO6sYKToYoO+AKSrIhwyJzIk/oOMMuguqf2Hrv+yuX5NFuf5oTP crki4O9qGf6wS7qPlf0LH+yHj8J2cIY3IqAaKQRoAiUKhyAYVBX4dCZxRJTD8Rz4Ssfj apJ5Ca1s60GLEAsBdFEjJ80QeSb0/rL7XWSpOLxw3qQ1ZygUbg9gVSI83UDPcr+R14Nr zudYnh7ry0SQD525/6UpRaOUdKroMXuuv+3cNihocHfxLRr+l70ViMZMDkuPUD2W2nO4 8R1Q== X-Received: by 10.180.84.162 with SMTP id a2mr12884519wiz.14.1360013340357; Mon, 04 Feb 2013 13:29:00 -0800 (PST) MIME-Version: 1.0 Received: by 10.194.80.68 with HTTP; Mon, 4 Feb 2013 13:28:40 -0800 (PST) In-Reply-To: <1359980575.7466.5.camel@zakaz.uk.xensource.com> References: <1359369167.6559.46.camel@zakaz.uk.xensource.com> <1359980575.7466.5.camel@zakaz.uk.xensource.com> From: Matthias Date: Mon, 4 Feb 2013 22:28:40 +0100 Message-ID: To: Ian Campbell Cc: "xen-users@lists.xen.org" Subject: Re: [Xen-users] xl nat and wrong IPs X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: 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 guess i finally understood the basic idea of the nat script: You set an IP for the vif interface. This will not be the IP of the interface, but the IP the domU will be using internally. This way if the dom0 receives a package for the configured IP, it will be routed through the dom0-interface to the domU. (In detail: This way the package goes into the iptables forward chain and not the input chain, changing the hosts general treatment of the package). So not setting the interface to the configured IP but only creating an ip route makes perfect sense. But then the vif-nat script assignes an IP+127 to the interface. This creates 2 problems in my opinion: 1) When using the dom0 for routing network traffic from one domU to an other, so basically using the dom0 as a network cable, the src attribute used in the routing creation will alter the source ip address from one domU to the ip+127 address which is, at least in my network setup, pretty annoying. So if you got domUs A (IP 10.0.0.1) and B (IP 10.0.0.2) and send traffic from A to B, B will see the traffic coming from 10.0.0.128 instead of .1 . 2) I haven't tested it, but I don't really know what would happen if you set IPs >128 in the domU configuration and this way create out-of-bounce routing IPs. Well, I think that most people don't use the nat feature of xen and this isn't tested much.. But somebody might want to look at it at a given point of time... For me, changing the IP setting lines to do_or_die ip addr add "0.0.0.0" dev "${dev}" do_or_die ip route add "$vif_ip" dev "${dev}" This doesn't set an IP to the interface in the domU and no src. attribute to the route, fixing the above issues.. Might be worth thinkin about including in xen main line, i don't really know.. Posted this only if somebody might need this later.. 2013/2/4 Ian Campbell : > On Sun, 2013-02-03 at 21:29 +0000, Matthias wrote: >> Hi, >> >> I finally got the chance to do the testing.. >> >> You were right, the issue was due to routing_ip or better why the >> calculated ($ip + 127) is used later here: >> >> do_or_die ip addr add "$router_ip" dev "${dev}" >> do_or_die ip route add "$vif_ip" dev "${dev}" src "$router_ip" >> >> I don't really see any point in creating a dedicated router-IP and > > Glad you've got it sorted, I don't understand this stuff either though > I'm afraid. (Perhaps they form two ends of a point-to-point /31 network? > Total guess) > >> using it this way and i dont' see why this worked for me when using xm >> earlier, but I might did some hacking before to fix this in my xm >> installation, i can't really remember.. > > FWIW this script doesn't appear to have changed in hg for many years. > > Ian. > _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Mon Feb 04 21:30:23 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 04 Feb 2013 21:30: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 1U2TbC-0007H2-1v; Mon, 04 Feb 2013 21:29:10 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U2TbB-0007Gw-0P for xen-users@lists.xen.org; Mon, 04 Feb 2013 21:29:09 +0000 Received: from [85.158.138.51:55928] by server-5.bemta-3.messagelabs.com id 65/70-04457-F1820115; Mon, 04 Feb 2013 21:29:03 +0000 X-Env-Sender: matthias.kannenberg@googlemail.com X-Msg-Ref: server-7.tower-174.messagelabs.com!1360013340!22018164!1 X-Originating-IP: [209.85.212.178] X-SpamReason: No, hits=0.3 required=7.0 tests=RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 7740 invoked from network); 4 Feb 2013 21:29:00 -0000 Received: from mail-wi0-f178.google.com (HELO mail-wi0-f178.google.com) (209.85.212.178) by server-7.tower-174.messagelabs.com with RC4-SHA encrypted SMTP; 4 Feb 2013 21:29:00 -0000 Received: by mail-wi0-f178.google.com with SMTP id o1so3513740wic.11 for ; Mon, 04 Feb 2013 13:29:00 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=20120113; h=x-received:mime-version:in-reply-to:references:from:date:message-id :subject:to:cc:content-type; bh=8/Q5p5CsN6Ha6HO4VKmNq/SeAHJlO7CMcKF8pwRHiPg=; b=mv9b7G6MW0otnatROeF+EC0wIFCiSg0tVzUmUChrufRpKqLQqKo3y4hIG4UTffaHWi IzQvF/FeX1xtL0YuzvO6sYKToYoO+AKSrIhwyJzIk/oOMMuguqf2Hrv+yuX5NFuf5oTP crki4O9qGf6wS7qPlf0LH+yHj8J2cIY3IqAaKQRoAiUKhyAYVBX4dCZxRJTD8Rz4Ssfj apJ5Ca1s60GLEAsBdFEjJ80QeSb0/rL7XWSpOLxw3qQ1ZygUbg9gVSI83UDPcr+R14Nr zudYnh7ry0SQD525/6UpRaOUdKroMXuuv+3cNihocHfxLRr+l70ViMZMDkuPUD2W2nO4 8R1Q== X-Received: by 10.180.84.162 with SMTP id a2mr12884519wiz.14.1360013340357; Mon, 04 Feb 2013 13:29:00 -0800 (PST) MIME-Version: 1.0 Received: by 10.194.80.68 with HTTP; Mon, 4 Feb 2013 13:28:40 -0800 (PST) In-Reply-To: <1359980575.7466.5.camel@zakaz.uk.xensource.com> References: <1359369167.6559.46.camel@zakaz.uk.xensource.com> <1359980575.7466.5.camel@zakaz.uk.xensource.com> From: Matthias Date: Mon, 4 Feb 2013 22:28:40 +0100 Message-ID: To: Ian Campbell Cc: "xen-users@lists.xen.org" Subject: Re: [Xen-users] xl nat and wrong IPs X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: 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 guess i finally understood the basic idea of the nat script: You set an IP for the vif interface. This will not be the IP of the interface, but the IP the domU will be using internally. This way if the dom0 receives a package for the configured IP, it will be routed through the dom0-interface to the domU. (In detail: This way the package goes into the iptables forward chain and not the input chain, changing the hosts general treatment of the package). So not setting the interface to the configured IP but only creating an ip route makes perfect sense. But then the vif-nat script assignes an IP+127 to the interface. This creates 2 problems in my opinion: 1) When using the dom0 for routing network traffic from one domU to an other, so basically using the dom0 as a network cable, the src attribute used in the routing creation will alter the source ip address from one domU to the ip+127 address which is, at least in my network setup, pretty annoying. So if you got domUs A (IP 10.0.0.1) and B (IP 10.0.0.2) and send traffic from A to B, B will see the traffic coming from 10.0.0.128 instead of .1 . 2) I haven't tested it, but I don't really know what would happen if you set IPs >128 in the domU configuration and this way create out-of-bounce routing IPs. Well, I think that most people don't use the nat feature of xen and this isn't tested much.. But somebody might want to look at it at a given point of time... For me, changing the IP setting lines to do_or_die ip addr add "0.0.0.0" dev "${dev}" do_or_die ip route add "$vif_ip" dev "${dev}" This doesn't set an IP to the interface in the domU and no src. attribute to the route, fixing the above issues.. Might be worth thinkin about including in xen main line, i don't really know.. Posted this only if somebody might need this later.. 2013/2/4 Ian Campbell : > On Sun, 2013-02-03 at 21:29 +0000, Matthias wrote: >> Hi, >> >> I finally got the chance to do the testing.. >> >> You were right, the issue was due to routing_ip or better why the >> calculated ($ip + 127) is used later here: >> >> do_or_die ip addr add "$router_ip" dev "${dev}" >> do_or_die ip route add "$vif_ip" dev "${dev}" src "$router_ip" >> >> I don't really see any point in creating a dedicated router-IP and > > Glad you've got it sorted, I don't understand this stuff either though > I'm afraid. (Perhaps they form two ends of a point-to-point /31 network? > Total guess) > >> using it this way and i dont' see why this worked for me when using xm >> earlier, but I might did some hacking before to fix this in my xm >> installation, i can't really remember.. > > FWIW this script doesn't appear to have changed in hg for many years. > > Ian. > _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Mon Feb 04 21:59:25 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 04 Feb 2013 21:59: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 1U2U3F-0007o2-Ve; Mon, 04 Feb 2013 21:58:09 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from <2rushikeshj@gmail.com>) id 1U2U3D-0007nu-Je for xen-users@lists.xen.org; Mon, 04 Feb 2013 21:58:07 +0000 Received: from [85.158.139.211:44983] by server-2.bemta-5.messagelabs.com id 16/EF-16911-EEE20115; Mon, 04 Feb 2013 21:58:06 +0000 X-Env-Sender: 2rushikeshj@gmail.com X-Msg-Ref: server-15.tower-206.messagelabs.com!1360015084!20750511!1 X-Originating-IP: [209.85.128.53] 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.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 21242 invoked from network); 4 Feb 2013 21:58:05 -0000 Received: from mail-qe0-f53.google.com (HELO mail-qe0-f53.google.com) (209.85.128.53) by server-15.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 4 Feb 2013 21:58:05 -0000 Received: by mail-qe0-f53.google.com with SMTP id 1so3049933qee.26 for ; Mon, 04 Feb 2013 13:58:04 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=CPyZ294ihLhy4xYKGmDuWyy8aBHUpNbWv2RUknDNnDw=; b=KoU85KY7sOn1nu9D6wf3j9rQHnVnQMHiRNB37tf9/8qXJiQEYuhHaaXVgBc4ahAoa5 uSFRPpF4CPp1/UeuWg7Kj/ZJeC/C0kK764hjSg6jdqf3zQ0VIcWBWit9ggEcvCKYpkws b9HjJ8D35XlaaT9kqMw3ISBfVJhNJwfruDSpN+te7wl3TdFNJNmx/EoCt9W5QuBMTgVQ XDxHUOwZkH7+C4yuH2CXt8DOvH0eTwJQPuObOKa4ACR/mlpCfQzvyYREuWiRIioUfOcW I7hGE8ziIsFwXsZMDlrRXNh2CqPSJi0H2ib0tyXG8hCga3MkvdAuxcPyyFk3XGlC70H6 9jaQ== MIME-Version: 1.0 X-Received: by 10.229.105.197 with SMTP id u5mr1137003qco.5.1360015084673; Mon, 04 Feb 2013 13:58:04 -0800 (PST) Received: by 10.229.131.81 with HTTP; Mon, 4 Feb 2013 13:58:04 -0800 (PST) In-Reply-To: <51101B8E.4050206@gmail.com> References: <51101B8E.4050206@gmail.com> Date: Tue, 5 Feb 2013 03:28:04 +0530 Message-ID: From: Rushikesh Jadhav <2rushikeshj@gmail.com> To: George Shuklin Cc: xen-users@lists.xen.org Subject: Re: [Xen-users] CentOS6 & Ubuntu12 PV domU 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: multipart/mixed; boundary="===============8282137575582025889==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============8282137575582025889== Content-Type: multipart/alternative; boundary=00235446ff8002dbef04d4ed30a9 --00235446ff8002dbef04d4ed30a9 Content-Type: text/plain; charset=ISO-8859-1 On Tue, Feb 5, 2013 at 2:05 AM, George Shuklin wrote: > On 04.02.2013 22:59, Rushikesh Jadhav wrote: > >> Hi Everyone, >> >> I'm not sure if I'm the only one facing it or is it a known issue. >> CentOS6 and Ubuntu12.04 domU report less memory than they actually have. >> >> Example, a CentOS6 VM with 512MB shows only 484 as total in free -m. >> A Ubuntu domU shows 284M as total if the static max is 8GB and target >> memory is 512MB. >> >> Both domUs are 64bit. >> >> CentOS5 reports the exact same memory as its target. >> I would be thankful if someone can share a reason or their domU # free -m >> >> > User-friendly answer: linux specific. Not XCP issue. > > Technical stuff: pv-ops version of linux kernel marks some used areas as > reserved (you can see this in dmesg output in Memory: line). AFAIK (I'm not > sure) -xen version of linux mark those areas as 'available', but 'busy'. > PV-ops kernel simply mark it as 'reserved'. > > You can compare 'free' memory for -xen and pv-ops kernels - it same. But > for -xen kernel TotalMem higher and Used is higher too, and for pv-ops > TotalMem is lower, but used is lower too. > > Thanks George, I can understand that *some* memory area to be reserved but I dont understand why does it change with the "static-max" parameter of VM. Total memory inside the domU is inversely proportional to the difference of "static-max" and target memory. In case of ubuntu VM, if static-max=8GB and target=1GB then free -m would show something near 600-700MB Whereas, if static-max=2GB and target=1GB then free -m would show near 850MB and if static-max=target=1GB then free -m would show near 950MB. The difference in available domU memory is quite a big figure with more than 100MB difference. I'm not sure but its doubtful that xen would need such huge reserved area. ( for ballooning ? ) > > ______________________________**_________________ > Xen-users mailing list > Xen-users@lists.xen.org > http://lists.xen.org/xen-users > --00235446ff8002dbef04d4ed30a9 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable

On Tue, Feb 5, 2013 at 2:05 AM, George S= huklin <george.shuklin@gmail.com> wrote:
On 04.02.2013 22:59, Rushikesh Jadh= av wrote:
Hi Everyone,

I'm not sure if I'm the only one facing it or is it a known issue.<= br> CentOS6 and Ubuntu12.04 domU report less memory than they actually have.
Example, a CentOS6 VM with 512MB shows only 484 as total in free -m.
A Ubuntu domU shows 284M as total if the static max is 8GB and target memor= y is 512MB.

Both domUs are 64bit.

CentOS5 reports the exact same memory as its target.
I would be thankful if someone can share a reason or their domU # free -m

User-friendly answer: linux specific. Not XCP issue.

Technical stuff: pv-ops version of linux kernel marks some used areas as re= served (you can see this in dmesg output in Memory: line). AFAIK (I'm n= ot sure) -xen version of linux mark those areas as 'available', but= 'busy'. PV-ops kernel simply mark it as 'reserved'.

You can compare 'free' memory for -xen and pv-ops kernels - it same= . But for -xen kernel TotalMem higher and Used is higher too, =A0and for pv= -ops TotalMem is lower, but used is lower too.


Thanks George,

I can understand that *some= * memory area to be reserved but I dont understand why does it change with = the "static-max" parameter of VM.
Total memory inside the domU= is inversely proportional to the difference of "static-max" and = target memory.

In case of ubuntu VM, if static-max=3D8GB and target=3D1GB then free -m= would show something near 600-700MB
Whereas, if static-max=3D2GB and ta= rget=3D1GB then free -m would show near 850MB and if static-max=3Dtarget=3D= 1GB then free -m would show near 950MB.

The difference in available domU memory is quite a big figure with more= than 100MB difference. I'm not sure but its doubtful that xen would ne= ed such huge reserved area. ( for ballooning ? )



=A0

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

--00235446ff8002dbef04d4ed30a9-- --===============8282137575582025889== 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 --===============8282137575582025889==-- From xen-users-bounces@lists.xen.org Mon Feb 04 21:59:25 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 04 Feb 2013 21:59: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 1U2U3F-0007o2-Ve; Mon, 04 Feb 2013 21:58:09 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from <2rushikeshj@gmail.com>) id 1U2U3D-0007nu-Je for xen-users@lists.xen.org; Mon, 04 Feb 2013 21:58:07 +0000 Received: from [85.158.139.211:44983] by server-2.bemta-5.messagelabs.com id 16/EF-16911-EEE20115; Mon, 04 Feb 2013 21:58:06 +0000 X-Env-Sender: 2rushikeshj@gmail.com X-Msg-Ref: server-15.tower-206.messagelabs.com!1360015084!20750511!1 X-Originating-IP: [209.85.128.53] 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.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 21242 invoked from network); 4 Feb 2013 21:58:05 -0000 Received: from mail-qe0-f53.google.com (HELO mail-qe0-f53.google.com) (209.85.128.53) by server-15.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 4 Feb 2013 21:58:05 -0000 Received: by mail-qe0-f53.google.com with SMTP id 1so3049933qee.26 for ; Mon, 04 Feb 2013 13:58:04 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=CPyZ294ihLhy4xYKGmDuWyy8aBHUpNbWv2RUknDNnDw=; b=KoU85KY7sOn1nu9D6wf3j9rQHnVnQMHiRNB37tf9/8qXJiQEYuhHaaXVgBc4ahAoa5 uSFRPpF4CPp1/UeuWg7Kj/ZJeC/C0kK764hjSg6jdqf3zQ0VIcWBWit9ggEcvCKYpkws b9HjJ8D35XlaaT9kqMw3ISBfVJhNJwfruDSpN+te7wl3TdFNJNmx/EoCt9W5QuBMTgVQ XDxHUOwZkH7+C4yuH2CXt8DOvH0eTwJQPuObOKa4ACR/mlpCfQzvyYREuWiRIioUfOcW I7hGE8ziIsFwXsZMDlrRXNh2CqPSJi0H2ib0tyXG8hCga3MkvdAuxcPyyFk3XGlC70H6 9jaQ== MIME-Version: 1.0 X-Received: by 10.229.105.197 with SMTP id u5mr1137003qco.5.1360015084673; Mon, 04 Feb 2013 13:58:04 -0800 (PST) Received: by 10.229.131.81 with HTTP; Mon, 4 Feb 2013 13:58:04 -0800 (PST) In-Reply-To: <51101B8E.4050206@gmail.com> References: <51101B8E.4050206@gmail.com> Date: Tue, 5 Feb 2013 03:28:04 +0530 Message-ID: From: Rushikesh Jadhav <2rushikeshj@gmail.com> To: George Shuklin Cc: xen-users@lists.xen.org Subject: Re: [Xen-users] CentOS6 & Ubuntu12 PV domU 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: multipart/mixed; boundary="===============8282137575582025889==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============8282137575582025889== Content-Type: multipart/alternative; boundary=00235446ff8002dbef04d4ed30a9 --00235446ff8002dbef04d4ed30a9 Content-Type: text/plain; charset=ISO-8859-1 On Tue, Feb 5, 2013 at 2:05 AM, George Shuklin wrote: > On 04.02.2013 22:59, Rushikesh Jadhav wrote: > >> Hi Everyone, >> >> I'm not sure if I'm the only one facing it or is it a known issue. >> CentOS6 and Ubuntu12.04 domU report less memory than they actually have. >> >> Example, a CentOS6 VM with 512MB shows only 484 as total in free -m. >> A Ubuntu domU shows 284M as total if the static max is 8GB and target >> memory is 512MB. >> >> Both domUs are 64bit. >> >> CentOS5 reports the exact same memory as its target. >> I would be thankful if someone can share a reason or their domU # free -m >> >> > User-friendly answer: linux specific. Not XCP issue. > > Technical stuff: pv-ops version of linux kernel marks some used areas as > reserved (you can see this in dmesg output in Memory: line). AFAIK (I'm not > sure) -xen version of linux mark those areas as 'available', but 'busy'. > PV-ops kernel simply mark it as 'reserved'. > > You can compare 'free' memory for -xen and pv-ops kernels - it same. But > for -xen kernel TotalMem higher and Used is higher too, and for pv-ops > TotalMem is lower, but used is lower too. > > Thanks George, I can understand that *some* memory area to be reserved but I dont understand why does it change with the "static-max" parameter of VM. Total memory inside the domU is inversely proportional to the difference of "static-max" and target memory. In case of ubuntu VM, if static-max=8GB and target=1GB then free -m would show something near 600-700MB Whereas, if static-max=2GB and target=1GB then free -m would show near 850MB and if static-max=target=1GB then free -m would show near 950MB. The difference in available domU memory is quite a big figure with more than 100MB difference. I'm not sure but its doubtful that xen would need such huge reserved area. ( for ballooning ? ) > > ______________________________**_________________ > Xen-users mailing list > Xen-users@lists.xen.org > http://lists.xen.org/xen-users > --00235446ff8002dbef04d4ed30a9 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable

On Tue, Feb 5, 2013 at 2:05 AM, George S= huklin <george.shuklin@gmail.com> wrote:
On 04.02.2013 22:59, Rushikesh Jadh= av wrote:
Hi Everyone,

I'm not sure if I'm the only one facing it or is it a known issue.<= br> CentOS6 and Ubuntu12.04 domU report less memory than they actually have.
Example, a CentOS6 VM with 512MB shows only 484 as total in free -m.
A Ubuntu domU shows 284M as total if the static max is 8GB and target memor= y is 512MB.

Both domUs are 64bit.

CentOS5 reports the exact same memory as its target.
I would be thankful if someone can share a reason or their domU # free -m

User-friendly answer: linux specific. Not XCP issue.

Technical stuff: pv-ops version of linux kernel marks some used areas as re= served (you can see this in dmesg output in Memory: line). AFAIK (I'm n= ot sure) -xen version of linux mark those areas as 'available', but= 'busy'. PV-ops kernel simply mark it as 'reserved'.

You can compare 'free' memory for -xen and pv-ops kernels - it same= . But for -xen kernel TotalMem higher and Used is higher too, =A0and for pv= -ops TotalMem is lower, but used is lower too.


Thanks George,

I can understand that *some= * memory area to be reserved but I dont understand why does it change with = the "static-max" parameter of VM.
Total memory inside the domU= is inversely proportional to the difference of "static-max" and = target memory.

In case of ubuntu VM, if static-max=3D8GB and target=3D1GB then free -m= would show something near 600-700MB
Whereas, if static-max=3D2GB and ta= rget=3D1GB then free -m would show near 850MB and if static-max=3Dtarget=3D= 1GB then free -m would show near 950MB.

The difference in available domU memory is quite a big figure with more= than 100MB difference. I'm not sure but its doubtful that xen would ne= ed such huge reserved area. ( for ballooning ? )



=A0

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

--00235446ff8002dbef04d4ed30a9-- --===============8282137575582025889== 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 --===============8282137575582025889==-- From xen-users-bounces@lists.xen.org Mon Feb 04 22:21:30 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 04 Feb 2013 22:21: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 1U2UOY-0008Pf-Pe; Mon, 04 Feb 2013 22:20:10 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U2UOX-0008PX-4N for xen-users@lists.xen.org; Mon, 04 Feb 2013 22:20:09 +0000 Received: from [85.158.139.83:9686] by server-4.bemta-5.messagelabs.com id F6/C0-29496-81430115; Mon, 04 Feb 2013 22:20:08 +0000 X-Env-Sender: george.shuklin@gmail.com X-Msg-Ref: server-6.tower-182.messagelabs.com!1360016406!23812625!1 X-Originating-IP: [209.85.217.172] X-SpamReason: No, hits=0.6 required=7.0 tests=HTML_40_50,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 3877 invoked from network); 4 Feb 2013 22:20:06 -0000 Received: from mail-lb0-f172.google.com (HELO mail-lb0-f172.google.com) (209.85.217.172) by server-6.tower-182.messagelabs.com with RC4-SHA encrypted SMTP; 4 Feb 2013 22:20:06 -0000 Received: by mail-lb0-f172.google.com with SMTP id n8so7127797lbj.17 for ; Mon, 04 Feb 2013 14:20:06 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type; bh=cpbH4zkaMCED4RrJ+FO0l1lGFjcfO+VyxCD+l0hXzes=; b=RTmraurIontfp85LF8b0Vl9N1EUQfJLZSuv+K9Q7ccK9vLTpKwOI9tBNHs0lZZpgl2 N3XcYJ3A2LHkTZxIMs1zIKnTjh92borQXLNsdBKaDXNlzg7iVhTPJPM7QVms9/3CQ1c0 +nIL3XxRtStO6ELFyN9JHD7t30YCbNXhE6jvXIx5X/S7YZmjQpdA8/gDm6t8kAbKT1Tj SVCt/+AwaYXL0cJhQ++Zb6v0O+0VTUw+i654vB6rvNYHhP9DgdRugwjt25DBcEe0Cr3Z eD/iZz/nnoI28mJrTvAEtvw9SbSxwiO7Zym/8b27JnhBEVOvRDAkg8qLb13EmFI1v4kQ W9mw== X-Received: by 10.112.98.105 with SMTP id eh9mr8848740lbb.131.1360016406133; Mon, 04 Feb 2013 14:20:06 -0800 (PST) Received: from home.desunote.ru ([2a00:11d8:1201:0:962b:18:e716:fb97]) by mx.google.com with ESMTPS id pz15sm9777839lab.3.2013.02.04.14.20.05 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 04 Feb 2013 14:20:05 -0800 (PST) Message-ID: <51103414.5020708@gmail.com> Date: Tue, 05 Feb 2013 02:20:04 +0400 From: George Shuklin User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:10.0.12) Gecko/20130116 Icedove/10.0.12 MIME-Version: 1.0 To: Rushikesh Jadhav <2rushikeshj@gmail.com> References: <51101B8E.4050206@gmail.com> In-Reply-To: Cc: xen-users@lists.xen.org Subject: Re: [Xen-users] CentOS6 & Ubuntu12 PV domU 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: multipart/mixed; boundary="===============0192062585185375506==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org This is a multi-part message in MIME format. --===============0192062585185375506== Content-Type: multipart/alternative; boundary="------------010807040504000609030408" This is a multi-part message in MIME format. --------------010807040504000609030408 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit On 05.02.2013 01:58, Rushikesh Jadhav wrote: > > > On Tue, Feb 5, 2013 at 2:05 AM, George Shuklin > > wrote: > > On 04.02.2013 22:59, Rushikesh Jadhav wrote: > > Hi Everyone, > > I'm not sure if I'm the only one facing it or is it a known issue. > CentOS6 and Ubuntu12.04 domU report less memory than they > actually have. > > Example, a CentOS6 VM with 512MB shows only 484 as total in > free -m. > A Ubuntu domU shows 284M as total if the static max is 8GB and > target memory is 512MB. > > Both domUs are 64bit. > > CentOS5 reports the exact same memory as its target. > I would be thankful if someone can share a reason or their > domU # free -m > > > User-friendly answer: linux specific. Not XCP issue. > > Technical stuff: pv-ops version of linux kernel marks some used > areas as reserved (you can see this in dmesg output in Memory: > line). AFAIK (I'm not sure) -xen version of linux mark those areas > as 'available', but 'busy'. PV-ops kernel simply mark it as > 'reserved'. > > You can compare 'free' memory for -xen and pv-ops kernels - it > same. But for -xen kernel TotalMem higher and Used is higher too, > and for pv-ops TotalMem is lower, but used is lower too. > > > Thanks George, > > I can understand that *some* memory area to be reserved but I dont > understand why does it change with the "static-max" parameter of VM. > Total memory inside the domU is inversely proportional to the > difference of "static-max" and target memory. > > In case of ubuntu VM, if static-max=8GB and target=1GB then free -m > would show something near 600-700MB > Whereas, if static-max=2GB and target=1GB then free -m would show near > 850MB and if static-max=target=1GB then free -m would show near 950MB. > > The difference in available domU memory is quite a big figure with > more than 100MB difference. I'm not sure but its doubtful that xen > would need such huge reserved area. ( for ballooning ? ) > > When you start domain it reserve memory to page tables and other stuff according to static-max. When you going below static max, it actually the xen-balloon gives back to xen some of pages from domU. But all internal data structures in kernel are designed to sustain up to static-max value. But yes, it is very huge amount at my opinion (I expect less). I still in debug reseach, but anyway, this is not xapi/xcp issue, this is pure linux stuff. --------------010807040504000609030408 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 8bit

On 05.02.2013 01:58, Rushikesh Jadhav wrote:


On Tue, Feb 5, 2013 at 2:05 AM, George Shuklin <george.shuklin@gmail.com> wrote:
On 04.02.2013 22:59, Rushikesh Jadhav wrote:
Hi Everyone,

I'm not sure if I'm the only one facing it or is it a known issue.
CentOS6 and Ubuntu12.04 domU report less memory than they actually have.

Example, a CentOS6 VM with 512MB shows only 484 as total in free -m.
A Ubuntu domU shows 284M as total if the static max is 8GB and target memory is 512MB.

Both domUs are 64bit.

CentOS5 reports the exact same memory as its target.
I would be thankful if someone can share a reason or their domU # free -m


User-friendly answer: linux specific. Not XCP issue.

Technical stuff: pv-ops version of linux kernel marks some used areas as reserved (you can see this in dmesg output in Memory: line). AFAIK (I'm not sure) -xen version of linux mark those areas as 'available', but 'busy'. PV-ops kernel simply mark it as 'reserved'.

You can compare 'free' memory for -xen and pv-ops kernels - it same. But for -xen kernel TotalMem higher and Used is higher too,  and for pv-ops TotalMem is lower, but used is lower too.


Thanks George,

I can understand that *some* memory area to be reserved but I dont understand why does it change with the "static-max" parameter of VM.
Total memory inside the domU is inversely proportional to the difference of "static-max" and target memory.

In case of ubuntu VM, if static-max=8GB and target=1GB then free -m would show something near 600-700MB
Whereas, if static-max=2GB and target=1GB then free -m would show near 850MB and if static-max=target=1GB then free -m would show near 950MB.

The difference in available domU memory is quite a big figure with more than 100MB difference. I'm not sure but its doubtful that xen would need such huge reserved area. ( for ballooning ? )



When you start domain it reserve memory to page tables and other stuff according to static-max. When you going below static max, it actually the xen-balloon gives back to xen some of pages from domU. But all internal data structures in kernel are designed to sustain up to static-max value.

But yes, it is very huge amount at my opinion (I expect less). I still in debug reseach, but anyway, this is not xapi/xcp issue, this is pure linux stuff. --------------010807040504000609030408-- --===============0192062585185375506== 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 --===============0192062585185375506==-- From xen-users-bounces@lists.xen.org Mon Feb 04 22:21:30 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 04 Feb 2013 22:21: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 1U2UOY-0008Pf-Pe; Mon, 04 Feb 2013 22:20:10 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U2UOX-0008PX-4N for xen-users@lists.xen.org; Mon, 04 Feb 2013 22:20:09 +0000 Received: from [85.158.139.83:9686] by server-4.bemta-5.messagelabs.com id F6/C0-29496-81430115; Mon, 04 Feb 2013 22:20:08 +0000 X-Env-Sender: george.shuklin@gmail.com X-Msg-Ref: server-6.tower-182.messagelabs.com!1360016406!23812625!1 X-Originating-IP: [209.85.217.172] X-SpamReason: No, hits=0.6 required=7.0 tests=HTML_40_50,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 3877 invoked from network); 4 Feb 2013 22:20:06 -0000 Received: from mail-lb0-f172.google.com (HELO mail-lb0-f172.google.com) (209.85.217.172) by server-6.tower-182.messagelabs.com with RC4-SHA encrypted SMTP; 4 Feb 2013 22:20:06 -0000 Received: by mail-lb0-f172.google.com with SMTP id n8so7127797lbj.17 for ; Mon, 04 Feb 2013 14:20:06 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type; bh=cpbH4zkaMCED4RrJ+FO0l1lGFjcfO+VyxCD+l0hXzes=; b=RTmraurIontfp85LF8b0Vl9N1EUQfJLZSuv+K9Q7ccK9vLTpKwOI9tBNHs0lZZpgl2 N3XcYJ3A2LHkTZxIMs1zIKnTjh92borQXLNsdBKaDXNlzg7iVhTPJPM7QVms9/3CQ1c0 +nIL3XxRtStO6ELFyN9JHD7t30YCbNXhE6jvXIx5X/S7YZmjQpdA8/gDm6t8kAbKT1Tj SVCt/+AwaYXL0cJhQ++Zb6v0O+0VTUw+i654vB6rvNYHhP9DgdRugwjt25DBcEe0Cr3Z eD/iZz/nnoI28mJrTvAEtvw9SbSxwiO7Zym/8b27JnhBEVOvRDAkg8qLb13EmFI1v4kQ W9mw== X-Received: by 10.112.98.105 with SMTP id eh9mr8848740lbb.131.1360016406133; Mon, 04 Feb 2013 14:20:06 -0800 (PST) Received: from home.desunote.ru ([2a00:11d8:1201:0:962b:18:e716:fb97]) by mx.google.com with ESMTPS id pz15sm9777839lab.3.2013.02.04.14.20.05 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 04 Feb 2013 14:20:05 -0800 (PST) Message-ID: <51103414.5020708@gmail.com> Date: Tue, 05 Feb 2013 02:20:04 +0400 From: George Shuklin User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:10.0.12) Gecko/20130116 Icedove/10.0.12 MIME-Version: 1.0 To: Rushikesh Jadhav <2rushikeshj@gmail.com> References: <51101B8E.4050206@gmail.com> In-Reply-To: Cc: xen-users@lists.xen.org Subject: Re: [Xen-users] CentOS6 & Ubuntu12 PV domU 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: multipart/mixed; boundary="===============0192062585185375506==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org This is a multi-part message in MIME format. --===============0192062585185375506== Content-Type: multipart/alternative; boundary="------------010807040504000609030408" This is a multi-part message in MIME format. --------------010807040504000609030408 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit On 05.02.2013 01:58, Rushikesh Jadhav wrote: > > > On Tue, Feb 5, 2013 at 2:05 AM, George Shuklin > > wrote: > > On 04.02.2013 22:59, Rushikesh Jadhav wrote: > > Hi Everyone, > > I'm not sure if I'm the only one facing it or is it a known issue. > CentOS6 and Ubuntu12.04 domU report less memory than they > actually have. > > Example, a CentOS6 VM with 512MB shows only 484 as total in > free -m. > A Ubuntu domU shows 284M as total if the static max is 8GB and > target memory is 512MB. > > Both domUs are 64bit. > > CentOS5 reports the exact same memory as its target. > I would be thankful if someone can share a reason or their > domU # free -m > > > User-friendly answer: linux specific. Not XCP issue. > > Technical stuff: pv-ops version of linux kernel marks some used > areas as reserved (you can see this in dmesg output in Memory: > line). AFAIK (I'm not sure) -xen version of linux mark those areas > as 'available', but 'busy'. PV-ops kernel simply mark it as > 'reserved'. > > You can compare 'free' memory for -xen and pv-ops kernels - it > same. But for -xen kernel TotalMem higher and Used is higher too, > and for pv-ops TotalMem is lower, but used is lower too. > > > Thanks George, > > I can understand that *some* memory area to be reserved but I dont > understand why does it change with the "static-max" parameter of VM. > Total memory inside the domU is inversely proportional to the > difference of "static-max" and target memory. > > In case of ubuntu VM, if static-max=8GB and target=1GB then free -m > would show something near 600-700MB > Whereas, if static-max=2GB and target=1GB then free -m would show near > 850MB and if static-max=target=1GB then free -m would show near 950MB. > > The difference in available domU memory is quite a big figure with > more than 100MB difference. I'm not sure but its doubtful that xen > would need such huge reserved area. ( for ballooning ? ) > > When you start domain it reserve memory to page tables and other stuff according to static-max. When you going below static max, it actually the xen-balloon gives back to xen some of pages from domU. But all internal data structures in kernel are designed to sustain up to static-max value. But yes, it is very huge amount at my opinion (I expect less). I still in debug reseach, but anyway, this is not xapi/xcp issue, this is pure linux stuff. --------------010807040504000609030408 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 8bit

On 05.02.2013 01:58, Rushikesh Jadhav wrote:


On Tue, Feb 5, 2013 at 2:05 AM, George Shuklin <george.shuklin@gmail.com> wrote:
On 04.02.2013 22:59, Rushikesh Jadhav wrote:
Hi Everyone,

I'm not sure if I'm the only one facing it or is it a known issue.
CentOS6 and Ubuntu12.04 domU report less memory than they actually have.

Example, a CentOS6 VM with 512MB shows only 484 as total in free -m.
A Ubuntu domU shows 284M as total if the static max is 8GB and target memory is 512MB.

Both domUs are 64bit.

CentOS5 reports the exact same memory as its target.
I would be thankful if someone can share a reason or their domU # free -m


User-friendly answer: linux specific. Not XCP issue.

Technical stuff: pv-ops version of linux kernel marks some used areas as reserved (you can see this in dmesg output in Memory: line). AFAIK (I'm not sure) -xen version of linux mark those areas as 'available', but 'busy'. PV-ops kernel simply mark it as 'reserved'.

You can compare 'free' memory for -xen and pv-ops kernels - it same. But for -xen kernel TotalMem higher and Used is higher too,  and for pv-ops TotalMem is lower, but used is lower too.


Thanks George,

I can understand that *some* memory area to be reserved but I dont understand why does it change with the "static-max" parameter of VM.
Total memory inside the domU is inversely proportional to the difference of "static-max" and target memory.

In case of ubuntu VM, if static-max=8GB and target=1GB then free -m would show something near 600-700MB
Whereas, if static-max=2GB and target=1GB then free -m would show near 850MB and if static-max=target=1GB then free -m would show near 950MB.

The difference in available domU memory is quite a big figure with more than 100MB difference. I'm not sure but its doubtful that xen would need such huge reserved area. ( for ballooning ? )



When you start domain it reserve memory to page tables and other stuff according to static-max. When you going below static max, it actually the xen-balloon gives back to xen some of pages from domU. But all internal data structures in kernel are designed to sustain up to static-max value.

But yes, it is very huge amount at my opinion (I expect less). I still in debug reseach, but anyway, this is not xapi/xcp issue, this is pure linux stuff. --------------010807040504000609030408-- --===============0192062585185375506== 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 --===============0192062585185375506==-- From xen-users-bounces@lists.xen.org Tue Feb 05 01:39:36 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 05 Feb 2013 01:39: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 1U2XTi-0006A8-01; Tue, 05 Feb 2013 01:37:42 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U2XTf-0006A3-Uk for xen-users@lists.xen.org; Tue, 05 Feb 2013 01:37:40 +0000 Received: from [85.158.137.99:16946] by server-1.bemta-3.messagelabs.com id 19/12-08955-E5260115; Tue, 05 Feb 2013 01:37:34 +0000 X-Env-Sender: smkent@smkent.net X-Msg-Ref: server-5.tower-217.messagelabs.com!1360028252!15266116!1 X-Originating-IP: [209.85.215.45] 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.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 14975 invoked from network); 5 Feb 2013 01:37:32 -0000 Received: from mail-la0-f45.google.com (HELO mail-la0-f45.google.com) (209.85.215.45) by server-5.tower-217.messagelabs.com with RC4-SHA encrypted SMTP; 5 Feb 2013 01:37:32 -0000 Received: by mail-la0-f45.google.com with SMTP id er20so5164273lab.4 for ; Mon, 04 Feb 2013 17:37:32 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-received:x-originating-ip:in-reply-to:references :date:message-id:subject:from:to:cc:content-type:x-gm-message-state; bh=8O1YIbEPsTMoeaQ5IRsptnwYBtC+mg41k4jtsCQfV3k=; b=HgJWQMepkZAgfkTtFcfH5sCvR9aQnhCAW1N9JPqcWK823eiW8I/NRAY8TIrrV7HtGI OE6qhQTKCOy15OGKl47KwtW5l8Dlds8e1d4/IcDHV+buJwY0bu7CEAINfssud8A3nxvf KCNnhImEeMDrMmjSVp+1VLataD0sS4aow/Gf44j12AJ3GwDM0V1fhGF+Q60WBAGW1giQ C7QSBpBB1+vGZrN05njOzG5uahTycjxS4N+8LJe2ueb4xxZC/12tZRGePez350vQO/Vn EmhPf2QmymEzkLCrxF0J1hWObkHdR2J8RGmhS1zV4Kji/MfUD4xVS9Wv+8kGlc68/8ET AGSQ== MIME-Version: 1.0 X-Received: by 10.152.127.202 with SMTP id ni10mr21247088lab.6.1360028252088; Mon, 04 Feb 2013 17:37:32 -0800 (PST) Received: by 10.112.131.137 with HTTP; Mon, 4 Feb 2013 17:37:31 -0800 (PST) X-Originating-IP: [174.21.254.192] In-Reply-To: References: Date: Mon, 4 Feb 2013 17:37:31 -0800 Message-ID: From: Stephen Kent To: Rushikesh Jadhav <2rushikeshj@gmail.com> X-Gm-Message-State: ALoCoQmnxsvdw1GZkOpV3X8zWlUPxUpinL5jHWCfDAMBidmsOey6C0j7YZz3T5LgOZbrLPURV+Sw Cc: xen-users@lists.xen.org Subject: Re: [Xen-users] XENBUS: Timeout connecting to device: device/vbd/51712 (local state 3, remote state 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="===============3907768722369739029==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============3907768722369739029== Content-Type: multipart/alternative; boundary=f46d042c6aebd9a8a904d4f04021 --f46d042c6aebd9a8a904d4f04021 Content-Type: text/plain; charset=UTF-8 I checked, PCI is enabled in both my dom0 and domU kernels. I've enabled all the Xen drivers I can find (including the block device frontend and backend drivers). On Mon, Feb 4, 2013 at 11:45 AM, Rushikesh Jadhav <2rushikeshj@gmail.com>wrote: > On Tue, Feb 5, 2013 at 12:00 AM, Stephen Kent wrote: > >> I just upgraded my computer from an old kernel (2.6.34-xen) to 3.6.11, >> and upgraded Xen to 4.2.0. I can't seem to get my domU to boot, as it can't >> find the root filesystem. >> >> I've compiled a domU kernel (also 3.6.11) with xen-blkfront built-in and >> set the domU config file with this disk configuration: >> >> disk = [ 'file:/home/data/xen/megatron/root.img,xvda,w' ] >> >> (The disk is just a file with an ext3 filesystem, I can mount it on >> loopback in dom0) >> >> After I xl start my domU, xl block-list in dom0 shows the device >> connected to the domU but the domU kernel (with root=/dev/xvda) can't find >> the root filesystem: >> >> >> [...] >> XENBUS: Timeout connecting to device: device/vbd/51712 (local state 3, >> remote state 1) >> console [netcon0] enabled >> netconsole: network logging started >> ALSA device list: >> No soundcards found. >> md: Waiting for all devices to be available before autodetect >> md: If you don't use raid, use raid=noautodetect >> md: Autodetecting RAID arrays. >> md: Scanned 0 and added 0 devices. >> md: autorun ... >> md: ... autorun DONE. >> VFS: Cannot open root device "xvda" or unknown-block(0,0): error -6 >> Please append a correct "root=" boot option; here are the available >> partitions: >> Kernel panic - not syncing: VFS: Unable to mount root fs on >> unknown-block(0,0) >> Pid: 1, comm: swapper/0 Not tainted 3.6.11-gentoo #8 >> Call Trace: >> [] ? panic+0xc5/0x1cc >> [] ? printk+0x4c/0x51 >> [] ? mount_block_root+0x1d4/0x1f2 >> [] ? lg_local_lock+0x11/0x14 >> [] ? kvm_io_bus_sort_cmp+0x1c/0x27 >> [] ? sys_mknodat+0x12c/0x140 >> [] ? mount_root+0x124/0x12b >> [] ? initrd_load+0x303/0x309 >> [] ? prepare_namespace+0x168/0x19e >> [] ? kernel_init+0x17f/0x191 >> [] ? parse_early_options+0x2a/0x2a >> [] ? kernel_thread_helper+0x4/0x10 >> [] ? retint_restore_args+0x5/0x6 >> [] ? gs_change+0x13/0x13 >> >> > Check if you have PCI enabled in domU kernel. > Select the PCI options while you do # make menuconfig > > > >> >> I don't see any earlier kernel messages about the Xen block frontend >> driver loading. Am I missing a kernel option or something? I'm not sure >> what else to try. >> >> Thanks! >> >> _______________________________________________ >> Xen-users mailing list >> Xen-users@lists.xen.org >> http://lists.xen.org/xen-users >> > > --f46d042c6aebd9a8a904d4f04021 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable I checked, PCI is enabled in both my dom0 and domU kernels. I've enable= d all the Xen drivers I can find (including the block device frontend and b= ackend drivers).


On Mon, Feb 4, 2013= at 11:45 AM, Rushikesh Jadhav <2rushikeshj@gmail.com> w= rote:
On Tue, Feb 5, 2013 at 12:00 AM, Stephen Kent <= ;smkent@smkent.net> wrote:
I just upgraded my computer from an old kernel (2.6.34-xen) to 3.6.11,= and upgraded Xen to 4.2.0. I can't seem to get my domU to boot, as it = can't find the root filesystem.

I've compi= led a domU kernel (also 3.6.11) with xen-blkfront built-in and set the domU= config file with this disk configuration:

disk =3D [ 'file:/home/data/xen/megatron/root.img,x= vda,w' ]

(The disk is just a file with an ext3= filesystem, I can mount it on loopback in dom0)

After I xl start my domU, xl block-list in dom0 shows the device connected = to the domU but the domU kernel (with root=3D/dev/xvda) can't find the = root filesystem:


[...]
XENBUS: Timeout connecting to device: device/vbd/51712 (local state 3, remo= te state 1)
console [netcon0] enabled
netconsole: netwo= rk logging started
ALSA device list:
=C2=A0 No soundcar= ds found.
md: Waiting for all devices to be available before autodetect
md: If you don't use raid, use raid=3Dnoautodetect
md: autorun ...
md: ... autorun DONE.
VFS: Cannot = open root device "xvda" or unknown-block(0,0): error -6
Please append a correct "root=3D" boot option; here are the avai= lable partitions:
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-bl= ock(0,0)
Pid: 1, comm: swapper/0 Not tainted 3.6.11-gentoo #8
Call Trace:
=C2=A0[<ffffffff815c59ff>] ? panic+0xc5/= 0x1cc
=C2=A0[<ffffffff815c5bd9>] ? printk+0x4c/0x51
=C2=A0[&= lt;ffffffff819990cd>] ? mount_block_root+0x1d4/0x1f2
=C2=A0[&l= t;ffffffff8108ebaa>] ? lg_local_lock+0x11/0x14
=C2=A0[<ffff= ffff81002930>] ? kvm_io_bus_sort_cmp+0x1c/0x27
=C2=A0[<ffffffff8110fcf8>] ? sys_mknodat+0x12c/0x140
= =C2=A0[<ffffffff8199920f>] ? mount_root+0x124/0x12b
=C2=A0[= <ffffffff81999d8f>] ? initrd_load+0x303/0x309
=C2=A0[<ff= ffffff8199937e>] ? prepare_namespace+0x168/0x19e
=C2=A0[<ffffffff81998702>] ? kernel_init+0x17f/0x191
= =C2=A0[<ffffffff8199852b>] ? parse_early_options+0x2a/0x2a
= =C2=A0[<ffffffff815cf644>] ? kernel_thread_helper+0x4/0x10
= =C2=A0[<ffffffff815c8338>] ? retint_restore_args+0x5/0x6
=C2=A0[<ffffffff815cf640>] ? gs_change+0x13/0x13

<= /div>

I don't see any earlier kernel messages = about the Xen block frontend driver loading. Am I missing a kernel option o= r something? I'm not sure what else to try.

Thanks!

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


--f46d042c6aebd9a8a904d4f04021-- --===============3907768722369739029== 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 --===============3907768722369739029==-- From xen-users-bounces@lists.xen.org Tue Feb 05 01:39:36 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 05 Feb 2013 01:39: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 1U2XTi-0006A8-01; Tue, 05 Feb 2013 01:37:42 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U2XTf-0006A3-Uk for xen-users@lists.xen.org; Tue, 05 Feb 2013 01:37:40 +0000 Received: from [85.158.137.99:16946] by server-1.bemta-3.messagelabs.com id 19/12-08955-E5260115; Tue, 05 Feb 2013 01:37:34 +0000 X-Env-Sender: smkent@smkent.net X-Msg-Ref: server-5.tower-217.messagelabs.com!1360028252!15266116!1 X-Originating-IP: [209.85.215.45] 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.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 14975 invoked from network); 5 Feb 2013 01:37:32 -0000 Received: from mail-la0-f45.google.com (HELO mail-la0-f45.google.com) (209.85.215.45) by server-5.tower-217.messagelabs.com with RC4-SHA encrypted SMTP; 5 Feb 2013 01:37:32 -0000 Received: by mail-la0-f45.google.com with SMTP id er20so5164273lab.4 for ; Mon, 04 Feb 2013 17:37:32 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-received:x-originating-ip:in-reply-to:references :date:message-id:subject:from:to:cc:content-type:x-gm-message-state; bh=8O1YIbEPsTMoeaQ5IRsptnwYBtC+mg41k4jtsCQfV3k=; b=HgJWQMepkZAgfkTtFcfH5sCvR9aQnhCAW1N9JPqcWK823eiW8I/NRAY8TIrrV7HtGI OE6qhQTKCOy15OGKl47KwtW5l8Dlds8e1d4/IcDHV+buJwY0bu7CEAINfssud8A3nxvf KCNnhImEeMDrMmjSVp+1VLataD0sS4aow/Gf44j12AJ3GwDM0V1fhGF+Q60WBAGW1giQ C7QSBpBB1+vGZrN05njOzG5uahTycjxS4N+8LJe2ueb4xxZC/12tZRGePez350vQO/Vn EmhPf2QmymEzkLCrxF0J1hWObkHdR2J8RGmhS1zV4Kji/MfUD4xVS9Wv+8kGlc68/8ET AGSQ== MIME-Version: 1.0 X-Received: by 10.152.127.202 with SMTP id ni10mr21247088lab.6.1360028252088; Mon, 04 Feb 2013 17:37:32 -0800 (PST) Received: by 10.112.131.137 with HTTP; Mon, 4 Feb 2013 17:37:31 -0800 (PST) X-Originating-IP: [174.21.254.192] In-Reply-To: References: Date: Mon, 4 Feb 2013 17:37:31 -0800 Message-ID: From: Stephen Kent To: Rushikesh Jadhav <2rushikeshj@gmail.com> X-Gm-Message-State: ALoCoQmnxsvdw1GZkOpV3X8zWlUPxUpinL5jHWCfDAMBidmsOey6C0j7YZz3T5LgOZbrLPURV+Sw Cc: xen-users@lists.xen.org Subject: Re: [Xen-users] XENBUS: Timeout connecting to device: device/vbd/51712 (local state 3, remote state 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="===============3907768722369739029==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============3907768722369739029== Content-Type: multipart/alternative; boundary=f46d042c6aebd9a8a904d4f04021 --f46d042c6aebd9a8a904d4f04021 Content-Type: text/plain; charset=UTF-8 I checked, PCI is enabled in both my dom0 and domU kernels. I've enabled all the Xen drivers I can find (including the block device frontend and backend drivers). On Mon, Feb 4, 2013 at 11:45 AM, Rushikesh Jadhav <2rushikeshj@gmail.com>wrote: > On Tue, Feb 5, 2013 at 12:00 AM, Stephen Kent wrote: > >> I just upgraded my computer from an old kernel (2.6.34-xen) to 3.6.11, >> and upgraded Xen to 4.2.0. I can't seem to get my domU to boot, as it can't >> find the root filesystem. >> >> I've compiled a domU kernel (also 3.6.11) with xen-blkfront built-in and >> set the domU config file with this disk configuration: >> >> disk = [ 'file:/home/data/xen/megatron/root.img,xvda,w' ] >> >> (The disk is just a file with an ext3 filesystem, I can mount it on >> loopback in dom0) >> >> After I xl start my domU, xl block-list in dom0 shows the device >> connected to the domU but the domU kernel (with root=/dev/xvda) can't find >> the root filesystem: >> >> >> [...] >> XENBUS: Timeout connecting to device: device/vbd/51712 (local state 3, >> remote state 1) >> console [netcon0] enabled >> netconsole: network logging started >> ALSA device list: >> No soundcards found. >> md: Waiting for all devices to be available before autodetect >> md: If you don't use raid, use raid=noautodetect >> md: Autodetecting RAID arrays. >> md: Scanned 0 and added 0 devices. >> md: autorun ... >> md: ... autorun DONE. >> VFS: Cannot open root device "xvda" or unknown-block(0,0): error -6 >> Please append a correct "root=" boot option; here are the available >> partitions: >> Kernel panic - not syncing: VFS: Unable to mount root fs on >> unknown-block(0,0) >> Pid: 1, comm: swapper/0 Not tainted 3.6.11-gentoo #8 >> Call Trace: >> [] ? panic+0xc5/0x1cc >> [] ? printk+0x4c/0x51 >> [] ? mount_block_root+0x1d4/0x1f2 >> [] ? lg_local_lock+0x11/0x14 >> [] ? kvm_io_bus_sort_cmp+0x1c/0x27 >> [] ? sys_mknodat+0x12c/0x140 >> [] ? mount_root+0x124/0x12b >> [] ? initrd_load+0x303/0x309 >> [] ? prepare_namespace+0x168/0x19e >> [] ? kernel_init+0x17f/0x191 >> [] ? parse_early_options+0x2a/0x2a >> [] ? kernel_thread_helper+0x4/0x10 >> [] ? retint_restore_args+0x5/0x6 >> [] ? gs_change+0x13/0x13 >> >> > Check if you have PCI enabled in domU kernel. > Select the PCI options while you do # make menuconfig > > > >> >> I don't see any earlier kernel messages about the Xen block frontend >> driver loading. Am I missing a kernel option or something? I'm not sure >> what else to try. >> >> Thanks! >> >> _______________________________________________ >> Xen-users mailing list >> Xen-users@lists.xen.org >> http://lists.xen.org/xen-users >> > > --f46d042c6aebd9a8a904d4f04021 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable I checked, PCI is enabled in both my dom0 and domU kernels. I've enable= d all the Xen drivers I can find (including the block device frontend and b= ackend drivers).


On Mon, Feb 4, 2013= at 11:45 AM, Rushikesh Jadhav <2rushikeshj@gmail.com> w= rote:
On Tue, Feb 5, 2013 at 12:00 AM, Stephen Kent <= ;smkent@smkent.net> wrote:
I just upgraded my computer from an old kernel (2.6.34-xen) to 3.6.11,= and upgraded Xen to 4.2.0. I can't seem to get my domU to boot, as it = can't find the root filesystem.

I've compi= led a domU kernel (also 3.6.11) with xen-blkfront built-in and set the domU= config file with this disk configuration:

disk =3D [ 'file:/home/data/xen/megatron/root.img,x= vda,w' ]

(The disk is just a file with an ext3= filesystem, I can mount it on loopback in dom0)

After I xl start my domU, xl block-list in dom0 shows the device connected = to the domU but the domU kernel (with root=3D/dev/xvda) can't find the = root filesystem:


[...]
XENBUS: Timeout connecting to device: device/vbd/51712 (local state 3, remo= te state 1)
console [netcon0] enabled
netconsole: netwo= rk logging started
ALSA device list:
=C2=A0 No soundcar= ds found.
md: Waiting for all devices to be available before autodetect
md: If you don't use raid, use raid=3Dnoautodetect
md: autorun ...
md: ... autorun DONE.
VFS: Cannot = open root device "xvda" or unknown-block(0,0): error -6
Please append a correct "root=3D" boot option; here are the avai= lable partitions:
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-bl= ock(0,0)
Pid: 1, comm: swapper/0 Not tainted 3.6.11-gentoo #8
Call Trace:
=C2=A0[<ffffffff815c59ff>] ? panic+0xc5/= 0x1cc
=C2=A0[<ffffffff815c5bd9>] ? printk+0x4c/0x51
=C2=A0[&= lt;ffffffff819990cd>] ? mount_block_root+0x1d4/0x1f2
=C2=A0[&l= t;ffffffff8108ebaa>] ? lg_local_lock+0x11/0x14
=C2=A0[<ffff= ffff81002930>] ? kvm_io_bus_sort_cmp+0x1c/0x27
=C2=A0[<ffffffff8110fcf8>] ? sys_mknodat+0x12c/0x140
= =C2=A0[<ffffffff8199920f>] ? mount_root+0x124/0x12b
=C2=A0[= <ffffffff81999d8f>] ? initrd_load+0x303/0x309
=C2=A0[<ff= ffffff8199937e>] ? prepare_namespace+0x168/0x19e
=C2=A0[<ffffffff81998702>] ? kernel_init+0x17f/0x191
= =C2=A0[<ffffffff8199852b>] ? parse_early_options+0x2a/0x2a
= =C2=A0[<ffffffff815cf644>] ? kernel_thread_helper+0x4/0x10
= =C2=A0[<ffffffff815c8338>] ? retint_restore_args+0x5/0x6
=C2=A0[<ffffffff815cf640>] ? gs_change+0x13/0x13

<= /div>

I don't see any earlier kernel messages = about the Xen block frontend driver loading. Am I missing a kernel option o= r something? I'm not sure what else to try.

Thanks!

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


--f46d042c6aebd9a8a904d4f04021-- --===============3907768722369739029== 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 --===============3907768722369739029==-- From xen-users-bounces@lists.xen.org Tue Feb 05 03:37:04 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 05 Feb 2013 03:37: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 1U2ZJK-0007mJ-U7; Tue, 05 Feb 2013 03:35:06 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U2ZJJ-0007mE-AC for xen-users@lists.xen.org; Tue, 05 Feb 2013 03:35:05 +0000 Received: from [85.158.143.35:36379] by server-1.bemta-4.messagelabs.com id 50/98-08839-FDD70115; Tue, 05 Feb 2013 03:34:55 +0000 X-Env-Sender: smkent@smkent.net X-Msg-Ref: server-4.tower-21.messagelabs.com!1360035293!5382075!1 X-Originating-IP: [209.85.217.171] 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.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 23059 invoked from network); 5 Feb 2013 03:34:53 -0000 Received: from mail-lb0-f171.google.com (HELO mail-lb0-f171.google.com) (209.85.217.171) by server-4.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 5 Feb 2013 03:34:53 -0000 Received: by mail-lb0-f171.google.com with SMTP id gg13so7144895lbb.2 for ; Mon, 04 Feb 2013 19:34:53 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-received:x-originating-ip:in-reply-to:references :date:message-id:subject:from:to:cc:content-type:x-gm-message-state; bh=HbJMV1ujtSHLuHW/cS7ZXuxMABZvnRGpgtKa02MhEeU=; b=ZUXkgI8epvg+4OgfFeuL5LJ+iMLbVbeay60/NAyPVfHOtF/tkwB1mgrzW4aYMecQ5b 4gfHlGhMLCvz96RJuiGwL8b3jU34h5q087jw37BpChuQbwYHpdtCiu2KWcqawl/+qE8m DvYpyDzDBnSXgkHlKbZyr1qqPF1z9ntslXHi7BZAD4LTVL78JJOnBiaDAg1unnMS2Rbe uNxTrWpIxZmsMe+e6GXuvBIfdFJLWmOY2JySdAAMm50LCICGmiE7eyFfRTbL4sS+jQhQ 4SJ1dPYQOzOnYsdhleJQcJz6DnGbyj5hPj6OwoNdR8NXkISzZGl7xFSW7WP0Hv2t041w JlEA== MIME-Version: 1.0 X-Received: by 10.112.13.162 with SMTP id i2mr8833003lbc.76.1360035292931; Mon, 04 Feb 2013 19:34:52 -0800 (PST) Received: by 10.112.131.137 with HTTP; Mon, 4 Feb 2013 19:34:52 -0800 (PST) X-Originating-IP: [174.21.254.192] In-Reply-To: References: Date: Mon, 4 Feb 2013 19:34:52 -0800 Message-ID: From: Stephen Kent To: Rushikesh Jadhav <2rushikeshj@gmail.com> X-Gm-Message-State: ALoCoQloBph+8og8J5q0WQf7/VjqXZyDdERWhBQU7SuZrmGIfX+8hTnvFbJ3VV4eT/rrdqg6iNBD Cc: xen-users@lists.xen.org Subject: Re: [Xen-users] XENBUS: Timeout connecting to device: device/vbd/51712 (local state 3, remote state 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="===============4471116421802472934==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============4471116421802472934== Content-Type: multipart/alternative; boundary=f46d0401fa5d84682604d4f1e44b --f46d0401fa5d84682604d4f1e44b Content-Type: text/plain; charset=UTF-8 I can't seem to attach the block device in domain 0 either: # xl block-attach 0 file:/home/data/xen/megatron/root.img /dev/xvda libxl: error: libxl.c:1752:libxl__device_from_disk: Invalid or unsupported virtual disk identifier /dev/xvda libxl: error: libxl.c:1844:device_disk_add: Invalid or unsupported virtual disk identifier /dev/xvda libxl: error: libxl.c:1720:device_addrm_aocomplete: unable to add device libxl_device_disk_add failed. I still feel like I'm missing a kernel config option or something, but I have no idea where to look. The Xen block backend and frontend drivers are both included, seems strange that I would be missing support for a simple loopback file. On Mon, Feb 4, 2013 at 5:37 PM, Stephen Kent wrote: > I checked, PCI is enabled in both my dom0 and domU kernels. I've enabled > all the Xen drivers I can find (including the block device frontend and > backend drivers). > > > On Mon, Feb 4, 2013 at 11:45 AM, Rushikesh Jadhav <2rushikeshj@gmail.com>wrote: > >> On Tue, Feb 5, 2013 at 12:00 AM, Stephen Kent wrote: >> >>> I just upgraded my computer from an old kernel (2.6.34-xen) to 3.6.11, >>> and upgraded Xen to 4.2.0. I can't seem to get my domU to boot, as it can't >>> find the root filesystem. >>> >>> I've compiled a domU kernel (also 3.6.11) with xen-blkfront built-in and >>> set the domU config file with this disk configuration: >>> >>> disk = [ 'file:/home/data/xen/megatron/root.img,xvda,w' ] >>> >>> (The disk is just a file with an ext3 filesystem, I can mount it on >>> loopback in dom0) >>> >>> After I xl start my domU, xl block-list in dom0 shows the device >>> connected to the domU but the domU kernel (with root=/dev/xvda) can't find >>> the root filesystem: >>> >>> >>> [...] >>> XENBUS: Timeout connecting to device: device/vbd/51712 (local state 3, >>> remote state 1) >>> console [netcon0] enabled >>> netconsole: network logging started >>> ALSA device list: >>> No soundcards found. >>> md: Waiting for all devices to be available before autodetect >>> md: If you don't use raid, use raid=noautodetect >>> md: Autodetecting RAID arrays. >>> md: Scanned 0 and added 0 devices. >>> md: autorun ... >>> md: ... autorun DONE. >>> VFS: Cannot open root device "xvda" or unknown-block(0,0): error -6 >>> Please append a correct "root=" boot option; here are the available >>> partitions: >>> Kernel panic - not syncing: VFS: Unable to mount root fs on >>> unknown-block(0,0) >>> Pid: 1, comm: swapper/0 Not tainted 3.6.11-gentoo #8 >>> Call Trace: >>> [] ? panic+0xc5/0x1cc >>> [] ? printk+0x4c/0x51 >>> [] ? mount_block_root+0x1d4/0x1f2 >>> [] ? lg_local_lock+0x11/0x14 >>> [] ? kvm_io_bus_sort_cmp+0x1c/0x27 >>> [] ? sys_mknodat+0x12c/0x140 >>> [] ? mount_root+0x124/0x12b >>> [] ? initrd_load+0x303/0x309 >>> [] ? prepare_namespace+0x168/0x19e >>> [] ? kernel_init+0x17f/0x191 >>> [] ? parse_early_options+0x2a/0x2a >>> [] ? kernel_thread_helper+0x4/0x10 >>> [] ? retint_restore_args+0x5/0x6 >>> [] ? gs_change+0x13/0x13 >>> >>> >> Check if you have PCI enabled in domU kernel. >> Select the PCI options while you do # make menuconfig >> >> >> >>> >>> I don't see any earlier kernel messages about the Xen block frontend >>> driver loading. Am I missing a kernel option or something? I'm not sure >>> what else to try. >>> >>> Thanks! >>> >>> _______________________________________________ >>> Xen-users mailing list >>> Xen-users@lists.xen.org >>> http://lists.xen.org/xen-users >>> >> >> > --f46d0401fa5d84682604d4f1e44b Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable I can't seem to attach the block device in domain 0 either:

# xl block-attach 0 file:/home/data/xen/megatron/root.img /dev= /xvda
libxl: error: libxl.c:1752:libxl__device_from_disk: Invalid= or unsupported virtual disk identifier /dev/xvda
libxl: error: libxl.c:1844:device_disk_add: Invalid or unsupported vir= tual disk identifier /dev/xvda
libxl: error: libxl.c:1720:device_= addrm_aocomplete: unable to add device
libxl_device_disk_add fail= ed.

I still feel like I'm missing a kernel config optio= n or something, but I have no idea where to look. The Xen block backend and= frontend drivers are both included, seems strange that I would be missing = support for a simple loopback file.


On Mon, Feb 4, 2013 at 5:37 P= M, Stephen Kent <smkent@smkent.net> wrote:
I checked, PCI is enabled in both my dom0 and domU kernels. I've enable= d all the Xen drivers I can find (including the block device frontend and b= ackend drivers).


On Mon, Feb 4, 2013 at 11:45 AM, Rushikesh Jadhav <2rushikeshj@gmail.c= om> wrote:
On Tue,= Feb 5, 2013 at 12:00 AM, Stephen Kent <smkent@smkent.net> w= rote:
I just upgraded my computer from an old kernel (2.6.34-xen) to 3.6.11,= and upgraded Xen to 4.2.0. I can't seem to get my domU to boot, as it = can't find the root filesystem.

I've compi= led a domU kernel (also 3.6.11) with xen-blkfront built-in and set the domU= config file with this disk configuration:

disk =3D [ 'file:/home/data/xen/megatron/root.img,x= vda,w' ]

(The disk is just a file with an ext3= filesystem, I can mount it on loopback in dom0)

After I xl start my domU, xl block-list in dom0 shows the device connected = to the domU but the domU kernel (with root=3D/dev/xvda) can't find the = root filesystem:


[...]
XENBUS: Timeout connecting to device: device/vbd/51712 (local state 3, remo= te state 1)
console [netcon0] enabled
netconsole: netwo= rk logging started
ALSA device list:
=C2=A0 No soundcar= ds found.
md: Waiting for all devices to be available before autodetect
md: If you don't use raid, use raid=3Dnoautodetect
md: Auto= detecting RAID arrays.
md: Scanned 0 and added 0 devices.
md: autorun ...
md: ... autorun DONE.
VFS: Cannot = open root device "xvda" or unknown-block(0,0): error -6
Please append a correct "root=3D" boot option; here are the avai= lable partitions:
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-bl= ock(0,0)
Pid: 1, comm: swapper/0 Not tainted 3.6.11-gentoo #8
Call Trace:
=C2=A0[<ffffffff815c59ff>] ? panic+0xc5/= 0x1cc
=C2=A0[<ffffffff815c5bd9>] ? printk+0x4c/0x51
=C2=A0[&= lt;ffffffff819990cd>] ? mount_block_root+0x1d4/0x1f2
=C2=A0[&l= t;ffffffff8108ebaa>] ? lg_local_lock+0x11/0x14
=C2=A0[<ffff= ffff81002930>] ? kvm_io_bus_sort_cmp+0x1c/0x27
=C2=A0[<ffffffff8110fcf8>] ? sys_mknodat+0x12c/0x140
= =C2=A0[<ffffffff8199920f>] ? mount_root+0x124/0x12b
=C2=A0[= <ffffffff81999d8f>] ? initrd_load+0x303/0x309
=C2=A0[<ff= ffffff8199937e>] ? prepare_namespace+0x168/0x19e
=C2=A0[<ffffffff81998702>] ? kernel_init+0x17f/0x191
= =C2=A0[<ffffffff8199852b>] ? parse_early_options+0x2a/0x2a
= =C2=A0[<ffffffff815cf644>] ? kernel_thread_helper+0x4/0x10
= =C2=A0[<ffffffff815c8338>] ? retint_restore_args+0x5/0x6
=C2=A0[<ffffffff815cf640>] ? gs_change+0x13/0x13

<= /div>

Check if you have PCI enabled in dom= U kernel.
Select the PCI options while you do # make menuconfig

= =C2=A0

I don't see any earlier kernel messages = about the Xen block frontend driver loading. Am I missing a kernel option o= r something? I'm not sure what else to try.

Thanks!

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



--f46d0401fa5d84682604d4f1e44b-- --===============4471116421802472934== 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 --===============4471116421802472934==-- From xen-users-bounces@lists.xen.org Tue Feb 05 03:37:04 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 05 Feb 2013 03:37: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 1U2ZJK-0007mJ-U7; Tue, 05 Feb 2013 03:35:06 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U2ZJJ-0007mE-AC for xen-users@lists.xen.org; Tue, 05 Feb 2013 03:35:05 +0000 Received: from [85.158.143.35:36379] by server-1.bemta-4.messagelabs.com id 50/98-08839-FDD70115; Tue, 05 Feb 2013 03:34:55 +0000 X-Env-Sender: smkent@smkent.net X-Msg-Ref: server-4.tower-21.messagelabs.com!1360035293!5382075!1 X-Originating-IP: [209.85.217.171] 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.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 23059 invoked from network); 5 Feb 2013 03:34:53 -0000 Received: from mail-lb0-f171.google.com (HELO mail-lb0-f171.google.com) (209.85.217.171) by server-4.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 5 Feb 2013 03:34:53 -0000 Received: by mail-lb0-f171.google.com with SMTP id gg13so7144895lbb.2 for ; Mon, 04 Feb 2013 19:34:53 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-received:x-originating-ip:in-reply-to:references :date:message-id:subject:from:to:cc:content-type:x-gm-message-state; bh=HbJMV1ujtSHLuHW/cS7ZXuxMABZvnRGpgtKa02MhEeU=; b=ZUXkgI8epvg+4OgfFeuL5LJ+iMLbVbeay60/NAyPVfHOtF/tkwB1mgrzW4aYMecQ5b 4gfHlGhMLCvz96RJuiGwL8b3jU34h5q087jw37BpChuQbwYHpdtCiu2KWcqawl/+qE8m DvYpyDzDBnSXgkHlKbZyr1qqPF1z9ntslXHi7BZAD4LTVL78JJOnBiaDAg1unnMS2Rbe uNxTrWpIxZmsMe+e6GXuvBIfdFJLWmOY2JySdAAMm50LCICGmiE7eyFfRTbL4sS+jQhQ 4SJ1dPYQOzOnYsdhleJQcJz6DnGbyj5hPj6OwoNdR8NXkISzZGl7xFSW7WP0Hv2t041w JlEA== MIME-Version: 1.0 X-Received: by 10.112.13.162 with SMTP id i2mr8833003lbc.76.1360035292931; Mon, 04 Feb 2013 19:34:52 -0800 (PST) Received: by 10.112.131.137 with HTTP; Mon, 4 Feb 2013 19:34:52 -0800 (PST) X-Originating-IP: [174.21.254.192] In-Reply-To: References: Date: Mon, 4 Feb 2013 19:34:52 -0800 Message-ID: From: Stephen Kent To: Rushikesh Jadhav <2rushikeshj@gmail.com> X-Gm-Message-State: ALoCoQloBph+8og8J5q0WQf7/VjqXZyDdERWhBQU7SuZrmGIfX+8hTnvFbJ3VV4eT/rrdqg6iNBD Cc: xen-users@lists.xen.org Subject: Re: [Xen-users] XENBUS: Timeout connecting to device: device/vbd/51712 (local state 3, remote state 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="===============4471116421802472934==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============4471116421802472934== Content-Type: multipart/alternative; boundary=f46d0401fa5d84682604d4f1e44b --f46d0401fa5d84682604d4f1e44b Content-Type: text/plain; charset=UTF-8 I can't seem to attach the block device in domain 0 either: # xl block-attach 0 file:/home/data/xen/megatron/root.img /dev/xvda libxl: error: libxl.c:1752:libxl__device_from_disk: Invalid or unsupported virtual disk identifier /dev/xvda libxl: error: libxl.c:1844:device_disk_add: Invalid or unsupported virtual disk identifier /dev/xvda libxl: error: libxl.c:1720:device_addrm_aocomplete: unable to add device libxl_device_disk_add failed. I still feel like I'm missing a kernel config option or something, but I have no idea where to look. The Xen block backend and frontend drivers are both included, seems strange that I would be missing support for a simple loopback file. On Mon, Feb 4, 2013 at 5:37 PM, Stephen Kent wrote: > I checked, PCI is enabled in both my dom0 and domU kernels. I've enabled > all the Xen drivers I can find (including the block device frontend and > backend drivers). > > > On Mon, Feb 4, 2013 at 11:45 AM, Rushikesh Jadhav <2rushikeshj@gmail.com>wrote: > >> On Tue, Feb 5, 2013 at 12:00 AM, Stephen Kent wrote: >> >>> I just upgraded my computer from an old kernel (2.6.34-xen) to 3.6.11, >>> and upgraded Xen to 4.2.0. I can't seem to get my domU to boot, as it can't >>> find the root filesystem. >>> >>> I've compiled a domU kernel (also 3.6.11) with xen-blkfront built-in and >>> set the domU config file with this disk configuration: >>> >>> disk = [ 'file:/home/data/xen/megatron/root.img,xvda,w' ] >>> >>> (The disk is just a file with an ext3 filesystem, I can mount it on >>> loopback in dom0) >>> >>> After I xl start my domU, xl block-list in dom0 shows the device >>> connected to the domU but the domU kernel (with root=/dev/xvda) can't find >>> the root filesystem: >>> >>> >>> [...] >>> XENBUS: Timeout connecting to device: device/vbd/51712 (local state 3, >>> remote state 1) >>> console [netcon0] enabled >>> netconsole: network logging started >>> ALSA device list: >>> No soundcards found. >>> md: Waiting for all devices to be available before autodetect >>> md: If you don't use raid, use raid=noautodetect >>> md: Autodetecting RAID arrays. >>> md: Scanned 0 and added 0 devices. >>> md: autorun ... >>> md: ... autorun DONE. >>> VFS: Cannot open root device "xvda" or unknown-block(0,0): error -6 >>> Please append a correct "root=" boot option; here are the available >>> partitions: >>> Kernel panic - not syncing: VFS: Unable to mount root fs on >>> unknown-block(0,0) >>> Pid: 1, comm: swapper/0 Not tainted 3.6.11-gentoo #8 >>> Call Trace: >>> [] ? panic+0xc5/0x1cc >>> [] ? printk+0x4c/0x51 >>> [] ? mount_block_root+0x1d4/0x1f2 >>> [] ? lg_local_lock+0x11/0x14 >>> [] ? kvm_io_bus_sort_cmp+0x1c/0x27 >>> [] ? sys_mknodat+0x12c/0x140 >>> [] ? mount_root+0x124/0x12b >>> [] ? initrd_load+0x303/0x309 >>> [] ? prepare_namespace+0x168/0x19e >>> [] ? kernel_init+0x17f/0x191 >>> [] ? parse_early_options+0x2a/0x2a >>> [] ? kernel_thread_helper+0x4/0x10 >>> [] ? retint_restore_args+0x5/0x6 >>> [] ? gs_change+0x13/0x13 >>> >>> >> Check if you have PCI enabled in domU kernel. >> Select the PCI options while you do # make menuconfig >> >> >> >>> >>> I don't see any earlier kernel messages about the Xen block frontend >>> driver loading. Am I missing a kernel option or something? I'm not sure >>> what else to try. >>> >>> Thanks! >>> >>> _______________________________________________ >>> Xen-users mailing list >>> Xen-users@lists.xen.org >>> http://lists.xen.org/xen-users >>> >> >> > --f46d0401fa5d84682604d4f1e44b Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable I can't seem to attach the block device in domain 0 either:

# xl block-attach 0 file:/home/data/xen/megatron/root.img /dev= /xvda
libxl: error: libxl.c:1752:libxl__device_from_disk: Invalid= or unsupported virtual disk identifier /dev/xvda
libxl: error: libxl.c:1844:device_disk_add: Invalid or unsupported vir= tual disk identifier /dev/xvda
libxl: error: libxl.c:1720:device_= addrm_aocomplete: unable to add device
libxl_device_disk_add fail= ed.

I still feel like I'm missing a kernel config optio= n or something, but I have no idea where to look. The Xen block backend and= frontend drivers are both included, seems strange that I would be missing = support for a simple loopback file.


On Mon, Feb 4, 2013 at 5:37 P= M, Stephen Kent <smkent@smkent.net> wrote:
I checked, PCI is enabled in both my dom0 and domU kernels. I've enable= d all the Xen drivers I can find (including the block device frontend and b= ackend drivers).


On Mon, Feb 4, 2013 at 11:45 AM, Rushikesh Jadhav <2rushikeshj@gmail.c= om> wrote:
On Tue,= Feb 5, 2013 at 12:00 AM, Stephen Kent <smkent@smkent.net> w= rote:
I just upgraded my computer from an old kernel (2.6.34-xen) to 3.6.11,= and upgraded Xen to 4.2.0. I can't seem to get my domU to boot, as it = can't find the root filesystem.

I've compi= led a domU kernel (also 3.6.11) with xen-blkfront built-in and set the domU= config file with this disk configuration:

disk =3D [ 'file:/home/data/xen/megatron/root.img,x= vda,w' ]

(The disk is just a file with an ext3= filesystem, I can mount it on loopback in dom0)

After I xl start my domU, xl block-list in dom0 shows the device connected = to the domU but the domU kernel (with root=3D/dev/xvda) can't find the = root filesystem:


[...]
XENBUS: Timeout connecting to device: device/vbd/51712 (local state 3, remo= te state 1)
console [netcon0] enabled
netconsole: netwo= rk logging started
ALSA device list:
=C2=A0 No soundcar= ds found.
md: Waiting for all devices to be available before autodetect
md: If you don't use raid, use raid=3Dnoautodetect
md: Auto= detecting RAID arrays.
md: Scanned 0 and added 0 devices.
md: autorun ...
md: ... autorun DONE.
VFS: Cannot = open root device "xvda" or unknown-block(0,0): error -6
Please append a correct "root=3D" boot option; here are the avai= lable partitions:
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-bl= ock(0,0)
Pid: 1, comm: swapper/0 Not tainted 3.6.11-gentoo #8
Call Trace:
=C2=A0[<ffffffff815c59ff>] ? panic+0xc5/= 0x1cc
=C2=A0[<ffffffff815c5bd9>] ? printk+0x4c/0x51
=C2=A0[&= lt;ffffffff819990cd>] ? mount_block_root+0x1d4/0x1f2
=C2=A0[&l= t;ffffffff8108ebaa>] ? lg_local_lock+0x11/0x14
=C2=A0[<ffff= ffff81002930>] ? kvm_io_bus_sort_cmp+0x1c/0x27
=C2=A0[<ffffffff8110fcf8>] ? sys_mknodat+0x12c/0x140
= =C2=A0[<ffffffff8199920f>] ? mount_root+0x124/0x12b
=C2=A0[= <ffffffff81999d8f>] ? initrd_load+0x303/0x309
=C2=A0[<ff= ffffff8199937e>] ? prepare_namespace+0x168/0x19e
=C2=A0[<ffffffff81998702>] ? kernel_init+0x17f/0x191
= =C2=A0[<ffffffff8199852b>] ? parse_early_options+0x2a/0x2a
= =C2=A0[<ffffffff815cf644>] ? kernel_thread_helper+0x4/0x10
= =C2=A0[<ffffffff815c8338>] ? retint_restore_args+0x5/0x6
=C2=A0[<ffffffff815cf640>] ? gs_change+0x13/0x13

<= /div>

Check if you have PCI enabled in dom= U kernel.
Select the PCI options while you do # make menuconfig

= =C2=A0

I don't see any earlier kernel messages = about the Xen block frontend driver loading. Am I missing a kernel option o= r something? I'm not sure what else to try.

Thanks!

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



--f46d0401fa5d84682604d4f1e44b-- --===============4471116421802472934== 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 --===============4471116421802472934==-- From xen-users-bounces@lists.xen.org Tue Feb 05 03:55:04 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 05 Feb 2013 03:55: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 1U2ZbG-0008DI-WF; Tue, 05 Feb 2013 03:53:39 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U2ZbF-0008DC-I3 for xen-users@lists.xen.org; Tue, 05 Feb 2013 03:53:37 +0000 Received: from [85.158.143.99:40009] by server-2.bemta-4.messagelabs.com id C0/42-01597-04280115; Tue, 05 Feb 2013 03:53:36 +0000 X-Env-Sender: smkent@smkent.net X-Msg-Ref: server-13.tower-216.messagelabs.com!1360036409!29943410!1 X-Originating-IP: [209.85.217.170] 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.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 19266 invoked from network); 5 Feb 2013 03:53:29 -0000 Received: from mail-lb0-f170.google.com (HELO mail-lb0-f170.google.com) (209.85.217.170) by server-13.tower-216.messagelabs.com with RC4-SHA encrypted SMTP; 5 Feb 2013 03:53:29 -0000 Received: by mail-lb0-f170.google.com with SMTP id ge1so7286387lbb.29 for ; Mon, 04 Feb 2013 19:53:28 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-received:x-originating-ip:in-reply-to:references :date:message-id:subject:from:to:cc:content-type:x-gm-message-state; bh=hDoTJjhbEJmEV5q3cPRNxyhE5+lGOmNkY4KM+/gNVF4=; b=CHaywOWX75T5bW0TD/m6cJ0gHaDL4bzUXo2Bu/Muprm2GKcNCC2YXDJ8xfMLV5ixHP fVjkHL9bKHcEsyqSlPzXukVymn3+GP8SMvyuyFDGvVXd1pl/Vmi+DmAIejZ8iJe9iAOR b/Ls4ISVdJV/U8XE0cBJK7A2YPK3qqJtepSJk1FLHQoisZ9hSTI44We2vZjs0dNgg3l+ KqPeWz6uK5uk6L/94ULIGEM+cWyhE/uTyqThaIYr6yOSdUOLUoWpPlhf3lOtqZ0y4FhF CN7PpoXj6NRR9BpMatIM/nn3I5hUMtf09az2Q6Pu8d6wKJ9VYX/HL9eRmh+LdEZjy5HP mqsA== MIME-Version: 1.0 X-Received: by 10.112.102.5 with SMTP id fk5mr9166636lbb.31.1360036408777; Mon, 04 Feb 2013 19:53:28 -0800 (PST) Received: by 10.112.131.137 with HTTP; Mon, 4 Feb 2013 19:53:28 -0800 (PST) X-Originating-IP: [174.21.254.192] In-Reply-To: References: Date: Mon, 4 Feb 2013 19:53:28 -0800 Message-ID: From: Stephen Kent To: Rushikesh Jadhav <2rushikeshj@gmail.com> X-Gm-Message-State: ALoCoQlgIf5Y1Iwsoqe+iPfSZ6f0kySGejmL4Q8Z6aoR/VXGvOG3pHr/FB1FyUKOeCe8orcakC35 Cc: xen-users@lists.xen.org Subject: Re: [Xen-users] XENBUS: Timeout connecting to device: device/vbd/51712 (local state 3, remote state 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="===============8915799093867293112==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============8915799093867293112== Content-Type: multipart/alternative; boundary=f46d0401fa8b06dd6204d4f2277f --f46d0401fa8b06dd6204d4f2277f Content-Type: text/plain; charset=UTF-8 It turns out /dev/xvda is the wrong type of disk specifier, just using "xvda" is correct instead. However, I'm still having issues attaching my virtual disks. If I manually run losetup /dev/loop1 /home/data/xen/megatron/root.img, and then attach phy:/dev/loop1 in my dom0, /dev/xvda appears and I can mount it. But, if I try to boot my domU with phy:/dev/loop1 instead of the file path, it just enters a reboot loop. On my dom0, when I try to xl block-attach the file directly (without a loop device), the command appears to succeed and xl block-list shows the device, but /dev/xvda is not created and nothing about xvda shows up in dmesg. It seems like the file backend driver in my dom0 is broken. Does this make sense to anyone? On Mon, Feb 4, 2013 at 7:34 PM, Stephen Kent wrote: > I can't seem to attach the block device in domain 0 either: > > # xl block-attach 0 file:/home/data/xen/megatron/root.img /dev/xvda > libxl: error: libxl.c:1752:libxl__device_from_disk: Invalid or unsupported > virtual disk identifier /dev/xvda > libxl: error: libxl.c:1844:device_disk_add: Invalid or unsupported virtual > disk identifier /dev/xvda > libxl: error: libxl.c:1720:device_addrm_aocomplete: unable to add device > libxl_device_disk_add failed. > > I still feel like I'm missing a kernel config option or something, but I > have no idea where to look. The Xen block backend and frontend drivers are > both included, seems strange that I would be missing support for a simple > loopback file. > > > On Mon, Feb 4, 2013 at 5:37 PM, Stephen Kent wrote: > >> I checked, PCI is enabled in both my dom0 and domU kernels. I've enabled >> all the Xen drivers I can find (including the block device frontend and >> backend drivers). >> >> >> On Mon, Feb 4, 2013 at 11:45 AM, Rushikesh Jadhav <2rushikeshj@gmail.com>wrote: >> >>> On Tue, Feb 5, 2013 at 12:00 AM, Stephen Kent wrote: >>> >>>> I just upgraded my computer from an old kernel (2.6.34-xen) to 3.6.11, >>>> and upgraded Xen to 4.2.0. I can't seem to get my domU to boot, as it can't >>>> find the root filesystem. >>>> >>>> I've compiled a domU kernel (also 3.6.11) with xen-blkfront built-in >>>> and set the domU config file with this disk configuration: >>>> >>>> disk = [ 'file:/home/data/xen/megatron/root.img,xvda,w' ] >>>> >>>> (The disk is just a file with an ext3 filesystem, I can mount it on >>>> loopback in dom0) >>>> >>>> After I xl start my domU, xl block-list in dom0 shows the device >>>> connected to the domU but the domU kernel (with root=/dev/xvda) can't find >>>> the root filesystem: >>>> >>>> >>>> [...] >>>> XENBUS: Timeout connecting to device: device/vbd/51712 (local state 3, >>>> remote state 1) >>>> console [netcon0] enabled >>>> netconsole: network logging started >>>> ALSA device list: >>>> No soundcards found. >>>> md: Waiting for all devices to be available before autodetect >>>> md: If you don't use raid, use raid=noautodetect >>>> md: Autodetecting RAID arrays. >>>> md: Scanned 0 and added 0 devices. >>>> md: autorun ... >>>> md: ... autorun DONE. >>>> VFS: Cannot open root device "xvda" or unknown-block(0,0): error -6 >>>> Please append a correct "root=" boot option; here are the available >>>> partitions: >>>> Kernel panic - not syncing: VFS: Unable to mount root fs on >>>> unknown-block(0,0) >>>> Pid: 1, comm: swapper/0 Not tainted 3.6.11-gentoo #8 >>>> Call Trace: >>>> [] ? panic+0xc5/0x1cc >>>> [] ? printk+0x4c/0x51 >>>> [] ? mount_block_root+0x1d4/0x1f2 >>>> [] ? lg_local_lock+0x11/0x14 >>>> [] ? kvm_io_bus_sort_cmp+0x1c/0x27 >>>> [] ? sys_mknodat+0x12c/0x140 >>>> [] ? mount_root+0x124/0x12b >>>> [] ? initrd_load+0x303/0x309 >>>> [] ? prepare_namespace+0x168/0x19e >>>> [] ? kernel_init+0x17f/0x191 >>>> [] ? parse_early_options+0x2a/0x2a >>>> [] ? kernel_thread_helper+0x4/0x10 >>>> [] ? retint_restore_args+0x5/0x6 >>>> [] ? gs_change+0x13/0x13 >>>> >>>> >>> Check if you have PCI enabled in domU kernel. >>> Select the PCI options while you do # make menuconfig >>> >>> >>> >>>> >>>> I don't see any earlier kernel messages about the Xen block frontend >>>> driver loading. Am I missing a kernel option or something? I'm not sure >>>> what else to try. >>>> >>>> Thanks! >>>> >>>> _______________________________________________ >>>> Xen-users mailing list >>>> Xen-users@lists.xen.org >>>> http://lists.xen.org/xen-users >>>> >>> >>> >> > --f46d0401fa8b06dd6204d4f2277f Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable It turns out /dev/xvda is the wrong type of disk specifier, just using &quo= t;xvda" is correct instead.

However, I'm still = having issues attaching my virtual disks. If I manually run losetup /dev/lo= op1 /home/data/xen/megatron/root.img, and then attach phy:/dev/loop1 in my = dom0, /dev/xvda appears and I can mount it. But, if I try to boot my domU w= ith phy:/dev/loop1 instead of the file path, it just enters a reboot loop. = On my dom0, when I try to xl block-attach the file directly (without a loop= device), the command appears to succeed and xl block-list shows the device= , but /dev/xvda is not created and nothing about xvda shows up in dmesg.

It seems like the file backend driver in my dom0 is bro= ken. Does this make sense to anyone?



On Mon, Feb 4, 2013 at 7:34 PM, Steph= en Kent <smkent@smkent.net> wrote:
I can't seem to attach the block device = in domain 0 either:

# xl block-attach 0 file:/home/= data/xen/megatron/root.img /dev/xvda
libxl: error: libxl.c:1752:libxl__device_from_disk: Invalid or unsuppo= rted virtual disk identifier /dev/xvda
libxl: error: libxl.c:1844:device_disk_add: Invalid or unsupported vir= tual disk identifier /dev/xvda
libxl: error: libxl.c:1720:device_= addrm_aocomplete: unable to add device
libxl_device_disk_add fail= ed.

I still feel like I'm missing a kernel config optio= n or something, but I have no idea where to look. The Xen block backend and= frontend drivers are both included, seems strange that I would be missing = support for a simple loopback file.


On Mon, Feb 4, 2013 at 5:37 P= M, Stephen Kent <smkent@smkent.net> wrote:
I checked, PCI is enabled in both my dom0 and domU kernels. I've enable= d all the Xen drivers I can find (including the block device frontend and b= ackend drivers).


On Mon, Feb 4, 2013 at 11:45 AM, Rushikesh Jadhav <2rushikeshj@gmail.c= om> wrote:
On Tue,= Feb 5, 2013 at 12:00 AM, Stephen Kent <smkent@smkent.net> w= rote:
I just upgraded my computer from an old kernel (2.6.34-xen) to 3.6.11,= and upgraded Xen to 4.2.0. I can't seem to get my domU to boot, as it = can't find the root filesystem.

I've compi= led a domU kernel (also 3.6.11) with xen-blkfront built-in and set the domU= config file with this disk configuration:

disk =3D [ 'file:/home/data/xen/megatron/root.img,x= vda,w' ]

(The disk is just a file with an ext3= filesystem, I can mount it on loopback in dom0)

After I xl start my domU, xl block-list in dom0 shows the device connected = to the domU but the domU kernel (with root=3D/dev/xvda) can't find the = root filesystem:


[...]
XENBUS: Timeout connecting to device: device/vbd/51712 (local state 3, remo= te state 1)
console [netcon0] enabled
netconsole: netwo= rk logging started
ALSA device list:
=C2=A0 No soundcar= ds found.
md: Waiting for all devices to be available before autodetect
md: If you don't use raid, use raid=3Dnoautodetect
md: Auto= detecting RAID arrays.
md: Scanned 0 and added 0 devices.
md: autorun ...
md: ... autorun DONE.
VFS: Cannot = open root device "xvda" or unknown-block(0,0): error -6
Please append a correct "root=3D" boot option; here are the avai= lable partitions:
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-bl= ock(0,0)
Pid: 1, comm: swapper/0 Not tainted 3.6.11-gentoo #8
Call Trace:
=C2=A0[<ffffffff815c59ff>] ? panic+0xc5/= 0x1cc
=C2=A0[<ffffffff815c5bd9>] ? printk+0x4c/0x51
=C2=A0[&= lt;ffffffff819990cd>] ? mount_block_root+0x1d4/0x1f2
=C2=A0[&l= t;ffffffff8108ebaa>] ? lg_local_lock+0x11/0x14
=C2=A0[<ffff= ffff81002930>] ? kvm_io_bus_sort_cmp+0x1c/0x27
=C2=A0[<ffffffff8110fcf8>] ? sys_mknodat+0x12c/0x140
= =C2=A0[<ffffffff8199920f>] ? mount_root+0x124/0x12b
=C2=A0[= <ffffffff81999d8f>] ? initrd_load+0x303/0x309
=C2=A0[<ff= ffffff8199937e>] ? prepare_namespace+0x168/0x19e
=C2=A0[<ffffffff81998702>] ? kernel_init+0x17f/0x191
= =C2=A0[<ffffffff8199852b>] ? parse_early_options+0x2a/0x2a
= =C2=A0[<ffffffff815cf644>] ? kernel_thread_helper+0x4/0x10
= =C2=A0[<ffffffff815c8338>] ? retint_restore_args+0x5/0x6
=C2=A0[<ffffffff815cf640>] ? gs_change+0x13/0x13

<= /div>

Check if you have PCI enabled in dom= U kernel.
Select the PCI options while you do # make menuconfig

= =C2=A0

I don't see any earlier kernel messages = about the Xen block frontend driver loading. Am I missing a kernel option o= r something? I'm not sure what else to try.

Thanks!

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




--f46d0401fa8b06dd6204d4f2277f-- --===============8915799093867293112== 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 --===============8915799093867293112==-- From xen-users-bounces@lists.xen.org Tue Feb 05 03:55:04 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 05 Feb 2013 03:55: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 1U2ZbG-0008DI-WF; Tue, 05 Feb 2013 03:53:39 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U2ZbF-0008DC-I3 for xen-users@lists.xen.org; Tue, 05 Feb 2013 03:53:37 +0000 Received: from [85.158.143.99:40009] by server-2.bemta-4.messagelabs.com id C0/42-01597-04280115; Tue, 05 Feb 2013 03:53:36 +0000 X-Env-Sender: smkent@smkent.net X-Msg-Ref: server-13.tower-216.messagelabs.com!1360036409!29943410!1 X-Originating-IP: [209.85.217.170] 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.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 19266 invoked from network); 5 Feb 2013 03:53:29 -0000 Received: from mail-lb0-f170.google.com (HELO mail-lb0-f170.google.com) (209.85.217.170) by server-13.tower-216.messagelabs.com with RC4-SHA encrypted SMTP; 5 Feb 2013 03:53:29 -0000 Received: by mail-lb0-f170.google.com with SMTP id ge1so7286387lbb.29 for ; Mon, 04 Feb 2013 19:53:28 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-received:x-originating-ip:in-reply-to:references :date:message-id:subject:from:to:cc:content-type:x-gm-message-state; bh=hDoTJjhbEJmEV5q3cPRNxyhE5+lGOmNkY4KM+/gNVF4=; b=CHaywOWX75T5bW0TD/m6cJ0gHaDL4bzUXo2Bu/Muprm2GKcNCC2YXDJ8xfMLV5ixHP fVjkHL9bKHcEsyqSlPzXukVymn3+GP8SMvyuyFDGvVXd1pl/Vmi+DmAIejZ8iJe9iAOR b/Ls4ISVdJV/U8XE0cBJK7A2YPK3qqJtepSJk1FLHQoisZ9hSTI44We2vZjs0dNgg3l+ KqPeWz6uK5uk6L/94ULIGEM+cWyhE/uTyqThaIYr6yOSdUOLUoWpPlhf3lOtqZ0y4FhF CN7PpoXj6NRR9BpMatIM/nn3I5hUMtf09az2Q6Pu8d6wKJ9VYX/HL9eRmh+LdEZjy5HP mqsA== MIME-Version: 1.0 X-Received: by 10.112.102.5 with SMTP id fk5mr9166636lbb.31.1360036408777; Mon, 04 Feb 2013 19:53:28 -0800 (PST) Received: by 10.112.131.137 with HTTP; Mon, 4 Feb 2013 19:53:28 -0800 (PST) X-Originating-IP: [174.21.254.192] In-Reply-To: References: Date: Mon, 4 Feb 2013 19:53:28 -0800 Message-ID: From: Stephen Kent To: Rushikesh Jadhav <2rushikeshj@gmail.com> X-Gm-Message-State: ALoCoQlgIf5Y1Iwsoqe+iPfSZ6f0kySGejmL4Q8Z6aoR/VXGvOG3pHr/FB1FyUKOeCe8orcakC35 Cc: xen-users@lists.xen.org Subject: Re: [Xen-users] XENBUS: Timeout connecting to device: device/vbd/51712 (local state 3, remote state 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="===============8915799093867293112==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============8915799093867293112== Content-Type: multipart/alternative; boundary=f46d0401fa8b06dd6204d4f2277f --f46d0401fa8b06dd6204d4f2277f Content-Type: text/plain; charset=UTF-8 It turns out /dev/xvda is the wrong type of disk specifier, just using "xvda" is correct instead. However, I'm still having issues attaching my virtual disks. If I manually run losetup /dev/loop1 /home/data/xen/megatron/root.img, and then attach phy:/dev/loop1 in my dom0, /dev/xvda appears and I can mount it. But, if I try to boot my domU with phy:/dev/loop1 instead of the file path, it just enters a reboot loop. On my dom0, when I try to xl block-attach the file directly (without a loop device), the command appears to succeed and xl block-list shows the device, but /dev/xvda is not created and nothing about xvda shows up in dmesg. It seems like the file backend driver in my dom0 is broken. Does this make sense to anyone? On Mon, Feb 4, 2013 at 7:34 PM, Stephen Kent wrote: > I can't seem to attach the block device in domain 0 either: > > # xl block-attach 0 file:/home/data/xen/megatron/root.img /dev/xvda > libxl: error: libxl.c:1752:libxl__device_from_disk: Invalid or unsupported > virtual disk identifier /dev/xvda > libxl: error: libxl.c:1844:device_disk_add: Invalid or unsupported virtual > disk identifier /dev/xvda > libxl: error: libxl.c:1720:device_addrm_aocomplete: unable to add device > libxl_device_disk_add failed. > > I still feel like I'm missing a kernel config option or something, but I > have no idea where to look. The Xen block backend and frontend drivers are > both included, seems strange that I would be missing support for a simple > loopback file. > > > On Mon, Feb 4, 2013 at 5:37 PM, Stephen Kent wrote: > >> I checked, PCI is enabled in both my dom0 and domU kernels. I've enabled >> all the Xen drivers I can find (including the block device frontend and >> backend drivers). >> >> >> On Mon, Feb 4, 2013 at 11:45 AM, Rushikesh Jadhav <2rushikeshj@gmail.com>wrote: >> >>> On Tue, Feb 5, 2013 at 12:00 AM, Stephen Kent wrote: >>> >>>> I just upgraded my computer from an old kernel (2.6.34-xen) to 3.6.11, >>>> and upgraded Xen to 4.2.0. I can't seem to get my domU to boot, as it can't >>>> find the root filesystem. >>>> >>>> I've compiled a domU kernel (also 3.6.11) with xen-blkfront built-in >>>> and set the domU config file with this disk configuration: >>>> >>>> disk = [ 'file:/home/data/xen/megatron/root.img,xvda,w' ] >>>> >>>> (The disk is just a file with an ext3 filesystem, I can mount it on >>>> loopback in dom0) >>>> >>>> After I xl start my domU, xl block-list in dom0 shows the device >>>> connected to the domU but the domU kernel (with root=/dev/xvda) can't find >>>> the root filesystem: >>>> >>>> >>>> [...] >>>> XENBUS: Timeout connecting to device: device/vbd/51712 (local state 3, >>>> remote state 1) >>>> console [netcon0] enabled >>>> netconsole: network logging started >>>> ALSA device list: >>>> No soundcards found. >>>> md: Waiting for all devices to be available before autodetect >>>> md: If you don't use raid, use raid=noautodetect >>>> md: Autodetecting RAID arrays. >>>> md: Scanned 0 and added 0 devices. >>>> md: autorun ... >>>> md: ... autorun DONE. >>>> VFS: Cannot open root device "xvda" or unknown-block(0,0): error -6 >>>> Please append a correct "root=" boot option; here are the available >>>> partitions: >>>> Kernel panic - not syncing: VFS: Unable to mount root fs on >>>> unknown-block(0,0) >>>> Pid: 1, comm: swapper/0 Not tainted 3.6.11-gentoo #8 >>>> Call Trace: >>>> [] ? panic+0xc5/0x1cc >>>> [] ? printk+0x4c/0x51 >>>> [] ? mount_block_root+0x1d4/0x1f2 >>>> [] ? lg_local_lock+0x11/0x14 >>>> [] ? kvm_io_bus_sort_cmp+0x1c/0x27 >>>> [] ? sys_mknodat+0x12c/0x140 >>>> [] ? mount_root+0x124/0x12b >>>> [] ? initrd_load+0x303/0x309 >>>> [] ? prepare_namespace+0x168/0x19e >>>> [] ? kernel_init+0x17f/0x191 >>>> [] ? parse_early_options+0x2a/0x2a >>>> [] ? kernel_thread_helper+0x4/0x10 >>>> [] ? retint_restore_args+0x5/0x6 >>>> [] ? gs_change+0x13/0x13 >>>> >>>> >>> Check if you have PCI enabled in domU kernel. >>> Select the PCI options while you do # make menuconfig >>> >>> >>> >>>> >>>> I don't see any earlier kernel messages about the Xen block frontend >>>> driver loading. Am I missing a kernel option or something? I'm not sure >>>> what else to try. >>>> >>>> Thanks! >>>> >>>> _______________________________________________ >>>> Xen-users mailing list >>>> Xen-users@lists.xen.org >>>> http://lists.xen.org/xen-users >>>> >>> >>> >> > --f46d0401fa8b06dd6204d4f2277f Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable It turns out /dev/xvda is the wrong type of disk specifier, just using &quo= t;xvda" is correct instead.

However, I'm still = having issues attaching my virtual disks. If I manually run losetup /dev/lo= op1 /home/data/xen/megatron/root.img, and then attach phy:/dev/loop1 in my = dom0, /dev/xvda appears and I can mount it. But, if I try to boot my domU w= ith phy:/dev/loop1 instead of the file path, it just enters a reboot loop. = On my dom0, when I try to xl block-attach the file directly (without a loop= device), the command appears to succeed and xl block-list shows the device= , but /dev/xvda is not created and nothing about xvda shows up in dmesg.

It seems like the file backend driver in my dom0 is bro= ken. Does this make sense to anyone?



On Mon, Feb 4, 2013 at 7:34 PM, Steph= en Kent <smkent@smkent.net> wrote:
I can't seem to attach the block device = in domain 0 either:

# xl block-attach 0 file:/home/= data/xen/megatron/root.img /dev/xvda
libxl: error: libxl.c:1752:libxl__device_from_disk: Invalid or unsuppo= rted virtual disk identifier /dev/xvda
libxl: error: libxl.c:1844:device_disk_add: Invalid or unsupported vir= tual disk identifier /dev/xvda
libxl: error: libxl.c:1720:device_= addrm_aocomplete: unable to add device
libxl_device_disk_add fail= ed.

I still feel like I'm missing a kernel config optio= n or something, but I have no idea where to look. The Xen block backend and= frontend drivers are both included, seems strange that I would be missing = support for a simple loopback file.


On Mon, Feb 4, 2013 at 5:37 P= M, Stephen Kent <smkent@smkent.net> wrote:
I checked, PCI is enabled in both my dom0 and domU kernels. I've enable= d all the Xen drivers I can find (including the block device frontend and b= ackend drivers).


On Mon, Feb 4, 2013 at 11:45 AM, Rushikesh Jadhav <2rushikeshj@gmail.c= om> wrote:
On Tue,= Feb 5, 2013 at 12:00 AM, Stephen Kent <smkent@smkent.net> w= rote:
I just upgraded my computer from an old kernel (2.6.34-xen) to 3.6.11,= and upgraded Xen to 4.2.0. I can't seem to get my domU to boot, as it = can't find the root filesystem.

I've compi= led a domU kernel (also 3.6.11) with xen-blkfront built-in and set the domU= config file with this disk configuration:

disk =3D [ 'file:/home/data/xen/megatron/root.img,x= vda,w' ]

(The disk is just a file with an ext3= filesystem, I can mount it on loopback in dom0)

After I xl start my domU, xl block-list in dom0 shows the device connected = to the domU but the domU kernel (with root=3D/dev/xvda) can't find the = root filesystem:


[...]
XENBUS: Timeout connecting to device: device/vbd/51712 (local state 3, remo= te state 1)
console [netcon0] enabled
netconsole: netwo= rk logging started
ALSA device list:
=C2=A0 No soundcar= ds found.
md: Waiting for all devices to be available before autodetect
md: If you don't use raid, use raid=3Dnoautodetect
md: Auto= detecting RAID arrays.
md: Scanned 0 and added 0 devices.
md: autorun ...
md: ... autorun DONE.
VFS: Cannot = open root device "xvda" or unknown-block(0,0): error -6
Please append a correct "root=3D" boot option; here are the avai= lable partitions:
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-bl= ock(0,0)
Pid: 1, comm: swapper/0 Not tainted 3.6.11-gentoo #8
Call Trace:
=C2=A0[<ffffffff815c59ff>] ? panic+0xc5/= 0x1cc
=C2=A0[<ffffffff815c5bd9>] ? printk+0x4c/0x51
=C2=A0[&= lt;ffffffff819990cd>] ? mount_block_root+0x1d4/0x1f2
=C2=A0[&l= t;ffffffff8108ebaa>] ? lg_local_lock+0x11/0x14
=C2=A0[<ffff= ffff81002930>] ? kvm_io_bus_sort_cmp+0x1c/0x27
=C2=A0[<ffffffff8110fcf8>] ? sys_mknodat+0x12c/0x140
= =C2=A0[<ffffffff8199920f>] ? mount_root+0x124/0x12b
=C2=A0[= <ffffffff81999d8f>] ? initrd_load+0x303/0x309
=C2=A0[<ff= ffffff8199937e>] ? prepare_namespace+0x168/0x19e
=C2=A0[<ffffffff81998702>] ? kernel_init+0x17f/0x191
= =C2=A0[<ffffffff8199852b>] ? parse_early_options+0x2a/0x2a
= =C2=A0[<ffffffff815cf644>] ? kernel_thread_helper+0x4/0x10
= =C2=A0[<ffffffff815c8338>] ? retint_restore_args+0x5/0x6
=C2=A0[<ffffffff815cf640>] ? gs_change+0x13/0x13

<= /div>

Check if you have PCI enabled in dom= U kernel.
Select the PCI options while you do # make menuconfig

= =C2=A0

I don't see any earlier kernel messages = about the Xen block frontend driver loading. Am I missing a kernel option o= r something? I'm not sure what else to try.

Thanks!

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




--f46d0401fa8b06dd6204d4f2277f-- --===============8915799093867293112== 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 --===============8915799093867293112==-- From xen-users-bounces@lists.xen.org Tue Feb 05 09:32:25 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 05 Feb 2013 09:32: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 1U2ert-0005eB-Cn; Tue, 05 Feb 2013 09:31:09 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U2err-0005e3-VY for xen-users@lists.xen.org; Tue, 05 Feb 2013 09:31:08 +0000 Received: from [85.158.138.51:55915] by server-7.bemta-3.messagelabs.com id 94/04-10367-651D0115; Tue, 05 Feb 2013 09:31:02 +0000 X-Env-Sender: Ian.Campbell@citrix.com X-Msg-Ref: server-16.tower-174.messagelabs.com!1360056659!30892948!1 X-Originating-IP: [46.33.159.39] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNDYuMzMuMTU5LjM5ID0+IDIwODEx\n X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 3877 invoked from network); 5 Feb 2013 09:31:00 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (46.33.159.39) by server-16.tower-174.messagelabs.com with RC4-SHA encrypted SMTP; 5 Feb 2013 09:31:00 -0000 X-IronPort-AV: E=Sophos;i="4.84,602,1355097600"; d="scan'208";a="1145730" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 05 Feb 2013 09:31:00 +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.297.1; Tue, 5 Feb 2013 09:30:59 +0000 Message-ID: <1360056658.7743.88.camel@zakaz.uk.xensource.com> From: Ian Campbell To: Matthias Date: Tue, 5 Feb 2013 09:30:58 +0000 In-Reply-To: References: <1359369167.6559.46.camel@zakaz.uk.xensource.com> <1359980575.7466.5.camel@zakaz.uk.xensource.com> Organization: Citrix Systems, Inc. X-Mailer: Evolution 3.4.4-1 MIME-Version: 1.0 Cc: "xen-users@lists.xen.org" Subject: Re: [Xen-users] xl nat and wrong IPs X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: 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, 2013-02-04 at 21:28 +0000, Matthias wrote: > I guess i finally understood the basic idea of the nat script: > > You set an IP for the vif interface. This will not be the IP of the > interface, but the IP the domU will be using internally. This way if > the dom0 receives a package for the configured IP, it will be routed > through the dom0-interface to the domU. (In detail: This way the > package goes into the iptables forward chain and not the input chain, > changing the hosts general treatment of the package). > > So not setting the interface to the configured IP but only creating an > ip route makes perfect sense. Is an IP on the vifX.Y device not required in order to route to it? And does that IP not need to differ from the one on the guests eth0 device? (otherwise the packet will get delivered to dom0) In the routing variant we use the IP address of dom0's own interface on all of the vifX.Y devices, I wonder why this doesn't suffice for NAT. > But then the vif-nat script assignes an IP+127 to the interface. This > creates 2 problems in my opinion: > > 1) When using the dom0 for routing network traffic from one domU to an > other, so basically using the dom0 as a network cable, the src > attribute used in the routing creation will alter the source ip > address from one domU to the ip+127 address which is, at least in my > network setup, pretty annoying. > > So if you got domUs A (IP 10.0.0.1) and B (IP 10.0.0.2) and send > traffic from A to B, B will see the traffic coming from 10.0.0.128 > instead of .1 . Isn't this an expected property of NAT? When communicating with off box hosts/VMs the IP address would be dom0's IP address. Sounds like you might actually want a nat'ed brouter type configuration? (i.e. the guests are bridged but offbox traffic is nat'ed) > 2) I haven't tested it, but I don't really know what would happen if > you set IPs >128 in the domU configuration and this way create > out-of-bounce routing IPs. I suspect this is probably a case of "don't do that". > Well, I think that most people don't use the nat feature of xen and > this isn't tested much.. But somebody might want to look at it at a > given point of time... It's certainly not the most widely used configuration. > For me, changing the IP setting lines to > > do_or_die ip addr add "0.0.0.0" dev "${dev}" > do_or_die ip route add "$vif_ip" dev "${dev}" > > This doesn't set an IP to the interface in the domU and no src. > attribute to the route, fixing the above issues.. Might be worth > thinkin about including in xen main line, i don't really know.. Me neither. > Posted this only if somebody might need this later.. Thanks. Ian. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Tue Feb 05 09:32:25 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 05 Feb 2013 09:32: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 1U2ert-0005eB-Cn; Tue, 05 Feb 2013 09:31:09 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U2err-0005e3-VY for xen-users@lists.xen.org; Tue, 05 Feb 2013 09:31:08 +0000 Received: from [85.158.138.51:55915] by server-7.bemta-3.messagelabs.com id 94/04-10367-651D0115; Tue, 05 Feb 2013 09:31:02 +0000 X-Env-Sender: Ian.Campbell@citrix.com X-Msg-Ref: server-16.tower-174.messagelabs.com!1360056659!30892948!1 X-Originating-IP: [46.33.159.39] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNDYuMzMuMTU5LjM5ID0+IDIwODEx\n X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 3877 invoked from network); 5 Feb 2013 09:31:00 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (46.33.159.39) by server-16.tower-174.messagelabs.com with RC4-SHA encrypted SMTP; 5 Feb 2013 09:31:00 -0000 X-IronPort-AV: E=Sophos;i="4.84,602,1355097600"; d="scan'208";a="1145730" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 05 Feb 2013 09:31:00 +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.297.1; Tue, 5 Feb 2013 09:30:59 +0000 Message-ID: <1360056658.7743.88.camel@zakaz.uk.xensource.com> From: Ian Campbell To: Matthias Date: Tue, 5 Feb 2013 09:30:58 +0000 In-Reply-To: References: <1359369167.6559.46.camel@zakaz.uk.xensource.com> <1359980575.7466.5.camel@zakaz.uk.xensource.com> Organization: Citrix Systems, Inc. X-Mailer: Evolution 3.4.4-1 MIME-Version: 1.0 Cc: "xen-users@lists.xen.org" Subject: Re: [Xen-users] xl nat and wrong IPs X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: 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, 2013-02-04 at 21:28 +0000, Matthias wrote: > I guess i finally understood the basic idea of the nat script: > > You set an IP for the vif interface. This will not be the IP of the > interface, but the IP the domU will be using internally. This way if > the dom0 receives a package for the configured IP, it will be routed > through the dom0-interface to the domU. (In detail: This way the > package goes into the iptables forward chain and not the input chain, > changing the hosts general treatment of the package). > > So not setting the interface to the configured IP but only creating an > ip route makes perfect sense. Is an IP on the vifX.Y device not required in order to route to it? And does that IP not need to differ from the one on the guests eth0 device? (otherwise the packet will get delivered to dom0) In the routing variant we use the IP address of dom0's own interface on all of the vifX.Y devices, I wonder why this doesn't suffice for NAT. > But then the vif-nat script assignes an IP+127 to the interface. This > creates 2 problems in my opinion: > > 1) When using the dom0 for routing network traffic from one domU to an > other, so basically using the dom0 as a network cable, the src > attribute used in the routing creation will alter the source ip > address from one domU to the ip+127 address which is, at least in my > network setup, pretty annoying. > > So if you got domUs A (IP 10.0.0.1) and B (IP 10.0.0.2) and send > traffic from A to B, B will see the traffic coming from 10.0.0.128 > instead of .1 . Isn't this an expected property of NAT? When communicating with off box hosts/VMs the IP address would be dom0's IP address. Sounds like you might actually want a nat'ed brouter type configuration? (i.e. the guests are bridged but offbox traffic is nat'ed) > 2) I haven't tested it, but I don't really know what would happen if > you set IPs >128 in the domU configuration and this way create > out-of-bounce routing IPs. I suspect this is probably a case of "don't do that". > Well, I think that most people don't use the nat feature of xen and > this isn't tested much.. But somebody might want to look at it at a > given point of time... It's certainly not the most widely used configuration. > For me, changing the IP setting lines to > > do_or_die ip addr add "0.0.0.0" dev "${dev}" > do_or_die ip route add "$vif_ip" dev "${dev}" > > This doesn't set an IP to the interface in the domU and no src. > attribute to the route, fixing the above issues.. Might be worth > thinkin about including in xen main line, i don't really know.. Me neither. > Posted this only if somebody might need this later.. Thanks. Ian. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Tue Feb 05 09:43:56 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 05 Feb 2013 09:43: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 1U2f3G-0006C7-1E; Tue, 05 Feb 2013 09:42:54 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U2f3E-0006C2-OL for xen-users@lists.xen.org; Tue, 05 Feb 2013 09:42:52 +0000 Received: from [193.109.254.147:7916] by server-4.bemta-14.messagelabs.com id D7/02-20719-C14D0115; Tue, 05 Feb 2013 09:42:52 +0000 X-Env-Sender: Ian.Campbell@citrix.com X-Msg-Ref: server-11.tower-27.messagelabs.com!1360057336!1750085!1 X-Originating-IP: [46.33.159.39] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNDYuMzMuMTU5LjM5ID0+IDIwODEx\n X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 25555 invoked from network); 5 Feb 2013 09:42:16 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (46.33.159.39) by server-11.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 5 Feb 2013 09:42:16 -0000 X-IronPort-AV: E=Sophos;i="4.84,602,1355097600"; d="scan'208";a="1146325" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 05 Feb 2013 09:42: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.297.1; Tue, 5 Feb 2013 09:42:15 +0000 Message-ID: <1360057333.17017.6.camel@zakaz.uk.xensource.com> From: Ian Campbell To: Stephen Kent Date: Tue, 5 Feb 2013 09:42:13 +0000 In-Reply-To: References: Organization: Citrix Systems, Inc. X-Mailer: Evolution 3.4.4-1 MIME-Version: 1.0 Cc: Rushikesh Jadhav <2rushikeshj@gmail.com>, "xen-users@lists.xen.org" Subject: Re: [Xen-users] XENBUS: Timeout connecting to device: device/vbd/51712 (local state 3, remote state 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 Tue, 2013-02-05 at 03:53 +0000, Stephen Kent wrote: > It turns out /dev/xvda is the wrong type of disk specifier, just using > "xvda" is correct instead. > > > However, I'm still having issues attaching my virtual disks. If I > manually run losetup /dev/loop1 /home/data/xen/megatron/root.img, and > then attach phy:/dev/loop1 in my dom0, /dev/xvda appears and I can > mount it. But, if I try to boot my domU with phy:/dev/loop1 instead of > the file path, it just enters a reboot loop. On my dom0, when I try to > xl block-attach the file directly (without a loop device), the command > appears to succeed and xl block-list shows the device, but /dev/xvda > is not created and nothing about xvda shows up in dmesg. > > > It seems like the file backend driver in my dom0 is broken. Does this > make sense to anyone? Do you know which backend is being used? If you look in Xenstore you should see nodes for the front and backend devices, please can you post those along with your full guest configuration. The complete guest dmesg might be useful as well. However you may want to switch back to file:// and debug that instead since phy:/dev/loop will use a different backend and isn't generally considered a safe configuration and didn't appear to be what you wanted in the first place anyway. > On Mon, Feb 4, 2013 at 5:37 PM, Stephen Kent > wrote: > I checked, PCI is enabled in both my dom0 and domU > kernels. I've enabled all the Xen drivers I can find > (including the block device frontend and backend > drivers). FWIW PCI is complete irrelevant to devices in a PV guest. Ian. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Tue Feb 05 09:43:56 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 05 Feb 2013 09:43: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 1U2f3G-0006C7-1E; Tue, 05 Feb 2013 09:42:54 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U2f3E-0006C2-OL for xen-users@lists.xen.org; Tue, 05 Feb 2013 09:42:52 +0000 Received: from [193.109.254.147:7916] by server-4.bemta-14.messagelabs.com id D7/02-20719-C14D0115; Tue, 05 Feb 2013 09:42:52 +0000 X-Env-Sender: Ian.Campbell@citrix.com X-Msg-Ref: server-11.tower-27.messagelabs.com!1360057336!1750085!1 X-Originating-IP: [46.33.159.39] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNDYuMzMuMTU5LjM5ID0+IDIwODEx\n X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 25555 invoked from network); 5 Feb 2013 09:42:16 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (46.33.159.39) by server-11.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 5 Feb 2013 09:42:16 -0000 X-IronPort-AV: E=Sophos;i="4.84,602,1355097600"; d="scan'208";a="1146325" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 05 Feb 2013 09:42: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.297.1; Tue, 5 Feb 2013 09:42:15 +0000 Message-ID: <1360057333.17017.6.camel@zakaz.uk.xensource.com> From: Ian Campbell To: Stephen Kent Date: Tue, 5 Feb 2013 09:42:13 +0000 In-Reply-To: References: Organization: Citrix Systems, Inc. X-Mailer: Evolution 3.4.4-1 MIME-Version: 1.0 Cc: Rushikesh Jadhav <2rushikeshj@gmail.com>, "xen-users@lists.xen.org" Subject: Re: [Xen-users] XENBUS: Timeout connecting to device: device/vbd/51712 (local state 3, remote state 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 Tue, 2013-02-05 at 03:53 +0000, Stephen Kent wrote: > It turns out /dev/xvda is the wrong type of disk specifier, just using > "xvda" is correct instead. > > > However, I'm still having issues attaching my virtual disks. If I > manually run losetup /dev/loop1 /home/data/xen/megatron/root.img, and > then attach phy:/dev/loop1 in my dom0, /dev/xvda appears and I can > mount it. But, if I try to boot my domU with phy:/dev/loop1 instead of > the file path, it just enters a reboot loop. On my dom0, when I try to > xl block-attach the file directly (without a loop device), the command > appears to succeed and xl block-list shows the device, but /dev/xvda > is not created and nothing about xvda shows up in dmesg. > > > It seems like the file backend driver in my dom0 is broken. Does this > make sense to anyone? Do you know which backend is being used? If you look in Xenstore you should see nodes for the front and backend devices, please can you post those along with your full guest configuration. The complete guest dmesg might be useful as well. However you may want to switch back to file:// and debug that instead since phy:/dev/loop will use a different backend and isn't generally considered a safe configuration and didn't appear to be what you wanted in the first place anyway. > On Mon, Feb 4, 2013 at 5:37 PM, Stephen Kent > wrote: > I checked, PCI is enabled in both my dom0 and domU > kernels. I've enabled all the Xen drivers I can find > (including the block device frontend and backend > drivers). FWIW PCI is complete irrelevant to devices in a PV guest. Ian. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Tue Feb 05 10:00:31 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 05 Feb 2013 10:00: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 1U2fJH-0006vX-LN; Tue, 05 Feb 2013 09:59:27 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U2fJF-0006vN-9I for xen-users@lists.xen.org; Tue, 05 Feb 2013 09:59:25 +0000 Received: from [85.158.138.51:23496] by server-1.bemta-3.messagelabs.com id DA/E9-08955-CF7D0115; Tue, 05 Feb 2013 09:59:24 +0000 X-Env-Sender: roger.pau@citrix.com X-Msg-Ref: server-14.tower-174.messagelabs.com!1360058349!22919138!1 X-Originating-IP: [46.33.159.39] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNDYuMzMuMTU5LjM5ID0+IDIwODEx\n X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 9711 invoked from network); 5 Feb 2013 09:59:10 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (46.33.159.39) by server-14.tower-174.messagelabs.com with RC4-SHA encrypted SMTP; 5 Feb 2013 09:59:10 -0000 X-IronPort-AV: E=Sophos;i="4.84,602,1355097600"; d="scan'208";a="1147100" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 05 Feb 2013 09:59:09 +0000 Received: from [192.168.1.30] (10.30.249.242) by LONPMAILMX01.citrite.net (10.30.203.162) with Microsoft SMTP Server id 8.3.297.1; Tue, 5 Feb 2013 09:59:09 +0000 Message-ID: <5110D7EC.8040608@citrix.com> Date: Tue, 5 Feb 2013 10:59:08 +0100 From: =?ISO-8859-1?Q?Roger_Pau_Monn=E9?= User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130107 Thunderbird/17.0.2 MIME-Version: 1.0 To: Yathindra References: <510DC655.5060205@cs.utah.edu> <510E3195.1010004@citrix.com> <510EA374.6060509@cs.utah.edu> In-Reply-To: <510EA374.6060509@cs.utah.edu> Cc: "xen-users@lists.xen.org" Subject: Re: [Xen-users] xen_blkbk times out before getting connected X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: 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 03/02/13 18:50, Yathindra wrote: > I'm using the latest linux kernel 3.8.0 with Xen 4.3-unstable. Xenstored > is being started at boot time. > I did not see any message (dmesg/syslog/console) about device being > plugged in but xenstore-ls shows me all > the entries backend and frontend. Could you post your DomU configuration file also? > Here are some details > ------------------------------ > From /var/log/syslog: > > Feb 3 10:37:31 localhost kernel: [ 36.466359] Event-channel device > installed. > Feb 3 10:37:31 localhost kernel: [ 36.636358] Register > xen_blkbk_driver <<< custom debug message I added > Feb 3 10:37:31 localhost kernel: [ 36.636367] > xenbus_register_backend <<< custom debug message I added > Feb 3 10:37:31 localhost kernel: [ 36.683533] xenbus_register_backend > Feb 3 10:37:31 localhost kernel: [ 36.830115] xen-pciback: backend is > vpci <<< custom debug message I added > Feb 3 10:37:31 localhost kernel: [ 36.830123] > xenbus_register_backend <<< custom debug message I added > Feb 3 10:37:32 localhost xenstored: Checking store ... > Feb 3 10:37:32 localhost xenstored: Checking store complete. > Feb 3 10:37:32 localhost kernel: [ 37.075217] xenbus_probe: xenstored > is ready <<< custom debug message I added > Feb 3 10:37:32 localhost kernel: [ 37.075230] watching node > FFFFFFFF81C7D1A0 > Feb 3 10:37:32 localhost kernel: [ 37.081309] xenbus_scanf for node cpu/0 > Feb 3 10:37:32 localhost kernel: [ 37.081327] XENBUS xen store gave: > unknown error cpu > Feb 3 10:37:32 localhost kernel: [ 37.081333] xenbus_scanf for node cpu/1 > Feb 3 10:37:32 localhost kernel: [ 37.085327] XENBUS unexpected type > [17], expected [2] > Feb 3 10:37:32 localhost kernel: [ 37.085342] watching node > FFFFFFFF81C7D0C0 > Feb 3 10:37:32 localhost kernel: [ 37.086857] XENBUS unexpected type > [17], expected [4] > Feb 3 10:37:32 localhost kernel: [ 37.086865] Failed to set shutdown > watcher > Feb 3 10:37:32 localhost kernel: [ 37.086880] backend_probe_and_watch > - enumerates devices in xenstore and watches for changes <<< custom > debug message I added > Feb 3 10:37:32 localhost kernel: [ 37.089401] XENBUS unexpected type > [4], expected [1] > Feb 3 10:37:32 localhost kernel: [ 37.089411] watching node > FFFFFFFF81C7D660 > Feb 3 10:37:32 localhost kernel: [ 37.090715] XENBUS xen store gave: > unknown error control/shutdown > Feb 3 10:37:32 localhost kernel: [ 37.090725] > frontend_probe_and_watch: calling xenbus_probe_devices <<< custom debug > message I added > Feb 3 10:37:32 localhost kernel: [ 37.092362] XENBUS unexpected type > [17], expected [1] > Feb 3 10:37:32 localhost kernel: [ 37.092376] watching node > FFFFFFFF81C7D820 > Feb 3 10:37:32 localhost kernel: [ 37.093334] watching node > FFFFFFFF81C7DB20 > Feb 3 10:37:32 localhost kernel: [ 37.094454] XENBUS xen store gave: > unknown error backend <<< still not sure how critical this is > Feb 3 10:37:32 localhost kernel: [ 37.094463] Failed to set balloon > watcher <<< still not sure how > critical this is > > > xenstore-ls > tool = "" > xenstored = "" > local = "" > domain = "" > 0 = "" > data = "" > meminfo_total = "930680" > meminfo_free = "691868" > os_name = "Ubuntu 12.04.1 LTS" > os_majorver = "12" > os_minorver = "04" > os_uname = "3.8.0-rc5+" > os_distro = "ubuntu" > updated = "Sun Feb 3 10:43:32 MST 2013" > name = "Domain-0" > attr = "" > xenbr0 = "" > ip = "155.98.39.2" > PVAddons = "" > MajorVersion = "5" > MinorVersion = "5" > MicroVersion = "0" > BuildVersion = "17913" > Installed = "1" > device-model = "" > 0 = "" > state = "running" > > After this I start the guest domain, here's the xenstore entries, > > nodea:~> sudo xenstore-ls > tool = "" > xenstored = "" > local = "" > domain = "" > 0 = "" > data = "" > meminfo_total = "930680" > meminfo_free = "695408" > os_name = "Ubuntu 12.04.1 LTS" > os_majorver = "12" > os_minorver = "04" > os_uname = "3.8.0-rc5+" > os_distro = "ubuntu" > updated = "Sun Feb 3 10:45:32 MST 2013" > name = "Domain-0" > attr = "" > xenbr0 = "" > ip = "155.98.39.2" > PVAddons = "" > MajorVersion = "5" > MinorVersion = "5" > MicroVersion = "0" > BuildVersion = "17913" > Installed = "1" > device-model = "" > 0 = "" > state = "running" > memory = "" > target = "1048576" > static-max = "4294967292" > freemem-slack = "314476" > libxl = "" > disable_udev = "1" > backend = "" > vbd = "" > 1 = "" > 2049 = "" > frontend = "/local/domain/1/device/vbd/2049" <<<< everything > seems to be enumerated > params = "/dev/loop0" > script = "/etc/xen/scripts/block" > physical-device = "7:0" > frontend-id = "1" > online = "1" > removable = "0" > bootable = "1" > state = "1" > dev = "sda1" > type = "phy" > mode = "w" > device-type = "disk" > 1 = "" > vm = "/vm/9b0dfb10-f69d-4e22-9158-bb70456ece2e" > name = "guest2" > cpu = "" > 0 = "" > availability = "online" > memory = "" > static-max = "512000" > target = "512001" > videoram = "-1" > device = "" > suspend = "" > event-channel = "" > vbd = "" > 2049 = "" > backend = "/local/domain/0/backend/vbd/1/2049" > backend-id = "0" > state = "1" <<<<< state changes to 5 and then after 5 secs it > times out > virtual-device = "2049" > device-type = "disk" > control = "" > shutdown = "" > platform-feature-multiprocessor-suspend = "1" > platform-feature-xs_reset_watches = "1" > data = "" > domid = "1" > store = "" > port = "1" > ring-ref = "156845" > vm = "" > 9b0dfb10-f69d-4e22-9158-bb70456ece2e = "" > uuid = "9b0dfb10-f69d-4e22-9158-bb70456ece2e" > name = "guest2" > image = "" > ostype = "linux" > kernel = "/boot/vmlinuz-3.8.0-rc5+" > ramdisk = "/boot/initrd.img-3.8.0-rc5+" > cmdline = "root=/dev/disk/by-path/xen-vbd-2049 ro xencons=tty" > start_time = "1359913591.67" > libxl = "" > 1 = "" > dm-version = "qemu_xen" > > Thanks, > Yathi _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Tue Feb 05 10:00:31 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 05 Feb 2013 10:00: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 1U2fJH-0006vX-LN; Tue, 05 Feb 2013 09:59:27 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U2fJF-0006vN-9I for xen-users@lists.xen.org; Tue, 05 Feb 2013 09:59:25 +0000 Received: from [85.158.138.51:23496] by server-1.bemta-3.messagelabs.com id DA/E9-08955-CF7D0115; Tue, 05 Feb 2013 09:59:24 +0000 X-Env-Sender: roger.pau@citrix.com X-Msg-Ref: server-14.tower-174.messagelabs.com!1360058349!22919138!1 X-Originating-IP: [46.33.159.39] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNDYuMzMuMTU5LjM5ID0+IDIwODEx\n X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 9711 invoked from network); 5 Feb 2013 09:59:10 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (46.33.159.39) by server-14.tower-174.messagelabs.com with RC4-SHA encrypted SMTP; 5 Feb 2013 09:59:10 -0000 X-IronPort-AV: E=Sophos;i="4.84,602,1355097600"; d="scan'208";a="1147100" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 05 Feb 2013 09:59:09 +0000 Received: from [192.168.1.30] (10.30.249.242) by LONPMAILMX01.citrite.net (10.30.203.162) with Microsoft SMTP Server id 8.3.297.1; Tue, 5 Feb 2013 09:59:09 +0000 Message-ID: <5110D7EC.8040608@citrix.com> Date: Tue, 5 Feb 2013 10:59:08 +0100 From: =?ISO-8859-1?Q?Roger_Pau_Monn=E9?= User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130107 Thunderbird/17.0.2 MIME-Version: 1.0 To: Yathindra References: <510DC655.5060205@cs.utah.edu> <510E3195.1010004@citrix.com> <510EA374.6060509@cs.utah.edu> In-Reply-To: <510EA374.6060509@cs.utah.edu> Cc: "xen-users@lists.xen.org" Subject: Re: [Xen-users] xen_blkbk times out before getting connected X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: 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 03/02/13 18:50, Yathindra wrote: > I'm using the latest linux kernel 3.8.0 with Xen 4.3-unstable. Xenstored > is being started at boot time. > I did not see any message (dmesg/syslog/console) about device being > plugged in but xenstore-ls shows me all > the entries backend and frontend. Could you post your DomU configuration file also? > Here are some details > ------------------------------ > From /var/log/syslog: > > Feb 3 10:37:31 localhost kernel: [ 36.466359] Event-channel device > installed. > Feb 3 10:37:31 localhost kernel: [ 36.636358] Register > xen_blkbk_driver <<< custom debug message I added > Feb 3 10:37:31 localhost kernel: [ 36.636367] > xenbus_register_backend <<< custom debug message I added > Feb 3 10:37:31 localhost kernel: [ 36.683533] xenbus_register_backend > Feb 3 10:37:31 localhost kernel: [ 36.830115] xen-pciback: backend is > vpci <<< custom debug message I added > Feb 3 10:37:31 localhost kernel: [ 36.830123] > xenbus_register_backend <<< custom debug message I added > Feb 3 10:37:32 localhost xenstored: Checking store ... > Feb 3 10:37:32 localhost xenstored: Checking store complete. > Feb 3 10:37:32 localhost kernel: [ 37.075217] xenbus_probe: xenstored > is ready <<< custom debug message I added > Feb 3 10:37:32 localhost kernel: [ 37.075230] watching node > FFFFFFFF81C7D1A0 > Feb 3 10:37:32 localhost kernel: [ 37.081309] xenbus_scanf for node cpu/0 > Feb 3 10:37:32 localhost kernel: [ 37.081327] XENBUS xen store gave: > unknown error cpu > Feb 3 10:37:32 localhost kernel: [ 37.081333] xenbus_scanf for node cpu/1 > Feb 3 10:37:32 localhost kernel: [ 37.085327] XENBUS unexpected type > [17], expected [2] > Feb 3 10:37:32 localhost kernel: [ 37.085342] watching node > FFFFFFFF81C7D0C0 > Feb 3 10:37:32 localhost kernel: [ 37.086857] XENBUS unexpected type > [17], expected [4] > Feb 3 10:37:32 localhost kernel: [ 37.086865] Failed to set shutdown > watcher > Feb 3 10:37:32 localhost kernel: [ 37.086880] backend_probe_and_watch > - enumerates devices in xenstore and watches for changes <<< custom > debug message I added > Feb 3 10:37:32 localhost kernel: [ 37.089401] XENBUS unexpected type > [4], expected [1] > Feb 3 10:37:32 localhost kernel: [ 37.089411] watching node > FFFFFFFF81C7D660 > Feb 3 10:37:32 localhost kernel: [ 37.090715] XENBUS xen store gave: > unknown error control/shutdown > Feb 3 10:37:32 localhost kernel: [ 37.090725] > frontend_probe_and_watch: calling xenbus_probe_devices <<< custom debug > message I added > Feb 3 10:37:32 localhost kernel: [ 37.092362] XENBUS unexpected type > [17], expected [1] > Feb 3 10:37:32 localhost kernel: [ 37.092376] watching node > FFFFFFFF81C7D820 > Feb 3 10:37:32 localhost kernel: [ 37.093334] watching node > FFFFFFFF81C7DB20 > Feb 3 10:37:32 localhost kernel: [ 37.094454] XENBUS xen store gave: > unknown error backend <<< still not sure how critical this is > Feb 3 10:37:32 localhost kernel: [ 37.094463] Failed to set balloon > watcher <<< still not sure how > critical this is > > > xenstore-ls > tool = "" > xenstored = "" > local = "" > domain = "" > 0 = "" > data = "" > meminfo_total = "930680" > meminfo_free = "691868" > os_name = "Ubuntu 12.04.1 LTS" > os_majorver = "12" > os_minorver = "04" > os_uname = "3.8.0-rc5+" > os_distro = "ubuntu" > updated = "Sun Feb 3 10:43:32 MST 2013" > name = "Domain-0" > attr = "" > xenbr0 = "" > ip = "155.98.39.2" > PVAddons = "" > MajorVersion = "5" > MinorVersion = "5" > MicroVersion = "0" > BuildVersion = "17913" > Installed = "1" > device-model = "" > 0 = "" > state = "running" > > After this I start the guest domain, here's the xenstore entries, > > nodea:~> sudo xenstore-ls > tool = "" > xenstored = "" > local = "" > domain = "" > 0 = "" > data = "" > meminfo_total = "930680" > meminfo_free = "695408" > os_name = "Ubuntu 12.04.1 LTS" > os_majorver = "12" > os_minorver = "04" > os_uname = "3.8.0-rc5+" > os_distro = "ubuntu" > updated = "Sun Feb 3 10:45:32 MST 2013" > name = "Domain-0" > attr = "" > xenbr0 = "" > ip = "155.98.39.2" > PVAddons = "" > MajorVersion = "5" > MinorVersion = "5" > MicroVersion = "0" > BuildVersion = "17913" > Installed = "1" > device-model = "" > 0 = "" > state = "running" > memory = "" > target = "1048576" > static-max = "4294967292" > freemem-slack = "314476" > libxl = "" > disable_udev = "1" > backend = "" > vbd = "" > 1 = "" > 2049 = "" > frontend = "/local/domain/1/device/vbd/2049" <<<< everything > seems to be enumerated > params = "/dev/loop0" > script = "/etc/xen/scripts/block" > physical-device = "7:0" > frontend-id = "1" > online = "1" > removable = "0" > bootable = "1" > state = "1" > dev = "sda1" > type = "phy" > mode = "w" > device-type = "disk" > 1 = "" > vm = "/vm/9b0dfb10-f69d-4e22-9158-bb70456ece2e" > name = "guest2" > cpu = "" > 0 = "" > availability = "online" > memory = "" > static-max = "512000" > target = "512001" > videoram = "-1" > device = "" > suspend = "" > event-channel = "" > vbd = "" > 2049 = "" > backend = "/local/domain/0/backend/vbd/1/2049" > backend-id = "0" > state = "1" <<<<< state changes to 5 and then after 5 secs it > times out > virtual-device = "2049" > device-type = "disk" > control = "" > shutdown = "" > platform-feature-multiprocessor-suspend = "1" > platform-feature-xs_reset_watches = "1" > data = "" > domid = "1" > store = "" > port = "1" > ring-ref = "156845" > vm = "" > 9b0dfb10-f69d-4e22-9158-bb70456ece2e = "" > uuid = "9b0dfb10-f69d-4e22-9158-bb70456ece2e" > name = "guest2" > image = "" > ostype = "linux" > kernel = "/boot/vmlinuz-3.8.0-rc5+" > ramdisk = "/boot/initrd.img-3.8.0-rc5+" > cmdline = "root=/dev/disk/by-path/xen-vbd-2049 ro xencons=tty" > start_time = "1359913591.67" > libxl = "" > 1 = "" > dm-version = "qemu_xen" > > Thanks, > Yathi _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Tue Feb 05 11:49:32 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 05 Feb 2013 11:49: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 1U2h0q-0004NV-8J; Tue, 05 Feb 2013 11:48:32 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U2h0p-0004NH-6w for xen-users@lists.xen.org; Tue, 05 Feb 2013 11:48:31 +0000 Received: from [85.158.143.35:55075] by server-3.bemta-4.messagelabs.com id 98/D5-08920-E81F0115; Tue, 05 Feb 2013 11:48:30 +0000 X-Env-Sender: thore@datensumpf.de X-Msg-Ref: server-12.tower-21.messagelabs.com!1360064764!13057272!1 X-Originating-IP: [212.12.52.213] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 31256 invoked from network); 5 Feb 2013 11:46:05 -0000 Received: from mail-2.ramdrive.org (HELO mail-2.ramdrive.org) (212.12.52.213) by server-12.tower-21.messagelabs.com with SMTP; 5 Feb 2013 11:46:05 -0000 Received: from localhost (localhost [127.0.0.1]) by mail-2.ramdrive.org (Postfix) with ESMTP id 90922783DFBA for ; Tue, 5 Feb 2013 11:55:14 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at mail-2.ramdrive.org Received: from mail-2.ramdrive.org ([127.0.0.1]) by localhost (mail-2.ramdrive.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yACdyq2bHM-P for ; Tue, 5 Feb 2013 11:55:14 +0000 (UTC) Received: from [127.0.0.1] (f054048114.adsl.alicedsl.de [78.54.48.114]) by mail-2.ramdrive.org (Postfix) with ESMTPSA id C0E05783DBBC for ; Tue, 5 Feb 2013 11:55:13 +0000 (UTC) Message-ID: <5110F0F9.6080204@datensumpf.de> Date: Tue, 05 Feb 2013 12:46:01 +0100 From: Thore User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130107 Thunderbird/17.0.2 MIME-Version: 1.0 To: xen-users@lists.xen.org Subject: [Xen-users] Using Ipv4 and IPv6 Subnet X-BeenThere: xen-users@lists.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 List, I have a problem/question for understanding. I have on my server (debian wheezy) 3 virtual systems running on xen with own IPv4 addresses. Form my hoster I got an IPv6 subnet, but I don't really know how to add it. Is it enought to add an address of it in the /etc/network/interfaces of the virtual systems? Or must I set up routing for Xen and how does it works together with bridging? Which settings I had to change? And am I able to set up an system only with Ipv6? (I have IPv6) Hopefully that you can help me. Regards Thore _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Tue Feb 05 11:49:32 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 05 Feb 2013 11:49: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 1U2h0q-0004NV-8J; Tue, 05 Feb 2013 11:48:32 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U2h0p-0004NH-6w for xen-users@lists.xen.org; Tue, 05 Feb 2013 11:48:31 +0000 Received: from [85.158.143.35:55075] by server-3.bemta-4.messagelabs.com id 98/D5-08920-E81F0115; Tue, 05 Feb 2013 11:48:30 +0000 X-Env-Sender: thore@datensumpf.de X-Msg-Ref: server-12.tower-21.messagelabs.com!1360064764!13057272!1 X-Originating-IP: [212.12.52.213] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 31256 invoked from network); 5 Feb 2013 11:46:05 -0000 Received: from mail-2.ramdrive.org (HELO mail-2.ramdrive.org) (212.12.52.213) by server-12.tower-21.messagelabs.com with SMTP; 5 Feb 2013 11:46:05 -0000 Received: from localhost (localhost [127.0.0.1]) by mail-2.ramdrive.org (Postfix) with ESMTP id 90922783DFBA for ; Tue, 5 Feb 2013 11:55:14 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at mail-2.ramdrive.org Received: from mail-2.ramdrive.org ([127.0.0.1]) by localhost (mail-2.ramdrive.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yACdyq2bHM-P for ; Tue, 5 Feb 2013 11:55:14 +0000 (UTC) Received: from [127.0.0.1] (f054048114.adsl.alicedsl.de [78.54.48.114]) by mail-2.ramdrive.org (Postfix) with ESMTPSA id C0E05783DBBC for ; Tue, 5 Feb 2013 11:55:13 +0000 (UTC) Message-ID: <5110F0F9.6080204@datensumpf.de> Date: Tue, 05 Feb 2013 12:46:01 +0100 From: Thore User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130107 Thunderbird/17.0.2 MIME-Version: 1.0 To: xen-users@lists.xen.org Subject: [Xen-users] Using Ipv4 and IPv6 Subnet X-BeenThere: xen-users@lists.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 List, I have a problem/question for understanding. I have on my server (debian wheezy) 3 virtual systems running on xen with own IPv4 addresses. Form my hoster I got an IPv6 subnet, but I don't really know how to add it. Is it enought to add an address of it in the /etc/network/interfaces of the virtual systems? Or must I set up routing for Xen and how does it works together with bridging? Which settings I had to change? And am I able to set up an system only with Ipv6? (I have IPv6) Hopefully that you can help me. Regards Thore _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Tue Feb 05 12:33:43 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 05 Feb 2013 12:33: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 1U2hhI-0005eX-9I; Tue, 05 Feb 2013 12:32:24 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U2hhG-0005eO-IL for xen-users@lists.xen.org; Tue, 05 Feb 2013 12:32:22 +0000 Received: from [193.109.254.147:29912] by server-13.bemta-14.messagelabs.com id 5F/68-30639-5DBF0115; Tue, 05 Feb 2013 12:32:21 +0000 X-Env-Sender: stephane.gaudiche@laposte.net X-Msg-Ref: server-9.tower-27.messagelabs.com!1360067541!9608973!1 X-Originating-IP: [193.253.67.230] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogMTkzLjI1My42Ny4yMzAgPT4gMjU1OTI=\n, ML_RADAR_SPEW_LINKS_14,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 9060 invoked from network); 5 Feb 2013 12:32:21 -0000 Received: from smtpout5.laposte.net (HELO smtpout.laposte.net) (193.253.67.230) by server-9.tower-27.messagelabs.com with SMTP; 5 Feb 2013 12:32:21 -0000 Received: from wwinf8222 ([10.99.54.223]) by mwinf8509-out with ME id wcYL1k00C4oxRQS03cYLhM; Tue, 05 Feb 2013 13:32:20 +0100 Date: Tue, 05 Feb 2013 13:32:20 +0100 From: =?UTF-8?Q?St=C3=A9phane_GAUDICHE?= To: xen-users@lists.xen.org Message-ID: <53320663.1650816.1360067540703.JavaMail.www@wwinf8222> In-Reply-To: <1550996225.104330.1359653797051.JavaMail.www@wwinf8306> References: <1550996225.104330.1359653797051.JavaMail.www@wwinf8306> MIME-Version: 1.0 X-Originating-IP: [91.212.128.130] X-Wum-Nature: EMAIL-NATURE X-WUM-FROM: |~| X-WUM-TO: |~| X-WUM-REPLYTO: |~| Subject: Re: [Xen-users] Xen LVM reducing HVM MS Windows guest disk X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: =?UTF-8?Q?St=C3=A9phane_GAUDICHE?= List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============6805482792595592400==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============6805482792595592400== Content-Type: multipart/alternative; boundary="----=_Part_1650815_173008043.1360067540703" ------=_Part_1650815_173008043.1360067540703 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Does anybody read me? > Message du 31/01/13 18:40 > De : "St=C3=A9phane GAUDICHE" > A : xen-users@lists.xen.org > Copie =C3=A0 : > Objet : [Xen-users] Xen LVM reducing HVM MS Windows guest disk > > Hello list, I run xen 4.0 on a debian squeeze host with local lvm2 storage I've got HVM VMs (Microsoft Windows) with 2 drives (c: [OS] & D: [Data]), f= ile system: NTFS I want to reduce the size of the D: drive of my HVMs. By reading several articles and howtos across web, 1- I backup datas first outside the XenHost 2- then from MSWindows guest-OS, I managed to live-reduce the partition's s= ize on the D: drive (from 150G to 50G) with the embedded tool "diskpart": "= shrink" operator, it worked just fine. 3- I power off the HVM. Now, from xen point of view, i got a Logical Volume called data_HVM_microso= ft.img of (steal) 150G. 4- I was expecting to do an "lvreduce" to reduce the logical volume (the bo= x) to 100G only but what happen to the filesystem (contenant in the box),which is seen as a= D: drive from the HVM with a small 50G NTFS partition from now) Do I care about it? I note that the logical volume were seen as Block-device from xen host file= -system (not sure, but i guess it quite nomal due to LVM). then 5-check lv 6-power on HVM 7-extend D: drive to 100G Can anyone help to understand if am I right by following these step? Une messagerie gratuite, garantie =C3=A0 vie et des services en plus, =C3= =A7a vous tente ? Je cr=C3=A9e ma bo=C3=AEte mail www.laposte.net ------=_Part_1650815_173008043.1360067540703 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

Does anybody read me?
=


> Message du 31/01/13 18:40
> De : &qu= ot;Stéphane GAUDICHE"
> A : xen-users@lists.xen.org> Copie à :
> Objet : [Xen-users] Xen LVM reducing HV= M MS Windows guest disk
>
>

Hello list,

I run xen 4.0 on a debian squ= eeze host with local lvm2 storage
I've got HVM VMs (Microsoft Windows)= with 2 drives (c: [OS] & D: [Data]), file system: NTFS
I want to = reduce the size of the D: drive of my HVMs.

By reading several a= rticles and howtos across web,
1- I backup datas first outside the Xen= Host
2- then from MSWindows guest-OS, I managed to live-reduce the par= tition's size on the D: drive (from 150G to 50G) with the embedded tool &q= uot;diskpart": "shrink" operator, it worked just fine.
= 3- I power off the HVM.
Now, from xen point of view, i got a Logical V= olume called data_HVM_microsoft.img of (steal) 150G.
4- I was expectin= g to do an "lvreduce" to reduce the logical volume (the box) to 1= 00G only
but what happen to the filesystem (contenant in the box),whic= h is seen as a D: drive from the HVM with a small 50G NTFS partition from n= ow)
Do I care about it?
I note that the logical volume were seen = as Block-device from xen host file-system (not sure, but i guess it quite n= omal due to LVM).
then
5-check lv
6-power on HVM
7-exte= nd D: drive to 100G
Can anyone help to understand if am I right by fol= lowing these step?




3D"" ------=_Part_1650815_173008043.1360067540703-- --===============6805482792595592400== 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 --===============6805482792595592400==-- From xen-users-bounces@lists.xen.org Tue Feb 05 12:33:43 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 05 Feb 2013 12:33: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 1U2hhI-0005eX-9I; Tue, 05 Feb 2013 12:32:24 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U2hhG-0005eO-IL for xen-users@lists.xen.org; Tue, 05 Feb 2013 12:32:22 +0000 Received: from [193.109.254.147:29912] by server-13.bemta-14.messagelabs.com id 5F/68-30639-5DBF0115; Tue, 05 Feb 2013 12:32:21 +0000 X-Env-Sender: stephane.gaudiche@laposte.net X-Msg-Ref: server-9.tower-27.messagelabs.com!1360067541!9608973!1 X-Originating-IP: [193.253.67.230] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogMTkzLjI1My42Ny4yMzAgPT4gMjU1OTI=\n, ML_RADAR_SPEW_LINKS_14,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 9060 invoked from network); 5 Feb 2013 12:32:21 -0000 Received: from smtpout5.laposte.net (HELO smtpout.laposte.net) (193.253.67.230) by server-9.tower-27.messagelabs.com with SMTP; 5 Feb 2013 12:32:21 -0000 Received: from wwinf8222 ([10.99.54.223]) by mwinf8509-out with ME id wcYL1k00C4oxRQS03cYLhM; Tue, 05 Feb 2013 13:32:20 +0100 Date: Tue, 05 Feb 2013 13:32:20 +0100 From: =?UTF-8?Q?St=C3=A9phane_GAUDICHE?= To: xen-users@lists.xen.org Message-ID: <53320663.1650816.1360067540703.JavaMail.www@wwinf8222> In-Reply-To: <1550996225.104330.1359653797051.JavaMail.www@wwinf8306> References: <1550996225.104330.1359653797051.JavaMail.www@wwinf8306> MIME-Version: 1.0 X-Originating-IP: [91.212.128.130] X-Wum-Nature: EMAIL-NATURE X-WUM-FROM: |~| X-WUM-TO: |~| X-WUM-REPLYTO: |~| Subject: Re: [Xen-users] Xen LVM reducing HVM MS Windows guest disk X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: =?UTF-8?Q?St=C3=A9phane_GAUDICHE?= List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============6805482792595592400==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============6805482792595592400== Content-Type: multipart/alternative; boundary="----=_Part_1650815_173008043.1360067540703" ------=_Part_1650815_173008043.1360067540703 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Does anybody read me? > Message du 31/01/13 18:40 > De : "St=C3=A9phane GAUDICHE" > A : xen-users@lists.xen.org > Copie =C3=A0 : > Objet : [Xen-users] Xen LVM reducing HVM MS Windows guest disk > > Hello list, I run xen 4.0 on a debian squeeze host with local lvm2 storage I've got HVM VMs (Microsoft Windows) with 2 drives (c: [OS] & D: [Data]), f= ile system: NTFS I want to reduce the size of the D: drive of my HVMs. By reading several articles and howtos across web, 1- I backup datas first outside the XenHost 2- then from MSWindows guest-OS, I managed to live-reduce the partition's s= ize on the D: drive (from 150G to 50G) with the embedded tool "diskpart": "= shrink" operator, it worked just fine. 3- I power off the HVM. Now, from xen point of view, i got a Logical Volume called data_HVM_microso= ft.img of (steal) 150G. 4- I was expecting to do an "lvreduce" to reduce the logical volume (the bo= x) to 100G only but what happen to the filesystem (contenant in the box),which is seen as a= D: drive from the HVM with a small 50G NTFS partition from now) Do I care about it? I note that the logical volume were seen as Block-device from xen host file= -system (not sure, but i guess it quite nomal due to LVM). then 5-check lv 6-power on HVM 7-extend D: drive to 100G Can anyone help to understand if am I right by following these step? Une messagerie gratuite, garantie =C3=A0 vie et des services en plus, =C3= =A7a vous tente ? Je cr=C3=A9e ma bo=C3=AEte mail www.laposte.net ------=_Part_1650815_173008043.1360067540703 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

Does anybody read me?
=


> Message du 31/01/13 18:40
> De : &qu= ot;Stéphane GAUDICHE"
> A : xen-users@lists.xen.org> Copie à :
> Objet : [Xen-users] Xen LVM reducing HV= M MS Windows guest disk
>
>

Hello list,

I run xen 4.0 on a debian squ= eeze host with local lvm2 storage
I've got HVM VMs (Microsoft Windows)= with 2 drives (c: [OS] & D: [Data]), file system: NTFS
I want to = reduce the size of the D: drive of my HVMs.

By reading several a= rticles and howtos across web,
1- I backup datas first outside the Xen= Host
2- then from MSWindows guest-OS, I managed to live-reduce the par= tition's size on the D: drive (from 150G to 50G) with the embedded tool &q= uot;diskpart": "shrink" operator, it worked just fine.
= 3- I power off the HVM.
Now, from xen point of view, i got a Logical V= olume called data_HVM_microsoft.img of (steal) 150G.
4- I was expectin= g to do an "lvreduce" to reduce the logical volume (the box) to 1= 00G only
but what happen to the filesystem (contenant in the box),whic= h is seen as a D: drive from the HVM with a small 50G NTFS partition from n= ow)
Do I care about it?
I note that the logical volume were seen = as Block-device from xen host file-system (not sure, but i guess it quite n= omal due to LVM).
then
5-check lv
6-power on HVM
7-exte= nd D: drive to 100G
Can anyone help to understand if am I right by fol= lowing these step?




3D"" ------=_Part_1650815_173008043.1360067540703-- --===============6805482792595592400== 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 --===============6805482792595592400==-- From xen-users-bounces@lists.xen.org Tue Feb 05 12:39:03 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 05 Feb 2013 12:39: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 1U2hms-0005wq-NE; Tue, 05 Feb 2013 12:38:10 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U2hmr-0005wd-NA for xen-users@lists.xen.org; Tue, 05 Feb 2013 12:38:09 +0000 Received: from [85.158.143.35:60350] by server-2.bemta-4.messagelabs.com id EA/D3-01597-13DF0115; Tue, 05 Feb 2013 12:38:09 +0000 X-Env-Sender: digvijaych@gmail.com X-Msg-Ref: server-12.tower-21.messagelabs.com!1360067885!13063728!1 X-Originating-IP: [209.85.217.172] 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.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 16068 invoked from network); 5 Feb 2013 12:38:06 -0000 Received: from mail-lb0-f172.google.com (HELO mail-lb0-f172.google.com) (209.85.217.172) by server-12.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 5 Feb 2013 12:38:06 -0000 Received: by mail-lb0-f172.google.com with SMTP id n8so179456lbj.31 for ; Tue, 05 Feb 2013 04:38:05 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:date:message-id:subject:from:to :content-type; bh=bZEbyjRZQFsIvZLS7vMFHafcVkOiEl6+5awE3p7XoNI=; b=X6IODBNKoRyBIBRlr8ubfcb/GTqIL3ohIlUhzVIDXI0bf7PFY8rA4Z/QjOIdVIpAp8 +ehrQ76d2U5l1gxz9r+RMi/qae24tU/TEEBMLt/kQX2M+svmSpRLM1/W5luEVpUaVUQT zue83hw/a6RjGP5DKW9cON19E5WxnEuWFTTs7xsHDenZ3NVMbGr4WfkCoqdFszinrf0C zWH4K/0EXHVkYCVKI0Z+GBCHvWNhf8ZHNJkw2jre3o/HvPLM/wSQy8aKDF+ZRF7WLi7i 7VifR9/EUUV4Vl+JLz6zKfz5zke7csIKRwfZ81Y+jC8bVoeYXH67AUtJLMuOk+xr0+MV j8Ow== MIME-Version: 1.0 X-Received: by 10.112.36.165 with SMTP id r5mr9762833lbj.112.1360067885404; Tue, 05 Feb 2013 04:38:05 -0800 (PST) Received: by 10.112.79.37 with HTTP; Tue, 5 Feb 2013 04:38:05 -0800 (PST) Date: Tue, 5 Feb 2013 18:08:05 +0530 Message-ID: From: digvijay chauhan To: xen-devel@lists.xensource.com, xen-users@lists.xen.org Subject: [Xen-users] What parameters to evaluate during live migration X-BeenThere: xen-users@lists.xen.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="===============5058106718974899986==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============5058106718974899986== Content-Type: multipart/alternative; boundary=e0cb4efe30bc2e115604d4f97b9e --e0cb4efe30bc2e115604d4f97b9e Content-Type: text/plain; charset=ISO-8859-1 Hello i am trying on live migration of vm using xen,bt during migration what parameters can be evaluated and which tool will be used in that ? I mean like memory performance ,disk,cpu performance etc.how can we measure? regards, digvijaysingh --e0cb4efe30bc2e115604d4f97b9e Content-Type: text/html; charset=ISO-8859-1 Hello i am trying on live migration of vm using xen,bt during migration what parameters can be evaluated and which tool will be used in that ?

I mean like memory performance ,disk,cpu performance etc.how can we measure?

regards,
digvijaysingh

--e0cb4efe30bc2e115604d4f97b9e-- --===============5058106718974899986== 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 --===============5058106718974899986==-- From xen-users-bounces@lists.xen.org Tue Feb 05 12:39:03 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 05 Feb 2013 12:39: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 1U2hms-0005wq-NE; Tue, 05 Feb 2013 12:38:10 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U2hmr-0005wd-NA for xen-users@lists.xen.org; Tue, 05 Feb 2013 12:38:09 +0000 Received: from [85.158.143.35:60350] by server-2.bemta-4.messagelabs.com id EA/D3-01597-13DF0115; Tue, 05 Feb 2013 12:38:09 +0000 X-Env-Sender: digvijaych@gmail.com X-Msg-Ref: server-12.tower-21.messagelabs.com!1360067885!13063728!1 X-Originating-IP: [209.85.217.172] 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.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 16068 invoked from network); 5 Feb 2013 12:38:06 -0000 Received: from mail-lb0-f172.google.com (HELO mail-lb0-f172.google.com) (209.85.217.172) by server-12.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 5 Feb 2013 12:38:06 -0000 Received: by mail-lb0-f172.google.com with SMTP id n8so179456lbj.31 for ; Tue, 05 Feb 2013 04:38:05 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:date:message-id:subject:from:to :content-type; bh=bZEbyjRZQFsIvZLS7vMFHafcVkOiEl6+5awE3p7XoNI=; b=X6IODBNKoRyBIBRlr8ubfcb/GTqIL3ohIlUhzVIDXI0bf7PFY8rA4Z/QjOIdVIpAp8 +ehrQ76d2U5l1gxz9r+RMi/qae24tU/TEEBMLt/kQX2M+svmSpRLM1/W5luEVpUaVUQT zue83hw/a6RjGP5DKW9cON19E5WxnEuWFTTs7xsHDenZ3NVMbGr4WfkCoqdFszinrf0C zWH4K/0EXHVkYCVKI0Z+GBCHvWNhf8ZHNJkw2jre3o/HvPLM/wSQy8aKDF+ZRF7WLi7i 7VifR9/EUUV4Vl+JLz6zKfz5zke7csIKRwfZ81Y+jC8bVoeYXH67AUtJLMuOk+xr0+MV j8Ow== MIME-Version: 1.0 X-Received: by 10.112.36.165 with SMTP id r5mr9762833lbj.112.1360067885404; Tue, 05 Feb 2013 04:38:05 -0800 (PST) Received: by 10.112.79.37 with HTTP; Tue, 5 Feb 2013 04:38:05 -0800 (PST) Date: Tue, 5 Feb 2013 18:08:05 +0530 Message-ID: From: digvijay chauhan To: xen-devel@lists.xensource.com, xen-users@lists.xen.org Subject: [Xen-users] What parameters to evaluate during live migration X-BeenThere: xen-users@lists.xen.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="===============5058106718974899986==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============5058106718974899986== Content-Type: multipart/alternative; boundary=e0cb4efe30bc2e115604d4f97b9e --e0cb4efe30bc2e115604d4f97b9e Content-Type: text/plain; charset=ISO-8859-1 Hello i am trying on live migration of vm using xen,bt during migration what parameters can be evaluated and which tool will be used in that ? I mean like memory performance ,disk,cpu performance etc.how can we measure? regards, digvijaysingh --e0cb4efe30bc2e115604d4f97b9e Content-Type: text/html; charset=ISO-8859-1 Hello i am trying on live migration of vm using xen,bt during migration what parameters can be evaluated and which tool will be used in that ?

I mean like memory performance ,disk,cpu performance etc.how can we measure?

regards,
digvijaysingh

--e0cb4efe30bc2e115604d4f97b9e-- --===============5058106718974899986== 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 --===============5058106718974899986==-- From xen-users-bounces@lists.xen.org Tue Feb 05 12:48:19 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 05 Feb 2013 12:48: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 1U2hvp-0006XQ-1P; Tue, 05 Feb 2013 12:47:25 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U2hvn-0006XK-Nm for xen-users@lists.xen.org; Tue, 05 Feb 2013 12:47:23 +0000 Received: from [193.109.254.147:56746] by server-13.bemta-14.messagelabs.com id D6/5C-30639-A5FF0115; Tue, 05 Feb 2013 12:47:22 +0000 X-Env-Sender: Ian.Campbell@citrix.com X-Msg-Ref: server-9.tower-27.messagelabs.com!1360068432!9611318!1 X-Originating-IP: [46.33.159.39] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNDYuMzMuMTU5LjM5ID0+IDIwODEx\n X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 6029 invoked from network); 5 Feb 2013 12:47:12 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (46.33.159.39) by server-9.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 5 Feb 2013 12:47:12 -0000 X-IronPort-AV: E=Sophos;i="4.84,602,1355097600"; d="scan'208";a="1154806" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 05 Feb 2013 12:47:11 +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.297.1; Tue, 5 Feb 2013 12:47:11 +0000 Message-ID: <1360068430.17017.72.camel@zakaz.uk.xensource.com> From: Ian Campbell To: =?ISO-8859-1?Q?St=E9phane?= GAUDICHE Date: Tue, 5 Feb 2013 12:47:10 +0000 In-Reply-To: <1550996225.104330.1359653797051.JavaMail.www@wwinf8306> References: <1550996225.104330.1359653797051.JavaMail.www@wwinf8306> Organization: Citrix Systems, Inc. X-Mailer: Evolution 3.4.4-1 MIME-Version: 1.0 Cc: "xen-users@lists.xen.org" Subject: Re: [Xen-users] Xen LVM reducing HVM MS Windows guest disk X-BeenThere: xen-users@lists.xen.org X-Mailman-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 T24gVGh1LCAyMDEzLTAxLTMxIGF0IDE3OjM2ICswMDAwLCBTdMOpcGhhbmUgR0FVRElDSEUgd3Jv dGU6Cj4gSGVsbG8gbGlzdCwKPiAKPiBJIHJ1biB4ZW4gNC4wIG9uIGEgZGViaWFuIHNxdWVlemUg aG9zdCB3aXRoIGxvY2FsIGx2bTIgc3RvcmFnZQo+IEkndmUgZ290IEhWTSBWTXMgKE1pY3Jvc29m dCBXaW5kb3dzKSB3aXRoIDIgZHJpdmVzIChjOiBbT1NdICYgRDoKPiBbRGF0YV0pLCBmaWxlIHN5 c3RlbTogTlRGUwo+IEkgd2FudCB0byByZWR1Y2UgdGhlIHNpemUgb2YgdGhlIEQ6IGRyaXZlIG9m IG15IEhWTXMuCj4gCj4gQnkgcmVhZGluZyBzZXZlcmFsIGFydGljbGVzIGFuZCBob3d0b3MgYWNy b3NzIHdlYiwKPiAxLSBJIGJhY2t1cCBkYXRhcyBmaXJzdCBvdXRzaWRlIHRoZSBYZW5Ib3N0Cj4g Mi0gdGhlbiBmcm9tIE1TV2luZG93cyBndWVzdC1PUywgSSBtYW5hZ2VkIHRvIGxpdmUtcmVkdWNl IHRoZQo+IHBhcnRpdGlvbidzIHNpemUgb24gdGhlIEQ6IGRyaXZlIChmcm9tIDE1MEcgdG8gNTBH KSB3aXRoIHRoZSBlbWJlZGRlZAo+IHRvb2wgImRpc2twYXJ0IjogInNocmluayIgb3BlcmF0b3Is IGl0IHdvcmtlZCBqdXN0IGZpbmUuCj4gMy0gSSBwb3dlciBvZmYgdGhlIEhWTS4KPiBOb3csIGZy b20geGVuIHBvaW50IG9mIHZpZXcsIGkgZ290IGEgTG9naWNhbCBWb2x1bWUgY2FsbGVkCj4gZGF0 YV9IVk1fbWljcm9zb2Z0LmltZyBvZiAoc3RlYWwpIDE1MEcuCj4gNC0gSSB3YXMgZXhwZWN0aW5n IHRvIGRvIGFuICJsdnJlZHVjZSIgdG8gcmVkdWNlIHRoZSBsb2dpY2FsIHZvbHVtZQo+ICh0aGUg Ym94KSB0byAxMDBHIG9ubHkKCldoeSAxMDBHQiBpZiB5b3UgYXJlIHJlZHVjaW5nIHRvIDUwR0I/ Cgo+IGJ1dCB3aGF0IGhhcHBlbiB0byB0aGUgZmlsZXN5c3RlbSAoY29udGVuYW50IGluIHRoZSBi b3gpLHdoaWNoIGlzIHNlZW4KPiBhcyBhIEQ6IGRyaXZlIGZyb20gdGhlIEhWTSB3aXRoIGEgc21h bGwgNTBHIE5URlMgcGFydGl0aW9uIGZyb20gbm93KQo+IERvIEkgY2FyZSBhYm91dCBpdD8KCklm IHlvdSBoYXZlIHJlZHVjZWQgdGhlIGZpbGVzeXN0ZW0gd2l0aGluIHRoZSBndWVzdCB0byA1MEdC IHRoZW4gb25seQp0aGUgZmlyc3QgNTBHQiBvZiB0aGUgZGV2aWNlIHdpbGwgYmUgdXNlZCwgc28g eW91IHNob3VsZCBiZSBhYmxlIHRvCnNhZmVseSByZWR1Y2UgdGhlIExWLiBZb3UnZCB3YW50IHRv IGJlIGRhbW5lZCBzdXJlIHRoYXQgeW91IGhhZCBpbmRlZWQKcmVkdWNlZCB0aGUgZmlsZXN5c3Rl bSB0byA1MEdCIGFuZCBub3QgZS5nLiA1MC4xR0IgdGhvdWdoLCBvciBlbHNlIHlvdQp3aWxsIGVu ZCB1cCB0cnVuY2F0aW5nIGl0LgoKTm90ZSB0aGF0IHJlc2l6aW5nIHRoZSBmaWxlc3lzdGVtIGlu IHRoZSBndWVzdCB3aWxsIGhhdmUgbm8gaW1wYWN0IG9uCnRoZSBzaXplIG9mIHRoZSB1bmRlcmx5 aW5nIHZpcnR1YWwgZGV2aWNlLCBub3Igd2lsbCBpdCBhZmZlY3QgdGhlIHNpemUKb2YgdGhlIExW TSB2b2x1bWUgYmFja2luZyB0aGUgZGV2aWNlLiBJJ20gbm90IHN1cmUgaWYgeW91IHdlcmUgZXhw ZWN0aW5nCnRoYXQgaXQgd291bGQuCgo+IEkgbm90ZSB0aGF0IHRoZSBsb2dpY2FsIHZvbHVtZSB3 ZXJlIHNlZW4gYXMgQmxvY2stZGV2aWNlIGZyb20geGVuIGhvc3QKPiBmaWxlLXN5c3RlbSAobm90 IHN1cmUsIGJ1dCBpIGd1ZXNzIGl0IHF1aXRlIG5vbWFsIGR1ZSB0byBMVk0pLgo+IHRoZW4KPiA1 LWNoZWNrIGx2Cj4gNi1wb3dlciBvbiBIVk0KPiA3LWV4dGVuZCBEOiBkcml2ZSB0byAxMDBHCgpX aHkgcmVkdWNlIHRvIDUwR0IgYW5kIHRoZW4gaW5jcmVhc2UgdG8gMTAwR0I/Cgo+IENhbiBhbnlv bmUgaGVscCB0byB1bmRlcnN0YW5kIGlmIGFtIEkgcmlnaHQgYnkgZm9sbG93aW5nIHRoZXNlIHN0 ZXA/CgpXZWxsLCB0aGV5IHNvdW5kIE9LIHRvIG1lIGZyb20gYSBYZW4gUE9WLiBJJ20gbm90IHNv IGZhbWlsaWFyIHdpdGggdGhlCldpbmRvd3Mgc2lkZSBvZiB0aGluZ3MuCgpQZXJoYXBzIHlvdSBj YW4gZXhwZXJpbWVudCBieSB0YWtpbmcgYW4gTFZNIHNuYXBzaG90IG9mIHRoZSBkZXZpY2UsCndo aWNoIHdvdWxkIGF2b2lkIHRoZSByaXNrIG9mIHRyYXNoaW5nIHRoZSBkZXZpY2UgdW50aWwgeW91 IGtub3cgd2hhdAp0aGUgcmlnaHQgcHJvY2VkdXJlIGlzLgoKSWFuLgoKCl9fX19fX19fX19fX19f X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fClhlbi11c2VycyBtYWlsaW5nIGxpc3QK WGVuLXVzZXJzQGxpc3RzLnhlbi5vcmcKaHR0cDovL2xpc3RzLnhlbi5vcmcveGVuLXVzZXJz From xen-users-bounces@lists.xen.org Tue Feb 05 12:48:19 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 05 Feb 2013 12:48: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 1U2hvp-0006XQ-1P; Tue, 05 Feb 2013 12:47:25 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U2hvn-0006XK-Nm for xen-users@lists.xen.org; Tue, 05 Feb 2013 12:47:23 +0000 Received: from [193.109.254.147:56746] by server-13.bemta-14.messagelabs.com id D6/5C-30639-A5FF0115; Tue, 05 Feb 2013 12:47:22 +0000 X-Env-Sender: Ian.Campbell@citrix.com X-Msg-Ref: server-9.tower-27.messagelabs.com!1360068432!9611318!1 X-Originating-IP: [46.33.159.39] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNDYuMzMuMTU5LjM5ID0+IDIwODEx\n X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 6029 invoked from network); 5 Feb 2013 12:47:12 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (46.33.159.39) by server-9.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 5 Feb 2013 12:47:12 -0000 X-IronPort-AV: E=Sophos;i="4.84,602,1355097600"; d="scan'208";a="1154806" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 05 Feb 2013 12:47:11 +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.297.1; Tue, 5 Feb 2013 12:47:11 +0000 Message-ID: <1360068430.17017.72.camel@zakaz.uk.xensource.com> From: Ian Campbell To: =?ISO-8859-1?Q?St=E9phane?= GAUDICHE Date: Tue, 5 Feb 2013 12:47:10 +0000 In-Reply-To: <1550996225.104330.1359653797051.JavaMail.www@wwinf8306> References: <1550996225.104330.1359653797051.JavaMail.www@wwinf8306> Organization: Citrix Systems, Inc. X-Mailer: Evolution 3.4.4-1 MIME-Version: 1.0 Cc: "xen-users@lists.xen.org" Subject: Re: [Xen-users] Xen LVM reducing HVM MS Windows guest disk X-BeenThere: xen-users@lists.xen.org X-Mailman-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 T24gVGh1LCAyMDEzLTAxLTMxIGF0IDE3OjM2ICswMDAwLCBTdMOpcGhhbmUgR0FVRElDSEUgd3Jv dGU6Cj4gSGVsbG8gbGlzdCwKPiAKPiBJIHJ1biB4ZW4gNC4wIG9uIGEgZGViaWFuIHNxdWVlemUg aG9zdCB3aXRoIGxvY2FsIGx2bTIgc3RvcmFnZQo+IEkndmUgZ290IEhWTSBWTXMgKE1pY3Jvc29m dCBXaW5kb3dzKSB3aXRoIDIgZHJpdmVzIChjOiBbT1NdICYgRDoKPiBbRGF0YV0pLCBmaWxlIHN5 c3RlbTogTlRGUwo+IEkgd2FudCB0byByZWR1Y2UgdGhlIHNpemUgb2YgdGhlIEQ6IGRyaXZlIG9m IG15IEhWTXMuCj4gCj4gQnkgcmVhZGluZyBzZXZlcmFsIGFydGljbGVzIGFuZCBob3d0b3MgYWNy b3NzIHdlYiwKPiAxLSBJIGJhY2t1cCBkYXRhcyBmaXJzdCBvdXRzaWRlIHRoZSBYZW5Ib3N0Cj4g Mi0gdGhlbiBmcm9tIE1TV2luZG93cyBndWVzdC1PUywgSSBtYW5hZ2VkIHRvIGxpdmUtcmVkdWNl IHRoZQo+IHBhcnRpdGlvbidzIHNpemUgb24gdGhlIEQ6IGRyaXZlIChmcm9tIDE1MEcgdG8gNTBH KSB3aXRoIHRoZSBlbWJlZGRlZAo+IHRvb2wgImRpc2twYXJ0IjogInNocmluayIgb3BlcmF0b3Is IGl0IHdvcmtlZCBqdXN0IGZpbmUuCj4gMy0gSSBwb3dlciBvZmYgdGhlIEhWTS4KPiBOb3csIGZy b20geGVuIHBvaW50IG9mIHZpZXcsIGkgZ290IGEgTG9naWNhbCBWb2x1bWUgY2FsbGVkCj4gZGF0 YV9IVk1fbWljcm9zb2Z0LmltZyBvZiAoc3RlYWwpIDE1MEcuCj4gNC0gSSB3YXMgZXhwZWN0aW5n IHRvIGRvIGFuICJsdnJlZHVjZSIgdG8gcmVkdWNlIHRoZSBsb2dpY2FsIHZvbHVtZQo+ICh0aGUg Ym94KSB0byAxMDBHIG9ubHkKCldoeSAxMDBHQiBpZiB5b3UgYXJlIHJlZHVjaW5nIHRvIDUwR0I/ Cgo+IGJ1dCB3aGF0IGhhcHBlbiB0byB0aGUgZmlsZXN5c3RlbSAoY29udGVuYW50IGluIHRoZSBi b3gpLHdoaWNoIGlzIHNlZW4KPiBhcyBhIEQ6IGRyaXZlIGZyb20gdGhlIEhWTSB3aXRoIGEgc21h bGwgNTBHIE5URlMgcGFydGl0aW9uIGZyb20gbm93KQo+IERvIEkgY2FyZSBhYm91dCBpdD8KCklm IHlvdSBoYXZlIHJlZHVjZWQgdGhlIGZpbGVzeXN0ZW0gd2l0aGluIHRoZSBndWVzdCB0byA1MEdC IHRoZW4gb25seQp0aGUgZmlyc3QgNTBHQiBvZiB0aGUgZGV2aWNlIHdpbGwgYmUgdXNlZCwgc28g eW91IHNob3VsZCBiZSBhYmxlIHRvCnNhZmVseSByZWR1Y2UgdGhlIExWLiBZb3UnZCB3YW50IHRv IGJlIGRhbW5lZCBzdXJlIHRoYXQgeW91IGhhZCBpbmRlZWQKcmVkdWNlZCB0aGUgZmlsZXN5c3Rl bSB0byA1MEdCIGFuZCBub3QgZS5nLiA1MC4xR0IgdGhvdWdoLCBvciBlbHNlIHlvdQp3aWxsIGVu ZCB1cCB0cnVuY2F0aW5nIGl0LgoKTm90ZSB0aGF0IHJlc2l6aW5nIHRoZSBmaWxlc3lzdGVtIGlu IHRoZSBndWVzdCB3aWxsIGhhdmUgbm8gaW1wYWN0IG9uCnRoZSBzaXplIG9mIHRoZSB1bmRlcmx5 aW5nIHZpcnR1YWwgZGV2aWNlLCBub3Igd2lsbCBpdCBhZmZlY3QgdGhlIHNpemUKb2YgdGhlIExW TSB2b2x1bWUgYmFja2luZyB0aGUgZGV2aWNlLiBJJ20gbm90IHN1cmUgaWYgeW91IHdlcmUgZXhw ZWN0aW5nCnRoYXQgaXQgd291bGQuCgo+IEkgbm90ZSB0aGF0IHRoZSBsb2dpY2FsIHZvbHVtZSB3 ZXJlIHNlZW4gYXMgQmxvY2stZGV2aWNlIGZyb20geGVuIGhvc3QKPiBmaWxlLXN5c3RlbSAobm90 IHN1cmUsIGJ1dCBpIGd1ZXNzIGl0IHF1aXRlIG5vbWFsIGR1ZSB0byBMVk0pLgo+IHRoZW4KPiA1 LWNoZWNrIGx2Cj4gNi1wb3dlciBvbiBIVk0KPiA3LWV4dGVuZCBEOiBkcml2ZSB0byAxMDBHCgpX aHkgcmVkdWNlIHRvIDUwR0IgYW5kIHRoZW4gaW5jcmVhc2UgdG8gMTAwR0I/Cgo+IENhbiBhbnlv bmUgaGVscCB0byB1bmRlcnN0YW5kIGlmIGFtIEkgcmlnaHQgYnkgZm9sbG93aW5nIHRoZXNlIHN0 ZXA/CgpXZWxsLCB0aGV5IHNvdW5kIE9LIHRvIG1lIGZyb20gYSBYZW4gUE9WLiBJJ20gbm90IHNv IGZhbWlsaWFyIHdpdGggdGhlCldpbmRvd3Mgc2lkZSBvZiB0aGluZ3MuCgpQZXJoYXBzIHlvdSBj YW4gZXhwZXJpbWVudCBieSB0YWtpbmcgYW4gTFZNIHNuYXBzaG90IG9mIHRoZSBkZXZpY2UsCndo aWNoIHdvdWxkIGF2b2lkIHRoZSByaXNrIG9mIHRyYXNoaW5nIHRoZSBkZXZpY2UgdW50aWwgeW91 IGtub3cgd2hhdAp0aGUgcmlnaHQgcHJvY2VkdXJlIGlzLgoKSWFuLgoKCl9fX19fX19fX19fX19f X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fClhlbi11c2VycyBtYWlsaW5nIGxpc3QK WGVuLXVzZXJzQGxpc3RzLnhlbi5vcmcKaHR0cDovL2xpc3RzLnhlbi5vcmcveGVuLXVzZXJz From xen-users-bounces@lists.xen.org Tue Feb 05 13:16:09 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 05 Feb 2013 13: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 1U2iMs-0007R0-1q; Tue, 05 Feb 2013 13:15:22 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U2iMq-0007QZ-09; Tue, 05 Feb 2013 13:15:20 +0000 Received: from [85.158.138.51:18533] by server-8.bemta-3.messagelabs.com id 91/04-25687-6E501115; Tue, 05 Feb 2013 13:15:18 +0000 X-Env-Sender: ianc@xenbits.xen.org X-Msg-Ref: server-9.tower-174.messagelabs.com!1360070116!31104417!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.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 18786 invoked from network); 5 Feb 2013 13:15:17 -0000 Received: from mail.xen.org (HELO mail.xen.org) (50.57.168.107) by server-9.tower-174.messagelabs.com with AES256-SHA encrypted SMTP; 5 Feb 2013 13:15:17 -0000 Received: from xenbits.xen.org ([50.57.170.242]) by mail.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U2iMe-0003a8-Mt; Tue, 05 Feb 2013 13:15:08 +0000 Received: from ianc by xenbits.xen.org with local (Exim 4.72) (envelope-from ) id 1U2iMe-00089M-1r; Tue, 05 Feb 2013 13:15:08 +0000 Date: Tue, 05 Feb 2013 13:15:08 +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 38 (CVE-2013-0215) - oxenstored incorrect handling of certain Xenbus ring states X-BeenThere: xen-users@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-2013-0215 / XSA-38 version 2 oxenstored incorrect handling of certain Xenbus ring states UPDATES IN VERSION 2 ==================== Public release. ISSUE DESCRIPTION ================= The oxenstored daemon (the ocaml version of the xenstore daemon) does not correctly handle unusual or malicious contents in the xenstore ring. A malicious guest can exploit this to cause oxenstored to read past the end of the ring (and very likely crash) or to allocate large amounts of RAM. IMPACT ====== A malicious guest administrator can mount a denial of service attack affecting domain control and management functions. In more detail: A malicious guest administrator can cause oxenstored to crash; after this many host control operations (for example, starting and stopping domains, device hotplug, and some monitoring functions), will be unavailable. Domains which are already running are not directly affected. Such an attacker can also cause a memory exhaustion in the domain running oxenstored; often this will make the host's management functions unavailable. Information leak of control plane data is also theoretically possible. VULNERABLE SYSTEMS ================== Any system running oxenstored is vulnerable. oxenstored was introduced in Xen version 4.1. oxenstored was made the default in Xen 4.2.if a suitable ocaml toolchain was installed at build time. Systems running a 32-bit oxenstored are vulnerable only to the crash and not to the large memory allocation issue. MITIGATION ========== Running the C version of xenstored will avoid this issue. RESOLUTION ========== Applying the attached patch resolves this issue. xsa38.patch Xen 4.1.x, Xen 4.2.x, xen-unstable $ sha256sum xsa38*.patch 7d7a5746bc76da747bf61eb87b3303a8f3abb0d96561f35a706c671317ebe4eb xsa38.patch $ -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) iQEcBAEBAgAGBQJREQI0AAoJEIP+FMlX6CvZ6wAIAJdVEbDm51534QlQBGEE160O beOVzi6J0y1XOV3iDVnPlSxynhhBn3HcNWl0p0ERRAJt+FbZrH/WLMZ/9XLLbzZO LWVQHPiKkTYxbgxYsNXt/64CxKN8We2lffuBZn6DUQt1ZiV7T9L4SYVTWHeKo5vW mvs4j4VvlGgQTxIy0a724bEEPbBXNCu76+b6uwbJCkocnul1QMxyMK5mCJK/n/dv Q4KCXjJ9sfRHcKR8jteU0v45MP3VXbgEjrW70nvqXed3ly01SdBt/OJVAadmiG38 /EPJiFDT9cqPbl9591yQ6tQqRH5B4J3VoT7vl/hcV9AI8cduHVkQ8nLhfo71lLg= =CAag -----END PGP SIGNATURE----- --=separator Content-Type: application/octet-stream; name="xsa38.patch" Content-Disposition: attachment; filename="xsa38.patch" Content-Transfer-Encoding: base64 ZGlmZiAtLWdpdCBhL3Rvb2xzL29jYW1sL2xpYnMveGIvcGFydGlhbC5tbCBi L3Rvb2xzL29jYW1sL2xpYnMveGIvcGFydGlhbC5tbAppbmRleCAzNTU4ODg5 Li5kNGQxYzdiIDEwMDY0NAotLS0gYS90b29scy9vY2FtbC9saWJzL3hiL3Bh cnRpYWwubWwKKysrIGIvdG9vbHMvb2NhbWwvbGlicy94Yi9wYXJ0aWFsLm1s CkBAIC0yNyw4ICsyNywxNSBAQCBleHRlcm5hbCBoZWFkZXJfc2l6ZTogdW5p dCAtPiBpbnQgPSAic3R1Yl9oZWFkZXJfc2l6ZSIKIGV4dGVybmFsIGhlYWRl cl9vZl9zdHJpbmdfaW50ZXJuYWw6IHN0cmluZyAtPiBpbnQgKiBpbnQgKiBp bnQgKiBpbnQKICAgICAgICAgID0gInN0dWJfaGVhZGVyX29mX3N0cmluZyIK IAorbGV0IHhlbnN0b3JlX3BheWxvYWRfbWF4ID0gNDA5NiAoKiB4ZW4vaW5j bHVkZS9wdWJsaWMvaW8veHNfd2lyZS5oICopCisKIGxldCBvZl9zdHJpbmcg cyA9CiAJbGV0IHRpZCwgcmlkLCBvcGludCwgZGxlbiA9IGhlYWRlcl9vZl9z dHJpbmdfaW50ZXJuYWwgcyBpbgorCSgqIEEgcGFja2V0IHdoaWNoIGlzIGJp Z2dlciB0aGFuIHhlbnN0b3JlX3BheWxvYWRfbWF4IGlzIGlsbGVnYWwuCisJ ICAgVGhpcyB3aWxsIGxlYXZlIHRoZSBndWVzdCBjb25uZWN0aW9uIGlzIGEg YmFkIHN0YXRlIGFuZCB3aWxsCisJICAgYmUgaGFyZCB0byByZWNvdmVyIGZy b20gd2l0aG91dCByZXN0YXJ0aW5nIHRoZSBjb25uZWN0aW9uCisJICAgKGll IHJlYm9vdGluZyB0aGUgZ3Vlc3QpICopCisJbGV0IGRsZW4gPSBtaW4geGVu c3RvcmVfcGF5bG9hZF9tYXggZGxlbiBpbgogCXsKIAkJdGlkID0gdGlkOwog CQlyaWQgPSByaWQ7CkBAIC0zOCw2ICs0NSw3IEBAIGxldCBvZl9zdHJpbmcg cyA9CiAJfQogCiBsZXQgYXBwZW5kIHBrdCBzIHN6ID0KKwlpZiBwa3QubGVu ID4gNDA5NiB0aGVuIGZhaWx3aXRoICJCdWZmZXIuYWRkOiBjYW5ub3QgZ3Jv dyBidWZmZXIiOwogCUJ1ZmZlci5hZGRfc3RyaW5nIHBrdC5idWYgKFN0cmlu Zy5zdWIgcyAwIHN6KQogCiBsZXQgdG9fY29tcGxldGUgcGt0ID0KZGlmZiAt LWdpdCBhL3Rvb2xzL29jYW1sL2xpYnMveGIveHNfcmluZ19zdHVicy5jIGIv dG9vbHMvb2NhbWwvbGlicy94Yi94c19yaW5nX3N0dWJzLmMKaW5kZXggMDA0 MTRjNS4uNDg4OGFjNSAxMDA2NDQKLS0tIGEvdG9vbHMvb2NhbWwvbGlicy94 Yi94c19yaW5nX3N0dWJzLmMKKysrIGIvdG9vbHMvb2NhbWwvbGlicy94Yi94 c19yaW5nX3N0dWJzLmMKQEAgLTM5LDIxICszOSwyMyBAQCBzdGF0aWMgaW50 IHhzX3JpbmdfcmVhZChzdHJ1Y3QgbW1hcF9pbnRlcmZhY2UgKmludGVyZmFj ZSwKICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgY2hhciAqYnVmZmVy LCBpbnQgbGVuKQogewogCXN0cnVjdCB4ZW5zdG9yZV9kb21haW5faW50ZXJm YWNlICppbnRmID0gaW50ZXJmYWNlLT5hZGRyOwotCVhFTlNUT1JFX1JJTkdf SURYIGNvbnMsIHByb2Q7CisJWEVOU1RPUkVfUklOR19JRFggY29ucywgcHJv ZDsgLyogb2Zmc2V0cyBvbmx5ICovCiAJaW50IHRvX3JlYWQ7CiAKLQljb25z ID0gaW50Zi0+cmVxX2NvbnM7Ci0JcHJvZCA9IGludGYtPnJlcV9wcm9kOwor CWNvbnMgPSAqKHZvbGF0aWxlIHVpbnQzMiopJmludGYtPnJlcV9jb25zOwor CXByb2QgPSAqKHZvbGF0aWxlIHVpbnQzMiopJmludGYtPnJlcV9wcm9kOwog CXhlbl9tYigpOworCWNvbnMgPSBNQVNLX1hFTlNUT1JFX0lEWChjb25zKTsK Kwlwcm9kID0gTUFTS19YRU5TVE9SRV9JRFgocHJvZCk7CiAJaWYgKHByb2Qg PT0gY29ucykKIAkJcmV0dXJuIDA7Ci0JaWYgKE1BU0tfWEVOU1RPUkVfSURY KHByb2QpID4gTUFTS19YRU5TVE9SRV9JRFgoY29ucykpIAorCWlmIChwcm9k ID4gY29ucykKIAkJdG9fcmVhZCA9IHByb2QgLSBjb25zOwogCWVsc2UKLQkJ dG9fcmVhZCA9IFhFTlNUT1JFX1JJTkdfU0laRSAtIE1BU0tfWEVOU1RPUkVf SURYKGNvbnMpOworCQl0b19yZWFkID0gWEVOU1RPUkVfUklOR19TSVpFIC0g Y29uczsKIAlpZiAodG9fcmVhZCA8IGxlbikKIAkJbGVuID0gdG9fcmVhZDsK LQltZW1jcHkoYnVmZmVyLCBpbnRmLT5yZXEgKyBNQVNLX1hFTlNUT1JFX0lE WChjb25zKSwgbGVuKTsKKwltZW1jcHkoYnVmZmVyLCBpbnRmLT5yZXEgKyBj b25zLCBsZW4pOwogCXhlbl9tYigpOwogCWludGYtPnJlcV9jb25zICs9IGxl bjsKIAlyZXR1cm4gbGVuOwpAQCAtNjYsOCArNjgsOCBAQCBzdGF0aWMgaW50 IHhzX3Jpbmdfd3JpdGUoc3RydWN0IG1tYXBfaW50ZXJmYWNlICppbnRlcmZh Y2UsCiAJWEVOU1RPUkVfUklOR19JRFggY29ucywgcHJvZDsKIAlpbnQgY2Fu X3dyaXRlOwogCi0JY29ucyA9IGludGYtPnJzcF9jb25zOwotCXByb2QgPSBp bnRmLT5yc3BfcHJvZDsKKwljb25zID0gKih2b2xhdGlsZSB1aW50MzIqKSZp bnRmLT5yc3BfY29uczsKKwlwcm9kID0gKih2b2xhdGlsZSB1aW50MzIqKSZp bnRmLT5yc3BfcHJvZDsKIAl4ZW5fbWIoKTsKIAlpZiAoIChwcm9kIC0gY29u cykgPj0gWEVOU1RPUkVfUklOR19TSVpFICkKIAkJcmV0dXJuIDA7Cg== --=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 Tue Feb 05 13:16:09 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 05 Feb 2013 13: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 1U2iMs-0007R0-1q; Tue, 05 Feb 2013 13:15:22 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U2iMq-0007QZ-09; Tue, 05 Feb 2013 13:15:20 +0000 Received: from [85.158.138.51:18533] by server-8.bemta-3.messagelabs.com id 91/04-25687-6E501115; Tue, 05 Feb 2013 13:15:18 +0000 X-Env-Sender: ianc@xenbits.xen.org X-Msg-Ref: server-9.tower-174.messagelabs.com!1360070116!31104417!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.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 18786 invoked from network); 5 Feb 2013 13:15:17 -0000 Received: from mail.xen.org (HELO mail.xen.org) (50.57.168.107) by server-9.tower-174.messagelabs.com with AES256-SHA encrypted SMTP; 5 Feb 2013 13:15:17 -0000 Received: from xenbits.xen.org ([50.57.170.242]) by mail.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U2iMe-0003a8-Mt; Tue, 05 Feb 2013 13:15:08 +0000 Received: from ianc by xenbits.xen.org with local (Exim 4.72) (envelope-from ) id 1U2iMe-00089M-1r; Tue, 05 Feb 2013 13:15:08 +0000 Date: Tue, 05 Feb 2013 13:15:08 +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 38 (CVE-2013-0215) - oxenstored incorrect handling of certain Xenbus ring states X-BeenThere: xen-users@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-2013-0215 / XSA-38 version 2 oxenstored incorrect handling of certain Xenbus ring states UPDATES IN VERSION 2 ==================== Public release. ISSUE DESCRIPTION ================= The oxenstored daemon (the ocaml version of the xenstore daemon) does not correctly handle unusual or malicious contents in the xenstore ring. A malicious guest can exploit this to cause oxenstored to read past the end of the ring (and very likely crash) or to allocate large amounts of RAM. IMPACT ====== A malicious guest administrator can mount a denial of service attack affecting domain control and management functions. In more detail: A malicious guest administrator can cause oxenstored to crash; after this many host control operations (for example, starting and stopping domains, device hotplug, and some monitoring functions), will be unavailable. Domains which are already running are not directly affected. Such an attacker can also cause a memory exhaustion in the domain running oxenstored; often this will make the host's management functions unavailable. Information leak of control plane data is also theoretically possible. VULNERABLE SYSTEMS ================== Any system running oxenstored is vulnerable. oxenstored was introduced in Xen version 4.1. oxenstored was made the default in Xen 4.2.if a suitable ocaml toolchain was installed at build time. Systems running a 32-bit oxenstored are vulnerable only to the crash and not to the large memory allocation issue. MITIGATION ========== Running the C version of xenstored will avoid this issue. RESOLUTION ========== Applying the attached patch resolves this issue. xsa38.patch Xen 4.1.x, Xen 4.2.x, xen-unstable $ sha256sum xsa38*.patch 7d7a5746bc76da747bf61eb87b3303a8f3abb0d96561f35a706c671317ebe4eb xsa38.patch $ -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) iQEcBAEBAgAGBQJREQI0AAoJEIP+FMlX6CvZ6wAIAJdVEbDm51534QlQBGEE160O beOVzi6J0y1XOV3iDVnPlSxynhhBn3HcNWl0p0ERRAJt+FbZrH/WLMZ/9XLLbzZO LWVQHPiKkTYxbgxYsNXt/64CxKN8We2lffuBZn6DUQt1ZiV7T9L4SYVTWHeKo5vW mvs4j4VvlGgQTxIy0a724bEEPbBXNCu76+b6uwbJCkocnul1QMxyMK5mCJK/n/dv Q4KCXjJ9sfRHcKR8jteU0v45MP3VXbgEjrW70nvqXed3ly01SdBt/OJVAadmiG38 /EPJiFDT9cqPbl9591yQ6tQqRH5B4J3VoT7vl/hcV9AI8cduHVkQ8nLhfo71lLg= =CAag -----END PGP SIGNATURE----- --=separator Content-Type: application/octet-stream; name="xsa38.patch" Content-Disposition: attachment; filename="xsa38.patch" Content-Transfer-Encoding: base64 ZGlmZiAtLWdpdCBhL3Rvb2xzL29jYW1sL2xpYnMveGIvcGFydGlhbC5tbCBi L3Rvb2xzL29jYW1sL2xpYnMveGIvcGFydGlhbC5tbAppbmRleCAzNTU4ODg5 Li5kNGQxYzdiIDEwMDY0NAotLS0gYS90b29scy9vY2FtbC9saWJzL3hiL3Bh cnRpYWwubWwKKysrIGIvdG9vbHMvb2NhbWwvbGlicy94Yi9wYXJ0aWFsLm1s CkBAIC0yNyw4ICsyNywxNSBAQCBleHRlcm5hbCBoZWFkZXJfc2l6ZTogdW5p dCAtPiBpbnQgPSAic3R1Yl9oZWFkZXJfc2l6ZSIKIGV4dGVybmFsIGhlYWRl cl9vZl9zdHJpbmdfaW50ZXJuYWw6IHN0cmluZyAtPiBpbnQgKiBpbnQgKiBp bnQgKiBpbnQKICAgICAgICAgID0gInN0dWJfaGVhZGVyX29mX3N0cmluZyIK IAorbGV0IHhlbnN0b3JlX3BheWxvYWRfbWF4ID0gNDA5NiAoKiB4ZW4vaW5j bHVkZS9wdWJsaWMvaW8veHNfd2lyZS5oICopCisKIGxldCBvZl9zdHJpbmcg cyA9CiAJbGV0IHRpZCwgcmlkLCBvcGludCwgZGxlbiA9IGhlYWRlcl9vZl9z dHJpbmdfaW50ZXJuYWwgcyBpbgorCSgqIEEgcGFja2V0IHdoaWNoIGlzIGJp Z2dlciB0aGFuIHhlbnN0b3JlX3BheWxvYWRfbWF4IGlzIGlsbGVnYWwuCisJ ICAgVGhpcyB3aWxsIGxlYXZlIHRoZSBndWVzdCBjb25uZWN0aW9uIGlzIGEg YmFkIHN0YXRlIGFuZCB3aWxsCisJICAgYmUgaGFyZCB0byByZWNvdmVyIGZy b20gd2l0aG91dCByZXN0YXJ0aW5nIHRoZSBjb25uZWN0aW9uCisJICAgKGll IHJlYm9vdGluZyB0aGUgZ3Vlc3QpICopCisJbGV0IGRsZW4gPSBtaW4geGVu c3RvcmVfcGF5bG9hZF9tYXggZGxlbiBpbgogCXsKIAkJdGlkID0gdGlkOwog CQlyaWQgPSByaWQ7CkBAIC0zOCw2ICs0NSw3IEBAIGxldCBvZl9zdHJpbmcg cyA9CiAJfQogCiBsZXQgYXBwZW5kIHBrdCBzIHN6ID0KKwlpZiBwa3QubGVu ID4gNDA5NiB0aGVuIGZhaWx3aXRoICJCdWZmZXIuYWRkOiBjYW5ub3QgZ3Jv dyBidWZmZXIiOwogCUJ1ZmZlci5hZGRfc3RyaW5nIHBrdC5idWYgKFN0cmlu Zy5zdWIgcyAwIHN6KQogCiBsZXQgdG9fY29tcGxldGUgcGt0ID0KZGlmZiAt LWdpdCBhL3Rvb2xzL29jYW1sL2xpYnMveGIveHNfcmluZ19zdHVicy5jIGIv dG9vbHMvb2NhbWwvbGlicy94Yi94c19yaW5nX3N0dWJzLmMKaW5kZXggMDA0 MTRjNS4uNDg4OGFjNSAxMDA2NDQKLS0tIGEvdG9vbHMvb2NhbWwvbGlicy94 Yi94c19yaW5nX3N0dWJzLmMKKysrIGIvdG9vbHMvb2NhbWwvbGlicy94Yi94 c19yaW5nX3N0dWJzLmMKQEAgLTM5LDIxICszOSwyMyBAQCBzdGF0aWMgaW50 IHhzX3JpbmdfcmVhZChzdHJ1Y3QgbW1hcF9pbnRlcmZhY2UgKmludGVyZmFj ZSwKICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgY2hhciAqYnVmZmVy LCBpbnQgbGVuKQogewogCXN0cnVjdCB4ZW5zdG9yZV9kb21haW5faW50ZXJm YWNlICppbnRmID0gaW50ZXJmYWNlLT5hZGRyOwotCVhFTlNUT1JFX1JJTkdf SURYIGNvbnMsIHByb2Q7CisJWEVOU1RPUkVfUklOR19JRFggY29ucywgcHJv ZDsgLyogb2Zmc2V0cyBvbmx5ICovCiAJaW50IHRvX3JlYWQ7CiAKLQljb25z ID0gaW50Zi0+cmVxX2NvbnM7Ci0JcHJvZCA9IGludGYtPnJlcV9wcm9kOwor CWNvbnMgPSAqKHZvbGF0aWxlIHVpbnQzMiopJmludGYtPnJlcV9jb25zOwor CXByb2QgPSAqKHZvbGF0aWxlIHVpbnQzMiopJmludGYtPnJlcV9wcm9kOwog CXhlbl9tYigpOworCWNvbnMgPSBNQVNLX1hFTlNUT1JFX0lEWChjb25zKTsK Kwlwcm9kID0gTUFTS19YRU5TVE9SRV9JRFgocHJvZCk7CiAJaWYgKHByb2Qg PT0gY29ucykKIAkJcmV0dXJuIDA7Ci0JaWYgKE1BU0tfWEVOU1RPUkVfSURY KHByb2QpID4gTUFTS19YRU5TVE9SRV9JRFgoY29ucykpIAorCWlmIChwcm9k ID4gY29ucykKIAkJdG9fcmVhZCA9IHByb2QgLSBjb25zOwogCWVsc2UKLQkJ dG9fcmVhZCA9IFhFTlNUT1JFX1JJTkdfU0laRSAtIE1BU0tfWEVOU1RPUkVf SURYKGNvbnMpOworCQl0b19yZWFkID0gWEVOU1RPUkVfUklOR19TSVpFIC0g Y29uczsKIAlpZiAodG9fcmVhZCA8IGxlbikKIAkJbGVuID0gdG9fcmVhZDsK LQltZW1jcHkoYnVmZmVyLCBpbnRmLT5yZXEgKyBNQVNLX1hFTlNUT1JFX0lE WChjb25zKSwgbGVuKTsKKwltZW1jcHkoYnVmZmVyLCBpbnRmLT5yZXEgKyBj b25zLCBsZW4pOwogCXhlbl9tYigpOwogCWludGYtPnJlcV9jb25zICs9IGxl bjsKIAlyZXR1cm4gbGVuOwpAQCAtNjYsOCArNjgsOCBAQCBzdGF0aWMgaW50 IHhzX3Jpbmdfd3JpdGUoc3RydWN0IG1tYXBfaW50ZXJmYWNlICppbnRlcmZh Y2UsCiAJWEVOU1RPUkVfUklOR19JRFggY29ucywgcHJvZDsKIAlpbnQgY2Fu X3dyaXRlOwogCi0JY29ucyA9IGludGYtPnJzcF9jb25zOwotCXByb2QgPSBp bnRmLT5yc3BfcHJvZDsKKwljb25zID0gKih2b2xhdGlsZSB1aW50MzIqKSZp bnRmLT5yc3BfY29uczsKKwlwcm9kID0gKih2b2xhdGlsZSB1aW50MzIqKSZp bnRmLT5yc3BfcHJvZDsKIAl4ZW5fbWIoKTsKIAlpZiAoIChwcm9kIC0gY29u cykgPj0gWEVOU1RPUkVfUklOR19TSVpFICkKIAkJcmV0dXJuIDA7Cg== --=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 Tue Feb 05 13:16:20 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 05 Feb 2013 13:16: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 1U2iMz-0007TV-Jk; Tue, 05 Feb 2013 13:15:29 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U2iMx-0007SU-9y; Tue, 05 Feb 2013 13:15:27 +0000 Received: from [85.158.143.99:40548] by server-2.bemta-4.messagelabs.com id 21/FB-01597-EE501115; Tue, 05 Feb 2013 13:15:26 +0000 X-Env-Sender: ianc@xenbits.xen.org X-Msg-Ref: server-12.tower-216.messagelabs.com!1360070121!22200145!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.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 27328 invoked from network); 5 Feb 2013 13:15:23 -0000 Received: from mail.xen.org (HELO mail.xen.org) (50.57.168.107) by server-12.tower-216.messagelabs.com with AES256-SHA encrypted SMTP; 5 Feb 2013 13:15:23 -0000 Received: from xenbits.xen.org ([50.57.170.242]) by mail.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U2iMi-0003aO-Bd; Tue, 05 Feb 2013 13:15:12 +0000 Received: from ianc by xenbits.xen.org with local (Exim 4.72) (envelope-from ) id 1U2iMi-0008AG-9I; Tue, 05 Feb 2013 13:15:12 +0000 Date: Tue, 05 Feb 2013 13:15:12 +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 39 (CVE-2013-0216, CVE-2013-0217) - Linux netback DoS via malicious guest ring. X-BeenThere: xen-users@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-2013-0216,CVE-2013-0217 / XSA-39 version 2 Linux netback DoS via malicious guest ring. UPDATES IN VERSION 2 ==================== Public release. ISSUE DESCRIPTION ================= The Xen netback implementation contains a couple of flaws which can allow a guest to cause a DoS in the backend domain, potentially affecting other domains in the system. CVE-2013-0216 is a failure to sanity check the ring producer/consumer pointers which can allow a guest to cause netback to loop for an extended period preventing other work from occurring. CVE-2013-0217 is a memory leak on an error path which is guest triggerable. IMPACT ====== A malicious guest can mount a DoS affecting the entire system. VULNERABLE SYSTEMS ================== All systems running guests with access to PV network devices are vulnerable. CVE-2013-0216 affects both mainline ("pvops") and classic-Xen patch kernels. CVE-2013-0217 affects only mainline ("pvops") kernels. MITIGATION ========== Running HVM guests with only emulated or passthrough NICs or PV guests with only passthrough NICs will avoid this vulnerability. RESOLUTION ========== Applying the appropriate attached patches in sequence resolves this issue. xsa39-pvops-*.patch Apply to mainline Linux 3.8-rc2 xsa39-classic-*.patch Apply to linux-2.6.18-xen tree. All patches for the given branch should be applied in numerical order. $ sha256sum xsa39*.patch 4b75961673b940f5eb31451080dd668b9119eb88db1df44db1a3ba4b0d037ce1 xsa39-classic-0001-xen-netback-garbage-ring.patch 096143750b99eb2d88970338c3f9debfbbfdaef766525a620281b28528ebe0ce xsa39-classic-0002-xen-netback-wrap-around.patch 99cf93e37985908243b974cc726f57e592e62ae005eca52969f11fb6fdea6fb5 xsa39-pvops-0001-xen-netback-shutdown-the-ring-if-it-contains-garbage.patch e0c4226b0910ca455f22ae117e8346d87053e9faf03ec155dd6c31e2f58a1969 xsa39-pvops-0002-xen-netback-don-t-leak-pages-on-failure-in-xen_netbk.patch 70e6cb644a57cdda7f29eb86086a8e697706c3fc974a44c52322e451fd6b9d5c xsa39-pvops-0003-xen-netback-free-already-allocated-memory-on-failure.patch 5d0db59bbd5ad3a7efae78a6c26fc2491b7c553e5519dd946d1422a116af73dd xsa39-pvops-0004-netback-correct-netbk_tx_err-to-handle-wrap-around.patch $ -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) iQEcBAEBAgAGBQJREQI5AAoJEIP+FMlX6CvZLbcIAL7gpD+EzDjb+g3ZlORl1jPV +icqyDoPWeWructbggY+YcJJc2IavNrRXBSN/9edSTUXSi7YTW+Tjeh8bcLza1JM McWKxPtJB8CKEIAjAeT8qMVaNUNQuJQTtTLtXHGuQE6xwxK8YmgLzQSx91OOp9Bx 49GK1Ptnp7bQoEoc7B3oN6GXr/hs/FvaD0Cr481yUxXX1GxV+AL7sxXiJ4kXu1rE UTSLFAzUfw1KWI5wP3GQCREhysCvgIq4mZyD5+TF8MUagpg+m1aURs2AUUxrJ/Zw o+LVEKWYRsTtWIRtwYOdPHn73bllyPOrBgimTDBM9rY9CztOnN8yoPRlUz0Sux0= =UhBt -----END PGP SIGNATURE----- --=separator Content-Type: application/octet-stream; name="xsa39-classic-0001-xen-netback-garbage-ring.patch" Content-Disposition: attachment; filename="xsa39-classic-0001-xen-netback-garbage-ring.patch" Content-Transfer-Encoding: base64 bmV0YmFjazogc2h1dGRvd24gdGhlIHJpbmcgaWYgaXQgY29udGFpbnMgZ2Fy YmFnZQoKQSBidWdneSBvciBtYWxpY2lvdXMgZnJvbnRlbmQgc2hvdWxkIG5v dCBiZSBhYmxlIHRvIGNvbmZ1c2UgbmV0YmFjay4KSWYgd2Ugc3BvdCBhbnl0 aGluZyB3aGljaCBpcyBub3QgYXMgaXQgc2hvdWxkIGJlIHRoZW4gc2h1dGRv d24gdGhlCmRldmljZSBhbmQgZG9uJ3QgdHJ5IHRvIGNvbnRpbnVlIHdpdGgg dGhlIHJpbmcgaW4gYSBwb3RlbnRpYWxseQpob3N0aWxlIHN0YXRlLiBXZWxs IGJlaGF2ZWQgYW5kIG5vbi1ob3N0aWxlIGZyb250ZW5kcyB3aWxsIG5vdCBi ZQpwZW5hbGlzZWQuCgpBcyB3ZWxsIGFzIG1ha2luZyB0aGUgZXhpc3Rpbmcg Y2hlY2tzIGZvciBzdWNoIGVycm9ycyBmYXRhbCBhbHNvIGFkZCBhCm5ldyBj aGVjayB0aGF0IGVuc3VyZXMgdGhhdCB0aGVyZSBpc24ndCBhbiBpbnNhbmUg bnVtYmVyIG9mIHJlcXVlc3RzCm9uIHRoZSByaW5nIChpLmUuIG1vcmUgdGhh biB3b3VsZCBmaXQgaW4gdGhlIHJpbmcpLiBJZiB0aGUgcmluZwpjb250YWlu cyBnYXJiYWdlIHRoZW4gcHJldmlvdXNseSBpcyB3YXMgcG9zc2libGUgdG8g bG9vcCBvdmVyIHRoaXMKaW5zYW5lIG51bWJlciwgZ2V0dGluZyBhbiBlcnJv ciBlYWNoIHRpbWUgYW5kIHRoZXJlZm9yZSBub3QgZ2VuZXJhdGluZwphbnkg bW9yZSBwZW5kaW5nIHJlcXVlc3RzIGFuZCB0aGVyZWZvcmUgbm90IGV4aXRp bmcgdGhlIGxvb3AgaW4KeGVuX25ldGJrX3R4X2J1aWxkX2dvcHMgZm9yIGFu IGV4dGVybmRlZCBwZXJpb2QuCgpBbHNvIHR1cm4gdmFyaW91cyBuZXRkZXZf ZGJnIGNhbGxzIHdoaWNoIG5vIHByZWNpcGl0YXRlIGEgZmF0YWwgZXJyb3IK aW50byBuZXRkZXZfZXJyLCB0aGV5IGFyZSByYXRlIGxpbWl0ZWQgYmVjYXVz ZSB0aGUgZGV2aWNlIGlzIHNodXRkb3duCmFmdGVyd2FyZHMuCgpUaGlzIGZp eGVzIGF0IGxlYXN0IG9uZSBrbm93biBEb1Mvc29mdGxvY2t1cCBvZiB0aGUg YmFja2VuZCBkb21haW4uCgpTaWduZWQtb2ZmLWJ5OiBJYW4gQ2FtcGJlbGwg PGlhbi5jYW1wYmVsbEBjaXRyaXguY29tPgpTaWduZWQtb2ZmLWJ5OiBKYW4g QmV1bGljaCA8SkJldWxpY2hAc3VzZS5jb20+CgotLS0gYS9kcml2ZXJzL3hl bi9uZXRiYWNrL2NvbW1vbi5oCisrKyBiL2RyaXZlcnMveGVuL25ldGJhY2sv Y29tbW9uLmgKQEAgLTIwNCw2ICsyMDQsOSBAQCBpbnQgbmV0aWZfYmVfc3Rh cnRfeG1pdChzdHJ1Y3Qgc2tfYnVmZiAqCiBzdHJ1Y3QgbmV0X2RldmljZV9z dGF0cyAqbmV0aWZfYmVfZ2V0X3N0YXRzKHN0cnVjdCBuZXRfZGV2aWNlICpk ZXYpOwogaXJxcmV0dXJuX3QgbmV0aWZfYmVfaW50KGludCBpcnEsIHZvaWQg KmRldl9pZCwgc3RydWN0IHB0X3JlZ3MgKnJlZ3MpOwogCisvKiBQcmV2ZW50 IHRoZSBkZXZpY2UgZnJvbSBnZW5lcmF0aW5nIGFueSBmdXJ0aGVyIHRyYWZm aWMuICovCit2b2lkIHhlbnZpZl9jYXJyaWVyX29mZihuZXRpZl90ICpuZXRp Zik7CisKIHN0YXRpYyBpbmxpbmUgaW50IG5ldGJrX2Nhbl9xdWV1ZShzdHJ1 Y3QgbmV0X2RldmljZSAqZGV2KQogewogCW5ldGlmX3QgKm5ldGlmID0gbmV0 ZGV2X3ByaXYoZGV2KTsKLS0tIGEvZHJpdmVycy94ZW4vbmV0YmFjay9pbnRl cmZhY2UuYworKysgYi9kcml2ZXJzL3hlbi9uZXRiYWNrL2ludGVyZmFjZS5j CkBAIC0zNDcsMTkgKzM0NywyMyBAQCBlcnJfcng6CiAJcmV0dXJuIGVycjsK IH0KIAordm9pZCB4ZW52aWZfY2Fycmllcl9vZmYobmV0aWZfdCAqbmV0aWYp Cit7CisJcnRubF9sb2NrKCk7CisJbmV0YmFja19jYXJyaWVyX29mZihuZXRp Zik7CisJbmV0aWZfY2Fycmllcl9vZmYobmV0aWYtPmRldik7IC8qIGRpc2Nh cmQgcXVldWVkIHBhY2tldHMgKi8KKwlpZiAobmV0aWZfcnVubmluZyhuZXRp Zi0+ZGV2KSkKKwkJX19uZXRpZl9kb3duKG5ldGlmKTsKKwlydG5sX3VubG9j aygpOworCW5ldGlmX3B1dChuZXRpZik7Cit9CisKIHZvaWQgbmV0aWZfZGlz Y29ubmVjdChzdHJ1Y3QgYmFja2VuZF9pbmZvICpiZSkKIHsKIAluZXRpZl90 ICpuZXRpZiA9IGJlLT5uZXRpZjsKIAotCWlmIChuZXRiYWNrX2NhcnJpZXJf b2sobmV0aWYpKSB7Ci0JCXJ0bmxfbG9jaygpOwotCQluZXRiYWNrX2NhcnJp ZXJfb2ZmKG5ldGlmKTsKLQkJbmV0aWZfY2Fycmllcl9vZmYobmV0aWYtPmRl dik7IC8qIGRpc2NhcmQgcXVldWVkIHBhY2tldHMgKi8KLQkJaWYgKG5ldGlm X3J1bm5pbmcobmV0aWYtPmRldikpCi0JCQlfX25ldGlmX2Rvd24obmV0aWYp OwotCQlydG5sX3VubG9jaygpOwotCQluZXRpZl9wdXQobmV0aWYpOwotCX0K KwlpZiAobmV0YmFja19jYXJyaWVyX29rKG5ldGlmKSkKKwkJeGVudmlmX2Nh cnJpZXJfb2ZmKG5ldGlmKTsKIAogCWF0b21pY19kZWMoJm5ldGlmLT5yZWZj bnQpOwogCXdhaXRfZXZlbnQobmV0aWYtPndhaXRpbmdfdG9fZnJlZSwgYXRv bWljX3JlYWQoJm5ldGlmLT5yZWZjbnQpID09IDApOwotLS0gYS9kcml2ZXJz L3hlbi9uZXRiYWNrL25ldGJhY2suYworKysgYi9kcml2ZXJzL3hlbi9uZXRi YWNrL25ldGJhY2suYwpAQCAtMTAyMCw2ICsxMDIwLDE0IEBAIHN0YXRpYyB2 b2lkIG5ldGJrX3R4X2VycihuZXRpZl90ICpuZXRpZiwKIAluZXRpZl9wdXQo bmV0aWYpOwogfQogCitzdGF0aWMgdm9pZCBuZXRia19mYXRhbF90eF9lcnIo bmV0aWZfdCAqbmV0aWYpCit7CisJcHJpbnRrKEtFUk5fRVJSICIlczogZmF0 YWwgZXJyb3I7IGRpc2FibGluZyBkZXZpY2VcbiIsCisJICAgICAgIG5ldGlm LT5kZXYtPm5hbWUpOworCXhlbnZpZl9jYXJyaWVyX29mZihuZXRpZik7CisJ bmV0aWZfcHV0KG5ldGlmKTsKK30KKwogc3RhdGljIGludCBuZXRia19jb3Vu dF9yZXF1ZXN0cyhuZXRpZl90ICpuZXRpZiwgbmV0aWZfdHhfcmVxdWVzdF90 ICpmaXJzdCwKIAkJCQluZXRpZl90eF9yZXF1ZXN0X3QgKnR4cCwgaW50IHdv cmtfdG9fZG8pCiB7CkBAIC0xMDMxLDE5ICsxMDM5LDI1IEBAIHN0YXRpYyBp bnQgbmV0YmtfY291bnRfcmVxdWVzdHMobmV0aWZfdCAKIAogCWRvIHsKIAkJ aWYgKGZyYWdzID49IHdvcmtfdG9fZG8pIHsKLQkJCURQUklOVEsoIk5lZWQg bW9yZSBmcmFnc1xuIik7CisJCQlwcmludGsoS0VSTl9FUlIgIiVzOiBOZWVk IG1vcmUgZnJhZ3NcbiIsCisJCQkgICAgICAgbmV0aWYtPmRldi0+bmFtZSk7 CisJCQluZXRia19mYXRhbF90eF9lcnIobmV0aWYpOwogCQkJcmV0dXJuIC1m cmFnczsKIAkJfQogCiAJCWlmICh1bmxpa2VseShmcmFncyA+PSBNQVhfU0tC X0ZSQUdTKSkgewotCQkJRFBSSU5USygiVG9vIG1hbnkgZnJhZ3NcbiIpOwor CQkJcHJpbnRrKEtFUk5fRVJSICIlczogVG9vIG1hbnkgZnJhZ3NcbiIsCisJ CQkgICAgICAgbmV0aWYtPmRldi0+bmFtZSk7CisJCQluZXRia19mYXRhbF90 eF9lcnIobmV0aWYpOwogCQkJcmV0dXJuIC1mcmFnczsKIAkJfQogCiAJCW1l bWNweSh0eHAsIFJJTkdfR0VUX1JFUVVFU1QoJm5ldGlmLT50eCwgY29ucyAr IGZyYWdzKSwKIAkJICAgICAgIHNpemVvZigqdHhwKSk7CiAJCWlmICh0eHAt PnNpemUgPiBmaXJzdC0+c2l6ZSkgewotCQkJRFBSSU5USygiRnJhZ3MgZ2Fs b3JlXG4iKTsKKwkJCXByaW50ayhLRVJOX0VSUiAiJXM6IEZyYWcgaXMgYmln Z2VyIHRoYW4gZnJhbWUuXG4iLAorCQkJICAgICAgIG5ldGlmLT5kZXYtPm5h bWUpOworCQkJbmV0YmtfZmF0YWxfdHhfZXJyKG5ldGlmKTsKIAkJCXJldHVy biAtZnJhZ3M7CiAJCX0KIApAQCAtMTA1MSw4ICsxMDY1LDkgQEAgc3RhdGlj IGludCBuZXRia19jb3VudF9yZXF1ZXN0cyhuZXRpZl90IAogCQlmcmFncysr OwogCiAJCWlmICh1bmxpa2VseSgodHhwLT5vZmZzZXQgKyB0eHAtPnNpemUp ID4gUEFHRV9TSVpFKSkgewotCQkJRFBSSU5USygidHhwLT5vZmZzZXQ6ICV4 LCBzaXplOiAldVxuIiwKLQkJCQl0eHAtPm9mZnNldCwgdHhwLT5zaXplKTsK KwkJCXByaW50ayhLRVJOX0VSUiAiJXM6IHR4cC0+b2Zmc2V0OiAleCwgc2l6 ZTogJXVcbiIsCisJCQkgICAgICAgbmV0aWYtPmRldi0+bmFtZSwgdHhwLT5v ZmZzZXQsIHR4cC0+c2l6ZSk7CisJCQluZXRia19mYXRhbF90eF9lcnIobmV0 aWYpOwogCQkJcmV0dXJuIC1mcmFnczsKIAkJfQogCX0gd2hpbGUgKCh0eHAr KyktPmZsYWdzICYgTkVUVFhGX21vcmVfZGF0YSk7CkBAIC0xMTk1LDcgKzEy MTAsOSBAQCBpbnQgbmV0YmtfZ2V0X2V4dHJhcyhuZXRpZl90ICpuZXRpZiwg c3RyCiAKIAlkbyB7CiAJCWlmICh1bmxpa2VseSh3b3JrX3RvX2RvLS0gPD0g MCkpIHsKLQkJCURQUklOVEsoIk1pc3NpbmcgZXh0cmEgaW5mb1xuIik7CisJ CQlwcmludGsoS0VSTl9FUlIgIiVzOiBNaXNzaW5nIGV4dHJhIGluZm9cbiIs CisJCQkgICAgICAgbmV0aWYtPmRldi0+bmFtZSk7CisJCQluZXRia19mYXRh bF90eF9lcnIobmV0aWYpOwogCQkJcmV0dXJuIC1FQkFEUjsKIAkJfQogCkBA IC0xMjA0LDcgKzEyMjEsOSBAQCBpbnQgbmV0YmtfZ2V0X2V4dHJhcyhuZXRp Zl90ICpuZXRpZiwgc3RyCiAJCWlmICh1bmxpa2VseSghZXh0cmEudHlwZSB8 fAogCQkJICAgICBleHRyYS50eXBlID49IFhFTl9ORVRJRl9FWFRSQV9UWVBF X01BWCkpIHsKIAkJCW5ldGlmLT50eC5yZXFfY29ucyA9ICsrY29uczsKLQkJ CURQUklOVEsoIkludmFsaWQgZXh0cmEgdHlwZTogJWRcbiIsIGV4dHJhLnR5 cGUpOworCQkJcHJpbnRrKEtFUk5fRVJSICIlczogSW52YWxpZCBleHRyYSB0 eXBlOiAlZFxuIiwKKwkJCSAgICAgICBuZXRpZi0+ZGV2LT5uYW1lLCBleHRy YS50eXBlKTsKKwkJCW5ldGJrX2ZhdGFsX3R4X2VycihuZXRpZik7CiAJCQly ZXR1cm4gLUVJTlZBTDsKIAkJfQogCkBAIC0xMjE1LDE2ICsxMjM0LDIxIEBA IGludCBuZXRia19nZXRfZXh0cmFzKG5ldGlmX3QgKm5ldGlmLCBzdHIKIAly ZXR1cm4gd29ya190b19kbzsKIH0KIAotc3RhdGljIGludCBuZXRia19zZXRf c2tiX2dzbyhzdHJ1Y3Qgc2tfYnVmZiAqc2tiLCBzdHJ1Y3QgbmV0aWZfZXh0 cmFfaW5mbyAqZ3NvKQorc3RhdGljIGludCBuZXRia19zZXRfc2tiX2dzbyhu ZXRpZl90ICpuZXRpZiwgc3RydWN0IHNrX2J1ZmYgKnNrYiwKKwkJCSAgICAg c3RydWN0IG5ldGlmX2V4dHJhX2luZm8gKmdzbykKIHsKIAlpZiAoIWdzby0+ dS5nc28uc2l6ZSkgewotCQlEUFJJTlRLKCJHU08gc2l6ZSBtdXN0IG5vdCBi ZSB6ZXJvLlxuIik7CisJCXByaW50ayhLRVJOX0VSUiAiJXM6IEdTTyBzaXpl IG11c3Qgbm90IGJlIHplcm8uXG4iLAorCQkgICAgICAgbmV0aWYtPmRldi0+ bmFtZSk7CisJCW5ldGJrX2ZhdGFsX3R4X2VycihuZXRpZik7CiAJCXJldHVy biAtRUlOVkFMOwogCX0KIAogCS8qIEN1cnJlbnRseSBvbmx5IFRDUHY0IFMu Ty4gaXMgc3VwcG9ydGVkLiAqLwogCWlmIChnc28tPnUuZ3NvLnR5cGUgIT0g WEVOX05FVElGX0dTT19UWVBFX1RDUFY0KSB7Ci0JCURQUklOVEsoIkJhZCBH U08gdHlwZSAlZC5cbiIsIGdzby0+dS5nc28udHlwZSk7CisJCXByaW50ayhL RVJOX0VSUiAiJXM6IEJhZCBHU08gdHlwZSAlZC5cbiIsCisJCSAgICAgICBu ZXRpZi0+ZGV2LT5uYW1lLCBnc28tPnUuZ3NvLnR5cGUpOworCQluZXRia19m YXRhbF90eF9lcnIobmV0aWYpOwogCQlyZXR1cm4gLUVJTlZBTDsKIAl9CiAK QEAgLTEyNTksOSArMTI4MywyNSBAQCBzdGF0aWMgdm9pZCBuZXRfdHhfYWN0 aW9uKHVuc2lnbmVkIGxvbmcgCiAJCSFsaXN0X2VtcHR5KCZuZXRfc2NoZWR1 bGVfbGlzdCkpIHsKIAkJLyogR2V0IGEgbmV0aWYgZnJvbSB0aGUgbGlzdCB3 aXRoIHdvcmsgdG8gZG8uICovCiAJCW5ldGlmID0gcG9sbF9uZXRfc2NoZWR1 bGVfbGlzdCgpOworCQkvKgorCQkgKiBUaGlzIGNhbiBzb21ldGltZXMgaGFw cGVuIGJlY2F1c2UgdGhlIHRlc3Qgb2YKKwkJICogbGlzdF9lbXB0eShuZXRf c2NoZWR1bGVfbGlzdCkgYXQgdGhlIHRvcCBvZiB0aGUKKwkJICogbG9vcCBp cyB1bmxvY2tlZC4gIEp1c3QgZ28gYmFjayBhbmQgaGF2ZSBhbm90aGVyCisJ CSAqIGxvb2suCisJCSAqLwogCQlpZiAoIW5ldGlmKQogCQkJY29udGludWU7 CiAKKwkJaWYgKG5ldGlmLT50eC5zcmluZy0+cmVxX3Byb2QgLSBuZXRpZi0+ dHgucmVxX2NvbnMgPgorCQkgICAgTkVUX1RYX1JJTkdfU0laRSkgeworCQkJ cHJpbnRrKEtFUk5fRVJSICIlczogSW1wb3NzaWJsZSBudW1iZXIgb2YgcmVx dWVzdHMuICIKKwkJCSAgICAgICAicmVxX3Byb2QgJXUsIHJlcV9jb25zICV1 LCBzaXplICVsdVxuIiwKKwkJCSAgICAgICBuZXRpZi0+ZGV2LT5uYW1lLCBu ZXRpZi0+dHguc3JpbmctPnJlcV9wcm9kLAorCQkJICAgICAgIG5ldGlmLT50 eC5yZXFfY29ucywgTkVUX1RYX1JJTkdfU0laRSk7CisJCQluZXRia19mYXRh bF90eF9lcnIobmV0aWYpOworCQkJY29udGludWU7CisJCX0KKwogCQlSSU5H X0ZJTkFMX0NIRUNLX0ZPUl9SRVFVRVNUUygmbmV0aWYtPnR4LCB3b3JrX3Rv X2RvKTsKIAkJaWYgKCF3b3JrX3RvX2RvKSB7CiAJCQluZXRpZl9wdXQobmV0 aWYpOwpAQCAtMTMxMywxNyArMTM1MywxNCBAQCBzdGF0aWMgdm9pZCBuZXRf dHhfYWN0aW9uKHVuc2lnbmVkIGxvbmcgCiAJCQl3b3JrX3RvX2RvID0gbmV0 YmtfZ2V0X2V4dHJhcyhuZXRpZiwgZXh0cmFzLAogCQkJCQkJICAgICAgd29y a190b19kbyk7CiAJCQlpID0gbmV0aWYtPnR4LnJlcV9jb25zOwotCQkJaWYg KHVubGlrZWx5KHdvcmtfdG9fZG8gPCAwKSkgewotCQkJCW5ldGJrX3R4X2Vy cihuZXRpZiwgJnR4cmVxLCBpKTsKKwkJCWlmICh1bmxpa2VseSh3b3JrX3Rv X2RvIDwgMCkpCiAJCQkJY29udGludWU7Ci0JCQl9CiAJCX0KIAogCQlyZXQg PSBuZXRia19jb3VudF9yZXF1ZXN0cyhuZXRpZiwgJnR4cmVxLCB0eGZyYWdz LCB3b3JrX3RvX2RvKTsKLQkJaWYgKHVubGlrZWx5KHJldCA8IDApKSB7Ci0J CQluZXRia190eF9lcnIobmV0aWYsICZ0eHJlcSwgaSAtIHJldCk7CisJCWlm ICh1bmxpa2VseShyZXQgPCAwKSkKIAkJCWNvbnRpbnVlOwotCQl9CisKIAkJ aSArPSByZXQ7CiAKIAkJaWYgKHVubGlrZWx5KHR4cmVxLnNpemUgPCBFVEhf SExFTikpIHsKQEAgLTEzMzQsMTAgKzEzNzEsMTAgQEAgc3RhdGljIHZvaWQg bmV0X3R4X2FjdGlvbih1bnNpZ25lZCBsb25nIAogCiAJCS8qIE5vIGNyb3Nz aW5nIGEgcGFnZSBhcyB0aGUgcGF5bG9hZCBtdXN0bid0IGZyYWdtZW50LiAq LwogCQlpZiAodW5saWtlbHkoKHR4cmVxLm9mZnNldCArIHR4cmVxLnNpemUp ID4gUEFHRV9TSVpFKSkgewotCQkJRFBSSU5USygidHhyZXEub2Zmc2V0OiAl eCwgc2l6ZTogJXUsIGVuZDogJWx1XG4iLCAKLQkJCQl0eHJlcS5vZmZzZXQs IHR4cmVxLnNpemUsIAotCQkJCSh0eHJlcS5vZmZzZXQgJn5QQUdFX01BU0sp ICsgdHhyZXEuc2l6ZSk7Ci0JCQluZXRia190eF9lcnIobmV0aWYsICZ0eHJl cSwgaSk7CisJCQlwcmludGsoS0VSTl9FUlIgIiVzOiB0eHJlcS5vZmZzZXQ6 ICV4LCBzaXplOiAldSwgZW5kOiAlbHVcbiIsCisJCQkgICAgICAgbmV0aWYt PmRldi0+bmFtZSwgdHhyZXEub2Zmc2V0LCB0eHJlcS5zaXplLAorCQkJICAg ICAgICh0eHJlcS5vZmZzZXQgJiB+UEFHRV9NQVNLKSArIHR4cmVxLnNpemUp OworCQkJbmV0YmtfZmF0YWxfdHhfZXJyKG5ldGlmKTsKIAkJCWNvbnRpbnVl OwogCQl9CiAKQEAgLTEzNjIsOSArMTM5OSw5IEBAIHN0YXRpYyB2b2lkIG5l dF90eF9hY3Rpb24odW5zaWduZWQgbG9uZyAKIAkJCXN0cnVjdCBuZXRpZl9l eHRyYV9pbmZvICpnc287CiAJCQlnc28gPSAmZXh0cmFzW1hFTl9ORVRJRl9F WFRSQV9UWVBFX0dTTyAtIDFdOwogCi0JCQlpZiAobmV0Ymtfc2V0X3NrYl9n c28oc2tiLCBnc28pKSB7CisJCQlpZiAobmV0Ymtfc2V0X3NrYl9nc28obmV0 aWYsIHNrYiwgZ3NvKSkgeworCQkJCS8qIEZhaWx1cmUgaW4gbmV0Ymtfc2V0 X3NrYl9nc28gaXMgZmF0YWwuICovCiAJCQkJa2ZyZWVfc2tiKHNrYik7Ci0J CQkJbmV0YmtfdHhfZXJyKG5ldGlmLCAmdHhyZXEsIGkpOwogCQkJCWNvbnRp bnVlOwogCQkJfQogCQl9Cg== --=separator Content-Type: application/octet-stream; name="xsa39-classic-0002-xen-netback-wrap-around.patch" Content-Disposition: attachment; filename="xsa39-classic-0002-xen-netback-wrap-around.patch" Content-Transfer-Encoding: base64 bmV0YmFjazogY29ycmVjdCBuZXRia190eF9lcnIoKSB0byBoYW5kbGUgd3Jh cCBhcm91bmQKClNpZ25lZC1vZmYtYnk6IElhbiBDYW1wYmVsbCA8aWFuLmNh bXBiZWxsQGNpdHJpeC5jb20+ClNpZ25lZC1vZmYtYnk6IEphbiBCZXVsaWNo IDxKQmV1bGljaEBzdXNlLmNvbT4KCi0tLSBhL2RyaXZlcnMveGVuL25ldGJh Y2svbmV0YmFjay5jCisrKyBiL2RyaXZlcnMveGVuL25ldGJhY2svbmV0YmFj ay5jCkBAIC0xMDExLDcgKzEwMTEsNyBAQCBzdGF0aWMgdm9pZCBuZXRia190 eF9lcnIobmV0aWZfdCAqbmV0aWYsCiAKIAlkbyB7CiAJCW1ha2VfdHhfcmVz cG9uc2UobmV0aWYsIHR4cCwgTkVUSUZfUlNQX0VSUk9SKTsKLQkJaWYgKGNv bnMgPj0gZW5kKQorCQlpZiAoY29ucyA9PSBlbmQpCiAJCQlicmVhazsKIAkJ dHhwID0gUklOR19HRVRfUkVRVUVTVCgmbmV0aWYtPnR4LCBjb25zKyspOwog CX0gd2hpbGUgKDEpOwo= --=separator Content-Type: application/octet-stream; name="xsa39-pvops-0001-xen-netback-shutdown-the-ring-if-it-contains-garbage.patch" Content-Disposition: attachment; filename="xsa39-pvops-0001-xen-netback-shutdown-the-ring-if-it-contains-garbage.patch" Content-Transfer-Encoding: base64 RnJvbSA3ZGQ3Y2U0NDU5M2E4YzRjNzE1ZmE2NjUwMjdhZjhlMDcyNDVjOGNm IE1vbiBTZXAgMTcgMDA6MDA6MDAgMjAwMQpGcm9tOiBJYW4gQ2FtcGJlbGwg PGlhbi5jYW1wYmVsbEBjaXRyaXguY29tPgpEYXRlOiBGcmksIDExIEphbiAy MDEzIDE0OjI2OjI5ICswMDAwClN1YmplY3Q6IFtQQVRDSCAxLzRdIHhlbi9u ZXRiYWNrOiBzaHV0ZG93biB0aGUgcmluZyBpZiBpdCBjb250YWlucyBnYXJi YWdlLgoKQSBidWdneSBvciBtYWxpY2lvdXMgZnJvbnRlbmQgc2hvdWxkIG5v dCBiZSBhYmxlIHRvIGNvbmZ1c2UgbmV0YmFjay4KSWYgd2Ugc3BvdCBhbnl0 aGluZyB3aGljaCBpcyBub3QgYXMgaXQgc2hvdWxkIGJlIHRoZW4gc2h1dGRv d24gdGhlCmRldmljZSBhbmQgZG9uJ3QgdHJ5IHRvIGNvbnRpbnVlIHdpdGgg dGhlIHJpbmcgaW4gYSBwb3RlbnRpYWxseQpob3N0aWxlIHN0YXRlLiBXZWxs IGJlaGF2ZWQgYW5kIG5vbi1ob3N0aWxlIGZyb250ZW5kcyB3aWxsIG5vdCBi ZQpwZW5hbGlzZWQuCgpBcyB3ZWxsIGFzIG1ha2luZyB0aGUgZXhpc3Rpbmcg Y2hlY2tzIGZvciBzdWNoIGVycm9ycyBmYXRhbCBhbHNvIGFkZCBhCm5ldyBj aGVjayB0aGF0IGVuc3VyZXMgdGhhdCB0aGVyZSBpc24ndCBhbiBpbnNhbmUg bnVtYmVyIG9mIHJlcXVlc3RzCm9uIHRoZSByaW5nIChpLmUuIG1vcmUgdGhh biB3b3VsZCBmaXQgaW4gdGhlIHJpbmcpLiBJZiB0aGUgcmluZwpjb250YWlu cyBnYXJiYWdlIHRoZW4gcHJldmlvdXNseSBpcyB3YXMgcG9zc2libGUgdG8g bG9vcCBvdmVyIHRoaXMKaW5zYW5lIG51bWJlciwgZ2V0dGluZyBhbiBlcnJv ciBlYWNoIHRpbWUgYW5kIHRoZXJlZm9yZSBub3QgZ2VuZXJhdGluZwphbnkg bW9yZSBwZW5kaW5nIHJlcXVlc3RzIGFuZCB0aGVyZWZvcmUgbm90IGV4aXRp bmcgdGhlIGxvb3AgaW4KeGVuX25ldGJrX3R4X2J1aWxkX2dvcHMgZm9yIGFu IGV4dGVybmRlZCBwZXJpb2QuCgpBbHNvIHR1cm4gdmFyaW91cyBuZXRkZXZf ZGJnIGNhbGxzIHdoaWNoIG5vIHByZWNpcGl0YXRlIGEgZmF0YWwgZXJyb3IK aW50byBuZXRkZXZfZXJyLCB0aGV5IGFyZSByYXRlIGxpbWl0ZWQgYmVjYXVz ZSB0aGUgZGV2aWNlIGlzIHNodXRkb3duCmFmdGVyd2FyZHMuCgpUaGlzIGZp eGVzIGF0IGxlYXN0IG9uZSBrbm93biBEb1Mvc29mdGxvY2t1cCBvZiB0aGUg YmFja2VuZCBkb21haW4uCgpTaWduZWQtb2ZmLWJ5OiBJYW4gQ2FtcGJlbGwg PGlhbi5jYW1wYmVsbEBjaXRyaXguY29tPgpSZXZpZXdlZC1ieTogS29ucmFk IFJ6ZXN6dXRlayBXaWxrIDxrb25yYWQud2lsa0BvcmFjbGUuY29tPgpBY2tl ZC1ieTogSmFuIEJldWxpY2ggPEpCZXVsaWNoQHN1c2UuY29tPgotLS0KIGRy aXZlcnMvbmV0L3hlbi1uZXRiYWNrL2NvbW1vbi5oICAgIHwgICAgMyArKwog ZHJpdmVycy9uZXQveGVuLW5ldGJhY2svaW50ZXJmYWNlLmMgfCAgIDIzICsr KysrKysrLS0tLS0KIGRyaXZlcnMvbmV0L3hlbi1uZXRiYWNrL25ldGJhY2su YyAgIHwgICA2MyArKysrKysrKysrKysrKysrKysrKysrKysrLS0tLS0tLS0t CiAzIGZpbGVzIGNoYW5nZWQsIDYzIGluc2VydGlvbnMoKyksIDI2IGRlbGV0 aW9ucygtKQoKZGlmZiAtLWdpdCBhL2RyaXZlcnMvbmV0L3hlbi1uZXRiYWNr L2NvbW1vbi5oIGIvZHJpdmVycy9uZXQveGVuLW5ldGJhY2svY29tbW9uLmgK aW5kZXggOTRiNzljMy4uOWQ3ZjE3MiAxMDA2NDQKLS0tIGEvZHJpdmVycy9u ZXQveGVuLW5ldGJhY2svY29tbW9uLmgKKysrIGIvZHJpdmVycy9uZXQveGVu LW5ldGJhY2svY29tbW9uLmgKQEAgLTE1MSw2ICsxNTEsOSBAQCB2b2lkIHhl bl9uZXRia19xdWV1ZV90eF9za2Ioc3RydWN0IHhlbnZpZiAqdmlmLCBzdHJ1 Y3Qgc2tfYnVmZiAqc2tiKTsKIC8qIE5vdGlmeSB4ZW52aWYgdGhhdCByaW5n IG5vdyBoYXMgc3BhY2UgdG8gc2VuZCBhbiBza2IgdG8gdGhlIGZyb250ZW5k ICovCiB2b2lkIHhlbnZpZl9ub3RpZnlfdHhfY29tcGxldGlvbihzdHJ1Y3Qg eGVudmlmICp2aWYpOwogCisvKiBQcmV2ZW50IHRoZSBkZXZpY2UgZnJvbSBn ZW5lcmF0aW5nIGFueSBmdXJ0aGVyIHRyYWZmaWMuICovCit2b2lkIHhlbnZp Zl9jYXJyaWVyX29mZihzdHJ1Y3QgeGVudmlmICp2aWYpOworCiAvKiBSZXR1 cm5zIG51bWJlciBvZiByaW5nIHNsb3RzIHJlcXVpcmVkIHRvIHNlbmQgYW4g c2tiIHRvIHRoZSBmcm9udGVuZCAqLwogdW5zaWduZWQgaW50IHhlbl9uZXRi a19jb3VudF9za2Jfc2xvdHMoc3RydWN0IHhlbnZpZiAqdmlmLCBzdHJ1Y3Qg c2tfYnVmZiAqc2tiKTsKIApkaWZmIC0tZ2l0IGEvZHJpdmVycy9uZXQveGVu LW5ldGJhY2svaW50ZXJmYWNlLmMgYi9kcml2ZXJzL25ldC94ZW4tbmV0YmFj ay9pbnRlcmZhY2UuYwppbmRleCBiN2Q0MWY4Li5iOGM1MTkzIDEwMDY0NAot LS0gYS9kcml2ZXJzL25ldC94ZW4tbmV0YmFjay9pbnRlcmZhY2UuYworKysg Yi9kcml2ZXJzL25ldC94ZW4tbmV0YmFjay9pbnRlcmZhY2UuYwpAQCAtMzQz LDE3ICszNDMsMjIgQEAgZXJyOgogCXJldHVybiBlcnI7CiB9CiAKLXZvaWQg eGVudmlmX2Rpc2Nvbm5lY3Qoc3RydWN0IHhlbnZpZiAqdmlmKQordm9pZCB4 ZW52aWZfY2Fycmllcl9vZmYoc3RydWN0IHhlbnZpZiAqdmlmKQogewogCXN0 cnVjdCBuZXRfZGV2aWNlICpkZXYgPSB2aWYtPmRldjsKLQlpZiAobmV0aWZf Y2Fycmllcl9vayhkZXYpKSB7Ci0JCXJ0bmxfbG9jaygpOwotCQluZXRpZl9j YXJyaWVyX29mZihkZXYpOyAvKiBkaXNjYXJkIHF1ZXVlZCBwYWNrZXRzICov Ci0JCWlmIChuZXRpZl9ydW5uaW5nKGRldikpCi0JCQl4ZW52aWZfZG93bih2 aWYpOwotCQlydG5sX3VubG9jaygpOwotCQl4ZW52aWZfcHV0KHZpZik7Ci0J fQorCisJcnRubF9sb2NrKCk7CisJbmV0aWZfY2Fycmllcl9vZmYoZGV2KTsg LyogZGlzY2FyZCBxdWV1ZWQgcGFja2V0cyAqLworCWlmIChuZXRpZl9ydW5u aW5nKGRldikpCisJCXhlbnZpZl9kb3duKHZpZik7CisJcnRubF91bmxvY2so KTsKKwl4ZW52aWZfcHV0KHZpZik7Cit9CisKK3ZvaWQgeGVudmlmX2Rpc2Nv bm5lY3Qoc3RydWN0IHhlbnZpZiAqdmlmKQoreworCWlmIChuZXRpZl9jYXJy aWVyX29rKHZpZi0+ZGV2KSkKKwkJeGVudmlmX2NhcnJpZXJfb2ZmKHZpZik7 CiAKIAlhdG9taWNfZGVjKCZ2aWYtPnJlZmNudCk7CiAJd2FpdF9ldmVudCh2 aWYtPndhaXRpbmdfdG9fZnJlZSwgYXRvbWljX3JlYWQoJnZpZi0+cmVmY250 KSA9PSAwKTsKZGlmZiAtLWdpdCBhL2RyaXZlcnMvbmV0L3hlbi1uZXRiYWNr L25ldGJhY2suYyBiL2RyaXZlcnMvbmV0L3hlbi1uZXRiYWNrL25ldGJhY2su YwppbmRleCBmMmQ2Yjc4Li4xYTQ0OWY5IDEwMDY0NAotLS0gYS9kcml2ZXJz L25ldC94ZW4tbmV0YmFjay9uZXRiYWNrLmMKKysrIGIvZHJpdmVycy9uZXQv eGVuLW5ldGJhY2svbmV0YmFjay5jCkBAIC04ODgsNiArODg4LDEzIEBAIHN0 YXRpYyB2b2lkIG5ldGJrX3R4X2VycihzdHJ1Y3QgeGVudmlmICp2aWYsCiAJ eGVudmlmX3B1dCh2aWYpOwogfQogCitzdGF0aWMgdm9pZCBuZXRia19mYXRh bF90eF9lcnIoc3RydWN0IHhlbnZpZiAqdmlmKQoreworCW5ldGRldl9lcnIo dmlmLT5kZXYsICJmYXRhbCBlcnJvcjsgZGlzYWJsaW5nIGRldmljZVxuIik7 CisJeGVudmlmX2NhcnJpZXJfb2ZmKHZpZik7CisJeGVudmlmX3B1dCh2aWYp OworfQorCiBzdGF0aWMgaW50IG5ldGJrX2NvdW50X3JlcXVlc3RzKHN0cnVj dCB4ZW52aWYgKnZpZiwKIAkJCQlzdHJ1Y3QgeGVuX25ldGlmX3R4X3JlcXVl c3QgKmZpcnN0LAogCQkJCXN0cnVjdCB4ZW5fbmV0aWZfdHhfcmVxdWVzdCAq dHhwLApAQCAtOTAxLDE5ICs5MDgsMjIgQEAgc3RhdGljIGludCBuZXRia19j b3VudF9yZXF1ZXN0cyhzdHJ1Y3QgeGVudmlmICp2aWYsCiAKIAlkbyB7CiAJ CWlmIChmcmFncyA+PSB3b3JrX3RvX2RvKSB7Ci0JCQluZXRkZXZfZGJnKHZp Zi0+ZGV2LCAiTmVlZCBtb3JlIGZyYWdzXG4iKTsKKwkJCW5ldGRldl9lcnIo dmlmLT5kZXYsICJOZWVkIG1vcmUgZnJhZ3NcbiIpOworCQkJbmV0YmtfZmF0 YWxfdHhfZXJyKHZpZik7CiAJCQlyZXR1cm4gLWZyYWdzOwogCQl9CiAKIAkJ aWYgKHVubGlrZWx5KGZyYWdzID49IE1BWF9TS0JfRlJBR1MpKSB7Ci0JCQlu ZXRkZXZfZGJnKHZpZi0+ZGV2LCAiVG9vIG1hbnkgZnJhZ3NcbiIpOworCQkJ bmV0ZGV2X2Vycih2aWYtPmRldiwgIlRvbyBtYW55IGZyYWdzXG4iKTsKKwkJ CW5ldGJrX2ZhdGFsX3R4X2Vycih2aWYpOwogCQkJcmV0dXJuIC1mcmFnczsK IAkJfQogCiAJCW1lbWNweSh0eHAsIFJJTkdfR0VUX1JFUVVFU1QoJnZpZi0+ dHgsIGNvbnMgKyBmcmFncyksCiAJCSAgICAgICBzaXplb2YoKnR4cCkpOwog CQlpZiAodHhwLT5zaXplID4gZmlyc3QtPnNpemUpIHsKLQkJCW5ldGRldl9k YmcodmlmLT5kZXYsICJGcmFncyBnYWxvcmVcbiIpOworCQkJbmV0ZGV2X2Vy cih2aWYtPmRldiwgIkZyYWcgaXMgYmlnZ2VyIHRoYW4gZnJhbWUuXG4iKTsK KwkJCW5ldGJrX2ZhdGFsX3R4X2Vycih2aWYpOwogCQkJcmV0dXJuIC1mcmFn czsKIAkJfQogCkBAIC05MjEsOCArOTMxLDkgQEAgc3RhdGljIGludCBuZXRi a19jb3VudF9yZXF1ZXN0cyhzdHJ1Y3QgeGVudmlmICp2aWYsCiAJCWZyYWdz Kys7CiAKIAkJaWYgKHVubGlrZWx5KCh0eHAtPm9mZnNldCArIHR4cC0+c2l6 ZSkgPiBQQUdFX1NJWkUpKSB7Ci0JCQluZXRkZXZfZGJnKHZpZi0+ZGV2LCAi dHhwLT5vZmZzZXQ6ICV4LCBzaXplOiAldVxuIiwKKwkJCW5ldGRldl9lcnIo dmlmLT5kZXYsICJ0eHAtPm9mZnNldDogJXgsIHNpemU6ICV1XG4iLAogCQkJ CSB0eHAtPm9mZnNldCwgdHhwLT5zaXplKTsKKwkJCW5ldGJrX2ZhdGFsX3R4 X2Vycih2aWYpOwogCQkJcmV0dXJuIC1mcmFnczsKIAkJfQogCX0gd2hpbGUg KCh0eHArKyktPmZsYWdzICYgWEVOX05FVFRYRl9tb3JlX2RhdGEpOwpAQCAt MTA5NSw3ICsxMTA2LDggQEAgc3RhdGljIGludCB4ZW5fbmV0YmtfZ2V0X2V4 dHJhcyhzdHJ1Y3QgeGVudmlmICp2aWYsCiAKIAlkbyB7CiAJCWlmICh1bmxp a2VseSh3b3JrX3RvX2RvLS0gPD0gMCkpIHsKLQkJCW5ldGRldl9kYmcodmlm LT5kZXYsICJNaXNzaW5nIGV4dHJhIGluZm9cbiIpOworCQkJbmV0ZGV2X2Vy cih2aWYtPmRldiwgIk1pc3NpbmcgZXh0cmEgaW5mb1xuIik7CisJCQluZXRi a19mYXRhbF90eF9lcnIodmlmKTsKIAkJCXJldHVybiAtRUJBRFI7CiAJCX0K IApAQCAtMTEwNCw4ICsxMTE2LDkgQEAgc3RhdGljIGludCB4ZW5fbmV0Ymtf Z2V0X2V4dHJhcyhzdHJ1Y3QgeGVudmlmICp2aWYsCiAJCWlmICh1bmxpa2Vs eSghZXh0cmEudHlwZSB8fAogCQkJICAgICBleHRyYS50eXBlID49IFhFTl9O RVRJRl9FWFRSQV9UWVBFX01BWCkpIHsKIAkJCXZpZi0+dHgucmVxX2NvbnMg PSArK2NvbnM7Ci0JCQluZXRkZXZfZGJnKHZpZi0+ZGV2LAorCQkJbmV0ZGV2 X2Vycih2aWYtPmRldiwKIAkJCQkgICAiSW52YWxpZCBleHRyYSB0eXBlOiAl ZFxuIiwgZXh0cmEudHlwZSk7CisJCQluZXRia19mYXRhbF90eF9lcnIodmlm KTsKIAkJCXJldHVybiAtRUlOVkFMOwogCQl9CiAKQEAgLTExMjEsMTMgKzEx MzQsMTUgQEAgc3RhdGljIGludCBuZXRia19zZXRfc2tiX2dzbyhzdHJ1Y3Qg eGVudmlmICp2aWYsCiAJCQkgICAgIHN0cnVjdCB4ZW5fbmV0aWZfZXh0cmFf aW5mbyAqZ3NvKQogewogCWlmICghZ3NvLT51Lmdzby5zaXplKSB7Ci0JCW5l dGRldl9kYmcodmlmLT5kZXYsICJHU08gc2l6ZSBtdXN0IG5vdCBiZSB6ZXJv LlxuIik7CisJCW5ldGRldl9lcnIodmlmLT5kZXYsICJHU08gc2l6ZSBtdXN0 IG5vdCBiZSB6ZXJvLlxuIik7CisJCW5ldGJrX2ZhdGFsX3R4X2Vycih2aWYp OwogCQlyZXR1cm4gLUVJTlZBTDsKIAl9CiAKIAkvKiBDdXJyZW50bHkgb25s eSBUQ1B2NCBTLk8uIGlzIHN1cHBvcnRlZC4gKi8KIAlpZiAoZ3NvLT51Lmdz by50eXBlICE9IFhFTl9ORVRJRl9HU09fVFlQRV9UQ1BWNCkgewotCQluZXRk ZXZfZGJnKHZpZi0+ZGV2LCAiQmFkIEdTTyB0eXBlICVkLlxuIiwgZ3NvLT51 Lmdzby50eXBlKTsKKwkJbmV0ZGV2X2Vycih2aWYtPmRldiwgIkJhZCBHU08g dHlwZSAlZC5cbiIsIGdzby0+dS5nc28udHlwZSk7CisJCW5ldGJrX2ZhdGFs X3R4X2Vycih2aWYpOwogCQlyZXR1cm4gLUVJTlZBTDsKIAl9CiAKQEAgLTEy NjQsOSArMTI3OSwyNiBAQCBzdGF0aWMgdW5zaWduZWQgeGVuX25ldGJrX3R4 X2J1aWxkX2dvcHMoc3RydWN0IHhlbl9uZXRiayAqbmV0YmspCiAKIAkJLyog R2V0IGEgbmV0aWYgZnJvbSB0aGUgbGlzdCB3aXRoIHdvcmsgdG8gZG8uICov CiAJCXZpZiA9IHBvbGxfbmV0X3NjaGVkdWxlX2xpc3QobmV0YmspOworCQkv KgorCQkgKiBUaGlzIGNhbiBzb21ldGltZXMgaGFwcGVuIGJlY2F1c2UgdGhl IHRlc3Qgb2YKKwkJICogbGlzdF9lbXB0eShuZXRfc2NoZWR1bGVfbGlzdCkg YXQgdGhlIHRvcCBvZiB0aGUKKwkJICogbG9vcCBpcyB1bmxvY2tlZC4gIEp1 c3QgZ28gYmFjayBhbmQgaGF2ZSBhbm90aGVyCisJCSAqIGxvb2suCisJCSAq LwogCQlpZiAoIXZpZikKIAkJCWNvbnRpbnVlOwogCisJCWlmICh2aWYtPnR4 LnNyaW5nLT5yZXFfcHJvZCAtIHZpZi0+dHgucmVxX2NvbnMgPgorCQkgICAg WEVOX05FVElGX1RYX1JJTkdfU0laRSkgeworCQkJbmV0ZGV2X2Vycih2aWYt PmRldiwKKwkJCQkgICAiSW1wb3NzaWJsZSBudW1iZXIgb2YgcmVxdWVzdHMu ICIKKwkJCQkgICAicmVxX3Byb2QgJWQsIHJlcV9jb25zICVkLCBzaXplICVs ZFxuIiwKKwkJCQkgICB2aWYtPnR4LnNyaW5nLT5yZXFfcHJvZCwgdmlmLT50 eC5yZXFfY29ucywKKwkJCQkgICBYRU5fTkVUSUZfVFhfUklOR19TSVpFKTsK KwkJCW5ldGJrX2ZhdGFsX3R4X2Vycih2aWYpOworCQkJY29udGludWU7CisJ CX0KKwogCQlSSU5HX0ZJTkFMX0NIRUNLX0ZPUl9SRVFVRVNUUygmdmlmLT50 eCwgd29ya190b19kbyk7CiAJCWlmICghd29ya190b19kbykgewogCQkJeGVu dmlmX3B1dCh2aWYpOwpAQCAtMTI5NCwxNyArMTMyNiwxNCBAQCBzdGF0aWMg dW5zaWduZWQgeGVuX25ldGJrX3R4X2J1aWxkX2dvcHMoc3RydWN0IHhlbl9u ZXRiayAqbmV0YmspCiAJCQl3b3JrX3RvX2RvID0geGVuX25ldGJrX2dldF9l eHRyYXModmlmLCBleHRyYXMsCiAJCQkJCQkJICB3b3JrX3RvX2RvKTsKIAkJ CWlkeCA9IHZpZi0+dHgucmVxX2NvbnM7Ci0JCQlpZiAodW5saWtlbHkod29y a190b19kbyA8IDApKSB7Ci0JCQkJbmV0YmtfdHhfZXJyKHZpZiwgJnR4cmVx LCBpZHgpOworCQkJaWYgKHVubGlrZWx5KHdvcmtfdG9fZG8gPCAwKSkKIAkJ CQljb250aW51ZTsKLQkJCX0KIAkJfQogCiAJCXJldCA9IG5ldGJrX2NvdW50 X3JlcXVlc3RzKHZpZiwgJnR4cmVxLCB0eGZyYWdzLCB3b3JrX3RvX2RvKTsK LQkJaWYgKHVubGlrZWx5KHJldCA8IDApKSB7Ci0JCQluZXRia190eF9lcnIo dmlmLCAmdHhyZXEsIGlkeCAtIHJldCk7CisJCWlmICh1bmxpa2VseShyZXQg PCAwKSkKIAkJCWNvbnRpbnVlOwotCQl9CisKIAkJaWR4ICs9IHJldDsKIAog CQlpZiAodW5saWtlbHkodHhyZXEuc2l6ZSA8IEVUSF9ITEVOKSkgewpAQCAt MTMxNiwxMSArMTM0NSwxMSBAQCBzdGF0aWMgdW5zaWduZWQgeGVuX25ldGJr X3R4X2J1aWxkX2dvcHMoc3RydWN0IHhlbl9uZXRiayAqbmV0YmspCiAKIAkJ LyogTm8gY3Jvc3NpbmcgYSBwYWdlIGFzIHRoZSBwYXlsb2FkIG11c3RuJ3Qg ZnJhZ21lbnQuICovCiAJCWlmICh1bmxpa2VseSgodHhyZXEub2Zmc2V0ICsg dHhyZXEuc2l6ZSkgPiBQQUdFX1NJWkUpKSB7Ci0JCQluZXRkZXZfZGJnKHZp Zi0+ZGV2LAorCQkJbmV0ZGV2X2Vycih2aWYtPmRldiwKIAkJCQkgICAidHhy ZXEub2Zmc2V0OiAleCwgc2l6ZTogJXUsIGVuZDogJWx1XG4iLAogCQkJCSAg IHR4cmVxLm9mZnNldCwgdHhyZXEuc2l6ZSwKIAkJCQkgICAodHhyZXEub2Zm c2V0Jn5QQUdFX01BU0spICsgdHhyZXEuc2l6ZSk7Ci0JCQluZXRia190eF9l cnIodmlmLCAmdHhyZXEsIGlkeCk7CisJCQluZXRia19mYXRhbF90eF9lcnIo dmlmKTsKIAkJCWNvbnRpbnVlOwogCQl9CiAKQEAgLTEzNDgsOCArMTM3Nyw4 IEBAIHN0YXRpYyB1bnNpZ25lZCB4ZW5fbmV0YmtfdHhfYnVpbGRfZ29wcyhz dHJ1Y3QgeGVuX25ldGJrICpuZXRiaykKIAkJCWdzbyA9ICZleHRyYXNbWEVO X05FVElGX0VYVFJBX1RZUEVfR1NPIC0gMV07CiAKIAkJCWlmIChuZXRia19z ZXRfc2tiX2dzbyh2aWYsIHNrYiwgZ3NvKSkgeworCQkJCS8qIEZhaWx1cmUg aW4gbmV0Ymtfc2V0X3NrYl9nc28gaXMgZmF0YWwuICovCiAJCQkJa2ZyZWVf c2tiKHNrYik7Ci0JCQkJbmV0YmtfdHhfZXJyKHZpZiwgJnR4cmVxLCBpZHgp OwogCQkJCWNvbnRpbnVlOwogCQkJfQogCQl9Ci0tIAoxLjcuMi41Cgo= --=separator Content-Type: application/octet-stream; name="xsa39-pvops-0002-xen-netback-don-t-leak-pages-on-failure-in-xen_netbk.patch" Content-Disposition: attachment; filename="xsa39-pvops-0002-xen-netback-don-t-leak-pages-on-failure-in-xen_netbk.patch" Content-Transfer-Encoding: base64 RnJvbSA5MDQyMDYzMWQyYjc4YWNhMjhjOTRiZWI2NmIyNTQ0N2U1N2E4ZGQ0 IE1vbiBTZXAgMTcgMDA6MDA6MDAgMjAwMQpGcm9tOiBJYW4gQ2FtcGJlbGwg PGlhbi5jYW1wYmVsbEBjaXRyaXguY29tPgpEYXRlOiBNb24sIDE0IEphbiAy MDEzIDEyOjIwOjA0ICswMDAwClN1YmplY3Q6IFtQQVRDSCAyLzRdIHhlbi9u ZXRiYWNrOiBkb24ndCBsZWFrIHBhZ2VzIG9uIGZhaWx1cmUgaW4geGVuX25l dGJrX3R4X2NoZWNrX2dvcC4KClNpZ25lZC1vZmYtYnk6IE1hdHRoZXcgRGFs ZXkgPG1hdHRqZEBnbWFpbC5jb20+ClJldmlld2VkLWJ5OiBLb25yYWQgUnpl c3p1dGVrIFdpbGsgPGtvbnJhZC53aWxrQG9yYWNsZS5jb20+CkFja2VkLWJ5 OiBJYW4gQ2FtcGJlbGwgPGlhbi5jYW1wYmVsbEBjaXRyaXguY29tPgpBY2tl ZC1ieTogSmFuIEJldWxpY2ggPEpCZXVsaWNoQHN1c2UuY29tPgotLS0KIGRy aXZlcnMvbmV0L3hlbi1uZXRiYWNrL25ldGJhY2suYyB8ICAgMzggKysrKysr KysrKysrLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tCiAxIGZpbGVzIGNoYW5n ZWQsIDEzIGluc2VydGlvbnMoKyksIDI1IGRlbGV0aW9ucygtKQoKZGlmZiAt LWdpdCBhL2RyaXZlcnMvbmV0L3hlbi1uZXRiYWNrL25ldGJhY2suYyBiL2Ry aXZlcnMvbmV0L3hlbi1uZXRiYWNrL25ldGJhY2suYwppbmRleCAxYTQ0OWY5 Li45NzUyNDFlIDEwMDY0NAotLS0gYS9kcml2ZXJzL25ldC94ZW4tbmV0YmFj ay9uZXRiYWNrLmMKKysrIGIvZHJpdmVycy9uZXQveGVuLW5ldGJhY2svbmV0 YmFjay5jCkBAIC0xNDcsNyArMTQ3LDggQEAgdm9pZCB4ZW5fbmV0YmtfcmVt b3ZlX3hlbnZpZihzdHJ1Y3QgeGVudmlmICp2aWYpCiAJYXRvbWljX2RlYygm bmV0YmstPm5ldGZyb250X2NvdW50KTsKIH0KIAotc3RhdGljIHZvaWQgeGVu X25ldGJrX2lkeF9yZWxlYXNlKHN0cnVjdCB4ZW5fbmV0YmsgKm5ldGJrLCB1 MTYgcGVuZGluZ19pZHgpOworc3RhdGljIHZvaWQgeGVuX25ldGJrX2lkeF9y ZWxlYXNlKHN0cnVjdCB4ZW5fbmV0YmsgKm5ldGJrLCB1MTYgcGVuZGluZ19p ZHgsCisJCQkJICB1OCBzdGF0dXMpOwogc3RhdGljIHZvaWQgbWFrZV90eF9y ZXNwb25zZShzdHJ1Y3QgeGVudmlmICp2aWYsCiAJCQkgICAgIHN0cnVjdCB4 ZW5fbmV0aWZfdHhfcmVxdWVzdCAqdHhwLAogCQkJICAgICBzOCAgICAgICBz dCk7CkBAIC0xMDA3LDMwICsxMDA4LDIwIEBAIHN0YXRpYyBpbnQgeGVuX25l dGJrX3R4X2NoZWNrX2dvcChzdHJ1Y3QgeGVuX25ldGJrICpuZXRiaywKIHsK IAlzdHJ1Y3QgZ250dGFiX2NvcHkgKmdvcCA9ICpnb3BwOwogCXUxNiBwZW5k aW5nX2lkeCA9ICooKHUxNiAqKXNrYi0+ZGF0YSk7Ci0Jc3RydWN0IHBlbmRp bmdfdHhfaW5mbyAqcGVuZGluZ190eF9pbmZvID0gbmV0YmstPnBlbmRpbmdf dHhfaW5mbzsKLQlzdHJ1Y3QgeGVudmlmICp2aWYgPSBwZW5kaW5nX3R4X2lu Zm9bcGVuZGluZ19pZHhdLnZpZjsKLQlzdHJ1Y3QgeGVuX25ldGlmX3R4X3Jl cXVlc3QgKnR4cDsKIAlzdHJ1Y3Qgc2tiX3NoYXJlZF9pbmZvICpzaGluZm8g PSBza2Jfc2hpbmZvKHNrYik7CiAJaW50IG5yX2ZyYWdzID0gc2hpbmZvLT5u cl9mcmFnczsKIAlpbnQgaSwgZXJyLCBzdGFydDsKIAogCS8qIENoZWNrIHN0 YXR1cyBvZiBoZWFkZXIuICovCiAJZXJyID0gZ29wLT5zdGF0dXM7Ci0JaWYg KHVubGlrZWx5KGVycikpIHsKLQkJcGVuZGluZ19yaW5nX2lkeF90IGluZGV4 OwotCQlpbmRleCA9IHBlbmRpbmdfaW5kZXgobmV0YmstPnBlbmRpbmdfcHJv ZCsrKTsKLQkJdHhwID0gJnBlbmRpbmdfdHhfaW5mb1twZW5kaW5nX2lkeF0u cmVxOwotCQltYWtlX3R4X3Jlc3BvbnNlKHZpZiwgdHhwLCBYRU5fTkVUSUZf UlNQX0VSUk9SKTsKLQkJbmV0YmstPnBlbmRpbmdfcmluZ1tpbmRleF0gPSBw ZW5kaW5nX2lkeDsKLQkJeGVudmlmX3B1dCh2aWYpOwotCX0KKwlpZiAodW5s aWtlbHkoZXJyKSkKKwkJeGVuX25ldGJrX2lkeF9yZWxlYXNlKG5ldGJrLCBw ZW5kaW5nX2lkeCwgWEVOX05FVElGX1JTUF9FUlJPUik7CiAKIAkvKiBTa2lw IGZpcnN0IHNrYiBmcmFnbWVudCBpZiBpdCBpcyBvbiBzYW1lIHBhZ2UgYXMg aGVhZGVyIGZyYWdtZW50LiAqLwogCXN0YXJ0ID0gKGZyYWdfZ2V0X3BlbmRp bmdfaWR4KCZzaGluZm8tPmZyYWdzWzBdKSA9PSBwZW5kaW5nX2lkeCk7CiAK IAlmb3IgKGkgPSBzdGFydDsgaSA8IG5yX2ZyYWdzOyBpKyspIHsKIAkJaW50 IGosIG5ld2VycjsKLQkJcGVuZGluZ19yaW5nX2lkeF90IGluZGV4OwogCiAJ CXBlbmRpbmdfaWR4ID0gZnJhZ19nZXRfcGVuZGluZ19pZHgoJnNoaW5mby0+ ZnJhZ3NbaV0pOwogCkBAIC0xMDM5LDE2ICsxMDMwLDEyIEBAIHN0YXRpYyBp bnQgeGVuX25ldGJrX3R4X2NoZWNrX2dvcChzdHJ1Y3QgeGVuX25ldGJrICpu ZXRiaywKIAkJaWYgKGxpa2VseSghbmV3ZXJyKSkgewogCQkJLyogSGFkIGEg cHJldmlvdXMgZXJyb3I/IEludmFsaWRhdGUgdGhpcyBmcmFnbWVudC4gKi8K IAkJCWlmICh1bmxpa2VseShlcnIpKQotCQkJCXhlbl9uZXRia19pZHhfcmVs ZWFzZShuZXRiaywgcGVuZGluZ19pZHgpOworCQkJCXhlbl9uZXRia19pZHhf cmVsZWFzZShuZXRiaywgcGVuZGluZ19pZHgsIFhFTl9ORVRJRl9SU1BfT0tB WSk7CiAJCQljb250aW51ZTsKIAkJfQogCiAJCS8qIEVycm9yIG9uIHRoaXMg ZnJhZ21lbnQ6IHJlc3BvbmQgdG8gY2xpZW50IHdpdGggYW4gZXJyb3IuICov Ci0JCXR4cCA9ICZuZXRiay0+cGVuZGluZ190eF9pbmZvW3BlbmRpbmdfaWR4 XS5yZXE7Ci0JCW1ha2VfdHhfcmVzcG9uc2UodmlmLCB0eHAsIFhFTl9ORVRJ Rl9SU1BfRVJST1IpOwotCQlpbmRleCA9IHBlbmRpbmdfaW5kZXgobmV0Ymst PnBlbmRpbmdfcHJvZCsrKTsKLQkJbmV0YmstPnBlbmRpbmdfcmluZ1tpbmRl eF0gPSBwZW5kaW5nX2lkeDsKLQkJeGVudmlmX3B1dCh2aWYpOworCQl4ZW5f bmV0YmtfaWR4X3JlbGVhc2UobmV0YmssIHBlbmRpbmdfaWR4LCBYRU5fTkVU SUZfUlNQX0VSUk9SKTsKIAogCQkvKiBOb3QgdGhlIGZpcnN0IGVycm9yPyBQ cmVjZWRpbmcgZnJhZ3MgYWxyZWFkeSBpbnZhbGlkYXRlZC4gKi8KIAkJaWYg KGVycikKQEAgLTEwNTYsMTAgKzEwNDMsMTAgQEAgc3RhdGljIGludCB4ZW5f bmV0YmtfdHhfY2hlY2tfZ29wKHN0cnVjdCB4ZW5fbmV0YmsgKm5ldGJrLAog CiAJCS8qIEZpcnN0IGVycm9yOiBpbnZhbGlkYXRlIGhlYWRlciBhbmQgcHJl Y2VkaW5nIGZyYWdtZW50cy4gKi8KIAkJcGVuZGluZ19pZHggPSAqKCh1MTYg Kilza2ItPmRhdGEpOwotCQl4ZW5fbmV0YmtfaWR4X3JlbGVhc2UobmV0Ymss IHBlbmRpbmdfaWR4KTsKKwkJeGVuX25ldGJrX2lkeF9yZWxlYXNlKG5ldGJr LCBwZW5kaW5nX2lkeCwgWEVOX05FVElGX1JTUF9PS0FZKTsKIAkJZm9yIChq ID0gc3RhcnQ7IGogPCBpOyBqKyspIHsKIAkJCXBlbmRpbmdfaWR4ID0gZnJh Z19nZXRfcGVuZGluZ19pZHgoJnNoaW5mby0+ZnJhZ3Nbal0pOwotCQkJeGVu X25ldGJrX2lkeF9yZWxlYXNlKG5ldGJrLCBwZW5kaW5nX2lkeCk7CisJCQl4 ZW5fbmV0YmtfaWR4X3JlbGVhc2UobmV0YmssIHBlbmRpbmdfaWR4LCBYRU5f TkVUSUZfUlNQX09LQVkpOwogCQl9CiAKIAkJLyogUmVtZW1iZXIgdGhlIGVy cm9yOiBpbnZhbGlkYXRlIGFsbCBzdWJzZXF1ZW50IGZyYWdtZW50cy4gKi8K QEAgLTEwOTMsNyArMTA4MCw3IEBAIHN0YXRpYyB2b2lkIHhlbl9uZXRia19m aWxsX2ZyYWdzKHN0cnVjdCB4ZW5fbmV0YmsgKm5ldGJrLCBzdHJ1Y3Qgc2tf YnVmZiAqc2tiKQogCiAJCS8qIFRha2UgYW4gZXh0cmEgcmVmZXJlbmNlIHRv IG9mZnNldCB4ZW5fbmV0YmtfaWR4X3JlbGVhc2UgKi8KIAkJZ2V0X3BhZ2Uo bmV0YmstPm1tYXBfcGFnZXNbcGVuZGluZ19pZHhdKTsKLQkJeGVuX25ldGJr X2lkeF9yZWxlYXNlKG5ldGJrLCBwZW5kaW5nX2lkeCk7CisJCXhlbl9uZXRi a19pZHhfcmVsZWFzZShuZXRiaywgcGVuZGluZ19pZHgsIFhFTl9ORVRJRl9S U1BfT0tBWSk7CiAJfQogfQogCkBAIC0xNDc3LDcgKzE0NjQsNyBAQCBzdGF0 aWMgdm9pZCB4ZW5fbmV0YmtfdHhfc3VibWl0KHN0cnVjdCB4ZW5fbmV0Ymsg Km5ldGJrKQogCQkJdHhwLT5zaXplIC09IGRhdGFfbGVuOwogCQl9IGVsc2Ug ewogCQkJLyogU2NoZWR1bGUgYSByZXNwb25zZSBpbW1lZGlhdGVseS4gKi8K LQkJCXhlbl9uZXRia19pZHhfcmVsZWFzZShuZXRiaywgcGVuZGluZ19pZHgp OworCQkJeGVuX25ldGJrX2lkeF9yZWxlYXNlKG5ldGJrLCBwZW5kaW5nX2lk eCwgWEVOX05FVElGX1JTUF9PS0FZKTsKIAkJfQogCiAJCWlmICh0eHAtPmZs YWdzICYgWEVOX05FVFRYRl9jc3VtX2JsYW5rKQpAQCAtMTUyOSw3ICsxNTE2 LDggQEAgc3RhdGljIHZvaWQgeGVuX25ldGJrX3R4X2FjdGlvbihzdHJ1Y3Qg eGVuX25ldGJrICpuZXRiaykKIAl4ZW5fbmV0YmtfdHhfc3VibWl0KG5ldGJr KTsKIH0KIAotc3RhdGljIHZvaWQgeGVuX25ldGJrX2lkeF9yZWxlYXNlKHN0 cnVjdCB4ZW5fbmV0YmsgKm5ldGJrLCB1MTYgcGVuZGluZ19pZHgpCitzdGF0 aWMgdm9pZCB4ZW5fbmV0YmtfaWR4X3JlbGVhc2Uoc3RydWN0IHhlbl9uZXRi ayAqbmV0YmssIHUxNiBwZW5kaW5nX2lkeCwKKwkJCQkgIHU4IHN0YXR1cykK IHsKIAlzdHJ1Y3QgeGVudmlmICp2aWY7CiAJc3RydWN0IHBlbmRpbmdfdHhf aW5mbyAqcGVuZGluZ190eF9pbmZvOwpAQCAtMTU0Myw3ICsxNTMxLDcgQEAg c3RhdGljIHZvaWQgeGVuX25ldGJrX2lkeF9yZWxlYXNlKHN0cnVjdCB4ZW5f bmV0YmsgKm5ldGJrLCB1MTYgcGVuZGluZ19pZHgpCiAKIAl2aWYgPSBwZW5k aW5nX3R4X2luZm8tPnZpZjsKIAotCW1ha2VfdHhfcmVzcG9uc2UodmlmLCAm cGVuZGluZ190eF9pbmZvLT5yZXEsIFhFTl9ORVRJRl9SU1BfT0tBWSk7CisJ bWFrZV90eF9yZXNwb25zZSh2aWYsICZwZW5kaW5nX3R4X2luZm8tPnJlcSwg c3RhdHVzKTsKIAogCWluZGV4ID0gcGVuZGluZ19pbmRleChuZXRiay0+cGVu ZGluZ19wcm9kKyspOwogCW5ldGJrLT5wZW5kaW5nX3JpbmdbaW5kZXhdID0g cGVuZGluZ19pZHg7Ci0tIAoxLjcuMi41Cgo= --=separator Content-Type: application/octet-stream; name="xsa39-pvops-0003-xen-netback-free-already-allocated-memory-on-failure.patch" Content-Disposition: attachment; filename="xsa39-pvops-0003-xen-netback-free-already-allocated-memory-on-failure.patch" Content-Transfer-Encoding: base64 RnJvbSBiNmIxZjE3YWE0NGFjZmUxMDI0OTY4YmFmYjFkMWZlNzcwNGE3NDlh IE1vbiBTZXAgMTcgMDA6MDA6MDAgMjAwMQpGcm9tOiBJYW4gQ2FtcGJlbGwg PGlhbi5jYW1wYmVsbEBjaXRyaXguY29tPgpEYXRlOiBNb24sIDE0IEphbiAy MDEzIDEyOjUxOjIyICswMDAwClN1YmplY3Q6IFtQQVRDSCAzLzRdIHhlbi9u ZXRiYWNrOiBmcmVlIGFscmVhZHkgYWxsb2NhdGVkIG1lbW9yeSBvbiBmYWls dXJlIGluIHhlbl9uZXRia19nZXRfcmVxdWVzdHMKClNpZ25lZC1vZmYtYnk6 IElhbiBDYW1wYmVsbCA8aWFuLmNhbXBiZWxsQGNpdHJpeC5jb20+Ci0tLQog ZHJpdmVycy9uZXQveGVuLW5ldGJhY2svbmV0YmFjay5jIHwgICAxNiArKysr KysrKysrKysrKystCiAxIGZpbGVzIGNoYW5nZWQsIDE1IGluc2VydGlvbnMo KyksIDEgZGVsZXRpb25zKC0pCgpkaWZmIC0tZ2l0IGEvZHJpdmVycy9uZXQv eGVuLW5ldGJhY2svbmV0YmFjay5jIGIvZHJpdmVycy9uZXQveGVuLW5ldGJh Y2svbmV0YmFjay5jCmluZGV4IDk3NTI0MWUuLjFhOTkyODggMTAwNjQ0Ci0t LSBhL2RyaXZlcnMvbmV0L3hlbi1uZXRiYWNrL25ldGJhY2suYworKysgYi9k cml2ZXJzL25ldC94ZW4tbmV0YmFjay9uZXRiYWNrLmMKQEAgLTk3OCw3ICs5 NzgsNyBAQCBzdGF0aWMgc3RydWN0IGdudHRhYl9jb3B5ICp4ZW5fbmV0Ymtf Z2V0X3JlcXVlc3RzKHN0cnVjdCB4ZW5fbmV0YmsgKm5ldGJrLAogCQlwZW5k aW5nX2lkeCA9IG5ldGJrLT5wZW5kaW5nX3JpbmdbaW5kZXhdOwogCQlwYWdl ID0geGVuX25ldGJrX2FsbG9jX3BhZ2UobmV0YmssIHNrYiwgcGVuZGluZ19p ZHgpOwogCQlpZiAoIXBhZ2UpCi0JCQlyZXR1cm4gTlVMTDsKKwkJCWdvdG8g ZXJyOwogCiAJCWdvcC0+c291cmNlLnUucmVmID0gdHhwLT5ncmVmOwogCQln b3AtPnNvdXJjZS5kb21pZCA9IHZpZi0+ZG9taWQ7CkBAIC0xMDAwLDYgKzEw MDAsMjAgQEAgc3RhdGljIHN0cnVjdCBnbnR0YWJfY29weSAqeGVuX25ldGJr X2dldF9yZXF1ZXN0cyhzdHJ1Y3QgeGVuX25ldGJrICpuZXRiaywKIAl9CiAK IAlyZXR1cm4gZ29wOworZXJyOgorCS8qCisJICogVW53aW5kLCBmcmVlaW5n IGFsbCBwYWdlcyBhbmQgc2VuZGluZyBlcnJvcgorCSAqIHJlcG9uc2VzLgor CSAqLworCXdoaWxlIChpLS0gPiBzdGFydCkgeworCQl4ZW5fbmV0YmtfaWR4 X3JlbGVhc2UobmV0YmssIGZyYWdfZ2V0X3BlbmRpbmdfaWR4KCZmcmFnc1tp XSksCisJCQkJICAgICAgWEVOX05FVElGX1JTUF9FUlJPUik7CisJfQorCS8q IFRoZSBoZWFkIHRvbywgaWYgbmVjZXNzYXJ5LiAqLworCWlmIChzdGFydCkK KwkJeGVuX25ldGJrX2lkeF9yZWxlYXNlKG5ldGJrLCBwZW5kaW5nX2lkeCwg WEVOX05FVElGX1JTUF9FUlJPUik7CisKKwlyZXR1cm4gTlVMTDsKIH0KIAog c3RhdGljIGludCB4ZW5fbmV0YmtfdHhfY2hlY2tfZ29wKHN0cnVjdCB4ZW5f bmV0YmsgKm5ldGJrLAotLSAKMS43LjIuNQoK --=separator Content-Type: application/octet-stream; name="xsa39-pvops-0004-netback-correct-netbk_tx_err-to-handle-wrap-around.patch" Content-Disposition: attachment; filename="xsa39-pvops-0004-netback-correct-netbk_tx_err-to-handle-wrap-around.patch" Content-Transfer-Encoding: base64 RnJvbSBlYTVlM2MxZThmZDlmZmU2MDgwZTAxYWY3NzY5YTlmYTQyMGNjNjJl IE1vbiBTZXAgMTcgMDA6MDA6MDAgMjAwMQpGcm9tOiBJYW4gQ2FtcGJlbGwg PGlhbi5jYW1wYmVsbEBjaXRyaXguY29tPgpEYXRlOiBNb24sIDE0IEphbiAy MDEzIDEzOjMyOjMxICswMDAwClN1YmplY3Q6IFtQQVRDSCA0LzRdIG5ldGJh Y2s6IGNvcnJlY3QgbmV0YmtfdHhfZXJyIHRvIGhhbmRsZSB3cmFwIGFyb3Vu ZC4KClNpZ25lZC1vZmYtYnk6IElhbiBDYW1wYmVsbCA8aWFuLmNhbXBiZWxs QGNpdHJpeC5jb20+CkFja2VkLWJ5OiBKYW4gQmV1bGljaCA8SkJldWxpY2hA c3VzZS5jb20+Ci0tLQogZHJpdmVycy9uZXQveGVuLW5ldGJhY2svbmV0YmFj ay5jIHwgICAgMiArLQogMSBmaWxlcyBjaGFuZ2VkLCAxIGluc2VydGlvbnMo KyksIDEgZGVsZXRpb25zKC0pCgpkaWZmIC0tZ2l0IGEvZHJpdmVycy9uZXQv eGVuLW5ldGJhY2svbmV0YmFjay5jIGIvZHJpdmVycy9uZXQveGVuLW5ldGJh Y2svbmV0YmFjay5jCmluZGV4IDFhOTkyODguLjI4ZDVlMDYgMTAwNjQ0Ci0t LSBhL2RyaXZlcnMvbmV0L3hlbi1uZXRiYWNrL25ldGJhY2suYworKysgYi9k cml2ZXJzL25ldC94ZW4tbmV0YmFjay9uZXRiYWNrLmMKQEAgLTg4MCw3ICs4 ODAsNyBAQCBzdGF0aWMgdm9pZCBuZXRia190eF9lcnIoc3RydWN0IHhlbnZp ZiAqdmlmLAogCiAJZG8gewogCQltYWtlX3R4X3Jlc3BvbnNlKHZpZiwgdHhw LCBYRU5fTkVUSUZfUlNQX0VSUk9SKTsKLQkJaWYgKGNvbnMgPj0gZW5kKQor CQlpZiAoY29ucyA9PSBlbmQpCiAJCQlicmVhazsKIAkJdHhwID0gUklOR19H RVRfUkVRVUVTVCgmdmlmLT50eCwgY29ucysrKTsKIAl9IHdoaWxlICgxKTsK LS0gCjEuNy4yLjUKCg== --=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 Tue Feb 05 13:16:20 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 05 Feb 2013 13:16: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 1U2iMz-0007TV-Jk; Tue, 05 Feb 2013 13:15:29 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U2iMx-0007SU-9y; Tue, 05 Feb 2013 13:15:27 +0000 Received: from [85.158.143.99:40548] by server-2.bemta-4.messagelabs.com id 21/FB-01597-EE501115; Tue, 05 Feb 2013 13:15:26 +0000 X-Env-Sender: ianc@xenbits.xen.org X-Msg-Ref: server-12.tower-216.messagelabs.com!1360070121!22200145!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.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 27328 invoked from network); 5 Feb 2013 13:15:23 -0000 Received: from mail.xen.org (HELO mail.xen.org) (50.57.168.107) by server-12.tower-216.messagelabs.com with AES256-SHA encrypted SMTP; 5 Feb 2013 13:15:23 -0000 Received: from xenbits.xen.org ([50.57.170.242]) by mail.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U2iMi-0003aO-Bd; Tue, 05 Feb 2013 13:15:12 +0000 Received: from ianc by xenbits.xen.org with local (Exim 4.72) (envelope-from ) id 1U2iMi-0008AG-9I; Tue, 05 Feb 2013 13:15:12 +0000 Date: Tue, 05 Feb 2013 13:15:12 +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 39 (CVE-2013-0216, CVE-2013-0217) - Linux netback DoS via malicious guest ring. X-BeenThere: xen-users@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-2013-0216,CVE-2013-0217 / XSA-39 version 2 Linux netback DoS via malicious guest ring. UPDATES IN VERSION 2 ==================== Public release. ISSUE DESCRIPTION ================= The Xen netback implementation contains a couple of flaws which can allow a guest to cause a DoS in the backend domain, potentially affecting other domains in the system. CVE-2013-0216 is a failure to sanity check the ring producer/consumer pointers which can allow a guest to cause netback to loop for an extended period preventing other work from occurring. CVE-2013-0217 is a memory leak on an error path which is guest triggerable. IMPACT ====== A malicious guest can mount a DoS affecting the entire system. VULNERABLE SYSTEMS ================== All systems running guests with access to PV network devices are vulnerable. CVE-2013-0216 affects both mainline ("pvops") and classic-Xen patch kernels. CVE-2013-0217 affects only mainline ("pvops") kernels. MITIGATION ========== Running HVM guests with only emulated or passthrough NICs or PV guests with only passthrough NICs will avoid this vulnerability. RESOLUTION ========== Applying the appropriate attached patches in sequence resolves this issue. xsa39-pvops-*.patch Apply to mainline Linux 3.8-rc2 xsa39-classic-*.patch Apply to linux-2.6.18-xen tree. All patches for the given branch should be applied in numerical order. $ sha256sum xsa39*.patch 4b75961673b940f5eb31451080dd668b9119eb88db1df44db1a3ba4b0d037ce1 xsa39-classic-0001-xen-netback-garbage-ring.patch 096143750b99eb2d88970338c3f9debfbbfdaef766525a620281b28528ebe0ce xsa39-classic-0002-xen-netback-wrap-around.patch 99cf93e37985908243b974cc726f57e592e62ae005eca52969f11fb6fdea6fb5 xsa39-pvops-0001-xen-netback-shutdown-the-ring-if-it-contains-garbage.patch e0c4226b0910ca455f22ae117e8346d87053e9faf03ec155dd6c31e2f58a1969 xsa39-pvops-0002-xen-netback-don-t-leak-pages-on-failure-in-xen_netbk.patch 70e6cb644a57cdda7f29eb86086a8e697706c3fc974a44c52322e451fd6b9d5c xsa39-pvops-0003-xen-netback-free-already-allocated-memory-on-failure.patch 5d0db59bbd5ad3a7efae78a6c26fc2491b7c553e5519dd946d1422a116af73dd xsa39-pvops-0004-netback-correct-netbk_tx_err-to-handle-wrap-around.patch $ -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) iQEcBAEBAgAGBQJREQI5AAoJEIP+FMlX6CvZLbcIAL7gpD+EzDjb+g3ZlORl1jPV +icqyDoPWeWructbggY+YcJJc2IavNrRXBSN/9edSTUXSi7YTW+Tjeh8bcLza1JM McWKxPtJB8CKEIAjAeT8qMVaNUNQuJQTtTLtXHGuQE6xwxK8YmgLzQSx91OOp9Bx 49GK1Ptnp7bQoEoc7B3oN6GXr/hs/FvaD0Cr481yUxXX1GxV+AL7sxXiJ4kXu1rE UTSLFAzUfw1KWI5wP3GQCREhysCvgIq4mZyD5+TF8MUagpg+m1aURs2AUUxrJ/Zw o+LVEKWYRsTtWIRtwYOdPHn73bllyPOrBgimTDBM9rY9CztOnN8yoPRlUz0Sux0= =UhBt -----END PGP SIGNATURE----- --=separator Content-Type: application/octet-stream; name="xsa39-classic-0001-xen-netback-garbage-ring.patch" Content-Disposition: attachment; filename="xsa39-classic-0001-xen-netback-garbage-ring.patch" Content-Transfer-Encoding: base64 bmV0YmFjazogc2h1dGRvd24gdGhlIHJpbmcgaWYgaXQgY29udGFpbnMgZ2Fy YmFnZQoKQSBidWdneSBvciBtYWxpY2lvdXMgZnJvbnRlbmQgc2hvdWxkIG5v dCBiZSBhYmxlIHRvIGNvbmZ1c2UgbmV0YmFjay4KSWYgd2Ugc3BvdCBhbnl0 aGluZyB3aGljaCBpcyBub3QgYXMgaXQgc2hvdWxkIGJlIHRoZW4gc2h1dGRv d24gdGhlCmRldmljZSBhbmQgZG9uJ3QgdHJ5IHRvIGNvbnRpbnVlIHdpdGgg dGhlIHJpbmcgaW4gYSBwb3RlbnRpYWxseQpob3N0aWxlIHN0YXRlLiBXZWxs IGJlaGF2ZWQgYW5kIG5vbi1ob3N0aWxlIGZyb250ZW5kcyB3aWxsIG5vdCBi ZQpwZW5hbGlzZWQuCgpBcyB3ZWxsIGFzIG1ha2luZyB0aGUgZXhpc3Rpbmcg Y2hlY2tzIGZvciBzdWNoIGVycm9ycyBmYXRhbCBhbHNvIGFkZCBhCm5ldyBj aGVjayB0aGF0IGVuc3VyZXMgdGhhdCB0aGVyZSBpc24ndCBhbiBpbnNhbmUg bnVtYmVyIG9mIHJlcXVlc3RzCm9uIHRoZSByaW5nIChpLmUuIG1vcmUgdGhh biB3b3VsZCBmaXQgaW4gdGhlIHJpbmcpLiBJZiB0aGUgcmluZwpjb250YWlu cyBnYXJiYWdlIHRoZW4gcHJldmlvdXNseSBpcyB3YXMgcG9zc2libGUgdG8g bG9vcCBvdmVyIHRoaXMKaW5zYW5lIG51bWJlciwgZ2V0dGluZyBhbiBlcnJv ciBlYWNoIHRpbWUgYW5kIHRoZXJlZm9yZSBub3QgZ2VuZXJhdGluZwphbnkg bW9yZSBwZW5kaW5nIHJlcXVlc3RzIGFuZCB0aGVyZWZvcmUgbm90IGV4aXRp bmcgdGhlIGxvb3AgaW4KeGVuX25ldGJrX3R4X2J1aWxkX2dvcHMgZm9yIGFu IGV4dGVybmRlZCBwZXJpb2QuCgpBbHNvIHR1cm4gdmFyaW91cyBuZXRkZXZf ZGJnIGNhbGxzIHdoaWNoIG5vIHByZWNpcGl0YXRlIGEgZmF0YWwgZXJyb3IK aW50byBuZXRkZXZfZXJyLCB0aGV5IGFyZSByYXRlIGxpbWl0ZWQgYmVjYXVz ZSB0aGUgZGV2aWNlIGlzIHNodXRkb3duCmFmdGVyd2FyZHMuCgpUaGlzIGZp eGVzIGF0IGxlYXN0IG9uZSBrbm93biBEb1Mvc29mdGxvY2t1cCBvZiB0aGUg YmFja2VuZCBkb21haW4uCgpTaWduZWQtb2ZmLWJ5OiBJYW4gQ2FtcGJlbGwg PGlhbi5jYW1wYmVsbEBjaXRyaXguY29tPgpTaWduZWQtb2ZmLWJ5OiBKYW4g QmV1bGljaCA8SkJldWxpY2hAc3VzZS5jb20+CgotLS0gYS9kcml2ZXJzL3hl bi9uZXRiYWNrL2NvbW1vbi5oCisrKyBiL2RyaXZlcnMveGVuL25ldGJhY2sv Y29tbW9uLmgKQEAgLTIwNCw2ICsyMDQsOSBAQCBpbnQgbmV0aWZfYmVfc3Rh cnRfeG1pdChzdHJ1Y3Qgc2tfYnVmZiAqCiBzdHJ1Y3QgbmV0X2RldmljZV9z dGF0cyAqbmV0aWZfYmVfZ2V0X3N0YXRzKHN0cnVjdCBuZXRfZGV2aWNlICpk ZXYpOwogaXJxcmV0dXJuX3QgbmV0aWZfYmVfaW50KGludCBpcnEsIHZvaWQg KmRldl9pZCwgc3RydWN0IHB0X3JlZ3MgKnJlZ3MpOwogCisvKiBQcmV2ZW50 IHRoZSBkZXZpY2UgZnJvbSBnZW5lcmF0aW5nIGFueSBmdXJ0aGVyIHRyYWZm aWMuICovCit2b2lkIHhlbnZpZl9jYXJyaWVyX29mZihuZXRpZl90ICpuZXRp Zik7CisKIHN0YXRpYyBpbmxpbmUgaW50IG5ldGJrX2Nhbl9xdWV1ZShzdHJ1 Y3QgbmV0X2RldmljZSAqZGV2KQogewogCW5ldGlmX3QgKm5ldGlmID0gbmV0 ZGV2X3ByaXYoZGV2KTsKLS0tIGEvZHJpdmVycy94ZW4vbmV0YmFjay9pbnRl cmZhY2UuYworKysgYi9kcml2ZXJzL3hlbi9uZXRiYWNrL2ludGVyZmFjZS5j CkBAIC0zNDcsMTkgKzM0NywyMyBAQCBlcnJfcng6CiAJcmV0dXJuIGVycjsK IH0KIAordm9pZCB4ZW52aWZfY2Fycmllcl9vZmYobmV0aWZfdCAqbmV0aWYp Cit7CisJcnRubF9sb2NrKCk7CisJbmV0YmFja19jYXJyaWVyX29mZihuZXRp Zik7CisJbmV0aWZfY2Fycmllcl9vZmYobmV0aWYtPmRldik7IC8qIGRpc2Nh cmQgcXVldWVkIHBhY2tldHMgKi8KKwlpZiAobmV0aWZfcnVubmluZyhuZXRp Zi0+ZGV2KSkKKwkJX19uZXRpZl9kb3duKG5ldGlmKTsKKwlydG5sX3VubG9j aygpOworCW5ldGlmX3B1dChuZXRpZik7Cit9CisKIHZvaWQgbmV0aWZfZGlz Y29ubmVjdChzdHJ1Y3QgYmFja2VuZF9pbmZvICpiZSkKIHsKIAluZXRpZl90 ICpuZXRpZiA9IGJlLT5uZXRpZjsKIAotCWlmIChuZXRiYWNrX2NhcnJpZXJf b2sobmV0aWYpKSB7Ci0JCXJ0bmxfbG9jaygpOwotCQluZXRiYWNrX2NhcnJp ZXJfb2ZmKG5ldGlmKTsKLQkJbmV0aWZfY2Fycmllcl9vZmYobmV0aWYtPmRl dik7IC8qIGRpc2NhcmQgcXVldWVkIHBhY2tldHMgKi8KLQkJaWYgKG5ldGlm X3J1bm5pbmcobmV0aWYtPmRldikpCi0JCQlfX25ldGlmX2Rvd24obmV0aWYp OwotCQlydG5sX3VubG9jaygpOwotCQluZXRpZl9wdXQobmV0aWYpOwotCX0K KwlpZiAobmV0YmFja19jYXJyaWVyX29rKG5ldGlmKSkKKwkJeGVudmlmX2Nh cnJpZXJfb2ZmKG5ldGlmKTsKIAogCWF0b21pY19kZWMoJm5ldGlmLT5yZWZj bnQpOwogCXdhaXRfZXZlbnQobmV0aWYtPndhaXRpbmdfdG9fZnJlZSwgYXRv bWljX3JlYWQoJm5ldGlmLT5yZWZjbnQpID09IDApOwotLS0gYS9kcml2ZXJz L3hlbi9uZXRiYWNrL25ldGJhY2suYworKysgYi9kcml2ZXJzL3hlbi9uZXRi YWNrL25ldGJhY2suYwpAQCAtMTAyMCw2ICsxMDIwLDE0IEBAIHN0YXRpYyB2 b2lkIG5ldGJrX3R4X2VycihuZXRpZl90ICpuZXRpZiwKIAluZXRpZl9wdXQo bmV0aWYpOwogfQogCitzdGF0aWMgdm9pZCBuZXRia19mYXRhbF90eF9lcnIo bmV0aWZfdCAqbmV0aWYpCit7CisJcHJpbnRrKEtFUk5fRVJSICIlczogZmF0 YWwgZXJyb3I7IGRpc2FibGluZyBkZXZpY2VcbiIsCisJICAgICAgIG5ldGlm LT5kZXYtPm5hbWUpOworCXhlbnZpZl9jYXJyaWVyX29mZihuZXRpZik7CisJ bmV0aWZfcHV0KG5ldGlmKTsKK30KKwogc3RhdGljIGludCBuZXRia19jb3Vu dF9yZXF1ZXN0cyhuZXRpZl90ICpuZXRpZiwgbmV0aWZfdHhfcmVxdWVzdF90 ICpmaXJzdCwKIAkJCQluZXRpZl90eF9yZXF1ZXN0X3QgKnR4cCwgaW50IHdv cmtfdG9fZG8pCiB7CkBAIC0xMDMxLDE5ICsxMDM5LDI1IEBAIHN0YXRpYyBp bnQgbmV0YmtfY291bnRfcmVxdWVzdHMobmV0aWZfdCAKIAogCWRvIHsKIAkJ aWYgKGZyYWdzID49IHdvcmtfdG9fZG8pIHsKLQkJCURQUklOVEsoIk5lZWQg bW9yZSBmcmFnc1xuIik7CisJCQlwcmludGsoS0VSTl9FUlIgIiVzOiBOZWVk IG1vcmUgZnJhZ3NcbiIsCisJCQkgICAgICAgbmV0aWYtPmRldi0+bmFtZSk7 CisJCQluZXRia19mYXRhbF90eF9lcnIobmV0aWYpOwogCQkJcmV0dXJuIC1m cmFnczsKIAkJfQogCiAJCWlmICh1bmxpa2VseShmcmFncyA+PSBNQVhfU0tC X0ZSQUdTKSkgewotCQkJRFBSSU5USygiVG9vIG1hbnkgZnJhZ3NcbiIpOwor CQkJcHJpbnRrKEtFUk5fRVJSICIlczogVG9vIG1hbnkgZnJhZ3NcbiIsCisJ CQkgICAgICAgbmV0aWYtPmRldi0+bmFtZSk7CisJCQluZXRia19mYXRhbF90 eF9lcnIobmV0aWYpOwogCQkJcmV0dXJuIC1mcmFnczsKIAkJfQogCiAJCW1l bWNweSh0eHAsIFJJTkdfR0VUX1JFUVVFU1QoJm5ldGlmLT50eCwgY29ucyAr IGZyYWdzKSwKIAkJICAgICAgIHNpemVvZigqdHhwKSk7CiAJCWlmICh0eHAt PnNpemUgPiBmaXJzdC0+c2l6ZSkgewotCQkJRFBSSU5USygiRnJhZ3MgZ2Fs b3JlXG4iKTsKKwkJCXByaW50ayhLRVJOX0VSUiAiJXM6IEZyYWcgaXMgYmln Z2VyIHRoYW4gZnJhbWUuXG4iLAorCQkJICAgICAgIG5ldGlmLT5kZXYtPm5h bWUpOworCQkJbmV0YmtfZmF0YWxfdHhfZXJyKG5ldGlmKTsKIAkJCXJldHVy biAtZnJhZ3M7CiAJCX0KIApAQCAtMTA1MSw4ICsxMDY1LDkgQEAgc3RhdGlj IGludCBuZXRia19jb3VudF9yZXF1ZXN0cyhuZXRpZl90IAogCQlmcmFncysr OwogCiAJCWlmICh1bmxpa2VseSgodHhwLT5vZmZzZXQgKyB0eHAtPnNpemUp ID4gUEFHRV9TSVpFKSkgewotCQkJRFBSSU5USygidHhwLT5vZmZzZXQ6ICV4 LCBzaXplOiAldVxuIiwKLQkJCQl0eHAtPm9mZnNldCwgdHhwLT5zaXplKTsK KwkJCXByaW50ayhLRVJOX0VSUiAiJXM6IHR4cC0+b2Zmc2V0OiAleCwgc2l6 ZTogJXVcbiIsCisJCQkgICAgICAgbmV0aWYtPmRldi0+bmFtZSwgdHhwLT5v ZmZzZXQsIHR4cC0+c2l6ZSk7CisJCQluZXRia19mYXRhbF90eF9lcnIobmV0 aWYpOwogCQkJcmV0dXJuIC1mcmFnczsKIAkJfQogCX0gd2hpbGUgKCh0eHAr KyktPmZsYWdzICYgTkVUVFhGX21vcmVfZGF0YSk7CkBAIC0xMTk1LDcgKzEy MTAsOSBAQCBpbnQgbmV0YmtfZ2V0X2V4dHJhcyhuZXRpZl90ICpuZXRpZiwg c3RyCiAKIAlkbyB7CiAJCWlmICh1bmxpa2VseSh3b3JrX3RvX2RvLS0gPD0g MCkpIHsKLQkJCURQUklOVEsoIk1pc3NpbmcgZXh0cmEgaW5mb1xuIik7CisJ CQlwcmludGsoS0VSTl9FUlIgIiVzOiBNaXNzaW5nIGV4dHJhIGluZm9cbiIs CisJCQkgICAgICAgbmV0aWYtPmRldi0+bmFtZSk7CisJCQluZXRia19mYXRh bF90eF9lcnIobmV0aWYpOwogCQkJcmV0dXJuIC1FQkFEUjsKIAkJfQogCkBA IC0xMjA0LDcgKzEyMjEsOSBAQCBpbnQgbmV0YmtfZ2V0X2V4dHJhcyhuZXRp Zl90ICpuZXRpZiwgc3RyCiAJCWlmICh1bmxpa2VseSghZXh0cmEudHlwZSB8 fAogCQkJICAgICBleHRyYS50eXBlID49IFhFTl9ORVRJRl9FWFRSQV9UWVBF X01BWCkpIHsKIAkJCW5ldGlmLT50eC5yZXFfY29ucyA9ICsrY29uczsKLQkJ CURQUklOVEsoIkludmFsaWQgZXh0cmEgdHlwZTogJWRcbiIsIGV4dHJhLnR5 cGUpOworCQkJcHJpbnRrKEtFUk5fRVJSICIlczogSW52YWxpZCBleHRyYSB0 eXBlOiAlZFxuIiwKKwkJCSAgICAgICBuZXRpZi0+ZGV2LT5uYW1lLCBleHRy YS50eXBlKTsKKwkJCW5ldGJrX2ZhdGFsX3R4X2VycihuZXRpZik7CiAJCQly ZXR1cm4gLUVJTlZBTDsKIAkJfQogCkBAIC0xMjE1LDE2ICsxMjM0LDIxIEBA IGludCBuZXRia19nZXRfZXh0cmFzKG5ldGlmX3QgKm5ldGlmLCBzdHIKIAly ZXR1cm4gd29ya190b19kbzsKIH0KIAotc3RhdGljIGludCBuZXRia19zZXRf c2tiX2dzbyhzdHJ1Y3Qgc2tfYnVmZiAqc2tiLCBzdHJ1Y3QgbmV0aWZfZXh0 cmFfaW5mbyAqZ3NvKQorc3RhdGljIGludCBuZXRia19zZXRfc2tiX2dzbyhu ZXRpZl90ICpuZXRpZiwgc3RydWN0IHNrX2J1ZmYgKnNrYiwKKwkJCSAgICAg c3RydWN0IG5ldGlmX2V4dHJhX2luZm8gKmdzbykKIHsKIAlpZiAoIWdzby0+ dS5nc28uc2l6ZSkgewotCQlEUFJJTlRLKCJHU08gc2l6ZSBtdXN0IG5vdCBi ZSB6ZXJvLlxuIik7CisJCXByaW50ayhLRVJOX0VSUiAiJXM6IEdTTyBzaXpl IG11c3Qgbm90IGJlIHplcm8uXG4iLAorCQkgICAgICAgbmV0aWYtPmRldi0+ bmFtZSk7CisJCW5ldGJrX2ZhdGFsX3R4X2VycihuZXRpZik7CiAJCXJldHVy biAtRUlOVkFMOwogCX0KIAogCS8qIEN1cnJlbnRseSBvbmx5IFRDUHY0IFMu Ty4gaXMgc3VwcG9ydGVkLiAqLwogCWlmIChnc28tPnUuZ3NvLnR5cGUgIT0g WEVOX05FVElGX0dTT19UWVBFX1RDUFY0KSB7Ci0JCURQUklOVEsoIkJhZCBH U08gdHlwZSAlZC5cbiIsIGdzby0+dS5nc28udHlwZSk7CisJCXByaW50ayhL RVJOX0VSUiAiJXM6IEJhZCBHU08gdHlwZSAlZC5cbiIsCisJCSAgICAgICBu ZXRpZi0+ZGV2LT5uYW1lLCBnc28tPnUuZ3NvLnR5cGUpOworCQluZXRia19m YXRhbF90eF9lcnIobmV0aWYpOwogCQlyZXR1cm4gLUVJTlZBTDsKIAl9CiAK QEAgLTEyNTksOSArMTI4MywyNSBAQCBzdGF0aWMgdm9pZCBuZXRfdHhfYWN0 aW9uKHVuc2lnbmVkIGxvbmcgCiAJCSFsaXN0X2VtcHR5KCZuZXRfc2NoZWR1 bGVfbGlzdCkpIHsKIAkJLyogR2V0IGEgbmV0aWYgZnJvbSB0aGUgbGlzdCB3 aXRoIHdvcmsgdG8gZG8uICovCiAJCW5ldGlmID0gcG9sbF9uZXRfc2NoZWR1 bGVfbGlzdCgpOworCQkvKgorCQkgKiBUaGlzIGNhbiBzb21ldGltZXMgaGFw cGVuIGJlY2F1c2UgdGhlIHRlc3Qgb2YKKwkJICogbGlzdF9lbXB0eShuZXRf c2NoZWR1bGVfbGlzdCkgYXQgdGhlIHRvcCBvZiB0aGUKKwkJICogbG9vcCBp cyB1bmxvY2tlZC4gIEp1c3QgZ28gYmFjayBhbmQgaGF2ZSBhbm90aGVyCisJ CSAqIGxvb2suCisJCSAqLwogCQlpZiAoIW5ldGlmKQogCQkJY29udGludWU7 CiAKKwkJaWYgKG5ldGlmLT50eC5zcmluZy0+cmVxX3Byb2QgLSBuZXRpZi0+ dHgucmVxX2NvbnMgPgorCQkgICAgTkVUX1RYX1JJTkdfU0laRSkgeworCQkJ cHJpbnRrKEtFUk5fRVJSICIlczogSW1wb3NzaWJsZSBudW1iZXIgb2YgcmVx dWVzdHMuICIKKwkJCSAgICAgICAicmVxX3Byb2QgJXUsIHJlcV9jb25zICV1 LCBzaXplICVsdVxuIiwKKwkJCSAgICAgICBuZXRpZi0+ZGV2LT5uYW1lLCBu ZXRpZi0+dHguc3JpbmctPnJlcV9wcm9kLAorCQkJICAgICAgIG5ldGlmLT50 eC5yZXFfY29ucywgTkVUX1RYX1JJTkdfU0laRSk7CisJCQluZXRia19mYXRh bF90eF9lcnIobmV0aWYpOworCQkJY29udGludWU7CisJCX0KKwogCQlSSU5H X0ZJTkFMX0NIRUNLX0ZPUl9SRVFVRVNUUygmbmV0aWYtPnR4LCB3b3JrX3Rv X2RvKTsKIAkJaWYgKCF3b3JrX3RvX2RvKSB7CiAJCQluZXRpZl9wdXQobmV0 aWYpOwpAQCAtMTMxMywxNyArMTM1MywxNCBAQCBzdGF0aWMgdm9pZCBuZXRf dHhfYWN0aW9uKHVuc2lnbmVkIGxvbmcgCiAJCQl3b3JrX3RvX2RvID0gbmV0 YmtfZ2V0X2V4dHJhcyhuZXRpZiwgZXh0cmFzLAogCQkJCQkJICAgICAgd29y a190b19kbyk7CiAJCQlpID0gbmV0aWYtPnR4LnJlcV9jb25zOwotCQkJaWYg KHVubGlrZWx5KHdvcmtfdG9fZG8gPCAwKSkgewotCQkJCW5ldGJrX3R4X2Vy cihuZXRpZiwgJnR4cmVxLCBpKTsKKwkJCWlmICh1bmxpa2VseSh3b3JrX3Rv X2RvIDwgMCkpCiAJCQkJY29udGludWU7Ci0JCQl9CiAJCX0KIAogCQlyZXQg PSBuZXRia19jb3VudF9yZXF1ZXN0cyhuZXRpZiwgJnR4cmVxLCB0eGZyYWdz LCB3b3JrX3RvX2RvKTsKLQkJaWYgKHVubGlrZWx5KHJldCA8IDApKSB7Ci0J CQluZXRia190eF9lcnIobmV0aWYsICZ0eHJlcSwgaSAtIHJldCk7CisJCWlm ICh1bmxpa2VseShyZXQgPCAwKSkKIAkJCWNvbnRpbnVlOwotCQl9CisKIAkJ aSArPSByZXQ7CiAKIAkJaWYgKHVubGlrZWx5KHR4cmVxLnNpemUgPCBFVEhf SExFTikpIHsKQEAgLTEzMzQsMTAgKzEzNzEsMTAgQEAgc3RhdGljIHZvaWQg bmV0X3R4X2FjdGlvbih1bnNpZ25lZCBsb25nIAogCiAJCS8qIE5vIGNyb3Nz aW5nIGEgcGFnZSBhcyB0aGUgcGF5bG9hZCBtdXN0bid0IGZyYWdtZW50LiAq LwogCQlpZiAodW5saWtlbHkoKHR4cmVxLm9mZnNldCArIHR4cmVxLnNpemUp ID4gUEFHRV9TSVpFKSkgewotCQkJRFBSSU5USygidHhyZXEub2Zmc2V0OiAl eCwgc2l6ZTogJXUsIGVuZDogJWx1XG4iLCAKLQkJCQl0eHJlcS5vZmZzZXQs IHR4cmVxLnNpemUsIAotCQkJCSh0eHJlcS5vZmZzZXQgJn5QQUdFX01BU0sp ICsgdHhyZXEuc2l6ZSk7Ci0JCQluZXRia190eF9lcnIobmV0aWYsICZ0eHJl cSwgaSk7CisJCQlwcmludGsoS0VSTl9FUlIgIiVzOiB0eHJlcS5vZmZzZXQ6 ICV4LCBzaXplOiAldSwgZW5kOiAlbHVcbiIsCisJCQkgICAgICAgbmV0aWYt PmRldi0+bmFtZSwgdHhyZXEub2Zmc2V0LCB0eHJlcS5zaXplLAorCQkJICAg ICAgICh0eHJlcS5vZmZzZXQgJiB+UEFHRV9NQVNLKSArIHR4cmVxLnNpemUp OworCQkJbmV0YmtfZmF0YWxfdHhfZXJyKG5ldGlmKTsKIAkJCWNvbnRpbnVl OwogCQl9CiAKQEAgLTEzNjIsOSArMTM5OSw5IEBAIHN0YXRpYyB2b2lkIG5l dF90eF9hY3Rpb24odW5zaWduZWQgbG9uZyAKIAkJCXN0cnVjdCBuZXRpZl9l eHRyYV9pbmZvICpnc287CiAJCQlnc28gPSAmZXh0cmFzW1hFTl9ORVRJRl9F WFRSQV9UWVBFX0dTTyAtIDFdOwogCi0JCQlpZiAobmV0Ymtfc2V0X3NrYl9n c28oc2tiLCBnc28pKSB7CisJCQlpZiAobmV0Ymtfc2V0X3NrYl9nc28obmV0 aWYsIHNrYiwgZ3NvKSkgeworCQkJCS8qIEZhaWx1cmUgaW4gbmV0Ymtfc2V0 X3NrYl9nc28gaXMgZmF0YWwuICovCiAJCQkJa2ZyZWVfc2tiKHNrYik7Ci0J CQkJbmV0YmtfdHhfZXJyKG5ldGlmLCAmdHhyZXEsIGkpOwogCQkJCWNvbnRp bnVlOwogCQkJfQogCQl9Cg== --=separator Content-Type: application/octet-stream; name="xsa39-classic-0002-xen-netback-wrap-around.patch" Content-Disposition: attachment; filename="xsa39-classic-0002-xen-netback-wrap-around.patch" Content-Transfer-Encoding: base64 bmV0YmFjazogY29ycmVjdCBuZXRia190eF9lcnIoKSB0byBoYW5kbGUgd3Jh cCBhcm91bmQKClNpZ25lZC1vZmYtYnk6IElhbiBDYW1wYmVsbCA8aWFuLmNh bXBiZWxsQGNpdHJpeC5jb20+ClNpZ25lZC1vZmYtYnk6IEphbiBCZXVsaWNo IDxKQmV1bGljaEBzdXNlLmNvbT4KCi0tLSBhL2RyaXZlcnMveGVuL25ldGJh Y2svbmV0YmFjay5jCisrKyBiL2RyaXZlcnMveGVuL25ldGJhY2svbmV0YmFj ay5jCkBAIC0xMDExLDcgKzEwMTEsNyBAQCBzdGF0aWMgdm9pZCBuZXRia190 eF9lcnIobmV0aWZfdCAqbmV0aWYsCiAKIAlkbyB7CiAJCW1ha2VfdHhfcmVz cG9uc2UobmV0aWYsIHR4cCwgTkVUSUZfUlNQX0VSUk9SKTsKLQkJaWYgKGNv bnMgPj0gZW5kKQorCQlpZiAoY29ucyA9PSBlbmQpCiAJCQlicmVhazsKIAkJ dHhwID0gUklOR19HRVRfUkVRVUVTVCgmbmV0aWYtPnR4LCBjb25zKyspOwog CX0gd2hpbGUgKDEpOwo= --=separator Content-Type: application/octet-stream; name="xsa39-pvops-0001-xen-netback-shutdown-the-ring-if-it-contains-garbage.patch" Content-Disposition: attachment; filename="xsa39-pvops-0001-xen-netback-shutdown-the-ring-if-it-contains-garbage.patch" Content-Transfer-Encoding: base64 RnJvbSA3ZGQ3Y2U0NDU5M2E4YzRjNzE1ZmE2NjUwMjdhZjhlMDcyNDVjOGNm IE1vbiBTZXAgMTcgMDA6MDA6MDAgMjAwMQpGcm9tOiBJYW4gQ2FtcGJlbGwg PGlhbi5jYW1wYmVsbEBjaXRyaXguY29tPgpEYXRlOiBGcmksIDExIEphbiAy MDEzIDE0OjI2OjI5ICswMDAwClN1YmplY3Q6IFtQQVRDSCAxLzRdIHhlbi9u ZXRiYWNrOiBzaHV0ZG93biB0aGUgcmluZyBpZiBpdCBjb250YWlucyBnYXJi YWdlLgoKQSBidWdneSBvciBtYWxpY2lvdXMgZnJvbnRlbmQgc2hvdWxkIG5v dCBiZSBhYmxlIHRvIGNvbmZ1c2UgbmV0YmFjay4KSWYgd2Ugc3BvdCBhbnl0 aGluZyB3aGljaCBpcyBub3QgYXMgaXQgc2hvdWxkIGJlIHRoZW4gc2h1dGRv d24gdGhlCmRldmljZSBhbmQgZG9uJ3QgdHJ5IHRvIGNvbnRpbnVlIHdpdGgg dGhlIHJpbmcgaW4gYSBwb3RlbnRpYWxseQpob3N0aWxlIHN0YXRlLiBXZWxs IGJlaGF2ZWQgYW5kIG5vbi1ob3N0aWxlIGZyb250ZW5kcyB3aWxsIG5vdCBi ZQpwZW5hbGlzZWQuCgpBcyB3ZWxsIGFzIG1ha2luZyB0aGUgZXhpc3Rpbmcg Y2hlY2tzIGZvciBzdWNoIGVycm9ycyBmYXRhbCBhbHNvIGFkZCBhCm5ldyBj aGVjayB0aGF0IGVuc3VyZXMgdGhhdCB0aGVyZSBpc24ndCBhbiBpbnNhbmUg bnVtYmVyIG9mIHJlcXVlc3RzCm9uIHRoZSByaW5nIChpLmUuIG1vcmUgdGhh biB3b3VsZCBmaXQgaW4gdGhlIHJpbmcpLiBJZiB0aGUgcmluZwpjb250YWlu cyBnYXJiYWdlIHRoZW4gcHJldmlvdXNseSBpcyB3YXMgcG9zc2libGUgdG8g bG9vcCBvdmVyIHRoaXMKaW5zYW5lIG51bWJlciwgZ2V0dGluZyBhbiBlcnJv ciBlYWNoIHRpbWUgYW5kIHRoZXJlZm9yZSBub3QgZ2VuZXJhdGluZwphbnkg bW9yZSBwZW5kaW5nIHJlcXVlc3RzIGFuZCB0aGVyZWZvcmUgbm90IGV4aXRp bmcgdGhlIGxvb3AgaW4KeGVuX25ldGJrX3R4X2J1aWxkX2dvcHMgZm9yIGFu IGV4dGVybmRlZCBwZXJpb2QuCgpBbHNvIHR1cm4gdmFyaW91cyBuZXRkZXZf ZGJnIGNhbGxzIHdoaWNoIG5vIHByZWNpcGl0YXRlIGEgZmF0YWwgZXJyb3IK aW50byBuZXRkZXZfZXJyLCB0aGV5IGFyZSByYXRlIGxpbWl0ZWQgYmVjYXVz ZSB0aGUgZGV2aWNlIGlzIHNodXRkb3duCmFmdGVyd2FyZHMuCgpUaGlzIGZp eGVzIGF0IGxlYXN0IG9uZSBrbm93biBEb1Mvc29mdGxvY2t1cCBvZiB0aGUg YmFja2VuZCBkb21haW4uCgpTaWduZWQtb2ZmLWJ5OiBJYW4gQ2FtcGJlbGwg PGlhbi5jYW1wYmVsbEBjaXRyaXguY29tPgpSZXZpZXdlZC1ieTogS29ucmFk IFJ6ZXN6dXRlayBXaWxrIDxrb25yYWQud2lsa0BvcmFjbGUuY29tPgpBY2tl ZC1ieTogSmFuIEJldWxpY2ggPEpCZXVsaWNoQHN1c2UuY29tPgotLS0KIGRy aXZlcnMvbmV0L3hlbi1uZXRiYWNrL2NvbW1vbi5oICAgIHwgICAgMyArKwog ZHJpdmVycy9uZXQveGVuLW5ldGJhY2svaW50ZXJmYWNlLmMgfCAgIDIzICsr KysrKysrLS0tLS0KIGRyaXZlcnMvbmV0L3hlbi1uZXRiYWNrL25ldGJhY2su YyAgIHwgICA2MyArKysrKysrKysrKysrKysrKysrKysrKysrLS0tLS0tLS0t CiAzIGZpbGVzIGNoYW5nZWQsIDYzIGluc2VydGlvbnMoKyksIDI2IGRlbGV0 aW9ucygtKQoKZGlmZiAtLWdpdCBhL2RyaXZlcnMvbmV0L3hlbi1uZXRiYWNr L2NvbW1vbi5oIGIvZHJpdmVycy9uZXQveGVuLW5ldGJhY2svY29tbW9uLmgK aW5kZXggOTRiNzljMy4uOWQ3ZjE3MiAxMDA2NDQKLS0tIGEvZHJpdmVycy9u ZXQveGVuLW5ldGJhY2svY29tbW9uLmgKKysrIGIvZHJpdmVycy9uZXQveGVu LW5ldGJhY2svY29tbW9uLmgKQEAgLTE1MSw2ICsxNTEsOSBAQCB2b2lkIHhl bl9uZXRia19xdWV1ZV90eF9za2Ioc3RydWN0IHhlbnZpZiAqdmlmLCBzdHJ1 Y3Qgc2tfYnVmZiAqc2tiKTsKIC8qIE5vdGlmeSB4ZW52aWYgdGhhdCByaW5n IG5vdyBoYXMgc3BhY2UgdG8gc2VuZCBhbiBza2IgdG8gdGhlIGZyb250ZW5k ICovCiB2b2lkIHhlbnZpZl9ub3RpZnlfdHhfY29tcGxldGlvbihzdHJ1Y3Qg eGVudmlmICp2aWYpOwogCisvKiBQcmV2ZW50IHRoZSBkZXZpY2UgZnJvbSBn ZW5lcmF0aW5nIGFueSBmdXJ0aGVyIHRyYWZmaWMuICovCit2b2lkIHhlbnZp Zl9jYXJyaWVyX29mZihzdHJ1Y3QgeGVudmlmICp2aWYpOworCiAvKiBSZXR1 cm5zIG51bWJlciBvZiByaW5nIHNsb3RzIHJlcXVpcmVkIHRvIHNlbmQgYW4g c2tiIHRvIHRoZSBmcm9udGVuZCAqLwogdW5zaWduZWQgaW50IHhlbl9uZXRi a19jb3VudF9za2Jfc2xvdHMoc3RydWN0IHhlbnZpZiAqdmlmLCBzdHJ1Y3Qg c2tfYnVmZiAqc2tiKTsKIApkaWZmIC0tZ2l0IGEvZHJpdmVycy9uZXQveGVu LW5ldGJhY2svaW50ZXJmYWNlLmMgYi9kcml2ZXJzL25ldC94ZW4tbmV0YmFj ay9pbnRlcmZhY2UuYwppbmRleCBiN2Q0MWY4Li5iOGM1MTkzIDEwMDY0NAot LS0gYS9kcml2ZXJzL25ldC94ZW4tbmV0YmFjay9pbnRlcmZhY2UuYworKysg Yi9kcml2ZXJzL25ldC94ZW4tbmV0YmFjay9pbnRlcmZhY2UuYwpAQCAtMzQz LDE3ICszNDMsMjIgQEAgZXJyOgogCXJldHVybiBlcnI7CiB9CiAKLXZvaWQg eGVudmlmX2Rpc2Nvbm5lY3Qoc3RydWN0IHhlbnZpZiAqdmlmKQordm9pZCB4 ZW52aWZfY2Fycmllcl9vZmYoc3RydWN0IHhlbnZpZiAqdmlmKQogewogCXN0 cnVjdCBuZXRfZGV2aWNlICpkZXYgPSB2aWYtPmRldjsKLQlpZiAobmV0aWZf Y2Fycmllcl9vayhkZXYpKSB7Ci0JCXJ0bmxfbG9jaygpOwotCQluZXRpZl9j YXJyaWVyX29mZihkZXYpOyAvKiBkaXNjYXJkIHF1ZXVlZCBwYWNrZXRzICov Ci0JCWlmIChuZXRpZl9ydW5uaW5nKGRldikpCi0JCQl4ZW52aWZfZG93bih2 aWYpOwotCQlydG5sX3VubG9jaygpOwotCQl4ZW52aWZfcHV0KHZpZik7Ci0J fQorCisJcnRubF9sb2NrKCk7CisJbmV0aWZfY2Fycmllcl9vZmYoZGV2KTsg LyogZGlzY2FyZCBxdWV1ZWQgcGFja2V0cyAqLworCWlmIChuZXRpZl9ydW5u aW5nKGRldikpCisJCXhlbnZpZl9kb3duKHZpZik7CisJcnRubF91bmxvY2so KTsKKwl4ZW52aWZfcHV0KHZpZik7Cit9CisKK3ZvaWQgeGVudmlmX2Rpc2Nv bm5lY3Qoc3RydWN0IHhlbnZpZiAqdmlmKQoreworCWlmIChuZXRpZl9jYXJy aWVyX29rKHZpZi0+ZGV2KSkKKwkJeGVudmlmX2NhcnJpZXJfb2ZmKHZpZik7 CiAKIAlhdG9taWNfZGVjKCZ2aWYtPnJlZmNudCk7CiAJd2FpdF9ldmVudCh2 aWYtPndhaXRpbmdfdG9fZnJlZSwgYXRvbWljX3JlYWQoJnZpZi0+cmVmY250 KSA9PSAwKTsKZGlmZiAtLWdpdCBhL2RyaXZlcnMvbmV0L3hlbi1uZXRiYWNr L25ldGJhY2suYyBiL2RyaXZlcnMvbmV0L3hlbi1uZXRiYWNrL25ldGJhY2su YwppbmRleCBmMmQ2Yjc4Li4xYTQ0OWY5IDEwMDY0NAotLS0gYS9kcml2ZXJz L25ldC94ZW4tbmV0YmFjay9uZXRiYWNrLmMKKysrIGIvZHJpdmVycy9uZXQv eGVuLW5ldGJhY2svbmV0YmFjay5jCkBAIC04ODgsNiArODg4LDEzIEBAIHN0 YXRpYyB2b2lkIG5ldGJrX3R4X2VycihzdHJ1Y3QgeGVudmlmICp2aWYsCiAJ eGVudmlmX3B1dCh2aWYpOwogfQogCitzdGF0aWMgdm9pZCBuZXRia19mYXRh bF90eF9lcnIoc3RydWN0IHhlbnZpZiAqdmlmKQoreworCW5ldGRldl9lcnIo dmlmLT5kZXYsICJmYXRhbCBlcnJvcjsgZGlzYWJsaW5nIGRldmljZVxuIik7 CisJeGVudmlmX2NhcnJpZXJfb2ZmKHZpZik7CisJeGVudmlmX3B1dCh2aWYp OworfQorCiBzdGF0aWMgaW50IG5ldGJrX2NvdW50X3JlcXVlc3RzKHN0cnVj dCB4ZW52aWYgKnZpZiwKIAkJCQlzdHJ1Y3QgeGVuX25ldGlmX3R4X3JlcXVl c3QgKmZpcnN0LAogCQkJCXN0cnVjdCB4ZW5fbmV0aWZfdHhfcmVxdWVzdCAq dHhwLApAQCAtOTAxLDE5ICs5MDgsMjIgQEAgc3RhdGljIGludCBuZXRia19j b3VudF9yZXF1ZXN0cyhzdHJ1Y3QgeGVudmlmICp2aWYsCiAKIAlkbyB7CiAJ CWlmIChmcmFncyA+PSB3b3JrX3RvX2RvKSB7Ci0JCQluZXRkZXZfZGJnKHZp Zi0+ZGV2LCAiTmVlZCBtb3JlIGZyYWdzXG4iKTsKKwkJCW5ldGRldl9lcnIo dmlmLT5kZXYsICJOZWVkIG1vcmUgZnJhZ3NcbiIpOworCQkJbmV0YmtfZmF0 YWxfdHhfZXJyKHZpZik7CiAJCQlyZXR1cm4gLWZyYWdzOwogCQl9CiAKIAkJ aWYgKHVubGlrZWx5KGZyYWdzID49IE1BWF9TS0JfRlJBR1MpKSB7Ci0JCQlu ZXRkZXZfZGJnKHZpZi0+ZGV2LCAiVG9vIG1hbnkgZnJhZ3NcbiIpOworCQkJ bmV0ZGV2X2Vycih2aWYtPmRldiwgIlRvbyBtYW55IGZyYWdzXG4iKTsKKwkJ CW5ldGJrX2ZhdGFsX3R4X2Vycih2aWYpOwogCQkJcmV0dXJuIC1mcmFnczsK IAkJfQogCiAJCW1lbWNweSh0eHAsIFJJTkdfR0VUX1JFUVVFU1QoJnZpZi0+ dHgsIGNvbnMgKyBmcmFncyksCiAJCSAgICAgICBzaXplb2YoKnR4cCkpOwog CQlpZiAodHhwLT5zaXplID4gZmlyc3QtPnNpemUpIHsKLQkJCW5ldGRldl9k YmcodmlmLT5kZXYsICJGcmFncyBnYWxvcmVcbiIpOworCQkJbmV0ZGV2X2Vy cih2aWYtPmRldiwgIkZyYWcgaXMgYmlnZ2VyIHRoYW4gZnJhbWUuXG4iKTsK KwkJCW5ldGJrX2ZhdGFsX3R4X2Vycih2aWYpOwogCQkJcmV0dXJuIC1mcmFn czsKIAkJfQogCkBAIC05MjEsOCArOTMxLDkgQEAgc3RhdGljIGludCBuZXRi a19jb3VudF9yZXF1ZXN0cyhzdHJ1Y3QgeGVudmlmICp2aWYsCiAJCWZyYWdz Kys7CiAKIAkJaWYgKHVubGlrZWx5KCh0eHAtPm9mZnNldCArIHR4cC0+c2l6 ZSkgPiBQQUdFX1NJWkUpKSB7Ci0JCQluZXRkZXZfZGJnKHZpZi0+ZGV2LCAi dHhwLT5vZmZzZXQ6ICV4LCBzaXplOiAldVxuIiwKKwkJCW5ldGRldl9lcnIo dmlmLT5kZXYsICJ0eHAtPm9mZnNldDogJXgsIHNpemU6ICV1XG4iLAogCQkJ CSB0eHAtPm9mZnNldCwgdHhwLT5zaXplKTsKKwkJCW5ldGJrX2ZhdGFsX3R4 X2Vycih2aWYpOwogCQkJcmV0dXJuIC1mcmFnczsKIAkJfQogCX0gd2hpbGUg KCh0eHArKyktPmZsYWdzICYgWEVOX05FVFRYRl9tb3JlX2RhdGEpOwpAQCAt MTA5NSw3ICsxMTA2LDggQEAgc3RhdGljIGludCB4ZW5fbmV0YmtfZ2V0X2V4 dHJhcyhzdHJ1Y3QgeGVudmlmICp2aWYsCiAKIAlkbyB7CiAJCWlmICh1bmxp a2VseSh3b3JrX3RvX2RvLS0gPD0gMCkpIHsKLQkJCW5ldGRldl9kYmcodmlm LT5kZXYsICJNaXNzaW5nIGV4dHJhIGluZm9cbiIpOworCQkJbmV0ZGV2X2Vy cih2aWYtPmRldiwgIk1pc3NpbmcgZXh0cmEgaW5mb1xuIik7CisJCQluZXRi a19mYXRhbF90eF9lcnIodmlmKTsKIAkJCXJldHVybiAtRUJBRFI7CiAJCX0K IApAQCAtMTEwNCw4ICsxMTE2LDkgQEAgc3RhdGljIGludCB4ZW5fbmV0Ymtf Z2V0X2V4dHJhcyhzdHJ1Y3QgeGVudmlmICp2aWYsCiAJCWlmICh1bmxpa2Vs eSghZXh0cmEudHlwZSB8fAogCQkJICAgICBleHRyYS50eXBlID49IFhFTl9O RVRJRl9FWFRSQV9UWVBFX01BWCkpIHsKIAkJCXZpZi0+dHgucmVxX2NvbnMg PSArK2NvbnM7Ci0JCQluZXRkZXZfZGJnKHZpZi0+ZGV2LAorCQkJbmV0ZGV2 X2Vycih2aWYtPmRldiwKIAkJCQkgICAiSW52YWxpZCBleHRyYSB0eXBlOiAl ZFxuIiwgZXh0cmEudHlwZSk7CisJCQluZXRia19mYXRhbF90eF9lcnIodmlm KTsKIAkJCXJldHVybiAtRUlOVkFMOwogCQl9CiAKQEAgLTExMjEsMTMgKzEx MzQsMTUgQEAgc3RhdGljIGludCBuZXRia19zZXRfc2tiX2dzbyhzdHJ1Y3Qg eGVudmlmICp2aWYsCiAJCQkgICAgIHN0cnVjdCB4ZW5fbmV0aWZfZXh0cmFf aW5mbyAqZ3NvKQogewogCWlmICghZ3NvLT51Lmdzby5zaXplKSB7Ci0JCW5l dGRldl9kYmcodmlmLT5kZXYsICJHU08gc2l6ZSBtdXN0IG5vdCBiZSB6ZXJv LlxuIik7CisJCW5ldGRldl9lcnIodmlmLT5kZXYsICJHU08gc2l6ZSBtdXN0 IG5vdCBiZSB6ZXJvLlxuIik7CisJCW5ldGJrX2ZhdGFsX3R4X2Vycih2aWYp OwogCQlyZXR1cm4gLUVJTlZBTDsKIAl9CiAKIAkvKiBDdXJyZW50bHkgb25s eSBUQ1B2NCBTLk8uIGlzIHN1cHBvcnRlZC4gKi8KIAlpZiAoZ3NvLT51Lmdz by50eXBlICE9IFhFTl9ORVRJRl9HU09fVFlQRV9UQ1BWNCkgewotCQluZXRk ZXZfZGJnKHZpZi0+ZGV2LCAiQmFkIEdTTyB0eXBlICVkLlxuIiwgZ3NvLT51 Lmdzby50eXBlKTsKKwkJbmV0ZGV2X2Vycih2aWYtPmRldiwgIkJhZCBHU08g dHlwZSAlZC5cbiIsIGdzby0+dS5nc28udHlwZSk7CisJCW5ldGJrX2ZhdGFs X3R4X2Vycih2aWYpOwogCQlyZXR1cm4gLUVJTlZBTDsKIAl9CiAKQEAgLTEy NjQsOSArMTI3OSwyNiBAQCBzdGF0aWMgdW5zaWduZWQgeGVuX25ldGJrX3R4 X2J1aWxkX2dvcHMoc3RydWN0IHhlbl9uZXRiayAqbmV0YmspCiAKIAkJLyog R2V0IGEgbmV0aWYgZnJvbSB0aGUgbGlzdCB3aXRoIHdvcmsgdG8gZG8uICov CiAJCXZpZiA9IHBvbGxfbmV0X3NjaGVkdWxlX2xpc3QobmV0YmspOworCQkv KgorCQkgKiBUaGlzIGNhbiBzb21ldGltZXMgaGFwcGVuIGJlY2F1c2UgdGhl IHRlc3Qgb2YKKwkJICogbGlzdF9lbXB0eShuZXRfc2NoZWR1bGVfbGlzdCkg YXQgdGhlIHRvcCBvZiB0aGUKKwkJICogbG9vcCBpcyB1bmxvY2tlZC4gIEp1 c3QgZ28gYmFjayBhbmQgaGF2ZSBhbm90aGVyCisJCSAqIGxvb2suCisJCSAq LwogCQlpZiAoIXZpZikKIAkJCWNvbnRpbnVlOwogCisJCWlmICh2aWYtPnR4 LnNyaW5nLT5yZXFfcHJvZCAtIHZpZi0+dHgucmVxX2NvbnMgPgorCQkgICAg WEVOX05FVElGX1RYX1JJTkdfU0laRSkgeworCQkJbmV0ZGV2X2Vycih2aWYt PmRldiwKKwkJCQkgICAiSW1wb3NzaWJsZSBudW1iZXIgb2YgcmVxdWVzdHMu ICIKKwkJCQkgICAicmVxX3Byb2QgJWQsIHJlcV9jb25zICVkLCBzaXplICVs ZFxuIiwKKwkJCQkgICB2aWYtPnR4LnNyaW5nLT5yZXFfcHJvZCwgdmlmLT50 eC5yZXFfY29ucywKKwkJCQkgICBYRU5fTkVUSUZfVFhfUklOR19TSVpFKTsK KwkJCW5ldGJrX2ZhdGFsX3R4X2Vycih2aWYpOworCQkJY29udGludWU7CisJ CX0KKwogCQlSSU5HX0ZJTkFMX0NIRUNLX0ZPUl9SRVFVRVNUUygmdmlmLT50 eCwgd29ya190b19kbyk7CiAJCWlmICghd29ya190b19kbykgewogCQkJeGVu dmlmX3B1dCh2aWYpOwpAQCAtMTI5NCwxNyArMTMyNiwxNCBAQCBzdGF0aWMg dW5zaWduZWQgeGVuX25ldGJrX3R4X2J1aWxkX2dvcHMoc3RydWN0IHhlbl9u ZXRiayAqbmV0YmspCiAJCQl3b3JrX3RvX2RvID0geGVuX25ldGJrX2dldF9l eHRyYXModmlmLCBleHRyYXMsCiAJCQkJCQkJICB3b3JrX3RvX2RvKTsKIAkJ CWlkeCA9IHZpZi0+dHgucmVxX2NvbnM7Ci0JCQlpZiAodW5saWtlbHkod29y a190b19kbyA8IDApKSB7Ci0JCQkJbmV0YmtfdHhfZXJyKHZpZiwgJnR4cmVx LCBpZHgpOworCQkJaWYgKHVubGlrZWx5KHdvcmtfdG9fZG8gPCAwKSkKIAkJ CQljb250aW51ZTsKLQkJCX0KIAkJfQogCiAJCXJldCA9IG5ldGJrX2NvdW50 X3JlcXVlc3RzKHZpZiwgJnR4cmVxLCB0eGZyYWdzLCB3b3JrX3RvX2RvKTsK LQkJaWYgKHVubGlrZWx5KHJldCA8IDApKSB7Ci0JCQluZXRia190eF9lcnIo dmlmLCAmdHhyZXEsIGlkeCAtIHJldCk7CisJCWlmICh1bmxpa2VseShyZXQg PCAwKSkKIAkJCWNvbnRpbnVlOwotCQl9CisKIAkJaWR4ICs9IHJldDsKIAog CQlpZiAodW5saWtlbHkodHhyZXEuc2l6ZSA8IEVUSF9ITEVOKSkgewpAQCAt MTMxNiwxMSArMTM0NSwxMSBAQCBzdGF0aWMgdW5zaWduZWQgeGVuX25ldGJr X3R4X2J1aWxkX2dvcHMoc3RydWN0IHhlbl9uZXRiayAqbmV0YmspCiAKIAkJ LyogTm8gY3Jvc3NpbmcgYSBwYWdlIGFzIHRoZSBwYXlsb2FkIG11c3RuJ3Qg ZnJhZ21lbnQuICovCiAJCWlmICh1bmxpa2VseSgodHhyZXEub2Zmc2V0ICsg dHhyZXEuc2l6ZSkgPiBQQUdFX1NJWkUpKSB7Ci0JCQluZXRkZXZfZGJnKHZp Zi0+ZGV2LAorCQkJbmV0ZGV2X2Vycih2aWYtPmRldiwKIAkJCQkgICAidHhy ZXEub2Zmc2V0OiAleCwgc2l6ZTogJXUsIGVuZDogJWx1XG4iLAogCQkJCSAg IHR4cmVxLm9mZnNldCwgdHhyZXEuc2l6ZSwKIAkJCQkgICAodHhyZXEub2Zm c2V0Jn5QQUdFX01BU0spICsgdHhyZXEuc2l6ZSk7Ci0JCQluZXRia190eF9l cnIodmlmLCAmdHhyZXEsIGlkeCk7CisJCQluZXRia19mYXRhbF90eF9lcnIo dmlmKTsKIAkJCWNvbnRpbnVlOwogCQl9CiAKQEAgLTEzNDgsOCArMTM3Nyw4 IEBAIHN0YXRpYyB1bnNpZ25lZCB4ZW5fbmV0YmtfdHhfYnVpbGRfZ29wcyhz dHJ1Y3QgeGVuX25ldGJrICpuZXRiaykKIAkJCWdzbyA9ICZleHRyYXNbWEVO X05FVElGX0VYVFJBX1RZUEVfR1NPIC0gMV07CiAKIAkJCWlmIChuZXRia19z ZXRfc2tiX2dzbyh2aWYsIHNrYiwgZ3NvKSkgeworCQkJCS8qIEZhaWx1cmUg aW4gbmV0Ymtfc2V0X3NrYl9nc28gaXMgZmF0YWwuICovCiAJCQkJa2ZyZWVf c2tiKHNrYik7Ci0JCQkJbmV0YmtfdHhfZXJyKHZpZiwgJnR4cmVxLCBpZHgp OwogCQkJCWNvbnRpbnVlOwogCQkJfQogCQl9Ci0tIAoxLjcuMi41Cgo= --=separator Content-Type: application/octet-stream; name="xsa39-pvops-0002-xen-netback-don-t-leak-pages-on-failure-in-xen_netbk.patch" Content-Disposition: attachment; filename="xsa39-pvops-0002-xen-netback-don-t-leak-pages-on-failure-in-xen_netbk.patch" Content-Transfer-Encoding: base64 RnJvbSA5MDQyMDYzMWQyYjc4YWNhMjhjOTRiZWI2NmIyNTQ0N2U1N2E4ZGQ0 IE1vbiBTZXAgMTcgMDA6MDA6MDAgMjAwMQpGcm9tOiBJYW4gQ2FtcGJlbGwg PGlhbi5jYW1wYmVsbEBjaXRyaXguY29tPgpEYXRlOiBNb24sIDE0IEphbiAy MDEzIDEyOjIwOjA0ICswMDAwClN1YmplY3Q6IFtQQVRDSCAyLzRdIHhlbi9u ZXRiYWNrOiBkb24ndCBsZWFrIHBhZ2VzIG9uIGZhaWx1cmUgaW4geGVuX25l dGJrX3R4X2NoZWNrX2dvcC4KClNpZ25lZC1vZmYtYnk6IE1hdHRoZXcgRGFs ZXkgPG1hdHRqZEBnbWFpbC5jb20+ClJldmlld2VkLWJ5OiBLb25yYWQgUnpl c3p1dGVrIFdpbGsgPGtvbnJhZC53aWxrQG9yYWNsZS5jb20+CkFja2VkLWJ5 OiBJYW4gQ2FtcGJlbGwgPGlhbi5jYW1wYmVsbEBjaXRyaXguY29tPgpBY2tl ZC1ieTogSmFuIEJldWxpY2ggPEpCZXVsaWNoQHN1c2UuY29tPgotLS0KIGRy aXZlcnMvbmV0L3hlbi1uZXRiYWNrL25ldGJhY2suYyB8ICAgMzggKysrKysr KysrKysrLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tCiAxIGZpbGVzIGNoYW5n ZWQsIDEzIGluc2VydGlvbnMoKyksIDI1IGRlbGV0aW9ucygtKQoKZGlmZiAt LWdpdCBhL2RyaXZlcnMvbmV0L3hlbi1uZXRiYWNrL25ldGJhY2suYyBiL2Ry aXZlcnMvbmV0L3hlbi1uZXRiYWNrL25ldGJhY2suYwppbmRleCAxYTQ0OWY5 Li45NzUyNDFlIDEwMDY0NAotLS0gYS9kcml2ZXJzL25ldC94ZW4tbmV0YmFj ay9uZXRiYWNrLmMKKysrIGIvZHJpdmVycy9uZXQveGVuLW5ldGJhY2svbmV0 YmFjay5jCkBAIC0xNDcsNyArMTQ3LDggQEAgdm9pZCB4ZW5fbmV0YmtfcmVt b3ZlX3hlbnZpZihzdHJ1Y3QgeGVudmlmICp2aWYpCiAJYXRvbWljX2RlYygm bmV0YmstPm5ldGZyb250X2NvdW50KTsKIH0KIAotc3RhdGljIHZvaWQgeGVu X25ldGJrX2lkeF9yZWxlYXNlKHN0cnVjdCB4ZW5fbmV0YmsgKm5ldGJrLCB1 MTYgcGVuZGluZ19pZHgpOworc3RhdGljIHZvaWQgeGVuX25ldGJrX2lkeF9y ZWxlYXNlKHN0cnVjdCB4ZW5fbmV0YmsgKm5ldGJrLCB1MTYgcGVuZGluZ19p ZHgsCisJCQkJICB1OCBzdGF0dXMpOwogc3RhdGljIHZvaWQgbWFrZV90eF9y ZXNwb25zZShzdHJ1Y3QgeGVudmlmICp2aWYsCiAJCQkgICAgIHN0cnVjdCB4 ZW5fbmV0aWZfdHhfcmVxdWVzdCAqdHhwLAogCQkJICAgICBzOCAgICAgICBz dCk7CkBAIC0xMDA3LDMwICsxMDA4LDIwIEBAIHN0YXRpYyBpbnQgeGVuX25l dGJrX3R4X2NoZWNrX2dvcChzdHJ1Y3QgeGVuX25ldGJrICpuZXRiaywKIHsK IAlzdHJ1Y3QgZ250dGFiX2NvcHkgKmdvcCA9ICpnb3BwOwogCXUxNiBwZW5k aW5nX2lkeCA9ICooKHUxNiAqKXNrYi0+ZGF0YSk7Ci0Jc3RydWN0IHBlbmRp bmdfdHhfaW5mbyAqcGVuZGluZ190eF9pbmZvID0gbmV0YmstPnBlbmRpbmdf dHhfaW5mbzsKLQlzdHJ1Y3QgeGVudmlmICp2aWYgPSBwZW5kaW5nX3R4X2lu Zm9bcGVuZGluZ19pZHhdLnZpZjsKLQlzdHJ1Y3QgeGVuX25ldGlmX3R4X3Jl cXVlc3QgKnR4cDsKIAlzdHJ1Y3Qgc2tiX3NoYXJlZF9pbmZvICpzaGluZm8g PSBza2Jfc2hpbmZvKHNrYik7CiAJaW50IG5yX2ZyYWdzID0gc2hpbmZvLT5u cl9mcmFnczsKIAlpbnQgaSwgZXJyLCBzdGFydDsKIAogCS8qIENoZWNrIHN0 YXR1cyBvZiBoZWFkZXIuICovCiAJZXJyID0gZ29wLT5zdGF0dXM7Ci0JaWYg KHVubGlrZWx5KGVycikpIHsKLQkJcGVuZGluZ19yaW5nX2lkeF90IGluZGV4 OwotCQlpbmRleCA9IHBlbmRpbmdfaW5kZXgobmV0YmstPnBlbmRpbmdfcHJv ZCsrKTsKLQkJdHhwID0gJnBlbmRpbmdfdHhfaW5mb1twZW5kaW5nX2lkeF0u cmVxOwotCQltYWtlX3R4X3Jlc3BvbnNlKHZpZiwgdHhwLCBYRU5fTkVUSUZf UlNQX0VSUk9SKTsKLQkJbmV0YmstPnBlbmRpbmdfcmluZ1tpbmRleF0gPSBw ZW5kaW5nX2lkeDsKLQkJeGVudmlmX3B1dCh2aWYpOwotCX0KKwlpZiAodW5s aWtlbHkoZXJyKSkKKwkJeGVuX25ldGJrX2lkeF9yZWxlYXNlKG5ldGJrLCBw ZW5kaW5nX2lkeCwgWEVOX05FVElGX1JTUF9FUlJPUik7CiAKIAkvKiBTa2lw IGZpcnN0IHNrYiBmcmFnbWVudCBpZiBpdCBpcyBvbiBzYW1lIHBhZ2UgYXMg aGVhZGVyIGZyYWdtZW50LiAqLwogCXN0YXJ0ID0gKGZyYWdfZ2V0X3BlbmRp bmdfaWR4KCZzaGluZm8tPmZyYWdzWzBdKSA9PSBwZW5kaW5nX2lkeCk7CiAK IAlmb3IgKGkgPSBzdGFydDsgaSA8IG5yX2ZyYWdzOyBpKyspIHsKIAkJaW50 IGosIG5ld2VycjsKLQkJcGVuZGluZ19yaW5nX2lkeF90IGluZGV4OwogCiAJ CXBlbmRpbmdfaWR4ID0gZnJhZ19nZXRfcGVuZGluZ19pZHgoJnNoaW5mby0+ ZnJhZ3NbaV0pOwogCkBAIC0xMDM5LDE2ICsxMDMwLDEyIEBAIHN0YXRpYyBp bnQgeGVuX25ldGJrX3R4X2NoZWNrX2dvcChzdHJ1Y3QgeGVuX25ldGJrICpu ZXRiaywKIAkJaWYgKGxpa2VseSghbmV3ZXJyKSkgewogCQkJLyogSGFkIGEg cHJldmlvdXMgZXJyb3I/IEludmFsaWRhdGUgdGhpcyBmcmFnbWVudC4gKi8K IAkJCWlmICh1bmxpa2VseShlcnIpKQotCQkJCXhlbl9uZXRia19pZHhfcmVs ZWFzZShuZXRiaywgcGVuZGluZ19pZHgpOworCQkJCXhlbl9uZXRia19pZHhf cmVsZWFzZShuZXRiaywgcGVuZGluZ19pZHgsIFhFTl9ORVRJRl9SU1BfT0tB WSk7CiAJCQljb250aW51ZTsKIAkJfQogCiAJCS8qIEVycm9yIG9uIHRoaXMg ZnJhZ21lbnQ6IHJlc3BvbmQgdG8gY2xpZW50IHdpdGggYW4gZXJyb3IuICov Ci0JCXR4cCA9ICZuZXRiay0+cGVuZGluZ190eF9pbmZvW3BlbmRpbmdfaWR4 XS5yZXE7Ci0JCW1ha2VfdHhfcmVzcG9uc2UodmlmLCB0eHAsIFhFTl9ORVRJ Rl9SU1BfRVJST1IpOwotCQlpbmRleCA9IHBlbmRpbmdfaW5kZXgobmV0Ymst PnBlbmRpbmdfcHJvZCsrKTsKLQkJbmV0YmstPnBlbmRpbmdfcmluZ1tpbmRl eF0gPSBwZW5kaW5nX2lkeDsKLQkJeGVudmlmX3B1dCh2aWYpOworCQl4ZW5f bmV0YmtfaWR4X3JlbGVhc2UobmV0YmssIHBlbmRpbmdfaWR4LCBYRU5fTkVU SUZfUlNQX0VSUk9SKTsKIAogCQkvKiBOb3QgdGhlIGZpcnN0IGVycm9yPyBQ cmVjZWRpbmcgZnJhZ3MgYWxyZWFkeSBpbnZhbGlkYXRlZC4gKi8KIAkJaWYg KGVycikKQEAgLTEwNTYsMTAgKzEwNDMsMTAgQEAgc3RhdGljIGludCB4ZW5f bmV0YmtfdHhfY2hlY2tfZ29wKHN0cnVjdCB4ZW5fbmV0YmsgKm5ldGJrLAog CiAJCS8qIEZpcnN0IGVycm9yOiBpbnZhbGlkYXRlIGhlYWRlciBhbmQgcHJl Y2VkaW5nIGZyYWdtZW50cy4gKi8KIAkJcGVuZGluZ19pZHggPSAqKCh1MTYg Kilza2ItPmRhdGEpOwotCQl4ZW5fbmV0YmtfaWR4X3JlbGVhc2UobmV0Ymss IHBlbmRpbmdfaWR4KTsKKwkJeGVuX25ldGJrX2lkeF9yZWxlYXNlKG5ldGJr LCBwZW5kaW5nX2lkeCwgWEVOX05FVElGX1JTUF9PS0FZKTsKIAkJZm9yIChq ID0gc3RhcnQ7IGogPCBpOyBqKyspIHsKIAkJCXBlbmRpbmdfaWR4ID0gZnJh Z19nZXRfcGVuZGluZ19pZHgoJnNoaW5mby0+ZnJhZ3Nbal0pOwotCQkJeGVu X25ldGJrX2lkeF9yZWxlYXNlKG5ldGJrLCBwZW5kaW5nX2lkeCk7CisJCQl4 ZW5fbmV0YmtfaWR4X3JlbGVhc2UobmV0YmssIHBlbmRpbmdfaWR4LCBYRU5f TkVUSUZfUlNQX09LQVkpOwogCQl9CiAKIAkJLyogUmVtZW1iZXIgdGhlIGVy cm9yOiBpbnZhbGlkYXRlIGFsbCBzdWJzZXF1ZW50IGZyYWdtZW50cy4gKi8K QEAgLTEwOTMsNyArMTA4MCw3IEBAIHN0YXRpYyB2b2lkIHhlbl9uZXRia19m aWxsX2ZyYWdzKHN0cnVjdCB4ZW5fbmV0YmsgKm5ldGJrLCBzdHJ1Y3Qgc2tf YnVmZiAqc2tiKQogCiAJCS8qIFRha2UgYW4gZXh0cmEgcmVmZXJlbmNlIHRv IG9mZnNldCB4ZW5fbmV0YmtfaWR4X3JlbGVhc2UgKi8KIAkJZ2V0X3BhZ2Uo bmV0YmstPm1tYXBfcGFnZXNbcGVuZGluZ19pZHhdKTsKLQkJeGVuX25ldGJr X2lkeF9yZWxlYXNlKG5ldGJrLCBwZW5kaW5nX2lkeCk7CisJCXhlbl9uZXRi a19pZHhfcmVsZWFzZShuZXRiaywgcGVuZGluZ19pZHgsIFhFTl9ORVRJRl9S U1BfT0tBWSk7CiAJfQogfQogCkBAIC0xNDc3LDcgKzE0NjQsNyBAQCBzdGF0 aWMgdm9pZCB4ZW5fbmV0YmtfdHhfc3VibWl0KHN0cnVjdCB4ZW5fbmV0Ymsg Km5ldGJrKQogCQkJdHhwLT5zaXplIC09IGRhdGFfbGVuOwogCQl9IGVsc2Ug ewogCQkJLyogU2NoZWR1bGUgYSByZXNwb25zZSBpbW1lZGlhdGVseS4gKi8K LQkJCXhlbl9uZXRia19pZHhfcmVsZWFzZShuZXRiaywgcGVuZGluZ19pZHgp OworCQkJeGVuX25ldGJrX2lkeF9yZWxlYXNlKG5ldGJrLCBwZW5kaW5nX2lk eCwgWEVOX05FVElGX1JTUF9PS0FZKTsKIAkJfQogCiAJCWlmICh0eHAtPmZs YWdzICYgWEVOX05FVFRYRl9jc3VtX2JsYW5rKQpAQCAtMTUyOSw3ICsxNTE2 LDggQEAgc3RhdGljIHZvaWQgeGVuX25ldGJrX3R4X2FjdGlvbihzdHJ1Y3Qg eGVuX25ldGJrICpuZXRiaykKIAl4ZW5fbmV0YmtfdHhfc3VibWl0KG5ldGJr KTsKIH0KIAotc3RhdGljIHZvaWQgeGVuX25ldGJrX2lkeF9yZWxlYXNlKHN0 cnVjdCB4ZW5fbmV0YmsgKm5ldGJrLCB1MTYgcGVuZGluZ19pZHgpCitzdGF0 aWMgdm9pZCB4ZW5fbmV0YmtfaWR4X3JlbGVhc2Uoc3RydWN0IHhlbl9uZXRi ayAqbmV0YmssIHUxNiBwZW5kaW5nX2lkeCwKKwkJCQkgIHU4IHN0YXR1cykK IHsKIAlzdHJ1Y3QgeGVudmlmICp2aWY7CiAJc3RydWN0IHBlbmRpbmdfdHhf aW5mbyAqcGVuZGluZ190eF9pbmZvOwpAQCAtMTU0Myw3ICsxNTMxLDcgQEAg c3RhdGljIHZvaWQgeGVuX25ldGJrX2lkeF9yZWxlYXNlKHN0cnVjdCB4ZW5f bmV0YmsgKm5ldGJrLCB1MTYgcGVuZGluZ19pZHgpCiAKIAl2aWYgPSBwZW5k aW5nX3R4X2luZm8tPnZpZjsKIAotCW1ha2VfdHhfcmVzcG9uc2UodmlmLCAm cGVuZGluZ190eF9pbmZvLT5yZXEsIFhFTl9ORVRJRl9SU1BfT0tBWSk7CisJ bWFrZV90eF9yZXNwb25zZSh2aWYsICZwZW5kaW5nX3R4X2luZm8tPnJlcSwg c3RhdHVzKTsKIAogCWluZGV4ID0gcGVuZGluZ19pbmRleChuZXRiay0+cGVu ZGluZ19wcm9kKyspOwogCW5ldGJrLT5wZW5kaW5nX3JpbmdbaW5kZXhdID0g cGVuZGluZ19pZHg7Ci0tIAoxLjcuMi41Cgo= --=separator Content-Type: application/octet-stream; name="xsa39-pvops-0003-xen-netback-free-already-allocated-memory-on-failure.patch" Content-Disposition: attachment; filename="xsa39-pvops-0003-xen-netback-free-already-allocated-memory-on-failure.patch" Content-Transfer-Encoding: base64 RnJvbSBiNmIxZjE3YWE0NGFjZmUxMDI0OTY4YmFmYjFkMWZlNzcwNGE3NDlh IE1vbiBTZXAgMTcgMDA6MDA6MDAgMjAwMQpGcm9tOiBJYW4gQ2FtcGJlbGwg PGlhbi5jYW1wYmVsbEBjaXRyaXguY29tPgpEYXRlOiBNb24sIDE0IEphbiAy MDEzIDEyOjUxOjIyICswMDAwClN1YmplY3Q6IFtQQVRDSCAzLzRdIHhlbi9u ZXRiYWNrOiBmcmVlIGFscmVhZHkgYWxsb2NhdGVkIG1lbW9yeSBvbiBmYWls dXJlIGluIHhlbl9uZXRia19nZXRfcmVxdWVzdHMKClNpZ25lZC1vZmYtYnk6 IElhbiBDYW1wYmVsbCA8aWFuLmNhbXBiZWxsQGNpdHJpeC5jb20+Ci0tLQog ZHJpdmVycy9uZXQveGVuLW5ldGJhY2svbmV0YmFjay5jIHwgICAxNiArKysr KysrKysrKysrKystCiAxIGZpbGVzIGNoYW5nZWQsIDE1IGluc2VydGlvbnMo KyksIDEgZGVsZXRpb25zKC0pCgpkaWZmIC0tZ2l0IGEvZHJpdmVycy9uZXQv eGVuLW5ldGJhY2svbmV0YmFjay5jIGIvZHJpdmVycy9uZXQveGVuLW5ldGJh Y2svbmV0YmFjay5jCmluZGV4IDk3NTI0MWUuLjFhOTkyODggMTAwNjQ0Ci0t LSBhL2RyaXZlcnMvbmV0L3hlbi1uZXRiYWNrL25ldGJhY2suYworKysgYi9k cml2ZXJzL25ldC94ZW4tbmV0YmFjay9uZXRiYWNrLmMKQEAgLTk3OCw3ICs5 NzgsNyBAQCBzdGF0aWMgc3RydWN0IGdudHRhYl9jb3B5ICp4ZW5fbmV0Ymtf Z2V0X3JlcXVlc3RzKHN0cnVjdCB4ZW5fbmV0YmsgKm5ldGJrLAogCQlwZW5k aW5nX2lkeCA9IG5ldGJrLT5wZW5kaW5nX3JpbmdbaW5kZXhdOwogCQlwYWdl ID0geGVuX25ldGJrX2FsbG9jX3BhZ2UobmV0YmssIHNrYiwgcGVuZGluZ19p ZHgpOwogCQlpZiAoIXBhZ2UpCi0JCQlyZXR1cm4gTlVMTDsKKwkJCWdvdG8g ZXJyOwogCiAJCWdvcC0+c291cmNlLnUucmVmID0gdHhwLT5ncmVmOwogCQln b3AtPnNvdXJjZS5kb21pZCA9IHZpZi0+ZG9taWQ7CkBAIC0xMDAwLDYgKzEw MDAsMjAgQEAgc3RhdGljIHN0cnVjdCBnbnR0YWJfY29weSAqeGVuX25ldGJr X2dldF9yZXF1ZXN0cyhzdHJ1Y3QgeGVuX25ldGJrICpuZXRiaywKIAl9CiAK IAlyZXR1cm4gZ29wOworZXJyOgorCS8qCisJICogVW53aW5kLCBmcmVlaW5n IGFsbCBwYWdlcyBhbmQgc2VuZGluZyBlcnJvcgorCSAqIHJlcG9uc2VzLgor CSAqLworCXdoaWxlIChpLS0gPiBzdGFydCkgeworCQl4ZW5fbmV0YmtfaWR4 X3JlbGVhc2UobmV0YmssIGZyYWdfZ2V0X3BlbmRpbmdfaWR4KCZmcmFnc1tp XSksCisJCQkJICAgICAgWEVOX05FVElGX1JTUF9FUlJPUik7CisJfQorCS8q IFRoZSBoZWFkIHRvbywgaWYgbmVjZXNzYXJ5LiAqLworCWlmIChzdGFydCkK KwkJeGVuX25ldGJrX2lkeF9yZWxlYXNlKG5ldGJrLCBwZW5kaW5nX2lkeCwg WEVOX05FVElGX1JTUF9FUlJPUik7CisKKwlyZXR1cm4gTlVMTDsKIH0KIAog c3RhdGljIGludCB4ZW5fbmV0YmtfdHhfY2hlY2tfZ29wKHN0cnVjdCB4ZW5f bmV0YmsgKm5ldGJrLAotLSAKMS43LjIuNQoK --=separator Content-Type: application/octet-stream; name="xsa39-pvops-0004-netback-correct-netbk_tx_err-to-handle-wrap-around.patch" Content-Disposition: attachment; filename="xsa39-pvops-0004-netback-correct-netbk_tx_err-to-handle-wrap-around.patch" Content-Transfer-Encoding: base64 RnJvbSBlYTVlM2MxZThmZDlmZmU2MDgwZTAxYWY3NzY5YTlmYTQyMGNjNjJl IE1vbiBTZXAgMTcgMDA6MDA6MDAgMjAwMQpGcm9tOiBJYW4gQ2FtcGJlbGwg PGlhbi5jYW1wYmVsbEBjaXRyaXguY29tPgpEYXRlOiBNb24sIDE0IEphbiAy MDEzIDEzOjMyOjMxICswMDAwClN1YmplY3Q6IFtQQVRDSCA0LzRdIG5ldGJh Y2s6IGNvcnJlY3QgbmV0YmtfdHhfZXJyIHRvIGhhbmRsZSB3cmFwIGFyb3Vu ZC4KClNpZ25lZC1vZmYtYnk6IElhbiBDYW1wYmVsbCA8aWFuLmNhbXBiZWxs QGNpdHJpeC5jb20+CkFja2VkLWJ5OiBKYW4gQmV1bGljaCA8SkJldWxpY2hA c3VzZS5jb20+Ci0tLQogZHJpdmVycy9uZXQveGVuLW5ldGJhY2svbmV0YmFj ay5jIHwgICAgMiArLQogMSBmaWxlcyBjaGFuZ2VkLCAxIGluc2VydGlvbnMo KyksIDEgZGVsZXRpb25zKC0pCgpkaWZmIC0tZ2l0IGEvZHJpdmVycy9uZXQv eGVuLW5ldGJhY2svbmV0YmFjay5jIGIvZHJpdmVycy9uZXQveGVuLW5ldGJh Y2svbmV0YmFjay5jCmluZGV4IDFhOTkyODguLjI4ZDVlMDYgMTAwNjQ0Ci0t LSBhL2RyaXZlcnMvbmV0L3hlbi1uZXRiYWNrL25ldGJhY2suYworKysgYi9k cml2ZXJzL25ldC94ZW4tbmV0YmFjay9uZXRiYWNrLmMKQEAgLTg4MCw3ICs4 ODAsNyBAQCBzdGF0aWMgdm9pZCBuZXRia190eF9lcnIoc3RydWN0IHhlbnZp ZiAqdmlmLAogCiAJZG8gewogCQltYWtlX3R4X3Jlc3BvbnNlKHZpZiwgdHhw LCBYRU5fTkVUSUZfUlNQX0VSUk9SKTsKLQkJaWYgKGNvbnMgPj0gZW5kKQor CQlpZiAoY29ucyA9PSBlbmQpCiAJCQlicmVhazsKIAkJdHhwID0gUklOR19H RVRfUkVRVUVTVCgmdmlmLT50eCwgY29ucysrKTsKIAl9IHdoaWxlICgxKTsK LS0gCjEuNy4yLjUKCg== --=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 Tue Feb 05 13:16:28 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 05 Feb 2013 13:16: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 1U2iNK-0007aJ-Cy; Tue, 05 Feb 2013 13:15:50 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U2iNG-0007YC-H3; Tue, 05 Feb 2013 13:15:47 +0000 Received: from [85.158.138.51:8056] by server-3.bemta-3.messagelabs.com id 27/9E-31070-10601115; Tue, 05 Feb 2013 13:15:45 +0000 X-Env-Sender: ianc@xenbits.xen.org X-Msg-Ref: server-5.tower-174.messagelabs.com!1360070134!28898814!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.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 23853 invoked from network); 5 Feb 2013 13:15:36 -0000 Received: from mail.xen.org (HELO mail.xen.org) (50.57.168.107) by server-5.tower-174.messagelabs.com with AES256-SHA encrypted SMTP; 5 Feb 2013 13:15:36 -0000 Received: from xenbits.xen.org ([50.57.170.242]) by mail.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U2iMZ-0003Zw-6U; Tue, 05 Feb 2013 13:15:03 +0000 Received: from ianc by xenbits.xen.org with local (Exim 4.72) (envelope-from ) id 1U2iMY-00088X-Tl; Tue, 05 Feb 2013 13:15:02 +0000 Date: Tue, 05 Feb 2013 13:15:02 +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 36 (CVE-2013-0153) - interrupt remap entries shared and old ones not cleared on AMD IOMMUs X-BeenThere: xen-users@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-2013-0153 / XSA-36 version 3 interrupt remap entries shared and old ones not cleared on AMD IOMMUs UPDATES IN VERSION 3 ==================== Public release. ISSUE DESCRIPTION ================= To avoid an erratum in early hardware, the Xen AMD IOMMU code by default chooses to use a single interrupt remapping table for the whole system. This sharing implies that any guest with a passed through PCI device that is bus mastering capable can inject interrupts into other guests, including domain 0. Furthermore, regardless of whether a shared interrupt remapping table is in use, old entries are not always cleared, providing opportunities (which accumulate over time) for guests to inject interrupts into other guests, again including domain 0. In a typical Xen system many devices are owned by domain 0 or driver domains, leaving them vulnerable to such an attack. Such a DoS is likely to have an impact on other guests running in the system. IMPACT ====== A malicious domain which is given access to a physical PCI device can mount a denial of service attack affecting the whole system. VULNERABLE SYSTEMS ================== Xen versions 3.3 onwards are vulnerable. Earlier Xen versions do not implement interrupt remapping, and hence do not support secure AMD-Vi PCI passthrough in any case. Only systems using AMD-Vi for PCI passthrough are vulnerable. Any domain which is given access to a PCI device can take advantage of this vulnerability. MITIGATION ========== This issue can be avoided by not assigning PCI devices to untrusted guests. In Xen versions 4.1.3 and above the sharing of the interrupt remapping table (and hence the more severe part of this problem) can be avoided by passing "iommu=amd-iommu-perdev-intremap" as a command line option to the hypervisor. This option is not fully functional on earlier hypervisors. RESOLUTION ========== Applying the appropriate attached patch resolves this issue. Note that on certain systems (SP5100 chipsets with erratum 28 present, or such with broken IVRS ACPI table) these patches will result in the IOMMU not being enabled anymore. This should be dealt with by a BIOS update, if available. Alternatively the check can be overridden by specifying "iommu=no-amd-iommu-perdev-intremap" on the Xen command line ("iommu=amd-iommu-global-intremap" on 4.1.x), at the price of re-opening the security hole addressed by these patches. xsa36-unstable.patch Xen unstable xsa36-4.2.patch Xen 4.2.x xsa36-4.1.patch Xen 4.1.x $ sha256sum xsa36*.patch 2254fa46dcbc164d2d55ad9d519e7aa4ac5b83e9fb8d8e1f224114d08fe44237 xsa36-4.1.patch 6848712b560b522f7d3cede53e29e799624311e7dee6e450f0c02c165a590783 xsa36-4.2.patch 0e5d53c0b2bbbf07ef07bf31d8adeca4c043c0277f122f74557b018dc7348b74 xsa36-unstable.patch $ -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) iQEcBAEBAgAGBQJREQItAAoJEIP+FMlX6CvZapMH/i+AeMV4Mi9EAe97JWto2xrg bCBdq7LEJ1cIpXGbhpXwTRzmsEGJmFR2VwkaxEtk+BuC7bzJ/KRjWYg6viQ7v+0t thHEMtaRYTOIIel8YZ5t+v8oMdEUos7Oo94xhCk+n7ioH6PO+quUTI+aGd0+lcJm d/5TC5f8w+HZNTB0nCQX9tQx5d4veQXghKs1NbKHeMyZ66nMZiqUqVUwQNTaFhUO 9eWyGOik5/mFctRrMxoOZHQm3d36AnDisiOku2CaG1xYYwDaAnOe/u6QcBZcVX3M Q9COmTAWnOfIKYMIFnXRnyHSiw2+oZL6PTD5nX4O68B6hZ8pemVa+lFhSTvxsXM= =5jP3 -----END PGP SIGNATURE----- --=separator Content-Type: application/octet-stream; name="xsa36-4.1.patch" Content-Disposition: attachment; filename="xsa36-4.1.patch" Content-Transfer-Encoding: base64 QUNQSTogYWNwaV90YWJsZV9wYXJzZSgpIHNob3VsZCByZXR1cm4gaGFuZGxl cidzIGVycm9yIGNvZGUKCkN1cnJlbnRseSwgdGhlIGVycm9yIGNvZGUgcmV0 dXJuZWQgYnkgYWNwaV90YWJsZV9wYXJzZSgpJ3MgaGFuZGxlcgppcyBpZ25v cmVkLiBUaGlzIHBhdGNoIHdpbGwgcHJvcGFnYXRlIGhhbmRsZXIncyByZXR1 cm4gdmFsdWUgdG8KYWNwaV90YWJsZV9wYXJzZSgpJ3MgY2FsbGVyLgoKQU1E LElPTU1VOiBDbGVhbiB1cCBvbGQgZW50cmllcyBpbiByZW1hcHBpbmcgdGFi bGVzIHdoZW4gY3JlYXRpbmcgbmV3CmludGVycnVwdCBtYXBwaW5nLgoKV2hl biBjaGFuZ2luZyB0aGUgYWZmaW5pdHkgb2YgYW4gSVJRIGFzc29jaWF0ZWQg d2l0aCBhIHBhc3NlZAp0aHJvdWdoIFBDSSBkZXZpY2UsIGNsZWFyIHByZXZp b3VzIG1hcHBpbmcuCgpJbiBhZGRpdGlvbiwgYmVjYXVzZSBzb21lIEJJT1Nl cyBtYXkgaW5jb3JyZWN0bHkgcHJvZ3JhbSBJVlJTCmVudHJpZXMgZm9yIElP QVBJQyB0cnkgdG8gY2hlY2sgZm9yIGVudHJ5J3MgY29uc2lzdGVuY3kuIFNw ZWNpZmljYWxseSwKaWYgY29uZmxpY3RpbmcgZW50cmllcyBhcmUgZm91bmQg ZGlzYWJsZSBJT01NVSBpZiBwZXItZGV2aWNlCnJlbWFwcGluZyB0YWJsZSBp cyB1c2VkLiBJZiBlbnRyaWVzIHJlZmVyIHRvIGJvZ3VzIElPQVBJQyBJRHMK ZGlzYWJsZSBJT01NVSB1bmNvbmRpdGlvbmFsbHkKCkFNRCxJT01NVTogRGlz YWJsZSBJT01NVSBpZiBTQVRBIENvbWJpbmVkIG1vZGUgaXMgb24KCkFNRCdz IFNQNTEwMCBjaGlwc2V0IGNhbiBiZSBwbGFjZWQgaW50byBTQVRBIENvbWJp bmVkIG1vZGUKdGhhdCBtYXkgY2F1c2UgcHJldmVudCBkb20wIGZyb20gYm9v dGluZyB3aGVuIElPTU1VIGlzCmVuYWJsZWQgYW5kIHBlci1kZXZpY2UgaW50 ZXJydXB0IHJlbWFwcGluZyB0YWJsZSBpcyB1c2VkLgpXaGlsZSBTUDUxMDAg ZXJyYXR1bSAyOCByZXF1aXJlcyBCSU9TZXMgdG8gZGlzYWJsZSB0aGlzIG1v ZGUsCnNvbWUgbWF5IHN0aWxsIHVzZSBpdC4KClRoaXMgcGF0Y2ggY2hlY2tz IHdoZXRoZXIgdGhpcyBtb2RlIGlzIG9uIGFuZCwgaWYgcGVyLWRldmljZQp0 YWJsZSBpcyBpbiB1c2UsIGRpc2FibGVzIElPTU1VLgoKQU1ELElPTU1VOiBN YWtlIHBlci1kZXZpY2UgaW50ZXJydXB0IHJlbWFwcGluZyB0YWJsZSBkZWZh dWx0CgpVc2luZyBnbG9iYWwgaW50ZXJydXB0IHJlbWFwcGluZyB0YWJsZSBt YXkgYmUgaW5zZWN1cmUsIGFzCmRlc2NyaWJlZCBieSBYU0EtMzYuIFRoaXMg cGF0Y2ggbWFrZXMgcGVyLWRldmljZSBtb2RlIGRlZmF1bHQuCgpUaGlzIGlz IFhTQS0zNiAvIENWRS0yMDEzLTAxNTMuCgpTaWduZWQtb2ZmLWJ5OiBKYW4g QmV1bGljaCA8amJldWxpY2hAc3VzZS5jb20+ClNpZ25lZC1vZmYtYnk6IEJv cmlzIE9zdHJvdnNreSA8Ym9yaXMub3N0cm92c2t5QGFtZC5jb20+CgotLS0g YS94ZW4vYXJjaC94ODYvaXJxLmMKKysrIGIveGVuL2FyY2gveDg2L2lycS5j CkBAIC0xNjc3LDkgKzE2NzcsNiBAQCBpbnQgbWFwX2RvbWFpbl9waXJxKAog ICAgICAgICBkLT5hcmNoLnBpcnFfaXJxW3BpcnFdID0gaXJxOwogICAgICAg ICBkLT5hcmNoLmlycV9waXJxW2lycV0gPSBwaXJxOwogICAgICAgICBzcGlu X3VubG9ja19pcnFyZXN0b3JlKCZkZXNjLT5sb2NrLCBmbGFncyk7Ci0KLSAg ICAgICAgaWYgKCBvcHRfaXJxX3ZlY3Rvcl9tYXAgPT0gT1BUX0lSUV9WRUNU T1JfTUFQX1BFUkRFViApCi0gICAgICAgICAgICBwcmludGsoWEVOTE9HX0lO Rk8gIlBlci1kZXZpY2UgdmVjdG9yIG1hcHMgZm9yIEdTSXMgbm90IGltcGxl bWVudGVkIHlldC5cbiIpOwogICAgIH0KIAogZG9uZToKLS0tIGEveGVuL2Ry aXZlcnMvYWNwaS90YWJsZXMuYworKysgYi94ZW4vZHJpdmVycy9hY3BpL3Rh Ymxlcy5jCkBAIC0yNjcsNyArMjY3LDcgQEAgYWNwaV90YWJsZV9wYXJzZV9t YWR0KGVudW0gYWNwaV9tYWR0X3R5cAogICogQGhhbmRsZXI6IGhhbmRsZXIg dG8gcnVuCiAgKgogICogU2NhbiB0aGUgQUNQSSBTeXN0ZW0gRGVzY3JpcHRv ciBUYWJsZSAoU1REKSBmb3IgYSB0YWJsZSBtYXRjaGluZyBAaWQsCi0gKiBy dW4gQGhhbmRsZXIgb24gaXQuICBSZXR1cm4gMCBpZiB0YWJsZSBmb3VuZCwg cmV0dXJuIG9uIGlmIG5vdC4KKyAqIHJ1biBAaGFuZGxlciBvbiBpdC4KICAq LwogaW50IGFjcGlfdGFibGVfcGFyc2UoY2hhciAqaWQsIGFjcGlfdGFibGVf aGFuZGxlciBoYW5kbGVyKQogewpAQCAtMjgyLDggKzI4Miw3IEBAIGludCBh Y3BpX3RhYmxlX3BhcnNlKGNoYXIgKmlkLCBhY3BpX3RhYmwKIAkJYWNwaV9n ZXRfdGFibGUoaWQsIDAsICZ0YWJsZSk7CiAKIAlpZiAodGFibGUpIHsKLQkJ aGFuZGxlcih0YWJsZSk7Ci0JCXJldHVybiAwOworCQlyZXR1cm4gaGFuZGxl cih0YWJsZSk7CiAJfSBlbHNlCiAJCXJldHVybiAxOwogfQotLS0gYS94ZW4v ZHJpdmVycy9wYXNzdGhyb3VnaC9hbWQvaW9tbXVfYWNwaS5jCisrKyBiL3hl bi9kcml2ZXJzL3Bhc3N0aHJvdWdoL2FtZC9pb21tdV9hY3BpLmMKQEAgLTIx LDYgKzIxLDcgQEAKICNpbmNsdWRlIDx4ZW4vY29uZmlnLmg+CiAjaW5jbHVk ZSA8eGVuL2Vycm5vLmg+CiAjaW5jbHVkZSA8YXNtL2FwaWNkZWYuaD4KKyNp bmNsdWRlIDxhc20vaW9fYXBpYy5oPgogI2luY2x1ZGUgPGFzbS9hbWQtaW9t bXUuaD4KICNpbmNsdWRlIDxhc20vaHZtL3N2bS9hbWQtaW9tbXUtcHJvdG8u aD4KICNpbmNsdWRlIDxhc20vaHZtL3N2bS9hbWQtaW9tbXUtYWNwaS5oPgpA QCAtMjksNyArMzAsNiBAQCBleHRlcm4gdW5zaWduZWQgbG9uZyBhbWRfaW9t bXVfcGFnZV9lbnRyCiBleHRlcm4gdW5zaWduZWQgc2hvcnQgaXZyc19iZGZf ZW50cmllczsKIGV4dGVybiBzdHJ1Y3QgaXZyc19tYXBwaW5ncyAqaXZyc19t YXBwaW5nczsKIGV4dGVybiB1bnNpZ25lZCBzaG9ydCBsYXN0X2JkZjsKLWV4 dGVybiBpbnQgaW9hcGljX2JkZltNQVhfSU9fQVBJQ1NdOwogZXh0ZXJuIHZv aWQgKnNoYXJlZF9pbnRyZW1hcF90YWJsZTsKIAogc3RhdGljIHZvaWQgYWRk X2l2cnNfbWFwcGluZ19lbnRyeSgKQEAgLTYzNiw2ICs2MzYsNyBAQCBzdGF0 aWMgdTE2IF9faW5pdCBwYXJzZV9pdmhkX2RldmljZV9zcGVjCiAgICAgdTE2 IGhlYWRlcl9sZW5ndGgsIHUxNiBibG9ja19sZW5ndGgsIHN0cnVjdCBhbWRf aW9tbXUgKmlvbW11KQogewogICAgIHUxNiBkZXZfbGVuZ3RoLCBiZGY7Cisg ICAgaW50IGFwaWM7CiAKICAgICBkZXZfbGVuZ3RoID0gc2l6ZW9mKHN0cnVj dCBhY3BpX2l2aGRfZGV2aWNlX3NwZWNpYWwpOwogICAgIGlmICggaGVhZGVy X2xlbmd0aCA8IChibG9ja19sZW5ndGggKyBkZXZfbGVuZ3RoKSApCkBAIC02 NTIsOSArNjUzLDU4IEBAIHN0YXRpYyB1MTYgX19pbml0IHBhcnNlX2l2aGRf ZGV2aWNlX3NwZWMKICAgICB9CiAKICAgICBhZGRfaXZyc19tYXBwaW5nX2Vu dHJ5KGJkZiwgYmRmLCBpdmhkX2RldmljZS0+aGVhZGVyLmZsYWdzLCBpb21t dSk7Ci0gICAgLyogc2V0IGRldmljZSBpZCBvZiBpb2FwaWMgKi8KLSAgICBp b2FwaWNfYmRmW2l2aGRfZGV2aWNlLT5zcGVjaWFsLmhhbmRsZV0gPSBiZGY7 Ci0gICAgcmV0dXJuIGRldl9sZW5ndGg7CisKKyAgICBpZiAoIGl2aGRfZGV2 aWNlLT5zcGVjaWFsLnZhcmlldHkgIT0gMSAvKiBBQ1BJX0lWSERfSU9BUElD ICovICkKKyAgICB7CisgICAgICAgIGlmICggaXZoZF9kZXZpY2UtPnNwZWNp YWwudmFyaWV0eSAhPSAyIC8qIEFDUElfSVZIRF9IUEVUICovICkKKyAgICAg ICAgICAgIHByaW50ayhYRU5MT0dfRVJSICJVbnJlY29nbml6ZWQgSVZIRCBz cGVjaWFsIHZhcmlldHkgJSN4XG4iLAorICAgICAgICAgICAgICAgICAgIGl2 aGRfZGV2aWNlLT5zcGVjaWFsLnZhcmlldHkpOworICAgICAgICByZXR1cm4g ZGV2X2xlbmd0aDsKKyAgICB9CisKKyAgICAvKgorICAgICAqIFNvbWUgQklP U2VzIGhhdmUgSU9BUElDIGJyb2tlbiBlbnRyaWVzIHNvIHdlIGNoZWNrIGZv ciBJVlJTCisgICAgICogY29uc2lzdGVuY3kgaGVyZSAtLS0gd2hldGhlciBl bnRyeSdzIElPQVBJQyBJRCBpcyB2YWxpZCBhbmQKKyAgICAgKiB3aGV0aGVy IHRoZXJlIGFyZSBjb25mbGljdGluZy9kdXBsaWNhdGVkIGVudHJpZXMuCisg ICAgICovCisgICAgZm9yICggYXBpYyA9IDA7IGFwaWMgPCBucl9pb2FwaWNz OyBhcGljKysgKQorICAgIHsKKyAgICAgICAgaWYgKCBJT19BUElDX0lEKGFw aWMpICE9IGl2aGRfZGV2aWNlLT5zcGVjaWFsLmhhbmRsZSApCisgICAgICAg ICAgICBjb250aW51ZTsKKworICAgICAgICBpZiAoIGlvYXBpY19iZGZbaXZo ZF9kZXZpY2UtPnNwZWNpYWwuaGFuZGxlXS5waW5fc2V0dXAgKQorICAgICAg ICB7CisgICAgICAgICAgICBpZiAoIGlvYXBpY19iZGZbaXZoZF9kZXZpY2Ut PnNwZWNpYWwuaGFuZGxlXS5iZGYgPT0gYmRmICkKKyAgICAgICAgICAgICAg ICBBTURfSU9NTVVfREVCVUcoIklWSEQgV2FybmluZzogRHVwbGljYXRlIElP LUFQSUMgJSN4IGVudHJpZXNcbiIsCisgICAgICAgICAgICAgICAgICAgICAg ICAgICAgICAgIGl2aGRfZGV2aWNlLT5zcGVjaWFsLmhhbmRsZSk7CisgICAg ICAgICAgICBlbHNlCisgICAgICAgICAgICB7CisgICAgICAgICAgICAgICAg cHJpbnRrKFhFTkxPR19FUlIgIklWSEQgRXJyb3I6IENvbmZsaWN0aW5nIElP LUFQSUMgJSN4IGVudHJpZXNcbiIsCisgICAgICAgICAgICAgICAgICAgICAg IGl2aGRfZGV2aWNlLT5zcGVjaWFsLmhhbmRsZSk7CisgICAgICAgICAgICAg ICAgaWYgKCBhbWRfaW9tbXVfcGVyZGV2X2ludHJlbWFwICkKKyAgICAgICAg ICAgICAgICAgICAgcmV0dXJuIDA7CisgICAgICAgICAgICB9CisgICAgICAg IH0KKyAgICAgICAgZWxzZQorICAgICAgICB7CisgICAgICAgICAgICAvKiBz ZXQgZGV2aWNlIGlkIG9mIGlvYXBpYyAqLworICAgICAgICAgICAgaW9hcGlj X2JkZltpdmhkX2RldmljZS0+c3BlY2lhbC5oYW5kbGVdLmJkZiA9IGJkZjsK KworICAgICAgICAgICAgaW9hcGljX2JkZltpdmhkX2RldmljZS0+c3BlY2lh bC5oYW5kbGVdLnBpbl9zZXR1cCA9IHh6YWxsb2NfYXJyYXkoCisgICAgICAg ICAgICAgICAgdW5zaWduZWQgbG9uZywgQklUU19UT19MT05HUyhucl9pb2Fw aWNfcmVnaXN0ZXJzW2FwaWNdKSk7CisgICAgICAgICAgICBpZiAoIG5yX2lv YXBpY19yZWdpc3RlcnNbYXBpY10gJiYKKyAgICAgICAgICAgICAgICAgIWlv YXBpY19iZGZbSU9fQVBJQ19JRChhcGljKV0ucGluX3NldHVwICkKKyAgICAg ICAgICAgIHsKKyAgICAgICAgICAgICAgICBwcmludGsoWEVOTE9HX0VSUiAi SVZIRCBFcnJvcjogT3V0IG9mIG1lbW9yeVxuIik7CisgICAgICAgICAgICAg ICAgcmV0dXJuIDA7CisgICAgICAgICAgICB9CisgICAgICAgIH0KKyAgICAg ICAgcmV0dXJuIGRldl9sZW5ndGg7CisgICAgfQorCisgICAgcHJpbnRrKFhF TkxPR19FUlIgIklWSEQgRXJyb3I6IEludmFsaWQgSU8tQVBJQyAlI3hcbiIs CisgICAgICAgICAgIGl2aGRfZGV2aWNlLT5zcGVjaWFsLmhhbmRsZSk7Cisg ICAgcmV0dXJuIDA7CiB9CiAKIHN0YXRpYyBpbnQgX19pbml0IHBhcnNlX2l2 aGRfYmxvY2soc3RydWN0IGFjcGlfaXZoZF9ibG9ja19oZWFkZXIgKml2aGRf YmxvY2spCi0tLSBhL3hlbi9kcml2ZXJzL3Bhc3N0aHJvdWdoL2FtZC9pb21t dV9pbml0LmMKKysrIGIveGVuL2RyaXZlcnMvcGFzc3Rocm91Z2gvYW1kL2lv bW11X2luaXQuYwpAQCAtODk3LDEyICs4OTcsNDUgQEAgc3RhdGljIGludCBf X2luaXQgYW1kX2lvbW11X3NldHVwX2RldmljZQogICAgIHJldHVybiAwOwog fQogCisvKiBDaGVjayB3aGV0aGVyIFNQNTEwMCBTQVRBIENvbWJpbmVkIG1v ZGUgaXMgb24gKi8KK3N0YXRpYyBib29sX3QgX19pbml0IGFtZF9zcDUxMDBf ZXJyYXR1bTI4KHZvaWQpCit7CisgICAgdTMyIGJ1cywgaWQ7CisgICAgdTE2 IHZlbmRvcl9pZCwgZGV2X2lkOworICAgIHU4IGJ5dGU7CisKKyAgICBmb3Ig KGJ1cyA9IDA7IGJ1cyA8IDI1NjsgYnVzKyspCisgICAgeworICAgICAgICBp ZCA9IHBjaV9jb25mX3JlYWQzMihidXMsIDB4MTQsIDAsIFBDSV9WRU5ET1Jf SUQpOworCisgICAgICAgIHZlbmRvcl9pZCA9IGlkICYgMHhmZmZmOworICAg ICAgICBkZXZfaWQgPSAoaWQgPj4gMTYpICYgMHhmZmZmOworCisgICAgICAg IC8qIFNQNTEwMCBTTUJ1cyBtb2R1bGUgc2V0cyBDb21iaW5lZCBtb2RlIG9u ICovCisgICAgICAgIGlmICh2ZW5kb3JfaWQgIT0gMHgxMDAyIHx8IGRldl9p ZCAhPSAweDQzODUpCisgICAgICAgICAgICBjb250aW51ZTsKKworICAgICAg ICBieXRlID0gcGNpX2NvbmZfcmVhZDgoYnVzLCAweDE0LCAwLCAweGFkKTsK KyAgICAgICAgaWYgKCAoYnl0ZSA+PiAzKSAmIDEgKQorICAgICAgICB7Cisg ICAgICAgICAgICBwcmludGsoWEVOTE9HX1dBUk5JTkcgIkFNRC1WaTogU1A1 MTAwIGVycmF0dW0gMjggZGV0ZWN0ZWQsIGRpc2FibGluZyBJT01NVS5cbiIK KyAgICAgICAgICAgICAgICAgICAiSWYgcG9zc2libGUsIGRpc2FibGUgU0FU QSBDb21iaW5lZCBtb2RlIGluIEJJT1Mgb3IgY29udGFjdCB5b3VyIHZlbmRv ciBmb3IgQklPUyB1cGRhdGUuXG4iKTsKKyAgICAgICAgICAgIHJldHVybiAx OworICAgICAgICB9CisgICAgfQorCisgICAgcmV0dXJuIDA7Cit9CisKIGlu dCBfX2luaXQgYW1kX2lvbW11X2luaXQodm9pZCkKIHsKICAgICBzdHJ1Y3Qg YW1kX2lvbW11ICppb21tdTsKIAogICAgIEJVR19PTiggIWlvbW11X2ZvdW5k KCkgKTsKIAorICAgIGlmICggYW1kX2lvbW11X3BlcmRldl9pbnRyZW1hcCAm JiBhbWRfc3A1MTAwX2VycmF0dW0yOCgpICkKKyAgICAgICAgZ290byBlcnJv cl9vdXQ7CisKICAgICBpcnFfdG9faW9tbXUgPSB4bWFsbG9jX2FycmF5KHN0 cnVjdCBhbWRfaW9tbXUgKiwgbnJfaXJxcyk7CiAgICAgaWYgKCBpcnFfdG9f aW9tbXUgPT0gTlVMTCApCiAgICAgICAgIGdvdG8gZXJyb3Jfb3V0OwotLS0g YS94ZW4vZHJpdmVycy9wYXNzdGhyb3VnaC9hbWQvaW9tbXVfaW50ci5jCisr KyBiL3hlbi9kcml2ZXJzL3Bhc3N0aHJvdWdoL2FtZC9pb21tdV9pbnRyLmMK QEAgLTI3LDcgKzI3LDcgQEAKICNkZWZpbmUgSU5UUkVNQVBfTEVOR1RIIDB4 QgogI2RlZmluZSBJTlRSRU1BUF9FTlRSSUVTICgxIDw8IElOVFJFTUFQX0xF TkdUSCkKIAotaW50IGlvYXBpY19iZGZbTUFYX0lPX0FQSUNTXTsKK3N0cnVj dCBpb2FwaWNfYmRmIGlvYXBpY19iZGZbTUFYX0lPX0FQSUNTXTsKIGV4dGVy biBzdHJ1Y3QgaXZyc19tYXBwaW5ncyAqaXZyc19tYXBwaW5nczsKIGV4dGVy biB1bnNpZ25lZCBzaG9ydCBpdnJzX2JkZl9lbnRyaWVzOwogdm9pZCAqc2hh cmVkX2ludHJlbWFwX3RhYmxlOwpAQCAtMTE3LDEyICsxMTcsMTIgQEAgdm9p ZCBpbnZhbGlkYXRlX2ludGVycnVwdF90YWJsZShzdHJ1Y3QgYQogc3RhdGlj IHZvaWQgdXBkYXRlX2ludHJlbWFwX2VudHJ5X2Zyb21faW9hcGljKAogICAg IGludCBiZGYsCiAgICAgc3RydWN0IGFtZF9pb21tdSAqaW9tbXUsCi0gICAg c3RydWN0IElPX0FQSUNfcm91dGVfZW50cnkgKmlvYXBpY19ydGUpCisgICAg Y29uc3Qgc3RydWN0IElPX0FQSUNfcm91dGVfZW50cnkgKnJ0ZSwKKyAgICBj b25zdCBzdHJ1Y3QgSU9fQVBJQ19yb3V0ZV9lbnRyeSAqb2xkX3J0ZSkKIHsK ICAgICB1bnNpZ25lZCBsb25nIGZsYWdzOwogICAgIHUzMiogZW50cnk7CiAg ICAgdTggZGVsaXZlcnlfbW9kZSwgZGVzdCwgdmVjdG9yLCBkZXN0X21vZGU7 Ci0gICAgc3RydWN0IElPX0FQSUNfcm91dGVfZW50cnkgKnJ0ZSA9IGlvYXBp Y19ydGU7CiAgICAgaW50IHJlcV9pZDsKICAgICBzcGlubG9ja190ICpsb2Nr OwogICAgIGludCBvZmZzZXQ7CkBAIC0xMzgsNiArMTM4LDE0IEBAIHN0YXRp YyB2b2lkIHVwZGF0ZV9pbnRyZW1hcF9lbnRyeV9mcm9tX2kKICAgICBzcGlu X2xvY2tfaXJxc2F2ZShsb2NrLCBmbGFncyk7CiAKICAgICBvZmZzZXQgPSBn ZXRfaW50cmVtYXBfb2Zmc2V0KHZlY3RvciwgZGVsaXZlcnlfbW9kZSk7Cisg ICAgaWYgKCBvbGRfcnRlICkKKyAgICB7CisgICAgICAgIGludCBvbGRfb2Zm c2V0ID0gZ2V0X2ludHJlbWFwX29mZnNldChvbGRfcnRlLT52ZWN0b3IsCisg ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICBv bGRfcnRlLT5kZWxpdmVyeV9tb2RlKTsKKworICAgICAgICBpZiAoIG9mZnNl dCAhPSBvbGRfb2Zmc2V0ICkKKyAgICAgICAgICAgIGZyZWVfaW50cmVtYXBf ZW50cnkoYmRmLCBvbGRfb2Zmc2V0KTsKKyAgICB9CiAgICAgZW50cnkgPSAo dTMyKilnZXRfaW50cmVtYXBfZW50cnkocmVxX2lkLCBvZmZzZXQpOwogICAg IHVwZGF0ZV9pbnRyZW1hcF9lbnRyeShlbnRyeSwgdmVjdG9yLCBkZWxpdmVy eV9tb2RlLCBkZXN0X21vZGUsIGRlc3QpOwogCkBAIC0xNzYsNyArMTg0LDcg QEAgaW50IF9faW5pdCBhbWRfaW9tbXVfc2V0dXBfaW9hcGljX3JlbWFwcAog ICAgICAgICAgICAgICAgIGNvbnRpbnVlOwogCiAgICAgICAgICAgICAvKiBn ZXQgZGV2aWNlIGlkIG9mIGlvYXBpYyBkZXZpY2VzICovCi0gICAgICAgICAg ICBiZGYgPSBpb2FwaWNfYmRmW0lPX0FQSUNfSUQoYXBpYyldOworICAgICAg ICAgICAgYmRmID0gaW9hcGljX2JkZltJT19BUElDX0lEKGFwaWMpXS5iZGY7 CiAgICAgICAgICAgICBpb21tdSA9IGZpbmRfaW9tbXVfZm9yX2RldmljZShi ZGYpOwogICAgICAgICAgICAgaWYgKCAhaW9tbXUgKQogICAgICAgICAgICAg ewpAQCAtMjA3LDYgKzIxNSw3IEBAIGludCBfX2luaXQgYW1kX2lvbW11X3Nl dHVwX2lvYXBpY19yZW1hcHAKICAgICAgICAgICAgICAgICBmbHVzaF9jb21t YW5kX2J1ZmZlcihpb21tdSk7CiAgICAgICAgICAgICAgICAgc3Bpbl91bmxv Y2tfaXJxcmVzdG9yZSgmaW9tbXUtPmxvY2ssIGZsYWdzKTsKICAgICAgICAg ICAgIH0KKyAgICAgICAgICAgIHNldF9iaXQocGluLCBpb2FwaWNfYmRmW0lP X0FQSUNfSUQoYXBpYyldLnBpbl9zZXR1cCk7CiAgICAgICAgIH0KICAgICB9 CiAgICAgcmV0dXJuIDA7CkBAIC0yMTgsNiArMjI3LDcgQEAgdm9pZCBhbWRf aW9tbXVfaW9hcGljX3VwZGF0ZV9pcmUoCiAgICAgc3RydWN0IElPX0FQSUNf cm91dGVfZW50cnkgb2xkX3J0ZSA9IHsgMCB9OwogICAgIHN0cnVjdCBJT19B UElDX3JvdXRlX2VudHJ5IG5ld19ydGUgPSB7IDAgfTsKICAgICB1bnNpZ25l ZCBpbnQgcnRlX2xvID0gKHJlZyAmIDEpID8gcmVnIC0gMSA6IHJlZzsKKyAg ICB1bnNpZ25lZCBpbnQgcGluID0gKHJlZyAtIDB4MTApIC8gMjsKICAgICBp bnQgc2F2ZWRfbWFzaywgYmRmOwogICAgIHN0cnVjdCBhbWRfaW9tbXUgKmlv bW11OwogCkBAIC0yMjgsNyArMjM4LDcgQEAgdm9pZCBhbWRfaW9tbXVfaW9h cGljX3VwZGF0ZV9pcmUoCiAgICAgfQogCiAgICAgLyogZ2V0IGRldmljZSBp ZCBvZiBpb2FwaWMgZGV2aWNlcyAqLwotICAgIGJkZiA9IGlvYXBpY19iZGZb SU9fQVBJQ19JRChhcGljKV07CisgICAgYmRmID0gaW9hcGljX2JkZltJT19B UElDX0lEKGFwaWMpXS5iZGY7CiAgICAgaW9tbXUgPSBmaW5kX2lvbW11X2Zv cl9kZXZpY2UoYmRmKTsKICAgICBpZiAoICFpb21tdSApCiAgICAgewpAQCAt MjU0LDYgKzI2NCwxNCBAQCB2b2lkIGFtZF9pb21tdV9pb2FwaWNfdXBkYXRl X2lyZSgKICAgICAgICAgKigoKHUzMiAqKSZuZXdfcnRlKSArIDEpID0gdmFs dWU7CiAgICAgfQogCisgICAgaWYgKCBuZXdfcnRlLm1hc2sgJiYKKyAgICAg ICAgICF0ZXN0X2JpdChwaW4sIGlvYXBpY19iZGZbSU9fQVBJQ19JRChhcGlj KV0ucGluX3NldHVwKSApCisgICAgeworICAgICAgICBBU1NFUlQoc2F2ZWRf bWFzayk7CisgICAgICAgIF9faW9fYXBpY193cml0ZShhcGljLCByZWcsIHZh bHVlKTsKKyAgICAgICAgcmV0dXJuOworICAgIH0KKwogICAgIC8qIG1hc2sg dGhlIGludGVycnVwdCB3aGlsZSB3ZSBjaGFuZ2UgdGhlIGludHJlbWFwIHRh YmxlICovCiAgICAgaWYgKCAhc2F2ZWRfbWFzayApCiAgICAgewpAQCAtMjYy LDcgKzI4MCwxMSBAQCB2b2lkIGFtZF9pb21tdV9pb2FwaWNfdXBkYXRlX2ly ZSgKICAgICB9CiAKICAgICAvKiBVcGRhdGUgaW50ZXJydXB0IHJlbWFwcGlu ZyBlbnRyeSAqLwotICAgIHVwZGF0ZV9pbnRyZW1hcF9lbnRyeV9mcm9tX2lv YXBpYyhiZGYsIGlvbW11LCAmbmV3X3J0ZSk7CisgICAgdXBkYXRlX2ludHJl bWFwX2VudHJ5X2Zyb21faW9hcGljKAorICAgICAgICBiZGYsIGlvbW11LCAm bmV3X3J0ZSwKKyAgICAgICAgdGVzdF9hbmRfc2V0X2JpdChwaW4sCisgICAg ICAgICAgICAgICAgICAgICAgICAgaW9hcGljX2JkZltJT19BUElDX0lEKGFw aWMpXS5waW5fc2V0dXApID8gJm9sZF9ydGUKKyAgICAgICAgICAgICAgICAg ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg ICAgOiBOVUxMKTsKIAogICAgIC8qIEZvcndhcmQgd3JpdGUgYWNjZXNzIHRv IElPLUFQSUMgUlRFICovCiAgICAgX19pb19hcGljX3dyaXRlKGFwaWMsIHJl ZywgdmFsdWUpOwpAQCAtMzczLDYgKzM5NSwxMiBAQCB2b2lkIGFtZF9pb21t dV9tc2lfbXNnX3VwZGF0ZV9pcmUoCiAgICAgICAgIHJldHVybjsKICAgICB9 CiAKKyAgICBpZiAoIG1zaV9kZXNjLT5yZW1hcF9pbmRleCA+PSAwICkKKyAg ICAgICAgdXBkYXRlX2ludHJlbWFwX2VudHJ5X2Zyb21fbXNpX21zZyhpb21t dSwgcGRldiwgbXNpX2Rlc2MsIE5VTEwpOworCisgICAgaWYgKCAhbXNnICkK KyAgICAgICAgcmV0dXJuOworCiAgICAgdXBkYXRlX2ludHJlbWFwX2VudHJ5 X2Zyb21fbXNpX21zZyhpb21tdSwgcGRldiwgbXNpX2Rlc2MsIG1zZyk7CiB9 CiAKLS0tIGEveGVuL2RyaXZlcnMvcGFzc3Rocm91Z2gvYW1kL3BjaV9hbWRf aW9tbXUuYworKysgYi94ZW4vZHJpdmVycy9wYXNzdGhyb3VnaC9hbWQvcGNp X2FtZF9pb21tdS5jCkBAIC0xOTUsNiArMTk1LDggQEAgaW50IF9faW5pdCBh bWRfaW92X2RldGVjdCh2b2lkKQogICAgIHsKICAgICAgICAgcHJpbnRrKCJB TUQtVmk6IE5vdCBvdmVycmlkaW5nIGlycV92ZWN0b3JfbWFwIHNldHRpbmdc biIpOwogICAgIH0KKyAgICBpZiAoICFhbWRfaW9tbXVfcGVyZGV2X2ludHJl bWFwICkKKyAgICAgICAgcHJpbnRrKFhFTkxPR19XQVJOSU5HICJBTUQtVmk6 IFVzaW5nIGdsb2JhbCBpbnRlcnJ1cHQgcmVtYXAgdGFibGUgaXMgbm90IHJl Y29tbWVuZGVkIChzZWUgWFNBLTM2KSFcbiIpOwogICAgIHJldHVybiBzY2Fu X3BjaV9kZXZpY2VzKCk7CiB9CiAKLS0tIGEveGVuL2RyaXZlcnMvcGFzc3Ro cm91Z2gvaW9tbXUuYworKysgYi94ZW4vZHJpdmVycy9wYXNzdGhyb3VnaC9p b21tdS5jCkBAIC00OSw3ICs0OSw3IEBAIGJvb2xfdCBfX3JlYWRfbW9zdGx5 IGlvbW11X3FpbnZhbCA9IDE7CiBib29sX3QgX19yZWFkX21vc3RseSBpb21t dV9pbnRyZW1hcCA9IDE7CiBib29sX3QgX19yZWFkX21vc3RseSBpb21tdV9o YXBfcHRfc2hhcmU7CiBib29sX3QgX19yZWFkX21vc3RseSBhbWRfaW9tbXVf ZGVidWc7Ci1ib29sX3QgX19yZWFkX21vc3RseSBhbWRfaW9tbXVfcGVyZGV2 X2ludHJlbWFwOworYm9vbF90IF9fcmVhZF9tb3N0bHkgYW1kX2lvbW11X3Bl cmRldl9pbnRyZW1hcCA9IDE7CiAKIHN0YXRpYyB2b2lkIF9faW5pdCBwYXJz ZV9pb21tdV9wYXJhbShjaGFyICpzKQogewpAQCAtNzgsNiArNzgsOCBAQCBz dGF0aWMgdm9pZCBfX2luaXQgcGFyc2VfaW9tbXVfcGFyYW0oY2hhCiAgICAg ICAgICAgICBhbWRfaW9tbXVfZGVidWcgPSAxOwogICAgICAgICBlbHNlIGlm ICggIXN0cmNtcChzLCAiYW1kLWlvbW11LXBlcmRldi1pbnRyZW1hcCIpICkK ICAgICAgICAgICAgIGFtZF9pb21tdV9wZXJkZXZfaW50cmVtYXAgPSAxOwor ICAgICAgICBlbHNlIGlmICggIXN0cmNtcChzLCAiYW1kLWlvbW11LWdsb2Jh bC1pbnRyZW1hcCIpICkKKyAgICAgICAgICAgIGFtZF9pb21tdV9wZXJkZXZf aW50cmVtYXAgPSAwOwogICAgICAgICBlbHNlIGlmICggIXN0cmNtcChzLCAi ZG9tMC1wYXNzdGhyb3VnaCIpICkKICAgICAgICAgICAgIGlvbW11X3Bhc3N0 aHJvdWdoID0gMTsKICAgICAgICAgZWxzZSBpZiAoICFzdHJjbXAocywgImRv bTAtc3RyaWN0IikgKQotLS0gYS94ZW4vaW5jbHVkZS9hc20teDg2L2h2bS9z dm0vYW1kLWlvbW11LXByb3RvLmgKKysrIGIveGVuL2luY2x1ZGUvYXNtLXg4 Ni9odm0vc3ZtL2FtZC1pb21tdS1wcm90by5oCkBAIC04OCw2ICs4OCwxMSBA QCB2b2lkIGFtZF9pb21tdV9yZWFkX21zaV9mcm9tX2lyZSgKIHVuc2lnbmVk IGludCBhbWRfaW9tbXVfcmVhZF9pb2FwaWNfZnJvbV9pcmUoCiAgICAgdW5z aWduZWQgaW50IGFwaWMsIHVuc2lnbmVkIGludCByZWcpOwogCitleHRlcm4g c3RydWN0IGlvYXBpY19iZGYgeworICAgIHUxNiBiZGY7CisgICAgdW5zaWdu ZWQgbG9uZyAqcGluX3NldHVwOworfSBpb2FwaWNfYmRmW107CisKIC8qIHBv d2VyIG1hbmFnZW1lbnQgc3VwcG9ydCAqLwogdm9pZCBhbWRfaW9tbXVfcmVz dW1lKHZvaWQpOwogdm9pZCBhbWRfaW9tbXVfc3VzcGVuZCh2b2lkKTsK --=separator Content-Type: application/octet-stream; name="xsa36-4.2.patch" Content-Disposition: attachment; filename="xsa36-4.2.patch" Content-Transfer-Encoding: base64 QUNQSTogYWNwaV90YWJsZV9wYXJzZSgpIHNob3VsZCByZXR1cm4gaGFuZGxl cidzIGVycm9yIGNvZGUKCkN1cnJlbnRseSwgdGhlIGVycm9yIGNvZGUgcmV0 dXJuZWQgYnkgYWNwaV90YWJsZV9wYXJzZSgpJ3MgaGFuZGxlcgppcyBpZ25v cmVkLiBUaGlzIHBhdGNoIHdpbGwgcHJvcGFnYXRlIGhhbmRsZXIncyByZXR1 cm4gdmFsdWUgdG8KYWNwaV90YWJsZV9wYXJzZSgpJ3MgY2FsbGVyLgoKQU1E LElPTU1VOiBDbGVhbiB1cCBvbGQgZW50cmllcyBpbiByZW1hcHBpbmcgdGFi bGVzIHdoZW4gY3JlYXRpbmcgbmV3CmludGVycnVwdCBtYXBwaW5nLgoKV2hl biBjaGFuZ2luZyB0aGUgYWZmaW5pdHkgb2YgYW4gSVJRIGFzc29jaWF0ZWQg d2l0aCBhIHBhc3NlZAp0aHJvdWdoIFBDSSBkZXZpY2UsIGNsZWFyIHByZXZp b3VzIG1hcHBpbmcuCgpJbiBhZGRpdGlvbiwgYmVjYXVzZSBzb21lIEJJT1Nl cyBtYXkgaW5jb3JyZWN0bHkgcHJvZ3JhbSBJVlJTCmVudHJpZXMgZm9yIElP QVBJQyB0cnkgdG8gY2hlY2sgZm9yIGVudHJ5J3MgY29uc2lzdGVuY3kuIFNw ZWNpZmljYWxseSwKaWYgY29uZmxpY3RpbmcgZW50cmllcyBhcmUgZm91bmQg ZGlzYWJsZSBJT01NVSBpZiBwZXItZGV2aWNlCnJlbWFwcGluZyB0YWJsZSBp cyB1c2VkLiBJZiBlbnRyaWVzIHJlZmVyIHRvIGJvZ3VzIElPQVBJQyBJRHMK ZGlzYWJsZSBJT01NVSB1bmNvbmRpdGlvbmFsbHkKCkFNRCxJT01NVTogRGlz YWJsZSBJT01NVSBpZiBTQVRBIENvbWJpbmVkIG1vZGUgaXMgb24KCkFNRCdz IFNQNTEwMCBjaGlwc2V0IGNhbiBiZSBwbGFjZWQgaW50byBTQVRBIENvbWJp bmVkIG1vZGUKdGhhdCBtYXkgY2F1c2UgcHJldmVudCBkb20wIGZyb20gYm9v dGluZyB3aGVuIElPTU1VIGlzCmVuYWJsZWQgYW5kIHBlci1kZXZpY2UgaW50 ZXJydXB0IHJlbWFwcGluZyB0YWJsZSBpcyB1c2VkLgpXaGlsZSBTUDUxMDAg ZXJyYXR1bSAyOCByZXF1aXJlcyBCSU9TZXMgdG8gZGlzYWJsZSB0aGlzIG1v ZGUsCnNvbWUgbWF5IHN0aWxsIHVzZSBpdC4KClRoaXMgcGF0Y2ggY2hlY2tz IHdoZXRoZXIgdGhpcyBtb2RlIGlzIG9uIGFuZCwgaWYgcGVyLWRldmljZQp0 YWJsZSBpcyBpbiB1c2UsIGRpc2FibGVzIElPTU1VLgoKQU1ELElPTU1VOiBN YWtlIHBlci1kZXZpY2UgaW50ZXJydXB0IHJlbWFwcGluZyB0YWJsZSBkZWZh dWx0CgpVc2luZyBnbG9iYWwgaW50ZXJydXB0IHJlbWFwcGluZyB0YWJsZSBt YXkgYmUgaW5zZWN1cmUsIGFzCmRlc2NyaWJlZCBieSBYU0EtMzYuIFRoaXMg cGF0Y2ggbWFrZXMgcGVyLWRldmljZSBtb2RlIGRlZmF1bHQuCgpUaGlzIGlz IFhTQS0zNiAvIENWRS0yMDEzLTAxNTMuCgpTaWduZWQtb2ZmLWJ5OiBKYW4g QmV1bGljaCA8amJldWxpY2hAc3VzZS5jb20+ClNpZ25lZC1vZmYtYnk6IEJv cmlzIE9zdHJvdnNreSA8Ym9yaXMub3N0cm92c2t5QGFtZC5jb20+CgotLS0g YS94ZW4vYXJjaC94ODYvaXJxLmMKKysrIGIveGVuL2FyY2gveDg2L2lycS5j CkBAIC0xOTQyLDkgKzE5NDIsNiBAQCBpbnQgbWFwX2RvbWFpbl9waXJxKAog ICAgICAgICBzcGluX2xvY2tfaXJxc2F2ZSgmZGVzYy0+bG9jaywgZmxhZ3Mp OwogICAgICAgICBzZXRfZG9tYWluX2lycV9waXJxKGQsIGlycSwgaW5mbyk7 CiAgICAgICAgIHNwaW5fdW5sb2NrX2lycXJlc3RvcmUoJmRlc2MtPmxvY2ss IGZsYWdzKTsKLQotICAgICAgICBpZiAoIG9wdF9pcnFfdmVjdG9yX21hcCA9 PSBPUFRfSVJRX1ZFQ1RPUl9NQVBfUEVSREVWICkKLSAgICAgICAgICAgIHBy aW50ayhYRU5MT0dfSU5GTyAiUGVyLWRldmljZSB2ZWN0b3IgbWFwcyBmb3Ig R1NJcyBub3QgaW1wbGVtZW50ZWQgeWV0LlxuIik7CiAgICAgfQogCiBkb25l OgotLS0gYS94ZW4vZHJpdmVycy9hY3BpL3RhYmxlcy5jCisrKyBiL3hlbi9k cml2ZXJzL2FjcGkvdGFibGVzLmMKQEAgLTI2Nyw3ICsyNjcsNyBAQCBhY3Bp X3RhYmxlX3BhcnNlX21hZHQoZW51bSBhY3BpX21hZHRfdHlwCiAgKiBAaGFu ZGxlcjogaGFuZGxlciB0byBydW4KICAqCiAgKiBTY2FuIHRoZSBBQ1BJIFN5 c3RlbSBEZXNjcmlwdG9yIFRhYmxlIChTVEQpIGZvciBhIHRhYmxlIG1hdGNo aW5nIEBpZCwKLSAqIHJ1biBAaGFuZGxlciBvbiBpdC4gIFJldHVybiAwIGlm IHRhYmxlIGZvdW5kLCByZXR1cm4gb24gaWYgbm90LgorICogcnVuIEBoYW5k bGVyIG9uIGl0LgogICovCiBpbnQgX19pbml0IGFjcGlfdGFibGVfcGFyc2Uo Y2hhciAqaWQsIGFjcGlfdGFibGVfaGFuZGxlciBoYW5kbGVyKQogewpAQCAt MjgyLDggKzI4Miw3IEBAIGludCBfX2luaXQgYWNwaV90YWJsZV9wYXJzZShj aGFyICppZCwgYWMKIAkJYWNwaV9nZXRfdGFibGUoaWQsIDAsICZ0YWJsZSk7 CiAKIAlpZiAodGFibGUpIHsKLQkJaGFuZGxlcih0YWJsZSk7Ci0JCXJldHVy biAwOworCQlyZXR1cm4gaGFuZGxlcih0YWJsZSk7CiAJfSBlbHNlCiAJCXJl dHVybiAxOwogfQotLS0gYS94ZW4vZHJpdmVycy9wYXNzdGhyb3VnaC9hbWQv aW9tbXVfYWNwaS5jCisrKyBiL3hlbi9kcml2ZXJzL3Bhc3N0aHJvdWdoL2Ft ZC9pb21tdV9hY3BpLmMKQEAgLTIyLDYgKzIyLDcgQEAKICNpbmNsdWRlIDx4 ZW4vZXJybm8uaD4KICNpbmNsdWRlIDx4ZW4vYWNwaS5oPgogI2luY2x1ZGUg PGFzbS9hcGljZGVmLmg+CisjaW5jbHVkZSA8YXNtL2lvX2FwaWMuaD4KICNp bmNsdWRlIDxhc20vYW1kLWlvbW11Lmg+CiAjaW5jbHVkZSA8YXNtL2h2bS9z dm0vYW1kLWlvbW11LXByb3RvLmg+CiAKQEAgLTYzNSw2ICs2MzYsNyBAQCBz dGF0aWMgdTE2IF9faW5pdCBwYXJzZV9pdmhkX2RldmljZV9zcGVjCiAgICAg dTE2IGhlYWRlcl9sZW5ndGgsIHUxNiBibG9ja19sZW5ndGgsIHN0cnVjdCBh bWRfaW9tbXUgKmlvbW11KQogewogICAgIHUxNiBkZXZfbGVuZ3RoLCBiZGY7 CisgICAgaW50IGFwaWM7CiAKICAgICBkZXZfbGVuZ3RoID0gc2l6ZW9mKCpz cGVjaWFsKTsKICAgICBpZiAoIGhlYWRlcl9sZW5ndGggPCAoYmxvY2tfbGVu Z3RoICsgZGV2X2xlbmd0aCkgKQpAQCAtNjUxLDEwICs2NTMsNTkgQEAgc3Rh dGljIHUxNiBfX2luaXQgcGFyc2VfaXZoZF9kZXZpY2Vfc3BlYwogICAgIH0K IAogICAgIGFkZF9pdnJzX21hcHBpbmdfZW50cnkoYmRmLCBiZGYsIHNwZWNp YWwtPmhlYWRlci5kYXRhX3NldHRpbmcsIGlvbW11KTsKLSAgICAvKiBzZXQg ZGV2aWNlIGlkIG9mIGlvYXBpYyAqLwotICAgIGlvYXBpY19zYmRmW3NwZWNp YWwtPmhhbmRsZV0uYmRmID0gYmRmOwotICAgIGlvYXBpY19zYmRmW3NwZWNp YWwtPmhhbmRsZV0uc2VnID0gc2VnOwotICAgIHJldHVybiBkZXZfbGVuZ3Ro OworCisgICAgaWYgKCBzcGVjaWFsLT52YXJpZXR5ICE9IEFDUElfSVZIRF9J T0FQSUMgKQorICAgIHsKKyAgICAgICAgaWYgKCBzcGVjaWFsLT52YXJpZXR5 ICE9IEFDUElfSVZIRF9IUEVUICkKKyAgICAgICAgICAgIHByaW50ayhYRU5M T0dfRVJSICJVbnJlY29nbml6ZWQgSVZIRCBzcGVjaWFsIHZhcmlldHkgJSN4 XG4iLAorICAgICAgICAgICAgICAgICAgIHNwZWNpYWwtPnZhcmlldHkpOwor ICAgICAgICByZXR1cm4gZGV2X2xlbmd0aDsKKyAgICB9CisKKyAgICAvKgor ICAgICAqIFNvbWUgQklPU2VzIGhhdmUgSU9BUElDIGJyb2tlbiBlbnRyaWVz IHNvIHdlIGNoZWNrIGZvciBJVlJTCisgICAgICogY29uc2lzdGVuY3kgaGVy ZSAtLS0gd2hldGhlciBlbnRyeSdzIElPQVBJQyBJRCBpcyB2YWxpZCBhbmQK KyAgICAgKiB3aGV0aGVyIHRoZXJlIGFyZSBjb25mbGljdGluZy9kdXBsaWNh dGVkIGVudHJpZXMuCisgICAgICovCisgICAgZm9yICggYXBpYyA9IDA7IGFw aWMgPCBucl9pb2FwaWNzOyBhcGljKysgKQorICAgIHsKKyAgICAgICAgaWYg KCBJT19BUElDX0lEKGFwaWMpICE9IHNwZWNpYWwtPmhhbmRsZSApCisgICAg ICAgICAgICBjb250aW51ZTsKKworICAgICAgICBpZiAoIGlvYXBpY19zYmRm W3NwZWNpYWwtPmhhbmRsZV0ucGluX3NldHVwICkKKyAgICAgICAgeworICAg ICAgICAgICAgaWYgKCBpb2FwaWNfc2JkZltzcGVjaWFsLT5oYW5kbGVdLmJk ZiA9PSBiZGYgJiYKKyAgICAgICAgICAgICAgICAgaW9hcGljX3NiZGZbc3Bl Y2lhbC0+aGFuZGxlXS5zZWcgPT0gc2VnICkKKyAgICAgICAgICAgICAgICBB TURfSU9NTVVfREVCVUcoIklWSEQgV2FybmluZzogRHVwbGljYXRlIElPLUFQ SUMgJSN4IGVudHJpZXNcbiIsCisgICAgICAgICAgICAgICAgICAgICAgICAg ICAgICAgIHNwZWNpYWwtPmhhbmRsZSk7CisgICAgICAgICAgICBlbHNlCisg ICAgICAgICAgICB7CisgICAgICAgICAgICAgICAgcHJpbnRrKFhFTkxPR19F UlIgIklWSEQgRXJyb3I6IENvbmZsaWN0aW5nIElPLUFQSUMgJSN4IGVudHJp ZXNcbiIsCisgICAgICAgICAgICAgICAgICAgICAgIHNwZWNpYWwtPmhhbmRs ZSk7CisgICAgICAgICAgICAgICAgaWYgKCBhbWRfaW9tbXVfcGVyZGV2X2lu dHJlbWFwICkKKyAgICAgICAgICAgICAgICAgICAgcmV0dXJuIDA7CisgICAg ICAgICAgICB9CisgICAgICAgIH0KKyAgICAgICAgZWxzZQorICAgICAgICB7 CisgICAgICAgICAgICAvKiBzZXQgZGV2aWNlIGlkIG9mIGlvYXBpYyAqLwor ICAgICAgICAgICAgaW9hcGljX3NiZGZbc3BlY2lhbC0+aGFuZGxlXS5iZGYg PSBiZGY7CisgICAgICAgICAgICBpb2FwaWNfc2JkZltzcGVjaWFsLT5oYW5k bGVdLnNlZyA9IHNlZzsKKworICAgICAgICAgICAgaW9hcGljX3NiZGZbc3Bl Y2lhbC0+aGFuZGxlXS5waW5fc2V0dXAgPSB4emFsbG9jX2FycmF5KAorICAg ICAgICAgICAgICAgIHVuc2lnbmVkIGxvbmcsIEJJVFNfVE9fTE9OR1MobnJf aW9hcGljX2VudHJpZXNbYXBpY10pKTsKKyAgICAgICAgICAgIGlmICggbnJf aW9hcGljX2VudHJpZXNbYXBpY10gJiYKKyAgICAgICAgICAgICAgICAgIWlv YXBpY19zYmRmW0lPX0FQSUNfSUQoYXBpYyldLnBpbl9zZXR1cCApCisgICAg ICAgICAgICB7CisgICAgICAgICAgICAgICAgcHJpbnRrKFhFTkxPR19FUlIg IklWSEQgRXJyb3I6IE91dCBvZiBtZW1vcnlcbiIpOworICAgICAgICAgICAg ICAgIHJldHVybiAwOworICAgICAgICAgICAgfQorICAgICAgICB9CisgICAg ICAgIHJldHVybiBkZXZfbGVuZ3RoOworICAgIH0KKworICAgIHByaW50ayhY RU5MT0dfRVJSICJJVkhEIEVycm9yOiBJbnZhbGlkIElPLUFQSUMgJSN4XG4i LCBzcGVjaWFsLT5oYW5kbGUpOworICAgIHJldHVybiAwOwogfQogCiBzdGF0 aWMgaW50IF9faW5pdCBwYXJzZV9pdmhkX2Jsb2NrKGNvbnN0IHN0cnVjdCBh Y3BpX2l2cnNfaGFyZHdhcmUgKml2aGRfYmxvY2spCi0tLSBhL3hlbi9kcml2 ZXJzL3Bhc3N0aHJvdWdoL2FtZC9pb21tdV9pbml0LmMKKysrIGIveGVuL2Ry aXZlcnMvcGFzc3Rocm91Z2gvYW1kL2lvbW11X2luaXQuYwpAQCAtMTEyNiwx MiArMTEyNiw0NSBAQCBzdGF0aWMgaW50IF9faW5pdCBhbWRfaW9tbXVfc2V0 dXBfZGV2aWNlCiAgICAgcmV0dXJuIDA7CiB9CiAKKy8qIENoZWNrIHdoZXRo ZXIgU1A1MTAwIFNBVEEgQ29tYmluZWQgbW9kZSBpcyBvbiAqLworc3RhdGlj IGJvb2xfdCBfX2luaXQgYW1kX3NwNTEwMF9lcnJhdHVtMjgodm9pZCkKK3sK KyAgICB1MzIgYnVzLCBpZDsKKyAgICB1MTYgdmVuZG9yX2lkLCBkZXZfaWQ7 CisgICAgdTggYnl0ZTsKKworICAgIGZvciAoYnVzID0gMDsgYnVzIDwgMjU2 OyBidXMrKykKKyAgICB7CisgICAgICAgIGlkID0gcGNpX2NvbmZfcmVhZDMy KDAsIGJ1cywgMHgxNCwgMCwgUENJX1ZFTkRPUl9JRCk7CisKKyAgICAgICAg dmVuZG9yX2lkID0gaWQgJiAweGZmZmY7CisgICAgICAgIGRldl9pZCA9IChp ZCA+PiAxNikgJiAweGZmZmY7CisKKyAgICAgICAgLyogU1A1MTAwIFNNQnVz IG1vZHVsZSBzZXRzIENvbWJpbmVkIG1vZGUgb24gKi8KKyAgICAgICAgaWYg KHZlbmRvcl9pZCAhPSAweDEwMDIgfHwgZGV2X2lkICE9IDB4NDM4NSkKKyAg ICAgICAgICAgIGNvbnRpbnVlOworCisgICAgICAgIGJ5dGUgPSBwY2lfY29u Zl9yZWFkOCgwLCBidXMsIDB4MTQsIDAsIDB4YWQpOworICAgICAgICBpZiAo IChieXRlID4+IDMpICYgMSApCisgICAgICAgIHsKKyAgICAgICAgICAgIHBy aW50ayhYRU5MT0dfV0FSTklORyAiQU1ELVZpOiBTUDUxMDAgZXJyYXR1bSAy OCBkZXRlY3RlZCwgZGlzYWJsaW5nIElPTU1VLlxuIgorICAgICAgICAgICAg ICAgICAgICJJZiBwb3NzaWJsZSwgZGlzYWJsZSBTQVRBIENvbWJpbmVkIG1v ZGUgaW4gQklPUyBvciBjb250YWN0IHlvdXIgdmVuZG9yIGZvciBCSU9TIHVw ZGF0ZS5cbiIpOworICAgICAgICAgICAgcmV0dXJuIDE7CisgICAgICAgIH0K KyAgICB9CisKKyAgICByZXR1cm4gMDsKK30KKwogaW50IF9faW5pdCBhbWRf aW9tbXVfaW5pdCh2b2lkKQogewogICAgIHN0cnVjdCBhbWRfaW9tbXUgKmlv bW11OwogCiAgICAgQlVHX09OKCAhaW9tbXVfZm91bmQoKSApOwogCisgICAg aWYgKCBhbWRfaW9tbXVfcGVyZGV2X2ludHJlbWFwICYmIGFtZF9zcDUxMDBf ZXJyYXR1bTI4KCkgKQorICAgICAgICBnb3RvIGVycm9yX291dDsKKwogICAg IGl2cnNfYmRmX2VudHJpZXMgPSBhbWRfaW9tbXVfZ2V0X2l2cnNfZGV2X2Vu dHJpZXMoKTsKIAogICAgIGlmICggIWl2cnNfYmRmX2VudHJpZXMgKQotLS0g YS94ZW4vZHJpdmVycy9wYXNzdGhyb3VnaC9hbWQvaW9tbXVfaW50ci5jCisr KyBiL3hlbi9kcml2ZXJzL3Bhc3N0aHJvdWdoL2FtZC9pb21tdV9pbnRyLmMK QEAgLTk5LDEyICs5OSwxMiBAQCBzdGF0aWMgdm9pZCB1cGRhdGVfaW50cmVt YXBfZW50cnkodTMyKiBlCiBzdGF0aWMgdm9pZCB1cGRhdGVfaW50cmVtYXBf ZW50cnlfZnJvbV9pb2FwaWMoCiAgICAgaW50IGJkZiwKICAgICBzdHJ1Y3Qg YW1kX2lvbW11ICppb21tdSwKLSAgICBzdHJ1Y3QgSU9fQVBJQ19yb3V0ZV9l bnRyeSAqaW9hcGljX3J0ZSkKKyAgICBjb25zdCBzdHJ1Y3QgSU9fQVBJQ19y b3V0ZV9lbnRyeSAqcnRlLAorICAgIGNvbnN0IHN0cnVjdCBJT19BUElDX3Jv dXRlX2VudHJ5ICpvbGRfcnRlKQogewogICAgIHVuc2lnbmVkIGxvbmcgZmxh Z3M7CiAgICAgdTMyKiBlbnRyeTsKICAgICB1OCBkZWxpdmVyeV9tb2RlLCBk ZXN0LCB2ZWN0b3IsIGRlc3RfbW9kZTsKLSAgICBzdHJ1Y3QgSU9fQVBJQ19y b3V0ZV9lbnRyeSAqcnRlID0gaW9hcGljX3J0ZTsKICAgICBpbnQgcmVxX2lk OwogICAgIHNwaW5sb2NrX3QgKmxvY2s7CiAgICAgaW50IG9mZnNldDsKQEAg LTEyMCw2ICsxMjAsMTQgQEAgc3RhdGljIHZvaWQgdXBkYXRlX2ludHJlbWFw X2VudHJ5X2Zyb21faQogICAgIHNwaW5fbG9ja19pcnFzYXZlKGxvY2ssIGZs YWdzKTsKIAogICAgIG9mZnNldCA9IGdldF9pbnRyZW1hcF9vZmZzZXQodmVj dG9yLCBkZWxpdmVyeV9tb2RlKTsKKyAgICBpZiAoIG9sZF9ydGUgKQorICAg IHsKKyAgICAgICAgaW50IG9sZF9vZmZzZXQgPSBnZXRfaW50cmVtYXBfb2Zm c2V0KG9sZF9ydGUtPnZlY3RvciwKKyAgICAgICAgICAgICAgICAgICAgICAg ICAgICAgICAgICAgICAgICAgICAgIG9sZF9ydGUtPmRlbGl2ZXJ5X21vZGUp OworCisgICAgICAgIGlmICggb2Zmc2V0ICE9IG9sZF9vZmZzZXQgKQorICAg ICAgICAgICAgZnJlZV9pbnRyZW1hcF9lbnRyeShpb21tdS0+c2VnLCBiZGYs IG9sZF9vZmZzZXQpOworICAgIH0KICAgICBlbnRyeSA9ICh1MzIqKWdldF9p bnRyZW1hcF9lbnRyeShpb21tdS0+c2VnLCByZXFfaWQsIG9mZnNldCk7CiAg ICAgdXBkYXRlX2ludHJlbWFwX2VudHJ5KGVudHJ5LCB2ZWN0b3IsIGRlbGl2 ZXJ5X21vZGUsIGRlc3RfbW9kZSwgZGVzdCk7CiAKQEAgLTE4OCw2ICsxOTYs NyBAQCBpbnQgX19pbml0IGFtZF9pb21tdV9zZXR1cF9pb2FwaWNfcmVtYXBw CiAgICAgICAgICAgICAgICAgYW1kX2lvbW11X2ZsdXNoX2ludHJlbWFwKGlv bW11LCByZXFfaWQpOwogICAgICAgICAgICAgICAgIHNwaW5fdW5sb2NrX2ly cXJlc3RvcmUoJmlvbW11LT5sb2NrLCBmbGFncyk7CiAgICAgICAgICAgICB9 CisgICAgICAgICAgICBzZXRfYml0KHBpbiwgaW9hcGljX3NiZGZbSU9fQVBJ Q19JRChhcGljKV0ucGluX3NldHVwKTsKICAgICAgICAgfQogICAgIH0KICAg ICByZXR1cm4gMDsKQEAgLTE5OSw2ICsyMDgsNyBAQCB2b2lkIGFtZF9pb21t dV9pb2FwaWNfdXBkYXRlX2lyZSgKICAgICBzdHJ1Y3QgSU9fQVBJQ19yb3V0 ZV9lbnRyeSBvbGRfcnRlID0geyAwIH07CiAgICAgc3RydWN0IElPX0FQSUNf cm91dGVfZW50cnkgbmV3X3J0ZSA9IHsgMCB9OwogICAgIHVuc2lnbmVkIGlu dCBydGVfbG8gPSAocmVnICYgMSkgPyByZWcgLSAxIDogcmVnOworICAgIHVu c2lnbmVkIGludCBwaW4gPSAocmVnIC0gMHgxMCkgLyAyOwogICAgIGludCBz YXZlZF9tYXNrLCBzZWcsIGJkZjsKICAgICBzdHJ1Y3QgYW1kX2lvbW11ICpp b21tdTsKIApAQCAtMjM2LDYgKzI0NiwxNCBAQCB2b2lkIGFtZF9pb21tdV9p b2FwaWNfdXBkYXRlX2lyZSgKICAgICAgICAgKigoKHUzMiAqKSZuZXdfcnRl KSArIDEpID0gdmFsdWU7CiAgICAgfQogCisgICAgaWYgKCBuZXdfcnRlLm1h c2sgJiYKKyAgICAgICAgICF0ZXN0X2JpdChwaW4sIGlvYXBpY19zYmRmW0lP X0FQSUNfSUQoYXBpYyldLnBpbl9zZXR1cCkgKQorICAgIHsKKyAgICAgICAg QVNTRVJUKHNhdmVkX21hc2spOworICAgICAgICBfX2lvX2FwaWNfd3JpdGUo YXBpYywgcmVnLCB2YWx1ZSk7CisgICAgICAgIHJldHVybjsKKyAgICB9CisK ICAgICAvKiBtYXNrIHRoZSBpbnRlcnJ1cHQgd2hpbGUgd2UgY2hhbmdlIHRo ZSBpbnRyZW1hcCB0YWJsZSAqLwogICAgIGlmICggIXNhdmVkX21hc2sgKQog ICAgIHsKQEAgLTI0NCw3ICsyNjIsMTEgQEAgdm9pZCBhbWRfaW9tbXVfaW9h cGljX3VwZGF0ZV9pcmUoCiAgICAgfQogCiAgICAgLyogVXBkYXRlIGludGVy cnVwdCByZW1hcHBpbmcgZW50cnkgKi8KLSAgICB1cGRhdGVfaW50cmVtYXBf ZW50cnlfZnJvbV9pb2FwaWMoYmRmLCBpb21tdSwgJm5ld19ydGUpOworICAg IHVwZGF0ZV9pbnRyZW1hcF9lbnRyeV9mcm9tX2lvYXBpYygKKyAgICAgICAg YmRmLCBpb21tdSwgJm5ld19ydGUsCisgICAgICAgIHRlc3RfYW5kX3NldF9i aXQocGluLAorICAgICAgICAgICAgICAgICAgICAgICAgIGlvYXBpY19zYmRm W0lPX0FQSUNfSUQoYXBpYyldLnBpbl9zZXR1cCkgPyAmb2xkX3J0ZQorICAg ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg ICAgICAgICAgICAgICAgICAgOiBOVUxMKTsKIAogICAgIC8qIEZvcndhcmQg d3JpdGUgYWNjZXNzIHRvIElPLUFQSUMgUlRFICovCiAgICAgX19pb19hcGlj X3dyaXRlKGFwaWMsIHJlZywgdmFsdWUpOwpAQCAtMzU0LDYgKzM3NiwxMiBA QCB2b2lkIGFtZF9pb21tdV9tc2lfbXNnX3VwZGF0ZV9pcmUoCiAgICAgICAg IHJldHVybjsKICAgICB9CiAKKyAgICBpZiAoIG1zaV9kZXNjLT5yZW1hcF9p bmRleCA+PSAwICkKKyAgICAgICAgdXBkYXRlX2ludHJlbWFwX2VudHJ5X2Zy b21fbXNpX21zZyhpb21tdSwgcGRldiwgbXNpX2Rlc2MsIE5VTEwpOworCisg ICAgaWYgKCAhbXNnICkKKyAgICAgICAgcmV0dXJuOworCiAgICAgdXBkYXRl X2ludHJlbWFwX2VudHJ5X2Zyb21fbXNpX21zZyhpb21tdSwgcGRldiwgbXNp X2Rlc2MsIG1zZyk7CiB9CiAKLS0tIGEveGVuL2RyaXZlcnMvcGFzc3Rocm91 Z2gvYW1kL3BjaV9hbWRfaW9tbXUuYworKysgYi94ZW4vZHJpdmVycy9wYXNz dGhyb3VnaC9hbWQvcGNpX2FtZF9pb21tdS5jCkBAIC0yMDUsNiArMjA1LDgg QEAgaW50IF9faW5pdCBhbWRfaW92X2RldGVjdCh2b2lkKQogICAgIHsKICAg ICAgICAgcHJpbnRrKCJBTUQtVmk6IE5vdCBvdmVycmlkaW5nIGlycV92ZWN0 b3JfbWFwIHNldHRpbmdcbiIpOwogICAgIH0KKyAgICBpZiAoICFhbWRfaW9t bXVfcGVyZGV2X2ludHJlbWFwICkKKyAgICAgICAgcHJpbnRrKFhFTkxPR19X QVJOSU5HICJBTUQtVmk6IFVzaW5nIGdsb2JhbCBpbnRlcnJ1cHQgcmVtYXAg dGFibGUgaXMgbm90IHJlY29tbWVuZGVkIChzZWUgWFNBLTM2KSFcbiIpOwog ICAgIHJldHVybiBzY2FuX3BjaV9kZXZpY2VzKCk7CiB9CiAKLS0tIGEveGVu L2RyaXZlcnMvcGFzc3Rocm91Z2gvaW9tbXUuYworKysgYi94ZW4vZHJpdmVy cy9wYXNzdGhyb3VnaC9pb21tdS5jCkBAIC01Miw3ICs1Miw3IEBAIGJvb2xf dCBfX3JlYWRfbW9zdGx5IGlvbW11X3FpbnZhbCA9IDE7CiBib29sX3QgX19y ZWFkX21vc3RseSBpb21tdV9pbnRyZW1hcCA9IDE7CiBib29sX3QgX19yZWFk X21vc3RseSBpb21tdV9oYXBfcHRfc2hhcmUgPSAxOwogYm9vbF90IF9fcmVh ZF9tb3N0bHkgaW9tbXVfZGVidWc7Ci1ib29sX3QgX19yZWFkX21vc3RseSBh bWRfaW9tbXVfcGVyZGV2X2ludHJlbWFwOworYm9vbF90IF9fcmVhZF9tb3N0 bHkgYW1kX2lvbW11X3BlcmRldl9pbnRyZW1hcCA9IDE7CiAKIERFRklORV9Q RVJfQ1BVKGJvb2xfdCwgaW9tbXVfZG9udF9mbHVzaF9pb3RsYik7CiAKLS0t IGEveGVuL2luY2x1ZGUvYXNtLXg4Ni9odm0vc3ZtL2FtZC1pb21tdS1wcm90 by5oCisrKyBiL3hlbi9pbmNsdWRlL2FzbS14ODYvaHZtL3N2bS9hbWQtaW9t bXUtcHJvdG8uaApAQCAtMTAwLDYgKzEwMCw3IEBAIHZvaWQgYW1kX2lvbW11 X3JlYWRfbXNpX2Zyb21faXJlKAogCiBleHRlcm4gc3RydWN0IGlvYXBpY19z YmRmIHsKICAgICB1MTYgYmRmLCBzZWc7CisgICAgdW5zaWduZWQgbG9uZyAq cGluX3NldHVwOwogfSBpb2FwaWNfc2JkZltNQVhfSU9fQVBJQ1NdOwogZXh0 ZXJuIHZvaWQgKnNoYXJlZF9pbnRyZW1hcF90YWJsZTsKIAo= --=separator Content-Type: application/octet-stream; name="xsa36-unstable.patch" Content-Disposition: attachment; filename="xsa36-unstable.patch" Content-Transfer-Encoding: base64 QUNQSTogYWNwaV90YWJsZV9wYXJzZSgpIHNob3VsZCByZXR1cm4gaGFuZGxl cidzIGVycm9yIGNvZGUKCkN1cnJlbnRseSwgdGhlIGVycm9yIGNvZGUgcmV0 dXJuZWQgYnkgYWNwaV90YWJsZV9wYXJzZSgpJ3MgaGFuZGxlcgppcyBpZ25v cmVkLiBUaGlzIHBhdGNoIHdpbGwgcHJvcGFnYXRlIGhhbmRsZXIncyByZXR1 cm4gdmFsdWUgdG8KYWNwaV90YWJsZV9wYXJzZSgpJ3MgY2FsbGVyLgoKQU1E LElPTU1VOiBDbGVhbiB1cCBvbGQgZW50cmllcyBpbiByZW1hcHBpbmcgdGFi bGVzIHdoZW4gY3JlYXRpbmcgbmV3CmludGVycnVwdCBtYXBwaW5nLgoKV2hl biBjaGFuZ2luZyB0aGUgYWZmaW5pdHkgb2YgYW4gSVJRIGFzc29jaWF0ZWQg d2l0aCBhIHBhc3NlZAp0aHJvdWdoIFBDSSBkZXZpY2UsIGNsZWFyIHByZXZp b3VzIG1hcHBpbmcuCgpJbiBhZGRpdGlvbiwgYmVjYXVzZSBzb21lIEJJT1Nl cyBtYXkgaW5jb3JyZWN0bHkgcHJvZ3JhbSBJVlJTCmVudHJpZXMgZm9yIElP QVBJQyB0cnkgdG8gY2hlY2sgZm9yIGVudHJ5J3MgY29uc2lzdGVuY3kuIFNw ZWNpZmljYWxseSwKaWYgY29uZmxpY3RpbmcgZW50cmllcyBhcmUgZm91bmQg ZGlzYWJsZSBJT01NVSBpZiBwZXItZGV2aWNlCnJlbWFwcGluZyB0YWJsZSBp cyB1c2VkLiBJZiBlbnRyaWVzIHJlZmVyIHRvIGJvZ3VzIElPQVBJQyBJRHMK ZGlzYWJsZSBJT01NVSB1bmNvbmRpdGlvbmFsbHkKCkFNRCxJT01NVTogRGlz YWJsZSBJT01NVSBpZiBTQVRBIENvbWJpbmVkIG1vZGUgaXMgb24KCkFNRCdz IFNQNTEwMCBjaGlwc2V0IGNhbiBiZSBwbGFjZWQgaW50byBTQVRBIENvbWJp bmVkIG1vZGUKdGhhdCBtYXkgY2F1c2UgcHJldmVudCBkb20wIGZyb20gYm9v dGluZyB3aGVuIElPTU1VIGlzCmVuYWJsZWQgYW5kIHBlci1kZXZpY2UgaW50 ZXJydXB0IHJlbWFwcGluZyB0YWJsZSBpcyB1c2VkLgpXaGlsZSBTUDUxMDAg ZXJyYXR1bSAyOCByZXF1aXJlcyBCSU9TZXMgdG8gZGlzYWJsZSB0aGlzIG1v ZGUsCnNvbWUgbWF5IHN0aWxsIHVzZSBpdC4KClRoaXMgcGF0Y2ggY2hlY2tz IHdoZXRoZXIgdGhpcyBtb2RlIGlzIG9uIGFuZCwgaWYgcGVyLWRldmljZQp0 YWJsZSBpcyBpbiB1c2UsIGRpc2FibGVzIElPTU1VLgoKQU1ELElPTU1VOiBN YWtlIHBlci1kZXZpY2UgaW50ZXJydXB0IHJlbWFwcGluZyB0YWJsZSBkZWZh dWx0CgpVc2luZyBnbG9iYWwgaW50ZXJydXB0IHJlbWFwcGluZyB0YWJsZSBt YXkgYmUgaW5zZWN1cmUsIGFzCmRlc2NyaWJlZCBieSBYU0EtMzYuIFRoaXMg cGF0Y2ggbWFrZXMgcGVyLWRldmljZSBtb2RlIGRlZmF1bHQuCgpUaGlzIGlz IFhTQS0zNiAvIENWRS0yMDEzLTAxNTMuCgpTaWduZWQtb2ZmLWJ5OiBKYW4g QmV1bGljaCA8amJldWxpY2hAc3VzZS5jb20+ClNpZ25lZC1vZmYtYnk6IEJv cmlzIE9zdHJvdnNreSA8Ym9yaXMub3N0cm92c2t5QGFtZC5jb20+CgotLS0g YS94ZW4vYXJjaC94ODYvaXJxLmMKKysrIGIveGVuL2FyY2gveDg2L2lycS5j CkBAIC0xOTQzLDkgKzE5NDMsNiBAQCBpbnQgbWFwX2RvbWFpbl9waXJxKAog ICAgICAgICBzcGluX2xvY2tfaXJxc2F2ZSgmZGVzYy0+bG9jaywgZmxhZ3Mp OwogICAgICAgICBzZXRfZG9tYWluX2lycV9waXJxKGQsIGlycSwgaW5mbyk7 CiAgICAgICAgIHNwaW5fdW5sb2NrX2lycXJlc3RvcmUoJmRlc2MtPmxvY2ss IGZsYWdzKTsKLQotICAgICAgICBpZiAoIG9wdF9pcnFfdmVjdG9yX21hcCA9 PSBPUFRfSVJRX1ZFQ1RPUl9NQVBfUEVSREVWICkKLSAgICAgICAgICAgIHBy aW50ayhYRU5MT0dfSU5GTyAiUGVyLWRldmljZSB2ZWN0b3IgbWFwcyBmb3Ig R1NJcyBub3QgaW1wbGVtZW50ZWQgeWV0LlxuIik7CiAgICAgfQogCiBkb25l OgotLS0gYS94ZW4vZHJpdmVycy9hY3BpL3RhYmxlcy5jCisrKyBiL3hlbi9k cml2ZXJzL2FjcGkvdGFibGVzLmMKQEAgLTI2NSw3ICsyNjUsNyBAQCBhY3Bp X3RhYmxlX3BhcnNlX21hZHQoZW51bSBhY3BpX21hZHRfdHlwCiAgKiBAaGFu ZGxlcjogaGFuZGxlciB0byBydW4KICAqCiAgKiBTY2FuIHRoZSBBQ1BJIFN5 c3RlbSBEZXNjcmlwdG9yIFRhYmxlIChTVEQpIGZvciBhIHRhYmxlIG1hdGNo aW5nIEBpZCwKLSAqIHJ1biBAaGFuZGxlciBvbiBpdC4gIFJldHVybiAwIGlm IHRhYmxlIGZvdW5kLCByZXR1cm4gb24gaWYgbm90LgorICogcnVuIEBoYW5k bGVyIG9uIGl0LgogICovCiBpbnQgX19pbml0IGFjcGlfdGFibGVfcGFyc2Uo Y2hhciAqaWQsIGFjcGlfdGFibGVfaGFuZGxlciBoYW5kbGVyKQogewpAQCAt MjgwLDggKzI4MCw3IEBAIGludCBfX2luaXQgYWNwaV90YWJsZV9wYXJzZShj aGFyICppZCwgYWMKIAkJYWNwaV9nZXRfdGFibGUoaWQsIDAsICZ0YWJsZSk7 CiAKIAlpZiAodGFibGUpIHsKLQkJaGFuZGxlcih0YWJsZSk7Ci0JCXJldHVy biAwOworCQlyZXR1cm4gaGFuZGxlcih0YWJsZSk7CiAJfSBlbHNlCiAJCXJl dHVybiAxOwogfQotLS0gYS94ZW4vZHJpdmVycy9wYXNzdGhyb3VnaC9hbWQv aW9tbXVfYWNwaS5jCisrKyBiL3hlbi9kcml2ZXJzL3Bhc3N0aHJvdWdoL2Ft ZC9pb21tdV9hY3BpLmMKQEAgLTIyLDYgKzIyLDcgQEAKICNpbmNsdWRlIDx4 ZW4vZXJybm8uaD4KICNpbmNsdWRlIDx4ZW4vYWNwaS5oPgogI2luY2x1ZGUg PGFzbS9hcGljZGVmLmg+CisjaW5jbHVkZSA8YXNtL2lvX2FwaWMuaD4KICNp bmNsdWRlIDxhc20vYW1kLWlvbW11Lmg+CiAjaW5jbHVkZSA8YXNtL2h2bS9z dm0vYW1kLWlvbW11LXByb3RvLmg+CiAKQEAgLTYzNyw2ICs2MzgsNyBAQCBz dGF0aWMgdTE2IF9faW5pdCBwYXJzZV9pdmhkX2RldmljZV9zcGVjCiAgICAg dTE2IGhlYWRlcl9sZW5ndGgsIHUxNiBibG9ja19sZW5ndGgsIHN0cnVjdCBh bWRfaW9tbXUgKmlvbW11KQogewogICAgIHUxNiBkZXZfbGVuZ3RoLCBiZGY7 CisgICAgaW50IGFwaWM7CiAKICAgICBkZXZfbGVuZ3RoID0gc2l6ZW9mKCpz cGVjaWFsKTsKICAgICBpZiAoIGhlYWRlcl9sZW5ndGggPCAoYmxvY2tfbGVu Z3RoICsgZGV2X2xlbmd0aCkgKQpAQCAtNjU3LDkgKzY1OSw1MyBAQCBzdGF0 aWMgdTE2IF9faW5pdCBwYXJzZV9pdmhkX2RldmljZV9zcGVjCiAgICAgc3dp dGNoICggc3BlY2lhbC0+dmFyaWV0eSApCiAgICAgewogICAgIGNhc2UgQUNQ SV9JVkhEX0lPQVBJQzoKLSAgICAvKiBzZXQgZGV2aWNlIGlkIG9mIGlvYXBp YyAqLwotICAgICAgICBpb2FwaWNfc2JkZltzcGVjaWFsLT5oYW5kbGVdLmJk ZiA9IGJkZjsKLSAgICAgICAgaW9hcGljX3NiZGZbc3BlY2lhbC0+aGFuZGxl XS5zZWcgPSBzZWc7CisgICAgICAgIC8qCisgICAgICAgICAqIFNvbWUgQklP U2VzIGhhdmUgSU9BUElDIGJyb2tlbiBlbnRyaWVzIHNvIHdlIGNoZWNrIGZv ciBJVlJTCisgICAgICAgICAqIGNvbnNpc3RlbmN5IGhlcmUgLS0tIHdoZXRo ZXIgZW50cnkncyBJT0FQSUMgSUQgaXMgdmFsaWQgYW5kCisgICAgICAgICAq IHdoZXRoZXIgdGhlcmUgYXJlIGNvbmZsaWN0aW5nL2R1cGxpY2F0ZWQgZW50 cmllcy4KKyAgICAgICAgICovCisgICAgICAgIGZvciAoIGFwaWMgPSAwOyBh cGljIDwgbnJfaW9hcGljczsgYXBpYysrICkKKyAgICAgICAgeworICAgICAg ICAgICAgaWYgKCBJT19BUElDX0lEKGFwaWMpICE9IHNwZWNpYWwtPmhhbmRs ZSApCisgICAgICAgICAgICAgICAgY29udGludWU7CisKKyAgICAgICAgICAg IGlmICggaW9hcGljX3NiZGZbc3BlY2lhbC0+aGFuZGxlXS5waW5fc2V0dXAg KQorICAgICAgICAgICAgeworICAgICAgICAgICAgICAgIGlmICggaW9hcGlj X3NiZGZbc3BlY2lhbC0+aGFuZGxlXS5iZGYgPT0gYmRmICYmCisgICAgICAg ICAgICAgICAgICAgICBpb2FwaWNfc2JkZltzcGVjaWFsLT5oYW5kbGVdLnNl ZyA9PSBzZWcgKQorICAgICAgICAgICAgICAgICAgICBBTURfSU9NTVVfREVC VUcoIklWSEQgV2FybmluZzogRHVwbGljYXRlIElPLUFQSUMgJSN4IGVudHJp ZXNcbiIsCisgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICBz cGVjaWFsLT5oYW5kbGUpOworICAgICAgICAgICAgICAgIGVsc2UKKyAgICAg ICAgICAgICAgICB7CisgICAgICAgICAgICAgICAgICAgIHByaW50ayhYRU5M T0dfRVJSICJJVkhEIEVycm9yOiBDb25mbGljdGluZyBJTy1BUElDICUjeCBl bnRyaWVzXG4iLAorICAgICAgICAgICAgICAgICAgICAgICAgICAgc3BlY2lh bC0+aGFuZGxlKTsKKyAgICAgICAgICAgICAgICAgICAgaWYgKCBhbWRfaW9t bXVfcGVyZGV2X2ludHJlbWFwICkKKyAgICAgICAgICAgICAgICAgICAgICAg IHJldHVybiAwOworICAgICAgICAgICAgICAgIH0KKyAgICAgICAgICAgIH0K KyAgICAgICAgICAgIGVsc2UKKyAgICAgICAgICAgIHsKKyAgICAgICAgICAg ICAgICAvKiBzZXQgZGV2aWNlIGlkIG9mIGlvYXBpYyAqLworICAgICAgICAg ICAgICAgIGlvYXBpY19zYmRmW3NwZWNpYWwtPmhhbmRsZV0uYmRmID0gYmRm OworICAgICAgICAgICAgICAgIGlvYXBpY19zYmRmW3NwZWNpYWwtPmhhbmRs ZV0uc2VnID0gc2VnOworCisgICAgICAgICAgICAgICAgaW9hcGljX3NiZGZb c3BlY2lhbC0+aGFuZGxlXS5waW5fc2V0dXAgPSB4emFsbG9jX2FycmF5KAor ICAgICAgICAgICAgICAgICAgICB1bnNpZ25lZCBsb25nLCBCSVRTX1RPX0xP TkdTKG5yX2lvYXBpY19lbnRyaWVzW2FwaWNdKSk7CisgICAgICAgICAgICAg ICAgaWYgKCBucl9pb2FwaWNfZW50cmllc1thcGljXSAmJgorICAgICAgICAg ICAgICAgICAgICAgIWlvYXBpY19zYmRmW0lPX0FQSUNfSUQoYXBpYyldLnBp bl9zZXR1cCApCisgICAgICAgICAgICAgICAgeworICAgICAgICAgICAgICAg ICAgICBwcmludGsoWEVOTE9HX0VSUiAiSVZIRCBFcnJvcjogT3V0IG9mIG1l bW9yeVxuIik7CisgICAgICAgICAgICAgICAgICAgIHJldHVybiAwOworICAg ICAgICAgICAgICAgIH0KKyAgICAgICAgICAgIH0KKyAgICAgICAgICAgIGJy ZWFrOworICAgICAgICB9CisgICAgICAgIGlmICggYXBpYyA9PSBucl9pb2Fw aWNzICkKKyAgICAgICAgeworICAgICAgICAgICAgcHJpbnRrKFhFTkxPR19F UlIgIklWSEQgRXJyb3I6IEludmFsaWQgSU8tQVBJQyAlI3hcbiIsCisgICAg ICAgICAgICAgICAgICAgc3BlY2lhbC0+aGFuZGxlKTsKKyAgICAgICAgICAg IHJldHVybiAwOworICAgICAgICB9CiAgICAgICAgIGJyZWFrOwogICAgIGNh c2UgQUNQSV9JVkhEX0hQRVQ6CiAgICAgICAgIC8qIHNldCBkZXZpY2UgaWQg b2YgaHBldCAqLwotLS0gYS94ZW4vZHJpdmVycy9wYXNzdGhyb3VnaC9hbWQv aW9tbXVfaW5pdC5jCisrKyBiL3hlbi9kcml2ZXJzL3Bhc3N0aHJvdWdoL2Ft ZC9pb21tdV9pbml0LmMKQEAgLTExMjAsMTIgKzExMjAsNDUgQEAgc3RhdGlj IGludCBfX2luaXQgYW1kX2lvbW11X3NldHVwX2RldmljZQogICAgIHJldHVy biAwOwogfQogCisvKiBDaGVjayB3aGV0aGVyIFNQNTEwMCBTQVRBIENvbWJp bmVkIG1vZGUgaXMgb24gKi8KK3N0YXRpYyBib29sX3QgX19pbml0IGFtZF9z cDUxMDBfZXJyYXR1bTI4KHZvaWQpCit7CisgICAgdTMyIGJ1cywgaWQ7Cisg ICAgdTE2IHZlbmRvcl9pZCwgZGV2X2lkOworICAgIHU4IGJ5dGU7CisKKyAg ICBmb3IgKGJ1cyA9IDA7IGJ1cyA8IDI1NjsgYnVzKyspCisgICAgeworICAg ICAgICBpZCA9IHBjaV9jb25mX3JlYWQzMigwLCBidXMsIDB4MTQsIDAsIFBD SV9WRU5ET1JfSUQpOworCisgICAgICAgIHZlbmRvcl9pZCA9IGlkICYgMHhm ZmZmOworICAgICAgICBkZXZfaWQgPSAoaWQgPj4gMTYpICYgMHhmZmZmOwor CisgICAgICAgIC8qIFNQNTEwMCBTTUJ1cyBtb2R1bGUgc2V0cyBDb21iaW5l ZCBtb2RlIG9uICovCisgICAgICAgIGlmICh2ZW5kb3JfaWQgIT0gMHgxMDAy IHx8IGRldl9pZCAhPSAweDQzODUpCisgICAgICAgICAgICBjb250aW51ZTsK KworICAgICAgICBieXRlID0gcGNpX2NvbmZfcmVhZDgoMCwgYnVzLCAweDE0 LCAwLCAweGFkKTsKKyAgICAgICAgaWYgKCAoYnl0ZSA+PiAzKSAmIDEgKQor ICAgICAgICB7CisgICAgICAgICAgICBwcmludGsoWEVOTE9HX1dBUk5JTkcg IkFNRC1WaTogU1A1MTAwIGVycmF0dW0gMjggZGV0ZWN0ZWQsIGRpc2FibGlu ZyBJT01NVS5cbiIKKyAgICAgICAgICAgICAgICAgICAiSWYgcG9zc2libGUs IGRpc2FibGUgU0FUQSBDb21iaW5lZCBtb2RlIGluIEJJT1Mgb3IgY29udGFj dCB5b3VyIHZlbmRvciBmb3IgQklPUyB1cGRhdGUuXG4iKTsKKyAgICAgICAg ICAgIHJldHVybiAxOworICAgICAgICB9CisgICAgfQorCisgICAgcmV0dXJu IDA7Cit9CisKIGludCBfX2luaXQgYW1kX2lvbW11X2luaXQodm9pZCkKIHsK ICAgICBzdHJ1Y3QgYW1kX2lvbW11ICppb21tdTsKIAogICAgIEJVR19PTigg IWlvbW11X2ZvdW5kKCkgKTsKIAorICAgIGlmICggYW1kX2lvbW11X3BlcmRl dl9pbnRyZW1hcCAmJiBhbWRfc3A1MTAwX2VycmF0dW0yOCgpICkKKyAgICAg ICAgZ290byBlcnJvcl9vdXQ7CisKICAgICBpdnJzX2JkZl9lbnRyaWVzID0g YW1kX2lvbW11X2dldF9pdnJzX2Rldl9lbnRyaWVzKCk7CiAKICAgICBpZiAo ICFpdnJzX2JkZl9lbnRyaWVzICkKLS0tIGEveGVuL2RyaXZlcnMvcGFzc3Ro cm91Z2gvYW1kL2lvbW11X2ludHIuYworKysgYi94ZW4vZHJpdmVycy9wYXNz dGhyb3VnaC9hbWQvaW9tbXVfaW50ci5jCkBAIC0xMDAsMTIgKzEwMCwxMiBA QCBzdGF0aWMgdm9pZCB1cGRhdGVfaW50cmVtYXBfZW50cnkodTMyKiBlCiBz dGF0aWMgdm9pZCB1cGRhdGVfaW50cmVtYXBfZW50cnlfZnJvbV9pb2FwaWMo CiAgICAgaW50IGJkZiwKICAgICBzdHJ1Y3QgYW1kX2lvbW11ICppb21tdSwK LSAgICBzdHJ1Y3QgSU9fQVBJQ19yb3V0ZV9lbnRyeSAqaW9hcGljX3J0ZSkK KyAgICBjb25zdCBzdHJ1Y3QgSU9fQVBJQ19yb3V0ZV9lbnRyeSAqcnRlLAor ICAgIGNvbnN0IHN0cnVjdCBJT19BUElDX3JvdXRlX2VudHJ5ICpvbGRfcnRl KQogewogICAgIHVuc2lnbmVkIGxvbmcgZmxhZ3M7CiAgICAgdTMyKiBlbnRy eTsKICAgICB1OCBkZWxpdmVyeV9tb2RlLCBkZXN0LCB2ZWN0b3IsIGRlc3Rf bW9kZTsKLSAgICBzdHJ1Y3QgSU9fQVBJQ19yb3V0ZV9lbnRyeSAqcnRlID0g aW9hcGljX3J0ZTsKICAgICBpbnQgcmVxX2lkOwogICAgIHNwaW5sb2NrX3Qg KmxvY2s7CiAgICAgaW50IG9mZnNldDsKQEAgLTEyMSw2ICsxMjEsMTQgQEAg c3RhdGljIHZvaWQgdXBkYXRlX2ludHJlbWFwX2VudHJ5X2Zyb21faQogICAg IHNwaW5fbG9ja19pcnFzYXZlKGxvY2ssIGZsYWdzKTsKIAogICAgIG9mZnNl dCA9IGdldF9pbnRyZW1hcF9vZmZzZXQodmVjdG9yLCBkZWxpdmVyeV9tb2Rl KTsKKyAgICBpZiAoIG9sZF9ydGUgKQorICAgIHsKKyAgICAgICAgaW50IG9s ZF9vZmZzZXQgPSBnZXRfaW50cmVtYXBfb2Zmc2V0KG9sZF9ydGUtPnZlY3Rv ciwKKyAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg ICAgIG9sZF9ydGUtPmRlbGl2ZXJ5X21vZGUpOworCisgICAgICAgIGlmICgg b2Zmc2V0ICE9IG9sZF9vZmZzZXQgKQorICAgICAgICAgICAgZnJlZV9pbnRy ZW1hcF9lbnRyeShpb21tdS0+c2VnLCBiZGYsIG9sZF9vZmZzZXQpOworICAg IH0KICAgICBlbnRyeSA9ICh1MzIqKWdldF9pbnRyZW1hcF9lbnRyeShpb21t dS0+c2VnLCByZXFfaWQsIG9mZnNldCk7CiAgICAgdXBkYXRlX2ludHJlbWFw X2VudHJ5KGVudHJ5LCB2ZWN0b3IsIGRlbGl2ZXJ5X21vZGUsIGRlc3RfbW9k ZSwgZGVzdCk7CiAKQEAgLTE4OSw2ICsxOTcsNyBAQCBpbnQgX19pbml0IGFt ZF9pb21tdV9zZXR1cF9pb2FwaWNfcmVtYXBwCiAgICAgICAgICAgICAgICAg YW1kX2lvbW11X2ZsdXNoX2ludHJlbWFwKGlvbW11LCByZXFfaWQpOwogICAg ICAgICAgICAgICAgIHNwaW5fdW5sb2NrX2lycXJlc3RvcmUoJmlvbW11LT5s b2NrLCBmbGFncyk7CiAgICAgICAgICAgICB9CisgICAgICAgICAgICBzZXRf Yml0KHBpbiwgaW9hcGljX3NiZGZbSU9fQVBJQ19JRChhcGljKV0ucGluX3Nl dHVwKTsKICAgICAgICAgfQogICAgIH0KICAgICByZXR1cm4gMDsKQEAgLTIw MCw2ICsyMDksNyBAQCB2b2lkIGFtZF9pb21tdV9pb2FwaWNfdXBkYXRlX2ly ZSgKICAgICBzdHJ1Y3QgSU9fQVBJQ19yb3V0ZV9lbnRyeSBvbGRfcnRlID0g eyAwIH07CiAgICAgc3RydWN0IElPX0FQSUNfcm91dGVfZW50cnkgbmV3X3J0 ZSA9IHsgMCB9OwogICAgIHVuc2lnbmVkIGludCBydGVfbG8gPSAocmVnICYg MSkgPyByZWcgLSAxIDogcmVnOworICAgIHVuc2lnbmVkIGludCBwaW4gPSAo cmVnIC0gMHgxMCkgLyAyOwogICAgIGludCBzYXZlZF9tYXNrLCBzZWcsIGJk ZjsKICAgICBzdHJ1Y3QgYW1kX2lvbW11ICppb21tdTsKIApAQCAtMjM3LDYg KzI0NywxNCBAQCB2b2lkIGFtZF9pb21tdV9pb2FwaWNfdXBkYXRlX2lyZSgK ICAgICAgICAgKigoKHUzMiAqKSZuZXdfcnRlKSArIDEpID0gdmFsdWU7CiAg ICAgfQogCisgICAgaWYgKCBuZXdfcnRlLm1hc2sgJiYKKyAgICAgICAgICF0 ZXN0X2JpdChwaW4sIGlvYXBpY19zYmRmW0lPX0FQSUNfSUQoYXBpYyldLnBp bl9zZXR1cCkgKQorICAgIHsKKyAgICAgICAgQVNTRVJUKHNhdmVkX21hc2sp OworICAgICAgICBfX2lvX2FwaWNfd3JpdGUoYXBpYywgcmVnLCB2YWx1ZSk7 CisgICAgICAgIHJldHVybjsKKyAgICB9CisKICAgICAvKiBtYXNrIHRoZSBp bnRlcnJ1cHQgd2hpbGUgd2UgY2hhbmdlIHRoZSBpbnRyZW1hcCB0YWJsZSAq LwogICAgIGlmICggIXNhdmVkX21hc2sgKQogICAgIHsKQEAgLTI0NSw3ICsy NjMsMTEgQEAgdm9pZCBhbWRfaW9tbXVfaW9hcGljX3VwZGF0ZV9pcmUoCiAg ICAgfQogCiAgICAgLyogVXBkYXRlIGludGVycnVwdCByZW1hcHBpbmcgZW50 cnkgKi8KLSAgICB1cGRhdGVfaW50cmVtYXBfZW50cnlfZnJvbV9pb2FwaWMo YmRmLCBpb21tdSwgJm5ld19ydGUpOworICAgIHVwZGF0ZV9pbnRyZW1hcF9l bnRyeV9mcm9tX2lvYXBpYygKKyAgICAgICAgYmRmLCBpb21tdSwgJm5ld19y dGUsCisgICAgICAgIHRlc3RfYW5kX3NldF9iaXQocGluLAorICAgICAgICAg ICAgICAgICAgICAgICAgIGlvYXBpY19zYmRmW0lPX0FQSUNfSUQoYXBpYyld LnBpbl9zZXR1cCkgPyAmb2xkX3J0ZQorICAgICAgICAgICAgICAgICAgICAg ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg OiBOVUxMKTsKIAogICAgIC8qIEZvcndhcmQgd3JpdGUgYWNjZXNzIHRvIElP LUFQSUMgUlRFICovCiAgICAgX19pb19hcGljX3dyaXRlKGFwaWMsIHJlZywg dmFsdWUpOwpAQCAtMzU2LDYgKzM3OCwxMiBAQCB2b2lkIGFtZF9pb21tdV9t c2lfbXNnX3VwZGF0ZV9pcmUoCiAgICAgICAgIHJldHVybjsKICAgICB9CiAK KyAgICBpZiAoIG1zaV9kZXNjLT5yZW1hcF9pbmRleCA+PSAwICkKKyAgICAg ICAgdXBkYXRlX2ludHJlbWFwX2VudHJ5X2Zyb21fbXNpX21zZyhpb21tdSwg YmRmLCBtc2lfZGVzYywgTlVMTCk7CisKKyAgICBpZiAoICFtc2cgKQorICAg ICAgICByZXR1cm47CisKICAgICB1cGRhdGVfaW50cmVtYXBfZW50cnlfZnJv bV9tc2lfbXNnKGlvbW11LCBiZGYsIG1zaV9kZXNjLCBtc2cpOwogfQogCi0t LSBhL3hlbi9kcml2ZXJzL3Bhc3N0aHJvdWdoL2FtZC9wY2lfYW1kX2lvbW11 LmMKKysrIGIveGVuL2RyaXZlcnMvcGFzc3Rocm91Z2gvYW1kL3BjaV9hbWRf aW9tbXUuYwpAQCAtMjA4LDYgKzIwOCw4IEBAIGludCBfX2luaXQgYW1kX2lv dl9kZXRlY3Qodm9pZCkKICAgICB7CiAgICAgICAgIHByaW50aygiQU1ELVZp OiBOb3Qgb3ZlcnJpZGluZyBpcnFfdmVjdG9yX21hcCBzZXR0aW5nXG4iKTsK ICAgICB9CisgICAgaWYgKCAhYW1kX2lvbW11X3BlcmRldl9pbnRyZW1hcCAp CisgICAgICAgIHByaW50ayhYRU5MT0dfV0FSTklORyAiQU1ELVZpOiBVc2lu ZyBnbG9iYWwgaW50ZXJydXB0IHJlbWFwIHRhYmxlIGlzIG5vdCByZWNvbW1l bmRlZCAoc2VlIFhTQS0zNikhXG4iKTsKICAgICByZXR1cm4gc2Nhbl9wY2lf ZGV2aWNlcygpOwogfQogCi0tLSBhL3hlbi9kcml2ZXJzL3Bhc3N0aHJvdWdo L2lvbW11LmMKKysrIGIveGVuL2RyaXZlcnMvcGFzc3Rocm91Z2gvaW9tbXUu YwpAQCAtNTMsNyArNTMsNyBAQCBib29sX3QgX19yZWFkX21vc3RseSBpb21t dV9xaW52YWwgPSAxOwogYm9vbF90IF9fcmVhZF9tb3N0bHkgaW9tbXVfaW50 cmVtYXAgPSAxOwogYm9vbF90IF9fcmVhZF9tb3N0bHkgaW9tbXVfaGFwX3B0 X3NoYXJlID0gMTsKIGJvb2xfdCBfX3JlYWRfbW9zdGx5IGlvbW11X2RlYnVn OwotYm9vbF90IF9fcmVhZF9tb3N0bHkgYW1kX2lvbW11X3BlcmRldl9pbnRy ZW1hcDsKK2Jvb2xfdCBfX3JlYWRfbW9zdGx5IGFtZF9pb21tdV9wZXJkZXZf aW50cmVtYXAgPSAxOwogCiBERUZJTkVfUEVSX0NQVShib29sX3QsIGlvbW11 X2RvbnRfZmx1c2hfaW90bGIpOwogCi0tLSBhL3hlbi9pbmNsdWRlL2FzbS14 ODYvaHZtL3N2bS9hbWQtaW9tbXUtcHJvdG8uaAorKysgYi94ZW4vaW5jbHVk ZS9hc20teDg2L2h2bS9zdm0vYW1kLWlvbW11LXByb3RvLmgKQEAgLTEwMSw2 ICsxMDEsNyBAQCBpbnQgYW1kX3NldHVwX2hwZXRfbXNpKHN0cnVjdCBtc2lf ZGVzYyAqCiAKIGV4dGVybiBzdHJ1Y3QgaW9hcGljX3NiZGYgewogICAgIHUx NiBiZGYsIHNlZzsKKyAgICB1bnNpZ25lZCBsb25nICpwaW5fc2V0dXA7CiB9 IGlvYXBpY19zYmRmW01BWF9JT19BUElDU107CiBleHRlcm4gdm9pZCAqc2hh cmVkX2ludHJlbWFwX3RhYmxlOwogCg== --=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 Tue Feb 05 13:16:28 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 05 Feb 2013 13:16: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 1U2iNK-0007aJ-Cy; Tue, 05 Feb 2013 13:15:50 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U2iNG-0007YC-H3; Tue, 05 Feb 2013 13:15:47 +0000 Received: from [85.158.138.51:8056] by server-3.bemta-3.messagelabs.com id 27/9E-31070-10601115; Tue, 05 Feb 2013 13:15:45 +0000 X-Env-Sender: ianc@xenbits.xen.org X-Msg-Ref: server-5.tower-174.messagelabs.com!1360070134!28898814!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.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 23853 invoked from network); 5 Feb 2013 13:15:36 -0000 Received: from mail.xen.org (HELO mail.xen.org) (50.57.168.107) by server-5.tower-174.messagelabs.com with AES256-SHA encrypted SMTP; 5 Feb 2013 13:15:36 -0000 Received: from xenbits.xen.org ([50.57.170.242]) by mail.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U2iMZ-0003Zw-6U; Tue, 05 Feb 2013 13:15:03 +0000 Received: from ianc by xenbits.xen.org with local (Exim 4.72) (envelope-from ) id 1U2iMY-00088X-Tl; Tue, 05 Feb 2013 13:15:02 +0000 Date: Tue, 05 Feb 2013 13:15:02 +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 36 (CVE-2013-0153) - interrupt remap entries shared and old ones not cleared on AMD IOMMUs X-BeenThere: xen-users@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-2013-0153 / XSA-36 version 3 interrupt remap entries shared and old ones not cleared on AMD IOMMUs UPDATES IN VERSION 3 ==================== Public release. ISSUE DESCRIPTION ================= To avoid an erratum in early hardware, the Xen AMD IOMMU code by default chooses to use a single interrupt remapping table for the whole system. This sharing implies that any guest with a passed through PCI device that is bus mastering capable can inject interrupts into other guests, including domain 0. Furthermore, regardless of whether a shared interrupt remapping table is in use, old entries are not always cleared, providing opportunities (which accumulate over time) for guests to inject interrupts into other guests, again including domain 0. In a typical Xen system many devices are owned by domain 0 or driver domains, leaving them vulnerable to such an attack. Such a DoS is likely to have an impact on other guests running in the system. IMPACT ====== A malicious domain which is given access to a physical PCI device can mount a denial of service attack affecting the whole system. VULNERABLE SYSTEMS ================== Xen versions 3.3 onwards are vulnerable. Earlier Xen versions do not implement interrupt remapping, and hence do not support secure AMD-Vi PCI passthrough in any case. Only systems using AMD-Vi for PCI passthrough are vulnerable. Any domain which is given access to a PCI device can take advantage of this vulnerability. MITIGATION ========== This issue can be avoided by not assigning PCI devices to untrusted guests. In Xen versions 4.1.3 and above the sharing of the interrupt remapping table (and hence the more severe part of this problem) can be avoided by passing "iommu=amd-iommu-perdev-intremap" as a command line option to the hypervisor. This option is not fully functional on earlier hypervisors. RESOLUTION ========== Applying the appropriate attached patch resolves this issue. Note that on certain systems (SP5100 chipsets with erratum 28 present, or such with broken IVRS ACPI table) these patches will result in the IOMMU not being enabled anymore. This should be dealt with by a BIOS update, if available. Alternatively the check can be overridden by specifying "iommu=no-amd-iommu-perdev-intremap" on the Xen command line ("iommu=amd-iommu-global-intremap" on 4.1.x), at the price of re-opening the security hole addressed by these patches. xsa36-unstable.patch Xen unstable xsa36-4.2.patch Xen 4.2.x xsa36-4.1.patch Xen 4.1.x $ sha256sum xsa36*.patch 2254fa46dcbc164d2d55ad9d519e7aa4ac5b83e9fb8d8e1f224114d08fe44237 xsa36-4.1.patch 6848712b560b522f7d3cede53e29e799624311e7dee6e450f0c02c165a590783 xsa36-4.2.patch 0e5d53c0b2bbbf07ef07bf31d8adeca4c043c0277f122f74557b018dc7348b74 xsa36-unstable.patch $ -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) iQEcBAEBAgAGBQJREQItAAoJEIP+FMlX6CvZapMH/i+AeMV4Mi9EAe97JWto2xrg bCBdq7LEJ1cIpXGbhpXwTRzmsEGJmFR2VwkaxEtk+BuC7bzJ/KRjWYg6viQ7v+0t thHEMtaRYTOIIel8YZ5t+v8oMdEUos7Oo94xhCk+n7ioH6PO+quUTI+aGd0+lcJm d/5TC5f8w+HZNTB0nCQX9tQx5d4veQXghKs1NbKHeMyZ66nMZiqUqVUwQNTaFhUO 9eWyGOik5/mFctRrMxoOZHQm3d36AnDisiOku2CaG1xYYwDaAnOe/u6QcBZcVX3M Q9COmTAWnOfIKYMIFnXRnyHSiw2+oZL6PTD5nX4O68B6hZ8pemVa+lFhSTvxsXM= =5jP3 -----END PGP SIGNATURE----- --=separator Content-Type: application/octet-stream; name="xsa36-4.1.patch" Content-Disposition: attachment; filename="xsa36-4.1.patch" Content-Transfer-Encoding: base64 QUNQSTogYWNwaV90YWJsZV9wYXJzZSgpIHNob3VsZCByZXR1cm4gaGFuZGxl cidzIGVycm9yIGNvZGUKCkN1cnJlbnRseSwgdGhlIGVycm9yIGNvZGUgcmV0 dXJuZWQgYnkgYWNwaV90YWJsZV9wYXJzZSgpJ3MgaGFuZGxlcgppcyBpZ25v cmVkLiBUaGlzIHBhdGNoIHdpbGwgcHJvcGFnYXRlIGhhbmRsZXIncyByZXR1 cm4gdmFsdWUgdG8KYWNwaV90YWJsZV9wYXJzZSgpJ3MgY2FsbGVyLgoKQU1E LElPTU1VOiBDbGVhbiB1cCBvbGQgZW50cmllcyBpbiByZW1hcHBpbmcgdGFi bGVzIHdoZW4gY3JlYXRpbmcgbmV3CmludGVycnVwdCBtYXBwaW5nLgoKV2hl biBjaGFuZ2luZyB0aGUgYWZmaW5pdHkgb2YgYW4gSVJRIGFzc29jaWF0ZWQg d2l0aCBhIHBhc3NlZAp0aHJvdWdoIFBDSSBkZXZpY2UsIGNsZWFyIHByZXZp b3VzIG1hcHBpbmcuCgpJbiBhZGRpdGlvbiwgYmVjYXVzZSBzb21lIEJJT1Nl cyBtYXkgaW5jb3JyZWN0bHkgcHJvZ3JhbSBJVlJTCmVudHJpZXMgZm9yIElP QVBJQyB0cnkgdG8gY2hlY2sgZm9yIGVudHJ5J3MgY29uc2lzdGVuY3kuIFNw ZWNpZmljYWxseSwKaWYgY29uZmxpY3RpbmcgZW50cmllcyBhcmUgZm91bmQg ZGlzYWJsZSBJT01NVSBpZiBwZXItZGV2aWNlCnJlbWFwcGluZyB0YWJsZSBp cyB1c2VkLiBJZiBlbnRyaWVzIHJlZmVyIHRvIGJvZ3VzIElPQVBJQyBJRHMK ZGlzYWJsZSBJT01NVSB1bmNvbmRpdGlvbmFsbHkKCkFNRCxJT01NVTogRGlz YWJsZSBJT01NVSBpZiBTQVRBIENvbWJpbmVkIG1vZGUgaXMgb24KCkFNRCdz IFNQNTEwMCBjaGlwc2V0IGNhbiBiZSBwbGFjZWQgaW50byBTQVRBIENvbWJp bmVkIG1vZGUKdGhhdCBtYXkgY2F1c2UgcHJldmVudCBkb20wIGZyb20gYm9v dGluZyB3aGVuIElPTU1VIGlzCmVuYWJsZWQgYW5kIHBlci1kZXZpY2UgaW50 ZXJydXB0IHJlbWFwcGluZyB0YWJsZSBpcyB1c2VkLgpXaGlsZSBTUDUxMDAg ZXJyYXR1bSAyOCByZXF1aXJlcyBCSU9TZXMgdG8gZGlzYWJsZSB0aGlzIG1v ZGUsCnNvbWUgbWF5IHN0aWxsIHVzZSBpdC4KClRoaXMgcGF0Y2ggY2hlY2tz IHdoZXRoZXIgdGhpcyBtb2RlIGlzIG9uIGFuZCwgaWYgcGVyLWRldmljZQp0 YWJsZSBpcyBpbiB1c2UsIGRpc2FibGVzIElPTU1VLgoKQU1ELElPTU1VOiBN YWtlIHBlci1kZXZpY2UgaW50ZXJydXB0IHJlbWFwcGluZyB0YWJsZSBkZWZh dWx0CgpVc2luZyBnbG9iYWwgaW50ZXJydXB0IHJlbWFwcGluZyB0YWJsZSBt YXkgYmUgaW5zZWN1cmUsIGFzCmRlc2NyaWJlZCBieSBYU0EtMzYuIFRoaXMg cGF0Y2ggbWFrZXMgcGVyLWRldmljZSBtb2RlIGRlZmF1bHQuCgpUaGlzIGlz IFhTQS0zNiAvIENWRS0yMDEzLTAxNTMuCgpTaWduZWQtb2ZmLWJ5OiBKYW4g QmV1bGljaCA8amJldWxpY2hAc3VzZS5jb20+ClNpZ25lZC1vZmYtYnk6IEJv cmlzIE9zdHJvdnNreSA8Ym9yaXMub3N0cm92c2t5QGFtZC5jb20+CgotLS0g YS94ZW4vYXJjaC94ODYvaXJxLmMKKysrIGIveGVuL2FyY2gveDg2L2lycS5j CkBAIC0xNjc3LDkgKzE2NzcsNiBAQCBpbnQgbWFwX2RvbWFpbl9waXJxKAog ICAgICAgICBkLT5hcmNoLnBpcnFfaXJxW3BpcnFdID0gaXJxOwogICAgICAg ICBkLT5hcmNoLmlycV9waXJxW2lycV0gPSBwaXJxOwogICAgICAgICBzcGlu X3VubG9ja19pcnFyZXN0b3JlKCZkZXNjLT5sb2NrLCBmbGFncyk7Ci0KLSAg ICAgICAgaWYgKCBvcHRfaXJxX3ZlY3Rvcl9tYXAgPT0gT1BUX0lSUV9WRUNU T1JfTUFQX1BFUkRFViApCi0gICAgICAgICAgICBwcmludGsoWEVOTE9HX0lO Rk8gIlBlci1kZXZpY2UgdmVjdG9yIG1hcHMgZm9yIEdTSXMgbm90IGltcGxl bWVudGVkIHlldC5cbiIpOwogICAgIH0KIAogZG9uZToKLS0tIGEveGVuL2Ry aXZlcnMvYWNwaS90YWJsZXMuYworKysgYi94ZW4vZHJpdmVycy9hY3BpL3Rh Ymxlcy5jCkBAIC0yNjcsNyArMjY3LDcgQEAgYWNwaV90YWJsZV9wYXJzZV9t YWR0KGVudW0gYWNwaV9tYWR0X3R5cAogICogQGhhbmRsZXI6IGhhbmRsZXIg dG8gcnVuCiAgKgogICogU2NhbiB0aGUgQUNQSSBTeXN0ZW0gRGVzY3JpcHRv ciBUYWJsZSAoU1REKSBmb3IgYSB0YWJsZSBtYXRjaGluZyBAaWQsCi0gKiBy dW4gQGhhbmRsZXIgb24gaXQuICBSZXR1cm4gMCBpZiB0YWJsZSBmb3VuZCwg cmV0dXJuIG9uIGlmIG5vdC4KKyAqIHJ1biBAaGFuZGxlciBvbiBpdC4KICAq LwogaW50IGFjcGlfdGFibGVfcGFyc2UoY2hhciAqaWQsIGFjcGlfdGFibGVf aGFuZGxlciBoYW5kbGVyKQogewpAQCAtMjgyLDggKzI4Miw3IEBAIGludCBh Y3BpX3RhYmxlX3BhcnNlKGNoYXIgKmlkLCBhY3BpX3RhYmwKIAkJYWNwaV9n ZXRfdGFibGUoaWQsIDAsICZ0YWJsZSk7CiAKIAlpZiAodGFibGUpIHsKLQkJ aGFuZGxlcih0YWJsZSk7Ci0JCXJldHVybiAwOworCQlyZXR1cm4gaGFuZGxl cih0YWJsZSk7CiAJfSBlbHNlCiAJCXJldHVybiAxOwogfQotLS0gYS94ZW4v ZHJpdmVycy9wYXNzdGhyb3VnaC9hbWQvaW9tbXVfYWNwaS5jCisrKyBiL3hl bi9kcml2ZXJzL3Bhc3N0aHJvdWdoL2FtZC9pb21tdV9hY3BpLmMKQEAgLTIx LDYgKzIxLDcgQEAKICNpbmNsdWRlIDx4ZW4vY29uZmlnLmg+CiAjaW5jbHVk ZSA8eGVuL2Vycm5vLmg+CiAjaW5jbHVkZSA8YXNtL2FwaWNkZWYuaD4KKyNp bmNsdWRlIDxhc20vaW9fYXBpYy5oPgogI2luY2x1ZGUgPGFzbS9hbWQtaW9t bXUuaD4KICNpbmNsdWRlIDxhc20vaHZtL3N2bS9hbWQtaW9tbXUtcHJvdG8u aD4KICNpbmNsdWRlIDxhc20vaHZtL3N2bS9hbWQtaW9tbXUtYWNwaS5oPgpA QCAtMjksNyArMzAsNiBAQCBleHRlcm4gdW5zaWduZWQgbG9uZyBhbWRfaW9t bXVfcGFnZV9lbnRyCiBleHRlcm4gdW5zaWduZWQgc2hvcnQgaXZyc19iZGZf ZW50cmllczsKIGV4dGVybiBzdHJ1Y3QgaXZyc19tYXBwaW5ncyAqaXZyc19t YXBwaW5nczsKIGV4dGVybiB1bnNpZ25lZCBzaG9ydCBsYXN0X2JkZjsKLWV4 dGVybiBpbnQgaW9hcGljX2JkZltNQVhfSU9fQVBJQ1NdOwogZXh0ZXJuIHZv aWQgKnNoYXJlZF9pbnRyZW1hcF90YWJsZTsKIAogc3RhdGljIHZvaWQgYWRk X2l2cnNfbWFwcGluZ19lbnRyeSgKQEAgLTYzNiw2ICs2MzYsNyBAQCBzdGF0 aWMgdTE2IF9faW5pdCBwYXJzZV9pdmhkX2RldmljZV9zcGVjCiAgICAgdTE2 IGhlYWRlcl9sZW5ndGgsIHUxNiBibG9ja19sZW5ndGgsIHN0cnVjdCBhbWRf aW9tbXUgKmlvbW11KQogewogICAgIHUxNiBkZXZfbGVuZ3RoLCBiZGY7Cisg ICAgaW50IGFwaWM7CiAKICAgICBkZXZfbGVuZ3RoID0gc2l6ZW9mKHN0cnVj dCBhY3BpX2l2aGRfZGV2aWNlX3NwZWNpYWwpOwogICAgIGlmICggaGVhZGVy X2xlbmd0aCA8IChibG9ja19sZW5ndGggKyBkZXZfbGVuZ3RoKSApCkBAIC02 NTIsOSArNjUzLDU4IEBAIHN0YXRpYyB1MTYgX19pbml0IHBhcnNlX2l2aGRf ZGV2aWNlX3NwZWMKICAgICB9CiAKICAgICBhZGRfaXZyc19tYXBwaW5nX2Vu dHJ5KGJkZiwgYmRmLCBpdmhkX2RldmljZS0+aGVhZGVyLmZsYWdzLCBpb21t dSk7Ci0gICAgLyogc2V0IGRldmljZSBpZCBvZiBpb2FwaWMgKi8KLSAgICBp b2FwaWNfYmRmW2l2aGRfZGV2aWNlLT5zcGVjaWFsLmhhbmRsZV0gPSBiZGY7 Ci0gICAgcmV0dXJuIGRldl9sZW5ndGg7CisKKyAgICBpZiAoIGl2aGRfZGV2 aWNlLT5zcGVjaWFsLnZhcmlldHkgIT0gMSAvKiBBQ1BJX0lWSERfSU9BUElD ICovICkKKyAgICB7CisgICAgICAgIGlmICggaXZoZF9kZXZpY2UtPnNwZWNp YWwudmFyaWV0eSAhPSAyIC8qIEFDUElfSVZIRF9IUEVUICovICkKKyAgICAg ICAgICAgIHByaW50ayhYRU5MT0dfRVJSICJVbnJlY29nbml6ZWQgSVZIRCBz cGVjaWFsIHZhcmlldHkgJSN4XG4iLAorICAgICAgICAgICAgICAgICAgIGl2 aGRfZGV2aWNlLT5zcGVjaWFsLnZhcmlldHkpOworICAgICAgICByZXR1cm4g ZGV2X2xlbmd0aDsKKyAgICB9CisKKyAgICAvKgorICAgICAqIFNvbWUgQklP U2VzIGhhdmUgSU9BUElDIGJyb2tlbiBlbnRyaWVzIHNvIHdlIGNoZWNrIGZv ciBJVlJTCisgICAgICogY29uc2lzdGVuY3kgaGVyZSAtLS0gd2hldGhlciBl bnRyeSdzIElPQVBJQyBJRCBpcyB2YWxpZCBhbmQKKyAgICAgKiB3aGV0aGVy IHRoZXJlIGFyZSBjb25mbGljdGluZy9kdXBsaWNhdGVkIGVudHJpZXMuCisg ICAgICovCisgICAgZm9yICggYXBpYyA9IDA7IGFwaWMgPCBucl9pb2FwaWNz OyBhcGljKysgKQorICAgIHsKKyAgICAgICAgaWYgKCBJT19BUElDX0lEKGFw aWMpICE9IGl2aGRfZGV2aWNlLT5zcGVjaWFsLmhhbmRsZSApCisgICAgICAg ICAgICBjb250aW51ZTsKKworICAgICAgICBpZiAoIGlvYXBpY19iZGZbaXZo ZF9kZXZpY2UtPnNwZWNpYWwuaGFuZGxlXS5waW5fc2V0dXAgKQorICAgICAg ICB7CisgICAgICAgICAgICBpZiAoIGlvYXBpY19iZGZbaXZoZF9kZXZpY2Ut PnNwZWNpYWwuaGFuZGxlXS5iZGYgPT0gYmRmICkKKyAgICAgICAgICAgICAg ICBBTURfSU9NTVVfREVCVUcoIklWSEQgV2FybmluZzogRHVwbGljYXRlIElP LUFQSUMgJSN4IGVudHJpZXNcbiIsCisgICAgICAgICAgICAgICAgICAgICAg ICAgICAgICAgIGl2aGRfZGV2aWNlLT5zcGVjaWFsLmhhbmRsZSk7CisgICAg ICAgICAgICBlbHNlCisgICAgICAgICAgICB7CisgICAgICAgICAgICAgICAg cHJpbnRrKFhFTkxPR19FUlIgIklWSEQgRXJyb3I6IENvbmZsaWN0aW5nIElP LUFQSUMgJSN4IGVudHJpZXNcbiIsCisgICAgICAgICAgICAgICAgICAgICAg IGl2aGRfZGV2aWNlLT5zcGVjaWFsLmhhbmRsZSk7CisgICAgICAgICAgICAg ICAgaWYgKCBhbWRfaW9tbXVfcGVyZGV2X2ludHJlbWFwICkKKyAgICAgICAg ICAgICAgICAgICAgcmV0dXJuIDA7CisgICAgICAgICAgICB9CisgICAgICAg IH0KKyAgICAgICAgZWxzZQorICAgICAgICB7CisgICAgICAgICAgICAvKiBz ZXQgZGV2aWNlIGlkIG9mIGlvYXBpYyAqLworICAgICAgICAgICAgaW9hcGlj X2JkZltpdmhkX2RldmljZS0+c3BlY2lhbC5oYW5kbGVdLmJkZiA9IGJkZjsK KworICAgICAgICAgICAgaW9hcGljX2JkZltpdmhkX2RldmljZS0+c3BlY2lh bC5oYW5kbGVdLnBpbl9zZXR1cCA9IHh6YWxsb2NfYXJyYXkoCisgICAgICAg ICAgICAgICAgdW5zaWduZWQgbG9uZywgQklUU19UT19MT05HUyhucl9pb2Fw aWNfcmVnaXN0ZXJzW2FwaWNdKSk7CisgICAgICAgICAgICBpZiAoIG5yX2lv YXBpY19yZWdpc3RlcnNbYXBpY10gJiYKKyAgICAgICAgICAgICAgICAgIWlv YXBpY19iZGZbSU9fQVBJQ19JRChhcGljKV0ucGluX3NldHVwICkKKyAgICAg ICAgICAgIHsKKyAgICAgICAgICAgICAgICBwcmludGsoWEVOTE9HX0VSUiAi SVZIRCBFcnJvcjogT3V0IG9mIG1lbW9yeVxuIik7CisgICAgICAgICAgICAg ICAgcmV0dXJuIDA7CisgICAgICAgICAgICB9CisgICAgICAgIH0KKyAgICAg ICAgcmV0dXJuIGRldl9sZW5ndGg7CisgICAgfQorCisgICAgcHJpbnRrKFhF TkxPR19FUlIgIklWSEQgRXJyb3I6IEludmFsaWQgSU8tQVBJQyAlI3hcbiIs CisgICAgICAgICAgIGl2aGRfZGV2aWNlLT5zcGVjaWFsLmhhbmRsZSk7Cisg ICAgcmV0dXJuIDA7CiB9CiAKIHN0YXRpYyBpbnQgX19pbml0IHBhcnNlX2l2 aGRfYmxvY2soc3RydWN0IGFjcGlfaXZoZF9ibG9ja19oZWFkZXIgKml2aGRf YmxvY2spCi0tLSBhL3hlbi9kcml2ZXJzL3Bhc3N0aHJvdWdoL2FtZC9pb21t dV9pbml0LmMKKysrIGIveGVuL2RyaXZlcnMvcGFzc3Rocm91Z2gvYW1kL2lv bW11X2luaXQuYwpAQCAtODk3LDEyICs4OTcsNDUgQEAgc3RhdGljIGludCBf X2luaXQgYW1kX2lvbW11X3NldHVwX2RldmljZQogICAgIHJldHVybiAwOwog fQogCisvKiBDaGVjayB3aGV0aGVyIFNQNTEwMCBTQVRBIENvbWJpbmVkIG1v ZGUgaXMgb24gKi8KK3N0YXRpYyBib29sX3QgX19pbml0IGFtZF9zcDUxMDBf ZXJyYXR1bTI4KHZvaWQpCit7CisgICAgdTMyIGJ1cywgaWQ7CisgICAgdTE2 IHZlbmRvcl9pZCwgZGV2X2lkOworICAgIHU4IGJ5dGU7CisKKyAgICBmb3Ig KGJ1cyA9IDA7IGJ1cyA8IDI1NjsgYnVzKyspCisgICAgeworICAgICAgICBp ZCA9IHBjaV9jb25mX3JlYWQzMihidXMsIDB4MTQsIDAsIFBDSV9WRU5ET1Jf SUQpOworCisgICAgICAgIHZlbmRvcl9pZCA9IGlkICYgMHhmZmZmOworICAg ICAgICBkZXZfaWQgPSAoaWQgPj4gMTYpICYgMHhmZmZmOworCisgICAgICAg IC8qIFNQNTEwMCBTTUJ1cyBtb2R1bGUgc2V0cyBDb21iaW5lZCBtb2RlIG9u ICovCisgICAgICAgIGlmICh2ZW5kb3JfaWQgIT0gMHgxMDAyIHx8IGRldl9p ZCAhPSAweDQzODUpCisgICAgICAgICAgICBjb250aW51ZTsKKworICAgICAg ICBieXRlID0gcGNpX2NvbmZfcmVhZDgoYnVzLCAweDE0LCAwLCAweGFkKTsK KyAgICAgICAgaWYgKCAoYnl0ZSA+PiAzKSAmIDEgKQorICAgICAgICB7Cisg ICAgICAgICAgICBwcmludGsoWEVOTE9HX1dBUk5JTkcgIkFNRC1WaTogU1A1 MTAwIGVycmF0dW0gMjggZGV0ZWN0ZWQsIGRpc2FibGluZyBJT01NVS5cbiIK KyAgICAgICAgICAgICAgICAgICAiSWYgcG9zc2libGUsIGRpc2FibGUgU0FU QSBDb21iaW5lZCBtb2RlIGluIEJJT1Mgb3IgY29udGFjdCB5b3VyIHZlbmRv ciBmb3IgQklPUyB1cGRhdGUuXG4iKTsKKyAgICAgICAgICAgIHJldHVybiAx OworICAgICAgICB9CisgICAgfQorCisgICAgcmV0dXJuIDA7Cit9CisKIGlu dCBfX2luaXQgYW1kX2lvbW11X2luaXQodm9pZCkKIHsKICAgICBzdHJ1Y3Qg YW1kX2lvbW11ICppb21tdTsKIAogICAgIEJVR19PTiggIWlvbW11X2ZvdW5k KCkgKTsKIAorICAgIGlmICggYW1kX2lvbW11X3BlcmRldl9pbnRyZW1hcCAm JiBhbWRfc3A1MTAwX2VycmF0dW0yOCgpICkKKyAgICAgICAgZ290byBlcnJv cl9vdXQ7CisKICAgICBpcnFfdG9faW9tbXUgPSB4bWFsbG9jX2FycmF5KHN0 cnVjdCBhbWRfaW9tbXUgKiwgbnJfaXJxcyk7CiAgICAgaWYgKCBpcnFfdG9f aW9tbXUgPT0gTlVMTCApCiAgICAgICAgIGdvdG8gZXJyb3Jfb3V0OwotLS0g YS94ZW4vZHJpdmVycy9wYXNzdGhyb3VnaC9hbWQvaW9tbXVfaW50ci5jCisr KyBiL3hlbi9kcml2ZXJzL3Bhc3N0aHJvdWdoL2FtZC9pb21tdV9pbnRyLmMK QEAgLTI3LDcgKzI3LDcgQEAKICNkZWZpbmUgSU5UUkVNQVBfTEVOR1RIIDB4 QgogI2RlZmluZSBJTlRSRU1BUF9FTlRSSUVTICgxIDw8IElOVFJFTUFQX0xF TkdUSCkKIAotaW50IGlvYXBpY19iZGZbTUFYX0lPX0FQSUNTXTsKK3N0cnVj dCBpb2FwaWNfYmRmIGlvYXBpY19iZGZbTUFYX0lPX0FQSUNTXTsKIGV4dGVy biBzdHJ1Y3QgaXZyc19tYXBwaW5ncyAqaXZyc19tYXBwaW5nczsKIGV4dGVy biB1bnNpZ25lZCBzaG9ydCBpdnJzX2JkZl9lbnRyaWVzOwogdm9pZCAqc2hh cmVkX2ludHJlbWFwX3RhYmxlOwpAQCAtMTE3LDEyICsxMTcsMTIgQEAgdm9p ZCBpbnZhbGlkYXRlX2ludGVycnVwdF90YWJsZShzdHJ1Y3QgYQogc3RhdGlj IHZvaWQgdXBkYXRlX2ludHJlbWFwX2VudHJ5X2Zyb21faW9hcGljKAogICAg IGludCBiZGYsCiAgICAgc3RydWN0IGFtZF9pb21tdSAqaW9tbXUsCi0gICAg c3RydWN0IElPX0FQSUNfcm91dGVfZW50cnkgKmlvYXBpY19ydGUpCisgICAg Y29uc3Qgc3RydWN0IElPX0FQSUNfcm91dGVfZW50cnkgKnJ0ZSwKKyAgICBj b25zdCBzdHJ1Y3QgSU9fQVBJQ19yb3V0ZV9lbnRyeSAqb2xkX3J0ZSkKIHsK ICAgICB1bnNpZ25lZCBsb25nIGZsYWdzOwogICAgIHUzMiogZW50cnk7CiAg ICAgdTggZGVsaXZlcnlfbW9kZSwgZGVzdCwgdmVjdG9yLCBkZXN0X21vZGU7 Ci0gICAgc3RydWN0IElPX0FQSUNfcm91dGVfZW50cnkgKnJ0ZSA9IGlvYXBp Y19ydGU7CiAgICAgaW50IHJlcV9pZDsKICAgICBzcGlubG9ja190ICpsb2Nr OwogICAgIGludCBvZmZzZXQ7CkBAIC0xMzgsNiArMTM4LDE0IEBAIHN0YXRp YyB2b2lkIHVwZGF0ZV9pbnRyZW1hcF9lbnRyeV9mcm9tX2kKICAgICBzcGlu X2xvY2tfaXJxc2F2ZShsb2NrLCBmbGFncyk7CiAKICAgICBvZmZzZXQgPSBn ZXRfaW50cmVtYXBfb2Zmc2V0KHZlY3RvciwgZGVsaXZlcnlfbW9kZSk7Cisg ICAgaWYgKCBvbGRfcnRlICkKKyAgICB7CisgICAgICAgIGludCBvbGRfb2Zm c2V0ID0gZ2V0X2ludHJlbWFwX29mZnNldChvbGRfcnRlLT52ZWN0b3IsCisg ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICBv bGRfcnRlLT5kZWxpdmVyeV9tb2RlKTsKKworICAgICAgICBpZiAoIG9mZnNl dCAhPSBvbGRfb2Zmc2V0ICkKKyAgICAgICAgICAgIGZyZWVfaW50cmVtYXBf ZW50cnkoYmRmLCBvbGRfb2Zmc2V0KTsKKyAgICB9CiAgICAgZW50cnkgPSAo dTMyKilnZXRfaW50cmVtYXBfZW50cnkocmVxX2lkLCBvZmZzZXQpOwogICAg IHVwZGF0ZV9pbnRyZW1hcF9lbnRyeShlbnRyeSwgdmVjdG9yLCBkZWxpdmVy eV9tb2RlLCBkZXN0X21vZGUsIGRlc3QpOwogCkBAIC0xNzYsNyArMTg0LDcg QEAgaW50IF9faW5pdCBhbWRfaW9tbXVfc2V0dXBfaW9hcGljX3JlbWFwcAog ICAgICAgICAgICAgICAgIGNvbnRpbnVlOwogCiAgICAgICAgICAgICAvKiBn ZXQgZGV2aWNlIGlkIG9mIGlvYXBpYyBkZXZpY2VzICovCi0gICAgICAgICAg ICBiZGYgPSBpb2FwaWNfYmRmW0lPX0FQSUNfSUQoYXBpYyldOworICAgICAg ICAgICAgYmRmID0gaW9hcGljX2JkZltJT19BUElDX0lEKGFwaWMpXS5iZGY7 CiAgICAgICAgICAgICBpb21tdSA9IGZpbmRfaW9tbXVfZm9yX2RldmljZShi ZGYpOwogICAgICAgICAgICAgaWYgKCAhaW9tbXUgKQogICAgICAgICAgICAg ewpAQCAtMjA3LDYgKzIxNSw3IEBAIGludCBfX2luaXQgYW1kX2lvbW11X3Nl dHVwX2lvYXBpY19yZW1hcHAKICAgICAgICAgICAgICAgICBmbHVzaF9jb21t YW5kX2J1ZmZlcihpb21tdSk7CiAgICAgICAgICAgICAgICAgc3Bpbl91bmxv Y2tfaXJxcmVzdG9yZSgmaW9tbXUtPmxvY2ssIGZsYWdzKTsKICAgICAgICAg ICAgIH0KKyAgICAgICAgICAgIHNldF9iaXQocGluLCBpb2FwaWNfYmRmW0lP X0FQSUNfSUQoYXBpYyldLnBpbl9zZXR1cCk7CiAgICAgICAgIH0KICAgICB9 CiAgICAgcmV0dXJuIDA7CkBAIC0yMTgsNiArMjI3LDcgQEAgdm9pZCBhbWRf aW9tbXVfaW9hcGljX3VwZGF0ZV9pcmUoCiAgICAgc3RydWN0IElPX0FQSUNf cm91dGVfZW50cnkgb2xkX3J0ZSA9IHsgMCB9OwogICAgIHN0cnVjdCBJT19B UElDX3JvdXRlX2VudHJ5IG5ld19ydGUgPSB7IDAgfTsKICAgICB1bnNpZ25l ZCBpbnQgcnRlX2xvID0gKHJlZyAmIDEpID8gcmVnIC0gMSA6IHJlZzsKKyAg ICB1bnNpZ25lZCBpbnQgcGluID0gKHJlZyAtIDB4MTApIC8gMjsKICAgICBp bnQgc2F2ZWRfbWFzaywgYmRmOwogICAgIHN0cnVjdCBhbWRfaW9tbXUgKmlv bW11OwogCkBAIC0yMjgsNyArMjM4LDcgQEAgdm9pZCBhbWRfaW9tbXVfaW9h cGljX3VwZGF0ZV9pcmUoCiAgICAgfQogCiAgICAgLyogZ2V0IGRldmljZSBp ZCBvZiBpb2FwaWMgZGV2aWNlcyAqLwotICAgIGJkZiA9IGlvYXBpY19iZGZb SU9fQVBJQ19JRChhcGljKV07CisgICAgYmRmID0gaW9hcGljX2JkZltJT19B UElDX0lEKGFwaWMpXS5iZGY7CiAgICAgaW9tbXUgPSBmaW5kX2lvbW11X2Zv cl9kZXZpY2UoYmRmKTsKICAgICBpZiAoICFpb21tdSApCiAgICAgewpAQCAt MjU0LDYgKzI2NCwxNCBAQCB2b2lkIGFtZF9pb21tdV9pb2FwaWNfdXBkYXRl X2lyZSgKICAgICAgICAgKigoKHUzMiAqKSZuZXdfcnRlKSArIDEpID0gdmFs dWU7CiAgICAgfQogCisgICAgaWYgKCBuZXdfcnRlLm1hc2sgJiYKKyAgICAg ICAgICF0ZXN0X2JpdChwaW4sIGlvYXBpY19iZGZbSU9fQVBJQ19JRChhcGlj KV0ucGluX3NldHVwKSApCisgICAgeworICAgICAgICBBU1NFUlQoc2F2ZWRf bWFzayk7CisgICAgICAgIF9faW9fYXBpY193cml0ZShhcGljLCByZWcsIHZh bHVlKTsKKyAgICAgICAgcmV0dXJuOworICAgIH0KKwogICAgIC8qIG1hc2sg dGhlIGludGVycnVwdCB3aGlsZSB3ZSBjaGFuZ2UgdGhlIGludHJlbWFwIHRh YmxlICovCiAgICAgaWYgKCAhc2F2ZWRfbWFzayApCiAgICAgewpAQCAtMjYy LDcgKzI4MCwxMSBAQCB2b2lkIGFtZF9pb21tdV9pb2FwaWNfdXBkYXRlX2ly ZSgKICAgICB9CiAKICAgICAvKiBVcGRhdGUgaW50ZXJydXB0IHJlbWFwcGlu ZyBlbnRyeSAqLwotICAgIHVwZGF0ZV9pbnRyZW1hcF9lbnRyeV9mcm9tX2lv YXBpYyhiZGYsIGlvbW11LCAmbmV3X3J0ZSk7CisgICAgdXBkYXRlX2ludHJl bWFwX2VudHJ5X2Zyb21faW9hcGljKAorICAgICAgICBiZGYsIGlvbW11LCAm bmV3X3J0ZSwKKyAgICAgICAgdGVzdF9hbmRfc2V0X2JpdChwaW4sCisgICAg ICAgICAgICAgICAgICAgICAgICAgaW9hcGljX2JkZltJT19BUElDX0lEKGFw aWMpXS5waW5fc2V0dXApID8gJm9sZF9ydGUKKyAgICAgICAgICAgICAgICAg ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg ICAgOiBOVUxMKTsKIAogICAgIC8qIEZvcndhcmQgd3JpdGUgYWNjZXNzIHRv IElPLUFQSUMgUlRFICovCiAgICAgX19pb19hcGljX3dyaXRlKGFwaWMsIHJl ZywgdmFsdWUpOwpAQCAtMzczLDYgKzM5NSwxMiBAQCB2b2lkIGFtZF9pb21t dV9tc2lfbXNnX3VwZGF0ZV9pcmUoCiAgICAgICAgIHJldHVybjsKICAgICB9 CiAKKyAgICBpZiAoIG1zaV9kZXNjLT5yZW1hcF9pbmRleCA+PSAwICkKKyAg ICAgICAgdXBkYXRlX2ludHJlbWFwX2VudHJ5X2Zyb21fbXNpX21zZyhpb21t dSwgcGRldiwgbXNpX2Rlc2MsIE5VTEwpOworCisgICAgaWYgKCAhbXNnICkK KyAgICAgICAgcmV0dXJuOworCiAgICAgdXBkYXRlX2ludHJlbWFwX2VudHJ5 X2Zyb21fbXNpX21zZyhpb21tdSwgcGRldiwgbXNpX2Rlc2MsIG1zZyk7CiB9 CiAKLS0tIGEveGVuL2RyaXZlcnMvcGFzc3Rocm91Z2gvYW1kL3BjaV9hbWRf aW9tbXUuYworKysgYi94ZW4vZHJpdmVycy9wYXNzdGhyb3VnaC9hbWQvcGNp X2FtZF9pb21tdS5jCkBAIC0xOTUsNiArMTk1LDggQEAgaW50IF9faW5pdCBh bWRfaW92X2RldGVjdCh2b2lkKQogICAgIHsKICAgICAgICAgcHJpbnRrKCJB TUQtVmk6IE5vdCBvdmVycmlkaW5nIGlycV92ZWN0b3JfbWFwIHNldHRpbmdc biIpOwogICAgIH0KKyAgICBpZiAoICFhbWRfaW9tbXVfcGVyZGV2X2ludHJl bWFwICkKKyAgICAgICAgcHJpbnRrKFhFTkxPR19XQVJOSU5HICJBTUQtVmk6 IFVzaW5nIGdsb2JhbCBpbnRlcnJ1cHQgcmVtYXAgdGFibGUgaXMgbm90IHJl Y29tbWVuZGVkIChzZWUgWFNBLTM2KSFcbiIpOwogICAgIHJldHVybiBzY2Fu X3BjaV9kZXZpY2VzKCk7CiB9CiAKLS0tIGEveGVuL2RyaXZlcnMvcGFzc3Ro cm91Z2gvaW9tbXUuYworKysgYi94ZW4vZHJpdmVycy9wYXNzdGhyb3VnaC9p b21tdS5jCkBAIC00OSw3ICs0OSw3IEBAIGJvb2xfdCBfX3JlYWRfbW9zdGx5 IGlvbW11X3FpbnZhbCA9IDE7CiBib29sX3QgX19yZWFkX21vc3RseSBpb21t dV9pbnRyZW1hcCA9IDE7CiBib29sX3QgX19yZWFkX21vc3RseSBpb21tdV9o YXBfcHRfc2hhcmU7CiBib29sX3QgX19yZWFkX21vc3RseSBhbWRfaW9tbXVf ZGVidWc7Ci1ib29sX3QgX19yZWFkX21vc3RseSBhbWRfaW9tbXVfcGVyZGV2 X2ludHJlbWFwOworYm9vbF90IF9fcmVhZF9tb3N0bHkgYW1kX2lvbW11X3Bl cmRldl9pbnRyZW1hcCA9IDE7CiAKIHN0YXRpYyB2b2lkIF9faW5pdCBwYXJz ZV9pb21tdV9wYXJhbShjaGFyICpzKQogewpAQCAtNzgsNiArNzgsOCBAQCBz dGF0aWMgdm9pZCBfX2luaXQgcGFyc2VfaW9tbXVfcGFyYW0oY2hhCiAgICAg ICAgICAgICBhbWRfaW9tbXVfZGVidWcgPSAxOwogICAgICAgICBlbHNlIGlm ICggIXN0cmNtcChzLCAiYW1kLWlvbW11LXBlcmRldi1pbnRyZW1hcCIpICkK ICAgICAgICAgICAgIGFtZF9pb21tdV9wZXJkZXZfaW50cmVtYXAgPSAxOwor ICAgICAgICBlbHNlIGlmICggIXN0cmNtcChzLCAiYW1kLWlvbW11LWdsb2Jh bC1pbnRyZW1hcCIpICkKKyAgICAgICAgICAgIGFtZF9pb21tdV9wZXJkZXZf aW50cmVtYXAgPSAwOwogICAgICAgICBlbHNlIGlmICggIXN0cmNtcChzLCAi ZG9tMC1wYXNzdGhyb3VnaCIpICkKICAgICAgICAgICAgIGlvbW11X3Bhc3N0 aHJvdWdoID0gMTsKICAgICAgICAgZWxzZSBpZiAoICFzdHJjbXAocywgImRv bTAtc3RyaWN0IikgKQotLS0gYS94ZW4vaW5jbHVkZS9hc20teDg2L2h2bS9z dm0vYW1kLWlvbW11LXByb3RvLmgKKysrIGIveGVuL2luY2x1ZGUvYXNtLXg4 Ni9odm0vc3ZtL2FtZC1pb21tdS1wcm90by5oCkBAIC04OCw2ICs4OCwxMSBA QCB2b2lkIGFtZF9pb21tdV9yZWFkX21zaV9mcm9tX2lyZSgKIHVuc2lnbmVk IGludCBhbWRfaW9tbXVfcmVhZF9pb2FwaWNfZnJvbV9pcmUoCiAgICAgdW5z aWduZWQgaW50IGFwaWMsIHVuc2lnbmVkIGludCByZWcpOwogCitleHRlcm4g c3RydWN0IGlvYXBpY19iZGYgeworICAgIHUxNiBiZGY7CisgICAgdW5zaWdu ZWQgbG9uZyAqcGluX3NldHVwOworfSBpb2FwaWNfYmRmW107CisKIC8qIHBv d2VyIG1hbmFnZW1lbnQgc3VwcG9ydCAqLwogdm9pZCBhbWRfaW9tbXVfcmVz dW1lKHZvaWQpOwogdm9pZCBhbWRfaW9tbXVfc3VzcGVuZCh2b2lkKTsK --=separator Content-Type: application/octet-stream; name="xsa36-4.2.patch" Content-Disposition: attachment; filename="xsa36-4.2.patch" Content-Transfer-Encoding: base64 QUNQSTogYWNwaV90YWJsZV9wYXJzZSgpIHNob3VsZCByZXR1cm4gaGFuZGxl cidzIGVycm9yIGNvZGUKCkN1cnJlbnRseSwgdGhlIGVycm9yIGNvZGUgcmV0 dXJuZWQgYnkgYWNwaV90YWJsZV9wYXJzZSgpJ3MgaGFuZGxlcgppcyBpZ25v cmVkLiBUaGlzIHBhdGNoIHdpbGwgcHJvcGFnYXRlIGhhbmRsZXIncyByZXR1 cm4gdmFsdWUgdG8KYWNwaV90YWJsZV9wYXJzZSgpJ3MgY2FsbGVyLgoKQU1E LElPTU1VOiBDbGVhbiB1cCBvbGQgZW50cmllcyBpbiByZW1hcHBpbmcgdGFi bGVzIHdoZW4gY3JlYXRpbmcgbmV3CmludGVycnVwdCBtYXBwaW5nLgoKV2hl biBjaGFuZ2luZyB0aGUgYWZmaW5pdHkgb2YgYW4gSVJRIGFzc29jaWF0ZWQg d2l0aCBhIHBhc3NlZAp0aHJvdWdoIFBDSSBkZXZpY2UsIGNsZWFyIHByZXZp b3VzIG1hcHBpbmcuCgpJbiBhZGRpdGlvbiwgYmVjYXVzZSBzb21lIEJJT1Nl cyBtYXkgaW5jb3JyZWN0bHkgcHJvZ3JhbSBJVlJTCmVudHJpZXMgZm9yIElP QVBJQyB0cnkgdG8gY2hlY2sgZm9yIGVudHJ5J3MgY29uc2lzdGVuY3kuIFNw ZWNpZmljYWxseSwKaWYgY29uZmxpY3RpbmcgZW50cmllcyBhcmUgZm91bmQg ZGlzYWJsZSBJT01NVSBpZiBwZXItZGV2aWNlCnJlbWFwcGluZyB0YWJsZSBp cyB1c2VkLiBJZiBlbnRyaWVzIHJlZmVyIHRvIGJvZ3VzIElPQVBJQyBJRHMK ZGlzYWJsZSBJT01NVSB1bmNvbmRpdGlvbmFsbHkKCkFNRCxJT01NVTogRGlz YWJsZSBJT01NVSBpZiBTQVRBIENvbWJpbmVkIG1vZGUgaXMgb24KCkFNRCdz IFNQNTEwMCBjaGlwc2V0IGNhbiBiZSBwbGFjZWQgaW50byBTQVRBIENvbWJp bmVkIG1vZGUKdGhhdCBtYXkgY2F1c2UgcHJldmVudCBkb20wIGZyb20gYm9v dGluZyB3aGVuIElPTU1VIGlzCmVuYWJsZWQgYW5kIHBlci1kZXZpY2UgaW50 ZXJydXB0IHJlbWFwcGluZyB0YWJsZSBpcyB1c2VkLgpXaGlsZSBTUDUxMDAg ZXJyYXR1bSAyOCByZXF1aXJlcyBCSU9TZXMgdG8gZGlzYWJsZSB0aGlzIG1v ZGUsCnNvbWUgbWF5IHN0aWxsIHVzZSBpdC4KClRoaXMgcGF0Y2ggY2hlY2tz IHdoZXRoZXIgdGhpcyBtb2RlIGlzIG9uIGFuZCwgaWYgcGVyLWRldmljZQp0 YWJsZSBpcyBpbiB1c2UsIGRpc2FibGVzIElPTU1VLgoKQU1ELElPTU1VOiBN YWtlIHBlci1kZXZpY2UgaW50ZXJydXB0IHJlbWFwcGluZyB0YWJsZSBkZWZh dWx0CgpVc2luZyBnbG9iYWwgaW50ZXJydXB0IHJlbWFwcGluZyB0YWJsZSBt YXkgYmUgaW5zZWN1cmUsIGFzCmRlc2NyaWJlZCBieSBYU0EtMzYuIFRoaXMg cGF0Y2ggbWFrZXMgcGVyLWRldmljZSBtb2RlIGRlZmF1bHQuCgpUaGlzIGlz IFhTQS0zNiAvIENWRS0yMDEzLTAxNTMuCgpTaWduZWQtb2ZmLWJ5OiBKYW4g QmV1bGljaCA8amJldWxpY2hAc3VzZS5jb20+ClNpZ25lZC1vZmYtYnk6IEJv cmlzIE9zdHJvdnNreSA8Ym9yaXMub3N0cm92c2t5QGFtZC5jb20+CgotLS0g YS94ZW4vYXJjaC94ODYvaXJxLmMKKysrIGIveGVuL2FyY2gveDg2L2lycS5j CkBAIC0xOTQyLDkgKzE5NDIsNiBAQCBpbnQgbWFwX2RvbWFpbl9waXJxKAog ICAgICAgICBzcGluX2xvY2tfaXJxc2F2ZSgmZGVzYy0+bG9jaywgZmxhZ3Mp OwogICAgICAgICBzZXRfZG9tYWluX2lycV9waXJxKGQsIGlycSwgaW5mbyk7 CiAgICAgICAgIHNwaW5fdW5sb2NrX2lycXJlc3RvcmUoJmRlc2MtPmxvY2ss IGZsYWdzKTsKLQotICAgICAgICBpZiAoIG9wdF9pcnFfdmVjdG9yX21hcCA9 PSBPUFRfSVJRX1ZFQ1RPUl9NQVBfUEVSREVWICkKLSAgICAgICAgICAgIHBy aW50ayhYRU5MT0dfSU5GTyAiUGVyLWRldmljZSB2ZWN0b3IgbWFwcyBmb3Ig R1NJcyBub3QgaW1wbGVtZW50ZWQgeWV0LlxuIik7CiAgICAgfQogCiBkb25l OgotLS0gYS94ZW4vZHJpdmVycy9hY3BpL3RhYmxlcy5jCisrKyBiL3hlbi9k cml2ZXJzL2FjcGkvdGFibGVzLmMKQEAgLTI2Nyw3ICsyNjcsNyBAQCBhY3Bp X3RhYmxlX3BhcnNlX21hZHQoZW51bSBhY3BpX21hZHRfdHlwCiAgKiBAaGFu ZGxlcjogaGFuZGxlciB0byBydW4KICAqCiAgKiBTY2FuIHRoZSBBQ1BJIFN5 c3RlbSBEZXNjcmlwdG9yIFRhYmxlIChTVEQpIGZvciBhIHRhYmxlIG1hdGNo aW5nIEBpZCwKLSAqIHJ1biBAaGFuZGxlciBvbiBpdC4gIFJldHVybiAwIGlm IHRhYmxlIGZvdW5kLCByZXR1cm4gb24gaWYgbm90LgorICogcnVuIEBoYW5k bGVyIG9uIGl0LgogICovCiBpbnQgX19pbml0IGFjcGlfdGFibGVfcGFyc2Uo Y2hhciAqaWQsIGFjcGlfdGFibGVfaGFuZGxlciBoYW5kbGVyKQogewpAQCAt MjgyLDggKzI4Miw3IEBAIGludCBfX2luaXQgYWNwaV90YWJsZV9wYXJzZShj aGFyICppZCwgYWMKIAkJYWNwaV9nZXRfdGFibGUoaWQsIDAsICZ0YWJsZSk7 CiAKIAlpZiAodGFibGUpIHsKLQkJaGFuZGxlcih0YWJsZSk7Ci0JCXJldHVy biAwOworCQlyZXR1cm4gaGFuZGxlcih0YWJsZSk7CiAJfSBlbHNlCiAJCXJl dHVybiAxOwogfQotLS0gYS94ZW4vZHJpdmVycy9wYXNzdGhyb3VnaC9hbWQv aW9tbXVfYWNwaS5jCisrKyBiL3hlbi9kcml2ZXJzL3Bhc3N0aHJvdWdoL2Ft ZC9pb21tdV9hY3BpLmMKQEAgLTIyLDYgKzIyLDcgQEAKICNpbmNsdWRlIDx4 ZW4vZXJybm8uaD4KICNpbmNsdWRlIDx4ZW4vYWNwaS5oPgogI2luY2x1ZGUg PGFzbS9hcGljZGVmLmg+CisjaW5jbHVkZSA8YXNtL2lvX2FwaWMuaD4KICNp bmNsdWRlIDxhc20vYW1kLWlvbW11Lmg+CiAjaW5jbHVkZSA8YXNtL2h2bS9z dm0vYW1kLWlvbW11LXByb3RvLmg+CiAKQEAgLTYzNSw2ICs2MzYsNyBAQCBz dGF0aWMgdTE2IF9faW5pdCBwYXJzZV9pdmhkX2RldmljZV9zcGVjCiAgICAg dTE2IGhlYWRlcl9sZW5ndGgsIHUxNiBibG9ja19sZW5ndGgsIHN0cnVjdCBh bWRfaW9tbXUgKmlvbW11KQogewogICAgIHUxNiBkZXZfbGVuZ3RoLCBiZGY7 CisgICAgaW50IGFwaWM7CiAKICAgICBkZXZfbGVuZ3RoID0gc2l6ZW9mKCpz cGVjaWFsKTsKICAgICBpZiAoIGhlYWRlcl9sZW5ndGggPCAoYmxvY2tfbGVu Z3RoICsgZGV2X2xlbmd0aCkgKQpAQCAtNjUxLDEwICs2NTMsNTkgQEAgc3Rh dGljIHUxNiBfX2luaXQgcGFyc2VfaXZoZF9kZXZpY2Vfc3BlYwogICAgIH0K IAogICAgIGFkZF9pdnJzX21hcHBpbmdfZW50cnkoYmRmLCBiZGYsIHNwZWNp YWwtPmhlYWRlci5kYXRhX3NldHRpbmcsIGlvbW11KTsKLSAgICAvKiBzZXQg ZGV2aWNlIGlkIG9mIGlvYXBpYyAqLwotICAgIGlvYXBpY19zYmRmW3NwZWNp YWwtPmhhbmRsZV0uYmRmID0gYmRmOwotICAgIGlvYXBpY19zYmRmW3NwZWNp YWwtPmhhbmRsZV0uc2VnID0gc2VnOwotICAgIHJldHVybiBkZXZfbGVuZ3Ro OworCisgICAgaWYgKCBzcGVjaWFsLT52YXJpZXR5ICE9IEFDUElfSVZIRF9J T0FQSUMgKQorICAgIHsKKyAgICAgICAgaWYgKCBzcGVjaWFsLT52YXJpZXR5 ICE9IEFDUElfSVZIRF9IUEVUICkKKyAgICAgICAgICAgIHByaW50ayhYRU5M T0dfRVJSICJVbnJlY29nbml6ZWQgSVZIRCBzcGVjaWFsIHZhcmlldHkgJSN4 XG4iLAorICAgICAgICAgICAgICAgICAgIHNwZWNpYWwtPnZhcmlldHkpOwor ICAgICAgICByZXR1cm4gZGV2X2xlbmd0aDsKKyAgICB9CisKKyAgICAvKgor ICAgICAqIFNvbWUgQklPU2VzIGhhdmUgSU9BUElDIGJyb2tlbiBlbnRyaWVz IHNvIHdlIGNoZWNrIGZvciBJVlJTCisgICAgICogY29uc2lzdGVuY3kgaGVy ZSAtLS0gd2hldGhlciBlbnRyeSdzIElPQVBJQyBJRCBpcyB2YWxpZCBhbmQK KyAgICAgKiB3aGV0aGVyIHRoZXJlIGFyZSBjb25mbGljdGluZy9kdXBsaWNh dGVkIGVudHJpZXMuCisgICAgICovCisgICAgZm9yICggYXBpYyA9IDA7IGFw aWMgPCBucl9pb2FwaWNzOyBhcGljKysgKQorICAgIHsKKyAgICAgICAgaWYg KCBJT19BUElDX0lEKGFwaWMpICE9IHNwZWNpYWwtPmhhbmRsZSApCisgICAg ICAgICAgICBjb250aW51ZTsKKworICAgICAgICBpZiAoIGlvYXBpY19zYmRm W3NwZWNpYWwtPmhhbmRsZV0ucGluX3NldHVwICkKKyAgICAgICAgeworICAg ICAgICAgICAgaWYgKCBpb2FwaWNfc2JkZltzcGVjaWFsLT5oYW5kbGVdLmJk ZiA9PSBiZGYgJiYKKyAgICAgICAgICAgICAgICAgaW9hcGljX3NiZGZbc3Bl Y2lhbC0+aGFuZGxlXS5zZWcgPT0gc2VnICkKKyAgICAgICAgICAgICAgICBB TURfSU9NTVVfREVCVUcoIklWSEQgV2FybmluZzogRHVwbGljYXRlIElPLUFQ SUMgJSN4IGVudHJpZXNcbiIsCisgICAgICAgICAgICAgICAgICAgICAgICAg ICAgICAgIHNwZWNpYWwtPmhhbmRsZSk7CisgICAgICAgICAgICBlbHNlCisg ICAgICAgICAgICB7CisgICAgICAgICAgICAgICAgcHJpbnRrKFhFTkxPR19F UlIgIklWSEQgRXJyb3I6IENvbmZsaWN0aW5nIElPLUFQSUMgJSN4IGVudHJp ZXNcbiIsCisgICAgICAgICAgICAgICAgICAgICAgIHNwZWNpYWwtPmhhbmRs ZSk7CisgICAgICAgICAgICAgICAgaWYgKCBhbWRfaW9tbXVfcGVyZGV2X2lu dHJlbWFwICkKKyAgICAgICAgICAgICAgICAgICAgcmV0dXJuIDA7CisgICAg ICAgICAgICB9CisgICAgICAgIH0KKyAgICAgICAgZWxzZQorICAgICAgICB7 CisgICAgICAgICAgICAvKiBzZXQgZGV2aWNlIGlkIG9mIGlvYXBpYyAqLwor ICAgICAgICAgICAgaW9hcGljX3NiZGZbc3BlY2lhbC0+aGFuZGxlXS5iZGYg PSBiZGY7CisgICAgICAgICAgICBpb2FwaWNfc2JkZltzcGVjaWFsLT5oYW5k bGVdLnNlZyA9IHNlZzsKKworICAgICAgICAgICAgaW9hcGljX3NiZGZbc3Bl Y2lhbC0+aGFuZGxlXS5waW5fc2V0dXAgPSB4emFsbG9jX2FycmF5KAorICAg ICAgICAgICAgICAgIHVuc2lnbmVkIGxvbmcsIEJJVFNfVE9fTE9OR1MobnJf aW9hcGljX2VudHJpZXNbYXBpY10pKTsKKyAgICAgICAgICAgIGlmICggbnJf aW9hcGljX2VudHJpZXNbYXBpY10gJiYKKyAgICAgICAgICAgICAgICAgIWlv YXBpY19zYmRmW0lPX0FQSUNfSUQoYXBpYyldLnBpbl9zZXR1cCApCisgICAg ICAgICAgICB7CisgICAgICAgICAgICAgICAgcHJpbnRrKFhFTkxPR19FUlIg IklWSEQgRXJyb3I6IE91dCBvZiBtZW1vcnlcbiIpOworICAgICAgICAgICAg ICAgIHJldHVybiAwOworICAgICAgICAgICAgfQorICAgICAgICB9CisgICAg ICAgIHJldHVybiBkZXZfbGVuZ3RoOworICAgIH0KKworICAgIHByaW50ayhY RU5MT0dfRVJSICJJVkhEIEVycm9yOiBJbnZhbGlkIElPLUFQSUMgJSN4XG4i LCBzcGVjaWFsLT5oYW5kbGUpOworICAgIHJldHVybiAwOwogfQogCiBzdGF0 aWMgaW50IF9faW5pdCBwYXJzZV9pdmhkX2Jsb2NrKGNvbnN0IHN0cnVjdCBh Y3BpX2l2cnNfaGFyZHdhcmUgKml2aGRfYmxvY2spCi0tLSBhL3hlbi9kcml2 ZXJzL3Bhc3N0aHJvdWdoL2FtZC9pb21tdV9pbml0LmMKKysrIGIveGVuL2Ry aXZlcnMvcGFzc3Rocm91Z2gvYW1kL2lvbW11X2luaXQuYwpAQCAtMTEyNiwx MiArMTEyNiw0NSBAQCBzdGF0aWMgaW50IF9faW5pdCBhbWRfaW9tbXVfc2V0 dXBfZGV2aWNlCiAgICAgcmV0dXJuIDA7CiB9CiAKKy8qIENoZWNrIHdoZXRo ZXIgU1A1MTAwIFNBVEEgQ29tYmluZWQgbW9kZSBpcyBvbiAqLworc3RhdGlj IGJvb2xfdCBfX2luaXQgYW1kX3NwNTEwMF9lcnJhdHVtMjgodm9pZCkKK3sK KyAgICB1MzIgYnVzLCBpZDsKKyAgICB1MTYgdmVuZG9yX2lkLCBkZXZfaWQ7 CisgICAgdTggYnl0ZTsKKworICAgIGZvciAoYnVzID0gMDsgYnVzIDwgMjU2 OyBidXMrKykKKyAgICB7CisgICAgICAgIGlkID0gcGNpX2NvbmZfcmVhZDMy KDAsIGJ1cywgMHgxNCwgMCwgUENJX1ZFTkRPUl9JRCk7CisKKyAgICAgICAg dmVuZG9yX2lkID0gaWQgJiAweGZmZmY7CisgICAgICAgIGRldl9pZCA9IChp ZCA+PiAxNikgJiAweGZmZmY7CisKKyAgICAgICAgLyogU1A1MTAwIFNNQnVz IG1vZHVsZSBzZXRzIENvbWJpbmVkIG1vZGUgb24gKi8KKyAgICAgICAgaWYg KHZlbmRvcl9pZCAhPSAweDEwMDIgfHwgZGV2X2lkICE9IDB4NDM4NSkKKyAg ICAgICAgICAgIGNvbnRpbnVlOworCisgICAgICAgIGJ5dGUgPSBwY2lfY29u Zl9yZWFkOCgwLCBidXMsIDB4MTQsIDAsIDB4YWQpOworICAgICAgICBpZiAo IChieXRlID4+IDMpICYgMSApCisgICAgICAgIHsKKyAgICAgICAgICAgIHBy aW50ayhYRU5MT0dfV0FSTklORyAiQU1ELVZpOiBTUDUxMDAgZXJyYXR1bSAy OCBkZXRlY3RlZCwgZGlzYWJsaW5nIElPTU1VLlxuIgorICAgICAgICAgICAg ICAgICAgICJJZiBwb3NzaWJsZSwgZGlzYWJsZSBTQVRBIENvbWJpbmVkIG1v ZGUgaW4gQklPUyBvciBjb250YWN0IHlvdXIgdmVuZG9yIGZvciBCSU9TIHVw ZGF0ZS5cbiIpOworICAgICAgICAgICAgcmV0dXJuIDE7CisgICAgICAgIH0K KyAgICB9CisKKyAgICByZXR1cm4gMDsKK30KKwogaW50IF9faW5pdCBhbWRf aW9tbXVfaW5pdCh2b2lkKQogewogICAgIHN0cnVjdCBhbWRfaW9tbXUgKmlv bW11OwogCiAgICAgQlVHX09OKCAhaW9tbXVfZm91bmQoKSApOwogCisgICAg aWYgKCBhbWRfaW9tbXVfcGVyZGV2X2ludHJlbWFwICYmIGFtZF9zcDUxMDBf ZXJyYXR1bTI4KCkgKQorICAgICAgICBnb3RvIGVycm9yX291dDsKKwogICAg IGl2cnNfYmRmX2VudHJpZXMgPSBhbWRfaW9tbXVfZ2V0X2l2cnNfZGV2X2Vu dHJpZXMoKTsKIAogICAgIGlmICggIWl2cnNfYmRmX2VudHJpZXMgKQotLS0g YS94ZW4vZHJpdmVycy9wYXNzdGhyb3VnaC9hbWQvaW9tbXVfaW50ci5jCisr KyBiL3hlbi9kcml2ZXJzL3Bhc3N0aHJvdWdoL2FtZC9pb21tdV9pbnRyLmMK QEAgLTk5LDEyICs5OSwxMiBAQCBzdGF0aWMgdm9pZCB1cGRhdGVfaW50cmVt YXBfZW50cnkodTMyKiBlCiBzdGF0aWMgdm9pZCB1cGRhdGVfaW50cmVtYXBf ZW50cnlfZnJvbV9pb2FwaWMoCiAgICAgaW50IGJkZiwKICAgICBzdHJ1Y3Qg YW1kX2lvbW11ICppb21tdSwKLSAgICBzdHJ1Y3QgSU9fQVBJQ19yb3V0ZV9l bnRyeSAqaW9hcGljX3J0ZSkKKyAgICBjb25zdCBzdHJ1Y3QgSU9fQVBJQ19y b3V0ZV9lbnRyeSAqcnRlLAorICAgIGNvbnN0IHN0cnVjdCBJT19BUElDX3Jv dXRlX2VudHJ5ICpvbGRfcnRlKQogewogICAgIHVuc2lnbmVkIGxvbmcgZmxh Z3M7CiAgICAgdTMyKiBlbnRyeTsKICAgICB1OCBkZWxpdmVyeV9tb2RlLCBk ZXN0LCB2ZWN0b3IsIGRlc3RfbW9kZTsKLSAgICBzdHJ1Y3QgSU9fQVBJQ19y b3V0ZV9lbnRyeSAqcnRlID0gaW9hcGljX3J0ZTsKICAgICBpbnQgcmVxX2lk OwogICAgIHNwaW5sb2NrX3QgKmxvY2s7CiAgICAgaW50IG9mZnNldDsKQEAg LTEyMCw2ICsxMjAsMTQgQEAgc3RhdGljIHZvaWQgdXBkYXRlX2ludHJlbWFw X2VudHJ5X2Zyb21faQogICAgIHNwaW5fbG9ja19pcnFzYXZlKGxvY2ssIGZs YWdzKTsKIAogICAgIG9mZnNldCA9IGdldF9pbnRyZW1hcF9vZmZzZXQodmVj dG9yLCBkZWxpdmVyeV9tb2RlKTsKKyAgICBpZiAoIG9sZF9ydGUgKQorICAg IHsKKyAgICAgICAgaW50IG9sZF9vZmZzZXQgPSBnZXRfaW50cmVtYXBfb2Zm c2V0KG9sZF9ydGUtPnZlY3RvciwKKyAgICAgICAgICAgICAgICAgICAgICAg ICAgICAgICAgICAgICAgICAgICAgIG9sZF9ydGUtPmRlbGl2ZXJ5X21vZGUp OworCisgICAgICAgIGlmICggb2Zmc2V0ICE9IG9sZF9vZmZzZXQgKQorICAg ICAgICAgICAgZnJlZV9pbnRyZW1hcF9lbnRyeShpb21tdS0+c2VnLCBiZGYs IG9sZF9vZmZzZXQpOworICAgIH0KICAgICBlbnRyeSA9ICh1MzIqKWdldF9p bnRyZW1hcF9lbnRyeShpb21tdS0+c2VnLCByZXFfaWQsIG9mZnNldCk7CiAg ICAgdXBkYXRlX2ludHJlbWFwX2VudHJ5KGVudHJ5LCB2ZWN0b3IsIGRlbGl2 ZXJ5X21vZGUsIGRlc3RfbW9kZSwgZGVzdCk7CiAKQEAgLTE4OCw2ICsxOTYs NyBAQCBpbnQgX19pbml0IGFtZF9pb21tdV9zZXR1cF9pb2FwaWNfcmVtYXBw CiAgICAgICAgICAgICAgICAgYW1kX2lvbW11X2ZsdXNoX2ludHJlbWFwKGlv bW11LCByZXFfaWQpOwogICAgICAgICAgICAgICAgIHNwaW5fdW5sb2NrX2ly cXJlc3RvcmUoJmlvbW11LT5sb2NrLCBmbGFncyk7CiAgICAgICAgICAgICB9 CisgICAgICAgICAgICBzZXRfYml0KHBpbiwgaW9hcGljX3NiZGZbSU9fQVBJ Q19JRChhcGljKV0ucGluX3NldHVwKTsKICAgICAgICAgfQogICAgIH0KICAg ICByZXR1cm4gMDsKQEAgLTE5OSw2ICsyMDgsNyBAQCB2b2lkIGFtZF9pb21t dV9pb2FwaWNfdXBkYXRlX2lyZSgKICAgICBzdHJ1Y3QgSU9fQVBJQ19yb3V0 ZV9lbnRyeSBvbGRfcnRlID0geyAwIH07CiAgICAgc3RydWN0IElPX0FQSUNf cm91dGVfZW50cnkgbmV3X3J0ZSA9IHsgMCB9OwogICAgIHVuc2lnbmVkIGlu dCBydGVfbG8gPSAocmVnICYgMSkgPyByZWcgLSAxIDogcmVnOworICAgIHVu c2lnbmVkIGludCBwaW4gPSAocmVnIC0gMHgxMCkgLyAyOwogICAgIGludCBz YXZlZF9tYXNrLCBzZWcsIGJkZjsKICAgICBzdHJ1Y3QgYW1kX2lvbW11ICpp b21tdTsKIApAQCAtMjM2LDYgKzI0NiwxNCBAQCB2b2lkIGFtZF9pb21tdV9p b2FwaWNfdXBkYXRlX2lyZSgKICAgICAgICAgKigoKHUzMiAqKSZuZXdfcnRl KSArIDEpID0gdmFsdWU7CiAgICAgfQogCisgICAgaWYgKCBuZXdfcnRlLm1h c2sgJiYKKyAgICAgICAgICF0ZXN0X2JpdChwaW4sIGlvYXBpY19zYmRmW0lP X0FQSUNfSUQoYXBpYyldLnBpbl9zZXR1cCkgKQorICAgIHsKKyAgICAgICAg QVNTRVJUKHNhdmVkX21hc2spOworICAgICAgICBfX2lvX2FwaWNfd3JpdGUo YXBpYywgcmVnLCB2YWx1ZSk7CisgICAgICAgIHJldHVybjsKKyAgICB9CisK ICAgICAvKiBtYXNrIHRoZSBpbnRlcnJ1cHQgd2hpbGUgd2UgY2hhbmdlIHRo ZSBpbnRyZW1hcCB0YWJsZSAqLwogICAgIGlmICggIXNhdmVkX21hc2sgKQog ICAgIHsKQEAgLTI0NCw3ICsyNjIsMTEgQEAgdm9pZCBhbWRfaW9tbXVfaW9h cGljX3VwZGF0ZV9pcmUoCiAgICAgfQogCiAgICAgLyogVXBkYXRlIGludGVy cnVwdCByZW1hcHBpbmcgZW50cnkgKi8KLSAgICB1cGRhdGVfaW50cmVtYXBf ZW50cnlfZnJvbV9pb2FwaWMoYmRmLCBpb21tdSwgJm5ld19ydGUpOworICAg IHVwZGF0ZV9pbnRyZW1hcF9lbnRyeV9mcm9tX2lvYXBpYygKKyAgICAgICAg YmRmLCBpb21tdSwgJm5ld19ydGUsCisgICAgICAgIHRlc3RfYW5kX3NldF9i aXQocGluLAorICAgICAgICAgICAgICAgICAgICAgICAgIGlvYXBpY19zYmRm W0lPX0FQSUNfSUQoYXBpYyldLnBpbl9zZXR1cCkgPyAmb2xkX3J0ZQorICAg ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg ICAgICAgICAgICAgICAgICAgOiBOVUxMKTsKIAogICAgIC8qIEZvcndhcmQg d3JpdGUgYWNjZXNzIHRvIElPLUFQSUMgUlRFICovCiAgICAgX19pb19hcGlj X3dyaXRlKGFwaWMsIHJlZywgdmFsdWUpOwpAQCAtMzU0LDYgKzM3NiwxMiBA QCB2b2lkIGFtZF9pb21tdV9tc2lfbXNnX3VwZGF0ZV9pcmUoCiAgICAgICAg IHJldHVybjsKICAgICB9CiAKKyAgICBpZiAoIG1zaV9kZXNjLT5yZW1hcF9p bmRleCA+PSAwICkKKyAgICAgICAgdXBkYXRlX2ludHJlbWFwX2VudHJ5X2Zy b21fbXNpX21zZyhpb21tdSwgcGRldiwgbXNpX2Rlc2MsIE5VTEwpOworCisg ICAgaWYgKCAhbXNnICkKKyAgICAgICAgcmV0dXJuOworCiAgICAgdXBkYXRl X2ludHJlbWFwX2VudHJ5X2Zyb21fbXNpX21zZyhpb21tdSwgcGRldiwgbXNp X2Rlc2MsIG1zZyk7CiB9CiAKLS0tIGEveGVuL2RyaXZlcnMvcGFzc3Rocm91 Z2gvYW1kL3BjaV9hbWRfaW9tbXUuYworKysgYi94ZW4vZHJpdmVycy9wYXNz dGhyb3VnaC9hbWQvcGNpX2FtZF9pb21tdS5jCkBAIC0yMDUsNiArMjA1LDgg QEAgaW50IF9faW5pdCBhbWRfaW92X2RldGVjdCh2b2lkKQogICAgIHsKICAg ICAgICAgcHJpbnRrKCJBTUQtVmk6IE5vdCBvdmVycmlkaW5nIGlycV92ZWN0 b3JfbWFwIHNldHRpbmdcbiIpOwogICAgIH0KKyAgICBpZiAoICFhbWRfaW9t bXVfcGVyZGV2X2ludHJlbWFwICkKKyAgICAgICAgcHJpbnRrKFhFTkxPR19X QVJOSU5HICJBTUQtVmk6IFVzaW5nIGdsb2JhbCBpbnRlcnJ1cHQgcmVtYXAg dGFibGUgaXMgbm90IHJlY29tbWVuZGVkIChzZWUgWFNBLTM2KSFcbiIpOwog ICAgIHJldHVybiBzY2FuX3BjaV9kZXZpY2VzKCk7CiB9CiAKLS0tIGEveGVu L2RyaXZlcnMvcGFzc3Rocm91Z2gvaW9tbXUuYworKysgYi94ZW4vZHJpdmVy cy9wYXNzdGhyb3VnaC9pb21tdS5jCkBAIC01Miw3ICs1Miw3IEBAIGJvb2xf dCBfX3JlYWRfbW9zdGx5IGlvbW11X3FpbnZhbCA9IDE7CiBib29sX3QgX19y ZWFkX21vc3RseSBpb21tdV9pbnRyZW1hcCA9IDE7CiBib29sX3QgX19yZWFk X21vc3RseSBpb21tdV9oYXBfcHRfc2hhcmUgPSAxOwogYm9vbF90IF9fcmVh ZF9tb3N0bHkgaW9tbXVfZGVidWc7Ci1ib29sX3QgX19yZWFkX21vc3RseSBh bWRfaW9tbXVfcGVyZGV2X2ludHJlbWFwOworYm9vbF90IF9fcmVhZF9tb3N0 bHkgYW1kX2lvbW11X3BlcmRldl9pbnRyZW1hcCA9IDE7CiAKIERFRklORV9Q RVJfQ1BVKGJvb2xfdCwgaW9tbXVfZG9udF9mbHVzaF9pb3RsYik7CiAKLS0t IGEveGVuL2luY2x1ZGUvYXNtLXg4Ni9odm0vc3ZtL2FtZC1pb21tdS1wcm90 by5oCisrKyBiL3hlbi9pbmNsdWRlL2FzbS14ODYvaHZtL3N2bS9hbWQtaW9t bXUtcHJvdG8uaApAQCAtMTAwLDYgKzEwMCw3IEBAIHZvaWQgYW1kX2lvbW11 X3JlYWRfbXNpX2Zyb21faXJlKAogCiBleHRlcm4gc3RydWN0IGlvYXBpY19z YmRmIHsKICAgICB1MTYgYmRmLCBzZWc7CisgICAgdW5zaWduZWQgbG9uZyAq cGluX3NldHVwOwogfSBpb2FwaWNfc2JkZltNQVhfSU9fQVBJQ1NdOwogZXh0 ZXJuIHZvaWQgKnNoYXJlZF9pbnRyZW1hcF90YWJsZTsKIAo= --=separator Content-Type: application/octet-stream; name="xsa36-unstable.patch" Content-Disposition: attachment; filename="xsa36-unstable.patch" Content-Transfer-Encoding: base64 QUNQSTogYWNwaV90YWJsZV9wYXJzZSgpIHNob3VsZCByZXR1cm4gaGFuZGxl cidzIGVycm9yIGNvZGUKCkN1cnJlbnRseSwgdGhlIGVycm9yIGNvZGUgcmV0 dXJuZWQgYnkgYWNwaV90YWJsZV9wYXJzZSgpJ3MgaGFuZGxlcgppcyBpZ25v cmVkLiBUaGlzIHBhdGNoIHdpbGwgcHJvcGFnYXRlIGhhbmRsZXIncyByZXR1 cm4gdmFsdWUgdG8KYWNwaV90YWJsZV9wYXJzZSgpJ3MgY2FsbGVyLgoKQU1E LElPTU1VOiBDbGVhbiB1cCBvbGQgZW50cmllcyBpbiByZW1hcHBpbmcgdGFi bGVzIHdoZW4gY3JlYXRpbmcgbmV3CmludGVycnVwdCBtYXBwaW5nLgoKV2hl biBjaGFuZ2luZyB0aGUgYWZmaW5pdHkgb2YgYW4gSVJRIGFzc29jaWF0ZWQg d2l0aCBhIHBhc3NlZAp0aHJvdWdoIFBDSSBkZXZpY2UsIGNsZWFyIHByZXZp b3VzIG1hcHBpbmcuCgpJbiBhZGRpdGlvbiwgYmVjYXVzZSBzb21lIEJJT1Nl cyBtYXkgaW5jb3JyZWN0bHkgcHJvZ3JhbSBJVlJTCmVudHJpZXMgZm9yIElP QVBJQyB0cnkgdG8gY2hlY2sgZm9yIGVudHJ5J3MgY29uc2lzdGVuY3kuIFNw ZWNpZmljYWxseSwKaWYgY29uZmxpY3RpbmcgZW50cmllcyBhcmUgZm91bmQg ZGlzYWJsZSBJT01NVSBpZiBwZXItZGV2aWNlCnJlbWFwcGluZyB0YWJsZSBp cyB1c2VkLiBJZiBlbnRyaWVzIHJlZmVyIHRvIGJvZ3VzIElPQVBJQyBJRHMK ZGlzYWJsZSBJT01NVSB1bmNvbmRpdGlvbmFsbHkKCkFNRCxJT01NVTogRGlz YWJsZSBJT01NVSBpZiBTQVRBIENvbWJpbmVkIG1vZGUgaXMgb24KCkFNRCdz IFNQNTEwMCBjaGlwc2V0IGNhbiBiZSBwbGFjZWQgaW50byBTQVRBIENvbWJp bmVkIG1vZGUKdGhhdCBtYXkgY2F1c2UgcHJldmVudCBkb20wIGZyb20gYm9v dGluZyB3aGVuIElPTU1VIGlzCmVuYWJsZWQgYW5kIHBlci1kZXZpY2UgaW50 ZXJydXB0IHJlbWFwcGluZyB0YWJsZSBpcyB1c2VkLgpXaGlsZSBTUDUxMDAg ZXJyYXR1bSAyOCByZXF1aXJlcyBCSU9TZXMgdG8gZGlzYWJsZSB0aGlzIG1v ZGUsCnNvbWUgbWF5IHN0aWxsIHVzZSBpdC4KClRoaXMgcGF0Y2ggY2hlY2tz IHdoZXRoZXIgdGhpcyBtb2RlIGlzIG9uIGFuZCwgaWYgcGVyLWRldmljZQp0 YWJsZSBpcyBpbiB1c2UsIGRpc2FibGVzIElPTU1VLgoKQU1ELElPTU1VOiBN YWtlIHBlci1kZXZpY2UgaW50ZXJydXB0IHJlbWFwcGluZyB0YWJsZSBkZWZh dWx0CgpVc2luZyBnbG9iYWwgaW50ZXJydXB0IHJlbWFwcGluZyB0YWJsZSBt YXkgYmUgaW5zZWN1cmUsIGFzCmRlc2NyaWJlZCBieSBYU0EtMzYuIFRoaXMg cGF0Y2ggbWFrZXMgcGVyLWRldmljZSBtb2RlIGRlZmF1bHQuCgpUaGlzIGlz IFhTQS0zNiAvIENWRS0yMDEzLTAxNTMuCgpTaWduZWQtb2ZmLWJ5OiBKYW4g QmV1bGljaCA8amJldWxpY2hAc3VzZS5jb20+ClNpZ25lZC1vZmYtYnk6IEJv cmlzIE9zdHJvdnNreSA8Ym9yaXMub3N0cm92c2t5QGFtZC5jb20+CgotLS0g YS94ZW4vYXJjaC94ODYvaXJxLmMKKysrIGIveGVuL2FyY2gveDg2L2lycS5j CkBAIC0xOTQzLDkgKzE5NDMsNiBAQCBpbnQgbWFwX2RvbWFpbl9waXJxKAog ICAgICAgICBzcGluX2xvY2tfaXJxc2F2ZSgmZGVzYy0+bG9jaywgZmxhZ3Mp OwogICAgICAgICBzZXRfZG9tYWluX2lycV9waXJxKGQsIGlycSwgaW5mbyk7 CiAgICAgICAgIHNwaW5fdW5sb2NrX2lycXJlc3RvcmUoJmRlc2MtPmxvY2ss IGZsYWdzKTsKLQotICAgICAgICBpZiAoIG9wdF9pcnFfdmVjdG9yX21hcCA9 PSBPUFRfSVJRX1ZFQ1RPUl9NQVBfUEVSREVWICkKLSAgICAgICAgICAgIHBy aW50ayhYRU5MT0dfSU5GTyAiUGVyLWRldmljZSB2ZWN0b3IgbWFwcyBmb3Ig R1NJcyBub3QgaW1wbGVtZW50ZWQgeWV0LlxuIik7CiAgICAgfQogCiBkb25l OgotLS0gYS94ZW4vZHJpdmVycy9hY3BpL3RhYmxlcy5jCisrKyBiL3hlbi9k cml2ZXJzL2FjcGkvdGFibGVzLmMKQEAgLTI2NSw3ICsyNjUsNyBAQCBhY3Bp X3RhYmxlX3BhcnNlX21hZHQoZW51bSBhY3BpX21hZHRfdHlwCiAgKiBAaGFu ZGxlcjogaGFuZGxlciB0byBydW4KICAqCiAgKiBTY2FuIHRoZSBBQ1BJIFN5 c3RlbSBEZXNjcmlwdG9yIFRhYmxlIChTVEQpIGZvciBhIHRhYmxlIG1hdGNo aW5nIEBpZCwKLSAqIHJ1biBAaGFuZGxlciBvbiBpdC4gIFJldHVybiAwIGlm IHRhYmxlIGZvdW5kLCByZXR1cm4gb24gaWYgbm90LgorICogcnVuIEBoYW5k bGVyIG9uIGl0LgogICovCiBpbnQgX19pbml0IGFjcGlfdGFibGVfcGFyc2Uo Y2hhciAqaWQsIGFjcGlfdGFibGVfaGFuZGxlciBoYW5kbGVyKQogewpAQCAt MjgwLDggKzI4MCw3IEBAIGludCBfX2luaXQgYWNwaV90YWJsZV9wYXJzZShj aGFyICppZCwgYWMKIAkJYWNwaV9nZXRfdGFibGUoaWQsIDAsICZ0YWJsZSk7 CiAKIAlpZiAodGFibGUpIHsKLQkJaGFuZGxlcih0YWJsZSk7Ci0JCXJldHVy biAwOworCQlyZXR1cm4gaGFuZGxlcih0YWJsZSk7CiAJfSBlbHNlCiAJCXJl dHVybiAxOwogfQotLS0gYS94ZW4vZHJpdmVycy9wYXNzdGhyb3VnaC9hbWQv aW9tbXVfYWNwaS5jCisrKyBiL3hlbi9kcml2ZXJzL3Bhc3N0aHJvdWdoL2Ft ZC9pb21tdV9hY3BpLmMKQEAgLTIyLDYgKzIyLDcgQEAKICNpbmNsdWRlIDx4 ZW4vZXJybm8uaD4KICNpbmNsdWRlIDx4ZW4vYWNwaS5oPgogI2luY2x1ZGUg PGFzbS9hcGljZGVmLmg+CisjaW5jbHVkZSA8YXNtL2lvX2FwaWMuaD4KICNp bmNsdWRlIDxhc20vYW1kLWlvbW11Lmg+CiAjaW5jbHVkZSA8YXNtL2h2bS9z dm0vYW1kLWlvbW11LXByb3RvLmg+CiAKQEAgLTYzNyw2ICs2MzgsNyBAQCBz dGF0aWMgdTE2IF9faW5pdCBwYXJzZV9pdmhkX2RldmljZV9zcGVjCiAgICAg dTE2IGhlYWRlcl9sZW5ndGgsIHUxNiBibG9ja19sZW5ndGgsIHN0cnVjdCBh bWRfaW9tbXUgKmlvbW11KQogewogICAgIHUxNiBkZXZfbGVuZ3RoLCBiZGY7 CisgICAgaW50IGFwaWM7CiAKICAgICBkZXZfbGVuZ3RoID0gc2l6ZW9mKCpz cGVjaWFsKTsKICAgICBpZiAoIGhlYWRlcl9sZW5ndGggPCAoYmxvY2tfbGVu Z3RoICsgZGV2X2xlbmd0aCkgKQpAQCAtNjU3LDkgKzY1OSw1MyBAQCBzdGF0 aWMgdTE2IF9faW5pdCBwYXJzZV9pdmhkX2RldmljZV9zcGVjCiAgICAgc3dp dGNoICggc3BlY2lhbC0+dmFyaWV0eSApCiAgICAgewogICAgIGNhc2UgQUNQ SV9JVkhEX0lPQVBJQzoKLSAgICAvKiBzZXQgZGV2aWNlIGlkIG9mIGlvYXBp YyAqLwotICAgICAgICBpb2FwaWNfc2JkZltzcGVjaWFsLT5oYW5kbGVdLmJk ZiA9IGJkZjsKLSAgICAgICAgaW9hcGljX3NiZGZbc3BlY2lhbC0+aGFuZGxl XS5zZWcgPSBzZWc7CisgICAgICAgIC8qCisgICAgICAgICAqIFNvbWUgQklP U2VzIGhhdmUgSU9BUElDIGJyb2tlbiBlbnRyaWVzIHNvIHdlIGNoZWNrIGZv ciBJVlJTCisgICAgICAgICAqIGNvbnNpc3RlbmN5IGhlcmUgLS0tIHdoZXRo ZXIgZW50cnkncyBJT0FQSUMgSUQgaXMgdmFsaWQgYW5kCisgICAgICAgICAq IHdoZXRoZXIgdGhlcmUgYXJlIGNvbmZsaWN0aW5nL2R1cGxpY2F0ZWQgZW50 cmllcy4KKyAgICAgICAgICovCisgICAgICAgIGZvciAoIGFwaWMgPSAwOyBh cGljIDwgbnJfaW9hcGljczsgYXBpYysrICkKKyAgICAgICAgeworICAgICAg ICAgICAgaWYgKCBJT19BUElDX0lEKGFwaWMpICE9IHNwZWNpYWwtPmhhbmRs ZSApCisgICAgICAgICAgICAgICAgY29udGludWU7CisKKyAgICAgICAgICAg IGlmICggaW9hcGljX3NiZGZbc3BlY2lhbC0+aGFuZGxlXS5waW5fc2V0dXAg KQorICAgICAgICAgICAgeworICAgICAgICAgICAgICAgIGlmICggaW9hcGlj X3NiZGZbc3BlY2lhbC0+aGFuZGxlXS5iZGYgPT0gYmRmICYmCisgICAgICAg ICAgICAgICAgICAgICBpb2FwaWNfc2JkZltzcGVjaWFsLT5oYW5kbGVdLnNl ZyA9PSBzZWcgKQorICAgICAgICAgICAgICAgICAgICBBTURfSU9NTVVfREVC VUcoIklWSEQgV2FybmluZzogRHVwbGljYXRlIElPLUFQSUMgJSN4IGVudHJp ZXNcbiIsCisgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICBz cGVjaWFsLT5oYW5kbGUpOworICAgICAgICAgICAgICAgIGVsc2UKKyAgICAg ICAgICAgICAgICB7CisgICAgICAgICAgICAgICAgICAgIHByaW50ayhYRU5M T0dfRVJSICJJVkhEIEVycm9yOiBDb25mbGljdGluZyBJTy1BUElDICUjeCBl bnRyaWVzXG4iLAorICAgICAgICAgICAgICAgICAgICAgICAgICAgc3BlY2lh bC0+aGFuZGxlKTsKKyAgICAgICAgICAgICAgICAgICAgaWYgKCBhbWRfaW9t bXVfcGVyZGV2X2ludHJlbWFwICkKKyAgICAgICAgICAgICAgICAgICAgICAg IHJldHVybiAwOworICAgICAgICAgICAgICAgIH0KKyAgICAgICAgICAgIH0K KyAgICAgICAgICAgIGVsc2UKKyAgICAgICAgICAgIHsKKyAgICAgICAgICAg ICAgICAvKiBzZXQgZGV2aWNlIGlkIG9mIGlvYXBpYyAqLworICAgICAgICAg ICAgICAgIGlvYXBpY19zYmRmW3NwZWNpYWwtPmhhbmRsZV0uYmRmID0gYmRm OworICAgICAgICAgICAgICAgIGlvYXBpY19zYmRmW3NwZWNpYWwtPmhhbmRs ZV0uc2VnID0gc2VnOworCisgICAgICAgICAgICAgICAgaW9hcGljX3NiZGZb c3BlY2lhbC0+aGFuZGxlXS5waW5fc2V0dXAgPSB4emFsbG9jX2FycmF5KAor ICAgICAgICAgICAgICAgICAgICB1bnNpZ25lZCBsb25nLCBCSVRTX1RPX0xP TkdTKG5yX2lvYXBpY19lbnRyaWVzW2FwaWNdKSk7CisgICAgICAgICAgICAg ICAgaWYgKCBucl9pb2FwaWNfZW50cmllc1thcGljXSAmJgorICAgICAgICAg ICAgICAgICAgICAgIWlvYXBpY19zYmRmW0lPX0FQSUNfSUQoYXBpYyldLnBp bl9zZXR1cCApCisgICAgICAgICAgICAgICAgeworICAgICAgICAgICAgICAg ICAgICBwcmludGsoWEVOTE9HX0VSUiAiSVZIRCBFcnJvcjogT3V0IG9mIG1l bW9yeVxuIik7CisgICAgICAgICAgICAgICAgICAgIHJldHVybiAwOworICAg ICAgICAgICAgICAgIH0KKyAgICAgICAgICAgIH0KKyAgICAgICAgICAgIGJy ZWFrOworICAgICAgICB9CisgICAgICAgIGlmICggYXBpYyA9PSBucl9pb2Fw aWNzICkKKyAgICAgICAgeworICAgICAgICAgICAgcHJpbnRrKFhFTkxPR19F UlIgIklWSEQgRXJyb3I6IEludmFsaWQgSU8tQVBJQyAlI3hcbiIsCisgICAg ICAgICAgICAgICAgICAgc3BlY2lhbC0+aGFuZGxlKTsKKyAgICAgICAgICAg IHJldHVybiAwOworICAgICAgICB9CiAgICAgICAgIGJyZWFrOwogICAgIGNh c2UgQUNQSV9JVkhEX0hQRVQ6CiAgICAgICAgIC8qIHNldCBkZXZpY2UgaWQg b2YgaHBldCAqLwotLS0gYS94ZW4vZHJpdmVycy9wYXNzdGhyb3VnaC9hbWQv aW9tbXVfaW5pdC5jCisrKyBiL3hlbi9kcml2ZXJzL3Bhc3N0aHJvdWdoL2Ft ZC9pb21tdV9pbml0LmMKQEAgLTExMjAsMTIgKzExMjAsNDUgQEAgc3RhdGlj IGludCBfX2luaXQgYW1kX2lvbW11X3NldHVwX2RldmljZQogICAgIHJldHVy biAwOwogfQogCisvKiBDaGVjayB3aGV0aGVyIFNQNTEwMCBTQVRBIENvbWJp bmVkIG1vZGUgaXMgb24gKi8KK3N0YXRpYyBib29sX3QgX19pbml0IGFtZF9z cDUxMDBfZXJyYXR1bTI4KHZvaWQpCit7CisgICAgdTMyIGJ1cywgaWQ7Cisg ICAgdTE2IHZlbmRvcl9pZCwgZGV2X2lkOworICAgIHU4IGJ5dGU7CisKKyAg ICBmb3IgKGJ1cyA9IDA7IGJ1cyA8IDI1NjsgYnVzKyspCisgICAgeworICAg ICAgICBpZCA9IHBjaV9jb25mX3JlYWQzMigwLCBidXMsIDB4MTQsIDAsIFBD SV9WRU5ET1JfSUQpOworCisgICAgICAgIHZlbmRvcl9pZCA9IGlkICYgMHhm ZmZmOworICAgICAgICBkZXZfaWQgPSAoaWQgPj4gMTYpICYgMHhmZmZmOwor CisgICAgICAgIC8qIFNQNTEwMCBTTUJ1cyBtb2R1bGUgc2V0cyBDb21iaW5l ZCBtb2RlIG9uICovCisgICAgICAgIGlmICh2ZW5kb3JfaWQgIT0gMHgxMDAy IHx8IGRldl9pZCAhPSAweDQzODUpCisgICAgICAgICAgICBjb250aW51ZTsK KworICAgICAgICBieXRlID0gcGNpX2NvbmZfcmVhZDgoMCwgYnVzLCAweDE0 LCAwLCAweGFkKTsKKyAgICAgICAgaWYgKCAoYnl0ZSA+PiAzKSAmIDEgKQor ICAgICAgICB7CisgICAgICAgICAgICBwcmludGsoWEVOTE9HX1dBUk5JTkcg IkFNRC1WaTogU1A1MTAwIGVycmF0dW0gMjggZGV0ZWN0ZWQsIGRpc2FibGlu ZyBJT01NVS5cbiIKKyAgICAgICAgICAgICAgICAgICAiSWYgcG9zc2libGUs IGRpc2FibGUgU0FUQSBDb21iaW5lZCBtb2RlIGluIEJJT1Mgb3IgY29udGFj dCB5b3VyIHZlbmRvciBmb3IgQklPUyB1cGRhdGUuXG4iKTsKKyAgICAgICAg ICAgIHJldHVybiAxOworICAgICAgICB9CisgICAgfQorCisgICAgcmV0dXJu IDA7Cit9CisKIGludCBfX2luaXQgYW1kX2lvbW11X2luaXQodm9pZCkKIHsK ICAgICBzdHJ1Y3QgYW1kX2lvbW11ICppb21tdTsKIAogICAgIEJVR19PTigg IWlvbW11X2ZvdW5kKCkgKTsKIAorICAgIGlmICggYW1kX2lvbW11X3BlcmRl dl9pbnRyZW1hcCAmJiBhbWRfc3A1MTAwX2VycmF0dW0yOCgpICkKKyAgICAg ICAgZ290byBlcnJvcl9vdXQ7CisKICAgICBpdnJzX2JkZl9lbnRyaWVzID0g YW1kX2lvbW11X2dldF9pdnJzX2Rldl9lbnRyaWVzKCk7CiAKICAgICBpZiAo ICFpdnJzX2JkZl9lbnRyaWVzICkKLS0tIGEveGVuL2RyaXZlcnMvcGFzc3Ro cm91Z2gvYW1kL2lvbW11X2ludHIuYworKysgYi94ZW4vZHJpdmVycy9wYXNz dGhyb3VnaC9hbWQvaW9tbXVfaW50ci5jCkBAIC0xMDAsMTIgKzEwMCwxMiBA QCBzdGF0aWMgdm9pZCB1cGRhdGVfaW50cmVtYXBfZW50cnkodTMyKiBlCiBz dGF0aWMgdm9pZCB1cGRhdGVfaW50cmVtYXBfZW50cnlfZnJvbV9pb2FwaWMo CiAgICAgaW50IGJkZiwKICAgICBzdHJ1Y3QgYW1kX2lvbW11ICppb21tdSwK LSAgICBzdHJ1Y3QgSU9fQVBJQ19yb3V0ZV9lbnRyeSAqaW9hcGljX3J0ZSkK KyAgICBjb25zdCBzdHJ1Y3QgSU9fQVBJQ19yb3V0ZV9lbnRyeSAqcnRlLAor ICAgIGNvbnN0IHN0cnVjdCBJT19BUElDX3JvdXRlX2VudHJ5ICpvbGRfcnRl KQogewogICAgIHVuc2lnbmVkIGxvbmcgZmxhZ3M7CiAgICAgdTMyKiBlbnRy eTsKICAgICB1OCBkZWxpdmVyeV9tb2RlLCBkZXN0LCB2ZWN0b3IsIGRlc3Rf bW9kZTsKLSAgICBzdHJ1Y3QgSU9fQVBJQ19yb3V0ZV9lbnRyeSAqcnRlID0g aW9hcGljX3J0ZTsKICAgICBpbnQgcmVxX2lkOwogICAgIHNwaW5sb2NrX3Qg KmxvY2s7CiAgICAgaW50IG9mZnNldDsKQEAgLTEyMSw2ICsxMjEsMTQgQEAg c3RhdGljIHZvaWQgdXBkYXRlX2ludHJlbWFwX2VudHJ5X2Zyb21faQogICAg IHNwaW5fbG9ja19pcnFzYXZlKGxvY2ssIGZsYWdzKTsKIAogICAgIG9mZnNl dCA9IGdldF9pbnRyZW1hcF9vZmZzZXQodmVjdG9yLCBkZWxpdmVyeV9tb2Rl KTsKKyAgICBpZiAoIG9sZF9ydGUgKQorICAgIHsKKyAgICAgICAgaW50IG9s ZF9vZmZzZXQgPSBnZXRfaW50cmVtYXBfb2Zmc2V0KG9sZF9ydGUtPnZlY3Rv ciwKKyAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg ICAgIG9sZF9ydGUtPmRlbGl2ZXJ5X21vZGUpOworCisgICAgICAgIGlmICgg b2Zmc2V0ICE9IG9sZF9vZmZzZXQgKQorICAgICAgICAgICAgZnJlZV9pbnRy ZW1hcF9lbnRyeShpb21tdS0+c2VnLCBiZGYsIG9sZF9vZmZzZXQpOworICAg IH0KICAgICBlbnRyeSA9ICh1MzIqKWdldF9pbnRyZW1hcF9lbnRyeShpb21t dS0+c2VnLCByZXFfaWQsIG9mZnNldCk7CiAgICAgdXBkYXRlX2ludHJlbWFw X2VudHJ5KGVudHJ5LCB2ZWN0b3IsIGRlbGl2ZXJ5X21vZGUsIGRlc3RfbW9k ZSwgZGVzdCk7CiAKQEAgLTE4OSw2ICsxOTcsNyBAQCBpbnQgX19pbml0IGFt ZF9pb21tdV9zZXR1cF9pb2FwaWNfcmVtYXBwCiAgICAgICAgICAgICAgICAg YW1kX2lvbW11X2ZsdXNoX2ludHJlbWFwKGlvbW11LCByZXFfaWQpOwogICAg ICAgICAgICAgICAgIHNwaW5fdW5sb2NrX2lycXJlc3RvcmUoJmlvbW11LT5s b2NrLCBmbGFncyk7CiAgICAgICAgICAgICB9CisgICAgICAgICAgICBzZXRf Yml0KHBpbiwgaW9hcGljX3NiZGZbSU9fQVBJQ19JRChhcGljKV0ucGluX3Nl dHVwKTsKICAgICAgICAgfQogICAgIH0KICAgICByZXR1cm4gMDsKQEAgLTIw MCw2ICsyMDksNyBAQCB2b2lkIGFtZF9pb21tdV9pb2FwaWNfdXBkYXRlX2ly ZSgKICAgICBzdHJ1Y3QgSU9fQVBJQ19yb3V0ZV9lbnRyeSBvbGRfcnRlID0g eyAwIH07CiAgICAgc3RydWN0IElPX0FQSUNfcm91dGVfZW50cnkgbmV3X3J0 ZSA9IHsgMCB9OwogICAgIHVuc2lnbmVkIGludCBydGVfbG8gPSAocmVnICYg MSkgPyByZWcgLSAxIDogcmVnOworICAgIHVuc2lnbmVkIGludCBwaW4gPSAo cmVnIC0gMHgxMCkgLyAyOwogICAgIGludCBzYXZlZF9tYXNrLCBzZWcsIGJk ZjsKICAgICBzdHJ1Y3QgYW1kX2lvbW11ICppb21tdTsKIApAQCAtMjM3LDYg KzI0NywxNCBAQCB2b2lkIGFtZF9pb21tdV9pb2FwaWNfdXBkYXRlX2lyZSgK ICAgICAgICAgKigoKHUzMiAqKSZuZXdfcnRlKSArIDEpID0gdmFsdWU7CiAg ICAgfQogCisgICAgaWYgKCBuZXdfcnRlLm1hc2sgJiYKKyAgICAgICAgICF0 ZXN0X2JpdChwaW4sIGlvYXBpY19zYmRmW0lPX0FQSUNfSUQoYXBpYyldLnBp bl9zZXR1cCkgKQorICAgIHsKKyAgICAgICAgQVNTRVJUKHNhdmVkX21hc2sp OworICAgICAgICBfX2lvX2FwaWNfd3JpdGUoYXBpYywgcmVnLCB2YWx1ZSk7 CisgICAgICAgIHJldHVybjsKKyAgICB9CisKICAgICAvKiBtYXNrIHRoZSBp bnRlcnJ1cHQgd2hpbGUgd2UgY2hhbmdlIHRoZSBpbnRyZW1hcCB0YWJsZSAq LwogICAgIGlmICggIXNhdmVkX21hc2sgKQogICAgIHsKQEAgLTI0NSw3ICsy NjMsMTEgQEAgdm9pZCBhbWRfaW9tbXVfaW9hcGljX3VwZGF0ZV9pcmUoCiAg ICAgfQogCiAgICAgLyogVXBkYXRlIGludGVycnVwdCByZW1hcHBpbmcgZW50 cnkgKi8KLSAgICB1cGRhdGVfaW50cmVtYXBfZW50cnlfZnJvbV9pb2FwaWMo YmRmLCBpb21tdSwgJm5ld19ydGUpOworICAgIHVwZGF0ZV9pbnRyZW1hcF9l bnRyeV9mcm9tX2lvYXBpYygKKyAgICAgICAgYmRmLCBpb21tdSwgJm5ld19y dGUsCisgICAgICAgIHRlc3RfYW5kX3NldF9iaXQocGluLAorICAgICAgICAg ICAgICAgICAgICAgICAgIGlvYXBpY19zYmRmW0lPX0FQSUNfSUQoYXBpYyld LnBpbl9zZXR1cCkgPyAmb2xkX3J0ZQorICAgICAgICAgICAgICAgICAgICAg ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg OiBOVUxMKTsKIAogICAgIC8qIEZvcndhcmQgd3JpdGUgYWNjZXNzIHRvIElP LUFQSUMgUlRFICovCiAgICAgX19pb19hcGljX3dyaXRlKGFwaWMsIHJlZywg dmFsdWUpOwpAQCAtMzU2LDYgKzM3OCwxMiBAQCB2b2lkIGFtZF9pb21tdV9t c2lfbXNnX3VwZGF0ZV9pcmUoCiAgICAgICAgIHJldHVybjsKICAgICB9CiAK KyAgICBpZiAoIG1zaV9kZXNjLT5yZW1hcF9pbmRleCA+PSAwICkKKyAgICAg ICAgdXBkYXRlX2ludHJlbWFwX2VudHJ5X2Zyb21fbXNpX21zZyhpb21tdSwg YmRmLCBtc2lfZGVzYywgTlVMTCk7CisKKyAgICBpZiAoICFtc2cgKQorICAg ICAgICByZXR1cm47CisKICAgICB1cGRhdGVfaW50cmVtYXBfZW50cnlfZnJv bV9tc2lfbXNnKGlvbW11LCBiZGYsIG1zaV9kZXNjLCBtc2cpOwogfQogCi0t LSBhL3hlbi9kcml2ZXJzL3Bhc3N0aHJvdWdoL2FtZC9wY2lfYW1kX2lvbW11 LmMKKysrIGIveGVuL2RyaXZlcnMvcGFzc3Rocm91Z2gvYW1kL3BjaV9hbWRf aW9tbXUuYwpAQCAtMjA4LDYgKzIwOCw4IEBAIGludCBfX2luaXQgYW1kX2lv dl9kZXRlY3Qodm9pZCkKICAgICB7CiAgICAgICAgIHByaW50aygiQU1ELVZp OiBOb3Qgb3ZlcnJpZGluZyBpcnFfdmVjdG9yX21hcCBzZXR0aW5nXG4iKTsK ICAgICB9CisgICAgaWYgKCAhYW1kX2lvbW11X3BlcmRldl9pbnRyZW1hcCAp CisgICAgICAgIHByaW50ayhYRU5MT0dfV0FSTklORyAiQU1ELVZpOiBVc2lu ZyBnbG9iYWwgaW50ZXJydXB0IHJlbWFwIHRhYmxlIGlzIG5vdCByZWNvbW1l bmRlZCAoc2VlIFhTQS0zNikhXG4iKTsKICAgICByZXR1cm4gc2Nhbl9wY2lf ZGV2aWNlcygpOwogfQogCi0tLSBhL3hlbi9kcml2ZXJzL3Bhc3N0aHJvdWdo L2lvbW11LmMKKysrIGIveGVuL2RyaXZlcnMvcGFzc3Rocm91Z2gvaW9tbXUu YwpAQCAtNTMsNyArNTMsNyBAQCBib29sX3QgX19yZWFkX21vc3RseSBpb21t dV9xaW52YWwgPSAxOwogYm9vbF90IF9fcmVhZF9tb3N0bHkgaW9tbXVfaW50 cmVtYXAgPSAxOwogYm9vbF90IF9fcmVhZF9tb3N0bHkgaW9tbXVfaGFwX3B0 X3NoYXJlID0gMTsKIGJvb2xfdCBfX3JlYWRfbW9zdGx5IGlvbW11X2RlYnVn OwotYm9vbF90IF9fcmVhZF9tb3N0bHkgYW1kX2lvbW11X3BlcmRldl9pbnRy ZW1hcDsKK2Jvb2xfdCBfX3JlYWRfbW9zdGx5IGFtZF9pb21tdV9wZXJkZXZf aW50cmVtYXAgPSAxOwogCiBERUZJTkVfUEVSX0NQVShib29sX3QsIGlvbW11 X2RvbnRfZmx1c2hfaW90bGIpOwogCi0tLSBhL3hlbi9pbmNsdWRlL2FzbS14 ODYvaHZtL3N2bS9hbWQtaW9tbXUtcHJvdG8uaAorKysgYi94ZW4vaW5jbHVk ZS9hc20teDg2L2h2bS9zdm0vYW1kLWlvbW11LXByb3RvLmgKQEAgLTEwMSw2 ICsxMDEsNyBAQCBpbnQgYW1kX3NldHVwX2hwZXRfbXNpKHN0cnVjdCBtc2lf ZGVzYyAqCiAKIGV4dGVybiBzdHJ1Y3QgaW9hcGljX3NiZGYgewogICAgIHUx NiBiZGYsIHNlZzsKKyAgICB1bnNpZ25lZCBsb25nICpwaW5fc2V0dXA7CiB9 IGlvYXBpY19zYmRmW01BWF9JT19BUElDU107CiBleHRlcm4gdm9pZCAqc2hh cmVkX2ludHJlbWFwX3RhYmxlOwogCg== --=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 Tue Feb 05 13:17:03 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 05 Feb 2013 13:17: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 1U2iO1-0007zu-5u; Tue, 05 Feb 2013 13:16:33 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U2iNy-0007xy-Q3; Tue, 05 Feb 2013 13:16:31 +0000 Received: from [193.109.254.147:30992] by server-15.bemta-14.messagelabs.com id 2E/C5-24599-D2601115; Tue, 05 Feb 2013 13:16:29 +0000 X-Env-Sender: ianc@xenbits.xen.org X-Msg-Ref: server-9.tower-27.messagelabs.com!1360070124!9615039!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.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 14883 invoked from network); 5 Feb 2013 13:15:26 -0000 Received: from mail.xen.org (HELO mail.xen.org) (50.57.168.107) by server-9.tower-27.messagelabs.com with AES256-SHA encrypted SMTP; 5 Feb 2013 13:15:26 -0000 Received: from xenbits.xen.org ([50.57.170.242]) by mail.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U2iMo-0003am-0E; Tue, 05 Feb 2013 13:15:18 +0000 Received: from ianc by xenbits.xen.org with local (Exim 4.72) (envelope-from ) id 1U2iMn-0008As-4b; Tue, 05 Feb 2013 13:15:17 +0000 Date: Tue, 05 Feb 2013 13:15:17 +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 43 (CVE-2013-0231) - Linux pciback DoS via not rate limited log messages. X-BeenThere: xen-users@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-2013-0231 / XSA-43 version 2 Linux pciback DoS via not rate limited log messages. UPDATES IN VERSION 2 ==================== Public release. ISSUE DESCRIPTION ================= Xen's PCI backend drivers in Linux allow a guest with assigned PCI device(s) to cause a DoS through a flood of kernel messages, potentially affecting other domains in the system. IMPACT ====== A malicious guest can mount a DoS affecting the entire system. VULNERABLE SYSTEMS ================== All systems running guests with access to passed through PCI devices are vulnerable. Both mainline ("pvops") and classic-Xen patch kernels are affected. MITIGATION ========== This issue can be avoided by not assigning PCI devices to untrusted guests. RESOLUTION ========== Applying the appropriate attached patch resolves this issue. xsa43-pvops.patch Apply to mainline Linux 3.8-rc5. xsa43-classic.patch Apply to linux-2.6.18-xen tree. $ sha256sum xsa43*.patch 4dec2d9b043bce2b8b54578573ba254fa7e6cbf4640cd100f40d8bf8a5a6a470 xsa43-classic.patch 6efe83c9951dcba20f18095814d19089e19230c6876bbdab32cc2f1165bb07c8 xsa43-pvops.patch $ -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) iQEcBAEBAgAGBQJREQI+AAoJEIP+FMlX6CvZkoEH/2sIEO+1qLiHTde/UJznrvr8 R8MDNC5tqXVLtbPjScoTItMHaPfz33lcypz9UFknHepdwZKhRrcuqy4E79lxeXDG BybbbbfNfJPeUG44O1fkyJTJys0xRBnAGzWInZZwq+gWRaJv+JNhzinFujvLNDJV 4m2ObnSwT1mx/9CjRxWGakKDhPcZSGmWIicyN5tueNKdWbAjSqiR/J8N5W+QJiCm +BzjzYpfUqn0vKOlARQIMshzqFjYVTnoHFZf/4Hl7ogIibxfGGo5t05pzBoAlIgj nTizW2Bxs9XM1NaFsZ2ESg8KVDTFSHS+jsMtdl0bWoHwRs6nNMQJJTjTPHXspCQ= =5o5U -----END PGP SIGNATURE----- --=separator Content-Type: application/octet-stream; name="xsa43-classic.patch" Content-Disposition: attachment; filename="xsa43-classic.patch" Content-Transfer-Encoding: base64 cGNpYmFjazogcmF0ZSBsaW1pdCBlcnJvciBtZXNzYWdlIGZyb20gcGNpYmFj a19lbmFibGVfbXNpKCkKCi4uLiBhcyBiZWluZyBndWVzdCB0cmlnZ2VyYWJs ZSAoZS5nLiBieSBpbnZva2luZyBYRU5fUENJX09QX2VuYWJsZV9tc2kKb24g YSBkZXZpY2Ugbm90IGJlaW5nIE1TSSBjYXBhYmxlKS4KClRoaXMgaXMgQ1ZF LTIwMTMtMDIzMSAvIFhTQS00My4KClNpZ25lZC1vZmYtYnk6IEphbiBCZXVs aWNoIDxqYmV1bGljaEBzdXNlLmNvbT4KCi0tLSBhL2RyaXZlcnMveGVuL3Bj aWJhY2svY29uZl9zcGFjZV9jYXBhYmlsaXR5X21zaS5jCisrKyBiL2RyaXZl cnMveGVuL3BjaWJhY2svY29uZl9zcGFjZV9jYXBhYmlsaXR5X21zaS5jCkBA IC0xMSwxMyArMTEsMTIgQEAKIGludCBwY2liYWNrX2VuYWJsZV9tc2koc3Ry dWN0IHBjaWJhY2tfZGV2aWNlICpwZGV2LAogCQlzdHJ1Y3QgcGNpX2RldiAq ZGV2LCBzdHJ1Y3QgeGVuX3BjaV9vcCAqb3ApCiB7Ci0JaW50IG90aGVyZW5k ID0gcGRldi0+eGRldi0+b3RoZXJlbmRfaWQ7Ci0JaW50IHN0YXR1czsKLQot CXN0YXR1cyA9IHBjaV9lbmFibGVfbXNpKGRldik7CisJaW50IHN0YXR1cyA9 IHBjaV9lbmFibGVfbXNpKGRldik7CiAKIAlpZiAoc3RhdHVzKSB7Ci0JCXBy aW50aygiZXJyb3IgZW5hYmxlIG1zaSBmb3IgZ3Vlc3QgJXggc3RhdHVzICV4 XG4iLCBvdGhlcmVuZCwgc3RhdHVzKTsKKwkJaWYgKHByaW50a19yYXRlbGlt aXQoKSkKKwkJCXByaW50aygiZXJyb3IgZW5hYmxpbmcgTVNJIGZvciBndWVz dCAldSBzdGF0dXMgJWRcbiIsCisJCQkgICAgICAgcGRldi0+eGRldi0+b3Ro ZXJlbmRfaWQsIHN0YXR1cyk7CiAJCW9wLT52YWx1ZSA9IDA7CiAJCXJldHVy biBYRU5fUENJX0VSUl9vcF9mYWlsZWQ7CiAJfQo= --=separator Content-Type: application/octet-stream; name="xsa43-pvops.patch" Content-Disposition: attachment; filename="xsa43-pvops.patch" Content-Transfer-Encoding: base64 eGVuLXBjaWJhY2s6IHJhdGUgbGltaXQgZXJyb3IgbWVzc2FnZXMgZnJvbSB4 ZW5fcGNpYmtfZW5hYmxlX21zaXsseH0oKQoKLi4uIGFzIGJlaW5nIGd1ZXN0 IHRyaWdnZXJhYmxlIChlLmcuIGJ5IGludm9raW5nClhFTl9QQ0lfT1BfZW5h YmxlX21zaXsseH0gb24gYSBkZXZpY2Ugbm90IGJlaW5nIE1TSS9NU0ktWCBj YXBhYmxlKS4KClRoaXMgaXMgQ1ZFLTIwMTMtMDIzMSAvIFhTQS00My4KCkFs c28gbWFrZSB0aGUgdHdvIG1lc3NhZ2VzIHVuaWZvcm0gaW4gYm90aCB0aGVp ciB3b3JkaW5nIGFuZCBzZXZlcml0eS4KClNpZ25lZC1vZmYtYnk6IEphbiBC ZXVsaWNoIDxqYmV1bGljaEBzdXNlLmNvbT4KQWNrZWQtYnk6IElhbiBDYW1w YmVsbCA8aWFuLmNhbXBiZWxsQGNpdHJpeC5jb20+ClJldmlld2VkLWJ5OiBL b25yYWQgUnplc3p1dGVrIFdpbGsgPGtvbnJhZC53aWxrQG9yYWNsZS5jb20+ CgotLS0KIGRyaXZlcnMveGVuL3hlbi1wY2liYWNrL3BjaWJhY2tfb3BzLmMg fCAgIDE0ICsrKysrKystLS0tLS0tCiAxIGZpbGUgY2hhbmdlZCwgNyBpbnNl cnRpb25zKCspLCA3IGRlbGV0aW9ucygtKQoKLS0tIDMuOC1yYzUvZHJpdmVy cy94ZW4veGVuLXBjaWJhY2svcGNpYmFja19vcHMuYworKysgMy44LXJjNS14 ZW4tcGNpYmFjay1yYXRlbGltaXQvZHJpdmVycy94ZW4veGVuLXBjaWJhY2sv cGNpYmFja19vcHMuYwpAQCAtMTM1LDcgKzEzNSw2IEBAIGludCB4ZW5fcGNp YmtfZW5hYmxlX21zaShzdHJ1Y3QgeGVuX3BjaWIKIAkJCSBzdHJ1Y3QgcGNp X2RldiAqZGV2LCBzdHJ1Y3QgeGVuX3BjaV9vcCAqb3ApCiB7CiAJc3RydWN0 IHhlbl9wY2lia19kZXZfZGF0YSAqZGV2X2RhdGE7Ci0JaW50IG90aGVyZW5k ID0gcGRldi0+eGRldi0+b3RoZXJlbmRfaWQ7CiAJaW50IHN0YXR1czsKIAog CWlmICh1bmxpa2VseSh2ZXJib3NlX3JlcXVlc3QpKQpAQCAtMTQ0LDggKzE0 Myw5IEBAIGludCB4ZW5fcGNpYmtfZW5hYmxlX21zaShzdHJ1Y3QgeGVuX3Bj aWIKIAlzdGF0dXMgPSBwY2lfZW5hYmxlX21zaShkZXYpOwogCiAJaWYgKHN0 YXR1cykgewotCQlwcmludGsoS0VSTl9FUlIgImVycm9yIGVuYWJsZSBtc2kg Zm9yIGd1ZXN0ICV4IHN0YXR1cyAleFxuIiwKLQkJCW90aGVyZW5kLCBzdGF0 dXMpOworCQlwcl93YXJuX3JhdGVsaW1pdGVkKERSVl9OQU1FICI6ICVzOiBl cnJvciBlbmFibGluZyBNU0kgZm9yIGd1ZXN0ICV1OiBlcnIgJWRcbiIsCisJ CQkJICAgIHBjaV9uYW1lKGRldiksIHBkZXYtPnhkZXYtPm90aGVyZW5kX2lk LAorCQkJCSAgICBzdGF0dXMpOwogCQlvcC0+dmFsdWUgPSAwOwogCQlyZXR1 cm4gWEVOX1BDSV9FUlJfb3BfZmFpbGVkOwogCX0KQEAgLTIyMywxMCArMjIz LDEwIEBAIGludCB4ZW5fcGNpYmtfZW5hYmxlX21zaXgoc3RydWN0IHhlbl9w Y2kKIAkJCQkJCXBjaV9uYW1lKGRldiksIGksCiAJCQkJCQlvcC0+bXNpeF9l bnRyaWVzW2ldLnZlY3Rvcik7CiAJCX0KLQl9IGVsc2UgewotCQlwcmludGso S0VSTl9XQVJOSU5HIERSVl9OQU1FICI6ICVzOiBmYWlsZWQgdG8gZW5hYmxl IE1TSS1YOiBlcnIgJWQhXG4iLAotCQkJcGNpX25hbWUoZGV2KSwgcmVzdWx0 KTsKLQl9CisJfSBlbHNlCisJCXByX3dhcm5fcmF0ZWxpbWl0ZWQoRFJWX05B TUUgIjogJXM6IGVycm9yIGVuYWJsaW5nIE1TSS1YIGZvciBndWVzdCAldTog ZXJyICVkIVxuIiwKKwkJCQkgICAgcGNpX25hbWUoZGV2KSwgcGRldi0+eGRl di0+b3RoZXJlbmRfaWQsCisJCQkJICAgIHJlc3VsdCk7CiAJa2ZyZWUoZW50 cmllcyk7CiAKIAlvcC0+dmFsdWUgPSByZXN1bHQ7Cg== --=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 Tue Feb 05 13:17:03 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 05 Feb 2013 13:17: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 1U2iO1-0007zu-5u; Tue, 05 Feb 2013 13:16:33 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U2iNy-0007xy-Q3; Tue, 05 Feb 2013 13:16:31 +0000 Received: from [193.109.254.147:30992] by server-15.bemta-14.messagelabs.com id 2E/C5-24599-D2601115; Tue, 05 Feb 2013 13:16:29 +0000 X-Env-Sender: ianc@xenbits.xen.org X-Msg-Ref: server-9.tower-27.messagelabs.com!1360070124!9615039!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.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 14883 invoked from network); 5 Feb 2013 13:15:26 -0000 Received: from mail.xen.org (HELO mail.xen.org) (50.57.168.107) by server-9.tower-27.messagelabs.com with AES256-SHA encrypted SMTP; 5 Feb 2013 13:15:26 -0000 Received: from xenbits.xen.org ([50.57.170.242]) by mail.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U2iMo-0003am-0E; Tue, 05 Feb 2013 13:15:18 +0000 Received: from ianc by xenbits.xen.org with local (Exim 4.72) (envelope-from ) id 1U2iMn-0008As-4b; Tue, 05 Feb 2013 13:15:17 +0000 Date: Tue, 05 Feb 2013 13:15:17 +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 43 (CVE-2013-0231) - Linux pciback DoS via not rate limited log messages. X-BeenThere: xen-users@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-2013-0231 / XSA-43 version 2 Linux pciback DoS via not rate limited log messages. UPDATES IN VERSION 2 ==================== Public release. ISSUE DESCRIPTION ================= Xen's PCI backend drivers in Linux allow a guest with assigned PCI device(s) to cause a DoS through a flood of kernel messages, potentially affecting other domains in the system. IMPACT ====== A malicious guest can mount a DoS affecting the entire system. VULNERABLE SYSTEMS ================== All systems running guests with access to passed through PCI devices are vulnerable. Both mainline ("pvops") and classic-Xen patch kernels are affected. MITIGATION ========== This issue can be avoided by not assigning PCI devices to untrusted guests. RESOLUTION ========== Applying the appropriate attached patch resolves this issue. xsa43-pvops.patch Apply to mainline Linux 3.8-rc5. xsa43-classic.patch Apply to linux-2.6.18-xen tree. $ sha256sum xsa43*.patch 4dec2d9b043bce2b8b54578573ba254fa7e6cbf4640cd100f40d8bf8a5a6a470 xsa43-classic.patch 6efe83c9951dcba20f18095814d19089e19230c6876bbdab32cc2f1165bb07c8 xsa43-pvops.patch $ -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) iQEcBAEBAgAGBQJREQI+AAoJEIP+FMlX6CvZkoEH/2sIEO+1qLiHTde/UJznrvr8 R8MDNC5tqXVLtbPjScoTItMHaPfz33lcypz9UFknHepdwZKhRrcuqy4E79lxeXDG BybbbbfNfJPeUG44O1fkyJTJys0xRBnAGzWInZZwq+gWRaJv+JNhzinFujvLNDJV 4m2ObnSwT1mx/9CjRxWGakKDhPcZSGmWIicyN5tueNKdWbAjSqiR/J8N5W+QJiCm +BzjzYpfUqn0vKOlARQIMshzqFjYVTnoHFZf/4Hl7ogIibxfGGo5t05pzBoAlIgj nTizW2Bxs9XM1NaFsZ2ESg8KVDTFSHS+jsMtdl0bWoHwRs6nNMQJJTjTPHXspCQ= =5o5U -----END PGP SIGNATURE----- --=separator Content-Type: application/octet-stream; name="xsa43-classic.patch" Content-Disposition: attachment; filename="xsa43-classic.patch" Content-Transfer-Encoding: base64 cGNpYmFjazogcmF0ZSBsaW1pdCBlcnJvciBtZXNzYWdlIGZyb20gcGNpYmFj a19lbmFibGVfbXNpKCkKCi4uLiBhcyBiZWluZyBndWVzdCB0cmlnZ2VyYWJs ZSAoZS5nLiBieSBpbnZva2luZyBYRU5fUENJX09QX2VuYWJsZV9tc2kKb24g YSBkZXZpY2Ugbm90IGJlaW5nIE1TSSBjYXBhYmxlKS4KClRoaXMgaXMgQ1ZF LTIwMTMtMDIzMSAvIFhTQS00My4KClNpZ25lZC1vZmYtYnk6IEphbiBCZXVs aWNoIDxqYmV1bGljaEBzdXNlLmNvbT4KCi0tLSBhL2RyaXZlcnMveGVuL3Bj aWJhY2svY29uZl9zcGFjZV9jYXBhYmlsaXR5X21zaS5jCisrKyBiL2RyaXZl cnMveGVuL3BjaWJhY2svY29uZl9zcGFjZV9jYXBhYmlsaXR5X21zaS5jCkBA IC0xMSwxMyArMTEsMTIgQEAKIGludCBwY2liYWNrX2VuYWJsZV9tc2koc3Ry dWN0IHBjaWJhY2tfZGV2aWNlICpwZGV2LAogCQlzdHJ1Y3QgcGNpX2RldiAq ZGV2LCBzdHJ1Y3QgeGVuX3BjaV9vcCAqb3ApCiB7Ci0JaW50IG90aGVyZW5k ID0gcGRldi0+eGRldi0+b3RoZXJlbmRfaWQ7Ci0JaW50IHN0YXR1czsKLQot CXN0YXR1cyA9IHBjaV9lbmFibGVfbXNpKGRldik7CisJaW50IHN0YXR1cyA9 IHBjaV9lbmFibGVfbXNpKGRldik7CiAKIAlpZiAoc3RhdHVzKSB7Ci0JCXBy aW50aygiZXJyb3IgZW5hYmxlIG1zaSBmb3IgZ3Vlc3QgJXggc3RhdHVzICV4 XG4iLCBvdGhlcmVuZCwgc3RhdHVzKTsKKwkJaWYgKHByaW50a19yYXRlbGlt aXQoKSkKKwkJCXByaW50aygiZXJyb3IgZW5hYmxpbmcgTVNJIGZvciBndWVz dCAldSBzdGF0dXMgJWRcbiIsCisJCQkgICAgICAgcGRldi0+eGRldi0+b3Ro ZXJlbmRfaWQsIHN0YXR1cyk7CiAJCW9wLT52YWx1ZSA9IDA7CiAJCXJldHVy biBYRU5fUENJX0VSUl9vcF9mYWlsZWQ7CiAJfQo= --=separator Content-Type: application/octet-stream; name="xsa43-pvops.patch" Content-Disposition: attachment; filename="xsa43-pvops.patch" Content-Transfer-Encoding: base64 eGVuLXBjaWJhY2s6IHJhdGUgbGltaXQgZXJyb3IgbWVzc2FnZXMgZnJvbSB4 ZW5fcGNpYmtfZW5hYmxlX21zaXsseH0oKQoKLi4uIGFzIGJlaW5nIGd1ZXN0 IHRyaWdnZXJhYmxlIChlLmcuIGJ5IGludm9raW5nClhFTl9QQ0lfT1BfZW5h YmxlX21zaXsseH0gb24gYSBkZXZpY2Ugbm90IGJlaW5nIE1TSS9NU0ktWCBj YXBhYmxlKS4KClRoaXMgaXMgQ1ZFLTIwMTMtMDIzMSAvIFhTQS00My4KCkFs c28gbWFrZSB0aGUgdHdvIG1lc3NhZ2VzIHVuaWZvcm0gaW4gYm90aCB0aGVp ciB3b3JkaW5nIGFuZCBzZXZlcml0eS4KClNpZ25lZC1vZmYtYnk6IEphbiBC ZXVsaWNoIDxqYmV1bGljaEBzdXNlLmNvbT4KQWNrZWQtYnk6IElhbiBDYW1w YmVsbCA8aWFuLmNhbXBiZWxsQGNpdHJpeC5jb20+ClJldmlld2VkLWJ5OiBL b25yYWQgUnplc3p1dGVrIFdpbGsgPGtvbnJhZC53aWxrQG9yYWNsZS5jb20+ CgotLS0KIGRyaXZlcnMveGVuL3hlbi1wY2liYWNrL3BjaWJhY2tfb3BzLmMg fCAgIDE0ICsrKysrKystLS0tLS0tCiAxIGZpbGUgY2hhbmdlZCwgNyBpbnNl cnRpb25zKCspLCA3IGRlbGV0aW9ucygtKQoKLS0tIDMuOC1yYzUvZHJpdmVy cy94ZW4veGVuLXBjaWJhY2svcGNpYmFja19vcHMuYworKysgMy44LXJjNS14 ZW4tcGNpYmFjay1yYXRlbGltaXQvZHJpdmVycy94ZW4veGVuLXBjaWJhY2sv cGNpYmFja19vcHMuYwpAQCAtMTM1LDcgKzEzNSw2IEBAIGludCB4ZW5fcGNp YmtfZW5hYmxlX21zaShzdHJ1Y3QgeGVuX3BjaWIKIAkJCSBzdHJ1Y3QgcGNp X2RldiAqZGV2LCBzdHJ1Y3QgeGVuX3BjaV9vcCAqb3ApCiB7CiAJc3RydWN0 IHhlbl9wY2lia19kZXZfZGF0YSAqZGV2X2RhdGE7Ci0JaW50IG90aGVyZW5k ID0gcGRldi0+eGRldi0+b3RoZXJlbmRfaWQ7CiAJaW50IHN0YXR1czsKIAog CWlmICh1bmxpa2VseSh2ZXJib3NlX3JlcXVlc3QpKQpAQCAtMTQ0LDggKzE0 Myw5IEBAIGludCB4ZW5fcGNpYmtfZW5hYmxlX21zaShzdHJ1Y3QgeGVuX3Bj aWIKIAlzdGF0dXMgPSBwY2lfZW5hYmxlX21zaShkZXYpOwogCiAJaWYgKHN0 YXR1cykgewotCQlwcmludGsoS0VSTl9FUlIgImVycm9yIGVuYWJsZSBtc2kg Zm9yIGd1ZXN0ICV4IHN0YXR1cyAleFxuIiwKLQkJCW90aGVyZW5kLCBzdGF0 dXMpOworCQlwcl93YXJuX3JhdGVsaW1pdGVkKERSVl9OQU1FICI6ICVzOiBl cnJvciBlbmFibGluZyBNU0kgZm9yIGd1ZXN0ICV1OiBlcnIgJWRcbiIsCisJ CQkJICAgIHBjaV9uYW1lKGRldiksIHBkZXYtPnhkZXYtPm90aGVyZW5kX2lk LAorCQkJCSAgICBzdGF0dXMpOwogCQlvcC0+dmFsdWUgPSAwOwogCQlyZXR1 cm4gWEVOX1BDSV9FUlJfb3BfZmFpbGVkOwogCX0KQEAgLTIyMywxMCArMjIz LDEwIEBAIGludCB4ZW5fcGNpYmtfZW5hYmxlX21zaXgoc3RydWN0IHhlbl9w Y2kKIAkJCQkJCXBjaV9uYW1lKGRldiksIGksCiAJCQkJCQlvcC0+bXNpeF9l bnRyaWVzW2ldLnZlY3Rvcik7CiAJCX0KLQl9IGVsc2UgewotCQlwcmludGso S0VSTl9XQVJOSU5HIERSVl9OQU1FICI6ICVzOiBmYWlsZWQgdG8gZW5hYmxl IE1TSS1YOiBlcnIgJWQhXG4iLAotCQkJcGNpX25hbWUoZGV2KSwgcmVzdWx0 KTsKLQl9CisJfSBlbHNlCisJCXByX3dhcm5fcmF0ZWxpbWl0ZWQoRFJWX05B TUUgIjogJXM6IGVycm9yIGVuYWJsaW5nIE1TSS1YIGZvciBndWVzdCAldTog ZXJyICVkIVxuIiwKKwkJCQkgICAgcGNpX25hbWUoZGV2KSwgcGRldi0+eGRl di0+b3RoZXJlbmRfaWQsCisJCQkJICAgIHJlc3VsdCk7CiAJa2ZyZWUoZW50 cmllcyk7CiAKIAlvcC0+dmFsdWUgPSByZXN1bHQ7Cg== --=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 Tue Feb 05 13:53:06 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 05 Feb 2013 13:53: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 1U2iwg-0004pq-P3; Tue, 05 Feb 2013 13:52:22 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U2PbM-00040K-Mj for xen-users@lists.xen.org; Mon, 04 Feb 2013 17:13:04 +0000 Received: from [85.158.143.99:51626] by server-1.bemta-4.messagelabs.com id D3/07-08839-02CEF015; Mon, 04 Feb 2013 17:13:04 +0000 X-Env-Sender: linuxhack2012@gmail.com X-Msg-Ref: server-7.tower-216.messagelabs.com!1359997982!24855525!1 X-Originating-IP: [209.85.128.41] 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.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 28528 invoked from network); 4 Feb 2013 17:13:03 -0000 Received: from mail-qe0-f41.google.com (HELO mail-qe0-f41.google.com) (209.85.128.41) by server-7.tower-216.messagelabs.com with RC4-SHA encrypted SMTP; 4 Feb 2013 17:13:03 -0000 Received: by mail-qe0-f41.google.com with SMTP id 7so2973697qeb.14 for ; Mon, 04 Feb 2013 09:13:02 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=eAUSdATK4QEnVwnNoYMKHTGn1R7HNPYFs5LNSgVDq5c=; b=Xdt2lK+rrfdLgu+nugtHO96dVVB8aVH0mh7/LOWrFFHyoq6+ZSZhgBkcHN5Z47a75O vT6/IadA6Aw9+Kt36N2/qxtoT5OP83ecB16MuNQZ/TJmPJA4VQb9Iuvgy1m85Ga8DYfg LDu8s7PQqo0+RgQL3ZMSl0VbNtbosztOOUUyaqBL59KJ2mnha/AcXGG8U9G2oq19Vp2e XYaSR5FCq1GEVoEWo9H9nzHFn5zA+08TJWYgcVici3nUX9/VPtxUYVNTgttU+HvyQZa1 3xqNS4eCUzoNgpsLstfy+YqRT9LZdM+XvX9CgrnCtQATH2f+toryi6koVwu6z6WUDagg VwlA== MIME-Version: 1.0 X-Received: by 10.224.182.70 with SMTP id cb6mr18251690qab.80.1359997981902; Mon, 04 Feb 2013 09:13:01 -0800 (PST) Received: by 10.49.52.66 with HTTP; Mon, 4 Feb 2013 09:13:01 -0800 (PST) In-Reply-To: <510FAFED.2010503@ts.fujitsu.com> References: <510F6165.9010908@ts.fujitsu.com> <510FAFED.2010503@ts.fujitsu.com> Date: Mon, 4 Feb 2013 22:43:01 +0530 Message-ID: From: Linux Hack To: Juergen Gross X-Mailman-Approved-At: Tue, 05 Feb 2013 13:52:21 +0000 Cc: "xen-users@lists.xen.org" Subject: Re: [Xen-users] xl cpupool X-BeenThere: xen-users@lists.xen.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="===============4439719739135478024==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============4439719739135478024== Content-Type: multipart/alternative; boundary=20cf303b41839b486204d4e93432 --20cf303b41839b486204d4e93432 Content-Type: text/plain; charset=ISO-8859-1 Ahh ok. Can you let me know what I need to modify on init script? On Monday, February 4, 2013, Juergen Gross wrote: > Am 04.02.2013 08:43, schrieb Linux Hack: >> >> Hi >> >> That's something interesting. Would it possible to make this work on xm >> or xl tool stack on xen version 3.4.4/4.1.4? > > 3.4.4: no (cpupools were introduced in 4.1) > > 4.1.4: yes. Please note, that xl is marked as "experimental" in 4.1. xm > should work. > > > Juergen > >> >> On Monday, February 4, 2013, Juergen Gross > > wrote: >> > Hi, >> > >> > Am 02.02.2013 00:53, schrieb Linux Hack: >> >> >> >> Hi, >> >> >> >> Would it possible to create cpupools with xl after the server boot and >> >> then assign one cpu-pool to dom0 and another one for dom-u's? >> > >> > Yes. >> > >> > You have to (assuming Xen 4.2): >> > >> > 1. remove cpus from Pool-0 with "xl cpupool-cpu-remove" >> > 2. reduce number of dom0 cpus to fit to reduced Pool-0 with "xl vcpu-set" >> > 3. create the domU cpupool with "xl cpupool-create" >> > 4. assign the free cpus to the new cpupool ("xl cpupool-cpu-add") >> > 5. create the domUs with "pool=" to start them in the new >> cpupool >> > (either in the config files of the domUs or as parameter of "xl >> create" >> > >> >> Also is there any change to make this work on server startup? >> > >> > You would have to add an init script in dom0. > > > -- > Juergen Gross Principal Developer Operating Systems > PBG PDG ES&S SWE OS6 Telephone: +49 (0) 89 3222 2967 > Fujitsu Technology Solutions e-mail: juergen.gross@ts.fujitsu.com > Domagkstr. 28 Internet: ts.fujitsu.com > D-80807 Muenchen Company details: ts.fujitsu.com/imprint.html > --20cf303b41839b486204d4e93432 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Ahh ok. Can you let me know what I need to modify on init script?

On= Monday, February 4, 2013, Juergen Gross <juergen.gross@ts.fujitsu.com> wrote:
> Am 04= .02.2013 08:43, schrieb Linux Hack:
>>
>> Hi
>>
>> That's something intere= sting. Would it possible to make this work on xm
>> or xl tool sta= ck on xen version 3.4.4/4.1.4?
>
> 3.4.4: no (cpupools were int= roduced in 4.1)
>
> 4.1.4: yes. Please note, that xl is marked as "experiment= al" in 4.1. xm
> =A0 =A0 =A0 =A0should work.
>
>
= > Juergen
>
>>
>> On Monday, February 4, 2013, J= uergen Gross <juergen.gr= oss@ts.fujitsu.com
>> <mailto:juergen= .gross@ts.fujitsu.com>> wrote:
>> =A0> Hi,
>>= ; =A0>
>> =A0> Am 02.02.2013 00:53, schrieb Linux Hack:
&= gt;> =A0>>
>> =A0>> Hi,
>> =A0>>
>> =A0>> Wo= uld it possible to create cpupools with xl after the server boot and
>= ;> =A0>> then assign one cpu-pool to dom0 and another one for dom-= u's?
>> =A0>
>> =A0> Yes.
>> =A0>
>> = =A0> You have to (assuming Xen 4.2):
>> =A0>
>> =A0= > 1. remove cpus from Pool-0 with "xl cpupool-cpu-remove"
&= gt;> =A0> 2. reduce number of dom0 cpus to fit to reduced Pool-0 with= "xl vcpu-set"
>> =A0> 3. create the domU cpupool with "xl cpupool-create&qu= ot;
>> =A0> 4. assign the free cpus to the new cpupool ("x= l cpupool-cpu-add")
>> =A0> 5. create the domUs with "= ;pool=3D<cpupool>" to start them in the new
>> cpupool
>> =A0> =A0 =A0(either in the config files of = the domUs or as parameter of "xl
>> create"
>> = =A0>
>> =A0>> Also is there any change to make this work = on server startup?
>> =A0>
>> =A0> You would have to add an init script i= n dom0.
>
>
> --
> Juergen Gross =A0 =A0 =A0 =A0 = =A0 =A0 =A0 =A0 Principal Developer Operating Systems
> PBG PDG ES&am= p;S SWE OS6 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 Telephone: +49 (0) 89 3222 = 2967
> Fujitsu Technology Solutions =A0 =A0 =A0 =A0 =A0 =A0 =A0e-mail: juergen.gross@ts.fujitsu.com<= br>> Domagkstr. 28 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 I= nternet: ts.fujitsu.com
> D-80807 Muenchen =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 Company details: ts.fujitsu.com/imprint.html<= br>> --20cf303b41839b486204d4e93432-- --===============4439719739135478024== 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 --===============4439719739135478024==-- From xen-users-bounces@lists.xen.org Tue Feb 05 13:53:06 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 05 Feb 2013 13:53: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 1U2iwg-0004pq-P3; Tue, 05 Feb 2013 13:52:22 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U2PbM-00040K-Mj for xen-users@lists.xen.org; Mon, 04 Feb 2013 17:13:04 +0000 Received: from [85.158.143.99:51626] by server-1.bemta-4.messagelabs.com id D3/07-08839-02CEF015; Mon, 04 Feb 2013 17:13:04 +0000 X-Env-Sender: linuxhack2012@gmail.com X-Msg-Ref: server-7.tower-216.messagelabs.com!1359997982!24855525!1 X-Originating-IP: [209.85.128.41] 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.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 28528 invoked from network); 4 Feb 2013 17:13:03 -0000 Received: from mail-qe0-f41.google.com (HELO mail-qe0-f41.google.com) (209.85.128.41) by server-7.tower-216.messagelabs.com with RC4-SHA encrypted SMTP; 4 Feb 2013 17:13:03 -0000 Received: by mail-qe0-f41.google.com with SMTP id 7so2973697qeb.14 for ; Mon, 04 Feb 2013 09:13:02 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=eAUSdATK4QEnVwnNoYMKHTGn1R7HNPYFs5LNSgVDq5c=; b=Xdt2lK+rrfdLgu+nugtHO96dVVB8aVH0mh7/LOWrFFHyoq6+ZSZhgBkcHN5Z47a75O vT6/IadA6Aw9+Kt36N2/qxtoT5OP83ecB16MuNQZ/TJmPJA4VQb9Iuvgy1m85Ga8DYfg LDu8s7PQqo0+RgQL3ZMSl0VbNtbosztOOUUyaqBL59KJ2mnha/AcXGG8U9G2oq19Vp2e XYaSR5FCq1GEVoEWo9H9nzHFn5zA+08TJWYgcVici3nUX9/VPtxUYVNTgttU+HvyQZa1 3xqNS4eCUzoNgpsLstfy+YqRT9LZdM+XvX9CgrnCtQATH2f+toryi6koVwu6z6WUDagg VwlA== MIME-Version: 1.0 X-Received: by 10.224.182.70 with SMTP id cb6mr18251690qab.80.1359997981902; Mon, 04 Feb 2013 09:13:01 -0800 (PST) Received: by 10.49.52.66 with HTTP; Mon, 4 Feb 2013 09:13:01 -0800 (PST) In-Reply-To: <510FAFED.2010503@ts.fujitsu.com> References: <510F6165.9010908@ts.fujitsu.com> <510FAFED.2010503@ts.fujitsu.com> Date: Mon, 4 Feb 2013 22:43:01 +0530 Message-ID: From: Linux Hack To: Juergen Gross X-Mailman-Approved-At: Tue, 05 Feb 2013 13:52:21 +0000 Cc: "xen-users@lists.xen.org" Subject: Re: [Xen-users] xl cpupool X-BeenThere: xen-users@lists.xen.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="===============4439719739135478024==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============4439719739135478024== Content-Type: multipart/alternative; boundary=20cf303b41839b486204d4e93432 --20cf303b41839b486204d4e93432 Content-Type: text/plain; charset=ISO-8859-1 Ahh ok. Can you let me know what I need to modify on init script? On Monday, February 4, 2013, Juergen Gross wrote: > Am 04.02.2013 08:43, schrieb Linux Hack: >> >> Hi >> >> That's something interesting. Would it possible to make this work on xm >> or xl tool stack on xen version 3.4.4/4.1.4? > > 3.4.4: no (cpupools were introduced in 4.1) > > 4.1.4: yes. Please note, that xl is marked as "experimental" in 4.1. xm > should work. > > > Juergen > >> >> On Monday, February 4, 2013, Juergen Gross > > wrote: >> > Hi, >> > >> > Am 02.02.2013 00:53, schrieb Linux Hack: >> >> >> >> Hi, >> >> >> >> Would it possible to create cpupools with xl after the server boot and >> >> then assign one cpu-pool to dom0 and another one for dom-u's? >> > >> > Yes. >> > >> > You have to (assuming Xen 4.2): >> > >> > 1. remove cpus from Pool-0 with "xl cpupool-cpu-remove" >> > 2. reduce number of dom0 cpus to fit to reduced Pool-0 with "xl vcpu-set" >> > 3. create the domU cpupool with "xl cpupool-create" >> > 4. assign the free cpus to the new cpupool ("xl cpupool-cpu-add") >> > 5. create the domUs with "pool=" to start them in the new >> cpupool >> > (either in the config files of the domUs or as parameter of "xl >> create" >> > >> >> Also is there any change to make this work on server startup? >> > >> > You would have to add an init script in dom0. > > > -- > Juergen Gross Principal Developer Operating Systems > PBG PDG ES&S SWE OS6 Telephone: +49 (0) 89 3222 2967 > Fujitsu Technology Solutions e-mail: juergen.gross@ts.fujitsu.com > Domagkstr. 28 Internet: ts.fujitsu.com > D-80807 Muenchen Company details: ts.fujitsu.com/imprint.html > --20cf303b41839b486204d4e93432 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Ahh ok. Can you let me know what I need to modify on init script?

On= Monday, February 4, 2013, Juergen Gross <juergen.gross@ts.fujitsu.com> wrote:
> Am 04= .02.2013 08:43, schrieb Linux Hack:
>>
>> Hi
>>
>> That's something intere= sting. Would it possible to make this work on xm
>> or xl tool sta= ck on xen version 3.4.4/4.1.4?
>
> 3.4.4: no (cpupools were int= roduced in 4.1)
>
> 4.1.4: yes. Please note, that xl is marked as "experiment= al" in 4.1. xm
> =A0 =A0 =A0 =A0should work.
>
>
= > Juergen
>
>>
>> On Monday, February 4, 2013, J= uergen Gross <juergen.gr= oss@ts.fujitsu.com
>> <mailto:juergen= .gross@ts.fujitsu.com>> wrote:
>> =A0> Hi,
>>= ; =A0>
>> =A0> Am 02.02.2013 00:53, schrieb Linux Hack:
&= gt;> =A0>>
>> =A0>> Hi,
>> =A0>>
>> =A0>> Wo= uld it possible to create cpupools with xl after the server boot and
>= ;> =A0>> then assign one cpu-pool to dom0 and another one for dom-= u's?
>> =A0>
>> =A0> Yes.
>> =A0>
>> = =A0> You have to (assuming Xen 4.2):
>> =A0>
>> =A0= > 1. remove cpus from Pool-0 with "xl cpupool-cpu-remove"
&= gt;> =A0> 2. reduce number of dom0 cpus to fit to reduced Pool-0 with= "xl vcpu-set"
>> =A0> 3. create the domU cpupool with "xl cpupool-create&qu= ot;
>> =A0> 4. assign the free cpus to the new cpupool ("x= l cpupool-cpu-add")
>> =A0> 5. create the domUs with "= ;pool=3D<cpupool>" to start them in the new
>> cpupool
>> =A0> =A0 =A0(either in the config files of = the domUs or as parameter of "xl
>> create"
>> = =A0>
>> =A0>> Also is there any change to make this work = on server startup?
>> =A0>
>> =A0> You would have to add an init script i= n dom0.
>
>
> --
> Juergen Gross =A0 =A0 =A0 =A0 = =A0 =A0 =A0 =A0 Principal Developer Operating Systems
> PBG PDG ES&am= p;S SWE OS6 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 Telephone: +49 (0) 89 3222 = 2967
> Fujitsu Technology Solutions =A0 =A0 =A0 =A0 =A0 =A0 =A0e-mail: juergen.gross@ts.fujitsu.com<= br>> Domagkstr. 28 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 I= nternet: ts.fujitsu.com
> D-80807 Muenchen =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 Company details: ts.fujitsu.com/imprint.html<= br>> --20cf303b41839b486204d4e93432-- --===============4439719739135478024== 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 --===============4439719739135478024==-- From xen-users-bounces@lists.xen.org Tue Feb 05 14:44:57 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 05 Feb 2013 14: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 1U2jkS-00075O-5M; Tue, 05 Feb 2013 14: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 1U2j9O-0005aq-3V for xen-users@lists.xen.org; Tue, 05 Feb 2013 14:05:30 +0000 Received: from [85.158.138.51:31373] by server-1.bemta-3.messagelabs.com id A5/73-08955-9A111115; Tue, 05 Feb 2013 14:05:29 +0000 X-Env-Sender: linuxhack2012@gmail.com X-Msg-Ref: server-13.tower-174.messagelabs.com!1360073116!12363051!1 X-Originating-IP: [209.85.216.173] X-SpamReason: No, hits=1.2 required=7.0 tests=BODY_RANDOM_LONG, 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.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 16872 invoked from network); 5 Feb 2013 14:05:18 -0000 Received: from mail-qc0-f173.google.com (HELO mail-qc0-f173.google.com) (209.85.216.173) by server-13.tower-174.messagelabs.com with RC4-SHA encrypted SMTP; 5 Feb 2013 14:05:18 -0000 Received: by mail-qc0-f173.google.com with SMTP id b12so65777qca.32 for ; Tue, 05 Feb 2013 06:05:15 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=Hf/Q6rdNtmfC1hPXHlNkc8bJP7zlWDClTDZm1obJFII=; b=FZxhCEtzM4ZvjaW6jSVPc7MdLqLeyVOKA11N961xEbmBvjxkzoigDPOoeSxBTIqibx 7bmUA6T6lOAPoml4Fj4zOgD++C0WG7O5xqfeeAAQX1eWi5WSh3InpTDuQVE+vMyWzht0 o/3KTF89f4pdlcfm5zrCcpjhfHTqS56x/ZR/h3j2ICn2QUKBxSbwWFIClLsIlE78UkAS xw8/rAZEvfK/L4OztyCJiJ+NiDN62cSdcDTMdi1WNfcG5xW0OkTenLcqKtS783oQ3nCH crgIoZHQNmLf/5eFkgJyw6Btr+p6ucge1tGbVv3/b7izMQgW+O2nRc1VwsMB01oknEYn pL8A== MIME-Version: 1.0 X-Received: by 10.224.31.16 with SMTP id w16mr19105071qac.52.1360073115821; Tue, 05 Feb 2013 06:05:15 -0800 (PST) Received: by 10.49.52.66 with HTTP; Tue, 5 Feb 2013 06:05:15 -0800 (PST) In-Reply-To: References: <510F6165.9010908@ts.fujitsu.com> <510FAFED.2010503@ts.fujitsu.com> Date: Tue, 5 Feb 2013 19:35:15 +0530 Message-ID: From: Linux Hack To: Juergen Gross X-Mailman-Approved-At: Tue, 05 Feb 2013 14:43:46 +0000 Cc: "xen-users@lists.xen.org" Subject: Re: [Xen-users] xl cpupool X-BeenThere: xen-users@lists.xen.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="===============0462602268058627870==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============0462602268058627870== Content-Type: multipart/alternative; boundary=20cf3074b456efe6b104d4fab293 --20cf3074b456efe6b104d4fab293 Content-Type: text/plain; charset=ISO-8859-1 Hi Can anyone give me detail how to make cpupool work with init scripts? On Monday, February 4, 2013, Linux Hack wrote: > Ahh ok. Can you let me know what I need to modify on init script? > > On Monday, February 4, 2013, Juergen Gross wrote: >> Am 04.02.2013 08:43, schrieb Linux Hack: >>> >>> Hi >>> >>> That's something interesting. Would it possible to make this work on xm >>> or xl tool stack on xen version 3.4.4/4.1.4? >> >> 3.4.4: no (cpupools were introduced in 4.1) >> >> 4.1.4: yes. Please note, that xl is marked as "experimental" in 4.1. xm >> should work. >> >> >> Juergen >> >>> >>> On Monday, February 4, 2013, Juergen Gross >> > wrote: >>> > Hi, >>> > >>> > Am 02.02.2013 00:53, schrieb Linux Hack: >>> >> >>> >> Hi, >>> >> >>> >> Would it possible to create cpupools with xl after the server boot and >>> >> then assign one cpu-pool to dom0 and another one for dom-u's? >>> > >>> > Yes. >>> > >>> > You have to (assuming Xen 4.2): >>> > >>> > 1. remove cpus from Pool-0 with "xl cpupool-cpu-remove" >>> > 2. reduce number of dom0 cpus to fit to reduced Pool-0 with "xl vcpu-set" >>> > 3. create the domU cpupool with "xl cpupool-create" >>> > 4. assign the free cpus to the new cpupool ("xl cpupool-cpu-add") >>> > 5. create the domUs with "pool=" to start them in the new >>> cpupool >>> > (either in the config files of the domUs or as parameter of "xl >>> create" >>> > >>> >> Also is there any change to make this work on server startup? >>> > >>> > You would have to add an init script in dom0. >> >> >> -- >> Juergen Gross Principal Developer Operating Systems >> PBG PDG ES&S SWE OS6 Telephone: +49 (0) 89 3222 2967 >> Fujitsu Technology Solutions e-mail: juergen.gross@ts.fujitsu.com >> Domagkstr. 28 Internet: ts.fujitsu.com >> D-80807 Muenchen Company details: ts.fujitsu.com/imprint.html >> --20cf3074b456efe6b104d4fab293 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Hi

Can anyone give me detail how to make cpupool work with init scri= pts?

On Monday, February 4, 2013, Linux Hack <linuxhack2012@gmail.com> wrote:
> Ahh = ok. Can you let me know what I need to modify on init script?
>
> On Monday, February 4, 2013, Juergen Gross <juergen.gross@ts.fujitsu.com> wrote= :
>> Am 04.02.2013 08:43, schrieb Linux Hack:
>>>
>>> Hi
>>>
>>> That's something intere= sting. Would it possible to make this work on xm
>>> or xl tool= stack on xen version 3.4.4/4.1.4?
>>
>> 3.4.4: no (cpupo= ols were introduced in 4.1)
>>
>> 4.1.4: yes. Please note, that xl is marked as "ex= perimental" in 4.1. xm
>> =A0 =A0 =A0 =A0should work.
>= >
>>
>> Juergen
>>
>>>
>>= ;> On Monday, February 4, 2013, Juergen Gross <juergen.gross@ts.fujitsu.com
>>> <mailto:jue= rgen.gross@ts.fujitsu.com>> wrote:
>>> =A0> Hi,>>> =A0>
>>> =A0> Am 02.02.2013 00:53, schrieb = Linux Hack:
>>> =A0>>
>>> =A0>> Hi,
>>> = =A0>>
>>> =A0>> Would it possible to create cpupool= s with xl after the server boot and
>>> =A0>> then assign= one cpu-pool to dom0 and another one for dom-u's?
>>> =A0>
>>> =A0> Yes.
>>> =A0>>>> =A0> You have to (assuming Xen 4.2):
>>> =A0&= gt;
>>> =A0> 1. remove cpus from Pool-0 with "xl cpupoo= l-cpu-remove"
>>> =A0> 2. reduce number of dom0 cpus to fit to reduced Pool-0= with "xl vcpu-set"
>>> =A0> 3. create the domU cp= upool with "xl cpupool-create"
>>> =A0> 4. assign = the free cpus to the new cpupool ("xl cpupool-cpu-add")
>>> =A0> 5. create the domUs with "pool=3D<cpupool>&= quot; to start them in the new
>>> cpupool
>>> =A0&= gt; =A0 =A0(either in the config files of the domUs or as parameter of &quo= t;xl
>>> create"
>>> =A0>
>>> =A0>&g= t; Also is there any change to make this work on server startup?
>>= ;> =A0>
>>> =A0> You would have to add an init script = in dom0.
>>
>>
>> --
>> Juergen Gross =A0 =A0 =A0 = =A0 =A0 =A0 =A0 =A0 Principal Developer Operating Systems
>> PBG P= DG ES&S SWE OS6 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 Telephone: +49 (0) = 89 3222 2967
>> Fujitsu Technology Solutions =A0 =A0 =A0 =A0 =A0 = =A0 =A0e-mail: juergen.gros= s@ts.fujitsu.com
>> Domagkstr. 28 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = Internet: ts.fujitsu.com
>> = D-80807 Muenchen =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 Company details: ts.fujitsu.com/imprint.html
>> --20cf3074b456efe6b104d4fab293-- --===============0462602268058627870== 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 --===============0462602268058627870==-- From xen-users-bounces@lists.xen.org Tue Feb 05 14:44:57 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 05 Feb 2013 14: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 1U2jkS-00075O-5M; Tue, 05 Feb 2013 14: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 1U2j9O-0005aq-3V for xen-users@lists.xen.org; Tue, 05 Feb 2013 14:05:30 +0000 Received: from [85.158.138.51:31373] by server-1.bemta-3.messagelabs.com id A5/73-08955-9A111115; Tue, 05 Feb 2013 14:05:29 +0000 X-Env-Sender: linuxhack2012@gmail.com X-Msg-Ref: server-13.tower-174.messagelabs.com!1360073116!12363051!1 X-Originating-IP: [209.85.216.173] X-SpamReason: No, hits=1.2 required=7.0 tests=BODY_RANDOM_LONG, 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.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 16872 invoked from network); 5 Feb 2013 14:05:18 -0000 Received: from mail-qc0-f173.google.com (HELO mail-qc0-f173.google.com) (209.85.216.173) by server-13.tower-174.messagelabs.com with RC4-SHA encrypted SMTP; 5 Feb 2013 14:05:18 -0000 Received: by mail-qc0-f173.google.com with SMTP id b12so65777qca.32 for ; Tue, 05 Feb 2013 06:05:15 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=Hf/Q6rdNtmfC1hPXHlNkc8bJP7zlWDClTDZm1obJFII=; b=FZxhCEtzM4ZvjaW6jSVPc7MdLqLeyVOKA11N961xEbmBvjxkzoigDPOoeSxBTIqibx 7bmUA6T6lOAPoml4Fj4zOgD++C0WG7O5xqfeeAAQX1eWi5WSh3InpTDuQVE+vMyWzht0 o/3KTF89f4pdlcfm5zrCcpjhfHTqS56x/ZR/h3j2ICn2QUKBxSbwWFIClLsIlE78UkAS xw8/rAZEvfK/L4OztyCJiJ+NiDN62cSdcDTMdi1WNfcG5xW0OkTenLcqKtS783oQ3nCH crgIoZHQNmLf/5eFkgJyw6Btr+p6ucge1tGbVv3/b7izMQgW+O2nRc1VwsMB01oknEYn pL8A== MIME-Version: 1.0 X-Received: by 10.224.31.16 with SMTP id w16mr19105071qac.52.1360073115821; Tue, 05 Feb 2013 06:05:15 -0800 (PST) Received: by 10.49.52.66 with HTTP; Tue, 5 Feb 2013 06:05:15 -0800 (PST) In-Reply-To: References: <510F6165.9010908@ts.fujitsu.com> <510FAFED.2010503@ts.fujitsu.com> Date: Tue, 5 Feb 2013 19:35:15 +0530 Message-ID: From: Linux Hack To: Juergen Gross X-Mailman-Approved-At: Tue, 05 Feb 2013 14:43:46 +0000 Cc: "xen-users@lists.xen.org" Subject: Re: [Xen-users] xl cpupool X-BeenThere: xen-users@lists.xen.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="===============0462602268058627870==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============0462602268058627870== Content-Type: multipart/alternative; boundary=20cf3074b456efe6b104d4fab293 --20cf3074b456efe6b104d4fab293 Content-Type: text/plain; charset=ISO-8859-1 Hi Can anyone give me detail how to make cpupool work with init scripts? On Monday, February 4, 2013, Linux Hack wrote: > Ahh ok. Can you let me know what I need to modify on init script? > > On Monday, February 4, 2013, Juergen Gross wrote: >> Am 04.02.2013 08:43, schrieb Linux Hack: >>> >>> Hi >>> >>> That's something interesting. Would it possible to make this work on xm >>> or xl tool stack on xen version 3.4.4/4.1.4? >> >> 3.4.4: no (cpupools were introduced in 4.1) >> >> 4.1.4: yes. Please note, that xl is marked as "experimental" in 4.1. xm >> should work. >> >> >> Juergen >> >>> >>> On Monday, February 4, 2013, Juergen Gross >> > wrote: >>> > Hi, >>> > >>> > Am 02.02.2013 00:53, schrieb Linux Hack: >>> >> >>> >> Hi, >>> >> >>> >> Would it possible to create cpupools with xl after the server boot and >>> >> then assign one cpu-pool to dom0 and another one for dom-u's? >>> > >>> > Yes. >>> > >>> > You have to (assuming Xen 4.2): >>> > >>> > 1. remove cpus from Pool-0 with "xl cpupool-cpu-remove" >>> > 2. reduce number of dom0 cpus to fit to reduced Pool-0 with "xl vcpu-set" >>> > 3. create the domU cpupool with "xl cpupool-create" >>> > 4. assign the free cpus to the new cpupool ("xl cpupool-cpu-add") >>> > 5. create the domUs with "pool=" to start them in the new >>> cpupool >>> > (either in the config files of the domUs or as parameter of "xl >>> create" >>> > >>> >> Also is there any change to make this work on server startup? >>> > >>> > You would have to add an init script in dom0. >> >> >> -- >> Juergen Gross Principal Developer Operating Systems >> PBG PDG ES&S SWE OS6 Telephone: +49 (0) 89 3222 2967 >> Fujitsu Technology Solutions e-mail: juergen.gross@ts.fujitsu.com >> Domagkstr. 28 Internet: ts.fujitsu.com >> D-80807 Muenchen Company details: ts.fujitsu.com/imprint.html >> --20cf3074b456efe6b104d4fab293 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Hi

Can anyone give me detail how to make cpupool work with init scri= pts?

On Monday, February 4, 2013, Linux Hack <linuxhack2012@gmail.com> wrote:
> Ahh = ok. Can you let me know what I need to modify on init script?
>
> On Monday, February 4, 2013, Juergen Gross <juergen.gross@ts.fujitsu.com> wrote= :
>> Am 04.02.2013 08:43, schrieb Linux Hack:
>>>
>>> Hi
>>>
>>> That's something intere= sting. Would it possible to make this work on xm
>>> or xl tool= stack on xen version 3.4.4/4.1.4?
>>
>> 3.4.4: no (cpupo= ols were introduced in 4.1)
>>
>> 4.1.4: yes. Please note, that xl is marked as "ex= perimental" in 4.1. xm
>> =A0 =A0 =A0 =A0should work.
>= >
>>
>> Juergen
>>
>>>
>>= ;> On Monday, February 4, 2013, Juergen Gross <juergen.gross@ts.fujitsu.com
>>> <mailto:jue= rgen.gross@ts.fujitsu.com>> wrote:
>>> =A0> Hi,>>> =A0>
>>> =A0> Am 02.02.2013 00:53, schrieb = Linux Hack:
>>> =A0>>
>>> =A0>> Hi,
>>> = =A0>>
>>> =A0>> Would it possible to create cpupool= s with xl after the server boot and
>>> =A0>> then assign= one cpu-pool to dom0 and another one for dom-u's?
>>> =A0>
>>> =A0> Yes.
>>> =A0>>>> =A0> You have to (assuming Xen 4.2):
>>> =A0&= gt;
>>> =A0> 1. remove cpus from Pool-0 with "xl cpupoo= l-cpu-remove"
>>> =A0> 2. reduce number of dom0 cpus to fit to reduced Pool-0= with "xl vcpu-set"
>>> =A0> 3. create the domU cp= upool with "xl cpupool-create"
>>> =A0> 4. assign = the free cpus to the new cpupool ("xl cpupool-cpu-add")
>>> =A0> 5. create the domUs with "pool=3D<cpupool>&= quot; to start them in the new
>>> cpupool
>>> =A0&= gt; =A0 =A0(either in the config files of the domUs or as parameter of &quo= t;xl
>>> create"
>>> =A0>
>>> =A0>&g= t; Also is there any change to make this work on server startup?
>>= ;> =A0>
>>> =A0> You would have to add an init script = in dom0.
>>
>>
>> --
>> Juergen Gross =A0 =A0 =A0 = =A0 =A0 =A0 =A0 =A0 Principal Developer Operating Systems
>> PBG P= DG ES&S SWE OS6 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 Telephone: +49 (0) = 89 3222 2967
>> Fujitsu Technology Solutions =A0 =A0 =A0 =A0 =A0 = =A0 =A0e-mail: juergen.gros= s@ts.fujitsu.com
>> Domagkstr. 28 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = Internet: ts.fujitsu.com
>> = D-80807 Muenchen =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 Company details: ts.fujitsu.com/imprint.html
>> --20cf3074b456efe6b104d4fab293-- --===============0462602268058627870== 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 --===============0462602268058627870==-- From xen-users-bounces@lists.xen.org Tue Feb 05 15:00:56 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 05 Feb 2013 15:00: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 1U2k05-0007x0-VI; Tue, 05 Feb 2013 14:59:57 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U2k04-0007wu-DZ for xen-users@lists.xen.org; Tue, 05 Feb 2013 14:59:56 +0000 Received: from [85.158.139.83:45966] by server-16.bemta-5.messagelabs.com id 01/56-14948-B6E11115; Tue, 05 Feb 2013 14:59:55 +0000 X-Env-Sender: eduardohideo@gmail.com X-Msg-Ref: server-10.tower-182.messagelabs.com!1360076394!27825512!1 X-Originating-IP: [209.85.212.174] 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.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 27100 invoked from network); 5 Feb 2013 14:59:54 -0000 Received: from mail-wi0-f174.google.com (HELO mail-wi0-f174.google.com) (209.85.212.174) by server-10.tower-182.messagelabs.com with RC4-SHA encrypted SMTP; 5 Feb 2013 14:59:54 -0000 Received: by mail-wi0-f174.google.com with SMTP id hi8so3807423wib.13 for ; Tue, 05 Feb 2013 06:59:54 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:mime-version:from:date:message-id:subject:to :content-type; bh=zSptofkS8V+1R22UZWrpzcxhLUZ1yEvGKkmyjipTQaA=; b=HllDEJlnLrYx8I8LleqOFYMakOO5Gwidwd/qzIDa5hIpnrj613OJxMKMtaKwa3UK8e xFQQEjOIZb2nAUM4wulrfuzDgTjjCHQGBS2dYeYfzu8UT6ilp6Qj9AoGMjaaYEvuiXa2 j1IIzCsm6mR2vYAIKFrlSDlVoXgqDS/lHS9xbAtLAgjN8hYJVoYHdEfZGQ8tvIuFtMm3 wvyqC3QxXe0XNm9lOOUk6/d9M7a4DrotXkSlfOObXL6rWPYOmYafo0nIxQIkdX8QcEJr NVfGtg8sPk9YvaXOUoeLo6/XS+dkcFjMsLwJnMUHXVdJwIXnG2vkEpJ0NXPiOwm2W+Jg S8vA== X-Received: by 10.194.174.234 with SMTP id bv10mr43243585wjc.47.1360076394547; Tue, 05 Feb 2013 06:59:54 -0800 (PST) MIME-Version: 1.0 Received: by 10.227.28.32 with HTTP; Tue, 5 Feb 2013 06:59:34 -0800 (PST) From: Eduardo Kuroda Date: Tue, 5 Feb 2013 12:59:34 -0200 Message-ID: To: xen-users@lists.xen.org Subject: [Xen-users] pv driver with NAPI support X-BeenThere: xen-users@lists.xen.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="===============6367357859543738143==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============6367357859543738143== Content-Type: multipart/alternative; boundary=089e013d185c5d4a9c04d4fb7641 --089e013d185c5d4a9c04d4fb7641 Content-Type: text/plain; charset=UTF-8 hello, I tried using NAPI in pv network drivers, but i discovered that it don't supports NAPI (kernel 3.5.0-17, xen 4.3.1). I like to know if any version of pv driver supports NAPI regards Eduardo --089e013d185c5d4a9c04d4fb7641 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
hello,

I tried using NAPI in pv network = drivers, but i discovered that it don't supports NAPI (kernel 3.5.0-17,= xen 4.3.1).
=C2=A0
I like to know if any version of pv= driver=C2=A0supports=C2=A0NAPI

regards
Eduardo
--089e013d185c5d4a9c04d4fb7641-- --===============6367357859543738143== 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 --===============6367357859543738143==-- From xen-users-bounces@lists.xen.org Tue Feb 05 15:00:56 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 05 Feb 2013 15:00: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 1U2k05-0007x0-VI; Tue, 05 Feb 2013 14:59:57 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U2k04-0007wu-DZ for xen-users@lists.xen.org; Tue, 05 Feb 2013 14:59:56 +0000 Received: from [85.158.139.83:45966] by server-16.bemta-5.messagelabs.com id 01/56-14948-B6E11115; Tue, 05 Feb 2013 14:59:55 +0000 X-Env-Sender: eduardohideo@gmail.com X-Msg-Ref: server-10.tower-182.messagelabs.com!1360076394!27825512!1 X-Originating-IP: [209.85.212.174] 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.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 27100 invoked from network); 5 Feb 2013 14:59:54 -0000 Received: from mail-wi0-f174.google.com (HELO mail-wi0-f174.google.com) (209.85.212.174) by server-10.tower-182.messagelabs.com with RC4-SHA encrypted SMTP; 5 Feb 2013 14:59:54 -0000 Received: by mail-wi0-f174.google.com with SMTP id hi8so3807423wib.13 for ; Tue, 05 Feb 2013 06:59:54 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:mime-version:from:date:message-id:subject:to :content-type; bh=zSptofkS8V+1R22UZWrpzcxhLUZ1yEvGKkmyjipTQaA=; b=HllDEJlnLrYx8I8LleqOFYMakOO5Gwidwd/qzIDa5hIpnrj613OJxMKMtaKwa3UK8e xFQQEjOIZb2nAUM4wulrfuzDgTjjCHQGBS2dYeYfzu8UT6ilp6Qj9AoGMjaaYEvuiXa2 j1IIzCsm6mR2vYAIKFrlSDlVoXgqDS/lHS9xbAtLAgjN8hYJVoYHdEfZGQ8tvIuFtMm3 wvyqC3QxXe0XNm9lOOUk6/d9M7a4DrotXkSlfOObXL6rWPYOmYafo0nIxQIkdX8QcEJr NVfGtg8sPk9YvaXOUoeLo6/XS+dkcFjMsLwJnMUHXVdJwIXnG2vkEpJ0NXPiOwm2W+Jg S8vA== X-Received: by 10.194.174.234 with SMTP id bv10mr43243585wjc.47.1360076394547; Tue, 05 Feb 2013 06:59:54 -0800 (PST) MIME-Version: 1.0 Received: by 10.227.28.32 with HTTP; Tue, 5 Feb 2013 06:59:34 -0800 (PST) From: Eduardo Kuroda Date: Tue, 5 Feb 2013 12:59:34 -0200 Message-ID: To: xen-users@lists.xen.org Subject: [Xen-users] pv driver with NAPI support X-BeenThere: xen-users@lists.xen.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="===============6367357859543738143==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============6367357859543738143== Content-Type: multipart/alternative; boundary=089e013d185c5d4a9c04d4fb7641 --089e013d185c5d4a9c04d4fb7641 Content-Type: text/plain; charset=UTF-8 hello, I tried using NAPI in pv network drivers, but i discovered that it don't supports NAPI (kernel 3.5.0-17, xen 4.3.1). I like to know if any version of pv driver supports NAPI regards Eduardo --089e013d185c5d4a9c04d4fb7641 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
hello,

I tried using NAPI in pv network = drivers, but i discovered that it don't supports NAPI (kernel 3.5.0-17,= xen 4.3.1).
=C2=A0
I like to know if any version of pv= driver=C2=A0supports=C2=A0NAPI

regards
Eduardo
--089e013d185c5d4a9c04d4fb7641-- --===============6367357859543738143== 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 --===============6367357859543738143==-- From xen-users-bounces@lists.xen.org Tue Feb 05 15:10:27 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 05 Feb 2013 15: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 1U2k9V-0008KM-K5; Tue, 05 Feb 2013 15:09:41 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U2k9U-0008KG-R8 for xen-users@lists.xen.org; Tue, 05 Feb 2013 15:09:40 +0000 Received: from [193.109.254.147:59369] by server-4.bemta-14.messagelabs.com id E8/7C-20719-4B021115; Tue, 05 Feb 2013 15:09:40 +0000 X-Env-Sender: wei.liu2@citrix.com X-Msg-Ref: server-2.tower-27.messagelabs.com!1360076838!9088775!1 X-Originating-IP: [66.165.176.63] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjYuMTY1LjE3Ni42MyA9PiAzMDE2Mzg=\n X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 22106 invoked from network); 5 Feb 2013 15:07:19 -0000 Received: from smtp02.citrix.com (HELO SMTP02.CITRIX.COM) (66.165.176.63) by server-2.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 5 Feb 2013 15:07:19 -0000 X-IronPort-AV: E=Sophos;i="4.84,602,1355097600"; d="scan'208";a="6014224" Received: from accessns.citrite.net (HELO FTLPEX01CL01.citrite.net) ([10.9.154.239]) by FTLPIPO02.CITRIX.COM with ESMTP/TLS/AES128-SHA; 05 Feb 2013 15:07:13 +0000 Received: from ukmail1.uk.xensource.com (10.80.16.128) by smtprelay.citrix.com (10.13.107.78) with Microsoft SMTP Server id 14.2.318.1; Tue, 5 Feb 2013 10:07:13 -0500 Received: from zion.uk.xensource.com ([10.80.2.73]) by ukmail1.uk.xensource.com with esmtp (Exim 4.69) (envelope-from ) id 1U2k76-0004O0-SG; Tue, 05 Feb 2013 15:07:12 +0000 Message-ID: <1360076832.7477.142.camel@zion.uk.xensource.com> From: Wei Liu To: Eduardo Kuroda Date: Tue, 5 Feb 2013 15:07:12 +0000 In-Reply-To: References: X-Mailer: Evolution 3.6.2 (3.6.2-3.fc18) MIME-Version: 1.0 Cc: "xen-users@lists.xen.org" , wei.liu2@citrix.com Subject: Re: [Xen-users] pv driver with NAPI support X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: 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, 2013-02-05 at 14:59 +0000, Eduardo Kuroda wrote: > hello, > > > I tried using NAPI in pv network drivers, but i discovered that it > don't supports NAPI (kernel 3.5.0-17, xen 4.3.1). > > I like to know if any version of pv driver supports NAPI > Netfront already uses NAPI but netback does not. There was a experimental netback implementation with NAPI and other stuffs, but it is not yet ready for upstream. Just asking, what's the motivation for you to use NAPI? Do you see bottleneck in current implementation? Wei. > > regards > Eduardo _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Tue Feb 05 15:10:27 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 05 Feb 2013 15: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 1U2k9V-0008KM-K5; Tue, 05 Feb 2013 15:09:41 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U2k9U-0008KG-R8 for xen-users@lists.xen.org; Tue, 05 Feb 2013 15:09:40 +0000 Received: from [193.109.254.147:59369] by server-4.bemta-14.messagelabs.com id E8/7C-20719-4B021115; Tue, 05 Feb 2013 15:09:40 +0000 X-Env-Sender: wei.liu2@citrix.com X-Msg-Ref: server-2.tower-27.messagelabs.com!1360076838!9088775!1 X-Originating-IP: [66.165.176.63] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjYuMTY1LjE3Ni42MyA9PiAzMDE2Mzg=\n X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 22106 invoked from network); 5 Feb 2013 15:07:19 -0000 Received: from smtp02.citrix.com (HELO SMTP02.CITRIX.COM) (66.165.176.63) by server-2.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 5 Feb 2013 15:07:19 -0000 X-IronPort-AV: E=Sophos;i="4.84,602,1355097600"; d="scan'208";a="6014224" Received: from accessns.citrite.net (HELO FTLPEX01CL01.citrite.net) ([10.9.154.239]) by FTLPIPO02.CITRIX.COM with ESMTP/TLS/AES128-SHA; 05 Feb 2013 15:07:13 +0000 Received: from ukmail1.uk.xensource.com (10.80.16.128) by smtprelay.citrix.com (10.13.107.78) with Microsoft SMTP Server id 14.2.318.1; Tue, 5 Feb 2013 10:07:13 -0500 Received: from zion.uk.xensource.com ([10.80.2.73]) by ukmail1.uk.xensource.com with esmtp (Exim 4.69) (envelope-from ) id 1U2k76-0004O0-SG; Tue, 05 Feb 2013 15:07:12 +0000 Message-ID: <1360076832.7477.142.camel@zion.uk.xensource.com> From: Wei Liu To: Eduardo Kuroda Date: Tue, 5 Feb 2013 15:07:12 +0000 In-Reply-To: References: X-Mailer: Evolution 3.6.2 (3.6.2-3.fc18) MIME-Version: 1.0 Cc: "xen-users@lists.xen.org" , wei.liu2@citrix.com Subject: Re: [Xen-users] pv driver with NAPI support X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: 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, 2013-02-05 at 14:59 +0000, Eduardo Kuroda wrote: > hello, > > > I tried using NAPI in pv network drivers, but i discovered that it > don't supports NAPI (kernel 3.5.0-17, xen 4.3.1). > > I like to know if any version of pv driver supports NAPI > Netfront already uses NAPI but netback does not. There was a experimental netback implementation with NAPI and other stuffs, but it is not yet ready for upstream. Just asking, what's the motivation for you to use NAPI? Do you see bottleneck in current implementation? Wei. > > regards > Eduardo _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Tue Feb 05 15:22:43 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 05 Feb 2013 15:22: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 1U2kLF-0000p9-FM; Tue, 05 Feb 2013 15:21:49 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U2kLD-0000oy-Pi for xen-users@lists.xen.org; Tue, 05 Feb 2013 15:21:48 +0000 Received: from [85.158.137.99:6331] by server-12.bemta-3.messagelabs.com id 3A/F6-05889-68321115; Tue, 05 Feb 2013 15:21:42 +0000 X-Env-Sender: eduardohideo@gmail.com X-Msg-Ref: server-13.tower-217.messagelabs.com!1360077701!20112153!1 X-Originating-IP: [74.125.82.41] 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.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 14541 invoked from network); 5 Feb 2013 15:21:41 -0000 Received: from mail-wg0-f41.google.com (HELO mail-wg0-f41.google.com) (74.125.82.41) by server-13.tower-217.messagelabs.com with RC4-SHA encrypted SMTP; 5 Feb 2013 15:21:41 -0000 Received: by mail-wg0-f41.google.com with SMTP id ds1so4152792wgb.0 for ; Tue, 05 Feb 2013 07:21:41 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:mime-version:in-reply-to:references:from:date:message-id :subject:to:cc:content-type; bh=HqDFITuDNQWl8/kZNQWXnuwF0TjMVn/LJvkraVodMss=; b=N2CIiD5dAtXTB73Apu5gcp5r7pl+yot2yBMnJMAv3Ink6kQPQL+stS7SFRO7XufSHV t4KINcIskd8UmRCV8oLk3GSJxaajlMUVwwavKC8scoo18vWx+rCTglv1i3QLpEbMIEmm cSOPvgiF+99yXgZRzWrhh4MOiWQQHn2zeB3xv3+EBedNF7ns796fkb14bqstV3YGnD7B 9Y3DQKE3G540XPX8bHeV/T+XjnKW+hu/JuehJ4KbHq4KXdPEP2eZ9Ppq/1EiNNt7xEk7 LfKZ145z7CtgKXtWKo385kyBMPGKfsPI8rHwyqSAVJj2OtqrY91iMlSmDElm8t8I9O5c ybFA== X-Received: by 10.180.104.10 with SMTP id ga10mr17946755wib.23.1360077700949; Tue, 05 Feb 2013 07:21:40 -0800 (PST) MIME-Version: 1.0 Received: by 10.227.28.32 with HTTP; Tue, 5 Feb 2013 07:21:20 -0800 (PST) In-Reply-To: <1360076832.7477.142.camel@zion.uk.xensource.com> References: <1360076832.7477.142.camel@zion.uk.xensource.com> From: Eduardo Kuroda Date: Tue, 5 Feb 2013 13:21:20 -0200 Message-ID: To: Wei Liu Cc: "xen-users@lists.xen.org" Subject: Re: [Xen-users] pv driver with NAPI support X-BeenThere: xen-users@lists.xen.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="===============6388995559120865162==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============6388995559120865162== Content-Type: multipart/alternative; boundary=f46d04374a093b677a04d4fbc4e7 --f46d04374a093b677a04d4fbc4e7 Content-Type: text/plain; charset=UTF-8 Hi Wei, i'm doing experiments with interrupt coalescence trying to find good values that increase bandwidth and reduce the amount of interruptions On Tue, Feb 5, 2013 at 1:07 PM, Wei Liu wrote: > On Tue, 2013-02-05 at 14:59 +0000, Eduardo Kuroda wrote: > > hello, > > > > > > I tried using NAPI in pv network drivers, but i discovered that it > > don't supports NAPI (kernel 3.5.0-17, xen 4.3.1). > > > > I like to know if any version of pv driver supports NAPI > > > > Netfront already uses NAPI but netback does not. There was a > experimental netback implementation with NAPI and other stuffs, but it > is not yet ready for upstream. > > Just asking, what's the motivation for you to use NAPI? Do you see > bottleneck in current implementation? > > > Wei. > > > > > regards > > Eduardo > > > --f46d04374a093b677a04d4fbc4e7 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Hi Wei,

i'm doing experiments with interrupt coalesc= ence trying to find good values that increase bandwidth and reduce the amou= nt of interruptions

On Tue, Feb 5, 2013 a= t 1:07 PM, Wei Liu <wei.liu2@citrix.com> wrote:
On T= ue, 2013-02-05 at 14:59 +0000, Eduardo Kuroda wrote:
> hello,
>
>
> I tried using NAPI in pv network drivers, but i discovered that it
> don't supports NAPI (kernel 3.5.0-17, xen 4.3.1).
>
> I like to know if any version of pv driver supports NAPI
>

Netfront already uses NAPI but netback does not. There was a experimental netback implementation with NAPI and other stuffs, but it
is not yet ready for upstream.

Just asking, what's the motivation for you to use NAPI? Do you see
bottleneck in current implementation?


Wei.

>
> regards
> Eduardo



--f46d04374a093b677a04d4fbc4e7-- --===============6388995559120865162== 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 --===============6388995559120865162==-- From xen-users-bounces@lists.xen.org Tue Feb 05 15:22:43 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 05 Feb 2013 15:22: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 1U2kLF-0000p9-FM; Tue, 05 Feb 2013 15:21:49 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U2kLD-0000oy-Pi for xen-users@lists.xen.org; Tue, 05 Feb 2013 15:21:48 +0000 Received: from [85.158.137.99:6331] by server-12.bemta-3.messagelabs.com id 3A/F6-05889-68321115; Tue, 05 Feb 2013 15:21:42 +0000 X-Env-Sender: eduardohideo@gmail.com X-Msg-Ref: server-13.tower-217.messagelabs.com!1360077701!20112153!1 X-Originating-IP: [74.125.82.41] 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.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 14541 invoked from network); 5 Feb 2013 15:21:41 -0000 Received: from mail-wg0-f41.google.com (HELO mail-wg0-f41.google.com) (74.125.82.41) by server-13.tower-217.messagelabs.com with RC4-SHA encrypted SMTP; 5 Feb 2013 15:21:41 -0000 Received: by mail-wg0-f41.google.com with SMTP id ds1so4152792wgb.0 for ; Tue, 05 Feb 2013 07:21:41 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:mime-version:in-reply-to:references:from:date:message-id :subject:to:cc:content-type; bh=HqDFITuDNQWl8/kZNQWXnuwF0TjMVn/LJvkraVodMss=; b=N2CIiD5dAtXTB73Apu5gcp5r7pl+yot2yBMnJMAv3Ink6kQPQL+stS7SFRO7XufSHV t4KINcIskd8UmRCV8oLk3GSJxaajlMUVwwavKC8scoo18vWx+rCTglv1i3QLpEbMIEmm cSOPvgiF+99yXgZRzWrhh4MOiWQQHn2zeB3xv3+EBedNF7ns796fkb14bqstV3YGnD7B 9Y3DQKE3G540XPX8bHeV/T+XjnKW+hu/JuehJ4KbHq4KXdPEP2eZ9Ppq/1EiNNt7xEk7 LfKZ145z7CtgKXtWKo385kyBMPGKfsPI8rHwyqSAVJj2OtqrY91iMlSmDElm8t8I9O5c ybFA== X-Received: by 10.180.104.10 with SMTP id ga10mr17946755wib.23.1360077700949; Tue, 05 Feb 2013 07:21:40 -0800 (PST) MIME-Version: 1.0 Received: by 10.227.28.32 with HTTP; Tue, 5 Feb 2013 07:21:20 -0800 (PST) In-Reply-To: <1360076832.7477.142.camel@zion.uk.xensource.com> References: <1360076832.7477.142.camel@zion.uk.xensource.com> From: Eduardo Kuroda Date: Tue, 5 Feb 2013 13:21:20 -0200 Message-ID: To: Wei Liu Cc: "xen-users@lists.xen.org" Subject: Re: [Xen-users] pv driver with NAPI support X-BeenThere: xen-users@lists.xen.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="===============6388995559120865162==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============6388995559120865162== Content-Type: multipart/alternative; boundary=f46d04374a093b677a04d4fbc4e7 --f46d04374a093b677a04d4fbc4e7 Content-Type: text/plain; charset=UTF-8 Hi Wei, i'm doing experiments with interrupt coalescence trying to find good values that increase bandwidth and reduce the amount of interruptions On Tue, Feb 5, 2013 at 1:07 PM, Wei Liu wrote: > On Tue, 2013-02-05 at 14:59 +0000, Eduardo Kuroda wrote: > > hello, > > > > > > I tried using NAPI in pv network drivers, but i discovered that it > > don't supports NAPI (kernel 3.5.0-17, xen 4.3.1). > > > > I like to know if any version of pv driver supports NAPI > > > > Netfront already uses NAPI but netback does not. There was a > experimental netback implementation with NAPI and other stuffs, but it > is not yet ready for upstream. > > Just asking, what's the motivation for you to use NAPI? Do you see > bottleneck in current implementation? > > > Wei. > > > > > regards > > Eduardo > > > --f46d04374a093b677a04d4fbc4e7 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Hi Wei,

i'm doing experiments with interrupt coalesc= ence trying to find good values that increase bandwidth and reduce the amou= nt of interruptions

On Tue, Feb 5, 2013 a= t 1:07 PM, Wei Liu <wei.liu2@citrix.com> wrote:
On T= ue, 2013-02-05 at 14:59 +0000, Eduardo Kuroda wrote:
> hello,
>
>
> I tried using NAPI in pv network drivers, but i discovered that it
> don't supports NAPI (kernel 3.5.0-17, xen 4.3.1).
>
> I like to know if any version of pv driver supports NAPI
>

Netfront already uses NAPI but netback does not. There was a experimental netback implementation with NAPI and other stuffs, but it
is not yet ready for upstream.

Just asking, what's the motivation for you to use NAPI? Do you see
bottleneck in current implementation?


Wei.

>
> regards
> Eduardo



--f46d04374a093b677a04d4fbc4e7-- --===============6388995559120865162== 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 --===============6388995559120865162==-- From xen-users-bounces@lists.xen.org Tue Feb 05 17:01:23 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 05 Feb 2013 17:01: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 1U2lsO-00079d-KA; Tue, 05 Feb 2013 17:00:08 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U2lsM-00079R-PI for xen-users@lists.xen.org; Tue, 05 Feb 2013 17:00:07 +0000 Received: from [85.158.137.99:55230] by server-13.bemta-3.messagelabs.com id 22/95-20653-59A31115; Tue, 05 Feb 2013 17:00:05 +0000 X-Env-Sender: stephane.gaudiche@laposte.net X-Msg-Ref: server-15.tower-217.messagelabs.com!1360083604!17778464!1 X-Originating-IP: [193.253.67.231] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogMTkzLjI1My42Ny4yMzEgPT4gMjMwOTY=\n, ML_RADAR_SPEW_LINKS_14,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 18100 invoked from network); 5 Feb 2013 17:00:04 -0000 Received: from smtpout6.laposte.net (HELO smtpout.laposte.net) (193.253.67.231) by server-15.tower-217.messagelabs.com with SMTP; 5 Feb 2013 17:00:04 -0000 Received: from wwinf8212 ([10.99.54.223]) by mwinf8511-out with ME id wh041k00F4oxRQS03h04JV; Tue, 05 Feb 2013 18:00:04 +0100 Date: Tue, 05 Feb 2013 18:00:04 +0100 From: =?UTF-8?Q?St=C3=A9phane_GAUDICHE?= To: "xen-users@lists.xen.org" Message-ID: <2017004300.822629.1360083604486.JavaMail.www@wwinf8212> In-Reply-To: <1360068430.17017.72.camel@zakaz.uk.xensource.com> References: <1550996225.104330.1359653797051.JavaMail.www@wwinf8306> <1360068430.17017.72.camel@zakaz.uk.xensource.com> MIME-Version: 1.0 X-Originating-IP: [91.212.128.130] X-Wum-Nature: EMAIL-NATURE X-WUM-FROM: |~| X-WUM-TO: |~| X-WUM-REPLYTO: |~| Subject: Re: [Xen-users] Xen LVM reducing HVM MS Windows guest disk X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: =?UTF-8?Q?St=C3=A9phane_GAUDICHE?= List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============8104148716828567813==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============8104148716828567813== Content-Type: multipart/alternative; boundary="----=_Part_822628_1637405394.1360083604486" ------=_Part_822628_1637405394.1360083604486 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable > Message du 05/02/13 13:47 > De : "Ian Campbell" > A : "St=C3=A9phane GAUDICHE" > Copie =C3=A0 : "xen-users@lists.xen.org" > Objet : Re: [Xen-users] Xen LVM reducing HVM MS Windows guest disk > > On Thu, 2013-01-31 at 17:36 +0000, St=C3=A9phane GAUDICHE wrote: > > Hello list, > > > > I run xen 4.0 on a debian squeeze host with local lvm2 storage > > I've got HVM VMs (Microsoft Windows) with 2 drives (c: [OS] & D: > > [Data]), file system: NTFS > > I want to reduce the size of the D: drive of my HVMs. > > > > By reading several articles and howtos across web, > > 1- I backup datas first outside the XenHost > > 2- then from MSWindows guest-OS, I managed to live-reduce the > > partition's size on the D: drive (from 150G to 50G) with the embedded > > tool "diskpart": "shrink" operator, it worked just fine. > > 3- I power off the HVM. > > Now, from xen point of view, i got a Logical Volume called > > data_HVM_microsoft.img of (steal) 150G. > > 4- I was expecting to do an "lvreduce" to reduce the logical volume > > (the box) to 100G only > > Why 100GB if you are reducing to 50GB? Just to be large! ;) in case of... > > > but what happen to the filesystem (contenant in the box),which is seen > > as a D: drive from the HVM with a small 50G NTFS partition from now) > > Do I care about it? > > If you have reduced the filesystem within the guest to 50GB then only > the first 50GB of the device will be used, so you should be able to > safely reduce the LV. "the first 50GB" is a good news "you should be able to safely reduce" doesn't sound very good for me. > You'd want to be damned sure that you had indeed > reduced the filesystem to 50GB and not e.g. 50.1GB though, or else you > will end up truncating it. That's why I make it larger than less. > Note that resizing the filesystem in the guest will have no impact on > the size of the underlying virtual device, nor will it affect the size > of the LVM volume backing the device. I'm not sure if you were expecting > that it would. Quite evidente for me, non-sense if not. > > I note that the logical volume were seen as Block-device from xen host > > file-system (not sure, but i guess it quite nomal due to LVM). > > then > > 5-check lv > > 6-power on HVM > > 7-extend D: drive to 100G > > Why reduce to 50GB and then increase to 100GB? Just to be large! ;) in case of... > > > Can anyone help to understand if am I right by following these step? > > Well, they sound OK to me from a Xen POV. I'm not so familiar with the > Windows side of things. > > Perhaps you can experiment by taking an LVM snapshot of the device, > which would avoid the risk of trashing the device until you know what > the right procedure is. > > Ian. > > I think it's a part of my problem Linux people don't deal with Windows trou= ble, no mix happen cause it is no such transparent in W case. :( -- St=C3=A9phane Une messagerie gratuite, garantie =C3=A0 vie et des services en plus, =C3= =A7a vous tente ? Je cr=C3=A9e ma bo=C3=AEte mail www.laposte.net ------=_Part_822628_1637405394.1360083604486 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable




> Message du 05/02/13 13:47
> = De : "Ian Campbell"
> A : "Stéphane GAUDICHE= "
> Copie à : "xen-users@lists.xen.org"
> Objet : Re: [Xen-users] Xen LVM reducing HVM MS Windows guest disk>
> On Thu, 2013-01-31 at 17:36 +0000, Stéphane GAUDI= CHE wrote:
> > Hello list,
> >
> > I run = xen 4.0 on a debian squeeze host with local lvm2 storage
> > I'v= e got HVM VMs (Microsoft Windows) with 2 drives (c: [OS] & D:
>= > [Data]), file system: NTFS
> > I want to reduce the size o= f the D: drive of my HVMs.
> >
> > By reading severa= l articles and howtos across web,
> > 1- I backup datas first ou= tside the XenHost
> > 2- then from MSWindows guest-OS, I managed= to live-reduce the
> > partition's size on the D: drive (from 1= 50G to 50G) with the embedded
> > tool "diskpart": &qu= ot;shrink" operator, it worked just fine.
> > 3- I power of= f the HVM.
> > Now, from xen point of view, i got a Logical Volu= me called
> > data_HVM_microsoft.img of (steal) 150G.
> = > 4- I was expecting to do an "lvreduce" to reduce the logical= volume
> > (the box) to 100G only
>
> Why 100G= B if you are reducing to 50GB?

Just to be large! ;) in case of..= .

>
> > but what happen to the filesystem (conten= ant in the box),which is seen
> > as a D: drive from the HVM wit= h a small 50G NTFS partition from now)
> > Do I care about it?>
> If you have reduced the filesystem within the guest to = 50GB then only
> the first 50GB of the device will be used, so you = should be able to
> safely reduce the LV.

"the fi= rst 50GB" is a good news
"you should be able to safely redu= ce" doesn't sound very good for me.

> You'd want to be= damned sure that you had indeed
> reduced the filesystem to 50GB a= nd not e.g. 50.1GB though, or else you
> will end up truncating it.=

That's why I make it larger than less.

> Note t= hat resizing the filesystem in the guest will have no impact on
> t= he size of the underlying virtual device, nor will it affect the size
= > of the LVM volume backing the device. I'm not sure if you were expecti= ng
> that it would.

Quite evidente for me, non-sense if= not.

> > I note that the logical volume were seen as Blo= ck-device from xen host
> > file-system (not sure, but i guess i= t quite nomal due to LVM).
> > then
> > 5-check lv> > 6-power on HVM
> > 7-extend D: drive to 100G
&= gt;
> Why reduce to 50GB and then increase to 100GB?

Ju= st to be large! ;) in case of...

>
> > Can anyone= help to understand if am I right by following these step?
>
= > Well, they sound OK to me from a Xen POV. I'm not so familiar with the=
> Windows side of things.
>
> Perhaps you can exp= eriment by taking an LVM snapshot of the device,
> which would avoi= d the risk of trashing the device until you know what
> the right p= rocedure is.
>
> Ian.
>
>

I= think it's a part of my problem Linux people don't deal with Windows trou= ble, no mix happen cause it is no such transparent in W case. :(
-- Stéphane


3D""<= a> ------=_Part_822628_1637405394.1360083604486-- --===============8104148716828567813== 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 --===============8104148716828567813==-- From xen-users-bounces@lists.xen.org Tue Feb 05 17:01:23 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 05 Feb 2013 17:01: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 1U2lsO-00079d-KA; Tue, 05 Feb 2013 17:00:08 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U2lsM-00079R-PI for xen-users@lists.xen.org; Tue, 05 Feb 2013 17:00:07 +0000 Received: from [85.158.137.99:55230] by server-13.bemta-3.messagelabs.com id 22/95-20653-59A31115; Tue, 05 Feb 2013 17:00:05 +0000 X-Env-Sender: stephane.gaudiche@laposte.net X-Msg-Ref: server-15.tower-217.messagelabs.com!1360083604!17778464!1 X-Originating-IP: [193.253.67.231] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogMTkzLjI1My42Ny4yMzEgPT4gMjMwOTY=\n, ML_RADAR_SPEW_LINKS_14,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 18100 invoked from network); 5 Feb 2013 17:00:04 -0000 Received: from smtpout6.laposte.net (HELO smtpout.laposte.net) (193.253.67.231) by server-15.tower-217.messagelabs.com with SMTP; 5 Feb 2013 17:00:04 -0000 Received: from wwinf8212 ([10.99.54.223]) by mwinf8511-out with ME id wh041k00F4oxRQS03h04JV; Tue, 05 Feb 2013 18:00:04 +0100 Date: Tue, 05 Feb 2013 18:00:04 +0100 From: =?UTF-8?Q?St=C3=A9phane_GAUDICHE?= To: "xen-users@lists.xen.org" Message-ID: <2017004300.822629.1360083604486.JavaMail.www@wwinf8212> In-Reply-To: <1360068430.17017.72.camel@zakaz.uk.xensource.com> References: <1550996225.104330.1359653797051.JavaMail.www@wwinf8306> <1360068430.17017.72.camel@zakaz.uk.xensource.com> MIME-Version: 1.0 X-Originating-IP: [91.212.128.130] X-Wum-Nature: EMAIL-NATURE X-WUM-FROM: |~| X-WUM-TO: |~| X-WUM-REPLYTO: |~| Subject: Re: [Xen-users] Xen LVM reducing HVM MS Windows guest disk X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: =?UTF-8?Q?St=C3=A9phane_GAUDICHE?= List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============8104148716828567813==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============8104148716828567813== Content-Type: multipart/alternative; boundary="----=_Part_822628_1637405394.1360083604486" ------=_Part_822628_1637405394.1360083604486 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable > Message du 05/02/13 13:47 > De : "Ian Campbell" > A : "St=C3=A9phane GAUDICHE" > Copie =C3=A0 : "xen-users@lists.xen.org" > Objet : Re: [Xen-users] Xen LVM reducing HVM MS Windows guest disk > > On Thu, 2013-01-31 at 17:36 +0000, St=C3=A9phane GAUDICHE wrote: > > Hello list, > > > > I run xen 4.0 on a debian squeeze host with local lvm2 storage > > I've got HVM VMs (Microsoft Windows) with 2 drives (c: [OS] & D: > > [Data]), file system: NTFS > > I want to reduce the size of the D: drive of my HVMs. > > > > By reading several articles and howtos across web, > > 1- I backup datas first outside the XenHost > > 2- then from MSWindows guest-OS, I managed to live-reduce the > > partition's size on the D: drive (from 150G to 50G) with the embedded > > tool "diskpart": "shrink" operator, it worked just fine. > > 3- I power off the HVM. > > Now, from xen point of view, i got a Logical Volume called > > data_HVM_microsoft.img of (steal) 150G. > > 4- I was expecting to do an "lvreduce" to reduce the logical volume > > (the box) to 100G only > > Why 100GB if you are reducing to 50GB? Just to be large! ;) in case of... > > > but what happen to the filesystem (contenant in the box),which is seen > > as a D: drive from the HVM with a small 50G NTFS partition from now) > > Do I care about it? > > If you have reduced the filesystem within the guest to 50GB then only > the first 50GB of the device will be used, so you should be able to > safely reduce the LV. "the first 50GB" is a good news "you should be able to safely reduce" doesn't sound very good for me. > You'd want to be damned sure that you had indeed > reduced the filesystem to 50GB and not e.g. 50.1GB though, or else you > will end up truncating it. That's why I make it larger than less. > Note that resizing the filesystem in the guest will have no impact on > the size of the underlying virtual device, nor will it affect the size > of the LVM volume backing the device. I'm not sure if you were expecting > that it would. Quite evidente for me, non-sense if not. > > I note that the logical volume were seen as Block-device from xen host > > file-system (not sure, but i guess it quite nomal due to LVM). > > then > > 5-check lv > > 6-power on HVM > > 7-extend D: drive to 100G > > Why reduce to 50GB and then increase to 100GB? Just to be large! ;) in case of... > > > Can anyone help to understand if am I right by following these step? > > Well, they sound OK to me from a Xen POV. I'm not so familiar with the > Windows side of things. > > Perhaps you can experiment by taking an LVM snapshot of the device, > which would avoid the risk of trashing the device until you know what > the right procedure is. > > Ian. > > I think it's a part of my problem Linux people don't deal with Windows trou= ble, no mix happen cause it is no such transparent in W case. :( -- St=C3=A9phane Une messagerie gratuite, garantie =C3=A0 vie et des services en plus, =C3= =A7a vous tente ? Je cr=C3=A9e ma bo=C3=AEte mail www.laposte.net ------=_Part_822628_1637405394.1360083604486 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable




> Message du 05/02/13 13:47
> = De : "Ian Campbell"
> A : "Stéphane GAUDICHE= "
> Copie à : "xen-users@lists.xen.org"
> Objet : Re: [Xen-users] Xen LVM reducing HVM MS Windows guest disk>
> On Thu, 2013-01-31 at 17:36 +0000, Stéphane GAUDI= CHE wrote:
> > Hello list,
> >
> > I run = xen 4.0 on a debian squeeze host with local lvm2 storage
> > I'v= e got HVM VMs (Microsoft Windows) with 2 drives (c: [OS] & D:
>= > [Data]), file system: NTFS
> > I want to reduce the size o= f the D: drive of my HVMs.
> >
> > By reading severa= l articles and howtos across web,
> > 1- I backup datas first ou= tside the XenHost
> > 2- then from MSWindows guest-OS, I managed= to live-reduce the
> > partition's size on the D: drive (from 1= 50G to 50G) with the embedded
> > tool "diskpart": &qu= ot;shrink" operator, it worked just fine.
> > 3- I power of= f the HVM.
> > Now, from xen point of view, i got a Logical Volu= me called
> > data_HVM_microsoft.img of (steal) 150G.
> = > 4- I was expecting to do an "lvreduce" to reduce the logical= volume
> > (the box) to 100G only
>
> Why 100G= B if you are reducing to 50GB?

Just to be large! ;) in case of..= .

>
> > but what happen to the filesystem (conten= ant in the box),which is seen
> > as a D: drive from the HVM wit= h a small 50G NTFS partition from now)
> > Do I care about it?>
> If you have reduced the filesystem within the guest to = 50GB then only
> the first 50GB of the device will be used, so you = should be able to
> safely reduce the LV.

"the fi= rst 50GB" is a good news
"you should be able to safely redu= ce" doesn't sound very good for me.

> You'd want to be= damned sure that you had indeed
> reduced the filesystem to 50GB a= nd not e.g. 50.1GB though, or else you
> will end up truncating it.=

That's why I make it larger than less.

> Note t= hat resizing the filesystem in the guest will have no impact on
> t= he size of the underlying virtual device, nor will it affect the size
= > of the LVM volume backing the device. I'm not sure if you were expecti= ng
> that it would.

Quite evidente for me, non-sense if= not.

> > I note that the logical volume were seen as Blo= ck-device from xen host
> > file-system (not sure, but i guess i= t quite nomal due to LVM).
> > then
> > 5-check lv> > 6-power on HVM
> > 7-extend D: drive to 100G
&= gt;
> Why reduce to 50GB and then increase to 100GB?

Ju= st to be large! ;) in case of...

>
> > Can anyone= help to understand if am I right by following these step?
>
= > Well, they sound OK to me from a Xen POV. I'm not so familiar with the=
> Windows side of things.
>
> Perhaps you can exp= eriment by taking an LVM snapshot of the device,
> which would avoi= d the risk of trashing the device until you know what
> the right p= rocedure is.
>
> Ian.
>
>

I= think it's a part of my problem Linux people don't deal with Windows trou= ble, no mix happen cause it is no such transparent in W case. :(
-- Stéphane


3D""<= a> ------=_Part_822628_1637405394.1360083604486-- --===============8104148716828567813== 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 --===============8104148716828567813==-- From xen-users-bounces@lists.xen.org Tue Feb 05 17:15:18 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 05 Feb 2013 17:15: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 1U2m69-0008Ot-Ni; Tue, 05 Feb 2013 17:14:21 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U2m68-0008Om-BI for xen-users@lists.xen.org; Tue, 05 Feb 2013 17:14:20 +0000 Received: from [193.109.254.147:21288] by server-4.bemta-14.messagelabs.com id A3/13-20719-BED31115; Tue, 05 Feb 2013 17:14:19 +0000 X-Env-Sender: paul@stimpsonfamily.co.uk X-Msg-Ref: server-14.tower-27.messagelabs.com!1360084455!4074036!1 X-Originating-IP: [94.136.40.61] X-SpamReason: No, hits=0.5 required=7.0 tests=sa_preprocessor: QmFkIElQOiA5NC4xMzYuNDAuNjEgPT4gNTcxODQ=\n,sa_preprocessor: QmFkIElQOiA5NC4xMzYuNDAuNjEgPT4gNTcxODQ=\n,BODY_RANDOM_LONG X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 5113 invoked from network); 5 Feb 2013 17:14:16 -0000 Received: from mailex.mailcore.me (HELO mailex.mailcore.me) (94.136.40.61) by server-14.tower-27.messagelabs.com with SMTP; 5 Feb 2013 17:14:16 -0000 Received: from [192.165.210.4] (helo=[192.168.225.223]) by mail11.atlas.pipex.net with esmtpa (Exim 4.71) (envelope-from ) id 1U2m63-0006dC-E9; Tue, 05 Feb 2013 17:14:15 +0000 Message-ID: <51113DE5.6030705@stimpsonfamily.co.uk> Date: Tue, 05 Feb 2013 17:14:13 +0000 From: Paul Stimpson User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130106 Thunderbird/17.0.2 MIME-Version: 1.0 To: Ian Campbell References: <510BF806.2010504@stimpsonfamily.co.uk> <1359972462.5281.17.camel@zakaz.uk.xensource.com> In-Reply-To: <1359972462.5281.17.camel@zakaz.uk.xensource.com> X-Mailcore-Auth: 8324857 X-Mailcore-Domain: 844183 Cc: "xen-users@lists.xen.org" Subject: Re: [Xen-users] Guest not starting after hardware migration X-BeenThere: xen-users@lists.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 Ian, Thank you for your reply. On 04/02/13 10:07, Ian Campbell wrote: > On Fri, 2013-02-01 at 17:14 +0000, Paul Stimpson wrote: > >> The machine looks like it boots OK and the host and Linux guest start >> fine. The Windows VM steadfastly refuses to boot and if I do an xl >> create on it, I get the following messages: >> >> libxl: error: libxl_create.c:420:libxl_domain_make: domain creation fail >> libxl: error: libxl_create.c:646:initiate_domain_create: cannot make domain: -3 > This seems to correspond to -ESRCH from xc_domain_create. > >> libxl: error: libxl.c:1392:libxl__destroy_domid: non-existant domain -1 >> libxl: error: libxl.c:1356:domain_destrpy_callback: unable to destroy guest with domid 4294967295 >> libxl: error: libxl_create.c:1152:domcreate_destruction_cb: unable to destroy domain 4294967295 following failed creation >> >> These errors don't seem to contain any useful information to me > "xl -vvv create ..." might give you some more information, or you might > see some useful messages in "xl dmesg". It might be useful to see the > complete logs in case something interesting is hidden there. It seems to go south fairly early on: > libxl: debug: libxl_create.c:1173:do_domain_create: ao 0x10b49a0: > create: how=(nil) callback=(nil) poller=0x10b4920 > libxl: error: libxl_create.c:420:libxl__domain_make: domain creation fail > libxl: error: libxl_create.c:646:initiate_domain_create: cannot make > domain: -3 > libxl: error: libxl.c:1392:libxl__destroy_domid: non-existant domain -1 > libxl: error: libxl.c:1356:domain_destroy_callback: unable to destroy > guest with domid 4294967295 > libxl: error: libxl_create.c:1152:domcreate_destruction_cb: unable to > destroy domain 4294967295 following failed creation > libxl: debug: libxl_event.c:1497:libxl__ao_complete: ao 0x10b49a0: > complete, rc=-3 > libxl: debug: libxl_create.c:1186:do_domain_create: ao 0x10b49a0: > inprogress: poller=0x10b4920, flags=ic > libxl: debug: libxl_event.c:1469:libxl__ao__destroy: ao 0x10b49a0: destroy > xc: debug: hypercall buffer: total allocations:5 total releases:5 > xc: debug: hypercall buffer: current allocations:0 maximum allocations:2 > xc: debug: hypercall buffer: cache current size:2 > xc: debug: hypercall buffer: cache hits:3 misses:2 toobig:0 > What does your guest configuration file contain? > > builder = "hvm" > name = "GUEST-Windows" > memory = 2048 > #vcpus = 7 > #cpus = "1,2,3,4,5,6,7" > disk = > ['phy:/dev/VolGroup00/LogVol03,hda,w','phy:/dev/DataVG/WindowsData,hdb,w'] > vif = ['bridge=xenbr0,ip=192.168.73.20'] > pci = ['01:00.00'] > usbdevice = "tablet" > vnc = 1 > vnclisten = "0.0.0.0" > vncpassword = "REDACTED" I commented the CPU allocations in the conf files and in /etc/default/grub out (and did an update-grub) since the recipient machine doesn't have hyperthreading and therefore only seems to have half the number of cores the source machine had. I also tried modding the conf file to make a new one with the Windows DVD mounted to try a reinstall. That also failed to launch. Comparison of the CPUs is here: http://www.cpu-world.com/Compare/825/Intel_Xeon_E5620_vs_Intel_Xeon_X3430.html The source machine has the E5620 and the destination the X3430. The source is an HP DL180G6 and the destination an original Dell Poweredge R210. My thoughts are that possible explanations could be: * The CPU or the chipset on the Dell is missing some feature that is expected. * The number of cores is coded somewhere I haven't found (I didn't build the image) and the box only having 4 cores is preventing the whole thing from starting. * Something about Windows is self-destructing milliseconds after launch (but that version of Windows from that DVD is known to run on the Dell native). * Some driver the Dell needs is missing. * Compiling Xen 4.2.0 on the source machine to the stock Ubuntu 12.04-x64 kernel and moving it produces a kernel that is somehow unacceptable on the Dell. Thanks again for your help. Paul. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Tue Feb 05 17:15:18 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 05 Feb 2013 17:15: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 1U2m69-0008Ot-Ni; Tue, 05 Feb 2013 17:14:21 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U2m68-0008Om-BI for xen-users@lists.xen.org; Tue, 05 Feb 2013 17:14:20 +0000 Received: from [193.109.254.147:21288] by server-4.bemta-14.messagelabs.com id A3/13-20719-BED31115; Tue, 05 Feb 2013 17:14:19 +0000 X-Env-Sender: paul@stimpsonfamily.co.uk X-Msg-Ref: server-14.tower-27.messagelabs.com!1360084455!4074036!1 X-Originating-IP: [94.136.40.61] X-SpamReason: No, hits=0.5 required=7.0 tests=sa_preprocessor: QmFkIElQOiA5NC4xMzYuNDAuNjEgPT4gNTcxODQ=\n,sa_preprocessor: QmFkIElQOiA5NC4xMzYuNDAuNjEgPT4gNTcxODQ=\n,BODY_RANDOM_LONG X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 5113 invoked from network); 5 Feb 2013 17:14:16 -0000 Received: from mailex.mailcore.me (HELO mailex.mailcore.me) (94.136.40.61) by server-14.tower-27.messagelabs.com with SMTP; 5 Feb 2013 17:14:16 -0000 Received: from [192.165.210.4] (helo=[192.168.225.223]) by mail11.atlas.pipex.net with esmtpa (Exim 4.71) (envelope-from ) id 1U2m63-0006dC-E9; Tue, 05 Feb 2013 17:14:15 +0000 Message-ID: <51113DE5.6030705@stimpsonfamily.co.uk> Date: Tue, 05 Feb 2013 17:14:13 +0000 From: Paul Stimpson User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130106 Thunderbird/17.0.2 MIME-Version: 1.0 To: Ian Campbell References: <510BF806.2010504@stimpsonfamily.co.uk> <1359972462.5281.17.camel@zakaz.uk.xensource.com> In-Reply-To: <1359972462.5281.17.camel@zakaz.uk.xensource.com> X-Mailcore-Auth: 8324857 X-Mailcore-Domain: 844183 Cc: "xen-users@lists.xen.org" Subject: Re: [Xen-users] Guest not starting after hardware migration X-BeenThere: xen-users@lists.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 Ian, Thank you for your reply. On 04/02/13 10:07, Ian Campbell wrote: > On Fri, 2013-02-01 at 17:14 +0000, Paul Stimpson wrote: > >> The machine looks like it boots OK and the host and Linux guest start >> fine. The Windows VM steadfastly refuses to boot and if I do an xl >> create on it, I get the following messages: >> >> libxl: error: libxl_create.c:420:libxl_domain_make: domain creation fail >> libxl: error: libxl_create.c:646:initiate_domain_create: cannot make domain: -3 > This seems to correspond to -ESRCH from xc_domain_create. > >> libxl: error: libxl.c:1392:libxl__destroy_domid: non-existant domain -1 >> libxl: error: libxl.c:1356:domain_destrpy_callback: unable to destroy guest with domid 4294967295 >> libxl: error: libxl_create.c:1152:domcreate_destruction_cb: unable to destroy domain 4294967295 following failed creation >> >> These errors don't seem to contain any useful information to me > "xl -vvv create ..." might give you some more information, or you might > see some useful messages in "xl dmesg". It might be useful to see the > complete logs in case something interesting is hidden there. It seems to go south fairly early on: > libxl: debug: libxl_create.c:1173:do_domain_create: ao 0x10b49a0: > create: how=(nil) callback=(nil) poller=0x10b4920 > libxl: error: libxl_create.c:420:libxl__domain_make: domain creation fail > libxl: error: libxl_create.c:646:initiate_domain_create: cannot make > domain: -3 > libxl: error: libxl.c:1392:libxl__destroy_domid: non-existant domain -1 > libxl: error: libxl.c:1356:domain_destroy_callback: unable to destroy > guest with domid 4294967295 > libxl: error: libxl_create.c:1152:domcreate_destruction_cb: unable to > destroy domain 4294967295 following failed creation > libxl: debug: libxl_event.c:1497:libxl__ao_complete: ao 0x10b49a0: > complete, rc=-3 > libxl: debug: libxl_create.c:1186:do_domain_create: ao 0x10b49a0: > inprogress: poller=0x10b4920, flags=ic > libxl: debug: libxl_event.c:1469:libxl__ao__destroy: ao 0x10b49a0: destroy > xc: debug: hypercall buffer: total allocations:5 total releases:5 > xc: debug: hypercall buffer: current allocations:0 maximum allocations:2 > xc: debug: hypercall buffer: cache current size:2 > xc: debug: hypercall buffer: cache hits:3 misses:2 toobig:0 > What does your guest configuration file contain? > > builder = "hvm" > name = "GUEST-Windows" > memory = 2048 > #vcpus = 7 > #cpus = "1,2,3,4,5,6,7" > disk = > ['phy:/dev/VolGroup00/LogVol03,hda,w','phy:/dev/DataVG/WindowsData,hdb,w'] > vif = ['bridge=xenbr0,ip=192.168.73.20'] > pci = ['01:00.00'] > usbdevice = "tablet" > vnc = 1 > vnclisten = "0.0.0.0" > vncpassword = "REDACTED" I commented the CPU allocations in the conf files and in /etc/default/grub out (and did an update-grub) since the recipient machine doesn't have hyperthreading and therefore only seems to have half the number of cores the source machine had. I also tried modding the conf file to make a new one with the Windows DVD mounted to try a reinstall. That also failed to launch. Comparison of the CPUs is here: http://www.cpu-world.com/Compare/825/Intel_Xeon_E5620_vs_Intel_Xeon_X3430.html The source machine has the E5620 and the destination the X3430. The source is an HP DL180G6 and the destination an original Dell Poweredge R210. My thoughts are that possible explanations could be: * The CPU or the chipset on the Dell is missing some feature that is expected. * The number of cores is coded somewhere I haven't found (I didn't build the image) and the box only having 4 cores is preventing the whole thing from starting. * Something about Windows is self-destructing milliseconds after launch (but that version of Windows from that DVD is known to run on the Dell native). * Some driver the Dell needs is missing. * Compiling Xen 4.2.0 on the source machine to the stock Ubuntu 12.04-x64 kernel and moving it produces a kernel that is somehow unacceptable on the Dell. Thanks again for your help. Paul. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Tue Feb 05 17:15:33 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 05 Feb 2013 17:15: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 1U2m6R-0008Pk-Co; Tue, 05 Feb 2013 17:14:39 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U2m4H-0008IX-9g for xen-users@lists.xen.org; Tue, 05 Feb 2013 17:12:25 +0000 Received: from [193.109.254.147:17506] by server-8.bemta-14.messagelabs.com id F4/5C-17325-57D31115; Tue, 05 Feb 2013 17:12:21 +0000 X-Env-Sender: ydev@cs.utah.edu X-Msg-Ref: server-12.tower-27.messagelabs.com!1360084318!9322104!1 X-Originating-IP: [155.98.64.241] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 31903 invoked from network); 5 Feb 2013 17:11:59 -0000 Received: from mail-svr1.cs.utah.edu (HELO mail-svr1.cs.utah.edu) (155.98.64.241) by server-12.tower-27.messagelabs.com with SMTP; 5 Feb 2013 17:11:59 -0000 Received: from localhost (localhost [127.0.0.1]) by mail-svr1.cs.utah.edu (Postfix) with ESMTP id 237346500C9; Tue, 5 Feb 2013 10:11:58 -0700 (MST) X-Virus-Scanned: amavisd-new at cs.utah.edu Received: from mail-svr1.cs.utah.edu ([127.0.0.1]) by localhost (mail-svr1.cs.utah.edu [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 54LRjChKjYLO; Tue, 5 Feb 2013 10:11:57 -0700 (MST) Received: from [192.168.1.16] (c-76-23-15-81.hsd1.ut.comcast.net [76.23.15.81]) by smtps.cs.utah.edu (Postfix) with ESMTPSA id C73FA6500C8; Tue, 5 Feb 2013 10:11:56 -0700 (MST) Message-ID: <51113D59.7030003@cs.utah.edu> Date: Tue, 05 Feb 2013 10:11:53 -0700 From: Yathindra User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130107 Thunderbird/17.0.2 MIME-Version: 1.0 To: =?ISO-8859-1?Q?Roger_Pau_Monn=E9?= References: <510DC655.5060205@cs.utah.edu> <510E3195.1010004@citrix.com> <510EA374.6060509@cs.utah.edu> <5110D7EC.8040608@citrix.com> In-Reply-To: <5110D7EC.8040608@citrix.com> X-Mailman-Approved-At: Tue, 05 Feb 2013 17:14:38 +0000 Cc: "xen-users@lists.xen.org" Subject: Re: [Xen-users] xen_blkbk times out before getting connected X-BeenThere: xen-users@lists.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 DomU configuration file looks like this: kernel =3D "/boot/vmlinuz-3.8.0-rc5+" ramdisk =3D "/boot/initrd.img-3.8.0-rc5+" memory =3D 500 name =3D "guest2" disk =3D ['phy:/dev/loop0,sda1,w'] root =3D "/dev/disk/by-path/xen-vbd-2049 ro" extra =3D 'xencons=3Dtty' On 2/5/2013 2:59 AM, Roger Pau Monn=E9 wrote: > On 03/02/13 18:50, Yathindra wrote: >> I'm using the latest linux kernel 3.8.0 with Xen 4.3-unstable. Xenstored >> is being started at boot time. >> I did not see any message (dmesg/syslog/console) about device being >> plugged in but xenstore-ls shows me all >> the entries backend and frontend. > Could you post your DomU configuration file also? > >> Here are some details >> ------------------------------ >> From /var/log/syslog: >> >> Feb 3 10:37:31 localhost kernel: [ 36.466359] Event-channel device >> installed. >> Feb 3 10:37:31 localhost kernel: [ 36.636358] Register >> xen_blkbk_driver <<< custom debug message I added >> Feb 3 10:37:31 localhost kernel: [ 36.636367] >> xenbus_register_backend <<< custom debug message I added >> Feb 3 10:37:31 localhost kernel: [ 36.683533] xenbus_register_backend >> Feb 3 10:37:31 localhost kernel: [ 36.830115] xen-pciback: backend is >> vpci <<< custom debug message I added >> Feb 3 10:37:31 localhost kernel: [ 36.830123] >> xenbus_register_backend <<< custom debug message I added >> Feb 3 10:37:32 localhost xenstored: Checking store ... >> Feb 3 10:37:32 localhost xenstored: Checking store complete. >> Feb 3 10:37:32 localhost kernel: [ 37.075217] xenbus_probe: xenstored >> is ready <<< custom debug message I added >> Feb 3 10:37:32 localhost kernel: [ 37.075230] watching node >> FFFFFFFF81C7D1A0 >> Feb 3 10:37:32 localhost kernel: [ 37.081309] xenbus_scanf for node c= pu/0 >> Feb 3 10:37:32 localhost kernel: [ 37.081327] XENBUS xen store gave: >> unknown error cpu >> Feb 3 10:37:32 localhost kernel: [ 37.081333] xenbus_scanf for node c= pu/1 >> Feb 3 10:37:32 localhost kernel: [ 37.085327] XENBUS unexpected type >> [17], expected [2] >> Feb 3 10:37:32 localhost kernel: [ 37.085342] watching node >> FFFFFFFF81C7D0C0 >> Feb 3 10:37:32 localhost kernel: [ 37.086857] XENBUS unexpected type >> [17], expected [4] >> Feb 3 10:37:32 localhost kernel: [ 37.086865] Failed to set shutdown >> watcher >> Feb 3 10:37:32 localhost kernel: [ 37.086880] backend_probe_and_watch >> - enumerates devices in xenstore and watches for changes <<< custom >> debug message I added >> Feb 3 10:37:32 localhost kernel: [ 37.089401] XENBUS unexpected type >> [4], expected [1] >> Feb 3 10:37:32 localhost kernel: [ 37.089411] watching node >> FFFFFFFF81C7D660 >> Feb 3 10:37:32 localhost kernel: [ 37.090715] XENBUS xen store gave: >> unknown error control/shutdown >> Feb 3 10:37:32 localhost kernel: [ 37.090725] >> frontend_probe_and_watch: calling xenbus_probe_devices <<< custom debug >> message I added >> Feb 3 10:37:32 localhost kernel: [ 37.092362] XENBUS unexpected type >> [17], expected [1] >> Feb 3 10:37:32 localhost kernel: [ 37.092376] watching node >> FFFFFFFF81C7D820 >> Feb 3 10:37:32 localhost kernel: [ 37.093334] watching node >> FFFFFFFF81C7DB20 >> Feb 3 10:37:32 localhost kernel: [ 37.094454] XENBUS xen store gave: >> unknown error backend <<< still not sure how critical this is >> Feb 3 10:37:32 localhost kernel: [ 37.094463] Failed to set balloon >> watcher <<< still not sure how >> critical this is >> >> > xenstore-ls >> tool =3D "" >> xenstored =3D "" >> local =3D "" >> domain =3D "" >> 0 =3D "" >> data =3D "" >> meminfo_total =3D "930680" >> meminfo_free =3D "691868" >> os_name =3D "Ubuntu 12.04.1 LTS" >> os_majorver =3D "12" >> os_minorver =3D "04" >> os_uname =3D "3.8.0-rc5+" >> os_distro =3D "ubuntu" >> updated =3D "Sun Feb 3 10:43:32 MST 2013" >> name =3D "Domain-0" >> attr =3D "" >> xenbr0 =3D "" >> ip =3D "155.98.39.2" >> PVAddons =3D "" >> MajorVersion =3D "5" >> MinorVersion =3D "5" >> MicroVersion =3D "0" >> BuildVersion =3D "17913" >> Installed =3D "1" >> device-model =3D "" >> 0 =3D "" >> state =3D "running" >> >> After this I start the guest domain, here's the xenstore entries, >> >> nodea:~> sudo xenstore-ls >> tool =3D "" >> xenstored =3D "" >> local =3D "" >> domain =3D "" >> 0 =3D "" >> data =3D "" >> meminfo_total =3D "930680" >> meminfo_free =3D "695408" >> os_name =3D "Ubuntu 12.04.1 LTS" >> os_majorver =3D "12" >> os_minorver =3D "04" >> os_uname =3D "3.8.0-rc5+" >> os_distro =3D "ubuntu" >> updated =3D "Sun Feb 3 10:45:32 MST 2013" >> name =3D "Domain-0" >> attr =3D "" >> xenbr0 =3D "" >> ip =3D "155.98.39.2" >> PVAddons =3D "" >> MajorVersion =3D "5" >> MinorVersion =3D "5" >> MicroVersion =3D "0" >> BuildVersion =3D "17913" >> Installed =3D "1" >> device-model =3D "" >> 0 =3D "" >> state =3D "running" >> memory =3D "" >> target =3D "1048576" >> static-max =3D "4294967292" >> freemem-slack =3D "314476" >> libxl =3D "" >> disable_udev =3D "1" >> backend =3D "" >> vbd =3D "" >> 1 =3D "" >> 2049 =3D "" >> frontend =3D "/local/domain/1/device/vbd/2049" <<<< everything >> seems to be enumerated >> params =3D "/dev/loop0" >> script =3D "/etc/xen/scripts/block" >> physical-device =3D "7:0" >> frontend-id =3D "1" >> online =3D "1" >> removable =3D "0" >> bootable =3D "1" >> state =3D "1" >> dev =3D "sda1" >> type =3D "phy" >> mode =3D "w" >> device-type =3D "disk" >> 1 =3D "" >> vm =3D "/vm/9b0dfb10-f69d-4e22-9158-bb70456ece2e" >> name =3D "guest2" >> cpu =3D "" >> 0 =3D "" >> availability =3D "online" >> memory =3D "" >> static-max =3D "512000" >> target =3D "512001" >> videoram =3D "-1" >> device =3D "" >> suspend =3D "" >> event-channel =3D "" >> vbd =3D "" >> 2049 =3D "" >> backend =3D "/local/domain/0/backend/vbd/1/2049" >> backend-id =3D "0" >> state =3D "1" <<<<< state changes to 5 and then after 5 secs it >> times out >> virtual-device =3D "2049" >> device-type =3D "disk" >> control =3D "" >> shutdown =3D "" >> platform-feature-multiprocessor-suspend =3D "1" >> platform-feature-xs_reset_watches =3D "1" >> data =3D "" >> domid =3D "1" >> store =3D "" >> port =3D "1" >> ring-ref =3D "156845" >> vm =3D "" >> 9b0dfb10-f69d-4e22-9158-bb70456ece2e =3D "" >> uuid =3D "9b0dfb10-f69d-4e22-9158-bb70456ece2e" >> name =3D "guest2" >> image =3D "" >> ostype =3D "linux" >> kernel =3D "/boot/vmlinuz-3.8.0-rc5+" >> ramdisk =3D "/boot/initrd.img-3.8.0-rc5+" >> cmdline =3D "root=3D/dev/disk/by-path/xen-vbd-2049 ro xencons=3Dtty" >> start_time =3D "1359913591.67" >> libxl =3D "" >> 1 =3D "" >> dm-version =3D "qemu_xen" >> >> Thanks, >> Yathi _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Tue Feb 05 17:15:33 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 05 Feb 2013 17:15: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 1U2m6R-0008Pk-Co; Tue, 05 Feb 2013 17:14:39 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U2m4H-0008IX-9g for xen-users@lists.xen.org; Tue, 05 Feb 2013 17:12:25 +0000 Received: from [193.109.254.147:17506] by server-8.bemta-14.messagelabs.com id F4/5C-17325-57D31115; Tue, 05 Feb 2013 17:12:21 +0000 X-Env-Sender: ydev@cs.utah.edu X-Msg-Ref: server-12.tower-27.messagelabs.com!1360084318!9322104!1 X-Originating-IP: [155.98.64.241] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 31903 invoked from network); 5 Feb 2013 17:11:59 -0000 Received: from mail-svr1.cs.utah.edu (HELO mail-svr1.cs.utah.edu) (155.98.64.241) by server-12.tower-27.messagelabs.com with SMTP; 5 Feb 2013 17:11:59 -0000 Received: from localhost (localhost [127.0.0.1]) by mail-svr1.cs.utah.edu (Postfix) with ESMTP id 237346500C9; Tue, 5 Feb 2013 10:11:58 -0700 (MST) X-Virus-Scanned: amavisd-new at cs.utah.edu Received: from mail-svr1.cs.utah.edu ([127.0.0.1]) by localhost (mail-svr1.cs.utah.edu [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 54LRjChKjYLO; Tue, 5 Feb 2013 10:11:57 -0700 (MST) Received: from [192.168.1.16] (c-76-23-15-81.hsd1.ut.comcast.net [76.23.15.81]) by smtps.cs.utah.edu (Postfix) with ESMTPSA id C73FA6500C8; Tue, 5 Feb 2013 10:11:56 -0700 (MST) Message-ID: <51113D59.7030003@cs.utah.edu> Date: Tue, 05 Feb 2013 10:11:53 -0700 From: Yathindra User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130107 Thunderbird/17.0.2 MIME-Version: 1.0 To: =?ISO-8859-1?Q?Roger_Pau_Monn=E9?= References: <510DC655.5060205@cs.utah.edu> <510E3195.1010004@citrix.com> <510EA374.6060509@cs.utah.edu> <5110D7EC.8040608@citrix.com> In-Reply-To: <5110D7EC.8040608@citrix.com> X-Mailman-Approved-At: Tue, 05 Feb 2013 17:14:38 +0000 Cc: "xen-users@lists.xen.org" Subject: Re: [Xen-users] xen_blkbk times out before getting connected X-BeenThere: xen-users@lists.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 DomU configuration file looks like this: kernel =3D "/boot/vmlinuz-3.8.0-rc5+" ramdisk =3D "/boot/initrd.img-3.8.0-rc5+" memory =3D 500 name =3D "guest2" disk =3D ['phy:/dev/loop0,sda1,w'] root =3D "/dev/disk/by-path/xen-vbd-2049 ro" extra =3D 'xencons=3Dtty' On 2/5/2013 2:59 AM, Roger Pau Monn=E9 wrote: > On 03/02/13 18:50, Yathindra wrote: >> I'm using the latest linux kernel 3.8.0 with Xen 4.3-unstable. Xenstored >> is being started at boot time. >> I did not see any message (dmesg/syslog/console) about device being >> plugged in but xenstore-ls shows me all >> the entries backend and frontend. > Could you post your DomU configuration file also? > >> Here are some details >> ------------------------------ >> From /var/log/syslog: >> >> Feb 3 10:37:31 localhost kernel: [ 36.466359] Event-channel device >> installed. >> Feb 3 10:37:31 localhost kernel: [ 36.636358] Register >> xen_blkbk_driver <<< custom debug message I added >> Feb 3 10:37:31 localhost kernel: [ 36.636367] >> xenbus_register_backend <<< custom debug message I added >> Feb 3 10:37:31 localhost kernel: [ 36.683533] xenbus_register_backend >> Feb 3 10:37:31 localhost kernel: [ 36.830115] xen-pciback: backend is >> vpci <<< custom debug message I added >> Feb 3 10:37:31 localhost kernel: [ 36.830123] >> xenbus_register_backend <<< custom debug message I added >> Feb 3 10:37:32 localhost xenstored: Checking store ... >> Feb 3 10:37:32 localhost xenstored: Checking store complete. >> Feb 3 10:37:32 localhost kernel: [ 37.075217] xenbus_probe: xenstored >> is ready <<< custom debug message I added >> Feb 3 10:37:32 localhost kernel: [ 37.075230] watching node >> FFFFFFFF81C7D1A0 >> Feb 3 10:37:32 localhost kernel: [ 37.081309] xenbus_scanf for node c= pu/0 >> Feb 3 10:37:32 localhost kernel: [ 37.081327] XENBUS xen store gave: >> unknown error cpu >> Feb 3 10:37:32 localhost kernel: [ 37.081333] xenbus_scanf for node c= pu/1 >> Feb 3 10:37:32 localhost kernel: [ 37.085327] XENBUS unexpected type >> [17], expected [2] >> Feb 3 10:37:32 localhost kernel: [ 37.085342] watching node >> FFFFFFFF81C7D0C0 >> Feb 3 10:37:32 localhost kernel: [ 37.086857] XENBUS unexpected type >> [17], expected [4] >> Feb 3 10:37:32 localhost kernel: [ 37.086865] Failed to set shutdown >> watcher >> Feb 3 10:37:32 localhost kernel: [ 37.086880] backend_probe_and_watch >> - enumerates devices in xenstore and watches for changes <<< custom >> debug message I added >> Feb 3 10:37:32 localhost kernel: [ 37.089401] XENBUS unexpected type >> [4], expected [1] >> Feb 3 10:37:32 localhost kernel: [ 37.089411] watching node >> FFFFFFFF81C7D660 >> Feb 3 10:37:32 localhost kernel: [ 37.090715] XENBUS xen store gave: >> unknown error control/shutdown >> Feb 3 10:37:32 localhost kernel: [ 37.090725] >> frontend_probe_and_watch: calling xenbus_probe_devices <<< custom debug >> message I added >> Feb 3 10:37:32 localhost kernel: [ 37.092362] XENBUS unexpected type >> [17], expected [1] >> Feb 3 10:37:32 localhost kernel: [ 37.092376] watching node >> FFFFFFFF81C7D820 >> Feb 3 10:37:32 localhost kernel: [ 37.093334] watching node >> FFFFFFFF81C7DB20 >> Feb 3 10:37:32 localhost kernel: [ 37.094454] XENBUS xen store gave: >> unknown error backend <<< still not sure how critical this is >> Feb 3 10:37:32 localhost kernel: [ 37.094463] Failed to set balloon >> watcher <<< still not sure how >> critical this is >> >> > xenstore-ls >> tool =3D "" >> xenstored =3D "" >> local =3D "" >> domain =3D "" >> 0 =3D "" >> data =3D "" >> meminfo_total =3D "930680" >> meminfo_free =3D "691868" >> os_name =3D "Ubuntu 12.04.1 LTS" >> os_majorver =3D "12" >> os_minorver =3D "04" >> os_uname =3D "3.8.0-rc5+" >> os_distro =3D "ubuntu" >> updated =3D "Sun Feb 3 10:43:32 MST 2013" >> name =3D "Domain-0" >> attr =3D "" >> xenbr0 =3D "" >> ip =3D "155.98.39.2" >> PVAddons =3D "" >> MajorVersion =3D "5" >> MinorVersion =3D "5" >> MicroVersion =3D "0" >> BuildVersion =3D "17913" >> Installed =3D "1" >> device-model =3D "" >> 0 =3D "" >> state =3D "running" >> >> After this I start the guest domain, here's the xenstore entries, >> >> nodea:~> sudo xenstore-ls >> tool =3D "" >> xenstored =3D "" >> local =3D "" >> domain =3D "" >> 0 =3D "" >> data =3D "" >> meminfo_total =3D "930680" >> meminfo_free =3D "695408" >> os_name =3D "Ubuntu 12.04.1 LTS" >> os_majorver =3D "12" >> os_minorver =3D "04" >> os_uname =3D "3.8.0-rc5+" >> os_distro =3D "ubuntu" >> updated =3D "Sun Feb 3 10:45:32 MST 2013" >> name =3D "Domain-0" >> attr =3D "" >> xenbr0 =3D "" >> ip =3D "155.98.39.2" >> PVAddons =3D "" >> MajorVersion =3D "5" >> MinorVersion =3D "5" >> MicroVersion =3D "0" >> BuildVersion =3D "17913" >> Installed =3D "1" >> device-model =3D "" >> 0 =3D "" >> state =3D "running" >> memory =3D "" >> target =3D "1048576" >> static-max =3D "4294967292" >> freemem-slack =3D "314476" >> libxl =3D "" >> disable_udev =3D "1" >> backend =3D "" >> vbd =3D "" >> 1 =3D "" >> 2049 =3D "" >> frontend =3D "/local/domain/1/device/vbd/2049" <<<< everything >> seems to be enumerated >> params =3D "/dev/loop0" >> script =3D "/etc/xen/scripts/block" >> physical-device =3D "7:0" >> frontend-id =3D "1" >> online =3D "1" >> removable =3D "0" >> bootable =3D "1" >> state =3D "1" >> dev =3D "sda1" >> type =3D "phy" >> mode =3D "w" >> device-type =3D "disk" >> 1 =3D "" >> vm =3D "/vm/9b0dfb10-f69d-4e22-9158-bb70456ece2e" >> name =3D "guest2" >> cpu =3D "" >> 0 =3D "" >> availability =3D "online" >> memory =3D "" >> static-max =3D "512000" >> target =3D "512001" >> videoram =3D "-1" >> device =3D "" >> suspend =3D "" >> event-channel =3D "" >> vbd =3D "" >> 2049 =3D "" >> backend =3D "/local/domain/0/backend/vbd/1/2049" >> backend-id =3D "0" >> state =3D "1" <<<<< state changes to 5 and then after 5 secs it >> times out >> virtual-device =3D "2049" >> device-type =3D "disk" >> control =3D "" >> shutdown =3D "" >> platform-feature-multiprocessor-suspend =3D "1" >> platform-feature-xs_reset_watches =3D "1" >> data =3D "" >> domid =3D "1" >> store =3D "" >> port =3D "1" >> ring-ref =3D "156845" >> vm =3D "" >> 9b0dfb10-f69d-4e22-9158-bb70456ece2e =3D "" >> uuid =3D "9b0dfb10-f69d-4e22-9158-bb70456ece2e" >> name =3D "guest2" >> image =3D "" >> ostype =3D "linux" >> kernel =3D "/boot/vmlinuz-3.8.0-rc5+" >> ramdisk =3D "/boot/initrd.img-3.8.0-rc5+" >> cmdline =3D "root=3D/dev/disk/by-path/xen-vbd-2049 ro xencons=3Dtty" >> start_time =3D "1359913591.67" >> libxl =3D "" >> 1 =3D "" >> dm-version =3D "qemu_xen" >> >> Thanks, >> Yathi _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Tue Feb 05 18:12:12 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 05 Feb 2013 18:12: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 1U2mz4-0003eZ-3l; Tue, 05 Feb 2013 18:11:06 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U2mz2-0003eT-HQ for xen-users@lists.xen.org; Tue, 05 Feb 2013 18:11:04 +0000 Received: from [85.158.139.83:13864] by server-5.bemta-5.messagelabs.com id 18/24-11945-73B41115; Tue, 05 Feb 2013 18:11:03 +0000 X-Env-Sender: roger.pau@citrix.com X-Msg-Ref: server-10.tower-182.messagelabs.com!1360087862!27855287!1 X-Originating-IP: [46.33.159.39] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNDYuMzMuMTU5LjM5ID0+IDIwODEx\n X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 27217 invoked from network); 5 Feb 2013 18:11:03 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (46.33.159.39) by server-10.tower-182.messagelabs.com with RC4-SHA encrypted SMTP; 5 Feb 2013 18:11:03 -0000 X-IronPort-AV: E=Sophos;i="4.84,609,1355097600"; d="scan'208";a="1167698" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 05 Feb 2013 18:11:03 +0000 Received: from [192.168.1.30] (10.30.249.242) by LONPMAILMX01.citrite.net (10.30.203.162) with Microsoft SMTP Server id 8.3.297.1; Tue, 5 Feb 2013 18:11:02 +0000 Message-ID: <51114B35.5050202@citrix.com> Date: Tue, 5 Feb 2013 19:11:01 +0100 From: =?ISO-8859-1?Q?Roger_Pau_Monn=E9?= User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130107 Thunderbird/17.0.2 MIME-Version: 1.0 To: Yathindra References: <510DC655.5060205@cs.utah.edu> <510E3195.1010004@citrix.com> <510EA374.6060509@cs.utah.edu> <5110D7EC.8040608@citrix.com> <51113D59.7030003@cs.utah.edu> In-Reply-To: <51113D59.7030003@cs.utah.edu> Cc: "xen-users@lists.xen.org" Subject: Re: [Xen-users] xen_blkbk times out before getting connected X-BeenThere: xen-users@lists.xen.org X-Mailman-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 05/02/13 18:11, Yathindra wrote: > DomU configuration file looks like this: Please don't do top posting. > kernel =3D "/boot/vmlinuz-3.8.0-rc5+" > ramdisk =3D "/boot/initrd.img-3.8.0-rc5+" > memory =3D 500 > name =3D "guest2" > disk =3D ['phy:/dev/loop0,sda1,w'] Why are you using sda1 instead of xvda1? > root =3D "/dev/disk/by-path/xen-vbd-2049 ro" > extra =3D 'xencons=3Dtty' You can use: extra=3D"root=3D/dev/xvda1" > = > On 2/5/2013 2:59 AM, Roger Pau Monn=E9 wrote: >> On 03/02/13 18:50, Yathindra wrote: >>> I'm using the latest linux kernel 3.8.0 with Xen 4.3-unstable. Xenstored >>> is being started at boot time. >>> I did not see any message (dmesg/syslog/console) about device being >>> plugged in but xenstore-ls shows me all >>> the entries backend and frontend. >> Could you post your DomU configuration file also? >> >>> Here are some details >>> ------------------------------ >>> From /var/log/syslog: >>> >>> Feb 3 10:37:31 localhost kernel: [ 36.466359] Event-channel device >>> installed. >>> Feb 3 10:37:31 localhost kernel: [ 36.636358] Register >>> xen_blkbk_driver <<< custom debug message I added >>> Feb 3 10:37:31 localhost kernel: [ 36.636367] >>> xenbus_register_backend <<< custom debug message I added >>> Feb 3 10:37:31 localhost kernel: [ 36.683533] xenbus_register_backend >>> Feb 3 10:37:31 localhost kernel: [ 36.830115] xen-pciback: backend is >>> vpci <<< custom debug message I added >>> Feb 3 10:37:31 localhost kernel: [ 36.830123] >>> xenbus_register_backend <<< custom debug message I added >>> Feb 3 10:37:32 localhost xenstored: Checking store ... >>> Feb 3 10:37:32 localhost xenstored: Checking store complete. >>> Feb 3 10:37:32 localhost kernel: [ 37.075217] xenbus_probe: xenstored >>> is ready <<< custom debug message I added >>> Feb 3 10:37:32 localhost kernel: [ 37.075230] watching node >>> FFFFFFFF81C7D1A0 >>> Feb 3 10:37:32 localhost kernel: [ 37.081309] xenbus_scanf for node = cpu/0 >>> Feb 3 10:37:32 localhost kernel: [ 37.081327] XENBUS xen store gave: >>> unknown error cpu >>> Feb 3 10:37:32 localhost kernel: [ 37.081333] xenbus_scanf for node = cpu/1 >>> Feb 3 10:37:32 localhost kernel: [ 37.085327] XENBUS unexpected type >>> [17], expected [2] >>> Feb 3 10:37:32 localhost kernel: [ 37.085342] watching node >>> FFFFFFFF81C7D0C0 >>> Feb 3 10:37:32 localhost kernel: [ 37.086857] XENBUS unexpected type >>> [17], expected [4] >>> Feb 3 10:37:32 localhost kernel: [ 37.086865] Failed to set shutdown >>> watcher >>> Feb 3 10:37:32 localhost kernel: [ 37.086880] backend_probe_and_watch >>> - enumerates devices in xenstore and watches for changes <<< custom >>> debug message I added >>> Feb 3 10:37:32 localhost kernel: [ 37.089401] XENBUS unexpected type >>> [4], expected [1] >>> Feb 3 10:37:32 localhost kernel: [ 37.089411] watching node >>> FFFFFFFF81C7D660 >>> Feb 3 10:37:32 localhost kernel: [ 37.090715] XENBUS xen store gave: >>> unknown error control/shutdown >>> Feb 3 10:37:32 localhost kernel: [ 37.090725] >>> frontend_probe_and_watch: calling xenbus_probe_devices <<< custom debug >>> message I added >>> Feb 3 10:37:32 localhost kernel: [ 37.092362] XENBUS unexpected type >>> [17], expected [1] >>> Feb 3 10:37:32 localhost kernel: [ 37.092376] watching node >>> FFFFFFFF81C7D820 >>> Feb 3 10:37:32 localhost kernel: [ 37.093334] watching node >>> FFFFFFFF81C7DB20 >>> Feb 3 10:37:32 localhost kernel: [ 37.094454] XENBUS xen store gave: >>> unknown error backend <<< still not sure how critical this is >>> Feb 3 10:37:32 localhost kernel: [ 37.094463] Failed to set balloon >>> watcher <<< still not sure how >>> critical this is >>> >>> > xenstore-ls >>> tool =3D "" >>> xenstored =3D "" >>> local =3D "" >>> domain =3D "" >>> 0 =3D "" >>> data =3D "" >>> meminfo_total =3D "930680" >>> meminfo_free =3D "691868" >>> os_name =3D "Ubuntu 12.04.1 LTS" >>> os_majorver =3D "12" >>> os_minorver =3D "04" >>> os_uname =3D "3.8.0-rc5+" >>> os_distro =3D "ubuntu" >>> updated =3D "Sun Feb 3 10:43:32 MST 2013" >>> name =3D "Domain-0" >>> attr =3D "" >>> xenbr0 =3D "" >>> ip =3D "155.98.39.2" >>> PVAddons =3D "" >>> MajorVersion =3D "5" >>> MinorVersion =3D "5" >>> MicroVersion =3D "0" >>> BuildVersion =3D "17913" >>> Installed =3D "1" >>> device-model =3D "" >>> 0 =3D "" >>> state =3D "running" >>> >>> After this I start the guest domain, here's the xenstore entries, >>> >>> nodea:~> sudo xenstore-ls >>> tool =3D "" >>> xenstored =3D "" >>> local =3D "" >>> domain =3D "" >>> 0 =3D "" >>> data =3D "" >>> meminfo_total =3D "930680" >>> meminfo_free =3D "695408" >>> os_name =3D "Ubuntu 12.04.1 LTS" >>> os_majorver =3D "12" >>> os_minorver =3D "04" >>> os_uname =3D "3.8.0-rc5+" >>> os_distro =3D "ubuntu" >>> updated =3D "Sun Feb 3 10:45:32 MST 2013" >>> name =3D "Domain-0" >>> attr =3D "" >>> xenbr0 =3D "" >>> ip =3D "155.98.39.2" >>> PVAddons =3D "" >>> MajorVersion =3D "5" >>> MinorVersion =3D "5" >>> MicroVersion =3D "0" >>> BuildVersion =3D "17913" >>> Installed =3D "1" >>> device-model =3D "" >>> 0 =3D "" >>> state =3D "running" >>> memory =3D "" >>> target =3D "1048576" >>> static-max =3D "4294967292" >>> freemem-slack =3D "314476" >>> libxl =3D "" >>> disable_udev =3D "1" >>> backend =3D "" >>> vbd =3D "" >>> 1 =3D "" >>> 2049 =3D "" >>> frontend =3D "/local/domain/1/device/vbd/2049" <<<< everything >>> seems to be enumerated >>> params =3D "/dev/loop0" >>> script =3D "/etc/xen/scripts/block" >>> physical-device =3D "7:0" >>> frontend-id =3D "1" >>> online =3D "1" >>> removable =3D "0" >>> bootable =3D "1" >>> state =3D "1" >>> dev =3D "sda1" >>> type =3D "phy" >>> mode =3D "w" >>> device-type =3D "disk" >>> 1 =3D "" >>> vm =3D "/vm/9b0dfb10-f69d-4e22-9158-bb70456ece2e" >>> name =3D "guest2" >>> cpu =3D "" >>> 0 =3D "" >>> availability =3D "online" >>> memory =3D "" >>> static-max =3D "512000" >>> target =3D "512001" >>> videoram =3D "-1" >>> device =3D "" >>> suspend =3D "" >>> event-channel =3D "" >>> vbd =3D "" >>> 2049 =3D "" >>> backend =3D "/local/domain/0/backend/vbd/1/2049" >>> backend-id =3D "0" >>> state =3D "1" <<<<< state changes to 5 and then after 5 secs it >>> times out >>> virtual-device =3D "2049" >>> device-type =3D "disk" >>> control =3D "" >>> shutdown =3D "" >>> platform-feature-multiprocessor-suspend =3D "1" >>> platform-feature-xs_reset_watches =3D "1" >>> data =3D "" >>> domid =3D "1" >>> store =3D "" >>> port =3D "1" >>> ring-ref =3D "156845" >>> vm =3D "" >>> 9b0dfb10-f69d-4e22-9158-bb70456ece2e =3D "" >>> uuid =3D "9b0dfb10-f69d-4e22-9158-bb70456ece2e" >>> name =3D "guest2" >>> image =3D "" >>> ostype =3D "linux" >>> kernel =3D "/boot/vmlinuz-3.8.0-rc5+" >>> ramdisk =3D "/boot/initrd.img-3.8.0-rc5+" >>> cmdline =3D "root=3D/dev/disk/by-path/xen-vbd-2049 ro xencons=3Dtt= y" >>> start_time =3D "1359913591.67" >>> libxl =3D "" >>> 1 =3D "" >>> dm-version =3D "qemu_xen" >>> >>> Thanks, >>> Yathi > = _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Tue Feb 05 18:12:12 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 05 Feb 2013 18:12: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 1U2mz4-0003eZ-3l; Tue, 05 Feb 2013 18:11:06 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U2mz2-0003eT-HQ for xen-users@lists.xen.org; Tue, 05 Feb 2013 18:11:04 +0000 Received: from [85.158.139.83:13864] by server-5.bemta-5.messagelabs.com id 18/24-11945-73B41115; Tue, 05 Feb 2013 18:11:03 +0000 X-Env-Sender: roger.pau@citrix.com X-Msg-Ref: server-10.tower-182.messagelabs.com!1360087862!27855287!1 X-Originating-IP: [46.33.159.39] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNDYuMzMuMTU5LjM5ID0+IDIwODEx\n X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 27217 invoked from network); 5 Feb 2013 18:11:03 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (46.33.159.39) by server-10.tower-182.messagelabs.com with RC4-SHA encrypted SMTP; 5 Feb 2013 18:11:03 -0000 X-IronPort-AV: E=Sophos;i="4.84,609,1355097600"; d="scan'208";a="1167698" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 05 Feb 2013 18:11:03 +0000 Received: from [192.168.1.30] (10.30.249.242) by LONPMAILMX01.citrite.net (10.30.203.162) with Microsoft SMTP Server id 8.3.297.1; Tue, 5 Feb 2013 18:11:02 +0000 Message-ID: <51114B35.5050202@citrix.com> Date: Tue, 5 Feb 2013 19:11:01 +0100 From: =?ISO-8859-1?Q?Roger_Pau_Monn=E9?= User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130107 Thunderbird/17.0.2 MIME-Version: 1.0 To: Yathindra References: <510DC655.5060205@cs.utah.edu> <510E3195.1010004@citrix.com> <510EA374.6060509@cs.utah.edu> <5110D7EC.8040608@citrix.com> <51113D59.7030003@cs.utah.edu> In-Reply-To: <51113D59.7030003@cs.utah.edu> Cc: "xen-users@lists.xen.org" Subject: Re: [Xen-users] xen_blkbk times out before getting connected X-BeenThere: xen-users@lists.xen.org X-Mailman-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 05/02/13 18:11, Yathindra wrote: > DomU configuration file looks like this: Please don't do top posting. > kernel =3D "/boot/vmlinuz-3.8.0-rc5+" > ramdisk =3D "/boot/initrd.img-3.8.0-rc5+" > memory =3D 500 > name =3D "guest2" > disk =3D ['phy:/dev/loop0,sda1,w'] Why are you using sda1 instead of xvda1? > root =3D "/dev/disk/by-path/xen-vbd-2049 ro" > extra =3D 'xencons=3Dtty' You can use: extra=3D"root=3D/dev/xvda1" > = > On 2/5/2013 2:59 AM, Roger Pau Monn=E9 wrote: >> On 03/02/13 18:50, Yathindra wrote: >>> I'm using the latest linux kernel 3.8.0 with Xen 4.3-unstable. Xenstored >>> is being started at boot time. >>> I did not see any message (dmesg/syslog/console) about device being >>> plugged in but xenstore-ls shows me all >>> the entries backend and frontend. >> Could you post your DomU configuration file also? >> >>> Here are some details >>> ------------------------------ >>> From /var/log/syslog: >>> >>> Feb 3 10:37:31 localhost kernel: [ 36.466359] Event-channel device >>> installed. >>> Feb 3 10:37:31 localhost kernel: [ 36.636358] Register >>> xen_blkbk_driver <<< custom debug message I added >>> Feb 3 10:37:31 localhost kernel: [ 36.636367] >>> xenbus_register_backend <<< custom debug message I added >>> Feb 3 10:37:31 localhost kernel: [ 36.683533] xenbus_register_backend >>> Feb 3 10:37:31 localhost kernel: [ 36.830115] xen-pciback: backend is >>> vpci <<< custom debug message I added >>> Feb 3 10:37:31 localhost kernel: [ 36.830123] >>> xenbus_register_backend <<< custom debug message I added >>> Feb 3 10:37:32 localhost xenstored: Checking store ... >>> Feb 3 10:37:32 localhost xenstored: Checking store complete. >>> Feb 3 10:37:32 localhost kernel: [ 37.075217] xenbus_probe: xenstored >>> is ready <<< custom debug message I added >>> Feb 3 10:37:32 localhost kernel: [ 37.075230] watching node >>> FFFFFFFF81C7D1A0 >>> Feb 3 10:37:32 localhost kernel: [ 37.081309] xenbus_scanf for node = cpu/0 >>> Feb 3 10:37:32 localhost kernel: [ 37.081327] XENBUS xen store gave: >>> unknown error cpu >>> Feb 3 10:37:32 localhost kernel: [ 37.081333] xenbus_scanf for node = cpu/1 >>> Feb 3 10:37:32 localhost kernel: [ 37.085327] XENBUS unexpected type >>> [17], expected [2] >>> Feb 3 10:37:32 localhost kernel: [ 37.085342] watching node >>> FFFFFFFF81C7D0C0 >>> Feb 3 10:37:32 localhost kernel: [ 37.086857] XENBUS unexpected type >>> [17], expected [4] >>> Feb 3 10:37:32 localhost kernel: [ 37.086865] Failed to set shutdown >>> watcher >>> Feb 3 10:37:32 localhost kernel: [ 37.086880] backend_probe_and_watch >>> - enumerates devices in xenstore and watches for changes <<< custom >>> debug message I added >>> Feb 3 10:37:32 localhost kernel: [ 37.089401] XENBUS unexpected type >>> [4], expected [1] >>> Feb 3 10:37:32 localhost kernel: [ 37.089411] watching node >>> FFFFFFFF81C7D660 >>> Feb 3 10:37:32 localhost kernel: [ 37.090715] XENBUS xen store gave: >>> unknown error control/shutdown >>> Feb 3 10:37:32 localhost kernel: [ 37.090725] >>> frontend_probe_and_watch: calling xenbus_probe_devices <<< custom debug >>> message I added >>> Feb 3 10:37:32 localhost kernel: [ 37.092362] XENBUS unexpected type >>> [17], expected [1] >>> Feb 3 10:37:32 localhost kernel: [ 37.092376] watching node >>> FFFFFFFF81C7D820 >>> Feb 3 10:37:32 localhost kernel: [ 37.093334] watching node >>> FFFFFFFF81C7DB20 >>> Feb 3 10:37:32 localhost kernel: [ 37.094454] XENBUS xen store gave: >>> unknown error backend <<< still not sure how critical this is >>> Feb 3 10:37:32 localhost kernel: [ 37.094463] Failed to set balloon >>> watcher <<< still not sure how >>> critical this is >>> >>> > xenstore-ls >>> tool =3D "" >>> xenstored =3D "" >>> local =3D "" >>> domain =3D "" >>> 0 =3D "" >>> data =3D "" >>> meminfo_total =3D "930680" >>> meminfo_free =3D "691868" >>> os_name =3D "Ubuntu 12.04.1 LTS" >>> os_majorver =3D "12" >>> os_minorver =3D "04" >>> os_uname =3D "3.8.0-rc5+" >>> os_distro =3D "ubuntu" >>> updated =3D "Sun Feb 3 10:43:32 MST 2013" >>> name =3D "Domain-0" >>> attr =3D "" >>> xenbr0 =3D "" >>> ip =3D "155.98.39.2" >>> PVAddons =3D "" >>> MajorVersion =3D "5" >>> MinorVersion =3D "5" >>> MicroVersion =3D "0" >>> BuildVersion =3D "17913" >>> Installed =3D "1" >>> device-model =3D "" >>> 0 =3D "" >>> state =3D "running" >>> >>> After this I start the guest domain, here's the xenstore entries, >>> >>> nodea:~> sudo xenstore-ls >>> tool =3D "" >>> xenstored =3D "" >>> local =3D "" >>> domain =3D "" >>> 0 =3D "" >>> data =3D "" >>> meminfo_total =3D "930680" >>> meminfo_free =3D "695408" >>> os_name =3D "Ubuntu 12.04.1 LTS" >>> os_majorver =3D "12" >>> os_minorver =3D "04" >>> os_uname =3D "3.8.0-rc5+" >>> os_distro =3D "ubuntu" >>> updated =3D "Sun Feb 3 10:45:32 MST 2013" >>> name =3D "Domain-0" >>> attr =3D "" >>> xenbr0 =3D "" >>> ip =3D "155.98.39.2" >>> PVAddons =3D "" >>> MajorVersion =3D "5" >>> MinorVersion =3D "5" >>> MicroVersion =3D "0" >>> BuildVersion =3D "17913" >>> Installed =3D "1" >>> device-model =3D "" >>> 0 =3D "" >>> state =3D "running" >>> memory =3D "" >>> target =3D "1048576" >>> static-max =3D "4294967292" >>> freemem-slack =3D "314476" >>> libxl =3D "" >>> disable_udev =3D "1" >>> backend =3D "" >>> vbd =3D "" >>> 1 =3D "" >>> 2049 =3D "" >>> frontend =3D "/local/domain/1/device/vbd/2049" <<<< everything >>> seems to be enumerated >>> params =3D "/dev/loop0" >>> script =3D "/etc/xen/scripts/block" >>> physical-device =3D "7:0" >>> frontend-id =3D "1" >>> online =3D "1" >>> removable =3D "0" >>> bootable =3D "1" >>> state =3D "1" >>> dev =3D "sda1" >>> type =3D "phy" >>> mode =3D "w" >>> device-type =3D "disk" >>> 1 =3D "" >>> vm =3D "/vm/9b0dfb10-f69d-4e22-9158-bb70456ece2e" >>> name =3D "guest2" >>> cpu =3D "" >>> 0 =3D "" >>> availability =3D "online" >>> memory =3D "" >>> static-max =3D "512000" >>> target =3D "512001" >>> videoram =3D "-1" >>> device =3D "" >>> suspend =3D "" >>> event-channel =3D "" >>> vbd =3D "" >>> 2049 =3D "" >>> backend =3D "/local/domain/0/backend/vbd/1/2049" >>> backend-id =3D "0" >>> state =3D "1" <<<<< state changes to 5 and then after 5 secs it >>> times out >>> virtual-device =3D "2049" >>> device-type =3D "disk" >>> control =3D "" >>> shutdown =3D "" >>> platform-feature-multiprocessor-suspend =3D "1" >>> platform-feature-xs_reset_watches =3D "1" >>> data =3D "" >>> domid =3D "1" >>> store =3D "" >>> port =3D "1" >>> ring-ref =3D "156845" >>> vm =3D "" >>> 9b0dfb10-f69d-4e22-9158-bb70456ece2e =3D "" >>> uuid =3D "9b0dfb10-f69d-4e22-9158-bb70456ece2e" >>> name =3D "guest2" >>> image =3D "" >>> ostype =3D "linux" >>> kernel =3D "/boot/vmlinuz-3.8.0-rc5+" >>> ramdisk =3D "/boot/initrd.img-3.8.0-rc5+" >>> cmdline =3D "root=3D/dev/disk/by-path/xen-vbd-2049 ro xencons=3Dtt= y" >>> start_time =3D "1359913591.67" >>> libxl =3D "" >>> 1 =3D "" >>> dm-version =3D "qemu_xen" >>> >>> Thanks, >>> Yathi > = _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Wed Feb 06 05:56:20 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 06 Feb 2013 05:56: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 1U2xxp-00026I-UF; Wed, 06 Feb 2013 05:54:33 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U2xxp-00026D-BF for Xen-users@lists.xen.org; Wed, 06 Feb 2013 05:54:33 +0000 Received: from [85.158.138.51:25224] by server-3.bemta-3.messagelabs.com id 37/35-31070-810F1115; Wed, 06 Feb 2013 05:54:32 +0000 X-Env-Sender: min.lee@gatech.edu X-Msg-Ref: server-14.tower-174.messagelabs.com!1360130071!23063715!1 X-Originating-IP: [130.207.160.69] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 7366 invoked from network); 6 Feb 2013 05:54:31 -0000 Received: from deliverator2.gatech.edu (HELO deliverator2.gatech.edu) (130.207.160.69) by server-14.tower-174.messagelabs.com with SMTP; 6 Feb 2013 05:54:31 -0000 Received: from deliverator2.gatech.edu (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id BB54DD1CCD3; Wed, 6 Feb 2013 00:54:30 -0500 (EST) Received: from mail7.gatech.edu (mail7.gatech.edu [130.207.185.167]) by deliverator2.gatech.edu (Postfix) with ESMTP id 3B775D1CC11; Wed, 6 Feb 2013 00:54:30 -0500 (EST) Received: from [143.215.207.70] (lawn-143-215-207-70.lawn.gatech.edu [143.215.207.70]) (Authenticated sender: mlee7) by mail7.gatech.edu (Postfix) with ESMTPSA id 2F28A2C8955; Wed, 6 Feb 2013 00:54:30 -0500 (EST) Message-ID: <5111F019.6080607@gatech.edu> Date: Wed, 06 Feb 2013 00:54:33 -0500 From: Min Lee User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130107 Thunderbird/17.0.2 MIME-Version: 1.0 To: Ian Campbell References: <510B0CD5.3060905@gatech.edu> <1359970738.5281.5.camel@zakaz.uk.xensource.com> In-Reply-To: <1359970738.5281.5.camel@zakaz.uk.xensource.com> X-GT-AVAS-Version: 5.6.1.2065439, Antispam-Engine: 2.7.2.376379, Antispam-Data: 2013.2.6.54221 X-GT-Spam-Details: Internal Mail X-GT-Spam-Rating: (0%) X-GT-True-Rating: (8%) Cc: "Xen-users@lists.xen.org" Subject: Re: [Xen-users] dom0's layout on physical 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-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 Thank you for your reply, Ian. I'll take a look at them.. thanks! Min On 2/4/2013 4:38 AM, Ian Campbell wrote: > On Fri, 2013-02-01 at 00:31 +0000, Min Lee wrote: >> Hello, all >> I thought dom0 is layed out on physical memory starting 0, linearly, but >> this message, >> >> (XEN) *** LOADING DOMAIN 0 *** >> (XEN) Xen kernel: 64-bit, lsb, compat32 >> (XEN) Dom0 kernel: 64-bit, PAE, lsb, paddr 0x1000000 -> 0x1d87000 >> (XEN) PHYSICAL MEMORY ARRANGEMENT: >> (XEN) Dom0 alloc.: 0000000c14000000->0000000c18000000 (498514 pages to >> be allocated) >> >> shows the address range 0000000c14000000->0000000c18000000 , >> what is this? > > That is the virtual address range. > > The start of day memory layout is described in > http://xenbits.xen.org/docs/unstable/hypercall/include,public,xen.h.html#incontents_startofday > >> it's 64MB range and why 64MB from Dom0 is located here? > > This is the size of the initial mapping given your kenrel and initrd > size etc. > >> I think 498514 pages will be allocated later, but where, exactly?? > > IIRC the kernel will map it as part of its initialisation, > init_memory_mapping() in Linux perhaps? > >> if dom0's memory is partitioned into several places, >> then, what happens to their GPFN?? > > I'm not sure I understand this question. > > Ian. > > > _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Wed Feb 06 05:56:20 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 06 Feb 2013 05:56: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 1U2xxp-00026I-UF; Wed, 06 Feb 2013 05:54:33 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U2xxp-00026D-BF for Xen-users@lists.xen.org; Wed, 06 Feb 2013 05:54:33 +0000 Received: from [85.158.138.51:25224] by server-3.bemta-3.messagelabs.com id 37/35-31070-810F1115; Wed, 06 Feb 2013 05:54:32 +0000 X-Env-Sender: min.lee@gatech.edu X-Msg-Ref: server-14.tower-174.messagelabs.com!1360130071!23063715!1 X-Originating-IP: [130.207.160.69] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 7366 invoked from network); 6 Feb 2013 05:54:31 -0000 Received: from deliverator2.gatech.edu (HELO deliverator2.gatech.edu) (130.207.160.69) by server-14.tower-174.messagelabs.com with SMTP; 6 Feb 2013 05:54:31 -0000 Received: from deliverator2.gatech.edu (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id BB54DD1CCD3; Wed, 6 Feb 2013 00:54:30 -0500 (EST) Received: from mail7.gatech.edu (mail7.gatech.edu [130.207.185.167]) by deliverator2.gatech.edu (Postfix) with ESMTP id 3B775D1CC11; Wed, 6 Feb 2013 00:54:30 -0500 (EST) Received: from [143.215.207.70] (lawn-143-215-207-70.lawn.gatech.edu [143.215.207.70]) (Authenticated sender: mlee7) by mail7.gatech.edu (Postfix) with ESMTPSA id 2F28A2C8955; Wed, 6 Feb 2013 00:54:30 -0500 (EST) Message-ID: <5111F019.6080607@gatech.edu> Date: Wed, 06 Feb 2013 00:54:33 -0500 From: Min Lee User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130107 Thunderbird/17.0.2 MIME-Version: 1.0 To: Ian Campbell References: <510B0CD5.3060905@gatech.edu> <1359970738.5281.5.camel@zakaz.uk.xensource.com> In-Reply-To: <1359970738.5281.5.camel@zakaz.uk.xensource.com> X-GT-AVAS-Version: 5.6.1.2065439, Antispam-Engine: 2.7.2.376379, Antispam-Data: 2013.2.6.54221 X-GT-Spam-Details: Internal Mail X-GT-Spam-Rating: (0%) X-GT-True-Rating: (8%) Cc: "Xen-users@lists.xen.org" Subject: Re: [Xen-users] dom0's layout on physical 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-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 Thank you for your reply, Ian. I'll take a look at them.. thanks! Min On 2/4/2013 4:38 AM, Ian Campbell wrote: > On Fri, 2013-02-01 at 00:31 +0000, Min Lee wrote: >> Hello, all >> I thought dom0 is layed out on physical memory starting 0, linearly, but >> this message, >> >> (XEN) *** LOADING DOMAIN 0 *** >> (XEN) Xen kernel: 64-bit, lsb, compat32 >> (XEN) Dom0 kernel: 64-bit, PAE, lsb, paddr 0x1000000 -> 0x1d87000 >> (XEN) PHYSICAL MEMORY ARRANGEMENT: >> (XEN) Dom0 alloc.: 0000000c14000000->0000000c18000000 (498514 pages to >> be allocated) >> >> shows the address range 0000000c14000000->0000000c18000000 , >> what is this? > > That is the virtual address range. > > The start of day memory layout is described in > http://xenbits.xen.org/docs/unstable/hypercall/include,public,xen.h.html#incontents_startofday > >> it's 64MB range and why 64MB from Dom0 is located here? > > This is the size of the initial mapping given your kenrel and initrd > size etc. > >> I think 498514 pages will be allocated later, but where, exactly?? > > IIRC the kernel will map it as part of its initialisation, > init_memory_mapping() in Linux perhaps? > >> if dom0's memory is partitioned into several places, >> then, what happens to their GPFN?? > > I'm not sure I understand this question. > > Ian. > > > _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Wed Feb 06 12:01:28 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 06 Feb 2013 12:01: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 1U33ff-0007fh-U3; Wed, 06 Feb 2013 12:00:11 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U33fb-0007fJ-Sn for xen-users@lists.xen.org; Wed, 06 Feb 2013 12:00:10 +0000 Received: from [85.158.137.99:63590] by server-9.bemta-3.messagelabs.com id 0B/D5-09484-7C542115; Wed, 06 Feb 2013 12:00:07 +0000 X-Env-Sender: linux@thehobsons.co.uk X-Msg-Ref: server-5.tower-217.messagelabs.com!1360152004!15524350!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.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 16514 invoked from network); 6 Feb 2013 12:00:05 -0000 Received: from patsy.thehobsons.co.uk (HELO patsy.thehobsons.co.uk) (81.174.135.208) by server-5.tower-217.messagelabs.com with SMTP; 6 Feb 2013 12:00:05 -0000 Received: from localhost (localhost [127.0.0.1]) by patsy.thehobsons.co.uk (Postfix) with ESMTP id B0DA310401A for ; Wed, 6 Feb 2013 12:00:02 +0000 (GMT) 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 kbuG3jtqErhb for ; Wed, 6 Feb 2013 12:00:02 +0000 (GMT) Received: from localhost (patsy.thehobsons.co.uk [192.168.0.33]) by patsy.thehobsons.co.uk (Postfix) with ESMTP id E5F8829F28 for ; Wed, 6 Feb 2013 12:00:01 +0000 (GMT) From: "Simon Hobson" To: xen-users@lists.xen.org Date: Wed, 6 Feb 2013 12:00:02 +0000 X-Priority: 3 X-Mailer: MailForge 3.0 Mac OS X Message-ID: <07C333514DC1233EBC29AFA91F4B2FC6@thehobsons.co.uk> Subject: Re: [Xen-users] Using Ipv4 and IPv6 Subnet X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org Thore wrote: >I have a problem/question for understanding. >I have on my server (debian wheezy) 3 virtual systems running on xen >with own IPv4 addresses. >Form my hoster I got an IPv6 subnet, but I don't really know how to add it. >Is it enought to add an address of it in the /etc/network/interfaces of >the virtual systems? >Or must I set up routing for Xen and how does it works together with >bridging? >Which settings I had to change? >And am I able to set up an system only with Ipv6? >(I have IPv6) These are mostly not really Xen questions, more a general networking issue. The first question is, how does the hoster present your networking ? And how is your Xen networking set up ? If (for example) your hoster presents you an ethernet cable, with your own IP range and a gateway address for their router; and you are using bridging on Xen; then it will simply be a case of configuring an IPv6 address on each box. Configuring IPv6 can be done several ways, and that depends on how the routers are configured. At it's simplest, the router(s) will advertise themselves and your devices can self-assign an address - auto configuration which should "just work". For hosting, you probably want to manually configure IPv6 addresses so they are fixed. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Wed Feb 06 12:01:28 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 06 Feb 2013 12:01: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 1U33ff-0007fh-U3; Wed, 06 Feb 2013 12:00:11 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U33fb-0007fJ-Sn for xen-users@lists.xen.org; Wed, 06 Feb 2013 12:00:10 +0000 Received: from [85.158.137.99:63590] by server-9.bemta-3.messagelabs.com id 0B/D5-09484-7C542115; Wed, 06 Feb 2013 12:00:07 +0000 X-Env-Sender: linux@thehobsons.co.uk X-Msg-Ref: server-5.tower-217.messagelabs.com!1360152004!15524350!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.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 16514 invoked from network); 6 Feb 2013 12:00:05 -0000 Received: from patsy.thehobsons.co.uk (HELO patsy.thehobsons.co.uk) (81.174.135.208) by server-5.tower-217.messagelabs.com with SMTP; 6 Feb 2013 12:00:05 -0000 Received: from localhost (localhost [127.0.0.1]) by patsy.thehobsons.co.uk (Postfix) with ESMTP id B0DA310401A for ; Wed, 6 Feb 2013 12:00:02 +0000 (GMT) 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 kbuG3jtqErhb for ; Wed, 6 Feb 2013 12:00:02 +0000 (GMT) Received: from localhost (patsy.thehobsons.co.uk [192.168.0.33]) by patsy.thehobsons.co.uk (Postfix) with ESMTP id E5F8829F28 for ; Wed, 6 Feb 2013 12:00:01 +0000 (GMT) From: "Simon Hobson" To: xen-users@lists.xen.org Date: Wed, 6 Feb 2013 12:00:02 +0000 X-Priority: 3 X-Mailer: MailForge 3.0 Mac OS X Message-ID: <07C333514DC1233EBC29AFA91F4B2FC6@thehobsons.co.uk> Subject: Re: [Xen-users] Using Ipv4 and IPv6 Subnet X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org Thore wrote: >I have a problem/question for understanding. >I have on my server (debian wheezy) 3 virtual systems running on xen >with own IPv4 addresses. >Form my hoster I got an IPv6 subnet, but I don't really know how to add it. >Is it enought to add an address of it in the /etc/network/interfaces of >the virtual systems? >Or must I set up routing for Xen and how does it works together with >bridging? >Which settings I had to change? >And am I able to set up an system only with Ipv6? >(I have IPv6) These are mostly not really Xen questions, more a general networking issue. The first question is, how does the hoster present your networking ? And how is your Xen networking set up ? If (for example) your hoster presents you an ethernet cable, with your own IP range and a gateway address for their router; and you are using bridging on Xen; then it will simply be a case of configuring an IPv6 address on each box. Configuring IPv6 can be done several ways, and that depends on how the routers are configured. At it's simplest, the router(s) will advertise themselves and your devices can self-assign an address - auto configuration which should "just work". For hosting, you probably want to manually configure IPv6 addresses so they are fixed. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Wed Feb 06 13:10:32 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 06 Feb 2013 13:10: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 1U34kp-0001ZD-V2; Wed, 06 Feb 2013 13:09:35 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U2qEq-0001xV-Lf for xen-users@lists.xen.org; Tue, 05 Feb 2013 21:39:36 +0000 Received: from [85.158.139.211:35161] by server-16.bemta-5.messagelabs.com id F6/93-14948-71C71115; Tue, 05 Feb 2013 21:39:35 +0000 X-Env-Sender: linuxhack2012@gmail.com X-Msg-Ref: server-3.tower-206.messagelabs.com!1360100373!19564020!1 X-Originating-IP: [209.85.216.50] 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.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 17656 invoked from network); 5 Feb 2013 21:39:34 -0000 Received: from mail-qa0-f50.google.com (HELO mail-qa0-f50.google.com) (209.85.216.50) by server-3.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 5 Feb 2013 21:39:34 -0000 Received: by mail-qa0-f50.google.com with SMTP id dx4so361873qab.16 for ; Tue, 05 Feb 2013 13:39:33 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:content-type; bh=sUptUlmxwUpndJUDshdeJGM4ZkDAVmH4ZfeH7xeV23U=; b=X4nLHOMzq9qHG5jgtFkpyS/8pphShw1UUZrL6yAJQyCeFFLv3RdzvnEUG5/HnXwU9+ f1MdqXH6EC9ksC2zHQNXoyasTm4UaCyzpwFqRRYi7a5HEUjqevC7ZFnBzAW5EsYxuXYY g81H1jBslf0WtSobJssQiHIJmEr/hL+UZPEtYhBaF7XXns2rGozoX8tRqKXRNmMT9sIo FPI/uYxqC3HyADk9krg4gVM7OZI0yMa+46lIQJ9HBO2k3GSh4lziwKVxNTB6bNoFm5ov mrVjzfN38My/5IQ8+srFX7x6e6QVCosd05MCQKm25F2EROGoEQHzA7jP2aRQp3pUQQE1 U58A== MIME-Version: 1.0 X-Received: by 10.224.44.197 with SMTP id b5mr20276353qaf.65.1360100373601; Tue, 05 Feb 2013 13:39:33 -0800 (PST) Received: by 10.49.52.66 with HTTP; Tue, 5 Feb 2013 13:39:33 -0800 (PST) In-Reply-To: References: Date: Wed, 6 Feb 2013 03:09:33 +0530 Message-ID: From: Linux Hack To: "xen-users@lists.xen.org" X-Mailman-Approved-At: Wed, 06 Feb 2013 13:09:34 +0000 Subject: Re: [Xen-users] Reg XSA39 X-BeenThere: xen-users@lists.xen.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="===============7336433449153976382==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============7336433449153976382== Content-Type: multipart/alternative; boundary=20cf3074ba9ca09e8304d5010bb1 --20cf3074ba9ca09e8304d5010bb1 Content-Type: text/plain; charset=ISO-8859-1 hi, I guess this needs to be patched into kernel-xen instead of xen hypervisior right? On Wed, Feb 6, 2013 at 2:56 AM, Linux Hack wrote: > Hi, > > I am unable to apply this patch on Xen-4.1.4 and seems the > file /drivers/xen/netback/common.h doesn't exists. > > =========== > Patch #39 (xsa39-classic-0001-xen-netback-garbage-ring.patch): > + patch -p1 -s > The text leading up to this was: > -------------------------- > |netback: shutdown the ring if it contains garbage > | > |A buggy or malicious frontend should not be able to confuse netback. > |If we spot anything which is not as it should be then shutdown the > |device and don't try to continue with the ring in a potentially > |hostile state. Well behaved and non-hostile frontends will not be > |penalised. > | > |As well as making the existing checks for such errors fatal also add a > |new check that ensures that there isn't an insane number of requests > |on the ring (i.e. more than would fit in the ring). If the ring > |contains garbage then previously is was possible to loop over this > |insane number, getting an error each time and therefore not generating > |any more pending requests and therefore not exiting the loop in > |xen_netbk_tx_build_gops for an externded period. > | > |Also turn various netdev_dbg calls which no precipitate a fatal error > |into netdev_err, they are rate limited because the device is shutdown > |afterwards. > | > |This fixes at least one known DoS/softlockup of the backend domain. > | > |Signed-off-by: Ian Campbell > |Signed-off-by: Jan Beulich > | > |--- a/drivers/xen/netback/common.h > |+++ b/drivers/xen/netback/common.h > -------------------------- > File to patch: > ================= > > Any help that would be great! > > --20cf3074ba9ca09e8304d5010bb1 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
hi,

I guess this needs to be patched in= to kernel-xen instead of xen hypervisior right?

<= div class=3D"gmail_extra">

On Wed, Feb 6,= 2013 at 2:56 AM, Linux Hack <linuxhack2012@gmail.com>= wrote:
Hi,

I am= unable to apply this patch on Xen-4.1.4 and seems the file=A0/drivers/xen/= netback/common.h doesn't exists.

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
Patch = #39 (xsa39-classic-0001-xen-netback-garbage-ring.patch):
+ patch -p1 -s
The text leading up to this was:
--= ------------------------
|netback: shutdown the ring if it contai= ns garbage
|
|A buggy or malicious frontend should not = be able to confuse netback.
|If we spot anything which is not as it should be then shutdown the
|device and don't try to continue with the ring in a potentiall= y
|hostile state. Well behaved and non-hostile frontends will not= be
|penalised.
|
|As well as making the existing chec= ks for such errors fatal also add a
|new check that ensures that = there isn't an insane number of requests
|on the ring (i.e. m= ore than would fit in the ring). If the ring
|contains garbage then previously is was possible to loop over this
|insane number, getting an error each time and therefore not genera= ting
|any more pending requests and therefore not exiting the loo= p in
|xen_netbk_tx_build_gops for an externded period.
|
|Also turn various netdev_dbg calls which no precipitate a fatal error
|into netdev_err, they are rate limited because the device is shutd= own
|afterwards.
|
|This fixes at least one known DoS/= softlockup of the backend domain.
|
|Signed-off-by: Ian= Campbell <= ian.campbell@citrix.com>
|Signed-off-by: Jan Beulich <JBeulich@suse.com>
|
|--- a/dri= vers/xen/netback/common.h
|+++ b/drivers/xen/netback/common.h
--------------------------
File to patch:
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D

Any help that would be great!


--20cf3074ba9ca09e8304d5010bb1-- --===============7336433449153976382== 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 --===============7336433449153976382==-- From xen-users-bounces@lists.xen.org Wed Feb 06 13:10:32 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 06 Feb 2013 13:10: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 1U34kh-0001Yo-A7; Wed, 06 Feb 2013 13:09:27 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U2q24-0001kN-Nn for xen-users@lists.xen.org; Tue, 05 Feb 2013 21:26:24 +0000 Received: from [85.158.137.99:11461] by server-4.bemta-3.messagelabs.com id FB/F6-12802-FF871115; Tue, 05 Feb 2013 21:26:23 +0000 X-Env-Sender: linuxhack2012@gmail.com X-Msg-Ref: server-13.tower-217.messagelabs.com!1360099581!20153518!1 X-Originating-IP: [209.85.216.169] 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.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 18700 invoked from network); 5 Feb 2013 21:26:22 -0000 Received: from mail-qc0-f169.google.com (HELO mail-qc0-f169.google.com) (209.85.216.169) by server-13.tower-217.messagelabs.com with RC4-SHA encrypted SMTP; 5 Feb 2013 21:26:22 -0000 Received: by mail-qc0-f169.google.com with SMTP id t2so256467qcq.0 for ; Tue, 05 Feb 2013 13:26:21 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:date:message-id:subject:from:to :content-type; bh=pW8js1gRN6jgL6DBN5bdGRUmrSrwqYe7N6jcXTkGapk=; b=TcVUMy0NVERjee+KqYNuueCBlJtfs/0rzAS4ZlzK9/tYSt/G32ir9HeB/XjzLbDzPI 4NOoxpOgg+IhvkPISErTVC+Br5mJS63ts0J6RmQglwy2eIePC8VIM7/adWf5+3Ft0WBO OixNB11OlmfMQX/wTH7qiIUW7A63NUKHBdX5nvcOKu58JPQXTtdkN8z/Ko4xUzeRqU+a Ur1+PQhgromSPHJYK3X/BDEyDEV/gd3Re/JjOwBrvpx86Zw+UCt9xAL1JeuPWLXDqOtr hHYx/8QEfAPAxUbv2I27lF6yKEBY0hioVtiYULf/iEWa/cCKWQxQ3IWz1qEW4uH003qk f7dA== MIME-Version: 1.0 X-Received: by 10.49.74.73 with SMTP id r9mr23314107qev.44.1360099581257; Tue, 05 Feb 2013 13:26:21 -0800 (PST) Received: by 10.49.52.66 with HTTP; Tue, 5 Feb 2013 13:26:21 -0800 (PST) Date: Wed, 6 Feb 2013 02:56:21 +0530 Message-ID: From: Linux Hack To: "xen-users@lists.xen.org" X-Mailman-Approved-At: Wed, 06 Feb 2013 13:09:25 +0000 Subject: [Xen-users] Reg XSA39 X-BeenThere: xen-users@lists.xen.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="===============4654336744809922058==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============4654336744809922058== Content-Type: multipart/alternative; boundary=047d7bdc11466666c904d500dc0f --047d7bdc11466666c904d500dc0f Content-Type: text/plain; charset=ISO-8859-1 Hi, I am unable to apply this patch on Xen-4.1.4 and seems the file /drivers/xen/netback/common.h doesn't exists. =========== Patch #39 (xsa39-classic-0001-xen-netback-garbage-ring.patch): + patch -p1 -s The text leading up to this was: -------------------------- |netback: shutdown the ring if it contains garbage | |A buggy or malicious frontend should not be able to confuse netback. |If we spot anything which is not as it should be then shutdown the |device and don't try to continue with the ring in a potentially |hostile state. Well behaved and non-hostile frontends will not be |penalised. | |As well as making the existing checks for such errors fatal also add a |new check that ensures that there isn't an insane number of requests |on the ring (i.e. more than would fit in the ring). If the ring |contains garbage then previously is was possible to loop over this |insane number, getting an error each time and therefore not generating |any more pending requests and therefore not exiting the loop in |xen_netbk_tx_build_gops for an externded period. | |Also turn various netdev_dbg calls which no precipitate a fatal error |into netdev_err, they are rate limited because the device is shutdown |afterwards. | |This fixes at least one known DoS/softlockup of the backend domain. | |Signed-off-by: Ian Campbell |Signed-off-by: Jan Beulich | |--- a/drivers/xen/netback/common.h |+++ b/drivers/xen/netback/common.h -------------------------- File to patch: ================= Any help that would be great! --047d7bdc11466666c904d500dc0f Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Hi,

I am unable to apply this patch on = Xen-4.1.4 and seems the file=A0/drivers/xen/netback/common.h doesn't ex= ists.

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
=
Patch #39 (xsa39-classic-0001-xen-netback-garbage-ring.patch):
+ patch -p1 -s
The text leading up to this was:
--= ------------------------
|netback: shutdown the ring if it contai= ns garbage
|
|A buggy or malicious frontend should not = be able to confuse netback.
|If we spot anything which is not as it should be then shutdown the
|device and don't try to continue with the ring in a potentiall= y
|hostile state. Well behaved and non-hostile frontends will not= be
|penalised.
|
|As well as making the existing chec= ks for such errors fatal also add a
|new check that ensures that = there isn't an insane number of requests
|on the ring (i.e. m= ore than would fit in the ring). If the ring
|contains garbage then previously is was possible to loop over this
|insane number, getting an error each time and therefore not genera= ting
|any more pending requests and therefore not exiting the loo= p in
|xen_netbk_tx_build_gops for an externded period.
|
|Also turn various netdev_dbg calls which no precipitate a fatal error
|into netdev_err, they are rate limited because the device is shutd= own
|afterwards.
|
|This fixes at least one known DoS/= softlockup of the backend domain.
|
|Signed-off-by: Ian= Campbell <ian.campbell@citri= x.com>
|Signed-off-by: Jan Beulich <J= Beulich@suse.com>
|
|--- a/drivers/xen/netback/c= ommon.h
|+++ b/drivers/xen/netback/common.h
-----------= ---------------
File to patch:
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D

Any help that would be great!

--047d7bdc11466666c904d500dc0f-- --===============4654336744809922058== 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 --===============4654336744809922058==-- From xen-users-bounces@lists.xen.org Wed Feb 06 13:10:32 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 06 Feb 2013 13:10: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 1U34kp-0001ZD-V2; Wed, 06 Feb 2013 13:09:35 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U2qEq-0001xV-Lf for xen-users@lists.xen.org; Tue, 05 Feb 2013 21:39:36 +0000 Received: from [85.158.139.211:35161] by server-16.bemta-5.messagelabs.com id F6/93-14948-71C71115; Tue, 05 Feb 2013 21:39:35 +0000 X-Env-Sender: linuxhack2012@gmail.com X-Msg-Ref: server-3.tower-206.messagelabs.com!1360100373!19564020!1 X-Originating-IP: [209.85.216.50] 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.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 17656 invoked from network); 5 Feb 2013 21:39:34 -0000 Received: from mail-qa0-f50.google.com (HELO mail-qa0-f50.google.com) (209.85.216.50) by server-3.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 5 Feb 2013 21:39:34 -0000 Received: by mail-qa0-f50.google.com with SMTP id dx4so361873qab.16 for ; Tue, 05 Feb 2013 13:39:33 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:content-type; bh=sUptUlmxwUpndJUDshdeJGM4ZkDAVmH4ZfeH7xeV23U=; b=X4nLHOMzq9qHG5jgtFkpyS/8pphShw1UUZrL6yAJQyCeFFLv3RdzvnEUG5/HnXwU9+ f1MdqXH6EC9ksC2zHQNXoyasTm4UaCyzpwFqRRYi7a5HEUjqevC7ZFnBzAW5EsYxuXYY g81H1jBslf0WtSobJssQiHIJmEr/hL+UZPEtYhBaF7XXns2rGozoX8tRqKXRNmMT9sIo FPI/uYxqC3HyADk9krg4gVM7OZI0yMa+46lIQJ9HBO2k3GSh4lziwKVxNTB6bNoFm5ov mrVjzfN38My/5IQ8+srFX7x6e6QVCosd05MCQKm25F2EROGoEQHzA7jP2aRQp3pUQQE1 U58A== MIME-Version: 1.0 X-Received: by 10.224.44.197 with SMTP id b5mr20276353qaf.65.1360100373601; Tue, 05 Feb 2013 13:39:33 -0800 (PST) Received: by 10.49.52.66 with HTTP; Tue, 5 Feb 2013 13:39:33 -0800 (PST) In-Reply-To: References: Date: Wed, 6 Feb 2013 03:09:33 +0530 Message-ID: From: Linux Hack To: "xen-users@lists.xen.org" X-Mailman-Approved-At: Wed, 06 Feb 2013 13:09:34 +0000 Subject: Re: [Xen-users] Reg XSA39 X-BeenThere: xen-users@lists.xen.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="===============7336433449153976382==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============7336433449153976382== Content-Type: multipart/alternative; boundary=20cf3074ba9ca09e8304d5010bb1 --20cf3074ba9ca09e8304d5010bb1 Content-Type: text/plain; charset=ISO-8859-1 hi, I guess this needs to be patched into kernel-xen instead of xen hypervisior right? On Wed, Feb 6, 2013 at 2:56 AM, Linux Hack wrote: > Hi, > > I am unable to apply this patch on Xen-4.1.4 and seems the > file /drivers/xen/netback/common.h doesn't exists. > > =========== > Patch #39 (xsa39-classic-0001-xen-netback-garbage-ring.patch): > + patch -p1 -s > The text leading up to this was: > -------------------------- > |netback: shutdown the ring if it contains garbage > | > |A buggy or malicious frontend should not be able to confuse netback. > |If we spot anything which is not as it should be then shutdown the > |device and don't try to continue with the ring in a potentially > |hostile state. Well behaved and non-hostile frontends will not be > |penalised. > | > |As well as making the existing checks for such errors fatal also add a > |new check that ensures that there isn't an insane number of requests > |on the ring (i.e. more than would fit in the ring). If the ring > |contains garbage then previously is was possible to loop over this > |insane number, getting an error each time and therefore not generating > |any more pending requests and therefore not exiting the loop in > |xen_netbk_tx_build_gops for an externded period. > | > |Also turn various netdev_dbg calls which no precipitate a fatal error > |into netdev_err, they are rate limited because the device is shutdown > |afterwards. > | > |This fixes at least one known DoS/softlockup of the backend domain. > | > |Signed-off-by: Ian Campbell > |Signed-off-by: Jan Beulich > | > |--- a/drivers/xen/netback/common.h > |+++ b/drivers/xen/netback/common.h > -------------------------- > File to patch: > ================= > > Any help that would be great! > > --20cf3074ba9ca09e8304d5010bb1 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
hi,

I guess this needs to be patched in= to kernel-xen instead of xen hypervisior right?

<= div class=3D"gmail_extra">

On Wed, Feb 6,= 2013 at 2:56 AM, Linux Hack <linuxhack2012@gmail.com>= wrote:
Hi,

I am= unable to apply this patch on Xen-4.1.4 and seems the file=A0/drivers/xen/= netback/common.h doesn't exists.

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
Patch = #39 (xsa39-classic-0001-xen-netback-garbage-ring.patch):
+ patch -p1 -s
The text leading up to this was:
--= ------------------------
|netback: shutdown the ring if it contai= ns garbage
|
|A buggy or malicious frontend should not = be able to confuse netback.
|If we spot anything which is not as it should be then shutdown the
|device and don't try to continue with the ring in a potentiall= y
|hostile state. Well behaved and non-hostile frontends will not= be
|penalised.
|
|As well as making the existing chec= ks for such errors fatal also add a
|new check that ensures that = there isn't an insane number of requests
|on the ring (i.e. m= ore than would fit in the ring). If the ring
|contains garbage then previously is was possible to loop over this
|insane number, getting an error each time and therefore not genera= ting
|any more pending requests and therefore not exiting the loo= p in
|xen_netbk_tx_build_gops for an externded period.
|
|Also turn various netdev_dbg calls which no precipitate a fatal error
|into netdev_err, they are rate limited because the device is shutd= own
|afterwards.
|
|This fixes at least one known DoS/= softlockup of the backend domain.
|
|Signed-off-by: Ian= Campbell <= ian.campbell@citrix.com>
|Signed-off-by: Jan Beulich <JBeulich@suse.com>
|
|--- a/dri= vers/xen/netback/common.h
|+++ b/drivers/xen/netback/common.h
--------------------------
File to patch:
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D

Any help that would be great!


--20cf3074ba9ca09e8304d5010bb1-- --===============7336433449153976382== 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 --===============7336433449153976382==-- From xen-users-bounces@lists.xen.org Wed Feb 06 13:10:32 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 06 Feb 2013 13:10: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 1U34kh-0001Yo-A7; Wed, 06 Feb 2013 13:09:27 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U2q24-0001kN-Nn for xen-users@lists.xen.org; Tue, 05 Feb 2013 21:26:24 +0000 Received: from [85.158.137.99:11461] by server-4.bemta-3.messagelabs.com id FB/F6-12802-FF871115; Tue, 05 Feb 2013 21:26:23 +0000 X-Env-Sender: linuxhack2012@gmail.com X-Msg-Ref: server-13.tower-217.messagelabs.com!1360099581!20153518!1 X-Originating-IP: [209.85.216.169] 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.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 18700 invoked from network); 5 Feb 2013 21:26:22 -0000 Received: from mail-qc0-f169.google.com (HELO mail-qc0-f169.google.com) (209.85.216.169) by server-13.tower-217.messagelabs.com with RC4-SHA encrypted SMTP; 5 Feb 2013 21:26:22 -0000 Received: by mail-qc0-f169.google.com with SMTP id t2so256467qcq.0 for ; Tue, 05 Feb 2013 13:26:21 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:date:message-id:subject:from:to :content-type; bh=pW8js1gRN6jgL6DBN5bdGRUmrSrwqYe7N6jcXTkGapk=; b=TcVUMy0NVERjee+KqYNuueCBlJtfs/0rzAS4ZlzK9/tYSt/G32ir9HeB/XjzLbDzPI 4NOoxpOgg+IhvkPISErTVC+Br5mJS63ts0J6RmQglwy2eIePC8VIM7/adWf5+3Ft0WBO OixNB11OlmfMQX/wTH7qiIUW7A63NUKHBdX5nvcOKu58JPQXTtdkN8z/Ko4xUzeRqU+a Ur1+PQhgromSPHJYK3X/BDEyDEV/gd3Re/JjOwBrvpx86Zw+UCt9xAL1JeuPWLXDqOtr hHYx/8QEfAPAxUbv2I27lF6yKEBY0hioVtiYULf/iEWa/cCKWQxQ3IWz1qEW4uH003qk f7dA== MIME-Version: 1.0 X-Received: by 10.49.74.73 with SMTP id r9mr23314107qev.44.1360099581257; Tue, 05 Feb 2013 13:26:21 -0800 (PST) Received: by 10.49.52.66 with HTTP; Tue, 5 Feb 2013 13:26:21 -0800 (PST) Date: Wed, 6 Feb 2013 02:56:21 +0530 Message-ID: From: Linux Hack To: "xen-users@lists.xen.org" X-Mailman-Approved-At: Wed, 06 Feb 2013 13:09:25 +0000 Subject: [Xen-users] Reg XSA39 X-BeenThere: xen-users@lists.xen.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="===============4654336744809922058==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============4654336744809922058== Content-Type: multipart/alternative; boundary=047d7bdc11466666c904d500dc0f --047d7bdc11466666c904d500dc0f Content-Type: text/plain; charset=ISO-8859-1 Hi, I am unable to apply this patch on Xen-4.1.4 and seems the file /drivers/xen/netback/common.h doesn't exists. =========== Patch #39 (xsa39-classic-0001-xen-netback-garbage-ring.patch): + patch -p1 -s The text leading up to this was: -------------------------- |netback: shutdown the ring if it contains garbage | |A buggy or malicious frontend should not be able to confuse netback. |If we spot anything which is not as it should be then shutdown the |device and don't try to continue with the ring in a potentially |hostile state. Well behaved and non-hostile frontends will not be |penalised. | |As well as making the existing checks for such errors fatal also add a |new check that ensures that there isn't an insane number of requests |on the ring (i.e. more than would fit in the ring). If the ring |contains garbage then previously is was possible to loop over this |insane number, getting an error each time and therefore not generating |any more pending requests and therefore not exiting the loop in |xen_netbk_tx_build_gops for an externded period. | |Also turn various netdev_dbg calls which no precipitate a fatal error |into netdev_err, they are rate limited because the device is shutdown |afterwards. | |This fixes at least one known DoS/softlockup of the backend domain. | |Signed-off-by: Ian Campbell |Signed-off-by: Jan Beulich | |--- a/drivers/xen/netback/common.h |+++ b/drivers/xen/netback/common.h -------------------------- File to patch: ================= Any help that would be great! --047d7bdc11466666c904d500dc0f Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Hi,

I am unable to apply this patch on = Xen-4.1.4 and seems the file=A0/drivers/xen/netback/common.h doesn't ex= ists.

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
=
Patch #39 (xsa39-classic-0001-xen-netback-garbage-ring.patch):
+ patch -p1 -s
The text leading up to this was:
--= ------------------------
|netback: shutdown the ring if it contai= ns garbage
|
|A buggy or malicious frontend should not = be able to confuse netback.
|If we spot anything which is not as it should be then shutdown the
|device and don't try to continue with the ring in a potentiall= y
|hostile state. Well behaved and non-hostile frontends will not= be
|penalised.
|
|As well as making the existing chec= ks for such errors fatal also add a
|new check that ensures that = there isn't an insane number of requests
|on the ring (i.e. m= ore than would fit in the ring). If the ring
|contains garbage then previously is was possible to loop over this
|insane number, getting an error each time and therefore not genera= ting
|any more pending requests and therefore not exiting the loo= p in
|xen_netbk_tx_build_gops for an externded period.
|
|Also turn various netdev_dbg calls which no precipitate a fatal error
|into netdev_err, they are rate limited because the device is shutd= own
|afterwards.
|
|This fixes at least one known DoS/= softlockup of the backend domain.
|
|Signed-off-by: Ian= Campbell <ian.campbell@citri= x.com>
|Signed-off-by: Jan Beulich <J= Beulich@suse.com>
|
|--- a/drivers/xen/netback/c= ommon.h
|+++ b/drivers/xen/netback/common.h
-----------= ---------------
File to patch:
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D

Any help that would be great!

--047d7bdc11466666c904d500dc0f-- --===============4654336744809922058== 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 --===============4654336744809922058==-- From xen-users-bounces@lists.xen.org Wed Feb 06 13:10:32 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 06 Feb 2013 13:10: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 1U34kq-0001ZO-Iz; Wed, 06 Feb 2013 13:09:36 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U2tSi-0002ZD-30 for xen-users@lists.xen.org; Wed, 06 Feb 2013 01:06:08 +0000 Received: from [85.158.138.51:26657] by server-8.bemta-3.messagelabs.com id C7/0F-25687-F7CA1115; Wed, 06 Feb 2013 01:06:07 +0000 X-Env-Sender: linuxhack2012@gmail.com X-Msg-Ref: server-5.tower-174.messagelabs.com!1360112753!28984618!1 X-Originating-IP: [209.85.216.174] 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.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 13900 invoked from network); 6 Feb 2013 01:05:54 -0000 Received: from mail-qc0-f174.google.com (HELO mail-qc0-f174.google.com) (209.85.216.174) by server-5.tower-174.messagelabs.com with RC4-SHA encrypted SMTP; 6 Feb 2013 01:05:54 -0000 Received: by mail-qc0-f174.google.com with SMTP id z24so319373qcq.33 for ; Tue, 05 Feb 2013 17:04:53 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:date:message-id:subject:from:to :content-type; bh=J0RuoZOgWQFVjO0mxIKknJt64Bv9fvAKEvVjepcIE5U=; b=P9TNrjsyUNvLNMCDAHn025Ghylr2PmIu+9K+6080TQKar3miPp510L8+I+X33qXB5g jBuZ+cO6I/0BHMIL2Yl5WNQTVIE6lsS+vqd2CR8y2qab6Pdx7d7ldiGdJ9olRO7IZ2PR +5TdUJe3HNtcKOPE5HKTmRJNM6ZJnkauQyVfKtWE9HpbR5mTbS34bTKwlDDkkxesVDRX V4k4v8vhsj4mgO5fqtE4SdsVHpLpLuOYzqgRuk5oNr/QcmYXK00UXoX6hp9iWwuXOEPQ 8eH/LNajBrCOqo/VA96ySwTub8bj9VdIJORLwhcfSw/2IgILLmQzjXKkimTqyEuWzcCB KqJA== MIME-Version: 1.0 X-Received: by 10.49.84.104 with SMTP id x8mr24411861qey.5.1360112693752; Tue, 05 Feb 2013 17:04:53 -0800 (PST) Received: by 10.49.52.66 with HTTP; Tue, 5 Feb 2013 17:04:53 -0800 (PST) Date: Wed, 6 Feb 2013 06:34:53 +0530 Message-ID: From: Linux Hack To: "xen-users@lists.xen.org" X-Mailman-Approved-At: Wed, 06 Feb 2013 13:09:34 +0000 Subject: [Xen-users] xsa33 patch 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="===============7245692077915726269==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============7245692077915726269== Content-Type: multipart/alternative; boundary=047d7bdc1728f7342f04d503e911 --047d7bdc1728f7342f04d503e911 Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable Hi, I am trying to apply the patch xsa33 to the source and making rpm to install on our server. But this patch doesn't working for Xen-4.1.4 source and I am getting the below error when I make rpm with this patch applied. =3D=3D=3D=3D=3D=3D=3D=3D=3D gcc -O2 -fomit-frame-pointer -m64 -fno-strict-aliasing -std=3Dgnu99 -Wall -Wstrict-prototypes -Wno-unused-value -Wdeclaration-after-statement -DNDEBUG -nostdinc -fno-builtin -fno-common -Wredundant-decls -iwithprefix include -Werror -Wno-pointer-arith -pipe -I/usr/src/redhat/BUILD/xen-4.1.4/xen/include -I/usr/src/redhat/BUILD/xen-4.1.4/xen/include/asm-x86/mach-generic -I/usr/src/redhat/BUILD/xen-4.1.4/xen/include/asm-x86/mach-default -msoft-float -fno-stack-protector -fno-exceptions -mno-red-zone -fpic -fno-asynchronous-unwind-tables -DGCC_HAS_VISIBILITY_ATTRIBUTE -g -D__XEN__ -MMD -MF .qinval.o.d -c qinval.c -o qinval.o gcc -O2 -fomit-frame-pointer -m64 -fno-strict-aliasing -std=3Dgnu99 -Wall -Wstrict-prototypes -Wno-unused-value -Wdeclaration-after-statement -DNDEBUG -nostdinc -fno-builtin -fno-common -Wredundant-decls -iwithprefix include -Werror -Wno-pointer-arith -pipe -I/usr/src/redhat/BUILD/xen-4.1.4/xen/include -I/usr/src/redhat/BUILD/xen-4.1.4/xen/include/asm-x86/mach-generic -I/usr/src/redhat/BUILD/xen-4.1.4/xen/include/asm-x86/mach-default -msoft-float -fno-stack-protector -fno-exceptions -mno-red-zone -fpic -fno-asynchronous-unwind-tables -DGCC_HAS_VISIBILITY_ATTRIBUTE -g -D__XEN__ -MMD -MF .intremap.o.d -c intremap.c -o intremap.o intremap.c: In function =91set_msi_source_id=92: intremap.c:502: error: =91SVT_VERIFY_BUS_SQ=92 undeclared (first use in thi= s function) intremap.c:502: error: (Each undeclared identifier is reported only once intremap.c:502: error: for each function it appears in.) make[6]: *** [intremap.o] Error 1 make[6]: Leaving directory `/usr/src/redhat/BUILD/xen-4.1.4/xen/drivers/passthrough/vtd' make[5]: *** [vtd/built_in.o] Error 2 make[5]: Leaving directory `/usr/src/redhat/BUILD/xen-4.1.4/xen/drivers/passthrough' make[4]: *** [passthrough/built_in.o] Error 2 make[4]: Leaving directory `/usr/src/redhat/BUILD/xen-4.1.4/xen/drivers' make[3]: *** [/usr/src/redhat/BUILD/xen-4.1.4/xen/drivers/built_in.o] Error 2 make[3]: Leaving directory `/usr/src/redhat/BUILD/xen-4.1.4/xen/arch/x86' make[2]: *** [/usr/src/redhat/BUILD/xen-4.1.4/xen/xen] Error 2 make[2]: Leaving directory `/usr/src/redhat/BUILD/xen-4.1.4/xen' make[1]: *** [install] Error 2 make[1]: Leaving directory `/usr/src/redhat/BUILD/xen-4.1.4/xen' make: *** [install-xen] Error 2 error: Bad exit status from /var/tmp/rpm-tmp.86045 (%build) =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D Any suggestion would be great. --047d7bdc1728f7342f04d503e911 Content-Type: text/html; charset=windows-1252 Content-Transfer-Encoding: quoted-printable
Hi,

I am trying to apply the patch xsa3= 3 to the source and making rpm to install on our server. But this patch doe= sn't working for Xen-4.1.4 source and I am getting the below error when= I make rpm with this patch applied.

=3D=3D=3D=3D=3D=3D=3D=3D=3D
gcc -O2 -fom= it-frame-pointer -m64 -fno-strict-aliasing -std=3Dgnu99 -Wall -Wstrict-prot= otypes -Wno-unused-value -Wdeclaration-after-statement =A0-DNDEBUG -nostdin= c -fno-builtin -fno-common -Wredundant-decls -iwithprefix include -Werror -= Wno-pointer-arith -pipe -I/usr/src/redhat/BUILD/xen-4.1.4/xen/include =A0-I= /usr/src/redhat/BUILD/xen-4.1.4/xen/include/asm-x86/mach-generic -I/usr/src= /redhat/BUILD/xen-4.1.4/xen/include/asm-x86/mach-default -msoft-float -fno-= stack-protector -fno-exceptions -mno-red-zone -fpic -fno-asynchronous-unwin= d-tables -DGCC_HAS_VISIBILITY_ATTRIBUTE -g -D__XEN__ -MMD -MF .qinval.o.d -= c qinval.c -o qinval.o
gcc -O2 -fomit-frame-pointer -m64 -fno-strict-aliasing -std=3Dgnu99 -W= all -Wstrict-prototypes -Wno-unused-value -Wdeclaration-after-statement =A0= -DNDEBUG -nostdinc -fno-builtin -fno-common -Wredundant-decls -iwithprefix = include -Werror -Wno-pointer-arith -pipe -I/usr/src/redhat/BUILD/xen-4.1.4/= xen/include =A0-I/usr/src/redhat/BUILD/xen-4.1.4/xen/include/asm-x86/mach-g= eneric -I/usr/src/redhat/BUILD/xen-4.1.4/xen/include/asm-x86/mach-default -= msoft-float -fno-stack-protector -fno-exceptions -mno-red-zone -fpic -fno-a= synchronous-unwind-tables -DGCC_HAS_VISIBILITY_ATTRIBUTE -g -D__XEN__ -MMD = -MF .intremap.o.d -c intremap.c -o intremap.o
intremap.c: In function =91set_msi_source_id=92:
intremap.c:= 502: error: =91SVT_VERIFY_BUS_SQ=92 undeclared (first use in this function)=
intremap.c:502: error: (Each undeclared identifier is reported o= nly once
intremap.c:502: error: for each function it appears in.)
mak= e[6]: *** [intremap.o] Error 1
make[6]: Leaving directory `/usr/s= rc/redhat/BUILD/xen-4.1.4/xen/drivers/passthrough/vtd'
make[5= ]: *** [vtd/built_in.o] Error 2
make[5]: Leaving directory `/usr/src/redhat/BUILD/xen-4.1.4/xen/driver= s/passthrough'
make[4]: *** [passthrough/built_in.o] Error 2<= /div>
make[4]: Leaving directory `/usr/src/redhat/BUILD/xen-4.1.4/xen/d= rivers'
make[3]: *** [/usr/src/redhat/BUILD/xen-4.1.4/xen/drivers/built_in.o] = Error 2
make[3]: Leaving directory `/usr/src/redhat/BUILD/xen-4.1= .4/xen/arch/x86'
make[2]: *** [/usr/src/redhat/BUILD/xen-4.1.= 4/xen/xen] Error 2
make[2]: Leaving directory `/usr/src/redhat/BUILD/xen-4.1.4/xen'
make[1]: *** [install] Error 2
make[1]: Leaving director= y `/usr/src/redhat/BUILD/xen-4.1.4/xen'
make: *** [install-xe= n] Error 2
error: Bad exit status from /var/tmp/rpm-tmp.86045 (%build)
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

Any = suggestion would be great.

--047d7bdc1728f7342f04d503e911-- --===============7245692077915726269== 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 --===============7245692077915726269==-- From xen-users-bounces@lists.xen.org Wed Feb 06 13:10:32 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 06 Feb 2013 13:10: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 1U34kr-0001ZY-8L; Wed, 06 Feb 2013 13:09:37 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U2v0k-000682-PB for xen-users@lists.xen.org; Wed, 06 Feb 2013 02:45:23 +0000 Received: from [85.158.137.99:62002] by server-2.bemta-3.messagelabs.com id AB/56-25961-CB3C1115; Wed, 06 Feb 2013 02:45:16 +0000 X-Env-Sender: ydev@cs.utah.edu X-Msg-Ref: server-9.tower-217.messagelabs.com!1360118715!16992045!1 X-Originating-IP: [155.98.64.241] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 18808 invoked from network); 6 Feb 2013 02:45:15 -0000 Received: from rio.cs.utah.edu (HELO mail-svr1.cs.utah.edu) (155.98.64.241) by server-9.tower-217.messagelabs.com with SMTP; 6 Feb 2013 02:45:15 -0000 Received: from localhost (localhost [127.0.0.1]) by mail-svr1.cs.utah.edu (Postfix) with ESMTP id 33A836500CB; Tue, 5 Feb 2013 19:45:14 -0700 (MST) X-Virus-Scanned: amavisd-new at cs.utah.edu Received: from mail-svr1.cs.utah.edu ([127.0.0.1]) by localhost (mail-svr1.cs.utah.edu [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sFMVDMafrif1; Tue, 5 Feb 2013 19:45:13 -0700 (MST) Received: from [192.168.1.16] (c-76-23-15-81.hsd1.ut.comcast.net [76.23.15.81]) by smtps.cs.utah.edu (Postfix) with ESMTPSA id 22CCA6500C7; Tue, 5 Feb 2013 19:45:13 -0700 (MST) Message-ID: <5111C3B6.1070705@cs.utah.edu> Date: Tue, 05 Feb 2013 19:45:10 -0700 From: Yathindra User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130107 Thunderbird/17.0.2 MIME-Version: 1.0 To: =?ISO-8859-1?Q?Roger_Pau_Monn=E9?= References: <510DC655.5060205@cs.utah.edu> <510E3195.1010004@citrix.com> <510EA374.6060509@cs.utah.edu> <5110D7EC.8040608@citrix.com> <51113D59.7030003@cs.utah.edu> <51114B35.5050202@citrix.com> In-Reply-To: <51114B35.5050202@citrix.com> X-Mailman-Approved-At: Wed, 06 Feb 2013 13:09:34 +0000 Cc: "xen-users@lists.xen.org" Subject: Re: [Xen-users] xen_blkbk times out before getting connected X-BeenThere: xen-users@lists.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 2/5/2013 11:11 AM, Roger Pau Monn=E9 wrote: > On 05/02/13 18:11, Yathindra wrote: >> DomU configuration file looks like this: > Please don't do top posting. > >> kernel =3D "/boot/vmlinuz-3.8.0-rc5+" >> ramdisk =3D "/boot/initrd.img-3.8.0-rc5+" >> memory =3D 500 >> name =3D "guest2" >> disk =3D ['phy:/dev/loop0,sda1,w'] > Why are you using sda1 instead of xvda1? > >> root =3D "/dev/disk/by-path/xen-vbd-2049 ro" >> extra =3D 'xencons=3Dtty' > You can use: > > extra=3D"root=3D/dev/xvda1" > >> On 2/5/2013 2:59 AM, Roger Pau Monn=E9 wrote: >>> On 03/02/13 18:50, Yathindra wrote: >>>> I'm using the latest linux kernel 3.8.0 with Xen 4.3-unstable. Xenstor= ed >>>> is being started at boot time. >>>> I did not see any message (dmesg/syslog/console) about device being >>>> plugged in but xenstore-ls shows me all >>>> the entries backend and frontend. >>> Could you post your DomU configuration file also? >>> >>>> Here are some details >>>> ------------------------------ >>>> From /var/log/syslog: >>>> >>>> Feb 3 10:37:31 localhost kernel: [ 36.466359] Event-channel device >>>> installed. >>>> Feb 3 10:37:31 localhost kernel: [ 36.636358] Register >>>> xen_blkbk_driver <<< custom debug message I added >>>> Feb 3 10:37:31 localhost kernel: [ 36.636367] >>>> xenbus_register_backend <<< custom debug message I added >>>> Feb 3 10:37:31 localhost kernel: [ 36.683533] xenbus_register_backe= nd >>>> Feb 3 10:37:31 localhost kernel: [ 36.830115] xen-pciback: backend = is >>>> vpci <<< custom debug message I added >>>> Feb 3 10:37:31 localhost kernel: [ 36.830123] >>>> xenbus_register_backend <<< custom debug message I added >>>> Feb 3 10:37:32 localhost xenstored: Checking store ... >>>> Feb 3 10:37:32 localhost xenstored: Checking store complete. >>>> Feb 3 10:37:32 localhost kernel: [ 37.075217] xenbus_probe: xenstor= ed >>>> is ready <<< custom debug message I added >>>> Feb 3 10:37:32 localhost kernel: [ 37.075230] watching node >>>> FFFFFFFF81C7D1A0 >>>> Feb 3 10:37:32 localhost kernel: [ 37.081309] xenbus_scanf for node= cpu/0 >>>> Feb 3 10:37:32 localhost kernel: [ 37.081327] XENBUS xen store gave: >>>> unknown error cpu >>>> Feb 3 10:37:32 localhost kernel: [ 37.081333] xenbus_scanf for node= cpu/1 >>>> Feb 3 10:37:32 localhost kernel: [ 37.085327] XENBUS unexpected type >>>> [17], expected [2] >>>> Feb 3 10:37:32 localhost kernel: [ 37.085342] watching node >>>> FFFFFFFF81C7D0C0 >>>> Feb 3 10:37:32 localhost kernel: [ 37.086857] XENBUS unexpected type >>>> [17], expected [4] >>>> Feb 3 10:37:32 localhost kernel: [ 37.086865] Failed to set shutdown >>>> watcher >>>> Feb 3 10:37:32 localhost kernel: [ 37.086880] backend_probe_and_wat= ch >>>> - enumerates devices in xenstore and watches for changes <<< custom >>>> debug message I added >>>> Feb 3 10:37:32 localhost kernel: [ 37.089401] XENBUS unexpected type >>>> [4], expected [1] >>>> Feb 3 10:37:32 localhost kernel: [ 37.089411] watching node >>>> FFFFFFFF81C7D660 >>>> Feb 3 10:37:32 localhost kernel: [ 37.090715] XENBUS xen store gave: >>>> unknown error control/shutdown >>>> Feb 3 10:37:32 localhost kernel: [ 37.090725] >>>> frontend_probe_and_watch: calling xenbus_probe_devices <<< custom debug >>>> message I added >>>> Feb 3 10:37:32 localhost kernel: [ 37.092362] XENBUS unexpected type >>>> [17], expected [1] >>>> Feb 3 10:37:32 localhost kernel: [ 37.092376] watching node >>>> FFFFFFFF81C7D820 >>>> Feb 3 10:37:32 localhost kernel: [ 37.093334] watching node >>>> FFFFFFFF81C7DB20 >>>> Feb 3 10:37:32 localhost kernel: [ 37.094454] XENBUS xen store gave: >>>> unknown error backend <<< still not sure how critical this is >>>> Feb 3 10:37:32 localhost kernel: [ 37.094463] Failed to set balloon >>>> watcher <<< still not sure how >>>> critical this is >>>> >>>> > xenstore-ls >>>> tool =3D "" >>>> xenstored =3D "" >>>> local =3D "" >>>> domain =3D "" >>>> 0 =3D "" >>>> data =3D "" >>>> meminfo_total =3D "930680" >>>> meminfo_free =3D "691868" >>>> os_name =3D "Ubuntu 12.04.1 LTS" >>>> os_majorver =3D "12" >>>> os_minorver =3D "04" >>>> os_uname =3D "3.8.0-rc5+" >>>> os_distro =3D "ubuntu" >>>> updated =3D "Sun Feb 3 10:43:32 MST 2013" >>>> name =3D "Domain-0" >>>> attr =3D "" >>>> xenbr0 =3D "" >>>> ip =3D "155.98.39.2" >>>> PVAddons =3D "" >>>> MajorVersion =3D "5" >>>> MinorVersion =3D "5" >>>> MicroVersion =3D "0" >>>> BuildVersion =3D "17913" >>>> Installed =3D "1" >>>> device-model =3D "" >>>> 0 =3D "" >>>> state =3D "running" >>>> >>>> After this I start the guest domain, here's the xenstore entries, >>>> >>>> nodea:~> sudo xenstore-ls >>>> tool =3D "" >>>> xenstored =3D "" >>>> local =3D "" >>>> domain =3D "" >>>> 0 =3D "" >>>> data =3D "" >>>> meminfo_total =3D "930680" >>>> meminfo_free =3D "695408" >>>> os_name =3D "Ubuntu 12.04.1 LTS" >>>> os_majorver =3D "12" >>>> os_minorver =3D "04" >>>> os_uname =3D "3.8.0-rc5+" >>>> os_distro =3D "ubuntu" >>>> updated =3D "Sun Feb 3 10:45:32 MST 2013" >>>> name =3D "Domain-0" >>>> attr =3D "" >>>> xenbr0 =3D "" >>>> ip =3D "155.98.39.2" >>>> PVAddons =3D "" >>>> MajorVersion =3D "5" >>>> MinorVersion =3D "5" >>>> MicroVersion =3D "0" >>>> BuildVersion =3D "17913" >>>> Installed =3D "1" >>>> device-model =3D "" >>>> 0 =3D "" >>>> state =3D "running" >>>> memory =3D "" >>>> target =3D "1048576" >>>> static-max =3D "4294967292" >>>> freemem-slack =3D "314476" >>>> libxl =3D "" >>>> disable_udev =3D "1" >>>> backend =3D "" >>>> vbd =3D "" >>>> 1 =3D "" >>>> 2049 =3D "" >>>> frontend =3D "/local/domain/1/device/vbd/2049" <<<< everythi= ng >>>> seems to be enumerated >>>> params =3D "/dev/loop0" >>>> script =3D "/etc/xen/scripts/block" >>>> physical-device =3D "7:0" >>>> frontend-id =3D "1" >>>> online =3D "1" >>>> removable =3D "0" >>>> bootable =3D "1" >>>> state =3D "1" >>>> dev =3D "sda1" >>>> type =3D "phy" >>>> mode =3D "w" >>>> device-type =3D "disk" >>>> 1 =3D "" >>>> vm =3D "/vm/9b0dfb10-f69d-4e22-9158-bb70456ece2e" >>>> name =3D "guest2" >>>> cpu =3D "" >>>> 0 =3D "" >>>> availability =3D "online" >>>> memory =3D "" >>>> static-max =3D "512000" >>>> target =3D "512001" >>>> videoram =3D "-1" >>>> device =3D "" >>>> suspend =3D "" >>>> event-channel =3D "" >>>> vbd =3D "" >>>> 2049 =3D "" >>>> backend =3D "/local/domain/0/backend/vbd/1/2049" >>>> backend-id =3D "0" >>>> state =3D "1" <<<<< state changes to 5 and then after 5 secs = it >>>> times out >>>> virtual-device =3D "2049" >>>> device-type =3D "disk" >>>> control =3D "" >>>> shutdown =3D "" >>>> platform-feature-multiprocessor-suspend =3D "1" >>>> platform-feature-xs_reset_watches =3D "1" >>>> data =3D "" >>>> domid =3D "1" >>>> store =3D "" >>>> port =3D "1" >>>> ring-ref =3D "156845" >>>> vm =3D "" >>>> 9b0dfb10-f69d-4e22-9158-bb70456ece2e =3D "" >>>> uuid =3D "9b0dfb10-f69d-4e22-9158-bb70456ece2e" >>>> name =3D "guest2" >>>> image =3D "" >>>> ostype =3D "linux" >>>> kernel =3D "/boot/vmlinuz-3.8.0-rc5+" >>>> ramdisk =3D "/boot/initrd.img-3.8.0-rc5+" >>>> cmdline =3D "root=3D/dev/disk/by-path/xen-vbd-2049 ro xencons=3D= tty" >>>> start_time =3D "1359913591.67" >>>> libxl =3D "" >>>> 1 =3D "" >>>> dm-version =3D "qemu_xen" >>>> >>>> Thanks, >>>> Yathi Sorry about top posting. I changed it to xvda1 and I still see the same = behavior. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Wed Feb 06 13:10:32 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 06 Feb 2013 13:10: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 1U34kq-0001ZO-Iz; Wed, 06 Feb 2013 13:09:36 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U2tSi-0002ZD-30 for xen-users@lists.xen.org; Wed, 06 Feb 2013 01:06:08 +0000 Received: from [85.158.138.51:26657] by server-8.bemta-3.messagelabs.com id C7/0F-25687-F7CA1115; Wed, 06 Feb 2013 01:06:07 +0000 X-Env-Sender: linuxhack2012@gmail.com X-Msg-Ref: server-5.tower-174.messagelabs.com!1360112753!28984618!1 X-Originating-IP: [209.85.216.174] 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.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 13900 invoked from network); 6 Feb 2013 01:05:54 -0000 Received: from mail-qc0-f174.google.com (HELO mail-qc0-f174.google.com) (209.85.216.174) by server-5.tower-174.messagelabs.com with RC4-SHA encrypted SMTP; 6 Feb 2013 01:05:54 -0000 Received: by mail-qc0-f174.google.com with SMTP id z24so319373qcq.33 for ; Tue, 05 Feb 2013 17:04:53 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:date:message-id:subject:from:to :content-type; bh=J0RuoZOgWQFVjO0mxIKknJt64Bv9fvAKEvVjepcIE5U=; b=P9TNrjsyUNvLNMCDAHn025Ghylr2PmIu+9K+6080TQKar3miPp510L8+I+X33qXB5g jBuZ+cO6I/0BHMIL2Yl5WNQTVIE6lsS+vqd2CR8y2qab6Pdx7d7ldiGdJ9olRO7IZ2PR +5TdUJe3HNtcKOPE5HKTmRJNM6ZJnkauQyVfKtWE9HpbR5mTbS34bTKwlDDkkxesVDRX V4k4v8vhsj4mgO5fqtE4SdsVHpLpLuOYzqgRuk5oNr/QcmYXK00UXoX6hp9iWwuXOEPQ 8eH/LNajBrCOqo/VA96ySwTub8bj9VdIJORLwhcfSw/2IgILLmQzjXKkimTqyEuWzcCB KqJA== MIME-Version: 1.0 X-Received: by 10.49.84.104 with SMTP id x8mr24411861qey.5.1360112693752; Tue, 05 Feb 2013 17:04:53 -0800 (PST) Received: by 10.49.52.66 with HTTP; Tue, 5 Feb 2013 17:04:53 -0800 (PST) Date: Wed, 6 Feb 2013 06:34:53 +0530 Message-ID: From: Linux Hack To: "xen-users@lists.xen.org" X-Mailman-Approved-At: Wed, 06 Feb 2013 13:09:34 +0000 Subject: [Xen-users] xsa33 patch 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="===============7245692077915726269==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============7245692077915726269== Content-Type: multipart/alternative; boundary=047d7bdc1728f7342f04d503e911 --047d7bdc1728f7342f04d503e911 Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable Hi, I am trying to apply the patch xsa33 to the source and making rpm to install on our server. But this patch doesn't working for Xen-4.1.4 source and I am getting the below error when I make rpm with this patch applied. =3D=3D=3D=3D=3D=3D=3D=3D=3D gcc -O2 -fomit-frame-pointer -m64 -fno-strict-aliasing -std=3Dgnu99 -Wall -Wstrict-prototypes -Wno-unused-value -Wdeclaration-after-statement -DNDEBUG -nostdinc -fno-builtin -fno-common -Wredundant-decls -iwithprefix include -Werror -Wno-pointer-arith -pipe -I/usr/src/redhat/BUILD/xen-4.1.4/xen/include -I/usr/src/redhat/BUILD/xen-4.1.4/xen/include/asm-x86/mach-generic -I/usr/src/redhat/BUILD/xen-4.1.4/xen/include/asm-x86/mach-default -msoft-float -fno-stack-protector -fno-exceptions -mno-red-zone -fpic -fno-asynchronous-unwind-tables -DGCC_HAS_VISIBILITY_ATTRIBUTE -g -D__XEN__ -MMD -MF .qinval.o.d -c qinval.c -o qinval.o gcc -O2 -fomit-frame-pointer -m64 -fno-strict-aliasing -std=3Dgnu99 -Wall -Wstrict-prototypes -Wno-unused-value -Wdeclaration-after-statement -DNDEBUG -nostdinc -fno-builtin -fno-common -Wredundant-decls -iwithprefix include -Werror -Wno-pointer-arith -pipe -I/usr/src/redhat/BUILD/xen-4.1.4/xen/include -I/usr/src/redhat/BUILD/xen-4.1.4/xen/include/asm-x86/mach-generic -I/usr/src/redhat/BUILD/xen-4.1.4/xen/include/asm-x86/mach-default -msoft-float -fno-stack-protector -fno-exceptions -mno-red-zone -fpic -fno-asynchronous-unwind-tables -DGCC_HAS_VISIBILITY_ATTRIBUTE -g -D__XEN__ -MMD -MF .intremap.o.d -c intremap.c -o intremap.o intremap.c: In function =91set_msi_source_id=92: intremap.c:502: error: =91SVT_VERIFY_BUS_SQ=92 undeclared (first use in thi= s function) intremap.c:502: error: (Each undeclared identifier is reported only once intremap.c:502: error: for each function it appears in.) make[6]: *** [intremap.o] Error 1 make[6]: Leaving directory `/usr/src/redhat/BUILD/xen-4.1.4/xen/drivers/passthrough/vtd' make[5]: *** [vtd/built_in.o] Error 2 make[5]: Leaving directory `/usr/src/redhat/BUILD/xen-4.1.4/xen/drivers/passthrough' make[4]: *** [passthrough/built_in.o] Error 2 make[4]: Leaving directory `/usr/src/redhat/BUILD/xen-4.1.4/xen/drivers' make[3]: *** [/usr/src/redhat/BUILD/xen-4.1.4/xen/drivers/built_in.o] Error 2 make[3]: Leaving directory `/usr/src/redhat/BUILD/xen-4.1.4/xen/arch/x86' make[2]: *** [/usr/src/redhat/BUILD/xen-4.1.4/xen/xen] Error 2 make[2]: Leaving directory `/usr/src/redhat/BUILD/xen-4.1.4/xen' make[1]: *** [install] Error 2 make[1]: Leaving directory `/usr/src/redhat/BUILD/xen-4.1.4/xen' make: *** [install-xen] Error 2 error: Bad exit status from /var/tmp/rpm-tmp.86045 (%build) =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D Any suggestion would be great. --047d7bdc1728f7342f04d503e911 Content-Type: text/html; charset=windows-1252 Content-Transfer-Encoding: quoted-printable
Hi,

I am trying to apply the patch xsa3= 3 to the source and making rpm to install on our server. But this patch doe= sn't working for Xen-4.1.4 source and I am getting the below error when= I make rpm with this patch applied.

=3D=3D=3D=3D=3D=3D=3D=3D=3D
gcc -O2 -fom= it-frame-pointer -m64 -fno-strict-aliasing -std=3Dgnu99 -Wall -Wstrict-prot= otypes -Wno-unused-value -Wdeclaration-after-statement =A0-DNDEBUG -nostdin= c -fno-builtin -fno-common -Wredundant-decls -iwithprefix include -Werror -= Wno-pointer-arith -pipe -I/usr/src/redhat/BUILD/xen-4.1.4/xen/include =A0-I= /usr/src/redhat/BUILD/xen-4.1.4/xen/include/asm-x86/mach-generic -I/usr/src= /redhat/BUILD/xen-4.1.4/xen/include/asm-x86/mach-default -msoft-float -fno-= stack-protector -fno-exceptions -mno-red-zone -fpic -fno-asynchronous-unwin= d-tables -DGCC_HAS_VISIBILITY_ATTRIBUTE -g -D__XEN__ -MMD -MF .qinval.o.d -= c qinval.c -o qinval.o
gcc -O2 -fomit-frame-pointer -m64 -fno-strict-aliasing -std=3Dgnu99 -W= all -Wstrict-prototypes -Wno-unused-value -Wdeclaration-after-statement =A0= -DNDEBUG -nostdinc -fno-builtin -fno-common -Wredundant-decls -iwithprefix = include -Werror -Wno-pointer-arith -pipe -I/usr/src/redhat/BUILD/xen-4.1.4/= xen/include =A0-I/usr/src/redhat/BUILD/xen-4.1.4/xen/include/asm-x86/mach-g= eneric -I/usr/src/redhat/BUILD/xen-4.1.4/xen/include/asm-x86/mach-default -= msoft-float -fno-stack-protector -fno-exceptions -mno-red-zone -fpic -fno-a= synchronous-unwind-tables -DGCC_HAS_VISIBILITY_ATTRIBUTE -g -D__XEN__ -MMD = -MF .intremap.o.d -c intremap.c -o intremap.o
intremap.c: In function =91set_msi_source_id=92:
intremap.c:= 502: error: =91SVT_VERIFY_BUS_SQ=92 undeclared (first use in this function)=
intremap.c:502: error: (Each undeclared identifier is reported o= nly once
intremap.c:502: error: for each function it appears in.)
mak= e[6]: *** [intremap.o] Error 1
make[6]: Leaving directory `/usr/s= rc/redhat/BUILD/xen-4.1.4/xen/drivers/passthrough/vtd'
make[5= ]: *** [vtd/built_in.o] Error 2
make[5]: Leaving directory `/usr/src/redhat/BUILD/xen-4.1.4/xen/driver= s/passthrough'
make[4]: *** [passthrough/built_in.o] Error 2<= /div>
make[4]: Leaving directory `/usr/src/redhat/BUILD/xen-4.1.4/xen/d= rivers'
make[3]: *** [/usr/src/redhat/BUILD/xen-4.1.4/xen/drivers/built_in.o] = Error 2
make[3]: Leaving directory `/usr/src/redhat/BUILD/xen-4.1= .4/xen/arch/x86'
make[2]: *** [/usr/src/redhat/BUILD/xen-4.1.= 4/xen/xen] Error 2
make[2]: Leaving directory `/usr/src/redhat/BUILD/xen-4.1.4/xen'
make[1]: *** [install] Error 2
make[1]: Leaving director= y `/usr/src/redhat/BUILD/xen-4.1.4/xen'
make: *** [install-xe= n] Error 2
error: Bad exit status from /var/tmp/rpm-tmp.86045 (%build)
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

Any = suggestion would be great.

--047d7bdc1728f7342f04d503e911-- --===============7245692077915726269== 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 --===============7245692077915726269==-- From xen-users-bounces@lists.xen.org Wed Feb 06 13:10:32 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 06 Feb 2013 13:10: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 1U34kr-0001ZY-8L; Wed, 06 Feb 2013 13:09:37 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U2v0k-000682-PB for xen-users@lists.xen.org; Wed, 06 Feb 2013 02:45:23 +0000 Received: from [85.158.137.99:62002] by server-2.bemta-3.messagelabs.com id AB/56-25961-CB3C1115; Wed, 06 Feb 2013 02:45:16 +0000 X-Env-Sender: ydev@cs.utah.edu X-Msg-Ref: server-9.tower-217.messagelabs.com!1360118715!16992045!1 X-Originating-IP: [155.98.64.241] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 18808 invoked from network); 6 Feb 2013 02:45:15 -0000 Received: from rio.cs.utah.edu (HELO mail-svr1.cs.utah.edu) (155.98.64.241) by server-9.tower-217.messagelabs.com with SMTP; 6 Feb 2013 02:45:15 -0000 Received: from localhost (localhost [127.0.0.1]) by mail-svr1.cs.utah.edu (Postfix) with ESMTP id 33A836500CB; Tue, 5 Feb 2013 19:45:14 -0700 (MST) X-Virus-Scanned: amavisd-new at cs.utah.edu Received: from mail-svr1.cs.utah.edu ([127.0.0.1]) by localhost (mail-svr1.cs.utah.edu [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sFMVDMafrif1; Tue, 5 Feb 2013 19:45:13 -0700 (MST) Received: from [192.168.1.16] (c-76-23-15-81.hsd1.ut.comcast.net [76.23.15.81]) by smtps.cs.utah.edu (Postfix) with ESMTPSA id 22CCA6500C7; Tue, 5 Feb 2013 19:45:13 -0700 (MST) Message-ID: <5111C3B6.1070705@cs.utah.edu> Date: Tue, 05 Feb 2013 19:45:10 -0700 From: Yathindra User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130107 Thunderbird/17.0.2 MIME-Version: 1.0 To: =?ISO-8859-1?Q?Roger_Pau_Monn=E9?= References: <510DC655.5060205@cs.utah.edu> <510E3195.1010004@citrix.com> <510EA374.6060509@cs.utah.edu> <5110D7EC.8040608@citrix.com> <51113D59.7030003@cs.utah.edu> <51114B35.5050202@citrix.com> In-Reply-To: <51114B35.5050202@citrix.com> X-Mailman-Approved-At: Wed, 06 Feb 2013 13:09:34 +0000 Cc: "xen-users@lists.xen.org" Subject: Re: [Xen-users] xen_blkbk times out before getting connected X-BeenThere: xen-users@lists.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 2/5/2013 11:11 AM, Roger Pau Monn=E9 wrote: > On 05/02/13 18:11, Yathindra wrote: >> DomU configuration file looks like this: > Please don't do top posting. > >> kernel =3D "/boot/vmlinuz-3.8.0-rc5+" >> ramdisk =3D "/boot/initrd.img-3.8.0-rc5+" >> memory =3D 500 >> name =3D "guest2" >> disk =3D ['phy:/dev/loop0,sda1,w'] > Why are you using sda1 instead of xvda1? > >> root =3D "/dev/disk/by-path/xen-vbd-2049 ro" >> extra =3D 'xencons=3Dtty' > You can use: > > extra=3D"root=3D/dev/xvda1" > >> On 2/5/2013 2:59 AM, Roger Pau Monn=E9 wrote: >>> On 03/02/13 18:50, Yathindra wrote: >>>> I'm using the latest linux kernel 3.8.0 with Xen 4.3-unstable. Xenstor= ed >>>> is being started at boot time. >>>> I did not see any message (dmesg/syslog/console) about device being >>>> plugged in but xenstore-ls shows me all >>>> the entries backend and frontend. >>> Could you post your DomU configuration file also? >>> >>>> Here are some details >>>> ------------------------------ >>>> From /var/log/syslog: >>>> >>>> Feb 3 10:37:31 localhost kernel: [ 36.466359] Event-channel device >>>> installed. >>>> Feb 3 10:37:31 localhost kernel: [ 36.636358] Register >>>> xen_blkbk_driver <<< custom debug message I added >>>> Feb 3 10:37:31 localhost kernel: [ 36.636367] >>>> xenbus_register_backend <<< custom debug message I added >>>> Feb 3 10:37:31 localhost kernel: [ 36.683533] xenbus_register_backe= nd >>>> Feb 3 10:37:31 localhost kernel: [ 36.830115] xen-pciback: backend = is >>>> vpci <<< custom debug message I added >>>> Feb 3 10:37:31 localhost kernel: [ 36.830123] >>>> xenbus_register_backend <<< custom debug message I added >>>> Feb 3 10:37:32 localhost xenstored: Checking store ... >>>> Feb 3 10:37:32 localhost xenstored: Checking store complete. >>>> Feb 3 10:37:32 localhost kernel: [ 37.075217] xenbus_probe: xenstor= ed >>>> is ready <<< custom debug message I added >>>> Feb 3 10:37:32 localhost kernel: [ 37.075230] watching node >>>> FFFFFFFF81C7D1A0 >>>> Feb 3 10:37:32 localhost kernel: [ 37.081309] xenbus_scanf for node= cpu/0 >>>> Feb 3 10:37:32 localhost kernel: [ 37.081327] XENBUS xen store gave: >>>> unknown error cpu >>>> Feb 3 10:37:32 localhost kernel: [ 37.081333] xenbus_scanf for node= cpu/1 >>>> Feb 3 10:37:32 localhost kernel: [ 37.085327] XENBUS unexpected type >>>> [17], expected [2] >>>> Feb 3 10:37:32 localhost kernel: [ 37.085342] watching node >>>> FFFFFFFF81C7D0C0 >>>> Feb 3 10:37:32 localhost kernel: [ 37.086857] XENBUS unexpected type >>>> [17], expected [4] >>>> Feb 3 10:37:32 localhost kernel: [ 37.086865] Failed to set shutdown >>>> watcher >>>> Feb 3 10:37:32 localhost kernel: [ 37.086880] backend_probe_and_wat= ch >>>> - enumerates devices in xenstore and watches for changes <<< custom >>>> debug message I added >>>> Feb 3 10:37:32 localhost kernel: [ 37.089401] XENBUS unexpected type >>>> [4], expected [1] >>>> Feb 3 10:37:32 localhost kernel: [ 37.089411] watching node >>>> FFFFFFFF81C7D660 >>>> Feb 3 10:37:32 localhost kernel: [ 37.090715] XENBUS xen store gave: >>>> unknown error control/shutdown >>>> Feb 3 10:37:32 localhost kernel: [ 37.090725] >>>> frontend_probe_and_watch: calling xenbus_probe_devices <<< custom debug >>>> message I added >>>> Feb 3 10:37:32 localhost kernel: [ 37.092362] XENBUS unexpected type >>>> [17], expected [1] >>>> Feb 3 10:37:32 localhost kernel: [ 37.092376] watching node >>>> FFFFFFFF81C7D820 >>>> Feb 3 10:37:32 localhost kernel: [ 37.093334] watching node >>>> FFFFFFFF81C7DB20 >>>> Feb 3 10:37:32 localhost kernel: [ 37.094454] XENBUS xen store gave: >>>> unknown error backend <<< still not sure how critical this is >>>> Feb 3 10:37:32 localhost kernel: [ 37.094463] Failed to set balloon >>>> watcher <<< still not sure how >>>> critical this is >>>> >>>> > xenstore-ls >>>> tool =3D "" >>>> xenstored =3D "" >>>> local =3D "" >>>> domain =3D "" >>>> 0 =3D "" >>>> data =3D "" >>>> meminfo_total =3D "930680" >>>> meminfo_free =3D "691868" >>>> os_name =3D "Ubuntu 12.04.1 LTS" >>>> os_majorver =3D "12" >>>> os_minorver =3D "04" >>>> os_uname =3D "3.8.0-rc5+" >>>> os_distro =3D "ubuntu" >>>> updated =3D "Sun Feb 3 10:43:32 MST 2013" >>>> name =3D "Domain-0" >>>> attr =3D "" >>>> xenbr0 =3D "" >>>> ip =3D "155.98.39.2" >>>> PVAddons =3D "" >>>> MajorVersion =3D "5" >>>> MinorVersion =3D "5" >>>> MicroVersion =3D "0" >>>> BuildVersion =3D "17913" >>>> Installed =3D "1" >>>> device-model =3D "" >>>> 0 =3D "" >>>> state =3D "running" >>>> >>>> After this I start the guest domain, here's the xenstore entries, >>>> >>>> nodea:~> sudo xenstore-ls >>>> tool =3D "" >>>> xenstored =3D "" >>>> local =3D "" >>>> domain =3D "" >>>> 0 =3D "" >>>> data =3D "" >>>> meminfo_total =3D "930680" >>>> meminfo_free =3D "695408" >>>> os_name =3D "Ubuntu 12.04.1 LTS" >>>> os_majorver =3D "12" >>>> os_minorver =3D "04" >>>> os_uname =3D "3.8.0-rc5+" >>>> os_distro =3D "ubuntu" >>>> updated =3D "Sun Feb 3 10:45:32 MST 2013" >>>> name =3D "Domain-0" >>>> attr =3D "" >>>> xenbr0 =3D "" >>>> ip =3D "155.98.39.2" >>>> PVAddons =3D "" >>>> MajorVersion =3D "5" >>>> MinorVersion =3D "5" >>>> MicroVersion =3D "0" >>>> BuildVersion =3D "17913" >>>> Installed =3D "1" >>>> device-model =3D "" >>>> 0 =3D "" >>>> state =3D "running" >>>> memory =3D "" >>>> target =3D "1048576" >>>> static-max =3D "4294967292" >>>> freemem-slack =3D "314476" >>>> libxl =3D "" >>>> disable_udev =3D "1" >>>> backend =3D "" >>>> vbd =3D "" >>>> 1 =3D "" >>>> 2049 =3D "" >>>> frontend =3D "/local/domain/1/device/vbd/2049" <<<< everythi= ng >>>> seems to be enumerated >>>> params =3D "/dev/loop0" >>>> script =3D "/etc/xen/scripts/block" >>>> physical-device =3D "7:0" >>>> frontend-id =3D "1" >>>> online =3D "1" >>>> removable =3D "0" >>>> bootable =3D "1" >>>> state =3D "1" >>>> dev =3D "sda1" >>>> type =3D "phy" >>>> mode =3D "w" >>>> device-type =3D "disk" >>>> 1 =3D "" >>>> vm =3D "/vm/9b0dfb10-f69d-4e22-9158-bb70456ece2e" >>>> name =3D "guest2" >>>> cpu =3D "" >>>> 0 =3D "" >>>> availability =3D "online" >>>> memory =3D "" >>>> static-max =3D "512000" >>>> target =3D "512001" >>>> videoram =3D "-1" >>>> device =3D "" >>>> suspend =3D "" >>>> event-channel =3D "" >>>> vbd =3D "" >>>> 2049 =3D "" >>>> backend =3D "/local/domain/0/backend/vbd/1/2049" >>>> backend-id =3D "0" >>>> state =3D "1" <<<<< state changes to 5 and then after 5 secs = it >>>> times out >>>> virtual-device =3D "2049" >>>> device-type =3D "disk" >>>> control =3D "" >>>> shutdown =3D "" >>>> platform-feature-multiprocessor-suspend =3D "1" >>>> platform-feature-xs_reset_watches =3D "1" >>>> data =3D "" >>>> domid =3D "1" >>>> store =3D "" >>>> port =3D "1" >>>> ring-ref =3D "156845" >>>> vm =3D "" >>>> 9b0dfb10-f69d-4e22-9158-bb70456ece2e =3D "" >>>> uuid =3D "9b0dfb10-f69d-4e22-9158-bb70456ece2e" >>>> name =3D "guest2" >>>> image =3D "" >>>> ostype =3D "linux" >>>> kernel =3D "/boot/vmlinuz-3.8.0-rc5+" >>>> ramdisk =3D "/boot/initrd.img-3.8.0-rc5+" >>>> cmdline =3D "root=3D/dev/disk/by-path/xen-vbd-2049 ro xencons=3D= tty" >>>> start_time =3D "1359913591.67" >>>> libxl =3D "" >>>> 1 =3D "" >>>> dm-version =3D "qemu_xen" >>>> >>>> Thanks, >>>> Yathi Sorry about top posting. I changed it to xvda1 and I still see the same = behavior. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Wed Feb 06 13:19:47 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 06 Feb 2013 13:19: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 1U34tw-000327-N8; Wed, 06 Feb 2013 13:19:00 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U34tv-00031y-7v for xen-users@lists.xen.org; Wed, 06 Feb 2013 13:18:59 +0000 Received: from [85.158.139.211:36208] by server-4.bemta-5.messagelabs.com id 9E/E4-29496-24852115; Wed, 06 Feb 2013 13:18:58 +0000 X-Env-Sender: carlos@ansp.br X-Msg-Ref: server-2.tower-206.messagelabs.com!1360156736!20282387!1 X-Originating-IP: [209.85.219.54] X-SpamReason: No, hits=0.6 required=7.0 tests=HTML_60_70,HTML_MESSAGE, RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 20541 invoked from network); 6 Feb 2013 13:18:57 -0000 Received: from mail-oa0-f54.google.com (HELO mail-oa0-f54.google.com) (209.85.219.54) by server-2.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 6 Feb 2013 13:18:57 -0000 Received: by mail-oa0-f54.google.com with SMTP id n12so1466556oag.13 for ; Wed, 06 Feb 2013 05:18:55 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-received:date:message-id:subject:from:to :content-type:x-gm-message-state; bh=hU/0o4knJC9kQUK1dJBGWynsbXGEW8vDo/6DCcBzyww=; b=OxbA+m4YD5CRhy0gedDHDxGXRDzJd2CW/YtZ/t7huARmGuh54nSKcGV2DZp6pun6PL HO0WiEN/1o+HMW6qsUsGC7Lc7sbTpdDLZpYWzf8GQpldG1U9COndemucAha4ij1gOaav diaYgC67G5916Uo4dJA2RbcPKod9xNY5AhhHM90uuhXSCRb5Q86ytJllFH+Yd1Eq/Ak1 bzXNh0rnwfgpwAMqCROTi2g2lQumsXVGFZYB53COGhqY1K70Z2YeCJkRAGIfMCSnmyW7 8PELJXAjouzI0xSYQmhSdufzwRysdgY4RbsrFc68aLKcMQltPZNwFxQ1d7mzd4+2xEIv kZgA== MIME-Version: 1.0 X-Received: by 10.182.48.37 with SMTP id i5mr20810804obn.18.1360156735723; Wed, 06 Feb 2013 05:18:55 -0800 (PST) Received: by 10.182.40.98 with HTTP; Wed, 6 Feb 2013 05:18:55 -0800 (PST) Date: Wed, 6 Feb 2013 11:18:55 -0200 Message-ID: From: Carlos Ribas To: xen-users@lists.xen.org X-Gm-Message-State: ALoCoQn1y8OFkfw1TWBiRr1EKhDAIdIc2AsRAr1gebBu5nKHTt1uz/OWq9H/kx/phkumLlzTLnIk Subject: [Xen-users] How to auto start DomU after reboot of 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="===============7377706990598495027==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============7377706990598495027== Content-Type: multipart/alternative; boundary=f46d0447a0591257cf04d50e2bbb --f46d0447a0591257cf04d50e2bbb Content-Type: text/plain; charset=ISO-8859-1 Hello all, I followed some tutorials to install Xen in a Debian Squeeze server. One of them [1] says to set up XENDOMAINS_RESTORE to false, because I can have problems with that. So, if my server shuts down or reboots how can I configure my VM to automatically start? Yesterday I did a quick script [2] that worked well, but I am not sure if it is the best way to do it. I would like to know what you do solve this issue. [1] - http://wiki.debian.org/Xen#Other_configuration_tweaks [2] - Script: #!/bin/bash # Start all the VMs from here VMS="/etc/xen/*.cfg" for vm in $VMS do if [ -e "$vm" ] # Check if file exist then data=`date '+%d/%m/%Y - %H:%M:%S'` # Current date/time (log purposes) echo "starting at: $data" /usr/sbin/xm create $vm # Create VM sleep 15 # Wait 15 sec to start the next echo continue # Next VM fi echo "Nothing to be done..." done exit 0 Regards, ------------------------------- Carlos Eduardo Ribas --f46d0447a0591257cf04d50e2bbb Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Hello all,

=A0 =A0 I followed some tutorials to install = Xen in a Debian Squeeze server. One of them [1] says to set up XENDOMAINS_R= ESTORE to false, because I can have problems with that. So, if my server sh= uts down or reboots how can I configure my VM to automatically start?

=A0 =A0=A0Yesterday I did a quick script [2] that worke= d well, but I am not sure if it is the best way to do it. I would like to k= now what you do solve this issue.


[2] - Script:

#!/bin/bash

#=A0Start all the VMs from here
VMS=3D"/etc/xen/*.cfg"=

for vm in $V= MS
do

=A0 if [ -e "$vm" ] =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0 =A0 =A0#=A0Check if file exist
=A0 then
=A0 =A0 data=3D`date '+%d/%m/%Y - %H:%M= :%S'` # Current date/time (log purposes)
=A0 =A0 echo "starting at: $data"=
=A0 =A0 /usr/sbin/xm create $vm = =A0 =A0 =A0 =A0 =A0 =A0#=A0Create VM
=A0 =A0 sleep 15 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0 =A0 =A0 #=A0Wait 15 sec to start the next
=A0 =A0 echo
=A0 =A0 continue =A0 =A0 =A0 =A0 =A0 = =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 #=A0Next VM
=A0 fi

=A0 echo "Nothing to be done..."

done

exit 0

Regards,

---------------= ----------------
Carlos Eduardo Ribas

--f46d0447a0591257cf04d50e2bbb-- --===============7377706990598495027== 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 --===============7377706990598495027==-- From xen-users-bounces@lists.xen.org Wed Feb 06 13:19:47 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 06 Feb 2013 13:19: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 1U34tw-000327-N8; Wed, 06 Feb 2013 13:19:00 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U34tv-00031y-7v for xen-users@lists.xen.org; Wed, 06 Feb 2013 13:18:59 +0000 Received: from [85.158.139.211:36208] by server-4.bemta-5.messagelabs.com id 9E/E4-29496-24852115; Wed, 06 Feb 2013 13:18:58 +0000 X-Env-Sender: carlos@ansp.br X-Msg-Ref: server-2.tower-206.messagelabs.com!1360156736!20282387!1 X-Originating-IP: [209.85.219.54] X-SpamReason: No, hits=0.6 required=7.0 tests=HTML_60_70,HTML_MESSAGE, RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 20541 invoked from network); 6 Feb 2013 13:18:57 -0000 Received: from mail-oa0-f54.google.com (HELO mail-oa0-f54.google.com) (209.85.219.54) by server-2.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 6 Feb 2013 13:18:57 -0000 Received: by mail-oa0-f54.google.com with SMTP id n12so1466556oag.13 for ; Wed, 06 Feb 2013 05:18:55 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-received:date:message-id:subject:from:to :content-type:x-gm-message-state; bh=hU/0o4knJC9kQUK1dJBGWynsbXGEW8vDo/6DCcBzyww=; b=OxbA+m4YD5CRhy0gedDHDxGXRDzJd2CW/YtZ/t7huARmGuh54nSKcGV2DZp6pun6PL HO0WiEN/1o+HMW6qsUsGC7Lc7sbTpdDLZpYWzf8GQpldG1U9COndemucAha4ij1gOaav diaYgC67G5916Uo4dJA2RbcPKod9xNY5AhhHM90uuhXSCRb5Q86ytJllFH+Yd1Eq/Ak1 bzXNh0rnwfgpwAMqCROTi2g2lQumsXVGFZYB53COGhqY1K70Z2YeCJkRAGIfMCSnmyW7 8PELJXAjouzI0xSYQmhSdufzwRysdgY4RbsrFc68aLKcMQltPZNwFxQ1d7mzd4+2xEIv kZgA== MIME-Version: 1.0 X-Received: by 10.182.48.37 with SMTP id i5mr20810804obn.18.1360156735723; Wed, 06 Feb 2013 05:18:55 -0800 (PST) Received: by 10.182.40.98 with HTTP; Wed, 6 Feb 2013 05:18:55 -0800 (PST) Date: Wed, 6 Feb 2013 11:18:55 -0200 Message-ID: From: Carlos Ribas To: xen-users@lists.xen.org X-Gm-Message-State: ALoCoQn1y8OFkfw1TWBiRr1EKhDAIdIc2AsRAr1gebBu5nKHTt1uz/OWq9H/kx/phkumLlzTLnIk Subject: [Xen-users] How to auto start DomU after reboot of 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="===============7377706990598495027==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============7377706990598495027== Content-Type: multipart/alternative; boundary=f46d0447a0591257cf04d50e2bbb --f46d0447a0591257cf04d50e2bbb Content-Type: text/plain; charset=ISO-8859-1 Hello all, I followed some tutorials to install Xen in a Debian Squeeze server. One of them [1] says to set up XENDOMAINS_RESTORE to false, because I can have problems with that. So, if my server shuts down or reboots how can I configure my VM to automatically start? Yesterday I did a quick script [2] that worked well, but I am not sure if it is the best way to do it. I would like to know what you do solve this issue. [1] - http://wiki.debian.org/Xen#Other_configuration_tweaks [2] - Script: #!/bin/bash # Start all the VMs from here VMS="/etc/xen/*.cfg" for vm in $VMS do if [ -e "$vm" ] # Check if file exist then data=`date '+%d/%m/%Y - %H:%M:%S'` # Current date/time (log purposes) echo "starting at: $data" /usr/sbin/xm create $vm # Create VM sleep 15 # Wait 15 sec to start the next echo continue # Next VM fi echo "Nothing to be done..." done exit 0 Regards, ------------------------------- Carlos Eduardo Ribas --f46d0447a0591257cf04d50e2bbb Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Hello all,

=A0 =A0 I followed some tutorials to install = Xen in a Debian Squeeze server. One of them [1] says to set up XENDOMAINS_R= ESTORE to false, because I can have problems with that. So, if my server sh= uts down or reboots how can I configure my VM to automatically start?

=A0 =A0=A0Yesterday I did a quick script [2] that worke= d well, but I am not sure if it is the best way to do it. I would like to k= now what you do solve this issue.


[2] - Script:

#!/bin/bash

#=A0Start all the VMs from here
VMS=3D"/etc/xen/*.cfg"=

for vm in $V= MS
do

=A0 if [ -e "$vm" ] =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0 =A0 =A0#=A0Check if file exist
=A0 then
=A0 =A0 data=3D`date '+%d/%m/%Y - %H:%M= :%S'` # Current date/time (log purposes)
=A0 =A0 echo "starting at: $data"=
=A0 =A0 /usr/sbin/xm create $vm = =A0 =A0 =A0 =A0 =A0 =A0#=A0Create VM
=A0 =A0 sleep 15 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0 =A0 =A0 #=A0Wait 15 sec to start the next
=A0 =A0 echo
=A0 =A0 continue =A0 =A0 =A0 =A0 =A0 = =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 #=A0Next VM
=A0 fi

=A0 echo "Nothing to be done..."

done

exit 0

Regards,

---------------= ----------------
Carlos Eduardo Ribas

--f46d0447a0591257cf04d50e2bbb-- --===============7377706990598495027== 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 --===============7377706990598495027==-- From xen-users-bounces@lists.xen.org Wed Feb 06 13:21:51 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 06 Feb 2013 13:21: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 1U34w5-0003IO-Kh; Wed, 06 Feb 2013 13:21:13 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U34w3-0003I8-U1 for xen-users@lists.xen.org; Wed, 06 Feb 2013 13:21:12 +0000 Received: from [193.109.254.147:42397] by server-3.bemta-14.messagelabs.com id E1/6D-22141-7C852115; Wed, 06 Feb 2013 13:21:11 +0000 X-Env-Sender: Ian.Campbell@citrix.com X-Msg-Ref: server-12.tower-27.messagelabs.com!1360156741!9422920!1 X-Originating-IP: [46.33.159.39] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNDYuMzMuMTU5LjM5ID0+IDIxMjEz\n X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 2655 invoked from network); 6 Feb 2013 13:19:09 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (46.33.159.39) by server-12.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 6 Feb 2013 13:19:09 -0000 X-IronPort-AV: E=Sophos;i="4.84,615,1355097600"; d="scan'208";a="1197672" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 06 Feb 2013 13:19:02 +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.297.1; Wed, 6 Feb 2013 13:19:01 +0000 Message-ID: <1360156740.32479.2.camel@zakaz.uk.xensource.com> From: Ian Campbell To: Linux Hack Date: Wed, 6 Feb 2013 13:19:00 +0000 In-Reply-To: References: Organization: Citrix Systems, Inc. X-Mailer: Evolution 3.4.4-1 MIME-Version: 1.0 Cc: "xen-users@lists.xen.org" Subject: Re: [Xen-users] Reg XSA39 X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: 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, 2013-02-05 at 21:39 +0000, Linux Hack wrote: > I guess this needs to be patched into kernel-xen instead of xen > hypervisior right? The advisory stated: xsa39-classic-*.patch Apply to linux-2.6.18-xen tree. So yes, of course. Ian. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Wed Feb 06 13:21:51 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 06 Feb 2013 13:21: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 1U34w5-0003IO-Kh; Wed, 06 Feb 2013 13:21:13 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U34w3-0003I8-U1 for xen-users@lists.xen.org; Wed, 06 Feb 2013 13:21:12 +0000 Received: from [193.109.254.147:42397] by server-3.bemta-14.messagelabs.com id E1/6D-22141-7C852115; Wed, 06 Feb 2013 13:21:11 +0000 X-Env-Sender: Ian.Campbell@citrix.com X-Msg-Ref: server-12.tower-27.messagelabs.com!1360156741!9422920!1 X-Originating-IP: [46.33.159.39] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNDYuMzMuMTU5LjM5ID0+IDIxMjEz\n X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 2655 invoked from network); 6 Feb 2013 13:19:09 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (46.33.159.39) by server-12.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 6 Feb 2013 13:19:09 -0000 X-IronPort-AV: E=Sophos;i="4.84,615,1355097600"; d="scan'208";a="1197672" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 06 Feb 2013 13:19:02 +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.297.1; Wed, 6 Feb 2013 13:19:01 +0000 Message-ID: <1360156740.32479.2.camel@zakaz.uk.xensource.com> From: Ian Campbell To: Linux Hack Date: Wed, 6 Feb 2013 13:19:00 +0000 In-Reply-To: References: Organization: Citrix Systems, Inc. X-Mailer: Evolution 3.4.4-1 MIME-Version: 1.0 Cc: "xen-users@lists.xen.org" Subject: Re: [Xen-users] Reg XSA39 X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: 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, 2013-02-05 at 21:39 +0000, Linux Hack wrote: > I guess this needs to be patched into kernel-xen instead of xen > hypervisior right? The advisory stated: xsa39-classic-*.patch Apply to linux-2.6.18-xen tree. So yes, of course. Ian. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Wed Feb 06 13:22:25 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 06 Feb 2013 13:22: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 1U34wo-0003SI-Ax; Wed, 06 Feb 2013 13:21:58 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U34wn-0003Rx-3l for xen-users@lists.xen.org; Wed, 06 Feb 2013 13:21:57 +0000 Received: from [85.158.143.99:9264] by server-2.bemta-4.messagelabs.com id 9F/1A-01597-4F852115; Wed, 06 Feb 2013 13:21:56 +0000 X-Env-Sender: Ian.Campbell@citrix.com X-Msg-Ref: server-10.tower-216.messagelabs.com!1360156901!23501146!1 X-Originating-IP: [46.33.159.39] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNDYuMzMuMTU5LjM5ID0+IDIxMjEz\n X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 9106 invoked from network); 6 Feb 2013 13:21:50 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (46.33.159.39) by server-10.tower-216.messagelabs.com with RC4-SHA encrypted SMTP; 6 Feb 2013 13:21:50 -0000 X-IronPort-AV: E=Sophos;i="4.84,615,1355097600"; d="scan'208";a="1197785" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 06 Feb 2013 13:21: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.297.1; Wed, 6 Feb 2013 13:21:41 +0000 Message-ID: <1360156900.32479.4.camel@zakaz.uk.xensource.com> From: Ian Campbell To: Linux Hack Date: Wed, 6 Feb 2013 13:21:40 +0000 In-Reply-To: References: Organization: Citrix Systems, Inc. X-Mailer: Evolution 3.4.4-1 MIME-Version: 1.0 Cc: "xen-users@lists.xen.org" Subject: Re: [Xen-users] xsa33 patch 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 On Wed, 2013-02-06 at 01:04 +0000, Linux Hack wrote: > Hi, > > > I am trying to apply the patch xsa33 to the source and making rpm to > install on our server. But this patch doesn't working for Xen-4.1.4 > source and I am getting the below error when I make rpm with this > patch applied. This is fixed by the updated patch in the updated advisory: http://lists.xen.org/archives/html/xen-announce/2013-01/msg00001.html Ian. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Wed Feb 06 13:22:25 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 06 Feb 2013 13:22: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 1U34wo-0003SI-Ax; Wed, 06 Feb 2013 13:21:58 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U34wn-0003Rx-3l for xen-users@lists.xen.org; Wed, 06 Feb 2013 13:21:57 +0000 Received: from [85.158.143.99:9264] by server-2.bemta-4.messagelabs.com id 9F/1A-01597-4F852115; Wed, 06 Feb 2013 13:21:56 +0000 X-Env-Sender: Ian.Campbell@citrix.com X-Msg-Ref: server-10.tower-216.messagelabs.com!1360156901!23501146!1 X-Originating-IP: [46.33.159.39] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNDYuMzMuMTU5LjM5ID0+IDIxMjEz\n X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 9106 invoked from network); 6 Feb 2013 13:21:50 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (46.33.159.39) by server-10.tower-216.messagelabs.com with RC4-SHA encrypted SMTP; 6 Feb 2013 13:21:50 -0000 X-IronPort-AV: E=Sophos;i="4.84,615,1355097600"; d="scan'208";a="1197785" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 06 Feb 2013 13:21: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.297.1; Wed, 6 Feb 2013 13:21:41 +0000 Message-ID: <1360156900.32479.4.camel@zakaz.uk.xensource.com> From: Ian Campbell To: Linux Hack Date: Wed, 6 Feb 2013 13:21:40 +0000 In-Reply-To: References: Organization: Citrix Systems, Inc. X-Mailer: Evolution 3.4.4-1 MIME-Version: 1.0 Cc: "xen-users@lists.xen.org" Subject: Re: [Xen-users] xsa33 patch 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 On Wed, 2013-02-06 at 01:04 +0000, Linux Hack wrote: > Hi, > > > I am trying to apply the patch xsa33 to the source and making rpm to > install on our server. But this patch doesn't working for Xen-4.1.4 > source and I am getting the below error when I make rpm with this > patch applied. This is fixed by the updated patch in the updated advisory: http://lists.xen.org/archives/html/xen-announce/2013-01/msg00001.html Ian. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Wed Feb 06 13:59:43 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 06 Feb 2013 13: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 1U35Wb-0005sp-J2; Wed, 06 Feb 2013 13:58:57 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U35WZ-0005si-Rq for xen-users@lists.xen.org; Wed, 06 Feb 2013 13:58:56 +0000 Received: from [85.158.143.35:6705] by server-1.bemta-4.messagelabs.com id 66/5E-08839-F9162115; Wed, 06 Feb 2013 13:58:55 +0000 X-Env-Sender: mailinglists.tech@gmail.com X-Msg-Ref: server-3.tower-21.messagelabs.com!1360158895!13931641!1 X-Originating-IP: [209.85.212.174] 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.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 15956 invoked from network); 6 Feb 2013 13:54:55 -0000 Received: from mail-wi0-f174.google.com (HELO mail-wi0-f174.google.com) (209.85.212.174) by server-3.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 6 Feb 2013 13:54:55 -0000 Received: by mail-wi0-f174.google.com with SMTP id hi8so5068419wib.13 for ; Wed, 06 Feb 2013 05:54:55 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:date:message-id:subject:from:to :content-type; bh=zB+gbeSfdJDtZmuLGUehY9R6IbVqwdzyzSDFXgpVyps=; b=c+uDVBhYeovZuYjx7MUQ1Kx5fKvCgVM7C2h/7fkGCZ5fV5OuYWAOXQT6+Vj5wywgyd Zhl3lx0Bkk2JZ5EsEk62xWXgy6+i/7tgEybv0tk0yqTO0Kx2n1e2HxF7sfYUZGrHkHWN HFiVP4k8CbvJhkrJYzZsOuqyKlMQR6sHi2ZYO1uyQCpzZOUOEtlw7o31c/TC3dtd+Jx5 kTkVTuUczKThs0LiKfz0m3M6MXoqVYunDjEayMv5SZ5zIgsAe1qB+gJfV4dfDGJsY1ss Ytk1tAncY/OT4NAIa8xCo+0qQGZFJTD3JA8V2HxTs+8w2duhPfpklyVPjBwGY7LB9GlW bsLw== MIME-Version: 1.0 X-Received: by 10.194.76.7 with SMTP id g7mr50306345wjw.50.1360158895367; Wed, 06 Feb 2013 05:54:55 -0800 (PST) Received: by 10.227.203.18 with HTTP; Wed, 6 Feb 2013 05:54:55 -0800 (PST) Date: Wed, 6 Feb 2013 14:54:55 +0100 Message-ID: From: tech mailinglists To: xen-users Subject: [Xen-users] PV or HVM guest for OpenBuildServices Host (OpenSUSE based) X-BeenThere: xen-users@lists.xen.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="===============3866788091629171854==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============3866788091629171854== Content-Type: multipart/alternative; boundary=047d7beba202cbe40504d50eabc5 --047d7beba202cbe40504d50eabc5 Content-Type: text/plain; charset=ISO-8859-1 Hello all, I don't know if it is a silly question but I am really unsure. I informed myself about the OpenBuildService project which was initialized by OpenSUSE. Now I am really interested in setting up an OpenBuildService VM where I can package some programs and so on for example own software and software I wan't to use on a few systems which have for example newer versions not in there offical repository actually. I think that OpenBuildService gives a more or less universal environment and secure build environment. I thought about which guest type I should use. I am not that familiar with for example compiler optimization algorithms and so I asked my self the question would it be better to build up an PV or an HVM OpenSUSE DomU. What would be better? Does it matter if it is a PV or HVM guest for compiler optimazations and so on? Would be great when someone could give me an answer. Best Regards --047d7beba202cbe40504d50eabc5 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Hello all,

I don't know if = it is a silly question but I am really unsure. I informed myself about the = OpenBuildService project which was initialized by OpenSUSE.

No= w I am really interested in setting up an OpenBuildService VM where I can p= ackage some programs and so on for example own software and software I wan&= #39;t to use on a few systems which have for example newer versions not in = there offical repository actually. I think that OpenBuildService gives a mo= re or less universal environment and secure build environment.

I thought about which guest type I should use. I am not that fami= liar with for example compiler optimization algorithms and so I asked my se= lf the question would it be better to build up an PV or an HVM OpenSUSE Dom= U. What would be better? Does it matter if it is a PV or HVM guest for comp= iler optimazations and so on?

Would be great when someone could give me an answer.

Best Regards
--047d7beba202cbe40504d50eabc5-- --===============3866788091629171854== 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 --===============3866788091629171854==-- From xen-users-bounces@lists.xen.org Wed Feb 06 13:59:43 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 06 Feb 2013 13: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 1U35Wb-0005sp-J2; Wed, 06 Feb 2013 13:58:57 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U35WZ-0005si-Rq for xen-users@lists.xen.org; Wed, 06 Feb 2013 13:58:56 +0000 Received: from [85.158.143.35:6705] by server-1.bemta-4.messagelabs.com id 66/5E-08839-F9162115; Wed, 06 Feb 2013 13:58:55 +0000 X-Env-Sender: mailinglists.tech@gmail.com X-Msg-Ref: server-3.tower-21.messagelabs.com!1360158895!13931641!1 X-Originating-IP: [209.85.212.174] 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.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 15956 invoked from network); 6 Feb 2013 13:54:55 -0000 Received: from mail-wi0-f174.google.com (HELO mail-wi0-f174.google.com) (209.85.212.174) by server-3.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 6 Feb 2013 13:54:55 -0000 Received: by mail-wi0-f174.google.com with SMTP id hi8so5068419wib.13 for ; Wed, 06 Feb 2013 05:54:55 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:date:message-id:subject:from:to :content-type; bh=zB+gbeSfdJDtZmuLGUehY9R6IbVqwdzyzSDFXgpVyps=; b=c+uDVBhYeovZuYjx7MUQ1Kx5fKvCgVM7C2h/7fkGCZ5fV5OuYWAOXQT6+Vj5wywgyd Zhl3lx0Bkk2JZ5EsEk62xWXgy6+i/7tgEybv0tk0yqTO0Kx2n1e2HxF7sfYUZGrHkHWN HFiVP4k8CbvJhkrJYzZsOuqyKlMQR6sHi2ZYO1uyQCpzZOUOEtlw7o31c/TC3dtd+Jx5 kTkVTuUczKThs0LiKfz0m3M6MXoqVYunDjEayMv5SZ5zIgsAe1qB+gJfV4dfDGJsY1ss Ytk1tAncY/OT4NAIa8xCo+0qQGZFJTD3JA8V2HxTs+8w2duhPfpklyVPjBwGY7LB9GlW bsLw== MIME-Version: 1.0 X-Received: by 10.194.76.7 with SMTP id g7mr50306345wjw.50.1360158895367; Wed, 06 Feb 2013 05:54:55 -0800 (PST) Received: by 10.227.203.18 with HTTP; Wed, 6 Feb 2013 05:54:55 -0800 (PST) Date: Wed, 6 Feb 2013 14:54:55 +0100 Message-ID: From: tech mailinglists To: xen-users Subject: [Xen-users] PV or HVM guest for OpenBuildServices Host (OpenSUSE based) X-BeenThere: xen-users@lists.xen.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="===============3866788091629171854==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============3866788091629171854== Content-Type: multipart/alternative; boundary=047d7beba202cbe40504d50eabc5 --047d7beba202cbe40504d50eabc5 Content-Type: text/plain; charset=ISO-8859-1 Hello all, I don't know if it is a silly question but I am really unsure. I informed myself about the OpenBuildService project which was initialized by OpenSUSE. Now I am really interested in setting up an OpenBuildService VM where I can package some programs and so on for example own software and software I wan't to use on a few systems which have for example newer versions not in there offical repository actually. I think that OpenBuildService gives a more or less universal environment and secure build environment. I thought about which guest type I should use. I am not that familiar with for example compiler optimization algorithms and so I asked my self the question would it be better to build up an PV or an HVM OpenSUSE DomU. What would be better? Does it matter if it is a PV or HVM guest for compiler optimazations and so on? Would be great when someone could give me an answer. Best Regards --047d7beba202cbe40504d50eabc5 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Hello all,

I don't know if = it is a silly question but I am really unsure. I informed myself about the = OpenBuildService project which was initialized by OpenSUSE.

No= w I am really interested in setting up an OpenBuildService VM where I can p= ackage some programs and so on for example own software and software I wan&= #39;t to use on a few systems which have for example newer versions not in = there offical repository actually. I think that OpenBuildService gives a mo= re or less universal environment and secure build environment.

I thought about which guest type I should use. I am not that fami= liar with for example compiler optimization algorithms and so I asked my se= lf the question would it be better to build up an PV or an HVM OpenSUSE Dom= U. What would be better? Does it matter if it is a PV or HVM guest for comp= iler optimazations and so on?

Would be great when someone could give me an answer.

Best Regards
--047d7beba202cbe40504d50eabc5-- --===============3866788091629171854== 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 --===============3866788091629171854==-- From xen-users-bounces@lists.xen.org Wed Feb 06 14:41:08 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 06 Feb 2013 14:41: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 1U36AR-0007xA-RL; Wed, 06 Feb 2013 14:40:07 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U36AO-0007wx-Na for xen-users@lists.xensource.com; Wed, 06 Feb 2013 14:40:06 +0000 Received: from [85.158.137.99:38974] by server-2.bemta-3.messagelabs.com id FD/C7-25961-34B62115; Wed, 06 Feb 2013 14:40:03 +0000 X-Env-Sender: Markus@hochholdinger.net X-Msg-Ref: server-11.tower-217.messagelabs.com!1360161597!19415690!1 X-Originating-IP: [89.19.235.135] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 26620 invoked from network); 6 Feb 2013 14:39:57 -0000 Received: from group.wh-serverpark.com (HELO group.wh-serverpark.com) (89.19.235.135) by server-11.tower-217.messagelabs.com with SMTP; 6 Feb 2013 14:39:57 -0000 Received: from localhost (localhost [127.0.0.1]) by group.wh-serverpark.com (Postfix) with ESMTP id 8B3649810A; Wed, 6 Feb 2013 15:39:42 +0100 (CET) X-Virus-Scanned: amavisd-new at valiant.wh-serverpark.com Received: from group.wh-serverpark.com ([127.0.0.1]) by localhost (group.wh-serverpark.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QpY1dLx0LWGZ; Wed, 6 Feb 2013 15:39:41 +0100 (CET) Received: from enterprise.localnet (et-0-30.gw-nat.bs.kae.de.oneandone.net [212.227.35.94]) by group.wh-serverpark.com (Postfix) with ESMTPSA id 80290980CD; Wed, 6 Feb 2013 15:39:41 +0100 (CET) From: Markus Hochholdinger To: Ian Campbell Date: Wed, 6 Feb 2013 15:39:37 +0100 User-Agent: KMail/1.13.7 (Linux/3.2.0-4-amd64; KDE/4.8.4; x86_64; ; ) References: <201301291646.43567.Markus@hochholdinger.net> <201301312044.17684.Markus@hochholdinger.net> <1359708995.9063.3.camel@dagon.hellion.org.uk> In-Reply-To: <1359708995.9063.3.camel@dagon.hellion.org.uk> MIME-Version: 1.0 Message-Id: <201302061539.40900.Markus@hochholdinger.net> Cc: "xen-users@lists.xensource.com" Subject: Re: [Xen-users] linux stubdom X-BeenThere: xen-users@lists.xen.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="===============8090097313789172367==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============8090097313789172367== Content-Type: multipart/signed; boundary="nextPart14810175.MTYN5Fseuj"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit --nextPart14810175.MTYN5Fseuj Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hello, Am 01.02.2013 um 09:56 Uhr schrieb Ian Campbell : > > > > Am I missing something? > > > Migration is a staged process. > > > 1. First an empty shell domain (with no devices) is created on t= he > > > target host. > > > 2. Then we copy the memory over, in several iterations, while the > > > domain is running on the source host (iterations happen to > > > handle the guest dirtying memory as we copy, this is the "liv= e" > > > aspect of the migration). > > > 3. After some iterations of live migration we pause the source > > > guest > > > 4. Now we copy the remaining dirty RAM > > > 5. Tear down devices on the source host > > > 6. Setup devices on the target host for the incoming domain > > > 7. Resume the guest on the target domain > > > 8. Guest reconnects to new backend > > > The key point is that the devices are only ever active on either the > > > source or the target host and never both. The domain is paused during > > > this final transfer (from #3 until #7) and therefore guest I/O is > > > quiesced. > > At what point are scripts like > > disk =3D [ ".., script=3Dmyblockscript.sh" ] > > executed? Would this be between #3 and #7? > It is part of the device teardown and setup, so it is during #5 and #6 > (strictly I think it is just after #5 and just before #6). > On xen-devel at the minute there is a patch series under discussion to > make the script hooks more flexible, in particular adding pre and post > migrate hooks (called something like #1-#3 and #7-#7) which can pre > setup bits of the storage stack which are safe to do with the guest > running but might be slow to initialise (e.g. iSCSI login, but not > opening the device). I don't think this needs to affect you though. at least with xm toolstack, block-scripts in /etc/xen/scripts/block-* are=20 executed on the destination host (add) before the script (remove) on the=20 source host is executed while live migrating a domU. (I've created the script /etc/xen/scripts/block-md which assembles and stop= s=20 raid1 devices.) Next, I'll test xl toolstack with this setup. [..] =2D-=20 greetings eMHa --nextPart14810175.MTYN5Fseuj Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (GNU/Linux) iEYEABECAAYFAlESaykACgkQXT3LE+AjWCvF7ACeKBoMvfeDCd5HbIP6lFpVkDXU atIAoPhqJBy+wsDnQRgm2AG72tP2LSAo =x0q0 -----END PGP SIGNATURE----- --nextPart14810175.MTYN5Fseuj-- --===============8090097313789172367== 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 --===============8090097313789172367==-- From xen-users-bounces@lists.xen.org Wed Feb 06 14:41:08 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 06 Feb 2013 14:41: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 1U36AR-0007xA-RL; Wed, 06 Feb 2013 14:40:07 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U36AO-0007wx-Na for xen-users@lists.xensource.com; Wed, 06 Feb 2013 14:40:06 +0000 Received: from [85.158.137.99:38974] by server-2.bemta-3.messagelabs.com id FD/C7-25961-34B62115; Wed, 06 Feb 2013 14:40:03 +0000 X-Env-Sender: Markus@hochholdinger.net X-Msg-Ref: server-11.tower-217.messagelabs.com!1360161597!19415690!1 X-Originating-IP: [89.19.235.135] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 26620 invoked from network); 6 Feb 2013 14:39:57 -0000 Received: from group.wh-serverpark.com (HELO group.wh-serverpark.com) (89.19.235.135) by server-11.tower-217.messagelabs.com with SMTP; 6 Feb 2013 14:39:57 -0000 Received: from localhost (localhost [127.0.0.1]) by group.wh-serverpark.com (Postfix) with ESMTP id 8B3649810A; Wed, 6 Feb 2013 15:39:42 +0100 (CET) X-Virus-Scanned: amavisd-new at valiant.wh-serverpark.com Received: from group.wh-serverpark.com ([127.0.0.1]) by localhost (group.wh-serverpark.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QpY1dLx0LWGZ; Wed, 6 Feb 2013 15:39:41 +0100 (CET) Received: from enterprise.localnet (et-0-30.gw-nat.bs.kae.de.oneandone.net [212.227.35.94]) by group.wh-serverpark.com (Postfix) with ESMTPSA id 80290980CD; Wed, 6 Feb 2013 15:39:41 +0100 (CET) From: Markus Hochholdinger To: Ian Campbell Date: Wed, 6 Feb 2013 15:39:37 +0100 User-Agent: KMail/1.13.7 (Linux/3.2.0-4-amd64; KDE/4.8.4; x86_64; ; ) References: <201301291646.43567.Markus@hochholdinger.net> <201301312044.17684.Markus@hochholdinger.net> <1359708995.9063.3.camel@dagon.hellion.org.uk> In-Reply-To: <1359708995.9063.3.camel@dagon.hellion.org.uk> MIME-Version: 1.0 Message-Id: <201302061539.40900.Markus@hochholdinger.net> Cc: "xen-users@lists.xensource.com" Subject: Re: [Xen-users] linux stubdom X-BeenThere: xen-users@lists.xen.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="===============8090097313789172367==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============8090097313789172367== Content-Type: multipart/signed; boundary="nextPart14810175.MTYN5Fseuj"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit --nextPart14810175.MTYN5Fseuj Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hello, Am 01.02.2013 um 09:56 Uhr schrieb Ian Campbell : > > > > Am I missing something? > > > Migration is a staged process. > > > 1. First an empty shell domain (with no devices) is created on t= he > > > target host. > > > 2. Then we copy the memory over, in several iterations, while the > > > domain is running on the source host (iterations happen to > > > handle the guest dirtying memory as we copy, this is the "liv= e" > > > aspect of the migration). > > > 3. After some iterations of live migration we pause the source > > > guest > > > 4. Now we copy the remaining dirty RAM > > > 5. Tear down devices on the source host > > > 6. Setup devices on the target host for the incoming domain > > > 7. Resume the guest on the target domain > > > 8. Guest reconnects to new backend > > > The key point is that the devices are only ever active on either the > > > source or the target host and never both. The domain is paused during > > > this final transfer (from #3 until #7) and therefore guest I/O is > > > quiesced. > > At what point are scripts like > > disk =3D [ ".., script=3Dmyblockscript.sh" ] > > executed? Would this be between #3 and #7? > It is part of the device teardown and setup, so it is during #5 and #6 > (strictly I think it is just after #5 and just before #6). > On xen-devel at the minute there is a patch series under discussion to > make the script hooks more flexible, in particular adding pre and post > migrate hooks (called something like #1-#3 and #7-#7) which can pre > setup bits of the storage stack which are safe to do with the guest > running but might be slow to initialise (e.g. iSCSI login, but not > opening the device). I don't think this needs to affect you though. at least with xm toolstack, block-scripts in /etc/xen/scripts/block-* are=20 executed on the destination host (add) before the script (remove) on the=20 source host is executed while live migrating a domU. (I've created the script /etc/xen/scripts/block-md which assembles and stop= s=20 raid1 devices.) Next, I'll test xl toolstack with this setup. [..] =2D-=20 greetings eMHa --nextPart14810175.MTYN5Fseuj Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (GNU/Linux) iEYEABECAAYFAlESaykACgkQXT3LE+AjWCvF7ACeKBoMvfeDCd5HbIP6lFpVkDXU atIAoPhqJBy+wsDnQRgm2AG72tP2LSAo =x0q0 -----END PGP SIGNATURE----- --nextPart14810175.MTYN5Fseuj-- --===============8090097313789172367== 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 --===============8090097313789172367==-- From xen-users-bounces@lists.xen.org Wed Feb 06 15:24:45 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 06 Feb 2013 15:24: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 1U36qq-0001zm-CS; Wed, 06 Feb 2013 15:23:56 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U36qp-0001zh-8n for xen-users@lists.xen.org; Wed, 06 Feb 2013 15:23:55 +0000 Received: from [85.158.139.83:32280] by server-3.bemta-5.messagelabs.com id 59/EC-07037-A8572115; Wed, 06 Feb 2013 15:23:54 +0000 X-Env-Sender: alk@ondore.com X-Msg-Ref: server-15.tower-182.messagelabs.com!1360164232!30997823!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.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 15856 invoked from network); 6 Feb 2013 15:23:53 -0000 Received: from host0a.ondore-systems.com (HELO host0a.ondore-systems.com) (184.172.38.138) by server-15.tower-182.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 6 Feb 2013 15:23:53 -0000 Received: from [201.122.115.101] (port=34768 helo=mail.ondore.i) by host0a.ondore-systems.com with esmtpsa (TLSv1:DHE-RSA-AES256-SHA:256) (Exim 4.80) (envelope-from ) id 1U36qm-0002u9-5c for xen-users@lists.xen.org; Wed, 06 Feb 2013 09:23:52 -0600 Received: from [10.13.34.96] (alk-desktop.sys.ondore.i [10.13.34.96]) by mail.ondore.i (Postfix) with ESMTPSA id 47FADA209 for ; Wed, 6 Feb 2013 09:20:02 -0600 (CST) Message-ID: <51127586.4080206@ondore.com> Date: Wed, 06 Feb 2013 09:23:50 -0600 From: Alexandre Kouznetsov User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130106 Thunderbird/17.0.2 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 X-Get-Message-Sender-Via: host0a.ondore-systems.com: authenticated_id: sys.intranet@ondore.com Subject: Re: [Xen-users] How to auto start DomU after reboot of 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-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. El 06/02/13 07:18, Carlos Ribas escribi=F3: > I followed some tutorials to install Xen in a Debian Squeeze > server. One of them [1] says to set up XENDOMAINS_RESTORE to false, > because I can have problems with that. So, if my server shuts down or > reboots how can I configure my VM to automatically start? That option has to do with Xen's feature to save/restore the domains, = instead of shutdown/startup. A close equivalent in baremetal computing = would be suspend/resume. > Yesterday I did a quick script [2] that worked well, but I am not > sure if it is the best way to do it. I would like to know what you do > solve this issue. Squeeze's Xend provides a very simple way to autostart the domains, = regardless they was saved or shot down. Check /etc/defaults/xendomains = file, it's heavily commented, particularly XENDOMAINS_AUTO section. Note = that you will have to create the directory /etc/xen/auto manually. I usually put there symbolic links to config files (that are stored = directly under /etc/xen), instead of the configuration files themselves. Greetings. -- = Alexandre Kouznetsov _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Wed Feb 06 15:24:45 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 06 Feb 2013 15:24: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 1U36qq-0001zm-CS; Wed, 06 Feb 2013 15:23:56 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U36qp-0001zh-8n for xen-users@lists.xen.org; Wed, 06 Feb 2013 15:23:55 +0000 Received: from [85.158.139.83:32280] by server-3.bemta-5.messagelabs.com id 59/EC-07037-A8572115; Wed, 06 Feb 2013 15:23:54 +0000 X-Env-Sender: alk@ondore.com X-Msg-Ref: server-15.tower-182.messagelabs.com!1360164232!30997823!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.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 15856 invoked from network); 6 Feb 2013 15:23:53 -0000 Received: from host0a.ondore-systems.com (HELO host0a.ondore-systems.com) (184.172.38.138) by server-15.tower-182.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 6 Feb 2013 15:23:53 -0000 Received: from [201.122.115.101] (port=34768 helo=mail.ondore.i) by host0a.ondore-systems.com with esmtpsa (TLSv1:DHE-RSA-AES256-SHA:256) (Exim 4.80) (envelope-from ) id 1U36qm-0002u9-5c for xen-users@lists.xen.org; Wed, 06 Feb 2013 09:23:52 -0600 Received: from [10.13.34.96] (alk-desktop.sys.ondore.i [10.13.34.96]) by mail.ondore.i (Postfix) with ESMTPSA id 47FADA209 for ; Wed, 6 Feb 2013 09:20:02 -0600 (CST) Message-ID: <51127586.4080206@ondore.com> Date: Wed, 06 Feb 2013 09:23:50 -0600 From: Alexandre Kouznetsov User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130106 Thunderbird/17.0.2 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 X-Get-Message-Sender-Via: host0a.ondore-systems.com: authenticated_id: sys.intranet@ondore.com Subject: Re: [Xen-users] How to auto start DomU after reboot of 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-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. El 06/02/13 07:18, Carlos Ribas escribi=F3: > I followed some tutorials to install Xen in a Debian Squeeze > server. One of them [1] says to set up XENDOMAINS_RESTORE to false, > because I can have problems with that. So, if my server shuts down or > reboots how can I configure my VM to automatically start? That option has to do with Xen's feature to save/restore the domains, = instead of shutdown/startup. A close equivalent in baremetal computing = would be suspend/resume. > Yesterday I did a quick script [2] that worked well, but I am not > sure if it is the best way to do it. I would like to know what you do > solve this issue. Squeeze's Xend provides a very simple way to autostart the domains, = regardless they was saved or shot down. Check /etc/defaults/xendomains = file, it's heavily commented, particularly XENDOMAINS_AUTO section. Note = that you will have to create the directory /etc/xen/auto manually. I usually put there symbolic links to config files (that are stored = directly under /etc/xen), instead of the configuration files themselves. Greetings. -- = Alexandre Kouznetsov _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Wed Feb 06 16:06:20 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 06 Feb 2013 16:06: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 1U37Uy-0004MC-5I; Wed, 06 Feb 2013 16:05:24 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U37Uw-0004M7-QT for xen-users@lists.xen.org; Wed, 06 Feb 2013 16:05:23 +0000 Received: from [85.158.139.211:33933] by server-11.bemta-5.messagelabs.com id 4F/10-19159-14F72115; Wed, 06 Feb 2013 16:05:21 +0000 X-Env-Sender: thore@datensumpf.de X-Msg-Ref: server-12.tower-206.messagelabs.com!1360166720!18626461!1 X-Originating-IP: [212.12.52.213] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 17847 invoked from network); 6 Feb 2013 16:05:21 -0000 Received: from mail-2.ramdrive.org (HELO mail-2.ramdrive.org) (212.12.52.213) by server-12.tower-206.messagelabs.com with SMTP; 6 Feb 2013 16:05:21 -0000 Received: from localhost (localhost [127.0.0.1]) by mail-2.ramdrive.org (Postfix) with ESMTP id 5B91C783DD50 for ; Wed, 6 Feb 2013 16:14:38 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at mail-2.ramdrive.org Received: from mail-2.ramdrive.org ([127.0.0.1]) by localhost (mail-2.ramdrive.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zQRBHTTXP2Cb for ; Wed, 6 Feb 2013 16:14:37 +0000 (UTC) Received: from [127.0.0.1] (g224083194.adsl.alicedsl.de [92.224.83.194]) by mail-2.ramdrive.org (Postfix) with ESMTPSA id 88CE7783DD4A for ; Wed, 6 Feb 2013 16:14:37 +0000 (UTC) Message-ID: <51127F3E.1040304@datensumpf.de> Date: Wed, 06 Feb 2013 17:05:18 +0100 From: Thore User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130107 Thunderbird/17.0.2 MIME-Version: 1.0 To: xen-users@lists.xen.org References: <07C333514DC1233EBC29AFA91F4B2FC6@thehobsons.co.uk> In-Reply-To: <07C333514DC1233EBC29AFA91F4B2FC6@thehobsons.co.uk> Subject: Re: [Xen-users] Using Ipv4 and IPv6 Subnet X-BeenThere: xen-users@lists.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 Am 06.02.2013 13:00, schrieb Simon Hobson: > Thore wrote: >> I have a problem/question for understanding. >> I have on my server (debian wheezy) 3 virtual systems running on xen >> with own IPv4 addresses. >> Form my hoster I got an IPv6 subnet, but I don't really know how to add it. >> Is it enought to add an address of it in the /etc/network/interfaces of >> the virtual systems? >> Or must I set up routing for Xen and how does it works together with >> bridging? >> Which settings I had to change? >> And am I able to set up an system only with Ipv6? >> (I have IPv6) > > > These are mostly not really Xen questions, more a general networking issue. > > The first question is, how does the hoster present your networking ? And how is your Xen networking set up ? > > If (for example) your hoster presents you an ethernet cable, with your own IP range and a gateway address for their router; and you are using bridging on Xen; then it will simply be a case of configuring an IPv6 address on each box. > Configuring IPv6 can be done several ways, and that depends on how the routers are configured. At it's simplest, the router(s) will advertise themselves and your devices can self-assign an address - auto configuration which should "just work". For hosting, you probably want to manually configure IPv6 addresses so they are fixed. I have a xenbr0 auto xenbr0 iface xenbr0 inet static address 1.2.3.4 netmask 255.255.255.255 gateway 2.3.4.5 bridge_ports eth0 Like this is my bridge configuration. Some time before I set this in my /etc/network/interfaces #iface eth0 inet6 static # address 2a01:4f8:140:1:2 # netmask 64 # gateway fe80::1 At the moment it is inaktive. I have 3 IPv4 Adresses, no Subnet. The server has only an eth0. And if it helps it is hosted by hetzner regards Thore _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Wed Feb 06 16:06:20 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 06 Feb 2013 16:06: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 1U37Uy-0004MC-5I; Wed, 06 Feb 2013 16:05:24 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U37Uw-0004M7-QT for xen-users@lists.xen.org; Wed, 06 Feb 2013 16:05:23 +0000 Received: from [85.158.139.211:33933] by server-11.bemta-5.messagelabs.com id 4F/10-19159-14F72115; Wed, 06 Feb 2013 16:05:21 +0000 X-Env-Sender: thore@datensumpf.de X-Msg-Ref: server-12.tower-206.messagelabs.com!1360166720!18626461!1 X-Originating-IP: [212.12.52.213] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 17847 invoked from network); 6 Feb 2013 16:05:21 -0000 Received: from mail-2.ramdrive.org (HELO mail-2.ramdrive.org) (212.12.52.213) by server-12.tower-206.messagelabs.com with SMTP; 6 Feb 2013 16:05:21 -0000 Received: from localhost (localhost [127.0.0.1]) by mail-2.ramdrive.org (Postfix) with ESMTP id 5B91C783DD50 for ; Wed, 6 Feb 2013 16:14:38 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at mail-2.ramdrive.org Received: from mail-2.ramdrive.org ([127.0.0.1]) by localhost (mail-2.ramdrive.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zQRBHTTXP2Cb for ; Wed, 6 Feb 2013 16:14:37 +0000 (UTC) Received: from [127.0.0.1] (g224083194.adsl.alicedsl.de [92.224.83.194]) by mail-2.ramdrive.org (Postfix) with ESMTPSA id 88CE7783DD4A for ; Wed, 6 Feb 2013 16:14:37 +0000 (UTC) Message-ID: <51127F3E.1040304@datensumpf.de> Date: Wed, 06 Feb 2013 17:05:18 +0100 From: Thore User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130107 Thunderbird/17.0.2 MIME-Version: 1.0 To: xen-users@lists.xen.org References: <07C333514DC1233EBC29AFA91F4B2FC6@thehobsons.co.uk> In-Reply-To: <07C333514DC1233EBC29AFA91F4B2FC6@thehobsons.co.uk> Subject: Re: [Xen-users] Using Ipv4 and IPv6 Subnet X-BeenThere: xen-users@lists.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 Am 06.02.2013 13:00, schrieb Simon Hobson: > Thore wrote: >> I have a problem/question for understanding. >> I have on my server (debian wheezy) 3 virtual systems running on xen >> with own IPv4 addresses. >> Form my hoster I got an IPv6 subnet, but I don't really know how to add it. >> Is it enought to add an address of it in the /etc/network/interfaces of >> the virtual systems? >> Or must I set up routing for Xen and how does it works together with >> bridging? >> Which settings I had to change? >> And am I able to set up an system only with Ipv6? >> (I have IPv6) > > > These are mostly not really Xen questions, more a general networking issue. > > The first question is, how does the hoster present your networking ? And how is your Xen networking set up ? > > If (for example) your hoster presents you an ethernet cable, with your own IP range and a gateway address for their router; and you are using bridging on Xen; then it will simply be a case of configuring an IPv6 address on each box. > Configuring IPv6 can be done several ways, and that depends on how the routers are configured. At it's simplest, the router(s) will advertise themselves and your devices can self-assign an address - auto configuration which should "just work". For hosting, you probably want to manually configure IPv6 addresses so they are fixed. I have a xenbr0 auto xenbr0 iface xenbr0 inet static address 1.2.3.4 netmask 255.255.255.255 gateway 2.3.4.5 bridge_ports eth0 Like this is my bridge configuration. Some time before I set this in my /etc/network/interfaces #iface eth0 inet6 static # address 2a01:4f8:140:1:2 # netmask 64 # gateway fe80::1 At the moment it is inaktive. I have 3 IPv4 Adresses, no Subnet. The server has only an eth0. And if it helps it is hosted by hetzner regards Thore _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Wed Feb 06 16:07:32 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 06 Feb 2013 16:07: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 1U37W9-0004Pu-SJ; Wed, 06 Feb 2013 16:06:37 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U37W8-0004Pl-1q for xen-users@lists.xen.org; Wed, 06 Feb 2013 16:06:36 +0000 Received: from [85.158.139.83:41975] by server-2.bemta-5.messagelabs.com id 24/DC-16911-B8F72115; Wed, 06 Feb 2013 16:06:35 +0000 X-Env-Sender: tolga@ozses.net X-Msg-Ref: server-12.tower-182.messagelabs.com!1360166789!31109582!1 X-Originating-IP: [209.85.210.43] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 18248 invoked from network); 6 Feb 2013 16:06:31 -0000 Received: from mail-da0-f43.google.com (HELO mail-da0-f43.google.com) (209.85.210.43) by server-12.tower-182.messagelabs.com with RC4-SHA encrypted SMTP; 6 Feb 2013 16:06:31 -0000 Received: by mail-da0-f43.google.com with SMTP id u36so733884dak.30 for ; Wed, 06 Feb 2013 08:06:29 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=x-received:references:from:mime-version:in-reply-to:date:message-id :subject:to:cc:content-type:content-transfer-encoding :x-gm-message-state; bh=JRlK5mr0of1FbVNHQoUfXzY+o63fUKIOf7Z3q4ZnMSM=; b=GNWRpw4zOIGqOFDHitYu8C9XDnbRA7slToXxL3nmNdzPL6sQDutx4cFvkuW44Vw4Wo Icd0avKua5lYhtQl49GNfVxha+NFxiLkOTO9s7sG3lS3QB3JQCNoUJzBg0l+nNlUfUSe 4rSSJ0WOUEE59APTAB22OKoeB7+yG59J2XoUUAbLzkM+Z4clHKY/gjqp5C4Lcq397Uv+ XiSgqlD85KTIabVZg82Kh+wq9ErFbYyz2ZHjie55iCd4p/SpHoJCqVTMOrR9H/429c7E HnxvKsCsbioauz/pgpgAUU1bsPTpkcR0eF0KZf7DPQNtpnA2/7gajVG7ID5Y5Bb219zj mngA== X-Received: by 10.66.78.1 with SMTP id x1mr77149215paw.2.1360166789252; Wed, 06 Feb 2013 08:06:29 -0800 (PST) References: <51127586.4080206@ondore.com> From: Muzaffer Tolga Ozses Mime-Version: 1.0 (1.0) In-Reply-To: <51127586.4080206@ondore.com> Date: Wed, 6 Feb 2013 18:06:28 +0200 Message-ID: <-5850233638147328292@unknownmsgid> To: Alexandre Kouznetsov X-Gm-Message-State: ALoCoQlBm2TYBb1Y8pc6Y0OsewNFLJYDQ5ZJqc/6nE7ua2qf97qY0N3XSegcx5rULPtMSJvyCPJf Cc: "xen-users@lists.xen.org" Subject: Re: [Xen-users] How to auto start DomU after reboot of 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: text/plain; charset="iso-8859-9" Content-Transfer-Encoding: quoted-printable Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org You could also start them using cron like below: @reboot xm create vm.cfg Regards M myPhone'dan g=F6nderdim 6 =DEub 2013 tarihinde 17:28 saatinde, Alexandre Kouznetsov =FEunlar=FD yazd=FD: > Hello. > > El 06/02/13 07:18, Carlos Ribas escribi=F3: >> I followed some tutorials to install Xen in a Debian Squeeze >> server. One of them [1] says to set up XENDOMAINS_RESTORE to false, >> because I can have problems with that. So, if my server shuts down or >> reboots how can I configure my VM to automatically start? > That option has to do with Xen's feature to save/restore the domains, ins= tead of shutdown/startup. A close equivalent in baremetal computing would b= e suspend/resume. > >> Yesterday I did a quick script [2] that worked well, but I am not >> sure if it is the best way to do it. I would like to know what you do >> solve this issue. > Squeeze's Xend provides a very simple way to autostart the domains, regar= dless they was saved or shot down. Check /etc/defaults/xendomains file, it'= s heavily commented, particularly XENDOMAINS_AUTO section. Note that you wi= ll have to create the directory /etc/xen/auto manually. > I usually put there symbolic links to config files (that are stored direc= tly under /etc/xen), instead of the configuration files themselves. > > Greetings. > > -- > Alexandre Kouznetsov > > > _______________________________________________ > 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 Feb 06 16:07:32 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 06 Feb 2013 16:07: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 1U37W9-0004Pu-SJ; Wed, 06 Feb 2013 16:06:37 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U37W8-0004Pl-1q for xen-users@lists.xen.org; Wed, 06 Feb 2013 16:06:36 +0000 Received: from [85.158.139.83:41975] by server-2.bemta-5.messagelabs.com id 24/DC-16911-B8F72115; Wed, 06 Feb 2013 16:06:35 +0000 X-Env-Sender: tolga@ozses.net X-Msg-Ref: server-12.tower-182.messagelabs.com!1360166789!31109582!1 X-Originating-IP: [209.85.210.43] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 18248 invoked from network); 6 Feb 2013 16:06:31 -0000 Received: from mail-da0-f43.google.com (HELO mail-da0-f43.google.com) (209.85.210.43) by server-12.tower-182.messagelabs.com with RC4-SHA encrypted SMTP; 6 Feb 2013 16:06:31 -0000 Received: by mail-da0-f43.google.com with SMTP id u36so733884dak.30 for ; Wed, 06 Feb 2013 08:06:29 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=x-received:references:from:mime-version:in-reply-to:date:message-id :subject:to:cc:content-type:content-transfer-encoding :x-gm-message-state; bh=JRlK5mr0of1FbVNHQoUfXzY+o63fUKIOf7Z3q4ZnMSM=; b=GNWRpw4zOIGqOFDHitYu8C9XDnbRA7slToXxL3nmNdzPL6sQDutx4cFvkuW44Vw4Wo Icd0avKua5lYhtQl49GNfVxha+NFxiLkOTO9s7sG3lS3QB3JQCNoUJzBg0l+nNlUfUSe 4rSSJ0WOUEE59APTAB22OKoeB7+yG59J2XoUUAbLzkM+Z4clHKY/gjqp5C4Lcq397Uv+ XiSgqlD85KTIabVZg82Kh+wq9ErFbYyz2ZHjie55iCd4p/SpHoJCqVTMOrR9H/429c7E HnxvKsCsbioauz/pgpgAUU1bsPTpkcR0eF0KZf7DPQNtpnA2/7gajVG7ID5Y5Bb219zj mngA== X-Received: by 10.66.78.1 with SMTP id x1mr77149215paw.2.1360166789252; Wed, 06 Feb 2013 08:06:29 -0800 (PST) References: <51127586.4080206@ondore.com> From: Muzaffer Tolga Ozses Mime-Version: 1.0 (1.0) In-Reply-To: <51127586.4080206@ondore.com> Date: Wed, 6 Feb 2013 18:06:28 +0200 Message-ID: <-5850233638147328292@unknownmsgid> To: Alexandre Kouznetsov X-Gm-Message-State: ALoCoQlBm2TYBb1Y8pc6Y0OsewNFLJYDQ5ZJqc/6nE7ua2qf97qY0N3XSegcx5rULPtMSJvyCPJf Cc: "xen-users@lists.xen.org" Subject: Re: [Xen-users] How to auto start DomU after reboot of 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: text/plain; charset="iso-8859-9" Content-Transfer-Encoding: quoted-printable Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org You could also start them using cron like below: @reboot xm create vm.cfg Regards M myPhone'dan g=F6nderdim 6 =DEub 2013 tarihinde 17:28 saatinde, Alexandre Kouznetsov =FEunlar=FD yazd=FD: > Hello. > > El 06/02/13 07:18, Carlos Ribas escribi=F3: >> I followed some tutorials to install Xen in a Debian Squeeze >> server. One of them [1] says to set up XENDOMAINS_RESTORE to false, >> because I can have problems with that. So, if my server shuts down or >> reboots how can I configure my VM to automatically start? > That option has to do with Xen's feature to save/restore the domains, ins= tead of shutdown/startup. A close equivalent in baremetal computing would b= e suspend/resume. > >> Yesterday I did a quick script [2] that worked well, but I am not >> sure if it is the best way to do it. I would like to know what you do >> solve this issue. > Squeeze's Xend provides a very simple way to autostart the domains, regar= dless they was saved or shot down. Check /etc/defaults/xendomains file, it'= s heavily commented, particularly XENDOMAINS_AUTO section. Note that you wi= ll have to create the directory /etc/xen/auto manually. > I usually put there symbolic links to config files (that are stored direc= tly under /etc/xen), instead of the configuration files themselves. > > Greetings. > > -- > Alexandre Kouznetsov > > > _______________________________________________ > 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 Feb 06 16:43:35 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 06 Feb 2013 16:43: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 1U3858-0006ut-DU; Wed, 06 Feb 2013 16:42:46 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U3857-0006uo-7G for xen-users@lists.xen.org; Wed, 06 Feb 2013 16:42:45 +0000 Received: from [85.158.138.51:46449] by server-16.bemta-3.messagelabs.com id D5/7F-02727-40882115; Wed, 06 Feb 2013 16:42:44 +0000 X-Env-Sender: linux@thehobsons.co.uk X-Msg-Ref: server-7.tower-174.messagelabs.com!1360168963!22333376!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.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 27424 invoked from network); 6 Feb 2013 16:42:43 -0000 Received: from patsy.thehobsons.co.uk (HELO patsy.thehobsons.co.uk) (81.174.135.208) by server-7.tower-174.messagelabs.com with SMTP; 6 Feb 2013 16:42:43 -0000 Received: from localhost (localhost [127.0.0.1]) by patsy.thehobsons.co.uk (Postfix) with ESMTP id C0EA810401A for ; Wed, 6 Feb 2013 16:42:41 +0000 (GMT) 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 1RpIVR-a3z4S for ; Wed, 6 Feb 2013 16:42:41 +0000 (GMT) Received: from localhost (patsy.thehobsons.co.uk [192.168.0.33]) by patsy.thehobsons.co.uk (Postfix) with ESMTP id 522A529F25 for ; Wed, 6 Feb 2013 16:42:41 +0000 (GMT) From: "Simon Hobson" To: xen-users@lists.xen.org Date: Wed, 6 Feb 2013 16:42:41 +0000 X-Priority: 3 X-Mailer: MailForge 3.0 Mac OS X Message-ID: <01FF60612CDD7CEA56FE205A4B6AD6@thehobsons.co.uk> Subject: Re: [Xen-users] Using Ipv4 and IPv6 Subnet X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org Thore wrote: >I have a xenbr0 Then there is nothing Xen-specific to set up >Some time before I set this in my /etc/network/interfaces >#iface eth0 inet6 static ># address 2a01:4f8:140:1:2 ># netmask 64 ># gateway fe80::1 fe80 addresses are self-assigned link-local, and you probably don't have an fe80::1 on the network. You need to set both a valid address and gateway. 2a01:4f8:140:1:2 is not a valid IPv6 address - is there a typo there (too few groups, is there a :: missing) ? The gateway might be configured by Route Advertisement broadcasts, or it might be configured manually - what does your hoster tell you to use ? >At the moment it is inaktive. >I have 3 IPv4 Adresses, no Subnet. Actually, you will have a subnet, but most likely you have 3 IPs from a larger subnet shared with other hosting clients. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Wed Feb 06 16:43:35 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 06 Feb 2013 16:43: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 1U3858-0006ut-DU; Wed, 06 Feb 2013 16:42:46 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U3857-0006uo-7G for xen-users@lists.xen.org; Wed, 06 Feb 2013 16:42:45 +0000 Received: from [85.158.138.51:46449] by server-16.bemta-3.messagelabs.com id D5/7F-02727-40882115; Wed, 06 Feb 2013 16:42:44 +0000 X-Env-Sender: linux@thehobsons.co.uk X-Msg-Ref: server-7.tower-174.messagelabs.com!1360168963!22333376!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.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 27424 invoked from network); 6 Feb 2013 16:42:43 -0000 Received: from patsy.thehobsons.co.uk (HELO patsy.thehobsons.co.uk) (81.174.135.208) by server-7.tower-174.messagelabs.com with SMTP; 6 Feb 2013 16:42:43 -0000 Received: from localhost (localhost [127.0.0.1]) by patsy.thehobsons.co.uk (Postfix) with ESMTP id C0EA810401A for ; Wed, 6 Feb 2013 16:42:41 +0000 (GMT) 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 1RpIVR-a3z4S for ; Wed, 6 Feb 2013 16:42:41 +0000 (GMT) Received: from localhost (patsy.thehobsons.co.uk [192.168.0.33]) by patsy.thehobsons.co.uk (Postfix) with ESMTP id 522A529F25 for ; Wed, 6 Feb 2013 16:42:41 +0000 (GMT) From: "Simon Hobson" To: xen-users@lists.xen.org Date: Wed, 6 Feb 2013 16:42:41 +0000 X-Priority: 3 X-Mailer: MailForge 3.0 Mac OS X Message-ID: <01FF60612CDD7CEA56FE205A4B6AD6@thehobsons.co.uk> Subject: Re: [Xen-users] Using Ipv4 and IPv6 Subnet X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org Thore wrote: >I have a xenbr0 Then there is nothing Xen-specific to set up >Some time before I set this in my /etc/network/interfaces >#iface eth0 inet6 static ># address 2a01:4f8:140:1:2 ># netmask 64 ># gateway fe80::1 fe80 addresses are self-assigned link-local, and you probably don't have an fe80::1 on the network. You need to set both a valid address and gateway. 2a01:4f8:140:1:2 is not a valid IPv6 address - is there a typo there (too few groups, is there a :: missing) ? The gateway might be configured by Route Advertisement broadcasts, or it might be configured manually - what does your hoster tell you to use ? >At the moment it is inaktive. >I have 3 IPv4 Adresses, no Subnet. Actually, you will have a subnet, but most likely you have 3 IPs from a larger subnet shared with other hosting clients. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Wed Feb 06 17:41:22 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 06 Feb 2013 17:41: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 1U38yl-0001eJ-Ex; Wed, 06 Feb 2013 17:40:15 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U38yj-0001eE-N5 for xen-users@lists.xen.org; Wed, 06 Feb 2013 17:40:13 +0000 Received: from [85.158.143.99:20609] by server-1.bemta-4.messagelabs.com id 0B/78-08839-C7592115; Wed, 06 Feb 2013 17:40:12 +0000 X-Env-Sender: carlos@ansp.br X-Msg-Ref: server-15.tower-216.messagelabs.com!1360172408!31118504!1 X-Originating-IP: [209.85.219.46] 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.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 17430 invoked from network); 6 Feb 2013 17:40:10 -0000 Received: from mail-oa0-f46.google.com (HELO mail-oa0-f46.google.com) (209.85.219.46) by server-15.tower-216.messagelabs.com with RC4-SHA encrypted SMTP; 6 Feb 2013 17:40:10 -0000 Received: by mail-oa0-f46.google.com with SMTP id k1so1787834oag.5 for ; Wed, 06 Feb 2013 09:40:08 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type:x-gm-message-state; bh=0ra8t0C4gIPUwhhHUvl5h25T6vlOMxGL1r4G+/3p/XI=; b=FbsEU/nIiBp2WGbo4UGnzptmOqbzQkcHNx/Gu8Q/OsaBJU0FGgZUj2pp6IiC3++IhU tI/1IEcUE13jwkK4Z8kRTcFoMZv6LjBYjQpy6hv1Z8CJWe3yQq0OPKMx1oanBBklk5HM lJm4GiWJSPrkUfajvCbtNHH7Kq1hiRK24vmO5Oasda61Myh1sfZMJ0rgcJ+sxdbffJ2S 24p4SvCrTMiZSC6gPDcD3EagRbSEnWkigY3FZGVPyTfCZTJk416Fp88OqYdj/qpF3Ly3 3NVZI3pb858ZEfnSQLuf9yg/w6fbDf2hKSJtZKvsK8PNnf9zqEzIVURdqDRPDsTnm8qg RVyQ== MIME-Version: 1.0 X-Received: by 10.60.6.105 with SMTP id z9mr9070500oez.52.1360172408522; Wed, 06 Feb 2013 09:40:08 -0800 (PST) Received: by 10.182.40.98 with HTTP; Wed, 6 Feb 2013 09:40:08 -0800 (PST) In-Reply-To: <-5850233638147328292@unknownmsgid> References: <51127586.4080206@ondore.com> <-5850233638147328292@unknownmsgid> Date: Wed, 6 Feb 2013 15:40:08 -0200 Message-ID: From: Carlos Ribas To: Muzaffer Tolga Ozses X-Gm-Message-State: ALoCoQn3FLZ0mx1hdekJ8t/FDQAqsILHy+e1isHb2XHqWKUH+7JOCXeXgaPhdvPjfAdULFSHRS30 Cc: "xen-users@lists.xen.org" , Alexandre Kouznetsov Subject: Re: [Xen-users] How to auto start DomU after reboot of 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="===============2467416324195674790==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============2467416324195674790== Content-Type: multipart/alternative; boundary=e89a8fb202883e48a304d511d1aa --e89a8fb202883e48a304d511d1aa Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Hello, As I thought, there is a simple way to do it. Thanks Alexandre! Muzaffer, we have only to check if xend starts first, if not this will not work. Probably a "sleep" helps. Thank you. Regards, ------------------------------- Carlos Eduardo Ribas 2013/2/6 Muzaffer Tolga Ozses > You could also start them using cron like below: > > @reboot xm create vm.cfg > > Regards > M > > myPhone'dan g=C3=B6nderdim > > 6 =C5=9Eub 2013 tarihinde 17:28 saatinde, Alexandre Kouznetsov > =C5=9Funlar=C4=B1 yazd=C4=B1: > > > Hello. > > > > El 06/02/13 07:18, Carlos Ribas escribi=C3=B3: > >> I followed some tutorials to install Xen in a Debian Squeeze > >> server. One of them [1] says to set up XENDOMAINS_RESTORE to false, > >> because I can have problems with that. So, if my server shuts down or > >> reboots how can I configure my VM to automatically start? > > That option has to do with Xen's feature to save/restore the domains, > instead of shutdown/startup. A close equivalent in baremetal computing > would be suspend/resume. > > > >> Yesterday I did a quick script [2] that worked well, but I am not > >> sure if it is the best way to do it. I would like to know what you do > >> solve this issue. > > Squeeze's Xend provides a very simple way to autostart the domains, > regardless they was saved or shot down. Check /etc/defaults/xendomains > file, it's heavily commented, particularly XENDOMAINS_AUTO section. Note > that you will have to create the directory /etc/xen/auto manually. > > I usually put there symbolic links to config files (that are stored > directly under /etc/xen), instead of the configuration files themselves. > > > > Greetings. > > > > -- > > Alexandre Kouznetsov > > > > > > _______________________________________________ > > 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 > --e89a8fb202883e48a304d511d1aa Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Hello,

=C2=A0 =C2=A0 As I thought, there is a simple way= to do it. Thanks Alexandre!

=C2=A0 =C2=A0 Muzaffe= r, we have only to check if xend starts first, if not this will not work. P= robably a "sleep" helps. Thank you. =C2=A0

Regards,

--------= -----------------------
Carlos Eduardo Ribas



2013/2/6 Muzaffer Tolga Ozses <tolga@ozs= es.net>
You could also start them using cron like below:

@reboot xm create vm.cfg

Regards
M

=C2=A0myPhone'dan g=C3=B6nderdim

6 =C5=9Eub 2013 tarihinde 17:28 saatinde, Alexandre Kouznetsov
<alk@ondore.com> =C5=9Funlar=C4= =B1 yazd=C4=B1:

> Hello.
>
> El 06/02/13 07:18, Carlos Ribas escribi=C3=B3:
>> =C2=A0 =C2=A0 I followed some tutorials to install Xen in a Debian= Squeeze
>> server. One of them [1] says to set up XENDOMAINS_RESTORE to false= ,
>> because I can have problems with that. So, if my server shuts down= or
>> reboots how can I configure my VM to automatically start?
> That option has to do with Xen's feature to save/restore the domai= ns, instead of shutdown/startup. A close equivalent in baremetal computing = would be suspend/resume.
>
>> =C2=A0 =C2=A0 Yesterday I did a quick script [2] that worked well,= but I am not
>> sure if it is the best way to do it. I would like to know what you= do
>> solve this issue.
> Squeeze's Xend provides a very simple way to autostart the domains= , regardless they was saved or shot down. Check /etc/defaults/xendomains fi= le, it's heavily commented, particularly XENDOMAINS_AUTO section. Note = that you will have to create the directory /etc/xen/auto manually.
> I usually put there symbolic links to config files (that are stored di= rectly under /etc/xen), instead of the configuration files themselves.
>
> Greetings.
>
> --
> Alexandre Kouznetsov
>
>
> _______________________________________________
> Xen-users mailing list
> Xen-users@lists.xen.org=
> http://li= sts.xen.org/xen-users

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

--e89a8fb202883e48a304d511d1aa-- --===============2467416324195674790== 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 --===============2467416324195674790==-- From xen-users-bounces@lists.xen.org Wed Feb 06 17:41:22 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 06 Feb 2013 17:41: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 1U38yl-0001eJ-Ex; Wed, 06 Feb 2013 17:40:15 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U38yj-0001eE-N5 for xen-users@lists.xen.org; Wed, 06 Feb 2013 17:40:13 +0000 Received: from [85.158.143.99:20609] by server-1.bemta-4.messagelabs.com id 0B/78-08839-C7592115; Wed, 06 Feb 2013 17:40:12 +0000 X-Env-Sender: carlos@ansp.br X-Msg-Ref: server-15.tower-216.messagelabs.com!1360172408!31118504!1 X-Originating-IP: [209.85.219.46] 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.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 17430 invoked from network); 6 Feb 2013 17:40:10 -0000 Received: from mail-oa0-f46.google.com (HELO mail-oa0-f46.google.com) (209.85.219.46) by server-15.tower-216.messagelabs.com with RC4-SHA encrypted SMTP; 6 Feb 2013 17:40:10 -0000 Received: by mail-oa0-f46.google.com with SMTP id k1so1787834oag.5 for ; Wed, 06 Feb 2013 09:40:08 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type:x-gm-message-state; bh=0ra8t0C4gIPUwhhHUvl5h25T6vlOMxGL1r4G+/3p/XI=; b=FbsEU/nIiBp2WGbo4UGnzptmOqbzQkcHNx/Gu8Q/OsaBJU0FGgZUj2pp6IiC3++IhU tI/1IEcUE13jwkK4Z8kRTcFoMZv6LjBYjQpy6hv1Z8CJWe3yQq0OPKMx1oanBBklk5HM lJm4GiWJSPrkUfajvCbtNHH7Kq1hiRK24vmO5Oasda61Myh1sfZMJ0rgcJ+sxdbffJ2S 24p4SvCrTMiZSC6gPDcD3EagRbSEnWkigY3FZGVPyTfCZTJk416Fp88OqYdj/qpF3Ly3 3NVZI3pb858ZEfnSQLuf9yg/w6fbDf2hKSJtZKvsK8PNnf9zqEzIVURdqDRPDsTnm8qg RVyQ== MIME-Version: 1.0 X-Received: by 10.60.6.105 with SMTP id z9mr9070500oez.52.1360172408522; Wed, 06 Feb 2013 09:40:08 -0800 (PST) Received: by 10.182.40.98 with HTTP; Wed, 6 Feb 2013 09:40:08 -0800 (PST) In-Reply-To: <-5850233638147328292@unknownmsgid> References: <51127586.4080206@ondore.com> <-5850233638147328292@unknownmsgid> Date: Wed, 6 Feb 2013 15:40:08 -0200 Message-ID: From: Carlos Ribas To: Muzaffer Tolga Ozses X-Gm-Message-State: ALoCoQn3FLZ0mx1hdekJ8t/FDQAqsILHy+e1isHb2XHqWKUH+7JOCXeXgaPhdvPjfAdULFSHRS30 Cc: "xen-users@lists.xen.org" , Alexandre Kouznetsov Subject: Re: [Xen-users] How to auto start DomU after reboot of 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="===============2467416324195674790==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============2467416324195674790== Content-Type: multipart/alternative; boundary=e89a8fb202883e48a304d511d1aa --e89a8fb202883e48a304d511d1aa Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Hello, As I thought, there is a simple way to do it. Thanks Alexandre! Muzaffer, we have only to check if xend starts first, if not this will not work. Probably a "sleep" helps. Thank you. Regards, ------------------------------- Carlos Eduardo Ribas 2013/2/6 Muzaffer Tolga Ozses > You could also start them using cron like below: > > @reboot xm create vm.cfg > > Regards > M > > myPhone'dan g=C3=B6nderdim > > 6 =C5=9Eub 2013 tarihinde 17:28 saatinde, Alexandre Kouznetsov > =C5=9Funlar=C4=B1 yazd=C4=B1: > > > Hello. > > > > El 06/02/13 07:18, Carlos Ribas escribi=C3=B3: > >> I followed some tutorials to install Xen in a Debian Squeeze > >> server. One of them [1] says to set up XENDOMAINS_RESTORE to false, > >> because I can have problems with that. So, if my server shuts down or > >> reboots how can I configure my VM to automatically start? > > That option has to do with Xen's feature to save/restore the domains, > instead of shutdown/startup. A close equivalent in baremetal computing > would be suspend/resume. > > > >> Yesterday I did a quick script [2] that worked well, but I am not > >> sure if it is the best way to do it. I would like to know what you do > >> solve this issue. > > Squeeze's Xend provides a very simple way to autostart the domains, > regardless they was saved or shot down. Check /etc/defaults/xendomains > file, it's heavily commented, particularly XENDOMAINS_AUTO section. Note > that you will have to create the directory /etc/xen/auto manually. > > I usually put there symbolic links to config files (that are stored > directly under /etc/xen), instead of the configuration files themselves. > > > > Greetings. > > > > -- > > Alexandre Kouznetsov > > > > > > _______________________________________________ > > 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 > --e89a8fb202883e48a304d511d1aa Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Hello,

=C2=A0 =C2=A0 As I thought, there is a simple way= to do it. Thanks Alexandre!

=C2=A0 =C2=A0 Muzaffe= r, we have only to check if xend starts first, if not this will not work. P= robably a "sleep" helps. Thank you. =C2=A0

Regards,

--------= -----------------------
Carlos Eduardo Ribas



2013/2/6 Muzaffer Tolga Ozses <tolga@ozs= es.net>
You could also start them using cron like below:

@reboot xm create vm.cfg

Regards
M

=C2=A0myPhone'dan g=C3=B6nderdim

6 =C5=9Eub 2013 tarihinde 17:28 saatinde, Alexandre Kouznetsov
<alk@ondore.com> =C5=9Funlar=C4= =B1 yazd=C4=B1:

> Hello.
>
> El 06/02/13 07:18, Carlos Ribas escribi=C3=B3:
>> =C2=A0 =C2=A0 I followed some tutorials to install Xen in a Debian= Squeeze
>> server. One of them [1] says to set up XENDOMAINS_RESTORE to false= ,
>> because I can have problems with that. So, if my server shuts down= or
>> reboots how can I configure my VM to automatically start?
> That option has to do with Xen's feature to save/restore the domai= ns, instead of shutdown/startup. A close equivalent in baremetal computing = would be suspend/resume.
>
>> =C2=A0 =C2=A0 Yesterday I did a quick script [2] that worked well,= but I am not
>> sure if it is the best way to do it. I would like to know what you= do
>> solve this issue.
> Squeeze's Xend provides a very simple way to autostart the domains= , regardless they was saved or shot down. Check /etc/defaults/xendomains fi= le, it's heavily commented, particularly XENDOMAINS_AUTO section. Note = that you will have to create the directory /etc/xen/auto manually.
> I usually put there symbolic links to config files (that are stored di= rectly under /etc/xen), instead of the configuration files themselves.
>
> Greetings.
>
> --
> Alexandre Kouznetsov
>
>
> _______________________________________________
> Xen-users mailing list
> Xen-users@lists.xen.org=
> http://li= sts.xen.org/xen-users

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

--e89a8fb202883e48a304d511d1aa-- --===============2467416324195674790== 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 --===============2467416324195674790==-- From xen-users-bounces@lists.xen.org Wed Feb 06 17:49:49 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 06 Feb 2013 17: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 1U397D-00027A-Sr; Wed, 06 Feb 2013 17:48:59 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U397C-00026v-MK; Wed, 06 Feb 2013 17:48:58 +0000 Received: from [85.158.143.99:15783] by server-1.bemta-4.messagelabs.com id 3B/DF-08839-98792115; Wed, 06 Feb 2013 17:48:57 +0000 X-Env-Sender: eneal@businessgrade.com X-Msg-Ref: server-5.tower-216.messagelabs.com!1360172936!27237889!1 X-Originating-IP: [66.151.104.17] X-SpamReason: No, hits=0.0 required=7.0 tests=UPPERCASE_25_50 X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 12714 invoked from network); 6 Feb 2013 17:48:57 -0000 Received: from smtp1.businessgrade.com (HELO smtp1.businessgrade.com) (66.151.104.17) by server-5.tower-216.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 6 Feb 2013 17:48:57 -0000 Received: from ashslvha1.businessgrade.local (127.0.0.1) by ashslvha1.businessgrade.local (Axigen) with ESMTPSA id 35A2CB; Wed, 6 Feb 2013 12:51:31 -0500 Received: from [70.193.196.187] by businessgrade.com with HTTP; Wed, 6 Feb 2013 12:51:31 -0500 From: Errol Neal Date: Wed, 6 Feb 2013 12:51:31 -0500 X-Mailer: Axigen WebMail To: xen-api Message-ID: <1360173091123022500@businessgrade.com> Importance: Normal MIME-Version: 1.0 Content-Disposition: inline Cc: "xen-users@lists.xensource.com" Subject: [Xen-users] [XCP] recompiling xapi rpm changes version and licensing details. X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: eneal@businessgrade.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 there. I needed to recompile xapi to fix a bug that was resolved regarding vdi-create not setting the sharable flag. I used the sources provided in the source-1.iso from xen.org. Everything is good in this regard, and creating a vdi that has "sharable=true" is possible, but I had a problem that forced me to revert to the older copy of the xapi binary because my XCP box was now being identified as a XenServer box. Here's a screen shot: http://picpaste.com/pics/xapi-Dyfq5vhO.1360171933.jpg The actual problem happened on a real host pool member that I had installed the new RPMs. As I mentioned, I had to revert back to a backup copy of the xapi binary because I could not start any of my VMs on that host. The error from xe was: There are no suitable hosts to start this VM on. The following table provides per-host reasons for why the VM could not be starte d: DCSC-XEN03 : Cannot start here [Not enough free memory] DCSC-XEN01: Cannot start here [Api_errors.Server_error("VM_HOST_INCOMPATIBLE_VERSION", _)] My question is how do I go about modifying the version and platform information for XAPI? My xensource-inventory file looks fine: BUILD_NUMBER='61809c' SOFTWARE_VERSION='1.6.10' DOM0_MEM='752' MANAGEMENT_INTERFACE='xenbr0' INSTALLATION_UUID='718e7db1-cf3d-46ea-bcc9-cee8c456ed4d' COMPANY_NAME_SHORT='xen.org' PLATFORM_NAME='XCP' PLATFORM_VERSION='1.6.10' KERNEL_VERSION='2.6.32.43-0.4.1.xs1.6.10.734.170748xen' BRAND_CONSOLE='a console' COMPANY_NAME='xen.org' XEN_VERSION='4.1.3' PRIMARY_DISK='/dev/disk/by-id/scsi-SATA_QEMU_HARDDISK_QM00001' CONTROL_DOMAIN_UUID='969c742c-9b46-46ca-85d1-7f7eb249d913' MANAGEMENT_ADDRESS_TYPE='IPv4' BACKUP_PARTITION='/dev/disk/by-id/scsi-SATA_QEMU_HARDDISK_QM00001-part2' PRODUCT_VERSION='XCP' INSTALLATION_DATE='2013-02-05 13:50:23.445194' It is almost as if the new xapi binary doesn't care about xensource-inventory? _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Wed Feb 06 17:49:49 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 06 Feb 2013 17: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 1U397D-00027A-Sr; Wed, 06 Feb 2013 17:48:59 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U397C-00026v-MK; Wed, 06 Feb 2013 17:48:58 +0000 Received: from [85.158.143.99:15783] by server-1.bemta-4.messagelabs.com id 3B/DF-08839-98792115; Wed, 06 Feb 2013 17:48:57 +0000 X-Env-Sender: eneal@businessgrade.com X-Msg-Ref: server-5.tower-216.messagelabs.com!1360172936!27237889!1 X-Originating-IP: [66.151.104.17] X-SpamReason: No, hits=0.0 required=7.0 tests=UPPERCASE_25_50 X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 12714 invoked from network); 6 Feb 2013 17:48:57 -0000 Received: from smtp1.businessgrade.com (HELO smtp1.businessgrade.com) (66.151.104.17) by server-5.tower-216.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 6 Feb 2013 17:48:57 -0000 Received: from ashslvha1.businessgrade.local (127.0.0.1) by ashslvha1.businessgrade.local (Axigen) with ESMTPSA id 35A2CB; Wed, 6 Feb 2013 12:51:31 -0500 Received: from [70.193.196.187] by businessgrade.com with HTTP; Wed, 6 Feb 2013 12:51:31 -0500 From: Errol Neal Date: Wed, 6 Feb 2013 12:51:31 -0500 X-Mailer: Axigen WebMail To: xen-api Message-ID: <1360173091123022500@businessgrade.com> Importance: Normal MIME-Version: 1.0 Content-Disposition: inline Cc: "xen-users@lists.xensource.com" Subject: [Xen-users] [XCP] recompiling xapi rpm changes version and licensing details. X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: eneal@businessgrade.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 there. I needed to recompile xapi to fix a bug that was resolved regarding vdi-create not setting the sharable flag. I used the sources provided in the source-1.iso from xen.org. Everything is good in this regard, and creating a vdi that has "sharable=true" is possible, but I had a problem that forced me to revert to the older copy of the xapi binary because my XCP box was now being identified as a XenServer box. Here's a screen shot: http://picpaste.com/pics/xapi-Dyfq5vhO.1360171933.jpg The actual problem happened on a real host pool member that I had installed the new RPMs. As I mentioned, I had to revert back to a backup copy of the xapi binary because I could not start any of my VMs on that host. The error from xe was: There are no suitable hosts to start this VM on. The following table provides per-host reasons for why the VM could not be starte d: DCSC-XEN03 : Cannot start here [Not enough free memory] DCSC-XEN01: Cannot start here [Api_errors.Server_error("VM_HOST_INCOMPATIBLE_VERSION", _)] My question is how do I go about modifying the version and platform information for XAPI? My xensource-inventory file looks fine: BUILD_NUMBER='61809c' SOFTWARE_VERSION='1.6.10' DOM0_MEM='752' MANAGEMENT_INTERFACE='xenbr0' INSTALLATION_UUID='718e7db1-cf3d-46ea-bcc9-cee8c456ed4d' COMPANY_NAME_SHORT='xen.org' PLATFORM_NAME='XCP' PLATFORM_VERSION='1.6.10' KERNEL_VERSION='2.6.32.43-0.4.1.xs1.6.10.734.170748xen' BRAND_CONSOLE='a console' COMPANY_NAME='xen.org' XEN_VERSION='4.1.3' PRIMARY_DISK='/dev/disk/by-id/scsi-SATA_QEMU_HARDDISK_QM00001' CONTROL_DOMAIN_UUID='969c742c-9b46-46ca-85d1-7f7eb249d913' MANAGEMENT_ADDRESS_TYPE='IPv4' BACKUP_PARTITION='/dev/disk/by-id/scsi-SATA_QEMU_HARDDISK_QM00001-part2' PRODUCT_VERSION='XCP' INSTALLATION_DATE='2013-02-05 13:50:23.445194' It is almost as if the new xapi binary doesn't care about xensource-inventory? _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Wed Feb 06 19:19:07 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 06 Feb 2013 19:19: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 1U3AUz-0006NG-Sg; Wed, 06 Feb 2013 19:17:37 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U3AUy-0006N2-Nz; Wed, 06 Feb 2013 19:17:36 +0000 Received: from [85.158.139.211:28947] by server-1.bemta-5.messagelabs.com id 7C/A2-29263-F4CA2115; Wed, 06 Feb 2013 19:17:35 +0000 X-Env-Sender: mike.mcclurg@citrix.com X-Msg-Ref: server-7.tower-206.messagelabs.com!1360178253!20995329!1 X-Originating-IP: [66.165.176.63] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjYuMTY1LjE3Ni42MyA9PiAzMDE5MTM=\n X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 3054 invoked from network); 6 Feb 2013 19:17:34 -0000 Received: from smtp02.citrix.com (HELO SMTP02.CITRIX.COM) (66.165.176.63) by server-7.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 6 Feb 2013 19:17:34 -0000 X-IronPort-AV: E=Sophos;i="4.84,617,1355097600"; d="scan'208";a="6212420" Received: from accessns.citrite.net (HELO FTLPEX01CL01.citrite.net) ([10.9.154.239]) by FTLPIPO02.CITRIX.COM with ESMTP/TLS/AES128-SHA; 06 Feb 2013 19:17:32 +0000 Received: from ukmail1.uk.xensource.com (10.80.16.128) by smtprelay.citrix.com (10.13.107.78) with Microsoft SMTP Server id 14.2.318.1; Wed, 6 Feb 2013 14:17:32 -0500 Received: from [10.80.118.125] by ukmail1.uk.xensource.com with esmtp (Exim 4.69) (envelope-from ) id 1U3AUu-0005YR-5n; Wed, 06 Feb 2013 19:17:32 +0000 Message-ID: <5112AC4B.3020304@citrix.com> Date: Wed, 6 Feb 2013 19:17:31 +0000 From: Mike McClurg User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130106 Thunderbird/17.0.2 MIME-Version: 1.0 To: "eneal@businessgrade.com" References: <1360173091123022500@businessgrade.com> In-Reply-To: <1360173091123022500@businessgrade.com> Cc: "xen-users@lists.xensource.com" , xen-api Subject: Re: [Xen-users] [XCP] recompiling xapi rpm changes version and licensing details. X-BeenThere: xen-users@lists.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 06/02/13 17:51, Errol Neal wrote: > Hi there. I needed to recompile xapi to fix a bug that was resolved regarding vdi-create not setting the sharable flag. I used the sources provided in the source-1.iso from xen.org. Everything is good in this regard, and creating a vdi that has "sharable=true" is possible, but I had a problem that forced me to revert to the older copy of the xapi binary because my XCP box was now being identified as a XenServer box. Hi Errol, Our build system uses environment variables to inject the PLATFORM_NAME and PLATFORM_VERSION into the RPM. (See the Makefile snippet below). Before you do rpmbuild, you should do: export PLATFORM_NAME=XCP export PLATFORM_VERSION=1.6.10 You may also want to export a BUILD_NUMBER, but I don't think that this is used for anything so you can probably ignore it. Mike The interesting bit from Xapi's Makefile: .PHONY: version version: @printf "(* This file is autogenerated. Grep for e17512ce-ba7c-11df-887b-0026b9799147 (random uuid) to see where it comes from. ;o) *) \n \ let git_id = \"$(shell git show-ref --head | grep -E ' HEAD$$' | cut -f 1 -d ' ')\" \n \ let hostname = \"$(shell hostname)\" \n \ let date = \"$(shell date -u +%Y-%m-%d)\" \n \ let product_version = Util_inventory.lookup ~default:\"\" \"PRODUCT_VERSION\" \n \ let product_version_text = Util_inventory.lookup ~default:\"\" \"PRODUCT_VERSION_TEXT\" \n \ let product_version_text_short = Util_inventory.lookup ~default:\"\" \"PRODUCT_VERSION_TEXT_SHORT\" \n \ let platform_name = \"$(PLATFORM_NAME)\" \n \ let platform_version = \"$(PLATFORM_VERSION)\" \n \ let product_brand = Util_inventory.lookup ~default:\"\" \"PRODUCT_BRAND\" \n \ let build_number = Util_inventory.lookup ~default:\"$(BUILD_NUMBER)\" \"BUILD_NUMBER\" \n \ let xapi_version_major = $(shell cut -d. -f1 VERSION) \n \ let xapi_version_minor = $(shell cut -d. -f2 VERSION) \n" \ > ocaml/util/version.ml _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Wed Feb 06 19:19:07 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 06 Feb 2013 19:19: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 1U3AUz-0006NG-Sg; Wed, 06 Feb 2013 19:17:37 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U3AUy-0006N2-Nz; Wed, 06 Feb 2013 19:17:36 +0000 Received: from [85.158.139.211:28947] by server-1.bemta-5.messagelabs.com id 7C/A2-29263-F4CA2115; Wed, 06 Feb 2013 19:17:35 +0000 X-Env-Sender: mike.mcclurg@citrix.com X-Msg-Ref: server-7.tower-206.messagelabs.com!1360178253!20995329!1 X-Originating-IP: [66.165.176.63] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjYuMTY1LjE3Ni42MyA9PiAzMDE5MTM=\n X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 3054 invoked from network); 6 Feb 2013 19:17:34 -0000 Received: from smtp02.citrix.com (HELO SMTP02.CITRIX.COM) (66.165.176.63) by server-7.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 6 Feb 2013 19:17:34 -0000 X-IronPort-AV: E=Sophos;i="4.84,617,1355097600"; d="scan'208";a="6212420" Received: from accessns.citrite.net (HELO FTLPEX01CL01.citrite.net) ([10.9.154.239]) by FTLPIPO02.CITRIX.COM with ESMTP/TLS/AES128-SHA; 06 Feb 2013 19:17:32 +0000 Received: from ukmail1.uk.xensource.com (10.80.16.128) by smtprelay.citrix.com (10.13.107.78) with Microsoft SMTP Server id 14.2.318.1; Wed, 6 Feb 2013 14:17:32 -0500 Received: from [10.80.118.125] by ukmail1.uk.xensource.com with esmtp (Exim 4.69) (envelope-from ) id 1U3AUu-0005YR-5n; Wed, 06 Feb 2013 19:17:32 +0000 Message-ID: <5112AC4B.3020304@citrix.com> Date: Wed, 6 Feb 2013 19:17:31 +0000 From: Mike McClurg User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130106 Thunderbird/17.0.2 MIME-Version: 1.0 To: "eneal@businessgrade.com" References: <1360173091123022500@businessgrade.com> In-Reply-To: <1360173091123022500@businessgrade.com> Cc: "xen-users@lists.xensource.com" , xen-api Subject: Re: [Xen-users] [XCP] recompiling xapi rpm changes version and licensing details. X-BeenThere: xen-users@lists.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 06/02/13 17:51, Errol Neal wrote: > Hi there. I needed to recompile xapi to fix a bug that was resolved regarding vdi-create not setting the sharable flag. I used the sources provided in the source-1.iso from xen.org. Everything is good in this regard, and creating a vdi that has "sharable=true" is possible, but I had a problem that forced me to revert to the older copy of the xapi binary because my XCP box was now being identified as a XenServer box. Hi Errol, Our build system uses environment variables to inject the PLATFORM_NAME and PLATFORM_VERSION into the RPM. (See the Makefile snippet below). Before you do rpmbuild, you should do: export PLATFORM_NAME=XCP export PLATFORM_VERSION=1.6.10 You may also want to export a BUILD_NUMBER, but I don't think that this is used for anything so you can probably ignore it. Mike The interesting bit from Xapi's Makefile: .PHONY: version version: @printf "(* This file is autogenerated. Grep for e17512ce-ba7c-11df-887b-0026b9799147 (random uuid) to see where it comes from. ;o) *) \n \ let git_id = \"$(shell git show-ref --head | grep -E ' HEAD$$' | cut -f 1 -d ' ')\" \n \ let hostname = \"$(shell hostname)\" \n \ let date = \"$(shell date -u +%Y-%m-%d)\" \n \ let product_version = Util_inventory.lookup ~default:\"\" \"PRODUCT_VERSION\" \n \ let product_version_text = Util_inventory.lookup ~default:\"\" \"PRODUCT_VERSION_TEXT\" \n \ let product_version_text_short = Util_inventory.lookup ~default:\"\" \"PRODUCT_VERSION_TEXT_SHORT\" \n \ let platform_name = \"$(PLATFORM_NAME)\" \n \ let platform_version = \"$(PLATFORM_VERSION)\" \n \ let product_brand = Util_inventory.lookup ~default:\"\" \"PRODUCT_BRAND\" \n \ let build_number = Util_inventory.lookup ~default:\"$(BUILD_NUMBER)\" \"BUILD_NUMBER\" \n \ let xapi_version_major = $(shell cut -d. -f1 VERSION) \n \ let xapi_version_minor = $(shell cut -d. -f2 VERSION) \n" \ > ocaml/util/version.ml _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Wed Feb 06 20:16:42 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 06 Feb 2013 20:16: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 1U3BP1-0008IJ-64; Wed, 06 Feb 2013 20:15:31 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U3BOz-0008I6-58; Wed, 06 Feb 2013 20:15:29 +0000 Received: from [193.109.254.147:22476] by server-2.bemta-14.messagelabs.com id 7D/F3-16277-0E9B2115; Wed, 06 Feb 2013 20:15:28 +0000 X-Env-Sender: eneal@businessgrade.com X-Msg-Ref: server-16.tower-27.messagelabs.com!1360181725!8809839!1 X-Originating-IP: [66.151.104.17] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 23087 invoked from network); 6 Feb 2013 20:15:26 -0000 Received: from smtp1.businessgrade.com (HELO smtp1.businessgrade.com) (66.151.104.17) by server-16.tower-27.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 6 Feb 2013 20:15:26 -0000 Received: from ashslvha1.businessgrade.local (127.0.0.1) by ashslvha1.businessgrade.local (Axigen) with ESMTPSA id 23BC7A; Wed, 6 Feb 2013 15:18:00 -0500 Received: from [70.193.196.187] by businessgrade.com with HTTP; Wed, 6 Feb 2013 15:18:00 -0500 From: Errol Neal Date: Wed, 6 Feb 2013 15:18:00 -0500 X-Mailer: Axigen WebMail To: Mike McClurg Message-ID: <1360181880208072500@businessgrade.com> In-Reply-To: <5112AC4B.3020304@citrix.com> References: <1360173091123022500@businessgrade.com> <5112AC4B.3020304@citrix.com> Importance: Normal MIME-Version: 1.0 Content-Disposition: inline Cc: "xen-users@lists.xensource.com" , xen-api Subject: Re: [Xen-users] [XCP] recompiling xapi rpm changes version and licensing details. X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: eneal@businessgrade.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 Wed, 02/06/2013 02:17 PM, Mike McClurg <mike.mcclurg@citrix.com> wrote: > On 06/02/13 17:51, Errol Neal wrote: > > Hi there. I needed to recompile xapi to fix a bug that was resolved regarding vdi-create not setting the sharable flag. I used the sources provided in the source-1.iso from xen.org. Everything is good in this regard, and creating a vdi that has "sharable=true" is possible, but I had a problem that forced me to revert to the older copy of the xapi binary because my XCP box was now being identified as a XenServer box. > > Hi Errol, > > Our build system uses environment variables to inject the PLATFORM_NAME > and PLATFORM_VERSION into the RPM. (See the Makefile snippet below). > Before you do rpmbuild, you should do: > > export PLATFORM_NAME=XCP > export PLATFORM_VERSION=1.6.10 > Jackpot! Thanks a ton! _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Wed Feb 06 20:16:42 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 06 Feb 2013 20:16: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 1U3BP1-0008IJ-64; Wed, 06 Feb 2013 20:15:31 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U3BOz-0008I6-58; Wed, 06 Feb 2013 20:15:29 +0000 Received: from [193.109.254.147:22476] by server-2.bemta-14.messagelabs.com id 7D/F3-16277-0E9B2115; Wed, 06 Feb 2013 20:15:28 +0000 X-Env-Sender: eneal@businessgrade.com X-Msg-Ref: server-16.tower-27.messagelabs.com!1360181725!8809839!1 X-Originating-IP: [66.151.104.17] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 23087 invoked from network); 6 Feb 2013 20:15:26 -0000 Received: from smtp1.businessgrade.com (HELO smtp1.businessgrade.com) (66.151.104.17) by server-16.tower-27.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 6 Feb 2013 20:15:26 -0000 Received: from ashslvha1.businessgrade.local (127.0.0.1) by ashslvha1.businessgrade.local (Axigen) with ESMTPSA id 23BC7A; Wed, 6 Feb 2013 15:18:00 -0500 Received: from [70.193.196.187] by businessgrade.com with HTTP; Wed, 6 Feb 2013 15:18:00 -0500 From: Errol Neal Date: Wed, 6 Feb 2013 15:18:00 -0500 X-Mailer: Axigen WebMail To: Mike McClurg Message-ID: <1360181880208072500@businessgrade.com> In-Reply-To: <5112AC4B.3020304@citrix.com> References: <1360173091123022500@businessgrade.com> <5112AC4B.3020304@citrix.com> Importance: Normal MIME-Version: 1.0 Content-Disposition: inline Cc: "xen-users@lists.xensource.com" , xen-api Subject: Re: [Xen-users] [XCP] recompiling xapi rpm changes version and licensing details. X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: eneal@businessgrade.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 Wed, 02/06/2013 02:17 PM, Mike McClurg <mike.mcclurg@citrix.com> wrote: > On 06/02/13 17:51, Errol Neal wrote: > > Hi there. I needed to recompile xapi to fix a bug that was resolved regarding vdi-create not setting the sharable flag. I used the sources provided in the source-1.iso from xen.org. Everything is good in this regard, and creating a vdi that has "sharable=true" is possible, but I had a problem that forced me to revert to the older copy of the xapi binary because my XCP box was now being identified as a XenServer box. > > Hi Errol, > > Our build system uses environment variables to inject the PLATFORM_NAME > and PLATFORM_VERSION into the RPM. (See the Makefile snippet below). > Before you do rpmbuild, you should do: > > export PLATFORM_NAME=XCP > export PLATFORM_VERSION=1.6.10 > Jackpot! Thanks a ton! _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Wed Feb 06 20:42:53 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 06 Feb 2013 20:42: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 1U3Bod-0000xs-QQ; Wed, 06 Feb 2013 20:41:59 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U3Bob-0000xN-IW for xen-users@lists.xen.org; Wed, 06 Feb 2013 20:41:57 +0000 Received: from [85.158.143.35:13107] by server-2.bemta-4.messagelabs.com id 91/6B-01597-410C2115; Wed, 06 Feb 2013 20:41:56 +0000 X-Env-Sender: matthias.kannenberg@googlemail.com X-Msg-Ref: server-4.tower-21.messagelabs.com!1360183310!5631695!1 X-Originating-IP: [74.125.82.43] X-SpamReason: No, hits=0.5 required=7.0 tests=RCVD_BY_IP,UPPERCASE_50_75 X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 5706 invoked from network); 6 Feb 2013 20:41:50 -0000 Received: from mail-wg0-f43.google.com (HELO mail-wg0-f43.google.com) (74.125.82.43) by server-4.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 6 Feb 2013 20:41:50 -0000 Received: by mail-wg0-f43.google.com with SMTP id e12so1455171wge.22 for ; Wed, 06 Feb 2013 12:41:49 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=20120113; h=x-received:mime-version:from:date:message-id:subject:to :content-type; bh=CZNImtyBkVh+crbYbkGuIF2OqAKwqvVOtsRR/rho3gg=; b=MtNZDcI3DKF64EeUP4jCFKmQewiZlu4hqzeUWscXXK5d2mEejCta9pXyneRQZtSaDQ UZ/S5EMM4+Pax+9w0U9gEEnBp7IoNVYDwQf88NzZAWasBfPOVzZt5CIe8K7M3OBw22e7 ++tGH51Bdob/QSBqRRMdcp6NPd0QspTQnC56W0i4F00iunKlwoadiAygqFL36JfuWyzH EiIIHX226O8uMIRSYXLif2GwYMqi9fK1ifFu9Vbtgn1NICufMaR9RVeqvFcqoz9dgVP4 aXm9vHCewq2Yya/FP+ElxMIr6pmGKLNa2F/KBPbvoIVrJMh7Pt8A69vogYV5e8CEiKSs FCeA== X-Received: by 10.194.78.207 with SMTP id d15mr52288036wjx.52.1360183309706; Wed, 06 Feb 2013 12:41:49 -0800 (PST) MIME-Version: 1.0 Received: by 10.194.80.68 with HTTP; Wed, 6 Feb 2013 12:41:28 -0800 (PST) From: Matthias Date: Wed, 6 Feb 2013 21:41:28 +0100 Message-ID: To: xen-users@lists.xen.org Subject: [Xen-users] CPU stall in RCU system X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: 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 everybody, I came across an error which causes my dom0 to freeze: INFO: rcu_preempt self-detected stall on CPU { 0} (t=60005 jiffies) INFO: rcu_preempt detected stalls on CPUs/tasks: { 0} (detected by 1, t=60007 jiffies) sending NMI to all CPUs: xen: vector 0x2 is not implemented This happens randomly 2-5 minutes after booting the dom0 and might be triggered through network usage (e.g. using ssh ). The strange thing is that in vanilla kernel 3.7.4, this happens with one config, but not with an other one (which has slightly more modules due to trying to fix an other problem). I pasted a diff at the end of this post. When using vanilla kernel 3.7.6, this happens also when using the previously working config. I'm using latest xen-unstable with a AMD Phenom 1090T (I know that at some point xen frequency scaling had problems with x15 family AMD CPUs, so I'm saying this here.. Any ideas what might causes this? diff .config_error .config_working 62,63c62,63 < CONFIG_KERNEL_GZIP=y < # CONFIG_KERNEL_BZIP2 is not set --- > # CONFIG_KERNEL_GZIP is not set > CONFIG_KERNEL_BZIP2=y 343c343 < CONFIG_KVM_GUEST=y --- > # CONFIG_KVM_GUEST is not set 390c390 < CONFIG_X86_MCE_INTEL=y --- > # CONFIG_X86_MCE_INTEL is not set 394d393 < CONFIG_X86_THERMAL_VECTOR=y 444,445c443 < CONFIG_X86_CHECK_BIOS_CORRUPTION=y < # CONFIG_X86_BOOTPARAM_MEMORY_CORRUPTION_CHECK is not set --- > # CONFIG_X86_CHECK_BIOS_CORRUPTION is not set 518c516 < CONFIG_ACPI_CUSTOM_METHOD=y --- > # CONFIG_ACPI_CUSTOM_METHOD is not set 548,549c546,547 < CONFIG_X86_PCC_CPUFREQ=y < CONFIG_X86_ACPI_CPUFREQ=y --- > CONFIG_X86_PCC_CPUFREQ=m > CONFIG_X86_ACPI_CPUFREQ=m 551,553c549,551 < CONFIG_X86_POWERNOW_K8=y < CONFIG_X86_SPEEDSTEP_CENTRINO=y < CONFIG_X86_P4_CLOCKMOD=y --- > CONFIG_X86_POWERNOW_K8=m > # CONFIG_X86_SPEEDSTEP_CENTRINO is not set > # CONFIG_X86_P4_CLOCKMOD is not set 558c556 < CONFIG_X86_SPEEDSTEP_LIB=y --- > # CONFIG_X86_SPEEDSTEP_LIB is not set 827c825 < CONFIG_NETFILTER_XT_TARGET_HMARK=m --- > # CONFIG_NETFILTER_XT_TARGET_HMARK is not set 1360d1357 < # CONFIG_NET_9P_VIRTIO is not set 1573c1570 < CONFIG_PARPORT_SERIAL=m --- > # CONFIG_PARPORT_SERIAL is not set 1645d1641 < CONFIG_VIRTIO_BLK=y 1734c1730 < CONFIG_SCSI_ENCLOSURE=m --- > # CONFIG_SCSI_ENCLOSURE is not set 1801d1796 < CONFIG_HYPERV_STORAGE=y 1843d1837 < CONFIG_SCSI_VIRTIO=y 1978c1972 < CONFIG_DM_LOG_USERSPACE=y --- > # CONFIG_DM_LOG_USERSPACE is not set 2032c2026 < CONFIG_NET_TEAM_MODE_BROADCAST=m --- > # CONFIG_NET_TEAM_MODE_BROADCAST is not set 2035c2029 < CONFIG_NET_TEAM_MODE_LOADBALANCE=m --- > # CONFIG_NET_TEAM_MODE_LOADBALANCE is not set 2038c2032 < CONFIG_VXLAN=y --- > CONFIG_VXLAN=m 2049d2042 < # CONFIG_VIRTIO_NET is not set 2310c2303 < CONFIG_MARVELL_PHY=y --- > CONFIG_MARVELL_PHY=m 2597d2589 < # CONFIG_HYPERV_NET is not set 3013d3004 < # CONFIG_VIRTIO_CONSOLE is not set 3026d3016 < # CONFIG_HW_RANDOM_VIRTIO is not set 3286d3275 < # CONFIG_CHARGER_ISP1704 is not set 3825,3826c3814 < CONFIG_DRM_VMWGFX=y < # CONFIG_DRM_VMWGFX_FBCON is not set --- > # CONFIG_DRM_VMWGFX is not set 4177c4165 < CONFIG_UHID=y --- > # CONFIG_UHID is not set 4240d4227 < # CONFIG_HID_HYPERV_MOUSE is not set 4310c4297 < CONFIG_USB_HCD_BCMA=m --- > # CONFIG_USB_HCD_BCMA is not set 4312,4314c4299 < CONFIG_USB_CHIPIDEA=y < # CONFIG_USB_CHIPIDEA_HOST is not set < # CONFIG_USB_CHIPIDEA_DEBUG is not set --- > # CONFIG_USB_CHIPIDEA is not set 4457,4458c4442,4443 < CONFIG_OMAP_USB2=y < CONFIG_USB_ISP1301=y --- > # CONFIG_OMAP_USB2 is not set > # CONFIG_USB_ISP1301 is not set 4469d4453 < CONFIG_USB_OTG_UTILS=y 4607d4590 < CONFIG_EDAC_I7CORE=m 4611d4593 < CONFIG_EDAC_SBRIDGE=m 4712c4694 < CONFIG_UIO=y --- > CONFIG_UIO=m 4721d4702 < CONFIG_VIRTIO=y 4726,4729c4707,4708 < CONFIG_VIRTIO_PCI=y < # CONFIG_VIRTIO_BALLOON is not set < CONFIG_VIRTIO_MMIO=y < CONFIG_VIRTIO_MMIO_CMDLINE_DEVICES=y --- > # CONFIG_VIRTIO_PCI is not set > # CONFIG_VIRTIO_MMIO is not set 4734,4735c4713 < CONFIG_HYPERV=y < CONFIG_HYPERV_UTILS=y --- > # CONFIG_HYPERV is not set 4983c4961 < CONFIG_DELL_RBU=y --- > CONFIG_DELL_RBU=m 4986c4964 < CONFIG_DMI_SYSFS=y --- > CONFIG_DMI_SYSFS=m 4989,4995c4967 < CONFIG_GOOGLE_FIRMWARE=y < < # < # Google Firmware Drivers < # < CONFIG_GOOGLE_SMI=y < CONFIG_GOOGLE_MEMCONSOLE=y --- > # CONFIG_GOOGLE_FIRMWARE is not set 5649c5621 < CONFIG_KVM_INTEL=y --- > # CONFIG_KVM_INTEL is not set 5653c5625 < CONFIG_TCM_VHOST=m --- > # CONFIG_TCM_VHOST is not set 5720c5692 < CONFIG_DDR=y --- > # CONFIG_DDR is not set _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Wed Feb 06 20:42:53 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 06 Feb 2013 20:42: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 1U3Bod-0000xs-QQ; Wed, 06 Feb 2013 20:41:59 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U3Bob-0000xN-IW for xen-users@lists.xen.org; Wed, 06 Feb 2013 20:41:57 +0000 Received: from [85.158.143.35:13107] by server-2.bemta-4.messagelabs.com id 91/6B-01597-410C2115; Wed, 06 Feb 2013 20:41:56 +0000 X-Env-Sender: matthias.kannenberg@googlemail.com X-Msg-Ref: server-4.tower-21.messagelabs.com!1360183310!5631695!1 X-Originating-IP: [74.125.82.43] X-SpamReason: No, hits=0.5 required=7.0 tests=RCVD_BY_IP,UPPERCASE_50_75 X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 5706 invoked from network); 6 Feb 2013 20:41:50 -0000 Received: from mail-wg0-f43.google.com (HELO mail-wg0-f43.google.com) (74.125.82.43) by server-4.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 6 Feb 2013 20:41:50 -0000 Received: by mail-wg0-f43.google.com with SMTP id e12so1455171wge.22 for ; Wed, 06 Feb 2013 12:41:49 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=20120113; h=x-received:mime-version:from:date:message-id:subject:to :content-type; bh=CZNImtyBkVh+crbYbkGuIF2OqAKwqvVOtsRR/rho3gg=; b=MtNZDcI3DKF64EeUP4jCFKmQewiZlu4hqzeUWscXXK5d2mEejCta9pXyneRQZtSaDQ UZ/S5EMM4+Pax+9w0U9gEEnBp7IoNVYDwQf88NzZAWasBfPOVzZt5CIe8K7M3OBw22e7 ++tGH51Bdob/QSBqRRMdcp6NPd0QspTQnC56W0i4F00iunKlwoadiAygqFL36JfuWyzH EiIIHX226O8uMIRSYXLif2GwYMqi9fK1ifFu9Vbtgn1NICufMaR9RVeqvFcqoz9dgVP4 aXm9vHCewq2Yya/FP+ElxMIr6pmGKLNa2F/KBPbvoIVrJMh7Pt8A69vogYV5e8CEiKSs FCeA== X-Received: by 10.194.78.207 with SMTP id d15mr52288036wjx.52.1360183309706; Wed, 06 Feb 2013 12:41:49 -0800 (PST) MIME-Version: 1.0 Received: by 10.194.80.68 with HTTP; Wed, 6 Feb 2013 12:41:28 -0800 (PST) From: Matthias Date: Wed, 6 Feb 2013 21:41:28 +0100 Message-ID: To: xen-users@lists.xen.org Subject: [Xen-users] CPU stall in RCU system X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: 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 everybody, I came across an error which causes my dom0 to freeze: INFO: rcu_preempt self-detected stall on CPU { 0} (t=60005 jiffies) INFO: rcu_preempt detected stalls on CPUs/tasks: { 0} (detected by 1, t=60007 jiffies) sending NMI to all CPUs: xen: vector 0x2 is not implemented This happens randomly 2-5 minutes after booting the dom0 and might be triggered through network usage (e.g. using ssh ). The strange thing is that in vanilla kernel 3.7.4, this happens with one config, but not with an other one (which has slightly more modules due to trying to fix an other problem). I pasted a diff at the end of this post. When using vanilla kernel 3.7.6, this happens also when using the previously working config. I'm using latest xen-unstable with a AMD Phenom 1090T (I know that at some point xen frequency scaling had problems with x15 family AMD CPUs, so I'm saying this here.. Any ideas what might causes this? diff .config_error .config_working 62,63c62,63 < CONFIG_KERNEL_GZIP=y < # CONFIG_KERNEL_BZIP2 is not set --- > # CONFIG_KERNEL_GZIP is not set > CONFIG_KERNEL_BZIP2=y 343c343 < CONFIG_KVM_GUEST=y --- > # CONFIG_KVM_GUEST is not set 390c390 < CONFIG_X86_MCE_INTEL=y --- > # CONFIG_X86_MCE_INTEL is not set 394d393 < CONFIG_X86_THERMAL_VECTOR=y 444,445c443 < CONFIG_X86_CHECK_BIOS_CORRUPTION=y < # CONFIG_X86_BOOTPARAM_MEMORY_CORRUPTION_CHECK is not set --- > # CONFIG_X86_CHECK_BIOS_CORRUPTION is not set 518c516 < CONFIG_ACPI_CUSTOM_METHOD=y --- > # CONFIG_ACPI_CUSTOM_METHOD is not set 548,549c546,547 < CONFIG_X86_PCC_CPUFREQ=y < CONFIG_X86_ACPI_CPUFREQ=y --- > CONFIG_X86_PCC_CPUFREQ=m > CONFIG_X86_ACPI_CPUFREQ=m 551,553c549,551 < CONFIG_X86_POWERNOW_K8=y < CONFIG_X86_SPEEDSTEP_CENTRINO=y < CONFIG_X86_P4_CLOCKMOD=y --- > CONFIG_X86_POWERNOW_K8=m > # CONFIG_X86_SPEEDSTEP_CENTRINO is not set > # CONFIG_X86_P4_CLOCKMOD is not set 558c556 < CONFIG_X86_SPEEDSTEP_LIB=y --- > # CONFIG_X86_SPEEDSTEP_LIB is not set 827c825 < CONFIG_NETFILTER_XT_TARGET_HMARK=m --- > # CONFIG_NETFILTER_XT_TARGET_HMARK is not set 1360d1357 < # CONFIG_NET_9P_VIRTIO is not set 1573c1570 < CONFIG_PARPORT_SERIAL=m --- > # CONFIG_PARPORT_SERIAL is not set 1645d1641 < CONFIG_VIRTIO_BLK=y 1734c1730 < CONFIG_SCSI_ENCLOSURE=m --- > # CONFIG_SCSI_ENCLOSURE is not set 1801d1796 < CONFIG_HYPERV_STORAGE=y 1843d1837 < CONFIG_SCSI_VIRTIO=y 1978c1972 < CONFIG_DM_LOG_USERSPACE=y --- > # CONFIG_DM_LOG_USERSPACE is not set 2032c2026 < CONFIG_NET_TEAM_MODE_BROADCAST=m --- > # CONFIG_NET_TEAM_MODE_BROADCAST is not set 2035c2029 < CONFIG_NET_TEAM_MODE_LOADBALANCE=m --- > # CONFIG_NET_TEAM_MODE_LOADBALANCE is not set 2038c2032 < CONFIG_VXLAN=y --- > CONFIG_VXLAN=m 2049d2042 < # CONFIG_VIRTIO_NET is not set 2310c2303 < CONFIG_MARVELL_PHY=y --- > CONFIG_MARVELL_PHY=m 2597d2589 < # CONFIG_HYPERV_NET is not set 3013d3004 < # CONFIG_VIRTIO_CONSOLE is not set 3026d3016 < # CONFIG_HW_RANDOM_VIRTIO is not set 3286d3275 < # CONFIG_CHARGER_ISP1704 is not set 3825,3826c3814 < CONFIG_DRM_VMWGFX=y < # CONFIG_DRM_VMWGFX_FBCON is not set --- > # CONFIG_DRM_VMWGFX is not set 4177c4165 < CONFIG_UHID=y --- > # CONFIG_UHID is not set 4240d4227 < # CONFIG_HID_HYPERV_MOUSE is not set 4310c4297 < CONFIG_USB_HCD_BCMA=m --- > # CONFIG_USB_HCD_BCMA is not set 4312,4314c4299 < CONFIG_USB_CHIPIDEA=y < # CONFIG_USB_CHIPIDEA_HOST is not set < # CONFIG_USB_CHIPIDEA_DEBUG is not set --- > # CONFIG_USB_CHIPIDEA is not set 4457,4458c4442,4443 < CONFIG_OMAP_USB2=y < CONFIG_USB_ISP1301=y --- > # CONFIG_OMAP_USB2 is not set > # CONFIG_USB_ISP1301 is not set 4469d4453 < CONFIG_USB_OTG_UTILS=y 4607d4590 < CONFIG_EDAC_I7CORE=m 4611d4593 < CONFIG_EDAC_SBRIDGE=m 4712c4694 < CONFIG_UIO=y --- > CONFIG_UIO=m 4721d4702 < CONFIG_VIRTIO=y 4726,4729c4707,4708 < CONFIG_VIRTIO_PCI=y < # CONFIG_VIRTIO_BALLOON is not set < CONFIG_VIRTIO_MMIO=y < CONFIG_VIRTIO_MMIO_CMDLINE_DEVICES=y --- > # CONFIG_VIRTIO_PCI is not set > # CONFIG_VIRTIO_MMIO is not set 4734,4735c4713 < CONFIG_HYPERV=y < CONFIG_HYPERV_UTILS=y --- > # CONFIG_HYPERV is not set 4983c4961 < CONFIG_DELL_RBU=y --- > CONFIG_DELL_RBU=m 4986c4964 < CONFIG_DMI_SYSFS=y --- > CONFIG_DMI_SYSFS=m 4989,4995c4967 < CONFIG_GOOGLE_FIRMWARE=y < < # < # Google Firmware Drivers < # < CONFIG_GOOGLE_SMI=y < CONFIG_GOOGLE_MEMCONSOLE=y --- > # CONFIG_GOOGLE_FIRMWARE is not set 5649c5621 < CONFIG_KVM_INTEL=y --- > # CONFIG_KVM_INTEL is not set 5653c5625 < CONFIG_TCM_VHOST=m --- > # CONFIG_TCM_VHOST is not set 5720c5692 < CONFIG_DDR=y --- > # CONFIG_DDR is not set _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Wed Feb 06 20:46:13 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 06 Feb 2013 20:46: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 1U3Brn-0001Ba-1Y; Wed, 06 Feb 2013 20:45:15 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U3Brk-0001BP-RC for xen-users@lists.xen.org; Wed, 06 Feb 2013 20:45:13 +0000 Received: from [85.158.138.51:44652] by server-11.bemta-3.messagelabs.com id FE/A9-10249-3D0C2115; Wed, 06 Feb 2013 20:45:07 +0000 X-Env-Sender: Nick.Couchman@seakr.com X-Msg-Ref: server-13.tower-174.messagelabs.com!1360183502!12589775!1 X-Originating-IP: [64.2.143.10] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 8195 invoked from network); 6 Feb 2013 20:45:05 -0000 Received: from mx1.seakr.com (HELO mx1.seakr.com) (64.2.143.10) by server-13.tower-174.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 6 Feb 2013 20:45:05 -0000 Received: from mx-inside.seakr.com ([192.168.100.31]) by mx1.seakr.com (8.14.3/8.14.3/Debian-9.4) with ESMTP id r16KhoVQ004203 for ; Wed, 6 Feb 2013 13:43:52 -0700 Received: from (mx-inside.seakr.com [192.168.100.31]) by mail-scanner1.it.seakr.com with smtp id 1fb6_01af_11aacf40_709e_11e2_bfb2_00137252735f; Wed, 06 Feb 2013 13:45:00 -0700 Received: from collaborate.seakr.com (collaborate.seakr.com [192.168.100.28]) by mx-inside.seakr.com (Postfix) with ESMTP id C4CDA44D9B for ; Wed, 6 Feb 2013 13:44:57 -0700 (MST) Received: from seakr-engineering-MTA by collaborate.seakr.com with Novell_GroupWise; Wed, 06 Feb 2013 13:44:57 -0700 Message-Id: <51125E5702000099000F2BF5@collaborate.seakr.com> X-Mailer: Novell GroupWise Internet Agent 8.0.3 Date: Wed, 06 Feb 2013 13:44:55 -0700 From: "Nick Couchman" To: "tech mailinglists" , "xen-users" Mime-Version: 1.0 Content-Disposition: inline X-NAIMIME-Disclaimer: 1 X-NAIMIME-Modified: 1 Subject: Re: [Xen-users] PV or HVM guest for OpenBuildServices Host (OpenSUSE based) X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: 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 would go with PV - in fact, I use a PV guest for an OBS host that I have here at my location. I only use HVM for systems that absolutely will not boot PV (Windows, mainly). -Nick >>> On 2013/02/06 at 06:54, tech mailinglists wrote: > Hello all, > > I don't know if it is a silly question but I am really unsure. I informed > myself about the OpenBuildService project which was initialized by OpenSUSE. > > Now I am really interested in setting up an OpenBuildService VM where I can > package some programs and so on for example own software and software I > wan't to use on a few systems which have for example newer versions not in > there offical repository actually. I think that OpenBuildService gives a > more or less universal environment and secure build environment. > > I thought about which guest type I should use. I am not that familiar with > for example compiler optimization algorithms and so I asked my self the > question would it be better to build up an PV or an HVM OpenSUSE DomU. What > would be better? Does it matter if it is a PV or HVM guest for compiler > optimazations and so on? > > Would be great when someone could give me an answer. > > Best Regards -------- This e-mail may contain confidential and privileged material for the sole use of the intended recipient. If this email is not intended for you, or you are not responsible for the delivery of this message to the intended recipient, please note that this message may contain SEAKR Engineering (SEAKR) Privileged/Proprietary Information. In such a case, you are strictly prohibited from downloading, photocopying, distributing or otherwise using this message, its contents or attachments in any way. If you have received this message in error, please notify us immediately by replying to this e-mail and delete the message from your mailbox. Information contained in this message that does not relate to the business of SEAKR is neither endorsed by nor attributable to SEAKR. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Wed Feb 06 20:46:13 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 06 Feb 2013 20:46: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 1U3Brn-0001Ba-1Y; Wed, 06 Feb 2013 20:45:15 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U3Brk-0001BP-RC for xen-users@lists.xen.org; Wed, 06 Feb 2013 20:45:13 +0000 Received: from [85.158.138.51:44652] by server-11.bemta-3.messagelabs.com id FE/A9-10249-3D0C2115; Wed, 06 Feb 2013 20:45:07 +0000 X-Env-Sender: Nick.Couchman@seakr.com X-Msg-Ref: server-13.tower-174.messagelabs.com!1360183502!12589775!1 X-Originating-IP: [64.2.143.10] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 8195 invoked from network); 6 Feb 2013 20:45:05 -0000 Received: from mx1.seakr.com (HELO mx1.seakr.com) (64.2.143.10) by server-13.tower-174.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 6 Feb 2013 20:45:05 -0000 Received: from mx-inside.seakr.com ([192.168.100.31]) by mx1.seakr.com (8.14.3/8.14.3/Debian-9.4) with ESMTP id r16KhoVQ004203 for ; Wed, 6 Feb 2013 13:43:52 -0700 Received: from (mx-inside.seakr.com [192.168.100.31]) by mail-scanner1.it.seakr.com with smtp id 1fb6_01af_11aacf40_709e_11e2_bfb2_00137252735f; Wed, 06 Feb 2013 13:45:00 -0700 Received: from collaborate.seakr.com (collaborate.seakr.com [192.168.100.28]) by mx-inside.seakr.com (Postfix) with ESMTP id C4CDA44D9B for ; Wed, 6 Feb 2013 13:44:57 -0700 (MST) Received: from seakr-engineering-MTA by collaborate.seakr.com with Novell_GroupWise; Wed, 06 Feb 2013 13:44:57 -0700 Message-Id: <51125E5702000099000F2BF5@collaborate.seakr.com> X-Mailer: Novell GroupWise Internet Agent 8.0.3 Date: Wed, 06 Feb 2013 13:44:55 -0700 From: "Nick Couchman" To: "tech mailinglists" , "xen-users" Mime-Version: 1.0 Content-Disposition: inline X-NAIMIME-Disclaimer: 1 X-NAIMIME-Modified: 1 Subject: Re: [Xen-users] PV or HVM guest for OpenBuildServices Host (OpenSUSE based) X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: 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 would go with PV - in fact, I use a PV guest for an OBS host that I have here at my location. I only use HVM for systems that absolutely will not boot PV (Windows, mainly). -Nick >>> On 2013/02/06 at 06:54, tech mailinglists wrote: > Hello all, > > I don't know if it is a silly question but I am really unsure. I informed > myself about the OpenBuildService project which was initialized by OpenSUSE. > > Now I am really interested in setting up an OpenBuildService VM where I can > package some programs and so on for example own software and software I > wan't to use on a few systems which have for example newer versions not in > there offical repository actually. I think that OpenBuildService gives a > more or less universal environment and secure build environment. > > I thought about which guest type I should use. I am not that familiar with > for example compiler optimization algorithms and so I asked my self the > question would it be better to build up an PV or an HVM OpenSUSE DomU. What > would be better? Does it matter if it is a PV or HVM guest for compiler > optimazations and so on? > > Would be great when someone could give me an answer. > > Best Regards -------- This e-mail may contain confidential and privileged material for the sole use of the intended recipient. If this email is not intended for you, or you are not responsible for the delivery of this message to the intended recipient, please note that this message may contain SEAKR Engineering (SEAKR) Privileged/Proprietary Information. In such a case, you are strictly prohibited from downloading, photocopying, distributing or otherwise using this message, its contents or attachments in any way. If you have received this message in error, please notify us immediately by replying to this e-mail and delete the message from your mailbox. Information contained in this message that does not relate to the business of SEAKR is neither endorsed by nor attributable to SEAKR. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Wed Feb 06 20:57:14 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 06 Feb 2013 20:57: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 1U3C2e-0001zU-1S; Wed, 06 Feb 2013 20:56:28 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U3C2c-0001zO-Ez for xen-users@lists.xen.org; Wed, 06 Feb 2013 20:56:26 +0000 Received: from [85.158.138.51:22333] by server-13.bemta-3.messagelabs.com id 3F/A4-20653-973C2115; Wed, 06 Feb 2013 20:56:25 +0000 X-Env-Sender: matthias.kannenberg@googlemail.com X-Msg-Ref: server-5.tower-174.messagelabs.com!1360184184!29132472!1 X-Originating-IP: [209.85.212.179] X-SpamReason: No, hits=0.3 required=7.0 tests=RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 26326 invoked from network); 6 Feb 2013 20:56:24 -0000 Received: from unknown (HELO mail-wi0-f179.google.com) (209.85.212.179) by server-5.tower-174.messagelabs.com with RC4-SHA encrypted SMTP; 6 Feb 2013 20:56:24 -0000 Received: by mail-wi0-f179.google.com with SMTP id ez12so2077974wid.12 for ; Wed, 06 Feb 2013 12:54:26 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=20120113; h=x-received:mime-version:from:date:message-id:subject:to :content-type; bh=O+/eFPs4irSVBq+7BT4lXxVCkEhybbGEnEPPasRNuuU=; b=g0xCUdvkY2pg4NXg16cFr36jTT28RT/9oi6GZaQ3kHaOzkXTK2qBvzfJ2+jWiS6+0c abH+Pvy1zzFlZpb3MgFmM7EE7fbFwcOoxAglooFjuiMfLWv+SbIyF88Cee03GN/S8ZXL YDItJRxlTlXP3s1tzjJWvZFydVRLoWzUUs62GEQu5/LcawouDEpedELuibbjqCEZBI1u 809rUWDOs9AJ5HMDdCMDkMBklAxREvCQXE7CKcWDoFMWG7K6w1xyXuv/zDxRkPryue/n nM6JwEhlqy1+whxhwBp1Lhf3wZOGAmcM93rmdmwjqEO89ACB3+BjTywomJBCAg2xCc40 ZEDg== X-Received: by 10.180.24.9 with SMTP id q9mr7524482wif.14.1360184066085; Wed, 06 Feb 2013 12:54:26 -0800 (PST) MIME-Version: 1.0 Received: by 10.194.80.68 with HTTP; Wed, 6 Feb 2013 12:54:05 -0800 (PST) From: Matthias Date: Wed, 6 Feb 2013 21:54:05 +0100 Message-ID: To: xen-users@lists.xen.org Subject: [Xen-users] xl / kernel can't reset pci device (USB2 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 Hi, lately i have switched from xm and a patched opensuse kernel to xl and a vanilla kernel. Now, when trying to pass my USB2 (OHCI) Host Controller to a domU, when starting and stopping, i get the following error: libxl: error: libxl_pci.c:989:libxl__device_pci_reset: The kernel doesn't support reset from sysfs for PCI device 0000:00:12.0 The pci device is: 00:12.0 USB controller: Advanced Micro Devices [AMD] nee ATI SB7x0/SB8x0/SB9x0 USB OHCI0 Controller Since I am new to xl and this never happend before: Is this a problem or causes this issues? Or can i safely ignore it? _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Wed Feb 06 20:57:14 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 06 Feb 2013 20:57: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 1U3C2e-0001zU-1S; Wed, 06 Feb 2013 20:56:28 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U3C2c-0001zO-Ez for xen-users@lists.xen.org; Wed, 06 Feb 2013 20:56:26 +0000 Received: from [85.158.138.51:22333] by server-13.bemta-3.messagelabs.com id 3F/A4-20653-973C2115; Wed, 06 Feb 2013 20:56:25 +0000 X-Env-Sender: matthias.kannenberg@googlemail.com X-Msg-Ref: server-5.tower-174.messagelabs.com!1360184184!29132472!1 X-Originating-IP: [209.85.212.179] X-SpamReason: No, hits=0.3 required=7.0 tests=RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 26326 invoked from network); 6 Feb 2013 20:56:24 -0000 Received: from unknown (HELO mail-wi0-f179.google.com) (209.85.212.179) by server-5.tower-174.messagelabs.com with RC4-SHA encrypted SMTP; 6 Feb 2013 20:56:24 -0000 Received: by mail-wi0-f179.google.com with SMTP id ez12so2077974wid.12 for ; Wed, 06 Feb 2013 12:54:26 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=20120113; h=x-received:mime-version:from:date:message-id:subject:to :content-type; bh=O+/eFPs4irSVBq+7BT4lXxVCkEhybbGEnEPPasRNuuU=; b=g0xCUdvkY2pg4NXg16cFr36jTT28RT/9oi6GZaQ3kHaOzkXTK2qBvzfJ2+jWiS6+0c abH+Pvy1zzFlZpb3MgFmM7EE7fbFwcOoxAglooFjuiMfLWv+SbIyF88Cee03GN/S8ZXL YDItJRxlTlXP3s1tzjJWvZFydVRLoWzUUs62GEQu5/LcawouDEpedELuibbjqCEZBI1u 809rUWDOs9AJ5HMDdCMDkMBklAxREvCQXE7CKcWDoFMWG7K6w1xyXuv/zDxRkPryue/n nM6JwEhlqy1+whxhwBp1Lhf3wZOGAmcM93rmdmwjqEO89ACB3+BjTywomJBCAg2xCc40 ZEDg== X-Received: by 10.180.24.9 with SMTP id q9mr7524482wif.14.1360184066085; Wed, 06 Feb 2013 12:54:26 -0800 (PST) MIME-Version: 1.0 Received: by 10.194.80.68 with HTTP; Wed, 6 Feb 2013 12:54:05 -0800 (PST) From: Matthias Date: Wed, 6 Feb 2013 21:54:05 +0100 Message-ID: To: xen-users@lists.xen.org Subject: [Xen-users] xl / kernel can't reset pci device (USB2 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 Hi, lately i have switched from xm and a patched opensuse kernel to xl and a vanilla kernel. Now, when trying to pass my USB2 (OHCI) Host Controller to a domU, when starting and stopping, i get the following error: libxl: error: libxl_pci.c:989:libxl__device_pci_reset: The kernel doesn't support reset from sysfs for PCI device 0000:00:12.0 The pci device is: 00:12.0 USB controller: Advanced Micro Devices [AMD] nee ATI SB7x0/SB8x0/SB9x0 USB OHCI0 Controller Since I am new to xl and this never happend before: Is this a problem or causes this issues? Or can i safely ignore it? _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Wed Feb 06 22:32:31 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 06 Feb 2013 22: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 1U3DWX-0005HC-Sx; Wed, 06 Feb 2013 22:31:25 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U3DWW-0005Gu-Tp for xen-users@lists.xen.org; Wed, 06 Feb 2013 22:31:25 +0000 Received: from [85.158.139.211:26029] by server-2.bemta-5.messagelabs.com id 7E/8B-16911-CB9D2115; Wed, 06 Feb 2013 22:31:24 +0000 X-Env-Sender: thore@datensumpf.de X-Msg-Ref: server-12.tower-206.messagelabs.com!1360189883!18665348!1 X-Originating-IP: [212.12.52.213] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 5915 invoked from network); 6 Feb 2013 22:31:23 -0000 Received: from mail-2.ramdrive.org (HELO mail-2.ramdrive.org) (212.12.52.213) by server-12.tower-206.messagelabs.com with SMTP; 6 Feb 2013 22:31:23 -0000 Received: from localhost (localhost [127.0.0.1]) by mail-2.ramdrive.org (Postfix) with ESMTP id 0400F783DD50 for ; Wed, 6 Feb 2013 22:40:43 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at mail-2.ramdrive.org Received: from mail-2.ramdrive.org ([127.0.0.1]) by localhost (mail-2.ramdrive.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id r4C58iB0S53D for ; Wed, 6 Feb 2013 22:40:36 +0000 (UTC) Received: from [192.168.178.33] (g224083194.adsl.alicedsl.de [92.224.83.194]) by mail-2.ramdrive.org (Postfix) with ESMTPSA id 62B4E783DBAA for ; Wed, 6 Feb 2013 22:40:36 +0000 (UTC) Message-ID: <5112D9B2.4040504@datensumpf.de> Date: Wed, 06 Feb 2013 23:31:14 +0100 From: Thore User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130106 Thunderbird/17.0.2 MIME-Version: 1.0 To: xen-users@lists.xen.org References: <01FF60612CDD7CEA56FE205A4B6AD6@thehobsons.co.uk> In-Reply-To: <01FF60612CDD7CEA56FE205A4B6AD6@thehobsons.co.uk> Subject: Re: [Xen-users] Using Ipv4 and IPv6 Subnet X-BeenThere: xen-users@lists.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 Am 06.02.2013 17:42, schrieb Simon Hobson: > Thore wrote: >> I have a xenbr0 > Then there is nothing Xen-specific to set up > >> Some time before I set this in my /etc/network/interfaces >> #iface eth0 inet6 static >> # address 2a01:4f8:140:1:2 >> # netmask 64 >> # gateway fe80::1 > fe80 addresses are self-assigned link-local, and you probably don't have an fe80::1 on the network. You need to set both a valid address and gateway. 2a01:4f8:140:1:2 is not a valid IPv6 address - is there a typo there (too few groups, is there a :: missing) ? > The gateway might be configured by Route Advertisement broadcasts, or it might be configured manually - what does your hoster tell you to use ? > >> At the moment it is inaktive. >> I have 3 IPv4 Adresses, no Subnet. > Actually, you will have a subnet, but most likely you have 3 IPs from a larger subnet shared with other hosting clients. > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xen.org > http://lists.xen.org/xen-users Hetzner says: ## /etc/network/interfaces example Hetzner root server # Loopback-Adapter auto lo iface lo inet loopback # LAN interface auto eth0 iface eth0 inet static # Main IP address of the server address 192.168.0.250 # Netmask 255.255.255.255 (/32) independent from the # real subnet size (e.g. /27) netmask 255.255.255.255 # explicit host route to the gateway gateway 192.168.0.1 pointopoint 192.168.0.1 iface eth0 inet6 static # Main IPv6 Address of the server address 2a01:4f8:61:20e1::2 netmask 64 gateway fe80::1 when I change it to my adresses, it would work, but how can I set it up for the domU's? I think I had to enable the script in the xend config. but what else I had to change? Add the address in the .cfg file? I read that xen is able to use both. But can I only use the xenbr0 or need I another bridge and another interface for the domU? regards Thore _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Wed Feb 06 22:32:31 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 06 Feb 2013 22: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 1U3DWX-0005HC-Sx; Wed, 06 Feb 2013 22:31:25 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U3DWW-0005Gu-Tp for xen-users@lists.xen.org; Wed, 06 Feb 2013 22:31:25 +0000 Received: from [85.158.139.211:26029] by server-2.bemta-5.messagelabs.com id 7E/8B-16911-CB9D2115; Wed, 06 Feb 2013 22:31:24 +0000 X-Env-Sender: thore@datensumpf.de X-Msg-Ref: server-12.tower-206.messagelabs.com!1360189883!18665348!1 X-Originating-IP: [212.12.52.213] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 5915 invoked from network); 6 Feb 2013 22:31:23 -0000 Received: from mail-2.ramdrive.org (HELO mail-2.ramdrive.org) (212.12.52.213) by server-12.tower-206.messagelabs.com with SMTP; 6 Feb 2013 22:31:23 -0000 Received: from localhost (localhost [127.0.0.1]) by mail-2.ramdrive.org (Postfix) with ESMTP id 0400F783DD50 for ; Wed, 6 Feb 2013 22:40:43 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at mail-2.ramdrive.org Received: from mail-2.ramdrive.org ([127.0.0.1]) by localhost (mail-2.ramdrive.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id r4C58iB0S53D for ; Wed, 6 Feb 2013 22:40:36 +0000 (UTC) Received: from [192.168.178.33] (g224083194.adsl.alicedsl.de [92.224.83.194]) by mail-2.ramdrive.org (Postfix) with ESMTPSA id 62B4E783DBAA for ; Wed, 6 Feb 2013 22:40:36 +0000 (UTC) Message-ID: <5112D9B2.4040504@datensumpf.de> Date: Wed, 06 Feb 2013 23:31:14 +0100 From: Thore User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130106 Thunderbird/17.0.2 MIME-Version: 1.0 To: xen-users@lists.xen.org References: <01FF60612CDD7CEA56FE205A4B6AD6@thehobsons.co.uk> In-Reply-To: <01FF60612CDD7CEA56FE205A4B6AD6@thehobsons.co.uk> Subject: Re: [Xen-users] Using Ipv4 and IPv6 Subnet X-BeenThere: xen-users@lists.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 Am 06.02.2013 17:42, schrieb Simon Hobson: > Thore wrote: >> I have a xenbr0 > Then there is nothing Xen-specific to set up > >> Some time before I set this in my /etc/network/interfaces >> #iface eth0 inet6 static >> # address 2a01:4f8:140:1:2 >> # netmask 64 >> # gateway fe80::1 > fe80 addresses are self-assigned link-local, and you probably don't have an fe80::1 on the network. You need to set both a valid address and gateway. 2a01:4f8:140:1:2 is not a valid IPv6 address - is there a typo there (too few groups, is there a :: missing) ? > The gateway might be configured by Route Advertisement broadcasts, or it might be configured manually - what does your hoster tell you to use ? > >> At the moment it is inaktive. >> I have 3 IPv4 Adresses, no Subnet. > Actually, you will have a subnet, but most likely you have 3 IPs from a larger subnet shared with other hosting clients. > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xen.org > http://lists.xen.org/xen-users Hetzner says: ## /etc/network/interfaces example Hetzner root server # Loopback-Adapter auto lo iface lo inet loopback # LAN interface auto eth0 iface eth0 inet static # Main IP address of the server address 192.168.0.250 # Netmask 255.255.255.255 (/32) independent from the # real subnet size (e.g. /27) netmask 255.255.255.255 # explicit host route to the gateway gateway 192.168.0.1 pointopoint 192.168.0.1 iface eth0 inet6 static # Main IPv6 Address of the server address 2a01:4f8:61:20e1::2 netmask 64 gateway fe80::1 when I change it to my adresses, it would work, but how can I set it up for the domU's? I think I had to enable the script in the xend config. but what else I had to change? Add the address in the .cfg file? I read that xen is able to use both. But can I only use the xenbr0 or need I another bridge and another interface for the domU? regards Thore _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Thu Feb 07 08:24:32 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 07 Feb 2013 08:24: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 1U3MlA-0000J2-8F; Thu, 07 Feb 2013 08:23:08 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U3Ml8-0000Iu-HY for xen-users@lists.xensource.com; Thu, 07 Feb 2013 08:23:06 +0000 Received: from [85.158.137.99:21847] by server-6.bemta-3.messagelabs.com id EE/21-29959-96463115; Thu, 07 Feb 2013 08:23:05 +0000 X-Env-Sender: hahn@univention.de X-Msg-Ref: server-9.tower-217.messagelabs.com!1360225385!17200052!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.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 26761 invoked from network); 7 Feb 2013 08:23:05 -0000 Received: from mail.univention.de (HELO mail.univention.de) (82.198.197.8) by server-9.tower-217.messagelabs.com with SMTP; 7 Feb 2013 08:23:05 -0000 Received: from localhost (localhost [127.0.0.1]) by slugis.knut.univention.de (Postfix) with ESMTP id CB85E148A990 for ; Thu, 7 Feb 2013 09:23:03 +0100 (CET) Received: from localhost (localhost [127.0.0.1]) by slugis.knut.univention.de (Postfix) with ESMTP id C287A148A991 for ; Thu, 7 Feb 2013 09:23:03 +0100 (CET) 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 eB4Ua2kqFd5c for ; Thu, 7 Feb 2013 09:23:03 +0100 (CET) Received: from stave.localnet (stave.knut.univention.de [192.168.0.191]) by slugis.knut.univention.de (Postfix) with ESMTPSA id 56888148A990 for ; Thu, 7 Feb 2013 09:23:03 +0100 (CET) From: Philipp Hahn Organization: Univention.de To: xen-users@lists.xensource.com Date: Thu, 7 Feb 2013 09:23:03 +0100 User-Agent: KMail/1.13.7 (Linux/3.2.0-4-amd64; KDE/4.8.4; x86_64; ; ) References: <01FF60612CDD7CEA56FE205A4B6AD6@thehobsons.co.uk> <5112D9B2.4040504@datensumpf.de> In-Reply-To: <5112D9B2.4040504@datensumpf.de> MIME-Version: 1.0 Message-Id: <201302070923.03809.hahn@univention.de> Subject: Re: [Xen-users] Using Ipv4 and IPv6 Subnet X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: 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, On Wednesday 06 February 2013 23:31:14 Thore wrote: > when I change it to my adresses, it would work, but how can I set it up > for the domU's? Think one moment what you would do with a real physical network: You have the cable from Hetzner, plug it into a switch, to which you would now connect all your hosts. As all hosts are part of the same broadcast domain, you would configure all hosts with the same gateway, netmask, but different host addresses. No back to virtualization: The cabel is eth0: is has no address on it's own. Your physical switch is now virtual and done by the Linux kernel on dom0 as br0. As the bridge and the dom0 are the same, this is the only difference: you configure the dom0 address on the bridge (and not on some bridge-to-dom0 dummy interface as it was done in one of the first releases of Xen) dom0: > # LAN interface > auto eth0 Change eth0 -> br0 > iface eth0 inet static Change eth0 -> br0 > # Main IP address of the server > address 192.168.0.250 > # Netmask 255.255.255.255 (/32) independent from the > # real subnet size (e.g. /27) > netmask 255.255.255.255 > # explicit host route to the gateway > gateway 192.168.0.1 > pointopoint 192.168.0.1 Add " bridge_ports eth0" Add " bridge_fd 0" is you know the consequences > iface eth0 inet6 static Change eth0 -> br0 > # Main IPv6 Address of the server > address 2a01:4f8:61:20e1::2 > netmask 64 > gateway fe80::1 For the domUs you use the original configuration without the br0->eth0 rename: There you get a virtual cable, where one end is already plugged in the virtual switch (vif${dom}.${iface}) by Xend and the other end is now your domUs interface eth0. > I think I had to enable the script in the xend config. Disable them: The current way is to use the mechanism provided by your Distribution, which for Debian is to edit /etc/network/interfaces. /etc/xen/xend-config.sxp: #(network-script network-bridge) This disabled xend from creating the bridge itself (vif-script vif-bridge) This tells Xend to plugin your domUs into the bridge. > Add the address in the .cfg file? That's more confusing than anything else: the IP address there is only used to setup anti-spoofing rules, the real IP configuration happens inside your domUs, since they receive all broadcast traffic. There you only specify the bridge vif = [ '..., bridge=br0, ...' ] > But can I only use the xenbr0 or need I another bridge and another > interface for the domU? In the past Xen did the xenbridge-dance itself to create one default bridge xenbr0 (later eth0), into which the interface eth0 (later peth0) was plugged in. Sincerely Philipp -- 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/ _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Thu Feb 07 08:24:32 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 07 Feb 2013 08:24: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 1U3MlA-0000J2-8F; Thu, 07 Feb 2013 08:23:08 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U3Ml8-0000Iu-HY for xen-users@lists.xensource.com; Thu, 07 Feb 2013 08:23:06 +0000 Received: from [85.158.137.99:21847] by server-6.bemta-3.messagelabs.com id EE/21-29959-96463115; Thu, 07 Feb 2013 08:23:05 +0000 X-Env-Sender: hahn@univention.de X-Msg-Ref: server-9.tower-217.messagelabs.com!1360225385!17200052!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.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 26761 invoked from network); 7 Feb 2013 08:23:05 -0000 Received: from mail.univention.de (HELO mail.univention.de) (82.198.197.8) by server-9.tower-217.messagelabs.com with SMTP; 7 Feb 2013 08:23:05 -0000 Received: from localhost (localhost [127.0.0.1]) by slugis.knut.univention.de (Postfix) with ESMTP id CB85E148A990 for ; Thu, 7 Feb 2013 09:23:03 +0100 (CET) Received: from localhost (localhost [127.0.0.1]) by slugis.knut.univention.de (Postfix) with ESMTP id C287A148A991 for ; Thu, 7 Feb 2013 09:23:03 +0100 (CET) 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 eB4Ua2kqFd5c for ; Thu, 7 Feb 2013 09:23:03 +0100 (CET) Received: from stave.localnet (stave.knut.univention.de [192.168.0.191]) by slugis.knut.univention.de (Postfix) with ESMTPSA id 56888148A990 for ; Thu, 7 Feb 2013 09:23:03 +0100 (CET) From: Philipp Hahn Organization: Univention.de To: xen-users@lists.xensource.com Date: Thu, 7 Feb 2013 09:23:03 +0100 User-Agent: KMail/1.13.7 (Linux/3.2.0-4-amd64; KDE/4.8.4; x86_64; ; ) References: <01FF60612CDD7CEA56FE205A4B6AD6@thehobsons.co.uk> <5112D9B2.4040504@datensumpf.de> In-Reply-To: <5112D9B2.4040504@datensumpf.de> MIME-Version: 1.0 Message-Id: <201302070923.03809.hahn@univention.de> Subject: Re: [Xen-users] Using Ipv4 and IPv6 Subnet X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: 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, On Wednesday 06 February 2013 23:31:14 Thore wrote: > when I change it to my adresses, it would work, but how can I set it up > for the domU's? Think one moment what you would do with a real physical network: You have the cable from Hetzner, plug it into a switch, to which you would now connect all your hosts. As all hosts are part of the same broadcast domain, you would configure all hosts with the same gateway, netmask, but different host addresses. No back to virtualization: The cabel is eth0: is has no address on it's own. Your physical switch is now virtual and done by the Linux kernel on dom0 as br0. As the bridge and the dom0 are the same, this is the only difference: you configure the dom0 address on the bridge (and not on some bridge-to-dom0 dummy interface as it was done in one of the first releases of Xen) dom0: > # LAN interface > auto eth0 Change eth0 -> br0 > iface eth0 inet static Change eth0 -> br0 > # Main IP address of the server > address 192.168.0.250 > # Netmask 255.255.255.255 (/32) independent from the > # real subnet size (e.g. /27) > netmask 255.255.255.255 > # explicit host route to the gateway > gateway 192.168.0.1 > pointopoint 192.168.0.1 Add " bridge_ports eth0" Add " bridge_fd 0" is you know the consequences > iface eth0 inet6 static Change eth0 -> br0 > # Main IPv6 Address of the server > address 2a01:4f8:61:20e1::2 > netmask 64 > gateway fe80::1 For the domUs you use the original configuration without the br0->eth0 rename: There you get a virtual cable, where one end is already plugged in the virtual switch (vif${dom}.${iface}) by Xend and the other end is now your domUs interface eth0. > I think I had to enable the script in the xend config. Disable them: The current way is to use the mechanism provided by your Distribution, which for Debian is to edit /etc/network/interfaces. /etc/xen/xend-config.sxp: #(network-script network-bridge) This disabled xend from creating the bridge itself (vif-script vif-bridge) This tells Xend to plugin your domUs into the bridge. > Add the address in the .cfg file? That's more confusing than anything else: the IP address there is only used to setup anti-spoofing rules, the real IP configuration happens inside your domUs, since they receive all broadcast traffic. There you only specify the bridge vif = [ '..., bridge=br0, ...' ] > But can I only use the xenbr0 or need I another bridge and another > interface for the domU? In the past Xen did the xenbridge-dance itself to create one default bridge xenbr0 (later eth0), into which the interface eth0 (later peth0) was plugged in. Sincerely Philipp -- 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/ _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Thu Feb 07 09:14:03 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 07 Feb 2013 09:14: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 1U3NXW-0002z1-AH; Thu, 07 Feb 2013 09:13:06 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U3NXV-0002yq-8X for xen-users@lists.xen.org; Thu, 07 Feb 2013 09:13:05 +0000 Received: from [85.158.143.35:14251] by server-1.bemta-4.messagelabs.com id 19/3A-08839-02073115; Thu, 07 Feb 2013 09:13:04 +0000 X-Env-Sender: Ian.Campbell@citrix.com X-Msg-Ref: server-4.tower-21.messagelabs.com!1360228358!5208783!1 X-Originating-IP: [46.33.159.39] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNDYuMzMuMTU5LjM5ID0+IDIxNDQ2\n X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 15760 invoked from network); 7 Feb 2013 09:12:38 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (46.33.159.39) by server-4.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 7 Feb 2013 09:12:38 -0000 X-IronPort-AV: E=Sophos;i="4.84,621,1355097600"; d="scan'208";a="1227082" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 07 Feb 2013 09:12: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.297.1; Thu, 7 Feb 2013 09:12:22 +0000 Message-ID: <1360228341.32479.33.camel@zakaz.uk.xensource.com> From: Ian Campbell To: Matthias Date: Thu, 7 Feb 2013 09:12:21 +0000 In-Reply-To: References: Organization: Citrix Systems, Inc. X-Mailer: Evolution 3.4.4-1 MIME-Version: 1.0 Cc: "xen-users@lists.xen.org" Subject: Re: [Xen-users] xl / kernel can't reset pci device (USB2 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 On Wed, 2013-02-06 at 20:54 +0000, Matthias wrote: > Hi, > > lately i have switched from xm and a patched opensuse kernel to xl and > a vanilla kernel. > > Now, when trying to pass my USB2 (OHCI) Host Controller to a domU, > when starting and stopping, i get the following error: > > libxl: error: libxl_pci.c:989:libxl__device_pci_reset: The kernel > doesn't support reset from sysfs for PCI device 0000:00:12.0 > > The pci device is: > 00:12.0 USB controller: Advanced Micro Devices [AMD] nee ATI > SB7x0/SB8x0/SB9x0 USB OHCI0 Controller > > Since I am new to xl and this never happend before: Is this a problem > or causes this issues? Or can i safely ignore it? It might be a problem when detaching the device and attaching it to a new domain or when rebooting the domain, but it very much depends on the specific hardware, if you aren't seeing any problems then don't worry about it. Note that this isn't a new issue it is just that xl is more verbose about failure to reset a device. Ian. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Thu Feb 07 09:14:03 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 07 Feb 2013 09:14: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 1U3NXW-0002z1-AH; Thu, 07 Feb 2013 09:13:06 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U3NXV-0002yq-8X for xen-users@lists.xen.org; Thu, 07 Feb 2013 09:13:05 +0000 Received: from [85.158.143.35:14251] by server-1.bemta-4.messagelabs.com id 19/3A-08839-02073115; Thu, 07 Feb 2013 09:13:04 +0000 X-Env-Sender: Ian.Campbell@citrix.com X-Msg-Ref: server-4.tower-21.messagelabs.com!1360228358!5208783!1 X-Originating-IP: [46.33.159.39] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNDYuMzMuMTU5LjM5ID0+IDIxNDQ2\n X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 15760 invoked from network); 7 Feb 2013 09:12:38 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (46.33.159.39) by server-4.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 7 Feb 2013 09:12:38 -0000 X-IronPort-AV: E=Sophos;i="4.84,621,1355097600"; d="scan'208";a="1227082" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 07 Feb 2013 09:12: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.297.1; Thu, 7 Feb 2013 09:12:22 +0000 Message-ID: <1360228341.32479.33.camel@zakaz.uk.xensource.com> From: Ian Campbell To: Matthias Date: Thu, 7 Feb 2013 09:12:21 +0000 In-Reply-To: References: Organization: Citrix Systems, Inc. X-Mailer: Evolution 3.4.4-1 MIME-Version: 1.0 Cc: "xen-users@lists.xen.org" Subject: Re: [Xen-users] xl / kernel can't reset pci device (USB2 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 On Wed, 2013-02-06 at 20:54 +0000, Matthias wrote: > Hi, > > lately i have switched from xm and a patched opensuse kernel to xl and > a vanilla kernel. > > Now, when trying to pass my USB2 (OHCI) Host Controller to a domU, > when starting and stopping, i get the following error: > > libxl: error: libxl_pci.c:989:libxl__device_pci_reset: The kernel > doesn't support reset from sysfs for PCI device 0000:00:12.0 > > The pci device is: > 00:12.0 USB controller: Advanced Micro Devices [AMD] nee ATI > SB7x0/SB8x0/SB9x0 USB OHCI0 Controller > > Since I am new to xl and this never happend before: Is this a problem > or causes this issues? Or can i safely ignore it? It might be a problem when detaching the device and attaching it to a new domain or when rebooting the domain, but it very much depends on the specific hardware, if you aren't seeing any problems then don't worry about it. Note that this isn't a new issue it is just that xl is more verbose about failure to reset a device. Ian. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Thu Feb 07 10:34:48 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 07 Feb 2013 10:34: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 1U3OnQ-00077N-Nc; Thu, 07 Feb 2013 10:33:36 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U3OnP-00077I-19 for xen-users@lists.xen.org; Thu, 07 Feb 2013 10:33:35 +0000 Received: from [85.158.143.35:20491] by server-3.bemta-4.messagelabs.com id D2/7B-08920-EF283115; Thu, 07 Feb 2013 10:33:34 +0000 X-Env-Sender: J.Witvliet@mindef.nl X-Msg-Ref: server-15.tower-21.messagelabs.com!1360233212!14434336!1 X-Originating-IP: [217.169.229.21] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogMjE3LjE2OS4yMjkuMjEgPT4gMTE3MzAw\n X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 24511 invoked from network); 7 Feb 2013 10:33:32 -0000 Received: from mx4-out.mindef.nl (HELO mx4-out.mindef.nl) (217.169.229.21) by server-15.tower-21.messagelabs.com with SMTP; 7 Feb 2013 10:33:32 -0000 Received: from somewhere by someone Received: from somewhere by someone Received: from somewhere by someone Received: from somewhere by someone Received: from somewhere by someone From: To: Date: Thu, 7 Feb 2013 11:33:25 +0100 References: <20130206141011.91D071928C9@jmr5021.mindef.local> In-Reply-To: <20130206141011.91D071928C9@jmr5021.mindef.local> Accept-Language: en-US, nl-NL Content-Language: en-US acceptlanguage: en-US, nl-NL MIME-Version: 1.0 Message-Id: <20130207103331.09C3721DD57@mx4-out.mindef.nl> Subject: Re: [Xen-users] PV or HVM guest for OpenBuildServices Host (OpenSUSE based) X-BeenThere: xen-users@lists.xen.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="===============5247961663069600802==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============5247961663069600802== Content-Language: en-US Content-Type: multipart/alternative; boundary="_000_62B7731D46267A49B8D6BBB8FA8542402DE1D7A139VAD4202modnl_" --_000_62B7731D46267A49B8D6BBB8FA8542402DE1D7A139VAD4202modnl_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable From: xen-users-bounces@lists.xen.org [mailto:xen-users-bounces@lists.xen.o= rg] On Behalf Of tech mailinglists Sent: Wednesday, February 06, 2013 2:55 PM To: xen-users Subject: [Xen-users] PV or HVM guest for OpenBuildServices Host (OpenSUSE b= ased) Hello all, I don't know if it is a silly question but I am really unsure. I informed m= yself about the OpenBuildService project which was initialized by OpenSUSE. Now I am really interested in setting up an OpenBuildService VM where I can= package some programs and so on for example own software and software I wa= n't to use on a few systems which have for example newer versions not in th= ere offical repository actually. I think that OpenBuildService gives a more= or less universal environment and secure build environment. I thought about which guest type I should use. I am not that familiar with = for example compiler optimization algorithms and so I asked my self the que= stion would it be better to build up an PV or an HVM OpenSUSE DomU. What wo= uld be better? Does it matter if it is a PV or HVM guest for compiler optim= azations and so on? Would be great when someone could give me an answer. Best Regards Hi, Disregarding the purpose of the machine, HVM comes at a costs. Sometimes it is unavoidable, if the OS (like *bsd) requires it, but otherwi= se: use PV. There are some drivers to lessen the pain, but PV remains almost the fastes= t way for virtualization/isolation. HW ______________________________________________________________________ Dit bericht kan informatie bevatten die niet voor u is bestemd. Indien u ni= et de geadresseerde bent of dit bericht abusievelijk aan u is toegezonden, = wordt u verzocht dat aan de afzender te melden en het bericht te verwijdere= n. De Staat aanvaardt geen aansprakelijkheid voor schade, van welke aard oo= k, die verband houdt met risico's verbonden aan het elektronisch verzenden = van berichten. This message may contain information that is not intended for you. If you a= re not the addressee or if this message was sent to you by mistake, you are= requested to inform the sender and delete the message. The State accepts n= o liability for damage of any kind resulting from the risks inherent in the= electronic transmission of messages. --_000_62B7731D46267A49B8D6BBB8FA8542402DE1D7A139VAD4202modnl_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

 

<= div style=3D'border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0= in 0in'>

From:= xen-users-bounces@lists.xen.org [ma= ilto:xen-users-bounces@lists.xen.org] O= n Behalf Of tech mailinglists
Sent: Wednesday, February 06, 2013 2:55 PM
To: xen-users
Subject: [Xen-users] PV or HVM guest for OpenBuildSe= rvices Host (OpenSUSE based)

 

Hello all,

I don't know if= it is a silly question but I am really unsure. I informed myself about the= OpenBuildService project which was initialized by OpenSUSE.

Now I= am really interested in setting up an OpenBuildService VM where I can pack= age some programs and so on for example own software and software I wan't t= o use on a few systems which have for example newer versions not in there o= ffical repository actually. I think that OpenBuildService gives a more or l= ess universal environment and secure build environment.

I thought = about which guest type I should use. I am not that familiar with for exampl= e compiler optimization algorithms and so I asked my self the question woul= d it be better to build up an PV or an HVM OpenSUSE DomU. What would be bet= ter? Does it matter if it is a PV or HVM guest for compiler optimazations a= nd so on?

Would be great when someone could give me an answer.

Best Regards

 

 <= /o:p>

Hi,

 <= /span>

Disregarding the purpose of the machine,  HVM comes = at a costs.

Sometimes it is unavoidable, if th= e OS (like *bsd) requires it, but otherwise: use PV.

= There are some drivers to lessen the pain, but PV remains almost the= fastest way for virtualization/isolation.

 

HW

&n= bsp;

 

Dit bericht kan informatie bevatten die niet voor u is bestemd. Indien = u niet de geadresseerde bent of dit bericht abusievelijk aan u is toegezond= en, wordt u verzocht dat aan de afzender te melden en het bericht te verwij= deren. De Staat aanvaardt geen aansprakelijkheid voor schade, van welke aar= d ook, die verband houdt met risico's verbonden aan het elektronisch ve= rzenden van berichten.

This message may contain information that is not intended for you. If you a= re not the addressee or if this message was sent to you by mistake, you are= requested to inform the sender and delete the message. The State accepts n= o liability for damage of any kind resulting from the risks inherent in the= electronic transmission of messages.
--_000_62B7731D46267A49B8D6BBB8FA8542402DE1D7A139VAD4202modnl_-- --===============5247961663069600802== 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 --===============5247961663069600802==-- From xen-users-bounces@lists.xen.org Thu Feb 07 10:34:48 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 07 Feb 2013 10:34: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 1U3OnQ-00077N-Nc; Thu, 07 Feb 2013 10:33:36 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U3OnP-00077I-19 for xen-users@lists.xen.org; Thu, 07 Feb 2013 10:33:35 +0000 Received: from [85.158.143.35:20491] by server-3.bemta-4.messagelabs.com id D2/7B-08920-EF283115; Thu, 07 Feb 2013 10:33:34 +0000 X-Env-Sender: J.Witvliet@mindef.nl X-Msg-Ref: server-15.tower-21.messagelabs.com!1360233212!14434336!1 X-Originating-IP: [217.169.229.21] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogMjE3LjE2OS4yMjkuMjEgPT4gMTE3MzAw\n X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 24511 invoked from network); 7 Feb 2013 10:33:32 -0000 Received: from mx4-out.mindef.nl (HELO mx4-out.mindef.nl) (217.169.229.21) by server-15.tower-21.messagelabs.com with SMTP; 7 Feb 2013 10:33:32 -0000 Received: from somewhere by someone Received: from somewhere by someone Received: from somewhere by someone Received: from somewhere by someone Received: from somewhere by someone From: To: Date: Thu, 7 Feb 2013 11:33:25 +0100 References: <20130206141011.91D071928C9@jmr5021.mindef.local> In-Reply-To: <20130206141011.91D071928C9@jmr5021.mindef.local> Accept-Language: en-US, nl-NL Content-Language: en-US acceptlanguage: en-US, nl-NL MIME-Version: 1.0 Message-Id: <20130207103331.09C3721DD57@mx4-out.mindef.nl> Subject: Re: [Xen-users] PV or HVM guest for OpenBuildServices Host (OpenSUSE based) X-BeenThere: xen-users@lists.xen.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="===============5247961663069600802==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============5247961663069600802== Content-Language: en-US Content-Type: multipart/alternative; boundary="_000_62B7731D46267A49B8D6BBB8FA8542402DE1D7A139VAD4202modnl_" --_000_62B7731D46267A49B8D6BBB8FA8542402DE1D7A139VAD4202modnl_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable From: xen-users-bounces@lists.xen.org [mailto:xen-users-bounces@lists.xen.o= rg] On Behalf Of tech mailinglists Sent: Wednesday, February 06, 2013 2:55 PM To: xen-users Subject: [Xen-users] PV or HVM guest for OpenBuildServices Host (OpenSUSE b= ased) Hello all, I don't know if it is a silly question but I am really unsure. I informed m= yself about the OpenBuildService project which was initialized by OpenSUSE. Now I am really interested in setting up an OpenBuildService VM where I can= package some programs and so on for example own software and software I wa= n't to use on a few systems which have for example newer versions not in th= ere offical repository actually. I think that OpenBuildService gives a more= or less universal environment and secure build environment. I thought about which guest type I should use. I am not that familiar with = for example compiler optimization algorithms and so I asked my self the que= stion would it be better to build up an PV or an HVM OpenSUSE DomU. What wo= uld be better? Does it matter if it is a PV or HVM guest for compiler optim= azations and so on? Would be great when someone could give me an answer. Best Regards Hi, Disregarding the purpose of the machine, HVM comes at a costs. Sometimes it is unavoidable, if the OS (like *bsd) requires it, but otherwi= se: use PV. There are some drivers to lessen the pain, but PV remains almost the fastes= t way for virtualization/isolation. HW ______________________________________________________________________ Dit bericht kan informatie bevatten die niet voor u is bestemd. Indien u ni= et de geadresseerde bent of dit bericht abusievelijk aan u is toegezonden, = wordt u verzocht dat aan de afzender te melden en het bericht te verwijdere= n. De Staat aanvaardt geen aansprakelijkheid voor schade, van welke aard oo= k, die verband houdt met risico's verbonden aan het elektronisch verzenden = van berichten. This message may contain information that is not intended for you. If you a= re not the addressee or if this message was sent to you by mistake, you are= requested to inform the sender and delete the message. The State accepts n= o liability for damage of any kind resulting from the risks inherent in the= electronic transmission of messages. --_000_62B7731D46267A49B8D6BBB8FA8542402DE1D7A139VAD4202modnl_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

 

<= div style=3D'border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0= in 0in'>

From:= xen-users-bounces@lists.xen.org [ma= ilto:xen-users-bounces@lists.xen.org] O= n Behalf Of tech mailinglists
Sent: Wednesday, February 06, 2013 2:55 PM
To: xen-users
Subject: [Xen-users] PV or HVM guest for OpenBuildSe= rvices Host (OpenSUSE based)

 

Hello all,

I don't know if= it is a silly question but I am really unsure. I informed myself about the= OpenBuildService project which was initialized by OpenSUSE.

Now I= am really interested in setting up an OpenBuildService VM where I can pack= age some programs and so on for example own software and software I wan't t= o use on a few systems which have for example newer versions not in there o= ffical repository actually. I think that OpenBuildService gives a more or l= ess universal environment and secure build environment.

I thought = about which guest type I should use. I am not that familiar with for exampl= e compiler optimization algorithms and so I asked my self the question woul= d it be better to build up an PV or an HVM OpenSUSE DomU. What would be bet= ter? Does it matter if it is a PV or HVM guest for compiler optimazations a= nd so on?

Would be great when someone could give me an answer.

Best Regards

 

 <= /o:p>

Hi,

 <= /span>

Disregarding the purpose of the machine,  HVM comes = at a costs.

Sometimes it is unavoidable, if th= e OS (like *bsd) requires it, but otherwise: use PV.

= There are some drivers to lessen the pain, but PV remains almost the= fastest way for virtualization/isolation.

 

HW

&n= bsp;

 

Dit bericht kan informatie bevatten die niet voor u is bestemd. Indien = u niet de geadresseerde bent of dit bericht abusievelijk aan u is toegezond= en, wordt u verzocht dat aan de afzender te melden en het bericht te verwij= deren. De Staat aanvaardt geen aansprakelijkheid voor schade, van welke aar= d ook, die verband houdt met risico's verbonden aan het elektronisch ve= rzenden van berichten.

This message may contain information that is not intended for you. If you a= re not the addressee or if this message was sent to you by mistake, you are= requested to inform the sender and delete the message. The State accepts n= o liability for damage of any kind resulting from the risks inherent in the= electronic transmission of messages.
--_000_62B7731D46267A49B8D6BBB8FA8542402DE1D7A139VAD4202modnl_-- --===============5247961663069600802== 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 --===============5247961663069600802==-- From xen-users-bounces@lists.xen.org Thu Feb 07 10:57:39 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 07 Feb 2013 10:57: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 1U3P9m-00083u-9n; Thu, 07 Feb 2013 10: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 1U3P9k-00083V-S0; Thu, 07 Feb 2013 10:56:41 +0000 Received: from [85.158.139.83:50776] by server-15.bemta-5.messagelabs.com id 8F/23-18914-86883115; Thu, 07 Feb 2013 10:56:40 +0000 X-Env-Sender: mailinglists.tech@gmail.com X-Msg-Ref: server-13.tower-182.messagelabs.com!1360234599!30403702!1 X-Originating-IP: [74.125.82.42] 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.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 5107 invoked from network); 7 Feb 2013 10:56:39 -0000 Received: from mail-wg0-f42.google.com (HELO mail-wg0-f42.google.com) (74.125.82.42) by server-13.tower-182.messagelabs.com with RC4-SHA encrypted SMTP; 7 Feb 2013 10:56:39 -0000 Received: by mail-wg0-f42.google.com with SMTP id 12so5839315wgh.3 for ; Thu, 07 Feb 2013 02:56:39 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:date:message-id:subject:from:to :content-type; bh=oa4+QnJfpbv6aOJUSmUPkkzQYvkr1EVbCKJG06Fe51o=; b=Q0j9EGEYPXwWBseWGgaI+qhU9EZRzK1kSErNLJXMm7NlU13D2ePBhhq+uW+V71vuKy 7SbxsRKJkZIa96ESV1LqNiMWas4EkCLo9G1Ja17Ui9tce4okgueCqc+ajkwUFRZauYqu FY3AQfcjiVu/9qOYJ+svYGvvh3VIOcUw59Pm+WrjrqUAnfw8q0fmcYu8e/AgcNCaLGea zr+0LyIoOLjs/34Wc/4N9JKoVsjgtGyFnE51rs9ZC1WVaPg1abBv3e4sTkwMnex7K2hM v2dCv9WwdA9KrNopKk8uybl0TPU3bLcbGjtVuHuFY7HoU4XJTqnIAmbuy0CE1PsXtbRC oRPA== MIME-Version: 1.0 X-Received: by 10.180.99.227 with SMTP id et3mr1784892wib.6.1360234599272; Thu, 07 Feb 2013 02:56:39 -0800 (PST) Received: by 10.227.203.18 with HTTP; Thu, 7 Feb 2013 02:56:39 -0800 (PST) Date: Thu, 7 Feb 2013 11:56:39 +0100 Message-ID: From: tech mailinglists To: xen-users , "xen-devel@lists.xen.org" Subject: [Xen-users] State of Stubdomains on NetBSD X-BeenThere: xen-users@lists.xen.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="===============1693472312857726244==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============1693472312857726244== Content-Type: multipart/alternative; boundary=f46d041826aa19d08b04d5204ccf --f46d041826aa19d08b04d5204ccf Content-Type: text/plain; charset=ISO-8859-1 Hello all, I read in the wiki that stubdomains aren't support on NetBSD. Will subdoms be supported on NetBSD? Is someone working on that topic actually? On the NetBSD Xen mailinglist I got no reply. Hope that someone could help me. Best Regards --f46d041826aa19d08b04d5204ccf Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Hello all,

I read in the wiki = that stubdomains aren't support on NetBSD. Will subdoms be supported on= NetBSD? Is someone working on that topic actually?

On the Net= BSD Xen mailinglist I got no reply. Hope that someone could help me.

Best Regards
--f46d041826aa19d08b04d5204ccf-- --===============1693472312857726244== 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 --===============1693472312857726244==-- From xen-users-bounces@lists.xen.org Thu Feb 07 10:57:39 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 07 Feb 2013 10:57: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 1U3P9m-00083u-9n; Thu, 07 Feb 2013 10: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 1U3P9k-00083V-S0; Thu, 07 Feb 2013 10:56:41 +0000 Received: from [85.158.139.83:50776] by server-15.bemta-5.messagelabs.com id 8F/23-18914-86883115; Thu, 07 Feb 2013 10:56:40 +0000 X-Env-Sender: mailinglists.tech@gmail.com X-Msg-Ref: server-13.tower-182.messagelabs.com!1360234599!30403702!1 X-Originating-IP: [74.125.82.42] 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.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 5107 invoked from network); 7 Feb 2013 10:56:39 -0000 Received: from mail-wg0-f42.google.com (HELO mail-wg0-f42.google.com) (74.125.82.42) by server-13.tower-182.messagelabs.com with RC4-SHA encrypted SMTP; 7 Feb 2013 10:56:39 -0000 Received: by mail-wg0-f42.google.com with SMTP id 12so5839315wgh.3 for ; Thu, 07 Feb 2013 02:56:39 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:date:message-id:subject:from:to :content-type; bh=oa4+QnJfpbv6aOJUSmUPkkzQYvkr1EVbCKJG06Fe51o=; b=Q0j9EGEYPXwWBseWGgaI+qhU9EZRzK1kSErNLJXMm7NlU13D2ePBhhq+uW+V71vuKy 7SbxsRKJkZIa96ESV1LqNiMWas4EkCLo9G1Ja17Ui9tce4okgueCqc+ajkwUFRZauYqu FY3AQfcjiVu/9qOYJ+svYGvvh3VIOcUw59Pm+WrjrqUAnfw8q0fmcYu8e/AgcNCaLGea zr+0LyIoOLjs/34Wc/4N9JKoVsjgtGyFnE51rs9ZC1WVaPg1abBv3e4sTkwMnex7K2hM v2dCv9WwdA9KrNopKk8uybl0TPU3bLcbGjtVuHuFY7HoU4XJTqnIAmbuy0CE1PsXtbRC oRPA== MIME-Version: 1.0 X-Received: by 10.180.99.227 with SMTP id et3mr1784892wib.6.1360234599272; Thu, 07 Feb 2013 02:56:39 -0800 (PST) Received: by 10.227.203.18 with HTTP; Thu, 7 Feb 2013 02:56:39 -0800 (PST) Date: Thu, 7 Feb 2013 11:56:39 +0100 Message-ID: From: tech mailinglists To: xen-users , "xen-devel@lists.xen.org" Subject: [Xen-users] State of Stubdomains on NetBSD X-BeenThere: xen-users@lists.xen.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="===============1693472312857726244==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============1693472312857726244== Content-Type: multipart/alternative; boundary=f46d041826aa19d08b04d5204ccf --f46d041826aa19d08b04d5204ccf Content-Type: text/plain; charset=ISO-8859-1 Hello all, I read in the wiki that stubdomains aren't support on NetBSD. Will subdoms be supported on NetBSD? Is someone working on that topic actually? On the NetBSD Xen mailinglist I got no reply. Hope that someone could help me. Best Regards --f46d041826aa19d08b04d5204ccf Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Hello all,

I read in the wiki = that stubdomains aren't support on NetBSD. Will subdoms be supported on= NetBSD? Is someone working on that topic actually?

On the Net= BSD Xen mailinglist I got no reply. Hope that someone could help me.

Best Regards
--f46d041826aa19d08b04d5204ccf-- --===============1693472312857726244== 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 --===============1693472312857726244==-- From xen-users-bounces@lists.xen.org Thu Feb 07 11:04:50 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 07 Feb 2013 11:04: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 1U3PGy-0000Oe-9M; Thu, 07 Feb 2013 11:04:08 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U3PGw-0000OM-KV; Thu, 07 Feb 2013 11:04:06 +0000 Received: from [85.158.137.99:29176] by server-5.bemta-3.messagelabs.com id 2F/B1-04457-52A83115; Thu, 07 Feb 2013 11:04:05 +0000 X-Env-Sender: samuel.thibault@ens-lyon.org X-Msg-Ref: server-8.tower-217.messagelabs.com!1360235043!14996501!1 X-Originating-IP: [192.134.164.83] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 6980 invoked from network); 7 Feb 2013 11:04:04 -0000 Received: from mail2-relais-roc.national.inria.fr (HELO mail2-relais-roc.national.inria.fr) (192.134.164.83) by server-8.tower-217.messagelabs.com with RC4-SHA encrypted SMTP; 7 Feb 2013 11:04:04 -0000 X-IronPort-AV: E=Sophos;i="4.84,621,1355094000"; d="scan'208";a="1794812" Received: from unknown (HELO type.ipv6) ([193.50.110.166]) by mail2-relais-roc.national.inria.fr with ESMTP/TLS/DHE-RSA-AES128-SHA; 07 Feb 2013 12:03:47 +0100 Received: from samy by type.ipv6 with local (Exim 4.80) (envelope-from ) id 1U3PGd-0002WE-OH; Thu, 07 Feb 2013 12:03:47 +0100 Date: Thu, 7 Feb 2013 12:03:47 +0100 From: Samuel Thibault To: tech mailinglists Message-ID: <20130207110347.GX6193@type.bordeaux.inria.fr> Mail-Followup-To: Samuel Thibault , tech mailinglists , xen-users , "xen-devel@lists.xen.org" References: MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21+34 (58baf7c9f32f) (2010-12-30) Cc: xen-users , "xen-devel@lists.xen.org" Subject: Re: [Xen-users] [Xen-devel] State of Stubdomains on NetBSD X-BeenThere: xen-users@lists.xen.org X-Mailman-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 Hello, tech mailinglists, le Thu 07 Feb 2013 11:56:39 +0100, a =E9crit : > I read in the wiki that stubdomains aren't support on NetBSD. Will subdom= s be > supported on NetBSD? Is someone working on that topic actually? I see no reason why it should be hard to do it, so it should be just a matter of someone with a NetBSD box to just try and fix the few missing bits. Samuel _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Thu Feb 07 11:04:50 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 07 Feb 2013 11:04: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 1U3PGy-0000Oe-9M; Thu, 07 Feb 2013 11:04:08 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U3PGw-0000OM-KV; Thu, 07 Feb 2013 11:04:06 +0000 Received: from [85.158.137.99:29176] by server-5.bemta-3.messagelabs.com id 2F/B1-04457-52A83115; Thu, 07 Feb 2013 11:04:05 +0000 X-Env-Sender: samuel.thibault@ens-lyon.org X-Msg-Ref: server-8.tower-217.messagelabs.com!1360235043!14996501!1 X-Originating-IP: [192.134.164.83] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 6980 invoked from network); 7 Feb 2013 11:04:04 -0000 Received: from mail2-relais-roc.national.inria.fr (HELO mail2-relais-roc.national.inria.fr) (192.134.164.83) by server-8.tower-217.messagelabs.com with RC4-SHA encrypted SMTP; 7 Feb 2013 11:04:04 -0000 X-IronPort-AV: E=Sophos;i="4.84,621,1355094000"; d="scan'208";a="1794812" Received: from unknown (HELO type.ipv6) ([193.50.110.166]) by mail2-relais-roc.national.inria.fr with ESMTP/TLS/DHE-RSA-AES128-SHA; 07 Feb 2013 12:03:47 +0100 Received: from samy by type.ipv6 with local (Exim 4.80) (envelope-from ) id 1U3PGd-0002WE-OH; Thu, 07 Feb 2013 12:03:47 +0100 Date: Thu, 7 Feb 2013 12:03:47 +0100 From: Samuel Thibault To: tech mailinglists Message-ID: <20130207110347.GX6193@type.bordeaux.inria.fr> Mail-Followup-To: Samuel Thibault , tech mailinglists , xen-users , "xen-devel@lists.xen.org" References: MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21+34 (58baf7c9f32f) (2010-12-30) Cc: xen-users , "xen-devel@lists.xen.org" Subject: Re: [Xen-users] [Xen-devel] State of Stubdomains on NetBSD X-BeenThere: xen-users@lists.xen.org X-Mailman-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 Hello, tech mailinglists, le Thu 07 Feb 2013 11:56:39 +0100, a =E9crit : > I read in the wiki that stubdomains aren't support on NetBSD. Will subdom= s be > supported on NetBSD? Is someone working on that topic actually? I see no reason why it should be hard to do it, so it should be just a matter of someone with a NetBSD box to just try and fix the few missing bits. Samuel _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Thu Feb 07 11:05:56 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 07 Feb 2013 11:05: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 1U3PI9-0000Zo-3N; Thu, 07 Feb 2013 11:05:21 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U3PI7-0000ZU-AX; Thu, 07 Feb 2013 11:05:19 +0000 Received: from [85.158.137.99:52228] by server-1.bemta-3.messagelabs.com id 70/BE-08955-96A83115; Thu, 07 Feb 2013 11:05:13 +0000 X-Env-Sender: Ian.Campbell@citrix.com X-Msg-Ref: server-10.tower-217.messagelabs.com!1360235112!19541683!1 X-Originating-IP: [46.33.159.39] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNDYuMzMuMTU5LjM5ID0+IDIxNDQ2\n X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 24762 invoked from network); 7 Feb 2013 11:05:13 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (46.33.159.39) by server-10.tower-217.messagelabs.com with RC4-SHA encrypted SMTP; 7 Feb 2013 11:05:13 -0000 X-IronPort-AV: E=Sophos;i="4.84,621,1355097600"; d="scan'208";a="1232771" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 07 Feb 2013 11:05:13 +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.297.1; Thu, 7 Feb 2013 11:05:12 +0000 Message-ID: <1360235111.32479.59.camel@zakaz.uk.xensource.com> From: Ian Campbell To: tech mailinglists Date: Thu, 7 Feb 2013 11:05:11 +0000 In-Reply-To: References: Organization: Citrix Systems, Inc. X-Mailer: Evolution 3.4.4-1 MIME-Version: 1.0 Cc: xen-users Subject: Re: [Xen-users] State of Stubdomains on NetBSD X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org -devel to bcc. On Thu, 2013-02-07 at 10:56 +0000, tech mailinglists wrote: > I read in the wiki that stubdomains aren't support on NetBSD. Will > subdoms be supported on NetBSD? Is someone working on that topic > actually? I don't follow NetBSD closely but AFAIK while you can't build a stubdom on NetBSD stubdoms images built elsewhere should work. Ian. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Thu Feb 07 11:05:56 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 07 Feb 2013 11:05: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 1U3PI9-0000Zo-3N; Thu, 07 Feb 2013 11:05:21 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U3PI7-0000ZU-AX; Thu, 07 Feb 2013 11:05:19 +0000 Received: from [85.158.137.99:52228] by server-1.bemta-3.messagelabs.com id 70/BE-08955-96A83115; Thu, 07 Feb 2013 11:05:13 +0000 X-Env-Sender: Ian.Campbell@citrix.com X-Msg-Ref: server-10.tower-217.messagelabs.com!1360235112!19541683!1 X-Originating-IP: [46.33.159.39] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNDYuMzMuMTU5LjM5ID0+IDIxNDQ2\n X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 24762 invoked from network); 7 Feb 2013 11:05:13 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (46.33.159.39) by server-10.tower-217.messagelabs.com with RC4-SHA encrypted SMTP; 7 Feb 2013 11:05:13 -0000 X-IronPort-AV: E=Sophos;i="4.84,621,1355097600"; d="scan'208";a="1232771" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 07 Feb 2013 11:05:13 +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.297.1; Thu, 7 Feb 2013 11:05:12 +0000 Message-ID: <1360235111.32479.59.camel@zakaz.uk.xensource.com> From: Ian Campbell To: tech mailinglists Date: Thu, 7 Feb 2013 11:05:11 +0000 In-Reply-To: References: Organization: Citrix Systems, Inc. X-Mailer: Evolution 3.4.4-1 MIME-Version: 1.0 Cc: xen-users Subject: Re: [Xen-users] State of Stubdomains on NetBSD X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org -devel to bcc. On Thu, 2013-02-07 at 10:56 +0000, tech mailinglists wrote: > I read in the wiki that stubdomains aren't support on NetBSD. Will > subdoms be supported on NetBSD? Is someone working on that topic > actually? I don't follow NetBSD closely but AFAIK while you can't build a stubdom on NetBSD stubdoms images built elsewhere should work. Ian. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Thu Feb 07 11:35:32 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 07 Feb 2013 11:35: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 1U3Pkc-000303-Pz; Thu, 07 Feb 2013 11:34:46 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U3Pka-0002zk-Mk for xen-users@lists.xen.org; Thu, 07 Feb 2013 11:34:44 +0000 Received: from [85.158.139.83:16914] by server-7.bemta-5.messagelabs.com id 19/B8-11121-35193115; Thu, 07 Feb 2013 11:34:43 +0000 X-Env-Sender: mailinglists.tech@gmail.com X-Msg-Ref: server-5.tower-182.messagelabs.com!1360236882!28865542!1 X-Originating-IP: [74.125.82.45] 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.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 26580 invoked from network); 7 Feb 2013 11:34:43 -0000 Received: from mail-wg0-f45.google.com (HELO mail-wg0-f45.google.com) (74.125.82.45) by server-5.tower-182.messagelabs.com with RC4-SHA encrypted SMTP; 7 Feb 2013 11:34:43 -0000 Received: by mail-wg0-f45.google.com with SMTP id dq12so1882648wgb.0 for ; Thu, 07 Feb 2013 03:34:42 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=gmq/wHzB+rV9Hm/si76J4E6Hgu2fU4g1CEGBBGONg9g=; b=ae5G2YUqCB0hn5/QK6ux6mR6Qz9w/LXeZSwgsXIE7aPgngQk142yHFNio/E6N+5JWF je3HhiJ36/zu2T/NFjtRG6Ird5VjAtHzKStqXEk1bgUd9jWmStAtfFR4Ap9LsOczIbtu fP6wZCyhrOHRyZpv56Tb/DvunVgnC/6w92jDOW9xa89A/hOEFo2hpYAqL4RdV0USpmkB SNjfmvdal4mbKHi4+9Lxt87JW7PKl7nSVHPXzWeT0zipeqIigp2Cz+JhYxc80WV37BKN 9fR42D4kP3NQWVziagkzVKpqo7ZAvXJsWKgG7w5eOC1KQToJcwz2WJkDJuFB4zrMNV7G swXw== MIME-Version: 1.0 X-Received: by 10.194.216.5 with SMTP id om5mr1973991wjc.27.1360236882839; Thu, 07 Feb 2013 03:34:42 -0800 (PST) Received: by 10.227.203.18 with HTTP; Thu, 7 Feb 2013 03:34:42 -0800 (PST) In-Reply-To: <1360235111.32479.59.camel@zakaz.uk.xensource.com> References: <1360235111.32479.59.camel@zakaz.uk.xensource.com> Date: Thu, 7 Feb 2013 12:34:42 +0100 Message-ID: From: tech mailinglists To: Ian Campbell Cc: xen-users Subject: Re: [Xen-users] State of Stubdomains on NetBSD X-BeenThere: xen-users@lists.xen.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="===============5197134406835944476==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============5197134406835944476== Content-Type: multipart/alternative; boundary=089e01493cce36490b04d520d472 --089e01493cce36490b04d520d472 Content-Type: text/plain; charset=ISO-8859-1 Hello, so I the wiki on the building page for NetBSD the wiki said that stubdoms aren't available on NetBSD. If building is the only reason that really would not be a problem to build the stubdoms on Linux and simply transfer the binary files to the NetBSD system. I only could test it in a nested virtualization environment whether they work but I don't know if this is a real reference. I use stubdoms actually on Linux and I would like to switch to NetBSD for different reasons and I don't want to lose this feature. Best Regards 2013/2/7 Ian Campbell > -devel to bcc. > > On Thu, 2013-02-07 at 10:56 +0000, tech mailinglists wrote: > > > I read in the wiki that stubdomains aren't support on NetBSD. Will > > subdoms be supported on NetBSD? Is someone working on that topic > > actually? > > I don't follow NetBSD closely but AFAIK while you can't build a stubdom > on NetBSD stubdoms images built elsewhere should work. > > Ian. > > --089e01493cce36490b04d520d472 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Hello,

so I the wiki on the buildin= g page for NetBSD the wiki said that stubdoms aren't available on NetBS= D. If building is the only reason that really would not be a problem to bui= ld the stubdoms on Linux and simply transfer the binary files to the NetBSD= system. I only could test it in a nested virtualization environment whethe= r they work but I don't know if this is a real reference.

I use stubdoms actually on Linux and I would like to switch to Ne= tBSD for different reasons and I don't want to lose this feature.
Best Regards


2013/2/7 Ian Campbell <Ian.Campbell@citrix.com>
-devel to bcc.

On Thu, 2013-02-07 at 10:56 +0000, tech mailinglists wrote:

> I read in the wiki that stubdomains aren't support on NetBSD. Will=
> subdoms be supported on NetBSD? Is someone working on that topic
> actually?

I don't follow NetBSD closely but AFAIK while you can't build= a stubdom
on NetBSD stubdoms images built elsewhere should work.

Ian.


--089e01493cce36490b04d520d472-- --===============5197134406835944476== 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 --===============5197134406835944476==-- From xen-users-bounces@lists.xen.org Thu Feb 07 11:35:32 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 07 Feb 2013 11:35: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 1U3Pkc-000303-Pz; Thu, 07 Feb 2013 11:34:46 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U3Pka-0002zk-Mk for xen-users@lists.xen.org; Thu, 07 Feb 2013 11:34:44 +0000 Received: from [85.158.139.83:16914] by server-7.bemta-5.messagelabs.com id 19/B8-11121-35193115; Thu, 07 Feb 2013 11:34:43 +0000 X-Env-Sender: mailinglists.tech@gmail.com X-Msg-Ref: server-5.tower-182.messagelabs.com!1360236882!28865542!1 X-Originating-IP: [74.125.82.45] 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.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 26580 invoked from network); 7 Feb 2013 11:34:43 -0000 Received: from mail-wg0-f45.google.com (HELO mail-wg0-f45.google.com) (74.125.82.45) by server-5.tower-182.messagelabs.com with RC4-SHA encrypted SMTP; 7 Feb 2013 11:34:43 -0000 Received: by mail-wg0-f45.google.com with SMTP id dq12so1882648wgb.0 for ; Thu, 07 Feb 2013 03:34:42 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=gmq/wHzB+rV9Hm/si76J4E6Hgu2fU4g1CEGBBGONg9g=; b=ae5G2YUqCB0hn5/QK6ux6mR6Qz9w/LXeZSwgsXIE7aPgngQk142yHFNio/E6N+5JWF je3HhiJ36/zu2T/NFjtRG6Ird5VjAtHzKStqXEk1bgUd9jWmStAtfFR4Ap9LsOczIbtu fP6wZCyhrOHRyZpv56Tb/DvunVgnC/6w92jDOW9xa89A/hOEFo2hpYAqL4RdV0USpmkB SNjfmvdal4mbKHi4+9Lxt87JW7PKl7nSVHPXzWeT0zipeqIigp2Cz+JhYxc80WV37BKN 9fR42D4kP3NQWVziagkzVKpqo7ZAvXJsWKgG7w5eOC1KQToJcwz2WJkDJuFB4zrMNV7G swXw== MIME-Version: 1.0 X-Received: by 10.194.216.5 with SMTP id om5mr1973991wjc.27.1360236882839; Thu, 07 Feb 2013 03:34:42 -0800 (PST) Received: by 10.227.203.18 with HTTP; Thu, 7 Feb 2013 03:34:42 -0800 (PST) In-Reply-To: <1360235111.32479.59.camel@zakaz.uk.xensource.com> References: <1360235111.32479.59.camel@zakaz.uk.xensource.com> Date: Thu, 7 Feb 2013 12:34:42 +0100 Message-ID: From: tech mailinglists To: Ian Campbell Cc: xen-users Subject: Re: [Xen-users] State of Stubdomains on NetBSD X-BeenThere: xen-users@lists.xen.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="===============5197134406835944476==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============5197134406835944476== Content-Type: multipart/alternative; boundary=089e01493cce36490b04d520d472 --089e01493cce36490b04d520d472 Content-Type: text/plain; charset=ISO-8859-1 Hello, so I the wiki on the building page for NetBSD the wiki said that stubdoms aren't available on NetBSD. If building is the only reason that really would not be a problem to build the stubdoms on Linux and simply transfer the binary files to the NetBSD system. I only could test it in a nested virtualization environment whether they work but I don't know if this is a real reference. I use stubdoms actually on Linux and I would like to switch to NetBSD for different reasons and I don't want to lose this feature. Best Regards 2013/2/7 Ian Campbell > -devel to bcc. > > On Thu, 2013-02-07 at 10:56 +0000, tech mailinglists wrote: > > > I read in the wiki that stubdomains aren't support on NetBSD. Will > > subdoms be supported on NetBSD? Is someone working on that topic > > actually? > > I don't follow NetBSD closely but AFAIK while you can't build a stubdom > on NetBSD stubdoms images built elsewhere should work. > > Ian. > > --089e01493cce36490b04d520d472 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Hello,

so I the wiki on the buildin= g page for NetBSD the wiki said that stubdoms aren't available on NetBS= D. If building is the only reason that really would not be a problem to bui= ld the stubdoms on Linux and simply transfer the binary files to the NetBSD= system. I only could test it in a nested virtualization environment whethe= r they work but I don't know if this is a real reference.

I use stubdoms actually on Linux and I would like to switch to Ne= tBSD for different reasons and I don't want to lose this feature.
Best Regards


2013/2/7 Ian Campbell <Ian.Campbell@citrix.com>
-devel to bcc.

On Thu, 2013-02-07 at 10:56 +0000, tech mailinglists wrote:

> I read in the wiki that stubdomains aren't support on NetBSD. Will=
> subdoms be supported on NetBSD? Is someone working on that topic
> actually?

I don't follow NetBSD closely but AFAIK while you can't build= a stubdom
on NetBSD stubdoms images built elsewhere should work.

Ian.


--089e01493cce36490b04d520d472-- --===============5197134406835944476== 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 --===============5197134406835944476==-- From xen-users-bounces@lists.xen.org Thu Feb 07 11:40:03 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 07 Feb 2013 11:40: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 1U3Pp3-0003MV-Dn; Thu, 07 Feb 2013 11:39:21 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U3Pp1-0003ML-Aq for xen-users@lists.xen.org; Thu, 07 Feb 2013 11:39:19 +0000 Received: from [85.158.138.51:17403] by server-13.bemta-3.messagelabs.com id 31/3B-20653-66293115; Thu, 07 Feb 2013 11:39:18 +0000 X-Env-Sender: mailinglists.tech@gmail.com X-Msg-Ref: server-10.tower-174.messagelabs.com!1360237157!24115113!1 X-Originating-IP: [209.85.212.174] 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.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 24279 invoked from network); 7 Feb 2013 11:39:17 -0000 Received: from mail-wi0-f174.google.com (HELO mail-wi0-f174.google.com) (209.85.212.174) by server-10.tower-174.messagelabs.com with RC4-SHA encrypted SMTP; 7 Feb 2013 11:39:17 -0000 Received: by mail-wi0-f174.google.com with SMTP id hi8so6252256wib.1 for ; Thu, 07 Feb 2013 03:39:17 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=MingL1UqhpqIVhysiJPV1SFO1ODh2U5L8TZLDLYAIMk=; b=zRVbRQ2iLmmaDhMT92IFa10lhemRdnt4PfGZJomBgcE+ABFvar8usEhMdtXdijgmas hV6Y6agjOMRnmaMiKWRGoT1RCpeyO0UDIBdFqBJ3dznq9zQcyn+bPyg96Cx3dRwryciJ KXfK4BtENAcwbbXpCHvKae7kw4Ft/v2gzEDBW7yyjUaMI38ZdIajhTieFrMbHvwf8gCd jtwowtsFE0vvEFRy5T48Xd4ttOkKMHN+HGEttsO9pRMYXJ5tLVT5VHeRjuANILJ7zttB /hl44T33YcXX9WHaQkPXcQ/dMSR2cJR0TJuYjiBMYICAhUHg9Kq72HBVRSTi6cNOYqJA PQXQ== MIME-Version: 1.0 X-Received: by 10.194.109.41 with SMTP id hp9mr1968595wjb.32.1360237157161; Thu, 07 Feb 2013 03:39:17 -0800 (PST) Received: by 10.227.203.18 with HTTP; Thu, 7 Feb 2013 03:39:17 -0800 (PST) In-Reply-To: <20130207103331.09C3721DD57@mx4-out.mindef.nl> References: <20130206141011.91D071928C9@jmr5021.mindef.local> <20130207103331.09C3721DD57@mx4-out.mindef.nl> Date: Thu, 7 Feb 2013 12:39:17 +0100 Message-ID: From: tech mailinglists To: J.Witvliet@mindef.nl Cc: xen-users Subject: Re: [Xen-users] PV or HVM guest for OpenBuildServices Host (OpenSUSE based) X-BeenThere: xen-users@lists.xen.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="===============1719533334388429503==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============1719533334388429503== Content-Type: multipart/alternative; boundary=047d7bf10a769019d304d520e4e5 --047d7bf10a769019d304d520e4e5 Content-Type: text/plain; charset=ISO-8859-1 Paravitualization is very great so I would prefer it but the things I tought was whether there are differences for compilers aspecially for languages like C/C++ in the case of HVM and PV. I think for a managed code codebase it would be unimportant where it get builds. I think that a few tests are needed to find out whether there are differences for build process in HVM mode and PV mode. Best Regards 2013/2/7 > ** ** > > *From:* xen-users-bounces@lists.xen.org [mailto: > xen-users-bounces@lists.xen.org] *On Behalf Of *tech mailinglists > *Sent:* Wednesday, February 06, 2013 2:55 PM > *To:* xen-users > *Subject:* [Xen-users] PV or HVM guest for OpenBuildServices Host > (OpenSUSE based)**** > > ** ** > > Hello all, > > I don't know if it is a silly question but I am really unsure. I informed > myself about the OpenBuildService project which was initialized by OpenSUSE. > **** > > Now I am really interested in setting up an OpenBuildService VM where I > can package some programs and so on for example own software and software I > wan't to use on a few systems which have for example newer versions not in > there offical repository actually. I think that OpenBuildService gives a > more or less universal environment and secure build environment.**** > > I thought about which guest type I should use. I am not that familiar with > for example compiler optimization algorithms and so I asked my self the > question would it be better to build up an PV or an HVM OpenSUSE DomU. What > would be better? Does it matter if it is a PV or HVM guest for compiler > optimazations and so on?**** > > Would be great when someone could give me an answer.**** > > Best Regards**** > > ** ** > > ** ** > > Hi,**** > > ** ** > > Disregarding the purpose of the machine, HVM comes at a costs.**** > > Sometimes it is unavoidable, if the OS (like *bsd) requires it, but > otherwise: use PV.**** > > There are some drivers to lessen the pain, but PV remains almost the > fastest way for virtualization/isolation.**** > > ** ** > > HW**** > > ** ** > > ** ** > ------------------------------ > Dit bericht kan informatie bevatten die niet voor u is bestemd. Indien u > niet de geadresseerde bent of dit bericht abusievelijk aan u is > toegezonden, wordt u verzocht dat aan de afzender te melden en het bericht > te verwijderen. De Staat aanvaardt geen aansprakelijkheid voor schade, van > welke aard ook, die verband houdt met risico's verbonden aan het > elektronisch verzenden van berichten. > > This message may contain information that is not intended for you. If you > are not the addressee or if this message was sent to you by mistake, you > are requested to inform the sender and delete the message. The State > accepts no liability for damage of any kind resulting from the risks > inherent in the electronic transmission of messages. > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xen.org > http://lists.xen.org/xen-users > --047d7bf10a769019d304d520e4e5 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Paravitualization is very great so I would prefer it = but the things I tought was whether there are differences for compilers asp= ecially for languages like C/C++ in the case of HVM and PV. I think for a m= anaged code codebase it would be unimportant where it get builds.

I think that a few tests are needed to find out whether there are= differences for build process in HVM mode and PV mode.

Best Regards=


201= 3/2/7 <J.Witvliet@mindef.nl>

=A0

From: xen-users-bo= unces@lists.xen.org [mailto:xen-users-bounces@lists.xen.org] On Behalf Of tech mailinglists
Sent: Wednesday, February 06= , 2013 2:55 PM
To: xen-us= ers
Subject: [Xen-users] = PV or HVM guest for OpenBuildServices Host (OpenSUSE based)

=A0

Hello all,

I don't know if it is a silly question but I am really unsure. I in= formed myself about the OpenBuildService project which was initialized by O= penSUSE.

= Now I am really interested in setting up an OpenBuildService VM where I can= package some programs and so on for example own software and software I wa= n't to use on a few systems which have for example newer versions not i= n there offical repository actually. I think that OpenBuildService gives a = more or less universal environment and secure build environment.<= /u>

I thought about= which guest type I should use. I am not that familiar with for example com= piler optimization algorithms and so I asked my self the question would it = be better to build up an PV or an HVM OpenSUSE DomU. What would be better? = Does it matter if it is a PV or HVM guest for compiler optimazations and so= on?

Would be great = when someone could give me an answer.

=

= Best Regards

= =A0

=A0<= /font>

Hi,

=A0

Disregarding the purpose of the machine, =A0HVM comes at a = costs.

Sometimes it is unavoidable, if the OS (like *bsd) requires= it, but otherwise: use PV.

There are some drivers to lessen the pain, but PV remains a= lmost the fastest way for virtualization/isolation.

=A0

<= font color=3D"#1f497d" face=3D"Calibri">HW

=A0

<= font color=3D"#1f497d" face=3D"Calibri">= =A0

Dit bericht kan informatie bevatten die niet voor u is bestemd. Indien = u niet de geadresseerde bent of dit bericht abusievelijk aan u is toegezond= en, wordt u verzocht dat aan de afzender te melden en het bericht te verwij= deren. De Staat aanvaardt geen aansprakelijkheid voor schade, van welke aar= d ook, die verband houdt met risico's verbonden aan het elektronisch ve= rzenden van berichten.

This message may contain information that is not intended for you. If you a= re not the addressee or if this message was sent to you by mistake, you are= requested to inform the sender and delete the message. The State accepts n= o liability for damage of any kind resulting from the risks inherent in the= electronic transmission of messages.

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

--047d7bf10a769019d304d520e4e5-- --===============1719533334388429503== 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 --===============1719533334388429503==-- From xen-users-bounces@lists.xen.org Thu Feb 07 11:40:03 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 07 Feb 2013 11:40: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 1U3Pp3-0003MV-Dn; Thu, 07 Feb 2013 11:39:21 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U3Pp1-0003ML-Aq for xen-users@lists.xen.org; Thu, 07 Feb 2013 11:39:19 +0000 Received: from [85.158.138.51:17403] by server-13.bemta-3.messagelabs.com id 31/3B-20653-66293115; Thu, 07 Feb 2013 11:39:18 +0000 X-Env-Sender: mailinglists.tech@gmail.com X-Msg-Ref: server-10.tower-174.messagelabs.com!1360237157!24115113!1 X-Originating-IP: [209.85.212.174] 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.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 24279 invoked from network); 7 Feb 2013 11:39:17 -0000 Received: from mail-wi0-f174.google.com (HELO mail-wi0-f174.google.com) (209.85.212.174) by server-10.tower-174.messagelabs.com with RC4-SHA encrypted SMTP; 7 Feb 2013 11:39:17 -0000 Received: by mail-wi0-f174.google.com with SMTP id hi8so6252256wib.1 for ; Thu, 07 Feb 2013 03:39:17 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=MingL1UqhpqIVhysiJPV1SFO1ODh2U5L8TZLDLYAIMk=; b=zRVbRQ2iLmmaDhMT92IFa10lhemRdnt4PfGZJomBgcE+ABFvar8usEhMdtXdijgmas hV6Y6agjOMRnmaMiKWRGoT1RCpeyO0UDIBdFqBJ3dznq9zQcyn+bPyg96Cx3dRwryciJ KXfK4BtENAcwbbXpCHvKae7kw4Ft/v2gzEDBW7yyjUaMI38ZdIajhTieFrMbHvwf8gCd jtwowtsFE0vvEFRy5T48Xd4ttOkKMHN+HGEttsO9pRMYXJ5tLVT5VHeRjuANILJ7zttB /hl44T33YcXX9WHaQkPXcQ/dMSR2cJR0TJuYjiBMYICAhUHg9Kq72HBVRSTi6cNOYqJA PQXQ== MIME-Version: 1.0 X-Received: by 10.194.109.41 with SMTP id hp9mr1968595wjb.32.1360237157161; Thu, 07 Feb 2013 03:39:17 -0800 (PST) Received: by 10.227.203.18 with HTTP; Thu, 7 Feb 2013 03:39:17 -0800 (PST) In-Reply-To: <20130207103331.09C3721DD57@mx4-out.mindef.nl> References: <20130206141011.91D071928C9@jmr5021.mindef.local> <20130207103331.09C3721DD57@mx4-out.mindef.nl> Date: Thu, 7 Feb 2013 12:39:17 +0100 Message-ID: From: tech mailinglists To: J.Witvliet@mindef.nl Cc: xen-users Subject: Re: [Xen-users] PV or HVM guest for OpenBuildServices Host (OpenSUSE based) X-BeenThere: xen-users@lists.xen.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="===============1719533334388429503==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============1719533334388429503== Content-Type: multipart/alternative; boundary=047d7bf10a769019d304d520e4e5 --047d7bf10a769019d304d520e4e5 Content-Type: text/plain; charset=ISO-8859-1 Paravitualization is very great so I would prefer it but the things I tought was whether there are differences for compilers aspecially for languages like C/C++ in the case of HVM and PV. I think for a managed code codebase it would be unimportant where it get builds. I think that a few tests are needed to find out whether there are differences for build process in HVM mode and PV mode. Best Regards 2013/2/7 > ** ** > > *From:* xen-users-bounces@lists.xen.org [mailto: > xen-users-bounces@lists.xen.org] *On Behalf Of *tech mailinglists > *Sent:* Wednesday, February 06, 2013 2:55 PM > *To:* xen-users > *Subject:* [Xen-users] PV or HVM guest for OpenBuildServices Host > (OpenSUSE based)**** > > ** ** > > Hello all, > > I don't know if it is a silly question but I am really unsure. I informed > myself about the OpenBuildService project which was initialized by OpenSUSE. > **** > > Now I am really interested in setting up an OpenBuildService VM where I > can package some programs and so on for example own software and software I > wan't to use on a few systems which have for example newer versions not in > there offical repository actually. I think that OpenBuildService gives a > more or less universal environment and secure build environment.**** > > I thought about which guest type I should use. I am not that familiar with > for example compiler optimization algorithms and so I asked my self the > question would it be better to build up an PV or an HVM OpenSUSE DomU. What > would be better? Does it matter if it is a PV or HVM guest for compiler > optimazations and so on?**** > > Would be great when someone could give me an answer.**** > > Best Regards**** > > ** ** > > ** ** > > Hi,**** > > ** ** > > Disregarding the purpose of the machine, HVM comes at a costs.**** > > Sometimes it is unavoidable, if the OS (like *bsd) requires it, but > otherwise: use PV.**** > > There are some drivers to lessen the pain, but PV remains almost the > fastest way for virtualization/isolation.**** > > ** ** > > HW**** > > ** ** > > ** ** > ------------------------------ > Dit bericht kan informatie bevatten die niet voor u is bestemd. Indien u > niet de geadresseerde bent of dit bericht abusievelijk aan u is > toegezonden, wordt u verzocht dat aan de afzender te melden en het bericht > te verwijderen. De Staat aanvaardt geen aansprakelijkheid voor schade, van > welke aard ook, die verband houdt met risico's verbonden aan het > elektronisch verzenden van berichten. > > This message may contain information that is not intended for you. If you > are not the addressee or if this message was sent to you by mistake, you > are requested to inform the sender and delete the message. The State > accepts no liability for damage of any kind resulting from the risks > inherent in the electronic transmission of messages. > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xen.org > http://lists.xen.org/xen-users > --047d7bf10a769019d304d520e4e5 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Paravitualization is very great so I would prefer it = but the things I tought was whether there are differences for compilers asp= ecially for languages like C/C++ in the case of HVM and PV. I think for a m= anaged code codebase it would be unimportant where it get builds.

I think that a few tests are needed to find out whether there are= differences for build process in HVM mode and PV mode.

Best Regards=


201= 3/2/7 <J.Witvliet@mindef.nl>

=A0

From: xen-users-bo= unces@lists.xen.org [mailto:xen-users-bounces@lists.xen.org] On Behalf Of tech mailinglists
Sent: Wednesday, February 06= , 2013 2:55 PM
To: xen-us= ers
Subject: [Xen-users] = PV or HVM guest for OpenBuildServices Host (OpenSUSE based)

=A0

Hello all,

I don't know if it is a silly question but I am really unsure. I in= formed myself about the OpenBuildService project which was initialized by O= penSUSE.

= Now I am really interested in setting up an OpenBuildService VM where I can= package some programs and so on for example own software and software I wa= n't to use on a few systems which have for example newer versions not i= n there offical repository actually. I think that OpenBuildService gives a = more or less universal environment and secure build environment.<= /u>

I thought about= which guest type I should use. I am not that familiar with for example com= piler optimization algorithms and so I asked my self the question would it = be better to build up an PV or an HVM OpenSUSE DomU. What would be better? = Does it matter if it is a PV or HVM guest for compiler optimazations and so= on?

Would be great = when someone could give me an answer.

=

= Best Regards

= =A0

=A0<= /font>

Hi,

=A0

Disregarding the purpose of the machine, =A0HVM comes at a = costs.

Sometimes it is unavoidable, if the OS (like *bsd) requires= it, but otherwise: use PV.

There are some drivers to lessen the pain, but PV remains a= lmost the fastest way for virtualization/isolation.

=A0

<= font color=3D"#1f497d" face=3D"Calibri">HW

=A0

<= font color=3D"#1f497d" face=3D"Calibri">= =A0

Dit bericht kan informatie bevatten die niet voor u is bestemd. Indien = u niet de geadresseerde bent of dit bericht abusievelijk aan u is toegezond= en, wordt u verzocht dat aan de afzender te melden en het bericht te verwij= deren. De Staat aanvaardt geen aansprakelijkheid voor schade, van welke aar= d ook, die verband houdt met risico's verbonden aan het elektronisch ve= rzenden van berichten.

This message may contain information that is not intended for you. If you a= re not the addressee or if this message was sent to you by mistake, you are= requested to inform the sender and delete the message. The State accepts n= o liability for damage of any kind resulting from the risks inherent in the= electronic transmission of messages.

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

--047d7bf10a769019d304d520e4e5-- --===============1719533334388429503== 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 --===============1719533334388429503==-- From xen-users-bounces@lists.xen.org Thu Feb 07 12:15:22 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 07 Feb 2013 12:15: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 1U3QNB-00060g-Sa; Thu, 07 Feb 2013 12:14:37 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U3QNA-00060R-JN; Thu, 07 Feb 2013 12:14:36 +0000 Received: from [85.158.137.99:25314] by server-16.bemta-3.messagelabs.com id EE/70-02727-BAA93115; Thu, 07 Feb 2013 12:14:35 +0000 X-Env-Sender: samuel.thibault@ens-lyon.org X-Msg-Ref: server-15.tower-217.messagelabs.com!1360239274!18080439!1 X-Originating-IP: [192.134.164.104] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 27579 invoked from network); 7 Feb 2013 12:14:35 -0000 Received: from mail3-relais-sop.national.inria.fr (HELO mail3-relais-sop.national.inria.fr) (192.134.164.104) by server-15.tower-217.messagelabs.com with RC4-SHA encrypted SMTP; 7 Feb 2013 12:14:35 -0000 X-IronPort-AV: E=Sophos;i="4.84,622,1355094000"; d="scan'208";a="1400556" Received: from unknown (HELO type.ipv6) ([193.50.110.166]) by mail3-relais-sop.national.inria.fr with ESMTP/TLS/DHE-RSA-AES128-SHA; 07 Feb 2013 13:07:41 +0100 Received: from samy by type.ipv6 with local (Exim 4.80) (envelope-from ) id 1U3QN8-0003dk-CH; Thu, 07 Feb 2013 13:14:34 +0100 Date: Thu, 7 Feb 2013 13:14:34 +0100 From: Samuel Thibault To: tech mailinglists , xen-users , "xen-devel@lists.xen.org" Message-ID: <20130207121434.GD9769@type.bordeaux.inria.fr> Mail-Followup-To: Samuel Thibault , tech mailinglists , xen-users , "xen-devel@lists.xen.org" References: <20130207110347.GX6193@type.bordeaux.inria.fr> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <20130207110347.GX6193@type.bordeaux.inria.fr> User-Agent: Mutt/1.5.21+34 (58baf7c9f32f) (2010-12-30) Subject: Re: [Xen-users] [Xen-devel] State of Stubdomains on NetBSD X-BeenThere: xen-users@lists.xen.org X-Mailman-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 Samuel Thibault, le Thu 07 Feb 2013 12:03:47 +0100, a =E9crit : > tech mailinglists, le Thu 07 Feb 2013 11:56:39 +0100, a =E9crit : > > I read in the wiki that stubdomains aren't support on NetBSD. Will subd= oms be > > supported on NetBSD? Is someone working on that topic actually? > = > I see no reason why it should be hard to do it, Except that you need a gcc compiler which is able to build mini-os & such, but I guess this is already the case? I see that there is already a -U __FreeBSD__ in the stubdom/Makefile, so it looks like somebody has already given a try on FreeBSD, and NetBSD shouldn't be very far. Samuel _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Thu Feb 07 12:15:22 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 07 Feb 2013 12:15: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 1U3QNB-00060g-Sa; Thu, 07 Feb 2013 12:14:37 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U3QNA-00060R-JN; Thu, 07 Feb 2013 12:14:36 +0000 Received: from [85.158.137.99:25314] by server-16.bemta-3.messagelabs.com id EE/70-02727-BAA93115; Thu, 07 Feb 2013 12:14:35 +0000 X-Env-Sender: samuel.thibault@ens-lyon.org X-Msg-Ref: server-15.tower-217.messagelabs.com!1360239274!18080439!1 X-Originating-IP: [192.134.164.104] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 27579 invoked from network); 7 Feb 2013 12:14:35 -0000 Received: from mail3-relais-sop.national.inria.fr (HELO mail3-relais-sop.national.inria.fr) (192.134.164.104) by server-15.tower-217.messagelabs.com with RC4-SHA encrypted SMTP; 7 Feb 2013 12:14:35 -0000 X-IronPort-AV: E=Sophos;i="4.84,622,1355094000"; d="scan'208";a="1400556" Received: from unknown (HELO type.ipv6) ([193.50.110.166]) by mail3-relais-sop.national.inria.fr with ESMTP/TLS/DHE-RSA-AES128-SHA; 07 Feb 2013 13:07:41 +0100 Received: from samy by type.ipv6 with local (Exim 4.80) (envelope-from ) id 1U3QN8-0003dk-CH; Thu, 07 Feb 2013 13:14:34 +0100 Date: Thu, 7 Feb 2013 13:14:34 +0100 From: Samuel Thibault To: tech mailinglists , xen-users , "xen-devel@lists.xen.org" Message-ID: <20130207121434.GD9769@type.bordeaux.inria.fr> Mail-Followup-To: Samuel Thibault , tech mailinglists , xen-users , "xen-devel@lists.xen.org" References: <20130207110347.GX6193@type.bordeaux.inria.fr> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <20130207110347.GX6193@type.bordeaux.inria.fr> User-Agent: Mutt/1.5.21+34 (58baf7c9f32f) (2010-12-30) Subject: Re: [Xen-users] [Xen-devel] State of Stubdomains on NetBSD X-BeenThere: xen-users@lists.xen.org X-Mailman-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 Samuel Thibault, le Thu 07 Feb 2013 12:03:47 +0100, a =E9crit : > tech mailinglists, le Thu 07 Feb 2013 11:56:39 +0100, a =E9crit : > > I read in the wiki that stubdomains aren't support on NetBSD. Will subd= oms be > > supported on NetBSD? Is someone working on that topic actually? > = > I see no reason why it should be hard to do it, Except that you need a gcc compiler which is able to build mini-os & such, but I guess this is already the case? I see that there is already a -U __FreeBSD__ in the stubdom/Makefile, so it looks like somebody has already given a try on FreeBSD, and NetBSD shouldn't be very far. Samuel _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Thu Feb 07 12:25:43 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 07 Feb 2013 12:25: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 1U3QXJ-0006r2-2e; Thu, 07 Feb 2013 12:25:05 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U3QXI-0006qj-1p; Thu, 07 Feb 2013 12:25:04 +0000 Received: from [85.158.143.99:44843] by server-2.bemta-4.messagelabs.com id 22/80-01597-F1D93115; Thu, 07 Feb 2013 12:25:03 +0000 X-Env-Sender: roger.pau@citrix.com X-Msg-Ref: server-2.tower-216.messagelabs.com!1360239902!23047853!1 X-Originating-IP: [46.33.159.39] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNDYuMzMuMTU5LjM5ID0+IDIxNDQ2\n X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 3201 invoked from network); 7 Feb 2013 12:25:03 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (46.33.159.39) by server-2.tower-216.messagelabs.com with RC4-SHA encrypted SMTP; 7 Feb 2013 12:25:03 -0000 X-IronPort-AV: E=Sophos;i="4.84,622,1355097600"; d="scan'208";a="1236108" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 07 Feb 2013 12:25:03 +0000 Received: from [192.168.1.30] (10.30.249.242) by LONPMAILMX01.citrite.net (10.30.203.162) with Microsoft SMTP Server id 8.3.297.1; Thu, 7 Feb 2013 12:25:02 +0000 Message-ID: <51139D20.60606@citrix.com> Date: Thu, 7 Feb 2013 13:25:04 +0100 From: =?ISO-8859-1?Q?Roger_Pau_Monn=E9?= User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130107 Thunderbird/17.0.2 MIME-Version: 1.0 To: Samuel Thibault , tech mailinglists , xen-users , "xen-devel@lists.xen.org" References: <20130207110347.GX6193@type.bordeaux.inria.fr> <20130207121434.GD9769@type.bordeaux.inria.fr> In-Reply-To: <20130207121434.GD9769@type.bordeaux.inria.fr> Subject: Re: [Xen-users] [Xen-devel] State of Stubdomains on NetBSD X-BeenThere: xen-users@lists.xen.org X-Mailman-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 07/02/13 13:14, Samuel Thibault wrote: > Samuel Thibault, le Thu 07 Feb 2013 12:03:47 +0100, a =E9crit : >> tech mailinglists, le Thu 07 Feb 2013 11:56:39 +0100, a =E9crit : >>> I read in the wiki that stubdomains aren't support on NetBSD. Will subd= oms be >>> supported on NetBSD? Is someone working on that topic actually? >> >> I see no reason why it should be hard to do it, > = > Except that you need a gcc compiler which is able to build mini-os & > such, but I guess this is already the case? I see that there is already > a -U __FreeBSD__ in the stubdom/Makefile, so it looks like somebody has > already given a try on FreeBSD, and NetBSD shouldn't be very far. I've given it a look some time ago, but the build of newlib (if I remember correctly) had dependencies on a bunch of Linux header files which are not present on NetBSD. I guess a solution would be to ship all those necessary headers with stubdoms, and use them when needed, but I'm afraid that will probably crash with headers already present in NetBSD. Another (and much simpler option) is to compile the stubdomains on a Linux system and then copy them to your NetBSD system (or fetch them from a packaged version of Xen from a Linux distro). _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Thu Feb 07 12:25:43 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 07 Feb 2013 12:25: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 1U3QXJ-0006r2-2e; Thu, 07 Feb 2013 12:25:05 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U3QXI-0006qj-1p; Thu, 07 Feb 2013 12:25:04 +0000 Received: from [85.158.143.99:44843] by server-2.bemta-4.messagelabs.com id 22/80-01597-F1D93115; Thu, 07 Feb 2013 12:25:03 +0000 X-Env-Sender: roger.pau@citrix.com X-Msg-Ref: server-2.tower-216.messagelabs.com!1360239902!23047853!1 X-Originating-IP: [46.33.159.39] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNDYuMzMuMTU5LjM5ID0+IDIxNDQ2\n X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 3201 invoked from network); 7 Feb 2013 12:25:03 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (46.33.159.39) by server-2.tower-216.messagelabs.com with RC4-SHA encrypted SMTP; 7 Feb 2013 12:25:03 -0000 X-IronPort-AV: E=Sophos;i="4.84,622,1355097600"; d="scan'208";a="1236108" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 07 Feb 2013 12:25:03 +0000 Received: from [192.168.1.30] (10.30.249.242) by LONPMAILMX01.citrite.net (10.30.203.162) with Microsoft SMTP Server id 8.3.297.1; Thu, 7 Feb 2013 12:25:02 +0000 Message-ID: <51139D20.60606@citrix.com> Date: Thu, 7 Feb 2013 13:25:04 +0100 From: =?ISO-8859-1?Q?Roger_Pau_Monn=E9?= User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130107 Thunderbird/17.0.2 MIME-Version: 1.0 To: Samuel Thibault , tech mailinglists , xen-users , "xen-devel@lists.xen.org" References: <20130207110347.GX6193@type.bordeaux.inria.fr> <20130207121434.GD9769@type.bordeaux.inria.fr> In-Reply-To: <20130207121434.GD9769@type.bordeaux.inria.fr> Subject: Re: [Xen-users] [Xen-devel] State of Stubdomains on NetBSD X-BeenThere: xen-users@lists.xen.org X-Mailman-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 07/02/13 13:14, Samuel Thibault wrote: > Samuel Thibault, le Thu 07 Feb 2013 12:03:47 +0100, a =E9crit : >> tech mailinglists, le Thu 07 Feb 2013 11:56:39 +0100, a =E9crit : >>> I read in the wiki that stubdomains aren't support on NetBSD. Will subd= oms be >>> supported on NetBSD? Is someone working on that topic actually? >> >> I see no reason why it should be hard to do it, > = > Except that you need a gcc compiler which is able to build mini-os & > such, but I guess this is already the case? I see that there is already > a -U __FreeBSD__ in the stubdom/Makefile, so it looks like somebody has > already given a try on FreeBSD, and NetBSD shouldn't be very far. I've given it a look some time ago, but the build of newlib (if I remember correctly) had dependencies on a bunch of Linux header files which are not present on NetBSD. I guess a solution would be to ship all those necessary headers with stubdoms, and use them when needed, but I'm afraid that will probably crash with headers already present in NetBSD. Another (and much simpler option) is to compile the stubdomains on a Linux system and then copy them to your NetBSD system (or fetch them from a packaged version of Xen from a Linux distro). _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Thu Feb 07 12:29:14 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 07 Feb 2013 12:29: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 1U3Qao-0007Mk-GY; Thu, 07 Feb 2013 12:28:42 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U3Qal-0007MM-Sk; Thu, 07 Feb 2013 12:28:40 +0000 Received: from [85.158.137.99:52696] by server-14.bemta-3.messagelabs.com id F0/DC-23533-6FD93115; Thu, 07 Feb 2013 12:28:38 +0000 X-Env-Sender: mailinglists.tech@gmail.com X-Msg-Ref: server-9.tower-217.messagelabs.com!1360240118!17249760!1 X-Originating-IP: [209.85.212.170] 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.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 14677 invoked from network); 7 Feb 2013 12:28:38 -0000 Received: from mail-wi0-f170.google.com (HELO mail-wi0-f170.google.com) (209.85.212.170) by server-9.tower-217.messagelabs.com with RC4-SHA encrypted SMTP; 7 Feb 2013 12:28:38 -0000 Received: by mail-wi0-f170.google.com with SMTP id hm11so8261628wib.3 for ; Thu, 07 Feb 2013 04:28:38 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=usodjGGjPwLT1MSSSFz8mI4l/6cV5gRz00ZeDVfdjwc=; b=uSnbE9zv3+D/DdWSZEFDQEvAeMcYC8/u/dcJfWQz1FGBxjk4+mC7E+WmYiw3hJDfZb U1GdH4Wk2INn/22Rs094nh6Pj3rIZH79ZAJt9vtDGtlYcAUkkYzUm7ICO+3PQC2v8OJr w+JRHGBJqLbHSF32et/gP19ik6L0PByUOtlEhAJCyY7xGEMNWxCOzprvoLGIk7Ugy4E3 7Ouw1izcwsi7ThyRlSMUDMdK0SlR/RXunzk29/9QvnG4TvbHxA+uIcFm1Lh2ae+6mizV HVY2hMa5ZMaUV+4zleI0rU+T10fI7CzDxqwkwDjIYxMFxNkFZZ7CG6uVsjJNhRonAvL8 AVEw== MIME-Version: 1.0 X-Received: by 10.194.76.7 with SMTP id g7mr2290858wjw.50.1360240117936; Thu, 07 Feb 2013 04:28:37 -0800 (PST) Received: by 10.227.203.18 with HTTP; Thu, 7 Feb 2013 04:28:37 -0800 (PST) In-Reply-To: <51139D20.60606@citrix.com> References: <20130207110347.GX6193@type.bordeaux.inria.fr> <20130207121434.GD9769@type.bordeaux.inria.fr> <51139D20.60606@citrix.com> Date: Thu, 7 Feb 2013 13:28:37 +0100 Message-ID: From: tech mailinglists To: =?ISO-8859-1?Q?Roger_Pau_Monn=E9?= Cc: Samuel Thibault , "xen-devel@lists.xen.org" , xen-users Subject: Re: [Xen-users] [Xen-devel] State of Stubdomains on NetBSD X-BeenThere: xen-users@lists.xen.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="===============6288592786402779184==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============6288592786402779184== Content-Type: multipart/alternative; boundary=047d7beba20209f24e04d5219561 --047d7beba20209f24e04d5219561 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Ok, the building will be no problem to do this on a Linux system. But all is given in the NetBSD Dom0 kernel and Xen to run Stubdoms on NetBSD am I right? Best Regards 2013/2/7 Roger Pau Monn=E9 > On 07/02/13 13:14, Samuel Thibault wrote: > > Samuel Thibault, le Thu 07 Feb 2013 12:03:47 +0100, a =E9crit : > >> tech mailinglists, le Thu 07 Feb 2013 11:56:39 +0100, a =E9crit : > >>> I read in the wiki that stubdomains aren't support on NetBSD. Will > subdoms be > >>> supported on NetBSD? Is someone working on that topic actually? > >> > >> I see no reason why it should be hard to do it, > > > > Except that you need a gcc compiler which is able to build mini-os & > > such, but I guess this is already the case? I see that there is alread= y > > a -U __FreeBSD__ in the stubdom/Makefile, so it looks like somebody has > > already given a try on FreeBSD, and NetBSD shouldn't be very far. > > I've given it a look some time ago, but the build of newlib (if I > remember correctly) had dependencies on a bunch of Linux header files > which are not present on NetBSD. I guess a solution would be to ship all > those necessary headers with stubdoms, and use them when needed, but I'm > afraid that will probably crash with headers already present in NetBSD. > > Another (and much simpler option) is to compile the stubdomains on a > Linux system and then copy them to your NetBSD system (or fetch them > from a packaged version of Xen from a Linux distro). > > --047d7beba20209f24e04d5219561 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Ok, the building will be no problem to do this on a Linux = system. But all is given in the NetBSD Dom0 kernel and Xen to run Stubdoms = on NetBSD am I right?

Best Regards


2013/2/7 Roger Pau Monn=E9 <roger.pa= u@citrix.com>
On 07/02/13 13:14, Samuel Thibault = wrote:
> Samuel Thibault, le Thu 07 Feb 2013 12:03:47 +0100, a =E9crit :
>> tech mailinglists, le Thu 07 Feb 2013 11:56:39 +0100, a =E9crit :<= br> >>> I read in the wiki that stubdomains aren't support on NetB= SD. Will subdoms be
>>> supported on NetBSD? Is someone working on that topic actually= ?
>>
>> I see no reason why it should be hard to do it,
>
> Except that you need a gcc compiler which is able to build mini-os &am= p;
> such, but I guess this is already the case? =A0I see that there is alr= eady
> a -U __FreeBSD__ in the stubdom/Makefile, so it looks like somebody ha= s
> already given a try on FreeBSD, and NetBSD shouldn't be very far.<= br>
I've given it a look some time ago, but the build of newlib= (if I
remember correctly) had dependencies on a bunch of Linux header files
which are not present on NetBSD. I guess a solution would be to ship all those necessary headers with stubdoms, and use them when needed, but I'= m
afraid that will probably crash with headers already present in NetBSD.

Another (and much simpler option) is to compile the stubdomains on a
Linux system and then copy them to your NetBSD system (or fetch them
from a packaged version of Xen from a Linux distro).


--047d7beba20209f24e04d5219561-- --===============6288592786402779184== 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 --===============6288592786402779184==-- From xen-users-bounces@lists.xen.org Thu Feb 07 12:29:14 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 07 Feb 2013 12:29: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 1U3Qao-0007Mk-GY; Thu, 07 Feb 2013 12:28:42 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U3Qal-0007MM-Sk; Thu, 07 Feb 2013 12:28:40 +0000 Received: from [85.158.137.99:52696] by server-14.bemta-3.messagelabs.com id F0/DC-23533-6FD93115; Thu, 07 Feb 2013 12:28:38 +0000 X-Env-Sender: mailinglists.tech@gmail.com X-Msg-Ref: server-9.tower-217.messagelabs.com!1360240118!17249760!1 X-Originating-IP: [209.85.212.170] 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.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 14677 invoked from network); 7 Feb 2013 12:28:38 -0000 Received: from mail-wi0-f170.google.com (HELO mail-wi0-f170.google.com) (209.85.212.170) by server-9.tower-217.messagelabs.com with RC4-SHA encrypted SMTP; 7 Feb 2013 12:28:38 -0000 Received: by mail-wi0-f170.google.com with SMTP id hm11so8261628wib.3 for ; Thu, 07 Feb 2013 04:28:38 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=usodjGGjPwLT1MSSSFz8mI4l/6cV5gRz00ZeDVfdjwc=; b=uSnbE9zv3+D/DdWSZEFDQEvAeMcYC8/u/dcJfWQz1FGBxjk4+mC7E+WmYiw3hJDfZb U1GdH4Wk2INn/22Rs094nh6Pj3rIZH79ZAJt9vtDGtlYcAUkkYzUm7ICO+3PQC2v8OJr w+JRHGBJqLbHSF32et/gP19ik6L0PByUOtlEhAJCyY7xGEMNWxCOzprvoLGIk7Ugy4E3 7Ouw1izcwsi7ThyRlSMUDMdK0SlR/RXunzk29/9QvnG4TvbHxA+uIcFm1Lh2ae+6mizV HVY2hMa5ZMaUV+4zleI0rU+T10fI7CzDxqwkwDjIYxMFxNkFZZ7CG6uVsjJNhRonAvL8 AVEw== MIME-Version: 1.0 X-Received: by 10.194.76.7 with SMTP id g7mr2290858wjw.50.1360240117936; Thu, 07 Feb 2013 04:28:37 -0800 (PST) Received: by 10.227.203.18 with HTTP; Thu, 7 Feb 2013 04:28:37 -0800 (PST) In-Reply-To: <51139D20.60606@citrix.com> References: <20130207110347.GX6193@type.bordeaux.inria.fr> <20130207121434.GD9769@type.bordeaux.inria.fr> <51139D20.60606@citrix.com> Date: Thu, 7 Feb 2013 13:28:37 +0100 Message-ID: From: tech mailinglists To: =?ISO-8859-1?Q?Roger_Pau_Monn=E9?= Cc: Samuel Thibault , "xen-devel@lists.xen.org" , xen-users Subject: Re: [Xen-users] [Xen-devel] State of Stubdomains on NetBSD X-BeenThere: xen-users@lists.xen.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="===============6288592786402779184==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============6288592786402779184== Content-Type: multipart/alternative; boundary=047d7beba20209f24e04d5219561 --047d7beba20209f24e04d5219561 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Ok, the building will be no problem to do this on a Linux system. But all is given in the NetBSD Dom0 kernel and Xen to run Stubdoms on NetBSD am I right? Best Regards 2013/2/7 Roger Pau Monn=E9 > On 07/02/13 13:14, Samuel Thibault wrote: > > Samuel Thibault, le Thu 07 Feb 2013 12:03:47 +0100, a =E9crit : > >> tech mailinglists, le Thu 07 Feb 2013 11:56:39 +0100, a =E9crit : > >>> I read in the wiki that stubdomains aren't support on NetBSD. Will > subdoms be > >>> supported on NetBSD? Is someone working on that topic actually? > >> > >> I see no reason why it should be hard to do it, > > > > Except that you need a gcc compiler which is able to build mini-os & > > such, but I guess this is already the case? I see that there is alread= y > > a -U __FreeBSD__ in the stubdom/Makefile, so it looks like somebody has > > already given a try on FreeBSD, and NetBSD shouldn't be very far. > > I've given it a look some time ago, but the build of newlib (if I > remember correctly) had dependencies on a bunch of Linux header files > which are not present on NetBSD. I guess a solution would be to ship all > those necessary headers with stubdoms, and use them when needed, but I'm > afraid that will probably crash with headers already present in NetBSD. > > Another (and much simpler option) is to compile the stubdomains on a > Linux system and then copy them to your NetBSD system (or fetch them > from a packaged version of Xen from a Linux distro). > > --047d7beba20209f24e04d5219561 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Ok, the building will be no problem to do this on a Linux = system. But all is given in the NetBSD Dom0 kernel and Xen to run Stubdoms = on NetBSD am I right?

Best Regards


2013/2/7 Roger Pau Monn=E9 <roger.pa= u@citrix.com>
On 07/02/13 13:14, Samuel Thibault = wrote:
> Samuel Thibault, le Thu 07 Feb 2013 12:03:47 +0100, a =E9crit :
>> tech mailinglists, le Thu 07 Feb 2013 11:56:39 +0100, a =E9crit :<= br> >>> I read in the wiki that stubdomains aren't support on NetB= SD. Will subdoms be
>>> supported on NetBSD? Is someone working on that topic actually= ?
>>
>> I see no reason why it should be hard to do it,
>
> Except that you need a gcc compiler which is able to build mini-os &am= p;
> such, but I guess this is already the case? =A0I see that there is alr= eady
> a -U __FreeBSD__ in the stubdom/Makefile, so it looks like somebody ha= s
> already given a try on FreeBSD, and NetBSD shouldn't be very far.<= br>
I've given it a look some time ago, but the build of newlib= (if I
remember correctly) had dependencies on a bunch of Linux header files
which are not present on NetBSD. I guess a solution would be to ship all those necessary headers with stubdoms, and use them when needed, but I'= m
afraid that will probably crash with headers already present in NetBSD.

Another (and much simpler option) is to compile the stubdomains on a
Linux system and then copy them to your NetBSD system (or fetch them
from a packaged version of Xen from a Linux distro).


--047d7beba20209f24e04d5219561-- --===============6288592786402779184== 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 --===============6288592786402779184==-- From xen-users-bounces@lists.xen.org Thu Feb 07 12:29:18 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 07 Feb 2013 12:29: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 1U3Qau-0007No-Mf; Thu, 07 Feb 2013 12:28:48 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U3Qas-0007NA-3l; Thu, 07 Feb 2013 12:28:46 +0000 Received: from [85.158.137.99:53300] by server-12.bemta-3.messagelabs.com id D7/6F-05889-DFD93115; Thu, 07 Feb 2013 12:28:45 +0000 X-Env-Sender: samuel.thibault@ens-lyon.org X-Msg-Ref: server-15.tower-217.messagelabs.com!1360240123!18083522!1 X-Originating-IP: [192.134.164.104] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 19606 invoked from network); 7 Feb 2013 12:28:44 -0000 Received: from mail3-relais-sop.national.inria.fr (HELO mail3-relais-sop.national.inria.fr) (192.134.164.104) by server-15.tower-217.messagelabs.com with RC4-SHA encrypted SMTP; 7 Feb 2013 12:28:44 -0000 X-IronPort-AV: E=Sophos;i="4.84,622,1355094000"; d="scan'208";a="1402323" Received: from unknown (HELO type.ipv6) ([193.50.110.166]) by mail3-relais-sop.national.inria.fr with ESMTP/TLS/DHE-RSA-AES128-SHA; 07 Feb 2013 13:21:50 +0100 Received: from samy by type.ipv6 with local (Exim 4.80) (envelope-from ) id 1U3Qao-0004CI-TL; Thu, 07 Feb 2013 13:28:42 +0100 Date: Thu, 7 Feb 2013 13:28:42 +0100 From: Samuel Thibault To: Roger Pau =?iso-8859-1?Q?Monn=E9?= Message-ID: <20130207122842.GF9769@type.bordeaux.inria.fr> Mail-Followup-To: Samuel Thibault , Roger Pau =?iso-8859-1?Q?Monn=E9?= , tech mailinglists , xen-users , "xen-devel@lists.xen.org" References: <20130207110347.GX6193@type.bordeaux.inria.fr> <20130207121434.GD9769@type.bordeaux.inria.fr> <51139D20.60606@citrix.com> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <51139D20.60606@citrix.com> User-Agent: Mutt/1.5.21+34 (58baf7c9f32f) (2010-12-30) Cc: tech mailinglists , xen-users , "xen-devel@lists.xen.org" Subject: Re: [Xen-users] [Xen-devel] State of Stubdomains on NetBSD X-BeenThere: xen-users@lists.xen.org X-Mailman-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 Roger Pau Monn=E9, le Thu 07 Feb 2013 13:25:04 +0100, a =E9crit : > the build of newlib (if I remember correctly) had dependencies on a > bunch of Linux header files which are not present on NetBSD. Ah? I don't see why newlib should fetch such header, since we configure it with target=3Darch-xen-elf, it's not supposed to assume anything linuxish. > Another (and much simpler option) is to compile the stubdomains on a > Linux system and then copy them to your NetBSD system (or fetch them > from a packaged version of Xen from a Linux distro). Yes, this should just work. Samuel _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Thu Feb 07 12:29:18 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 07 Feb 2013 12:29: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 1U3Qau-0007No-Mf; Thu, 07 Feb 2013 12:28:48 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U3Qas-0007NA-3l; Thu, 07 Feb 2013 12:28:46 +0000 Received: from [85.158.137.99:53300] by server-12.bemta-3.messagelabs.com id D7/6F-05889-DFD93115; Thu, 07 Feb 2013 12:28:45 +0000 X-Env-Sender: samuel.thibault@ens-lyon.org X-Msg-Ref: server-15.tower-217.messagelabs.com!1360240123!18083522!1 X-Originating-IP: [192.134.164.104] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 19606 invoked from network); 7 Feb 2013 12:28:44 -0000 Received: from mail3-relais-sop.national.inria.fr (HELO mail3-relais-sop.national.inria.fr) (192.134.164.104) by server-15.tower-217.messagelabs.com with RC4-SHA encrypted SMTP; 7 Feb 2013 12:28:44 -0000 X-IronPort-AV: E=Sophos;i="4.84,622,1355094000"; d="scan'208";a="1402323" Received: from unknown (HELO type.ipv6) ([193.50.110.166]) by mail3-relais-sop.national.inria.fr with ESMTP/TLS/DHE-RSA-AES128-SHA; 07 Feb 2013 13:21:50 +0100 Received: from samy by type.ipv6 with local (Exim 4.80) (envelope-from ) id 1U3Qao-0004CI-TL; Thu, 07 Feb 2013 13:28:42 +0100 Date: Thu, 7 Feb 2013 13:28:42 +0100 From: Samuel Thibault To: Roger Pau =?iso-8859-1?Q?Monn=E9?= Message-ID: <20130207122842.GF9769@type.bordeaux.inria.fr> Mail-Followup-To: Samuel Thibault , Roger Pau =?iso-8859-1?Q?Monn=E9?= , tech mailinglists , xen-users , "xen-devel@lists.xen.org" References: <20130207110347.GX6193@type.bordeaux.inria.fr> <20130207121434.GD9769@type.bordeaux.inria.fr> <51139D20.60606@citrix.com> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <51139D20.60606@citrix.com> User-Agent: Mutt/1.5.21+34 (58baf7c9f32f) (2010-12-30) Cc: tech mailinglists , xen-users , "xen-devel@lists.xen.org" Subject: Re: [Xen-users] [Xen-devel] State of Stubdomains on NetBSD X-BeenThere: xen-users@lists.xen.org X-Mailman-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 Roger Pau Monn=E9, le Thu 07 Feb 2013 13:25:04 +0100, a =E9crit : > the build of newlib (if I remember correctly) had dependencies on a > bunch of Linux header files which are not present on NetBSD. Ah? I don't see why newlib should fetch such header, since we configure it with target=3Darch-xen-elf, it's not supposed to assume anything linuxish. > Another (and much simpler option) is to compile the stubdomains on a > Linux system and then copy them to your NetBSD system (or fetch them > from a packaged version of Xen from a Linux distro). Yes, this should just work. Samuel _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Thu Feb 07 12:32:18 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 07 Feb 2013 12:32: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 1U3Qdv-000065-EW; Thu, 07 Feb 2013 12:31:55 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U3Qds-00005b-Se; Thu, 07 Feb 2013 12:31:52 +0000 Received: from [85.158.137.99:28956] by server-8.bemta-3.messagelabs.com id C0/D0-25687-2BE93115; Thu, 07 Feb 2013 12:31:46 +0000 X-Env-Sender: samuel.thibault@ens-lyon.org X-Msg-Ref: server-15.tower-217.messagelabs.com!1360240295!18084169!1 X-Originating-IP: [192.134.164.83] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 3868 invoked from network); 7 Feb 2013 12:31:35 -0000 Received: from mail2-relais-roc.national.inria.fr (HELO mail2-relais-roc.national.inria.fr) (192.134.164.83) by server-15.tower-217.messagelabs.com with RC4-SHA encrypted SMTP; 7 Feb 2013 12:31:35 -0000 X-IronPort-AV: E=Sophos;i="4.84,622,1355094000"; d="scan'208";a="1808103" Received: from unknown (HELO type.ipv6) ([193.50.110.166]) by mail2-relais-roc.national.inria.fr with ESMTP/TLS/DHE-RSA-AES128-SHA; 07 Feb 2013 13:31:35 +0100 Received: from samy by type.ipv6 with local (Exim 4.80) (envelope-from ) id 1U3Qda-0004NI-Tk; Thu, 07 Feb 2013 13:31:34 +0100 Date: Thu, 7 Feb 2013 13:31:34 +0100 From: Samuel Thibault To: tech mailinglists Message-ID: <20130207123134.GH9769@type.bordeaux.inria.fr> Mail-Followup-To: Samuel Thibault , tech mailinglists , Roger Pau =?iso-8859-1?Q?Monn=E9?= , xen-users , "xen-devel@lists.xen.org" References: <20130207110347.GX6193@type.bordeaux.inria.fr> <20130207121434.GD9769@type.bordeaux.inria.fr> <51139D20.60606@citrix.com> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21+34 (58baf7c9f32f) (2010-12-30) Cc: xen-users , "xen-devel@lists.xen.org" , Roger Pau =?iso-8859-1?Q?Monn=E9?= Subject: Re: [Xen-users] [Xen-devel] State of Stubdomains on NetBSD X-BeenThere: xen-users@lists.xen.org X-Mailman-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 tech mailinglists, le Thu 07 Feb 2013 13:28:37 +0100, a =E9crit : > Ok, the building will be no problem to do this on a Linux system. But all= is > given in the NetBSD Dom0 kernel and Xen to run Stubdoms on NetBSD am I ri= ght? Dom0 is not really involved when using a stubdom, so be it Linux or NetBSD should not matter. Samuel _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Thu Feb 07 12:32:18 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 07 Feb 2013 12:32: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 1U3Qdv-000065-EW; Thu, 07 Feb 2013 12:31:55 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U3Qds-00005b-Se; Thu, 07 Feb 2013 12:31:52 +0000 Received: from [85.158.137.99:28956] by server-8.bemta-3.messagelabs.com id C0/D0-25687-2BE93115; Thu, 07 Feb 2013 12:31:46 +0000 X-Env-Sender: samuel.thibault@ens-lyon.org X-Msg-Ref: server-15.tower-217.messagelabs.com!1360240295!18084169!1 X-Originating-IP: [192.134.164.83] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 3868 invoked from network); 7 Feb 2013 12:31:35 -0000 Received: from mail2-relais-roc.national.inria.fr (HELO mail2-relais-roc.national.inria.fr) (192.134.164.83) by server-15.tower-217.messagelabs.com with RC4-SHA encrypted SMTP; 7 Feb 2013 12:31:35 -0000 X-IronPort-AV: E=Sophos;i="4.84,622,1355094000"; d="scan'208";a="1808103" Received: from unknown (HELO type.ipv6) ([193.50.110.166]) by mail2-relais-roc.national.inria.fr with ESMTP/TLS/DHE-RSA-AES128-SHA; 07 Feb 2013 13:31:35 +0100 Received: from samy by type.ipv6 with local (Exim 4.80) (envelope-from ) id 1U3Qda-0004NI-Tk; Thu, 07 Feb 2013 13:31:34 +0100 Date: Thu, 7 Feb 2013 13:31:34 +0100 From: Samuel Thibault To: tech mailinglists Message-ID: <20130207123134.GH9769@type.bordeaux.inria.fr> Mail-Followup-To: Samuel Thibault , tech mailinglists , Roger Pau =?iso-8859-1?Q?Monn=E9?= , xen-users , "xen-devel@lists.xen.org" References: <20130207110347.GX6193@type.bordeaux.inria.fr> <20130207121434.GD9769@type.bordeaux.inria.fr> <51139D20.60606@citrix.com> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21+34 (58baf7c9f32f) (2010-12-30) Cc: xen-users , "xen-devel@lists.xen.org" , Roger Pau =?iso-8859-1?Q?Monn=E9?= Subject: Re: [Xen-users] [Xen-devel] State of Stubdomains on NetBSD X-BeenThere: xen-users@lists.xen.org X-Mailman-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 tech mailinglists, le Thu 07 Feb 2013 13:28:37 +0100, a =E9crit : > Ok, the building will be no problem to do this on a Linux system. But all= is > given in the NetBSD Dom0 kernel and Xen to run Stubdoms on NetBSD am I ri= ght? Dom0 is not really involved when using a stubdom, so be it Linux or NetBSD should not matter. Samuel _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Thu Feb 07 14:50:17 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 07 Feb 2013 14:50: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 1U3Smr-0006hy-G1; Thu, 07 Feb 2013 14:49:17 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U3Smq-0006hn-4C for xen-users@lists.xen.org; Thu, 07 Feb 2013 14:49:16 +0000 Received: from [85.158.143.35:38261] by server-2.bemta-4.messagelabs.com id 4A/1E-01597-BEEB3115; Thu, 07 Feb 2013 14:49:15 +0000 X-Env-Sender: Nick.Couchman@seakr.com X-Msg-Ref: server-4.tower-21.messagelabs.com!1360248506!5256026!1 X-Originating-IP: [64.2.143.10] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 2033 invoked from network); 7 Feb 2013 14:48:28 -0000 Received: from mx1.seakr.com (HELO mx1.seakr.com) (64.2.143.10) by server-4.tower-21.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 7 Feb 2013 14:48:28 -0000 Received: from mx-inside.seakr.com ([192.168.100.31]) by mx1.seakr.com (8.14.3/8.14.3/Debian-9.4) with ESMTP id r17ElDld023325 for ; Thu, 7 Feb 2013 07:47:15 -0700 Received: from (mx-inside.seakr.com [192.168.100.31]) by mail-scanner1.it.seakr.com with smtp id 1fb8_326b_6c71df1c_7135_11e2_bfb2_00137252735f; Thu, 07 Feb 2013 07:48:25 -0700 Received: from collaborate.seakr.com (collaborate.seakr.com [192.168.100.28]) by mx-inside.seakr.com (Postfix) with ESMTP id 124AA44D9C for ; Thu, 7 Feb 2013 07:48:24 -0700 (MST) Received: from seakr-engineering-MTA by collaborate.seakr.com with Novell_GroupWise; Thu, 07 Feb 2013 07:48:23 -0700 Message-Id: <51135C44020000990002AB39@collaborate.seakr.com> X-Mailer: Novell GroupWise Internet Agent 8.0.3 Date: Thu, 07 Feb 2013 07:48:20 -0700 From: "Nick Couchman" To: "tech mailinglists" , Mime-Version: 1.0 Content-Disposition: inline X-NAIMIME-Disclaimer: 1 X-NAIMIME-Modified: 1 Cc: xen-users Subject: Re: [Xen-users] PV or HVM guest for OpenBuildServices Host (OpenSUSE based) X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: 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, there should be no difference in the compiled code out of a PV machine vs. an HVM machine. The difference between PV and HVM is simply how they access the hardware - the results of machine-generated code should not different between the two. -Nick >>> On 2013/02/07 at 04:39, tech mailinglists wrote: > Paravitualization is very great so I would prefer it but the things I > tought was whether there are differences for compilers aspecially for > languages like C/C++ in the case of HVM and PV. I think for a managed code > codebase it would be unimportant where it get builds. > > I think that a few tests are needed to find out whether there are > differences for build process in HVM mode and PV mode. > > Best Regards > > > 2013/2/7 > >> ** ** >> >> *From:* xen-users-bounces@lists.xen.org [mailto: >> xen-users-bounces@lists.xen.org] *On Behalf Of *tech mailinglists >> *Sent:* Wednesday, February 06, 2013 2:55 PM >> *To:* xen-users >> *Subject:* [Xen-users] PV or HVM guest for OpenBuildServices Host >> (OpenSUSE based)**** >> >> ** ** >> >> Hello all, >> >> I don't know if it is a silly question but I am really unsure. I informed >> myself about the OpenBuildService project which was initialized by OpenSUSE. >> **** >> >> Now I am really interested in setting up an OpenBuildService VM where I >> can package some programs and so on for example own software and software I >> wan't to use on a few systems which have for example newer versions not in >> there offical repository actually. I think that OpenBuildService gives a >> more or less universal environment and secure build environment.**** >> >> I thought about which guest type I should use. I am not that familiar with >> for example compiler optimization algorithms and so I asked my self the >> question would it be better to build up an PV or an HVM OpenSUSE DomU. What >> would be better? Does it matter if it is a PV or HVM guest for compiler >> optimazations and so on?**** >> >> Would be great when someone could give me an answer.**** >> >> Best Regards**** >> >> ** ** >> >> ** ** >> >> Hi,**** >> >> ** ** >> >> Disregarding the purpose of the machine, HVM comes at a costs.**** >> >> Sometimes it is unavoidable, if the OS (like *bsd) requires it, but >> otherwise: use PV.**** >> >> There are some drivers to lessen the pain, but PV remains almost the >> fastest way for virtualization/isolation.**** >> >> ** ** >> >> HW**** >> >> ** ** >> >> ** ** >> ------------------------------ >> Dit bericht kan informatie bevatten die niet voor u is bestemd. Indien u >> niet de geadresseerde bent of dit bericht abusievelijk aan u is >> toegezonden, wordt u verzocht dat aan de afzender te melden en het bericht >> te verwijderen. De Staat aanvaardt geen aansprakelijkheid voor schade, van >> welke aard ook, die verband houdt met risico's verbonden aan het >> elektronisch verzenden van berichten. >> >> This message may contain information that is not intended for you. If you >> are not the addressee or if this message was sent to you by mistake, you >> are requested to inform the sender and delete the message. The State >> accepts no liability for damage of any kind resulting from the risks >> inherent in the electronic transmission of messages. >> >> _______________________________________________ >> Xen-users mailing list >> Xen-users@lists.xen.org >> http://lists.xen.org/xen-users >> -------- This e-mail may contain confidential and privileged material for the sole use of the intended recipient. If this email is not intended for you, or you are not responsible for the delivery of this message to the intended recipient, please note that this message may contain SEAKR Engineering (SEAKR) Privileged/Proprietary Information. In such a case, you are strictly prohibited from downloading, photocopying, distributing or otherwise using this message, its contents or attachments in any way. If you have received this message in error, please notify us immediately by replying to this e-mail and delete the message from your mailbox. Information contained in this message that does not relate to the business of SEAKR is neither endorsed by nor attributable to SEAKR. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Thu Feb 07 14:50:17 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 07 Feb 2013 14:50: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 1U3Smr-0006hy-G1; Thu, 07 Feb 2013 14:49:17 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U3Smq-0006hn-4C for xen-users@lists.xen.org; Thu, 07 Feb 2013 14:49:16 +0000 Received: from [85.158.143.35:38261] by server-2.bemta-4.messagelabs.com id 4A/1E-01597-BEEB3115; Thu, 07 Feb 2013 14:49:15 +0000 X-Env-Sender: Nick.Couchman@seakr.com X-Msg-Ref: server-4.tower-21.messagelabs.com!1360248506!5256026!1 X-Originating-IP: [64.2.143.10] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 2033 invoked from network); 7 Feb 2013 14:48:28 -0000 Received: from mx1.seakr.com (HELO mx1.seakr.com) (64.2.143.10) by server-4.tower-21.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 7 Feb 2013 14:48:28 -0000 Received: from mx-inside.seakr.com ([192.168.100.31]) by mx1.seakr.com (8.14.3/8.14.3/Debian-9.4) with ESMTP id r17ElDld023325 for ; Thu, 7 Feb 2013 07:47:15 -0700 Received: from (mx-inside.seakr.com [192.168.100.31]) by mail-scanner1.it.seakr.com with smtp id 1fb8_326b_6c71df1c_7135_11e2_bfb2_00137252735f; Thu, 07 Feb 2013 07:48:25 -0700 Received: from collaborate.seakr.com (collaborate.seakr.com [192.168.100.28]) by mx-inside.seakr.com (Postfix) with ESMTP id 124AA44D9C for ; Thu, 7 Feb 2013 07:48:24 -0700 (MST) Received: from seakr-engineering-MTA by collaborate.seakr.com with Novell_GroupWise; Thu, 07 Feb 2013 07:48:23 -0700 Message-Id: <51135C44020000990002AB39@collaborate.seakr.com> X-Mailer: Novell GroupWise Internet Agent 8.0.3 Date: Thu, 07 Feb 2013 07:48:20 -0700 From: "Nick Couchman" To: "tech mailinglists" , Mime-Version: 1.0 Content-Disposition: inline X-NAIMIME-Disclaimer: 1 X-NAIMIME-Modified: 1 Cc: xen-users Subject: Re: [Xen-users] PV or HVM guest for OpenBuildServices Host (OpenSUSE based) X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: 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, there should be no difference in the compiled code out of a PV machine vs. an HVM machine. The difference between PV and HVM is simply how they access the hardware - the results of machine-generated code should not different between the two. -Nick >>> On 2013/02/07 at 04:39, tech mailinglists wrote: > Paravitualization is very great so I would prefer it but the things I > tought was whether there are differences for compilers aspecially for > languages like C/C++ in the case of HVM and PV. I think for a managed code > codebase it would be unimportant where it get builds. > > I think that a few tests are needed to find out whether there are > differences for build process in HVM mode and PV mode. > > Best Regards > > > 2013/2/7 > >> ** ** >> >> *From:* xen-users-bounces@lists.xen.org [mailto: >> xen-users-bounces@lists.xen.org] *On Behalf Of *tech mailinglists >> *Sent:* Wednesday, February 06, 2013 2:55 PM >> *To:* xen-users >> *Subject:* [Xen-users] PV or HVM guest for OpenBuildServices Host >> (OpenSUSE based)**** >> >> ** ** >> >> Hello all, >> >> I don't know if it is a silly question but I am really unsure. I informed >> myself about the OpenBuildService project which was initialized by OpenSUSE. >> **** >> >> Now I am really interested in setting up an OpenBuildService VM where I >> can package some programs and so on for example own software and software I >> wan't to use on a few systems which have for example newer versions not in >> there offical repository actually. I think that OpenBuildService gives a >> more or less universal environment and secure build environment.**** >> >> I thought about which guest type I should use. I am not that familiar with >> for example compiler optimization algorithms and so I asked my self the >> question would it be better to build up an PV or an HVM OpenSUSE DomU. What >> would be better? Does it matter if it is a PV or HVM guest for compiler >> optimazations and so on?**** >> >> Would be great when someone could give me an answer.**** >> >> Best Regards**** >> >> ** ** >> >> ** ** >> >> Hi,**** >> >> ** ** >> >> Disregarding the purpose of the machine, HVM comes at a costs.**** >> >> Sometimes it is unavoidable, if the OS (like *bsd) requires it, but >> otherwise: use PV.**** >> >> There are some drivers to lessen the pain, but PV remains almost the >> fastest way for virtualization/isolation.**** >> >> ** ** >> >> HW**** >> >> ** ** >> >> ** ** >> ------------------------------ >> Dit bericht kan informatie bevatten die niet voor u is bestemd. Indien u >> niet de geadresseerde bent of dit bericht abusievelijk aan u is >> toegezonden, wordt u verzocht dat aan de afzender te melden en het bericht >> te verwijderen. De Staat aanvaardt geen aansprakelijkheid voor schade, van >> welke aard ook, die verband houdt met risico's verbonden aan het >> elektronisch verzenden van berichten. >> >> This message may contain information that is not intended for you. If you >> are not the addressee or if this message was sent to you by mistake, you >> are requested to inform the sender and delete the message. The State >> accepts no liability for damage of any kind resulting from the risks >> inherent in the electronic transmission of messages. >> >> _______________________________________________ >> Xen-users mailing list >> Xen-users@lists.xen.org >> http://lists.xen.org/xen-users >> -------- This e-mail may contain confidential and privileged material for the sole use of the intended recipient. If this email is not intended for you, or you are not responsible for the delivery of this message to the intended recipient, please note that this message may contain SEAKR Engineering (SEAKR) Privileged/Proprietary Information. In such a case, you are strictly prohibited from downloading, photocopying, distributing or otherwise using this message, its contents or attachments in any way. If you have received this message in error, please notify us immediately by replying to this e-mail and delete the message from your mailbox. Information contained in this message that does not relate to the business of SEAKR is neither endorsed by nor attributable to SEAKR. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Thu Feb 07 16:23:54 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 07 Feb 2013 16: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 1U3UFZ-0004SB-95; Thu, 07 Feb 2013 16:23:01 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U3UFX-0004Ry-Ip for xen-users@lists.xen.org; Thu, 07 Feb 2013 16:22:59 +0000 Received: from [85.158.139.211:53375] by server-6.bemta-5.messagelabs.com id BD/47-01489-2E4D3115; Thu, 07 Feb 2013 16:22:58 +0000 X-Env-Sender: mike@estone.ca X-Msg-Ref: server-12.tower-206.messagelabs.com!1360254164!18800186!1 X-Originating-IP: [199.185.220.80] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogMTk5LjE4NS4yMjAuODAgPT4gMjc2ODEx\n X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 12899 invoked from network); 7 Feb 2013 16:22:44 -0000 Received: from defout.telus.net (HELO outbound03.telus.net) (199.185.220.80) by server-12.tower-206.messagelabs.com with SMTP; 7 Feb 2013 16:22:44 -0000 Received: from edtncm02 ([199.185.220.224]) by priv-edtnes29.telusplanet.net (InterMail vM.8.01.03.00 201-2260-125-20100507) with ESMTP id <20130207162243.VEQQ12187.priv-edtnes29.telusplanet.net@edtncm02> for ; Thu, 7 Feb 2013 09:22:43 -0700 Received: from estone.ca ([154.20.1.203]) by edtncm02 with bizsmtp id xUNe1k00g4NnoEJ01UNfVB; Thu, 07 Feb 2013 09:22:42 -0700 X-Authority-Analysis: v=1.1 cv=SUDmmYpofWFcHskeL6GXKlG83HAHnN0LLSyWvxHysSM= c=1 sm=2 a=HXLQNss8UggA:10 a=d9BVEMumb3ZhJ1jenVoA:9 a=QEXdDO2ut3YA:10 a=SSmOFEACAAAA:8 a=iArNVvhu2_IA:10 a=zJJgJrR4LD4A:10 a=frz4AuCg-hUA:10 a=2HcVojCoY74_Cgs4:21 X-Telus-Outbound-IP: 154.20.1.203 Received: from estone.ca ([192.168.1.253] helo=mail.estone.ca) by estone.ca with esmtp (Exim 4.80) (envelope-from ) id 1U3UFH-0001AU-Vd for xen-users@lists.xen.org; Thu, 07 Feb 2013 08:22:44 -0800 Message-id: X-FC-Thread-ID: 00000001-e6699230 Date: Thu, 07 Feb 2013 08:21:26 -0800 X-Mailer: FirstClass 11.1 (build 11.128) X-FC-SERVER-TZ: 6554336 To: xen-users@lists.xen.org From: "Mike Egglestone" MIME-Version: 1.0 Subject: [Xen-users] need advise with a redhat 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="===============5953819433822635573==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org This is a multi-part message in MIME format. --===============5953819433822635573== Content-Type: multipart/alternative; boundary="--=_--e6699238.e6699230.cd398506" This is a multi-part message in MIME format. ----=_--e6699238.e6699230.cd398506 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Hello, I have xen dom0 running on Debian with a RedHat 5.4 domU. (under HVM) Its working, but performance is crappy. I think I need to get PV drivers in the RH kernel, or flip this to a PV domU? The RH kernel is 2.6.18, which doesn't come stock with PV drivers. Any suggestions on how to get his domU up to snuff? Thanks! ----=_--e6699238.e6699230.cd398506 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable <=21DOCTYPE HTML PUBLIC =22-//W3C//DTD HTML 4.0 Transitional//EN=22>
Hello,

I have xen dom0 running on Debian wit= h a RedHat 5.4 domU. (under HVM)
Its working, but performance is crapp= y.

I think I need to get PV drivers in t= he RH kernel, or flip this to a PV domU?
The RH kernel is 2.6.18, which doesn'= t come stock with PV drivers.

Any suggestions on how to get his dom= U up to snuff?

Thanks=21


----=_--e6699238.e6699230.cd398506-- --===============5953819433822635573== 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 --===============5953819433822635573==-- From xen-users-bounces@lists.xen.org Thu Feb 07 16:23:54 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 07 Feb 2013 16: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 1U3UFZ-0004SB-95; Thu, 07 Feb 2013 16:23:01 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U3UFX-0004Ry-Ip for xen-users@lists.xen.org; Thu, 07 Feb 2013 16:22:59 +0000 Received: from [85.158.139.211:53375] by server-6.bemta-5.messagelabs.com id BD/47-01489-2E4D3115; Thu, 07 Feb 2013 16:22:58 +0000 X-Env-Sender: mike@estone.ca X-Msg-Ref: server-12.tower-206.messagelabs.com!1360254164!18800186!1 X-Originating-IP: [199.185.220.80] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogMTk5LjE4NS4yMjAuODAgPT4gMjc2ODEx\n X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 12899 invoked from network); 7 Feb 2013 16:22:44 -0000 Received: from defout.telus.net (HELO outbound03.telus.net) (199.185.220.80) by server-12.tower-206.messagelabs.com with SMTP; 7 Feb 2013 16:22:44 -0000 Received: from edtncm02 ([199.185.220.224]) by priv-edtnes29.telusplanet.net (InterMail vM.8.01.03.00 201-2260-125-20100507) with ESMTP id <20130207162243.VEQQ12187.priv-edtnes29.telusplanet.net@edtncm02> for ; Thu, 7 Feb 2013 09:22:43 -0700 Received: from estone.ca ([154.20.1.203]) by edtncm02 with bizsmtp id xUNe1k00g4NnoEJ01UNfVB; Thu, 07 Feb 2013 09:22:42 -0700 X-Authority-Analysis: v=1.1 cv=SUDmmYpofWFcHskeL6GXKlG83HAHnN0LLSyWvxHysSM= c=1 sm=2 a=HXLQNss8UggA:10 a=d9BVEMumb3ZhJ1jenVoA:9 a=QEXdDO2ut3YA:10 a=SSmOFEACAAAA:8 a=iArNVvhu2_IA:10 a=zJJgJrR4LD4A:10 a=frz4AuCg-hUA:10 a=2HcVojCoY74_Cgs4:21 X-Telus-Outbound-IP: 154.20.1.203 Received: from estone.ca ([192.168.1.253] helo=mail.estone.ca) by estone.ca with esmtp (Exim 4.80) (envelope-from ) id 1U3UFH-0001AU-Vd for xen-users@lists.xen.org; Thu, 07 Feb 2013 08:22:44 -0800 Message-id: X-FC-Thread-ID: 00000001-e6699230 Date: Thu, 07 Feb 2013 08:21:26 -0800 X-Mailer: FirstClass 11.1 (build 11.128) X-FC-SERVER-TZ: 6554336 To: xen-users@lists.xen.org From: "Mike Egglestone" MIME-Version: 1.0 Subject: [Xen-users] need advise with a redhat 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="===============5953819433822635573==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org This is a multi-part message in MIME format. --===============5953819433822635573== Content-Type: multipart/alternative; boundary="--=_--e6699238.e6699230.cd398506" This is a multi-part message in MIME format. ----=_--e6699238.e6699230.cd398506 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Hello, I have xen dom0 running on Debian with a RedHat 5.4 domU. (under HVM) Its working, but performance is crappy. I think I need to get PV drivers in the RH kernel, or flip this to a PV domU? The RH kernel is 2.6.18, which doesn't come stock with PV drivers. Any suggestions on how to get his domU up to snuff? Thanks! ----=_--e6699238.e6699230.cd398506 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable <=21DOCTYPE HTML PUBLIC =22-//W3C//DTD HTML 4.0 Transitional//EN=22>
Hello,

I have xen dom0 running on Debian wit= h a RedHat 5.4 domU. (under HVM)
Its working, but performance is crapp= y.

I think I need to get PV drivers in t= he RH kernel, or flip this to a PV domU?
The RH kernel is 2.6.18, which doesn'= t come stock with PV drivers.

Any suggestions on how to get his dom= U up to snuff?

Thanks=21


----=_--e6699238.e6699230.cd398506-- --===============5953819433822635573== 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 --===============5953819433822635573==-- From xen-users-bounces@lists.xen.org Thu Feb 07 17:40:13 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 07 Feb 2013 17:40: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 1U3VRI-0001ry-RM; Thu, 07 Feb 2013 17:39:12 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U3VRH-0001rp-6n for xen-users@lists.xen.org; Thu, 07 Feb 2013 17:39:11 +0000 Received: from [193.109.254.147:53360] by server-7.bemta-14.messagelabs.com id 7A/01-13581-EB6E3115; Thu, 07 Feb 2013 17:39:10 +0000 X-Env-Sender: peter.gansterer@paradigma.net X-Msg-Ref: server-9.tower-27.messagelabs.com!1360258749!9912134!1 X-Originating-IP: [213.47.215.227] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 27331 invoked from network); 7 Feb 2013 17:39:09 -0000 Received: from majere.luchs.at (HELO majere.luchs.at) (213.47.215.227) by server-9.tower-27.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 7 Feb 2013 17:39:09 -0000 Received: from localhost (localhost [127.0.0.1]) by majere.luchs.at (Postfix) with ESMTP id 8EE57D007E25 for ; Thu, 7 Feb 2013 18:39:08 +0100 (CET) X-Virus-Scanned: by majere.luchs.at Received: from majere.luchs.at ([127.0.0.1]) by localhost (majere.luchs.at [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Zb1A+-DqDgbX for ; Thu, 7 Feb 2013 18:39:07 +0100 (CET) Received: from earth (earth.elements.lan [10.0.0.2]) by majere.luchs.at (Postfix) with ESMTP id 77708D007E23 for ; Thu, 7 Feb 2013 18:39:07 +0100 (CET) Received: from pedos (pedos.elements.lan [10.0.0.108]) by earth (Postfix) with SMTP id BBACF7840 for ; Thu, 7 Feb 2013 18:39:05 +0100 (CET) Received: by pedos (sSMTP sendmail emulation); Thu, 07 Feb 2013 18:37:17 +0100 Content-Disposition: inline MIME-Version: 1.0 X-Mailer: MIME-tools 5.503 (Entity 5.503) Message-ID: <1360255718.EBA4d10.2491@pedos> From: "Peter Gansterer" Date: Thu, 07 Feb 2013 18:37:16 +0100 To: "xen-users" Subject: [Xen-users] "dynamic memory allocation" for windows guests? X-BeenThere: xen-users@lists.xen.org X-Mailman-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 SGVsbG8sCgpJbiBvdXIgb2ZmaWNlIHdlIHdvdWxkIGxpa2UgdG8gZG8gc29tZXRoaW5nIGxpa2Ug Im1lbW9yeSBvdmVyY29tbWl0bWVudCIgb3IgcmF0aGVyICJkeW5hbWljIGFsbG9jYXRpb24iIGZv ciBhIGJ1bmNoIG9mIHdpbmRvd3MgZG9tVXMgKHNlcnZlciAyMDAzICYgMjAwOCkuCgpXZSB0aG91 Z2h0IHRoaXMgc2hvdWxkIGJlIGEgc2ltcGxlIGZlYXR1cmUsIGhvd2V2ZXIgd2UgZGlkIG5vdCBm aW5kIGFueSBmaXR0aW5nIHNvbHV0aW9uLgpXZSB1c2UgWGVuIDQuMi4xIHdpdGggeGwgdG9vbHN0 YWNrLgoKVGhlIGlkZWEgaXMgdG8gdXNlIGJhbGxvb25pbmcgdG8gZHluYW1pY2FsbHkgKGFuZCBh dXRvbWF0aWNhbGx5KSBjaGFuZ2UgcGh5c2ljYWwgbWVtb3J5IGF2YWlsYWJsZSB0byB0aGUgZG9t VXMgYWNjb3JkaW5nIHRvIHRoZWlyIG1lbW9yeSBuZWVkcy4KVGhlcmUgd2FzIHNvbWV0aGluZyBj YWxsZWQgInhlbmJhbGxvb25kIiBmb3IgbGludXggZ3Vlc3RzIGJlZm9yZSAidG1lbSIgd2FzIGlu dGVncmF0ZWQsIGFuZCB0aGlzIHNlZW1zIHRvIGJlIGV4YWN0bHkgd2hhdCB3ZSdyZSBsb29raW5n IGZvciwgZXhjZXB0IHRoYXQgd2UgbmVlZCBpdCBmb3Igd2luZG93cyBkb21Vcy4KCklzIHRoZXJl IHJlYWxseSBubyBzdWNoIHRoaW5nIGZvciB3aW5kb3dzIGd1ZXN0cywgb3IgYXJlIHdlIGp1c3Qg dG9vIHN0dXBpZCB0byBmaW5kIGl0PwpXZSB3b3VsZCBiZSBoYXBweSBhYm91dCBhbnkgaGludHMu CgpJZiB0aGVyZSByZWFsbHkgaXMgbm9uZSwgdGhlbiwgaXMgdGhlcmUgYSByZWFzb24gZm9yIHRo YXQ/CgpJdCBzZWVtcyBsaWtlIGEgc2ltcGxlIHRoaW5nOgotIHN0YXJ0IGEgcHJvY2VzcyBvbiBl YWNoIHdpbmRvd3MgZ3Vlc3QgdG8gbW9uaXRvciBtZW1vcnkgdXNhZ2UKLSBpZiB0aGVyZSBpcyBz cGFyZSBtZW1vcnkgLT4gdGVsbCB0aGUgaHlwZXJ2aXNvciB0byBsb3dlciB0aGUgbWVtLXRhcmdl dAotIGlmIG1lbW9yeSBpcyB1c2VkIHVwLCBkZWNpZGUgdXBvbiBDUFUgdXNhZ2UgYW5kIG1lbSBo aXN0b3J5OgogIC4gaWRsZSBmb3Igc29tZSB0aW1lIC0+IHRyeSB0byBmcmVlIGJ1ZmZlcnMgYnkg YWxsb2NhdGluZyBhbmQgZnJlZWluZyBibG9ja3MKICAuIGxvYWRlZCAtPiBkbyBub3RoaW5nIG9y IGluY3JlYXNlIG1lbS10YXJnZXQsIGFjY29yZGluZyB0byBwYWdlZmlsZSB1c2FnZQogIC4gcmVj ZW50bHkgaW5jcmVhc2VkIC0+IGluY3JlYXNlIG1lbS10YXJnZXQKLSBJZiBtZW1vcnkgaXMgbmVl ZGVkIHF1aWNrbHksIHRoZSBwYWdlZmlsZSB3aWxsIGJlIHVzZWQgdGVtcG9yYXJpbHkuCi0gSW4g YSB0cml2aWFsIGltcGxlbWVudGF0aW9uLCBhIHNpbXBsZSBzY3JpcHQgb24gZG9tMCBjb3VsZCBy ZWNlaXZlCiAgdGhlIG1lbS10YXJnZXQgcmVxdWVzdHMgYW5kIGRvIHRoZSBhY3R1YWwgInhsIG1l bS1zZXQiIGNhbGxzCiAgKGFjY29yZGluZyB0byBzb21lIGJhbGFuY2luZyBhbGdvcml0aG0pLgoK T3IgaXMgdGhpcyBhcHByb2FjaCBqdXN0IHRvbyBuYWl2ZT8KCkluIG91ciBzY2VuYXJpbyAodmly dHVhbCBkZXNrdG9wcyBhbmQgdGVzdHNlcnZlcnMpIHRoZXJlIGFyZSBhbHdheXMgaWRsZSBndWVz dHMgd2FzdGluZyBtZW1vcnkgYW5kIG5vdCByZWFsbHkgdXNpbmcgaXQuIEkgc3VwcG9zZSB0aGVy ZSBtdXN0IGJlIGEgd2F5IHRvIGF1dG9tYXRpY2FsbHkgKGlmIGp1c3Qgc2xvd2x5KSBzaGlmdCBt ZW1vcnkgdG8gdGhvc2UgaW4gbmVlZCwgYW5kIHRodXMgcmVkdWNpbmcgb3ZlcmFsbCBtZW1vcnkg cmVxdWlyZW1lbnRzLgoKeW91cnMsCi0gcGV0ZXIuCgotLSAKUGV0ZXIgR2Fuc3RlcmVyCgpQQVJB RElHTUEgVW50ZXJuZWhtZW5zYmVyYXR1bmcgR21iSApNYXJpYWhpbGZlcnN0cmHDn2UgNDcvMS8z CkEtMTA2MCBXaWVuClRlbDogMDA0My0oMCkxLTU4NSA0OSA3MgpodHRwOi8vd3d3LnBhcmFkaWdt YS5uZXQKCkZpcm1lbmJ1Y2hudW1tZXI6IEZOIDEzNDU2NCBwClJlY2h0c2Zvcm06IEdtYkgKRmly bWVuYnVjaGdlcmljaHQ6IEhhbmRlbHNnZXJpY2h0IFdpZW4KCl9fX19fX19fX19fX19fX19fX19f X19fX19fX19fX19fX19fX19fX19fX19fX19fClhlbi11c2VycyBtYWlsaW5nIGxpc3QKWGVuLXVz ZXJzQGxpc3RzLnhlbi5vcmcKaHR0cDovL2xpc3RzLnhlbi5vcmcveGVuLXVzZXJz From xen-users-bounces@lists.xen.org Thu Feb 07 17:40:13 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 07 Feb 2013 17:40: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 1U3VRI-0001ry-RM; Thu, 07 Feb 2013 17:39:12 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U3VRH-0001rp-6n for xen-users@lists.xen.org; Thu, 07 Feb 2013 17:39:11 +0000 Received: from [193.109.254.147:53360] by server-7.bemta-14.messagelabs.com id 7A/01-13581-EB6E3115; Thu, 07 Feb 2013 17:39:10 +0000 X-Env-Sender: peter.gansterer@paradigma.net X-Msg-Ref: server-9.tower-27.messagelabs.com!1360258749!9912134!1 X-Originating-IP: [213.47.215.227] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 27331 invoked from network); 7 Feb 2013 17:39:09 -0000 Received: from majere.luchs.at (HELO majere.luchs.at) (213.47.215.227) by server-9.tower-27.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 7 Feb 2013 17:39:09 -0000 Received: from localhost (localhost [127.0.0.1]) by majere.luchs.at (Postfix) with ESMTP id 8EE57D007E25 for ; Thu, 7 Feb 2013 18:39:08 +0100 (CET) X-Virus-Scanned: by majere.luchs.at Received: from majere.luchs.at ([127.0.0.1]) by localhost (majere.luchs.at [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Zb1A+-DqDgbX for ; Thu, 7 Feb 2013 18:39:07 +0100 (CET) Received: from earth (earth.elements.lan [10.0.0.2]) by majere.luchs.at (Postfix) with ESMTP id 77708D007E23 for ; Thu, 7 Feb 2013 18:39:07 +0100 (CET) Received: from pedos (pedos.elements.lan [10.0.0.108]) by earth (Postfix) with SMTP id BBACF7840 for ; Thu, 7 Feb 2013 18:39:05 +0100 (CET) Received: by pedos (sSMTP sendmail emulation); Thu, 07 Feb 2013 18:37:17 +0100 Content-Disposition: inline MIME-Version: 1.0 X-Mailer: MIME-tools 5.503 (Entity 5.503) Message-ID: <1360255718.EBA4d10.2491@pedos> From: "Peter Gansterer" Date: Thu, 07 Feb 2013 18:37:16 +0100 To: "xen-users" Subject: [Xen-users] "dynamic memory allocation" for windows guests? X-BeenThere: xen-users@lists.xen.org X-Mailman-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 SGVsbG8sCgpJbiBvdXIgb2ZmaWNlIHdlIHdvdWxkIGxpa2UgdG8gZG8gc29tZXRoaW5nIGxpa2Ug Im1lbW9yeSBvdmVyY29tbWl0bWVudCIgb3IgcmF0aGVyICJkeW5hbWljIGFsbG9jYXRpb24iIGZv ciBhIGJ1bmNoIG9mIHdpbmRvd3MgZG9tVXMgKHNlcnZlciAyMDAzICYgMjAwOCkuCgpXZSB0aG91 Z2h0IHRoaXMgc2hvdWxkIGJlIGEgc2ltcGxlIGZlYXR1cmUsIGhvd2V2ZXIgd2UgZGlkIG5vdCBm aW5kIGFueSBmaXR0aW5nIHNvbHV0aW9uLgpXZSB1c2UgWGVuIDQuMi4xIHdpdGggeGwgdG9vbHN0 YWNrLgoKVGhlIGlkZWEgaXMgdG8gdXNlIGJhbGxvb25pbmcgdG8gZHluYW1pY2FsbHkgKGFuZCBh dXRvbWF0aWNhbGx5KSBjaGFuZ2UgcGh5c2ljYWwgbWVtb3J5IGF2YWlsYWJsZSB0byB0aGUgZG9t VXMgYWNjb3JkaW5nIHRvIHRoZWlyIG1lbW9yeSBuZWVkcy4KVGhlcmUgd2FzIHNvbWV0aGluZyBj YWxsZWQgInhlbmJhbGxvb25kIiBmb3IgbGludXggZ3Vlc3RzIGJlZm9yZSAidG1lbSIgd2FzIGlu dGVncmF0ZWQsIGFuZCB0aGlzIHNlZW1zIHRvIGJlIGV4YWN0bHkgd2hhdCB3ZSdyZSBsb29raW5n IGZvciwgZXhjZXB0IHRoYXQgd2UgbmVlZCBpdCBmb3Igd2luZG93cyBkb21Vcy4KCklzIHRoZXJl IHJlYWxseSBubyBzdWNoIHRoaW5nIGZvciB3aW5kb3dzIGd1ZXN0cywgb3IgYXJlIHdlIGp1c3Qg dG9vIHN0dXBpZCB0byBmaW5kIGl0PwpXZSB3b3VsZCBiZSBoYXBweSBhYm91dCBhbnkgaGludHMu CgpJZiB0aGVyZSByZWFsbHkgaXMgbm9uZSwgdGhlbiwgaXMgdGhlcmUgYSByZWFzb24gZm9yIHRo YXQ/CgpJdCBzZWVtcyBsaWtlIGEgc2ltcGxlIHRoaW5nOgotIHN0YXJ0IGEgcHJvY2VzcyBvbiBl YWNoIHdpbmRvd3MgZ3Vlc3QgdG8gbW9uaXRvciBtZW1vcnkgdXNhZ2UKLSBpZiB0aGVyZSBpcyBz cGFyZSBtZW1vcnkgLT4gdGVsbCB0aGUgaHlwZXJ2aXNvciB0byBsb3dlciB0aGUgbWVtLXRhcmdl dAotIGlmIG1lbW9yeSBpcyB1c2VkIHVwLCBkZWNpZGUgdXBvbiBDUFUgdXNhZ2UgYW5kIG1lbSBo aXN0b3J5OgogIC4gaWRsZSBmb3Igc29tZSB0aW1lIC0+IHRyeSB0byBmcmVlIGJ1ZmZlcnMgYnkg YWxsb2NhdGluZyBhbmQgZnJlZWluZyBibG9ja3MKICAuIGxvYWRlZCAtPiBkbyBub3RoaW5nIG9y IGluY3JlYXNlIG1lbS10YXJnZXQsIGFjY29yZGluZyB0byBwYWdlZmlsZSB1c2FnZQogIC4gcmVj ZW50bHkgaW5jcmVhc2VkIC0+IGluY3JlYXNlIG1lbS10YXJnZXQKLSBJZiBtZW1vcnkgaXMgbmVl ZGVkIHF1aWNrbHksIHRoZSBwYWdlZmlsZSB3aWxsIGJlIHVzZWQgdGVtcG9yYXJpbHkuCi0gSW4g YSB0cml2aWFsIGltcGxlbWVudGF0aW9uLCBhIHNpbXBsZSBzY3JpcHQgb24gZG9tMCBjb3VsZCBy ZWNlaXZlCiAgdGhlIG1lbS10YXJnZXQgcmVxdWVzdHMgYW5kIGRvIHRoZSBhY3R1YWwgInhsIG1l bS1zZXQiIGNhbGxzCiAgKGFjY29yZGluZyB0byBzb21lIGJhbGFuY2luZyBhbGdvcml0aG0pLgoK T3IgaXMgdGhpcyBhcHByb2FjaCBqdXN0IHRvbyBuYWl2ZT8KCkluIG91ciBzY2VuYXJpbyAodmly dHVhbCBkZXNrdG9wcyBhbmQgdGVzdHNlcnZlcnMpIHRoZXJlIGFyZSBhbHdheXMgaWRsZSBndWVz dHMgd2FzdGluZyBtZW1vcnkgYW5kIG5vdCByZWFsbHkgdXNpbmcgaXQuIEkgc3VwcG9zZSB0aGVy ZSBtdXN0IGJlIGEgd2F5IHRvIGF1dG9tYXRpY2FsbHkgKGlmIGp1c3Qgc2xvd2x5KSBzaGlmdCBt ZW1vcnkgdG8gdGhvc2UgaW4gbmVlZCwgYW5kIHRodXMgcmVkdWNpbmcgb3ZlcmFsbCBtZW1vcnkg cmVxdWlyZW1lbnRzLgoKeW91cnMsCi0gcGV0ZXIuCgotLSAKUGV0ZXIgR2Fuc3RlcmVyCgpQQVJB RElHTUEgVW50ZXJuZWhtZW5zYmVyYXR1bmcgR21iSApNYXJpYWhpbGZlcnN0cmHDn2UgNDcvMS8z CkEtMTA2MCBXaWVuClRlbDogMDA0My0oMCkxLTU4NSA0OSA3MgpodHRwOi8vd3d3LnBhcmFkaWdt YS5uZXQKCkZpcm1lbmJ1Y2hudW1tZXI6IEZOIDEzNDU2NCBwClJlY2h0c2Zvcm06IEdtYkgKRmly bWVuYnVjaGdlcmljaHQ6IEhhbmRlbHNnZXJpY2h0IFdpZW4KCl9fX19fX19fX19fX19fX19fX19f X19fX19fX19fX19fX19fX19fX19fX19fX19fClhlbi11c2VycyBtYWlsaW5nIGxpc3QKWGVuLXVz ZXJzQGxpc3RzLnhlbi5vcmcKaHR0cDovL2xpc3RzLnhlbi5vcmcveGVuLXVzZXJz From xen-users-bounces@lists.xen.org Thu Feb 07 19:16:25 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 07 Feb 2013 19:16: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 1U3Ww8-0005jB-Mz; Thu, 07 Feb 2013 19:15:08 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U3Ww7-0005j3-AP for xen-users@lists.xen.org; Thu, 07 Feb 2013 19:15:07 +0000 Received: from [85.158.139.211:60324] by server-8.bemta-5.messagelabs.com id E6/F8-19075-A3DF3115; Thu, 07 Feb 2013 19:15:06 +0000 X-Env-Sender: matthias.kannenberg@googlemail.com X-Msg-Ref: server-8.tower-206.messagelabs.com!1360264504!21546835!1 X-Originating-IP: [209.85.212.179] X-SpamReason: No, hits=0.3 required=7.0 tests=HTML_MESSAGE,RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 7493 invoked from network); 7 Feb 2013 19:15:04 -0000 Received: from mail-wi0-f179.google.com (HELO mail-wi0-f179.google.com) (209.85.212.179) by server-8.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 7 Feb 2013 19:15:04 -0000 Received: by mail-wi0-f179.google.com with SMTP id ez12so3350851wid.6 for ; Thu, 07 Feb 2013 11:15:04 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=20120113; h=x-received:mime-version:from:date:message-id:subject:to :content-type; bh=OPEhsXZAelCU4DqKFDqH8ENnqaVbYxdGxv6MuiPHctg=; b=w7K7XLVQsLhQVjHMBEHpdnvAN4yd05z8nWjIb9R9Tu6Dw1yUnLJlYJ7lEfKQani3g1 RUGqhUhoP+5GmH+Kic285LadXAecrwNICqoR/b3E2pBY6ksV3hCWjo4i4CJUl2wqGqnd WwcoV5D3lJEpDmh/mrJ/4DI20vsAiu/qJO7+JueEsUXFNDktRbIN/yCE0vPBpLSHxUYS I9I24bFfDTifVG1kVy2E1mWodxi9m2WqXwboi03+0Muwt+nh8o8o3XN7JwL+LpP5zEuM B6feI+WedCjxuwnhx5AfoPKSZYLdacc3taoFg97y8B+b4KTMWcD+8UeyxKn2AIbbj4GV 1UfQ== X-Received: by 10.180.100.163 with SMTP id ez3mr4917002wib.32.1360264504494; Thu, 07 Feb 2013 11:15:04 -0800 (PST) MIME-Version: 1.0 Received: by 10.194.80.68 with HTTP; Thu, 7 Feb 2013 11:14:44 -0800 (PST) From: Matthias Date: Thu, 7 Feb 2013 20:14:44 +0100 Message-ID: To: xen-users@lists.xen.org Content-Type: multipart/mixed; boundary=f46d0444edff974bfa04d527420a Subject: [Xen-users] ATI/AMDs atikmpag.sys BSOD while 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: , Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --f46d0444edff974bfa04d527420a Content-Type: text/plain; charset=ISO-8859-1 Hi everyone since I'm currently migrating from xm to xl and now are also a victim of the said error, I started researching on it and found that many people had the issue but not many found solution and behind this BSOD (=Bluescreen of Death), there are actually multiple errors in hiding. What I would like to do is gather as much info as possible in this thread to form a kind of comprehensive guide to fixing this issue. >From what i gathered so far, there are at least 3 different problems with the same symptopms. 1) Situation: After booting the dom0 and booting a windows domU with an ATI/AMD Card, Windows generally works fine, but after rebooting the system, or shutting down / restarting, the Bluescreen occurs or the performance massively below normal. Error: Most likely this is cause the Card is not properly resetted (no FLR [function level reset] ) Solution: If the domU reboots into BSOD, you are screwed and have to reboot the dom0. If it only degrades performance, eject the card and reinitialize to perform a manual reset. Or use the xm toolkit. Status: Don't know if it is fixed yet Source: http://lists.xen.org/archives/html/xen-users/2012-02/msg00443.html , http://wiki.xen.org/wiki/Talk:Xen_VGA_Passthrough_Tested_Adapters 2) Situation: Booting a windows domU results in a BSOD when the CCC (=Catalyst Control Center) installed. Error: The CCC tries to set some specific settings (most likely performance tweaks) within the driver which the driver can't pass to the vga through passthrough mode. Result is a BSOD. Solution: Deinstall the CCC in windows safe mode. The driver itself works without it pretty fine. Status: Don't know if it is fixed yet Source: http://lists.xen.org/archives/html/xen-users/2012-03/msg00617.html Note: I don't really know if this holds for the Vision Engine Control center, too. the VECC is basically the same as the CCC, so i assume it does. I simply haven't found any things referencing it. 3) Situation: This is actually the issue I have. Things seem a lot more random then the other ones. A BSOD happens basically in 80% of booting the Windows domU. Which means, after rebooting dom0, it mostly works. Rebooting or shutting down / starting the domU works sometimes (Once i achieved 6 consecutive reboots or shutdowns / starts before the BSOD happened) but after I get one Bluescreen, almost never (I can't exactly remember if really 'never') comes up again. Of course I tried the above solutions but this didn't helped me. I also tried different different versions of the Catalyst driver (from 12/1 to 13/1) and current releases of xen-4.2-testing and xen-unsable. As I said, this is when using the xl toolkit. I never had this issues using xm. I thought this might belinked to me passing other PCI devices in addition (I'm passing some USB controller to the domU) but even deactivating them didn't help. What I actually found helping boosting the success rate (but not solving the overall issue) is deinstalling all VGA-Related AMD Driver. Windows then runs on it's own VGA-Driver (the graphic card is currectly identified and this is an actual ati driver, so I'm not talking about some generic standard vga driver. I don't know where is driver is coming from). I've attached an analysis file i've gethered from the bluescreen crash dump. I created it using BluescreenView. This is more for currectly identifieng the different BSODs, I guess. Some Infos: Kernel: 3.7.4 kernel.org kernel without patches Xen: latest xen-unstable (but also tested with xen-4.2-testing) Processor: AMD Phenom 1090T Mainboard: Asus Crossfire IV VGA: Radeon HD5700 and Radeon HD5450 Driver: Currently running Catalyst 13/1 but tested nearly everything between 12/1 and 13/1 Error: Don't know yet Solution: Don't know yet Status: unsolved Source: Okay, so basically that's the story. It would be great if some people can complete and extend the list. Especially some who already fixed the issue on their side. (And of course it would be great if someone has an idea for my problem). Thanks --f46d0444edff974bfa04d527420a Content-Type: text/html; charset=UTF-16LE; name="BSOD_info.htm" Content-Disposition: attachment; filename="BSOD_info.htm" Content-Transfer-Encoding: base64 X-Attachment-Id: f_hcwa9fgu0 //48ACEARABPAEMAVABZAFAARQAgAGgAdABtAGwAIABQAFUAQgBMAEkAQwAgACIALQAvAC8AVwAz AEMALwAvAEQAVABEACAASABUAE0ATAAgADMALgAyACAARgBpAG4AYQBsAC8ALwBFAE4AIgA+AA0A CgA8AGgAdABtAGwAPgA8AGgAZQBhAGQAPgANAAoAPABtAGUAdABhACAAaAB0AHQAcAAtAGUAcQB1 AGkAdgA9ACIAYwBvAG4AdABlAG4AdAAtAHQAeQBwAGUAIgAgAGMAbwBuAHQAZQBuAHQAPQAiAHQA ZQB4AHQALwBoAHQAbQBsADsAIABjAGgAYQByAHMAZQB0AD0AVQBUAEYALQAxADYAIgA+ADwAdABp AHQAbABlAD4AQwByAGEAcwBoACAATABpAHMAdAA8AC8AdABpAHQAbABlAD4APAAvAGgAZQBhAGQA PgANAAoAPABiAG8AZAB5AD4ADQAKACAAPABoADMAPgBHAGUAbgBlAHIAYQBsACAAaQBuAGYAbwBy AG0AYQB0AGkAbwBuACAAYQBiAG8AdQB0ACAAQgBTAE8ARAA8AC8AaAAzAD4ADQAKACAAPAB0AGEA YgBsAGUAIABiAG8AcgBkAGUAcgA9ACIAMQAiACAAYwBlAGwAbABwAGEAZABkAGkAbgBnAD0AIgA1 ACIAPgA8AHQAYgBvAGQAeQA+ADwAdAByACAAYgBnAGMAbwBsAG8AcgA9ACIARQAwAEUAMABFADAA IgA+AA0ACgA8AHQAaAA+AEQAdQBtAHAAIABGAGkAbABlAA0ACgA8AC8AdABoAD4APAB0AGgAPgBD AHIAYQBzAGgAIABUAGkAbQBlAA0ACgA8AC8AdABoAD4APAB0AGgAPgBCAHUAZwAgAEMAaABlAGMA awAgAFMAdAByAGkAbgBnAA0ACgA8AC8AdABoAD4APAB0AGgAPgBCAHUAZwAgAEMAaABlAGMAawAg AEMAbwBkAGUADQAKADwALwB0AGgAPgA8AHQAaAA+AFAAYQByAGEAbQBlAHQAZQByACAAMQANAAoA PAAvAHQAaAA+ADwAdABoAD4AUABhAHIAYQBtAGUAdABlAHIAIAAyAA0ACgA8AC8AdABoAD4APAB0 AGgAPgBQAGEAcgBhAG0AZQB0AGUAcgAgADMADQAKADwALwB0AGgAPgA8AHQAaAA+AFAAYQByAGEA bQBlAHQAZQByACAANAANAAoAPAAvAHQAaAA+ADwAdABoAD4AQwBhAHUAcwBlAGQAIABCAHkAIABE AHIAaQB2AGUAcgANAAoAPAAvAHQAaAA+ADwAdABoAD4AQwBhAHUAcwBlAGQAIABCAHkAIABBAGQA ZAByAGUAcwBzAA0ACgA8AC8AdABoAD4APAB0AGgAPgBGAGkAbABlACAARABlAHMAYwByAGkAcAB0 AGkAbwBuAA0ACgA8AC8AdABoAD4APAB0AGgAPgBQAHIAbwBkAHUAYwB0ACAATgBhAG0AZQANAAoA PAAvAHQAaAA+ADwAdABoAD4AQwBvAG0AcABhAG4AeQANAAoAPAAvAHQAaAA+ADwAdABoAD4ARgBp AGwAZQAgAFYAZQByAHMAaQBvAG4ADQAKADwALwB0AGgAPgA8AHQAaAA+AFAAcgBvAGMAZQBzAHMA bwByAA0ACgA8AC8AdABoAD4APAB0AGgAPgBDAHIAYQBzAGgAIABBAGQAZAByAGUAcwBzAA0ACgA8 AC8AdABoAD4APAB0AGgAPgBTAHQAYQBjAGsAIABBAGQAZAByAGUAcwBzACAAMQANAAoAPAAvAHQA aAA+ADwAdABoAD4AUwB0AGEAYwBrACAAQQBkAGQAcgBlAHMAcwAgADIADQAKADwALwB0AGgAPgA8 AHQAaAA+AFMAdABhAGMAawAgAEEAZABkAHIAZQBzAHMAIAAzAA0ACgA8AC8AdABoAD4APAB0AGgA PgBDAG8AbQBwAHUAdABlAHIAIABOAGEAbQBlAA0ACgA8AC8AdABoAD4APAB0AGgAPgBGAHUAbABs ACAAUABhAHQAaAANAAoAPAAvAHQAaAA+ADwAdABoAD4AUAByAG8AYwBlAHMAcwBvAHIAcwAgAEMA bwB1AG4AdAANAAoAPAAvAHQAaAA+ADwAdABoAD4ATQBhAGoAbwByACAAVgBlAHIAcwBpAG8AbgAN AAoAPAAvAHQAaAA+ADwAdABoAD4ATQBpAG4AbwByACAAVgBlAHIAcwBpAG8AbgANAAoAPAAvAHQA aAA+ADwAdABoAD4ARAB1AG0AcAAgAEYAaQBsAGUAIABTAGkAegBlAA0ACgA8AC8AdABoAD4APAAv AHQAcgA+ADwAdAByAD4APAB0AGQAIABiAGcAYwBvAGwAbwByAD0AIgAjAEYARgBGAEYARgBGACIA IABuAG8AdwByAGEAcAA9ACIAbgBvAHcAcgBhAHAAIgA+ADAAMgAwADUAMQAzAC0ANQA1ADIANQA1 AC0AMAAxAC4AZABtAHAAPAAvAHQAZAA+ADwAdABkACAAYgBnAGMAbwBsAG8AcgA9ACIAIwBGAEYA RgBGAEYARgAiACAAbgBvAHcAcgBhAHAAPQAiAG4AbwB3AHIAYQBwACIAPgAwADUALgAwADIALgAy ADAAMQAzACAAMAAyADoAMAA2ADoAMgA2ADwALwB0AGQAPgA8AHQAZAAgAGIAZwBjAG8AbABvAHIA PQAiACMARgBGAEYARgBGAEYAIgAgAG4AbwB3AHIAYQBwAD0AIgBuAG8AdwByAGEAcAAiAD4AJgBu AGIAcwBwADsAPAAvAHQAZAA+ADwAdABkACAAYgBnAGMAbwBsAG8AcgA9ACIAIwBGAEYARgBGAEYA RgAiACAAbgBvAHcAcgBhAHAAPQAiAG4AbwB3AHIAYQBwACIAPgAwAHgAMAAwADAAMAAwADEAMQA2 ADwALwB0AGQAPgA8AHQAZAAgAGIAZwBjAG8AbABvAHIAPQAiACMARgBGAEYARgBGAEYAIgAgAG4A bwB3AHIAYQBwAD0AIgBuAG8AdwByAGEAcAAiAD4AZgBmAGYAZgBmAGEAOAAwAGAAMAA4ADMAMgA4 ADAAMQAwADwALwB0AGQAPgA8AHQAZAAgAGIAZwBjAG8AbABvAHIAPQAiACMARgBGAEYARgBGAEYA IgAgAG4AbwB3AHIAYQBwAD0AIgBuAG8AdwByAGEAcAAiAD4AZgBmAGYAZgBmADgAOAAwAGAAMAA0 ADYAYQA4AGQAYgA4ADwALwB0AGQAPgA8AHQAZAAgAGIAZwBjAG8AbABvAHIAPQAiACMARgBGAEYA RgBGAEYAIgAgAG4AbwB3AHIAYQBwAD0AIgBuAG8AdwByAGEAcAAiAD4AMAAwADAAMAAwADAAMAAw AGAAMAAwADAAMAAwADAAMAAwADwALwB0AGQAPgA8AHQAZAAgAGIAZwBjAG8AbABvAHIAPQAiACMA RgBGAEYARgBGAEYAIgAgAG4AbwB3AHIAYQBwAD0AIgBuAG8AdwByAGEAcAAiAD4AMAAwADAAMAAw ADAAMAAwAGAAMAAwADAAMAAwADAAMAAyADwALwB0AGQAPgA8AHQAZAAgAGIAZwBjAG8AbABvAHIA PQAiACMARgBGAEYARgBGAEYAIgAgAG4AbwB3AHIAYQBwAD0AIgBuAG8AdwByAGEAcAAiAD4AZAB4 AGcAawByAG4AbAAuAHMAeQBzADwALwB0AGQAPgA8AHQAZAAgAGIAZwBjAG8AbABvAHIAPQAiACMA RgBGAEYARgBGAEYAIgAgAG4AbwB3AHIAYQBwAD0AIgBuAG8AdwByAGEAcAAiAD4AZAB4AGcAawBy AG4AbAAuAHMAeQBzACsANQBkADAAMAAwADwALwB0AGQAPgA8AHQAZAAgAGIAZwBjAG8AbABvAHIA PQAiACMARgBGAEYARgBGAEYAIgAgAG4AbwB3AHIAYQBwAD0AIgBuAG8AdwByAGEAcAAiAD4AJgBu AGIAcwBwADsAPAAvAHQAZAA+ADwAdABkACAAYgBnAGMAbwBsAG8AcgA9ACIAIwBGAEYARgBGAEYA RgAiACAAbgBvAHcAcgBhAHAAPQAiAG4AbwB3AHIAYQBwACIAPgAmAG4AYgBzAHAAOwA8AC8AdABk AD4APAB0AGQAIABiAGcAYwBvAGwAbwByAD0AIgAjAEYARgBGAEYARgBGACIAIABuAG8AdwByAGEA cAA9ACIAbgBvAHcAcgBhAHAAIgA+ACYAbgBiAHMAcAA7ADwALwB0AGQAPgA8AHQAZAAgAGIAZwBj AG8AbABvAHIAPQAiACMARgBGAEYARgBGAEYAIgAgAG4AbwB3AHIAYQBwAD0AIgBuAG8AdwByAGEA cAAiAD4AJgBuAGIAcwBwADsAPAAvAHQAZAA+ADwAdABkACAAYgBnAGMAbwBsAG8AcgA9ACIAIwBG AEYARgBGAEYARgAiACAAbgBvAHcAcgBhAHAAPQAiAG4AbwB3AHIAYQBwACIAPgB4ADYANAA8AC8A dABkAD4APAB0AGQAIABiAGcAYwBvAGwAbwByAD0AIgAjAEYARgBGAEYARgBGACIAIABuAG8AdwBy AGEAcAA9ACIAbgBvAHcAcgBhAHAAIgA+AG4AdABvAHMAawByAG4AbAAuAGUAeABlACsANwBlAGYA YwAwADwALwB0AGQAPgA8AHQAZAAgAGIAZwBjAG8AbABvAHIAPQAiACMARgBGAEYARgBGAEYAIgAg AG4AbwB3AHIAYQBwAD0AIgBuAG8AdwByAGEAcAAiAD4AJgBuAGIAcwBwADsAPAAvAHQAZAA+ADwA dABkACAAYgBnAGMAbwBsAG8AcgA9ACIAIwBGAEYARgBGAEYARgAiACAAbgBvAHcAcgBhAHAAPQAi AG4AbwB3AHIAYQBwACIAPgAmAG4AYgBzAHAAOwA8AC8AdABkAD4APAB0AGQAIABiAGcAYwBvAGwA bwByAD0AIgAjAEYARgBGAEYARgBGACIAIABuAG8AdwByAGEAcAA9ACIAbgBvAHcAcgBhAHAAIgA+ ACYAbgBiAHMAcAA7ADwALwB0AGQAPgA8AHQAZAAgAGIAZwBjAG8AbABvAHIAPQAiACMARgBGAEYA RgBGAEYAIgAgAG4AbwB3AHIAYQBwAD0AIgBuAG8AdwByAGEAcAAiAD4AJgBuAGIAcwBwADsAPAAv AHQAZAA+ADwAdABkACAAYgBnAGMAbwBsAG8AcgA9ACIAIwBGAEYARgBGAEYARgAiACAAbgBvAHcA cgBhAHAAPQAiAG4AbwB3AHIAYQBwACIAPgBDADoAXABXAGkAbgBkAG8AdwBzAFwATQBpAG4AaQBk AHUAbQBwAFwAMAAyADAANQAxADMALQA1ADUAMgA1ADUALQAwADEALgBkAG0AcAA8AC8AdABkAD4A PAB0AGQAIABiAGcAYwBvAGwAbwByAD0AIgAjAEYARgBGAEYARgBGACIAIABuAG8AdwByAGEAcAA9 ACIAbgBvAHcAcgBhAHAAIgA+ADQAPAAvAHQAZAA+ADwAdABkACAAYgBnAGMAbwBsAG8AcgA9ACIA IwBGAEYARgBGAEYARgAiACAAbgBvAHcAcgBhAHAAPQAiAG4AbwB3AHIAYQBwACIAPgAxADUAPAAv AHQAZAA+ADwAdABkACAAYgBnAGMAbwBsAG8AcgA9ACIAIwBGAEYARgBGAEYARgAiACAAbgBvAHcA cgBhAHAAPQAiAG4AbwB3AHIAYQBwACIAPgA3ADYAMAAxADwALwB0AGQAPgA8AHQAZAAgAGIAZwBj AG8AbABvAHIAPQAiACMARgBGAEYARgBGAEYAIgAgAG4AbwB3AHIAYQBwAD0AIgBuAG8AdwByAGEA cAAiAD4ANQA1ADYALgAwADYANAANAAoAPAAvAHQAZAA+ADwALwB0AHIAPgA8AC8AdABiAG8AZAB5 AD4APAAvAHQAYQBiAGwAZQA+AA0ACgAgADwAaAAzAD4ARgBhAHUAbAB0AGkAbgBnACAARAByAGkA dgBlAHIAPAAvAGgAMwA+AA0ACgA8AHQAYQBiAGwAZQAgAGIAbwByAGQAZQByAD0AIgAxACIAIABj AGUAbABsAHAAYQBkAGQAaQBuAGcAPQAiADUAIgA+ADwAdABiAG8AZAB5AD4APAB0AHIAIABiAGcA YwBvAGwAbwByAD0AIgBFADAARQAwAEUAMAAiAD4ADQAKADwAdABoAD4ARgBpAGwAZQBuAGEAbQBl AA0ACgA8AC8AdABoAD4APAB0AGgAPgBBAGQAZAByAGUAcwBzACAASQBuACAAUwB0AGEAYwBrAA0A CgA8AC8AdABoAD4APAB0AGgAPgBGAHIAbwBtACAAQQBkAGQAcgBlAHMAcwANAAoAPAAvAHQAaAA+ ADwAdABoAD4AVABvACAAQQBkAGQAcgBlAHMAcwANAAoAPAAvAHQAaAA+ADwAdABoAD4AUwBpAHoA ZQANAAoAPAAvAHQAaAA+ADwAdABoAD4AVABpAG0AZQAgAFMAdABhAG0AcAANAAoAPAAvAHQAaAA+ ADwAdABoAD4AVABpAG0AZQAgAFMAdAByAGkAbgBnAA0ACgA8AC8AdABoAD4APAB0AGgAPgBQAHIA bwBkAHUAYwB0ACAATgBhAG0AZQANAAoAPAAvAHQAaAA+ADwAdABoAD4ARgBpAGwAZQAgAEQAZQBz AGMAcgBpAHAAdABpAG8AbgANAAoAPAAvAHQAaAA+ADwAdABoAD4ARgBpAGwAZQAgAFYAZQByAHMA aQBvAG4ADQAKADwALwB0AGgAPgA8AHQAaAA+AEMAbwBtAHAAYQBuAHkADQAKADwALwB0AGgAPgA8 AHQAaAA+AEYAdQBsAGwAIABQAGEAdABoAA0ACgA8AC8AdABoAD4APAAvAHQAcgA+ADwAdAByAD4A PAB0AGQAIABiAGcAYwBvAGwAbwByAD0AIgAjAEYARgBGAEYARgBGACIAIABuAG8AdwByAGEAcAA9 ACIAbgBvAHcAcgBhAHAAIgA+AGEAdABpAGsAbQBwAGEAZwAuAHMAeQBzADwALwB0AGQAPgA8AHQA ZAAgAGIAZwBjAG8AbABvAHIAPQAiACMARgBGAEYARgBGAEYAIgAgAG4AbwB3AHIAYQBwAD0AIgBu AG8AdwByAGEAcAAiAD4AYQB0AGkAawBtAHAAYQBnAC4AcwB5AHMAKwA4AGQAYgA4ADwALwB0AGQA PgA8AHQAZAAgAGIAZwBjAG8AbABvAHIAPQAiACMARgBGAEYARgBGAEYAIgAgAG4AbwB3AHIAYQBw AD0AIgBuAG8AdwByAGEAcAAiAD4AZgBmAGYAZgBmADgAOAAwAGAAMAA0ADYAYQAwADAAMAAwADwA LwB0AGQAPgA8AHQAZAAgAGIAZwBjAG8AbABvAHIAPQAiACMARgBGAEYARgBGAEYAIgAgAG4AbwB3 AHIAYQBwAD0AIgBuAG8AdwByAGEAcAAiAD4AZgBmAGYAZgBmADgAOAAwAGAAMAA0ADcAMQA2ADAA MAAwADwALwB0AGQAPgA8AHQAZAAgAGIAZwBjAG8AbABvAHIAPQAiACMARgBGAEYARgBGAEYAIgAg AG4AbwB3AHIAYQBwAD0AIgBuAG8AdwByAGEAcAAiAD4AMAB4ADAAMAAwADcANgAwADAAMAA8AC8A dABkAD4APAB0AGQAIABiAGcAYwBvAGwAbwByAD0AIgAjAEYARgBGAEYARgBGACIAIABuAG8AdwBy AGEAcAA9ACIAbgBvAHcAcgBhAHAAIgA+ADAAeAA1ADAANgA0AGYAOQA5ADQAPAAvAHQAZAA+ADwA dABkACAAYgBnAGMAbwBsAG8AcgA9ACIAIwBGAEYARgBGAEYARgAiACAAbgBvAHcAcgBhAHAAPQAi AG4AbwB3AHIAYQBwACIAPgAyADgALgAwADkALgAyADAAMQAyACAAMAAyADoAMQAyADoANQAyADwA LwB0AGQAPgA8AHQAZAAgAGIAZwBjAG8AbABvAHIAPQAiACMARgBGAEYARgBGAEYAIgAgAG4AbwB3 AHIAYQBwAD0AIgBuAG8AdwByAGEAcAAiAD4AJgBuAGIAcwBwADsAPAAvAHQAZAA+ADwAdABkACAA YgBnAGMAbwBsAG8AcgA9ACIAIwBGAEYARgBGAEYARgAiACAAbgBvAHcAcgBhAHAAPQAiAG4AbwB3 AHIAYQBwACIAPgAmAG4AYgBzAHAAOwA8AC8AdABkAD4APAB0AGQAIABiAGcAYwBvAGwAbwByAD0A IgAjAEYARgBGAEYARgBGACIAIABuAG8AdwByAGEAcAA9ACIAbgBvAHcAcgBhAHAAIgA+ACYAbgBi AHMAcAA7ADwALwB0AGQAPgA8AHQAZAAgAGIAZwBjAG8AbABvAHIAPQAiACMARgBGAEYARgBGAEYA IgAgAG4AbwB3AHIAYQBwAD0AIgBuAG8AdwByAGEAcAAiAD4AJgBuAGIAcwBwADsAPAAvAHQAZAA+ ADwAdABkACAAYgBnAGMAbwBsAG8AcgA9ACIAIwBGAEYARgBGAEYARgAiACAAbgBvAHcAcgBhAHAA PQAiAG4AbwB3AHIAYQBwACIAPgAmAG4AYgBzAHAAOwANAAoAPAAvAHQAZAA+ADwALwB0AHIAPgA8 AHQAcgA+ADwAdABkACAAYgBnAGMAbwBsAG8AcgA9ACIAIwBGAEYARgBGAEYARgAiACAAbgBvAHcA cgBhAHAAPQAiAG4AbwB3AHIAYQBwACIAPgBkAHgAZwBrAHIAbgBsAC4AcwB5AHMAPAAvAHQAZAA+ ADwAdABkACAAYgBnAGMAbwBsAG8AcgA9ACIAIwBGAEYARgBGAEYARgAiACAAbgBvAHcAcgBhAHAA PQAiAG4AbwB3AHIAYQBwACIAPgBkAHgAZwBrAHIAbgBsAC4AcwB5AHMAKwA1AGQAMAAwADAAPAAv AHQAZAA+ADwAdABkACAAYgBnAGMAbwBsAG8AcgA9ACIAIwBGAEYARgBGAEYARgAiACAAbgBvAHcA cgBhAHAAPQAiAG4AbwB3AHIAYQBwACIAPgBmAGYAZgBmAGYAOAA4ADAAYAAwADUANAA4AGQAMAAw ADAAPAAvAHQAZAA+ADwAdABkACAAYgBnAGMAbwBsAG8AcgA9ACIAIwBGAEYARgBGAEYARgAiACAA bgBvAHcAcgBhAHAAPQAiAG4AbwB3AHIAYQBwACIAPgBmAGYAZgBmAGYAOAA4ADAAYAAwADUANQA4 ADEAMAAwADAAPAAvAHQAZAA+ADwAdABkACAAYgBnAGMAbwBsAG8AcgA9ACIAIwBGAEYARgBGAEYA RgAiACAAbgBvAHcAcgBhAHAAPQAiAG4AbwB3AHIAYQBwACIAPgAwAHgAMAAwADAAZgA0ADAAMAAw ADwALwB0AGQAPgA8AHQAZAAgAGIAZwBjAG8AbABvAHIAPQAiACMARgBGAEYARgBGAEYAIgAgAG4A bwB3AHIAYQBwAD0AIgBuAG8AdwByAGEAcAAiAD4AMAB4ADQAYwBlADcAOQA5AGYAYQA8AC8AdABk AD4APAB0AGQAIABiAGcAYwBvAGwAbwByAD0AIgAjAEYARgBGAEYARgBGACIAIABuAG8AdwByAGEA cAA9ACIAbgBvAHcAcgBhAHAAIgA+ADIAMAAuADEAMQAuADIAMAAxADAAIAAxADAAOgA1ADAAOgA1 ADAAPAAvAHQAZAA+ADwAdABkACAAYgBnAGMAbwBsAG8AcgA9ACIAIwBGAEYARgBGAEYARgAiACAA bgBvAHcAcgBhAHAAPQAiAG4AbwB3AHIAYQBwACIAPgAmAG4AYgBzAHAAOwA8AC8AdABkAD4APAB0 AGQAIABiAGcAYwBvAGwAbwByAD0AIgAjAEYARgBGAEYARgBGACIAIABuAG8AdwByAGEAcAA9ACIA bgBvAHcAcgBhAHAAIgA+ACYAbgBiAHMAcAA7ADwALwB0AGQAPgA8AHQAZAAgAGIAZwBjAG8AbABv AHIAPQAiACMARgBGAEYARgBGAEYAIgAgAG4AbwB3AHIAYQBwAD0AIgBuAG8AdwByAGEAcAAiAD4A JgBuAGIAcwBwADsAPAAvAHQAZAA+ADwAdABkACAAYgBnAGMAbwBsAG8AcgA9ACIAIwBGAEYARgBG AEYARgAiACAAbgBvAHcAcgBhAHAAPQAiAG4AbwB3AHIAYQBwACIAPgAmAG4AYgBzAHAAOwA8AC8A dABkAD4APAB0AGQAIABiAGcAYwBvAGwAbwByAD0AIgAjAEYARgBGAEYARgBGACIAIABuAG8AdwBy AGEAcAA9ACIAbgBvAHcAcgBhAHAAIgA+ACYAbgBiAHMAcAA7AA0ACgA8AC8AdABkAD4APAAvAHQA cgA+ADwAdAByAD4APAB0AGQAIABiAGcAYwBvAGwAbwByAD0AIgAjAEYARgBGAEYARgBGACIAIABu AG8AdwByAGEAcAA9ACIAbgBvAHcAcgBhAHAAIgA+AGQAeABnAG0AbQBzADEALgBzAHkAcwA8AC8A dABkAD4APAB0AGQAIABiAGcAYwBvAGwAbwByAD0AIgAjAEYARgBGAEYARgBGACIAIABuAG8AdwBy AGEAcAA9ACIAbgBvAHcAcgBhAHAAIgA+AGQAeABnAG0AbQBzADEALgBzAHkAcwArAGYAZgAwADcA PAAvAHQAZAA+ADwAdABkACAAYgBnAGMAbwBsAG8AcgA9ACIAIwBGAEYARgBGAEYARgAiACAAbgBv AHcAcgBhAHAAPQAiAG4AbwB3AHIAYQBwACIAPgBmAGYAZgBmAGYAOAA4ADAAYAAwADUANQA4ADEA MAAwADAAPAAvAHQAZAA+ADwAdABkACAAYgBnAGMAbwBsAG8AcgA9ACIAIwBGAEYARgBGAEYARgAi ACAAbgBvAHcAcgBhAHAAPQAiAG4AbwB3AHIAYQBwACIAPgBmAGYAZgBmAGYAOAA4ADAAYAAwADUA NQBjADcAMAAwADAAPAAvAHQAZAA+ADwAdABkACAAYgBnAGMAbwBsAG8AcgA9ACIAIwBGAEYARgBG AEYARgAiACAAbgBvAHcAcgBhAHAAPQAiAG4AbwB3AHIAYQBwACIAPgAwAHgAMAAwADAANAA2ADAA MAAwADwALwB0AGQAPgA8AHQAZAAgAGIAZwBjAG8AbABvAHIAPQAiACMARgBGAEYARgBGAEYAIgAg AG4AbwB3AHIAYQBwAD0AIgBuAG8AdwByAGEAcAAiAD4AMAB4ADQAYwBlADcAOQA5AGMAMQA8AC8A dABkAD4APAB0AGQAIABiAGcAYwBvAGwAbwByAD0AIgAjAEYARgBGAEYARgBGACIAIABuAG8AdwBy AGEAcAA9ACIAbgBvAHcAcgBhAHAAIgA+ADIAMAAuADEAMQAuADIAMAAxADAAIAAxADAAOgA0ADkA OgA1ADMAPAAvAHQAZAA+ADwAdABkACAAYgBnAGMAbwBsAG8AcgA9ACIAIwBGAEYARgBGAEYARgAi ACAAbgBvAHcAcgBhAHAAPQAiAG4AbwB3AHIAYQBwACIAPgAmAG4AYgBzAHAAOwA8AC8AdABkAD4A PAB0AGQAIABiAGcAYwBvAGwAbwByAD0AIgAjAEYARgBGAEYARgBGACIAIABuAG8AdwByAGEAcAA9 ACIAbgBvAHcAcgBhAHAAIgA+ACYAbgBiAHMAcAA7ADwALwB0AGQAPgA8AHQAZAAgAGIAZwBjAG8A bABvAHIAPQAiACMARgBGAEYARgBGAEYAIgAgAG4AbwB3AHIAYQBwAD0AIgBuAG8AdwByAGEAcAAi AD4AJgBuAGIAcwBwADsAPAAvAHQAZAA+ADwAdABkACAAYgBnAGMAbwBsAG8AcgA9ACIAIwBGAEYA RgBGAEYARgAiACAAbgBvAHcAcgBhAHAAPQAiAG4AbwB3AHIAYQBwACIAPgAmAG4AYgBzAHAAOwA8 AC8AdABkAD4APAB0AGQAIABiAGcAYwBvAGwAbwByAD0AIgAjAEYARgBGAEYARgBGACIAIABuAG8A dwByAGEAcAA9ACIAbgBvAHcAcgBhAHAAIgA+ACYAbgBiAHMAcAA7AA0ACgA8AC8AdABkAD4APAAv AHQAcgA+ADwALwB0AGIAbwBkAHkAPgA8AC8AdABhAGIAbABlAD4ADQAKAA0ACgA8AC8AcAA+ADwA LwBiAG8AZAB5AD4APAAvAGgAdABtAGwAPgA= --f46d0444edff974bfa04d527420a 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 --f46d0444edff974bfa04d527420a-- From xen-users-bounces@lists.xen.org Thu Feb 07 19:16:25 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 07 Feb 2013 19:16: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 1U3Ww8-0005jB-Mz; Thu, 07 Feb 2013 19:15:08 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U3Ww7-0005j3-AP for xen-users@lists.xen.org; Thu, 07 Feb 2013 19:15:07 +0000 Received: from [85.158.139.211:60324] by server-8.bemta-5.messagelabs.com id E6/F8-19075-A3DF3115; Thu, 07 Feb 2013 19:15:06 +0000 X-Env-Sender: matthias.kannenberg@googlemail.com X-Msg-Ref: server-8.tower-206.messagelabs.com!1360264504!21546835!1 X-Originating-IP: [209.85.212.179] X-SpamReason: No, hits=0.3 required=7.0 tests=HTML_MESSAGE,RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 7493 invoked from network); 7 Feb 2013 19:15:04 -0000 Received: from mail-wi0-f179.google.com (HELO mail-wi0-f179.google.com) (209.85.212.179) by server-8.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 7 Feb 2013 19:15:04 -0000 Received: by mail-wi0-f179.google.com with SMTP id ez12so3350851wid.6 for ; Thu, 07 Feb 2013 11:15:04 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=20120113; h=x-received:mime-version:from:date:message-id:subject:to :content-type; bh=OPEhsXZAelCU4DqKFDqH8ENnqaVbYxdGxv6MuiPHctg=; b=w7K7XLVQsLhQVjHMBEHpdnvAN4yd05z8nWjIb9R9Tu6Dw1yUnLJlYJ7lEfKQani3g1 RUGqhUhoP+5GmH+Kic285LadXAecrwNICqoR/b3E2pBY6ksV3hCWjo4i4CJUl2wqGqnd WwcoV5D3lJEpDmh/mrJ/4DI20vsAiu/qJO7+JueEsUXFNDktRbIN/yCE0vPBpLSHxUYS I9I24bFfDTifVG1kVy2E1mWodxi9m2WqXwboi03+0Muwt+nh8o8o3XN7JwL+LpP5zEuM B6feI+WedCjxuwnhx5AfoPKSZYLdacc3taoFg97y8B+b4KTMWcD+8UeyxKn2AIbbj4GV 1UfQ== X-Received: by 10.180.100.163 with SMTP id ez3mr4917002wib.32.1360264504494; Thu, 07 Feb 2013 11:15:04 -0800 (PST) MIME-Version: 1.0 Received: by 10.194.80.68 with HTTP; Thu, 7 Feb 2013 11:14:44 -0800 (PST) From: Matthias Date: Thu, 7 Feb 2013 20:14:44 +0100 Message-ID: To: xen-users@lists.xen.org Content-Type: multipart/mixed; boundary=f46d0444edff974bfa04d527420a Subject: [Xen-users] ATI/AMDs atikmpag.sys BSOD while 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: , Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --f46d0444edff974bfa04d527420a Content-Type: text/plain; charset=ISO-8859-1 Hi everyone since I'm currently migrating from xm to xl and now are also a victim of the said error, I started researching on it and found that many people had the issue but not many found solution and behind this BSOD (=Bluescreen of Death), there are actually multiple errors in hiding. What I would like to do is gather as much info as possible in this thread to form a kind of comprehensive guide to fixing this issue. >From what i gathered so far, there are at least 3 different problems with the same symptopms. 1) Situation: After booting the dom0 and booting a windows domU with an ATI/AMD Card, Windows generally works fine, but after rebooting the system, or shutting down / restarting, the Bluescreen occurs or the performance massively below normal. Error: Most likely this is cause the Card is not properly resetted (no FLR [function level reset] ) Solution: If the domU reboots into BSOD, you are screwed and have to reboot the dom0. If it only degrades performance, eject the card and reinitialize to perform a manual reset. Or use the xm toolkit. Status: Don't know if it is fixed yet Source: http://lists.xen.org/archives/html/xen-users/2012-02/msg00443.html , http://wiki.xen.org/wiki/Talk:Xen_VGA_Passthrough_Tested_Adapters 2) Situation: Booting a windows domU results in a BSOD when the CCC (=Catalyst Control Center) installed. Error: The CCC tries to set some specific settings (most likely performance tweaks) within the driver which the driver can't pass to the vga through passthrough mode. Result is a BSOD. Solution: Deinstall the CCC in windows safe mode. The driver itself works without it pretty fine. Status: Don't know if it is fixed yet Source: http://lists.xen.org/archives/html/xen-users/2012-03/msg00617.html Note: I don't really know if this holds for the Vision Engine Control center, too. the VECC is basically the same as the CCC, so i assume it does. I simply haven't found any things referencing it. 3) Situation: This is actually the issue I have. Things seem a lot more random then the other ones. A BSOD happens basically in 80% of booting the Windows domU. Which means, after rebooting dom0, it mostly works. Rebooting or shutting down / starting the domU works sometimes (Once i achieved 6 consecutive reboots or shutdowns / starts before the BSOD happened) but after I get one Bluescreen, almost never (I can't exactly remember if really 'never') comes up again. Of course I tried the above solutions but this didn't helped me. I also tried different different versions of the Catalyst driver (from 12/1 to 13/1) and current releases of xen-4.2-testing and xen-unsable. As I said, this is when using the xl toolkit. I never had this issues using xm. I thought this might belinked to me passing other PCI devices in addition (I'm passing some USB controller to the domU) but even deactivating them didn't help. What I actually found helping boosting the success rate (but not solving the overall issue) is deinstalling all VGA-Related AMD Driver. Windows then runs on it's own VGA-Driver (the graphic card is currectly identified and this is an actual ati driver, so I'm not talking about some generic standard vga driver. I don't know where is driver is coming from). I've attached an analysis file i've gethered from the bluescreen crash dump. I created it using BluescreenView. This is more for currectly identifieng the different BSODs, I guess. Some Infos: Kernel: 3.7.4 kernel.org kernel without patches Xen: latest xen-unstable (but also tested with xen-4.2-testing) Processor: AMD Phenom 1090T Mainboard: Asus Crossfire IV VGA: Radeon HD5700 and Radeon HD5450 Driver: Currently running Catalyst 13/1 but tested nearly everything between 12/1 and 13/1 Error: Don't know yet Solution: Don't know yet Status: unsolved Source: Okay, so basically that's the story. It would be great if some people can complete and extend the list. Especially some who already fixed the issue on their side. (And of course it would be great if someone has an idea for my problem). Thanks --f46d0444edff974bfa04d527420a Content-Type: text/html; charset=UTF-16LE; name="BSOD_info.htm" Content-Disposition: attachment; filename="BSOD_info.htm" Content-Transfer-Encoding: base64 X-Attachment-Id: f_hcwa9fgu0 //48ACEARABPAEMAVABZAFAARQAgAGgAdABtAGwAIABQAFUAQgBMAEkAQwAgACIALQAvAC8AVwAz AEMALwAvAEQAVABEACAASABUAE0ATAAgADMALgAyACAARgBpAG4AYQBsAC8ALwBFAE4AIgA+AA0A CgA8AGgAdABtAGwAPgA8AGgAZQBhAGQAPgANAAoAPABtAGUAdABhACAAaAB0AHQAcAAtAGUAcQB1 AGkAdgA9ACIAYwBvAG4AdABlAG4AdAAtAHQAeQBwAGUAIgAgAGMAbwBuAHQAZQBuAHQAPQAiAHQA ZQB4AHQALwBoAHQAbQBsADsAIABjAGgAYQByAHMAZQB0AD0AVQBUAEYALQAxADYAIgA+ADwAdABp AHQAbABlAD4AQwByAGEAcwBoACAATABpAHMAdAA8AC8AdABpAHQAbABlAD4APAAvAGgAZQBhAGQA PgANAAoAPABiAG8AZAB5AD4ADQAKACAAPABoADMAPgBHAGUAbgBlAHIAYQBsACAAaQBuAGYAbwBy AG0AYQB0AGkAbwBuACAAYQBiAG8AdQB0ACAAQgBTAE8ARAA8AC8AaAAzAD4ADQAKACAAPAB0AGEA YgBsAGUAIABiAG8AcgBkAGUAcgA9ACIAMQAiACAAYwBlAGwAbABwAGEAZABkAGkAbgBnAD0AIgA1 ACIAPgA8AHQAYgBvAGQAeQA+ADwAdAByACAAYgBnAGMAbwBsAG8AcgA9ACIARQAwAEUAMABFADAA IgA+AA0ACgA8AHQAaAA+AEQAdQBtAHAAIABGAGkAbABlAA0ACgA8AC8AdABoAD4APAB0AGgAPgBD AHIAYQBzAGgAIABUAGkAbQBlAA0ACgA8AC8AdABoAD4APAB0AGgAPgBCAHUAZwAgAEMAaABlAGMA awAgAFMAdAByAGkAbgBnAA0ACgA8AC8AdABoAD4APAB0AGgAPgBCAHUAZwAgAEMAaABlAGMAawAg AEMAbwBkAGUADQAKADwALwB0AGgAPgA8AHQAaAA+AFAAYQByAGEAbQBlAHQAZQByACAAMQANAAoA PAAvAHQAaAA+ADwAdABoAD4AUABhAHIAYQBtAGUAdABlAHIAIAAyAA0ACgA8AC8AdABoAD4APAB0 AGgAPgBQAGEAcgBhAG0AZQB0AGUAcgAgADMADQAKADwALwB0AGgAPgA8AHQAaAA+AFAAYQByAGEA bQBlAHQAZQByACAANAANAAoAPAAvAHQAaAA+ADwAdABoAD4AQwBhAHUAcwBlAGQAIABCAHkAIABE AHIAaQB2AGUAcgANAAoAPAAvAHQAaAA+ADwAdABoAD4AQwBhAHUAcwBlAGQAIABCAHkAIABBAGQA ZAByAGUAcwBzAA0ACgA8AC8AdABoAD4APAB0AGgAPgBGAGkAbABlACAARABlAHMAYwByAGkAcAB0 AGkAbwBuAA0ACgA8AC8AdABoAD4APAB0AGgAPgBQAHIAbwBkAHUAYwB0ACAATgBhAG0AZQANAAoA PAAvAHQAaAA+ADwAdABoAD4AQwBvAG0AcABhAG4AeQANAAoAPAAvAHQAaAA+ADwAdABoAD4ARgBp AGwAZQAgAFYAZQByAHMAaQBvAG4ADQAKADwALwB0AGgAPgA8AHQAaAA+AFAAcgBvAGMAZQBzAHMA bwByAA0ACgA8AC8AdABoAD4APAB0AGgAPgBDAHIAYQBzAGgAIABBAGQAZAByAGUAcwBzAA0ACgA8 AC8AdABoAD4APAB0AGgAPgBTAHQAYQBjAGsAIABBAGQAZAByAGUAcwBzACAAMQANAAoAPAAvAHQA aAA+ADwAdABoAD4AUwB0AGEAYwBrACAAQQBkAGQAcgBlAHMAcwAgADIADQAKADwALwB0AGgAPgA8 AHQAaAA+AFMAdABhAGMAawAgAEEAZABkAHIAZQBzAHMAIAAzAA0ACgA8AC8AdABoAD4APAB0AGgA PgBDAG8AbQBwAHUAdABlAHIAIABOAGEAbQBlAA0ACgA8AC8AdABoAD4APAB0AGgAPgBGAHUAbABs ACAAUABhAHQAaAANAAoAPAAvAHQAaAA+ADwAdABoAD4AUAByAG8AYwBlAHMAcwBvAHIAcwAgAEMA bwB1AG4AdAANAAoAPAAvAHQAaAA+ADwAdABoAD4ATQBhAGoAbwByACAAVgBlAHIAcwBpAG8AbgAN AAoAPAAvAHQAaAA+ADwAdABoAD4ATQBpAG4AbwByACAAVgBlAHIAcwBpAG8AbgANAAoAPAAvAHQA aAA+ADwAdABoAD4ARAB1AG0AcAAgAEYAaQBsAGUAIABTAGkAegBlAA0ACgA8AC8AdABoAD4APAAv AHQAcgA+ADwAdAByAD4APAB0AGQAIABiAGcAYwBvAGwAbwByAD0AIgAjAEYARgBGAEYARgBGACIA IABuAG8AdwByAGEAcAA9ACIAbgBvAHcAcgBhAHAAIgA+ADAAMgAwADUAMQAzAC0ANQA1ADIANQA1 AC0AMAAxAC4AZABtAHAAPAAvAHQAZAA+ADwAdABkACAAYgBnAGMAbwBsAG8AcgA9ACIAIwBGAEYA RgBGAEYARgAiACAAbgBvAHcAcgBhAHAAPQAiAG4AbwB3AHIAYQBwACIAPgAwADUALgAwADIALgAy ADAAMQAzACAAMAAyADoAMAA2ADoAMgA2ADwALwB0AGQAPgA8AHQAZAAgAGIAZwBjAG8AbABvAHIA PQAiACMARgBGAEYARgBGAEYAIgAgAG4AbwB3AHIAYQBwAD0AIgBuAG8AdwByAGEAcAAiAD4AJgBu AGIAcwBwADsAPAAvAHQAZAA+ADwAdABkACAAYgBnAGMAbwBsAG8AcgA9ACIAIwBGAEYARgBGAEYA RgAiACAAbgBvAHcAcgBhAHAAPQAiAG4AbwB3AHIAYQBwACIAPgAwAHgAMAAwADAAMAAwADEAMQA2 ADwALwB0AGQAPgA8AHQAZAAgAGIAZwBjAG8AbABvAHIAPQAiACMARgBGAEYARgBGAEYAIgAgAG4A bwB3AHIAYQBwAD0AIgBuAG8AdwByAGEAcAAiAD4AZgBmAGYAZgBmAGEAOAAwAGAAMAA4ADMAMgA4 ADAAMQAwADwALwB0AGQAPgA8AHQAZAAgAGIAZwBjAG8AbABvAHIAPQAiACMARgBGAEYARgBGAEYA IgAgAG4AbwB3AHIAYQBwAD0AIgBuAG8AdwByAGEAcAAiAD4AZgBmAGYAZgBmADgAOAAwAGAAMAA0 ADYAYQA4AGQAYgA4ADwALwB0AGQAPgA8AHQAZAAgAGIAZwBjAG8AbABvAHIAPQAiACMARgBGAEYA RgBGAEYAIgAgAG4AbwB3AHIAYQBwAD0AIgBuAG8AdwByAGEAcAAiAD4AMAAwADAAMAAwADAAMAAw AGAAMAAwADAAMAAwADAAMAAwADwALwB0AGQAPgA8AHQAZAAgAGIAZwBjAG8AbABvAHIAPQAiACMA RgBGAEYARgBGAEYAIgAgAG4AbwB3AHIAYQBwAD0AIgBuAG8AdwByAGEAcAAiAD4AMAAwADAAMAAw ADAAMAAwAGAAMAAwADAAMAAwADAAMAAyADwALwB0AGQAPgA8AHQAZAAgAGIAZwBjAG8AbABvAHIA PQAiACMARgBGAEYARgBGAEYAIgAgAG4AbwB3AHIAYQBwAD0AIgBuAG8AdwByAGEAcAAiAD4AZAB4 AGcAawByAG4AbAAuAHMAeQBzADwALwB0AGQAPgA8AHQAZAAgAGIAZwBjAG8AbABvAHIAPQAiACMA RgBGAEYARgBGAEYAIgAgAG4AbwB3AHIAYQBwAD0AIgBuAG8AdwByAGEAcAAiAD4AZAB4AGcAawBy AG4AbAAuAHMAeQBzACsANQBkADAAMAAwADwALwB0AGQAPgA8AHQAZAAgAGIAZwBjAG8AbABvAHIA PQAiACMARgBGAEYARgBGAEYAIgAgAG4AbwB3AHIAYQBwAD0AIgBuAG8AdwByAGEAcAAiAD4AJgBu AGIAcwBwADsAPAAvAHQAZAA+ADwAdABkACAAYgBnAGMAbwBsAG8AcgA9ACIAIwBGAEYARgBGAEYA RgAiACAAbgBvAHcAcgBhAHAAPQAiAG4AbwB3AHIAYQBwACIAPgAmAG4AYgBzAHAAOwA8AC8AdABk AD4APAB0AGQAIABiAGcAYwBvAGwAbwByAD0AIgAjAEYARgBGAEYARgBGACIAIABuAG8AdwByAGEA cAA9ACIAbgBvAHcAcgBhAHAAIgA+ACYAbgBiAHMAcAA7ADwALwB0AGQAPgA8AHQAZAAgAGIAZwBj AG8AbABvAHIAPQAiACMARgBGAEYARgBGAEYAIgAgAG4AbwB3AHIAYQBwAD0AIgBuAG8AdwByAGEA cAAiAD4AJgBuAGIAcwBwADsAPAAvAHQAZAA+ADwAdABkACAAYgBnAGMAbwBsAG8AcgA9ACIAIwBG AEYARgBGAEYARgAiACAAbgBvAHcAcgBhAHAAPQAiAG4AbwB3AHIAYQBwACIAPgB4ADYANAA8AC8A dABkAD4APAB0AGQAIABiAGcAYwBvAGwAbwByAD0AIgAjAEYARgBGAEYARgBGACIAIABuAG8AdwBy AGEAcAA9ACIAbgBvAHcAcgBhAHAAIgA+AG4AdABvAHMAawByAG4AbAAuAGUAeABlACsANwBlAGYA YwAwADwALwB0AGQAPgA8AHQAZAAgAGIAZwBjAG8AbABvAHIAPQAiACMARgBGAEYARgBGAEYAIgAg AG4AbwB3AHIAYQBwAD0AIgBuAG8AdwByAGEAcAAiAD4AJgBuAGIAcwBwADsAPAAvAHQAZAA+ADwA dABkACAAYgBnAGMAbwBsAG8AcgA9ACIAIwBGAEYARgBGAEYARgAiACAAbgBvAHcAcgBhAHAAPQAi AG4AbwB3AHIAYQBwACIAPgAmAG4AYgBzAHAAOwA8AC8AdABkAD4APAB0AGQAIABiAGcAYwBvAGwA bwByAD0AIgAjAEYARgBGAEYARgBGACIAIABuAG8AdwByAGEAcAA9ACIAbgBvAHcAcgBhAHAAIgA+ ACYAbgBiAHMAcAA7ADwALwB0AGQAPgA8AHQAZAAgAGIAZwBjAG8AbABvAHIAPQAiACMARgBGAEYA RgBGAEYAIgAgAG4AbwB3AHIAYQBwAD0AIgBuAG8AdwByAGEAcAAiAD4AJgBuAGIAcwBwADsAPAAv AHQAZAA+ADwAdABkACAAYgBnAGMAbwBsAG8AcgA9ACIAIwBGAEYARgBGAEYARgAiACAAbgBvAHcA cgBhAHAAPQAiAG4AbwB3AHIAYQBwACIAPgBDADoAXABXAGkAbgBkAG8AdwBzAFwATQBpAG4AaQBk AHUAbQBwAFwAMAAyADAANQAxADMALQA1ADUAMgA1ADUALQAwADEALgBkAG0AcAA8AC8AdABkAD4A PAB0AGQAIABiAGcAYwBvAGwAbwByAD0AIgAjAEYARgBGAEYARgBGACIAIABuAG8AdwByAGEAcAA9 ACIAbgBvAHcAcgBhAHAAIgA+ADQAPAAvAHQAZAA+ADwAdABkACAAYgBnAGMAbwBsAG8AcgA9ACIA IwBGAEYARgBGAEYARgAiACAAbgBvAHcAcgBhAHAAPQAiAG4AbwB3AHIAYQBwACIAPgAxADUAPAAv AHQAZAA+ADwAdABkACAAYgBnAGMAbwBsAG8AcgA9ACIAIwBGAEYARgBGAEYARgAiACAAbgBvAHcA cgBhAHAAPQAiAG4AbwB3AHIAYQBwACIAPgA3ADYAMAAxADwALwB0AGQAPgA8AHQAZAAgAGIAZwBj AG8AbABvAHIAPQAiACMARgBGAEYARgBGAEYAIgAgAG4AbwB3AHIAYQBwAD0AIgBuAG8AdwByAGEA cAAiAD4ANQA1ADYALgAwADYANAANAAoAPAAvAHQAZAA+ADwALwB0AHIAPgA8AC8AdABiAG8AZAB5 AD4APAAvAHQAYQBiAGwAZQA+AA0ACgAgADwAaAAzAD4ARgBhAHUAbAB0AGkAbgBnACAARAByAGkA dgBlAHIAPAAvAGgAMwA+AA0ACgA8AHQAYQBiAGwAZQAgAGIAbwByAGQAZQByAD0AIgAxACIAIABj AGUAbABsAHAAYQBkAGQAaQBuAGcAPQAiADUAIgA+ADwAdABiAG8AZAB5AD4APAB0AHIAIABiAGcA YwBvAGwAbwByAD0AIgBFADAARQAwAEUAMAAiAD4ADQAKADwAdABoAD4ARgBpAGwAZQBuAGEAbQBl AA0ACgA8AC8AdABoAD4APAB0AGgAPgBBAGQAZAByAGUAcwBzACAASQBuACAAUwB0AGEAYwBrAA0A CgA8AC8AdABoAD4APAB0AGgAPgBGAHIAbwBtACAAQQBkAGQAcgBlAHMAcwANAAoAPAAvAHQAaAA+ ADwAdABoAD4AVABvACAAQQBkAGQAcgBlAHMAcwANAAoAPAAvAHQAaAA+ADwAdABoAD4AUwBpAHoA ZQANAAoAPAAvAHQAaAA+ADwAdABoAD4AVABpAG0AZQAgAFMAdABhAG0AcAANAAoAPAAvAHQAaAA+ ADwAdABoAD4AVABpAG0AZQAgAFMAdAByAGkAbgBnAA0ACgA8AC8AdABoAD4APAB0AGgAPgBQAHIA bwBkAHUAYwB0ACAATgBhAG0AZQANAAoAPAAvAHQAaAA+ADwAdABoAD4ARgBpAGwAZQAgAEQAZQBz AGMAcgBpAHAAdABpAG8AbgANAAoAPAAvAHQAaAA+ADwAdABoAD4ARgBpAGwAZQAgAFYAZQByAHMA aQBvAG4ADQAKADwALwB0AGgAPgA8AHQAaAA+AEMAbwBtAHAAYQBuAHkADQAKADwALwB0AGgAPgA8 AHQAaAA+AEYAdQBsAGwAIABQAGEAdABoAA0ACgA8AC8AdABoAD4APAAvAHQAcgA+ADwAdAByAD4A PAB0AGQAIABiAGcAYwBvAGwAbwByAD0AIgAjAEYARgBGAEYARgBGACIAIABuAG8AdwByAGEAcAA9 ACIAbgBvAHcAcgBhAHAAIgA+AGEAdABpAGsAbQBwAGEAZwAuAHMAeQBzADwALwB0AGQAPgA8AHQA ZAAgAGIAZwBjAG8AbABvAHIAPQAiACMARgBGAEYARgBGAEYAIgAgAG4AbwB3AHIAYQBwAD0AIgBu AG8AdwByAGEAcAAiAD4AYQB0AGkAawBtAHAAYQBnAC4AcwB5AHMAKwA4AGQAYgA4ADwALwB0AGQA PgA8AHQAZAAgAGIAZwBjAG8AbABvAHIAPQAiACMARgBGAEYARgBGAEYAIgAgAG4AbwB3AHIAYQBw AD0AIgBuAG8AdwByAGEAcAAiAD4AZgBmAGYAZgBmADgAOAAwAGAAMAA0ADYAYQAwADAAMAAwADwA LwB0AGQAPgA8AHQAZAAgAGIAZwBjAG8AbABvAHIAPQAiACMARgBGAEYARgBGAEYAIgAgAG4AbwB3 AHIAYQBwAD0AIgBuAG8AdwByAGEAcAAiAD4AZgBmAGYAZgBmADgAOAAwAGAAMAA0ADcAMQA2ADAA MAAwADwALwB0AGQAPgA8AHQAZAAgAGIAZwBjAG8AbABvAHIAPQAiACMARgBGAEYARgBGAEYAIgAg AG4AbwB3AHIAYQBwAD0AIgBuAG8AdwByAGEAcAAiAD4AMAB4ADAAMAAwADcANgAwADAAMAA8AC8A dABkAD4APAB0AGQAIABiAGcAYwBvAGwAbwByAD0AIgAjAEYARgBGAEYARgBGACIAIABuAG8AdwBy AGEAcAA9ACIAbgBvAHcAcgBhAHAAIgA+ADAAeAA1ADAANgA0AGYAOQA5ADQAPAAvAHQAZAA+ADwA dABkACAAYgBnAGMAbwBsAG8AcgA9ACIAIwBGAEYARgBGAEYARgAiACAAbgBvAHcAcgBhAHAAPQAi AG4AbwB3AHIAYQBwACIAPgAyADgALgAwADkALgAyADAAMQAyACAAMAAyADoAMQAyADoANQAyADwA LwB0AGQAPgA8AHQAZAAgAGIAZwBjAG8AbABvAHIAPQAiACMARgBGAEYARgBGAEYAIgAgAG4AbwB3 AHIAYQBwAD0AIgBuAG8AdwByAGEAcAAiAD4AJgBuAGIAcwBwADsAPAAvAHQAZAA+ADwAdABkACAA YgBnAGMAbwBsAG8AcgA9ACIAIwBGAEYARgBGAEYARgAiACAAbgBvAHcAcgBhAHAAPQAiAG4AbwB3 AHIAYQBwACIAPgAmAG4AYgBzAHAAOwA8AC8AdABkAD4APAB0AGQAIABiAGcAYwBvAGwAbwByAD0A IgAjAEYARgBGAEYARgBGACIAIABuAG8AdwByAGEAcAA9ACIAbgBvAHcAcgBhAHAAIgA+ACYAbgBi AHMAcAA7ADwALwB0AGQAPgA8AHQAZAAgAGIAZwBjAG8AbABvAHIAPQAiACMARgBGAEYARgBGAEYA IgAgAG4AbwB3AHIAYQBwAD0AIgBuAG8AdwByAGEAcAAiAD4AJgBuAGIAcwBwADsAPAAvAHQAZAA+ ADwAdABkACAAYgBnAGMAbwBsAG8AcgA9ACIAIwBGAEYARgBGAEYARgAiACAAbgBvAHcAcgBhAHAA PQAiAG4AbwB3AHIAYQBwACIAPgAmAG4AYgBzAHAAOwANAAoAPAAvAHQAZAA+ADwALwB0AHIAPgA8 AHQAcgA+ADwAdABkACAAYgBnAGMAbwBsAG8AcgA9ACIAIwBGAEYARgBGAEYARgAiACAAbgBvAHcA cgBhAHAAPQAiAG4AbwB3AHIAYQBwACIAPgBkAHgAZwBrAHIAbgBsAC4AcwB5AHMAPAAvAHQAZAA+ ADwAdABkACAAYgBnAGMAbwBsAG8AcgA9ACIAIwBGAEYARgBGAEYARgAiACAAbgBvAHcAcgBhAHAA PQAiAG4AbwB3AHIAYQBwACIAPgBkAHgAZwBrAHIAbgBsAC4AcwB5AHMAKwA1AGQAMAAwADAAPAAv AHQAZAA+ADwAdABkACAAYgBnAGMAbwBsAG8AcgA9ACIAIwBGAEYARgBGAEYARgAiACAAbgBvAHcA cgBhAHAAPQAiAG4AbwB3AHIAYQBwACIAPgBmAGYAZgBmAGYAOAA4ADAAYAAwADUANAA4AGQAMAAw ADAAPAAvAHQAZAA+ADwAdABkACAAYgBnAGMAbwBsAG8AcgA9ACIAIwBGAEYARgBGAEYARgAiACAA bgBvAHcAcgBhAHAAPQAiAG4AbwB3AHIAYQBwACIAPgBmAGYAZgBmAGYAOAA4ADAAYAAwADUANQA4 ADEAMAAwADAAPAAvAHQAZAA+ADwAdABkACAAYgBnAGMAbwBsAG8AcgA9ACIAIwBGAEYARgBGAEYA RgAiACAAbgBvAHcAcgBhAHAAPQAiAG4AbwB3AHIAYQBwACIAPgAwAHgAMAAwADAAZgA0ADAAMAAw ADwALwB0AGQAPgA8AHQAZAAgAGIAZwBjAG8AbABvAHIAPQAiACMARgBGAEYARgBGAEYAIgAgAG4A bwB3AHIAYQBwAD0AIgBuAG8AdwByAGEAcAAiAD4AMAB4ADQAYwBlADcAOQA5AGYAYQA8AC8AdABk AD4APAB0AGQAIABiAGcAYwBvAGwAbwByAD0AIgAjAEYARgBGAEYARgBGACIAIABuAG8AdwByAGEA cAA9ACIAbgBvAHcAcgBhAHAAIgA+ADIAMAAuADEAMQAuADIAMAAxADAAIAAxADAAOgA1ADAAOgA1 ADAAPAAvAHQAZAA+ADwAdABkACAAYgBnAGMAbwBsAG8AcgA9ACIAIwBGAEYARgBGAEYARgAiACAA bgBvAHcAcgBhAHAAPQAiAG4AbwB3AHIAYQBwACIAPgAmAG4AYgBzAHAAOwA8AC8AdABkAD4APAB0 AGQAIABiAGcAYwBvAGwAbwByAD0AIgAjAEYARgBGAEYARgBGACIAIABuAG8AdwByAGEAcAA9ACIA bgBvAHcAcgBhAHAAIgA+ACYAbgBiAHMAcAA7ADwALwB0AGQAPgA8AHQAZAAgAGIAZwBjAG8AbABv AHIAPQAiACMARgBGAEYARgBGAEYAIgAgAG4AbwB3AHIAYQBwAD0AIgBuAG8AdwByAGEAcAAiAD4A JgBuAGIAcwBwADsAPAAvAHQAZAA+ADwAdABkACAAYgBnAGMAbwBsAG8AcgA9ACIAIwBGAEYARgBG AEYARgAiACAAbgBvAHcAcgBhAHAAPQAiAG4AbwB3AHIAYQBwACIAPgAmAG4AYgBzAHAAOwA8AC8A dABkAD4APAB0AGQAIABiAGcAYwBvAGwAbwByAD0AIgAjAEYARgBGAEYARgBGACIAIABuAG8AdwBy AGEAcAA9ACIAbgBvAHcAcgBhAHAAIgA+ACYAbgBiAHMAcAA7AA0ACgA8AC8AdABkAD4APAAvAHQA cgA+ADwAdAByAD4APAB0AGQAIABiAGcAYwBvAGwAbwByAD0AIgAjAEYARgBGAEYARgBGACIAIABu AG8AdwByAGEAcAA9ACIAbgBvAHcAcgBhAHAAIgA+AGQAeABnAG0AbQBzADEALgBzAHkAcwA8AC8A dABkAD4APAB0AGQAIABiAGcAYwBvAGwAbwByAD0AIgAjAEYARgBGAEYARgBGACIAIABuAG8AdwBy AGEAcAA9ACIAbgBvAHcAcgBhAHAAIgA+AGQAeABnAG0AbQBzADEALgBzAHkAcwArAGYAZgAwADcA PAAvAHQAZAA+ADwAdABkACAAYgBnAGMAbwBsAG8AcgA9ACIAIwBGAEYARgBGAEYARgAiACAAbgBv AHcAcgBhAHAAPQAiAG4AbwB3AHIAYQBwACIAPgBmAGYAZgBmAGYAOAA4ADAAYAAwADUANQA4ADEA MAAwADAAPAAvAHQAZAA+ADwAdABkACAAYgBnAGMAbwBsAG8AcgA9ACIAIwBGAEYARgBGAEYARgAi ACAAbgBvAHcAcgBhAHAAPQAiAG4AbwB3AHIAYQBwACIAPgBmAGYAZgBmAGYAOAA4ADAAYAAwADUA NQBjADcAMAAwADAAPAAvAHQAZAA+ADwAdABkACAAYgBnAGMAbwBsAG8AcgA9ACIAIwBGAEYARgBG AEYARgAiACAAbgBvAHcAcgBhAHAAPQAiAG4AbwB3AHIAYQBwACIAPgAwAHgAMAAwADAANAA2ADAA MAAwADwALwB0AGQAPgA8AHQAZAAgAGIAZwBjAG8AbABvAHIAPQAiACMARgBGAEYARgBGAEYAIgAg AG4AbwB3AHIAYQBwAD0AIgBuAG8AdwByAGEAcAAiAD4AMAB4ADQAYwBlADcAOQA5AGMAMQA8AC8A dABkAD4APAB0AGQAIABiAGcAYwBvAGwAbwByAD0AIgAjAEYARgBGAEYARgBGACIAIABuAG8AdwBy AGEAcAA9ACIAbgBvAHcAcgBhAHAAIgA+ADIAMAAuADEAMQAuADIAMAAxADAAIAAxADAAOgA0ADkA OgA1ADMAPAAvAHQAZAA+ADwAdABkACAAYgBnAGMAbwBsAG8AcgA9ACIAIwBGAEYARgBGAEYARgAi ACAAbgBvAHcAcgBhAHAAPQAiAG4AbwB3AHIAYQBwACIAPgAmAG4AYgBzAHAAOwA8AC8AdABkAD4A PAB0AGQAIABiAGcAYwBvAGwAbwByAD0AIgAjAEYARgBGAEYARgBGACIAIABuAG8AdwByAGEAcAA9 ACIAbgBvAHcAcgBhAHAAIgA+ACYAbgBiAHMAcAA7ADwALwB0AGQAPgA8AHQAZAAgAGIAZwBjAG8A bABvAHIAPQAiACMARgBGAEYARgBGAEYAIgAgAG4AbwB3AHIAYQBwAD0AIgBuAG8AdwByAGEAcAAi AD4AJgBuAGIAcwBwADsAPAAvAHQAZAA+ADwAdABkACAAYgBnAGMAbwBsAG8AcgA9ACIAIwBGAEYA RgBGAEYARgAiACAAbgBvAHcAcgBhAHAAPQAiAG4AbwB3AHIAYQBwACIAPgAmAG4AYgBzAHAAOwA8 AC8AdABkAD4APAB0AGQAIABiAGcAYwBvAGwAbwByAD0AIgAjAEYARgBGAEYARgBGACIAIABuAG8A dwByAGEAcAA9ACIAbgBvAHcAcgBhAHAAIgA+ACYAbgBiAHMAcAA7AA0ACgA8AC8AdABkAD4APAAv AHQAcgA+ADwALwB0AGIAbwBkAHkAPgA8AC8AdABhAGIAbABlAD4ADQAKAA0ACgA8AC8AcAA+ADwA LwBiAG8AZAB5AD4APAAvAGgAdABtAGwAPgA= --f46d0444edff974bfa04d527420a 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 --f46d0444edff974bfa04d527420a-- From xen-users-bounces@lists.xen.org Thu Feb 07 20:46:15 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 07 Feb 2013 20:46: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 1U3YLB-0000jN-CH; Thu, 07 Feb 2013 20:45:05 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U3YL9-0000jI-3v for xen-users@lists.xen.org; Thu, 07 Feb 2013 20:45:03 +0000 Received: from [85.158.139.211:9314] by server-14.bemta-5.messagelabs.com id B8/73-06967-E4214115; Thu, 07 Feb 2013 20:45:02 +0000 X-Env-Sender: juliofong@mail.com X-Msg-Ref: server-7.tower-206.messagelabs.com!1360269901!21172825!1 X-Originating-IP: [74.208.4.201] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNzQuMjA4LjQuMjAxID0+IDU3NDM=\n, ML_RADAR_SPEW_LINKS_14, spamassassin: X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 5617 invoked from network); 7 Feb 2013 20:45:01 -0000 Received: from mout.gmx.net (HELO mout.gmx.net) (74.208.4.201) by server-7.tower-206.messagelabs.com with SMTP; 7 Feb 2013 20:45:01 -0000 Received: from mailout-us.gmx.com ([172.19.198.46]) by mrigmx.server.lan (mrigmxus002) with ESMTP (Nemesis) id 0MI6uY-1U5DIQ1W6Y-003tUP for ; Thu, 07 Feb 2013 21:45:00 +0100 Received: (qmail 3476 invoked by uid 0); 7 Feb 2013 20:45:00 -0000 Received: from 86.66.222.237 by rms-us005 with HTTP Date: Thu, 07 Feb 2013 15:44:59 -0500 From: "FONG Julio" Message-ID: <20130207204500.209610@gmx.com> MIME-Version: 1.0 To: xen-users@lists.xen.org X-Authenticated: #76551402 X-Flags: 0001 X-Mailer: GMX.com Web Mailer x-registered: 0 X-GMX-UID: G3dmcYUw3zOlO4t3+3AhMgV+IGRvbwCT Subject: [Xen-users] Getting xen domus memory stats working on CentOS X-BeenThere: xen-users@lists.xen.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="===============0389487966668216909==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============0389487966668216909== Content-Type: multipart/alternative; boundary="========GMXBoundary20961136026990032004" --========GMXBoundary20961136026990032004 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit I would like to thank you for all your xen support. There is now 1 week that I'm trying to find a way to get domus memory stats on CentOS using xen 3.0.3, I also tried with xen 3.4.4. I compiled the last libvirt from source, I heard that some libvirt api functions has been disabled by rhel developer because of a flaw, I readed that they had patched the xen driver in the past before they had been removed for other releases. I would like to develop and contribute but I don't even know how to create files patch. Can you explain me a little bit about this patch that they added? what they done after that? Do you know some CentOS releases that support the domus memory function call? I can use fedora that provide xen-driver rpm but the problem is that it was build for xen 4 witch is not stable. What you suggest me? I'm using now CentOS 5.8 with xen 3.0.3. and xentop doesn't refresh memory used by domus. Many Thanks. Julio --========GMXBoundary20961136026990032004 Content-Type: text/html; charset="utf-8" Content-Transfer-Encoding: quoted-printable I would = like to thank you for all your xen support.

There is now 1 week = that I'm trying to find a way to get domus memory stats on CentOS using xen= 3.0.3, I also tried with xen 3.4.4. I compiled the last libvirt from sourc= e, I heard that some libvirt api functions has been disabled by rhel develo= per because of a flaw, I readed that they had patched the xen driver in the= past before they had been removed for other releases. I would like to deve= lop and contribute but I don't even know how to create files patch.
Ca= n you explain me a little bit about this patch that they added? what they d= one after that?
Do you know some CentOS releases that support the domu= s memory function call?
I can use fedora that provide xen-driver rpm b= ut the problem is that it was build for xen 4 witch is not stable. What you= suggest me? I'm using now CentOS 5.8 with xen 3.0.3. and xentop doesn't re= fresh memory used by domus.

Many Thanks. Julio --========GMXBoundary20961136026990032004-- --===============0389487966668216909== 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 --===============0389487966668216909==-- From xen-users-bounces@lists.xen.org Thu Feb 07 20:46:15 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 07 Feb 2013 20:46: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 1U3YLB-0000jN-CH; Thu, 07 Feb 2013 20:45:05 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U3YL9-0000jI-3v for xen-users@lists.xen.org; Thu, 07 Feb 2013 20:45:03 +0000 Received: from [85.158.139.211:9314] by server-14.bemta-5.messagelabs.com id B8/73-06967-E4214115; Thu, 07 Feb 2013 20:45:02 +0000 X-Env-Sender: juliofong@mail.com X-Msg-Ref: server-7.tower-206.messagelabs.com!1360269901!21172825!1 X-Originating-IP: [74.208.4.201] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNzQuMjA4LjQuMjAxID0+IDU3NDM=\n, ML_RADAR_SPEW_LINKS_14, spamassassin: X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 5617 invoked from network); 7 Feb 2013 20:45:01 -0000 Received: from mout.gmx.net (HELO mout.gmx.net) (74.208.4.201) by server-7.tower-206.messagelabs.com with SMTP; 7 Feb 2013 20:45:01 -0000 Received: from mailout-us.gmx.com ([172.19.198.46]) by mrigmx.server.lan (mrigmxus002) with ESMTP (Nemesis) id 0MI6uY-1U5DIQ1W6Y-003tUP for ; Thu, 07 Feb 2013 21:45:00 +0100 Received: (qmail 3476 invoked by uid 0); 7 Feb 2013 20:45:00 -0000 Received: from 86.66.222.237 by rms-us005 with HTTP Date: Thu, 07 Feb 2013 15:44:59 -0500 From: "FONG Julio" Message-ID: <20130207204500.209610@gmx.com> MIME-Version: 1.0 To: xen-users@lists.xen.org X-Authenticated: #76551402 X-Flags: 0001 X-Mailer: GMX.com Web Mailer x-registered: 0 X-GMX-UID: G3dmcYUw3zOlO4t3+3AhMgV+IGRvbwCT Subject: [Xen-users] Getting xen domus memory stats working on CentOS X-BeenThere: xen-users@lists.xen.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="===============0389487966668216909==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============0389487966668216909== Content-Type: multipart/alternative; boundary="========GMXBoundary20961136026990032004" --========GMXBoundary20961136026990032004 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit I would like to thank you for all your xen support. There is now 1 week that I'm trying to find a way to get domus memory stats on CentOS using xen 3.0.3, I also tried with xen 3.4.4. I compiled the last libvirt from source, I heard that some libvirt api functions has been disabled by rhel developer because of a flaw, I readed that they had patched the xen driver in the past before they had been removed for other releases. I would like to develop and contribute but I don't even know how to create files patch. Can you explain me a little bit about this patch that they added? what they done after that? Do you know some CentOS releases that support the domus memory function call? I can use fedora that provide xen-driver rpm but the problem is that it was build for xen 4 witch is not stable. What you suggest me? I'm using now CentOS 5.8 with xen 3.0.3. and xentop doesn't refresh memory used by domus. Many Thanks. Julio --========GMXBoundary20961136026990032004 Content-Type: text/html; charset="utf-8" Content-Transfer-Encoding: quoted-printable I would = like to thank you for all your xen support.

There is now 1 week = that I'm trying to find a way to get domus memory stats on CentOS using xen= 3.0.3, I also tried with xen 3.4.4. I compiled the last libvirt from sourc= e, I heard that some libvirt api functions has been disabled by rhel develo= per because of a flaw, I readed that they had patched the xen driver in the= past before they had been removed for other releases. I would like to deve= lop and contribute but I don't even know how to create files patch.
Ca= n you explain me a little bit about this patch that they added? what they d= one after that?
Do you know some CentOS releases that support the domu= s memory function call?
I can use fedora that provide xen-driver rpm b= ut the problem is that it was build for xen 4 witch is not stable. What you= suggest me? I'm using now CentOS 5.8 with xen 3.0.3. and xentop doesn't re= fresh memory used by domus.

Many Thanks. Julio --========GMXBoundary20961136026990032004-- --===============0389487966668216909== 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 --===============0389487966668216909==-- From xen-users-bounces@lists.xen.org Thu Feb 07 21:57:17 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 07 Feb 2013 21:57: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 1U3ZRx-0003fs-63; Thu, 07 Feb 2013 21:56:09 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U3ZRv-0003fk-9G for xen-users@lists.xen.org; Thu, 07 Feb 2013 21:56:07 +0000 Received: from [85.158.139.83:31411] by server-13.bemta-5.messagelabs.com id 62/5D-06769-6F224115; Thu, 07 Feb 2013 21:56:06 +0000 X-Env-Sender: davidtecher@yahoo.fr X-Msg-Ref: server-2.tower-182.messagelabs.com!1360274160!30913247!1 X-Originating-IP: [77.238.189.68] 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,ML_RADAR_SPEW_LINKS_6, spamassassin: X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 11289 invoked from network); 7 Feb 2013 21:56:04 -0000 Received: from nm15.bullet.mail.ird.yahoo.com (HELO nm15.bullet.mail.ird.yahoo.com) (77.238.189.68) by server-2.tower-182.messagelabs.com with SMTP; 7 Feb 2013 21:56:04 -0000 Received: from [212.82.105.245] by nm15.bullet.mail.ird.yahoo.com with NNFMP; 07 Feb 2013 21:56:00 -0000 Received: from [212.82.108.118] by tm17.bullet.mail.ird.yahoo.com with NNFMP; 07 Feb 2013 21:56:00 -0000 Received: from [127.0.0.1] by omp1027.mail.ird.yahoo.com with NNFMP; 07 Feb 2013 21:56:00 -0000 X-Yahoo-Newman-Property: ymail-3 X-Yahoo-Newman-Id: 835528.70834.bm@omp1027.mail.ird.yahoo.com Received: (qmail 66079 invoked by uid 60001); 7 Feb 2013 21:56:00 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.fr; s=s1024; t=1360274160; bh=H4KfS4nnZ53O32XKfWI67KbEFX2QwZvbSQu2g35OYQY=; h=X-YMail-OSG:Received:X-Rocket-MIMEInfo:X-Mailer:References:Message-ID:Date:From:Reply-To:Subject:To:In-Reply-To:MIME-Version:Content-Type; b=rJ2DGsojetVUyg7xsxluuxlg0khVtBioIciUBBsMWp3LzBOkD6uoVDhLP6h84drB6+Pk4xwqddzHPqrTJC53TMbjBMIIB0PUcECfYtZCpOh6Zlb3zkW3lQ1LSY0KKzLr4topLt+Mel5j5l2V/RGwf804wDjwa8XZA6A4BE6ffsA= DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.fr; h=X-YMail-OSG:Received:X-Rocket-MIMEInfo:X-Mailer:References:Message-ID:Date:From:Reply-To:Subject:To:In-Reply-To:MIME-Version:Content-Type; b=29X9eQbJZOX2s0VUPU0EX/58sunZ2Xhp6kBFdZPBZnwQKnqsSOJA0wCBw0PK8IYyEQGMg6f5OYbABZx4Y6vuUHHol2eMyGd6CHenhI3Om8qDnQohoOQn81ynNmk9xMevKo/3F6yb8WH7jns40IvzXIJ71Ta7ly71ntlJXnuJY54=; X-YMail-OSG: mTHUyUIVM1mgU9ZR.X8DIItOY1Tki0woL7G.ZGNFbCeSbY5 Q88PMFz79ybn3eq3v4L53sv4KsGc5MYkSTYkxTKifu.zGaaKuiZYeR5uctPY HerfShozMq1U8TgohMTkBC5R2E18b.Y6rD3QUnvXkubfNPdszWGwEN7yICja o.zCDSp_C_ZF6skbzGJCFnnRhIV6RtmRoUNnLjYCCCPh4ujdZvf5QlVyUsx. .e5YrIOi20Vw_u7UCV3PUYBIXvDWj4jyQxA9FK8_rK2IDm_WWeBDC5p4DsNN EWVS8ua_MkSVwjKepIMgpvho0Muxe1cs92aHROO7M5hCmUlGeSIcHfR8ZN89 84Fv_kRDgdiTty4xSt37ZkYoIdiPb89ADwHFpnYzFaypX9dY2I4Z4TV9GHNf dyesxzp._iZa5YymehGSQLdnw4N5wQyYImIvfOnphPaoOjxyXeqY.G9YCd.F SiKtH057RvWdwZp.TsHjAk6.8gAzt.x95AkZ7jROLpBdpKiuRvPlNjW268iA BUgGJTtXVIREABW4RrNJSGrvRgIp0ujiEClpXYk3fjDEtWclzmJXZ3ZjOu1F zFHNuVBwF2NtMbtVvOUwAWiWyS9e89JVzKSaSInqu4zV_bTv4ywE4P1LxomM gILykZ8HWzMJav.C_.OgkhplNHEGP6WLVL4JMx.AnG20hw1.OEsIe7ENZeNT hyVx6Ml_TlsXmaBVLZaL9.P0NcNVCfGguzyitGZof0xRlEl2aMmflAxa7.46 TuN.2g91R9SEKwz147O8jhOUSs.2D7.IXWn29yDgi9VL3KQ2dJJQFIrL9723 Tj2imKPHZ8Ud0ZzXwZVWvyRnAvw-- Received: from [83.154.246.188] by web172003.mail.ir2.yahoo.com via HTTP; Thu, 07 Feb 2013 21:56:00 GMT X-Rocket-MIMEInfo: 001.001, SXNzdWVzIGZvciBDQ0MgZGVwZW5kcyBvbiB5b3VyIFZpZGVvIENhcmQgdG9vLgoKLSBHb3QgYSBIRCA3OTA3MC4gSXQgd29ya2VkIGZvciBtZSB0byBhZGQgQ0NDIHdoaWxlIGluc3RhbGxpbmcgdGhlIDEzLjIgYmV0YSBkcml2ZXIuCgrCoMKgwqDCoMKgIFVuZm9ydHVuYXRlbHkgdGhlcmUgd2FzwqAgQlNPRCBpc3N1ZSB3aGVuIHJlYm9vdGluZyB0aGUgZG9tVS4KCsKgwqDCoMKgIEkgaGFkIHRvIGluc3RhbGwgLk5FVCA0IEZyYW1ld29yayBhbmQgQ0NDIG5vdyB3b3JrcyBhcyBleHBlY3RlZCA6KQoKLSBDQ0MBMAEBAQE- X-Mailer: YahooMailWebService/0.8.132.503 References: Message-ID: <1360274160.57405.YahooMailNeo@web172003.mail.ir2.yahoo.com> Date: Thu, 7 Feb 2013 21:56:00 +0000 (GMT) From: David TECHER To: Matthias , "xen-users@lists.xen.org" In-Reply-To: MIME-Version: 1.0 Subject: Re: [Xen-users] ATI/AMDs atikmpag.sys BSOD while vga passthrough X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: David TECHER List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============7627065345000737788==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============7627065345000737788== Content-Type: multipart/alternative; boundary="-661429482-1614994385-1360274160=:57405" ---661429482-1614994385-1360274160=:57405 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Issues for CCC depends on your Video Card too.=0A=0A- Got a HD 79070. It wo= rked for me to add CCC while installing the 13.2 beta driver.=0A=0A=A0=A0= =A0=A0=A0 Unfortunately there was=A0 BSOD issue when rebooting the domU.=0A= =0A=A0=A0=A0=A0 I had to install .NET 4 Framework and CCC now works as expe= cted :)=0A=0A- CCC is not supposed to work for HD 6870 but it worked for HD= 7970.=0A=0AFYI to fix atikmap.sys issue there is a well-known workaround w= ith something like=0A=0Ahttp://www.computertipsfree.com/fix-43029-atikmdag-= sys-blue-screen-bsod-in-windows-7/=0A=0Aexpand -r atikmdag.sy_ atikmdag.sys= =0A=0A=0ABut it doesn't work for me :(=0A=0AThe good news is that I've just= installed Crysis 3 beta demo. It works like a charm! =0A=0A=0A=0A=0A______= __________________________=0A De=A0: Matthias =0A=C0=A0: xen-users@lists.xen.org =0AEnvoy=E9 le : Jeudi 7 f=E9vrie= r 2013 20h14=0AObjet=A0: [Xen-users] ATI/AMDs atikmpag.sys BSOD while vga p= assthrough=0A =0AHi everyone=0A=0Asince I'm currently migrating from xm to = xl and now are also a victim=0Aof the said error, I started researching on = it and found that many=0Apeople had the issue but not many found solution a= nd behind this BSOD=0A(=3DBluescreen of Death), there are actually multiple= errors in hiding.=0A=0AWhat I would like to do is gather as much info as p= ossible in this=0Athread to form a kind of comprehensive guide to fixing th= is issue.=0A=0AFrom what i gathered so far, there are at least 3 different = problems=0Awith the same symptopms.=0A=0A1)=0ASituation: After booting the = dom0 and booting a windows domU with an=0AATI/AMD Card, Windows generally w= orks fine, but after rebooting the=0Asystem, or shutting down / restarting,= the Bluescreen occurs or the=0Aperformance massively below normal.=0AError= : Most likely this is cause the Card is not properly resetted (no=0AFLR [fu= nction level reset] )=0ASolution: If the domU reboots into BSOD, you are sc= rewed and have to=0Areboot the dom0. If it only degrades performance, eject= the card and=0Areinitialize to perform a manual reset. Or use the xm toolk= it.=0AStatus: Don't know if it is fixed yet=0ASource: http://lists.xen.org/= archives/html/xen-users/2012-02/msg00443.html=0A, http://wiki.xen.org/wiki/= Talk:Xen_VGA_Passthrough_Tested_Adapters=0A=0A2)=0ASituation: Booting a win= dows domU results in a BSOD when the CCC=0A(=3DCatalyst Control Center) ins= talled.=0AError: The CCC tries to set some specific settings (most likely= =0Aperformance tweaks) within the driver which the driver can't pass to=0At= he vga through passthrough mode. Result is a BSOD.=0ASolution: Deinstall th= e CCC in windows safe mode. The driver itself=0Aworks without it pretty fin= e.=0AStatus: Don't know if it is fixed yet=0ASource: http://lists.xen.org/a= rchives/html/xen-users/2012-03/msg00617.html=0ANote: I don't really know if= this holds for the Vision Engine Control=0Acenter, too. the VECC is basica= lly the same as the CCC, so i assume it=0Adoes. I simply haven't found any = things referencing it.=0A=0A3)=0ASituation: This is actually the issue I ha= ve. Things seem a lot more=0Arandom then the other ones. A BSOD happens bas= ically in 80% of booting=0Athe Windows domU. Which means, after rebooting d= om0, it mostly works.=0ARebooting or shutting down / starting the domU work= s sometimes (Once i=0Aachieved 6 consecutive reboots or shutdowns / starts = before the BSOD=0Ahappened) but after I get one Bluescreen, almost never (I= can't=0Aexactly remember if really 'never') comes up again. Of course I tr= ied=0Athe above solutions but this didn't helped me. I also tried different= =0Adifferent versions of the Catalyst driver (from 12/1 to 13/1) and=0Acurr= ent releases of xen-4.2-testing and xen-unsable. As I said, this=0Ais when = using the xl toolkit. I never had this issues using xm.=0AI thought this mi= ght belinked to me passing other PCI devices in=0Aaddition (I'm passing som= e USB controller to the domU) but even=0Adeactivating them didn't help. Wha= t I actually found helping boosting=0Athe success rate (but not solving the= overall issue) is deinstalling=0Aall VGA-Related AMD Driver. Windows then = runs on it's own VGA-Driver=0A(the graphic card is currectly identified and= this is an actual ati=0Adriver, so I'm not talking about some generic stan= dard vga driver. I=0Adon't know where is driver is coming from).=0AI've att= ached an analysis file i've gethered from the bluescreen crash=0Adump. I cr= eated it using BluescreenView. This is more for currectly=0Aidentifieng the= different BSODs, I guess.=0A=0A=0ASome Infos:=0AKernel: 3.7.4 kernel.org k= ernel without patches=0AXen: latest xen-unstable (but also tested with xen-= 4.2-testing)=0AProcessor: AMD Phenom 1090T=0AMainboard: Asus Crossfire IV= =0AVGA: Radeon HD5700 and Radeon HD5450=0ADriver: Currently running Catalys= t 13/1 but tested nearly everything=0Abetween 12/1 and 13/1=0A=0AError: Don= 't know yet=0ASolution: Don't know yet=0AStatus: unsolved=0ASource:=0A=0A= =0AOkay, so basically that's the story. It would be great if some people=0A= can complete and extend the list. Especially some who already fixed=0Athe i= ssue on their side. (And of course it would be great if someone=0Ahas an id= ea for my problem).=0A=0AThanks=0A=0A______________________________________= _________=0AXen-users mailing list=0AXen-users@lists.xen.org=0Ahttp://lists= .xen.org/xen-users ---661429482-1614994385-1360274160=:57405 Content-Type: text/html; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable
Issues for CCC depend= s on your Video Card too.

- Got a HD 79070. It worked for me to add = CCC while installing the 13.2 beta driver.

    &= nbsp; Unfortunately there was  BSOD issue when rebooting the domU.
=
     I had to install .NET 4 Framework and CCC now = works as expected :)

- CCC is not supposed to work for HD 6870 but i= t worked for HD 7970.

FYI to fix atikmap.sys issue there is a well-k= nown workaround with something like

http://www.computertipsfree.com/= fix-43029-atikmdag-sys-blue-screen-bsod-in-windows-7/

expand -r atikmdag.sy_ atikmdag.sys

But it doesn't work for me :(

<= div style=3D"color: rgb(0, 0, 0); font-size: 16px; font-family: times new roman,new york,times,serif; background-color: transparent; font-style: nor= mal;">The good news is that I've just installed Crysis 3 beta demo. It work= s like a charm!


= De : Matthias <matt= hias.kannenberg@googlemail.com>
Envoy=E9 le : Jeudi 7 f=E9vrier 2013 20h14
Objet : [Xen-users] ATI/AMDs a= tikmpag.sys BSOD while vga passthrough

Hi everyone
since I'm currently migrating from xm to xl and now are also a victim=
of the said error, I started researching on it and found that many
p= eople had the issue but not many found solution and behind this BSOD
(= =3DBluescreen of Death), there are actually multiple errors in hiding.
<= br>What I would like to do is gather as much info as possible in this
th= read to form a kind of comprehensive guide to fixing this issue.

Fro= m what i gathered so far, there are at least 3 different problems
with t= he same symptopms.

1)
Situation: After booting the dom0 and booti= ng a windows domU with an
ATI/AMD Card, Windows generally works fine, bu= t after rebooting the
system, or shutting down / restarting, the Bluescreen occurs or the
performance massively below normal.
Error: = Most likely this is cause the Card is not properly resetted (no
FLR [fun= ction level reset] )
Solution: If the domU reboots into BSOD, you are sc= rewed and have to
reboot the dom0. If it only degrades performance, ejec= t the card and
reinitialize to perform a manual reset. Or use the xm too= lkit.
Status: Don't know if it is fixed yet
Source: http://lists.xen.org/archives/html/xen-users/2012-02/msg00443.html=
, http://wiki.xen.org/wiki/Talk:Xen_VGA_Passthroug= h_Tested_Adapters

2)
Situation: Booting a windows domU result= s in a BSOD when the CCC
(=3DCatalyst Control Center) installed.
Erro= r: The CCC tries to set some specific settings (most likely
performance tweaks) within the driver which the driver can't pass to
the vga throug= h passthrough mode. Result is a BSOD.
Solution: Deinstall the CCC in win= dows safe mode. The driver itself
works without it pretty fine.
Statu= s: Don't know if it is fixed yet
Source: http://li= sts.xen.org/archives/html/xen-users/2012-03/msg00617.html
Note: I do= n't really know if this holds for the Vision Engine Control
center, too.= the VECC is basically the same as the CCC, so i assume it
does. I simpl= y haven't found any things referencing it.

3)
Situation: This is = actually the issue I have. Things seem a lot more
random then the other = ones. A BSOD happens basically in 80% of booting
the Windows domU. Which= means, after rebooting dom0, it mostly works.
Rebooting or shutting dow= n / starting the domU works sometimes (Once i
achieved 6 consecutive reboots or shutdowns / starts before the BSOD
happened) but after I get= one Bluescreen, almost never (I can't
exactly remember if really 'never= ') comes up again. Of course I tried
the above solutions but this didn't= helped me. I also tried different
different versions of the Catalyst dr= iver (from 12/1 to 13/1) and
current releases of xen-4.2-testing and xen= -unsable. As I said, this
is when using the xl toolkit. I never had this= issues using xm.
I thought this might belinked to me passing other PCI = devices in
addition (I'm passing some USB controller to the domU) but ev= en
deactivating them didn't help. What I actually found helping boosting=
the success rate (but not solving the overall issue) is deinstallingall VGA-Related AMD Driver. Windows then runs on it's own VGA-Driver
(t= he graphic card is currectly identified and this is an actual ati
driver= , so I'm not talking about some generic standard vga driver. I
don't know where is driver is coming from).
I've attached an analy= sis file i've gethered from the bluescreen crash
dump. I created it usin= g BluescreenView. This is more for currectly
identifieng the different B= SODs, I guess.


Some Infos:
Kernel: 3.7.4 kernel.org kernel wi= thout patches
Xen: latest xen-unstable (but also tested with xen-4.2-tes= ting)
Processor: AMD Phenom 1090T
Mainboard: Asus Crossfire IV
VGA= : Radeon HD5700 and Radeon HD5450
Driver: Currently running Catalyst 13/= 1 but tested nearly everything
between 12/1 and 13/1

Error: Don't= know yet
Solution: Don't know yet
Status: unsolved
Source:

Okay, so basically that's the story. It would be great if some people<= br>can complete and extend the list. Especially some who already fixed
t= he issue on their side. (And of course it would be great if someone
has = an idea for my problem).

Thanks

___________________________________________= ____
Xen-users mailing list
Xen-users@lists.xen.orghttp://lists.= xen.org/xen-users

---661429482-1614994385-1360274160=:57405-- --===============7627065345000737788== 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 --===============7627065345000737788==-- From xen-users-bounces@lists.xen.org Thu Feb 07 21:57:17 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 07 Feb 2013 21:57: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 1U3ZRx-0003fs-63; Thu, 07 Feb 2013 21:56:09 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U3ZRv-0003fk-9G for xen-users@lists.xen.org; Thu, 07 Feb 2013 21:56:07 +0000 Received: from [85.158.139.83:31411] by server-13.bemta-5.messagelabs.com id 62/5D-06769-6F224115; Thu, 07 Feb 2013 21:56:06 +0000 X-Env-Sender: davidtecher@yahoo.fr X-Msg-Ref: server-2.tower-182.messagelabs.com!1360274160!30913247!1 X-Originating-IP: [77.238.189.68] 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,ML_RADAR_SPEW_LINKS_6, spamassassin: X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 11289 invoked from network); 7 Feb 2013 21:56:04 -0000 Received: from nm15.bullet.mail.ird.yahoo.com (HELO nm15.bullet.mail.ird.yahoo.com) (77.238.189.68) by server-2.tower-182.messagelabs.com with SMTP; 7 Feb 2013 21:56:04 -0000 Received: from [212.82.105.245] by nm15.bullet.mail.ird.yahoo.com with NNFMP; 07 Feb 2013 21:56:00 -0000 Received: from [212.82.108.118] by tm17.bullet.mail.ird.yahoo.com with NNFMP; 07 Feb 2013 21:56:00 -0000 Received: from [127.0.0.1] by omp1027.mail.ird.yahoo.com with NNFMP; 07 Feb 2013 21:56:00 -0000 X-Yahoo-Newman-Property: ymail-3 X-Yahoo-Newman-Id: 835528.70834.bm@omp1027.mail.ird.yahoo.com Received: (qmail 66079 invoked by uid 60001); 7 Feb 2013 21:56:00 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.fr; s=s1024; t=1360274160; bh=H4KfS4nnZ53O32XKfWI67KbEFX2QwZvbSQu2g35OYQY=; h=X-YMail-OSG:Received:X-Rocket-MIMEInfo:X-Mailer:References:Message-ID:Date:From:Reply-To:Subject:To:In-Reply-To:MIME-Version:Content-Type; b=rJ2DGsojetVUyg7xsxluuxlg0khVtBioIciUBBsMWp3LzBOkD6uoVDhLP6h84drB6+Pk4xwqddzHPqrTJC53TMbjBMIIB0PUcECfYtZCpOh6Zlb3zkW3lQ1LSY0KKzLr4topLt+Mel5j5l2V/RGwf804wDjwa8XZA6A4BE6ffsA= DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.fr; h=X-YMail-OSG:Received:X-Rocket-MIMEInfo:X-Mailer:References:Message-ID:Date:From:Reply-To:Subject:To:In-Reply-To:MIME-Version:Content-Type; b=29X9eQbJZOX2s0VUPU0EX/58sunZ2Xhp6kBFdZPBZnwQKnqsSOJA0wCBw0PK8IYyEQGMg6f5OYbABZx4Y6vuUHHol2eMyGd6CHenhI3Om8qDnQohoOQn81ynNmk9xMevKo/3F6yb8WH7jns40IvzXIJ71Ta7ly71ntlJXnuJY54=; X-YMail-OSG: mTHUyUIVM1mgU9ZR.X8DIItOY1Tki0woL7G.ZGNFbCeSbY5 Q88PMFz79ybn3eq3v4L53sv4KsGc5MYkSTYkxTKifu.zGaaKuiZYeR5uctPY HerfShozMq1U8TgohMTkBC5R2E18b.Y6rD3QUnvXkubfNPdszWGwEN7yICja o.zCDSp_C_ZF6skbzGJCFnnRhIV6RtmRoUNnLjYCCCPh4ujdZvf5QlVyUsx. .e5YrIOi20Vw_u7UCV3PUYBIXvDWj4jyQxA9FK8_rK2IDm_WWeBDC5p4DsNN EWVS8ua_MkSVwjKepIMgpvho0Muxe1cs92aHROO7M5hCmUlGeSIcHfR8ZN89 84Fv_kRDgdiTty4xSt37ZkYoIdiPb89ADwHFpnYzFaypX9dY2I4Z4TV9GHNf dyesxzp._iZa5YymehGSQLdnw4N5wQyYImIvfOnphPaoOjxyXeqY.G9YCd.F SiKtH057RvWdwZp.TsHjAk6.8gAzt.x95AkZ7jROLpBdpKiuRvPlNjW268iA BUgGJTtXVIREABW4RrNJSGrvRgIp0ujiEClpXYk3fjDEtWclzmJXZ3ZjOu1F zFHNuVBwF2NtMbtVvOUwAWiWyS9e89JVzKSaSInqu4zV_bTv4ywE4P1LxomM gILykZ8HWzMJav.C_.OgkhplNHEGP6WLVL4JMx.AnG20hw1.OEsIe7ENZeNT hyVx6Ml_TlsXmaBVLZaL9.P0NcNVCfGguzyitGZof0xRlEl2aMmflAxa7.46 TuN.2g91R9SEKwz147O8jhOUSs.2D7.IXWn29yDgi9VL3KQ2dJJQFIrL9723 Tj2imKPHZ8Ud0ZzXwZVWvyRnAvw-- Received: from [83.154.246.188] by web172003.mail.ir2.yahoo.com via HTTP; Thu, 07 Feb 2013 21:56:00 GMT X-Rocket-MIMEInfo: 001.001, SXNzdWVzIGZvciBDQ0MgZGVwZW5kcyBvbiB5b3VyIFZpZGVvIENhcmQgdG9vLgoKLSBHb3QgYSBIRCA3OTA3MC4gSXQgd29ya2VkIGZvciBtZSB0byBhZGQgQ0NDIHdoaWxlIGluc3RhbGxpbmcgdGhlIDEzLjIgYmV0YSBkcml2ZXIuCgrCoMKgwqDCoMKgIFVuZm9ydHVuYXRlbHkgdGhlcmUgd2FzwqAgQlNPRCBpc3N1ZSB3aGVuIHJlYm9vdGluZyB0aGUgZG9tVS4KCsKgwqDCoMKgIEkgaGFkIHRvIGluc3RhbGwgLk5FVCA0IEZyYW1ld29yayBhbmQgQ0NDIG5vdyB3b3JrcyBhcyBleHBlY3RlZCA6KQoKLSBDQ0MBMAEBAQE- X-Mailer: YahooMailWebService/0.8.132.503 References: Message-ID: <1360274160.57405.YahooMailNeo@web172003.mail.ir2.yahoo.com> Date: Thu, 7 Feb 2013 21:56:00 +0000 (GMT) From: David TECHER To: Matthias , "xen-users@lists.xen.org" In-Reply-To: MIME-Version: 1.0 Subject: Re: [Xen-users] ATI/AMDs atikmpag.sys BSOD while vga passthrough X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: David TECHER List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============7627065345000737788==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============7627065345000737788== Content-Type: multipart/alternative; boundary="-661429482-1614994385-1360274160=:57405" ---661429482-1614994385-1360274160=:57405 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Issues for CCC depends on your Video Card too.=0A=0A- Got a HD 79070. It wo= rked for me to add CCC while installing the 13.2 beta driver.=0A=0A=A0=A0= =A0=A0=A0 Unfortunately there was=A0 BSOD issue when rebooting the domU.=0A= =0A=A0=A0=A0=A0 I had to install .NET 4 Framework and CCC now works as expe= cted :)=0A=0A- CCC is not supposed to work for HD 6870 but it worked for HD= 7970.=0A=0AFYI to fix atikmap.sys issue there is a well-known workaround w= ith something like=0A=0Ahttp://www.computertipsfree.com/fix-43029-atikmdag-= sys-blue-screen-bsod-in-windows-7/=0A=0Aexpand -r atikmdag.sy_ atikmdag.sys= =0A=0A=0ABut it doesn't work for me :(=0A=0AThe good news is that I've just= installed Crysis 3 beta demo. It works like a charm! =0A=0A=0A=0A=0A______= __________________________=0A De=A0: Matthias =0A=C0=A0: xen-users@lists.xen.org =0AEnvoy=E9 le : Jeudi 7 f=E9vrie= r 2013 20h14=0AObjet=A0: [Xen-users] ATI/AMDs atikmpag.sys BSOD while vga p= assthrough=0A =0AHi everyone=0A=0Asince I'm currently migrating from xm to = xl and now are also a victim=0Aof the said error, I started researching on = it and found that many=0Apeople had the issue but not many found solution a= nd behind this BSOD=0A(=3DBluescreen of Death), there are actually multiple= errors in hiding.=0A=0AWhat I would like to do is gather as much info as p= ossible in this=0Athread to form a kind of comprehensive guide to fixing th= is issue.=0A=0AFrom what i gathered so far, there are at least 3 different = problems=0Awith the same symptopms.=0A=0A1)=0ASituation: After booting the = dom0 and booting a windows domU with an=0AATI/AMD Card, Windows generally w= orks fine, but after rebooting the=0Asystem, or shutting down / restarting,= the Bluescreen occurs or the=0Aperformance massively below normal.=0AError= : Most likely this is cause the Card is not properly resetted (no=0AFLR [fu= nction level reset] )=0ASolution: If the domU reboots into BSOD, you are sc= rewed and have to=0Areboot the dom0. If it only degrades performance, eject= the card and=0Areinitialize to perform a manual reset. Or use the xm toolk= it.=0AStatus: Don't know if it is fixed yet=0ASource: http://lists.xen.org/= archives/html/xen-users/2012-02/msg00443.html=0A, http://wiki.xen.org/wiki/= Talk:Xen_VGA_Passthrough_Tested_Adapters=0A=0A2)=0ASituation: Booting a win= dows domU results in a BSOD when the CCC=0A(=3DCatalyst Control Center) ins= talled.=0AError: The CCC tries to set some specific settings (most likely= =0Aperformance tweaks) within the driver which the driver can't pass to=0At= he vga through passthrough mode. Result is a BSOD.=0ASolution: Deinstall th= e CCC in windows safe mode. The driver itself=0Aworks without it pretty fin= e.=0AStatus: Don't know if it is fixed yet=0ASource: http://lists.xen.org/a= rchives/html/xen-users/2012-03/msg00617.html=0ANote: I don't really know if= this holds for the Vision Engine Control=0Acenter, too. the VECC is basica= lly the same as the CCC, so i assume it=0Adoes. I simply haven't found any = things referencing it.=0A=0A3)=0ASituation: This is actually the issue I ha= ve. Things seem a lot more=0Arandom then the other ones. A BSOD happens bas= ically in 80% of booting=0Athe Windows domU. Which means, after rebooting d= om0, it mostly works.=0ARebooting or shutting down / starting the domU work= s sometimes (Once i=0Aachieved 6 consecutive reboots or shutdowns / starts = before the BSOD=0Ahappened) but after I get one Bluescreen, almost never (I= can't=0Aexactly remember if really 'never') comes up again. Of course I tr= ied=0Athe above solutions but this didn't helped me. I also tried different= =0Adifferent versions of the Catalyst driver (from 12/1 to 13/1) and=0Acurr= ent releases of xen-4.2-testing and xen-unsable. As I said, this=0Ais when = using the xl toolkit. I never had this issues using xm.=0AI thought this mi= ght belinked to me passing other PCI devices in=0Aaddition (I'm passing som= e USB controller to the domU) but even=0Adeactivating them didn't help. Wha= t I actually found helping boosting=0Athe success rate (but not solving the= overall issue) is deinstalling=0Aall VGA-Related AMD Driver. Windows then = runs on it's own VGA-Driver=0A(the graphic card is currectly identified and= this is an actual ati=0Adriver, so I'm not talking about some generic stan= dard vga driver. I=0Adon't know where is driver is coming from).=0AI've att= ached an analysis file i've gethered from the bluescreen crash=0Adump. I cr= eated it using BluescreenView. This is more for currectly=0Aidentifieng the= different BSODs, I guess.=0A=0A=0ASome Infos:=0AKernel: 3.7.4 kernel.org k= ernel without patches=0AXen: latest xen-unstable (but also tested with xen-= 4.2-testing)=0AProcessor: AMD Phenom 1090T=0AMainboard: Asus Crossfire IV= =0AVGA: Radeon HD5700 and Radeon HD5450=0ADriver: Currently running Catalys= t 13/1 but tested nearly everything=0Abetween 12/1 and 13/1=0A=0AError: Don= 't know yet=0ASolution: Don't know yet=0AStatus: unsolved=0ASource:=0A=0A= =0AOkay, so basically that's the story. It would be great if some people=0A= can complete and extend the list. Especially some who already fixed=0Athe i= ssue on their side. (And of course it would be great if someone=0Ahas an id= ea for my problem).=0A=0AThanks=0A=0A______________________________________= _________=0AXen-users mailing list=0AXen-users@lists.xen.org=0Ahttp://lists= .xen.org/xen-users ---661429482-1614994385-1360274160=:57405 Content-Type: text/html; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable
Issues for CCC depend= s on your Video Card too.

- Got a HD 79070. It worked for me to add = CCC while installing the 13.2 beta driver.

    &= nbsp; Unfortunately there was  BSOD issue when rebooting the domU.
=
     I had to install .NET 4 Framework and CCC now = works as expected :)

- CCC is not supposed to work for HD 6870 but i= t worked for HD 7970.

FYI to fix atikmap.sys issue there is a well-k= nown workaround with something like

http://www.computertipsfree.com/= fix-43029-atikmdag-sys-blue-screen-bsod-in-windows-7/

expand -r atikmdag.sy_ atikmdag.sys

But it doesn't work for me :(

<= div style=3D"color: rgb(0, 0, 0); font-size: 16px; font-family: times new roman,new york,times,serif; background-color: transparent; font-style: nor= mal;">The good news is that I've just installed Crysis 3 beta demo. It work= s like a charm!


= De : Matthias <matt= hias.kannenberg@googlemail.com>
Envoy=E9 le : Jeudi 7 f=E9vrier 2013 20h14
Objet : [Xen-users] ATI/AMDs a= tikmpag.sys BSOD while vga passthrough

Hi everyone
since I'm currently migrating from xm to xl and now are also a victim=
of the said error, I started researching on it and found that many
p= eople had the issue but not many found solution and behind this BSOD
(= =3DBluescreen of Death), there are actually multiple errors in hiding.
<= br>What I would like to do is gather as much info as possible in this
th= read to form a kind of comprehensive guide to fixing this issue.

Fro= m what i gathered so far, there are at least 3 different problems
with t= he same symptopms.

1)
Situation: After booting the dom0 and booti= ng a windows domU with an
ATI/AMD Card, Windows generally works fine, bu= t after rebooting the
system, or shutting down / restarting, the Bluescreen occurs or the
performance massively below normal.
Error: = Most likely this is cause the Card is not properly resetted (no
FLR [fun= ction level reset] )
Solution: If the domU reboots into BSOD, you are sc= rewed and have to
reboot the dom0. If it only degrades performance, ejec= t the card and
reinitialize to perform a manual reset. Or use the xm too= lkit.
Status: Don't know if it is fixed yet
Source: http://lists.xen.org/archives/html/xen-users/2012-02/msg00443.html=
, http://wiki.xen.org/wiki/Talk:Xen_VGA_Passthroug= h_Tested_Adapters

2)
Situation: Booting a windows domU result= s in a BSOD when the CCC
(=3DCatalyst Control Center) installed.
Erro= r: The CCC tries to set some specific settings (most likely
performance tweaks) within the driver which the driver can't pass to
the vga throug= h passthrough mode. Result is a BSOD.
Solution: Deinstall the CCC in win= dows safe mode. The driver itself
works without it pretty fine.
Statu= s: Don't know if it is fixed yet
Source: http://li= sts.xen.org/archives/html/xen-users/2012-03/msg00617.html
Note: I do= n't really know if this holds for the Vision Engine Control
center, too.= the VECC is basically the same as the CCC, so i assume it
does. I simpl= y haven't found any things referencing it.

3)
Situation: This is = actually the issue I have. Things seem a lot more
random then the other = ones. A BSOD happens basically in 80% of booting
the Windows domU. Which= means, after rebooting dom0, it mostly works.
Rebooting or shutting dow= n / starting the domU works sometimes (Once i
achieved 6 consecutive reboots or shutdowns / starts before the BSOD
happened) but after I get= one Bluescreen, almost never (I can't
exactly remember if really 'never= ') comes up again. Of course I tried
the above solutions but this didn't= helped me. I also tried different
different versions of the Catalyst dr= iver (from 12/1 to 13/1) and
current releases of xen-4.2-testing and xen= -unsable. As I said, this
is when using the xl toolkit. I never had this= issues using xm.
I thought this might belinked to me passing other PCI = devices in
addition (I'm passing some USB controller to the domU) but ev= en
deactivating them didn't help. What I actually found helping boosting=
the success rate (but not solving the overall issue) is deinstallingall VGA-Related AMD Driver. Windows then runs on it's own VGA-Driver
(t= he graphic card is currectly identified and this is an actual ati
driver= , so I'm not talking about some generic standard vga driver. I
don't know where is driver is coming from).
I've attached an analy= sis file i've gethered from the bluescreen crash
dump. I created it usin= g BluescreenView. This is more for currectly
identifieng the different B= SODs, I guess.


Some Infos:
Kernel: 3.7.4 kernel.org kernel wi= thout patches
Xen: latest xen-unstable (but also tested with xen-4.2-tes= ting)
Processor: AMD Phenom 1090T
Mainboard: Asus Crossfire IV
VGA= : Radeon HD5700 and Radeon HD5450
Driver: Currently running Catalyst 13/= 1 but tested nearly everything
between 12/1 and 13/1

Error: Don't= know yet
Solution: Don't know yet
Status: unsolved
Source:

Okay, so basically that's the story. It would be great if some people<= br>can complete and extend the list. Especially some who already fixed
t= he issue on their side. (And of course it would be great if someone
has = an idea for my problem).

Thanks

___________________________________________= ____
Xen-users mailing list
Xen-users@lists.xen.orghttp://lists.= xen.org/xen-users

---661429482-1614994385-1360274160=:57405-- --===============7627065345000737788== 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 --===============7627065345000737788==-- From xen-users-bounces@lists.xen.org Thu Feb 07 22:18:02 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 07 Feb 2013 22:18: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 1U3ZmC-0004ag-BO; Thu, 07 Feb 2013 22:17:04 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U3ZmA-0004ab-PI for xen-users@lists.xen.org; Thu, 07 Feb 2013 22:17:03 +0000 Received: from [193.109.254.147:30568] by server-11.bemta-14.messagelabs.com id D4/CE-30685-ED724115; Thu, 07 Feb 2013 22:17:02 +0000 X-Env-Sender: cdelorme@gmail.com X-Msg-Ref: server-3.tower-27.messagelabs.com!1360275416!9595693!1 X-Originating-IP: [209.85.212.43] 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.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 20236 invoked from network); 7 Feb 2013 22:16:57 -0000 Received: from mail-vb0-f43.google.com (HELO mail-vb0-f43.google.com) (209.85.212.43) by server-3.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 7 Feb 2013 22:16:57 -0000 Received: by mail-vb0-f43.google.com with SMTP id fs19so1961861vbb.30 for ; Thu, 07 Feb 2013 14:16:55 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=6HqDW18j/VgOQ/Ho5yGES9FJvGRj+bksf180aX3oMco=; b=BW7xKRNIsq4bi2CYVRY3Iw+GTjTKS0fstj95Dyaahb5n8z28AI6Ep7Sc7m7fRGxwQ9 Aeu8IwVexYf0qZeCGeZdhc3xwftgNATpuPo5hf8fU0gRL4epM+jXcwFQK+eIAdE+z1tu ItSGh6tlwAJUvsx9QmZr484nsdCFqDYfSEc6ZoEnMQjhLH9SfCG+eSWgLzoxqEuiWpHs V0wP/WFtwBkPXBlbwgNorQPaWxGnO7c06yAtSZYqVoZMdPhejbxbXRZ8BYIB6VxatlY8 ookKQEh+qTv7gZF8nk0Ufauvdw1QEzGkRtMYN08U71v4d3fZ1qdd9ca9R3Ve6CC4uGrY fQIw== MIME-Version: 1.0 X-Received: by 10.52.19.65 with SMTP id c1mr3457493vde.36.1360275415799; Thu, 07 Feb 2013 14:16:55 -0800 (PST) Received: by 10.58.32.199 with HTTP; Thu, 7 Feb 2013 14:16:55 -0800 (PST) In-Reply-To: <1360274160.57405.YahooMailNeo@web172003.mail.ir2.yahoo.com> References: <1360274160.57405.YahooMailNeo@web172003.mail.ir2.yahoo.com> Date: Thu, 7 Feb 2013 17:16:55 -0500 Message-ID: From: Casey DeLorme To: David TECHER Cc: "xen-users@lists.xen.org" , Matthias Subject: Re: [Xen-users] ATI/AMDs atikmpag.sys BSOD while 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="===============2529276979055605528==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============2529276979055605528== Content-Type: multipart/alternative; boundary=bcaec5040b9af497f804d529cc67 --bcaec5040b9af497f804d529cc67 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable I have an HD 6870 and working CCC, tested on both Windows 7 and windows 8. Don't have any BSoD's either. I only had problems with CCC and drivers when I attempted to install or update drivers without having freshly rebooted or ejected the card. Unfortunately Windows 8 attempts to auto-install the drivers at boot time and this caused some headaches during my first go at it. I experience performance problems after rebooting the HVM, to fix it I just eject the card from the "Safely Remove Hardware and Eject Media" icon. On Thu, Feb 7, 2013 at 4:56 PM, David TECHER wrote: > Issues for CCC depends on your Video Card too. > > - Got a HD 79070. It worked for me to add CCC while installing the 13.2 > beta driver. > > Unfortunately there was BSOD issue when rebooting the domU. > > I had to install .NET 4 Framework and CCC now works as expected :) > > - CCC is not supposed to work for HD 6870 but it worked for HD 7970. > > FYI to fix atikmap.sys issue there is a well-known workaround with > something like > > > http://www.computertipsfree.com/fix-43029-atikmdag-sys-blue-screen-bsod-i= n-windows-7/ > > expand -r atikmdag.sy_ atikmdag.sys > > But it doesn't work for me :( > > The good news is that I've just installed Crysis 3 beta demo. It works > like a charm! > > > ------------------------------ > *De :* Matthias > *=C3=80 :* xen-users@lists.xen.org > *Envoy=C3=A9 le :* Jeudi 7 f=C3=A9vrier 2013 20h14 > *Objet :* [Xen-users] ATI/AMDs atikmpag.sys BSOD while vga passthrough > > Hi everyone > > since I'm currently migrating from xm to xl and now are also a victim > of the said error, I started researching on it and found that many > people had the issue but not many found solution and behind this BSOD > (=3DBluescreen of Death), there are actually multiple errors in hiding. > > What I would like to do is gather as much info as possible in this > thread to form a kind of comprehensive guide to fixing this issue. > > From what i gathered so far, there are at least 3 different problems > with the same symptopms. > > 1) > Situation: After booting the dom0 and booting a windows domU with an > ATI/AMD Card, Windows generally works fine, but after rebooting the > system, or shutting down / restarting, the Bluescreen occurs or the > performance massively below normal. > Error: Most likely this is cause the Card is not properly resetted (no > FLR [function level reset] ) > Solution: If the domU reboots into BSOD, you are screwed and have to > reboot the dom0. If it only degrades performance, eject the card and > reinitialize to perform a manual reset. Or use the xm toolkit. > Status: Don't know if it is fixed yet > Source: http://lists.xen.org/archives/html/xen-users/2012-02/msg00443.htm= l > , http://wiki.xen.org/wiki/Talk:Xen_VGA_Passthrough_Tested_Adapters > > 2) > Situation: Booting a windows domU results in a BSOD when the CCC > (=3DCatalyst Control Center) installed. > Error: The CCC tries to set some specific settings (most likely > performance tweaks) within the driver which the driver can't pass to > the vga through passthrough mode. Result is a BSOD. > Solution: Deinstall the CCC in windows safe mode. The driver itself > works without it pretty fine. > Status: Don't know if it is fixed yet > Source: http://lists.xen.org/archives/html/xen-users/2012-03/msg00617.htm= l > Note: I don't really know if this holds for the Vision Engine Control > center, too. the VECC is basically the same as the CCC, so i assume it > does. I simply haven't found any things referencing it. > > 3) > Situation: This is actually the issue I have. Things seem a lot more > random then the other ones. A BSOD happens basically in 80% of booting > the Windows domU. Which means, after rebooting dom0, it mostly works. > Rebooting or shutting down / starting the domU works sometimes (Once i > achieved 6 consecutive reboots or shutdowns / starts before the BSOD > happened) but after I get one Bluescreen, almost never (I can't > exactly remember if really 'never') comes up again. Of course I tried > the above solutions but this didn't helped me. I also tried different > different versions of the Catalyst driver (from 12/1 to 13/1) and > current releases of xen-4.2-testing and xen-unsable. As I said, this > is when using the xl toolkit. I never had this issues using xm. > I thought this might belinked to me passing other PCI devices in > addition (I'm passing some USB controller to the domU) but even > deactivating them didn't help. What I actually found helping boosting > the success rate (but not solving the overall issue) is deinstalling > all VGA-Related AMD Driver. Windows then runs on it's own VGA-Driver > (the graphic card is currectly identified and this is an actual ati > driver, so I'm not talking about some generic standard vga driver. I > don't know where is driver is coming from). > I've attached an analysis file i've gethered from the bluescreen crash > dump. I created it using BluescreenView. This is more for currectly > identifieng the different BSODs, I guess. > > > Some Infos: > Kernel: 3.7.4 kernel.org kernel without patches > Xen: latest xen-unstable (but also tested with xen-4.2-testing) > Processor: AMD Phenom 1090T > Mainboard: Asus Crossfire IV > VGA: Radeon HD5700 and Radeon HD5450 > Driver: Currently running Catalyst 13/1 but tested nearly everything > between 12/1 and 13/1 > > Error: Don't know yet > Solution: Don't know yet > Status: unsolved > Source: > > > Okay, so basically that's the story. It would be great if some people > can complete and extend the list. Especially some who already fixed > the issue on their side. (And of course it would be great if someone > has an idea for my problem). > > Thanks > > _______________________________________________ > 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 > --bcaec5040b9af497f804d529cc67 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
I have an HD 6870 and working CCC, tested on both Windows = 7 and windows 8. =C2=A0Don't have any BSoD's either.
=
I only had problems with CCC and drivers when I attemp= ted to install or update drivers without having freshly rebooted or ejected= the card.

Unfortunately Windows 8 attempts to auto-in= stall the drivers at boot time and this caused some headaches during my fir= st go at it.

I experience performance = problems after rebooting the HVM, to fix it I just eject the card from the = "Safely Remove Hardware and Eject Media" icon.


On Thu,= Feb 7, 2013 at 4:56 PM, David TECHER <davidtecher@yahoo.fr> wrote:
Issues for CCC depends on your Vide= o Card too.

- Got a HD 79070. It worked for me to add CCC while installing the 13.2= beta driver.

=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 Unfortunately there was= =C2=A0 BSOD issue when rebooting the domU.

=C2=A0=C2=A0=C2=A0=C2=A0 = I had to install .NET 4 Framework and CCC now works as expected :)

- CCC is not supposed to work for HD 6870 but it worked for HD 7970.
FYI to fix atikmap.sys issue there is a well-known workaround with som= ething like

http://www.comp= utertipsfree.com/fix-43029-atikmdag-sys-blue-screen-bsod-in-windows-7/<= br>
expand -r atikmdag.sy_ atikmdag.sys

But it doesn't work for me :(
=
The good news is that I've just installed Crysis 3 beta demo. It works = like a charm!


De=C2=A0: Matthias <matthias.kannenberg@= googlemail.com>
=C3=80=C2=A0: xen-users@lists.xen.org=
Envoy=C3=A9 le : Jeudi= 7 f=C3=A9vrier 2013 20h14
Objet=C2=A0: [Xen-users] AT= I/AMDs atikmpag.sys BSOD while vga passthrough

Hi everyone

since I'm currently migrating from= xm to xl and now are also a victim
of the said error, I started researching on it and found that many
peopl= e had the issue but not many found solution and behind this BSOD
(=3DBlu= escreen of Death), there are actually multiple errors in hiding.

Wha= t I would like to do is gather as much info as possible in this
thread to form a kind of comprehensive guide to fixing this issue.

F= rom what i gathered so far, there are at least 3 different problems
with= the same symptopms.

1)
Situation: After booting the dom0 and boo= ting a windows domU with an
ATI/AMD Card, Windows generally works fine, but after rebooting the
syst= em, or shutting down / restarting, the Bluescreen occurs or the
performance massively below normal.
Error: = Most likely this is cause the Card is not properly resetted (no
FLR [fun= ction level reset] )
Solution: If the domU reboots into BSOD, you are sc= rewed and have to
reboot the dom0. If it only degrades performance, eject the card and
rei= nitialize to perform a manual reset. Or use the xm toolkit.
Status: Don&= #39;t know if it is fixed yet
Source: http://lists= .xen.org/archives/html/xen-users/2012-02/msg00443.html
, http://wiki.xen.org/wiki/Talk:Xen_VGA_Passthrough_Te= sted_Adapters

2)
Situation: Booting a windows domU results in= a BSOD when the CCC
(=3DCatalyst Control Center) installed.
Error: The CCC tries to set some= specific settings (most likely
performance tweaks) within the driver which the driver can't pass to
the vga th= rough passthrough mode. Result is a BSOD.
Solution: Deinstall the CCC in= windows safe mode. The driver itself
works without it pretty fine.
Status: Don't know if it is fixed yet
Source: = http://lists.xen.org/archives/html/xen-users/2012-03/msg00617.html
N= ote: I don't really know if this holds for the Vision Engine Control center, too. the VECC is basically the same as the CCC, so i assume it
d= oes. I simply haven't found any things referencing it.

3)
Sit= uation: This is actually the issue I have. Things seem a lot more
random= then the other ones. A BSOD happens basically in 80% of booting
the Windows domU. Which means, after rebooting dom0, it mostly works.
Re= booting or shutting down / starting the domU works sometimes (Once i
ach= ieved 6 consecutive reboots or shutdowns / starts before the BSOD
happened) but after I get= one Bluescreen, almost never (I can't
exactly remember if really &#= 39;never') comes up again. Of course I tried
the above solutions but= this didn't helped me. I also tried different
different versions of the Catalyst driver (from 12/1 to 13/1) and
curren= t releases of xen-4.2-testing and xen-unsable. As I said, this
is when u= sing the xl toolkit. I never had this issues using xm.
I thought this mi= ght belinked to me passing other PCI devices in
addition (I'm passing some USB controller to the domU) but even
deac= tivating them didn't help. What I actually found helping boosting
th= e success rate (but not solving the overall issue) is deinstalling
all V= GA-Related AMD Driver. Windows then runs on it's own VGA-Driver
(the graphic card is currectly identified and this is an actual ati
driv= er, so I'm not talking about some generic standard vga driver. I
don't know where is driver is coming from).
I've attached = an analysis file i've gethered from the bluescreen crash
dump. I cre= ated it using BluescreenView. This is more for currectly
identifieng the= different BSODs, I guess.


Some Infos:
Kernel: 3.7.4 kernel.org kernel without patches
Xen: latest xen-unstab= le (but also tested with xen-4.2-testing)
Processor: AMD Phenom 1090TMainboard: Asus Crossfire IV
VGA: Radeon HD5700 and Radeon HD5450
Driver: Currently running Catalyst = 13/1 but tested nearly everything
between 12/1 and 13/1

Error: Do= n't know yet
Solution: Don't know yet
Status: unsolved
Source:


Okay, so basically that's the story. It would be gre= at if some people
can complete and extend the list. Especially some who = already fixed
the issue on their side. (And of course it would be great = if someone
has an idea for my problem).

Thanks

_______________________________= ________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.xen.org/xen-u= sers


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

--bcaec5040b9af497f804d529cc67-- --===============2529276979055605528== 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 --===============2529276979055605528==-- From xen-users-bounces@lists.xen.org Thu Feb 07 22:18:02 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 07 Feb 2013 22:18: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 1U3ZmC-0004ag-BO; Thu, 07 Feb 2013 22:17:04 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U3ZmA-0004ab-PI for xen-users@lists.xen.org; Thu, 07 Feb 2013 22:17:03 +0000 Received: from [193.109.254.147:30568] by server-11.bemta-14.messagelabs.com id D4/CE-30685-ED724115; Thu, 07 Feb 2013 22:17:02 +0000 X-Env-Sender: cdelorme@gmail.com X-Msg-Ref: server-3.tower-27.messagelabs.com!1360275416!9595693!1 X-Originating-IP: [209.85.212.43] 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.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 20236 invoked from network); 7 Feb 2013 22:16:57 -0000 Received: from mail-vb0-f43.google.com (HELO mail-vb0-f43.google.com) (209.85.212.43) by server-3.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 7 Feb 2013 22:16:57 -0000 Received: by mail-vb0-f43.google.com with SMTP id fs19so1961861vbb.30 for ; Thu, 07 Feb 2013 14:16:55 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=6HqDW18j/VgOQ/Ho5yGES9FJvGRj+bksf180aX3oMco=; b=BW7xKRNIsq4bi2CYVRY3Iw+GTjTKS0fstj95Dyaahb5n8z28AI6Ep7Sc7m7fRGxwQ9 Aeu8IwVexYf0qZeCGeZdhc3xwftgNATpuPo5hf8fU0gRL4epM+jXcwFQK+eIAdE+z1tu ItSGh6tlwAJUvsx9QmZr484nsdCFqDYfSEc6ZoEnMQjhLH9SfCG+eSWgLzoxqEuiWpHs V0wP/WFtwBkPXBlbwgNorQPaWxGnO7c06yAtSZYqVoZMdPhejbxbXRZ8BYIB6VxatlY8 ookKQEh+qTv7gZF8nk0Ufauvdw1QEzGkRtMYN08U71v4d3fZ1qdd9ca9R3Ve6CC4uGrY fQIw== MIME-Version: 1.0 X-Received: by 10.52.19.65 with SMTP id c1mr3457493vde.36.1360275415799; Thu, 07 Feb 2013 14:16:55 -0800 (PST) Received: by 10.58.32.199 with HTTP; Thu, 7 Feb 2013 14:16:55 -0800 (PST) In-Reply-To: <1360274160.57405.YahooMailNeo@web172003.mail.ir2.yahoo.com> References: <1360274160.57405.YahooMailNeo@web172003.mail.ir2.yahoo.com> Date: Thu, 7 Feb 2013 17:16:55 -0500 Message-ID: From: Casey DeLorme To: David TECHER Cc: "xen-users@lists.xen.org" , Matthias Subject: Re: [Xen-users] ATI/AMDs atikmpag.sys BSOD while 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="===============2529276979055605528==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============2529276979055605528== Content-Type: multipart/alternative; boundary=bcaec5040b9af497f804d529cc67 --bcaec5040b9af497f804d529cc67 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable I have an HD 6870 and working CCC, tested on both Windows 7 and windows 8. Don't have any BSoD's either. I only had problems with CCC and drivers when I attempted to install or update drivers without having freshly rebooted or ejected the card. Unfortunately Windows 8 attempts to auto-install the drivers at boot time and this caused some headaches during my first go at it. I experience performance problems after rebooting the HVM, to fix it I just eject the card from the "Safely Remove Hardware and Eject Media" icon. On Thu, Feb 7, 2013 at 4:56 PM, David TECHER wrote: > Issues for CCC depends on your Video Card too. > > - Got a HD 79070. It worked for me to add CCC while installing the 13.2 > beta driver. > > Unfortunately there was BSOD issue when rebooting the domU. > > I had to install .NET 4 Framework and CCC now works as expected :) > > - CCC is not supposed to work for HD 6870 but it worked for HD 7970. > > FYI to fix atikmap.sys issue there is a well-known workaround with > something like > > > http://www.computertipsfree.com/fix-43029-atikmdag-sys-blue-screen-bsod-i= n-windows-7/ > > expand -r atikmdag.sy_ atikmdag.sys > > But it doesn't work for me :( > > The good news is that I've just installed Crysis 3 beta demo. It works > like a charm! > > > ------------------------------ > *De :* Matthias > *=C3=80 :* xen-users@lists.xen.org > *Envoy=C3=A9 le :* Jeudi 7 f=C3=A9vrier 2013 20h14 > *Objet :* [Xen-users] ATI/AMDs atikmpag.sys BSOD while vga passthrough > > Hi everyone > > since I'm currently migrating from xm to xl and now are also a victim > of the said error, I started researching on it and found that many > people had the issue but not many found solution and behind this BSOD > (=3DBluescreen of Death), there are actually multiple errors in hiding. > > What I would like to do is gather as much info as possible in this > thread to form a kind of comprehensive guide to fixing this issue. > > From what i gathered so far, there are at least 3 different problems > with the same symptopms. > > 1) > Situation: After booting the dom0 and booting a windows domU with an > ATI/AMD Card, Windows generally works fine, but after rebooting the > system, or shutting down / restarting, the Bluescreen occurs or the > performance massively below normal. > Error: Most likely this is cause the Card is not properly resetted (no > FLR [function level reset] ) > Solution: If the domU reboots into BSOD, you are screwed and have to > reboot the dom0. If it only degrades performance, eject the card and > reinitialize to perform a manual reset. Or use the xm toolkit. > Status: Don't know if it is fixed yet > Source: http://lists.xen.org/archives/html/xen-users/2012-02/msg00443.htm= l > , http://wiki.xen.org/wiki/Talk:Xen_VGA_Passthrough_Tested_Adapters > > 2) > Situation: Booting a windows domU results in a BSOD when the CCC > (=3DCatalyst Control Center) installed. > Error: The CCC tries to set some specific settings (most likely > performance tweaks) within the driver which the driver can't pass to > the vga through passthrough mode. Result is a BSOD. > Solution: Deinstall the CCC in windows safe mode. The driver itself > works without it pretty fine. > Status: Don't know if it is fixed yet > Source: http://lists.xen.org/archives/html/xen-users/2012-03/msg00617.htm= l > Note: I don't really know if this holds for the Vision Engine Control > center, too. the VECC is basically the same as the CCC, so i assume it > does. I simply haven't found any things referencing it. > > 3) > Situation: This is actually the issue I have. Things seem a lot more > random then the other ones. A BSOD happens basically in 80% of booting > the Windows domU. Which means, after rebooting dom0, it mostly works. > Rebooting or shutting down / starting the domU works sometimes (Once i > achieved 6 consecutive reboots or shutdowns / starts before the BSOD > happened) but after I get one Bluescreen, almost never (I can't > exactly remember if really 'never') comes up again. Of course I tried > the above solutions but this didn't helped me. I also tried different > different versions of the Catalyst driver (from 12/1 to 13/1) and > current releases of xen-4.2-testing and xen-unsable. As I said, this > is when using the xl toolkit. I never had this issues using xm. > I thought this might belinked to me passing other PCI devices in > addition (I'm passing some USB controller to the domU) but even > deactivating them didn't help. What I actually found helping boosting > the success rate (but not solving the overall issue) is deinstalling > all VGA-Related AMD Driver. Windows then runs on it's own VGA-Driver > (the graphic card is currectly identified and this is an actual ati > driver, so I'm not talking about some generic standard vga driver. I > don't know where is driver is coming from). > I've attached an analysis file i've gethered from the bluescreen crash > dump. I created it using BluescreenView. This is more for currectly > identifieng the different BSODs, I guess. > > > Some Infos: > Kernel: 3.7.4 kernel.org kernel without patches > Xen: latest xen-unstable (but also tested with xen-4.2-testing) > Processor: AMD Phenom 1090T > Mainboard: Asus Crossfire IV > VGA: Radeon HD5700 and Radeon HD5450 > Driver: Currently running Catalyst 13/1 but tested nearly everything > between 12/1 and 13/1 > > Error: Don't know yet > Solution: Don't know yet > Status: unsolved > Source: > > > Okay, so basically that's the story. It would be great if some people > can complete and extend the list. Especially some who already fixed > the issue on their side. (And of course it would be great if someone > has an idea for my problem). > > Thanks > > _______________________________________________ > 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 > --bcaec5040b9af497f804d529cc67 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
I have an HD 6870 and working CCC, tested on both Windows = 7 and windows 8. =C2=A0Don't have any BSoD's either.
=
I only had problems with CCC and drivers when I attemp= ted to install or update drivers without having freshly rebooted or ejected= the card.

Unfortunately Windows 8 attempts to auto-in= stall the drivers at boot time and this caused some headaches during my fir= st go at it.

I experience performance = problems after rebooting the HVM, to fix it I just eject the card from the = "Safely Remove Hardware and Eject Media" icon.


On Thu,= Feb 7, 2013 at 4:56 PM, David TECHER <davidtecher@yahoo.fr> wrote:
Issues for CCC depends on your Vide= o Card too.

- Got a HD 79070. It worked for me to add CCC while installing the 13.2= beta driver.

=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 Unfortunately there was= =C2=A0 BSOD issue when rebooting the domU.

=C2=A0=C2=A0=C2=A0=C2=A0 = I had to install .NET 4 Framework and CCC now works as expected :)

- CCC is not supposed to work for HD 6870 but it worked for HD 7970.
FYI to fix atikmap.sys issue there is a well-known workaround with som= ething like

http://www.comp= utertipsfree.com/fix-43029-atikmdag-sys-blue-screen-bsod-in-windows-7/<= br>
expand -r atikmdag.sy_ atikmdag.sys

But it doesn't work for me :(
=
The good news is that I've just installed Crysis 3 beta demo. It works = like a charm!


De=C2=A0: Matthias <matthias.kannenberg@= googlemail.com>
=C3=80=C2=A0: xen-users@lists.xen.org=
Envoy=C3=A9 le : Jeudi= 7 f=C3=A9vrier 2013 20h14
Objet=C2=A0: [Xen-users] AT= I/AMDs atikmpag.sys BSOD while vga passthrough

Hi everyone

since I'm currently migrating from= xm to xl and now are also a victim
of the said error, I started researching on it and found that many
peopl= e had the issue but not many found solution and behind this BSOD
(=3DBlu= escreen of Death), there are actually multiple errors in hiding.

Wha= t I would like to do is gather as much info as possible in this
thread to form a kind of comprehensive guide to fixing this issue.

F= rom what i gathered so far, there are at least 3 different problems
with= the same symptopms.

1)
Situation: After booting the dom0 and boo= ting a windows domU with an
ATI/AMD Card, Windows generally works fine, but after rebooting the
syst= em, or shutting down / restarting, the Bluescreen occurs or the
performance massively below normal.
Error: = Most likely this is cause the Card is not properly resetted (no
FLR [fun= ction level reset] )
Solution: If the domU reboots into BSOD, you are sc= rewed and have to
reboot the dom0. If it only degrades performance, eject the card and
rei= nitialize to perform a manual reset. Or use the xm toolkit.
Status: Don&= #39;t know if it is fixed yet
Source: http://lists= .xen.org/archives/html/xen-users/2012-02/msg00443.html
, http://wiki.xen.org/wiki/Talk:Xen_VGA_Passthrough_Te= sted_Adapters

2)
Situation: Booting a windows domU results in= a BSOD when the CCC
(=3DCatalyst Control Center) installed.
Error: The CCC tries to set some= specific settings (most likely
performance tweaks) within the driver which the driver can't pass to
the vga th= rough passthrough mode. Result is a BSOD.
Solution: Deinstall the CCC in= windows safe mode. The driver itself
works without it pretty fine.
Status: Don't know if it is fixed yet
Source: = http://lists.xen.org/archives/html/xen-users/2012-03/msg00617.html
N= ote: I don't really know if this holds for the Vision Engine Control center, too. the VECC is basically the same as the CCC, so i assume it
d= oes. I simply haven't found any things referencing it.

3)
Sit= uation: This is actually the issue I have. Things seem a lot more
random= then the other ones. A BSOD happens basically in 80% of booting
the Windows domU. Which means, after rebooting dom0, it mostly works.
Re= booting or shutting down / starting the domU works sometimes (Once i
ach= ieved 6 consecutive reboots or shutdowns / starts before the BSOD
happened) but after I get= one Bluescreen, almost never (I can't
exactly remember if really &#= 39;never') comes up again. Of course I tried
the above solutions but= this didn't helped me. I also tried different
different versions of the Catalyst driver (from 12/1 to 13/1) and
curren= t releases of xen-4.2-testing and xen-unsable. As I said, this
is when u= sing the xl toolkit. I never had this issues using xm.
I thought this mi= ght belinked to me passing other PCI devices in
addition (I'm passing some USB controller to the domU) but even
deac= tivating them didn't help. What I actually found helping boosting
th= e success rate (but not solving the overall issue) is deinstalling
all V= GA-Related AMD Driver. Windows then runs on it's own VGA-Driver
(the graphic card is currectly identified and this is an actual ati
driv= er, so I'm not talking about some generic standard vga driver. I
don't know where is driver is coming from).
I've attached = an analysis file i've gethered from the bluescreen crash
dump. I cre= ated it using BluescreenView. This is more for currectly
identifieng the= different BSODs, I guess.


Some Infos:
Kernel: 3.7.4 kernel.org kernel without patches
Xen: latest xen-unstab= le (but also tested with xen-4.2-testing)
Processor: AMD Phenom 1090TMainboard: Asus Crossfire IV
VGA: Radeon HD5700 and Radeon HD5450
Driver: Currently running Catalyst = 13/1 but tested nearly everything
between 12/1 and 13/1

Error: Do= n't know yet
Solution: Don't know yet
Status: unsolved
Source:


Okay, so basically that's the story. It would be gre= at if some people
can complete and extend the list. Especially some who = already fixed
the issue on their side. (And of course it would be great = if someone
has an idea for my problem).

Thanks

_______________________________= ________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.xen.org/xen-u= sers


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

--bcaec5040b9af497f804d529cc67-- --===============2529276979055605528== 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 --===============2529276979055605528==-- From xen-users-bounces@lists.xen.org Fri Feb 08 08:13:58 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 08 Feb 2013 08:13: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 1U3j4f-000441-H4; Fri, 08 Feb 2013 08:12:45 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U3j4e-00043m-7j for xen-users@lists.xen.org; Fri, 08 Feb 2013 08:12:44 +0000 Received: from [85.158.139.211:27641] by server-15.bemta-5.messagelabs.com id 9F/2C-18914-B73B4115; Fri, 08 Feb 2013 08:12:43 +0000 X-Env-Sender: al@ohosting.org.ua X-Msg-Ref: server-13.tower-206.messagelabs.com!1360311155!17664504!1 X-Originating-IP: [195.248.169.244] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 20098 invoked from network); 8 Feb 2013 08:12:36 -0000 Received: from ohosting.org.ua (HELO ohosting.org.ua) (195.248.169.244) by server-13.tower-206.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 8 Feb 2013 08:12:36 -0000 Received: from AL (df-cr.ucomline.com [78.111.215.53] (may be forged)) (authenticated bits=0) by ohosting.org.ua (8.14.5/8.14.5) with ESMTP id r188C1RP005161; Fri, 8 Feb 2013 10:12:02 +0200 Message-ID: From: "Likarpenkov Alexander" To: "Phil Evans" , References: In-Reply-To: Date: Fri, 8 Feb 2013 10:12:46 +0200 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.7600.16385 FL-Build: Fidolook 2007 (HV) 6.0.6000.97 - 22/5/2009 19:59:07 Subject: Re: [Xen-users] Ever increasing time offset for HVM domain / Hugeamounts of drift X-BeenThere: xen-users@lists.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 Who knows the reason? ----- Original Message ----- From: Phil Evans To: xen-users@lists.xen.org Sent: Friday, January 11, 2013 1:01 AM Subject: [Xen-users] Ever increasing time offset for HVM domain / Hugeamounts of drift Hi, I am currently running Xen 4.2.1 (this has also happened in 4.2.0 as well). We have been having a major problem with sometimes huge amounts of clock drift in Windows VMs. Sometimes the clock on a VM could suddenly jump by over a week (usually forwards, however time has been known to go backwards as well). Now I don't profess to know the internals of Xen, however through my investigation I believe I have a degree of knowledge of what could be causing the problem. The steps to reproduce this (for me at least), is to simply do a manual NTP sync on a Windows VM. Upon monitoring the qemu-dm log file for the VM, I see similar to the following: Time offset set 489, added offset 480 Time offset set 436, added offset -53 Time offset set 496, added offset 60 Time offset set 494, added offset -2 Time offset set 554, added offset 60 Time offset set 565, added offset 11 Time offset set 606, added offset 41 Time offset set -1974, added offset -2580 Time offset set 1626, added offset 3600 Time offset set 1579, added offset -47 Time offset set 1639, added offset 60 It seems to add the same number of seconds to the offset as has passed since the last sync. The offset just keeps on increasing, eventually resulting in huge numbers equating to days. Occasionally the offset may jump a bit and go down but the general trend is up. Although this does not affect the VM immediately, at some point I am guessing it syncs itself with the CMOS clock (which is now a large number of seconds offset from the actual time), resulting in a huge jump in time. A reboot is a guaranteed way to get the new, incorrect time. Although I do not understand all of the underlying code, I presume the correct way this should work is it should be comparing the CMOS time that's just been set with the hardware clock on the physical machine, resulting in an offset between the two. This would result in a generally stable number (ideally 0). Obviously it is incorrect behaviour for the number to keep going up. To my mind it looks like it may be somehow getting an inaccurate time from the system (in many cases a fixed time rather than an up-to-date current time). Does anyone have any light they may be able to shed on this? Is it possible it could be struggling to get an accurate time from the hardware? I have checked on several occasions and both the system time and the BIOS clock are spot on. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Fri Feb 08 08:13:58 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 08 Feb 2013 08:13: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 1U3j4f-000441-H4; Fri, 08 Feb 2013 08:12:45 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U3j4e-00043m-7j for xen-users@lists.xen.org; Fri, 08 Feb 2013 08:12:44 +0000 Received: from [85.158.139.211:27641] by server-15.bemta-5.messagelabs.com id 9F/2C-18914-B73B4115; Fri, 08 Feb 2013 08:12:43 +0000 X-Env-Sender: al@ohosting.org.ua X-Msg-Ref: server-13.tower-206.messagelabs.com!1360311155!17664504!1 X-Originating-IP: [195.248.169.244] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 20098 invoked from network); 8 Feb 2013 08:12:36 -0000 Received: from ohosting.org.ua (HELO ohosting.org.ua) (195.248.169.244) by server-13.tower-206.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 8 Feb 2013 08:12:36 -0000 Received: from AL (df-cr.ucomline.com [78.111.215.53] (may be forged)) (authenticated bits=0) by ohosting.org.ua (8.14.5/8.14.5) with ESMTP id r188C1RP005161; Fri, 8 Feb 2013 10:12:02 +0200 Message-ID: From: "Likarpenkov Alexander" To: "Phil Evans" , References: In-Reply-To: Date: Fri, 8 Feb 2013 10:12:46 +0200 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.7600.16385 FL-Build: Fidolook 2007 (HV) 6.0.6000.97 - 22/5/2009 19:59:07 Subject: Re: [Xen-users] Ever increasing time offset for HVM domain / Hugeamounts of drift X-BeenThere: xen-users@lists.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 Who knows the reason? ----- Original Message ----- From: Phil Evans To: xen-users@lists.xen.org Sent: Friday, January 11, 2013 1:01 AM Subject: [Xen-users] Ever increasing time offset for HVM domain / Hugeamounts of drift Hi, I am currently running Xen 4.2.1 (this has also happened in 4.2.0 as well). We have been having a major problem with sometimes huge amounts of clock drift in Windows VMs. Sometimes the clock on a VM could suddenly jump by over a week (usually forwards, however time has been known to go backwards as well). Now I don't profess to know the internals of Xen, however through my investigation I believe I have a degree of knowledge of what could be causing the problem. The steps to reproduce this (for me at least), is to simply do a manual NTP sync on a Windows VM. Upon monitoring the qemu-dm log file for the VM, I see similar to the following: Time offset set 489, added offset 480 Time offset set 436, added offset -53 Time offset set 496, added offset 60 Time offset set 494, added offset -2 Time offset set 554, added offset 60 Time offset set 565, added offset 11 Time offset set 606, added offset 41 Time offset set -1974, added offset -2580 Time offset set 1626, added offset 3600 Time offset set 1579, added offset -47 Time offset set 1639, added offset 60 It seems to add the same number of seconds to the offset as has passed since the last sync. The offset just keeps on increasing, eventually resulting in huge numbers equating to days. Occasionally the offset may jump a bit and go down but the general trend is up. Although this does not affect the VM immediately, at some point I am guessing it syncs itself with the CMOS clock (which is now a large number of seconds offset from the actual time), resulting in a huge jump in time. A reboot is a guaranteed way to get the new, incorrect time. Although I do not understand all of the underlying code, I presume the correct way this should work is it should be comparing the CMOS time that's just been set with the hardware clock on the physical machine, resulting in an offset between the two. This would result in a generally stable number (ideally 0). Obviously it is incorrect behaviour for the number to keep going up. To my mind it looks like it may be somehow getting an inaccurate time from the system (in many cases a fixed time rather than an up-to-date current time). Does anyone have any light they may be able to shed on this? Is it possible it could be struggling to get an accurate time from the hardware? I have checked on several occasions and both the system time and the BIOS clock are spot on. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Fri Feb 08 11:26:54 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 08 Feb 2013 11:26: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 1U3m5K-0002uB-BY; Fri, 08 Feb 2013 11:25:38 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U3m5I-0002tv-7g; Fri, 08 Feb 2013 11:25:36 +0000 Received: from [85.158.139.83:12900] by server-2.bemta-5.messagelabs.com id 3D/B9-16911-FA0E4115; Fri, 08 Feb 2013 11:25:35 +0000 X-Env-Sender: Ian.Campbell@citrix.com X-Msg-Ref: server-6.tower-182.messagelabs.com!1360322726!24416515!1 X-Originating-IP: [46.33.159.39] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNDYuMzMuMTU5LjM5ID0+IDIxNDA5\n X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 14629 invoked from network); 8 Feb 2013 11:25:26 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (46.33.159.39) by server-6.tower-182.messagelabs.com with RC4-SHA encrypted SMTP; 8 Feb 2013 11:25:26 -0000 X-IronPort-AV: E=Sophos;i="4.84,628,1355097600"; d="scan'208";a="1276373" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 08 Feb 2013 11:25:26 +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.297.1; Fri, 8 Feb 2013 11:25:25 +0000 Message-ID: <1360322724.32479.159.camel@zakaz.uk.xensource.com> From: Ian Campbell To: Andrew Cooper , Lars Kurth Date: Fri, 8 Feb 2013 11:25:24 +0000 In-Reply-To: <1357558616.7989.41.camel@zakaz.uk.xensource.com> References: <50EAAFAB.9000904@citrix.com> <1357558616.7989.41.camel@zakaz.uk.xensource.com> Organization: Citrix Systems, Inc. X-Mailer: Evolution 3.4.4-1 MIME-Version: 1.0 Cc: xen-users , "Keir \(Xen.org\)" , "xen-devel@lists.xen.org" Subject: Re: [Xen-users] [Xen-devel] Security support for debug=y builds (Was Re: Xen Security Advisory 37 (CVE-2013-0154) - Hypervisor crash due to incorrect ASSERT (debug build only)) X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: 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, 2013-01-07 at 11:36 +0000, Ian Campbell wrote: > On Mon, 2013-01-07 at 11:21 +0000, Andrew Cooper wrote: > > On 07/01/13 11:08, Keir Fraser wrote: > > > On 07/01/2013 10:21, "Ian Campbell" wrote: > > >> * debug=y bugs are Just Bugs and not security issues. i.e. they > > >> are discussed and fixed publicly on xen-devel and the fix is > > >> checked in in the usual way. There is no embargo or specific > > >> announcement. changelog may or may not refer to the security > > >> implications if debug=y is enabled. > > > This is my preference. I consider debug builds to be developer builds, and > > > wouldn't expect to see them used in production environments. We set debug=n > > > by default in our stable branches for that reason. > > > > > > -- Keir > > > > I second this opinion. Production environments should not be running > > development builds. > > I tried to keep my initial mail unbiased, but this is my opinion too. Looks like we have a consensus on this then. Lars, could you add some words to the doc? e.g. under "Scope of this process". This process primarily covers the Xen Hypervisor Project. Vulnerabilties reported against other Xen.org projects will be handled on a best effort basis by the relevant Project Lead together with the security team. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Fri Feb 08 11:26:54 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 08 Feb 2013 11:26: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 1U3m5K-0002uB-BY; Fri, 08 Feb 2013 11:25:38 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U3m5I-0002tv-7g; Fri, 08 Feb 2013 11:25:36 +0000 Received: from [85.158.139.83:12900] by server-2.bemta-5.messagelabs.com id 3D/B9-16911-FA0E4115; Fri, 08 Feb 2013 11:25:35 +0000 X-Env-Sender: Ian.Campbell@citrix.com X-Msg-Ref: server-6.tower-182.messagelabs.com!1360322726!24416515!1 X-Originating-IP: [46.33.159.39] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNDYuMzMuMTU5LjM5ID0+IDIxNDA5\n X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 14629 invoked from network); 8 Feb 2013 11:25:26 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (46.33.159.39) by server-6.tower-182.messagelabs.com with RC4-SHA encrypted SMTP; 8 Feb 2013 11:25:26 -0000 X-IronPort-AV: E=Sophos;i="4.84,628,1355097600"; d="scan'208";a="1276373" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 08 Feb 2013 11:25:26 +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.297.1; Fri, 8 Feb 2013 11:25:25 +0000 Message-ID: <1360322724.32479.159.camel@zakaz.uk.xensource.com> From: Ian Campbell To: Andrew Cooper , Lars Kurth Date: Fri, 8 Feb 2013 11:25:24 +0000 In-Reply-To: <1357558616.7989.41.camel@zakaz.uk.xensource.com> References: <50EAAFAB.9000904@citrix.com> <1357558616.7989.41.camel@zakaz.uk.xensource.com> Organization: Citrix Systems, Inc. X-Mailer: Evolution 3.4.4-1 MIME-Version: 1.0 Cc: xen-users , "Keir \(Xen.org\)" , "xen-devel@lists.xen.org" Subject: Re: [Xen-users] [Xen-devel] Security support for debug=y builds (Was Re: Xen Security Advisory 37 (CVE-2013-0154) - Hypervisor crash due to incorrect ASSERT (debug build only)) X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: 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, 2013-01-07 at 11:36 +0000, Ian Campbell wrote: > On Mon, 2013-01-07 at 11:21 +0000, Andrew Cooper wrote: > > On 07/01/13 11:08, Keir Fraser wrote: > > > On 07/01/2013 10:21, "Ian Campbell" wrote: > > >> * debug=y bugs are Just Bugs and not security issues. i.e. they > > >> are discussed and fixed publicly on xen-devel and the fix is > > >> checked in in the usual way. There is no embargo or specific > > >> announcement. changelog may or may not refer to the security > > >> implications if debug=y is enabled. > > > This is my preference. I consider debug builds to be developer builds, and > > > wouldn't expect to see them used in production environments. We set debug=n > > > by default in our stable branches for that reason. > > > > > > -- Keir > > > > I second this opinion. Production environments should not be running > > development builds. > > I tried to keep my initial mail unbiased, but this is my opinion too. Looks like we have a consensus on this then. Lars, could you add some words to the doc? e.g. under "Scope of this process". This process primarily covers the Xen Hypervisor Project. Vulnerabilties reported against other Xen.org projects will be handled on a best effort basis by the relevant Project Lead together with the security team. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Fri Feb 08 11:30:15 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 08 Feb 2013 11:30: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 1U3m8o-0003Be-Rm; Fri, 08 Feb 2013 11:29:14 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U3m8m-0003BL-MB; Fri, 08 Feb 2013 11:29:12 +0000 Received: from [85.158.143.99:37162] by server-2.bemta-4.messagelabs.com id 85/17-01597-781E4115; Fri, 08 Feb 2013 11:29:11 +0000 X-Env-Sender: Ian.Campbell@citrix.com X-Msg-Ref: server-16.tower-216.messagelabs.com!1360322950!18489252!1 X-Originating-IP: [46.33.159.39] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNDYuMzMuMTU5LjM5ID0+IDIxNDA5\n X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 22282 invoked from network); 8 Feb 2013 11:29:10 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (46.33.159.39) by server-16.tower-216.messagelabs.com with RC4-SHA encrypted SMTP; 8 Feb 2013 11:29:10 -0000 X-IronPort-AV: E=Sophos;i="4.84,628,1355097600"; d="scan'208";a="1276602" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 08 Feb 2013 11:29:11 +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.297.1; Fri, 8 Feb 2013 11:29:09 +0000 Message-ID: <1360322948.29432.0.camel@zakaz.uk.xensource.com> From: Ian Campbell To: Andrew Cooper , Lars Kurth Date: Fri, 8 Feb 2013 11:29:08 +0000 In-Reply-To: <1357558616.7989.41.camel@zakaz.uk.xensource.com> References: <50EAAFAB.9000904@citrix.com> <1357558616.7989.41.camel@zakaz.uk.xensource.com> Organization: Citrix Systems, Inc. X-Mailer: Evolution 3.4.4-1 MIME-Version: 1.0 Cc: xen-users , "Keir \(Xen.org\)" , "xen-devel@lists.xen.org" Subject: Re: [Xen-users] [Xen-devel] Security support for debug=y builds (Was Re: Xen Security Advisory 37 (CVE-2013-0154) - Hypervisor crash due to incorrect ASSERT (debug build only)) X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: 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, 2013-01-07 at 11:36 +0000, Ian Campbell wrote: > On Mon, 2013-01-07 at 11:21 +0000, Andrew Cooper wrote: > > On 07/01/13 11:08, Keir Fraser wrote: > > > On 07/01/2013 10:21, "Ian Campbell" wrote: > > >> * debug=y bugs are Just Bugs and not security issues. i.e. they > > >> are discussed and fixed publicly on xen-devel and the fix is > > >> checked in in the usual way. There is no embargo or specific > > >> announcement. changelog may or may not refer to the security > > >> implications if debug=y is enabled. > > > This is my preference. I consider debug builds to be developer builds, and > > > wouldn't expect to see them used in production environments. We set debug=n > > > by default in our stable branches for that reason. > > > > > > -- Keir > > > > I second this opinion. Production environments should not be running > > development builds. > > I tried to keep my initial mail unbiased, but this is my opinion too. Looks like we have a consensus on this then. I'm in two minds about whether this needs to be made explicit in the vulnerability process. If it were then e.g. "Scope of this process" could become: This process primarily covers the Xen Hypervisor Project and covers production configurations only, that is builds without debugging features enabled, e.g. debug=y. Vulnerabilties reported against other Xen.org projects will be handled on a best effort basis by the relevant Project Lead together with the security team. Ian. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Fri Feb 08 11:30:15 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 08 Feb 2013 11:30: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 1U3m8o-0003Be-Rm; Fri, 08 Feb 2013 11:29:14 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U3m8m-0003BL-MB; Fri, 08 Feb 2013 11:29:12 +0000 Received: from [85.158.143.99:37162] by server-2.bemta-4.messagelabs.com id 85/17-01597-781E4115; Fri, 08 Feb 2013 11:29:11 +0000 X-Env-Sender: Ian.Campbell@citrix.com X-Msg-Ref: server-16.tower-216.messagelabs.com!1360322950!18489252!1 X-Originating-IP: [46.33.159.39] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNDYuMzMuMTU5LjM5ID0+IDIxNDA5\n X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 22282 invoked from network); 8 Feb 2013 11:29:10 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (46.33.159.39) by server-16.tower-216.messagelabs.com with RC4-SHA encrypted SMTP; 8 Feb 2013 11:29:10 -0000 X-IronPort-AV: E=Sophos;i="4.84,628,1355097600"; d="scan'208";a="1276602" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 08 Feb 2013 11:29:11 +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.297.1; Fri, 8 Feb 2013 11:29:09 +0000 Message-ID: <1360322948.29432.0.camel@zakaz.uk.xensource.com> From: Ian Campbell To: Andrew Cooper , Lars Kurth Date: Fri, 8 Feb 2013 11:29:08 +0000 In-Reply-To: <1357558616.7989.41.camel@zakaz.uk.xensource.com> References: <50EAAFAB.9000904@citrix.com> <1357558616.7989.41.camel@zakaz.uk.xensource.com> Organization: Citrix Systems, Inc. X-Mailer: Evolution 3.4.4-1 MIME-Version: 1.0 Cc: xen-users , "Keir \(Xen.org\)" , "xen-devel@lists.xen.org" Subject: Re: [Xen-users] [Xen-devel] Security support for debug=y builds (Was Re: Xen Security Advisory 37 (CVE-2013-0154) - Hypervisor crash due to incorrect ASSERT (debug build only)) X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: 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, 2013-01-07 at 11:36 +0000, Ian Campbell wrote: > On Mon, 2013-01-07 at 11:21 +0000, Andrew Cooper wrote: > > On 07/01/13 11:08, Keir Fraser wrote: > > > On 07/01/2013 10:21, "Ian Campbell" wrote: > > >> * debug=y bugs are Just Bugs and not security issues. i.e. they > > >> are discussed and fixed publicly on xen-devel and the fix is > > >> checked in in the usual way. There is no embargo or specific > > >> announcement. changelog may or may not refer to the security > > >> implications if debug=y is enabled. > > > This is my preference. I consider debug builds to be developer builds, and > > > wouldn't expect to see them used in production environments. We set debug=n > > > by default in our stable branches for that reason. > > > > > > -- Keir > > > > I second this opinion. Production environments should not be running > > development builds. > > I tried to keep my initial mail unbiased, but this is my opinion too. Looks like we have a consensus on this then. I'm in two minds about whether this needs to be made explicit in the vulnerability process. If it were then e.g. "Scope of this process" could become: This process primarily covers the Xen Hypervisor Project and covers production configurations only, that is builds without debugging features enabled, e.g. debug=y. Vulnerabilties reported against other Xen.org projects will be handled on a best effort basis by the relevant Project Lead together with the security team. Ian. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Fri Feb 08 11:30:23 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 08 Feb 2013 11:30: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 1U3m9B-0003E7-1B; Fri, 08 Feb 2013 11:29:37 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U3m98-0003DM-IJ; Fri, 08 Feb 2013 11:29:34 +0000 Received: from [85.158.138.51:39448] by server-15.bemta-3.messagelabs.com id B2/34-25405-D91E4115; Fri, 08 Feb 2013 11:29:33 +0000 X-Env-Sender: Ian.Campbell@citrix.com X-Msg-Ref: server-10.tower-174.messagelabs.com!1360322972!24278457!1 X-Originating-IP: [46.33.159.39] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNDYuMzMuMTU5LjM5ID0+IDIxNDA5\n X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 23188 invoked from network); 8 Feb 2013 11:29:33 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (46.33.159.39) by server-10.tower-174.messagelabs.com with RC4-SHA encrypted SMTP; 8 Feb 2013 11:29:33 -0000 X-IronPort-AV: E=Sophos;i="4.84,628,1355097600"; d="scan'208";a="1276636" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 08 Feb 2013 11:29: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.297.1; Fri, 8 Feb 2013 11:29:32 +0000 Message-ID: <1360322971.29432.3.camel@zakaz.uk.xensource.com> From: Ian Campbell To: Andrew Cooper Date: Fri, 8 Feb 2013 11:29:31 +0000 In-Reply-To: <1360322724.32479.159.camel@zakaz.uk.xensource.com> References: <50EAAFAB.9000904@citrix.com> <1357558616.7989.41.camel@zakaz.uk.xensource.com> <1360322724.32479.159.camel@zakaz.uk.xensource.com> Organization: Citrix Systems, Inc. X-Mailer: Evolution 3.4.4-1 MIME-Version: 1.0 Cc: xen-users , Lars Kurth , "Keir \(Xen.org\)" , "xen-devel@lists.xen.org" Subject: Re: [Xen-users] [Xen-devel] Security support for debug=y builds (Was Re: Xen Security Advisory 37 (CVE-2013-0154) - Hypervisor crash due to incorrect ASSERT (debug build only)) X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org Ignore this one, hit send too soon. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Fri Feb 08 11:30:23 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 08 Feb 2013 11:30: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 1U3m9B-0003E7-1B; Fri, 08 Feb 2013 11:29:37 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U3m98-0003DM-IJ; Fri, 08 Feb 2013 11:29:34 +0000 Received: from [85.158.138.51:39448] by server-15.bemta-3.messagelabs.com id B2/34-25405-D91E4115; Fri, 08 Feb 2013 11:29:33 +0000 X-Env-Sender: Ian.Campbell@citrix.com X-Msg-Ref: server-10.tower-174.messagelabs.com!1360322972!24278457!1 X-Originating-IP: [46.33.159.39] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNDYuMzMuMTU5LjM5ID0+IDIxNDA5\n X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 23188 invoked from network); 8 Feb 2013 11:29:33 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (46.33.159.39) by server-10.tower-174.messagelabs.com with RC4-SHA encrypted SMTP; 8 Feb 2013 11:29:33 -0000 X-IronPort-AV: E=Sophos;i="4.84,628,1355097600"; d="scan'208";a="1276636" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 08 Feb 2013 11:29: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.297.1; Fri, 8 Feb 2013 11:29:32 +0000 Message-ID: <1360322971.29432.3.camel@zakaz.uk.xensource.com> From: Ian Campbell To: Andrew Cooper Date: Fri, 8 Feb 2013 11:29:31 +0000 In-Reply-To: <1360322724.32479.159.camel@zakaz.uk.xensource.com> References: <50EAAFAB.9000904@citrix.com> <1357558616.7989.41.camel@zakaz.uk.xensource.com> <1360322724.32479.159.camel@zakaz.uk.xensource.com> Organization: Citrix Systems, Inc. X-Mailer: Evolution 3.4.4-1 MIME-Version: 1.0 Cc: xen-users , Lars Kurth , "Keir \(Xen.org\)" , "xen-devel@lists.xen.org" Subject: Re: [Xen-users] [Xen-devel] Security support for debug=y builds (Was Re: Xen Security Advisory 37 (CVE-2013-0154) - Hypervisor crash due to incorrect ASSERT (debug build only)) X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org Ignore this one, hit send too soon. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Fri Feb 08 11:41:06 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 08 Feb 2013 11: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 1U3mJZ-0004t8-Qg; Fri, 08 Feb 2013 11:40:21 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U3mJY-0004sp-Hf; Fri, 08 Feb 2013 11:40:20 +0000 Received: from [85.158.143.35:40301] by server-3.bemta-4.messagelabs.com id A0/1F-08920-324E4115; Fri, 08 Feb 2013 11:40:19 +0000 X-Env-Sender: JBeulich@suse.com X-Msg-Ref: server-10.tower-21.messagelabs.com!1360323616!10112188!1 X-Originating-IP: [130.57.49.28] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogMTMwLjU3LjQ5LjI4ID0+IDQxMDQ=\n X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 28697 invoked from network); 8 Feb 2013 11:40:16 -0000 Received: from nat28.tlf.novell.com (HELO nat28.tlf.novell.com) (130.57.49.28) by server-10.tower-21.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 8 Feb 2013 11:40:16 -0000 Received: from EMEA1-MTA by nat28.tlf.novell.com with Novell_GroupWise; Fri, 08 Feb 2013 11:40:15 +0000 Message-Id: <5114F22F02000078000BD2C6@nat28.tlf.novell.com> X-Mailer: Novell GroupWise Internet Agent 12.0.1 Date: Fri, 08 Feb 2013 11:40:15 +0000 From: "Jan Beulich" To: "Ian Campbell" , "Lars Kurth" References: <50EAAFAB.9000904@citrix.com> <1357558616.7989.41.camel@zakaz.uk.xensource.com> <1360322948.29432.0.camel@zakaz.uk.xensource.com> In-Reply-To: <1360322948.29432.0.camel@zakaz.uk.xensource.com> Mime-Version: 1.0 Content-Disposition: inline Cc: Andrew Cooper , xen-users , "Keir \(Xen.org\)" , "xen-devel@lists.xen.org" Subject: Re: [Xen-users] [Xen-devel] Security support for debug=y builds (Was Re: Xen Security Advisory 37 (CVE-2013-0154) - Hypervisor crash due to incorrect ASSERT (debug build only)) X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: 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 08.02.13 at 12:29, Ian Campbell wrote: > If it were then e.g. "Scope of this process" could become: > > This process primarily covers the Xen Hypervisor Project and > covers production configurations only, that is builds without > debugging features enabled, e.g. debug=y. To me, with the wording above, the "debug=y" example here is ambiguous (in that I could read it to mean only "debug=y" is covered by the process, even if I agree that this makes little sense). Jan > Vulnerabilties reported against other Xen.org projects will be > handled on a best effort basis by the relevant Project Lead > together with the security team. > > Ian. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Fri Feb 08 11:41:06 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 08 Feb 2013 11: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 1U3mJZ-0004t8-Qg; Fri, 08 Feb 2013 11:40:21 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U3mJY-0004sp-Hf; Fri, 08 Feb 2013 11:40:20 +0000 Received: from [85.158.143.35:40301] by server-3.bemta-4.messagelabs.com id A0/1F-08920-324E4115; Fri, 08 Feb 2013 11:40:19 +0000 X-Env-Sender: JBeulich@suse.com X-Msg-Ref: server-10.tower-21.messagelabs.com!1360323616!10112188!1 X-Originating-IP: [130.57.49.28] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogMTMwLjU3LjQ5LjI4ID0+IDQxMDQ=\n X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 28697 invoked from network); 8 Feb 2013 11:40:16 -0000 Received: from nat28.tlf.novell.com (HELO nat28.tlf.novell.com) (130.57.49.28) by server-10.tower-21.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 8 Feb 2013 11:40:16 -0000 Received: from EMEA1-MTA by nat28.tlf.novell.com with Novell_GroupWise; Fri, 08 Feb 2013 11:40:15 +0000 Message-Id: <5114F22F02000078000BD2C6@nat28.tlf.novell.com> X-Mailer: Novell GroupWise Internet Agent 12.0.1 Date: Fri, 08 Feb 2013 11:40:15 +0000 From: "Jan Beulich" To: "Ian Campbell" , "Lars Kurth" References: <50EAAFAB.9000904@citrix.com> <1357558616.7989.41.camel@zakaz.uk.xensource.com> <1360322948.29432.0.camel@zakaz.uk.xensource.com> In-Reply-To: <1360322948.29432.0.camel@zakaz.uk.xensource.com> Mime-Version: 1.0 Content-Disposition: inline Cc: Andrew Cooper , xen-users , "Keir \(Xen.org\)" , "xen-devel@lists.xen.org" Subject: Re: [Xen-users] [Xen-devel] Security support for debug=y builds (Was Re: Xen Security Advisory 37 (CVE-2013-0154) - Hypervisor crash due to incorrect ASSERT (debug build only)) X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: 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 08.02.13 at 12:29, Ian Campbell wrote: > If it were then e.g. "Scope of this process" could become: > > This process primarily covers the Xen Hypervisor Project and > covers production configurations only, that is builds without > debugging features enabled, e.g. debug=y. To me, with the wording above, the "debug=y" example here is ambiguous (in that I could read it to mean only "debug=y" is covered by the process, even if I agree that this makes little sense). Jan > Vulnerabilties reported against other Xen.org projects will be > handled on a best effort basis by the relevant Project Lead > together with the security team. > > Ian. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Fri Feb 08 11:48:07 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 08 Feb 2013 11:48: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 1U3mQP-0005nV-B5; Fri, 08 Feb 2013 11:47:25 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U3mQN-0005n7-ON; Fri, 08 Feb 2013 11:47:23 +0000 Received: from [85.158.143.35:60721] by server-1.bemta-4.messagelabs.com id B0/39-08839-BC5E4115; Fri, 08 Feb 2013 11:47:23 +0000 X-Env-Sender: Ian.Campbell@citrix.com X-Msg-Ref: server-7.tower-21.messagelabs.com!1360324038!11628652!1 X-Originating-IP: [46.33.159.39] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNDYuMzMuMTU5LjM5ID0+IDIxNDA5\n X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 29367 invoked from network); 8 Feb 2013 11:47:19 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (46.33.159.39) by server-7.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 8 Feb 2013 11:47:19 -0000 X-IronPort-AV: E=Sophos;i="4.84,629,1355097600"; d="scan'208";a="1277344" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 08 Feb 2013 11:47: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.297.1; Fri, 8 Feb 2013 11:47:18 +0000 Message-ID: <1360324037.29432.10.camel@zakaz.uk.xensource.com> From: Ian Campbell To: Jan Beulich Date: Fri, 8 Feb 2013 11:47:17 +0000 In-Reply-To: <5114F22F02000078000BD2C6@nat28.tlf.novell.com> References: <50EAAFAB.9000904@citrix.com> <1357558616.7989.41.camel@zakaz.uk.xensource.com> <1360322948.29432.0.camel@zakaz.uk.xensource.com> <5114F22F02000078000BD2C6@nat28.tlf.novell.com> Organization: Citrix Systems, Inc. X-Mailer: Evolution 3.4.4-1 MIME-Version: 1.0 Cc: Andrew Cooper , xen-users , Lars Kurth , "Keir \(Xen.org\)" , "xen-devel@lists.xen.org" Subject: Re: [Xen-users] [Xen-devel] Security support for debug=y builds (Was Re: Xen Security Advisory 37 (CVE-2013-0154) - Hypervisor crash due to incorrect ASSERT (debug build only)) X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: 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, 2013-02-08 at 11:40 +0000, Jan Beulich wrote: > >>> On 08.02.13 at 12:29, Ian Campbell wrote: > > If it were then e.g. "Scope of this process" could become: > > > > This process primarily covers the Xen Hypervisor Project and > > covers production configurations only, that is builds without > > debugging features enabled, e.g. debug=y. > > To me, with the wording above, the "debug=y" example here is > ambiguous (in that I could read it to mean only "debug=y" is > covered by the process, even if I agree that this makes little > sense). yes, you are right. I was trying to avoid having to explicitly list all the options while also avoiding suggesting that other debug options, like perfc=y or (in the future) coverage=y, might be supported. Perhaps .... Therefore configurations built with e.g. debug=y are not covered by this process. Ian. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Fri Feb 08 11:48:07 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 08 Feb 2013 11:48: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 1U3mQP-0005nV-B5; Fri, 08 Feb 2013 11:47:25 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U3mQN-0005n7-ON; Fri, 08 Feb 2013 11:47:23 +0000 Received: from [85.158.143.35:60721] by server-1.bemta-4.messagelabs.com id B0/39-08839-BC5E4115; Fri, 08 Feb 2013 11:47:23 +0000 X-Env-Sender: Ian.Campbell@citrix.com X-Msg-Ref: server-7.tower-21.messagelabs.com!1360324038!11628652!1 X-Originating-IP: [46.33.159.39] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNDYuMzMuMTU5LjM5ID0+IDIxNDA5\n X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 29367 invoked from network); 8 Feb 2013 11:47:19 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (46.33.159.39) by server-7.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 8 Feb 2013 11:47:19 -0000 X-IronPort-AV: E=Sophos;i="4.84,629,1355097600"; d="scan'208";a="1277344" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 08 Feb 2013 11:47: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.297.1; Fri, 8 Feb 2013 11:47:18 +0000 Message-ID: <1360324037.29432.10.camel@zakaz.uk.xensource.com> From: Ian Campbell To: Jan Beulich Date: Fri, 8 Feb 2013 11:47:17 +0000 In-Reply-To: <5114F22F02000078000BD2C6@nat28.tlf.novell.com> References: <50EAAFAB.9000904@citrix.com> <1357558616.7989.41.camel@zakaz.uk.xensource.com> <1360322948.29432.0.camel@zakaz.uk.xensource.com> <5114F22F02000078000BD2C6@nat28.tlf.novell.com> Organization: Citrix Systems, Inc. X-Mailer: Evolution 3.4.4-1 MIME-Version: 1.0 Cc: Andrew Cooper , xen-users , Lars Kurth , "Keir \(Xen.org\)" , "xen-devel@lists.xen.org" Subject: Re: [Xen-users] [Xen-devel] Security support for debug=y builds (Was Re: Xen Security Advisory 37 (CVE-2013-0154) - Hypervisor crash due to incorrect ASSERT (debug build only)) X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: 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, 2013-02-08 at 11:40 +0000, Jan Beulich wrote: > >>> On 08.02.13 at 12:29, Ian Campbell wrote: > > If it were then e.g. "Scope of this process" could become: > > > > This process primarily covers the Xen Hypervisor Project and > > covers production configurations only, that is builds without > > debugging features enabled, e.g. debug=y. > > To me, with the wording above, the "debug=y" example here is > ambiguous (in that I could read it to mean only "debug=y" is > covered by the process, even if I agree that this makes little > sense). yes, you are right. I was trying to avoid having to explicitly list all the options while also avoiding suggesting that other debug options, like perfc=y or (in the future) coverage=y, might be supported. Perhaps .... Therefore configurations built with e.g. debug=y are not covered by this process. Ian. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Fri Feb 08 14:34:38 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 08 Feb 2013 14:34: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 1U3p11-0004x6-P2; Fri, 08 Feb 2013 14:33:23 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U3p0z-0004wy-F7 for xen-users@lists.xen.org; Fri, 08 Feb 2013 14:33:21 +0000 Received: from [85.158.143.35:52269] by server-1.bemta-4.messagelabs.com id AA/B4-08839-0BC05115; Fri, 08 Feb 2013 14:33:20 +0000 X-Env-Sender: Nick.Couchman@seakr.com X-Msg-Ref: server-15.tower-21.messagelabs.com!1360333998!13852397!1 X-Originating-IP: [64.2.143.10] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 22192 invoked from network); 8 Feb 2013 14:33:19 -0000 Received: from mx1.seakr.com (HELO mx1.seakr.com) (64.2.143.10) by server-15.tower-21.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 8 Feb 2013 14:33:19 -0000 Received: from mx-inside.seakr.com ([192.168.100.31]) by mx1.seakr.com (8.14.3/8.14.3/Debian-9.4) with ESMTP id r18EW2JB000867 for ; Fri, 8 Feb 2013 07:32:04 -0700 Received: from (mx-inside.seakr.com [192.168.100.31]) by mail-scanner1.it.seakr.com with smtp id 1e1a_4e4e_79c97fc2_71fc_11e2_94ff_00137252735f; Fri, 08 Feb 2013 07:33:17 -0700 Received: from collaborate.seakr.com (collaborate.seakr.com [192.168.100.28]) by mx-inside.seakr.com (Postfix) with ESMTP id 4B43444D9D for ; Fri, 8 Feb 2013 07:33:16 -0700 (MST) Received: from seakr-engineering-MTA by collaborate.seakr.com with Novell_GroupWise; Fri, 08 Feb 2013 07:33:16 -0700 Message-Id: <5114AA3B02000099000F2CAC@collaborate.seakr.com> X-Mailer: Novell GroupWise Internet Agent 8.0.3 Date: Fri, 08 Feb 2013 07:33:15 -0700 From: "Nick Couchman" To: "Mike Egglestone" , Mime-Version: 1.0 Content-Disposition: inline X-NAIMIME-Disclaimer: 1 X-NAIMIME-Modified: 1 Subject: Re: [Xen-users] need advise with a redhat 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: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org Mike, I think you need to better categorize the statement "performance is crappy." Dig into the performance some and figure out where your bottleneck is - disk, network, CPU, memory?? The standard tools you'd use on a physical machine should work fine on a VM - iostat, vmstat, top, free, sar, etc., etc. Once you nail down where the problem is, you can post back and folks will probably have some better suggestions on how to alleviate specific bottlenecks. Also, let us know what you're doing with the VM. Running a basic web server? Oracle database server? Compiling code? The tuning will be very different based on where the bottleneck is and what you're trying to do with the system. -Nick >>> On 2013/02/07 at 09:21, "Mike Egglestone" wrote: > Hello, > > I have xen dom0 running on Debian with a RedHat 5.4 domU. (under HVM) > Its working, but performance is crappy. > > I think I need to get PV drivers in the RH kernel, or flip this to a PV > domU? > The RH kernel is 2.6.18, which doesn't come stock with PV drivers. > > Any suggestions on how to get his domU up to snuff? > > Thanks! -------- This e-mail may contain confidential and privileged material for the sole use of the intended recipient. If this email is not intended for you, or you are not responsible for the delivery of this message to the intended recipient, please note that this message may contain SEAKR Engineering (SEAKR) Privileged/Proprietary Information. In such a case, you are strictly prohibited from downloading, photocopying, distributing or otherwise using this message, its contents or attachments in any way. If you have received this message in error, please notify us immediately by replying to this e-mail and delete the message from your mailbox. Information contained in this message that does not relate to the business of SEAKR is neither endorsed by nor attributable to SEAKR. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Fri Feb 08 14:34:38 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 08 Feb 2013 14:34: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 1U3p11-0004x6-P2; Fri, 08 Feb 2013 14:33:23 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U3p0z-0004wy-F7 for xen-users@lists.xen.org; Fri, 08 Feb 2013 14:33:21 +0000 Received: from [85.158.143.35:52269] by server-1.bemta-4.messagelabs.com id AA/B4-08839-0BC05115; Fri, 08 Feb 2013 14:33:20 +0000 X-Env-Sender: Nick.Couchman@seakr.com X-Msg-Ref: server-15.tower-21.messagelabs.com!1360333998!13852397!1 X-Originating-IP: [64.2.143.10] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 22192 invoked from network); 8 Feb 2013 14:33:19 -0000 Received: from mx1.seakr.com (HELO mx1.seakr.com) (64.2.143.10) by server-15.tower-21.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 8 Feb 2013 14:33:19 -0000 Received: from mx-inside.seakr.com ([192.168.100.31]) by mx1.seakr.com (8.14.3/8.14.3/Debian-9.4) with ESMTP id r18EW2JB000867 for ; Fri, 8 Feb 2013 07:32:04 -0700 Received: from (mx-inside.seakr.com [192.168.100.31]) by mail-scanner1.it.seakr.com with smtp id 1e1a_4e4e_79c97fc2_71fc_11e2_94ff_00137252735f; Fri, 08 Feb 2013 07:33:17 -0700 Received: from collaborate.seakr.com (collaborate.seakr.com [192.168.100.28]) by mx-inside.seakr.com (Postfix) with ESMTP id 4B43444D9D for ; Fri, 8 Feb 2013 07:33:16 -0700 (MST) Received: from seakr-engineering-MTA by collaborate.seakr.com with Novell_GroupWise; Fri, 08 Feb 2013 07:33:16 -0700 Message-Id: <5114AA3B02000099000F2CAC@collaborate.seakr.com> X-Mailer: Novell GroupWise Internet Agent 8.0.3 Date: Fri, 08 Feb 2013 07:33:15 -0700 From: "Nick Couchman" To: "Mike Egglestone" , Mime-Version: 1.0 Content-Disposition: inline X-NAIMIME-Disclaimer: 1 X-NAIMIME-Modified: 1 Subject: Re: [Xen-users] need advise with a redhat 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: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org Mike, I think you need to better categorize the statement "performance is crappy." Dig into the performance some and figure out where your bottleneck is - disk, network, CPU, memory?? The standard tools you'd use on a physical machine should work fine on a VM - iostat, vmstat, top, free, sar, etc., etc. Once you nail down where the problem is, you can post back and folks will probably have some better suggestions on how to alleviate specific bottlenecks. Also, let us know what you're doing with the VM. Running a basic web server? Oracle database server? Compiling code? The tuning will be very different based on where the bottleneck is and what you're trying to do with the system. -Nick >>> On 2013/02/07 at 09:21, "Mike Egglestone" wrote: > Hello, > > I have xen dom0 running on Debian with a RedHat 5.4 domU. (under HVM) > Its working, but performance is crappy. > > I think I need to get PV drivers in the RH kernel, or flip this to a PV > domU? > The RH kernel is 2.6.18, which doesn't come stock with PV drivers. > > Any suggestions on how to get his domU up to snuff? > > Thanks! -------- This e-mail may contain confidential and privileged material for the sole use of the intended recipient. If this email is not intended for you, or you are not responsible for the delivery of this message to the intended recipient, please note that this message may contain SEAKR Engineering (SEAKR) Privileged/Proprietary Information. In such a case, you are strictly prohibited from downloading, photocopying, distributing or otherwise using this message, its contents or attachments in any way. If you have received this message in error, please notify us immediately by replying to this e-mail and delete the message from your mailbox. Information contained in this message that does not relate to the business of SEAKR is neither endorsed by nor attributable to SEAKR. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Fri Feb 08 18:28:54 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 08 Feb 2013 18: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 1U3sf4-0000eW-C4; Fri, 08 Feb 2013 18:26:58 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U3sf2-0000eR-9D for xen-users@lists.xen.org; Fri, 08 Feb 2013 18:26:56 +0000 Received: from [85.158.139.211:6771] by server-15.bemta-5.messagelabs.com id E1/41-18914-F6345115; Fri, 08 Feb 2013 18:26:55 +0000 X-Env-Sender: jaceksburghardt@gmail.com X-Msg-Ref: server-9.tower-206.messagelabs.com!1360348013!20234842!1 X-Originating-IP: [209.85.210.177] 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.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 20320 invoked from network); 8 Feb 2013 18:26:54 -0000 Received: from mail-ia0-f177.google.com (HELO mail-ia0-f177.google.com) (209.85.210.177) by server-9.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 8 Feb 2013 18:26:54 -0000 Received: by mail-ia0-f177.google.com with SMTP id h8so4537400iaa.22 for ; Fri, 08 Feb 2013 10:26:53 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:date:message-id:subject:from:to :content-type; bh=4fAeAFZ67sir51KnZbbQEn4Be2v6eR4s3XeZ/3WMJDQ=; b=nTxOWGLrhh62klSBFRkFdUi/41kNVU3ecks2MsiUE++6WIWuNOYuuH4bq2eGyXZfpo bX9u4RJmgjMKo79Vb16uRvBRsGVBZG3NSXKI8j9fpdU8A0RZhWkP4nnVu8YcyR3AyyjD af6aXUGgJIJWmWyW2w1D8q1M6Bwy9u+UR1zrL98I7r5W6jBBCXe0l5qRZe8Iuw5UhoU7 GSeF8M0mO+D2ATQXu/S0VUzk4IaUSRldhVzQYmDGmxnj3OX5DBy2QfP0n2fcGVoqGhS0 WCFpKIuvKpy6R4vBdR0v7NucwQ6+yF7lvfN7xrZKKekabKhVP2hlq2KCJEw8H6LJaw3M 29yw== MIME-Version: 1.0 X-Received: by 10.50.151.176 with SMTP id ur16mr4361840igb.30.1360348013078; Fri, 08 Feb 2013 10:26:53 -0800 (PST) Received: by 10.42.41.5 with HTTP; Fri, 8 Feb 2013 10:26:52 -0800 (PST) Date: Fri, 8 Feb 2013 11:26:52 -0700 Message-ID: From: jacek burghardt To: xen-users Subject: [Xen-users] xen and lsi sas1064SE X-BeenThere: xen-users@lists.xen.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="===============2317547443911312244==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============2317547443911312244== Content-Type: multipart/alternative; boundary=e89a8f3b9f3b17275004d53ab4ac --e89a8f3b9f3b17275004d53ab4ac Content-Type: text/plain; charset=ISO-8859-1 I have dell cloud server that I got from dell and it has lsi sas1064 raid controller. I have xen 4.3 running on it. I would like to upgrade hard drives to 3TB I wonder if anyone knows if there firmware upgrade for controller and how I upgrade it under xen --e89a8f3b9f3b17275004d53ab4ac Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable I have dell cloud server that I got from dell and it has=A0=A0lsi sas1064 r= aid controller. I have xen 4.3 running on it. I would like to upgrade hard = drives to 3TB I wonder if anyone knows if there firmware upgrade for=A0cont= roller=A0and how I upgrade it under xen=A0 --e89a8f3b9f3b17275004d53ab4ac-- --===============2317547443911312244== 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 --===============2317547443911312244==-- From xen-users-bounces@lists.xen.org Fri Feb 08 18:28:54 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 08 Feb 2013 18: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 1U3sf4-0000eW-C4; Fri, 08 Feb 2013 18:26:58 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U3sf2-0000eR-9D for xen-users@lists.xen.org; Fri, 08 Feb 2013 18:26:56 +0000 Received: from [85.158.139.211:6771] by server-15.bemta-5.messagelabs.com id E1/41-18914-F6345115; Fri, 08 Feb 2013 18:26:55 +0000 X-Env-Sender: jaceksburghardt@gmail.com X-Msg-Ref: server-9.tower-206.messagelabs.com!1360348013!20234842!1 X-Originating-IP: [209.85.210.177] 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.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 20320 invoked from network); 8 Feb 2013 18:26:54 -0000 Received: from mail-ia0-f177.google.com (HELO mail-ia0-f177.google.com) (209.85.210.177) by server-9.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 8 Feb 2013 18:26:54 -0000 Received: by mail-ia0-f177.google.com with SMTP id h8so4537400iaa.22 for ; Fri, 08 Feb 2013 10:26:53 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:date:message-id:subject:from:to :content-type; bh=4fAeAFZ67sir51KnZbbQEn4Be2v6eR4s3XeZ/3WMJDQ=; b=nTxOWGLrhh62klSBFRkFdUi/41kNVU3ecks2MsiUE++6WIWuNOYuuH4bq2eGyXZfpo bX9u4RJmgjMKo79Vb16uRvBRsGVBZG3NSXKI8j9fpdU8A0RZhWkP4nnVu8YcyR3AyyjD af6aXUGgJIJWmWyW2w1D8q1M6Bwy9u+UR1zrL98I7r5W6jBBCXe0l5qRZe8Iuw5UhoU7 GSeF8M0mO+D2ATQXu/S0VUzk4IaUSRldhVzQYmDGmxnj3OX5DBy2QfP0n2fcGVoqGhS0 WCFpKIuvKpy6R4vBdR0v7NucwQ6+yF7lvfN7xrZKKekabKhVP2hlq2KCJEw8H6LJaw3M 29yw== MIME-Version: 1.0 X-Received: by 10.50.151.176 with SMTP id ur16mr4361840igb.30.1360348013078; Fri, 08 Feb 2013 10:26:53 -0800 (PST) Received: by 10.42.41.5 with HTTP; Fri, 8 Feb 2013 10:26:52 -0800 (PST) Date: Fri, 8 Feb 2013 11:26:52 -0700 Message-ID: From: jacek burghardt To: xen-users Subject: [Xen-users] xen and lsi sas1064SE X-BeenThere: xen-users@lists.xen.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="===============2317547443911312244==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============2317547443911312244== Content-Type: multipart/alternative; boundary=e89a8f3b9f3b17275004d53ab4ac --e89a8f3b9f3b17275004d53ab4ac Content-Type: text/plain; charset=ISO-8859-1 I have dell cloud server that I got from dell and it has lsi sas1064 raid controller. I have xen 4.3 running on it. I would like to upgrade hard drives to 3TB I wonder if anyone knows if there firmware upgrade for controller and how I upgrade it under xen --e89a8f3b9f3b17275004d53ab4ac Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable I have dell cloud server that I got from dell and it has=A0=A0lsi sas1064 r= aid controller. I have xen 4.3 running on it. I would like to upgrade hard = drives to 3TB I wonder if anyone knows if there firmware upgrade for=A0cont= roller=A0and how I upgrade it under xen=A0 --e89a8f3b9f3b17275004d53ab4ac-- --===============2317547443911312244== 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 --===============2317547443911312244==-- From xen-users-bounces@lists.xen.org Fri Feb 08 20:40:11 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 08 Feb 2013 20:40: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 1U3uiq-00064M-VW; Fri, 08 Feb 2013 20:39:00 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U3uip-00064E-26 for xen-users@lists.xen.org; Fri, 08 Feb 2013 20:38:59 +0000 Received: from [85.158.143.99:48764] by server-1.bemta-4.messagelabs.com id 48/D3-08839-26265115; Fri, 08 Feb 2013 20:38:58 +0000 X-Env-Sender: mike@estone.ca X-Msg-Ref: server-13.tower-216.messagelabs.com!1360355936!30586172!1 X-Originating-IP: [204.209.205.34] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogMjA0LjIwOS4yMDUuMzQgPT4gMTIwMzYy\n X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 31731 invoked from network); 8 Feb 2013 20:38:57 -0000 Received: from defout.telus.net (HELO defout.telus.net) (204.209.205.34) by server-13.tower-216.messagelabs.com with SMTP; 8 Feb 2013 20:38:57 -0000 Received: from edmwcm04 ([204.209.205.31]) by priv-edmwes04.telusplanet.net (InterMail vM.8.01.03.00 201-2260-125-20100507) with ESMTP id <20130208203851.PFSV15363.priv-edmwes04.telusplanet.net@edmwcm04> for ; Fri, 8 Feb 2013 13:38:51 -0700 Received: from estone.ca ([154.20.1.203]) by edmwcm04 with bizsmtp id xwem1k0024NnoEJ01weovW; Fri, 08 Feb 2013 13:38:50 -0700 X-Authority-Analysis: v=1.1 cv=rMclIWNOyWbaRaosMf477BSoDkSAEHI3rR4jEZfW1q4= c=1 sm=2 a=P_U1kJitcyAA:10 a=AJiS3eauAAAA:8 a=mLnsDVdbAAAA:8 a=LI_lRchgKdjjYXHAtm4A:9 a=QEXdDO2ut3YA:10 a=5xNTf9GLujYA:10 a=SSmOFEACAAAA:8 a=iArNVvhu2_IA:10 a=zJJgJrR4LD4A:10 a=frz4AuCg-hUA:10 a=tXsnliwV7b4A:10 a=VIg8ssY0raRGrABO:21 X-Telus-Outbound-IP: 154.20.1.203 Received: from estone.ca ([192.168.1.253] helo=mail.estone.ca) by estone.ca with esmtp (Exim 4.80) (envelope-from ) id 1U3uij-0001RF-9i for xen-users@lists.xen.org; Fri, 08 Feb 2013 12:38:53 -0800 Message-id: X-FC-Thread-ID: 3b9aca00-465dbe96 Date: Fri, 08 Feb 2013 12:38:52 -0800 X-Mailer: FirstClass 11.1 (build 11.128) X-FC-SERVER-TZ: 6554336 To: xen-users@lists.xen.org From: "Mike Egglestone" References: <5114AA3B02000099000F2CAC@collaborate.seakr.com> In-Reply-To: <5114AA3B02000099000F2CAC@collaborate.seakr.com> MIME-Version: 1.0 Subject: Re: [Xen-users] need advise with a redhat 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="===============2593141196437315405==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org This is a multi-part message in MIME format. --===============2593141196437315405== Content-Type: multipart/alternative; boundary="--=_--e66992f9.e66992ee.cd3b12dc" This is a multi-part message in MIME format. ----=_--e66992f9.e66992ee.cd3b12dc Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit "Nick Couchman" writes: #I think you need to better categorize the statement "performance is crappy." Dig into the performance some and figure out where your bottleneck is - disk, network, CPU, memory?? The standard tools you'd use on a physical machine should work fine on a VM - iostat, vmstat, top, free, sar, etc., etc. Once you nail down where the problem is, you can post back and folks will probably have some better suggestions on how to alleviate specific bottlenecks. Also, let us know what you're doing with #the VM. Running a basic web server? Oracle database server? Compiling code? The tuning will be very different based on where the bottleneck is and what you're trying to do with the system. Sorry, should have been more specific in my OP. Redhat DomU: The network speed at best is around 17MB/sec. And the disk IO is around 140MB/sec (running dd command to create a zero'd file) The DomO network is speed is normal gigabit at around 80MB/sec and the disk IO is around 400+MB/sec. (8 disk RAID 10) My other DomU's such as an hvm Windows 2008 R2 server, and my hvm Debian 6.0 DomU all have normal benchmarks for a typical domU. Both Windows and Debian DomU using PV drivers. Disk Speeds around 230MB/sec and network IO around 70MB/sec Its just this one redhat domU thats not performing well. I'm blaming the old kernel on it. (2.6.18) so perhaps no PV drivers in that kernel. This redhat server will mostly be a frontend webserver fetching data from a database on another different physical server. So, maybe this VM is fine the way it is. I mostly concerned about disk IO and network speed. The network speed and disk IO is considerably slower than my Debian domU. I guess its not that bad after all, but just curious if I can get the full speed out of the redhat kernel. By either installing PVHVM drivers into the redhat kernel, or making the DomU a PV guest. I've been trying to follow the guidelines here: http://wiki.xen.org/wiki/Xen_Linux_PV_on_HVM_drivers#Using_Xen_PVHVM_drivers_with_Ubuntu_HVM_guests Thanks, Mike ----=_--e66992f9.e66992ee.cd3b12dc Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable <=21DOCTYPE HTML PUBLIC =22-//W3C//DTD HTML 4.0 Transitional//EN=22>
"Nick Couchman" <Nick.Couchman=40seakr.com>= writes:
I think you need to better categorize the statement "per= formance is crappy."  Dig into the performance some and figure ou= t where your bottleneck is - disk, network, CPU, memory??  The standar= d tools you'd use on a physical machine should work fine on a VM - iostat, = vmstat, top, free, sar, etc., etc.  Once you nail down where the probl= em is, you can post back and folks will probably have some better suggestio= ns on how to alleviate specific bottlenecks.  Also, let us know what y= ou're doing with the VM.  Running a basic web server?  Oracle dat= abase server?  Compiling code?  The tuning will be very different= based on where the bottleneck is and what you're trying to do with the sys= tem.

Sorry, should have been more specific= in my OP.

Redhat DomU:
The network speed at best is around 1= 7MB/sec.
And the disk IO is around 140MB/sec (= running dd command to create a zero'd file)

The DomO network is speed is normal g= igabit at around 80MB/sec
and the disk IO is around 400+MB/sec.= (8 disk RAID 10)

My other DomU's such as an hvm Window= s 2008 R2 server, and
my hvm Debian 6.0 DomU all have norma= l benchmarks for a typical domU.
Both Windows and Debian DomU using PV= drivers.
Disk Speeds around 230MB/sec and netw= ork IO around 70MB/sec

Its just this one redhat domU thats n= ot performing well. I'm blaming
the old kernel on it. (2.6.18) so per= haps no PV drivers in that kernel.

This redhat server will mostly be a f= rontend webserver fetching data from a database on another
different physical server. So, maybe = this VM is fine the way it is.
I mostly concerned about disk IO and = network speed.
The network speed and disk IO is cons= iderably slower than my Debian domU.
I guess its not that bad after all, b= ut just curious if I can get the full speed out
of the redhat kernel. By either insta= lling PVHVM drivers into the redhat kernel, or making
the DomU a PV guest.  
I've been trying to follow the guidel= ines here:

Thanks,
Mike

----=_--e66992f9.e66992ee.cd3b12dc-- --===============2593141196437315405== 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 --===============2593141196437315405==-- From xen-users-bounces@lists.xen.org Fri Feb 08 20:40:11 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 08 Feb 2013 20:40: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 1U3uiq-00064M-VW; Fri, 08 Feb 2013 20:39:00 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U3uip-00064E-26 for xen-users@lists.xen.org; Fri, 08 Feb 2013 20:38:59 +0000 Received: from [85.158.143.99:48764] by server-1.bemta-4.messagelabs.com id 48/D3-08839-26265115; Fri, 08 Feb 2013 20:38:58 +0000 X-Env-Sender: mike@estone.ca X-Msg-Ref: server-13.tower-216.messagelabs.com!1360355936!30586172!1 X-Originating-IP: [204.209.205.34] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogMjA0LjIwOS4yMDUuMzQgPT4gMTIwMzYy\n X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 31731 invoked from network); 8 Feb 2013 20:38:57 -0000 Received: from defout.telus.net (HELO defout.telus.net) (204.209.205.34) by server-13.tower-216.messagelabs.com with SMTP; 8 Feb 2013 20:38:57 -0000 Received: from edmwcm04 ([204.209.205.31]) by priv-edmwes04.telusplanet.net (InterMail vM.8.01.03.00 201-2260-125-20100507) with ESMTP id <20130208203851.PFSV15363.priv-edmwes04.telusplanet.net@edmwcm04> for ; Fri, 8 Feb 2013 13:38:51 -0700 Received: from estone.ca ([154.20.1.203]) by edmwcm04 with bizsmtp id xwem1k0024NnoEJ01weovW; Fri, 08 Feb 2013 13:38:50 -0700 X-Authority-Analysis: v=1.1 cv=rMclIWNOyWbaRaosMf477BSoDkSAEHI3rR4jEZfW1q4= c=1 sm=2 a=P_U1kJitcyAA:10 a=AJiS3eauAAAA:8 a=mLnsDVdbAAAA:8 a=LI_lRchgKdjjYXHAtm4A:9 a=QEXdDO2ut3YA:10 a=5xNTf9GLujYA:10 a=SSmOFEACAAAA:8 a=iArNVvhu2_IA:10 a=zJJgJrR4LD4A:10 a=frz4AuCg-hUA:10 a=tXsnliwV7b4A:10 a=VIg8ssY0raRGrABO:21 X-Telus-Outbound-IP: 154.20.1.203 Received: from estone.ca ([192.168.1.253] helo=mail.estone.ca) by estone.ca with esmtp (Exim 4.80) (envelope-from ) id 1U3uij-0001RF-9i for xen-users@lists.xen.org; Fri, 08 Feb 2013 12:38:53 -0800 Message-id: X-FC-Thread-ID: 3b9aca00-465dbe96 Date: Fri, 08 Feb 2013 12:38:52 -0800 X-Mailer: FirstClass 11.1 (build 11.128) X-FC-SERVER-TZ: 6554336 To: xen-users@lists.xen.org From: "Mike Egglestone" References: <5114AA3B02000099000F2CAC@collaborate.seakr.com> In-Reply-To: <5114AA3B02000099000F2CAC@collaborate.seakr.com> MIME-Version: 1.0 Subject: Re: [Xen-users] need advise with a redhat 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="===============2593141196437315405==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org This is a multi-part message in MIME format. --===============2593141196437315405== Content-Type: multipart/alternative; boundary="--=_--e66992f9.e66992ee.cd3b12dc" This is a multi-part message in MIME format. ----=_--e66992f9.e66992ee.cd3b12dc Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit "Nick Couchman" writes: #I think you need to better categorize the statement "performance is crappy." Dig into the performance some and figure out where your bottleneck is - disk, network, CPU, memory?? The standard tools you'd use on a physical machine should work fine on a VM - iostat, vmstat, top, free, sar, etc., etc. Once you nail down where the problem is, you can post back and folks will probably have some better suggestions on how to alleviate specific bottlenecks. Also, let us know what you're doing with #the VM. Running a basic web server? Oracle database server? Compiling code? The tuning will be very different based on where the bottleneck is and what you're trying to do with the system. Sorry, should have been more specific in my OP. Redhat DomU: The network speed at best is around 17MB/sec. And the disk IO is around 140MB/sec (running dd command to create a zero'd file) The DomO network is speed is normal gigabit at around 80MB/sec and the disk IO is around 400+MB/sec. (8 disk RAID 10) My other DomU's such as an hvm Windows 2008 R2 server, and my hvm Debian 6.0 DomU all have normal benchmarks for a typical domU. Both Windows and Debian DomU using PV drivers. Disk Speeds around 230MB/sec and network IO around 70MB/sec Its just this one redhat domU thats not performing well. I'm blaming the old kernel on it. (2.6.18) so perhaps no PV drivers in that kernel. This redhat server will mostly be a frontend webserver fetching data from a database on another different physical server. So, maybe this VM is fine the way it is. I mostly concerned about disk IO and network speed. The network speed and disk IO is considerably slower than my Debian domU. I guess its not that bad after all, but just curious if I can get the full speed out of the redhat kernel. By either installing PVHVM drivers into the redhat kernel, or making the DomU a PV guest. I've been trying to follow the guidelines here: http://wiki.xen.org/wiki/Xen_Linux_PV_on_HVM_drivers#Using_Xen_PVHVM_drivers_with_Ubuntu_HVM_guests Thanks, Mike ----=_--e66992f9.e66992ee.cd3b12dc Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable <=21DOCTYPE HTML PUBLIC =22-//W3C//DTD HTML 4.0 Transitional//EN=22>
"Nick Couchman" <Nick.Couchman=40seakr.com>= writes:
I think you need to better categorize the statement "per= formance is crappy."  Dig into the performance some and figure ou= t where your bottleneck is - disk, network, CPU, memory??  The standar= d tools you'd use on a physical machine should work fine on a VM - iostat, = vmstat, top, free, sar, etc., etc.  Once you nail down where the probl= em is, you can post back and folks will probably have some better suggestio= ns on how to alleviate specific bottlenecks.  Also, let us know what y= ou're doing with the VM.  Running a basic web server?  Oracle dat= abase server?  Compiling code?  The tuning will be very different= based on where the bottleneck is and what you're trying to do with the sys= tem.

Sorry, should have been more specific= in my OP.

Redhat DomU:
The network speed at best is around 1= 7MB/sec.
And the disk IO is around 140MB/sec (= running dd command to create a zero'd file)

The DomO network is speed is normal g= igabit at around 80MB/sec
and the disk IO is around 400+MB/sec.= (8 disk RAID 10)

My other DomU's such as an hvm Window= s 2008 R2 server, and
my hvm Debian 6.0 DomU all have norma= l benchmarks for a typical domU.
Both Windows and Debian DomU using PV= drivers.
Disk Speeds around 230MB/sec and netw= ork IO around 70MB/sec

Its just this one redhat domU thats n= ot performing well. I'm blaming
the old kernel on it. (2.6.18) so per= haps no PV drivers in that kernel.

This redhat server will mostly be a f= rontend webserver fetching data from a database on another
different physical server. So, maybe = this VM is fine the way it is.
I mostly concerned about disk IO and = network speed.
The network speed and disk IO is cons= iderably slower than my Debian domU.
I guess its not that bad after all, b= ut just curious if I can get the full speed out
of the redhat kernel. By either insta= lling PVHVM drivers into the redhat kernel, or making
the DomU a PV guest.  
I've been trying to follow the guidel= ines here:

Thanks,
Mike

----=_--e66992f9.e66992ee.cd3b12dc-- --===============2593141196437315405== 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 --===============2593141196437315405==-- From xen-users-bounces@lists.xen.org Fri Feb 08 21:34:12 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 08 Feb 2013 21: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 1U3vZ2-0000Px-Di; Fri, 08 Feb 2013 21:32:56 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U3tBq-0001pg-K0 for xen-users@lists.xen.org; Fri, 08 Feb 2013 19:00:50 +0000 Received: from [85.158.139.211:39878] by server-9.bemta-5.messagelabs.com id A9/92-24440-16B45115; Fri, 08 Feb 2013 19:00:49 +0000 X-Env-Sender: ydev@cs.utah.edu X-Msg-Ref: server-6.tower-206.messagelabs.com!1360350048!21579461!1 X-Originating-IP: [155.98.64.241] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 1173 invoked from network); 8 Feb 2013 19:00:48 -0000 Received: from rio.cs.utah.edu (HELO mail-svr1.cs.utah.edu) (155.98.64.241) by server-6.tower-206.messagelabs.com with SMTP; 8 Feb 2013 19:00:48 -0000 Received: from localhost (localhost [127.0.0.1]) by mail-svr1.cs.utah.edu (Postfix) with ESMTP id 690F86500C5 for ; Fri, 8 Feb 2013 12:00:47 -0700 (MST) X-Virus-Scanned: amavisd-new at cs.utah.edu Received: from mail-svr1.cs.utah.edu ([127.0.0.1]) by localhost (mail-svr1.cs.utah.edu [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xgUqsYpiRafX; Fri, 8 Feb 2013 12:00:47 -0700 (MST) Received: from [128.110.92.242] (128-110-92-242.uconnect.utah.edu [128.110.92.242]) by smtps.cs.utah.edu (Postfix) with ESMTPSA id 0F4796500BC; Fri, 8 Feb 2013 12:00:47 -0700 (MST) Message-ID: <51154B5A.60303@cs.utah.edu> Date: Fri, 08 Feb 2013 12:00:42 -0700 From: Yathindra User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130107 Thunderbird/17.0.2 MIME-Version: 1.0 To: "xen-users@lists.xen.org" X-Mailman-Approved-At: Fri, 08 Feb 2013 21:32:55 +0000 Cc: Yathindra Naik Subject: [Xen-users] Dynamic Debugging X-BeenThere: xen-users@lists.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'm using printk and DPRINTK on several files like drivers/xen/xenbus/xenbus_probe.c, drivers/xen/xenbus/xenbus_probe_backend.c, etc. in Linux-3.7.5 but don't see some of the messages I expected to see in syslog or dmesg. I have printk's in almost all the functions in these files but I don't see most of them. I also enabled CONFIG_DYNAMIC_DEBUG and turned on each of those files for logging in /sys/kernel/debug/dynamic_debug/control but I don't see them anywhere when I'm trying to create a guest domain. Thanks, Yathi _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Fri Feb 08 21:34:12 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 08 Feb 2013 21: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 1U3vZ2-0000Px-Di; Fri, 08 Feb 2013 21:32:56 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U3tBq-0001pg-K0 for xen-users@lists.xen.org; Fri, 08 Feb 2013 19:00:50 +0000 Received: from [85.158.139.211:39878] by server-9.bemta-5.messagelabs.com id A9/92-24440-16B45115; Fri, 08 Feb 2013 19:00:49 +0000 X-Env-Sender: ydev@cs.utah.edu X-Msg-Ref: server-6.tower-206.messagelabs.com!1360350048!21579461!1 X-Originating-IP: [155.98.64.241] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 1173 invoked from network); 8 Feb 2013 19:00:48 -0000 Received: from rio.cs.utah.edu (HELO mail-svr1.cs.utah.edu) (155.98.64.241) by server-6.tower-206.messagelabs.com with SMTP; 8 Feb 2013 19:00:48 -0000 Received: from localhost (localhost [127.0.0.1]) by mail-svr1.cs.utah.edu (Postfix) with ESMTP id 690F86500C5 for ; Fri, 8 Feb 2013 12:00:47 -0700 (MST) X-Virus-Scanned: amavisd-new at cs.utah.edu Received: from mail-svr1.cs.utah.edu ([127.0.0.1]) by localhost (mail-svr1.cs.utah.edu [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xgUqsYpiRafX; Fri, 8 Feb 2013 12:00:47 -0700 (MST) Received: from [128.110.92.242] (128-110-92-242.uconnect.utah.edu [128.110.92.242]) by smtps.cs.utah.edu (Postfix) with ESMTPSA id 0F4796500BC; Fri, 8 Feb 2013 12:00:47 -0700 (MST) Message-ID: <51154B5A.60303@cs.utah.edu> Date: Fri, 08 Feb 2013 12:00:42 -0700 From: Yathindra User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130107 Thunderbird/17.0.2 MIME-Version: 1.0 To: "xen-users@lists.xen.org" X-Mailman-Approved-At: Fri, 08 Feb 2013 21:32:55 +0000 Cc: Yathindra Naik Subject: [Xen-users] Dynamic Debugging X-BeenThere: xen-users@lists.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'm using printk and DPRINTK on several files like drivers/xen/xenbus/xenbus_probe.c, drivers/xen/xenbus/xenbus_probe_backend.c, etc. in Linux-3.7.5 but don't see some of the messages I expected to see in syslog or dmesg. I have printk's in almost all the functions in these files but I don't see most of them. I also enabled CONFIG_DYNAMIC_DEBUG and turned on each of those files for logging in /sys/kernel/debug/dynamic_debug/control but I don't see them anywhere when I'm trying to create a guest domain. Thanks, Yathi _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Sat Feb 09 01:16:05 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sat, 09 Feb 2013 01:16: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 1U3z1f-0003JW-78; Sat, 09 Feb 2013 01:14:43 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U3z1e-0003JR-1O for xen-users@lists.xen.org; Sat, 09 Feb 2013 01:14:42 +0000 Received: from [193.109.254.147:42209] by server-6.bemta-14.messagelabs.com id A1/7E-12010-103A5115; Sat, 09 Feb 2013 01:14:41 +0000 X-Env-Sender: epretorious@yahoo.com X-Msg-Ref: server-11.tower-27.messagelabs.com!1360372478!2223568!1 X-Originating-IP: [98.138.229.115] 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.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 23951 invoked from network); 9 Feb 2013 01:14:40 -0000 Received: from nm36-vm3.bullet.mail.ne1.yahoo.com (HELO nm36-vm3.bullet.mail.ne1.yahoo.com) (98.138.229.115) by server-11.tower-27.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 9 Feb 2013 01:14:40 -0000 Received: from [98.138.226.180] by nm36.bullet.mail.ne1.yahoo.com with NNFMP; 09 Feb 2013 01:13:33 -0000 Received: from [98.138.89.234] by tm15.bullet.mail.ne1.yahoo.com with NNFMP; 09 Feb 2013 01:13:32 -0000 Received: from [127.0.0.1] by omp1049.mail.ne1.yahoo.com with NNFMP; 09 Feb 2013 01:13:32 -0000 X-Yahoo-Newman-Property: ymail-3 X-Yahoo-Newman-Id: 983124.38934.bm@omp1049.mail.ne1.yahoo.com Received: (qmail 90966 invoked by uid 60001); 9 Feb 2013 01:13:32 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1360372412; bh=DdZlAhTUZtLy1Jvh+fECS5jICcUo2CrHIb/Rq35lTDk=; h=X-YMail-OSG:Received:X-Rocket-MIMEInfo:X-Mailer:Message-ID:Date:From:Reply-To:Subject:To:MIME-Version:Content-Type; b=RidG4hQdUmOm7vrwqpFvQMUrrV8Luq7ihN/FZHo57Ib4kVDZ0UyjVxQeqjvoMsibpH1uX/+YwDTMdKHJPycvRI04BPWg/+O1kz4d9NcqY8e9Qg0VRl2TMQdJhfoV3cbOlDUir0jiTZ4ePouMrxFXGziBjKhIg8/rOvYRY4HEFH0= DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=X-YMail-OSG:Received:X-Rocket-MIMEInfo:X-Mailer:Message-ID:Date:From:Reply-To:Subject:To:MIME-Version:Content-Type; b=DP3O+FvNRxKyFBjEQ8AVCXTXP/106VxiY8xaiCQo9TJ521J8/1+4rIFjLhZsoz8zHyfeycXcdUcQM/kxoaOFH56awtaDfbfuH7MweLpbFzY1To1JQ5yB1ZSyuRiN4j6FxrD1NRLIywMpzWn4BQcPDzgWv7o+5Fa61WIns4It59Y=; X-YMail-OSG: BVmzowAVM1nd_tRoL3O5pz92_y8tj1y4iq_E8zyluDNeoy. VMZOQQa2S4W14Iw9L8CCz1N2roVF0p4P1wzcqb1ajVNlH83_nfHyHN75Y84X 0lkXVGkVS9_nWI6xyn.6o3zo1VNjjV.UXoFFW.8Os93k_6_Vrf1rFDOm0Wim 522T_RlLDoV5qulujv9znr13D0o.JLFrbQg9WdbnNCP8PhHIjPVhOxzEkgqf ScwO4Lv_PlaKu7HBVktdCCWoWYm._j31Im9sZJFJrfB2VlydmNeZCdcfZYZ9 EJgpnsPhdprccRtztppafrTCRqZTsBMvOl.92Ck9z.tcsVWOxmD0aprwjb1H udl4ejepDRu4k5k3UB7bEna7L2RhLhagnPWbk7Kf7jTeUrId6UxIKotJghRH v.Bsf4H5WgQy_X6m.1feWsmVfazLMFAV5AwCNUAVVKdJ8eyG2CJ6qLxLH5Xy xSkjd91heatVt6wRbngrdu3eUtmPbMqfQPeWZpzgDKfNPQe8Gi0GOhvBs2Gk hB3ETo6NSP0K9zGTnxPxFQqa1dIiInvLofWCLI6wFzUBWn22AiHkWES5ncdP oIUdxrfxyoOIOagHSAxPxWtjniRDPrjvvz.ka_TMtzzHFIRTbC.ejgPQ5_kr k4w-- Received: from [74.197.253.230] by web126001.mail.ne1.yahoo.com via HTTP; Fri, 08 Feb 2013 17:13:32 PST X-Rocket-MIMEInfo: 001.001, SSd2ZSBjb3BpZWQgdGhlIGNvbnRlbnRzIG9mIHRoZSBPcmFjbGUgTGludXggNi4zIGluc3RhbGxhdGlvbiBtZWRpYSB0byBhbiBkaXJlY3RvcnkgdGhhdCdzIGV4cG9ydGVkIHZpYSBORlM6CgoKc2FuMjp.ICMgbHMgLTEgL3Nydi9tZDEyOC9yZXBvc2l0b3JpZXMvb3JhY2xlLzYuMy9vcy94ODZfNjQvCkVGSQpFVUxBCmV1bGEuZW5fVVMKZXVsYS5weQpHUEwKSGlnaEF2YWlsYWJpbGl0eQppbWFnZXMKaXNvbGludXgKTG9hZEJhbGFuY2VyCm1lZGlhLnJlcG8KUGFja2FnZXMKUkVBRE1FLWVuClJFQURNRS1lbi4BMAEBAQE- X-Mailer: YahooMailWebService/0.8.132.503 Message-ID: <1360372412.38317.YahooMailNeo@web126001.mail.ne1.yahoo.com> Date: Fri, 8 Feb 2013 17:13:32 -0800 (PST) From: Eric To: "xen-users@lists.xen.org" MIME-Version: 1.0 Subject: [Xen-users] Unable to Create an Oracle Linux VM Using virt-install X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: Eric List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============2953175784201028928==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============2953175784201028928== Content-Type: multipart/alternative; boundary="28998604-1765442854-1360372412=:38317" --28998604-1765442854-1360372412=:38317 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable I've copied the contents of the Oracle Linux 6.3 installation media to an d= irectory that's exported via NFS:=0A=0A=0Asan2:~ # ls -1 /srv/md128/reposit= ories/oracle/6.3/os/x86_64/=0AEFI=0AEULA=0Aeula.en_US=0Aeula.py=0AGPL=0AHig= hAvailability=0Aimages=0Aisolinux=0ALoadBalancer=0Amedia.repo=0APackages=0A= README-en=0AREADME-en.html=0ARELEASE-NOTES-en=0ARELEASE-NOTES-en.html=0AREL= EASE-NOTES-x86_64-en=0ARELEASE-NOTES-x86_64-en.html=0ARELEASE-NOTES-x86-en= =0ARELEASE-NOTES-x86-en.html=0Arepodata=0AResilientStorage=0ARPM-GPG-KEY=0A= RPM-GPG-KEY-oracle=0AScalableFileSystem=0AServer=0Asupportinfo=0ATRANS.TBL= =0AUEK2=0A=0A...and tried to use the directory to install an Oracle Linux V= M with virt-install:=0A=0A=0Axen2:~ # virt-install -p --name dns2 --ram 786= --disk /dev/disk/by-id/scsi-14945540000000000705f69534353492d73616e315f310= 000 --location nfs://192.168.0.2/srv/md128/repositories/oracle/6.3/os/x86_6= 4/ --graphics none=0A=0A...but virt-install complains:=0A=0A=0AStarting ins= tall...=0AERROR=A0=A0=A0 Couldn't find xen kernel for Red Hat Enterprise Li= nux tree.=0A=0AThis is a tried-and-true methodology: I use this method for = installing CentOS & SuSE regularly:=0A=0A=0Asan2:~ # ls -1 /srv/md128/repos= itories/centos/6.3/os/x86_64/=0ACentOS_BuildTag=0A.discinfo=0AEFI=0AEULA=0A= GPL=0Aimages=0Aisolinux=0APackages=0ARELEASE-NOTES-en-US.html=0Arepodata=0A= RPM-GPG-KEY-CentOS-6=0ARPM-GPG-KEY-CentOS-Debug-6=0ARPM-GPG-KEY-CentOS-Secu= rity-6=0ARPM-GPG-KEY-CentOS-Testing-6=0A.treeinfo=0A=0Axen2:~ # virt-instal= l -p --name dns2 --ram 786 --disk /dev/disk/by-id/scsi-14945540000000000705= f69534353492d73616e315f310000 --location nfs://192.168.0.2/srv/md128/reposi= tories/centos/6.3/os/x86_64/ --graphics none=0A=0AWhat is it that's differe= nt about the Oracle Linux installation media that causes this failure? Is t= here a workaround?=0A=0AEric Pretorious=0ATruckee, CA =0A --28998604-1765442854-1360372412=:38317 Content-Type: text/html; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable
I've copi= ed the contents of the Oracle Linux 6.3 installation media to an directory = that's exported via NFS:

san2:~ # = ls -1 /srv/md128/repositories/oracle= /6.3/os/x86_64/
EFI
EULA
eula.en_US
eula.py
GPL
Hi= ghAvailability
images
isolinux
LoadBalancer
media.repo
Packa= ges
README-en
README-en.html
RELEASE-NOTES-en
RELEASE-NOTES-en.= html
RELEASE-NOTES-x86_64-en
RELEASE-NOTES-x86_64-en.html
RELEASE-= NOTES-x86-en
RELEASE-NOTES-x86-en.html
repodata
ResilientStorageRPM-GPG-KEY
RPM-GPG-KEY-oracle
ScalableFileSystem
Server
supp= ortinfo
TRANS.TBL
UEK2

...and tried to use the directory= to install an Oracle Linux VM with virt-install:

xen2:~ # virt-install -p --name dns2 --ram 78= 6 --disk /dev/disk/by-id/scsi-14945540000000000705f69534353492d73616e315f31= 0000 --location nfs://192.168.0.2/srv/md128/repositories/oracle/6.3/os/x86_64/ --graphics none

...but virt-install complains:

Starting install...
ERROR    Couldn't find xen kernel = for Red Hat Enterprise Linux tree.

This is a tried-and-true me= thodology: I use this method for installing CentOS & SuSE regularly:
san2:~ # ls -1 /srv/md128/repositori= es/centos/6.3/os/x86_64/
CentOS_BuildTag
.discinfo
EFI<= br>EULA
GPL
images
isolinux
Packages
RELEASE-NOTES-en-US.htm= l
repodata
RPM-GPG-KEY-CentOS-6
RPM-GPG-KEY-CentOS-Debug-6
RPM-= GPG-KEY-CentOS-Security-6
RPM-GPG-KEY-CentOS-Testing-6
.treeinfo
<= br>xen2:~ # virt-install -p --name dns2 --ram 786 --disk /dev/disk/by-id/sc= si-14945540000000000705f69534353492d73616e315f310000 --location nfs://192.1= 68.0.2/srv/md128/repositories/cento= s/6.3/os/x86_64/ --graphics none

What is it that's diff= erent about the Oracle Linux installation media that causes this failure? I= s there a workaround?

Eric Pretorious
Truckee, CA
--28998604-1765442854-1360372412=:38317-- --===============2953175784201028928== 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 --===============2953175784201028928==-- From xen-users-bounces@lists.xen.org Sat Feb 09 01:16:05 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sat, 09 Feb 2013 01:16: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 1U3z1f-0003JW-78; Sat, 09 Feb 2013 01:14:43 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U3z1e-0003JR-1O for xen-users@lists.xen.org; Sat, 09 Feb 2013 01:14:42 +0000 Received: from [193.109.254.147:42209] by server-6.bemta-14.messagelabs.com id A1/7E-12010-103A5115; Sat, 09 Feb 2013 01:14:41 +0000 X-Env-Sender: epretorious@yahoo.com X-Msg-Ref: server-11.tower-27.messagelabs.com!1360372478!2223568!1 X-Originating-IP: [98.138.229.115] 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.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 23951 invoked from network); 9 Feb 2013 01:14:40 -0000 Received: from nm36-vm3.bullet.mail.ne1.yahoo.com (HELO nm36-vm3.bullet.mail.ne1.yahoo.com) (98.138.229.115) by server-11.tower-27.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 9 Feb 2013 01:14:40 -0000 Received: from [98.138.226.180] by nm36.bullet.mail.ne1.yahoo.com with NNFMP; 09 Feb 2013 01:13:33 -0000 Received: from [98.138.89.234] by tm15.bullet.mail.ne1.yahoo.com with NNFMP; 09 Feb 2013 01:13:32 -0000 Received: from [127.0.0.1] by omp1049.mail.ne1.yahoo.com with NNFMP; 09 Feb 2013 01:13:32 -0000 X-Yahoo-Newman-Property: ymail-3 X-Yahoo-Newman-Id: 983124.38934.bm@omp1049.mail.ne1.yahoo.com Received: (qmail 90966 invoked by uid 60001); 9 Feb 2013 01:13:32 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1360372412; bh=DdZlAhTUZtLy1Jvh+fECS5jICcUo2CrHIb/Rq35lTDk=; h=X-YMail-OSG:Received:X-Rocket-MIMEInfo:X-Mailer:Message-ID:Date:From:Reply-To:Subject:To:MIME-Version:Content-Type; b=RidG4hQdUmOm7vrwqpFvQMUrrV8Luq7ihN/FZHo57Ib4kVDZ0UyjVxQeqjvoMsibpH1uX/+YwDTMdKHJPycvRI04BPWg/+O1kz4d9NcqY8e9Qg0VRl2TMQdJhfoV3cbOlDUir0jiTZ4ePouMrxFXGziBjKhIg8/rOvYRY4HEFH0= DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=X-YMail-OSG:Received:X-Rocket-MIMEInfo:X-Mailer:Message-ID:Date:From:Reply-To:Subject:To:MIME-Version:Content-Type; b=DP3O+FvNRxKyFBjEQ8AVCXTXP/106VxiY8xaiCQo9TJ521J8/1+4rIFjLhZsoz8zHyfeycXcdUcQM/kxoaOFH56awtaDfbfuH7MweLpbFzY1To1JQ5yB1ZSyuRiN4j6FxrD1NRLIywMpzWn4BQcPDzgWv7o+5Fa61WIns4It59Y=; X-YMail-OSG: BVmzowAVM1nd_tRoL3O5pz92_y8tj1y4iq_E8zyluDNeoy. VMZOQQa2S4W14Iw9L8CCz1N2roVF0p4P1wzcqb1ajVNlH83_nfHyHN75Y84X 0lkXVGkVS9_nWI6xyn.6o3zo1VNjjV.UXoFFW.8Os93k_6_Vrf1rFDOm0Wim 522T_RlLDoV5qulujv9znr13D0o.JLFrbQg9WdbnNCP8PhHIjPVhOxzEkgqf ScwO4Lv_PlaKu7HBVktdCCWoWYm._j31Im9sZJFJrfB2VlydmNeZCdcfZYZ9 EJgpnsPhdprccRtztppafrTCRqZTsBMvOl.92Ck9z.tcsVWOxmD0aprwjb1H udl4ejepDRu4k5k3UB7bEna7L2RhLhagnPWbk7Kf7jTeUrId6UxIKotJghRH v.Bsf4H5WgQy_X6m.1feWsmVfazLMFAV5AwCNUAVVKdJ8eyG2CJ6qLxLH5Xy xSkjd91heatVt6wRbngrdu3eUtmPbMqfQPeWZpzgDKfNPQe8Gi0GOhvBs2Gk hB3ETo6NSP0K9zGTnxPxFQqa1dIiInvLofWCLI6wFzUBWn22AiHkWES5ncdP oIUdxrfxyoOIOagHSAxPxWtjniRDPrjvvz.ka_TMtzzHFIRTbC.ejgPQ5_kr k4w-- Received: from [74.197.253.230] by web126001.mail.ne1.yahoo.com via HTTP; Fri, 08 Feb 2013 17:13:32 PST X-Rocket-MIMEInfo: 001.001, SSd2ZSBjb3BpZWQgdGhlIGNvbnRlbnRzIG9mIHRoZSBPcmFjbGUgTGludXggNi4zIGluc3RhbGxhdGlvbiBtZWRpYSB0byBhbiBkaXJlY3RvcnkgdGhhdCdzIGV4cG9ydGVkIHZpYSBORlM6CgoKc2FuMjp.ICMgbHMgLTEgL3Nydi9tZDEyOC9yZXBvc2l0b3JpZXMvb3JhY2xlLzYuMy9vcy94ODZfNjQvCkVGSQpFVUxBCmV1bGEuZW5fVVMKZXVsYS5weQpHUEwKSGlnaEF2YWlsYWJpbGl0eQppbWFnZXMKaXNvbGludXgKTG9hZEJhbGFuY2VyCm1lZGlhLnJlcG8KUGFja2FnZXMKUkVBRE1FLWVuClJFQURNRS1lbi4BMAEBAQE- X-Mailer: YahooMailWebService/0.8.132.503 Message-ID: <1360372412.38317.YahooMailNeo@web126001.mail.ne1.yahoo.com> Date: Fri, 8 Feb 2013 17:13:32 -0800 (PST) From: Eric To: "xen-users@lists.xen.org" MIME-Version: 1.0 Subject: [Xen-users] Unable to Create an Oracle Linux VM Using virt-install X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: Eric List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============2953175784201028928==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============2953175784201028928== Content-Type: multipart/alternative; boundary="28998604-1765442854-1360372412=:38317" --28998604-1765442854-1360372412=:38317 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable I've copied the contents of the Oracle Linux 6.3 installation media to an d= irectory that's exported via NFS:=0A=0A=0Asan2:~ # ls -1 /srv/md128/reposit= ories/oracle/6.3/os/x86_64/=0AEFI=0AEULA=0Aeula.en_US=0Aeula.py=0AGPL=0AHig= hAvailability=0Aimages=0Aisolinux=0ALoadBalancer=0Amedia.repo=0APackages=0A= README-en=0AREADME-en.html=0ARELEASE-NOTES-en=0ARELEASE-NOTES-en.html=0AREL= EASE-NOTES-x86_64-en=0ARELEASE-NOTES-x86_64-en.html=0ARELEASE-NOTES-x86-en= =0ARELEASE-NOTES-x86-en.html=0Arepodata=0AResilientStorage=0ARPM-GPG-KEY=0A= RPM-GPG-KEY-oracle=0AScalableFileSystem=0AServer=0Asupportinfo=0ATRANS.TBL= =0AUEK2=0A=0A...and tried to use the directory to install an Oracle Linux V= M with virt-install:=0A=0A=0Axen2:~ # virt-install -p --name dns2 --ram 786= --disk /dev/disk/by-id/scsi-14945540000000000705f69534353492d73616e315f310= 000 --location nfs://192.168.0.2/srv/md128/repositories/oracle/6.3/os/x86_6= 4/ --graphics none=0A=0A...but virt-install complains:=0A=0A=0AStarting ins= tall...=0AERROR=A0=A0=A0 Couldn't find xen kernel for Red Hat Enterprise Li= nux tree.=0A=0AThis is a tried-and-true methodology: I use this method for = installing CentOS & SuSE regularly:=0A=0A=0Asan2:~ # ls -1 /srv/md128/repos= itories/centos/6.3/os/x86_64/=0ACentOS_BuildTag=0A.discinfo=0AEFI=0AEULA=0A= GPL=0Aimages=0Aisolinux=0APackages=0ARELEASE-NOTES-en-US.html=0Arepodata=0A= RPM-GPG-KEY-CentOS-6=0ARPM-GPG-KEY-CentOS-Debug-6=0ARPM-GPG-KEY-CentOS-Secu= rity-6=0ARPM-GPG-KEY-CentOS-Testing-6=0A.treeinfo=0A=0Axen2:~ # virt-instal= l -p --name dns2 --ram 786 --disk /dev/disk/by-id/scsi-14945540000000000705= f69534353492d73616e315f310000 --location nfs://192.168.0.2/srv/md128/reposi= tories/centos/6.3/os/x86_64/ --graphics none=0A=0AWhat is it that's differe= nt about the Oracle Linux installation media that causes this failure? Is t= here a workaround?=0A=0AEric Pretorious=0ATruckee, CA =0A --28998604-1765442854-1360372412=:38317 Content-Type: text/html; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable
I've copi= ed the contents of the Oracle Linux 6.3 installation media to an directory = that's exported via NFS:

san2:~ # = ls -1 /srv/md128/repositories/oracle= /6.3/os/x86_64/
EFI
EULA
eula.en_US
eula.py
GPL
Hi= ghAvailability
images
isolinux
LoadBalancer
media.repo
Packa= ges
README-en
README-en.html
RELEASE-NOTES-en
RELEASE-NOTES-en.= html
RELEASE-NOTES-x86_64-en
RELEASE-NOTES-x86_64-en.html
RELEASE-= NOTES-x86-en
RELEASE-NOTES-x86-en.html
repodata
ResilientStorageRPM-GPG-KEY
RPM-GPG-KEY-oracle
ScalableFileSystem
Server
supp= ortinfo
TRANS.TBL
UEK2

...and tried to use the directory= to install an Oracle Linux VM with virt-install:

xen2:~ # virt-install -p --name dns2 --ram 78= 6 --disk /dev/disk/by-id/scsi-14945540000000000705f69534353492d73616e315f31= 0000 --location nfs://192.168.0.2/srv/md128/repositories/oracle/6.3/os/x86_64/ --graphics none

...but virt-install complains:

Starting install...
ERROR    Couldn't find xen kernel = for Red Hat Enterprise Linux tree.

This is a tried-and-true me= thodology: I use this method for installing CentOS & SuSE regularly:
san2:~ # ls -1 /srv/md128/repositori= es/centos/6.3/os/x86_64/
CentOS_BuildTag
.discinfo
EFI<= br>EULA
GPL
images
isolinux
Packages
RELEASE-NOTES-en-US.htm= l
repodata
RPM-GPG-KEY-CentOS-6
RPM-GPG-KEY-CentOS-Debug-6
RPM-= GPG-KEY-CentOS-Security-6
RPM-GPG-KEY-CentOS-Testing-6
.treeinfo
<= br>xen2:~ # virt-install -p --name dns2 --ram 786 --disk /dev/disk/by-id/sc= si-14945540000000000705f69534353492d73616e315f310000 --location nfs://192.1= 68.0.2/srv/md128/repositories/cento= s/6.3/os/x86_64/ --graphics none

What is it that's diff= erent about the Oracle Linux installation media that causes this failure? I= s there a workaround?

Eric Pretorious
Truckee, CA
--28998604-1765442854-1360372412=:38317-- --===============2953175784201028928== 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 --===============2953175784201028928==-- From xen-users-bounces@lists.xen.org Sat Feb 09 02:14:51 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sat, 09 Feb 2013 02: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 1U3zwE-0005O2-43; Sat, 09 Feb 2013 02:13:10 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U3zwB-0005Mx-NT for xen-users@lists.xen.org; Sat, 09 Feb 2013 02:13:08 +0000 Received: from [85.158.139.211:40783] by server-6.bemta-5.messagelabs.com id 7B/97-01489-2B0B5115; Sat, 09 Feb 2013 02:13:06 +0000 X-Env-Sender: matthias.kannenberg@googlemail.com X-Msg-Ref: server-7.tower-206.messagelabs.com!1360375986!21349597!1 X-Originating-IP: [209.85.212.175] X-SpamReason: No, hits=0.3 required=7.0 tests=RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 21569 invoked from network); 9 Feb 2013 02:13:06 -0000 Received: from mail-wi0-f175.google.com (HELO mail-wi0-f175.google.com) (209.85.212.175) by server-7.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 9 Feb 2013 02:13:06 -0000 Received: by mail-wi0-f175.google.com with SMTP id l13so1531407wie.8 for ; Fri, 08 Feb 2013 18:13:06 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=20120113; h=x-received:mime-version:from:date:message-id:subject:to:cc :content-type; bh=VjC1hBG0fiBO8wuZhDQaRXyEDVtcjvzPHMS8DBXPlRY=; b=mKL5pIX04rK7icqf4LyR2ELi/jm18q1CtEtYoegNx33DOfqmB+pOmSxtuZ/RO0dlnY EBM1m7IdxfkxoNCCbKxVb69m6BVO/y4l/wwC9CFKGBznsMQ0fYcgiJKCg1HvIOX3hFs+ icSH5RUqW8E9SO5SkGQvTN52MXQIjobRaoitvA80jXMRV895R35HsyoeTvm1tZ6bLIXK osRxLLiBsAkpy4zgGmXaMJraCtTtu/rk4MElVweHoDnOOWqc81fN7De61ENsJYcjmUFC Yuy4kkxQhqryhWORdNPOEdUPnh14ca0P8fvf+LLYFoP1EiFBoWDl7KEXmx3bs28lSu7D hYNg== X-Received: by 10.194.109.10 with SMTP id ho10mr13205639wjb.16.1360375986168; Fri, 08 Feb 2013 18:13:06 -0800 (PST) MIME-Version: 1.0 Received: by 10.194.80.68 with HTTP; Fri, 8 Feb 2013 18:12:46 -0800 (PST) From: Matthias Date: Sat, 9 Feb 2013 03:12:46 +0100 Message-ID: To: jbeulich@suse.com, boris.ostrovsky@amd.com Cc: xen-users@lists.xen.org Subject: [Xen-users] Latest AMD, IOMMU Security Change causing CPU0 Panic and general Problems with AMD+IOMMU changes X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: 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, unfortunatly your latest change "AMD,IOMMU: Clean up old entries in remapping tables when creating new one" (Changeset 26517 in xen-unstable and 25975 in xen-4.2-testing) is causing a CPU0 Panic at boot for me. When i tried to boot latest versions of xen unstable or xen-testing, my dom0 gives me the message: (XEN) ************************************* (XEN) Panic on CPU 0: (XEN) DATAL PAGE FAULT (XEN) [error_code=0000] (XEN) Faulting linear address: 0000000000000000 (XEN) ************************************* I can reproduce this with vanilla kernels 3.8-rc6, 3.7.6, 3.7.4 and Debian Kernel 3.2.0-2. My System: CPU: AMD Phenom II 1090T Mainboard: Asus Crosshair IV Ram: 16GB VGA: AMD HD5700 + AMD HD5450 OS: latest Debian Wheezy Compiler: gcc 4.7.2 Grub lines: multiboot /boot/xen.gz dom0_mem=2048M loglvl=all guest_loglvl=all iommu=1 module /boot/vmlinuz-3.7.6-xen root=/dev/sda1 ro xen-pciback.hide=(06:00.0)(06:00.1)(00:12.0)(00:12.2)(00:14.5)(00:16.0)(00:16.2) xen-pciback.permissive After the error I did a bisection of the current xen-unstable and found 26516 being the last working one for me. So 26517 (the above changeset) is the faulting one. When reverting the specific changeset, my server boots beyond the point of the previous pagefault, but runs in some serious trouble later in the boot process when trying to establish the data link. I'm seeing multiple errors like: ata1.00: qc timeout (cmd 0xec) ata1.00: failed to IDENTIFY (I/O error, err_mask=0x4) ata9.00: TEST_UNIT_READY failed (err_mask=0x5) and generally a lot of disk time outs. The server, not able to mount any root devices, later reverts to the initramfs. So basically besides the above mentioned CPU Panic, i got other issues with your changes which prevent a clear boot. Are there any prerequisites for your changes I am missing or can I help in any way with fixing this? _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Sat Feb 09 02:14:51 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sat, 09 Feb 2013 02: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 1U3zwE-0005O2-43; Sat, 09 Feb 2013 02:13:10 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U3zwB-0005Mx-NT for xen-users@lists.xen.org; Sat, 09 Feb 2013 02:13:08 +0000 Received: from [85.158.139.211:40783] by server-6.bemta-5.messagelabs.com id 7B/97-01489-2B0B5115; Sat, 09 Feb 2013 02:13:06 +0000 X-Env-Sender: matthias.kannenberg@googlemail.com X-Msg-Ref: server-7.tower-206.messagelabs.com!1360375986!21349597!1 X-Originating-IP: [209.85.212.175] X-SpamReason: No, hits=0.3 required=7.0 tests=RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 21569 invoked from network); 9 Feb 2013 02:13:06 -0000 Received: from mail-wi0-f175.google.com (HELO mail-wi0-f175.google.com) (209.85.212.175) by server-7.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 9 Feb 2013 02:13:06 -0000 Received: by mail-wi0-f175.google.com with SMTP id l13so1531407wie.8 for ; Fri, 08 Feb 2013 18:13:06 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=20120113; h=x-received:mime-version:from:date:message-id:subject:to:cc :content-type; bh=VjC1hBG0fiBO8wuZhDQaRXyEDVtcjvzPHMS8DBXPlRY=; b=mKL5pIX04rK7icqf4LyR2ELi/jm18q1CtEtYoegNx33DOfqmB+pOmSxtuZ/RO0dlnY EBM1m7IdxfkxoNCCbKxVb69m6BVO/y4l/wwC9CFKGBznsMQ0fYcgiJKCg1HvIOX3hFs+ icSH5RUqW8E9SO5SkGQvTN52MXQIjobRaoitvA80jXMRV895R35HsyoeTvm1tZ6bLIXK osRxLLiBsAkpy4zgGmXaMJraCtTtu/rk4MElVweHoDnOOWqc81fN7De61ENsJYcjmUFC Yuy4kkxQhqryhWORdNPOEdUPnh14ca0P8fvf+LLYFoP1EiFBoWDl7KEXmx3bs28lSu7D hYNg== X-Received: by 10.194.109.10 with SMTP id ho10mr13205639wjb.16.1360375986168; Fri, 08 Feb 2013 18:13:06 -0800 (PST) MIME-Version: 1.0 Received: by 10.194.80.68 with HTTP; Fri, 8 Feb 2013 18:12:46 -0800 (PST) From: Matthias Date: Sat, 9 Feb 2013 03:12:46 +0100 Message-ID: To: jbeulich@suse.com, boris.ostrovsky@amd.com Cc: xen-users@lists.xen.org Subject: [Xen-users] Latest AMD, IOMMU Security Change causing CPU0 Panic and general Problems with AMD+IOMMU changes X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: 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, unfortunatly your latest change "AMD,IOMMU: Clean up old entries in remapping tables when creating new one" (Changeset 26517 in xen-unstable and 25975 in xen-4.2-testing) is causing a CPU0 Panic at boot for me. When i tried to boot latest versions of xen unstable or xen-testing, my dom0 gives me the message: (XEN) ************************************* (XEN) Panic on CPU 0: (XEN) DATAL PAGE FAULT (XEN) [error_code=0000] (XEN) Faulting linear address: 0000000000000000 (XEN) ************************************* I can reproduce this with vanilla kernels 3.8-rc6, 3.7.6, 3.7.4 and Debian Kernel 3.2.0-2. My System: CPU: AMD Phenom II 1090T Mainboard: Asus Crosshair IV Ram: 16GB VGA: AMD HD5700 + AMD HD5450 OS: latest Debian Wheezy Compiler: gcc 4.7.2 Grub lines: multiboot /boot/xen.gz dom0_mem=2048M loglvl=all guest_loglvl=all iommu=1 module /boot/vmlinuz-3.7.6-xen root=/dev/sda1 ro xen-pciback.hide=(06:00.0)(06:00.1)(00:12.0)(00:12.2)(00:14.5)(00:16.0)(00:16.2) xen-pciback.permissive After the error I did a bisection of the current xen-unstable and found 26516 being the last working one for me. So 26517 (the above changeset) is the faulting one. When reverting the specific changeset, my server boots beyond the point of the previous pagefault, but runs in some serious trouble later in the boot process when trying to establish the data link. I'm seeing multiple errors like: ata1.00: qc timeout (cmd 0xec) ata1.00: failed to IDENTIFY (I/O error, err_mask=0x4) ata9.00: TEST_UNIT_READY failed (err_mask=0x5) and generally a lot of disk time outs. The server, not able to mount any root devices, later reverts to the initramfs. So basically besides the above mentioned CPU Panic, i got other issues with your changes which prevent a clear boot. Are there any prerequisites for your changes I am missing or can I help in any way with fixing this? _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Sat Feb 09 12:08:52 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sat, 09 Feb 2013 12:08: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 1U49D8-0006d8-51; Sat, 09 Feb 2013 12:07:14 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U3xRF-0004VK-E6 for xen-users@lists.xen.org; Fri, 08 Feb 2013 23:33:01 +0000 Received: from [85.158.143.35:60650] by server-3.bemta-4.messagelabs.com id 3B/51-08920-C2B85115; Fri, 08 Feb 2013 23:33:00 +0000 X-Env-Sender: ydev@cs.utah.edu X-Msg-Ref: server-2.tower-21.messagelabs.com!1360366378!4767831!1 X-Originating-IP: [155.98.64.241] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 26801 invoked from network); 8 Feb 2013 23:32:58 -0000 Received: from rio.cs.utah.edu (HELO mail-svr1.cs.utah.edu) (155.98.64.241) by server-2.tower-21.messagelabs.com with SMTP; 8 Feb 2013 23:32:58 -0000 Received: from localhost (localhost [127.0.0.1]) by mail-svr1.cs.utah.edu (Postfix) with ESMTP id A01A76500BC; Fri, 8 Feb 2013 16:32:57 -0700 (MST) X-Virus-Scanned: amavisd-new at cs.utah.edu Received: from mail-svr1.cs.utah.edu ([127.0.0.1]) by localhost (mail-svr1.cs.utah.edu [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3ORu-1S9cuGN; Fri, 8 Feb 2013 16:32:48 -0700 (MST) Received: from [128.110.92.242] (128-110-92-242.uconnect.utah.edu [128.110.92.242]) by smtps.cs.utah.edu (Postfix) with ESMTPSA id 35F446500B7; Fri, 8 Feb 2013 16:32:48 -0700 (MST) Message-ID: <51158B1B.8090007@cs.utah.edu> Date: Fri, 08 Feb 2013 16:32:43 -0700 From: Yathindra User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130107 Thunderbird/17.0.2 MIME-Version: 1.0 To: "xen-users@lists.xen.org" References: <510DC655.5060205@cs.utah.edu> <510E3195.1010004@citrix.com> <510EA374.6060509@cs.utah.edu> <5110D7EC.8040608@citrix.com> <51113D59.7030003@cs.utah.edu> <51114B35.5050202@citrix.com> <5111C3B6.1070705@cs.utah.edu> In-Reply-To: <5111C3B6.1070705@cs.utah.edu> X-Mailman-Approved-At: Sat, 09 Feb 2013 12:07:12 +0000 Cc: =?ISO-8859-1?Q?Roger_Pau_Monn=E9?= Subject: Re: [Xen-users] xen_blkbk times out before getting connected X-BeenThere: xen-users@lists.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 2/5/2013 7:45 PM, Yathindra wrote: > On 2/5/2013 11:11 AM, Roger Pau Monn=E9 wrote: >> On 05/02/13 18:11, Yathindra wrote: >>> DomU configuration file looks like this: >> Please don't do top posting. >> >>> kernel =3D "/boot/vmlinuz-3.8.0-rc5+" >>> ramdisk =3D "/boot/initrd.img-3.8.0-rc5+" >>> memory =3D 500 >>> name =3D "guest2" >>> disk =3D ['phy:/dev/loop0,sda1,w'] >> Why are you using sda1 instead of xvda1? >> >>> root =3D "/dev/disk/by-path/xen-vbd-2049 ro" >>> extra =3D 'xencons=3Dtty' >> You can use: >> >> extra=3D"root=3D/dev/xvda1" >> >>> On 2/5/2013 2:59 AM, Roger Pau Monn=E9 wrote: >>>> On 03/02/13 18:50, Yathindra wrote: >>>>> I'm using the latest linux kernel 3.8.0 with Xen 4.3-unstable. = >>>>> Xenstored >>>>> is being started at boot time. >>>>> I did not see any message (dmesg/syslog/console) about device being >>>>> plugged in but xenstore-ls shows me all >>>>> the entries backend and frontend. >>>> Could you post your DomU configuration file also? >>>> >>>>> Here are some details >>>>> ------------------------------ >>>>> From /var/log/syslog: >>>>> >>>>> Feb 3 10:37:31 localhost kernel: [ 36.466359] Event-channel device >>>>> installed. >>>>> Feb 3 10:37:31 localhost kernel: [ 36.636358] Register >>>>> xen_blkbk_driver <<< custom debug message I added >>>>> Feb 3 10:37:31 localhost kernel: [ 36.636367] >>>>> xenbus_register_backend <<< custom debug message I added >>>>> Feb 3 10:37:31 localhost kernel: [ 36.683533] = >>>>> xenbus_register_backend >>>>> Feb 3 10:37:31 localhost kernel: [ 36.830115] xen-pciback: = >>>>> backend is >>>>> vpci <<< custom debug message I added >>>>> Feb 3 10:37:31 localhost kernel: [ 36.830123] >>>>> xenbus_register_backend <<< custom debug message I added >>>>> Feb 3 10:37:32 localhost xenstored: Checking store ... >>>>> Feb 3 10:37:32 localhost xenstored: Checking store complete. >>>>> Feb 3 10:37:32 localhost kernel: [ 37.075217] xenbus_probe: = >>>>> xenstored >>>>> is ready <<< custom debug message I added >>>>> Feb 3 10:37:32 localhost kernel: [ 37.075230] watching node >>>>> FFFFFFFF81C7D1A0 >>>>> Feb 3 10:37:32 localhost kernel: [ 37.081309] xenbus_scanf for = >>>>> node cpu/0 >>>>> Feb 3 10:37:32 localhost kernel: [ 37.081327] XENBUS xen store = >>>>> gave: >>>>> unknown error cpu >>>>> Feb 3 10:37:32 localhost kernel: [ 37.081333] xenbus_scanf for = >>>>> node cpu/1 >>>>> Feb 3 10:37:32 localhost kernel: [ 37.085327] XENBUS unexpected = >>>>> type >>>>> [17], expected [2] >>>>> Feb 3 10:37:32 localhost kernel: [ 37.085342] watching node >>>>> FFFFFFFF81C7D0C0 >>>>> Feb 3 10:37:32 localhost kernel: [ 37.086857] XENBUS unexpected = >>>>> type >>>>> [17], expected [4] >>>>> Feb 3 10:37:32 localhost kernel: [ 37.086865] Failed to set = >>>>> shutdown >>>>> watcher >>>>> Feb 3 10:37:32 localhost kernel: [ 37.086880] = >>>>> backend_probe_and_watch >>>>> - enumerates devices in xenstore and watches for changes <<< custom >>>>> debug message I added >>>>> Feb 3 10:37:32 localhost kernel: [ 37.089401] XENBUS unexpected = >>>>> type >>>>> [4], expected [1] >>>>> Feb 3 10:37:32 localhost kernel: [ 37.089411] watching node >>>>> FFFFFFFF81C7D660 >>>>> Feb 3 10:37:32 localhost kernel: [ 37.090715] XENBUS xen store = >>>>> gave: >>>>> unknown error control/shutdown >>>>> Feb 3 10:37:32 localhost kernel: [ 37.090725] >>>>> frontend_probe_and_watch: calling xenbus_probe_devices <<< custom = >>>>> debug >>>>> message I added >>>>> Feb 3 10:37:32 localhost kernel: [ 37.092362] XENBUS unexpected = >>>>> type >>>>> [17], expected [1] >>>>> Feb 3 10:37:32 localhost kernel: [ 37.092376] watching node >>>>> FFFFFFFF81C7D820 >>>>> Feb 3 10:37:32 localhost kernel: [ 37.093334] watching node >>>>> FFFFFFFF81C7DB20 >>>>> Feb 3 10:37:32 localhost kernel: [ 37.094454] XENBUS xen store = >>>>> gave: >>>>> unknown error backend <<< still not sure how critical this is >>>>> Feb 3 10:37:32 localhost kernel: [ 37.094463] Failed to set = >>>>> balloon >>>>> watcher <<< still not sure how >>>>> critical this is >>>>> >>>>> > xenstore-ls >>>>> tool =3D "" >>>>> xenstored =3D "" >>>>> local =3D "" >>>>> domain =3D "" >>>>> 0 =3D "" >>>>> data =3D "" >>>>> meminfo_total =3D "930680" >>>>> meminfo_free =3D "691868" >>>>> os_name =3D "Ubuntu 12.04.1 LTS" >>>>> os_majorver =3D "12" >>>>> os_minorver =3D "04" >>>>> os_uname =3D "3.8.0-rc5+" >>>>> os_distro =3D "ubuntu" >>>>> updated =3D "Sun Feb 3 10:43:32 MST 2013" >>>>> name =3D "Domain-0" >>>>> attr =3D "" >>>>> xenbr0 =3D "" >>>>> ip =3D "155.98.39.2" >>>>> PVAddons =3D "" >>>>> MajorVersion =3D "5" >>>>> MinorVersion =3D "5" >>>>> MicroVersion =3D "0" >>>>> BuildVersion =3D "17913" >>>>> Installed =3D "1" >>>>> device-model =3D "" >>>>> 0 =3D "" >>>>> state =3D "running" >>>>> >>>>> After this I start the guest domain, here's the xenstore entries, >>>>> >>>>> nodea:~> sudo xenstore-ls >>>>> tool =3D "" >>>>> xenstored =3D "" >>>>> local =3D "" >>>>> domain =3D "" >>>>> 0 =3D "" >>>>> data =3D "" >>>>> meminfo_total =3D "930680" >>>>> meminfo_free =3D "695408" >>>>> os_name =3D "Ubuntu 12.04.1 LTS" >>>>> os_majorver =3D "12" >>>>> os_minorver =3D "04" >>>>> os_uname =3D "3.8.0-rc5+" >>>>> os_distro =3D "ubuntu" >>>>> updated =3D "Sun Feb 3 10:45:32 MST 2013" >>>>> name =3D "Domain-0" >>>>> attr =3D "" >>>>> xenbr0 =3D "" >>>>> ip =3D "155.98.39.2" >>>>> PVAddons =3D "" >>>>> MajorVersion =3D "5" >>>>> MinorVersion =3D "5" >>>>> MicroVersion =3D "0" >>>>> BuildVersion =3D "17913" >>>>> Installed =3D "1" >>>>> device-model =3D "" >>>>> 0 =3D "" >>>>> state =3D "running" >>>>> memory =3D "" >>>>> target =3D "1048576" >>>>> static-max =3D "4294967292" >>>>> freemem-slack =3D "314476" >>>>> libxl =3D "" >>>>> disable_udev =3D "1" >>>>> backend =3D "" >>>>> vbd =3D "" >>>>> 1 =3D "" >>>>> 2049 =3D "" >>>>> frontend =3D "/local/domain/1/device/vbd/2049" <<<< = >>>>> everything >>>>> seems to be enumerated >>>>> params =3D "/dev/loop0" >>>>> script =3D "/etc/xen/scripts/block" >>>>> physical-device =3D "7:0" >>>>> frontend-id =3D "1" >>>>> online =3D "1" >>>>> removable =3D "0" >>>>> bootable =3D "1" >>>>> state =3D "1" >>>>> dev =3D "sda1" >>>>> type =3D "phy" >>>>> mode =3D "w" >>>>> device-type =3D "disk" >>>>> 1 =3D "" >>>>> vm =3D "/vm/9b0dfb10-f69d-4e22-9158-bb70456ece2e" >>>>> name =3D "guest2" >>>>> cpu =3D "" >>>>> 0 =3D "" >>>>> availability =3D "online" >>>>> memory =3D "" >>>>> static-max =3D "512000" >>>>> target =3D "512001" >>>>> videoram =3D "-1" >>>>> device =3D "" >>>>> suspend =3D "" >>>>> event-channel =3D "" >>>>> vbd =3D "" >>>>> 2049 =3D "" >>>>> backend =3D "/local/domain/0/backend/vbd/1/2049" >>>>> backend-id =3D "0" >>>>> state =3D "1" <<<<< state changes to 5 and then after 5 = >>>>> secs it >>>>> times out >>>>> virtual-device =3D "2049" >>>>> device-type =3D "disk" >>>>> control =3D "" >>>>> shutdown =3D "" >>>>> platform-feature-multiprocessor-suspend =3D "1" >>>>> platform-feature-xs_reset_watches =3D "1" >>>>> data =3D "" >>>>> domid =3D "1" >>>>> store =3D "" >>>>> port =3D "1" >>>>> ring-ref =3D "156845" >>>>> vm =3D "" >>>>> 9b0dfb10-f69d-4e22-9158-bb70456ece2e =3D "" >>>>> uuid =3D "9b0dfb10-f69d-4e22-9158-bb70456ece2e" >>>>> name =3D "guest2" >>>>> image =3D "" >>>>> ostype =3D "linux" >>>>> kernel =3D "/boot/vmlinuz-3.8.0-rc5+" >>>>> ramdisk =3D "/boot/initrd.img-3.8.0-rc5+" >>>>> cmdline =3D "root=3D/dev/disk/by-path/xen-vbd-2049 ro xencons= =3Dtty" >>>>> start_time =3D "1359913591.67" >>>>> libxl =3D "" >>>>> 1 =3D "" >>>>> dm-version =3D "qemu_xen" >>>>> >>>>> Thanks, >>>>> Yathi > Sorry about top posting. I changed it to xvda1 and I still see the = > same behavior. > I instrumented the backend drivers and here's a trace of the events. I = observed that XS_DIRECTORY for "backend" ( as the "backend" node was not created in = xenstore yet) and "device" ( as the "device" node was not created in xenstore yet) = fails to return anything. Are they supposed to be in xenstore right after dom0 is created ? [ 3.011816] xen-balloon: Initialising balloon driver. [ 3.016043] xen/balloon: Xen selfballooning driver disabled for domain0. [ 3.420054] Switching to clocksource xen [ 3.510038] xen: registering gsi 13 triggering 1 polarity 0 [ 3.540022] xen: registering gsi 8 triggering 1 polarity 0 [ 3.566198] xen: registering gsi 4 triggering 1 polarity 0 [ 3.589252] xen: registering gsi 3 triggering 1 polarity 0 [ 4.096790] xen: registering gsi 16 triggering 0 polarity 1 [ 4.102431] xen: --> pirq=3D16 -> irq=3D16 (gsi=3D16) [ 4.107062] xen: registering gsi 16 triggering 0 polarity 1 [ 4.116460] xen: registering gsi 16 triggering 0 polarity 1 [ 4.125956] xen: registering gsi 16 triggering 0 polarity 1 [ 4.135307] xen: registering gsi 16 triggering 0 polarity 1 [ 4.144529] xen: registering gsi 16 triggering 0 polarity 1 [ 4.153912] xen: registering gsi 16 triggering 0 polarity 1 [ 4.163262] xen: registering gsi 16 triggering 0 polarity 1 [ 4.469657] xen: registering gsi 21 triggering 0 polarity 1 [ 4.475307] xen: --> pirq=3D21 -> irq=3D21 (gsi=3D21) [ 4.486553] xen: registering gsi 20 triggering 0 polarity 1 [ 4.492186] xen: --> pirq=3D20 -> irq=3D20 (gsi=3D20) [ 4.503457] xen: registering gsi 21 triggering 0 polarity 1 [ 4.519484] xen: registering gsi 20 triggering 0 polarity 1 [ 4.535518] xen: registering gsi 21 triggering 0 polarity 1 [ 5.733514] xenbus_register_frontend [ 5.788723] xenbus_register_frontend [ 5.796982] xen: registering gsi 23 triggering 0 polarity 1 [ 5.802619] xen: --> pirq=3D23 -> irq=3D23 (gsi=3D23) [ 6.019447] xenbus_register_frontend [ 6.029696] xen: registering gsi 21 triggering 0 polarity 1 [ 6.122280] xen: registering gsi 21 triggering 0 polarity 1 [ 6.214955] xen: registering gsi 20 triggering 0 polarity 1 [ 6.262081] xen: registering gsi 21 triggering 0 polarity 1 [ 6.309240] xen: registering gsi 20 triggering 0 polarity 1 [ 6.657173] xen: registering gsi 18 triggering 0 polarity 1 [ 6.657232] xen: registering gsi 16 triggering 0 polarity 1 [ 6.672277] xen: --> pirq=3D18 -> irq=3D18 (gsi=3D18) [ 6.761063] xen: registering gsi 16 triggering 0 polarity 1 [ 6.785518] xen: registering gsi 16 triggering 0 polarity 1 [ 7.015253] xen: registering gsi 19 triggering 0 polarity 1 [ 7.020861] xen: --> pirq=3D19 -> irq=3D19 (gsi=3D19) [ 7.339228] xen: registering gsi 16 triggering 0 polarity 1 [ 7.673945] xen: registering gsi 17 triggering 0 polarity 1 [ 7.679568] xen: --> pirq=3D17 -> irq=3D17 (gsi=3D17) [ 38.374483] xen: registering gsi 19 triggering 0 polarity 1 [ 44.712442] xenbr0: port 1(eth0) entered forwarding state [ 44.712449] xenbr0: port 1(eth0) entered forwarding state [ 48.572924] xen_blkif_xenbus_init: Register xen_blkbk_driver [ 48.572928] xenbus_register_backend [ 48.596414] xenbus_register_backend [ 48.619245] xen-pciback: backend is vpci [ 48.619251] xenbus_register_backend [ 48.776436] xenbus_scanf for node cpu/0 [ 48.782133] XENBUS xen store gave: unknown error cpu [ 48.782137] xenbus_scanf for node cpu/1 [ 48.782386] xenbus_scanf for node cpu/2 [ 48.782605] xenbus_scanf for node cpu/3 [ 48.782813] xenbus_scanf for node cpu/4 [ 48.783019] xenbus_scanf for node cpu/5 [ 48.783225] xenbus_scanf for node cpu/6 [ 48.783432] xenbus_scanf for node cpu/7 [ 48.783917] Failed to set shutdown watcher =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D [ 48.793731] backend_probe_and_watch [ 48.793733] xenbus_probe_devices started ... [ 48.793821] xenbus_directory: get dir "backend" contents [ 48.793825] xenbus_directory: ERROR getting dir = 8\xffffff92\xffffffb9\xfffffff7\x01\xffffff88\xffffffff\xffffffff\xffff ffd0\xffffff99\xffffff99\xffffffb9\xfffffff7\x01\xffffff88\xffffffff\xfffff= fffX\xffffff92\xffffffb9\xfffffff7\x01\xffffff8 8\xffffffff\xffffffff`\xffffff92\xffffffb9\xfffffff7\x01\xffffff88\xfffffff= f\xffffffff\xffffff98\xffffff90\xffffffb9\xffff fff7\x01\xffffff88\xffffffff\xffffffff\xffffffc8\xffffff99\xffffff99\xfffff= fb9\xfffffff7\x01\xffffff88\xffffffff\xffffffff \x01 contents [ 48.793827] xenbus_probe_devices: ERROR after xenbus_directory [ 48.793831] XENBUS xen store gave: unknown error control/shutdown [ 48.793831] XENBUS xen store gave: unknown error control/shutdown =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D [ 48.793833] frontend_probe_and_watch [ 48.793835] xenbus_probe_devices started ... [ 48.793837] xenbus_directory: get dir "device" contents [ 48.797288] xenbus_directory: ERROR getting dir = 8\xffffff92\xffffffb9\xfffffff7\x01\xffffff88\xffffffff\xffffffffOK cos [ 48.797290] xenbus_probe_devices: ERROR after xenbus_directory [ 48.797298] XENBUS xen store gave: unknown error backend [ 48.797299] Failed to set balloon watcher =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D [ 59.740081] xenbr0: port 1(eth0) entered forwarding state [ 63.739432] NFS: Registering the id_resolver key type [ 63.739455] Key type id_resolver registered [ 63.739457] Key type id_legacy registered [ 82.767858] init: ttyS0 main process (2257) terminated with status 1 [ 82.767909] init: ttyS0 main process ended, respawning Thanks, Yathi _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Sat Feb 09 12:08:52 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sat, 09 Feb 2013 12:08: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 1U49D9-0006dQ-EC; Sat, 09 Feb 2013 12:07:15 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U3yv1-0003Bz-O1 for xen-users@lists.xen.org; Sat, 09 Feb 2013 01:07:52 +0000 Received: from [85.158.139.83:43745] by server-8.bemta-5.messagelabs.com id 6D/96-19075-661A5115; Sat, 09 Feb 2013 01:07:50 +0000 X-Env-Sender: oleg.stepura@gmail.com X-Msg-Ref: server-4.tower-182.messagelabs.com!1360372068!26118157!1 X-Originating-IP: [209.85.214.179] 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.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 16967 invoked from network); 9 Feb 2013 01:07:49 -0000 Received: from mail-ob0-f179.google.com (HELO mail-ob0-f179.google.com) (209.85.214.179) by server-4.tower-182.messagelabs.com with RC4-SHA encrypted SMTP; 9 Feb 2013 01:07:49 -0000 Received: by mail-ob0-f179.google.com with SMTP id un3so4509753obb.38 for ; Fri, 08 Feb 2013 17:07:29 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:mime-version:sender:from:date:x-google-sender-auth :message-id:subject:to:content-type; bh=YZzYglYkZlbkpb87yDzbyXDUvpo5omik3ZHCRLjZ11Y=; b=QlDD/56mtqdCDH/ZsCeYlJlkMi7MnlJlYMgy26KYZQoqRDMfUnon7Fls32/HTVFWg7 tUKqN5d3DWgaGFivjsG+tKe2oPTEMA2XoOyCO0Hpy03DrmGVspb+0ys9YkIKsWmov4Gx om0dAA77RrYGVrkUwE5NbI61Lud51AebWhg8Hz1mkrXyQaELp6gAj3EJlTJOHNfGMthV 5/SHIejlBHGfbdv7YGyMwtGupxZHpycgpZj0jvHjgEoEXAaMqh3/lLayBi5uxy/Z+e9/ ZEcRkLdKxwcpuWxBLgAljbRsOWKXi6FNkaA8T4SGTE2e4GS0fZ68oYoxH2cZpWdl0B2/ zEYA== X-Received: by 10.60.32.134 with SMTP id j6mr5848825oei.15.1360372049266; Fri, 08 Feb 2013 17:07:29 -0800 (PST) MIME-Version: 1.0 Received: by 10.76.26.3 with HTTP; Fri, 8 Feb 2013 17:06:49 -0800 (PST) From: Oleg Stepura Date: Sat, 9 Feb 2013 04:06:49 +0300 X-Google-Sender-Auth: agf2W5xEq78LuXSHKhEkyJkbk1I Message-ID: To: xen-users@lists.xen.org X-Mailman-Approved-At: Sat, 09 Feb 2013 12:07:12 +0000 Subject: [Xen-users] Asrock X79 Extreme9 + Intel i7-3820 X-BeenThere: xen-users@lists.xen.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="===============3474663833297213215==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============3474663833297213215== Content-Type: multipart/alternative; boundary=e89a8fb1f07cc2481e04d5404c28 --e89a8fb1f07cc2481e04d5404c28 Content-Type: text/plain; charset=UTF-8 Hi! I decided to build a new virtualization PC instead of two regular PCs being used currently. The purpose is to create a XEN-based setup on Gentoo, planning to have Dom0 for Media-center (on XBMC) and domU with VGA-passthrough for Gaming. Searching through all possible options I found that the best chipset with huge data throughput currently is x79, and there are some motherboards with reported successful VGA passed through on this chipset as well as x79 is listed on Intel as supported for Vt-d ( http://www.intel.com/support/motherboards/desktop/sb/CS-030922.htm). The motherboard I stopped at is Asrock X79 Extreme9 ( http://www.asrock.com/mb/Intel/X79%20Extreme9/index.asp). This MB is cool since it has lots of SATA ports and several PCIex16 slots thus theoretically allowing multiple VMs to work with VGA passed through. Also it's good in terms of future upgrades since it supports up to 64Gb of RAM so maybe in future I will just buy extra memory if needed. And 4-channel memory should be faster that the regular 2-channel on Z77 chipsets. Since all the CPUs for LGA2011 are still too expensive the only one I can afford is Intel i7-3820 ( http://ark.intel.com/products/63698/Intel-Core-i7-3820-Processor-10M-Cache-up-to-3_80-GHz). Both the MB and CPU are advertised to support VT-d (the MB has Vt-d in BIOS according to manual). According to history here: http://wiki.xen.org/wiki/VTd_HowTo someone named Mans added on 4 dec 2012 Asrock X79 Extreme9 as a supported motherboard for VT-d. But I cannot find any success story for passing VGA through to DomU VMs with this motherboard. Since the whole amount of money spent for the new rig is big, I need your help. - Can anyone confirm that this motherboard (or better this MB with this CPU) work for VGA Passthrough with XEN? - Is this motherboard somewhat compatible with XEN in the sense that all required drivers are already in kernel? - Can anyone tell if this motherboard allows inserting PCIe x1 cards into it's lower PCIex16 slots (WIFI card and audio card in my case)? (Maybe any MB allows, just don't know) Thanks a lot! --e89a8fb1f07cc2481e04d5404c28 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Hi!

I decided to build a new virtualization PC instead o= f two regular PCs being used currently. The purpose is to create a XEN-base= d setup on Gentoo, planning to have Dom0 for Media-center (on XBMC) and dom= U with VGA-passthrough for Gaming.

Searching through all possible options I found that the= best chipset with huge data throughput currently is x79, and there are som= e motherboards with reported successful VGA passed through on this chipset = as well as x79 is listed on Intel as supported for Vt-d (http://www.intel.com/support/motherboards/desktop/sb/CS-030922.htm)= .

The motherboard I stopped at is Asrock X79 Extreme9 (http://www.asrock.com/mb/Intel/X79%20Extreme9/index.asp). This= MB is cool since it has lots of SATA ports and several PCIex16 slots thus = theoretically allowing multiple VMs to work with VGA passed through. Also i= t's good in terms of future upgrades since it supports up to 64Gb of RA= M so maybe in future I will just buy extra memory if needed. And 4-channel = memory should be faster that the regular 2-channel on Z77 chipsets.

Since all the CPUs for LGA2011 are still too expensive = the only one I can afford is Intel i7-3820=C2=A0(http://ark.intel.com/products/63698/Intel-Core-i7-3820-P= rocessor-10M-Cache-up-to-3_80-GHz). Both the MB and CPU are advertised = to support VT-d (the MB has Vt-d in BIOS according to manual).

According to history here:=C2=A0http://wiki.xen.org/wiki/VTd_HowTo= someone named Mans=C2=A0added=C2=A0on 4 dec 2012 Asrock X79 Extreme9 as a = supported motherboard for VT-d. But I cannot find any success story for pas= sing VGA through to DomU VMs with this motherboard. Since the whole amount = of money spent for the new rig is big, I need your help.

- Can anyone confirm that this motherboard (or better t= his MB with this CPU) work for VGA Passthrough with XEN?
- Is thi= s motherboard somewhat compatible with XEN in the sense that all required d= rivers are already in kernel?
- Can anyone tell if this motherboard allows inserting PCIe x1 cards i= nto it's lower PCIex16 slots (WIFI card and audio card in my case)? (Ma= ybe any MB allows, just don't know)

Thanks a lot!
--e89a8fb1f07cc2481e04d5404c28-- --===============3474663833297213215== 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 --===============3474663833297213215==-- From xen-users-bounces@lists.xen.org Sat Feb 09 12:08:52 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sat, 09 Feb 2013 12:08: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 1U49D8-0006dH-Qg; Sat, 09 Feb 2013 12:07:14 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U3xXY-0004WC-J6 for xen-users@lists.xen.org; Fri, 08 Feb 2013 23:39:33 +0000 Received: from [85.158.137.99:11037] by server-13.bemta-3.messagelabs.com id 24/D4-20653-3BC85115; Fri, 08 Feb 2013 23:39:31 +0000 X-Env-Sender: ydev@cs.utah.edu X-Msg-Ref: server-3.tower-217.messagelabs.com!1360366769!12237562!1 X-Originating-IP: [155.98.64.241] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 10961 invoked from network); 8 Feb 2013 23:39:29 -0000 Received: from rio.cs.utah.edu (HELO mail-svr1.cs.utah.edu) (155.98.64.241) by server-3.tower-217.messagelabs.com with SMTP; 8 Feb 2013 23:39:29 -0000 Received: from localhost (localhost [127.0.0.1]) by mail-svr1.cs.utah.edu (Postfix) with ESMTP id B94386500BC; Fri, 8 Feb 2013 16:39:28 -0700 (MST) X-Virus-Scanned: amavisd-new at cs.utah.edu Received: from mail-svr1.cs.utah.edu ([127.0.0.1]) by localhost (mail-svr1.cs.utah.edu [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gBNykLkDWJLT; Fri, 8 Feb 2013 16:39:27 -0700 (MST) Received: from [128.110.92.242] (128-110-92-242.uconnect.utah.edu [128.110.92.242]) by smtps.cs.utah.edu (Postfix) with ESMTPSA id 861E86500B7; Fri, 8 Feb 2013 16:39:27 -0700 (MST) Message-ID: <51158CAA.1060800@cs.utah.edu> Date: Fri, 08 Feb 2013 16:39:22 -0700 From: Yathindra User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130107 Thunderbird/17.0.2 MIME-Version: 1.0 To: "xen-users@lists.xen.org" References: <510DC655.5060205@cs.utah.edu> <510E3195.1010004@citrix.com> <510EA374.6060509@cs.utah.edu> <5110D7EC.8040608@citrix.com> <51113D59.7030003@cs.utah.edu> <51114B35.5050202@citrix.com> <5111C3B6.1070705@cs.utah.edu> <51158B1B.8090007@cs.utah.edu> In-Reply-To: <51158B1B.8090007@cs.utah.edu> X-Mailman-Approved-At: Sat, 09 Feb 2013 12:07:12 +0000 Cc: =?ISO-8859-1?Q?Roger_Pau_Monn=E9?= Subject: Re: [Xen-users] xen_blkbk times out before getting connected X-BeenThere: xen-users@lists.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 2/8/2013 4:32 PM, Yathindra wrote: > On 2/5/2013 7:45 PM, Yathindra wrote: >> On 2/5/2013 11:11 AM, Roger Pau Monn=E9 wrote: >>> On 05/02/13 18:11, Yathindra wrote: >>>> DomU configuration file looks like this: >>> Please don't do top posting. >>> >>>> kernel =3D "/boot/vmlinuz-3.8.0-rc5+" >>>> ramdisk =3D "/boot/initrd.img-3.8.0-rc5+" >>>> memory =3D 500 >>>> name =3D "guest2" >>>> disk =3D ['phy:/dev/loop0,sda1,w'] >>> Why are you using sda1 instead of xvda1? >>> >>>> root =3D "/dev/disk/by-path/xen-vbd-2049 ro" >>>> extra =3D 'xencons=3Dtty' >>> You can use: >>> >>> extra=3D"root=3D/dev/xvda1" >>> >>>> On 2/5/2013 2:59 AM, Roger Pau Monn=E9 wrote: >>>>> On 03/02/13 18:50, Yathindra wrote: >>>>>> I'm using the latest linux kernel 3.8.0 with Xen 4.3-unstable. = >>>>>> Xenstored >>>>>> is being started at boot time. >>>>>> I did not see any message (dmesg/syslog/console) about device being >>>>>> plugged in but xenstore-ls shows me all >>>>>> the entries backend and frontend. >>>>> Could you post your DomU configuration file also? >>>>> >>>>>> Here are some details >>>>>> ------------------------------ >>>>>> From /var/log/syslog: >>>>>> >>>>>> Feb 3 10:37:31 localhost kernel: [ 36.466359] Event-channel = >>>>>> device >>>>>> installed. >>>>>> Feb 3 10:37:31 localhost kernel: [ 36.636358] Register >>>>>> xen_blkbk_driver <<< custom debug message I added >>>>>> Feb 3 10:37:31 localhost kernel: [ 36.636367] >>>>>> xenbus_register_backend <<< custom debug message I added >>>>>> Feb 3 10:37:31 localhost kernel: [ 36.683533] = >>>>>> xenbus_register_backend >>>>>> Feb 3 10:37:31 localhost kernel: [ 36.830115] xen-pciback: = >>>>>> backend is >>>>>> vpci <<< custom debug message I added >>>>>> Feb 3 10:37:31 localhost kernel: [ 36.830123] >>>>>> xenbus_register_backend <<< custom debug message I added >>>>>> Feb 3 10:37:32 localhost xenstored: Checking store ... >>>>>> Feb 3 10:37:32 localhost xenstored: Checking store complete. >>>>>> Feb 3 10:37:32 localhost kernel: [ 37.075217] xenbus_probe: = >>>>>> xenstored >>>>>> is ready <<< custom debug message I added >>>>>> Feb 3 10:37:32 localhost kernel: [ 37.075230] watching node >>>>>> FFFFFFFF81C7D1A0 >>>>>> Feb 3 10:37:32 localhost kernel: [ 37.081309] xenbus_scanf for = >>>>>> node cpu/0 >>>>>> Feb 3 10:37:32 localhost kernel: [ 37.081327] XENBUS xen store = >>>>>> gave: >>>>>> unknown error cpu >>>>>> Feb 3 10:37:32 localhost kernel: [ 37.081333] xenbus_scanf for = >>>>>> node cpu/1 >>>>>> Feb 3 10:37:32 localhost kernel: [ 37.085327] XENBUS = >>>>>> unexpected type >>>>>> [17], expected [2] >>>>>> Feb 3 10:37:32 localhost kernel: [ 37.085342] watching node >>>>>> FFFFFFFF81C7D0C0 >>>>>> Feb 3 10:37:32 localhost kernel: [ 37.086857] XENBUS = >>>>>> unexpected type >>>>>> [17], expected [4] >>>>>> Feb 3 10:37:32 localhost kernel: [ 37.086865] Failed to set = >>>>>> shutdown >>>>>> watcher >>>>>> Feb 3 10:37:32 localhost kernel: [ 37.086880] = >>>>>> backend_probe_and_watch >>>>>> - enumerates devices in xenstore and watches for changes <<< custom >>>>>> debug message I added >>>>>> Feb 3 10:37:32 localhost kernel: [ 37.089401] XENBUS = >>>>>> unexpected type >>>>>> [4], expected [1] >>>>>> Feb 3 10:37:32 localhost kernel: [ 37.089411] watching node >>>>>> FFFFFFFF81C7D660 >>>>>> Feb 3 10:37:32 localhost kernel: [ 37.090715] XENBUS xen store = >>>>>> gave: >>>>>> unknown error control/shutdown >>>>>> Feb 3 10:37:32 localhost kernel: [ 37.090725] >>>>>> frontend_probe_and_watch: calling xenbus_probe_devices <<< custom = >>>>>> debug >>>>>> message I added >>>>>> Feb 3 10:37:32 localhost kernel: [ 37.092362] XENBUS = >>>>>> unexpected type >>>>>> [17], expected [1] >>>>>> Feb 3 10:37:32 localhost kernel: [ 37.092376] watching node >>>>>> FFFFFFFF81C7D820 >>>>>> Feb 3 10:37:32 localhost kernel: [ 37.093334] watching node >>>>>> FFFFFFFF81C7DB20 >>>>>> Feb 3 10:37:32 localhost kernel: [ 37.094454] XENBUS xen store = >>>>>> gave: >>>>>> unknown error backend <<< still not sure how critical this is >>>>>> Feb 3 10:37:32 localhost kernel: [ 37.094463] Failed to set = >>>>>> balloon >>>>>> watcher <<< still not sure how >>>>>> critical this is >>>>>> >>>>>> > xenstore-ls >>>>>> tool =3D "" >>>>>> xenstored =3D "" >>>>>> local =3D "" >>>>>> domain =3D "" >>>>>> 0 =3D "" >>>>>> data =3D "" >>>>>> meminfo_total =3D "930680" >>>>>> meminfo_free =3D "691868" >>>>>> os_name =3D "Ubuntu 12.04.1 LTS" >>>>>> os_majorver =3D "12" >>>>>> os_minorver =3D "04" >>>>>> os_uname =3D "3.8.0-rc5+" >>>>>> os_distro =3D "ubuntu" >>>>>> updated =3D "Sun Feb 3 10:43:32 MST 2013" >>>>>> name =3D "Domain-0" >>>>>> attr =3D "" >>>>>> xenbr0 =3D "" >>>>>> ip =3D "155.98.39.2" >>>>>> PVAddons =3D "" >>>>>> MajorVersion =3D "5" >>>>>> MinorVersion =3D "5" >>>>>> MicroVersion =3D "0" >>>>>> BuildVersion =3D "17913" >>>>>> Installed =3D "1" >>>>>> device-model =3D "" >>>>>> 0 =3D "" >>>>>> state =3D "running" >>>>>> >>>>>> After this I start the guest domain, here's the xenstore entries, >>>>>> >>>>>> nodea:~> sudo xenstore-ls >>>>>> tool =3D "" >>>>>> xenstored =3D "" >>>>>> local =3D "" >>>>>> domain =3D "" >>>>>> 0 =3D "" >>>>>> data =3D "" >>>>>> meminfo_total =3D "930680" >>>>>> meminfo_free =3D "695408" >>>>>> os_name =3D "Ubuntu 12.04.1 LTS" >>>>>> os_majorver =3D "12" >>>>>> os_minorver =3D "04" >>>>>> os_uname =3D "3.8.0-rc5+" >>>>>> os_distro =3D "ubuntu" >>>>>> updated =3D "Sun Feb 3 10:45:32 MST 2013" >>>>>> name =3D "Domain-0" >>>>>> attr =3D "" >>>>>> xenbr0 =3D "" >>>>>> ip =3D "155.98.39.2" >>>>>> PVAddons =3D "" >>>>>> MajorVersion =3D "5" >>>>>> MinorVersion =3D "5" >>>>>> MicroVersion =3D "0" >>>>>> BuildVersion =3D "17913" >>>>>> Installed =3D "1" >>>>>> device-model =3D "" >>>>>> 0 =3D "" >>>>>> state =3D "running" >>>>>> memory =3D "" >>>>>> target =3D "1048576" >>>>>> static-max =3D "4294967292" >>>>>> freemem-slack =3D "314476" >>>>>> libxl =3D "" >>>>>> disable_udev =3D "1" >>>>>> backend =3D "" >>>>>> vbd =3D "" >>>>>> 1 =3D "" >>>>>> 2049 =3D "" >>>>>> frontend =3D "/local/domain/1/device/vbd/2049" <<<< = >>>>>> everything >>>>>> seems to be enumerated >>>>>> params =3D "/dev/loop0" >>>>>> script =3D "/etc/xen/scripts/block" >>>>>> physical-device =3D "7:0" >>>>>> frontend-id =3D "1" >>>>>> online =3D "1" >>>>>> removable =3D "0" >>>>>> bootable =3D "1" >>>>>> state =3D "1" >>>>>> dev =3D "sda1" >>>>>> type =3D "phy" >>>>>> mode =3D "w" >>>>>> device-type =3D "disk" >>>>>> 1 =3D "" >>>>>> vm =3D "/vm/9b0dfb10-f69d-4e22-9158-bb70456ece2e" >>>>>> name =3D "guest2" >>>>>> cpu =3D "" >>>>>> 0 =3D "" >>>>>> availability =3D "online" >>>>>> memory =3D "" >>>>>> static-max =3D "512000" >>>>>> target =3D "512001" >>>>>> videoram =3D "-1" >>>>>> device =3D "" >>>>>> suspend =3D "" >>>>>> event-channel =3D "" >>>>>> vbd =3D "" >>>>>> 2049 =3D "" >>>>>> backend =3D "/local/domain/0/backend/vbd/1/2049" >>>>>> backend-id =3D "0" >>>>>> state =3D "1" <<<<< state changes to 5 and then after 5 = >>>>>> secs it >>>>>> times out >>>>>> virtual-device =3D "2049" >>>>>> device-type =3D "disk" >>>>>> control =3D "" >>>>>> shutdown =3D "" >>>>>> platform-feature-multiprocessor-suspend =3D "1" >>>>>> platform-feature-xs_reset_watches =3D "1" >>>>>> data =3D "" >>>>>> domid =3D "1" >>>>>> store =3D "" >>>>>> port =3D "1" >>>>>> ring-ref =3D "156845" >>>>>> vm =3D "" >>>>>> 9b0dfb10-f69d-4e22-9158-bb70456ece2e =3D "" >>>>>> uuid =3D "9b0dfb10-f69d-4e22-9158-bb70456ece2e" >>>>>> name =3D "guest2" >>>>>> image =3D "" >>>>>> ostype =3D "linux" >>>>>> kernel =3D "/boot/vmlinuz-3.8.0-rc5+" >>>>>> ramdisk =3D "/boot/initrd.img-3.8.0-rc5+" >>>>>> cmdline =3D "root=3D/dev/disk/by-path/xen-vbd-2049 ro xencons= =3Dtty" >>>>>> start_time =3D "1359913591.67" >>>>>> libxl =3D "" >>>>>> 1 =3D "" >>>>>> dm-version =3D "qemu_xen" >>>>>> >>>>>> Thanks, >>>>>> Yathi >> Sorry about top posting. I changed it to xvda1 and I still see the = >> same behavior. >> > > I instrumented the backend drivers and here's a trace of the events. I = > observed that > XS_DIRECTORY for "backend" ( as the "backend" node was not created in = > xenstore yet) > and "device" ( as the "device" node was not created in xenstore yet) = > fails to return anything. > Are they supposed to be in xenstore right after dom0 is created ? > > [ 3.011816] xen-balloon: Initialising balloon driver. > [ 3.016043] xen/balloon: Xen selfballooning driver disabled for = > domain0. > [ 3.420054] Switching to clocksource xen > [ 3.510038] xen: registering gsi 13 triggering 1 polarity 0 > [ 3.540022] xen: registering gsi 8 triggering 1 polarity 0 > [ 3.566198] xen: registering gsi 4 triggering 1 polarity 0 > [ 3.589252] xen: registering gsi 3 triggering 1 polarity 0 > [ 4.096790] xen: registering gsi 16 triggering 0 polarity 1 > [ 4.102431] xen: --> pirq=3D16 -> irq=3D16 (gsi=3D16) > [ 4.107062] xen: registering gsi 16 triggering 0 polarity 1 > [ 4.116460] xen: registering gsi 16 triggering 0 polarity 1 > [ 4.125956] xen: registering gsi 16 triggering 0 polarity 1 > [ 4.135307] xen: registering gsi 16 triggering 0 polarity 1 > [ 4.144529] xen: registering gsi 16 triggering 0 polarity 1 > [ 4.153912] xen: registering gsi 16 triggering 0 polarity 1 > [ 4.163262] xen: registering gsi 16 triggering 0 polarity 1 > [ 4.469657] xen: registering gsi 21 triggering 0 polarity 1 > [ 4.475307] xen: --> pirq=3D21 -> irq=3D21 (gsi=3D21) > [ 4.486553] xen: registering gsi 20 triggering 0 polarity 1 > [ 4.492186] xen: --> pirq=3D20 -> irq=3D20 (gsi=3D20) > [ 4.503457] xen: registering gsi 21 triggering 0 polarity 1 > [ 4.519484] xen: registering gsi 20 triggering 0 polarity 1 > [ 4.535518] xen: registering gsi 21 triggering 0 polarity 1 > [ 5.733514] xenbus_register_frontend > [ 5.788723] xenbus_register_frontend > [ 5.796982] xen: registering gsi 23 triggering 0 polarity 1 > [ 5.802619] xen: --> pirq=3D23 -> irq=3D23 (gsi=3D23) > [ 6.019447] xenbus_register_frontend > [ 6.029696] xen: registering gsi 21 triggering 0 polarity 1 > [ 6.122280] xen: registering gsi 21 triggering 0 polarity 1 > [ 6.214955] xen: registering gsi 20 triggering 0 polarity 1 > [ 6.262081] xen: registering gsi 21 triggering 0 polarity 1 > [ 6.309240] xen: registering gsi 20 triggering 0 polarity 1 > [ 6.657173] xen: registering gsi 18 triggering 0 polarity 1 > [ 6.657232] xen: registering gsi 16 triggering 0 polarity 1 > [ 6.672277] xen: --> pirq=3D18 -> irq=3D18 (gsi=3D18) > [ 6.761063] xen: registering gsi 16 triggering 0 polarity 1 > [ 6.785518] xen: registering gsi 16 triggering 0 polarity 1 > [ 7.015253] xen: registering gsi 19 triggering 0 polarity 1 > [ 7.020861] xen: --> pirq=3D19 -> irq=3D19 (gsi=3D19) > [ 7.339228] xen: registering gsi 16 triggering 0 polarity 1 > [ 7.673945] xen: registering gsi 17 triggering 0 polarity 1 > [ 7.679568] xen: --> pirq=3D17 -> irq=3D17 (gsi=3D17) > [ 38.374483] xen: registering gsi 19 triggering 0 polarity 1 > [ 44.712442] xenbr0: port 1(eth0) entered forwarding state > [ 44.712449] xenbr0: port 1(eth0) entered forwarding state > [ 48.572924] xen_blkif_xenbus_init: Register xen_blkbk_driver > [ 48.572928] xenbus_register_backend > [ 48.596414] xenbus_register_backend > [ 48.619245] xen-pciback: backend is vpci > [ 48.619251] xenbus_register_backend > [ 48.776436] xenbus_scanf for node cpu/0 > [ 48.782133] XENBUS xen store gave: unknown error cpu > [ 48.782137] xenbus_scanf for node cpu/1 > [ 48.782386] xenbus_scanf for node cpu/2 > [ 48.782605] xenbus_scanf for node cpu/3 > [ 48.782813] xenbus_scanf for node cpu/4 > [ 48.783019] xenbus_scanf for node cpu/5 > [ 48.783225] xenbus_scanf for node cpu/6 > [ 48.783432] xenbus_scanf for node cpu/7 > [ 48.783917] Failed to set shutdown watcher > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D = > > [ 48.793731] backend_probe_and_watch > [ 48.793733] xenbus_probe_devices started ... > [ 48.793821] xenbus_directory: get dir "backend" contents > [ 48.793825] xenbus_directory: ERROR getting dir = > 8\xffffff92\xffffffb9\xfffffff7\x01\xffffff88\xffffffff\xffffffff\xffff > ffd0\xffffff99\xffffff99\xffffffb9\xfffffff7\x01\xffffff88\xffffffff\xfff= fffffX\xffffff92\xffffffb9\xfffffff7\x01\xffffff8 = > > 8\xffffffff\xffffffff`\xffffff92\xffffffb9\xfffffff7\x01\xffffff88\xfffff= fff\xffffffff\xffffff98\xffffff90\xffffffb9\xffff = > > fff7\x01\xffffff88\xffffffff\xffffffff\xffffffc8\xffffff99\xffffff99\xfff= fffb9\xfffffff7\x01\xffffff88\xffffffff\xffffffff = > > \x01 contents > [ 48.793827] xenbus_probe_devices: ERROR after xenbus_directory > [ 48.793831] XENBUS xen store gave: unknown error control/shutdown > [ 48.793831] XENBUS xen store gave: unknown error control/shutdown > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D = > > [ 48.793833] frontend_probe_and_watch > [ 48.793835] xenbus_probe_devices started ... > [ 48.793837] xenbus_directory: get dir "device" contents > [ 48.797288] xenbus_directory: ERROR getting dir = > 8\xffffff92\xffffffb9\xfffffff7\x01\xffffff88\xffffffff\xffffffffOK cos > [ 48.797290] xenbus_probe_devices: ERROR after xenbus_directory > [ 48.797298] XENBUS xen store gave: unknown error backend > [ 48.797299] Failed to set balloon watcher > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D = > > [ 59.740081] xenbr0: port 1(eth0) entered forwarding state > [ 63.739432] NFS: Registering the id_resolver key type > [ 63.739455] Key type id_resolver registered > [ 63.739457] Key type id_legacy registered > [ 82.767858] init: ttyS0 main process (2257) terminated with status 1 > [ 82.767909] init: ttyS0 main process ended, respawning > > Thanks, > Yathi > > > The trace was right after dom0 was running. I did not create any guest = domain yet. Once I create the guest domain, I do not see any more messages from = backend/frontend. Is it because xenbus_probe_devices is called only once from = xenbus_probe_backend_init ? If thats the case, when guest starts xenbus_probe_devices is not called = to connect the disk ? Thanks, Yathi _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Sat Feb 09 12:08:52 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sat, 09 Feb 2013 12:08: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 1U49D8-0006dH-Qg; Sat, 09 Feb 2013 12:07:14 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U3xXY-0004WC-J6 for xen-users@lists.xen.org; Fri, 08 Feb 2013 23:39:33 +0000 Received: from [85.158.137.99:11037] by server-13.bemta-3.messagelabs.com id 24/D4-20653-3BC85115; Fri, 08 Feb 2013 23:39:31 +0000 X-Env-Sender: ydev@cs.utah.edu X-Msg-Ref: server-3.tower-217.messagelabs.com!1360366769!12237562!1 X-Originating-IP: [155.98.64.241] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 10961 invoked from network); 8 Feb 2013 23:39:29 -0000 Received: from rio.cs.utah.edu (HELO mail-svr1.cs.utah.edu) (155.98.64.241) by server-3.tower-217.messagelabs.com with SMTP; 8 Feb 2013 23:39:29 -0000 Received: from localhost (localhost [127.0.0.1]) by mail-svr1.cs.utah.edu (Postfix) with ESMTP id B94386500BC; Fri, 8 Feb 2013 16:39:28 -0700 (MST) X-Virus-Scanned: amavisd-new at cs.utah.edu Received: from mail-svr1.cs.utah.edu ([127.0.0.1]) by localhost (mail-svr1.cs.utah.edu [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gBNykLkDWJLT; Fri, 8 Feb 2013 16:39:27 -0700 (MST) Received: from [128.110.92.242] (128-110-92-242.uconnect.utah.edu [128.110.92.242]) by smtps.cs.utah.edu (Postfix) with ESMTPSA id 861E86500B7; Fri, 8 Feb 2013 16:39:27 -0700 (MST) Message-ID: <51158CAA.1060800@cs.utah.edu> Date: Fri, 08 Feb 2013 16:39:22 -0700 From: Yathindra User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130107 Thunderbird/17.0.2 MIME-Version: 1.0 To: "xen-users@lists.xen.org" References: <510DC655.5060205@cs.utah.edu> <510E3195.1010004@citrix.com> <510EA374.6060509@cs.utah.edu> <5110D7EC.8040608@citrix.com> <51113D59.7030003@cs.utah.edu> <51114B35.5050202@citrix.com> <5111C3B6.1070705@cs.utah.edu> <51158B1B.8090007@cs.utah.edu> In-Reply-To: <51158B1B.8090007@cs.utah.edu> X-Mailman-Approved-At: Sat, 09 Feb 2013 12:07:12 +0000 Cc: =?ISO-8859-1?Q?Roger_Pau_Monn=E9?= Subject: Re: [Xen-users] xen_blkbk times out before getting connected X-BeenThere: xen-users@lists.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 2/8/2013 4:32 PM, Yathindra wrote: > On 2/5/2013 7:45 PM, Yathindra wrote: >> On 2/5/2013 11:11 AM, Roger Pau Monn=E9 wrote: >>> On 05/02/13 18:11, Yathindra wrote: >>>> DomU configuration file looks like this: >>> Please don't do top posting. >>> >>>> kernel =3D "/boot/vmlinuz-3.8.0-rc5+" >>>> ramdisk =3D "/boot/initrd.img-3.8.0-rc5+" >>>> memory =3D 500 >>>> name =3D "guest2" >>>> disk =3D ['phy:/dev/loop0,sda1,w'] >>> Why are you using sda1 instead of xvda1? >>> >>>> root =3D "/dev/disk/by-path/xen-vbd-2049 ro" >>>> extra =3D 'xencons=3Dtty' >>> You can use: >>> >>> extra=3D"root=3D/dev/xvda1" >>> >>>> On 2/5/2013 2:59 AM, Roger Pau Monn=E9 wrote: >>>>> On 03/02/13 18:50, Yathindra wrote: >>>>>> I'm using the latest linux kernel 3.8.0 with Xen 4.3-unstable. = >>>>>> Xenstored >>>>>> is being started at boot time. >>>>>> I did not see any message (dmesg/syslog/console) about device being >>>>>> plugged in but xenstore-ls shows me all >>>>>> the entries backend and frontend. >>>>> Could you post your DomU configuration file also? >>>>> >>>>>> Here are some details >>>>>> ------------------------------ >>>>>> From /var/log/syslog: >>>>>> >>>>>> Feb 3 10:37:31 localhost kernel: [ 36.466359] Event-channel = >>>>>> device >>>>>> installed. >>>>>> Feb 3 10:37:31 localhost kernel: [ 36.636358] Register >>>>>> xen_blkbk_driver <<< custom debug message I added >>>>>> Feb 3 10:37:31 localhost kernel: [ 36.636367] >>>>>> xenbus_register_backend <<< custom debug message I added >>>>>> Feb 3 10:37:31 localhost kernel: [ 36.683533] = >>>>>> xenbus_register_backend >>>>>> Feb 3 10:37:31 localhost kernel: [ 36.830115] xen-pciback: = >>>>>> backend is >>>>>> vpci <<< custom debug message I added >>>>>> Feb 3 10:37:31 localhost kernel: [ 36.830123] >>>>>> xenbus_register_backend <<< custom debug message I added >>>>>> Feb 3 10:37:32 localhost xenstored: Checking store ... >>>>>> Feb 3 10:37:32 localhost xenstored: Checking store complete. >>>>>> Feb 3 10:37:32 localhost kernel: [ 37.075217] xenbus_probe: = >>>>>> xenstored >>>>>> is ready <<< custom debug message I added >>>>>> Feb 3 10:37:32 localhost kernel: [ 37.075230] watching node >>>>>> FFFFFFFF81C7D1A0 >>>>>> Feb 3 10:37:32 localhost kernel: [ 37.081309] xenbus_scanf for = >>>>>> node cpu/0 >>>>>> Feb 3 10:37:32 localhost kernel: [ 37.081327] XENBUS xen store = >>>>>> gave: >>>>>> unknown error cpu >>>>>> Feb 3 10:37:32 localhost kernel: [ 37.081333] xenbus_scanf for = >>>>>> node cpu/1 >>>>>> Feb 3 10:37:32 localhost kernel: [ 37.085327] XENBUS = >>>>>> unexpected type >>>>>> [17], expected [2] >>>>>> Feb 3 10:37:32 localhost kernel: [ 37.085342] watching node >>>>>> FFFFFFFF81C7D0C0 >>>>>> Feb 3 10:37:32 localhost kernel: [ 37.086857] XENBUS = >>>>>> unexpected type >>>>>> [17], expected [4] >>>>>> Feb 3 10:37:32 localhost kernel: [ 37.086865] Failed to set = >>>>>> shutdown >>>>>> watcher >>>>>> Feb 3 10:37:32 localhost kernel: [ 37.086880] = >>>>>> backend_probe_and_watch >>>>>> - enumerates devices in xenstore and watches for changes <<< custom >>>>>> debug message I added >>>>>> Feb 3 10:37:32 localhost kernel: [ 37.089401] XENBUS = >>>>>> unexpected type >>>>>> [4], expected [1] >>>>>> Feb 3 10:37:32 localhost kernel: [ 37.089411] watching node >>>>>> FFFFFFFF81C7D660 >>>>>> Feb 3 10:37:32 localhost kernel: [ 37.090715] XENBUS xen store = >>>>>> gave: >>>>>> unknown error control/shutdown >>>>>> Feb 3 10:37:32 localhost kernel: [ 37.090725] >>>>>> frontend_probe_and_watch: calling xenbus_probe_devices <<< custom = >>>>>> debug >>>>>> message I added >>>>>> Feb 3 10:37:32 localhost kernel: [ 37.092362] XENBUS = >>>>>> unexpected type >>>>>> [17], expected [1] >>>>>> Feb 3 10:37:32 localhost kernel: [ 37.092376] watching node >>>>>> FFFFFFFF81C7D820 >>>>>> Feb 3 10:37:32 localhost kernel: [ 37.093334] watching node >>>>>> FFFFFFFF81C7DB20 >>>>>> Feb 3 10:37:32 localhost kernel: [ 37.094454] XENBUS xen store = >>>>>> gave: >>>>>> unknown error backend <<< still not sure how critical this is >>>>>> Feb 3 10:37:32 localhost kernel: [ 37.094463] Failed to set = >>>>>> balloon >>>>>> watcher <<< still not sure how >>>>>> critical this is >>>>>> >>>>>> > xenstore-ls >>>>>> tool =3D "" >>>>>> xenstored =3D "" >>>>>> local =3D "" >>>>>> domain =3D "" >>>>>> 0 =3D "" >>>>>> data =3D "" >>>>>> meminfo_total =3D "930680" >>>>>> meminfo_free =3D "691868" >>>>>> os_name =3D "Ubuntu 12.04.1 LTS" >>>>>> os_majorver =3D "12" >>>>>> os_minorver =3D "04" >>>>>> os_uname =3D "3.8.0-rc5+" >>>>>> os_distro =3D "ubuntu" >>>>>> updated =3D "Sun Feb 3 10:43:32 MST 2013" >>>>>> name =3D "Domain-0" >>>>>> attr =3D "" >>>>>> xenbr0 =3D "" >>>>>> ip =3D "155.98.39.2" >>>>>> PVAddons =3D "" >>>>>> MajorVersion =3D "5" >>>>>> MinorVersion =3D "5" >>>>>> MicroVersion =3D "0" >>>>>> BuildVersion =3D "17913" >>>>>> Installed =3D "1" >>>>>> device-model =3D "" >>>>>> 0 =3D "" >>>>>> state =3D "running" >>>>>> >>>>>> After this I start the guest domain, here's the xenstore entries, >>>>>> >>>>>> nodea:~> sudo xenstore-ls >>>>>> tool =3D "" >>>>>> xenstored =3D "" >>>>>> local =3D "" >>>>>> domain =3D "" >>>>>> 0 =3D "" >>>>>> data =3D "" >>>>>> meminfo_total =3D "930680" >>>>>> meminfo_free =3D "695408" >>>>>> os_name =3D "Ubuntu 12.04.1 LTS" >>>>>> os_majorver =3D "12" >>>>>> os_minorver =3D "04" >>>>>> os_uname =3D "3.8.0-rc5+" >>>>>> os_distro =3D "ubuntu" >>>>>> updated =3D "Sun Feb 3 10:45:32 MST 2013" >>>>>> name =3D "Domain-0" >>>>>> attr =3D "" >>>>>> xenbr0 =3D "" >>>>>> ip =3D "155.98.39.2" >>>>>> PVAddons =3D "" >>>>>> MajorVersion =3D "5" >>>>>> MinorVersion =3D "5" >>>>>> MicroVersion =3D "0" >>>>>> BuildVersion =3D "17913" >>>>>> Installed =3D "1" >>>>>> device-model =3D "" >>>>>> 0 =3D "" >>>>>> state =3D "running" >>>>>> memory =3D "" >>>>>> target =3D "1048576" >>>>>> static-max =3D "4294967292" >>>>>> freemem-slack =3D "314476" >>>>>> libxl =3D "" >>>>>> disable_udev =3D "1" >>>>>> backend =3D "" >>>>>> vbd =3D "" >>>>>> 1 =3D "" >>>>>> 2049 =3D "" >>>>>> frontend =3D "/local/domain/1/device/vbd/2049" <<<< = >>>>>> everything >>>>>> seems to be enumerated >>>>>> params =3D "/dev/loop0" >>>>>> script =3D "/etc/xen/scripts/block" >>>>>> physical-device =3D "7:0" >>>>>> frontend-id =3D "1" >>>>>> online =3D "1" >>>>>> removable =3D "0" >>>>>> bootable =3D "1" >>>>>> state =3D "1" >>>>>> dev =3D "sda1" >>>>>> type =3D "phy" >>>>>> mode =3D "w" >>>>>> device-type =3D "disk" >>>>>> 1 =3D "" >>>>>> vm =3D "/vm/9b0dfb10-f69d-4e22-9158-bb70456ece2e" >>>>>> name =3D "guest2" >>>>>> cpu =3D "" >>>>>> 0 =3D "" >>>>>> availability =3D "online" >>>>>> memory =3D "" >>>>>> static-max =3D "512000" >>>>>> target =3D "512001" >>>>>> videoram =3D "-1" >>>>>> device =3D "" >>>>>> suspend =3D "" >>>>>> event-channel =3D "" >>>>>> vbd =3D "" >>>>>> 2049 =3D "" >>>>>> backend =3D "/local/domain/0/backend/vbd/1/2049" >>>>>> backend-id =3D "0" >>>>>> state =3D "1" <<<<< state changes to 5 and then after 5 = >>>>>> secs it >>>>>> times out >>>>>> virtual-device =3D "2049" >>>>>> device-type =3D "disk" >>>>>> control =3D "" >>>>>> shutdown =3D "" >>>>>> platform-feature-multiprocessor-suspend =3D "1" >>>>>> platform-feature-xs_reset_watches =3D "1" >>>>>> data =3D "" >>>>>> domid =3D "1" >>>>>> store =3D "" >>>>>> port =3D "1" >>>>>> ring-ref =3D "156845" >>>>>> vm =3D "" >>>>>> 9b0dfb10-f69d-4e22-9158-bb70456ece2e =3D "" >>>>>> uuid =3D "9b0dfb10-f69d-4e22-9158-bb70456ece2e" >>>>>> name =3D "guest2" >>>>>> image =3D "" >>>>>> ostype =3D "linux" >>>>>> kernel =3D "/boot/vmlinuz-3.8.0-rc5+" >>>>>> ramdisk =3D "/boot/initrd.img-3.8.0-rc5+" >>>>>> cmdline =3D "root=3D/dev/disk/by-path/xen-vbd-2049 ro xencons= =3Dtty" >>>>>> start_time =3D "1359913591.67" >>>>>> libxl =3D "" >>>>>> 1 =3D "" >>>>>> dm-version =3D "qemu_xen" >>>>>> >>>>>> Thanks, >>>>>> Yathi >> Sorry about top posting. I changed it to xvda1 and I still see the = >> same behavior. >> > > I instrumented the backend drivers and here's a trace of the events. I = > observed that > XS_DIRECTORY for "backend" ( as the "backend" node was not created in = > xenstore yet) > and "device" ( as the "device" node was not created in xenstore yet) = > fails to return anything. > Are they supposed to be in xenstore right after dom0 is created ? > > [ 3.011816] xen-balloon: Initialising balloon driver. > [ 3.016043] xen/balloon: Xen selfballooning driver disabled for = > domain0. > [ 3.420054] Switching to clocksource xen > [ 3.510038] xen: registering gsi 13 triggering 1 polarity 0 > [ 3.540022] xen: registering gsi 8 triggering 1 polarity 0 > [ 3.566198] xen: registering gsi 4 triggering 1 polarity 0 > [ 3.589252] xen: registering gsi 3 triggering 1 polarity 0 > [ 4.096790] xen: registering gsi 16 triggering 0 polarity 1 > [ 4.102431] xen: --> pirq=3D16 -> irq=3D16 (gsi=3D16) > [ 4.107062] xen: registering gsi 16 triggering 0 polarity 1 > [ 4.116460] xen: registering gsi 16 triggering 0 polarity 1 > [ 4.125956] xen: registering gsi 16 triggering 0 polarity 1 > [ 4.135307] xen: registering gsi 16 triggering 0 polarity 1 > [ 4.144529] xen: registering gsi 16 triggering 0 polarity 1 > [ 4.153912] xen: registering gsi 16 triggering 0 polarity 1 > [ 4.163262] xen: registering gsi 16 triggering 0 polarity 1 > [ 4.469657] xen: registering gsi 21 triggering 0 polarity 1 > [ 4.475307] xen: --> pirq=3D21 -> irq=3D21 (gsi=3D21) > [ 4.486553] xen: registering gsi 20 triggering 0 polarity 1 > [ 4.492186] xen: --> pirq=3D20 -> irq=3D20 (gsi=3D20) > [ 4.503457] xen: registering gsi 21 triggering 0 polarity 1 > [ 4.519484] xen: registering gsi 20 triggering 0 polarity 1 > [ 4.535518] xen: registering gsi 21 triggering 0 polarity 1 > [ 5.733514] xenbus_register_frontend > [ 5.788723] xenbus_register_frontend > [ 5.796982] xen: registering gsi 23 triggering 0 polarity 1 > [ 5.802619] xen: --> pirq=3D23 -> irq=3D23 (gsi=3D23) > [ 6.019447] xenbus_register_frontend > [ 6.029696] xen: registering gsi 21 triggering 0 polarity 1 > [ 6.122280] xen: registering gsi 21 triggering 0 polarity 1 > [ 6.214955] xen: registering gsi 20 triggering 0 polarity 1 > [ 6.262081] xen: registering gsi 21 triggering 0 polarity 1 > [ 6.309240] xen: registering gsi 20 triggering 0 polarity 1 > [ 6.657173] xen: registering gsi 18 triggering 0 polarity 1 > [ 6.657232] xen: registering gsi 16 triggering 0 polarity 1 > [ 6.672277] xen: --> pirq=3D18 -> irq=3D18 (gsi=3D18) > [ 6.761063] xen: registering gsi 16 triggering 0 polarity 1 > [ 6.785518] xen: registering gsi 16 triggering 0 polarity 1 > [ 7.015253] xen: registering gsi 19 triggering 0 polarity 1 > [ 7.020861] xen: --> pirq=3D19 -> irq=3D19 (gsi=3D19) > [ 7.339228] xen: registering gsi 16 triggering 0 polarity 1 > [ 7.673945] xen: registering gsi 17 triggering 0 polarity 1 > [ 7.679568] xen: --> pirq=3D17 -> irq=3D17 (gsi=3D17) > [ 38.374483] xen: registering gsi 19 triggering 0 polarity 1 > [ 44.712442] xenbr0: port 1(eth0) entered forwarding state > [ 44.712449] xenbr0: port 1(eth0) entered forwarding state > [ 48.572924] xen_blkif_xenbus_init: Register xen_blkbk_driver > [ 48.572928] xenbus_register_backend > [ 48.596414] xenbus_register_backend > [ 48.619245] xen-pciback: backend is vpci > [ 48.619251] xenbus_register_backend > [ 48.776436] xenbus_scanf for node cpu/0 > [ 48.782133] XENBUS xen store gave: unknown error cpu > [ 48.782137] xenbus_scanf for node cpu/1 > [ 48.782386] xenbus_scanf for node cpu/2 > [ 48.782605] xenbus_scanf for node cpu/3 > [ 48.782813] xenbus_scanf for node cpu/4 > [ 48.783019] xenbus_scanf for node cpu/5 > [ 48.783225] xenbus_scanf for node cpu/6 > [ 48.783432] xenbus_scanf for node cpu/7 > [ 48.783917] Failed to set shutdown watcher > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D = > > [ 48.793731] backend_probe_and_watch > [ 48.793733] xenbus_probe_devices started ... > [ 48.793821] xenbus_directory: get dir "backend" contents > [ 48.793825] xenbus_directory: ERROR getting dir = > 8\xffffff92\xffffffb9\xfffffff7\x01\xffffff88\xffffffff\xffffffff\xffff > ffd0\xffffff99\xffffff99\xffffffb9\xfffffff7\x01\xffffff88\xffffffff\xfff= fffffX\xffffff92\xffffffb9\xfffffff7\x01\xffffff8 = > > 8\xffffffff\xffffffff`\xffffff92\xffffffb9\xfffffff7\x01\xffffff88\xfffff= fff\xffffffff\xffffff98\xffffff90\xffffffb9\xffff = > > fff7\x01\xffffff88\xffffffff\xffffffff\xffffffc8\xffffff99\xffffff99\xfff= fffb9\xfffffff7\x01\xffffff88\xffffffff\xffffffff = > > \x01 contents > [ 48.793827] xenbus_probe_devices: ERROR after xenbus_directory > [ 48.793831] XENBUS xen store gave: unknown error control/shutdown > [ 48.793831] XENBUS xen store gave: unknown error control/shutdown > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D = > > [ 48.793833] frontend_probe_and_watch > [ 48.793835] xenbus_probe_devices started ... > [ 48.793837] xenbus_directory: get dir "device" contents > [ 48.797288] xenbus_directory: ERROR getting dir = > 8\xffffff92\xffffffb9\xfffffff7\x01\xffffff88\xffffffff\xffffffffOK cos > [ 48.797290] xenbus_probe_devices: ERROR after xenbus_directory > [ 48.797298] XENBUS xen store gave: unknown error backend > [ 48.797299] Failed to set balloon watcher > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D = > > [ 59.740081] xenbr0: port 1(eth0) entered forwarding state > [ 63.739432] NFS: Registering the id_resolver key type > [ 63.739455] Key type id_resolver registered > [ 63.739457] Key type id_legacy registered > [ 82.767858] init: ttyS0 main process (2257) terminated with status 1 > [ 82.767909] init: ttyS0 main process ended, respawning > > Thanks, > Yathi > > > The trace was right after dom0 was running. I did not create any guest = domain yet. Once I create the guest domain, I do not see any more messages from = backend/frontend. Is it because xenbus_probe_devices is called only once from = xenbus_probe_backend_init ? If thats the case, when guest starts xenbus_probe_devices is not called = to connect the disk ? Thanks, Yathi _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Sat Feb 09 12:08:52 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sat, 09 Feb 2013 12:08: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 1U49D8-0006d8-51; Sat, 09 Feb 2013 12:07:14 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U3xRF-0004VK-E6 for xen-users@lists.xen.org; Fri, 08 Feb 2013 23:33:01 +0000 Received: from [85.158.143.35:60650] by server-3.bemta-4.messagelabs.com id 3B/51-08920-C2B85115; Fri, 08 Feb 2013 23:33:00 +0000 X-Env-Sender: ydev@cs.utah.edu X-Msg-Ref: server-2.tower-21.messagelabs.com!1360366378!4767831!1 X-Originating-IP: [155.98.64.241] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 26801 invoked from network); 8 Feb 2013 23:32:58 -0000 Received: from rio.cs.utah.edu (HELO mail-svr1.cs.utah.edu) (155.98.64.241) by server-2.tower-21.messagelabs.com with SMTP; 8 Feb 2013 23:32:58 -0000 Received: from localhost (localhost [127.0.0.1]) by mail-svr1.cs.utah.edu (Postfix) with ESMTP id A01A76500BC; Fri, 8 Feb 2013 16:32:57 -0700 (MST) X-Virus-Scanned: amavisd-new at cs.utah.edu Received: from mail-svr1.cs.utah.edu ([127.0.0.1]) by localhost (mail-svr1.cs.utah.edu [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3ORu-1S9cuGN; Fri, 8 Feb 2013 16:32:48 -0700 (MST) Received: from [128.110.92.242] (128-110-92-242.uconnect.utah.edu [128.110.92.242]) by smtps.cs.utah.edu (Postfix) with ESMTPSA id 35F446500B7; Fri, 8 Feb 2013 16:32:48 -0700 (MST) Message-ID: <51158B1B.8090007@cs.utah.edu> Date: Fri, 08 Feb 2013 16:32:43 -0700 From: Yathindra User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130107 Thunderbird/17.0.2 MIME-Version: 1.0 To: "xen-users@lists.xen.org" References: <510DC655.5060205@cs.utah.edu> <510E3195.1010004@citrix.com> <510EA374.6060509@cs.utah.edu> <5110D7EC.8040608@citrix.com> <51113D59.7030003@cs.utah.edu> <51114B35.5050202@citrix.com> <5111C3B6.1070705@cs.utah.edu> In-Reply-To: <5111C3B6.1070705@cs.utah.edu> X-Mailman-Approved-At: Sat, 09 Feb 2013 12:07:12 +0000 Cc: =?ISO-8859-1?Q?Roger_Pau_Monn=E9?= Subject: Re: [Xen-users] xen_blkbk times out before getting connected X-BeenThere: xen-users@lists.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 2/5/2013 7:45 PM, Yathindra wrote: > On 2/5/2013 11:11 AM, Roger Pau Monn=E9 wrote: >> On 05/02/13 18:11, Yathindra wrote: >>> DomU configuration file looks like this: >> Please don't do top posting. >> >>> kernel =3D "/boot/vmlinuz-3.8.0-rc5+" >>> ramdisk =3D "/boot/initrd.img-3.8.0-rc5+" >>> memory =3D 500 >>> name =3D "guest2" >>> disk =3D ['phy:/dev/loop0,sda1,w'] >> Why are you using sda1 instead of xvda1? >> >>> root =3D "/dev/disk/by-path/xen-vbd-2049 ro" >>> extra =3D 'xencons=3Dtty' >> You can use: >> >> extra=3D"root=3D/dev/xvda1" >> >>> On 2/5/2013 2:59 AM, Roger Pau Monn=E9 wrote: >>>> On 03/02/13 18:50, Yathindra wrote: >>>>> I'm using the latest linux kernel 3.8.0 with Xen 4.3-unstable. = >>>>> Xenstored >>>>> is being started at boot time. >>>>> I did not see any message (dmesg/syslog/console) about device being >>>>> plugged in but xenstore-ls shows me all >>>>> the entries backend and frontend. >>>> Could you post your DomU configuration file also? >>>> >>>>> Here are some details >>>>> ------------------------------ >>>>> From /var/log/syslog: >>>>> >>>>> Feb 3 10:37:31 localhost kernel: [ 36.466359] Event-channel device >>>>> installed. >>>>> Feb 3 10:37:31 localhost kernel: [ 36.636358] Register >>>>> xen_blkbk_driver <<< custom debug message I added >>>>> Feb 3 10:37:31 localhost kernel: [ 36.636367] >>>>> xenbus_register_backend <<< custom debug message I added >>>>> Feb 3 10:37:31 localhost kernel: [ 36.683533] = >>>>> xenbus_register_backend >>>>> Feb 3 10:37:31 localhost kernel: [ 36.830115] xen-pciback: = >>>>> backend is >>>>> vpci <<< custom debug message I added >>>>> Feb 3 10:37:31 localhost kernel: [ 36.830123] >>>>> xenbus_register_backend <<< custom debug message I added >>>>> Feb 3 10:37:32 localhost xenstored: Checking store ... >>>>> Feb 3 10:37:32 localhost xenstored: Checking store complete. >>>>> Feb 3 10:37:32 localhost kernel: [ 37.075217] xenbus_probe: = >>>>> xenstored >>>>> is ready <<< custom debug message I added >>>>> Feb 3 10:37:32 localhost kernel: [ 37.075230] watching node >>>>> FFFFFFFF81C7D1A0 >>>>> Feb 3 10:37:32 localhost kernel: [ 37.081309] xenbus_scanf for = >>>>> node cpu/0 >>>>> Feb 3 10:37:32 localhost kernel: [ 37.081327] XENBUS xen store = >>>>> gave: >>>>> unknown error cpu >>>>> Feb 3 10:37:32 localhost kernel: [ 37.081333] xenbus_scanf for = >>>>> node cpu/1 >>>>> Feb 3 10:37:32 localhost kernel: [ 37.085327] XENBUS unexpected = >>>>> type >>>>> [17], expected [2] >>>>> Feb 3 10:37:32 localhost kernel: [ 37.085342] watching node >>>>> FFFFFFFF81C7D0C0 >>>>> Feb 3 10:37:32 localhost kernel: [ 37.086857] XENBUS unexpected = >>>>> type >>>>> [17], expected [4] >>>>> Feb 3 10:37:32 localhost kernel: [ 37.086865] Failed to set = >>>>> shutdown >>>>> watcher >>>>> Feb 3 10:37:32 localhost kernel: [ 37.086880] = >>>>> backend_probe_and_watch >>>>> - enumerates devices in xenstore and watches for changes <<< custom >>>>> debug message I added >>>>> Feb 3 10:37:32 localhost kernel: [ 37.089401] XENBUS unexpected = >>>>> type >>>>> [4], expected [1] >>>>> Feb 3 10:37:32 localhost kernel: [ 37.089411] watching node >>>>> FFFFFFFF81C7D660 >>>>> Feb 3 10:37:32 localhost kernel: [ 37.090715] XENBUS xen store = >>>>> gave: >>>>> unknown error control/shutdown >>>>> Feb 3 10:37:32 localhost kernel: [ 37.090725] >>>>> frontend_probe_and_watch: calling xenbus_probe_devices <<< custom = >>>>> debug >>>>> message I added >>>>> Feb 3 10:37:32 localhost kernel: [ 37.092362] XENBUS unexpected = >>>>> type >>>>> [17], expected [1] >>>>> Feb 3 10:37:32 localhost kernel: [ 37.092376] watching node >>>>> FFFFFFFF81C7D820 >>>>> Feb 3 10:37:32 localhost kernel: [ 37.093334] watching node >>>>> FFFFFFFF81C7DB20 >>>>> Feb 3 10:37:32 localhost kernel: [ 37.094454] XENBUS xen store = >>>>> gave: >>>>> unknown error backend <<< still not sure how critical this is >>>>> Feb 3 10:37:32 localhost kernel: [ 37.094463] Failed to set = >>>>> balloon >>>>> watcher <<< still not sure how >>>>> critical this is >>>>> >>>>> > xenstore-ls >>>>> tool =3D "" >>>>> xenstored =3D "" >>>>> local =3D "" >>>>> domain =3D "" >>>>> 0 =3D "" >>>>> data =3D "" >>>>> meminfo_total =3D "930680" >>>>> meminfo_free =3D "691868" >>>>> os_name =3D "Ubuntu 12.04.1 LTS" >>>>> os_majorver =3D "12" >>>>> os_minorver =3D "04" >>>>> os_uname =3D "3.8.0-rc5+" >>>>> os_distro =3D "ubuntu" >>>>> updated =3D "Sun Feb 3 10:43:32 MST 2013" >>>>> name =3D "Domain-0" >>>>> attr =3D "" >>>>> xenbr0 =3D "" >>>>> ip =3D "155.98.39.2" >>>>> PVAddons =3D "" >>>>> MajorVersion =3D "5" >>>>> MinorVersion =3D "5" >>>>> MicroVersion =3D "0" >>>>> BuildVersion =3D "17913" >>>>> Installed =3D "1" >>>>> device-model =3D "" >>>>> 0 =3D "" >>>>> state =3D "running" >>>>> >>>>> After this I start the guest domain, here's the xenstore entries, >>>>> >>>>> nodea:~> sudo xenstore-ls >>>>> tool =3D "" >>>>> xenstored =3D "" >>>>> local =3D "" >>>>> domain =3D "" >>>>> 0 =3D "" >>>>> data =3D "" >>>>> meminfo_total =3D "930680" >>>>> meminfo_free =3D "695408" >>>>> os_name =3D "Ubuntu 12.04.1 LTS" >>>>> os_majorver =3D "12" >>>>> os_minorver =3D "04" >>>>> os_uname =3D "3.8.0-rc5+" >>>>> os_distro =3D "ubuntu" >>>>> updated =3D "Sun Feb 3 10:45:32 MST 2013" >>>>> name =3D "Domain-0" >>>>> attr =3D "" >>>>> xenbr0 =3D "" >>>>> ip =3D "155.98.39.2" >>>>> PVAddons =3D "" >>>>> MajorVersion =3D "5" >>>>> MinorVersion =3D "5" >>>>> MicroVersion =3D "0" >>>>> BuildVersion =3D "17913" >>>>> Installed =3D "1" >>>>> device-model =3D "" >>>>> 0 =3D "" >>>>> state =3D "running" >>>>> memory =3D "" >>>>> target =3D "1048576" >>>>> static-max =3D "4294967292" >>>>> freemem-slack =3D "314476" >>>>> libxl =3D "" >>>>> disable_udev =3D "1" >>>>> backend =3D "" >>>>> vbd =3D "" >>>>> 1 =3D "" >>>>> 2049 =3D "" >>>>> frontend =3D "/local/domain/1/device/vbd/2049" <<<< = >>>>> everything >>>>> seems to be enumerated >>>>> params =3D "/dev/loop0" >>>>> script =3D "/etc/xen/scripts/block" >>>>> physical-device =3D "7:0" >>>>> frontend-id =3D "1" >>>>> online =3D "1" >>>>> removable =3D "0" >>>>> bootable =3D "1" >>>>> state =3D "1" >>>>> dev =3D "sda1" >>>>> type =3D "phy" >>>>> mode =3D "w" >>>>> device-type =3D "disk" >>>>> 1 =3D "" >>>>> vm =3D "/vm/9b0dfb10-f69d-4e22-9158-bb70456ece2e" >>>>> name =3D "guest2" >>>>> cpu =3D "" >>>>> 0 =3D "" >>>>> availability =3D "online" >>>>> memory =3D "" >>>>> static-max =3D "512000" >>>>> target =3D "512001" >>>>> videoram =3D "-1" >>>>> device =3D "" >>>>> suspend =3D "" >>>>> event-channel =3D "" >>>>> vbd =3D "" >>>>> 2049 =3D "" >>>>> backend =3D "/local/domain/0/backend/vbd/1/2049" >>>>> backend-id =3D "0" >>>>> state =3D "1" <<<<< state changes to 5 and then after 5 = >>>>> secs it >>>>> times out >>>>> virtual-device =3D "2049" >>>>> device-type =3D "disk" >>>>> control =3D "" >>>>> shutdown =3D "" >>>>> platform-feature-multiprocessor-suspend =3D "1" >>>>> platform-feature-xs_reset_watches =3D "1" >>>>> data =3D "" >>>>> domid =3D "1" >>>>> store =3D "" >>>>> port =3D "1" >>>>> ring-ref =3D "156845" >>>>> vm =3D "" >>>>> 9b0dfb10-f69d-4e22-9158-bb70456ece2e =3D "" >>>>> uuid =3D "9b0dfb10-f69d-4e22-9158-bb70456ece2e" >>>>> name =3D "guest2" >>>>> image =3D "" >>>>> ostype =3D "linux" >>>>> kernel =3D "/boot/vmlinuz-3.8.0-rc5+" >>>>> ramdisk =3D "/boot/initrd.img-3.8.0-rc5+" >>>>> cmdline =3D "root=3D/dev/disk/by-path/xen-vbd-2049 ro xencons= =3Dtty" >>>>> start_time =3D "1359913591.67" >>>>> libxl =3D "" >>>>> 1 =3D "" >>>>> dm-version =3D "qemu_xen" >>>>> >>>>> Thanks, >>>>> Yathi > Sorry about top posting. I changed it to xvda1 and I still see the = > same behavior. > I instrumented the backend drivers and here's a trace of the events. I = observed that XS_DIRECTORY for "backend" ( as the "backend" node was not created in = xenstore yet) and "device" ( as the "device" node was not created in xenstore yet) = fails to return anything. Are they supposed to be in xenstore right after dom0 is created ? [ 3.011816] xen-balloon: Initialising balloon driver. [ 3.016043] xen/balloon: Xen selfballooning driver disabled for domain0. [ 3.420054] Switching to clocksource xen [ 3.510038] xen: registering gsi 13 triggering 1 polarity 0 [ 3.540022] xen: registering gsi 8 triggering 1 polarity 0 [ 3.566198] xen: registering gsi 4 triggering 1 polarity 0 [ 3.589252] xen: registering gsi 3 triggering 1 polarity 0 [ 4.096790] xen: registering gsi 16 triggering 0 polarity 1 [ 4.102431] xen: --> pirq=3D16 -> irq=3D16 (gsi=3D16) [ 4.107062] xen: registering gsi 16 triggering 0 polarity 1 [ 4.116460] xen: registering gsi 16 triggering 0 polarity 1 [ 4.125956] xen: registering gsi 16 triggering 0 polarity 1 [ 4.135307] xen: registering gsi 16 triggering 0 polarity 1 [ 4.144529] xen: registering gsi 16 triggering 0 polarity 1 [ 4.153912] xen: registering gsi 16 triggering 0 polarity 1 [ 4.163262] xen: registering gsi 16 triggering 0 polarity 1 [ 4.469657] xen: registering gsi 21 triggering 0 polarity 1 [ 4.475307] xen: --> pirq=3D21 -> irq=3D21 (gsi=3D21) [ 4.486553] xen: registering gsi 20 triggering 0 polarity 1 [ 4.492186] xen: --> pirq=3D20 -> irq=3D20 (gsi=3D20) [ 4.503457] xen: registering gsi 21 triggering 0 polarity 1 [ 4.519484] xen: registering gsi 20 triggering 0 polarity 1 [ 4.535518] xen: registering gsi 21 triggering 0 polarity 1 [ 5.733514] xenbus_register_frontend [ 5.788723] xenbus_register_frontend [ 5.796982] xen: registering gsi 23 triggering 0 polarity 1 [ 5.802619] xen: --> pirq=3D23 -> irq=3D23 (gsi=3D23) [ 6.019447] xenbus_register_frontend [ 6.029696] xen: registering gsi 21 triggering 0 polarity 1 [ 6.122280] xen: registering gsi 21 triggering 0 polarity 1 [ 6.214955] xen: registering gsi 20 triggering 0 polarity 1 [ 6.262081] xen: registering gsi 21 triggering 0 polarity 1 [ 6.309240] xen: registering gsi 20 triggering 0 polarity 1 [ 6.657173] xen: registering gsi 18 triggering 0 polarity 1 [ 6.657232] xen: registering gsi 16 triggering 0 polarity 1 [ 6.672277] xen: --> pirq=3D18 -> irq=3D18 (gsi=3D18) [ 6.761063] xen: registering gsi 16 triggering 0 polarity 1 [ 6.785518] xen: registering gsi 16 triggering 0 polarity 1 [ 7.015253] xen: registering gsi 19 triggering 0 polarity 1 [ 7.020861] xen: --> pirq=3D19 -> irq=3D19 (gsi=3D19) [ 7.339228] xen: registering gsi 16 triggering 0 polarity 1 [ 7.673945] xen: registering gsi 17 triggering 0 polarity 1 [ 7.679568] xen: --> pirq=3D17 -> irq=3D17 (gsi=3D17) [ 38.374483] xen: registering gsi 19 triggering 0 polarity 1 [ 44.712442] xenbr0: port 1(eth0) entered forwarding state [ 44.712449] xenbr0: port 1(eth0) entered forwarding state [ 48.572924] xen_blkif_xenbus_init: Register xen_blkbk_driver [ 48.572928] xenbus_register_backend [ 48.596414] xenbus_register_backend [ 48.619245] xen-pciback: backend is vpci [ 48.619251] xenbus_register_backend [ 48.776436] xenbus_scanf for node cpu/0 [ 48.782133] XENBUS xen store gave: unknown error cpu [ 48.782137] xenbus_scanf for node cpu/1 [ 48.782386] xenbus_scanf for node cpu/2 [ 48.782605] xenbus_scanf for node cpu/3 [ 48.782813] xenbus_scanf for node cpu/4 [ 48.783019] xenbus_scanf for node cpu/5 [ 48.783225] xenbus_scanf for node cpu/6 [ 48.783432] xenbus_scanf for node cpu/7 [ 48.783917] Failed to set shutdown watcher =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D [ 48.793731] backend_probe_and_watch [ 48.793733] xenbus_probe_devices started ... [ 48.793821] xenbus_directory: get dir "backend" contents [ 48.793825] xenbus_directory: ERROR getting dir = 8\xffffff92\xffffffb9\xfffffff7\x01\xffffff88\xffffffff\xffffffff\xffff ffd0\xffffff99\xffffff99\xffffffb9\xfffffff7\x01\xffffff88\xffffffff\xfffff= fffX\xffffff92\xffffffb9\xfffffff7\x01\xffffff8 8\xffffffff\xffffffff`\xffffff92\xffffffb9\xfffffff7\x01\xffffff88\xfffffff= f\xffffffff\xffffff98\xffffff90\xffffffb9\xffff fff7\x01\xffffff88\xffffffff\xffffffff\xffffffc8\xffffff99\xffffff99\xfffff= fb9\xfffffff7\x01\xffffff88\xffffffff\xffffffff \x01 contents [ 48.793827] xenbus_probe_devices: ERROR after xenbus_directory [ 48.793831] XENBUS xen store gave: unknown error control/shutdown [ 48.793831] XENBUS xen store gave: unknown error control/shutdown =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D [ 48.793833] frontend_probe_and_watch [ 48.793835] xenbus_probe_devices started ... [ 48.793837] xenbus_directory: get dir "device" contents [ 48.797288] xenbus_directory: ERROR getting dir = 8\xffffff92\xffffffb9\xfffffff7\x01\xffffff88\xffffffff\xffffffffOK cos [ 48.797290] xenbus_probe_devices: ERROR after xenbus_directory [ 48.797298] XENBUS xen store gave: unknown error backend [ 48.797299] Failed to set balloon watcher =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D [ 59.740081] xenbr0: port 1(eth0) entered forwarding state [ 63.739432] NFS: Registering the id_resolver key type [ 63.739455] Key type id_resolver registered [ 63.739457] Key type id_legacy registered [ 82.767858] init: ttyS0 main process (2257) terminated with status 1 [ 82.767909] init: ttyS0 main process ended, respawning Thanks, Yathi _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Sat Feb 09 12:08:52 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sat, 09 Feb 2013 12:08: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 1U49D9-0006dQ-EC; Sat, 09 Feb 2013 12:07:15 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U3yv1-0003Bz-O1 for xen-users@lists.xen.org; Sat, 09 Feb 2013 01:07:52 +0000 Received: from [85.158.139.83:43745] by server-8.bemta-5.messagelabs.com id 6D/96-19075-661A5115; Sat, 09 Feb 2013 01:07:50 +0000 X-Env-Sender: oleg.stepura@gmail.com X-Msg-Ref: server-4.tower-182.messagelabs.com!1360372068!26118157!1 X-Originating-IP: [209.85.214.179] 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.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 16967 invoked from network); 9 Feb 2013 01:07:49 -0000 Received: from mail-ob0-f179.google.com (HELO mail-ob0-f179.google.com) (209.85.214.179) by server-4.tower-182.messagelabs.com with RC4-SHA encrypted SMTP; 9 Feb 2013 01:07:49 -0000 Received: by mail-ob0-f179.google.com with SMTP id un3so4509753obb.38 for ; Fri, 08 Feb 2013 17:07:29 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:mime-version:sender:from:date:x-google-sender-auth :message-id:subject:to:content-type; bh=YZzYglYkZlbkpb87yDzbyXDUvpo5omik3ZHCRLjZ11Y=; b=QlDD/56mtqdCDH/ZsCeYlJlkMi7MnlJlYMgy26KYZQoqRDMfUnon7Fls32/HTVFWg7 tUKqN5d3DWgaGFivjsG+tKe2oPTEMA2XoOyCO0Hpy03DrmGVspb+0ys9YkIKsWmov4Gx om0dAA77RrYGVrkUwE5NbI61Lud51AebWhg8Hz1mkrXyQaELp6gAj3EJlTJOHNfGMthV 5/SHIejlBHGfbdv7YGyMwtGupxZHpycgpZj0jvHjgEoEXAaMqh3/lLayBi5uxy/Z+e9/ ZEcRkLdKxwcpuWxBLgAljbRsOWKXi6FNkaA8T4SGTE2e4GS0fZ68oYoxH2cZpWdl0B2/ zEYA== X-Received: by 10.60.32.134 with SMTP id j6mr5848825oei.15.1360372049266; Fri, 08 Feb 2013 17:07:29 -0800 (PST) MIME-Version: 1.0 Received: by 10.76.26.3 with HTTP; Fri, 8 Feb 2013 17:06:49 -0800 (PST) From: Oleg Stepura Date: Sat, 9 Feb 2013 04:06:49 +0300 X-Google-Sender-Auth: agf2W5xEq78LuXSHKhEkyJkbk1I Message-ID: To: xen-users@lists.xen.org X-Mailman-Approved-At: Sat, 09 Feb 2013 12:07:12 +0000 Subject: [Xen-users] Asrock X79 Extreme9 + Intel i7-3820 X-BeenThere: xen-users@lists.xen.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="===============3474663833297213215==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============3474663833297213215== Content-Type: multipart/alternative; boundary=e89a8fb1f07cc2481e04d5404c28 --e89a8fb1f07cc2481e04d5404c28 Content-Type: text/plain; charset=UTF-8 Hi! I decided to build a new virtualization PC instead of two regular PCs being used currently. The purpose is to create a XEN-based setup on Gentoo, planning to have Dom0 for Media-center (on XBMC) and domU with VGA-passthrough for Gaming. Searching through all possible options I found that the best chipset with huge data throughput currently is x79, and there are some motherboards with reported successful VGA passed through on this chipset as well as x79 is listed on Intel as supported for Vt-d ( http://www.intel.com/support/motherboards/desktop/sb/CS-030922.htm). The motherboard I stopped at is Asrock X79 Extreme9 ( http://www.asrock.com/mb/Intel/X79%20Extreme9/index.asp). This MB is cool since it has lots of SATA ports and several PCIex16 slots thus theoretically allowing multiple VMs to work with VGA passed through. Also it's good in terms of future upgrades since it supports up to 64Gb of RAM so maybe in future I will just buy extra memory if needed. And 4-channel memory should be faster that the regular 2-channel on Z77 chipsets. Since all the CPUs for LGA2011 are still too expensive the only one I can afford is Intel i7-3820 ( http://ark.intel.com/products/63698/Intel-Core-i7-3820-Processor-10M-Cache-up-to-3_80-GHz). Both the MB and CPU are advertised to support VT-d (the MB has Vt-d in BIOS according to manual). According to history here: http://wiki.xen.org/wiki/VTd_HowTo someone named Mans added on 4 dec 2012 Asrock X79 Extreme9 as a supported motherboard for VT-d. But I cannot find any success story for passing VGA through to DomU VMs with this motherboard. Since the whole amount of money spent for the new rig is big, I need your help. - Can anyone confirm that this motherboard (or better this MB with this CPU) work for VGA Passthrough with XEN? - Is this motherboard somewhat compatible with XEN in the sense that all required drivers are already in kernel? - Can anyone tell if this motherboard allows inserting PCIe x1 cards into it's lower PCIex16 slots (WIFI card and audio card in my case)? (Maybe any MB allows, just don't know) Thanks a lot! --e89a8fb1f07cc2481e04d5404c28 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Hi!

I decided to build a new virtualization PC instead o= f two regular PCs being used currently. The purpose is to create a XEN-base= d setup on Gentoo, planning to have Dom0 for Media-center (on XBMC) and dom= U with VGA-passthrough for Gaming.

Searching through all possible options I found that the= best chipset with huge data throughput currently is x79, and there are som= e motherboards with reported successful VGA passed through on this chipset = as well as x79 is listed on Intel as supported for Vt-d (http://www.intel.com/support/motherboards/desktop/sb/CS-030922.htm)= .

The motherboard I stopped at is Asrock X79 Extreme9 (http://www.asrock.com/mb/Intel/X79%20Extreme9/index.asp). This= MB is cool since it has lots of SATA ports and several PCIex16 slots thus = theoretically allowing multiple VMs to work with VGA passed through. Also i= t's good in terms of future upgrades since it supports up to 64Gb of RA= M so maybe in future I will just buy extra memory if needed. And 4-channel = memory should be faster that the regular 2-channel on Z77 chipsets.

Since all the CPUs for LGA2011 are still too expensive = the only one I can afford is Intel i7-3820=C2=A0(http://ark.intel.com/products/63698/Intel-Core-i7-3820-P= rocessor-10M-Cache-up-to-3_80-GHz). Both the MB and CPU are advertised = to support VT-d (the MB has Vt-d in BIOS according to manual).

According to history here:=C2=A0http://wiki.xen.org/wiki/VTd_HowTo= someone named Mans=C2=A0added=C2=A0on 4 dec 2012 Asrock X79 Extreme9 as a = supported motherboard for VT-d. But I cannot find any success story for pas= sing VGA through to DomU VMs with this motherboard. Since the whole amount = of money spent for the new rig is big, I need your help.

- Can anyone confirm that this motherboard (or better t= his MB with this CPU) work for VGA Passthrough with XEN?
- Is thi= s motherboard somewhat compatible with XEN in the sense that all required d= rivers are already in kernel?
- Can anyone tell if this motherboard allows inserting PCIe x1 cards i= nto it's lower PCIex16 slots (WIFI card and audio card in my case)? (Ma= ybe any MB allows, just don't know)

Thanks a lot!
--e89a8fb1f07cc2481e04d5404c28-- --===============3474663833297213215== 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 --===============3474663833297213215==-- From xen-users-bounces@lists.xen.org Sat Feb 09 12:39:41 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sat, 09 Feb 2013 12:39: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 1U49hX-0008OU-Vl; Sat, 09 Feb 2013 12:38:39 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U49hV-0008OF-JR; Sat, 09 Feb 2013 12:38:37 +0000 Received: from [85.158.139.211:61922] by server-7.bemta-5.messagelabs.com id B0/12-11121-C4346115; Sat, 09 Feb 2013 12:38:36 +0000 X-Env-Sender: mailinglists.tech@gmail.com X-Msg-Ref: server-8.tower-206.messagelabs.com!1360413514!21770854!1 X-Originating-IP: [209.85.216.48] 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.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 3567 invoked from network); 9 Feb 2013 12:38:35 -0000 Received: from mail-qa0-f48.google.com (HELO mail-qa0-f48.google.com) (209.85.216.48) by server-8.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 9 Feb 2013 12:38:35 -0000 Received: by mail-qa0-f48.google.com with SMTP id j8so655588qah.7 for ; Sat, 09 Feb 2013 04:38:34 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:date:message-id:subject:from:to :content-type; bh=OEiCj3TyRc5wMW9y95MZySVOfgeNrWxmTKlb/cU/ob0=; b=X3k8j1DxouxrttHAZ8JuzpLekv5TVoAk4+Wwjdsi36HGtYhApTl4ym82DFRAbA6XBq 7EsjJqM7o47mIwH86glflI8SwXgPbwMkPTtwZCgddiiw+OabPxK4iyHdHkUjkmLd4LkW j85PqWpRvE6gDM09rQESrmjlxGkqF3Bc+J4kLLJdG/KD+16vNg6CytbuO4+XXlgrtOzo GZax/1N8hCh9RLdb86rMWvF5MV0XtiId4dky7iTeycTzoDEx/wzYOtv4baSt0NSPhHJk 74HN9+Zb2MlTTvyX3kxCUvMMNlj5VFm8qaIU1JjKnuOYWVUHdqieoO9FopCP/6U8PGY6 nRRA== MIME-Version: 1.0 X-Received: by 10.224.111.83 with SMTP id r19mr3246873qap.39.1360413514498; Sat, 09 Feb 2013 04:38:34 -0800 (PST) Received: by 10.49.110.70 with HTTP; Sat, 9 Feb 2013 04:38:34 -0800 (PST) Date: Sat, 9 Feb 2013 13:38:34 +0100 Message-ID: From: tech mailinglists To: port-xen@netbsd.org, xen-users , "xen-devel@lists.xen.org" Subject: [Xen-users] Building Xen 4.2.1 with vTPM on NetBSD 6.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-Type: multipart/mixed; boundary="===============8023340392125098007==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============8023340392125098007== Content-Type: multipart/alternative; boundary=20cf306f77a847833704d549f4a8 --20cf306f77a847833704d549f4a8 Content-Type: text/plain; charset=ISO-8859-1 Hello all, I try to build Xen 4.2.1 on NetBSD 6.0.1 with vTPM. I would say that dependencies are missing but I don't know it. I have done the following: I installed the building dependencies from pkgsrc Run configure as follows: ./configure PYTHON=/usr/pkg/bin/python2.7 APPEND_INCLUDES=/usr/pkg/include APPEND_LIB=/usr/pkg/lib --prefix=/usr/xen42 --enable-vtpm Builded Xen itself successfully. Run gmake for the tools target as follows: gmake LD_LIBRARY_PATH=/usr/pkg/lib tools This fails with the following error: gmake[5]: Entering directory `/root/xen-4.2.1/tools/vtpm_manager/manager' gcc -Werror -g3 -D_GNU_SOURCE -DLOGGING_MODULES="(BITMASK(VTPM_LOG_TCS)|BITMASK(VTPM_LOG_VTSP)|BITMASK(VTPM_LOG_VTPM))" -I/root/xen-4.2.1/tools/vtpm_manager/manager/../../../tools/vtpm_manager/crypto -I/root/xen-4.2.1/tools/vtpm_manager/manager/../../../tools/vtpm_manager/util -I/root/xen-4.2.1/tools/vtpm_manager/manager/../../../tools/vtpm_manager/tcs -I/root/xen-4.2.1/tools/vtpm_manager/manager/../../../tools/vtpm_manager/manager -pthread -c -o vtpmd.o vtpmd.c -I/usr/pkg/include cc1: warnings being treated as errors vtpmd.c: In function 'signal_handler': vtpmd.c:96:3: error: passing argument 2 of '__libc_thr_equal' makes pointer from integer without a cast /usr/include/pthread.h:368:5: note: expected 'pthread_t' but argument is of type '__pid_t' vtpmd.c: In function 'main': vtpmd.c:343:28: error: assignment makes integer from pointer without a cast gmake[5]: *** [vtpmd.o] Error 1 gmake[5]: Leaving directory `/root/xen-4.2.1/tools/vtpm_manager/manager' gmake[4]: *** [subdir-install-manager] Error 2 gmake[4]: Leaving directory `/root/xen-4.2.1/tools/vtpm_manager' gmake[3]: *** [subdirs-install] Error 2 gmake[3]: Leaving directory `/root/xen-4.2.1/tools/vtpm_manager' gmake[2]: *** [subdir-install-vtpm_manager] Error 2 gmake[2]: Leaving directory `/root/xen-4.2.1/tools' gmake[1]: *** [subdirs-install] Error 2 gmake[1]: Leaving directory `/root/xen-4.2.1/tools' gmake: *** [install-tools] Error 2 So I know that already one dependency is missing I think it's libgmp but I found no way to build it on NetBSD. Is vTPM buildable on NetBSD and what does this error/warning which was treated as error mean? Best Regards --20cf306f77a847833704d549f4a8 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable

Hello all,

I try to build Xen 4= .2.1 on NetBSD 6.0.1 with vTPM. I would say that dependencies are missing b= ut I don't know it.

I have done the following:
I installed the building dependencies from pkgsrc

<= div>Run configure as follows: 
./configure PYTHON=3D/usr/pkg/bin/py=
thon2.7 APPEND_INCLUDES=3D/usr/pkg/include APPEND_LIB=3D/usr/pkg/lib --pref=
ix=3D/usr/xen42 --enable-vtpm


Builded Xen itself successfully.

Run gmake=
 for the tools target as follows: 

gmake LD_LIBRARY_PATH=3D/usr/pkg/=
lib tools

This fails with the following error:



gmake[5]: Entering directory `/root/xen-4.2.1/tools/vtpm_manager/manag=
er'
gcc  -Werror -g3 -D_GNU_SOURCE -DLOGGING_MODULES=3D"(BITMAS=
K(VTPM_LOG_TCS)|BITMASK(VTPM_LOG_VTSP)|BITMASK(VTPM_LOG_VTPM))" -I/roo=
t/xen-4.2.1/tools/vtpm_manager/manager/../../../tools/vtpm_manager/crypto -=
I/root/xen-4.2.1/tools/vtpm_manager/manager/../../../tools/vtpm_manager/uti=
l -I/root/xen-4.2.1/tools/vtpm_manager/manager/../../../tools/vtpm_manager/=
tcs -I/root/xen-4.2.1/tools/vtpm_manager/manager/../../../tools/vtpm_manage=
r/manager -pthread  -c -o vtpmd.o vtpmd.c  -I/usr/pkg/include

cc1: warnings being treated as errors
vtpmd.c: In function 'signal_h=
andler':
vtpmd.c:96:3: error: passing argument 2 of '__libc_thr_=
equal' makes pointer from integer without a cast
/usr/include/pthrea=
d.h:368:5: note: expected 'pthread_t' but argument is of type '=
__pid_t'

vtpmd.c: In function 'main':
vtpmd.c:343:28: error: assignment m=
akes integer from pointer without a cast
gmake[5]: *** [vtpmd.o] Error 1=

gmake[5]: Leaving directory `/root/xen-4.2.1/tools/vtpm_manager/manager=
'

gmake[4]: *** [subdir-install-manager] Error 2
gmake[4]: Leaving directo=
ry `/root/xen-4.2.1/tools/vtpm_manager'
gmake[3]: *** [subdirs-insta=
ll] Error 2
gmake[3]: Leaving directory `/root/xen-4.2.1/tools/vtpm_mana=
ger'

gmake[2]: *** [subdir-install-vtpm_manager] Error 2
gmake[2]: Leaving di=
rectory `/root/xen-4.2.1/tools'
gmake[1]: *** [subdirs-install] Erro=
r 2
gmake[1]: Leaving directory `/root/xen-4.2.1/tools'
gmake: **=
* [install-tools] Error 2


So I know that already one dependency is missing I think it&=
#39;s libgmp but I found no way to build it on NetBSD.

Is=
 vTPM buildable on NetBSD and what does this error/warning which was treate=
d as error mean?


Best Regards
--20cf306f77a847833704d549f4a8-- --===============8023340392125098007== 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 --===============8023340392125098007==-- From xen-users-bounces@lists.xen.org Sat Feb 09 12:39:41 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sat, 09 Feb 2013 12:39: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 1U49hX-0008OU-Vl; Sat, 09 Feb 2013 12:38:39 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U49hV-0008OF-JR; Sat, 09 Feb 2013 12:38:37 +0000 Received: from [85.158.139.211:61922] by server-7.bemta-5.messagelabs.com id B0/12-11121-C4346115; Sat, 09 Feb 2013 12:38:36 +0000 X-Env-Sender: mailinglists.tech@gmail.com X-Msg-Ref: server-8.tower-206.messagelabs.com!1360413514!21770854!1 X-Originating-IP: [209.85.216.48] 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.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 3567 invoked from network); 9 Feb 2013 12:38:35 -0000 Received: from mail-qa0-f48.google.com (HELO mail-qa0-f48.google.com) (209.85.216.48) by server-8.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 9 Feb 2013 12:38:35 -0000 Received: by mail-qa0-f48.google.com with SMTP id j8so655588qah.7 for ; Sat, 09 Feb 2013 04:38:34 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:date:message-id:subject:from:to :content-type; bh=OEiCj3TyRc5wMW9y95MZySVOfgeNrWxmTKlb/cU/ob0=; b=X3k8j1DxouxrttHAZ8JuzpLekv5TVoAk4+Wwjdsi36HGtYhApTl4ym82DFRAbA6XBq 7EsjJqM7o47mIwH86glflI8SwXgPbwMkPTtwZCgddiiw+OabPxK4iyHdHkUjkmLd4LkW j85PqWpRvE6gDM09rQESrmjlxGkqF3Bc+J4kLLJdG/KD+16vNg6CytbuO4+XXlgrtOzo GZax/1N8hCh9RLdb86rMWvF5MV0XtiId4dky7iTeycTzoDEx/wzYOtv4baSt0NSPhHJk 74HN9+Zb2MlTTvyX3kxCUvMMNlj5VFm8qaIU1JjKnuOYWVUHdqieoO9FopCP/6U8PGY6 nRRA== MIME-Version: 1.0 X-Received: by 10.224.111.83 with SMTP id r19mr3246873qap.39.1360413514498; Sat, 09 Feb 2013 04:38:34 -0800 (PST) Received: by 10.49.110.70 with HTTP; Sat, 9 Feb 2013 04:38:34 -0800 (PST) Date: Sat, 9 Feb 2013 13:38:34 +0100 Message-ID: From: tech mailinglists To: port-xen@netbsd.org, xen-users , "xen-devel@lists.xen.org" Subject: [Xen-users] Building Xen 4.2.1 with vTPM on NetBSD 6.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-Type: multipart/mixed; boundary="===============8023340392125098007==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============8023340392125098007== Content-Type: multipart/alternative; boundary=20cf306f77a847833704d549f4a8 --20cf306f77a847833704d549f4a8 Content-Type: text/plain; charset=ISO-8859-1 Hello all, I try to build Xen 4.2.1 on NetBSD 6.0.1 with vTPM. I would say that dependencies are missing but I don't know it. I have done the following: I installed the building dependencies from pkgsrc Run configure as follows: ./configure PYTHON=/usr/pkg/bin/python2.7 APPEND_INCLUDES=/usr/pkg/include APPEND_LIB=/usr/pkg/lib --prefix=/usr/xen42 --enable-vtpm Builded Xen itself successfully. Run gmake for the tools target as follows: gmake LD_LIBRARY_PATH=/usr/pkg/lib tools This fails with the following error: gmake[5]: Entering directory `/root/xen-4.2.1/tools/vtpm_manager/manager' gcc -Werror -g3 -D_GNU_SOURCE -DLOGGING_MODULES="(BITMASK(VTPM_LOG_TCS)|BITMASK(VTPM_LOG_VTSP)|BITMASK(VTPM_LOG_VTPM))" -I/root/xen-4.2.1/tools/vtpm_manager/manager/../../../tools/vtpm_manager/crypto -I/root/xen-4.2.1/tools/vtpm_manager/manager/../../../tools/vtpm_manager/util -I/root/xen-4.2.1/tools/vtpm_manager/manager/../../../tools/vtpm_manager/tcs -I/root/xen-4.2.1/tools/vtpm_manager/manager/../../../tools/vtpm_manager/manager -pthread -c -o vtpmd.o vtpmd.c -I/usr/pkg/include cc1: warnings being treated as errors vtpmd.c: In function 'signal_handler': vtpmd.c:96:3: error: passing argument 2 of '__libc_thr_equal' makes pointer from integer without a cast /usr/include/pthread.h:368:5: note: expected 'pthread_t' but argument is of type '__pid_t' vtpmd.c: In function 'main': vtpmd.c:343:28: error: assignment makes integer from pointer without a cast gmake[5]: *** [vtpmd.o] Error 1 gmake[5]: Leaving directory `/root/xen-4.2.1/tools/vtpm_manager/manager' gmake[4]: *** [subdir-install-manager] Error 2 gmake[4]: Leaving directory `/root/xen-4.2.1/tools/vtpm_manager' gmake[3]: *** [subdirs-install] Error 2 gmake[3]: Leaving directory `/root/xen-4.2.1/tools/vtpm_manager' gmake[2]: *** [subdir-install-vtpm_manager] Error 2 gmake[2]: Leaving directory `/root/xen-4.2.1/tools' gmake[1]: *** [subdirs-install] Error 2 gmake[1]: Leaving directory `/root/xen-4.2.1/tools' gmake: *** [install-tools] Error 2 So I know that already one dependency is missing I think it's libgmp but I found no way to build it on NetBSD. Is vTPM buildable on NetBSD and what does this error/warning which was treated as error mean? Best Regards --20cf306f77a847833704d549f4a8 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable

Hello all,

I try to build Xen 4= .2.1 on NetBSD 6.0.1 with vTPM. I would say that dependencies are missing b= ut I don't know it.

I have done the following:
I installed the building dependencies from pkgsrc

<= div>Run configure as follows: 
./configure PYTHON=3D/usr/pkg/bin/py=
thon2.7 APPEND_INCLUDES=3D/usr/pkg/include APPEND_LIB=3D/usr/pkg/lib --pref=
ix=3D/usr/xen42 --enable-vtpm


Builded Xen itself successfully.

Run gmake=
 for the tools target as follows: 

gmake LD_LIBRARY_PATH=3D/usr/pkg/=
lib tools

This fails with the following error:



gmake[5]: Entering directory `/root/xen-4.2.1/tools/vtpm_manager/manag=
er'
gcc  -Werror -g3 -D_GNU_SOURCE -DLOGGING_MODULES=3D"(BITMAS=
K(VTPM_LOG_TCS)|BITMASK(VTPM_LOG_VTSP)|BITMASK(VTPM_LOG_VTPM))" -I/roo=
t/xen-4.2.1/tools/vtpm_manager/manager/../../../tools/vtpm_manager/crypto -=
I/root/xen-4.2.1/tools/vtpm_manager/manager/../../../tools/vtpm_manager/uti=
l -I/root/xen-4.2.1/tools/vtpm_manager/manager/../../../tools/vtpm_manager/=
tcs -I/root/xen-4.2.1/tools/vtpm_manager/manager/../../../tools/vtpm_manage=
r/manager -pthread  -c -o vtpmd.o vtpmd.c  -I/usr/pkg/include

cc1: warnings being treated as errors
vtpmd.c: In function 'signal_h=
andler':
vtpmd.c:96:3: error: passing argument 2 of '__libc_thr_=
equal' makes pointer from integer without a cast
/usr/include/pthrea=
d.h:368:5: note: expected 'pthread_t' but argument is of type '=
__pid_t'

vtpmd.c: In function 'main':
vtpmd.c:343:28: error: assignment m=
akes integer from pointer without a cast
gmake[5]: *** [vtpmd.o] Error 1=

gmake[5]: Leaving directory `/root/xen-4.2.1/tools/vtpm_manager/manager=
'

gmake[4]: *** [subdir-install-manager] Error 2
gmake[4]: Leaving directo=
ry `/root/xen-4.2.1/tools/vtpm_manager'
gmake[3]: *** [subdirs-insta=
ll] Error 2
gmake[3]: Leaving directory `/root/xen-4.2.1/tools/vtpm_mana=
ger'

gmake[2]: *** [subdir-install-vtpm_manager] Error 2
gmake[2]: Leaving di=
rectory `/root/xen-4.2.1/tools'
gmake[1]: *** [subdirs-install] Erro=
r 2
gmake[1]: Leaving directory `/root/xen-4.2.1/tools'
gmake: **=
* [install-tools] Error 2


So I know that already one dependency is missing I think it&=
#39;s libgmp but I found no way to build it on NetBSD.

Is=
 vTPM buildable on NetBSD and what does this error/warning which was treate=
d as error mean?


Best Regards
--20cf306f77a847833704d549f4a8-- --===============8023340392125098007== 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 --===============8023340392125098007==-- From xen-users-bounces@lists.xen.org Sun Feb 10 11:23:58 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sun, 10 Feb 2013 11: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 1U4Uyy-0000sH-KS; Sun, 10 Feb 2013 11:22:04 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U4Uyw-0000sC-Mn for xen-users@lists.xen.org; Sun, 10 Feb 2013 11:22:02 +0000 Received: from [85.158.139.83:39041] by server-5.bemta-5.messagelabs.com id 74/9A-11945-9D287115; Sun, 10 Feb 2013 11:22:01 +0000 X-Env-Sender: peter.gansterer@paradigma.net X-Msg-Ref: server-11.tower-182.messagelabs.com!1360495320!20727072!1 X-Originating-IP: [213.47.215.227] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 17737 invoked from network); 10 Feb 2013 11:22:01 -0000 Received: from majere.luchs.at (HELO majere.luchs.at) (213.47.215.227) by server-11.tower-182.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 10 Feb 2013 11:22:01 -0000 Received: from localhost (localhost [127.0.0.1]) by majere.luchs.at (Postfix) with ESMTP id 8C39CD007E28 for ; Sun, 10 Feb 2013 12:21:59 +0100 (CET) X-Virus-Scanned: by majere.luchs.at Received: from majere.luchs.at ([127.0.0.1]) by localhost (majere.luchs.at [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5JEnR0wRzLqG for ; Sun, 10 Feb 2013 12:21:58 +0100 (CET) Received: from earth (earth.elements.lan [10.0.0.2]) by majere.luchs.at (Postfix) with ESMTP id 1FBB1D007E21 for ; Sun, 10 Feb 2013 12:21:58 +0100 (CET) Received: from pedos (pedos.elements.lan [10.0.0.108]) by earth (Postfix) with SMTP id 80C793E22D for ; Sun, 10 Feb 2013 12:21:56 +0100 (CET) Received: by pedos (sSMTP sendmail emulation); Sun, 10 Feb 2013 12:20:06 +0100 Content-Disposition: inline MIME-Version: 1.0 X-Mailer: MIME-tools 5.503 (Entity 5.503) Message-ID: <1360494858.301F0a21.2491@pedos> From: "Peter Gansterer" Date: Sun, 10 Feb 2013 12:20:04 +0100 In-Reply-To: <1360255718.EBA4d10.2491@pedos> To: "xen-users" Subject: Re: [Xen-users] "dynamic memory allocation" for windows guests? X-BeenThere: xen-users@lists.xen.org X-Mailman-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 SGkgYWdhaW4sCgpBcmUgdGhlcmUgcmVhbGx5IG5vIGhpbnRzIGFib3V0IHRoaXMgdG9waWM/CgpJ dCB3b3VsZCBhbHNvIGJlIHVzZWZ1bCB0byBkZWZpbml0ZWx5IGtub3cgdGhlcmUgaXMgbm8gc29s dXRpb24gZm9yIHdoYXQgd2UgYXJlIGxvb2tpbmcgZm9yIC0gb3IgZXZlbiBpbnB1dCBhcyB0byB3 aHkgdGhpcyB3b3VsZG4ndCB3b3JrLgpPdGhlcndpc2Ugd2UnZCB0aGluayBhYm91dCB0cnlpbmcg aXQgb24gb3VyIG93bi4KCi0gcGVkYS4KCgpPbiAyMDEzLTAyLTA3IDE4OjM3OjE2LjQ4MTQxNiBQ ZXRlciBHYW5zdGVyZXIgd3JvdGU6Cj4gSGVsbG8sCj4gCj4gSW4gb3VyIG9mZmljZSB3ZSB3b3Vs ZCBsaWtlIHRvIGRvIHNvbWV0aGluZyBsaWtlICJtZW1vcnkgb3ZlcmNvbW1pdG1lbnQiCj4gb3Ig cmF0aGVyICJkeW5hbWljIGFsbG9jYXRpb24iIGZvciBhIGJ1bmNoIG9mIHdpbmRvd3MgZG9tVXMg KHNlcnZlciAyMDAzICYgMjAwOCkuCj4gCj4gV2UgdGhvdWdodCB0aGlzIHNob3VsZCBiZSBhIHNp bXBsZSBmZWF0dXJlLCBob3dldmVyIHdlIGRpZCBub3QgZmluZCBhbnkKPiBmaXR0aW5nIHNvbHV0 aW9uLgo+IFdlIHVzZSBYZW4gNC4yLjEgd2l0aCB4bCB0b29sc3RhY2suCj4gCj4gVGhlIGlkZWEg aXMgdG8gdXNlIGJhbGxvb25pbmcgdG8gZHluYW1pY2FsbHkgKGFuZCBhdXRvbWF0aWNhbGx5KSBj aGFuZ2UKPiBwaHlzaWNhbCBtZW1vcnkgYXZhaWxhYmxlIHRvIHRoZSBkb21VcyBhY2NvcmRpbmcg dG8gdGhlaXIgbWVtb3J5IG5lZWRzLgo+IFRoZXJlIHdhcyBzb21ldGhpbmcgY2FsbGVkICJ4ZW5i YWxsb29uZCIgZm9yIGxpbnV4IGd1ZXN0cyBiZWZvcmUgInRtZW0iCj4gd2FzIGludGVncmF0ZWQs IGFuZCB0aGlzIHNlZW1zIHRvIGJlIGV4YWN0bHkgd2hhdCB3ZSdyZSBsb29raW5nIGZvciwKPiBl eGNlcHQgdGhhdCB3ZSBuZWVkIGl0IGZvciB3aW5kb3dzIGRvbVVzLgo+IAo+IElzIHRoZXJlIHJl YWxseSBubyBzdWNoIHRoaW5nIGZvciB3aW5kb3dzIGd1ZXN0cywgb3IgYXJlIHdlIGp1c3QgdG9v IHN0dXBpZCB0byBmaW5kIGl0Pwo+IFdlIHdvdWxkIGJlIGhhcHB5IGFib3V0IGFueSBoaW50cy4K PiAKPiBJZiB0aGVyZSByZWFsbHkgaXMgbm9uZSwgdGhlbiwgaXMgdGhlcmUgYSByZWFzb24gZm9y IHRoYXQ/Cj4gCj4gSXQgc2VlbXMgbGlrZSBhIHNpbXBsZSB0aGluZzoKPiAtIHN0YXJ0IGEgcHJv Y2VzcyBvbiBlYWNoIHdpbmRvd3MgZ3Vlc3QgdG8gbW9uaXRvciBtZW1vcnkgdXNhZ2UKPiAtIGlm IHRoZXJlIGlzIHNwYXJlIG1lbW9yeSAtPiB0ZWxsIHRoZSBoeXBlcnZpc29yIHRvIGxvd2VyIHRo ZSBtZW0tdGFyZ2V0Cj4gLSBpZiBtZW1vcnkgaXMgdXNlZCB1cCwgZGVjaWRlIHVwb24gQ1BVIHVz YWdlIGFuZCBtZW0gaGlzdG9yeToKPiAgIC4gaWRsZSBmb3Igc29tZSB0aW1lIC0+IHRyeSB0byBm cmVlIGJ1ZmZlcnMgYnkgYWxsb2NhdGluZyBhbmQgZnJlZWluZyBibG9ja3MKPiAgIC4gbG9hZGVk IC0+IGRvIG5vdGhpbmcgb3IgaW5jcmVhc2UgbWVtLXRhcmdldCwgYWNjb3JkaW5nIHRvIHBhZ2Vm aWxlIHVzYWdlCj4gICAuIHJlY2VudGx5IGluY3JlYXNlZCAtPiBpbmNyZWFzZSBtZW0tdGFyZ2V0 Cj4gLSBJZiBtZW1vcnkgaXMgbmVlZGVkIHF1aWNrbHksIHRoZSBwYWdlZmlsZSB3aWxsIGJlIHVz ZWQgdGVtcG9yYXJpbHkuCj4gLSBJbiBhIHRyaXZpYWwgaW1wbGVtZW50YXRpb24sIGEgc2ltcGxl IHNjcmlwdCBvbiBkb20wIGNvdWxkIHJlY2VpdmUKPiAgIHRoZSBtZW0tdGFyZ2V0IHJlcXVlc3Rz IGFuZCBkbyB0aGUgYWN0dWFsICJ4bCBtZW0tc2V0IiBjYWxscwo+ICAgKGFjY29yZGluZyB0byBz b21lIGJhbGFuY2luZyBhbGdvcml0aG0pLgo+IAo+IE9yIGlzIHRoaXMgYXBwcm9hY2gganVzdCB0 b28gbmFpdmU/Cj4gCj4gSW4gb3VyIHNjZW5hcmlvICh2aXJ0dWFsIGRlc2t0b3BzIGFuZCB0ZXN0 c2VydmVycykgdGhlcmUgYXJlIGFsd2F5cyBpZGxlCj4gZ3Vlc3RzIHdhc3RpbmcgbWVtb3J5IGFu ZCBub3QgcmVhbGx5IHVzaW5nIGl0LiBJIHN1cHBvc2UgdGhlcmUgbXVzdCBiZSBhCj4gd2F5IHRv IGF1dG9tYXRpY2FsbHkgKGlmIGp1c3Qgc2xvd2x5KSBzaGlmdCBtZW1vcnkgdG8gdGhvc2UgaW4g bmVlZCwgYW5kCj4gdGh1cyByZWR1Y2luZyBvdmVyYWxsIG1lbW9yeSByZXF1aXJlbWVudHMuCj4g Cj4geW91cnMsCj4gLSBwZXRlci4KPiAKPiAtLSAKPiBQZXRlciBHYW5zdGVyZXIKPiAKPiBQQVJB RElHTUEgVW50ZXJuZWhtZW5zYmVyYXR1bmcgR21iSAo+IE1hcmlhaGlsZmVyc3RyYcOfZSA0Ny8x LzMKPiBBLTEwNjAgV2llbgo+IFRlbDogMDA0My0oMCkxLTU4NSA0OSA3Mgo+IGh0dHA6Ly93d3cu cGFyYWRpZ21hLm5ldAo+IAo+IEZpcm1lbmJ1Y2hudW1tZXI6IEZOIDEzNDU2NCBwCj4gUmVjaHRz Zm9ybTogR21iSAo+IEZpcm1lbmJ1Y2hnZXJpY2h0OiBIYW5kZWxzZ2VyaWNodCBXaWVuCgpfX19f X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXwpYZW4tdXNlcnMgbWFp bGluZyBsaXN0Clhlbi11c2Vyc0BsaXN0cy54ZW4ub3JnCmh0dHA6Ly9saXN0cy54ZW4ub3JnL3hl bi11c2Vycw== From xen-users-bounces@lists.xen.org Sun Feb 10 11:23:58 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sun, 10 Feb 2013 11: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 1U4Uyy-0000sH-KS; Sun, 10 Feb 2013 11:22:04 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U4Uyw-0000sC-Mn for xen-users@lists.xen.org; Sun, 10 Feb 2013 11:22:02 +0000 Received: from [85.158.139.83:39041] by server-5.bemta-5.messagelabs.com id 74/9A-11945-9D287115; Sun, 10 Feb 2013 11:22:01 +0000 X-Env-Sender: peter.gansterer@paradigma.net X-Msg-Ref: server-11.tower-182.messagelabs.com!1360495320!20727072!1 X-Originating-IP: [213.47.215.227] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 17737 invoked from network); 10 Feb 2013 11:22:01 -0000 Received: from majere.luchs.at (HELO majere.luchs.at) (213.47.215.227) by server-11.tower-182.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 10 Feb 2013 11:22:01 -0000 Received: from localhost (localhost [127.0.0.1]) by majere.luchs.at (Postfix) with ESMTP id 8C39CD007E28 for ; Sun, 10 Feb 2013 12:21:59 +0100 (CET) X-Virus-Scanned: by majere.luchs.at Received: from majere.luchs.at ([127.0.0.1]) by localhost (majere.luchs.at [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5JEnR0wRzLqG for ; Sun, 10 Feb 2013 12:21:58 +0100 (CET) Received: from earth (earth.elements.lan [10.0.0.2]) by majere.luchs.at (Postfix) with ESMTP id 1FBB1D007E21 for ; Sun, 10 Feb 2013 12:21:58 +0100 (CET) Received: from pedos (pedos.elements.lan [10.0.0.108]) by earth (Postfix) with SMTP id 80C793E22D for ; Sun, 10 Feb 2013 12:21:56 +0100 (CET) Received: by pedos (sSMTP sendmail emulation); Sun, 10 Feb 2013 12:20:06 +0100 Content-Disposition: inline MIME-Version: 1.0 X-Mailer: MIME-tools 5.503 (Entity 5.503) Message-ID: <1360494858.301F0a21.2491@pedos> From: "Peter Gansterer" Date: Sun, 10 Feb 2013 12:20:04 +0100 In-Reply-To: <1360255718.EBA4d10.2491@pedos> To: "xen-users" Subject: Re: [Xen-users] "dynamic memory allocation" for windows guests? X-BeenThere: xen-users@lists.xen.org X-Mailman-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 SGkgYWdhaW4sCgpBcmUgdGhlcmUgcmVhbGx5IG5vIGhpbnRzIGFib3V0IHRoaXMgdG9waWM/CgpJ dCB3b3VsZCBhbHNvIGJlIHVzZWZ1bCB0byBkZWZpbml0ZWx5IGtub3cgdGhlcmUgaXMgbm8gc29s dXRpb24gZm9yIHdoYXQgd2UgYXJlIGxvb2tpbmcgZm9yIC0gb3IgZXZlbiBpbnB1dCBhcyB0byB3 aHkgdGhpcyB3b3VsZG4ndCB3b3JrLgpPdGhlcndpc2Ugd2UnZCB0aGluayBhYm91dCB0cnlpbmcg aXQgb24gb3VyIG93bi4KCi0gcGVkYS4KCgpPbiAyMDEzLTAyLTA3IDE4OjM3OjE2LjQ4MTQxNiBQ ZXRlciBHYW5zdGVyZXIgd3JvdGU6Cj4gSGVsbG8sCj4gCj4gSW4gb3VyIG9mZmljZSB3ZSB3b3Vs ZCBsaWtlIHRvIGRvIHNvbWV0aGluZyBsaWtlICJtZW1vcnkgb3ZlcmNvbW1pdG1lbnQiCj4gb3Ig cmF0aGVyICJkeW5hbWljIGFsbG9jYXRpb24iIGZvciBhIGJ1bmNoIG9mIHdpbmRvd3MgZG9tVXMg KHNlcnZlciAyMDAzICYgMjAwOCkuCj4gCj4gV2UgdGhvdWdodCB0aGlzIHNob3VsZCBiZSBhIHNp bXBsZSBmZWF0dXJlLCBob3dldmVyIHdlIGRpZCBub3QgZmluZCBhbnkKPiBmaXR0aW5nIHNvbHV0 aW9uLgo+IFdlIHVzZSBYZW4gNC4yLjEgd2l0aCB4bCB0b29sc3RhY2suCj4gCj4gVGhlIGlkZWEg aXMgdG8gdXNlIGJhbGxvb25pbmcgdG8gZHluYW1pY2FsbHkgKGFuZCBhdXRvbWF0aWNhbGx5KSBj aGFuZ2UKPiBwaHlzaWNhbCBtZW1vcnkgYXZhaWxhYmxlIHRvIHRoZSBkb21VcyBhY2NvcmRpbmcg dG8gdGhlaXIgbWVtb3J5IG5lZWRzLgo+IFRoZXJlIHdhcyBzb21ldGhpbmcgY2FsbGVkICJ4ZW5i YWxsb29uZCIgZm9yIGxpbnV4IGd1ZXN0cyBiZWZvcmUgInRtZW0iCj4gd2FzIGludGVncmF0ZWQs IGFuZCB0aGlzIHNlZW1zIHRvIGJlIGV4YWN0bHkgd2hhdCB3ZSdyZSBsb29raW5nIGZvciwKPiBl eGNlcHQgdGhhdCB3ZSBuZWVkIGl0IGZvciB3aW5kb3dzIGRvbVVzLgo+IAo+IElzIHRoZXJlIHJl YWxseSBubyBzdWNoIHRoaW5nIGZvciB3aW5kb3dzIGd1ZXN0cywgb3IgYXJlIHdlIGp1c3QgdG9v IHN0dXBpZCB0byBmaW5kIGl0Pwo+IFdlIHdvdWxkIGJlIGhhcHB5IGFib3V0IGFueSBoaW50cy4K PiAKPiBJZiB0aGVyZSByZWFsbHkgaXMgbm9uZSwgdGhlbiwgaXMgdGhlcmUgYSByZWFzb24gZm9y IHRoYXQ/Cj4gCj4gSXQgc2VlbXMgbGlrZSBhIHNpbXBsZSB0aGluZzoKPiAtIHN0YXJ0IGEgcHJv Y2VzcyBvbiBlYWNoIHdpbmRvd3MgZ3Vlc3QgdG8gbW9uaXRvciBtZW1vcnkgdXNhZ2UKPiAtIGlm IHRoZXJlIGlzIHNwYXJlIG1lbW9yeSAtPiB0ZWxsIHRoZSBoeXBlcnZpc29yIHRvIGxvd2VyIHRo ZSBtZW0tdGFyZ2V0Cj4gLSBpZiBtZW1vcnkgaXMgdXNlZCB1cCwgZGVjaWRlIHVwb24gQ1BVIHVz YWdlIGFuZCBtZW0gaGlzdG9yeToKPiAgIC4gaWRsZSBmb3Igc29tZSB0aW1lIC0+IHRyeSB0byBm cmVlIGJ1ZmZlcnMgYnkgYWxsb2NhdGluZyBhbmQgZnJlZWluZyBibG9ja3MKPiAgIC4gbG9hZGVk IC0+IGRvIG5vdGhpbmcgb3IgaW5jcmVhc2UgbWVtLXRhcmdldCwgYWNjb3JkaW5nIHRvIHBhZ2Vm aWxlIHVzYWdlCj4gICAuIHJlY2VudGx5IGluY3JlYXNlZCAtPiBpbmNyZWFzZSBtZW0tdGFyZ2V0 Cj4gLSBJZiBtZW1vcnkgaXMgbmVlZGVkIHF1aWNrbHksIHRoZSBwYWdlZmlsZSB3aWxsIGJlIHVz ZWQgdGVtcG9yYXJpbHkuCj4gLSBJbiBhIHRyaXZpYWwgaW1wbGVtZW50YXRpb24sIGEgc2ltcGxl IHNjcmlwdCBvbiBkb20wIGNvdWxkIHJlY2VpdmUKPiAgIHRoZSBtZW0tdGFyZ2V0IHJlcXVlc3Rz IGFuZCBkbyB0aGUgYWN0dWFsICJ4bCBtZW0tc2V0IiBjYWxscwo+ICAgKGFjY29yZGluZyB0byBz b21lIGJhbGFuY2luZyBhbGdvcml0aG0pLgo+IAo+IE9yIGlzIHRoaXMgYXBwcm9hY2gganVzdCB0 b28gbmFpdmU/Cj4gCj4gSW4gb3VyIHNjZW5hcmlvICh2aXJ0dWFsIGRlc2t0b3BzIGFuZCB0ZXN0 c2VydmVycykgdGhlcmUgYXJlIGFsd2F5cyBpZGxlCj4gZ3Vlc3RzIHdhc3RpbmcgbWVtb3J5IGFu ZCBub3QgcmVhbGx5IHVzaW5nIGl0LiBJIHN1cHBvc2UgdGhlcmUgbXVzdCBiZSBhCj4gd2F5IHRv IGF1dG9tYXRpY2FsbHkgKGlmIGp1c3Qgc2xvd2x5KSBzaGlmdCBtZW1vcnkgdG8gdGhvc2UgaW4g bmVlZCwgYW5kCj4gdGh1cyByZWR1Y2luZyBvdmVyYWxsIG1lbW9yeSByZXF1aXJlbWVudHMuCj4g Cj4geW91cnMsCj4gLSBwZXRlci4KPiAKPiAtLSAKPiBQZXRlciBHYW5zdGVyZXIKPiAKPiBQQVJB RElHTUEgVW50ZXJuZWhtZW5zYmVyYXR1bmcgR21iSAo+IE1hcmlhaGlsZmVyc3RyYcOfZSA0Ny8x LzMKPiBBLTEwNjAgV2llbgo+IFRlbDogMDA0My0oMCkxLTU4NSA0OSA3Mgo+IGh0dHA6Ly93d3cu cGFyYWRpZ21hLm5ldAo+IAo+IEZpcm1lbmJ1Y2hudW1tZXI6IEZOIDEzNDU2NCBwCj4gUmVjaHRz Zm9ybTogR21iSAo+IEZpcm1lbmJ1Y2hnZXJpY2h0OiBIYW5kZWxzZ2VyaWNodCBXaWVuCgpfX19f X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXwpYZW4tdXNlcnMgbWFp bGluZyBsaXN0Clhlbi11c2Vyc0BsaXN0cy54ZW4ub3JnCmh0dHA6Ly9saXN0cy54ZW4ub3JnL3hl bi11c2Vycw== From xen-users-bounces@lists.xen.org Sun Feb 10 12:19:40 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sun, 10 Feb 2013 12:19: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 1U4Vr3-0002Av-1U; Sun, 10 Feb 2013 12:17:57 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U4Vr1-0002Aq-8Y for xen-users@lists.xen.org; Sun, 10 Feb 2013 12:17:55 +0000 Received: from [85.158.139.211:24771] by server-7.bemta-5.messagelabs.com id D6/FA-11121-2FF87115; Sun, 10 Feb 2013 12:17:54 +0000 X-Env-Sender: peter.gansterer@paradigma.net X-Msg-Ref: server-10.tower-206.messagelabs.com!1360498673!19069471!1 X-Originating-IP: [213.47.215.227] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 26593 invoked from network); 10 Feb 2013 12:17:53 -0000 Received: from majere.luchs.at (HELO majere.luchs.at) (213.47.215.227) by server-10.tower-206.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 10 Feb 2013 12:17:53 -0000 Received: from localhost (localhost [127.0.0.1]) by majere.luchs.at (Postfix) with ESMTP id 115B9D007E28 for ; Sun, 10 Feb 2013 13:17:53 +0100 (CET) X-Virus-Scanned: by majere.luchs.at Received: from majere.luchs.at ([127.0.0.1]) by localhost (majere.luchs.at [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id h9TqvxBIUxnY for ; Sun, 10 Feb 2013 13:17:51 +0100 (CET) Received: from earth (earth.elements.lan [10.0.0.2]) by majere.luchs.at (Postfix) with ESMTP id 98A14D007E21 for ; Sun, 10 Feb 2013 13:17:51 +0100 (CET) Received: from pedos (pedos.elements.lan [10.0.0.108]) by earth (Postfix) with SMTP id 41D7B3E453 for ; Sun, 10 Feb 2013 13:17:50 +0100 (CET) Received: by pedos (sSMTP sendmail emulation); Sun, 10 Feb 2013 13:16:00 +0100 Content-Disposition: inline MIME-Version: 1.0 X-Mailer: MIME-tools 5.503 (Entity 5.503) Message-ID: <1360495896.0CCE0aE22.2491@pedos> From: "Peter Gansterer" Date: Sun, 10 Feb 2013 13:15:50 +0100 To: "xen-users" Subject: [Xen-users] Problem using PoD on Xen 4.2.1 (win domU 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: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org SGksCgpJbiBzaG9ydDoKV2luZG93cyBkb21VIGRvZXNuJ3Qgc2hvdyBhbnkgYmFsbG9vbmVkIG1l bW9yeSBhbmQgZmluYWxseSBjcmFzaGVzICgib3V0IG9mIFBvRCBtZW1vcnkiKSB3aGVuICJzdGFy dGluZyBiYWxsb29uZWQiLgoKV2UgdGVzdGVkIG9uIDIgZGlmZmVyZW50IGhvc3RzIGFuZCB3aW5k b3dzIGd1ZXN0czoKICBXaW5kb3dzIFNlcnZlciAyMDA4IFIyIGFuZCAyMDAzLgogIFhlbiA0LjIu MSBvbiBnZW50b28sIGRvbTAga2VybmVsczogMy43LngKICBzaWduZWQgZ3BscHYgZHJpdmVycyBm cm9tIHVuaXZlbnRpb24uCgpXaGVuIGNvbmZpZ3VyZWQgdG8gc3RhcnQgYmFsbG9vbmVkIChlZy4g bWVtPTFHQiwgbWF4PTRHQikKd2Ugc2VlIHRoZSBmb2xsb3dpbmcgYmVoYXZpb3VyOgoKLSAieGwg bGlzdCIgc2F5cywgdGhlIGd1ZXN0IHVzZXMgMUdCIG9mIG1lbW9yeQotIHdpbmRvd3Mgc2hvd3Mg NEdCIHBoeXNpY2FsIG1lbW9yeSAoYXMgZXhwZWN0ZWQpCi0gYnV0IHdpbmRvd3Mgc2hvd3Mgbm8g c2lnbiBvZiBhIGJhbGxvb24gKGllOiBhbGwgNEdCIGlzIGZyZWUpCi0gd2UgYXJlIGFibGUgdG8g ZWF0IGFsbCB0aGUgNEdCIHdpdGhvdXQgcGFnaW5nLgotICJ4bCBsaXN0IiBkb2Vzbid0IG5vdGlj ZSBhbnkgY2hhbmdlcyAoYWx3YXlzIHN0YXlzIGF0IDFHQikuCi0gSWYgd2UgdHJ5IHRvIGFsbG9j YXRlIGFib3ZlIHBoeXNpY2FsIG1lbW9yeSBvZiB0aGUgaG9zdCwgdGhlIGRvbVUganVzdCBjcmFz aGVzOgogIChYRU4pIHAybV9wb2RfZGVtYW5kX3BvcHVsYXRlOiBEb20zIG91dCBvZiBQb0QgbWVt b3J5ISAodG90PTEzMTA2NCBlbnRzPTE5NjU1MzYgZG9tMykKICAoWEVOKSBkb21haW5fY3Jhc2gg Y2FsbGVkIGZyb20gcDJtLXBvZC5jOjEwNzcKCldlIGRpZG4ndCBzdGFydCBiYWxsb29uZWQgd2lu ZG93cyBkb21VcyBiZWZvcmUsIHNvIHdlJ3JlIG5vdCBleGFjdGx5IHN1cmUgb24gaG93IGl0IHNo b3VsZCBiZWhhdmUgKGV4cGVjdGVkIHRvIHNlZSB0aGUgImJhbGxvb25lZCByZWdpb24iIHJpZ2h0 IGFmdGVyIGJvb3Rpbmcgd2luZG93czsgYW5kIGNlcnRhaW5seSBubyBjcmFzaGVzIDotKSkuCgpJ cyB0aGlzIGEgYnVnIGluIHRoaXMgc3BlY2lhbCBjb21iaW5hdGlvbiBvZiBjb21wb25lbnRzLCBv ciBkaWQgd2UgbWVzcyB1cCB3aXRoIG91ciBjb25maWd1cmF0aW9uPwoKZG9tVSBDb25maWc6Ci0t LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLQpidWlsZGVyID0gImh2bSIKbmFtZSA9ICJ3aW4y MDA4Igp2aXJpZGlhbiA9IDEKbWVtb3J5ID0gMTAyNAptYXhtZW0gPSA0MDk2CnZjcHVzID0gMgp2 aWYgPSBbICdicmlkZ2U9eGVuYnIwLCBtYWM9MDA6MTg6NGU6ZmE6YWI6MTMsIG1vZGVsPWUxMDAw JyAgXQpkaXNrID0gWyAncGh5Oi9kZXYvc2RhMyxoZGEscncnIF0Kdm5jID0xCnZuY2xpc3Rlbj0i MTI3LjAuMC4xIgp2bmNwYXNzd2Q9InRlc3QiCnN0ZHZnYSA9IDEKdmlkZW9yYW0gPSA4IAphY3Bp ID0gMQphcGljID0gMQp1c2IgPSAxCnVzYmRldmljZSA9ICJ0YWJsZXQiCnNlcmlhbD0ncHR5Jwp4 ZW5fcGxhdGZvcm1fcGNpPTEKLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tCgp5b3VycywK LSBwZXRlcgoKCi0tIApQZXRlciBHYW5zdGVyZXIKClBBUkFESUdNQSBVbnRlcm5laG1lbnNiZXJh dHVuZyBHbWJICk1hcmlhaGlsZmVyc3RyYcOfZSA0Ny8xLzMKQS0xMDYwIFdpZW4KVGVsOiAwMDQz LSgwKTEtNTg1IDQ5IDcyCmh0dHA6Ly93d3cucGFyYWRpZ21hLm5ldAoKRmlybWVuYnVjaG51bW1l cjogRk4gMTM0NTY0IHAKUmVjaHRzZm9ybTogR21iSApGaXJtZW5idWNoZ2VyaWNodDogSGFuZGVs c2dlcmljaHQgV2llbgoKX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f X19fX18KWGVuLXVzZXJzIG1haWxpbmcgbGlzdApYZW4tdXNlcnNAbGlzdHMueGVuLm9yZwpodHRw Oi8vbGlzdHMueGVuLm9yZy94ZW4tdXNlcnM= From xen-users-bounces@lists.xen.org Sun Feb 10 12:19:40 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sun, 10 Feb 2013 12:19: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 1U4Vr3-0002Av-1U; Sun, 10 Feb 2013 12:17:57 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U4Vr1-0002Aq-8Y for xen-users@lists.xen.org; Sun, 10 Feb 2013 12:17:55 +0000 Received: from [85.158.139.211:24771] by server-7.bemta-5.messagelabs.com id D6/FA-11121-2FF87115; Sun, 10 Feb 2013 12:17:54 +0000 X-Env-Sender: peter.gansterer@paradigma.net X-Msg-Ref: server-10.tower-206.messagelabs.com!1360498673!19069471!1 X-Originating-IP: [213.47.215.227] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 26593 invoked from network); 10 Feb 2013 12:17:53 -0000 Received: from majere.luchs.at (HELO majere.luchs.at) (213.47.215.227) by server-10.tower-206.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 10 Feb 2013 12:17:53 -0000 Received: from localhost (localhost [127.0.0.1]) by majere.luchs.at (Postfix) with ESMTP id 115B9D007E28 for ; Sun, 10 Feb 2013 13:17:53 +0100 (CET) X-Virus-Scanned: by majere.luchs.at Received: from majere.luchs.at ([127.0.0.1]) by localhost (majere.luchs.at [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id h9TqvxBIUxnY for ; Sun, 10 Feb 2013 13:17:51 +0100 (CET) Received: from earth (earth.elements.lan [10.0.0.2]) by majere.luchs.at (Postfix) with ESMTP id 98A14D007E21 for ; Sun, 10 Feb 2013 13:17:51 +0100 (CET) Received: from pedos (pedos.elements.lan [10.0.0.108]) by earth (Postfix) with SMTP id 41D7B3E453 for ; Sun, 10 Feb 2013 13:17:50 +0100 (CET) Received: by pedos (sSMTP sendmail emulation); Sun, 10 Feb 2013 13:16:00 +0100 Content-Disposition: inline MIME-Version: 1.0 X-Mailer: MIME-tools 5.503 (Entity 5.503) Message-ID: <1360495896.0CCE0aE22.2491@pedos> From: "Peter Gansterer" Date: Sun, 10 Feb 2013 13:15:50 +0100 To: "xen-users" Subject: [Xen-users] Problem using PoD on Xen 4.2.1 (win domU 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: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org SGksCgpJbiBzaG9ydDoKV2luZG93cyBkb21VIGRvZXNuJ3Qgc2hvdyBhbnkgYmFsbG9vbmVkIG1l bW9yeSBhbmQgZmluYWxseSBjcmFzaGVzICgib3V0IG9mIFBvRCBtZW1vcnkiKSB3aGVuICJzdGFy dGluZyBiYWxsb29uZWQiLgoKV2UgdGVzdGVkIG9uIDIgZGlmZmVyZW50IGhvc3RzIGFuZCB3aW5k b3dzIGd1ZXN0czoKICBXaW5kb3dzIFNlcnZlciAyMDA4IFIyIGFuZCAyMDAzLgogIFhlbiA0LjIu MSBvbiBnZW50b28sIGRvbTAga2VybmVsczogMy43LngKICBzaWduZWQgZ3BscHYgZHJpdmVycyBm cm9tIHVuaXZlbnRpb24uCgpXaGVuIGNvbmZpZ3VyZWQgdG8gc3RhcnQgYmFsbG9vbmVkIChlZy4g bWVtPTFHQiwgbWF4PTRHQikKd2Ugc2VlIHRoZSBmb2xsb3dpbmcgYmVoYXZpb3VyOgoKLSAieGwg bGlzdCIgc2F5cywgdGhlIGd1ZXN0IHVzZXMgMUdCIG9mIG1lbW9yeQotIHdpbmRvd3Mgc2hvd3Mg NEdCIHBoeXNpY2FsIG1lbW9yeSAoYXMgZXhwZWN0ZWQpCi0gYnV0IHdpbmRvd3Mgc2hvd3Mgbm8g c2lnbiBvZiBhIGJhbGxvb24gKGllOiBhbGwgNEdCIGlzIGZyZWUpCi0gd2UgYXJlIGFibGUgdG8g ZWF0IGFsbCB0aGUgNEdCIHdpdGhvdXQgcGFnaW5nLgotICJ4bCBsaXN0IiBkb2Vzbid0IG5vdGlj ZSBhbnkgY2hhbmdlcyAoYWx3YXlzIHN0YXlzIGF0IDFHQikuCi0gSWYgd2UgdHJ5IHRvIGFsbG9j YXRlIGFib3ZlIHBoeXNpY2FsIG1lbW9yeSBvZiB0aGUgaG9zdCwgdGhlIGRvbVUganVzdCBjcmFz aGVzOgogIChYRU4pIHAybV9wb2RfZGVtYW5kX3BvcHVsYXRlOiBEb20zIG91dCBvZiBQb0QgbWVt b3J5ISAodG90PTEzMTA2NCBlbnRzPTE5NjU1MzYgZG9tMykKICAoWEVOKSBkb21haW5fY3Jhc2gg Y2FsbGVkIGZyb20gcDJtLXBvZC5jOjEwNzcKCldlIGRpZG4ndCBzdGFydCBiYWxsb29uZWQgd2lu ZG93cyBkb21VcyBiZWZvcmUsIHNvIHdlJ3JlIG5vdCBleGFjdGx5IHN1cmUgb24gaG93IGl0IHNo b3VsZCBiZWhhdmUgKGV4cGVjdGVkIHRvIHNlZSB0aGUgImJhbGxvb25lZCByZWdpb24iIHJpZ2h0 IGFmdGVyIGJvb3Rpbmcgd2luZG93czsgYW5kIGNlcnRhaW5seSBubyBjcmFzaGVzIDotKSkuCgpJ cyB0aGlzIGEgYnVnIGluIHRoaXMgc3BlY2lhbCBjb21iaW5hdGlvbiBvZiBjb21wb25lbnRzLCBv ciBkaWQgd2UgbWVzcyB1cCB3aXRoIG91ciBjb25maWd1cmF0aW9uPwoKZG9tVSBDb25maWc6Ci0t LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLQpidWlsZGVyID0gImh2bSIKbmFtZSA9ICJ3aW4y MDA4Igp2aXJpZGlhbiA9IDEKbWVtb3J5ID0gMTAyNAptYXhtZW0gPSA0MDk2CnZjcHVzID0gMgp2 aWYgPSBbICdicmlkZ2U9eGVuYnIwLCBtYWM9MDA6MTg6NGU6ZmE6YWI6MTMsIG1vZGVsPWUxMDAw JyAgXQpkaXNrID0gWyAncGh5Oi9kZXYvc2RhMyxoZGEscncnIF0Kdm5jID0xCnZuY2xpc3Rlbj0i MTI3LjAuMC4xIgp2bmNwYXNzd2Q9InRlc3QiCnN0ZHZnYSA9IDEKdmlkZW9yYW0gPSA4IAphY3Bp ID0gMQphcGljID0gMQp1c2IgPSAxCnVzYmRldmljZSA9ICJ0YWJsZXQiCnNlcmlhbD0ncHR5Jwp4 ZW5fcGxhdGZvcm1fcGNpPTEKLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tCgp5b3VycywK LSBwZXRlcgoKCi0tIApQZXRlciBHYW5zdGVyZXIKClBBUkFESUdNQSBVbnRlcm5laG1lbnNiZXJh dHVuZyBHbWJICk1hcmlhaGlsZmVyc3RyYcOfZSA0Ny8xLzMKQS0xMDYwIFdpZW4KVGVsOiAwMDQz LSgwKTEtNTg1IDQ5IDcyCmh0dHA6Ly93d3cucGFyYWRpZ21hLm5ldAoKRmlybWVuYnVjaG51bW1l cjogRk4gMTM0NTY0IHAKUmVjaHRzZm9ybTogR21iSApGaXJtZW5idWNoZ2VyaWNodDogSGFuZGVs c2dlcmljaHQgV2llbgoKX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f X19fX18KWGVuLXVzZXJzIG1haWxpbmcgbGlzdApYZW4tdXNlcnNAbGlzdHMueGVuLm9yZwpodHRw Oi8vbGlzdHMueGVuLm9yZy94ZW4tdXNlcnM= From xen-users-bounces@lists.xen.org Sun Feb 10 13:00:39 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sun, 10 Feb 2013 13:00: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 1U4WUr-0003BZ-Ol; Sun, 10 Feb 2013 12:59:05 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U4WUq-0003BU-IX for xen-users@lists.xen.org; Sun, 10 Feb 2013 12:59:04 +0000 Received: from [85.158.139.83:34016] by server-7.bemta-5.messagelabs.com id 9A/C8-11121-79997115; Sun, 10 Feb 2013 12:59:03 +0000 X-Env-Sender: pigeon@pigeond.net X-Msg-Ref: server-8.tower-182.messagelabs.com!1360501141!20363085!1 X-Originating-IP: [203.59.1.226] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogMjAzLjU5LjEuMjI2ID0+IDE0NTcz\n X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 11058 invoked from network); 10 Feb 2013 12:59:02 -0000 Received: from icp-osb-irony-out9.external.iinet.net.au (HELO icp-osb-irony-out9.external.iinet.net.au) (203.59.1.226) by server-8.tower-182.messagelabs.com with SMTP; 10 Feb 2013 12:59:02 -0000 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: Av0EAOOYF1F8lWUl/2dsb2JhbABFwRIWc4JgZxQ0OgGIN55FoDOOYIMqA5YjhhSKQIMa X-IronPort-AV: E=Sophos;i="4.84,637,1355068800"; d="scan'208";a="84136925" Received: from unknown (HELO torankusu.pigeond.net) ([124.149.101.37]) by icp-osb-irony-out9.iinet.net.au with ESMTP; 10 Feb 2013 20:58:59 +0800 Received: from furiza.pigeond.net ([192.168.42.20]:44928 helo=pigeond.net) by torankusu.pigeond.net with esmtp (Exim 4.72) (envelope-from ) id 1U4WUk-0007Ja-M5 for xen-users@lists.xen.org; Sun, 10 Feb 2013 23:58:58 +1100 Date: Sun, 10 Feb 2013 23:58:53 +1100 From: Howell Tam To: xen-users@lists.xen.org Message-ID: <20130210235853.4ebb70b8@pigeond.net> Organization: pigeond.net X-Mailer: Claws Mail 3.8.1 (GTK+ 2.24.10; x86_64-pc-linux-gnu) Mime-Version: 1.0 Subject: [Xen-users] Dom0 freeze on HVM DomU Windows reboot with 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 Hi, I'm doing VGA passthrough for an ATI (HD 6770) graphics card to a DomU Windows. The passthrough itself is working. However, everytime when I reboot the DomU Windows, the whole machine freezes. I see no error messages from Dom0 kernel or the xen qemu log (or perhaps I haven't got the most verbose debugging turned on?). Though from what I can tell, the the freeze happens when DomU starts again, not the shutdown. Is there any pointers on how I could debug this? Xen 4.2.1, Dom0 is Linux 3.2.36, with xl passthrough. I have tried both WinXP and Win7 and both shows the same result. Thanks! -- Regards, Howell. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Sun Feb 10 13:00:39 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sun, 10 Feb 2013 13:00: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 1U4WUr-0003BZ-Ol; Sun, 10 Feb 2013 12:59:05 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U4WUq-0003BU-IX for xen-users@lists.xen.org; Sun, 10 Feb 2013 12:59:04 +0000 Received: from [85.158.139.83:34016] by server-7.bemta-5.messagelabs.com id 9A/C8-11121-79997115; Sun, 10 Feb 2013 12:59:03 +0000 X-Env-Sender: pigeon@pigeond.net X-Msg-Ref: server-8.tower-182.messagelabs.com!1360501141!20363085!1 X-Originating-IP: [203.59.1.226] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogMjAzLjU5LjEuMjI2ID0+IDE0NTcz\n X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 11058 invoked from network); 10 Feb 2013 12:59:02 -0000 Received: from icp-osb-irony-out9.external.iinet.net.au (HELO icp-osb-irony-out9.external.iinet.net.au) (203.59.1.226) by server-8.tower-182.messagelabs.com with SMTP; 10 Feb 2013 12:59:02 -0000 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: Av0EAOOYF1F8lWUl/2dsb2JhbABFwRIWc4JgZxQ0OgGIN55FoDOOYIMqA5YjhhSKQIMa X-IronPort-AV: E=Sophos;i="4.84,637,1355068800"; d="scan'208";a="84136925" Received: from unknown (HELO torankusu.pigeond.net) ([124.149.101.37]) by icp-osb-irony-out9.iinet.net.au with ESMTP; 10 Feb 2013 20:58:59 +0800 Received: from furiza.pigeond.net ([192.168.42.20]:44928 helo=pigeond.net) by torankusu.pigeond.net with esmtp (Exim 4.72) (envelope-from ) id 1U4WUk-0007Ja-M5 for xen-users@lists.xen.org; Sun, 10 Feb 2013 23:58:58 +1100 Date: Sun, 10 Feb 2013 23:58:53 +1100 From: Howell Tam To: xen-users@lists.xen.org Message-ID: <20130210235853.4ebb70b8@pigeond.net> Organization: pigeond.net X-Mailer: Claws Mail 3.8.1 (GTK+ 2.24.10; x86_64-pc-linux-gnu) Mime-Version: 1.0 Subject: [Xen-users] Dom0 freeze on HVM DomU Windows reboot with 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 Hi, I'm doing VGA passthrough for an ATI (HD 6770) graphics card to a DomU Windows. The passthrough itself is working. However, everytime when I reboot the DomU Windows, the whole machine freezes. I see no error messages from Dom0 kernel or the xen qemu log (or perhaps I haven't got the most verbose debugging turned on?). Though from what I can tell, the the freeze happens when DomU starts again, not the shutdown. Is there any pointers on how I could debug this? Xen 4.2.1, Dom0 is Linux 3.2.36, with xl passthrough. I have tried both WinXP and Win7 and both shows the same result. Thanks! -- Regards, Howell. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Sun Feb 10 13:15:11 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sun, 10 Feb 2013 13:15: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 1U4WjG-0003pq-FM; Sun, 10 Feb 2013 13:13:58 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U4WjE-0003pj-BA for xen-users@lists.xen.org; Sun, 10 Feb 2013 13:13:56 +0000 Received: from [85.158.139.83:7380] by server-1.bemta-5.messagelabs.com id FB/51-29263-31D97115; Sun, 10 Feb 2013 13:13:55 +0000 X-Env-Sender: mike.mcclurg@citrix.com X-Msg-Ref: server-6.tower-182.messagelabs.com!1360502033!24634515!1 X-Originating-IP: [66.165.176.89] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjYuMTY1LjE3Ni44OSA9PiAxOTc4NDM=\n X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 4964 invoked from network); 10 Feb 2013 13:13:54 -0000 Received: from smtp.citrix.com (HELO SMTP.CITRIX.COM) (66.165.176.89) by server-6.tower-182.messagelabs.com with RC4-SHA encrypted SMTP; 10 Feb 2013 13:13:54 -0000 X-IronPort-AV: E=Sophos;i="4.84,637,1355097600"; d="scan'208";a="6942032" Received: from accessns.citrite.net (HELO FTLPEX01CL03.citrite.net) ([10.9.154.239]) by FTLPIPO01.CITRIX.COM with ESMTP/TLS/AES128-SHA; 10 Feb 2013 13:13:53 +0000 Received: from ukmail1.uk.xensource.com (10.80.16.128) by smtprelay.citrix.com (10.13.107.80) with Microsoft SMTP Server id 14.2.318.1; Sun, 10 Feb 2013 08:13:53 -0500 Received: from gateway-1.uk.xensource.com ([10.80.16.66] helo=[192.168.0.6]) by ukmail1.uk.xensource.com with esmtp (Exim 4.69) (envelope-from ) id 1U4WjA-00013C-Ng; Sun, 10 Feb 2013 13:13:52 +0000 Message-ID: <51179D0F.90409@citrix.com> Date: Sun, 10 Feb 2013 13:13:51 +0000 From: Mike McClurg User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130106 Thunderbird/17.0.2 MIME-Version: 1.0 To: Peter Gansterer References: <1360494858.301F0a21.2491@pedos> In-Reply-To: <1360494858.301F0a21.2491@pedos> Cc: xen-users Subject: Re: [Xen-users] "dynamic memory allocation" for windows guests? X-BeenThere: xen-users@lists.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 10/02/13 11:20, Peter Gansterer wrote: > Hi again, > > Are there really no hints about this topic? > > It would also be useful to definitely know there is no solution for what we are looking for - or even input as to why this wouldn't work. > Otherwise we'd think about trying it on our own. You should look into the Xen Cloud Platform (XCP) [1], which has a feature called Dynamic Memory Control, or memory ballooning [2]. It requires you to install special PV drivers in your Windows guest. One of these drivers is a ballooning daemon, which allocates a range of memory from the guest OS, and then gives that memory back to Xen, which gives the physical memory backed by that memory region to other guests. See [2], "How do balloon drivers work and what is a memory balloon" for more details. Mike [1] http://wiki.xen.org/wiki/XCP_Overview [2] http://wiki.xen.org/wiki/Dynamic_Memory_Control _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Sun Feb 10 13:15:11 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sun, 10 Feb 2013 13:15: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 1U4WjG-0003pq-FM; Sun, 10 Feb 2013 13:13:58 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U4WjE-0003pj-BA for xen-users@lists.xen.org; Sun, 10 Feb 2013 13:13:56 +0000 Received: from [85.158.139.83:7380] by server-1.bemta-5.messagelabs.com id FB/51-29263-31D97115; Sun, 10 Feb 2013 13:13:55 +0000 X-Env-Sender: mike.mcclurg@citrix.com X-Msg-Ref: server-6.tower-182.messagelabs.com!1360502033!24634515!1 X-Originating-IP: [66.165.176.89] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjYuMTY1LjE3Ni44OSA9PiAxOTc4NDM=\n X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 4964 invoked from network); 10 Feb 2013 13:13:54 -0000 Received: from smtp.citrix.com (HELO SMTP.CITRIX.COM) (66.165.176.89) by server-6.tower-182.messagelabs.com with RC4-SHA encrypted SMTP; 10 Feb 2013 13:13:54 -0000 X-IronPort-AV: E=Sophos;i="4.84,637,1355097600"; d="scan'208";a="6942032" Received: from accessns.citrite.net (HELO FTLPEX01CL03.citrite.net) ([10.9.154.239]) by FTLPIPO01.CITRIX.COM with ESMTP/TLS/AES128-SHA; 10 Feb 2013 13:13:53 +0000 Received: from ukmail1.uk.xensource.com (10.80.16.128) by smtprelay.citrix.com (10.13.107.80) with Microsoft SMTP Server id 14.2.318.1; Sun, 10 Feb 2013 08:13:53 -0500 Received: from gateway-1.uk.xensource.com ([10.80.16.66] helo=[192.168.0.6]) by ukmail1.uk.xensource.com with esmtp (Exim 4.69) (envelope-from ) id 1U4WjA-00013C-Ng; Sun, 10 Feb 2013 13:13:52 +0000 Message-ID: <51179D0F.90409@citrix.com> Date: Sun, 10 Feb 2013 13:13:51 +0000 From: Mike McClurg User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130106 Thunderbird/17.0.2 MIME-Version: 1.0 To: Peter Gansterer References: <1360494858.301F0a21.2491@pedos> In-Reply-To: <1360494858.301F0a21.2491@pedos> Cc: xen-users Subject: Re: [Xen-users] "dynamic memory allocation" for windows guests? X-BeenThere: xen-users@lists.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 10/02/13 11:20, Peter Gansterer wrote: > Hi again, > > Are there really no hints about this topic? > > It would also be useful to definitely know there is no solution for what we are looking for - or even input as to why this wouldn't work. > Otherwise we'd think about trying it on our own. You should look into the Xen Cloud Platform (XCP) [1], which has a feature called Dynamic Memory Control, or memory ballooning [2]. It requires you to install special PV drivers in your Windows guest. One of these drivers is a ballooning daemon, which allocates a range of memory from the guest OS, and then gives that memory back to Xen, which gives the physical memory backed by that memory region to other guests. See [2], "How do balloon drivers work and what is a memory balloon" for more details. Mike [1] http://wiki.xen.org/wiki/XCP_Overview [2] http://wiki.xen.org/wiki/Dynamic_Memory_Control _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Sun Feb 10 13:47:22 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sun, 10 Feb 2013 13:47: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 1U4XER-0004k0-I4; Sun, 10 Feb 2013 13:46:11 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U4XEQ-0004jv-A1 for xen-users@lists.xen.org; Sun, 10 Feb 2013 13:46:10 +0000 Received: from [85.158.138.51:6922] by server-2.bemta-3.messagelabs.com id 16/42-25961-1A4A7115; Sun, 10 Feb 2013 13:46:09 +0000 X-Env-Sender: peter.gansterer@paradigma.net X-Msg-Ref: server-7.tower-174.messagelabs.com!1360503968!18590397!1 X-Originating-IP: [213.47.215.227] X-SpamReason: No, hits=0.5 required=7.0 tests=BODY_RANDOM_LONG X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 27116 invoked from network); 10 Feb 2013 13:46:08 -0000 Received: from majere.luchs.at (HELO majere.luchs.at) (213.47.215.227) by server-7.tower-174.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 10 Feb 2013 13:46:08 -0000 Received: from localhost (localhost [127.0.0.1]) by majere.luchs.at (Postfix) with ESMTP id 1BBDCD007E28; Sun, 10 Feb 2013 14:46:08 +0100 (CET) X-Virus-Scanned: by majere.luchs.at Received: from majere.luchs.at ([127.0.0.1]) by localhost (majere.luchs.at [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kjqH0AtiM4dC; Sun, 10 Feb 2013 14:46:06 +0100 (CET) Received: from earth (earth.elements.lan [10.0.0.2]) by majere.luchs.at (Postfix) with ESMTP id 5E1CCD007E21; Sun, 10 Feb 2013 14:46:06 +0100 (CET) Received: from pedos (pedos.elements.lan [10.0.0.108]) by earth (Postfix) with SMTP id CC4F23327; Sun, 10 Feb 2013 14:46:04 +0100 (CET) Received: by pedos (sSMTP sendmail emulation); Sun, 10 Feb 2013 14:44:14 +0100 Content-Disposition: inline MIME-Version: 1.0 X-Mailer: MIME-tools 5.503 (Entity 5.503) Message-ID: <1360502603.CDD80dB23.2491@pedos> From: "Peter Gansterer" Date: Sun, 10 Feb 2013 14:44:14 +0100 In-Reply-To: <51179D0F.90409@citrix.com> To: "Mike McClurg" Cc: xen-users Subject: Re: [Xen-users] "dynamic memory allocation" for windows guests? X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: 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 2013-02-10 13:13:51 Mike McClurg wrote: > On 10/02/13 11:20, Peter Gansterer wrote: > > Hi again, > > > > Are there really no hints about this topic? > > > > It would also be useful to definitely know there is no solution > > for what we are looking for - or even input as to why this wouldn't work. > > Otherwise we'd think about trying it on our own. > > You should look into the Xen Cloud Platform (XCP) [1], which has a > feature called Dynamic Memory Control, or memory ballooning [2]. It > requires you to install special PV drivers in your Windows guest. One of > these drivers is a ballooning daemon, which allocates a range of memory > from the guest OS, and then gives that memory back to Xen, which gives > the physical memory backed by that memory region to other guests. See > [2], "How do balloon drivers work and what is a memory balloon" for more > details. > > Mike > > [1] http://wiki.xen.org/wiki/XCP_Overview > [2] http://wiki.xen.org/wiki/Dynamic_Memory_Control Thx for the hint. I had a look at the docs; but from there it seems this is just an automatic way to distribute memory targets when starting or stopping guests. As long as guests don't change, memory config stays static. There is no hint, that memory targets are chosen according to the guests actual requirements. I don't like the idea of seting up an XCP system just to confirm that this is not what we're looking for. Maybe there is an XCP user on the list, who can tell me if DMC dynamically changes memory targets according to requirements in the domU (even if no machines are started or stopped)? - peter. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Sun Feb 10 13:47:22 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sun, 10 Feb 2013 13:47: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 1U4XER-0004k0-I4; Sun, 10 Feb 2013 13:46:11 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U4XEQ-0004jv-A1 for xen-users@lists.xen.org; Sun, 10 Feb 2013 13:46:10 +0000 Received: from [85.158.138.51:6922] by server-2.bemta-3.messagelabs.com id 16/42-25961-1A4A7115; Sun, 10 Feb 2013 13:46:09 +0000 X-Env-Sender: peter.gansterer@paradigma.net X-Msg-Ref: server-7.tower-174.messagelabs.com!1360503968!18590397!1 X-Originating-IP: [213.47.215.227] X-SpamReason: No, hits=0.5 required=7.0 tests=BODY_RANDOM_LONG X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 27116 invoked from network); 10 Feb 2013 13:46:08 -0000 Received: from majere.luchs.at (HELO majere.luchs.at) (213.47.215.227) by server-7.tower-174.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 10 Feb 2013 13:46:08 -0000 Received: from localhost (localhost [127.0.0.1]) by majere.luchs.at (Postfix) with ESMTP id 1BBDCD007E28; Sun, 10 Feb 2013 14:46:08 +0100 (CET) X-Virus-Scanned: by majere.luchs.at Received: from majere.luchs.at ([127.0.0.1]) by localhost (majere.luchs.at [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kjqH0AtiM4dC; Sun, 10 Feb 2013 14:46:06 +0100 (CET) Received: from earth (earth.elements.lan [10.0.0.2]) by majere.luchs.at (Postfix) with ESMTP id 5E1CCD007E21; Sun, 10 Feb 2013 14:46:06 +0100 (CET) Received: from pedos (pedos.elements.lan [10.0.0.108]) by earth (Postfix) with SMTP id CC4F23327; Sun, 10 Feb 2013 14:46:04 +0100 (CET) Received: by pedos (sSMTP sendmail emulation); Sun, 10 Feb 2013 14:44:14 +0100 Content-Disposition: inline MIME-Version: 1.0 X-Mailer: MIME-tools 5.503 (Entity 5.503) Message-ID: <1360502603.CDD80dB23.2491@pedos> From: "Peter Gansterer" Date: Sun, 10 Feb 2013 14:44:14 +0100 In-Reply-To: <51179D0F.90409@citrix.com> To: "Mike McClurg" Cc: xen-users Subject: Re: [Xen-users] "dynamic memory allocation" for windows guests? X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: 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 2013-02-10 13:13:51 Mike McClurg wrote: > On 10/02/13 11:20, Peter Gansterer wrote: > > Hi again, > > > > Are there really no hints about this topic? > > > > It would also be useful to definitely know there is no solution > > for what we are looking for - or even input as to why this wouldn't work. > > Otherwise we'd think about trying it on our own. > > You should look into the Xen Cloud Platform (XCP) [1], which has a > feature called Dynamic Memory Control, or memory ballooning [2]. It > requires you to install special PV drivers in your Windows guest. One of > these drivers is a ballooning daemon, which allocates a range of memory > from the guest OS, and then gives that memory back to Xen, which gives > the physical memory backed by that memory region to other guests. See > [2], "How do balloon drivers work and what is a memory balloon" for more > details. > > Mike > > [1] http://wiki.xen.org/wiki/XCP_Overview > [2] http://wiki.xen.org/wiki/Dynamic_Memory_Control Thx for the hint. I had a look at the docs; but from there it seems this is just an automatic way to distribute memory targets when starting or stopping guests. As long as guests don't change, memory config stays static. There is no hint, that memory targets are chosen according to the guests actual requirements. I don't like the idea of seting up an XCP system just to confirm that this is not what we're looking for. Maybe there is an XCP user on the list, who can tell me if DMC dynamically changes memory targets according to requirements in the domU (even if no machines are started or stopped)? - peter. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Sun Feb 10 14:01:43 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sun, 10 Feb 2013 14:01: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 1U4XSS-0005HA-6f; Sun, 10 Feb 2013 14:00:40 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U4XSQ-0005H3-Cv for xen-users@lists.xen.org; Sun, 10 Feb 2013 14:00:38 +0000 Received: from [85.158.139.211:25315] by server-5.bemta-5.messagelabs.com id 7B/72-11945-508A7115; Sun, 10 Feb 2013 14:00:37 +0000 X-Env-Sender: mike.mcclurg@citrix.com X-Msg-Ref: server-16.tower-206.messagelabs.com!1360504834!20767486!1 X-Originating-IP: [66.165.176.89] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjYuMTY1LjE3Ni44OSA9PiAxOTc4NDM=\n X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 17633 invoked from network); 10 Feb 2013 14:00:36 -0000 Received: from smtp.citrix.com (HELO SMTP.CITRIX.COM) (66.165.176.89) by server-16.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 10 Feb 2013 14:00:36 -0000 X-IronPort-AV: E=Sophos;i="4.84,637,1355097600"; d="scan'208";a="6943147" Received: from accessns.citrite.net (HELO FTLPEX01CL03.citrite.net) ([10.9.154.239]) by FTLPIPO01.CITRIX.COM with ESMTP/TLS/AES128-SHA; 10 Feb 2013 14:00:34 +0000 Received: from ukmail1.uk.xensource.com (10.80.16.128) by smtprelay.citrix.com (10.13.107.80) with Microsoft SMTP Server id 14.2.318.1; Sun, 10 Feb 2013 09:00:33 -0500 Received: from gateway-1.uk.xensource.com ([10.80.16.66] helo=[192.168.0.6]) by ukmail1.uk.xensource.com with esmtp (Exim 4.69) (envelope-from ) id 1U4XSL-0001hT-Gc; Sun, 10 Feb 2013 14:00:33 +0000 Message-ID: <5117A800.2020808@citrix.com> Date: Sun, 10 Feb 2013 14:00:32 +0000 From: Mike McClurg User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130106 Thunderbird/17.0.2 MIME-Version: 1.0 To: Peter Gansterer References: <1360502603.CDD80dB23.2491@pedos> In-Reply-To: <1360502603.CDD80dB23.2491@pedos> Cc: xen-users Subject: Re: [Xen-users] "dynamic memory allocation" for windows guests? X-BeenThere: xen-users@lists.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 10/02/13 13:44, Peter Gansterer wrote: > On 2013-02-10 13:13:51 Mike McClurg wrote: >> On 10/02/13 11:20, Peter Gansterer wrote: >>> Hi again, >>> >>> Are there really no hints about this topic? >>> >>> It would also be useful to definitely know there is no solution >>> for what we are looking for - or even input as to why this wouldn't work. >>> Otherwise we'd think about trying it on our own. >> >> You should look into the Xen Cloud Platform (XCP) [1], which has a >> feature called Dynamic Memory Control, or memory ballooning [2]. It >> requires you to install special PV drivers in your Windows guest. One of >> these drivers is a ballooning daemon, which allocates a range of memory >> from the guest OS, and then gives that memory back to Xen, which gives >> the physical memory backed by that memory region to other guests. See >> [2], "How do balloon drivers work and what is a memory balloon" for more >> details. >> >> Mike >> >> [1] http://wiki.xen.org/wiki/XCP_Overview >> [2] http://wiki.xen.org/wiki/Dynamic_Memory_Control > > Thx for the hint. > I had a look at the docs; but from there it seems this is just an automatic way to distribute memory targets when starting or stopping guests. As long as guests don't change, memory config stays static. > There is no hint, that memory targets are chosen according to the guests actual requirements. > > I don't like the idea of seting up an XCP system just to confirm that this is not what we're looking for. > > Maybe there is an XCP user on the list, who can tell me if DMC dynamically changes memory targets according to requirements in the domU (even if no machines are started or stopped)? DMC allows you to change the memory targets of the guest while the guest is running, not just before the guest boots. It allows you to "overprovision" your system, so that the maximum amount of memory allocated to guests is greater than the total amount of physical memory on the system. It does not dynamically change memory targets based on memory pressure in the guest (as mentioned in the DMC FAQ I referenced above). You'll probably have to roll your own custom solution for this. If you would like to demo XCP without committing a physical box, you can run XCP inside a VM (it works on VirtualBox, Xen, and VMWare Player). Unfortunately, you can't run HVM guests inside a virtual XCP like this, only PV guests, so you won't be able to boot Windows guests inside your nested XCP system. Mike _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Sun Feb 10 14:01:43 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sun, 10 Feb 2013 14:01: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 1U4XSS-0005HA-6f; Sun, 10 Feb 2013 14:00:40 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U4XSQ-0005H3-Cv for xen-users@lists.xen.org; Sun, 10 Feb 2013 14:00:38 +0000 Received: from [85.158.139.211:25315] by server-5.bemta-5.messagelabs.com id 7B/72-11945-508A7115; Sun, 10 Feb 2013 14:00:37 +0000 X-Env-Sender: mike.mcclurg@citrix.com X-Msg-Ref: server-16.tower-206.messagelabs.com!1360504834!20767486!1 X-Originating-IP: [66.165.176.89] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjYuMTY1LjE3Ni44OSA9PiAxOTc4NDM=\n X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 17633 invoked from network); 10 Feb 2013 14:00:36 -0000 Received: from smtp.citrix.com (HELO SMTP.CITRIX.COM) (66.165.176.89) by server-16.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 10 Feb 2013 14:00:36 -0000 X-IronPort-AV: E=Sophos;i="4.84,637,1355097600"; d="scan'208";a="6943147" Received: from accessns.citrite.net (HELO FTLPEX01CL03.citrite.net) ([10.9.154.239]) by FTLPIPO01.CITRIX.COM with ESMTP/TLS/AES128-SHA; 10 Feb 2013 14:00:34 +0000 Received: from ukmail1.uk.xensource.com (10.80.16.128) by smtprelay.citrix.com (10.13.107.80) with Microsoft SMTP Server id 14.2.318.1; Sun, 10 Feb 2013 09:00:33 -0500 Received: from gateway-1.uk.xensource.com ([10.80.16.66] helo=[192.168.0.6]) by ukmail1.uk.xensource.com with esmtp (Exim 4.69) (envelope-from ) id 1U4XSL-0001hT-Gc; Sun, 10 Feb 2013 14:00:33 +0000 Message-ID: <5117A800.2020808@citrix.com> Date: Sun, 10 Feb 2013 14:00:32 +0000 From: Mike McClurg User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130106 Thunderbird/17.0.2 MIME-Version: 1.0 To: Peter Gansterer References: <1360502603.CDD80dB23.2491@pedos> In-Reply-To: <1360502603.CDD80dB23.2491@pedos> Cc: xen-users Subject: Re: [Xen-users] "dynamic memory allocation" for windows guests? X-BeenThere: xen-users@lists.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 10/02/13 13:44, Peter Gansterer wrote: > On 2013-02-10 13:13:51 Mike McClurg wrote: >> On 10/02/13 11:20, Peter Gansterer wrote: >>> Hi again, >>> >>> Are there really no hints about this topic? >>> >>> It would also be useful to definitely know there is no solution >>> for what we are looking for - or even input as to why this wouldn't work. >>> Otherwise we'd think about trying it on our own. >> >> You should look into the Xen Cloud Platform (XCP) [1], which has a >> feature called Dynamic Memory Control, or memory ballooning [2]. It >> requires you to install special PV drivers in your Windows guest. One of >> these drivers is a ballooning daemon, which allocates a range of memory >> from the guest OS, and then gives that memory back to Xen, which gives >> the physical memory backed by that memory region to other guests. See >> [2], "How do balloon drivers work and what is a memory balloon" for more >> details. >> >> Mike >> >> [1] http://wiki.xen.org/wiki/XCP_Overview >> [2] http://wiki.xen.org/wiki/Dynamic_Memory_Control > > Thx for the hint. > I had a look at the docs; but from there it seems this is just an automatic way to distribute memory targets when starting or stopping guests. As long as guests don't change, memory config stays static. > There is no hint, that memory targets are chosen according to the guests actual requirements. > > I don't like the idea of seting up an XCP system just to confirm that this is not what we're looking for. > > Maybe there is an XCP user on the list, who can tell me if DMC dynamically changes memory targets according to requirements in the domU (even if no machines are started or stopped)? DMC allows you to change the memory targets of the guest while the guest is running, not just before the guest boots. It allows you to "overprovision" your system, so that the maximum amount of memory allocated to guests is greater than the total amount of physical memory on the system. It does not dynamically change memory targets based on memory pressure in the guest (as mentioned in the DMC FAQ I referenced above). You'll probably have to roll your own custom solution for this. If you would like to demo XCP without committing a physical box, you can run XCP inside a VM (it works on VirtualBox, Xen, and VMWare Player). Unfortunately, you can't run HVM guests inside a virtual XCP like this, only PV guests, so you won't be able to boot Windows guests inside your nested XCP system. Mike _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Sun Feb 10 14:15:18 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sun, 10 Feb 2013 14:15: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 1U4Xfi-0005wU-TS; Sun, 10 Feb 2013 14:14:22 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U4Xfh-0005wP-U0 for xen-users@lists.xen.org; Sun, 10 Feb 2013 14:14:22 +0000 Received: from [85.158.139.83:49776] by server-5.bemta-5.messagelabs.com id DF/B7-11945-D3BA7115; Sun, 10 Feb 2013 14:14:21 +0000 X-Env-Sender: peter.gansterer@paradigma.net X-Msg-Ref: server-10.tower-182.messagelabs.com!1360505660!28523592!1 X-Originating-IP: [213.47.215.227] X-SpamReason: No, hits=0.5 required=7.0 tests=BODY_RANDOM_LONG X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 21333 invoked from network); 10 Feb 2013 14:14:20 -0000 Received: from majere.luchs.at (HELO majere.luchs.at) (213.47.215.227) by server-10.tower-182.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 10 Feb 2013 14:14:20 -0000 Received: from localhost (localhost [127.0.0.1]) by majere.luchs.at (Postfix) with ESMTP id 6836BD007E28; Sun, 10 Feb 2013 15:14:19 +0100 (CET) X-Virus-Scanned: by majere.luchs.at Received: from majere.luchs.at ([127.0.0.1]) by localhost (majere.luchs.at [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6QeKrVq-3tSF; Sun, 10 Feb 2013 15:14:18 +0100 (CET) Received: from earth (earth.elements.lan [10.0.0.2]) by majere.luchs.at (Postfix) with ESMTP id 9CEEDD007E21; Sun, 10 Feb 2013 15:14:18 +0100 (CET) Received: from pedos (pedos.elements.lan [10.0.0.108]) by earth (Postfix) with SMTP id 779953340; Sun, 10 Feb 2013 15:14:17 +0100 (CET) Received: by pedos (sSMTP sendmail emulation); Sun, 10 Feb 2013 15:12:27 +0100 Content-Disposition: inline MIME-Version: 1.0 X-Mailer: MIME-tools 5.503 (Entity 5.503) Message-ID: <1360505083.5e0aE7424.2491@pedos> From: "Peter Gansterer" Date: Sun, 10 Feb 2013 15:12:21 +0100 In-Reply-To: <5117A800.2020808@citrix.com> To: "Mike McClurg" Cc: xen-users Subject: Re: [Xen-users] "dynamic memory allocation" for windows guests? X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: 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 2013-02-10 14:00:32 Mike McClurg wrote: > [...] > > DMC allows you to change the memory targets of the guest while the guest > is running, not just before the guest boots. It allows you to > "overprovision" your system, so that the maximum amount of memory > allocated to guests is greater than the total amount of physical memory > on the system. > > It does not dynamically change memory targets based on memory pressure > in the guest (as mentioned in the DMC FAQ I referenced above). You'll > probably have to roll your own custom solution for this. > > If you would like to demo XCP without committing a physical box, you can > run XCP inside a VM (it works on VirtualBox, Xen, and VMWare Player). > Unfortunately, you can't run HVM guests inside a virtual XCP like this, > only PV guests, so you won't be able to boot Windows guests inside your > nested XCP system. All right, thx for confirming. So it's not exactly what we want to do. Am I the only one who thinks it would be useful to change memory targets according to actual guest requirements, or is my naive approach just not feasible in practice? I'd rather refrain from creating our own solution if it already failed before... - peter. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Sun Feb 10 14:15:18 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sun, 10 Feb 2013 14:15: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 1U4Xfi-0005wU-TS; Sun, 10 Feb 2013 14:14:22 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U4Xfh-0005wP-U0 for xen-users@lists.xen.org; Sun, 10 Feb 2013 14:14:22 +0000 Received: from [85.158.139.83:49776] by server-5.bemta-5.messagelabs.com id DF/B7-11945-D3BA7115; Sun, 10 Feb 2013 14:14:21 +0000 X-Env-Sender: peter.gansterer@paradigma.net X-Msg-Ref: server-10.tower-182.messagelabs.com!1360505660!28523592!1 X-Originating-IP: [213.47.215.227] X-SpamReason: No, hits=0.5 required=7.0 tests=BODY_RANDOM_LONG X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 21333 invoked from network); 10 Feb 2013 14:14:20 -0000 Received: from majere.luchs.at (HELO majere.luchs.at) (213.47.215.227) by server-10.tower-182.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 10 Feb 2013 14:14:20 -0000 Received: from localhost (localhost [127.0.0.1]) by majere.luchs.at (Postfix) with ESMTP id 6836BD007E28; Sun, 10 Feb 2013 15:14:19 +0100 (CET) X-Virus-Scanned: by majere.luchs.at Received: from majere.luchs.at ([127.0.0.1]) by localhost (majere.luchs.at [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6QeKrVq-3tSF; Sun, 10 Feb 2013 15:14:18 +0100 (CET) Received: from earth (earth.elements.lan [10.0.0.2]) by majere.luchs.at (Postfix) with ESMTP id 9CEEDD007E21; Sun, 10 Feb 2013 15:14:18 +0100 (CET) Received: from pedos (pedos.elements.lan [10.0.0.108]) by earth (Postfix) with SMTP id 779953340; Sun, 10 Feb 2013 15:14:17 +0100 (CET) Received: by pedos (sSMTP sendmail emulation); Sun, 10 Feb 2013 15:12:27 +0100 Content-Disposition: inline MIME-Version: 1.0 X-Mailer: MIME-tools 5.503 (Entity 5.503) Message-ID: <1360505083.5e0aE7424.2491@pedos> From: "Peter Gansterer" Date: Sun, 10 Feb 2013 15:12:21 +0100 In-Reply-To: <5117A800.2020808@citrix.com> To: "Mike McClurg" Cc: xen-users Subject: Re: [Xen-users] "dynamic memory allocation" for windows guests? X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: 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 2013-02-10 14:00:32 Mike McClurg wrote: > [...] > > DMC allows you to change the memory targets of the guest while the guest > is running, not just before the guest boots. It allows you to > "overprovision" your system, so that the maximum amount of memory > allocated to guests is greater than the total amount of physical memory > on the system. > > It does not dynamically change memory targets based on memory pressure > in the guest (as mentioned in the DMC FAQ I referenced above). You'll > probably have to roll your own custom solution for this. > > If you would like to demo XCP without committing a physical box, you can > run XCP inside a VM (it works on VirtualBox, Xen, and VMWare Player). > Unfortunately, you can't run HVM guests inside a virtual XCP like this, > only PV guests, so you won't be able to boot Windows guests inside your > nested XCP system. All right, thx for confirming. So it's not exactly what we want to do. Am I the only one who thinks it would be useful to change memory targets according to actual guest requirements, or is my naive approach just not feasible in practice? I'd rather refrain from creating our own solution if it already failed before... - peter. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Sun Feb 10 22:30:31 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sun, 10 Feb 2013 22:30: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 1U4fOB-000644-7p; Sun, 10 Feb 2013 22:28:47 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U4fO9-00063x-6Y for xen-users@lists.xen.org; Sun, 10 Feb 2013 22:28:45 +0000 Received: from [85.158.138.51:47373] by server-1.bemta-3.messagelabs.com id F7/36-08955-71F18115; Sun, 10 Feb 2013 22:28:39 +0000 X-Env-Sender: james.harper@bendigoit.com.au X-Msg-Ref: server-3.tower-174.messagelabs.com!1360535314!21558313!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.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 30285 invoked from network); 10 Feb 2013 22:28:37 -0000 Received: from smtp1.bendigoit.com.au (HELO smtp1.bendigoit.com.au) (203.16.224.4) by server-3.tower-174.messagelabs.com with AES256-SHA encrypted SMTP; 10 Feb 2013 22:28:37 -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 1U4fNt-000882-2F; Mon, 11 Feb 2013 09:28:29 +1100 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.0438.000; Mon, 11 Feb 2013 09:28:28 +1100 From: James Harper To: Peter Gansterer , xen-users Thread-Topic: [Xen-users] Problem using PoD on Xen 4.2.1 (win domU crash) Thread-Index: AQHOB4rUq4YqYUC7L0mlGk3L+Aa0wZhzqoAQ Date: Sun, 10 Feb 2013 22:28:27 +0000 Message-ID: <6035A0D088A63A46850C3988ED045A4B35665186@BITCOM1.int.sbss.com.au> References: <1360495896.0CCE0aE22.2491@pedos> In-Reply-To: <1360495896.0CCE0aE22.2491@pedos> 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:b80e:ea50:dc96:baea] x-tm-as-product-ver: SMEX-10.2.0.2087-7.000.1014-19628.002 x-tm-as-result: No--36.037100-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] Problem using PoD on Xen 4.2.1 (win domU 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: 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 short: > Windows domU doesn't show any ballooned memory and finally crashes > ("out of PoD memory") when "starting ballooned". > > We tested on 2 different hosts and windows guests: > Windows Server 2008 R2 and 2003. > Xen 4.2.1 on gentoo, dom0 kernels: 3.7.x > signed gplpv drivers from univention. > Which version of the univention drivers? Maybe the univention signed drivers are bit old. Try one of: http://www.meadowcourt.org/private/gplpv_2000_0.11.0.372.msi http://www.meadowcourt.org/private/gplpv_2000_0.11.0.372_debug.msi http://www.meadowcourt.org/private/gplpv_2003x32_0.11.0.372.msi http://www.meadowcourt.org/private/gplpv_2003x32_0.11.0.372_debug.msi http://www.meadowcourt.org/private/gplpv_2003x64_0.11.0.372.msi http://www.meadowcourt.org/private/gplpv_2003x64_0.11.0.372_debug.msi http://www.meadowcourt.org/private/gplpv_Vista2008x32_0.11.0.372.msi http://www.meadowcourt.org/private/gplpv_Vista2008x32_0.11.0.372_debug.msi http://www.meadowcourt.org/private/gplpv_Vista2008x64_0.11.0.372.msi http://www.meadowcourt.org/private/gplpv_Vista2008x64_0.11.0.372_debug.msi http://www.meadowcourt.org/private/gplpv_XP_0.11.0.372.msi http://www.meadowcourt.org/private/gplpv_XP_0.11.0.372_debug.msi and give it a go. I just tried it on 2003 and it works fine, or at least from 30 seconds testing it correctly shows that of the 4G I assigned to the domu, only 787MB is free immediately after boot. If it still doesn't work, use the _debug version and send me the /var/log/xen/qemu-dm-.log. You should see something like: 13005008537656: XenPCI --> XenPci_InitialBalloonDown 13005008537656: XenPCI base = 0x40000000, Xen Signature = XenVMMXenVMM, EAX = 0x40000002 13005008537671: XenPCI Xen Version 4.1 13005008537671: XenPCI Hypercall area at 8AD62000 13005008537671: XenPCI XENMEM_maximum_reservation = 1049600 13005008537671: XenPCI XENMEM_current_reservation = 263157 13005008537671: XenPCI Trying to give 3145772 KB (3072 MB) to Xen 13005008556656: XenPCI <-- XenPci_InitialBalloonDown James _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Sun Feb 10 22:30:31 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sun, 10 Feb 2013 22:30: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 1U4fOB-000644-7p; Sun, 10 Feb 2013 22:28:47 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U4fO9-00063x-6Y for xen-users@lists.xen.org; Sun, 10 Feb 2013 22:28:45 +0000 Received: from [85.158.138.51:47373] by server-1.bemta-3.messagelabs.com id F7/36-08955-71F18115; Sun, 10 Feb 2013 22:28:39 +0000 X-Env-Sender: james.harper@bendigoit.com.au X-Msg-Ref: server-3.tower-174.messagelabs.com!1360535314!21558313!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.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 30285 invoked from network); 10 Feb 2013 22:28:37 -0000 Received: from smtp1.bendigoit.com.au (HELO smtp1.bendigoit.com.au) (203.16.224.4) by server-3.tower-174.messagelabs.com with AES256-SHA encrypted SMTP; 10 Feb 2013 22:28:37 -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 1U4fNt-000882-2F; Mon, 11 Feb 2013 09:28:29 +1100 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.0438.000; Mon, 11 Feb 2013 09:28:28 +1100 From: James Harper To: Peter Gansterer , xen-users Thread-Topic: [Xen-users] Problem using PoD on Xen 4.2.1 (win domU crash) Thread-Index: AQHOB4rUq4YqYUC7L0mlGk3L+Aa0wZhzqoAQ Date: Sun, 10 Feb 2013 22:28:27 +0000 Message-ID: <6035A0D088A63A46850C3988ED045A4B35665186@BITCOM1.int.sbss.com.au> References: <1360495896.0CCE0aE22.2491@pedos> In-Reply-To: <1360495896.0CCE0aE22.2491@pedos> 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:b80e:ea50:dc96:baea] x-tm-as-product-ver: SMEX-10.2.0.2087-7.000.1014-19628.002 x-tm-as-result: No--36.037100-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] Problem using PoD on Xen 4.2.1 (win domU 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: 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 short: > Windows domU doesn't show any ballooned memory and finally crashes > ("out of PoD memory") when "starting ballooned". > > We tested on 2 different hosts and windows guests: > Windows Server 2008 R2 and 2003. > Xen 4.2.1 on gentoo, dom0 kernels: 3.7.x > signed gplpv drivers from univention. > Which version of the univention drivers? Maybe the univention signed drivers are bit old. Try one of: http://www.meadowcourt.org/private/gplpv_2000_0.11.0.372.msi http://www.meadowcourt.org/private/gplpv_2000_0.11.0.372_debug.msi http://www.meadowcourt.org/private/gplpv_2003x32_0.11.0.372.msi http://www.meadowcourt.org/private/gplpv_2003x32_0.11.0.372_debug.msi http://www.meadowcourt.org/private/gplpv_2003x64_0.11.0.372.msi http://www.meadowcourt.org/private/gplpv_2003x64_0.11.0.372_debug.msi http://www.meadowcourt.org/private/gplpv_Vista2008x32_0.11.0.372.msi http://www.meadowcourt.org/private/gplpv_Vista2008x32_0.11.0.372_debug.msi http://www.meadowcourt.org/private/gplpv_Vista2008x64_0.11.0.372.msi http://www.meadowcourt.org/private/gplpv_Vista2008x64_0.11.0.372_debug.msi http://www.meadowcourt.org/private/gplpv_XP_0.11.0.372.msi http://www.meadowcourt.org/private/gplpv_XP_0.11.0.372_debug.msi and give it a go. I just tried it on 2003 and it works fine, or at least from 30 seconds testing it correctly shows that of the 4G I assigned to the domu, only 787MB is free immediately after boot. If it still doesn't work, use the _debug version and send me the /var/log/xen/qemu-dm-.log. You should see something like: 13005008537656: XenPCI --> XenPci_InitialBalloonDown 13005008537656: XenPCI base = 0x40000000, Xen Signature = XenVMMXenVMM, EAX = 0x40000002 13005008537671: XenPCI Xen Version 4.1 13005008537671: XenPCI Hypercall area at 8AD62000 13005008537671: XenPCI XENMEM_maximum_reservation = 1049600 13005008537671: XenPCI XENMEM_current_reservation = 263157 13005008537671: XenPCI Trying to give 3145772 KB (3072 MB) to Xen 13005008556656: XenPCI <-- XenPci_InitialBalloonDown James _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Sun Feb 10 23:30:48 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sun, 10 Feb 2013 23:30: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 1U4gKQ-0006az-Ab; Sun, 10 Feb 2013 23:28:58 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U4gKO-0006au-EP for xen-users@lists.xen.org; Sun, 10 Feb 2013 23:28:56 +0000 Received: from [85.158.143.35:22641] by server-1.bemta-4.messagelabs.com id 61/AF-08839-73D28115; Sun, 10 Feb 2013 23:28:55 +0000 X-Env-Sender: Nick.Couchman@seakr.com X-Msg-Ref: server-7.tower-21.messagelabs.com!1360538932!11861026!1 X-Originating-IP: [64.2.143.10] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 27336 invoked from network); 10 Feb 2013 23:28:54 -0000 Received: from mx1.seakr.com (HELO mx1.seakr.com) (64.2.143.10) by server-7.tower-21.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 10 Feb 2013 23:28:54 -0000 Received: from mx-inside.seakr.com ([192.168.100.31]) by mx1.seakr.com (8.14.3/8.14.3/Debian-9.4) with ESMTP id r1ANRSm6001573 for ; Sun, 10 Feb 2013 16:27:30 -0700 Received: from (mx-inside.seakr.com [192.168.100.31]) by mail-scanner1.it.seakr.com with smtp id 2fff_089c_a03a8636_73d9_11e2_87a6_00137252735f; Sun, 10 Feb 2013 16:28:52 -0700 Received: from collaborate.seakr.com (collaborate.seakr.com [192.168.100.28]) by mx-inside.seakr.com (Postfix) with ESMTP id B13FF44D9C for ; Sun, 10 Feb 2013 16:28:50 -0700 (MST) Received: from seakr-engineering-MTA by collaborate.seakr.com with Novell_GroupWise; Sun, 10 Feb 2013 16:28:50 -0700 Message-Id: <5117CABF020000990002B06B@collaborate.seakr.com> X-Mailer: Novell GroupWise Internet Agent 8.0.3 Date: Sun, 10 Feb 2013 16:28:47 -0700 From: "Nick Couchman" To: "xen-users" , "Peter Gansterer" Mime-Version: 1.0 Content-Disposition: inline X-NAIMIME-Disclaimer: 1 X-NAIMIME-Modified: 1 Subject: Re: [Xen-users] "dynamic memory allocation" for windows guests? X-BeenThere: xen-users@lists.xen.org X-Mailman-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-15" Content-Transfer-Encoding: quoted-printable Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org Peter, There are a couple of options. First, I believe recent versions of Xen will let you set a maximum allocation and then a lower initial allocation (XCP at least lets you do this) and you can then allocate memory between the initial and maximum allocation. Unfortunately, due to limitations with Windows virtualization, what actually happens is that Xen tells Windows that is has memory at the maximum level but marks the difference between the current allocation and the maximum allocation as used memory. As you increase allocation up from the current allocation to your maximum allocation it frees up the memory in that range. This requires a driver/daemon inside of Windows to accomplish the dynamic allocation - I think GPLPV drivers have support, and I know the XCP/XenServer drivers include support. Overcommitment is something entirely different and, while supported in the open source versions of the Xen hypervisor (look up xenpaging), is not at this time supported in XCP or commercial XenServer (to my knowledge). Overcommitment is the idea of actually allocating more memory to guests than you have available on your physical machines, with the risk of running into a situation where you cannot fulfill the required commitment level to all of the guests. Overcommitment is a hypervisor/dom0 feature and shouldn't require any additional drivers inside the guest to accomplish. -Nick >>> On 2013/02/10 at 04:20, "Peter Gansterer" wrote: = > Hi again, > = > Are there really no hints about this topic? > = > It would also be useful to definitely know there is no solution for what we = > are looking for - or even input as to why this wouldn't work. > Otherwise we'd think about trying it on our own. > = > - peda. > = > = > On 2013-02-07 18:37:16.481416 Peter Gansterer wrote: >> Hello, >> = >> In our office we would like to do something like "memory overcommitment" >> or rather "dynamic allocation" for a bunch of windows domUs (server 2003 & = > 2008). >> = >> We thought this should be a simple feature, however we did not find any >> fitting solution. >> We use Xen 4.2.1 with xl toolstack. >> = >> The idea is to use ballooning to dynamically (and automatically) change >> physical memory available to the domUs according to their memory needs. >> There was something called "xenballoond" for linux guests before "tmem" >> was integrated, and this seems to be exactly what we're looking for, >> except that we need it for windows domUs. >> = >> Is there really no such thing for windows guests, or are we just too stupid = > to find it? >> We would be happy about any hints. >> = >> If there really is none, then, is there a reason for that? >> = >> It seems like a simple thing: >> - start a process on each windows guest to monitor memory usage >> - if there is spare memory -> tell the hypervisor to lower the mem-target >> - if memory is used up, decide upon CPU usage and mem history: >> . idle for some time -> try to free buffers by allocating and freeing = > blocks >> . loaded -> do nothing or increase mem-target, according to pagefile usage >> . recently increased -> increase mem-target >> - If memory is needed quickly, the pagefile will be used temporarily. >> - In a trivial implementation, a simple script on dom0 could receive >> the mem-target requests and do the actual "xl mem-set" calls >> (according to some balancing algorithm). >> = >> Or is this approach just too naive? >> = >> In our scenario (virtual desktops and testservers) there are always idle >> guests wasting memory and not really using it. I suppose there must be a >> way to automatically (if just slowly) shift memory to those in need, and >> thus reducing overall memory requirements. >> = >> yours, >> - peter. >> = >> -- = >> Peter Gansterer >> = >> PARADIGMA Unternehmensberatung GmbH >> Mariahilferstra=DFe 47/1/3 >> A-1060 Wien >> Tel: 0043-(0)1-585 49 72 >> http://www.paradigma.net >> = >> Firmenbuchnummer: FN 134564 p >> Rechtsform: GmbH >> Firmenbuchgericht: Handelsgericht Wien -------- This e-mail may contain confidential and privileged material for the sole u= se of the intended recipient. If this email is not intended for you, or yo= u are not responsible for the delivery of this message to the intended reci= pient, please note that this message may contain SEAKR Engineering (SEAKR) = Privileged/Proprietary Information. In such a case, you are strictly prohi= bited from downloading, photocopying, distributing or otherwise using this = message, its contents or attachments in any way. If you have received this= message in error, please notify us immediately by replying to this e-mail = and delete the message from your mailbox. Information contained in this me= ssage that does not relate to the business of SEAKR is neither endorsed by = nor attributable to SEAKR. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Sun Feb 10 23:30:48 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sun, 10 Feb 2013 23:30: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 1U4gKQ-0006az-Ab; Sun, 10 Feb 2013 23:28:58 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U4gKO-0006au-EP for xen-users@lists.xen.org; Sun, 10 Feb 2013 23:28:56 +0000 Received: from [85.158.143.35:22641] by server-1.bemta-4.messagelabs.com id 61/AF-08839-73D28115; Sun, 10 Feb 2013 23:28:55 +0000 X-Env-Sender: Nick.Couchman@seakr.com X-Msg-Ref: server-7.tower-21.messagelabs.com!1360538932!11861026!1 X-Originating-IP: [64.2.143.10] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 27336 invoked from network); 10 Feb 2013 23:28:54 -0000 Received: from mx1.seakr.com (HELO mx1.seakr.com) (64.2.143.10) by server-7.tower-21.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 10 Feb 2013 23:28:54 -0000 Received: from mx-inside.seakr.com ([192.168.100.31]) by mx1.seakr.com (8.14.3/8.14.3/Debian-9.4) with ESMTP id r1ANRSm6001573 for ; Sun, 10 Feb 2013 16:27:30 -0700 Received: from (mx-inside.seakr.com [192.168.100.31]) by mail-scanner1.it.seakr.com with smtp id 2fff_089c_a03a8636_73d9_11e2_87a6_00137252735f; Sun, 10 Feb 2013 16:28:52 -0700 Received: from collaborate.seakr.com (collaborate.seakr.com [192.168.100.28]) by mx-inside.seakr.com (Postfix) with ESMTP id B13FF44D9C for ; Sun, 10 Feb 2013 16:28:50 -0700 (MST) Received: from seakr-engineering-MTA by collaborate.seakr.com with Novell_GroupWise; Sun, 10 Feb 2013 16:28:50 -0700 Message-Id: <5117CABF020000990002B06B@collaborate.seakr.com> X-Mailer: Novell GroupWise Internet Agent 8.0.3 Date: Sun, 10 Feb 2013 16:28:47 -0700 From: "Nick Couchman" To: "xen-users" , "Peter Gansterer" Mime-Version: 1.0 Content-Disposition: inline X-NAIMIME-Disclaimer: 1 X-NAIMIME-Modified: 1 Subject: Re: [Xen-users] "dynamic memory allocation" for windows guests? X-BeenThere: xen-users@lists.xen.org X-Mailman-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-15" Content-Transfer-Encoding: quoted-printable Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org Peter, There are a couple of options. First, I believe recent versions of Xen will let you set a maximum allocation and then a lower initial allocation (XCP at least lets you do this) and you can then allocate memory between the initial and maximum allocation. Unfortunately, due to limitations with Windows virtualization, what actually happens is that Xen tells Windows that is has memory at the maximum level but marks the difference between the current allocation and the maximum allocation as used memory. As you increase allocation up from the current allocation to your maximum allocation it frees up the memory in that range. This requires a driver/daemon inside of Windows to accomplish the dynamic allocation - I think GPLPV drivers have support, and I know the XCP/XenServer drivers include support. Overcommitment is something entirely different and, while supported in the open source versions of the Xen hypervisor (look up xenpaging), is not at this time supported in XCP or commercial XenServer (to my knowledge). Overcommitment is the idea of actually allocating more memory to guests than you have available on your physical machines, with the risk of running into a situation where you cannot fulfill the required commitment level to all of the guests. Overcommitment is a hypervisor/dom0 feature and shouldn't require any additional drivers inside the guest to accomplish. -Nick >>> On 2013/02/10 at 04:20, "Peter Gansterer" wrote: = > Hi again, > = > Are there really no hints about this topic? > = > It would also be useful to definitely know there is no solution for what we = > are looking for - or even input as to why this wouldn't work. > Otherwise we'd think about trying it on our own. > = > - peda. > = > = > On 2013-02-07 18:37:16.481416 Peter Gansterer wrote: >> Hello, >> = >> In our office we would like to do something like "memory overcommitment" >> or rather "dynamic allocation" for a bunch of windows domUs (server 2003 & = > 2008). >> = >> We thought this should be a simple feature, however we did not find any >> fitting solution. >> We use Xen 4.2.1 with xl toolstack. >> = >> The idea is to use ballooning to dynamically (and automatically) change >> physical memory available to the domUs according to their memory needs. >> There was something called "xenballoond" for linux guests before "tmem" >> was integrated, and this seems to be exactly what we're looking for, >> except that we need it for windows domUs. >> = >> Is there really no such thing for windows guests, or are we just too stupid = > to find it? >> We would be happy about any hints. >> = >> If there really is none, then, is there a reason for that? >> = >> It seems like a simple thing: >> - start a process on each windows guest to monitor memory usage >> - if there is spare memory -> tell the hypervisor to lower the mem-target >> - if memory is used up, decide upon CPU usage and mem history: >> . idle for some time -> try to free buffers by allocating and freeing = > blocks >> . loaded -> do nothing or increase mem-target, according to pagefile usage >> . recently increased -> increase mem-target >> - If memory is needed quickly, the pagefile will be used temporarily. >> - In a trivial implementation, a simple script on dom0 could receive >> the mem-target requests and do the actual "xl mem-set" calls >> (according to some balancing algorithm). >> = >> Or is this approach just too naive? >> = >> In our scenario (virtual desktops and testservers) there are always idle >> guests wasting memory and not really using it. I suppose there must be a >> way to automatically (if just slowly) shift memory to those in need, and >> thus reducing overall memory requirements. >> = >> yours, >> - peter. >> = >> -- = >> Peter Gansterer >> = >> PARADIGMA Unternehmensberatung GmbH >> Mariahilferstra=DFe 47/1/3 >> A-1060 Wien >> Tel: 0043-(0)1-585 49 72 >> http://www.paradigma.net >> = >> Firmenbuchnummer: FN 134564 p >> Rechtsform: GmbH >> Firmenbuchgericht: Handelsgericht Wien -------- This e-mail may contain confidential and privileged material for the sole u= se of the intended recipient. If this email is not intended for you, or yo= u are not responsible for the delivery of this message to the intended reci= pient, please note that this message may contain SEAKR Engineering (SEAKR) = Privileged/Proprietary Information. In such a case, you are strictly prohi= bited from downloading, photocopying, distributing or otherwise using this = message, its contents or attachments in any way. If you have received this= message in error, please notify us immediately by replying to this e-mail = and delete the message from your mailbox. Information contained in this me= ssage that does not relate to the business of SEAKR is neither endorsed by = nor attributable to SEAKR. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Mon Feb 11 00:01:40 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 11 Feb 2013 00:01: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 1U4goM-00078m-LQ; Sun, 10 Feb 2013 23:59:54 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U4goK-00078h-Bz for xen-users@lists.xen.org; Sun, 10 Feb 2013 23:59:52 +0000 Received: from [85.158.143.99:57638] by server-3.bemta-4.messagelabs.com id 91/37-08920-77438115; Sun, 10 Feb 2013 23:59:51 +0000 X-Env-Sender: james.harper@bendigoit.com.au X-Msg-Ref: server-13.tower-216.messagelabs.com!1360540787!30759826!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.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 19781 invoked from network); 10 Feb 2013 23:59:50 -0000 Received: from mail.bendigoit.com.au (HELO smtp2.bendigoit.com.au) (203.16.207.99) by server-13.tower-216.messagelabs.com with AES256-SHA encrypted SMTP; 10 Feb 2013 23:59:50 -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 1U4goD-0008Rc-6y; Mon, 11 Feb 2013 10:59:45 +1100 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.0438.000; Mon, 11 Feb 2013 10:59:45 +1100 From: James Harper To: Peter Gansterer Thread-Topic: Suspicious URL:Re: [Xen-users] Problem using PoD on Xen 4.2.1 (win domU crash) Thread-Index: AQHOB4rUq4YqYUC7L0mlGk3L+Aa0wZhzqoAQ//9daoCAAL0J4A== Date: Sun, 10 Feb 2013 23:59:43 +0000 Message-ID: <6035A0D088A63A46850C3988ED045A4B3566543E@BITCOM1.int.sbss.com.au> References: <6035A0D088A63A46850C3988ED045A4B35665186@BITCOM1.int.sbss.com.au> <1360539113.22CCbA26.2491@pedos> In-Reply-To: <1360539113.22CCbA26.2491@pedos> 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:b80e:ea50:dc96:baea] x-tm-as-product-ver: SMEX-10.2.0.2087-7.000.1014-19628.002 x-tm-as-result: No--36.493500-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 Subject: Re: [Xen-users] Suspicious URL:Re: Problem using PoD on Xen 4.2.1 (win domU 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: 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 tried on my win2008R2/64 and it is still the same with the new driver. > Started with 1/8GB; no sign of a "balloon"; did some alloc/dealloc until it > crashed. > Tried both regular & debug. Log and xl dmesg attached. > > (To make sure, I just also tried with 1/4GB - the same) > Your one says: 13005008825593: XenPCI --> XenPci_InitialBalloonDown 13005008825593: XenPCI base = 0x40000000, Xen Signature = Microsoft Hv, EAX = 0x40000006 13005008825593: XenPCI base = 0x40000100, Xen Signature = XenVMMXenVMM, EAX = 0x40000102 13005008825593: XenPCI Xen Version 4.2 13005008825593: XenPCI Hypercall area at FFFFFA80063A4000 13005008825593: XenPCI XENMEM_maximum_reservation = 262400 13005008825593: XenPCI XENMEM_current_reservation = 262136 13005008825609: XenPCI Trying to give 1056 KB (1 MB) to Xen 13005008825624: XenPCI <-- XenPci_InitialBalloonDown So for some reason gplpv can't determine that you want to be ballooned down 7GB, it's just giving back the default 1MB (there are/were some problems with save/restore when this didn't happen). I notice you are using 4.2 while I'm using 4.1, which probably accounts for the difference. I'll post on xen-devel to ask what the correct way of determining this is under 4.2... I suspect that giving your VM 8G but ballooning down to 1G might be pushing things a bit. There are overheads with higher amounts of memory, and Windows will make some assumptions about how large to allocate internal tables etc based on the amount of memory. James _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Mon Feb 11 00:01:40 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 11 Feb 2013 00:01: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 1U4goM-00078m-LQ; Sun, 10 Feb 2013 23:59:54 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U4goK-00078h-Bz for xen-users@lists.xen.org; Sun, 10 Feb 2013 23:59:52 +0000 Received: from [85.158.143.99:57638] by server-3.bemta-4.messagelabs.com id 91/37-08920-77438115; Sun, 10 Feb 2013 23:59:51 +0000 X-Env-Sender: james.harper@bendigoit.com.au X-Msg-Ref: server-13.tower-216.messagelabs.com!1360540787!30759826!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.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 19781 invoked from network); 10 Feb 2013 23:59:50 -0000 Received: from mail.bendigoit.com.au (HELO smtp2.bendigoit.com.au) (203.16.207.99) by server-13.tower-216.messagelabs.com with AES256-SHA encrypted SMTP; 10 Feb 2013 23:59:50 -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 1U4goD-0008Rc-6y; Mon, 11 Feb 2013 10:59:45 +1100 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.0438.000; Mon, 11 Feb 2013 10:59:45 +1100 From: James Harper To: Peter Gansterer Thread-Topic: Suspicious URL:Re: [Xen-users] Problem using PoD on Xen 4.2.1 (win domU crash) Thread-Index: AQHOB4rUq4YqYUC7L0mlGk3L+Aa0wZhzqoAQ//9daoCAAL0J4A== Date: Sun, 10 Feb 2013 23:59:43 +0000 Message-ID: <6035A0D088A63A46850C3988ED045A4B3566543E@BITCOM1.int.sbss.com.au> References: <6035A0D088A63A46850C3988ED045A4B35665186@BITCOM1.int.sbss.com.au> <1360539113.22CCbA26.2491@pedos> In-Reply-To: <1360539113.22CCbA26.2491@pedos> 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:b80e:ea50:dc96:baea] x-tm-as-product-ver: SMEX-10.2.0.2087-7.000.1014-19628.002 x-tm-as-result: No--36.493500-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 Subject: Re: [Xen-users] Suspicious URL:Re: Problem using PoD on Xen 4.2.1 (win domU 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: 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 tried on my win2008R2/64 and it is still the same with the new driver. > Started with 1/8GB; no sign of a "balloon"; did some alloc/dealloc until it > crashed. > Tried both regular & debug. Log and xl dmesg attached. > > (To make sure, I just also tried with 1/4GB - the same) > Your one says: 13005008825593: XenPCI --> XenPci_InitialBalloonDown 13005008825593: XenPCI base = 0x40000000, Xen Signature = Microsoft Hv, EAX = 0x40000006 13005008825593: XenPCI base = 0x40000100, Xen Signature = XenVMMXenVMM, EAX = 0x40000102 13005008825593: XenPCI Xen Version 4.2 13005008825593: XenPCI Hypercall area at FFFFFA80063A4000 13005008825593: XenPCI XENMEM_maximum_reservation = 262400 13005008825593: XenPCI XENMEM_current_reservation = 262136 13005008825609: XenPCI Trying to give 1056 KB (1 MB) to Xen 13005008825624: XenPCI <-- XenPci_InitialBalloonDown So for some reason gplpv can't determine that you want to be ballooned down 7GB, it's just giving back the default 1MB (there are/were some problems with save/restore when this didn't happen). I notice you are using 4.2 while I'm using 4.1, which probably accounts for the difference. I'll post on xen-devel to ask what the correct way of determining this is under 4.2... I suspect that giving your VM 8G but ballooning down to 1G might be pushing things a bit. There are overheads with higher amounts of memory, and Windows will make some assumptions about how large to allocate internal tables etc based on the amount of memory. James _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Mon Feb 11 00:15:36 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 11 Feb 2013 00:15: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 1U4h21-00083N-Mr; Mon, 11 Feb 2013 00: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 1U4h20-00083G-5l for xen-users@lists.xen.org; Mon, 11 Feb 2013 00:14:00 +0000 Received: from [85.158.143.99:18364] by server-1.bemta-4.messagelabs.com id BB/48-08839-7C738115; Mon, 11 Feb 2013 00:13:59 +0000 X-Env-Sender: peter.gansterer@paradigma.net X-Msg-Ref: server-16.tower-216.messagelabs.com!1360541638!18736085!1 X-Originating-IP: [213.47.215.227] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 8560 invoked from network); 11 Feb 2013 00:13:58 -0000 Received: from majere.luchs.at (HELO majere.luchs.at) (213.47.215.227) by server-16.tower-216.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 11 Feb 2013 00:13:58 -0000 Received: from localhost (localhost [127.0.0.1]) by majere.luchs.at (Postfix) with ESMTP id D3D00D007E24; Mon, 11 Feb 2013 01:13:57 +0100 (CET) X-Virus-Scanned: by majere.luchs.at Received: from majere.luchs.at ([127.0.0.1]) by localhost (majere.luchs.at [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id a4UjjDcriQJ5; Mon, 11 Feb 2013 01:13:56 +0100 (CET) Received: from earth (earth.elements.lan [10.0.0.2]) by majere.luchs.at (Postfix) with ESMTP id 3D92FD007E21; Mon, 11 Feb 2013 01:13:56 +0100 (CET) Received: from pedos (pedos.elements.lan [10.0.0.108]) by earth (Postfix) with SMTP id AFFB87ED9; Mon, 11 Feb 2013 01:13:54 +0100 (CET) Received: by pedos (sSMTP sendmail emulation); Mon, 11 Feb 2013 01:12:04 +0100 Content-Disposition: inline MIME-Version: 1.0 X-Mailer: MIME-tools 5.503 (Entity 5.503) Message-ID: <1360539932.2C5C61D27.2491@pedos> From: "Peter Gansterer" Date: Mon, 11 Feb 2013 01:12:01 +0100 In-Reply-To: <5117CABF020000990002B06B@collaborate.seakr.com> To: "Nick Couchman" Cc: xen-users Subject: Re: [Xen-users] "dynamic memory allocation" for windows guests? X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: 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 2013-02-10 16:28:47 Nick Couchman wrote: > Peter, > There are a couple of options. First, I believe recent versions of Xen > will let you set a maximum allocation and then a lower initial > allocation (XCP at least lets you do this) and you can then allocate > memory between the initial and maximum allocation. Unfortunately, due > to limitations with Windows virtualization, what actually happens is > that Xen tells Windows that is has memory at the maximum level but marks > the difference between the current allocation and the maximum allocation > as used memory. As you increase allocation up from the current > allocation to your maximum allocation it frees up the memory in that > range. This requires a driver/daemon inside of Windows to accomplish > the dynamic allocation - I think GPLPV drivers have support, and I know > the XCP/XenServer drivers include support. I am well aware of "ballooning" as a means to change the amount of memory allocated to a running guest. But you still have to manually set that memory target... > Overcommitment is something entirely different and, while supported in > the open source versions of the Xen hypervisor (look up xenpaging), is > not at this time supported in XCP or commercial XenServer (to my > knowledge). Overcommitment is the idea of actually allocating more > memory to guests than you have available on your physical machines, with > the risk of running into a situation where you cannot fulfill the > required commitment level to all of the guests. Overcommitment is a > hypervisor/dom0 feature and shouldn't require any additional drivers > inside the guest to accomplish. Now THAT is a good hint! I wasn't aware of "xenpaging". We will definitely give it a try, although there is a big fat Warning right on top of "xenpaging.txt" :-/ Thanks a lot! - peter. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Mon Feb 11 00:15:36 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 11 Feb 2013 00:15: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 1U4h21-00083N-Mr; Mon, 11 Feb 2013 00: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 1U4h20-00083G-5l for xen-users@lists.xen.org; Mon, 11 Feb 2013 00:14:00 +0000 Received: from [85.158.143.99:18364] by server-1.bemta-4.messagelabs.com id BB/48-08839-7C738115; Mon, 11 Feb 2013 00:13:59 +0000 X-Env-Sender: peter.gansterer@paradigma.net X-Msg-Ref: server-16.tower-216.messagelabs.com!1360541638!18736085!1 X-Originating-IP: [213.47.215.227] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 8560 invoked from network); 11 Feb 2013 00:13:58 -0000 Received: from majere.luchs.at (HELO majere.luchs.at) (213.47.215.227) by server-16.tower-216.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 11 Feb 2013 00:13:58 -0000 Received: from localhost (localhost [127.0.0.1]) by majere.luchs.at (Postfix) with ESMTP id D3D00D007E24; Mon, 11 Feb 2013 01:13:57 +0100 (CET) X-Virus-Scanned: by majere.luchs.at Received: from majere.luchs.at ([127.0.0.1]) by localhost (majere.luchs.at [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id a4UjjDcriQJ5; Mon, 11 Feb 2013 01:13:56 +0100 (CET) Received: from earth (earth.elements.lan [10.0.0.2]) by majere.luchs.at (Postfix) with ESMTP id 3D92FD007E21; Mon, 11 Feb 2013 01:13:56 +0100 (CET) Received: from pedos (pedos.elements.lan [10.0.0.108]) by earth (Postfix) with SMTP id AFFB87ED9; Mon, 11 Feb 2013 01:13:54 +0100 (CET) Received: by pedos (sSMTP sendmail emulation); Mon, 11 Feb 2013 01:12:04 +0100 Content-Disposition: inline MIME-Version: 1.0 X-Mailer: MIME-tools 5.503 (Entity 5.503) Message-ID: <1360539932.2C5C61D27.2491@pedos> From: "Peter Gansterer" Date: Mon, 11 Feb 2013 01:12:01 +0100 In-Reply-To: <5117CABF020000990002B06B@collaborate.seakr.com> To: "Nick Couchman" Cc: xen-users Subject: Re: [Xen-users] "dynamic memory allocation" for windows guests? X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: 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 2013-02-10 16:28:47 Nick Couchman wrote: > Peter, > There are a couple of options. First, I believe recent versions of Xen > will let you set a maximum allocation and then a lower initial > allocation (XCP at least lets you do this) and you can then allocate > memory between the initial and maximum allocation. Unfortunately, due > to limitations with Windows virtualization, what actually happens is > that Xen tells Windows that is has memory at the maximum level but marks > the difference between the current allocation and the maximum allocation > as used memory. As you increase allocation up from the current > allocation to your maximum allocation it frees up the memory in that > range. This requires a driver/daemon inside of Windows to accomplish > the dynamic allocation - I think GPLPV drivers have support, and I know > the XCP/XenServer drivers include support. I am well aware of "ballooning" as a means to change the amount of memory allocated to a running guest. But you still have to manually set that memory target... > Overcommitment is something entirely different and, while supported in > the open source versions of the Xen hypervisor (look up xenpaging), is > not at this time supported in XCP or commercial XenServer (to my > knowledge). Overcommitment is the idea of actually allocating more > memory to guests than you have available on your physical machines, with > the risk of running into a situation where you cannot fulfill the > required commitment level to all of the guests. Overcommitment is a > hypervisor/dom0 feature and shouldn't require any additional drivers > inside the guest to accomplish. Now THAT is a good hint! I wasn't aware of "xenpaging". We will definitely give it a try, although there is a big fat Warning right on top of "xenpaging.txt" :-/ Thanks a lot! - peter. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Mon Feb 11 11:18:39 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 11 Feb 2013 11:18: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 1U4rNk-0000js-En; Mon, 11 Feb 2013 11:17:08 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U4rNi-0000jh-Tm for xen-users@lists.xensource.com; Mon, 11 Feb 2013 11:17:07 +0000 Received: from [85.158.138.51:41354] by server-14.bemta-3.messagelabs.com id E6/37-23533-D23D8115; Mon, 11 Feb 2013 11:17:01 +0000 X-Env-Sender: mehdi.alishahi@gmail.com X-Msg-Ref: server-10.tower-174.messagelabs.com!1360581418!24596152!1 X-Originating-IP: [74.52.4.138] X-SpamReason: No, hits=0.0 required=7.0 tests=HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 19897 invoked from network); 11 Feb 2013 11:16:58 -0000 Received: from smtp3.getafreelancer.com (HELO smtp3.getafreelancer.com) (74.52.4.138) by server-10.tower-174.messagelabs.com with SMTP; 11 Feb 2013 11:16:58 -0000 Received: from mail.getafreelancer.com (smtp1.getafreelancer.com [174.129.205.207]) by smtp3.getafreelancer.com (Postfix) with ESMTP id C5827584365 for ; Mon, 11 Feb 2013 06:16:57 -0500 (EST) Received: from localhost.localdomain (ip-10-113-17-122.ec2.internal [10.113.17.122]) by mail.getafreelancer.com (Postfix) with ESMTP id D8769604062 for ; Mon, 11 Feb 2013 11:16:57 +0000 (UTC) Received: from phpmailer by localhost.localdomain with local (PHPMailer); Mon, 11 Feb 2013 06:16:57 -0500 Date: Mon, 11 Feb 2013 06:16:57 -0500 To: xen-users@lists.xensource.com From: Mehdi Alishahi Message-ID: <435ab3275053ed173ce94f7d9f30e3db@localhost.localdomain> X-Priority: 3 (Normal) X-Mailer: Freelancer.com Generic Mailer X-Accept-Language: en MIME-Version: 1.0 Subject: [Xen-users] Mehdi Alishahi invites you to Freelancer.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: multipart/mixed; boundary="===============9050792954087273673==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============9050792954087273673== Content-Type: multipart/alternative; boundary="b1_435ab3275053ed173ce94f7d9f30e3db" --b1_435ab3275053ed173ce94f7d9f30e3db Content-Type: text/plain; charset = "utf-8" Content-Transfer-Encoding: 8bit 11 February 2013 Hi, Mehdi Alishahi is inviting you to join Freelancer.com (http://www.freelancer.com/users/6904907.html?utm_campaign=new_freelancer_invite&utm_medium=email&utm_source=freelancer&utm_content=new_freelancer_invite) Mehdi Alishahi (http://www.freelancer.com/users/6904907.html?utm_campaign=new_freelancer_invite&utm_medium=email&utm_source=freelancer&utm_content=new_freelancer_invite) 11 February 2013 Freelancer.com is the world's largest micro-outsourcing site. We have over 7,013,983 registered professionals ready to bid on your jobs and produce high quality work. The average job is under $200 USD and you can outsource anything, whether you need web design, graphic design, marketing or sales. Turbocharge your business today! Looking for work? We also have the largest network of employers ready to hire just about any skill set. Join Freelancer.com (http://www.freelancer.com/friend-invitation/join.php?id=10104762&utm_campaign=new_freelancer_invite&utm_medium=email&utm_source=freelancer&utm_content=new_freelancer_invite) xen-users@lists.xensource.com was invited to join Freelancer.com by Mehdi Alishahi. --b1_435ab3275053ed173ce94f7d9f30e3db Content-Type: text/html; charset = "utf-8" Content-Transfer-Encoding: 8bit
Freelancer 11 February 2013

Hi,
Mehdi Alishahi is inviting you to join Freelancer.com
Mehdi Alishahi
11 February 2013
Freelancer.com is the world's largest micro-outsourcing site. We have over 7,013,983 registered professionals ready to bid on your jobs and produce high quality work.
The average job is under $200 USD and you can outsource anything, whether you need web design, graphic design, marketing or sales. Turbocharge your business today!
Looking for work? We also have the largest network of employers ready to hire just about any skill set.
xen-users@lists.xensource.com was invited to join Freelancer.com by Mehdi Alishahi.
--b1_435ab3275053ed173ce94f7d9f30e3db-- --===============9050792954087273673== 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 --===============9050792954087273673==-- From xen-users-bounces@lists.xen.org Mon Feb 11 11:18:39 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 11 Feb 2013 11:18: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 1U4rNk-0000js-En; Mon, 11 Feb 2013 11:17:08 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U4rNi-0000jh-Tm for xen-users@lists.xensource.com; Mon, 11 Feb 2013 11:17:07 +0000 Received: from [85.158.138.51:41354] by server-14.bemta-3.messagelabs.com id E6/37-23533-D23D8115; Mon, 11 Feb 2013 11:17:01 +0000 X-Env-Sender: mehdi.alishahi@gmail.com X-Msg-Ref: server-10.tower-174.messagelabs.com!1360581418!24596152!1 X-Originating-IP: [74.52.4.138] X-SpamReason: No, hits=0.0 required=7.0 tests=HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 19897 invoked from network); 11 Feb 2013 11:16:58 -0000 Received: from smtp3.getafreelancer.com (HELO smtp3.getafreelancer.com) (74.52.4.138) by server-10.tower-174.messagelabs.com with SMTP; 11 Feb 2013 11:16:58 -0000 Received: from mail.getafreelancer.com (smtp1.getafreelancer.com [174.129.205.207]) by smtp3.getafreelancer.com (Postfix) with ESMTP id C5827584365 for ; Mon, 11 Feb 2013 06:16:57 -0500 (EST) Received: from localhost.localdomain (ip-10-113-17-122.ec2.internal [10.113.17.122]) by mail.getafreelancer.com (Postfix) with ESMTP id D8769604062 for ; Mon, 11 Feb 2013 11:16:57 +0000 (UTC) Received: from phpmailer by localhost.localdomain with local (PHPMailer); Mon, 11 Feb 2013 06:16:57 -0500 Date: Mon, 11 Feb 2013 06:16:57 -0500 To: xen-users@lists.xensource.com From: Mehdi Alishahi Message-ID: <435ab3275053ed173ce94f7d9f30e3db@localhost.localdomain> X-Priority: 3 (Normal) X-Mailer: Freelancer.com Generic Mailer X-Accept-Language: en MIME-Version: 1.0 Subject: [Xen-users] Mehdi Alishahi invites you to Freelancer.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: multipart/mixed; boundary="===============9050792954087273673==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============9050792954087273673== Content-Type: multipart/alternative; boundary="b1_435ab3275053ed173ce94f7d9f30e3db" --b1_435ab3275053ed173ce94f7d9f30e3db Content-Type: text/plain; charset = "utf-8" Content-Transfer-Encoding: 8bit 11 February 2013 Hi, Mehdi Alishahi is inviting you to join Freelancer.com (http://www.freelancer.com/users/6904907.html?utm_campaign=new_freelancer_invite&utm_medium=email&utm_source=freelancer&utm_content=new_freelancer_invite) Mehdi Alishahi (http://www.freelancer.com/users/6904907.html?utm_campaign=new_freelancer_invite&utm_medium=email&utm_source=freelancer&utm_content=new_freelancer_invite) 11 February 2013 Freelancer.com is the world's largest micro-outsourcing site. We have over 7,013,983 registered professionals ready to bid on your jobs and produce high quality work. The average job is under $200 USD and you can outsource anything, whether you need web design, graphic design, marketing or sales. Turbocharge your business today! Looking for work? We also have the largest network of employers ready to hire just about any skill set. Join Freelancer.com (http://www.freelancer.com/friend-invitation/join.php?id=10104762&utm_campaign=new_freelancer_invite&utm_medium=email&utm_source=freelancer&utm_content=new_freelancer_invite) xen-users@lists.xensource.com was invited to join Freelancer.com by Mehdi Alishahi. --b1_435ab3275053ed173ce94f7d9f30e3db Content-Type: text/html; charset = "utf-8" Content-Transfer-Encoding: 8bit
Freelancer 11 February 2013

Hi,
Mehdi Alishahi is inviting you to join Freelancer.com
Mehdi Alishahi
11 February 2013
Freelancer.com is the world's largest micro-outsourcing site. We have over 7,013,983 registered professionals ready to bid on your jobs and produce high quality work.
The average job is under $200 USD and you can outsource anything, whether you need web design, graphic design, marketing or sales. Turbocharge your business today!
Looking for work? We also have the largest network of employers ready to hire just about any skill set.
xen-users@lists.xensource.com was invited to join Freelancer.com by Mehdi Alishahi.
--b1_435ab3275053ed173ce94f7d9f30e3db-- --===============9050792954087273673== 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 --===============9050792954087273673==-- From xen-users-bounces@lists.xen.org Mon Feb 11 11:24:35 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 11 Feb 2013 11:24: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 1U4rTn-000176-VU; Mon, 11 Feb 2013 11:23:23 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U4rTm-00016w-5G for xen-users@lists.xen.org; Mon, 11 Feb 2013 11:23:22 +0000 Received: from [85.158.137.99:65067] by server-5.bemta-3.messagelabs.com id 78/3C-04457-9A4D8115; Mon, 11 Feb 2013 11:23:21 +0000 X-Env-Sender: Ian.Campbell@citrix.com X-Msg-Ref: server-16.tower-217.messagelabs.com!1360581800!20875015!1 X-Originating-IP: [46.33.159.39] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNDYuMzMuMTU5LjM5ID0+IDIxNzE2\n X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 29244 invoked from network); 11 Feb 2013 11:23:20 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (46.33.159.39) by server-16.tower-217.messagelabs.com with RC4-SHA encrypted SMTP; 11 Feb 2013 11:23:20 -0000 X-IronPort-AV: E=Sophos;i="4.84,641,1355097600"; d="scan'208";a="1325253" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 11 Feb 2013 11:22:21 +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.297.1; Mon, 11 Feb 2013 11:22:20 +0000 Message-ID: <1360581739.29432.115.camel@zakaz.uk.xensource.com> From: Ian Campbell To: Matthias Date: Mon, 11 Feb 2013 11:22:19 +0000 In-Reply-To: References: Organization: Citrix Systems, Inc. X-Mailer: Evolution 3.4.4-1 MIME-Version: 1.0 Cc: "boris.ostrovsky@amd.com" , "jbeulich@suse.com" , "xen-users@lists.xen.org" Subject: Re: [Xen-users] Latest AMD, IOMMU Security Change causing CPU0 Panic and general Problems with AMD+IOMMU changes X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: 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, 2013-02-09 at 02:12 +0000, Matthias wrote: > Hi, > > unfortunatly your latest change "AMD,IOMMU: Clean up old entries in > remapping tables when creating new one" (Changeset 26517 in > xen-unstable and 25975 in xen-4.2-testing) is causing a CPU0 Panic at > boot for me. > > When i tried to boot latest versions of xen unstable or xen-testing, > my dom0 gives me the message: > > (XEN) ************************************* > (XEN) Panic on CPU 0: > (XEN) DATAL PAGE FAULT > (XEN) [error_code=0000] > (XEN) Faulting linear address: 0000000000000000 > (XEN) ************************************* I think this is fixed by "[PATCH 1/2] AMD IOMMU: also spot missing IO-APIC entries in IVRS table" posted to xen-devel on Wednesday. Message-ID <511264B402000078000BC754@nat28.tlf.novell.com> Ian. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Mon Feb 11 11:24:35 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 11 Feb 2013 11:24: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 1U4rTn-000176-VU; Mon, 11 Feb 2013 11:23:23 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U4rTm-00016w-5G for xen-users@lists.xen.org; Mon, 11 Feb 2013 11:23:22 +0000 Received: from [85.158.137.99:65067] by server-5.bemta-3.messagelabs.com id 78/3C-04457-9A4D8115; Mon, 11 Feb 2013 11:23:21 +0000 X-Env-Sender: Ian.Campbell@citrix.com X-Msg-Ref: server-16.tower-217.messagelabs.com!1360581800!20875015!1 X-Originating-IP: [46.33.159.39] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNDYuMzMuMTU5LjM5ID0+IDIxNzE2\n X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 29244 invoked from network); 11 Feb 2013 11:23:20 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (46.33.159.39) by server-16.tower-217.messagelabs.com with RC4-SHA encrypted SMTP; 11 Feb 2013 11:23:20 -0000 X-IronPort-AV: E=Sophos;i="4.84,641,1355097600"; d="scan'208";a="1325253" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 11 Feb 2013 11:22:21 +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.297.1; Mon, 11 Feb 2013 11:22:20 +0000 Message-ID: <1360581739.29432.115.camel@zakaz.uk.xensource.com> From: Ian Campbell To: Matthias Date: Mon, 11 Feb 2013 11:22:19 +0000 In-Reply-To: References: Organization: Citrix Systems, Inc. X-Mailer: Evolution 3.4.4-1 MIME-Version: 1.0 Cc: "boris.ostrovsky@amd.com" , "jbeulich@suse.com" , "xen-users@lists.xen.org" Subject: Re: [Xen-users] Latest AMD, IOMMU Security Change causing CPU0 Panic and general Problems with AMD+IOMMU changes X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: 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, 2013-02-09 at 02:12 +0000, Matthias wrote: > Hi, > > unfortunatly your latest change "AMD,IOMMU: Clean up old entries in > remapping tables when creating new one" (Changeset 26517 in > xen-unstable and 25975 in xen-4.2-testing) is causing a CPU0 Panic at > boot for me. > > When i tried to boot latest versions of xen unstable or xen-testing, > my dom0 gives me the message: > > (XEN) ************************************* > (XEN) Panic on CPU 0: > (XEN) DATAL PAGE FAULT > (XEN) [error_code=0000] > (XEN) Faulting linear address: 0000000000000000 > (XEN) ************************************* I think this is fixed by "[PATCH 1/2] AMD IOMMU: also spot missing IO-APIC entries in IVRS table" posted to xen-devel on Wednesday. Message-ID <511264B402000078000BC754@nat28.tlf.novell.com> Ian. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Mon Feb 11 15:02:23 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 11 Feb 2013 15:02: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 1U4us8-00063J-FF; Mon, 11 Feb 2013 15:00:44 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U4us7-00063E-I8 for xen-users@lists.xen.org; Mon, 11 Feb 2013 15:00:43 +0000 Received: from [85.158.139.83:33313] by server-12.bemta-5.messagelabs.com id AC/7F-20195-A9709115; Mon, 11 Feb 2013 15:00:42 +0000 X-Env-Sender: Markus@hochholdinger.net X-Msg-Ref: server-2.tower-182.messagelabs.com!1360594802!31348120!1 X-Originating-IP: [89.19.235.135] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 18203 invoked from network); 11 Feb 2013 15:00:02 -0000 Received: from group.wh-serverpark.com (HELO group.wh-serverpark.com) (89.19.235.135) by server-2.tower-182.messagelabs.com with SMTP; 11 Feb 2013 15:00:02 -0000 Received: from localhost (localhost [127.0.0.1]) by group.wh-serverpark.com (Postfix) with ESMTP id B09A298016; Mon, 11 Feb 2013 16:00:01 +0100 (CET) X-Virus-Scanned: amavisd-new at valiant.wh-serverpark.com Received: from group.wh-serverpark.com ([127.0.0.1]) by localhost (group.wh-serverpark.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xrRyVoQgXqcC; Mon, 11 Feb 2013 16:00:00 +0100 (CET) Received: from enterprise.localnet (et-0-30.gw-nat.bs.kae.de.oneandone.net [212.227.35.94]) by group.wh-serverpark.com (Postfix) with ESMTPSA id 5E9AF98014; Mon, 11 Feb 2013 15:59:59 +0100 (CET) From: Markus Hochholdinger To: xen-users@lists.xen.org Date: Mon, 11 Feb 2013 15:59:54 +0100 User-Agent: KMail/1.13.7 (Linux/3.2.0-4-amd64; KDE/4.8.4; x86_64; ; ) References: <201301291646.43567.Markus@hochholdinger.net> <1359708995.9063.3.camel@dagon.hellion.org.uk> <201302061539.40900.Markus@hochholdinger.net> In-Reply-To: <201302061539.40900.Markus@hochholdinger.net> MIME-Version: 1.0 X-UID: 780931 Message-Id: <201302111559.58269.Markus@hochholdinger.net> Cc: Ian Campbell Subject: Re: [Xen-users] linux stubdom X-BeenThere: xen-users@lists.xen.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="===============8243261571493586516==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============8243261571493586516== Content-Type: multipart/signed; boundary="nextPart2842776.hFoqWTmuye"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit --nextPart2842776.hFoqWTmuye Content-Type: Text/Plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Hello, Am 06.02.2013 um 15:39 Uhr schrieb Markus Hochholdinger=20 : > Am 01.02.2013 um 09:56 Uhr schrieb Ian Campbell : [..] > > > executed? Would this be between #3 and #7? > > It is part of the device teardown and setup, so it is during #5 and #6 > > (strictly I think it is just after #5 and just before #6). > > On xen-devel at the minute there is a patch series under discussion to > > make the script hooks more flexible, in particular adding pre and post > > migrate hooks (called something like #1-#3 and #7-#7) which can pre > > setup bits of the storage stack which are safe to do with the guest > > running but might be slow to initialise (e.g. iSCSI login, but not > > opening the device). I don't think this needs to affect you though. > at least with xm toolstack, block-scripts in /etc/xen/scripts/block-* are > executed on the destination host (add) before the script (remove) on the > source host is executed while live migrating a domU. > (I've created the script /etc/xen/scripts/block-md which assembles and > stops raid1 devices.) > Next, I'll test xl toolstack with this setup. with Xen 4.1 there's no support for custom scripts within libxl. With Xen 4.2.1 there's support for custom scripts (like with xm toolstack) = but=20 also only add/remove. And add is called on the destination side before remo= ve=20 is called on the transmitting side while doing a live migration of a domU. Next I'll test latest development version... =2D-=20 greetings eMHa --nextPart2842776.hFoqWTmuye Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (GNU/Linux) iEYEABECAAYFAlEZB2sACgkQXT3LE+AjWCtnMQCfTPP5QB+fp4cA1rPO3DF2qxZS HJkAoIHUgJF34lYMwgUNDG2rYNGlk5zw =Uwwn -----END PGP SIGNATURE----- --nextPart2842776.hFoqWTmuye-- --===============8243261571493586516== 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 --===============8243261571493586516==-- From xen-users-bounces@lists.xen.org Mon Feb 11 15:02:23 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 11 Feb 2013 15:02: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 1U4us8-00063J-FF; Mon, 11 Feb 2013 15:00:44 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U4us7-00063E-I8 for xen-users@lists.xen.org; Mon, 11 Feb 2013 15:00:43 +0000 Received: from [85.158.139.83:33313] by server-12.bemta-5.messagelabs.com id AC/7F-20195-A9709115; Mon, 11 Feb 2013 15:00:42 +0000 X-Env-Sender: Markus@hochholdinger.net X-Msg-Ref: server-2.tower-182.messagelabs.com!1360594802!31348120!1 X-Originating-IP: [89.19.235.135] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 18203 invoked from network); 11 Feb 2013 15:00:02 -0000 Received: from group.wh-serverpark.com (HELO group.wh-serverpark.com) (89.19.235.135) by server-2.tower-182.messagelabs.com with SMTP; 11 Feb 2013 15:00:02 -0000 Received: from localhost (localhost [127.0.0.1]) by group.wh-serverpark.com (Postfix) with ESMTP id B09A298016; Mon, 11 Feb 2013 16:00:01 +0100 (CET) X-Virus-Scanned: amavisd-new at valiant.wh-serverpark.com Received: from group.wh-serverpark.com ([127.0.0.1]) by localhost (group.wh-serverpark.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xrRyVoQgXqcC; Mon, 11 Feb 2013 16:00:00 +0100 (CET) Received: from enterprise.localnet (et-0-30.gw-nat.bs.kae.de.oneandone.net [212.227.35.94]) by group.wh-serverpark.com (Postfix) with ESMTPSA id 5E9AF98014; Mon, 11 Feb 2013 15:59:59 +0100 (CET) From: Markus Hochholdinger To: xen-users@lists.xen.org Date: Mon, 11 Feb 2013 15:59:54 +0100 User-Agent: KMail/1.13.7 (Linux/3.2.0-4-amd64; KDE/4.8.4; x86_64; ; ) References: <201301291646.43567.Markus@hochholdinger.net> <1359708995.9063.3.camel@dagon.hellion.org.uk> <201302061539.40900.Markus@hochholdinger.net> In-Reply-To: <201302061539.40900.Markus@hochholdinger.net> MIME-Version: 1.0 X-UID: 780931 Message-Id: <201302111559.58269.Markus@hochholdinger.net> Cc: Ian Campbell Subject: Re: [Xen-users] linux stubdom X-BeenThere: xen-users@lists.xen.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="===============8243261571493586516==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============8243261571493586516== Content-Type: multipart/signed; boundary="nextPart2842776.hFoqWTmuye"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit --nextPart2842776.hFoqWTmuye Content-Type: Text/Plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Hello, Am 06.02.2013 um 15:39 Uhr schrieb Markus Hochholdinger=20 : > Am 01.02.2013 um 09:56 Uhr schrieb Ian Campbell : [..] > > > executed? Would this be between #3 and #7? > > It is part of the device teardown and setup, so it is during #5 and #6 > > (strictly I think it is just after #5 and just before #6). > > On xen-devel at the minute there is a patch series under discussion to > > make the script hooks more flexible, in particular adding pre and post > > migrate hooks (called something like #1-#3 and #7-#7) which can pre > > setup bits of the storage stack which are safe to do with the guest > > running but might be slow to initialise (e.g. iSCSI login, but not > > opening the device). I don't think this needs to affect you though. > at least with xm toolstack, block-scripts in /etc/xen/scripts/block-* are > executed on the destination host (add) before the script (remove) on the > source host is executed while live migrating a domU. > (I've created the script /etc/xen/scripts/block-md which assembles and > stops raid1 devices.) > Next, I'll test xl toolstack with this setup. with Xen 4.1 there's no support for custom scripts within libxl. With Xen 4.2.1 there's support for custom scripts (like with xm toolstack) = but=20 also only add/remove. And add is called on the destination side before remo= ve=20 is called on the transmitting side while doing a live migration of a domU. Next I'll test latest development version... =2D-=20 greetings eMHa --nextPart2842776.hFoqWTmuye Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (GNU/Linux) iEYEABECAAYFAlEZB2sACgkQXT3LE+AjWCtnMQCfTPP5QB+fp4cA1rPO3DF2qxZS HJkAoIHUgJF34lYMwgUNDG2rYNGlk5zw =Uwwn -----END PGP SIGNATURE----- --nextPart2842776.hFoqWTmuye-- --===============8243261571493586516== 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 --===============8243261571493586516==-- From xen-users-bounces@lists.xen.org Mon Feb 11 15:06:38 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 11 Feb 2013 15:06: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 1U4uwa-0006FE-Dn; Mon, 11 Feb 2013 15:05:20 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U4uwY-0006F7-To for xen-users@lists.xen.org; Mon, 11 Feb 2013 15:05:19 +0000 Received: from [85.158.138.51:38495] by server-16.bemta-3.messagelabs.com id 1F/05-02727-EA809115; Mon, 11 Feb 2013 15:05:18 +0000 X-Env-Sender: Ian.Campbell@citrix.com X-Msg-Ref: server-5.tower-174.messagelabs.com!1360595117!29740158!1 X-Originating-IP: [46.33.159.39] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNDYuMzMuMTU5LjM5ID0+IDIxNzE2\n X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 11932 invoked from network); 11 Feb 2013 15:05:17 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (46.33.159.39) by server-5.tower-174.messagelabs.com with RC4-SHA encrypted SMTP; 11 Feb 2013 15:05:17 -0000 X-IronPort-AV: E=Sophos;i="4.84,643,1355097600"; d="scan'208";a="1334330" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 11 Feb 2013 15:05: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.297.1; Mon, 11 Feb 2013 15:05:17 +0000 Message-ID: <1360595115.20449.51.camel@zakaz.uk.xensource.com> From: Ian Campbell To: Markus Hochholdinger Date: Mon, 11 Feb 2013 15:05:15 +0000 In-Reply-To: <201302111559.58269.Markus@hochholdinger.net> References: <201301291646.43567.Markus@hochholdinger.net> <1359708995.9063.3.camel@dagon.hellion.org.uk> <201302061539.40900.Markus@hochholdinger.net> <201302111559.58269.Markus@hochholdinger.net> Organization: Citrix Systems, Inc. X-Mailer: Evolution 3.4.4-1 MIME-Version: 1.0 Cc: "xen-users@lists.xen.org" , Roger Pau Monne Subject: Re: [Xen-users] linux stubdom X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: 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, 2013-02-11 at 14:59 +0000, Markus Hochholdinger wrote: > Hello, > > Am 06.02.2013 um 15:39 Uhr schrieb Markus Hochholdinger > : > > Am 01.02.2013 um 09:56 Uhr schrieb Ian Campbell : > [..] > > > > executed? Would this be between #3 and #7? > > > It is part of the device teardown and setup, so it is during #5 and #6 > > > (strictly I think it is just after #5 and just before #6). > > > On xen-devel at the minute there is a patch series under discussion to > > > make the script hooks more flexible, in particular adding pre and post > > > migrate hooks (called something like #1-#3 and #7-#7) which can pre > > > setup bits of the storage stack which are safe to do with the guest > > > running but might be slow to initialise (e.g. iSCSI login, but not > > > opening the device). I don't think this needs to affect you though. > > at least with xm toolstack, block-scripts in /etc/xen/scripts/block-* are > > executed on the destination host (add) before the script (remove) on the > > source host is executed while live migrating a domU. > > (I've created the script /etc/xen/scripts/block-md which assembles and > > stops raid1 devices.) > > Next, I'll test xl toolstack with this setup. > > with Xen 4.1 there's no support for custom scripts within libxl. > > With Xen 4.2.1 there's support for custom scripts (like with xm toolstack) but > also only add/remove. And add is called on the destination side before remove > is called on the transmitting side while doing a live migration of a domU. This sounds like a bug which ought to be addressed (Roger, can you take a look?) > Next I'll test latest development version... I'm not sure it will differ from 4.2.x in this area (yet). Roger can probably advise better than me though. Ian. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Mon Feb 11 15:06:38 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 11 Feb 2013 15:06: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 1U4uwa-0006FE-Dn; Mon, 11 Feb 2013 15:05:20 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U4uwY-0006F7-To for xen-users@lists.xen.org; Mon, 11 Feb 2013 15:05:19 +0000 Received: from [85.158.138.51:38495] by server-16.bemta-3.messagelabs.com id 1F/05-02727-EA809115; Mon, 11 Feb 2013 15:05:18 +0000 X-Env-Sender: Ian.Campbell@citrix.com X-Msg-Ref: server-5.tower-174.messagelabs.com!1360595117!29740158!1 X-Originating-IP: [46.33.159.39] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNDYuMzMuMTU5LjM5ID0+IDIxNzE2\n X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 11932 invoked from network); 11 Feb 2013 15:05:17 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (46.33.159.39) by server-5.tower-174.messagelabs.com with RC4-SHA encrypted SMTP; 11 Feb 2013 15:05:17 -0000 X-IronPort-AV: E=Sophos;i="4.84,643,1355097600"; d="scan'208";a="1334330" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 11 Feb 2013 15:05: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.297.1; Mon, 11 Feb 2013 15:05:17 +0000 Message-ID: <1360595115.20449.51.camel@zakaz.uk.xensource.com> From: Ian Campbell To: Markus Hochholdinger Date: Mon, 11 Feb 2013 15:05:15 +0000 In-Reply-To: <201302111559.58269.Markus@hochholdinger.net> References: <201301291646.43567.Markus@hochholdinger.net> <1359708995.9063.3.camel@dagon.hellion.org.uk> <201302061539.40900.Markus@hochholdinger.net> <201302111559.58269.Markus@hochholdinger.net> Organization: Citrix Systems, Inc. X-Mailer: Evolution 3.4.4-1 MIME-Version: 1.0 Cc: "xen-users@lists.xen.org" , Roger Pau Monne Subject: Re: [Xen-users] linux stubdom X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: 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, 2013-02-11 at 14:59 +0000, Markus Hochholdinger wrote: > Hello, > > Am 06.02.2013 um 15:39 Uhr schrieb Markus Hochholdinger > : > > Am 01.02.2013 um 09:56 Uhr schrieb Ian Campbell : > [..] > > > > executed? Would this be between #3 and #7? > > > It is part of the device teardown and setup, so it is during #5 and #6 > > > (strictly I think it is just after #5 and just before #6). > > > On xen-devel at the minute there is a patch series under discussion to > > > make the script hooks more flexible, in particular adding pre and post > > > migrate hooks (called something like #1-#3 and #7-#7) which can pre > > > setup bits of the storage stack which are safe to do with the guest > > > running but might be slow to initialise (e.g. iSCSI login, but not > > > opening the device). I don't think this needs to affect you though. > > at least with xm toolstack, block-scripts in /etc/xen/scripts/block-* are > > executed on the destination host (add) before the script (remove) on the > > source host is executed while live migrating a domU. > > (I've created the script /etc/xen/scripts/block-md which assembles and > > stops raid1 devices.) > > Next, I'll test xl toolstack with this setup. > > with Xen 4.1 there's no support for custom scripts within libxl. > > With Xen 4.2.1 there's support for custom scripts (like with xm toolstack) but > also only add/remove. And add is called on the destination side before remove > is called on the transmitting side while doing a live migration of a domU. This sounds like a bug which ought to be addressed (Roger, can you take a look?) > Next I'll test latest development version... I'm not sure it will differ from 4.2.x in this area (yet). Roger can probably advise better than me though. Ian. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Mon Feb 11 15:08:20 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 11 Feb 2013 15:08: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 1U4uyF-0006Mz-8a; Mon, 11 Feb 2013 15:07:03 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U4uyE-0006Mm-D3; Mon, 11 Feb 2013 15:07:02 +0000 Received: from [85.158.143.35:30304] by server-2.bemta-4.messagelabs.com id 42/C0-01597-51909115; Mon, 11 Feb 2013 15:07:01 +0000 X-Env-Sender: Ian.Campbell@citrix.com X-Msg-Ref: server-8.tower-21.messagelabs.com!1360595211!12444533!1 X-Originating-IP: [46.33.159.39] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNDYuMzMuMTU5LjM5ID0+IDIxNzE2\n X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 30900 invoked from network); 11 Feb 2013 15:06:52 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (46.33.159.39) by server-8.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 11 Feb 2013 15:06:52 -0000 X-IronPort-AV: E=Sophos;i="4.84,643,1355097600"; d="scan'208";a="1334394" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 11 Feb 2013 15:06:51 +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.297.1; Mon, 11 Feb 2013 15:06:51 +0000 Message-ID: <1360595210.20449.52.camel@zakaz.uk.xensource.com> From: Ian Campbell To: Fabiano Francesconi Date: Mon, 11 Feb 2013 15:06:50 +0000 In-Reply-To: <9E695C71278D43F7A53208C5BF34FBA3@gmail.com> References: <9E695C71278D43F7A53208C5BF34FBA3@gmail.com> Organization: Citrix Systems, Inc. X-Mailer: Evolution 3.4.4-1 MIME-Version: 1.0 Cc: xen-users@lists.xen.org Subject: Re: [Xen-users] [Xen-devel] Xen 4.2.0: unable to add disk 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 This seems like a -users question to me, please try and pick the appropriate list for your questions. I've moved this there. On Mon, 2013-02-11 at 14:53 +0000, Fabiano Francesconi wrote: > Is there a way to reload all the stuff I've removed? Rebooting is the most obvious way to reset to a known good state quickly. You could also try restarting the "xencommons" service. However the only thing which should be in xenstore at start of day is the domain 0 name, the rest should be created on the fly as needed, and what you have now looks a lot like a fresh system to me, so I'm not quite sure what is causing your issue. I'm not 100% sure but perhaps this has also broken the backend driver's watches on the xenstore. But I thought they were path based, rather than based on the specific node, and so shouldn't be affected but perhaps I am mistaken. Anyway, you could try rmmod and modprobe all of the Xen related modules in your kernel (assuming they are mostly modular). Ian. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Mon Feb 11 15:08:20 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 11 Feb 2013 15:08: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 1U4uyF-0006Mz-8a; Mon, 11 Feb 2013 15:07:03 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U4uyE-0006Mm-D3; Mon, 11 Feb 2013 15:07:02 +0000 Received: from [85.158.143.35:30304] by server-2.bemta-4.messagelabs.com id 42/C0-01597-51909115; Mon, 11 Feb 2013 15:07:01 +0000 X-Env-Sender: Ian.Campbell@citrix.com X-Msg-Ref: server-8.tower-21.messagelabs.com!1360595211!12444533!1 X-Originating-IP: [46.33.159.39] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNDYuMzMuMTU5LjM5ID0+IDIxNzE2\n X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 30900 invoked from network); 11 Feb 2013 15:06:52 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (46.33.159.39) by server-8.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 11 Feb 2013 15:06:52 -0000 X-IronPort-AV: E=Sophos;i="4.84,643,1355097600"; d="scan'208";a="1334394" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 11 Feb 2013 15:06:51 +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.297.1; Mon, 11 Feb 2013 15:06:51 +0000 Message-ID: <1360595210.20449.52.camel@zakaz.uk.xensource.com> From: Ian Campbell To: Fabiano Francesconi Date: Mon, 11 Feb 2013 15:06:50 +0000 In-Reply-To: <9E695C71278D43F7A53208C5BF34FBA3@gmail.com> References: <9E695C71278D43F7A53208C5BF34FBA3@gmail.com> Organization: Citrix Systems, Inc. X-Mailer: Evolution 3.4.4-1 MIME-Version: 1.0 Cc: xen-users@lists.xen.org Subject: Re: [Xen-users] [Xen-devel] Xen 4.2.0: unable to add disk 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 This seems like a -users question to me, please try and pick the appropriate list for your questions. I've moved this there. On Mon, 2013-02-11 at 14:53 +0000, Fabiano Francesconi wrote: > Is there a way to reload all the stuff I've removed? Rebooting is the most obvious way to reset to a known good state quickly. You could also try restarting the "xencommons" service. However the only thing which should be in xenstore at start of day is the domain 0 name, the rest should be created on the fly as needed, and what you have now looks a lot like a fresh system to me, so I'm not quite sure what is causing your issue. I'm not 100% sure but perhaps this has also broken the backend driver's watches on the xenstore. But I thought they were path based, rather than based on the specific node, and so shouldn't be affected but perhaps I am mistaken. Anyway, you could try rmmod and modprobe all of the Xen related modules in your kernel (assuming they are mostly modular). Ian. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Mon Feb 11 15:13:46 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 11 Feb 2013 15:13: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 1U4v3s-0006nh-E0; Mon, 11 Feb 2013 15:12:52 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U4v3o-0006nM-Nz for xen-users@lists.xen.org; Mon, 11 Feb 2013 15:12:50 +0000 Received: from [85.158.139.83:35739] by server-14.bemta-5.messagelabs.com id 38/82-06967-F6A09115; Mon, 11 Feb 2013 15:12:47 +0000 X-Env-Sender: fabiano.francesconi@gmail.com X-Msg-Ref: server-6.tower-182.messagelabs.com!1360595567!24779984!1 X-Originating-IP: [74.125.83.54] X-SpamReason: No, hits=0.0 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, spamassassin: X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 10437 invoked from network); 11 Feb 2013 15:12:47 -0000 Received: from mail-ee0-f54.google.com (HELO mail-ee0-f54.google.com) (74.125.83.54) by server-6.tower-182.messagelabs.com with RC4-SHA encrypted SMTP; 11 Feb 2013 15:12:47 -0000 Received: by mail-ee0-f54.google.com with SMTP id c41so3173078eek.27 for ; Mon, 11 Feb 2013 07:12:46 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:date:from:to:message-id:in-reply-to:references:subject :x-mailer:mime-version:content-type:content-transfer-encoding :content-disposition; bh=qKawfDs8tFhsKvBRKnnb8leRHWQ6nU6G5HeXdlPTSfk=; b=h++QXXVd/s8I3lTPLixYvAzm0RsCE0SHIB35KYZbTW/P+kLz10jdKQGUtx28QmqYa4 arl0lEv7xmlZsYnUC4W69ulDmp+vdZwYKZOy1WOIRysEQO8mBo47CWjztMFBpyPPef34 8otCPV8IVjqidid+xvRy4WZ7pWciOqPo4W1AstjAq7dsBYZguTT+qiFOgw3iiWCAWuUj YzEKjbqmbADRue2cnQH4S8YXlyrU5FWV1BETTr+kiUPZ3hRh7Ca5x6ZqpKkUbhCr12g3 Fd3XUt0FVZ8+tHfd03k7YJUwZFYZmuC0Gk2nImsHRJvAD8o+3oLHnQpjmwoScVbAvJWo tNrg== X-Received: by 10.14.0.135 with SMTP id 7mr27234786eeb.5.1360595566722; Mon, 11 Feb 2013 07:12:46 -0800 (PST) Received: from [192.168.0.145] (host111-111-dynamic.14-87-r.retail.telecomitalia.it. [87.14.111.111]) by mx.google.com with ESMTPS id k7sm60342314een.8.2013.02.11.07.12.45 (version=TLSv1 cipher=RC4-SHA bits=128/128); Mon, 11 Feb 2013 07:12:45 -0800 (PST) Date: Mon, 11 Feb 2013 16:12:43 +0100 From: Fabiano Francesconi To: xen-users@lists.xen.org Message-ID: In-Reply-To: <1360595210.20449.52.camel@zakaz.uk.xensource.com> References: <9E695C71278D43F7A53208C5BF34FBA3@gmail.com> <1360595210.20449.52.camel@zakaz.uk.xensource.com> X-Mailer: sparrow 1.6.4 (build 1176) MIME-Version: 1.0 Content-Disposition: inline Subject: Re: [Xen-users] [Xen-devel] Xen 4.2.0: unable to add disk 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 On Monday 11 February 2013 at 16:06, Ian Campbell wrote: > This seems like a -users question to me, please try and pick the > appropriate list for your questions. I've moved this there. Sorry and thank you! > > On Mon, 2013-02-11 at 14:53 +0000, Fabiano Francesconi wrote: > > Is there a way to reload all the stuff I've removed? > > > > Rebooting is the most obvious way to reset to a known good state > quickly. > > You could also try restarting the "xencommons" service. > > However the only thing which should be in xenstore at start of day is > the domain 0 name, the rest should be created on the fly as needed, and > what you have now looks a lot like a fresh system to me, so I'm not > quite sure what is causing your issue. > > I'm not 100% sure but perhaps this has also broken the backend driver's > watches on the xenstore. But I thought they were path based, rather than > based on the specific node, and so shouldn't be affected but perhaps I > am mistaken. Anyway, you could try rmmod and modprobe all of the Xen > related modules in your kernel (assuming they are mostly modular). > > Ian. Rebooting solved the issue. I tried rebooting twice, before, but it didn't help. This time I completely turned off the server and turned it back on. Sorry but it is the whole day that I'm working on these machines and I hurried up writing here while I should have spent more time digging into it by myself. Still, thank you very much. -- Fabiano Francesconi _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Mon Feb 11 15:13:46 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 11 Feb 2013 15:13: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 1U4v3s-0006nh-E0; Mon, 11 Feb 2013 15:12:52 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U4v3o-0006nM-Nz for xen-users@lists.xen.org; Mon, 11 Feb 2013 15:12:50 +0000 Received: from [85.158.139.83:35739] by server-14.bemta-5.messagelabs.com id 38/82-06967-F6A09115; Mon, 11 Feb 2013 15:12:47 +0000 X-Env-Sender: fabiano.francesconi@gmail.com X-Msg-Ref: server-6.tower-182.messagelabs.com!1360595567!24779984!1 X-Originating-IP: [74.125.83.54] X-SpamReason: No, hits=0.0 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, spamassassin: X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 10437 invoked from network); 11 Feb 2013 15:12:47 -0000 Received: from mail-ee0-f54.google.com (HELO mail-ee0-f54.google.com) (74.125.83.54) by server-6.tower-182.messagelabs.com with RC4-SHA encrypted SMTP; 11 Feb 2013 15:12:47 -0000 Received: by mail-ee0-f54.google.com with SMTP id c41so3173078eek.27 for ; Mon, 11 Feb 2013 07:12:46 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:date:from:to:message-id:in-reply-to:references:subject :x-mailer:mime-version:content-type:content-transfer-encoding :content-disposition; bh=qKawfDs8tFhsKvBRKnnb8leRHWQ6nU6G5HeXdlPTSfk=; b=h++QXXVd/s8I3lTPLixYvAzm0RsCE0SHIB35KYZbTW/P+kLz10jdKQGUtx28QmqYa4 arl0lEv7xmlZsYnUC4W69ulDmp+vdZwYKZOy1WOIRysEQO8mBo47CWjztMFBpyPPef34 8otCPV8IVjqidid+xvRy4WZ7pWciOqPo4W1AstjAq7dsBYZguTT+qiFOgw3iiWCAWuUj YzEKjbqmbADRue2cnQH4S8YXlyrU5FWV1BETTr+kiUPZ3hRh7Ca5x6ZqpKkUbhCr12g3 Fd3XUt0FVZ8+tHfd03k7YJUwZFYZmuC0Gk2nImsHRJvAD8o+3oLHnQpjmwoScVbAvJWo tNrg== X-Received: by 10.14.0.135 with SMTP id 7mr27234786eeb.5.1360595566722; Mon, 11 Feb 2013 07:12:46 -0800 (PST) Received: from [192.168.0.145] (host111-111-dynamic.14-87-r.retail.telecomitalia.it. [87.14.111.111]) by mx.google.com with ESMTPS id k7sm60342314een.8.2013.02.11.07.12.45 (version=TLSv1 cipher=RC4-SHA bits=128/128); Mon, 11 Feb 2013 07:12:45 -0800 (PST) Date: Mon, 11 Feb 2013 16:12:43 +0100 From: Fabiano Francesconi To: xen-users@lists.xen.org Message-ID: In-Reply-To: <1360595210.20449.52.camel@zakaz.uk.xensource.com> References: <9E695C71278D43F7A53208C5BF34FBA3@gmail.com> <1360595210.20449.52.camel@zakaz.uk.xensource.com> X-Mailer: sparrow 1.6.4 (build 1176) MIME-Version: 1.0 Content-Disposition: inline Subject: Re: [Xen-users] [Xen-devel] Xen 4.2.0: unable to add disk 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 On Monday 11 February 2013 at 16:06, Ian Campbell wrote: > This seems like a -users question to me, please try and pick the > appropriate list for your questions. I've moved this there. Sorry and thank you! > > On Mon, 2013-02-11 at 14:53 +0000, Fabiano Francesconi wrote: > > Is there a way to reload all the stuff I've removed? > > > > Rebooting is the most obvious way to reset to a known good state > quickly. > > You could also try restarting the "xencommons" service. > > However the only thing which should be in xenstore at start of day is > the domain 0 name, the rest should be created on the fly as needed, and > what you have now looks a lot like a fresh system to me, so I'm not > quite sure what is causing your issue. > > I'm not 100% sure but perhaps this has also broken the backend driver's > watches on the xenstore. But I thought they were path based, rather than > based on the specific node, and so shouldn't be affected but perhaps I > am mistaken. Anyway, you could try rmmod and modprobe all of the Xen > related modules in your kernel (assuming they are mostly modular). > > Ian. Rebooting solved the issue. I tried rebooting twice, before, but it didn't help. This time I completely turned off the server and turned it back on. Sorry but it is the whole day that I'm working on these machines and I hurried up writing here while I should have spent more time digging into it by myself. Still, thank you very much. -- Fabiano Francesconi _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Mon Feb 11 15:28:34 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 11 Feb 2013 15:28: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 1U4vIP-0007MJ-6U; Mon, 11 Feb 2013 15:27:53 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U4vIN-0007ME-OO for xen-users@lists.xen.org; Mon, 11 Feb 2013 15:27:51 +0000 Received: from [193.109.254.147:26125] by server-6.bemta-14.messagelabs.com id C8/3D-12010-6FD09115; Mon, 11 Feb 2013 15:27:50 +0000 X-Env-Sender: fabiano.francesconi@gmail.com X-Msg-Ref: server-11.tower-27.messagelabs.com!1360596413!2444767!1 X-Originating-IP: [209.85.215.175] 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.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 22572 invoked from network); 11 Feb 2013 15:26:53 -0000 Received: from mail-ea0-f175.google.com (HELO mail-ea0-f175.google.com) (209.85.215.175) by server-11.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 11 Feb 2013 15:26:53 -0000 Received: by mail-ea0-f175.google.com with SMTP id d1so2687138eab.6 for ; Mon, 11 Feb 2013 07:25:54 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:date:from:to:message-id:subject:x-mailer:mime-version :content-type:content-transfer-encoding:content-disposition; bh=P2QL3sb1KyriW8ZrTfRb+qx69jesVhK0Rhkex6ERkZQ=; b=NiPZ75HXy+KZcjlf7e/B2N7nfLOJf6y84M8I8kse7UeYxgxMKh5rQdtoT7dSRbBAfL 6u7oriLmeL24aYGs//2Q9wJAPoXAWs+0zK+9Q3XBqP43SkRYCJkGf2bR5loKUxFZD7dL nvAnbMV9DT0+sUYBbrI3e3fRejabG2TikdcxRlGEKOhCY4HvJrMqccpEMpbNtPd7Wn6I TPhWO0Ih3FKdpmdUR0JYMQ+W/E6kJDafQ8Cucy8wUYQmYQieG653J9dB0jeOnJmSSpg9 t+IqYCthayOrG+OB8rs6uDL7N8E32oQR/JtCWmryNYORmxT1ueEoqUymOujvbBGfUq2L cZTw== X-Received: by 10.14.225.133 with SMTP id z5mr51284524eep.15.1360596354036; Mon, 11 Feb 2013 07:25:54 -0800 (PST) Received: from [192.168.0.145] (host111-111-dynamic.14-87-r.retail.telecomitalia.it. [87.14.111.111]) by mx.google.com with ESMTPS id q5sm63063835eep.11.2013.02.11.07.25.52 (version=TLSv1 cipher=RC4-SHA bits=128/128); Mon, 11 Feb 2013 07:25:53 -0800 (PST) Date: Mon, 11 Feb 2013 16:25:51 +0100 From: Fabiano Francesconi To: xen-users@lists.xen.org Message-ID: <3C0CB81079134B2586C4CB56AC211233@gmail.com> X-Mailer: sparrow 1.6.4 (build 1176) MIME-Version: 1.0 Content-Disposition: inline Subject: [Xen-users] Xen domU PV linux-3.7.0-hardened won'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: 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 everybody, today I was trying to update my domU to linux kernel v3. At the moment it's running with a 2.6.38 kernel and it's running smooth. I simply took the .config and run a make oldconfig in linux v3 sources and what I get is that it won't boot. No kernel bootlog to inspect. I'm running xen 4.2.0 on a 32bit paravirt environment. The dom0 kernel is Linux 3.3.8 and the other domU machine I have is running with the same version of the kernel. The sole machine that is giving me troubles is the hardened one, currently running with grsec+pax on the 2.6.38. This is my current configuration: - kernel config file (domU): http://codepad.org/sgnyXLqL - domU configuration file (xen): http://codepad.org/jdqO3W9H This is the output: xevelon ~ # xl create -c /xen/configs/caprica Parsing config from /xen/configs/caprica Daemon running with PID 4460 libxl: error: libxl_dom.c:34:libxl__domain_type: unable to get domain type for domid=6 Unable to attach console libxl: error: libxl_exec.c:118:libxl_report_child_exitstatus: console child [0] exited with error status 1 xevelon ~ # cat /var/log/xen/xl-caprica.log Waiting for domain caprica (domid 6) to die [pid 4461] Domain 6 has shut down, reason code 3 0x3 Action for shutdown reason code 3 is destroy Domain 6 needs to be cleaned up: destroying the domain Done. Exiting now xl dmesg: XEN) d6:v0: unhandled page fault (ec=0000) (XEN) Pagetable walk from 00000e94: (XEN) L3[0x000] = 0000000000000000 ffffffff (XEN) domain_crash_sync called from entry.S (ff1ef878) (XEN) Domain 6 (vcpu#0) crashed on cpu#3: (XEN) ----[ Xen-4.2.0 x86_32p debug=n Not tainted ]---- (XEN) CPU: 3 (XEN) EIP: e019:[] (XEN) EFLAGS: 00000206 EM: 1 CONTEXT: pv guest (XEN) eax: 00003f3f ebx: 00000000 ecx: 00000000 edx: 00000000 (XEN) esi: c1a80000 edi: c14b1000 ebp: 00000000 esp: c1601f3c (XEN) cr0: 8005003b cr4: 000006f4 cr3: 28e51000 cr2: 00000e94 (XEN) ds: e021 es: e021 fs: e021 gs: e021 ss: e021 cs: e019 (XEN) Guest stack trace from esp=c1601f3c: (XEN) 00000000 c10b2fc2 0001e019 00010006 00000000 c16561b2 00000000 00000000 (XEN) 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 (XEN) 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 (XEN) 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 (XEN) 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 (XEN) 00000000 00000000 00000000 00000000 00000000 00000000 c1a80000 c14b1000 (XEN) 00000000 00000000 c16dad04 00000068 00000000 00000000 00000000 00000000 (XEN) 014a5000 c1023a28 00000082 00000000 00000000 00000000 00000000 c16dad04 (XEN) 00000000 00000000 00000000 00000068 00000060 00000068 00000068 000000d8 (XEN) 00000000 00000000 80000000 00000000 00000000 00000000 00000000 00000000 (XEN) 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 (XEN) 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 (XEN) 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 (XEN) 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 (XEN) 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 (XEN) 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 (XEN) 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 (XEN) 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 (XEN) 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 (XEN) 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 - xl info: http://codepad.org/wJCTXtoD - xl create (-vvv ultraverbose): http://codepad.org/XhXN5ztl Does somebody have any clue about it? Thank you so much!-- Fabiano Francesconi [GPG key: 0x81E53461] _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Mon Feb 11 15:28:34 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 11 Feb 2013 15:28: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 1U4vIP-0007MJ-6U; Mon, 11 Feb 2013 15:27:53 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U4vIN-0007ME-OO for xen-users@lists.xen.org; Mon, 11 Feb 2013 15:27:51 +0000 Received: from [193.109.254.147:26125] by server-6.bemta-14.messagelabs.com id C8/3D-12010-6FD09115; Mon, 11 Feb 2013 15:27:50 +0000 X-Env-Sender: fabiano.francesconi@gmail.com X-Msg-Ref: server-11.tower-27.messagelabs.com!1360596413!2444767!1 X-Originating-IP: [209.85.215.175] 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.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 22572 invoked from network); 11 Feb 2013 15:26:53 -0000 Received: from mail-ea0-f175.google.com (HELO mail-ea0-f175.google.com) (209.85.215.175) by server-11.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 11 Feb 2013 15:26:53 -0000 Received: by mail-ea0-f175.google.com with SMTP id d1so2687138eab.6 for ; Mon, 11 Feb 2013 07:25:54 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:date:from:to:message-id:subject:x-mailer:mime-version :content-type:content-transfer-encoding:content-disposition; bh=P2QL3sb1KyriW8ZrTfRb+qx69jesVhK0Rhkex6ERkZQ=; b=NiPZ75HXy+KZcjlf7e/B2N7nfLOJf6y84M8I8kse7UeYxgxMKh5rQdtoT7dSRbBAfL 6u7oriLmeL24aYGs//2Q9wJAPoXAWs+0zK+9Q3XBqP43SkRYCJkGf2bR5loKUxFZD7dL nvAnbMV9DT0+sUYBbrI3e3fRejabG2TikdcxRlGEKOhCY4HvJrMqccpEMpbNtPd7Wn6I TPhWO0Ih3FKdpmdUR0JYMQ+W/E6kJDafQ8Cucy8wUYQmYQieG653J9dB0jeOnJmSSpg9 t+IqYCthayOrG+OB8rs6uDL7N8E32oQR/JtCWmryNYORmxT1ueEoqUymOujvbBGfUq2L cZTw== X-Received: by 10.14.225.133 with SMTP id z5mr51284524eep.15.1360596354036; Mon, 11 Feb 2013 07:25:54 -0800 (PST) Received: from [192.168.0.145] (host111-111-dynamic.14-87-r.retail.telecomitalia.it. [87.14.111.111]) by mx.google.com with ESMTPS id q5sm63063835eep.11.2013.02.11.07.25.52 (version=TLSv1 cipher=RC4-SHA bits=128/128); Mon, 11 Feb 2013 07:25:53 -0800 (PST) Date: Mon, 11 Feb 2013 16:25:51 +0100 From: Fabiano Francesconi To: xen-users@lists.xen.org Message-ID: <3C0CB81079134B2586C4CB56AC211233@gmail.com> X-Mailer: sparrow 1.6.4 (build 1176) MIME-Version: 1.0 Content-Disposition: inline Subject: [Xen-users] Xen domU PV linux-3.7.0-hardened won'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: 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 everybody, today I was trying to update my domU to linux kernel v3. At the moment it's running with a 2.6.38 kernel and it's running smooth. I simply took the .config and run a make oldconfig in linux v3 sources and what I get is that it won't boot. No kernel bootlog to inspect. I'm running xen 4.2.0 on a 32bit paravirt environment. The dom0 kernel is Linux 3.3.8 and the other domU machine I have is running with the same version of the kernel. The sole machine that is giving me troubles is the hardened one, currently running with grsec+pax on the 2.6.38. This is my current configuration: - kernel config file (domU): http://codepad.org/sgnyXLqL - domU configuration file (xen): http://codepad.org/jdqO3W9H This is the output: xevelon ~ # xl create -c /xen/configs/caprica Parsing config from /xen/configs/caprica Daemon running with PID 4460 libxl: error: libxl_dom.c:34:libxl__domain_type: unable to get domain type for domid=6 Unable to attach console libxl: error: libxl_exec.c:118:libxl_report_child_exitstatus: console child [0] exited with error status 1 xevelon ~ # cat /var/log/xen/xl-caprica.log Waiting for domain caprica (domid 6) to die [pid 4461] Domain 6 has shut down, reason code 3 0x3 Action for shutdown reason code 3 is destroy Domain 6 needs to be cleaned up: destroying the domain Done. Exiting now xl dmesg: XEN) d6:v0: unhandled page fault (ec=0000) (XEN) Pagetable walk from 00000e94: (XEN) L3[0x000] = 0000000000000000 ffffffff (XEN) domain_crash_sync called from entry.S (ff1ef878) (XEN) Domain 6 (vcpu#0) crashed on cpu#3: (XEN) ----[ Xen-4.2.0 x86_32p debug=n Not tainted ]---- (XEN) CPU: 3 (XEN) EIP: e019:[] (XEN) EFLAGS: 00000206 EM: 1 CONTEXT: pv guest (XEN) eax: 00003f3f ebx: 00000000 ecx: 00000000 edx: 00000000 (XEN) esi: c1a80000 edi: c14b1000 ebp: 00000000 esp: c1601f3c (XEN) cr0: 8005003b cr4: 000006f4 cr3: 28e51000 cr2: 00000e94 (XEN) ds: e021 es: e021 fs: e021 gs: e021 ss: e021 cs: e019 (XEN) Guest stack trace from esp=c1601f3c: (XEN) 00000000 c10b2fc2 0001e019 00010006 00000000 c16561b2 00000000 00000000 (XEN) 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 (XEN) 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 (XEN) 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 (XEN) 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 (XEN) 00000000 00000000 00000000 00000000 00000000 00000000 c1a80000 c14b1000 (XEN) 00000000 00000000 c16dad04 00000068 00000000 00000000 00000000 00000000 (XEN) 014a5000 c1023a28 00000082 00000000 00000000 00000000 00000000 c16dad04 (XEN) 00000000 00000000 00000000 00000068 00000060 00000068 00000068 000000d8 (XEN) 00000000 00000000 80000000 00000000 00000000 00000000 00000000 00000000 (XEN) 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 (XEN) 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 (XEN) 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 (XEN) 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 (XEN) 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 (XEN) 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 (XEN) 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 (XEN) 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 (XEN) 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 (XEN) 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 - xl info: http://codepad.org/wJCTXtoD - xl create (-vvv ultraverbose): http://codepad.org/XhXN5ztl Does somebody have any clue about it? Thank you so much!-- Fabiano Francesconi [GPG key: 0x81E53461] _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Mon Feb 11 16:01:22 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 11 Feb 2013 16: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 1U4vni-0008B6-Lu; Mon, 11 Feb 2013 16:00:14 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U4vnh-0008B1-Os for xen-users@lists.xen.org; Mon, 11 Feb 2013 16:00:14 +0000 Received: from [85.158.138.51:29637] by server-3.bemta-3.messagelabs.com id 25/66-31070-C8519115; Mon, 11 Feb 2013 16:00:12 +0000 X-Env-Sender: roger.pau@citrix.com X-Msg-Ref: server-9.tower-174.messagelabs.com!1360598401!31949566!1 X-Originating-IP: [46.33.159.39] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNDYuMzMuMTU5LjM5ID0+IDIxNzE2\n X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 30817 invoked from network); 11 Feb 2013 16:00:01 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (46.33.159.39) by server-9.tower-174.messagelabs.com with RC4-SHA encrypted SMTP; 11 Feb 2013 16:00:01 -0000 X-IronPort-AV: E=Sophos;i="4.84,643,1355097600"; d="scan'208";a="1336844" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 11 Feb 2013 16:00:01 +0000 Received: from [192.168.1.30] (10.30.249.242) by LONPMAILMX01.citrite.net (10.30.203.162) with Microsoft SMTP Server id 8.3.297.1; Mon, 11 Feb 2013 16:00:00 +0000 Message-ID: <5119158D.1010408@citrix.com> Date: Mon, 11 Feb 2013 17:00:13 +0100 From: =?UTF-8?B?Um9nZXIgUGF1IE1vbm7DqQ==?= User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130107 Thunderbird/17.0.2 MIME-Version: 1.0 To: Ian Campbell References: <201301291646.43567.Markus@hochholdinger.net> <1359708995.9063.3.camel@dagon.hellion.org.uk> <201302061539.40900.Markus@hochholdinger.net> <201302111559.58269.Markus@hochholdinger.net> <1360595115.20449.51.camel@zakaz.uk.xensource.com> In-Reply-To: <1360595115.20449.51.camel@zakaz.uk.xensource.com> Cc: "xen-users@lists.xen.org" , Markus Hochholdinger Subject: Re: [Xen-users] linux stubdom X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: 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 11/02/13 16:05, Ian Campbell wrote: > On Mon, 2013-02-11 at 14:59 +0000, Markus Hochholdinger wrote: >> Hello, >> >> Am 06.02.2013 um 15:39 Uhr schrieb Markus Hochholdinger >> : >>> Am 01.02.2013 um 09:56 Uhr schrieb Ian Campbell : >> [..] >>>>> executed? Would this be between #3 and #7? >>>> It is part of the device teardown and setup, so it is during #5 and #6 >>>> (strictly I think it is just after #5 and just before #6). >>>> On xen-devel at the minute there is a patch series under discussion to >>>> make the script hooks more flexible, in particular adding pre and post >>>> migrate hooks (called something like #1-#3 and #7-#7) which can pre >>>> setup bits of the storage stack which are safe to do with the guest >>>> running but might be slow to initialise (e.g. iSCSI login, but not >>>> opening the device). I don't think this needs to affect you though. >>> at least with xm toolstack, block-scripts in /etc/xen/scripts/block-* are >>> executed on the destination host (add) before the script (remove) on the >>> source host is executed while live migrating a domU. >>> (I've created the script /etc/xen/scripts/block-md which assembles and >>> stops raid1 devices.) >>> Next, I'll test xl toolstack with this setup. >> >> with Xen 4.1 there's no support for custom scripts within libxl. >> >> With Xen 4.2.1 there's support for custom scripts (like with xm toolstack) but >> also only add/remove. And add is called on the destination side before remove >> is called on the transmitting side while doing a live migration of a domU. Yes, I've also realized this while working on the new hotplug implementation. The hotplug script is executed on the destination before the other end has executed the remove script (this is due to the fact that the remove script is executed when the migrated domain is destroyed on the source). So at a certain point the destination host has executed the "add" script before the source host executes the "remove" hotplug script. This is not a problem with the current hotplug scripts in-three, because we can guarantee that the device will not be accessed simultaneously (because the guest only resumes on either the source or the destination hosts, but never on both). So the scheme looks more like: 1. First an empty shell domain (with no devices) is created on the target host. 2. Then we copy the memory over, in several iterations, while the domain is running on the source host (iterations happen to handle the guest dirtying memory as we copy, this is the "live" aspect of the migration). 3. After some iterations of live migration we pause the source guest 4. Setup devices on the target host for the incoming domain 5. Now we copy the remaining dirty RAM 6. Resume the guest on the target domain 7. Tear down devices on the source host 8. Guest reconnects to new backend (#7 and #8 can happen in different order) #4 will be where the hotplug script "add" call happens on the target host, and #7 where the hotplug script "remove" call happens on the source host. > > This sounds like a bug which ought to be addressed (Roger, can you take > a look?) I think this is how migration works in both xl and xm, but if there are hotplug scripts that cannot be executed simultaneously (ie you cannot make two simultaneous calls to "add" without calling "remove" first) we could mark it as a bug. It would make the resume on source host more complicated, since in case of failure we will have to remove the devices on the destination host and reconnect them on the source host. >> Next I'll test latest development version... > > I'm not sure it will differ from 4.2.x in this area (yet). Roger can > probably advise better than me though. No, this has not changed in -unstable. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Mon Feb 11 16:01:22 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 11 Feb 2013 16: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 1U4vni-0008B6-Lu; Mon, 11 Feb 2013 16:00:14 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U4vnh-0008B1-Os for xen-users@lists.xen.org; Mon, 11 Feb 2013 16:00:14 +0000 Received: from [85.158.138.51:29637] by server-3.bemta-3.messagelabs.com id 25/66-31070-C8519115; Mon, 11 Feb 2013 16:00:12 +0000 X-Env-Sender: roger.pau@citrix.com X-Msg-Ref: server-9.tower-174.messagelabs.com!1360598401!31949566!1 X-Originating-IP: [46.33.159.39] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNDYuMzMuMTU5LjM5ID0+IDIxNzE2\n X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 30817 invoked from network); 11 Feb 2013 16:00:01 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (46.33.159.39) by server-9.tower-174.messagelabs.com with RC4-SHA encrypted SMTP; 11 Feb 2013 16:00:01 -0000 X-IronPort-AV: E=Sophos;i="4.84,643,1355097600"; d="scan'208";a="1336844" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 11 Feb 2013 16:00:01 +0000 Received: from [192.168.1.30] (10.30.249.242) by LONPMAILMX01.citrite.net (10.30.203.162) with Microsoft SMTP Server id 8.3.297.1; Mon, 11 Feb 2013 16:00:00 +0000 Message-ID: <5119158D.1010408@citrix.com> Date: Mon, 11 Feb 2013 17:00:13 +0100 From: =?UTF-8?B?Um9nZXIgUGF1IE1vbm7DqQ==?= User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130107 Thunderbird/17.0.2 MIME-Version: 1.0 To: Ian Campbell References: <201301291646.43567.Markus@hochholdinger.net> <1359708995.9063.3.camel@dagon.hellion.org.uk> <201302061539.40900.Markus@hochholdinger.net> <201302111559.58269.Markus@hochholdinger.net> <1360595115.20449.51.camel@zakaz.uk.xensource.com> In-Reply-To: <1360595115.20449.51.camel@zakaz.uk.xensource.com> Cc: "xen-users@lists.xen.org" , Markus Hochholdinger Subject: Re: [Xen-users] linux stubdom X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: 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 11/02/13 16:05, Ian Campbell wrote: > On Mon, 2013-02-11 at 14:59 +0000, Markus Hochholdinger wrote: >> Hello, >> >> Am 06.02.2013 um 15:39 Uhr schrieb Markus Hochholdinger >> : >>> Am 01.02.2013 um 09:56 Uhr schrieb Ian Campbell : >> [..] >>>>> executed? Would this be between #3 and #7? >>>> It is part of the device teardown and setup, so it is during #5 and #6 >>>> (strictly I think it is just after #5 and just before #6). >>>> On xen-devel at the minute there is a patch series under discussion to >>>> make the script hooks more flexible, in particular adding pre and post >>>> migrate hooks (called something like #1-#3 and #7-#7) which can pre >>>> setup bits of the storage stack which are safe to do with the guest >>>> running but might be slow to initialise (e.g. iSCSI login, but not >>>> opening the device). I don't think this needs to affect you though. >>> at least with xm toolstack, block-scripts in /etc/xen/scripts/block-* are >>> executed on the destination host (add) before the script (remove) on the >>> source host is executed while live migrating a domU. >>> (I've created the script /etc/xen/scripts/block-md which assembles and >>> stops raid1 devices.) >>> Next, I'll test xl toolstack with this setup. >> >> with Xen 4.1 there's no support for custom scripts within libxl. >> >> With Xen 4.2.1 there's support for custom scripts (like with xm toolstack) but >> also only add/remove. And add is called on the destination side before remove >> is called on the transmitting side while doing a live migration of a domU. Yes, I've also realized this while working on the new hotplug implementation. The hotplug script is executed on the destination before the other end has executed the remove script (this is due to the fact that the remove script is executed when the migrated domain is destroyed on the source). So at a certain point the destination host has executed the "add" script before the source host executes the "remove" hotplug script. This is not a problem with the current hotplug scripts in-three, because we can guarantee that the device will not be accessed simultaneously (because the guest only resumes on either the source or the destination hosts, but never on both). So the scheme looks more like: 1. First an empty shell domain (with no devices) is created on the target host. 2. Then we copy the memory over, in several iterations, while the domain is running on the source host (iterations happen to handle the guest dirtying memory as we copy, this is the "live" aspect of the migration). 3. After some iterations of live migration we pause the source guest 4. Setup devices on the target host for the incoming domain 5. Now we copy the remaining dirty RAM 6. Resume the guest on the target domain 7. Tear down devices on the source host 8. Guest reconnects to new backend (#7 and #8 can happen in different order) #4 will be where the hotplug script "add" call happens on the target host, and #7 where the hotplug script "remove" call happens on the source host. > > This sounds like a bug which ought to be addressed (Roger, can you take > a look?) I think this is how migration works in both xl and xm, but if there are hotplug scripts that cannot be executed simultaneously (ie you cannot make two simultaneous calls to "add" without calling "remove" first) we could mark it as a bug. It would make the resume on source host more complicated, since in case of failure we will have to remove the devices on the destination host and reconnect them on the source host. >> Next I'll test latest development version... > > I'm not sure it will differ from 4.2.x in this area (yet). Roger can > probably advise better than me though. No, this has not changed in -unstable. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Mon Feb 11 16:28:46 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 11 Feb 2013 16:28: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 1U4wEK-0000hR-Oi; Mon, 11 Feb 2013 16:27:44 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U4wEJ-0000hK-3B for xen-users@lists.xen.org; Mon, 11 Feb 2013 16:27:43 +0000 Received: from [85.158.143.99:44578] by server-1.bemta-4.messagelabs.com id 4C/E2-08839-EFB19115; Mon, 11 Feb 2013 16:27:42 +0000 X-Env-Sender: Markus@hochholdinger.net X-Msg-Ref: server-5.tower-216.messagelabs.com!1360600061!27827440!1 X-Originating-IP: [89.19.235.135] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 12988 invoked from network); 11 Feb 2013 16:27:41 -0000 Received: from group.wh-serverpark.com (HELO group.wh-serverpark.com) (89.19.235.135) by server-5.tower-216.messagelabs.com with SMTP; 11 Feb 2013 16:27:41 -0000 Received: from localhost (localhost [127.0.0.1]) by group.wh-serverpark.com (Postfix) with ESMTP id 1F632980D8; Mon, 11 Feb 2013 17:27:41 +0100 (CET) X-Virus-Scanned: amavisd-new at valiant.wh-serverpark.com Received: from group.wh-serverpark.com ([127.0.0.1]) by localhost (group.wh-serverpark.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id G28hSPFsx+Zi; Mon, 11 Feb 2013 17:27:40 +0100 (CET) Received: from enterprise.localnet (et-0-30.gw-nat.bs.kae.de.oneandone.net [212.227.35.94]) by group.wh-serverpark.com (Postfix) with ESMTPSA id 478B498016; Mon, 11 Feb 2013 17:27:40 +0100 (CET) From: Markus Hochholdinger To: Roger Pau =?iso-8859-1?q?Monn=E9?= Date: Mon, 11 Feb 2013 17:27:35 +0100 User-Agent: KMail/1.13.7 (Linux/3.2.0-4-amd64; KDE/4.8.4; x86_64; ; ) References: <201301291646.43567.Markus@hochholdinger.net> <1360595115.20449.51.camel@zakaz.uk.xensource.com> <5119158D.1010408@citrix.com> In-Reply-To: <5119158D.1010408@citrix.com> MIME-Version: 1.0 Message-Id: <201302111727.39510.Markus@hochholdinger.net> Cc: "xen-users@lists.xen.org" , Ian Campbell Subject: Re: [Xen-users] linux stubdom X-BeenThere: xen-users@lists.xen.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="===============6305399143088651494==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============6305399143088651494== Content-Type: multipart/signed; boundary="nextPart2199292.JmX8Mgyn4u"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit --nextPart2199292.JmX8Mgyn4u Content-Type: Text/Plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Hello, Am 11.02.2013 um 17:00 Uhr schrieb Roger Pau Monn=C3=A9 : > On 11/02/13 16:05, Ian Campbell wrote: > > On Mon, 2013-02-11 at 14:59 +0000, Markus Hochholdinger wrote: > >> Am 06.02.2013 um 15:39 Uhr schrieb Markus Hochholdinger > >>> Am 01.02.2013 um 09:56 Uhr schrieb Ian Campbell [..] > >> With Xen 4.2.1 there's support for custom scripts (like with xm > >> toolstack) but also only add/remove. And add is called on the > >> destination side before remove is called on the transmitting side while > >> doing a live migration of a domU. > Yes, I've also realized this while working on the new hotplug > implementation. The hotplug script is executed on the destination before > the other end has executed the remove script (this is due to the fact > that the remove script is executed when the migrated domain is destroyed > on the source). So at a certain point the destination host has executed > the "add" script before the source host executes the "remove" hotplug > script. OK, so this is what I thought before. Many thanks for clarification. > This is not a problem with the current hotplug scripts in-three, because > we can guarantee that the device will not be accessed simultaneously > (because the guest only resumes on either the source or the destination > hosts, but never on both). > So the scheme looks more like: > 1. First an empty shell domain (with no devices) is created on the > target host. > 2. Then we copy the memory over, in several iterations, while the > domain is running on the source host (iterations happen to > handle the guest dirtying memory as we copy, this is the "live" > aspect of the migration). > 3. After some iterations of live migration we pause the source > guest > 4. Setup devices on the target host for the incoming domain > 5. Now we copy the remaining dirty RAM > 6. Resume the guest on the target domain > 7. Tear down devices on the source host > 8. Guest reconnects to new backend > (#7 and #8 can happen in different order) > #4 will be where the hotplug script "add" call happens on the target > host, and #7 where the hotplug script "remove" call happens on the > source host. As far as I understand now the (block) device on the destination host will = be=20 read before the block device on the source is detached. > > This sounds like a bug which ought to be addressed (Roger, can you take > > a look?) > I think this is how migration works in both xl and xm, but if there are > hotplug scripts that cannot be executed simultaneously (ie you cannot > make two simultaneous calls to "add" without calling "remove" first) we > could mark it as a bug. No, it was not a bug of the hotplug scripts, I made a hotplug script myself= to=20 assemble linux raid1 devices and log timestamps of execution. > It would make the resume on source host more complicated, since in case > of failure we will have to remove the devices on the destination host > and reconnect them on the source host. I understand. > >> Next I'll test latest development version... > > I'm not sure it will differ from 4.2.x in this area (yet). Roger can > > probably advise better than me though. > No, this has not changed in -unstable. OK. Many thanks. =2D-=20 greetings eMHa --nextPart2199292.JmX8Mgyn4u Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (GNU/Linux) iEYEABECAAYFAlEZG/cACgkQXT3LE+AjWCv1EACfXoW9AQ8btkzr/RhSKNwwcbql 7ykAnis7csHjXVMsyszs8dkFDYxQzvlP =up/E -----END PGP SIGNATURE----- --nextPart2199292.JmX8Mgyn4u-- --===============6305399143088651494== 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 --===============6305399143088651494==-- From xen-users-bounces@lists.xen.org Mon Feb 11 16:28:46 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 11 Feb 2013 16:28: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 1U4wEK-0000hR-Oi; Mon, 11 Feb 2013 16:27:44 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U4wEJ-0000hK-3B for xen-users@lists.xen.org; Mon, 11 Feb 2013 16:27:43 +0000 Received: from [85.158.143.99:44578] by server-1.bemta-4.messagelabs.com id 4C/E2-08839-EFB19115; Mon, 11 Feb 2013 16:27:42 +0000 X-Env-Sender: Markus@hochholdinger.net X-Msg-Ref: server-5.tower-216.messagelabs.com!1360600061!27827440!1 X-Originating-IP: [89.19.235.135] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 12988 invoked from network); 11 Feb 2013 16:27:41 -0000 Received: from group.wh-serverpark.com (HELO group.wh-serverpark.com) (89.19.235.135) by server-5.tower-216.messagelabs.com with SMTP; 11 Feb 2013 16:27:41 -0000 Received: from localhost (localhost [127.0.0.1]) by group.wh-serverpark.com (Postfix) with ESMTP id 1F632980D8; Mon, 11 Feb 2013 17:27:41 +0100 (CET) X-Virus-Scanned: amavisd-new at valiant.wh-serverpark.com Received: from group.wh-serverpark.com ([127.0.0.1]) by localhost (group.wh-serverpark.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id G28hSPFsx+Zi; Mon, 11 Feb 2013 17:27:40 +0100 (CET) Received: from enterprise.localnet (et-0-30.gw-nat.bs.kae.de.oneandone.net [212.227.35.94]) by group.wh-serverpark.com (Postfix) with ESMTPSA id 478B498016; Mon, 11 Feb 2013 17:27:40 +0100 (CET) From: Markus Hochholdinger To: Roger Pau =?iso-8859-1?q?Monn=E9?= Date: Mon, 11 Feb 2013 17:27:35 +0100 User-Agent: KMail/1.13.7 (Linux/3.2.0-4-amd64; KDE/4.8.4; x86_64; ; ) References: <201301291646.43567.Markus@hochholdinger.net> <1360595115.20449.51.camel@zakaz.uk.xensource.com> <5119158D.1010408@citrix.com> In-Reply-To: <5119158D.1010408@citrix.com> MIME-Version: 1.0 Message-Id: <201302111727.39510.Markus@hochholdinger.net> Cc: "xen-users@lists.xen.org" , Ian Campbell Subject: Re: [Xen-users] linux stubdom X-BeenThere: xen-users@lists.xen.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="===============6305399143088651494==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============6305399143088651494== Content-Type: multipart/signed; boundary="nextPart2199292.JmX8Mgyn4u"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit --nextPart2199292.JmX8Mgyn4u Content-Type: Text/Plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Hello, Am 11.02.2013 um 17:00 Uhr schrieb Roger Pau Monn=C3=A9 : > On 11/02/13 16:05, Ian Campbell wrote: > > On Mon, 2013-02-11 at 14:59 +0000, Markus Hochholdinger wrote: > >> Am 06.02.2013 um 15:39 Uhr schrieb Markus Hochholdinger > >>> Am 01.02.2013 um 09:56 Uhr schrieb Ian Campbell [..] > >> With Xen 4.2.1 there's support for custom scripts (like with xm > >> toolstack) but also only add/remove. And add is called on the > >> destination side before remove is called on the transmitting side while > >> doing a live migration of a domU. > Yes, I've also realized this while working on the new hotplug > implementation. The hotplug script is executed on the destination before > the other end has executed the remove script (this is due to the fact > that the remove script is executed when the migrated domain is destroyed > on the source). So at a certain point the destination host has executed > the "add" script before the source host executes the "remove" hotplug > script. OK, so this is what I thought before. Many thanks for clarification. > This is not a problem with the current hotplug scripts in-three, because > we can guarantee that the device will not be accessed simultaneously > (because the guest only resumes on either the source or the destination > hosts, but never on both). > So the scheme looks more like: > 1. First an empty shell domain (with no devices) is created on the > target host. > 2. Then we copy the memory over, in several iterations, while the > domain is running on the source host (iterations happen to > handle the guest dirtying memory as we copy, this is the "live" > aspect of the migration). > 3. After some iterations of live migration we pause the source > guest > 4. Setup devices on the target host for the incoming domain > 5. Now we copy the remaining dirty RAM > 6. Resume the guest on the target domain > 7. Tear down devices on the source host > 8. Guest reconnects to new backend > (#7 and #8 can happen in different order) > #4 will be where the hotplug script "add" call happens on the target > host, and #7 where the hotplug script "remove" call happens on the > source host. As far as I understand now the (block) device on the destination host will = be=20 read before the block device on the source is detached. > > This sounds like a bug which ought to be addressed (Roger, can you take > > a look?) > I think this is how migration works in both xl and xm, but if there are > hotplug scripts that cannot be executed simultaneously (ie you cannot > make two simultaneous calls to "add" without calling "remove" first) we > could mark it as a bug. No, it was not a bug of the hotplug scripts, I made a hotplug script myself= to=20 assemble linux raid1 devices and log timestamps of execution. > It would make the resume on source host more complicated, since in case > of failure we will have to remove the devices on the destination host > and reconnect them on the source host. I understand. > >> Next I'll test latest development version... > > I'm not sure it will differ from 4.2.x in this area (yet). Roger can > > probably advise better than me though. > No, this has not changed in -unstable. OK. Many thanks. =2D-=20 greetings eMHa --nextPart2199292.JmX8Mgyn4u Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (GNU/Linux) iEYEABECAAYFAlEZG/cACgkQXT3LE+AjWCv1EACfXoW9AQ8btkzr/RhSKNwwcbql 7ykAnis7csHjXVMsyszs8dkFDYxQzvlP =up/E -----END PGP SIGNATURE----- --nextPart2199292.JmX8Mgyn4u-- --===============6305399143088651494== 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 --===============6305399143088651494==-- From xen-users-bounces@lists.xen.org Mon Feb 11 20:49:04 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 11 Feb 2013 20:49: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 1U50Hy-0003Hu-1c; Mon, 11 Feb 2013 20:47:46 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U4udq-0005r5-GG for xen-users@lists.xen.org; Mon, 11 Feb 2013 14:45:58 +0000 Received: from [85.158.139.83:20641] by server-7.bemta-5.messagelabs.com id 3C/10-11121-52409115; Mon, 11 Feb 2013 14:45:57 +0000 X-Env-Sender: Mark.Thebridge@metaswitch.com X-Msg-Ref: server-11.tower-182.messagelabs.com!1360593956!20869436!1 X-Originating-IP: [192.91.191.38] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 6016 invoked from network); 11 Feb 2013 14:45:57 -0000 Received: from enficsets1.metaswitch.com (HELO ENFICSETS1.metaswitch.com) (192.91.191.38) by server-11.tower-182.messagelabs.com with AES128-SHA encrypted SMTP; 11 Feb 2013 14:45:57 -0000 Received: from ENFIRHMBX1.datcon.co.uk (172.18.74.36) by ENFICSETS1.metaswitch.com (172.18.4.18) with Microsoft SMTP Server (TLS) id 14.2.328.9; Mon, 11 Feb 2013 14:45:00 +0000 Received: from ENFICSMBX1.datcon.co.uk ([fe80::d5d5:c683:a3be:3a19]) by ENFIRHMBX1.datcon.co.uk ([fe80::b06d:4d13:5f63:3715%19]) with mapi id 14.02.0328.009; Mon, 11 Feb 2013 14:45:56 +0000 From: Mark Thebridge To: "xen-users@lists.xen.org" Thread-Topic: Clock problems running RHEL6.3 PV guest Thread-Index: Ac4IZhrIdBftndmYT2a1NeRCHqjy8A== Date: Mon, 11 Feb 2013 14:45:55 +0000 Message-ID: <4F486DD9FF355D45ADB74F18D356F918D65161F8@ENFICSMBX1.datcon.co.uk> Accept-Language: en-GB, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [172.18.70.115] MIME-Version: 1.0 X-Mailman-Approved-At: Mon, 11 Feb 2013 20:47:44 +0000 Subject: [Xen-users] Clock problems running RHEL6.3 PV 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: , Content-Type: 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 a reasonably time-critical, networking application that I'm trying to get running in a Xen PV guest. Unfortunately, I'm experiencing intermittent lockups that seem to be down to poor timekeeping in the domU. The application runs on Red Hat Enterprise Linux 6.3, and so I'm using that as the domU. For dom0 I've tried both CentOS 5.9 with Xen 3.1, and Fedora 18 with Xen 4.2.1. Both have the same effect. The problem manifests as what seem to be lockups - a single vCPU appears to hang. My application has internal monitoring threads that try to determine if any part of the application has hung and these are erroneously triggering constantly. If I have a shell open to the guest, then sometimes it becomes unresponsive for a second or two. And very occasionally (maybe 3 or 4 times a day?) the kernel reports soft lockups of around 25 seconds, always with the following stack: [] ? watchdog_timer_fn+0x1c2/0x1d0 [] ? __run_hrtimer+0x8e/0x1a0 [] ? xen_clocksource_get_cycles+0x9/0x10 [] ? hrtimer_interrupt+0xe6/0x250 [] ? __hrtimer_peek_ahead_timers+0x3f/0x50 [] ? hrtimer_peek_ahead_timers+0x24/0x40 [] ? run_hrtimer_softirq+0x3b/0x40 [] ? __do_softirq+0xbb/0x1f0 [] ? call_softirq+0x1c/0x30 [] ? do_softirq+0x65/0xa0 [] ? ksoftirqd+0x80/0x110 [] ? ksoftirqd+0x0/0x110 [] ? kthread+0x96/0xa0 [] ? child_rip+0xa/0x20 [] ? int_ret_from_sys_call+0x7/0x1b [] ? retint_restore_args+0x5/0x6 [] ? child_rip+0x0/0x20 I also get regular "clocksource tsc unstable" messages in domU. If I turn on ntpd in the domU then the clock moves fast enough that NTP can't compensate. Note that the time in dom0 seems fine, and I've seen no issues there. Has anyone seen anything similar? I know this application *can* run virtualized - I have run it many times on VMware servers with no problem, and the application has been stable in Amazon EC2 as well - so I feel it must be something odd about my hypervisor/dom0 setup. But I'm stumped if I can work out what's wrong. Other potentially useful information: -- Underlying physical CPUs are fairly standard 64-bit Intels - Xeon E5645. -- There are no other domUs running, and the dom0 is doing nothing unusual. -- Other things I've tried, none of which seem to make any difference: -- Switching from xen to tsc as the clocksource in the guest (the only two available) -- Change the hypervisor command line to set clocksource=pit rather than HPET -- Boot the domU with a single vCPU -- Pinning or not pinning the vCPUs to fixed physical CPUs, both in dom0 and domU. Thanks, Mark _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Mon Feb 11 20:49:04 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 11 Feb 2013 20:49: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 1U50Hy-0003Hu-1c; Mon, 11 Feb 2013 20:47:46 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U4udq-0005r5-GG for xen-users@lists.xen.org; Mon, 11 Feb 2013 14:45:58 +0000 Received: from [85.158.139.83:20641] by server-7.bemta-5.messagelabs.com id 3C/10-11121-52409115; Mon, 11 Feb 2013 14:45:57 +0000 X-Env-Sender: Mark.Thebridge@metaswitch.com X-Msg-Ref: server-11.tower-182.messagelabs.com!1360593956!20869436!1 X-Originating-IP: [192.91.191.38] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 6016 invoked from network); 11 Feb 2013 14:45:57 -0000 Received: from enficsets1.metaswitch.com (HELO ENFICSETS1.metaswitch.com) (192.91.191.38) by server-11.tower-182.messagelabs.com with AES128-SHA encrypted SMTP; 11 Feb 2013 14:45:57 -0000 Received: from ENFIRHMBX1.datcon.co.uk (172.18.74.36) by ENFICSETS1.metaswitch.com (172.18.4.18) with Microsoft SMTP Server (TLS) id 14.2.328.9; Mon, 11 Feb 2013 14:45:00 +0000 Received: from ENFICSMBX1.datcon.co.uk ([fe80::d5d5:c683:a3be:3a19]) by ENFIRHMBX1.datcon.co.uk ([fe80::b06d:4d13:5f63:3715%19]) with mapi id 14.02.0328.009; Mon, 11 Feb 2013 14:45:56 +0000 From: Mark Thebridge To: "xen-users@lists.xen.org" Thread-Topic: Clock problems running RHEL6.3 PV guest Thread-Index: Ac4IZhrIdBftndmYT2a1NeRCHqjy8A== Date: Mon, 11 Feb 2013 14:45:55 +0000 Message-ID: <4F486DD9FF355D45ADB74F18D356F918D65161F8@ENFICSMBX1.datcon.co.uk> Accept-Language: en-GB, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [172.18.70.115] MIME-Version: 1.0 X-Mailman-Approved-At: Mon, 11 Feb 2013 20:47:44 +0000 Subject: [Xen-users] Clock problems running RHEL6.3 PV 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: , Content-Type: 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 a reasonably time-critical, networking application that I'm trying to get running in a Xen PV guest. Unfortunately, I'm experiencing intermittent lockups that seem to be down to poor timekeeping in the domU. The application runs on Red Hat Enterprise Linux 6.3, and so I'm using that as the domU. For dom0 I've tried both CentOS 5.9 with Xen 3.1, and Fedora 18 with Xen 4.2.1. Both have the same effect. The problem manifests as what seem to be lockups - a single vCPU appears to hang. My application has internal monitoring threads that try to determine if any part of the application has hung and these are erroneously triggering constantly. If I have a shell open to the guest, then sometimes it becomes unresponsive for a second or two. And very occasionally (maybe 3 or 4 times a day?) the kernel reports soft lockups of around 25 seconds, always with the following stack: [] ? watchdog_timer_fn+0x1c2/0x1d0 [] ? __run_hrtimer+0x8e/0x1a0 [] ? xen_clocksource_get_cycles+0x9/0x10 [] ? hrtimer_interrupt+0xe6/0x250 [] ? __hrtimer_peek_ahead_timers+0x3f/0x50 [] ? hrtimer_peek_ahead_timers+0x24/0x40 [] ? run_hrtimer_softirq+0x3b/0x40 [] ? __do_softirq+0xbb/0x1f0 [] ? call_softirq+0x1c/0x30 [] ? do_softirq+0x65/0xa0 [] ? ksoftirqd+0x80/0x110 [] ? ksoftirqd+0x0/0x110 [] ? kthread+0x96/0xa0 [] ? child_rip+0xa/0x20 [] ? int_ret_from_sys_call+0x7/0x1b [] ? retint_restore_args+0x5/0x6 [] ? child_rip+0x0/0x20 I also get regular "clocksource tsc unstable" messages in domU. If I turn on ntpd in the domU then the clock moves fast enough that NTP can't compensate. Note that the time in dom0 seems fine, and I've seen no issues there. Has anyone seen anything similar? I know this application *can* run virtualized - I have run it many times on VMware servers with no problem, and the application has been stable in Amazon EC2 as well - so I feel it must be something odd about my hypervisor/dom0 setup. But I'm stumped if I can work out what's wrong. Other potentially useful information: -- Underlying physical CPUs are fairly standard 64-bit Intels - Xeon E5645. -- There are no other domUs running, and the dom0 is doing nothing unusual. -- Other things I've tried, none of which seem to make any difference: -- Switching from xen to tsc as the clocksource in the guest (the only two available) -- Change the hypervisor command line to set clocksource=pit rather than HPET -- Boot the domU with a single vCPU -- Pinning or not pinning the vCPUs to fixed physical CPUs, both in dom0 and domU. Thanks, Mark _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Mon Feb 11 21:48:58 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 11 Feb 2013 21:48: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 1U51Dw-0003vw-E6; Mon, 11 Feb 2013 21:47:40 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U51Du-0003vr-9b for xen-users@lists.xen.org; Mon, 11 Feb 2013 21:47:38 +0000 Received: from [85.158.139.83:10829] by server-1.bemta-5.messagelabs.com id A2/71-29263-9F669115; Mon, 11 Feb 2013 21:47:37 +0000 X-Env-Sender: pigeon@pigeond.net X-Msg-Ref: server-6.tower-182.messagelabs.com!1360619254!24828738!1 X-Originating-IP: [203.59.1.226] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogMjAzLjU5LjEuMjI2ID0+IDEzNDcy\n X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 6031 invoked from network); 11 Feb 2013 21:47:36 -0000 Received: from icp-osb-irony-out9.external.iinet.net.au (HELO icp-osb-irony-out9.external.iinet.net.au) (203.59.1.226) by server-6.tower-182.messagelabs.com with SMTP; 11 Feb 2013 21:47:36 -0000 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: Av4EAM5lGVF8lWUl/2dsb2JhbABEwSYWc4IfAQEEATpECwsNFCUPOgENiCUFsD2PZY5jgyoDliOGFIpAgxo X-IronPort-AV: E=Sophos;i="4.84,646,1355068800"; d="scan'208";a="84587310" Received: from unknown (HELO torankusu.pigeond.net) ([124.149.101.37]) by icp-osb-irony-out9.iinet.net.au with ESMTP; 12 Feb 2013 05:47:32 +0800 Received: from furiza.pigeond.net ([192.168.42.20]:59410 helo=pigeond.net) by torankusu.pigeond.net with esmtp (Exim 4.72) (envelope-from ) id 1U51Dn-0004uv-Az for xen-users@lists.xen.org; Tue, 12 Feb 2013 08:47:31 +1100 Date: Tue, 12 Feb 2013 08:47:28 +1100 From: Howell Tam To: xen-users@lists.xen.org Message-ID: <20130212084728.64c49ea1@pigeond.net> In-Reply-To: <20130210235853.4ebb70b8@pigeond.net> References: <20130210235853.4ebb70b8@pigeond.net> Organization: pigeond.net X-Mailer: Claws Mail 3.8.1 (GTK+ 2.24.10; x86_64-pc-linux-gnu) Mime-Version: 1.0 Subject: Re: [Xen-users] Dom0 freeze on HVM DomU Windows reboot with 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 > I'm doing VGA passthrough for an ATI (HD 6770) graphics card > to a DomU Windows. The passthrough itself is working. However, > everytime when I reboot the DomU Windows, the whole machine freezes. And FWIW, I tested with Xen latest tree and I still get the freezing problem. I have tried to turn on more debugging with loglvl and guest_loglvl but there's nothing obvious. Any more suggestions anyone? Thanks. -- Regards, Howell. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Mon Feb 11 21:48:58 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 11 Feb 2013 21:48: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 1U51Dw-0003vw-E6; Mon, 11 Feb 2013 21:47:40 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U51Du-0003vr-9b for xen-users@lists.xen.org; Mon, 11 Feb 2013 21:47:38 +0000 Received: from [85.158.139.83:10829] by server-1.bemta-5.messagelabs.com id A2/71-29263-9F669115; Mon, 11 Feb 2013 21:47:37 +0000 X-Env-Sender: pigeon@pigeond.net X-Msg-Ref: server-6.tower-182.messagelabs.com!1360619254!24828738!1 X-Originating-IP: [203.59.1.226] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogMjAzLjU5LjEuMjI2ID0+IDEzNDcy\n X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 6031 invoked from network); 11 Feb 2013 21:47:36 -0000 Received: from icp-osb-irony-out9.external.iinet.net.au (HELO icp-osb-irony-out9.external.iinet.net.au) (203.59.1.226) by server-6.tower-182.messagelabs.com with SMTP; 11 Feb 2013 21:47:36 -0000 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: Av4EAM5lGVF8lWUl/2dsb2JhbABEwSYWc4IfAQEEATpECwsNFCUPOgENiCUFsD2PZY5jgyoDliOGFIpAgxo X-IronPort-AV: E=Sophos;i="4.84,646,1355068800"; d="scan'208";a="84587310" Received: from unknown (HELO torankusu.pigeond.net) ([124.149.101.37]) by icp-osb-irony-out9.iinet.net.au with ESMTP; 12 Feb 2013 05:47:32 +0800 Received: from furiza.pigeond.net ([192.168.42.20]:59410 helo=pigeond.net) by torankusu.pigeond.net with esmtp (Exim 4.72) (envelope-from ) id 1U51Dn-0004uv-Az for xen-users@lists.xen.org; Tue, 12 Feb 2013 08:47:31 +1100 Date: Tue, 12 Feb 2013 08:47:28 +1100 From: Howell Tam To: xen-users@lists.xen.org Message-ID: <20130212084728.64c49ea1@pigeond.net> In-Reply-To: <20130210235853.4ebb70b8@pigeond.net> References: <20130210235853.4ebb70b8@pigeond.net> Organization: pigeond.net X-Mailer: Claws Mail 3.8.1 (GTK+ 2.24.10; x86_64-pc-linux-gnu) Mime-Version: 1.0 Subject: Re: [Xen-users] Dom0 freeze on HVM DomU Windows reboot with 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 > I'm doing VGA passthrough for an ATI (HD 6770) graphics card > to a DomU Windows. The passthrough itself is working. However, > everytime when I reboot the DomU Windows, the whole machine freezes. And FWIW, I tested with Xen latest tree and I still get the freezing problem. I have tried to turn on more debugging with loglvl and guest_loglvl but there's nothing obvious. Any more suggestions anyone? Thanks. -- Regards, Howell. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Tue Feb 12 00:20:06 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 12 Feb 2013 00:20: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 1U53a0-0005U5-Gt; Tue, 12 Feb 2013 00:18:36 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U53Zz-0005U0-5P for xen-users@lists.xen.org; Tue, 12 Feb 2013 00:18:35 +0000 Received: from [85.158.138.51:54605] by server-6.bemta-3.messagelabs.com id F7/22-29959-A5A89115; Tue, 12 Feb 2013 00:18:34 +0000 X-Env-Sender: james.harper@bendigoit.com.au X-Msg-Ref: server-15.tower-174.messagelabs.com!1360628310!30185248!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.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 18018 invoked from network); 12 Feb 2013 00:18:33 -0000 Received: from smtp1.bendigoit.com.au (HELO smtp1.bendigoit.com.au) (203.16.224.4) by server-15.tower-174.messagelabs.com with AES256-SHA encrypted SMTP; 12 Feb 2013 00:18:33 -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 1U53Zp-0007Ls-5T; Tue, 12 Feb 2013 11:18:25 +1100 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.0438.000; Tue, 12 Feb 2013 11:18:25 +1100 From: James Harper To: Howell Tam , "xen-users@lists.xen.org" Thread-Topic: [Xen-users] Dom0 freeze on HVM DomU Windows reboot with VGA passthrough Thread-Index: AQHOB5BxBzN2PphSd0+JtBPDkMIs0Jh0ez0AgADiTCA= Date: Tue, 12 Feb 2013 00:18:24 +0000 Message-ID: <6035A0D088A63A46850C3988ED045A4B35667928@BITCOM1.int.sbss.com.au> References: <20130210235853.4ebb70b8@pigeond.net> <20130212084728.64c49ea1@pigeond.net> In-Reply-To: <20130212084728.64c49ea1@pigeond.net> 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:71ca:8aba:3150:8f75] x-tm-as-product-ver: SMEX-10.2.0.2087-7.000.1014-19630.003 x-tm-as-result: No--37.920800-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] Dom0 freeze on HVM DomU Windows reboot with 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 > > > I'm doing VGA passthrough for an ATI (HD 6770) graphics card > > to a DomU Windows. The passthrough itself is working. However, > > everytime when I reboot the DomU Windows, the whole machine freezes. > > And FWIW, I tested with Xen latest tree and I still get the > freezing problem. > > I have tried to turn on more debugging with loglvl and > guest_loglvl but there's nothing obvious. > > Any more suggestions anyone? > If you are using GPLPV, I have a very beta version that no longer tries to do anything funky with interrupts and may make a difference here... unless you are also freezing without using GPLPV in which case it won't. James _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Tue Feb 12 00:20:06 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 12 Feb 2013 00:20: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 1U53a0-0005U5-Gt; Tue, 12 Feb 2013 00:18:36 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U53Zz-0005U0-5P for xen-users@lists.xen.org; Tue, 12 Feb 2013 00:18:35 +0000 Received: from [85.158.138.51:54605] by server-6.bemta-3.messagelabs.com id F7/22-29959-A5A89115; Tue, 12 Feb 2013 00:18:34 +0000 X-Env-Sender: james.harper@bendigoit.com.au X-Msg-Ref: server-15.tower-174.messagelabs.com!1360628310!30185248!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.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 18018 invoked from network); 12 Feb 2013 00:18:33 -0000 Received: from smtp1.bendigoit.com.au (HELO smtp1.bendigoit.com.au) (203.16.224.4) by server-15.tower-174.messagelabs.com with AES256-SHA encrypted SMTP; 12 Feb 2013 00:18:33 -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 1U53Zp-0007Ls-5T; Tue, 12 Feb 2013 11:18:25 +1100 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.0438.000; Tue, 12 Feb 2013 11:18:25 +1100 From: James Harper To: Howell Tam , "xen-users@lists.xen.org" Thread-Topic: [Xen-users] Dom0 freeze on HVM DomU Windows reboot with VGA passthrough Thread-Index: AQHOB5BxBzN2PphSd0+JtBPDkMIs0Jh0ez0AgADiTCA= Date: Tue, 12 Feb 2013 00:18:24 +0000 Message-ID: <6035A0D088A63A46850C3988ED045A4B35667928@BITCOM1.int.sbss.com.au> References: <20130210235853.4ebb70b8@pigeond.net> <20130212084728.64c49ea1@pigeond.net> In-Reply-To: <20130212084728.64c49ea1@pigeond.net> 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:71ca:8aba:3150:8f75] x-tm-as-product-ver: SMEX-10.2.0.2087-7.000.1014-19630.003 x-tm-as-result: No--37.920800-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] Dom0 freeze on HVM DomU Windows reboot with 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 > > > I'm doing VGA passthrough for an ATI (HD 6770) graphics card > > to a DomU Windows. The passthrough itself is working. However, > > everytime when I reboot the DomU Windows, the whole machine freezes. > > And FWIW, I tested with Xen latest tree and I still get the > freezing problem. > > I have tried to turn on more debugging with loglvl and > guest_loglvl but there's nothing obvious. > > Any more suggestions anyone? > If you are using GPLPV, I have a very beta version that no longer tries to do anything funky with interrupts and may make a difference here... unless you are also freezing without using GPLPV in which case it won't. James _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Tue Feb 12 08:46:27 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 12 Feb 2013 08: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 1U5BU1-00056c-5t; Tue, 12 Feb 2013 08:44:57 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U5BU0-00056X-FS for xen-users@lists.xen.org; Tue, 12 Feb 2013 08:44:56 +0000 Received: from [85.158.143.99:44159] by server-2.bemta-4.messagelabs.com id CE/B0-01597-7010A115; Tue, 12 Feb 2013 08:44:55 +0000 X-Env-Sender: JBeulich@suse.com X-Msg-Ref: server-14.tower-216.messagelabs.com!1360658660!22242835!1 X-Originating-IP: [130.57.49.28] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogMTMwLjU3LjQ5LjI4ID0+IDQwNzM=\n X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 29985 invoked from network); 12 Feb 2013 08:44:21 -0000 Received: from nat28.tlf.novell.com (HELO nat28.tlf.novell.com) (130.57.49.28) by server-14.tower-216.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 12 Feb 2013 08:44:21 -0000 Received: from EMEA1-MTA by nat28.tlf.novell.com with Novell_GroupWise; Tue, 12 Feb 2013 08:44:06 +0000 Message-Id: <511A0E9C02000078000BD9EA@nat28.tlf.novell.com> X-Mailer: Novell GroupWise Internet Agent 12.0.1 Date: Tue, 12 Feb 2013 08:42:52 +0000 From: "Jan Beulich" To: "Ian Campbell" , "Matthias" References: <1360581739.29432.115.camel@zakaz.uk.xensource.com> In-Reply-To: <1360581739.29432.115.camel@zakaz.uk.xensource.com> Mime-Version: 1.0 Content-Disposition: inline Cc: "boris.ostrovsky@amd.com" , "xen-users@lists.xen.org" Subject: Re: [Xen-users] Latest AMD, IOMMU Security Change causing CPU0 Panic and general Problems with AMD+IOMMU changes X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: 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 11.02.13 at 12:22, Ian Campbell wrote: > On Sat, 2013-02-09 at 02:12 +0000, Matthias wrote: >> Hi, >> >> unfortunatly your latest change "AMD,IOMMU: Clean up old entries in >> remapping tables when creating new one" (Changeset 26517 in >> xen-unstable and 25975 in xen-4.2-testing) is causing a CPU0 Panic at >> boot for me. >> >> When i tried to boot latest versions of xen unstable or xen-testing, >> my dom0 gives me the message: >> >> (XEN) ************************************* >> (XEN) Panic on CPU 0: >> (XEN) DATAL PAGE FAULT >> (XEN) [error_code=0000] >> (XEN) Faulting linear address: 0000000000000000 >> (XEN) ************************************* > > I think this is fixed by "[PATCH 1/2] AMD IOMMU: also spot missing > IO-APIC entries in IVRS table" posted to xen-devel on Wednesday. > Message-ID <511264B402000078000BC754@nat28.tlf.novell.com> Without a full register/stack trace I would also guess so, but in that mode it's no more than a guess really. Jan _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Tue Feb 12 08:46:27 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 12 Feb 2013 08: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 1U5BU1-00056c-5t; Tue, 12 Feb 2013 08:44:57 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U5BU0-00056X-FS for xen-users@lists.xen.org; Tue, 12 Feb 2013 08:44:56 +0000 Received: from [85.158.143.99:44159] by server-2.bemta-4.messagelabs.com id CE/B0-01597-7010A115; Tue, 12 Feb 2013 08:44:55 +0000 X-Env-Sender: JBeulich@suse.com X-Msg-Ref: server-14.tower-216.messagelabs.com!1360658660!22242835!1 X-Originating-IP: [130.57.49.28] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogMTMwLjU3LjQ5LjI4ID0+IDQwNzM=\n X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 29985 invoked from network); 12 Feb 2013 08:44:21 -0000 Received: from nat28.tlf.novell.com (HELO nat28.tlf.novell.com) (130.57.49.28) by server-14.tower-216.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 12 Feb 2013 08:44:21 -0000 Received: from EMEA1-MTA by nat28.tlf.novell.com with Novell_GroupWise; Tue, 12 Feb 2013 08:44:06 +0000 Message-Id: <511A0E9C02000078000BD9EA@nat28.tlf.novell.com> X-Mailer: Novell GroupWise Internet Agent 12.0.1 Date: Tue, 12 Feb 2013 08:42:52 +0000 From: "Jan Beulich" To: "Ian Campbell" , "Matthias" References: <1360581739.29432.115.camel@zakaz.uk.xensource.com> In-Reply-To: <1360581739.29432.115.camel@zakaz.uk.xensource.com> Mime-Version: 1.0 Content-Disposition: inline Cc: "boris.ostrovsky@amd.com" , "xen-users@lists.xen.org" Subject: Re: [Xen-users] Latest AMD, IOMMU Security Change causing CPU0 Panic and general Problems with AMD+IOMMU changes X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: 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 11.02.13 at 12:22, Ian Campbell wrote: > On Sat, 2013-02-09 at 02:12 +0000, Matthias wrote: >> Hi, >> >> unfortunatly your latest change "AMD,IOMMU: Clean up old entries in >> remapping tables when creating new one" (Changeset 26517 in >> xen-unstable and 25975 in xen-4.2-testing) is causing a CPU0 Panic at >> boot for me. >> >> When i tried to boot latest versions of xen unstable or xen-testing, >> my dom0 gives me the message: >> >> (XEN) ************************************* >> (XEN) Panic on CPU 0: >> (XEN) DATAL PAGE FAULT >> (XEN) [error_code=0000] >> (XEN) Faulting linear address: 0000000000000000 >> (XEN) ************************************* > > I think this is fixed by "[PATCH 1/2] AMD IOMMU: also spot missing > IO-APIC entries in IVRS table" posted to xen-devel on Wednesday. > Message-ID <511264B402000078000BC754@nat28.tlf.novell.com> Without a full register/stack trace I would also guess so, but in that mode it's no more than a guess really. Jan _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Tue Feb 12 09:22:23 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 12 Feb 2013 09:22: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 1U5C33-0005yc-T6; Tue, 12 Feb 2013 09:21:09 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U5C31-0005yU-Mf for xen-users@lists.xen.org; Tue, 12 Feb 2013 09:21:08 +0000 Received: from [85.158.139.211:23428] by server-8.bemta-5.messagelabs.com id D6/7C-19075-2890A115; Tue, 12 Feb 2013 09:21:06 +0000 X-Env-Sender: matthias.kannenberg@googlemail.com X-Msg-Ref: server-4.tower-206.messagelabs.com!1360660865!22092759!1 X-Originating-IP: [74.125.82.180] X-SpamReason: No, hits=0.8 required=7.0 tests=BODY_RANDOM_LONG, RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 25106 invoked from network); 12 Feb 2013 09:21:05 -0000 Received: from mail-we0-f180.google.com (HELO mail-we0-f180.google.com) (74.125.82.180) by server-4.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 12 Feb 2013 09:21:05 -0000 Received: by mail-we0-f180.google.com with SMTP id k14so5428854wer.39 for ; Tue, 12 Feb 2013 01:21:05 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=20120113; h=x-received:mime-version:in-reply-to:references:from:date:message-id :subject:to:cc:content-type:content-transfer-encoding; bh=tPF+42UFPF4+DpEQ86QPx4WpPxPrfAp+qf/zus/jOsI=; b=oMzOiZborzjUfpPIgfXir2Sq8/6jr1TsGo5AOTHwA3Mn91jJ6kneUiCaHi/CQwqDLg NL+rDUnY4dWGcZ9CTKvoz0w/WpYtz84vFir6yhiQUDtYoDZnxAZIwzJ9tY7wwLVufoCR MvjPZaMX215k3h5rWiyoi3bC+gE88hTc2+bIYMAZNz/KCkfXmzbJ8UYhzqT97EVLKyam wwXPLa+qqWsAXhiPF4ygpFV7jr0vAnNBquePZZpqJm0U4LXFsQvjQ9DGCHOPgGIuAPgr J7xCcdWyL66NGkXaPgTdQ8wKZvaKmhMJv7OSgSxoE27zrgRftBt56DcYwFUztYbooR9W bd+w== X-Received: by 10.194.19.97 with SMTP id d1mr14846808wje.52.1360660865434; Tue, 12 Feb 2013 01:21:05 -0800 (PST) MIME-Version: 1.0 Received: by 10.194.80.68 with HTTP; Tue, 12 Feb 2013 01:20:45 -0800 (PST) In-Reply-To: References: <1360274160.57405.YahooMailNeo@web172003.mail.ir2.yahoo.com> From: Matthias Date: Tue, 12 Feb 2013 10:20:45 +0100 Message-ID: To: "xen-users@lists.xen.org" Cc: Casey DeLorme , David TECHER Subject: Re: [Xen-users] ATI/AMDs atikmpag.sys BSOD while 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="iso-8859-1" Content-Transfer-Encoding: quoted-printable Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org Hi and thank you both for your input. >From what I can tell, the things you mentioned are pretty similar to what i wrote in my summary in the initial mail. But it's interesting that you both got different cards running with CCC. So the CCC might be an actual issue of either vga- and mainboard combo or vendor specific. May I ask what setup's you got, especially the vendors / exact models of your HD6870. ? For the well-known fix for the atikmpaq.sys BSOD, at least in my opinion you can ignore all the solutions posted which are not xen related. I think the BSOD here is clearly xen related since at least for my it only happens with the xl toolstack and not the xm one, with the same domU. But if someone really got lucky with such a non-xen fix, it would be interesting to see, too.. Last but not least, can you say something about your setup? I would be especially curious about if you do some vga bios stuff, like extracting and including it into the xen build, and what kernel and domU parameters you use, for example if iommu=3D1 or iomu=3Dsoft @ kernel and stuff like pci_msitranslate=3D1 and pci_powermanagement in domU config (and if the viridian=3D1 option does actually do anything).. There are a lot of vga passthrough tutorials lately, but from what it's worth, in my opinion they all lack some detail because everyone simply describes the setup he got working and there is no comprehensive summary about the benefits of the different options. It would be great if you can help with your experience. 2013/2/7 Casey DeLorme : > I have an HD 6870 and working CCC, tested on both Windows 7 and windows 8. > Don't have any BSoD's either. > > I only had problems with CCC and drivers when I attempted to install or > update drivers without having freshly rebooted or ejected the card. > > Unfortunately Windows 8 attempts to auto-install the drivers at boot time > and this caused some headaches during my first go at it. > > I experience performance problems after rebooting the HVM, to fix it I ju= st > eject the card from the "Safely Remove Hardware and Eject Media" icon. > > > On Thu, Feb 7, 2013 at 4:56 PM, David TECHER wrote: >> >> Issues for CCC depends on your Video Card too. >> >> - Got a HD 79070. It worked for me to add CCC while installing the 13.2 >> beta driver. >> >> Unfortunately there was BSOD issue when rebooting the domU. >> >> I had to install .NET 4 Framework and CCC now works as expected :) >> >> - CCC is not supposed to work for HD 6870 but it worked for HD 7970. >> >> FYI to fix atikmap.sys issue there is a well-known workaround with >> something like >> >> >> http://www.computertipsfree.com/fix-43029-atikmdag-sys-blue-screen-bsod-= in-windows-7/ >> >> expand -r atikmdag.sy_ atikmdag.sys >> >> But it doesn't work for me :( >> >> The good news is that I've just installed Crysis 3 beta demo. It works >> like a charm! >> >> >> ________________________________ >> De : Matthias >> =C0 : xen-users@lists.xen.org >> Envoy=E9 le : Jeudi 7 f=E9vrier 2013 20h14 >> Objet : [Xen-users] ATI/AMDs atikmpag.sys BSOD while vga passthrough >> >> Hi everyone >> >> since I'm currently migrating from xm to xl and now are also a victim >> of the said error, I started researching on it and found that many >> people had the issue but not many found solution and behind this BSOD >> (=3DBluescreen of Death), there are actually multiple errors in hiding. >> >> What I would like to do is gather as much info as possible in this >> thread to form a kind of comprehensive guide to fixing this issue. >> >> From what i gathered so far, there are at least 3 different problems >> with the same symptopms. >> >> 1) >> Situation: After booting the dom0 and booting a windows domU with an >> ATI/AMD Card, Windows generally works fine, but after rebooting the >> system, or shutting down / restarting, the Bluescreen occurs or the >> performance massively below normal. >> Error: Most likely this is cause the Card is not properly resetted (no >> FLR [function level reset] ) >> Solution: If the domU reboots into BSOD, you are screwed and have to >> reboot the dom0. If it only degrades performance, eject the card and >> reinitialize to perform a manual reset. Or use the xm toolkit. >> Status: Don't know if it is fixed yet >> Source: http://lists.xen.org/archives/html/xen-users/2012-02/msg00443.ht= ml >> , http://wiki.xen.org/wiki/Talk:Xen_VGA_Passthrough_Tested_Adapters >> >> 2) >> Situation: Booting a windows domU results in a BSOD when the CCC >> (=3DCatalyst Control Center) installed. >> Error: The CCC tries to set some specific settings (most likely >> performance tweaks) within the driver which the driver can't pass to >> the vga through passthrough mode. Result is a BSOD. >> Solution: Deinstall the CCC in windows safe mode. The driver itself >> works without it pretty fine. >> Status: Don't know if it is fixed yet >> Source: http://lists.xen.org/archives/html/xen-users/2012-03/msg00617.ht= ml >> Note: I don't really know if this holds for the Vision Engine Control >> center, too. the VECC is basically the same as the CCC, so i assume it >> does. I simply haven't found any things referencing it. >> >> 3) >> Situation: This is actually the issue I have. Things seem a lot more >> random then the other ones. A BSOD happens basically in 80% of booting >> the Windows domU. Which means, after rebooting dom0, it mostly works. >> Rebooting or shutting down / starting the domU works sometimes (Once i >> achieved 6 consecutive reboots or shutdowns / starts before the BSOD >> happened) but after I get one Bluescreen, almost never (I can't >> exactly remember if really 'never') comes up again. Of course I tried >> the above solutions but this didn't helped me. I also tried different >> different versions of the Catalyst driver (from 12/1 to 13/1) and >> current releases of xen-4.2-testing and xen-unsable. As I said, this >> is when using the xl toolkit. I never had this issues using xm. >> I thought this might belinked to me passing other PCI devices in >> addition (I'm passing some USB controller to the domU) but even >> deactivating them didn't help. What I actually found helping boosting >> the success rate (but not solving the overall issue) is deinstalling >> all VGA-Related AMD Driver. Windows then runs on it's own VGA-Driver >> (the graphic card is currectly identified and this is an actual ati >> driver, so I'm not talking about some generic standard vga driver. I >> don't know where is driver is coming from). >> I've attached an analysis file i've gethered from the bluescreen crash >> dump. I created it using BluescreenView. This is more for currectly >> identifieng the different BSODs, I guess. >> >> >> Some Infos: >> Kernel: 3.7.4 kernel.org kernel without patches >> Xen: latest xen-unstable (but also tested with xen-4.2-testing) >> Processor: AMD Phenom 1090T >> Mainboard: Asus Crossfire IV >> VGA: Radeon HD5700 and Radeon HD5450 >> Driver: Currently running Catalyst 13/1 but tested nearly everything >> between 12/1 and 13/1 >> >> Error: Don't know yet >> Solution: Don't know yet >> Status: unsolved >> Source: >> >> >> Okay, so basically that's the story. It would be great if some people >> can complete and extend the list. Especially some who already fixed >> the issue on their side. (And of course it would be great if someone >> has an idea for my problem). >> >> Thanks >> >> _______________________________________________ >> 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 Tue Feb 12 09:22:23 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 12 Feb 2013 09:22: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 1U5C33-0005yc-T6; Tue, 12 Feb 2013 09:21:09 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U5C31-0005yU-Mf for xen-users@lists.xen.org; Tue, 12 Feb 2013 09:21:08 +0000 Received: from [85.158.139.211:23428] by server-8.bemta-5.messagelabs.com id D6/7C-19075-2890A115; Tue, 12 Feb 2013 09:21:06 +0000 X-Env-Sender: matthias.kannenberg@googlemail.com X-Msg-Ref: server-4.tower-206.messagelabs.com!1360660865!22092759!1 X-Originating-IP: [74.125.82.180] X-SpamReason: No, hits=0.8 required=7.0 tests=BODY_RANDOM_LONG, RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 25106 invoked from network); 12 Feb 2013 09:21:05 -0000 Received: from mail-we0-f180.google.com (HELO mail-we0-f180.google.com) (74.125.82.180) by server-4.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 12 Feb 2013 09:21:05 -0000 Received: by mail-we0-f180.google.com with SMTP id k14so5428854wer.39 for ; Tue, 12 Feb 2013 01:21:05 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=20120113; h=x-received:mime-version:in-reply-to:references:from:date:message-id :subject:to:cc:content-type:content-transfer-encoding; bh=tPF+42UFPF4+DpEQ86QPx4WpPxPrfAp+qf/zus/jOsI=; b=oMzOiZborzjUfpPIgfXir2Sq8/6jr1TsGo5AOTHwA3Mn91jJ6kneUiCaHi/CQwqDLg NL+rDUnY4dWGcZ9CTKvoz0w/WpYtz84vFir6yhiQUDtYoDZnxAZIwzJ9tY7wwLVufoCR MvjPZaMX215k3h5rWiyoi3bC+gE88hTc2+bIYMAZNz/KCkfXmzbJ8UYhzqT97EVLKyam wwXPLa+qqWsAXhiPF4ygpFV7jr0vAnNBquePZZpqJm0U4LXFsQvjQ9DGCHOPgGIuAPgr J7xCcdWyL66NGkXaPgTdQ8wKZvaKmhMJv7OSgSxoE27zrgRftBt56DcYwFUztYbooR9W bd+w== X-Received: by 10.194.19.97 with SMTP id d1mr14846808wje.52.1360660865434; Tue, 12 Feb 2013 01:21:05 -0800 (PST) MIME-Version: 1.0 Received: by 10.194.80.68 with HTTP; Tue, 12 Feb 2013 01:20:45 -0800 (PST) In-Reply-To: References: <1360274160.57405.YahooMailNeo@web172003.mail.ir2.yahoo.com> From: Matthias Date: Tue, 12 Feb 2013 10:20:45 +0100 Message-ID: To: "xen-users@lists.xen.org" Cc: Casey DeLorme , David TECHER Subject: Re: [Xen-users] ATI/AMDs atikmpag.sys BSOD while 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="iso-8859-1" Content-Transfer-Encoding: quoted-printable Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org Hi and thank you both for your input. >From what I can tell, the things you mentioned are pretty similar to what i wrote in my summary in the initial mail. But it's interesting that you both got different cards running with CCC. So the CCC might be an actual issue of either vga- and mainboard combo or vendor specific. May I ask what setup's you got, especially the vendors / exact models of your HD6870. ? For the well-known fix for the atikmpaq.sys BSOD, at least in my opinion you can ignore all the solutions posted which are not xen related. I think the BSOD here is clearly xen related since at least for my it only happens with the xl toolstack and not the xm one, with the same domU. But if someone really got lucky with such a non-xen fix, it would be interesting to see, too.. Last but not least, can you say something about your setup? I would be especially curious about if you do some vga bios stuff, like extracting and including it into the xen build, and what kernel and domU parameters you use, for example if iommu=3D1 or iomu=3Dsoft @ kernel and stuff like pci_msitranslate=3D1 and pci_powermanagement in domU config (and if the viridian=3D1 option does actually do anything).. There are a lot of vga passthrough tutorials lately, but from what it's worth, in my opinion they all lack some detail because everyone simply describes the setup he got working and there is no comprehensive summary about the benefits of the different options. It would be great if you can help with your experience. 2013/2/7 Casey DeLorme : > I have an HD 6870 and working CCC, tested on both Windows 7 and windows 8. > Don't have any BSoD's either. > > I only had problems with CCC and drivers when I attempted to install or > update drivers without having freshly rebooted or ejected the card. > > Unfortunately Windows 8 attempts to auto-install the drivers at boot time > and this caused some headaches during my first go at it. > > I experience performance problems after rebooting the HVM, to fix it I ju= st > eject the card from the "Safely Remove Hardware and Eject Media" icon. > > > On Thu, Feb 7, 2013 at 4:56 PM, David TECHER wrote: >> >> Issues for CCC depends on your Video Card too. >> >> - Got a HD 79070. It worked for me to add CCC while installing the 13.2 >> beta driver. >> >> Unfortunately there was BSOD issue when rebooting the domU. >> >> I had to install .NET 4 Framework and CCC now works as expected :) >> >> - CCC is not supposed to work for HD 6870 but it worked for HD 7970. >> >> FYI to fix atikmap.sys issue there is a well-known workaround with >> something like >> >> >> http://www.computertipsfree.com/fix-43029-atikmdag-sys-blue-screen-bsod-= in-windows-7/ >> >> expand -r atikmdag.sy_ atikmdag.sys >> >> But it doesn't work for me :( >> >> The good news is that I've just installed Crysis 3 beta demo. It works >> like a charm! >> >> >> ________________________________ >> De : Matthias >> =C0 : xen-users@lists.xen.org >> Envoy=E9 le : Jeudi 7 f=E9vrier 2013 20h14 >> Objet : [Xen-users] ATI/AMDs atikmpag.sys BSOD while vga passthrough >> >> Hi everyone >> >> since I'm currently migrating from xm to xl and now are also a victim >> of the said error, I started researching on it and found that many >> people had the issue but not many found solution and behind this BSOD >> (=3DBluescreen of Death), there are actually multiple errors in hiding. >> >> What I would like to do is gather as much info as possible in this >> thread to form a kind of comprehensive guide to fixing this issue. >> >> From what i gathered so far, there are at least 3 different problems >> with the same symptopms. >> >> 1) >> Situation: After booting the dom0 and booting a windows domU with an >> ATI/AMD Card, Windows generally works fine, but after rebooting the >> system, or shutting down / restarting, the Bluescreen occurs or the >> performance massively below normal. >> Error: Most likely this is cause the Card is not properly resetted (no >> FLR [function level reset] ) >> Solution: If the domU reboots into BSOD, you are screwed and have to >> reboot the dom0. If it only degrades performance, eject the card and >> reinitialize to perform a manual reset. Or use the xm toolkit. >> Status: Don't know if it is fixed yet >> Source: http://lists.xen.org/archives/html/xen-users/2012-02/msg00443.ht= ml >> , http://wiki.xen.org/wiki/Talk:Xen_VGA_Passthrough_Tested_Adapters >> >> 2) >> Situation: Booting a windows domU results in a BSOD when the CCC >> (=3DCatalyst Control Center) installed. >> Error: The CCC tries to set some specific settings (most likely >> performance tweaks) within the driver which the driver can't pass to >> the vga through passthrough mode. Result is a BSOD. >> Solution: Deinstall the CCC in windows safe mode. The driver itself >> works without it pretty fine. >> Status: Don't know if it is fixed yet >> Source: http://lists.xen.org/archives/html/xen-users/2012-03/msg00617.ht= ml >> Note: I don't really know if this holds for the Vision Engine Control >> center, too. the VECC is basically the same as the CCC, so i assume it >> does. I simply haven't found any things referencing it. >> >> 3) >> Situation: This is actually the issue I have. Things seem a lot more >> random then the other ones. A BSOD happens basically in 80% of booting >> the Windows domU. Which means, after rebooting dom0, it mostly works. >> Rebooting or shutting down / starting the domU works sometimes (Once i >> achieved 6 consecutive reboots or shutdowns / starts before the BSOD >> happened) but after I get one Bluescreen, almost never (I can't >> exactly remember if really 'never') comes up again. Of course I tried >> the above solutions but this didn't helped me. I also tried different >> different versions of the Catalyst driver (from 12/1 to 13/1) and >> current releases of xen-4.2-testing and xen-unsable. As I said, this >> is when using the xl toolkit. I never had this issues using xm. >> I thought this might belinked to me passing other PCI devices in >> addition (I'm passing some USB controller to the domU) but even >> deactivating them didn't help. What I actually found helping boosting >> the success rate (but not solving the overall issue) is deinstalling >> all VGA-Related AMD Driver. Windows then runs on it's own VGA-Driver >> (the graphic card is currectly identified and this is an actual ati >> driver, so I'm not talking about some generic standard vga driver. I >> don't know where is driver is coming from). >> I've attached an analysis file i've gethered from the bluescreen crash >> dump. I created it using BluescreenView. This is more for currectly >> identifieng the different BSODs, I guess. >> >> >> Some Infos: >> Kernel: 3.7.4 kernel.org kernel without patches >> Xen: latest xen-unstable (but also tested with xen-4.2-testing) >> Processor: AMD Phenom 1090T >> Mainboard: Asus Crossfire IV >> VGA: Radeon HD5700 and Radeon HD5450 >> Driver: Currently running Catalyst 13/1 but tested nearly everything >> between 12/1 and 13/1 >> >> Error: Don't know yet >> Solution: Don't know yet >> Status: unsolved >> Source: >> >> >> Okay, so basically that's the story. It would be great if some people >> can complete and extend the list. Especially some who already fixed >> the issue on their side. (And of course it would be great if someone >> has an idea for my problem). >> >> Thanks >> >> _______________________________________________ >> 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 Tue Feb 12 10:06:56 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 12 Feb 2013 10:06: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 1U5CkI-0007Kq-7e; Tue, 12 Feb 2013 10:05:50 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U5CkH-0007Kj-1j for xen-users@lists.xen.org; Tue, 12 Feb 2013 10:05:49 +0000 Received: from [85.158.137.99:22583] by server-12.bemta-3.messagelabs.com id 7D/49-05889-CF31A115; Tue, 12 Feb 2013 10:05:48 +0000 X-Env-Sender: pigeon@pigeond.net X-Msg-Ref: server-16.tower-217.messagelabs.com!1360663545!21033775!1 X-Originating-IP: [203.59.1.226] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogMjAzLjU5LjEuMjI2ID0+IDE2MTk4\n X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 23566 invoked from network); 12 Feb 2013 10:05:47 -0000 Received: from icp-osb-irony-out9.external.iinet.net.au (HELO icp-osb-irony-out9.external.iinet.net.au) (203.59.1.226) by server-16.tower-217.messagelabs.com with SMTP; 12 Feb 2013 10:05:47 -0000 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: Av4EACwTGlF8lWUl/2dsb2JhbABEwTEWc4IfAQEEATpECwsNFCUPOgENBogfBa9zkAeSBwOWI4YUikCDGg X-IronPort-AV: E=Sophos;i="4.84,648,1355068800"; d="scan'208";a="84870755" Received: from unknown (HELO torankusu.pigeond.net) ([124.149.101.37]) by icp-osb-irony-out9.iinet.net.au with ESMTP; 12 Feb 2013 18:05:43 +0800 Received: from furiza.pigeond.net ([192.168.42.20]:37170 helo=pigeond.net) by torankusu.pigeond.net with esmtp (Exim 4.72) (envelope-from ) id 1U5CkA-0006wb-Ds for xen-users@lists.xen.org; Tue, 12 Feb 2013 21:05:42 +1100 Date: Tue, 12 Feb 2013 21:05:41 +1100 From: Howell Tam To: "xen-users@lists.xen.org" Message-ID: <20130212210541.3b71b98f@pigeond.net> In-Reply-To: <6035A0D088A63A46850C3988ED045A4B35667928@BITCOM1.int.sbss.com.au> References: <20130210235853.4ebb70b8@pigeond.net> <20130212084728.64c49ea1@pigeond.net> <6035A0D088A63A46850C3988ED045A4B35667928@BITCOM1.int.sbss.com.au> Organization: pigeond.net X-Mailer: Claws Mail 3.8.1 (GTK+ 2.24.10; x86_64-pc-linux-gnu) Mime-Version: 1.0 Subject: Re: [Xen-users] Dom0 freeze on HVM DomU Windows reboot with 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 > If you are using GPLPV, I have a very beta version that no longer > tries to do anything funky with interrupts and may make a difference > here... unless you are also freezing without using GPLPV in which > case it won't. Thanks for the tip. I just uninstalled the GPLPV driver in the win7 guest, and now that win7 won't boot anymore, it just gives me a BSOD at startup. The BSOD stays if I disable the PCI/VGA passthrough so it's not related I guess. -- Regards, Howell. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Tue Feb 12 10:06:56 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 12 Feb 2013 10:06: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 1U5CkI-0007Kq-7e; Tue, 12 Feb 2013 10:05:50 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U5CkH-0007Kj-1j for xen-users@lists.xen.org; Tue, 12 Feb 2013 10:05:49 +0000 Received: from [85.158.137.99:22583] by server-12.bemta-3.messagelabs.com id 7D/49-05889-CF31A115; Tue, 12 Feb 2013 10:05:48 +0000 X-Env-Sender: pigeon@pigeond.net X-Msg-Ref: server-16.tower-217.messagelabs.com!1360663545!21033775!1 X-Originating-IP: [203.59.1.226] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogMjAzLjU5LjEuMjI2ID0+IDE2MTk4\n X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 23566 invoked from network); 12 Feb 2013 10:05:47 -0000 Received: from icp-osb-irony-out9.external.iinet.net.au (HELO icp-osb-irony-out9.external.iinet.net.au) (203.59.1.226) by server-16.tower-217.messagelabs.com with SMTP; 12 Feb 2013 10:05:47 -0000 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: Av4EACwTGlF8lWUl/2dsb2JhbABEwTEWc4IfAQEEATpECwsNFCUPOgENBogfBa9zkAeSBwOWI4YUikCDGg X-IronPort-AV: E=Sophos;i="4.84,648,1355068800"; d="scan'208";a="84870755" Received: from unknown (HELO torankusu.pigeond.net) ([124.149.101.37]) by icp-osb-irony-out9.iinet.net.au with ESMTP; 12 Feb 2013 18:05:43 +0800 Received: from furiza.pigeond.net ([192.168.42.20]:37170 helo=pigeond.net) by torankusu.pigeond.net with esmtp (Exim 4.72) (envelope-from ) id 1U5CkA-0006wb-Ds for xen-users@lists.xen.org; Tue, 12 Feb 2013 21:05:42 +1100 Date: Tue, 12 Feb 2013 21:05:41 +1100 From: Howell Tam To: "xen-users@lists.xen.org" Message-ID: <20130212210541.3b71b98f@pigeond.net> In-Reply-To: <6035A0D088A63A46850C3988ED045A4B35667928@BITCOM1.int.sbss.com.au> References: <20130210235853.4ebb70b8@pigeond.net> <20130212084728.64c49ea1@pigeond.net> <6035A0D088A63A46850C3988ED045A4B35667928@BITCOM1.int.sbss.com.au> Organization: pigeond.net X-Mailer: Claws Mail 3.8.1 (GTK+ 2.24.10; x86_64-pc-linux-gnu) Mime-Version: 1.0 Subject: Re: [Xen-users] Dom0 freeze on HVM DomU Windows reboot with 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 > If you are using GPLPV, I have a very beta version that no longer > tries to do anything funky with interrupts and may make a difference > here... unless you are also freezing without using GPLPV in which > case it won't. Thanks for the tip. I just uninstalled the GPLPV driver in the win7 guest, and now that win7 won't boot anymore, it just gives me a BSOD at startup. The BSOD stays if I disable the PCI/VGA passthrough so it's not related I guess. -- Regards, Howell. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Tue Feb 12 10:24:01 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 12 Feb 2013 10:24: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 1U5D15-00008Y-18; Tue, 12 Feb 2013 10:23:11 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U5D12-00008P-OL for xen-users@lists.xen.org; Tue, 12 Feb 2013 10:23:09 +0000 Received: from [85.158.138.51:47100] by server-1.bemta-3.messagelabs.com id C2/0D-08955-B081A115; Tue, 12 Feb 2013 10:23:07 +0000 X-Env-Sender: fabiano.francesconi@gmail.com X-Msg-Ref: server-8.tower-174.messagelabs.com!1360664449!30248482!1 X-Originating-IP: [209.85.215.171] 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.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 21042 invoked from network); 12 Feb 2013 10:20:49 -0000 Received: from mail-ea0-f171.google.com (HELO mail-ea0-f171.google.com) (209.85.215.171) by server-8.tower-174.messagelabs.com with RC4-SHA encrypted SMTP; 12 Feb 2013 10:20:49 -0000 Received: by mail-ea0-f171.google.com with SMTP id c13so82899eaa.16 for ; Tue, 12 Feb 2013 02:20:49 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:date:from:to:message-id:in-reply-to:references:subject :x-mailer:mime-version:content-type:content-transfer-encoding :content-disposition; bh=ZouR8iMM8gkaP7DHugDf3lEZBihGU5dwXgpQ5v38Ews=; b=NhUY5qa3NOq3XeiHTU7MhaFPo6M2alucR1CjuJ9xcsUrJNgCiBaE01gzChW4486aq6 Gh459WhUXBeA0HjurMaB1lht3vIuiKpp3R4y0zi5Y2SFz2IrBIyE9OOxOlor5pMPY2er d/88o+qvbh2PJgb/a5jnnIb7DMLxf44Pxy5Tlqw4kCQtFUm/P2JX5oOvWnWNlhmvQ++U KjmUJ6QPn0AURR/ParX4qeHdxyQmneFD5oR6SmHkfyRmUaEFcuiZUMWDvXlA+BkP3/KA AsUnXaAisaqHeFhzce51fxSoSD5d4Y68wi+PY4kfkwcTu+Fz4Bl3eOVfMRRu7aVFEag2 9E2A== X-Received: by 10.14.176.66 with SMTP id a42mr61197873eem.34.1360664448919; Tue, 12 Feb 2013 02:20:48 -0800 (PST) Received: from [192.168.0.145] (host111-111-dynamic.14-87-r.retail.telecomitalia.it. [87.14.111.111]) by mx.google.com with ESMTPS id q5sm67002928eep.11.2013.02.12.02.20.47 (version=TLSv1 cipher=RC4-SHA bits=128/128); Tue, 12 Feb 2013 02:20:48 -0800 (PST) Date: Tue, 12 Feb 2013 11:20:47 +0100 From: Fabiano Francesconi To: xen-users@lists.xen.org Message-ID: In-Reply-To: <3C0CB81079134B2586C4CB56AC211233@gmail.com> References: <3C0CB81079134B2586C4CB56AC211233@gmail.com> X-Mailer: sparrow 1.6.4 (build 1176) MIME-Version: 1.0 Content-Disposition: inline Subject: Re: [Xen-users] Xen domU PV linux-3.7.0-hardened won'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: 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 Monday 11 February 2013 at 16:25, Fabiano Francesconi wrote: > Hello everybody, > today I was trying to update my domU to linux kernel v3. > > At the moment it's running with a 2.6.38 kernel and it's running smooth. > I simply took the .config and run a make oldconfig in linux v3 sources and what I get is that it won't boot. No kernel bootlog to inspect. > > I'm running xen 4.2.0 on a 32bit paravirt environment. > The dom0 kernel is Linux 3.3.8 and the other domU machine I have is running with the same version of the kernel. > > The sole machine that is giving me troubles is the hardened one, currently running with grsec+pax on the 2.6.38. > > This is my current configuration: > - kernel config file (domU): http://codepad.org/sgnyXLqL > - domU configuration file (xen): http://codepad.org/jdqO3W9H > > This is the output: > > xevelon ~ # xl create -c /xen/configs/caprica > Parsing config from /xen/configs/caprica > Daemon running with PID 4460 > libxl: error: libxl_dom.c:34:libxl__domain_type: unable to get domain type for domid=6 > Unable to attach console > libxl: error: libxl_exec.c:118:libxl_report_child_exitstatus: console child [0] exited with error status 1 > > > xevelon ~ # cat /var/log/xen/xl-caprica.log > Waiting for domain caprica (domid 6) to die [pid 4461] > Domain 6 has shut down, reason code 3 0x3 > Action for shutdown reason code 3 is destroy > Domain 6 needs to be cleaned up: destroying the domain > Done. Exiting now > > > > xl dmesg: > XEN) d6:v0: unhandled page fault (ec=0000) > (XEN) Pagetable walk from 00000e94: > (XEN) L3[0x000] = 0000000000000000 ffffffff > (XEN) domain_crash_sync called from entry.S (ff1ef878) > (XEN) Domain 6 (vcpu#0) crashed on cpu#3: > (XEN) ----[ Xen-4.2.0 x86_32p debug=n Not tainted ]---- > (XEN) CPU: 3 > (XEN) EIP: e019:[] > (XEN) EFLAGS: 00000206 EM: 1 CONTEXT: pv guest > (XEN) eax: 00003f3f ebx: 00000000 ecx: 00000000 edx: 00000000 > (XEN) esi: c1a80000 edi: c14b1000 ebp: 00000000 esp: c1601f3c > (XEN) cr0: 8005003b cr4: 000006f4 cr3: 28e51000 cr2: 00000e94 > (XEN) ds: e021 es: e021 fs: e021 gs: e021 ss: e021 cs: e019 > (XEN) Guest stack trace from esp=c1601f3c: > (XEN) 00000000 c10b2fc2 0001e019 00010006 00000000 c16561b2 00000000 00000000 > (XEN) 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 > (XEN) 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 > (XEN) 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 > (XEN) 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 > (XEN) 00000000 00000000 00000000 00000000 00000000 00000000 c1a80000 c14b1000 > (XEN) 00000000 00000000 c16dad04 00000068 00000000 00000000 00000000 00000000 > (XEN) 014a5000 c1023a28 00000082 00000000 00000000 00000000 00000000 c16dad04 > (XEN) 00000000 00000000 00000000 00000068 00000060 00000068 00000068 000000d8 > (XEN) 00000000 00000000 80000000 00000000 00000000 00000000 00000000 00000000 > (XEN) 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 > (XEN) 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 > (XEN) 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 > (XEN) 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 > (XEN) 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 > (XEN) 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 > (XEN) 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 > (XEN) 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 > (XEN) 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 > (XEN) 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 > > > > > - xl info: http://codepad.org/wJCTXtoD > - xl create (-vvv ultraverbose): http://codepad.org/XhXN5ztl > > Does somebody have any clue about it? > > Thank you so much!-- > Fabiano Francesconi [GPG key: 0x81E53461] I think I found what the problem was. The problem comes from the grsec section in the kernel. In particular, it is related to one of the miscellaneous hardening features of PaX. According to what I discovered, it may be one of the following (I disabled all three): - CONFIG_PAX_MEMORY_SANITIZE - CONFIG_PAX_MEMORY_STACKLEAK - CONFIG_PAX_USERCOPY I tend to be more biased towards the last since I get a lot of warning during the compile phase about copy_to_user and copy_from_user syscalls. I think this should be pointed out to the GRSEC team. -- Fabiano Francesconi [GPG key: 0x81E53461] _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Tue Feb 12 10:24:01 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 12 Feb 2013 10:24: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 1U5D15-00008Y-18; Tue, 12 Feb 2013 10:23:11 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U5D12-00008P-OL for xen-users@lists.xen.org; Tue, 12 Feb 2013 10:23:09 +0000 Received: from [85.158.138.51:47100] by server-1.bemta-3.messagelabs.com id C2/0D-08955-B081A115; Tue, 12 Feb 2013 10:23:07 +0000 X-Env-Sender: fabiano.francesconi@gmail.com X-Msg-Ref: server-8.tower-174.messagelabs.com!1360664449!30248482!1 X-Originating-IP: [209.85.215.171] 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.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 21042 invoked from network); 12 Feb 2013 10:20:49 -0000 Received: from mail-ea0-f171.google.com (HELO mail-ea0-f171.google.com) (209.85.215.171) by server-8.tower-174.messagelabs.com with RC4-SHA encrypted SMTP; 12 Feb 2013 10:20:49 -0000 Received: by mail-ea0-f171.google.com with SMTP id c13so82899eaa.16 for ; Tue, 12 Feb 2013 02:20:49 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:date:from:to:message-id:in-reply-to:references:subject :x-mailer:mime-version:content-type:content-transfer-encoding :content-disposition; bh=ZouR8iMM8gkaP7DHugDf3lEZBihGU5dwXgpQ5v38Ews=; b=NhUY5qa3NOq3XeiHTU7MhaFPo6M2alucR1CjuJ9xcsUrJNgCiBaE01gzChW4486aq6 Gh459WhUXBeA0HjurMaB1lht3vIuiKpp3R4y0zi5Y2SFz2IrBIyE9OOxOlor5pMPY2er d/88o+qvbh2PJgb/a5jnnIb7DMLxf44Pxy5Tlqw4kCQtFUm/P2JX5oOvWnWNlhmvQ++U KjmUJ6QPn0AURR/ParX4qeHdxyQmneFD5oR6SmHkfyRmUaEFcuiZUMWDvXlA+BkP3/KA AsUnXaAisaqHeFhzce51fxSoSD5d4Y68wi+PY4kfkwcTu+Fz4Bl3eOVfMRRu7aVFEag2 9E2A== X-Received: by 10.14.176.66 with SMTP id a42mr61197873eem.34.1360664448919; Tue, 12 Feb 2013 02:20:48 -0800 (PST) Received: from [192.168.0.145] (host111-111-dynamic.14-87-r.retail.telecomitalia.it. [87.14.111.111]) by mx.google.com with ESMTPS id q5sm67002928eep.11.2013.02.12.02.20.47 (version=TLSv1 cipher=RC4-SHA bits=128/128); Tue, 12 Feb 2013 02:20:48 -0800 (PST) Date: Tue, 12 Feb 2013 11:20:47 +0100 From: Fabiano Francesconi To: xen-users@lists.xen.org Message-ID: In-Reply-To: <3C0CB81079134B2586C4CB56AC211233@gmail.com> References: <3C0CB81079134B2586C4CB56AC211233@gmail.com> X-Mailer: sparrow 1.6.4 (build 1176) MIME-Version: 1.0 Content-Disposition: inline Subject: Re: [Xen-users] Xen domU PV linux-3.7.0-hardened won'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: 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 Monday 11 February 2013 at 16:25, Fabiano Francesconi wrote: > Hello everybody, > today I was trying to update my domU to linux kernel v3. > > At the moment it's running with a 2.6.38 kernel and it's running smooth. > I simply took the .config and run a make oldconfig in linux v3 sources and what I get is that it won't boot. No kernel bootlog to inspect. > > I'm running xen 4.2.0 on a 32bit paravirt environment. > The dom0 kernel is Linux 3.3.8 and the other domU machine I have is running with the same version of the kernel. > > The sole machine that is giving me troubles is the hardened one, currently running with grsec+pax on the 2.6.38. > > This is my current configuration: > - kernel config file (domU): http://codepad.org/sgnyXLqL > - domU configuration file (xen): http://codepad.org/jdqO3W9H > > This is the output: > > xevelon ~ # xl create -c /xen/configs/caprica > Parsing config from /xen/configs/caprica > Daemon running with PID 4460 > libxl: error: libxl_dom.c:34:libxl__domain_type: unable to get domain type for domid=6 > Unable to attach console > libxl: error: libxl_exec.c:118:libxl_report_child_exitstatus: console child [0] exited with error status 1 > > > xevelon ~ # cat /var/log/xen/xl-caprica.log > Waiting for domain caprica (domid 6) to die [pid 4461] > Domain 6 has shut down, reason code 3 0x3 > Action for shutdown reason code 3 is destroy > Domain 6 needs to be cleaned up: destroying the domain > Done. Exiting now > > > > xl dmesg: > XEN) d6:v0: unhandled page fault (ec=0000) > (XEN) Pagetable walk from 00000e94: > (XEN) L3[0x000] = 0000000000000000 ffffffff > (XEN) domain_crash_sync called from entry.S (ff1ef878) > (XEN) Domain 6 (vcpu#0) crashed on cpu#3: > (XEN) ----[ Xen-4.2.0 x86_32p debug=n Not tainted ]---- > (XEN) CPU: 3 > (XEN) EIP: e019:[] > (XEN) EFLAGS: 00000206 EM: 1 CONTEXT: pv guest > (XEN) eax: 00003f3f ebx: 00000000 ecx: 00000000 edx: 00000000 > (XEN) esi: c1a80000 edi: c14b1000 ebp: 00000000 esp: c1601f3c > (XEN) cr0: 8005003b cr4: 000006f4 cr3: 28e51000 cr2: 00000e94 > (XEN) ds: e021 es: e021 fs: e021 gs: e021 ss: e021 cs: e019 > (XEN) Guest stack trace from esp=c1601f3c: > (XEN) 00000000 c10b2fc2 0001e019 00010006 00000000 c16561b2 00000000 00000000 > (XEN) 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 > (XEN) 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 > (XEN) 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 > (XEN) 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 > (XEN) 00000000 00000000 00000000 00000000 00000000 00000000 c1a80000 c14b1000 > (XEN) 00000000 00000000 c16dad04 00000068 00000000 00000000 00000000 00000000 > (XEN) 014a5000 c1023a28 00000082 00000000 00000000 00000000 00000000 c16dad04 > (XEN) 00000000 00000000 00000000 00000068 00000060 00000068 00000068 000000d8 > (XEN) 00000000 00000000 80000000 00000000 00000000 00000000 00000000 00000000 > (XEN) 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 > (XEN) 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 > (XEN) 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 > (XEN) 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 > (XEN) 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 > (XEN) 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 > (XEN) 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 > (XEN) 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 > (XEN) 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 > (XEN) 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 > > > > > - xl info: http://codepad.org/wJCTXtoD > - xl create (-vvv ultraverbose): http://codepad.org/XhXN5ztl > > Does somebody have any clue about it? > > Thank you so much!-- > Fabiano Francesconi [GPG key: 0x81E53461] I think I found what the problem was. The problem comes from the grsec section in the kernel. In particular, it is related to one of the miscellaneous hardening features of PaX. According to what I discovered, it may be one of the following (I disabled all three): - CONFIG_PAX_MEMORY_SANITIZE - CONFIG_PAX_MEMORY_STACKLEAK - CONFIG_PAX_USERCOPY I tend to be more biased towards the last since I get a lot of warning during the compile phase about copy_to_user and copy_from_user syscalls. I think this should be pointed out to the GRSEC team. -- Fabiano Francesconi [GPG key: 0x81E53461] _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Tue Feb 12 10:25:12 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 12 Feb 2013 10:25: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 1U5D2I-0000E4-P9; Tue, 12 Feb 2013 10:24:26 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U5D2H-0000Dw-5c for xen-users@lists.xen.org; Tue, 12 Feb 2013 10:24:25 +0000 Received: from [85.158.137.99:5235] by server-9.bemta-3.messagelabs.com id 89/CF-09484-3581A115; Tue, 12 Feb 2013 10:24:19 +0000 X-Env-Sender: james.harper@bendigoit.com.au X-Msg-Ref: server-2.tower-217.messagelabs.com!1360664654!20951193!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.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 29155 invoked from network); 12 Feb 2013 10:24:18 -0000 Received: from smtp2.bendigoit.com.au (HELO smtp2.bendigoit.com.au) (203.16.207.99) by server-2.tower-217.messagelabs.com with AES256-SHA encrypted SMTP; 12 Feb 2013 10:24:18 -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 1U5D23-00086f-HI; Tue, 12 Feb 2013 21:24:11 +1100 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.0438.000; Tue, 12 Feb 2013 21:24:11 +1100 From: James Harper To: Howell Tam , "xen-users@lists.xen.org" Thread-Topic: [Xen-users] Dom0 freeze on HVM DomU Windows reboot with VGA passthrough Thread-Index: AQHOCQqRJ9EGzSp9okOqF40XzGZ+vph2A4Bw Date: Tue, 12 Feb 2013 10:24:09 +0000 Message-ID: <6035A0D088A63A46850C3988ED045A4B3566C353@BITCOM1.int.sbss.com.au> References: <20130210235853.4ebb70b8@pigeond.net> <20130212084728.64c49ea1@pigeond.net> <6035A0D088A63A46850C3988ED045A4B35667928@BITCOM1.int.sbss.com.au> <20130212210541.3b71b98f@pigeond.net> In-Reply-To: <20130212210541.3b71b98f@pigeond.net> 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-19632.002 x-tm-as-result: No--42.245500-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] Dom0 freeze on HVM DomU Windows reboot with 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 > > > If you are using GPLPV, I have a very beta version that no longer > > tries to do anything funky with interrupts and may make a difference > > here... unless you are also freezing without using GPLPV in which > > case it won't. > > Thanks for the tip. > > I just uninstalled the GPLPV driver in the win7 guest, and now > that win7 won't boot anymore, it just gives me a BSOD at startup. > > The BSOD stays if I disable the PCI/VGA passthrough so it's not > related I guess. > Uninstalling GPLPV leaves a registry entry present that causes it to not boot. Is the BSoD start with 0x0000007b? If so that's the "cant find boot device" If you can boot of the win7 boot cd then into the recovery console, load the registry hive (eg load c:\windows\system32\config\system) and delete xenpci from anything called upperfilters it should boot again. James _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Tue Feb 12 10:25:12 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 12 Feb 2013 10:25: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 1U5D2I-0000E4-P9; Tue, 12 Feb 2013 10:24:26 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U5D2H-0000Dw-5c for xen-users@lists.xen.org; Tue, 12 Feb 2013 10:24:25 +0000 Received: from [85.158.137.99:5235] by server-9.bemta-3.messagelabs.com id 89/CF-09484-3581A115; Tue, 12 Feb 2013 10:24:19 +0000 X-Env-Sender: james.harper@bendigoit.com.au X-Msg-Ref: server-2.tower-217.messagelabs.com!1360664654!20951193!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.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 29155 invoked from network); 12 Feb 2013 10:24:18 -0000 Received: from smtp2.bendigoit.com.au (HELO smtp2.bendigoit.com.au) (203.16.207.99) by server-2.tower-217.messagelabs.com with AES256-SHA encrypted SMTP; 12 Feb 2013 10:24:18 -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 1U5D23-00086f-HI; Tue, 12 Feb 2013 21:24:11 +1100 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.0438.000; Tue, 12 Feb 2013 21:24:11 +1100 From: James Harper To: Howell Tam , "xen-users@lists.xen.org" Thread-Topic: [Xen-users] Dom0 freeze on HVM DomU Windows reboot with VGA passthrough Thread-Index: AQHOCQqRJ9EGzSp9okOqF40XzGZ+vph2A4Bw Date: Tue, 12 Feb 2013 10:24:09 +0000 Message-ID: <6035A0D088A63A46850C3988ED045A4B3566C353@BITCOM1.int.sbss.com.au> References: <20130210235853.4ebb70b8@pigeond.net> <20130212084728.64c49ea1@pigeond.net> <6035A0D088A63A46850C3988ED045A4B35667928@BITCOM1.int.sbss.com.au> <20130212210541.3b71b98f@pigeond.net> In-Reply-To: <20130212210541.3b71b98f@pigeond.net> 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-19632.002 x-tm-as-result: No--42.245500-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] Dom0 freeze on HVM DomU Windows reboot with 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 > > > If you are using GPLPV, I have a very beta version that no longer > > tries to do anything funky with interrupts and may make a difference > > here... unless you are also freezing without using GPLPV in which > > case it won't. > > Thanks for the tip. > > I just uninstalled the GPLPV driver in the win7 guest, and now > that win7 won't boot anymore, it just gives me a BSOD at startup. > > The BSOD stays if I disable the PCI/VGA passthrough so it's not > related I guess. > Uninstalling GPLPV leaves a registry entry present that causes it to not boot. Is the BSoD start with 0x0000007b? If so that's the "cant find boot device" If you can boot of the win7 boot cd then into the recovery console, load the registry hive (eg load c:\windows\system32\config\system) and delete xenpci from anything called upperfilters it should boot again. James _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Tue Feb 12 10:53:21 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 12 Feb 2013 10:53: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 1U5DTX-0001je-5X; Tue, 12 Feb 2013 10:52:35 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U5DTV-0001jX-J9 for xen-users@lists.xen.org; Tue, 12 Feb 2013 10:52:33 +0000 Received: from [85.158.139.83:62933] by server-11.bemta-5.messagelabs.com id 04/B7-19159-0FE1A115; Tue, 12 Feb 2013 10:52:32 +0000 X-Env-Sender: herydians@gmail.com X-Msg-Ref: server-12.tower-182.messagelabs.com!1360666347!27493696!1 X-Originating-IP: [74.125.82.178] X-SpamReason: No, hits=0.9 required=7.0 tests=HTML_40_50,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14, ML_RADAR_SPEW_LINKS_23, RCVD_BY_IP, spamassassin: X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 28085 invoked from network); 12 Feb 2013 10:52:27 -0000 Received: from mail-we0-f178.google.com (HELO mail-we0-f178.google.com) (74.125.82.178) by server-12.tower-182.messagelabs.com with RC4-SHA encrypted SMTP; 12 Feb 2013 10:52:27 -0000 Received: by mail-we0-f178.google.com with SMTP id x48so5636629wey.37 for ; Tue, 12 Feb 2013 02:52:26 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:content-type; bh=YggVX9655Y8Yt8j39vZ+IqxLaKFqVyzMylVHcMzz0iU=; b=C2soDPCYeFTxw8zvz3RWWhmhHaxR+8JNN3XJVEALi5bjOqAz4r3LZr8HAnmX3GSkcC dz5/yxvwrlExjS7U0Olgcq+kV4wxE0s+GJn6sKtCncxtFuO3ddOM3iJRTGhIM1FI/NQN 00bSmbgE5ZYo/I6lmMPHHOnLnLnQP3A1MDo099wsaa22KWLaYS6aJSIjvEXTWfRnWNq2 LnQW3WsUD7oXbE4uLYWaAYDMhf5Qc0KduaoBixW7Xvxn2T5yYPClFS2pRGv0JUh5M7fF asKS1YdxvMB4f5GinYwgwXn9tg41WzxBJ8lbeQU/Vh7D0579/xvpyVoTMoEBWhVYPgnD JXyQ== MIME-Version: 1.0 X-Received: by 10.180.84.131 with SMTP id z3mr2232261wiy.25.1360666346880; Tue, 12 Feb 2013 02:52:26 -0800 (PST) Received: by 10.216.107.132 with HTTP; Tue, 12 Feb 2013 02:52:26 -0800 (PST) In-Reply-To: References: Date: Tue, 12 Feb 2013 11:52:26 +0100 Message-ID: From: Hery Dian Septama To: xen-users Subject: [Xen-users] Remus on Ubuntu 12.04 with XEN 4.1 AMD 64 X-BeenThere: xen-users@lists.xen.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="===============1735499249342719722==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============1735499249342719722== Content-Type: multipart/alternative; boundary=f46d043bdd64437fb904d584d296 --f46d043bdd64437fb904d584d296 Content-Type: text/plain; charset=UTF-8 Dear all, I am new in XEN and quite confusing with this remus installation. Could anyone point me out how to do it. I have Ubuntu 12.04 with kernel 3.2.0-29-generic 64 bit bot for Dom0 dan DomU with Para Virtualization. I have installed Xen4.1 AMD 64 bit by following this https://help.ubuntu.com/community/XenProposed. I have succesfully done the migration from one machine into another. How ever I want to run this remus to support my server. I have read http://remusha.wikidot.com/ to configuring and install remus. Could any body point me out what I should do? am I have to re-installed my machine with supported kernel firstly (kernel 2.6.x) or something. Thank you very much. Regards, Agya _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel --f46d043bdd64437fb904d584d296 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Dear all,

I am new in XEN and quite= confusing with this remus installation. Could anyone point me out how to d= o it.
I have Ubuntu 12.04 with kernel 3.2.0-29-generic 64 bit bot for Dom0 dan Do= mU with Para Virtualization. I have installed Xen4.1 AMD 64 bit by followin= g this=C2=A0https://help.ubuntu.com/community= /XenProposed. I have succesfully done the migration from one machine in= to another. How ever I want to run this remus to support my server. I have = read=C2=A0http://remusha.wikidot.com/=C2=A0to configuring a= nd install remus.

= Could any body point me out what I should do? am I have to re-installed my = machine with supported kernel firstly (kernel 2.6.x) or something.

Thank you very much.

Regards,

Agya


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


--f46d043bdd64437fb904d584d296-- --===============1735499249342719722== 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 --===============1735499249342719722==-- From xen-users-bounces@lists.xen.org Tue Feb 12 10:53:21 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 12 Feb 2013 10:53: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 1U5DTX-0001je-5X; Tue, 12 Feb 2013 10:52:35 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U5DTV-0001jX-J9 for xen-users@lists.xen.org; Tue, 12 Feb 2013 10:52:33 +0000 Received: from [85.158.139.83:62933] by server-11.bemta-5.messagelabs.com id 04/B7-19159-0FE1A115; Tue, 12 Feb 2013 10:52:32 +0000 X-Env-Sender: herydians@gmail.com X-Msg-Ref: server-12.tower-182.messagelabs.com!1360666347!27493696!1 X-Originating-IP: [74.125.82.178] X-SpamReason: No, hits=0.9 required=7.0 tests=HTML_40_50,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14, ML_RADAR_SPEW_LINKS_23, RCVD_BY_IP, spamassassin: X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 28085 invoked from network); 12 Feb 2013 10:52:27 -0000 Received: from mail-we0-f178.google.com (HELO mail-we0-f178.google.com) (74.125.82.178) by server-12.tower-182.messagelabs.com with RC4-SHA encrypted SMTP; 12 Feb 2013 10:52:27 -0000 Received: by mail-we0-f178.google.com with SMTP id x48so5636629wey.37 for ; Tue, 12 Feb 2013 02:52:26 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:content-type; bh=YggVX9655Y8Yt8j39vZ+IqxLaKFqVyzMylVHcMzz0iU=; b=C2soDPCYeFTxw8zvz3RWWhmhHaxR+8JNN3XJVEALi5bjOqAz4r3LZr8HAnmX3GSkcC dz5/yxvwrlExjS7U0Olgcq+kV4wxE0s+GJn6sKtCncxtFuO3ddOM3iJRTGhIM1FI/NQN 00bSmbgE5ZYo/I6lmMPHHOnLnLnQP3A1MDo099wsaa22KWLaYS6aJSIjvEXTWfRnWNq2 LnQW3WsUD7oXbE4uLYWaAYDMhf5Qc0KduaoBixW7Xvxn2T5yYPClFS2pRGv0JUh5M7fF asKS1YdxvMB4f5GinYwgwXn9tg41WzxBJ8lbeQU/Vh7D0579/xvpyVoTMoEBWhVYPgnD JXyQ== MIME-Version: 1.0 X-Received: by 10.180.84.131 with SMTP id z3mr2232261wiy.25.1360666346880; Tue, 12 Feb 2013 02:52:26 -0800 (PST) Received: by 10.216.107.132 with HTTP; Tue, 12 Feb 2013 02:52:26 -0800 (PST) In-Reply-To: References: Date: Tue, 12 Feb 2013 11:52:26 +0100 Message-ID: From: Hery Dian Septama To: xen-users Subject: [Xen-users] Remus on Ubuntu 12.04 with XEN 4.1 AMD 64 X-BeenThere: xen-users@lists.xen.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="===============1735499249342719722==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============1735499249342719722== Content-Type: multipart/alternative; boundary=f46d043bdd64437fb904d584d296 --f46d043bdd64437fb904d584d296 Content-Type: text/plain; charset=UTF-8 Dear all, I am new in XEN and quite confusing with this remus installation. Could anyone point me out how to do it. I have Ubuntu 12.04 with kernel 3.2.0-29-generic 64 bit bot for Dom0 dan DomU with Para Virtualization. I have installed Xen4.1 AMD 64 bit by following this https://help.ubuntu.com/community/XenProposed. I have succesfully done the migration from one machine into another. How ever I want to run this remus to support my server. I have read http://remusha.wikidot.com/ to configuring and install remus. Could any body point me out what I should do? am I have to re-installed my machine with supported kernel firstly (kernel 2.6.x) or something. Thank you very much. Regards, Agya _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel --f46d043bdd64437fb904d584d296 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Dear all,

I am new in XEN and quite= confusing with this remus installation. Could anyone point me out how to d= o it.
I have Ubuntu 12.04 with kernel 3.2.0-29-generic 64 bit bot for Dom0 dan Do= mU with Para Virtualization. I have installed Xen4.1 AMD 64 bit by followin= g this=C2=A0https://help.ubuntu.com/community= /XenProposed. I have succesfully done the migration from one machine in= to another. How ever I want to run this remus to support my server. I have = read=C2=A0http://remusha.wikidot.com/=C2=A0to configuring a= nd install remus.

= Could any body point me out what I should do? am I have to re-installed my = machine with supported kernel firstly (kernel 2.6.x) or something.

Thank you very much.

Regards,

Agya


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


--f46d043bdd64437fb904d584d296-- --===============1735499249342719722== 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 --===============1735499249342719722==-- From xen-users-bounces@lists.xen.org Tue Feb 12 15:52:54 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 12 Feb 2013 15:52: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 1U5I8y-0000qk-6i; Tue, 12 Feb 2013 15:51:40 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U5I8w-0000qH-Hh; Tue, 12 Feb 2013 15:51:38 +0000 Received: from [85.158.139.83:4121] by server-8.bemta-5.messagelabs.com id 52/55-19075-9056A115; Tue, 12 Feb 2013 15:51:37 +0000 X-Env-Sender: Ian.Jackson@eu.citrix.com X-Msg-Ref: server-13.tower-182.messagelabs.com!1360684296!31115743!1 X-Originating-IP: [46.33.159.39] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNDYuMzMuMTU5LjM5ID0+IDIxOTY2\n X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 6379 invoked from network); 12 Feb 2013 15:51:37 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (46.33.159.39) by server-13.tower-182.messagelabs.com with RC4-SHA encrypted SMTP; 12 Feb 2013 15:51:37 -0000 X-IronPort-AV: E=Sophos;i="4.84,650,1355097600"; d="scan'208";a="1380433" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 12 Feb 2013 15:51:37 +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.297.1; Tue, 12 Feb 2013 15:51:36 +0000 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 1U5I8u-0008W7-HV; Tue, 12 Feb 2013 15:51:36 +0000 Received: from iwj by mariner.uk.xensource.com with local (Exim 4.72) (envelope-from ) id 1U5I8u-0004Rl-DU; Tue, 12 Feb 2013 15:51:36 +0000 From: Ian Jackson MIME-Version: 1.0 Message-ID: <20762.25864.314580.353107@mariner.uk.xensource.com> Date: Tue, 12 Feb 2013 15:51:36 +0000 To: Konrad Rzeszutek Wilk Newsgroups: chiark.mail.xen.devel In-Reply-To: References: <20121022135023.GU8912@reaktio.net> X-Mailer: VM 8.1.0 under 23.2.1 (i486-pc-linux-gnu) Cc: "xen-users@lists.xen.org" , "xen-devel@lists.xen.org" , "Fan, Huaxiang" Subject: Re: [Xen-users] [Xen-devel] e820_host 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 Konrad Rzeszutek Wilk writes ("Re: [Xen-devel] e820_host problems"): > On Wed, Oct 24, 2012 at 06:02:11AM +0000, Fan, Huaxiang wrote: > > Hi Pasi, > > > > Thanks for your reply. I've tried the latest table kernel 3.6.3. The situation is better, but still not perfect. > > When I assign 6144M to domu wcg ,the output of 'xl list' only indicates 5110M allocated for domu wcg. > > When I logon domu wcg, the totol memory is *limited within 3G*. I suspect the e820-map was wrong. > > It looks like there is a bug in the libxl when assembling the e820 map. This would be in e820_sanitize in libxl_x86.c I guess ? Konrad, are you looking into a fix ? Ian. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Tue Feb 12 15:52:54 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 12 Feb 2013 15:52: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 1U5I8y-0000qk-6i; Tue, 12 Feb 2013 15:51:40 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U5I8w-0000qH-Hh; Tue, 12 Feb 2013 15:51:38 +0000 Received: from [85.158.139.83:4121] by server-8.bemta-5.messagelabs.com id 52/55-19075-9056A115; Tue, 12 Feb 2013 15:51:37 +0000 X-Env-Sender: Ian.Jackson@eu.citrix.com X-Msg-Ref: server-13.tower-182.messagelabs.com!1360684296!31115743!1 X-Originating-IP: [46.33.159.39] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNDYuMzMuMTU5LjM5ID0+IDIxOTY2\n X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 6379 invoked from network); 12 Feb 2013 15:51:37 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (46.33.159.39) by server-13.tower-182.messagelabs.com with RC4-SHA encrypted SMTP; 12 Feb 2013 15:51:37 -0000 X-IronPort-AV: E=Sophos;i="4.84,650,1355097600"; d="scan'208";a="1380433" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 12 Feb 2013 15:51:37 +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.297.1; Tue, 12 Feb 2013 15:51:36 +0000 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 1U5I8u-0008W7-HV; Tue, 12 Feb 2013 15:51:36 +0000 Received: from iwj by mariner.uk.xensource.com with local (Exim 4.72) (envelope-from ) id 1U5I8u-0004Rl-DU; Tue, 12 Feb 2013 15:51:36 +0000 From: Ian Jackson MIME-Version: 1.0 Message-ID: <20762.25864.314580.353107@mariner.uk.xensource.com> Date: Tue, 12 Feb 2013 15:51:36 +0000 To: Konrad Rzeszutek Wilk Newsgroups: chiark.mail.xen.devel In-Reply-To: References: <20121022135023.GU8912@reaktio.net> X-Mailer: VM 8.1.0 under 23.2.1 (i486-pc-linux-gnu) Cc: "xen-users@lists.xen.org" , "xen-devel@lists.xen.org" , "Fan, Huaxiang" Subject: Re: [Xen-users] [Xen-devel] e820_host 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 Konrad Rzeszutek Wilk writes ("Re: [Xen-devel] e820_host problems"): > On Wed, Oct 24, 2012 at 06:02:11AM +0000, Fan, Huaxiang wrote: > > Hi Pasi, > > > > Thanks for your reply. I've tried the latest table kernel 3.6.3. The situation is better, but still not perfect. > > When I assign 6144M to domu wcg ,the output of 'xl list' only indicates 5110M allocated for domu wcg. > > When I logon domu wcg, the totol memory is *limited within 3G*. I suspect the e820-map was wrong. > > It looks like there is a bug in the libxl when assembling the e820 map. This would be in e820_sanitize in libxl_x86.c I guess ? Konrad, are you looking into a fix ? Ian. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Tue Feb 12 16:53:40 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 12 Feb 2013 16:53: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 1U5J5c-0002tf-MQ; Tue, 12 Feb 2013 16:52:16 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U5J5b-0002ta-1b for xen-users@lists.xen.org; Tue, 12 Feb 2013 16:52:15 +0000 Received: from [85.158.138.51:48005] by server-3.bemta-3.messagelabs.com id 21/92-31070-E337A115; Tue, 12 Feb 2013 16:52:14 +0000 X-Env-Sender: roger.pau@citrix.com X-Msg-Ref: server-7.tower-174.messagelabs.com!1360687933!18923496!1 X-Originating-IP: [46.33.159.39] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNDYuMzMuMTU5LjM5ID0+IDIxOTY2\n X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 595 invoked from network); 12 Feb 2013 16:52:13 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (46.33.159.39) by server-7.tower-174.messagelabs.com with RC4-SHA encrypted SMTP; 12 Feb 2013 16:52:13 -0000 X-IronPort-AV: E=Sophos;i="4.84,650,1355097600"; d="scan'208";a="1382552" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 12 Feb 2013 16:52:13 +0000 Received: from [192.168.1.30] (10.30.249.242) by LONPMAILMX01.citrite.net (10.30.203.162) with Microsoft SMTP Server id 8.3.297.1; Tue, 12 Feb 2013 16:52:12 +0000 Message-ID: <511A734D.2040707@citrix.com> Date: Tue, 12 Feb 2013 17:52:29 +0100 From: =?ISO-8859-1?Q?Roger_Pau_Monn=E9?= User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130107 Thunderbird/17.0.2 MIME-Version: 1.0 To: Yathindra References: <510DC655.5060205@cs.utah.edu> <510E3195.1010004@citrix.com> <510EA374.6060509@cs.utah.edu> <5110D7EC.8040608@citrix.com> <51113D59.7030003@cs.utah.edu> <51114B35.5050202@citrix.com> <5111C3B6.1070705@cs.utah.edu> In-Reply-To: <5111C3B6.1070705@cs.utah.edu> Cc: "xen-users@lists.xen.org" Subject: Re: [Xen-users] xen_blkbk times out before getting connected X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org > Sorry about top posting. I changed it to xvda1 and I still see the same > behavior. What kernel version are you using? Have you tried using a pre-packaged kernel from your distro? _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Tue Feb 12 16:53:40 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 12 Feb 2013 16:53: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 1U5J5c-0002tf-MQ; Tue, 12 Feb 2013 16:52:16 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U5J5b-0002ta-1b for xen-users@lists.xen.org; Tue, 12 Feb 2013 16:52:15 +0000 Received: from [85.158.138.51:48005] by server-3.bemta-3.messagelabs.com id 21/92-31070-E337A115; Tue, 12 Feb 2013 16:52:14 +0000 X-Env-Sender: roger.pau@citrix.com X-Msg-Ref: server-7.tower-174.messagelabs.com!1360687933!18923496!1 X-Originating-IP: [46.33.159.39] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNDYuMzMuMTU5LjM5ID0+IDIxOTY2\n X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 595 invoked from network); 12 Feb 2013 16:52:13 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (46.33.159.39) by server-7.tower-174.messagelabs.com with RC4-SHA encrypted SMTP; 12 Feb 2013 16:52:13 -0000 X-IronPort-AV: E=Sophos;i="4.84,650,1355097600"; d="scan'208";a="1382552" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 12 Feb 2013 16:52:13 +0000 Received: from [192.168.1.30] (10.30.249.242) by LONPMAILMX01.citrite.net (10.30.203.162) with Microsoft SMTP Server id 8.3.297.1; Tue, 12 Feb 2013 16:52:12 +0000 Message-ID: <511A734D.2040707@citrix.com> Date: Tue, 12 Feb 2013 17:52:29 +0100 From: =?ISO-8859-1?Q?Roger_Pau_Monn=E9?= User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130107 Thunderbird/17.0.2 MIME-Version: 1.0 To: Yathindra References: <510DC655.5060205@cs.utah.edu> <510E3195.1010004@citrix.com> <510EA374.6060509@cs.utah.edu> <5110D7EC.8040608@citrix.com> <51113D59.7030003@cs.utah.edu> <51114B35.5050202@citrix.com> <5111C3B6.1070705@cs.utah.edu> In-Reply-To: <5111C3B6.1070705@cs.utah.edu> Cc: "xen-users@lists.xen.org" Subject: Re: [Xen-users] xen_blkbk times out before getting connected X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org > Sorry about top posting. I changed it to xvda1 and I still see the same > behavior. What kernel version are you using? Have you tried using a pre-packaged kernel from your distro? _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Tue Feb 12 17:21:22 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 12 Feb 2013 17:21: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 1U5JWe-0003Wp-2z; Tue, 12 Feb 2013 17:20:12 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U5JWc-0003Wk-1Y for xen-users@lists.xen.org; Tue, 12 Feb 2013 17:20:10 +0000 Received: from [85.158.139.83:17053] by server-7.bemta-5.messagelabs.com id A3/A1-11121-9C97A115; Tue, 12 Feb 2013 17:20:09 +0000 X-Env-Sender: cdelorme@gmail.com X-Msg-Ref: server-11.tower-182.messagelabs.com!1360689600!21073273!1 X-Originating-IP: [209.85.212.48] 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.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 24667 invoked from network); 12 Feb 2013 17:20:02 -0000 Received: from mail-vb0-f48.google.com (HELO mail-vb0-f48.google.com) (209.85.212.48) by server-11.tower-182.messagelabs.com with RC4-SHA encrypted SMTP; 12 Feb 2013 17:20:02 -0000 Received: by mail-vb0-f48.google.com with SMTP id fc21so189726vbb.35 for ; Tue, 12 Feb 2013 09:20:00 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=5uhIDLEL5iX/RgN3MSiDGy8TKIcA1YUl+XGehYwDmqg=; b=Uh+sm46nrOJK5l9QPRUISyilTq7K4FwptAKVTJsfRh0xpOls6GzqZBdnY60ACxfH9d 8H4F5fiyvxLelgTEar/UmDj2wt3OuooOGDiFRnpfM6103pxokeR3LSfZ7qBAZzrIng/B O32X00X5Xb0Phm2A2tkDZn4gA+8nmVnrCESr/HD4TPgy/SW8fdevw2FgBrnfCqPoKx0v YYAiXAJNMzPGQ/tFQrIqglulxlWx2rkVD4N7V2HiFi+ZwyRa0z43vJBoWkHLQFHzCyYK k0SBpX9Fe44wmTWf8Fb8o7VKbkCQ7UiDOdUf7KqulOF1g+3tuQ0uP60dJYBaqdhWqx3Z rkPA== MIME-Version: 1.0 X-Received: by 10.52.19.65 with SMTP id c1mr21688985vde.36.1360689586794; Tue, 12 Feb 2013 09:19:46 -0800 (PST) Received: by 10.58.32.199 with HTTP; Tue, 12 Feb 2013 09:19:46 -0800 (PST) In-Reply-To: References: <1360274160.57405.YahooMailNeo@web172003.mail.ir2.yahoo.com> Date: Tue, 12 Feb 2013 12:19:46 -0500 Message-ID: From: Casey DeLorme To: Matthias Cc: "xen-users@lists.xen.org" , David TECHER Subject: Re: [Xen-users] ATI/AMDs atikmpag.sys BSOD while 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="===============4921913537783869731==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============4921913537783869731== Content-Type: multipart/alternative; boundary=bcaec5040b9a78712104d58a3b34 --bcaec5040b9a78712104d58a3b34 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On Tue, Feb 12, 2013 at 4:20 AM, Matthias < matthias.kannenberg@googlemail.com> wrote: > Hi and thank you both for your input. > > From what I can tell, the things you mentioned are pretty similar to > what i wrote in my summary in the initial mail. But it's interesting > that you both got different cards running with CCC. So the CCC might > be an actual issue of either vga- and mainboard combo or vendor > specific. May I ask what setup's you got, especially the vendors / > exact models of your HD6870. ? > > My card is an XFX Radeom HD 6870, the exact details on the box: Model No: HD-687A-ZD Part No: HD-687A-ZDFC HD 6870 900M 1GB DDR5 DUAL MINIDP HDMI DUAL DVI PCI-E My configuration is as follows: Debian Wheezy Dom0 x64 - Control OS & Base System Debian Wheezy DomU x64 - Web Development & DNS Server IPFire (Debian Squeeze) - Firewall/Router/Proxy Windows 7/8 x64 - Multimedia & Gaming VM I pass my graphics card to Windows, and with my latest configuration onboard wireless to my IPFire for in-box WAP. Dom0 sits behind the IPFire HVM and is protected by the same Firewall as the other machines. As this is a home setup I am not as concerned with internal security, but I do plenty of backups since the only real danger behind the firewall is myself. I use an uEFI boot loader, so at certain points I did modify Xen source since it did not see all my RAM otherwise. However I did not do anything with VGA BIOS. I have tested my card and configuration successfully on two sets of hardware. Set 1: MoBo: ASRock Z68 Extreme4 Gen3 CPU: Intel Core i7 2600 RAM: 12GB 1333Mhz Corsair XMS (2x2G 2x4G) SSD: 240GB OCZ Vertex 3 Set 2: MoBo: ASRock Z77 Extreme9 CPU: Intel Core i7 3770 RAM: 32GB 1600Mhz Corsair XMS (4x8GB) I have tested an ASRock Z68 Extreme7 Gen3, which failed to provide for my needs on several levels. It had an NF200 PCIe Bridge which did not support passthrough and sat behind most of the PCI Express slots leaving me with only one 8x for a Graphics Card. It also had a (multiple?) PLX PCI Bridge, which treated several entirely different devices as "functions" in BDF reference, and passing one of them to pciback hid four out 7 behind it, including my dual lan controller which created lots of confusion and trouble. > For the well-known fix for the atikmpaq.sys BSOD, at least in my > opinion you can ignore all the solutions posted which are not xen > related. I think the BSOD here is clearly xen related since at least > for my it only happens with the xl toolstack and not the xm one, with > the same domU. But if someone really got lucky with such a non-xen > fix, it would be interesting to see, too.. > I started my experiments on Xen after xm had been deprecated and since I was building new from source I never bothered trying it. From what I read the success stories were just as mixed as those using xl. I am not a specialist, just an enthusiast, so while I have performed tests they were not exactly professionally documented. After getting a successful install by accident once out of 5 attempts, I decided to run tests to narrow down the possible causes of my failed attempts. I freshly rebuilt Xen and installed Windows 80 times, changing the process each time to attempt to pin-point the cause of failure. My conclusion was as stated, anytime I attempted to install or upgrade the drivers and the physical system had not been freshly rebooted OR I had not ejected the card then one of several things would happen (these appeared to be entirely random consequences). I would encounter a BSoD during installation, sometimes with and sometimes without CCC (it appeared to occur less often if I de-selected CCC). I sometimes encountered a BSoD rebooting and every subsequent. Othertimes it almost worked but would BSoD over time, and this got worse (happened faster) as I continued to use the system. Another result was severe horizontal tearing on video playback, but the system would work normally otherwise even on reboots. My conclusion was pretty simple, and it has worked for me successfully on over 30 Windows installations (25 being test runs). I shared details about queer FLR issues in previous email chains, but many xen-users have reported entirely different problems or that my solution did not work for their configuration. So though I would like to imagine otherwise it is very possible that every card's make, model and vendor could behave differently. > Last but not least, can you say something about your setup? I would be > especially curious about if you do some vga bios stuff, like > extracting and including it into the xen build, and what kernel and > domU parameters you use, for example if iommu=3D1 or iomu=3Dsoft @ kernel > and stuff like pci_msitranslate=3D1 and pci_powermanagement in domU > config (and if the viridian=3D1 option does actually do anything).. > > I researched and tested setting the iommu kernel flag, but during all of my tests it never made any difference in the results so eventually I started omitting it. This is very different from the results others have gotten, and I haven't the foggiest why. If you google Xen Man Pages you'll find complete documentation of xl.cfg for VM Configurations, which includes descriptions for all the flags for virtual machines. The additional pci flags (global and otherwise) I tried but saw no visible differences in use or they caused brand new errors instead of solving anything so I also omitted them. I have the viridian flag on for Windows, as the Xen Man Pages describes it as potentially boosting Windows Vista and newer performance by enabling Hyper-V extensions. I do not know if this has had any real impact on my performance, as I also installed GPLPV drivers, if I have time I may perform some tests later. > There are a lot of vga passthrough tutorials lately, but from what > it's worth, in my opinion they all lack some detail because everyone > simply describes the setup he got working and there is no > comprehensive summary about the benefits of the different options. > > By the definition of the word detail I would disagree that many of the guides lack it, more that they are too detailed. I created a guide and just like you said I was very specific about my hardware. However that is because success with Xen is very hardware dependent. It would be extremely difficult to write a "catch-all" guide on passthrough that retained any usefulness if every card make/model/vendor not to mention every other part in a computer could behave even slightly differently. I also don't know anyone who has both the time and money to purchase and test all available combinations of similar equipment, but if vendors are interested in lending equipment I'd happily volunteer to test it. Not sure what you mean by different options, is that hardware options or the flags mentioned above? > It would be great if you can help with your experience. > > I hope this information is useful, and look forward to following further replies. > > > > 2013/2/7 Casey DeLorme : > > I have an HD 6870 and working CCC, tested on both Windows 7 and windows > 8. > > Don't have any BSoD's either. > > > > I only had problems with CCC and drivers when I attempted to install or > > update drivers without having freshly rebooted or ejected the card. > > > > Unfortunately Windows 8 attempts to auto-install the drivers at boot ti= me > > and this caused some headaches during my first go at it. > > > > I experience performance problems after rebooting the HVM, to fix it I > just > > eject the card from the "Safely Remove Hardware and Eject Media" icon. > > > > > > On Thu, Feb 7, 2013 at 4:56 PM, David TECHER > wrote: > >> > >> Issues for CCC depends on your Video Card too. > >> > >> - Got a HD 79070. It worked for me to add CCC while installing the 13.= 2 > >> beta driver. > >> > >> Unfortunately there was BSOD issue when rebooting the domU. > >> > >> I had to install .NET 4 Framework and CCC now works as expected := ) > >> > >> - CCC is not supposed to work for HD 6870 but it worked for HD 7970. > >> > >> FYI to fix atikmap.sys issue there is a well-known workaround with > >> something like > >> > >> > >> > http://www.computertipsfree.com/fix-43029-atikmdag-sys-blue-screen-bsod-i= n-windows-7/ > >> > >> expand -r atikmdag.sy_ atikmdag.sys > >> > >> But it doesn't work for me :( > >> > >> The good news is that I've just installed Crysis 3 beta demo. It works > >> like a charm! > >> > >> > >> ________________________________ > >> De : Matthias > >> =C3=80 : xen-users@lists.xen.org > >> Envoy=C3=A9 le : Jeudi 7 f=C3=A9vrier 2013 20h14 > >> Objet : [Xen-users] ATI/AMDs atikmpag.sys BSOD while vga passthrough > >> > >> Hi everyone > >> > >> since I'm currently migrating from xm to xl and now are also a victim > >> of the said error, I started researching on it and found that many > >> people had the issue but not many found solution and behind this BSOD > >> (=3DBluescreen of Death), there are actually multiple errors in hiding= . > >> > >> What I would like to do is gather as much info as possible in this > >> thread to form a kind of comprehensive guide to fixing this issue. > >> > >> From what i gathered so far, there are at least 3 different problems > >> with the same symptopms. > >> > >> 1) > >> Situation: After booting the dom0 and booting a windows domU with an > >> ATI/AMD Card, Windows generally works fine, but after rebooting the > >> system, or shutting down / restarting, the Bluescreen occurs or the > >> performance massively below normal. > >> Error: Most likely this is cause the Card is not properly resetted (no > >> FLR [function level reset] ) > >> Solution: If the domU reboots into BSOD, you are screwed and have to > >> reboot the dom0. If it only degrades performance, eject the card and > >> reinitialize to perform a manual reset. Or use the xm toolkit. > >> Status: Don't know if it is fixed yet > >> Source: > http://lists.xen.org/archives/html/xen-users/2012-02/msg00443.html > >> , http://wiki.xen.org/wiki/Talk:Xen_VGA_Passthrough_Tested_Adapters > >> > >> 2) > >> Situation: Booting a windows domU results in a BSOD when the CCC > >> (=3DCatalyst Control Center) installed. > >> Error: The CCC tries to set some specific settings (most likely > >> performance tweaks) within the driver which the driver can't pass to > >> the vga through passthrough mode. Result is a BSOD. > >> Solution: Deinstall the CCC in windows safe mode. The driver itself > >> works without it pretty fine. > >> Status: Don't know if it is fixed yet > >> Source: > http://lists.xen.org/archives/html/xen-users/2012-03/msg00617.html > >> Note: I don't really know if this holds for the Vision Engine Control > >> center, too. the VECC is basically the same as the CCC, so i assume it > >> does. I simply haven't found any things referencing it. > >> > >> 3) > >> Situation: This is actually the issue I have. Things seem a lot more > >> random then the other ones. A BSOD happens basically in 80% of booting > >> the Windows domU. Which means, after rebooting dom0, it mostly works. > >> Rebooting or shutting down / starting the domU works sometimes (Once i > >> achieved 6 consecutive reboots or shutdowns / starts before the BSOD > >> happened) but after I get one Bluescreen, almost never (I can't > >> exactly remember if really 'never') comes up again. Of course I tried > >> the above solutions but this didn't helped me. I also tried different > >> different versions of the Catalyst driver (from 12/1 to 13/1) and > >> current releases of xen-4.2-testing and xen-unsable. As I said, this > >> is when using the xl toolkit. I never had this issues using xm. > >> I thought this might belinked to me passing other PCI devices in > >> addition (I'm passing some USB controller to the domU) but even > >> deactivating them didn't help. What I actually found helping boosting > >> the success rate (but not solving the overall issue) is deinstalling > >> all VGA-Related AMD Driver. Windows then runs on it's own VGA-Driver > >> (the graphic card is currectly identified and this is an actual ati > >> driver, so I'm not talking about some generic standard vga driver. I > >> don't know where is driver is coming from). > >> I've attached an analysis file i've gethered from the bluescreen crash > >> dump. I created it using BluescreenView. This is more for currectly > >> identifieng the different BSODs, I guess. > >> > >> > >> Some Infos: > >> Kernel: 3.7.4 kernel.org kernel without patches > >> Xen: latest xen-unstable (but also tested with xen-4.2-testing) > >> Processor: AMD Phenom 1090T > >> Mainboard: Asus Crossfire IV > >> VGA: Radeon HD5700 and Radeon HD5450 > >> Driver: Currently running Catalyst 13/1 but tested nearly everything > >> between 12/1 and 13/1 > >> > >> Error: Don't know yet > >> Solution: Don't know yet > >> Status: unsolved > >> Source: > >> > >> > >> Okay, so basically that's the story. It would be great if some people > >> can complete and extend the list. Especially some who already fixed > >> the issue on their side. (And of course it would be great if someone > >> has an idea for my problem). > >> > >> Thanks > >> > >> _______________________________________________ > >> 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 > > > > > --bcaec5040b9a78712104d58a3b34 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
On Tue, Feb 12, 2013 at 4:20 AM, Matthias <matthias.kannenberg@googlemail.com> wrote:
Hi and thank you both for your = input.

>From what I can tell, the things you mentioned are pretty similar to
what i wrote in my summary in the initial mail. But it's interesting that you both got different cards running with CCC. So the CCC might
be an actual issue of either vga- and mainboard combo or vendor
specific. May I ask what setup's you got, especially the vendors /
exact models of your HD6870. ?


My card is an XFX Radeom HD 6870,= the exact details on the box:

Model No: HD-687A-Z= D
Part No: HD-687A-ZDFC
HD 6870 900M 1GB DDR5 DUAL MINI= DP HDMI DUAL DVI PCI-E


My configuration is as follows:

Debian Wheezy Dom0 x64 - Control OS & Base System
Debian Wheezy DomU x64 - Web Development & DNS Server
IPFire (Debian Squeeze) - Firewall/Router/Proxy
Windows 7/8 x64 -= Multimedia & Gaming VM

I pass my graphics car= d to Windows, and with my latest configuration onboard wireless to my IPFir= e for in-box WAP. =C2=A0Dom0 sits behind the IPFire HVM and is protected by= the same Firewall as the other machines. =C2=A0As this is a home setup I a= m not as concerned with internal security, but I do plenty of backups since= the only real danger behind the firewall is myself. =C2=A0I use an uEFI bo= ot loader, so at certain points I did modify Xen source since it did not se= e all my RAM otherwise. =C2=A0However I did not do anything with VGA BIOS.<= /div>


I have tested my card and configuration = successfully on two sets of hardware.

Set 1:
=

MoBo: ASRock Z68 Extreme4 Gen3
CPU: Intel Cor= e i7 2600
RAM: 12GB 1333Mhz Corsair XMS (2x2G 2x4G)
SSD: 240GB OCZ Ver= tex 3


Set 2:

MoBo: ASRock Z77 Extreme9
CPU: Intel Core i7 3770
RAM: 32GB 1600Mhz Corsair XMS (4x8GB)


I have tested an ASRock Z68 Extreme7 Gen3, which failed to provide for m= y needs on several levels. =C2=A0It had an NF200 PCIe Bridge which did not = support passthrough and sat behind most of the PCI Express slots leaving me= with only one 8x for a Graphics Card. =C2=A0It also had a (multiple?) PLX = PCI Bridge, which treated several entirely different devices as "funct= ions" in BDF reference, and passing one of them to pciback hid four ou= t 7 behind it, including my dual lan controller which created lots of confu= sion and trouble.
=C2=A0
For the well-known fix for the atikmpaq.sys BSOD, at least in my
opinion you can ignore all the solutions posted which are not xen
related. I think the BSOD here is clearly xen related since at least
for my it only happens with the xl toolstack and not the xm one, with
the same domU. But if someone really got lucky with such a non-xen
fix, it would be interesting to see, too..

I started my experiments on Xen after xm had been deprecated and s= ince I was building new from source I never bothered trying it. =C2=A0From = what I read the success stories were just as mixed as those using xl.

I am not a specialist, just an enthusiast, so while I h= ave performed tests they were not exactly professionally documented. =C2=A0= After getting a successful install by accident once out of 5 attempts, I de= cided to run tests to narrow down the possible causes of my failed attempts= . =C2=A0I freshly rebuilt Xen and installed Windows 80 times, changing the = process each time to attempt to pin-point the cause of failure. =C2=A0My co= nclusion was as stated, anytime I attempted to install or upgrade the drive= rs and the physical system had not been freshly rebooted OR I had not eject= ed the card then one of several things would happen (these appeared to be e= ntirely random consequences). =C2=A0I would encounter a BSoD during install= ation, sometimes with and sometimes without CCC (it appeared to occur less = often if I de-selected CCC). =C2=A0I sometimes encountered a BSoD rebooting= and every subsequent. =C2=A0Othertimes it almost worked but would BSoD ove= r time, and this got worse (happened faster) as I continued to use the syst= em. =C2=A0Another result was severe horizontal tearing on video playback, b= ut the system would work normally otherwise even on reboots.

My conclusion was pretty simple, and it has worke= d for me successfully on over 30 Windows installations (25 being test runs)= . =C2=A0I shared details about queer FLR issues in previous email chains, b= ut many xen-users have reported entirely different problems or that my solu= tion did not work for their configuration. =C2=A0So though I would like to = imagine otherwise it is very possible that every card's make, model and= vendor could behave differently.
=C2=A0
Last but not least, can you say something about your setup? I would be
especially curious about if you do some vga bios stuff, like
extracting and including it into the xen build, and what kernel and
domU parameters you use, for example if iommu=3D1 or iomu=3Dsoft @ kernel and stuff like pci_msitranslate=3D1 and pci_powermanagement in domU
config (and if the viridian=3D1 option does actually do anything)..


I researched and tested setting t= he iommu kernel flag, but during all of my tests it never made any differen= ce in the results so eventually I started omitting it. =C2=A0This is very d= ifferent from the results others have gotten, and I haven't the foggies= t why.

If you google Xen Man Pages you'll find complete do= cumentation of xl.cfg for VM Configurations, which includes descriptions fo= r all the flags for virtual machines.

The addition= al pci flags (global and otherwise) I tried but saw no visible differences = in use or they caused brand new errors instead of solving anything so I als= o omitted them.

I have the viridian flag on for Windows, as the Xen Man= Pages describes it as potentially boosting Windows Vista and newer perform= ance by enabling Hyper-V extensions. =C2=A0I do not know if this has had an= y real impact on my performance, as I also installed GPLPV drivers, if I ha= ve time I may perform some tests later.
=C2=A0
There are a lot of vga passthrough tutorials lately, but from what
it's worth, in my opinion they all lack some detail because everyone simply describes the setup he got working and there is no
comprehensive summary about the benefits of the different options.


By the definition of the word detail I= would disagree that many of the guides lack it, more that they are too det= ailed. =C2=A0I created a guide and just like you said I was very specific a= bout my hardware. =C2=A0However that is because success with Xen is very ha= rdware dependent. =C2=A0It would be extremely difficult to write a "ca= tch-all" guide on passthrough that retained any usefulness if every ca= rd make/model/vendor not to mention every other part in a computer could be= have even slightly differently.

I also don't know anyone who has both the time and = money to purchase and test all available combinations of similar equipment,= but if vendors are interested in lending equipment I'd happily volunte= er to test it.

Not sure what you mean by different options, is that ha= rdware options or the flags mentioned above?
=C2=A0
It would be great if you can help with your experience.


I hope this information is useful, and= look forward to following further replies.
=C2=A0



2013/2/7 Casey DeLorme <cdelorme@g= mail.com>:
> I have an HD 6870 and working CCC, t= ested on both Windows 7 and windows 8.
> Don't have any BSoD's either.
>
> I only had problems with CCC and drivers when I attempted to install o= r
> update drivers without having freshly rebooted or ejected the card. >
> Unfortunately Windows 8 attempts to auto-install the drivers at boot t= ime
> and this caused some headaches during my first go at it.
>
> I experience performance problems after rebooting the HVM, to fix it I= just
> eject the card from the "Safely Remove Hardware and Eject Media&q= uot; icon.
>
>
> On Thu, Feb 7, 2013 at 4:56 PM, David TECHER <davidtecher@yahoo.fr> wrote:
>>
>> Issues for CCC depends on your Video Card too.
>>
>> - Got a HD 79070. It worked for me to add CCC while installing the= 13.2
>> beta driver.
>>
>> =C2=A0 =C2=A0 =C2=A0 Unfortunately there was =C2=A0BSOD issue when= rebooting the domU.
>>
>> =C2=A0 =C2=A0 =C2=A0I had to install .NET 4 Framework and CCC now = works as expected :)
>>
>> - CCC is not supposed to work for HD 6870 but it worked for HD 797= 0.
>>
>> FYI to fix atikmap.sys issue there is a well-known workaround with=
>> something like
>>
>>
>> http://www.computertipsfr= ee.com/fix-43029-atikmdag-sys-blue-screen-bsod-in-windows-7/
>>
>> expand -r atikmdag.sy_ atikmdag.sys
>>
>> But it doesn't work for me :(
>>
>> The good news is that I've just installed Crysis 3 beta demo. = It works
>> like a charm!
>>
>>
>> ________________________________
>> De : Matthias <matthias.kannenberg@googlemail.com>
>> =C3=80 : xen-users@list= s.xen.org
>> Envoy=C3=A9 le : Jeudi 7 f=C3=A9vrier 2013 20h14
>> Objet : [Xen-users] ATI/AMDs atikmpag.sys BSOD while vga passthrou= gh
>>
>> Hi everyone
>>
>> since I'm currently migrating from xm to xl and now are also a= victim
>> of the said error, I started researching on it and found that many=
>> people had the issue but not many found solution and behind this B= SOD
>> (=3DBluescreen of Death), there are actually multiple errors in hi= ding.
>>
>> What I would like to do is gather as much info as possible in this=
>> thread to form a kind of comprehensive guide to fixing this issue.=
>>
>> From what i gathered so far, there are at least 3 different proble= ms
>> with the same symptopms.
>>
>> 1)
>> Situation: After booting the dom0 and booting a windows domU with = an
>> ATI/AMD Card, Windows generally works fine, but after rebooting th= e
>> system, or shutting down / restarting, the Bluescreen occurs or th= e
>> performance massively below normal.
>> Error: Most likely this is cause the Card is not properly resetted= (no
>> FLR [function level reset] )
>> Solution: If the domU reboots into BSOD, you are screwed and have = to
>> reboot the dom0. If it only degrades performance, eject the card a= nd
>> reinitialize to perform a manual reset. Or use the xm toolkit.
>> Status: Don't know if it is fixed yet
>> Source: http://lists.xen.org/archives/html/x= en-users/2012-02/msg00443.html
>> , http://wiki.xen.org/wiki/Talk:Xen_VGA_Passt= hrough_Tested_Adapters
>>
>> 2)
>> Situation: Booting a windows domU results in a BSOD when the CCC >> (=3DCatalyst Control Center) installed.
>> Error: The CCC tries to set some specific settings (most likely >> performance tweaks) within the driver which the driver can't p= ass to
>> the vga through passthrough mode. Result is a BSOD.
>> Solution: Deinstall the CCC in windows safe mode. The driver itsel= f
>> works without it pretty fine.
>> Status: Don't know if it is fixed yet
>> Source: http://lists.xen.org/archives/html/x= en-users/2012-03/msg00617.html
>> Note: I don't really know if this holds for the Vision Engine = Control
>> center, too. the VECC is basically the same as the CCC, so i assum= e it
>> does. I simply haven't found any things referencing it.
>>
>> 3)
>> Situation: This is actually the issue I have. Things seem a lot mo= re
>> random then the other ones. A BSOD happens basically in 80% of boo= ting
>> the Windows domU. Which means, after rebooting dom0, it mostly wor= ks.
>> Rebooting or shutting down / starting the domU works sometimes (On= ce i
>> achieved 6 consecutive reboots or shutdowns / starts before the BS= OD
>> happened) but after I get one Bluescreen, almost never (I can'= t
>> exactly remember if really 'never') comes up again. Of cou= rse I tried
>> the above solutions but this didn't helped me. I also tried di= fferent
>> different versions of the Catalyst driver (from 12/1 to 13/1) and<= br> >> current releases of xen-4.2-testing and xen-unsable. As I said, th= is
>> is when using the xl toolkit. I never had this issues using xm. >> I thought this might belinked to me passing other PCI devices in >> addition (I'm passing some USB controller to the domU) but eve= n
>> deactivating them didn't help. What I actually found helping b= oosting
>> the success rate (but not solving the overall issue) is deinstalli= ng
>> all VGA-Related AMD Driver. Windows then runs on it's own VGA-= Driver
>> (the graphic card is currectly identified and this is an actual at= i
>> driver, so I'm not talking about some generic standard vga dri= ver. I
>> don't know where is driver is coming from).
>> I've attached an analysis file i've gethered from the blue= screen crash
>> dump. I created it using BluescreenView. This is more for currectl= y
>> identifieng the different BSODs, I guess.
>>
>>
>> Some Infos:
>> Kernel: 3.7.4 kern= el.org kernel without patches
>> Xen: latest xen-unstable (but also tested with xen-4.2-testing) >> Processor: AMD Phenom 1090T
>> Mainboard: Asus Crossfire IV
>> VGA: Radeon HD5700 and Radeon HD5450
>> Driver: Currently running Catalyst 13/1 but tested nearly everythi= ng
>> between 12/1 and 13/1
>>
>> Error: Don't know yet
>> Solution: Don't know yet
>> Status: unsolved
>> Source:
>>
>>
>> Okay, so basically that's the story. It would be great if some= people
>> can complete and extend the list. Especially some who already fixe= d
>> the issue on their side. (And of course it would be great if someo= ne
>> has an idea for my problem).
>>
>> Thanks
>>
>> _______________________________________________
>> 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
>
>

--bcaec5040b9a78712104d58a3b34-- --===============4921913537783869731== 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 --===============4921913537783869731==-- From xen-users-bounces@lists.xen.org Tue Feb 12 17:21:22 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 12 Feb 2013 17:21: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 1U5JWe-0003Wp-2z; Tue, 12 Feb 2013 17:20:12 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U5JWc-0003Wk-1Y for xen-users@lists.xen.org; Tue, 12 Feb 2013 17:20:10 +0000 Received: from [85.158.139.83:17053] by server-7.bemta-5.messagelabs.com id A3/A1-11121-9C97A115; Tue, 12 Feb 2013 17:20:09 +0000 X-Env-Sender: cdelorme@gmail.com X-Msg-Ref: server-11.tower-182.messagelabs.com!1360689600!21073273!1 X-Originating-IP: [209.85.212.48] 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.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 24667 invoked from network); 12 Feb 2013 17:20:02 -0000 Received: from mail-vb0-f48.google.com (HELO mail-vb0-f48.google.com) (209.85.212.48) by server-11.tower-182.messagelabs.com with RC4-SHA encrypted SMTP; 12 Feb 2013 17:20:02 -0000 Received: by mail-vb0-f48.google.com with SMTP id fc21so189726vbb.35 for ; Tue, 12 Feb 2013 09:20:00 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=5uhIDLEL5iX/RgN3MSiDGy8TKIcA1YUl+XGehYwDmqg=; b=Uh+sm46nrOJK5l9QPRUISyilTq7K4FwptAKVTJsfRh0xpOls6GzqZBdnY60ACxfH9d 8H4F5fiyvxLelgTEar/UmDj2wt3OuooOGDiFRnpfM6103pxokeR3LSfZ7qBAZzrIng/B O32X00X5Xb0Phm2A2tkDZn4gA+8nmVnrCESr/HD4TPgy/SW8fdevw2FgBrnfCqPoKx0v YYAiXAJNMzPGQ/tFQrIqglulxlWx2rkVD4N7V2HiFi+ZwyRa0z43vJBoWkHLQFHzCyYK k0SBpX9Fe44wmTWf8Fb8o7VKbkCQ7UiDOdUf7KqulOF1g+3tuQ0uP60dJYBaqdhWqx3Z rkPA== MIME-Version: 1.0 X-Received: by 10.52.19.65 with SMTP id c1mr21688985vde.36.1360689586794; Tue, 12 Feb 2013 09:19:46 -0800 (PST) Received: by 10.58.32.199 with HTTP; Tue, 12 Feb 2013 09:19:46 -0800 (PST) In-Reply-To: References: <1360274160.57405.YahooMailNeo@web172003.mail.ir2.yahoo.com> Date: Tue, 12 Feb 2013 12:19:46 -0500 Message-ID: From: Casey DeLorme To: Matthias Cc: "xen-users@lists.xen.org" , David TECHER Subject: Re: [Xen-users] ATI/AMDs atikmpag.sys BSOD while 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="===============4921913537783869731==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============4921913537783869731== Content-Type: multipart/alternative; boundary=bcaec5040b9a78712104d58a3b34 --bcaec5040b9a78712104d58a3b34 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On Tue, Feb 12, 2013 at 4:20 AM, Matthias < matthias.kannenberg@googlemail.com> wrote: > Hi and thank you both for your input. > > From what I can tell, the things you mentioned are pretty similar to > what i wrote in my summary in the initial mail. But it's interesting > that you both got different cards running with CCC. So the CCC might > be an actual issue of either vga- and mainboard combo or vendor > specific. May I ask what setup's you got, especially the vendors / > exact models of your HD6870. ? > > My card is an XFX Radeom HD 6870, the exact details on the box: Model No: HD-687A-ZD Part No: HD-687A-ZDFC HD 6870 900M 1GB DDR5 DUAL MINIDP HDMI DUAL DVI PCI-E My configuration is as follows: Debian Wheezy Dom0 x64 - Control OS & Base System Debian Wheezy DomU x64 - Web Development & DNS Server IPFire (Debian Squeeze) - Firewall/Router/Proxy Windows 7/8 x64 - Multimedia & Gaming VM I pass my graphics card to Windows, and with my latest configuration onboard wireless to my IPFire for in-box WAP. Dom0 sits behind the IPFire HVM and is protected by the same Firewall as the other machines. As this is a home setup I am not as concerned with internal security, but I do plenty of backups since the only real danger behind the firewall is myself. I use an uEFI boot loader, so at certain points I did modify Xen source since it did not see all my RAM otherwise. However I did not do anything with VGA BIOS. I have tested my card and configuration successfully on two sets of hardware. Set 1: MoBo: ASRock Z68 Extreme4 Gen3 CPU: Intel Core i7 2600 RAM: 12GB 1333Mhz Corsair XMS (2x2G 2x4G) SSD: 240GB OCZ Vertex 3 Set 2: MoBo: ASRock Z77 Extreme9 CPU: Intel Core i7 3770 RAM: 32GB 1600Mhz Corsair XMS (4x8GB) I have tested an ASRock Z68 Extreme7 Gen3, which failed to provide for my needs on several levels. It had an NF200 PCIe Bridge which did not support passthrough and sat behind most of the PCI Express slots leaving me with only one 8x for a Graphics Card. It also had a (multiple?) PLX PCI Bridge, which treated several entirely different devices as "functions" in BDF reference, and passing one of them to pciback hid four out 7 behind it, including my dual lan controller which created lots of confusion and trouble. > For the well-known fix for the atikmpaq.sys BSOD, at least in my > opinion you can ignore all the solutions posted which are not xen > related. I think the BSOD here is clearly xen related since at least > for my it only happens with the xl toolstack and not the xm one, with > the same domU. But if someone really got lucky with such a non-xen > fix, it would be interesting to see, too.. > I started my experiments on Xen after xm had been deprecated and since I was building new from source I never bothered trying it. From what I read the success stories were just as mixed as those using xl. I am not a specialist, just an enthusiast, so while I have performed tests they were not exactly professionally documented. After getting a successful install by accident once out of 5 attempts, I decided to run tests to narrow down the possible causes of my failed attempts. I freshly rebuilt Xen and installed Windows 80 times, changing the process each time to attempt to pin-point the cause of failure. My conclusion was as stated, anytime I attempted to install or upgrade the drivers and the physical system had not been freshly rebooted OR I had not ejected the card then one of several things would happen (these appeared to be entirely random consequences). I would encounter a BSoD during installation, sometimes with and sometimes without CCC (it appeared to occur less often if I de-selected CCC). I sometimes encountered a BSoD rebooting and every subsequent. Othertimes it almost worked but would BSoD over time, and this got worse (happened faster) as I continued to use the system. Another result was severe horizontal tearing on video playback, but the system would work normally otherwise even on reboots. My conclusion was pretty simple, and it has worked for me successfully on over 30 Windows installations (25 being test runs). I shared details about queer FLR issues in previous email chains, but many xen-users have reported entirely different problems or that my solution did not work for their configuration. So though I would like to imagine otherwise it is very possible that every card's make, model and vendor could behave differently. > Last but not least, can you say something about your setup? I would be > especially curious about if you do some vga bios stuff, like > extracting and including it into the xen build, and what kernel and > domU parameters you use, for example if iommu=3D1 or iomu=3Dsoft @ kernel > and stuff like pci_msitranslate=3D1 and pci_powermanagement in domU > config (and if the viridian=3D1 option does actually do anything).. > > I researched and tested setting the iommu kernel flag, but during all of my tests it never made any difference in the results so eventually I started omitting it. This is very different from the results others have gotten, and I haven't the foggiest why. If you google Xen Man Pages you'll find complete documentation of xl.cfg for VM Configurations, which includes descriptions for all the flags for virtual machines. The additional pci flags (global and otherwise) I tried but saw no visible differences in use or they caused brand new errors instead of solving anything so I also omitted them. I have the viridian flag on for Windows, as the Xen Man Pages describes it as potentially boosting Windows Vista and newer performance by enabling Hyper-V extensions. I do not know if this has had any real impact on my performance, as I also installed GPLPV drivers, if I have time I may perform some tests later. > There are a lot of vga passthrough tutorials lately, but from what > it's worth, in my opinion they all lack some detail because everyone > simply describes the setup he got working and there is no > comprehensive summary about the benefits of the different options. > > By the definition of the word detail I would disagree that many of the guides lack it, more that they are too detailed. I created a guide and just like you said I was very specific about my hardware. However that is because success with Xen is very hardware dependent. It would be extremely difficult to write a "catch-all" guide on passthrough that retained any usefulness if every card make/model/vendor not to mention every other part in a computer could behave even slightly differently. I also don't know anyone who has both the time and money to purchase and test all available combinations of similar equipment, but if vendors are interested in lending equipment I'd happily volunteer to test it. Not sure what you mean by different options, is that hardware options or the flags mentioned above? > It would be great if you can help with your experience. > > I hope this information is useful, and look forward to following further replies. > > > > 2013/2/7 Casey DeLorme : > > I have an HD 6870 and working CCC, tested on both Windows 7 and windows > 8. > > Don't have any BSoD's either. > > > > I only had problems with CCC and drivers when I attempted to install or > > update drivers without having freshly rebooted or ejected the card. > > > > Unfortunately Windows 8 attempts to auto-install the drivers at boot ti= me > > and this caused some headaches during my first go at it. > > > > I experience performance problems after rebooting the HVM, to fix it I > just > > eject the card from the "Safely Remove Hardware and Eject Media" icon. > > > > > > On Thu, Feb 7, 2013 at 4:56 PM, David TECHER > wrote: > >> > >> Issues for CCC depends on your Video Card too. > >> > >> - Got a HD 79070. It worked for me to add CCC while installing the 13.= 2 > >> beta driver. > >> > >> Unfortunately there was BSOD issue when rebooting the domU. > >> > >> I had to install .NET 4 Framework and CCC now works as expected := ) > >> > >> - CCC is not supposed to work for HD 6870 but it worked for HD 7970. > >> > >> FYI to fix atikmap.sys issue there is a well-known workaround with > >> something like > >> > >> > >> > http://www.computertipsfree.com/fix-43029-atikmdag-sys-blue-screen-bsod-i= n-windows-7/ > >> > >> expand -r atikmdag.sy_ atikmdag.sys > >> > >> But it doesn't work for me :( > >> > >> The good news is that I've just installed Crysis 3 beta demo. It works > >> like a charm! > >> > >> > >> ________________________________ > >> De : Matthias > >> =C3=80 : xen-users@lists.xen.org > >> Envoy=C3=A9 le : Jeudi 7 f=C3=A9vrier 2013 20h14 > >> Objet : [Xen-users] ATI/AMDs atikmpag.sys BSOD while vga passthrough > >> > >> Hi everyone > >> > >> since I'm currently migrating from xm to xl and now are also a victim > >> of the said error, I started researching on it and found that many > >> people had the issue but not many found solution and behind this BSOD > >> (=3DBluescreen of Death), there are actually multiple errors in hiding= . > >> > >> What I would like to do is gather as much info as possible in this > >> thread to form a kind of comprehensive guide to fixing this issue. > >> > >> From what i gathered so far, there are at least 3 different problems > >> with the same symptopms. > >> > >> 1) > >> Situation: After booting the dom0 and booting a windows domU with an > >> ATI/AMD Card, Windows generally works fine, but after rebooting the > >> system, or shutting down / restarting, the Bluescreen occurs or the > >> performance massively below normal. > >> Error: Most likely this is cause the Card is not properly resetted (no > >> FLR [function level reset] ) > >> Solution: If the domU reboots into BSOD, you are screwed and have to > >> reboot the dom0. If it only degrades performance, eject the card and > >> reinitialize to perform a manual reset. Or use the xm toolkit. > >> Status: Don't know if it is fixed yet > >> Source: > http://lists.xen.org/archives/html/xen-users/2012-02/msg00443.html > >> , http://wiki.xen.org/wiki/Talk:Xen_VGA_Passthrough_Tested_Adapters > >> > >> 2) > >> Situation: Booting a windows domU results in a BSOD when the CCC > >> (=3DCatalyst Control Center) installed. > >> Error: The CCC tries to set some specific settings (most likely > >> performance tweaks) within the driver which the driver can't pass to > >> the vga through passthrough mode. Result is a BSOD. > >> Solution: Deinstall the CCC in windows safe mode. The driver itself > >> works without it pretty fine. > >> Status: Don't know if it is fixed yet > >> Source: > http://lists.xen.org/archives/html/xen-users/2012-03/msg00617.html > >> Note: I don't really know if this holds for the Vision Engine Control > >> center, too. the VECC is basically the same as the CCC, so i assume it > >> does. I simply haven't found any things referencing it. > >> > >> 3) > >> Situation: This is actually the issue I have. Things seem a lot more > >> random then the other ones. A BSOD happens basically in 80% of booting > >> the Windows domU. Which means, after rebooting dom0, it mostly works. > >> Rebooting or shutting down / starting the domU works sometimes (Once i > >> achieved 6 consecutive reboots or shutdowns / starts before the BSOD > >> happened) but after I get one Bluescreen, almost never (I can't > >> exactly remember if really 'never') comes up again. Of course I tried > >> the above solutions but this didn't helped me. I also tried different > >> different versions of the Catalyst driver (from 12/1 to 13/1) and > >> current releases of xen-4.2-testing and xen-unsable. As I said, this > >> is when using the xl toolkit. I never had this issues using xm. > >> I thought this might belinked to me passing other PCI devices in > >> addition (I'm passing some USB controller to the domU) but even > >> deactivating them didn't help. What I actually found helping boosting > >> the success rate (but not solving the overall issue) is deinstalling > >> all VGA-Related AMD Driver. Windows then runs on it's own VGA-Driver > >> (the graphic card is currectly identified and this is an actual ati > >> driver, so I'm not talking about some generic standard vga driver. I > >> don't know where is driver is coming from). > >> I've attached an analysis file i've gethered from the bluescreen crash > >> dump. I created it using BluescreenView. This is more for currectly > >> identifieng the different BSODs, I guess. > >> > >> > >> Some Infos: > >> Kernel: 3.7.4 kernel.org kernel without patches > >> Xen: latest xen-unstable (but also tested with xen-4.2-testing) > >> Processor: AMD Phenom 1090T > >> Mainboard: Asus Crossfire IV > >> VGA: Radeon HD5700 and Radeon HD5450 > >> Driver: Currently running Catalyst 13/1 but tested nearly everything > >> between 12/1 and 13/1 > >> > >> Error: Don't know yet > >> Solution: Don't know yet > >> Status: unsolved > >> Source: > >> > >> > >> Okay, so basically that's the story. It would be great if some people > >> can complete and extend the list. Especially some who already fixed > >> the issue on their side. (And of course it would be great if someone > >> has an idea for my problem). > >> > >> Thanks > >> > >> _______________________________________________ > >> 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 > > > > > --bcaec5040b9a78712104d58a3b34 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
On Tue, Feb 12, 2013 at 4:20 AM, Matthias <matthias.kannenberg@googlemail.com> wrote:
Hi and thank you both for your = input.

>From what I can tell, the things you mentioned are pretty similar to
what i wrote in my summary in the initial mail. But it's interesting that you both got different cards running with CCC. So the CCC might
be an actual issue of either vga- and mainboard combo or vendor
specific. May I ask what setup's you got, especially the vendors /
exact models of your HD6870. ?


My card is an XFX Radeom HD 6870,= the exact details on the box:

Model No: HD-687A-Z= D
Part No: HD-687A-ZDFC
HD 6870 900M 1GB DDR5 DUAL MINI= DP HDMI DUAL DVI PCI-E


My configuration is as follows:

Debian Wheezy Dom0 x64 - Control OS & Base System
Debian Wheezy DomU x64 - Web Development & DNS Server
IPFire (Debian Squeeze) - Firewall/Router/Proxy
Windows 7/8 x64 -= Multimedia & Gaming VM

I pass my graphics car= d to Windows, and with my latest configuration onboard wireless to my IPFir= e for in-box WAP. =C2=A0Dom0 sits behind the IPFire HVM and is protected by= the same Firewall as the other machines. =C2=A0As this is a home setup I a= m not as concerned with internal security, but I do plenty of backups since= the only real danger behind the firewall is myself. =C2=A0I use an uEFI bo= ot loader, so at certain points I did modify Xen source since it did not se= e all my RAM otherwise. =C2=A0However I did not do anything with VGA BIOS.<= /div>


I have tested my card and configuration = successfully on two sets of hardware.

Set 1:
=

MoBo: ASRock Z68 Extreme4 Gen3
CPU: Intel Cor= e i7 2600
RAM: 12GB 1333Mhz Corsair XMS (2x2G 2x4G)
SSD: 240GB OCZ Ver= tex 3


Set 2:

MoBo: ASRock Z77 Extreme9
CPU: Intel Core i7 3770
RAM: 32GB 1600Mhz Corsair XMS (4x8GB)


I have tested an ASRock Z68 Extreme7 Gen3, which failed to provide for m= y needs on several levels. =C2=A0It had an NF200 PCIe Bridge which did not = support passthrough and sat behind most of the PCI Express slots leaving me= with only one 8x for a Graphics Card. =C2=A0It also had a (multiple?) PLX = PCI Bridge, which treated several entirely different devices as "funct= ions" in BDF reference, and passing one of them to pciback hid four ou= t 7 behind it, including my dual lan controller which created lots of confu= sion and trouble.
=C2=A0
For the well-known fix for the atikmpaq.sys BSOD, at least in my
opinion you can ignore all the solutions posted which are not xen
related. I think the BSOD here is clearly xen related since at least
for my it only happens with the xl toolstack and not the xm one, with
the same domU. But if someone really got lucky with such a non-xen
fix, it would be interesting to see, too..

I started my experiments on Xen after xm had been deprecated and s= ince I was building new from source I never bothered trying it. =C2=A0From = what I read the success stories were just as mixed as those using xl.

I am not a specialist, just an enthusiast, so while I h= ave performed tests they were not exactly professionally documented. =C2=A0= After getting a successful install by accident once out of 5 attempts, I de= cided to run tests to narrow down the possible causes of my failed attempts= . =C2=A0I freshly rebuilt Xen and installed Windows 80 times, changing the = process each time to attempt to pin-point the cause of failure. =C2=A0My co= nclusion was as stated, anytime I attempted to install or upgrade the drive= rs and the physical system had not been freshly rebooted OR I had not eject= ed the card then one of several things would happen (these appeared to be e= ntirely random consequences). =C2=A0I would encounter a BSoD during install= ation, sometimes with and sometimes without CCC (it appeared to occur less = often if I de-selected CCC). =C2=A0I sometimes encountered a BSoD rebooting= and every subsequent. =C2=A0Othertimes it almost worked but would BSoD ove= r time, and this got worse (happened faster) as I continued to use the syst= em. =C2=A0Another result was severe horizontal tearing on video playback, b= ut the system would work normally otherwise even on reboots.

My conclusion was pretty simple, and it has worke= d for me successfully on over 30 Windows installations (25 being test runs)= . =C2=A0I shared details about queer FLR issues in previous email chains, b= ut many xen-users have reported entirely different problems or that my solu= tion did not work for their configuration. =C2=A0So though I would like to = imagine otherwise it is very possible that every card's make, model and= vendor could behave differently.
=C2=A0
Last but not least, can you say something about your setup? I would be
especially curious about if you do some vga bios stuff, like
extracting and including it into the xen build, and what kernel and
domU parameters you use, for example if iommu=3D1 or iomu=3Dsoft @ kernel and stuff like pci_msitranslate=3D1 and pci_powermanagement in domU
config (and if the viridian=3D1 option does actually do anything)..


I researched and tested setting t= he iommu kernel flag, but during all of my tests it never made any differen= ce in the results so eventually I started omitting it. =C2=A0This is very d= ifferent from the results others have gotten, and I haven't the foggies= t why.

If you google Xen Man Pages you'll find complete do= cumentation of xl.cfg for VM Configurations, which includes descriptions fo= r all the flags for virtual machines.

The addition= al pci flags (global and otherwise) I tried but saw no visible differences = in use or they caused brand new errors instead of solving anything so I als= o omitted them.

I have the viridian flag on for Windows, as the Xen Man= Pages describes it as potentially boosting Windows Vista and newer perform= ance by enabling Hyper-V extensions. =C2=A0I do not know if this has had an= y real impact on my performance, as I also installed GPLPV drivers, if I ha= ve time I may perform some tests later.
=C2=A0
There are a lot of vga passthrough tutorials lately, but from what
it's worth, in my opinion they all lack some detail because everyone simply describes the setup he got working and there is no
comprehensive summary about the benefits of the different options.


By the definition of the word detail I= would disagree that many of the guides lack it, more that they are too det= ailed. =C2=A0I created a guide and just like you said I was very specific a= bout my hardware. =C2=A0However that is because success with Xen is very ha= rdware dependent. =C2=A0It would be extremely difficult to write a "ca= tch-all" guide on passthrough that retained any usefulness if every ca= rd make/model/vendor not to mention every other part in a computer could be= have even slightly differently.

I also don't know anyone who has both the time and = money to purchase and test all available combinations of similar equipment,= but if vendors are interested in lending equipment I'd happily volunte= er to test it.

Not sure what you mean by different options, is that ha= rdware options or the flags mentioned above?
=C2=A0
It would be great if you can help with your experience.


I hope this information is useful, and= look forward to following further replies.
=C2=A0



2013/2/7 Casey DeLorme <cdelorme@g= mail.com>:
> I have an HD 6870 and working CCC, t= ested on both Windows 7 and windows 8.
> Don't have any BSoD's either.
>
> I only had problems with CCC and drivers when I attempted to install o= r
> update drivers without having freshly rebooted or ejected the card. >
> Unfortunately Windows 8 attempts to auto-install the drivers at boot t= ime
> and this caused some headaches during my first go at it.
>
> I experience performance problems after rebooting the HVM, to fix it I= just
> eject the card from the "Safely Remove Hardware and Eject Media&q= uot; icon.
>
>
> On Thu, Feb 7, 2013 at 4:56 PM, David TECHER <davidtecher@yahoo.fr> wrote:
>>
>> Issues for CCC depends on your Video Card too.
>>
>> - Got a HD 79070. It worked for me to add CCC while installing the= 13.2
>> beta driver.
>>
>> =C2=A0 =C2=A0 =C2=A0 Unfortunately there was =C2=A0BSOD issue when= rebooting the domU.
>>
>> =C2=A0 =C2=A0 =C2=A0I had to install .NET 4 Framework and CCC now = works as expected :)
>>
>> - CCC is not supposed to work for HD 6870 but it worked for HD 797= 0.
>>
>> FYI to fix atikmap.sys issue there is a well-known workaround with=
>> something like
>>
>>
>> http://www.computertipsfr= ee.com/fix-43029-atikmdag-sys-blue-screen-bsod-in-windows-7/
>>
>> expand -r atikmdag.sy_ atikmdag.sys
>>
>> But it doesn't work for me :(
>>
>> The good news is that I've just installed Crysis 3 beta demo. = It works
>> like a charm!
>>
>>
>> ________________________________
>> De : Matthias <matthias.kannenberg@googlemail.com>
>> =C3=80 : xen-users@list= s.xen.org
>> Envoy=C3=A9 le : Jeudi 7 f=C3=A9vrier 2013 20h14
>> Objet : [Xen-users] ATI/AMDs atikmpag.sys BSOD while vga passthrou= gh
>>
>> Hi everyone
>>
>> since I'm currently migrating from xm to xl and now are also a= victim
>> of the said error, I started researching on it and found that many=
>> people had the issue but not many found solution and behind this B= SOD
>> (=3DBluescreen of Death), there are actually multiple errors in hi= ding.
>>
>> What I would like to do is gather as much info as possible in this=
>> thread to form a kind of comprehensive guide to fixing this issue.=
>>
>> From what i gathered so far, there are at least 3 different proble= ms
>> with the same symptopms.
>>
>> 1)
>> Situation: After booting the dom0 and booting a windows domU with = an
>> ATI/AMD Card, Windows generally works fine, but after rebooting th= e
>> system, or shutting down / restarting, the Bluescreen occurs or th= e
>> performance massively below normal.
>> Error: Most likely this is cause the Card is not properly resetted= (no
>> FLR [function level reset] )
>> Solution: If the domU reboots into BSOD, you are screwed and have = to
>> reboot the dom0. If it only degrades performance, eject the card a= nd
>> reinitialize to perform a manual reset. Or use the xm toolkit.
>> Status: Don't know if it is fixed yet
>> Source: http://lists.xen.org/archives/html/x= en-users/2012-02/msg00443.html
>> , http://wiki.xen.org/wiki/Talk:Xen_VGA_Passt= hrough_Tested_Adapters
>>
>> 2)
>> Situation: Booting a windows domU results in a BSOD when the CCC >> (=3DCatalyst Control Center) installed.
>> Error: The CCC tries to set some specific settings (most likely >> performance tweaks) within the driver which the driver can't p= ass to
>> the vga through passthrough mode. Result is a BSOD.
>> Solution: Deinstall the CCC in windows safe mode. The driver itsel= f
>> works without it pretty fine.
>> Status: Don't know if it is fixed yet
>> Source: http://lists.xen.org/archives/html/x= en-users/2012-03/msg00617.html
>> Note: I don't really know if this holds for the Vision Engine = Control
>> center, too. the VECC is basically the same as the CCC, so i assum= e it
>> does. I simply haven't found any things referencing it.
>>
>> 3)
>> Situation: This is actually the issue I have. Things seem a lot mo= re
>> random then the other ones. A BSOD happens basically in 80% of boo= ting
>> the Windows domU. Which means, after rebooting dom0, it mostly wor= ks.
>> Rebooting or shutting down / starting the domU works sometimes (On= ce i
>> achieved 6 consecutive reboots or shutdowns / starts before the BS= OD
>> happened) but after I get one Bluescreen, almost never (I can'= t
>> exactly remember if really 'never') comes up again. Of cou= rse I tried
>> the above solutions but this didn't helped me. I also tried di= fferent
>> different versions of the Catalyst driver (from 12/1 to 13/1) and<= br> >> current releases of xen-4.2-testing and xen-unsable. As I said, th= is
>> is when using the xl toolkit. I never had this issues using xm. >> I thought this might belinked to me passing other PCI devices in >> addition (I'm passing some USB controller to the domU) but eve= n
>> deactivating them didn't help. What I actually found helping b= oosting
>> the success rate (but not solving the overall issue) is deinstalli= ng
>> all VGA-Related AMD Driver. Windows then runs on it's own VGA-= Driver
>> (the graphic card is currectly identified and this is an actual at= i
>> driver, so I'm not talking about some generic standard vga dri= ver. I
>> don't know where is driver is coming from).
>> I've attached an analysis file i've gethered from the blue= screen crash
>> dump. I created it using BluescreenView. This is more for currectl= y
>> identifieng the different BSODs, I guess.
>>
>>
>> Some Infos:
>> Kernel: 3.7.4 kern= el.org kernel without patches
>> Xen: latest xen-unstable (but also tested with xen-4.2-testing) >> Processor: AMD Phenom 1090T
>> Mainboard: Asus Crossfire IV
>> VGA: Radeon HD5700 and Radeon HD5450
>> Driver: Currently running Catalyst 13/1 but tested nearly everythi= ng
>> between 12/1 and 13/1
>>
>> Error: Don't know yet
>> Solution: Don't know yet
>> Status: unsolved
>> Source:
>>
>>
>> Okay, so basically that's the story. It would be great if some= people
>> can complete and extend the list. Especially some who already fixe= d
>> the issue on their side. (And of course it would be great if someo= ne
>> has an idea for my problem).
>>
>> Thanks
>>
>> _______________________________________________
>> 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
>
>

--bcaec5040b9a78712104d58a3b34-- --===============4921913537783869731== 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 --===============4921913537783869731==-- From xen-users-bounces@lists.xen.org Wed Feb 13 08:29:13 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 13 Feb 2013 08:29: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 1U5Xgz-0008Hv-C2; Wed, 13 Feb 2013 08:27:49 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U5Xgx-0008Hc-Pu for xen-users@lists.xen.org; Wed, 13 Feb 2013 08:27:48 +0000 Received: from [85.158.137.99:4279] by server-10.bemta-3.messagelabs.com id 5A/22-10609-28E4B115; Wed, 13 Feb 2013 08:27:46 +0000 X-Env-Sender: matthias.kannenberg@googlemail.com X-Msg-Ref: server-14.tower-217.messagelabs.com!1360744050!17798146!1 X-Originating-IP: [209.85.212.177] X-SpamReason: No, hits=0.3 required=7.0 tests=RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 14877 invoked from network); 13 Feb 2013 08:27:31 -0000 Received: from mail-wi0-f177.google.com (HELO mail-wi0-f177.google.com) (209.85.212.177) by server-14.tower-217.messagelabs.com with RC4-SHA encrypted SMTP; 13 Feb 2013 08:27:31 -0000 Received: by mail-wi0-f177.google.com with SMTP id hm14so1058825wib.4 for ; Wed, 13 Feb 2013 00:27:30 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=20120113; h=x-received:mime-version:in-reply-to:references:from:date:message-id :subject:to:cc:content-type; bh=EJ1AAypAlX6QBpVFeRpA8p5en9a85MvtJdMAPKVpKTs=; b=NwTwQuxrHSNWJGITGrk/2nznagL9DJv5auOAG5HkZc8tVLr9wlOZO1bMN//0BND1fG Al5w7RxMF+8pBaPlUjZDXOlk361wNIeAkXhd0EujmYJgWSer6acLHO4BDc3KSY8izChI w/LQodlmEBdwzjbDmsVWgJhPLClNIEZ0Pn7md2PypYW8N+uEBAIlL/k/cEeDgAdMQlUz 1TEr8D7QmF2JyEUtxmxqC0rahxqEv9Q/tEX2D5N9etAyUBynYcLTYNigaLm7V357FKVy ruKtXIlWQMuVUONNSyBxCknvlN8KVF9/GO5HwCcU/W/0Ngc8znmFXnO6VZWmipYl5OeX mb0A== X-Received: by 10.194.57.206 with SMTP id k14mr36025123wjq.26.1360744050652; Wed, 13 Feb 2013 00:27:30 -0800 (PST) MIME-Version: 1.0 Received: by 10.194.80.68 with HTTP; Wed, 13 Feb 2013 00:27:10 -0800 (PST) In-Reply-To: <511A0E9C02000078000BD9EA@nat28.tlf.novell.com> References: <1360581739.29432.115.camel@zakaz.uk.xensource.com> <511A0E9C02000078000BD9EA@nat28.tlf.novell.com> From: Matthias Date: Wed, 13 Feb 2013 09:27:10 +0100 Message-ID: To: Jan Beulich Cc: "boris.ostrovsky@amd.com" , Ian Campbell , "xen-users@lists.xen.org" Subject: Re: [Xen-users] Latest AMD, IOMMU Security Change causing CPU0 Panic and general Problems with AMD+IOMMU changes X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: 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 the info, I guess I have to watch xen-devel more closely. I will test this tomorow when i get a chance and report if the patch fixes my issue. Do you have any idea when all the new AMD/IOMMU patches will be included in the unstable repo? Since i got some issues with the other patches as well and have seen you got around 10 patches for fixing this in xen-devel, it would generally like the idea of having all the fixes in the hg repo then patching everything by hand. Thanks 2013/2/12 Jan Beulich : >>>> On 11.02.13 at 12:22, Ian Campbell wrote: >> On Sat, 2013-02-09 at 02:12 +0000, Matthias wrote: >>> Hi, >>> >>> unfortunatly your latest change "AMD,IOMMU: Clean up old entries in >>> remapping tables when creating new one" (Changeset 26517 in >>> xen-unstable and 25975 in xen-4.2-testing) is causing a CPU0 Panic at >>> boot for me. >>> >>> When i tried to boot latest versions of xen unstable or xen-testing, >>> my dom0 gives me the message: >>> >>> (XEN) ************************************* >>> (XEN) Panic on CPU 0: >>> (XEN) DATAL PAGE FAULT >>> (XEN) [error_code=0000] >>> (XEN) Faulting linear address: 0000000000000000 >>> (XEN) ************************************* >> >> I think this is fixed by "[PATCH 1/2] AMD IOMMU: also spot missing >> IO-APIC entries in IVRS table" posted to xen-devel on Wednesday. >> Message-ID <511264B402000078000BC754@nat28.tlf.novell.com> > > Without a full register/stack trace I would also guess so, but in > that mode it's no more than a guess really. > > Jan > _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Wed Feb 13 08:29:13 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 13 Feb 2013 08:29: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 1U5Xgz-0008Hv-C2; Wed, 13 Feb 2013 08:27:49 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U5Xgx-0008Hc-Pu for xen-users@lists.xen.org; Wed, 13 Feb 2013 08:27:48 +0000 Received: from [85.158.137.99:4279] by server-10.bemta-3.messagelabs.com id 5A/22-10609-28E4B115; Wed, 13 Feb 2013 08:27:46 +0000 X-Env-Sender: matthias.kannenberg@googlemail.com X-Msg-Ref: server-14.tower-217.messagelabs.com!1360744050!17798146!1 X-Originating-IP: [209.85.212.177] X-SpamReason: No, hits=0.3 required=7.0 tests=RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 14877 invoked from network); 13 Feb 2013 08:27:31 -0000 Received: from mail-wi0-f177.google.com (HELO mail-wi0-f177.google.com) (209.85.212.177) by server-14.tower-217.messagelabs.com with RC4-SHA encrypted SMTP; 13 Feb 2013 08:27:31 -0000 Received: by mail-wi0-f177.google.com with SMTP id hm14so1058825wib.4 for ; Wed, 13 Feb 2013 00:27:30 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=20120113; h=x-received:mime-version:in-reply-to:references:from:date:message-id :subject:to:cc:content-type; bh=EJ1AAypAlX6QBpVFeRpA8p5en9a85MvtJdMAPKVpKTs=; b=NwTwQuxrHSNWJGITGrk/2nznagL9DJv5auOAG5HkZc8tVLr9wlOZO1bMN//0BND1fG Al5w7RxMF+8pBaPlUjZDXOlk361wNIeAkXhd0EujmYJgWSer6acLHO4BDc3KSY8izChI w/LQodlmEBdwzjbDmsVWgJhPLClNIEZ0Pn7md2PypYW8N+uEBAIlL/k/cEeDgAdMQlUz 1TEr8D7QmF2JyEUtxmxqC0rahxqEv9Q/tEX2D5N9etAyUBynYcLTYNigaLm7V357FKVy ruKtXIlWQMuVUONNSyBxCknvlN8KVF9/GO5HwCcU/W/0Ngc8znmFXnO6VZWmipYl5OeX mb0A== X-Received: by 10.194.57.206 with SMTP id k14mr36025123wjq.26.1360744050652; Wed, 13 Feb 2013 00:27:30 -0800 (PST) MIME-Version: 1.0 Received: by 10.194.80.68 with HTTP; Wed, 13 Feb 2013 00:27:10 -0800 (PST) In-Reply-To: <511A0E9C02000078000BD9EA@nat28.tlf.novell.com> References: <1360581739.29432.115.camel@zakaz.uk.xensource.com> <511A0E9C02000078000BD9EA@nat28.tlf.novell.com> From: Matthias Date: Wed, 13 Feb 2013 09:27:10 +0100 Message-ID: To: Jan Beulich Cc: "boris.ostrovsky@amd.com" , Ian Campbell , "xen-users@lists.xen.org" Subject: Re: [Xen-users] Latest AMD, IOMMU Security Change causing CPU0 Panic and general Problems with AMD+IOMMU changes X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: 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 the info, I guess I have to watch xen-devel more closely. I will test this tomorow when i get a chance and report if the patch fixes my issue. Do you have any idea when all the new AMD/IOMMU patches will be included in the unstable repo? Since i got some issues with the other patches as well and have seen you got around 10 patches for fixing this in xen-devel, it would generally like the idea of having all the fixes in the hg repo then patching everything by hand. Thanks 2013/2/12 Jan Beulich : >>>> On 11.02.13 at 12:22, Ian Campbell wrote: >> On Sat, 2013-02-09 at 02:12 +0000, Matthias wrote: >>> Hi, >>> >>> unfortunatly your latest change "AMD,IOMMU: Clean up old entries in >>> remapping tables when creating new one" (Changeset 26517 in >>> xen-unstable and 25975 in xen-4.2-testing) is causing a CPU0 Panic at >>> boot for me. >>> >>> When i tried to boot latest versions of xen unstable or xen-testing, >>> my dom0 gives me the message: >>> >>> (XEN) ************************************* >>> (XEN) Panic on CPU 0: >>> (XEN) DATAL PAGE FAULT >>> (XEN) [error_code=0000] >>> (XEN) Faulting linear address: 0000000000000000 >>> (XEN) ************************************* >> >> I think this is fixed by "[PATCH 1/2] AMD IOMMU: also spot missing >> IO-APIC entries in IVRS table" posted to xen-devel on Wednesday. >> Message-ID <511264B402000078000BC754@nat28.tlf.novell.com> > > Without a full register/stack trace I would also guess so, but in > that mode it's no more than a guess really. > > Jan > _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Wed Feb 13 08:32:56 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 13 Feb 2013 08:32: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 1U5Xks-0000HJ-Ty; Wed, 13 Feb 2013 08:31:50 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U5Xkr-0000HA-4b for xen-users@lists.xen.org; Wed, 13 Feb 2013 08:31:49 +0000 Received: from [85.158.138.51:58557] by server-7.bemta-3.messagelabs.com id 54/59-10367-47F4B115; Wed, 13 Feb 2013 08:31:48 +0000 X-Env-Sender: JBeulich@suse.com X-Msg-Ref: server-9.tower-174.messagelabs.com!1360744271!27405961!1 X-Originating-IP: [130.57.49.28] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogMTMwLjU3LjQ5LjI4ID0+IDQxMDk=\n X-StarScan-Received: X-StarScan-Version: 6.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 12711 invoked from network); 13 Feb 2013 08:31:11 -0000 Received: from nat28.tlf.novell.com (HELO nat28.tlf.novell.com) (130.57.49.28) by server-9.tower-174.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 13 Feb 2013 08:31:11 -0000 Received: from EMEA1-MTA by nat28.tlf.novell.com with Novell_GroupWise; Wed, 13 Feb 2013 08:31:10 +0000 Message-Id: <511B5D5B02000078000BDE76@nat28.tlf.novell.com> X-Mailer: Novell GroupWise Internet Agent 12.0.1 Date: Wed, 13 Feb 2013 08:31:07 +0000 From: "Jan Beulich" To: "Matthias" References: <1360581739.29432.115.camel@zakaz.uk.xensource.com> <511A0E9C02000078000BD9EA@nat28.tlf.novell.com> In-Reply-To: Mime-Version: 1.0 Content-Disposition: inline Cc: "boris.ostrovsky@amd.com" , Ian Campbell , "xen-users@lists.xen.org" Subject: Re: [Xen-users] Latest AMD, IOMMU Security Change causing CPU0 Panic and general Problems with AMD+IOMMU changes X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: 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 13.02.13 at 09:27, Matthias wrote: > Do you have any idea when all the new AMD/IOMMU patches will be > included in the unstable repo? Since i got some issues with the other > patches as well and have seen you got around 10 patches for fixing > this in xen-devel, it would generally like the idea of having all the > fixes in the hg repo then patching everything by hand. This largely depends on the pending patches getting reviewed and acked appropriately. But it's three patches only according to my counting, one of which being in need of a conceptual decision (i.e. unlikely to go in very quickly), and out of those three only one is a regression fix (the one I pointed you to). Jan _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Wed Feb 13 08:32:56 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 13 Feb 2013 08:32: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 1U5Xks-0000HJ-Ty; Wed, 13 Feb 2013 08:31:50 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U5Xkr-0000HA-4b for xen-users@lists.xen.org; Wed, 13 Feb 2013 08:31:49 +0000 Received: from [85.158.138.51:58557] by server-7.bemta-3.messagelabs.com id 54/59-10367-47F4B115; Wed, 13 Feb 2013 08:31:48 +0000 X-Env-Sender: JBeulich@suse.com X-Msg-Ref: server-9.tower-174.messagelabs.com!1360744271!27405961!1 X-Originating-IP: [130.57.49.28] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogMTMwLjU3LjQ5LjI4ID0+IDQxMDk=\n X-StarScan-Received: X-StarScan-Version: 6.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 12711 invoked from network); 13 Feb 2013 08:31:11 -0000 Received: from nat28.tlf.novell.com (HELO nat28.tlf.novell.com) (130.57.49.28) by server-9.tower-174.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 13 Feb 2013 08:31:11 -0000 Received: from EMEA1-MTA by nat28.tlf.novell.com with Novell_GroupWise; Wed, 13 Feb 2013 08:31:10 +0000 Message-Id: <511B5D5B02000078000BDE76@nat28.tlf.novell.com> X-Mailer: Novell GroupWise Internet Agent 12.0.1 Date: Wed, 13 Feb 2013 08:31:07 +0000 From: "Jan Beulich" To: "Matthias" References: <1360581739.29432.115.camel@zakaz.uk.xensource.com> <511A0E9C02000078000BD9EA@nat28.tlf.novell.com> In-Reply-To: Mime-Version: 1.0 Content-Disposition: inline Cc: "boris.ostrovsky@amd.com" , Ian Campbell , "xen-users@lists.xen.org" Subject: Re: [Xen-users] Latest AMD, IOMMU Security Change causing CPU0 Panic and general Problems with AMD+IOMMU changes X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: 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 13.02.13 at 09:27, Matthias wrote: > Do you have any idea when all the new AMD/IOMMU patches will be > included in the unstable repo? Since i got some issues with the other > patches as well and have seen you got around 10 patches for fixing > this in xen-devel, it would generally like the idea of having all the > fixes in the hg repo then patching everything by hand. This largely depends on the pending patches getting reviewed and acked appropriately. But it's three patches only according to my counting, one of which being in need of a conceptual decision (i.e. unlikely to go in very quickly), and out of those three only one is a regression fix (the one I pointed you to). Jan _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Wed Feb 13 11:07:41 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 13 Feb 2013 11:07: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 1U5aAN-0002ht-1R; Wed, 13 Feb 2013 11:06:19 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U5aAM-0002ho-63 for xen-users@lists.xen.org; Wed, 13 Feb 2013 11:06:18 +0000 Received: from [85.158.139.83:26810] by server-10.bemta-5.messagelabs.com id FD/74-04697-9A37B115; Wed, 13 Feb 2013 11:06:17 +0000 X-Env-Sender: pigeon@pigeond.net X-Msg-Ref: server-4.tower-182.messagelabs.com!1360753543!26690607!1 X-Originating-IP: [203.59.1.218] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogMjAzLjU5LjEuMjE4ID0+IDE0NTg0\n X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 845 invoked from network); 13 Feb 2013 11:05:44 -0000 Received: from icp-osb-irony-out2.external.iinet.net.au (HELO icp-osb-irony-out2.external.iinet.net.au) (203.59.1.218) by server-4.tower-182.messagelabs.com with SMTP; 13 Feb 2013 11:05:44 -0000 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: Av8EAGFyG1F8lWUl/2dsb2JhbABEwG8Wc4IfAQEEATpECwsNFCUPOgENBgEsh3IFvyGSAwOWI4YUikCDGg X-IronPort-AV: E=Sophos;i="4.84,655,1355068800"; d="scan'208";a="86285000" Received: from unknown (HELO torankusu.pigeond.net) ([124.149.101.37]) by icp-osb-irony-out2.iinet.net.au with ESMTP; 13 Feb 2013 19:05:41 +0800 Received: from furiza.pigeond.net ([192.168.42.20]:50369 helo=pigeond.net) by torankusu.pigeond.net with esmtp (Exim 4.72) (envelope-from ) id 1U5a9k-0003w5-Gu; Wed, 13 Feb 2013 22:05:40 +1100 Date: Wed, 13 Feb 2013 22:05:35 +1100 From: Howell Tam To: James Harper , "xen-users@lists.xen.org" Message-ID: <20130213220535.06c0de16@pigeond.net> In-Reply-To: <6035A0D088A63A46850C3988ED045A4B3566C353@BITCOM1.int.sbss.com.au> References: <20130210235853.4ebb70b8@pigeond.net> <20130212084728.64c49ea1@pigeond.net> <6035A0D088A63A46850C3988ED045A4B35667928@BITCOM1.int.sbss.com.au> <20130212210541.3b71b98f@pigeond.net> <6035A0D088A63A46850C3988ED045A4B3566C353@BITCOM1.int.sbss.com.au> Organization: pigeond.net X-Mailer: Claws Mail 3.8.1 (GTK+ 2.24.10; x86_64-pc-linux-gnu) Mime-Version: 1.0 Subject: Re: [Xen-users] Dom0 freeze on HVM DomU Windows reboot with 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 > Uninstalling GPLPV leaves a registry entry present that causes it to > not boot. Is the BSoD start with 0x0000007b? If so that's the "cant > find boot device" > > If you can boot of the win7 boot cd then into the recovery console, > load the registry hive (eg load c:\windows\system32\config\system) > and delete xenpci from anything called upperfilters it should boot > again. Thanks. The good news is, I did what you said and now the win7 boots again. The bad news is now, without the GPLPV drivers, shutting down/restarting the win7 will still cause a complete machine freeze. -- Regards, Howell. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Wed Feb 13 11:07:41 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 13 Feb 2013 11:07: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 1U5aAN-0002ht-1R; Wed, 13 Feb 2013 11:06:19 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U5aAM-0002ho-63 for xen-users@lists.xen.org; Wed, 13 Feb 2013 11:06:18 +0000 Received: from [85.158.139.83:26810] by server-10.bemta-5.messagelabs.com id FD/74-04697-9A37B115; Wed, 13 Feb 2013 11:06:17 +0000 X-Env-Sender: pigeon@pigeond.net X-Msg-Ref: server-4.tower-182.messagelabs.com!1360753543!26690607!1 X-Originating-IP: [203.59.1.218] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogMjAzLjU5LjEuMjE4ID0+IDE0NTg0\n X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 845 invoked from network); 13 Feb 2013 11:05:44 -0000 Received: from icp-osb-irony-out2.external.iinet.net.au (HELO icp-osb-irony-out2.external.iinet.net.au) (203.59.1.218) by server-4.tower-182.messagelabs.com with SMTP; 13 Feb 2013 11:05:44 -0000 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: Av8EAGFyG1F8lWUl/2dsb2JhbABEwG8Wc4IfAQEEATpECwsNFCUPOgENBgEsh3IFvyGSAwOWI4YUikCDGg X-IronPort-AV: E=Sophos;i="4.84,655,1355068800"; d="scan'208";a="86285000" Received: from unknown (HELO torankusu.pigeond.net) ([124.149.101.37]) by icp-osb-irony-out2.iinet.net.au with ESMTP; 13 Feb 2013 19:05:41 +0800 Received: from furiza.pigeond.net ([192.168.42.20]:50369 helo=pigeond.net) by torankusu.pigeond.net with esmtp (Exim 4.72) (envelope-from ) id 1U5a9k-0003w5-Gu; Wed, 13 Feb 2013 22:05:40 +1100 Date: Wed, 13 Feb 2013 22:05:35 +1100 From: Howell Tam To: James Harper , "xen-users@lists.xen.org" Message-ID: <20130213220535.06c0de16@pigeond.net> In-Reply-To: <6035A0D088A63A46850C3988ED045A4B3566C353@BITCOM1.int.sbss.com.au> References: <20130210235853.4ebb70b8@pigeond.net> <20130212084728.64c49ea1@pigeond.net> <6035A0D088A63A46850C3988ED045A4B35667928@BITCOM1.int.sbss.com.au> <20130212210541.3b71b98f@pigeond.net> <6035A0D088A63A46850C3988ED045A4B3566C353@BITCOM1.int.sbss.com.au> Organization: pigeond.net X-Mailer: Claws Mail 3.8.1 (GTK+ 2.24.10; x86_64-pc-linux-gnu) Mime-Version: 1.0 Subject: Re: [Xen-users] Dom0 freeze on HVM DomU Windows reboot with 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 > Uninstalling GPLPV leaves a registry entry present that causes it to > not boot. Is the BSoD start with 0x0000007b? If so that's the "cant > find boot device" > > If you can boot of the win7 boot cd then into the recovery console, > load the registry hive (eg load c:\windows\system32\config\system) > and delete xenpci from anything called upperfilters it should boot > again. Thanks. The good news is, I did what you said and now the win7 boots again. The bad news is now, without the GPLPV drivers, shutting down/restarting the win7 will still cause a complete machine freeze. -- Regards, Howell. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Wed Feb 13 14:19:34 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 13 Feb 2013 14:19: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 1U5dA5-0005Zp-TD; Wed, 13 Feb 2013 14:18:13 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U5dA4-0005Zk-Bd for xen-users@lists.xen.org; Wed, 13 Feb 2013 14:18:12 +0000 Received: from [85.158.138.51:30267] by server-7.bemta-3.messagelabs.com id 33/BE-10367-3A0AB115; Wed, 13 Feb 2013 14:18:11 +0000 X-Env-Sender: falck.andreas.lists@gmail.com X-Msg-Ref: server-10.tower-174.messagelabs.com!1360765088!23365400!1 X-Originating-IP: [209.85.217.182] X-SpamReason: No, hits=2.2 required=7.0 tests=BODY_RANDOMQ,HTML_10_20, HTML_MESSAGE,ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 23976 invoked from network); 13 Feb 2013 14:18:09 -0000 Received: from mail-lb0-f182.google.com (HELO mail-lb0-f182.google.com) (209.85.217.182) by server-10.tower-174.messagelabs.com with RC4-SHA encrypted SMTP; 13 Feb 2013 14:18:09 -0000 Received: by mail-lb0-f182.google.com with SMTP id gg6so958604lbb.41 for ; Wed, 13 Feb 2013 06:17:54 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:date:message-id:subject:from:to :content-type; bh=t6V/8SJmh+mS/2Amu39r+tCY3BOHK2aKOXKry1ZQ59Q=; b=BDyIFqt6Gl8lRrIknKKDuYiaKAsbDy+VTwTtp351d4vXQaEP2cOE3OZAc9c5UR/y26 Ndoy2H6hgfXfZjhSgolbOtNkxxBhxCQMtkqR26WsbByI7iU28gmpYHfS/3AQW1KOsLlv 2ni6S/sayl2T65x26CnDxbXYLjX9SDPlidEXBWWwaiZgdNJre/1UvaeeZaTEJ0Rs+Nbi QVItagisL+MQf32CWnilxN8lj380rraz+GXSNeyV2kjZcGu+aaU++TWh5MU1Mm25gAue g3uEEzqVO4b8C2FIlOFpdFbAiRAJ02qNcldwGlrR/H3k6RTkkHeQGarrSZNYalq60KMA tsUQ== MIME-Version: 1.0 X-Received: by 10.152.106.5 with SMTP id gq5mr20429522lab.5.1360765074407; Wed, 13 Feb 2013 06:17:54 -0800 (PST) Received: by 10.114.11.170 with HTTP; Wed, 13 Feb 2013 06:17:54 -0800 (PST) Date: Wed, 13 Feb 2013 15:17:54 +0100 Message-ID: From: Andreas Falck To: xen-users@lists.xen.org Subject: [Xen-users] IVHD error, AMD-Vi gets disabled (4.1.3-3ubuntu1.3) X-BeenThere: xen-users@lists.xen.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="===============1818140942270693756==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============1818140942270693756== Content-Type: multipart/alternative; boundary=f46d04083f2de2024104d59bce34 --f46d04083f2de2024104d59bce34 Content-Type: text/plain; charset=ISO-8859-1 Hello, I have a system running ubuntu12.10 with xen 4.1.3, which I believe was recently upgraded from xen 4.1.2 via the normal ubuntu 'apt-get upgrade' path. 2 AMD opteron 6134 cpus, supermicro H8DG6 motherboard. Recently I noticed that AMD-Vi gets disabled at boot, which didn't happen before. >From 'xm dmesg': (XEN) Command line: placeholder amd-iommu-debug iommu=verbose iommu=1 apic=debug iommu_inclusive_mapping=1 [...] (XEN) IVHD Error: Conflicting IO-APIC 0x0 entries (XEN) AMD-Vi: Error initialization (XEN) I/O virtualisation disabled I noticed it when getting an error upon trying to passthrough a PCI device. A month ago PCI passthru worked, but I haven't tested in between so I cannot say exactly when the problem arose, if it has to do with the transit from 4.1.2 to 4.1.3 or not. IOMMU is enabled in BIOS, of course. Could it be a xen bug (I know that my system is somewhat unusual), a old BIOS bug interacting with newer xen or an aqcuired hardware error? I'll of course provide more logs if needed. Thanks, Andreas ADDENDUM: Some additional debugging I did (maybe helpful, maybe not): If I boot a baremetal linux3.5 kernel, IOMMU seems to enable as it should, but I get an "AMD-Vi: Completion-Wait loop timed out" message in dmesg followed by a soft CPU lockup: [ 1.152261] AMD-Vi: Enabling IOMMU at 0000:00:00.2 cap 0x40 [ 1.226282] AMD-Vi: Enabling IOMMU at 0000:40:00.2 cap 0x40 [ 1.333560] AMD-Vi: Completion-Wait loop timed out [ 1.440835] AMD-Vi: Completion-Wait loop timed out (last line repeated x 100ish) [ 28.425464] BUG: soft lockup - CPU#11 stuck for 22s! [swapper/0:1] [ 28.425467] Modules linked in: [ 28.425471] CPU 11 [ 28.425472] Modules linked in: [ 28.425476] [ 28.425479] Pid: 1, comm: swapper/0 Not tainted 3.5.0-23-generic #35-Ubuntu Supermicro H8DG6/H8DGi/H8DG6/H8DGi [ 28.425486] RIP: 0010:[] [] native_read_tsc+0x6/0x20 [ 28.425497] RSP: 0000:ffff880234855d10 EFLAGS: 00000246 [ 28.425501] RAX: 00000000226cded8 RBX: 00000000ffffffff RCX: 000000000118c4ae [ 28.425504] RDX: 0000000000000025 RSI: 0000000000000286 RDI: 00000000000008ea [ 28.425507] RBP: ffff880234855d10 R08: 000000000000040a R09: 0000000000001ff0 [ 28.425511] R10: 0720072007200720 R11: 0720072007200720 R12: ffffffff81e49c23 [ 28.425514] R13: 0000000000000246 R14: ffff880234855cf0 R15: 0000000000000006 [ 28.425517] FS: 0000000000000000(0000) GS:ffff88083fcc0000(0000) knlGS:0000000000000000 [ 28.425521] CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b [ 28.425524] CR2: 0000000000000000 CR3: 0000000001c0b000 CR4: 00000000000007e0 [ 28.425527] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 [ 28.425531] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400 [ 28.425534] Process swapper/0 (pid: 1, threadinfo ffff880234854000, task ffff880234858000) [ 28.425538] Stack: [ 28.425540] ffff880234855d40 ffffffff8133599a 0000000000010ef6 ffff880234855d98 [ 28.425547] 0000000000000286 0000000000002000 ffff880234855d50 ffffffff813358cc [ 28.425553] ffff880234855d70 ffffffff8154a7c5 ffff880434e4c800 ffff880434e4c814 [ 28.425559] Call Trace: [ 28.425566] [] delay_tsc+0x4a/0x80 [ 28.425570] [] __const_udelay+0x2c/0x30 [ 28.425577] [] wait_on_sem+0x35/0x70 [ 28.425582] [] iommu_queue_command_sync+0x83/0x140 [ 28.425587] [] iommu_queue_command+0x13/0x20 [ 28.425592] [] iommu_flush_all_caches+0xd7/0x100 [ 28.425597] [] enable_iommus+0x250/0x360 [ 28.425605] [] ? memblock_find_dma_reserve+0x13d/0x13d [ 28.425611] [] amd_iommu_init_hardware+0x1f7/0x231 [ 28.425616] [] amd_iommu_init+0xb/0x8b [ 28.425620] [] pci_iommu_init+0x13/0x3e [ 28.425627] [] do_one_initcall+0x12a/0x180 [ 28.425631] [] kernel_init+0x140/0x1c9 [ 28.425635] [] ? loglevel+0x31/0x31 [ 28.425642] [] kernel_thread_helper+0x4/0x10 [ 28.425646] [] ? start_kernel+0x3d2/0x3d2 [ 28.425650] [] ? gs_change+0x13/0x13 [ 28.425652] Code: c3 0f 1f 40 00 55 89 f8 48 89 e5 e6 70 e4 71 5d c3 0f 1f 40 00 55 89 f0 4 8 89 e5 e6 70 89 f8 e6 71 5d c3 66 90 55 48 89 e5 0f 31 <89> c0 48 c1 e2 20 48 09 c2 48 89 d0 5d c3 66 66 66 2e 0f 1f 84 [ 28.458326] AMD-Vi: Completion-Wait loop timed out [ 28.565522] AMD-Vi: Completion-Wait loop timed out [ 28.672707] AMD-Vi: Completion-Wait loop timed out [ 28.779909] AMD-Vi: Completion-Wait loop timed out [ 28.886441] AMD-Vi: Completion-Wait loop timed out [ 28.886491] pci 0000:00:00.2: irq 40 for MSI/MSI-X [ 28.886676] pci 0000:40:00.2: irq 41 for MSI/MSI-X [ 28.896427] AMD-Vi: Lazy IO/TLB flushing enabled (boot continues as normal) This may point towards either hardware or bios. But I do not know if this would have happened before I started getting problems with xen. --f46d04083f2de2024104d59bce34 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Hello,

I have a system running ubuntu12.10 with xen 4.1.3, which I b= elieve was recently upgraded from xen 4.1.2 via the normal ubuntu 'apt-= get upgrade' path. 2 AMD opteron 6134 cpus, supermicro H8DG6 motherboar= d.

Recently I noticed that AMD-Vi gets disabled at boot, which didn't = happen before.

From 'xm dmesg':

(XEN) Command line: = placeholder amd-iommu-debug iommu=3Dverbose iommu=3D1 apic=3Ddebug iommu_in= clusive_mapping=3D1
[...]
(XEN) IVHD Error: Conflicting IO-APIC 0x0 entries
(XEN) AMD-Vi:= Error initialization
(XEN) I/O virtualisation disabled

I noticed it when getting an error= upon trying to passthrough a PCI device. A month ago PCI passthru worked, = but I haven't tested in between so I cannot say exactly when the proble= m arose, if it has to do with the transit from 4.1.2 to 4.1.3 or not. IOMMU= is enabled in BIOS, of course.

Could it be a xen bug (I know that my system is somewhat unusual), a ol= d BIOS bug interacting with newer xen or an aqcuired hardware error? I'= ll of course provide more logs if needed.

Thanks,
Andreas




ADDENDUM:
Some additional debugging I did (maybe helpful= , maybe not):

If I boot a baremetal linux3.5 kernel, IOMMU seems to= enable as it should, but I get an "AMD-Vi: Completion-Wait loop timed= out" message in dmesg followed by a soft CPU lockup:

[=A0=A0=A0 1.152261] AMD-Vi: Enabling IOMMU at 0000:00:00.2 cap 0x40[=A0=A0=A0 1.226282] AMD-Vi: Enabling IOMMU at 0000:40:00.2 cap 0x40
[= =A0=A0=A0 1.333560] AMD-Vi: Completion-Wait loop timed out
[=A0=A0=A0 1.= 440835] AMD-Vi: Completion-Wait loop timed out

(last line repeated x 100ish)

[=A0=A0 28.425464] BUG: soft locku= p - CPU#11 stuck for 22s! [swapper/0:1]
[=A0=A0 28.425467] Modules linke= d in:
[=A0=A0 28.425471] CPU 11
[=A0=A0 28.425472] Modules linked in= :
[=A0=A0 28.425476]
[=A0=A0 28.425479] Pid: 1, comm: swapper/0 Not tainted 3.5.0-23-generic #35= -Ubuntu Supermicro H8DG6/H8DGi/H8DG6/H8DGi
[=A0=A0 28.425486] RIP: 0010:= [<ffffffff8101aff6>]=A0 [<ffffffff8101aff6>] native_read_tsc+0x= 6/0x20
[=A0=A0 28.425497] RSP: 0000:ffff880234855d10=A0 EFLAGS: 00000246
[=A0= =A0 28.425501] RAX: 00000000226cded8 RBX: 00000000ffffffff RCX: 00000000011= 8c4ae
[=A0=A0 28.425504] RDX: 0000000000000025 RSI: 0000000000000286 RDI= : 00000000000008ea
[=A0=A0 28.425507] RBP: ffff880234855d10 R08: 000000000000040a R09: 0000000= 000001ff0
[=A0=A0 28.425511] R10: 0720072007200720 R11: 0720072007200720= R12: ffffffff81e49c23
[=A0=A0 28.425514] R13: 0000000000000246 R14: fff= f880234855cf0 R15: 0000000000000006
[=A0=A0 28.425517] FS:=A0 0000000000000000(0000) GS:ffff88083fcc0000(0000) = knlGS:0000000000000000
[=A0=A0 28.425521] CS:=A0 0010 DS: 0000 ES: 0000 = CR0: 000000008005003b
[=A0=A0 28.425524] CR2: 0000000000000000 CR3: 0000= 000001c0b000 CR4: 00000000000007e0
[=A0=A0 28.425527] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000= 000000000
[=A0=A0 28.425531] DR3: 0000000000000000 DR6: 00000000ffff0ff0= DR7: 0000000000000400
[=A0=A0 28.425534] Process swapper/0 (pid: 1, thr= eadinfo ffff880234854000, task ffff880234858000)
[=A0=A0 28.425538] Stack:
[=A0=A0 28.425540]=A0 ffff880234855d40 fffffff= f8133599a 0000000000010ef6 ffff880234855d98
[=A0=A0 28.425547]=A0 000000= 0000000286 0000000000002000 ffff880234855d50 ffffffff813358cc
[=A0=A0 28= .425553]=A0 ffff880234855d70 ffffffff8154a7c5 ffff880434e4c800 ffff880434e4= c814
[=A0=A0 28.425559] Call Trace:
[=A0=A0 28.425566]=A0 [<ffffffff813359= 9a>] delay_tsc+0x4a/0x80
[=A0=A0 28.425570]=A0 [<ffffffff813358cc&= gt;] __const_udelay+0x2c/0x30
[=A0=A0 28.425577]=A0 [<ffffffff8154a7c= 5>] wait_on_sem+0x35/0x70
[=A0=A0 28.425582]=A0 [<ffffffff8154b493>] iommu_queue_command_sync+0= x83/0x140
[=A0=A0 28.425587]=A0 [<ffffffff8154b563>] iommu_queue_c= ommand+0x13/0x20
[=A0=A0 28.425592]=A0 [<ffffffff8154dd37>] iommu_= flush_all_caches+0xd7/0x100
[=A0=A0 28.425597]=A0 [<ffffffff8154ed90>] enable_iommus+0x250/0x360<= br>[=A0=A0 28.425605]=A0 [<ffffffff81cfc17e>] ? memblock_find_dma_res= erve+0x13d/0x13d
[=A0=A0 28.425611]=A0 [<ffffffff81d328ce>] amd_io= mmu_init_hardware+0x1f7/0x231
[=A0=A0 28.425616]=A0 [<ffffffff81d32913>] amd_iommu_init+0xb/0x8b[=A0=A0 28.425620]=A0 [<ffffffff81cfc191>] pci_iommu_init+0x13/0x3e<= br>[=A0=A0 28.425627]=A0 [<ffffffff8100212a>] do_one_initcall+0x12a/0= x180
[=A0=A0 28.425631]=A0 [<ffffffff81cf3d3a>] kernel_init+0x140/= 0x1c9
[=A0=A0 28.425635]=A0 [<ffffffff81cf3588>] ? loglevel+0x31/0x31
[= =A0=A0 28.425642]=A0 [<ffffffff8168ce64>] kernel_thread_helper+0x4/0x= 10
[=A0=A0 28.425646]=A0 [<ffffffff81cf3bfa>] ? start_kernel+0x3d2= /0x3d2
[=A0=A0 28.425650]=A0 [<ffffffff8168ce60>] ? gs_change+0x13= /0x13
[=A0=A0 28.425652] Code: c3 0f 1f 40 00 55 89 f8 48 89 e5 e6 70 e4 71 5d c3= 0f 1f 40 00 55 89 f0 4
8 89 e5 e6 70 89 f8 e6 71 5d c3 66 90 55 48 89 e= 5 0f 31 <89> c0 48 c1 e2 20 48 09 c2 48 89 d0
5d c3 66 66 66 2e 0= f 1f 84
[=A0=A0 28.458326] AMD-Vi: Completion-Wait loop timed out
[=A0=A0 28.565= 522] AMD-Vi: Completion-Wait loop timed out
[=A0=A0 28.672707] AMD-Vi: C= ompletion-Wait loop timed out
[=A0=A0 28.779909] AMD-Vi: Completion-Wait= loop timed out
[=A0=A0 28.886441] AMD-Vi: Completion-Wait loop timed out
[=A0=A0 28.886= 491] pci 0000:00:00.2: irq 40 for MSI/MSI-X
[=A0=A0 28.886676] pci 0000:= 40:00.2: irq 41 for MSI/MSI-X
[=A0=A0 28.896427] AMD-Vi: Lazy IO/TLB flu= shing enabled

(boot continues as normal)

This may point towards either hardwar= e or bios. But I do not know if this would have happened before I started g= etting problems with xen.
--f46d04083f2de2024104d59bce34-- --===============1818140942270693756== 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 --===============1818140942270693756==-- From xen-users-bounces@lists.xen.org Wed Feb 13 14:19:34 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 13 Feb 2013 14:19: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 1U5dA5-0005Zp-TD; Wed, 13 Feb 2013 14:18:13 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U5dA4-0005Zk-Bd for xen-users@lists.xen.org; Wed, 13 Feb 2013 14:18:12 +0000 Received: from [85.158.138.51:30267] by server-7.bemta-3.messagelabs.com id 33/BE-10367-3A0AB115; Wed, 13 Feb 2013 14:18:11 +0000 X-Env-Sender: falck.andreas.lists@gmail.com X-Msg-Ref: server-10.tower-174.messagelabs.com!1360765088!23365400!1 X-Originating-IP: [209.85.217.182] X-SpamReason: No, hits=2.2 required=7.0 tests=BODY_RANDOMQ,HTML_10_20, HTML_MESSAGE,ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 23976 invoked from network); 13 Feb 2013 14:18:09 -0000 Received: from mail-lb0-f182.google.com (HELO mail-lb0-f182.google.com) (209.85.217.182) by server-10.tower-174.messagelabs.com with RC4-SHA encrypted SMTP; 13 Feb 2013 14:18:09 -0000 Received: by mail-lb0-f182.google.com with SMTP id gg6so958604lbb.41 for ; Wed, 13 Feb 2013 06:17:54 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:date:message-id:subject:from:to :content-type; bh=t6V/8SJmh+mS/2Amu39r+tCY3BOHK2aKOXKry1ZQ59Q=; b=BDyIFqt6Gl8lRrIknKKDuYiaKAsbDy+VTwTtp351d4vXQaEP2cOE3OZAc9c5UR/y26 Ndoy2H6hgfXfZjhSgolbOtNkxxBhxCQMtkqR26WsbByI7iU28gmpYHfS/3AQW1KOsLlv 2ni6S/sayl2T65x26CnDxbXYLjX9SDPlidEXBWWwaiZgdNJre/1UvaeeZaTEJ0Rs+Nbi QVItagisL+MQf32CWnilxN8lj380rraz+GXSNeyV2kjZcGu+aaU++TWh5MU1Mm25gAue g3uEEzqVO4b8C2FIlOFpdFbAiRAJ02qNcldwGlrR/H3k6RTkkHeQGarrSZNYalq60KMA tsUQ== MIME-Version: 1.0 X-Received: by 10.152.106.5 with SMTP id gq5mr20429522lab.5.1360765074407; Wed, 13 Feb 2013 06:17:54 -0800 (PST) Received: by 10.114.11.170 with HTTP; Wed, 13 Feb 2013 06:17:54 -0800 (PST) Date: Wed, 13 Feb 2013 15:17:54 +0100 Message-ID: From: Andreas Falck To: xen-users@lists.xen.org Subject: [Xen-users] IVHD error, AMD-Vi gets disabled (4.1.3-3ubuntu1.3) X-BeenThere: xen-users@lists.xen.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="===============1818140942270693756==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============1818140942270693756== Content-Type: multipart/alternative; boundary=f46d04083f2de2024104d59bce34 --f46d04083f2de2024104d59bce34 Content-Type: text/plain; charset=ISO-8859-1 Hello, I have a system running ubuntu12.10 with xen 4.1.3, which I believe was recently upgraded from xen 4.1.2 via the normal ubuntu 'apt-get upgrade' path. 2 AMD opteron 6134 cpus, supermicro H8DG6 motherboard. Recently I noticed that AMD-Vi gets disabled at boot, which didn't happen before. >From 'xm dmesg': (XEN) Command line: placeholder amd-iommu-debug iommu=verbose iommu=1 apic=debug iommu_inclusive_mapping=1 [...] (XEN) IVHD Error: Conflicting IO-APIC 0x0 entries (XEN) AMD-Vi: Error initialization (XEN) I/O virtualisation disabled I noticed it when getting an error upon trying to passthrough a PCI device. A month ago PCI passthru worked, but I haven't tested in between so I cannot say exactly when the problem arose, if it has to do with the transit from 4.1.2 to 4.1.3 or not. IOMMU is enabled in BIOS, of course. Could it be a xen bug (I know that my system is somewhat unusual), a old BIOS bug interacting with newer xen or an aqcuired hardware error? I'll of course provide more logs if needed. Thanks, Andreas ADDENDUM: Some additional debugging I did (maybe helpful, maybe not): If I boot a baremetal linux3.5 kernel, IOMMU seems to enable as it should, but I get an "AMD-Vi: Completion-Wait loop timed out" message in dmesg followed by a soft CPU lockup: [ 1.152261] AMD-Vi: Enabling IOMMU at 0000:00:00.2 cap 0x40 [ 1.226282] AMD-Vi: Enabling IOMMU at 0000:40:00.2 cap 0x40 [ 1.333560] AMD-Vi: Completion-Wait loop timed out [ 1.440835] AMD-Vi: Completion-Wait loop timed out (last line repeated x 100ish) [ 28.425464] BUG: soft lockup - CPU#11 stuck for 22s! [swapper/0:1] [ 28.425467] Modules linked in: [ 28.425471] CPU 11 [ 28.425472] Modules linked in: [ 28.425476] [ 28.425479] Pid: 1, comm: swapper/0 Not tainted 3.5.0-23-generic #35-Ubuntu Supermicro H8DG6/H8DGi/H8DG6/H8DGi [ 28.425486] RIP: 0010:[] [] native_read_tsc+0x6/0x20 [ 28.425497] RSP: 0000:ffff880234855d10 EFLAGS: 00000246 [ 28.425501] RAX: 00000000226cded8 RBX: 00000000ffffffff RCX: 000000000118c4ae [ 28.425504] RDX: 0000000000000025 RSI: 0000000000000286 RDI: 00000000000008ea [ 28.425507] RBP: ffff880234855d10 R08: 000000000000040a R09: 0000000000001ff0 [ 28.425511] R10: 0720072007200720 R11: 0720072007200720 R12: ffffffff81e49c23 [ 28.425514] R13: 0000000000000246 R14: ffff880234855cf0 R15: 0000000000000006 [ 28.425517] FS: 0000000000000000(0000) GS:ffff88083fcc0000(0000) knlGS:0000000000000000 [ 28.425521] CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b [ 28.425524] CR2: 0000000000000000 CR3: 0000000001c0b000 CR4: 00000000000007e0 [ 28.425527] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 [ 28.425531] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400 [ 28.425534] Process swapper/0 (pid: 1, threadinfo ffff880234854000, task ffff880234858000) [ 28.425538] Stack: [ 28.425540] ffff880234855d40 ffffffff8133599a 0000000000010ef6 ffff880234855d98 [ 28.425547] 0000000000000286 0000000000002000 ffff880234855d50 ffffffff813358cc [ 28.425553] ffff880234855d70 ffffffff8154a7c5 ffff880434e4c800 ffff880434e4c814 [ 28.425559] Call Trace: [ 28.425566] [] delay_tsc+0x4a/0x80 [ 28.425570] [] __const_udelay+0x2c/0x30 [ 28.425577] [] wait_on_sem+0x35/0x70 [ 28.425582] [] iommu_queue_command_sync+0x83/0x140 [ 28.425587] [] iommu_queue_command+0x13/0x20 [ 28.425592] [] iommu_flush_all_caches+0xd7/0x100 [ 28.425597] [] enable_iommus+0x250/0x360 [ 28.425605] [] ? memblock_find_dma_reserve+0x13d/0x13d [ 28.425611] [] amd_iommu_init_hardware+0x1f7/0x231 [ 28.425616] [] amd_iommu_init+0xb/0x8b [ 28.425620] [] pci_iommu_init+0x13/0x3e [ 28.425627] [] do_one_initcall+0x12a/0x180 [ 28.425631] [] kernel_init+0x140/0x1c9 [ 28.425635] [] ? loglevel+0x31/0x31 [ 28.425642] [] kernel_thread_helper+0x4/0x10 [ 28.425646] [] ? start_kernel+0x3d2/0x3d2 [ 28.425650] [] ? gs_change+0x13/0x13 [ 28.425652] Code: c3 0f 1f 40 00 55 89 f8 48 89 e5 e6 70 e4 71 5d c3 0f 1f 40 00 55 89 f0 4 8 89 e5 e6 70 89 f8 e6 71 5d c3 66 90 55 48 89 e5 0f 31 <89> c0 48 c1 e2 20 48 09 c2 48 89 d0 5d c3 66 66 66 2e 0f 1f 84 [ 28.458326] AMD-Vi: Completion-Wait loop timed out [ 28.565522] AMD-Vi: Completion-Wait loop timed out [ 28.672707] AMD-Vi: Completion-Wait loop timed out [ 28.779909] AMD-Vi: Completion-Wait loop timed out [ 28.886441] AMD-Vi: Completion-Wait loop timed out [ 28.886491] pci 0000:00:00.2: irq 40 for MSI/MSI-X [ 28.886676] pci 0000:40:00.2: irq 41 for MSI/MSI-X [ 28.896427] AMD-Vi: Lazy IO/TLB flushing enabled (boot continues as normal) This may point towards either hardware or bios. But I do not know if this would have happened before I started getting problems with xen. --f46d04083f2de2024104d59bce34 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Hello,

I have a system running ubuntu12.10 with xen 4.1.3, which I b= elieve was recently upgraded from xen 4.1.2 via the normal ubuntu 'apt-= get upgrade' path. 2 AMD opteron 6134 cpus, supermicro H8DG6 motherboar= d.

Recently I noticed that AMD-Vi gets disabled at boot, which didn't = happen before.

From 'xm dmesg':

(XEN) Command line: = placeholder amd-iommu-debug iommu=3Dverbose iommu=3D1 apic=3Ddebug iommu_in= clusive_mapping=3D1
[...]
(XEN) IVHD Error: Conflicting IO-APIC 0x0 entries
(XEN) AMD-Vi:= Error initialization
(XEN) I/O virtualisation disabled

I noticed it when getting an error= upon trying to passthrough a PCI device. A month ago PCI passthru worked, = but I haven't tested in between so I cannot say exactly when the proble= m arose, if it has to do with the transit from 4.1.2 to 4.1.3 or not. IOMMU= is enabled in BIOS, of course.

Could it be a xen bug (I know that my system is somewhat unusual), a ol= d BIOS bug interacting with newer xen or an aqcuired hardware error? I'= ll of course provide more logs if needed.

Thanks,
Andreas




ADDENDUM:
Some additional debugging I did (maybe helpful= , maybe not):

If I boot a baremetal linux3.5 kernel, IOMMU seems to= enable as it should, but I get an "AMD-Vi: Completion-Wait loop timed= out" message in dmesg followed by a soft CPU lockup:

[=A0=A0=A0 1.152261] AMD-Vi: Enabling IOMMU at 0000:00:00.2 cap 0x40[=A0=A0=A0 1.226282] AMD-Vi: Enabling IOMMU at 0000:40:00.2 cap 0x40
[= =A0=A0=A0 1.333560] AMD-Vi: Completion-Wait loop timed out
[=A0=A0=A0 1.= 440835] AMD-Vi: Completion-Wait loop timed out

(last line repeated x 100ish)

[=A0=A0 28.425464] BUG: soft locku= p - CPU#11 stuck for 22s! [swapper/0:1]
[=A0=A0 28.425467] Modules linke= d in:
[=A0=A0 28.425471] CPU 11
[=A0=A0 28.425472] Modules linked in= :
[=A0=A0 28.425476]
[=A0=A0 28.425479] Pid: 1, comm: swapper/0 Not tainted 3.5.0-23-generic #35= -Ubuntu Supermicro H8DG6/H8DGi/H8DG6/H8DGi
[=A0=A0 28.425486] RIP: 0010:= [<ffffffff8101aff6>]=A0 [<ffffffff8101aff6>] native_read_tsc+0x= 6/0x20
[=A0=A0 28.425497] RSP: 0000:ffff880234855d10=A0 EFLAGS: 00000246
[=A0= =A0 28.425501] RAX: 00000000226cded8 RBX: 00000000ffffffff RCX: 00000000011= 8c4ae
[=A0=A0 28.425504] RDX: 0000000000000025 RSI: 0000000000000286 RDI= : 00000000000008ea
[=A0=A0 28.425507] RBP: ffff880234855d10 R08: 000000000000040a R09: 0000000= 000001ff0
[=A0=A0 28.425511] R10: 0720072007200720 R11: 0720072007200720= R12: ffffffff81e49c23
[=A0=A0 28.425514] R13: 0000000000000246 R14: fff= f880234855cf0 R15: 0000000000000006
[=A0=A0 28.425517] FS:=A0 0000000000000000(0000) GS:ffff88083fcc0000(0000) = knlGS:0000000000000000
[=A0=A0 28.425521] CS:=A0 0010 DS: 0000 ES: 0000 = CR0: 000000008005003b
[=A0=A0 28.425524] CR2: 0000000000000000 CR3: 0000= 000001c0b000 CR4: 00000000000007e0
[=A0=A0 28.425527] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000= 000000000
[=A0=A0 28.425531] DR3: 0000000000000000 DR6: 00000000ffff0ff0= DR7: 0000000000000400
[=A0=A0 28.425534] Process swapper/0 (pid: 1, thr= eadinfo ffff880234854000, task ffff880234858000)
[=A0=A0 28.425538] Stack:
[=A0=A0 28.425540]=A0 ffff880234855d40 fffffff= f8133599a 0000000000010ef6 ffff880234855d98
[=A0=A0 28.425547]=A0 000000= 0000000286 0000000000002000 ffff880234855d50 ffffffff813358cc
[=A0=A0 28= .425553]=A0 ffff880234855d70 ffffffff8154a7c5 ffff880434e4c800 ffff880434e4= c814
[=A0=A0 28.425559] Call Trace:
[=A0=A0 28.425566]=A0 [<ffffffff813359= 9a>] delay_tsc+0x4a/0x80
[=A0=A0 28.425570]=A0 [<ffffffff813358cc&= gt;] __const_udelay+0x2c/0x30
[=A0=A0 28.425577]=A0 [<ffffffff8154a7c= 5>] wait_on_sem+0x35/0x70
[=A0=A0 28.425582]=A0 [<ffffffff8154b493>] iommu_queue_command_sync+0= x83/0x140
[=A0=A0 28.425587]=A0 [<ffffffff8154b563>] iommu_queue_c= ommand+0x13/0x20
[=A0=A0 28.425592]=A0 [<ffffffff8154dd37>] iommu_= flush_all_caches+0xd7/0x100
[=A0=A0 28.425597]=A0 [<ffffffff8154ed90>] enable_iommus+0x250/0x360<= br>[=A0=A0 28.425605]=A0 [<ffffffff81cfc17e>] ? memblock_find_dma_res= erve+0x13d/0x13d
[=A0=A0 28.425611]=A0 [<ffffffff81d328ce>] amd_io= mmu_init_hardware+0x1f7/0x231
[=A0=A0 28.425616]=A0 [<ffffffff81d32913>] amd_iommu_init+0xb/0x8b[=A0=A0 28.425620]=A0 [<ffffffff81cfc191>] pci_iommu_init+0x13/0x3e<= br>[=A0=A0 28.425627]=A0 [<ffffffff8100212a>] do_one_initcall+0x12a/0= x180
[=A0=A0 28.425631]=A0 [<ffffffff81cf3d3a>] kernel_init+0x140/= 0x1c9
[=A0=A0 28.425635]=A0 [<ffffffff81cf3588>] ? loglevel+0x31/0x31
[= =A0=A0 28.425642]=A0 [<ffffffff8168ce64>] kernel_thread_helper+0x4/0x= 10
[=A0=A0 28.425646]=A0 [<ffffffff81cf3bfa>] ? start_kernel+0x3d2= /0x3d2
[=A0=A0 28.425650]=A0 [<ffffffff8168ce60>] ? gs_change+0x13= /0x13
[=A0=A0 28.425652] Code: c3 0f 1f 40 00 55 89 f8 48 89 e5 e6 70 e4 71 5d c3= 0f 1f 40 00 55 89 f0 4
8 89 e5 e6 70 89 f8 e6 71 5d c3 66 90 55 48 89 e= 5 0f 31 <89> c0 48 c1 e2 20 48 09 c2 48 89 d0
5d c3 66 66 66 2e 0= f 1f 84
[=A0=A0 28.458326] AMD-Vi: Completion-Wait loop timed out
[=A0=A0 28.565= 522] AMD-Vi: Completion-Wait loop timed out
[=A0=A0 28.672707] AMD-Vi: C= ompletion-Wait loop timed out
[=A0=A0 28.779909] AMD-Vi: Completion-Wait= loop timed out
[=A0=A0 28.886441] AMD-Vi: Completion-Wait loop timed out
[=A0=A0 28.886= 491] pci 0000:00:00.2: irq 40 for MSI/MSI-X
[=A0=A0 28.886676] pci 0000:= 40:00.2: irq 41 for MSI/MSI-X
[=A0=A0 28.896427] AMD-Vi: Lazy IO/TLB flu= shing enabled

(boot continues as normal)

This may point towards either hardwar= e or bios. But I do not know if this would have happened before I started g= etting problems with xen.
--f46d04083f2de2024104d59bce34-- --===============1818140942270693756== 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 --===============1818140942270693756==-- From xen-users-bounces@lists.xen.org Wed Feb 13 16:52:39 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 13 Feb 2013 16:52: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 1U5fYJ-0001lh-VE; Wed, 13 Feb 2013 16:51:23 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U5fYH-0001lH-VA; Wed, 13 Feb 2013 16:51:22 +0000 Received: from [85.158.143.35:32056] by server-3.bemta-4.messagelabs.com id 66/97-08920-984CB115; Wed, 13 Feb 2013 16:51:21 +0000 X-Env-Sender: iwj@xenbits.xen.org X-Msg-Ref: server-10.tower-21.messagelabs.com!1360774248!10193618!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.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 14092 invoked from network); 13 Feb 2013 16:50:50 -0000 Received: from mail.xen.org (HELO mail.xen.org) (50.57.168.107) by server-10.tower-21.messagelabs.com with AES256-SHA encrypted SMTP; 13 Feb 2013 16:50:50 -0000 Received: from xenbits.xen.org ([50.57.170.242]) by mail.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U5fXd-0000EK-Hh; Wed, 13 Feb 2013 16:50:41 +0000 Received: from iwj by xenbits.xen.org with local (Exim 4.72) (envelope-from ) id 1U5fXd-0004ML-2n; Wed, 13 Feb 2013 16:50:41 +0000 Date: Wed, 13 Feb 2013 16:50: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 Cc: "Xen.org security team" Subject: [Xen-users] Xen Security Advisory 42 (CVE-2013-0228) - Linux kernel hits general protection if %ds is corrupt for 32-bit PVOPS. X-BeenThere: xen-users@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-2013-0228 / XSA-42 version 2 Linux kernel hits general protection if %ds is corrupt for 32-bit PVOPS. UPDATES IN VERSION 2 ==================== Public release. ISSUE DESCRIPTION ================= Linux kernel when returning from an iret assumes that %ds segment is safe and uses it to reference various per-cpu related fields. Unfortunately the user can modify the LDT and provide a NULL one. Whenever an iret is called we end up in xen_iret and try to use the %ds segment and cause an general protection fault. IMPACT ====== Malicious or buggy unprivileged user space can cause the guest kernel to crash, or permit a privilege escalation within the guest, or operate erroneously. VULNERABLE SYSTEMS ================== All 32bit PVOPS versions of Linux are affected, since the introduction of Xen PVOPS support in 2.6.23. Classic-Xen kernels are not vulnerable. MITIGATION ========== This can be mitigated by not running 32bit PVOPS Linux guests. 32bit classic-Xen guests, all 64bit PV guests and all HVM guests are unaffected. RESOLUTION ========== Applying the appropriate attached patch resolves this issue. $ sha256sum xsa42*.patch a931fdc161653fb1a3a6d8c1cf6d2c9954c5aec134b610be6e9699552a659eb8 xsa42-pvops-0001-x86-xen-don-t-assume-ds-is-usable-in-xen_iret-for-32.patch $ -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) iQEcBAEBAgAGBQJRG8PxAAoJEIP+FMlX6CvZC3gH/0v/9nr3jXbsMHZlkBRtCx9n np1ed8btQGpmmk/WqbyLj/KcTNlXLIa1zwhTSPUgXlVIoDPuzstfGXm96gBNfYhS hl56QYTruhHPAvvrAwE8SNIlMUH+n7Wq1BThkXFU1yBnjXxzTi4SdmUwy4gAA/SE Xp35RAcIV6IwLRMMY12aat7XKnVx4S5n+gCC5eu0WZ+n73Ecrlqmsq+2X2ZHo3wP nu9UN+PChmBJHfcA8OhelY/X4X4DV1HNPuFkj9ypyPrvXIrl6M0D5TfGoyRNXMHq izAn51ro8gTGND6xY+s3auelquKiJkyl/5AXnfd0y9bSewGJS6oxoRzFdctJqxM= =mgHb -----END PGP SIGNATURE----- --=separator Content-Type: application/octet-stream; name="xsa42-pvops-0001-x86-xen-don-t-assume-ds-is-usable-in-xen_iret-for-32.patch" Content-Disposition: attachment; filename="xsa42-pvops-0001-x86-xen-don-t-assume-ds-is-usable-in-xen_iret-for-32.patch" Content-Transfer-Encoding: base64 RnJvbSA5OGUwODljNWYyM2IzNmRiNDE1ZDBhNGMzODU0ZTk2OWM3YTRlY2Zh IE1vbiBTZXAgMTcgMDA6MDA6MDAgMjAwMQpGcm9tOiBKYW4gQmV1bGljaCA8 SkJldWxpY2hAc3VzZS5jb20+CkRhdGU6IFRodSwgMjQgSmFuIDIwMTMgMTM6 MTE6MTAgKzAwMDAKU3ViamVjdDogW1BBVENIXSB4ODYveGVuOiBkb24ndCBh c3N1bWUgJWRzIGlzIHVzYWJsZSBpbiB4ZW5faXJldCBmb3IgMzItYml0CiBQ Vk9QUy4KClRoaXMgZml4ZXMgQ1ZFLTIwMTMtMDIyOCAvIFhTQS00MgoKRHJl dyBKb25lcyB3aGlsZSB3b3JraW5nIG9uIENWRS0yMDEzLTAxOTAgZm91bmQg dGhhdCB0aGF0IHVucHJpdmlsZWdlZCBndWVzdCB1c2VyCmluIDMyYml0IFBW IGd1ZXN0IGNhbiB1c2UgdG8gY3Jhc2ggdGhlID4gZ3Vlc3Qgd2l0aCB0aGUg cGFuaWMgbGlrZSB0aGlzOgoKLS0tLS0tLS0tLS0tLQpnZW5lcmFsIHByb3Rl Y3Rpb24gZmF1bHQ6IDAwMDAgWyMxXSBTTVAKbGFzdCBzeXNmcyBmaWxlOiAv c3lzL2RldmljZXMvdmJkLTUxNzEyL2Jsb2NrL3h2ZGEvZGV2Ck1vZHVsZXMg bGlua2VkIGluOiBzdW5ycGMgaXB0X1JFSkVDVCBuZl9jb25udHJhY2tfaXB2 NCBuZl9kZWZyYWdfaXB2NAppcHRhYmxlX2ZpbHRlciBpcF90YWJsZXMgaXA2 dF9SRUpFQ1QgbmZfY29ubnRyYWNrX2lwdjYgbmZfZGVmcmFnX2lwdjYKeHRf c3RhdGUgbmZfY29ubnRyYWNrIGlwNnRhYmxlX2ZpbHRlciBpcDZfdGFibGVz IGlwdjYgeGVuX25ldGZyb250IGV4dDQKbWJjYWNoZSBqYmQyIHhlbl9ibGtm cm9udCBkbV9taXJyb3IgZG1fcmVnaW9uX2hhc2ggZG1fbG9nIGRtX21vZCBb bGFzdAp1bmxvYWRlZDogc2NzaV93YWl0X3NjYW5dCgpQaWQ6IDEyNTAsIGNv bW06IHIgTm90IHRhaW50ZWQgMi42LjMyLTM1Ni5lbDYuaTY4NiAjMQpFSVA6 IDAwNjE6WzxjMDQwNzQ2Mj5dIEVGTEFHUzogMDAwMTAwODYgQ1BVOiAwCkVJ UCBpcyBhdCB4ZW5faXJldCsweDEyLzB4MmIKRUFYOiBlYjhkMDAwMCBFQlg6 IDAwMDAwMDAxIEVDWDogMDgwNDk4NjAgRURYOiAwMDAwMDAxMApFU0k6IDAw MDAwMDAwIEVESTogMDAzZDBmMDAgRUJQOiBiNzdmODM4OCBFU1A6IGViOGQx ZmUwCiBEUzogMDAwMCBFUzogMDA3YiBGUzogMDAwMCBHUzogMDBlMCBTUzog MDA2OQpQcm9jZXNzIHIgKHBpZDogMTI1MCwgdGk9ZWI4ZDAwMDAgdGFzaz1j Mjk1MzU1MCB0YXNrLnRpPWViOGQwMDAwKQpTdGFjazoKIDAwMDAwMDAwIDAw MjdmNDE2IDAwMDAwMDczIDAwMDAwMjA2IGI3N2Y4MzY0IDAwMDAwMDdiIDAw MDAwMDAwIDAwMDAwMDAwCkNhbGwgVHJhY2U6CkNvZGU6IGMzIDhiIDQ0IDI0 IDE4IDgxIDRjIDI0IDM4IDAwIDAyIDAwIDAwIDhkIDY0IDI0IDMwIGU5IDAz IDAwIDAwIDAwCjhkIDc2IDAwIGY3IDQ0IDI0IDA4IDAwIDAwIDAyIDgwIDc1 IDMzIDUwIGI4IDAwIGUwIGZmIGZmIDIxIGUwIDw4Yj4gNDAKMTAgOGIgMDQg ODUgYTAgZjYgYWIgYzAgOGIgODAgMGMgYjAgYjMgYzAgZjYgNDQgMjQgMGQg MDIKRUlQOiBbPGMwNDA3NDYyPl0geGVuX2lyZXQrMHgxMi8weDJiIFNTOkVT UCAwMDY5OmViOGQxZmUwCmdlbmVyYWwgcHJvdGVjdGlvbiBmYXVsdDogMDAw MCBbIzJdCi0tLVsgZW5kIHRyYWNlIGFiMGQyOWE0OTJkY2QzMzAgXS0tLQpL ZXJuZWwgcGFuaWMgLSBub3Qgc3luY2luZzogRmF0YWwgZXhjZXB0aW9uClBp ZDogMTI1MCwgY29tbTogciBUYWludGVkOiBHICAgICAgRCAgICAtLS0tLS0t LS0tLS0tLS0KMi42LjMyLTM1Ni5lbDYuaTY4NiAjMQpDYWxsIFRyYWNlOgog WzxjMDg0NzZkZj5dID8gcGFuaWMrMHg2ZS8weDEyMgogWzxjMDg0YjYzYz5d ID8gb29wc19lbmQrMHhiYy8weGQwCiBbPGMwODRiMjYwPl0gPyBkb19nZW5l cmFsX3Byb3RlY3Rpb24rMHgwLzB4MjEwCiBbPGMwODRhOWI3Pl0gPyBlcnJv cl9jb2RlKzB4NzMvCi0tLS0tLS0tLS0tLS0KClBldHIgc2F5czogIgogSSd2 ZSBhbmFseXNlZCB0aGUgYnVnIGFuZCBJIHRoaW5rIHRoYXQgeGVuX2lyZXQo KSBjYW5ub3QgY29wZSB3aXRoCiBtYW5nbGVkIERTLCBpbiB0aGlzIGNhc2Ug emVyb2VkIG91dCAobnVsbCBzZWxlY3Rvci9kZXNjcmlwdG9yKSBieSBlaXRo ZXIKIHhlbl9mYWlsc2FmZV9jYWxsYmFjaygpIG9yIFJFU1RPUkVfUkVHUyBi ZWNhdXNlIHRoZSBjb3JyZXNwb25kaW5nIExEVAogZW50cnkgd2FzIGludmFs aWRhdGVkIGJ5IHRoZSByZXByb2R1Y2VyLiAiCgpKYW4gdG9vayBhIGxvb2sg YXQgdGhlIHByZWxpbWluYXJ5IHBhdGNoIGFuZCBjYW1lIHVwIGEgZml4IHRo YXQgc29sdmVzCnRoaXMgcHJvYmxlbToKCiJUaGlzIGNvZGUgZ2V0cyBjYWxs ZWQgYWZ0ZXIgYWxsIHJlZ2lzdGVycyBvdGhlciB0aGFuIHRob3NlIGhhbmRs ZWQgYnkKSVJFVCBnb3QgYWxyZWFkeSByZXN0b3JlZCwgaGVuY2UgYSBudWxs IHNlbGVjdG9yIGluICVkcyBvciBhIG5vbi1udWxsCm9uZSB0aGF0IGdvdCBs b2FkZWQgZnJvbSBhIGNvZGUgb3IgcmVhZC1vbmx5IGRhdGEgZGVzY3JpcHRv ciB3b3VsZApjYXVzZSBhIGtlcm5lbCBtb2RlIGZhdWx0ICh3aXRoIHRoZSBw b3RlbnRpYWwgb2YgY3Jhc2hpbmcgdGhlIGtlcm5lbAphcyBhIHdob2xlLCBp ZiBwYW5pY19vbl9vb3BzIGlzIHNldCkuIgoKVGhlIHdheSB0byBmaXggdGhp cyBpcyB0byByZWFsaXplIHRoYXQgdGhlIHdlIGNhbiBvbmx5IHJlbGF5IG9u IHRoZQpyZWdpc3RlcnMgdGhhdCBJUkVUIHJlc3RvcmVzLiBUaGUgdHdvIHRo YXQgYXJlIGd1YXJhbnRlZWQgYXJlIHRoZQolY3MgYW5kICVzcyBhcyB0aGV5 IGFyZSBhbHdheXMgZml4ZWQgR0RUIHNlbGVjdG9ycy4gQWxzbyB0aGV5IGFy ZQppbmFjY2Vzc2libGUgZnJvbSB1c2VyIG1vZGUgLSBzbyB0aGV5IGNhbm5v dCBiZSBhbHRlcmVkLiBUaGlzIGlzCnRoZSBhcHByb2FjaCB0YWtlbiBpbiB0 aGlzIHBhdGNoLgoKQW5vdGhlciBhbHRlcm5hdGl2ZSBvcHRpb24gc3VnZ2Vz dGVkIGJ5IEphbiB3b3VsZCBiZSB0byByZWxheSBvbgp0aGUgc3VidGxlIHJl YWxpemF0aW9uIHRoYXQgdXNpbmcgdGhlICVlYnAgb3IgJWVzcCByZWxhdGl2 ZSByZWZlcmVuY2VzIHVzZXMKdGhlICVzcyBzZWdtZW50LiAgSW4gd2hpY2gg Y2FzZSB3ZSBjb3VsZCBzd2l0Y2ggZnJvbSB1c2luZyAlZWF4IHRvICVlYnAg YW5kCndvdWxkIG5vdCBuZWVkIHRoZSAlc3Mgb3Zlci1yaWRlcy4gVGhhdCB3 b3VsZCBhbHNvIHJlcXVpcmUgb25lIGV4dHJhCmluc3RydWN0aW9uIHRvIGNv bXBlbnNhdGUgZm9yIHRoZSBvbmUgcGxhY2Ugd2hlcmUgdGhlIHJlZ2lzdGVy IGlzIHVzZWQKYXMgc2NhbGVkIGluZGV4LiBIb3dldmVyIEFuZHJldyBwb2lu dGVkIG91dCB0aGF0IGlzIHRvbyBzdWJ0bGUgYW5kIGlmCmZ1cnRoZXIgd29y ayB3YXMgdG8gYmUgZG9uZSBpbiB0aGlzIGNvZGUtcGF0aCBpdCBjb3VsZCBl c2NhcGUgZm9sa3MgYXR0ZW50aW9uCmFuZCBsZWFkIHRvIGFjY2lkZW50cy4K ClJldmlld2VkLWJ5OiBQZXRyIE1hdG91c2VrIDxwbWF0b3VzZUByZWRoYXQu Y29tPgpSZXBvcnRlZC1ieTogUGV0ciBNYXRvdXNlayA8cG1hdG91c2VAcmVk aGF0LmNvbT4KUmV2aWV3ZWQtYnk6IEFuZHJldyBDb29wZXIgPGFuZHJldy5j b29wZXIzQGNpdHJpeC5jb20+ClNpZ25lZC1vZmYtYnk6IEphbiBCZXVsaWNo IDxqYmV1bGljaEBzdXNlLmNvbT4KU2lnbmVkLW9mZi1ieTogS29ucmFkIFJ6 ZXN6dXRlayBXaWxrIDxrb25yYWQud2lsa0BvcmFjbGUuY29tPgotLS0KIGFy Y2gveDg2L3hlbi94ZW4tYXNtXzMyLlMgfCAxNCArKysrKysrLS0tLS0tLQog MSBmaWxlIGNoYW5nZWQsIDcgaW5zZXJ0aW9ucygrKSwgNyBkZWxldGlvbnMo LSkKCmRpZmYgLS1naXQgYS9hcmNoL3g4Ni94ZW4veGVuLWFzbV8zMi5TIGIv YXJjaC94ODYveGVuL3hlbi1hc21fMzIuUwppbmRleCBmOTY0M2ZjLi4zM2Nh NmU0IDEwMDY0NAotLS0gYS9hcmNoL3g4Ni94ZW4veGVuLWFzbV8zMi5TCisr KyBiL2FyY2gveDg2L3hlbi94ZW4tYXNtXzMyLlMKQEAgLTg5LDExICs4OSwx MSBAQCBFTlRSWSh4ZW5faXJldCkKIAkgKi8KICNpZmRlZiBDT05GSUdfU01Q CiAJR0VUX1RIUkVBRF9JTkZPKCVlYXgpCi0JbW92bCBUSV9jcHUoJWVheCks ICVlYXgKLQltb3ZsIF9fcGVyX2NwdV9vZmZzZXQoLCVlYXgsNCksICVlYXgK LQltb3YgeGVuX3ZjcHUoJWVheCksICVlYXgKKwltb3ZsICVzczpUSV9jcHUo JWVheCksICVlYXgKKwltb3ZsICVzczpfX3Blcl9jcHVfb2Zmc2V0KCwlZWF4 LDQpLCAlZWF4CisJbW92ICVzczp4ZW5fdmNwdSglZWF4KSwgJWVheAogI2Vs c2UKLQltb3ZsIHhlbl92Y3B1LCAlZWF4CisJbW92bCAlc3M6eGVuX3ZjcHUs ICVlYXgKICNlbmRpZgogCiAJLyogY2hlY2sgSUYgc3RhdGUgd2UncmUgcmVz dG9yaW5nICovCkBAIC0xMDYsMTEgKzEwNiwxMSBAQCBFTlRSWSh4ZW5faXJl dCkKIAkgKiByZXN1bWluZyB0aGUgY29kZSwgc28gd2UgZG9uJ3QgaGF2ZSB0 byBiZSB3b3JyaWVkIGFib3V0CiAJICogYmVpbmcgcHJlZW1wdGVkIHRvIGFu b3RoZXIgQ1BVLgogCSAqLwotCXNldHogWEVOX3ZjcHVfaW5mb19tYXNrKCVl YXgpCisJc2V0eiAlc3M6WEVOX3ZjcHVfaW5mb19tYXNrKCVlYXgpCiB4ZW5f aXJldF9zdGFydF9jcml0OgogCiAJLyogY2hlY2sgZm9yIHVubWFza2VkIGFu ZCBwZW5kaW5nICovCi0JY21wdyAkMHgwMDAxLCBYRU5fdmNwdV9pbmZvX3Bl bmRpbmcoJWVheCkKKwljbXB3ICQweDAwMDEsICVzczpYRU5fdmNwdV9pbmZv X3BlbmRpbmcoJWVheCkKIAogCS8qCiAJICogSWYgdGhlcmUncyBzb21ldGhp bmcgcGVuZGluZywgbWFzayBldmVudHMgYWdhaW4gc28gd2UgY2FuCkBAIC0x MTgsNyArMTE4LDcgQEAgeGVuX2lyZXRfc3RhcnRfY3JpdDoKIAkgKiB0b3Vj aCBYRU5fdmNwdV9pbmZvX21hc2suCiAJICovCiAJam5lIDFmCi0JbW92YiAk MSwgWEVOX3ZjcHVfaW5mb19tYXNrKCVlYXgpCisJbW92YiAkMSwgJXNzOlhF Tl92Y3B1X2luZm9fbWFzayglZWF4KQogCiAxOglwb3BsICVlYXgKIAotLSAK MS44LjAuMgoK --=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 Feb 13 16:52:39 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 13 Feb 2013 16:52: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 1U5fYJ-0001lh-VE; Wed, 13 Feb 2013 16:51:23 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U5fYH-0001lH-VA; Wed, 13 Feb 2013 16:51:22 +0000 Received: from [85.158.143.35:32056] by server-3.bemta-4.messagelabs.com id 66/97-08920-984CB115; Wed, 13 Feb 2013 16:51:21 +0000 X-Env-Sender: iwj@xenbits.xen.org X-Msg-Ref: server-10.tower-21.messagelabs.com!1360774248!10193618!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.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 14092 invoked from network); 13 Feb 2013 16:50:50 -0000 Received: from mail.xen.org (HELO mail.xen.org) (50.57.168.107) by server-10.tower-21.messagelabs.com with AES256-SHA encrypted SMTP; 13 Feb 2013 16:50:50 -0000 Received: from xenbits.xen.org ([50.57.170.242]) by mail.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U5fXd-0000EK-Hh; Wed, 13 Feb 2013 16:50:41 +0000 Received: from iwj by xenbits.xen.org with local (Exim 4.72) (envelope-from ) id 1U5fXd-0004ML-2n; Wed, 13 Feb 2013 16:50:41 +0000 Date: Wed, 13 Feb 2013 16:50: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 Cc: "Xen.org security team" Subject: [Xen-users] Xen Security Advisory 42 (CVE-2013-0228) - Linux kernel hits general protection if %ds is corrupt for 32-bit PVOPS. X-BeenThere: xen-users@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-2013-0228 / XSA-42 version 2 Linux kernel hits general protection if %ds is corrupt for 32-bit PVOPS. UPDATES IN VERSION 2 ==================== Public release. ISSUE DESCRIPTION ================= Linux kernel when returning from an iret assumes that %ds segment is safe and uses it to reference various per-cpu related fields. Unfortunately the user can modify the LDT and provide a NULL one. Whenever an iret is called we end up in xen_iret and try to use the %ds segment and cause an general protection fault. IMPACT ====== Malicious or buggy unprivileged user space can cause the guest kernel to crash, or permit a privilege escalation within the guest, or operate erroneously. VULNERABLE SYSTEMS ================== All 32bit PVOPS versions of Linux are affected, since the introduction of Xen PVOPS support in 2.6.23. Classic-Xen kernels are not vulnerable. MITIGATION ========== This can be mitigated by not running 32bit PVOPS Linux guests. 32bit classic-Xen guests, all 64bit PV guests and all HVM guests are unaffected. RESOLUTION ========== Applying the appropriate attached patch resolves this issue. $ sha256sum xsa42*.patch a931fdc161653fb1a3a6d8c1cf6d2c9954c5aec134b610be6e9699552a659eb8 xsa42-pvops-0001-x86-xen-don-t-assume-ds-is-usable-in-xen_iret-for-32.patch $ -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) iQEcBAEBAgAGBQJRG8PxAAoJEIP+FMlX6CvZC3gH/0v/9nr3jXbsMHZlkBRtCx9n np1ed8btQGpmmk/WqbyLj/KcTNlXLIa1zwhTSPUgXlVIoDPuzstfGXm96gBNfYhS hl56QYTruhHPAvvrAwE8SNIlMUH+n7Wq1BThkXFU1yBnjXxzTi4SdmUwy4gAA/SE Xp35RAcIV6IwLRMMY12aat7XKnVx4S5n+gCC5eu0WZ+n73Ecrlqmsq+2X2ZHo3wP nu9UN+PChmBJHfcA8OhelY/X4X4DV1HNPuFkj9ypyPrvXIrl6M0D5TfGoyRNXMHq izAn51ro8gTGND6xY+s3auelquKiJkyl/5AXnfd0y9bSewGJS6oxoRzFdctJqxM= =mgHb -----END PGP SIGNATURE----- --=separator Content-Type: application/octet-stream; name="xsa42-pvops-0001-x86-xen-don-t-assume-ds-is-usable-in-xen_iret-for-32.patch" Content-Disposition: attachment; filename="xsa42-pvops-0001-x86-xen-don-t-assume-ds-is-usable-in-xen_iret-for-32.patch" Content-Transfer-Encoding: base64 RnJvbSA5OGUwODljNWYyM2IzNmRiNDE1ZDBhNGMzODU0ZTk2OWM3YTRlY2Zh IE1vbiBTZXAgMTcgMDA6MDA6MDAgMjAwMQpGcm9tOiBKYW4gQmV1bGljaCA8 SkJldWxpY2hAc3VzZS5jb20+CkRhdGU6IFRodSwgMjQgSmFuIDIwMTMgMTM6 MTE6MTAgKzAwMDAKU3ViamVjdDogW1BBVENIXSB4ODYveGVuOiBkb24ndCBh c3N1bWUgJWRzIGlzIHVzYWJsZSBpbiB4ZW5faXJldCBmb3IgMzItYml0CiBQ Vk9QUy4KClRoaXMgZml4ZXMgQ1ZFLTIwMTMtMDIyOCAvIFhTQS00MgoKRHJl dyBKb25lcyB3aGlsZSB3b3JraW5nIG9uIENWRS0yMDEzLTAxOTAgZm91bmQg dGhhdCB0aGF0IHVucHJpdmlsZWdlZCBndWVzdCB1c2VyCmluIDMyYml0IFBW IGd1ZXN0IGNhbiB1c2UgdG8gY3Jhc2ggdGhlID4gZ3Vlc3Qgd2l0aCB0aGUg cGFuaWMgbGlrZSB0aGlzOgoKLS0tLS0tLS0tLS0tLQpnZW5lcmFsIHByb3Rl Y3Rpb24gZmF1bHQ6IDAwMDAgWyMxXSBTTVAKbGFzdCBzeXNmcyBmaWxlOiAv c3lzL2RldmljZXMvdmJkLTUxNzEyL2Jsb2NrL3h2ZGEvZGV2Ck1vZHVsZXMg bGlua2VkIGluOiBzdW5ycGMgaXB0X1JFSkVDVCBuZl9jb25udHJhY2tfaXB2 NCBuZl9kZWZyYWdfaXB2NAppcHRhYmxlX2ZpbHRlciBpcF90YWJsZXMgaXA2 dF9SRUpFQ1QgbmZfY29ubnRyYWNrX2lwdjYgbmZfZGVmcmFnX2lwdjYKeHRf c3RhdGUgbmZfY29ubnRyYWNrIGlwNnRhYmxlX2ZpbHRlciBpcDZfdGFibGVz IGlwdjYgeGVuX25ldGZyb250IGV4dDQKbWJjYWNoZSBqYmQyIHhlbl9ibGtm cm9udCBkbV9taXJyb3IgZG1fcmVnaW9uX2hhc2ggZG1fbG9nIGRtX21vZCBb bGFzdAp1bmxvYWRlZDogc2NzaV93YWl0X3NjYW5dCgpQaWQ6IDEyNTAsIGNv bW06IHIgTm90IHRhaW50ZWQgMi42LjMyLTM1Ni5lbDYuaTY4NiAjMQpFSVA6 IDAwNjE6WzxjMDQwNzQ2Mj5dIEVGTEFHUzogMDAwMTAwODYgQ1BVOiAwCkVJ UCBpcyBhdCB4ZW5faXJldCsweDEyLzB4MmIKRUFYOiBlYjhkMDAwMCBFQlg6 IDAwMDAwMDAxIEVDWDogMDgwNDk4NjAgRURYOiAwMDAwMDAxMApFU0k6IDAw MDAwMDAwIEVESTogMDAzZDBmMDAgRUJQOiBiNzdmODM4OCBFU1A6IGViOGQx ZmUwCiBEUzogMDAwMCBFUzogMDA3YiBGUzogMDAwMCBHUzogMDBlMCBTUzog MDA2OQpQcm9jZXNzIHIgKHBpZDogMTI1MCwgdGk9ZWI4ZDAwMDAgdGFzaz1j Mjk1MzU1MCB0YXNrLnRpPWViOGQwMDAwKQpTdGFjazoKIDAwMDAwMDAwIDAw MjdmNDE2IDAwMDAwMDczIDAwMDAwMjA2IGI3N2Y4MzY0IDAwMDAwMDdiIDAw MDAwMDAwIDAwMDAwMDAwCkNhbGwgVHJhY2U6CkNvZGU6IGMzIDhiIDQ0IDI0 IDE4IDgxIDRjIDI0IDM4IDAwIDAyIDAwIDAwIDhkIDY0IDI0IDMwIGU5IDAz IDAwIDAwIDAwCjhkIDc2IDAwIGY3IDQ0IDI0IDA4IDAwIDAwIDAyIDgwIDc1 IDMzIDUwIGI4IDAwIGUwIGZmIGZmIDIxIGUwIDw4Yj4gNDAKMTAgOGIgMDQg ODUgYTAgZjYgYWIgYzAgOGIgODAgMGMgYjAgYjMgYzAgZjYgNDQgMjQgMGQg MDIKRUlQOiBbPGMwNDA3NDYyPl0geGVuX2lyZXQrMHgxMi8weDJiIFNTOkVT UCAwMDY5OmViOGQxZmUwCmdlbmVyYWwgcHJvdGVjdGlvbiBmYXVsdDogMDAw MCBbIzJdCi0tLVsgZW5kIHRyYWNlIGFiMGQyOWE0OTJkY2QzMzAgXS0tLQpL ZXJuZWwgcGFuaWMgLSBub3Qgc3luY2luZzogRmF0YWwgZXhjZXB0aW9uClBp ZDogMTI1MCwgY29tbTogciBUYWludGVkOiBHICAgICAgRCAgICAtLS0tLS0t LS0tLS0tLS0KMi42LjMyLTM1Ni5lbDYuaTY4NiAjMQpDYWxsIFRyYWNlOgog WzxjMDg0NzZkZj5dID8gcGFuaWMrMHg2ZS8weDEyMgogWzxjMDg0YjYzYz5d ID8gb29wc19lbmQrMHhiYy8weGQwCiBbPGMwODRiMjYwPl0gPyBkb19nZW5l cmFsX3Byb3RlY3Rpb24rMHgwLzB4MjEwCiBbPGMwODRhOWI3Pl0gPyBlcnJv cl9jb2RlKzB4NzMvCi0tLS0tLS0tLS0tLS0KClBldHIgc2F5czogIgogSSd2 ZSBhbmFseXNlZCB0aGUgYnVnIGFuZCBJIHRoaW5rIHRoYXQgeGVuX2lyZXQo KSBjYW5ub3QgY29wZSB3aXRoCiBtYW5nbGVkIERTLCBpbiB0aGlzIGNhc2Ug emVyb2VkIG91dCAobnVsbCBzZWxlY3Rvci9kZXNjcmlwdG9yKSBieSBlaXRo ZXIKIHhlbl9mYWlsc2FmZV9jYWxsYmFjaygpIG9yIFJFU1RPUkVfUkVHUyBi ZWNhdXNlIHRoZSBjb3JyZXNwb25kaW5nIExEVAogZW50cnkgd2FzIGludmFs aWRhdGVkIGJ5IHRoZSByZXByb2R1Y2VyLiAiCgpKYW4gdG9vayBhIGxvb2sg YXQgdGhlIHByZWxpbWluYXJ5IHBhdGNoIGFuZCBjYW1lIHVwIGEgZml4IHRo YXQgc29sdmVzCnRoaXMgcHJvYmxlbToKCiJUaGlzIGNvZGUgZ2V0cyBjYWxs ZWQgYWZ0ZXIgYWxsIHJlZ2lzdGVycyBvdGhlciB0aGFuIHRob3NlIGhhbmRs ZWQgYnkKSVJFVCBnb3QgYWxyZWFkeSByZXN0b3JlZCwgaGVuY2UgYSBudWxs IHNlbGVjdG9yIGluICVkcyBvciBhIG5vbi1udWxsCm9uZSB0aGF0IGdvdCBs b2FkZWQgZnJvbSBhIGNvZGUgb3IgcmVhZC1vbmx5IGRhdGEgZGVzY3JpcHRv ciB3b3VsZApjYXVzZSBhIGtlcm5lbCBtb2RlIGZhdWx0ICh3aXRoIHRoZSBw b3RlbnRpYWwgb2YgY3Jhc2hpbmcgdGhlIGtlcm5lbAphcyBhIHdob2xlLCBp ZiBwYW5pY19vbl9vb3BzIGlzIHNldCkuIgoKVGhlIHdheSB0byBmaXggdGhp cyBpcyB0byByZWFsaXplIHRoYXQgdGhlIHdlIGNhbiBvbmx5IHJlbGF5IG9u IHRoZQpyZWdpc3RlcnMgdGhhdCBJUkVUIHJlc3RvcmVzLiBUaGUgdHdvIHRo YXQgYXJlIGd1YXJhbnRlZWQgYXJlIHRoZQolY3MgYW5kICVzcyBhcyB0aGV5 IGFyZSBhbHdheXMgZml4ZWQgR0RUIHNlbGVjdG9ycy4gQWxzbyB0aGV5IGFy ZQppbmFjY2Vzc2libGUgZnJvbSB1c2VyIG1vZGUgLSBzbyB0aGV5IGNhbm5v dCBiZSBhbHRlcmVkLiBUaGlzIGlzCnRoZSBhcHByb2FjaCB0YWtlbiBpbiB0 aGlzIHBhdGNoLgoKQW5vdGhlciBhbHRlcm5hdGl2ZSBvcHRpb24gc3VnZ2Vz dGVkIGJ5IEphbiB3b3VsZCBiZSB0byByZWxheSBvbgp0aGUgc3VidGxlIHJl YWxpemF0aW9uIHRoYXQgdXNpbmcgdGhlICVlYnAgb3IgJWVzcCByZWxhdGl2 ZSByZWZlcmVuY2VzIHVzZXMKdGhlICVzcyBzZWdtZW50LiAgSW4gd2hpY2gg Y2FzZSB3ZSBjb3VsZCBzd2l0Y2ggZnJvbSB1c2luZyAlZWF4IHRvICVlYnAg YW5kCndvdWxkIG5vdCBuZWVkIHRoZSAlc3Mgb3Zlci1yaWRlcy4gVGhhdCB3 b3VsZCBhbHNvIHJlcXVpcmUgb25lIGV4dHJhCmluc3RydWN0aW9uIHRvIGNv bXBlbnNhdGUgZm9yIHRoZSBvbmUgcGxhY2Ugd2hlcmUgdGhlIHJlZ2lzdGVy IGlzIHVzZWQKYXMgc2NhbGVkIGluZGV4LiBIb3dldmVyIEFuZHJldyBwb2lu dGVkIG91dCB0aGF0IGlzIHRvbyBzdWJ0bGUgYW5kIGlmCmZ1cnRoZXIgd29y ayB3YXMgdG8gYmUgZG9uZSBpbiB0aGlzIGNvZGUtcGF0aCBpdCBjb3VsZCBl c2NhcGUgZm9sa3MgYXR0ZW50aW9uCmFuZCBsZWFkIHRvIGFjY2lkZW50cy4K ClJldmlld2VkLWJ5OiBQZXRyIE1hdG91c2VrIDxwbWF0b3VzZUByZWRoYXQu Y29tPgpSZXBvcnRlZC1ieTogUGV0ciBNYXRvdXNlayA8cG1hdG91c2VAcmVk aGF0LmNvbT4KUmV2aWV3ZWQtYnk6IEFuZHJldyBDb29wZXIgPGFuZHJldy5j b29wZXIzQGNpdHJpeC5jb20+ClNpZ25lZC1vZmYtYnk6IEphbiBCZXVsaWNo IDxqYmV1bGljaEBzdXNlLmNvbT4KU2lnbmVkLW9mZi1ieTogS29ucmFkIFJ6 ZXN6dXRlayBXaWxrIDxrb25yYWQud2lsa0BvcmFjbGUuY29tPgotLS0KIGFy Y2gveDg2L3hlbi94ZW4tYXNtXzMyLlMgfCAxNCArKysrKysrLS0tLS0tLQog MSBmaWxlIGNoYW5nZWQsIDcgaW5zZXJ0aW9ucygrKSwgNyBkZWxldGlvbnMo LSkKCmRpZmYgLS1naXQgYS9hcmNoL3g4Ni94ZW4veGVuLWFzbV8zMi5TIGIv YXJjaC94ODYveGVuL3hlbi1hc21fMzIuUwppbmRleCBmOTY0M2ZjLi4zM2Nh NmU0IDEwMDY0NAotLS0gYS9hcmNoL3g4Ni94ZW4veGVuLWFzbV8zMi5TCisr KyBiL2FyY2gveDg2L3hlbi94ZW4tYXNtXzMyLlMKQEAgLTg5LDExICs4OSwx MSBAQCBFTlRSWSh4ZW5faXJldCkKIAkgKi8KICNpZmRlZiBDT05GSUdfU01Q CiAJR0VUX1RIUkVBRF9JTkZPKCVlYXgpCi0JbW92bCBUSV9jcHUoJWVheCks ICVlYXgKLQltb3ZsIF9fcGVyX2NwdV9vZmZzZXQoLCVlYXgsNCksICVlYXgK LQltb3YgeGVuX3ZjcHUoJWVheCksICVlYXgKKwltb3ZsICVzczpUSV9jcHUo JWVheCksICVlYXgKKwltb3ZsICVzczpfX3Blcl9jcHVfb2Zmc2V0KCwlZWF4 LDQpLCAlZWF4CisJbW92ICVzczp4ZW5fdmNwdSglZWF4KSwgJWVheAogI2Vs c2UKLQltb3ZsIHhlbl92Y3B1LCAlZWF4CisJbW92bCAlc3M6eGVuX3ZjcHUs ICVlYXgKICNlbmRpZgogCiAJLyogY2hlY2sgSUYgc3RhdGUgd2UncmUgcmVz dG9yaW5nICovCkBAIC0xMDYsMTEgKzEwNiwxMSBAQCBFTlRSWSh4ZW5faXJl dCkKIAkgKiByZXN1bWluZyB0aGUgY29kZSwgc28gd2UgZG9uJ3QgaGF2ZSB0 byBiZSB3b3JyaWVkIGFib3V0CiAJICogYmVpbmcgcHJlZW1wdGVkIHRvIGFu b3RoZXIgQ1BVLgogCSAqLwotCXNldHogWEVOX3ZjcHVfaW5mb19tYXNrKCVl YXgpCisJc2V0eiAlc3M6WEVOX3ZjcHVfaW5mb19tYXNrKCVlYXgpCiB4ZW5f aXJldF9zdGFydF9jcml0OgogCiAJLyogY2hlY2sgZm9yIHVubWFza2VkIGFu ZCBwZW5kaW5nICovCi0JY21wdyAkMHgwMDAxLCBYRU5fdmNwdV9pbmZvX3Bl bmRpbmcoJWVheCkKKwljbXB3ICQweDAwMDEsICVzczpYRU5fdmNwdV9pbmZv X3BlbmRpbmcoJWVheCkKIAogCS8qCiAJICogSWYgdGhlcmUncyBzb21ldGhp bmcgcGVuZGluZywgbWFzayBldmVudHMgYWdhaW4gc28gd2UgY2FuCkBAIC0x MTgsNyArMTE4LDcgQEAgeGVuX2lyZXRfc3RhcnRfY3JpdDoKIAkgKiB0b3Vj aCBYRU5fdmNwdV9pbmZvX21hc2suCiAJICovCiAJam5lIDFmCi0JbW92YiAk MSwgWEVOX3ZjcHVfaW5mb19tYXNrKCVlYXgpCisJbW92YiAkMSwgJXNzOlhF Tl92Y3B1X2luZm9fbWFzayglZWF4KQogCiAxOglwb3BsICVlYXgKIAotLSAK MS44LjAuMgoK --=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 Feb 14 02:45:29 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 14 Feb 2013 02:45: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 1U5onj-0001B1-Ra; Thu, 14 Feb 2013 02:43:55 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U5dxz-0006ej-Mp for xen-users@lists.xen.org; Wed, 13 Feb 2013 15:09:47 +0000 Received: from [193.109.254.147:41690] by server-6.bemta-14.messagelabs.com id 69/F8-12010-BBCAB115; Wed, 13 Feb 2013 15:09:47 +0000 X-Env-Sender: cocopyaach@yahoo.com X-Msg-Ref: server-12.tower-27.messagelabs.com!1360768163!9176412!1 X-Originating-IP: [98.139.213.164] X-SpamReason: No, hits=0.6 required=7.0 tests=BODY_RANDOM_LONG, HTML_30_40, HTML_MESSAGE, ML_RADAR_SPEW_LINKS_12, ML_RADAR_SPEW_LINKS_14, ML_RADAR_SPEW_LINKS_6,ML_RADAR_SPEW_LINKS_8,spamassassin: , async_handler: YXN5bmNfZGVsYXk6IDcwNTk4NTcgKHRpbWVvdXQp\n X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 30068 invoked from network); 13 Feb 2013 15:09:24 -0000 Received: from nm14-vm0.bullet.mail.bf1.yahoo.com (HELO nm14-vm0.bullet.mail.bf1.yahoo.com) (98.139.213.164) by server-12.tower-27.messagelabs.com with SMTP; 13 Feb 2013 15:09:24 -0000 Received: from [98.139.212.152] by nm14.bullet.mail.bf1.yahoo.com with NNFMP; 13 Feb 2013 15:09:23 -0000 Received: from [98.139.212.212] by tm9.bullet.mail.bf1.yahoo.com with NNFMP; 13 Feb 2013 15:09:23 -0000 Received: from [127.0.0.1] by omp1021.mail.bf1.yahoo.com with NNFMP; 13 Feb 2013 15:09:23 -0000 X-Yahoo-Newman-Property: ymail-3 X-Yahoo-Newman-Id: 52683.68381.bm@omp1021.mail.bf1.yahoo.com Received: (qmail 19309 invoked by uid 60001); 13 Feb 2013 15:09:23 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1360768162; bh=UP0p2Z/p8x1SLZfil8bUrnIzJtT+gca9DULg8/nESWQ=; h=X-YMail-OSG:Received:X-Rocket-MIMEInfo:X-Mailer:Message-ID:Date:From:Subject:To:MIME-Version:Content-Type; b=PEuUA0a63de0F0jEse0Z/LvwWEI7PU1RlDhAG7ZL4M0wuNQplcOUdzFTluOwe1LegMXTBGQ6Uu+CkQHSOH9n+iwsXt8DWm444UoHprQxdoG0W9pXfqD/l21I83ZafjL2xIBh+yIpM4+yRxh2mhPEzEfXxvu03Cd7JfWuRYuDF4k= DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=X-YMail-OSG:Received:X-Rocket-MIMEInfo:X-Mailer:Message-ID:Date:From:Subject:To:MIME-Version:Content-Type; b=2q+ysea5oY9tcE54ucEd53AGZfZ4N1wFecK6Mu3joe/blWfdGa7mGlUSRkml0LF7rYDS8NvDbzT2UAUY27IJhNBrYpII4tQ4TB2VQNraKuGv1nIIGFcPm01IJPenU+vGFwkEJ9GS+X6wu8R/nCv5VuuF38fBs+KpdkCEaJvOVWA=; X-YMail-OSG: Q.X6L7cVM1kTPnUGxm4r_B8l51yNNuXH5aOSan8zPYujGhz Bbn8p2ctaihcjNhbkaDGk0zJCtk5L.2k7F8DnjneY1hwrHFGoTLhvcvDbKjH cGDNwQLoeR6WymibgiJqaH.08rG7WhGU7B06iXbPGDRFWvCcYNMme2EK3PJt 2N6sBu5nNW1fWAtpw4TI6GiaMZQnjAhsf2Y1a6OTzoMzy7RRd2c39nV2ntgh 8rxM1uSCfcqe353Z4ac_eT_o.99Enm5E.PSX17QCs70FtjRGBAcpVdFMG0kI Df31byaQ8k41B6FmIoHKbpWNzotJd0Hn8XLp91QVViTsBVFspM_DLl_DfItS d6dv_dRdWxpujbe._XWBG8FDk2oJxOZD7pgDtrFaUtdtsl_xm41PLnQQLY91 vxSA8VHRxbiQ5DZSGvKrsC3PkQC9CyhHRc2J7TlR1EKzX97ts1v1EKtbftXD 6PE_kbGmGukMHWbqNJlcB9q2byF36idlqJJm1rPR0TyPdzu1mj1L7phRxYpe xGW6vqGEqsZw.KTtoIybYv7qrj1KTWE.ySRNxkG4db287aUAP8YQRzEV3Qm_ _iYt2v4XjJ5CB6GhRviKwae601NCRhc4dNSCAuZ30fdhUhRxH0YqdHfhrZWa SPw8P1.HKhxSi1G3N18mi3bkl3KtsZS_1F9hzo5UjptQjbOx8kbH54pF8Lta MATw_oDh_cjzOlTBTUn7n_EJeYE4- Received: from [41.204.183.100] by web142604.mail.bf1.yahoo.com via HTTP; Wed, 13 Feb 2013 07:09:22 PST X-Rocket-MIMEInfo: 001.001, R3JlZXRpbmdzLA0KSSBhbSB2aWN0b3IuIGluIHRoZSByZWNlbnQgcGFzdCBpIGhhdmUgaGFkIGludGVyZXN0IGluIGNsb3VkIGNvbXB1dGluZyBhbmQgbW9yZSBzbyBvbiB0aGUgdmlydHVhbGl6YXRpb24gYXNwZWN0IG9mIGl0LiBTaW5jZSBhbSBkb2luZyBteSBtYXN0ZXJzIGluIElULCBpIGRlY2lkZWQgdG8gcGljayB0aGlzIGFzIG15IHJlc2VhcmNoIHRvcGljLiBJIGFtIGFwcGVhbGluZyB0byB5b3UgYWxsIHVzZXJzIGFuZCB2aXJ0dWFsaXphdGlvbiBlbnRodXNpYXN0cywgaGVscCBtZSBieSBmaWxsaW4BMAEBAQE- X-Mailer: YahooMailClassic/15.1.2 YahooMailWebService/0.8.133.508 Message-ID: <1360768162.18819.YahooMailClassic@web142604.mail.bf1.yahoo.com> Date: Wed, 13 Feb 2013 07:09:22 -0800 (PST) From: victor makanga To: xen-users@lists.xen.org MIME-Version: 1.0 X-Mailman-Approved-At: Thu, 14 Feb 2013 02:43:55 +0000 Subject: [Xen-users] Evaluative Standard for Cloud specific Virtualization Security concerns X-BeenThere: xen-users@lists.xen.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="===============2199994214099577099==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============2199994214099577099== Content-Type: multipart/alternative; boundary="473635693-1859958340-1360768162=:18819" --473635693-1859958340-1360768162=:18819 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Greetings, I am victor. in the recent past i have had interest in cloud computing and = more so on the virtualization aspect of it. Since am doing my masters in IT= , i decided to pick this as my research topic. I am appealing to you all us= ers and virtualization enthusiasts, help me by filling in this questionnair= e. Thank you in advance ---=20 From: vmakanga@gmail.com Subject: Evaluative Standard for Cloud specific Virtualization Security con= cerns To: cocopyaach@yahoo.com Date: Wednesday, February 6, 2013, 8:06 AM =0A=0AHallo Sir/Madam=0AMy name is Victor Makanga, a postgraduate student i= n Strathmore University. I am doing a research in =E2=80=98Evaluative stand= ard for cloud specific Virtualization security concerns=E2=80=99. The infor= mation requested is needed purely for academic research purpose and will th= erefore be treated with utmost confidentiality. I will appreciate your part= icipation in the study through answering of the questionnaire. Thank you in= advance.=0A=0AYours Sincerely,=0AVictor Makanga.=0A=0A=0AI've invited you = to fill out the form Evaluative Standard for Cloud specific Virtualization = Security concerns. To fill it out, visit:=0A =0Ahttps://docs.google.com/spreadsheet/viewform?fromEmail=3Dtrue&formkey=3D= dDkzYThsNkptUTdYR25NOHB1a3gzWFE6MQ=0A=0A --473635693-1859958340-1360768162=:18819 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable
Greetings,
I am victor. in the recent past= i have had interest in cloud computing and more so on the virtualization a= spect of it. Since am doing my masters in IT, i decided to pick this as my = research topic. I am appealing to you all users and virtualization enthusia= sts, help me by filling in this questionnaire. Thank you in advance

= ---

From: vmakanga@gmail.com <vmakanga@= gmail.com>
Subject: Evaluative Standard for Cloud specific Virtualiza= tion Security concerns
To: cocopyaach@yahoo.com
Date: Wednesday, Febr= uary 6, 2013, 8:06 AM

=0A

=0A
Hallo Sir/Madam=0AMy name is Victor Makanga, a postgraduate student in St= rathmore University. I am doing a research in =E2=80=98Evaluative standard = for cloud specific Virtualization security concerns=E2=80=99. The informati= on requested is needed purely for academic research purpose and will theref= ore be treated with utmost confidentiality. I will appreciate your particip= ation in the study through answering of the questionnaire. Thank you in adv= ance.=0A=0AYours Sincerely,=0AVictor Makanga.=0A
=0A

=0AI've inv= ited you to fill out the form Evaluative St= andard for Cloud specific Virtualization Security concerns. To f= ill it out, visit:=0A
=0Ahttps://docs.google.com/spre= adsheet/viewform?fromEmail=3Dtrue&formkey=3DdDkzYThsNkptUTdYR25NOHB1a3g= zWFE6MQ=0A

=0A
--473635693-1859958340-1360768162=:18819-- --===============2199994214099577099== 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 --===============2199994214099577099==-- From xen-users-bounces@lists.xen.org Thu Feb 14 02:45:29 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 14 Feb 2013 02:45: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 1U5onj-0001B1-Ra; Thu, 14 Feb 2013 02:43:55 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U5dxz-0006ej-Mp for xen-users@lists.xen.org; Wed, 13 Feb 2013 15:09:47 +0000 Received: from [193.109.254.147:41690] by server-6.bemta-14.messagelabs.com id 69/F8-12010-BBCAB115; Wed, 13 Feb 2013 15:09:47 +0000 X-Env-Sender: cocopyaach@yahoo.com X-Msg-Ref: server-12.tower-27.messagelabs.com!1360768163!9176412!1 X-Originating-IP: [98.139.213.164] X-SpamReason: No, hits=0.6 required=7.0 tests=BODY_RANDOM_LONG, HTML_30_40, HTML_MESSAGE, ML_RADAR_SPEW_LINKS_12, ML_RADAR_SPEW_LINKS_14, ML_RADAR_SPEW_LINKS_6,ML_RADAR_SPEW_LINKS_8,spamassassin: , async_handler: YXN5bmNfZGVsYXk6IDcwNTk4NTcgKHRpbWVvdXQp\n X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 30068 invoked from network); 13 Feb 2013 15:09:24 -0000 Received: from nm14-vm0.bullet.mail.bf1.yahoo.com (HELO nm14-vm0.bullet.mail.bf1.yahoo.com) (98.139.213.164) by server-12.tower-27.messagelabs.com with SMTP; 13 Feb 2013 15:09:24 -0000 Received: from [98.139.212.152] by nm14.bullet.mail.bf1.yahoo.com with NNFMP; 13 Feb 2013 15:09:23 -0000 Received: from [98.139.212.212] by tm9.bullet.mail.bf1.yahoo.com with NNFMP; 13 Feb 2013 15:09:23 -0000 Received: from [127.0.0.1] by omp1021.mail.bf1.yahoo.com with NNFMP; 13 Feb 2013 15:09:23 -0000 X-Yahoo-Newman-Property: ymail-3 X-Yahoo-Newman-Id: 52683.68381.bm@omp1021.mail.bf1.yahoo.com Received: (qmail 19309 invoked by uid 60001); 13 Feb 2013 15:09:23 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1360768162; bh=UP0p2Z/p8x1SLZfil8bUrnIzJtT+gca9DULg8/nESWQ=; h=X-YMail-OSG:Received:X-Rocket-MIMEInfo:X-Mailer:Message-ID:Date:From:Subject:To:MIME-Version:Content-Type; b=PEuUA0a63de0F0jEse0Z/LvwWEI7PU1RlDhAG7ZL4M0wuNQplcOUdzFTluOwe1LegMXTBGQ6Uu+CkQHSOH9n+iwsXt8DWm444UoHprQxdoG0W9pXfqD/l21I83ZafjL2xIBh+yIpM4+yRxh2mhPEzEfXxvu03Cd7JfWuRYuDF4k= DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=X-YMail-OSG:Received:X-Rocket-MIMEInfo:X-Mailer:Message-ID:Date:From:Subject:To:MIME-Version:Content-Type; b=2q+ysea5oY9tcE54ucEd53AGZfZ4N1wFecK6Mu3joe/blWfdGa7mGlUSRkml0LF7rYDS8NvDbzT2UAUY27IJhNBrYpII4tQ4TB2VQNraKuGv1nIIGFcPm01IJPenU+vGFwkEJ9GS+X6wu8R/nCv5VuuF38fBs+KpdkCEaJvOVWA=; X-YMail-OSG: Q.X6L7cVM1kTPnUGxm4r_B8l51yNNuXH5aOSan8zPYujGhz Bbn8p2ctaihcjNhbkaDGk0zJCtk5L.2k7F8DnjneY1hwrHFGoTLhvcvDbKjH cGDNwQLoeR6WymibgiJqaH.08rG7WhGU7B06iXbPGDRFWvCcYNMme2EK3PJt 2N6sBu5nNW1fWAtpw4TI6GiaMZQnjAhsf2Y1a6OTzoMzy7RRd2c39nV2ntgh 8rxM1uSCfcqe353Z4ac_eT_o.99Enm5E.PSX17QCs70FtjRGBAcpVdFMG0kI Df31byaQ8k41B6FmIoHKbpWNzotJd0Hn8XLp91QVViTsBVFspM_DLl_DfItS d6dv_dRdWxpujbe._XWBG8FDk2oJxOZD7pgDtrFaUtdtsl_xm41PLnQQLY91 vxSA8VHRxbiQ5DZSGvKrsC3PkQC9CyhHRc2J7TlR1EKzX97ts1v1EKtbftXD 6PE_kbGmGukMHWbqNJlcB9q2byF36idlqJJm1rPR0TyPdzu1mj1L7phRxYpe xGW6vqGEqsZw.KTtoIybYv7qrj1KTWE.ySRNxkG4db287aUAP8YQRzEV3Qm_ _iYt2v4XjJ5CB6GhRviKwae601NCRhc4dNSCAuZ30fdhUhRxH0YqdHfhrZWa SPw8P1.HKhxSi1G3N18mi3bkl3KtsZS_1F9hzo5UjptQjbOx8kbH54pF8Lta MATw_oDh_cjzOlTBTUn7n_EJeYE4- Received: from [41.204.183.100] by web142604.mail.bf1.yahoo.com via HTTP; Wed, 13 Feb 2013 07:09:22 PST X-Rocket-MIMEInfo: 001.001, R3JlZXRpbmdzLA0KSSBhbSB2aWN0b3IuIGluIHRoZSByZWNlbnQgcGFzdCBpIGhhdmUgaGFkIGludGVyZXN0IGluIGNsb3VkIGNvbXB1dGluZyBhbmQgbW9yZSBzbyBvbiB0aGUgdmlydHVhbGl6YXRpb24gYXNwZWN0IG9mIGl0LiBTaW5jZSBhbSBkb2luZyBteSBtYXN0ZXJzIGluIElULCBpIGRlY2lkZWQgdG8gcGljayB0aGlzIGFzIG15IHJlc2VhcmNoIHRvcGljLiBJIGFtIGFwcGVhbGluZyB0byB5b3UgYWxsIHVzZXJzIGFuZCB2aXJ0dWFsaXphdGlvbiBlbnRodXNpYXN0cywgaGVscCBtZSBieSBmaWxsaW4BMAEBAQE- X-Mailer: YahooMailClassic/15.1.2 YahooMailWebService/0.8.133.508 Message-ID: <1360768162.18819.YahooMailClassic@web142604.mail.bf1.yahoo.com> Date: Wed, 13 Feb 2013 07:09:22 -0800 (PST) From: victor makanga To: xen-users@lists.xen.org MIME-Version: 1.0 X-Mailman-Approved-At: Thu, 14 Feb 2013 02:43:55 +0000 Subject: [Xen-users] Evaluative Standard for Cloud specific Virtualization Security concerns X-BeenThere: xen-users@lists.xen.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="===============2199994214099577099==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============2199994214099577099== Content-Type: multipart/alternative; boundary="473635693-1859958340-1360768162=:18819" --473635693-1859958340-1360768162=:18819 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Greetings, I am victor. in the recent past i have had interest in cloud computing and = more so on the virtualization aspect of it. Since am doing my masters in IT= , i decided to pick this as my research topic. I am appealing to you all us= ers and virtualization enthusiasts, help me by filling in this questionnair= e. Thank you in advance ---=20 From: vmakanga@gmail.com Subject: Evaluative Standard for Cloud specific Virtualization Security con= cerns To: cocopyaach@yahoo.com Date: Wednesday, February 6, 2013, 8:06 AM =0A=0AHallo Sir/Madam=0AMy name is Victor Makanga, a postgraduate student i= n Strathmore University. I am doing a research in =E2=80=98Evaluative stand= ard for cloud specific Virtualization security concerns=E2=80=99. The infor= mation requested is needed purely for academic research purpose and will th= erefore be treated with utmost confidentiality. I will appreciate your part= icipation in the study through answering of the questionnaire. Thank you in= advance.=0A=0AYours Sincerely,=0AVictor Makanga.=0A=0A=0AI've invited you = to fill out the form Evaluative Standard for Cloud specific Virtualization = Security concerns. To fill it out, visit:=0A =0Ahttps://docs.google.com/spreadsheet/viewform?fromEmail=3Dtrue&formkey=3D= dDkzYThsNkptUTdYR25NOHB1a3gzWFE6MQ=0A=0A --473635693-1859958340-1360768162=:18819 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable
Greetings,
I am victor. in the recent past= i have had interest in cloud computing and more so on the virtualization a= spect of it. Since am doing my masters in IT, i decided to pick this as my = research topic. I am appealing to you all users and virtualization enthusia= sts, help me by filling in this questionnaire. Thank you in advance

= ---

From: vmakanga@gmail.com <vmakanga@= gmail.com>
Subject: Evaluative Standard for Cloud specific Virtualiza= tion Security concerns
To: cocopyaach@yahoo.com
Date: Wednesday, Febr= uary 6, 2013, 8:06 AM

=0A

=0A
Hallo Sir/Madam=0AMy name is Victor Makanga, a postgraduate student in St= rathmore University. I am doing a research in =E2=80=98Evaluative standard = for cloud specific Virtualization security concerns=E2=80=99. The informati= on requested is needed purely for academic research purpose and will theref= ore be treated with utmost confidentiality. I will appreciate your particip= ation in the study through answering of the questionnaire. Thank you in adv= ance.=0A=0AYours Sincerely,=0AVictor Makanga.=0A
=0A

=0AI've inv= ited you to fill out the form Evaluative St= andard for Cloud specific Virtualization Security concerns. To f= ill it out, visit:=0A
=0Ahttps://docs.google.com/spre= adsheet/viewform?fromEmail=3Dtrue&formkey=3DdDkzYThsNkptUTdYR25NOHB1a3g= zWFE6MQ=0A

=0A
--473635693-1859958340-1360768162=:18819-- --===============2199994214099577099== 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 --===============2199994214099577099==-- From xen-users-bounces@lists.xen.org Thu Feb 14 10:05:42 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 14 Feb 2013 10: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 1U5vfV-00056x-1d; Thu, 14 Feb 2013 10:03:53 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U5vfT-00056o-1w for xen-users@lists.xen.org; Thu, 14 Feb 2013 10:03:51 +0000 Received: from [85.158.143.99:29810] by server-1.bemta-4.messagelabs.com id 3A/FF-08839-686BC115; Thu, 14 Feb 2013 10:03:50 +0000 X-Env-Sender: Ian.Campbell@citrix.com X-Msg-Ref: server-8.tower-216.messagelabs.com!1360836222!17706934!1 X-Originating-IP: [46.33.159.39] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNDYuMzMuMTU5LjM5ID0+IDIyNTYw\n X-StarScan-Received: X-StarScan-Version: 6.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 30297 invoked from network); 14 Feb 2013 10:03:42 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (46.33.159.39) by server-8.tower-216.messagelabs.com with RC4-SHA encrypted SMTP; 14 Feb 2013 10:03:42 -0000 X-IronPort-AV: E=Sophos;i="4.84,664,1355097600"; d="scan'208";a="1451585" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 14 Feb 2013 10:03: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.297.1; Thu, 14 Feb 2013 10:03:42 +0000 Message-ID: <1360836221.20449.312.camel@zakaz.uk.xensource.com> From: Ian Campbell To: Andreas Falck Date: Thu, 14 Feb 2013 10:03:41 +0000 In-Reply-To: References: Organization: Citrix Systems, Inc. X-Mailer: Evolution 3.4.4-1 MIME-Version: 1.0 Cc: "xen-users@lists.xen.org" Subject: Re: [Xen-users] IVHD error, AMD-Vi gets disabled (4.1.3-3ubuntu1.3) X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: 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, 2013-02-13 at 14:17 +0000, Andreas Falck wrote: > > Could it be a xen bug (I know that my system is somewhat unusual), a > old BIOS bug interacting with newer xen or an aqcuired hardware error? > I'll of course provide more logs if needed. Almost certainly the middle one IMHO, as bugs get fixed in Xen it becomes less tolerant of dubious BIOS tables. Ian. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Thu Feb 14 10:05:42 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 14 Feb 2013 10: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 1U5vfV-00056x-1d; Thu, 14 Feb 2013 10:03:53 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U5vfT-00056o-1w for xen-users@lists.xen.org; Thu, 14 Feb 2013 10:03:51 +0000 Received: from [85.158.143.99:29810] by server-1.bemta-4.messagelabs.com id 3A/FF-08839-686BC115; Thu, 14 Feb 2013 10:03:50 +0000 X-Env-Sender: Ian.Campbell@citrix.com X-Msg-Ref: server-8.tower-216.messagelabs.com!1360836222!17706934!1 X-Originating-IP: [46.33.159.39] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNDYuMzMuMTU5LjM5ID0+IDIyNTYw\n X-StarScan-Received: X-StarScan-Version: 6.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 30297 invoked from network); 14 Feb 2013 10:03:42 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (46.33.159.39) by server-8.tower-216.messagelabs.com with RC4-SHA encrypted SMTP; 14 Feb 2013 10:03:42 -0000 X-IronPort-AV: E=Sophos;i="4.84,664,1355097600"; d="scan'208";a="1451585" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 14 Feb 2013 10:03: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.297.1; Thu, 14 Feb 2013 10:03:42 +0000 Message-ID: <1360836221.20449.312.camel@zakaz.uk.xensource.com> From: Ian Campbell To: Andreas Falck Date: Thu, 14 Feb 2013 10:03:41 +0000 In-Reply-To: References: Organization: Citrix Systems, Inc. X-Mailer: Evolution 3.4.4-1 MIME-Version: 1.0 Cc: "xen-users@lists.xen.org" Subject: Re: [Xen-users] IVHD error, AMD-Vi gets disabled (4.1.3-3ubuntu1.3) X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: 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, 2013-02-13 at 14:17 +0000, Andreas Falck wrote: > > Could it be a xen bug (I know that my system is somewhat unusual), a > old BIOS bug interacting with newer xen or an aqcuired hardware error? > I'll of course provide more logs if needed. Almost certainly the middle one IMHO, as bugs get fixed in Xen it becomes less tolerant of dubious BIOS tables. Ian. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Thu Feb 14 17:05:09 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 14 Feb 2013 17:05: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 1U62Dy-0003W4-Rs; Thu, 14 Feb 2013 17: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 1U62Dx-0003Ss-JV for xen-users@lists.xen.org; Thu, 14 Feb 2013 17:03:53 +0000 Received: from [85.158.143.35:11907] by server-2.bemta-4.messagelabs.com id 61/00-01597-8F81D115; Thu, 14 Feb 2013 17:03:52 +0000 X-Env-Sender: juliofong@mail.com X-Msg-Ref: server-12.tower-21.messagelabs.com!1360861431!12391479!1 X-Originating-IP: [74.208.4.201] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNzQuMjA4LjQuMjAxID0+IDUzNTA=\n, ML_RADAR_SPEW_LINKS_14, spamassassin: X-StarScan-Received: X-StarScan-Version: 6.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 22546 invoked from network); 14 Feb 2013 17:03:51 -0000 Received: from mout.gmx.net (HELO mout.gmx.net) (74.208.4.201) by server-12.tower-21.messagelabs.com with SMTP; 14 Feb 2013 17:03:51 -0000 Received: from mailout-us.gmx.com ([172.19.198.45]) by mrigmx.server.lan (mrigmxus001) with ESMTP (Nemesis) id 0MAyVk-1UDlys3ACi-009wWN for ; Thu, 14 Feb 2013 18:03:50 +0100 Received: (qmail 25914 invoked by uid 0); 14 Feb 2013 17:03:50 -0000 Received: from 86.66.222.237 by rms-us010 with HTTP Date: Thu, 14 Feb 2013 12:03:49 -0500 From: "FONG Julio" Message-ID: <20130214170349.280610@gmx.com> MIME-Version: 1.0 To: xen-users@lists.xen.org X-Authenticated: #76551402 X-Flags: 0001 X-Mailer: GMX.com Web Mailer x-registered: 0 X-GMX-UID: on1vcfkM3zOlO4t3+3Ahhrd+IGRvbwAG Subject: [Xen-users] xen 4.1.2 cpu cores question X-BeenThere: xen-users@lists.xen.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="===============2803556428233117469==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============2803556428233117469== Content-Type: multipart/alternative; boundary="========GMXBoundary280611360861429642081" --========GMXBoundary280611360861429642081 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit Hi, I have a i5 2500K quad core and command "xm info" return me 4 cores. Is it normal as on xen 3 it was 8 cores?? thanks guy. JF --========GMXBoundary280611360861429642081 Content-Type: text/html; charset="utf-8" Content-Transfer-Encoding: quoted-printable Hi,

I have a i5 2500K quad core and command "xm info" return me 4 cores.=

Is it normal as on xen 3 it was 8 cores??

thanks guy= . JF --========GMXBoundary280611360861429642081-- --===============2803556428233117469== 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 --===============2803556428233117469==-- From xen-users-bounces@lists.xen.org Thu Feb 14 17:05:09 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 14 Feb 2013 17:05: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 1U62Dy-0003W4-Rs; Thu, 14 Feb 2013 17: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 1U62Dx-0003Ss-JV for xen-users@lists.xen.org; Thu, 14 Feb 2013 17:03:53 +0000 Received: from [85.158.143.35:11907] by server-2.bemta-4.messagelabs.com id 61/00-01597-8F81D115; Thu, 14 Feb 2013 17:03:52 +0000 X-Env-Sender: juliofong@mail.com X-Msg-Ref: server-12.tower-21.messagelabs.com!1360861431!12391479!1 X-Originating-IP: [74.208.4.201] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNzQuMjA4LjQuMjAxID0+IDUzNTA=\n, ML_RADAR_SPEW_LINKS_14, spamassassin: X-StarScan-Received: X-StarScan-Version: 6.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 22546 invoked from network); 14 Feb 2013 17:03:51 -0000 Received: from mout.gmx.net (HELO mout.gmx.net) (74.208.4.201) by server-12.tower-21.messagelabs.com with SMTP; 14 Feb 2013 17:03:51 -0000 Received: from mailout-us.gmx.com ([172.19.198.45]) by mrigmx.server.lan (mrigmxus001) with ESMTP (Nemesis) id 0MAyVk-1UDlys3ACi-009wWN for ; Thu, 14 Feb 2013 18:03:50 +0100 Received: (qmail 25914 invoked by uid 0); 14 Feb 2013 17:03:50 -0000 Received: from 86.66.222.237 by rms-us010 with HTTP Date: Thu, 14 Feb 2013 12:03:49 -0500 From: "FONG Julio" Message-ID: <20130214170349.280610@gmx.com> MIME-Version: 1.0 To: xen-users@lists.xen.org X-Authenticated: #76551402 X-Flags: 0001 X-Mailer: GMX.com Web Mailer x-registered: 0 X-GMX-UID: on1vcfkM3zOlO4t3+3Ahhrd+IGRvbwAG Subject: [Xen-users] xen 4.1.2 cpu cores question X-BeenThere: xen-users@lists.xen.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="===============2803556428233117469==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============2803556428233117469== Content-Type: multipart/alternative; boundary="========GMXBoundary280611360861429642081" --========GMXBoundary280611360861429642081 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit Hi, I have a i5 2500K quad core and command "xm info" return me 4 cores. Is it normal as on xen 3 it was 8 cores?? thanks guy. JF --========GMXBoundary280611360861429642081 Content-Type: text/html; charset="utf-8" Content-Transfer-Encoding: quoted-printable Hi,

I have a i5 2500K quad core and command "xm info" return me 4 cores.=

Is it normal as on xen 3 it was 8 cores??

thanks guy= . JF --========GMXBoundary280611360861429642081-- --===============2803556428233117469== 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 --===============2803556428233117469==-- From xen-users-bounces@lists.xen.org Fri Feb 15 02:57:32 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 15 Feb 2013 02:57: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 1U6BT2-0007Ql-DQ; Fri, 15 Feb 2013 02:56:04 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U6BT0-0007Qg-A8 for xen-users@lists.xen.org; Fri, 15 Feb 2013 02:56:02 +0000 Received: from [85.158.138.51:24073] by server-5.bemta-3.messagelabs.com id 0C/25-04457-1C3AD115; Fri, 15 Feb 2013 02:56:01 +0000 X-Env-Sender: matthias.kannenberg@googlemail.com X-Msg-Ref: server-7.tower-174.messagelabs.com!1360896960!18750930!1 X-Originating-IP: [74.125.82.182] X-SpamReason: No, hits=0.8 required=7.0 tests=BODY_RANDOM_LONG, RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 15599 invoked from network); 15 Feb 2013 02:56:00 -0000 Received: from mail-we0-f182.google.com (HELO mail-we0-f182.google.com) (74.125.82.182) by server-7.tower-174.messagelabs.com with RC4-SHA encrypted SMTP; 15 Feb 2013 02:56:00 -0000 Received: by mail-we0-f182.google.com with SMTP id t57so2506093wey.41 for ; Thu, 14 Feb 2013 18:56:00 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=20120113; h=x-received:mime-version:in-reply-to:references:from:date:message-id :subject:to:cc:content-type; bh=owksWHnT8X9X1PQcw6qS5ZjCgi7Dl+BQJ9qM2b+pZ4U=; b=JwH3P37v8ihEXXfjVj3BwzTFvCtQqUDXPgnYJMlE0g2JfKsOWDG/3COaSqbOG0vxIu 2tLgcaXIEYulVQwSo6u5SmXdsM+9pyM4sYiGM6wiaRF6p5rXia4WSbaxTCgxwY2/pLQ0 ss+MraBSdV0xbXq/vWymGQGUhDAOfmPkcE+pk1UBrlQ+Kpc0664yEOvQeOnbzO65RLA9 Tqf9MiV9+nmKd03Pd3ncXRwnpnu6SE4sAIy0gVOKl4fRhaR1fN0t4mkfq5kvoddVpqz2 ZV+8vBEpbm7tUC+rXh6ltG+ZC5Q0WM3gP2g/SL+sTj6dARVpheBfUnN+VEBTyxilE0Ly PdLQ== X-Received: by 10.180.84.162 with SMTP id a2mr1406027wiz.14.1360896960365; Thu, 14 Feb 2013 18:56:00 -0800 (PST) MIME-Version: 1.0 Received: by 10.194.80.68 with HTTP; Thu, 14 Feb 2013 18:55:40 -0800 (PST) In-Reply-To: <511B5D5B02000078000BDE76@nat28.tlf.novell.com> References: <1360581739.29432.115.camel@zakaz.uk.xensource.com> <511A0E9C02000078000BD9EA@nat28.tlf.novell.com> <511B5D5B02000078000BDE76@nat28.tlf.novell.com> From: Matthias Date: Fri, 15 Feb 2013 03:55:40 +0100 Message-ID: To: Jan Beulich Cc: "boris.ostrovsky@amd.com" , Ian Campbell , "xen-users@lists.xen.org" Subject: Re: [Xen-users] Latest AMD, IOMMU Security Change causing CPU0 Panic and general Problems with AMD+IOMMU changes X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: 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 finally had the chance to test the new patches and it's great that they made it to the main rep already. With the new patches (rev 26532 xen-unstable) I neither have the boot time crash nore the disk access issue I reported above. Unfortunatly, the changes disable my IOMMU rendering pci and vga passthrough unusable for me. Now, I might have missed something, but what exactly is the point of this at all? My Xen is running fine with AMD IOMMU for years now but if i still want to do this, I have to revert changes 26532, 26531, 26519, 26518 and 25617 (basically all the AMD/IOMMU changes). When don't reverting them, I get the AMD-Vi is disabled messages at boot time and an error message for every PCI device I try to assign. Is there any chance you might rethink the whole approach? Because pci passthrough is something i heavily use.. xl dmesg output for AMD-Vi: (XEN) Initing memory sharing. (XEN) AMD Fam10h machine check reporting enabled (XEN) PCI: MCFG configuration 0: base e0000000 segment 0000 buses 00 - ff (XEN) PCI: Not using MCFG for segment 0000 bus 00-ff (XEN) IVHD Error: no information for IO-APIC 0x6 (XEN) AMD-Vi: Error initialization (XEN) I/O virtualisation disabled (XEN) ENABLING IO-APIC IRQs (XEN) -> Using new ACK method (XEN) ..TIMER: vector=0xF0 apic1=0 pin1=2 apic2=-1 pin2=-1 Output when starting the domU with PCI passthrough (every pci-failed line is for one pci device i try to pass): root@Server:~/xen/domu# xl create WORK Parsing config from WORK xc: info: VIRTUAL MEMORY ARRANGEMENT: Loader: 0000000000100000->000000000019e9a8 Modules: 0000000000000000->0000000000000000 TOTAL: 0000000000000000->000000013f800000 ENTRY ADDRESS: 0000000000100000 xc: info: PHYSICAL MEMORY ALLOCATION: 4KB PAGES: 0x0000000000000200 2MB PAGES: 0x00000000000003fb 1GB PAGES: 0x0000000000000003 libxl: error: libxl_pci.c:948:do_pci_add: xc_assign_device failed libxl: error: libxl_pci.c:948:do_pci_add: xc_assign_device failed libxl: error: libxl_pci.c:989:libxl__device_pci_reset: The kernel doesn't support reset from sysfs for PCI device 0000:00:12.0 libxl: error: libxl_pci.c:948:do_pci_add: xc_assign_device failed libxl: error: libxl_pci.c:948:do_pci_add: xc_assign_device failed libxl: error: libxl_pci.c:989:libxl__device_pci_reset: The kernel doesn't support reset from sysfs for PCI device 0000:00:13.0 libxl: error: libxl_pci.c:948:do_pci_add: xc_assign_device failed libxl: error: libxl_pci.c:948:do_pci_add: xc_assign_device failed libxl: error: libxl_pci.c:948:do_pci_add: xc_assign_device failed libxl: error: libxl_pci.c:989:libxl__device_pci_reset: The kernel doesn't support reset from sysfs for PCI device 0000:00:14.5 libxl: error: libxl_pci.c:948:do_pci_add: xc_assign_device failed libxl: error: libxl_pci.c:989:libxl__device_pci_reset: The kernel doesn't support reset from sysfs for PCI device 0000:00:16.0 libxl: error: libxl_pci.c:948:do_pci_add: xc_assign_device failed libxl: error: libxl_pci.c:948:do_pci_add: xc_assign_device failed Daemon running with PID 3448 The 'kernel doesn't support reset from sysfs' messages are normal and don't indicate any malfunction. 2013/2/13 Jan Beulich : >>>> On 13.02.13 at 09:27, Matthias wrote: >> Do you have any idea when all the new AMD/IOMMU patches will be >> included in the unstable repo? Since i got some issues with the other >> patches as well and have seen you got around 10 patches for fixing >> this in xen-devel, it would generally like the idea of having all the >> fixes in the hg repo then patching everything by hand. > > This largely depends on the pending patches getting reviewed > and acked appropriately. But it's three patches only according to > my counting, one of which being in need of a conceptual decision > (i.e. unlikely to go in very quickly), and out of those three only > one is a regression fix (the one I pointed you to). > > Jan > _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Fri Feb 15 02:57:32 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 15 Feb 2013 02:57: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 1U6BT2-0007Ql-DQ; Fri, 15 Feb 2013 02:56:04 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U6BT0-0007Qg-A8 for xen-users@lists.xen.org; Fri, 15 Feb 2013 02:56:02 +0000 Received: from [85.158.138.51:24073] by server-5.bemta-3.messagelabs.com id 0C/25-04457-1C3AD115; Fri, 15 Feb 2013 02:56:01 +0000 X-Env-Sender: matthias.kannenberg@googlemail.com X-Msg-Ref: server-7.tower-174.messagelabs.com!1360896960!18750930!1 X-Originating-IP: [74.125.82.182] X-SpamReason: No, hits=0.8 required=7.0 tests=BODY_RANDOM_LONG, RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 15599 invoked from network); 15 Feb 2013 02:56:00 -0000 Received: from mail-we0-f182.google.com (HELO mail-we0-f182.google.com) (74.125.82.182) by server-7.tower-174.messagelabs.com with RC4-SHA encrypted SMTP; 15 Feb 2013 02:56:00 -0000 Received: by mail-we0-f182.google.com with SMTP id t57so2506093wey.41 for ; Thu, 14 Feb 2013 18:56:00 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=20120113; h=x-received:mime-version:in-reply-to:references:from:date:message-id :subject:to:cc:content-type; bh=owksWHnT8X9X1PQcw6qS5ZjCgi7Dl+BQJ9qM2b+pZ4U=; b=JwH3P37v8ihEXXfjVj3BwzTFvCtQqUDXPgnYJMlE0g2JfKsOWDG/3COaSqbOG0vxIu 2tLgcaXIEYulVQwSo6u5SmXdsM+9pyM4sYiGM6wiaRF6p5rXia4WSbaxTCgxwY2/pLQ0 ss+MraBSdV0xbXq/vWymGQGUhDAOfmPkcE+pk1UBrlQ+Kpc0664yEOvQeOnbzO65RLA9 Tqf9MiV9+nmKd03Pd3ncXRwnpnu6SE4sAIy0gVOKl4fRhaR1fN0t4mkfq5kvoddVpqz2 ZV+8vBEpbm7tUC+rXh6ltG+ZC5Q0WM3gP2g/SL+sTj6dARVpheBfUnN+VEBTyxilE0Ly PdLQ== X-Received: by 10.180.84.162 with SMTP id a2mr1406027wiz.14.1360896960365; Thu, 14 Feb 2013 18:56:00 -0800 (PST) MIME-Version: 1.0 Received: by 10.194.80.68 with HTTP; Thu, 14 Feb 2013 18:55:40 -0800 (PST) In-Reply-To: <511B5D5B02000078000BDE76@nat28.tlf.novell.com> References: <1360581739.29432.115.camel@zakaz.uk.xensource.com> <511A0E9C02000078000BD9EA@nat28.tlf.novell.com> <511B5D5B02000078000BDE76@nat28.tlf.novell.com> From: Matthias Date: Fri, 15 Feb 2013 03:55:40 +0100 Message-ID: To: Jan Beulich Cc: "boris.ostrovsky@amd.com" , Ian Campbell , "xen-users@lists.xen.org" Subject: Re: [Xen-users] Latest AMD, IOMMU Security Change causing CPU0 Panic and general Problems with AMD+IOMMU changes X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: 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 finally had the chance to test the new patches and it's great that they made it to the main rep already. With the new patches (rev 26532 xen-unstable) I neither have the boot time crash nore the disk access issue I reported above. Unfortunatly, the changes disable my IOMMU rendering pci and vga passthrough unusable for me. Now, I might have missed something, but what exactly is the point of this at all? My Xen is running fine with AMD IOMMU for years now but if i still want to do this, I have to revert changes 26532, 26531, 26519, 26518 and 25617 (basically all the AMD/IOMMU changes). When don't reverting them, I get the AMD-Vi is disabled messages at boot time and an error message for every PCI device I try to assign. Is there any chance you might rethink the whole approach? Because pci passthrough is something i heavily use.. xl dmesg output for AMD-Vi: (XEN) Initing memory sharing. (XEN) AMD Fam10h machine check reporting enabled (XEN) PCI: MCFG configuration 0: base e0000000 segment 0000 buses 00 - ff (XEN) PCI: Not using MCFG for segment 0000 bus 00-ff (XEN) IVHD Error: no information for IO-APIC 0x6 (XEN) AMD-Vi: Error initialization (XEN) I/O virtualisation disabled (XEN) ENABLING IO-APIC IRQs (XEN) -> Using new ACK method (XEN) ..TIMER: vector=0xF0 apic1=0 pin1=2 apic2=-1 pin2=-1 Output when starting the domU with PCI passthrough (every pci-failed line is for one pci device i try to pass): root@Server:~/xen/domu# xl create WORK Parsing config from WORK xc: info: VIRTUAL MEMORY ARRANGEMENT: Loader: 0000000000100000->000000000019e9a8 Modules: 0000000000000000->0000000000000000 TOTAL: 0000000000000000->000000013f800000 ENTRY ADDRESS: 0000000000100000 xc: info: PHYSICAL MEMORY ALLOCATION: 4KB PAGES: 0x0000000000000200 2MB PAGES: 0x00000000000003fb 1GB PAGES: 0x0000000000000003 libxl: error: libxl_pci.c:948:do_pci_add: xc_assign_device failed libxl: error: libxl_pci.c:948:do_pci_add: xc_assign_device failed libxl: error: libxl_pci.c:989:libxl__device_pci_reset: The kernel doesn't support reset from sysfs for PCI device 0000:00:12.0 libxl: error: libxl_pci.c:948:do_pci_add: xc_assign_device failed libxl: error: libxl_pci.c:948:do_pci_add: xc_assign_device failed libxl: error: libxl_pci.c:989:libxl__device_pci_reset: The kernel doesn't support reset from sysfs for PCI device 0000:00:13.0 libxl: error: libxl_pci.c:948:do_pci_add: xc_assign_device failed libxl: error: libxl_pci.c:948:do_pci_add: xc_assign_device failed libxl: error: libxl_pci.c:948:do_pci_add: xc_assign_device failed libxl: error: libxl_pci.c:989:libxl__device_pci_reset: The kernel doesn't support reset from sysfs for PCI device 0000:00:14.5 libxl: error: libxl_pci.c:948:do_pci_add: xc_assign_device failed libxl: error: libxl_pci.c:989:libxl__device_pci_reset: The kernel doesn't support reset from sysfs for PCI device 0000:00:16.0 libxl: error: libxl_pci.c:948:do_pci_add: xc_assign_device failed libxl: error: libxl_pci.c:948:do_pci_add: xc_assign_device failed Daemon running with PID 3448 The 'kernel doesn't support reset from sysfs' messages are normal and don't indicate any malfunction. 2013/2/13 Jan Beulich : >>>> On 13.02.13 at 09:27, Matthias wrote: >> Do you have any idea when all the new AMD/IOMMU patches will be >> included in the unstable repo? Since i got some issues with the other >> patches as well and have seen you got around 10 patches for fixing >> this in xen-devel, it would generally like the idea of having all the >> fixes in the hg repo then patching everything by hand. > > This largely depends on the pending patches getting reviewed > and acked appropriately. But it's three patches only according to > my counting, one of which being in need of a conceptual decision > (i.e. unlikely to go in very quickly), and out of those three only > one is a regression fix (the one I pointed you to). > > Jan > _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Fri Feb 15 03:16:17 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 15 Feb 2013 03:16: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 1U6BlP-0007pI-EY; Fri, 15 Feb 2013 03:15:03 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U6BlN-0007pC-6z for xen-users@lists.xensource.com; Fri, 15 Feb 2013 03:15:01 +0000 Received: from [85.158.143.99:59528] by server-2.bemta-4.messagelabs.com id B9/F2-01597-438AD115; Fri, 15 Feb 2013 03:15:00 +0000 X-Env-Sender: apxeng@gmail.com X-Msg-Ref: server-11.tower-216.messagelabs.com!1360898099!20084079!1 X-Originating-IP: [209.85.216.174] 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.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 27366 invoked from network); 15 Feb 2013 03:14:59 -0000 Received: from mail-qc0-f174.google.com (HELO mail-qc0-f174.google.com) (209.85.216.174) by server-11.tower-216.messagelabs.com with RC4-SHA encrypted SMTP; 15 Feb 2013 03:14:59 -0000 Received: by mail-qc0-f174.google.com with SMTP id z24so1126076qcq.5 for ; Thu, 14 Feb 2013 19:14:58 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:date:message-id:subject:from:to :content-type; bh=0+6atuTpbFI6RN1gKzrmQ6gNsRXSbS2Jv7b66BHbErE=; b=cWSUFW77KOJBf3WFvD4nLrUA+pFnVsxHcppxPM6RDxb3hAKIX8rwbXVCnGXu4koIaK CuyvkfJ49itdQ7F7upD2s3U/wMKzKaPzoBAfdaQUOYyED7JhCsc0fRYFpmak3rHwsw5a QM1WbYGq41fmNoMuB90TWYJKnEkowq44m0ImNNEJbDoFL2UrxoW1d3offJuLcB/eb3pu mKjg2oYu4+TNF5y0bSubYYO9NxIVKsrCUdNPkVN4UMi98s9tHkwjxzssHQ3OYSA/rSbK 7eU+KrPQlhEsoN88DRZcjd6FPOMkYcv8RaG+mR4yloj/5apgQLOrFeeH4XMMgAPcABWY sPTg== MIME-Version: 1.0 X-Received: by 10.49.12.138 with SMTP id y10mr418977qeb.64.1360898098809; Thu, 14 Feb 2013 19:14:58 -0800 (PST) Received: by 10.49.4.4 with HTTP; Thu, 14 Feb 2013 19:14:58 -0800 (PST) Date: Thu, 14 Feb 2013 19:14:58 -0800 Message-ID: From: AP To: xen-users@lists.xensource.com Subject: [Xen-users] Issues creating a minimal Xen /Dom0 Ubuntu 12.04 install X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: 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 create a minimal Xen/Dom0 based on Ubuntu 12.04. I am using upstream Xen 4.1.1 with a Linux 3.1.2 Dom0 kernel. I am building Xen and Linux offline i.e. on another server, creating deb packages (I back-ported "make deb" from Xen 4.2 to Xen 4.1.1) that I then install on the minimal system. All this is happening correctly, Xen and Dom0 comes up. I am able to do basic commands like "xl list" and "xl info". However when I go to bring up a Ubuntu pv guest I get the following error: root@knc-11588:~# xl create -c /etc/xen/ubuntu-12.04-1pv Parsing config file /etc/xen/ubuntu-12.04-1pv Unable to attach console Here is the DomU config: builder = 'linux' bootloader ="pygrub" memory = 4096 name = 'ubuntu-12.04-1pv' vcpus = 2 vif = [ 'type=vif' ] disk = ['phy:/dev/xvdd,xvda,w'] I do not see any log files being created in /var/log/xen/. Nor do I see any output after initial boot from "xl dmesg" or "dmesg". I do realize the "make deb" process does not generate any dependencies so I suspect that I am missing some packages. I also know on Ubuntu installing the tools needs to be done with "make install-tools PYTHON_PREFIX_ARG=". Maybe that is not being simulated when going deb route? Does someone know how to debug this issue? Thanks, AP _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Fri Feb 15 03:16:17 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 15 Feb 2013 03:16: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 1U6BlP-0007pI-EY; Fri, 15 Feb 2013 03:15:03 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U6BlN-0007pC-6z for xen-users@lists.xensource.com; Fri, 15 Feb 2013 03:15:01 +0000 Received: from [85.158.143.99:59528] by server-2.bemta-4.messagelabs.com id B9/F2-01597-438AD115; Fri, 15 Feb 2013 03:15:00 +0000 X-Env-Sender: apxeng@gmail.com X-Msg-Ref: server-11.tower-216.messagelabs.com!1360898099!20084079!1 X-Originating-IP: [209.85.216.174] 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.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 27366 invoked from network); 15 Feb 2013 03:14:59 -0000 Received: from mail-qc0-f174.google.com (HELO mail-qc0-f174.google.com) (209.85.216.174) by server-11.tower-216.messagelabs.com with RC4-SHA encrypted SMTP; 15 Feb 2013 03:14:59 -0000 Received: by mail-qc0-f174.google.com with SMTP id z24so1126076qcq.5 for ; Thu, 14 Feb 2013 19:14:58 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:date:message-id:subject:from:to :content-type; bh=0+6atuTpbFI6RN1gKzrmQ6gNsRXSbS2Jv7b66BHbErE=; b=cWSUFW77KOJBf3WFvD4nLrUA+pFnVsxHcppxPM6RDxb3hAKIX8rwbXVCnGXu4koIaK CuyvkfJ49itdQ7F7upD2s3U/wMKzKaPzoBAfdaQUOYyED7JhCsc0fRYFpmak3rHwsw5a QM1WbYGq41fmNoMuB90TWYJKnEkowq44m0ImNNEJbDoFL2UrxoW1d3offJuLcB/eb3pu mKjg2oYu4+TNF5y0bSubYYO9NxIVKsrCUdNPkVN4UMi98s9tHkwjxzssHQ3OYSA/rSbK 7eU+KrPQlhEsoN88DRZcjd6FPOMkYcv8RaG+mR4yloj/5apgQLOrFeeH4XMMgAPcABWY sPTg== MIME-Version: 1.0 X-Received: by 10.49.12.138 with SMTP id y10mr418977qeb.64.1360898098809; Thu, 14 Feb 2013 19:14:58 -0800 (PST) Received: by 10.49.4.4 with HTTP; Thu, 14 Feb 2013 19:14:58 -0800 (PST) Date: Thu, 14 Feb 2013 19:14:58 -0800 Message-ID: From: AP To: xen-users@lists.xensource.com Subject: [Xen-users] Issues creating a minimal Xen /Dom0 Ubuntu 12.04 install X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: 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 create a minimal Xen/Dom0 based on Ubuntu 12.04. I am using upstream Xen 4.1.1 with a Linux 3.1.2 Dom0 kernel. I am building Xen and Linux offline i.e. on another server, creating deb packages (I back-ported "make deb" from Xen 4.2 to Xen 4.1.1) that I then install on the minimal system. All this is happening correctly, Xen and Dom0 comes up. I am able to do basic commands like "xl list" and "xl info". However when I go to bring up a Ubuntu pv guest I get the following error: root@knc-11588:~# xl create -c /etc/xen/ubuntu-12.04-1pv Parsing config file /etc/xen/ubuntu-12.04-1pv Unable to attach console Here is the DomU config: builder = 'linux' bootloader ="pygrub" memory = 4096 name = 'ubuntu-12.04-1pv' vcpus = 2 vif = [ 'type=vif' ] disk = ['phy:/dev/xvdd,xvda,w'] I do not see any log files being created in /var/log/xen/. Nor do I see any output after initial boot from "xl dmesg" or "dmesg". I do realize the "make deb" process does not generate any dependencies so I suspect that I am missing some packages. I also know on Ubuntu installing the tools needs to be done with "make install-tools PYTHON_PREFIX_ARG=". Maybe that is not being simulated when going deb route? Does someone know how to debug this issue? Thanks, AP _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Fri Feb 15 04:04:38 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 15 Feb 2013 04:04: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 1U6CWF-0008N4-NR; Fri, 15 Feb 2013 04:03:27 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U6Bx9-00088k-Hd for xen-users@lists.xensource.com; Fri, 15 Feb 2013 03:27:11 +0000 Received: from [85.158.139.211:59173] by server-16.bemta-5.messagelabs.com id 66/D9-14948-E0BAD115; Fri, 15 Feb 2013 03:27:10 +0000 X-Env-Sender: liuhuan123123123@yahoo.com X-Msg-Ref: server-8.tower-206.messagelabs.com!1360898829!22583494!1 X-Originating-IP: [216.139.236.26] X-SpamReason: No, hits=3.0 required=7.0 tests=BODY_RANDOM_LONG, FORGED_YAHOO_RCVD, FROM_ENDS_IN_NUMS, ML_RADAR_SPEW_LINKS_14, spamassassin: X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 32360 invoked from network); 15 Feb 2013 03:27:10 -0000 Received: from sam.nabble.com (HELO sam.nabble.com) (216.139.236.26) by server-8.tower-206.messagelabs.com with AES256-SHA encrypted SMTP; 15 Feb 2013 03:27:10 -0000 Received: from [192.168.236.26] (helo=sam.nabble.com) by sam.nabble.com with esmtp (Exim 4.72) (envelope-from ) id 1U6Bx6-0004ka-Bf for xen-users@lists.xensource.com; Thu, 14 Feb 2013 19:27:08 -0800 Date: Thu, 14 Feb 2013 19:27:08 -0800 (PST) From: liuhuan To: xen-users@lists.xensource.com Message-ID: <1360898828351-5714193.post@n5.nabble.com> In-Reply-To: References: MIME-Version: 1.0 X-Mailman-Approved-At: Fri, 15 Feb 2013 04:03:26 +0000 Subject: Re: [Xen-users] Xwindows or Freenx in a guest domain X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org Most bodies do not crop adequate adversity of their feet. Buy Isabel Marant and accretion an addition to walking everywhere barefoot Isabel Marant sneakers and artificial basal tinnitus and electric shocks to abate alone project, walk, and added http://fashionisabel.com/goods-4-isabel-marant-Beckett-suede-wedge-sneakers.html isabel marant sale such as active accession and dancing. These added adherence and control, in adjustment to accomplish feet, ankle, the adversity aback heel acquaintance and accidents. A lot of sports Iabel await on their marant chaussures nets equipment, accomplish anxiety just air breeze to breathe. These filigree apparatus of baby holes, and advice lower electricity, baptize formed in bottom smells and allergies. As you know,Isabel Marant is a french abode of actualization founded 1994 by Isabel Marant. The aggregation has 10 shops worldwide: Paris, New York, Tokyo, Hong Kong, Beijing, Madrid, Beirut and has banker in added than 35 countries. It's boots is actual adequate and it can accurate your own style. -- View this message in context: http://xen.1045712.n5.nabble.com/Xwindows-or-Freenx-in-a-guest-domain-tp2556589p5714193.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 Fri Feb 15 04:04:38 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 15 Feb 2013 04:04: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 1U6CWF-0008N4-NR; Fri, 15 Feb 2013 04:03:27 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U6Bx9-00088k-Hd for xen-users@lists.xensource.com; Fri, 15 Feb 2013 03:27:11 +0000 Received: from [85.158.139.211:59173] by server-16.bemta-5.messagelabs.com id 66/D9-14948-E0BAD115; Fri, 15 Feb 2013 03:27:10 +0000 X-Env-Sender: liuhuan123123123@yahoo.com X-Msg-Ref: server-8.tower-206.messagelabs.com!1360898829!22583494!1 X-Originating-IP: [216.139.236.26] X-SpamReason: No, hits=3.0 required=7.0 tests=BODY_RANDOM_LONG, FORGED_YAHOO_RCVD, FROM_ENDS_IN_NUMS, ML_RADAR_SPEW_LINKS_14, spamassassin: X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 32360 invoked from network); 15 Feb 2013 03:27:10 -0000 Received: from sam.nabble.com (HELO sam.nabble.com) (216.139.236.26) by server-8.tower-206.messagelabs.com with AES256-SHA encrypted SMTP; 15 Feb 2013 03:27:10 -0000 Received: from [192.168.236.26] (helo=sam.nabble.com) by sam.nabble.com with esmtp (Exim 4.72) (envelope-from ) id 1U6Bx6-0004ka-Bf for xen-users@lists.xensource.com; Thu, 14 Feb 2013 19:27:08 -0800 Date: Thu, 14 Feb 2013 19:27:08 -0800 (PST) From: liuhuan To: xen-users@lists.xensource.com Message-ID: <1360898828351-5714193.post@n5.nabble.com> In-Reply-To: References: MIME-Version: 1.0 X-Mailman-Approved-At: Fri, 15 Feb 2013 04:03:26 +0000 Subject: Re: [Xen-users] Xwindows or Freenx in a guest domain X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org Most bodies do not crop adequate adversity of their feet. Buy Isabel Marant and accretion an addition to walking everywhere barefoot Isabel Marant sneakers and artificial basal tinnitus and electric shocks to abate alone project, walk, and added http://fashionisabel.com/goods-4-isabel-marant-Beckett-suede-wedge-sneakers.html isabel marant sale such as active accession and dancing. These added adherence and control, in adjustment to accomplish feet, ankle, the adversity aback heel acquaintance and accidents. A lot of sports Iabel await on their marant chaussures nets equipment, accomplish anxiety just air breeze to breathe. These filigree apparatus of baby holes, and advice lower electricity, baptize formed in bottom smells and allergies. As you know,Isabel Marant is a french abode of actualization founded 1994 by Isabel Marant. The aggregation has 10 shops worldwide: Paris, New York, Tokyo, Hong Kong, Beijing, Madrid, Beirut and has banker in added than 35 countries. It's boots is actual adequate and it can accurate your own style. -- View this message in context: http://xen.1045712.n5.nabble.com/Xwindows-or-Freenx-in-a-guest-domain-tp2556589p5714193.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 Fri Feb 15 08:09:04 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 15 Feb 2013 08:09: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 1U6GKY-0001yJ-UY; Fri, 15 Feb 2013 08:07:38 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U6GKX-0001yE-D1 for xen-users@lists.xen.org; Fri, 15 Feb 2013 08:07:37 +0000 Received: from [85.158.139.83:18391] by server-9.bemta-5.messagelabs.com id B4/86-24440-8CCED115; Fri, 15 Feb 2013 08:07:36 +0000 X-Env-Sender: JBeulich@suse.com X-Msg-Ref: server-9.tower-182.messagelabs.com!1360915655!26716663!1 X-Originating-IP: [130.57.49.28] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogMTMwLjU3LjQ5LjI4ID0+IDQyNzQ=\n X-StarScan-Received: X-StarScan-Version: 6.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 9820 invoked from network); 15 Feb 2013 08:07:35 -0000 Received: from nat28.tlf.novell.com (HELO nat28.tlf.novell.com) (130.57.49.28) by server-9.tower-182.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 15 Feb 2013 08:07:35 -0000 Received: from EMEA1-MTA by nat28.tlf.novell.com with Novell_GroupWise; Fri, 15 Feb 2013 08:07:34 +0000 Message-Id: <511DFB0C02000078000BE94B@nat28.tlf.novell.com> X-Mailer: Novell GroupWise Internet Agent 12.0.1 Date: Fri, 15 Feb 2013 08:08:28 +0000 From: "Jan Beulich" To: "Matthias" References: <1360581739.29432.115.camel@zakaz.uk.xensource.com> <511A0E9C02000078000BD9EA@nat28.tlf.novell.com> <511B5D5B02000078000BDE76@nat28.tlf.novell.com> In-Reply-To: Mime-Version: 1.0 Content-Disposition: inline Cc: "xen-users@lists.xen.org" , Boris Ostrovsky , Ian Campbell Subject: Re: [Xen-users] Latest AMD, IOMMU Security Change causing CPU0 Panic and general Problems with AMD+IOMMU changes X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: 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.02.13 at 03:55, Matthias wrote: > Unfortunatly, the changes disable my IOMMU rendering pci and vga > passthrough unusable for me. Now, I might have missed something, but > what exactly is the point of this at all? My Xen is running fine with > AMD IOMMU for years now but if i still want to do this, I have to > revert changes 26532, 26531, 26519, 26518 and 25617 (basically all the > AMD/IOMMU changes). No, you rather need to get your firmware fixed, because this > (XEN) IVHD Error: no information for IO-APIC 0x6 is simply not tolerable. But you can, at the expense of security, revert to using the global interrupt remapping table, as pointed out in this same context to others before ("iommu=no-amd-iommu-perdev-intremap"). And yes, we are indeed re-thinking the situation, but in everything to consider doing you need to realize the security implications. See for instance http://lists.xen.org/archives/html/xen-devel/2013-02/msg00591.html and the single IOMMU consideration in http://lists.xen.org/archives/html/xen-devel/2013-02/msg00817.html (but which I don't think will actually work without looking at the PCI bus topology). Feel free to participate in that discussion. Jan _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Fri Feb 15 08:09:04 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 15 Feb 2013 08:09: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 1U6GKY-0001yJ-UY; Fri, 15 Feb 2013 08:07:38 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U6GKX-0001yE-D1 for xen-users@lists.xen.org; Fri, 15 Feb 2013 08:07:37 +0000 Received: from [85.158.139.83:18391] by server-9.bemta-5.messagelabs.com id B4/86-24440-8CCED115; Fri, 15 Feb 2013 08:07:36 +0000 X-Env-Sender: JBeulich@suse.com X-Msg-Ref: server-9.tower-182.messagelabs.com!1360915655!26716663!1 X-Originating-IP: [130.57.49.28] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogMTMwLjU3LjQ5LjI4ID0+IDQyNzQ=\n X-StarScan-Received: X-StarScan-Version: 6.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 9820 invoked from network); 15 Feb 2013 08:07:35 -0000 Received: from nat28.tlf.novell.com (HELO nat28.tlf.novell.com) (130.57.49.28) by server-9.tower-182.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 15 Feb 2013 08:07:35 -0000 Received: from EMEA1-MTA by nat28.tlf.novell.com with Novell_GroupWise; Fri, 15 Feb 2013 08:07:34 +0000 Message-Id: <511DFB0C02000078000BE94B@nat28.tlf.novell.com> X-Mailer: Novell GroupWise Internet Agent 12.0.1 Date: Fri, 15 Feb 2013 08:08:28 +0000 From: "Jan Beulich" To: "Matthias" References: <1360581739.29432.115.camel@zakaz.uk.xensource.com> <511A0E9C02000078000BD9EA@nat28.tlf.novell.com> <511B5D5B02000078000BDE76@nat28.tlf.novell.com> In-Reply-To: Mime-Version: 1.0 Content-Disposition: inline Cc: "xen-users@lists.xen.org" , Boris Ostrovsky , Ian Campbell Subject: Re: [Xen-users] Latest AMD, IOMMU Security Change causing CPU0 Panic and general Problems with AMD+IOMMU changes X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: 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.02.13 at 03:55, Matthias wrote: > Unfortunatly, the changes disable my IOMMU rendering pci and vga > passthrough unusable for me. Now, I might have missed something, but > what exactly is the point of this at all? My Xen is running fine with > AMD IOMMU for years now but if i still want to do this, I have to > revert changes 26532, 26531, 26519, 26518 and 25617 (basically all the > AMD/IOMMU changes). No, you rather need to get your firmware fixed, because this > (XEN) IVHD Error: no information for IO-APIC 0x6 is simply not tolerable. But you can, at the expense of security, revert to using the global interrupt remapping table, as pointed out in this same context to others before ("iommu=no-amd-iommu-perdev-intremap"). And yes, we are indeed re-thinking the situation, but in everything to consider doing you need to realize the security implications. See for instance http://lists.xen.org/archives/html/xen-devel/2013-02/msg00591.html and the single IOMMU consideration in http://lists.xen.org/archives/html/xen-devel/2013-02/msg00817.html (but which I don't think will actually work without looking at the PCI bus topology). Feel free to participate in that discussion. Jan _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Fri Feb 15 11:44:24 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 15 Feb 2013 11:44: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 1U6Jgy-0005xO-8V; Fri, 15 Feb 2013 11:43:00 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U6Jgv-0005ww-Av; Fri, 15 Feb 2013 11:42:57 +0000 Received: from [85.158.138.51:23424] by server-3.bemta-3.messagelabs.com id CF/2C-31070-04F1E115; Fri, 15 Feb 2013 11:42:56 +0000 X-Env-Sender: iwj@xenbits.xen.org X-Msg-Ref: server-3.tower-174.messagelabs.com!1360928487!19616301!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.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 10916 invoked from network); 15 Feb 2013 11:41:30 -0000 Received: from mail.xen.org (HELO mail.xen.org) (50.57.168.107) by server-3.tower-174.messagelabs.com with AES256-SHA encrypted SMTP; 15 Feb 2013 11:41:30 -0000 Received: from xenbits.xen.org ([50.57.170.242]) by mail.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U6JfM-0001hk-PT; Fri, 15 Feb 2013 11:41:20 +0000 Received: from iwj by xenbits.xen.org with local (Exim 4.72) (envelope-from ) id 1U6JfM-0003Qu-0l; Fri, 15 Feb 2013 11:41:20 +0000 Date: Fri, 15 Feb 2013 11:41:20 +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 38 (CVE-2013-0215) - oxenstored incorrect handling of certain Xenbus ring states X-BeenThere: xen-users@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-2013-0215 / XSA-38 version 3 oxenstored incorrect handling of certain Xenbus ring states UPDATES IN VERSION 3 ==================== The patch supplied contained an error which would cause a failure when the ring became full. An updated patch is attached. The incremental fix can be found at: http://xenbits.xen.org/hg/staging/xen-unstable.hg/rev/759574df84a6 ISSUE DESCRIPTION ================= The oxenstored daemon (the ocaml version of the xenstore daemon) does not correctly handle unusual or malicious contents in the xenstore ring. A malicious guest can exploit this to cause oxenstored to read past the end of the ring (and very likely crash) or to allocate large amounts of RAM. IMPACT ====== A malicious guest administrator can mount a denial of service attack affecting domain control and management functions. In more detail: A malicious guest administrator can cause oxenstored to crash; after this many host control operations (for example, starting and stopping domains, device hotplug, and some monitoring functions), will be unavailable. Domains which are already running are not directly affected. Such an attacker can also cause a memory exhaustion in the domain running oxenstored; often this will make the host's management functions unavailable. Information leak of control plane data is also theoretically possible. VULNERABLE SYSTEMS ================== Any system running oxenstored is vulnerable. oxenstored was introduced in Xen version 4.1. oxenstored was made the default in Xen 4.2.if a suitable ocaml toolchain was installed at build time. Systems running a 32-bit oxenstored are vulnerable only to the crash and not to the large memory allocation issue. MITIGATION ========== Running the C version of xenstored will avoid this issue. RESOLUTION ========== Applying the attached patch resolves this issue. xsa38.patch Xen 4.1.x, Xen 4.2.x, xen-unstable $ sha256sum xsa38*.patch 9912d3239a6f784418fcec53fad7c316588a421e352462f661cd1070fcf21d4b xsa38.patch $ -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) iQEcBAEBAgAGBQJRHh6yAAoJEIP+FMlX6CvZekUH/AsBw9dg8t2QLsPd391zxX6C XUJGW616979+tVCGVr+ahyRKnE2T598LBD+Vojvi7/jL+k59/j48jOkJIen9NfV6 aawnCrDWICa1Hq4/7xoj1ZagmdQuRuESbdsV6VbzF7v6eBybzKHjhFLNg2cSw6YB Zhay6tqpQGQIZrqWZla0OzNf34gWFZAnD4SL3CzlQaMlUb4gab1qprb2kOHttfcK wlPxy+U3CPppiRHR5Zs9RmGqnRCA9YpZF2JjxuunrZhFtvY1v+udLCiMkdUGblss tKimBDyxC1Qlthye6MTVftvRSsmBmhRJV7R9Wia3s7iAW4KASeobxS+4wicbcHM= =GBLo -----END PGP SIGNATURE----- --=separator Content-Type: application/octet-stream; name="xsa38.patch" Content-Disposition: attachment; filename="xsa38.patch" Content-Transfer-Encoding: base64 ZGlmZiAtLWdpdCBhL3Rvb2xzL29jYW1sL2xpYnMveGIvcGFydGlhbC5tbCBi L3Rvb2xzL29jYW1sL2xpYnMveGIvcGFydGlhbC5tbAppbmRleCAzNTU4ODg5 Li5kNGQxYzdiIDEwMDY0NAotLS0gYS90b29scy9vY2FtbC9saWJzL3hiL3Bh cnRpYWwubWwKKysrIGIvdG9vbHMvb2NhbWwvbGlicy94Yi9wYXJ0aWFsLm1s CkBAIC0yNyw4ICsyNywxNSBAQCBleHRlcm5hbCBoZWFkZXJfc2l6ZTogdW5p dCAtPiBpbnQgPSAic3R1Yl9oZWFkZXJfc2l6ZSIKIGV4dGVybmFsIGhlYWRl cl9vZl9zdHJpbmdfaW50ZXJuYWw6IHN0cmluZyAtPiBpbnQgKiBpbnQgKiBp bnQgKiBpbnQKICAgICAgICAgID0gInN0dWJfaGVhZGVyX29mX3N0cmluZyIK IAorbGV0IHhlbnN0b3JlX3BheWxvYWRfbWF4ID0gNDA5NiAoKiB4ZW4vaW5j bHVkZS9wdWJsaWMvaW8veHNfd2lyZS5oICopCisKIGxldCBvZl9zdHJpbmcg cyA9CiAJbGV0IHRpZCwgcmlkLCBvcGludCwgZGxlbiA9IGhlYWRlcl9vZl9z dHJpbmdfaW50ZXJuYWwgcyBpbgorCSgqIEEgcGFja2V0IHdoaWNoIGlzIGJp Z2dlciB0aGFuIHhlbnN0b3JlX3BheWxvYWRfbWF4IGlzIGlsbGVnYWwuCisJ ICAgVGhpcyB3aWxsIGxlYXZlIHRoZSBndWVzdCBjb25uZWN0aW9uIGlzIGEg YmFkIHN0YXRlIGFuZCB3aWxsCisJICAgYmUgaGFyZCB0byByZWNvdmVyIGZy b20gd2l0aG91dCByZXN0YXJ0aW5nIHRoZSBjb25uZWN0aW9uCisJICAgKGll IHJlYm9vdGluZyB0aGUgZ3Vlc3QpICopCisJbGV0IGRsZW4gPSBtaW4geGVu c3RvcmVfcGF5bG9hZF9tYXggZGxlbiBpbgogCXsKIAkJdGlkID0gdGlkOwog CQlyaWQgPSByaWQ7CkBAIC0zOCw2ICs0NSw3IEBAIGxldCBvZl9zdHJpbmcg cyA9CiAJfQogCiBsZXQgYXBwZW5kIHBrdCBzIHN6ID0KKwlpZiBwa3QubGVu ID4gNDA5NiB0aGVuIGZhaWx3aXRoICJCdWZmZXIuYWRkOiBjYW5ub3QgZ3Jv dyBidWZmZXIiOwogCUJ1ZmZlci5hZGRfc3RyaW5nIHBrdC5idWYgKFN0cmlu Zy5zdWIgcyAwIHN6KQogCiBsZXQgdG9fY29tcGxldGUgcGt0ID0KZGlmZiAt LWdpdCBhL3Rvb2xzL29jYW1sL2xpYnMveGIveHNfcmluZ19zdHVicy5jIGIv dG9vbHMvb2NhbWwvbGlicy94Yi94c19yaW5nX3N0dWJzLmMKaW5kZXggMDA0 MTRjNS4uNDg4OGFjNSAxMDA2NDQKLS0tIGEvdG9vbHMvb2NhbWwvbGlicy94 Yi94c19yaW5nX3N0dWJzLmMKKysrIGIvdG9vbHMvb2NhbWwvbGlicy94Yi94 c19yaW5nX3N0dWJzLmMKQEAgLTM5LDIxICszOSwyMyBAQCBzdGF0aWMgaW50 IHhzX3JpbmdfcmVhZChzdHJ1Y3QgbW1hcF9pbnRlcmZhY2UgKmludGVyZmFj ZSwKICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgY2hhciAqYnVmZmVy LCBpbnQgbGVuKQogewogCXN0cnVjdCB4ZW5zdG9yZV9kb21haW5faW50ZXJm YWNlICppbnRmID0gaW50ZXJmYWNlLT5hZGRyOwotCVhFTlNUT1JFX1JJTkdf SURYIGNvbnMsIHByb2Q7CisJWEVOU1RPUkVfUklOR19JRFggY29ucywgcHJv ZDsgLyogb2Zmc2V0cyBvbmx5ICovCiAJaW50IHRvX3JlYWQ7CiAKLQljb25z ID0gaW50Zi0+cmVxX2NvbnM7Ci0JcHJvZCA9IGludGYtPnJlcV9wcm9kOwor CWNvbnMgPSAqKHZvbGF0aWxlIHVpbnQzMiopJmludGYtPnJlcV9jb25zOwor CXByb2QgPSAqKHZvbGF0aWxlIHVpbnQzMiopJmludGYtPnJlcV9wcm9kOwog CXhlbl9tYigpOwogCWlmIChwcm9kID09IGNvbnMpCiAJCXJldHVybiAwOwot CWlmIChNQVNLX1hFTlNUT1JFX0lEWChwcm9kKSA+IE1BU0tfWEVOU1RPUkVf SURYKGNvbnMpKSAKKwljb25zID0gTUFTS19YRU5TVE9SRV9JRFgoY29ucyk7 CisJcHJvZCA9IE1BU0tfWEVOU1RPUkVfSURYKHByb2QpOworCWlmIChwcm9k ID4gY29ucykKIAkJdG9fcmVhZCA9IHByb2QgLSBjb25zOwogCWVsc2UKLQkJ dG9fcmVhZCA9IFhFTlNUT1JFX1JJTkdfU0laRSAtIE1BU0tfWEVOU1RPUkVf SURYKGNvbnMpOworCQl0b19yZWFkID0gWEVOU1RPUkVfUklOR19TSVpFIC0g Y29uczsKIAlpZiAodG9fcmVhZCA8IGxlbikKIAkJbGVuID0gdG9fcmVhZDsK LQltZW1jcHkoYnVmZmVyLCBpbnRmLT5yZXEgKyBNQVNLX1hFTlNUT1JFX0lE WChjb25zKSwgbGVuKTsKKwltZW1jcHkoYnVmZmVyLCBpbnRmLT5yZXEgKyBj b25zLCBsZW4pOwogCXhlbl9tYigpOwogCWludGYtPnJlcV9jb25zICs9IGxl bjsKIAlyZXR1cm4gbGVuOwpAQCAtNjYsOCArNjgsOCBAQCBzdGF0aWMgaW50 IHhzX3Jpbmdfd3JpdGUoc3RydWN0IG1tYXBfaW50ZXJmYWNlICppbnRlcmZh Y2UsCiAJWEVOU1RPUkVfUklOR19JRFggY29ucywgcHJvZDsKIAlpbnQgY2Fu X3dyaXRlOwogCi0JY29ucyA9IGludGYtPnJzcF9jb25zOwotCXByb2QgPSBp bnRmLT5yc3BfcHJvZDsKKwljb25zID0gKih2b2xhdGlsZSB1aW50MzIqKSZp bnRmLT5yc3BfY29uczsKKwlwcm9kID0gKih2b2xhdGlsZSB1aW50MzIqKSZp bnRmLT5yc3BfcHJvZDsKIAl4ZW5fbWIoKTsKIAlpZiAoIChwcm9kIC0gY29u cykgPj0gWEVOU1RPUkVfUklOR19TSVpFICkKIAkJcmV0dXJuIDA7Cg== --=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 Feb 15 11:44:24 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 15 Feb 2013 11:44: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 1U6Jgy-0005xO-8V; Fri, 15 Feb 2013 11:43:00 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U6Jgv-0005ww-Av; Fri, 15 Feb 2013 11:42:57 +0000 Received: from [85.158.138.51:23424] by server-3.bemta-3.messagelabs.com id CF/2C-31070-04F1E115; Fri, 15 Feb 2013 11:42:56 +0000 X-Env-Sender: iwj@xenbits.xen.org X-Msg-Ref: server-3.tower-174.messagelabs.com!1360928487!19616301!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.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 10916 invoked from network); 15 Feb 2013 11:41:30 -0000 Received: from mail.xen.org (HELO mail.xen.org) (50.57.168.107) by server-3.tower-174.messagelabs.com with AES256-SHA encrypted SMTP; 15 Feb 2013 11:41:30 -0000 Received: from xenbits.xen.org ([50.57.170.242]) by mail.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U6JfM-0001hk-PT; Fri, 15 Feb 2013 11:41:20 +0000 Received: from iwj by xenbits.xen.org with local (Exim 4.72) (envelope-from ) id 1U6JfM-0003Qu-0l; Fri, 15 Feb 2013 11:41:20 +0000 Date: Fri, 15 Feb 2013 11:41:20 +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 38 (CVE-2013-0215) - oxenstored incorrect handling of certain Xenbus ring states X-BeenThere: xen-users@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-2013-0215 / XSA-38 version 3 oxenstored incorrect handling of certain Xenbus ring states UPDATES IN VERSION 3 ==================== The patch supplied contained an error which would cause a failure when the ring became full. An updated patch is attached. The incremental fix can be found at: http://xenbits.xen.org/hg/staging/xen-unstable.hg/rev/759574df84a6 ISSUE DESCRIPTION ================= The oxenstored daemon (the ocaml version of the xenstore daemon) does not correctly handle unusual or malicious contents in the xenstore ring. A malicious guest can exploit this to cause oxenstored to read past the end of the ring (and very likely crash) or to allocate large amounts of RAM. IMPACT ====== A malicious guest administrator can mount a denial of service attack affecting domain control and management functions. In more detail: A malicious guest administrator can cause oxenstored to crash; after this many host control operations (for example, starting and stopping domains, device hotplug, and some monitoring functions), will be unavailable. Domains which are already running are not directly affected. Such an attacker can also cause a memory exhaustion in the domain running oxenstored; often this will make the host's management functions unavailable. Information leak of control plane data is also theoretically possible. VULNERABLE SYSTEMS ================== Any system running oxenstored is vulnerable. oxenstored was introduced in Xen version 4.1. oxenstored was made the default in Xen 4.2.if a suitable ocaml toolchain was installed at build time. Systems running a 32-bit oxenstored are vulnerable only to the crash and not to the large memory allocation issue. MITIGATION ========== Running the C version of xenstored will avoid this issue. RESOLUTION ========== Applying the attached patch resolves this issue. xsa38.patch Xen 4.1.x, Xen 4.2.x, xen-unstable $ sha256sum xsa38*.patch 9912d3239a6f784418fcec53fad7c316588a421e352462f661cd1070fcf21d4b xsa38.patch $ -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) iQEcBAEBAgAGBQJRHh6yAAoJEIP+FMlX6CvZekUH/AsBw9dg8t2QLsPd391zxX6C XUJGW616979+tVCGVr+ahyRKnE2T598LBD+Vojvi7/jL+k59/j48jOkJIen9NfV6 aawnCrDWICa1Hq4/7xoj1ZagmdQuRuESbdsV6VbzF7v6eBybzKHjhFLNg2cSw6YB Zhay6tqpQGQIZrqWZla0OzNf34gWFZAnD4SL3CzlQaMlUb4gab1qprb2kOHttfcK wlPxy+U3CPppiRHR5Zs9RmGqnRCA9YpZF2JjxuunrZhFtvY1v+udLCiMkdUGblss tKimBDyxC1Qlthye6MTVftvRSsmBmhRJV7R9Wia3s7iAW4KASeobxS+4wicbcHM= =GBLo -----END PGP SIGNATURE----- --=separator Content-Type: application/octet-stream; name="xsa38.patch" Content-Disposition: attachment; filename="xsa38.patch" Content-Transfer-Encoding: base64 ZGlmZiAtLWdpdCBhL3Rvb2xzL29jYW1sL2xpYnMveGIvcGFydGlhbC5tbCBi L3Rvb2xzL29jYW1sL2xpYnMveGIvcGFydGlhbC5tbAppbmRleCAzNTU4ODg5 Li5kNGQxYzdiIDEwMDY0NAotLS0gYS90b29scy9vY2FtbC9saWJzL3hiL3Bh cnRpYWwubWwKKysrIGIvdG9vbHMvb2NhbWwvbGlicy94Yi9wYXJ0aWFsLm1s CkBAIC0yNyw4ICsyNywxNSBAQCBleHRlcm5hbCBoZWFkZXJfc2l6ZTogdW5p dCAtPiBpbnQgPSAic3R1Yl9oZWFkZXJfc2l6ZSIKIGV4dGVybmFsIGhlYWRl cl9vZl9zdHJpbmdfaW50ZXJuYWw6IHN0cmluZyAtPiBpbnQgKiBpbnQgKiBp bnQgKiBpbnQKICAgICAgICAgID0gInN0dWJfaGVhZGVyX29mX3N0cmluZyIK IAorbGV0IHhlbnN0b3JlX3BheWxvYWRfbWF4ID0gNDA5NiAoKiB4ZW4vaW5j bHVkZS9wdWJsaWMvaW8veHNfd2lyZS5oICopCisKIGxldCBvZl9zdHJpbmcg cyA9CiAJbGV0IHRpZCwgcmlkLCBvcGludCwgZGxlbiA9IGhlYWRlcl9vZl9z dHJpbmdfaW50ZXJuYWwgcyBpbgorCSgqIEEgcGFja2V0IHdoaWNoIGlzIGJp Z2dlciB0aGFuIHhlbnN0b3JlX3BheWxvYWRfbWF4IGlzIGlsbGVnYWwuCisJ ICAgVGhpcyB3aWxsIGxlYXZlIHRoZSBndWVzdCBjb25uZWN0aW9uIGlzIGEg YmFkIHN0YXRlIGFuZCB3aWxsCisJICAgYmUgaGFyZCB0byByZWNvdmVyIGZy b20gd2l0aG91dCByZXN0YXJ0aW5nIHRoZSBjb25uZWN0aW9uCisJICAgKGll IHJlYm9vdGluZyB0aGUgZ3Vlc3QpICopCisJbGV0IGRsZW4gPSBtaW4geGVu c3RvcmVfcGF5bG9hZF9tYXggZGxlbiBpbgogCXsKIAkJdGlkID0gdGlkOwog CQlyaWQgPSByaWQ7CkBAIC0zOCw2ICs0NSw3IEBAIGxldCBvZl9zdHJpbmcg cyA9CiAJfQogCiBsZXQgYXBwZW5kIHBrdCBzIHN6ID0KKwlpZiBwa3QubGVu ID4gNDA5NiB0aGVuIGZhaWx3aXRoICJCdWZmZXIuYWRkOiBjYW5ub3QgZ3Jv dyBidWZmZXIiOwogCUJ1ZmZlci5hZGRfc3RyaW5nIHBrdC5idWYgKFN0cmlu Zy5zdWIgcyAwIHN6KQogCiBsZXQgdG9fY29tcGxldGUgcGt0ID0KZGlmZiAt LWdpdCBhL3Rvb2xzL29jYW1sL2xpYnMveGIveHNfcmluZ19zdHVicy5jIGIv dG9vbHMvb2NhbWwvbGlicy94Yi94c19yaW5nX3N0dWJzLmMKaW5kZXggMDA0 MTRjNS4uNDg4OGFjNSAxMDA2NDQKLS0tIGEvdG9vbHMvb2NhbWwvbGlicy94 Yi94c19yaW5nX3N0dWJzLmMKKysrIGIvdG9vbHMvb2NhbWwvbGlicy94Yi94 c19yaW5nX3N0dWJzLmMKQEAgLTM5LDIxICszOSwyMyBAQCBzdGF0aWMgaW50 IHhzX3JpbmdfcmVhZChzdHJ1Y3QgbW1hcF9pbnRlcmZhY2UgKmludGVyZmFj ZSwKICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgY2hhciAqYnVmZmVy LCBpbnQgbGVuKQogewogCXN0cnVjdCB4ZW5zdG9yZV9kb21haW5faW50ZXJm YWNlICppbnRmID0gaW50ZXJmYWNlLT5hZGRyOwotCVhFTlNUT1JFX1JJTkdf SURYIGNvbnMsIHByb2Q7CisJWEVOU1RPUkVfUklOR19JRFggY29ucywgcHJv ZDsgLyogb2Zmc2V0cyBvbmx5ICovCiAJaW50IHRvX3JlYWQ7CiAKLQljb25z ID0gaW50Zi0+cmVxX2NvbnM7Ci0JcHJvZCA9IGludGYtPnJlcV9wcm9kOwor CWNvbnMgPSAqKHZvbGF0aWxlIHVpbnQzMiopJmludGYtPnJlcV9jb25zOwor CXByb2QgPSAqKHZvbGF0aWxlIHVpbnQzMiopJmludGYtPnJlcV9wcm9kOwog CXhlbl9tYigpOwogCWlmIChwcm9kID09IGNvbnMpCiAJCXJldHVybiAwOwot CWlmIChNQVNLX1hFTlNUT1JFX0lEWChwcm9kKSA+IE1BU0tfWEVOU1RPUkVf SURYKGNvbnMpKSAKKwljb25zID0gTUFTS19YRU5TVE9SRV9JRFgoY29ucyk7 CisJcHJvZCA9IE1BU0tfWEVOU1RPUkVfSURYKHByb2QpOworCWlmIChwcm9k ID4gY29ucykKIAkJdG9fcmVhZCA9IHByb2QgLSBjb25zOwogCWVsc2UKLQkJ dG9fcmVhZCA9IFhFTlNUT1JFX1JJTkdfU0laRSAtIE1BU0tfWEVOU1RPUkVf SURYKGNvbnMpOworCQl0b19yZWFkID0gWEVOU1RPUkVfUklOR19TSVpFIC0g Y29uczsKIAlpZiAodG9fcmVhZCA8IGxlbikKIAkJbGVuID0gdG9fcmVhZDsK LQltZW1jcHkoYnVmZmVyLCBpbnRmLT5yZXEgKyBNQVNLX1hFTlNUT1JFX0lE WChjb25zKSwgbGVuKTsKKwltZW1jcHkoYnVmZmVyLCBpbnRmLT5yZXEgKyBj b25zLCBsZW4pOwogCXhlbl9tYigpOwogCWludGYtPnJlcV9jb25zICs9IGxl bjsKIAlyZXR1cm4gbGVuOwpAQCAtNjYsOCArNjgsOCBAQCBzdGF0aWMgaW50 IHhzX3Jpbmdfd3JpdGUoc3RydWN0IG1tYXBfaW50ZXJmYWNlICppbnRlcmZh Y2UsCiAJWEVOU1RPUkVfUklOR19JRFggY29ucywgcHJvZDsKIAlpbnQgY2Fu X3dyaXRlOwogCi0JY29ucyA9IGludGYtPnJzcF9jb25zOwotCXByb2QgPSBp bnRmLT5yc3BfcHJvZDsKKwljb25zID0gKih2b2xhdGlsZSB1aW50MzIqKSZp bnRmLT5yc3BfY29uczsKKwlwcm9kID0gKih2b2xhdGlsZSB1aW50MzIqKSZp bnRmLT5yc3BfcHJvZDsKIAl4ZW5fbWIoKTsKIAlpZiAoIChwcm9kIC0gY29u cykgPj0gWEVOU1RPUkVfUklOR19TSVpFICkKIAkJcmV0dXJuIDA7Cg== --=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 Feb 15 13:55:29 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 15 Feb 2013 13:55: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 1U6Lk4-0006OT-Ox; Fri, 15 Feb 2013 13:54:20 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U6Lk3-0006OO-3Q for xen-users@lists.xen.org; Fri, 15 Feb 2013 13:54:19 +0000 Received: from [85.158.137.99:30384] by server-4.bemta-3.messagelabs.com id 18/B1-17521-A0E3E115; Fri, 15 Feb 2013 13:54:18 +0000 X-Env-Sender: matthias.kannenberg@googlemail.com X-Msg-Ref: server-4.tower-217.messagelabs.com!1360936457!21595091!1 X-Originating-IP: [209.85.212.182] X-SpamReason: No, hits=0.3 required=7.0 tests=RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 24867 invoked from network); 15 Feb 2013 13:54:17 -0000 Received: from mail-wi0-f182.google.com (HELO mail-wi0-f182.google.com) (209.85.212.182) by server-4.tower-217.messagelabs.com with RC4-SHA encrypted SMTP; 15 Feb 2013 13:54:17 -0000 Received: by mail-wi0-f182.google.com with SMTP id hi18so1182872wib.9 for ; Fri, 15 Feb 2013 05:54:17 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=20120113; h=x-received:mime-version:in-reply-to:references:from:date:message-id :subject:to:cc:content-type; bh=//MuVT/UBcATqnhVo4x7VHZsxL9YOMo4AVFwnUUAu94=; b=yBhotNLkiic0sqmefJ0oTE5nJqQya6KzohU9KXPyrAHn8+Cpajx0AZqllJRuP9+oY4 olB2ziHU5T9RvxpSbzIZMdUtFiGQ3r+QPBFvVlmETexy6YKMidyx4FeHr7B80yUaACHp bIAjyxgWrrwRPasRGIvnzU8Q1FecOI53Sxe9TeAgNtcxNOoyhlr7gPtuxxfCCyD/51XT TwVSFGlVO8Wy46/O5++yU7B9LVsTWMSdEmMuy526ub9T20FI3C8RkViDIv5L9RjvGuzc BvJCdx2JoPUGm8uBa5Z8jLMUYh5m/wQTe6RDPHzEdLh7n/T+RVfL/TcVACKjONv9tQb1 oomA== X-Received: by 10.194.109.10 with SMTP id ho10mr4475819wjb.16.1360936446703; Fri, 15 Feb 2013 05:54:06 -0800 (PST) MIME-Version: 1.0 Received: by 10.194.80.68 with HTTP; Fri, 15 Feb 2013 05:53:45 -0800 (PST) In-Reply-To: <511DFB0C02000078000BE94B@nat28.tlf.novell.com> References: <1360581739.29432.115.camel@zakaz.uk.xensource.com> <511A0E9C02000078000BD9EA@nat28.tlf.novell.com> <511B5D5B02000078000BDE76@nat28.tlf.novell.com> <511DFB0C02000078000BE94B@nat28.tlf.novell.com> From: Matthias Date: Fri, 15 Feb 2013 14:53:45 +0100 Message-ID: To: Jan Beulich Cc: "xen-users@lists.xen.org" , Boris Ostrovsky , Ian Campbell Subject: Re: [Xen-users] Latest AMD, IOMMU Security Change causing CPU0 Panic and general Problems with AMD+IOMMU changes X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: 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, you were right. After your hint about my firmware, I did a BIOS update which ultimately fixed my issue and now IOMMU is activated with your patches, too. Sorry that I haven't thought about this earlier. So in general I think this is solved for me. My xen now behaves rather strange (random HDD / DMA read / write errors), but i can reproduce this with and without your patches so I think this is a whole other story. Thank you for your help 2013/2/15 Jan Beulich : >>>> On 15.02.13 at 03:55, Matthias wrote: >> Unfortunatly, the changes disable my IOMMU rendering pci and vga >> passthrough unusable for me. Now, I might have missed something, but >> what exactly is the point of this at all? My Xen is running fine with >> AMD IOMMU for years now but if i still want to do this, I have to >> revert changes 26532, 26531, 26519, 26518 and 25617 (basically all the >> AMD/IOMMU changes). > > No, you rather need to get your firmware fixed, because this > >> (XEN) IVHD Error: no information for IO-APIC 0x6 > > is simply not tolerable. But you can, at the expense of security, > revert to using the global interrupt remapping table, as pointed > out in this same context to others before > ("iommu=no-amd-iommu-perdev-intremap"). > > And yes, we are indeed re-thinking the situation, but in everything > to consider doing you need to realize the security implications. See > for instance > http://lists.xen.org/archives/html/xen-devel/2013-02/msg00591.html > and the single IOMMU consideration in > http://lists.xen.org/archives/html/xen-devel/2013-02/msg00817.html > (but which I don't think will actually work without looking at the PCI > bus topology). Feel free to participate in that discussion. > > Jan > _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Fri Feb 15 13:55:29 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 15 Feb 2013 13:55: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 1U6Lk4-0006OT-Ox; Fri, 15 Feb 2013 13:54:20 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U6Lk3-0006OO-3Q for xen-users@lists.xen.org; Fri, 15 Feb 2013 13:54:19 +0000 Received: from [85.158.137.99:30384] by server-4.bemta-3.messagelabs.com id 18/B1-17521-A0E3E115; Fri, 15 Feb 2013 13:54:18 +0000 X-Env-Sender: matthias.kannenberg@googlemail.com X-Msg-Ref: server-4.tower-217.messagelabs.com!1360936457!21595091!1 X-Originating-IP: [209.85.212.182] X-SpamReason: No, hits=0.3 required=7.0 tests=RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 24867 invoked from network); 15 Feb 2013 13:54:17 -0000 Received: from mail-wi0-f182.google.com (HELO mail-wi0-f182.google.com) (209.85.212.182) by server-4.tower-217.messagelabs.com with RC4-SHA encrypted SMTP; 15 Feb 2013 13:54:17 -0000 Received: by mail-wi0-f182.google.com with SMTP id hi18so1182872wib.9 for ; Fri, 15 Feb 2013 05:54:17 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=20120113; h=x-received:mime-version:in-reply-to:references:from:date:message-id :subject:to:cc:content-type; bh=//MuVT/UBcATqnhVo4x7VHZsxL9YOMo4AVFwnUUAu94=; b=yBhotNLkiic0sqmefJ0oTE5nJqQya6KzohU9KXPyrAHn8+Cpajx0AZqllJRuP9+oY4 olB2ziHU5T9RvxpSbzIZMdUtFiGQ3r+QPBFvVlmETexy6YKMidyx4FeHr7B80yUaACHp bIAjyxgWrrwRPasRGIvnzU8Q1FecOI53Sxe9TeAgNtcxNOoyhlr7gPtuxxfCCyD/51XT TwVSFGlVO8Wy46/O5++yU7B9LVsTWMSdEmMuy526ub9T20FI3C8RkViDIv5L9RjvGuzc BvJCdx2JoPUGm8uBa5Z8jLMUYh5m/wQTe6RDPHzEdLh7n/T+RVfL/TcVACKjONv9tQb1 oomA== X-Received: by 10.194.109.10 with SMTP id ho10mr4475819wjb.16.1360936446703; Fri, 15 Feb 2013 05:54:06 -0800 (PST) MIME-Version: 1.0 Received: by 10.194.80.68 with HTTP; Fri, 15 Feb 2013 05:53:45 -0800 (PST) In-Reply-To: <511DFB0C02000078000BE94B@nat28.tlf.novell.com> References: <1360581739.29432.115.camel@zakaz.uk.xensource.com> <511A0E9C02000078000BD9EA@nat28.tlf.novell.com> <511B5D5B02000078000BDE76@nat28.tlf.novell.com> <511DFB0C02000078000BE94B@nat28.tlf.novell.com> From: Matthias Date: Fri, 15 Feb 2013 14:53:45 +0100 Message-ID: To: Jan Beulich Cc: "xen-users@lists.xen.org" , Boris Ostrovsky , Ian Campbell Subject: Re: [Xen-users] Latest AMD, IOMMU Security Change causing CPU0 Panic and general Problems with AMD+IOMMU changes X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: 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, you were right. After your hint about my firmware, I did a BIOS update which ultimately fixed my issue and now IOMMU is activated with your patches, too. Sorry that I haven't thought about this earlier. So in general I think this is solved for me. My xen now behaves rather strange (random HDD / DMA read / write errors), but i can reproduce this with and without your patches so I think this is a whole other story. Thank you for your help 2013/2/15 Jan Beulich : >>>> On 15.02.13 at 03:55, Matthias wrote: >> Unfortunatly, the changes disable my IOMMU rendering pci and vga >> passthrough unusable for me. Now, I might have missed something, but >> what exactly is the point of this at all? My Xen is running fine with >> AMD IOMMU for years now but if i still want to do this, I have to >> revert changes 26532, 26531, 26519, 26518 and 25617 (basically all the >> AMD/IOMMU changes). > > No, you rather need to get your firmware fixed, because this > >> (XEN) IVHD Error: no information for IO-APIC 0x6 > > is simply not tolerable. But you can, at the expense of security, > revert to using the global interrupt remapping table, as pointed > out in this same context to others before > ("iommu=no-amd-iommu-perdev-intremap"). > > And yes, we are indeed re-thinking the situation, but in everything > to consider doing you need to realize the security implications. See > for instance > http://lists.xen.org/archives/html/xen-devel/2013-02/msg00591.html > and the single IOMMU consideration in > http://lists.xen.org/archives/html/xen-devel/2013-02/msg00817.html > (but which I don't think will actually work without looking at the PCI > bus topology). Feel free to participate in that discussion. > > Jan > _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Fri Feb 15 15:39:05 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 15 Feb 2013 15:39: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 1U6NME-0003WD-3A; Fri, 15 Feb 2013 15:37:50 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U6NMC-0003Vy-1h for xen-users@lists.xen.org; Fri, 15 Feb 2013 15:37:48 +0000 Received: from [85.158.139.211:64702] by server-7.bemta-5.messagelabs.com id 5E/EF-11121-A465E115; Fri, 15 Feb 2013 15:37:46 +0000 X-Env-Sender: jaceksburghardt@gmail.com X-Msg-Ref: server-4.tower-206.messagelabs.com!1360942664!22665145!1 X-Originating-IP: [209.85.223.182] 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.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 10328 invoked from network); 15 Feb 2013 15:37:46 -0000 Received: from mail-ie0-f182.google.com (HELO mail-ie0-f182.google.com) (209.85.223.182) by server-4.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 15 Feb 2013 15:37:46 -0000 Received: by mail-ie0-f182.google.com with SMTP id k14so4901810iea.13 for ; Fri, 15 Feb 2013 07:37:44 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:date:message-id:subject:from:to :content-type; bh=Bouq43kSA8ztqjF+aCY3fc8f2aBSXNmD+19NUfIFr1I=; b=KH5FjCz+XYrutYfcV4aXHIe2wKir+tTicptoCwZKpuQd4OFu8GQ1QsLFbywg9cQenB kCUvZxiNiGRlMyJWKY4nbdl4nHSx2tEb64htkgZdc9rezc/lsKRK24QOxafU7qtiIXYy VRP3ewSs6kKpYCDesjUkc/dwZt5YyKtg6OYcToh1OkoZW3KQ8IFlhjeJZXjuuXCFyi+V LSDDt5viXU8jbPCMVxcpUKerkv9uAfspkWGE0PjhtyrhEYdeprxVN3tHbXzCvYEJ9b08 VaJiwH1tHc4zrj+0kL72biIPWbsLm08LaJxmwKmAxSpmyBiW6WcaaMbI9lSnVLs7Fma4 bHCA== MIME-Version: 1.0 X-Received: by 10.50.41.167 with SMTP id g7mr1978135igl.90.1360942648655; Fri, 15 Feb 2013 07:37:28 -0800 (PST) Received: by 10.42.41.5 with HTTP; Fri, 15 Feb 2013 07:37:28 -0800 (PST) Date: Fri, 15 Feb 2013 08:37:28 -0700 Message-ID: From: jacek burghardt To: xen-users Subject: [Xen-users] 3.7.8 kernel xen specific 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="===============5857834656626733502==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============5857834656626733502== Content-Type: multipart/alternative; boundary=14dae93409b92200ad04d5c52755 --14dae93409b92200ad04d5c52755 Content-Type: text/plain; charset=ISO-8859-1 I want to upgrade my kernel to 3.7.8 and looking for pointers were I can get xen specific patches such as acpci. I tried to patch kernel from Konrad git but kernel had caused issues with crashing. --14dae93409b92200ad04d5c52755 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable I want to upgrade my kernel to 3.7.8 and looking for=A0pointers=A0were I ca= n get xen specific patches such as acpci. I tried to patch kernel =A0from= =A0Konrad=A0git but kernel had caused issues with crashing.=A0 --14dae93409b92200ad04d5c52755-- --===============5857834656626733502== 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 --===============5857834656626733502==-- From xen-users-bounces@lists.xen.org Fri Feb 15 15:39:05 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 15 Feb 2013 15:39: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 1U6NME-0003WD-3A; Fri, 15 Feb 2013 15:37:50 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U6NMC-0003Vy-1h for xen-users@lists.xen.org; Fri, 15 Feb 2013 15:37:48 +0000 Received: from [85.158.139.211:64702] by server-7.bemta-5.messagelabs.com id 5E/EF-11121-A465E115; Fri, 15 Feb 2013 15:37:46 +0000 X-Env-Sender: jaceksburghardt@gmail.com X-Msg-Ref: server-4.tower-206.messagelabs.com!1360942664!22665145!1 X-Originating-IP: [209.85.223.182] 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.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 10328 invoked from network); 15 Feb 2013 15:37:46 -0000 Received: from mail-ie0-f182.google.com (HELO mail-ie0-f182.google.com) (209.85.223.182) by server-4.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 15 Feb 2013 15:37:46 -0000 Received: by mail-ie0-f182.google.com with SMTP id k14so4901810iea.13 for ; Fri, 15 Feb 2013 07:37:44 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:date:message-id:subject:from:to :content-type; bh=Bouq43kSA8ztqjF+aCY3fc8f2aBSXNmD+19NUfIFr1I=; b=KH5FjCz+XYrutYfcV4aXHIe2wKir+tTicptoCwZKpuQd4OFu8GQ1QsLFbywg9cQenB kCUvZxiNiGRlMyJWKY4nbdl4nHSx2tEb64htkgZdc9rezc/lsKRK24QOxafU7qtiIXYy VRP3ewSs6kKpYCDesjUkc/dwZt5YyKtg6OYcToh1OkoZW3KQ8IFlhjeJZXjuuXCFyi+V LSDDt5viXU8jbPCMVxcpUKerkv9uAfspkWGE0PjhtyrhEYdeprxVN3tHbXzCvYEJ9b08 VaJiwH1tHc4zrj+0kL72biIPWbsLm08LaJxmwKmAxSpmyBiW6WcaaMbI9lSnVLs7Fma4 bHCA== MIME-Version: 1.0 X-Received: by 10.50.41.167 with SMTP id g7mr1978135igl.90.1360942648655; Fri, 15 Feb 2013 07:37:28 -0800 (PST) Received: by 10.42.41.5 with HTTP; Fri, 15 Feb 2013 07:37:28 -0800 (PST) Date: Fri, 15 Feb 2013 08:37:28 -0700 Message-ID: From: jacek burghardt To: xen-users Subject: [Xen-users] 3.7.8 kernel xen specific 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="===============5857834656626733502==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============5857834656626733502== Content-Type: multipart/alternative; boundary=14dae93409b92200ad04d5c52755 --14dae93409b92200ad04d5c52755 Content-Type: text/plain; charset=ISO-8859-1 I want to upgrade my kernel to 3.7.8 and looking for pointers were I can get xen specific patches such as acpci. I tried to patch kernel from Konrad git but kernel had caused issues with crashing. --14dae93409b92200ad04d5c52755 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable I want to upgrade my kernel to 3.7.8 and looking for=A0pointers=A0were I ca= n get xen specific patches such as acpci. I tried to patch kernel =A0from= =A0Konrad=A0git but kernel had caused issues with crashing.=A0 --14dae93409b92200ad04d5c52755-- --===============5857834656626733502== 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 --===============5857834656626733502==-- From xen-users-bounces@lists.xen.org Fri Feb 15 23:45:35 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 15 Feb 2013 23:45: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 1U6Uwn-0001YR-AZ; Fri, 15 Feb 2013 23:44:05 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U6Uwl-0001YM-8y for xen-users@lists.xen.org; Fri, 15 Feb 2013 23:44:03 +0000 Received: from [85.158.137.99:34725] by server-10.bemta-3.messagelabs.com id C3/60-10609-248CE115; Fri, 15 Feb 2013 23:44:02 +0000 X-Env-Sender: mcbeagle@gmx.de X-Msg-Ref: server-16.tower-217.messagelabs.com!1360971841!21642686!1 X-Originating-IP: [212.227.17.20] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogMjEyLjIyNy4xNy4yMCA9PiAzNDA1Nw==\n, ML_RADAR_SPEW_LINKS_14,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 16591 invoked from network); 15 Feb 2013 23:44:01 -0000 Received: from mout.gmx.net (HELO mout.gmx.net) (212.227.17.20) by server-16.tower-217.messagelabs.com with SMTP; 15 Feb 2013 23:44:01 -0000 Received: from mailout-de.gmx.net ([10.1.76.24]) by mrigmx.server.lan (mrigmx001) with ESMTP (Nemesis) id 0MRQbm-1UUea107cO-00Seo9 for ; Sat, 16 Feb 2013 00:44:01 +0100 Received: (qmail invoked by alias); 15 Feb 2013 23:44:00 -0000 Received: from g224186051.adsl.alicedsl.de (EHLO sheik-lin.localnet) [92.224.186.51] by mail.gmx.net (mp024) with SMTP; 16 Feb 2013 00:44:00 +0100 X-Authenticated: #432297 X-Provags-ID: V01U2FsdGVkX18WyOlJH70WZP8jkuoGVARW9BRImRkx2vnKs9SYy9 S3623Z2wX/fXjT From: Hans Mueller To: xen-users@lists.xen.org Date: Sat, 16 Feb 2013 00:43:59 +0100 Message-ID: <2020185.9Jm3ie67Tx@sheik-lin> User-Agent: KMail/4.9.5 (Linux/3.6.11-gentoo-c3; KDE/4.9.5; x86_64; ; ) In-Reply-To: References: MIME-Version: 1.0 X-Y-GMX-Trusted: 0 Subject: Re: [Xen-users] IVHD error, AMD-Vi gets disabled (4.1.3-3ubuntu1.3) X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: 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 Wednesday, 13. February 2013 15:17:54 Andreas Falck wrote: > Hello, > > I have a system running ubuntu12.10 with xen 4.1.3, which I believe was > recently upgraded from xen 4.1.2 via the normal ubuntu 'apt-get upgrade' > path. 2 AMD opteron 6134 cpus, supermicro H8DG6 motherboard. > > Recently I noticed that AMD-Vi gets disabled at boot, which didn't happen > before. > > From 'xm dmesg': > > (XEN) Command line: placeholder amd-iommu-debug iommu=verbose iommu=1 > apic=debug iommu_inclusive_mapping=1 > [...] > (XEN) IVHD Error: Conflicting IO-APIC 0x0 entries > (XEN) AMD-Vi: Error initialization > (XEN) I/O virtualisation disabled looks like related to the XSA-36 http://lists.xen.org/archives/html/xen-announce/2013-02/msg00002.html _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Fri Feb 15 23:45:35 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 15 Feb 2013 23:45: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 1U6Uwn-0001YR-AZ; Fri, 15 Feb 2013 23:44:05 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U6Uwl-0001YM-8y for xen-users@lists.xen.org; Fri, 15 Feb 2013 23:44:03 +0000 Received: from [85.158.137.99:34725] by server-10.bemta-3.messagelabs.com id C3/60-10609-248CE115; Fri, 15 Feb 2013 23:44:02 +0000 X-Env-Sender: mcbeagle@gmx.de X-Msg-Ref: server-16.tower-217.messagelabs.com!1360971841!21642686!1 X-Originating-IP: [212.227.17.20] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogMjEyLjIyNy4xNy4yMCA9PiAzNDA1Nw==\n, ML_RADAR_SPEW_LINKS_14,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 16591 invoked from network); 15 Feb 2013 23:44:01 -0000 Received: from mout.gmx.net (HELO mout.gmx.net) (212.227.17.20) by server-16.tower-217.messagelabs.com with SMTP; 15 Feb 2013 23:44:01 -0000 Received: from mailout-de.gmx.net ([10.1.76.24]) by mrigmx.server.lan (mrigmx001) with ESMTP (Nemesis) id 0MRQbm-1UUea107cO-00Seo9 for ; Sat, 16 Feb 2013 00:44:01 +0100 Received: (qmail invoked by alias); 15 Feb 2013 23:44:00 -0000 Received: from g224186051.adsl.alicedsl.de (EHLO sheik-lin.localnet) [92.224.186.51] by mail.gmx.net (mp024) with SMTP; 16 Feb 2013 00:44:00 +0100 X-Authenticated: #432297 X-Provags-ID: V01U2FsdGVkX18WyOlJH70WZP8jkuoGVARW9BRImRkx2vnKs9SYy9 S3623Z2wX/fXjT From: Hans Mueller To: xen-users@lists.xen.org Date: Sat, 16 Feb 2013 00:43:59 +0100 Message-ID: <2020185.9Jm3ie67Tx@sheik-lin> User-Agent: KMail/4.9.5 (Linux/3.6.11-gentoo-c3; KDE/4.9.5; x86_64; ; ) In-Reply-To: References: MIME-Version: 1.0 X-Y-GMX-Trusted: 0 Subject: Re: [Xen-users] IVHD error, AMD-Vi gets disabled (4.1.3-3ubuntu1.3) X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: 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 Wednesday, 13. February 2013 15:17:54 Andreas Falck wrote: > Hello, > > I have a system running ubuntu12.10 with xen 4.1.3, which I believe was > recently upgraded from xen 4.1.2 via the normal ubuntu 'apt-get upgrade' > path. 2 AMD opteron 6134 cpus, supermicro H8DG6 motherboard. > > Recently I noticed that AMD-Vi gets disabled at boot, which didn't happen > before. > > From 'xm dmesg': > > (XEN) Command line: placeholder amd-iommu-debug iommu=verbose iommu=1 > apic=debug iommu_inclusive_mapping=1 > [...] > (XEN) IVHD Error: Conflicting IO-APIC 0x0 entries > (XEN) AMD-Vi: Error initialization > (XEN) I/O virtualisation disabled looks like related to the XSA-36 http://lists.xen.org/archives/html/xen-announce/2013-02/msg00002.html _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Sat Feb 16 08:00:26 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sat, 16 Feb 2013 08:00: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 1U6cfX-0004MH-GQ; Sat, 16 Feb 2013 07:58:47 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U6cfV-0004MC-CF for xen-users@lists.xen.org; Sat, 16 Feb 2013 07:58:45 +0000 Received: from [85.158.143.99:5744] by server-3.bemta-4.messagelabs.com id E0/62-08920-43C3F115; Sat, 16 Feb 2013 07:58:44 +0000 X-Env-Sender: falck.andreas.lists@gmail.com X-Msg-Ref: server-14.tower-216.messagelabs.com!1361001523!18156450!1 X-Originating-IP: [209.85.217.180] X-SpamReason: No, hits=2.2 required=7.0 tests=BODY_RANDOMQ,HTML_20_30, HTML_MESSAGE,ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 15337 invoked from network); 16 Feb 2013 07:58:43 -0000 Received: from mail-lb0-f180.google.com (HELO mail-lb0-f180.google.com) (209.85.217.180) by server-14.tower-216.messagelabs.com with RC4-SHA encrypted SMTP; 16 Feb 2013 07:58:43 -0000 Received: by mail-lb0-f180.google.com with SMTP id q12so3157076lbc.11 for ; Fri, 15 Feb 2013 23:58:42 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:content-type; bh=+30eLOGcsDsMu02QKZ2BzapgTq1CyWO5pLDU5zadPYo=; b=zcryfJM0JlSGHyt5mf7kq0jOUvmXbH9+0V/WU+52stpKT/Om7BTK37P5+1M1pmiK9Y 7YHX0dNr93wTcZa/+4AjDV5TwpwRDY/pN5wTrr46JwwB8DQ6Q0jEuOZlyu9zVKya1DSA 2ABB0/50dSlzmkQirL770I18nwNNuxrgmRlfzeQGEVdcZokvxv3Am7ZIBeqBVjBfQbrE AYldXw6vKLx0YUw82JRvAuJNM8U6nj1/PXVKPXlQuaR6fJE6RDhPFxcgw7Oe1KFdmnjA 9RN+vJxcC4xV5I0iwRCCj9ZcOwhU77eWxb0TeCemCtCV+j5O8a+TQjqDZkNwy0e+z463 xc1A== MIME-Version: 1.0 X-Received: by 10.152.46.17 with SMTP id r17mr4511597lam.47.1361001522740; Fri, 15 Feb 2013 23:58:42 -0800 (PST) Received: by 10.114.21.230 with HTTP; Fri, 15 Feb 2013 23:58:42 -0800 (PST) In-Reply-To: <1360836221.20449.312.camel@zakaz.uk.xensource.com> References: <1360836221.20449.312.camel@zakaz.uk.xensource.com> Date: Sat, 16 Feb 2013 08:58:42 +0100 Message-ID: From: Andreas Falck To: "xen-users@lists.xen.org" Subject: Re: [Xen-users] IVHD error, AMD-Vi gets disabled (4.1.3-3ubuntu1.3) X-BeenThere: xen-users@lists.xen.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="===============9041283111771152429==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============9041283111771152429== Content-Type: multipart/alternative; boundary=bcaec55241064d3c0304d5d2dc4e --bcaec55241064d3c0304d5d2dc4e Content-Type: text/plain; charset=ISO-8859-1 Ian and Hans are probably right. Adding the "iommu=amd-iommu-global-intremap" option to xen enables the IOMMU with warnings. A BIOS update did NOT work however, to the latest one available from Supermicro (R 3.0, Bios Date 09/10/2012). This would suggest that Supermicro mainboard models H8DG6 / H8DGi / H8DG6-F / H8DGi-F are broken in this respect, at least with current available BIOSes. I will stick with the insecure workaround, but I'll notify Supermicro about the problem. Thanks 2013/2/14 Ian Campbell >On Wed, 2013-02-13 at 14:17 +0000, Andreas Falck wrote: >> >> Could it be a xen bug (I know that my system is somewhat unusual), a >> old BIOS bug interacting with newer xen or an aqcuired hardware error? >> I'll of course provide more logs if needed. >Almost certainly the middle one IMHO, as bugs get fixed in Xen it >becomes less tolerant of dubious BIOS tables. 2013/2/16 Hans Mueller >On Wednesday, 13. February 2013 15:17:54 Andreas Falck wrote: >> [...] >> (XEN) IVHD Error: Conflicting IO-APIC 0x0 entries >> (XEN) AMD-Vi: Error initialization >> (XEN) I/O virtualisation disabled >looks like related to the XSA-36 >http://lists.xen.org/archives/html/xen-announce/2013-02/msg00002.html --bcaec55241064d3c0304d5d2dc4e Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Ian and Hans are probably right. Adding the "iommu=3Damd-iommu-global-= intremap" option to xen enables the IOMMU with warnings.

A BIOS= update did NOT work however, to the latest one available from Supermicro (= R 3.0, Bios Date 09/10/2012). This would suggest that Supermicro mainboard = models H8DG6 / H8DGi / H8DG6-F / H8DGi-F are broken in this respect, at lea= st with current available BIOSes.

I will stick with the insecure workaround, but I'll notify Supermic= ro about the problem.

Thanks

2013/= 2/14 Ian Campbell
>On Wed, 2013-02-13 at 14:17 +0000, Andreas Falck = wrote:
>>
>> Could it be a xen bug (I know that my system is somewh= at unusual), a
>> old BIOS bug interacting with newer xen or an aq= cuired hardware error?
>> I'll of course provide more logs if = needed.
=A0
>Almost certainly the middle one IMHO, as bugs get fixed in = Xen it
>becomes less tolerant of dubious BIOS tables.

= 2013/2/16 Hans Mueller
>On Wednesday, 13. February 2013 15:17:54 Andr= eas Falck wrote:
>> [...]
>> (XEN) IVHD Error: Conflicting IO-APIC 0x0 entries
>> (XEN) AMD-Vi: Error initialization
>> (XEN) I/O virtualisation disabled

>looks like related to the XSA-36
>http://lists.xen.org/archives/html/xen-announc= e/2013-02/msg00002.html

--bcaec55241064d3c0304d5d2dc4e-- --===============9041283111771152429== 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 --===============9041283111771152429==-- From xen-users-bounces@lists.xen.org Sat Feb 16 08:00:26 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sat, 16 Feb 2013 08:00: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 1U6cfX-0004MH-GQ; Sat, 16 Feb 2013 07:58:47 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U6cfV-0004MC-CF for xen-users@lists.xen.org; Sat, 16 Feb 2013 07:58:45 +0000 Received: from [85.158.143.99:5744] by server-3.bemta-4.messagelabs.com id E0/62-08920-43C3F115; Sat, 16 Feb 2013 07:58:44 +0000 X-Env-Sender: falck.andreas.lists@gmail.com X-Msg-Ref: server-14.tower-216.messagelabs.com!1361001523!18156450!1 X-Originating-IP: [209.85.217.180] X-SpamReason: No, hits=2.2 required=7.0 tests=BODY_RANDOMQ,HTML_20_30, HTML_MESSAGE,ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 15337 invoked from network); 16 Feb 2013 07:58:43 -0000 Received: from mail-lb0-f180.google.com (HELO mail-lb0-f180.google.com) (209.85.217.180) by server-14.tower-216.messagelabs.com with RC4-SHA encrypted SMTP; 16 Feb 2013 07:58:43 -0000 Received: by mail-lb0-f180.google.com with SMTP id q12so3157076lbc.11 for ; Fri, 15 Feb 2013 23:58:42 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:content-type; bh=+30eLOGcsDsMu02QKZ2BzapgTq1CyWO5pLDU5zadPYo=; b=zcryfJM0JlSGHyt5mf7kq0jOUvmXbH9+0V/WU+52stpKT/Om7BTK37P5+1M1pmiK9Y 7YHX0dNr93wTcZa/+4AjDV5TwpwRDY/pN5wTrr46JwwB8DQ6Q0jEuOZlyu9zVKya1DSA 2ABB0/50dSlzmkQirL770I18nwNNuxrgmRlfzeQGEVdcZokvxv3Am7ZIBeqBVjBfQbrE AYldXw6vKLx0YUw82JRvAuJNM8U6nj1/PXVKPXlQuaR6fJE6RDhPFxcgw7Oe1KFdmnjA 9RN+vJxcC4xV5I0iwRCCj9ZcOwhU77eWxb0TeCemCtCV+j5O8a+TQjqDZkNwy0e+z463 xc1A== MIME-Version: 1.0 X-Received: by 10.152.46.17 with SMTP id r17mr4511597lam.47.1361001522740; Fri, 15 Feb 2013 23:58:42 -0800 (PST) Received: by 10.114.21.230 with HTTP; Fri, 15 Feb 2013 23:58:42 -0800 (PST) In-Reply-To: <1360836221.20449.312.camel@zakaz.uk.xensource.com> References: <1360836221.20449.312.camel@zakaz.uk.xensource.com> Date: Sat, 16 Feb 2013 08:58:42 +0100 Message-ID: From: Andreas Falck To: "xen-users@lists.xen.org" Subject: Re: [Xen-users] IVHD error, AMD-Vi gets disabled (4.1.3-3ubuntu1.3) X-BeenThere: xen-users@lists.xen.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="===============9041283111771152429==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============9041283111771152429== Content-Type: multipart/alternative; boundary=bcaec55241064d3c0304d5d2dc4e --bcaec55241064d3c0304d5d2dc4e Content-Type: text/plain; charset=ISO-8859-1 Ian and Hans are probably right. Adding the "iommu=amd-iommu-global-intremap" option to xen enables the IOMMU with warnings. A BIOS update did NOT work however, to the latest one available from Supermicro (R 3.0, Bios Date 09/10/2012). This would suggest that Supermicro mainboard models H8DG6 / H8DGi / H8DG6-F / H8DGi-F are broken in this respect, at least with current available BIOSes. I will stick with the insecure workaround, but I'll notify Supermicro about the problem. Thanks 2013/2/14 Ian Campbell >On Wed, 2013-02-13 at 14:17 +0000, Andreas Falck wrote: >> >> Could it be a xen bug (I know that my system is somewhat unusual), a >> old BIOS bug interacting with newer xen or an aqcuired hardware error? >> I'll of course provide more logs if needed. >Almost certainly the middle one IMHO, as bugs get fixed in Xen it >becomes less tolerant of dubious BIOS tables. 2013/2/16 Hans Mueller >On Wednesday, 13. February 2013 15:17:54 Andreas Falck wrote: >> [...] >> (XEN) IVHD Error: Conflicting IO-APIC 0x0 entries >> (XEN) AMD-Vi: Error initialization >> (XEN) I/O virtualisation disabled >looks like related to the XSA-36 >http://lists.xen.org/archives/html/xen-announce/2013-02/msg00002.html --bcaec55241064d3c0304d5d2dc4e Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Ian and Hans are probably right. Adding the "iommu=3Damd-iommu-global-= intremap" option to xen enables the IOMMU with warnings.

A BIOS= update did NOT work however, to the latest one available from Supermicro (= R 3.0, Bios Date 09/10/2012). This would suggest that Supermicro mainboard = models H8DG6 / H8DGi / H8DG6-F / H8DGi-F are broken in this respect, at lea= st with current available BIOSes.

I will stick with the insecure workaround, but I'll notify Supermic= ro about the problem.

Thanks

2013/= 2/14 Ian Campbell
>On Wed, 2013-02-13 at 14:17 +0000, Andreas Falck = wrote:
>>
>> Could it be a xen bug (I know that my system is somewh= at unusual), a
>> old BIOS bug interacting with newer xen or an aq= cuired hardware error?
>> I'll of course provide more logs if = needed.
=A0
>Almost certainly the middle one IMHO, as bugs get fixed in = Xen it
>becomes less tolerant of dubious BIOS tables.

= 2013/2/16 Hans Mueller
>On Wednesday, 13. February 2013 15:17:54 Andr= eas Falck wrote:
>> [...]
>> (XEN) IVHD Error: Conflicting IO-APIC 0x0 entries
>> (XEN) AMD-Vi: Error initialization
>> (XEN) I/O virtualisation disabled

>looks like related to the XSA-36
>http://lists.xen.org/archives/html/xen-announc= e/2013-02/msg00002.html

--bcaec55241064d3c0304d5d2dc4e-- --===============9041283111771152429== 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 --===============9041283111771152429==-- From xen-users-bounces@lists.xen.org Sat Feb 16 11:04:19 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sat, 16 Feb 2013 11:04: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 1U6fXf-0007Vk-PI; Sat, 16 Feb 2013 11:02:51 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U6fXe-0007Vf-Gc for Xen-users@lists.xen.org; Sat, 16 Feb 2013 11:02:50 +0000 Received: from [193.109.254.147:7104] by server-13.bemta-14.messagelabs.com id EE/EE-30639-9576F115; Sat, 16 Feb 2013 11:02:49 +0000 X-Env-Sender: tolga@ozses.net X-Msg-Ref: server-6.tower-27.messagelabs.com!1361012566!2969406!1 X-Originating-IP: [209.85.210.48] 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.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 30140 invoked from network); 16 Feb 2013 11:02:48 -0000 Received: from mail-da0-f48.google.com (HELO mail-da0-f48.google.com) (209.85.210.48) by server-6.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 16 Feb 2013 11:02:48 -0000 Received: by mail-da0-f48.google.com with SMTP id v40so1810828dad.7 for ; Sat, 16 Feb 2013 03:02:45 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-received:x-originating-ip:date:message-id:subject :from:to:content-type:x-gm-message-state; bh=rt7IkgLPdBR7CgesDWD6WH5AhYISRY0Dyw+kBckSrW0=; b=DGI8k0tZcphI4kjK5tlSc8mkCWHHam4vvr7/SU3H7NB9od5W9yHTJ/C1f7YMbJGPmQ gcA3z0xM+eUMgpykTjPBIU2ZZVn64WMk0dkYaoA5sIJaMB1t4yz+WiEH0RomUyRRnSq3 LqQQXzvB67VYXISBzTbmuxp3+9CUBXol6CBpf9CQOEoe1w4jN7SDA+DYV4KiAWsRg1jn S+6wuY9towzFEOqivfVxtCgmWBiCxpCXkvCYLHMO033s3b6qdY2m2Y4wLQ2IL0lSg7lK Qp5nt85/XG5mcx8efvJ412/4agSJKISLfuANsv8PRR5YcP4FITD9xHsl2bDwpdKoBgzw TW2g== MIME-Version: 1.0 X-Received: by 10.68.130.166 with SMTP id of6mr13473632pbb.72.1361012565679; Sat, 16 Feb 2013 03:02:45 -0800 (PST) Received: by 10.66.80.8 with HTTP; Sat, 16 Feb 2013 03:02:45 -0800 (PST) X-Originating-IP: [46.196.57.29] Date: Sat, 16 Feb 2013 13:02:45 +0200 Message-ID: From: Kartagis To: Xen-users@lists.xen.org X-Gm-Message-State: ALoCoQk5fAKw9cektdQIcWlaBr9owA69AYE16haNcALXNkS/VQkqXLROLreKBF1UHQg6Hy6qEng8 Subject: [Xen-users] Debootstrap X-BeenThere: xen-users@lists.xen.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="===============2677687448135021499==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============2677687448135021499== Content-Type: multipart/alternative; boundary=047d7b10cb61831c9504d5d56ee9 --047d7b10cb61831c9504d5d56ee9 Content-Type: text/plain; charset=ISO-8859-1 Hi, I don't know if this is the right mailing list, so please feel free to redirect me as appropriate. Having said that, how do I tell debootstrap which packages to install in the newly created VM? Regards, --047d7b10cb61831c9504d5d56ee9 Content-Type: text/html; charset=ISO-8859-1 Hi,

I don't know if this is the right mailing list, so please feel free to redirect me as appropriate.

Having said that, how do I tell debootstrap which packages to install in the newly created VM?

Regards,
--047d7b10cb61831c9504d5d56ee9-- --===============2677687448135021499== 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 --===============2677687448135021499==-- From xen-users-bounces@lists.xen.org Sat Feb 16 11:04:19 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sat, 16 Feb 2013 11:04: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 1U6fXf-0007Vk-PI; Sat, 16 Feb 2013 11:02:51 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U6fXe-0007Vf-Gc for Xen-users@lists.xen.org; Sat, 16 Feb 2013 11:02:50 +0000 Received: from [193.109.254.147:7104] by server-13.bemta-14.messagelabs.com id EE/EE-30639-9576F115; Sat, 16 Feb 2013 11:02:49 +0000 X-Env-Sender: tolga@ozses.net X-Msg-Ref: server-6.tower-27.messagelabs.com!1361012566!2969406!1 X-Originating-IP: [209.85.210.48] 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.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 30140 invoked from network); 16 Feb 2013 11:02:48 -0000 Received: from mail-da0-f48.google.com (HELO mail-da0-f48.google.com) (209.85.210.48) by server-6.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 16 Feb 2013 11:02:48 -0000 Received: by mail-da0-f48.google.com with SMTP id v40so1810828dad.7 for ; Sat, 16 Feb 2013 03:02:45 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-received:x-originating-ip:date:message-id:subject :from:to:content-type:x-gm-message-state; bh=rt7IkgLPdBR7CgesDWD6WH5AhYISRY0Dyw+kBckSrW0=; b=DGI8k0tZcphI4kjK5tlSc8mkCWHHam4vvr7/SU3H7NB9od5W9yHTJ/C1f7YMbJGPmQ gcA3z0xM+eUMgpykTjPBIU2ZZVn64WMk0dkYaoA5sIJaMB1t4yz+WiEH0RomUyRRnSq3 LqQQXzvB67VYXISBzTbmuxp3+9CUBXol6CBpf9CQOEoe1w4jN7SDA+DYV4KiAWsRg1jn S+6wuY9towzFEOqivfVxtCgmWBiCxpCXkvCYLHMO033s3b6qdY2m2Y4wLQ2IL0lSg7lK Qp5nt85/XG5mcx8efvJ412/4agSJKISLfuANsv8PRR5YcP4FITD9xHsl2bDwpdKoBgzw TW2g== MIME-Version: 1.0 X-Received: by 10.68.130.166 with SMTP id of6mr13473632pbb.72.1361012565679; Sat, 16 Feb 2013 03:02:45 -0800 (PST) Received: by 10.66.80.8 with HTTP; Sat, 16 Feb 2013 03:02:45 -0800 (PST) X-Originating-IP: [46.196.57.29] Date: Sat, 16 Feb 2013 13:02:45 +0200 Message-ID: From: Kartagis To: Xen-users@lists.xen.org X-Gm-Message-State: ALoCoQk5fAKw9cektdQIcWlaBr9owA69AYE16haNcALXNkS/VQkqXLROLreKBF1UHQg6Hy6qEng8 Subject: [Xen-users] Debootstrap X-BeenThere: xen-users@lists.xen.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="===============2677687448135021499==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============2677687448135021499== Content-Type: multipart/alternative; boundary=047d7b10cb61831c9504d5d56ee9 --047d7b10cb61831c9504d5d56ee9 Content-Type: text/plain; charset=ISO-8859-1 Hi, I don't know if this is the right mailing list, so please feel free to redirect me as appropriate. Having said that, how do I tell debootstrap which packages to install in the newly created VM? Regards, --047d7b10cb61831c9504d5d56ee9 Content-Type: text/html; charset=ISO-8859-1 Hi,

I don't know if this is the right mailing list, so please feel free to redirect me as appropriate.

Having said that, how do I tell debootstrap which packages to install in the newly created VM?

Regards,
--047d7b10cb61831c9504d5d56ee9-- --===============2677687448135021499== 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 --===============2677687448135021499==-- From xen-users-bounces@lists.xen.org Sat Feb 16 11:31:34 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sat, 16 Feb 2013 11:31: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 1U6fyF-00083J-Ei; Sat, 16 Feb 2013 11:30:19 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U6fyD-00083E-SU for xen-users@lists.xen.org; Sat, 16 Feb 2013 11:30:18 +0000 Received: from [193.109.254.147:19029] by server-15.bemta-14.messagelabs.com id 5B/99-24599-9CD6F115; Sat, 16 Feb 2013 11:30:17 +0000 X-Env-Sender: sylvain.chevalier@gmail.com X-Msg-Ref: server-14.tower-27.messagelabs.com!1361014214!1771367!1 X-Originating-IP: [209.85.215.46] 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.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 20931 invoked from network); 16 Feb 2013 11:30:15 -0000 Received: from mail-la0-f46.google.com (HELO mail-la0-f46.google.com) (209.85.215.46) by server-14.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 16 Feb 2013 11:30:15 -0000 Received: by mail-la0-f46.google.com with SMTP id fq12so4223860lab.19 for ; Sat, 16 Feb 2013 03:30:14 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:date:message-id:subject:from:to :content-type; bh=nt/4buGfszz854UJ+rdWGGfUEM15Q+3ebxP9rb3GqO4=; b=NSOmpH8xlBPH4Sr0IyxrybO3mScx78f20gRnhUnSVmJIbzYL/Wndpq5HsGmFc2kQti FUnRj4ujUT1nPMARzccrrCQ9swm2GFYNXW/cpIriDy92wA1n3xnLOKcD9eV3iwq9mCpn r3ZDdsLm2BTNSQFP+/OvkUuYbPh9YSIccVEFJjeZfUPoEpLkElxGEinm/aUi5Jo3mLKv ESPnNnmBSNCnK+8fCAOVgz/Q6MbuhqDPXFIKYCm8uZAXQa27Uyib6CT1btVNZPjo8dV9 IvPxL6EZTd5LPLs7pSfBfXMm2MlCL1zKeps1h01eBbyxoqLu60ZyLJ5gj7gJXvywhm8j NCHg== MIME-Version: 1.0 X-Received: by 10.112.98.166 with SMTP id ej6mr3274280lbb.62.1361014213484; Sat, 16 Feb 2013 03:30:13 -0800 (PST) Received: by 10.112.59.1 with HTTP; Sat, 16 Feb 2013 03:30:13 -0800 (PST) Date: Sat, 16 Feb 2013 19:30:13 +0800 Message-ID: From: Sylvain Chevalier To: xen-users@lists.xen.org Subject: [Xen-users] Can't boot dom0 after upgrading to non-modified 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-Type: multipart/mixed; boundary="===============6380541620662405216==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============6380541620662405216== Content-Type: multipart/alternative; boundary=f46d0401f96fbaa2cf04d5d5d022 --f46d0401f96fbaa2cf04d5d5d022 Content-Type: text/plain; charset=ISO-8859-1 Hi, I am migrating my gentoo server from the modified kernel 2.6.38 modified to the plain 3.6.11 kernel from the distribution. domUs all work fine with the new kernel, after a few changes in the configs (such as changing /dev/sd... to /dev/xvd...) but dom0 won't boot when using the new kernel. It fails saying something like "please append a correct root=" (It reboots right away, I barely have time to read). In other words, this grub entry works fine (kernel is xen-sources): root (hd0,1) kernel /boot/xen.gz dom0_mem=4096M dom0_max_vcpus=1 dom0_vcpus_pin module /boot/kernel-2.6.38-xen-dom0 root=/dev/sda6 This grub setting fails (kernel is gentoo-sources): root (hd0,1) kernel /boot/xen.gz dom0_mem=4096M dom0_max_vcpus=1 dom0_vcpus_pin module /boot/kernel-3.6.11-gentoo root=/dev/sda6 I have compiled the kernel with all options mentioned in the gentoo xen doc, do you know of anything I might be missing? Thanks a lot in advance, Sylvain --f46d0401f96fbaa2cf04d5d5d022 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Hi,

I am migrat= ing my gentoo server from the modified kernel 2.6.38 modified to the plain = 3.6.11 kernel from the distribution.

domUs all work fine with = the new kernel, after a few changes in the configs (such as changing /dev/s= d... to /dev/xvd...) but dom0 won't boot when using the new kernel. It = fails saying something like "please append a correct root=3D" (It= reboots right away, I barely have time to read).

In other words, this grub entry works fine (kernel is xen-sources= ):
root (hd0,1)
kernel /boot/xen.gz dom0_mem=3D4096M dom0_max_vcpus= =3D1 dom0_vcpus_pin
module /boot/kernel-2.6.38-xen-dom0 root=3D/dev/sda6=


This grub setting fails (kernel is gentoo-sources):
root (hd0,1)=
kernel /boot/xen.gz dom0_mem=3D4096M dom0_max_vcpus=3D1 dom0_vcpus_pin<= br>module /boot/kernel-3.6.11-gentoo root=3D/dev/sda6

I have c= ompiled the kernel with all options mentioned in the gentoo xen doc, do you= know of anything I might be missing?

Thanks a lot in advance,

Sylvain
--f46d0401f96fbaa2cf04d5d5d022-- --===============6380541620662405216== 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 --===============6380541620662405216==-- From xen-users-bounces@lists.xen.org Sat Feb 16 11:31:34 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sat, 16 Feb 2013 11:31: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 1U6fyF-00083J-Ei; Sat, 16 Feb 2013 11:30:19 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U6fyD-00083E-SU for xen-users@lists.xen.org; Sat, 16 Feb 2013 11:30:18 +0000 Received: from [193.109.254.147:19029] by server-15.bemta-14.messagelabs.com id 5B/99-24599-9CD6F115; Sat, 16 Feb 2013 11:30:17 +0000 X-Env-Sender: sylvain.chevalier@gmail.com X-Msg-Ref: server-14.tower-27.messagelabs.com!1361014214!1771367!1 X-Originating-IP: [209.85.215.46] 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.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 20931 invoked from network); 16 Feb 2013 11:30:15 -0000 Received: from mail-la0-f46.google.com (HELO mail-la0-f46.google.com) (209.85.215.46) by server-14.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 16 Feb 2013 11:30:15 -0000 Received: by mail-la0-f46.google.com with SMTP id fq12so4223860lab.19 for ; Sat, 16 Feb 2013 03:30:14 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:date:message-id:subject:from:to :content-type; bh=nt/4buGfszz854UJ+rdWGGfUEM15Q+3ebxP9rb3GqO4=; b=NSOmpH8xlBPH4Sr0IyxrybO3mScx78f20gRnhUnSVmJIbzYL/Wndpq5HsGmFc2kQti FUnRj4ujUT1nPMARzccrrCQ9swm2GFYNXW/cpIriDy92wA1n3xnLOKcD9eV3iwq9mCpn r3ZDdsLm2BTNSQFP+/OvkUuYbPh9YSIccVEFJjeZfUPoEpLkElxGEinm/aUi5Jo3mLKv ESPnNnmBSNCnK+8fCAOVgz/Q6MbuhqDPXFIKYCm8uZAXQa27Uyib6CT1btVNZPjo8dV9 IvPxL6EZTd5LPLs7pSfBfXMm2MlCL1zKeps1h01eBbyxoqLu60ZyLJ5gj7gJXvywhm8j NCHg== MIME-Version: 1.0 X-Received: by 10.112.98.166 with SMTP id ej6mr3274280lbb.62.1361014213484; Sat, 16 Feb 2013 03:30:13 -0800 (PST) Received: by 10.112.59.1 with HTTP; Sat, 16 Feb 2013 03:30:13 -0800 (PST) Date: Sat, 16 Feb 2013 19:30:13 +0800 Message-ID: From: Sylvain Chevalier To: xen-users@lists.xen.org Subject: [Xen-users] Can't boot dom0 after upgrading to non-modified 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-Type: multipart/mixed; boundary="===============6380541620662405216==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============6380541620662405216== Content-Type: multipart/alternative; boundary=f46d0401f96fbaa2cf04d5d5d022 --f46d0401f96fbaa2cf04d5d5d022 Content-Type: text/plain; charset=ISO-8859-1 Hi, I am migrating my gentoo server from the modified kernel 2.6.38 modified to the plain 3.6.11 kernel from the distribution. domUs all work fine with the new kernel, after a few changes in the configs (such as changing /dev/sd... to /dev/xvd...) but dom0 won't boot when using the new kernel. It fails saying something like "please append a correct root=" (It reboots right away, I barely have time to read). In other words, this grub entry works fine (kernel is xen-sources): root (hd0,1) kernel /boot/xen.gz dom0_mem=4096M dom0_max_vcpus=1 dom0_vcpus_pin module /boot/kernel-2.6.38-xen-dom0 root=/dev/sda6 This grub setting fails (kernel is gentoo-sources): root (hd0,1) kernel /boot/xen.gz dom0_mem=4096M dom0_max_vcpus=1 dom0_vcpus_pin module /boot/kernel-3.6.11-gentoo root=/dev/sda6 I have compiled the kernel with all options mentioned in the gentoo xen doc, do you know of anything I might be missing? Thanks a lot in advance, Sylvain --f46d0401f96fbaa2cf04d5d5d022 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Hi,

I am migrat= ing my gentoo server from the modified kernel 2.6.38 modified to the plain = 3.6.11 kernel from the distribution.

domUs all work fine with = the new kernel, after a few changes in the configs (such as changing /dev/s= d... to /dev/xvd...) but dom0 won't boot when using the new kernel. It = fails saying something like "please append a correct root=3D" (It= reboots right away, I barely have time to read).

In other words, this grub entry works fine (kernel is xen-sources= ):
root (hd0,1)
kernel /boot/xen.gz dom0_mem=3D4096M dom0_max_vcpus= =3D1 dom0_vcpus_pin
module /boot/kernel-2.6.38-xen-dom0 root=3D/dev/sda6=


This grub setting fails (kernel is gentoo-sources):
root (hd0,1)=
kernel /boot/xen.gz dom0_mem=3D4096M dom0_max_vcpus=3D1 dom0_vcpus_pin<= br>module /boot/kernel-3.6.11-gentoo root=3D/dev/sda6

I have c= ompiled the kernel with all options mentioned in the gentoo xen doc, do you= know of anything I might be missing?

Thanks a lot in advance,

Sylvain
--f46d0401f96fbaa2cf04d5d5d022-- --===============6380541620662405216== 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 --===============6380541620662405216==-- From xen-users-bounces@lists.xen.org Sat Feb 16 11:34:38 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sat, 16 Feb 2013 11:34: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 1U6g1J-0008Il-9v; Sat, 16 Feb 2013 11:33:29 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U6g1H-0008Ic-LU for xen-users@lists.xen.org; Sat, 16 Feb 2013 11:33:27 +0000 Received: from [85.158.137.99:56194] by server-4.bemta-3.messagelabs.com id 47/0D-17521-58E6F115; Sat, 16 Feb 2013 11:33:25 +0000 X-Env-Sender: mlg-hessigheim@gmx.de X-Msg-Ref: server-16.tower-217.messagelabs.com!1361014404!21684724!1 X-Originating-IP: [212.227.17.20] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogMjEyLjIyNy4xNy4yMCA9PiAzNTYzMg==\n, ML_RADAR_SPEW_LINKS_14,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 19296 invoked from network); 16 Feb 2013 11:33:24 -0000 Received: from mout.gmx.net (HELO mout.gmx.net) (212.227.17.20) by server-16.tower-217.messagelabs.com with SMTP; 16 Feb 2013 11:33:24 -0000 Received: from mailout-de.gmx.net ([10.1.76.10]) by mrigmx.server.lan (mrigmx001) with ESMTP (Nemesis) id 0MbvXU-1UMYD74BXy-00JHGq for ; Sat, 16 Feb 2013 12:33:24 +0100 Received: (qmail invoked by alias); 16 Feb 2013 11:33:23 -0000 Received: from HSI-KBW-085-216-074-171.hsi.kabelbw.de (EHLO [192.168.2.163]) [85.216.74.171] by mail.gmx.net (mp010) with SMTP; 16 Feb 2013 12:33:23 +0100 X-Authenticated: #12881343 X-Provags-ID: V01U2FsdGVkX19chQwmfn5cjUzRP+S6DqrjA7KSJIFTkeOpNsOpD9 M9Y2ErxDlYrONP Message-ID: <511F6E82.8040107@gmx.de> Date: Sat, 16 Feb 2013 12:33:22 +0100 From: Martin Lang User-Agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/20130106 Thunderbird/17.0.2 MIME-Version: 1.0 To: xen-users@lists.xen.org X-Y-GMX-Trusted: 0 Subject: [Xen-users] Boot problem with Debian Squeeza and Xen X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: mlg-hessigheim@gmx.de 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 just upgraded my Debian/Etch with Xen3.3 machine to Debian/Squeeze Xen4.0 and now have problems with starting the Dom0 kernel. I always get the error message: Kernel panic not syncing: the kernel parameter noapic is incompatible with xen. My grub.cfg is: menuentry 'Debian GNU/Linux, with Linux 2.6.32-5-xen-686 and XEN 4.0-i386' --cl$ insmod part_msdos insmod ext2 set root='(hd0,msdos1)' search --no-floppy --fs-uuid --set 743d959f-5054-441f-b68d-32d9970bb8ab echo 'Loading Linux 2.6.32-5-xen-686 ...' multiboot /boot/xen-4.0-i386.gz noreboot placeholder module /boot/vmlinuz-2.6.32-5-xen-686 placeholder root=UUID=743d959f-5$ echo 'Loading initial ramdisk ...' module /boot/initrd.img-2.6.32-5-xen-686 I already tried the boot parameters: noapic nolapic acpi=off in the line mulitboot .... and module /boot/vmlinuz line. What can I do to get the machine running? _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Sat Feb 16 11:34:38 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sat, 16 Feb 2013 11:34: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 1U6g1J-0008Il-9v; Sat, 16 Feb 2013 11:33:29 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U6g1H-0008Ic-LU for xen-users@lists.xen.org; Sat, 16 Feb 2013 11:33:27 +0000 Received: from [85.158.137.99:56194] by server-4.bemta-3.messagelabs.com id 47/0D-17521-58E6F115; Sat, 16 Feb 2013 11:33:25 +0000 X-Env-Sender: mlg-hessigheim@gmx.de X-Msg-Ref: server-16.tower-217.messagelabs.com!1361014404!21684724!1 X-Originating-IP: [212.227.17.20] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogMjEyLjIyNy4xNy4yMCA9PiAzNTYzMg==\n, ML_RADAR_SPEW_LINKS_14,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 19296 invoked from network); 16 Feb 2013 11:33:24 -0000 Received: from mout.gmx.net (HELO mout.gmx.net) (212.227.17.20) by server-16.tower-217.messagelabs.com with SMTP; 16 Feb 2013 11:33:24 -0000 Received: from mailout-de.gmx.net ([10.1.76.10]) by mrigmx.server.lan (mrigmx001) with ESMTP (Nemesis) id 0MbvXU-1UMYD74BXy-00JHGq for ; Sat, 16 Feb 2013 12:33:24 +0100 Received: (qmail invoked by alias); 16 Feb 2013 11:33:23 -0000 Received: from HSI-KBW-085-216-074-171.hsi.kabelbw.de (EHLO [192.168.2.163]) [85.216.74.171] by mail.gmx.net (mp010) with SMTP; 16 Feb 2013 12:33:23 +0100 X-Authenticated: #12881343 X-Provags-ID: V01U2FsdGVkX19chQwmfn5cjUzRP+S6DqrjA7KSJIFTkeOpNsOpD9 M9Y2ErxDlYrONP Message-ID: <511F6E82.8040107@gmx.de> Date: Sat, 16 Feb 2013 12:33:22 +0100 From: Martin Lang User-Agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/20130106 Thunderbird/17.0.2 MIME-Version: 1.0 To: xen-users@lists.xen.org X-Y-GMX-Trusted: 0 Subject: [Xen-users] Boot problem with Debian Squeeza and Xen X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: mlg-hessigheim@gmx.de 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 just upgraded my Debian/Etch with Xen3.3 machine to Debian/Squeeze Xen4.0 and now have problems with starting the Dom0 kernel. I always get the error message: Kernel panic not syncing: the kernel parameter noapic is incompatible with xen. My grub.cfg is: menuentry 'Debian GNU/Linux, with Linux 2.6.32-5-xen-686 and XEN 4.0-i386' --cl$ insmod part_msdos insmod ext2 set root='(hd0,msdos1)' search --no-floppy --fs-uuid --set 743d959f-5054-441f-b68d-32d9970bb8ab echo 'Loading Linux 2.6.32-5-xen-686 ...' multiboot /boot/xen-4.0-i386.gz noreboot placeholder module /boot/vmlinuz-2.6.32-5-xen-686 placeholder root=UUID=743d959f-5$ echo 'Loading initial ramdisk ...' module /boot/initrd.img-2.6.32-5-xen-686 I already tried the boot parameters: noapic nolapic acpi=off in the line mulitboot .... and module /boot/vmlinuz line. What can I do to get the machine running? _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Sat Feb 16 16:52:29 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sat, 16 Feb 2013 16:52: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 1U6kyd-0005D0-9b; Sat, 16 Feb 2013 16: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 1U6kyc-0005C1-8z for xen-users@lists.xen.org; Sat, 16 Feb 2013 16:51:02 +0000 Received: from [85.158.138.51:9035] by server-15.bemta-3.messagelabs.com id 88/B1-25405-5F8BF115; Sat, 16 Feb 2013 16:51:01 +0000 X-Env-Sender: ghudiczius@gmail.com X-Msg-Ref: server-13.tower-174.messagelabs.com!1361033460!9149425!1 X-Originating-IP: [209.85.215.170] X-SpamReason: No, hits=0.0 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, spamassassin: X-StarScan-Received: X-StarScan-Version: 6.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 19915 invoked from network); 16 Feb 2013 16:51:01 -0000 Received: from mail-ea0-f170.google.com (HELO mail-ea0-f170.google.com) (209.85.215.170) by server-13.tower-174.messagelabs.com with RC4-SHA encrypted SMTP; 16 Feb 2013 16:51:01 -0000 Received: by mail-ea0-f170.google.com with SMTP id a11so1769173eaa.15 for ; Sat, 16 Feb 2013 08:51:00 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:reply-to:user-agent:mime-version:to :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=KoMH1denBt0OF/8Ho9vD4ouESpiQzxy3Bwf/wQHvGHI=; b=A2YWwLwp2Oyod2tGioQ6vmKcLiY7bSNWXOZYh9PsqpcgKay1klqYJwq1aHFq+HIcRG wpuJ8z4Zm5jk94URluBpqzt1DOU/8e1nUDQV/j3tWNjMBuDbz6Kz9xaslY+QUZDLkzXN tkT28MKM5V+ivWf/3MKIo+KfhVIsqb1vvIbA/VkFXENB3SUkb+vKRORnl/MoI8WqDz0k p5UFL6mQnxmOcigOf6kC6GSOAemQvWtdCIlYZrCAh8SuspEaZ4VdntreZRXqBk+uUY4d p8cyZ151lnnJ/zjzGTi2RYLrGluiILjfKkWcEE/NGv5IekPbkmCGiVAr1y7+tldob4ID 6Icg== X-Received: by 10.14.0.73 with SMTP id 49mr22500635eea.21.1361033460741; Sat, 16 Feb 2013 08:51:00 -0800 (PST) Received: from ?IPv6:2a01:368:e10d::10? ([2a01:368:e10d::10]) by mx.google.com with ESMTPS id t4sm89289620eel.0.2013.02.16.08.50.58 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sat, 16 Feb 2013 08:50:59 -0800 (PST) Message-ID: <511FB8EE.9010901@gmail.com> Date: Sat, 16 Feb 2013 17:50:54 +0100 From: Gabor Hudiczius User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:17.0) Gecko/20130107 Thunderbird/17.0.2 MIME-Version: 1.0 To: xen-users@lists.xen.org References: In-Reply-To: Subject: Re: [Xen-users] Debootstrap X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: ghudiczius@gmail.com 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, man debootstrap states that there's a "--include=alpha,beta" option for debootstrap, which takes a "comma separated list of packages which will be added to download and extract lists". Regards, Gabor Hudiczius On 13.02.16. 12:02, Kartagis wrote: > Hi, > > I don't know if this is the right mailing list, so please feel free to > redirect me as appropriate. > > Having said that, how do I tell debootstrap which packages to install in > the newly created VM? > > Regards, > > > _______________________________________________ > 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 Feb 16 16:52:29 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sat, 16 Feb 2013 16:52: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 1U6kyd-0005D0-9b; Sat, 16 Feb 2013 16: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 1U6kyc-0005C1-8z for xen-users@lists.xen.org; Sat, 16 Feb 2013 16:51:02 +0000 Received: from [85.158.138.51:9035] by server-15.bemta-3.messagelabs.com id 88/B1-25405-5F8BF115; Sat, 16 Feb 2013 16:51:01 +0000 X-Env-Sender: ghudiczius@gmail.com X-Msg-Ref: server-13.tower-174.messagelabs.com!1361033460!9149425!1 X-Originating-IP: [209.85.215.170] X-SpamReason: No, hits=0.0 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, spamassassin: X-StarScan-Received: X-StarScan-Version: 6.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 19915 invoked from network); 16 Feb 2013 16:51:01 -0000 Received: from mail-ea0-f170.google.com (HELO mail-ea0-f170.google.com) (209.85.215.170) by server-13.tower-174.messagelabs.com with RC4-SHA encrypted SMTP; 16 Feb 2013 16:51:01 -0000 Received: by mail-ea0-f170.google.com with SMTP id a11so1769173eaa.15 for ; Sat, 16 Feb 2013 08:51:00 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:reply-to:user-agent:mime-version:to :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=KoMH1denBt0OF/8Ho9vD4ouESpiQzxy3Bwf/wQHvGHI=; b=A2YWwLwp2Oyod2tGioQ6vmKcLiY7bSNWXOZYh9PsqpcgKay1klqYJwq1aHFq+HIcRG wpuJ8z4Zm5jk94URluBpqzt1DOU/8e1nUDQV/j3tWNjMBuDbz6Kz9xaslY+QUZDLkzXN tkT28MKM5V+ivWf/3MKIo+KfhVIsqb1vvIbA/VkFXENB3SUkb+vKRORnl/MoI8WqDz0k p5UFL6mQnxmOcigOf6kC6GSOAemQvWtdCIlYZrCAh8SuspEaZ4VdntreZRXqBk+uUY4d p8cyZ151lnnJ/zjzGTi2RYLrGluiILjfKkWcEE/NGv5IekPbkmCGiVAr1y7+tldob4ID 6Icg== X-Received: by 10.14.0.73 with SMTP id 49mr22500635eea.21.1361033460741; Sat, 16 Feb 2013 08:51:00 -0800 (PST) Received: from ?IPv6:2a01:368:e10d::10? ([2a01:368:e10d::10]) by mx.google.com with ESMTPS id t4sm89289620eel.0.2013.02.16.08.50.58 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sat, 16 Feb 2013 08:50:59 -0800 (PST) Message-ID: <511FB8EE.9010901@gmail.com> Date: Sat, 16 Feb 2013 17:50:54 +0100 From: Gabor Hudiczius User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:17.0) Gecko/20130107 Thunderbird/17.0.2 MIME-Version: 1.0 To: xen-users@lists.xen.org References: In-Reply-To: Subject: Re: [Xen-users] Debootstrap X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: ghudiczius@gmail.com 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, man debootstrap states that there's a "--include=alpha,beta" option for debootstrap, which takes a "comma separated list of packages which will be added to download and extract lists". Regards, Gabor Hudiczius On 13.02.16. 12:02, Kartagis wrote: > Hi, > > I don't know if this is the right mailing list, so please feel free to > redirect me as appropriate. > > Having said that, how do I tell debootstrap which packages to install in > the newly created VM? > > Regards, > > > _______________________________________________ > 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 Feb 16 17:35:26 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sat, 16 Feb 2013 17:35: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 1U6leL-00065S-Bf; Sat, 16 Feb 2013 17:34:09 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U6leI-00065K-HM for xen-users@lists.xen.org; Sat, 16 Feb 2013 17:34:06 +0000 Received: from [85.158.139.83:53886] by server-2.bemta-5.messagelabs.com id 59/F7-16911-D03CF115; Sat, 16 Feb 2013 17:34:05 +0000 X-Env-Sender: tolga@ozses.net X-Msg-Ref: server-11.tower-182.messagelabs.com!1361036042!20355285!1 X-Originating-IP: [209.85.160.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.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 4408 invoked from network); 16 Feb 2013 17:34:04 -0000 Received: from mail-pb0-f45.google.com (HELO mail-pb0-f45.google.com) (209.85.160.45) by server-11.tower-182.messagelabs.com with RC4-SHA encrypted SMTP; 16 Feb 2013 17:34:04 -0000 Received: by mail-pb0-f45.google.com with SMTP id ro8so1037038pbb.18 for ; Sat, 16 Feb 2013 09:34:02 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-received:x-originating-ip:in-reply-to:references :date:message-id:subject:from:to:cc:content-type:x-gm-message-state; bh=+BE97c/1SsGpA0vXaD96YnBK+btTMzQHWhQzrpLGxrs=; b=MOwlYxIMl0s9YPxlyGsvuKFze5NKbS0ffMRAmVMz+mZ8Jgv8FUDulgWxkJgBbev46/ VquJZWab9gCDftuLCM5kh8bkegl1jkERF7hHir1kPH0DCuRFuwzNQRTVTuNzfiGmbxQS X/sOSTThJutTU+vZrTvJO48asfYVejKmsNSxMrliacM5a6N9j9Eakw2PvsZJvjI+b6cs sg+ii8oTNinbPR8GhyhK+Pxyj2FwJriQi+KwHkxRZkt5/xBvosSrRIZ0gs75hFbwruH+ QsimYUFOoEK6JMKuc769+7auu8ar82xxrH4oXih+uH2hVqxosWiv1cvTIb1IEssa4Alg FSfA== MIME-Version: 1.0 X-Received: by 10.68.254.69 with SMTP id ag5mr16059249pbd.31.1361036042262; Sat, 16 Feb 2013 09:34:02 -0800 (PST) Received: by 10.66.80.8 with HTTP; Sat, 16 Feb 2013 09:34:02 -0800 (PST) X-Originating-IP: [46.196.57.29] In-Reply-To: <511FB8EE.9010901@gmail.com> References: <511FB8EE.9010901@gmail.com> Date: Sat, 16 Feb 2013 19:34:02 +0200 Message-ID: From: Kartagis To: ghudiczius@gmail.com X-Gm-Message-State: ALoCoQm3qDXf0kn2taeq17cT2tjmNKtb12JyygpS9UoExKk+kFVDgN2XxMV3JqIx0/s4CN5DtFAF Cc: xen-users@lists.xen.org Subject: Re: [Xen-users] Debootstrap X-BeenThere: xen-users@lists.xen.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="===============2411601967092225300==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============2411601967092225300== Content-Type: multipart/alternative; boundary=047d7b160291d35a6004d5dae517 --047d7b160291d35a6004d5dae517 Content-Type: text/plain; charset=ISO-8859-1 I've read that, but I was wondering if the same could be done with xen-create-image. On 16 February 2013 18:50, Gabor Hudiczius wrote: > Hi, > > man debootstrap states that there's a "--include=alpha,beta" option for > debootstrap, which takes a "comma separated list of packages which will be > added to download and extract lists". > > Regards, > Gabor Hudiczius > > > On 13.02.16. 12:02, Kartagis wrote: > >> Hi, >> >> I don't know if this is the right mailing list, so please feel free to >> redirect me as appropriate. >> >> Having said that, how do I tell debootstrap which packages to install in >> the newly created VM? >> >> Regards, >> >> >> ______________________________**_________________ >> 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 > --047d7b160291d35a6004d5dae517 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable I've read that, but I was wondering if the same could be done with xen-= create-image.

On 16 February 2013 18:50, = Gabor Hudiczius <ghudiczius@gmail.com> wrote:
Hi,

man debootstrap states that there's a "--include=3Dalpha,beta"= ; option for debootstrap, which takes a "comma separated list of packa= ges which will be added to download and extract lists".

Regards,
Gabor Hudiczius


On 13.02.16. 12:02, Kartagis wrote:
Hi,

I don't know if this is the right mailing list, so please feel free to<= br> redirect me as appropriate.

Having said that, how do I tell debootstrap which packages to install in the newly created VM?

Regards,


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



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

--047d7b160291d35a6004d5dae517-- --===============2411601967092225300== 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 --===============2411601967092225300==-- From xen-users-bounces@lists.xen.org Sat Feb 16 17:35:26 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sat, 16 Feb 2013 17:35: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 1U6leL-00065S-Bf; Sat, 16 Feb 2013 17:34:09 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U6leI-00065K-HM for xen-users@lists.xen.org; Sat, 16 Feb 2013 17:34:06 +0000 Received: from [85.158.139.83:53886] by server-2.bemta-5.messagelabs.com id 59/F7-16911-D03CF115; Sat, 16 Feb 2013 17:34:05 +0000 X-Env-Sender: tolga@ozses.net X-Msg-Ref: server-11.tower-182.messagelabs.com!1361036042!20355285!1 X-Originating-IP: [209.85.160.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.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 4408 invoked from network); 16 Feb 2013 17:34:04 -0000 Received: from mail-pb0-f45.google.com (HELO mail-pb0-f45.google.com) (209.85.160.45) by server-11.tower-182.messagelabs.com with RC4-SHA encrypted SMTP; 16 Feb 2013 17:34:04 -0000 Received: by mail-pb0-f45.google.com with SMTP id ro8so1037038pbb.18 for ; Sat, 16 Feb 2013 09:34:02 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-received:x-originating-ip:in-reply-to:references :date:message-id:subject:from:to:cc:content-type:x-gm-message-state; bh=+BE97c/1SsGpA0vXaD96YnBK+btTMzQHWhQzrpLGxrs=; b=MOwlYxIMl0s9YPxlyGsvuKFze5NKbS0ffMRAmVMz+mZ8Jgv8FUDulgWxkJgBbev46/ VquJZWab9gCDftuLCM5kh8bkegl1jkERF7hHir1kPH0DCuRFuwzNQRTVTuNzfiGmbxQS X/sOSTThJutTU+vZrTvJO48asfYVejKmsNSxMrliacM5a6N9j9Eakw2PvsZJvjI+b6cs sg+ii8oTNinbPR8GhyhK+Pxyj2FwJriQi+KwHkxRZkt5/xBvosSrRIZ0gs75hFbwruH+ QsimYUFOoEK6JMKuc769+7auu8ar82xxrH4oXih+uH2hVqxosWiv1cvTIb1IEssa4Alg FSfA== MIME-Version: 1.0 X-Received: by 10.68.254.69 with SMTP id ag5mr16059249pbd.31.1361036042262; Sat, 16 Feb 2013 09:34:02 -0800 (PST) Received: by 10.66.80.8 with HTTP; Sat, 16 Feb 2013 09:34:02 -0800 (PST) X-Originating-IP: [46.196.57.29] In-Reply-To: <511FB8EE.9010901@gmail.com> References: <511FB8EE.9010901@gmail.com> Date: Sat, 16 Feb 2013 19:34:02 +0200 Message-ID: From: Kartagis To: ghudiczius@gmail.com X-Gm-Message-State: ALoCoQm3qDXf0kn2taeq17cT2tjmNKtb12JyygpS9UoExKk+kFVDgN2XxMV3JqIx0/s4CN5DtFAF Cc: xen-users@lists.xen.org Subject: Re: [Xen-users] Debootstrap X-BeenThere: xen-users@lists.xen.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="===============2411601967092225300==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============2411601967092225300== Content-Type: multipart/alternative; boundary=047d7b160291d35a6004d5dae517 --047d7b160291d35a6004d5dae517 Content-Type: text/plain; charset=ISO-8859-1 I've read that, but I was wondering if the same could be done with xen-create-image. On 16 February 2013 18:50, Gabor Hudiczius wrote: > Hi, > > man debootstrap states that there's a "--include=alpha,beta" option for > debootstrap, which takes a "comma separated list of packages which will be > added to download and extract lists". > > Regards, > Gabor Hudiczius > > > On 13.02.16. 12:02, Kartagis wrote: > >> Hi, >> >> I don't know if this is the right mailing list, so please feel free to >> redirect me as appropriate. >> >> Having said that, how do I tell debootstrap which packages to install in >> the newly created VM? >> >> Regards, >> >> >> ______________________________**_________________ >> 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 > --047d7b160291d35a6004d5dae517 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable I've read that, but I was wondering if the same could be done with xen-= create-image.

On 16 February 2013 18:50, = Gabor Hudiczius <ghudiczius@gmail.com> wrote:
Hi,

man debootstrap states that there's a "--include=3Dalpha,beta"= ; option for debootstrap, which takes a "comma separated list of packa= ges which will be added to download and extract lists".

Regards,
Gabor Hudiczius


On 13.02.16. 12:02, Kartagis wrote:
Hi,

I don't know if this is the right mailing list, so please feel free to<= br> redirect me as appropriate.

Having said that, how do I tell debootstrap which packages to install in the newly created VM?

Regards,


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



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

--047d7b160291d35a6004d5dae517-- --===============2411601967092225300== 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 --===============2411601967092225300==-- From xen-users-bounces@lists.xen.org Sat Feb 16 17:39:29 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sat, 16 Feb 2013 17:39: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 1U6liQ-0006FE-Cw; Sat, 16 Feb 2013 17:38:22 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U6liP-0006F7-0K for xen-users@lists.xen.org; Sat, 16 Feb 2013 17:38:21 +0000 Received: from [85.158.139.211:58573] by server-5.bemta-5.messagelabs.com id 56/B7-11945-C04CF115; Sat, 16 Feb 2013 17:38:20 +0000 X-Env-Sender: matthias.kannenberg@googlemail.com X-Msg-Ref: server-11.tower-206.messagelabs.com!1361036299!22759010!1 X-Originating-IP: [74.125.82.175] X-SpamReason: No, hits=0.3 required=7.0 tests=RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 20962 invoked from network); 16 Feb 2013 17:38:19 -0000 Received: from mail-we0-f175.google.com (HELO mail-we0-f175.google.com) (74.125.82.175) by server-11.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 16 Feb 2013 17:38:19 -0000 Received: by mail-we0-f175.google.com with SMTP id x8so3771491wey.34 for ; Sat, 16 Feb 2013 09:38:19 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=20120113; h=x-received:mime-version:in-reply-to:references:from:date:message-id :subject:to:cc:content-type; bh=q5ZfwZjKYy8h1obJlkgz/nNkWno3si0nHbNNlcbuROU=; b=VnJYrtMzAE7R7oetpmHcUDL/C+gXq/nBwGPtgF0ZcpZ0Yrvjs1vI1/oHLmp1JHgxyh r6XbtYS6X3qHf3Rq8RgEkF7AvltfosFzJSIsU7FWo28YDDMPMi03VNXYQ77Z3uePsBpX VfQ0e/7Y7/ZYidtKNalrnnQ+p1BL60ZH62jHW4aer9LfiuiKoTPDYE3AHgPzvMztXR/3 3kHVmMZl8U5wY3n150ssZDBM00c21ZrUSFdnu8XPxu5iDNf7u/1fx6YyLx7qt+XJzUI2 bSt5P3oW+wZkQrcUEy+cZ6Ux5CBJjw3STXEwPK5qjvPt3//3Ekw+KNhaXBuOXsGwhHsX cxaw== X-Received: by 10.194.109.10 with SMTP id ho10mr10560348wjb.16.1361036299707; Sat, 16 Feb 2013 09:38:19 -0800 (PST) MIME-Version: 1.0 Received: by 10.194.80.68 with HTTP; Sat, 16 Feb 2013 09:37:58 -0800 (PST) In-Reply-To: <20130213220535.06c0de16@pigeond.net> References: <20130210235853.4ebb70b8@pigeond.net> <20130212084728.64c49ea1@pigeond.net> <6035A0D088A63A46850C3988ED045A4B35667928@BITCOM1.int.sbss.com.au> <20130212210541.3b71b98f@pigeond.net> <6035A0D088A63A46850C3988ED045A4B3566C353@BITCOM1.int.sbss.com.au> <20130213220535.06c0de16@pigeond.net> From: Matthias Date: Sat, 16 Feb 2013 18:37:58 +0100 Message-ID: To: Howell Tam Cc: "xen-users@lists.xen.org" , James Harper Subject: Re: [Xen-users] Dom0 freeze on HVM DomU Windows reboot with 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 Hi, have you found a solution for this behaviour? Cause I'm currently seeing a similar result with my installation. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Sat Feb 16 17:39:29 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sat, 16 Feb 2013 17:39: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 1U6liQ-0006FE-Cw; Sat, 16 Feb 2013 17:38:22 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U6liP-0006F7-0K for xen-users@lists.xen.org; Sat, 16 Feb 2013 17:38:21 +0000 Received: from [85.158.139.211:58573] by server-5.bemta-5.messagelabs.com id 56/B7-11945-C04CF115; Sat, 16 Feb 2013 17:38:20 +0000 X-Env-Sender: matthias.kannenberg@googlemail.com X-Msg-Ref: server-11.tower-206.messagelabs.com!1361036299!22759010!1 X-Originating-IP: [74.125.82.175] X-SpamReason: No, hits=0.3 required=7.0 tests=RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 20962 invoked from network); 16 Feb 2013 17:38:19 -0000 Received: from mail-we0-f175.google.com (HELO mail-we0-f175.google.com) (74.125.82.175) by server-11.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 16 Feb 2013 17:38:19 -0000 Received: by mail-we0-f175.google.com with SMTP id x8so3771491wey.34 for ; Sat, 16 Feb 2013 09:38:19 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=20120113; h=x-received:mime-version:in-reply-to:references:from:date:message-id :subject:to:cc:content-type; bh=q5ZfwZjKYy8h1obJlkgz/nNkWno3si0nHbNNlcbuROU=; b=VnJYrtMzAE7R7oetpmHcUDL/C+gXq/nBwGPtgF0ZcpZ0Yrvjs1vI1/oHLmp1JHgxyh r6XbtYS6X3qHf3Rq8RgEkF7AvltfosFzJSIsU7FWo28YDDMPMi03VNXYQ77Z3uePsBpX VfQ0e/7Y7/ZYidtKNalrnnQ+p1BL60ZH62jHW4aer9LfiuiKoTPDYE3AHgPzvMztXR/3 3kHVmMZl8U5wY3n150ssZDBM00c21ZrUSFdnu8XPxu5iDNf7u/1fx6YyLx7qt+XJzUI2 bSt5P3oW+wZkQrcUEy+cZ6Ux5CBJjw3STXEwPK5qjvPt3//3Ekw+KNhaXBuOXsGwhHsX cxaw== X-Received: by 10.194.109.10 with SMTP id ho10mr10560348wjb.16.1361036299707; Sat, 16 Feb 2013 09:38:19 -0800 (PST) MIME-Version: 1.0 Received: by 10.194.80.68 with HTTP; Sat, 16 Feb 2013 09:37:58 -0800 (PST) In-Reply-To: <20130213220535.06c0de16@pigeond.net> References: <20130210235853.4ebb70b8@pigeond.net> <20130212084728.64c49ea1@pigeond.net> <6035A0D088A63A46850C3988ED045A4B35667928@BITCOM1.int.sbss.com.au> <20130212210541.3b71b98f@pigeond.net> <6035A0D088A63A46850C3988ED045A4B3566C353@BITCOM1.int.sbss.com.au> <20130213220535.06c0de16@pigeond.net> From: Matthias Date: Sat, 16 Feb 2013 18:37:58 +0100 Message-ID: To: Howell Tam Cc: "xen-users@lists.xen.org" , James Harper Subject: Re: [Xen-users] Dom0 freeze on HVM DomU Windows reboot with 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 Hi, have you found a solution for this behaviour? Cause I'm currently seeing a similar result with my installation. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Sat Feb 16 17:57:22 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sat, 16 Feb 2013 17:57: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 1U6lzl-0006wT-PK; Sat, 16 Feb 2013 17:56:17 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U6lzj-0006wE-0t; Sat, 16 Feb 2013 17:56:15 +0000 Received: from [85.158.137.99:18629] by server-5.bemta-3.messagelabs.com id 1F/AF-04457-938CF115; Sat, 16 Feb 2013 17:56:09 +0000 X-Env-Sender: agya.naila@gmail.com X-Msg-Ref: server-10.tower-217.messagelabs.com!1361037368!20890405!1 X-Originating-IP: [74.125.82.180] 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.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 9784 invoked from network); 16 Feb 2013 17:56:08 -0000 Received: from mail-we0-f180.google.com (HELO mail-we0-f180.google.com) (74.125.82.180) by server-10.tower-217.messagelabs.com with RC4-SHA encrypted SMTP; 16 Feb 2013 17:56:08 -0000 Received: by mail-we0-f180.google.com with SMTP id k14so3609941wer.25 for ; Sat, 16 Feb 2013 09:56:08 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:date:message-id:subject:from:to :content-type; bh=OTK7eymCYKF2YI2rRCLHzvl1r7ql/1cDLWX2b81ZK1Q=; b=aPYrnWYKVqjQStfuwi6yPZ24oBCK0sxWR4AU2XECP+Cty2p6HodMMYpAtICcRbqdla za7ZZJk4JkcMKrxbTuTpADiOgsWIvk7/Ky3XrPF7vsihqV2vhawAYLt9jBXult9A08jZ vccd5W8h5Brf+RLfFWMaDxw/kMKxbrLKFZRHq5TNri4IPN3APmxUDJAmYdHOBfH9s2L9 h2/c2EB/d/qBe1eGu/k2WEQUeohAKsHIZsSN02ONfmhcffwqCMJ9Wsk6WH0P6h8ytaK8 UsiXuuSey18u2r+c0y+mRqCapHfX16ea1tFDUz5hxpPq8OJRi3bBGf2wwe+a1bIi8/9b 6MEA== MIME-Version: 1.0 X-Received: by 10.180.85.103 with SMTP id g7mr10238221wiz.29.1361037368062; Sat, 16 Feb 2013 09:56:08 -0800 (PST) Received: by 10.216.236.13 with HTTP; Sat, 16 Feb 2013 09:56:07 -0800 (PST) Date: Sat, 16 Feb 2013 18:56:07 +0100 Message-ID: From: agya naila To: xen-devel@lists.xen.org, xen-users@lists.xen.org Subject: [Xen-users] Remus disk replication failed X-BeenThere: xen-users@lists.xen.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="===============3633592137188223771==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============3633592137188223771== Content-Type: multipart/alternative; boundary=f46d043bdce6d9728f04d5db3412 --f46d043bdce6d9728f04d5db3412 Content-Type: text/plain; charset=ISO-8859-1 Dear all, I am configure my machine to run the remus disk replication. I am using xen 4.2.3 installed from sources and Ubuntu 12.04 64 bit both for Dom0 and DomU. I have install the blktap and its work properly with configuration string phy or tap2 like this : disk = ['phy:/dev/vggroup/DomU,xvda,w'] or disk = ['tap2:tapdisk:aio:/dev/vggroup/DomU,xvda,w'] and remus command remus --no-net myvm mybackuphost However when I change the string as suggested on remus pages to enable the disk replication its still failed : name = "DomU" memory = 1024 disk = ['tap2:remus:10.10.10.3:8002|aio:/dev/vggroup/DomU,xvda,w'] vif = ['ip=192.168.1.55,bridge=xenbr0'] bootloader = "pygrub" with error messages : name1@machine1:~$ sudo xm create -c /etc/xen/DomU.cfg Using config file "/etc/xen/DomU.cfg". Error: ('create', '-aremus:10.10.10.3:8002|aio:/dev/vggroup/DomU') failed (512 ) and on the log file : name1@machine1:~$ sudo sudo tail /var/log/xen/xend.log mounted_vbd_uuid = dom0.create_vbd(vbd, disk); File "/usr/local/lib/python2.7/dist-packages/xen/xend/XendDomainInfo.py", line 3987, in create_vbd devid = dev_control.createDevice(config) File "/usr/local/lib/python2.7/dist-packages/xen/xend/server/BlktapController.py", line 174, in createDevice device = TapdiskController.create(params, file) File "/usr/local/lib/python2.7/dist-packages/xen/xend/server/BlktapController.py", line 286, in create return TapdiskController.exc('create', '-a%s:%s' % (dtype, image)) File "/usr/local/lib/python2.7/dist-packages/xen/xend/server/BlktapController.py", line 233, in exc (args, rc, out, err)) TapdiskException: ('create', '-aremus:10.10.10.3:8002|aio:/dev/vggroup/DomU') failed (512 ) Any hints and help would very appreciated. Regards, Agya --f46d043bdce6d9728f04d5db3412 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Dear all,

I am configure my machine to run the remus dis= k replication. I am using xen 4.2.3 installed from sources and Ubuntu 12.04= 64 bit both for Dom0 and DomU.=A0
I have install the blktap and its work properly with configuration= string phy or tap2 like this :
disk =3D ['phy:/dev/vggroup/= DomU,xvda,w']
o= r
disk =3D ['tap2:tapdi= sk:aio:/dev/vggroup/DomU,xvda,w']

and remus command=A0

<= div style=3D"color:rgb(34,34,34);font-size:13px;background-color:rgb(255,25= 5,255)"> remus --no-net myvm mybackuphost

However when I change th= e string as suggested on remus pages to enable the disk replication its sti= ll failed :

name =3D "DomU"
memory =3D 1024
disk =3D ['tap2:remus:10.10.10.3= :8002|aio:/dev/vggroup/DomU,xvda,w'] =A0
vif =3D ['ip=3D192.168.1.55,bridge=3Dxenbr0= 9;]
bootloader =3D "pygrub"= ;

with error messages :

name1@machine= 1:~$ sudo xm create -c /etc/xen/DomU.cfg
Using config file "/etc/xen/DomU.cfg".
Error: ('create', '-= aremus:10.10.10.3:8002|aio:/dev/vggroup/DomU') failed (512 =A0)<= /div>

and on the log file :

=

name1@machine1:~$ sudo sudo tail /var/log/= xen/xend.log
=A0 =A0 mounted_vbd_uuid =3D dom= 0.create_vbd(vbd, disk);
=A0 File "/usr/local/lib/python2.7/dist-packages/xen/xend/XendDom= ainInfo.py", line 3987, in create_vbd
=A0 =A0 devid =3D dev_control.cr= eateDevice(config)
= =A0 File "/usr/local/lib/python2.7/dist-packages/xen/xend/server/Blkta= pController.py", line 174, in createDevice
=A0 =A0 device =3D TapdiskContro= ller.create(params, file)
=A0 File "/usr/local/lib/python2.7/dist-packages/xen/xend/server= /BlktapController.py", line 286, in create
=A0 =A0 return TapdiskController= .exc('create', '-a%s:%s' % (dtype, image))
=A0 File "/usr/local/lib/python= 2.7/dist-packages/xen/xend/server/BlktapController.py", line 233, in e= xc
=A0 =A0 (args, rc, out, err))
TapdiskException: (= 9;create', '-aremus:10.10.10.3:8002|aio:/dev/vggroup/DomU') fai= led (512 =A0)

Any hints and help would very appreciated.

Regards,

Agya

--f46d043bdce6d9728f04d5db3412-- --===============3633592137188223771== 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 --===============3633592137188223771==-- From xen-users-bounces@lists.xen.org Sat Feb 16 17:57:22 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sat, 16 Feb 2013 17:57: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 1U6lzl-0006wT-PK; Sat, 16 Feb 2013 17:56:17 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U6lzj-0006wE-0t; Sat, 16 Feb 2013 17:56:15 +0000 Received: from [85.158.137.99:18629] by server-5.bemta-3.messagelabs.com id 1F/AF-04457-938CF115; Sat, 16 Feb 2013 17:56:09 +0000 X-Env-Sender: agya.naila@gmail.com X-Msg-Ref: server-10.tower-217.messagelabs.com!1361037368!20890405!1 X-Originating-IP: [74.125.82.180] 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.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 9784 invoked from network); 16 Feb 2013 17:56:08 -0000 Received: from mail-we0-f180.google.com (HELO mail-we0-f180.google.com) (74.125.82.180) by server-10.tower-217.messagelabs.com with RC4-SHA encrypted SMTP; 16 Feb 2013 17:56:08 -0000 Received: by mail-we0-f180.google.com with SMTP id k14so3609941wer.25 for ; Sat, 16 Feb 2013 09:56:08 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:date:message-id:subject:from:to :content-type; bh=OTK7eymCYKF2YI2rRCLHzvl1r7ql/1cDLWX2b81ZK1Q=; b=aPYrnWYKVqjQStfuwi6yPZ24oBCK0sxWR4AU2XECP+Cty2p6HodMMYpAtICcRbqdla za7ZZJk4JkcMKrxbTuTpADiOgsWIvk7/Ky3XrPF7vsihqV2vhawAYLt9jBXult9A08jZ vccd5W8h5Brf+RLfFWMaDxw/kMKxbrLKFZRHq5TNri4IPN3APmxUDJAmYdHOBfH9s2L9 h2/c2EB/d/qBe1eGu/k2WEQUeohAKsHIZsSN02ONfmhcffwqCMJ9Wsk6WH0P6h8ytaK8 UsiXuuSey18u2r+c0y+mRqCapHfX16ea1tFDUz5hxpPq8OJRi3bBGf2wwe+a1bIi8/9b 6MEA== MIME-Version: 1.0 X-Received: by 10.180.85.103 with SMTP id g7mr10238221wiz.29.1361037368062; Sat, 16 Feb 2013 09:56:08 -0800 (PST) Received: by 10.216.236.13 with HTTP; Sat, 16 Feb 2013 09:56:07 -0800 (PST) Date: Sat, 16 Feb 2013 18:56:07 +0100 Message-ID: From: agya naila To: xen-devel@lists.xen.org, xen-users@lists.xen.org Subject: [Xen-users] Remus disk replication failed X-BeenThere: xen-users@lists.xen.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="===============3633592137188223771==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============3633592137188223771== Content-Type: multipart/alternative; boundary=f46d043bdce6d9728f04d5db3412 --f46d043bdce6d9728f04d5db3412 Content-Type: text/plain; charset=ISO-8859-1 Dear all, I am configure my machine to run the remus disk replication. I am using xen 4.2.3 installed from sources and Ubuntu 12.04 64 bit both for Dom0 and DomU. I have install the blktap and its work properly with configuration string phy or tap2 like this : disk = ['phy:/dev/vggroup/DomU,xvda,w'] or disk = ['tap2:tapdisk:aio:/dev/vggroup/DomU,xvda,w'] and remus command remus --no-net myvm mybackuphost However when I change the string as suggested on remus pages to enable the disk replication its still failed : name = "DomU" memory = 1024 disk = ['tap2:remus:10.10.10.3:8002|aio:/dev/vggroup/DomU,xvda,w'] vif = ['ip=192.168.1.55,bridge=xenbr0'] bootloader = "pygrub" with error messages : name1@machine1:~$ sudo xm create -c /etc/xen/DomU.cfg Using config file "/etc/xen/DomU.cfg". Error: ('create', '-aremus:10.10.10.3:8002|aio:/dev/vggroup/DomU') failed (512 ) and on the log file : name1@machine1:~$ sudo sudo tail /var/log/xen/xend.log mounted_vbd_uuid = dom0.create_vbd(vbd, disk); File "/usr/local/lib/python2.7/dist-packages/xen/xend/XendDomainInfo.py", line 3987, in create_vbd devid = dev_control.createDevice(config) File "/usr/local/lib/python2.7/dist-packages/xen/xend/server/BlktapController.py", line 174, in createDevice device = TapdiskController.create(params, file) File "/usr/local/lib/python2.7/dist-packages/xen/xend/server/BlktapController.py", line 286, in create return TapdiskController.exc('create', '-a%s:%s' % (dtype, image)) File "/usr/local/lib/python2.7/dist-packages/xen/xend/server/BlktapController.py", line 233, in exc (args, rc, out, err)) TapdiskException: ('create', '-aremus:10.10.10.3:8002|aio:/dev/vggroup/DomU') failed (512 ) Any hints and help would very appreciated. Regards, Agya --f46d043bdce6d9728f04d5db3412 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Dear all,

I am configure my machine to run the remus dis= k replication. I am using xen 4.2.3 installed from sources and Ubuntu 12.04= 64 bit both for Dom0 and DomU.=A0
I have install the blktap and its work properly with configuration= string phy or tap2 like this :
disk =3D ['phy:/dev/vggroup/= DomU,xvda,w']
o= r
disk =3D ['tap2:tapdi= sk:aio:/dev/vggroup/DomU,xvda,w']

and remus command=A0

<= div style=3D"color:rgb(34,34,34);font-size:13px;background-color:rgb(255,25= 5,255)"> remus --no-net myvm mybackuphost

However when I change th= e string as suggested on remus pages to enable the disk replication its sti= ll failed :

name =3D "DomU"
memory =3D 1024
disk =3D ['tap2:remus:10.10.10.3= :8002|aio:/dev/vggroup/DomU,xvda,w'] =A0
vif =3D ['ip=3D192.168.1.55,bridge=3Dxenbr0= 9;]
bootloader =3D "pygrub"= ;

with error messages :

name1@machine= 1:~$ sudo xm create -c /etc/xen/DomU.cfg
Using config file "/etc/xen/DomU.cfg".
Error: ('create', '-= aremus:10.10.10.3:8002|aio:/dev/vggroup/DomU') failed (512 =A0)<= /div>

and on the log file :

=

name1@machine1:~$ sudo sudo tail /var/log/= xen/xend.log
=A0 =A0 mounted_vbd_uuid =3D dom= 0.create_vbd(vbd, disk);
=A0 File "/usr/local/lib/python2.7/dist-packages/xen/xend/XendDom= ainInfo.py", line 3987, in create_vbd
=A0 =A0 devid =3D dev_control.cr= eateDevice(config)
= =A0 File "/usr/local/lib/python2.7/dist-packages/xen/xend/server/Blkta= pController.py", line 174, in createDevice
=A0 =A0 device =3D TapdiskContro= ller.create(params, file)
=A0 File "/usr/local/lib/python2.7/dist-packages/xen/xend/server= /BlktapController.py", line 286, in create
=A0 =A0 return TapdiskController= .exc('create', '-a%s:%s' % (dtype, image))
=A0 File "/usr/local/lib/python= 2.7/dist-packages/xen/xend/server/BlktapController.py", line 233, in e= xc
=A0 =A0 (args, rc, out, err))
TapdiskException: (= 9;create', '-aremus:10.10.10.3:8002|aio:/dev/vggroup/DomU') fai= led (512 =A0)

Any hints and help would very appreciated.

Regards,

Agya

--f46d043bdce6d9728f04d5db3412-- --===============3633592137188223771== 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 --===============3633592137188223771==-- From xen-users-bounces@lists.xen.org Sat Feb 16 18:31:58 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sat, 16 Feb 2013 18:31: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 1U6mXJ-0007pa-Aj; Sat, 16 Feb 2013 18:30:57 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U6mXH-0007pV-52 for xen-users@lists.xen.org; Sat, 16 Feb 2013 18:30:55 +0000 Received: from [85.158.143.99:64643] by server-1.bemta-4.messagelabs.com id BA/1C-08839-E50DF115; Sat, 16 Feb 2013 18:30:54 +0000 X-Env-Sender: lists@hilboll.de X-Msg-Ref: server-3.tower-216.messagelabs.com!1361039453!27225380!1 X-Originating-IP: [130.185.108.51] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 4093 invoked from network); 16 Feb 2013 18:30:53 -0000 Received: from srv2.andreas-h.info (HELO srv2.andreas-h.info) (130.185.108.51) by server-3.tower-216.messagelabs.com with SMTP; 16 Feb 2013 18:30:53 -0000 Received: from localhost (localhost [127.0.0.1]) by srv2.andreas-h.info (Postfix) with ESMTP id 03E8D1C2549; Sat, 16 Feb 2013 19:30:25 +0100 (CET) X-Virus-Scanned: Debian amavisd-new at srv2.andreas-h.info Received: from srv2.andreas-h.info ([127.0.0.1]) by localhost (srv2.andreas-h.info [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0gxqOlxg5u2y; Sat, 16 Feb 2013 19:30:23 +0100 (CET) Received: from srv1.andreas-h.info (srv1.andreas-h.info [195.138.240.26]) by srv2.andreas-h.info (Postfix) with ESMTP id CF9B21C24C9; Sat, 16 Feb 2013 19:30:22 +0100 (CET) Received: from [192.168.178.26] (dyndsl-031-150-100-102.ewe-ip-backbone.de [31.150.100.102]) by srv1.andreas-h.info (Postfix) with ESMTPSA id EA5C5A605A6; Sat, 16 Feb 2013 19:30:49 +0100 (CET) Message-ID: <511FD059.10805@hilboll.de> Date: Sat, 16 Feb 2013 19:30:49 +0100 From: Andreas Hilboll User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130106 Thunderbird/17.0.2 MIME-Version: 1.0 To: Kartagis References: <511FB8EE.9010901@gmail.com> In-Reply-To: Cc: xen-users@lists.xen.org, ghudiczius@gmail.com Subject: Re: [Xen-users] Debootstrap X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org But you asked about debootstrap ;) With xen-create-image, you can write your own role scripts. Check --role and --role-dir in xen-create-image manpage. A. > I've read that, but I was wondering if the same could be done with > xen-create-image. > > On 16 February 2013 18:50, Gabor Hudiczius > wrote: > > Hi, > > man debootstrap states that there's a "--include=alpha,beta" option > for debootstrap, which takes a "comma separated list of packages > which will be added to download and extract lists". > > Regards, > Gabor Hudiczius > > > On 13.02.16. 12:02, Kartagis wrote: > > Hi, > > I don't know if this is the right mailing list, so please feel > free to > redirect me as appropriate. > > Having said that, how do I tell debootstrap which packages to > install in > the newly created VM? > > Regards, > > > _________________________________________________ > 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 Sat Feb 16 18:31:58 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sat, 16 Feb 2013 18:31: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 1U6mXJ-0007pa-Aj; Sat, 16 Feb 2013 18:30:57 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U6mXH-0007pV-52 for xen-users@lists.xen.org; Sat, 16 Feb 2013 18:30:55 +0000 Received: from [85.158.143.99:64643] by server-1.bemta-4.messagelabs.com id BA/1C-08839-E50DF115; Sat, 16 Feb 2013 18:30:54 +0000 X-Env-Sender: lists@hilboll.de X-Msg-Ref: server-3.tower-216.messagelabs.com!1361039453!27225380!1 X-Originating-IP: [130.185.108.51] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 4093 invoked from network); 16 Feb 2013 18:30:53 -0000 Received: from srv2.andreas-h.info (HELO srv2.andreas-h.info) (130.185.108.51) by server-3.tower-216.messagelabs.com with SMTP; 16 Feb 2013 18:30:53 -0000 Received: from localhost (localhost [127.0.0.1]) by srv2.andreas-h.info (Postfix) with ESMTP id 03E8D1C2549; Sat, 16 Feb 2013 19:30:25 +0100 (CET) X-Virus-Scanned: Debian amavisd-new at srv2.andreas-h.info Received: from srv2.andreas-h.info ([127.0.0.1]) by localhost (srv2.andreas-h.info [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0gxqOlxg5u2y; Sat, 16 Feb 2013 19:30:23 +0100 (CET) Received: from srv1.andreas-h.info (srv1.andreas-h.info [195.138.240.26]) by srv2.andreas-h.info (Postfix) with ESMTP id CF9B21C24C9; Sat, 16 Feb 2013 19:30:22 +0100 (CET) Received: from [192.168.178.26] (dyndsl-031-150-100-102.ewe-ip-backbone.de [31.150.100.102]) by srv1.andreas-h.info (Postfix) with ESMTPSA id EA5C5A605A6; Sat, 16 Feb 2013 19:30:49 +0100 (CET) Message-ID: <511FD059.10805@hilboll.de> Date: Sat, 16 Feb 2013 19:30:49 +0100 From: Andreas Hilboll User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130106 Thunderbird/17.0.2 MIME-Version: 1.0 To: Kartagis References: <511FB8EE.9010901@gmail.com> In-Reply-To: Cc: xen-users@lists.xen.org, ghudiczius@gmail.com Subject: Re: [Xen-users] Debootstrap X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org But you asked about debootstrap ;) With xen-create-image, you can write your own role scripts. Check --role and --role-dir in xen-create-image manpage. A. > I've read that, but I was wondering if the same could be done with > xen-create-image. > > On 16 February 2013 18:50, Gabor Hudiczius > wrote: > > Hi, > > man debootstrap states that there's a "--include=alpha,beta" option > for debootstrap, which takes a "comma separated list of packages > which will be added to download and extract lists". > > Regards, > Gabor Hudiczius > > > On 13.02.16. 12:02, Kartagis wrote: > > Hi, > > I don't know if this is the right mailing list, so please feel > free to > redirect me as appropriate. > > Having said that, how do I tell debootstrap which packages to > install in > the newly created VM? > > Regards, > > > _________________________________________________ > 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 Sat Feb 16 18:33:28 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sat, 16 Feb 2013 18:33: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 1U6mYq-00082n-1i; Sat, 16 Feb 2013 18:32:32 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U6mYo-00082d-EH for xen-users@lists.xen.org; Sat, 16 Feb 2013 18:32:30 +0000 Received: from [85.158.139.211:4420] by server-10.bemta-5.messagelabs.com id 66/24-04697-DB0DF115; Sat, 16 Feb 2013 18:32:29 +0000 X-Env-Sender: tolga@ozses.net X-Msg-Ref: server-2.tower-206.messagelabs.com!1361039546!21736518!1 X-Originating-IP: [209.85.210.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.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 13808 invoked from network); 16 Feb 2013 18:32:28 -0000 Received: from mail-da0-f45.google.com (HELO mail-da0-f45.google.com) (209.85.210.45) by server-2.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 16 Feb 2013 18:32:28 -0000 Received: by mail-da0-f45.google.com with SMTP id w4so1837937dam.18 for ; Sat, 16 Feb 2013 10:32:24 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-received:x-originating-ip:in-reply-to:references :date:message-id:subject:from:to:cc:content-type:x-gm-message-state; bh=FkOwFhWiaUcyglCfxiUgRBd/PuxEXqc6/ZFFPwCUpSI=; b=ZU2mKNylCFY6yObdQ2j2gluiuAWLeErAwQMiYzqM++9pex53zB/rK2ewiXR1QT6oyY rf8ZmXyfHC8p6tYXct//BC2E9gYOIRY+NfNrStsaAny6AA4/r0cI0NGFMDWZWaL1IiaI YxstxZb1hm5AjWtIseCuXam/VKv9nr064DMTN/z6jE0r7Ezbg55MFglSZO8CUpJLixgW h19z/74hOWGhEdn3B26LQJNM9t3SWdjQGuhKv8G+bSC8CNa5kr4G8WOQ4L+y4P7HyEzT USjUF1xGHXTlEhrVkAgQpWpxK8Jb3ALoMiqLi6saD/z2jCPOoxfBSyYdHZJihwa3Sytc BxoA== MIME-Version: 1.0 X-Received: by 10.68.190.231 with SMTP id gt7mr16361307pbc.117.1361039544143; Sat, 16 Feb 2013 10:32:24 -0800 (PST) Received: by 10.66.80.8 with HTTP; Sat, 16 Feb 2013 10:32:24 -0800 (PST) X-Originating-IP: [46.196.57.29] In-Reply-To: <511FD059.10805@hilboll.de> References: <511FB8EE.9010901@gmail.com> <511FD059.10805@hilboll.de> Date: Sat, 16 Feb 2013 20:32:24 +0200 Message-ID: From: Kartagis To: Andreas Hilboll X-Gm-Message-State: ALoCoQlUQZDICfvHcWiCUhYxP9kfguUb5CEVWrry3rt9mr2CyfAR49ckAFjek1I4bcVT1dtaL29I Cc: xen-users@lists.xen.org, ghudiczius@gmail.com Subject: Re: [Xen-users] Debootstrap X-BeenThere: xen-users@lists.xen.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="===============7583640681117978897==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============7583640681117978897== Content-Type: multipart/alternative; boundary=e89a8ff1c9668dcdf504d5dbb666 --e89a8ff1c9668dcdf504d5dbb666 Content-Type: text/plain; charset=ISO-8859-1 Yeah, sorry if I confused you. I meant to ask about --install-method=debootstrap On 16 February 2013 20:30, Andreas Hilboll wrote: > But you asked about debootstrap ;) > > With xen-create-image, you can write your own role scripts. Check --role > and --role-dir in xen-create-image manpage. > > A. > > > I've read that, but I was wondering if the same could be done with > > xen-create-image. > > > > On 16 February 2013 18:50, Gabor Hudiczius > > wrote: > > > > Hi, > > > > man debootstrap states that there's a "--include=alpha,beta" option > > for debootstrap, which takes a "comma separated list of packages > > which will be added to download and extract lists". > > > > Regards, > > Gabor Hudiczius > > > > > > On 13.02.16. 12:02, Kartagis wrote: > > > > Hi, > > > > I don't know if this is the right mailing list, so please feel > > free to > > redirect me as appropriate. > > > > Having said that, how do I tell debootstrap which packages to > > install in > > the newly created VM? > > > > Regards, > > > > > > _________________________________________________ > > 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 > > > > --e89a8ff1c9668dcdf504d5dbb666 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Yeah, sorry if I confused you. I meant to ask about --install-method=3Ddebo= otstrap

On 16 February 2013 20:30, Andrea= s Hilboll <lists@hilboll.de> wrote:
But you asked about debootstrap ;)

With xen-create-image, you can write your own role scripts. Check --role and --role-dir in xen-create-image manpage.

A.

> I've read that, but I was wondering if the same could be done with=
> xen-create-image.
>
> On 16 February 2013 18:50, Gabor Hudiczius <ghudiczius@gmail.com
> <mailto:ghudiczius@gmail.com>> wrote:
>
> =A0 =A0 Hi,
>
> =A0 =A0 man debootstrap states that there's a "--include=3Dal= pha,beta" option
> =A0 =A0 for debootstrap, which takes a "comma separated list of p= ackages
> =A0 =A0 which will be added to download and extract lists".
>
> =A0 =A0 Regards,
> =A0 =A0 Gabor Hudiczius
>
>
> =A0 =A0 On 13.02.16. 12:02, Kartagis wrote:
>
> =A0 =A0 =A0 =A0 Hi,
>
> =A0 =A0 =A0 =A0 I don't know if this is the right mailing list, so= please feel
> =A0 =A0 =A0 =A0 free to
> =A0 =A0 =A0 =A0 redirect me as appropriate.
>
> =A0 =A0 =A0 =A0 Having said that, how do I tell debootstrap which pack= ages to
> =A0 =A0 =A0 =A0 install in
> =A0 =A0 =A0 =A0 the newly created VM?
>
> =A0 =A0 =A0 =A0 Regards,
>
>
> =A0 =A0 =A0 =A0 ________________________________________________= _
> =A0 =A0 =A0 =A0 Xen-users mailing list
> =A0 =A0 =A0 =A0 Xen-users@l= ists.xen.org <mailto:Xen-= users@lists.xen.org>
> =A0 =A0 =A0 =A0 http://lists.xen.org/xen-users
>
>
>
> =A0 =A0 _________________________________________________
> =A0 =A0 Xen-users mailing list
> =A0 =A0 Xen-users@lists.xen= .org <mailto:Xen-users@li= sts.xen.org>
> =A0 =A0 http://lists.xen.org/xen-users >
>
>
>
> _______________________________________________
> Xen-users mailing list
> Xen-users@lists.xen.org=
> http://li= sts.xen.org/xen-users
>


--e89a8ff1c9668dcdf504d5dbb666-- --===============7583640681117978897== 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 --===============7583640681117978897==-- From xen-users-bounces@lists.xen.org Sat Feb 16 18:33:28 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sat, 16 Feb 2013 18:33: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 1U6mYq-00082n-1i; Sat, 16 Feb 2013 18:32:32 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U6mYo-00082d-EH for xen-users@lists.xen.org; Sat, 16 Feb 2013 18:32:30 +0000 Received: from [85.158.139.211:4420] by server-10.bemta-5.messagelabs.com id 66/24-04697-DB0DF115; Sat, 16 Feb 2013 18:32:29 +0000 X-Env-Sender: tolga@ozses.net X-Msg-Ref: server-2.tower-206.messagelabs.com!1361039546!21736518!1 X-Originating-IP: [209.85.210.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.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 13808 invoked from network); 16 Feb 2013 18:32:28 -0000 Received: from mail-da0-f45.google.com (HELO mail-da0-f45.google.com) (209.85.210.45) by server-2.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 16 Feb 2013 18:32:28 -0000 Received: by mail-da0-f45.google.com with SMTP id w4so1837937dam.18 for ; Sat, 16 Feb 2013 10:32:24 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-received:x-originating-ip:in-reply-to:references :date:message-id:subject:from:to:cc:content-type:x-gm-message-state; bh=FkOwFhWiaUcyglCfxiUgRBd/PuxEXqc6/ZFFPwCUpSI=; b=ZU2mKNylCFY6yObdQ2j2gluiuAWLeErAwQMiYzqM++9pex53zB/rK2ewiXR1QT6oyY rf8ZmXyfHC8p6tYXct//BC2E9gYOIRY+NfNrStsaAny6AA4/r0cI0NGFMDWZWaL1IiaI YxstxZb1hm5AjWtIseCuXam/VKv9nr064DMTN/z6jE0r7Ezbg55MFglSZO8CUpJLixgW h19z/74hOWGhEdn3B26LQJNM9t3SWdjQGuhKv8G+bSC8CNa5kr4G8WOQ4L+y4P7HyEzT USjUF1xGHXTlEhrVkAgQpWpxK8Jb3ALoMiqLi6saD/z2jCPOoxfBSyYdHZJihwa3Sytc BxoA== MIME-Version: 1.0 X-Received: by 10.68.190.231 with SMTP id gt7mr16361307pbc.117.1361039544143; Sat, 16 Feb 2013 10:32:24 -0800 (PST) Received: by 10.66.80.8 with HTTP; Sat, 16 Feb 2013 10:32:24 -0800 (PST) X-Originating-IP: [46.196.57.29] In-Reply-To: <511FD059.10805@hilboll.de> References: <511FB8EE.9010901@gmail.com> <511FD059.10805@hilboll.de> Date: Sat, 16 Feb 2013 20:32:24 +0200 Message-ID: From: Kartagis To: Andreas Hilboll X-Gm-Message-State: ALoCoQlUQZDICfvHcWiCUhYxP9kfguUb5CEVWrry3rt9mr2CyfAR49ckAFjek1I4bcVT1dtaL29I Cc: xen-users@lists.xen.org, ghudiczius@gmail.com Subject: Re: [Xen-users] Debootstrap X-BeenThere: xen-users@lists.xen.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="===============7583640681117978897==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============7583640681117978897== Content-Type: multipart/alternative; boundary=e89a8ff1c9668dcdf504d5dbb666 --e89a8ff1c9668dcdf504d5dbb666 Content-Type: text/plain; charset=ISO-8859-1 Yeah, sorry if I confused you. I meant to ask about --install-method=debootstrap On 16 February 2013 20:30, Andreas Hilboll wrote: > But you asked about debootstrap ;) > > With xen-create-image, you can write your own role scripts. Check --role > and --role-dir in xen-create-image manpage. > > A. > > > I've read that, but I was wondering if the same could be done with > > xen-create-image. > > > > On 16 February 2013 18:50, Gabor Hudiczius > > wrote: > > > > Hi, > > > > man debootstrap states that there's a "--include=alpha,beta" option > > for debootstrap, which takes a "comma separated list of packages > > which will be added to download and extract lists". > > > > Regards, > > Gabor Hudiczius > > > > > > On 13.02.16. 12:02, Kartagis wrote: > > > > Hi, > > > > I don't know if this is the right mailing list, so please feel > > free to > > redirect me as appropriate. > > > > Having said that, how do I tell debootstrap which packages to > > install in > > the newly created VM? > > > > Regards, > > > > > > _________________________________________________ > > 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 > > > > --e89a8ff1c9668dcdf504d5dbb666 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Yeah, sorry if I confused you. I meant to ask about --install-method=3Ddebo= otstrap

On 16 February 2013 20:30, Andrea= s Hilboll <lists@hilboll.de> wrote:
But you asked about debootstrap ;)

With xen-create-image, you can write your own role scripts. Check --role and --role-dir in xen-create-image manpage.

A.

> I've read that, but I was wondering if the same could be done with=
> xen-create-image.
>
> On 16 February 2013 18:50, Gabor Hudiczius <ghudiczius@gmail.com
> <mailto:ghudiczius@gmail.com>> wrote:
>
> =A0 =A0 Hi,
>
> =A0 =A0 man debootstrap states that there's a "--include=3Dal= pha,beta" option
> =A0 =A0 for debootstrap, which takes a "comma separated list of p= ackages
> =A0 =A0 which will be added to download and extract lists".
>
> =A0 =A0 Regards,
> =A0 =A0 Gabor Hudiczius
>
>
> =A0 =A0 On 13.02.16. 12:02, Kartagis wrote:
>
> =A0 =A0 =A0 =A0 Hi,
>
> =A0 =A0 =A0 =A0 I don't know if this is the right mailing list, so= please feel
> =A0 =A0 =A0 =A0 free to
> =A0 =A0 =A0 =A0 redirect me as appropriate.
>
> =A0 =A0 =A0 =A0 Having said that, how do I tell debootstrap which pack= ages to
> =A0 =A0 =A0 =A0 install in
> =A0 =A0 =A0 =A0 the newly created VM?
>
> =A0 =A0 =A0 =A0 Regards,
>
>
> =A0 =A0 =A0 =A0 ________________________________________________= _
> =A0 =A0 =A0 =A0 Xen-users mailing list
> =A0 =A0 =A0 =A0 Xen-users@l= ists.xen.org <mailto:Xen-= users@lists.xen.org>
> =A0 =A0 =A0 =A0 http://lists.xen.org/xen-users
>
>
>
> =A0 =A0 _________________________________________________
> =A0 =A0 Xen-users mailing list
> =A0 =A0 Xen-users@lists.xen= .org <mailto:Xen-users@li= sts.xen.org>
> =A0 =A0 http://lists.xen.org/xen-users >
>
>
>
> _______________________________________________
> Xen-users mailing list
> Xen-users@lists.xen.org=
> http://li= sts.xen.org/xen-users
>


--e89a8ff1c9668dcdf504d5dbb666-- --===============7583640681117978897== 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 --===============7583640681117978897==-- From xen-users-bounces@lists.xen.org Sat Feb 16 20:41:10 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sat, 16 Feb 2013 20:41: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 1U6oY9-0001jF-0c; Sat, 16 Feb 2013 20:39:57 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U6oY7-0001jA-D7 for xen-users@lists.xen.org; Sat, 16 Feb 2013 20:39:55 +0000 Received: from [85.158.139.211:17897] by server-8.bemta-5.messagelabs.com id F7/CA-19075-A9EEF115; Sat, 16 Feb 2013 20:39:54 +0000 X-Env-Sender: juliofong@mail.com X-Msg-Ref: server-14.tower-206.messagelabs.com!1361047193!22748983!1 X-Originating-IP: [74.208.4.200] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNzQuMjA4LjQuMjAwID0+IDYzNTg=\n, ML_RADAR_SPEW_LINKS_14, spamassassin: X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 16913 invoked from network); 16 Feb 2013 20:39:53 -0000 Received: from mout.gmx.net (HELO mout.gmx.net) (74.208.4.200) by server-14.tower-206.messagelabs.com with SMTP; 16 Feb 2013 20:39:53 -0000 Received: from mailout-us.gmx.com ([172.19.198.48]) by mrigmx.server.lan (mrigmxus002) with ESMTP (Nemesis) id 0MAeGl-1UCXqt25LH-00Bt11 for ; Sat, 16 Feb 2013 21:39:52 +0100 Received: (qmail 7695 invoked by uid 0); 16 Feb 2013 20:39:52 -0000 Received: from 86.66.222.237 by rms-us020 with HTTP Date: Sat, 16 Feb 2013 15:39:50 -0500 From: "FONG Julio" Message-ID: <20130216203950.129730@gmx.com> MIME-Version: 1.0 To: xen-users@lists.xen.org X-Authenticated: #76551402 X-Flags: 0001 X-Mailer: GMX.com Web Mailer x-registered: 0 X-GMX-UID: wYttcclT3zOlO4t3+3AhEpZ+IGRvbwDi Subject: Re: [Xen-users] add vif-route support to libxl/xl X-BeenThere: xen-users@lists.xen.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="===============6258698760729672345==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============6258698760729672345== Content-Type: multipart/alternative; boundary="========GMXBoundary129731361047190495118" --========GMXBoundary129731361047190495118 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit Hi roger, I saw your previous post here http://www.gossamer-threads.com/lists/xen/devel/270781 I would like to try the network route mode, may be you can show the way to apply your patch, this one I'm little bit confuse. Yours, Julio --========GMXBoundary129731361047190495118 Content-Type: text/html; charset="utf-8" Content-Transfer-Encoding: quoted-printable Hi roger= ,

I saw your previous post here http://www.gossamer-threads.com/= lists/xen/devel/270781
I would like to try the network route mode, may= be you can show the way to apply your patch, this one I'm little bit confu= se.

Yours, Julio --========GMXBoundary129731361047190495118-- --===============6258698760729672345== 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 --===============6258698760729672345==-- From xen-users-bounces@lists.xen.org Sat Feb 16 20:41:10 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sat, 16 Feb 2013 20:41: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 1U6oY9-0001jF-0c; Sat, 16 Feb 2013 20:39:57 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U6oY7-0001jA-D7 for xen-users@lists.xen.org; Sat, 16 Feb 2013 20:39:55 +0000 Received: from [85.158.139.211:17897] by server-8.bemta-5.messagelabs.com id F7/CA-19075-A9EEF115; Sat, 16 Feb 2013 20:39:54 +0000 X-Env-Sender: juliofong@mail.com X-Msg-Ref: server-14.tower-206.messagelabs.com!1361047193!22748983!1 X-Originating-IP: [74.208.4.200] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNzQuMjA4LjQuMjAwID0+IDYzNTg=\n, ML_RADAR_SPEW_LINKS_14, spamassassin: X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 16913 invoked from network); 16 Feb 2013 20:39:53 -0000 Received: from mout.gmx.net (HELO mout.gmx.net) (74.208.4.200) by server-14.tower-206.messagelabs.com with SMTP; 16 Feb 2013 20:39:53 -0000 Received: from mailout-us.gmx.com ([172.19.198.48]) by mrigmx.server.lan (mrigmxus002) with ESMTP (Nemesis) id 0MAeGl-1UCXqt25LH-00Bt11 for ; Sat, 16 Feb 2013 21:39:52 +0100 Received: (qmail 7695 invoked by uid 0); 16 Feb 2013 20:39:52 -0000 Received: from 86.66.222.237 by rms-us020 with HTTP Date: Sat, 16 Feb 2013 15:39:50 -0500 From: "FONG Julio" Message-ID: <20130216203950.129730@gmx.com> MIME-Version: 1.0 To: xen-users@lists.xen.org X-Authenticated: #76551402 X-Flags: 0001 X-Mailer: GMX.com Web Mailer x-registered: 0 X-GMX-UID: wYttcclT3zOlO4t3+3AhEpZ+IGRvbwDi Subject: Re: [Xen-users] add vif-route support to libxl/xl X-BeenThere: xen-users@lists.xen.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="===============6258698760729672345==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============6258698760729672345== Content-Type: multipart/alternative; boundary="========GMXBoundary129731361047190495118" --========GMXBoundary129731361047190495118 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit Hi roger, I saw your previous post here http://www.gossamer-threads.com/lists/xen/devel/270781 I would like to try the network route mode, may be you can show the way to apply your patch, this one I'm little bit confuse. Yours, Julio --========GMXBoundary129731361047190495118 Content-Type: text/html; charset="utf-8" Content-Transfer-Encoding: quoted-printable Hi roger= ,

I saw your previous post here http://www.gossamer-threads.com/= lists/xen/devel/270781
I would like to try the network route mode, may= be you can show the way to apply your patch, this one I'm little bit confu= se.

Yours, Julio --========GMXBoundary129731361047190495118-- --===============6258698760729672345== 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 --===============6258698760729672345==-- From xen-users-bounces@lists.xen.org Sun Feb 17 06:07:14 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sun, 17 Feb 2013 06:07: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 1U6xNf-0006Fo-KA; Sun, 17 Feb 2013 06:05:43 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U6xNe-0006Fj-6C for xen-users@lists.xen.org; Sun, 17 Feb 2013 06:05:42 +0000 Received: from [85.158.143.35:9957] by server-3.bemta-4.messagelabs.com id 12/78-08920-53370215; Sun, 17 Feb 2013 06:05:41 +0000 X-Env-Sender: jaceksburghardt@gmail.com X-Msg-Ref: server-7.tower-21.messagelabs.com!1361081138!11805064!1 X-Originating-IP: [209.85.223.172] X-SpamReason: No, hits=3.1 required=7.0 tests=HTML_00_10,HTML_MESSAGE, HTML_SHORT_LENGTH,ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 10122 invoked from network); 17 Feb 2013 06:05:40 -0000 Received: from mail-ie0-f172.google.com (HELO mail-ie0-f172.google.com) (209.85.223.172) by server-7.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 17 Feb 2013 06:05:40 -0000 Received: by mail-ie0-f172.google.com with SMTP id c10so6291102ieb.3 for ; Sat, 16 Feb 2013 22:05:38 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:date:message-id:subject:from:to :content-type; bh=kZc4L0biBe88hvm99Ssiw4gl2z9b5rIwnBdl0mhIrX0=; b=ZSVIjDwRtyFND0NIxu8QqSR/9slC+cnpfb3IEtWnV9hlkv8EdERpmPCaGtuWCAp/RV 5OP++9T+w2I1dalGNG+HsqMid3dHz6oX5DGkeQZ8/DblG6W/mq5AXzI+n9wtdS0RMk5N +BdijaHyRM9mplqqSPOOeOSx3ATKjcffdRMgWdqbid8Zc3vyl/ej6OCOHiTcTxhUoyDa pYQNB041XlDL1ycXmZ7sWq1u2dgZ7xjLskZZsvISvRVIhhGXsaJCcfZ4faq6WZYAmoUf Swpbcmlvuk4O1DQDZFBHHylbtcV+49u2eu+1gdX7Wfvs6/D0H7ubrgpopXgFzehLtKc4 yKmg== MIME-Version: 1.0 X-Received: by 10.50.34.131 with SMTP id z3mr5550599igi.30.1361081138187; Sat, 16 Feb 2013 22:05:38 -0800 (PST) Received: by 10.42.41.5 with HTTP; Sat, 16 Feb 2013 22:05:37 -0800 (PST) Date: Sat, 16 Feb 2013 23:05:37 -0700 Message-ID: From: jacek burghardt To: xen-users Subject: [Xen-users] gplpv drivers X-BeenThere: xen-users@lists.xen.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="===============5454266086975811496==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============5454266086975811496== Content-Type: multipart/alternative; boundary=14dae9340c4dc08ea304d5e56540 --14dae9340c4dc08ea304d5e56540 Content-Type: text/plain; charset=ISO-8859-1 Can someone point me to latest precompiled drivers . Signed would be nice. Can someone point me to microsoft sdk kits downloads --14dae9340c4dc08ea304d5e56540 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Can someone point me to latest precompiled drivers . Signed=A0 would be nic= e. Can someone point me to microsoft sdk kits downloads
--14dae9340c4dc08ea304d5e56540-- --===============5454266086975811496== 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 --===============5454266086975811496==-- From xen-users-bounces@lists.xen.org Sun Feb 17 06:07:14 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sun, 17 Feb 2013 06:07: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 1U6xNf-0006Fo-KA; Sun, 17 Feb 2013 06:05:43 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U6xNe-0006Fj-6C for xen-users@lists.xen.org; Sun, 17 Feb 2013 06:05:42 +0000 Received: from [85.158.143.35:9957] by server-3.bemta-4.messagelabs.com id 12/78-08920-53370215; Sun, 17 Feb 2013 06:05:41 +0000 X-Env-Sender: jaceksburghardt@gmail.com X-Msg-Ref: server-7.tower-21.messagelabs.com!1361081138!11805064!1 X-Originating-IP: [209.85.223.172] X-SpamReason: No, hits=3.1 required=7.0 tests=HTML_00_10,HTML_MESSAGE, HTML_SHORT_LENGTH,ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 10122 invoked from network); 17 Feb 2013 06:05:40 -0000 Received: from mail-ie0-f172.google.com (HELO mail-ie0-f172.google.com) (209.85.223.172) by server-7.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 17 Feb 2013 06:05:40 -0000 Received: by mail-ie0-f172.google.com with SMTP id c10so6291102ieb.3 for ; Sat, 16 Feb 2013 22:05:38 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:date:message-id:subject:from:to :content-type; bh=kZc4L0biBe88hvm99Ssiw4gl2z9b5rIwnBdl0mhIrX0=; b=ZSVIjDwRtyFND0NIxu8QqSR/9slC+cnpfb3IEtWnV9hlkv8EdERpmPCaGtuWCAp/RV 5OP++9T+w2I1dalGNG+HsqMid3dHz6oX5DGkeQZ8/DblG6W/mq5AXzI+n9wtdS0RMk5N +BdijaHyRM9mplqqSPOOeOSx3ATKjcffdRMgWdqbid8Zc3vyl/ej6OCOHiTcTxhUoyDa pYQNB041XlDL1ycXmZ7sWq1u2dgZ7xjLskZZsvISvRVIhhGXsaJCcfZ4faq6WZYAmoUf Swpbcmlvuk4O1DQDZFBHHylbtcV+49u2eu+1gdX7Wfvs6/D0H7ubrgpopXgFzehLtKc4 yKmg== MIME-Version: 1.0 X-Received: by 10.50.34.131 with SMTP id z3mr5550599igi.30.1361081138187; Sat, 16 Feb 2013 22:05:38 -0800 (PST) Received: by 10.42.41.5 with HTTP; Sat, 16 Feb 2013 22:05:37 -0800 (PST) Date: Sat, 16 Feb 2013 23:05:37 -0700 Message-ID: From: jacek burghardt To: xen-users Subject: [Xen-users] gplpv drivers X-BeenThere: xen-users@lists.xen.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="===============5454266086975811496==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============5454266086975811496== Content-Type: multipart/alternative; boundary=14dae9340c4dc08ea304d5e56540 --14dae9340c4dc08ea304d5e56540 Content-Type: text/plain; charset=ISO-8859-1 Can someone point me to latest precompiled drivers . Signed would be nice. Can someone point me to microsoft sdk kits downloads --14dae9340c4dc08ea304d5e56540 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Can someone point me to latest precompiled drivers . Signed=A0 would be nic= e. Can someone point me to microsoft sdk kits downloads
--14dae9340c4dc08ea304d5e56540-- --===============5454266086975811496== 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 --===============5454266086975811496==-- From xen-users-bounces@lists.xen.org Sun Feb 17 06:35:20 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sun, 17 Feb 2013 06:35: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 1U6xp6-0006ws-HB; Sun, 17 Feb 2013 06:34:04 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U6xp5-0006wn-GZ for xen-users@lists.xen.org; Sun, 17 Feb 2013 06:34:03 +0000 Received: from [85.158.139.83:13499] by server-14.bemta-5.messagelabs.com id F1/68-06967-AD970215; Sun, 17 Feb 2013 06:34:02 +0000 X-Env-Sender: daniel.farrell@gmail.com X-Msg-Ref: server-4.tower-182.messagelabs.com!1361082839!24895341!1 X-Originating-IP: [209.85.220.50] 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.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 10809 invoked from network); 17 Feb 2013 06:34:01 -0000 Received: from mail-pa0-f50.google.com (HELO mail-pa0-f50.google.com) (209.85.220.50) by server-4.tower-182.messagelabs.com with RC4-SHA encrypted SMTP; 17 Feb 2013 06:34:01 -0000 Received: by mail-pa0-f50.google.com with SMTP id fa11so2323445pad.23 for ; Sat, 16 Feb 2013 22:33:59 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:from:content-type:subject:message-id:date:to :mime-version:x-mailer; bh=npKUnNdB9xofz4rs3e74wYM766UdSV0jD8TlEhKCW2c=; b=MpiLs2O03xsAjZwvdkfIYVZW8nQMXqlpiCJir94JHb7xWW5vpXQ+ZFE8ZhsTbPFEfs MJpgYn5W1lgaZ10hG3tK63dscq/RmJDsuEyeMoS1Q1qlGfMPah6XBmX7TzGFe3rRqci+ Cogsf+m/tP7hWHD62vQM1jjrbCwyzOEKjMI2kXiY4siTXMEU2eKrv0/Ei7vnEnYjSjAa FdiHVy/Supxwo+A8SvZR03zpvAiM453/n/RSDcs8ku4e6MmUgRbXauxOQxjaoGrAnVXy c1pjq9+y8wpF57mGQQcKmcysp65xZIAhmkpP/hMNUx2aXGbWa6n0NM13ydEA+Eckdyob 2E0Q== X-Received: by 10.68.224.199 with SMTP id re7mr19681831pbc.108.1361082839583; Sat, 16 Feb 2013 22:33:59 -0800 (PST) Received: from lady-lula-belle.home (pool-108-0-220-206.lsanca.fios.verizon.net. [108.0.220.206]) by mx.google.com with ESMTPS id rn14sm10243888pbb.33.2013.02.16.22.33.57 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sat, 16 Feb 2013 22:33:58 -0800 (PST) From: Daniel Farrell Message-Id: <80883B3E-3FAF-481A-BA6E-700372B3018C@gmail.com> Date: Sat, 16 Feb 2013 22:33:56 -0800 To: xen-users@lists.xen.org Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\)) X-Mailer: Apple Mail (2.1499) Subject: [Xen-users] Install issues for Xen 4.2.1 on Ubuntu 12.10 X-BeenThere: xen-users@lists.xen.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="===============7149965062050313316==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============7149965062050313316== Content-Type: multipart/alternative; boundary="Apple-Mail=_E999E1AB-1950-4244-98CA-AF6D65FECA1D" --Apple-Mail=_E999E1AB-1950-4244-98CA-AF6D65FECA1D Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii Good evening everyone, I am attempting to compile Xen 4.2.1 from source on Ubuntu 12.10 and = cannot for the life of me figure out what I am doing wrong. This is the = script I wrote that I am running on a brand new install from = ubuntu-12.10-server-amd64.iso apt-get update apt-get -y upgrade apt-get -y dist-upgrade reboot (uname -r returns back 3.5.0-23-generic) apt-get install -y build-essential python-dev gettext bin86 bcc iasl = uuid-dev libncurses5-dev pkg-config libglib2.0-dev libyajl-dev git = gcc-multilib texinfo fakeroot libglib2.0-dev texinfo pciutils = pciutils-dev qemu-common gpg --recv-key 57E82BD9 wget = http://bits.xensource.com/oss-xen/release/4.2.1/xen-4.2.1.tar.gz.sig wget http://bits.xensource.com/oss-xen/release/4.2.1/xen-4.2.1.tar.gz gpg --verify xen-4.2.1.tar.gz.sig xen-4.2.1.tar.gz tar -vzxf xen-4.2.1.tar.gz cd xen-4.2.1 ./configure make install-xen make install-tools PYTHON_PREFIX_ARG=3D make install-kernels make install-stubdom make install-docs sed -i 's/GRUB_DEFAULT=3D.*\+/GRUB_DEFAULT=3D"Ubuntu GNU\/Linux, with = Xen hypervisor"/' /etc/default/grub sed -i 's/GRUB_CMDLINE_LINUX=3D.*\+/GRUB_CMDLINE_LINUX=3D"apparmor=3D0"/' = /etc/default/grub sed -i '/GRUB_CMDLINE_LINUX=3D"apparmor=3D0"/ = a\GRUB_CMDLINE_XEN=3D"dom0_mem=3D384M,max:384M dom0_max_vcpus=3D1 = no-bootscrub"' /etc/default/grub update-grub echo "none /proc/xen xenfs defaults 0 0" >> /etc/fstab reboot After the reboot -=20 $ ls /proc/xen capabilities privcmd xenbus xsd_kva xsd_port $ cat /proc/xen/capabilities control_d $ xl info libxl: error: libxl.c:87:libxl_ctx_alloc: Is xenstore daemon running? failed to stat /var/run/xenstored.pid: No such file or directory cannot init xl context Any help would be greatly appreciated. --Apple-Mail=_E999E1AB-1950-4244-98CA-AF6D65FECA1D Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=us-ascii Good = evening everyone,

I am attempting to compile Xen = 4.2.1 from source on Ubuntu 12.10 and cannot for the life of me figure = out what I am doing wrong. This is the script I wrote that I am running = on a brand new install = from ubuntu-12.10-server-amd64.iso

apt-get = update
apt-get -y upgrade
apt-get -y = dist-upgrade
reboot
(uname -r returns = back 3.5.0-23-generic)

apt-get install = -y build-essential python-dev gettext bin86 bcc iasl uuid-dev = libncurses5-dev pkg-config libglib2.0-dev libyajl-dev git gcc-multilib = texinfo fakeroot libglib2.0-dev texinfo pciutils = pciutils-dev qemu-common
gpg --recv-key = 57E82BD9
cd xen-4.2.1
./configure
make = install-xen
make install-tools PYTHON_PREFIX_ARG=3D
make = install-kernels
make install-stubdom
make install-docs
sed -i = 's/GRUB_DEFAULT=3D.*\+/GRUB_DEFAULT=3D"Ubuntu GNU\/Linux, with Xen = hypervisor"/' /etc/default/grub
sed -i = 's/GRUB_CMDLINE_LINUX=3D.*\+/GRUB_CMDLINE_LINUX=3D"apparmor=3D0"/' = /etc/default/grub
sed -i '/GRUB_CMDLINE_LINUX=3D"apparmor=3D0"/ = a\GRUB_CMDLINE_XEN=3D"dom0_mem=3D384M,max:384M dom0_max_vcpus=3D1 = no-bootscrub"' /etc/default/grub
update-grub
echo "none = /proc/xen xenfs defaults 0 0" >> = /etc/fstab
reboot

After the reboot = - 

$ ls /proc/xen
capabilities =  privcmd  xenbus  xsd_kva =  xsd_port

$ cat = /proc/xen/capabilities
control_d

$ xl = info
libxl: error: libxl.c:87:libxl_ctx_alloc: Is xenstore = daemon running?
failed to stat /var/run/xenstored.pid: No such file = or directory
cannot init xl context

Any help = would be greatly appreciated.

= --Apple-Mail=_E999E1AB-1950-4244-98CA-AF6D65FECA1D-- --===============7149965062050313316== 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 --===============7149965062050313316==-- From xen-users-bounces@lists.xen.org Sun Feb 17 06:35:20 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sun, 17 Feb 2013 06:35: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 1U6xp6-0006ws-HB; Sun, 17 Feb 2013 06:34:04 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U6xp5-0006wn-GZ for xen-users@lists.xen.org; Sun, 17 Feb 2013 06:34:03 +0000 Received: from [85.158.139.83:13499] by server-14.bemta-5.messagelabs.com id F1/68-06967-AD970215; Sun, 17 Feb 2013 06:34:02 +0000 X-Env-Sender: daniel.farrell@gmail.com X-Msg-Ref: server-4.tower-182.messagelabs.com!1361082839!24895341!1 X-Originating-IP: [209.85.220.50] 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.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 10809 invoked from network); 17 Feb 2013 06:34:01 -0000 Received: from mail-pa0-f50.google.com (HELO mail-pa0-f50.google.com) (209.85.220.50) by server-4.tower-182.messagelabs.com with RC4-SHA encrypted SMTP; 17 Feb 2013 06:34:01 -0000 Received: by mail-pa0-f50.google.com with SMTP id fa11so2323445pad.23 for ; Sat, 16 Feb 2013 22:33:59 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:from:content-type:subject:message-id:date:to :mime-version:x-mailer; bh=npKUnNdB9xofz4rs3e74wYM766UdSV0jD8TlEhKCW2c=; b=MpiLs2O03xsAjZwvdkfIYVZW8nQMXqlpiCJir94JHb7xWW5vpXQ+ZFE8ZhsTbPFEfs MJpgYn5W1lgaZ10hG3tK63dscq/RmJDsuEyeMoS1Q1qlGfMPah6XBmX7TzGFe3rRqci+ Cogsf+m/tP7hWHD62vQM1jjrbCwyzOEKjMI2kXiY4siTXMEU2eKrv0/Ei7vnEnYjSjAa FdiHVy/Supxwo+A8SvZR03zpvAiM453/n/RSDcs8ku4e6MmUgRbXauxOQxjaoGrAnVXy c1pjq9+y8wpF57mGQQcKmcysp65xZIAhmkpP/hMNUx2aXGbWa6n0NM13ydEA+Eckdyob 2E0Q== X-Received: by 10.68.224.199 with SMTP id re7mr19681831pbc.108.1361082839583; Sat, 16 Feb 2013 22:33:59 -0800 (PST) Received: from lady-lula-belle.home (pool-108-0-220-206.lsanca.fios.verizon.net. [108.0.220.206]) by mx.google.com with ESMTPS id rn14sm10243888pbb.33.2013.02.16.22.33.57 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sat, 16 Feb 2013 22:33:58 -0800 (PST) From: Daniel Farrell Message-Id: <80883B3E-3FAF-481A-BA6E-700372B3018C@gmail.com> Date: Sat, 16 Feb 2013 22:33:56 -0800 To: xen-users@lists.xen.org Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\)) X-Mailer: Apple Mail (2.1499) Subject: [Xen-users] Install issues for Xen 4.2.1 on Ubuntu 12.10 X-BeenThere: xen-users@lists.xen.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="===============7149965062050313316==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============7149965062050313316== Content-Type: multipart/alternative; boundary="Apple-Mail=_E999E1AB-1950-4244-98CA-AF6D65FECA1D" --Apple-Mail=_E999E1AB-1950-4244-98CA-AF6D65FECA1D Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii Good evening everyone, I am attempting to compile Xen 4.2.1 from source on Ubuntu 12.10 and = cannot for the life of me figure out what I am doing wrong. This is the = script I wrote that I am running on a brand new install from = ubuntu-12.10-server-amd64.iso apt-get update apt-get -y upgrade apt-get -y dist-upgrade reboot (uname -r returns back 3.5.0-23-generic) apt-get install -y build-essential python-dev gettext bin86 bcc iasl = uuid-dev libncurses5-dev pkg-config libglib2.0-dev libyajl-dev git = gcc-multilib texinfo fakeroot libglib2.0-dev texinfo pciutils = pciutils-dev qemu-common gpg --recv-key 57E82BD9 wget = http://bits.xensource.com/oss-xen/release/4.2.1/xen-4.2.1.tar.gz.sig wget http://bits.xensource.com/oss-xen/release/4.2.1/xen-4.2.1.tar.gz gpg --verify xen-4.2.1.tar.gz.sig xen-4.2.1.tar.gz tar -vzxf xen-4.2.1.tar.gz cd xen-4.2.1 ./configure make install-xen make install-tools PYTHON_PREFIX_ARG=3D make install-kernels make install-stubdom make install-docs sed -i 's/GRUB_DEFAULT=3D.*\+/GRUB_DEFAULT=3D"Ubuntu GNU\/Linux, with = Xen hypervisor"/' /etc/default/grub sed -i 's/GRUB_CMDLINE_LINUX=3D.*\+/GRUB_CMDLINE_LINUX=3D"apparmor=3D0"/' = /etc/default/grub sed -i '/GRUB_CMDLINE_LINUX=3D"apparmor=3D0"/ = a\GRUB_CMDLINE_XEN=3D"dom0_mem=3D384M,max:384M dom0_max_vcpus=3D1 = no-bootscrub"' /etc/default/grub update-grub echo "none /proc/xen xenfs defaults 0 0" >> /etc/fstab reboot After the reboot -=20 $ ls /proc/xen capabilities privcmd xenbus xsd_kva xsd_port $ cat /proc/xen/capabilities control_d $ xl info libxl: error: libxl.c:87:libxl_ctx_alloc: Is xenstore daemon running? failed to stat /var/run/xenstored.pid: No such file or directory cannot init xl context Any help would be greatly appreciated. --Apple-Mail=_E999E1AB-1950-4244-98CA-AF6D65FECA1D Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=us-ascii Good = evening everyone,

I am attempting to compile Xen = 4.2.1 from source on Ubuntu 12.10 and cannot for the life of me figure = out what I am doing wrong. This is the script I wrote that I am running = on a brand new install = from ubuntu-12.10-server-amd64.iso

apt-get = update
apt-get -y upgrade
apt-get -y = dist-upgrade
reboot
(uname -r returns = back 3.5.0-23-generic)

apt-get install = -y build-essential python-dev gettext bin86 bcc iasl uuid-dev = libncurses5-dev pkg-config libglib2.0-dev libyajl-dev git gcc-multilib = texinfo fakeroot libglib2.0-dev texinfo pciutils = pciutils-dev qemu-common
gpg --recv-key = 57E82BD9
cd xen-4.2.1
./configure
make = install-xen
make install-tools PYTHON_PREFIX_ARG=3D
make = install-kernels
make install-stubdom
make install-docs
sed -i = 's/GRUB_DEFAULT=3D.*\+/GRUB_DEFAULT=3D"Ubuntu GNU\/Linux, with Xen = hypervisor"/' /etc/default/grub
sed -i = 's/GRUB_CMDLINE_LINUX=3D.*\+/GRUB_CMDLINE_LINUX=3D"apparmor=3D0"/' = /etc/default/grub
sed -i '/GRUB_CMDLINE_LINUX=3D"apparmor=3D0"/ = a\GRUB_CMDLINE_XEN=3D"dom0_mem=3D384M,max:384M dom0_max_vcpus=3D1 = no-bootscrub"' /etc/default/grub
update-grub
echo "none = /proc/xen xenfs defaults 0 0" >> = /etc/fstab
reboot

After the reboot = - 

$ ls /proc/xen
capabilities =  privcmd  xenbus  xsd_kva =  xsd_port

$ cat = /proc/xen/capabilities
control_d

$ xl = info
libxl: error: libxl.c:87:libxl_ctx_alloc: Is xenstore = daemon running?
failed to stat /var/run/xenstored.pid: No such file = or directory
cannot init xl context

Any help = would be greatly appreciated.

= --Apple-Mail=_E999E1AB-1950-4244-98CA-AF6D65FECA1D-- --===============7149965062050313316== 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 --===============7149965062050313316==-- From xen-users-bounces@lists.xen.org Sun Feb 17 10:45:43 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sun, 17 Feb 2013 10: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 1U71jJ-0003XW-C5; Sun, 17 Feb 2013 10:44:21 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U71jH-0003XR-Fm for xen-users@lists.xen.org; Sun, 17 Feb 2013 10:44:19 +0000 Received: from [85.158.143.35:52020] by server-3.bemta-4.messagelabs.com id 11/18-08920-284B0215; Sun, 17 Feb 2013 10:44:18 +0000 X-Env-Sender: mossa@poisson.phc.unipi.it X-Msg-Ref: server-16.tower-21.messagelabs.com!1361097857!13429385!1 X-Originating-IP: [131.114.10.30] X-SpamReason: No, hits=0.5 required=7.0 tests=BODY_RANDOM_LONG X-StarScan-Received: X-StarScan-Version: 6.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 12047 invoked from network); 17 Feb 2013 10:44:18 -0000 Received: from poisson.phc.unipi.it (HELO poisson.phc.unipi.it) (131.114.10.30) by server-16.tower-21.messagelabs.com with SMTP; 17 Feb 2013 10:44:18 -0000 Received: from intersect (unknown [131.114.119.29]) (Authenticated sender: mossa) by poisson.phc.unipi.it (Postfix) with ESMTPSA id 0077A12600A; Sun, 17 Feb 2013 11:44:16 +0100 (CET) Date: Sun, 17 Feb 2013 11:44:12 +0100 From: Giorgio Mossa To: Daniel Farrell Message-ID: <20130217104412.GA2932@intersect> References: <80883B3E-3FAF-481A-BA6E-700372B3018C@gmail.com> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <80883B3E-3FAF-481A-BA6E-700372B3018C@gmail.com> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: xen-users@lists.xen.org Subject: Re: [Xen-users] Install issues for Xen 4.2.1 on Ubuntu 12.10 X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: 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, have you tryed the command sudo service xencommons start ? Giorgio On Sat, Feb 16, 2013 at 10:33:56PM -0800, Daniel Farrell wrote: > Good evening everyone, > > I am attempting to compile Xen 4.2.1 from source on Ubuntu 12.10 and cannot for the life of me figure out what I am doing wrong. This is the script I wrote that I am running on a brand new install from ubuntu-12.10-server-amd64.iso > > apt-get update > apt-get -y upgrade > apt-get -y dist-upgrade > reboot > (uname -r returns back 3.5.0-23-generic) > > apt-get install -y build-essential python-dev gettext bin86 bcc iasl uuid-dev libncurses5-dev pkg-config libglib2.0-dev libyajl-dev git gcc-multilib texinfo fakeroot libglib2.0-dev texinfo pciutils pciutils-dev qemu-common > gpg --recv-key 57E82BD9 > wget http://bits.xensource.com/oss-xen/release/4.2.1/xen-4.2.1.tar.gz.sig > wget http://bits.xensource.com/oss-xen/release/4.2.1/xen-4.2.1.tar.gz > gpg --verify xen-4.2.1.tar.gz.sig xen-4.2.1.tar.gz > tar -vzxf xen-4.2.1.tar.gz > cd xen-4.2.1 > ./configure > make install-xen > make install-tools PYTHON_PREFIX_ARG= > make install-kernels > make install-stubdom > make install-docs > sed -i 's/GRUB_DEFAULT=.*\+/GRUB_DEFAULT="Ubuntu GNU\/Linux, with Xen hypervisor"/' /etc/default/grub > sed -i 's/GRUB_CMDLINE_LINUX=.*\+/GRUB_CMDLINE_LINUX="apparmor=0"/' /etc/default/grub > sed -i '/GRUB_CMDLINE_LINUX="apparmor=0"/ a\GRUB_CMDLINE_XEN="dom0_mem=384M,max:384M dom0_max_vcpus=1 no-bootscrub"' /etc/default/grub > update-grub > echo "none /proc/xen xenfs defaults 0 0" >> /etc/fstab > reboot > > After the reboot - > > $ ls /proc/xen > capabilities privcmd xenbus xsd_kva xsd_port > > $ cat /proc/xen/capabilities > control_d > > $ xl info > libxl: error: libxl.c:87:libxl_ctx_alloc: Is xenstore daemon running? > failed to stat /var/run/xenstored.pid: No such file or directory > cannot init xl context > > Any help would be greatly appreciated. > > _______________________________________________ > 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 Feb 17 10:45:43 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sun, 17 Feb 2013 10: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 1U71jJ-0003XW-C5; Sun, 17 Feb 2013 10:44:21 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U71jH-0003XR-Fm for xen-users@lists.xen.org; Sun, 17 Feb 2013 10:44:19 +0000 Received: from [85.158.143.35:52020] by server-3.bemta-4.messagelabs.com id 11/18-08920-284B0215; Sun, 17 Feb 2013 10:44:18 +0000 X-Env-Sender: mossa@poisson.phc.unipi.it X-Msg-Ref: server-16.tower-21.messagelabs.com!1361097857!13429385!1 X-Originating-IP: [131.114.10.30] X-SpamReason: No, hits=0.5 required=7.0 tests=BODY_RANDOM_LONG X-StarScan-Received: X-StarScan-Version: 6.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 12047 invoked from network); 17 Feb 2013 10:44:18 -0000 Received: from poisson.phc.unipi.it (HELO poisson.phc.unipi.it) (131.114.10.30) by server-16.tower-21.messagelabs.com with SMTP; 17 Feb 2013 10:44:18 -0000 Received: from intersect (unknown [131.114.119.29]) (Authenticated sender: mossa) by poisson.phc.unipi.it (Postfix) with ESMTPSA id 0077A12600A; Sun, 17 Feb 2013 11:44:16 +0100 (CET) Date: Sun, 17 Feb 2013 11:44:12 +0100 From: Giorgio Mossa To: Daniel Farrell Message-ID: <20130217104412.GA2932@intersect> References: <80883B3E-3FAF-481A-BA6E-700372B3018C@gmail.com> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <80883B3E-3FAF-481A-BA6E-700372B3018C@gmail.com> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: xen-users@lists.xen.org Subject: Re: [Xen-users] Install issues for Xen 4.2.1 on Ubuntu 12.10 X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: 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, have you tryed the command sudo service xencommons start ? Giorgio On Sat, Feb 16, 2013 at 10:33:56PM -0800, Daniel Farrell wrote: > Good evening everyone, > > I am attempting to compile Xen 4.2.1 from source on Ubuntu 12.10 and cannot for the life of me figure out what I am doing wrong. This is the script I wrote that I am running on a brand new install from ubuntu-12.10-server-amd64.iso > > apt-get update > apt-get -y upgrade > apt-get -y dist-upgrade > reboot > (uname -r returns back 3.5.0-23-generic) > > apt-get install -y build-essential python-dev gettext bin86 bcc iasl uuid-dev libncurses5-dev pkg-config libglib2.0-dev libyajl-dev git gcc-multilib texinfo fakeroot libglib2.0-dev texinfo pciutils pciutils-dev qemu-common > gpg --recv-key 57E82BD9 > wget http://bits.xensource.com/oss-xen/release/4.2.1/xen-4.2.1.tar.gz.sig > wget http://bits.xensource.com/oss-xen/release/4.2.1/xen-4.2.1.tar.gz > gpg --verify xen-4.2.1.tar.gz.sig xen-4.2.1.tar.gz > tar -vzxf xen-4.2.1.tar.gz > cd xen-4.2.1 > ./configure > make install-xen > make install-tools PYTHON_PREFIX_ARG= > make install-kernels > make install-stubdom > make install-docs > sed -i 's/GRUB_DEFAULT=.*\+/GRUB_DEFAULT="Ubuntu GNU\/Linux, with Xen hypervisor"/' /etc/default/grub > sed -i 's/GRUB_CMDLINE_LINUX=.*\+/GRUB_CMDLINE_LINUX="apparmor=0"/' /etc/default/grub > sed -i '/GRUB_CMDLINE_LINUX="apparmor=0"/ a\GRUB_CMDLINE_XEN="dom0_mem=384M,max:384M dom0_max_vcpus=1 no-bootscrub"' /etc/default/grub > update-grub > echo "none /proc/xen xenfs defaults 0 0" >> /etc/fstab > reboot > > After the reboot - > > $ ls /proc/xen > capabilities privcmd xenbus xsd_kva xsd_port > > $ cat /proc/xen/capabilities > control_d > > $ xl info > libxl: error: libxl.c:87:libxl_ctx_alloc: Is xenstore daemon running? > failed to stat /var/run/xenstored.pid: No such file or directory > cannot init xl context > > Any help would be greatly appreciated. > > _______________________________________________ > 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 Feb 17 14:31:46 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sun, 17 Feb 2013 14:31: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 1U75GA-0007C0-FS; Sun, 17 Feb 2013 14:30:30 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U73wC-0005vB-BR for xen-users@lists.xen.org; Sun, 17 Feb 2013 13:05:48 +0000 Received: from [85.158.139.83:14721] by server-12.bemta-5.messagelabs.com id 57/F1-20195-BA5D0215; Sun, 17 Feb 2013 13:05:47 +0000 X-Env-Sender: tommy_scc@hotmail.com X-Msg-Ref: server-11.tower-182.messagelabs.com!1361106346!20412324!1 X-Originating-IP: [157.55.1.168] X-SpamReason: No, hits=0.6 required=7.0 tests=BODY_RANDOM_LONG, FORGED_HOTMAIL_RCVD,HTML_MESSAGE,ML_RADAR_SPEW_LINKS_12, ML_RADAR_SPEW_LINKS_14,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 18226 invoked from network); 17 Feb 2013 13:05:46 -0000 Received: from dub0-omc2-s29.dub0.hotmail.com (HELO dub0-omc2-s29.dub0.hotmail.com) (157.55.1.168) by server-11.tower-182.messagelabs.com with SMTP; 17 Feb 2013 13:05:46 -0000 Received: from DUB002-W73 ([157.55.1.136]) by dub0-omc2-s29.dub0.hotmail.com with Microsoft SMTPSVC(6.0.3790.4675); Sun, 17 Feb 2013 05:05:46 -0800 X-EIP: [5mVZ2S9dHBJJoGhwfhyaF4urwXw7lQzg] X-Originating-Email: [tommy_scc@hotmail.com] Message-ID: From: Tom To: "xen-users@lists.xen.org" Date: Sun, 17 Feb 2013 13:05:45 +0000 Importance: Normal MIME-Version: 1.0 X-OriginalArrivalTime: 17 Feb 2013 13:05:46.0007 (UTC) FILETIME=[7FCC0270:01CE0D0F] X-Mailman-Approved-At: Sun, 17 Feb 2013 14:30:28 +0000 Subject: [Xen-users] Issue with starting X with Intel gfx card (Ubuntu 12.10) X-BeenThere: xen-users@lists.xen.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="===============6139644232544153092==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============6139644232544153092== Content-Type: multipart/alternative; boundary="_df95780a-2007-44ac-9c70-be43de5ac24d_" --_df95780a-2007-44ac-9c70-be43de5ac24d_ Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable =0A= Hi=2C I'm trying to get my X working with Xen on my Ubuntu 12.10 oob installation= =2C but keeps on hanging on boot=3B lspci | grep VGA00:02.0 VGA compatible controller: Intel Corporation Xeon E= 3-1200 v2/3rd Gen Core processor Graphics Controller (rev 09)=0A= =0A= I've read about the Intel graphic cards which should be fully supported in = 3.x.x kernel versions. Kernel options in this generic kernel are enabled: CONFIG_INTEL_IOMMU=3Dy CONFIG_DMAR_TABLE=3Dy Any help would be greatly appreciated. = --_df95780a-2007-44ac-9c70-be43de5ac24d_ Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
=0A=
Hi=2C

I'm trying to get my X working with Xen on my = Ubuntu 12.10 oob installation=2C but keeps on hanging on boot=3B

lsp= ci | grep VGA
00:02.0 VGA compatible controller: Intel Corporation Xeon E3-12= 00 v2/3rd Gen Core processor Graphics Controller (rev 09)
=0A= =0A=
I've read about the Intel graphic cards which should be fully supported= in 3.x.x kernel versions. Kernel options in this generic kernel are enable= d:

CONFIG_INTEL_IOMMU=3Dy
CONFIG_DMAR_TABLE=3Dy

An=
y help would be greatly appreciated.

= --_df95780a-2007-44ac-9c70-be43de5ac24d_-- --===============6139644232544153092== 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 --===============6139644232544153092==-- From xen-users-bounces@lists.xen.org Sun Feb 17 14:31:46 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sun, 17 Feb 2013 14:31: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 1U75GA-0007C0-FS; Sun, 17 Feb 2013 14:30:30 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U73wC-0005vB-BR for xen-users@lists.xen.org; Sun, 17 Feb 2013 13:05:48 +0000 Received: from [85.158.139.83:14721] by server-12.bemta-5.messagelabs.com id 57/F1-20195-BA5D0215; Sun, 17 Feb 2013 13:05:47 +0000 X-Env-Sender: tommy_scc@hotmail.com X-Msg-Ref: server-11.tower-182.messagelabs.com!1361106346!20412324!1 X-Originating-IP: [157.55.1.168] X-SpamReason: No, hits=0.6 required=7.0 tests=BODY_RANDOM_LONG, FORGED_HOTMAIL_RCVD,HTML_MESSAGE,ML_RADAR_SPEW_LINKS_12, ML_RADAR_SPEW_LINKS_14,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 18226 invoked from network); 17 Feb 2013 13:05:46 -0000 Received: from dub0-omc2-s29.dub0.hotmail.com (HELO dub0-omc2-s29.dub0.hotmail.com) (157.55.1.168) by server-11.tower-182.messagelabs.com with SMTP; 17 Feb 2013 13:05:46 -0000 Received: from DUB002-W73 ([157.55.1.136]) by dub0-omc2-s29.dub0.hotmail.com with Microsoft SMTPSVC(6.0.3790.4675); Sun, 17 Feb 2013 05:05:46 -0800 X-EIP: [5mVZ2S9dHBJJoGhwfhyaF4urwXw7lQzg] X-Originating-Email: [tommy_scc@hotmail.com] Message-ID: From: Tom To: "xen-users@lists.xen.org" Date: Sun, 17 Feb 2013 13:05:45 +0000 Importance: Normal MIME-Version: 1.0 X-OriginalArrivalTime: 17 Feb 2013 13:05:46.0007 (UTC) FILETIME=[7FCC0270:01CE0D0F] X-Mailman-Approved-At: Sun, 17 Feb 2013 14:30:28 +0000 Subject: [Xen-users] Issue with starting X with Intel gfx card (Ubuntu 12.10) X-BeenThere: xen-users@lists.xen.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="===============6139644232544153092==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============6139644232544153092== Content-Type: multipart/alternative; boundary="_df95780a-2007-44ac-9c70-be43de5ac24d_" --_df95780a-2007-44ac-9c70-be43de5ac24d_ Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable =0A= Hi=2C I'm trying to get my X working with Xen on my Ubuntu 12.10 oob installation= =2C but keeps on hanging on boot=3B lspci | grep VGA00:02.0 VGA compatible controller: Intel Corporation Xeon E= 3-1200 v2/3rd Gen Core processor Graphics Controller (rev 09)=0A= =0A= I've read about the Intel graphic cards which should be fully supported in = 3.x.x kernel versions. Kernel options in this generic kernel are enabled: CONFIG_INTEL_IOMMU=3Dy CONFIG_DMAR_TABLE=3Dy Any help would be greatly appreciated. = --_df95780a-2007-44ac-9c70-be43de5ac24d_ Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
=0A=
Hi=2C

I'm trying to get my X working with Xen on my = Ubuntu 12.10 oob installation=2C but keeps on hanging on boot=3B

lsp= ci | grep VGA
00:02.0 VGA compatible controller: Intel Corporation Xeon E3-12= 00 v2/3rd Gen Core processor Graphics Controller (rev 09)
=0A= =0A=
I've read about the Intel graphic cards which should be fully supported= in 3.x.x kernel versions. Kernel options in this generic kernel are enable= d:

CONFIG_INTEL_IOMMU=3Dy
CONFIG_DMAR_TABLE=3Dy

An=
y help would be greatly appreciated.

= --_df95780a-2007-44ac-9c70-be43de5ac24d_-- --===============6139644232544153092== 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 --===============6139644232544153092==-- From xen-users-bounces@lists.xen.org Sun Feb 17 14:31:46 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sun, 17 Feb 2013 14:31: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 1U75G9-0007Br-SR; Sun, 17 Feb 2013 14:30:29 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U6xbU-0006fL-23 for xen-users@lists.xen.org; Sun, 17 Feb 2013 06:20:00 +0000 Received: from [85.158.143.99:7716] by server-3.bemta-4.messagelabs.com id 7F/4B-08920-F8670215; Sun, 17 Feb 2013 06:19:59 +0000 X-Env-Sender: daniel.farrell@gmail.com X-Msg-Ref: server-6.tower-216.messagelabs.com!1361081996!20822247!1 X-Originating-IP: [209.85.220.49] 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.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 25853 invoked from network); 17 Feb 2013 06:19:58 -0000 Received: from mail-pa0-f49.google.com (HELO mail-pa0-f49.google.com) (209.85.220.49) by server-6.tower-216.messagelabs.com with RC4-SHA encrypted SMTP; 17 Feb 2013 06:19:58 -0000 Received: by mail-pa0-f49.google.com with SMTP id kp6so2304175pab.8 for ; Sat, 16 Feb 2013 22:19:56 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:from:content-type:subject:message-id:date:to :mime-version:x-mailer; bh=jDRyRnwoUqPfZM1gQhfqfGXrrtdXRV2bBnLky1y/MoQ=; b=K8ufQU2NkJlZe6wolAI2jggKiKGJXty1ZIOSFh2NnWNtQpBMh1FWzlZuqFaKNV7E1z Qh0+lSvUWtzhT8Z1l6JYjSapw3xTvnZxaaZDO0vPBnOZZ9kwenGtP0FycRpg8XSYqPYi iGhc8EjilnZdZR0RuLx/InRlR9VflSsfpaSgJzhJr7o9yEEq5KmosIPgvIYU23nzffPB i4n+7AfT7iKGrDnvcFBOaGPJoJMl0nCYUboMyVwYmJrWGuLF0XOp/S/ZyGJjpmj/OyYZ xV+XWqbxitEhfmIdYbWq76HcOSGd9+w3zxd47/tcazxVOc4oVGrRjYMEl2iKR65dwMaD 17LQ== X-Received: by 10.66.72.201 with SMTP id f9mr25955577pav.38.1361081996088; Sat, 16 Feb 2013 22:19:56 -0800 (PST) Received: from lady-lula-belle.home (pool-108-0-220-206.lsanca.fios.verizon.net. [108.0.220.206]) by mx.google.com with ESMTPS id o5sm99345687pay.5.2013.02.16.22.19.53 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sat, 16 Feb 2013 22:19:54 -0800 (PST) From: Daniel Farrell Message-Id: <0C2D7A88-77C5-42D8-A071-1FF049C10F26@gmail.com> Date: Sat, 16 Feb 2013 22:19:51 -0800 To: xen-users@lists.xen.org Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\)) X-Mailer: Apple Mail (2.1499) X-Mailman-Approved-At: Sun, 17 Feb 2013 14:30:28 +0000 Subject: [Xen-users] Install issues for Xen 4.2.1 on Ubuntu 12.10 X-BeenThere: xen-users@lists.xen.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="===============3124001428338768900==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============3124001428338768900== Content-Type: multipart/alternative; boundary="Apple-Mail=_E773D353-037D-46F7-BE24-C1F69AE61442" --Apple-Mail=_E773D353-037D-46F7-BE24-C1F69AE61442 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii Good evening everyone, I am attempting to compile Xen 4.2.1 from source on Ubuntu 12.10 and = cannot for the life of me figure out what I am doing wrong. This is the = script I wrote that I am running on a brand new install from = ubuntu-12.10-server-amd64.iso apt-get update apt-get -y upgrade apt-get -y dist-upgrade reboot (uname -r returns back 3.5.0-23-generic) apt-get install -y build-essential python-dev gettext bin86 bcc iasl = uuid-dev libncurses5-dev pkg-config libglib2.0-dev libyajl-dev git = gcc-multilib texinfo fakeroot libglib2.0-dev texinfo pciutils = pciutils-dev qemu-common gpg --recv-key 57E82BD9 wget = http://bits.xensource.com/oss-xen/release/4.2.1/xen-4.2.1.tar.gz.sig wget http://bits.xensource.com/oss-xen/release/4.2.1/xen-4.2.1.tar.gz gpg --verify xen-4.2.1.tar.gz.sig xen-4.2.1.tar.gz tar -vzxf xen-4.2.1.tar.gz cd xen-4.2.1 ./configure make install-xen make install-tools PYTHON_PREFIX_ARG=3D make install-kernels make install-stubdom make install-docs sed -i 's/GRUB_DEFAULT=3D.*\+/GRUB_DEFAULT=3D"Ubuntu GNU\/Linux, with = Xen hypervisor"/' /etc/default/grub sed -i 's/GRUB_CMDLINE_LINUX=3D.*\+/GRUB_CMDLINE_LINUX=3D"apparmor=3D0"/' = /etc/default/grub sed -i '/GRUB_CMDLINE_LINUX=3D"apparmor=3D0"/ = a\GRUB_CMDLINE_XEN=3D"dom0_mem=3D384M,max:384M dom0_max_vcpus=3D1 = no-bootscrub"' /etc/default/grub update-grub echo "none /proc/xen xenfs defaults 0 0" >> /etc/fstab reboot After the reboot -=20 $ ls /proc/xen capabilities privcmd xenbus xsd_kva xsd_port $ cat /proc/xen/capabilities control_d $ xl info libxl: error: libxl.c:87:libxl_ctx_alloc: Is xenstore daemon running? failed to stat /var/run/xenstored.pid: No such file or directory cannot init xl context Any help would be greatly appreciated. --Apple-Mail=_E773D353-037D-46F7-BE24-C1F69AE61442 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=us-ascii Good = evening everyone,

I am attempting to compile Xen = 4.2.1 from source on Ubuntu 12.10 and cannot for the life of me figure = out what I am doing wrong. This is the script I wrote that I am running = on a brand new install = from ubuntu-12.10-server-amd64.iso

apt-get = update
apt-get -y upgrade
apt-get -y = dist-upgrade
reboot
(uname -r returns = back 3.5.0-23-generic)

apt-get install = -y build-essential python-dev gettext bin86 bcc iasl uuid-dev = libncurses5-dev pkg-config libglib2.0-dev libyajl-dev git gcc-multilib = texinfo fakeroot libglib2.0-dev texinfo pciutils = pciutils-dev qemu-common
gpg --recv-key = 57E82BD9
cd xen-4.2.1
./configure
make = install-xen
make install-tools PYTHON_PREFIX_ARG=3D
make = install-kernels
make install-stubdom
make install-docs
sed -i = 's/GRUB_DEFAULT=3D.*\+/GRUB_DEFAULT=3D"Ubuntu GNU\/Linux, with Xen = hypervisor"/' /etc/default/grub
sed -i = 's/GRUB_CMDLINE_LINUX=3D.*\+/GRUB_CMDLINE_LINUX=3D"apparmor=3D0"/' = /etc/default/grub
sed -i '/GRUB_CMDLINE_LINUX=3D"apparmor=3D0"/ = a\GRUB_CMDLINE_XEN=3D"dom0_mem=3D384M,max:384M dom0_max_vcpus=3D1 = no-bootscrub"' /etc/default/grub
update-grub
echo "none = /proc/xen xenfs defaults 0 0" >> = /etc/fstab
reboot

After the reboot = - 

$ ls /proc/xen
capabilities =  privcmd  xenbus  xsd_kva =  xsd_port

$ cat = /proc/xen/capabilities
control_d

$ xl = info
libxl: error: libxl.c:87:libxl_ctx_alloc: Is xenstore = daemon running?
failed to stat /var/run/xenstored.pid: No such file = or directory
cannot init xl context

Any help = would be greatly appreciated.

= --Apple-Mail=_E773D353-037D-46F7-BE24-C1F69AE61442-- --===============3124001428338768900== 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 --===============3124001428338768900==-- From xen-users-bounces@lists.xen.org Sun Feb 17 14:31:46 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sun, 17 Feb 2013 14:31: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 1U75G9-0007Br-SR; Sun, 17 Feb 2013 14:30:29 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U6xbU-0006fL-23 for xen-users@lists.xen.org; Sun, 17 Feb 2013 06:20:00 +0000 Received: from [85.158.143.99:7716] by server-3.bemta-4.messagelabs.com id 7F/4B-08920-F8670215; Sun, 17 Feb 2013 06:19:59 +0000 X-Env-Sender: daniel.farrell@gmail.com X-Msg-Ref: server-6.tower-216.messagelabs.com!1361081996!20822247!1 X-Originating-IP: [209.85.220.49] 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.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 25853 invoked from network); 17 Feb 2013 06:19:58 -0000 Received: from mail-pa0-f49.google.com (HELO mail-pa0-f49.google.com) (209.85.220.49) by server-6.tower-216.messagelabs.com with RC4-SHA encrypted SMTP; 17 Feb 2013 06:19:58 -0000 Received: by mail-pa0-f49.google.com with SMTP id kp6so2304175pab.8 for ; Sat, 16 Feb 2013 22:19:56 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:from:content-type:subject:message-id:date:to :mime-version:x-mailer; bh=jDRyRnwoUqPfZM1gQhfqfGXrrtdXRV2bBnLky1y/MoQ=; b=K8ufQU2NkJlZe6wolAI2jggKiKGJXty1ZIOSFh2NnWNtQpBMh1FWzlZuqFaKNV7E1z Qh0+lSvUWtzhT8Z1l6JYjSapw3xTvnZxaaZDO0vPBnOZZ9kwenGtP0FycRpg8XSYqPYi iGhc8EjilnZdZR0RuLx/InRlR9VflSsfpaSgJzhJr7o9yEEq5KmosIPgvIYU23nzffPB i4n+7AfT7iKGrDnvcFBOaGPJoJMl0nCYUboMyVwYmJrWGuLF0XOp/S/ZyGJjpmj/OyYZ xV+XWqbxitEhfmIdYbWq76HcOSGd9+w3zxd47/tcazxVOc4oVGrRjYMEl2iKR65dwMaD 17LQ== X-Received: by 10.66.72.201 with SMTP id f9mr25955577pav.38.1361081996088; Sat, 16 Feb 2013 22:19:56 -0800 (PST) Received: from lady-lula-belle.home (pool-108-0-220-206.lsanca.fios.verizon.net. [108.0.220.206]) by mx.google.com with ESMTPS id o5sm99345687pay.5.2013.02.16.22.19.53 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sat, 16 Feb 2013 22:19:54 -0800 (PST) From: Daniel Farrell Message-Id: <0C2D7A88-77C5-42D8-A071-1FF049C10F26@gmail.com> Date: Sat, 16 Feb 2013 22:19:51 -0800 To: xen-users@lists.xen.org Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\)) X-Mailer: Apple Mail (2.1499) X-Mailman-Approved-At: Sun, 17 Feb 2013 14:30:28 +0000 Subject: [Xen-users] Install issues for Xen 4.2.1 on Ubuntu 12.10 X-BeenThere: xen-users@lists.xen.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="===============3124001428338768900==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============3124001428338768900== Content-Type: multipart/alternative; boundary="Apple-Mail=_E773D353-037D-46F7-BE24-C1F69AE61442" --Apple-Mail=_E773D353-037D-46F7-BE24-C1F69AE61442 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii Good evening everyone, I am attempting to compile Xen 4.2.1 from source on Ubuntu 12.10 and = cannot for the life of me figure out what I am doing wrong. This is the = script I wrote that I am running on a brand new install from = ubuntu-12.10-server-amd64.iso apt-get update apt-get -y upgrade apt-get -y dist-upgrade reboot (uname -r returns back 3.5.0-23-generic) apt-get install -y build-essential python-dev gettext bin86 bcc iasl = uuid-dev libncurses5-dev pkg-config libglib2.0-dev libyajl-dev git = gcc-multilib texinfo fakeroot libglib2.0-dev texinfo pciutils = pciutils-dev qemu-common gpg --recv-key 57E82BD9 wget = http://bits.xensource.com/oss-xen/release/4.2.1/xen-4.2.1.tar.gz.sig wget http://bits.xensource.com/oss-xen/release/4.2.1/xen-4.2.1.tar.gz gpg --verify xen-4.2.1.tar.gz.sig xen-4.2.1.tar.gz tar -vzxf xen-4.2.1.tar.gz cd xen-4.2.1 ./configure make install-xen make install-tools PYTHON_PREFIX_ARG=3D make install-kernels make install-stubdom make install-docs sed -i 's/GRUB_DEFAULT=3D.*\+/GRUB_DEFAULT=3D"Ubuntu GNU\/Linux, with = Xen hypervisor"/' /etc/default/grub sed -i 's/GRUB_CMDLINE_LINUX=3D.*\+/GRUB_CMDLINE_LINUX=3D"apparmor=3D0"/' = /etc/default/grub sed -i '/GRUB_CMDLINE_LINUX=3D"apparmor=3D0"/ = a\GRUB_CMDLINE_XEN=3D"dom0_mem=3D384M,max:384M dom0_max_vcpus=3D1 = no-bootscrub"' /etc/default/grub update-grub echo "none /proc/xen xenfs defaults 0 0" >> /etc/fstab reboot After the reboot -=20 $ ls /proc/xen capabilities privcmd xenbus xsd_kva xsd_port $ cat /proc/xen/capabilities control_d $ xl info libxl: error: libxl.c:87:libxl_ctx_alloc: Is xenstore daemon running? failed to stat /var/run/xenstored.pid: No such file or directory cannot init xl context Any help would be greatly appreciated. --Apple-Mail=_E773D353-037D-46F7-BE24-C1F69AE61442 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=us-ascii Good = evening everyone,

I am attempting to compile Xen = 4.2.1 from source on Ubuntu 12.10 and cannot for the life of me figure = out what I am doing wrong. This is the script I wrote that I am running = on a brand new install = from ubuntu-12.10-server-amd64.iso

apt-get = update
apt-get -y upgrade
apt-get -y = dist-upgrade
reboot
(uname -r returns = back 3.5.0-23-generic)

apt-get install = -y build-essential python-dev gettext bin86 bcc iasl uuid-dev = libncurses5-dev pkg-config libglib2.0-dev libyajl-dev git gcc-multilib = texinfo fakeroot libglib2.0-dev texinfo pciutils = pciutils-dev qemu-common
gpg --recv-key = 57E82BD9
cd xen-4.2.1
./configure
make = install-xen
make install-tools PYTHON_PREFIX_ARG=3D
make = install-kernels
make install-stubdom
make install-docs
sed -i = 's/GRUB_DEFAULT=3D.*\+/GRUB_DEFAULT=3D"Ubuntu GNU\/Linux, with Xen = hypervisor"/' /etc/default/grub
sed -i = 's/GRUB_CMDLINE_LINUX=3D.*\+/GRUB_CMDLINE_LINUX=3D"apparmor=3D0"/' = /etc/default/grub
sed -i '/GRUB_CMDLINE_LINUX=3D"apparmor=3D0"/ = a\GRUB_CMDLINE_XEN=3D"dom0_mem=3D384M,max:384M dom0_max_vcpus=3D1 = no-bootscrub"' /etc/default/grub
update-grub
echo "none = /proc/xen xenfs defaults 0 0" >> = /etc/fstab
reboot

After the reboot = - 

$ ls /proc/xen
capabilities =  privcmd  xenbus  xsd_kva =  xsd_port

$ cat = /proc/xen/capabilities
control_d

$ xl = info
libxl: error: libxl.c:87:libxl_ctx_alloc: Is xenstore = daemon running?
failed to stat /var/run/xenstored.pid: No such file = or directory
cannot init xl context

Any help = would be greatly appreciated.

= --Apple-Mail=_E773D353-037D-46F7-BE24-C1F69AE61442-- --===============3124001428338768900== 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 --===============3124001428338768900==-- From xen-users-bounces@lists.xen.org Sun Feb 17 15:57:02 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sun, 17 Feb 2013 15:57: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 1U76am-0000kx-28; Sun, 17 Feb 2013 15:55:52 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U76ak-0000ks-QT for xen-users@lists.xen.org; Sun, 17 Feb 2013 15:55:51 +0000 Received: from [85.158.143.99:58996] by server-2.bemta-4.messagelabs.com id FB/7D-01597-68DF0215; Sun, 17 Feb 2013 15:55:50 +0000 X-Env-Sender: matthias.kannenberg@googlemail.com X-Msg-Ref: server-2.tower-216.messagelabs.com!1361116549!22562649!1 X-Originating-IP: [209.85.212.181] X-SpamReason: No, hits=0.3 required=7.0 tests=RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 28234 invoked from network); 17 Feb 2013 15:55:49 -0000 Received: from mail-wi0-f181.google.com (HELO mail-wi0-f181.google.com) (209.85.212.181) by server-2.tower-216.messagelabs.com with RC4-SHA encrypted SMTP; 17 Feb 2013 15:55:49 -0000 Received: by mail-wi0-f181.google.com with SMTP id hm6so2684434wib.8 for ; Sun, 17 Feb 2013 07:55:49 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=20120113; h=x-received:mime-version:in-reply-to:references:from:date:message-id :subject:to:cc:content-type; bh=uYSeh/kaBtR7SZr4cq0vQwUVLeSYM5c1B7shgH1ri1c=; b=a/9PpgiDNrQ5qlyZv2fo0hAqfxdv2cm0SLOc5MZOOiJs3jqJYf2hNqTXRA5b5S8Maa Ayt55YW3vddVy4xYv/ipD0sbo6Fdl1cSc1aJYLZD7+toN5/9lTTjCPctIqpE7zMBYXXD RVp3faJ1M9glheKwZiO6KwjtfVvDoUz3jzUSWNlMeatclj2dR1SLqM10LXHE/2LlaL8J BGyUujfgSa9R6z9DIXeqiIxuSEiG3rokA4iBhjmwIiny98R4lerU4wxaD1O3NryUc7NB khkmSwcFSpNGGYYxRHwKx6TT2YSjjI8SMt3T2Z/8YQ/IDLNLFRCrqnYJfiYIruhI7vz9 1Ixg== X-Received: by 10.194.57.206 with SMTP id k14mr14168796wjq.26.1361116549356; Sun, 17 Feb 2013 07:55:49 -0800 (PST) MIME-Version: 1.0 Received: by 10.194.80.68 with HTTP; Sun, 17 Feb 2013 07:55:29 -0800 (PST) In-Reply-To: References: From: Matthias Date: Sun, 17 Feb 2013 16:55:29 +0100 Message-ID: To: jacek burghardt Cc: xen-users Subject: Re: [Xen-users] gplpv drivers X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org Do you need something specific a simple google search for 'xen gplpv driver' didn't turned up? If not, just start here: http://wiki.xen.org/wiki/Xen_Windows_GplPv There are links for the signed and unsigned driver as well as the microsoft SDKs in the buildprocess subsection. But for simply installing you don't need the SDKs iirc. Off Topic: Why is there no reference to James on the wiki page? I think he deserves some credit :) 2013/2/17 jacek burghardt : > Can someone point me to latest precompiled drivers . Signed would be nice. > Can someone point me to microsoft sdk kits downloads > > _______________________________________________ > 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 Feb 17 15:57:02 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sun, 17 Feb 2013 15:57: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 1U76am-0000kx-28; Sun, 17 Feb 2013 15:55:52 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U76ak-0000ks-QT for xen-users@lists.xen.org; Sun, 17 Feb 2013 15:55:51 +0000 Received: from [85.158.143.99:58996] by server-2.bemta-4.messagelabs.com id FB/7D-01597-68DF0215; Sun, 17 Feb 2013 15:55:50 +0000 X-Env-Sender: matthias.kannenberg@googlemail.com X-Msg-Ref: server-2.tower-216.messagelabs.com!1361116549!22562649!1 X-Originating-IP: [209.85.212.181] X-SpamReason: No, hits=0.3 required=7.0 tests=RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 28234 invoked from network); 17 Feb 2013 15:55:49 -0000 Received: from mail-wi0-f181.google.com (HELO mail-wi0-f181.google.com) (209.85.212.181) by server-2.tower-216.messagelabs.com with RC4-SHA encrypted SMTP; 17 Feb 2013 15:55:49 -0000 Received: by mail-wi0-f181.google.com with SMTP id hm6so2684434wib.8 for ; Sun, 17 Feb 2013 07:55:49 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=20120113; h=x-received:mime-version:in-reply-to:references:from:date:message-id :subject:to:cc:content-type; bh=uYSeh/kaBtR7SZr4cq0vQwUVLeSYM5c1B7shgH1ri1c=; b=a/9PpgiDNrQ5qlyZv2fo0hAqfxdv2cm0SLOc5MZOOiJs3jqJYf2hNqTXRA5b5S8Maa Ayt55YW3vddVy4xYv/ipD0sbo6Fdl1cSc1aJYLZD7+toN5/9lTTjCPctIqpE7zMBYXXD RVp3faJ1M9glheKwZiO6KwjtfVvDoUz3jzUSWNlMeatclj2dR1SLqM10LXHE/2LlaL8J BGyUujfgSa9R6z9DIXeqiIxuSEiG3rokA4iBhjmwIiny98R4lerU4wxaD1O3NryUc7NB khkmSwcFSpNGGYYxRHwKx6TT2YSjjI8SMt3T2Z/8YQ/IDLNLFRCrqnYJfiYIruhI7vz9 1Ixg== X-Received: by 10.194.57.206 with SMTP id k14mr14168796wjq.26.1361116549356; Sun, 17 Feb 2013 07:55:49 -0800 (PST) MIME-Version: 1.0 Received: by 10.194.80.68 with HTTP; Sun, 17 Feb 2013 07:55:29 -0800 (PST) In-Reply-To: References: From: Matthias Date: Sun, 17 Feb 2013 16:55:29 +0100 Message-ID: To: jacek burghardt Cc: xen-users Subject: Re: [Xen-users] gplpv drivers X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org Do you need something specific a simple google search for 'xen gplpv driver' didn't turned up? If not, just start here: http://wiki.xen.org/wiki/Xen_Windows_GplPv There are links for the signed and unsigned driver as well as the microsoft SDKs in the buildprocess subsection. But for simply installing you don't need the SDKs iirc. Off Topic: Why is there no reference to James on the wiki page? I think he deserves some credit :) 2013/2/17 jacek burghardt : > Can someone point me to latest precompiled drivers . Signed would be nice. > Can someone point me to microsoft sdk kits downloads > > _______________________________________________ > 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 Feb 17 16:03:30 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sun, 17 Feb 2013 16: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 1U76h3-0001UI-4h; Sun, 17 Feb 2013 16:02:21 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U76h1-0001UC-H1 for xen-users@lists.xen.org; Sun, 17 Feb 2013 16:02:19 +0000 Received: from [85.158.138.51:10395] by server-3.bemta-3.messagelabs.com id 97/56-31070-50FF0215; Sun, 17 Feb 2013 16:02:13 +0000 X-Env-Sender: matthias.kannenberg@googlemail.com X-Msg-Ref: server-3.tower-174.messagelabs.com!1361116933!19811420!1 X-Originating-IP: [209.85.212.175] X-SpamReason: No, hits=0.3 required=7.0 tests=RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 17485 invoked from network); 17 Feb 2013 16:02:13 -0000 Received: from mail-wi0-f175.google.com (HELO mail-wi0-f175.google.com) (209.85.212.175) by server-3.tower-174.messagelabs.com with RC4-SHA encrypted SMTP; 17 Feb 2013 16:02:13 -0000 Received: by mail-wi0-f175.google.com with SMTP id l13so2664451wie.8 for ; Sun, 17 Feb 2013 08:02:13 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=20120113; h=x-received:mime-version:in-reply-to:references:from:date:message-id :subject:to:cc:content-type; bh=XYI2qnQvajzxIkFt0muTCfcZo3JFvSMlzGZHLCTgkoA=; b=V5Llm+UQYfD79QsfEomX8y3I6q3RLhFIuQ1JJBtbUnOMM0roPXmPwqqXGT2IDOxiGX x+Ob5WZ3159TZFCoFSOHv1m0NYd2Buo1xX6Sgao82yamdi3GxhX7wV25J8j/8qCHtC/G D3JHxFYCykH4H3HuvrrDG01ijiDnJg46pa5ZyuZFH2iOoFbVZ82lurEjXXBHekHp5h9Z aa6mx8T9jiGLTMVDjjlRsebC/V/32hsWFs1Hi1QzqLM2JZs36rDnt5mHiozJvnBOgLdP Pm1f4KQG9q6m90UoVgUnJHrYoZRQZ7zHlxR4H7YTSxn5B3s7hdd8hvpMF9ZcPzCSzbB2 cYsQ== X-Received: by 10.194.19.97 with SMTP id d1mr14084418wje.52.1361116933081; Sun, 17 Feb 2013 08:02:13 -0800 (PST) MIME-Version: 1.0 Received: by 10.194.80.68 with HTTP; Sun, 17 Feb 2013 08:01:53 -0800 (PST) In-Reply-To: <0C2D7A88-77C5-42D8-A071-1FF049C10F26@gmail.com> References: <0C2D7A88-77C5-42D8-A071-1FF049C10F26@gmail.com> From: Matthias Date: Sun, 17 Feb 2013 17:01:53 +0100 Message-ID: To: Daniel Farrell Cc: xen-users@lists.xen.org Subject: Re: [Xen-users] Install issues for Xen 4.2.1 on Ubuntu 12.10 X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: 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 think you missing the actuall make process in your script.. like make the individual packages or do a 'make world'.. If you are on a Debian based OS (as Ubuntu basically is), I found http://wiki.xen.org/wiki/Comprehensive_Xen_Debian_Wheezy_PCI_Passthrough_Tutorial (compiling xen section) very helpfull and building deb packages is much easier in the long term then normal build if you are switching xen versions later.. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Sun Feb 17 16:03:30 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sun, 17 Feb 2013 16: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 1U76h3-0001UI-4h; Sun, 17 Feb 2013 16:02:21 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U76h1-0001UC-H1 for xen-users@lists.xen.org; Sun, 17 Feb 2013 16:02:19 +0000 Received: from [85.158.138.51:10395] by server-3.bemta-3.messagelabs.com id 97/56-31070-50FF0215; Sun, 17 Feb 2013 16:02:13 +0000 X-Env-Sender: matthias.kannenberg@googlemail.com X-Msg-Ref: server-3.tower-174.messagelabs.com!1361116933!19811420!1 X-Originating-IP: [209.85.212.175] X-SpamReason: No, hits=0.3 required=7.0 tests=RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 17485 invoked from network); 17 Feb 2013 16:02:13 -0000 Received: from mail-wi0-f175.google.com (HELO mail-wi0-f175.google.com) (209.85.212.175) by server-3.tower-174.messagelabs.com with RC4-SHA encrypted SMTP; 17 Feb 2013 16:02:13 -0000 Received: by mail-wi0-f175.google.com with SMTP id l13so2664451wie.8 for ; Sun, 17 Feb 2013 08:02:13 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=20120113; h=x-received:mime-version:in-reply-to:references:from:date:message-id :subject:to:cc:content-type; bh=XYI2qnQvajzxIkFt0muTCfcZo3JFvSMlzGZHLCTgkoA=; b=V5Llm+UQYfD79QsfEomX8y3I6q3RLhFIuQ1JJBtbUnOMM0roPXmPwqqXGT2IDOxiGX x+Ob5WZ3159TZFCoFSOHv1m0NYd2Buo1xX6Sgao82yamdi3GxhX7wV25J8j/8qCHtC/G D3JHxFYCykH4H3HuvrrDG01ijiDnJg46pa5ZyuZFH2iOoFbVZ82lurEjXXBHekHp5h9Z aa6mx8T9jiGLTMVDjjlRsebC/V/32hsWFs1Hi1QzqLM2JZs36rDnt5mHiozJvnBOgLdP Pm1f4KQG9q6m90UoVgUnJHrYoZRQZ7zHlxR4H7YTSxn5B3s7hdd8hvpMF9ZcPzCSzbB2 cYsQ== X-Received: by 10.194.19.97 with SMTP id d1mr14084418wje.52.1361116933081; Sun, 17 Feb 2013 08:02:13 -0800 (PST) MIME-Version: 1.0 Received: by 10.194.80.68 with HTTP; Sun, 17 Feb 2013 08:01:53 -0800 (PST) In-Reply-To: <0C2D7A88-77C5-42D8-A071-1FF049C10F26@gmail.com> References: <0C2D7A88-77C5-42D8-A071-1FF049C10F26@gmail.com> From: Matthias Date: Sun, 17 Feb 2013 17:01:53 +0100 Message-ID: To: Daniel Farrell Cc: xen-users@lists.xen.org Subject: Re: [Xen-users] Install issues for Xen 4.2.1 on Ubuntu 12.10 X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: 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 think you missing the actuall make process in your script.. like make the individual packages or do a 'make world'.. If you are on a Debian based OS (as Ubuntu basically is), I found http://wiki.xen.org/wiki/Comprehensive_Xen_Debian_Wheezy_PCI_Passthrough_Tutorial (compiling xen section) very helpfull and building deb packages is much easier in the long term then normal build if you are switching xen versions later.. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Sun Feb 17 16:54:40 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sun, 17 Feb 2013 16: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 1U77UX-0002aR-FL; Sun, 17 Feb 2013 16:53:29 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U77UV-0002aM-1k for xen-users@lists.xen.org; Sun, 17 Feb 2013 16:53:27 +0000 Received: from [85.158.143.35:53216] by server-2.bemta-4.messagelabs.com id 3C/C8-01597-60B01215; Sun, 17 Feb 2013 16:53:26 +0000 X-Env-Sender: matthias.kannenberg@googlemail.com X-Msg-Ref: server-6.tower-21.messagelabs.com!1361120005!15919016!1 X-Originating-IP: [74.125.82.53] X-SpamReason: No, hits=0.8 required=7.0 tests=BODY_RANDOM_LONG, RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 20646 invoked from network); 17 Feb 2013 16:53:25 -0000 Received: from mail-wg0-f53.google.com (HELO mail-wg0-f53.google.com) (74.125.82.53) by server-6.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 17 Feb 2013 16:53:25 -0000 Received: by mail-wg0-f53.google.com with SMTP id fn15so4134974wgb.32 for ; Sun, 17 Feb 2013 08:53:25 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=20120113; h=x-received:mime-version:in-reply-to:references:from:date:message-id :subject:to:cc:content-type; bh=mCkyY0n2hDEfkCEGtWDwDiTYBDBUBXMsf1AIQV2Rj5I=; b=R3IxoujrNXHcEDMbz4RzDL7x4ws/ywzbt4RAabpKnEh+NiVkXSxFkQuo33qcf0Dgi9 v9UYniX9NTwVyJU/R/bxp6yW7xwj/kG4Ekba6SS0cRP1WNlfV0hnsCo3KW2xLypskZ1d U7fh3uCYKZkMvqQfKjt/mHsjRJ7LlUa4dCJa/C8ZuZarNiiocy1YCBnMSNuFgnk8OQw4 TDxOS0OMRWjkh+lx81d7MGd8JjPvK1UngkH7u2I88UKdUNFvknGYYSFN2nz6XJx+/qFq FReyrVttjbj/aSZNSRd3RQRG5e4a9aMPBkWUDunlmbSzKQ56liXmB42cMOv/sk9KpNVe ET+w== X-Received: by 10.194.19.97 with SMTP id d1mr14275940wje.52.1361120005275; Sun, 17 Feb 2013 08:53:25 -0800 (PST) MIME-Version: 1.0 Received: by 10.194.80.68 with HTTP; Sun, 17 Feb 2013 08:53:05 -0800 (PST) In-Reply-To: References: From: Matthias Date: Sun, 17 Feb 2013 17:53:05 +0100 Message-ID: To: jacek burghardt Cc: xen-users@lists.xen.org, James Harper Subject: Re: [Xen-users] gplpv drivers X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: 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 the one hand, yes, the most recent prebuild drivers are about a year old. This is because James Harper is doing, as far as I understood, a major rework on them tu cut irq usage to a minimum. But this seems to be mostly done and a new beta version for first testing will be released more sooner then later. On the other hand, you really should have a decent performance even without gplpv driver and near-native performance with the current one year old ones. So if you got major performance issues, it's very likely that this is not a gplpv issue. Two years ago I had a similar issue and found out I had to disable C-States in dom0 to get decent performance in my Windows domU. Just to show you that the issue can be in an entirely different place. Also, don't get your hopes too high on the new gplpv drivers cause afaik James uses a Win7 for testing his drivers and I haven't heard from anyone testing them on Win2012 yet. But never the less I added him in cc, maybe he can clerify the situation a bit more. 2013/2/17 jacek burghardt : > Well all precompiled drivers are one year old and it seems that lots had > changed. I installed signed driver with windows server 2012 and latest 4.3 > unstable and it seems that my server 2012 is very slow now. > > On Sun, Feb 17, 2013 at 8:55 AM, Matthias > wrote: >> >> Do you need something specific a simple google search for 'xen gplpv >> driver' didn't turned up? >> >> If not, just start here: http://wiki.xen.org/wiki/Xen_Windows_GplPv >> >> There are links for the signed and unsigned driver as well as the >> microsoft SDKs in the buildprocess subsection. But for simply >> installing you don't need the SDKs iirc. >> >> Off Topic: Why is there no reference to James on the wiki page? I >> think he deserves some credit :) >> >> 2013/2/17 jacek burghardt : >> > Can someone point me to latest precompiled drivers . Signed would be >> > nice. >> > Can someone point me to microsoft sdk kits downloads >> > >> > _______________________________________________ >> > 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 Feb 17 16:54:40 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sun, 17 Feb 2013 16: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 1U77UX-0002aR-FL; Sun, 17 Feb 2013 16:53:29 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U77UV-0002aM-1k for xen-users@lists.xen.org; Sun, 17 Feb 2013 16:53:27 +0000 Received: from [85.158.143.35:53216] by server-2.bemta-4.messagelabs.com id 3C/C8-01597-60B01215; Sun, 17 Feb 2013 16:53:26 +0000 X-Env-Sender: matthias.kannenberg@googlemail.com X-Msg-Ref: server-6.tower-21.messagelabs.com!1361120005!15919016!1 X-Originating-IP: [74.125.82.53] X-SpamReason: No, hits=0.8 required=7.0 tests=BODY_RANDOM_LONG, RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 20646 invoked from network); 17 Feb 2013 16:53:25 -0000 Received: from mail-wg0-f53.google.com (HELO mail-wg0-f53.google.com) (74.125.82.53) by server-6.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 17 Feb 2013 16:53:25 -0000 Received: by mail-wg0-f53.google.com with SMTP id fn15so4134974wgb.32 for ; Sun, 17 Feb 2013 08:53:25 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=20120113; h=x-received:mime-version:in-reply-to:references:from:date:message-id :subject:to:cc:content-type; bh=mCkyY0n2hDEfkCEGtWDwDiTYBDBUBXMsf1AIQV2Rj5I=; b=R3IxoujrNXHcEDMbz4RzDL7x4ws/ywzbt4RAabpKnEh+NiVkXSxFkQuo33qcf0Dgi9 v9UYniX9NTwVyJU/R/bxp6yW7xwj/kG4Ekba6SS0cRP1WNlfV0hnsCo3KW2xLypskZ1d U7fh3uCYKZkMvqQfKjt/mHsjRJ7LlUa4dCJa/C8ZuZarNiiocy1YCBnMSNuFgnk8OQw4 TDxOS0OMRWjkh+lx81d7MGd8JjPvK1UngkH7u2I88UKdUNFvknGYYSFN2nz6XJx+/qFq FReyrVttjbj/aSZNSRd3RQRG5e4a9aMPBkWUDunlmbSzKQ56liXmB42cMOv/sk9KpNVe ET+w== X-Received: by 10.194.19.97 with SMTP id d1mr14275940wje.52.1361120005275; Sun, 17 Feb 2013 08:53:25 -0800 (PST) MIME-Version: 1.0 Received: by 10.194.80.68 with HTTP; Sun, 17 Feb 2013 08:53:05 -0800 (PST) In-Reply-To: References: From: Matthias Date: Sun, 17 Feb 2013 17:53:05 +0100 Message-ID: To: jacek burghardt Cc: xen-users@lists.xen.org, James Harper Subject: Re: [Xen-users] gplpv drivers X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: 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 the one hand, yes, the most recent prebuild drivers are about a year old. This is because James Harper is doing, as far as I understood, a major rework on them tu cut irq usage to a minimum. But this seems to be mostly done and a new beta version for first testing will be released more sooner then later. On the other hand, you really should have a decent performance even without gplpv driver and near-native performance with the current one year old ones. So if you got major performance issues, it's very likely that this is not a gplpv issue. Two years ago I had a similar issue and found out I had to disable C-States in dom0 to get decent performance in my Windows domU. Just to show you that the issue can be in an entirely different place. Also, don't get your hopes too high on the new gplpv drivers cause afaik James uses a Win7 for testing his drivers and I haven't heard from anyone testing them on Win2012 yet. But never the less I added him in cc, maybe he can clerify the situation a bit more. 2013/2/17 jacek burghardt : > Well all precompiled drivers are one year old and it seems that lots had > changed. I installed signed driver with windows server 2012 and latest 4.3 > unstable and it seems that my server 2012 is very slow now. > > On Sun, Feb 17, 2013 at 8:55 AM, Matthias > wrote: >> >> Do you need something specific a simple google search for 'xen gplpv >> driver' didn't turned up? >> >> If not, just start here: http://wiki.xen.org/wiki/Xen_Windows_GplPv >> >> There are links for the signed and unsigned driver as well as the >> microsoft SDKs in the buildprocess subsection. But for simply >> installing you don't need the SDKs iirc. >> >> Off Topic: Why is there no reference to James on the wiki page? I >> think he deserves some credit :) >> >> 2013/2/17 jacek burghardt : >> > Can someone point me to latest precompiled drivers . Signed would be >> > nice. >> > Can someone point me to microsoft sdk kits downloads >> > >> > _______________________________________________ >> > 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 Feb 17 19:07:36 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sun, 17 Feb 2013 19:07: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 1U79YY-0004pu-Dq; Sun, 17 Feb 2013 19:05:46 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U79YW-0004pn-LM for xen-users@lists.xen.org; Sun, 17 Feb 2013 19:05:44 +0000 Received: from [85.158.139.211:25778] by server-4.bemta-5.messagelabs.com id 5B/B4-29496-70A21215; Sun, 17 Feb 2013 19:05:43 +0000 X-Env-Sender: murrayie@yahoo.co.uk X-Msg-Ref: server-13.tower-206.messagelabs.com!1361127942!18913750!1 X-Originating-IP: [77.238.189.222] 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.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 30160 invoked from network); 17 Feb 2013 19:05:42 -0000 Received: from nm7-vm0.bullet.mail.ird.yahoo.com (HELO nm7-vm0.bullet.mail.ird.yahoo.com) (77.238.189.222) by server-13.tower-206.messagelabs.com with SMTP; 17 Feb 2013 19:05:42 -0000 Received: from [212.82.105.245] by nm7.bullet.mail.ird.yahoo.com with NNFMP; 17 Feb 2013 19:05:42 -0000 Received: from [46.228.39.111] by tm17.bullet.mail.ird.yahoo.com with NNFMP; 17 Feb 2013 19:05:42 -0000 Received: from [127.0.0.1] by smtp148.mail.ir2.yahoo.com with NNFMP; 17 Feb 2013 19:05:42 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.co.uk; s=s1024; t=1361127942; bh=/2todiy3k0NGqdwPRngfm31u18kdyPEAof4Rdazyg/I=; 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:References:In-Reply-To:Content-Type:Content-Transfer-Encoding; b=KePX186sXYZoxrO4A/mA5VR8RfohPE+uEN6TldYE9DqjU/b7Jen60zihSFy+Vegf/jWG4dc6k8UZJ8TSz/TOftacLwv+1QFwQ8E98lzUGHfOQMbSgFxSqH5T24uk1IkFe+meia+hxKkOtaSlMR5939DlA0/aXylbaJYg04+UHsw= X-Yahoo-Newman-Id: 398196.47814.bm@smtp148.mail.ir2.yahoo.com X-Yahoo-Newman-Property: ymail-3 X-YMail-OSG: UL6ntnYVM1lu.yvtUJH3cg0SVvbFZlClpqGs.RP8AdkV85I f2Vjjn3kdB4HQY9LYSrUFuK7VzAaX.suEKes01orINphtAFmWZLLoWvG_uEo Hs8yiqpXfOZGXt_ZjqcFiDtwzZTSrfk_CtJBkCHX5V7XphaaWbIkI_ydsgp9 Vzt3n3.IoBD7Kj51sHs8spDJltd2qw1Wem_B96UT.OKoXSVacqgr2DYqUZmc WYN6ucpEsvTGhUjXxTeed.cGnjpNUnhmWyj0nMCowsvqCuzqqeA8mYM3Kggq rm0ZqGzyF2v.qg1eL7QTLuhVDCygHxes1AYVGj42OMvdS1TaNSI_XOxS.on8 h3p2gI6CJ3CsiGrbUT3VdLfTbxh.DLYuKnmWVXDSAmkEcLOW.IsnJqQD8pfQ sPMgU9qmjk9G4HvT7rmT2dJ7AFe4MPMtsPZR02HNL26NqGBat1EfHV1BocVW bY5puLmE_2gIkQO1cwE50XoIe.F_fc94hz9Peu0JQjc5_bHpBkdHKVdZufiF MQo4EercIDI_TJPhL7wllAFvN7SnhbkZDHCt.p10NwUNbOfboSk0- X-Yahoo-SMTP: P.LfrmaswBDlKN6tCvtOaEZlSVsY Received: from [192.168.88.150] (murrayie@87.127.155.20 with plain) by smtp148.mail.ir2.yahoo.com with SMTP; 17 Feb 2013 19:05:42 +0000 UTC Message-ID: <51212A08.1020901@yahoo.co.uk> Date: Sun, 17 Feb 2013 19:05:44 +0000 From: Ian User-Agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/20130106 Thunderbird/17.0.2 MIME-Version: 1.0 To: xen-users@lists.xen.org References: <0C2D7A88-77C5-42D8-A071-1FF049C10F26@gmail.com> In-Reply-To: <0C2D7A88-77C5-42D8-A071-1FF049C10F26@gmail.com> Subject: Re: [Xen-users] Install issues for Xen 4.2.1 on Ubuntu 12.10 X-BeenThere: xen-users@lists.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 17/02/13 06:19, Daniel Farrell wrote: > Good evening everyone, > > I am attempting to compile Xen 4.2.1 from source on Ubuntu 12.10 and > cannot for the life of me figure out what I am doing wrong. This is > the script I wrote that I am running on a brand new install > from ubuntu-12.10-server-amd64.iso > > apt-get update > apt-get -y upgrade > apt-get -y dist-upgrade > reboot > /(uname -r returns back 3.5.0-23-generic)/ > > apt-get install -y build-essential python-dev gettext bin86 bcc iasl > uuid-dev libncurses5-dev pkg-config libglib2.0-dev libyajl-dev git > gcc-multilib texinfo fakeroot libglib2.0-dev texinfo pciutils > pciutils-dev qemu-common > gpg --recv-key 57E82BD9 > wget http://bits.xensource.com/oss-xen/release/4.2.1/xen-4.2.1.tar.gz.sig > wget http://bits.xensource.com/oss-xen/release/4.2.1/xen-4.2.1.tar.gz > gpg --verify xen-4.2.1.tar.gz.sig xen-4.2.1.tar.gz > tar -vzxf xen-4.2.1.tar.gz > cd xen-4.2.1 > ./configure > make install-xen > make install-tools PYTHON_PREFIX_ARG= > make install-kernels > make install-stubdom > make install-docs > sed -i 's/GRUB_DEFAULT=.*\+/GRUB_DEFAULT="Ubuntu GNU\/Linux, with Xen > hypervisor"/' /etc/default/grub > sed -i 's/GRUB_CMDLINE_LINUX=.*\+/GRUB_CMDLINE_LINUX="apparmor=0"/' > /etc/default/grub > sed -i '/GRUB_CMDLINE_LINUX="apparmor=0"/ > a\GRUB_CMDLINE_XEN="dom0_mem=384M,max:384M dom0_max_vcpus=1 > no-bootscrub"' /etc/default/grub > update-grub > echo "none /proc/xen xenfs defaults 0 0" >> /etc/fstab > reboot > > After the reboot - > > $ ls /proc/xen > capabilities privcmd xenbus xsd_kva xsd_port > > $ cat /proc/xen/capabilities > control_d > > $ xl info > libxl: error: libxl.c:87:libxl_ctx_alloc: Is xenstore daemon running? > failed to stat /var/run/xenstored.pid: No such file or directory > cannot init xl context > > Any help would be greatly appreciated. > > > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xen.org > http://lists.xen.org/xen-users Did you start the xencommons service? _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Sun Feb 17 19:07:36 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sun, 17 Feb 2013 19:07: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 1U79YY-0004pu-Dq; Sun, 17 Feb 2013 19:05:46 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U79YW-0004pn-LM for xen-users@lists.xen.org; Sun, 17 Feb 2013 19:05:44 +0000 Received: from [85.158.139.211:25778] by server-4.bemta-5.messagelabs.com id 5B/B4-29496-70A21215; Sun, 17 Feb 2013 19:05:43 +0000 X-Env-Sender: murrayie@yahoo.co.uk X-Msg-Ref: server-13.tower-206.messagelabs.com!1361127942!18913750!1 X-Originating-IP: [77.238.189.222] 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.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 30160 invoked from network); 17 Feb 2013 19:05:42 -0000 Received: from nm7-vm0.bullet.mail.ird.yahoo.com (HELO nm7-vm0.bullet.mail.ird.yahoo.com) (77.238.189.222) by server-13.tower-206.messagelabs.com with SMTP; 17 Feb 2013 19:05:42 -0000 Received: from [212.82.105.245] by nm7.bullet.mail.ird.yahoo.com with NNFMP; 17 Feb 2013 19:05:42 -0000 Received: from [46.228.39.111] by tm17.bullet.mail.ird.yahoo.com with NNFMP; 17 Feb 2013 19:05:42 -0000 Received: from [127.0.0.1] by smtp148.mail.ir2.yahoo.com with NNFMP; 17 Feb 2013 19:05:42 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.co.uk; s=s1024; t=1361127942; bh=/2todiy3k0NGqdwPRngfm31u18kdyPEAof4Rdazyg/I=; 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:References:In-Reply-To:Content-Type:Content-Transfer-Encoding; b=KePX186sXYZoxrO4A/mA5VR8RfohPE+uEN6TldYE9DqjU/b7Jen60zihSFy+Vegf/jWG4dc6k8UZJ8TSz/TOftacLwv+1QFwQ8E98lzUGHfOQMbSgFxSqH5T24uk1IkFe+meia+hxKkOtaSlMR5939DlA0/aXylbaJYg04+UHsw= X-Yahoo-Newman-Id: 398196.47814.bm@smtp148.mail.ir2.yahoo.com X-Yahoo-Newman-Property: ymail-3 X-YMail-OSG: UL6ntnYVM1lu.yvtUJH3cg0SVvbFZlClpqGs.RP8AdkV85I f2Vjjn3kdB4HQY9LYSrUFuK7VzAaX.suEKes01orINphtAFmWZLLoWvG_uEo Hs8yiqpXfOZGXt_ZjqcFiDtwzZTSrfk_CtJBkCHX5V7XphaaWbIkI_ydsgp9 Vzt3n3.IoBD7Kj51sHs8spDJltd2qw1Wem_B96UT.OKoXSVacqgr2DYqUZmc WYN6ucpEsvTGhUjXxTeed.cGnjpNUnhmWyj0nMCowsvqCuzqqeA8mYM3Kggq rm0ZqGzyF2v.qg1eL7QTLuhVDCygHxes1AYVGj42OMvdS1TaNSI_XOxS.on8 h3p2gI6CJ3CsiGrbUT3VdLfTbxh.DLYuKnmWVXDSAmkEcLOW.IsnJqQD8pfQ sPMgU9qmjk9G4HvT7rmT2dJ7AFe4MPMtsPZR02HNL26NqGBat1EfHV1BocVW bY5puLmE_2gIkQO1cwE50XoIe.F_fc94hz9Peu0JQjc5_bHpBkdHKVdZufiF MQo4EercIDI_TJPhL7wllAFvN7SnhbkZDHCt.p10NwUNbOfboSk0- X-Yahoo-SMTP: P.LfrmaswBDlKN6tCvtOaEZlSVsY Received: from [192.168.88.150] (murrayie@87.127.155.20 with plain) by smtp148.mail.ir2.yahoo.com with SMTP; 17 Feb 2013 19:05:42 +0000 UTC Message-ID: <51212A08.1020901@yahoo.co.uk> Date: Sun, 17 Feb 2013 19:05:44 +0000 From: Ian User-Agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/20130106 Thunderbird/17.0.2 MIME-Version: 1.0 To: xen-users@lists.xen.org References: <0C2D7A88-77C5-42D8-A071-1FF049C10F26@gmail.com> In-Reply-To: <0C2D7A88-77C5-42D8-A071-1FF049C10F26@gmail.com> Subject: Re: [Xen-users] Install issues for Xen 4.2.1 on Ubuntu 12.10 X-BeenThere: xen-users@lists.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 17/02/13 06:19, Daniel Farrell wrote: > Good evening everyone, > > I am attempting to compile Xen 4.2.1 from source on Ubuntu 12.10 and > cannot for the life of me figure out what I am doing wrong. This is > the script I wrote that I am running on a brand new install > from ubuntu-12.10-server-amd64.iso > > apt-get update > apt-get -y upgrade > apt-get -y dist-upgrade > reboot > /(uname -r returns back 3.5.0-23-generic)/ > > apt-get install -y build-essential python-dev gettext bin86 bcc iasl > uuid-dev libncurses5-dev pkg-config libglib2.0-dev libyajl-dev git > gcc-multilib texinfo fakeroot libglib2.0-dev texinfo pciutils > pciutils-dev qemu-common > gpg --recv-key 57E82BD9 > wget http://bits.xensource.com/oss-xen/release/4.2.1/xen-4.2.1.tar.gz.sig > wget http://bits.xensource.com/oss-xen/release/4.2.1/xen-4.2.1.tar.gz > gpg --verify xen-4.2.1.tar.gz.sig xen-4.2.1.tar.gz > tar -vzxf xen-4.2.1.tar.gz > cd xen-4.2.1 > ./configure > make install-xen > make install-tools PYTHON_PREFIX_ARG= > make install-kernels > make install-stubdom > make install-docs > sed -i 's/GRUB_DEFAULT=.*\+/GRUB_DEFAULT="Ubuntu GNU\/Linux, with Xen > hypervisor"/' /etc/default/grub > sed -i 's/GRUB_CMDLINE_LINUX=.*\+/GRUB_CMDLINE_LINUX="apparmor=0"/' > /etc/default/grub > sed -i '/GRUB_CMDLINE_LINUX="apparmor=0"/ > a\GRUB_CMDLINE_XEN="dom0_mem=384M,max:384M dom0_max_vcpus=1 > no-bootscrub"' /etc/default/grub > update-grub > echo "none /proc/xen xenfs defaults 0 0" >> /etc/fstab > reboot > > After the reboot - > > $ ls /proc/xen > capabilities privcmd xenbus xsd_kva xsd_port > > $ cat /proc/xen/capabilities > control_d > > $ xl info > libxl: error: libxl.c:87:libxl_ctx_alloc: Is xenstore daemon running? > failed to stat /var/run/xenstored.pid: No such file or directory > cannot init xl context > > Any help would be greatly appreciated. > > > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xen.org > http://lists.xen.org/xen-users Did you start the xencommons service? _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Sun Feb 17 22:28:10 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sun, 17 Feb 2013 22:28: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 1U7Ch3-0006V9-30; Sun, 17 Feb 2013 22:26:45 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U7Ch1-0006V2-Vc for xen-users@lists.xen.org; Sun, 17 Feb 2013 22:26:44 +0000 Received: from [85.158.143.35:57822] by server-2.bemta-4.messagelabs.com id 1B/29-01597-32951215; Sun, 17 Feb 2013 22:26:43 +0000 X-Env-Sender: james.harper@bendigoit.com.au X-Msg-Ref: server-16.tower-21.messagelabs.com!1361139998!13466820!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.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 4039 invoked from network); 17 Feb 2013 22:26:41 -0000 Received: from smtp1.bendigoit.com.au (HELO smtp1.bendigoit.com.au) (203.16.224.4) by server-16.tower-21.messagelabs.com with AES256-SHA encrypted SMTP; 17 Feb 2013 22:26:41 -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 1U7Cgs-0005T3-76; Mon, 18 Feb 2013 09:26:34 +1100 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.0438.000; Mon, 18 Feb 2013 09:26:34 +1100 From: James Harper To: Matthias , jacek burghardt Thread-Topic: [Xen-users] gplpv drivers Thread-Index: AQHODNUEvK/f6C0a2kKmdL+CFSvrqZh9fFmAgADIxHyAAFvWIA== Date: Sun, 17 Feb 2013 22:26:32 +0000 Message-ID: <6035A0D088A63A46850C3988ED045A4B3567D7E6@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-19644.002 x-tm-as-result: No--25.075500-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] gplpv drivers X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org > Also, don't get your hopes too high on the new gplpv drivers cause > afaik James uses a Win7 for testing his drivers and I haven't heard > from anyone testing them on Win2012 yet. But never the less I added > him in cc, maybe he can clerify the situation a bit more. > 2012 works (as in boots and runs) but I haven't done any performance testing yet. Windows 8 has a feature where by default when you say shutdown it actually hibernates instead, and I'm having a bit of trouble getting hibernate working (or specifically, resume from hibernate). I think it won't actually matter too much because on resume from hibernate, windows uses bios calls to load the crash dump and this is horribly slow because it goes via qemu not gplpv so most people would turn off the feature, but I'd still like to have it working so a default install of win8 works and I don't get emails asking why it crashed etc. James _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Sun Feb 17 22:28:10 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sun, 17 Feb 2013 22:28: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 1U7Ch3-0006V9-30; Sun, 17 Feb 2013 22:26:45 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U7Ch1-0006V2-Vc for xen-users@lists.xen.org; Sun, 17 Feb 2013 22:26:44 +0000 Received: from [85.158.143.35:57822] by server-2.bemta-4.messagelabs.com id 1B/29-01597-32951215; Sun, 17 Feb 2013 22:26:43 +0000 X-Env-Sender: james.harper@bendigoit.com.au X-Msg-Ref: server-16.tower-21.messagelabs.com!1361139998!13466820!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.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 4039 invoked from network); 17 Feb 2013 22:26:41 -0000 Received: from smtp1.bendigoit.com.au (HELO smtp1.bendigoit.com.au) (203.16.224.4) by server-16.tower-21.messagelabs.com with AES256-SHA encrypted SMTP; 17 Feb 2013 22:26:41 -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 1U7Cgs-0005T3-76; Mon, 18 Feb 2013 09:26:34 +1100 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.0438.000; Mon, 18 Feb 2013 09:26:34 +1100 From: James Harper To: Matthias , jacek burghardt Thread-Topic: [Xen-users] gplpv drivers Thread-Index: AQHODNUEvK/f6C0a2kKmdL+CFSvrqZh9fFmAgADIxHyAAFvWIA== Date: Sun, 17 Feb 2013 22:26:32 +0000 Message-ID: <6035A0D088A63A46850C3988ED045A4B3567D7E6@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-19644.002 x-tm-as-result: No--25.075500-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] gplpv drivers X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org > Also, don't get your hopes too high on the new gplpv drivers cause > afaik James uses a Win7 for testing his drivers and I haven't heard > from anyone testing them on Win2012 yet. But never the less I added > him in cc, maybe he can clerify the situation a bit more. > 2012 works (as in boots and runs) but I haven't done any performance testing yet. Windows 8 has a feature where by default when you say shutdown it actually hibernates instead, and I'm having a bit of trouble getting hibernate working (or specifically, resume from hibernate). I think it won't actually matter too much because on resume from hibernate, windows uses bios calls to load the crash dump and this is horribly slow because it goes via qemu not gplpv so most people would turn off the feature, but I'd still like to have it working so a default install of win8 works and I don't get emails asking why it crashed etc. James _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Sun Feb 17 23:01:02 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sun, 17 Feb 2013 23: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 1U7DCy-0006x3-5C; Sun, 17 Feb 2013 22:59:44 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U7DCw-0006wy-6T for xen-users@lists.xen.org; Sun, 17 Feb 2013 22:59:42 +0000 Received: from [193.109.254.147:58529] by server-9.bemta-14.messagelabs.com id 66/48-30867-DD061215; Sun, 17 Feb 2013 22:59:41 +0000 X-Env-Sender: daniel.farrell@gmail.com X-Msg-Ref: server-14.tower-27.messagelabs.com!1361141979!1865481!1 X-Originating-IP: [209.85.220.47] X-SpamReason: No, hits=0.0 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, spamassassin: X-StarScan-Received: X-StarScan-Version: 6.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 23666 invoked from network); 17 Feb 2013 22:59:40 -0000 Received: from mail-pa0-f47.google.com (HELO mail-pa0-f47.google.com) (209.85.220.47) by server-14.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 17 Feb 2013 22:59:40 -0000 Received: by mail-pa0-f47.google.com with SMTP id bj3so2530499pad.34 for ; Sun, 17 Feb 2013 14:59:38 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:content-type:mime-version:subject:from:in-reply-to:date :cc:content-transfer-encoding:message-id:references:to:x-mailer; bh=phHIO6pv6G4fQFkXFi8dp7tsXfGJnYoVOCnzpI+pWgc=; b=IPDJjCO7kndjPTlrRAKcd4OkHP6+szB/YTV/cEqkxI2ZVQwXaSRdqzUhKLwoHw7vnp DZ0EdfH983iHJi8CtOQrgUlrAyemf2fjBkffV9wm4/oBlFRBrew04lGiPdkTZAX8z7ru /sY4tfAPHT1LY3LPF0bmt2DnQWCufvbZTEW0h5W6XDvTusAzh3JDvWdPW9R2fXs4ULNG f+GH5Jk5SYdXArf9J8aiMagEGFV8702C4uvFxzee7ZTXqUZKgtB59O9Xp4HYMpNSU7hg z+H5X9zEfN7WzIVTpf/pgsEjf/3PGvmhHvmGENP/MuOaLzMOj3OpPA6hVNx/0uzl9GI1 qqNQ== X-Received: by 10.67.22.33 with SMTP id hp1mr31277341pad.3.1361141978260; Sun, 17 Feb 2013 14:59:38 -0800 (PST) Received: from lady-lula-belle.home (pool-108-0-220-206.lsanca.fios.verizon.net. [108.0.220.206]) by mx.google.com with ESMTPS id pn9sm5462994pbb.22.2013.02.17.14.59.35 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sun, 17 Feb 2013 14:59:36 -0800 (PST) Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\)) From: Daniel Farrell In-Reply-To: Date: Sun, 17 Feb 2013 14:59:34 -0800 Message-Id: <41EF9148-EA07-4C43-A84C-153891C54BA9@gmail.com> References: <0C2D7A88-77C5-42D8-A071-1FF049C10F26@gmail.com> To: Matthias X-Mailer: Apple Mail (2.1499) Cc: xen-users@lists.xen.org Subject: Re: [Xen-users] Install issues for Xen 4.2.1 on Ubuntu 12.10 X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: 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 link. Figured it out On Feb 17, 2013, at 8:01 AM, Matthias wrote: > I think you missing the actuall make process in your script.. like > make the individual packages or do a 'make world'.. > > If you are on a Debian based OS (as Ubuntu basically is), I found > http://wiki.xen.org/wiki/Comprehensive_Xen_Debian_Wheezy_PCI_Passthrough_Tutorial > (compiling xen section) very helpfull and building deb packages is > much easier in the long term then normal build if you are switching > xen versions later.. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Sun Feb 17 23:01:02 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sun, 17 Feb 2013 23: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 1U7DCy-0006x3-5C; Sun, 17 Feb 2013 22:59:44 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U7DCw-0006wy-6T for xen-users@lists.xen.org; Sun, 17 Feb 2013 22:59:42 +0000 Received: from [193.109.254.147:58529] by server-9.bemta-14.messagelabs.com id 66/48-30867-DD061215; Sun, 17 Feb 2013 22:59:41 +0000 X-Env-Sender: daniel.farrell@gmail.com X-Msg-Ref: server-14.tower-27.messagelabs.com!1361141979!1865481!1 X-Originating-IP: [209.85.220.47] X-SpamReason: No, hits=0.0 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, spamassassin: X-StarScan-Received: X-StarScan-Version: 6.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 23666 invoked from network); 17 Feb 2013 22:59:40 -0000 Received: from mail-pa0-f47.google.com (HELO mail-pa0-f47.google.com) (209.85.220.47) by server-14.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 17 Feb 2013 22:59:40 -0000 Received: by mail-pa0-f47.google.com with SMTP id bj3so2530499pad.34 for ; Sun, 17 Feb 2013 14:59:38 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:content-type:mime-version:subject:from:in-reply-to:date :cc:content-transfer-encoding:message-id:references:to:x-mailer; bh=phHIO6pv6G4fQFkXFi8dp7tsXfGJnYoVOCnzpI+pWgc=; b=IPDJjCO7kndjPTlrRAKcd4OkHP6+szB/YTV/cEqkxI2ZVQwXaSRdqzUhKLwoHw7vnp DZ0EdfH983iHJi8CtOQrgUlrAyemf2fjBkffV9wm4/oBlFRBrew04lGiPdkTZAX8z7ru /sY4tfAPHT1LY3LPF0bmt2DnQWCufvbZTEW0h5W6XDvTusAzh3JDvWdPW9R2fXs4ULNG f+GH5Jk5SYdXArf9J8aiMagEGFV8702C4uvFxzee7ZTXqUZKgtB59O9Xp4HYMpNSU7hg z+H5X9zEfN7WzIVTpf/pgsEjf/3PGvmhHvmGENP/MuOaLzMOj3OpPA6hVNx/0uzl9GI1 qqNQ== X-Received: by 10.67.22.33 with SMTP id hp1mr31277341pad.3.1361141978260; Sun, 17 Feb 2013 14:59:38 -0800 (PST) Received: from lady-lula-belle.home (pool-108-0-220-206.lsanca.fios.verizon.net. [108.0.220.206]) by mx.google.com with ESMTPS id pn9sm5462994pbb.22.2013.02.17.14.59.35 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sun, 17 Feb 2013 14:59:36 -0800 (PST) Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\)) From: Daniel Farrell In-Reply-To: Date: Sun, 17 Feb 2013 14:59:34 -0800 Message-Id: <41EF9148-EA07-4C43-A84C-153891C54BA9@gmail.com> References: <0C2D7A88-77C5-42D8-A071-1FF049C10F26@gmail.com> To: Matthias X-Mailer: Apple Mail (2.1499) Cc: xen-users@lists.xen.org Subject: Re: [Xen-users] Install issues for Xen 4.2.1 on Ubuntu 12.10 X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: 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 link. Figured it out On Feb 17, 2013, at 8:01 AM, Matthias wrote: > I think you missing the actuall make process in your script.. like > make the individual packages or do a 'make world'.. > > If you are on a Debian based OS (as Ubuntu basically is), I found > http://wiki.xen.org/wiki/Comprehensive_Xen_Debian_Wheezy_PCI_Passthrough_Tutorial > (compiling xen section) very helpfull and building deb packages is > much easier in the long term then normal build if you are switching > xen versions later.. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Mon Feb 18 00:36:12 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 18 Feb 2013 00: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 1U7Eh1-0008A2-Kv; Mon, 18 Feb 2013 00:34:51 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U7Eh0-00089x-8G for xen-users@lists.xen.org; Mon, 18 Feb 2013 00:34:50 +0000 Received: from [85.158.143.99:21100] by server-2.bemta-4.messagelabs.com id BB/E4-01597-92771215; Mon, 18 Feb 2013 00:34:49 +0000 X-Env-Sender: mailing.son@gmail.com X-Msg-Ref: server-3.tower-216.messagelabs.com!1361147688!27316117!1 X-Originating-IP: [74.125.83.46] 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.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 11263 invoked from network); 18 Feb 2013 00:34:48 -0000 Received: from mail-ee0-f46.google.com (HELO mail-ee0-f46.google.com) (74.125.83.46) by server-3.tower-216.messagelabs.com with RC4-SHA encrypted SMTP; 18 Feb 2013 00:34:48 -0000 Received: by mail-ee0-f46.google.com with SMTP id e49so2585396eek.19 for ; Sun, 17 Feb 2013 16:34:48 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:date:message-id:subject:from:to :content-type; bh=NXnwdsL1BqcKl4cpaLZd74EMScu0bFTps10XtTzZPbQ=; b=IWycyxPhaKDZEAmSvYV3tOXGF8lr+OYTngvxnbslZ2E5ORwB2KpFzFLS3o+ZJBaaba ykn5XP+3uh6dbRHS4lLgf33NkGixpIbR9d5uprewi13e8RQI7LMDMPglY6qWzHQ+PqNw QOmN5oq8ahGUp3uinyvTKjFgUhS4my0pUl9Pf4UemDEpFxKOFm3zxFuuUjNHdN+uKZh4 Q/yeRT/zGEF7KApxIiOxkcyBkaICLV4JmsTDWkZBIFNrwX6tNutEWS+u8j88q2+/Tqwn F9uZzWVn6oj35pIKjm6H7NjldMsSiSBIqvzHDDdRzYy4yp1JWtZBnVBUgkRzHe1ZlJKy JtaQ== MIME-Version: 1.0 X-Received: by 10.14.218.71 with SMTP id j47mr37822566eep.28.1361147688493; Sun, 17 Feb 2013 16:34:48 -0800 (PST) Received: by 10.14.69.4 with HTTP; Sun, 17 Feb 2013 16:34:48 -0800 (PST) Date: Mon, 18 Feb 2013 09:34:48 +0900 Message-ID: From: Andrew Son To: xen-users@lists.xen.org Subject: [Xen-users] CPU cap and weight X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: 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 guest VM is configured with CAP like: xm sched-credit -d capvm --cap=10 xm sched-credit -d capvm Name ID Weight Cap capvm 2 256 10 The result of top command: top - 08:58:09 up 57 min, 3 users, load average: 1.54, 0.73, 0.46 Tasks: 110 total, 2 running, 108 sleeping, 0 stopped, 0 zombie Cpu0 : 0.0%us, 0.0%sy, 0.0%ni, 1.2%id, 3.2%wa, 0.0%hi, 0.0%si, 95.7%st Cpu1 : 0.0%us, 1.8%sy, 0.0%ni, 43.0%id, 5.4%wa, 0.0%hi, 0.0%si, 49.8%st Cpu2 : 0.0%us, 0.7%sy, 0.0%ni, 63.6%id, 6.0%wa, 0.0%hi, 0.0%si, 29.7%st Cpu3 : 0.1%us, 1.6%sy, 0.0%ni, 27.0%id, 40.1%wa, 0.0%hi, 0.0%si, 31.1%st Mem: 1048576k total, 997124k used, 51452k free, 176k buffers Swap: 2104504k total, 212416k used, 1892088k free, 6180k cached ... The guest VM suffers from steel time meaning guest vm can not get cpu cycles. Does this mean other guest vm can obtain cpu cycles or just waste my own cpu cycles? Thanks, _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Mon Feb 18 00:36:12 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 18 Feb 2013 00: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 1U7Eh1-0008A2-Kv; Mon, 18 Feb 2013 00:34:51 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U7Eh0-00089x-8G for xen-users@lists.xen.org; Mon, 18 Feb 2013 00:34:50 +0000 Received: from [85.158.143.99:21100] by server-2.bemta-4.messagelabs.com id BB/E4-01597-92771215; Mon, 18 Feb 2013 00:34:49 +0000 X-Env-Sender: mailing.son@gmail.com X-Msg-Ref: server-3.tower-216.messagelabs.com!1361147688!27316117!1 X-Originating-IP: [74.125.83.46] 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.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 11263 invoked from network); 18 Feb 2013 00:34:48 -0000 Received: from mail-ee0-f46.google.com (HELO mail-ee0-f46.google.com) (74.125.83.46) by server-3.tower-216.messagelabs.com with RC4-SHA encrypted SMTP; 18 Feb 2013 00:34:48 -0000 Received: by mail-ee0-f46.google.com with SMTP id e49so2585396eek.19 for ; Sun, 17 Feb 2013 16:34:48 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:date:message-id:subject:from:to :content-type; bh=NXnwdsL1BqcKl4cpaLZd74EMScu0bFTps10XtTzZPbQ=; b=IWycyxPhaKDZEAmSvYV3tOXGF8lr+OYTngvxnbslZ2E5ORwB2KpFzFLS3o+ZJBaaba ykn5XP+3uh6dbRHS4lLgf33NkGixpIbR9d5uprewi13e8RQI7LMDMPglY6qWzHQ+PqNw QOmN5oq8ahGUp3uinyvTKjFgUhS4my0pUl9Pf4UemDEpFxKOFm3zxFuuUjNHdN+uKZh4 Q/yeRT/zGEF7KApxIiOxkcyBkaICLV4JmsTDWkZBIFNrwX6tNutEWS+u8j88q2+/Tqwn F9uZzWVn6oj35pIKjm6H7NjldMsSiSBIqvzHDDdRzYy4yp1JWtZBnVBUgkRzHe1ZlJKy JtaQ== MIME-Version: 1.0 X-Received: by 10.14.218.71 with SMTP id j47mr37822566eep.28.1361147688493; Sun, 17 Feb 2013 16:34:48 -0800 (PST) Received: by 10.14.69.4 with HTTP; Sun, 17 Feb 2013 16:34:48 -0800 (PST) Date: Mon, 18 Feb 2013 09:34:48 +0900 Message-ID: From: Andrew Son To: xen-users@lists.xen.org Subject: [Xen-users] CPU cap and weight X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: 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 guest VM is configured with CAP like: xm sched-credit -d capvm --cap=10 xm sched-credit -d capvm Name ID Weight Cap capvm 2 256 10 The result of top command: top - 08:58:09 up 57 min, 3 users, load average: 1.54, 0.73, 0.46 Tasks: 110 total, 2 running, 108 sleeping, 0 stopped, 0 zombie Cpu0 : 0.0%us, 0.0%sy, 0.0%ni, 1.2%id, 3.2%wa, 0.0%hi, 0.0%si, 95.7%st Cpu1 : 0.0%us, 1.8%sy, 0.0%ni, 43.0%id, 5.4%wa, 0.0%hi, 0.0%si, 49.8%st Cpu2 : 0.0%us, 0.7%sy, 0.0%ni, 63.6%id, 6.0%wa, 0.0%hi, 0.0%si, 29.7%st Cpu3 : 0.1%us, 1.6%sy, 0.0%ni, 27.0%id, 40.1%wa, 0.0%hi, 0.0%si, 31.1%st Mem: 1048576k total, 997124k used, 51452k free, 176k buffers Swap: 2104504k total, 212416k used, 1892088k free, 6180k cached ... The guest VM suffers from steel time meaning guest vm can not get cpu cycles. Does this mean other guest vm can obtain cpu cycles or just waste my own cpu cycles? Thanks, _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Mon Feb 18 01:36:33 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 18 Feb 2013 01: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 1U7FdU-0004D3-5b; Mon, 18 Feb 2013 01:35:16 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U7FdT-0004Cw-Aw for xen-users@lists.xen.org; Mon, 18 Feb 2013 01:35:15 +0000 Received: from [85.158.143.99:50783] by server-2.bemta-4.messagelabs.com id E7/53-01597-25581215; Mon, 18 Feb 2013 01:35:14 +0000 X-Env-Sender: skupko.sk@gmail.com X-Msg-Ref: server-5.tower-216.messagelabs.com!1361151313!27430088!1 X-Originating-IP: [74.125.83.46] X-SpamReason: No, hits=0.0 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, spamassassin: X-StarScan-Received: X-StarScan-Version: 6.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 18643 invoked from network); 18 Feb 2013 01:35:13 -0000 Received: from mail-ee0-f46.google.com (HELO mail-ee0-f46.google.com) (74.125.83.46) by server-5.tower-216.messagelabs.com with RC4-SHA encrypted SMTP; 18 Feb 2013 01:35:13 -0000 Received: by mail-ee0-f46.google.com with SMTP id e49so2594771eek.19 for ; Sun, 17 Feb 2013 17:35:12 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=P9YbwBVHLor48ctwPAkkoA6BXqf6v6CICqVjdX7DTME=; b=i1DHEfcc3TLwJu4AClERQwGfeDNwOdxAyyh8bhxqWOPeizVg16iDp9plBauYuUugQp H9sOJm9qjGXenwjtpVVlTUhYsp98sbdK0kC8/t/S6d30zx2V14vi3QFftm272PNqKnso KQymDufXoeUDaQC0jxAcnqGWhTcjwWEeT/cICurlUuVlQs7be5wF5C/ERsF/+XSuiYe+ WA6VDlJp1LCvSXQ6nmApkjLe/cJA3aptcApsG/CMuHTpfBT5GUjY0tAf8JusGG6FvfeH ZtheYQuDL9R4CFG6lANC9g94mMyTrF6paPMbIWNKTzO6/aZlTWTz2VzWAe+I3llWI17y s0Gw== X-Received: by 10.14.214.66 with SMTP id b42mr38575322eep.34.1361151312846; Sun, 17 Feb 2013 17:35:12 -0800 (PST) Received: from [192.168.30.208] (chello089173144208.chello.sk. [89.173.144.208]) by mx.google.com with ESMTPS id d47sm37105287eem.9.2013.02.17.17.35.11 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sun, 17 Feb 2013 17:35:12 -0800 (PST) Message-ID: <5121854B.3080106@gmail.com> Date: Mon, 18 Feb 2013 02:35:07 +0100 From: Peter Viskup User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:10.0.12) Gecko/20130116 Icedove/10.0.12 MIME-Version: 1.0 To: Andrew Son References: In-Reply-To: Cc: xen-users@lists.xen.org Subject: Re: [Xen-users] CPU cap and weight X-BeenThere: xen-users@lists.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 02/18/2013 01:34 AM, Andrew Son wrote: > The guest VM suffers from steel time meaning guest vm can not get cpu > cycles. Does this mean other guest vm can obtain cpu cycles or just > waste my own cpu cycles? Hi Andrew, the steal time is here since Linux kernel 2.6.11 [1]. Of course, other guests can obtain cpu cycles from the backing CPU of that vCPU. Read more about Xen credit scheduler (Xen's default) [2]. [1] http://lwn.net/Articles/108605/ [2] http://wiki.xen.org/wiki/Credit_Scheduler -- Peter Viskup _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Mon Feb 18 01:36:33 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 18 Feb 2013 01: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 1U7FdU-0004D3-5b; Mon, 18 Feb 2013 01:35:16 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U7FdT-0004Cw-Aw for xen-users@lists.xen.org; Mon, 18 Feb 2013 01:35:15 +0000 Received: from [85.158.143.99:50783] by server-2.bemta-4.messagelabs.com id E7/53-01597-25581215; Mon, 18 Feb 2013 01:35:14 +0000 X-Env-Sender: skupko.sk@gmail.com X-Msg-Ref: server-5.tower-216.messagelabs.com!1361151313!27430088!1 X-Originating-IP: [74.125.83.46] X-SpamReason: No, hits=0.0 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, spamassassin: X-StarScan-Received: X-StarScan-Version: 6.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 18643 invoked from network); 18 Feb 2013 01:35:13 -0000 Received: from mail-ee0-f46.google.com (HELO mail-ee0-f46.google.com) (74.125.83.46) by server-5.tower-216.messagelabs.com with RC4-SHA encrypted SMTP; 18 Feb 2013 01:35:13 -0000 Received: by mail-ee0-f46.google.com with SMTP id e49so2594771eek.19 for ; Sun, 17 Feb 2013 17:35:12 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=P9YbwBVHLor48ctwPAkkoA6BXqf6v6CICqVjdX7DTME=; b=i1DHEfcc3TLwJu4AClERQwGfeDNwOdxAyyh8bhxqWOPeizVg16iDp9plBauYuUugQp H9sOJm9qjGXenwjtpVVlTUhYsp98sbdK0kC8/t/S6d30zx2V14vi3QFftm272PNqKnso KQymDufXoeUDaQC0jxAcnqGWhTcjwWEeT/cICurlUuVlQs7be5wF5C/ERsF/+XSuiYe+ WA6VDlJp1LCvSXQ6nmApkjLe/cJA3aptcApsG/CMuHTpfBT5GUjY0tAf8JusGG6FvfeH ZtheYQuDL9R4CFG6lANC9g94mMyTrF6paPMbIWNKTzO6/aZlTWTz2VzWAe+I3llWI17y s0Gw== X-Received: by 10.14.214.66 with SMTP id b42mr38575322eep.34.1361151312846; Sun, 17 Feb 2013 17:35:12 -0800 (PST) Received: from [192.168.30.208] (chello089173144208.chello.sk. [89.173.144.208]) by mx.google.com with ESMTPS id d47sm37105287eem.9.2013.02.17.17.35.11 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sun, 17 Feb 2013 17:35:12 -0800 (PST) Message-ID: <5121854B.3080106@gmail.com> Date: Mon, 18 Feb 2013 02:35:07 +0100 From: Peter Viskup User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:10.0.12) Gecko/20130116 Icedove/10.0.12 MIME-Version: 1.0 To: Andrew Son References: In-Reply-To: Cc: xen-users@lists.xen.org Subject: Re: [Xen-users] CPU cap and weight X-BeenThere: xen-users@lists.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 02/18/2013 01:34 AM, Andrew Son wrote: > The guest VM suffers from steel time meaning guest vm can not get cpu > cycles. Does this mean other guest vm can obtain cpu cycles or just > waste my own cpu cycles? Hi Andrew, the steal time is here since Linux kernel 2.6.11 [1]. Of course, other guests can obtain cpu cycles from the backing CPU of that vCPU. Read more about Xen credit scheduler (Xen's default) [2]. [1] http://lwn.net/Articles/108605/ [2] http://wiki.xen.org/wiki/Credit_Scheduler -- Peter Viskup _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Mon Feb 18 01:51:06 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 18 Feb 2013 01:51: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 1U7Frj-0004Xg-Qt; Mon, 18 Feb 2013 01:49:59 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U7Fri-0004Xa-K5 for xen-users@lists.xen.org; Mon, 18 Feb 2013 01:49:58 +0000 Received: from [193.109.254.147:19733] by server-3.bemta-14.messagelabs.com id 9B/C2-22141-5C881215; Mon, 18 Feb 2013 01:49:57 +0000 X-Env-Sender: mailing.son@gmail.com X-Msg-Ref: server-10.tower-27.messagelabs.com!1361152196!3575929!1 X-Originating-IP: [209.85.215.180] 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.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 26700 invoked from network); 18 Feb 2013 01:49:57 -0000 Received: from mail-ea0-f180.google.com (HELO mail-ea0-f180.google.com) (209.85.215.180) by server-10.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 18 Feb 2013 01:49:57 -0000 Received: by mail-ea0-f180.google.com with SMTP id c1so2057818eaa.25 for ; Sun, 17 Feb 2013 17:49:56 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=ouUFsbPDnwYLOGIdPkD2sdJdCo98Mzh9v3k+m4UhLMs=; b=vZtRTrDgGxI+m12+aCdpC7YJPRWDwYmnehh8ikT598i2h2GIcqUh9yChHFOOC6dOL0 cKfg1beNfbbCwvlSQugNvl7qj57bjO/Tdg1BRX4SWhvzfZYViy1q8wQbQGOwufoiqYnS Pa4YbqQmcXF2dlAGiAiQ7I8ggN/T5YXdKStr5Q/cMRJCqL3WWxx52wWfRpuB+URcraqw R5LEmiCJ02m/8qsCk11IQvp1CPMzfvEXpCJzDtInE5pqdcayKrtdTZaHCtYnlu8RLsIL GZyEI4wvrnUhIQs52K20DcS5+StUSwgOxx1pAnZZCIG9tKzpn29ZEZ1QbNO8ltldylsO MTwQ== MIME-Version: 1.0 X-Received: by 10.14.1.130 with SMTP id 2mr38686021eed.15.1361152196751; Sun, 17 Feb 2013 17:49:56 -0800 (PST) Received: by 10.14.69.4 with HTTP; Sun, 17 Feb 2013 17:49:56 -0800 (PST) In-Reply-To: <5121854B.3080106@gmail.com> References: <5121854B.3080106@gmail.com> Date: Mon, 18 Feb 2013 10:49:56 +0900 Message-ID: From: Andrew Son To: Peter Viskup Cc: xen-users@lists.xen.org Subject: Re: [Xen-users] CPU cap and weight X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: 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, Thank for references. My detailed question is: If the host machine is not busy, guest VM can get VCPU (timeslices) in every 30ms. If the CAP value is 50, does guest VM get 15ms? or guest VM can get 30ms, but it can not use 15ms? 2013/2/18 Peter Viskup : > On 02/18/2013 01:34 AM, Andrew Son wrote: >> >> The guest VM suffers from steel time meaning guest vm can not get cpu >> cycles. Does this mean other guest vm can obtain cpu cycles or just >> waste my own cpu cycles? > > Hi Andrew, > the steal time is here since Linux kernel 2.6.11 [1]. > Of course, other guests can obtain cpu cycles from the backing CPU of that > vCPU. Read more about Xen credit scheduler (Xen's default) [2]. > > [1] http://lwn.net/Articles/108605/ > [2] http://wiki.xen.org/wiki/Credit_Scheduler > > -- > Peter Viskup _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Mon Feb 18 01:51:06 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 18 Feb 2013 01:51: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 1U7Frj-0004Xg-Qt; Mon, 18 Feb 2013 01:49:59 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U7Fri-0004Xa-K5 for xen-users@lists.xen.org; Mon, 18 Feb 2013 01:49:58 +0000 Received: from [193.109.254.147:19733] by server-3.bemta-14.messagelabs.com id 9B/C2-22141-5C881215; Mon, 18 Feb 2013 01:49:57 +0000 X-Env-Sender: mailing.son@gmail.com X-Msg-Ref: server-10.tower-27.messagelabs.com!1361152196!3575929!1 X-Originating-IP: [209.85.215.180] 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.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 26700 invoked from network); 18 Feb 2013 01:49:57 -0000 Received: from mail-ea0-f180.google.com (HELO mail-ea0-f180.google.com) (209.85.215.180) by server-10.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 18 Feb 2013 01:49:57 -0000 Received: by mail-ea0-f180.google.com with SMTP id c1so2057818eaa.25 for ; Sun, 17 Feb 2013 17:49:56 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=ouUFsbPDnwYLOGIdPkD2sdJdCo98Mzh9v3k+m4UhLMs=; b=vZtRTrDgGxI+m12+aCdpC7YJPRWDwYmnehh8ikT598i2h2GIcqUh9yChHFOOC6dOL0 cKfg1beNfbbCwvlSQugNvl7qj57bjO/Tdg1BRX4SWhvzfZYViy1q8wQbQGOwufoiqYnS Pa4YbqQmcXF2dlAGiAiQ7I8ggN/T5YXdKStr5Q/cMRJCqL3WWxx52wWfRpuB+URcraqw R5LEmiCJ02m/8qsCk11IQvp1CPMzfvEXpCJzDtInE5pqdcayKrtdTZaHCtYnlu8RLsIL GZyEI4wvrnUhIQs52K20DcS5+StUSwgOxx1pAnZZCIG9tKzpn29ZEZ1QbNO8ltldylsO MTwQ== MIME-Version: 1.0 X-Received: by 10.14.1.130 with SMTP id 2mr38686021eed.15.1361152196751; Sun, 17 Feb 2013 17:49:56 -0800 (PST) Received: by 10.14.69.4 with HTTP; Sun, 17 Feb 2013 17:49:56 -0800 (PST) In-Reply-To: <5121854B.3080106@gmail.com> References: <5121854B.3080106@gmail.com> Date: Mon, 18 Feb 2013 10:49:56 +0900 Message-ID: From: Andrew Son To: Peter Viskup Cc: xen-users@lists.xen.org Subject: Re: [Xen-users] CPU cap and weight X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: 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, Thank for references. My detailed question is: If the host machine is not busy, guest VM can get VCPU (timeslices) in every 30ms. If the CAP value is 50, does guest VM get 15ms? or guest VM can get 30ms, but it can not use 15ms? 2013/2/18 Peter Viskup : > On 02/18/2013 01:34 AM, Andrew Son wrote: >> >> The guest VM suffers from steel time meaning guest vm can not get cpu >> cycles. Does this mean other guest vm can obtain cpu cycles or just >> waste my own cpu cycles? > > Hi Andrew, > the steal time is here since Linux kernel 2.6.11 [1]. > Of course, other guests can obtain cpu cycles from the backing CPU of that > vCPU. Read more about Xen credit scheduler (Xen's default) [2]. > > [1] http://lwn.net/Articles/108605/ > [2] http://wiki.xen.org/wiki/Credit_Scheduler > > -- > Peter Viskup _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Mon Feb 18 02:03:44 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 18 Feb 2013 02:03: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 1U7G40-0005El-C6; Mon, 18 Feb 2013 02:02:40 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U7G3z-0005Ef-2I for xen-users@lists.xen.org; Mon, 18 Feb 2013 02:02:39 +0000 Received: from [85.158.139.83:39542] by server-15.bemta-5.messagelabs.com id 82/10-18914-EBB81215; Mon, 18 Feb 2013 02:02:38 +0000 X-Env-Sender: skupko.sk@gmail.com X-Msg-Ref: server-3.tower-182.messagelabs.com!1361152957!27681765!1 X-Originating-IP: [74.125.83.44] X-SpamReason: No, hits=0.0 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, spamassassin: X-StarScan-Received: X-StarScan-Version: 6.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 24560 invoked from network); 18 Feb 2013 02:02:37 -0000 Received: from mail-ee0-f44.google.com (HELO mail-ee0-f44.google.com) (74.125.83.44) by server-3.tower-182.messagelabs.com with RC4-SHA encrypted SMTP; 18 Feb 2013 02:02:37 -0000 Received: by mail-ee0-f44.google.com with SMTP id l10so2668318eei.31 for ; Sun, 17 Feb 2013 18:02:37 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=ak9U9HAzmytMfTiLtcwRnJevRN5IZDnKnCFNJ3JLThw=; b=KQ3kmWUdfHbD40iAW2aHXmeRBRtrq2gWTIlQ4Z4CB0zQnl3ovyF7JvLrmlmEJgR9aG sfcFx2AZDF72Z/y2igm342uYzgHLn6PHiZo9JjnapGEnVFm0gPKuOR3bqQQ/OsyckEX0 OY5ZjTl3HsRPiAUeHx8h20m6Y7XGoTFpxwTwGu/sBeVwW6aTgDg/QYb5A4+M7RbPgUym Ya5vYjNjKB03r3xDe2ROfy6dRqgCK3yAmAmuemWZv1LubN1BkKBuva0/G+AOixX7OeMw OZxXpR4A9CDCtI4gM6HvsUN+Fmfdb/r1ucnnXEaTti9WpjI3+uDI8foyPblGip8dRIFa l02g== X-Received: by 10.14.210.8 with SMTP id t8mr38819989eeo.35.1361152957465; Sun, 17 Feb 2013 18:02:37 -0800 (PST) Received: from [192.168.30.208] (chello089173144208.chello.sk. [89.173.144.208]) by mx.google.com with ESMTPS id u44sm36048946eel.7.2013.02.17.18.02.36 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sun, 17 Feb 2013 18:02:36 -0800 (PST) Message-ID: <51218BBC.6050207@gmail.com> Date: Mon, 18 Feb 2013 03:02:36 +0100 From: Peter Viskup User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:10.0.12) Gecko/20130116 Icedove/10.0.12 MIME-Version: 1.0 To: Andrew Son References: <5121854B.3080106@gmail.com> In-Reply-To: Cc: xen-users@lists.xen.org Subject: Re: [Xen-users] CPU cap and weight X-BeenThere: xen-users@lists.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 02/18/2013 02:49 AM, Andrew Son wrote: > Hi Peter, > > Thank for references. > My detailed question is: > > If the host machine is not busy, guest VM can get VCPU (timeslices) in > every 30ms. > If the CAP value is 50, does guest VM get 15ms? > or guest VM can get 30ms, but it can not use 15ms? > It's not about the shortage of timeslices. It's about how many timeslices the guest will be given. Read the wiki more carefully and especially the Algorithm section and you will find it's more about credits - if you use the default scheduler. The host machine/hypervisor will assign the CPU time (timeslice) every time the guest has credits or other guest is not asking for that CPU. -- Peter Viskup _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Mon Feb 18 02:03:44 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 18 Feb 2013 02:03: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 1U7G40-0005El-C6; Mon, 18 Feb 2013 02:02:40 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U7G3z-0005Ef-2I for xen-users@lists.xen.org; Mon, 18 Feb 2013 02:02:39 +0000 Received: from [85.158.139.83:39542] by server-15.bemta-5.messagelabs.com id 82/10-18914-EBB81215; Mon, 18 Feb 2013 02:02:38 +0000 X-Env-Sender: skupko.sk@gmail.com X-Msg-Ref: server-3.tower-182.messagelabs.com!1361152957!27681765!1 X-Originating-IP: [74.125.83.44] X-SpamReason: No, hits=0.0 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, spamassassin: X-StarScan-Received: X-StarScan-Version: 6.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 24560 invoked from network); 18 Feb 2013 02:02:37 -0000 Received: from mail-ee0-f44.google.com (HELO mail-ee0-f44.google.com) (74.125.83.44) by server-3.tower-182.messagelabs.com with RC4-SHA encrypted SMTP; 18 Feb 2013 02:02:37 -0000 Received: by mail-ee0-f44.google.com with SMTP id l10so2668318eei.31 for ; Sun, 17 Feb 2013 18:02:37 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=ak9U9HAzmytMfTiLtcwRnJevRN5IZDnKnCFNJ3JLThw=; b=KQ3kmWUdfHbD40iAW2aHXmeRBRtrq2gWTIlQ4Z4CB0zQnl3ovyF7JvLrmlmEJgR9aG sfcFx2AZDF72Z/y2igm342uYzgHLn6PHiZo9JjnapGEnVFm0gPKuOR3bqQQ/OsyckEX0 OY5ZjTl3HsRPiAUeHx8h20m6Y7XGoTFpxwTwGu/sBeVwW6aTgDg/QYb5A4+M7RbPgUym Ya5vYjNjKB03r3xDe2ROfy6dRqgCK3yAmAmuemWZv1LubN1BkKBuva0/G+AOixX7OeMw OZxXpR4A9CDCtI4gM6HvsUN+Fmfdb/r1ucnnXEaTti9WpjI3+uDI8foyPblGip8dRIFa l02g== X-Received: by 10.14.210.8 with SMTP id t8mr38819989eeo.35.1361152957465; Sun, 17 Feb 2013 18:02:37 -0800 (PST) Received: from [192.168.30.208] (chello089173144208.chello.sk. [89.173.144.208]) by mx.google.com with ESMTPS id u44sm36048946eel.7.2013.02.17.18.02.36 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sun, 17 Feb 2013 18:02:36 -0800 (PST) Message-ID: <51218BBC.6050207@gmail.com> Date: Mon, 18 Feb 2013 03:02:36 +0100 From: Peter Viskup User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:10.0.12) Gecko/20130116 Icedove/10.0.12 MIME-Version: 1.0 To: Andrew Son References: <5121854B.3080106@gmail.com> In-Reply-To: Cc: xen-users@lists.xen.org Subject: Re: [Xen-users] CPU cap and weight X-BeenThere: xen-users@lists.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 02/18/2013 02:49 AM, Andrew Son wrote: > Hi Peter, > > Thank for references. > My detailed question is: > > If the host machine is not busy, guest VM can get VCPU (timeslices) in > every 30ms. > If the CAP value is 50, does guest VM get 15ms? > or guest VM can get 30ms, but it can not use 15ms? > It's not about the shortage of timeslices. It's about how many timeslices the guest will be given. Read the wiki more carefully and especially the Algorithm section and you will find it's more about credits - if you use the default scheduler. The host machine/hypervisor will assign the CPU time (timeslice) every time the guest has credits or other guest is not asking for that CPU. -- Peter Viskup _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Mon Feb 18 07:34:47 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 18 Feb 2013 07:34: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 1U7LE5-0007t9-An; Mon, 18 Feb 2013 07:33:25 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U7LE4-0007t4-Ho for xen-users@lists.xen.org; Mon, 18 Feb 2013 07:33:24 +0000 Received: from [85.158.139.211:64378] by server-6.bemta-5.messagelabs.com id 13/93-01489-349D1215; Mon, 18 Feb 2013 07:33:23 +0000 X-Env-Sender: roger.pau@citrix.com X-Msg-Ref: server-15.tower-206.messagelabs.com!1361172802!18047323!1 X-Originating-IP: [46.33.159.39] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNDYuMzMuMTU5LjM5ID0+IDIzMTk1\n X-StarScan-Received: X-StarScan-Version: 6.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 3162 invoked from network); 18 Feb 2013 07:33:23 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (46.33.159.39) by server-15.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 18 Feb 2013 07:33:23 -0000 X-IronPort-AV: E=Sophos;i="4.84,684,1355097600"; d="scan'208";a="1556526" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 18 Feb 2013 07:33:23 +0000 Received: from [192.168.1.30] (10.30.249.242) by LONPMAILMX01.citrite.net (10.30.203.162) with Microsoft SMTP Server id 8.3.297.1; Mon, 18 Feb 2013 07:33:22 +0000 Message-ID: <5121D961.8030006@citrix.com> Date: Mon, 18 Feb 2013 08:33:53 +0100 From: =?UTF-8?B?Um9nZXIgUGF1IE1vbm7DqQ==?= User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130107 Thunderbird/17.0.2 MIME-Version: 1.0 To: FONG Julio References: <20130216203950.129730@gmx.com> In-Reply-To: <20130216203950.129730@gmx.com> Cc: "xen-users@lists.xen.org" Subject: Re: [Xen-users] add vif-route support to libxl/xl X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: 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/02/13 21:39, FONG Julio wrote: > Hi roger, > > I saw your previous post here > http://www.gossamer-threads.com/lists/xen/devel/270781 > I would like to try the network route mode, may be you can show the way > to apply your patch, this one I'm little bit confuse. > > Yours, Julio Hello Julio, I've pushed a branch to my git repo that contains the vif route changes, so it can be fetched more easily. You just need to clone the branch in my repo: $ git clone -b vif_route_v2 git://xenbits.xen.org/people/royger/xen.git After that just compile and install Xen from source. You can find information about how to build Xen from source for your specific distro at http://wiki.xen.org/wiki/Compiling_Xen_From_Source#Building_from_Source Thanks for testing, Roger. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Mon Feb 18 07:34:47 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 18 Feb 2013 07:34: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 1U7LE5-0007t9-An; Mon, 18 Feb 2013 07:33:25 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U7LE4-0007t4-Ho for xen-users@lists.xen.org; Mon, 18 Feb 2013 07:33:24 +0000 Received: from [85.158.139.211:64378] by server-6.bemta-5.messagelabs.com id 13/93-01489-349D1215; Mon, 18 Feb 2013 07:33:23 +0000 X-Env-Sender: roger.pau@citrix.com X-Msg-Ref: server-15.tower-206.messagelabs.com!1361172802!18047323!1 X-Originating-IP: [46.33.159.39] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNDYuMzMuMTU5LjM5ID0+IDIzMTk1\n X-StarScan-Received: X-StarScan-Version: 6.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 3162 invoked from network); 18 Feb 2013 07:33:23 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (46.33.159.39) by server-15.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 18 Feb 2013 07:33:23 -0000 X-IronPort-AV: E=Sophos;i="4.84,684,1355097600"; d="scan'208";a="1556526" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 18 Feb 2013 07:33:23 +0000 Received: from [192.168.1.30] (10.30.249.242) by LONPMAILMX01.citrite.net (10.30.203.162) with Microsoft SMTP Server id 8.3.297.1; Mon, 18 Feb 2013 07:33:22 +0000 Message-ID: <5121D961.8030006@citrix.com> Date: Mon, 18 Feb 2013 08:33:53 +0100 From: =?UTF-8?B?Um9nZXIgUGF1IE1vbm7DqQ==?= User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130107 Thunderbird/17.0.2 MIME-Version: 1.0 To: FONG Julio References: <20130216203950.129730@gmx.com> In-Reply-To: <20130216203950.129730@gmx.com> Cc: "xen-users@lists.xen.org" Subject: Re: [Xen-users] add vif-route support to libxl/xl X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: 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/02/13 21:39, FONG Julio wrote: > Hi roger, > > I saw your previous post here > http://www.gossamer-threads.com/lists/xen/devel/270781 > I would like to try the network route mode, may be you can show the way > to apply your patch, this one I'm little bit confuse. > > Yours, Julio Hello Julio, I've pushed a branch to my git repo that contains the vif route changes, so it can be fetched more easily. You just need to clone the branch in my repo: $ git clone -b vif_route_v2 git://xenbits.xen.org/people/royger/xen.git After that just compile and install Xen from source. You can find information about how to build Xen from source for your specific distro at http://wiki.xen.org/wiki/Compiling_Xen_From_Source#Building_from_Source Thanks for testing, Roger. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Mon Feb 18 09:30:38 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 18 Feb 2013 09:30: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 1U7N2K-0001dy-7E; Mon, 18 Feb 2013 09:29:24 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U7N2H-0001dt-U4 for xen-users@lists.xen.org; Mon, 18 Feb 2013 09:29:22 +0000 Received: from [85.158.139.83:56735] by server-15.bemta-5.messagelabs.com id 45/05-18914-174F1215; Mon, 18 Feb 2013 09:29:21 +0000 X-Env-Sender: wei.liu2@citrix.com X-Msg-Ref: server-7.tower-182.messagelabs.com!1361179741!23768519!1 X-Originating-IP: [66.165.176.63] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjYuMTY1LjE3Ni42MyA9PiAzMDMwNjE=\n X-StarScan-Received: X-StarScan-Version: 6.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 21482 invoked from network); 18 Feb 2013 09:29:02 -0000 Received: from smtp02.citrix.com (HELO SMTP02.CITRIX.COM) (66.165.176.63) by server-7.tower-182.messagelabs.com with RC4-SHA encrypted SMTP; 18 Feb 2013 09:29:02 -0000 X-IronPort-AV: E=Sophos;i="4.84,686,1355097600"; d="scan'208";a="7569897" Received: from accessns.citrite.net (HELO FTLPEX01CL03.citrite.net) ([10.9.154.239]) by FTLPIPO02.CITRIX.COM with ESMTP/TLS/AES128-SHA; 18 Feb 2013 09:29:00 +0000 Received: from ukmail1.uk.xensource.com (10.80.16.128) by smtprelay.citrix.com (10.13.107.80) with Microsoft SMTP Server id 14.2.318.1; Mon, 18 Feb 2013 04:29:00 -0500 Received: from zion.uk.xensource.com ([10.80.2.73]) by ukmail1.uk.xensource.com with esmtp (Exim 4.69) (envelope-from ) id 1U7N1w-0005pv-5J; Mon, 18 Feb 2013 09:29:00 +0000 Date: Mon, 18 Feb 2013 09:29:00 +0000 From: Wei Liu To: Tom Message-ID: <20130218092900.GA30133@zion.uk.xensource.com> References: MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) Cc: "xen-users@lists.xen.org" Subject: Re: [Xen-users] Issue with starting X with Intel gfx card (Ubuntu 12.10) X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: 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, Feb 17, 2013 at 01:05:45PM +0000, Tom wrote: > Hi, > > I'm trying to get my X working with Xen on my Ubuntu 12.10 oob installation, but keeps on hanging on boot; > > lspci | grep VGA > 00:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller (rev 09) > > I've read about the Intel graphic cards which should be fully supported in 3.x.x kernel versions. Kernel options in this generic kernel are enabled: > > CONFIG_INTEL_IOMMU=y > CONFIG_DMAR_TABLE=y > > > Any help would be greatly appreciated. > What makes you think it is related to your graphic card? Wei. > _______________________________________________ > 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 Feb 18 09:30:38 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 18 Feb 2013 09:30: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 1U7N2K-0001dy-7E; Mon, 18 Feb 2013 09:29:24 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U7N2H-0001dt-U4 for xen-users@lists.xen.org; Mon, 18 Feb 2013 09:29:22 +0000 Received: from [85.158.139.83:56735] by server-15.bemta-5.messagelabs.com id 45/05-18914-174F1215; Mon, 18 Feb 2013 09:29:21 +0000 X-Env-Sender: wei.liu2@citrix.com X-Msg-Ref: server-7.tower-182.messagelabs.com!1361179741!23768519!1 X-Originating-IP: [66.165.176.63] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjYuMTY1LjE3Ni42MyA9PiAzMDMwNjE=\n X-StarScan-Received: X-StarScan-Version: 6.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 21482 invoked from network); 18 Feb 2013 09:29:02 -0000 Received: from smtp02.citrix.com (HELO SMTP02.CITRIX.COM) (66.165.176.63) by server-7.tower-182.messagelabs.com with RC4-SHA encrypted SMTP; 18 Feb 2013 09:29:02 -0000 X-IronPort-AV: E=Sophos;i="4.84,686,1355097600"; d="scan'208";a="7569897" Received: from accessns.citrite.net (HELO FTLPEX01CL03.citrite.net) ([10.9.154.239]) by FTLPIPO02.CITRIX.COM with ESMTP/TLS/AES128-SHA; 18 Feb 2013 09:29:00 +0000 Received: from ukmail1.uk.xensource.com (10.80.16.128) by smtprelay.citrix.com (10.13.107.80) with Microsoft SMTP Server id 14.2.318.1; Mon, 18 Feb 2013 04:29:00 -0500 Received: from zion.uk.xensource.com ([10.80.2.73]) by ukmail1.uk.xensource.com with esmtp (Exim 4.69) (envelope-from ) id 1U7N1w-0005pv-5J; Mon, 18 Feb 2013 09:29:00 +0000 Date: Mon, 18 Feb 2013 09:29:00 +0000 From: Wei Liu To: Tom Message-ID: <20130218092900.GA30133@zion.uk.xensource.com> References: MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) Cc: "xen-users@lists.xen.org" Subject: Re: [Xen-users] Issue with starting X with Intel gfx card (Ubuntu 12.10) X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: 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, Feb 17, 2013 at 01:05:45PM +0000, Tom wrote: > Hi, > > I'm trying to get my X working with Xen on my Ubuntu 12.10 oob installation, but keeps on hanging on boot; > > lspci | grep VGA > 00:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller (rev 09) > > I've read about the Intel graphic cards which should be fully supported in 3.x.x kernel versions. Kernel options in this generic kernel are enabled: > > CONFIG_INTEL_IOMMU=y > CONFIG_DMAR_TABLE=y > > > Any help would be greatly appreciated. > What makes you think it is related to your graphic card? Wei. > _______________________________________________ > 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 Feb 18 10:25:13 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 18 Feb 2013 10:25: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 1U7NtJ-0003FC-T5; Mon, 18 Feb 2013 10:24:09 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U7NtI-0003F5-Jc for xen-users@lists.xen.org; Mon, 18 Feb 2013 10:24:08 +0000 Received: from [85.158.143.99:42409] by server-2.bemta-4.messagelabs.com id 9B/AE-01597-74102215; Mon, 18 Feb 2013 10:24:07 +0000 X-Env-Sender: netmatters@gmail.com X-Msg-Ref: server-6.tower-216.messagelabs.com!1361183028!20943001!1 X-Originating-IP: [209.85.128.180] 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.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 6860 invoked from network); 18 Feb 2013 10:23:49 -0000 Received: from mail-ve0-f180.google.com (HELO mail-ve0-f180.google.com) (209.85.128.180) by server-6.tower-216.messagelabs.com with RC4-SHA encrypted SMTP; 18 Feb 2013 10:23:49 -0000 Received: by mail-ve0-f180.google.com with SMTP id jx10so4755388veb.11 for ; Mon, 18 Feb 2013 02:23:45 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:content-type; bh=TeE0bXHLPcicGtrLxwVSx5inp0lB1i97BtG9SEWWfkk=; b=JJoinkbmN8+3ohScCVZLQe86Gm5yvBQ4DaU6mK7NV73n5NGSxZ75ZtVGhlECsR1P26 tTDdebGoey/FFRgCX43etv7IRyX4GqmS7/idK1c3libsAGolCFOJBTPEHH02nhHrjSpm ndOJwNT3VzmI0vD9RqgvbJaTEMCtabWrA89PzNlFo0niF3h9YitMTfGDgdrmeAu+qrlY 6C/9lNH3XMHEoOxTDqmJki4v/SK754M1If0hUe9eK3wAv3O1PsjBohhgzt+f90r+6hIB oDo9l04Fw2g+4UyBDFZfj+TXNSXAkiCyj8AH6B1Dti2KVaa1JOOY66d4haQGuAzEFXXS WA+g== MIME-Version: 1.0 X-Received: by 10.52.71.174 with SMTP id w14mr12735180vdu.122.1361183025321; Mon, 18 Feb 2013 02:23:45 -0800 (PST) Received: by 10.58.106.133 with HTTP; Mon, 18 Feb 2013 02:23:45 -0800 (PST) In-Reply-To: References: Date: Mon, 18 Feb 2013 12:23:45 +0200 Message-ID: From: Gavin To: "xen-users@lists.xen.org" Subject: [Xen-users] Fwd: Recent hypervisor update on Debian Wheezy breaks domU 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="===============8199324943687157047==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============8199324943687157047== Content-Type: multipart/alternative; boundary=20cf3071ce7ab2d7bf04d5fd1e61 --20cf3071ce7ab2d7bf04d5fd1e61 Content-Type: text/plain; charset=ISO-8859-1 Hi, Firstly I apologise for the cross-post, however I don't expect to get as quick a response from the Debian/Xen package maintainers as I do from the Xen community, and this issue affects a service that I've got scheduled to go live at midnight this evening. :( A recent update from xen-hypervisor-4.1-amd64 version 4.1.3-7, to version 4.1.3-8 on Debian Wheezy has caused all vm's on this host to not receive their arp replies anymore and as such they cannot reach their gateways and are now isolated from the network. There was a more recent update as well (4.1.4-2) which I have now since applied however this particular issue persists. The arp replies are received by the host and passed all the way up to the bridge (br200) being used by Xen, however they are not seen on the vif (vif2.0) created for the particular vm. If I statically add the arp entry to the vm all starts working, ie: vm is no longer isolated and is now connected to the world, but we all know that this is not an ideal workaround. This was working perfectly before this update. :( 1) Please let me know if I should roll-back this particular xen update, kernel and all, and what those steps may be, or if this is a known issue with a particular workaround that I can apply. 2) Would moving to openvswitch be another possible workaround? My config:- Bonded ethernet connected to trunks on Cisco 3750 stack with connection as follows:- eth0 --> bond0 eth1 --> bond0 --> br200 --> vif2.0 /etc/network/interfaces:- iface bond0 inet manual slaves eth0 eth1 bond_mode 5 bond-miimon 100 bond-downdelay 200 bond-updelay 200 auto br200 iface br200 inet static address 172.31.1.66 gateway 172.31.1.65 netmask 255.255.255.240 bridge_ports bond0 bridge_maxwait 0 bridge_fd 9 bridge_hello 2 bridge_maxage 12 bridge_stp off root@scjhb01:/home/gavin# brctl show bridge name bridge id STP enabled interfaces br200 8000.d4bed9f309a1 no bond0 vif2.0 root@scjhb01:/home/gavin# tcpdump -i bond0 'arp' tcpdump: WARNING: bond0: no IPv4 address assigned tcpdump: verbose output suppressed, use -v or -vv for full protocol decode listening on bond0, link-type EN10MB (Ethernet), capture size 65535 bytes 11:26:00.287489 ARP, Request who-has 172.31.1.49 tell 172.31.1.50, length 28 11:26:00.287524 ARP, Request who-has 172.31.1.49 tell 172.31.1.50, length 46 11:26:00.287669 ARP, Reply 172.31.1.49 is-at 00:09:0f:09:21:0e (oui Unknown), length 46 11:26:01.303484 ARP, Request who-has 172.31.1.49 tell 172.31.1.50, length 28 11:26:01.303518 ARP, Request who-has 172.31.1.49 tell 172.31.1.50, length 46 11:26:01.303674 ARP, Reply 172.31.1.49 is-at 00:09:0f:09:21:0e (oui Unknown), length 46 11:26:02.303484 ARP, Request who-has 172.31.1.49 tell 172.31.1.50, length 28 11:26:02.303518 ARP, Request who-has 172.31.1.49 tell 172.31.1.50, length 46 11:26:02.303579 ARP, Reply 172.31.1.49 is-at 00:09:0f:09:21:0e (oui Unknown), length 46 root@scjhb01:/home/gavin# tcpdump -i br200 'arp' tcpdump: verbose output suppressed, use -v or -vv for full protocol decode listening on br200, link-type EN10MB (Ethernet), capture size 65535 bytes 11:26:15.367489 ARP, Request who-has 172.31.1.49 tell 172.31.1.50, length 28 11:26:15.367514 ARP, Request who-has 172.31.1.49 tell 172.31.1.50, length 46 11:26:15.367580 ARP, Reply 172.31.1.49 is-at 00:09:0f:09:21:0e (oui Unknown), length 46 11:26:16.383476 ARP, Request who-has 172.31.1.49 tell 172.31.1.50, length 28 11:26:16.383511 ARP, Request who-has 172.31.1.49 tell 172.31.1.50, length 46 11:26:16.383592 ARP, Reply 172.31.1.49 is-at 00:09:0f:09:21:0e (oui Unknown), length 46 11:26:17.383486 ARP, Request who-has 172.31.1.49 tell 172.31.1.50, length 28 11:26:17.383520 ARP, Request who-has 172.31.1.49 tell 172.31.1.50, length 46 11:26:17.383616 ARP, Reply 172.31.1.49 is-at 00:09:0f:09:21:0e (oui Unknown), length 46 root@scjhb01:/home/gavin# tcpdump -i vif2.0 'arp' tcpdump: WARNING: vif2.0: no IPv4 address assigned tcpdump: verbose output suppressed, use -v or -vv for full protocol decode listening on vif2.0, link-type EN10MB (Ethernet), capture size 65535 bytes 11:26:31.463481 ARP, Request who-has 172.31.1.49 tell 172.31.1.50, length 28 11:26:31.463521 ARP, Request who-has 172.31.1.49 tell 172.31.1.50, length 46 11:26:32.463480 ARP, Request who-has 172.31.1.49 tell 172.31.1.50, length 28 11:26:32.463521 ARP, Request who-has 172.31.1.49 tell 172.31.1.50, length 46 11:26:33.463477 ARP, Request who-has 172.31.1.49 tell 172.31.1.50, length 28 11:26:33.463515 ARP, Request who-has 172.31.1.49 tell 172.31.1.50, length 46 11:26:34.479482 ARP, Request who-has 172.31.1.49 tell 172.31.1.50, length 28 11:26:34.479523 ARP, Request who-has 172.31.1.49 tell 172.31.1.50, length 46 11:26:35.479478 ARP, Request who-has 172.31.1.49 tell 172.31.1.50, length 28 11:26:35.479515 ARP, Request who-has 172.31.1.49 tell 172.31.1.50, length 46 Thanks and Regards. Gavin --20cf3071ce7ab2d7bf04d5fd1e61 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Hi,
Firstly I apologise for the cross-post, however I don't ex= pect to get as quick a response from the Debian/Xen package maintainers as = I do from the Xen community, and this issue affects a service that I've= got scheduled to go live at midnight this evening. :(

A recent update from xen-hypervisor-4.1-amd64 version 4= .1.3-7, to version 4.1.3-8 on Debian Wheezy has caused all vm's on this= host to not receive their arp replies anymore and as such they cannot reac= h their gateways and are now isolated from the network.

There was a more recent update as well (4.1.4-2) which = I have now since applied however this particular issue persists.
=
The arp replies are received by the host and passed all the = way up to the bridge (br200) being used by Xen, however they are not seen o= n the vif (vif2.0) created for the particular vm.

If I statically add the arp entry to the vm all starts = working, ie: vm is no longer isolated and is now connected to the world, bu= t we all know that this is not an ideal workaround.

This was working perfectly before this update. :(
=
1) Please let me know if I should roll-back this particular = xen update, kernel and all, and what those steps may be, or if this is a kn= own issue with a particular workaround that I can apply.

2) Would moving to openvswitch be another possible work= around?=A0

My config:- =A0

Bonded ethernet connected to trunks on Cisco 3750 stack with connection a= s follows:-

eth0 --> bond0
eth1 --> bond0 --> br= 200 --> vif2.0

/etc/network/interfaces:-
<= div>
iface bond0 inet manual
=A0 =A0 =A0 =A0 slaves eth0 eth1
=A0 =A0 =A0 =A0 bond_mode 5 =A0<= /div>
=A0 =A0 =A0 =A0 bond-miimon 100
=A0 =A0 =A0 =A0 bond-do= wndelay 200
=A0 =A0 =A0 =A0 bond-updelay 200

=
auto br200
iface br200 inet static
=A0 =A0 =A0 =A0 address 172.31.1.66
=A0 =A0 =A0 =A0 gateway = 172.31.1.65
=A0 =A0 =A0 =A0 netmask 255.255.255.240
=A0= =A0 =A0 =A0 bridge_ports bond0
=A0 =A0 =A0 =A0 bridge_maxwait 0<= /div>
=A0 =A0 =A0 =A0 bridge_fd 9
=A0 =A0 =A0 =A0 bridge_hello 2
=A0 =A0 =A0 =A0 bridge_maxage 12
=A0 =A0 =A0 =A0 bridge_stp off

root@scjhb= 01:/home/gavin# brctl show
bridge name bridge id ST= P enabled interfaces
br200 8000.d4bed9f309a1 no bond0
= vif2.0

root@scjhb01:/home/gavin# tcpdump -i bond0 'arp'= ;
tcpdump: WARNING: bond0: no IPv4 address assigned
tcp= dump: verbose output suppressed, use -v or -vv for full protocol decode
listening on bond0, link-type EN10MB (Ethernet), capture size 65535 by= tes
11:26:00.287489 ARP, Request who-has 172.31.1.49 tell 172.31.= 1.50, length 28
11:26:00.287524 ARP, Request who-has 172.31.1.49 = tell 172.31.1.50, length 46
11:26:00.287669 ARP, Reply 172.31.1.49 is-at 00:09:0f:09:21:0e (oui Un= known), length 46
11:26:01.303484 ARP, Request who-has 172.31.1.4= 9 tell 172.31.1.50, length 28
11:26:01.303518 ARP, Request who-ha= s 172.31.1.49 tell 172.31.1.50, length 46
11:26:01.303674 ARP, Reply 172.31.1.49 is-at 00:09:0f:09:21:0e (oui Un= known), length 46
11:26:02.303484 ARP, Request who-has 172.31.1.4= 9 tell 172.31.1.50, length 28
11:26:02.303518 ARP, Request who-ha= s 172.31.1.49 tell 172.31.1.50, length 46
11:26:02.303579 ARP, Reply 172.31.1.49 is-at 00:09:0f:09:21:0e (oui Un= known), length 46


root@scjhb01:/hom= e/gavin# tcpdump -i br200 'arp'
tcpdump: verbose output s= uppressed, use -v or -vv for full protocol decode
listening on br200, link-type EN10MB (Ethernet), capture size 65535 by= tes
11:26:15.367489 ARP, Request who-has 172.31.1.49 tell 172.31.= 1.50, length 28
11:26:15.367514 ARP, Request who-has 172.31.1.49 = tell 172.31.1.50, length 46
11:26:15.367580 ARP, Reply 172.31.1.49 is-at 00:09:0f:09:21:0e (oui Un= known), length 46
11:26:16.383476 ARP, Request who-has 172.31.1.4= 9 tell 172.31.1.50, length 28
11:26:16.383511 ARP, Request who-ha= s 172.31.1.49 tell 172.31.1.50, length 46
11:26:16.383592 ARP, Reply 172.31.1.49 is-at 00:09:0f:09:21:0e (oui Un= known), length 46
11:26:17.383486 ARP, Request who-has 172.31.1.4= 9 tell 172.31.1.50, length 28
11:26:17.383520 ARP, Request who-ha= s 172.31.1.49 tell 172.31.1.50, length 46
11:26:17.383616 ARP, Reply 172.31.1.49 is-at 00:09:0f:09:21:0e (oui Un= known), length 46


root@scjhb01:/hom= e/gavin# tcpdump -i vif2.0 'arp'
tcpdump: WARNING: vif2.0= : no IPv4 address assigned
tcpdump: verbose output suppressed, use -v or -vv for full protocol de= code
listening on vif2.0, link-type EN10MB (Ethernet), capture si= ze 65535 bytes
11:26:31.463481 ARP, Request who-has 172.31.1.49 t= ell 172.31.1.50, length 28
11:26:31.463521 ARP, Request who-has 172.31.1.49 tell 172.31.1.50, len= gth 46
11:26:32.463480 ARP, Request who-has 172.31.1.49 tell 172.= 31.1.50, length 28
11:26:32.463521 ARP, Request who-has 172.31.1.= 49 tell 172.31.1.50, length 46
11:26:33.463477 ARP, Request who-has 172.31.1.49 tell 172.31.1.50, len= gth 28
11:26:33.463515 ARP, Request who-has 172.31.1.49 tell 172.= 31.1.50, length 46
11:26:34.479482 ARP, Request who-has 172.31.1.= 49 tell 172.31.1.50, length 28
11:26:34.479523 ARP, Request who-has 172.31.1.49 tell 172.31.1.50, len= gth 46
11:26:35.479478 ARP, Request who-has 172.31.1.49 tell 172.= 31.1.50, length 28
11:26:35.479515 ARP, Request who-has 172.31.1.= 49 tell 172.31.1.50, length 46

Thanks and Regards.
Gavin

--20cf3071ce7ab2d7bf04d5fd1e61-- --===============8199324943687157047== 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 --===============8199324943687157047==-- From xen-users-bounces@lists.xen.org Mon Feb 18 10:25:13 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 18 Feb 2013 10:25: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 1U7NtJ-0003FC-T5; Mon, 18 Feb 2013 10:24:09 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U7NtI-0003F5-Jc for xen-users@lists.xen.org; Mon, 18 Feb 2013 10:24:08 +0000 Received: from [85.158.143.99:42409] by server-2.bemta-4.messagelabs.com id 9B/AE-01597-74102215; Mon, 18 Feb 2013 10:24:07 +0000 X-Env-Sender: netmatters@gmail.com X-Msg-Ref: server-6.tower-216.messagelabs.com!1361183028!20943001!1 X-Originating-IP: [209.85.128.180] 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.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 6860 invoked from network); 18 Feb 2013 10:23:49 -0000 Received: from mail-ve0-f180.google.com (HELO mail-ve0-f180.google.com) (209.85.128.180) by server-6.tower-216.messagelabs.com with RC4-SHA encrypted SMTP; 18 Feb 2013 10:23:49 -0000 Received: by mail-ve0-f180.google.com with SMTP id jx10so4755388veb.11 for ; Mon, 18 Feb 2013 02:23:45 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:content-type; bh=TeE0bXHLPcicGtrLxwVSx5inp0lB1i97BtG9SEWWfkk=; b=JJoinkbmN8+3ohScCVZLQe86Gm5yvBQ4DaU6mK7NV73n5NGSxZ75ZtVGhlECsR1P26 tTDdebGoey/FFRgCX43etv7IRyX4GqmS7/idK1c3libsAGolCFOJBTPEHH02nhHrjSpm ndOJwNT3VzmI0vD9RqgvbJaTEMCtabWrA89PzNlFo0niF3h9YitMTfGDgdrmeAu+qrlY 6C/9lNH3XMHEoOxTDqmJki4v/SK754M1If0hUe9eK3wAv3O1PsjBohhgzt+f90r+6hIB oDo9l04Fw2g+4UyBDFZfj+TXNSXAkiCyj8AH6B1Dti2KVaa1JOOY66d4haQGuAzEFXXS WA+g== MIME-Version: 1.0 X-Received: by 10.52.71.174 with SMTP id w14mr12735180vdu.122.1361183025321; Mon, 18 Feb 2013 02:23:45 -0800 (PST) Received: by 10.58.106.133 with HTTP; Mon, 18 Feb 2013 02:23:45 -0800 (PST) In-Reply-To: References: Date: Mon, 18 Feb 2013 12:23:45 +0200 Message-ID: From: Gavin To: "xen-users@lists.xen.org" Subject: [Xen-users] Fwd: Recent hypervisor update on Debian Wheezy breaks domU 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="===============8199324943687157047==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============8199324943687157047== Content-Type: multipart/alternative; boundary=20cf3071ce7ab2d7bf04d5fd1e61 --20cf3071ce7ab2d7bf04d5fd1e61 Content-Type: text/plain; charset=ISO-8859-1 Hi, Firstly I apologise for the cross-post, however I don't expect to get as quick a response from the Debian/Xen package maintainers as I do from the Xen community, and this issue affects a service that I've got scheduled to go live at midnight this evening. :( A recent update from xen-hypervisor-4.1-amd64 version 4.1.3-7, to version 4.1.3-8 on Debian Wheezy has caused all vm's on this host to not receive their arp replies anymore and as such they cannot reach their gateways and are now isolated from the network. There was a more recent update as well (4.1.4-2) which I have now since applied however this particular issue persists. The arp replies are received by the host and passed all the way up to the bridge (br200) being used by Xen, however they are not seen on the vif (vif2.0) created for the particular vm. If I statically add the arp entry to the vm all starts working, ie: vm is no longer isolated and is now connected to the world, but we all know that this is not an ideal workaround. This was working perfectly before this update. :( 1) Please let me know if I should roll-back this particular xen update, kernel and all, and what those steps may be, or if this is a known issue with a particular workaround that I can apply. 2) Would moving to openvswitch be another possible workaround? My config:- Bonded ethernet connected to trunks on Cisco 3750 stack with connection as follows:- eth0 --> bond0 eth1 --> bond0 --> br200 --> vif2.0 /etc/network/interfaces:- iface bond0 inet manual slaves eth0 eth1 bond_mode 5 bond-miimon 100 bond-downdelay 200 bond-updelay 200 auto br200 iface br200 inet static address 172.31.1.66 gateway 172.31.1.65 netmask 255.255.255.240 bridge_ports bond0 bridge_maxwait 0 bridge_fd 9 bridge_hello 2 bridge_maxage 12 bridge_stp off root@scjhb01:/home/gavin# brctl show bridge name bridge id STP enabled interfaces br200 8000.d4bed9f309a1 no bond0 vif2.0 root@scjhb01:/home/gavin# tcpdump -i bond0 'arp' tcpdump: WARNING: bond0: no IPv4 address assigned tcpdump: verbose output suppressed, use -v or -vv for full protocol decode listening on bond0, link-type EN10MB (Ethernet), capture size 65535 bytes 11:26:00.287489 ARP, Request who-has 172.31.1.49 tell 172.31.1.50, length 28 11:26:00.287524 ARP, Request who-has 172.31.1.49 tell 172.31.1.50, length 46 11:26:00.287669 ARP, Reply 172.31.1.49 is-at 00:09:0f:09:21:0e (oui Unknown), length 46 11:26:01.303484 ARP, Request who-has 172.31.1.49 tell 172.31.1.50, length 28 11:26:01.303518 ARP, Request who-has 172.31.1.49 tell 172.31.1.50, length 46 11:26:01.303674 ARP, Reply 172.31.1.49 is-at 00:09:0f:09:21:0e (oui Unknown), length 46 11:26:02.303484 ARP, Request who-has 172.31.1.49 tell 172.31.1.50, length 28 11:26:02.303518 ARP, Request who-has 172.31.1.49 tell 172.31.1.50, length 46 11:26:02.303579 ARP, Reply 172.31.1.49 is-at 00:09:0f:09:21:0e (oui Unknown), length 46 root@scjhb01:/home/gavin# tcpdump -i br200 'arp' tcpdump: verbose output suppressed, use -v or -vv for full protocol decode listening on br200, link-type EN10MB (Ethernet), capture size 65535 bytes 11:26:15.367489 ARP, Request who-has 172.31.1.49 tell 172.31.1.50, length 28 11:26:15.367514 ARP, Request who-has 172.31.1.49 tell 172.31.1.50, length 46 11:26:15.367580 ARP, Reply 172.31.1.49 is-at 00:09:0f:09:21:0e (oui Unknown), length 46 11:26:16.383476 ARP, Request who-has 172.31.1.49 tell 172.31.1.50, length 28 11:26:16.383511 ARP, Request who-has 172.31.1.49 tell 172.31.1.50, length 46 11:26:16.383592 ARP, Reply 172.31.1.49 is-at 00:09:0f:09:21:0e (oui Unknown), length 46 11:26:17.383486 ARP, Request who-has 172.31.1.49 tell 172.31.1.50, length 28 11:26:17.383520 ARP, Request who-has 172.31.1.49 tell 172.31.1.50, length 46 11:26:17.383616 ARP, Reply 172.31.1.49 is-at 00:09:0f:09:21:0e (oui Unknown), length 46 root@scjhb01:/home/gavin# tcpdump -i vif2.0 'arp' tcpdump: WARNING: vif2.0: no IPv4 address assigned tcpdump: verbose output suppressed, use -v or -vv for full protocol decode listening on vif2.0, link-type EN10MB (Ethernet), capture size 65535 bytes 11:26:31.463481 ARP, Request who-has 172.31.1.49 tell 172.31.1.50, length 28 11:26:31.463521 ARP, Request who-has 172.31.1.49 tell 172.31.1.50, length 46 11:26:32.463480 ARP, Request who-has 172.31.1.49 tell 172.31.1.50, length 28 11:26:32.463521 ARP, Request who-has 172.31.1.49 tell 172.31.1.50, length 46 11:26:33.463477 ARP, Request who-has 172.31.1.49 tell 172.31.1.50, length 28 11:26:33.463515 ARP, Request who-has 172.31.1.49 tell 172.31.1.50, length 46 11:26:34.479482 ARP, Request who-has 172.31.1.49 tell 172.31.1.50, length 28 11:26:34.479523 ARP, Request who-has 172.31.1.49 tell 172.31.1.50, length 46 11:26:35.479478 ARP, Request who-has 172.31.1.49 tell 172.31.1.50, length 28 11:26:35.479515 ARP, Request who-has 172.31.1.49 tell 172.31.1.50, length 46 Thanks and Regards. Gavin --20cf3071ce7ab2d7bf04d5fd1e61 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Hi,
Firstly I apologise for the cross-post, however I don't ex= pect to get as quick a response from the Debian/Xen package maintainers as = I do from the Xen community, and this issue affects a service that I've= got scheduled to go live at midnight this evening. :(

A recent update from xen-hypervisor-4.1-amd64 version 4= .1.3-7, to version 4.1.3-8 on Debian Wheezy has caused all vm's on this= host to not receive their arp replies anymore and as such they cannot reac= h their gateways and are now isolated from the network.

There was a more recent update as well (4.1.4-2) which = I have now since applied however this particular issue persists.
=
The arp replies are received by the host and passed all the = way up to the bridge (br200) being used by Xen, however they are not seen o= n the vif (vif2.0) created for the particular vm.

If I statically add the arp entry to the vm all starts = working, ie: vm is no longer isolated and is now connected to the world, bu= t we all know that this is not an ideal workaround.

This was working perfectly before this update. :(
=
1) Please let me know if I should roll-back this particular = xen update, kernel and all, and what those steps may be, or if this is a kn= own issue with a particular workaround that I can apply.

2) Would moving to openvswitch be another possible work= around?=A0

My config:- =A0

Bonded ethernet connected to trunks on Cisco 3750 stack with connection a= s follows:-

eth0 --> bond0
eth1 --> bond0 --> br= 200 --> vif2.0

/etc/network/interfaces:-
<= div>
iface bond0 inet manual
=A0 =A0 =A0 =A0 slaves eth0 eth1
=A0 =A0 =A0 =A0 bond_mode 5 =A0<= /div>
=A0 =A0 =A0 =A0 bond-miimon 100
=A0 =A0 =A0 =A0 bond-do= wndelay 200
=A0 =A0 =A0 =A0 bond-updelay 200

=
auto br200
iface br200 inet static
=A0 =A0 =A0 =A0 address 172.31.1.66
=A0 =A0 =A0 =A0 gateway = 172.31.1.65
=A0 =A0 =A0 =A0 netmask 255.255.255.240
=A0= =A0 =A0 =A0 bridge_ports bond0
=A0 =A0 =A0 =A0 bridge_maxwait 0<= /div>
=A0 =A0 =A0 =A0 bridge_fd 9
=A0 =A0 =A0 =A0 bridge_hello 2
=A0 =A0 =A0 =A0 bridge_maxage 12
=A0 =A0 =A0 =A0 bridge_stp off

root@scjhb= 01:/home/gavin# brctl show
bridge name bridge id ST= P enabled interfaces
br200 8000.d4bed9f309a1 no bond0
= vif2.0

root@scjhb01:/home/gavin# tcpdump -i bond0 'arp'= ;
tcpdump: WARNING: bond0: no IPv4 address assigned
tcp= dump: verbose output suppressed, use -v or -vv for full protocol decode
listening on bond0, link-type EN10MB (Ethernet), capture size 65535 by= tes
11:26:00.287489 ARP, Request who-has 172.31.1.49 tell 172.31.= 1.50, length 28
11:26:00.287524 ARP, Request who-has 172.31.1.49 = tell 172.31.1.50, length 46
11:26:00.287669 ARP, Reply 172.31.1.49 is-at 00:09:0f:09:21:0e (oui Un= known), length 46
11:26:01.303484 ARP, Request who-has 172.31.1.4= 9 tell 172.31.1.50, length 28
11:26:01.303518 ARP, Request who-ha= s 172.31.1.49 tell 172.31.1.50, length 46
11:26:01.303674 ARP, Reply 172.31.1.49 is-at 00:09:0f:09:21:0e (oui Un= known), length 46
11:26:02.303484 ARP, Request who-has 172.31.1.4= 9 tell 172.31.1.50, length 28
11:26:02.303518 ARP, Request who-ha= s 172.31.1.49 tell 172.31.1.50, length 46
11:26:02.303579 ARP, Reply 172.31.1.49 is-at 00:09:0f:09:21:0e (oui Un= known), length 46


root@scjhb01:/hom= e/gavin# tcpdump -i br200 'arp'
tcpdump: verbose output s= uppressed, use -v or -vv for full protocol decode
listening on br200, link-type EN10MB (Ethernet), capture size 65535 by= tes
11:26:15.367489 ARP, Request who-has 172.31.1.49 tell 172.31.= 1.50, length 28
11:26:15.367514 ARP, Request who-has 172.31.1.49 = tell 172.31.1.50, length 46
11:26:15.367580 ARP, Reply 172.31.1.49 is-at 00:09:0f:09:21:0e (oui Un= known), length 46
11:26:16.383476 ARP, Request who-has 172.31.1.4= 9 tell 172.31.1.50, length 28
11:26:16.383511 ARP, Request who-ha= s 172.31.1.49 tell 172.31.1.50, length 46
11:26:16.383592 ARP, Reply 172.31.1.49 is-at 00:09:0f:09:21:0e (oui Un= known), length 46
11:26:17.383486 ARP, Request who-has 172.31.1.4= 9 tell 172.31.1.50, length 28
11:26:17.383520 ARP, Request who-ha= s 172.31.1.49 tell 172.31.1.50, length 46
11:26:17.383616 ARP, Reply 172.31.1.49 is-at 00:09:0f:09:21:0e (oui Un= known), length 46


root@scjhb01:/hom= e/gavin# tcpdump -i vif2.0 'arp'
tcpdump: WARNING: vif2.0= : no IPv4 address assigned
tcpdump: verbose output suppressed, use -v or -vv for full protocol de= code
listening on vif2.0, link-type EN10MB (Ethernet), capture si= ze 65535 bytes
11:26:31.463481 ARP, Request who-has 172.31.1.49 t= ell 172.31.1.50, length 28
11:26:31.463521 ARP, Request who-has 172.31.1.49 tell 172.31.1.50, len= gth 46
11:26:32.463480 ARP, Request who-has 172.31.1.49 tell 172.= 31.1.50, length 28
11:26:32.463521 ARP, Request who-has 172.31.1.= 49 tell 172.31.1.50, length 46
11:26:33.463477 ARP, Request who-has 172.31.1.49 tell 172.31.1.50, len= gth 28
11:26:33.463515 ARP, Request who-has 172.31.1.49 tell 172.= 31.1.50, length 46
11:26:34.479482 ARP, Request who-has 172.31.1.= 49 tell 172.31.1.50, length 28
11:26:34.479523 ARP, Request who-has 172.31.1.49 tell 172.31.1.50, len= gth 46
11:26:35.479478 ARP, Request who-has 172.31.1.49 tell 172.= 31.1.50, length 28
11:26:35.479515 ARP, Request who-has 172.31.1.= 49 tell 172.31.1.50, length 46

Thanks and Regards.
Gavin

--20cf3071ce7ab2d7bf04d5fd1e61-- --===============8199324943687157047== 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 --===============8199324943687157047==-- From xen-users-bounces@lists.xen.org Mon Feb 18 10:25:40 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 18 Feb 2013 10:25: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 1U7Nu2-0003If-IW; Mon, 18 Feb 2013 10:24:54 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U7Nu1-0003IQ-9o for xen-users@lists.xen.org; Mon, 18 Feb 2013 10:24:53 +0000 Received: from [85.158.143.35:22993] by server-3.bemta-4.messagelabs.com id C5/9A-08920-47102215; Mon, 18 Feb 2013 10:24:52 +0000 X-Env-Sender: Ian.Campbell@citrix.com X-Msg-Ref: server-16.tower-21.messagelabs.com!1361182969!13127955!1 X-Originating-IP: [46.33.159.39] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNDYuMzMuMTU5LjM5ID0+IDIzMTUw\n X-StarScan-Received: X-StarScan-Version: 6.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 18981 invoked from network); 18 Feb 2013 10:22:50 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (46.33.159.39) by server-16.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 18 Feb 2013 10:22:50 -0000 X-IronPort-AV: E=Sophos;i="4.84,686,1355097600"; d="scan'208";a="1563360" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 18 Feb 2013 10:22:50 +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.297.1; Mon, 18 Feb 2013 10:22:49 +0000 Message-ID: <1361182968.31407.125.camel@zakaz.uk.xensource.com> From: Ian Campbell To: Sylvain Chevalier Date: Mon, 18 Feb 2013 10:22:48 +0000 In-Reply-To: References: Organization: Citrix Systems, Inc. X-Mailer: Evolution 3.4.4-1 MIME-Version: 1.0 Cc: "xen-users@lists.xen.org" Subject: Re: [Xen-users] Can't boot dom0 after upgrading to non-modified 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-Type: 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, 2013-02-16 at 11:30 +0000, Sylvain Chevalier wrote: > > This grub setting fails (kernel is gentoo-sources): > root (hd0,1) > kernel /boot/xen.gz dom0_mem=4096M dom0_max_vcpus=1 dom0_vcpus_pin > module /boot/kernel-3.6.11-gentoo root=/dev/sda6 Does this kernel boot natively? Are you sure you have all the necessary drivers etc? Given the lack of logs it is rather hard to give any more specific advice. Ian. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Mon Feb 18 10:25:40 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 18 Feb 2013 10:25: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 1U7Nu2-0003If-IW; Mon, 18 Feb 2013 10:24:54 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U7Nu1-0003IQ-9o for xen-users@lists.xen.org; Mon, 18 Feb 2013 10:24:53 +0000 Received: from [85.158.143.35:22993] by server-3.bemta-4.messagelabs.com id C5/9A-08920-47102215; Mon, 18 Feb 2013 10:24:52 +0000 X-Env-Sender: Ian.Campbell@citrix.com X-Msg-Ref: server-16.tower-21.messagelabs.com!1361182969!13127955!1 X-Originating-IP: [46.33.159.39] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNDYuMzMuMTU5LjM5ID0+IDIzMTUw\n X-StarScan-Received: X-StarScan-Version: 6.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 18981 invoked from network); 18 Feb 2013 10:22:50 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (46.33.159.39) by server-16.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 18 Feb 2013 10:22:50 -0000 X-IronPort-AV: E=Sophos;i="4.84,686,1355097600"; d="scan'208";a="1563360" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 18 Feb 2013 10:22:50 +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.297.1; Mon, 18 Feb 2013 10:22:49 +0000 Message-ID: <1361182968.31407.125.camel@zakaz.uk.xensource.com> From: Ian Campbell To: Sylvain Chevalier Date: Mon, 18 Feb 2013 10:22:48 +0000 In-Reply-To: References: Organization: Citrix Systems, Inc. X-Mailer: Evolution 3.4.4-1 MIME-Version: 1.0 Cc: "xen-users@lists.xen.org" Subject: Re: [Xen-users] Can't boot dom0 after upgrading to non-modified 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-Type: 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, 2013-02-16 at 11:30 +0000, Sylvain Chevalier wrote: > > This grub setting fails (kernel is gentoo-sources): > root (hd0,1) > kernel /boot/xen.gz dom0_mem=4096M dom0_max_vcpus=1 dom0_vcpus_pin > module /boot/kernel-3.6.11-gentoo root=/dev/sda6 Does this kernel boot natively? Are you sure you have all the necessary drivers etc? Given the lack of logs it is rather hard to give any more specific advice. Ian. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Mon Feb 18 10:30:30 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 18 Feb 2013 10:30: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 1U7Nyd-0003gh-H2; Mon, 18 Feb 2013 10:29:39 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U7Nyb-0003gY-Ru for xen-users@lists.xen.org; Mon, 18 Feb 2013 10:29:38 +0000 Received: from [193.109.254.147:34793] by server-7.bemta-14.messagelabs.com id C9/33-13581-19202215; Mon, 18 Feb 2013 10:29:37 +0000 X-Env-Sender: Ian.Campbell@citrix.com X-Msg-Ref: server-16.tower-27.messagelabs.com!1361183375!8623173!1 X-Originating-IP: [46.33.159.39] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNDYuMzMuMTU5LjM5ID0+IDIzMTUw\n X-StarScan-Received: X-StarScan-Version: 6.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 15297 invoked from network); 18 Feb 2013 10:29:36 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (46.33.159.39) by server-16.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 18 Feb 2013 10:29:36 -0000 X-IronPort-AV: E=Sophos;i="4.84,686,1355097600"; d="scan'208";a="1563592" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 18 Feb 2013 10:29:36 +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.297.1; Mon, 18 Feb 2013 10:29:35 +0000 Message-ID: <1361183374.31407.129.camel@zakaz.uk.xensource.com> From: Ian Campbell To: "mlg-hessigheim@gmx.de" Date: Mon, 18 Feb 2013 10:29:34 +0000 In-Reply-To: <511F6E82.8040107@gmx.de> References: <511F6E82.8040107@gmx.de> Organization: Citrix Systems, Inc. X-Mailer: Evolution 3.4.4-1 MIME-Version: 1.0 Cc: "xen-users@lists.xen.org" Subject: Re: [Xen-users] Boot problem with Debian Squeeza and 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 On Sat, 2013-02-16 at 11:33 +0000, Martin Lang wrote: > Hi all, > > I just upgraded my Debian/Etch with Xen3.3 machine to Debian/Squeeze > Xen4.0 and now have problems with starting the Dom0 kernel. I always get > the error message: Kernel panic not syncing: the kernel parameter noapic > is incompatible with xen. Is this the literal message? I've grepped the kernel and hypervisor source and cannot find it anywhere. Please can you collect the actual logs from the system. http://wiki.xen.org/wiki/Reporting_Bugs_against_Xen#Host_console_logs What sort of processor does this system have? > My grub.cfg is: > > menuentry 'Debian GNU/Linux, with Linux 2.6.32-5-xen-686 and XEN > 4.0-i386' --cl$ > insmod part_msdos > insmod ext2 > set root='(hd0,msdos1)' > search --no-floppy --fs-uuid --set > 743d959f-5054-441f-b68d-32d9970bb8ab > echo 'Loading Linux 2.6.32-5-xen-686 ...' > multiboot /boot/xen-4.0-i386.gz noreboot placeholder > module /boot/vmlinuz-2.6.32-5-xen-686 placeholder > root=UUID=743d959f-5$ > echo 'Loading initial ramdisk ...' > module /boot/initrd.img-2.6.32-5-xen-686 > > > I already tried the boot parameters: noapic nolapic acpi=off in the line > mulitboot .... and module /boot/vmlinuz line. The message is complaining about the presence of "noapic" not its absence, so I hope you also tried without. Ian. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Mon Feb 18 10:30:30 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 18 Feb 2013 10:30: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 1U7Nyd-0003gh-H2; Mon, 18 Feb 2013 10:29:39 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U7Nyb-0003gY-Ru for xen-users@lists.xen.org; Mon, 18 Feb 2013 10:29:38 +0000 Received: from [193.109.254.147:34793] by server-7.bemta-14.messagelabs.com id C9/33-13581-19202215; Mon, 18 Feb 2013 10:29:37 +0000 X-Env-Sender: Ian.Campbell@citrix.com X-Msg-Ref: server-16.tower-27.messagelabs.com!1361183375!8623173!1 X-Originating-IP: [46.33.159.39] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNDYuMzMuMTU5LjM5ID0+IDIzMTUw\n X-StarScan-Received: X-StarScan-Version: 6.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 15297 invoked from network); 18 Feb 2013 10:29:36 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (46.33.159.39) by server-16.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 18 Feb 2013 10:29:36 -0000 X-IronPort-AV: E=Sophos;i="4.84,686,1355097600"; d="scan'208";a="1563592" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 18 Feb 2013 10:29:36 +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.297.1; Mon, 18 Feb 2013 10:29:35 +0000 Message-ID: <1361183374.31407.129.camel@zakaz.uk.xensource.com> From: Ian Campbell To: "mlg-hessigheim@gmx.de" Date: Mon, 18 Feb 2013 10:29:34 +0000 In-Reply-To: <511F6E82.8040107@gmx.de> References: <511F6E82.8040107@gmx.de> Organization: Citrix Systems, Inc. X-Mailer: Evolution 3.4.4-1 MIME-Version: 1.0 Cc: "xen-users@lists.xen.org" Subject: Re: [Xen-users] Boot problem with Debian Squeeza and 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 On Sat, 2013-02-16 at 11:33 +0000, Martin Lang wrote: > Hi all, > > I just upgraded my Debian/Etch with Xen3.3 machine to Debian/Squeeze > Xen4.0 and now have problems with starting the Dom0 kernel. I always get > the error message: Kernel panic not syncing: the kernel parameter noapic > is incompatible with xen. Is this the literal message? I've grepped the kernel and hypervisor source and cannot find it anywhere. Please can you collect the actual logs from the system. http://wiki.xen.org/wiki/Reporting_Bugs_against_Xen#Host_console_logs What sort of processor does this system have? > My grub.cfg is: > > menuentry 'Debian GNU/Linux, with Linux 2.6.32-5-xen-686 and XEN > 4.0-i386' --cl$ > insmod part_msdos > insmod ext2 > set root='(hd0,msdos1)' > search --no-floppy --fs-uuid --set > 743d959f-5054-441f-b68d-32d9970bb8ab > echo 'Loading Linux 2.6.32-5-xen-686 ...' > multiboot /boot/xen-4.0-i386.gz noreboot placeholder > module /boot/vmlinuz-2.6.32-5-xen-686 placeholder > root=UUID=743d959f-5$ > echo 'Loading initial ramdisk ...' > module /boot/initrd.img-2.6.32-5-xen-686 > > > I already tried the boot parameters: noapic nolapic acpi=off in the line > mulitboot .... and module /boot/vmlinuz line. The message is complaining about the presence of "noapic" not its absence, so I hope you also tried without. Ian. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Mon Feb 18 10:39:10 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 18 Feb 2013 10:39: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 1U7O79-0004XD-Ji; Mon, 18 Feb 2013 10:38:27 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U7O78-0004Wp-Ex; Mon, 18 Feb 2013 10:38:26 +0000 Received: from [85.158.138.51:59053] by server-16.bemta-3.messagelabs.com id 6D/12-02727-1A402215; Mon, 18 Feb 2013 10:38:25 +0000 X-Env-Sender: herydians@gmail.com X-Msg-Ref: server-12.tower-174.messagelabs.com!1361183904!20049769!1 X-Originating-IP: [74.125.82.47] 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.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 27104 invoked from network); 18 Feb 2013 10:38:24 -0000 Received: from mail-wg0-f47.google.com (HELO mail-wg0-f47.google.com) (74.125.82.47) by server-12.tower-174.messagelabs.com with RC4-SHA encrypted SMTP; 18 Feb 2013 10:38:24 -0000 Received: by mail-wg0-f47.google.com with SMTP id dr13so4537187wgb.14 for ; Mon, 18 Feb 2013 02:38:24 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=SpMEUvIIm0NqY5rga6t9hyR7wMN9Qrup5mJFFdaDWj4=; b=CMUX5cuCH0wBU+zRg6iiBFwo4HbvN+dFpb+d3Ta2e7k6vWUFUICpKYPPKK4KYmxtBu PAIQJhKhDk/0JDQ88ROV2DbOAse6ZVu9uyhq3PNEdShlmVsxQwoCc9DC888u/aMtRm9H 1ANs8Bsc3p21fPKEMHdZyTz0hYSYh8p/XMMeDTXTLcTER+ER2eiLze4ZIAOL3G3iFDPL 1pVT2fQ9f0fHVJxtzCVAiTwbCxNJal9mq9hYFz+Hxmp8F7jmJVw8Vo3c/18fLIQaI1QU UHA8z1r9B1x3XnMED9WvyP2W8XW53pbRgimejBDdaL3zOpPzG/XocizGi0MAsYxPmr2R 5zLQ== MIME-Version: 1.0 X-Received: by 10.194.236.233 with SMTP id ux9mr17814549wjc.36.1361183904021; Mon, 18 Feb 2013 02:38:24 -0800 (PST) Received: by 10.216.107.132 with HTTP; Mon, 18 Feb 2013 02:38:23 -0800 (PST) In-Reply-To: References: Date: Mon, 18 Feb 2013 11:38:23 +0100 Message-ID: From: Hery Dian Septama To: agya naila Cc: xen-users@lists.xen.org, xen-devel@lists.xen.org Subject: Re: [Xen-users] [Xen-devel] Remus disk replication failed X-BeenThere: xen-users@lists.xen.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="===============4187313111895256091==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============4187313111895256091== Content-Type: multipart/alternative; boundary=089e01493ee412bb3c04d5fd5341 --089e01493ee412bb3c04d5fd5341 Content-Type: text/plain; charset=UTF-8 Hello, Anyone have a clue? I have tried but still failed :( On Sat, Feb 16, 2013 at 6:56 PM, agya naila wrote: > Dear all, > > I am configure my machine to run the remus disk replication. I am using > xen 4.2.3 installed from sources and Ubuntu 12.04 64 bit both for Dom0 and > DomU. > I have install the blktap and its work properly with configuration string > phy or tap2 like this : > disk = ['phy:/dev/vggroup/DomU,xvda,w'] > or > disk = ['tap2:tapdisk:aio:/dev/vggroup/DomU,xvda,w'] > > and remus command > > remus --no-net myvm mybackuphost > > > However when I change the string as suggested on remus pages to enable the > disk replication its still failed : > > name = "DomU" > memory = 1024 > disk = ['tap2:remus:10.10.10.3:8002|aio:/dev/vggroup/DomU,xvda,w'] > vif = ['ip=192.168.1.55,bridge=xenbr0'] > bootloader = "pygrub" > > with error messages : > > name1@machine1:~$ sudo xm create -c /etc/xen/DomU.cfg > Using config file "/etc/xen/DomU.cfg". > Error: ('create', '-aremus:10.10.10.3:8002|aio:/dev/vggroup/DomU') failed > (512 ) > > and on the log file : > > > name1@machine1:~$ sudo sudo tail /var/log/xen/xend.log > mounted_vbd_uuid = dom0.create_vbd(vbd, disk); > File > "/usr/local/lib/python2.7/dist-packages/xen/xend/XendDomainInfo.py", line > 3987, in create_vbd > devid = dev_control.createDevice(config) > File > "/usr/local/lib/python2.7/dist-packages/xen/xend/server/BlktapController.py", > line 174, in createDevice > device = TapdiskController.create(params, file) > File > "/usr/local/lib/python2.7/dist-packages/xen/xend/server/BlktapController.py", > line 286, in create > return TapdiskController.exc('create', '-a%s:%s' % (dtype, image)) > File > "/usr/local/lib/python2.7/dist-packages/xen/xend/server/BlktapController.py", > line 233, in exc > (args, rc, out, err)) > TapdiskException: ('create', '-aremus:10.10.10.3:8002|aio:/dev/vggroup/DomU') > failed (512 ) > > Any hints and help would very appreciated. > > Regards, > > Agya > > > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xen.org > http://lists.xen.org/xen-devel > > --089e01493ee412bb3c04d5fd5341 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Hello, Anyone have a clue? I have tried but still failed :(

On Sat, Feb 16, 2013 at 6:56 PM, agya naila <agya.na= ila@gmail.com> wrote:
Dear all,

I am configure = my machine to run the remus disk replication. I am using xen 4.2.3 installe= d from sources and Ubuntu 12.04 64 bit both for Dom0 and DomU.=C2=A0
I have install the blktap and its work properly with configuratio= n string phy or tap2 like this :
disk =3D ['phy:/dev/vggroup/= DomU,xvda,w']
o= r
disk =3D ['tap2:tapdi= sk:aio:/dev/vggroup/DomU,xvda,w']

and remus command=C2=A0

remus --no-net myvm mybackuphost

However when I change the string as suggested on remus pag= es to enable the disk replication its still failed :

name =3D "DomU"
memory =3D 1024
disk =3D ['tap2:remus:10.10.10.3= :8002|aio:/dev/vggroup/DomU,xvda,w'] =C2=A0
vif =3D ['ip=3D192.168.1.55,bridge=3Dxenbr0= ']
bootloader =3D "pygrub"= ;

with error messages :

name1@machine1:~$ sudo xm create -c /etc/xen/Do= mU.cfg
Using config = file "/etc/xen/DomU.cfg".
Error: ('create', '-= aremus:10.10.10.3:8002|aio:/dev/vggroup/DomU') failed (512 =C2=A0)

and on the log file :

=

name1@machine1:~$ sudo sudo tail /var/log/= xen/xend.log
=C2=A0 =C2=A0 mounted_vbd_uuid = =3D dom0.create_vbd(vbd, disk);
=C2=A0 File "/usr/local/lib/python2.7/dist-packages/xen/xe= nd/XendDomainInfo.py", line 3987, in create_vbd
=C2=A0 =C2=A0 devid =3D dev_cont= rol.createDevice(config)
=C2=A0 File "/usr/local/lib/python2.7/dist-packages/xen/xend/serv= er/BlktapController.py", line 174, in createDevice
=C2=A0 =C2=A0 device =3D Tapdisk= Controller.create(params, file)
=C2=A0 File "/usr/local/lib/python2.7/dist-packages/xen/xe= nd/server/BlktapController.py", line 286, in create
=C2=A0 =C2=A0 return TapdiskCont= roller.exc('create', '-a%s:%s' % (dtype, image))
=C2=A0 File "/usr/local/l= ib/python2.7/dist-packages/xen/xend/server/BlktapController.py", line = 233, in exc
=C2=A0 =C2=A0 (args, rc, out, er= r))
TapdiskException= : ('create', '-aremus:10.10.10.3:8002|aio:/dev/vggroup/DomU'= ;) failed (512 =C2=A0)

Any hints and help would very appreciated.

Regards,

Agya


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


--089e01493ee412bb3c04d5fd5341-- --===============4187313111895256091== 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 --===============4187313111895256091==-- From xen-users-bounces@lists.xen.org Mon Feb 18 10:39:10 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 18 Feb 2013 10:39: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 1U7O79-0004XD-Ji; Mon, 18 Feb 2013 10:38:27 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U7O78-0004Wp-Ex; Mon, 18 Feb 2013 10:38:26 +0000 Received: from [85.158.138.51:59053] by server-16.bemta-3.messagelabs.com id 6D/12-02727-1A402215; Mon, 18 Feb 2013 10:38:25 +0000 X-Env-Sender: herydians@gmail.com X-Msg-Ref: server-12.tower-174.messagelabs.com!1361183904!20049769!1 X-Originating-IP: [74.125.82.47] 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.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 27104 invoked from network); 18 Feb 2013 10:38:24 -0000 Received: from mail-wg0-f47.google.com (HELO mail-wg0-f47.google.com) (74.125.82.47) by server-12.tower-174.messagelabs.com with RC4-SHA encrypted SMTP; 18 Feb 2013 10:38:24 -0000 Received: by mail-wg0-f47.google.com with SMTP id dr13so4537187wgb.14 for ; Mon, 18 Feb 2013 02:38:24 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=SpMEUvIIm0NqY5rga6t9hyR7wMN9Qrup5mJFFdaDWj4=; b=CMUX5cuCH0wBU+zRg6iiBFwo4HbvN+dFpb+d3Ta2e7k6vWUFUICpKYPPKK4KYmxtBu PAIQJhKhDk/0JDQ88ROV2DbOAse6ZVu9uyhq3PNEdShlmVsxQwoCc9DC888u/aMtRm9H 1ANs8Bsc3p21fPKEMHdZyTz0hYSYh8p/XMMeDTXTLcTER+ER2eiLze4ZIAOL3G3iFDPL 1pVT2fQ9f0fHVJxtzCVAiTwbCxNJal9mq9hYFz+Hxmp8F7jmJVw8Vo3c/18fLIQaI1QU UHA8z1r9B1x3XnMED9WvyP2W8XW53pbRgimejBDdaL3zOpPzG/XocizGi0MAsYxPmr2R 5zLQ== MIME-Version: 1.0 X-Received: by 10.194.236.233 with SMTP id ux9mr17814549wjc.36.1361183904021; Mon, 18 Feb 2013 02:38:24 -0800 (PST) Received: by 10.216.107.132 with HTTP; Mon, 18 Feb 2013 02:38:23 -0800 (PST) In-Reply-To: References: Date: Mon, 18 Feb 2013 11:38:23 +0100 Message-ID: From: Hery Dian Septama To: agya naila Cc: xen-users@lists.xen.org, xen-devel@lists.xen.org Subject: Re: [Xen-users] [Xen-devel] Remus disk replication failed X-BeenThere: xen-users@lists.xen.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="===============4187313111895256091==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============4187313111895256091== Content-Type: multipart/alternative; boundary=089e01493ee412bb3c04d5fd5341 --089e01493ee412bb3c04d5fd5341 Content-Type: text/plain; charset=UTF-8 Hello, Anyone have a clue? I have tried but still failed :( On Sat, Feb 16, 2013 at 6:56 PM, agya naila wrote: > Dear all, > > I am configure my machine to run the remus disk replication. I am using > xen 4.2.3 installed from sources and Ubuntu 12.04 64 bit both for Dom0 and > DomU. > I have install the blktap and its work properly with configuration string > phy or tap2 like this : > disk = ['phy:/dev/vggroup/DomU,xvda,w'] > or > disk = ['tap2:tapdisk:aio:/dev/vggroup/DomU,xvda,w'] > > and remus command > > remus --no-net myvm mybackuphost > > > However when I change the string as suggested on remus pages to enable the > disk replication its still failed : > > name = "DomU" > memory = 1024 > disk = ['tap2:remus:10.10.10.3:8002|aio:/dev/vggroup/DomU,xvda,w'] > vif = ['ip=192.168.1.55,bridge=xenbr0'] > bootloader = "pygrub" > > with error messages : > > name1@machine1:~$ sudo xm create -c /etc/xen/DomU.cfg > Using config file "/etc/xen/DomU.cfg". > Error: ('create', '-aremus:10.10.10.3:8002|aio:/dev/vggroup/DomU') failed > (512 ) > > and on the log file : > > > name1@machine1:~$ sudo sudo tail /var/log/xen/xend.log > mounted_vbd_uuid = dom0.create_vbd(vbd, disk); > File > "/usr/local/lib/python2.7/dist-packages/xen/xend/XendDomainInfo.py", line > 3987, in create_vbd > devid = dev_control.createDevice(config) > File > "/usr/local/lib/python2.7/dist-packages/xen/xend/server/BlktapController.py", > line 174, in createDevice > device = TapdiskController.create(params, file) > File > "/usr/local/lib/python2.7/dist-packages/xen/xend/server/BlktapController.py", > line 286, in create > return TapdiskController.exc('create', '-a%s:%s' % (dtype, image)) > File > "/usr/local/lib/python2.7/dist-packages/xen/xend/server/BlktapController.py", > line 233, in exc > (args, rc, out, err)) > TapdiskException: ('create', '-aremus:10.10.10.3:8002|aio:/dev/vggroup/DomU') > failed (512 ) > > Any hints and help would very appreciated. > > Regards, > > Agya > > > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xen.org > http://lists.xen.org/xen-devel > > --089e01493ee412bb3c04d5fd5341 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Hello, Anyone have a clue? I have tried but still failed :(

On Sat, Feb 16, 2013 at 6:56 PM, agya naila <agya.na= ila@gmail.com> wrote:
Dear all,

I am configure = my machine to run the remus disk replication. I am using xen 4.2.3 installe= d from sources and Ubuntu 12.04 64 bit both for Dom0 and DomU.=C2=A0
I have install the blktap and its work properly with configuratio= n string phy or tap2 like this :
disk =3D ['phy:/dev/vggroup/= DomU,xvda,w']
o= r
disk =3D ['tap2:tapdi= sk:aio:/dev/vggroup/DomU,xvda,w']

and remus command=C2=A0

remus --no-net myvm mybackuphost

However when I change the string as suggested on remus pag= es to enable the disk replication its still failed :

name =3D "DomU"
memory =3D 1024
disk =3D ['tap2:remus:10.10.10.3= :8002|aio:/dev/vggroup/DomU,xvda,w'] =C2=A0
vif =3D ['ip=3D192.168.1.55,bridge=3Dxenbr0= ']
bootloader =3D "pygrub"= ;

with error messages :

name1@machine1:~$ sudo xm create -c /etc/xen/Do= mU.cfg
Using config = file "/etc/xen/DomU.cfg".
Error: ('create', '-= aremus:10.10.10.3:8002|aio:/dev/vggroup/DomU') failed (512 =C2=A0)

and on the log file :

=

name1@machine1:~$ sudo sudo tail /var/log/= xen/xend.log
=C2=A0 =C2=A0 mounted_vbd_uuid = =3D dom0.create_vbd(vbd, disk);
=C2=A0 File "/usr/local/lib/python2.7/dist-packages/xen/xe= nd/XendDomainInfo.py", line 3987, in create_vbd
=C2=A0 =C2=A0 devid =3D dev_cont= rol.createDevice(config)
=C2=A0 File "/usr/local/lib/python2.7/dist-packages/xen/xend/serv= er/BlktapController.py", line 174, in createDevice
=C2=A0 =C2=A0 device =3D Tapdisk= Controller.create(params, file)
=C2=A0 File "/usr/local/lib/python2.7/dist-packages/xen/xe= nd/server/BlktapController.py", line 286, in create
=C2=A0 =C2=A0 return TapdiskCont= roller.exc('create', '-a%s:%s' % (dtype, image))
=C2=A0 File "/usr/local/l= ib/python2.7/dist-packages/xen/xend/server/BlktapController.py", line = 233, in exc
=C2=A0 =C2=A0 (args, rc, out, er= r))
TapdiskException= : ('create', '-aremus:10.10.10.3:8002|aio:/dev/vggroup/DomU'= ;) failed (512 =C2=A0)

Any hints and help would very appreciated.

Regards,

Agya


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


--089e01493ee412bb3c04d5fd5341-- --===============4187313111895256091== 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 --===============4187313111895256091==-- From xen-users-bounces@lists.xen.org Mon Feb 18 10:46:28 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 18 Feb 2013 10:46: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 1U7OED-0005Gz-Ej; Mon, 18 Feb 2013 10:45:45 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U7OEB-0005Gm-QL for xen-users@lists.xen.org; Mon, 18 Feb 2013 10:45:43 +0000 Received: from [85.158.138.51:61964] by server-9.bemta-3.messagelabs.com id 68/36-09484-25602215; Mon, 18 Feb 2013 10:45:38 +0000 X-Env-Sender: pigeon@pigeond.net X-Msg-Ref: server-9.tower-174.messagelabs.com!1361184335!28048495!1 X-Originating-IP: [202.65.223.218] X-SpamReason: No, hits=1.9 required=7.0 tests=BODY_RANDOM_LONG, RCVD_NUMERIC_HELO X-StarScan-Received: X-StarScan-Version: 6.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 16970 invoked from network); 18 Feb 2013 10:45:37 -0000 Received: from static-ip-218-223-65-202.rev.dyxnet.com (HELO pan.pigeond.net) (202.65.223.218) by server-9.tower-174.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 18 Feb 2013 10:45:37 -0000 Received: from 114.40.77.101 (114-40-77-101.dynamic.hinet.net [114.40.77.101]) by pan.pigeond.net (Postfix) with ESMTPA id 505AA137CA; Mon, 18 Feb 2013 18:45:29 +0800 (HKT) Date: Mon, 18 Feb 2013 21:45:25 +1100 From: Howell Tam To: Matthias Message-ID: <20130218214525.5afe4b19@114.40.77.101> In-Reply-To: References: <20130210235853.4ebb70b8@pigeond.net> <20130212084728.64c49ea1@pigeond.net> <6035A0D088A63A46850C3988ED045A4B35667928@BITCOM1.int.sbss.com.au> <20130212210541.3b71b98f@pigeond.net> <6035A0D088A63A46850C3988ED045A4B3566C353@BITCOM1.int.sbss.com.au> <20130213220535.06c0de16@pigeond.net> Organization: pigeond.net X-Mailer: Claws Mail 3.8.1 (GTK+ 2.24.10; x86_64-pc-linux-gnu) Mime-Version: 1.0 Cc: "xen-users@lists.xen.org" , James Harper Subject: Re: [Xen-users] Dom0 freeze on HVM DomU Windows reboot with 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 Hi Matthias and all, > have you found a solution for this behaviour? Cause I'm currently > seeing a similar result with my installation. Unfortunately not yet. I remember I do not have this problem at the very beginning, with working VGA passthrough. I only have the common problem where after restarting the DomU Win7, the VGA passthrough screen will become blank, but does not cause any freeze. I'm not sure what has been changed and then the freezing started. -- Regards, Howell. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Mon Feb 18 10:46:28 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 18 Feb 2013 10:46: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 1U7OED-0005Gz-Ej; Mon, 18 Feb 2013 10:45:45 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U7OEB-0005Gm-QL for xen-users@lists.xen.org; Mon, 18 Feb 2013 10:45:43 +0000 Received: from [85.158.138.51:61964] by server-9.bemta-3.messagelabs.com id 68/36-09484-25602215; Mon, 18 Feb 2013 10:45:38 +0000 X-Env-Sender: pigeon@pigeond.net X-Msg-Ref: server-9.tower-174.messagelabs.com!1361184335!28048495!1 X-Originating-IP: [202.65.223.218] X-SpamReason: No, hits=1.9 required=7.0 tests=BODY_RANDOM_LONG, RCVD_NUMERIC_HELO X-StarScan-Received: X-StarScan-Version: 6.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 16970 invoked from network); 18 Feb 2013 10:45:37 -0000 Received: from static-ip-218-223-65-202.rev.dyxnet.com (HELO pan.pigeond.net) (202.65.223.218) by server-9.tower-174.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 18 Feb 2013 10:45:37 -0000 Received: from 114.40.77.101 (114-40-77-101.dynamic.hinet.net [114.40.77.101]) by pan.pigeond.net (Postfix) with ESMTPA id 505AA137CA; Mon, 18 Feb 2013 18:45:29 +0800 (HKT) Date: Mon, 18 Feb 2013 21:45:25 +1100 From: Howell Tam To: Matthias Message-ID: <20130218214525.5afe4b19@114.40.77.101> In-Reply-To: References: <20130210235853.4ebb70b8@pigeond.net> <20130212084728.64c49ea1@pigeond.net> <6035A0D088A63A46850C3988ED045A4B35667928@BITCOM1.int.sbss.com.au> <20130212210541.3b71b98f@pigeond.net> <6035A0D088A63A46850C3988ED045A4B3566C353@BITCOM1.int.sbss.com.au> <20130213220535.06c0de16@pigeond.net> Organization: pigeond.net X-Mailer: Claws Mail 3.8.1 (GTK+ 2.24.10; x86_64-pc-linux-gnu) Mime-Version: 1.0 Cc: "xen-users@lists.xen.org" , James Harper Subject: Re: [Xen-users] Dom0 freeze on HVM DomU Windows reboot with 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 Hi Matthias and all, > have you found a solution for this behaviour? Cause I'm currently > seeing a similar result with my installation. Unfortunately not yet. I remember I do not have this problem at the very beginning, with working VGA passthrough. I only have the common problem where after restarting the DomU Win7, the VGA passthrough screen will become blank, but does not cause any freeze. I'm not sure what has been changed and then the freezing started. -- Regards, Howell. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Mon Feb 18 10:54:01 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 18 Feb 2013 10:54: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 1U7OLh-0005w9-3O; Mon, 18 Feb 2013 10:53:29 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U7OLf-0005vn-5o for xen-users@lists.xen.org; Mon, 18 Feb 2013 10:53:27 +0000 Received: from [85.158.143.99:3248] by server-1.bemta-4.messagelabs.com id F4/F1-08839-62802215; Mon, 18 Feb 2013 10:53:26 +0000 X-Env-Sender: christian@holpert.de X-Msg-Ref: server-5.tower-216.messagelabs.com!1361184806!27492824!1 X-Originating-IP: [80.67.18.44] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogODAuNjcuMTguNDQgPT4gNjEzNjc=\n X-StarScan-Received: X-StarScan-Version: 6.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 15368 invoked from network); 18 Feb 2013 10:53:26 -0000 Received: from smtprelay02.ispgateway.de (HELO smtprelay02.ispgateway.de) (80.67.18.44) by server-5.tower-216.messagelabs.com with SMTP; 18 Feb 2013 10:53:26 -0000 Received: from [217.83.81.125] (helo=colin.holpert.de) by smtprelay02.ispgateway.de with esmtpa (Exim 4.68) (envelope-from ) id 1U7OLd-0006vY-Jz for xen-users@lists.xen.org; Mon, 18 Feb 2013 11:53:25 +0100 Received: from PRO43287A006.holpert.de (unknown [10.75.157.20]) by colin.holpert.de (Postfix) with ESMTP id DC94F7FF3 for ; Mon, 18 Feb 2013 11:53:25 +0100 (CET) X-PGP-Fingerprint: D092 371C 931D 8F21 D71B 7A11 DC07 0F36 [RSA] X-PGP-Fingerprint: 8E3B 2F47 6673 B936 9EAE 52F3 4C8B C713 58C5 FFD6 [DH/DSS] X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9 Date: Mon, 18 Feb 2013 11:53:23 +0100 To: xen-users@lists.xen.org From: Christian Holpert In-Reply-To: References: Mime-Version: 1.0 Message-Id: X-Df-Sender: Y2hyaXN0aWFuQGhvbHBlcnQuZGU= Subject: Re: [Xen-users] Can't boot dom0 after upgrading to non-modified 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: 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 At 12:30 16.02.2013, you wrote: >domUs all work fine with the new kernel, after a few changes in the = >configs (such as changing /dev/sd... to /dev/xvd...) but dom0 won't = >boot when using the new kernel. It fails saying something like = >"please append a correct root=3D" (It reboots right away, I barely = >have time to read). use a camera and rewind the movie ;-) >This grub setting fails (kernel is gentoo-sources): >root (hd0,1) >kernel /boot/xen.gz dom0_mem=3D4096M dom0_max_vcpus=3D1 dom0_vcpus_pin >module /boot/kernel-3.6.11-gentoo root=3D/dev/sda6 > >I have compiled the kernel with all options mentioned in the gentoo = >xen doc, do you know of anything I might be missing? doesn't sound like a xen-problem in first place. Did you double-check all FS-Options and all drivers for your = chipset/HD-Controllers? Christian -- = Markt-Apotheke Christian Holpert e.K., M=F6mbris http://www.marktapotheke.org - info@marktapotheke.org http://www.blue-essentials-shop.de - info@blue-essentials-shop.de Apotheker Christian Holpert Im Markthof 5 63776 M=F6mbris Tel.: 06029-1379 Fax: 9986589 Amtsgericht Aschaffenburg, HR.A, Registernummer 2165 _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Mon Feb 18 10:54:01 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 18 Feb 2013 10:54: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 1U7OLh-0005w9-3O; Mon, 18 Feb 2013 10:53:29 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U7OLf-0005vn-5o for xen-users@lists.xen.org; Mon, 18 Feb 2013 10:53:27 +0000 Received: from [85.158.143.99:3248] by server-1.bemta-4.messagelabs.com id F4/F1-08839-62802215; Mon, 18 Feb 2013 10:53:26 +0000 X-Env-Sender: christian@holpert.de X-Msg-Ref: server-5.tower-216.messagelabs.com!1361184806!27492824!1 X-Originating-IP: [80.67.18.44] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogODAuNjcuMTguNDQgPT4gNjEzNjc=\n X-StarScan-Received: X-StarScan-Version: 6.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 15368 invoked from network); 18 Feb 2013 10:53:26 -0000 Received: from smtprelay02.ispgateway.de (HELO smtprelay02.ispgateway.de) (80.67.18.44) by server-5.tower-216.messagelabs.com with SMTP; 18 Feb 2013 10:53:26 -0000 Received: from [217.83.81.125] (helo=colin.holpert.de) by smtprelay02.ispgateway.de with esmtpa (Exim 4.68) (envelope-from ) id 1U7OLd-0006vY-Jz for xen-users@lists.xen.org; Mon, 18 Feb 2013 11:53:25 +0100 Received: from PRO43287A006.holpert.de (unknown [10.75.157.20]) by colin.holpert.de (Postfix) with ESMTP id DC94F7FF3 for ; Mon, 18 Feb 2013 11:53:25 +0100 (CET) X-PGP-Fingerprint: D092 371C 931D 8F21 D71B 7A11 DC07 0F36 [RSA] X-PGP-Fingerprint: 8E3B 2F47 6673 B936 9EAE 52F3 4C8B C713 58C5 FFD6 [DH/DSS] X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9 Date: Mon, 18 Feb 2013 11:53:23 +0100 To: xen-users@lists.xen.org From: Christian Holpert In-Reply-To: References: Mime-Version: 1.0 Message-Id: X-Df-Sender: Y2hyaXN0aWFuQGhvbHBlcnQuZGU= Subject: Re: [Xen-users] Can't boot dom0 after upgrading to non-modified 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: 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 At 12:30 16.02.2013, you wrote: >domUs all work fine with the new kernel, after a few changes in the = >configs (such as changing /dev/sd... to /dev/xvd...) but dom0 won't = >boot when using the new kernel. It fails saying something like = >"please append a correct root=3D" (It reboots right away, I barely = >have time to read). use a camera and rewind the movie ;-) >This grub setting fails (kernel is gentoo-sources): >root (hd0,1) >kernel /boot/xen.gz dom0_mem=3D4096M dom0_max_vcpus=3D1 dom0_vcpus_pin >module /boot/kernel-3.6.11-gentoo root=3D/dev/sda6 > >I have compiled the kernel with all options mentioned in the gentoo = >xen doc, do you know of anything I might be missing? doesn't sound like a xen-problem in first place. Did you double-check all FS-Options and all drivers for your = chipset/HD-Controllers? Christian -- = Markt-Apotheke Christian Holpert e.K., M=F6mbris http://www.marktapotheke.org - info@marktapotheke.org http://www.blue-essentials-shop.de - info@blue-essentials-shop.de Apotheker Christian Holpert Im Markthof 5 63776 M=F6mbris Tel.: 06029-1379 Fax: 9986589 Amtsgericht Aschaffenburg, HR.A, Registernummer 2165 _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Mon Feb 18 10:59:26 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 18 Feb 2013 10:59: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 1U7OQx-0006Ri-I8; Mon, 18 Feb 2013 10:58:55 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U7OQv-0006RY-Nj for xen-users@lists.xen.org; Mon, 18 Feb 2013 10:58:54 +0000 Received: from [85.158.138.51:11237] by server-4.bemta-3.messagelabs.com id EC/47-17521-D6902215; Mon, 18 Feb 2013 10:58:53 +0000 X-Env-Sender: eross@corp.locatrix.com X-Msg-Ref: server-14.tower-174.messagelabs.com!1361185129!21646998!1 X-Originating-IP: [209.85.210.171] 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.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 32282 invoked from network); 18 Feb 2013 10:58:51 -0000 Received: from mail-ia0-f171.google.com (HELO mail-ia0-f171.google.com) (209.85.210.171) by server-14.tower-174.messagelabs.com with RC4-SHA encrypted SMTP; 18 Feb 2013 10:58:51 -0000 Received: by mail-ia0-f171.google.com with SMTP id z13so5104998iaz.30 for ; Mon, 18 Feb 2013 02:58:49 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=x-received:mime-version:from:date:message-id:subject:to :content-type:x-gm-message-state; bh=Bk7dibwM/4Kkmliwgl10NXyvGwoU8CFWbrys5rocZwY=; b=Clr2jRrYs2h9afm0vRLjY4qR/+i5hMBf2U0rpWdDQ2EE3fWd1N3BNrjdXtYQv71UnL hQDOYzzczCqh0hq6dR7MFqHFLHTlJ4NjNEWp1yfur/W64f6jkh2VqO6ep/WELFLlX/Iv UbwhR8RwfCWOVpkPEU/+tiiqCafSWvYUUo7kbmUXzIcH/fXWAKVdFtV3LlURa+n/sgJf eBAB0CaIouGCtAUvn7H6/3fYR6fvuH/Wi9kuXzwTqJWD0IclcwiNJle+c431SO8k4688 UyONX+ws9UqdJbuhQumnjeg7MbuEactVHt/pSJTDMBUB+Yfvk8cSLWNbcrnQJKfl7mot xyEQ== X-Received: by 10.50.17.163 with SMTP id p3mr1045118igd.90.1361185129165; Mon, 18 Feb 2013 02:58:49 -0800 (PST) MIME-Version: 1.0 Received: by 10.64.44.197 with HTTP; Mon, 18 Feb 2013 02:58:29 -0800 (PST) From: Andrew Eross Date: Mon, 18 Feb 2013 07:58:29 -0300 Message-ID: To: xen-users@lists.xen.org X-Gm-Message-State: ALoCoQl6YbMviFXsFGV/XDWRdxAx7kf/DdtN5wCS+J92EEyWSkOY0WzWwRTwIO1lVE+UbIB4lzrh Subject: [Xen-users] Xen 4.2.1 unable to get domain type for domid X-BeenThere: xen-users@lists.xen.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="===============2610748965392734648==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============2610748965392734648== Content-Type: multipart/alternative; boundary=14dae93407cf18f3f604d5fd9cd5 --14dae93407cf18f3f604d5fd9cd5 Content-Type: text/plain; charset=ISO-8859-1 Hi guys, I'm running Xen 4.2.1, compiled manually so I can play with Remus and DRBD, running on Ubuntu 12.10. I keep getting this error when trying to start up my first VM to run the Ubuntu netboot installer. ----------------------------------------------------------------- root@left:/home/eross# xl create /etc/xen/ubuntu.cfg -c Parsing config from /etc/xen/ubuntu.cfg Daemon running with PID 1513 libxl: error: libxl_dom.c:34:libxl__domain_type: unable to get domain type for domid=1 Unable to attach console libxl: error: libxl_exec.c:118:libxl_report_child_exitstatus: console child [0] exited with error status 1 ----------------------------------------------------------------- Here's my VM's config: ----------------------------------------------------------------- root@left:/home/eross# cat /etc/xen/ubuntu.cfg name = "ubuntu" memory = 256 disk = [ 'drbd:drbd-vm,xvda,w' ] vif = [' '] kernel = "/var/lib/xen/images/ubuntu-netboot/vmlinuz" ramdisk = "/var/lib/xen/images/ubuntu-netboot/initrd.gz" extra = "debian-installer/exit/always_halt=true -- console=hvc0" ----------------------------------------------------------------- The ubuntu-netboot image there is 64-bit 12.04 Precise. Any ideas? Thank you! Andrew --14dae93407cf18f3f604d5fd9cd5 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Hi guys,

I'm running Xen 4.2.1, compiled = manually so I can play with Remus and DRBD, running on Ubuntu 12.10.
<= div>
I keep getting this error when trying to start up my fir= st VM to run the Ubuntu netboot installer.

-------------------------------------------------------= ----------
root@left:/home/eross#=A0xl create /etc/xen/ubuntu.cfg= -c
Parsing config from /etc/xen/ubuntu.cfg
Daemon runn= ing with PID 1513
libxl: error: libxl_dom.c:34:libxl__domain_type: unable to get domain = type for domid=3D1
Unable to attach console
libxl: erro= r: libxl_exec.c:118:libxl_report_child_exitstatus: console child [0] exited= with error status 1
-----------------------------------------------------------------

Here's my VM's config:
-------------= ----------------------------------------------------
root@left:/h= ome/eross# cat /etc/xen/ubuntu.cfg
name =3D "ubuntu"

memory =3D 256

disk =3D [ 'drbd:drbd-vm,xvda,w' ]
vif =3D [' ']

kernel =3D "/var/lib/x= en/images/ubuntu-netboot/vmlinuz"
ramdisk =3D "/var/lib/xen/images/ubuntu-netboot/initrd.gz"
extra =3D "debian-installer/exit/always_halt=3Dtrue -- consol= e=3Dhvc0"
--------------------------------------------------= ---------------

The ubuntu-netboot image there is 64-bit 12.04 Precise.=

Any ideas?

Thank you!
Andrew

--14dae93407cf18f3f604d5fd9cd5-- --===============2610748965392734648== 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 --===============2610748965392734648==-- From xen-users-bounces@lists.xen.org Mon Feb 18 10:59:26 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 18 Feb 2013 10:59: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 1U7OQx-0006Ri-I8; Mon, 18 Feb 2013 10:58:55 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U7OQv-0006RY-Nj for xen-users@lists.xen.org; Mon, 18 Feb 2013 10:58:54 +0000 Received: from [85.158.138.51:11237] by server-4.bemta-3.messagelabs.com id EC/47-17521-D6902215; Mon, 18 Feb 2013 10:58:53 +0000 X-Env-Sender: eross@corp.locatrix.com X-Msg-Ref: server-14.tower-174.messagelabs.com!1361185129!21646998!1 X-Originating-IP: [209.85.210.171] 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.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 32282 invoked from network); 18 Feb 2013 10:58:51 -0000 Received: from mail-ia0-f171.google.com (HELO mail-ia0-f171.google.com) (209.85.210.171) by server-14.tower-174.messagelabs.com with RC4-SHA encrypted SMTP; 18 Feb 2013 10:58:51 -0000 Received: by mail-ia0-f171.google.com with SMTP id z13so5104998iaz.30 for ; Mon, 18 Feb 2013 02:58:49 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=x-received:mime-version:from:date:message-id:subject:to :content-type:x-gm-message-state; bh=Bk7dibwM/4Kkmliwgl10NXyvGwoU8CFWbrys5rocZwY=; b=Clr2jRrYs2h9afm0vRLjY4qR/+i5hMBf2U0rpWdDQ2EE3fWd1N3BNrjdXtYQv71UnL hQDOYzzczCqh0hq6dR7MFqHFLHTlJ4NjNEWp1yfur/W64f6jkh2VqO6ep/WELFLlX/Iv UbwhR8RwfCWOVpkPEU/+tiiqCafSWvYUUo7kbmUXzIcH/fXWAKVdFtV3LlURa+n/sgJf eBAB0CaIouGCtAUvn7H6/3fYR6fvuH/Wi9kuXzwTqJWD0IclcwiNJle+c431SO8k4688 UyONX+ws9UqdJbuhQumnjeg7MbuEactVHt/pSJTDMBUB+Yfvk8cSLWNbcrnQJKfl7mot xyEQ== X-Received: by 10.50.17.163 with SMTP id p3mr1045118igd.90.1361185129165; Mon, 18 Feb 2013 02:58:49 -0800 (PST) MIME-Version: 1.0 Received: by 10.64.44.197 with HTTP; Mon, 18 Feb 2013 02:58:29 -0800 (PST) From: Andrew Eross Date: Mon, 18 Feb 2013 07:58:29 -0300 Message-ID: To: xen-users@lists.xen.org X-Gm-Message-State: ALoCoQl6YbMviFXsFGV/XDWRdxAx7kf/DdtN5wCS+J92EEyWSkOY0WzWwRTwIO1lVE+UbIB4lzrh Subject: [Xen-users] Xen 4.2.1 unable to get domain type for domid X-BeenThere: xen-users@lists.xen.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="===============2610748965392734648==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============2610748965392734648== Content-Type: multipart/alternative; boundary=14dae93407cf18f3f604d5fd9cd5 --14dae93407cf18f3f604d5fd9cd5 Content-Type: text/plain; charset=ISO-8859-1 Hi guys, I'm running Xen 4.2.1, compiled manually so I can play with Remus and DRBD, running on Ubuntu 12.10. I keep getting this error when trying to start up my first VM to run the Ubuntu netboot installer. ----------------------------------------------------------------- root@left:/home/eross# xl create /etc/xen/ubuntu.cfg -c Parsing config from /etc/xen/ubuntu.cfg Daemon running with PID 1513 libxl: error: libxl_dom.c:34:libxl__domain_type: unable to get domain type for domid=1 Unable to attach console libxl: error: libxl_exec.c:118:libxl_report_child_exitstatus: console child [0] exited with error status 1 ----------------------------------------------------------------- Here's my VM's config: ----------------------------------------------------------------- root@left:/home/eross# cat /etc/xen/ubuntu.cfg name = "ubuntu" memory = 256 disk = [ 'drbd:drbd-vm,xvda,w' ] vif = [' '] kernel = "/var/lib/xen/images/ubuntu-netboot/vmlinuz" ramdisk = "/var/lib/xen/images/ubuntu-netboot/initrd.gz" extra = "debian-installer/exit/always_halt=true -- console=hvc0" ----------------------------------------------------------------- The ubuntu-netboot image there is 64-bit 12.04 Precise. Any ideas? Thank you! Andrew --14dae93407cf18f3f604d5fd9cd5 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Hi guys,

I'm running Xen 4.2.1, compiled = manually so I can play with Remus and DRBD, running on Ubuntu 12.10.
<= div>
I keep getting this error when trying to start up my fir= st VM to run the Ubuntu netboot installer.

-------------------------------------------------------= ----------
root@left:/home/eross#=A0xl create /etc/xen/ubuntu.cfg= -c
Parsing config from /etc/xen/ubuntu.cfg
Daemon runn= ing with PID 1513
libxl: error: libxl_dom.c:34:libxl__domain_type: unable to get domain = type for domid=3D1
Unable to attach console
libxl: erro= r: libxl_exec.c:118:libxl_report_child_exitstatus: console child [0] exited= with error status 1
-----------------------------------------------------------------

Here's my VM's config:
-------------= ----------------------------------------------------
root@left:/h= ome/eross# cat /etc/xen/ubuntu.cfg
name =3D "ubuntu"

memory =3D 256

disk =3D [ 'drbd:drbd-vm,xvda,w' ]
vif =3D [' ']

kernel =3D "/var/lib/x= en/images/ubuntu-netboot/vmlinuz"
ramdisk =3D "/var/lib/xen/images/ubuntu-netboot/initrd.gz"
extra =3D "debian-installer/exit/always_halt=3Dtrue -- consol= e=3Dhvc0"
--------------------------------------------------= ---------------

The ubuntu-netboot image there is 64-bit 12.04 Precise.=

Any ideas?

Thank you!
Andrew

--14dae93407cf18f3f604d5fd9cd5-- --===============2610748965392734648== 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 --===============2610748965392734648==-- From xen-users-bounces@lists.xen.org Mon Feb 18 10:59:47 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 18 Feb 2013 10:59: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 1U7ORO-0006WN-VM; Mon, 18 Feb 2013 10:59:22 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U7ORN-0006Vt-Bj for xen-users@lists.xen.org; Mon, 18 Feb 2013 10:59:21 +0000 Received: from [85.158.143.99:14111] by server-1.bemta-4.messagelabs.com id 68/9D-08839-88902215; Mon, 18 Feb 2013 10:59:20 +0000 X-Env-Sender: Ian.Campbell@citrix.com X-Msg-Ref: server-15.tower-216.messagelabs.com!1361185158!27939666!1 X-Originating-IP: [46.33.159.39] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNDYuMzMuMTU5LjM5ID0+IDIzMTUw\n X-StarScan-Received: X-StarScan-Version: 6.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 17763 invoked from network); 18 Feb 2013 10:59:20 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (46.33.159.39) by server-15.tower-216.messagelabs.com with RC4-SHA encrypted SMTP; 18 Feb 2013 10:59:20 -0000 X-IronPort-AV: E=Sophos;i="4.84,686,1355097600"; d="scan'208";a="1565086" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 18 Feb 2013 10:59: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.297.1; Mon, 18 Feb 2013 10:59:18 +0000 Message-ID: <1361185156.31407.148.camel@zakaz.uk.xensource.com> From: Ian Campbell To: Christian Holpert Date: Mon, 18 Feb 2013 10:59:16 +0000 In-Reply-To: References: Organization: Citrix Systems, Inc. X-Mailer: Evolution 3.4.4-1 MIME-Version: 1.0 Cc: "xen-users@lists.xen.org" Subject: Re: [Xen-users] Can't boot dom0 after upgrading to non-modified 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-Type: 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, 2013-02-18 at 10:53 +0000, Christian Holpert wrote: > At 12:30 16.02.2013, you wrote: > >domUs all work fine with the new kernel, after a few changes in the > >configs (such as changing /dev/sd... to /dev/xvd...) but dom0 won't > >boot when using the new kernel. It fails saying something like > >"please append a correct root=" (It reboots right away, I barely > >have time to read). > > use a camera and rewind the movie ;-) Or add "noreboot" to your hypervisor command line. Ian. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Mon Feb 18 10:59:47 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 18 Feb 2013 10:59: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 1U7ORO-0006WN-VM; Mon, 18 Feb 2013 10:59:22 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U7ORN-0006Vt-Bj for xen-users@lists.xen.org; Mon, 18 Feb 2013 10:59:21 +0000 Received: from [85.158.143.99:14111] by server-1.bemta-4.messagelabs.com id 68/9D-08839-88902215; Mon, 18 Feb 2013 10:59:20 +0000 X-Env-Sender: Ian.Campbell@citrix.com X-Msg-Ref: server-15.tower-216.messagelabs.com!1361185158!27939666!1 X-Originating-IP: [46.33.159.39] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNDYuMzMuMTU5LjM5ID0+IDIzMTUw\n X-StarScan-Received: X-StarScan-Version: 6.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 17763 invoked from network); 18 Feb 2013 10:59:20 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (46.33.159.39) by server-15.tower-216.messagelabs.com with RC4-SHA encrypted SMTP; 18 Feb 2013 10:59:20 -0000 X-IronPort-AV: E=Sophos;i="4.84,686,1355097600"; d="scan'208";a="1565086" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 18 Feb 2013 10:59: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.297.1; Mon, 18 Feb 2013 10:59:18 +0000 Message-ID: <1361185156.31407.148.camel@zakaz.uk.xensource.com> From: Ian Campbell To: Christian Holpert Date: Mon, 18 Feb 2013 10:59:16 +0000 In-Reply-To: References: Organization: Citrix Systems, Inc. X-Mailer: Evolution 3.4.4-1 MIME-Version: 1.0 Cc: "xen-users@lists.xen.org" Subject: Re: [Xen-users] Can't boot dom0 after upgrading to non-modified 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-Type: 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, 2013-02-18 at 10:53 +0000, Christian Holpert wrote: > At 12:30 16.02.2013, you wrote: > >domUs all work fine with the new kernel, after a few changes in the > >configs (such as changing /dev/sd... to /dev/xvd...) but dom0 won't > >boot when using the new kernel. It fails saying something like > >"please append a correct root=" (It reboots right away, I barely > >have time to read). > > use a camera and rewind the movie ;-) Or add "noreboot" to your hypervisor command line. Ian. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Mon Feb 18 11:02:56 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 18 Feb 2013 11:02: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 1U7OUN-0007BJ-Sc; Mon, 18 Feb 2013 11:02:27 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U7OUM-0007Az-1Z for xen-users@lists.xen.org; Mon, 18 Feb 2013 11:02:26 +0000 Received: from [85.158.139.83:38936] by server-10.bemta-5.messagelabs.com id 2A/D9-04697-14A02215; Mon, 18 Feb 2013 11:02:25 +0000 X-Env-Sender: Ian.Campbell@citrix.com X-Msg-Ref: server-16.tower-182.messagelabs.com!1361185324!20386333!1 X-Originating-IP: [46.33.159.39] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNDYuMzMuMTU5LjM5ID0+IDIzMTUw\n X-StarScan-Received: X-StarScan-Version: 6.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 20477 invoked from network); 18 Feb 2013 11:02:04 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (46.33.159.39) by server-16.tower-182.messagelabs.com with RC4-SHA encrypted SMTP; 18 Feb 2013 11:02:04 -0000 X-IronPort-AV: E=Sophos;i="4.84,686,1355097600"; d="scan'208";a="1565223" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 18 Feb 2013 11:02:04 +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.297.1; Mon, 18 Feb 2013 11:02:03 +0000 Message-ID: <1361185322.31407.150.camel@zakaz.uk.xensource.com> From: Ian Campbell To: Daniel Farrell Date: Mon, 18 Feb 2013 11:02:02 +0000 In-Reply-To: <80883B3E-3FAF-481A-BA6E-700372B3018C@gmail.com> References: <80883B3E-3FAF-481A-BA6E-700372B3018C@gmail.com> Organization: Citrix Systems, Inc. X-Mailer: Evolution 3.4.4-1 MIME-Version: 1.0 Cc: "xen-users@lists.xen.org" Subject: Re: [Xen-users] Install issues for Xen 4.2.1 on Ubuntu 12.10 X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: 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, 2013-02-17 at 06:33 +0000, Daniel Farrell wrote: > > > $ xl info libxl: error: libxl.c:87:libxl_ctx_alloc: Is xenstore daemon > running? > failed to stat /var/run/xenstored.pid: No such file or directory > cannot init xl context Looks like you didn't enable the xencommons initscript, try: update-rc.d -f xencommons start 70 2 3 4 5 . stop 10 0 1 6 . Ian. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Mon Feb 18 11:02:56 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 18 Feb 2013 11:02: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 1U7OUN-0007BJ-Sc; Mon, 18 Feb 2013 11:02:27 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U7OUM-0007Az-1Z for xen-users@lists.xen.org; Mon, 18 Feb 2013 11:02:26 +0000 Received: from [85.158.139.83:38936] by server-10.bemta-5.messagelabs.com id 2A/D9-04697-14A02215; Mon, 18 Feb 2013 11:02:25 +0000 X-Env-Sender: Ian.Campbell@citrix.com X-Msg-Ref: server-16.tower-182.messagelabs.com!1361185324!20386333!1 X-Originating-IP: [46.33.159.39] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNDYuMzMuMTU5LjM5ID0+IDIzMTUw\n X-StarScan-Received: X-StarScan-Version: 6.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 20477 invoked from network); 18 Feb 2013 11:02:04 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (46.33.159.39) by server-16.tower-182.messagelabs.com with RC4-SHA encrypted SMTP; 18 Feb 2013 11:02:04 -0000 X-IronPort-AV: E=Sophos;i="4.84,686,1355097600"; d="scan'208";a="1565223" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 18 Feb 2013 11:02:04 +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.297.1; Mon, 18 Feb 2013 11:02:03 +0000 Message-ID: <1361185322.31407.150.camel@zakaz.uk.xensource.com> From: Ian Campbell To: Daniel Farrell Date: Mon, 18 Feb 2013 11:02:02 +0000 In-Reply-To: <80883B3E-3FAF-481A-BA6E-700372B3018C@gmail.com> References: <80883B3E-3FAF-481A-BA6E-700372B3018C@gmail.com> Organization: Citrix Systems, Inc. X-Mailer: Evolution 3.4.4-1 MIME-Version: 1.0 Cc: "xen-users@lists.xen.org" Subject: Re: [Xen-users] Install issues for Xen 4.2.1 on Ubuntu 12.10 X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: 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, 2013-02-17 at 06:33 +0000, Daniel Farrell wrote: > > > $ xl info libxl: error: libxl.c:87:libxl_ctx_alloc: Is xenstore daemon > running? > failed to stat /var/run/xenstored.pid: No such file or directory > cannot init xl context Looks like you didn't enable the xencommons initscript, try: update-rc.d -f xencommons start 70 2 3 4 5 . stop 10 0 1 6 . Ian. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Mon Feb 18 11:41:42 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 18 Feb 2013 11:41: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 1U7P5Z-0000UQ-Sp; Mon, 18 Feb 2013 11:40:53 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U7P5Y-0000UL-Pr for xen-users@lists.xen.org; Mon, 18 Feb 2013 11:40:53 +0000 Received: from [85.158.138.51:2946] by server-16.bemta-3.messagelabs.com id EF/E6-02727-F3312215; Mon, 18 Feb 2013 11:40:47 +0000 X-Env-Sender: netmatters@gmail.com X-Msg-Ref: server-10.tower-174.messagelabs.com!1361187638!23949432!1 X-Originating-IP: [209.85.128.169] 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.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 11599 invoked from network); 18 Feb 2013 11:40:40 -0000 Received: from mail-ve0-f169.google.com (HELO mail-ve0-f169.google.com) (209.85.128.169) by server-10.tower-174.messagelabs.com with RC4-SHA encrypted SMTP; 18 Feb 2013 11:40:40 -0000 Received: by mail-ve0-f169.google.com with SMTP id 15so4697762vea.14 for ; Mon, 18 Feb 2013 03:40:38 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=YqIgsKEPDCL6JViB+8/UaV9usfCyz+YuXkb8s2aBMfc=; b=J37gW8/A5IONtZZNnKFazLBwrIk93UE88IlYtg8IqrHsqNGyTg0yNlWNHGZw5BaD9d P/x6YjRU2HYoroGFKw//9BP+zXK3+1++HXubwdGSA/YpoWGivj1s0twgG+N7h61gyn93 WVWDbhhGcqKpaRJSsYQ3c7P77KEQk8Ez0v0WtBe+l/bgGJT8RkXZ6i5D9nzbP5vz7ezQ YHyl6R+WInbjaAS60aQ5q3KQOpnEHG544Bxx4TrbYQZFHEKideLt4c6XFWRBn7+MzxnM 2OTyk24PeT4SjLaMLYGPtfrjISrzw4QYHimCAwxHcMd5lcdjLykoAwCXDoB3OQJLvnwN jdxQ== MIME-Version: 1.0 X-Received: by 10.220.149.198 with SMTP id u6mr14750107vcv.52.1361187638501; Mon, 18 Feb 2013 03:40:38 -0800 (PST) Received: by 10.58.106.133 with HTTP; Mon, 18 Feb 2013 03:40:38 -0800 (PST) In-Reply-To: <1361184601.31407.144.camel@zakaz.uk.xensource.com> References: <1361184601.31407.144.camel@zakaz.uk.xensource.com> Date: Mon, 18 Feb 2013 13:40:38 +0200 Message-ID: From: Gavin To: Ian Campbell Cc: pkg-xen-devel@lists.alioth.debian.org, xen-users , debian-user@lists.debian.org Subject: Re: [Xen-users] [Pkg-xen-devel] Recent hypervisor update on Debian Wheezy breaks domU 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="===============7515223315650177198==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============7515223315650177198== Content-Type: multipart/alternative; boundary=f46d043c816caa623e04d5fe3164 --f46d043c816caa623e04d5fe3164 Content-Type: text/plain; charset=ISO-8859-1 On 18 February 2013 12:50, Ian Campbell wrote: > On Mon, 2013-02-18 at 12:04 +0200, Gavin wrote: > > > > Firstly I apologise for the cross-post, > > I've added xen-users since you also bounced this there. > Thanks. :-/ Thanks too for your quick reply. > > > however I don't expect to get as quick a response from the package > > maintainers as I do from the Debian community, and this issue affects > > a service that I've got scheduled to go live at midnight this > > evening. :( > > > > > > A recent update from xen-hypervisor-4.1-amd64 version 4.1.3-7, to > > version 4.1.3-8 on Debian Wheezy has caused all vm's on this host to > > not receive their arp replies anymore and as such they cannot reach > > their gateways and are now isolated from the network. > > > > > > There was a more recent update as well (4.1.4-2) which I have now > > since applied however this particular issue persists. > > Networking level stuff is all done by the dom0 (or driver domain) kernel > rather than the hypervisor so it is far more likely that a kernel level > change rather than a hypervisor change would be responsible. What kernel > version are you running? Did it also change? > This makes sense, although when I did the apt-get upgrade, there was no kernel update, however there may have been packages/drivers that required a kernel mod. Here is the apt history which details what was upgraded when this broke:- Upgrade: dnsmasq-base:amd64 (2.62-3, 2.62-3+deb7u1), tasksel-data:amd64 (3.14, 3.14+nmu1), xen-hypervisor-4.1-amd64:amd64 (4.1.3-7, 4.1.3-8), xen-utils-common:amd64 (4.1.3-7, 4.1.3-8), perl:amd64 (5.14.2-16, 5.14.2-17), firmware-linux-free:amd64 (3.1, 3.2), perl-base:amd64 (5.14.2-16, 5.14.2-17), xen-utils-4.1:amd64 (4.1.3-7, 4.1.3-8), libgnutls26:amd64 (2.12.20-2, 2.12.20-4), perl-modules:amd64 (5.14.2-16, 5.14.2-17), psmisc:amd64 (22.19-1, 22.19-1+deb7u1), python2.6:amd64 (2.6.8-0.2, 2.6.8-1.1), libxenstore3.0:amd64 (4.1.3-7, 4.1.3-8), python2.6-minimal:amd64 (2.6.8-0.2, 2.6.8-1.1), coreutils:amd64 (8.13-3.4, 8.13-3.5), libvirt0:amd64 (0.9.12-5, 0.9.12-6), libcurl3:amd64 (7.26.0-1, 7.26.0-1+wheezy1), manpages:amd64 (3.42-1, 3.44-1), tasksel:amd64 (3.14, 3.14+nmu1), libperl5.14:amd64 (5.14.2-16, 5.14.2-17), libsystemd-login0:amd64 (44-7, 44-8), libxen-4.1:amd64 (4.1.3-7, 4.1.3-8), libcurl3-gnutls:amd64 (7.26.0-1, 7.26.0-1+wheezy1), host:amd64 (9.8.4.dfsg.P1-1, 9.8.4.dfsg.P1-4), libvirt-bin:amd64 (0.9.12-5, 0.9.12-6), rinse:amd64 (2.0-1, 2.0.1-1), ca-certificates:amd64 (20120623, 20130119), xenstore-utils:amd64 (4.1.3-7, 4.1.3-8) The kernel I am using is: 3.2.0-2-amd64, also tried 3.2.0-4-amd64 on another host with no success. Would the upgrade above of xen-hypervisor-4.1-amd64 on this Debian system not cause the Dom0 kernel to be changed in any way ?? > > The arp replies are received by the host and passed all the way up to > > the bridge (br200) being used by Xen, however they are not seen on the > > vif (vif2.0) created for the particular vm. > > Do you have any firewall or ebfilter entries which might have either > been discarded or reintroduced by the reboot? (i.e. a manual settings > modification which wasn't propagated to the startup scripts). Or perhaps > sysctl tweaks? > Nope, not using iptables/ebtables, this was working 100% until the apt upgrade above. After this broke I did try and add the following to /etc/sysctl.conf but it made no difference:- net.bridge.bridge-nf-call-ip6tables = 0 net.bridge.bridge-nf-call-iptables = 0 net.bridge.bridge-nf-call-arptables = 0 It did add iptables rules but made no difference to this issue. > > > 1) Please let me know if I should roll-back this particular xen > > update, kernel and all, and what those steps may be, or if this is a > > known issue with a particular workaround that I can apply. > > I'd certainly be tempted to try the older kernel, assuming that was also > upgraded. It may even still be installed and in your grub menu already. > The problem is now we are using grub2 and it appears that on boot grub loads a Linux menu, then the Xen Menu with configs in /etc/grub.d/ so I'm battling to figure out how to do this. I also do not have physical access to this host at the moment so need to set the boot order 'correctly' prior to a reboot. > > > 2) Would moving to openvswitch be another possible workaround? > > Without knowing what the underlying issue is it is hard to predict > whether it will also affect ovs. > Agreed. > > > My config:- > > Looks correct to me. > > Ian. > Thanks Ian. --f46d043c816caa623e04d5fe3164 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
On 18 February 2013 12:50, Ian Campbell = <ijc@hellion.org= .uk> wrote:
On Mon, 2013-02-18 at 12:04 +0200, Gavin wrote:


> Firstly I apologise for the cross-post,

I've added xen-users since you also bounced this there.

Thanks. :-/ =A0Thanks too for your quick r= eply.

> =A0however I don't expect to get as quick a response from the pack= age
> maintainers as I do from the Debian community, and this issue affects<= br> > a service that I've got scheduled to go live at midnight this
> evening. :(
>
>
> A recent update from xen-hypervisor-4.1-amd64 version 4.1.3-7, to
> version 4.1.3-8 on Debian Wheezy has caused all vm's on this host = to
> not receive their arp replies anymore and as such they cannot reach > their gateways and are now isolated from the network.
>
>
> There was a more recent update as well (4.1.4-2) which I have now
> since applied however this particular issue persists.

Networking level stuff is all done by the dom0 (or driver domain) ker= nel
rather than the hypervisor so it is far more likely that a kernel level
change rather than a hypervisor change would be responsible. What kernel version are you running? Did it also change?

This makes sense, although when I did the apt-get upgrade, ther= e was no kernel update, however there may have been packages/drivers that r= equired a kernel mod.

Here is the apt history which details what = was upgraded when this broke:-

Upgrade: dnsm= asq-base:amd64 (2.62-3, 2.62-3+deb7u1), tasksel-data:amd64 (3.14, 3.14+nmu1= ), xen-hypervisor-4.1-amd64:amd64 (4.1.3-7, 4.1.3-8), xen-utils-common:amd6= 4 (4.1.3-7, 4.1.3-8), perl:amd64 (5.14.2-16, 5.14.2-17), firmware-linux-fre= e:amd64 (3.1, 3.2), perl-base:amd64 (5.14.2-16, 5.14.2-17), xen-utils-4.1:a= md64 (4.1.3-7, 4.1.3-8), libgnutls26:amd64 (2.12.20-2, 2.12.20-4), perl-mod= ules:amd64 (5.14.2-16, 5.14.2-17), psmisc:amd64 (22.19-1, 22.19-1+deb7u1), = python2.6:amd64 (2.6.8-0.2, 2.6.8-1.1), libxenstore3.0:amd64 (4.1.3-7, 4.1.= 3-8), python2.6-minimal:amd64 (2.6.8-0.2, 2.6.8-1.1), coreutils:amd64 (8.13= -3.4, 8.13-3.5), libvirt0:amd64 (0.9.12-5, 0.9.12-6), libcurl3:amd64 (7.26.= 0-1, 7.26.0-1+wheezy1), manpages:amd64 (3.42-1, 3.44-1), tasksel:amd64 (3.1= 4, 3.14+nmu1), libperl5.14:amd64 (5.14.2-16, 5.14.2-17), libsystemd-login0:= amd64 (44-7, 44-8), libxen-4.1:amd64 (4.1.3-7, 4.1.3-8), libcurl3-gnutls:am= d64 (7.26.0-1, 7.26.0-1+wheezy1), host:amd64 (9.8.4.dfsg.P1-1, 9.8.4.dfsg.P= 1-4), libvirt-bin:amd64 (0.9.12-5, 0.9.12-6), rinse:amd64 (2.0-1, 2.0.1-1),= ca-certificates:amd64 (20120623, 20130119), xenstore-utils:amd64 (4.1.3-7,= 4.1.3-8)

The kernel I am using is:=A03.2.0-2-amd64, also t= ried 3.2.0-4-amd64 on another host with no success.
=A0
Would the upgrade above of xen-hypervisor-4.1-amd64 on this De= bian system not cause the Dom0 kernel to be changed in any way ??=A0
=A0
> The arp replies are received by the host and passed all the way up to<= br> > the bridge (br200) being used by Xen, however they are not seen on the=
> vif (vif2.0) created for the particular vm.

Do you have any firewall or ebfilter entries which might have either<= br> been discarded or reintroduced by the reboot? (i.e. a manual settings
modification which wasn't propagated to the startup scripts). Or perhap= s
sysctl tweaks?

Nope, not using ip= tables/ebtables, this was working 100% until the apt upgrade above.

After this broke I did try and add the follow= ing to /etc/sysctl.conf but it made no difference:-

net.bridge.bridge-nf-call-ip6tables = =3D 0
net.bridge.bridge-nf-call-iptables =3D 0
net.brid= ge.bridge-nf-call-arptables =3D 0

It did add= iptables rules but made no difference to this issue.
=A0

> 1) Please let me know if I should roll-back this particular xen
> update, kernel and all, and what those steps may be, or if this is a > known issue with a particular workaround that I can apply.

I'd certainly be tempted to try the older kernel, assuming that w= as also
upgraded. It may even still be installed and in your grub menu already.
=

The problem is now we are using grub= 2 and it appears that on boot grub loads a Linux menu, then the Xen Menu wi= th configs in /etc/grub.d/ so I'm battling to figure out how to do this= .

I also do not have physical access to this = host at the moment so need to set the boot order 'correctly' prior = to a reboot.

> 2) Would moving to openvswitch be another possible workaround?

Without knowing what the underlying issue is it is hard to predict whether it will also affect ovs.

= Agreed.=A0

> My config:-

Looks correct to me.

Ian.

Thanks Ian.=A0=

=A0

--f46d043c816caa623e04d5fe3164-- --===============7515223315650177198== 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 --===============7515223315650177198==-- From xen-users-bounces@lists.xen.org Mon Feb 18 11:41:42 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 18 Feb 2013 11:41: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 1U7P5Z-0000UQ-Sp; Mon, 18 Feb 2013 11:40:53 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U7P5Y-0000UL-Pr for xen-users@lists.xen.org; Mon, 18 Feb 2013 11:40:53 +0000 Received: from [85.158.138.51:2946] by server-16.bemta-3.messagelabs.com id EF/E6-02727-F3312215; Mon, 18 Feb 2013 11:40:47 +0000 X-Env-Sender: netmatters@gmail.com X-Msg-Ref: server-10.tower-174.messagelabs.com!1361187638!23949432!1 X-Originating-IP: [209.85.128.169] 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.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 11599 invoked from network); 18 Feb 2013 11:40:40 -0000 Received: from mail-ve0-f169.google.com (HELO mail-ve0-f169.google.com) (209.85.128.169) by server-10.tower-174.messagelabs.com with RC4-SHA encrypted SMTP; 18 Feb 2013 11:40:40 -0000 Received: by mail-ve0-f169.google.com with SMTP id 15so4697762vea.14 for ; Mon, 18 Feb 2013 03:40:38 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=YqIgsKEPDCL6JViB+8/UaV9usfCyz+YuXkb8s2aBMfc=; b=J37gW8/A5IONtZZNnKFazLBwrIk93UE88IlYtg8IqrHsqNGyTg0yNlWNHGZw5BaD9d P/x6YjRU2HYoroGFKw//9BP+zXK3+1++HXubwdGSA/YpoWGivj1s0twgG+N7h61gyn93 WVWDbhhGcqKpaRJSsYQ3c7P77KEQk8Ez0v0WtBe+l/bgGJT8RkXZ6i5D9nzbP5vz7ezQ YHyl6R+WInbjaAS60aQ5q3KQOpnEHG544Bxx4TrbYQZFHEKideLt4c6XFWRBn7+MzxnM 2OTyk24PeT4SjLaMLYGPtfrjISrzw4QYHimCAwxHcMd5lcdjLykoAwCXDoB3OQJLvnwN jdxQ== MIME-Version: 1.0 X-Received: by 10.220.149.198 with SMTP id u6mr14750107vcv.52.1361187638501; Mon, 18 Feb 2013 03:40:38 -0800 (PST) Received: by 10.58.106.133 with HTTP; Mon, 18 Feb 2013 03:40:38 -0800 (PST) In-Reply-To: <1361184601.31407.144.camel@zakaz.uk.xensource.com> References: <1361184601.31407.144.camel@zakaz.uk.xensource.com> Date: Mon, 18 Feb 2013 13:40:38 +0200 Message-ID: From: Gavin To: Ian Campbell Cc: pkg-xen-devel@lists.alioth.debian.org, xen-users , debian-user@lists.debian.org Subject: Re: [Xen-users] [Pkg-xen-devel] Recent hypervisor update on Debian Wheezy breaks domU 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="===============7515223315650177198==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============7515223315650177198== Content-Type: multipart/alternative; boundary=f46d043c816caa623e04d5fe3164 --f46d043c816caa623e04d5fe3164 Content-Type: text/plain; charset=ISO-8859-1 On 18 February 2013 12:50, Ian Campbell wrote: > On Mon, 2013-02-18 at 12:04 +0200, Gavin wrote: > > > > Firstly I apologise for the cross-post, > > I've added xen-users since you also bounced this there. > Thanks. :-/ Thanks too for your quick reply. > > > however I don't expect to get as quick a response from the package > > maintainers as I do from the Debian community, and this issue affects > > a service that I've got scheduled to go live at midnight this > > evening. :( > > > > > > A recent update from xen-hypervisor-4.1-amd64 version 4.1.3-7, to > > version 4.1.3-8 on Debian Wheezy has caused all vm's on this host to > > not receive their arp replies anymore and as such they cannot reach > > their gateways and are now isolated from the network. > > > > > > There was a more recent update as well (4.1.4-2) which I have now > > since applied however this particular issue persists. > > Networking level stuff is all done by the dom0 (or driver domain) kernel > rather than the hypervisor so it is far more likely that a kernel level > change rather than a hypervisor change would be responsible. What kernel > version are you running? Did it also change? > This makes sense, although when I did the apt-get upgrade, there was no kernel update, however there may have been packages/drivers that required a kernel mod. Here is the apt history which details what was upgraded when this broke:- Upgrade: dnsmasq-base:amd64 (2.62-3, 2.62-3+deb7u1), tasksel-data:amd64 (3.14, 3.14+nmu1), xen-hypervisor-4.1-amd64:amd64 (4.1.3-7, 4.1.3-8), xen-utils-common:amd64 (4.1.3-7, 4.1.3-8), perl:amd64 (5.14.2-16, 5.14.2-17), firmware-linux-free:amd64 (3.1, 3.2), perl-base:amd64 (5.14.2-16, 5.14.2-17), xen-utils-4.1:amd64 (4.1.3-7, 4.1.3-8), libgnutls26:amd64 (2.12.20-2, 2.12.20-4), perl-modules:amd64 (5.14.2-16, 5.14.2-17), psmisc:amd64 (22.19-1, 22.19-1+deb7u1), python2.6:amd64 (2.6.8-0.2, 2.6.8-1.1), libxenstore3.0:amd64 (4.1.3-7, 4.1.3-8), python2.6-minimal:amd64 (2.6.8-0.2, 2.6.8-1.1), coreutils:amd64 (8.13-3.4, 8.13-3.5), libvirt0:amd64 (0.9.12-5, 0.9.12-6), libcurl3:amd64 (7.26.0-1, 7.26.0-1+wheezy1), manpages:amd64 (3.42-1, 3.44-1), tasksel:amd64 (3.14, 3.14+nmu1), libperl5.14:amd64 (5.14.2-16, 5.14.2-17), libsystemd-login0:amd64 (44-7, 44-8), libxen-4.1:amd64 (4.1.3-7, 4.1.3-8), libcurl3-gnutls:amd64 (7.26.0-1, 7.26.0-1+wheezy1), host:amd64 (9.8.4.dfsg.P1-1, 9.8.4.dfsg.P1-4), libvirt-bin:amd64 (0.9.12-5, 0.9.12-6), rinse:amd64 (2.0-1, 2.0.1-1), ca-certificates:amd64 (20120623, 20130119), xenstore-utils:amd64 (4.1.3-7, 4.1.3-8) The kernel I am using is: 3.2.0-2-amd64, also tried 3.2.0-4-amd64 on another host with no success. Would the upgrade above of xen-hypervisor-4.1-amd64 on this Debian system not cause the Dom0 kernel to be changed in any way ?? > > The arp replies are received by the host and passed all the way up to > > the bridge (br200) being used by Xen, however they are not seen on the > > vif (vif2.0) created for the particular vm. > > Do you have any firewall or ebfilter entries which might have either > been discarded or reintroduced by the reboot? (i.e. a manual settings > modification which wasn't propagated to the startup scripts). Or perhaps > sysctl tweaks? > Nope, not using iptables/ebtables, this was working 100% until the apt upgrade above. After this broke I did try and add the following to /etc/sysctl.conf but it made no difference:- net.bridge.bridge-nf-call-ip6tables = 0 net.bridge.bridge-nf-call-iptables = 0 net.bridge.bridge-nf-call-arptables = 0 It did add iptables rules but made no difference to this issue. > > > 1) Please let me know if I should roll-back this particular xen > > update, kernel and all, and what those steps may be, or if this is a > > known issue with a particular workaround that I can apply. > > I'd certainly be tempted to try the older kernel, assuming that was also > upgraded. It may even still be installed and in your grub menu already. > The problem is now we are using grub2 and it appears that on boot grub loads a Linux menu, then the Xen Menu with configs in /etc/grub.d/ so I'm battling to figure out how to do this. I also do not have physical access to this host at the moment so need to set the boot order 'correctly' prior to a reboot. > > > 2) Would moving to openvswitch be another possible workaround? > > Without knowing what the underlying issue is it is hard to predict > whether it will also affect ovs. > Agreed. > > > My config:- > > Looks correct to me. > > Ian. > Thanks Ian. --f46d043c816caa623e04d5fe3164 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
On 18 February 2013 12:50, Ian Campbell = <ijc@hellion.org= .uk> wrote:
On Mon, 2013-02-18 at 12:04 +0200, Gavin wrote:


> Firstly I apologise for the cross-post,

I've added xen-users since you also bounced this there.

Thanks. :-/ =A0Thanks too for your quick r= eply.

> =A0however I don't expect to get as quick a response from the pack= age
> maintainers as I do from the Debian community, and this issue affects<= br> > a service that I've got scheduled to go live at midnight this
> evening. :(
>
>
> A recent update from xen-hypervisor-4.1-amd64 version 4.1.3-7, to
> version 4.1.3-8 on Debian Wheezy has caused all vm's on this host = to
> not receive their arp replies anymore and as such they cannot reach > their gateways and are now isolated from the network.
>
>
> There was a more recent update as well (4.1.4-2) which I have now
> since applied however this particular issue persists.

Networking level stuff is all done by the dom0 (or driver domain) ker= nel
rather than the hypervisor so it is far more likely that a kernel level
change rather than a hypervisor change would be responsible. What kernel version are you running? Did it also change?

This makes sense, although when I did the apt-get upgrade, ther= e was no kernel update, however there may have been packages/drivers that r= equired a kernel mod.

Here is the apt history which details what = was upgraded when this broke:-

Upgrade: dnsm= asq-base:amd64 (2.62-3, 2.62-3+deb7u1), tasksel-data:amd64 (3.14, 3.14+nmu1= ), xen-hypervisor-4.1-amd64:amd64 (4.1.3-7, 4.1.3-8), xen-utils-common:amd6= 4 (4.1.3-7, 4.1.3-8), perl:amd64 (5.14.2-16, 5.14.2-17), firmware-linux-fre= e:amd64 (3.1, 3.2), perl-base:amd64 (5.14.2-16, 5.14.2-17), xen-utils-4.1:a= md64 (4.1.3-7, 4.1.3-8), libgnutls26:amd64 (2.12.20-2, 2.12.20-4), perl-mod= ules:amd64 (5.14.2-16, 5.14.2-17), psmisc:amd64 (22.19-1, 22.19-1+deb7u1), = python2.6:amd64 (2.6.8-0.2, 2.6.8-1.1), libxenstore3.0:amd64 (4.1.3-7, 4.1.= 3-8), python2.6-minimal:amd64 (2.6.8-0.2, 2.6.8-1.1), coreutils:amd64 (8.13= -3.4, 8.13-3.5), libvirt0:amd64 (0.9.12-5, 0.9.12-6), libcurl3:amd64 (7.26.= 0-1, 7.26.0-1+wheezy1), manpages:amd64 (3.42-1, 3.44-1), tasksel:amd64 (3.1= 4, 3.14+nmu1), libperl5.14:amd64 (5.14.2-16, 5.14.2-17), libsystemd-login0:= amd64 (44-7, 44-8), libxen-4.1:amd64 (4.1.3-7, 4.1.3-8), libcurl3-gnutls:am= d64 (7.26.0-1, 7.26.0-1+wheezy1), host:amd64 (9.8.4.dfsg.P1-1, 9.8.4.dfsg.P= 1-4), libvirt-bin:amd64 (0.9.12-5, 0.9.12-6), rinse:amd64 (2.0-1, 2.0.1-1),= ca-certificates:amd64 (20120623, 20130119), xenstore-utils:amd64 (4.1.3-7,= 4.1.3-8)

The kernel I am using is:=A03.2.0-2-amd64, also t= ried 3.2.0-4-amd64 on another host with no success.
=A0
Would the upgrade above of xen-hypervisor-4.1-amd64 on this De= bian system not cause the Dom0 kernel to be changed in any way ??=A0
=A0
> The arp replies are received by the host and passed all the way up to<= br> > the bridge (br200) being used by Xen, however they are not seen on the=
> vif (vif2.0) created for the particular vm.

Do you have any firewall or ebfilter entries which might have either<= br> been discarded or reintroduced by the reboot? (i.e. a manual settings
modification which wasn't propagated to the startup scripts). Or perhap= s
sysctl tweaks?

Nope, not using ip= tables/ebtables, this was working 100% until the apt upgrade above.

After this broke I did try and add the follow= ing to /etc/sysctl.conf but it made no difference:-

net.bridge.bridge-nf-call-ip6tables = =3D 0
net.bridge.bridge-nf-call-iptables =3D 0
net.brid= ge.bridge-nf-call-arptables =3D 0

It did add= iptables rules but made no difference to this issue.
=A0

> 1) Please let me know if I should roll-back this particular xen
> update, kernel and all, and what those steps may be, or if this is a > known issue with a particular workaround that I can apply.

I'd certainly be tempted to try the older kernel, assuming that w= as also
upgraded. It may even still be installed and in your grub menu already.
=

The problem is now we are using grub= 2 and it appears that on boot grub loads a Linux menu, then the Xen Menu wi= th configs in /etc/grub.d/ so I'm battling to figure out how to do this= .

I also do not have physical access to this = host at the moment so need to set the boot order 'correctly' prior = to a reboot.

> 2) Would moving to openvswitch be another possible workaround?

Without knowing what the underlying issue is it is hard to predict whether it will also affect ovs.

= Agreed.=A0

> My config:-

Looks correct to me.

Ian.

Thanks Ian.=A0=

=A0

--f46d043c816caa623e04d5fe3164-- --===============7515223315650177198== 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 --===============7515223315650177198==-- From xen-users-bounces@lists.xen.org Mon Feb 18 11:48:24 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 18 Feb 2013 11:48: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 1U7PC5-0000nj-7O; Mon, 18 Feb 2013 11:47:37 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U7PC3-0000ne-6k for xen-users@lists.xen.org; Mon, 18 Feb 2013 11:47:35 +0000 Received: from [85.158.143.99:51972] by server-3.bemta-4.messagelabs.com id F8/3F-08920-6D412215; Mon, 18 Feb 2013 11:47:34 +0000 X-Env-Sender: jonas@freesources.org X-Msg-Ref: server-14.tower-216.messagelabs.com!1361188039!18360600!1 X-Originating-IP: [80.237.252.132] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 13180 invoked from network); 18 Feb 2013 11:47:19 -0000 Received: from mx01.freesources.org (HELO mail01.freesources.org) (80.237.252.132) by server-14.tower-216.messagelabs.com with AES256-SHA encrypted SMTP; 18 Feb 2013 11:47:19 -0000 Received: from secure.freesources.org ([80.237.252.133]) by mail01.freesources.org with esmtpsa (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.72) (envelope-from ) id 1U7PBj-0001yT-E4 for xen-users@lists.xen.org; Mon, 18 Feb 2013 11:47:18 +0000 MIME-Version: 1.0 Date: Mon, 18 Feb 2013 12:47:15 +0100 From: Jonas Meurer To: Message-ID: X-Sender: jonas@freesources.org User-Agent: Roundcube Webmail/0.7.1 X-SA-Exim-Connect-IP: 80.237.252.133 X-SA-Exim-Mail-From: jonas@freesources.org X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on mail01.freesources.org X-Spam-Level: X-Spam-Status: No, score=-3.5 required=5.0 tests=ALL_TRUSTED,BAYES_00, RP_MATCHES_RCVD autolearn=ham version=3.3.1 X-SA-Exim-Version: 4.2.1 (built Mon, 22 Mar 2010 06:26:47 +0000) X-SA-Exim-Scanned: Yes (on mail01.freesources.org) Subject: [Xen-users] Question regarding xen networking (bonding, xen-bridging) X-BeenThere: xen-users@lists.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 fail to fully understand the xen bridge networking concept. In particular, the relation between bonding, bridging and Vlans is not clear to me. I have to admit that I'm not a network/bridging/routing expert at all. I'll try to explain setup and problem in detail. Please apologize if anything sounds illegitimate or absurd to you, or if I missed important information. My system is a Debian/Wheezy Usually, we use a setup with different Vlan tags for each domU. Eth0/bond0 on the dom0 are untagged. For every domU, we create a interface 'vlanXXX' with eth0/bond0 as raw device, and a bridge 'brXXX' with the vlan interface as bridge port. brXXX is the bridge used for the domU: auto vlanXXX iface vlanXXX inet manual vlan_raw_device bond0 auto brXXX iface brXXX inet manual bridge_ports vlanXXX bridge_stp off bridge_fd 0 This works quite well. But now I tried (and until now failed) to setup a Xen host with bridging, and dom0 + domUs in the same network (no Vlan management on dom0). After quite some time I got it working half the way. The bond0 device is set up as manual, and a bridge 'xenbr0' is created with interface 'bond0' as bridge port. The domU uses 'xenbr0' as bridge: On the dom0 LAN connection works as expected. Gateway responds, connection to the internet works. Dom0 and domU see each other. But from domU, everything beyond the dom0 is unreachable, e.g. the gateway doesn't respond. MAC address from the domU is propagated to switches and gateway, I can see it in the arp table. In other words, the packets from domU find their way out, but the responding packets don't find their way back. A quick look at the iptables rules on dom0 give me the impression, that dom0 doesn't know how to handle packets for domU: # iptables -L FORWARD Chain FORWARD (policy ACCEPT) target prot opt source destination ACCEPT all -- anywhere anywhere PHYSDEV match --physdev-out vif1.0 --physdev-is-bridged ACCEPT udp -- anywhere anywhere PHYSDEV match --physdev-in vif1.0 --physdev-is-bridged udp spt:bootpc dpt:bootps ACCEPT all -- anywhere anywhere PHYSDEV match --physdev-out vif1.0 --physdev-is-bridged ACCEPT all -- anywhere PHYSDEV match --physdev-in vif1.0 --physdev-is-bridged The last rule seems to accept packets with domU-IP as source, but I cannot find a rule which handles incoming packets for domU. In other words, the dom0 doesn't know what to do with packets for the domU. Is my assumption correct? If yes, why is this the case? Is it related to interface bonding? I don't get the picture, maybe you can help me :) Kind regards, jonas _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Mon Feb 18 11:48:24 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 18 Feb 2013 11:48: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 1U7PC5-0000nj-7O; Mon, 18 Feb 2013 11:47:37 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U7PC3-0000ne-6k for xen-users@lists.xen.org; Mon, 18 Feb 2013 11:47:35 +0000 Received: from [85.158.143.99:51972] by server-3.bemta-4.messagelabs.com id F8/3F-08920-6D412215; Mon, 18 Feb 2013 11:47:34 +0000 X-Env-Sender: jonas@freesources.org X-Msg-Ref: server-14.tower-216.messagelabs.com!1361188039!18360600!1 X-Originating-IP: [80.237.252.132] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 13180 invoked from network); 18 Feb 2013 11:47:19 -0000 Received: from mx01.freesources.org (HELO mail01.freesources.org) (80.237.252.132) by server-14.tower-216.messagelabs.com with AES256-SHA encrypted SMTP; 18 Feb 2013 11:47:19 -0000 Received: from secure.freesources.org ([80.237.252.133]) by mail01.freesources.org with esmtpsa (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.72) (envelope-from ) id 1U7PBj-0001yT-E4 for xen-users@lists.xen.org; Mon, 18 Feb 2013 11:47:18 +0000 MIME-Version: 1.0 Date: Mon, 18 Feb 2013 12:47:15 +0100 From: Jonas Meurer To: Message-ID: X-Sender: jonas@freesources.org User-Agent: Roundcube Webmail/0.7.1 X-SA-Exim-Connect-IP: 80.237.252.133 X-SA-Exim-Mail-From: jonas@freesources.org X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on mail01.freesources.org X-Spam-Level: X-Spam-Status: No, score=-3.5 required=5.0 tests=ALL_TRUSTED,BAYES_00, RP_MATCHES_RCVD autolearn=ham version=3.3.1 X-SA-Exim-Version: 4.2.1 (built Mon, 22 Mar 2010 06:26:47 +0000) X-SA-Exim-Scanned: Yes (on mail01.freesources.org) Subject: [Xen-users] Question regarding xen networking (bonding, xen-bridging) X-BeenThere: xen-users@lists.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 fail to fully understand the xen bridge networking concept. In particular, the relation between bonding, bridging and Vlans is not clear to me. I have to admit that I'm not a network/bridging/routing expert at all. I'll try to explain setup and problem in detail. Please apologize if anything sounds illegitimate or absurd to you, or if I missed important information. My system is a Debian/Wheezy Usually, we use a setup with different Vlan tags for each domU. Eth0/bond0 on the dom0 are untagged. For every domU, we create a interface 'vlanXXX' with eth0/bond0 as raw device, and a bridge 'brXXX' with the vlan interface as bridge port. brXXX is the bridge used for the domU: auto vlanXXX iface vlanXXX inet manual vlan_raw_device bond0 auto brXXX iface brXXX inet manual bridge_ports vlanXXX bridge_stp off bridge_fd 0 This works quite well. But now I tried (and until now failed) to setup a Xen host with bridging, and dom0 + domUs in the same network (no Vlan management on dom0). After quite some time I got it working half the way. The bond0 device is set up as manual, and a bridge 'xenbr0' is created with interface 'bond0' as bridge port. The domU uses 'xenbr0' as bridge: On the dom0 LAN connection works as expected. Gateway responds, connection to the internet works. Dom0 and domU see each other. But from domU, everything beyond the dom0 is unreachable, e.g. the gateway doesn't respond. MAC address from the domU is propagated to switches and gateway, I can see it in the arp table. In other words, the packets from domU find their way out, but the responding packets don't find their way back. A quick look at the iptables rules on dom0 give me the impression, that dom0 doesn't know how to handle packets for domU: # iptables -L FORWARD Chain FORWARD (policy ACCEPT) target prot opt source destination ACCEPT all -- anywhere anywhere PHYSDEV match --physdev-out vif1.0 --physdev-is-bridged ACCEPT udp -- anywhere anywhere PHYSDEV match --physdev-in vif1.0 --physdev-is-bridged udp spt:bootpc dpt:bootps ACCEPT all -- anywhere anywhere PHYSDEV match --physdev-out vif1.0 --physdev-is-bridged ACCEPT all -- anywhere PHYSDEV match --physdev-in vif1.0 --physdev-is-bridged The last rule seems to accept packets with domU-IP as source, but I cannot find a rule which handles incoming packets for domU. In other words, the dom0 doesn't know what to do with packets for the domU. Is my assumption correct? If yes, why is this the case? Is it related to interface bonding? I don't get the picture, maybe you can help me :) Kind regards, jonas _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Mon Feb 18 12:00:43 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 18 Feb 2013 12:00: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 1U7PO3-0001Eh-QK; Mon, 18 Feb 2013 11:59:59 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U7PO2-0001Ea-5o for xen-users@lists.xen.org; Mon, 18 Feb 2013 11:59:58 +0000 Received: from [85.158.143.35:6858] by server-3.bemta-4.messagelabs.com id 84/71-08920-DB712215; Mon, 18 Feb 2013 11:59:57 +0000 X-Env-Sender: juliofong@mail.com X-Msg-Ref: server-7.tower-21.messagelabs.com!1361188666!11662649!1 X-Originating-IP: [74.208.4.200] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNzQuMjA4LjQuMjAwID0+IDQ5MTc=\n, ML_RADAR_SPEW_LINKS_14, spamassassin: X-StarScan-Received: X-StarScan-Version: 6.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 10688 invoked from network); 18 Feb 2013 11:57:46 -0000 Received: from mout.gmx.net (HELO mout.gmx.net) (74.208.4.200) by server-7.tower-21.messagelabs.com with SMTP; 18 Feb 2013 11:57:46 -0000 Received: from mailout-us.gmx.com ([172.19.198.46]) by mrigmx.server.lan (mrigmxus001) with ESMTP (Nemesis) id 0MVvAq-1UMtxC0DPs-00X6uj for ; Mon, 18 Feb 2013 12:57:46 +0100 Received: (qmail 17335 invoked by uid 0); 18 Feb 2013 11:57:45 -0000 Received: from 86.66.222.237 by rms-us016 with HTTP Date: Mon, 18 Feb 2013 06:57:42 -0500 From: "FONG Julio" Message-ID: <20130218115743.198660@gmx.com> MIME-Version: 1.0 To: xen-users@lists.xen.org X-Authenticated: #76551402 X-Flags: 0001 X-Mailer: GMX.com Web Mailer x-registered: 0 X-GMX-UID: YHJQcf4s3zOlO4t3+3Ahtfd+IGRvb8C4 Subject: [Xen-users] Please question about xenstore X-BeenThere: xen-users@lists.xen.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="===============3270274893395739554==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============3270274893395739554== Content-Type: multipart/alternative; boundary="========GMXBoundary198661361188663139448" --========GMXBoundary198661361188663139448 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit Hello, I would like guests be able to communicate with host using xenstore. Do you have any idea how can I install xenstore-utils from source? Julio --========GMXBoundary198661361188663139448 Content-Type: text/html; charset="utf-8" Content-Transfer-Encoding: quoted-printable Hello,
I would like guests be able to communicate with host using xensto= re.
Do you have any idea how can I install xenstore-utils from source?=

Julio --========GMXBoundary198661361188663139448-- --===============3270274893395739554== 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 --===============3270274893395739554==-- From xen-users-bounces@lists.xen.org Mon Feb 18 12:00:43 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 18 Feb 2013 12:00: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 1U7PO3-0001Eh-QK; Mon, 18 Feb 2013 11:59:59 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U7PO2-0001Ea-5o for xen-users@lists.xen.org; Mon, 18 Feb 2013 11:59:58 +0000 Received: from [85.158.143.35:6858] by server-3.bemta-4.messagelabs.com id 84/71-08920-DB712215; Mon, 18 Feb 2013 11:59:57 +0000 X-Env-Sender: juliofong@mail.com X-Msg-Ref: server-7.tower-21.messagelabs.com!1361188666!11662649!1 X-Originating-IP: [74.208.4.200] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNzQuMjA4LjQuMjAwID0+IDQ5MTc=\n, ML_RADAR_SPEW_LINKS_14, spamassassin: X-StarScan-Received: X-StarScan-Version: 6.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 10688 invoked from network); 18 Feb 2013 11:57:46 -0000 Received: from mout.gmx.net (HELO mout.gmx.net) (74.208.4.200) by server-7.tower-21.messagelabs.com with SMTP; 18 Feb 2013 11:57:46 -0000 Received: from mailout-us.gmx.com ([172.19.198.46]) by mrigmx.server.lan (mrigmxus001) with ESMTP (Nemesis) id 0MVvAq-1UMtxC0DPs-00X6uj for ; Mon, 18 Feb 2013 12:57:46 +0100 Received: (qmail 17335 invoked by uid 0); 18 Feb 2013 11:57:45 -0000 Received: from 86.66.222.237 by rms-us016 with HTTP Date: Mon, 18 Feb 2013 06:57:42 -0500 From: "FONG Julio" Message-ID: <20130218115743.198660@gmx.com> MIME-Version: 1.0 To: xen-users@lists.xen.org X-Authenticated: #76551402 X-Flags: 0001 X-Mailer: GMX.com Web Mailer x-registered: 0 X-GMX-UID: YHJQcf4s3zOlO4t3+3Ahtfd+IGRvb8C4 Subject: [Xen-users] Please question about xenstore X-BeenThere: xen-users@lists.xen.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="===============3270274893395739554==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============3270274893395739554== Content-Type: multipart/alternative; boundary="========GMXBoundary198661361188663139448" --========GMXBoundary198661361188663139448 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit Hello, I would like guests be able to communicate with host using xenstore. Do you have any idea how can I install xenstore-utils from source? Julio --========GMXBoundary198661361188663139448 Content-Type: text/html; charset="utf-8" Content-Transfer-Encoding: quoted-printable Hello,
I would like guests be able to communicate with host using xensto= re.
Do you have any idea how can I install xenstore-utils from source?=

Julio --========GMXBoundary198661361188663139448-- --===============3270274893395739554== 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 --===============3270274893395739554==-- From xen-users-bounces@lists.xen.org Mon Feb 18 12:11:54 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 18 Feb 2013 12: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 1U7PYw-0001pD-03; Mon, 18 Feb 2013 12:11:14 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U7PYu-0001p0-Ss for xen-users@lists.xen.org; Mon, 18 Feb 2013 12:11:13 +0000 Received: from [85.158.143.35:35803] by server-1.bemta-4.messagelabs.com id CC/CF-08839-06A12215; Mon, 18 Feb 2013 12:11:12 +0000 X-Env-Sender: J.Witvliet@mindef.nl X-Msg-Ref: server-13.tower-21.messagelabs.com!1361189470!14420781!1 X-Originating-IP: [217.169.229.21] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogMjE3LjE2OS4yMjkuMjEgPT4gMTE4NDY0\n X-StarScan-Received: X-StarScan-Version: 6.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 16706 invoked from network); 18 Feb 2013 12:11:10 -0000 Received: from mx4-out.mindef.nl (HELO mx4-out.mindef.nl) (217.169.229.21) by server-13.tower-21.messagelabs.com with SMTP; 18 Feb 2013 12:11:10 -0000 Received: from somewhere by someone Received: from somewhere by someone Received: from somewhere by someone Received: from somewhere by someone Received: from somewhere by someone From: To: Date: Mon, 18 Feb 2013 13:10:54 +0100 Accept-Language: en-US, nl-NL Content-Language: en-US x-cr-puzzleid: {1C2608C9-1B97-49FC-ABF9-15692799F611} x-cr-hashedpuzzle: A/DU Eo34 F3w+ GGeU HQyv Hxk1 H77J JCLM NQJI OTE+ Pm/W Pncc RrV1 WLsE XL4J Y9MG; 2; aAB3AGkAdABAAGEALQBkAG8AbQBhAG4AaQAuAG4AbAA7AHgAZQBuAC0AdQBzAGUAcgBzAEAAbABpAHMAdABzAC4AeABlAG4ALgBvAHIAZwA=; Sosha1_v1; 7; {1C2608C9-1B97-49FC-ABF9-15692799F611}; agAuAHcAaQB0AHYAbABpAGUAdABAAG0AaQBuAGQAZQBmAC4AbgBsAA==; Mon, 18 Feb 2013 12:10:54 GMT;QQBFAFMA acceptlanguage: en-US, nl-NL MIME-Version: 1.0 Message-Id: <20130218121109.877C921DD02@mx4-out.mindef.nl> Cc: hwit@a-domani.nl Subject: [Xen-users] AES X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: 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, Just read that someone was doing performance test on openvpn. He wrote that he could get a performance boost, by using the AES-NI capabilities of modern CPU's. So I was wondering, what would happen when doing such tests when running openvpn virtualized.. Would there be any difference between PV-guests and HW-guests? Or are these extensions only available when running directly on the bare metal? Hans ______________________________________________________________________ Dit bericht kan informatie bevatten die niet voor u is bestemd. Indien u niet de geadresseerde bent of dit bericht abusievelijk aan u is toegezonden, word u verzocht dat aan de afzender te melden en het bericht te verwijderen. De Staat aanvaardt geen aansprakelijkheid voor schade, van welke aard ook, die verband houdt met risico's verbonden aan het electronisch verzenden van berichten. This message may contain information that is not intended for you. If you are not the addressee or if this message was sent to you by mistake, you are requested to inform the sender and delete the message. The State accepts no liability for damage of any kind resulting from the risks inherent in the electronic transmission of messages. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Mon Feb 18 12:11:54 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 18 Feb 2013 12: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 1U7PYw-0001pD-03; Mon, 18 Feb 2013 12:11:14 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U7PYu-0001p0-Ss for xen-users@lists.xen.org; Mon, 18 Feb 2013 12:11:13 +0000 Received: from [85.158.143.35:35803] by server-1.bemta-4.messagelabs.com id CC/CF-08839-06A12215; Mon, 18 Feb 2013 12:11:12 +0000 X-Env-Sender: J.Witvliet@mindef.nl X-Msg-Ref: server-13.tower-21.messagelabs.com!1361189470!14420781!1 X-Originating-IP: [217.169.229.21] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogMjE3LjE2OS4yMjkuMjEgPT4gMTE4NDY0\n X-StarScan-Received: X-StarScan-Version: 6.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 16706 invoked from network); 18 Feb 2013 12:11:10 -0000 Received: from mx4-out.mindef.nl (HELO mx4-out.mindef.nl) (217.169.229.21) by server-13.tower-21.messagelabs.com with SMTP; 18 Feb 2013 12:11:10 -0000 Received: from somewhere by someone Received: from somewhere by someone Received: from somewhere by someone Received: from somewhere by someone Received: from somewhere by someone From: To: Date: Mon, 18 Feb 2013 13:10:54 +0100 Accept-Language: en-US, nl-NL Content-Language: en-US x-cr-puzzleid: {1C2608C9-1B97-49FC-ABF9-15692799F611} x-cr-hashedpuzzle: A/DU Eo34 F3w+ GGeU HQyv Hxk1 H77J JCLM NQJI OTE+ Pm/W Pncc RrV1 WLsE XL4J Y9MG; 2; aAB3AGkAdABAAGEALQBkAG8AbQBhAG4AaQAuAG4AbAA7AHgAZQBuAC0AdQBzAGUAcgBzAEAAbABpAHMAdABzAC4AeABlAG4ALgBvAHIAZwA=; Sosha1_v1; 7; {1C2608C9-1B97-49FC-ABF9-15692799F611}; agAuAHcAaQB0AHYAbABpAGUAdABAAG0AaQBuAGQAZQBmAC4AbgBsAA==; Mon, 18 Feb 2013 12:10:54 GMT;QQBFAFMA acceptlanguage: en-US, nl-NL MIME-Version: 1.0 Message-Id: <20130218121109.877C921DD02@mx4-out.mindef.nl> Cc: hwit@a-domani.nl Subject: [Xen-users] AES X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: 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, Just read that someone was doing performance test on openvpn. He wrote that he could get a performance boost, by using the AES-NI capabilities of modern CPU's. So I was wondering, what would happen when doing such tests when running openvpn virtualized.. Would there be any difference between PV-guests and HW-guests? Or are these extensions only available when running directly on the bare metal? Hans ______________________________________________________________________ Dit bericht kan informatie bevatten die niet voor u is bestemd. Indien u niet de geadresseerde bent of dit bericht abusievelijk aan u is toegezonden, word u verzocht dat aan de afzender te melden en het bericht te verwijderen. De Staat aanvaardt geen aansprakelijkheid voor schade, van welke aard ook, die verband houdt met risico's verbonden aan het electronisch verzenden van berichten. This message may contain information that is not intended for you. If you are not the addressee or if this message was sent to you by mistake, you are requested to inform the sender and delete the message. The State accepts no liability for damage of any kind resulting from the risks inherent in the electronic transmission of messages. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Mon Feb 18 12:12:18 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 18 Feb 2013 12:12: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 1U7PZN-0001tE-PO; Mon, 18 Feb 2013 12:11:41 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U7PZM-0001sm-0K for xen-users@lists.xen.org; Mon, 18 Feb 2013 12:11:40 +0000 Received: from [85.158.138.51:46088] by server-14.bemta-3.messagelabs.com id 63/0B-23533-B7A12215; Mon, 18 Feb 2013 12:11:39 +0000 X-Env-Sender: wei.liu2@citrix.com X-Msg-Ref: server-4.tower-174.messagelabs.com!1361189497!27968554!1 X-Originating-IP: [66.165.176.63] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjYuMTY1LjE3Ni42MyA9PiAzMDMwNjE=\n X-StarScan-Received: X-StarScan-Version: 6.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 2414 invoked from network); 18 Feb 2013 12:11:38 -0000 Received: from smtp02.citrix.com (HELO SMTP02.CITRIX.COM) (66.165.176.63) by server-4.tower-174.messagelabs.com with RC4-SHA encrypted SMTP; 18 Feb 2013 12:11:38 -0000 X-IronPort-AV: E=Sophos;i="4.84,687,1355097600"; d="scan'208";a="7589413" Received: from accessns.citrite.net (HELO FTLPEX01CL01.citrite.net) ([10.9.154.239]) by FTLPIPO02.CITRIX.COM with ESMTP/TLS/AES128-SHA; 18 Feb 2013 12:11:36 +0000 Received: from ukmail1.uk.xensource.com (10.80.16.128) by smtprelay.citrix.com (10.13.107.78) with Microsoft SMTP Server id 14.2.318.1; Mon, 18 Feb 2013 07:11:36 -0500 Received: from zion.uk.xensource.com ([10.80.2.73]) by ukmail1.uk.xensource.com with esmtp (Exim 4.69) (envelope-from ) id 1U7PZI-0001JT-0o; Mon, 18 Feb 2013 12:11:36 +0000 Message-ID: <1361189496.3825.1.camel@zion.uk.xensource.com> From: Wei Liu To: FONG Julio Date: Mon, 18 Feb 2013 12:11:36 +0000 In-Reply-To: <20130218115743.198660@gmx.com> References: <20130218115743.198660@gmx.com> X-Mailer: Evolution 3.6.2 (3.6.2-3.fc18) MIME-Version: 1.0 Cc: "xen-users@lists.xen.org" , wei.liu2@citrix.com Subject: Re: [Xen-users] Please question about xenstore X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: 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, 2013-02-18 at 11:57 +0000, FONG Julio wrote: > Hello, > > I would like guests be able to communicate with host using xenstore. > Do you have any idea how can I install xenstore-utils from source? > > Julio Just download Xen source and `cd xen_source_dir; ./configure; cd tools/xenstore; make; make install`, this will install xenstore-utils in your Dom0. Wei. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Mon Feb 18 12:12:18 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 18 Feb 2013 12:12: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 1U7PZN-0001tE-PO; Mon, 18 Feb 2013 12:11:41 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U7PZM-0001sm-0K for xen-users@lists.xen.org; Mon, 18 Feb 2013 12:11:40 +0000 Received: from [85.158.138.51:46088] by server-14.bemta-3.messagelabs.com id 63/0B-23533-B7A12215; Mon, 18 Feb 2013 12:11:39 +0000 X-Env-Sender: wei.liu2@citrix.com X-Msg-Ref: server-4.tower-174.messagelabs.com!1361189497!27968554!1 X-Originating-IP: [66.165.176.63] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjYuMTY1LjE3Ni42MyA9PiAzMDMwNjE=\n X-StarScan-Received: X-StarScan-Version: 6.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 2414 invoked from network); 18 Feb 2013 12:11:38 -0000 Received: from smtp02.citrix.com (HELO SMTP02.CITRIX.COM) (66.165.176.63) by server-4.tower-174.messagelabs.com with RC4-SHA encrypted SMTP; 18 Feb 2013 12:11:38 -0000 X-IronPort-AV: E=Sophos;i="4.84,687,1355097600"; d="scan'208";a="7589413" Received: from accessns.citrite.net (HELO FTLPEX01CL01.citrite.net) ([10.9.154.239]) by FTLPIPO02.CITRIX.COM with ESMTP/TLS/AES128-SHA; 18 Feb 2013 12:11:36 +0000 Received: from ukmail1.uk.xensource.com (10.80.16.128) by smtprelay.citrix.com (10.13.107.78) with Microsoft SMTP Server id 14.2.318.1; Mon, 18 Feb 2013 07:11:36 -0500 Received: from zion.uk.xensource.com ([10.80.2.73]) by ukmail1.uk.xensource.com with esmtp (Exim 4.69) (envelope-from ) id 1U7PZI-0001JT-0o; Mon, 18 Feb 2013 12:11:36 +0000 Message-ID: <1361189496.3825.1.camel@zion.uk.xensource.com> From: Wei Liu To: FONG Julio Date: Mon, 18 Feb 2013 12:11:36 +0000 In-Reply-To: <20130218115743.198660@gmx.com> References: <20130218115743.198660@gmx.com> X-Mailer: Evolution 3.6.2 (3.6.2-3.fc18) MIME-Version: 1.0 Cc: "xen-users@lists.xen.org" , wei.liu2@citrix.com Subject: Re: [Xen-users] Please question about xenstore X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: 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, 2013-02-18 at 11:57 +0000, FONG Julio wrote: > Hello, > > I would like guests be able to communicate with host using xenstore. > Do you have any idea how can I install xenstore-utils from source? > > Julio Just download Xen source and `cd xen_source_dir; ./configure; cd tools/xenstore; make; make install`, this will install xenstore-utils in your Dom0. Wei. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Mon Feb 18 12:26:58 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 18 Feb 2013 12:26: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 1U7Pna-0002mT-75; Mon, 18 Feb 2013 12:26:22 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U7OIg-0005di-Sj for xen-users@lists.xen.org; Mon, 18 Feb 2013 10:50:23 +0000 Received: from [85.158.138.51:52549] by server-13.bemta-3.messagelabs.com id B9/6C-20653-E6702215; Mon, 18 Feb 2013 10:50:22 +0000 X-Env-Sender: ijc@hellion.org.uk X-Msg-Ref: server-7.tower-174.messagelabs.com!1361184612!19090516!1 X-Originating-IP: [212.110.190.137] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 2440 invoked from network); 18 Feb 2013 10:50:13 -0000 Received: from benson.vm.bytemark.co.uk (HELO benson.vm.bytemark.co.uk) (212.110.190.137) by server-7.tower-174.messagelabs.com with AES256-SHA encrypted SMTP; 18 Feb 2013 10:50:13 -0000 Received: from cpc22-cmbg14-2-0-cust482.5-4.cable.virginmedia.com ([86.6.25.227] helo=hopkins.hellion.org.uk) by benson.vm.bytemark.co.uk with esmtpsa (TLS1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.72) (envelope-from ) id 1U7OIU-0000ic-6G; Mon, 18 Feb 2013 10:50:10 +0000 Received: from firewall.ctxuk.citrix.com ([46.33.159.2] helo=[10.80.2.42]) by hopkins.hellion.org.uk with esmtpsa (SSL3.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.72) (envelope-from ) id 1U7OIR-0004Hn-84; Mon, 18 Feb 2013 10:50:09 +0000 Message-ID: <1361184601.31407.144.camel@zakaz.uk.xensource.com> From: Ian Campbell To: Gavin Date: Mon, 18 Feb 2013 10:50:01 +0000 In-Reply-To: References: X-Mailer: Evolution 3.4.4-1 Mime-Version: 1.0 X-SA-Exim-Connect-IP: 46.33.159.2 X-SA-Exim-Mail-From: ijc@hellion.org.uk X-SA-Exim-Version: 4.2.1 (built Mon, 22 Mar 2010 06:51:10 +0000) X-SA-Exim-Scanned: Yes (on hopkins.hellion.org.uk) X-Mailman-Approved-At: Mon, 18 Feb 2013 12:26:20 +0000 Cc: pkg-xen-devel@lists.alioth.debian.org, xen-users , debian-user@lists.debian.org Subject: Re: [Xen-users] [Pkg-xen-devel] Recent hypervisor update on Debian Wheezy breaks domU 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 Mon, 2013-02-18 at 12:04 +0200, Gavin wrote: > Firstly I apologise for the cross-post, I've added xen-users since you also bounced this there. > however I don't expect to get as quick a response from the package > maintainers as I do from the Debian community, and this issue affects > a service that I've got scheduled to go live at midnight this > evening. :( > > > A recent update from xen-hypervisor-4.1-amd64 version 4.1.3-7, to > version 4.1.3-8 on Debian Wheezy has caused all vm's on this host to > not receive their arp replies anymore and as such they cannot reach > their gateways and are now isolated from the network. > > > There was a more recent update as well (4.1.4-2) which I have now > since applied however this particular issue persists. Networking level stuff is all done by the dom0 (or driver domain) kernel rather than the hypervisor so it is far more likely that a kernel level change rather than a hypervisor change would be responsible. What kernel version are you running? Did it also change? > The arp replies are received by the host and passed all the way up to > the bridge (br200) being used by Xen, however they are not seen on the > vif (vif2.0) created for the particular vm. Do you have any firewall or ebfilter entries which might have either been discarded or reintroduced by the reboot? (i.e. a manual settings modification which wasn't propagated to the startup scripts). Or perhaps sysctl tweaks? > 1) Please let me know if I should roll-back this particular xen > update, kernel and all, and what those steps may be, or if this is a > known issue with a particular workaround that I can apply. I'd certainly be tempted to try the older kernel, assuming that was also upgraded. It may even still be installed and in your grub menu already. > 2) Would moving to openvswitch be another possible workaround? Without knowing what the underlying issue is it is hard to predict whether it will also affect ovs. > My config:- Looks correct to me. Ian. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Mon Feb 18 12:26:58 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 18 Feb 2013 12:26: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 1U7Pna-0002mT-75; Mon, 18 Feb 2013 12:26:22 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U7OIg-0005di-Sj for xen-users@lists.xen.org; Mon, 18 Feb 2013 10:50:23 +0000 Received: from [85.158.138.51:52549] by server-13.bemta-3.messagelabs.com id B9/6C-20653-E6702215; Mon, 18 Feb 2013 10:50:22 +0000 X-Env-Sender: ijc@hellion.org.uk X-Msg-Ref: server-7.tower-174.messagelabs.com!1361184612!19090516!1 X-Originating-IP: [212.110.190.137] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 2440 invoked from network); 18 Feb 2013 10:50:13 -0000 Received: from benson.vm.bytemark.co.uk (HELO benson.vm.bytemark.co.uk) (212.110.190.137) by server-7.tower-174.messagelabs.com with AES256-SHA encrypted SMTP; 18 Feb 2013 10:50:13 -0000 Received: from cpc22-cmbg14-2-0-cust482.5-4.cable.virginmedia.com ([86.6.25.227] helo=hopkins.hellion.org.uk) by benson.vm.bytemark.co.uk with esmtpsa (TLS1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.72) (envelope-from ) id 1U7OIU-0000ic-6G; Mon, 18 Feb 2013 10:50:10 +0000 Received: from firewall.ctxuk.citrix.com ([46.33.159.2] helo=[10.80.2.42]) by hopkins.hellion.org.uk with esmtpsa (SSL3.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.72) (envelope-from ) id 1U7OIR-0004Hn-84; Mon, 18 Feb 2013 10:50:09 +0000 Message-ID: <1361184601.31407.144.camel@zakaz.uk.xensource.com> From: Ian Campbell To: Gavin Date: Mon, 18 Feb 2013 10:50:01 +0000 In-Reply-To: References: X-Mailer: Evolution 3.4.4-1 Mime-Version: 1.0 X-SA-Exim-Connect-IP: 46.33.159.2 X-SA-Exim-Mail-From: ijc@hellion.org.uk X-SA-Exim-Version: 4.2.1 (built Mon, 22 Mar 2010 06:51:10 +0000) X-SA-Exim-Scanned: Yes (on hopkins.hellion.org.uk) X-Mailman-Approved-At: Mon, 18 Feb 2013 12:26:20 +0000 Cc: pkg-xen-devel@lists.alioth.debian.org, xen-users , debian-user@lists.debian.org Subject: Re: [Xen-users] [Pkg-xen-devel] Recent hypervisor update on Debian Wheezy breaks domU 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 Mon, 2013-02-18 at 12:04 +0200, Gavin wrote: > Firstly I apologise for the cross-post, I've added xen-users since you also bounced this there. > however I don't expect to get as quick a response from the package > maintainers as I do from the Debian community, and this issue affects > a service that I've got scheduled to go live at midnight this > evening. :( > > > A recent update from xen-hypervisor-4.1-amd64 version 4.1.3-7, to > version 4.1.3-8 on Debian Wheezy has caused all vm's on this host to > not receive their arp replies anymore and as such they cannot reach > their gateways and are now isolated from the network. > > > There was a more recent update as well (4.1.4-2) which I have now > since applied however this particular issue persists. Networking level stuff is all done by the dom0 (or driver domain) kernel rather than the hypervisor so it is far more likely that a kernel level change rather than a hypervisor change would be responsible. What kernel version are you running? Did it also change? > The arp replies are received by the host and passed all the way up to > the bridge (br200) being used by Xen, however they are not seen on the > vif (vif2.0) created for the particular vm. Do you have any firewall or ebfilter entries which might have either been discarded or reintroduced by the reboot? (i.e. a manual settings modification which wasn't propagated to the startup scripts). Or perhaps sysctl tweaks? > 1) Please let me know if I should roll-back this particular xen > update, kernel and all, and what those steps may be, or if this is a > known issue with a particular workaround that I can apply. I'd certainly be tempted to try the older kernel, assuming that was also upgraded. It may even still be installed and in your grub menu already. > 2) Would moving to openvswitch be another possible workaround? Without knowing what the underlying issue is it is hard to predict whether it will also affect ovs. > My config:- Looks correct to me. Ian. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Mon Feb 18 12:26:59 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 18 Feb 2013 12:26: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 1U7PnZ-0002mK-GG; Mon, 18 Feb 2013 12:26:21 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U78AA-0003U7-D8 for xen-users@lists.xen.org; Sun, 17 Feb 2013 17:36:30 +0000 Received: from [85.158.143.99:52625] by server-2.bemta-4.messagelabs.com id 91/71-01597-D1511215; Sun, 17 Feb 2013 17:36:29 +0000 X-Env-Sender: steve@st3v3.co.uk X-Msg-Ref: server-2.tower-216.messagelabs.com!1361122588!22568060!1 X-Originating-IP: [198.98.118.193] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 25399 invoked from network); 17 Feb 2013 17:36:29 -0000 Received: from unknown (HELO server.st3v3.co.uk) (198.98.118.193) by server-2.tower-216.messagelabs.com with SMTP; 17 Feb 2013 17:36:29 -0000 Received: from Admin-PC.st3v3 (unknown [31.105.72.130]) (Authenticated sender: steve) by server.st3v3.co.uk (Postfix) with ESMTP id 97C3DCE2CB for ; Sun, 17 Feb 2013 12:36:32 -0500 (EST) Message-ID: <5121151A.5030509@st3v3.co.uk> Date: Sun, 17 Feb 2013 17:36:26 +0000 From: Steve Rowe User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:12.0) Gecko/20120428 Thunderbird/12.0.1 MIME-Version: 1.0 To: xen-users@lists.xen.org X-Mailman-Approved-At: Mon, 18 Feb 2013 12:26:20 +0000 Subject: [Xen-users] Xen Server on a Xen vps X-BeenThere: xen-users@lists.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 have recently purchased a vps that is a xen instance with budgetvm. My question is this Is there a way to run a xen server within this server as it already a xen machine, ideally i would like to use cloudmin GPL to manage the doms. Thanks in advance. Regards eXcalibre _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Mon Feb 18 12:26:59 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 18 Feb 2013 12:26: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 1U7PnZ-0002mK-GG; Mon, 18 Feb 2013 12:26:21 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U78AA-0003U7-D8 for xen-users@lists.xen.org; Sun, 17 Feb 2013 17:36:30 +0000 Received: from [85.158.143.99:52625] by server-2.bemta-4.messagelabs.com id 91/71-01597-D1511215; Sun, 17 Feb 2013 17:36:29 +0000 X-Env-Sender: steve@st3v3.co.uk X-Msg-Ref: server-2.tower-216.messagelabs.com!1361122588!22568060!1 X-Originating-IP: [198.98.118.193] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 25399 invoked from network); 17 Feb 2013 17:36:29 -0000 Received: from unknown (HELO server.st3v3.co.uk) (198.98.118.193) by server-2.tower-216.messagelabs.com with SMTP; 17 Feb 2013 17:36:29 -0000 Received: from Admin-PC.st3v3 (unknown [31.105.72.130]) (Authenticated sender: steve) by server.st3v3.co.uk (Postfix) with ESMTP id 97C3DCE2CB for ; Sun, 17 Feb 2013 12:36:32 -0500 (EST) Message-ID: <5121151A.5030509@st3v3.co.uk> Date: Sun, 17 Feb 2013 17:36:26 +0000 From: Steve Rowe User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:12.0) Gecko/20120428 Thunderbird/12.0.1 MIME-Version: 1.0 To: xen-users@lists.xen.org X-Mailman-Approved-At: Mon, 18 Feb 2013 12:26:20 +0000 Subject: [Xen-users] Xen Server on a Xen vps X-BeenThere: xen-users@lists.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 have recently purchased a vps that is a xen instance with budgetvm. My question is this Is there a way to run a xen server within this server as it already a xen machine, ideally i would like to use cloudmin GPL to manage the doms. Thanks in advance. Regards eXcalibre _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Mon Feb 18 12:34:46 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 18 Feb 2013 12:34: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 1U7Pv8-0003MT-O1; Mon, 18 Feb 2013 12:34:10 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U7Pv7-0003ML-A3 for xen-users@lists.xen.org; Mon, 18 Feb 2013 12:34:09 +0000 Received: from [85.158.137.99:46190] by server-3.bemta-3.messagelabs.com id FB/A7-31070-0CF12215; Mon, 18 Feb 2013 12:34:08 +0000 X-Env-Sender: linux@thehobsons.co.uk X-Msg-Ref: server-2.tower-217.messagelabs.com!1361190847!21812951!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.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 29302 invoked from network); 18 Feb 2013 12:34:07 -0000 Received: from patsy.thehobsons.co.uk (HELO patsy.thehobsons.co.uk) (81.174.135.208) by server-2.tower-217.messagelabs.com with SMTP; 18 Feb 2013 12:34:07 -0000 Received: from localhost (localhost [127.0.0.1]) by patsy.thehobsons.co.uk (Postfix) with ESMTP id EA17910401A for ; Mon, 18 Feb 2013 12:33:06 +0000 (GMT) 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 CyQ4aCdiq6uj for ; Mon, 18 Feb 2013 12:33:06 +0000 (GMT) Received: from localhost (patsy.thehobsons.co.uk [192.168.0.33]) by patsy.thehobsons.co.uk (Postfix) with ESMTP id 92CE929EF5 for ; Mon, 18 Feb 2013 12:33:06 +0000 (GMT) From: "Simon Hobson" To: Date: Mon, 18 Feb 2013 12:33:08 +0000 X-Priority: 3 X-Mailer: MailForge 3.0 Mac OS X Message-ID: <09DDE88ECE695EDF05B1B4B132A4990AF@thehobsons.co.uk> Subject: Re: [Xen-users] Question regarding xen networking (bonding, xen-bridging) X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org Jonas Meurer wrote: > On the dom0 LAN connection works as expected. Gateway responds, >connection to the internet works. Dom0 and domU see each other. > >But from domU, everything beyond the dom0 is unreachable, e.g. the >gateway doesn't respond. MAC address from the domU is propagated to >switches and gateway, I can see it in the arp table. In other words, the >packets from domU find their way out, but the responding packets don't >find their way back. A quick look at the iptables rules on dom0 give me >the impression, that dom0 doesn't know how to handle packets for domU: > ># iptables -L FORWARD >Chain FORWARD (policy ACCEPT) >target prot opt source destination >ACCEPT all -- anywhere anywhere PHYSDEV match --physdev-out >vif1.0 --physdev-is-bridged >ACCEPT udp -- anywhere anywhere PHYSDEV match --physdev-in >vif1.0 --physdev-is-bridged udp spt:bootpc dpt:bootps >ACCEPT all -- anywhere anywhere PHYSDEV match --physdev-out >vif1.0 --physdev-is-bridged >ACCEPT all -- anywhere PHYSDEV match --physdev-in >vif1.0 --physdev-is-bridged > > >The last rule seems to accept packets with domU-IP as source, but I >cannot find a rule which handles incoming packets for domU. In other >words, the dom0 doesn't know what to do with packets for the domU. Is my >assumption correct? If yes, why is this the case? Is it related to >interface bonding? I think you've answered your own question there. For testing purposes, clear iptables and see if everything starts working. There is something in the standard scripts that is supposed to manipulate iptables rules when guest domains are started/stopped (there is the option of specifying "ip-a.b.c.d" in the VIF declaration), but I've never looked into it. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Mon Feb 18 12:34:46 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 18 Feb 2013 12:34: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 1U7Pv8-0003MT-O1; Mon, 18 Feb 2013 12:34:10 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U7Pv7-0003ML-A3 for xen-users@lists.xen.org; Mon, 18 Feb 2013 12:34:09 +0000 Received: from [85.158.137.99:46190] by server-3.bemta-3.messagelabs.com id FB/A7-31070-0CF12215; Mon, 18 Feb 2013 12:34:08 +0000 X-Env-Sender: linux@thehobsons.co.uk X-Msg-Ref: server-2.tower-217.messagelabs.com!1361190847!21812951!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.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 29302 invoked from network); 18 Feb 2013 12:34:07 -0000 Received: from patsy.thehobsons.co.uk (HELO patsy.thehobsons.co.uk) (81.174.135.208) by server-2.tower-217.messagelabs.com with SMTP; 18 Feb 2013 12:34:07 -0000 Received: from localhost (localhost [127.0.0.1]) by patsy.thehobsons.co.uk (Postfix) with ESMTP id EA17910401A for ; Mon, 18 Feb 2013 12:33:06 +0000 (GMT) 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 CyQ4aCdiq6uj for ; Mon, 18 Feb 2013 12:33:06 +0000 (GMT) Received: from localhost (patsy.thehobsons.co.uk [192.168.0.33]) by patsy.thehobsons.co.uk (Postfix) with ESMTP id 92CE929EF5 for ; Mon, 18 Feb 2013 12:33:06 +0000 (GMT) From: "Simon Hobson" To: Date: Mon, 18 Feb 2013 12:33:08 +0000 X-Priority: 3 X-Mailer: MailForge 3.0 Mac OS X Message-ID: <09DDE88ECE695EDF05B1B4B132A4990AF@thehobsons.co.uk> Subject: Re: [Xen-users] Question regarding xen networking (bonding, xen-bridging) X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org Jonas Meurer wrote: > On the dom0 LAN connection works as expected. Gateway responds, >connection to the internet works. Dom0 and domU see each other. > >But from domU, everything beyond the dom0 is unreachable, e.g. the >gateway doesn't respond. MAC address from the domU is propagated to >switches and gateway, I can see it in the arp table. In other words, the >packets from domU find their way out, but the responding packets don't >find their way back. A quick look at the iptables rules on dom0 give me >the impression, that dom0 doesn't know how to handle packets for domU: > ># iptables -L FORWARD >Chain FORWARD (policy ACCEPT) >target prot opt source destination >ACCEPT all -- anywhere anywhere PHYSDEV match --physdev-out >vif1.0 --physdev-is-bridged >ACCEPT udp -- anywhere anywhere PHYSDEV match --physdev-in >vif1.0 --physdev-is-bridged udp spt:bootpc dpt:bootps >ACCEPT all -- anywhere anywhere PHYSDEV match --physdev-out >vif1.0 --physdev-is-bridged >ACCEPT all -- anywhere PHYSDEV match --physdev-in >vif1.0 --physdev-is-bridged > > >The last rule seems to accept packets with domU-IP as source, but I >cannot find a rule which handles incoming packets for domU. In other >words, the dom0 doesn't know what to do with packets for the domU. Is my >assumption correct? If yes, why is this the case? Is it related to >interface bonding? I think you've answered your own question there. For testing purposes, clear iptables and see if everything starts working. There is something in the standard scripts that is supposed to manipulate iptables rules when guest domains are started/stopped (there is the option of specifying "ip-a.b.c.d" in the VIF declaration), but I've never looked into it. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Mon Feb 18 13:05:28 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 18 Feb 2013 13:05: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 1U7QOV-0004K7-Jm; Mon, 18 Feb 2013 13:04:31 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U7QOT-0004K2-Jp for xen-users@lists.xen.org; Mon, 18 Feb 2013 13:04:29 +0000 Received: from [193.109.254.147:7632] by server-15.bemta-14.messagelabs.com id D4/8C-24599-CD622215; Mon, 18 Feb 2013 13:04:28 +0000 X-Env-Sender: eross@corp.locatrix.com X-Msg-Ref: server-10.tower-27.messagelabs.com!1361192665!3637998!1 X-Originating-IP: [209.85.210.177] 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.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 1817 invoked from network); 18 Feb 2013 13:04:28 -0000 Received: from mail-ia0-f177.google.com (HELO mail-ia0-f177.google.com) (209.85.210.177) by server-10.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 18 Feb 2013 13:04:28 -0000 Received: by mail-ia0-f177.google.com with SMTP id o25so365286iad.22 for ; Mon, 18 Feb 2013 05:04:24 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=x-received:mime-version:in-reply-to:references:from:date:message-id :subject:to:content-type:x-gm-message-state; bh=4XDqINXYZsCxKiQoiy2uJGuY4KX9nKtxhYidEqFaSSQ=; b=S5aEvNegkfbQwWEpYvYgT9sS4D1Os6d4oDAsPWppukuru1pI6eLSQhH+WaUqi77dce q43Jnz+pgVeh4Wg6uMJvA7WdEsl+eTn7fzUx6Eice5cIT61JMdgpx+io+i8op2DPlT2v IpWuMsd9J31X6qWuRqsVMH5TT3GPDBCJBJt3HszswJiL/JfTDptgr1oKuNu8ftk43R6b spWk/JLR70q7b9NJrteb6dfY/UTM0TTApowl45XDqK3/PlP/B7S1uMuAiyZjxD9UV7ow 9PTWY+n5BXpJ5ygtvp8WeQ5VIGy86cFPymOuXBpqBt1qYU9iUZ8htK4ffjrgoHTS5Wnh vMBw== X-Received: by 10.50.7.240 with SMTP id m16mr6264955iga.91.1361192664727; Mon, 18 Feb 2013 05:04:24 -0800 (PST) MIME-Version: 1.0 Received: by 10.64.44.197 with HTTP; Mon, 18 Feb 2013 05:04:04 -0800 (PST) In-Reply-To: References: From: Andrew Eross Date: Mon, 18 Feb 2013 10:04:04 -0300 Message-ID: To: xen-users@lists.xen.org X-Gm-Message-State: ALoCoQkaPY6I8ENbmhY4Z5nn6vdsnRsIwJheSUNSTkNmPQk8oajOKREiIzkNvydkfo1hUNjsvf1S Subject: Re: [Xen-users] Xen 4.2.1 unable to get domain type for domid X-BeenThere: xen-users@lists.xen.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="===============8302956261437606778==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============8302956261437606778== Content-Type: multipart/alternative; boundary=f46d0447976d40822a04d5ff5deb --f46d0447976d40822a04d5ff5deb Content-Type: text/plain; charset=ISO-8859-1 Strangely, if I use Ubuntu 13.04 (raring) for the installer netboot, it works just fine with exactly the same configuration. However, I can't imagine that Ubuntu 12.04 wouldn't be supported for some reason? On Mon, Feb 18, 2013 at 7:58 AM, Andrew Eross wrote: > Hi guys, > > I'm running Xen 4.2.1, compiled manually so I can play with Remus and > DRBD, running on Ubuntu 12.10. > > I keep getting this error when trying to start up my first VM to run the > Ubuntu netboot installer. > > ----------------------------------------------------------------- > root@left:/home/eross# xl create /etc/xen/ubuntu.cfg -c > Parsing config from /etc/xen/ubuntu.cfg > Daemon running with PID 1513 > libxl: error: libxl_dom.c:34:libxl__domain_type: unable to get domain type > for domid=1 > Unable to attach console > libxl: error: libxl_exec.c:118:libxl_report_child_exitstatus: console > child [0] exited with error status 1 > ----------------------------------------------------------------- > > Here's my VM's config: > ----------------------------------------------------------------- > root@left:/home/eross# cat /etc/xen/ubuntu.cfg > name = "ubuntu" > > memory = 256 > > disk = [ 'drbd:drbd-vm,xvda,w' ] > vif = [' '] > > kernel = "/var/lib/xen/images/ubuntu-netboot/vmlinuz" > ramdisk = "/var/lib/xen/images/ubuntu-netboot/initrd.gz" > extra = "debian-installer/exit/always_halt=true -- console=hvc0" > ----------------------------------------------------------------- > > The ubuntu-netboot image there is 64-bit 12.04 Precise. > > Any ideas? > > Thank you! > Andrew > > --f46d0447976d40822a04d5ff5deb Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Strangely, if I use Ubuntu 13.04 (raring) for the installer netboot, it wor= ks just fine with exactly the same configuration.

Howeve= r, I can't imagine that Ubuntu 12.04 wouldn't be supported for some= reason?

On Mon, Feb 18, 2013 at 7:58 AM, Andrew Eros= s <eross@locatrix.com> wrote:
Hi guys,

I'm running Xen 4.2.1, compiled = manually so I can play with Remus and DRBD, running on Ubuntu 12.10.
<= div>
I keep getting this error when trying to start up my fir= st VM to run the Ubuntu netboot installer.

-------------------------------------------------------= ----------
root@left:/home/eross#=A0xl create /etc/xen/ubuntu.cfg= -c
Parsing config from /etc/xen/ubuntu.cfg
Daemon runn= ing with PID 1513
libxl: error: libxl_dom.c:34:libxl__domain_type: unable to get domain = type for domid=3D1
Unable to attach console
libxl: erro= r: libxl_exec.c:118:libxl_report_child_exitstatus: console child [0] exited= with error status 1
-----------------------------------------------------------------

Here's my VM's config:
-------------= ----------------------------------------------------
root@left:/h= ome/eross# cat /etc/xen/ubuntu.cfg
name =3D "ubuntu"

memory =3D 256

disk =3D [ 'drbd:drbd-vm,xvda,w' ]
vif =3D [' ']

kernel =3D "/var/lib/x= en/images/ubuntu-netboot/vmlinuz"
ramdisk =3D "/var/lib/xen/images/ubuntu-netboot/initrd.gz"
extra =3D "debian-installer/exit/always_halt=3Dtrue -- consol= e=3Dhvc0"
--------------------------------------------------= ---------------

The ubuntu-netboot image there is 64-bit 12.04 Precise.=

Any ideas?

Thank you!
Andrew

--f46d0447976d40822a04d5ff5deb-- --===============8302956261437606778== 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 --===============8302956261437606778==-- From xen-users-bounces@lists.xen.org Mon Feb 18 13:05:28 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 18 Feb 2013 13:05: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 1U7QOV-0004K7-Jm; Mon, 18 Feb 2013 13:04:31 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U7QOT-0004K2-Jp for xen-users@lists.xen.org; Mon, 18 Feb 2013 13:04:29 +0000 Received: from [193.109.254.147:7632] by server-15.bemta-14.messagelabs.com id D4/8C-24599-CD622215; Mon, 18 Feb 2013 13:04:28 +0000 X-Env-Sender: eross@corp.locatrix.com X-Msg-Ref: server-10.tower-27.messagelabs.com!1361192665!3637998!1 X-Originating-IP: [209.85.210.177] 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.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 1817 invoked from network); 18 Feb 2013 13:04:28 -0000 Received: from mail-ia0-f177.google.com (HELO mail-ia0-f177.google.com) (209.85.210.177) by server-10.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 18 Feb 2013 13:04:28 -0000 Received: by mail-ia0-f177.google.com with SMTP id o25so365286iad.22 for ; Mon, 18 Feb 2013 05:04:24 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=x-received:mime-version:in-reply-to:references:from:date:message-id :subject:to:content-type:x-gm-message-state; bh=4XDqINXYZsCxKiQoiy2uJGuY4KX9nKtxhYidEqFaSSQ=; b=S5aEvNegkfbQwWEpYvYgT9sS4D1Os6d4oDAsPWppukuru1pI6eLSQhH+WaUqi77dce q43Jnz+pgVeh4Wg6uMJvA7WdEsl+eTn7fzUx6Eice5cIT61JMdgpx+io+i8op2DPlT2v IpWuMsd9J31X6qWuRqsVMH5TT3GPDBCJBJt3HszswJiL/JfTDptgr1oKuNu8ftk43R6b spWk/JLR70q7b9NJrteb6dfY/UTM0TTApowl45XDqK3/PlP/B7S1uMuAiyZjxD9UV7ow 9PTWY+n5BXpJ5ygtvp8WeQ5VIGy86cFPymOuXBpqBt1qYU9iUZ8htK4ffjrgoHTS5Wnh vMBw== X-Received: by 10.50.7.240 with SMTP id m16mr6264955iga.91.1361192664727; Mon, 18 Feb 2013 05:04:24 -0800 (PST) MIME-Version: 1.0 Received: by 10.64.44.197 with HTTP; Mon, 18 Feb 2013 05:04:04 -0800 (PST) In-Reply-To: References: From: Andrew Eross Date: Mon, 18 Feb 2013 10:04:04 -0300 Message-ID: To: xen-users@lists.xen.org X-Gm-Message-State: ALoCoQkaPY6I8ENbmhY4Z5nn6vdsnRsIwJheSUNSTkNmPQk8oajOKREiIzkNvydkfo1hUNjsvf1S Subject: Re: [Xen-users] Xen 4.2.1 unable to get domain type for domid X-BeenThere: xen-users@lists.xen.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="===============8302956261437606778==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============8302956261437606778== Content-Type: multipart/alternative; boundary=f46d0447976d40822a04d5ff5deb --f46d0447976d40822a04d5ff5deb Content-Type: text/plain; charset=ISO-8859-1 Strangely, if I use Ubuntu 13.04 (raring) for the installer netboot, it works just fine with exactly the same configuration. However, I can't imagine that Ubuntu 12.04 wouldn't be supported for some reason? On Mon, Feb 18, 2013 at 7:58 AM, Andrew Eross wrote: > Hi guys, > > I'm running Xen 4.2.1, compiled manually so I can play with Remus and > DRBD, running on Ubuntu 12.10. > > I keep getting this error when trying to start up my first VM to run the > Ubuntu netboot installer. > > ----------------------------------------------------------------- > root@left:/home/eross# xl create /etc/xen/ubuntu.cfg -c > Parsing config from /etc/xen/ubuntu.cfg > Daemon running with PID 1513 > libxl: error: libxl_dom.c:34:libxl__domain_type: unable to get domain type > for domid=1 > Unable to attach console > libxl: error: libxl_exec.c:118:libxl_report_child_exitstatus: console > child [0] exited with error status 1 > ----------------------------------------------------------------- > > Here's my VM's config: > ----------------------------------------------------------------- > root@left:/home/eross# cat /etc/xen/ubuntu.cfg > name = "ubuntu" > > memory = 256 > > disk = [ 'drbd:drbd-vm,xvda,w' ] > vif = [' '] > > kernel = "/var/lib/xen/images/ubuntu-netboot/vmlinuz" > ramdisk = "/var/lib/xen/images/ubuntu-netboot/initrd.gz" > extra = "debian-installer/exit/always_halt=true -- console=hvc0" > ----------------------------------------------------------------- > > The ubuntu-netboot image there is 64-bit 12.04 Precise. > > Any ideas? > > Thank you! > Andrew > > --f46d0447976d40822a04d5ff5deb Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Strangely, if I use Ubuntu 13.04 (raring) for the installer netboot, it wor= ks just fine with exactly the same configuration.

Howeve= r, I can't imagine that Ubuntu 12.04 wouldn't be supported for some= reason?

On Mon, Feb 18, 2013 at 7:58 AM, Andrew Eros= s <eross@locatrix.com> wrote:
Hi guys,

I'm running Xen 4.2.1, compiled = manually so I can play with Remus and DRBD, running on Ubuntu 12.10.
<= div>
I keep getting this error when trying to start up my fir= st VM to run the Ubuntu netboot installer.

-------------------------------------------------------= ----------
root@left:/home/eross#=A0xl create /etc/xen/ubuntu.cfg= -c
Parsing config from /etc/xen/ubuntu.cfg
Daemon runn= ing with PID 1513
libxl: error: libxl_dom.c:34:libxl__domain_type: unable to get domain = type for domid=3D1
Unable to attach console
libxl: erro= r: libxl_exec.c:118:libxl_report_child_exitstatus: console child [0] exited= with error status 1
-----------------------------------------------------------------

Here's my VM's config:
-------------= ----------------------------------------------------
root@left:/h= ome/eross# cat /etc/xen/ubuntu.cfg
name =3D "ubuntu"

memory =3D 256

disk =3D [ 'drbd:drbd-vm,xvda,w' ]
vif =3D [' ']

kernel =3D "/var/lib/x= en/images/ubuntu-netboot/vmlinuz"
ramdisk =3D "/var/lib/xen/images/ubuntu-netboot/initrd.gz"
extra =3D "debian-installer/exit/always_halt=3Dtrue -- consol= e=3Dhvc0"
--------------------------------------------------= ---------------

The ubuntu-netboot image there is 64-bit 12.04 Precise.=

Any ideas?

Thank you!
Andrew

--f46d0447976d40822a04d5ff5deb-- --===============8302956261437606778== 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 --===============8302956261437606778==-- From xen-users-bounces@lists.xen.org Mon Feb 18 13:52:19 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 18 Feb 2013 13:52: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 1U7R7p-00060n-1Q; Mon, 18 Feb 2013 13:51:21 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U7R7m-00060f-NP for xen-users@lists.xen.org; Mon, 18 Feb 2013 13:51:19 +0000 Received: from [85.158.139.83:65034] by server-12.bemta-5.messagelabs.com id B1/2E-20195-5D132215; Mon, 18 Feb 2013 13:51:17 +0000 X-Env-Sender: netmatters@gmail.com X-Msg-Ref: server-11.tower-182.messagelabs.com!1361195472!20539833!1 X-Originating-IP: [209.85.128.176] 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.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 12182 invoked from network); 18 Feb 2013 13:51:14 -0000 Received: from mail-ve0-f176.google.com (HELO mail-ve0-f176.google.com) (209.85.128.176) by server-11.tower-182.messagelabs.com with RC4-SHA encrypted SMTP; 18 Feb 2013 13:51:14 -0000 Received: by mail-ve0-f176.google.com with SMTP id cz10so4754637veb.21 for ; Mon, 18 Feb 2013 05:51:12 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=NK/mLPFIK+YYWb37rtVPNfunP6Qlezbj9/qtAIyhIXk=; b=XKdTYdtJjMHb/OYvHxlPW1isLvV90lirNQTEhifihae/gvLd8dBa4NQlwye8p8IdjR l1spDNoYdxyaAjUn/oDVwZ4N+Ki+T+Q7O8jvc8AzUwcurLpCKyTWJkyToCrCLb8Ayvct 5eJmwy0b3tZFzp0RuwNmEMg72hZqIhCP4/6q3w879jWE/D1biixlBVXFnFpMgZgi7kq8 91JaO/zB0nu8tDdzTmkfCj+feNv7sEGoWAS/rMLO1eLhaEro1XOr3lvXJsLOFXiJht1A B7Kxn5votlane4VbI4lvamPiVKeCOqSlIqS6KQ61MXe+3YCR/RaBAWfzdclPufmXanSk LSOQ== MIME-Version: 1.0 X-Received: by 10.58.132.170 with SMTP id ov10mr15649478veb.57.1361195472510; Mon, 18 Feb 2013 05:51:12 -0800 (PST) Received: by 10.58.106.133 with HTTP; Mon, 18 Feb 2013 05:51:12 -0800 (PST) In-Reply-To: References: <1361184601.31407.144.camel@zakaz.uk.xensource.com> Date: Mon, 18 Feb 2013 15:51:12 +0200 Message-ID: From: Gavin To: Ian Campbell Cc: pkg-xen-devel@lists.alioth.debian.org, xen-users , debian-user@lists.debian.org Subject: Re: [Xen-users] [Pkg-xen-devel] Recent hypervisor update on Debian Wheezy breaks domU 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="===============8346526638002564726==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============8346526638002564726== Content-Type: multipart/alternative; boundary=047d7b6da8f89be0b104d600049f --047d7b6da8f89be0b104d600049f Content-Type: text/plain; charset=ISO-8859-1 On 18 February 2013 13:40, Gavin wrote: > On 18 February 2013 12:50, Ian Campbell wrote: > >> >> Networking level stuff is all done by the dom0 (or driver domain) kernel >> rather than the hypervisor so it is far more likely that a kernel level >> change rather than a hypervisor change would be responsible. What kernel >> version are you running? Did it also change? >> > > This makes sense, although when I did the apt-get upgrade, there was no > kernel update, however there may have been packages/drivers that required a > kernel mod. > > Here is the apt history which details what was upgraded when this broke:- > > Upgrade: xen-hypervisor-4.1-amd64:amd64 (4.1.3-7, 4.1.3-8) > > The kernel I am using is: 3.2.0-2-amd64, also tried 3.2.0-4-amd64 on > another host with no success. > > Would the upgrade above of xen-hypervisor-4.1-amd64 on this Debian system > not cause the Dom0 kernel to be changed in any way ?? > >> >> > 1) Please let me know if I should roll-back this particular xen >> > update, kernel and all, and what those steps may be, or if this is a >> > known issue with a particular workaround that I can apply. >> >> I'd certainly be tempted to try the older kernel, assuming that was also >> upgraded. It may even still be installed and in your grub menu already. >> > > The problem is now we are using grub2 and it appears that on boot grub > loads a Linux menu, then the Xen Menu with configs in /etc/grub.d/ so I'm > battling to figure out how to do this. > > I also do not have physical access to this host at the moment so need to > set the boot order 'correctly' prior to a reboot. > I managed to get iDRAC console access and on further inspection it appears that grub first boots xen-4.1-amd64.gz and then the Linux kernel. When I updated the Xen Hypervisor does it not also upgrade the xen-4.1-amd64.gz file ?? Are there any better ways to trace where this arp reply is being lost apart from just tcpdump ? None of the log files are reporting back any errors and my googling just does not seem to return any useful results. --047d7b6da8f89be0b104d600049f Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
On 18 February 2013 13:40, Gavin <netmatters@gmail.com= > wrote:
On 18 February 2013 12:50, Ian Campbell = <ijc@hellion.org.uk> wrote:

Networking level stuff is all done by the dom0 (or driver domain) ker= nel
rather than the hypervisor so it is far more likely that a kernel level
change rather than a hypervisor change would be responsible. What kernel version are you running? Did it also change?

This makes sense, although when I did the apt-get upgrade, ther= e was no kernel update, however there may have been packages/drivers that r= equired a kernel mod.

Here is the apt history which details what was upgraded= when this broke:-

Upgrade: xen-hypervisor-4.1-amd= 64:amd64 (4.1.3-7, 4.1.3-8)

The kernel I am using is:=A03.2.0-2-amd64, also tried 3= .2.0-4-amd64 on another host with no success.
=A0
Would= the upgrade above of xen-hypervisor-4.1-amd64 on this Debian system not ca= use the Dom0 kernel to be changed in any way ??=A0

> 1) Please let me know if I should roll-back this particular xen
> update, kernel and all, and what those steps may be, or if this is a > known issue with a particular workaround that I can apply.

I'd certainly be tempted to try the older kernel, assuming that w= as also
upgraded. It may even still be installed and in your grub menu already.
=

The problem is now we are using grub= 2 and it appears that on boot grub loads a Linux menu, then the Xen Menu wi= th configs in /etc/grub.d/ so I'm battling to figure out how to do this= .

I also do not have physical access to this host at the = moment so need to set the boot order 'correctly' prior to a reboot.=

I managed to= get iDRAC console access and on further inspection it appears that grub fi= rst boots xen-4.1-amd64.gz and then the Linux kernel.

When I updated the Xen Hypervisor does it n= ot also upgrade the xen-4.1-amd64.gz file ??=A0

Are there any better ways to trace where this ar= p reply is being lost apart from just tcpdump ?=A0

None of the log files are reporting back any errors and my googling just d= oes not seem to return any useful results.

<stumped! />
--047d7b6da8f89be0b104d600049f-- --===============8346526638002564726== 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 --===============8346526638002564726==-- From xen-users-bounces@lists.xen.org Mon Feb 18 13:52:19 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 18 Feb 2013 13:52: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 1U7R7p-00060n-1Q; Mon, 18 Feb 2013 13:51:21 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U7R7m-00060f-NP for xen-users@lists.xen.org; Mon, 18 Feb 2013 13:51:19 +0000 Received: from [85.158.139.83:65034] by server-12.bemta-5.messagelabs.com id B1/2E-20195-5D132215; Mon, 18 Feb 2013 13:51:17 +0000 X-Env-Sender: netmatters@gmail.com X-Msg-Ref: server-11.tower-182.messagelabs.com!1361195472!20539833!1 X-Originating-IP: [209.85.128.176] 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.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 12182 invoked from network); 18 Feb 2013 13:51:14 -0000 Received: from mail-ve0-f176.google.com (HELO mail-ve0-f176.google.com) (209.85.128.176) by server-11.tower-182.messagelabs.com with RC4-SHA encrypted SMTP; 18 Feb 2013 13:51:14 -0000 Received: by mail-ve0-f176.google.com with SMTP id cz10so4754637veb.21 for ; Mon, 18 Feb 2013 05:51:12 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=NK/mLPFIK+YYWb37rtVPNfunP6Qlezbj9/qtAIyhIXk=; b=XKdTYdtJjMHb/OYvHxlPW1isLvV90lirNQTEhifihae/gvLd8dBa4NQlwye8p8IdjR l1spDNoYdxyaAjUn/oDVwZ4N+Ki+T+Q7O8jvc8AzUwcurLpCKyTWJkyToCrCLb8Ayvct 5eJmwy0b3tZFzp0RuwNmEMg72hZqIhCP4/6q3w879jWE/D1biixlBVXFnFpMgZgi7kq8 91JaO/zB0nu8tDdzTmkfCj+feNv7sEGoWAS/rMLO1eLhaEro1XOr3lvXJsLOFXiJht1A B7Kxn5votlane4VbI4lvamPiVKeCOqSlIqS6KQ61MXe+3YCR/RaBAWfzdclPufmXanSk LSOQ== MIME-Version: 1.0 X-Received: by 10.58.132.170 with SMTP id ov10mr15649478veb.57.1361195472510; Mon, 18 Feb 2013 05:51:12 -0800 (PST) Received: by 10.58.106.133 with HTTP; Mon, 18 Feb 2013 05:51:12 -0800 (PST) In-Reply-To: References: <1361184601.31407.144.camel@zakaz.uk.xensource.com> Date: Mon, 18 Feb 2013 15:51:12 +0200 Message-ID: From: Gavin To: Ian Campbell Cc: pkg-xen-devel@lists.alioth.debian.org, xen-users , debian-user@lists.debian.org Subject: Re: [Xen-users] [Pkg-xen-devel] Recent hypervisor update on Debian Wheezy breaks domU 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="===============8346526638002564726==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============8346526638002564726== Content-Type: multipart/alternative; boundary=047d7b6da8f89be0b104d600049f --047d7b6da8f89be0b104d600049f Content-Type: text/plain; charset=ISO-8859-1 On 18 February 2013 13:40, Gavin wrote: > On 18 February 2013 12:50, Ian Campbell wrote: > >> >> Networking level stuff is all done by the dom0 (or driver domain) kernel >> rather than the hypervisor so it is far more likely that a kernel level >> change rather than a hypervisor change would be responsible. What kernel >> version are you running? Did it also change? >> > > This makes sense, although when I did the apt-get upgrade, there was no > kernel update, however there may have been packages/drivers that required a > kernel mod. > > Here is the apt history which details what was upgraded when this broke:- > > Upgrade: xen-hypervisor-4.1-amd64:amd64 (4.1.3-7, 4.1.3-8) > > The kernel I am using is: 3.2.0-2-amd64, also tried 3.2.0-4-amd64 on > another host with no success. > > Would the upgrade above of xen-hypervisor-4.1-amd64 on this Debian system > not cause the Dom0 kernel to be changed in any way ?? > >> >> > 1) Please let me know if I should roll-back this particular xen >> > update, kernel and all, and what those steps may be, or if this is a >> > known issue with a particular workaround that I can apply. >> >> I'd certainly be tempted to try the older kernel, assuming that was also >> upgraded. It may even still be installed and in your grub menu already. >> > > The problem is now we are using grub2 and it appears that on boot grub > loads a Linux menu, then the Xen Menu with configs in /etc/grub.d/ so I'm > battling to figure out how to do this. > > I also do not have physical access to this host at the moment so need to > set the boot order 'correctly' prior to a reboot. > I managed to get iDRAC console access and on further inspection it appears that grub first boots xen-4.1-amd64.gz and then the Linux kernel. When I updated the Xen Hypervisor does it not also upgrade the xen-4.1-amd64.gz file ?? Are there any better ways to trace where this arp reply is being lost apart from just tcpdump ? None of the log files are reporting back any errors and my googling just does not seem to return any useful results. --047d7b6da8f89be0b104d600049f Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
On 18 February 2013 13:40, Gavin <netmatters@gmail.com= > wrote:
On 18 February 2013 12:50, Ian Campbell = <ijc@hellion.org.uk> wrote:

Networking level stuff is all done by the dom0 (or driver domain) ker= nel
rather than the hypervisor so it is far more likely that a kernel level
change rather than a hypervisor change would be responsible. What kernel version are you running? Did it also change?

This makes sense, although when I did the apt-get upgrade, ther= e was no kernel update, however there may have been packages/drivers that r= equired a kernel mod.

Here is the apt history which details what was upgraded= when this broke:-

Upgrade: xen-hypervisor-4.1-amd= 64:amd64 (4.1.3-7, 4.1.3-8)

The kernel I am using is:=A03.2.0-2-amd64, also tried 3= .2.0-4-amd64 on another host with no success.
=A0
Would= the upgrade above of xen-hypervisor-4.1-amd64 on this Debian system not ca= use the Dom0 kernel to be changed in any way ??=A0

> 1) Please let me know if I should roll-back this particular xen
> update, kernel and all, and what those steps may be, or if this is a > known issue with a particular workaround that I can apply.

I'd certainly be tempted to try the older kernel, assuming that w= as also
upgraded. It may even still be installed and in your grub menu already.
=

The problem is now we are using grub= 2 and it appears that on boot grub loads a Linux menu, then the Xen Menu wi= th configs in /etc/grub.d/ so I'm battling to figure out how to do this= .

I also do not have physical access to this host at the = moment so need to set the boot order 'correctly' prior to a reboot.=

I managed to= get iDRAC console access and on further inspection it appears that grub fi= rst boots xen-4.1-amd64.gz and then the Linux kernel.

When I updated the Xen Hypervisor does it n= ot also upgrade the xen-4.1-amd64.gz file ??=A0

Are there any better ways to trace where this ar= p reply is being lost apart from just tcpdump ?=A0

None of the log files are reporting back any errors and my googling just d= oes not seem to return any useful results.

<stumped! />
--047d7b6da8f89be0b104d600049f-- --===============8346526638002564726== 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 --===============8346526638002564726==-- From xen-users-bounces@lists.xen.org Mon Feb 18 14:26:13 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 18 Feb 2013 14:26: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 1U7Rec-00073a-Sy; Mon, 18 Feb 2013 14:25:14 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U7Reb-00073V-PF for xen-users@lists.xen.org; Mon, 18 Feb 2013 14:25:14 +0000 Received: from [85.158.137.99:44315] by server-16.bemta-3.messagelabs.com id 1E/A6-02727-4C932215; Mon, 18 Feb 2013 14:25:08 +0000 X-Env-Sender: jonas@freesources.org X-Msg-Ref: server-5.tower-217.messagelabs.com!1361197506!17253117!1 X-Originating-IP: [80.237.252.132] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 6600 invoked from network); 18 Feb 2013 14:25:06 -0000 Received: from mx01.freesources.org (HELO mail01.freesources.org) (80.237.252.132) by server-5.tower-217.messagelabs.com with AES256-SHA encrypted SMTP; 18 Feb 2013 14:25:06 -0000 Received: from secure.freesources.org ([80.237.252.133]) by mail01.freesources.org with esmtpsa (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.72) (envelope-from ) id 1U7ReM-0002tw-Lz for xen-users@lists.xen.org; Mon, 18 Feb 2013 14:25:05 +0000 MIME-Version: 1.0 Date: Mon, 18 Feb 2013 15:24:58 +0100 From: Jonas Meurer To: In-Reply-To: <09DDE88ECE695EDF05B1B4B132A4990AF@thehobsons.co.uk> References: <09DDE88ECE695EDF05B1B4B132A4990AF@thehobsons.co.uk> Message-ID: <8437969a04956ee482ef1cd81a1c3dae@imap.freesources.org> X-Sender: jonas@freesources.org User-Agent: Roundcube Webmail/0.7.1 X-SA-Exim-Connect-IP: 80.237.252.133 X-SA-Exim-Mail-From: jonas@freesources.org X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on mail01.freesources.org X-Spam-Level: X-Spam-Status: No, score=-3.5 required=5.0 tests=ALL_TRUSTED,BAYES_00, RP_MATCHES_RCVD autolearn=ham version=3.3.1 X-SA-Exim-Version: 4.2.1 (built Mon, 22 Mar 2010 06:26:47 +0000) X-SA-Exim-Scanned: Yes (on mail01.freesources.org) Subject: Re: [Xen-users] Question regarding xen networking (bonding, xen-bridging) X-BeenThere: xen-users@lists.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 Am 18.02.2013 13:33, schrieb Simon Hobson: > Jonas Meurer wrote: > >> On the dom0 LAN connection works as expected. Gateway responds, >>connection to the internet works. Dom0 and domU see each other. >> >>But from domU, everything beyond the dom0 is unreachable, e.g. the >>gateway doesn't respond. MAC address from the domU is propagated to >>switches and gateway, I can see it in the arp table. In other words, >> the >>packets from domU find their way out, but the responding packets >> don't >>find their way back. A quick look at the iptables rules on dom0 give >> me >>the impression, that dom0 doesn't know how to handle packets for >> domU: >> >># iptables -L FORWARD >>Chain FORWARD (policy ACCEPT) >>target prot opt source destination >>ACCEPT all -- anywhere anywhere PHYSDEV match --physdev-out >>vif1.0 --physdev-is-bridged >>ACCEPT udp -- anywhere anywhere PHYSDEV match --physdev-in >>vif1.0 --physdev-is-bridged udp spt:bootpc dpt:bootps >>ACCEPT all -- anywhere anywhere PHYSDEV match --physdev-out >>vif1.0 --physdev-is-bridged >>ACCEPT all -- anywhere PHYSDEV match --physdev-in >>vif1.0 --physdev-is-bridged >> >> >>The last rule seems to accept packets with domU-IP as source, but I >>cannot find a rule which handles incoming packets for domU. In other >>words, the dom0 doesn't know what to do with packets for the domU. Is >> my >>assumption correct? If yes, why is this the case? Is it related to >>interface bonding? > > I think you've answered your own question there. For testing > purposes, clear iptables and see if everything starts working. > > There is something in the standard scripts that is supposed to > manipulate iptables rules when guest domains are started/stopped > (there is the option of specifying "ip-a.b.c.d" in the VIF > declaration), but I've never looked into it. Hello Simon, Thanks for the quick response. For some unknown reason, suddenly the setup started to work. Maybe I didn't wait long enough for the switches to accept the new domU as devices. Whatever, below is the dom0 interface setup that works for me (as reference for the future): /etc/network/interfaces: --8-<----8-<----8-<----8-<----8-<----8-<----8-<-- auto bond0 iface bond0 inet manual slaves eth0 eth1 bond_mode balance-xor bond_miimon 100 bond_downdelay 200 bond_updelay 200 auto xenbr0 iface xenbr0 inet static bridge_ports bond0 bridge_maxwait 0 bridge_stp off bridge_fd 0 address netmask network broadcast gateway -->-8---->-8---->-8---->-8---->-8---->-8---->-8-- I didn't modify the iptables rules created by xen helper scripts: # iptables-save --8-<----8-<----8-<----8-<----8-<----8-<----8-<-- -A FORWARD -m physdev --physdev-out vif2.0 --physdev-is-bridged -j ACCEPT -A FORWARD -p udp -m physdev --physdev-in vif2.0 --physdev-is-bridged -m udp --sport 68 --dport 67 -j ACCEPT -A FORWARD -m physdev --physdev-out vif2.0 --physdev-is-bridged -j ACCEPT -A FORWARD -s /32 -m physdev --physdev-in vif2.0 --physdev-is-bridged -j ACCEPT -->-8---->-8---->-8---->-8---->-8---->-8---->-8-- Kind regards, jonas _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Mon Feb 18 14:26:13 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 18 Feb 2013 14:26: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 1U7Rec-00073a-Sy; Mon, 18 Feb 2013 14:25:14 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U7Reb-00073V-PF for xen-users@lists.xen.org; Mon, 18 Feb 2013 14:25:14 +0000 Received: from [85.158.137.99:44315] by server-16.bemta-3.messagelabs.com id 1E/A6-02727-4C932215; Mon, 18 Feb 2013 14:25:08 +0000 X-Env-Sender: jonas@freesources.org X-Msg-Ref: server-5.tower-217.messagelabs.com!1361197506!17253117!1 X-Originating-IP: [80.237.252.132] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 6600 invoked from network); 18 Feb 2013 14:25:06 -0000 Received: from mx01.freesources.org (HELO mail01.freesources.org) (80.237.252.132) by server-5.tower-217.messagelabs.com with AES256-SHA encrypted SMTP; 18 Feb 2013 14:25:06 -0000 Received: from secure.freesources.org ([80.237.252.133]) by mail01.freesources.org with esmtpsa (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.72) (envelope-from ) id 1U7ReM-0002tw-Lz for xen-users@lists.xen.org; Mon, 18 Feb 2013 14:25:05 +0000 MIME-Version: 1.0 Date: Mon, 18 Feb 2013 15:24:58 +0100 From: Jonas Meurer To: In-Reply-To: <09DDE88ECE695EDF05B1B4B132A4990AF@thehobsons.co.uk> References: <09DDE88ECE695EDF05B1B4B132A4990AF@thehobsons.co.uk> Message-ID: <8437969a04956ee482ef1cd81a1c3dae@imap.freesources.org> X-Sender: jonas@freesources.org User-Agent: Roundcube Webmail/0.7.1 X-SA-Exim-Connect-IP: 80.237.252.133 X-SA-Exim-Mail-From: jonas@freesources.org X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on mail01.freesources.org X-Spam-Level: X-Spam-Status: No, score=-3.5 required=5.0 tests=ALL_TRUSTED,BAYES_00, RP_MATCHES_RCVD autolearn=ham version=3.3.1 X-SA-Exim-Version: 4.2.1 (built Mon, 22 Mar 2010 06:26:47 +0000) X-SA-Exim-Scanned: Yes (on mail01.freesources.org) Subject: Re: [Xen-users] Question regarding xen networking (bonding, xen-bridging) X-BeenThere: xen-users@lists.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 Am 18.02.2013 13:33, schrieb Simon Hobson: > Jonas Meurer wrote: > >> On the dom0 LAN connection works as expected. Gateway responds, >>connection to the internet works. Dom0 and domU see each other. >> >>But from domU, everything beyond the dom0 is unreachable, e.g. the >>gateway doesn't respond. MAC address from the domU is propagated to >>switches and gateway, I can see it in the arp table. In other words, >> the >>packets from domU find their way out, but the responding packets >> don't >>find their way back. A quick look at the iptables rules on dom0 give >> me >>the impression, that dom0 doesn't know how to handle packets for >> domU: >> >># iptables -L FORWARD >>Chain FORWARD (policy ACCEPT) >>target prot opt source destination >>ACCEPT all -- anywhere anywhere PHYSDEV match --physdev-out >>vif1.0 --physdev-is-bridged >>ACCEPT udp -- anywhere anywhere PHYSDEV match --physdev-in >>vif1.0 --physdev-is-bridged udp spt:bootpc dpt:bootps >>ACCEPT all -- anywhere anywhere PHYSDEV match --physdev-out >>vif1.0 --physdev-is-bridged >>ACCEPT all -- anywhere PHYSDEV match --physdev-in >>vif1.0 --physdev-is-bridged >> >> >>The last rule seems to accept packets with domU-IP as source, but I >>cannot find a rule which handles incoming packets for domU. In other >>words, the dom0 doesn't know what to do with packets for the domU. Is >> my >>assumption correct? If yes, why is this the case? Is it related to >>interface bonding? > > I think you've answered your own question there. For testing > purposes, clear iptables and see if everything starts working. > > There is something in the standard scripts that is supposed to > manipulate iptables rules when guest domains are started/stopped > (there is the option of specifying "ip-a.b.c.d" in the VIF > declaration), but I've never looked into it. Hello Simon, Thanks for the quick response. For some unknown reason, suddenly the setup started to work. Maybe I didn't wait long enough for the switches to accept the new domU as devices. Whatever, below is the dom0 interface setup that works for me (as reference for the future): /etc/network/interfaces: --8-<----8-<----8-<----8-<----8-<----8-<----8-<-- auto bond0 iface bond0 inet manual slaves eth0 eth1 bond_mode balance-xor bond_miimon 100 bond_downdelay 200 bond_updelay 200 auto xenbr0 iface xenbr0 inet static bridge_ports bond0 bridge_maxwait 0 bridge_stp off bridge_fd 0 address netmask network broadcast gateway -->-8---->-8---->-8---->-8---->-8---->-8---->-8-- I didn't modify the iptables rules created by xen helper scripts: # iptables-save --8-<----8-<----8-<----8-<----8-<----8-<----8-<-- -A FORWARD -m physdev --physdev-out vif2.0 --physdev-is-bridged -j ACCEPT -A FORWARD -p udp -m physdev --physdev-in vif2.0 --physdev-is-bridged -m udp --sport 68 --dport 67 -j ACCEPT -A FORWARD -m physdev --physdev-out vif2.0 --physdev-is-bridged -j ACCEPT -A FORWARD -s /32 -m physdev --physdev-in vif2.0 --physdev-is-bridged -j ACCEPT -->-8---->-8---->-8---->-8---->-8---->-8---->-8-- Kind regards, jonas _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Mon Feb 18 14:34:11 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 18 Feb 2013 14:34: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 1U7RmP-0007YD-QK; Mon, 18 Feb 2013 14:33:17 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U7RmO-0007Y7-Gz for xen-users@lists.xen.org; Mon, 18 Feb 2013 14:33:16 +0000 Received: from [85.158.143.99:4176] by server-1.bemta-4.messagelabs.com id 55/EF-08839-BAB32215; Mon, 18 Feb 2013 14:33:15 +0000 X-Env-Sender: mliebherr99@googlemail.com X-Msg-Ref: server-12.tower-216.messagelabs.com!1361197993!22764905!1 X-Originating-IP: [209.85.212.177] X-SpamReason: No, hits=0.8 required=7.0 tests=BODY_RANDOM_LONG, RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 4779 invoked from network); 18 Feb 2013 14:33:14 -0000 Received: from mail-wi0-f177.google.com (HELO mail-wi0-f177.google.com) (209.85.212.177) by server-12.tower-216.messagelabs.com with RC4-SHA encrypted SMTP; 18 Feb 2013 14:33:14 -0000 Received: by mail-wi0-f177.google.com with SMTP id hm14so3575704wib.16 for ; Mon, 18 Feb 2013 06:33:13 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=20120113; h=mime-version:x-received:date:message-id:subject:from:to :content-type; bh=mZugA9IkRBaGPW2OrwFjPpBEIXi5h0Y0E+DPYSAwsmU=; b=Gv9w8Mn/c9Y3D8K46qG7e5GZLynfwIkNsNUwRAbTI/X+ywtnmGf7/Ub9kMYUutetst zcR+Ufgs0NisUKRW0HsCa/TrHYy97TsxC6PH4wkS6iyegk9EcBnNAmO19aiifsIFTmbe Fni9amFEUnq2jb3lzxgAWEG0OOiPQ4blfD0pLRozIZtWSOtgfebzJafLqrzi5GN+y2b3 CGoFiqJ86gHYiCvLxvk13kIzLrMoAli9FF/Dmx85Snk0YUeKsjyPEal8Np3Nc+Q6C5MR 3G6WsJoSxhoooJdtkSt3vkCmLmSnWvZxObrR5g/w2s6FyrRJvciO9hHSGGfOFm9BN4+P Q/6Q== MIME-Version: 1.0 X-Received: by 10.180.87.98 with SMTP id w2mr18847484wiz.30.1361197985249; Mon, 18 Feb 2013 06:33:05 -0800 (PST) Received: by 10.227.100.194 with HTTP; Mon, 18 Feb 2013 06:33:05 -0800 (PST) Date: Mon, 18 Feb 2013 15:33:05 +0100 Message-ID: From: ml ml To: xen-users@lists.xen.org Subject: [Xen-users] Kernel Error with Debian Squeeze, DRBD, 3.2.0-0.bpo.4-amd64 and Xen4.0 X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: 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 List, i am running Debian Squeeze and i installed DRBD, 3.2.0-0.bpo.4-amd64 and Xen4.0 from the Backports. Sometimes i get such ugly Kernel message: [257318.441757] BUG: unable to handle kernel paging request at ffff880025f19000 Log: [256820.643918] xen-blkback:ring-ref 772, event-channel 16, protocol 1 (x86_64-abi) [256830.802492] vif86.0: no IPv6 routers present [256835.674481] br-vlan111: port 2(vif86.0) entering forwarding state [257035.389461] block drbd0: peer( Secondary -> Primary ) [257035.404098] block drbd2: peer( Secondary -> Primary ) [257035.431535] block drbd1: peer( Secondary -> Primary ) [257199.267429] br-vlan111: port 2(vif86.0) entering forwarding state [257199.267622] device vif86.0 left promiscuous mode [257199.267664] br-vlan111: port 2(vif86.0) entering disabled state [257199.337808] block drbd0: role( Primary -> Secondary ) [257199.337896] block drbd0: bitmap WRITE of 0 pages took 0 jiffies [257199.337963] block drbd0: 0 KB (0 bits) marked out-of-sync by on disk bit-map. [257199.344910] block drbd2: role( Primary -> Secondary ) [257199.344992] block drbd2: bitmap WRITE of 0 pages took 0 jiffies [257199.345042] block drbd2: 0 KB (0 bits) marked out-of-sync by on disk bit-map. [257199.345709] xt_physdev: using --physdev-out in the OUTPUT, FORWARD and POSTROUTING chains for non-bridged traffic is not supported anymore. [257199.345796] xt_physdev: using --physdev-out in the OUTPUT, FORWARD and POSTROUTING chains for non-bridged traffic is not supported anymore. [257199.349213] xt_physdev: using --physdev-out in the OUTPUT, FORWARD and POSTROUTING chains for non-bridged traffic is not supported anymore. [257199.351852] block drbd1: role( Primary -> Secondary ) [257199.351944] block drbd1: bitmap WRITE of 0 pages took 0 jiffies [257199.351999] block drbd1: 0 KB (0 bits) marked out-of-sync by on disk bit-map. [257318.388508] device vif87.0 entered promiscuous mode [257318.392558] ADDRCONF(NETDEV_UP): vif87.0: link is not ready [257318.404746] block drbd0: role( Secondary -> Primary ) [257318.408416] xt_physdev: using --physdev-out in the OUTPUT, FORWARD and POSTROUTING chains for non-bridged traffic is not supported anymore. [257318.411760] xt_physdev: using --physdev-out in the OUTPUT, FORWARD and POSTROUTING chains for non-bridged traffic is not supported anymore. [257318.411868] xt_physdev: using --physdev-out in the OUTPUT, FORWARD and POSTROUTING chains for non-bridged traffic is not supported anymore. [257318.422198] block drbd2: role( Secondary -> Primary ) [257318.434969] block drbd1: role( Secondary -> Primary ) [257318.441757] BUG: unable to handle kernel paging request at ffff880025f19000 [257318.441819] IP: [] __sanitize_i387_state+0x24/0xe1 [257318.441881] PGD 1606067 PUD 160a067 PMD d13067 PTE 0 [257318.441950] Oops: 0000 [#10] SMP [257318.442006] CPU 22 [257318.442020] Modules linked in: drbd loop nf_conntrack_ipv4 nf_defrag_ipv4 xt_state nf_conntrack xt_physdev iptable_filter ip_tables x_tables xen_netback xen_blkback lru_cache xen_evtchn xenfs bridge 8021q garp stp bonding coretemp crc32c_intel ghash_clmulni_intel aesni_intel snd_pcm cryptd aes_x86_64 snd_timer aes_generic snd soundcore snd_page_alloc pcspkr cdc_ether usbnet joydev evdev mii i2c_i801 i2c_core shpchp ioatdma dca tpm_tis tpm tpm_bios wmi button acpi_cpufreq mperf processor thermal_sys ext3 jbd mbcache dm_mod sg sr_mod cdrom sd_mod crc_t10dif usbhid hid usb_storage ehci_hcd usbcore usb_common mpt2sas scsi_transport_sas raid_class be2net scsi_mod [last unloaded: drbd] [257318.442892] [257318.442926] Pid: 20138, comm: block-drbd Tainted: G D 3.2.0-0.bpo.4-amd64 #1 Debian 3.2.35-2~bpo60+1 IBM BladeCenter HS23 -[7875B3G]-/46C9222 [257318.443031] RIP: e030:[] [] __sanitize_i387_state+0x24/0xe1 [257318.443110] RSP: e02b:ffff880026cbfe10 EFLAGS: 00010246 [257318.443152] RAX: 0000000000000000 RBX: 00007fffc4e0d900 RCX: 0000000000000200 [257318.443226] RDX: ffff880025f18e00 RSI: ffff880026cbffd8 RDI: ffff8800284d7690 [257318.443298] RBP: ffff8800284d7690 R08: ffff88003ede77e0 R09: 0000000000000004 [257318.443368] R10: 0000000000000000 R11: ffffffff81004531 R12: 0000000000000000 [257318.443438] R13: 00007fffc4e0d738 R14: ffff8800284d7690 R15: 00007fffc4e0d900 [257318.443510] FS: 00007f7590b92700(0000) GS:ffff88003a0c0000(0000) knlGS:0000000000000000 [257318.443581] CS: e033 DS: 0000 ES: 0000 CR0: 000000008005003b [257318.443624] CR2: ffff880025f19000 CR3: 000000000254e000 CR4: 0000000000002660 [257318.443697] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 [257318.443766] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400 [257318.443835] Process block-drbd (pid: 20138, threadinfo ffff880026cbe000, task ffff8800284d7690) [257318.443909] Stack: [257318.443947] ffffffff81015f54 ffff880026cbff58 0000000000000011 ffff8800284d7b30 [257318.444045] ffffffff8100e132 0000000000000000 ffff8800284d7690 0000000000000011 [257318.444140] 0000000000040001 0000000000004eae ffff880000000000 0000000000000000 [257318.444237] Call Trace: [257318.444274] [] ? save_i387_xstate+0x118/0x1e2 [257318.444321] [] ? do_signal+0x21f/0x635 [257318.444365] [] ? wake_up_new_task+0x96/0xc2 [257318.444410] [] ? do_notify_resume+0x25/0x67 [257318.444455] [] ? sys_read+0x45/0x6e [257318.444499] [] ? int_signal+0x12/0x17 [257318.444541] Code: c1 ea 20 0f 01 d1 c3 48 8b 97 58 04 00 00 48 85 d2 0f 84 d0 00 00 00 83 bf 50 04 00 00 00 74 04 0f 0b eb fe 48 8b 05 b1 a7 72 00 <48> 8b b2 00 02 00 00 48 89 c1 48 21 f1 48 39 c1 0f 84 a6 00 00 [257318.445078] RIP [] __sanitize_i387_state+0x24/0xe1 [257318.445128] RSP [257318.445165] CR2: ffff880025f19000 [257318.445648] ---[ end trace 26d0e86b7e73aaf1 ]--- [257481.553642] br-vlan111: port 2(vif87.0) entering disabled state [257481.554004] device vif87.0 left promiscuous mode [257481.554128] br-vlan111: port 2(vif87.0) entering disabled state [257481.633747] block drbd0: role( Primary -> Secondary ) [257481.633888] block drbd0: bitmap WRITE of 0 pages took 0 jiffies [257481.634009] block drbd0: 0 KB (0 bits) marked out-of-sync by on disk bit-map. [257481.636098] block drbd2: role( Primary -> Secondary ) [257481.636254] block drbd2: bitmap WRITE of 0 pages took 0 jiffies [257481.636368] block drbd2: 0 KB (0 bits) marked out-of-sync by on disk bit-map. [257481.638277] xt_physdev: using --physdev-out in the OUTPUT, FORWARD and POSTROUTING chains for non-bridged traffic is not supported anymore. [257481.638502] xt_physdev: using --physdev-out in the OUTPUT, FORWARD and POSTROUTING chains for non-bridged traffic is not supported anymore. [257481.642140] xt_physdev: using --physdev-out in the OUTPUT, FORWARD and POSTROUTING chains for non-bridged traffic is not supported anymore. [257481.643226] block drbd1: role( Primary -> Secondary ) [257481.643407] block drbd1: bitmap WRITE of 0 pages took 0 jiffies [257481.643533] block drbd1: 0 KB (0 bits) marked out-of-sync by on disk bit-map. [257483.545207] block drbd0: peer( Primary -> Secondary ) [257483.546821] block drbd2: peer( Primary -> Secondary ) [257483.556219] block drbd1: peer( Primary -> Secondary ) [257486.503136] device vif88.0 entered promiscuous mode [257486.507545] ADDRCONF(NETDEV_UP): vif88.0: link is not ready [257486.518673] block drbd0: role( Secondary -> Primary ) [257486.523460] xt_physdev: using --physdev-out in the OUTPUT, FORWARD and POSTROUTING chains for non-bridged traffic is not supported anymore. [257486.526926] xt_physdev: using --physdev-out in the OUTPUT, FORWARD and POSTROUTING chains for non-bridged traffic is not supported anymore. [257486.527083] xt_physdev: using --physdev-out in the OUTPUT, FORWARD and POSTROUTING chains for non-bridged traffic is not supported anymore. [257486.535652] block drbd2: role( Secondary -> Primary ) [257486.551319] block drbd1: role( Secondary -> Primary ) [257490.246194] xen-blkback:ring-ref 8, event-channel 13, protocol 1 (x86_64-abi) [257490.253751] xen-blkback:ring-ref 9, event-channel 14, protocol 1 (x86_64-abi) [257490.261218] xen-blkback:ring-ref 768, event-channel 15, protocol 1 (x86_64-abi) [257490.279022] ADDRCONF(NETDEV_CHANGE): vif88.0: link becomes ready [257490.279165] br-vlan111: port 2(vif88.0) entering forwarding state [257490.279267] br-vlan111: port 2(vif88.0) entering forwarding state [257500.398520] vif88.0: no IPv6 routers present [257505.310541] br-vlan111: port 2(vif88.0) entering forwarding state [257926.392591] block drbd0: peer( Secondary -> Primary ) [257926.407140] block drbd2: peer( Secondary -> Primary ) Does anyone have an idea where it could come from? Thanks, Mario _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Mon Feb 18 14:34:11 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 18 Feb 2013 14:34: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 1U7RmP-0007YD-QK; Mon, 18 Feb 2013 14:33:17 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U7RmO-0007Y7-Gz for xen-users@lists.xen.org; Mon, 18 Feb 2013 14:33:16 +0000 Received: from [85.158.143.99:4176] by server-1.bemta-4.messagelabs.com id 55/EF-08839-BAB32215; Mon, 18 Feb 2013 14:33:15 +0000 X-Env-Sender: mliebherr99@googlemail.com X-Msg-Ref: server-12.tower-216.messagelabs.com!1361197993!22764905!1 X-Originating-IP: [209.85.212.177] X-SpamReason: No, hits=0.8 required=7.0 tests=BODY_RANDOM_LONG, RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 4779 invoked from network); 18 Feb 2013 14:33:14 -0000 Received: from mail-wi0-f177.google.com (HELO mail-wi0-f177.google.com) (209.85.212.177) by server-12.tower-216.messagelabs.com with RC4-SHA encrypted SMTP; 18 Feb 2013 14:33:14 -0000 Received: by mail-wi0-f177.google.com with SMTP id hm14so3575704wib.16 for ; Mon, 18 Feb 2013 06:33:13 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=20120113; h=mime-version:x-received:date:message-id:subject:from:to :content-type; bh=mZugA9IkRBaGPW2OrwFjPpBEIXi5h0Y0E+DPYSAwsmU=; b=Gv9w8Mn/c9Y3D8K46qG7e5GZLynfwIkNsNUwRAbTI/X+ywtnmGf7/Ub9kMYUutetst zcR+Ufgs0NisUKRW0HsCa/TrHYy97TsxC6PH4wkS6iyegk9EcBnNAmO19aiifsIFTmbe Fni9amFEUnq2jb3lzxgAWEG0OOiPQ4blfD0pLRozIZtWSOtgfebzJafLqrzi5GN+y2b3 CGoFiqJ86gHYiCvLxvk13kIzLrMoAli9FF/Dmx85Snk0YUeKsjyPEal8Np3Nc+Q6C5MR 3G6WsJoSxhoooJdtkSt3vkCmLmSnWvZxObrR5g/w2s6FyrRJvciO9hHSGGfOFm9BN4+P Q/6Q== MIME-Version: 1.0 X-Received: by 10.180.87.98 with SMTP id w2mr18847484wiz.30.1361197985249; Mon, 18 Feb 2013 06:33:05 -0800 (PST) Received: by 10.227.100.194 with HTTP; Mon, 18 Feb 2013 06:33:05 -0800 (PST) Date: Mon, 18 Feb 2013 15:33:05 +0100 Message-ID: From: ml ml To: xen-users@lists.xen.org Subject: [Xen-users] Kernel Error with Debian Squeeze, DRBD, 3.2.0-0.bpo.4-amd64 and Xen4.0 X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: 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 List, i am running Debian Squeeze and i installed DRBD, 3.2.0-0.bpo.4-amd64 and Xen4.0 from the Backports. Sometimes i get such ugly Kernel message: [257318.441757] BUG: unable to handle kernel paging request at ffff880025f19000 Log: [256820.643918] xen-blkback:ring-ref 772, event-channel 16, protocol 1 (x86_64-abi) [256830.802492] vif86.0: no IPv6 routers present [256835.674481] br-vlan111: port 2(vif86.0) entering forwarding state [257035.389461] block drbd0: peer( Secondary -> Primary ) [257035.404098] block drbd2: peer( Secondary -> Primary ) [257035.431535] block drbd1: peer( Secondary -> Primary ) [257199.267429] br-vlan111: port 2(vif86.0) entering forwarding state [257199.267622] device vif86.0 left promiscuous mode [257199.267664] br-vlan111: port 2(vif86.0) entering disabled state [257199.337808] block drbd0: role( Primary -> Secondary ) [257199.337896] block drbd0: bitmap WRITE of 0 pages took 0 jiffies [257199.337963] block drbd0: 0 KB (0 bits) marked out-of-sync by on disk bit-map. [257199.344910] block drbd2: role( Primary -> Secondary ) [257199.344992] block drbd2: bitmap WRITE of 0 pages took 0 jiffies [257199.345042] block drbd2: 0 KB (0 bits) marked out-of-sync by on disk bit-map. [257199.345709] xt_physdev: using --physdev-out in the OUTPUT, FORWARD and POSTROUTING chains for non-bridged traffic is not supported anymore. [257199.345796] xt_physdev: using --physdev-out in the OUTPUT, FORWARD and POSTROUTING chains for non-bridged traffic is not supported anymore. [257199.349213] xt_physdev: using --physdev-out in the OUTPUT, FORWARD and POSTROUTING chains for non-bridged traffic is not supported anymore. [257199.351852] block drbd1: role( Primary -> Secondary ) [257199.351944] block drbd1: bitmap WRITE of 0 pages took 0 jiffies [257199.351999] block drbd1: 0 KB (0 bits) marked out-of-sync by on disk bit-map. [257318.388508] device vif87.0 entered promiscuous mode [257318.392558] ADDRCONF(NETDEV_UP): vif87.0: link is not ready [257318.404746] block drbd0: role( Secondary -> Primary ) [257318.408416] xt_physdev: using --physdev-out in the OUTPUT, FORWARD and POSTROUTING chains for non-bridged traffic is not supported anymore. [257318.411760] xt_physdev: using --physdev-out in the OUTPUT, FORWARD and POSTROUTING chains for non-bridged traffic is not supported anymore. [257318.411868] xt_physdev: using --physdev-out in the OUTPUT, FORWARD and POSTROUTING chains for non-bridged traffic is not supported anymore. [257318.422198] block drbd2: role( Secondary -> Primary ) [257318.434969] block drbd1: role( Secondary -> Primary ) [257318.441757] BUG: unable to handle kernel paging request at ffff880025f19000 [257318.441819] IP: [] __sanitize_i387_state+0x24/0xe1 [257318.441881] PGD 1606067 PUD 160a067 PMD d13067 PTE 0 [257318.441950] Oops: 0000 [#10] SMP [257318.442006] CPU 22 [257318.442020] Modules linked in: drbd loop nf_conntrack_ipv4 nf_defrag_ipv4 xt_state nf_conntrack xt_physdev iptable_filter ip_tables x_tables xen_netback xen_blkback lru_cache xen_evtchn xenfs bridge 8021q garp stp bonding coretemp crc32c_intel ghash_clmulni_intel aesni_intel snd_pcm cryptd aes_x86_64 snd_timer aes_generic snd soundcore snd_page_alloc pcspkr cdc_ether usbnet joydev evdev mii i2c_i801 i2c_core shpchp ioatdma dca tpm_tis tpm tpm_bios wmi button acpi_cpufreq mperf processor thermal_sys ext3 jbd mbcache dm_mod sg sr_mod cdrom sd_mod crc_t10dif usbhid hid usb_storage ehci_hcd usbcore usb_common mpt2sas scsi_transport_sas raid_class be2net scsi_mod [last unloaded: drbd] [257318.442892] [257318.442926] Pid: 20138, comm: block-drbd Tainted: G D 3.2.0-0.bpo.4-amd64 #1 Debian 3.2.35-2~bpo60+1 IBM BladeCenter HS23 -[7875B3G]-/46C9222 [257318.443031] RIP: e030:[] [] __sanitize_i387_state+0x24/0xe1 [257318.443110] RSP: e02b:ffff880026cbfe10 EFLAGS: 00010246 [257318.443152] RAX: 0000000000000000 RBX: 00007fffc4e0d900 RCX: 0000000000000200 [257318.443226] RDX: ffff880025f18e00 RSI: ffff880026cbffd8 RDI: ffff8800284d7690 [257318.443298] RBP: ffff8800284d7690 R08: ffff88003ede77e0 R09: 0000000000000004 [257318.443368] R10: 0000000000000000 R11: ffffffff81004531 R12: 0000000000000000 [257318.443438] R13: 00007fffc4e0d738 R14: ffff8800284d7690 R15: 00007fffc4e0d900 [257318.443510] FS: 00007f7590b92700(0000) GS:ffff88003a0c0000(0000) knlGS:0000000000000000 [257318.443581] CS: e033 DS: 0000 ES: 0000 CR0: 000000008005003b [257318.443624] CR2: ffff880025f19000 CR3: 000000000254e000 CR4: 0000000000002660 [257318.443697] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 [257318.443766] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400 [257318.443835] Process block-drbd (pid: 20138, threadinfo ffff880026cbe000, task ffff8800284d7690) [257318.443909] Stack: [257318.443947] ffffffff81015f54 ffff880026cbff58 0000000000000011 ffff8800284d7b30 [257318.444045] ffffffff8100e132 0000000000000000 ffff8800284d7690 0000000000000011 [257318.444140] 0000000000040001 0000000000004eae ffff880000000000 0000000000000000 [257318.444237] Call Trace: [257318.444274] [] ? save_i387_xstate+0x118/0x1e2 [257318.444321] [] ? do_signal+0x21f/0x635 [257318.444365] [] ? wake_up_new_task+0x96/0xc2 [257318.444410] [] ? do_notify_resume+0x25/0x67 [257318.444455] [] ? sys_read+0x45/0x6e [257318.444499] [] ? int_signal+0x12/0x17 [257318.444541] Code: c1 ea 20 0f 01 d1 c3 48 8b 97 58 04 00 00 48 85 d2 0f 84 d0 00 00 00 83 bf 50 04 00 00 00 74 04 0f 0b eb fe 48 8b 05 b1 a7 72 00 <48> 8b b2 00 02 00 00 48 89 c1 48 21 f1 48 39 c1 0f 84 a6 00 00 [257318.445078] RIP [] __sanitize_i387_state+0x24/0xe1 [257318.445128] RSP [257318.445165] CR2: ffff880025f19000 [257318.445648] ---[ end trace 26d0e86b7e73aaf1 ]--- [257481.553642] br-vlan111: port 2(vif87.0) entering disabled state [257481.554004] device vif87.0 left promiscuous mode [257481.554128] br-vlan111: port 2(vif87.0) entering disabled state [257481.633747] block drbd0: role( Primary -> Secondary ) [257481.633888] block drbd0: bitmap WRITE of 0 pages took 0 jiffies [257481.634009] block drbd0: 0 KB (0 bits) marked out-of-sync by on disk bit-map. [257481.636098] block drbd2: role( Primary -> Secondary ) [257481.636254] block drbd2: bitmap WRITE of 0 pages took 0 jiffies [257481.636368] block drbd2: 0 KB (0 bits) marked out-of-sync by on disk bit-map. [257481.638277] xt_physdev: using --physdev-out in the OUTPUT, FORWARD and POSTROUTING chains for non-bridged traffic is not supported anymore. [257481.638502] xt_physdev: using --physdev-out in the OUTPUT, FORWARD and POSTROUTING chains for non-bridged traffic is not supported anymore. [257481.642140] xt_physdev: using --physdev-out in the OUTPUT, FORWARD and POSTROUTING chains for non-bridged traffic is not supported anymore. [257481.643226] block drbd1: role( Primary -> Secondary ) [257481.643407] block drbd1: bitmap WRITE of 0 pages took 0 jiffies [257481.643533] block drbd1: 0 KB (0 bits) marked out-of-sync by on disk bit-map. [257483.545207] block drbd0: peer( Primary -> Secondary ) [257483.546821] block drbd2: peer( Primary -> Secondary ) [257483.556219] block drbd1: peer( Primary -> Secondary ) [257486.503136] device vif88.0 entered promiscuous mode [257486.507545] ADDRCONF(NETDEV_UP): vif88.0: link is not ready [257486.518673] block drbd0: role( Secondary -> Primary ) [257486.523460] xt_physdev: using --physdev-out in the OUTPUT, FORWARD and POSTROUTING chains for non-bridged traffic is not supported anymore. [257486.526926] xt_physdev: using --physdev-out in the OUTPUT, FORWARD and POSTROUTING chains for non-bridged traffic is not supported anymore. [257486.527083] xt_physdev: using --physdev-out in the OUTPUT, FORWARD and POSTROUTING chains for non-bridged traffic is not supported anymore. [257486.535652] block drbd2: role( Secondary -> Primary ) [257486.551319] block drbd1: role( Secondary -> Primary ) [257490.246194] xen-blkback:ring-ref 8, event-channel 13, protocol 1 (x86_64-abi) [257490.253751] xen-blkback:ring-ref 9, event-channel 14, protocol 1 (x86_64-abi) [257490.261218] xen-blkback:ring-ref 768, event-channel 15, protocol 1 (x86_64-abi) [257490.279022] ADDRCONF(NETDEV_CHANGE): vif88.0: link becomes ready [257490.279165] br-vlan111: port 2(vif88.0) entering forwarding state [257490.279267] br-vlan111: port 2(vif88.0) entering forwarding state [257500.398520] vif88.0: no IPv6 routers present [257505.310541] br-vlan111: port 2(vif88.0) entering forwarding state [257926.392591] block drbd0: peer( Secondary -> Primary ) [257926.407140] block drbd2: peer( Secondary -> Primary ) Does anyone have an idea where it could come from? Thanks, Mario _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Mon Feb 18 15:19:29 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 18 Feb 2013 15:19: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 1U7SUJ-00012y-BY; Mon, 18 Feb 2013 15:18:39 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U7SUG-00012Q-PH; Mon, 18 Feb 2013 15:18:36 +0000 Received: from [193.109.254.147:60744] by server-10.bemta-14.messagelabs.com id B5/1A-12679-B4642215; Mon, 18 Feb 2013 15:18:35 +0000 X-Env-Sender: wei.liu2@citrix.com X-Msg-Ref: server-9.tower-27.messagelabs.com!1361200455!8799605!1 X-Originating-IP: [66.165.176.89] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjYuMTY1LjE3Ni44OSA9PiAxOTk1MzQ=\n X-StarScan-Received: X-StarScan-Version: 6.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 7906 invoked from network); 18 Feb 2013 15:14:17 -0000 Received: from smtp.citrix.com (HELO SMTP.CITRIX.COM) (66.165.176.89) by server-9.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 18 Feb 2013 15:14:17 -0000 X-IronPort-AV: E=Sophos;i="4.84,688,1355097600"; d="scan'208";a="8008026" Received: from accessns.citrite.net (HELO FTLPEX01CL01.citrite.net) ([10.9.154.239]) by FTLPIPO01.CITRIX.COM with ESMTP/TLS/AES128-SHA; 18 Feb 2013 15:14:14 +0000 Received: from ukmail1.uk.xensource.com (10.80.16.128) by smtprelay.citrix.com (10.13.107.78) with Microsoft SMTP Server id 14.2.318.1; Mon, 18 Feb 2013 10:14:14 -0500 Received: from zion.uk.xensource.com ([10.80.2.73]) by ukmail1.uk.xensource.com with esmtp (Exim 4.69) (envelope-from ) id 1U7SQ1-0004CI-U7; Mon, 18 Feb 2013 15:14:13 +0000 Message-ID: <1361200453.3825.19.camel@zion.uk.xensource.com> From: Wei Liu To: "xen-devel@lists.xen.org" , , "xen-users@lists.xen.org" , Date: Mon, 18 Feb 2013 15:14:13 +0000 X-Mailer: Evolution 3.6.2 (3.6.2-3.fc18) MIME-Version: 1.0 Cc: "lars.kurth@xen.org" , wei.liu2@citrix.com Subject: [Xen-users] Xen Document Day: Feb 25th, 2013 on IRC freenode #xendocs X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: 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 everybody A quick reminder that the next Xen Document Day is happening next Monday (Feb 25). 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. Best Regards Wei. ********************* * 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! _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Mon Feb 18 15:19:29 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 18 Feb 2013 15:19: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 1U7SUJ-00012y-BY; Mon, 18 Feb 2013 15:18:39 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U7SUG-00012Q-PH; Mon, 18 Feb 2013 15:18:36 +0000 Received: from [193.109.254.147:60744] by server-10.bemta-14.messagelabs.com id B5/1A-12679-B4642215; Mon, 18 Feb 2013 15:18:35 +0000 X-Env-Sender: wei.liu2@citrix.com X-Msg-Ref: server-9.tower-27.messagelabs.com!1361200455!8799605!1 X-Originating-IP: [66.165.176.89] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjYuMTY1LjE3Ni44OSA9PiAxOTk1MzQ=\n X-StarScan-Received: X-StarScan-Version: 6.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 7906 invoked from network); 18 Feb 2013 15:14:17 -0000 Received: from smtp.citrix.com (HELO SMTP.CITRIX.COM) (66.165.176.89) by server-9.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 18 Feb 2013 15:14:17 -0000 X-IronPort-AV: E=Sophos;i="4.84,688,1355097600"; d="scan'208";a="8008026" Received: from accessns.citrite.net (HELO FTLPEX01CL01.citrite.net) ([10.9.154.239]) by FTLPIPO01.CITRIX.COM with ESMTP/TLS/AES128-SHA; 18 Feb 2013 15:14:14 +0000 Received: from ukmail1.uk.xensource.com (10.80.16.128) by smtprelay.citrix.com (10.13.107.78) with Microsoft SMTP Server id 14.2.318.1; Mon, 18 Feb 2013 10:14:14 -0500 Received: from zion.uk.xensource.com ([10.80.2.73]) by ukmail1.uk.xensource.com with esmtp (Exim 4.69) (envelope-from ) id 1U7SQ1-0004CI-U7; Mon, 18 Feb 2013 15:14:13 +0000 Message-ID: <1361200453.3825.19.camel@zion.uk.xensource.com> From: Wei Liu To: "xen-devel@lists.xen.org" , , "xen-users@lists.xen.org" , Date: Mon, 18 Feb 2013 15:14:13 +0000 X-Mailer: Evolution 3.6.2 (3.6.2-3.fc18) MIME-Version: 1.0 Cc: "lars.kurth@xen.org" , wei.liu2@citrix.com Subject: [Xen-users] Xen Document Day: Feb 25th, 2013 on IRC freenode #xendocs X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: 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 everybody A quick reminder that the next Xen Document Day is happening next Monday (Feb 25). 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. Best Regards Wei. ********************* * 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! _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Mon Feb 18 16:06:16 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 18 Feb 2013 16:06: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 1U7TDT-00043N-Jl; Mon, 18 Feb 2013 16:05:19 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U7TDS-00043E-OP for xen-users@lists.xen.org; Mon, 18 Feb 2013 16:05:18 +0000 Received: from [193.109.254.147:13751] by server-11.bemta-14.messagelabs.com id 93/68-30685-E3152215; Mon, 18 Feb 2013 16:05:18 +0000 X-Env-Sender: alk@ondore.com X-Msg-Ref: server-15.tower-27.messagelabs.com!1361203515!1904056!1 X-Originating-IP: [184.172.38.138] X-SpamReason: No, hits=0.5 required=7.0 tests=BODY_RANDOM_LONG X-StarScan-Received: X-StarScan-Version: 6.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 21368 invoked from network); 18 Feb 2013 16:05:16 -0000 Received: from host0a.ondore-systems.com (HELO host0a.ondore-systems.com) (184.172.38.138) by server-15.tower-27.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 18 Feb 2013 16:05:16 -0000 Received: from [201.122.115.101] (port=50795 helo=mail.ondore.i) by host0a.ondore-systems.com with esmtpsa (TLSv1:DHE-RSA-AES256-SHA:256) (Exim 4.80) (envelope-from ) id 1U7TDO-0007qy-Hz for xen-users@lists.xen.org; Mon, 18 Feb 2013 10:05:14 -0600 Received: from [10.13.34.96] (alk-desktop.sys.ondore.i [10.13.34.96]) by mail.ondore.i (Postfix) with ESMTPSA id 6D4E3A209 for ; Mon, 18 Feb 2013 10:01:01 -0600 (CST) Message-ID: <51225139.3000201@ondore.com> Date: Mon, 18 Feb 2013 10:05:13 -0600 From: Alexandre Kouznetsov User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130106 Thunderbird/17.0.2 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 X-Get-Message-Sender-Via: host0a.ondore-systems.com: authenticated_id: sys.intranet@ondore.com Subject: Re: [Xen-users] Question regarding xen networking (bonding, xen-bridging) X-BeenThere: xen-users@lists.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. El 18/02/13 05:47, Jonas Meurer escribi=F3: > On the dom0 LAN connection works as expected. Gateway responds, > connection to the internet works. Dom0 and domU see each other. Make sure, the DomU's interface is really attached to the intended bridge. xm list brctl show > But from domU, everything beyond the dom0 is unreachable, e.g. the > gateway doesn't respond. MAC address from the domU is propagated to > switches and gateway, I can see it in the arp table. In other words, the > packets from domU find their way out, but the responding packets don't > find their way back. Double check your routing and ipfilter (or whatever) configuration on = your DomU and the gateway. This is the most common cause of issues with = this description. > A quick look at the iptables rules on dom0 give me > the impression, that dom0 doesn't know how to handle packets for domU: > > # iptables -L FORWARD > Chain FORWARD (policy ACCEPT) > target prot opt source destination > ACCEPT all -- anywhere anywhere PHYSDEV match --physdev-out > vif1.0 --physdev-is-bridged > ACCEPT udp -- anywhere anywhere PHYSDEV match --physdev-in > vif1.0 --physdev-is-bridged udp spt:bootpc dpt:bootps > ACCEPT all -- anywhere anywhere PHYSDEV match --physdev-out > vif1.0 --physdev-is-bridged > ACCEPT all -- anywhere PHYSDEV match --physdev-in > vif1.0 --physdev-is-bridged > > The last rule seems to accept packets [...] Your policy is ACCEPT. So, unless there is a specific DROP or REJECT = rule, you may count on netfilter does not prevent the packets from arriving. > with domU-IP as source, but I > cannot find a rule which handles incoming packets for domU. That is a, mostly, antyspoofing rule. Most of Xen't iptabels setup is = intended to protect the network from the DomU's, so it does not filter = incoming traffic by default. > In other > words, the dom0 doesn't know what to do with packets for the domU. Is my > assumption correct? It does not need to know a too much. It a packet made it to the bridge, = it should be picked up by the interface (member of the bridge) with the = corresponding destination MAC. That is, unless there is some filtering = preventing it, which seems not to be the case. Check with tcpdump on Dom0 (bridge) and DomU (interface). You are = supposed to see the same traffic involving your DomU's MAC address, = including the incoming responses to outgoing connections. Any difference = should bring some light to the matter. > Is it related to interface bonding? Should not. A incorrect bonding setup could prevent packets leaving = physical interface, or arriving on it. If a packet is visible on the = bridge, than it already has made it through the bond, so we may assume = it works fine, unless it looses some packets. -- = Alexandre Kouznetsov _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Mon Feb 18 16:06:16 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 18 Feb 2013 16:06: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 1U7TDT-00043N-Jl; Mon, 18 Feb 2013 16:05:19 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U7TDS-00043E-OP for xen-users@lists.xen.org; Mon, 18 Feb 2013 16:05:18 +0000 Received: from [193.109.254.147:13751] by server-11.bemta-14.messagelabs.com id 93/68-30685-E3152215; Mon, 18 Feb 2013 16:05:18 +0000 X-Env-Sender: alk@ondore.com X-Msg-Ref: server-15.tower-27.messagelabs.com!1361203515!1904056!1 X-Originating-IP: [184.172.38.138] X-SpamReason: No, hits=0.5 required=7.0 tests=BODY_RANDOM_LONG X-StarScan-Received: X-StarScan-Version: 6.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 21368 invoked from network); 18 Feb 2013 16:05:16 -0000 Received: from host0a.ondore-systems.com (HELO host0a.ondore-systems.com) (184.172.38.138) by server-15.tower-27.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 18 Feb 2013 16:05:16 -0000 Received: from [201.122.115.101] (port=50795 helo=mail.ondore.i) by host0a.ondore-systems.com with esmtpsa (TLSv1:DHE-RSA-AES256-SHA:256) (Exim 4.80) (envelope-from ) id 1U7TDO-0007qy-Hz for xen-users@lists.xen.org; Mon, 18 Feb 2013 10:05:14 -0600 Received: from [10.13.34.96] (alk-desktop.sys.ondore.i [10.13.34.96]) by mail.ondore.i (Postfix) with ESMTPSA id 6D4E3A209 for ; Mon, 18 Feb 2013 10:01:01 -0600 (CST) Message-ID: <51225139.3000201@ondore.com> Date: Mon, 18 Feb 2013 10:05:13 -0600 From: Alexandre Kouznetsov User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130106 Thunderbird/17.0.2 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 X-Get-Message-Sender-Via: host0a.ondore-systems.com: authenticated_id: sys.intranet@ondore.com Subject: Re: [Xen-users] Question regarding xen networking (bonding, xen-bridging) X-BeenThere: xen-users@lists.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. El 18/02/13 05:47, Jonas Meurer escribi=F3: > On the dom0 LAN connection works as expected. Gateway responds, > connection to the internet works. Dom0 and domU see each other. Make sure, the DomU's interface is really attached to the intended bridge. xm list brctl show > But from domU, everything beyond the dom0 is unreachable, e.g. the > gateway doesn't respond. MAC address from the domU is propagated to > switches and gateway, I can see it in the arp table. In other words, the > packets from domU find their way out, but the responding packets don't > find their way back. Double check your routing and ipfilter (or whatever) configuration on = your DomU and the gateway. This is the most common cause of issues with = this description. > A quick look at the iptables rules on dom0 give me > the impression, that dom0 doesn't know how to handle packets for domU: > > # iptables -L FORWARD > Chain FORWARD (policy ACCEPT) > target prot opt source destination > ACCEPT all -- anywhere anywhere PHYSDEV match --physdev-out > vif1.0 --physdev-is-bridged > ACCEPT udp -- anywhere anywhere PHYSDEV match --physdev-in > vif1.0 --physdev-is-bridged udp spt:bootpc dpt:bootps > ACCEPT all -- anywhere anywhere PHYSDEV match --physdev-out > vif1.0 --physdev-is-bridged > ACCEPT all -- anywhere PHYSDEV match --physdev-in > vif1.0 --physdev-is-bridged > > The last rule seems to accept packets [...] Your policy is ACCEPT. So, unless there is a specific DROP or REJECT = rule, you may count on netfilter does not prevent the packets from arriving. > with domU-IP as source, but I > cannot find a rule which handles incoming packets for domU. That is a, mostly, antyspoofing rule. Most of Xen't iptabels setup is = intended to protect the network from the DomU's, so it does not filter = incoming traffic by default. > In other > words, the dom0 doesn't know what to do with packets for the domU. Is my > assumption correct? It does not need to know a too much. It a packet made it to the bridge, = it should be picked up by the interface (member of the bridge) with the = corresponding destination MAC. That is, unless there is some filtering = preventing it, which seems not to be the case. Check with tcpdump on Dom0 (bridge) and DomU (interface). You are = supposed to see the same traffic involving your DomU's MAC address, = including the incoming responses to outgoing connections. Any difference = should bring some light to the matter. > Is it related to interface bonding? Should not. A incorrect bonding setup could prevent packets leaving = physical interface, or arriving on it. If a packet is visible on the = bridge, than it already has made it through the bond, so we may assume = it works fine, unless it looses some packets. -- = Alexandre Kouznetsov _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Mon Feb 18 16:33:45 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 18 Feb 2013 16:33: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 1U7TeA-0005Px-Rm; Mon, 18 Feb 2013 16:32:54 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U7Te8-0005Pp-Ms for xen-users@lists.xen.org; Mon, 18 Feb 2013 16:32:52 +0000 Received: from [193.109.254.147:12312] by server-15.bemta-14.messagelabs.com id 2B/70-24599-3B752215; Mon, 18 Feb 2013 16:32:51 +0000 X-Env-Sender: netmatters@gmail.com X-Msg-Ref: server-9.tower-27.messagelabs.com!1361205128!8810179!1 X-Originating-IP: [209.85.128.176] 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.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 23719 invoked from network); 18 Feb 2013 16:32:09 -0000 Received: from mail-ve0-f176.google.com (HELO mail-ve0-f176.google.com) (209.85.128.176) by server-9.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 18 Feb 2013 16:32:09 -0000 Received: by mail-ve0-f176.google.com with SMTP id cz10so4918722veb.21 for ; Mon, 18 Feb 2013 08:32:08 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:date:message-id:subject:from:to:cc :content-type; bh=UmHoOeVs6+HTGxbQmzUeBqiNsmeptQmaWvchMrluJMQ=; b=c8jwtBVDauyI74TAq+RiUxaMAjb2g6NYGZ9y9bzObKP3bUPNSaWtlKt52MGzD3qLnh qg1JZqRApvjGladcjBqG656jEOToz1evJvh/9m13oZ73wkmPpaWyGcB58HAUzAdZjz1j CbP9jeg4bTTbHbfC01apx3vsdbLI/uyqM5kL/weAQ/Gx6tSasAoj9+JgF8XwDi0yGa8o GLIHwHQ65k8BOIrg+HibT1/GLluXeaPOzTEWHiSHg2wkHx2hLozPCi/YgETzpongYJfw pZeIRGkrMETxI7fFzNl6Uu9o32tWRKT5f7fugAOYrEXFmi/zmJAscjiNrwyvDsEHi6bG 3z2Q== MIME-Version: 1.0 X-Received: by 10.52.71.174 with SMTP id w14mr14129941vdu.122.1361205128006; Mon, 18 Feb 2013 08:32:08 -0800 (PST) Received: by 10.58.106.133 with HTTP; Mon, 18 Feb 2013 08:32:07 -0800 (PST) Date: Mon, 18 Feb 2013 18:32:07 +0200 Message-ID: From: Gavin To: Ian Campbell Cc: "pkg-xen-devel@lists.alioth.debian.org" , "debian-user@lists.debian.org" , xen-users Subject: [Xen-users] [SOLVED] Re: [Pkg-xen-devel] Recent hypervisor update on Debian Wheezy breaks domU 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="===============5327288888762630562==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============5327288888762630562== Content-Type: multipart/alternative; boundary=20cf3071ce7a1f0bbb04d6024475 --20cf3071ce7a1f0bbb04d6024475 Content-Type: text/plain; charset=ISO-8859-1 On 18 February 2013 16:32, Ian Campbell wrote: > On Mon, 2013-02-18 at 13:51 +0000, Gavin wrote: > > > > > If the kernel hasn't changed and you are 100% sure the network > configuration before and after the reboot is the same then so am I. > > All I can suggest is to reinstall the previous version of Xen. > Thanks very much for all your assistance Ian, the problem was with the network. We introduced a second switch into the stack and it seems like it was our bond interface to the switch that caused this particular issue. We were using bond mode 5 since that works for us elsewhere and did not think that this could be the problem since we were seeing the arp-replies reach the host bridge interface. As per Xen recommendations I tried mode 7 but that too did not work. Once configured to use bond mode 1 (active-backup) this all started working again. Apologies for the run-around, the false accusations and also the cross-posting, have a few hours before going live with this platform and was under a fair amount of pressure. All good now!! :) Regards, Gavin > > --20cf3071ce7a1f0bbb04d6024475 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
On 18 February 2013 16:32, Ian Campbell = <ijc@hellion.org= .uk> wrote:
On Mon, 2013-02-18 at 13:51 +0000, Gavin wrote:

> <stumped! />

If the=A0kernel=A0hasn't changed and you are 100% sure the network
configuration before and after the reboot is the same then so am I.

All I can suggest is to reinstall the previous version of Xen.

Thanks very much for all your assistance Ian,= the problem was with the network.

We introduced =A0a second switch into the stack and it seems like it was ou= r bond interface to the switch that caused this particular issue.

We were using bond mode 5 since that works for = us elsewhere and did not think that this could be the problem since we were= seeing the arp-replies reach the host bridge interface.

As per Xen recommendations I tried mode 7 b= ut that too did not work.=A0

Once conf= igured to use bond mode 1 (active-backup) this all started working again.

Apologies for the run-around, the false acc= usations and also the cross-posting, have a few hours before going live wit= h this platform and was under a fair amount of pressure.

All good now!! =A0:)

Regards,
Gavin
=A0<= span>

--20cf3071ce7a1f0bbb04d6024475-- --===============5327288888762630562== 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 --===============5327288888762630562==-- From xen-users-bounces@lists.xen.org Mon Feb 18 16:33:45 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 18 Feb 2013 16:33: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 1U7TeA-0005Px-Rm; Mon, 18 Feb 2013 16:32:54 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U7Te8-0005Pp-Ms for xen-users@lists.xen.org; Mon, 18 Feb 2013 16:32:52 +0000 Received: from [193.109.254.147:12312] by server-15.bemta-14.messagelabs.com id 2B/70-24599-3B752215; Mon, 18 Feb 2013 16:32:51 +0000 X-Env-Sender: netmatters@gmail.com X-Msg-Ref: server-9.tower-27.messagelabs.com!1361205128!8810179!1 X-Originating-IP: [209.85.128.176] 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.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 23719 invoked from network); 18 Feb 2013 16:32:09 -0000 Received: from mail-ve0-f176.google.com (HELO mail-ve0-f176.google.com) (209.85.128.176) by server-9.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 18 Feb 2013 16:32:09 -0000 Received: by mail-ve0-f176.google.com with SMTP id cz10so4918722veb.21 for ; Mon, 18 Feb 2013 08:32:08 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:date:message-id:subject:from:to:cc :content-type; bh=UmHoOeVs6+HTGxbQmzUeBqiNsmeptQmaWvchMrluJMQ=; b=c8jwtBVDauyI74TAq+RiUxaMAjb2g6NYGZ9y9bzObKP3bUPNSaWtlKt52MGzD3qLnh qg1JZqRApvjGladcjBqG656jEOToz1evJvh/9m13oZ73wkmPpaWyGcB58HAUzAdZjz1j CbP9jeg4bTTbHbfC01apx3vsdbLI/uyqM5kL/weAQ/Gx6tSasAoj9+JgF8XwDi0yGa8o GLIHwHQ65k8BOIrg+HibT1/GLluXeaPOzTEWHiSHg2wkHx2hLozPCi/YgETzpongYJfw pZeIRGkrMETxI7fFzNl6Uu9o32tWRKT5f7fugAOYrEXFmi/zmJAscjiNrwyvDsEHi6bG 3z2Q== MIME-Version: 1.0 X-Received: by 10.52.71.174 with SMTP id w14mr14129941vdu.122.1361205128006; Mon, 18 Feb 2013 08:32:08 -0800 (PST) Received: by 10.58.106.133 with HTTP; Mon, 18 Feb 2013 08:32:07 -0800 (PST) Date: Mon, 18 Feb 2013 18:32:07 +0200 Message-ID: From: Gavin To: Ian Campbell Cc: "pkg-xen-devel@lists.alioth.debian.org" , "debian-user@lists.debian.org" , xen-users Subject: [Xen-users] [SOLVED] Re: [Pkg-xen-devel] Recent hypervisor update on Debian Wheezy breaks domU 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="===============5327288888762630562==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============5327288888762630562== Content-Type: multipart/alternative; boundary=20cf3071ce7a1f0bbb04d6024475 --20cf3071ce7a1f0bbb04d6024475 Content-Type: text/plain; charset=ISO-8859-1 On 18 February 2013 16:32, Ian Campbell wrote: > On Mon, 2013-02-18 at 13:51 +0000, Gavin wrote: > > > > > If the kernel hasn't changed and you are 100% sure the network > configuration before and after the reboot is the same then so am I. > > All I can suggest is to reinstall the previous version of Xen. > Thanks very much for all your assistance Ian, the problem was with the network. We introduced a second switch into the stack and it seems like it was our bond interface to the switch that caused this particular issue. We were using bond mode 5 since that works for us elsewhere and did not think that this could be the problem since we were seeing the arp-replies reach the host bridge interface. As per Xen recommendations I tried mode 7 but that too did not work. Once configured to use bond mode 1 (active-backup) this all started working again. Apologies for the run-around, the false accusations and also the cross-posting, have a few hours before going live with this platform and was under a fair amount of pressure. All good now!! :) Regards, Gavin > > --20cf3071ce7a1f0bbb04d6024475 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
On 18 February 2013 16:32, Ian Campbell = <ijc@hellion.org= .uk> wrote:
On Mon, 2013-02-18 at 13:51 +0000, Gavin wrote:

> <stumped! />

If the=A0kernel=A0hasn't changed and you are 100% sure the network
configuration before and after the reboot is the same then so am I.

All I can suggest is to reinstall the previous version of Xen.

Thanks very much for all your assistance Ian,= the problem was with the network.

We introduced =A0a second switch into the stack and it seems like it was ou= r bond interface to the switch that caused this particular issue.

We were using bond mode 5 since that works for = us elsewhere and did not think that this could be the problem since we were= seeing the arp-replies reach the host bridge interface.

As per Xen recommendations I tried mode 7 b= ut that too did not work.=A0

Once conf= igured to use bond mode 1 (active-backup) this all started working again.

Apologies for the run-around, the false acc= usations and also the cross-posting, have a few hours before going live wit= h this platform and was under a fair amount of pressure.

All good now!! =A0:)

Regards,
Gavin
=A0<= span>

--20cf3071ce7a1f0bbb04d6024475-- --===============5327288888762630562== 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 --===============5327288888762630562==-- From xen-users-bounces@lists.xen.org Mon Feb 18 18:02:38 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 18 Feb 2013 18:02: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 1U7V27-0007Xt-DN; Mon, 18 Feb 2013 18:01:43 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U7Rm3-0007XH-Tx for xen-users@lists.xen.org; Mon, 18 Feb 2013 14:32:56 +0000 Received: from [85.158.139.83:16499] by server-8.bemta-5.messagelabs.com id 44/68-19075-69B32215; Mon, 18 Feb 2013 14:32:54 +0000 X-Env-Sender: ijc@hellion.org.uk X-Msg-Ref: server-10.tower-182.messagelabs.com!1361197951!28054160!1 X-Originating-IP: [212.110.190.137] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 29103 invoked from network); 18 Feb 2013 14:32:32 -0000 Received: from benson.vm.bytemark.co.uk (HELO benson.vm.bytemark.co.uk) (212.110.190.137) by server-10.tower-182.messagelabs.com with AES256-SHA encrypted SMTP; 18 Feb 2013 14:32:32 -0000 Received: from cpc22-cmbg14-2-0-cust482.5-4.cable.virginmedia.com ([86.6.25.227] helo=hopkins.hellion.org.uk) by benson.vm.bytemark.co.uk with esmtpsa (TLS1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.72) (envelope-from ) id 1U7Rle-0002vk-Py; Mon, 18 Feb 2013 14:32:30 +0000 Received: from firewall.ctxuk.citrix.com ([46.33.159.2] helo=[10.80.2.42]) by hopkins.hellion.org.uk with esmtpsa (SSL3.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.72) (envelope-from ) id 1U7Rlc-0005MQ-31; Mon, 18 Feb 2013 14:32:30 +0000 Message-ID: <1361197937.32047.13.camel@zakaz.uk.xensource.com> From: Ian Campbell To: Gavin Date: Mon, 18 Feb 2013 14:32:17 +0000 In-Reply-To: References: <1361184601.31407.144.camel@zakaz.uk.xensource.com> X-Mailer: Evolution 3.4.4-1 Mime-Version: 1.0 X-SA-Exim-Connect-IP: 46.33.159.2 X-SA-Exim-Mail-From: ijc@hellion.org.uk X-SA-Exim-Version: 4.2.1 (built Mon, 22 Mar 2010 06:51:10 +0000) X-SA-Exim-Scanned: Yes (on hopkins.hellion.org.uk) X-Mailman-Approved-At: Mon, 18 Feb 2013 18:01:42 +0000 Cc: "pkg-xen-devel@lists.alioth.debian.org" , "debian-user@lists.debian.org" , xen-users Subject: Re: [Xen-users] [Pkg-xen-devel] Recent hypervisor update on Debian Wheezy breaks domU 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 Mon, 2013-02-18 at 13:51 +0000, Gavin wrote: > I managed to get iDRAC console access and on further inspection it > appears that grub first boots xen-4.1-amd64.gz and then the Linux > kernel. Correct. > When I updated the Xen Hypervisor does it not also upgrade the > xen-4.1-amd64.gz file ?? Yes. Unless the version number changes in which case you get a new file in addition to the older version, but that doesn't apply here. > Are there any better ways to trace where this arp reply is being lost > apart from just tcpdump ? tcpdump is what I would use. > If the kenrel hasn't changed and you are 100% sure the network configuration before and after the reboot is the same then so am I. All I can suggest is to reinstall the previous version of Xen. Ian. -- Ian Campbell Current Noise: Karma To Burn - Thirty Five America, how can I write a holy litany in your silly mood? -- Allen Ginsberg _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Mon Feb 18 18:02:38 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 18 Feb 2013 18:02: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 1U7V27-0007Xt-DN; Mon, 18 Feb 2013 18:01:43 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U7Rm3-0007XH-Tx for xen-users@lists.xen.org; Mon, 18 Feb 2013 14:32:56 +0000 Received: from [85.158.139.83:16499] by server-8.bemta-5.messagelabs.com id 44/68-19075-69B32215; Mon, 18 Feb 2013 14:32:54 +0000 X-Env-Sender: ijc@hellion.org.uk X-Msg-Ref: server-10.tower-182.messagelabs.com!1361197951!28054160!1 X-Originating-IP: [212.110.190.137] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 29103 invoked from network); 18 Feb 2013 14:32:32 -0000 Received: from benson.vm.bytemark.co.uk (HELO benson.vm.bytemark.co.uk) (212.110.190.137) by server-10.tower-182.messagelabs.com with AES256-SHA encrypted SMTP; 18 Feb 2013 14:32:32 -0000 Received: from cpc22-cmbg14-2-0-cust482.5-4.cable.virginmedia.com ([86.6.25.227] helo=hopkins.hellion.org.uk) by benson.vm.bytemark.co.uk with esmtpsa (TLS1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.72) (envelope-from ) id 1U7Rle-0002vk-Py; Mon, 18 Feb 2013 14:32:30 +0000 Received: from firewall.ctxuk.citrix.com ([46.33.159.2] helo=[10.80.2.42]) by hopkins.hellion.org.uk with esmtpsa (SSL3.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.72) (envelope-from ) id 1U7Rlc-0005MQ-31; Mon, 18 Feb 2013 14:32:30 +0000 Message-ID: <1361197937.32047.13.camel@zakaz.uk.xensource.com> From: Ian Campbell To: Gavin Date: Mon, 18 Feb 2013 14:32:17 +0000 In-Reply-To: References: <1361184601.31407.144.camel@zakaz.uk.xensource.com> X-Mailer: Evolution 3.4.4-1 Mime-Version: 1.0 X-SA-Exim-Connect-IP: 46.33.159.2 X-SA-Exim-Mail-From: ijc@hellion.org.uk X-SA-Exim-Version: 4.2.1 (built Mon, 22 Mar 2010 06:51:10 +0000) X-SA-Exim-Scanned: Yes (on hopkins.hellion.org.uk) X-Mailman-Approved-At: Mon, 18 Feb 2013 18:01:42 +0000 Cc: "pkg-xen-devel@lists.alioth.debian.org" , "debian-user@lists.debian.org" , xen-users Subject: Re: [Xen-users] [Pkg-xen-devel] Recent hypervisor update on Debian Wheezy breaks domU 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 Mon, 2013-02-18 at 13:51 +0000, Gavin wrote: > I managed to get iDRAC console access and on further inspection it > appears that grub first boots xen-4.1-amd64.gz and then the Linux > kernel. Correct. > When I updated the Xen Hypervisor does it not also upgrade the > xen-4.1-amd64.gz file ?? Yes. Unless the version number changes in which case you get a new file in addition to the older version, but that doesn't apply here. > Are there any better ways to trace where this arp reply is being lost > apart from just tcpdump ? tcpdump is what I would use. > If the kenrel hasn't changed and you are 100% sure the network configuration before and after the reboot is the same then so am I. All I can suggest is to reinstall the previous version of Xen. Ian. -- Ian Campbell Current Noise: Karma To Burn - Thirty Five America, how can I write a holy litany in your silly mood? -- Allen Ginsberg _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Mon Feb 18 18:02:38 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 18 Feb 2013 18:02: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 1U7V28-0007Y2-0D; Mon, 18 Feb 2013 18:01:44 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U7S0f-00080E-PW for xen-users@lists.xen.org; Mon, 18 Feb 2013 14:48:02 +0000 Received: from [85.158.138.51:38113] by server-11.bemta-3.messagelabs.com id 1B/E9-10249-02F32215; Mon, 18 Feb 2013 14:48:00 +0000 X-Env-Sender: hex445@gmail.com X-Msg-Ref: server-7.tower-174.messagelabs.com!1361198879!19135782!1 X-Originating-IP: [209.85.128.169] 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.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 11750 invoked from network); 18 Feb 2013 14:48:00 -0000 Received: from mail-ve0-f169.google.com (HELO mail-ve0-f169.google.com) (209.85.128.169) by server-7.tower-174.messagelabs.com with RC4-SHA encrypted SMTP; 18 Feb 2013 14:48:00 -0000 Received: by mail-ve0-f169.google.com with SMTP id 15so4976296vea.0 for ; Mon, 18 Feb 2013 06:47:59 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=18K4gNrzebKqOnD+hSwjIVCmH9wtn6UsA2RWmaYZJ9k=; b=skyq1gAvzq7dXQK2RSiC5VCT6ay7rDpA+0iVr6ZDUPuF3czVCSJa3Ad/XzNFNK3nlt AUw4SnMXMywlKtcCASPHW+vAbzS/2ZpRS1N22gcnXo7gv+uCsUTbnfJ+gdMpOsh1z9TC 3WoahSuOPS6Exj50ILhgKq0BAyMyw4LkdBTutSIc9HEuQfopiyVVHjBvp3E7FpRtGnBV mawdLnvAVVHuBYWh3U0UBmMpB1ikR5z/kNPhRZf8tDz1EpMfP0ZVa4xyhipne3lOxhz9 G7fGf/IERvm7hYR8Lrv+Ri1kYxBt8fM4yjdJs2elJaj9OAW0o0KIgclfPLF38M1BGS11 3i4w== MIME-Version: 1.0 X-Received: by 10.58.106.161 with SMTP id gv1mr16292377veb.35.1361198878892; Mon, 18 Feb 2013 06:47:58 -0800 (PST) Received: by 10.58.206.107 with HTTP; Mon, 18 Feb 2013 06:47:58 -0800 (PST) In-Reply-To: References: Date: Mon, 18 Feb 2013 15:47:58 +0100 Message-ID: From: T To: mliebherr99@googlemail.com X-Mailman-Approved-At: Mon, 18 Feb 2013 18:01:42 +0000 Cc: xen-users@lists.xen.org Subject: Re: [Xen-users] Kernel Error with Debian Squeeze, DRBD, 3.2.0-0.bpo.4-amd64 and Xen4.0 X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: 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: ml ml > Date: 2013/2/18 > Subject: [Xen-users] Kernel Error with Debian Squeeze, DRBD, > 3.2.0-0.bpo.4-amd64 and Xen4.0 > To: xen-users@lists.xen.org > > > Hello List, > > i am running Debian Squeeze and i installed DRBD, 3.2.0-0.bpo.4-amd64 > and Xen4.0 from the Backports. > > Sometimes i get such ugly Kernel message: > [257318.441757] BUG: unable to handle kernel paging request at ffff880025f19000 > Check if your cpu has xsaveopt instruction: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=695658 -- T _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Mon Feb 18 18:02:38 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 18 Feb 2013 18:02: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 1U7V28-0007Y2-0D; Mon, 18 Feb 2013 18:01:44 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U7S0f-00080E-PW for xen-users@lists.xen.org; Mon, 18 Feb 2013 14:48:02 +0000 Received: from [85.158.138.51:38113] by server-11.bemta-3.messagelabs.com id 1B/E9-10249-02F32215; Mon, 18 Feb 2013 14:48:00 +0000 X-Env-Sender: hex445@gmail.com X-Msg-Ref: server-7.tower-174.messagelabs.com!1361198879!19135782!1 X-Originating-IP: [209.85.128.169] 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.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 11750 invoked from network); 18 Feb 2013 14:48:00 -0000 Received: from mail-ve0-f169.google.com (HELO mail-ve0-f169.google.com) (209.85.128.169) by server-7.tower-174.messagelabs.com with RC4-SHA encrypted SMTP; 18 Feb 2013 14:48:00 -0000 Received: by mail-ve0-f169.google.com with SMTP id 15so4976296vea.0 for ; Mon, 18 Feb 2013 06:47:59 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=18K4gNrzebKqOnD+hSwjIVCmH9wtn6UsA2RWmaYZJ9k=; b=skyq1gAvzq7dXQK2RSiC5VCT6ay7rDpA+0iVr6ZDUPuF3czVCSJa3Ad/XzNFNK3nlt AUw4SnMXMywlKtcCASPHW+vAbzS/2ZpRS1N22gcnXo7gv+uCsUTbnfJ+gdMpOsh1z9TC 3WoahSuOPS6Exj50ILhgKq0BAyMyw4LkdBTutSIc9HEuQfopiyVVHjBvp3E7FpRtGnBV mawdLnvAVVHuBYWh3U0UBmMpB1ikR5z/kNPhRZf8tDz1EpMfP0ZVa4xyhipne3lOxhz9 G7fGf/IERvm7hYR8Lrv+Ri1kYxBt8fM4yjdJs2elJaj9OAW0o0KIgclfPLF38M1BGS11 3i4w== MIME-Version: 1.0 X-Received: by 10.58.106.161 with SMTP id gv1mr16292377veb.35.1361198878892; Mon, 18 Feb 2013 06:47:58 -0800 (PST) Received: by 10.58.206.107 with HTTP; Mon, 18 Feb 2013 06:47:58 -0800 (PST) In-Reply-To: References: Date: Mon, 18 Feb 2013 15:47:58 +0100 Message-ID: From: T To: mliebherr99@googlemail.com X-Mailman-Approved-At: Mon, 18 Feb 2013 18:01:42 +0000 Cc: xen-users@lists.xen.org Subject: Re: [Xen-users] Kernel Error with Debian Squeeze, DRBD, 3.2.0-0.bpo.4-amd64 and Xen4.0 X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: 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: ml ml > Date: 2013/2/18 > Subject: [Xen-users] Kernel Error with Debian Squeeze, DRBD, > 3.2.0-0.bpo.4-amd64 and Xen4.0 > To: xen-users@lists.xen.org > > > Hello List, > > i am running Debian Squeeze and i installed DRBD, 3.2.0-0.bpo.4-amd64 > and Xen4.0 from the Backports. > > Sometimes i get such ugly Kernel message: > [257318.441757] BUG: unable to handle kernel paging request at ffff880025f19000 > Check if your cpu has xsaveopt instruction: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=695658 -- T _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Mon Feb 18 18:02:38 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 18 Feb 2013 18:02: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 1U7V29-0007YM-8F; Mon, 18 Feb 2013 18:01:45 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U7Upt-0007Qc-Q3 for xen-users@lists.xen.org; Mon, 18 Feb 2013 17:49:06 +0000 Received: from [193.109.254.147:6508] by server-12.bemta-14.messagelabs.com id 9F/70-32582-19962215; Mon, 18 Feb 2013 17:49:05 +0000 X-Env-Sender: Dale.Galekovic@pace.com X-Msg-Ref: server-7.tower-27.messagelabs.com!1361209741!1111075!1 X-Originating-IP: [65.55.88.11] X-SpamReason: No, hits=0.0 required=7.0 tests=HTML_MESSAGE X-StarScan-Received: X-StarScan-Version: 6.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 27802 invoked from network); 18 Feb 2013 17:49:02 -0000 Received: from tx2ehsobe001.messaging.microsoft.com (HELO tx2outboundpool.messaging.microsoft.com) (65.55.88.11) by server-7.tower-27.messagelabs.com with AES128-SHA encrypted SMTP; 18 Feb 2013 17:49:02 -0000 Received: from mail72-tx2-R.bigfish.com (10.9.14.239) by TX2EHSOBE006.bigfish.com (10.9.40.26) with Microsoft SMTP Server id 14.1.225.23; Mon, 18 Feb 2013 17:49:01 +0000 Received: from mail72-tx2 (localhost [127.0.0.1]) by mail72-tx2-R.bigfish.com (Postfix) with ESMTP id 0C6F52E0111 for ; Mon, 18 Feb 2013 17:49:01 +0000 (UTC) X-Forefront-Antispam-Report: CIP:157.56.232.213; KIP:(null); UIP:(null); IPV:NLI; H:BLUPRD0511HT002.namprd05.prod.outlook.com; RD:none; EFVD:NLI X-SpamScore: -11 X-BigFish: PS-11(zzc85fh1443I11eeRzz1f42h1ee6h1de0h1202h1e76h1d1ah1d2ahzz17326ah8275bh8275dh18c673hz2dh2a8h668h839hd25hf0ah1288h12a5h12bdh137ah1441h1504h1537h153bh15d0h162dh1631h1758h18e1h1946h19b5h19ceh1155h) Received: from mail72-tx2 (localhost.localdomain [127.0.0.1]) by mail72-tx2 (MessageSwitch) id 1361209738801240_18693; Mon, 18 Feb 2013 17:48:58 +0000 (UTC) Received: from TX2EHSMHS031.bigfish.com (unknown [10.9.14.254]) by mail72-tx2.bigfish.com (Postfix) with ESMTP id B3D191E0090 for ; Mon, 18 Feb 2013 17:48:58 +0000 (UTC) Received: from BLUPRD0511HT002.namprd05.prod.outlook.com (157.56.232.213) by TX2EHSMHS031.bigfish.com (10.9.99.131) with Microsoft SMTP Server (TLS) id 14.1.225.23; Mon, 18 Feb 2013 17:48:58 +0000 Received: from BLUPRD0511MB426.namprd05.prod.outlook.com ([169.254.12.246]) by BLUPRD0511HT002.namprd05.prod.outlook.com ([10.255.135.165]) with mapi id 14.16.0263.000; Mon, 18 Feb 2013 17:48:57 +0000 From: Dale Galekovic To: "xen-users@lists.xen.org" Thread-Topic: Problem building Tools Xen 4.2 Thread-Index: Ac4LvFSnAP6IHeNcTPuUmK8jVqw1Aw== Date: Mon, 18 Feb 2013 17:48:56 +0000 Message-ID: <374DD7FF31C7AB4EA7E0B48BD2049C821F9BBB71@BLUPRD0511MB426.namprd05.prod.outlook.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [209.156.171.253] MIME-Version: 1.0 X-OriginatorOrg: pace.com X-Mailman-Approved-At: Mon, 18 Feb 2013 18:01:42 +0000 Subject: [Xen-users] Problem building Tools Xen 4.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: multipart/mixed; boundary="===============3622896576429344001==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============3622896576429344001== Content-Language: en-US Content-Type: multipart/alternative; boundary="_000_374DD7FF31C7AB4EA7E0B48BD2049C821F9BBB71BLUPRD0511MB426_" --_000_374DD7FF31C7AB4EA7E0B48BD2049C821F9BBB71BLUPRD0511MB426_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Trying to build xen 4.2 .... Everything was going OK until I tried to make = tools I'm getting the following error. [root@Dales-xen-server xen-4.2.0-rc2]# make tools make -C tools qemu-xen-dir-find make[1]: Entering directory `/home/rig/xen/xen-4.2.0-rc2/tools' if test -d git://xenbits.xen.org/qemu-upstream-unstable.git ; then \ mkdir -p qemu-xen-dir; \ else \ export GIT=3Dgit; \ /home/rig/xen/xen-4.2.0-rc2/tools/../scripts/git-checkout.s= h git://xenbits.xen.org/qemu-upstream-unstable.git master qemu-xen-dir ; \ fi Initialized empty Git repository in /home/rig/xen/xen-4.2.0-rc2/tools/qemu-= xen-dir-remote.tmp/.git/ xenbits.xen.org[0: 50.57.170.242]: errno=3DConnection timed out fatal: unable to connect a socket (Connection timed out) make[1]: *** [qemu-xen-dir-find] Error 128 make[1]: Leaving directory `/home/rig/xen/xen-4.2.0-rc2/tools' make: *** [tools/qemu-xen-dir] Error 2 Not sure if it's firewall related. Does anyone know what port git uses? Host OS is Centos 6.3 64 bit Linux Dales-xen-server.pace.internal 2.6.32-279.22.1.el6.x86_64 #1 SMP Wed = Feb 6 03:10:46 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux Thanks in advance Dale G. --_000_374DD7FF31C7AB4EA7E0B48BD2049C821F9BBB71BLUPRD0511MB426_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Trying to build xen 4.2 …. Every= thing was going OK until I tried to make tools

I’m getting the following error.=

 

[root@Dales-xen-server xen-4.2.0-rc2]#= make tools

make -C tools qemu-xen-dir-find

make[1]: Entering directory `/home/rig= /xen/xen-4.2.0-rc2/tools'

if test -d git://xenbits.xen.org/qemu-= upstream-unstable.git ; then \

      &n= bsp;         mkdir -p qemu-xen-dir;= \

      &n= bsp; else \

      &n= bsp;         export GIT=3Dgit; \

      &n= bsp;         /home/rig/xen/xen-4.2.= 0-rc2/tools/../scripts/git-checkout.sh git://xenbits.xen.org/qemu-upstream-= unstable.git master qemu-xen-dir ; \

      &n= bsp; fi

Initialized empty Git repository in /h= ome/rig/xen/xen-4.2.0-rc2/tools/qemu-xen-dir-remote.tmp/.git/

xenbits.xen.org[0: 50.57.170.242]: err= no=3DConnection timed out

fatal: unable to connect a socket (Con= nection timed out)

make[1]: *** [qemu-xen-dir-find] Error= 128

make[1]: Leaving directory `/home/rig/= xen/xen-4.2.0-rc2/tools'

make: *** [tools/qemu-xen-dir] Error 2=

 

Not sure if it’s firewall relate= d. Does anyone know what port git uses?

 

Host OS is Centos 6.3 64 bit

Linux Dales-xen-server.pace.internal 2= .6.32-279.22.1.el6.x86_64 #1 SMP Wed Feb 6 03:10:46 UTC 2013 x86_64 x86_64 = x86_64 GNU/Linux

 

Thanks in advance

 

Dale G.

--_000_374DD7FF31C7AB4EA7E0B48BD2049C821F9BBB71BLUPRD0511MB426_-- --===============3622896576429344001== 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 --===============3622896576429344001==-- From xen-users-bounces@lists.xen.org Mon Feb 18 18:02:38 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 18 Feb 2013 18:02: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 1U7V29-0007YM-8F; Mon, 18 Feb 2013 18:01:45 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U7Upt-0007Qc-Q3 for xen-users@lists.xen.org; Mon, 18 Feb 2013 17:49:06 +0000 Received: from [193.109.254.147:6508] by server-12.bemta-14.messagelabs.com id 9F/70-32582-19962215; Mon, 18 Feb 2013 17:49:05 +0000 X-Env-Sender: Dale.Galekovic@pace.com X-Msg-Ref: server-7.tower-27.messagelabs.com!1361209741!1111075!1 X-Originating-IP: [65.55.88.11] X-SpamReason: No, hits=0.0 required=7.0 tests=HTML_MESSAGE X-StarScan-Received: X-StarScan-Version: 6.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 27802 invoked from network); 18 Feb 2013 17:49:02 -0000 Received: from tx2ehsobe001.messaging.microsoft.com (HELO tx2outboundpool.messaging.microsoft.com) (65.55.88.11) by server-7.tower-27.messagelabs.com with AES128-SHA encrypted SMTP; 18 Feb 2013 17:49:02 -0000 Received: from mail72-tx2-R.bigfish.com (10.9.14.239) by TX2EHSOBE006.bigfish.com (10.9.40.26) with Microsoft SMTP Server id 14.1.225.23; Mon, 18 Feb 2013 17:49:01 +0000 Received: from mail72-tx2 (localhost [127.0.0.1]) by mail72-tx2-R.bigfish.com (Postfix) with ESMTP id 0C6F52E0111 for ; Mon, 18 Feb 2013 17:49:01 +0000 (UTC) X-Forefront-Antispam-Report: CIP:157.56.232.213; KIP:(null); UIP:(null); IPV:NLI; H:BLUPRD0511HT002.namprd05.prod.outlook.com; RD:none; EFVD:NLI X-SpamScore: -11 X-BigFish: PS-11(zzc85fh1443I11eeRzz1f42h1ee6h1de0h1202h1e76h1d1ah1d2ahzz17326ah8275bh8275dh18c673hz2dh2a8h668h839hd25hf0ah1288h12a5h12bdh137ah1441h1504h1537h153bh15d0h162dh1631h1758h18e1h1946h19b5h19ceh1155h) Received: from mail72-tx2 (localhost.localdomain [127.0.0.1]) by mail72-tx2 (MessageSwitch) id 1361209738801240_18693; Mon, 18 Feb 2013 17:48:58 +0000 (UTC) Received: from TX2EHSMHS031.bigfish.com (unknown [10.9.14.254]) by mail72-tx2.bigfish.com (Postfix) with ESMTP id B3D191E0090 for ; Mon, 18 Feb 2013 17:48:58 +0000 (UTC) Received: from BLUPRD0511HT002.namprd05.prod.outlook.com (157.56.232.213) by TX2EHSMHS031.bigfish.com (10.9.99.131) with Microsoft SMTP Server (TLS) id 14.1.225.23; Mon, 18 Feb 2013 17:48:58 +0000 Received: from BLUPRD0511MB426.namprd05.prod.outlook.com ([169.254.12.246]) by BLUPRD0511HT002.namprd05.prod.outlook.com ([10.255.135.165]) with mapi id 14.16.0263.000; Mon, 18 Feb 2013 17:48:57 +0000 From: Dale Galekovic To: "xen-users@lists.xen.org" Thread-Topic: Problem building Tools Xen 4.2 Thread-Index: Ac4LvFSnAP6IHeNcTPuUmK8jVqw1Aw== Date: Mon, 18 Feb 2013 17:48:56 +0000 Message-ID: <374DD7FF31C7AB4EA7E0B48BD2049C821F9BBB71@BLUPRD0511MB426.namprd05.prod.outlook.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [209.156.171.253] MIME-Version: 1.0 X-OriginatorOrg: pace.com X-Mailman-Approved-At: Mon, 18 Feb 2013 18:01:42 +0000 Subject: [Xen-users] Problem building Tools Xen 4.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: multipart/mixed; boundary="===============3622896576429344001==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============3622896576429344001== Content-Language: en-US Content-Type: multipart/alternative; boundary="_000_374DD7FF31C7AB4EA7E0B48BD2049C821F9BBB71BLUPRD0511MB426_" --_000_374DD7FF31C7AB4EA7E0B48BD2049C821F9BBB71BLUPRD0511MB426_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Trying to build xen 4.2 .... Everything was going OK until I tried to make = tools I'm getting the following error. [root@Dales-xen-server xen-4.2.0-rc2]# make tools make -C tools qemu-xen-dir-find make[1]: Entering directory `/home/rig/xen/xen-4.2.0-rc2/tools' if test -d git://xenbits.xen.org/qemu-upstream-unstable.git ; then \ mkdir -p qemu-xen-dir; \ else \ export GIT=3Dgit; \ /home/rig/xen/xen-4.2.0-rc2/tools/../scripts/git-checkout.s= h git://xenbits.xen.org/qemu-upstream-unstable.git master qemu-xen-dir ; \ fi Initialized empty Git repository in /home/rig/xen/xen-4.2.0-rc2/tools/qemu-= xen-dir-remote.tmp/.git/ xenbits.xen.org[0: 50.57.170.242]: errno=3DConnection timed out fatal: unable to connect a socket (Connection timed out) make[1]: *** [qemu-xen-dir-find] Error 128 make[1]: Leaving directory `/home/rig/xen/xen-4.2.0-rc2/tools' make: *** [tools/qemu-xen-dir] Error 2 Not sure if it's firewall related. Does anyone know what port git uses? Host OS is Centos 6.3 64 bit Linux Dales-xen-server.pace.internal 2.6.32-279.22.1.el6.x86_64 #1 SMP Wed = Feb 6 03:10:46 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux Thanks in advance Dale G. --_000_374DD7FF31C7AB4EA7E0B48BD2049C821F9BBB71BLUPRD0511MB426_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Trying to build xen 4.2 …. Every= thing was going OK until I tried to make tools

I’m getting the following error.=

 

[root@Dales-xen-server xen-4.2.0-rc2]#= make tools

make -C tools qemu-xen-dir-find

make[1]: Entering directory `/home/rig= /xen/xen-4.2.0-rc2/tools'

if test -d git://xenbits.xen.org/qemu-= upstream-unstable.git ; then \

      &n= bsp;         mkdir -p qemu-xen-dir;= \

      &n= bsp; else \

      &n= bsp;         export GIT=3Dgit; \

      &n= bsp;         /home/rig/xen/xen-4.2.= 0-rc2/tools/../scripts/git-checkout.sh git://xenbits.xen.org/qemu-upstream-= unstable.git master qemu-xen-dir ; \

      &n= bsp; fi

Initialized empty Git repository in /h= ome/rig/xen/xen-4.2.0-rc2/tools/qemu-xen-dir-remote.tmp/.git/

xenbits.xen.org[0: 50.57.170.242]: err= no=3DConnection timed out

fatal: unable to connect a socket (Con= nection timed out)

make[1]: *** [qemu-xen-dir-find] Error= 128

make[1]: Leaving directory `/home/rig/= xen/xen-4.2.0-rc2/tools'

make: *** [tools/qemu-xen-dir] Error 2=

 

Not sure if it’s firewall relate= d. Does anyone know what port git uses?

 

Host OS is Centos 6.3 64 bit

Linux Dales-xen-server.pace.internal 2= .6.32-279.22.1.el6.x86_64 #1 SMP Wed Feb 6 03:10:46 UTC 2013 x86_64 x86_64 = x86_64 GNU/Linux

 

Thanks in advance

 

Dale G.

--_000_374DD7FF31C7AB4EA7E0B48BD2049C821F9BBB71BLUPRD0511MB426_-- --===============3622896576429344001== 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 --===============3622896576429344001==-- From xen-users-bounces@lists.xen.org Mon Feb 18 18:02:38 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 18 Feb 2013 18:02: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 1U7V28-0007YB-JL; Mon, 18 Feb 2013 18:01:44 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U7UM7-0006qr-Ey; Mon, 18 Feb 2013 17:18:19 +0000 Received: from [85.158.137.99:55751] by server-12.bemta-3.messagelabs.com id 8C/23-05889-95262215; Mon, 18 Feb 2013 17:18:17 +0000 X-Env-Sender: Matthew.Fioravante@jhuapl.edu X-Msg-Ref: server-6.tower-217.messagelabs.com!1361207889!14156115!1 X-Originating-IP: [128.244.251.37] X-SpamReason: No, hits=0.1 required=7.0 tests=HTML_50_60,HTML_MESSAGE X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 32391 invoked from network); 18 Feb 2013 17:18:12 -0000 Received: from piper.jhuapl.edu (HELO piper.jhuapl.edu) (128.244.251.37) by server-6.tower-217.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 18 Feb 2013 17:18:12 -0000 Received: from aplexcas1.dom1.jhuapl.edu (aplexcas1.dom1.jhuapl.edu [128.244.198.90]) by piper.jhuapl.edu with smtp (TLS: TLSv1/SSLv3,128bits,RC4-MD5) id 16ba_51e1_0e6ba42b_3a6f_4ec1_a363_6c2601379061; Mon, 18 Feb 2013 12:18:00 -0500 Received: from aplesstripe.dom1.jhuapl.edu ([128.244.198.211]) by aplexcas1.dom1.jhuapl.edu ([128.244.198.90]) with mapi; Mon, 18 Feb 2013 12:17:48 -0500 From: "Fioravante, Matthew E." To: tech mailinglists , "port-xen@netbsd.org" , xen-users , "xen-devel@lists.xen.org" Date: Mon, 18 Feb 2013 12:17:47 -0500 Thread-Topic: [Xen-devel] Building Xen 4.2.1 with vTPM on NetBSD 6.0.1 Thread-Index: Ac4Gwmz5o5Rp8EDWRF23zBGAQ1QyYwHOUlgg Message-ID: <068F06DC4D106941B297C0C5F9F446EA49199E95FD@aplesstripe.dom1.jhuapl.edu> References: In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US MIME-Version: 1.0 X-Mailman-Approved-At: Mon, 18 Feb 2013 18:01:42 +0000 Subject: Re: [Xen-users] [Xen-devel] Building Xen 4.2.1 with vTPM on NetBSD 6.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-Type: multipart/mixed; boundary="===============3276932328111566082==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============3276932328111566082== Content-Language: en-US Content-Type: multipart/alternative; boundary="_000_068F06DC4D106941B297C0C5F9F446EA49199E95FDaplesstripedo_" --_000_068F06DC4D106941B297C0C5F9F446EA49199E95FDaplesstripedo_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable I've never tried to use vtpm on netbsd so I cannot say whether it will work= or not. This is the old vtpm system which is now deprecated. Even if you can build = it I wouldn't recommend using it. From: xen-devel-bounces@lists.xen.org [mailto:xen-devel-bounces@lists.xen.o= rg] On Behalf Of tech mailinglists Sent: Saturday, February 09, 2013 7:39 AM To: port-xen@netbsd.org; xen-users; xen-devel@lists.xen.org Subject: [Xen-devel] Building Xen 4.2.1 with vTPM on NetBSD 6.0.1 Hello all, I try to build Xen 4.2.1 on NetBSD 6.0.1 with vTPM. I would say that depend= encies are missing but I don't know it. I have done the following: I installed the building dependencies from pkgsrc Run configure as follows: ./configure PYTHON=3D/usr/pkg/bin/python2.7 APPEND_INCLUDES=3D/usr/pkg/incl= ude APPEND_LIB=3D/usr/pkg/lib --prefix=3D/usr/xen42 --enable-vtpm Builded Xen itself successfully. Run gmake for the tools target as follows: gmake LD_LIBRARY_PATH=3D/usr/pkg/lib tools This fails with the following error: gmake[5]: Entering directory `/root/xen-4.2.1/tools/vtpm_manager/manager' gcc -Werror -g3 -D_GNU_SOURCE -DLOGGING_MODULES=3D"(BITMASK(VTPM_LOG_TCS)|= BITMASK(VTPM_LOG_VTSP)|BITMASK(VTPM_LOG_VTPM))" -I/root/xen-4.2.1/tools/vtp= m_manager/manager/../../../tools/vtpm_manager/crypto -I/root/xen-4.2.1/tool= s/vtpm_manager/manager/../../../tools/vtpm_manager/util -I/root/xen-4.2.1/t= ools/vtpm_manager/manager/../../../tools/vtpm_manager/tcs -I/root/xen-4.2.1= /tools/vtpm_manager/manager/../../../tools/vtpm_manager/manager -pthread -= c -o vtpmd.o vtpmd.c -I/usr/pkg/include cc1: warnings being treated as errors vtpmd.c: In function 'signal_handler': vtpmd.c:96:3: error: passing argument 2 of '__libc_thr_equal' makes pointer= from integer without a cast /usr/include/pthread.h:368:5: note: expected 'pthread_t' but argument is of= type '__pid_t' vtpmd.c: In function 'main': vtpmd.c:343:28: error: assignment makes integer from pointer without a cast gmake[5]: *** [vtpmd.o] Error 1 gmake[5]: Leaving directory `/root/xen-4.2.1/tools/vtpm_manager/manager' gmake[4]: *** [subdir-install-manager] Error 2 gmake[4]: Leaving directory `/root/xen-4.2.1/tools/vtpm_manager' gmake[3]: *** [subdirs-install] Error 2 gmake[3]: Leaving directory `/root/xen-4.2.1/tools/vtpm_manager' gmake[2]: *** [subdir-install-vtpm_manager] Error 2 gmake[2]: Leaving directory `/root/xen-4.2.1/tools' gmake[1]: *** [subdirs-install] Error 2 gmake[1]: Leaving directory `/root/xen-4.2.1/tools' gmake: *** [install-tools] Error 2 So I know that already one dependency is missing I think it's libgmp but I = found no way to build it on NetBSD. Is vTPM buildable on NetBSD and what does this error/warning which was trea= ted as error mean? Best Regards --_000_068F06DC4D106941B297C0C5F9F446EA49199E95FDaplesstripedo_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

I’v= e never tried to use vtpm on netbsd so I cannot say whether it will work or= not.

 

This is the old vtpm system which is no= w deprecated. Even if you can build it I wouldn’t recommend using it.=

 <= /p>

From: xen-devel-bounces@lists.xe= n.org [mailto:xen-devel-bounces@lists.xen.org] On Behalf Of tech mai= linglists
Sent: Saturday, February 09, 2013 7:39 AM
To:= port-xen@netbsd.org; xen-users; xen-devel@lists.xen.org
Subject:= [Xen-devel] Building Xen 4.2.1 with vTPM on NetBSD 6.0.1=

 

 

Hello all,

I try to build Xen 4.2.1 on NetBSD= 6.0.1 with vTPM. I would say that dependencies are missing but I don't kno= w it.

I have done the following:

I installed the building dependencies = from pkgsrc

Run configure as = follows: 

./configure PYTHON=3D/usr/pkg/bin/python2.7 AP=
PEND_INCLUDES=3D/usr/pkg/include APPEND_LIB=3D/usr/pkg/lib --prefix=3D/usr/=
xen42 --enable-vtpm

 
Builded Xen itself successfully.
Run gmake for the tools target a=
s follows: 

gmake LD_LIBRARY_PATH=3D/usr/pkg/lib tools
This fails with the following error:=

gmake[5]: Entering directory `/root/xen-4.2.1/tools/v=
tpm_manager/manager'
gcc  -Werror -g3 -D_GNU_SOURCE -DLOGGING_MODUL=
ES=3D"(BITMASK(VTPM_LOG_TCS)|BITMASK(VTPM_LOG_VTSP)|BITMASK(VTPM_LOG_V=
TPM))" -I/root/xen-4.2.1/tools/vtpm_manager/manager/../../../tools/vtp=
m_manager/crypto -I/root/xen-4.2.1/tools/vtpm_manager/manager/../../../tool=
s/vtpm_manager/util -I/root/xen-4.2.1/tools/vtpm_manager/manager/../../../t=
ools/vtpm_manager/tcs -I/root/xen-4.2.1/tools/vtpm_manager/manager/../../..=
/tools/vtpm_manager/manager -pthread  -c -o vtpmd.o vtpmd.c  -I/u=
sr/pkg/include

cc1: warnings being treated as =
errors
vtpmd.c: In function 'signal_handler':
vtpmd.c:96:3: error: pa=
ssing argument 2 of '__libc_thr_equal' makes pointer from integer without a=
 cast
/usr/include/pthread.h:368:5: note: expected 'pthread_t' but argum=
ent is of type '__pid_t'

vtpmd.c: In function =
'main':
vtpmd.c:343:28: error: assignment makes integer from pointer wit=
hout a cast
gmake[5]: *** [vtpmd.o] Error 1
gmake[5]: Leaving directo=
ry `/root/xen-4.2.1/tools/vtpm_manager/manager'

gmake[4]: *** [subdir-install-manager] Error 2
gmake[4]: Leaving direc=
tory `/root/xen-4.2.1/tools/vtpm_manager'
gmake[3]: *** [subdirs-install=
] Error 2
gmake[3]: Leaving directory `/root/xen-4.2.1/tools/vtpm_manage=
r'

gmake[2]: *** [subdir-install-vtpm_manager]=
 Error 2
gmake[2]: Leaving directory `/root/xen-4.2.1/tools'
gmake[1]=
: *** [subdirs-install] Error 2
gmake[1]: Leaving directory `/root/xen-4=
.2.1/tools'
gmake: *** [install-tools] Error 2

<= pre> 
So I know th=
at already one dependency is missing I think it's libgmp but I found no way=
 to build it on NetBSD.
Is vTPM buildable on NetBSD an=
d what does this error/warning which was treated as error mean?

 
Best Regards
=
= --_000_068F06DC4D106941B297C0C5F9F446EA49199E95FDaplesstripedo_-- --===============3276932328111566082== 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 --===============3276932328111566082==-- From xen-users-bounces@lists.xen.org Mon Feb 18 18:02:38 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 18 Feb 2013 18:02: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 1U7V28-0007YB-JL; Mon, 18 Feb 2013 18:01:44 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U7UM7-0006qr-Ey; Mon, 18 Feb 2013 17:18:19 +0000 Received: from [85.158.137.99:55751] by server-12.bemta-3.messagelabs.com id 8C/23-05889-95262215; Mon, 18 Feb 2013 17:18:17 +0000 X-Env-Sender: Matthew.Fioravante@jhuapl.edu X-Msg-Ref: server-6.tower-217.messagelabs.com!1361207889!14156115!1 X-Originating-IP: [128.244.251.37] X-SpamReason: No, hits=0.1 required=7.0 tests=HTML_50_60,HTML_MESSAGE X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 32391 invoked from network); 18 Feb 2013 17:18:12 -0000 Received: from piper.jhuapl.edu (HELO piper.jhuapl.edu) (128.244.251.37) by server-6.tower-217.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 18 Feb 2013 17:18:12 -0000 Received: from aplexcas1.dom1.jhuapl.edu (aplexcas1.dom1.jhuapl.edu [128.244.198.90]) by piper.jhuapl.edu with smtp (TLS: TLSv1/SSLv3,128bits,RC4-MD5) id 16ba_51e1_0e6ba42b_3a6f_4ec1_a363_6c2601379061; Mon, 18 Feb 2013 12:18:00 -0500 Received: from aplesstripe.dom1.jhuapl.edu ([128.244.198.211]) by aplexcas1.dom1.jhuapl.edu ([128.244.198.90]) with mapi; Mon, 18 Feb 2013 12:17:48 -0500 From: "Fioravante, Matthew E." To: tech mailinglists , "port-xen@netbsd.org" , xen-users , "xen-devel@lists.xen.org" Date: Mon, 18 Feb 2013 12:17:47 -0500 Thread-Topic: [Xen-devel] Building Xen 4.2.1 with vTPM on NetBSD 6.0.1 Thread-Index: Ac4Gwmz5o5Rp8EDWRF23zBGAQ1QyYwHOUlgg Message-ID: <068F06DC4D106941B297C0C5F9F446EA49199E95FD@aplesstripe.dom1.jhuapl.edu> References: In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US MIME-Version: 1.0 X-Mailman-Approved-At: Mon, 18 Feb 2013 18:01:42 +0000 Subject: Re: [Xen-users] [Xen-devel] Building Xen 4.2.1 with vTPM on NetBSD 6.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-Type: multipart/mixed; boundary="===============3276932328111566082==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============3276932328111566082== Content-Language: en-US Content-Type: multipart/alternative; boundary="_000_068F06DC4D106941B297C0C5F9F446EA49199E95FDaplesstripedo_" --_000_068F06DC4D106941B297C0C5F9F446EA49199E95FDaplesstripedo_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable I've never tried to use vtpm on netbsd so I cannot say whether it will work= or not. This is the old vtpm system which is now deprecated. Even if you can build = it I wouldn't recommend using it. From: xen-devel-bounces@lists.xen.org [mailto:xen-devel-bounces@lists.xen.o= rg] On Behalf Of tech mailinglists Sent: Saturday, February 09, 2013 7:39 AM To: port-xen@netbsd.org; xen-users; xen-devel@lists.xen.org Subject: [Xen-devel] Building Xen 4.2.1 with vTPM on NetBSD 6.0.1 Hello all, I try to build Xen 4.2.1 on NetBSD 6.0.1 with vTPM. I would say that depend= encies are missing but I don't know it. I have done the following: I installed the building dependencies from pkgsrc Run configure as follows: ./configure PYTHON=3D/usr/pkg/bin/python2.7 APPEND_INCLUDES=3D/usr/pkg/incl= ude APPEND_LIB=3D/usr/pkg/lib --prefix=3D/usr/xen42 --enable-vtpm Builded Xen itself successfully. Run gmake for the tools target as follows: gmake LD_LIBRARY_PATH=3D/usr/pkg/lib tools This fails with the following error: gmake[5]: Entering directory `/root/xen-4.2.1/tools/vtpm_manager/manager' gcc -Werror -g3 -D_GNU_SOURCE -DLOGGING_MODULES=3D"(BITMASK(VTPM_LOG_TCS)|= BITMASK(VTPM_LOG_VTSP)|BITMASK(VTPM_LOG_VTPM))" -I/root/xen-4.2.1/tools/vtp= m_manager/manager/../../../tools/vtpm_manager/crypto -I/root/xen-4.2.1/tool= s/vtpm_manager/manager/../../../tools/vtpm_manager/util -I/root/xen-4.2.1/t= ools/vtpm_manager/manager/../../../tools/vtpm_manager/tcs -I/root/xen-4.2.1= /tools/vtpm_manager/manager/../../../tools/vtpm_manager/manager -pthread -= c -o vtpmd.o vtpmd.c -I/usr/pkg/include cc1: warnings being treated as errors vtpmd.c: In function 'signal_handler': vtpmd.c:96:3: error: passing argument 2 of '__libc_thr_equal' makes pointer= from integer without a cast /usr/include/pthread.h:368:5: note: expected 'pthread_t' but argument is of= type '__pid_t' vtpmd.c: In function 'main': vtpmd.c:343:28: error: assignment makes integer from pointer without a cast gmake[5]: *** [vtpmd.o] Error 1 gmake[5]: Leaving directory `/root/xen-4.2.1/tools/vtpm_manager/manager' gmake[4]: *** [subdir-install-manager] Error 2 gmake[4]: Leaving directory `/root/xen-4.2.1/tools/vtpm_manager' gmake[3]: *** [subdirs-install] Error 2 gmake[3]: Leaving directory `/root/xen-4.2.1/tools/vtpm_manager' gmake[2]: *** [subdir-install-vtpm_manager] Error 2 gmake[2]: Leaving directory `/root/xen-4.2.1/tools' gmake[1]: *** [subdirs-install] Error 2 gmake[1]: Leaving directory `/root/xen-4.2.1/tools' gmake: *** [install-tools] Error 2 So I know that already one dependency is missing I think it's libgmp but I = found no way to build it on NetBSD. Is vTPM buildable on NetBSD and what does this error/warning which was trea= ted as error mean? Best Regards --_000_068F06DC4D106941B297C0C5F9F446EA49199E95FDaplesstripedo_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

I’v= e never tried to use vtpm on netbsd so I cannot say whether it will work or= not.

 

This is the old vtpm system which is no= w deprecated. Even if you can build it I wouldn’t recommend using it.=

 <= /p>

From: xen-devel-bounces@lists.xe= n.org [mailto:xen-devel-bounces@lists.xen.org] On Behalf Of tech mai= linglists
Sent: Saturday, February 09, 2013 7:39 AM
To:= port-xen@netbsd.org; xen-users; xen-devel@lists.xen.org
Subject:= [Xen-devel] Building Xen 4.2.1 with vTPM on NetBSD 6.0.1=

 

 

Hello all,

I try to build Xen 4.2.1 on NetBSD= 6.0.1 with vTPM. I would say that dependencies are missing but I don't kno= w it.

I have done the following:

I installed the building dependencies = from pkgsrc

Run configure as = follows: 

./configure PYTHON=3D/usr/pkg/bin/python2.7 AP=
PEND_INCLUDES=3D/usr/pkg/include APPEND_LIB=3D/usr/pkg/lib --prefix=3D/usr/=
xen42 --enable-vtpm

 
Builded Xen itself successfully.
Run gmake for the tools target a=
s follows: 

gmake LD_LIBRARY_PATH=3D/usr/pkg/lib tools
This fails with the following error:=

gmake[5]: Entering directory `/root/xen-4.2.1/tools/v=
tpm_manager/manager'
gcc  -Werror -g3 -D_GNU_SOURCE -DLOGGING_MODUL=
ES=3D"(BITMASK(VTPM_LOG_TCS)|BITMASK(VTPM_LOG_VTSP)|BITMASK(VTPM_LOG_V=
TPM))" -I/root/xen-4.2.1/tools/vtpm_manager/manager/../../../tools/vtp=
m_manager/crypto -I/root/xen-4.2.1/tools/vtpm_manager/manager/../../../tool=
s/vtpm_manager/util -I/root/xen-4.2.1/tools/vtpm_manager/manager/../../../t=
ools/vtpm_manager/tcs -I/root/xen-4.2.1/tools/vtpm_manager/manager/../../..=
/tools/vtpm_manager/manager -pthread  -c -o vtpmd.o vtpmd.c  -I/u=
sr/pkg/include

cc1: warnings being treated as =
errors
vtpmd.c: In function 'signal_handler':
vtpmd.c:96:3: error: pa=
ssing argument 2 of '__libc_thr_equal' makes pointer from integer without a=
 cast
/usr/include/pthread.h:368:5: note: expected 'pthread_t' but argum=
ent is of type '__pid_t'

vtpmd.c: In function =
'main':
vtpmd.c:343:28: error: assignment makes integer from pointer wit=
hout a cast
gmake[5]: *** [vtpmd.o] Error 1
gmake[5]: Leaving directo=
ry `/root/xen-4.2.1/tools/vtpm_manager/manager'

gmake[4]: *** [subdir-install-manager] Error 2
gmake[4]: Leaving direc=
tory `/root/xen-4.2.1/tools/vtpm_manager'
gmake[3]: *** [subdirs-install=
] Error 2
gmake[3]: Leaving directory `/root/xen-4.2.1/tools/vtpm_manage=
r'

gmake[2]: *** [subdir-install-vtpm_manager]=
 Error 2
gmake[2]: Leaving directory `/root/xen-4.2.1/tools'
gmake[1]=
: *** [subdirs-install] Error 2
gmake[1]: Leaving directory `/root/xen-4=
.2.1/tools'
gmake: *** [install-tools] Error 2

<= pre> 
So I know th=
at already one dependency is missing I think it's libgmp but I found no way=
 to build it on NetBSD.
Is vTPM buildable on NetBSD an=
d what does this error/warning which was treated as error mean?

 
Best Regards
=
= --_000_068F06DC4D106941B297C0C5F9F446EA49199E95FDaplesstripedo_-- --===============3276932328111566082== 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 --===============3276932328111566082==-- From xen-users-bounces@lists.xen.org Mon Feb 18 20:10:43 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 18 Feb 2013 20:10: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 1U7X1w-0000yr-3S; Mon, 18 Feb 2013 20:09:40 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U7X1t-0000yR-Ro; Mon, 18 Feb 2013 20:09:38 +0000 Received: from [85.158.138.51:20976] by server-10.bemta-3.messagelabs.com id 80/15-10609-08A82215; Mon, 18 Feb 2013 20:09:36 +0000 X-Env-Sender: rshriram@cs.ubc.ca X-Msg-Ref: server-5.tower-174.messagelabs.com!1361218174!28147797!1 X-Originating-IP: [142.103.6.52] X-SpamReason: No, hits=0.3 required=7.0 tests=RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 32767 invoked from network); 18 Feb 2013 20:09:35 -0000 Received: from smtp.cs.ubc.ca (HELO smtp.cs.ubc.ca) (142.103.6.52) by server-5.tower-174.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 18 Feb 2013 20:09:35 -0000 Received: from mail-ia0-f176.google.com (mail-ia0-f176.google.com [209.85.210.176]) (authenticated bits=0) by smtp.cs.ubc.ca (8.14.3/8.13.6) with ESMTP id r1IK9WQq027053 (version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=FAIL); Mon, 18 Feb 2013 12:09:32 -0800 Received: by mail-ia0-f176.google.com with SMTP id i18so5398378iac.35 for ; Mon, 18 Feb 2013 12:09:31 -0800 (PST) X-Received: by 10.50.37.162 with SMTP id z2mr7215343igj.13.1361218170943; Mon, 18 Feb 2013 12:09:30 -0800 (PST) MIME-Version: 1.0 Received: by 10.43.2.67 with HTTP; Mon, 18 Feb 2013 12:08:50 -0800 (PST) In-Reply-To: References: From: Shriram Rajagopalan Date: Mon, 18 Feb 2013 15:08:50 -0500 Message-ID: To: Hery Dian Septama Cc: "xen-users@lists.xen.org" , agya naila , "xen-devel@lists.xen.org" Subject: Re: [Xen-users] [Xen-devel] Remus disk replication failed X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: rshriram@cs.ubc.ca List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: 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 sorry for the delayed response. IIRC the blktap2 driver required for tapdisk replication doesnt exist in the mainstream dom0 kernels, IIRC. I havent used it in a long time myself. I suggest trying disk replication with DRBD. thanks shriram On Mon, Feb 18, 2013 at 5:38 AM, Hery Dian Septama wrote: > Hello, Anyone have a clue? I have tried but still failed :( > > On Sat, Feb 16, 2013 at 6:56 PM, agya naila wrote: >> >> Dear all, >> >> I am configure my machine to run the remus disk replication. I am using >> xen 4.2.3 installed from sources and Ubuntu 12.04 64 bit both for Dom0 and >> DomU. >> I have install the blktap and its work properly with configuration string >> phy or tap2 like this : >> disk = ['phy:/dev/vggroup/DomU,xvda,w'] >> or >> disk = ['tap2:tapdisk:aio:/dev/vggroup/DomU,xvda,w'] >> >> and remus command >> >> remus --no-net myvm mybackuphost >> >> >> However when I change the string as suggested on remus pages to enable the >> disk replication its still failed : >> >> name = "DomU" >> memory = 1024 >> disk = ['tap2:remus:10.10.10.3:8002|aio:/dev/vggroup/DomU,xvda,w'] >> vif = ['ip=192.168.1.55,bridge=xenbr0'] >> bootloader = "pygrub" >> >> with error messages : >> >> name1@machine1:~$ sudo xm create -c /etc/xen/DomU.cfg >> Using config file "/etc/xen/DomU.cfg". >> Error: ('create', '-aremus:10.10.10.3:8002|aio:/dev/vggroup/DomU') failed >> (512 ) >> >> and on the log file : >> >> >> name1@machine1:~$ sudo sudo tail /var/log/xen/xend.log >> mounted_vbd_uuid = dom0.create_vbd(vbd, disk); >> File >> "/usr/local/lib/python2.7/dist-packages/xen/xend/XendDomainInfo.py", line >> 3987, in create_vbd >> devid = dev_control.createDevice(config) >> File >> "/usr/local/lib/python2.7/dist-packages/xen/xend/server/BlktapController.py", >> line 174, in createDevice >> device = TapdiskController.create(params, file) >> File >> "/usr/local/lib/python2.7/dist-packages/xen/xend/server/BlktapController.py", >> line 286, in create >> return TapdiskController.exc('create', '-a%s:%s' % (dtype, image)) >> File >> "/usr/local/lib/python2.7/dist-packages/xen/xend/server/BlktapController.py", >> line 233, in exc >> (args, rc, out, err)) >> TapdiskException: ('create', >> '-aremus:10.10.10.3:8002|aio:/dev/vggroup/DomU') failed (512 ) >> >> Any hints and help would very appreciated. >> >> Regards, >> >> Agya >> >> >> _______________________________________________ >> Xen-devel mailing list >> Xen-devel@lists.xen.org >> http://lists.xen.org/xen-devel >> > > > _______________________________________________ > 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 Mon Feb 18 20:10:43 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 18 Feb 2013 20:10: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 1U7X1w-0000yr-3S; Mon, 18 Feb 2013 20:09:40 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U7X1t-0000yR-Ro; Mon, 18 Feb 2013 20:09:38 +0000 Received: from [85.158.138.51:20976] by server-10.bemta-3.messagelabs.com id 80/15-10609-08A82215; Mon, 18 Feb 2013 20:09:36 +0000 X-Env-Sender: rshriram@cs.ubc.ca X-Msg-Ref: server-5.tower-174.messagelabs.com!1361218174!28147797!1 X-Originating-IP: [142.103.6.52] X-SpamReason: No, hits=0.3 required=7.0 tests=RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 32767 invoked from network); 18 Feb 2013 20:09:35 -0000 Received: from smtp.cs.ubc.ca (HELO smtp.cs.ubc.ca) (142.103.6.52) by server-5.tower-174.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 18 Feb 2013 20:09:35 -0000 Received: from mail-ia0-f176.google.com (mail-ia0-f176.google.com [209.85.210.176]) (authenticated bits=0) by smtp.cs.ubc.ca (8.14.3/8.13.6) with ESMTP id r1IK9WQq027053 (version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=FAIL); Mon, 18 Feb 2013 12:09:32 -0800 Received: by mail-ia0-f176.google.com with SMTP id i18so5398378iac.35 for ; Mon, 18 Feb 2013 12:09:31 -0800 (PST) X-Received: by 10.50.37.162 with SMTP id z2mr7215343igj.13.1361218170943; Mon, 18 Feb 2013 12:09:30 -0800 (PST) MIME-Version: 1.0 Received: by 10.43.2.67 with HTTP; Mon, 18 Feb 2013 12:08:50 -0800 (PST) In-Reply-To: References: From: Shriram Rajagopalan Date: Mon, 18 Feb 2013 15:08:50 -0500 Message-ID: To: Hery Dian Septama Cc: "xen-users@lists.xen.org" , agya naila , "xen-devel@lists.xen.org" Subject: Re: [Xen-users] [Xen-devel] Remus disk replication failed X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: rshriram@cs.ubc.ca List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: 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 sorry for the delayed response. IIRC the blktap2 driver required for tapdisk replication doesnt exist in the mainstream dom0 kernels, IIRC. I havent used it in a long time myself. I suggest trying disk replication with DRBD. thanks shriram On Mon, Feb 18, 2013 at 5:38 AM, Hery Dian Septama wrote: > Hello, Anyone have a clue? I have tried but still failed :( > > On Sat, Feb 16, 2013 at 6:56 PM, agya naila wrote: >> >> Dear all, >> >> I am configure my machine to run the remus disk replication. I am using >> xen 4.2.3 installed from sources and Ubuntu 12.04 64 bit both for Dom0 and >> DomU. >> I have install the blktap and its work properly with configuration string >> phy or tap2 like this : >> disk = ['phy:/dev/vggroup/DomU,xvda,w'] >> or >> disk = ['tap2:tapdisk:aio:/dev/vggroup/DomU,xvda,w'] >> >> and remus command >> >> remus --no-net myvm mybackuphost >> >> >> However when I change the string as suggested on remus pages to enable the >> disk replication its still failed : >> >> name = "DomU" >> memory = 1024 >> disk = ['tap2:remus:10.10.10.3:8002|aio:/dev/vggroup/DomU,xvda,w'] >> vif = ['ip=192.168.1.55,bridge=xenbr0'] >> bootloader = "pygrub" >> >> with error messages : >> >> name1@machine1:~$ sudo xm create -c /etc/xen/DomU.cfg >> Using config file "/etc/xen/DomU.cfg". >> Error: ('create', '-aremus:10.10.10.3:8002|aio:/dev/vggroup/DomU') failed >> (512 ) >> >> and on the log file : >> >> >> name1@machine1:~$ sudo sudo tail /var/log/xen/xend.log >> mounted_vbd_uuid = dom0.create_vbd(vbd, disk); >> File >> "/usr/local/lib/python2.7/dist-packages/xen/xend/XendDomainInfo.py", line >> 3987, in create_vbd >> devid = dev_control.createDevice(config) >> File >> "/usr/local/lib/python2.7/dist-packages/xen/xend/server/BlktapController.py", >> line 174, in createDevice >> device = TapdiskController.create(params, file) >> File >> "/usr/local/lib/python2.7/dist-packages/xen/xend/server/BlktapController.py", >> line 286, in create >> return TapdiskController.exc('create', '-a%s:%s' % (dtype, image)) >> File >> "/usr/local/lib/python2.7/dist-packages/xen/xend/server/BlktapController.py", >> line 233, in exc >> (args, rc, out, err)) >> TapdiskException: ('create', >> '-aremus:10.10.10.3:8002|aio:/dev/vggroup/DomU') failed (512 ) >> >> Any hints and help would very appreciated. >> >> Regards, >> >> Agya >> >> >> _______________________________________________ >> Xen-devel mailing list >> Xen-devel@lists.xen.org >> http://lists.xen.org/xen-devel >> > > > _______________________________________________ > 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 Mon Feb 18 20:18:55 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 18 Feb 2013 20:18: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 1U7X9v-0001dT-5O; Mon, 18 Feb 2013 20:17:55 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U7X9u-0001dI-BY for xen-users@lists.xen.org; Mon, 18 Feb 2013 20:17:54 +0000 Received: from [85.158.143.99:25963] by server-1.bemta-4.messagelabs.com id 46/77-08839-17C82215; Mon, 18 Feb 2013 20:17:53 +0000 X-Env-Sender: eross@corp.locatrix.com X-Msg-Ref: server-6.tower-216.messagelabs.com!1361218672!21038842!1 X-Originating-IP: [74.125.83.49] 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.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 20297 invoked from network); 18 Feb 2013 20:17:52 -0000 Received: from mail-ee0-f49.google.com (HELO mail-ee0-f49.google.com) (74.125.83.49) by server-6.tower-216.messagelabs.com with RC4-SHA encrypted SMTP; 18 Feb 2013 20:17:52 -0000 Received: by mail-ee0-f49.google.com with SMTP id d4so3092774eek.36 for ; Mon, 18 Feb 2013 12:17:52 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=x-received:mime-version:in-reply-to:references:from:date:message-id :subject:to:content-type:x-gm-message-state; bh=j86PRUsIrSKz/MC1YzYJz3/6ReBNJEtDHgNVomjzMkw=; b=JNUvKJxBX+ZyEtpBCtej3bQP2yg4PwIaI86W6sFh59yabtg1Pg02ePdt2wIrupsQum IwN2l3DbC5J+OSFhToh0b2m1u9svdbSAU+d8nTDfSvMWP7ZCgRm82jB/x37WU42QyzdE nYfh1zAy8+Zb/HdwOgwGorY3dcHMRKO68wxfsX4QRUtQGnlFmPDvdM2HXbQYf/PIJo4E G6H1UNUaJdWH8/m7jCawAR1axy+n6Ur6IzEvYPnQ3GXkH97XgyqofPT/KWSXdbtCo7Xq TFqnN3QlPjZgACQoyYW1rTxDrU+yVTN6YdkbMAOFOWbX/HxpaHtBrVcs+sbflZ2P5f23 N/Eg== X-Received: by 10.14.202.71 with SMTP id c47mr47885191eeo.39.1361218672209; Mon, 18 Feb 2013 12:17:52 -0800 (PST) MIME-Version: 1.0 Received: by 10.223.4.144 with HTTP; Mon, 18 Feb 2013 12:17:30 -0800 (PST) In-Reply-To: References: From: Andrew Eross Date: Mon, 18 Feb 2013 17:17:30 -0300 Message-ID: To: xen-users@lists.xen.org X-Gm-Message-State: ALoCoQl5sW1pF8wydvGL3iOwc7ZxEU0nc0T6WAz9siGAdDxUMDGf3cYZVnAI41RId7+qScdyMnMx Subject: Re: [Xen-users] Xen 4.2.1 unable to get domain type for domid X-BeenThere: xen-users@lists.xen.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="===============4895591825764292938==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============4895591825764292938== Content-Type: multipart/alternative; boundary=047d7b343e386b2fcb04d6056b5e --047d7b343e386b2fcb04d6056b5e Content-Type: text/plain; charset=ISO-8859-1 Hi guys, I eventually gave up and went back to Xen 4.1.4, which works perfectly fine using the exact same install method and Ubuntu domU configuration, but just with xm. I wrote up how I did the Xen 4.2.1 install here for reference - http://locatrix.com/building-and-installing-xen-4-2-1-from-source-on-ubuntu-12-10/ And the Xen 4.1.4 install here - http://locatrix.com/building-and-install-xen-4-1-4-from-source-on-ubuntu-12-10/ I hope maybe some others could give it a try and see if they also are unable to install Ubuntu domUs with xl on 4.2.1 like I'd been trying to. Cheers, Andrew On Mon, Feb 18, 2013 at 10:04 AM, Andrew Eross wrote: > Strangely, if I use Ubuntu 13.04 (raring) for the installer netboot, it > works just fine with exactly the same configuration. > > However, I can't imagine that Ubuntu 12.04 wouldn't be supported for some > reason? > > > On Mon, Feb 18, 2013 at 7:58 AM, Andrew Eross wrote: > >> Hi guys, >> >> I'm running Xen 4.2.1, compiled manually so I can play with Remus and >> DRBD, running on Ubuntu 12.10. >> >> I keep getting this error when trying to start up my first VM to run the >> Ubuntu netboot installer. >> >> ----------------------------------------------------------------- >> root@left:/home/eross# xl create /etc/xen/ubuntu.cfg -c >> Parsing config from /etc/xen/ubuntu.cfg >> Daemon running with PID 1513 >> libxl: error: libxl_dom.c:34:libxl__domain_type: unable to get domain >> type for domid=1 >> Unable to attach console >> libxl: error: libxl_exec.c:118:libxl_report_child_exitstatus: console >> child [0] exited with error status 1 >> ----------------------------------------------------------------- >> >> Here's my VM's config: >> ----------------------------------------------------------------- >> root@left:/home/eross# cat /etc/xen/ubuntu.cfg >> name = "ubuntu" >> >> memory = 256 >> >> disk = [ 'drbd:drbd-vm,xvda,w' ] >> vif = [' '] >> >> kernel = "/var/lib/xen/images/ubuntu-netboot/vmlinuz" >> ramdisk = "/var/lib/xen/images/ubuntu-netboot/initrd.gz" >> extra = "debian-installer/exit/always_halt=true -- console=hvc0" >> ----------------------------------------------------------------- >> >> The ubuntu-netboot image there is 64-bit 12.04 Precise. >> >> Any ideas? >> >> Thank you! >> Andrew >> >> > --047d7b343e386b2fcb04d6056b5e Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Hi guys,

I eventually gave up and went back to Xen 4.1.4= , which works perfectly fine using the exact same install method and Ubuntu= domU configuration, but just with xm.

I wrote up = how I did the Xen 4.2.1 install here for reference -

And the Xen 4= .1.4 install here -

I hope maybe some o= thers could give it a try and see if they also are unable to install Ubuntu= domUs with xl on 4.2.1 like I'd been trying to.

Cheers,
Andrew


<= div class=3D"gmail_quote">On Mon, Feb 18, 2013 at 10:04 AM, Andrew Eross <eross@locatrix.com> wrote:
Strangely, if I use Ubuntu 13.04 (raring) fo= r the installer netboot, it works just fine with exactly the same configura= tion.

However, I can't imagine that Ubuntu 12.04 wouldn't = be supported for some reason?


On Mon, Feb 18, 2013 at 7:58 AM, Andrew Eros= s <eross@locatrix.com> wrote:
Hi guys,

I'm running Xen 4.2.1, compiled = manually so I can play with Remus and DRBD, running on Ubuntu 12.10.
<= div>
I keep getting this error when trying to start up my fir= st VM to run the Ubuntu netboot installer.

-------------------------------------------------------= ----------
root@left:/home/eross#=A0xl create /etc/xen/ubuntu.cfg= -c
Parsing config from /etc/xen/ubuntu.cfg
Daemon runn= ing with PID 1513
libxl: error: libxl_dom.c:34:libxl__domain_type: unable to get domain = type for domid=3D1
Unable to attach console
libxl: erro= r: libxl_exec.c:118:libxl_report_child_exitstatus: console child [0] exited= with error status 1
-----------------------------------------------------------------

Here's my VM's config:
-------------= ----------------------------------------------------
root@left:/h= ome/eross# cat /etc/xen/ubuntu.cfg
name =3D "ubuntu"

memory =3D 256

disk =3D [ 'drbd:drbd-vm,xvda,w' ]
vif =3D [' ']

kernel =3D "/var/lib/x= en/images/ubuntu-netboot/vmlinuz"
ramdisk =3D "/var/lib/xen/images/ubuntu-netboot/initrd.gz"
extra =3D "debian-installer/exit/always_halt=3Dtrue -- consol= e=3Dhvc0"
--------------------------------------------------= ---------------

The ubuntu-netboot image there is 64-bit 12.04 Precise.=

Any ideas?

Thank you!
Andrew



--047d7b343e386b2fcb04d6056b5e-- --===============4895591825764292938== 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 --===============4895591825764292938==-- From xen-users-bounces@lists.xen.org Mon Feb 18 20:18:55 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 18 Feb 2013 20:18: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 1U7X9v-0001dT-5O; Mon, 18 Feb 2013 20:17:55 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U7X9u-0001dI-BY for xen-users@lists.xen.org; Mon, 18 Feb 2013 20:17:54 +0000 Received: from [85.158.143.99:25963] by server-1.bemta-4.messagelabs.com id 46/77-08839-17C82215; Mon, 18 Feb 2013 20:17:53 +0000 X-Env-Sender: eross@corp.locatrix.com X-Msg-Ref: server-6.tower-216.messagelabs.com!1361218672!21038842!1 X-Originating-IP: [74.125.83.49] 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.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 20297 invoked from network); 18 Feb 2013 20:17:52 -0000 Received: from mail-ee0-f49.google.com (HELO mail-ee0-f49.google.com) (74.125.83.49) by server-6.tower-216.messagelabs.com with RC4-SHA encrypted SMTP; 18 Feb 2013 20:17:52 -0000 Received: by mail-ee0-f49.google.com with SMTP id d4so3092774eek.36 for ; Mon, 18 Feb 2013 12:17:52 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=x-received:mime-version:in-reply-to:references:from:date:message-id :subject:to:content-type:x-gm-message-state; bh=j86PRUsIrSKz/MC1YzYJz3/6ReBNJEtDHgNVomjzMkw=; b=JNUvKJxBX+ZyEtpBCtej3bQP2yg4PwIaI86W6sFh59yabtg1Pg02ePdt2wIrupsQum IwN2l3DbC5J+OSFhToh0b2m1u9svdbSAU+d8nTDfSvMWP7ZCgRm82jB/x37WU42QyzdE nYfh1zAy8+Zb/HdwOgwGorY3dcHMRKO68wxfsX4QRUtQGnlFmPDvdM2HXbQYf/PIJo4E G6H1UNUaJdWH8/m7jCawAR1axy+n6Ur6IzEvYPnQ3GXkH97XgyqofPT/KWSXdbtCo7Xq TFqnN3QlPjZgACQoyYW1rTxDrU+yVTN6YdkbMAOFOWbX/HxpaHtBrVcs+sbflZ2P5f23 N/Eg== X-Received: by 10.14.202.71 with SMTP id c47mr47885191eeo.39.1361218672209; Mon, 18 Feb 2013 12:17:52 -0800 (PST) MIME-Version: 1.0 Received: by 10.223.4.144 with HTTP; Mon, 18 Feb 2013 12:17:30 -0800 (PST) In-Reply-To: References: From: Andrew Eross Date: Mon, 18 Feb 2013 17:17:30 -0300 Message-ID: To: xen-users@lists.xen.org X-Gm-Message-State: ALoCoQl5sW1pF8wydvGL3iOwc7ZxEU0nc0T6WAz9siGAdDxUMDGf3cYZVnAI41RId7+qScdyMnMx Subject: Re: [Xen-users] Xen 4.2.1 unable to get domain type for domid X-BeenThere: xen-users@lists.xen.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="===============4895591825764292938==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============4895591825764292938== Content-Type: multipart/alternative; boundary=047d7b343e386b2fcb04d6056b5e --047d7b343e386b2fcb04d6056b5e Content-Type: text/plain; charset=ISO-8859-1 Hi guys, I eventually gave up and went back to Xen 4.1.4, which works perfectly fine using the exact same install method and Ubuntu domU configuration, but just with xm. I wrote up how I did the Xen 4.2.1 install here for reference - http://locatrix.com/building-and-installing-xen-4-2-1-from-source-on-ubuntu-12-10/ And the Xen 4.1.4 install here - http://locatrix.com/building-and-install-xen-4-1-4-from-source-on-ubuntu-12-10/ I hope maybe some others could give it a try and see if they also are unable to install Ubuntu domUs with xl on 4.2.1 like I'd been trying to. Cheers, Andrew On Mon, Feb 18, 2013 at 10:04 AM, Andrew Eross wrote: > Strangely, if I use Ubuntu 13.04 (raring) for the installer netboot, it > works just fine with exactly the same configuration. > > However, I can't imagine that Ubuntu 12.04 wouldn't be supported for some > reason? > > > On Mon, Feb 18, 2013 at 7:58 AM, Andrew Eross wrote: > >> Hi guys, >> >> I'm running Xen 4.2.1, compiled manually so I can play with Remus and >> DRBD, running on Ubuntu 12.10. >> >> I keep getting this error when trying to start up my first VM to run the >> Ubuntu netboot installer. >> >> ----------------------------------------------------------------- >> root@left:/home/eross# xl create /etc/xen/ubuntu.cfg -c >> Parsing config from /etc/xen/ubuntu.cfg >> Daemon running with PID 1513 >> libxl: error: libxl_dom.c:34:libxl__domain_type: unable to get domain >> type for domid=1 >> Unable to attach console >> libxl: error: libxl_exec.c:118:libxl_report_child_exitstatus: console >> child [0] exited with error status 1 >> ----------------------------------------------------------------- >> >> Here's my VM's config: >> ----------------------------------------------------------------- >> root@left:/home/eross# cat /etc/xen/ubuntu.cfg >> name = "ubuntu" >> >> memory = 256 >> >> disk = [ 'drbd:drbd-vm,xvda,w' ] >> vif = [' '] >> >> kernel = "/var/lib/xen/images/ubuntu-netboot/vmlinuz" >> ramdisk = "/var/lib/xen/images/ubuntu-netboot/initrd.gz" >> extra = "debian-installer/exit/always_halt=true -- console=hvc0" >> ----------------------------------------------------------------- >> >> The ubuntu-netboot image there is 64-bit 12.04 Precise. >> >> Any ideas? >> >> Thank you! >> Andrew >> >> > --047d7b343e386b2fcb04d6056b5e Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Hi guys,

I eventually gave up and went back to Xen 4.1.4= , which works perfectly fine using the exact same install method and Ubuntu= domU configuration, but just with xm.

I wrote up = how I did the Xen 4.2.1 install here for reference -

And the Xen 4= .1.4 install here -

I hope maybe some o= thers could give it a try and see if they also are unable to install Ubuntu= domUs with xl on 4.2.1 like I'd been trying to.

Cheers,
Andrew


<= div class=3D"gmail_quote">On Mon, Feb 18, 2013 at 10:04 AM, Andrew Eross <eross@locatrix.com> wrote:
Strangely, if I use Ubuntu 13.04 (raring) fo= r the installer netboot, it works just fine with exactly the same configura= tion.

However, I can't imagine that Ubuntu 12.04 wouldn't = be supported for some reason?


On Mon, Feb 18, 2013 at 7:58 AM, Andrew Eros= s <eross@locatrix.com> wrote:
Hi guys,

I'm running Xen 4.2.1, compiled = manually so I can play with Remus and DRBD, running on Ubuntu 12.10.
<= div>
I keep getting this error when trying to start up my fir= st VM to run the Ubuntu netboot installer.

-------------------------------------------------------= ----------
root@left:/home/eross#=A0xl create /etc/xen/ubuntu.cfg= -c
Parsing config from /etc/xen/ubuntu.cfg
Daemon runn= ing with PID 1513
libxl: error: libxl_dom.c:34:libxl__domain_type: unable to get domain = type for domid=3D1
Unable to attach console
libxl: erro= r: libxl_exec.c:118:libxl_report_child_exitstatus: console child [0] exited= with error status 1
-----------------------------------------------------------------

Here's my VM's config:
-------------= ----------------------------------------------------
root@left:/h= ome/eross# cat /etc/xen/ubuntu.cfg
name =3D "ubuntu"

memory =3D 256

disk =3D [ 'drbd:drbd-vm,xvda,w' ]
vif =3D [' ']

kernel =3D "/var/lib/x= en/images/ubuntu-netboot/vmlinuz"
ramdisk =3D "/var/lib/xen/images/ubuntu-netboot/initrd.gz"
extra =3D "debian-installer/exit/always_halt=3Dtrue -- consol= e=3Dhvc0"
--------------------------------------------------= ---------------

The ubuntu-netboot image there is 64-bit 12.04 Precise.=

Any ideas?

Thank you!
Andrew



--047d7b343e386b2fcb04d6056b5e-- --===============4895591825764292938== 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 --===============4895591825764292938==-- From xen-users-bounces@lists.xen.org Mon Feb 18 21:13:15 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 18 Feb 2013 21:13: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 1U7Y0Y-0002vF-An; Mon, 18 Feb 2013 21:12:18 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U7Y0V-0002v0-Th; Mon, 18 Feb 2013 21:12:16 +0000 Received: from [85.158.143.35:14584] by server-3.bemta-4.messagelabs.com id DE/58-08920-E2992215; Mon, 18 Feb 2013 21:12:14 +0000 X-Env-Sender: agya.naila@gmail.com X-Msg-Ref: server-9.tower-21.messagelabs.com!1361221873!4649684!1 X-Originating-IP: [74.125.82.42] 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.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 20165 invoked from network); 18 Feb 2013 21:11:14 -0000 Received: from mail-wg0-f42.google.com (HELO mail-wg0-f42.google.com) (74.125.82.42) by server-9.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 18 Feb 2013 21:11:14 -0000 Received: by mail-wg0-f42.google.com with SMTP id 12so3075520wgh.5 for ; Mon, 18 Feb 2013 13:11:13 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=dX4XXsrZw6ZKmgAo41Se82Ywy7T6tm3Bi27cTWZv++E=; b=SGICjMW14G/C6dJn4r54q9kS8+sU+1EGHFmDImL/LSY6xcYdpJMLrl9zrwzw8reUId Qnb1u9v9A4wRbcWqlG5b7+R387AiA6Rd5nYAwXVvwBGMzBjsXVXQF4YqeqXVF3MRnwFA KZZqxoEzxoVctk3tpApHJiLWudmSpS2/eEoBq4qVc4Ko9gRmHDfC99LcfpPKKelUpPZ/ TtH4V6znEwN/Jel90NHoqehqeJyBVIj+KrThQfaKkBBisR0xk5h7oRUBr12/6ytf4hYN wolbt0zPEden3nbA2wl2vhibiU+BcOFJsz279qMMRhozL0tyJsNFzt7VG6i+tpxONVux HiJw== MIME-Version: 1.0 X-Received: by 10.180.102.7 with SMTP id fk7mr21090960wib.27.1361221872860; Mon, 18 Feb 2013 13:11:12 -0800 (PST) Received: by 10.216.236.13 with HTTP; Mon, 18 Feb 2013 13:11:12 -0800 (PST) In-Reply-To: References: Date: Mon, 18 Feb 2013 22:11:12 +0100 Message-ID: From: agya naila To: rshriram@cs.ubc.ca Cc: "xen-users@lists.xen.org" , "xen-devel@lists.xen.org" Subject: Re: [Xen-users] [Xen-devel] Remus disk replication failed X-BeenThere: xen-users@lists.xen.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="===============3731334846460705237==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============3731334846460705237== Content-Type: multipart/alternative; boundary=f46d0444e7d7313d5804d6062a44 --f46d0444e7d7313d5804d6062a44 Content-Type: text/plain; charset=ISO-8859-1 On Mon, Feb 18, 2013 at 9:08 PM, Shriram Rajagopalan wrote: > hi > Thank you shriram. > sorry for the delayed response. IIRC the blktap2 driver required for > tapdisk replication doesnt exist in the mainstream dom0 kernels, IIRC. > I havent used it in a long time myself. I suggest trying disk > replication with DRBD. > > I am also found some information here http://osdir.com/ml/xen-users/2011-07/msg00653.html about blktap2 problem on amd64 architecture. I have tried to install and configure the DRBD but its didn't connect each other. I used drbd-8.3.11-remus and installed as follow cd /usr/src/ wget http://remusha.wikidot.com/local--files/configuring-and-installing-remus/drbd-8.3.11-remus.tar.gz tar xzf drbd-8.3.9-remus.tar.gz chown -R root:root drbd-8.3-remus cd /usr/src/drbd-8.3-remus chmod 777 autogen.sh ./autogen.sh dpkg-buildpackage -b -uc cd /usr/src/drbd-8.3-remus/drbd make clean make make install cd /usr/src/ cp /usr/src/drbd-8.3-remus/scripts/global_common.conf.protoD /etc/drbd.d/global_common.conf cp /usr/src/drbd-8.3-remus/scripts/testvms_protoD.res /etc/drbd.d/SystemHA_protoD.res sudo apt-get install drbd8-utils from tutorial http://remusha.wikidot.com/configuring-and-installing-remus My *.res configuration as follow : resource drbd-vm{ device /dev/drbd1; disk /dev/vgvoip/DomU; meta-disk internal; on machine1 { address 10.10.10.1:7789; } on machine2 { address 10.10.10.3:7789; } } and then I invoke command to create that meta drbdadm create-md drbd-vm However, when I try to make this configuration up by : drbdadm up drbd-vm Its come with error : $ sudo drbdadm up drbd-vm 1: Failure: (124) Device is attached to a disk (use detach first) Command 'drbdsetup 1 disk /dev/vgvoip/DomU /dev/vgvoip/DomU internal --set-defaults --create-device --fencing=dont-care --on-io-error=pass_on' terminated with exit code 10 If I run the $ sudo drbdadm detach drbd-vm Its come error $ sudo drbdadm detach drbd-vm 1: State change failed: (-2) Need access to UpToDate data Command 'drbdsetup 1 detach' terminated with exit code 17 Here the /proc/drbd on both machine Machine 1 $ sudo cat /proc/drbd version: 8.3.11 (api:88/proto:86-96) GIT-hash: 0de839cee13a4160eed6037c4bddd066645e23c5 build by root@machine1, 2013-02-18 18:49:57 1: cs:StandAlone ro:Primary/Unknown ds:UpToDate/DUnknown r----s ns:0 nr:0 dw:0 dr:1712 al:0 bm:0 lo:0 pe:0 ua:0 ap:0 ep:1 wo:b def:0 chkpt:0 oos:10485404 Machine 2 $ sudo cat /proc/drbd version: 8.3.11 (api:88/proto:86-96) GIT-hash: 0de839cee13a4160eed6037c4bddd066645e23c5 build by root@machine2, 2013-02-18 19:26:57 1: cs:StandAlone ro:Secondary/Unknown ds:Inconsistent/DUnknown r----s ns:0 nr:0 dw:0 dr:0 al:0 bm:0 lo:0 pe:0 ua:0 ap:0 ep:1 wo:b def:0 chkpt:0 oos:10485404 Do you have some hints? Thank you, Agya thanks > shriram > > On Mon, Feb 18, 2013 at 5:38 AM, Hery Dian Septama > wrote: > > Hello, Anyone have a clue? I have tried but still failed :( > > > > On Sat, Feb 16, 2013 at 6:56 PM, agya naila > wrote: > >> > >> Dear all, > >> > >> I am configure my machine to run the remus disk replication. I am using > >> xen 4.2.3 installed from sources and Ubuntu 12.04 64 bit both for Dom0 > and > >> DomU. > >> I have install the blktap and its work properly with configuration > string > >> phy or tap2 like this : > >> disk = ['phy:/dev/vggroup/DomU,xvda,w'] > >> or > >> disk = ['tap2:tapdisk:aio:/dev/vggroup/DomU,xvda,w'] > >> > >> and remus command > >> > >> remus --no-net myvm mybackuphost > >> > >> > >> However when I change the string as suggested on remus pages to enable > the > >> disk replication its still failed : > >> > >> name = "DomU" > >> memory = 1024 > >> disk = ['tap2:remus:10.10.10.3:8002|aio:/dev/vggroup/DomU,xvda,w'] > >> vif = ['ip=192.168.1.55,bridge=xenbr0'] > >> bootloader = "pygrub" > >> > >> with error messages : > >> > >> name1@machine1:~$ sudo xm create -c /etc/xen/DomU.cfg > >> Using config file "/etc/xen/DomU.cfg". > >> Error: ('create', '-aremus:10.10.10.3:8002|aio:/dev/vggroup/DomU') > failed > >> (512 ) > >> > >> and on the log file : > >> > >> > >> name1@machine1:~$ sudo sudo tail /var/log/xen/xend.log > >> mounted_vbd_uuid = dom0.create_vbd(vbd, disk); > >> File > >> "/usr/local/lib/python2.7/dist-packages/xen/xend/XendDomainInfo.py", > line > >> 3987, in create_vbd > >> devid = dev_control.createDevice(config) > >> File > >> > "/usr/local/lib/python2.7/dist-packages/xen/xend/server/BlktapController.py", > >> line 174, in createDevice > >> device = TapdiskController.create(params, file) > >> File > >> > "/usr/local/lib/python2.7/dist-packages/xen/xend/server/BlktapController.py", > >> line 286, in create > >> return TapdiskController.exc('create', '-a%s:%s' % (dtype, image)) > >> File > >> > "/usr/local/lib/python2.7/dist-packages/xen/xend/server/BlktapController.py", > >> line 233, in exc > >> (args, rc, out, err)) > >> TapdiskException: ('create', > >> '-aremus:10.10.10.3:8002|aio:/dev/vggroup/DomU') failed (512 ) > >> > >> Any hints and help would very appreciated. > >> > >> Regards, > >> > >> Agya > >> > >> > >> _______________________________________________ > >> Xen-devel mailing list > >> Xen-devel@lists.xen.org > >> http://lists.xen.org/xen-devel > >> > > > > > > _______________________________________________ > > Xen-devel mailing list > > Xen-devel@lists.xen.org > > http://lists.xen.org/xen-devel > > > --f46d0444e7d7313d5804d6062a44 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
On Mon, Feb 18, 2013 at 9:08 PM, Shriram Raj= agopalan <rshriram@cs.ubc.ca> wrote:
hi

Thank you shriram.
=A0
=A0sorry for the delayed response. IIRC the blktap2 driver required for
tapdisk replication doesnt exist in the mainstream dom0 kernels, IIRC.
=A0I havent used it in a long time myself. I suggest trying disk
replication with DRBD.


I am also found some information here= =A0http://o= sdir.com/ml/xen-users/2011-07/msg00653.html about blktap2 problem on am= d64 architecture. I have tried to install and configure the DRBD but its di= dn't connect each other.
I used=A0drbd-8.3.11-remus and installed= as follow=A0
cd /usr/src/
wget http://remusha.wikidot.com/local--f=
iles/configuring-and-installing-remus/drbd-8.3.11-remus.tar.gz
tar xzf drbd-8.3.9-remus.tar.gz
chown -R root:root drbd-8.3-remus=20
cd /usr/src/drbd-8.3-remus
chmod 777 autogen.sh
./autogen.sh
dpkg-buildpackage -b -uc
cd /usr/src/drbd-8.3-remus/drbd
make clean
make
make install
cd /usr/src/
cp /usr/src/drbd-8.3-remus/scripts/global_common.conf.protoD /etc/drbd.d/gl=
obal_common.conf
cp /usr/src/drbd-8.3-remus/scripts/testvms_protoD.res /etc/drbd.d/SystemHA_=
protoD.res
sudo apt-get install drbd8-utils

My *.res configuration as fo= llow :

resource drb= d-vm{
=A0 device =A0= =A0/dev/drbd1;
=A0 = disk =A0 =A0 =A0/dev/vgvoip/DomU;
=A0 meta-disk internal;
=A0 on machine1 {
=A0 =A0 address =A0 10.10.10.1:7789;
=A0 }
=A0 on machine2 {
=A0 =A0 address =A0 10.10.10.3:7789;
=A0 }
}

and th= en I invoke command to create that meta

drbdadm create-md drbd-vm
However, when I try to make this configur=
ation up by :
drbdadm up drbd-vm
Its come with error :
$ sudo drbdadm up drbd=
-vm
1: Failure: (124) Device is attached to a disk (use detach first)
Command 'drbdsetup 1 disk /dev/vgvoip/DomU /dev/vgvoip/DomU internal --=
set-defaults --create-device --fencing=3Ddont-care --on-io-error=3Dpass_on&=
#39; terminated with exit code 10I=
f I run the=A0

$ sudo drbdadm=
 detach drbd-vm
Its come error 
$ sudo drbdadm detach drbd-vm
1: State change failed: (-2) Need access to UpToDate data
Command 'drbdsetup 1 detach' terminated with exit code 17
Here the /=
proc/drbd on both machine
Machine 1


$ sudo cat /proc/drbd
version: 8.3.11 (api:88/proto:86-96)
GIT-hash: 0de839cee13a4160eed6037c4bddd066645e23c5 build by root@machine1, =
2013-02-18 18:49:57

 1: cs:StandAlone ro:Primary/Unknown ds:UpToDate/DUnknown   r----s
    ns:0 nr:0 dw:0 dr:1712 al:0 bm:0 lo:0 pe:0 ua:0 ap:0 ep:1 wo:b def:0 ch=
kpt:0 oos:10485404


Machine 2
$ sudo c=
at /proc/drbd
version: 8.3.11 (api:88/proto:86-96)
GIT-hash: 0de839cee13a4160eed6037c4bddd066645e23c5 build by root@machine2, =
2013-02-18 19:26:57

 1: cs:StandAlone ro:Secondary/Unknown ds:Inconsistent/DUnknown   r----s
    ns:0 nr:0 dw:0 dr:0 al:0 bm:0 lo:0 pe:0 ua:0 ap:0 ep:1 wo:b def:0 chkpt=
:0 oos:10485404


Do you have some =
hints?


Thank you,

=
Agya

thanks
shriram

On Mon, Feb 18, 2013 at 5:38 AM, Hery Dian Septama <herydians@gmail.com> wrote:
> Hello, Anyone have a clue? I have tried but still failed :(
>
> On Sat, Feb 16, 2013 at 6:56 PM, agya naila <agya.naila@gmail.com> wrote:
>>
>> Dear all,
>>
>> I am configure my machine to run the remus disk replication. I am = using
>> xen 4.2.3 installed from sources and Ubuntu 12.04 64 bit both for = Dom0 and
>> DomU.
>> I have install the blktap and its work properly with configuration= string
>> phy or tap2 like this :
>> disk =3D ['phy:/dev/vggroup/DomU,xvda,w']
>> or
>> disk =3D ['tap2:tapdisk:aio:/dev/vggroup/DomU,xvda,w']
>>
>> and remus command
>>
>> remus --no-net myvm mybackuphost
>>
>>
>> However when I change the string as suggested on remus pages to en= able the
>> disk replication its still failed :
>>
>> name =3D "DomU"
>> memory =3D 1024
>> disk =3D ['tap2:remus:10.10.10.3:8002|aio:/dev/vggroup/DomU,xv= da,w']
>> vif =3D ['ip=3D192.168.1.55,bridge=3Dxenbr0']
>> bootloader =3D "pygrub"
>>
>> with error messages :
>>
>> name1@machine1:~$ sudo xm create -c /etc/xen/DomU.cfg
>> Using config file "/etc/xen/DomU.cfg".
>> Error: ('create', '-aremus:10.10.10.3:8002|aio:/dev/vg= group/DomU') failed
>> (512 =A0)
>>
>> and on the log file :
>>
>>
>> name1@machine1:~$ sudo sudo tail /var/log/xen/xend.log
>> =A0 =A0 mounted_vbd_uuid =3D dom0.create_vbd(vbd, disk);
>> =A0 File
>> "/usr/local/lib/python2.7/dist-packages/xen/xend/XendDomainIn= fo.py", line
>> 3987, in create_vbd
>> =A0 =A0 devid =3D dev_control.createDevice(config)
>> =A0 File
>> "/usr/local/lib/python2.7/dist-packages/xen/xend/server/Blkta= pController.py",
>> line 174, in createDevice
>> =A0 =A0 device =3D TapdiskController.create(params, file)
>> =A0 File
>> "/usr/local/lib/python2.7/dist-packages/xen/xend/server/Blkta= pController.py",
>> line 286, in create
>> =A0 =A0 return TapdiskController.exc('create', '-a%s:%= s' % (dtype, image))
>> =A0 File
>> "/usr/local/lib/python2.7/dist-packages/xen/xend/server/Blkta= pController.py",
>> line 233, in exc
>> =A0 =A0 (args, rc, out, err))
>> TapdiskException: ('create',
>> '-aremus:10.10.10.3:8002|aio:/dev/vggroup/DomU') failed (5= 12 =A0)
>>
>> Any hints and help would very appreciated.
>>
>> Regards,
>>
>> Agya
>>
>>
>> _______________________________________________
>> Xen-devel mailing list
>> Xen-devel@lists.xen.org=
>> http:= //lists.xen.org/xen-devel
>>
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org=
> http://li= sts.xen.org/xen-devel
>

--f46d0444e7d7313d5804d6062a44-- --===============3731334846460705237== 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 --===============3731334846460705237==-- From xen-users-bounces@lists.xen.org Mon Feb 18 21:13:15 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 18 Feb 2013 21:13: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 1U7Y0Y-0002vF-An; Mon, 18 Feb 2013 21:12:18 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U7Y0V-0002v0-Th; Mon, 18 Feb 2013 21:12:16 +0000 Received: from [85.158.143.35:14584] by server-3.bemta-4.messagelabs.com id DE/58-08920-E2992215; Mon, 18 Feb 2013 21:12:14 +0000 X-Env-Sender: agya.naila@gmail.com X-Msg-Ref: server-9.tower-21.messagelabs.com!1361221873!4649684!1 X-Originating-IP: [74.125.82.42] 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.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 20165 invoked from network); 18 Feb 2013 21:11:14 -0000 Received: from mail-wg0-f42.google.com (HELO mail-wg0-f42.google.com) (74.125.82.42) by server-9.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 18 Feb 2013 21:11:14 -0000 Received: by mail-wg0-f42.google.com with SMTP id 12so3075520wgh.5 for ; Mon, 18 Feb 2013 13:11:13 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=dX4XXsrZw6ZKmgAo41Se82Ywy7T6tm3Bi27cTWZv++E=; b=SGICjMW14G/C6dJn4r54q9kS8+sU+1EGHFmDImL/LSY6xcYdpJMLrl9zrwzw8reUId Qnb1u9v9A4wRbcWqlG5b7+R387AiA6Rd5nYAwXVvwBGMzBjsXVXQF4YqeqXVF3MRnwFA KZZqxoEzxoVctk3tpApHJiLWudmSpS2/eEoBq4qVc4Ko9gRmHDfC99LcfpPKKelUpPZ/ TtH4V6znEwN/Jel90NHoqehqeJyBVIj+KrThQfaKkBBisR0xk5h7oRUBr12/6ytf4hYN wolbt0zPEden3nbA2wl2vhibiU+BcOFJsz279qMMRhozL0tyJsNFzt7VG6i+tpxONVux HiJw== MIME-Version: 1.0 X-Received: by 10.180.102.7 with SMTP id fk7mr21090960wib.27.1361221872860; Mon, 18 Feb 2013 13:11:12 -0800 (PST) Received: by 10.216.236.13 with HTTP; Mon, 18 Feb 2013 13:11:12 -0800 (PST) In-Reply-To: References: Date: Mon, 18 Feb 2013 22:11:12 +0100 Message-ID: From: agya naila To: rshriram@cs.ubc.ca Cc: "xen-users@lists.xen.org" , "xen-devel@lists.xen.org" Subject: Re: [Xen-users] [Xen-devel] Remus disk replication failed X-BeenThere: xen-users@lists.xen.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="===============3731334846460705237==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============3731334846460705237== Content-Type: multipart/alternative; boundary=f46d0444e7d7313d5804d6062a44 --f46d0444e7d7313d5804d6062a44 Content-Type: text/plain; charset=ISO-8859-1 On Mon, Feb 18, 2013 at 9:08 PM, Shriram Rajagopalan wrote: > hi > Thank you shriram. > sorry for the delayed response. IIRC the blktap2 driver required for > tapdisk replication doesnt exist in the mainstream dom0 kernels, IIRC. > I havent used it in a long time myself. I suggest trying disk > replication with DRBD. > > I am also found some information here http://osdir.com/ml/xen-users/2011-07/msg00653.html about blktap2 problem on amd64 architecture. I have tried to install and configure the DRBD but its didn't connect each other. I used drbd-8.3.11-remus and installed as follow cd /usr/src/ wget http://remusha.wikidot.com/local--files/configuring-and-installing-remus/drbd-8.3.11-remus.tar.gz tar xzf drbd-8.3.9-remus.tar.gz chown -R root:root drbd-8.3-remus cd /usr/src/drbd-8.3-remus chmod 777 autogen.sh ./autogen.sh dpkg-buildpackage -b -uc cd /usr/src/drbd-8.3-remus/drbd make clean make make install cd /usr/src/ cp /usr/src/drbd-8.3-remus/scripts/global_common.conf.protoD /etc/drbd.d/global_common.conf cp /usr/src/drbd-8.3-remus/scripts/testvms_protoD.res /etc/drbd.d/SystemHA_protoD.res sudo apt-get install drbd8-utils from tutorial http://remusha.wikidot.com/configuring-and-installing-remus My *.res configuration as follow : resource drbd-vm{ device /dev/drbd1; disk /dev/vgvoip/DomU; meta-disk internal; on machine1 { address 10.10.10.1:7789; } on machine2 { address 10.10.10.3:7789; } } and then I invoke command to create that meta drbdadm create-md drbd-vm However, when I try to make this configuration up by : drbdadm up drbd-vm Its come with error : $ sudo drbdadm up drbd-vm 1: Failure: (124) Device is attached to a disk (use detach first) Command 'drbdsetup 1 disk /dev/vgvoip/DomU /dev/vgvoip/DomU internal --set-defaults --create-device --fencing=dont-care --on-io-error=pass_on' terminated with exit code 10 If I run the $ sudo drbdadm detach drbd-vm Its come error $ sudo drbdadm detach drbd-vm 1: State change failed: (-2) Need access to UpToDate data Command 'drbdsetup 1 detach' terminated with exit code 17 Here the /proc/drbd on both machine Machine 1 $ sudo cat /proc/drbd version: 8.3.11 (api:88/proto:86-96) GIT-hash: 0de839cee13a4160eed6037c4bddd066645e23c5 build by root@machine1, 2013-02-18 18:49:57 1: cs:StandAlone ro:Primary/Unknown ds:UpToDate/DUnknown r----s ns:0 nr:0 dw:0 dr:1712 al:0 bm:0 lo:0 pe:0 ua:0 ap:0 ep:1 wo:b def:0 chkpt:0 oos:10485404 Machine 2 $ sudo cat /proc/drbd version: 8.3.11 (api:88/proto:86-96) GIT-hash: 0de839cee13a4160eed6037c4bddd066645e23c5 build by root@machine2, 2013-02-18 19:26:57 1: cs:StandAlone ro:Secondary/Unknown ds:Inconsistent/DUnknown r----s ns:0 nr:0 dw:0 dr:0 al:0 bm:0 lo:0 pe:0 ua:0 ap:0 ep:1 wo:b def:0 chkpt:0 oos:10485404 Do you have some hints? Thank you, Agya thanks > shriram > > On Mon, Feb 18, 2013 at 5:38 AM, Hery Dian Septama > wrote: > > Hello, Anyone have a clue? I have tried but still failed :( > > > > On Sat, Feb 16, 2013 at 6:56 PM, agya naila > wrote: > >> > >> Dear all, > >> > >> I am configure my machine to run the remus disk replication. I am using > >> xen 4.2.3 installed from sources and Ubuntu 12.04 64 bit both for Dom0 > and > >> DomU. > >> I have install the blktap and its work properly with configuration > string > >> phy or tap2 like this : > >> disk = ['phy:/dev/vggroup/DomU,xvda,w'] > >> or > >> disk = ['tap2:tapdisk:aio:/dev/vggroup/DomU,xvda,w'] > >> > >> and remus command > >> > >> remus --no-net myvm mybackuphost > >> > >> > >> However when I change the string as suggested on remus pages to enable > the > >> disk replication its still failed : > >> > >> name = "DomU" > >> memory = 1024 > >> disk = ['tap2:remus:10.10.10.3:8002|aio:/dev/vggroup/DomU,xvda,w'] > >> vif = ['ip=192.168.1.55,bridge=xenbr0'] > >> bootloader = "pygrub" > >> > >> with error messages : > >> > >> name1@machine1:~$ sudo xm create -c /etc/xen/DomU.cfg > >> Using config file "/etc/xen/DomU.cfg". > >> Error: ('create', '-aremus:10.10.10.3:8002|aio:/dev/vggroup/DomU') > failed > >> (512 ) > >> > >> and on the log file : > >> > >> > >> name1@machine1:~$ sudo sudo tail /var/log/xen/xend.log > >> mounted_vbd_uuid = dom0.create_vbd(vbd, disk); > >> File > >> "/usr/local/lib/python2.7/dist-packages/xen/xend/XendDomainInfo.py", > line > >> 3987, in create_vbd > >> devid = dev_control.createDevice(config) > >> File > >> > "/usr/local/lib/python2.7/dist-packages/xen/xend/server/BlktapController.py", > >> line 174, in createDevice > >> device = TapdiskController.create(params, file) > >> File > >> > "/usr/local/lib/python2.7/dist-packages/xen/xend/server/BlktapController.py", > >> line 286, in create > >> return TapdiskController.exc('create', '-a%s:%s' % (dtype, image)) > >> File > >> > "/usr/local/lib/python2.7/dist-packages/xen/xend/server/BlktapController.py", > >> line 233, in exc > >> (args, rc, out, err)) > >> TapdiskException: ('create', > >> '-aremus:10.10.10.3:8002|aio:/dev/vggroup/DomU') failed (512 ) > >> > >> Any hints and help would very appreciated. > >> > >> Regards, > >> > >> Agya > >> > >> > >> _______________________________________________ > >> Xen-devel mailing list > >> Xen-devel@lists.xen.org > >> http://lists.xen.org/xen-devel > >> > > > > > > _______________________________________________ > > Xen-devel mailing list > > Xen-devel@lists.xen.org > > http://lists.xen.org/xen-devel > > > --f46d0444e7d7313d5804d6062a44 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
On Mon, Feb 18, 2013 at 9:08 PM, Shriram Raj= agopalan <rshriram@cs.ubc.ca> wrote:
hi

Thank you shriram.
=A0
=A0sorry for the delayed response. IIRC the blktap2 driver required for
tapdisk replication doesnt exist in the mainstream dom0 kernels, IIRC.
=A0I havent used it in a long time myself. I suggest trying disk
replication with DRBD.


I am also found some information here= =A0http://o= sdir.com/ml/xen-users/2011-07/msg00653.html about blktap2 problem on am= d64 architecture. I have tried to install and configure the DRBD but its di= dn't connect each other.
I used=A0drbd-8.3.11-remus and installed= as follow=A0
cd /usr/src/
wget http://remusha.wikidot.com/local--f=
iles/configuring-and-installing-remus/drbd-8.3.11-remus.tar.gz
tar xzf drbd-8.3.9-remus.tar.gz
chown -R root:root drbd-8.3-remus=20
cd /usr/src/drbd-8.3-remus
chmod 777 autogen.sh
./autogen.sh
dpkg-buildpackage -b -uc
cd /usr/src/drbd-8.3-remus/drbd
make clean
make
make install
cd /usr/src/
cp /usr/src/drbd-8.3-remus/scripts/global_common.conf.protoD /etc/drbd.d/gl=
obal_common.conf
cp /usr/src/drbd-8.3-remus/scripts/testvms_protoD.res /etc/drbd.d/SystemHA_=
protoD.res
sudo apt-get install drbd8-utils

My *.res configuration as fo= llow :

resource drb= d-vm{
=A0 device =A0= =A0/dev/drbd1;
=A0 = disk =A0 =A0 =A0/dev/vgvoip/DomU;
=A0 meta-disk internal;
=A0 on machine1 {
=A0 =A0 address =A0 10.10.10.1:7789;
=A0 }
=A0 on machine2 {
=A0 =A0 address =A0 10.10.10.3:7789;
=A0 }
}

and th= en I invoke command to create that meta

drbdadm create-md drbd-vm
However, when I try to make this configur=
ation up by :
drbdadm up drbd-vm
Its come with error :
$ sudo drbdadm up drbd=
-vm
1: Failure: (124) Device is attached to a disk (use detach first)
Command 'drbdsetup 1 disk /dev/vgvoip/DomU /dev/vgvoip/DomU internal --=
set-defaults --create-device --fencing=3Ddont-care --on-io-error=3Dpass_on&=
#39; terminated with exit code 10I=
f I run the=A0

$ sudo drbdadm=
 detach drbd-vm
Its come error 
$ sudo drbdadm detach drbd-vm
1: State change failed: (-2) Need access to UpToDate data
Command 'drbdsetup 1 detach' terminated with exit code 17
Here the /=
proc/drbd on both machine
Machine 1


$ sudo cat /proc/drbd
version: 8.3.11 (api:88/proto:86-96)
GIT-hash: 0de839cee13a4160eed6037c4bddd066645e23c5 build by root@machine1, =
2013-02-18 18:49:57

 1: cs:StandAlone ro:Primary/Unknown ds:UpToDate/DUnknown   r----s
    ns:0 nr:0 dw:0 dr:1712 al:0 bm:0 lo:0 pe:0 ua:0 ap:0 ep:1 wo:b def:0 ch=
kpt:0 oos:10485404


Machine 2
$ sudo c=
at /proc/drbd
version: 8.3.11 (api:88/proto:86-96)
GIT-hash: 0de839cee13a4160eed6037c4bddd066645e23c5 build by root@machine2, =
2013-02-18 19:26:57

 1: cs:StandAlone ro:Secondary/Unknown ds:Inconsistent/DUnknown   r----s
    ns:0 nr:0 dw:0 dr:0 al:0 bm:0 lo:0 pe:0 ua:0 ap:0 ep:1 wo:b def:0 chkpt=
:0 oos:10485404


Do you have some =
hints?


Thank you,

=
Agya

thanks
shriram

On Mon, Feb 18, 2013 at 5:38 AM, Hery Dian Septama <herydians@gmail.com> wrote:
> Hello, Anyone have a clue? I have tried but still failed :(
>
> On Sat, Feb 16, 2013 at 6:56 PM, agya naila <agya.naila@gmail.com> wrote:
>>
>> Dear all,
>>
>> I am configure my machine to run the remus disk replication. I am = using
>> xen 4.2.3 installed from sources and Ubuntu 12.04 64 bit both for = Dom0 and
>> DomU.
>> I have install the blktap and its work properly with configuration= string
>> phy or tap2 like this :
>> disk =3D ['phy:/dev/vggroup/DomU,xvda,w']
>> or
>> disk =3D ['tap2:tapdisk:aio:/dev/vggroup/DomU,xvda,w']
>>
>> and remus command
>>
>> remus --no-net myvm mybackuphost
>>
>>
>> However when I change the string as suggested on remus pages to en= able the
>> disk replication its still failed :
>>
>> name =3D "DomU"
>> memory =3D 1024
>> disk =3D ['tap2:remus:10.10.10.3:8002|aio:/dev/vggroup/DomU,xv= da,w']
>> vif =3D ['ip=3D192.168.1.55,bridge=3Dxenbr0']
>> bootloader =3D "pygrub"
>>
>> with error messages :
>>
>> name1@machine1:~$ sudo xm create -c /etc/xen/DomU.cfg
>> Using config file "/etc/xen/DomU.cfg".
>> Error: ('create', '-aremus:10.10.10.3:8002|aio:/dev/vg= group/DomU') failed
>> (512 =A0)
>>
>> and on the log file :
>>
>>
>> name1@machine1:~$ sudo sudo tail /var/log/xen/xend.log
>> =A0 =A0 mounted_vbd_uuid =3D dom0.create_vbd(vbd, disk);
>> =A0 File
>> "/usr/local/lib/python2.7/dist-packages/xen/xend/XendDomainIn= fo.py", line
>> 3987, in create_vbd
>> =A0 =A0 devid =3D dev_control.createDevice(config)
>> =A0 File
>> "/usr/local/lib/python2.7/dist-packages/xen/xend/server/Blkta= pController.py",
>> line 174, in createDevice
>> =A0 =A0 device =3D TapdiskController.create(params, file)
>> =A0 File
>> "/usr/local/lib/python2.7/dist-packages/xen/xend/server/Blkta= pController.py",
>> line 286, in create
>> =A0 =A0 return TapdiskController.exc('create', '-a%s:%= s' % (dtype, image))
>> =A0 File
>> "/usr/local/lib/python2.7/dist-packages/xen/xend/server/Blkta= pController.py",
>> line 233, in exc
>> =A0 =A0 (args, rc, out, err))
>> TapdiskException: ('create',
>> '-aremus:10.10.10.3:8002|aio:/dev/vggroup/DomU') failed (5= 12 =A0)
>>
>> Any hints and help would very appreciated.
>>
>> Regards,
>>
>> Agya
>>
>>
>> _______________________________________________
>> Xen-devel mailing list
>> Xen-devel@lists.xen.org=
>> http:= //lists.xen.org/xen-devel
>>
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org=
> http://li= sts.xen.org/xen-devel
>

--f46d0444e7d7313d5804d6062a44-- --===============3731334846460705237== 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 --===============3731334846460705237==-- From xen-users-bounces@lists.xen.org Mon Feb 18 21:33:01 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 18 Feb 2013 21:33: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 1U7YJq-0003T7-6s; Mon, 18 Feb 2013 21:32:14 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U7YJo-0003T2-2F for xen-users@lists.xen.org; Mon, 18 Feb 2013 21:32:12 +0000 Received: from [85.158.139.83:40782] by server-16.bemta-5.messagelabs.com id B6/ED-14948-BDD92215; Mon, 18 Feb 2013 21:32:11 +0000 X-Env-Sender: eross@corp.locatrix.com X-Msg-Ref: server-6.tower-182.messagelabs.com!1361223129!23953358!1 X-Originating-IP: [209.85.210.174] X-SpamReason: No, hits=1.1 required=7.0 tests=BODY_RANDOM_LONG, HTML_60_70,HTML_MESSAGE,RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 25639 invoked from network); 18 Feb 2013 21:32:10 -0000 Received: from mail-ia0-f174.google.com (HELO mail-ia0-f174.google.com) (209.85.210.174) by server-6.tower-182.messagelabs.com with RC4-SHA encrypted SMTP; 18 Feb 2013 21:32:10 -0000 Received: by mail-ia0-f174.google.com with SMTP id u20so1330572iag.5 for ; Mon, 18 Feb 2013 13:32:08 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=x-received:mime-version:in-reply-to:references:from:date:message-id :subject:to:content-type:x-gm-message-state; bh=AtMj6rbO/qEhK0eiVPSc2hcu7YQUAJjw+dDbY6LyvUo=; b=FrUwkFdjxtwwWmoFlbxa1z6OPA/BLAsEpZuBOX9YfqVxjV44gsENxXQAgR/WLFvW0W 8z1LMOwRxwMxpPrEi0XkythXguvlBI3PfdJBno+B6WWpU8dmmkLgPKrRfRW/ab2e0Uoc 84SZRTS4slrO+7lkImTv5biNDxxSN0etB8ssT7pFCh3iXsTI4Tc5qv3I+RWsu6eHUngC ubz46b2AQSoMfzzr8reVzvKO+AI0MGLi7xUcTFp3TYwr7aYQSJXMr5EChLdjj8QPW5FZ S9clbvza7wyoXGIzMxDIY+/zkboG5SHXO9gd7jdPdseCBcoEOqtvOtwCWZEecWcuY4u7 1q+g== X-Received: by 10.50.150.228 with SMTP id ul4mr7495539igb.9.1361223128767; Mon, 18 Feb 2013 13:32:08 -0800 (PST) MIME-Version: 1.0 Received: by 10.64.44.197 with HTTP; Mon, 18 Feb 2013 13:31:48 -0800 (PST) In-Reply-To: References: From: Andrew Eross Date: Mon, 18 Feb 2013 18:31:48 -0300 Message-ID: To: rshriram@cs.ubc.ca, xen-users@lists.xen.org X-Gm-Message-State: ALoCoQnmGdNm3gfGNqGpRCY6CkFE7pC+11ENi/YIZN4Uz20eH7CY3lv701vzX8Sjeoe+O1K5AOvQ Subject: Re: [Xen-users] Remus Suspend event channel kernel support X-BeenThere: xen-users@lists.xen.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="===============1356580144704099033==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============1356580144704099033== Content-Type: multipart/alternative; boundary=f46d043c7b600cde0f04d60675d6 --f46d043c7b600cde0f04d60675d6 Content-Type: text/plain; charset=ISO-8859-1 And sorry I messed up your name, Shriram =) On Mon, Feb 18, 2013 at 6:31 PM, Andrew Eross wrote: > Hi Shiriam, > > I've noticed there's a fair amount of mention of the need for "suspend > event channel" support in the domU kernel when using Remus, and there's > some mention of certain kernels that support it (e.g. > http://xenbits.xen.org/hg/linux-2.6.18-xen.hg/) > > However, I'm running Ubuntu 12.04+ these days, and I don't think I'd want > to install that kernel in favor of the linux 3.5 kernel it comes with (?). > > I was trying to see if there's a way to be able to compile a custom kernel > with the required support? > > I just couldn't figure out exactly what having "suspend event channel > support" means (e.g. is it a driver, a config option, a code change), and > was hoping you might be able to help? > > Thanks! > Andrew > --f46d043c7b600cde0f04d60675d6 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable And sorry I messed up your name,=A0Shriram =3D)

On Mon, Feb 18, 2013 at 6:31 PM, Andrew Eross <eross@= locatrix.com> wrote:
= Hi Shiriam,

I've noticed there'= ;s a fair amount of mention of the need for "suspend event channel&quo= t; support in the domU kernel when using Remus, and there's some mentio= n of certain kernels that support it (e.g.=A0http://xenbits.xen.org/hg/li= nux-2.6.18-xen.hg/)

However, I'm running Ubuntu 12.= 04+ these days, and I don't think I'd want to install that kernel i= n favor of the linux 3.5 kernel it comes with (?).

I was trying to see if there's = a way to be able to compile a custom kernel with the required support?

I just couldn't figure out exac= tly what having=A0"su= spend event channel support" means (e.g. is it a driver, a config opti= on, a code change), and was hoping you might be able to help?

Thanks!
Andrew

--f46d043c7b600cde0f04d60675d6-- --===============1356580144704099033== 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 --===============1356580144704099033==-- From xen-users-bounces@lists.xen.org Mon Feb 18 21:33:01 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 18 Feb 2013 21:33: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 1U7YJq-0003T7-6s; Mon, 18 Feb 2013 21:32:14 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U7YJo-0003T2-2F for xen-users@lists.xen.org; Mon, 18 Feb 2013 21:32:12 +0000 Received: from [85.158.139.83:40782] by server-16.bemta-5.messagelabs.com id B6/ED-14948-BDD92215; Mon, 18 Feb 2013 21:32:11 +0000 X-Env-Sender: eross@corp.locatrix.com X-Msg-Ref: server-6.tower-182.messagelabs.com!1361223129!23953358!1 X-Originating-IP: [209.85.210.174] X-SpamReason: No, hits=1.1 required=7.0 tests=BODY_RANDOM_LONG, HTML_60_70,HTML_MESSAGE,RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 25639 invoked from network); 18 Feb 2013 21:32:10 -0000 Received: from mail-ia0-f174.google.com (HELO mail-ia0-f174.google.com) (209.85.210.174) by server-6.tower-182.messagelabs.com with RC4-SHA encrypted SMTP; 18 Feb 2013 21:32:10 -0000 Received: by mail-ia0-f174.google.com with SMTP id u20so1330572iag.5 for ; Mon, 18 Feb 2013 13:32:08 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=x-received:mime-version:in-reply-to:references:from:date:message-id :subject:to:content-type:x-gm-message-state; bh=AtMj6rbO/qEhK0eiVPSc2hcu7YQUAJjw+dDbY6LyvUo=; b=FrUwkFdjxtwwWmoFlbxa1z6OPA/BLAsEpZuBOX9YfqVxjV44gsENxXQAgR/WLFvW0W 8z1LMOwRxwMxpPrEi0XkythXguvlBI3PfdJBno+B6WWpU8dmmkLgPKrRfRW/ab2e0Uoc 84SZRTS4slrO+7lkImTv5biNDxxSN0etB8ssT7pFCh3iXsTI4Tc5qv3I+RWsu6eHUngC ubz46b2AQSoMfzzr8reVzvKO+AI0MGLi7xUcTFp3TYwr7aYQSJXMr5EChLdjj8QPW5FZ S9clbvza7wyoXGIzMxDIY+/zkboG5SHXO9gd7jdPdseCBcoEOqtvOtwCWZEecWcuY4u7 1q+g== X-Received: by 10.50.150.228 with SMTP id ul4mr7495539igb.9.1361223128767; Mon, 18 Feb 2013 13:32:08 -0800 (PST) MIME-Version: 1.0 Received: by 10.64.44.197 with HTTP; Mon, 18 Feb 2013 13:31:48 -0800 (PST) In-Reply-To: References: From: Andrew Eross Date: Mon, 18 Feb 2013 18:31:48 -0300 Message-ID: To: rshriram@cs.ubc.ca, xen-users@lists.xen.org X-Gm-Message-State: ALoCoQnmGdNm3gfGNqGpRCY6CkFE7pC+11ENi/YIZN4Uz20eH7CY3lv701vzX8Sjeoe+O1K5AOvQ Subject: Re: [Xen-users] Remus Suspend event channel kernel support X-BeenThere: xen-users@lists.xen.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="===============1356580144704099033==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============1356580144704099033== Content-Type: multipart/alternative; boundary=f46d043c7b600cde0f04d60675d6 --f46d043c7b600cde0f04d60675d6 Content-Type: text/plain; charset=ISO-8859-1 And sorry I messed up your name, Shriram =) On Mon, Feb 18, 2013 at 6:31 PM, Andrew Eross wrote: > Hi Shiriam, > > I've noticed there's a fair amount of mention of the need for "suspend > event channel" support in the domU kernel when using Remus, and there's > some mention of certain kernels that support it (e.g. > http://xenbits.xen.org/hg/linux-2.6.18-xen.hg/) > > However, I'm running Ubuntu 12.04+ these days, and I don't think I'd want > to install that kernel in favor of the linux 3.5 kernel it comes with (?). > > I was trying to see if there's a way to be able to compile a custom kernel > with the required support? > > I just couldn't figure out exactly what having "suspend event channel > support" means (e.g. is it a driver, a config option, a code change), and > was hoping you might be able to help? > > Thanks! > Andrew > --f46d043c7b600cde0f04d60675d6 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable And sorry I messed up your name,=A0Shriram =3D)

On Mon, Feb 18, 2013 at 6:31 PM, Andrew Eross <eross@= locatrix.com> wrote:
= Hi Shiriam,

I've noticed there'= ;s a fair amount of mention of the need for "suspend event channel&quo= t; support in the domU kernel when using Remus, and there's some mentio= n of certain kernels that support it (e.g.=A0http://xenbits.xen.org/hg/li= nux-2.6.18-xen.hg/)

However, I'm running Ubuntu 12.= 04+ these days, and I don't think I'd want to install that kernel i= n favor of the linux 3.5 kernel it comes with (?).

I was trying to see if there's = a way to be able to compile a custom kernel with the required support?

I just couldn't figure out exac= tly what having=A0"su= spend event channel support" means (e.g. is it a driver, a config opti= on, a code change), and was hoping you might be able to help?

Thanks!
Andrew

--f46d043c7b600cde0f04d60675d6-- --===============1356580144704099033== 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 --===============1356580144704099033==-- From xen-users-bounces@lists.xen.org Mon Feb 18 21:33:03 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 18 Feb 2013 21: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 1U7YJW-0003SO-Hg; Mon, 18 Feb 2013 21:31:54 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U7YJV-0003SJ-BM for xen-users@lists.xen.org; Mon, 18 Feb 2013 21:31:53 +0000 Received: from [85.158.139.211:36919] by server-11.bemta-5.messagelabs.com id 88/D8-19159-8CD92215; Mon, 18 Feb 2013 21:31:52 +0000 X-Env-Sender: eross@corp.locatrix.com X-Msg-Ref: server-13.tower-206.messagelabs.com!1361223110!14133013!1 X-Originating-IP: [209.85.223.176] X-SpamReason: No, hits=0.9 required=7.0 tests=BODY_RANDOM_LONG, HTML_50_60,HTML_MESSAGE,RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 12437 invoked from network); 18 Feb 2013 21:31:51 -0000 Received: from mail-ie0-f176.google.com (HELO mail-ie0-f176.google.com) (209.85.223.176) by server-13.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 18 Feb 2013 21:31:51 -0000 Received: by mail-ie0-f176.google.com with SMTP id k13so7676263iea.21 for ; Mon, 18 Feb 2013 13:31:31 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=x-received:mime-version:from:date:message-id:subject:to :content-type:x-gm-message-state; bh=goGfGcwvzak2uTvqjntDuvAwu+J1o4j7asvrQ1WVHdg=; b=DESOuv+/nGxmGKN3yalHz3vtv0G5QXkFO5UxxypLIcBULPWhv5t9Ms/fYYigEIVwUd 5XuvQQcJ1eDU77eENPyX8hjvoW7gI4WCAj2rtzDh/A0qLr/OVSwx3IT3GYzlXCsvSNrd LYQvEUX2DhJgtb4IVpVj9yMBar722Te5p7q6TdbvrIGoxzoZOzntfwjL/aOjECD3DRXM 2hbWyrw7/suahNcJ+qwafp408FqF4biduLD5qCnjmiU/oziEBH8Rlin1ac5pwLoL9Czn reawuXBzSP8ytIseX6kkcMEySjVRlqXvB7kzOKnL1/Wggy/kIw1h7GG2GOh8dqLqLFvu HhLA== X-Received: by 10.43.62.12 with SMTP id wy12mr6502948icb.19.1361223091216; Mon, 18 Feb 2013 13:31:31 -0800 (PST) MIME-Version: 1.0 Received: by 10.64.44.197 with HTTP; Mon, 18 Feb 2013 13:31:10 -0800 (PST) From: Andrew Eross Date: Mon, 18 Feb 2013 18:31:10 -0300 Message-ID: To: rshriram@cs.ubc.ca, xen-users@lists.xen.org X-Gm-Message-State: ALoCoQniAZ2OHY7BHZoXWJQjwhNMPw1w+77S7mG4xDvPH6jJy+2R+C2maeJqsSQVC9z9Vn2s9fx4 Subject: [Xen-users] Remus Suspend event channel kernel support X-BeenThere: xen-users@lists.xen.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="===============4221535600791552867==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============4221535600791552867== Content-Type: multipart/alternative; boundary=bcaec51d2980cfe08504d6067261 --bcaec51d2980cfe08504d6067261 Content-Type: text/plain; charset=ISO-8859-1 Hi Shiriam, I've noticed there's a fair amount of mention of the need for "suspend event channel" support in the domU kernel when using Remus, and there's some mention of certain kernels that support it (e.g. http://xenbits.xen.org/hg/linux-2.6.18-xen.hg/) However, I'm running Ubuntu 12.04+ these days, and I don't think I'd want to install that kernel in favor of the linux 3.5 kernel it comes with (?). I was trying to see if there's a way to be able to compile a custom kernel with the required support? I just couldn't figure out exactly what having "suspend event channel support" means (e.g. is it a driver, a config option, a code change), and was hoping you might be able to help? Thanks! Andrew --bcaec51d2980cfe08504d6067261 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Hi Shiriam,

I've noticed there's a fair amount of me= ntion of the need for "suspend event channel" support in the domU= kernel when using Remus, and there's some mention of certain kernels t= hat support it (e.g.=A0http://xenbits.xen.org/hg/linux-2.6.18-xen.hg/)

However, I'm running Ubuntu 12.= 04+ these days, and I don't think I'd want to install that kernel i= n favor of the linux 3.5 kernel it comes with (?).

I was trying to see if there's = a way to be able to compile a custom kernel with the required support?

I just couldn't figure out exac= tly what having=A0"su= spend event channel support" means (e.g. is it a driver, a config opti= on, a code change), and was hoping you might be able to help?

Thanks!
Andrew
--bcaec51d2980cfe08504d6067261-- --===============4221535600791552867== 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 --===============4221535600791552867==-- From xen-users-bounces@lists.xen.org Mon Feb 18 21:33:03 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 18 Feb 2013 21: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 1U7YJW-0003SO-Hg; Mon, 18 Feb 2013 21:31:54 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U7YJV-0003SJ-BM for xen-users@lists.xen.org; Mon, 18 Feb 2013 21:31:53 +0000 Received: from [85.158.139.211:36919] by server-11.bemta-5.messagelabs.com id 88/D8-19159-8CD92215; Mon, 18 Feb 2013 21:31:52 +0000 X-Env-Sender: eross@corp.locatrix.com X-Msg-Ref: server-13.tower-206.messagelabs.com!1361223110!14133013!1 X-Originating-IP: [209.85.223.176] X-SpamReason: No, hits=0.9 required=7.0 tests=BODY_RANDOM_LONG, HTML_50_60,HTML_MESSAGE,RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 12437 invoked from network); 18 Feb 2013 21:31:51 -0000 Received: from mail-ie0-f176.google.com (HELO mail-ie0-f176.google.com) (209.85.223.176) by server-13.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 18 Feb 2013 21:31:51 -0000 Received: by mail-ie0-f176.google.com with SMTP id k13so7676263iea.21 for ; Mon, 18 Feb 2013 13:31:31 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=x-received:mime-version:from:date:message-id:subject:to :content-type:x-gm-message-state; bh=goGfGcwvzak2uTvqjntDuvAwu+J1o4j7asvrQ1WVHdg=; b=DESOuv+/nGxmGKN3yalHz3vtv0G5QXkFO5UxxypLIcBULPWhv5t9Ms/fYYigEIVwUd 5XuvQQcJ1eDU77eENPyX8hjvoW7gI4WCAj2rtzDh/A0qLr/OVSwx3IT3GYzlXCsvSNrd LYQvEUX2DhJgtb4IVpVj9yMBar722Te5p7q6TdbvrIGoxzoZOzntfwjL/aOjECD3DRXM 2hbWyrw7/suahNcJ+qwafp408FqF4biduLD5qCnjmiU/oziEBH8Rlin1ac5pwLoL9Czn reawuXBzSP8ytIseX6kkcMEySjVRlqXvB7kzOKnL1/Wggy/kIw1h7GG2GOh8dqLqLFvu HhLA== X-Received: by 10.43.62.12 with SMTP id wy12mr6502948icb.19.1361223091216; Mon, 18 Feb 2013 13:31:31 -0800 (PST) MIME-Version: 1.0 Received: by 10.64.44.197 with HTTP; Mon, 18 Feb 2013 13:31:10 -0800 (PST) From: Andrew Eross Date: Mon, 18 Feb 2013 18:31:10 -0300 Message-ID: To: rshriram@cs.ubc.ca, xen-users@lists.xen.org X-Gm-Message-State: ALoCoQniAZ2OHY7BHZoXWJQjwhNMPw1w+77S7mG4xDvPH6jJy+2R+C2maeJqsSQVC9z9Vn2s9fx4 Subject: [Xen-users] Remus Suspend event channel kernel support X-BeenThere: xen-users@lists.xen.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="===============4221535600791552867==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============4221535600791552867== Content-Type: multipart/alternative; boundary=bcaec51d2980cfe08504d6067261 --bcaec51d2980cfe08504d6067261 Content-Type: text/plain; charset=ISO-8859-1 Hi Shiriam, I've noticed there's a fair amount of mention of the need for "suspend event channel" support in the domU kernel when using Remus, and there's some mention of certain kernels that support it (e.g. http://xenbits.xen.org/hg/linux-2.6.18-xen.hg/) However, I'm running Ubuntu 12.04+ these days, and I don't think I'd want to install that kernel in favor of the linux 3.5 kernel it comes with (?). I was trying to see if there's a way to be able to compile a custom kernel with the required support? I just couldn't figure out exactly what having "suspend event channel support" means (e.g. is it a driver, a config option, a code change), and was hoping you might be able to help? Thanks! Andrew --bcaec51d2980cfe08504d6067261 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Hi Shiriam,

I've noticed there's a fair amount of me= ntion of the need for "suspend event channel" support in the domU= kernel when using Remus, and there's some mention of certain kernels t= hat support it (e.g.=A0http://xenbits.xen.org/hg/linux-2.6.18-xen.hg/)

However, I'm running Ubuntu 12.= 04+ these days, and I don't think I'd want to install that kernel i= n favor of the linux 3.5 kernel it comes with (?).

I was trying to see if there's = a way to be able to compile a custom kernel with the required support?

I just couldn't figure out exac= tly what having=A0"su= spend event channel support" means (e.g. is it a driver, a config opti= on, a code change), and was hoping you might be able to help?

Thanks!
Andrew
--bcaec51d2980cfe08504d6067261-- --===============4221535600791552867== 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 --===============4221535600791552867==-- From xen-users-bounces@lists.xen.org Mon Feb 18 21:34:43 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 18 Feb 2013 21:34: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 1U7YLU-0003fw-PW; Mon, 18 Feb 2013 21:33:56 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U7YLT-0003fp-VH for xen-users@lists.xen.org; Mon, 18 Feb 2013 21:33:56 +0000 Received: from [85.158.139.83:46371] by server-16.bemta-5.messagelabs.com id 2F/1F-14948-34E92215; Mon, 18 Feb 2013 21:33:55 +0000 X-Env-Sender: murrayie@yahoo.co.uk X-Msg-Ref: server-12.tower-182.messagelabs.com!1361223234!27834571!1 X-Originating-IP: [77.238.189.39] X-SpamReason: No, hits=0.0 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, spamassassin: X-StarScan-Received: X-StarScan-Version: 6.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 27519 invoked from network); 18 Feb 2013 21:33:54 -0000 Received: from nm10.bullet.mail.ird.yahoo.com (HELO nm10.bullet.mail.ird.yahoo.com) (77.238.189.39) by server-12.tower-182.messagelabs.com with SMTP; 18 Feb 2013 21:33:54 -0000 Received: from [77.238.189.234] by nm10.bullet.mail.ird.yahoo.com with NNFMP; 18 Feb 2013 21:33:54 -0000 Received: from [46.228.39.123] by tm15.bullet.mail.ird.yahoo.com with NNFMP; 18 Feb 2013 21:33:54 -0000 Received: from [127.0.0.1] by smtp160.mail.ir2.yahoo.com with NNFMP; 18 Feb 2013 21:33:54 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.co.uk; s=s1024; t=1361223234; bh=C/cY9jfFlT05pFVagFPBwWos7ltgxaLrDn/dz1Y4iFo=; 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:References:In-Reply-To:Content-Type:Content-Transfer-Encoding; b=hmfv+xLUV3/z6Gg4chd4wM+LMxI0QqiRc+o+ygjB6ozjM0qcp2cGFY+Ia5L1yte42txMIsOZaYJpDjW8bIqtJ9F1duwuc/MkoPc4nP8/wWLwKZd6ud4ZScmzAo3HTvsnRuyTT/8xBKGL6G+jPTrdE1P/D2NP/mhYmhrfNP5s7ak= X-Yahoo-Newman-Id: 285224.22107.bm@smtp160.mail.ir2.yahoo.com X-Yahoo-Newman-Property: ymail-3 X-YMail-OSG: BMJ1.ucVM1lB0BbiC3zvwMrwe8UNdlaXqF2G71PNNEmETqj tEJtlD1t.lMGP3PDARoFkyi.VCxn0E4LwRQaNyl9meawjIhMcH2bjxy_B.VB jejJGaKm90_FtSF6va9NxLneTUoY0zgUsqfvYhr6rgiPq3WeFkvsv1DCvlZU lDjiJaB_RspkNm5KoMKkSybdDyPFAQWnSEn.zGN5tOf6tqN6yLNdhD3x9_3f isUK0FRJ8BOPjx_nQNWqqWUXHMByqoOUpZBPmJm90qNk8GnJn9RVfkby5J5G gVFE7gl9a68Jir6SKnXxdTQgF9KLF9ssNeod4ceb5wf_D6FDTP0m0KU67.6I SrWKnbsVMhmz2h3wFM17Rnp11GjKpCnBfYEq4tSfDLGPWB79scnXBn_g65mT L8FZ1AB5VbVkpcK0DhuXUKG4m_95ee7nPuZ6UaRHzT_b5M4LhOzCBHIlL0ZB F.c0WlyXZdm04wEQtscjyFqtjVgjd0z3XM7adDaXG94E37AB8ZbhxElzuj8P C5S0LV1OSAC0k1YcARRlo929F6CV6yQGgLYmjxEJiPC4t._iJUCYdDlIt X-Yahoo-SMTP: P.LfrmaswBDlKN6tCvtOaEZlSVsY Received: from [192.168.1.136] (murrayie@109.157.15.99 with plain) by smtp160.mail.ir2.yahoo.com with SMTP; 18 Feb 2013 21:33:54 +0000 UTC Message-ID: <51229E41.2090103@yahoo.co.uk> Date: Mon, 18 Feb 2013 21:33:53 +0000 From: Ian User-Agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/20130106 Thunderbird/17.0.2 MIME-Version: 1.0 To: xen-users@lists.xen.org References: In-Reply-To: Subject: Re: [Xen-users] Xen 4.2.1 unable to get domain type for domid X-BeenThere: xen-users@lists.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 18/02/13 20:17, Andrew Eross wrote: > Hi guys, > > I eventually gave up and went back to Xen 4.1.4, which works perfectly > fine using the exact same install method and Ubuntu domU > configuration, but just with xm. > > I wrote up how I did the Xen 4.2.1 install here for reference - > http://locatrix.com/building-and-installing-xen-4-2-1-from-source-on-ubuntu-12-10/ > > And the Xen 4.1.4 install here - > http://locatrix.com/building-and-install-xen-4-1-4-from-source-on-ubuntu-12-10/ > > I hope maybe some others could give it a try and see if they also are > unable to install Ubuntu domUs with xl on 4.2.1 like I'd been trying to. > > Cheers, > Andrew > I have 12.04 DomU's running under 12.04 Dom0 on self compiled 4.2.1, using xl toolstack The only issue I have had is that 12.04 DomU ends up with a non-PAE kernel, which needs to be fixed after the install. 12.10 DomU's don't appear to suffer this. No idea what the difference is between our set-ups, although I just use LVMs and always specify a MAC address. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Mon Feb 18 21:34:43 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 18 Feb 2013 21:34: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 1U7YLU-0003fw-PW; Mon, 18 Feb 2013 21:33:56 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U7YLT-0003fp-VH for xen-users@lists.xen.org; Mon, 18 Feb 2013 21:33:56 +0000 Received: from [85.158.139.83:46371] by server-16.bemta-5.messagelabs.com id 2F/1F-14948-34E92215; Mon, 18 Feb 2013 21:33:55 +0000 X-Env-Sender: murrayie@yahoo.co.uk X-Msg-Ref: server-12.tower-182.messagelabs.com!1361223234!27834571!1 X-Originating-IP: [77.238.189.39] X-SpamReason: No, hits=0.0 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, spamassassin: X-StarScan-Received: X-StarScan-Version: 6.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 27519 invoked from network); 18 Feb 2013 21:33:54 -0000 Received: from nm10.bullet.mail.ird.yahoo.com (HELO nm10.bullet.mail.ird.yahoo.com) (77.238.189.39) by server-12.tower-182.messagelabs.com with SMTP; 18 Feb 2013 21:33:54 -0000 Received: from [77.238.189.234] by nm10.bullet.mail.ird.yahoo.com with NNFMP; 18 Feb 2013 21:33:54 -0000 Received: from [46.228.39.123] by tm15.bullet.mail.ird.yahoo.com with NNFMP; 18 Feb 2013 21:33:54 -0000 Received: from [127.0.0.1] by smtp160.mail.ir2.yahoo.com with NNFMP; 18 Feb 2013 21:33:54 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.co.uk; s=s1024; t=1361223234; bh=C/cY9jfFlT05pFVagFPBwWos7ltgxaLrDn/dz1Y4iFo=; 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:References:In-Reply-To:Content-Type:Content-Transfer-Encoding; b=hmfv+xLUV3/z6Gg4chd4wM+LMxI0QqiRc+o+ygjB6ozjM0qcp2cGFY+Ia5L1yte42txMIsOZaYJpDjW8bIqtJ9F1duwuc/MkoPc4nP8/wWLwKZd6ud4ZScmzAo3HTvsnRuyTT/8xBKGL6G+jPTrdE1P/D2NP/mhYmhrfNP5s7ak= X-Yahoo-Newman-Id: 285224.22107.bm@smtp160.mail.ir2.yahoo.com X-Yahoo-Newman-Property: ymail-3 X-YMail-OSG: BMJ1.ucVM1lB0BbiC3zvwMrwe8UNdlaXqF2G71PNNEmETqj tEJtlD1t.lMGP3PDARoFkyi.VCxn0E4LwRQaNyl9meawjIhMcH2bjxy_B.VB jejJGaKm90_FtSF6va9NxLneTUoY0zgUsqfvYhr6rgiPq3WeFkvsv1DCvlZU lDjiJaB_RspkNm5KoMKkSybdDyPFAQWnSEn.zGN5tOf6tqN6yLNdhD3x9_3f isUK0FRJ8BOPjx_nQNWqqWUXHMByqoOUpZBPmJm90qNk8GnJn9RVfkby5J5G gVFE7gl9a68Jir6SKnXxdTQgF9KLF9ssNeod4ceb5wf_D6FDTP0m0KU67.6I SrWKnbsVMhmz2h3wFM17Rnp11GjKpCnBfYEq4tSfDLGPWB79scnXBn_g65mT L8FZ1AB5VbVkpcK0DhuXUKG4m_95ee7nPuZ6UaRHzT_b5M4LhOzCBHIlL0ZB F.c0WlyXZdm04wEQtscjyFqtjVgjd0z3XM7adDaXG94E37AB8ZbhxElzuj8P C5S0LV1OSAC0k1YcARRlo929F6CV6yQGgLYmjxEJiPC4t._iJUCYdDlIt X-Yahoo-SMTP: P.LfrmaswBDlKN6tCvtOaEZlSVsY Received: from [192.168.1.136] (murrayie@109.157.15.99 with plain) by smtp160.mail.ir2.yahoo.com with SMTP; 18 Feb 2013 21:33:54 +0000 UTC Message-ID: <51229E41.2090103@yahoo.co.uk> Date: Mon, 18 Feb 2013 21:33:53 +0000 From: Ian User-Agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/20130106 Thunderbird/17.0.2 MIME-Version: 1.0 To: xen-users@lists.xen.org References: In-Reply-To: Subject: Re: [Xen-users] Xen 4.2.1 unable to get domain type for domid X-BeenThere: xen-users@lists.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 18/02/13 20:17, Andrew Eross wrote: > Hi guys, > > I eventually gave up and went back to Xen 4.1.4, which works perfectly > fine using the exact same install method and Ubuntu domU > configuration, but just with xm. > > I wrote up how I did the Xen 4.2.1 install here for reference - > http://locatrix.com/building-and-installing-xen-4-2-1-from-source-on-ubuntu-12-10/ > > And the Xen 4.1.4 install here - > http://locatrix.com/building-and-install-xen-4-1-4-from-source-on-ubuntu-12-10/ > > I hope maybe some others could give it a try and see if they also are > unable to install Ubuntu domUs with xl on 4.2.1 like I'd been trying to. > > Cheers, > Andrew > I have 12.04 DomU's running under 12.04 Dom0 on self compiled 4.2.1, using xl toolstack The only issue I have had is that 12.04 DomU ends up with a non-PAE kernel, which needs to be fixed after the install. 12.10 DomU's don't appear to suffer this. No idea what the difference is between our set-ups, although I just use LVMs and always specify a MAC address. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Mon Feb 18 21:35:45 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 18 Feb 2013 21:35: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 1U7YMc-0003ry-Sy; Mon, 18 Feb 2013 21:35:06 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U7YMa-0003rS-UI; Mon, 18 Feb 2013 21:35:05 +0000 Received: from [85.158.143.35:40027] by server-1.bemta-4.messagelabs.com id F5/F4-08839-88E92215; Mon, 18 Feb 2013 21:35:04 +0000 X-Env-Sender: rshriram@cs.ubc.ca X-Msg-Ref: server-16.tower-21.messagelabs.com!1361223295!13181757!1 X-Originating-IP: [142.103.6.52] X-SpamReason: No, hits=0.3 required=7.0 tests=RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 8532 invoked from network); 18 Feb 2013 21:35:02 -0000 Received: from unknown (HELO smtp.cs.ubc.ca) (142.103.6.52) by server-16.tower-21.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 18 Feb 2013 21:35:02 -0000 Received: from mail-ie0-f181.google.com (mail-ie0-f181.google.com [209.85.223.181]) (authenticated bits=0) by smtp.cs.ubc.ca (8.14.3/8.13.6) with ESMTP id r1ILXqXZ016075 (version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=FAIL); Mon, 18 Feb 2013 13:33:52 -0800 Received: by mail-ie0-f181.google.com with SMTP id 17so7774948iea.12 for ; Mon, 18 Feb 2013 13:33:51 -0800 (PST) X-Received: by 10.50.214.67 with SMTP id ny3mr8068679igc.13.1361223231144; Mon, 18 Feb 2013 13:33:51 -0800 (PST) MIME-Version: 1.0 Received: by 10.43.2.67 with HTTP; Mon, 18 Feb 2013 13:33:11 -0800 (PST) In-Reply-To: References: From: Shriram Rajagopalan Date: Mon, 18 Feb 2013 16:33:11 -0500 Message-ID: To: agya naila Cc: "xen-users@lists.xen.org" , "xen-devel@lists.xen.org" Subject: Re: [Xen-users] [Xen-devel] Remus disk replication failed X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: rshriram@cs.ubc.ca List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: 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 suggest you read up on the DRBD setup documentation from the drbd.org website. The setup procedure is same. You can later flip to the remus replication protocol by simply changing the protocol type (C to D). thanks shriram On Mon, Feb 18, 2013 at 4:11 PM, agya naila wrote: > > On Mon, Feb 18, 2013 at 9:08 PM, Shriram Rajagopalan > wrote: >> >> hi > > > Thank you shriram. > >> >> sorry for the delayed response. IIRC the blktap2 driver required for >> tapdisk replication doesnt exist in the mainstream dom0 kernels, IIRC. >> I havent used it in a long time myself. I suggest trying disk >> replication with DRBD. >> > > I am also found some information here > http://osdir.com/ml/xen-users/2011-07/msg00653.html about blktap2 problem on > amd64 architecture. I have tried to install and configure the DRBD but its > didn't connect each other. > I used drbd-8.3.11-remus and installed as follow > > cd /usr/src/ > wget > http://remusha.wikidot.com/local--files/configuring-and-installing-remus/drbd-8.3.11-remus.tar.gz > tar xzf drbd-8.3.9-remus.tar.gz > chown -R root:root drbd-8.3-remus > cd /usr/src/drbd-8.3-remus > chmod 777 autogen.sh > ./autogen.sh > dpkg-buildpackage -b -uc > cd /usr/src/drbd-8.3-remus/drbd > make clean > make > make install > cd /usr/src/ > cp /usr/src/drbd-8.3-remus/scripts/global_common.conf.protoD > /etc/drbd.d/global_common.conf > cp /usr/src/drbd-8.3-remus/scripts/testvms_protoD.res > /etc/drbd.d/SystemHA_protoD.res > > sudo apt-get install drbd8-utils > > from tutorial http://remusha.wikidot.com/configuring-and-installing-remus > > My *.res configuration as follow : > > resource drbd-vm{ > device /dev/drbd1; > disk /dev/vgvoip/DomU; > meta-disk internal; > on machine1 { > address 10.10.10.1:7789; > } > on machine2 { > address 10.10.10.3:7789; > } > } > > and then I invoke command to create that meta > > drbdadm create-md drbd-vm > > However, when I try to make this configuration up by : > > drbdadm up drbd-vm > > Its come with error : > > $ sudo drbdadm up drbd-vm > 1: Failure: (124) Device is attached to a disk (use detach first) > Command 'drbdsetup 1 disk /dev/vgvoip/DomU /dev/vgvoip/DomU internal > --set-defaults --create-device --fencing=dont-care --on-io-error=pass_on' > terminated with exit code 10 > > If I run the > > $ sudo drbdadm detach drbd-vm > > Its come error > > $ sudo drbdadm detach drbd-vm > 1: State change failed: (-2) Need access to UpToDate data > Command 'drbdsetup 1 detach' terminated with exit code 17 > > Here the /proc/drbd on both machine > > Machine 1 > > $ sudo cat /proc/drbd > version: 8.3.11 (api:88/proto:86-96) > GIT-hash: 0de839cee13a4160eed6037c4bddd066645e23c5 build by root@machine1, > 2013-02-18 18:49:57 > > 1: cs:StandAlone ro:Primary/Unknown ds:UpToDate/DUnknown r----s > ns:0 nr:0 dw:0 dr:1712 al:0 bm:0 lo:0 pe:0 ua:0 ap:0 ep:1 wo:b def:0 > chkpt:0 oos:10485404 > > > Machine 2 > > $ sudo cat /proc/drbd > version: 8.3.11 (api:88/proto:86-96) > GIT-hash: 0de839cee13a4160eed6037c4bddd066645e23c5 build by root@machine2, > 2013-02-18 19:26:57 > > 1: cs:StandAlone ro:Secondary/Unknown ds:Inconsistent/DUnknown r----s > ns:0 nr:0 dw:0 dr:0 al:0 bm:0 lo:0 pe:0 ua:0 ap:0 ep:1 wo:b def:0 > chkpt:0 oos:10485404 > > > Do you have some hints? > > Thank you, > > > Agya > > >> thanks >> shriram >> >> On Mon, Feb 18, 2013 at 5:38 AM, Hery Dian Septama >> wrote: >> > Hello, Anyone have a clue? I have tried but still failed :( >> > >> > On Sat, Feb 16, 2013 at 6:56 PM, agya naila >> > wrote: >> >> >> >> Dear all, >> >> >> >> I am configure my machine to run the remus disk replication. I am using >> >> xen 4.2.3 installed from sources and Ubuntu 12.04 64 bit both for Dom0 >> >> and >> >> DomU. >> >> I have install the blktap and its work properly with configuration >> >> string >> >> phy or tap2 like this : >> >> disk = ['phy:/dev/vggroup/DomU,xvda,w'] >> >> or >> >> disk = ['tap2:tapdisk:aio:/dev/vggroup/DomU,xvda,w'] >> >> >> >> and remus command >> >> >> >> remus --no-net myvm mybackuphost >> >> >> >> >> >> However when I change the string as suggested on remus pages to enable >> >> the >> >> disk replication its still failed : >> >> >> >> name = "DomU" >> >> memory = 1024 >> >> disk = ['tap2:remus:10.10.10.3:8002|aio:/dev/vggroup/DomU,xvda,w'] >> >> vif = ['ip=192.168.1.55,bridge=xenbr0'] >> >> bootloader = "pygrub" >> >> >> >> with error messages : >> >> >> >> name1@machine1:~$ sudo xm create -c /etc/xen/DomU.cfg >> >> Using config file "/etc/xen/DomU.cfg". >> >> Error: ('create', '-aremus:10.10.10.3:8002|aio:/dev/vggroup/DomU') >> >> failed >> >> (512 ) >> >> >> >> and on the log file : >> >> >> >> >> >> name1@machine1:~$ sudo sudo tail /var/log/xen/xend.log >> >> mounted_vbd_uuid = dom0.create_vbd(vbd, disk); >> >> File >> >> "/usr/local/lib/python2.7/dist-packages/xen/xend/XendDomainInfo.py", >> >> line >> >> 3987, in create_vbd >> >> devid = dev_control.createDevice(config) >> >> File >> >> >> >> "/usr/local/lib/python2.7/dist-packages/xen/xend/server/BlktapController.py", >> >> line 174, in createDevice >> >> device = TapdiskController.create(params, file) >> >> File >> >> >> >> "/usr/local/lib/python2.7/dist-packages/xen/xend/server/BlktapController.py", >> >> line 286, in create >> >> return TapdiskController.exc('create', '-a%s:%s' % (dtype, image)) >> >> File >> >> >> >> "/usr/local/lib/python2.7/dist-packages/xen/xend/server/BlktapController.py", >> >> line 233, in exc >> >> (args, rc, out, err)) >> >> TapdiskException: ('create', >> >> '-aremus:10.10.10.3:8002|aio:/dev/vggroup/DomU') failed (512 ) >> >> >> >> Any hints and help would very appreciated. >> >> >> >> Regards, >> >> >> >> Agya >> >> >> >> >> >> _______________________________________________ >> >> Xen-devel mailing list >> >> Xen-devel@lists.xen.org >> >> http://lists.xen.org/xen-devel >> >> >> > >> > >> > _______________________________________________ >> > 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 Mon Feb 18 21:35:45 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 18 Feb 2013 21:35: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 1U7YMc-0003ry-Sy; Mon, 18 Feb 2013 21:35:06 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U7YMa-0003rS-UI; Mon, 18 Feb 2013 21:35:05 +0000 Received: from [85.158.143.35:40027] by server-1.bemta-4.messagelabs.com id F5/F4-08839-88E92215; Mon, 18 Feb 2013 21:35:04 +0000 X-Env-Sender: rshriram@cs.ubc.ca X-Msg-Ref: server-16.tower-21.messagelabs.com!1361223295!13181757!1 X-Originating-IP: [142.103.6.52] X-SpamReason: No, hits=0.3 required=7.0 tests=RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 8532 invoked from network); 18 Feb 2013 21:35:02 -0000 Received: from unknown (HELO smtp.cs.ubc.ca) (142.103.6.52) by server-16.tower-21.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 18 Feb 2013 21:35:02 -0000 Received: from mail-ie0-f181.google.com (mail-ie0-f181.google.com [209.85.223.181]) (authenticated bits=0) by smtp.cs.ubc.ca (8.14.3/8.13.6) with ESMTP id r1ILXqXZ016075 (version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=FAIL); Mon, 18 Feb 2013 13:33:52 -0800 Received: by mail-ie0-f181.google.com with SMTP id 17so7774948iea.12 for ; Mon, 18 Feb 2013 13:33:51 -0800 (PST) X-Received: by 10.50.214.67 with SMTP id ny3mr8068679igc.13.1361223231144; Mon, 18 Feb 2013 13:33:51 -0800 (PST) MIME-Version: 1.0 Received: by 10.43.2.67 with HTTP; Mon, 18 Feb 2013 13:33:11 -0800 (PST) In-Reply-To: References: From: Shriram Rajagopalan Date: Mon, 18 Feb 2013 16:33:11 -0500 Message-ID: To: agya naila Cc: "xen-users@lists.xen.org" , "xen-devel@lists.xen.org" Subject: Re: [Xen-users] [Xen-devel] Remus disk replication failed X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: rshriram@cs.ubc.ca List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: 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 suggest you read up on the DRBD setup documentation from the drbd.org website. The setup procedure is same. You can later flip to the remus replication protocol by simply changing the protocol type (C to D). thanks shriram On Mon, Feb 18, 2013 at 4:11 PM, agya naila wrote: > > On Mon, Feb 18, 2013 at 9:08 PM, Shriram Rajagopalan > wrote: >> >> hi > > > Thank you shriram. > >> >> sorry for the delayed response. IIRC the blktap2 driver required for >> tapdisk replication doesnt exist in the mainstream dom0 kernels, IIRC. >> I havent used it in a long time myself. I suggest trying disk >> replication with DRBD. >> > > I am also found some information here > http://osdir.com/ml/xen-users/2011-07/msg00653.html about blktap2 problem on > amd64 architecture. I have tried to install and configure the DRBD but its > didn't connect each other. > I used drbd-8.3.11-remus and installed as follow > > cd /usr/src/ > wget > http://remusha.wikidot.com/local--files/configuring-and-installing-remus/drbd-8.3.11-remus.tar.gz > tar xzf drbd-8.3.9-remus.tar.gz > chown -R root:root drbd-8.3-remus > cd /usr/src/drbd-8.3-remus > chmod 777 autogen.sh > ./autogen.sh > dpkg-buildpackage -b -uc > cd /usr/src/drbd-8.3-remus/drbd > make clean > make > make install > cd /usr/src/ > cp /usr/src/drbd-8.3-remus/scripts/global_common.conf.protoD > /etc/drbd.d/global_common.conf > cp /usr/src/drbd-8.3-remus/scripts/testvms_protoD.res > /etc/drbd.d/SystemHA_protoD.res > > sudo apt-get install drbd8-utils > > from tutorial http://remusha.wikidot.com/configuring-and-installing-remus > > My *.res configuration as follow : > > resource drbd-vm{ > device /dev/drbd1; > disk /dev/vgvoip/DomU; > meta-disk internal; > on machine1 { > address 10.10.10.1:7789; > } > on machine2 { > address 10.10.10.3:7789; > } > } > > and then I invoke command to create that meta > > drbdadm create-md drbd-vm > > However, when I try to make this configuration up by : > > drbdadm up drbd-vm > > Its come with error : > > $ sudo drbdadm up drbd-vm > 1: Failure: (124) Device is attached to a disk (use detach first) > Command 'drbdsetup 1 disk /dev/vgvoip/DomU /dev/vgvoip/DomU internal > --set-defaults --create-device --fencing=dont-care --on-io-error=pass_on' > terminated with exit code 10 > > If I run the > > $ sudo drbdadm detach drbd-vm > > Its come error > > $ sudo drbdadm detach drbd-vm > 1: State change failed: (-2) Need access to UpToDate data > Command 'drbdsetup 1 detach' terminated with exit code 17 > > Here the /proc/drbd on both machine > > Machine 1 > > $ sudo cat /proc/drbd > version: 8.3.11 (api:88/proto:86-96) > GIT-hash: 0de839cee13a4160eed6037c4bddd066645e23c5 build by root@machine1, > 2013-02-18 18:49:57 > > 1: cs:StandAlone ro:Primary/Unknown ds:UpToDate/DUnknown r----s > ns:0 nr:0 dw:0 dr:1712 al:0 bm:0 lo:0 pe:0 ua:0 ap:0 ep:1 wo:b def:0 > chkpt:0 oos:10485404 > > > Machine 2 > > $ sudo cat /proc/drbd > version: 8.3.11 (api:88/proto:86-96) > GIT-hash: 0de839cee13a4160eed6037c4bddd066645e23c5 build by root@machine2, > 2013-02-18 19:26:57 > > 1: cs:StandAlone ro:Secondary/Unknown ds:Inconsistent/DUnknown r----s > ns:0 nr:0 dw:0 dr:0 al:0 bm:0 lo:0 pe:0 ua:0 ap:0 ep:1 wo:b def:0 > chkpt:0 oos:10485404 > > > Do you have some hints? > > Thank you, > > > Agya > > >> thanks >> shriram >> >> On Mon, Feb 18, 2013 at 5:38 AM, Hery Dian Septama >> wrote: >> > Hello, Anyone have a clue? I have tried but still failed :( >> > >> > On Sat, Feb 16, 2013 at 6:56 PM, agya naila >> > wrote: >> >> >> >> Dear all, >> >> >> >> I am configure my machine to run the remus disk replication. I am using >> >> xen 4.2.3 installed from sources and Ubuntu 12.04 64 bit both for Dom0 >> >> and >> >> DomU. >> >> I have install the blktap and its work properly with configuration >> >> string >> >> phy or tap2 like this : >> >> disk = ['phy:/dev/vggroup/DomU,xvda,w'] >> >> or >> >> disk = ['tap2:tapdisk:aio:/dev/vggroup/DomU,xvda,w'] >> >> >> >> and remus command >> >> >> >> remus --no-net myvm mybackuphost >> >> >> >> >> >> However when I change the string as suggested on remus pages to enable >> >> the >> >> disk replication its still failed : >> >> >> >> name = "DomU" >> >> memory = 1024 >> >> disk = ['tap2:remus:10.10.10.3:8002|aio:/dev/vggroup/DomU,xvda,w'] >> >> vif = ['ip=192.168.1.55,bridge=xenbr0'] >> >> bootloader = "pygrub" >> >> >> >> with error messages : >> >> >> >> name1@machine1:~$ sudo xm create -c /etc/xen/DomU.cfg >> >> Using config file "/etc/xen/DomU.cfg". >> >> Error: ('create', '-aremus:10.10.10.3:8002|aio:/dev/vggroup/DomU') >> >> failed >> >> (512 ) >> >> >> >> and on the log file : >> >> >> >> >> >> name1@machine1:~$ sudo sudo tail /var/log/xen/xend.log >> >> mounted_vbd_uuid = dom0.create_vbd(vbd, disk); >> >> File >> >> "/usr/local/lib/python2.7/dist-packages/xen/xend/XendDomainInfo.py", >> >> line >> >> 3987, in create_vbd >> >> devid = dev_control.createDevice(config) >> >> File >> >> >> >> "/usr/local/lib/python2.7/dist-packages/xen/xend/server/BlktapController.py", >> >> line 174, in createDevice >> >> device = TapdiskController.create(params, file) >> >> File >> >> >> >> "/usr/local/lib/python2.7/dist-packages/xen/xend/server/BlktapController.py", >> >> line 286, in create >> >> return TapdiskController.exc('create', '-a%s:%s' % (dtype, image)) >> >> File >> >> >> >> "/usr/local/lib/python2.7/dist-packages/xen/xend/server/BlktapController.py", >> >> line 233, in exc >> >> (args, rc, out, err)) >> >> TapdiskException: ('create', >> >> '-aremus:10.10.10.3:8002|aio:/dev/vggroup/DomU') failed (512 ) >> >> >> >> Any hints and help would very appreciated. >> >> >> >> Regards, >> >> >> >> Agya >> >> >> >> >> >> _______________________________________________ >> >> Xen-devel mailing list >> >> Xen-devel@lists.xen.org >> >> http://lists.xen.org/xen-devel >> >> >> > >> > >> > _______________________________________________ >> > 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 Mon Feb 18 21:40:42 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 18 Feb 2013 21:40: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 1U7YRX-0004UJ-2g; Mon, 18 Feb 2013 21:40:11 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U7YRV-0004U3-7n for xen-users@lists.xen.org; Mon, 18 Feb 2013 21:40:09 +0000 Received: from [85.158.137.99:4300] by server-15.bemta-3.messagelabs.com id 8B/A0-25405-8BF92215; Mon, 18 Feb 2013 21:40:08 +0000 X-Env-Sender: rshriram@cs.ubc.ca X-Msg-Ref: server-11.tower-217.messagelabs.com!1361223605!21168142!1 X-Originating-IP: [142.103.6.52] X-SpamReason: No, hits=0.8 required=7.0 tests=BODY_RANDOM_LONG, RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 27406 invoked from network); 18 Feb 2013 21:40:07 -0000 Received: from smtp.cs.ubc.ca (HELO smtp.cs.ubc.ca) (142.103.6.52) by server-11.tower-217.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 18 Feb 2013 21:40:07 -0000 Received: from mail-ia0-f177.google.com (mail-ia0-f177.google.com [209.85.210.177]) (authenticated bits=0) by smtp.cs.ubc.ca (8.14.3/8.13.6) with ESMTP id r1ILe307016934 (version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=FAIL) for ; Mon, 18 Feb 2013 13:40:04 -0800 Received: by mail-ia0-f177.google.com with SMTP id o25so738423iad.36 for ; Mon, 18 Feb 2013 13:40:02 -0800 (PST) X-Received: by 10.50.37.162 with SMTP id z2mr7325138igj.13.1361223602618; Mon, 18 Feb 2013 13:40:02 -0800 (PST) MIME-Version: 1.0 Received: by 10.43.2.67 with HTTP; Mon, 18 Feb 2013 13:39:22 -0800 (PST) In-Reply-To: References: From: Shriram Rajagopalan Date: Mon, 18 Feb 2013 16:39:22 -0500 Message-ID: To: Andrew Eross Cc: "xen-users@lists.xen.org" Subject: Re: [Xen-users] Remus Suspend event channel kernel support X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: rshriram@cs.ubc.ca List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: 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 The suspend event channel support exists in all Open SuSE kernels afaict. 3.* kernels inclusive. It hasnt made its way into mainline. It is not a config option. It requires some code modification and cannot be selectively enabled, in a clean way. I tried to add the event channel support to the kernel during the 3.0 release cycle. I couldnt quite get it to work and decided to drop it. 2.6.18 domU these days is certainly not a good choice :P. But you might be able to pull a Suse kernel, compile and change it to a .deb package, to install on the Ubuntu domU. cheers shriram On Mon, Feb 18, 2013 at 4:31 PM, Andrew Eross wrote: > And sorry I messed up your name, Shriram =) > > On Mon, Feb 18, 2013 at 6:31 PM, Andrew Eross wrote: >> >> Hi Shiriam, >> >> I've noticed there's a fair amount of mention of the need for "suspend >> event channel" support in the domU kernel when using Remus, and there's some >> mention of certain kernels that support it (e.g. >> http://xenbits.xen.org/hg/linux-2.6.18-xen.hg/) >> >> However, I'm running Ubuntu 12.04+ these days, and I don't think I'd want >> to install that kernel in favor of the linux 3.5 kernel it comes with (?). >> >> I was trying to see if there's a way to be able to compile a custom kernel >> with the required support? >> >> I just couldn't figure out exactly what having "suspend event channel >> support" means (e.g. is it a driver, a config option, a code change), and >> was hoping you might be able to help? >> >> Thanks! >> Andrew > > _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Mon Feb 18 21:40:42 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 18 Feb 2013 21:40: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 1U7YRX-0004UJ-2g; Mon, 18 Feb 2013 21:40:11 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U7YRV-0004U3-7n for xen-users@lists.xen.org; Mon, 18 Feb 2013 21:40:09 +0000 Received: from [85.158.137.99:4300] by server-15.bemta-3.messagelabs.com id 8B/A0-25405-8BF92215; Mon, 18 Feb 2013 21:40:08 +0000 X-Env-Sender: rshriram@cs.ubc.ca X-Msg-Ref: server-11.tower-217.messagelabs.com!1361223605!21168142!1 X-Originating-IP: [142.103.6.52] X-SpamReason: No, hits=0.8 required=7.0 tests=BODY_RANDOM_LONG, RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 27406 invoked from network); 18 Feb 2013 21:40:07 -0000 Received: from smtp.cs.ubc.ca (HELO smtp.cs.ubc.ca) (142.103.6.52) by server-11.tower-217.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 18 Feb 2013 21:40:07 -0000 Received: from mail-ia0-f177.google.com (mail-ia0-f177.google.com [209.85.210.177]) (authenticated bits=0) by smtp.cs.ubc.ca (8.14.3/8.13.6) with ESMTP id r1ILe307016934 (version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=FAIL) for ; Mon, 18 Feb 2013 13:40:04 -0800 Received: by mail-ia0-f177.google.com with SMTP id o25so738423iad.36 for ; Mon, 18 Feb 2013 13:40:02 -0800 (PST) X-Received: by 10.50.37.162 with SMTP id z2mr7325138igj.13.1361223602618; Mon, 18 Feb 2013 13:40:02 -0800 (PST) MIME-Version: 1.0 Received: by 10.43.2.67 with HTTP; Mon, 18 Feb 2013 13:39:22 -0800 (PST) In-Reply-To: References: From: Shriram Rajagopalan Date: Mon, 18 Feb 2013 16:39:22 -0500 Message-ID: To: Andrew Eross Cc: "xen-users@lists.xen.org" Subject: Re: [Xen-users] Remus Suspend event channel kernel support X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: rshriram@cs.ubc.ca List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: 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 The suspend event channel support exists in all Open SuSE kernels afaict. 3.* kernels inclusive. It hasnt made its way into mainline. It is not a config option. It requires some code modification and cannot be selectively enabled, in a clean way. I tried to add the event channel support to the kernel during the 3.0 release cycle. I couldnt quite get it to work and decided to drop it. 2.6.18 domU these days is certainly not a good choice :P. But you might be able to pull a Suse kernel, compile and change it to a .deb package, to install on the Ubuntu domU. cheers shriram On Mon, Feb 18, 2013 at 4:31 PM, Andrew Eross wrote: > And sorry I messed up your name, Shriram =) > > On Mon, Feb 18, 2013 at 6:31 PM, Andrew Eross wrote: >> >> Hi Shiriam, >> >> I've noticed there's a fair amount of mention of the need for "suspend >> event channel" support in the domU kernel when using Remus, and there's some >> mention of certain kernels that support it (e.g. >> http://xenbits.xen.org/hg/linux-2.6.18-xen.hg/) >> >> However, I'm running Ubuntu 12.04+ these days, and I don't think I'd want >> to install that kernel in favor of the linux 3.5 kernel it comes with (?). >> >> I was trying to see if there's a way to be able to compile a custom kernel >> with the required support? >> >> I just couldn't figure out exactly what having "suspend event channel >> support" means (e.g. is it a driver, a config option, a code change), and >> was hoping you might be able to help? >> >> Thanks! >> Andrew > > _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Mon Feb 18 21:49:47 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 18 Feb 2013 21:49: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 1U7YaF-00057n-Bh; Mon, 18 Feb 2013 21:49:11 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U7YaD-00057e-F3 for xen-users@lists.xen.org; Mon, 18 Feb 2013 21:49:09 +0000 Received: from [85.158.138.51:24028] by server-4.bemta-3.messagelabs.com id EE/86-17521-4D1A2215; Mon, 18 Feb 2013 21:49:08 +0000 X-Env-Sender: jaceksburghardt@gmail.com X-Msg-Ref: server-15.tower-174.messagelabs.com!1361224146!26332466!1 X-Originating-IP: [209.85.223.181] 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.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 8800 invoked from network); 18 Feb 2013 21:49:07 -0000 Received: from mail-ie0-f181.google.com (HELO mail-ie0-f181.google.com) (209.85.223.181) by server-15.tower-174.messagelabs.com with RC4-SHA encrypted SMTP; 18 Feb 2013 21:49:07 -0000 Received: by mail-ie0-f181.google.com with SMTP id 17so7790833iea.12 for ; Mon, 18 Feb 2013 13:49:06 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=/FarGZ0PODWN8FPBsnV+aGcaJ7/7P014Rqc4+ZCWAZ8=; b=0XtWA6MpgvPtDO+EgDJAeFfEd74HfNl5/qnimO7/JB0a3btHPuCDvqQ9GKRf2dHc42 GOjK91/kdjuPBqRnUuyIVSN8/ifyUtW/mMvYZ4w8QZYS0shZx+YERk1h8dcAvr9V1f9q rbkxln1pQJHKSNhl8hU623VoBTz6QjRzWEJQjm8ZmuIX0HTMRetBi/PnJz1a6eQjwn7S yyvi22bVpbshdqtUGnq66uRHxlXKBELfcVEhU4p6zd7MtL0B9XefPvNX4VmJVBgt47QW qh4YnXSr54djJCIIzp4rM8XdZhzM4DzvanH2JKmxaGsE1LYaSHgumHdVGu0kPQjHUq2A 5ZDg== MIME-Version: 1.0 X-Received: by 10.50.17.163 with SMTP id p3mr1975508igd.90.1361224146148; Mon, 18 Feb 2013 13:49:06 -0800 (PST) Received: by 10.42.41.5 with HTTP; Mon, 18 Feb 2013 13:49:06 -0800 (PST) In-Reply-To: <6035A0D088A63A46850C3988ED045A4B3567D7E6@BITCOM1.int.sbss.com.au> References: <6035A0D088A63A46850C3988ED045A4B3567D7E6@BITCOM1.int.sbss.com.au> Date: Mon, 18 Feb 2013 14:49:06 -0700 Message-ID: From: jacek burghardt To: James Harper Cc: "xen-users@lists.xen.org" , Matthias Subject: Re: [Xen-users] gplpv drivers X-BeenThere: xen-users@lists.xen.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="===============4746654775387011903==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============4746654775387011903== Content-Type: multipart/alternative; boundary=14dae93407cfb0db9604d606b1f1 --14dae93407cfb0db9604d606b1f1 Content-Type: text/plain; charset=ISO-8859-1 I was testing something and xl reboot does not do anything xen states domain xx rebooting but it seems nothing is being send to server 2012 . On Sun, Feb 17, 2013 at 3:26 PM, James Harper wrote: > > Also, don't get your hopes too high on the new gplpv drivers cause > > afaik James uses a Win7 for testing his drivers and I haven't heard > > from anyone testing them on Win2012 yet. But never the less I added > > him in cc, maybe he can clerify the situation a bit more. > > > > 2012 works (as in boots and runs) but I haven't done any performance > testing yet. > > Windows 8 has a feature where by default when you say shutdown it actually > hibernates instead, and I'm having a bit of trouble getting hibernate > working (or specifically, resume from hibernate). I think it won't actually > matter too much because on resume from hibernate, windows uses bios calls > to load the crash dump and this is horribly slow because it goes via qemu > not gplpv so most people would turn off the feature, but I'd still like to > have it working so a default install of win8 works and I don't get emails > asking why it crashed etc. > > James > > > --14dae93407cfb0db9604d606b1f1 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable I was testing something and xl reboot does not do anything xen states domai= n xx rebooting but it seems nothing is being send to server 2012 .

<= div class=3D"gmail_quote">On Sun, Feb 17, 2013 at 3:26 PM, James Harper <james.harper@bendigoit.com.au> wrote:
> Also, don't get your hopes too high= on the new gplpv drivers cause
> afaik James uses a Win7 for testing his drivers and I haven't hear= d
> from anyone testing them on Win2012 yet. But never the less I added > him in cc, maybe he can clerify the situation a bit more.
>

2012 works (as in boots and runs) but I haven't done any performance te= sting yet.

Windows 8 has a feature where by default when you say shutdown it actually = hibernates instead, and I'm having a bit of trouble getting hibernate w= orking (or specifically, resume from hibernate). I think it won't actua= lly matter too much because on resume from hibernate, windows uses bios cal= ls to load the crash dump and this is horribly slow because it goes via qem= u not gplpv so most people would turn off the feature, but I'd still li= ke to have it working so a default install of win8 works and I don't ge= t emails asking why it crashed etc.

James



--14dae93407cfb0db9604d606b1f1-- --===============4746654775387011903== 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 --===============4746654775387011903==-- From xen-users-bounces@lists.xen.org Mon Feb 18 21:49:47 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 18 Feb 2013 21:49: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 1U7YaF-00057n-Bh; Mon, 18 Feb 2013 21:49:11 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U7YaD-00057e-F3 for xen-users@lists.xen.org; Mon, 18 Feb 2013 21:49:09 +0000 Received: from [85.158.138.51:24028] by server-4.bemta-3.messagelabs.com id EE/86-17521-4D1A2215; Mon, 18 Feb 2013 21:49:08 +0000 X-Env-Sender: jaceksburghardt@gmail.com X-Msg-Ref: server-15.tower-174.messagelabs.com!1361224146!26332466!1 X-Originating-IP: [209.85.223.181] 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.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 8800 invoked from network); 18 Feb 2013 21:49:07 -0000 Received: from mail-ie0-f181.google.com (HELO mail-ie0-f181.google.com) (209.85.223.181) by server-15.tower-174.messagelabs.com with RC4-SHA encrypted SMTP; 18 Feb 2013 21:49:07 -0000 Received: by mail-ie0-f181.google.com with SMTP id 17so7790833iea.12 for ; Mon, 18 Feb 2013 13:49:06 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=/FarGZ0PODWN8FPBsnV+aGcaJ7/7P014Rqc4+ZCWAZ8=; b=0XtWA6MpgvPtDO+EgDJAeFfEd74HfNl5/qnimO7/JB0a3btHPuCDvqQ9GKRf2dHc42 GOjK91/kdjuPBqRnUuyIVSN8/ifyUtW/mMvYZ4w8QZYS0shZx+YERk1h8dcAvr9V1f9q rbkxln1pQJHKSNhl8hU623VoBTz6QjRzWEJQjm8ZmuIX0HTMRetBi/PnJz1a6eQjwn7S yyvi22bVpbshdqtUGnq66uRHxlXKBELfcVEhU4p6zd7MtL0B9XefPvNX4VmJVBgt47QW qh4YnXSr54djJCIIzp4rM8XdZhzM4DzvanH2JKmxaGsE1LYaSHgumHdVGu0kPQjHUq2A 5ZDg== MIME-Version: 1.0 X-Received: by 10.50.17.163 with SMTP id p3mr1975508igd.90.1361224146148; Mon, 18 Feb 2013 13:49:06 -0800 (PST) Received: by 10.42.41.5 with HTTP; Mon, 18 Feb 2013 13:49:06 -0800 (PST) In-Reply-To: <6035A0D088A63A46850C3988ED045A4B3567D7E6@BITCOM1.int.sbss.com.au> References: <6035A0D088A63A46850C3988ED045A4B3567D7E6@BITCOM1.int.sbss.com.au> Date: Mon, 18 Feb 2013 14:49:06 -0700 Message-ID: From: jacek burghardt To: James Harper Cc: "xen-users@lists.xen.org" , Matthias Subject: Re: [Xen-users] gplpv drivers X-BeenThere: xen-users@lists.xen.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="===============4746654775387011903==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============4746654775387011903== Content-Type: multipart/alternative; boundary=14dae93407cfb0db9604d606b1f1 --14dae93407cfb0db9604d606b1f1 Content-Type: text/plain; charset=ISO-8859-1 I was testing something and xl reboot does not do anything xen states domain xx rebooting but it seems nothing is being send to server 2012 . On Sun, Feb 17, 2013 at 3:26 PM, James Harper wrote: > > Also, don't get your hopes too high on the new gplpv drivers cause > > afaik James uses a Win7 for testing his drivers and I haven't heard > > from anyone testing them on Win2012 yet. But never the less I added > > him in cc, maybe he can clerify the situation a bit more. > > > > 2012 works (as in boots and runs) but I haven't done any performance > testing yet. > > Windows 8 has a feature where by default when you say shutdown it actually > hibernates instead, and I'm having a bit of trouble getting hibernate > working (or specifically, resume from hibernate). I think it won't actually > matter too much because on resume from hibernate, windows uses bios calls > to load the crash dump and this is horribly slow because it goes via qemu > not gplpv so most people would turn off the feature, but I'd still like to > have it working so a default install of win8 works and I don't get emails > asking why it crashed etc. > > James > > > --14dae93407cfb0db9604d606b1f1 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable I was testing something and xl reboot does not do anything xen states domai= n xx rebooting but it seems nothing is being send to server 2012 .

<= div class=3D"gmail_quote">On Sun, Feb 17, 2013 at 3:26 PM, James Harper <james.harper@bendigoit.com.au> wrote:
> Also, don't get your hopes too high= on the new gplpv drivers cause
> afaik James uses a Win7 for testing his drivers and I haven't hear= d
> from anyone testing them on Win2012 yet. But never the less I added > him in cc, maybe he can clerify the situation a bit more.
>

2012 works (as in boots and runs) but I haven't done any performance te= sting yet.

Windows 8 has a feature where by default when you say shutdown it actually = hibernates instead, and I'm having a bit of trouble getting hibernate w= orking (or specifically, resume from hibernate). I think it won't actua= lly matter too much because on resume from hibernate, windows uses bios cal= ls to load the crash dump and this is horribly slow because it goes via qem= u not gplpv so most people would turn off the feature, but I'd still li= ke to have it working so a default install of win8 works and I don't ge= t emails asking why it crashed etc.

James



--14dae93407cfb0db9604d606b1f1-- --===============4746654775387011903== 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 --===============4746654775387011903==-- From xen-users-bounces@lists.xen.org Mon Feb 18 21:53:07 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 18 Feb 2013 21: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 1U7YdZ-0005N2-8N; Mon, 18 Feb 2013 21:52:37 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U7YdX-0005Mv-86 for xen-users@lists.xen.org; Mon, 18 Feb 2013 21:52:35 +0000 Received: from [85.158.139.211:32066] by server-13.bemta-5.messagelabs.com id A3/91-06769-2A2A2215; Mon, 18 Feb 2013 21:52:34 +0000 X-Env-Sender: eross@corp.locatrix.com X-Msg-Ref: server-4.tower-206.messagelabs.com!1361224351!18138740!1 X-Originating-IP: [209.85.223.179] X-SpamReason: No, hits=0.9 required=7.0 tests=BODY_RANDOM_LONG, HTML_30_40,HTML_MESSAGE,RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 19048 invoked from network); 18 Feb 2013 21:52:33 -0000 Received: from mail-ie0-f179.google.com (HELO mail-ie0-f179.google.com) (209.85.223.179) by server-4.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 18 Feb 2013 21:52:33 -0000 Received: by mail-ie0-f179.google.com with SMTP id k11so7771104iea.10 for ; Mon, 18 Feb 2013 13:51:32 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=x-received:mime-version:in-reply-to:references:from:date:message-id :subject:to:cc:content-type:x-gm-message-state; bh=shn8RNmDZ5hAdUKyvKkG7ZGw+0lMJKquco2qrX7tN7k=; b=COGWWPifhgVrgawJQ5ISAXwSWbQN7UE/mVK3LwRR5vc1KVuGTI+UkLa9wwnBNkVMGe vKRmd5hcFhCaguVqlpz/KSL9eHSnvBHgskOUoE1iyxRLUoog11rHVGIfOJz+CQO4Cq3L Oo2REIdAbT3+WZQznCkXHAWY+9nuXrNJhLZ5Qmn8tDu+TzDS61h3n1vwHHvjeK5VmnMI LTUlhvnGIpKkUK7VSDrW3Ha3Bsd8DwlLXV5sZCInYGttNgpoKuY0Jj9ZZArBQxCC6eEQ vJaDcBc5u42gMi5FHwadmr9kVN9U6A5eapzmIY7/THlFAQewqoBOFlzx3s+n/PjNXWMb wU7A== X-Received: by 10.42.121.14 with SMTP id h14mr6509865icr.27.1361224292490; Mon, 18 Feb 2013 13:51:32 -0800 (PST) MIME-Version: 1.0 Received: by 10.64.44.197 with HTTP; Mon, 18 Feb 2013 13:51:12 -0800 (PST) In-Reply-To: References: From: Andrew Eross Date: Mon, 18 Feb 2013 18:51:12 -0300 Message-ID: To: rshriram@cs.ubc.ca X-Gm-Message-State: ALoCoQmOFWLgkM/0K+W1GaYIrYrO1btHbuVrHN0Zs2r94oAQtoGZ//iHvioXqQQsauRJ0EtOaUz3 Cc: "xen-users@lists.xen.org" Subject: Re: [Xen-users] Remus Suspend event channel kernel support X-BeenThere: xen-users@lists.xen.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="===============4035867237508534649==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============4035867237508534649== Content-Type: multipart/alternative; boundary=20cf301b667169de4104d606baeb --20cf301b667169de4104d606baeb Content-Type: text/plain; charset=ISO-8859-1 Ahh gotcha, ok, thanks Shriram, it was tricky to discern that until now. For my lab experiment here I think I'll just use a OpenSuse domU then for now as it sounds like the easiest path. Many thanks, Andrew On Mon, Feb 18, 2013 at 6:39 PM, Shriram Rajagopalan wrote: > Hi > The suspend event channel support exists in all Open SuSE kernels > afaict. 3.* kernels inclusive. > It hasnt made its way into mainline. > It is not a config option. It requires some code modification and > cannot be selectively enabled, in a clean way. > I tried to add the event channel support to the kernel during the > 3.0 release cycle. I couldnt quite get it to work and decided to drop > it. > > 2.6.18 domU these days is certainly not a good choice :P. > But you might be able to pull a Suse kernel, compile and change it > to a .deb package, to install on the Ubuntu domU. > > cheers > shriram > > On Mon, Feb 18, 2013 at 4:31 PM, Andrew Eross wrote: > > And sorry I messed up your name, Shriram =) > > > > On Mon, Feb 18, 2013 at 6:31 PM, Andrew Eross > wrote: > >> > >> Hi Shiriam, > >> > >> I've noticed there's a fair amount of mention of the need for "suspend > >> event channel" support in the domU kernel when using Remus, and there's > some > >> mention of certain kernels that support it (e.g. > >> http://xenbits.xen.org/hg/linux-2.6.18-xen.hg/) > >> > >> However, I'm running Ubuntu 12.04+ these days, and I don't think I'd > want > >> to install that kernel in favor of the linux 3.5 kernel it comes with > (?). > >> > >> I was trying to see if there's a way to be able to compile a custom > kernel > >> with the required support? > >> > >> I just couldn't figure out exactly what having "suspend event channel > >> support" means (e.g. is it a driver, a config option, a code change), > and > >> was hoping you might be able to help? > >> > >> Thanks! > >> Andrew > > > > > --20cf301b667169de4104d606baeb Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Ahh gotcha, ok, thanks Shriram, it was tricky to discern that until now.
For my lab experiment here I think I'll just use a Ope= nSuse domU then for now as it sounds like the easiest path.

Many thanks,
Andrew


On Mon, Feb 18, 2013 at 6:39 PM, Shriram= Rajagopalan <rshriram@cs.ubc.ca> wrote:
Hi
=A0The suspend event channel support exists in all Open SuSE kernels
afaict. 3.* kernels inclusive.
=A0 It hasnt made its way into mainline.
=A0 It is not a config option. It requires some code modification and
cannot be selectively enabled, in a clean way.
=A0 I tried to add the event channel support to the kernel during the
3.0 release cycle. I couldnt quite get it to work and decided to drop
it.

=A0 2.6.18 domU these days is certainly not a good choice :P.
=A0 But you might be able to pull a Suse kernel, compile and change it
to a .deb package, to install on the Ubuntu domU.

cheers
shriram

On Mon, Feb 18, 2013 at 4:31 PM, Andrew Eross <eross@locatrix.com> wrote:
> And sorry I messed up your name, Shriram =3D)
>
> On Mon, Feb 18, 2013 at 6:31 PM, Andrew Eross <eross@locatrix.com> wrote:
>>
>> Hi Shiriam,
>>
>> I've noticed there's a fair amount of mention of the need = for "suspend
>> event channel" support in the domU kernel when using Remus, a= nd there's some
>> mention of certain kernels that support it (e.g.
>> http://xenbits.xen.org/hg/linux-2.6.18-xen.hg/)
>>
>> However, I'm running Ubuntu 12.04+ these days, and I don't= think I'd want
>> to install that kernel in favor of the linux 3.5 kernel it comes w= ith (?).
>>
>> I was trying to see if there's a way to be able to compile a c= ustom kernel
>> with the required support?
>>
>> I just couldn't figure out exactly what having "suspend e= vent channel
>> support" means (e.g. is it a driver, a config option, a code = change), and
>> was hoping you might be able to help?
>>
>> Thanks!
>> Andrew
>
>

--20cf301b667169de4104d606baeb-- --===============4035867237508534649== 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 --===============4035867237508534649==-- From xen-users-bounces@lists.xen.org Mon Feb 18 21:53:07 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 18 Feb 2013 21: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 1U7YdZ-0005N2-8N; Mon, 18 Feb 2013 21:52:37 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U7YdX-0005Mv-86 for xen-users@lists.xen.org; Mon, 18 Feb 2013 21:52:35 +0000 Received: from [85.158.139.211:32066] by server-13.bemta-5.messagelabs.com id A3/91-06769-2A2A2215; Mon, 18 Feb 2013 21:52:34 +0000 X-Env-Sender: eross@corp.locatrix.com X-Msg-Ref: server-4.tower-206.messagelabs.com!1361224351!18138740!1 X-Originating-IP: [209.85.223.179] X-SpamReason: No, hits=0.9 required=7.0 tests=BODY_RANDOM_LONG, HTML_30_40,HTML_MESSAGE,RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 19048 invoked from network); 18 Feb 2013 21:52:33 -0000 Received: from mail-ie0-f179.google.com (HELO mail-ie0-f179.google.com) (209.85.223.179) by server-4.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 18 Feb 2013 21:52:33 -0000 Received: by mail-ie0-f179.google.com with SMTP id k11so7771104iea.10 for ; Mon, 18 Feb 2013 13:51:32 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=x-received:mime-version:in-reply-to:references:from:date:message-id :subject:to:cc:content-type:x-gm-message-state; bh=shn8RNmDZ5hAdUKyvKkG7ZGw+0lMJKquco2qrX7tN7k=; b=COGWWPifhgVrgawJQ5ISAXwSWbQN7UE/mVK3LwRR5vc1KVuGTI+UkLa9wwnBNkVMGe vKRmd5hcFhCaguVqlpz/KSL9eHSnvBHgskOUoE1iyxRLUoog11rHVGIfOJz+CQO4Cq3L Oo2REIdAbT3+WZQznCkXHAWY+9nuXrNJhLZ5Qmn8tDu+TzDS61h3n1vwHHvjeK5VmnMI LTUlhvnGIpKkUK7VSDrW3Ha3Bsd8DwlLXV5sZCInYGttNgpoKuY0Jj9ZZArBQxCC6eEQ vJaDcBc5u42gMi5FHwadmr9kVN9U6A5eapzmIY7/THlFAQewqoBOFlzx3s+n/PjNXWMb wU7A== X-Received: by 10.42.121.14 with SMTP id h14mr6509865icr.27.1361224292490; Mon, 18 Feb 2013 13:51:32 -0800 (PST) MIME-Version: 1.0 Received: by 10.64.44.197 with HTTP; Mon, 18 Feb 2013 13:51:12 -0800 (PST) In-Reply-To: References: From: Andrew Eross Date: Mon, 18 Feb 2013 18:51:12 -0300 Message-ID: To: rshriram@cs.ubc.ca X-Gm-Message-State: ALoCoQmOFWLgkM/0K+W1GaYIrYrO1btHbuVrHN0Zs2r94oAQtoGZ//iHvioXqQQsauRJ0EtOaUz3 Cc: "xen-users@lists.xen.org" Subject: Re: [Xen-users] Remus Suspend event channel kernel support X-BeenThere: xen-users@lists.xen.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="===============4035867237508534649==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============4035867237508534649== Content-Type: multipart/alternative; boundary=20cf301b667169de4104d606baeb --20cf301b667169de4104d606baeb Content-Type: text/plain; charset=ISO-8859-1 Ahh gotcha, ok, thanks Shriram, it was tricky to discern that until now. For my lab experiment here I think I'll just use a OpenSuse domU then for now as it sounds like the easiest path. Many thanks, Andrew On Mon, Feb 18, 2013 at 6:39 PM, Shriram Rajagopalan wrote: > Hi > The suspend event channel support exists in all Open SuSE kernels > afaict. 3.* kernels inclusive. > It hasnt made its way into mainline. > It is not a config option. It requires some code modification and > cannot be selectively enabled, in a clean way. > I tried to add the event channel support to the kernel during the > 3.0 release cycle. I couldnt quite get it to work and decided to drop > it. > > 2.6.18 domU these days is certainly not a good choice :P. > But you might be able to pull a Suse kernel, compile and change it > to a .deb package, to install on the Ubuntu domU. > > cheers > shriram > > On Mon, Feb 18, 2013 at 4:31 PM, Andrew Eross wrote: > > And sorry I messed up your name, Shriram =) > > > > On Mon, Feb 18, 2013 at 6:31 PM, Andrew Eross > wrote: > >> > >> Hi Shiriam, > >> > >> I've noticed there's a fair amount of mention of the need for "suspend > >> event channel" support in the domU kernel when using Remus, and there's > some > >> mention of certain kernels that support it (e.g. > >> http://xenbits.xen.org/hg/linux-2.6.18-xen.hg/) > >> > >> However, I'm running Ubuntu 12.04+ these days, and I don't think I'd > want > >> to install that kernel in favor of the linux 3.5 kernel it comes with > (?). > >> > >> I was trying to see if there's a way to be able to compile a custom > kernel > >> with the required support? > >> > >> I just couldn't figure out exactly what having "suspend event channel > >> support" means (e.g. is it a driver, a config option, a code change), > and > >> was hoping you might be able to help? > >> > >> Thanks! > >> Andrew > > > > > --20cf301b667169de4104d606baeb Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Ahh gotcha, ok, thanks Shriram, it was tricky to discern that until now.
For my lab experiment here I think I'll just use a Ope= nSuse domU then for now as it sounds like the easiest path.

Many thanks,
Andrew


On Mon, Feb 18, 2013 at 6:39 PM, Shriram= Rajagopalan <rshriram@cs.ubc.ca> wrote:
Hi
=A0The suspend event channel support exists in all Open SuSE kernels
afaict. 3.* kernels inclusive.
=A0 It hasnt made its way into mainline.
=A0 It is not a config option. It requires some code modification and
cannot be selectively enabled, in a clean way.
=A0 I tried to add the event channel support to the kernel during the
3.0 release cycle. I couldnt quite get it to work and decided to drop
it.

=A0 2.6.18 domU these days is certainly not a good choice :P.
=A0 But you might be able to pull a Suse kernel, compile and change it
to a .deb package, to install on the Ubuntu domU.

cheers
shriram

On Mon, Feb 18, 2013 at 4:31 PM, Andrew Eross <eross@locatrix.com> wrote:
> And sorry I messed up your name, Shriram =3D)
>
> On Mon, Feb 18, 2013 at 6:31 PM, Andrew Eross <eross@locatrix.com> wrote:
>>
>> Hi Shiriam,
>>
>> I've noticed there's a fair amount of mention of the need = for "suspend
>> event channel" support in the domU kernel when using Remus, a= nd there's some
>> mention of certain kernels that support it (e.g.
>> http://xenbits.xen.org/hg/linux-2.6.18-xen.hg/)
>>
>> However, I'm running Ubuntu 12.04+ these days, and I don't= think I'd want
>> to install that kernel in favor of the linux 3.5 kernel it comes w= ith (?).
>>
>> I was trying to see if there's a way to be able to compile a c= ustom kernel
>> with the required support?
>>
>> I just couldn't figure out exactly what having "suspend e= vent channel
>> support" means (e.g. is it a driver, a config option, a code = change), and
>> was hoping you might be able to help?
>>
>> Thanks!
>> Andrew
>
>

--20cf301b667169de4104d606baeb-- --===============4035867237508534649== 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 --===============4035867237508534649==-- From xen-users-bounces@lists.xen.org Mon Feb 18 21:59:42 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 18 Feb 2013 21:59: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 1U7Yju-0005hp-F8; Mon, 18 Feb 2013 21:59:10 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U7Yjs-0005ha-6k for xen-users@lists.xen.org; Mon, 18 Feb 2013 21:59:08 +0000 Received: from [85.158.139.211:55823] by server-5.bemta-5.messagelabs.com id 83/D5-11945-B24A2215; Mon, 18 Feb 2013 21:59:07 +0000 X-Env-Sender: eross@corp.locatrix.com X-Msg-Ref: server-2.tower-206.messagelabs.com!1361224744!18113828!1 X-Originating-IP: [209.85.210.173] X-SpamReason: No, hits=1.4 required=7.0 tests=BODY_RANDOM_LONG, HTML_40_50,HTML_MESSAGE,RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 23274 invoked from network); 18 Feb 2013 21:59:06 -0000 Received: from mail-ia0-f173.google.com (HELO mail-ia0-f173.google.com) (209.85.210.173) by server-2.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 18 Feb 2013 21:59:06 -0000 Received: by mail-ia0-f173.google.com with SMTP id h37so5546658iak.4 for ; Mon, 18 Feb 2013 13:59:03 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=x-received:mime-version:from:date:message-id:subject:to :content-type:x-gm-message-state; bh=tbU91V7mzxT0xN+e/SPG1P16cvkzeblUH010hDNhfXY=; b=aXlqg3y0duKS26F7Lkiw2DVS0hLS0HJarD5W4TO2fr0MEFUHNgVk8hS0162KRTmjHi npHvExsOMeJfHqB0ZKZ98RqJSEABWaL/RqseXHaWHtwpVvSxgAXowsEFfcX8KFl8zmQU KGHYpcWwY+azrB6q6eAbPdUOKD6AmmuQmk2JiyBvCUiokZb6gWDOMMi3L0LyfcfUNCvM G7T8h+AZFe+Z5z6gMfnRCRPg8A9dKlX48zxCH9q/Xuvn0iL6IRSS0zW4Ywvou7nm6cai eqd1L1LX+gVIvmMO6ZLNBtVr1vay3nP0vIFreiMZPyxZZEGli1Bu/s8IMZ7J6mHKikPb wKVw== X-Received: by 10.50.186.134 with SMTP id fk6mr8305762igc.9.1361224743332; Mon, 18 Feb 2013 13:59:03 -0800 (PST) MIME-Version: 1.0 Received: by 10.64.44.197 with HTTP; Mon, 18 Feb 2013 13:58:43 -0800 (PST) From: Andrew Eross Date: Mon, 18 Feb 2013 18:58:43 -0300 Message-ID: To: rshriram@cs.ubc.ca, xen-users@lists.xen.org X-Gm-Message-State: ALoCoQnbxt2UhoCxvaNoNCZmzg4xGQRl8z2KP13gr3cIgbED7VrS1HfyhAOTBVhvUWR1w/8hgdDH Subject: [Xen-users] Remus dom0 network buffering X-BeenThere: xen-users@lists.xen.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="===============8414361374979157334==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============8414361374979157334== Content-Type: multipart/alternative; boundary=14dae9340f2d492a7704d606d51f --14dae9340f2d492a7704d606d51f Content-Type: text/plain; charset=ISO-8859-1 Hi Shriram, I had another question for you if you don't mind - I've been experimenting with a Ubuntu 12.10 dom0 running Xen 4.1.4 and using Remus with DRBD. I'm writing it all up and will post up my findings on our blog as well... once I figure it out =). I can run Remus successfully now in fact, transitioning VMs from one test machine to another with DRBD, but only when I use "--no-net". If I run "remus -i 40 --no-net rt left" this works. If I run "remus -i 40 rt left", I get the below: WARNING: suspend event channel unavailable, falling back to slow xenstore signalling PROF: suspending at 1361224385.607101 installing buffer on ifb0... RTNETLINK answers: Invalid argument xc: error: Suspend request failed: Internal error xc: error: Domain appears not to have suspended: Internal error PROF: resumed at 1361224385.618021 Traceback (most recent call last): File "/usr/bin/remus", line 219, in run(cfg) File "/usr/bin/remus", line 205, in run for buf in bufs: File "/usr/bin/remus", line 142, in postsuspend buf.postsuspend() File "/usr/lib/python2.7/dist-packages/xen/remus/device.py", line 333, in postsuspend self.install() File "/usr/lib/python2.7/dist-packages/xen/remus/device.py", line 380, in install self.rth.talk(req.pack()) File "/usr/lib/python2.7/dist-packages/xen/remus/netlink.py", line 318, in talk self._rth.talk(req) IOError: error sending message My /etc/modules contains: sch_plug sch_prio sch_ingress cls_basic cls_tcindex cls_u32 act_mirred ifb I was under the impression that "ifb" and "sch_plug" were the key items required, but I'm not quite sure - all the online materials are a bit mixed in their explanations on this point. For further information, here's my system's modules: root@right:/home/eross# lsmod Module Size Used by ifb 12897 0 xt_physdev 12588 4 iptable_filter 12811 1 ip_tables 26996 1 iptable_filter x_tables 29757 3 xt_physdev,iptable_filter,ip_tables xen_netback 27434 0 [permanent] xen_blkback 23041 0 [permanent] xen_gntdev 17391 0 xen_evtchn 13221 3 xenfs 12986 1 xen_privcmd 13081 16 xenfs bridge 90447 0 stp 12977 1 bridge llc 14553 2 bridge,stp coretemp 13401 0 snd_hda_codec_via 46676 1 ghash_clmulni_intel 13221 0 cryptd 20404 1 ghash_clmulni_intel eeepc_wmi 13110 0 asus_wmi 24089 1 eeepc_wmi sparse_keymap 13891 1 asus_wmi microcode 22804 0 psmouse 95595 0 serio_raw 13216 0 ext2 72881 1 act_mirred 13039 1 mac_hid 13206 0 cls_u32 17138 1 cls_tcindex 13059 0 cls_basic 12947 0 sch_ingress 12867 1 wmi 19071 1 asus_wmi sch_prio 13153 0 sch_plug 12655 0 drbd 300253 4 snd_hda_intel 33492 0 lpc_ich 17062 0 snd_hda_codec 134213 2 snd_hda_codec_via,snd_hda_intel snd_hwdep 17699 1 snd_hda_codec snd_pcm 96668 2 snd_hda_intel,snd_hda_codec snd_timer 29426 1 snd_pcm snd 78921 6 snd_hda_codec_via,snd_hda_intel,snd_hda_codec,snd_hwdep,snd_pcm,snd_timer soundcore 15048 1 snd i915 520621 1 snd_page_alloc 18485 2 snd_hda_intel,snd_pcm mei 40691 0 drm_kms_helper 49113 1 i915 drm 288721 2 i915,drm_kms_helper lp 17760 0 parport 46346 1 lp i2c_algo_bit 13414 1 i915 video 19336 1 i915 r8169 61651 0 root@right:/home/eross# uname -a Linux right 3.5.0-23-generic #35-Ubuntu SMP Thu Jan 24 13:15:40 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux Thanks! Andrew --14dae9340f2d492a7704d606d51f Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Hi Shriram,

I had another question for you if you don= 9;t mind -

I've been experimenting with a Ubun= tu 12.10 dom0 running Xen 4.1.4 and using Remus with DRBD.

I'm writing it all up and will post up my findings on our bl= og as well... once I figure it out =3D).

I can run= Remus successfully now in fact, transitioning VMs from one test machine to= another with DRBD, but only when I use "--no-net".

If I run "remus -i 40 --no-net rt left" this = works.

If I run "remus -i 40 rt left", I= get the below:

WARNING: suspend event channe= l unavailable, falling back to slow xenstore signalling
PROF: suspending at 1361224385.607101
installing buffer on i= fb0... RTNETLINK answers: Invalid argument
xc: error: Suspend req= uest failed: Internal error
xc: error: Domain appears not to have= suspended: Internal error
PROF: resumed at 1361224385.618021

Traceback = (most recent call last):
=A0 File "/usr/bin/remus", lin= e 219, in <module>
=A0 =A0 run(cfg)
=A0 File &quo= t;/usr/bin/remus", line 205, in run
=A0 =A0 for buf in bufs:
=A0 File "/usr/bin/remus"= , line 142, in postsuspend
=A0 =A0 buf.postsuspend()
= =A0 File "/usr/lib/python2.7/dist-packages/xen/remus/device.py", = line 333, in postsuspend
=A0 =A0 self.install()
=A0 File "/usr/lib/python2.7/dis= t-packages/xen/remus/device.py", line 380, in install
=A0 = =A0 self.rth.talk(req.pack())
=A0 File "/usr/lib/python2.7/d= ist-packages/xen/remus/netlink.py", line 318, in talk
=A0 =A0 self._rth.talk(req)
IOError: error sending message

My /etc/modules contains:
sch_plug
sch_prio
sch_ingress
cls_basic
cls_t= cindex
cls_u32
act_mirred
ifb

<= div>I was under the impression that "ifb" and "sch_plug"= ; were the key items required, but I'm not quite sure - all the online = materials are a bit mixed in their explanations on this point.

For further information, here's my system's mod= ules:

root@right:/home/eross# lsmod
Module =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0Size =A0Used by
ifb = =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A012897 =A00=A0
xt_physdev =A0 =A0 =A0 =A0 =A0 =A0 12588 =A04=A0
iptable_fil= ter =A0 =A0 =A0 =A0 12811 =A01=A0
ip_tables =A0 =A0 =A0 =A0 =A0 = =A0 =A026996 =A01 iptable_filter
x_tables =A0 =A0 =A0 =A0 =A0 =A0= =A0 29757 =A03 xt_physdev,iptable_filter,ip_tables
xen_netback =A0 =A0 =A0 =A0 =A0 =A027434 =A00 [permanent]
xe= n_blkback =A0 =A0 =A0 =A0 =A0 =A023041 =A00 [permanent]
xen_gntde= v =A0 =A0 =A0 =A0 =A0 =A0 17391 =A00=A0
xen_evtchn =A0 =A0 =A0 = =A0 =A0 =A0 13221 =A03=A0
xenfs =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A012986 =A01=A0
xen_privcmd =A0 =A0 =A0 =A0 =A0 =A013081 =A016 xenfs
bridge = =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 90447 =A00=A0
stp =A0 =A0 =A0 =A0= =A0 =A0 =A0 =A0 =A0 =A012977 =A01 bridge
llc =A0 =A0 =A0 =A0 =A0= =A0 =A0 =A0 =A0 =A014553 =A02 bridge,stp
coretemp =A0 =A0 =A0 = =A0 =A0 =A0 =A0 13401 =A00=A0
snd_hda_codec_via =A0 =A0 =A046676 =A01=A0
ghash_clmulni_int= el =A0 =A013221 =A00=A0
cryptd =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 20= 404 =A01 ghash_clmulni_intel
eeepc_wmi =A0 =A0 =A0 =A0 =A0 =A0 = =A013110 =A00=A0
asus_wmi =A0 =A0 =A0 =A0 =A0 =A0 =A0 24089 =A01 = eeepc_wmi
sparse_keymap =A0 =A0 =A0 =A0 =A013891 =A01 asus_wmi
microco= de =A0 =A0 =A0 =A0 =A0 =A0 =A022804 =A00=A0
psmouse =A0 =A0 =A0 = =A0 =A0 =A0 =A0 =A095595 =A00=A0
serio_raw =A0 =A0 =A0 =A0 =A0 = =A0 =A013216 =A00=A0
ext2 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 728= 81 =A01=A0
act_mirred =A0 =A0 =A0 =A0 =A0 =A0 13039 =A01=A0
mac_hid =A0= =A0 =A0 =A0 =A0 =A0 =A0 =A013206 =A00=A0
cls_u32 =A0 =A0 =A0 =A0= =A0 =A0 =A0 =A017138 =A01=A0
cls_tcindex =A0 =A0 =A0 =A0 =A0 =A0= 13059 =A00=A0
cls_basic =A0 =A0 =A0 =A0 =A0 =A0 =A012947 =A00=A0<= /div>
sch_ingress =A0 =A0 =A0 =A0 =A0 =A012867 =A01=A0
wmi =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A019071 =A01 asus_wmi
sch_prio =A0 =A0 =A0 =A0 =A0 =A0 =A0 13153 =A00=A0
sch_plug = =A0 =A0 =A0 =A0 =A0 =A0 =A0 12655 =A00=A0
drbd =A0 =A0 =A0 =A0 = =A0 =A0 =A0 =A0 =A0300253 =A04=A0
snd_hda_intel =A0 =A0 =A0 =A0 = =A033492 =A00=A0
lpc_ich =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A017062 =A00=A0
snd_hda= _codec =A0 =A0 =A0 =A0 134213 =A02 snd_hda_codec_via,snd_hda_intel
snd_hwdep =A0 =A0 =A0 =A0 =A0 =A0 =A017699 =A01 snd_hda_codec
s= nd_pcm =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A096668 =A02 snd_hda_intel,snd_hda_code= c
snd_timer =A0 =A0 =A0 =A0 =A0 =A0 =A029426 =A01 snd_pcm
snd = =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A078921 =A06 snd_hda_codec_via,snd_hda= _intel,snd_hda_codec,snd_hwdep,snd_pcm,snd_timer
soundcore =A0 = =A0 =A0 =A0 =A0 =A0 =A015048 =A01 snd
i915 =A0 =A0 =A0 =A0 =A0 = =A0 =A0 =A0 =A0520621 =A01=A0
snd_page_alloc =A0 =A0 =A0 =A0 18485 =A02 snd_hda_intel,snd_pcm
<= div>mei =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A040691 =A00=A0
drm_= kms_helper =A0 =A0 =A0 =A0 49113 =A01 i915
drm =A0 =A0 =A0 =A0 = =A0 =A0 =A0 =A0 =A0 288721 =A02 i915,drm_kms_helper
lp =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 17760 =A00=A0
parport = =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A046346 =A01 lp
i2c_algo_bit =A0 =A0= =A0 =A0 =A0 13414 =A01 i915
video =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0 =A019336 =A01 i915
r8169 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A06= 1651 =A00=A0

root@right:/home/eross# uname -a
Linux right 3.5.0= -23-generic #35-Ubuntu SMP Thu Jan 24 13:15:40 UTC 2013 x86_64 x86_64 x86_6= 4 GNU/Linux

Thanks!
Andrew
--14dae9340f2d492a7704d606d51f-- --===============8414361374979157334== 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 --===============8414361374979157334==-- From xen-users-bounces@lists.xen.org Mon Feb 18 21:59:42 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 18 Feb 2013 21:59: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 1U7Yju-0005hp-F8; Mon, 18 Feb 2013 21:59:10 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U7Yjs-0005ha-6k for xen-users@lists.xen.org; Mon, 18 Feb 2013 21:59:08 +0000 Received: from [85.158.139.211:55823] by server-5.bemta-5.messagelabs.com id 83/D5-11945-B24A2215; Mon, 18 Feb 2013 21:59:07 +0000 X-Env-Sender: eross@corp.locatrix.com X-Msg-Ref: server-2.tower-206.messagelabs.com!1361224744!18113828!1 X-Originating-IP: [209.85.210.173] X-SpamReason: No, hits=1.4 required=7.0 tests=BODY_RANDOM_LONG, HTML_40_50,HTML_MESSAGE,RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 23274 invoked from network); 18 Feb 2013 21:59:06 -0000 Received: from mail-ia0-f173.google.com (HELO mail-ia0-f173.google.com) (209.85.210.173) by server-2.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 18 Feb 2013 21:59:06 -0000 Received: by mail-ia0-f173.google.com with SMTP id h37so5546658iak.4 for ; Mon, 18 Feb 2013 13:59:03 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=x-received:mime-version:from:date:message-id:subject:to :content-type:x-gm-message-state; bh=tbU91V7mzxT0xN+e/SPG1P16cvkzeblUH010hDNhfXY=; b=aXlqg3y0duKS26F7Lkiw2DVS0hLS0HJarD5W4TO2fr0MEFUHNgVk8hS0162KRTmjHi npHvExsOMeJfHqB0ZKZ98RqJSEABWaL/RqseXHaWHtwpVvSxgAXowsEFfcX8KFl8zmQU KGHYpcWwY+azrB6q6eAbPdUOKD6AmmuQmk2JiyBvCUiokZb6gWDOMMi3L0LyfcfUNCvM G7T8h+AZFe+Z5z6gMfnRCRPg8A9dKlX48zxCH9q/Xuvn0iL6IRSS0zW4Ywvou7nm6cai eqd1L1LX+gVIvmMO6ZLNBtVr1vay3nP0vIFreiMZPyxZZEGli1Bu/s8IMZ7J6mHKikPb wKVw== X-Received: by 10.50.186.134 with SMTP id fk6mr8305762igc.9.1361224743332; Mon, 18 Feb 2013 13:59:03 -0800 (PST) MIME-Version: 1.0 Received: by 10.64.44.197 with HTTP; Mon, 18 Feb 2013 13:58:43 -0800 (PST) From: Andrew Eross Date: Mon, 18 Feb 2013 18:58:43 -0300 Message-ID: To: rshriram@cs.ubc.ca, xen-users@lists.xen.org X-Gm-Message-State: ALoCoQnbxt2UhoCxvaNoNCZmzg4xGQRl8z2KP13gr3cIgbED7VrS1HfyhAOTBVhvUWR1w/8hgdDH Subject: [Xen-users] Remus dom0 network buffering X-BeenThere: xen-users@lists.xen.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="===============8414361374979157334==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============8414361374979157334== Content-Type: multipart/alternative; boundary=14dae9340f2d492a7704d606d51f --14dae9340f2d492a7704d606d51f Content-Type: text/plain; charset=ISO-8859-1 Hi Shriram, I had another question for you if you don't mind - I've been experimenting with a Ubuntu 12.10 dom0 running Xen 4.1.4 and using Remus with DRBD. I'm writing it all up and will post up my findings on our blog as well... once I figure it out =). I can run Remus successfully now in fact, transitioning VMs from one test machine to another with DRBD, but only when I use "--no-net". If I run "remus -i 40 --no-net rt left" this works. If I run "remus -i 40 rt left", I get the below: WARNING: suspend event channel unavailable, falling back to slow xenstore signalling PROF: suspending at 1361224385.607101 installing buffer on ifb0... RTNETLINK answers: Invalid argument xc: error: Suspend request failed: Internal error xc: error: Domain appears not to have suspended: Internal error PROF: resumed at 1361224385.618021 Traceback (most recent call last): File "/usr/bin/remus", line 219, in run(cfg) File "/usr/bin/remus", line 205, in run for buf in bufs: File "/usr/bin/remus", line 142, in postsuspend buf.postsuspend() File "/usr/lib/python2.7/dist-packages/xen/remus/device.py", line 333, in postsuspend self.install() File "/usr/lib/python2.7/dist-packages/xen/remus/device.py", line 380, in install self.rth.talk(req.pack()) File "/usr/lib/python2.7/dist-packages/xen/remus/netlink.py", line 318, in talk self._rth.talk(req) IOError: error sending message My /etc/modules contains: sch_plug sch_prio sch_ingress cls_basic cls_tcindex cls_u32 act_mirred ifb I was under the impression that "ifb" and "sch_plug" were the key items required, but I'm not quite sure - all the online materials are a bit mixed in their explanations on this point. For further information, here's my system's modules: root@right:/home/eross# lsmod Module Size Used by ifb 12897 0 xt_physdev 12588 4 iptable_filter 12811 1 ip_tables 26996 1 iptable_filter x_tables 29757 3 xt_physdev,iptable_filter,ip_tables xen_netback 27434 0 [permanent] xen_blkback 23041 0 [permanent] xen_gntdev 17391 0 xen_evtchn 13221 3 xenfs 12986 1 xen_privcmd 13081 16 xenfs bridge 90447 0 stp 12977 1 bridge llc 14553 2 bridge,stp coretemp 13401 0 snd_hda_codec_via 46676 1 ghash_clmulni_intel 13221 0 cryptd 20404 1 ghash_clmulni_intel eeepc_wmi 13110 0 asus_wmi 24089 1 eeepc_wmi sparse_keymap 13891 1 asus_wmi microcode 22804 0 psmouse 95595 0 serio_raw 13216 0 ext2 72881 1 act_mirred 13039 1 mac_hid 13206 0 cls_u32 17138 1 cls_tcindex 13059 0 cls_basic 12947 0 sch_ingress 12867 1 wmi 19071 1 asus_wmi sch_prio 13153 0 sch_plug 12655 0 drbd 300253 4 snd_hda_intel 33492 0 lpc_ich 17062 0 snd_hda_codec 134213 2 snd_hda_codec_via,snd_hda_intel snd_hwdep 17699 1 snd_hda_codec snd_pcm 96668 2 snd_hda_intel,snd_hda_codec snd_timer 29426 1 snd_pcm snd 78921 6 snd_hda_codec_via,snd_hda_intel,snd_hda_codec,snd_hwdep,snd_pcm,snd_timer soundcore 15048 1 snd i915 520621 1 snd_page_alloc 18485 2 snd_hda_intel,snd_pcm mei 40691 0 drm_kms_helper 49113 1 i915 drm 288721 2 i915,drm_kms_helper lp 17760 0 parport 46346 1 lp i2c_algo_bit 13414 1 i915 video 19336 1 i915 r8169 61651 0 root@right:/home/eross# uname -a Linux right 3.5.0-23-generic #35-Ubuntu SMP Thu Jan 24 13:15:40 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux Thanks! Andrew --14dae9340f2d492a7704d606d51f Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Hi Shriram,

I had another question for you if you don= 9;t mind -

I've been experimenting with a Ubun= tu 12.10 dom0 running Xen 4.1.4 and using Remus with DRBD.

I'm writing it all up and will post up my findings on our bl= og as well... once I figure it out =3D).

I can run= Remus successfully now in fact, transitioning VMs from one test machine to= another with DRBD, but only when I use "--no-net".

If I run "remus -i 40 --no-net rt left" this = works.

If I run "remus -i 40 rt left", I= get the below:

WARNING: suspend event channe= l unavailable, falling back to slow xenstore signalling
PROF: suspending at 1361224385.607101
installing buffer on i= fb0... RTNETLINK answers: Invalid argument
xc: error: Suspend req= uest failed: Internal error
xc: error: Domain appears not to have= suspended: Internal error
PROF: resumed at 1361224385.618021

Traceback = (most recent call last):
=A0 File "/usr/bin/remus", lin= e 219, in <module>
=A0 =A0 run(cfg)
=A0 File &quo= t;/usr/bin/remus", line 205, in run
=A0 =A0 for buf in bufs:
=A0 File "/usr/bin/remus"= , line 142, in postsuspend
=A0 =A0 buf.postsuspend()
= =A0 File "/usr/lib/python2.7/dist-packages/xen/remus/device.py", = line 333, in postsuspend
=A0 =A0 self.install()
=A0 File "/usr/lib/python2.7/dis= t-packages/xen/remus/device.py", line 380, in install
=A0 = =A0 self.rth.talk(req.pack())
=A0 File "/usr/lib/python2.7/d= ist-packages/xen/remus/netlink.py", line 318, in talk
=A0 =A0 self._rth.talk(req)
IOError: error sending message

My /etc/modules contains:
sch_plug
sch_prio
sch_ingress
cls_basic
cls_t= cindex
cls_u32
act_mirred
ifb

<= div>I was under the impression that "ifb" and "sch_plug"= ; were the key items required, but I'm not quite sure - all the online = materials are a bit mixed in their explanations on this point.

For further information, here's my system's mod= ules:

root@right:/home/eross# lsmod
Module =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0Size =A0Used by
ifb = =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A012897 =A00=A0
xt_physdev =A0 =A0 =A0 =A0 =A0 =A0 12588 =A04=A0
iptable_fil= ter =A0 =A0 =A0 =A0 12811 =A01=A0
ip_tables =A0 =A0 =A0 =A0 =A0 = =A0 =A026996 =A01 iptable_filter
x_tables =A0 =A0 =A0 =A0 =A0 =A0= =A0 29757 =A03 xt_physdev,iptable_filter,ip_tables
xen_netback =A0 =A0 =A0 =A0 =A0 =A027434 =A00 [permanent]
xe= n_blkback =A0 =A0 =A0 =A0 =A0 =A023041 =A00 [permanent]
xen_gntde= v =A0 =A0 =A0 =A0 =A0 =A0 17391 =A00=A0
xen_evtchn =A0 =A0 =A0 = =A0 =A0 =A0 13221 =A03=A0
xenfs =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A012986 =A01=A0
xen_privcmd =A0 =A0 =A0 =A0 =A0 =A013081 =A016 xenfs
bridge = =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 90447 =A00=A0
stp =A0 =A0 =A0 =A0= =A0 =A0 =A0 =A0 =A0 =A012977 =A01 bridge
llc =A0 =A0 =A0 =A0 =A0= =A0 =A0 =A0 =A0 =A014553 =A02 bridge,stp
coretemp =A0 =A0 =A0 = =A0 =A0 =A0 =A0 13401 =A00=A0
snd_hda_codec_via =A0 =A0 =A046676 =A01=A0
ghash_clmulni_int= el =A0 =A013221 =A00=A0
cryptd =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 20= 404 =A01 ghash_clmulni_intel
eeepc_wmi =A0 =A0 =A0 =A0 =A0 =A0 = =A013110 =A00=A0
asus_wmi =A0 =A0 =A0 =A0 =A0 =A0 =A0 24089 =A01 = eeepc_wmi
sparse_keymap =A0 =A0 =A0 =A0 =A013891 =A01 asus_wmi
microco= de =A0 =A0 =A0 =A0 =A0 =A0 =A022804 =A00=A0
psmouse =A0 =A0 =A0 = =A0 =A0 =A0 =A0 =A095595 =A00=A0
serio_raw =A0 =A0 =A0 =A0 =A0 = =A0 =A013216 =A00=A0
ext2 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 728= 81 =A01=A0
act_mirred =A0 =A0 =A0 =A0 =A0 =A0 13039 =A01=A0
mac_hid =A0= =A0 =A0 =A0 =A0 =A0 =A0 =A013206 =A00=A0
cls_u32 =A0 =A0 =A0 =A0= =A0 =A0 =A0 =A017138 =A01=A0
cls_tcindex =A0 =A0 =A0 =A0 =A0 =A0= 13059 =A00=A0
cls_basic =A0 =A0 =A0 =A0 =A0 =A0 =A012947 =A00=A0<= /div>
sch_ingress =A0 =A0 =A0 =A0 =A0 =A012867 =A01=A0
wmi =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A019071 =A01 asus_wmi
sch_prio =A0 =A0 =A0 =A0 =A0 =A0 =A0 13153 =A00=A0
sch_plug = =A0 =A0 =A0 =A0 =A0 =A0 =A0 12655 =A00=A0
drbd =A0 =A0 =A0 =A0 = =A0 =A0 =A0 =A0 =A0300253 =A04=A0
snd_hda_intel =A0 =A0 =A0 =A0 = =A033492 =A00=A0
lpc_ich =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A017062 =A00=A0
snd_hda= _codec =A0 =A0 =A0 =A0 134213 =A02 snd_hda_codec_via,snd_hda_intel
snd_hwdep =A0 =A0 =A0 =A0 =A0 =A0 =A017699 =A01 snd_hda_codec
s= nd_pcm =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A096668 =A02 snd_hda_intel,snd_hda_code= c
snd_timer =A0 =A0 =A0 =A0 =A0 =A0 =A029426 =A01 snd_pcm
snd = =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A078921 =A06 snd_hda_codec_via,snd_hda= _intel,snd_hda_codec,snd_hwdep,snd_pcm,snd_timer
soundcore =A0 = =A0 =A0 =A0 =A0 =A0 =A015048 =A01 snd
i915 =A0 =A0 =A0 =A0 =A0 = =A0 =A0 =A0 =A0520621 =A01=A0
snd_page_alloc =A0 =A0 =A0 =A0 18485 =A02 snd_hda_intel,snd_pcm
<= div>mei =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A040691 =A00=A0
drm_= kms_helper =A0 =A0 =A0 =A0 49113 =A01 i915
drm =A0 =A0 =A0 =A0 = =A0 =A0 =A0 =A0 =A0 288721 =A02 i915,drm_kms_helper
lp =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 17760 =A00=A0
parport = =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A046346 =A01 lp
i2c_algo_bit =A0 =A0= =A0 =A0 =A0 13414 =A01 i915
video =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0 =A019336 =A01 i915
r8169 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A06= 1651 =A00=A0

root@right:/home/eross# uname -a
Linux right 3.5.0= -23-generic #35-Ubuntu SMP Thu Jan 24 13:15:40 UTC 2013 x86_64 x86_64 x86_6= 4 GNU/Linux

Thanks!
Andrew
--14dae9340f2d492a7704d606d51f-- --===============8414361374979157334== 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 --===============8414361374979157334==-- From xen-users-bounces@lists.xen.org Mon Feb 18 22:11:35 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 18 Feb 2013 22:11: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 1U7YvQ-0006DN-E3; Mon, 18 Feb 2013 22:11:04 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U7YvN-0006Cz-0m; Mon, 18 Feb 2013 22:11:02 +0000 Received: from [85.158.143.99:14584] by server-2.bemta-4.messagelabs.com id 26/C6-12656-4F6A2215; Mon, 18 Feb 2013 22:11:00 +0000 X-Env-Sender: agya.naila@gmail.com X-Msg-Ref: server-8.tower-216.messagelabs.com!1361225457!18290330!1 X-Originating-IP: [209.85.212.170] 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.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 20714 invoked from network); 18 Feb 2013 22:10:57 -0000 Received: from mail-wi0-f170.google.com (HELO mail-wi0-f170.google.com) (209.85.212.170) by server-8.tower-216.messagelabs.com with RC4-SHA encrypted SMTP; 18 Feb 2013 22:10:57 -0000 Received: by mail-wi0-f170.google.com with SMTP id hm11so4336841wib.5 for ; Mon, 18 Feb 2013 14:10:57 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=Okoqn2pB87OLKdFFDuNQYBrOJhtIK5Aga9qnWih1HO4=; b=MtYpoagMnSNRKVFEgU7EI9zc6NDNacvu2mE4+wwUAE+ujttkgIXIVF4p4SsTBDbT80 PcwMz8anhJaPnEWpxnETuJdqTpeE91iCJ+5yMEAwgl96WAiZzN0UQCg8+xEAzEPt80cR az3vyXdeOz/FhTXfLoKmbwWEHHIzVQareF7Jee2ZuK7oQQ6fLPgaHMpxbc5ZlR8iMoZ9 yEyLRP8Ahdibfv6265Ww66GCOdpEzuCZjsN730h/VePWawmFu0RH+yorWrwHk+jywrKL M488Uwl0PKXu3kkbCn5XFGQl8HWTjB9bRs/I+pIG9LhV4uy6Oxjggrn4l6uH6xYbJ9Sl FwZA== MIME-Version: 1.0 X-Received: by 10.194.94.40 with SMTP id cz8mr5703649wjb.15.1361224856940; Mon, 18 Feb 2013 14:00:56 -0800 (PST) Received: by 10.216.236.13 with HTTP; Mon, 18 Feb 2013 14:00:56 -0800 (PST) In-Reply-To: References: Date: Mon, 18 Feb 2013 23:00:56 +0100 Message-ID: From: agya naila To: rshriram@cs.ubc.ca Cc: "xen-users@lists.xen.org" , "xen-devel@lists.xen.org" Subject: Re: [Xen-users] [Xen-devel] Remus disk replication failed X-BeenThere: xen-users@lists.xen.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="===============5644870332814961597==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============5644870332814961597== Content-Type: multipart/alternative; boundary=047d7bb04c9a0eb1b904d606dc19 --047d7bb04c9a0eb1b904d606dc19 Content-Type: text/plain; charset=ISO-8859-1 On Mon, Feb 18, 2013 at 10:33 PM, Shriram Rajagopalan wrote: > Hi, > I suggest you read up on the DRBD setup documentation from the > drbd.org website. > The setup procedure is same. You can later flip to the remus > replication protocol by simply > changing the protocol type (C to D). > > I am comparing my configuration with drbd website, however I got this error : $ sudo drbdadm up drbd-vm *'D' is no valid protocol.* *Command 'drbdsetup 1 net ipv4:10.10.10.1:7789 ipv4:10.10.10.3:7789 D --set-defaults --create-device --rr-conflict=disconnect --after-sb-2pri=disconnect --after-sb-1pri=discard-secondary --after-sb-0pri=discard-younger-primary --allow-two-primaries --ko-count=4 --max-epoch-size=4096 --unplug-watermark=4096 --max-buffers=8192 --ping-timeout=20 --ping-int=3 --timeout=30' terminated with exit code 20* *drbdadm connect drbd-vm: exited with code 20* * * $ sudo drbd-overview 1:drbd-vm StandAlone Secondary/Unknown UpToDate/DUnknown r----s Thank you, Agya > thanks > shriram > > On Mon, Feb 18, 2013 at 4:11 PM, agya naila wrote: > > > > On Mon, Feb 18, 2013 at 9:08 PM, Shriram Rajagopalan > > > wrote: > >> > >> hi > > > > > > Thank you shriram. > > > >> > >> sorry for the delayed response. IIRC the blktap2 driver required for > >> tapdisk replication doesnt exist in the mainstream dom0 kernels, IIRC. > >> I havent used it in a long time myself. I suggest trying disk > >> replication with DRBD. > >> > > > > I am also found some information here > > http://osdir.com/ml/xen-users/2011-07/msg00653.html about blktap2 > problem on > > amd64 architecture. I have tried to install and configure the DRBD but > its > > didn't connect each other. > > I used drbd-8.3.11-remus and installed as follow > > > > cd /usr/src/ > > wget > > > http://remusha.wikidot.com/local--files/configuring-and-installing-remus/drbd-8.3.11-remus.tar.gz > > tar xzf drbd-8.3.9-remus.tar.gz > > chown -R root:root drbd-8.3-remus > > cd /usr/src/drbd-8.3-remus > > chmod 777 autogen.sh > > ./autogen.sh > > dpkg-buildpackage -b -uc > > cd /usr/src/drbd-8.3-remus/drbd > > make clean > > make > > make install > > cd /usr/src/ > > cp /usr/src/drbd-8.3-remus/scripts/global_common.conf.protoD > > /etc/drbd.d/global_common.conf > > cp /usr/src/drbd-8.3-remus/scripts/testvms_protoD.res > > /etc/drbd.d/SystemHA_protoD.res > > > > sudo apt-get install drbd8-utils > > > > from tutorial > http://remusha.wikidot.com/configuring-and-installing-remus > > > > My *.res configuration as follow : > > > > resource drbd-vm{ > > device /dev/drbd1; > > disk /dev/vgvoip/DomU; > > meta-disk internal; > > on machine1 { > > address 10.10.10.1:7789; > > } > > on machine2 { > > address 10.10.10.3:7789; > > } > > } > > > > and then I invoke command to create that meta > > > > drbdadm create-md drbd-vm > > > > However, when I try to make this configuration up by : > > > > drbdadm up drbd-vm > > > > Its come with error : > > > > $ sudo drbdadm up drbd-vm > > 1: Failure: (124) Device is attached to a disk (use detach first) > > Command 'drbdsetup 1 disk /dev/vgvoip/DomU /dev/vgvoip/DomU internal > > --set-defaults --create-device --fencing=dont-care --on-io-error=pass_on' > > terminated with exit code 10 > > > > If I run the > > > > $ sudo drbdadm detach drbd-vm > > > > Its come error > > > > $ sudo drbdadm detach drbd-vm > > 1: State change failed: (-2) Need access to UpToDate data > > Command 'drbdsetup 1 detach' terminated with exit code 17 > > > > Here the /proc/drbd on both machine > > > > Machine 1 > > > > $ sudo cat /proc/drbd > > version: 8.3.11 (api:88/proto:86-96) > > GIT-hash: 0de839cee13a4160eed6037c4bddd066645e23c5 build by root@machine1 > , > > 2013-02-18 18:49:57 > > > > 1: cs:StandAlone ro:Primary/Unknown ds:UpToDate/DUnknown r----s > > ns:0 nr:0 dw:0 dr:1712 al:0 bm:0 lo:0 pe:0 ua:0 ap:0 ep:1 wo:b def:0 > > chkpt:0 oos:10485404 > > > > > > Machine 2 > > > > $ sudo cat /proc/drbd > > version: 8.3.11 (api:88/proto:86-96) > > GIT-hash: 0de839cee13a4160eed6037c4bddd066645e23c5 build by root@machine2 > , > > 2013-02-18 19:26:57 > > > > 1: cs:StandAlone ro:Secondary/Unknown ds:Inconsistent/DUnknown r----s > > ns:0 nr:0 dw:0 dr:0 al:0 bm:0 lo:0 pe:0 ua:0 ap:0 ep:1 wo:b def:0 > > chkpt:0 oos:10485404 > > > > > > Do you have some hints? > > > > Thank you, > > > > > > Agya > > > > > >> thanks > >> shriram > >> > >> On Mon, Feb 18, 2013 at 5:38 AM, Hery Dian Septama > > >> wrote: > >> > Hello, Anyone have a clue? I have tried but still failed :( > >> > > >> > On Sat, Feb 16, 2013 at 6:56 PM, agya naila > >> > wrote: > >> >> > >> >> Dear all, > >> >> > >> >> I am configure my machine to run the remus disk replication. I am > using > >> >> xen 4.2.3 installed from sources and Ubuntu 12.04 64 bit both for > Dom0 > >> >> and > >> >> DomU. > >> >> I have install the blktap and its work properly with configuration > >> >> string > >> >> phy or tap2 like this : > >> >> disk = ['phy:/dev/vggroup/DomU,xvda,w'] > >> >> or > >> >> disk = ['tap2:tapdisk:aio:/dev/vggroup/DomU,xvda,w'] > >> >> > >> >> and remus command > >> >> > >> >> remus --no-net myvm mybackuphost > >> >> > >> >> > >> >> However when I change the string as suggested on remus pages to > enable > >> >> the > >> >> disk replication its still failed : > >> >> > >> >> name = "DomU" > >> >> memory = 1024 > >> >> disk = ['tap2:remus:10.10.10.3:8002|aio:/dev/vggroup/DomU,xvda,w'] > >> >> vif = ['ip=192.168.1.55,bridge=xenbr0'] > >> >> bootloader = "pygrub" > >> >> > >> >> with error messages : > >> >> > >> >> name1@machine1:~$ sudo xm create -c /etc/xen/DomU.cfg > >> >> Using config file "/etc/xen/DomU.cfg". > >> >> Error: ('create', '-aremus:10.10.10.3:8002|aio:/dev/vggroup/DomU') > >> >> failed > >> >> (512 ) > >> >> > >> >> and on the log file : > >> >> > >> >> > >> >> name1@machine1:~$ sudo sudo tail /var/log/xen/xend.log > >> >> mounted_vbd_uuid = dom0.create_vbd(vbd, disk); > >> >> File > >> >> "/usr/local/lib/python2.7/dist-packages/xen/xend/XendDomainInfo.py", > >> >> line > >> >> 3987, in create_vbd > >> >> devid = dev_control.createDevice(config) > >> >> File > >> >> > >> >> > "/usr/local/lib/python2.7/dist-packages/xen/xend/server/BlktapController.py", > >> >> line 174, in createDevice > >> >> device = TapdiskController.create(params, file) > >> >> File > >> >> > >> >> > "/usr/local/lib/python2.7/dist-packages/xen/xend/server/BlktapController.py", > >> >> line 286, in create > >> >> return TapdiskController.exc('create', '-a%s:%s' % (dtype, > image)) > >> >> File > >> >> > >> >> > "/usr/local/lib/python2.7/dist-packages/xen/xend/server/BlktapController.py", > >> >> line 233, in exc > >> >> (args, rc, out, err)) > >> >> TapdiskException: ('create', > >> >> '-aremus:10.10.10.3:8002|aio:/dev/vggroup/DomU') failed (512 ) > >> >> > >> >> Any hints and help would very appreciated. > >> >> > >> >> Regards, > >> >> > >> >> Agya > >> >> > >> >> > >> >> _______________________________________________ > >> >> Xen-devel mailing list > >> >> Xen-devel@lists.xen.org > >> >> http://lists.xen.org/xen-devel > >> >> > >> > > >> > > >> > _______________________________________________ > >> > Xen-devel mailing list > >> > Xen-devel@lists.xen.org > >> > http://lists.xen.org/xen-devel > >> > > > > > > --047d7bb04c9a0eb1b904d606dc19 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
On Mon, Feb 18, 2013 at 10:33 PM, Shriram Rajagopalan <rshriram@cs.u= bc.ca> wrote:
Hi,
=A0I suggest you read up on the DRBD setup documentation from the
drbd.org website.
=A0The setup procedure is same. You can later flip to the remus
replication protocol by simply
=A0changing the protocol type (C to D).

I am comparing my configuration with drbd website, however= I got this error :

$ sudo drbdadm up drbd-vm
'D' is no valid protocol.
Command 'drbdsetup 1 net = ipv4:10.10.10.1:7789 ipv4:10.10.10.3:7789 D --set-defaults --create-devi= ce --rr-conflict=3Ddisconnect --after-sb-2pri=3Ddisconnect --after-sb-1pri= =3Ddiscard-secondary --after-sb-0pri=3Ddiscard-younger-primary --allow-two-= primaries --ko-count=3D4 --max-epoch-size=3D4096 --unplug-watermark=3D4096 = --max-buffers=3D8192 --ping-timeout=3D20 --ping-int=3D3 --timeout=3D30'= terminated with exit code 20
drbdadm connect drbd-vm: exit= ed with code 20
=
$ sudo d= rbd-overview
=A0 = 1:drbd-vm =A0StandAlone Secondary/Unknown UpToDate/DUnknown r----s

Thank you,

Agya
=
=A0
thanks
shriram

On Mon, Feb 18, 2013 at 4:11 PM, agya naila <agya.naila@gmail.com> wrote:
>
> On Mon, Feb 18, 2013 at 9:08 PM, Shriram Rajagopalan <rshriram@cs.ubc.ca>
> wrote:
>>
>> hi
>
>
> Thank you shriram.
>
>>
>> =A0sorry for the delayed response. IIRC the blktap2 driver require= d for
>> tapdisk replication doesnt exist in the mainstream dom0 kernels, I= IRC.
>> =A0I havent used it in a long time myself. I suggest trying disk >> replication with DRBD.
>>
>
> I am also found some information here
> http://osdir.com/ml/xen-users/2011-07/msg00653.html about b= lktap2 problem on
> amd64 architecture. I have tried to install and configure the DRBD but= its
> didn't connect each other.
> I used drbd-8.3.11-remus and installed as follow
>
> cd /usr/src/
> wget
> http://remusha.wi= kidot.com/local--files/configuring-and-installing-remus/drbd-8.3.11-remus.t= ar.gz
> tar xzf drbd-8.3.9-remus.tar.gz
> chown -R root:root drbd-8.3-remus
> cd /usr/src/drbd-8.3-remus
> chmod 777 autogen.sh
> ./autogen.sh
> dpkg-buildpackage -b -uc
> cd /usr/src/drbd-8.3-remus/drbd
> make clean
> make
> make install
> cd /usr/src/
> cp /usr/src/drbd-8.3-remus/scripts/global_common.conf.protoD
> /etc/drbd.d/global_common.conf
> cp /usr/src/drbd-8.3-remus/scripts/testvms_protoD.res
> /etc/drbd.d/SystemHA_protoD.res
>
> sudo apt-get install drbd8-utils
>
> =A0from tutorial http://remusha.wikidot.com/configuring= -and-installing-remus
>
> My *.res configuration as follow :
>
> resource drbd-vm{
> =A0 device =A0 =A0/dev/drbd1;
> =A0 disk =A0 =A0 =A0/dev/vgvoip/DomU;
> =A0 meta-disk internal;
> =A0 on machine1 {
> =A0 =A0 address =A0 10.10.10.1:7789;
> =A0 }
> =A0 on machine2 {
> =A0 =A0 address =A0 10.10.10.3:7789;
> =A0 }
> }
>
> and then I invoke command to create that meta
>
> drbdadm create-md drbd-vm
>
> However, when I try to make this configuration up by :
>
> drbdadm up drbd-vm
>
> Its come with error :
>
> $ sudo drbdadm up drbd-vm
> 1: Failure: (124) Device is attached to a disk (use detach first)
> Command 'drbdsetup 1 disk /dev/vgvoip/DomU /dev/vgvoip/DomU intern= al
> --set-defaults --create-device --fencing=3Ddont-care --on-io-error=3Dp= ass_on'
> terminated with exit code 10
>
> If I run the
>
> $ sudo drbdadm detach drbd-vm
>
> Its come error
>
> $ sudo drbdadm detach drbd-vm
> 1: State change failed: (-2) Need access to UpToDate data
> Command 'drbdsetup 1 detach' terminated with exit code 17
>
> Here the /proc/drbd on both machine
>
> Machine 1
>
> $ sudo cat /proc/drbd
> version: 8.3.11 (api:88/proto:86-96)
> GIT-hash: 0de839cee13a4160eed6037c4bddd066645e23c5 build by root@machi= ne1,
> 2013-02-18 18:49:57
>
> =A01: cs:StandAlone ro:Primary/Unknown ds:UpToDate/DUnknown =A0 r----s=
> =A0 =A0 ns:0 nr:0 dw:0 dr:1712 al:0 bm:0 lo:0 pe:0 ua:0 ap:0 ep:1 wo:b= def:0
> chkpt:0 oos:10485404
>
>
> Machine 2
>
> $ sudo cat /proc/drbd
> version: 8.3.11 (api:88/proto:86-96)
> GIT-hash: 0de839cee13a4160eed6037c4bddd066645e23c5 build by root@machi= ne2,
> 2013-02-18 19:26:57
>
> =A01: cs:StandAlone ro:Secondary/Unknown ds:Inconsistent/DUnknown =A0 = r----s
> =A0 =A0 ns:0 nr:0 dw:0 dr:0 al:0 bm:0 lo:0 pe:0 ua:0 ap:0 ep:1 wo:b de= f:0
> chkpt:0 oos:10485404
>
>
> Do you have some hints?
>
> Thank you,
>
>
> Agya
>
>
>> thanks
>> shriram
>>
>> On Mon, Feb 18, 2013 at 5:38 AM, Hery Dian Septama <herydians@gmail.com>
>> wrote:
>> > Hello, Anyone have a clue? I have tried but still failed :( >> >
>> > On Sat, Feb 16, 2013 at 6:56 PM, agya naila <agya.naila@gmail.com>
>> > wrote:
>> >>
>> >> Dear all,
>> >>
>> >> I am configure my machine to run the remus disk replicati= on. I am using
>> >> xen 4.2.3 installed from sources and Ubuntu 12.04 64 bit = both for Dom0
>> >> and
>> >> DomU.
>> >> I have install the blktap and its work properly with conf= iguration
>> >> string
>> >> phy or tap2 like this :
>> >> disk =3D ['phy:/dev/vggroup/DomU,xvda,w']
>> >> or
>> >> disk =3D ['tap2:tapdisk:aio:/dev/vggroup/DomU,xvda,w&= #39;]
>> >>
>> >> and remus command
>> >>
>> >> remus --no-net myvm mybackuphost
>> >>
>> >>
>> >> However when I change the string as suggested on remus pa= ges to enable
>> >> the
>> >> disk replication its still failed :
>> >>
>> >> name =3D "DomU"
>> >> memory =3D 1024
>> >> disk =3D ['tap2:remus:10.10.10.3:8002|aio:/dev/vggrou= p/DomU,xvda,w']
>> >> vif =3D ['ip=3D192.168.1.55,bridge=3Dxenbr0']
>> >> bootloader =3D "pygrub"
>> >>
>> >> with error messages :
>> >>
>> >> name1@machine1:~$ sudo xm create -c /etc/xen/DomU.cfg
>> >> Using config file "/etc/xen/DomU.cfg".
>> >> Error: ('create', '-aremus:10.10.10.3:8002|ai= o:/dev/vggroup/DomU')
>> >> failed
>> >> (512 =A0)
>> >>
>> >> and on the log file :
>> >>
>> >>
>> >> name1@machine1:~$ sudo sudo tail /var/log/xen/xend.log >> >> =A0 =A0 mounted_vbd_uuid =3D dom0.create_vbd(vbd, disk);<= br> >> >> =A0 File
>> >> "/usr/local/lib/python2.7/dist-packages/xen/xend/Xen= dDomainInfo.py",
>> >> line
>> >> 3987, in create_vbd
>> >> =A0 =A0 devid =3D dev_control.createDevice(config)
>> >> =A0 File
>> >>
>> >> "/usr/local/lib/python2.7/dist-packages/xen/xend/ser= ver/BlktapController.py",
>> >> line 174, in createDevice
>> >> =A0 =A0 device =3D TapdiskController.create(params, file)=
>> >> =A0 File
>> >>
>> >> "/usr/local/lib/python2.7/dist-packages/xen/xend/ser= ver/BlktapController.py",
>> >> line 286, in create
>> >> =A0 =A0 return TapdiskController.exc('create', &#= 39;-a%s:%s' % (dtype, image))
>> >> =A0 File
>> >>
>> >> "/usr/local/lib/python2.7/dist-packages/xen/xend/ser= ver/BlktapController.py",
>> >> line 233, in exc
>> >> =A0 =A0 (args, rc, out, err))
>> >> TapdiskException: ('create',
>> >> '-aremus:10.10.10.3:8002|aio:/dev/vggroup/DomU') = failed (512 =A0)
>> >>
>> >> Any hints and help would very appreciated.
>> >>
>> >> Regards,
>> >>
>> >> Agya
>> >>
>> >>
>> >> _______________________________________________
>> >> Xen-devel mailing list
>> >> Xen-devel@list= s.xen.org
>> >> http://lists.xen.org/xen-devel
>> >>
>> >
>> >
>> > _______________________________________________
>> > Xen-devel mailing list
>> > Xen-devel@lists.xe= n.org
>> > = http://lists.xen.org/xen-devel
>> >
>
>

--047d7bb04c9a0eb1b904d606dc19-- --===============5644870332814961597== 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 --===============5644870332814961597==-- From xen-users-bounces@lists.xen.org Mon Feb 18 22:11:35 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 18 Feb 2013 22:11: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 1U7YvQ-0006DN-E3; Mon, 18 Feb 2013 22:11:04 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U7YvN-0006Cz-0m; Mon, 18 Feb 2013 22:11:02 +0000 Received: from [85.158.143.99:14584] by server-2.bemta-4.messagelabs.com id 26/C6-12656-4F6A2215; Mon, 18 Feb 2013 22:11:00 +0000 X-Env-Sender: agya.naila@gmail.com X-Msg-Ref: server-8.tower-216.messagelabs.com!1361225457!18290330!1 X-Originating-IP: [209.85.212.170] 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.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 20714 invoked from network); 18 Feb 2013 22:10:57 -0000 Received: from mail-wi0-f170.google.com (HELO mail-wi0-f170.google.com) (209.85.212.170) by server-8.tower-216.messagelabs.com with RC4-SHA encrypted SMTP; 18 Feb 2013 22:10:57 -0000 Received: by mail-wi0-f170.google.com with SMTP id hm11so4336841wib.5 for ; Mon, 18 Feb 2013 14:10:57 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=Okoqn2pB87OLKdFFDuNQYBrOJhtIK5Aga9qnWih1HO4=; b=MtYpoagMnSNRKVFEgU7EI9zc6NDNacvu2mE4+wwUAE+ujttkgIXIVF4p4SsTBDbT80 PcwMz8anhJaPnEWpxnETuJdqTpeE91iCJ+5yMEAwgl96WAiZzN0UQCg8+xEAzEPt80cR az3vyXdeOz/FhTXfLoKmbwWEHHIzVQareF7Jee2ZuK7oQQ6fLPgaHMpxbc5ZlR8iMoZ9 yEyLRP8Ahdibfv6265Ww66GCOdpEzuCZjsN730h/VePWawmFu0RH+yorWrwHk+jywrKL M488Uwl0PKXu3kkbCn5XFGQl8HWTjB9bRs/I+pIG9LhV4uy6Oxjggrn4l6uH6xYbJ9Sl FwZA== MIME-Version: 1.0 X-Received: by 10.194.94.40 with SMTP id cz8mr5703649wjb.15.1361224856940; Mon, 18 Feb 2013 14:00:56 -0800 (PST) Received: by 10.216.236.13 with HTTP; Mon, 18 Feb 2013 14:00:56 -0800 (PST) In-Reply-To: References: Date: Mon, 18 Feb 2013 23:00:56 +0100 Message-ID: From: agya naila To: rshriram@cs.ubc.ca Cc: "xen-users@lists.xen.org" , "xen-devel@lists.xen.org" Subject: Re: [Xen-users] [Xen-devel] Remus disk replication failed X-BeenThere: xen-users@lists.xen.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="===============5644870332814961597==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============5644870332814961597== Content-Type: multipart/alternative; boundary=047d7bb04c9a0eb1b904d606dc19 --047d7bb04c9a0eb1b904d606dc19 Content-Type: text/plain; charset=ISO-8859-1 On Mon, Feb 18, 2013 at 10:33 PM, Shriram Rajagopalan wrote: > Hi, > I suggest you read up on the DRBD setup documentation from the > drbd.org website. > The setup procedure is same. You can later flip to the remus > replication protocol by simply > changing the protocol type (C to D). > > I am comparing my configuration with drbd website, however I got this error : $ sudo drbdadm up drbd-vm *'D' is no valid protocol.* *Command 'drbdsetup 1 net ipv4:10.10.10.1:7789 ipv4:10.10.10.3:7789 D --set-defaults --create-device --rr-conflict=disconnect --after-sb-2pri=disconnect --after-sb-1pri=discard-secondary --after-sb-0pri=discard-younger-primary --allow-two-primaries --ko-count=4 --max-epoch-size=4096 --unplug-watermark=4096 --max-buffers=8192 --ping-timeout=20 --ping-int=3 --timeout=30' terminated with exit code 20* *drbdadm connect drbd-vm: exited with code 20* * * $ sudo drbd-overview 1:drbd-vm StandAlone Secondary/Unknown UpToDate/DUnknown r----s Thank you, Agya > thanks > shriram > > On Mon, Feb 18, 2013 at 4:11 PM, agya naila wrote: > > > > On Mon, Feb 18, 2013 at 9:08 PM, Shriram Rajagopalan > > > wrote: > >> > >> hi > > > > > > Thank you shriram. > > > >> > >> sorry for the delayed response. IIRC the blktap2 driver required for > >> tapdisk replication doesnt exist in the mainstream dom0 kernels, IIRC. > >> I havent used it in a long time myself. I suggest trying disk > >> replication with DRBD. > >> > > > > I am also found some information here > > http://osdir.com/ml/xen-users/2011-07/msg00653.html about blktap2 > problem on > > amd64 architecture. I have tried to install and configure the DRBD but > its > > didn't connect each other. > > I used drbd-8.3.11-remus and installed as follow > > > > cd /usr/src/ > > wget > > > http://remusha.wikidot.com/local--files/configuring-and-installing-remus/drbd-8.3.11-remus.tar.gz > > tar xzf drbd-8.3.9-remus.tar.gz > > chown -R root:root drbd-8.3-remus > > cd /usr/src/drbd-8.3-remus > > chmod 777 autogen.sh > > ./autogen.sh > > dpkg-buildpackage -b -uc > > cd /usr/src/drbd-8.3-remus/drbd > > make clean > > make > > make install > > cd /usr/src/ > > cp /usr/src/drbd-8.3-remus/scripts/global_common.conf.protoD > > /etc/drbd.d/global_common.conf > > cp /usr/src/drbd-8.3-remus/scripts/testvms_protoD.res > > /etc/drbd.d/SystemHA_protoD.res > > > > sudo apt-get install drbd8-utils > > > > from tutorial > http://remusha.wikidot.com/configuring-and-installing-remus > > > > My *.res configuration as follow : > > > > resource drbd-vm{ > > device /dev/drbd1; > > disk /dev/vgvoip/DomU; > > meta-disk internal; > > on machine1 { > > address 10.10.10.1:7789; > > } > > on machine2 { > > address 10.10.10.3:7789; > > } > > } > > > > and then I invoke command to create that meta > > > > drbdadm create-md drbd-vm > > > > However, when I try to make this configuration up by : > > > > drbdadm up drbd-vm > > > > Its come with error : > > > > $ sudo drbdadm up drbd-vm > > 1: Failure: (124) Device is attached to a disk (use detach first) > > Command 'drbdsetup 1 disk /dev/vgvoip/DomU /dev/vgvoip/DomU internal > > --set-defaults --create-device --fencing=dont-care --on-io-error=pass_on' > > terminated with exit code 10 > > > > If I run the > > > > $ sudo drbdadm detach drbd-vm > > > > Its come error > > > > $ sudo drbdadm detach drbd-vm > > 1: State change failed: (-2) Need access to UpToDate data > > Command 'drbdsetup 1 detach' terminated with exit code 17 > > > > Here the /proc/drbd on both machine > > > > Machine 1 > > > > $ sudo cat /proc/drbd > > version: 8.3.11 (api:88/proto:86-96) > > GIT-hash: 0de839cee13a4160eed6037c4bddd066645e23c5 build by root@machine1 > , > > 2013-02-18 18:49:57 > > > > 1: cs:StandAlone ro:Primary/Unknown ds:UpToDate/DUnknown r----s > > ns:0 nr:0 dw:0 dr:1712 al:0 bm:0 lo:0 pe:0 ua:0 ap:0 ep:1 wo:b def:0 > > chkpt:0 oos:10485404 > > > > > > Machine 2 > > > > $ sudo cat /proc/drbd > > version: 8.3.11 (api:88/proto:86-96) > > GIT-hash: 0de839cee13a4160eed6037c4bddd066645e23c5 build by root@machine2 > , > > 2013-02-18 19:26:57 > > > > 1: cs:StandAlone ro:Secondary/Unknown ds:Inconsistent/DUnknown r----s > > ns:0 nr:0 dw:0 dr:0 al:0 bm:0 lo:0 pe:0 ua:0 ap:0 ep:1 wo:b def:0 > > chkpt:0 oos:10485404 > > > > > > Do you have some hints? > > > > Thank you, > > > > > > Agya > > > > > >> thanks > >> shriram > >> > >> On Mon, Feb 18, 2013 at 5:38 AM, Hery Dian Septama > > >> wrote: > >> > Hello, Anyone have a clue? I have tried but still failed :( > >> > > >> > On Sat, Feb 16, 2013 at 6:56 PM, agya naila > >> > wrote: > >> >> > >> >> Dear all, > >> >> > >> >> I am configure my machine to run the remus disk replication. I am > using > >> >> xen 4.2.3 installed from sources and Ubuntu 12.04 64 bit both for > Dom0 > >> >> and > >> >> DomU. > >> >> I have install the blktap and its work properly with configuration > >> >> string > >> >> phy or tap2 like this : > >> >> disk = ['phy:/dev/vggroup/DomU,xvda,w'] > >> >> or > >> >> disk = ['tap2:tapdisk:aio:/dev/vggroup/DomU,xvda,w'] > >> >> > >> >> and remus command > >> >> > >> >> remus --no-net myvm mybackuphost > >> >> > >> >> > >> >> However when I change the string as suggested on remus pages to > enable > >> >> the > >> >> disk replication its still failed : > >> >> > >> >> name = "DomU" > >> >> memory = 1024 > >> >> disk = ['tap2:remus:10.10.10.3:8002|aio:/dev/vggroup/DomU,xvda,w'] > >> >> vif = ['ip=192.168.1.55,bridge=xenbr0'] > >> >> bootloader = "pygrub" > >> >> > >> >> with error messages : > >> >> > >> >> name1@machine1:~$ sudo xm create -c /etc/xen/DomU.cfg > >> >> Using config file "/etc/xen/DomU.cfg". > >> >> Error: ('create', '-aremus:10.10.10.3:8002|aio:/dev/vggroup/DomU') > >> >> failed > >> >> (512 ) > >> >> > >> >> and on the log file : > >> >> > >> >> > >> >> name1@machine1:~$ sudo sudo tail /var/log/xen/xend.log > >> >> mounted_vbd_uuid = dom0.create_vbd(vbd, disk); > >> >> File > >> >> "/usr/local/lib/python2.7/dist-packages/xen/xend/XendDomainInfo.py", > >> >> line > >> >> 3987, in create_vbd > >> >> devid = dev_control.createDevice(config) > >> >> File > >> >> > >> >> > "/usr/local/lib/python2.7/dist-packages/xen/xend/server/BlktapController.py", > >> >> line 174, in createDevice > >> >> device = TapdiskController.create(params, file) > >> >> File > >> >> > >> >> > "/usr/local/lib/python2.7/dist-packages/xen/xend/server/BlktapController.py", > >> >> line 286, in create > >> >> return TapdiskController.exc('create', '-a%s:%s' % (dtype, > image)) > >> >> File > >> >> > >> >> > "/usr/local/lib/python2.7/dist-packages/xen/xend/server/BlktapController.py", > >> >> line 233, in exc > >> >> (args, rc, out, err)) > >> >> TapdiskException: ('create', > >> >> '-aremus:10.10.10.3:8002|aio:/dev/vggroup/DomU') failed (512 ) > >> >> > >> >> Any hints and help would very appreciated. > >> >> > >> >> Regards, > >> >> > >> >> Agya > >> >> > >> >> > >> >> _______________________________________________ > >> >> Xen-devel mailing list > >> >> Xen-devel@lists.xen.org > >> >> http://lists.xen.org/xen-devel > >> >> > >> > > >> > > >> > _______________________________________________ > >> > Xen-devel mailing list > >> > Xen-devel@lists.xen.org > >> > http://lists.xen.org/xen-devel > >> > > > > > > --047d7bb04c9a0eb1b904d606dc19 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
On Mon, Feb 18, 2013 at 10:33 PM, Shriram Rajagopalan <rshriram@cs.u= bc.ca> wrote:
Hi,
=A0I suggest you read up on the DRBD setup documentation from the
drbd.org website.
=A0The setup procedure is same. You can later flip to the remus
replication protocol by simply
=A0changing the protocol type (C to D).

I am comparing my configuration with drbd website, however= I got this error :

$ sudo drbdadm up drbd-vm
'D' is no valid protocol.
Command 'drbdsetup 1 net = ipv4:10.10.10.1:7789 ipv4:10.10.10.3:7789 D --set-defaults --create-devi= ce --rr-conflict=3Ddisconnect --after-sb-2pri=3Ddisconnect --after-sb-1pri= =3Ddiscard-secondary --after-sb-0pri=3Ddiscard-younger-primary --allow-two-= primaries --ko-count=3D4 --max-epoch-size=3D4096 --unplug-watermark=3D4096 = --max-buffers=3D8192 --ping-timeout=3D20 --ping-int=3D3 --timeout=3D30'= terminated with exit code 20
drbdadm connect drbd-vm: exit= ed with code 20
=
$ sudo d= rbd-overview
=A0 = 1:drbd-vm =A0StandAlone Secondary/Unknown UpToDate/DUnknown r----s

Thank you,

Agya
=
=A0
thanks
shriram

On Mon, Feb 18, 2013 at 4:11 PM, agya naila <agya.naila@gmail.com> wrote:
>
> On Mon, Feb 18, 2013 at 9:08 PM, Shriram Rajagopalan <rshriram@cs.ubc.ca>
> wrote:
>>
>> hi
>
>
> Thank you shriram.
>
>>
>> =A0sorry for the delayed response. IIRC the blktap2 driver require= d for
>> tapdisk replication doesnt exist in the mainstream dom0 kernels, I= IRC.
>> =A0I havent used it in a long time myself. I suggest trying disk >> replication with DRBD.
>>
>
> I am also found some information here
> http://osdir.com/ml/xen-users/2011-07/msg00653.html about b= lktap2 problem on
> amd64 architecture. I have tried to install and configure the DRBD but= its
> didn't connect each other.
> I used drbd-8.3.11-remus and installed as follow
>
> cd /usr/src/
> wget
> http://remusha.wi= kidot.com/local--files/configuring-and-installing-remus/drbd-8.3.11-remus.t= ar.gz
> tar xzf drbd-8.3.9-remus.tar.gz
> chown -R root:root drbd-8.3-remus
> cd /usr/src/drbd-8.3-remus
> chmod 777 autogen.sh
> ./autogen.sh
> dpkg-buildpackage -b -uc
> cd /usr/src/drbd-8.3-remus/drbd
> make clean
> make
> make install
> cd /usr/src/
> cp /usr/src/drbd-8.3-remus/scripts/global_common.conf.protoD
> /etc/drbd.d/global_common.conf
> cp /usr/src/drbd-8.3-remus/scripts/testvms_protoD.res
> /etc/drbd.d/SystemHA_protoD.res
>
> sudo apt-get install drbd8-utils
>
> =A0from tutorial http://remusha.wikidot.com/configuring= -and-installing-remus
>
> My *.res configuration as follow :
>
> resource drbd-vm{
> =A0 device =A0 =A0/dev/drbd1;
> =A0 disk =A0 =A0 =A0/dev/vgvoip/DomU;
> =A0 meta-disk internal;
> =A0 on machine1 {
> =A0 =A0 address =A0 10.10.10.1:7789;
> =A0 }
> =A0 on machine2 {
> =A0 =A0 address =A0 10.10.10.3:7789;
> =A0 }
> }
>
> and then I invoke command to create that meta
>
> drbdadm create-md drbd-vm
>
> However, when I try to make this configuration up by :
>
> drbdadm up drbd-vm
>
> Its come with error :
>
> $ sudo drbdadm up drbd-vm
> 1: Failure: (124) Device is attached to a disk (use detach first)
> Command 'drbdsetup 1 disk /dev/vgvoip/DomU /dev/vgvoip/DomU intern= al
> --set-defaults --create-device --fencing=3Ddont-care --on-io-error=3Dp= ass_on'
> terminated with exit code 10
>
> If I run the
>
> $ sudo drbdadm detach drbd-vm
>
> Its come error
>
> $ sudo drbdadm detach drbd-vm
> 1: State change failed: (-2) Need access to UpToDate data
> Command 'drbdsetup 1 detach' terminated with exit code 17
>
> Here the /proc/drbd on both machine
>
> Machine 1
>
> $ sudo cat /proc/drbd
> version: 8.3.11 (api:88/proto:86-96)
> GIT-hash: 0de839cee13a4160eed6037c4bddd066645e23c5 build by root@machi= ne1,
> 2013-02-18 18:49:57
>
> =A01: cs:StandAlone ro:Primary/Unknown ds:UpToDate/DUnknown =A0 r----s=
> =A0 =A0 ns:0 nr:0 dw:0 dr:1712 al:0 bm:0 lo:0 pe:0 ua:0 ap:0 ep:1 wo:b= def:0
> chkpt:0 oos:10485404
>
>
> Machine 2
>
> $ sudo cat /proc/drbd
> version: 8.3.11 (api:88/proto:86-96)
> GIT-hash: 0de839cee13a4160eed6037c4bddd066645e23c5 build by root@machi= ne2,
> 2013-02-18 19:26:57
>
> =A01: cs:StandAlone ro:Secondary/Unknown ds:Inconsistent/DUnknown =A0 = r----s
> =A0 =A0 ns:0 nr:0 dw:0 dr:0 al:0 bm:0 lo:0 pe:0 ua:0 ap:0 ep:1 wo:b de= f:0
> chkpt:0 oos:10485404
>
>
> Do you have some hints?
>
> Thank you,
>
>
> Agya
>
>
>> thanks
>> shriram
>>
>> On Mon, Feb 18, 2013 at 5:38 AM, Hery Dian Septama <herydians@gmail.com>
>> wrote:
>> > Hello, Anyone have a clue? I have tried but still failed :( >> >
>> > On Sat, Feb 16, 2013 at 6:56 PM, agya naila <agya.naila@gmail.com>
>> > wrote:
>> >>
>> >> Dear all,
>> >>
>> >> I am configure my machine to run the remus disk replicati= on. I am using
>> >> xen 4.2.3 installed from sources and Ubuntu 12.04 64 bit = both for Dom0
>> >> and
>> >> DomU.
>> >> I have install the blktap and its work properly with conf= iguration
>> >> string
>> >> phy or tap2 like this :
>> >> disk =3D ['phy:/dev/vggroup/DomU,xvda,w']
>> >> or
>> >> disk =3D ['tap2:tapdisk:aio:/dev/vggroup/DomU,xvda,w&= #39;]
>> >>
>> >> and remus command
>> >>
>> >> remus --no-net myvm mybackuphost
>> >>
>> >>
>> >> However when I change the string as suggested on remus pa= ges to enable
>> >> the
>> >> disk replication its still failed :
>> >>
>> >> name =3D "DomU"
>> >> memory =3D 1024
>> >> disk =3D ['tap2:remus:10.10.10.3:8002|aio:/dev/vggrou= p/DomU,xvda,w']
>> >> vif =3D ['ip=3D192.168.1.55,bridge=3Dxenbr0']
>> >> bootloader =3D "pygrub"
>> >>
>> >> with error messages :
>> >>
>> >> name1@machine1:~$ sudo xm create -c /etc/xen/DomU.cfg
>> >> Using config file "/etc/xen/DomU.cfg".
>> >> Error: ('create', '-aremus:10.10.10.3:8002|ai= o:/dev/vggroup/DomU')
>> >> failed
>> >> (512 =A0)
>> >>
>> >> and on the log file :
>> >>
>> >>
>> >> name1@machine1:~$ sudo sudo tail /var/log/xen/xend.log >> >> =A0 =A0 mounted_vbd_uuid =3D dom0.create_vbd(vbd, disk);<= br> >> >> =A0 File
>> >> "/usr/local/lib/python2.7/dist-packages/xen/xend/Xen= dDomainInfo.py",
>> >> line
>> >> 3987, in create_vbd
>> >> =A0 =A0 devid =3D dev_control.createDevice(config)
>> >> =A0 File
>> >>
>> >> "/usr/local/lib/python2.7/dist-packages/xen/xend/ser= ver/BlktapController.py",
>> >> line 174, in createDevice
>> >> =A0 =A0 device =3D TapdiskController.create(params, file)=
>> >> =A0 File
>> >>
>> >> "/usr/local/lib/python2.7/dist-packages/xen/xend/ser= ver/BlktapController.py",
>> >> line 286, in create
>> >> =A0 =A0 return TapdiskController.exc('create', &#= 39;-a%s:%s' % (dtype, image))
>> >> =A0 File
>> >>
>> >> "/usr/local/lib/python2.7/dist-packages/xen/xend/ser= ver/BlktapController.py",
>> >> line 233, in exc
>> >> =A0 =A0 (args, rc, out, err))
>> >> TapdiskException: ('create',
>> >> '-aremus:10.10.10.3:8002|aio:/dev/vggroup/DomU') = failed (512 =A0)
>> >>
>> >> Any hints and help would very appreciated.
>> >>
>> >> Regards,
>> >>
>> >> Agya
>> >>
>> >>
>> >> _______________________________________________
>> >> Xen-devel mailing list
>> >> Xen-devel@list= s.xen.org
>> >> http://lists.xen.org/xen-devel
>> >>
>> >
>> >
>> > _______________________________________________
>> > Xen-devel mailing list
>> > Xen-devel@lists.xe= n.org
>> > = http://lists.xen.org/xen-devel
>> >
>
>

--047d7bb04c9a0eb1b904d606dc19-- --===============5644870332814961597== 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 --===============5644870332814961597==-- From xen-users-bounces@lists.xen.org Mon Feb 18 22:14:27 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 18 Feb 2013 22:14: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 1U7YyD-0006aQ-A1; Mon, 18 Feb 2013 22:13:57 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U7YyB-0006a6-Gc; Mon, 18 Feb 2013 22:13:55 +0000 Received: from [85.158.143.99:26416] by server-2.bemta-4.messagelabs.com id A0/B7-12656-2A7A2215; Mon, 18 Feb 2013 22:13:54 +0000 X-Env-Sender: agya.naila@gmail.com X-Msg-Ref: server-13.tower-216.messagelabs.com!1361225628!27150695!1 X-Originating-IP: [74.125.82.180] 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.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 28846 invoked from network); 18 Feb 2013 22:13:49 -0000 Received: from mail-we0-f180.google.com (HELO mail-we0-f180.google.com) (74.125.82.180) by server-13.tower-216.messagelabs.com with RC4-SHA encrypted SMTP; 18 Feb 2013 22:13:49 -0000 Received: by mail-we0-f180.google.com with SMTP id k14so5012206wer.39 for ; Mon, 18 Feb 2013 14:13:48 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=p4g1tH8Rx62BX/0trQmexP0fgMXLXkZBzl1+42FIjbg=; b=nVB40bgxjmjErd9H5guGHrtiEoyrcD17O4DbKD+Xv2zwfy0JwlG72Mj4hNZiQo4VwL /vMYVqJZ7XSoQ96HK4qEcoJ/PxBTBFZ9sRjLjkyUDdjq7728v+eHRFCbAB0SBTPhAt0+ sLj/yxV75drCecMAwYeT/NT717NAS0/CL9h1SidjBYc+J/gf4L+Hc5z8Yuex6xPrAkTX RlU3pU+4WwEwXMRLBKjU/Zv6qAdUxYcJs9bSZ3khbh9cHLhzdLt8tjHMQ7Mp1Ta0NJ7C IEVa8XQEFORExunPByNJvwZDYlBcJgYaaSxE/tikydw5U5h0bWHYG/KAWAH3RoJ8eLAD Ndkg== MIME-Version: 1.0 X-Received: by 10.180.98.232 with SMTP id el8mr19975098wib.22.1361225628717; Mon, 18 Feb 2013 14:13:48 -0800 (PST) Received: by 10.216.236.13 with HTTP; Mon, 18 Feb 2013 14:13:48 -0800 (PST) In-Reply-To: References: Date: Mon, 18 Feb 2013 23:13:48 +0100 Message-ID: From: agya naila To: rshriram@cs.ubc.ca Cc: "xen-users@lists.xen.org" , "xen-devel@lists.xen.org" Subject: Re: [Xen-users] [Xen-devel] Remus disk replication failed X-BeenThere: xen-users@lists.xen.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="===============6194876638353693985==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============6194876638353693985== Content-Type: multipart/alternative; boundary=f46d0442885e0f10fe04d6070a66 --f46d0442885e0f10fe04d6070a66 Content-Type: text/plain; charset=ISO-8859-1 I forgot to told that its work with protocol C $ sudo drbd-overview 1:drbd-vm SyncTarget Secondary/Secondary Inconsistent/UpToDate C r----- [=>..................] sync'ed: 12.0% (9016/10236)M $ sudo drbd-overview 1:drbd-vm Connected Secondary/Secondary UpToDate/UpToDate C r----- On Mon, Feb 18, 2013 at 11:00 PM, agya naila wrote: > On Mon, Feb 18, 2013 at 10:33 PM, Shriram Rajagopalan wrote: > >> Hi, >> I suggest you read up on the DRBD setup documentation from the >> drbd.org website. >> The setup procedure is same. You can later flip to the remus >> replication protocol by simply >> changing the protocol type (C to D). >> >> I am comparing my configuration with drbd website, however I got this > error : > > $ sudo drbdadm up drbd-vm > *'D' is no valid protocol.* > *Command 'drbdsetup 1 net ipv4:10.10.10.1:7789 ipv4:10.10.10.3:7789 D > --set-defaults --create-device --rr-conflict=disconnect > --after-sb-2pri=disconnect --after-sb-1pri=discard-secondary > --after-sb-0pri=discard-younger-primary --allow-two-primaries --ko-count=4 > --max-epoch-size=4096 --unplug-watermark=4096 --max-buffers=8192 > --ping-timeout=20 --ping-int=3 --timeout=30' terminated with exit code 20* > *drbdadm connect drbd-vm: exited with code 20* > * > * > $ sudo drbd-overview > 1:drbd-vm StandAlone Secondary/Unknown UpToDate/DUnknown r----s > > Thank you, > > Agya > > > >> thanks >> shriram >> >> On Mon, Feb 18, 2013 at 4:11 PM, agya naila wrote: >> > >> > On Mon, Feb 18, 2013 at 9:08 PM, Shriram Rajagopalan < >> rshriram@cs.ubc.ca> >> > wrote: >> >> >> >> hi >> > >> > >> > Thank you shriram. >> > >> >> >> >> sorry for the delayed response. IIRC the blktap2 driver required for >> >> tapdisk replication doesnt exist in the mainstream dom0 kernels, IIRC. >> >> I havent used it in a long time myself. I suggest trying disk >> >> replication with DRBD. >> >> >> > >> > I am also found some information here >> > http://osdir.com/ml/xen-users/2011-07/msg00653.html about blktap2 >> problem on >> > amd64 architecture. I have tried to install and configure the DRBD but >> its >> > didn't connect each other. >> > I used drbd-8.3.11-remus and installed as follow >> > >> > cd /usr/src/ >> > wget >> > >> http://remusha.wikidot.com/local--files/configuring-and-installing-remus/drbd-8.3.11-remus.tar.gz >> > tar xzf drbd-8.3.9-remus.tar.gz >> > chown -R root:root drbd-8.3-remus >> > cd /usr/src/drbd-8.3-remus >> > chmod 777 autogen.sh >> > ./autogen.sh >> > dpkg-buildpackage -b -uc >> > cd /usr/src/drbd-8.3-remus/drbd >> > make clean >> > make >> > make install >> > cd /usr/src/ >> > cp /usr/src/drbd-8.3-remus/scripts/global_common.conf.protoD >> > /etc/drbd.d/global_common.conf >> > cp /usr/src/drbd-8.3-remus/scripts/testvms_protoD.res >> > /etc/drbd.d/SystemHA_protoD.res >> > >> > sudo apt-get install drbd8-utils >> > >> > from tutorial >> http://remusha.wikidot.com/configuring-and-installing-remus >> > >> > My *.res configuration as follow : >> > >> > resource drbd-vm{ >> > device /dev/drbd1; >> > disk /dev/vgvoip/DomU; >> > meta-disk internal; >> > on machine1 { >> > address 10.10.10.1:7789; >> > } >> > on machine2 { >> > address 10.10.10.3:7789; >> > } >> > } >> > >> > and then I invoke command to create that meta >> > >> > drbdadm create-md drbd-vm >> > >> > However, when I try to make this configuration up by : >> > >> > drbdadm up drbd-vm >> > >> > Its come with error : >> > >> > $ sudo drbdadm up drbd-vm >> > 1: Failure: (124) Device is attached to a disk (use detach first) >> > Command 'drbdsetup 1 disk /dev/vgvoip/DomU /dev/vgvoip/DomU internal >> > --set-defaults --create-device --fencing=dont-care >> --on-io-error=pass_on' >> > terminated with exit code 10 >> > >> > If I run the >> > >> > $ sudo drbdadm detach drbd-vm >> > >> > Its come error >> > >> > $ sudo drbdadm detach drbd-vm >> > 1: State change failed: (-2) Need access to UpToDate data >> > Command 'drbdsetup 1 detach' terminated with exit code 17 >> > >> > Here the /proc/drbd on both machine >> > >> > Machine 1 >> > >> > $ sudo cat /proc/drbd >> > version: 8.3.11 (api:88/proto:86-96) >> > GIT-hash: 0de839cee13a4160eed6037c4bddd066645e23c5 build by >> root@machine1, >> > 2013-02-18 18:49:57 >> > >> > 1: cs:StandAlone ro:Primary/Unknown ds:UpToDate/DUnknown r----s >> > ns:0 nr:0 dw:0 dr:1712 al:0 bm:0 lo:0 pe:0 ua:0 ap:0 ep:1 wo:b def:0 >> > chkpt:0 oos:10485404 >> > >> > >> > Machine 2 >> > >> > $ sudo cat /proc/drbd >> > version: 8.3.11 (api:88/proto:86-96) >> > GIT-hash: 0de839cee13a4160eed6037c4bddd066645e23c5 build by >> root@machine2, >> > 2013-02-18 19:26:57 >> > >> > 1: cs:StandAlone ro:Secondary/Unknown ds:Inconsistent/DUnknown r----s >> > ns:0 nr:0 dw:0 dr:0 al:0 bm:0 lo:0 pe:0 ua:0 ap:0 ep:1 wo:b def:0 >> > chkpt:0 oos:10485404 >> > >> > >> > Do you have some hints? >> > >> > Thank you, >> > >> > >> > Agya >> > >> > >> >> thanks >> >> shriram >> >> >> >> On Mon, Feb 18, 2013 at 5:38 AM, Hery Dian Septama < >> herydians@gmail.com> >> >> wrote: >> >> > Hello, Anyone have a clue? I have tried but still failed :( >> >> > >> >> > On Sat, Feb 16, 2013 at 6:56 PM, agya naila >> >> > wrote: >> >> >> >> >> >> Dear all, >> >> >> >> >> >> I am configure my machine to run the remus disk replication. I am >> using >> >> >> xen 4.2.3 installed from sources and Ubuntu 12.04 64 bit both for >> Dom0 >> >> >> and >> >> >> DomU. >> >> >> I have install the blktap and its work properly with configuration >> >> >> string >> >> >> phy or tap2 like this : >> >> >> disk = ['phy:/dev/vggroup/DomU,xvda,w'] >> >> >> or >> >> >> disk = ['tap2:tapdisk:aio:/dev/vggroup/DomU,xvda,w'] >> >> >> >> >> >> and remus command >> >> >> >> >> >> remus --no-net myvm mybackuphost >> >> >> >> >> >> >> >> >> However when I change the string as suggested on remus pages to >> enable >> >> >> the >> >> >> disk replication its still failed : >> >> >> >> >> >> name = "DomU" >> >> >> memory = 1024 >> >> >> disk = ['tap2:remus:10.10.10.3:8002|aio:/dev/vggroup/DomU,xvda,w'] >> >> >> vif = ['ip=192.168.1.55,bridge=xenbr0'] >> >> >> bootloader = "pygrub" >> >> >> >> >> >> with error messages : >> >> >> >> >> >> name1@machine1:~$ sudo xm create -c /etc/xen/DomU.cfg >> >> >> Using config file "/etc/xen/DomU.cfg". >> >> >> Error: ('create', '-aremus:10.10.10.3:8002|aio:/dev/vggroup/DomU') >> >> >> failed >> >> >> (512 ) >> >> >> >> >> >> and on the log file : >> >> >> >> >> >> >> >> >> name1@machine1:~$ sudo sudo tail /var/log/xen/xend.log >> >> >> mounted_vbd_uuid = dom0.create_vbd(vbd, disk); >> >> >> File >> >> >> "/usr/local/lib/python2.7/dist-packages/xen/xend/XendDomainInfo.py", >> >> >> line >> >> >> 3987, in create_vbd >> >> >> devid = dev_control.createDevice(config) >> >> >> File >> >> >> >> >> >> >> "/usr/local/lib/python2.7/dist-packages/xen/xend/server/BlktapController.py", >> >> >> line 174, in createDevice >> >> >> device = TapdiskController.create(params, file) >> >> >> File >> >> >> >> >> >> >> "/usr/local/lib/python2.7/dist-packages/xen/xend/server/BlktapController.py", >> >> >> line 286, in create >> >> >> return TapdiskController.exc('create', '-a%s:%s' % (dtype, >> image)) >> >> >> File >> >> >> >> >> >> >> "/usr/local/lib/python2.7/dist-packages/xen/xend/server/BlktapController.py", >> >> >> line 233, in exc >> >> >> (args, rc, out, err)) >> >> >> TapdiskException: ('create', >> >> >> '-aremus:10.10.10.3:8002|aio:/dev/vggroup/DomU') failed (512 ) >> >> >> >> >> >> Any hints and help would very appreciated. >> >> >> >> >> >> Regards, >> >> >> >> >> >> Agya >> >> >> >> >> >> >> >> >> _______________________________________________ >> >> >> Xen-devel mailing list >> >> >> Xen-devel@lists.xen.org >> >> >> http://lists.xen.org/xen-devel >> >> >> >> >> > >> >> > >> >> > _______________________________________________ >> >> > Xen-devel mailing list >> >> > Xen-devel@lists.xen.org >> >> > http://lists.xen.org/xen-devel >> >> > >> > >> > >> > > --f46d0442885e0f10fe04d6070a66 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable I forgot to told that its =A0work with protocol C

<= font face=3D"courier new, monospace">=A0$ sudo drbd-overview
=A0 1:drbd-vm =A0SyncTarget Second= ary/Secondary Inconsistent/UpToDate C r-----
=A0 =A0 =A0 =A0 [=3D>........= ..........] sync'ed: 12.0% (9016/10236)M

$ sudo drbd-overview
=A0 1:drbd-vm =A0Connected Secon= dary/Secondary UpToDate/UpToDate C r-----

<= br>
On Mon, Feb 18, 2013 at 11:00 PM, agya = naila <agya.naila@gmail.com> wrote:
On Mon, Feb 18, 2013 = at 10:33 PM, Shriram Rajagopalan <rshriram@cs.ubc.ca> wrote= :
Hi,
=A0I suggest you read up on the DRBD setup documentation from the
drbd.org website.
=A0The setup procedure is same. You can later flip to the remus
replication protocol by simply
=A0changing the protocol type (C to D).

I am comparing my configuration with drbd website, h= owever I got this error :

$ sudo drbdadm up drbd-vm
'D' is no valid proto= col.
Command 'drbdsetup 1 net = ipv4:10.10.10.1:7789 ipv4:10.10.10.3:778= 9 D --set-defaults --create-device --rr-conflict=3Ddisconnect --after-s= b-2pri=3Ddisconnect --after-sb-1pri=3Ddiscard-secondary --after-sb-0pri=3Dd= iscard-younger-primary --allow-two-primaries --ko-count=3D4 --max-epoch-siz= e=3D4096 --unplug-watermark=3D4096 --max-buffers=3D8192 --ping-timeout=3D20= --ping-int=3D3 --timeout=3D30' terminated with exit code 20=
drbdadm connect drbd-vm: exit= ed with code 20
=
$ sudo d= rbd-overview
=A0 = 1:drbd-vm =A0StandAlone Secondary/Unknown UpToDate/DUnknown r----s

Thank you,

Agya

=A0
thanks
shriram

On Mon, Feb 18, 2013 at 4:11 PM, agya naila <agya.naila@gmail.com> wrote:
>
> On Mon, Feb 18, 2013 at 9:08 PM, Shriram Rajagopalan <rshriram@cs.ubc.ca>
> wrote:
>>
>> hi
>
>
> Thank you shriram.
>
>>
>> =A0sorry for the delayed response. IIRC the blktap2 driver require= d for
>> tapdisk replication doesnt exist in the mainstream dom0 kernels, I= IRC.
>> =A0I havent used it in a long time myself. I suggest trying disk >> replication with DRBD.
>>
>
> I am also found some information here
> http://osdir.com/ml/xen-users/2011-07/msg00653.html about b= lktap2 problem on
> amd64 architecture. I have tried to install and configure the DRBD but= its
> didn't connect each other.
> I used drbd-8.3.11-remus and installed as follow
>
> cd /usr/src/
> wget
> http://remusha.wi= kidot.com/local--files/configuring-and-installing-remus/drbd-8.3.11-remus.t= ar.gz
> tar xzf drbd-8.3.9-remus.tar.gz
> chown -R root:root drbd-8.3-remus
> cd /usr/src/drbd-8.3-remus
> chmod 777 autogen.sh
> ./autogen.sh
> dpkg-buildpackage -b -uc
> cd /usr/src/drbd-8.3-remus/drbd
> make clean
> make
> make install
> cd /usr/src/
> cp /usr/src/drbd-8.3-remus/scripts/global_common.conf.protoD
> /etc/drbd.d/global_common.conf
> cp /usr/src/drbd-8.3-remus/scripts/testvms_protoD.res
> /etc/drbd.d/SystemHA_protoD.res
>
> sudo apt-get install drbd8-utils
>
> =A0from tutorial http://remusha.wikidot.com/configuring= -and-installing-remus
>
> My *.res configuration as follow :
>
> resource drbd-vm{
> =A0 device =A0 =A0/dev/drbd1;
> =A0 disk =A0 =A0 =A0/dev/vgvoip/DomU;
> =A0 meta-disk internal;
> =A0 on machine1 {
> =A0 =A0 address =A0 10.10.10.1:7789;
> =A0 }
> =A0 on machine2 {
> =A0 =A0 address =A0 10.10.10.3:7789;
> =A0 }
> }
>
> and then I invoke command to create that meta
>
> drbdadm create-md drbd-vm
>
> However, when I try to make this configuration up by :
>
> drbdadm up drbd-vm
>
> Its come with error :
>
> $ sudo drbdadm up drbd-vm
> 1: Failure: (124) Device is attached to a disk (use detach first)
> Command 'drbdsetup 1 disk /dev/vgvoip/DomU /dev/vgvoip/DomU intern= al
> --set-defaults --create-device --fencing=3Ddont-care --on-io-error=3Dp= ass_on'
> terminated with exit code 10
>
> If I run the
>
> $ sudo drbdadm detach drbd-vm
>
> Its come error
>
> $ sudo drbdadm detach drbd-vm
> 1: State change failed: (-2) Need access to UpToDate data
> Command 'drbdsetup 1 detach' terminated with exit code 17
>
> Here the /proc/drbd on both machine
>
> Machine 1
>
> $ sudo cat /proc/drbd
> version: 8.3.11 (api:88/proto:86-96)
> GIT-hash: 0de839cee13a4160eed6037c4bddd066645e23c5 build by root@machi= ne1,
> 2013-02-18 18:49:57
>
> =A01: cs:StandAlone ro:Primary/Unknown ds:UpToDate/DUnknown =A0 r----s=
> =A0 =A0 ns:0 nr:0 dw:0 dr:1712 al:0 bm:0 lo:0 pe:0 ua:0 ap:0 ep:1 wo:b= def:0
> chkpt:0 oos:10485404
>
>
> Machine 2
>
> $ sudo cat /proc/drbd
> version: 8.3.11 (api:88/proto:86-96)
> GIT-hash: 0de839cee13a4160eed6037c4bddd066645e23c5 build by root@machi= ne2,
> 2013-02-18 19:26:57
>
> =A01: cs:StandAlone ro:Secondary/Unknown ds:Inconsistent/DUnknown =A0 = r----s
> =A0 =A0 ns:0 nr:0 dw:0 dr:0 al:0 bm:0 lo:0 pe:0 ua:0 ap:0 ep:1 wo:b de= f:0
> chkpt:0 oos:10485404
>
>
> Do you have some hints?
>
> Thank you,
>
>
> Agya
>
>
>> thanks
>> shriram
>>
>> On Mon, Feb 18, 2013 at 5:38 AM, Hery Dian Septama <herydians@gmail.com> >> wrote:
>> > Hello, Anyone have a clue? I have tried but still failed :( >> >
>> > On Sat, Feb 16, 2013 at 6:56 PM, agya naila <agya.naila@gmail.com> >> > wrote:
>> >>
>> >> Dear all,
>> >>
>> >> I am configure my machine to run the remus disk replicati= on. I am using
>> >> xen 4.2.3 installed from sources and Ubuntu 12.04 64 bit = both for Dom0
>> >> and
>> >> DomU.
>> >> I have install the blktap and its work properly with conf= iguration
>> >> string
>> >> phy or tap2 like this :
>> >> disk =3D ['phy:/dev/vggroup/DomU,xvda,w']
>> >> or
>> >> disk =3D ['tap2:tapdisk:aio:/dev/vggroup/DomU,xvda,w&= #39;]
>> >>
>> >> and remus command
>> >>
>> >> remus --no-net myvm mybackuphost
>> >>
>> >>
>> >> However when I change the string as suggested on remus pa= ges to enable
>> >> the
>> >> disk replication its still failed :
>> >>
>> >> name =3D "DomU"
>> >> memory =3D 1024
>> >> disk =3D ['tap2:remus:10.10.10.3:8002|aio:/dev/vggrou= p/DomU,xvda,w']
>> >> vif =3D ['ip=3D192.168.1.55,bridge=3Dxenbr0']
>> >> bootloader =3D "pygrub"
>> >>
>> >> with error messages :
>> >>
>> >> name1@machine1:~$ sudo xm create -c /etc/xen/DomU.cfg
>> >> Using config file "/etc/xen/DomU.cfg".
>> >> Error: ('create', '-aremus:10.10.10.3:8002|ai= o:/dev/vggroup/DomU')
>> >> failed
>> >> (512 =A0)
>> >>
>> >> and on the log file :
>> >>
>> >>
>> >> name1@machine1:~$ sudo sudo tail /var/log/xen/xend.log >> >> =A0 =A0 mounted_vbd_uuid =3D dom0.create_vbd(vbd, disk);<= br> >> >> =A0 File
>> >> "/usr/local/lib/python2.7/dist-packages/xen/xend/Xen= dDomainInfo.py",
>> >> line
>> >> 3987, in create_vbd
>> >> =A0 =A0 devid =3D dev_control.createDevice(config)
>> >> =A0 File
>> >>
>> >> "/usr/local/lib/python2.7/dist-packages/xen/xend/ser= ver/BlktapController.py",
>> >> line 174, in createDevice
>> >> =A0 =A0 device =3D TapdiskController.create(params, file)=
>> >> =A0 File
>> >>
>> >> "/usr/local/lib/python2.7/dist-packages/xen/xend/ser= ver/BlktapController.py",
>> >> line 286, in create
>> >> =A0 =A0 return TapdiskController.exc('create', &#= 39;-a%s:%s' % (dtype, image))
>> >> =A0 File
>> >>
>> >> "/usr/local/lib/python2.7/dist-packages/xen/xend/ser= ver/BlktapController.py",
>> >> line 233, in exc
>> >> =A0 =A0 (args, rc, out, err))
>> >> TapdiskException: ('create',
>> >> '-aremus:10.10.10.3:8002|aio:/dev/vggroup/DomU') = failed (512 =A0)
>> >>
>> >> Any hints and help would very appreciated.
>> >>
>> >> Regards,
>> >>
>> >> Agya
>> >>
>> >>
>> >> _______________________________________________
>> >> Xen-devel mailing list
>> >> Xen-devel@lists.xen.org
>> >> http://lists.xen.org/xen-devel
>> >>
>> >
>> >
>> > _______________________________________________
>> > Xen-devel mailing list
>> > = Xen-devel@lists.xen.org
>> > = http://lists.xen.org/xen-devel
>> >
>
>


--f46d0442885e0f10fe04d6070a66-- --===============6194876638353693985== 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 --===============6194876638353693985==-- From xen-users-bounces@lists.xen.org Mon Feb 18 22:14:27 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 18 Feb 2013 22:14: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 1U7YyD-0006aQ-A1; Mon, 18 Feb 2013 22:13:57 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U7YyB-0006a6-Gc; Mon, 18 Feb 2013 22:13:55 +0000 Received: from [85.158.143.99:26416] by server-2.bemta-4.messagelabs.com id A0/B7-12656-2A7A2215; Mon, 18 Feb 2013 22:13:54 +0000 X-Env-Sender: agya.naila@gmail.com X-Msg-Ref: server-13.tower-216.messagelabs.com!1361225628!27150695!1 X-Originating-IP: [74.125.82.180] 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.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 28846 invoked from network); 18 Feb 2013 22:13:49 -0000 Received: from mail-we0-f180.google.com (HELO mail-we0-f180.google.com) (74.125.82.180) by server-13.tower-216.messagelabs.com with RC4-SHA encrypted SMTP; 18 Feb 2013 22:13:49 -0000 Received: by mail-we0-f180.google.com with SMTP id k14so5012206wer.39 for ; Mon, 18 Feb 2013 14:13:48 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=p4g1tH8Rx62BX/0trQmexP0fgMXLXkZBzl1+42FIjbg=; b=nVB40bgxjmjErd9H5guGHrtiEoyrcD17O4DbKD+Xv2zwfy0JwlG72Mj4hNZiQo4VwL /vMYVqJZ7XSoQ96HK4qEcoJ/PxBTBFZ9sRjLjkyUDdjq7728v+eHRFCbAB0SBTPhAt0+ sLj/yxV75drCecMAwYeT/NT717NAS0/CL9h1SidjBYc+J/gf4L+Hc5z8Yuex6xPrAkTX RlU3pU+4WwEwXMRLBKjU/Zv6qAdUxYcJs9bSZ3khbh9cHLhzdLt8tjHMQ7Mp1Ta0NJ7C IEVa8XQEFORExunPByNJvwZDYlBcJgYaaSxE/tikydw5U5h0bWHYG/KAWAH3RoJ8eLAD Ndkg== MIME-Version: 1.0 X-Received: by 10.180.98.232 with SMTP id el8mr19975098wib.22.1361225628717; Mon, 18 Feb 2013 14:13:48 -0800 (PST) Received: by 10.216.236.13 with HTTP; Mon, 18 Feb 2013 14:13:48 -0800 (PST) In-Reply-To: References: Date: Mon, 18 Feb 2013 23:13:48 +0100 Message-ID: From: agya naila To: rshriram@cs.ubc.ca Cc: "xen-users@lists.xen.org" , "xen-devel@lists.xen.org" Subject: Re: [Xen-users] [Xen-devel] Remus disk replication failed X-BeenThere: xen-users@lists.xen.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="===============6194876638353693985==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============6194876638353693985== Content-Type: multipart/alternative; boundary=f46d0442885e0f10fe04d6070a66 --f46d0442885e0f10fe04d6070a66 Content-Type: text/plain; charset=ISO-8859-1 I forgot to told that its work with protocol C $ sudo drbd-overview 1:drbd-vm SyncTarget Secondary/Secondary Inconsistent/UpToDate C r----- [=>..................] sync'ed: 12.0% (9016/10236)M $ sudo drbd-overview 1:drbd-vm Connected Secondary/Secondary UpToDate/UpToDate C r----- On Mon, Feb 18, 2013 at 11:00 PM, agya naila wrote: > On Mon, Feb 18, 2013 at 10:33 PM, Shriram Rajagopalan wrote: > >> Hi, >> I suggest you read up on the DRBD setup documentation from the >> drbd.org website. >> The setup procedure is same. You can later flip to the remus >> replication protocol by simply >> changing the protocol type (C to D). >> >> I am comparing my configuration with drbd website, however I got this > error : > > $ sudo drbdadm up drbd-vm > *'D' is no valid protocol.* > *Command 'drbdsetup 1 net ipv4:10.10.10.1:7789 ipv4:10.10.10.3:7789 D > --set-defaults --create-device --rr-conflict=disconnect > --after-sb-2pri=disconnect --after-sb-1pri=discard-secondary > --after-sb-0pri=discard-younger-primary --allow-two-primaries --ko-count=4 > --max-epoch-size=4096 --unplug-watermark=4096 --max-buffers=8192 > --ping-timeout=20 --ping-int=3 --timeout=30' terminated with exit code 20* > *drbdadm connect drbd-vm: exited with code 20* > * > * > $ sudo drbd-overview > 1:drbd-vm StandAlone Secondary/Unknown UpToDate/DUnknown r----s > > Thank you, > > Agya > > > >> thanks >> shriram >> >> On Mon, Feb 18, 2013 at 4:11 PM, agya naila wrote: >> > >> > On Mon, Feb 18, 2013 at 9:08 PM, Shriram Rajagopalan < >> rshriram@cs.ubc.ca> >> > wrote: >> >> >> >> hi >> > >> > >> > Thank you shriram. >> > >> >> >> >> sorry for the delayed response. IIRC the blktap2 driver required for >> >> tapdisk replication doesnt exist in the mainstream dom0 kernels, IIRC. >> >> I havent used it in a long time myself. I suggest trying disk >> >> replication with DRBD. >> >> >> > >> > I am also found some information here >> > http://osdir.com/ml/xen-users/2011-07/msg00653.html about blktap2 >> problem on >> > amd64 architecture. I have tried to install and configure the DRBD but >> its >> > didn't connect each other. >> > I used drbd-8.3.11-remus and installed as follow >> > >> > cd /usr/src/ >> > wget >> > >> http://remusha.wikidot.com/local--files/configuring-and-installing-remus/drbd-8.3.11-remus.tar.gz >> > tar xzf drbd-8.3.9-remus.tar.gz >> > chown -R root:root drbd-8.3-remus >> > cd /usr/src/drbd-8.3-remus >> > chmod 777 autogen.sh >> > ./autogen.sh >> > dpkg-buildpackage -b -uc >> > cd /usr/src/drbd-8.3-remus/drbd >> > make clean >> > make >> > make install >> > cd /usr/src/ >> > cp /usr/src/drbd-8.3-remus/scripts/global_common.conf.protoD >> > /etc/drbd.d/global_common.conf >> > cp /usr/src/drbd-8.3-remus/scripts/testvms_protoD.res >> > /etc/drbd.d/SystemHA_protoD.res >> > >> > sudo apt-get install drbd8-utils >> > >> > from tutorial >> http://remusha.wikidot.com/configuring-and-installing-remus >> > >> > My *.res configuration as follow : >> > >> > resource drbd-vm{ >> > device /dev/drbd1; >> > disk /dev/vgvoip/DomU; >> > meta-disk internal; >> > on machine1 { >> > address 10.10.10.1:7789; >> > } >> > on machine2 { >> > address 10.10.10.3:7789; >> > } >> > } >> > >> > and then I invoke command to create that meta >> > >> > drbdadm create-md drbd-vm >> > >> > However, when I try to make this configuration up by : >> > >> > drbdadm up drbd-vm >> > >> > Its come with error : >> > >> > $ sudo drbdadm up drbd-vm >> > 1: Failure: (124) Device is attached to a disk (use detach first) >> > Command 'drbdsetup 1 disk /dev/vgvoip/DomU /dev/vgvoip/DomU internal >> > --set-defaults --create-device --fencing=dont-care >> --on-io-error=pass_on' >> > terminated with exit code 10 >> > >> > If I run the >> > >> > $ sudo drbdadm detach drbd-vm >> > >> > Its come error >> > >> > $ sudo drbdadm detach drbd-vm >> > 1: State change failed: (-2) Need access to UpToDate data >> > Command 'drbdsetup 1 detach' terminated with exit code 17 >> > >> > Here the /proc/drbd on both machine >> > >> > Machine 1 >> > >> > $ sudo cat /proc/drbd >> > version: 8.3.11 (api:88/proto:86-96) >> > GIT-hash: 0de839cee13a4160eed6037c4bddd066645e23c5 build by >> root@machine1, >> > 2013-02-18 18:49:57 >> > >> > 1: cs:StandAlone ro:Primary/Unknown ds:UpToDate/DUnknown r----s >> > ns:0 nr:0 dw:0 dr:1712 al:0 bm:0 lo:0 pe:0 ua:0 ap:0 ep:1 wo:b def:0 >> > chkpt:0 oos:10485404 >> > >> > >> > Machine 2 >> > >> > $ sudo cat /proc/drbd >> > version: 8.3.11 (api:88/proto:86-96) >> > GIT-hash: 0de839cee13a4160eed6037c4bddd066645e23c5 build by >> root@machine2, >> > 2013-02-18 19:26:57 >> > >> > 1: cs:StandAlone ro:Secondary/Unknown ds:Inconsistent/DUnknown r----s >> > ns:0 nr:0 dw:0 dr:0 al:0 bm:0 lo:0 pe:0 ua:0 ap:0 ep:1 wo:b def:0 >> > chkpt:0 oos:10485404 >> > >> > >> > Do you have some hints? >> > >> > Thank you, >> > >> > >> > Agya >> > >> > >> >> thanks >> >> shriram >> >> >> >> On Mon, Feb 18, 2013 at 5:38 AM, Hery Dian Septama < >> herydians@gmail.com> >> >> wrote: >> >> > Hello, Anyone have a clue? I have tried but still failed :( >> >> > >> >> > On Sat, Feb 16, 2013 at 6:56 PM, agya naila >> >> > wrote: >> >> >> >> >> >> Dear all, >> >> >> >> >> >> I am configure my machine to run the remus disk replication. I am >> using >> >> >> xen 4.2.3 installed from sources and Ubuntu 12.04 64 bit both for >> Dom0 >> >> >> and >> >> >> DomU. >> >> >> I have install the blktap and its work properly with configuration >> >> >> string >> >> >> phy or tap2 like this : >> >> >> disk = ['phy:/dev/vggroup/DomU,xvda,w'] >> >> >> or >> >> >> disk = ['tap2:tapdisk:aio:/dev/vggroup/DomU,xvda,w'] >> >> >> >> >> >> and remus command >> >> >> >> >> >> remus --no-net myvm mybackuphost >> >> >> >> >> >> >> >> >> However when I change the string as suggested on remus pages to >> enable >> >> >> the >> >> >> disk replication its still failed : >> >> >> >> >> >> name = "DomU" >> >> >> memory = 1024 >> >> >> disk = ['tap2:remus:10.10.10.3:8002|aio:/dev/vggroup/DomU,xvda,w'] >> >> >> vif = ['ip=192.168.1.55,bridge=xenbr0'] >> >> >> bootloader = "pygrub" >> >> >> >> >> >> with error messages : >> >> >> >> >> >> name1@machine1:~$ sudo xm create -c /etc/xen/DomU.cfg >> >> >> Using config file "/etc/xen/DomU.cfg". >> >> >> Error: ('create', '-aremus:10.10.10.3:8002|aio:/dev/vggroup/DomU') >> >> >> failed >> >> >> (512 ) >> >> >> >> >> >> and on the log file : >> >> >> >> >> >> >> >> >> name1@machine1:~$ sudo sudo tail /var/log/xen/xend.log >> >> >> mounted_vbd_uuid = dom0.create_vbd(vbd, disk); >> >> >> File >> >> >> "/usr/local/lib/python2.7/dist-packages/xen/xend/XendDomainInfo.py", >> >> >> line >> >> >> 3987, in create_vbd >> >> >> devid = dev_control.createDevice(config) >> >> >> File >> >> >> >> >> >> >> "/usr/local/lib/python2.7/dist-packages/xen/xend/server/BlktapController.py", >> >> >> line 174, in createDevice >> >> >> device = TapdiskController.create(params, file) >> >> >> File >> >> >> >> >> >> >> "/usr/local/lib/python2.7/dist-packages/xen/xend/server/BlktapController.py", >> >> >> line 286, in create >> >> >> return TapdiskController.exc('create', '-a%s:%s' % (dtype, >> image)) >> >> >> File >> >> >> >> >> >> >> "/usr/local/lib/python2.7/dist-packages/xen/xend/server/BlktapController.py", >> >> >> line 233, in exc >> >> >> (args, rc, out, err)) >> >> >> TapdiskException: ('create', >> >> >> '-aremus:10.10.10.3:8002|aio:/dev/vggroup/DomU') failed (512 ) >> >> >> >> >> >> Any hints and help would very appreciated. >> >> >> >> >> >> Regards, >> >> >> >> >> >> Agya >> >> >> >> >> >> >> >> >> _______________________________________________ >> >> >> Xen-devel mailing list >> >> >> Xen-devel@lists.xen.org >> >> >> http://lists.xen.org/xen-devel >> >> >> >> >> > >> >> > >> >> > _______________________________________________ >> >> > Xen-devel mailing list >> >> > Xen-devel@lists.xen.org >> >> > http://lists.xen.org/xen-devel >> >> > >> > >> > >> > > --f46d0442885e0f10fe04d6070a66 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable I forgot to told that its =A0work with protocol C

<= font face=3D"courier new, monospace">=A0$ sudo drbd-overview
=A0 1:drbd-vm =A0SyncTarget Second= ary/Secondary Inconsistent/UpToDate C r-----
=A0 =A0 =A0 =A0 [=3D>........= ..........] sync'ed: 12.0% (9016/10236)M

$ sudo drbd-overview
=A0 1:drbd-vm =A0Connected Secon= dary/Secondary UpToDate/UpToDate C r-----

<= br>
On Mon, Feb 18, 2013 at 11:00 PM, agya = naila <agya.naila@gmail.com> wrote:
On Mon, Feb 18, 2013 = at 10:33 PM, Shriram Rajagopalan <rshriram@cs.ubc.ca> wrote= :
Hi,
=A0I suggest you read up on the DRBD setup documentation from the
drbd.org website.
=A0The setup procedure is same. You can later flip to the remus
replication protocol by simply
=A0changing the protocol type (C to D).

I am comparing my configuration with drbd website, h= owever I got this error :

$ sudo drbdadm up drbd-vm
'D' is no valid proto= col.
Command 'drbdsetup 1 net = ipv4:10.10.10.1:7789 ipv4:10.10.10.3:778= 9 D --set-defaults --create-device --rr-conflict=3Ddisconnect --after-s= b-2pri=3Ddisconnect --after-sb-1pri=3Ddiscard-secondary --after-sb-0pri=3Dd= iscard-younger-primary --allow-two-primaries --ko-count=3D4 --max-epoch-siz= e=3D4096 --unplug-watermark=3D4096 --max-buffers=3D8192 --ping-timeout=3D20= --ping-int=3D3 --timeout=3D30' terminated with exit code 20=
drbdadm connect drbd-vm: exit= ed with code 20
=
$ sudo d= rbd-overview
=A0 = 1:drbd-vm =A0StandAlone Secondary/Unknown UpToDate/DUnknown r----s

Thank you,

Agya

=A0
thanks
shriram

On Mon, Feb 18, 2013 at 4:11 PM, agya naila <agya.naila@gmail.com> wrote:
>
> On Mon, Feb 18, 2013 at 9:08 PM, Shriram Rajagopalan <rshriram@cs.ubc.ca>
> wrote:
>>
>> hi
>
>
> Thank you shriram.
>
>>
>> =A0sorry for the delayed response. IIRC the blktap2 driver require= d for
>> tapdisk replication doesnt exist in the mainstream dom0 kernels, I= IRC.
>> =A0I havent used it in a long time myself. I suggest trying disk >> replication with DRBD.
>>
>
> I am also found some information here
> http://osdir.com/ml/xen-users/2011-07/msg00653.html about b= lktap2 problem on
> amd64 architecture. I have tried to install and configure the DRBD but= its
> didn't connect each other.
> I used drbd-8.3.11-remus and installed as follow
>
> cd /usr/src/
> wget
> http://remusha.wi= kidot.com/local--files/configuring-and-installing-remus/drbd-8.3.11-remus.t= ar.gz
> tar xzf drbd-8.3.9-remus.tar.gz
> chown -R root:root drbd-8.3-remus
> cd /usr/src/drbd-8.3-remus
> chmod 777 autogen.sh
> ./autogen.sh
> dpkg-buildpackage -b -uc
> cd /usr/src/drbd-8.3-remus/drbd
> make clean
> make
> make install
> cd /usr/src/
> cp /usr/src/drbd-8.3-remus/scripts/global_common.conf.protoD
> /etc/drbd.d/global_common.conf
> cp /usr/src/drbd-8.3-remus/scripts/testvms_protoD.res
> /etc/drbd.d/SystemHA_protoD.res
>
> sudo apt-get install drbd8-utils
>
> =A0from tutorial http://remusha.wikidot.com/configuring= -and-installing-remus
>
> My *.res configuration as follow :
>
> resource drbd-vm{
> =A0 device =A0 =A0/dev/drbd1;
> =A0 disk =A0 =A0 =A0/dev/vgvoip/DomU;
> =A0 meta-disk internal;
> =A0 on machine1 {
> =A0 =A0 address =A0 10.10.10.1:7789;
> =A0 }
> =A0 on machine2 {
> =A0 =A0 address =A0 10.10.10.3:7789;
> =A0 }
> }
>
> and then I invoke command to create that meta
>
> drbdadm create-md drbd-vm
>
> However, when I try to make this configuration up by :
>
> drbdadm up drbd-vm
>
> Its come with error :
>
> $ sudo drbdadm up drbd-vm
> 1: Failure: (124) Device is attached to a disk (use detach first)
> Command 'drbdsetup 1 disk /dev/vgvoip/DomU /dev/vgvoip/DomU intern= al
> --set-defaults --create-device --fencing=3Ddont-care --on-io-error=3Dp= ass_on'
> terminated with exit code 10
>
> If I run the
>
> $ sudo drbdadm detach drbd-vm
>
> Its come error
>
> $ sudo drbdadm detach drbd-vm
> 1: State change failed: (-2) Need access to UpToDate data
> Command 'drbdsetup 1 detach' terminated with exit code 17
>
> Here the /proc/drbd on both machine
>
> Machine 1
>
> $ sudo cat /proc/drbd
> version: 8.3.11 (api:88/proto:86-96)
> GIT-hash: 0de839cee13a4160eed6037c4bddd066645e23c5 build by root@machi= ne1,
> 2013-02-18 18:49:57
>
> =A01: cs:StandAlone ro:Primary/Unknown ds:UpToDate/DUnknown =A0 r----s=
> =A0 =A0 ns:0 nr:0 dw:0 dr:1712 al:0 bm:0 lo:0 pe:0 ua:0 ap:0 ep:1 wo:b= def:0
> chkpt:0 oos:10485404
>
>
> Machine 2
>
> $ sudo cat /proc/drbd
> version: 8.3.11 (api:88/proto:86-96)
> GIT-hash: 0de839cee13a4160eed6037c4bddd066645e23c5 build by root@machi= ne2,
> 2013-02-18 19:26:57
>
> =A01: cs:StandAlone ro:Secondary/Unknown ds:Inconsistent/DUnknown =A0 = r----s
> =A0 =A0 ns:0 nr:0 dw:0 dr:0 al:0 bm:0 lo:0 pe:0 ua:0 ap:0 ep:1 wo:b de= f:0
> chkpt:0 oos:10485404
>
>
> Do you have some hints?
>
> Thank you,
>
>
> Agya
>
>
>> thanks
>> shriram
>>
>> On Mon, Feb 18, 2013 at 5:38 AM, Hery Dian Septama <herydians@gmail.com> >> wrote:
>> > Hello, Anyone have a clue? I have tried but still failed :( >> >
>> > On Sat, Feb 16, 2013 at 6:56 PM, agya naila <agya.naila@gmail.com> >> > wrote:
>> >>
>> >> Dear all,
>> >>
>> >> I am configure my machine to run the remus disk replicati= on. I am using
>> >> xen 4.2.3 installed from sources and Ubuntu 12.04 64 bit = both for Dom0
>> >> and
>> >> DomU.
>> >> I have install the blktap and its work properly with conf= iguration
>> >> string
>> >> phy or tap2 like this :
>> >> disk =3D ['phy:/dev/vggroup/DomU,xvda,w']
>> >> or
>> >> disk =3D ['tap2:tapdisk:aio:/dev/vggroup/DomU,xvda,w&= #39;]
>> >>
>> >> and remus command
>> >>
>> >> remus --no-net myvm mybackuphost
>> >>
>> >>
>> >> However when I change the string as suggested on remus pa= ges to enable
>> >> the
>> >> disk replication its still failed :
>> >>
>> >> name =3D "DomU"
>> >> memory =3D 1024
>> >> disk =3D ['tap2:remus:10.10.10.3:8002|aio:/dev/vggrou= p/DomU,xvda,w']
>> >> vif =3D ['ip=3D192.168.1.55,bridge=3Dxenbr0']
>> >> bootloader =3D "pygrub"
>> >>
>> >> with error messages :
>> >>
>> >> name1@machine1:~$ sudo xm create -c /etc/xen/DomU.cfg
>> >> Using config file "/etc/xen/DomU.cfg".
>> >> Error: ('create', '-aremus:10.10.10.3:8002|ai= o:/dev/vggroup/DomU')
>> >> failed
>> >> (512 =A0)
>> >>
>> >> and on the log file :
>> >>
>> >>
>> >> name1@machine1:~$ sudo sudo tail /var/log/xen/xend.log >> >> =A0 =A0 mounted_vbd_uuid =3D dom0.create_vbd(vbd, disk);<= br> >> >> =A0 File
>> >> "/usr/local/lib/python2.7/dist-packages/xen/xend/Xen= dDomainInfo.py",
>> >> line
>> >> 3987, in create_vbd
>> >> =A0 =A0 devid =3D dev_control.createDevice(config)
>> >> =A0 File
>> >>
>> >> "/usr/local/lib/python2.7/dist-packages/xen/xend/ser= ver/BlktapController.py",
>> >> line 174, in createDevice
>> >> =A0 =A0 device =3D TapdiskController.create(params, file)=
>> >> =A0 File
>> >>
>> >> "/usr/local/lib/python2.7/dist-packages/xen/xend/ser= ver/BlktapController.py",
>> >> line 286, in create
>> >> =A0 =A0 return TapdiskController.exc('create', &#= 39;-a%s:%s' % (dtype, image))
>> >> =A0 File
>> >>
>> >> "/usr/local/lib/python2.7/dist-packages/xen/xend/ser= ver/BlktapController.py",
>> >> line 233, in exc
>> >> =A0 =A0 (args, rc, out, err))
>> >> TapdiskException: ('create',
>> >> '-aremus:10.10.10.3:8002|aio:/dev/vggroup/DomU') = failed (512 =A0)
>> >>
>> >> Any hints and help would very appreciated.
>> >>
>> >> Regards,
>> >>
>> >> Agya
>> >>
>> >>
>> >> _______________________________________________
>> >> Xen-devel mailing list
>> >> Xen-devel@lists.xen.org
>> >> http://lists.xen.org/xen-devel
>> >>
>> >
>> >
>> > _______________________________________________
>> > Xen-devel mailing list
>> > = Xen-devel@lists.xen.org
>> > = http://lists.xen.org/xen-devel
>> >
>
>


--f46d0442885e0f10fe04d6070a66-- --===============6194876638353693985== 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 --===============6194876638353693985==-- From xen-users-bounces@lists.xen.org Mon Feb 18 22:21:34 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 18 Feb 2013 22:21: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 1U7Z52-0007AQ-I9; Mon, 18 Feb 2013 22:21:00 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U7Z51-00079u-5q for xen-users@lists.xen.org; Mon, 18 Feb 2013 22:20:59 +0000 Received: from [85.158.143.35:37954] by server-3.bemta-4.messagelabs.com id 36/01-08920-A49A2215; Mon, 18 Feb 2013 22:20:58 +0000 X-Env-Sender: cdelorme@gmail.com X-Msg-Ref: server-6.tower-21.messagelabs.com!1361226049!16047358!1 X-Originating-IP: [209.85.220.170] 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.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 10975 invoked from network); 18 Feb 2013 22:20:51 -0000 Received: from mail-vc0-f170.google.com (HELO mail-vc0-f170.google.com) (209.85.220.170) by server-6.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 18 Feb 2013 22:20:51 -0000 Received: by mail-vc0-f170.google.com with SMTP id p16so3916803vcq.15 for ; Mon, 18 Feb 2013 14:20:49 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:date:message-id:subject:from:to :content-type; bh=UDp75YBbW5ClLlXTJ56ValJ/W6AuG+miK5bOjjqfBy8=; b=VdS6UnSeTi1a1Z9OV5chF44h4s/XIKq9eFxYruYJl6ERBMfQyGKZixyYiHKXaJeJ5o 0JAUoyliNGjfKcaJGws8NfvYPnKBE0JDKESbbynCzDO9BQj3x/HDS/sKqV1iMXNBJdI4 BKqKBjxYhA6wMFzKDSU3CSsPLTrGnstyK5Chay+zfEaW9u7Y+PkQdFdjyh8GV9t8Oesp TooHPNMwFlizUOaWjjOu9XX4wf5lWueOzykeoslaLAt8kygXPCSXbcyFkLuHLMO4AUMP Nw6lYNZeCWJqiGYpJjRdzDPguSDZHs26rl11k0m9onFq49rdtEGibcSw4xno8g8UHkKM KT2Q== MIME-Version: 1.0 X-Received: by 10.58.94.234 with SMTP id df10mr8888910veb.4.1361226049510; Mon, 18 Feb 2013 14:20:49 -0800 (PST) Received: by 10.58.32.199 with HTTP; Mon, 18 Feb 2013 14:20:49 -0800 (PST) Date: Mon, 18 Feb 2013 17:20:49 -0500 Message-ID: From: Casey DeLorme To: "xen-users@lists.xen.org" Subject: [Xen-users] xendomains stop and gplpv network questions X-BeenThere: xen-users@lists.xen.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="===============8963537468415427750==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============8963537468415427750== Content-Type: multipart/alternative; boundary=047d7b6dcfdc23db8404d6072336 --047d7b6dcfdc23db8404d6072336 Content-Type: text/plain; charset=UTF-8 Hello Xen Users, I have a couple of unrelated questions but didn't want to clutter everyones in-boxes with two emails. --- 1. Has anyone else been having trouble with the xendomains script? I am running 4.2 stable on Debian Wheezy, and the xendomains script does not shut down my running domains (specifically two linux HVM's one with PVHVM). When run manually via `service xendomains stop` or `/etc/init.d/xendomains stop` it returns a success message, but my machines continue to run as though nothing happened. When I shut down my computer without running `xl destroy` on the running domains it locks up, my guess is because the domains are still running. Has anyone else encountered this problem? --- 2. Is anyone else having problems restarting network adapters on Windows HVM's with GPLPV drivers? Without them it works fine, but with GPLPV installed if I disable and then attempt to re-enable a network adapter the device disappears from the machine. The only solution so far has been to reboot the HVM. Thanks for your help in advance. Sincerely, ~Casey --047d7b6dcfdc23db8404d6072336 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Hello Xen Users,

I have a co= uple of unrelated questions but didn't want to clutter everyones in-box= es with two emails.

---

1. Has anyone else been having trouble with the xendomains script?

I am running 4.2 stable on Debian Wheezy, and the xendomai= ns script does not shut down my running domains (specifically two linux HVM= 's one with PVHVM).

When run manually via `service xendomains stop` or `/et= c/init.d/xendomains stop` it returns a success message, but my machines con= tinue to run as though nothing happened.

When I sh= ut down my computer without running `xl destroy` on the running domains it = locks up, my guess is because the domains are still running.

Has anyone else encountered this problem?
---

2. Is anyone else having problems = restarting network adapters on Windows HVM's with GPLPV drivers?

Without them it works fine, but with GPLPV installed if= I disable and then attempt to re-enable a network adapter the device disap= pears from the machine.

The only solution so far h= as been to reboot the HVM.


Thanks for your help in advance.

Sincerely,

~Casey
--047d7b6dcfdc23db8404d6072336-- --===============8963537468415427750== 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 --===============8963537468415427750==-- From xen-users-bounces@lists.xen.org Mon Feb 18 22:21:34 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 18 Feb 2013 22:21: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 1U7Z52-0007AQ-I9; Mon, 18 Feb 2013 22:21:00 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U7Z51-00079u-5q for xen-users@lists.xen.org; Mon, 18 Feb 2013 22:20:59 +0000 Received: from [85.158.143.35:37954] by server-3.bemta-4.messagelabs.com id 36/01-08920-A49A2215; Mon, 18 Feb 2013 22:20:58 +0000 X-Env-Sender: cdelorme@gmail.com X-Msg-Ref: server-6.tower-21.messagelabs.com!1361226049!16047358!1 X-Originating-IP: [209.85.220.170] 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.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 10975 invoked from network); 18 Feb 2013 22:20:51 -0000 Received: from mail-vc0-f170.google.com (HELO mail-vc0-f170.google.com) (209.85.220.170) by server-6.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 18 Feb 2013 22:20:51 -0000 Received: by mail-vc0-f170.google.com with SMTP id p16so3916803vcq.15 for ; Mon, 18 Feb 2013 14:20:49 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:date:message-id:subject:from:to :content-type; bh=UDp75YBbW5ClLlXTJ56ValJ/W6AuG+miK5bOjjqfBy8=; b=VdS6UnSeTi1a1Z9OV5chF44h4s/XIKq9eFxYruYJl6ERBMfQyGKZixyYiHKXaJeJ5o 0JAUoyliNGjfKcaJGws8NfvYPnKBE0JDKESbbynCzDO9BQj3x/HDS/sKqV1iMXNBJdI4 BKqKBjxYhA6wMFzKDSU3CSsPLTrGnstyK5Chay+zfEaW9u7Y+PkQdFdjyh8GV9t8Oesp TooHPNMwFlizUOaWjjOu9XX4wf5lWueOzykeoslaLAt8kygXPCSXbcyFkLuHLMO4AUMP Nw6lYNZeCWJqiGYpJjRdzDPguSDZHs26rl11k0m9onFq49rdtEGibcSw4xno8g8UHkKM KT2Q== MIME-Version: 1.0 X-Received: by 10.58.94.234 with SMTP id df10mr8888910veb.4.1361226049510; Mon, 18 Feb 2013 14:20:49 -0800 (PST) Received: by 10.58.32.199 with HTTP; Mon, 18 Feb 2013 14:20:49 -0800 (PST) Date: Mon, 18 Feb 2013 17:20:49 -0500 Message-ID: From: Casey DeLorme To: "xen-users@lists.xen.org" Subject: [Xen-users] xendomains stop and gplpv network questions X-BeenThere: xen-users@lists.xen.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="===============8963537468415427750==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============8963537468415427750== Content-Type: multipart/alternative; boundary=047d7b6dcfdc23db8404d6072336 --047d7b6dcfdc23db8404d6072336 Content-Type: text/plain; charset=UTF-8 Hello Xen Users, I have a couple of unrelated questions but didn't want to clutter everyones in-boxes with two emails. --- 1. Has anyone else been having trouble with the xendomains script? I am running 4.2 stable on Debian Wheezy, and the xendomains script does not shut down my running domains (specifically two linux HVM's one with PVHVM). When run manually via `service xendomains stop` or `/etc/init.d/xendomains stop` it returns a success message, but my machines continue to run as though nothing happened. When I shut down my computer without running `xl destroy` on the running domains it locks up, my guess is because the domains are still running. Has anyone else encountered this problem? --- 2. Is anyone else having problems restarting network adapters on Windows HVM's with GPLPV drivers? Without them it works fine, but with GPLPV installed if I disable and then attempt to re-enable a network adapter the device disappears from the machine. The only solution so far has been to reboot the HVM. Thanks for your help in advance. Sincerely, ~Casey --047d7b6dcfdc23db8404d6072336 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Hello Xen Users,

I have a co= uple of unrelated questions but didn't want to clutter everyones in-box= es with two emails.

---

1. Has anyone else been having trouble with the xendomains script?

I am running 4.2 stable on Debian Wheezy, and the xendomai= ns script does not shut down my running domains (specifically two linux HVM= 's one with PVHVM).

When run manually via `service xendomains stop` or `/et= c/init.d/xendomains stop` it returns a success message, but my machines con= tinue to run as though nothing happened.

When I sh= ut down my computer without running `xl destroy` on the running domains it = locks up, my guess is because the domains are still running.

Has anyone else encountered this problem?
---

2. Is anyone else having problems = restarting network adapters on Windows HVM's with GPLPV drivers?

Without them it works fine, but with GPLPV installed if= I disable and then attempt to re-enable a network adapter the device disap= pears from the machine.

The only solution so far h= as been to reboot the HVM.


Thanks for your help in advance.

Sincerely,

~Casey
--047d7b6dcfdc23db8404d6072336-- --===============8963537468415427750== 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 --===============8963537468415427750==-- From xen-users-bounces@lists.xen.org Mon Feb 18 22:35:38 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 18 Feb 2013 22:35: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 1U7ZIU-0007i7-8T; Mon, 18 Feb 2013 22:34:54 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U7ZIR-0007hy-Pu for xen-users@lists.xen.org; Mon, 18 Feb 2013 22:34:52 +0000 Received: from [85.158.137.99:56750] by server-13.bemta-3.messagelabs.com id 27/51-20653-A8CA2215; Mon, 18 Feb 2013 22:34:50 +0000 X-Env-Sender: matthias.kannenberg@googlemail.com X-Msg-Ref: server-10.tower-217.messagelabs.com!1361226890!21156160!1 X-Originating-IP: [74.125.82.182] X-SpamReason: No, hits=0.3 required=7.0 tests=RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 30964 invoked from network); 18 Feb 2013 22:34:50 -0000 Received: from mail-we0-f182.google.com (HELO mail-we0-f182.google.com) (74.125.82.182) by server-10.tower-217.messagelabs.com with RC4-SHA encrypted SMTP; 18 Feb 2013 22:34:50 -0000 Received: by mail-we0-f182.google.com with SMTP id t57so5172754wey.41 for ; Mon, 18 Feb 2013 14:34:50 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=20120113; h=x-received:mime-version:in-reply-to:references:from:date:message-id :subject:to:cc:content-type; bh=HruSCD3wF2YzqlN0hvnFTXP7qtCDi5hFrPFsO/YrLbM=; b=WTSHUfpy9MW2yIkFSbEwgbDEefLct9CSVwpXf9/RL9k0OyBw2swVRKdVhzXsKCI2xS usDYsxWGNeOWqvaW1XsLsHPMYURrJy+1r6cc5Jc2jHmd5uqRfFTizkhC+NK9m2DBnsEa 25pevHtCkP7xcsFHC/ARbvvscWDcGaiXvFfPhTfrKPi4EGIqxrw3m806DDADfh3rNOBl 7t+WVN7STtt7FJsruxkC8All6oX0bPNMt2XbW7UAg5ZSnCLzgDsiC/vHmrs8yMhP8Sbt Z8cEO1LahArWKVnrVLnf/DUmfAzhq79y9Hjn7L+A548+k1yTWNNGMEET86XzPIp2SRxj s93g== X-Received: by 10.194.19.97 with SMTP id d1mr22142328wje.52.1361226890087; Mon, 18 Feb 2013 14:34:50 -0800 (PST) MIME-Version: 1.0 Received: by 10.194.80.68 with HTTP; Mon, 18 Feb 2013 14:34:30 -0800 (PST) In-Reply-To: References: <6035A0D088A63A46850C3988ED045A4B3567D7E6@BITCOM1.int.sbss.com.au> From: Matthias Date: Mon, 18 Feb 2013 23:34:30 +0100 Message-ID: To: jacek burghardt Cc: "xen-users@lists.xen.org" , James Harper Subject: Re: [Xen-users] gplpv drivers X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org Did you also install the xen reboot service? Since windows can't interprete the external shutdown request, you need a specific service who listens to it.. this is usually included in the gplpv driver but iirc has to be installed seperately.. 2013/2/18 jacek burghardt : > I was testing something and xl reboot does not do anything xen states domain > xx rebooting but it seems nothing is being send to server 2012 . > > > On Sun, Feb 17, 2013 at 3:26 PM, James Harper > wrote: >> >> > Also, don't get your hopes too high on the new gplpv drivers cause >> > afaik James uses a Win7 for testing his drivers and I haven't heard >> > from anyone testing them on Win2012 yet. But never the less I added >> > him in cc, maybe he can clerify the situation a bit more. >> > >> >> 2012 works (as in boots and runs) but I haven't done any performance >> testing yet. >> >> Windows 8 has a feature where by default when you say shutdown it actually >> hibernates instead, and I'm having a bit of trouble getting hibernate >> working (or specifically, resume from hibernate). I think it won't actually >> matter too much because on resume from hibernate, windows uses bios calls to >> load the crash dump and this is horribly slow because it goes via qemu not >> gplpv so most people would turn off the feature, but I'd still like to have >> it working so a default install of win8 works and I don't get emails asking >> why it crashed etc. >> >> James >> >> > _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Mon Feb 18 22:35:38 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 18 Feb 2013 22:35: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 1U7ZIU-0007i7-8T; Mon, 18 Feb 2013 22:34:54 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U7ZIR-0007hy-Pu for xen-users@lists.xen.org; Mon, 18 Feb 2013 22:34:52 +0000 Received: from [85.158.137.99:56750] by server-13.bemta-3.messagelabs.com id 27/51-20653-A8CA2215; Mon, 18 Feb 2013 22:34:50 +0000 X-Env-Sender: matthias.kannenberg@googlemail.com X-Msg-Ref: server-10.tower-217.messagelabs.com!1361226890!21156160!1 X-Originating-IP: [74.125.82.182] X-SpamReason: No, hits=0.3 required=7.0 tests=RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 30964 invoked from network); 18 Feb 2013 22:34:50 -0000 Received: from mail-we0-f182.google.com (HELO mail-we0-f182.google.com) (74.125.82.182) by server-10.tower-217.messagelabs.com with RC4-SHA encrypted SMTP; 18 Feb 2013 22:34:50 -0000 Received: by mail-we0-f182.google.com with SMTP id t57so5172754wey.41 for ; Mon, 18 Feb 2013 14:34:50 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=20120113; h=x-received:mime-version:in-reply-to:references:from:date:message-id :subject:to:cc:content-type; bh=HruSCD3wF2YzqlN0hvnFTXP7qtCDi5hFrPFsO/YrLbM=; b=WTSHUfpy9MW2yIkFSbEwgbDEefLct9CSVwpXf9/RL9k0OyBw2swVRKdVhzXsKCI2xS usDYsxWGNeOWqvaW1XsLsHPMYURrJy+1r6cc5Jc2jHmd5uqRfFTizkhC+NK9m2DBnsEa 25pevHtCkP7xcsFHC/ARbvvscWDcGaiXvFfPhTfrKPi4EGIqxrw3m806DDADfh3rNOBl 7t+WVN7STtt7FJsruxkC8All6oX0bPNMt2XbW7UAg5ZSnCLzgDsiC/vHmrs8yMhP8Sbt Z8cEO1LahArWKVnrVLnf/DUmfAzhq79y9Hjn7L+A548+k1yTWNNGMEET86XzPIp2SRxj s93g== X-Received: by 10.194.19.97 with SMTP id d1mr22142328wje.52.1361226890087; Mon, 18 Feb 2013 14:34:50 -0800 (PST) MIME-Version: 1.0 Received: by 10.194.80.68 with HTTP; Mon, 18 Feb 2013 14:34:30 -0800 (PST) In-Reply-To: References: <6035A0D088A63A46850C3988ED045A4B3567D7E6@BITCOM1.int.sbss.com.au> From: Matthias Date: Mon, 18 Feb 2013 23:34:30 +0100 Message-ID: To: jacek burghardt Cc: "xen-users@lists.xen.org" , James Harper Subject: Re: [Xen-users] gplpv drivers X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org Did you also install the xen reboot service? Since windows can't interprete the external shutdown request, you need a specific service who listens to it.. this is usually included in the gplpv driver but iirc has to be installed seperately.. 2013/2/18 jacek burghardt : > I was testing something and xl reboot does not do anything xen states domain > xx rebooting but it seems nothing is being send to server 2012 . > > > On Sun, Feb 17, 2013 at 3:26 PM, James Harper > wrote: >> >> > Also, don't get your hopes too high on the new gplpv drivers cause >> > afaik James uses a Win7 for testing his drivers and I haven't heard >> > from anyone testing them on Win2012 yet. But never the less I added >> > him in cc, maybe he can clerify the situation a bit more. >> > >> >> 2012 works (as in boots and runs) but I haven't done any performance >> testing yet. >> >> Windows 8 has a feature where by default when you say shutdown it actually >> hibernates instead, and I'm having a bit of trouble getting hibernate >> working (or specifically, resume from hibernate). I think it won't actually >> matter too much because on resume from hibernate, windows uses bios calls to >> load the crash dump and this is horribly slow because it goes via qemu not >> gplpv so most people would turn off the feature, but I'd still like to have >> it working so a default install of win8 works and I don't get emails asking >> why it crashed etc. >> >> James >> >> > _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Mon Feb 18 22:35:54 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 18 Feb 2013 22:35: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 1U7ZIs-0007jy-TV; Mon, 18 Feb 2013 22:35:18 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U7ZIr-0007jc-6Y for xen-users@lists.xen.org; Mon, 18 Feb 2013 22:35:17 +0000 Received: from [85.158.143.99:38138] by server-1.bemta-4.messagelabs.com id 2F/39-08839-4ACA2215; Mon, 18 Feb 2013 22:35:16 +0000 X-Env-Sender: james.harper@bendigoit.com.au X-Msg-Ref: server-7.tower-216.messagelabs.com!1361226912!24712639!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.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 8667 invoked from network); 18 Feb 2013 22:35:15 -0000 Received: from smtp1.bendigoit.com.au (HELO smtp1.bendigoit.com.au) (203.16.224.4) by server-7.tower-216.messagelabs.com with AES256-SHA encrypted SMTP; 18 Feb 2013 22:35:15 -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 1U7ZIh-0005Zb-Bz; Tue, 19 Feb 2013 09:35:07 +1100 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.0438.000; Tue, 19 Feb 2013 09:35:07 +1100 From: James Harper To: jacek burghardt Thread-Topic: [Xen-users] gplpv drivers Thread-Index: AQHODNUEvK/f6C0a2kKmdL+CFSvrqZh9fFmAgADIxHyAAFvWIIAA0IgAgADFFcA= Date: Mon, 18 Feb 2013 22:35:06 +0000 Message-ID: <6035A0D088A63A46850C3988ED045A4B35680118@BITCOM1.int.sbss.com.au> References: <6035A0D088A63A46850C3988ED045A4B3567D7E6@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:2088:5a93:4fa0:263e] x-tm-as-product-ver: SMEX-10.2.0.2087-7.000.1014-19646.002 x-tm-as-result: No--26.445400-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" , Matthias Subject: Re: [Xen-users] gplpv drivers X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: 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 was testing something and xl reboot does not do anything xen states > domain xx rebooting but it seems nothing is being send to server 2012 . > That would happen if shutdownmon service wasn't running. Can you check that? Otherwise install the debug version of the drivers and send me the output of /var/log/xen/qemu-dm-.log after issuing the reboot. James _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Mon Feb 18 22:35:54 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 18 Feb 2013 22:35: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 1U7ZIs-0007jy-TV; Mon, 18 Feb 2013 22:35:18 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U7ZIr-0007jc-6Y for xen-users@lists.xen.org; Mon, 18 Feb 2013 22:35:17 +0000 Received: from [85.158.143.99:38138] by server-1.bemta-4.messagelabs.com id 2F/39-08839-4ACA2215; Mon, 18 Feb 2013 22:35:16 +0000 X-Env-Sender: james.harper@bendigoit.com.au X-Msg-Ref: server-7.tower-216.messagelabs.com!1361226912!24712639!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.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 8667 invoked from network); 18 Feb 2013 22:35:15 -0000 Received: from smtp1.bendigoit.com.au (HELO smtp1.bendigoit.com.au) (203.16.224.4) by server-7.tower-216.messagelabs.com with AES256-SHA encrypted SMTP; 18 Feb 2013 22:35:15 -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 1U7ZIh-0005Zb-Bz; Tue, 19 Feb 2013 09:35:07 +1100 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.0438.000; Tue, 19 Feb 2013 09:35:07 +1100 From: James Harper To: jacek burghardt Thread-Topic: [Xen-users] gplpv drivers Thread-Index: AQHODNUEvK/f6C0a2kKmdL+CFSvrqZh9fFmAgADIxHyAAFvWIIAA0IgAgADFFcA= Date: Mon, 18 Feb 2013 22:35:06 +0000 Message-ID: <6035A0D088A63A46850C3988ED045A4B35680118@BITCOM1.int.sbss.com.au> References: <6035A0D088A63A46850C3988ED045A4B3567D7E6@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:2088:5a93:4fa0:263e] x-tm-as-product-ver: SMEX-10.2.0.2087-7.000.1014-19646.002 x-tm-as-result: No--26.445400-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" , Matthias Subject: Re: [Xen-users] gplpv drivers X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: 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 was testing something and xl reboot does not do anything xen states > domain xx rebooting but it seems nothing is being send to server 2012 . > That would happen if shutdownmon service wasn't running. Can you check that? Otherwise install the debug version of the drivers and send me the output of /var/log/xen/qemu-dm-.log after issuing the reboot. James _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Mon Feb 18 22:40:34 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 18 Feb 2013 22:40: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 1U7ZNL-00087o-SY; Mon, 18 Feb 2013 22:39:55 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U7ZNK-00087f-0Z for xen-users@lists.xen.org; Mon, 18 Feb 2013 22:39:54 +0000 Received: from [85.158.143.35:31550] by server-2.bemta-4.messagelabs.com id 0F/8F-12656-9BDA2215; Mon, 18 Feb 2013 22:39:53 +0000 X-Env-Sender: james.harper@bendigoit.com.au X-Msg-Ref: server-9.tower-21.messagelabs.com!1361227175!4656254!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.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 2740 invoked from network); 18 Feb 2013 22:39:38 -0000 Received: from smtp1.bendigoit.com.au (HELO smtp1.bendigoit.com.au) (203.16.224.4) by server-9.tower-21.messagelabs.com with AES256-SHA encrypted SMTP; 18 Feb 2013 22:39:38 -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 1U7ZMy-0005cY-UE; Tue, 19 Feb 2013 09:39:33 +1100 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.0438.000; Tue, 19 Feb 2013 09:39:33 +1100 From: James Harper To: Matthias , jacek burghardt Thread-Topic: [Xen-users] gplpv drivers Thread-Index: AQHODNUEvK/f6C0a2kKmdL+CFSvrqZh9fFmAgADIxHyAAFvWIIAA0IgAgAAMrwCAALlu4A== Date: Mon, 18 Feb 2013 22:39:31 +0000 Message-ID: <6035A0D088A63A46850C3988ED045A4B356801C2@BITCOM1.int.sbss.com.au> References: <6035A0D088A63A46850C3988ED045A4B3567D7E6@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:2088:5a93:4fa0:263e] x-tm-as-product-ver: SMEX-10.2.0.2087-7.000.1014-19646.002 x-tm-as-result: No--28.484300-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] gplpv drivers X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org > > Did you also install the xen reboot service? Since windows can't > interprete the external shutdown request, you need a specific service > who listens to it.. this is usually included in the gplpv driver but > iirc has to be installed seperately.. > If you just click 'Next' and 'Continue' and 'Complete' without changing any defaults when installing GPLPV it should install everything. James _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Mon Feb 18 22:40:34 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 18 Feb 2013 22:40: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 1U7ZNL-00087o-SY; Mon, 18 Feb 2013 22:39:55 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U7ZNK-00087f-0Z for xen-users@lists.xen.org; Mon, 18 Feb 2013 22:39:54 +0000 Received: from [85.158.143.35:31550] by server-2.bemta-4.messagelabs.com id 0F/8F-12656-9BDA2215; Mon, 18 Feb 2013 22:39:53 +0000 X-Env-Sender: james.harper@bendigoit.com.au X-Msg-Ref: server-9.tower-21.messagelabs.com!1361227175!4656254!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.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 2740 invoked from network); 18 Feb 2013 22:39:38 -0000 Received: from smtp1.bendigoit.com.au (HELO smtp1.bendigoit.com.au) (203.16.224.4) by server-9.tower-21.messagelabs.com with AES256-SHA encrypted SMTP; 18 Feb 2013 22:39:38 -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 1U7ZMy-0005cY-UE; Tue, 19 Feb 2013 09:39:33 +1100 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.0438.000; Tue, 19 Feb 2013 09:39:33 +1100 From: James Harper To: Matthias , jacek burghardt Thread-Topic: [Xen-users] gplpv drivers Thread-Index: AQHODNUEvK/f6C0a2kKmdL+CFSvrqZh9fFmAgADIxHyAAFvWIIAA0IgAgAAMrwCAALlu4A== Date: Mon, 18 Feb 2013 22:39:31 +0000 Message-ID: <6035A0D088A63A46850C3988ED045A4B356801C2@BITCOM1.int.sbss.com.au> References: <6035A0D088A63A46850C3988ED045A4B3567D7E6@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:2088:5a93:4fa0:263e] x-tm-as-product-ver: SMEX-10.2.0.2087-7.000.1014-19646.002 x-tm-as-result: No--28.484300-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] gplpv drivers X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org > > Did you also install the xen reboot service? Since windows can't > interprete the external shutdown request, you need a specific service > who listens to it.. this is usually included in the gplpv driver but > iirc has to be installed seperately.. > If you just click 'Next' and 'Continue' and 'Complete' without changing any defaults when installing GPLPV it should install everything. James _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Mon Feb 18 22:42:51 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 18 Feb 2013 22:42: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 1U7ZPg-0008Qm-MO; Mon, 18 Feb 2013 22:42:20 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U7ZPf-0008QZ-KN for xen-users@lists.xen.org; Mon, 18 Feb 2013 22:42:19 +0000 Received: from [85.158.138.51:53777] by server-16.bemta-3.messagelabs.com id 98/F6-02727-A4EA2215; Mon, 18 Feb 2013 22:42:18 +0000 X-Env-Sender: jaceksburghardt@gmail.com X-Msg-Ref: server-11.tower-174.messagelabs.com!1361227336!28096578!1 X-Originating-IP: [209.85.210.177] 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.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 6301 invoked from network); 18 Feb 2013 22:42:17 -0000 Received: from mail-ia0-f177.google.com (HELO mail-ia0-f177.google.com) (209.85.210.177) by server-11.tower-174.messagelabs.com with RC4-SHA encrypted SMTP; 18 Feb 2013 22:42:17 -0000 Received: by mail-ia0-f177.google.com with SMTP id o25so775750iad.22 for ; Mon, 18 Feb 2013 14:42:16 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:content-type; bh=6o8meTijbRAkdk9XX+v6EzCSEd0KOTdgXLqRKub/EOw=; b=deXTwke9kVy2QuuByKC1vh+zrXrr0366+7/Qf9yUGZP5x35b6ze6cMS7ejveDVoln7 ThZWOnqWWAKQLdyiZr3fd0xzueCFvhKCo9jXr+VlLJAy5YdEC01sR0i2e1EcWAEdG36d gORgHsLNOZZ8CxfBW47ucVgw0mzbOHO6KtFRbLOIbv4LPvYBGL58xD3rUJQ0+TUqnD5Q LQo8r6dp7FHd2UmMHP/qWQq21kPsppCXOP8ESuCq/JtTB5d4ChHmBPEZCjT1A0dOPEVi e5jB+rkfpA29MhxAtppbSa9NUb29id257O3DxRY/h9QbjPN1wMNy1m4y6MN7ir6wiIWG S75A== MIME-Version: 1.0 X-Received: by 10.50.77.230 with SMTP id v6mr7637916igw.29.1361227335970; Mon, 18 Feb 2013 14:42:15 -0800 (PST) Received: by 10.42.41.5 with HTTP; Mon, 18 Feb 2013 14:42:15 -0800 (PST) In-Reply-To: <6035A0D088A63A46850C3988ED045A4B35680118@BITCOM1.int.sbss.com.au> References: <6035A0D088A63A46850C3988ED045A4B3567D7E6@BITCOM1.int.sbss.com.au> <6035A0D088A63A46850C3988ED045A4B35680118@BITCOM1.int.sbss.com.au> Date: Mon, 18 Feb 2013 15:42:15 -0700 Message-ID: From: jacek burghardt To: "xen-users@lists.xen.org" Subject: Re: [Xen-users] gplpv drivers X-BeenThere: xen-users@lists.xen.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="===============7491779380256804606==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============7491779380256804606== Content-Type: multipart/alternative; boundary=e89a8f3ba87fd1b05904d6076f22 --e89a8f3ba87fd1b05904d6076f22 Content-Type: text/plain; charset=ISO-8859-1 Well my other two servers don't have any issues as they run older version of 4.3. I assume that xl reboot should simulate key press acpic sending proper command to server 2012. My other servers running servers 2012 will reboot with xl reboot and they acknowledge the fact that signal was send to reboot server. On Mon, Feb 18, 2013 at 3:35 PM, James Harper wrote: > > > > I was testing something and xl reboot does not do anything xen states > > domain xx rebooting but it seems nothing is being send to server 2012 . > > > > That would happen if shutdownmon service wasn't running. Can you check > that? > > Otherwise install the debug version of the drivers and send me the output > of /var/log/xen/qemu-dm-.log after issuing the reboot. > > James > --e89a8f3ba87fd1b05904d6076f22 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Well my other two servers don't have any issues as they run older versi= on of 4.3. I assume that xl reboot should simulate key press acpic=A0 sendi= ng proper command to server 2012. My other servers running servers 2012 wil= l reboot with xl reboot and they acknowledge the fact that signal was send = to reboot server.

On Mon, Feb 18, 2013 at 3:35 PM, James Harpe= r <james.harper@bendigoit.com.au> wrote:
>
> I was testing something and xl reboot does not do anything xen states<= br> > domain xx rebooting but it seems nothing is being send to server 2012 = .
>

That would happen if shutdownmon service wasn't running. Can you = check that?

Otherwise install the debug version of the drivers and send me the output o= f /var/log/xen/qemu-dm-<domu name>.log after issuing the reboot.

James

--e89a8f3ba87fd1b05904d6076f22-- --===============7491779380256804606== 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 --===============7491779380256804606==-- From xen-users-bounces@lists.xen.org Mon Feb 18 22:42:51 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 18 Feb 2013 22:42: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 1U7ZPg-0008Qm-MO; Mon, 18 Feb 2013 22:42:20 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U7ZPf-0008QZ-KN for xen-users@lists.xen.org; Mon, 18 Feb 2013 22:42:19 +0000 Received: from [85.158.138.51:53777] by server-16.bemta-3.messagelabs.com id 98/F6-02727-A4EA2215; Mon, 18 Feb 2013 22:42:18 +0000 X-Env-Sender: jaceksburghardt@gmail.com X-Msg-Ref: server-11.tower-174.messagelabs.com!1361227336!28096578!1 X-Originating-IP: [209.85.210.177] 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.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 6301 invoked from network); 18 Feb 2013 22:42:17 -0000 Received: from mail-ia0-f177.google.com (HELO mail-ia0-f177.google.com) (209.85.210.177) by server-11.tower-174.messagelabs.com with RC4-SHA encrypted SMTP; 18 Feb 2013 22:42:17 -0000 Received: by mail-ia0-f177.google.com with SMTP id o25so775750iad.22 for ; Mon, 18 Feb 2013 14:42:16 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:content-type; bh=6o8meTijbRAkdk9XX+v6EzCSEd0KOTdgXLqRKub/EOw=; b=deXTwke9kVy2QuuByKC1vh+zrXrr0366+7/Qf9yUGZP5x35b6ze6cMS7ejveDVoln7 ThZWOnqWWAKQLdyiZr3fd0xzueCFvhKCo9jXr+VlLJAy5YdEC01sR0i2e1EcWAEdG36d gORgHsLNOZZ8CxfBW47ucVgw0mzbOHO6KtFRbLOIbv4LPvYBGL58xD3rUJQ0+TUqnD5Q LQo8r6dp7FHd2UmMHP/qWQq21kPsppCXOP8ESuCq/JtTB5d4ChHmBPEZCjT1A0dOPEVi e5jB+rkfpA29MhxAtppbSa9NUb29id257O3DxRY/h9QbjPN1wMNy1m4y6MN7ir6wiIWG S75A== MIME-Version: 1.0 X-Received: by 10.50.77.230 with SMTP id v6mr7637916igw.29.1361227335970; Mon, 18 Feb 2013 14:42:15 -0800 (PST) Received: by 10.42.41.5 with HTTP; Mon, 18 Feb 2013 14:42:15 -0800 (PST) In-Reply-To: <6035A0D088A63A46850C3988ED045A4B35680118@BITCOM1.int.sbss.com.au> References: <6035A0D088A63A46850C3988ED045A4B3567D7E6@BITCOM1.int.sbss.com.au> <6035A0D088A63A46850C3988ED045A4B35680118@BITCOM1.int.sbss.com.au> Date: Mon, 18 Feb 2013 15:42:15 -0700 Message-ID: From: jacek burghardt To: "xen-users@lists.xen.org" Subject: Re: [Xen-users] gplpv drivers X-BeenThere: xen-users@lists.xen.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="===============7491779380256804606==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============7491779380256804606== Content-Type: multipart/alternative; boundary=e89a8f3ba87fd1b05904d6076f22 --e89a8f3ba87fd1b05904d6076f22 Content-Type: text/plain; charset=ISO-8859-1 Well my other two servers don't have any issues as they run older version of 4.3. I assume that xl reboot should simulate key press acpic sending proper command to server 2012. My other servers running servers 2012 will reboot with xl reboot and they acknowledge the fact that signal was send to reboot server. On Mon, Feb 18, 2013 at 3:35 PM, James Harper wrote: > > > > I was testing something and xl reboot does not do anything xen states > > domain xx rebooting but it seems nothing is being send to server 2012 . > > > > That would happen if shutdownmon service wasn't running. Can you check > that? > > Otherwise install the debug version of the drivers and send me the output > of /var/log/xen/qemu-dm-.log after issuing the reboot. > > James > --e89a8f3ba87fd1b05904d6076f22 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Well my other two servers don't have any issues as they run older versi= on of 4.3. I assume that xl reboot should simulate key press acpic=A0 sendi= ng proper command to server 2012. My other servers running servers 2012 wil= l reboot with xl reboot and they acknowledge the fact that signal was send = to reboot server.

On Mon, Feb 18, 2013 at 3:35 PM, James Harpe= r <james.harper@bendigoit.com.au> wrote:
>
> I was testing something and xl reboot does not do anything xen states<= br> > domain xx rebooting but it seems nothing is being send to server 2012 = .
>

That would happen if shutdownmon service wasn't running. Can you = check that?

Otherwise install the debug version of the drivers and send me the output o= f /var/log/xen/qemu-dm-<domu name>.log after issuing the reboot.

James

--e89a8f3ba87fd1b05904d6076f22-- --===============7491779380256804606== 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 --===============7491779380256804606==-- From xen-users-bounces@lists.xen.org Mon Feb 18 22:44:05 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 18 Feb 2013 22:44: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 1U7ZQt-0000Bd-To; Mon, 18 Feb 2013 22:43:35 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U7ZQs-0000BB-FB for xen-users@lists.xen.org; Mon, 18 Feb 2013 22:43:34 +0000 Received: from [85.158.137.99:28659] by server-13.bemta-3.messagelabs.com id 33/E4-20653-59EA2215; Mon, 18 Feb 2013 22:43:33 +0000 X-Env-Sender: jaceksburghardt@gmail.com X-Msg-Ref: server-13.tower-217.messagelabs.com!1361227411!22000189!1 X-Originating-IP: [209.85.223.174] X-SpamReason: No, hits=1.4 required=7.0 tests=BODY_RANDOM_LONG, HTML_40_50, HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14, RCVD_BY_IP, spamassassin: X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 7937 invoked from network); 18 Feb 2013 22:43:32 -0000 Received: from mail-ie0-f174.google.com (HELO mail-ie0-f174.google.com) (209.85.223.174) by server-13.tower-217.messagelabs.com with RC4-SHA encrypted SMTP; 18 Feb 2013 22:43:32 -0000 Received: by mail-ie0-f174.google.com with SMTP id k10so7810418iea.33 for ; Mon, 18 Feb 2013 14:43:30 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:content-type; bh=xQYbcDMyBaGPgJW+AwihjcNO+UEix5fRSmKY4Z0muvE=; b=lfXKWnwtCVq9uH4RytdSKdbRUwPGHdyEZybMplrVotetFoFBmzKi70qSbYQcb/tmM0 9/xIcxU6wN7IRXBIZEkV6+he2Oq8LRIbSHIy0E9B9cVw45DqCKrbB142SDaXLzAiw/Lq D1wAIX5eqT+vpTuQMdCrRxGcoWfGE2Hhy5HQwc6NujsO34txS5Pa/jrpM5rG0qfq8EO8 Sae7rGCQbGd6Tb0x2JKGKQpZeP8xf+jf4UlN9cFES6FV6WsL+ufMjmzfHPbO4wgQEu/h E50xG0BVeP2VU9PpaYGxBAXBWxAHCu6zV9Hj7zUMLOZZuWuO7mGer/9OnOZSIcWozx1B XJ6A== MIME-Version: 1.0 X-Received: by 10.50.17.163 with SMTP id p3mr2039017igd.90.1361227410845; Mon, 18 Feb 2013 14:43:30 -0800 (PST) Received: by 10.42.41.5 with HTTP; Mon, 18 Feb 2013 14:43:30 -0800 (PST) In-Reply-To: References: <6035A0D088A63A46850C3988ED045A4B3567D7E6@BITCOM1.int.sbss.com.au> <6035A0D088A63A46850C3988ED045A4B35680118@BITCOM1.int.sbss.com.au> Date: Mon, 18 Feb 2013 15:43:30 -0700 Message-ID: From: jacek burghardt To: "xen-users@lists.xen.org" Subject: Re: [Xen-users] gplpv drivers X-BeenThere: xen-users@lists.xen.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="===============5600602438494724842==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============5600602438494724842== Content-Type: multipart/alternative; boundary=14dae93407cf482ebd04d6077473 --14dae93407cf482ebd04d6077473 Content-Type: text/plain; charset=ISO-8859-1 How do i get debugging with xl ? On Mon, Feb 18, 2013 at 3:42 PM, jacek burghardt wrote: > Well my other two servers don't have any issues as they run older version > of 4.3. I assume that xl reboot should simulate key press acpic sending > proper command to server 2012. My other servers running servers 2012 will > reboot with xl reboot and they acknowledge the fact that signal was send to > reboot server. > > On Mon, Feb 18, 2013 at 3:35 PM, James Harper < > james.harper@bendigoit.com.au> wrote: > >> > >> > I was testing something and xl reboot does not do anything xen states >> > domain xx rebooting but it seems nothing is being send to server 2012 . >> > >> >> That would happen if shutdownmon service wasn't running. Can you check >> that? >> >> Otherwise install the debug version of the drivers and send me the output >> of /var/log/xen/qemu-dm-.log after issuing the reboot. >> >> James >> > > --14dae93407cf482ebd04d6077473 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable How do i get debugging with xl ?

On Mon, = Feb 18, 2013 at 3:42 PM, jacek burghardt <jaceksburghardt@gmail.co= m> wrote:
Well my other two servers don't have any= issues as they run older version of 4.3. I assume that xl reboot should si= mulate key press acpic=A0 sending proper command to server 2012. My other s= ervers running servers 2012 will reboot with xl reboot and they acknowledge= the fact that signal was send to reboot server.

On Mon, Feb 18, 2013 at 3:35 PM, James Harpe= r <james.harper@bendigoit.com.au> wrote:
>
> I was testing something and xl reboot does not do anything xen states<= br> > domain xx rebooting but it seems nothing is being send to server 2012 = .
>

That would happen if shutdownmon service wasn't running. Can you = check that?

Otherwise install the debug version of the drivers and send me the output o= f /var/log/xen/qemu-dm-<domu name>.log after issuing the reboot.

James


--14dae93407cf482ebd04d6077473-- --===============5600602438494724842== 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 --===============5600602438494724842==-- From xen-users-bounces@lists.xen.org Mon Feb 18 22:44:05 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 18 Feb 2013 22:44: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 1U7ZQt-0000Bd-To; Mon, 18 Feb 2013 22:43:35 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U7ZQs-0000BB-FB for xen-users@lists.xen.org; Mon, 18 Feb 2013 22:43:34 +0000 Received: from [85.158.137.99:28659] by server-13.bemta-3.messagelabs.com id 33/E4-20653-59EA2215; Mon, 18 Feb 2013 22:43:33 +0000 X-Env-Sender: jaceksburghardt@gmail.com X-Msg-Ref: server-13.tower-217.messagelabs.com!1361227411!22000189!1 X-Originating-IP: [209.85.223.174] X-SpamReason: No, hits=1.4 required=7.0 tests=BODY_RANDOM_LONG, HTML_40_50, HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14, RCVD_BY_IP, spamassassin: X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 7937 invoked from network); 18 Feb 2013 22:43:32 -0000 Received: from mail-ie0-f174.google.com (HELO mail-ie0-f174.google.com) (209.85.223.174) by server-13.tower-217.messagelabs.com with RC4-SHA encrypted SMTP; 18 Feb 2013 22:43:32 -0000 Received: by mail-ie0-f174.google.com with SMTP id k10so7810418iea.33 for ; Mon, 18 Feb 2013 14:43:30 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:content-type; bh=xQYbcDMyBaGPgJW+AwihjcNO+UEix5fRSmKY4Z0muvE=; b=lfXKWnwtCVq9uH4RytdSKdbRUwPGHdyEZybMplrVotetFoFBmzKi70qSbYQcb/tmM0 9/xIcxU6wN7IRXBIZEkV6+he2Oq8LRIbSHIy0E9B9cVw45DqCKrbB142SDaXLzAiw/Lq D1wAIX5eqT+vpTuQMdCrRxGcoWfGE2Hhy5HQwc6NujsO34txS5Pa/jrpM5rG0qfq8EO8 Sae7rGCQbGd6Tb0x2JKGKQpZeP8xf+jf4UlN9cFES6FV6WsL+ufMjmzfHPbO4wgQEu/h E50xG0BVeP2VU9PpaYGxBAXBWxAHCu6zV9Hj7zUMLOZZuWuO7mGer/9OnOZSIcWozx1B XJ6A== MIME-Version: 1.0 X-Received: by 10.50.17.163 with SMTP id p3mr2039017igd.90.1361227410845; Mon, 18 Feb 2013 14:43:30 -0800 (PST) Received: by 10.42.41.5 with HTTP; Mon, 18 Feb 2013 14:43:30 -0800 (PST) In-Reply-To: References: <6035A0D088A63A46850C3988ED045A4B3567D7E6@BITCOM1.int.sbss.com.au> <6035A0D088A63A46850C3988ED045A4B35680118@BITCOM1.int.sbss.com.au> Date: Mon, 18 Feb 2013 15:43:30 -0700 Message-ID: From: jacek burghardt To: "xen-users@lists.xen.org" Subject: Re: [Xen-users] gplpv drivers X-BeenThere: xen-users@lists.xen.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="===============5600602438494724842==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============5600602438494724842== Content-Type: multipart/alternative; boundary=14dae93407cf482ebd04d6077473 --14dae93407cf482ebd04d6077473 Content-Type: text/plain; charset=ISO-8859-1 How do i get debugging with xl ? On Mon, Feb 18, 2013 at 3:42 PM, jacek burghardt wrote: > Well my other two servers don't have any issues as they run older version > of 4.3. I assume that xl reboot should simulate key press acpic sending > proper command to server 2012. My other servers running servers 2012 will > reboot with xl reboot and they acknowledge the fact that signal was send to > reboot server. > > On Mon, Feb 18, 2013 at 3:35 PM, James Harper < > james.harper@bendigoit.com.au> wrote: > >> > >> > I was testing something and xl reboot does not do anything xen states >> > domain xx rebooting but it seems nothing is being send to server 2012 . >> > >> >> That would happen if shutdownmon service wasn't running. Can you check >> that? >> >> Otherwise install the debug version of the drivers and send me the output >> of /var/log/xen/qemu-dm-.log after issuing the reboot. >> >> James >> > > --14dae93407cf482ebd04d6077473 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable How do i get debugging with xl ?

On Mon, = Feb 18, 2013 at 3:42 PM, jacek burghardt <jaceksburghardt@gmail.co= m> wrote:
Well my other two servers don't have any= issues as they run older version of 4.3. I assume that xl reboot should si= mulate key press acpic=A0 sending proper command to server 2012. My other s= ervers running servers 2012 will reboot with xl reboot and they acknowledge= the fact that signal was send to reboot server.

On Mon, Feb 18, 2013 at 3:35 PM, James Harpe= r <james.harper@bendigoit.com.au> wrote:
>
> I was testing something and xl reboot does not do anything xen states<= br> > domain xx rebooting but it seems nothing is being send to server 2012 = .
>

That would happen if shutdownmon service wasn't running. Can you = check that?

Otherwise install the debug version of the drivers and send me the output o= f /var/log/xen/qemu-dm-<domu name>.log after issuing the reboot.

James


--14dae93407cf482ebd04d6077473-- --===============5600602438494724842== 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 --===============5600602438494724842==-- From xen-users-bounces@lists.xen.org Mon Feb 18 22:53:47 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 18 Feb 2013 22:53: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 1U7ZaG-0000x8-Gm; Mon, 18 Feb 2013 22:53:16 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U7ZaE-0000x0-VM for xen-users@lists.xen.org; Mon, 18 Feb 2013 22:53:15 +0000 Received: from [193.109.254.147:45636] by server-16.bemta-14.messagelabs.com id FE/39-25906-AD0B2215; Mon, 18 Feb 2013 22:53:14 +0000 X-Env-Sender: jaceksburghardt@gmail.com X-Msg-Ref: server-6.tower-27.messagelabs.com!1361227990!3194538!1 X-Originating-IP: [209.85.223.176] X-SpamReason: No, hits=1.4 required=7.0 tests=BODY_RANDOM_LONG, HTML_40_50, HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14, RCVD_BY_IP, spamassassin: X-StarScan-Received: X-StarScan-Version: 6.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 6333 invoked from network); 18 Feb 2013 22:53:13 -0000 Received: from mail-ie0-f176.google.com (HELO mail-ie0-f176.google.com) (209.85.223.176) by server-6.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 18 Feb 2013 22:53:13 -0000 Received: by mail-ie0-f176.google.com with SMTP id k13so7721077iea.35 for ; Mon, 18 Feb 2013 14:53:10 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:content-type; bh=tAVaeo+bw1pCgWc8h85oaoN5ZE0CztMTdk2dHfa0mn0=; b=ezcFFJ2vsDxfYJuZAWVPw66fVQ1WOPYCvbr7+3xVwsz0Jx0Ul8IN66IC5Jipt3s5jN Y7tXE7RQ7dTBkj3AOuTTpZTsrsyLmXiF5QGL332UONo+0FxD/dbQ9ETK8yoBkFznxVVd 7QkqlAMBfaRoSP8+tTpyuXNPC7kMGBwKiS53Jv5q8lvPaT2cbnptsJbmsLJLCpWacJvr C4rkqZScDhAcrc2krir4GtMbjLHqL0c7jOO2qgyvbAkqkIa922l8zcZ5TtsFy+nYdVt/ p4UsNsp6n18dS8rv7LKQx2Lgvh8nOqwpt2RLHxCtgbXD6Izedvzo/w5r7mLpO8TkFupa QACQ== MIME-Version: 1.0 X-Received: by 10.42.201.73 with SMTP id ez9mr6094717icb.29.1361227990326; Mon, 18 Feb 2013 14:53:10 -0800 (PST) Received: by 10.42.41.5 with HTTP; Mon, 18 Feb 2013 14:53:10 -0800 (PST) In-Reply-To: References: <6035A0D088A63A46850C3988ED045A4B3567D7E6@BITCOM1.int.sbss.com.au> <6035A0D088A63A46850C3988ED045A4B35680118@BITCOM1.int.sbss.com.au> Date: Mon, 18 Feb 2013 15:53:10 -0700 Message-ID: From: jacek burghardt To: "xen-users@lists.xen.org" Subject: Re: [Xen-users] gplpv drivers X-BeenThere: xen-users@lists.xen.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="===============0426637402736304457==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============0426637402736304457== Content-Type: multipart/alternative; boundary=20cf301cc498d25c6004d60796de --20cf301cc498d25c6004d60796de Content-Type: text/plain; charset=ISO-8859-1 I tested xl reboot on my other server with older version of 4.3 the server 2012 rebooted and domain was destroyed and recreated . So it is clear that there is bug in latest 4.3 code On Mon, Feb 18, 2013 at 3:43 PM, jacek burghardt wrote: > How do i get debugging with xl ? > > > On Mon, Feb 18, 2013 at 3:42 PM, jacek burghardt < > jaceksburghardt@gmail.com> wrote: > >> Well my other two servers don't have any issues as they run older version >> of 4.3. I assume that xl reboot should simulate key press acpic sending >> proper command to server 2012. My other servers running servers 2012 will >> reboot with xl reboot and they acknowledge the fact that signal was send to >> reboot server. >> >> On Mon, Feb 18, 2013 at 3:35 PM, James Harper < >> james.harper@bendigoit.com.au> wrote: >> >>> > >>> > I was testing something and xl reboot does not do anything xen states >>> > domain xx rebooting but it seems nothing is being send to server 2012 . >>> > >>> >>> That would happen if shutdownmon service wasn't running. Can you check >>> that? >>> >>> Otherwise install the debug version of the drivers and send me the >>> output of /var/log/xen/qemu-dm-.log after issuing the reboot. >>> >>> James >>> >> >> > --20cf301cc498d25c6004d60796de Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable I tested xl reboot on my other server with older version of 4.3 the server = 2012 rebooted and domain was destroyed and recreated . So it is clear that = there is bug in latest=A0 4.3 code

On Mo= n, Feb 18, 2013 at 3:43 PM, jacek burghardt <jaceksburghardt@gma= il.com> wrote:
How do i get debugging with xl ?


On Mon, Fe= b 18, 2013 at 3:42 PM, jacek burghardt <jaceksburghardt@gmail.com<= /a>> wrote:
Well my other two servers don't have any= issues as they run older version of 4.3. I assume that xl reboot should si= mulate key press acpic=A0 sending proper command to server 2012. My other s= ervers running servers 2012 will reboot with xl reboot and they acknowledge= the fact that signal was send to reboot server.

On Mon, Feb 18, 2013 at 3:35 PM, James Harpe= r <james.harper@bendigoit.com.au> wrote:
>
> I was testing something and xl reboot does not do anything xen states<= br> > domain xx rebooting but it seems nothing is being send to server 2012 = .
>

That would happen if shutdownmon service wasn't running. Can you = check that?

Otherwise install the debug version of the drivers and send me the output o= f /var/log/xen/qemu-dm-<domu name>.log after issuing the reboot.

James



--20cf301cc498d25c6004d60796de-- --===============0426637402736304457== 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 --===============0426637402736304457==-- From xen-users-bounces@lists.xen.org Mon Feb 18 22:53:47 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 18 Feb 2013 22:53: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 1U7ZaG-0000x8-Gm; Mon, 18 Feb 2013 22:53:16 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U7ZaE-0000x0-VM for xen-users@lists.xen.org; Mon, 18 Feb 2013 22:53:15 +0000 Received: from [193.109.254.147:45636] by server-16.bemta-14.messagelabs.com id FE/39-25906-AD0B2215; Mon, 18 Feb 2013 22:53:14 +0000 X-Env-Sender: jaceksburghardt@gmail.com X-Msg-Ref: server-6.tower-27.messagelabs.com!1361227990!3194538!1 X-Originating-IP: [209.85.223.176] X-SpamReason: No, hits=1.4 required=7.0 tests=BODY_RANDOM_LONG, HTML_40_50, HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14, RCVD_BY_IP, spamassassin: X-StarScan-Received: X-StarScan-Version: 6.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 6333 invoked from network); 18 Feb 2013 22:53:13 -0000 Received: from mail-ie0-f176.google.com (HELO mail-ie0-f176.google.com) (209.85.223.176) by server-6.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 18 Feb 2013 22:53:13 -0000 Received: by mail-ie0-f176.google.com with SMTP id k13so7721077iea.35 for ; Mon, 18 Feb 2013 14:53:10 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:content-type; bh=tAVaeo+bw1pCgWc8h85oaoN5ZE0CztMTdk2dHfa0mn0=; b=ezcFFJ2vsDxfYJuZAWVPw66fVQ1WOPYCvbr7+3xVwsz0Jx0Ul8IN66IC5Jipt3s5jN Y7tXE7RQ7dTBkj3AOuTTpZTsrsyLmXiF5QGL332UONo+0FxD/dbQ9ETK8yoBkFznxVVd 7QkqlAMBfaRoSP8+tTpyuXNPC7kMGBwKiS53Jv5q8lvPaT2cbnptsJbmsLJLCpWacJvr C4rkqZScDhAcrc2krir4GtMbjLHqL0c7jOO2qgyvbAkqkIa922l8zcZ5TtsFy+nYdVt/ p4UsNsp6n18dS8rv7LKQx2Lgvh8nOqwpt2RLHxCtgbXD6Izedvzo/w5r7mLpO8TkFupa QACQ== MIME-Version: 1.0 X-Received: by 10.42.201.73 with SMTP id ez9mr6094717icb.29.1361227990326; Mon, 18 Feb 2013 14:53:10 -0800 (PST) Received: by 10.42.41.5 with HTTP; Mon, 18 Feb 2013 14:53:10 -0800 (PST) In-Reply-To: References: <6035A0D088A63A46850C3988ED045A4B3567D7E6@BITCOM1.int.sbss.com.au> <6035A0D088A63A46850C3988ED045A4B35680118@BITCOM1.int.sbss.com.au> Date: Mon, 18 Feb 2013 15:53:10 -0700 Message-ID: From: jacek burghardt To: "xen-users@lists.xen.org" Subject: Re: [Xen-users] gplpv drivers X-BeenThere: xen-users@lists.xen.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="===============0426637402736304457==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============0426637402736304457== Content-Type: multipart/alternative; boundary=20cf301cc498d25c6004d60796de --20cf301cc498d25c6004d60796de Content-Type: text/plain; charset=ISO-8859-1 I tested xl reboot on my other server with older version of 4.3 the server 2012 rebooted and domain was destroyed and recreated . So it is clear that there is bug in latest 4.3 code On Mon, Feb 18, 2013 at 3:43 PM, jacek burghardt wrote: > How do i get debugging with xl ? > > > On Mon, Feb 18, 2013 at 3:42 PM, jacek burghardt < > jaceksburghardt@gmail.com> wrote: > >> Well my other two servers don't have any issues as they run older version >> of 4.3. I assume that xl reboot should simulate key press acpic sending >> proper command to server 2012. My other servers running servers 2012 will >> reboot with xl reboot and they acknowledge the fact that signal was send to >> reboot server. >> >> On Mon, Feb 18, 2013 at 3:35 PM, James Harper < >> james.harper@bendigoit.com.au> wrote: >> >>> > >>> > I was testing something and xl reboot does not do anything xen states >>> > domain xx rebooting but it seems nothing is being send to server 2012 . >>> > >>> >>> That would happen if shutdownmon service wasn't running. Can you check >>> that? >>> >>> Otherwise install the debug version of the drivers and send me the >>> output of /var/log/xen/qemu-dm-.log after issuing the reboot. >>> >>> James >>> >> >> > --20cf301cc498d25c6004d60796de Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable I tested xl reboot on my other server with older version of 4.3 the server = 2012 rebooted and domain was destroyed and recreated . So it is clear that = there is bug in latest=A0 4.3 code

On Mo= n, Feb 18, 2013 at 3:43 PM, jacek burghardt <jaceksburghardt@gma= il.com> wrote:
How do i get debugging with xl ?


On Mon, Fe= b 18, 2013 at 3:42 PM, jacek burghardt <jaceksburghardt@gmail.com<= /a>> wrote:
Well my other two servers don't have any= issues as they run older version of 4.3. I assume that xl reboot should si= mulate key press acpic=A0 sending proper command to server 2012. My other s= ervers running servers 2012 will reboot with xl reboot and they acknowledge= the fact that signal was send to reboot server.

On Mon, Feb 18, 2013 at 3:35 PM, James Harpe= r <james.harper@bendigoit.com.au> wrote:
>
> I was testing something and xl reboot does not do anything xen states<= br> > domain xx rebooting but it seems nothing is being send to server 2012 = .
>

That would happen if shutdownmon service wasn't running. Can you = check that?

Otherwise install the debug version of the drivers and send me the output o= f /var/log/xen/qemu-dm-<domu name>.log after issuing the reboot.

James



--20cf301cc498d25c6004d60796de-- --===============0426637402736304457== 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 --===============0426637402736304457==-- From xen-users-bounces@lists.xen.org Mon Feb 18 23:06:27 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 18 Feb 2013 23:06: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 1U7ZmW-0001Zd-LV; Mon, 18 Feb 2013 23:05:56 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U7ZmU-0001ZS-Db for xen-users@lists.xen.org; Mon, 18 Feb 2013 23:05:54 +0000 Received: from [85.158.137.99:58909] by server-5.bemta-3.messagelabs.com id 66/3C-04457-1D3B2215; Mon, 18 Feb 2013 23:05:53 +0000 X-Env-Sender: james.harper@bendigoit.com.au X-Msg-Ref: server-14.tower-217.messagelabs.com!1361228749!18577675!1 X-Originating-IP: [203.16.224.4] X-SpamReason: No, hits=0.5 required=7.0 tests=BODY_RANDOM_LONG X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 25378 invoked from network); 18 Feb 2013 23:05:52 -0000 Received: from smtp1.bendigoit.com.au (HELO smtp1.bendigoit.com.au) (203.16.224.4) by server-14.tower-217.messagelabs.com with AES256-SHA encrypted SMTP; 18 Feb 2013 23:05:52 -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 1U7ZmL-0005oP-Dp; Tue, 19 Feb 2013 10:05:45 +1100 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.0438.000; Tue, 19 Feb 2013 10:05:45 +1100 From: James Harper To: Casey DeLorme , "xen-users@lists.xen.org" Thread-Topic: [Xen-users] xendomains stop and gplpv network questions Thread-Index: AQHODie9fXP2cXpPZEieAWQ5cLTG75iAO86g Date: Mon, 18 Feb 2013 23:05:43 +0000 Message-ID: <6035A0D088A63A46850C3988ED045A4B35680334@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: [2001:388:e000:712:2088:5a93:4fa0:263e] x-tm-as-product-ver: SMEX-10.2.0.2087-7.000.1014-19646.002 x-tm-as-result: No--30.973100-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] xendomains stop and gplpv network questions X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org > 1. Has anyone else been having trouble with the xendomains script? > > I am running 4.2 stable on Debian Wheezy, and the xendomains script does > not shut down my running domains (specifically two linux HVM's one with > PVHVM). > > When run manually via `service xendomains stop` or `/etc/init.d/xendomains > stop` it returns a success message, but my machines continue to run as > though nothing happened. That is a bit strange. Check the /etc/default/xendomains and see what the behaviours are set to... it shouldn't leave the domains running but maybe is set to save but save is failing? > When I shut down my computer without running `xl destroy` on the running > domains it locks up, my guess is because the domains are still running. > When you say 'locks up' do you mean dom0 gets part way through the shutdown tasks then hangs waiting for xen services to shut down? > > 2. Is anyone else having problems restarting network adapters on Windows > HVM's with GPLPV drivers? > > Without them it works fine, but with GPLPV installed if I disable and then > attempt to re-enable a network adapter the device disappears from the > machine. > > The only solution so far has been to reboot the HVM. > What Windows OS and what version of GPLPV? Sounds like a bug but I've disabled and enabled adapters lots of times without problems... James _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Mon Feb 18 23:06:27 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 18 Feb 2013 23:06: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 1U7ZmW-0001Zd-LV; Mon, 18 Feb 2013 23:05:56 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U7ZmU-0001ZS-Db for xen-users@lists.xen.org; Mon, 18 Feb 2013 23:05:54 +0000 Received: from [85.158.137.99:58909] by server-5.bemta-3.messagelabs.com id 66/3C-04457-1D3B2215; Mon, 18 Feb 2013 23:05:53 +0000 X-Env-Sender: james.harper@bendigoit.com.au X-Msg-Ref: server-14.tower-217.messagelabs.com!1361228749!18577675!1 X-Originating-IP: [203.16.224.4] X-SpamReason: No, hits=0.5 required=7.0 tests=BODY_RANDOM_LONG X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 25378 invoked from network); 18 Feb 2013 23:05:52 -0000 Received: from smtp1.bendigoit.com.au (HELO smtp1.bendigoit.com.au) (203.16.224.4) by server-14.tower-217.messagelabs.com with AES256-SHA encrypted SMTP; 18 Feb 2013 23:05:52 -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 1U7ZmL-0005oP-Dp; Tue, 19 Feb 2013 10:05:45 +1100 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.0438.000; Tue, 19 Feb 2013 10:05:45 +1100 From: James Harper To: Casey DeLorme , "xen-users@lists.xen.org" Thread-Topic: [Xen-users] xendomains stop and gplpv network questions Thread-Index: AQHODie9fXP2cXpPZEieAWQ5cLTG75iAO86g Date: Mon, 18 Feb 2013 23:05:43 +0000 Message-ID: <6035A0D088A63A46850C3988ED045A4B35680334@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: [2001:388:e000:712:2088:5a93:4fa0:263e] x-tm-as-product-ver: SMEX-10.2.0.2087-7.000.1014-19646.002 x-tm-as-result: No--30.973100-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] xendomains stop and gplpv network questions X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org > 1. Has anyone else been having trouble with the xendomains script? > > I am running 4.2 stable on Debian Wheezy, and the xendomains script does > not shut down my running domains (specifically two linux HVM's one with > PVHVM). > > When run manually via `service xendomains stop` or `/etc/init.d/xendomains > stop` it returns a success message, but my machines continue to run as > though nothing happened. That is a bit strange. Check the /etc/default/xendomains and see what the behaviours are set to... it shouldn't leave the domains running but maybe is set to save but save is failing? > When I shut down my computer without running `xl destroy` on the running > domains it locks up, my guess is because the domains are still running. > When you say 'locks up' do you mean dom0 gets part way through the shutdown tasks then hangs waiting for xen services to shut down? > > 2. Is anyone else having problems restarting network adapters on Windows > HVM's with GPLPV drivers? > > Without them it works fine, but with GPLPV installed if I disable and then > attempt to re-enable a network adapter the device disappears from the > machine. > > The only solution so far has been to reboot the HVM. > What Windows OS and what version of GPLPV? Sounds like a bug but I've disabled and enabled adapters lots of times without problems... James _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Mon Feb 18 23:28:37 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 18 Feb 2013 23:28: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 1U7a7g-00028l-TI; Mon, 18 Feb 2013 23:27:48 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U7a7f-00028g-Sq for xen-users@lists.xen.org; Mon, 18 Feb 2013 23:27:48 +0000 Received: from [193.109.254.147:44923] by server-3.bemta-14.messagelabs.com id 02/EB-22141-3F8B2215; Mon, 18 Feb 2013 23:27:47 +0000 X-Env-Sender: rshriram@cs.ubc.ca X-Msg-Ref: server-5.tower-27.messagelabs.com!1361230035!6416967!1 X-Originating-IP: [142.103.6.52] X-SpamReason: No, hits=0.3 required=7.0 tests=RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 18804 invoked from network); 18 Feb 2013 23:27:18 -0000 Received: from smtp.cs.ubc.ca (HELO smtp.cs.ubc.ca) (142.103.6.52) by server-5.tower-27.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 18 Feb 2013 23:27:18 -0000 Received: from mail-ie0-f176.google.com (mail-ie0-f176.google.com [209.85.223.176]) (authenticated bits=0) by smtp.cs.ubc.ca (8.14.3/8.13.6) with ESMTP id r1INRESx002883 (version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=FAIL) for ; Mon, 18 Feb 2013 15:27:14 -0800 Received: by mail-ie0-f176.google.com with SMTP id k13so7748334iea.35 for ; Mon, 18 Feb 2013 15:27:13 -0800 (PST) X-Received: by 10.42.42.69 with SMTP id s5mr6726590ice.2.1361230032808; Mon, 18 Feb 2013 15:27:12 -0800 (PST) MIME-Version: 1.0 Received: by 10.43.2.67 with HTTP; Mon, 18 Feb 2013 15:26:32 -0800 (PST) In-Reply-To: References: From: Shriram Rajagopalan Date: Mon, 18 Feb 2013 18:26:32 -0500 Message-ID: To: Andrew Eross Cc: "xen-users@lists.xen.org" Subject: Re: [Xen-users] Remus dom0 network buffering X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: rshriram@cs.ubc.ca List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org ah darn. Yes, the 3.5 kernel has sch_plug in it. Unfortunately, the technique to initialize the sch_plug module is bit different with the module thats already mainline. You ll have to patch the qdisc.py python module. I ll submit the patch to xen devel soon. Mean while, can you try the patch below and see if it works ? Secondly, you said you were writing a blog about how you set it up. One of the remus users created a wiki remusha.wikidot.com, which has a whole tutorial on how to setup remus with Debian Squeeze. I have been under fire lately for a host of remus issues. It would be great if you could post your experiences on the wiki too. (http://remusha.wikidot.com/system:join) thanks shriram --- diff -r 6435f1edf24e tools/python/xen/remus/qdisc.py --- a/tools/python/xen/remus/qdisc.py Tue Jul 17 19:23:30 2012 -0400 +++ b/tools/python/xen/remus/qdisc.py Mon Feb 18 18:25:22 2013 -0500 @@ -1,6 +1,9 @@ import socket, struct import netlink +import platform + +kernelversion = platform.platform(terse=True).split("-")[1].split(".") qdisc_kinds = {} @@ -150,9 +153,14 @@ TC_PLUG_RELEASE = 1 class PlugQdisc(Qdisc): - fmt = 'I' def __init__(self, qdict=None): + if int(kernelversion[0]) >= 3 and int(kernelversion[1]) >= 4: + self.fmt = 'iI' + self.limit = 10000 + else: + self.fmt = 'I' + if not qdict: qdict = {'kind': 'plug', 'handle': TC_H_ROOT} @@ -161,7 +169,10 @@ self.action = 0 def pack(self): - return struct.pack(self.fmt, self.action) + if int(kernelversion[0]) >= 3 and int(kernelversion[1]) >= 4: + return struct.pack(self.fmt, self.action, self.limit) + else: + return struct.pack(self.fmt, self.action) def parse(self, args): if not args: _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Mon Feb 18 23:28:37 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 18 Feb 2013 23:28: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 1U7a7g-00028l-TI; Mon, 18 Feb 2013 23:27:48 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U7a7f-00028g-Sq for xen-users@lists.xen.org; Mon, 18 Feb 2013 23:27:48 +0000 Received: from [193.109.254.147:44923] by server-3.bemta-14.messagelabs.com id 02/EB-22141-3F8B2215; Mon, 18 Feb 2013 23:27:47 +0000 X-Env-Sender: rshriram@cs.ubc.ca X-Msg-Ref: server-5.tower-27.messagelabs.com!1361230035!6416967!1 X-Originating-IP: [142.103.6.52] X-SpamReason: No, hits=0.3 required=7.0 tests=RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 18804 invoked from network); 18 Feb 2013 23:27:18 -0000 Received: from smtp.cs.ubc.ca (HELO smtp.cs.ubc.ca) (142.103.6.52) by server-5.tower-27.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 18 Feb 2013 23:27:18 -0000 Received: from mail-ie0-f176.google.com (mail-ie0-f176.google.com [209.85.223.176]) (authenticated bits=0) by smtp.cs.ubc.ca (8.14.3/8.13.6) with ESMTP id r1INRESx002883 (version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=FAIL) for ; Mon, 18 Feb 2013 15:27:14 -0800 Received: by mail-ie0-f176.google.com with SMTP id k13so7748334iea.35 for ; Mon, 18 Feb 2013 15:27:13 -0800 (PST) X-Received: by 10.42.42.69 with SMTP id s5mr6726590ice.2.1361230032808; Mon, 18 Feb 2013 15:27:12 -0800 (PST) MIME-Version: 1.0 Received: by 10.43.2.67 with HTTP; Mon, 18 Feb 2013 15:26:32 -0800 (PST) In-Reply-To: References: From: Shriram Rajagopalan Date: Mon, 18 Feb 2013 18:26:32 -0500 Message-ID: To: Andrew Eross Cc: "xen-users@lists.xen.org" Subject: Re: [Xen-users] Remus dom0 network buffering X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: rshriram@cs.ubc.ca List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org ah darn. Yes, the 3.5 kernel has sch_plug in it. Unfortunately, the technique to initialize the sch_plug module is bit different with the module thats already mainline. You ll have to patch the qdisc.py python module. I ll submit the patch to xen devel soon. Mean while, can you try the patch below and see if it works ? Secondly, you said you were writing a blog about how you set it up. One of the remus users created a wiki remusha.wikidot.com, which has a whole tutorial on how to setup remus with Debian Squeeze. I have been under fire lately for a host of remus issues. It would be great if you could post your experiences on the wiki too. (http://remusha.wikidot.com/system:join) thanks shriram --- diff -r 6435f1edf24e tools/python/xen/remus/qdisc.py --- a/tools/python/xen/remus/qdisc.py Tue Jul 17 19:23:30 2012 -0400 +++ b/tools/python/xen/remus/qdisc.py Mon Feb 18 18:25:22 2013 -0500 @@ -1,6 +1,9 @@ import socket, struct import netlink +import platform + +kernelversion = platform.platform(terse=True).split("-")[1].split(".") qdisc_kinds = {} @@ -150,9 +153,14 @@ TC_PLUG_RELEASE = 1 class PlugQdisc(Qdisc): - fmt = 'I' def __init__(self, qdict=None): + if int(kernelversion[0]) >= 3 and int(kernelversion[1]) >= 4: + self.fmt = 'iI' + self.limit = 10000 + else: + self.fmt = 'I' + if not qdict: qdict = {'kind': 'plug', 'handle': TC_H_ROOT} @@ -161,7 +169,10 @@ self.action = 0 def pack(self): - return struct.pack(self.fmt, self.action) + if int(kernelversion[0]) >= 3 and int(kernelversion[1]) >= 4: + return struct.pack(self.fmt, self.action, self.limit) + else: + return struct.pack(self.fmt, self.action) def parse(self, args): if not args: _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Mon Feb 18 23:31:22 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 18 Feb 2013 23:31: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 1U7aAY-0002KV-Ov; Mon, 18 Feb 2013 23: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 1U7aAX-0002KN-GI for xen-users@lists.xen.org; Mon, 18 Feb 2013 23:30:45 +0000 Received: from [85.158.143.35:54257] by server-1.bemta-4.messagelabs.com id 87/9E-08839-4A9B2215; Mon, 18 Feb 2013 23:30:44 +0000 X-Env-Sender: cdelorme@gmail.com X-Msg-Ref: server-5.tower-21.messagelabs.com!1361230242!3960073!1 X-Originating-IP: [209.85.128.182] 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.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 6193 invoked from network); 18 Feb 2013 23:30:43 -0000 Received: from mail-ve0-f182.google.com (HELO mail-ve0-f182.google.com) (209.85.128.182) by server-5.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 18 Feb 2013 23:30:43 -0000 Received: by mail-ve0-f182.google.com with SMTP id ox1so5351650veb.13 for ; Mon, 18 Feb 2013 15:30:42 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=PcXH7RolpxXjxjydrLfUxn6HN75l1OIe1XEGMtM0yxg=; b=UsjnQ0YfuJqQs19UD/WUsNSDLSkAKY2u/J1jE0Lugza57heURXzyxv5SuavCHS5yCy R0wGv/ssPIw/Pubny4TLNohVjfkbcmBrexnqmhso7WR7E8mXzsD7ZaRTqn4J1Jsngiby fbIRSN5TIEJx4eawBRMGbRPsGHhAJI++12BJf6JDrMNp9IxPsxXw43rKYXB40UJnlreI OGUC81DZyG1gbUeR+ldHNSP6kUcH9p+pSz+VLQo6dZ+GbOEr8EMkHQEr2z5uF4q0gqr8 W79puzCevBs6f1M0QwVlIzmEbaGZH4PIeK+t6x29KvDJiaeFUUyYZb6dEaN4XVugyYK7 gkfQ== MIME-Version: 1.0 X-Received: by 10.58.19.232 with SMTP id i8mr18093496vee.53.1361230241817; Mon, 18 Feb 2013 15:30:41 -0800 (PST) Received: by 10.58.32.199 with HTTP; Mon, 18 Feb 2013 15:30:41 -0800 (PST) In-Reply-To: <6035A0D088A63A46850C3988ED045A4B35680334@BITCOM1.int.sbss.com.au> References: <6035A0D088A63A46850C3988ED045A4B35680334@BITCOM1.int.sbss.com.au> Date: Mon, 18 Feb 2013 18:30:41 -0500 Message-ID: From: Casey DeLorme To: James Harper Cc: "xen-users@lists.xen.org" Subject: Re: [Xen-users] xendomains stop and gplpv network questions X-BeenThere: xen-users@lists.xen.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="===============2789234222134738839==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============2789234222134738839== Content-Type: multipart/alternative; boundary=047d7b86f2ec05662404d6081db2 --047d7b86f2ec05662404d6081db2 Content-Type: text/plain; charset=UTF-8 On Mon, Feb 18, 2013 at 6:05 PM, James Harper wrote: > > 1. Has anyone else been having trouble with the xendomains script? > > > > I am running 4.2 stable on Debian Wheezy, and the xendomains script does > > not shut down my running domains (specifically two linux HVM's one with > > PVHVM). > > > > When run manually via `service xendomains stop` or > `/etc/init.d/xendomains > > stop` it returns a success message, but my machines continue to run as > > though nothing happened. > > That is a bit strange. Check the /etc/default/xendomains and see what the > behaviours are set to... it shouldn't leave the domains running but maybe > is set to save but save is failing? > > I see, totally forgot about that file. All set to defaults, and `XENDOMAINS_SAVE` is set to `/var/lib/xen/save`, should I set it to an empty string? > > When I shut down my computer without running `xl destroy` on the running > > domains it locks up, my guess is because the domains are still running. > > > > When you say 'locks up' do you mean dom0 gets part way through the > shutdown tasks then hangs waiting for xen services to shut down? > > I mean if I run `shutdown -r "now"` with running domains it goes through all the shutdown messages and then simply stops at the last message, and sits there. Since after the shutdown commands are run I can't interact with the machine I can't exactly do much about it, but if I shut down the machines first manually then run the shutdown command it reboots without a problem. > > > > 2. Is anyone else having problems restarting network adapters on Windows > > HVM's with GPLPV drivers? > > > > Without them it works fine, but with GPLPV installed if I disable and > then > > attempt to re-enable a network adapter the device disappears from the > > machine. > > > > The only solution so far has been to reboot the HVM. > > > > What Windows OS and what version of GPLPV? Sounds like a bug but I've > disabled and enabled adapters lots of times without problems... > > I am using GPLPV 11.0.357. I had the same problems on Windows 7 but am currently using Windows 8. At first I thought it was a misconfigured vif, but after trying every combination of options without any changes I think it must be something else. I have attached my windows CFG to this email. > James > --047d7b86f2ec05662404d6081db2 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
On Mon, Feb 18, 2013 at 6:05 PM, James Harper <james.harper@bendigoit.com.au> wrote:
> 1. Has a= nyone else been having trouble with the xendomains script?
>
> I am running 4.2 stable on Debian Wheezy, and the xendomains script do= es
> not shut down my running domains (specifically two linux HVM's one= with
> PVHVM).
>
> When run manually via `service xendomains stop` or `/etc/init.d/xendom= ains
> stop` it returns a success message, but my machines continue to run as=
> though nothing happened.

That is a bit strange. Check the /etc/default/xendomains and see what= the behaviours are set to... it shouldn't leave the domains running bu= t maybe is set to save but save is failing?

I see, totally forgot a= bout that file. =C2=A0All set to defaults, and `XENDOMAINS_SAVE` is set to = `/var/lib/xen/save`, should I set it to an empty string?
=C2=A0
> When I shut down my computer without running `xl destroy` on the runni= ng
> domains it locks up, my guess is because the domains are still running= .
>

When you say 'locks up' do you mean dom0 gets part way throug= h the shutdown tasks then hangs waiting for xen services to shut down?

I mean if I run `shutdo= wn -r "now"` with running domains it goes through all the shutdow= n messages and then simply stops at the last message, and sits there. =C2= =A0Since after the shutdown commands are run I can't interact with the = machine I can't exactly do much about it, but if I shut down the machin= es first manually then run the shutdown command it reboots without a proble= m.
=C2=A0
>
> 2. Is anyone else having problems restarting network adapters on Windo= ws
> HVM's with GPLPV drivers?
>
> Without them it works fine, but with GPLPV installed if I disable and = then
> attempt to re-enable a network adapter the device disappears from the<= br> > machine.
>
> The only solution so far has been to reboot the HVM.
>

What Windows OS and what version of GPLPV? Sounds like a bug but I= 9;ve disabled and enabled adapters lots of times without problems...

I am using GPLPV 11.0.357.

I ha= d the same problems on Windows 7 but am currently using Windows 8.

At first I thought it was a misconfigured vif, but aft= er trying every combination of options without any changes I think it must = be something else. =C2=A0I have attached my windows CFG to this email.
=C2=A0
James

--047d7b86f2ec05662404d6081db2-- --===============2789234222134738839== 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 --===============2789234222134738839==-- From xen-users-bounces@lists.xen.org Mon Feb 18 23:31:22 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 18 Feb 2013 23:31: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 1U7aAY-0002KV-Ov; Mon, 18 Feb 2013 23: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 1U7aAX-0002KN-GI for xen-users@lists.xen.org; Mon, 18 Feb 2013 23:30:45 +0000 Received: from [85.158.143.35:54257] by server-1.bemta-4.messagelabs.com id 87/9E-08839-4A9B2215; Mon, 18 Feb 2013 23:30:44 +0000 X-Env-Sender: cdelorme@gmail.com X-Msg-Ref: server-5.tower-21.messagelabs.com!1361230242!3960073!1 X-Originating-IP: [209.85.128.182] 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.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 6193 invoked from network); 18 Feb 2013 23:30:43 -0000 Received: from mail-ve0-f182.google.com (HELO mail-ve0-f182.google.com) (209.85.128.182) by server-5.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 18 Feb 2013 23:30:43 -0000 Received: by mail-ve0-f182.google.com with SMTP id ox1so5351650veb.13 for ; Mon, 18 Feb 2013 15:30:42 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=PcXH7RolpxXjxjydrLfUxn6HN75l1OIe1XEGMtM0yxg=; b=UsjnQ0YfuJqQs19UD/WUsNSDLSkAKY2u/J1jE0Lugza57heURXzyxv5SuavCHS5yCy R0wGv/ssPIw/Pubny4TLNohVjfkbcmBrexnqmhso7WR7E8mXzsD7ZaRTqn4J1Jsngiby fbIRSN5TIEJx4eawBRMGbRPsGHhAJI++12BJf6JDrMNp9IxPsxXw43rKYXB40UJnlreI OGUC81DZyG1gbUeR+ldHNSP6kUcH9p+pSz+VLQo6dZ+GbOEr8EMkHQEr2z5uF4q0gqr8 W79puzCevBs6f1M0QwVlIzmEbaGZH4PIeK+t6x29KvDJiaeFUUyYZb6dEaN4XVugyYK7 gkfQ== MIME-Version: 1.0 X-Received: by 10.58.19.232 with SMTP id i8mr18093496vee.53.1361230241817; Mon, 18 Feb 2013 15:30:41 -0800 (PST) Received: by 10.58.32.199 with HTTP; Mon, 18 Feb 2013 15:30:41 -0800 (PST) In-Reply-To: <6035A0D088A63A46850C3988ED045A4B35680334@BITCOM1.int.sbss.com.au> References: <6035A0D088A63A46850C3988ED045A4B35680334@BITCOM1.int.sbss.com.au> Date: Mon, 18 Feb 2013 18:30:41 -0500 Message-ID: From: Casey DeLorme To: James Harper Cc: "xen-users@lists.xen.org" Subject: Re: [Xen-users] xendomains stop and gplpv network questions X-BeenThere: xen-users@lists.xen.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="===============2789234222134738839==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============2789234222134738839== Content-Type: multipart/alternative; boundary=047d7b86f2ec05662404d6081db2 --047d7b86f2ec05662404d6081db2 Content-Type: text/plain; charset=UTF-8 On Mon, Feb 18, 2013 at 6:05 PM, James Harper wrote: > > 1. Has anyone else been having trouble with the xendomains script? > > > > I am running 4.2 stable on Debian Wheezy, and the xendomains script does > > not shut down my running domains (specifically two linux HVM's one with > > PVHVM). > > > > When run manually via `service xendomains stop` or > `/etc/init.d/xendomains > > stop` it returns a success message, but my machines continue to run as > > though nothing happened. > > That is a bit strange. Check the /etc/default/xendomains and see what the > behaviours are set to... it shouldn't leave the domains running but maybe > is set to save but save is failing? > > I see, totally forgot about that file. All set to defaults, and `XENDOMAINS_SAVE` is set to `/var/lib/xen/save`, should I set it to an empty string? > > When I shut down my computer without running `xl destroy` on the running > > domains it locks up, my guess is because the domains are still running. > > > > When you say 'locks up' do you mean dom0 gets part way through the > shutdown tasks then hangs waiting for xen services to shut down? > > I mean if I run `shutdown -r "now"` with running domains it goes through all the shutdown messages and then simply stops at the last message, and sits there. Since after the shutdown commands are run I can't interact with the machine I can't exactly do much about it, but if I shut down the machines first manually then run the shutdown command it reboots without a problem. > > > > 2. Is anyone else having problems restarting network adapters on Windows > > HVM's with GPLPV drivers? > > > > Without them it works fine, but with GPLPV installed if I disable and > then > > attempt to re-enable a network adapter the device disappears from the > > machine. > > > > The only solution so far has been to reboot the HVM. > > > > What Windows OS and what version of GPLPV? Sounds like a bug but I've > disabled and enabled adapters lots of times without problems... > > I am using GPLPV 11.0.357. I had the same problems on Windows 7 but am currently using Windows 8. At first I thought it was a misconfigured vif, but after trying every combination of options without any changes I think it must be something else. I have attached my windows CFG to this email. > James > --047d7b86f2ec05662404d6081db2 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
On Mon, Feb 18, 2013 at 6:05 PM, James Harper <james.harper@bendigoit.com.au> wrote:
> 1. Has a= nyone else been having trouble with the xendomains script?
>
> I am running 4.2 stable on Debian Wheezy, and the xendomains script do= es
> not shut down my running domains (specifically two linux HVM's one= with
> PVHVM).
>
> When run manually via `service xendomains stop` or `/etc/init.d/xendom= ains
> stop` it returns a success message, but my machines continue to run as=
> though nothing happened.

That is a bit strange. Check the /etc/default/xendomains and see what= the behaviours are set to... it shouldn't leave the domains running bu= t maybe is set to save but save is failing?

I see, totally forgot a= bout that file. =C2=A0All set to defaults, and `XENDOMAINS_SAVE` is set to = `/var/lib/xen/save`, should I set it to an empty string?
=C2=A0
> When I shut down my computer without running `xl destroy` on the runni= ng
> domains it locks up, my guess is because the domains are still running= .
>

When you say 'locks up' do you mean dom0 gets part way throug= h the shutdown tasks then hangs waiting for xen services to shut down?

I mean if I run `shutdo= wn -r "now"` with running domains it goes through all the shutdow= n messages and then simply stops at the last message, and sits there. =C2= =A0Since after the shutdown commands are run I can't interact with the = machine I can't exactly do much about it, but if I shut down the machin= es first manually then run the shutdown command it reboots without a proble= m.
=C2=A0
>
> 2. Is anyone else having problems restarting network adapters on Windo= ws
> HVM's with GPLPV drivers?
>
> Without them it works fine, but with GPLPV installed if I disable and = then
> attempt to re-enable a network adapter the device disappears from the<= br> > machine.
>
> The only solution so far has been to reboot the HVM.
>

What Windows OS and what version of GPLPV? Sounds like a bug but I= 9;ve disabled and enabled adapters lots of times without problems...

I am using GPLPV 11.0.357.

I ha= d the same problems on Windows 7 but am currently using Windows 8.

At first I thought it was a misconfigured vif, but aft= er trying every combination of options without any changes I think it must = be something else. =C2=A0I have attached my windows CFG to this email.
=C2=A0
James

--047d7b86f2ec05662404d6081db2-- --===============2789234222134738839== 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 --===============2789234222134738839==-- From xen-users-bounces@lists.xen.org Mon Feb 18 23:47:54 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 18 Feb 2013 23:47: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 1U7aQ3-0002sf-KG; Mon, 18 Feb 2013 23:46:47 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U7aQ2-0002sa-2u for xen-users@lists.xen.org; Mon, 18 Feb 2013 23:46:46 +0000 Received: from [85.158.138.51:46243] by server-5.bemta-3.messagelabs.com id DA/8C-04457-56DB2215; Mon, 18 Feb 2013 23:46:45 +0000 X-Env-Sender: james.harper@bendigoit.com.au X-Msg-Ref: server-2.tower-174.messagelabs.com!1361231201!28112176!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.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 27218 invoked from network); 18 Feb 2013 23:46:44 -0000 Received: from mail.bendigoit.com.au (HELO smtp2.bendigoit.com.au) (203.16.207.99) by server-2.tower-174.messagelabs.com with AES256-SHA encrypted SMTP; 18 Feb 2013 23:46:44 -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 1U7aPu-0002da-7v; Tue, 19 Feb 2013 10:46:38 +1100 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.0438.000; Tue, 19 Feb 2013 10:46:38 +1100 From: James Harper To: Casey DeLorme Thread-Topic: [Xen-users] xendomains stop and gplpv network questions Thread-Index: AQHODie9fXP2cXpPZEieAWQ5cLTG75iAO86g//9PaYCAALzGEA== Date: Mon, 18 Feb 2013 23:46:37 +0000 Message-ID: <6035A0D088A63A46850C3988ED045A4B35680482@BITCOM1.int.sbss.com.au> References: <6035A0D088A63A46850C3988ED045A4B35680334@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:2088:5a93:4fa0:263e] x-tm-as-product-ver: SMEX-10.2.0.2087-7.000.1014-19646.002 x-tm-as-result: No--30.863100-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] xendomains stop and gplpv network questions X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org > What Windows OS and what version of GPLPV? Sounds like a bug but > I've disabled and enabled adapters lots of times without problems... > > > > I am using GPLPV 11.0.357. > > I had the same problems on Windows 7 but am currently using Windows 8. > > At first I thought it was a misconfigured vif, but after trying every > combination of options without any changes I think it must be something > else. I have attached my windows CFG to this email. > > I don't see an attachment. James _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Mon Feb 18 23:47:54 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 18 Feb 2013 23:47: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 1U7aQ3-0002sf-KG; Mon, 18 Feb 2013 23:46:47 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U7aQ2-0002sa-2u for xen-users@lists.xen.org; Mon, 18 Feb 2013 23:46:46 +0000 Received: from [85.158.138.51:46243] by server-5.bemta-3.messagelabs.com id DA/8C-04457-56DB2215; Mon, 18 Feb 2013 23:46:45 +0000 X-Env-Sender: james.harper@bendigoit.com.au X-Msg-Ref: server-2.tower-174.messagelabs.com!1361231201!28112176!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.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 27218 invoked from network); 18 Feb 2013 23:46:44 -0000 Received: from mail.bendigoit.com.au (HELO smtp2.bendigoit.com.au) (203.16.207.99) by server-2.tower-174.messagelabs.com with AES256-SHA encrypted SMTP; 18 Feb 2013 23:46:44 -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 1U7aPu-0002da-7v; Tue, 19 Feb 2013 10:46:38 +1100 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.0438.000; Tue, 19 Feb 2013 10:46:38 +1100 From: James Harper To: Casey DeLorme Thread-Topic: [Xen-users] xendomains stop and gplpv network questions Thread-Index: AQHODie9fXP2cXpPZEieAWQ5cLTG75iAO86g//9PaYCAALzGEA== Date: Mon, 18 Feb 2013 23:46:37 +0000 Message-ID: <6035A0D088A63A46850C3988ED045A4B35680482@BITCOM1.int.sbss.com.au> References: <6035A0D088A63A46850C3988ED045A4B35680334@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:2088:5a93:4fa0:263e] x-tm-as-product-ver: SMEX-10.2.0.2087-7.000.1014-19646.002 x-tm-as-result: No--30.863100-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] xendomains stop and gplpv network questions X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org > What Windows OS and what version of GPLPV? Sounds like a bug but > I've disabled and enabled adapters lots of times without problems... > > > > I am using GPLPV 11.0.357. > > I had the same problems on Windows 7 but am currently using Windows 8. > > At first I thought it was a misconfigured vif, but after trying every > combination of options without any changes I think it must be something > else. I have attached my windows CFG to this email. > > I don't see an attachment. James _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Tue Feb 19 00:01:27 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 19 Feb 2013 00:01: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 1U7adO-0003W4-AF; Tue, 19 Feb 2013 00:00:34 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U7adM-0003Vz-8t for xen-users@lists.xen.org; Tue, 19 Feb 2013 00:00:32 +0000 Received: from [85.158.143.99:48337] by server-2.bemta-4.messagelabs.com id 7B/75-12656-F90C2215; Tue, 19 Feb 2013 00:00:31 +0000 X-Env-Sender: cdelorme@gmail.com X-Msg-Ref: server-6.tower-216.messagelabs.com!1361232028!21054578!1 X-Originating-IP: [209.85.220.180] 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.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 16744 invoked from network); 19 Feb 2013 00:00:30 -0000 Received: from mail-vc0-f180.google.com (HELO mail-vc0-f180.google.com) (209.85.220.180) by server-6.tower-216.messagelabs.com with RC4-SHA encrypted SMTP; 19 Feb 2013 00:00:30 -0000 Received: by mail-vc0-f180.google.com with SMTP id fo13so4009911vcb.11 for ; Mon, 18 Feb 2013 16:00:28 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=G6EZj8blDUl0w5TpmTblih5bE4ImrnYyXPxaTsEEl6U=; b=RWnu873k38Dmal0OidSZTkzuriKkO404rHzX9oJyLL9YbemAdNe1aXp5wX9/g5PbnO hGSMVHzLqPtCVbhaKMOhJFLE1Tu1g+iHOTtleTQMoJHDnhUWaNpmckRZe6Q1KuG6QI3c x+yPWb6Uo9wMfAdcXcRmsoOtMTkoEwTcoRmcx52iWcelrxenMVTk12R5OM8xiUkbb1P4 H9LbKCh2V4hoopQ3WpFMZxPt+jimp/26XqcrQV2FGLiUN5qwGviCzZGjs6xejpj5cSsv cxvSJ129qghuqVeyLsvVLcLO8+omuegnYOJ0n9kqAM1yr42VUB2BK1/X+I4BObza5C/k FaVA== MIME-Version: 1.0 X-Received: by 10.58.186.241 with SMTP id fn17mr18388734vec.8.1361232028478; Mon, 18 Feb 2013 16:00:28 -0800 (PST) Received: by 10.58.32.199 with HTTP; Mon, 18 Feb 2013 16:00:28 -0800 (PST) In-Reply-To: <6035A0D088A63A46850C3988ED045A4B35680482@BITCOM1.int.sbss.com.au> References: <6035A0D088A63A46850C3988ED045A4B35680334@BITCOM1.int.sbss.com.au> <6035A0D088A63A46850C3988ED045A4B35680482@BITCOM1.int.sbss.com.au> Date: Mon, 18 Feb 2013 19:00:28 -0500 Message-ID: From: Casey DeLorme To: James Harper Content-Type: multipart/mixed; boundary=047d7b6dcf4683aebe04d6088723 Cc: "xen-users@lists.xen.org" Subject: Re: [Xen-users] xendomains stop and gplpv network questions X-BeenThere: xen-users@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 --047d7b6dcf4683aebe04d6088723 Content-Type: multipart/alternative; boundary=047d7b6dcf4683aebb04d6088721 --047d7b6dcf4683aebb04d6088721 Content-Type: text/plain; charset=UTF-8 Sorry, guess it didn't take. Just in case: name='windows' builder='hvm' vcpus=4 memory=8192 disk=[ '/dev/mapper/xen-windows,,hda,w', '/dev/mapper/backups-music,,hdb,w' ] vif=[ 'mac=00:16:3e:14:b1:1d,bridge=xenbr1' ] 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" usb=1 usbdevice="tablet" localtime=1 viridian=1 xen_platform_pci=1 On Mon, Feb 18, 2013 at 6:46 PM, James Harper wrote: > > What Windows OS and what version of GPLPV? Sounds like a bug but > > I've disabled and enabled adapters lots of times without problems... > > > > > > > > I am using GPLPV 11.0.357. > > > > I had the same problems on Windows 7 but am currently using Windows 8. > > > > At first I thought it was a misconfigured vif, but after trying every > > combination of options without any changes I think it must be something > > else. I have attached my windows CFG to this email. > > > > > > I don't see an attachment. > > James > --047d7b6dcf4683aebb04d6088721 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Sorry, guess it didn't take. =C2=A0Just in case:
<= br>
name=3D'windows'
builder=3D'h= vm'
vcpus=3D4
memory=3D8192
disk=3D[
'/dev/mapper/x= en-windows,,hda,w',
'/dev/mapper/ba= ckups-music,,hdb,w'
]
vif=3D[
'mac=3D00:16:3e:14:b1:1d,bridge= =3Dxenbr1'
]
pci=3D[
'00:1d.0',
'01:00.0',
'01:00.1',
'0b:00.0',<= /div>
'0c:00.0&#= 39;
]
boot=3D'c'
pae=3D1
nx= =3D1
videoram=3D16
stdvga=3D1
#sdl=3D1
vnc=3D= 1
vnclisten=3D"0.0.0.0:10&= quot;
usb=3D1
usbdevice=3D"tablet"
= localtime=3D1
viridian=3D1
xen_platform_pci=3D1

=



On Mon, Feb 18, 2013 at 6:46 PM, James Harper <j= ames.harper@bendigoit.com.au> wrote:
> =C2=A0 =C2=A0 =C2=A0 = What Windows OS and what version of GPLPV? Sounds like a bug but
> I've disabled and enabled adapters lots of times without problems.= ..
>
>
>
> I am using GPLPV 11.0.357.
>
> I had the same problems on Windows 7 but am currently using Windows 8.=
>
> At first I thought it was a misconfigured vif, but after trying every<= br> > combination of options without any changes I think it must be somethin= g
> else. =C2=A0I have attached my windows CFG to this email.
>
>

I don't see an attachment.

James

--047d7b6dcf4683aebb04d6088721-- --047d7b6dcf4683aebe04d6088723 Content-Type: application/octet-stream; name="windows.cfg" Content-Disposition: attachment; filename="windows.cfg" Content-Transfer-Encoding: base64 X-Attachment-Id: f_hdcae1ju0 bmFtZT0nd2luZG93cycKYnVpbGRlcj0naHZtJwp2Y3B1cz00Cm1lbW9yeT04MTkyCmRpc2s9WwoJ Jy9kZXYvbWFwcGVyL3hlbi13aW5kb3dzLCxoZGEsdycsCgknL2Rldi9tYXBwZXIvYmFja3Vwcy1t dXNpYywsaGRiLHcnCl0KdmlmPVsKCSdtYWM9MDA6MTY6M2U6MTQ6YjE6MWQsYnJpZGdlPXhlbmJy MScKXQpwY2k9WwoJJzAwOjFkLjAnLAoJJzAxOjAwLjAnLAoJJzAxOjAwLjEnLAoJJzBiOjAwLjAn LAoJJzBjOjAwLjAnCl0KYm9vdD0nYycKcGFlPTEKbng9MQp2aWRlb3JhbT0xNgpzdGR2Z2E9MQoj c2RsPTEKdm5jPTEKdm5jbGlzdGVuPSIwLjAuMC4wOjEwIgp1c2I9MQp1c2JkZXZpY2U9InRhYmxl dCIKbG9jYWx0aW1lPTEKdmlyaWRpYW49MQp4ZW5fcGxhdGZvcm1fcGNpPTEK --047d7b6dcf4683aebe04d6088723 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 --047d7b6dcf4683aebe04d6088723-- From xen-users-bounces@lists.xen.org Tue Feb 19 00:01:27 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 19 Feb 2013 00:01: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 1U7adO-0003W4-AF; Tue, 19 Feb 2013 00:00:34 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U7adM-0003Vz-8t for xen-users@lists.xen.org; Tue, 19 Feb 2013 00:00:32 +0000 Received: from [85.158.143.99:48337] by server-2.bemta-4.messagelabs.com id 7B/75-12656-F90C2215; Tue, 19 Feb 2013 00:00:31 +0000 X-Env-Sender: cdelorme@gmail.com X-Msg-Ref: server-6.tower-216.messagelabs.com!1361232028!21054578!1 X-Originating-IP: [209.85.220.180] 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.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 16744 invoked from network); 19 Feb 2013 00:00:30 -0000 Received: from mail-vc0-f180.google.com (HELO mail-vc0-f180.google.com) (209.85.220.180) by server-6.tower-216.messagelabs.com with RC4-SHA encrypted SMTP; 19 Feb 2013 00:00:30 -0000 Received: by mail-vc0-f180.google.com with SMTP id fo13so4009911vcb.11 for ; Mon, 18 Feb 2013 16:00:28 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=G6EZj8blDUl0w5TpmTblih5bE4ImrnYyXPxaTsEEl6U=; b=RWnu873k38Dmal0OidSZTkzuriKkO404rHzX9oJyLL9YbemAdNe1aXp5wX9/g5PbnO hGSMVHzLqPtCVbhaKMOhJFLE1Tu1g+iHOTtleTQMoJHDnhUWaNpmckRZe6Q1KuG6QI3c x+yPWb6Uo9wMfAdcXcRmsoOtMTkoEwTcoRmcx52iWcelrxenMVTk12R5OM8xiUkbb1P4 H9LbKCh2V4hoopQ3WpFMZxPt+jimp/26XqcrQV2FGLiUN5qwGviCzZGjs6xejpj5cSsv cxvSJ129qghuqVeyLsvVLcLO8+omuegnYOJ0n9kqAM1yr42VUB2BK1/X+I4BObza5C/k FaVA== MIME-Version: 1.0 X-Received: by 10.58.186.241 with SMTP id fn17mr18388734vec.8.1361232028478; Mon, 18 Feb 2013 16:00:28 -0800 (PST) Received: by 10.58.32.199 with HTTP; Mon, 18 Feb 2013 16:00:28 -0800 (PST) In-Reply-To: <6035A0D088A63A46850C3988ED045A4B35680482@BITCOM1.int.sbss.com.au> References: <6035A0D088A63A46850C3988ED045A4B35680334@BITCOM1.int.sbss.com.au> <6035A0D088A63A46850C3988ED045A4B35680482@BITCOM1.int.sbss.com.au> Date: Mon, 18 Feb 2013 19:00:28 -0500 Message-ID: From: Casey DeLorme To: James Harper Content-Type: multipart/mixed; boundary=047d7b6dcf4683aebe04d6088723 Cc: "xen-users@lists.xen.org" Subject: Re: [Xen-users] xendomains stop and gplpv network questions X-BeenThere: xen-users@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 --047d7b6dcf4683aebe04d6088723 Content-Type: multipart/alternative; boundary=047d7b6dcf4683aebb04d6088721 --047d7b6dcf4683aebb04d6088721 Content-Type: text/plain; charset=UTF-8 Sorry, guess it didn't take. Just in case: name='windows' builder='hvm' vcpus=4 memory=8192 disk=[ '/dev/mapper/xen-windows,,hda,w', '/dev/mapper/backups-music,,hdb,w' ] vif=[ 'mac=00:16:3e:14:b1:1d,bridge=xenbr1' ] 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" usb=1 usbdevice="tablet" localtime=1 viridian=1 xen_platform_pci=1 On Mon, Feb 18, 2013 at 6:46 PM, James Harper wrote: > > What Windows OS and what version of GPLPV? Sounds like a bug but > > I've disabled and enabled adapters lots of times without problems... > > > > > > > > I am using GPLPV 11.0.357. > > > > I had the same problems on Windows 7 but am currently using Windows 8. > > > > At first I thought it was a misconfigured vif, but after trying every > > combination of options without any changes I think it must be something > > else. I have attached my windows CFG to this email. > > > > > > I don't see an attachment. > > James > --047d7b6dcf4683aebb04d6088721 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Sorry, guess it didn't take. =C2=A0Just in case:
<= br>
name=3D'windows'
builder=3D'h= vm'
vcpus=3D4
memory=3D8192
disk=3D[
'/dev/mapper/x= en-windows,,hda,w',
'/dev/mapper/ba= ckups-music,,hdb,w'
]
vif=3D[
'mac=3D00:16:3e:14:b1:1d,bridge= =3Dxenbr1'
]
pci=3D[
'00:1d.0',
'01:00.0',
'01:00.1',
'0b:00.0',<= /div>
'0c:00.0&#= 39;
]
boot=3D'c'
pae=3D1
nx= =3D1
videoram=3D16
stdvga=3D1
#sdl=3D1
vnc=3D= 1
vnclisten=3D"0.0.0.0:10&= quot;
usb=3D1
usbdevice=3D"tablet"
= localtime=3D1
viridian=3D1
xen_platform_pci=3D1

=



On Mon, Feb 18, 2013 at 6:46 PM, James Harper <j= ames.harper@bendigoit.com.au> wrote:
> =C2=A0 =C2=A0 =C2=A0 = What Windows OS and what version of GPLPV? Sounds like a bug but
> I've disabled and enabled adapters lots of times without problems.= ..
>
>
>
> I am using GPLPV 11.0.357.
>
> I had the same problems on Windows 7 but am currently using Windows 8.=
>
> At first I thought it was a misconfigured vif, but after trying every<= br> > combination of options without any changes I think it must be somethin= g
> else. =C2=A0I have attached my windows CFG to this email.
>
>

I don't see an attachment.

James

--047d7b6dcf4683aebb04d6088721-- --047d7b6dcf4683aebe04d6088723 Content-Type: application/octet-stream; name="windows.cfg" Content-Disposition: attachment; filename="windows.cfg" Content-Transfer-Encoding: base64 X-Attachment-Id: f_hdcae1ju0 bmFtZT0nd2luZG93cycKYnVpbGRlcj0naHZtJwp2Y3B1cz00Cm1lbW9yeT04MTkyCmRpc2s9WwoJ Jy9kZXYvbWFwcGVyL3hlbi13aW5kb3dzLCxoZGEsdycsCgknL2Rldi9tYXBwZXIvYmFja3Vwcy1t dXNpYywsaGRiLHcnCl0KdmlmPVsKCSdtYWM9MDA6MTY6M2U6MTQ6YjE6MWQsYnJpZGdlPXhlbmJy MScKXQpwY2k9WwoJJzAwOjFkLjAnLAoJJzAxOjAwLjAnLAoJJzAxOjAwLjEnLAoJJzBiOjAwLjAn LAoJJzBjOjAwLjAnCl0KYm9vdD0nYycKcGFlPTEKbng9MQp2aWRlb3JhbT0xNgpzdGR2Z2E9MQoj c2RsPTEKdm5jPTEKdm5jbGlzdGVuPSIwLjAuMC4wOjEwIgp1c2I9MQp1c2JkZXZpY2U9InRhYmxl dCIKbG9jYWx0aW1lPTEKdmlyaWRpYW49MQp4ZW5fcGxhdGZvcm1fcGNpPTEK --047d7b6dcf4683aebe04d6088723 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 --047d7b6dcf4683aebe04d6088723-- From xen-users-bounces@lists.xen.org Tue Feb 19 00:24:25 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 19 Feb 2013 00:24: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 1U7azk-0004Pu-Gj; Tue, 19 Feb 2013 00:23:40 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U7azi-0004Pp-QU for xen-users@lists.xen.org; Tue, 19 Feb 2013 00:23:39 +0000 Received: from [85.158.143.35:18615] by server-2.bemta-4.messagelabs.com id 15/3F-12656-A06C2215; Tue, 19 Feb 2013 00:23:38 +0000 X-Env-Sender: murrayie@yahoo.co.uk X-Msg-Ref: server-2.tower-21.messagelabs.com!1361233417!4744587!1 X-Originating-IP: [77.238.189.77] X-SpamReason: No, hits=0.0 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, spamassassin: X-StarScan-Received: X-StarScan-Version: 6.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 10511 invoked from network); 19 Feb 2013 00:23:37 -0000 Received: from nm20.bullet.mail.ird.yahoo.com (HELO nm20.bullet.mail.ird.yahoo.com) (77.238.189.77) by server-2.tower-21.messagelabs.com with SMTP; 19 Feb 2013 00:23:37 -0000 Received: from [77.238.189.50] by nm20.bullet.mail.ird.yahoo.com with NNFMP; 19 Feb 2013 00:23:37 -0000 Received: from [217.146.188.160] by tm3.bullet.mail.ird.yahoo.com with NNFMP; 19 Feb 2013 00:23:37 -0000 Received: from [127.0.0.1] by smtp128.mail.ird.yahoo.com with NNFMP; 19 Feb 2013 00:23:37 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.co.uk; s=s1024; t=1361233417; bh=w6pbZR9R95Ejxp8gD9494+/LZFeoLwSobLmmBIv13a0=; 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:References:In-Reply-To:Content-Type:Content-Transfer-Encoding; b=NbBk9VUXZL7DxrTvhzkW8osZBXOM+3Vy3AAMEZJjixgHLm6zuX50INJpCBnRjNAWRZN9ybLq6b63NhQinpFY0x3EtqN64NK8Dw88LZMIAoH0EXhqZh+MGUsAQVkJnVblt3MEB7PraxiwdkU37mbXeGYSnzudyYFtMkzukVyOS1w= X-Yahoo-Newman-Id: 348851.68306.bm@smtp128.mail.ird.yahoo.com X-Yahoo-Newman-Property: ymail-3 X-YMail-OSG: _6k9BFQVM1mYxUa..3mG9w0tDkIPU2jIezCVaGGyZhVNbt6 cBbWcWWejgxSVuPgR7_t8_.XU1KgvtEgEplMvxXCOdY9J86PDkVryIrdn3kT uiUR06fqbXmaE6ly4aTTx.V8v0TZR7G7t5O6zk_z2.Owr1324rvcvOIBJQjL A5FyAPHfbmjcl0lK6noJx2UYA7QcK7tg4Y95knTImdQC6Bace0jT40lccUmf RSE4d5t_PLThAqKQyCNUHFp5pgV1dm9hZuLjnJbu9c9NoRfQB2Imh_DBPyaj 8Ntw15jsRI.mgDh8M6mj2OvsJE4QE.T5yvoIz.iYR9dOcgWjFx1PpaPWfim2 cyaI5DlKpL6m6mWtiCx1uOBepJlyWO3u9fpGz.OlmuGb2kBSrpWFIocXoUHo a4tSCad002BwWlA3o0y2Se08ChqrCfwTyVGkYV_l5JOZT2dzTKQ-- X-Yahoo-SMTP: P.LfrmaswBDlKN6tCvtOaEZlSVsY Received: from [192.168.1.136] (murrayie@109.157.15.99 with plain) by smtp128.mail.ird.yahoo.com with SMTP; 18 Feb 2013 16:23:37 -0800 PST Message-ID: <5122C609.3060706@yahoo.co.uk> Date: Tue, 19 Feb 2013 00:23:37 +0000 From: Ian User-Agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/20130106 Thunderbird/17.0.2 MIME-Version: 1.0 To: xen-users@lists.xen.org References: In-Reply-To: Subject: Re: [Xen-users] xendomains stop and gplpv network questions X-BeenThere: xen-users@lists.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 18/02/13 22:20, Casey DeLorme wrote: > Hello Xen Users, > > I have a couple of unrelated questions but didn't want to clutter > everyones in-boxes with two emails. > > --- > > 1. Has anyone else been having trouble with the xendomains script? > > I am running 4.2 stable on Debian Wheezy, and the xendomains script > does not shut down my running domains (specifically two linux HVM's > one with PVHVM). > > When run manually via `service xendomains stop` or > `/etc/init.d/xendomains stop` it returns a success message, but my > machines continue to run as though nothing happened. > > When I shut down my computer without running `xl destroy` on the > running domains it locks up, my guess is because the domains are still > running. > > Has anyone else encountered this problem? > > --- Xendomains is always horribly broken for me when using xl. I wrote a patch to fix it. I can't remember if I was getting exactly the same behaviour as you, but it is worth a try. This is using the script from the vanilla Xen sources, so I doubt it will patch against the Debian version. I can email the whole xendomains script off-list if you like, or it is pretty easy to mod by hand. I have one Dom0 based on Ubuntu 12.04 and another against Scientific Linux 6.3 with custom kernel and the same script works on both. Whoever maintains the xendomains script must test it against an environment very alien to me! My patch (untested against xm):- --- xendomains.421 2012-12-17 15:00:34.000000000 +0000 +++ xendomains 2013-01-06 11:14:44.622409914 +0000 @@ -27,11 +27,13 @@ # boots / shuts down. ### END INIT INFO +HEADCOMP="LinuxGuestRecord" CMD=xm $CMD list &> /dev/null if test $? -ne 0 then CMD=xl + HEADCOMP="Xen saved domain" fi $CMD list &> /dev/null @@ -202,10 +204,10 @@ done } -LIST_GREP='((domain\|(domid\|(name\|^{$\|"name":\|"domid":' +LIST_GREP='((domain$\|(domid\|(name\|^{$\|"name":\|"domid":' parseln() { - if [[ "$1" =~ '(domain' ]] || [[ "$1" = "{" ]]; then + if [[ "$1" = '(domain' ]] || [[ "$1" = "{" ]]; then name=;id= elif [[ "$1" =~ '(name' ]]; then name=$(echo $1 | sed -e 's/^.*(name \(.*\))$/\1/') @@ -255,7 +257,7 @@ for dom in $XENDOMAINS_SAVE/*; do if [ -f $dom ] ; then HEADER=`head -c 16 $dom | head -n 1 2> /dev/null` - if [ $HEADER = "LinuxGuestRecord" ]; then + if [ "$HEADER" = "$HEADCOMP" ]; then echo -n " ${dom##*/}" XMR=`$CMD restore $dom 2>&1 1>/dev/null` #$CMD restore $dom _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Tue Feb 19 00:24:25 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 19 Feb 2013 00:24: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 1U7azk-0004Pu-Gj; Tue, 19 Feb 2013 00:23:40 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U7azi-0004Pp-QU for xen-users@lists.xen.org; Tue, 19 Feb 2013 00:23:39 +0000 Received: from [85.158.143.35:18615] by server-2.bemta-4.messagelabs.com id 15/3F-12656-A06C2215; Tue, 19 Feb 2013 00:23:38 +0000 X-Env-Sender: murrayie@yahoo.co.uk X-Msg-Ref: server-2.tower-21.messagelabs.com!1361233417!4744587!1 X-Originating-IP: [77.238.189.77] X-SpamReason: No, hits=0.0 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, spamassassin: X-StarScan-Received: X-StarScan-Version: 6.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 10511 invoked from network); 19 Feb 2013 00:23:37 -0000 Received: from nm20.bullet.mail.ird.yahoo.com (HELO nm20.bullet.mail.ird.yahoo.com) (77.238.189.77) by server-2.tower-21.messagelabs.com with SMTP; 19 Feb 2013 00:23:37 -0000 Received: from [77.238.189.50] by nm20.bullet.mail.ird.yahoo.com with NNFMP; 19 Feb 2013 00:23:37 -0000 Received: from [217.146.188.160] by tm3.bullet.mail.ird.yahoo.com with NNFMP; 19 Feb 2013 00:23:37 -0000 Received: from [127.0.0.1] by smtp128.mail.ird.yahoo.com with NNFMP; 19 Feb 2013 00:23:37 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.co.uk; s=s1024; t=1361233417; bh=w6pbZR9R95Ejxp8gD9494+/LZFeoLwSobLmmBIv13a0=; 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:References:In-Reply-To:Content-Type:Content-Transfer-Encoding; b=NbBk9VUXZL7DxrTvhzkW8osZBXOM+3Vy3AAMEZJjixgHLm6zuX50INJpCBnRjNAWRZN9ybLq6b63NhQinpFY0x3EtqN64NK8Dw88LZMIAoH0EXhqZh+MGUsAQVkJnVblt3MEB7PraxiwdkU37mbXeGYSnzudyYFtMkzukVyOS1w= X-Yahoo-Newman-Id: 348851.68306.bm@smtp128.mail.ird.yahoo.com X-Yahoo-Newman-Property: ymail-3 X-YMail-OSG: _6k9BFQVM1mYxUa..3mG9w0tDkIPU2jIezCVaGGyZhVNbt6 cBbWcWWejgxSVuPgR7_t8_.XU1KgvtEgEplMvxXCOdY9J86PDkVryIrdn3kT uiUR06fqbXmaE6ly4aTTx.V8v0TZR7G7t5O6zk_z2.Owr1324rvcvOIBJQjL A5FyAPHfbmjcl0lK6noJx2UYA7QcK7tg4Y95knTImdQC6Bace0jT40lccUmf RSE4d5t_PLThAqKQyCNUHFp5pgV1dm9hZuLjnJbu9c9NoRfQB2Imh_DBPyaj 8Ntw15jsRI.mgDh8M6mj2OvsJE4QE.T5yvoIz.iYR9dOcgWjFx1PpaPWfim2 cyaI5DlKpL6m6mWtiCx1uOBepJlyWO3u9fpGz.OlmuGb2kBSrpWFIocXoUHo a4tSCad002BwWlA3o0y2Se08ChqrCfwTyVGkYV_l5JOZT2dzTKQ-- X-Yahoo-SMTP: P.LfrmaswBDlKN6tCvtOaEZlSVsY Received: from [192.168.1.136] (murrayie@109.157.15.99 with plain) by smtp128.mail.ird.yahoo.com with SMTP; 18 Feb 2013 16:23:37 -0800 PST Message-ID: <5122C609.3060706@yahoo.co.uk> Date: Tue, 19 Feb 2013 00:23:37 +0000 From: Ian User-Agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/20130106 Thunderbird/17.0.2 MIME-Version: 1.0 To: xen-users@lists.xen.org References: In-Reply-To: Subject: Re: [Xen-users] xendomains stop and gplpv network questions X-BeenThere: xen-users@lists.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 18/02/13 22:20, Casey DeLorme wrote: > Hello Xen Users, > > I have a couple of unrelated questions but didn't want to clutter > everyones in-boxes with two emails. > > --- > > 1. Has anyone else been having trouble with the xendomains script? > > I am running 4.2 stable on Debian Wheezy, and the xendomains script > does not shut down my running domains (specifically two linux HVM's > one with PVHVM). > > When run manually via `service xendomains stop` or > `/etc/init.d/xendomains stop` it returns a success message, but my > machines continue to run as though nothing happened. > > When I shut down my computer without running `xl destroy` on the > running domains it locks up, my guess is because the domains are still > running. > > Has anyone else encountered this problem? > > --- Xendomains is always horribly broken for me when using xl. I wrote a patch to fix it. I can't remember if I was getting exactly the same behaviour as you, but it is worth a try. This is using the script from the vanilla Xen sources, so I doubt it will patch against the Debian version. I can email the whole xendomains script off-list if you like, or it is pretty easy to mod by hand. I have one Dom0 based on Ubuntu 12.04 and another against Scientific Linux 6.3 with custom kernel and the same script works on both. Whoever maintains the xendomains script must test it against an environment very alien to me! My patch (untested against xm):- --- xendomains.421 2012-12-17 15:00:34.000000000 +0000 +++ xendomains 2013-01-06 11:14:44.622409914 +0000 @@ -27,11 +27,13 @@ # boots / shuts down. ### END INIT INFO +HEADCOMP="LinuxGuestRecord" CMD=xm $CMD list &> /dev/null if test $? -ne 0 then CMD=xl + HEADCOMP="Xen saved domain" fi $CMD list &> /dev/null @@ -202,10 +204,10 @@ done } -LIST_GREP='((domain\|(domid\|(name\|^{$\|"name":\|"domid":' +LIST_GREP='((domain$\|(domid\|(name\|^{$\|"name":\|"domid":' parseln() { - if [[ "$1" =~ '(domain' ]] || [[ "$1" = "{" ]]; then + if [[ "$1" = '(domain' ]] || [[ "$1" = "{" ]]; then name=;id= elif [[ "$1" =~ '(name' ]]; then name=$(echo $1 | sed -e 's/^.*(name \(.*\))$/\1/') @@ -255,7 +257,7 @@ for dom in $XENDOMAINS_SAVE/*; do if [ -f $dom ] ; then HEADER=`head -c 16 $dom | head -n 1 2> /dev/null` - if [ $HEADER = "LinuxGuestRecord" ]; then + if [ "$HEADER" = "$HEADCOMP" ]; then echo -n " ${dom##*/}" XMR=`$CMD restore $dom 2>&1 1>/dev/null` #$CMD restore $dom _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Tue Feb 19 07:39:36 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 19 Feb 2013 07:39: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 1U7hmI-0003DK-TA; Tue, 19 Feb 2013 07:38:14 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U7hmG-0003D5-I0; Tue, 19 Feb 2013 07:38:12 +0000 Received: from [193.109.254.147:14896] by server-14.bemta-14.messagelabs.com id 0D/7D-02031-3EB23215; Tue, 19 Feb 2013 07:38:11 +0000 X-Env-Sender: agya.naila@gmail.com X-Msg-Ref: server-5.tower-27.messagelabs.com!1361259484!6446863!1 X-Originating-IP: [209.85.212.175] 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.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 27229 invoked from network); 19 Feb 2013 07:38:04 -0000 Received: from mail-wi0-f175.google.com (HELO mail-wi0-f175.google.com) (209.85.212.175) by server-5.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 19 Feb 2013 07:38:04 -0000 Received: by mail-wi0-f175.google.com with SMTP id l13so4432769wie.2 for ; Mon, 18 Feb 2013 23:38:04 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=CKZOqcNXKrcF7HX5ICq3Q42QROEcqiPmVHlN6MXIlIs=; b=o2qfu92JHwcGWfcQG0TLqNjZ/HcbYm1tHbxKRdygBWbwBtOHIwl5cuyH7RxsmlAnRL HGeCkjdN9JXQSJ42DUM7zv/8mcURMEjr8PUr9WmafiA1EOzXnzMpz4rKBln3gAbHkRtN CKo6ODTkJdDwa/OMImZqB6t/qvP8V1BaxnCxLkdqAqcEOWt6HwhGfc7yavlTBMVdko5J rmezZF37UPVKB/C5gSZmsN55Z07Iu1pB47e1O1f15MfJQ/2C6RSFUbUAQnWon+/GDVbc Xr/SYkXwG9KCfMiJIZzF9qQL5wyznJ/0pMA1dsDTbzYamlXdnNmJoSf/HN9nkd64efvQ XApQ== MIME-Version: 1.0 X-Received: by 10.194.158.165 with SMTP id wv5mr23954132wjb.45.1361259484599; Mon, 18 Feb 2013 23:38:04 -0800 (PST) Received: by 10.216.236.13 with HTTP; Mon, 18 Feb 2013 23:38:04 -0800 (PST) In-Reply-To: References: Date: Tue, 19 Feb 2013 08:38:04 +0100 Message-ID: From: agya naila To: rshriram@cs.ubc.ca Cc: "xen-users@lists.xen.org" , "xen-devel@lists.xen.org" Subject: Re: [Xen-users] [Xen-devel] Remus disk replication failed X-BeenThere: xen-users@lists.xen.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="===============8203710917008002532==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============8203710917008002532== Content-Type: multipart/alternative; boundary=089e0122ef8806d75f04d60eecc2 --089e0122ef8806d75f04d60eecc2 Content-Type: text/plain; charset=ISO-8859-1 Okay, I solve it. I removed drbd8-utils and re-install drbd from sources. DRBD connected with D protocol. I could go further with disk replication, hopefully there is no mistaken step again :) Regards, Agya On Mon, Feb 18, 2013 at 11:13 PM, agya naila wrote: > I forgot to told that its work with protocol C > > $ sudo drbd-overview > 1:drbd-vm SyncTarget Secondary/Secondary Inconsistent/UpToDate C r----- > [=>..................] sync'ed: 12.0% (9016/10236)M > > $ sudo drbd-overview > 1:drbd-vm Connected Secondary/Secondary UpToDate/UpToDate C r----- > > > On Mon, Feb 18, 2013 at 11:00 PM, agya naila wrote: > >> On Mon, Feb 18, 2013 at 10:33 PM, Shriram Rajagopalan > > wrote: >> >>> Hi, >>> I suggest you read up on the DRBD setup documentation from the >>> drbd.org website. >>> The setup procedure is same. You can later flip to the remus >>> replication protocol by simply >>> changing the protocol type (C to D). >>> >>> I am comparing my configuration with drbd website, however I got this >> error : >> >> $ sudo drbdadm up drbd-vm >> *'D' is no valid protocol.* >> *Command 'drbdsetup 1 net ipv4:10.10.10.1:7789 ipv4:10.10.10.3:7789 D >> --set-defaults --create-device --rr-conflict=disconnect >> --after-sb-2pri=disconnect --after-sb-1pri=discard-secondary >> --after-sb-0pri=discard-younger-primary --allow-two-primaries --ko-count=4 >> --max-epoch-size=4096 --unplug-watermark=4096 --max-buffers=8192 >> --ping-timeout=20 --ping-int=3 --timeout=30' terminated with exit code 20 >> * >> *drbdadm connect drbd-vm: exited with code 20* >> * >> * >> $ sudo drbd-overview >> 1:drbd-vm StandAlone Secondary/Unknown UpToDate/DUnknown r----s >> >> Thank you, >> >> Agya >> >> >> >>> thanks >>> shriram >>> >>> On Mon, Feb 18, 2013 at 4:11 PM, agya naila >>> wrote: >>> > >>> > On Mon, Feb 18, 2013 at 9:08 PM, Shriram Rajagopalan < >>> rshriram@cs.ubc.ca> >>> > wrote: >>> >> >>> >> hi >>> > >>> > >>> > Thank you shriram. >>> > >>> >> >>> >> sorry for the delayed response. IIRC the blktap2 driver required for >>> >> tapdisk replication doesnt exist in the mainstream dom0 kernels, IIRC. >>> >> I havent used it in a long time myself. I suggest trying disk >>> >> replication with DRBD. >>> >> >>> > >>> > I am also found some information here >>> > http://osdir.com/ml/xen-users/2011-07/msg00653.html about blktap2 >>> problem on >>> > amd64 architecture. I have tried to install and configure the DRBD but >>> its >>> > didn't connect each other. >>> > I used drbd-8.3.11-remus and installed as follow >>> > >>> > cd /usr/src/ >>> > wget >>> > >>> http://remusha.wikidot.com/local--files/configuring-and-installing-remus/drbd-8.3.11-remus.tar.gz >>> > tar xzf drbd-8.3.9-remus.tar.gz >>> > chown -R root:root drbd-8.3-remus >>> > cd /usr/src/drbd-8.3-remus >>> > chmod 777 autogen.sh >>> > ./autogen.sh >>> > dpkg-buildpackage -b -uc >>> > cd /usr/src/drbd-8.3-remus/drbd >>> > make clean >>> > make >>> > make install >>> > cd /usr/src/ >>> > cp /usr/src/drbd-8.3-remus/scripts/global_common.conf.protoD >>> > /etc/drbd.d/global_common.conf >>> > cp /usr/src/drbd-8.3-remus/scripts/testvms_protoD.res >>> > /etc/drbd.d/SystemHA_protoD.res >>> > >>> > sudo apt-get install drbd8-utils >>> > >>> > from tutorial >>> http://remusha.wikidot.com/configuring-and-installing-remus >>> > >>> > My *.res configuration as follow : >>> > >>> > resource drbd-vm{ >>> > device /dev/drbd1; >>> > disk /dev/vgvoip/DomU; >>> > meta-disk internal; >>> > on machine1 { >>> > address 10.10.10.1:7789; >>> > } >>> > on machine2 { >>> > address 10.10.10.3:7789; >>> > } >>> > } >>> > >>> > and then I invoke command to create that meta >>> > >>> > drbdadm create-md drbd-vm >>> > >>> > However, when I try to make this configuration up by : >>> > >>> > drbdadm up drbd-vm >>> > >>> > Its come with error : >>> > >>> > $ sudo drbdadm up drbd-vm >>> > 1: Failure: (124) Device is attached to a disk (use detach first) >>> > Command 'drbdsetup 1 disk /dev/vgvoip/DomU /dev/vgvoip/DomU internal >>> > --set-defaults --create-device --fencing=dont-care >>> --on-io-error=pass_on' >>> > terminated with exit code 10 >>> > >>> > If I run the >>> > >>> > $ sudo drbdadm detach drbd-vm >>> > >>> > Its come error >>> > >>> > $ sudo drbdadm detach drbd-vm >>> > 1: State change failed: (-2) Need access to UpToDate data >>> > Command 'drbdsetup 1 detach' terminated with exit code 17 >>> > >>> > Here the /proc/drbd on both machine >>> > >>> > Machine 1 >>> > >>> > $ sudo cat /proc/drbd >>> > version: 8.3.11 (api:88/proto:86-96) >>> > GIT-hash: 0de839cee13a4160eed6037c4bddd066645e23c5 build by >>> root@machine1, >>> > 2013-02-18 18:49:57 >>> > >>> > 1: cs:StandAlone ro:Primary/Unknown ds:UpToDate/DUnknown r----s >>> > ns:0 nr:0 dw:0 dr:1712 al:0 bm:0 lo:0 pe:0 ua:0 ap:0 ep:1 wo:b >>> def:0 >>> > chkpt:0 oos:10485404 >>> > >>> > >>> > Machine 2 >>> > >>> > $ sudo cat /proc/drbd >>> > version: 8.3.11 (api:88/proto:86-96) >>> > GIT-hash: 0de839cee13a4160eed6037c4bddd066645e23c5 build by >>> root@machine2, >>> > 2013-02-18 19:26:57 >>> > >>> > 1: cs:StandAlone ro:Secondary/Unknown ds:Inconsistent/DUnknown >>> r----s >>> > ns:0 nr:0 dw:0 dr:0 al:0 bm:0 lo:0 pe:0 ua:0 ap:0 ep:1 wo:b def:0 >>> > chkpt:0 oos:10485404 >>> > >>> > >>> > Do you have some hints? >>> > >>> > Thank you, >>> > >>> > >>> > Agya >>> > >>> > >>> >> thanks >>> >> shriram >>> >> >>> >> On Mon, Feb 18, 2013 at 5:38 AM, Hery Dian Septama < >>> herydians@gmail.com> >>> >> wrote: >>> >> > Hello, Anyone have a clue? I have tried but still failed :( >>> >> > >>> >> > On Sat, Feb 16, 2013 at 6:56 PM, agya naila >>> >> > wrote: >>> >> >> >>> >> >> Dear all, >>> >> >> >>> >> >> I am configure my machine to run the remus disk replication. I am >>> using >>> >> >> xen 4.2.3 installed from sources and Ubuntu 12.04 64 bit both for >>> Dom0 >>> >> >> and >>> >> >> DomU. >>> >> >> I have install the blktap and its work properly with configuration >>> >> >> string >>> >> >> phy or tap2 like this : >>> >> >> disk = ['phy:/dev/vggroup/DomU,xvda,w'] >>> >> >> or >>> >> >> disk = ['tap2:tapdisk:aio:/dev/vggroup/DomU,xvda,w'] >>> >> >> >>> >> >> and remus command >>> >> >> >>> >> >> remus --no-net myvm mybackuphost >>> >> >> >>> >> >> >>> >> >> However when I change the string as suggested on remus pages to >>> enable >>> >> >> the >>> >> >> disk replication its still failed : >>> >> >> >>> >> >> name = "DomU" >>> >> >> memory = 1024 >>> >> >> disk = ['tap2:remus:10.10.10.3:8002|aio:/dev/vggroup/DomU,xvda,w'] >>> >> >> vif = ['ip=192.168.1.55,bridge=xenbr0'] >>> >> >> bootloader = "pygrub" >>> >> >> >>> >> >> with error messages : >>> >> >> >>> >> >> name1@machine1:~$ sudo xm create -c /etc/xen/DomU.cfg >>> >> >> Using config file "/etc/xen/DomU.cfg". >>> >> >> Error: ('create', '-aremus:10.10.10.3:8002|aio:/dev/vggroup/DomU') >>> >> >> failed >>> >> >> (512 ) >>> >> >> >>> >> >> and on the log file : >>> >> >> >>> >> >> >>> >> >> name1@machine1:~$ sudo sudo tail /var/log/xen/xend.log >>> >> >> mounted_vbd_uuid = dom0.create_vbd(vbd, disk); >>> >> >> File >>> >> >> >>> "/usr/local/lib/python2.7/dist-packages/xen/xend/XendDomainInfo.py", >>> >> >> line >>> >> >> 3987, in create_vbd >>> >> >> devid = dev_control.createDevice(config) >>> >> >> File >>> >> >> >>> >> >> >>> "/usr/local/lib/python2.7/dist-packages/xen/xend/server/BlktapController.py", >>> >> >> line 174, in createDevice >>> >> >> device = TapdiskController.create(params, file) >>> >> >> File >>> >> >> >>> >> >> >>> "/usr/local/lib/python2.7/dist-packages/xen/xend/server/BlktapController.py", >>> >> >> line 286, in create >>> >> >> return TapdiskController.exc('create', '-a%s:%s' % (dtype, >>> image)) >>> >> >> File >>> >> >> >>> >> >> >>> "/usr/local/lib/python2.7/dist-packages/xen/xend/server/BlktapController.py", >>> >> >> line 233, in exc >>> >> >> (args, rc, out, err)) >>> >> >> TapdiskException: ('create', >>> >> >> '-aremus:10.10.10.3:8002|aio:/dev/vggroup/DomU') failed (512 ) >>> >> >> >>> >> >> Any hints and help would very appreciated. >>> >> >> >>> >> >> Regards, >>> >> >> >>> >> >> Agya >>> >> >> >>> >> >> >>> >> >> _______________________________________________ >>> >> >> Xen-devel mailing list >>> >> >> Xen-devel@lists.xen.org >>> >> >> http://lists.xen.org/xen-devel >>> >> >> >>> >> > >>> >> > >>> >> > _______________________________________________ >>> >> > Xen-devel mailing list >>> >> > Xen-devel@lists.xen.org >>> >> > http://lists.xen.org/xen-devel >>> >> > >>> > >>> > >>> >> >> > --089e0122ef8806d75f04d60eecc2 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Okay, I solve it. I removed drbd8-utils and re-install drbd from sources. D= RBD connected with D protocol. I could go further with disk replication, ho= pefully there is no mistaken step again :)

Regards,

Agya

On Mon, Feb 18, = 2013 at 11:13 PM, agya naila <agya.naila@gmail.com> wrote= :
I forgot to told that its =A0work with proto= col C

=A0$ su= do drbd-overview
=A0 1:drbd-vm =A0SyncTarget Seco= ndary/Secondary Inconsistent/UpToDate C r-----
=A0 =A0 =A0 =A0 [=3D>........= ..........] sync'ed: 12.0% (9016/10236)M

$ sudo drbd-overview
=A0 1:drbd-vm =A0Connected Secon= dary/Secondary UpToDate/UpToDate C r-----


On Mon, Feb 18, = 2013 at 11:00 PM, agya naila <agya.naila@gmail.com> wrote= :
On Mon, Feb 18, 2013 at 10:33 PM, = Shriram Rajagopalan <rshriram@cs.ubc.ca> wrote:
Hi,
=A0I suggest you read up on the DRBD setup documentation from the
drbd.org website.
=A0The setup procedure is same. You can later flip to the remus
replication protocol by simply
=A0changing the protocol type (C to D).

I am comparing my configuration with drbd website, h= owever I got this error :

$ sudo drbdadm up drbd-vm
'D' is no valid proto= col.
Command 'drbdsetup 1 net = ipv4:10.10.10.1:7789 ipv4:10.10.10.3:778= 9 D --set-defaults --create-device --rr-conflict=3Ddisconnect --after-s= b-2pri=3Ddisconnect --after-sb-1pri=3Ddiscard-secondary --after-sb-0pri=3Dd= iscard-younger-primary --allow-two-primaries --ko-count=3D4 --max-epoch-siz= e=3D4096 --unplug-watermark=3D4096 --max-buffers=3D8192 --ping-timeout=3D20= --ping-int=3D3 --timeout=3D30' terminated with exit code 20=
drbdadm connect drbd-vm: exit= ed with code 20
=
$ sudo d= rbd-overview
=A0 = 1:drbd-vm =A0StandAlone Secondary/Unknown UpToDate/DUnknown r----s

Thank you,

Agya

=A0
thanks
shriram

On Mon, Feb 18, 2013 at 4:11 PM, agya naila <agya.naila@gmail.com> wrote:
>
> On Mon, Feb 18, 2013 at 9:08 PM, Shriram Rajagopalan <rshriram@cs.ubc.ca>
> wrote:
>>
>> hi
>
>
> Thank you shriram.
>
>>
>> =A0sorry for the delayed response. IIRC the blktap2 driver require= d for
>> tapdisk replication doesnt exist in the mainstream dom0 kernels, I= IRC.
>> =A0I havent used it in a long time myself. I suggest trying disk >> replication with DRBD.
>>
>
> I am also found some information here
> http://osdir.com/ml/xen-users/2011-07/msg00653.html about b= lktap2 problem on
> amd64 architecture. I have tried to install and configure the DRBD but= its
> didn't connect each other.
> I used drbd-8.3.11-remus and installed as follow
>
> cd /usr/src/
> wget
> http://remusha.wi= kidot.com/local--files/configuring-and-installing-remus/drbd-8.3.11-remus.t= ar.gz
> tar xzf drbd-8.3.9-remus.tar.gz
> chown -R root:root drbd-8.3-remus
> cd /usr/src/drbd-8.3-remus
> chmod 777 autogen.sh
> ./autogen.sh
> dpkg-buildpackage -b -uc
> cd /usr/src/drbd-8.3-remus/drbd
> make clean
> make
> make install
> cd /usr/src/
> cp /usr/src/drbd-8.3-remus/scripts/global_common.conf.protoD
> /etc/drbd.d/global_common.conf
> cp /usr/src/drbd-8.3-remus/scripts/testvms_protoD.res
> /etc/drbd.d/SystemHA_protoD.res
>
> sudo apt-get install drbd8-utils
>
> =A0from tutorial http://remusha.wikidot.com/configuring= -and-installing-remus
>
> My *.res configuration as follow :
>
> resource drbd-vm{
> =A0 device =A0 =A0/dev/drbd1;
> =A0 disk =A0 =A0 =A0/dev/vgvoip/DomU;
> =A0 meta-disk internal;
> =A0 on machine1 {
> =A0 =A0 address =A0 10.10.10.1:7789;
> =A0 }
> =A0 on machine2 {
> =A0 =A0 address =A0 10.10.10.3:7789;
> =A0 }
> }
>
> and then I invoke command to create that meta
>
> drbdadm create-md drbd-vm
>
> However, when I try to make this configuration up by :
>
> drbdadm up drbd-vm
>
> Its come with error :
>
> $ sudo drbdadm up drbd-vm
> 1: Failure: (124) Device is attached to a disk (use detach first)
> Command 'drbdsetup 1 disk /dev/vgvoip/DomU /dev/vgvoip/DomU intern= al
> --set-defaults --create-device --fencing=3Ddont-care --on-io-error=3Dp= ass_on'
> terminated with exit code 10
>
> If I run the
>
> $ sudo drbdadm detach drbd-vm
>
> Its come error
>
> $ sudo drbdadm detach drbd-vm
> 1: State change failed: (-2) Need access to UpToDate data
> Command 'drbdsetup 1 detach' terminated with exit code 17
>
> Here the /proc/drbd on both machine
>
> Machine 1
>
> $ sudo cat /proc/drbd
> version: 8.3.11 (api:88/proto:86-96)
> GIT-hash: 0de839cee13a4160eed6037c4bddd066645e23c5 build by root@machi= ne1,
> 2013-02-18 18:49:57
>
> =A01: cs:StandAlone ro:Primary/Unknown ds:UpToDate/DUnknown =A0 r----s=
> =A0 =A0 ns:0 nr:0 dw:0 dr:1712 al:0 bm:0 lo:0 pe:0 ua:0 ap:0 ep:1 wo:b= def:0
> chkpt:0 oos:10485404
>
>
> Machine 2
>
> $ sudo cat /proc/drbd
> version: 8.3.11 (api:88/proto:86-96)
> GIT-hash: 0de839cee13a4160eed6037c4bddd066645e23c5 build by root@machi= ne2,
> 2013-02-18 19:26:57
>
> =A01: cs:StandAlone ro:Secondary/Unknown ds:Inconsistent/DUnknown =A0 = r----s
> =A0 =A0 ns:0 nr:0 dw:0 dr:0 al:0 bm:0 lo:0 pe:0 ua:0 ap:0 ep:1 wo:b de= f:0
> chkpt:0 oos:10485404
>
>
> Do you have some hints?
>
> Thank you,
>
>
> Agya
>
>
>> thanks
>> shriram
>>
>> On Mon, Feb 18, 2013 at 5:38 AM, Hery Dian Septama <herydians@gmail.com> >> wrote:
>> > Hello, Anyone have a clue? I have tried but still failed :( >> >
>> > On Sat, Feb 16, 2013 at 6:56 PM, agya naila <agya.naila@gmail.com> >> > wrote:
>> >>
>> >> Dear all,
>> >>
>> >> I am configure my machine to run the remus disk replicati= on. I am using
>> >> xen 4.2.3 installed from sources and Ubuntu 12.04 64 bit = both for Dom0
>> >> and
>> >> DomU.
>> >> I have install the blktap and its work properly with conf= iguration
>> >> string
>> >> phy or tap2 like this :
>> >> disk =3D ['phy:/dev/vggroup/DomU,xvda,w']
>> >> or
>> >> disk =3D ['tap2:tapdisk:aio:/dev/vggroup/DomU,xvda,w&= #39;]
>> >>
>> >> and remus command
>> >>
>> >> remus --no-net myvm mybackuphost
>> >>
>> >>
>> >> However when I change the string as suggested on remus pa= ges to enable
>> >> the
>> >> disk replication its still failed :
>> >>
>> >> name =3D "DomU"
>> >> memory =3D 1024
>> >> disk =3D ['tap2:remus:10.10.10.3:8002|aio:/dev/vggrou= p/DomU,xvda,w']
>> >> vif =3D ['ip=3D192.168.1.55,bridge=3Dxenbr0']
>> >> bootloader =3D "pygrub"
>> >>
>> >> with error messages :
>> >>
>> >> name1@machine1:~$ sudo xm create -c /etc/xen/DomU.cfg
>> >> Using config file "/etc/xen/DomU.cfg".
>> >> Error: ('create', '-aremus:10.10.10.3:8002|ai= o:/dev/vggroup/DomU')
>> >> failed
>> >> (512 =A0)
>> >>
>> >> and on the log file :
>> >>
>> >>
>> >> name1@machine1:~$ sudo sudo tail /var/log/xen/xend.log >> >> =A0 =A0 mounted_vbd_uuid =3D dom0.create_vbd(vbd, disk);<= br> >> >> =A0 File
>> >> "/usr/local/lib/python2.7/dist-packages/xen/xend/Xen= dDomainInfo.py",
>> >> line
>> >> 3987, in create_vbd
>> >> =A0 =A0 devid =3D dev_control.createDevice(config)
>> >> =A0 File
>> >>
>> >> "/usr/local/lib/python2.7/dist-packages/xen/xend/ser= ver/BlktapController.py",
>> >> line 174, in createDevice
>> >> =A0 =A0 device =3D TapdiskController.create(params, file)=
>> >> =A0 File
>> >>
>> >> "/usr/local/lib/python2.7/dist-packages/xen/xend/ser= ver/BlktapController.py",
>> >> line 286, in create
>> >> =A0 =A0 return TapdiskController.exc('create', &#= 39;-a%s:%s' % (dtype, image))
>> >> =A0 File
>> >>
>> >> "/usr/local/lib/python2.7/dist-packages/xen/xend/ser= ver/BlktapController.py",
>> >> line 233, in exc
>> >> =A0 =A0 (args, rc, out, err))
>> >> TapdiskException: ('create',
>> >> '-aremus:10.10.10.3:8002|aio:/dev/vggroup/DomU') = failed (512 =A0)
>> >>
>> >> Any hints and help would very appreciated.
>> >>
>> >> Regards,
>> >>
>> >> Agya
>> >>
>> >>
>> >> _______________________________________________
>> >> Xen-devel mailing list
>> >> Xen-devel@lists.xen.org
>> >> http://lists.xen.org/xen-devel
>> >>
>> >
>> >
>> > _______________________________________________
>> > Xen-devel mailing list
>> > = Xen-devel@lists.xen.org
>> > = http://lists.xen.org/xen-devel
>> >
>
>



--089e0122ef8806d75f04d60eecc2-- --===============8203710917008002532== 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 --===============8203710917008002532==-- From xen-users-bounces@lists.xen.org Tue Feb 19 07:39:36 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 19 Feb 2013 07:39: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 1U7hmI-0003DK-TA; Tue, 19 Feb 2013 07:38:14 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U7hmG-0003D5-I0; Tue, 19 Feb 2013 07:38:12 +0000 Received: from [193.109.254.147:14896] by server-14.bemta-14.messagelabs.com id 0D/7D-02031-3EB23215; Tue, 19 Feb 2013 07:38:11 +0000 X-Env-Sender: agya.naila@gmail.com X-Msg-Ref: server-5.tower-27.messagelabs.com!1361259484!6446863!1 X-Originating-IP: [209.85.212.175] 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.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 27229 invoked from network); 19 Feb 2013 07:38:04 -0000 Received: from mail-wi0-f175.google.com (HELO mail-wi0-f175.google.com) (209.85.212.175) by server-5.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 19 Feb 2013 07:38:04 -0000 Received: by mail-wi0-f175.google.com with SMTP id l13so4432769wie.2 for ; Mon, 18 Feb 2013 23:38:04 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=CKZOqcNXKrcF7HX5ICq3Q42QROEcqiPmVHlN6MXIlIs=; b=o2qfu92JHwcGWfcQG0TLqNjZ/HcbYm1tHbxKRdygBWbwBtOHIwl5cuyH7RxsmlAnRL HGeCkjdN9JXQSJ42DUM7zv/8mcURMEjr8PUr9WmafiA1EOzXnzMpz4rKBln3gAbHkRtN CKo6ODTkJdDwa/OMImZqB6t/qvP8V1BaxnCxLkdqAqcEOWt6HwhGfc7yavlTBMVdko5J rmezZF37UPVKB/C5gSZmsN55Z07Iu1pB47e1O1f15MfJQ/2C6RSFUbUAQnWon+/GDVbc Xr/SYkXwG9KCfMiJIZzF9qQL5wyznJ/0pMA1dsDTbzYamlXdnNmJoSf/HN9nkd64efvQ XApQ== MIME-Version: 1.0 X-Received: by 10.194.158.165 with SMTP id wv5mr23954132wjb.45.1361259484599; Mon, 18 Feb 2013 23:38:04 -0800 (PST) Received: by 10.216.236.13 with HTTP; Mon, 18 Feb 2013 23:38:04 -0800 (PST) In-Reply-To: References: Date: Tue, 19 Feb 2013 08:38:04 +0100 Message-ID: From: agya naila To: rshriram@cs.ubc.ca Cc: "xen-users@lists.xen.org" , "xen-devel@lists.xen.org" Subject: Re: [Xen-users] [Xen-devel] Remus disk replication failed X-BeenThere: xen-users@lists.xen.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="===============8203710917008002532==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============8203710917008002532== Content-Type: multipart/alternative; boundary=089e0122ef8806d75f04d60eecc2 --089e0122ef8806d75f04d60eecc2 Content-Type: text/plain; charset=ISO-8859-1 Okay, I solve it. I removed drbd8-utils and re-install drbd from sources. DRBD connected with D protocol. I could go further with disk replication, hopefully there is no mistaken step again :) Regards, Agya On Mon, Feb 18, 2013 at 11:13 PM, agya naila wrote: > I forgot to told that its work with protocol C > > $ sudo drbd-overview > 1:drbd-vm SyncTarget Secondary/Secondary Inconsistent/UpToDate C r----- > [=>..................] sync'ed: 12.0% (9016/10236)M > > $ sudo drbd-overview > 1:drbd-vm Connected Secondary/Secondary UpToDate/UpToDate C r----- > > > On Mon, Feb 18, 2013 at 11:00 PM, agya naila wrote: > >> On Mon, Feb 18, 2013 at 10:33 PM, Shriram Rajagopalan > > wrote: >> >>> Hi, >>> I suggest you read up on the DRBD setup documentation from the >>> drbd.org website. >>> The setup procedure is same. You can later flip to the remus >>> replication protocol by simply >>> changing the protocol type (C to D). >>> >>> I am comparing my configuration with drbd website, however I got this >> error : >> >> $ sudo drbdadm up drbd-vm >> *'D' is no valid protocol.* >> *Command 'drbdsetup 1 net ipv4:10.10.10.1:7789 ipv4:10.10.10.3:7789 D >> --set-defaults --create-device --rr-conflict=disconnect >> --after-sb-2pri=disconnect --after-sb-1pri=discard-secondary >> --after-sb-0pri=discard-younger-primary --allow-two-primaries --ko-count=4 >> --max-epoch-size=4096 --unplug-watermark=4096 --max-buffers=8192 >> --ping-timeout=20 --ping-int=3 --timeout=30' terminated with exit code 20 >> * >> *drbdadm connect drbd-vm: exited with code 20* >> * >> * >> $ sudo drbd-overview >> 1:drbd-vm StandAlone Secondary/Unknown UpToDate/DUnknown r----s >> >> Thank you, >> >> Agya >> >> >> >>> thanks >>> shriram >>> >>> On Mon, Feb 18, 2013 at 4:11 PM, agya naila >>> wrote: >>> > >>> > On Mon, Feb 18, 2013 at 9:08 PM, Shriram Rajagopalan < >>> rshriram@cs.ubc.ca> >>> > wrote: >>> >> >>> >> hi >>> > >>> > >>> > Thank you shriram. >>> > >>> >> >>> >> sorry for the delayed response. IIRC the blktap2 driver required for >>> >> tapdisk replication doesnt exist in the mainstream dom0 kernels, IIRC. >>> >> I havent used it in a long time myself. I suggest trying disk >>> >> replication with DRBD. >>> >> >>> > >>> > I am also found some information here >>> > http://osdir.com/ml/xen-users/2011-07/msg00653.html about blktap2 >>> problem on >>> > amd64 architecture. I have tried to install and configure the DRBD but >>> its >>> > didn't connect each other. >>> > I used drbd-8.3.11-remus and installed as follow >>> > >>> > cd /usr/src/ >>> > wget >>> > >>> http://remusha.wikidot.com/local--files/configuring-and-installing-remus/drbd-8.3.11-remus.tar.gz >>> > tar xzf drbd-8.3.9-remus.tar.gz >>> > chown -R root:root drbd-8.3-remus >>> > cd /usr/src/drbd-8.3-remus >>> > chmod 777 autogen.sh >>> > ./autogen.sh >>> > dpkg-buildpackage -b -uc >>> > cd /usr/src/drbd-8.3-remus/drbd >>> > make clean >>> > make >>> > make install >>> > cd /usr/src/ >>> > cp /usr/src/drbd-8.3-remus/scripts/global_common.conf.protoD >>> > /etc/drbd.d/global_common.conf >>> > cp /usr/src/drbd-8.3-remus/scripts/testvms_protoD.res >>> > /etc/drbd.d/SystemHA_protoD.res >>> > >>> > sudo apt-get install drbd8-utils >>> > >>> > from tutorial >>> http://remusha.wikidot.com/configuring-and-installing-remus >>> > >>> > My *.res configuration as follow : >>> > >>> > resource drbd-vm{ >>> > device /dev/drbd1; >>> > disk /dev/vgvoip/DomU; >>> > meta-disk internal; >>> > on machine1 { >>> > address 10.10.10.1:7789; >>> > } >>> > on machine2 { >>> > address 10.10.10.3:7789; >>> > } >>> > } >>> > >>> > and then I invoke command to create that meta >>> > >>> > drbdadm create-md drbd-vm >>> > >>> > However, when I try to make this configuration up by : >>> > >>> > drbdadm up drbd-vm >>> > >>> > Its come with error : >>> > >>> > $ sudo drbdadm up drbd-vm >>> > 1: Failure: (124) Device is attached to a disk (use detach first) >>> > Command 'drbdsetup 1 disk /dev/vgvoip/DomU /dev/vgvoip/DomU internal >>> > --set-defaults --create-device --fencing=dont-care >>> --on-io-error=pass_on' >>> > terminated with exit code 10 >>> > >>> > If I run the >>> > >>> > $ sudo drbdadm detach drbd-vm >>> > >>> > Its come error >>> > >>> > $ sudo drbdadm detach drbd-vm >>> > 1: State change failed: (-2) Need access to UpToDate data >>> > Command 'drbdsetup 1 detach' terminated with exit code 17 >>> > >>> > Here the /proc/drbd on both machine >>> > >>> > Machine 1 >>> > >>> > $ sudo cat /proc/drbd >>> > version: 8.3.11 (api:88/proto:86-96) >>> > GIT-hash: 0de839cee13a4160eed6037c4bddd066645e23c5 build by >>> root@machine1, >>> > 2013-02-18 18:49:57 >>> > >>> > 1: cs:StandAlone ro:Primary/Unknown ds:UpToDate/DUnknown r----s >>> > ns:0 nr:0 dw:0 dr:1712 al:0 bm:0 lo:0 pe:0 ua:0 ap:0 ep:1 wo:b >>> def:0 >>> > chkpt:0 oos:10485404 >>> > >>> > >>> > Machine 2 >>> > >>> > $ sudo cat /proc/drbd >>> > version: 8.3.11 (api:88/proto:86-96) >>> > GIT-hash: 0de839cee13a4160eed6037c4bddd066645e23c5 build by >>> root@machine2, >>> > 2013-02-18 19:26:57 >>> > >>> > 1: cs:StandAlone ro:Secondary/Unknown ds:Inconsistent/DUnknown >>> r----s >>> > ns:0 nr:0 dw:0 dr:0 al:0 bm:0 lo:0 pe:0 ua:0 ap:0 ep:1 wo:b def:0 >>> > chkpt:0 oos:10485404 >>> > >>> > >>> > Do you have some hints? >>> > >>> > Thank you, >>> > >>> > >>> > Agya >>> > >>> > >>> >> thanks >>> >> shriram >>> >> >>> >> On Mon, Feb 18, 2013 at 5:38 AM, Hery Dian Septama < >>> herydians@gmail.com> >>> >> wrote: >>> >> > Hello, Anyone have a clue? I have tried but still failed :( >>> >> > >>> >> > On Sat, Feb 16, 2013 at 6:56 PM, agya naila >>> >> > wrote: >>> >> >> >>> >> >> Dear all, >>> >> >> >>> >> >> I am configure my machine to run the remus disk replication. I am >>> using >>> >> >> xen 4.2.3 installed from sources and Ubuntu 12.04 64 bit both for >>> Dom0 >>> >> >> and >>> >> >> DomU. >>> >> >> I have install the blktap and its work properly with configuration >>> >> >> string >>> >> >> phy or tap2 like this : >>> >> >> disk = ['phy:/dev/vggroup/DomU,xvda,w'] >>> >> >> or >>> >> >> disk = ['tap2:tapdisk:aio:/dev/vggroup/DomU,xvda,w'] >>> >> >> >>> >> >> and remus command >>> >> >> >>> >> >> remus --no-net myvm mybackuphost >>> >> >> >>> >> >> >>> >> >> However when I change the string as suggested on remus pages to >>> enable >>> >> >> the >>> >> >> disk replication its still failed : >>> >> >> >>> >> >> name = "DomU" >>> >> >> memory = 1024 >>> >> >> disk = ['tap2:remus:10.10.10.3:8002|aio:/dev/vggroup/DomU,xvda,w'] >>> >> >> vif = ['ip=192.168.1.55,bridge=xenbr0'] >>> >> >> bootloader = "pygrub" >>> >> >> >>> >> >> with error messages : >>> >> >> >>> >> >> name1@machine1:~$ sudo xm create -c /etc/xen/DomU.cfg >>> >> >> Using config file "/etc/xen/DomU.cfg". >>> >> >> Error: ('create', '-aremus:10.10.10.3:8002|aio:/dev/vggroup/DomU') >>> >> >> failed >>> >> >> (512 ) >>> >> >> >>> >> >> and on the log file : >>> >> >> >>> >> >> >>> >> >> name1@machine1:~$ sudo sudo tail /var/log/xen/xend.log >>> >> >> mounted_vbd_uuid = dom0.create_vbd(vbd, disk); >>> >> >> File >>> >> >> >>> "/usr/local/lib/python2.7/dist-packages/xen/xend/XendDomainInfo.py", >>> >> >> line >>> >> >> 3987, in create_vbd >>> >> >> devid = dev_control.createDevice(config) >>> >> >> File >>> >> >> >>> >> >> >>> "/usr/local/lib/python2.7/dist-packages/xen/xend/server/BlktapController.py", >>> >> >> line 174, in createDevice >>> >> >> device = TapdiskController.create(params, file) >>> >> >> File >>> >> >> >>> >> >> >>> "/usr/local/lib/python2.7/dist-packages/xen/xend/server/BlktapController.py", >>> >> >> line 286, in create >>> >> >> return TapdiskController.exc('create', '-a%s:%s' % (dtype, >>> image)) >>> >> >> File >>> >> >> >>> >> >> >>> "/usr/local/lib/python2.7/dist-packages/xen/xend/server/BlktapController.py", >>> >> >> line 233, in exc >>> >> >> (args, rc, out, err)) >>> >> >> TapdiskException: ('create', >>> >> >> '-aremus:10.10.10.3:8002|aio:/dev/vggroup/DomU') failed (512 ) >>> >> >> >>> >> >> Any hints and help would very appreciated. >>> >> >> >>> >> >> Regards, >>> >> >> >>> >> >> Agya >>> >> >> >>> >> >> >>> >> >> _______________________________________________ >>> >> >> Xen-devel mailing list >>> >> >> Xen-devel@lists.xen.org >>> >> >> http://lists.xen.org/xen-devel >>> >> >> >>> >> > >>> >> > >>> >> > _______________________________________________ >>> >> > Xen-devel mailing list >>> >> > Xen-devel@lists.xen.org >>> >> > http://lists.xen.org/xen-devel >>> >> > >>> > >>> > >>> >> >> > --089e0122ef8806d75f04d60eecc2 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Okay, I solve it. I removed drbd8-utils and re-install drbd from sources. D= RBD connected with D protocol. I could go further with disk replication, ho= pefully there is no mistaken step again :)

Regards,

Agya

On Mon, Feb 18, = 2013 at 11:13 PM, agya naila <agya.naila@gmail.com> wrote= :
I forgot to told that its =A0work with proto= col C

=A0$ su= do drbd-overview
=A0 1:drbd-vm =A0SyncTarget Seco= ndary/Secondary Inconsistent/UpToDate C r-----
=A0 =A0 =A0 =A0 [=3D>........= ..........] sync'ed: 12.0% (9016/10236)M

$ sudo drbd-overview
=A0 1:drbd-vm =A0Connected Secon= dary/Secondary UpToDate/UpToDate C r-----


On Mon, Feb 18, = 2013 at 11:00 PM, agya naila <agya.naila@gmail.com> wrote= :
On Mon, Feb 18, 2013 at 10:33 PM, = Shriram Rajagopalan <rshriram@cs.ubc.ca> wrote:
Hi,
=A0I suggest you read up on the DRBD setup documentation from the
drbd.org website.
=A0The setup procedure is same. You can later flip to the remus
replication protocol by simply
=A0changing the protocol type (C to D).

I am comparing my configuration with drbd website, h= owever I got this error :

$ sudo drbdadm up drbd-vm
'D' is no valid proto= col.
Command 'drbdsetup 1 net = ipv4:10.10.10.1:7789 ipv4:10.10.10.3:778= 9 D --set-defaults --create-device --rr-conflict=3Ddisconnect --after-s= b-2pri=3Ddisconnect --after-sb-1pri=3Ddiscard-secondary --after-sb-0pri=3Dd= iscard-younger-primary --allow-two-primaries --ko-count=3D4 --max-epoch-siz= e=3D4096 --unplug-watermark=3D4096 --max-buffers=3D8192 --ping-timeout=3D20= --ping-int=3D3 --timeout=3D30' terminated with exit code 20=
drbdadm connect drbd-vm: exit= ed with code 20
=
$ sudo d= rbd-overview
=A0 = 1:drbd-vm =A0StandAlone Secondary/Unknown UpToDate/DUnknown r----s

Thank you,

Agya

=A0
thanks
shriram

On Mon, Feb 18, 2013 at 4:11 PM, agya naila <agya.naila@gmail.com> wrote:
>
> On Mon, Feb 18, 2013 at 9:08 PM, Shriram Rajagopalan <rshriram@cs.ubc.ca>
> wrote:
>>
>> hi
>
>
> Thank you shriram.
>
>>
>> =A0sorry for the delayed response. IIRC the blktap2 driver require= d for
>> tapdisk replication doesnt exist in the mainstream dom0 kernels, I= IRC.
>> =A0I havent used it in a long time myself. I suggest trying disk >> replication with DRBD.
>>
>
> I am also found some information here
> http://osdir.com/ml/xen-users/2011-07/msg00653.html about b= lktap2 problem on
> amd64 architecture. I have tried to install and configure the DRBD but= its
> didn't connect each other.
> I used drbd-8.3.11-remus and installed as follow
>
> cd /usr/src/
> wget
> http://remusha.wi= kidot.com/local--files/configuring-and-installing-remus/drbd-8.3.11-remus.t= ar.gz
> tar xzf drbd-8.3.9-remus.tar.gz
> chown -R root:root drbd-8.3-remus
> cd /usr/src/drbd-8.3-remus
> chmod 777 autogen.sh
> ./autogen.sh
> dpkg-buildpackage -b -uc
> cd /usr/src/drbd-8.3-remus/drbd
> make clean
> make
> make install
> cd /usr/src/
> cp /usr/src/drbd-8.3-remus/scripts/global_common.conf.protoD
> /etc/drbd.d/global_common.conf
> cp /usr/src/drbd-8.3-remus/scripts/testvms_protoD.res
> /etc/drbd.d/SystemHA_protoD.res
>
> sudo apt-get install drbd8-utils
>
> =A0from tutorial http://remusha.wikidot.com/configuring= -and-installing-remus
>
> My *.res configuration as follow :
>
> resource drbd-vm{
> =A0 device =A0 =A0/dev/drbd1;
> =A0 disk =A0 =A0 =A0/dev/vgvoip/DomU;
> =A0 meta-disk internal;
> =A0 on machine1 {
> =A0 =A0 address =A0 10.10.10.1:7789;
> =A0 }
> =A0 on machine2 {
> =A0 =A0 address =A0 10.10.10.3:7789;
> =A0 }
> }
>
> and then I invoke command to create that meta
>
> drbdadm create-md drbd-vm
>
> However, when I try to make this configuration up by :
>
> drbdadm up drbd-vm
>
> Its come with error :
>
> $ sudo drbdadm up drbd-vm
> 1: Failure: (124) Device is attached to a disk (use detach first)
> Command 'drbdsetup 1 disk /dev/vgvoip/DomU /dev/vgvoip/DomU intern= al
> --set-defaults --create-device --fencing=3Ddont-care --on-io-error=3Dp= ass_on'
> terminated with exit code 10
>
> If I run the
>
> $ sudo drbdadm detach drbd-vm
>
> Its come error
>
> $ sudo drbdadm detach drbd-vm
> 1: State change failed: (-2) Need access to UpToDate data
> Command 'drbdsetup 1 detach' terminated with exit code 17
>
> Here the /proc/drbd on both machine
>
> Machine 1
>
> $ sudo cat /proc/drbd
> version: 8.3.11 (api:88/proto:86-96)
> GIT-hash: 0de839cee13a4160eed6037c4bddd066645e23c5 build by root@machi= ne1,
> 2013-02-18 18:49:57
>
> =A01: cs:StandAlone ro:Primary/Unknown ds:UpToDate/DUnknown =A0 r----s=
> =A0 =A0 ns:0 nr:0 dw:0 dr:1712 al:0 bm:0 lo:0 pe:0 ua:0 ap:0 ep:1 wo:b= def:0
> chkpt:0 oos:10485404
>
>
> Machine 2
>
> $ sudo cat /proc/drbd
> version: 8.3.11 (api:88/proto:86-96)
> GIT-hash: 0de839cee13a4160eed6037c4bddd066645e23c5 build by root@machi= ne2,
> 2013-02-18 19:26:57
>
> =A01: cs:StandAlone ro:Secondary/Unknown ds:Inconsistent/DUnknown =A0 = r----s
> =A0 =A0 ns:0 nr:0 dw:0 dr:0 al:0 bm:0 lo:0 pe:0 ua:0 ap:0 ep:1 wo:b de= f:0
> chkpt:0 oos:10485404
>
>
> Do you have some hints?
>
> Thank you,
>
>
> Agya
>
>
>> thanks
>> shriram
>>
>> On Mon, Feb 18, 2013 at 5:38 AM, Hery Dian Septama <herydians@gmail.com> >> wrote:
>> > Hello, Anyone have a clue? I have tried but still failed :( >> >
>> > On Sat, Feb 16, 2013 at 6:56 PM, agya naila <agya.naila@gmail.com> >> > wrote:
>> >>
>> >> Dear all,
>> >>
>> >> I am configure my machine to run the remus disk replicati= on. I am using
>> >> xen 4.2.3 installed from sources and Ubuntu 12.04 64 bit = both for Dom0
>> >> and
>> >> DomU.
>> >> I have install the blktap and its work properly with conf= iguration
>> >> string
>> >> phy or tap2 like this :
>> >> disk =3D ['phy:/dev/vggroup/DomU,xvda,w']
>> >> or
>> >> disk =3D ['tap2:tapdisk:aio:/dev/vggroup/DomU,xvda,w&= #39;]
>> >>
>> >> and remus command
>> >>
>> >> remus --no-net myvm mybackuphost
>> >>
>> >>
>> >> However when I change the string as suggested on remus pa= ges to enable
>> >> the
>> >> disk replication its still failed :
>> >>
>> >> name =3D "DomU"
>> >> memory =3D 1024
>> >> disk =3D ['tap2:remus:10.10.10.3:8002|aio:/dev/vggrou= p/DomU,xvda,w']
>> >> vif =3D ['ip=3D192.168.1.55,bridge=3Dxenbr0']
>> >> bootloader =3D "pygrub"
>> >>
>> >> with error messages :
>> >>
>> >> name1@machine1:~$ sudo xm create -c /etc/xen/DomU.cfg
>> >> Using config file "/etc/xen/DomU.cfg".
>> >> Error: ('create', '-aremus:10.10.10.3:8002|ai= o:/dev/vggroup/DomU')
>> >> failed
>> >> (512 =A0)
>> >>
>> >> and on the log file :
>> >>
>> >>
>> >> name1@machine1:~$ sudo sudo tail /var/log/xen/xend.log >> >> =A0 =A0 mounted_vbd_uuid =3D dom0.create_vbd(vbd, disk);<= br> >> >> =A0 File
>> >> "/usr/local/lib/python2.7/dist-packages/xen/xend/Xen= dDomainInfo.py",
>> >> line
>> >> 3987, in create_vbd
>> >> =A0 =A0 devid =3D dev_control.createDevice(config)
>> >> =A0 File
>> >>
>> >> "/usr/local/lib/python2.7/dist-packages/xen/xend/ser= ver/BlktapController.py",
>> >> line 174, in createDevice
>> >> =A0 =A0 device =3D TapdiskController.create(params, file)=
>> >> =A0 File
>> >>
>> >> "/usr/local/lib/python2.7/dist-packages/xen/xend/ser= ver/BlktapController.py",
>> >> line 286, in create
>> >> =A0 =A0 return TapdiskController.exc('create', &#= 39;-a%s:%s' % (dtype, image))
>> >> =A0 File
>> >>
>> >> "/usr/local/lib/python2.7/dist-packages/xen/xend/ser= ver/BlktapController.py",
>> >> line 233, in exc
>> >> =A0 =A0 (args, rc, out, err))
>> >> TapdiskException: ('create',
>> >> '-aremus:10.10.10.3:8002|aio:/dev/vggroup/DomU') = failed (512 =A0)
>> >>
>> >> Any hints and help would very appreciated.
>> >>
>> >> Regards,
>> >>
>> >> Agya
>> >>
>> >>
>> >> _______________________________________________
>> >> Xen-devel mailing list
>> >> Xen-devel@lists.xen.org
>> >> http://lists.xen.org/xen-devel
>> >>
>> >
>> >
>> > _______________________________________________
>> > Xen-devel mailing list
>> > = Xen-devel@lists.xen.org
>> > = http://lists.xen.org/xen-devel
>> >
>
>



--089e0122ef8806d75f04d60eecc2-- --===============8203710917008002532== 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 --===============8203710917008002532==-- From xen-users-bounces@lists.xen.org Tue Feb 19 08:48:33 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 19 Feb 2013 08:48: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 1U7irC-0004iT-2C; Tue, 19 Feb 2013 08:47:22 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U7irA-0004iO-Pb for xen-users@lists.xen.org; Tue, 19 Feb 2013 08:47:20 +0000 Received: from [193.109.254.147:27509] by server-15.bemta-14.messagelabs.com id 45/E9-24599-71C33215; Tue, 19 Feb 2013 08:47:19 +0000 X-Env-Sender: Ian.Campbell@citrix.com X-Msg-Ref: server-10.tower-27.messagelabs.com!1361263557!3739730!1 X-Originating-IP: [46.33.159.39] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNDYuMzMuMTU5LjM5ID0+IDIzMzg5\n X-StarScan-Received: X-StarScan-Version: 6.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 5355 invoked from network); 19 Feb 2013 08:46:07 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (46.33.159.39) by server-10.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 19 Feb 2013 08:46:07 -0000 X-IronPort-AV: E=Sophos;i="4.84,693,1355097600"; d="scan'208";a="1592973" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 19 Feb 2013 08:45: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.297.1; Tue, 19 Feb 2013 08:45:40 +0000 Message-ID: <1361263538.1051.52.camel@zakaz.uk.xensource.com> From: Ian Campbell To: Dale Galekovic Date: Tue, 19 Feb 2013 08:45:38 +0000 In-Reply-To: <374DD7FF31C7AB4EA7E0B48BD2049C821F9BBB71@BLUPRD0511MB426.namprd05.prod.outlook.com> References: <374DD7FF31C7AB4EA7E0B48BD2049C821F9BBB71@BLUPRD0511MB426.namprd05.prod.outlook.com> Organization: Citrix Systems, Inc. X-Mailer: Evolution 3.4.4-1 MIME-Version: 1.0 Cc: "xen-users@lists.xen.org" Subject: Re: [Xen-users] Problem building Tools Xen 4.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="utf-8" Content-Transfer-Encoding: base64 Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org T24gTW9uLCAyMDEzLTAyLTE4IGF0IDE3OjQ4ICswMDAwLCBEYWxlIEdhbGVrb3ZpYyB3cm90ZToK PiBOb3Qgc3VyZSBpZiBpdOKAmXMgZmlyZXdhbGwgcmVsYXRlZC4KCkl0IGNlcnRhaW5seSBsb29r cyBsaWtlIGl0LgoKPiAgRG9lcyBhbnlvbmUga25vdyB3aGF0IHBvcnQgZ2l0IHVzZXM/CgpJIGRv bid0IG9mZmhhbmQgYnV0IEknbSBzdXJlIHlvdSBjYW4gZ29vZ2xlIG9yIGdyZXAgL2V0Yy9zZXJ2 aWNlcyBqdXN0CmFzIGVhc2lseSBhcyBJIGNhbi4uLgoKSWYgeW91IGNhbm5vdCBnZXQgdGhlIHJp Z2h0IHBvcnQgb3BlbmVkIHRoZW4geW91IGNhbiB1c2UgdGhlIHNsb3dlciBodHRwCmJhc2VkIG1l dGhvZCB3aXRoIGdpdCB0byBjbG9uZSB0aGVzZSB0cmVlcywgcGFzcyAiLS1lbmFibGUtZ2l0aHR0 cCIgdG8KY29uZmlndXJlLgoKSWFuLgoKCgpfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f X19fX19fX19fX19fX19fXwpYZW4tdXNlcnMgbWFpbGluZyBsaXN0Clhlbi11c2Vyc0BsaXN0cy54 ZW4ub3JnCmh0dHA6Ly9saXN0cy54ZW4ub3JnL3hlbi11c2Vycw== From xen-users-bounces@lists.xen.org Tue Feb 19 08:48:33 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 19 Feb 2013 08:48: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 1U7irC-0004iT-2C; Tue, 19 Feb 2013 08:47:22 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U7irA-0004iO-Pb for xen-users@lists.xen.org; Tue, 19 Feb 2013 08:47:20 +0000 Received: from [193.109.254.147:27509] by server-15.bemta-14.messagelabs.com id 45/E9-24599-71C33215; Tue, 19 Feb 2013 08:47:19 +0000 X-Env-Sender: Ian.Campbell@citrix.com X-Msg-Ref: server-10.tower-27.messagelabs.com!1361263557!3739730!1 X-Originating-IP: [46.33.159.39] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNDYuMzMuMTU5LjM5ID0+IDIzMzg5\n X-StarScan-Received: X-StarScan-Version: 6.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 5355 invoked from network); 19 Feb 2013 08:46:07 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (46.33.159.39) by server-10.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 19 Feb 2013 08:46:07 -0000 X-IronPort-AV: E=Sophos;i="4.84,693,1355097600"; d="scan'208";a="1592973" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 19 Feb 2013 08:45: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.297.1; Tue, 19 Feb 2013 08:45:40 +0000 Message-ID: <1361263538.1051.52.camel@zakaz.uk.xensource.com> From: Ian Campbell To: Dale Galekovic Date: Tue, 19 Feb 2013 08:45:38 +0000 In-Reply-To: <374DD7FF31C7AB4EA7E0B48BD2049C821F9BBB71@BLUPRD0511MB426.namprd05.prod.outlook.com> References: <374DD7FF31C7AB4EA7E0B48BD2049C821F9BBB71@BLUPRD0511MB426.namprd05.prod.outlook.com> Organization: Citrix Systems, Inc. X-Mailer: Evolution 3.4.4-1 MIME-Version: 1.0 Cc: "xen-users@lists.xen.org" Subject: Re: [Xen-users] Problem building Tools Xen 4.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="utf-8" Content-Transfer-Encoding: base64 Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org T24gTW9uLCAyMDEzLTAyLTE4IGF0IDE3OjQ4ICswMDAwLCBEYWxlIEdhbGVrb3ZpYyB3cm90ZToK PiBOb3Qgc3VyZSBpZiBpdOKAmXMgZmlyZXdhbGwgcmVsYXRlZC4KCkl0IGNlcnRhaW5seSBsb29r cyBsaWtlIGl0LgoKPiAgRG9lcyBhbnlvbmUga25vdyB3aGF0IHBvcnQgZ2l0IHVzZXM/CgpJIGRv bid0IG9mZmhhbmQgYnV0IEknbSBzdXJlIHlvdSBjYW4gZ29vZ2xlIG9yIGdyZXAgL2V0Yy9zZXJ2 aWNlcyBqdXN0CmFzIGVhc2lseSBhcyBJIGNhbi4uLgoKSWYgeW91IGNhbm5vdCBnZXQgdGhlIHJp Z2h0IHBvcnQgb3BlbmVkIHRoZW4geW91IGNhbiB1c2UgdGhlIHNsb3dlciBodHRwCmJhc2VkIG1l dGhvZCB3aXRoIGdpdCB0byBjbG9uZSB0aGVzZSB0cmVlcywgcGFzcyAiLS1lbmFibGUtZ2l0aHR0 cCIgdG8KY29uZmlndXJlLgoKSWFuLgoKCgpfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f X19fX19fX19fX19fX19fXwpYZW4tdXNlcnMgbWFpbGluZyBsaXN0Clhlbi11c2Vyc0BsaXN0cy54 ZW4ub3JnCmh0dHA6Ly9saXN0cy54ZW4ub3JnL3hlbi11c2Vycw== From xen-users-bounces@lists.xen.org Tue Feb 19 10:13:11 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 19 Feb 2013 10:13: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 1U7kB7-0006hM-Pi; Tue, 19 Feb 2013 10:12:01 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U7kB5-0006hH-VZ for xen-users@lists.xen.org; Tue, 19 Feb 2013 10:12:00 +0000 Received: from [85.158.143.99:20720] by server-1.bemta-4.messagelabs.com id 1B/8B-08839-EEF43215; Tue, 19 Feb 2013 10:11:58 +0000 X-Env-Sender: Ian.Campbell@citrix.com X-Msg-Ref: server-9.tower-216.messagelabs.com!1361268717!28163580!1 X-Originating-IP: [46.33.159.39] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNDYuMzMuMTU5LjM5ID0+IDIzNTM5\n X-StarScan-Received: X-StarScan-Version: 6.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 4840 invoked from network); 19 Feb 2013 10:11:57 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (46.33.159.39) by server-9.tower-216.messagelabs.com with RC4-SHA encrypted SMTP; 19 Feb 2013 10:11:57 -0000 X-IronPort-AV: E=Sophos;i="4.84,694,1355097600"; d="scan'208";a="1596717" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 19 Feb 2013 10:11:57 +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.297.1; Tue, 19 Feb 2013 10:11:57 +0000 Message-ID: <1361268715.1051.85.camel@zakaz.uk.xensource.com> From: Ian Campbell To: Ian Date: Tue, 19 Feb 2013 10:11:55 +0000 In-Reply-To: <5122C609.3060706@yahoo.co.uk> References: <5122C609.3060706@yahoo.co.uk> Organization: Citrix Systems, Inc. X-Mailer: Evolution 3.4.4-1 MIME-Version: 1.0 Cc: "xen-users@lists.xen.org" Subject: Re: [Xen-users] xendomains stop and gplpv network questions X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: 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, 2013-02-19 at 00:23 +0000, Ian wrote: > Xendomains is always horribly broken for me when using xl. I wrote a > patch to fix it. Did you resend this patch as discussed in <1357813957.67365.YahooMailNeo@web171303.mail.ir2.yahoo.com> ? Sorry if I've missed it somewhere along the way. > I can't remember if I was getting exactly the same > behaviour as you, but it is worth a try. > This is using the script from the vanilla Xen sources, so I doubt it > will patch against the Debian version. IIRC Debian has a completely rewritten version of this script. It's likely that the Ubuntu packages have picked this up also. Of course this won't matter if you are pulling from source. Ian. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Tue Feb 19 10:13:11 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 19 Feb 2013 10:13: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 1U7kB7-0006hM-Pi; Tue, 19 Feb 2013 10:12:01 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U7kB5-0006hH-VZ for xen-users@lists.xen.org; Tue, 19 Feb 2013 10:12:00 +0000 Received: from [85.158.143.99:20720] by server-1.bemta-4.messagelabs.com id 1B/8B-08839-EEF43215; Tue, 19 Feb 2013 10:11:58 +0000 X-Env-Sender: Ian.Campbell@citrix.com X-Msg-Ref: server-9.tower-216.messagelabs.com!1361268717!28163580!1 X-Originating-IP: [46.33.159.39] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNDYuMzMuMTU5LjM5ID0+IDIzNTM5\n X-StarScan-Received: X-StarScan-Version: 6.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 4840 invoked from network); 19 Feb 2013 10:11:57 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (46.33.159.39) by server-9.tower-216.messagelabs.com with RC4-SHA encrypted SMTP; 19 Feb 2013 10:11:57 -0000 X-IronPort-AV: E=Sophos;i="4.84,694,1355097600"; d="scan'208";a="1596717" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 19 Feb 2013 10:11:57 +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.297.1; Tue, 19 Feb 2013 10:11:57 +0000 Message-ID: <1361268715.1051.85.camel@zakaz.uk.xensource.com> From: Ian Campbell To: Ian Date: Tue, 19 Feb 2013 10:11:55 +0000 In-Reply-To: <5122C609.3060706@yahoo.co.uk> References: <5122C609.3060706@yahoo.co.uk> Organization: Citrix Systems, Inc. X-Mailer: Evolution 3.4.4-1 MIME-Version: 1.0 Cc: "xen-users@lists.xen.org" Subject: Re: [Xen-users] xendomains stop and gplpv network questions X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: 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, 2013-02-19 at 00:23 +0000, Ian wrote: > Xendomains is always horribly broken for me when using xl. I wrote a > patch to fix it. Did you resend this patch as discussed in <1357813957.67365.YahooMailNeo@web171303.mail.ir2.yahoo.com> ? Sorry if I've missed it somewhere along the way. > I can't remember if I was getting exactly the same > behaviour as you, but it is worth a try. > This is using the script from the vanilla Xen sources, so I doubt it > will patch against the Debian version. IIRC Debian has a completely rewritten version of this script. It's likely that the Ubuntu packages have picked this up also. Of course this won't matter if you are pulling from source. Ian. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Tue Feb 19 11:24:31 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 19 Feb 2013 11:24: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 1U7lIA-0007Yy-8L; Tue, 19 Feb 2013 11:23:22 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U7lI8-0007Yt-E8 for xen-users@lists.xen.org; Tue, 19 Feb 2013 11:23:20 +0000 Received: from [85.158.139.211:17454] by server-11.bemta-5.messagelabs.com id 36/79-19159-7A063215; Tue, 19 Feb 2013 11:23:19 +0000 X-Env-Sender: raistlin.df@gmail.com X-Msg-Ref: server-14.tower-206.messagelabs.com!1361272949!18154777!1 X-Originating-IP: [74.125.83.45] X-SpamReason: No, hits=0.0 required=7.0 tests=ML_RADAR_SPEW_LINKS_8, spamassassin: , async_handler: YXN5bmNfZGVsYXk6IDcwNTMwOTcgKHRpbWVvdXQp\n X-StarScan-Received: X-StarScan-Version: 6.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 5435 invoked from network); 19 Feb 2013 11:22:30 -0000 Received: from mail-ee0-f45.google.com (HELO mail-ee0-f45.google.com) (74.125.83.45) by server-14.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 19 Feb 2013 11:22:30 -0000 Received: by mail-ee0-f45.google.com with SMTP id b57so3319824eek.4 for ; Tue, 19 Feb 2013 03:21:56 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:sender:message-id:subject:from:to:cc:date:in-reply-to :references:content-type:x-mailer:mime-version; bh=2xjequ5WxpRjWgKH9TFN6lHJmXfm2ABzqu7T7ejvJHQ=; b=acNQJPHDJbMebBjLxjSAuyZ0QE9kSepLwXN++mh4+RwTsOdoV+IPziFahjaSCtxRWG IEFcOdH+8ciYk7j+nXGqmD/3LWSXYZ4k//cIVlvWF8nj+mytpTelefSsKthzy9g+9T4N 7aHPrsia9YlStGXdhzI2/llNjQ7F0U0C8T+C2/dg8JuaSpv77IQ8JkgECmj449E5EWou 8Ut+V+hlsqw2RTW6DgjpbXET1nECp7QsaoDZ8vqOSKobzgVBeXUGnqniZTV116pX8io1 AfXMtsSS0cQQ4duTIL2832UoiZ/9mnukY2iFvmQQZkvAoPJqFa+bwlUTn2Xs9h8A2/x2 Y1uA== X-Received: by 10.14.225.72 with SMTP id y48mr55916984eep.45.1361272916612; Tue, 19 Feb 2013 03:21:56 -0800 (PST) Received: from [192.168.0.20] (ip-143-209.sn3.eutelia.it. [213.136.143.209]) by mx.google.com with ESMTPS id u44sm43503546eel.7.2013.02.19.03.21.53 (version=TLSv1 cipher=RC4-SHA bits=128/128); Tue, 19 Feb 2013 03:21:55 -0800 (PST) Message-ID: <1361272892.30467.1.camel@Abyss> From: Dario Faggioli To: Tom Date: Tue, 19 Feb 2013 12:21:32 +0100 In-Reply-To: References: X-Mailer: Evolution 3.6.3 (3.6.3-2.fc18) Mime-Version: 1.0 Cc: "xen-users@lists.xen.org" Subject: Re: [Xen-users] Issue with starting X with Intel gfx card (Ubuntu 12.10) X-BeenThere: xen-users@lists.xen.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="===============7257468857781042680==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============7257468857781042680== Content-Type: multipart/signed; micalg="pgp-sha1"; protocol="application/pgp-signature"; boundary="=-0qkBZUWAhKzpy5cDXJjC" --=-0qkBZUWAhKzpy5cDXJjC Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On dom, 2013-02-17 at 13:05 +0000, Tom wrote: > Hi, >=20 Hello, > I'm trying to get my X working with Xen on my Ubuntu 12.10 oob > installation, but keeps on hanging on boot; >=20 Hangs where? Kernel? Init scripts? "Just" Xorg? > lspci | grep VGA > 00:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200 > v2/3rd Gen Core processor Graphics Controller (rev 09) >=20 Yeah, fine, but until we don't understand _where_ in the boot process it hangs, it's going to be quite hard to blame specific components... Regards, Dario --=20 <> (Raistlin Majere) ----------------------------------------------------------------- Dario Faggioli, Ph.D, http://about.me/dario.faggioli Senior Software Engineer, Citrix Systems R&D Ltd., Cambridge (UK) --=-0qkBZUWAhKzpy5cDXJjC 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.13 (GNU/Linux) iEYEABECAAYFAlEjYDwACgkQk4XaBE3IOsRm1gCeOV3Lo4R5/kBPcN7+m7HFhT0S LX4An3dxKAWlJcBQB4LYFmJW0C7deTNs =YdJ+ -----END PGP SIGNATURE----- --=-0qkBZUWAhKzpy5cDXJjC-- --===============7257468857781042680== 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 --===============7257468857781042680==-- From xen-users-bounces@lists.xen.org Tue Feb 19 11:24:31 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 19 Feb 2013 11:24: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 1U7lIA-0007Yy-8L; Tue, 19 Feb 2013 11:23:22 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U7lI8-0007Yt-E8 for xen-users@lists.xen.org; Tue, 19 Feb 2013 11:23:20 +0000 Received: from [85.158.139.211:17454] by server-11.bemta-5.messagelabs.com id 36/79-19159-7A063215; Tue, 19 Feb 2013 11:23:19 +0000 X-Env-Sender: raistlin.df@gmail.com X-Msg-Ref: server-14.tower-206.messagelabs.com!1361272949!18154777!1 X-Originating-IP: [74.125.83.45] X-SpamReason: No, hits=0.0 required=7.0 tests=ML_RADAR_SPEW_LINKS_8, spamassassin: , async_handler: YXN5bmNfZGVsYXk6IDcwNTMwOTcgKHRpbWVvdXQp\n X-StarScan-Received: X-StarScan-Version: 6.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 5435 invoked from network); 19 Feb 2013 11:22:30 -0000 Received: from mail-ee0-f45.google.com (HELO mail-ee0-f45.google.com) (74.125.83.45) by server-14.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 19 Feb 2013 11:22:30 -0000 Received: by mail-ee0-f45.google.com with SMTP id b57so3319824eek.4 for ; Tue, 19 Feb 2013 03:21:56 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:sender:message-id:subject:from:to:cc:date:in-reply-to :references:content-type:x-mailer:mime-version; bh=2xjequ5WxpRjWgKH9TFN6lHJmXfm2ABzqu7T7ejvJHQ=; b=acNQJPHDJbMebBjLxjSAuyZ0QE9kSepLwXN++mh4+RwTsOdoV+IPziFahjaSCtxRWG IEFcOdH+8ciYk7j+nXGqmD/3LWSXYZ4k//cIVlvWF8nj+mytpTelefSsKthzy9g+9T4N 7aHPrsia9YlStGXdhzI2/llNjQ7F0U0C8T+C2/dg8JuaSpv77IQ8JkgECmj449E5EWou 8Ut+V+hlsqw2RTW6DgjpbXET1nECp7QsaoDZ8vqOSKobzgVBeXUGnqniZTV116pX8io1 AfXMtsSS0cQQ4duTIL2832UoiZ/9mnukY2iFvmQQZkvAoPJqFa+bwlUTn2Xs9h8A2/x2 Y1uA== X-Received: by 10.14.225.72 with SMTP id y48mr55916984eep.45.1361272916612; Tue, 19 Feb 2013 03:21:56 -0800 (PST) Received: from [192.168.0.20] (ip-143-209.sn3.eutelia.it. [213.136.143.209]) by mx.google.com with ESMTPS id u44sm43503546eel.7.2013.02.19.03.21.53 (version=TLSv1 cipher=RC4-SHA bits=128/128); Tue, 19 Feb 2013 03:21:55 -0800 (PST) Message-ID: <1361272892.30467.1.camel@Abyss> From: Dario Faggioli To: Tom Date: Tue, 19 Feb 2013 12:21:32 +0100 In-Reply-To: References: X-Mailer: Evolution 3.6.3 (3.6.3-2.fc18) Mime-Version: 1.0 Cc: "xen-users@lists.xen.org" Subject: Re: [Xen-users] Issue with starting X with Intel gfx card (Ubuntu 12.10) X-BeenThere: xen-users@lists.xen.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="===============7257468857781042680==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============7257468857781042680== Content-Type: multipart/signed; micalg="pgp-sha1"; protocol="application/pgp-signature"; boundary="=-0qkBZUWAhKzpy5cDXJjC" --=-0qkBZUWAhKzpy5cDXJjC Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On dom, 2013-02-17 at 13:05 +0000, Tom wrote: > Hi, >=20 Hello, > I'm trying to get my X working with Xen on my Ubuntu 12.10 oob > installation, but keeps on hanging on boot; >=20 Hangs where? Kernel? Init scripts? "Just" Xorg? > lspci | grep VGA > 00:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200 > v2/3rd Gen Core processor Graphics Controller (rev 09) >=20 Yeah, fine, but until we don't understand _where_ in the boot process it hangs, it's going to be quite hard to blame specific components... Regards, Dario --=20 <> (Raistlin Majere) ----------------------------------------------------------------- Dario Faggioli, Ph.D, http://about.me/dario.faggioli Senior Software Engineer, Citrix Systems R&D Ltd., Cambridge (UK) --=-0qkBZUWAhKzpy5cDXJjC 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.13 (GNU/Linux) iEYEABECAAYFAlEjYDwACgkQk4XaBE3IOsRm1gCeOV3Lo4R5/kBPcN7+m7HFhT0S LX4An3dxKAWlJcBQB4LYFmJW0C7deTNs =YdJ+ -----END PGP SIGNATURE----- --=-0qkBZUWAhKzpy5cDXJjC-- --===============7257468857781042680== 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 --===============7257468857781042680==-- From xen-users-bounces@lists.xen.org Tue Feb 19 11:36:55 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 19 Feb 2013 11:36: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 1U7lUA-0007sr-Qh; Tue, 19 Feb 2013 11:35:46 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U7lU9-0007sl-5b for xen-users@lists.xen.org; Tue, 19 Feb 2013 11:35:45 +0000 Received: from [85.158.138.51:50111] by server-12.bemta-3.messagelabs.com id 70/A6-05889-09363215; Tue, 19 Feb 2013 11:35:44 +0000 X-Env-Sender: sylvain.chevalier@gmail.com X-Msg-Ref: server-16.tower-174.messagelabs.com!1361273741!28081458!1 X-Originating-IP: [209.85.214.176] 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.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 26994 invoked from network); 19 Feb 2013 11:35:43 -0000 Received: from mail-ob0-f176.google.com (HELO mail-ob0-f176.google.com) (209.85.214.176) by server-16.tower-174.messagelabs.com with RC4-SHA encrypted SMTP; 19 Feb 2013 11:35:43 -0000 Received: by mail-ob0-f176.google.com with SMTP id v19so6479179obq.21 for ; Tue, 19 Feb 2013 03:34:42 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=hkqCg6WPPekXTCqnCVH8KGZy1WVAJrhiyyzFBU+Vyec=; b=voZnL2Q/EzcykSxAqJ+82VZRkUo8AOTGKtGIwI4ZcDfuV3QWtlQtbGzUci7LksgOGm 74q5lcDJFCJidfltz6qJpHpDPdVLbSPGSR77M2WqvPRdc7TLdaRUxyTMoMpvqMGQeI+A hazKz9JC9ak6H82jQsilcmW14SV8biRBH176CTorGNUD2JHK/ZGQnmveULh4hppHyQwE qHEqXe6Ex1eQuqpTyLAz1y1LYdrmEJeLWFt8oXiwJ7R5mlnJPKmPsRLtxzh8TSXTQxrK iTYLZz4L15dSrlKlTouJ6M0vzsI7v68tI0PMGP/vkmwD04+H9IbHYqOZQnUMHn58SkNh pSiQ== MIME-Version: 1.0 X-Received: by 10.60.3.193 with SMTP id e1mr7727427oee.39.1361273682040; Tue, 19 Feb 2013 03:34:42 -0800 (PST) Received: by 10.76.172.73 with HTTP; Tue, 19 Feb 2013 03:34:41 -0800 (PST) In-Reply-To: <1361182968.31407.125.camel@zakaz.uk.xensource.com> References: <1361182968.31407.125.camel@zakaz.uk.xensource.com> Date: Tue, 19 Feb 2013 19:34:41 +0800 Message-ID: From: Sylvain Chevalier To: Ian Campbell Cc: "xen-users@lists.xen.org" Subject: Re: [Xen-users] Can't boot dom0 after upgrading to non-modified 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-Type: multipart/mixed; boundary="===============0426406396366620160==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============0426406396366620160== Content-Type: multipart/alternative; boundary=e89a8ff2563e4298d104d6123a0f --e89a8ff2563e4298d104d6123a0f Content-Type: text/plain; charset=ISO-8859-1 Thanks Ian, I am embarrassed, it was indeed a missing driver that was dropped when migrating the .config. It now works well, it really makes things way more convenient to use the kernel directly from the distrib's main tree. On Mon, Feb 18, 2013 at 6:22 PM, Ian Campbell wrote: > On Sat, 2013-02-16 at 11:30 +0000, Sylvain Chevalier wrote: > > > > > This grub setting fails (kernel is gentoo-sources): > > root (hd0,1) > > kernel /boot/xen.gz dom0_mem=4096M dom0_max_vcpus=1 dom0_vcpus_pin > > module /boot/kernel-3.6.11-gentoo root=/dev/sda6 > > Does this kernel boot natively? Are you sure you have all the necessary > drivers etc? > > Given the lack of logs it is rather hard to give any more specific > advice. > > Ian. > > > --e89a8ff2563e4298d104d6123a0f Content-Type: text/html; charset=ISO-8859-1
Thanks Ian, I am embarrassed, it was indeed a missing driver that was dropped when migrating the .config. It now works well, it really makes things way more convenient to use the kernel directly from the distrib's main tree.


On Mon, Feb 18, 2013 at 6:22 PM, Ian Campbell <Ian.Campbell@citrix.com> wrote:
On Sat, 2013-02-16 at 11:30 +0000, Sylvain Chevalier wrote:

>
> This grub setting fails (kernel is gentoo-sources):
> root (hd0,1)
> kernel /boot/xen.gz dom0_mem=4096M dom0_max_vcpus=1 dom0_vcpus_pin
> module /boot/kernel-3.6.11-gentoo root=/dev/sda6

Does this kernel boot natively? Are you sure you have all the necessary
drivers etc?

Given the lack of logs it is rather hard to give any more specific
advice.

Ian.



--e89a8ff2563e4298d104d6123a0f-- --===============0426406396366620160== 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 --===============0426406396366620160==-- From xen-users-bounces@lists.xen.org Tue Feb 19 11:36:55 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 19 Feb 2013 11:36: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 1U7lUA-0007sr-Qh; Tue, 19 Feb 2013 11:35:46 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U7lU9-0007sl-5b for xen-users@lists.xen.org; Tue, 19 Feb 2013 11:35:45 +0000 Received: from [85.158.138.51:50111] by server-12.bemta-3.messagelabs.com id 70/A6-05889-09363215; Tue, 19 Feb 2013 11:35:44 +0000 X-Env-Sender: sylvain.chevalier@gmail.com X-Msg-Ref: server-16.tower-174.messagelabs.com!1361273741!28081458!1 X-Originating-IP: [209.85.214.176] 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.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 26994 invoked from network); 19 Feb 2013 11:35:43 -0000 Received: from mail-ob0-f176.google.com (HELO mail-ob0-f176.google.com) (209.85.214.176) by server-16.tower-174.messagelabs.com with RC4-SHA encrypted SMTP; 19 Feb 2013 11:35:43 -0000 Received: by mail-ob0-f176.google.com with SMTP id v19so6479179obq.21 for ; Tue, 19 Feb 2013 03:34:42 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=hkqCg6WPPekXTCqnCVH8KGZy1WVAJrhiyyzFBU+Vyec=; b=voZnL2Q/EzcykSxAqJ+82VZRkUo8AOTGKtGIwI4ZcDfuV3QWtlQtbGzUci7LksgOGm 74q5lcDJFCJidfltz6qJpHpDPdVLbSPGSR77M2WqvPRdc7TLdaRUxyTMoMpvqMGQeI+A hazKz9JC9ak6H82jQsilcmW14SV8biRBH176CTorGNUD2JHK/ZGQnmveULh4hppHyQwE qHEqXe6Ex1eQuqpTyLAz1y1LYdrmEJeLWFt8oXiwJ7R5mlnJPKmPsRLtxzh8TSXTQxrK iTYLZz4L15dSrlKlTouJ6M0vzsI7v68tI0PMGP/vkmwD04+H9IbHYqOZQnUMHn58SkNh pSiQ== MIME-Version: 1.0 X-Received: by 10.60.3.193 with SMTP id e1mr7727427oee.39.1361273682040; Tue, 19 Feb 2013 03:34:42 -0800 (PST) Received: by 10.76.172.73 with HTTP; Tue, 19 Feb 2013 03:34:41 -0800 (PST) In-Reply-To: <1361182968.31407.125.camel@zakaz.uk.xensource.com> References: <1361182968.31407.125.camel@zakaz.uk.xensource.com> Date: Tue, 19 Feb 2013 19:34:41 +0800 Message-ID: From: Sylvain Chevalier To: Ian Campbell Cc: "xen-users@lists.xen.org" Subject: Re: [Xen-users] Can't boot dom0 after upgrading to non-modified 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-Type: multipart/mixed; boundary="===============0426406396366620160==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============0426406396366620160== Content-Type: multipart/alternative; boundary=e89a8ff2563e4298d104d6123a0f --e89a8ff2563e4298d104d6123a0f Content-Type: text/plain; charset=ISO-8859-1 Thanks Ian, I am embarrassed, it was indeed a missing driver that was dropped when migrating the .config. It now works well, it really makes things way more convenient to use the kernel directly from the distrib's main tree. On Mon, Feb 18, 2013 at 6:22 PM, Ian Campbell wrote: > On Sat, 2013-02-16 at 11:30 +0000, Sylvain Chevalier wrote: > > > > > This grub setting fails (kernel is gentoo-sources): > > root (hd0,1) > > kernel /boot/xen.gz dom0_mem=4096M dom0_max_vcpus=1 dom0_vcpus_pin > > module /boot/kernel-3.6.11-gentoo root=/dev/sda6 > > Does this kernel boot natively? Are you sure you have all the necessary > drivers etc? > > Given the lack of logs it is rather hard to give any more specific > advice. > > Ian. > > > --e89a8ff2563e4298d104d6123a0f Content-Type: text/html; charset=ISO-8859-1
Thanks Ian, I am embarrassed, it was indeed a missing driver that was dropped when migrating the .config. It now works well, it really makes things way more convenient to use the kernel directly from the distrib's main tree.


On Mon, Feb 18, 2013 at 6:22 PM, Ian Campbell <Ian.Campbell@citrix.com> wrote:
On Sat, 2013-02-16 at 11:30 +0000, Sylvain Chevalier wrote:

>
> This grub setting fails (kernel is gentoo-sources):
> root (hd0,1)
> kernel /boot/xen.gz dom0_mem=4096M dom0_max_vcpus=1 dom0_vcpus_pin
> module /boot/kernel-3.6.11-gentoo root=/dev/sda6

Does this kernel boot natively? Are you sure you have all the necessary
drivers etc?

Given the lack of logs it is rather hard to give any more specific
advice.

Ian.



--e89a8ff2563e4298d104d6123a0f-- --===============0426406396366620160== 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 --===============0426406396366620160==-- From xen-users-bounces@lists.xen.org Tue Feb 19 11:40:48 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 19 Feb 2013 11:40: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 1U7lYD-00085G-OR; Tue, 19 Feb 2013 11:39:57 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U7lYB-000852-R4 for xen-users@lists.xen.org; Tue, 19 Feb 2013 11:39:56 +0000 Received: from [85.158.139.83:55182] by server-5.bemta-5.messagelabs.com id 1B/B6-11945-98463215; Tue, 19 Feb 2013 11:39:53 +0000 X-Env-Sender: eross@corp.locatrix.com X-Msg-Ref: server-4.tower-182.messagelabs.com!1361273990!25194145!1 X-Originating-IP: [209.85.210.170] 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.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 31080 invoked from network); 19 Feb 2013 11:39:51 -0000 Received: from mail-ia0-f170.google.com (HELO mail-ia0-f170.google.com) (209.85.210.170) by server-4.tower-182.messagelabs.com with RC4-SHA encrypted SMTP; 19 Feb 2013 11:39:51 -0000 Received: by mail-ia0-f170.google.com with SMTP id k20so6105032iak.29 for ; Tue, 19 Feb 2013 03:39:50 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=x-received:mime-version:in-reply-to:references:from:date:message-id :subject:to:cc:content-type:x-gm-message-state; bh=eLgcMbgokvWAK0UQDllA7myRfXaG395ZrB4f2Snq8ys=; b=jZ65EAGQ/cYcEWkXdYYcztBc2ffS/++sy6zrvwS8WhktBhwmqbMG4podprh1wRlcqR v7A1861XFnDhJUrtUOHveNwGk9HbmxCR/B8gxtsC8xpgE68/hn0ecl9DkuhkPp42mnIu 7w6XM2gaKX7pGPGNKM7WCAjpwmGl31lfcfhF07kWwUQ4IqwCn4qSC46WVBEI0SuHHbr5 cKqzab9HcG3KAQHmMSSydHfBY/dhh3CcnzMgWjQZaZXS69jQZJjnEAAEvRgkxf98K2ZT 72+so2NqeY9vFSbLK4uHc2s9C14F5VI+tl//mmtDoGZcyvmxdlZj7+A0p723dkocq9pr gaXA== X-Received: by 10.50.7.240 with SMTP id m16mr8016395iga.91.1361273990100; Tue, 19 Feb 2013 03:39:50 -0800 (PST) MIME-Version: 1.0 Received: by 10.64.44.197 with HTTP; Tue, 19 Feb 2013 03:39:29 -0800 (PST) In-Reply-To: References: From: Andrew Eross Date: Tue, 19 Feb 2013 08:39:29 -0300 Message-ID: To: rshriram@cs.ubc.ca X-Gm-Message-State: ALoCoQnIEQfL9xoUx1AT6jX70VWk4pvNAnlGBg9Iu/zh7cYStt/sFcUQmOEAUXprBjadH0MLrF4+ Cc: "xen-users@lists.xen.org" Subject: Re: [Xen-users] Remus dom0 network buffering X-BeenThere: xen-users@lists.xen.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="===============8023063087848522065==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============8023063087848522065== Content-Type: multipart/alternative; boundary=f46d0447976d9f375104d6124c66 --f46d0447976d9f375104d6124c66 Content-Type: text/plain; charset=ISO-8859-1 Hi all, To close off on this, Shriram's patch worked great, thank you. So Ubuntu 12.10's standard generic kernel is now working fine as a dom0 for Remus with Xen 4.1.4 (with the patch from this thread). I wrote up my full install instructions here: http://wiki.xen.org/wiki/Install_Xen_4.1.4_with_Remus_and_DRBD_on_Ubuntu_12.10 I also took a shot at a number of updates to: http://wiki.xen.org/wiki/Remus And added these pages: http://wiki.xen.org/wiki/Remus_PV_domU_requirements http://wiki.xen.org/wiki/Remus_dom0_requirements Feedback very welcome, a lot of that information was a bit old, so I did my best. Cheers, Andrew On Mon, Feb 18, 2013 at 8:26 PM, Shriram Rajagopalan wrote: > ah darn. Yes, the 3.5 kernel has sch_plug in it. Unfortunately, the > technique to initialize the sch_plug module is bit > different with the module thats already mainline. You ll have to patch > the qdisc.py python module. I ll submit the > patch to xen devel soon. > Mean while, can you try the patch below and see if it works ? > > Secondly, you said you were writing a blog about how you set it up. > One of the remus users created a wiki > remusha.wikidot.com, which has a whole tutorial on how to setup remus > with Debian Squeeze. I have been under fire > lately for a host of remus issues. It would be great if you could post > your experiences on the wiki too. > (http://remusha.wikidot.com/system:join) > > thanks > shriram > > --- > diff -r 6435f1edf24e tools/python/xen/remus/qdisc.py > --- a/tools/python/xen/remus/qdisc.py Tue Jul 17 19:23:30 2012 -0400 > +++ b/tools/python/xen/remus/qdisc.py Mon Feb 18 18:25:22 2013 -0500 > @@ -1,6 +1,9 @@ > import socket, struct > > import netlink > +import platform > + > +kernelversion = platform.platform(terse=True).split("-")[1].split(".") > > qdisc_kinds = {} > > @@ -150,9 +153,14 @@ > TC_PLUG_RELEASE = 1 > > class PlugQdisc(Qdisc): > - fmt = 'I' > > def __init__(self, qdict=None): > + if int(kernelversion[0]) >= 3 and int(kernelversion[1]) >= 4: > + self.fmt = 'iI' > + self.limit = 10000 > + else: > + self.fmt = 'I' > + > if not qdict: > qdict = {'kind': 'plug', > 'handle': TC_H_ROOT} > @@ -161,7 +169,10 @@ > self.action = 0 > > def pack(self): > - return struct.pack(self.fmt, self.action) > + if int(kernelversion[0]) >= 3 and int(kernelversion[1]) >= 4: > + return struct.pack(self.fmt, self.action, self.limit) > + else: > + return struct.pack(self.fmt, self.action) > > def parse(self, args): > if not args: > --f46d0447976d9f375104d6124c66 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Hi all,

To close off on this, Shriram's patch worked= great, thank you.

So Ubuntu 12.10's standard = generic kernel is now working fine as a dom0 for Remus with Xen 4.1.4 (with= the patch from this thread).

I wrote up my full install instructions here:
http://wiki.xen.org/wiki/Install_Xen_4.1.4_with_Remus_and_= DRBD_on_Ubuntu_12.10

I also took a shot at a number of updates to:
http://wiki.xen.org/wiki/Remus<= /a>


Feedba= ck very welcome, a lot of that information was a bit old, so I did my best.=

Cheers,
Andrew


<= div class=3D"gmail_quote">On Mon, Feb 18, 2013 at 8:26 PM, Shriram Rajagopa= lan <rshriram@cs.ubc.ca> wrote:
ah darn. Yes, the 3.5 kernel has sch_plug in= it. Unfortunately, the
technique to initialize the sch_plug module is bit
different with the module thats already mainline. You ll have to patch
the qdisc.py python module. I ll submit the
patch to xen devel soon.
Mean while, can you try the patch below and see if it works ?

Secondly, you said you were writing a blog about how you set it up.
One of the remus users created a wiki
remusha.wikidot.co= m, which has a whole tutorial on how to setup remus
with Debian Squeeze. I have been under fire
lately for a host of remus issues. It would be great if you could post
your experiences on the wiki too.
(http:= //remusha.wikidot.com/system:join)

thanks
shriram

---
diff -r 6435f1edf24e tools/python/xen/remus/qdisc.py
--- a/tools/python/xen/remus/qdisc.py =A0 Tue Jul 17 19:23:30 2012 -0400 +++ b/tools/python/xen/remus/qdisc.py =A0 Mon Feb 18 18:25:22 2013 -0500 @@ -1,6 +1,9 @@
=A0import socket, struct

=A0import netlink
+import platform
+
+kernelversion =3D platform.platform(terse=3DTrue).split("-")[1].= split(".")

=A0qdisc_kinds =3D {}

@@ -150,9 +153,14 @@
=A0TC_PLUG_RELEASE =3D 1

=A0class PlugQdisc(Qdisc):
- =A0 =A0fmt =3D 'I'

=A0 =A0 =A0def __init__(self, qdict=3DNone):
+ =A0 =A0 =A0 =A0if int(kernelversion[0]) >=3D 3 and int(kernelversion[1= ]) >=3D 4:
+ =A0 =A0 =A0 =A0 =A0 =A0self.fmt =3D 'iI'
+ =A0 =A0 =A0 =A0 =A0 =A0self.limit =3D 10000
+ =A0 =A0 =A0 =A0else:
+ =A0 =A0 =A0 =A0 =A0 =A0self.fmt =3D 'I'
+
=A0 =A0 =A0 =A0 =A0if not qdict:
=A0 =A0 =A0 =A0 =A0 =A0 =A0qdict =3D {'kind': 'plug',
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 'handle': TC_H_ROOT} @@ -161,7 +169,10 @@
=A0 =A0 =A0 =A0 =A0self.action =3D 0

=A0 =A0 =A0def pack(self):
- =A0 =A0 =A0 =A0return struct.pack(self.fmt, self.action)
+ =A0 =A0 =A0 =A0if int(kernelversion[0]) >=3D 3 and int(kernelversion[1= ]) >=3D 4:
+ =A0 =A0 =A0 =A0 =A0 =A0return struct.pack(self.fmt, self.action, self.lim= it)
+ =A0 =A0 =A0 =A0else:
+ =A0 =A0 =A0 =A0 =A0 =A0return struct.pack(self.fmt, self.action)

=A0 =A0 =A0def parse(self, args):
=A0 =A0 =A0 =A0 =A0if not args:

--f46d0447976d9f375104d6124c66-- --===============8023063087848522065== 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 --===============8023063087848522065==-- From xen-users-bounces@lists.xen.org Tue Feb 19 11:40:48 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 19 Feb 2013 11:40: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 1U7lYD-00085G-OR; Tue, 19 Feb 2013 11:39:57 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U7lYB-000852-R4 for xen-users@lists.xen.org; Tue, 19 Feb 2013 11:39:56 +0000 Received: from [85.158.139.83:55182] by server-5.bemta-5.messagelabs.com id 1B/B6-11945-98463215; Tue, 19 Feb 2013 11:39:53 +0000 X-Env-Sender: eross@corp.locatrix.com X-Msg-Ref: server-4.tower-182.messagelabs.com!1361273990!25194145!1 X-Originating-IP: [209.85.210.170] 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.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 31080 invoked from network); 19 Feb 2013 11:39:51 -0000 Received: from mail-ia0-f170.google.com (HELO mail-ia0-f170.google.com) (209.85.210.170) by server-4.tower-182.messagelabs.com with RC4-SHA encrypted SMTP; 19 Feb 2013 11:39:51 -0000 Received: by mail-ia0-f170.google.com with SMTP id k20so6105032iak.29 for ; Tue, 19 Feb 2013 03:39:50 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=x-received:mime-version:in-reply-to:references:from:date:message-id :subject:to:cc:content-type:x-gm-message-state; bh=eLgcMbgokvWAK0UQDllA7myRfXaG395ZrB4f2Snq8ys=; b=jZ65EAGQ/cYcEWkXdYYcztBc2ffS/++sy6zrvwS8WhktBhwmqbMG4podprh1wRlcqR v7A1861XFnDhJUrtUOHveNwGk9HbmxCR/B8gxtsC8xpgE68/hn0ecl9DkuhkPp42mnIu 7w6XM2gaKX7pGPGNKM7WCAjpwmGl31lfcfhF07kWwUQ4IqwCn4qSC46WVBEI0SuHHbr5 cKqzab9HcG3KAQHmMSSydHfBY/dhh3CcnzMgWjQZaZXS69jQZJjnEAAEvRgkxf98K2ZT 72+so2NqeY9vFSbLK4uHc2s9C14F5VI+tl//mmtDoGZcyvmxdlZj7+A0p723dkocq9pr gaXA== X-Received: by 10.50.7.240 with SMTP id m16mr8016395iga.91.1361273990100; Tue, 19 Feb 2013 03:39:50 -0800 (PST) MIME-Version: 1.0 Received: by 10.64.44.197 with HTTP; Tue, 19 Feb 2013 03:39:29 -0800 (PST) In-Reply-To: References: From: Andrew Eross Date: Tue, 19 Feb 2013 08:39:29 -0300 Message-ID: To: rshriram@cs.ubc.ca X-Gm-Message-State: ALoCoQnIEQfL9xoUx1AT6jX70VWk4pvNAnlGBg9Iu/zh7cYStt/sFcUQmOEAUXprBjadH0MLrF4+ Cc: "xen-users@lists.xen.org" Subject: Re: [Xen-users] Remus dom0 network buffering X-BeenThere: xen-users@lists.xen.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="===============8023063087848522065==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============8023063087848522065== Content-Type: multipart/alternative; boundary=f46d0447976d9f375104d6124c66 --f46d0447976d9f375104d6124c66 Content-Type: text/plain; charset=ISO-8859-1 Hi all, To close off on this, Shriram's patch worked great, thank you. So Ubuntu 12.10's standard generic kernel is now working fine as a dom0 for Remus with Xen 4.1.4 (with the patch from this thread). I wrote up my full install instructions here: http://wiki.xen.org/wiki/Install_Xen_4.1.4_with_Remus_and_DRBD_on_Ubuntu_12.10 I also took a shot at a number of updates to: http://wiki.xen.org/wiki/Remus And added these pages: http://wiki.xen.org/wiki/Remus_PV_domU_requirements http://wiki.xen.org/wiki/Remus_dom0_requirements Feedback very welcome, a lot of that information was a bit old, so I did my best. Cheers, Andrew On Mon, Feb 18, 2013 at 8:26 PM, Shriram Rajagopalan wrote: > ah darn. Yes, the 3.5 kernel has sch_plug in it. Unfortunately, the > technique to initialize the sch_plug module is bit > different with the module thats already mainline. You ll have to patch > the qdisc.py python module. I ll submit the > patch to xen devel soon. > Mean while, can you try the patch below and see if it works ? > > Secondly, you said you were writing a blog about how you set it up. > One of the remus users created a wiki > remusha.wikidot.com, which has a whole tutorial on how to setup remus > with Debian Squeeze. I have been under fire > lately for a host of remus issues. It would be great if you could post > your experiences on the wiki too. > (http://remusha.wikidot.com/system:join) > > thanks > shriram > > --- > diff -r 6435f1edf24e tools/python/xen/remus/qdisc.py > --- a/tools/python/xen/remus/qdisc.py Tue Jul 17 19:23:30 2012 -0400 > +++ b/tools/python/xen/remus/qdisc.py Mon Feb 18 18:25:22 2013 -0500 > @@ -1,6 +1,9 @@ > import socket, struct > > import netlink > +import platform > + > +kernelversion = platform.platform(terse=True).split("-")[1].split(".") > > qdisc_kinds = {} > > @@ -150,9 +153,14 @@ > TC_PLUG_RELEASE = 1 > > class PlugQdisc(Qdisc): > - fmt = 'I' > > def __init__(self, qdict=None): > + if int(kernelversion[0]) >= 3 and int(kernelversion[1]) >= 4: > + self.fmt = 'iI' > + self.limit = 10000 > + else: > + self.fmt = 'I' > + > if not qdict: > qdict = {'kind': 'plug', > 'handle': TC_H_ROOT} > @@ -161,7 +169,10 @@ > self.action = 0 > > def pack(self): > - return struct.pack(self.fmt, self.action) > + if int(kernelversion[0]) >= 3 and int(kernelversion[1]) >= 4: > + return struct.pack(self.fmt, self.action, self.limit) > + else: > + return struct.pack(self.fmt, self.action) > > def parse(self, args): > if not args: > --f46d0447976d9f375104d6124c66 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Hi all,

To close off on this, Shriram's patch worked= great, thank you.

So Ubuntu 12.10's standard = generic kernel is now working fine as a dom0 for Remus with Xen 4.1.4 (with= the patch from this thread).

I wrote up my full install instructions here:
http://wiki.xen.org/wiki/Install_Xen_4.1.4_with_Remus_and_= DRBD_on_Ubuntu_12.10

I also took a shot at a number of updates to:
http://wiki.xen.org/wiki/Remus<= /a>


Feedba= ck very welcome, a lot of that information was a bit old, so I did my best.=

Cheers,
Andrew


<= div class=3D"gmail_quote">On Mon, Feb 18, 2013 at 8:26 PM, Shriram Rajagopa= lan <rshriram@cs.ubc.ca> wrote:
ah darn. Yes, the 3.5 kernel has sch_plug in= it. Unfortunately, the
technique to initialize the sch_plug module is bit
different with the module thats already mainline. You ll have to patch
the qdisc.py python module. I ll submit the
patch to xen devel soon.
Mean while, can you try the patch below and see if it works ?

Secondly, you said you were writing a blog about how you set it up.
One of the remus users created a wiki
remusha.wikidot.co= m, which has a whole tutorial on how to setup remus
with Debian Squeeze. I have been under fire
lately for a host of remus issues. It would be great if you could post
your experiences on the wiki too.
(http:= //remusha.wikidot.com/system:join)

thanks
shriram

---
diff -r 6435f1edf24e tools/python/xen/remus/qdisc.py
--- a/tools/python/xen/remus/qdisc.py =A0 Tue Jul 17 19:23:30 2012 -0400 +++ b/tools/python/xen/remus/qdisc.py =A0 Mon Feb 18 18:25:22 2013 -0500 @@ -1,6 +1,9 @@
=A0import socket, struct

=A0import netlink
+import platform
+
+kernelversion =3D platform.platform(terse=3DTrue).split("-")[1].= split(".")

=A0qdisc_kinds =3D {}

@@ -150,9 +153,14 @@
=A0TC_PLUG_RELEASE =3D 1

=A0class PlugQdisc(Qdisc):
- =A0 =A0fmt =3D 'I'

=A0 =A0 =A0def __init__(self, qdict=3DNone):
+ =A0 =A0 =A0 =A0if int(kernelversion[0]) >=3D 3 and int(kernelversion[1= ]) >=3D 4:
+ =A0 =A0 =A0 =A0 =A0 =A0self.fmt =3D 'iI'
+ =A0 =A0 =A0 =A0 =A0 =A0self.limit =3D 10000
+ =A0 =A0 =A0 =A0else:
+ =A0 =A0 =A0 =A0 =A0 =A0self.fmt =3D 'I'
+
=A0 =A0 =A0 =A0 =A0if not qdict:
=A0 =A0 =A0 =A0 =A0 =A0 =A0qdict =3D {'kind': 'plug',
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 'handle': TC_H_ROOT} @@ -161,7 +169,10 @@
=A0 =A0 =A0 =A0 =A0self.action =3D 0

=A0 =A0 =A0def pack(self):
- =A0 =A0 =A0 =A0return struct.pack(self.fmt, self.action)
+ =A0 =A0 =A0 =A0if int(kernelversion[0]) >=3D 3 and int(kernelversion[1= ]) >=3D 4:
+ =A0 =A0 =A0 =A0 =A0 =A0return struct.pack(self.fmt, self.action, self.lim= it)
+ =A0 =A0 =A0 =A0else:
+ =A0 =A0 =A0 =A0 =A0 =A0return struct.pack(self.fmt, self.action)

=A0 =A0 =A0def parse(self, args):
=A0 =A0 =A0 =A0 =A0if not args:

--f46d0447976d9f375104d6124c66-- --===============8023063087848522065== 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 --===============8023063087848522065==-- From xen-users-bounces@lists.xen.org Tue Feb 19 12:25:12 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 19 Feb 2013 12:25: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 1U7mEs-00014p-Cm; Tue, 19 Feb 2013 12:24:02 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U7mEq-00014k-Nz for xen-users@lists.xen.org; Tue, 19 Feb 2013 12:24:01 +0000 Received: from [85.158.143.99:45151] by server-1.bemta-4.messagelabs.com id 2E/B8-08839-0EE63215; Tue, 19 Feb 2013 12:24:00 +0000 X-Env-Sender: eross@corp.locatrix.com X-Msg-Ref: server-4.tower-216.messagelabs.com!1361276636!22881351!1 X-Originating-IP: [209.85.223.171] 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.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 28243 invoked from network); 19 Feb 2013 12:23:57 -0000 Received: from mail-ie0-f171.google.com (HELO mail-ie0-f171.google.com) (209.85.223.171) by server-4.tower-216.messagelabs.com with RC4-SHA encrypted SMTP; 19 Feb 2013 12:23:57 -0000 Received: by mail-ie0-f171.google.com with SMTP id 10so8316336ied.2 for ; Tue, 19 Feb 2013 04:23:56 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=x-received:mime-version:in-reply-to:references:from:date:message-id :subject:to:cc:content-type:x-gm-message-state; bh=NwsPfStoT5NiQky8Ct/EG2p2z3dzEmR9ZKV0Z14auPE=; b=aYhEu6JodDEacmFEskvMsuypJT3edSnirPw87Jkh37BpyslDirNk6jQv+fWW63Cnk6 Ta/sBKtQxYfqz9OiQlsjSC7f9JiNKrDreC87Eh2g3XMUghTRBPCEkpZjIUjmU7sfcQ6e 8uCRAsnjAs4TdLbRa/iygezKFZZCBfHnqMKQKRuu2lpwkelFVFu159LKWuIdX2Lf3sFz REbQBBEWgnAJqxyG33TfWVNR6Yh5xVion+GjH/BpgE2sqHmEcxOMG1ZHq+q4vtHpqUVC lkvPcsUH6X28gpzkeS5sS4tW0lXkAkTrR8fvQlUW5VIUMZqLy/s56adLJoZHiFmSX0wI YteA== X-Received: by 10.50.186.134 with SMTP id fk6mr9309297igc.9.1361276636216; Tue, 19 Feb 2013 04:23:56 -0800 (PST) MIME-Version: 1.0 Received: by 10.64.44.197 with HTTP; Tue, 19 Feb 2013 04:23:36 -0800 (PST) In-Reply-To: <51229E41.2090103@yahoo.co.uk> References: <51229E41.2090103@yahoo.co.uk> From: Andrew Eross Date: Tue, 19 Feb 2013 09:23:36 -0300 Message-ID: To: Ian X-Gm-Message-State: ALoCoQlaghmVKYuF7FSyUnTnYf651a7dpnrJhPIKv60mArwIakKXJ0sg4b2kvgg1h0/hOgWu58F2 Cc: xen-users@lists.xen.org Subject: Re: [Xen-users] Xen 4.2.1 unable to get domain type for domid X-BeenThere: xen-users@lists.xen.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="===============2230583862173465868==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============2230583862173465868== Content-Type: multipart/alternative; boundary=14dae9340f2d57be6104d612ea53 --14dae9340f2d57be6104d612ea53 Content-Type: text/plain; charset=ISO-8859-1 Hi Ian, Thanks for the feedback - Strangely myself I've given it another shot, and I've had better luck now using the xen-create-image tool instead of trying to directly launch the netboot installer myself. Using the exact same setup as I had before, I manually installed the Ubuntu packaged xen-tools and created an image with xen-create-image, like this: apt-get install libtext-template-perl libconfig-inifiles-perl libfile-slurp-perl liblist-moreutils-perl wget http://mirror.pnl.gov/ubuntu/pool/universe/x/xen-tools/xen-tools_4.3.1-1_all.deb dpkg -i xen-tools_4.3.1-1_all.deb xen-create-image --hostname=ubuntu \ --memory=512mb \ --vcpus=2 \ --lvm=center \ --dhcp \ --pygrub \ --dist=precise I'm still a little wary that perhaps there's a bug in xl since the netboot image should've worked I think, but happy that this method does work. Cheers, Andrew On Mon, Feb 18, 2013 at 6:33 PM, Ian wrote: > On 18/02/13 20:17, Andrew Eross wrote: > >> Hi guys, >> >> I eventually gave up and went back to Xen 4.1.4, which works perfectly >> fine using the exact same install method and Ubuntu domU configuration, but >> just with xm. >> >> I wrote up how I did the Xen 4.2.1 install here for reference - >> http://locatrix.com/building-**and-installing-xen-4-2-1-from-** >> source-on-ubuntu-12-10/ >> >> And the Xen 4.1.4 install here - >> http://locatrix.com/building-**and-install-xen-4-1-4-from-** >> source-on-ubuntu-12-10/ >> >> I hope maybe some others could give it a try and see if they also are >> unable to install Ubuntu domUs with xl on 4.2.1 like I'd been trying to. >> >> Cheers, >> Andrew >> >> > I have 12.04 DomU's running under 12.04 Dom0 on self compiled 4.2.1, using > xl toolstack > > The only issue I have had is that 12.04 DomU ends up with a non-PAE > kernel, which needs to be fixed after the install. 12.10 DomU's don't > appear to suffer this. No idea what the difference is between our set-ups, > although I just use LVMs and always specify a MAC address. > > ______________________________**_________________ > Xen-users mailing list > Xen-users@lists.xen.org > http://lists.xen.org/xen-users > --14dae9340f2d57be6104d612ea53 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Hi Ian,

Thanks for the feedback -

Strangely myself I've given it another shot, and I've had better= luck now using the xen-create-image tool instead of trying to directly lau= nch the netboot installer myself.

Using the exact same setup as I had before, I manually = installed the Ubuntu packaged xen-tools and created an image with xen-creat= e-image, like this:

apt-get install libtext-t= emplate-perl libconfig-inifiles-perl libfile-slurp-perl liblist-moreutils-p= erl
dpkg -i xen-tools_4.3.1-1_a= ll.deb

xen-create-image --hostname=3Dubuntu \
=A0 --= memory=3D512mb \
=A0 --vcpus=3D2 \
=A0 --lvm=3Dcenter \=
=A0 --dhcp \
=A0 --pygrub \
=A0 --dist=3Dpre= cise

I'm still a little wary that perhaps there's a bug i= n xl since the netboot image should've worked I think, but happy that t= his method does work.

Cheers,
Andrew

On Mon, Feb 18, 2013 at 6:33 PM, Ian <murrayie@yahoo.co.uk> wrote:
On 18/02/13 20:17, Andrew Eross wrote:
Hi guys,

I eventually gave up and went back to Xen 4.1.4, which works perfectly fine= using the exact same install method and Ubuntu domU configuration, but jus= t with xm.

I wrote up how I did the Xen 4.2.1 install here for reference -
http://locatrix.com/building-a= nd-installing-xen-4-2-1-from-source-on-ubuntu-12-10/

And the Xen 4.1.4 install here -
http://locatrix.com/building-and-= install-xen-4-1-4-from-source-on-ubuntu-12-10/

I hope maybe some others could give it a try and see if they also are unabl= e to install Ubuntu domUs with xl on 4.2.1 like I'd been trying to.

Cheers,
Andrew


I have 12.04 DomU's running under 12.04 Dom0 on self compiled 4.2.1, us= ing xl toolstack

The only issue I have had is that 12.04 DomU ends up with a non-PAE kernel,= which needs to be fixed after the install. 12.10 DomU's don't appe= ar to suffer this. No idea what the difference is between our set-ups, alth= ough I just use LVMs and always specify a MAC address.

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

--14dae9340f2d57be6104d612ea53-- --===============2230583862173465868== 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 --===============2230583862173465868==-- From xen-users-bounces@lists.xen.org Tue Feb 19 12:25:12 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 19 Feb 2013 12:25: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 1U7mEs-00014p-Cm; Tue, 19 Feb 2013 12:24:02 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U7mEq-00014k-Nz for xen-users@lists.xen.org; Tue, 19 Feb 2013 12:24:01 +0000 Received: from [85.158.143.99:45151] by server-1.bemta-4.messagelabs.com id 2E/B8-08839-0EE63215; Tue, 19 Feb 2013 12:24:00 +0000 X-Env-Sender: eross@corp.locatrix.com X-Msg-Ref: server-4.tower-216.messagelabs.com!1361276636!22881351!1 X-Originating-IP: [209.85.223.171] 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.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 28243 invoked from network); 19 Feb 2013 12:23:57 -0000 Received: from mail-ie0-f171.google.com (HELO mail-ie0-f171.google.com) (209.85.223.171) by server-4.tower-216.messagelabs.com with RC4-SHA encrypted SMTP; 19 Feb 2013 12:23:57 -0000 Received: by mail-ie0-f171.google.com with SMTP id 10so8316336ied.2 for ; Tue, 19 Feb 2013 04:23:56 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=x-received:mime-version:in-reply-to:references:from:date:message-id :subject:to:cc:content-type:x-gm-message-state; bh=NwsPfStoT5NiQky8Ct/EG2p2z3dzEmR9ZKV0Z14auPE=; b=aYhEu6JodDEacmFEskvMsuypJT3edSnirPw87Jkh37BpyslDirNk6jQv+fWW63Cnk6 Ta/sBKtQxYfqz9OiQlsjSC7f9JiNKrDreC87Eh2g3XMUghTRBPCEkpZjIUjmU7sfcQ6e 8uCRAsnjAs4TdLbRa/iygezKFZZCBfHnqMKQKRuu2lpwkelFVFu159LKWuIdX2Lf3sFz REbQBBEWgnAJqxyG33TfWVNR6Yh5xVion+GjH/BpgE2sqHmEcxOMG1ZHq+q4vtHpqUVC lkvPcsUH6X28gpzkeS5sS4tW0lXkAkTrR8fvQlUW5VIUMZqLy/s56adLJoZHiFmSX0wI YteA== X-Received: by 10.50.186.134 with SMTP id fk6mr9309297igc.9.1361276636216; Tue, 19 Feb 2013 04:23:56 -0800 (PST) MIME-Version: 1.0 Received: by 10.64.44.197 with HTTP; Tue, 19 Feb 2013 04:23:36 -0800 (PST) In-Reply-To: <51229E41.2090103@yahoo.co.uk> References: <51229E41.2090103@yahoo.co.uk> From: Andrew Eross Date: Tue, 19 Feb 2013 09:23:36 -0300 Message-ID: To: Ian X-Gm-Message-State: ALoCoQlaghmVKYuF7FSyUnTnYf651a7dpnrJhPIKv60mArwIakKXJ0sg4b2kvgg1h0/hOgWu58F2 Cc: xen-users@lists.xen.org Subject: Re: [Xen-users] Xen 4.2.1 unable to get domain type for domid X-BeenThere: xen-users@lists.xen.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="===============2230583862173465868==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============2230583862173465868== Content-Type: multipart/alternative; boundary=14dae9340f2d57be6104d612ea53 --14dae9340f2d57be6104d612ea53 Content-Type: text/plain; charset=ISO-8859-1 Hi Ian, Thanks for the feedback - Strangely myself I've given it another shot, and I've had better luck now using the xen-create-image tool instead of trying to directly launch the netboot installer myself. Using the exact same setup as I had before, I manually installed the Ubuntu packaged xen-tools and created an image with xen-create-image, like this: apt-get install libtext-template-perl libconfig-inifiles-perl libfile-slurp-perl liblist-moreutils-perl wget http://mirror.pnl.gov/ubuntu/pool/universe/x/xen-tools/xen-tools_4.3.1-1_all.deb dpkg -i xen-tools_4.3.1-1_all.deb xen-create-image --hostname=ubuntu \ --memory=512mb \ --vcpus=2 \ --lvm=center \ --dhcp \ --pygrub \ --dist=precise I'm still a little wary that perhaps there's a bug in xl since the netboot image should've worked I think, but happy that this method does work. Cheers, Andrew On Mon, Feb 18, 2013 at 6:33 PM, Ian wrote: > On 18/02/13 20:17, Andrew Eross wrote: > >> Hi guys, >> >> I eventually gave up and went back to Xen 4.1.4, which works perfectly >> fine using the exact same install method and Ubuntu domU configuration, but >> just with xm. >> >> I wrote up how I did the Xen 4.2.1 install here for reference - >> http://locatrix.com/building-**and-installing-xen-4-2-1-from-** >> source-on-ubuntu-12-10/ >> >> And the Xen 4.1.4 install here - >> http://locatrix.com/building-**and-install-xen-4-1-4-from-** >> source-on-ubuntu-12-10/ >> >> I hope maybe some others could give it a try and see if they also are >> unable to install Ubuntu domUs with xl on 4.2.1 like I'd been trying to. >> >> Cheers, >> Andrew >> >> > I have 12.04 DomU's running under 12.04 Dom0 on self compiled 4.2.1, using > xl toolstack > > The only issue I have had is that 12.04 DomU ends up with a non-PAE > kernel, which needs to be fixed after the install. 12.10 DomU's don't > appear to suffer this. No idea what the difference is between our set-ups, > although I just use LVMs and always specify a MAC address. > > ______________________________**_________________ > Xen-users mailing list > Xen-users@lists.xen.org > http://lists.xen.org/xen-users > --14dae9340f2d57be6104d612ea53 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Hi Ian,

Thanks for the feedback -

Strangely myself I've given it another shot, and I've had better= luck now using the xen-create-image tool instead of trying to directly lau= nch the netboot installer myself.

Using the exact same setup as I had before, I manually = installed the Ubuntu packaged xen-tools and created an image with xen-creat= e-image, like this:

apt-get install libtext-t= emplate-perl libconfig-inifiles-perl libfile-slurp-perl liblist-moreutils-p= erl
dpkg -i xen-tools_4.3.1-1_a= ll.deb

xen-create-image --hostname=3Dubuntu \
=A0 --= memory=3D512mb \
=A0 --vcpus=3D2 \
=A0 --lvm=3Dcenter \=
=A0 --dhcp \
=A0 --pygrub \
=A0 --dist=3Dpre= cise

I'm still a little wary that perhaps there's a bug i= n xl since the netboot image should've worked I think, but happy that t= his method does work.

Cheers,
Andrew

On Mon, Feb 18, 2013 at 6:33 PM, Ian <murrayie@yahoo.co.uk> wrote:
On 18/02/13 20:17, Andrew Eross wrote:
Hi guys,

I eventually gave up and went back to Xen 4.1.4, which works perfectly fine= using the exact same install method and Ubuntu domU configuration, but jus= t with xm.

I wrote up how I did the Xen 4.2.1 install here for reference -
http://locatrix.com/building-a= nd-installing-xen-4-2-1-from-source-on-ubuntu-12-10/

And the Xen 4.1.4 install here -
http://locatrix.com/building-and-= install-xen-4-1-4-from-source-on-ubuntu-12-10/

I hope maybe some others could give it a try and see if they also are unabl= e to install Ubuntu domUs with xl on 4.2.1 like I'd been trying to.

Cheers,
Andrew


I have 12.04 DomU's running under 12.04 Dom0 on self compiled 4.2.1, us= ing xl toolstack

The only issue I have had is that 12.04 DomU ends up with a non-PAE kernel,= which needs to be fixed after the install. 12.10 DomU's don't appe= ar to suffer this. No idea what the difference is between our set-ups, alth= ough I just use LVMs and always specify a MAC address.

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

--14dae9340f2d57be6104d612ea53-- --===============2230583862173465868== 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 --===============2230583862173465868==-- From xen-users-bounces@lists.xen.org Tue Feb 19 13:42:52 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 19 Feb 2013 13:42: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 1U7nRy-0004eh-2R; Tue, 19 Feb 2013 13:41:38 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U7nRw-0004eF-Tr for xen-users@lists.xen.org; Tue, 19 Feb 2013 13:41:37 +0000 Received: from [85.158.138.51:41002] by server-10.bemta-3.messagelabs.com id CB/B8-10609-01183215; Tue, 19 Feb 2013 13:41:36 +0000 X-Env-Sender: murrayie@yahoo.co.uk X-Msg-Ref: server-10.tower-174.messagelabs.com!1361281295!24151560!1 X-Originating-IP: [77.238.189.60] X-SpamReason: No, hits=0.0 required=7.0 tests=ML_RADAR_SPEW_LINKS_12, ML_RADAR_SPEW_LINKS_14,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 23728 invoked from network); 19 Feb 2013 13:41:35 -0000 Received: from nm3.bullet.mail.ird.yahoo.com (HELO nm3.bullet.mail.ird.yahoo.com) (77.238.189.60) by server-10.tower-174.messagelabs.com with SMTP; 19 Feb 2013 13:41:35 -0000 Received: from [212.82.105.245] by nm3.bullet.mail.ird.yahoo.com with NNFMP; 19 Feb 2013 13:41:35 -0000 Received: from [212.82.109.129] by tm17.bullet.mail.ird.yahoo.com with NNFMP; 19 Feb 2013 13:41:35 -0000 Received: from [127.0.0.1] by omp1036.mail.ird.yahoo.com with NNFMP; 19 Feb 2013 13:41:35 -0000 X-Yahoo-Newman-Property: ymail-3 X-Yahoo-Newman-Id: 208634.92170.bm@omp1036.mail.ird.yahoo.com Received: (qmail 12398 invoked by uid 60001); 19 Feb 2013 13:41:35 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.co.uk; s=s1024; t=1361281295; bh=3cWsd2ZqgBoReJLX0FFU14oBN0XnC7paLHyGtsGhhlE=; h=X-YMail-OSG:Received:X-Rocket-MIMEInfo:X-Mailer:References:Message-ID:Date:From:Reply-To:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=pCqAPJna1eOXhGAaG7bwFwbKftLKrEbpcTU3/w+Q7e+XZHCZwe12sdW17avCDtrMew5gSkcJ6bxoBI2X1apU7KeZESqje36g5GlbSyfYoBnTo04+dfJ9l09/3OEP3bUIm/HQHdqCh/3Xal75qDnU6X77haw4PW64nx55XBCw/HU= DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.co.uk; h=X-YMail-OSG:Received:X-Rocket-MIMEInfo:X-Mailer:References:Message-ID:Date:From:Reply-To:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=6GaZd4eGFDvvBSjZxfoOzGuaTUw4QZ1oB3gxRZun+w9fIV/6o9431n4I0tJXPBMb4WG+mElHaPjloX0F69D+/TJbdeyIbU4U6RC1dj1NY7v7i9nOXOsByiLxseGivD8GcRIOylKsl+6FGfj7XMJhOrW1/aakDJ8ZiOloDt7tUt8=; X-YMail-OSG: gogXdukVM1lRy2Rf1ioBfFwLGuB_HOAPC2_f_0o.Iz7FJUm Ql5au4U6KEbPAGbsCUlpM2hNg08A3ppsra5S9dumvw5ltt4FjmkObEL2TNvC g20gCth5EE4ZLRImbGCFFAVeWTe3d1wG.fXo04TOAj0hemjT9COcyc2Z49dS sInh1Xx7NJ3lZ7cJrcW_NE9w2.i9JyJXgA2E_DFag45tmHBLThOJvCxBI9sz 1XH80.TWLBtUOkT8vDcjIWcrSlCX_6lkO.OTUoTTjqyWgE11n5Ywcm6ykvKa 0ux0WQsBQc3dlLbUsJBq_NtPeIJ_bCieiRhs3NP.nUqMq4XwJkPGEijIlDgj YDR0R5aSl6Fq1qxdJjvQiFHWG9wH4uY_5SSce61K9jHJClMEGHgEW9_JHLQI yBtQkM03zKWAidssYH2x0K2kQDR7m4G.HOwT3nN0p7Zu08gkNg74dAG.hyuT OZh0Y1EWKVf2j15wc5dVIaPO3syYviHQcbfkKhcfLlfEPiYdiCOv4pXFC Received: from [195.212.29.67] by web171304.mail.ir2.yahoo.com via HTTP; Tue, 19 Feb 2013 13:41:34 GMT X-Rocket-MIMEInfo: 001.001, Cgo.SGkgSWFuLAo.Cj4KPlRoYW5rcyBmb3IgdGhlIGZlZWRiYWNrIC0KCgpObyBwcm9ibGVtLgoKPgo.Cj5JJ20gc3RpbGwgYSBsaXR0bGUgd2FyeSB0aGF0IHBlcmhhcHMgdGhlcmUncyBhIGJ1ZyBpbiB4bCBzaW5jZSB0aGUgbmV0Ym9vdCBpbWFnZSBzaG91bGQndmUgd29ya2VkIEkgdGhpbmssIGJ1dCBoYXBweSB0aGF0IHRoaXMgbWV0aG9kIGRvZXMgd29yay4KPgo.CgoKSSd2ZSBqdXN0IHRyaWVkIGl0IGFnYWluIHdpdGggMTIuMDQuMiB4ZW4gYm9vdCBpbWFnZXMgYW5kIGFsbCB3ZW50IHdlbGwuIEhlcmUBMAEBAQE- X-Mailer: YahooMailWebService/0.8.133.508 References: <51229E41.2090103@yahoo.co.uk> Message-ID: <1361281294.8796.YahooMailNeo@web171304.mail.ir2.yahoo.com> Date: Tue, 19 Feb 2013 13:41:34 +0000 (GMT) From: Ian Murray To: Andrew Eross In-Reply-To: MIME-Version: 1.0 Cc: "xen-users@lists.xen.org" Subject: Re: [Xen-users] Xen 4.2.1 unable to get domain type for domid X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: Ian Murray 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 Ian, > > >Thanks for the feedback - No problem. > > >I'm still a little wary that perhaps there's a bug in xl since the netboot= image should've worked I think, but happy that this method does work. > > I've just tried it again with 12.04.2 xen boot images and all went well. He= re is my config file... name=A0=A0=A0=A0=A0 =3D "ubuntu-calendar-test" memory=A0=A0=A0 =3D 1024 disk=A0=A0=A0=A0=A0 =3D ['phy:/dev/VG1/ubuntu-calendar-test,xvda,w' ] vif =3D [ 'mac=3D00:16:31:55:1c:82' ] kernel=A0=A0=A0 =3D "/root/xen/ubuntu1204/vmlinuz" ramdisk=A0=A0 =3D "/root/xen/ubuntu1204/initrd.gz" vcpus=A0=A0=A0=A0 =3D 2 on_reboot =3D 'destroy' on_crash=A0 =3D 'destroy' Are you sure there is no problem with your images? Here is are md5 hashes f= or the two files I used (12.04.2, 32bit as far as I remember)... f1f36dbfe47ebda085f41394dd079d09=A0 initrd.gz 8525c3e8d6131ae462ba85b935a70bae=A0 vmlinuz _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Tue Feb 19 13:42:52 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 19 Feb 2013 13:42: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 1U7nRy-0004eh-2R; Tue, 19 Feb 2013 13:41:38 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U7nRw-0004eF-Tr for xen-users@lists.xen.org; Tue, 19 Feb 2013 13:41:37 +0000 Received: from [85.158.138.51:41002] by server-10.bemta-3.messagelabs.com id CB/B8-10609-01183215; Tue, 19 Feb 2013 13:41:36 +0000 X-Env-Sender: murrayie@yahoo.co.uk X-Msg-Ref: server-10.tower-174.messagelabs.com!1361281295!24151560!1 X-Originating-IP: [77.238.189.60] X-SpamReason: No, hits=0.0 required=7.0 tests=ML_RADAR_SPEW_LINKS_12, ML_RADAR_SPEW_LINKS_14,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 23728 invoked from network); 19 Feb 2013 13:41:35 -0000 Received: from nm3.bullet.mail.ird.yahoo.com (HELO nm3.bullet.mail.ird.yahoo.com) (77.238.189.60) by server-10.tower-174.messagelabs.com with SMTP; 19 Feb 2013 13:41:35 -0000 Received: from [212.82.105.245] by nm3.bullet.mail.ird.yahoo.com with NNFMP; 19 Feb 2013 13:41:35 -0000 Received: from [212.82.109.129] by tm17.bullet.mail.ird.yahoo.com with NNFMP; 19 Feb 2013 13:41:35 -0000 Received: from [127.0.0.1] by omp1036.mail.ird.yahoo.com with NNFMP; 19 Feb 2013 13:41:35 -0000 X-Yahoo-Newman-Property: ymail-3 X-Yahoo-Newman-Id: 208634.92170.bm@omp1036.mail.ird.yahoo.com Received: (qmail 12398 invoked by uid 60001); 19 Feb 2013 13:41:35 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.co.uk; s=s1024; t=1361281295; bh=3cWsd2ZqgBoReJLX0FFU14oBN0XnC7paLHyGtsGhhlE=; h=X-YMail-OSG:Received:X-Rocket-MIMEInfo:X-Mailer:References:Message-ID:Date:From:Reply-To:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=pCqAPJna1eOXhGAaG7bwFwbKftLKrEbpcTU3/w+Q7e+XZHCZwe12sdW17avCDtrMew5gSkcJ6bxoBI2X1apU7KeZESqje36g5GlbSyfYoBnTo04+dfJ9l09/3OEP3bUIm/HQHdqCh/3Xal75qDnU6X77haw4PW64nx55XBCw/HU= DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.co.uk; h=X-YMail-OSG:Received:X-Rocket-MIMEInfo:X-Mailer:References:Message-ID:Date:From:Reply-To:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=6GaZd4eGFDvvBSjZxfoOzGuaTUw4QZ1oB3gxRZun+w9fIV/6o9431n4I0tJXPBMb4WG+mElHaPjloX0F69D+/TJbdeyIbU4U6RC1dj1NY7v7i9nOXOsByiLxseGivD8GcRIOylKsl+6FGfj7XMJhOrW1/aakDJ8ZiOloDt7tUt8=; X-YMail-OSG: gogXdukVM1lRy2Rf1ioBfFwLGuB_HOAPC2_f_0o.Iz7FJUm Ql5au4U6KEbPAGbsCUlpM2hNg08A3ppsra5S9dumvw5ltt4FjmkObEL2TNvC g20gCth5EE4ZLRImbGCFFAVeWTe3d1wG.fXo04TOAj0hemjT9COcyc2Z49dS sInh1Xx7NJ3lZ7cJrcW_NE9w2.i9JyJXgA2E_DFag45tmHBLThOJvCxBI9sz 1XH80.TWLBtUOkT8vDcjIWcrSlCX_6lkO.OTUoTTjqyWgE11n5Ywcm6ykvKa 0ux0WQsBQc3dlLbUsJBq_NtPeIJ_bCieiRhs3NP.nUqMq4XwJkPGEijIlDgj YDR0R5aSl6Fq1qxdJjvQiFHWG9wH4uY_5SSce61K9jHJClMEGHgEW9_JHLQI yBtQkM03zKWAidssYH2x0K2kQDR7m4G.HOwT3nN0p7Zu08gkNg74dAG.hyuT OZh0Y1EWKVf2j15wc5dVIaPO3syYviHQcbfkKhcfLlfEPiYdiCOv4pXFC Received: from [195.212.29.67] by web171304.mail.ir2.yahoo.com via HTTP; Tue, 19 Feb 2013 13:41:34 GMT X-Rocket-MIMEInfo: 001.001, Cgo.SGkgSWFuLAo.Cj4KPlRoYW5rcyBmb3IgdGhlIGZlZWRiYWNrIC0KCgpObyBwcm9ibGVtLgoKPgo.Cj5JJ20gc3RpbGwgYSBsaXR0bGUgd2FyeSB0aGF0IHBlcmhhcHMgdGhlcmUncyBhIGJ1ZyBpbiB4bCBzaW5jZSB0aGUgbmV0Ym9vdCBpbWFnZSBzaG91bGQndmUgd29ya2VkIEkgdGhpbmssIGJ1dCBoYXBweSB0aGF0IHRoaXMgbWV0aG9kIGRvZXMgd29yay4KPgo.CgoKSSd2ZSBqdXN0IHRyaWVkIGl0IGFnYWluIHdpdGggMTIuMDQuMiB4ZW4gYm9vdCBpbWFnZXMgYW5kIGFsbCB3ZW50IHdlbGwuIEhlcmUBMAEBAQE- X-Mailer: YahooMailWebService/0.8.133.508 References: <51229E41.2090103@yahoo.co.uk> Message-ID: <1361281294.8796.YahooMailNeo@web171304.mail.ir2.yahoo.com> Date: Tue, 19 Feb 2013 13:41:34 +0000 (GMT) From: Ian Murray To: Andrew Eross In-Reply-To: MIME-Version: 1.0 Cc: "xen-users@lists.xen.org" Subject: Re: [Xen-users] Xen 4.2.1 unable to get domain type for domid X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: Ian Murray 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 Ian, > > >Thanks for the feedback - No problem. > > >I'm still a little wary that perhaps there's a bug in xl since the netboot= image should've worked I think, but happy that this method does work. > > I've just tried it again with 12.04.2 xen boot images and all went well. He= re is my config file... name=A0=A0=A0=A0=A0 =3D "ubuntu-calendar-test" memory=A0=A0=A0 =3D 1024 disk=A0=A0=A0=A0=A0 =3D ['phy:/dev/VG1/ubuntu-calendar-test,xvda,w' ] vif =3D [ 'mac=3D00:16:31:55:1c:82' ] kernel=A0=A0=A0 =3D "/root/xen/ubuntu1204/vmlinuz" ramdisk=A0=A0 =3D "/root/xen/ubuntu1204/initrd.gz" vcpus=A0=A0=A0=A0 =3D 2 on_reboot =3D 'destroy' on_crash=A0 =3D 'destroy' Are you sure there is no problem with your images? Here is are md5 hashes f= or the two files I used (12.04.2, 32bit as far as I remember)... f1f36dbfe47ebda085f41394dd079d09=A0 initrd.gz 8525c3e8d6131ae462ba85b935a70bae=A0 vmlinuz _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Tue Feb 19 14:36:56 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 19 Feb 2013 14:36: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 1U7oId-0006h1-Ak; Tue, 19 Feb 2013 14:36:03 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U7oIb-0006gu-Lh for xen-users@lists.xen.org; Tue, 19 Feb 2013 14:36:02 +0000 Received: from [193.109.254.147:35577] by server-5.bemta-14.messagelabs.com id 7D/41-21539-0DD83215; Tue, 19 Feb 2013 14:36:00 +0000 X-Env-Sender: raistlin.df@gmail.com X-Msg-Ref: server-15.tower-27.messagelabs.com!1361284548!2025808!1 X-Originating-IP: [74.125.83.47] X-SpamReason: No, hits=0.0 required=7.0 tests=ML_RADAR_SPEW_LINKS_8, spamassassin: , async_handler: YXN5bmNfZGVsYXk6IDcwNjE4MDUgKHRpbWVvdXQp\n X-StarScan-Received: X-StarScan-Version: 6.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 7782 invoked from network); 19 Feb 2013 14:35:48 -0000 Received: from mail-ee0-f47.google.com (HELO mail-ee0-f47.google.com) (74.125.83.47) by server-15.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 19 Feb 2013 14:35:48 -0000 Received: by mail-ee0-f47.google.com with SMTP id e52so3489952eek.34 for ; Tue, 19 Feb 2013 06:35:48 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:sender:message-id:subject:from:to:cc:date:in-reply-to :references:content-type:x-mailer:mime-version; bh=E/tvXf+em1W3kBBTiL40t8Qs06Y8ciMJFIyTPPLo9eo=; b=VZ3kRUIKMLBnLcrgARVajiTYBMSm5ej2VGFR8AEvusjwViNNswfWVtNFNWIzZb8HDQ dI7CSy2ObNk5GhiL9z2Pe5hsKzQnxLrepzTJmHb1xCh16KsughHLNmVowyZDGE3+cpeI WphjNmL0be9RXrH10hOSCPpXxLt3TdMrJHh2xX+sJyX5sPVWizDPItJxbOH6FDEJXy7j kibiZLBlw3TbDHFe1Mwv4+2FrbFnDhzMRrTWIkcZpO202L6geg+QCkf4faMT++gXpm8K GNHEuRMp+WMQoo0a/wXQHs9W84G+jT1WVKeP4ExJ/EJgBVwFnZRG7rYcPs6TCBaduSW9 kzHg== X-Received: by 10.14.0.135 with SMTP id 7mr57379033eeb.5.1361284548332; Tue, 19 Feb 2013 06:35:48 -0800 (PST) Received: from [192.168.0.40] (ip-143-209.sn3.eutelia.it. [213.136.143.209]) by mx.google.com with ESMTPS id 44sm104256312eek.5.2013.02.19.06.35.46 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 19 Feb 2013 06:35:47 -0800 (PST) Message-ID: <1361284532.11615.3.camel@Solace> From: Dario Faggioli To: FONG Julio Date: Tue, 19 Feb 2013 15:35:32 +0100 In-Reply-To: <20130214170349.280610@gmx.com> References: <20130214170349.280610@gmx.com> X-Mailer: Evolution 3.4.4-2 Mime-Version: 1.0 Cc: xen-users@lists.xen.org Subject: Re: [Xen-users] xen 4.1.2 cpu cores question X-BeenThere: xen-users@lists.xen.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="===============1719168419707150108==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============1719168419707150108== Content-Type: multipart/signed; micalg="pgp-sha1"; protocol="application/pgp-signature"; boundary="=-V7lwVkEf5p9OBx11izYh" --=-V7lwVkEf5p9OBx11izYh Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Thu, 2013-02-14 at 12:03 -0500, FONG Julio wrote: > Hi, > Hi, > I have a i5 2500K quad core and command "xm info" return me 4 cores. > Quand core, and each core hyperthreaded (I guess so, basing on what you say below). > Is it normal as on xen 3 it was 8 cores?? > Well, if it's a 4 cores with HT, it should tell you 8. I've never used Xen 3, but I don't see a reason why switching from 3 to 4 should have "eaten" 4 cores! Have you perhaps disabled hyperthreading in BIOS, or anything like that? What does /proc/cpuinfo say if booting Linux baremetal (i.e., without Xen)? Dario --=20 <> (Raistlin Majere) ----------------------------------------------------------------- Dario Faggioli, Ph.D, http://about.me/dario.faggioli Senior Software Engineer, Citrix Systems R&D Ltd., Cambridge (UK) --=-V7lwVkEf5p9OBx11izYh 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.12 (GNU/Linux) iEYEABECAAYFAlEjjbQACgkQk4XaBE3IOsQsJACfYYa7TnzPfUHqZuWihZjujGHO eVcAnj/68tWaJV/y/fFc3uaRqUC4E39A =xiKX -----END PGP SIGNATURE----- --=-V7lwVkEf5p9OBx11izYh-- --===============1719168419707150108== 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 --===============1719168419707150108==-- From xen-users-bounces@lists.xen.org Tue Feb 19 14:36:56 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 19 Feb 2013 14:36: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 1U7oId-0006h1-Ak; Tue, 19 Feb 2013 14:36:03 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U7oIb-0006gu-Lh for xen-users@lists.xen.org; Tue, 19 Feb 2013 14:36:02 +0000 Received: from [193.109.254.147:35577] by server-5.bemta-14.messagelabs.com id 7D/41-21539-0DD83215; Tue, 19 Feb 2013 14:36:00 +0000 X-Env-Sender: raistlin.df@gmail.com X-Msg-Ref: server-15.tower-27.messagelabs.com!1361284548!2025808!1 X-Originating-IP: [74.125.83.47] X-SpamReason: No, hits=0.0 required=7.0 tests=ML_RADAR_SPEW_LINKS_8, spamassassin: , async_handler: YXN5bmNfZGVsYXk6IDcwNjE4MDUgKHRpbWVvdXQp\n X-StarScan-Received: X-StarScan-Version: 6.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 7782 invoked from network); 19 Feb 2013 14:35:48 -0000 Received: from mail-ee0-f47.google.com (HELO mail-ee0-f47.google.com) (74.125.83.47) by server-15.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 19 Feb 2013 14:35:48 -0000 Received: by mail-ee0-f47.google.com with SMTP id e52so3489952eek.34 for ; Tue, 19 Feb 2013 06:35:48 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:sender:message-id:subject:from:to:cc:date:in-reply-to :references:content-type:x-mailer:mime-version; bh=E/tvXf+em1W3kBBTiL40t8Qs06Y8ciMJFIyTPPLo9eo=; b=VZ3kRUIKMLBnLcrgARVajiTYBMSm5ej2VGFR8AEvusjwViNNswfWVtNFNWIzZb8HDQ dI7CSy2ObNk5GhiL9z2Pe5hsKzQnxLrepzTJmHb1xCh16KsughHLNmVowyZDGE3+cpeI WphjNmL0be9RXrH10hOSCPpXxLt3TdMrJHh2xX+sJyX5sPVWizDPItJxbOH6FDEJXy7j kibiZLBlw3TbDHFe1Mwv4+2FrbFnDhzMRrTWIkcZpO202L6geg+QCkf4faMT++gXpm8K GNHEuRMp+WMQoo0a/wXQHs9W84G+jT1WVKeP4ExJ/EJgBVwFnZRG7rYcPs6TCBaduSW9 kzHg== X-Received: by 10.14.0.135 with SMTP id 7mr57379033eeb.5.1361284548332; Tue, 19 Feb 2013 06:35:48 -0800 (PST) Received: from [192.168.0.40] (ip-143-209.sn3.eutelia.it. [213.136.143.209]) by mx.google.com with ESMTPS id 44sm104256312eek.5.2013.02.19.06.35.46 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 19 Feb 2013 06:35:47 -0800 (PST) Message-ID: <1361284532.11615.3.camel@Solace> From: Dario Faggioli To: FONG Julio Date: Tue, 19 Feb 2013 15:35:32 +0100 In-Reply-To: <20130214170349.280610@gmx.com> References: <20130214170349.280610@gmx.com> X-Mailer: Evolution 3.4.4-2 Mime-Version: 1.0 Cc: xen-users@lists.xen.org Subject: Re: [Xen-users] xen 4.1.2 cpu cores question X-BeenThere: xen-users@lists.xen.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="===============1719168419707150108==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============1719168419707150108== Content-Type: multipart/signed; micalg="pgp-sha1"; protocol="application/pgp-signature"; boundary="=-V7lwVkEf5p9OBx11izYh" --=-V7lwVkEf5p9OBx11izYh Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Thu, 2013-02-14 at 12:03 -0500, FONG Julio wrote: > Hi, > Hi, > I have a i5 2500K quad core and command "xm info" return me 4 cores. > Quand core, and each core hyperthreaded (I guess so, basing on what you say below). > Is it normal as on xen 3 it was 8 cores?? > Well, if it's a 4 cores with HT, it should tell you 8. I've never used Xen 3, but I don't see a reason why switching from 3 to 4 should have "eaten" 4 cores! Have you perhaps disabled hyperthreading in BIOS, or anything like that? What does /proc/cpuinfo say if booting Linux baremetal (i.e., without Xen)? Dario --=20 <> (Raistlin Majere) ----------------------------------------------------------------- Dario Faggioli, Ph.D, http://about.me/dario.faggioli Senior Software Engineer, Citrix Systems R&D Ltd., Cambridge (UK) --=-V7lwVkEf5p9OBx11izYh 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.12 (GNU/Linux) iEYEABECAAYFAlEjjbQACgkQk4XaBE3IOsQsJACfYYa7TnzPfUHqZuWihZjujGHO eVcAnj/68tWaJV/y/fFc3uaRqUC4E39A =xiKX -----END PGP SIGNATURE----- --=-V7lwVkEf5p9OBx11izYh-- --===============1719168419707150108== 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 --===============1719168419707150108==-- From xen-users-bounces@lists.xen.org Tue Feb 19 14:59:11 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 19 Feb 2013 14:59: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 1U7oeA-0000JK-Vo; Tue, 19 Feb 2013 14:58:18 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U7oe9-0000J3-HR for xen-users@lists.xen.org; Tue, 19 Feb 2013 14:58:17 +0000 Received: from [85.158.137.99:57178] by server-13.bemta-3.messagelabs.com id 1A/00-20653-80393215; Tue, 19 Feb 2013 14:58:16 +0000 X-Env-Sender: s.munaut@whatever-company.com X-Msg-Ref: server-7.tower-217.messagelabs.com!1361285894!12258503!1 X-Originating-IP: [209.85.214.42] X-SpamReason: No, hits=0.3 required=7.0 tests=RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 19562 invoked from network); 19 Feb 2013 14:58:15 -0000 Received: from mail-bk0-f42.google.com (HELO mail-bk0-f42.google.com) (209.85.214.42) by server-7.tower-217.messagelabs.com with RC4-SHA encrypted SMTP; 19 Feb 2013 14:58:15 -0000 Received: by mail-bk0-f42.google.com with SMTP id jk7so3084753bkc.15 for ; Tue, 19 Feb 2013 06:58:14 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-received:date:message-id:subject:from:to :content-type:x-gm-message-state; bh=mCwA7WYrS7LdKHDFVz+KhR5BY+cQ2EAhGtNldSua3Ss=; b=JtNYVTxAYfK25c1c9wmxXu6Li4cefCeZyLgz6tlYnHbVeqp4ooSlVvNrApK4sxc1aw sr6QbXBEaGBU6snu6LJe5n69eUXTwW1OyJPmb3jYDtBp7BU7Xbw2wtrBbmWtnGafpmEU DdGJVpC699EFkrtbx70g3YTmQgyr4/k92aJg6SYFFG9qmo2H7bYJz09CEOlumhT74o6l v7CgziRkkSqOsDLarnXd27r7+8hzggRNtPcRgYSpBJhCEkwQuBK/AlOv7jg6eArlOhBL Vyl3smm50ZUZKLrzPtRHHOIFUzJB7c9UgX3kvaoTtlgqKPRA1TS8WohZXAN1Olqwi6JX Rc+w== MIME-Version: 1.0 X-Received: by 10.204.145.195 with SMTP id e3mr6801625bkv.27.1361285894490; Tue, 19 Feb 2013 06:58:14 -0800 (PST) Received: by 10.205.137.141 with HTTP; Tue, 19 Feb 2013 06:58:14 -0800 (PST) Date: Tue, 19 Feb 2013 15:58:14 +0100 Message-ID: From: Sylvain Munaut To: xen-users@lists.xen.org X-Gm-Message-State: ALoCoQmWzUwbj1YWimSZmqOeDbDfX91nsSwGIvcKSkiyoykum0mhRcBIgCMpolLPbTulDJAx/aeh Subject: [Xen-users] Xen 4.1.2 - stub domains for IO. Not working ? X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: 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 use stub domains for IO for HVM domains, under Xen 4.1.2 with xl toolstack The domain works fine with either qemu-xen-traditional or qemu upstream, but I'd like to try stub domains. If I understand the doc correctly just adding "device_model_stubdomain_override = 1" to the config should do the trick. However doing that doesn't really work. - qemu-dm is still started in the dom0 which AFAIU shouldn't be the case. - There is a xxx-dm domain that starts so that's a good sign, however they both stay stuck like : wxp-00 7 1531 1 ------ 0.0 wxp-00-dm 8 32 1 ---sc- 0.0 Here's the xl -vvv log : root@smallbox:/etc/xen # xl -vvv create vm-wxp-00 Parsing config from vm-wxp-00 libxl: debug: libxl_create.c:1174:do_domain_create: ao 0x2578f40: create: how=(nil) callback=(nil) poller=0x2578820 libxl: debug: libxl_device.c:229:libxl__device_disk_set_backend: Disk vdev=xvda spec.backend=unknown libxl: debug: libxl_device.c:265:libxl__device_disk_set_backend: Disk vdev=xvda, 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=0x2579310: deregister unregistered libxl: debug: libxl_numa.c:435:libxl__get_numa_candidate: New best NUMA placement candidate found: nr_nodes=1, nr_cpus=2, nr_vcpus=4, free_memkb=7321 libxl: detail: libxl_dom.c:192:numa_place_domain: NUMA placement candidate with 1 nodes, 2 cpus and 7321 KB free selected xc: detail: elf_parse_binary: phdr: paddr=0x100000 memsz=0x9dda8 xc: detail: elf_parse_binary: memory: 0x100000 -> 0x19dda8 xc: info: VIRTUAL MEMORY ARRANGEMENT: Loader: 0000000000100000->000000000019dda8 TOTAL: 0000000000000000->000000005f800000 ENTRY ADDRESS: 0000000000100608 xc: info: PHYSICAL MEMORY ALLOCATION: 4KB PAGES: 0x0000000000000200 2MB PAGES: 0x00000000000002fb 1GB PAGES: 0x0000000000000000 xc: detail: elf_load_binary: phdr 0 at 0x0x7ffc12f5d000 -> 0x0x7ffc12ff1c35 libxl: debug: libxl_device.c:229:libxl__device_disk_set_backend: Disk vdev=xvda spec.backend=phy libxl: debug: libxl_event.c:512:libxl__ev_xswatch_register: watch w=0x257a918 wpath=/local/domain/0/backend/vbd/7/51712/state token=3/0: register slotnum=3 libxl: debug: libxl_create.c:1187:do_domain_create: ao 0x2578f40: inprogress: poller=0x2578820, flags=i libxl: debug: libxl_event.c:457:watchfd_callback: watch w=0x257a918 wpath=/local/domain/0/backend/vbd/7/51712/state token=3/0: event epath=/local/domain/0/backend/vbd/7/51712/state libxl: debug: libxl_event.c:600:devstate_watch_callback: backend /local/domain/0/backend/vbd/7/51712/state wanted state 2 still waiting state 1 libxl: debug: libxl_event.c:457:watchfd_callback: watch w=0x257a918 wpath=/local/domain/0/backend/vbd/7/51712/state token=3/0: event epath=/local/domain/0/backend/vbd/7/51712/state libxl: debug: libxl_event.c:596:devstate_watch_callback: backend /local/domain/0/backend/vbd/7/51712/state wanted state 2 ok libxl: debug: libxl_event.c:549:libxl__ev_xswatch_deregister: watch w=0x257a918 wpath=/local/domain/0/backend/vbd/7/51712/state token=3/0: deregister slotnum=3 libxl: debug: libxl_event.c:561:libxl__ev_xswatch_deregister: watch w=0x257a918: deregister unregistered libxl: debug: libxl_device.c:917:device_hotplug: calling hotplug script: /etc/xen/scripts/block add libxl: debug: libxl_numa.c:435:libxl__get_numa_candidate: New best NUMA placement candidate found: nr_nodes=1, nr_cpus=2, nr_vcpus=5, free_memkb=5783 libxl: detail: libxl_dom.c:192:numa_place_domain: NUMA placement candidate with 1 nodes, 2 cpus and 5783 KB free selected domainbuilder: detail: xc_dom_allocate: cmdline=" -d 7", features="" libxl: debug: libxl_dom.c:380:libxl__build_pv: pv kernel mapped 0 path /usr/lib/xen-4.2/boot/ioemu-stubdom.gz domainbuilder: detail: xc_dom_kernel_file: filename="/usr/lib/xen-4.2/boot/ioemu-stubdom.gz" domainbuilder: detail: xc_dom_malloc_filemap : 826 kB domainbuilder: detail: xc_dom_malloc : 8487 kB domainbuilder: detail: xc_dom_do_gunzip: unzip ok, 0xce974 -> 0x849cc3 domainbuilder: detail: xc_dom_boot_xen_init: ver 4.2, 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 domainbuilder: detail: xc_dom_parse_image: called domainbuilder: detail: xc_dom_find_loader: trying multiboot-binary loader ... domainbuilder: detail: loader probe failed domainbuilder: detail: xc_dom_find_loader: trying Linux bzImage loader ... domainbuilder: detail: xc_dom_probe_bzimage_kernel: kernel is not a bzImage domainbuilder: detail: loader probe failed domainbuilder: detail: xc_dom_find_loader: trying ELF-generic loader ... domainbuilder: detail: loader probe OK xc: detail: elf_parse_binary: phdr: paddr=0x0 memsz=0x566d18 xc: detail: elf_parse_binary: memory: 0x0 -> 0x566d18 xc: detail: elf_xen_parse: __xen_guest: "GUEST_OS=Mini-OS,XEN_VER=xen-3.0,VIRT_BASE=0x0,ELF_PADDR_OFFSET=0x0,HYPERCALL_PAGE=0x2,LOADER=generic" xc: detail: elf_xen_parse_guest_info: GUEST_OS="Mini-OS" xc: detail: elf_xen_parse_guest_info: XEN_VER="xen-3.0" xc: detail: elf_xen_parse_guest_info: VIRT_BASE="0x0" xc: detail: elf_xen_parse_guest_info: ELF_PADDR_OFFSET="0x0" xc: detail: elf_xen_parse_guest_info: HYPERCALL_PAGE="0x2" xc: detail: elf_xen_parse_guest_info: LOADER="generic" xc: detail: elf_xen_addr_calc_check: addresses: xc: detail: virt_base = 0x0 xc: detail: elf_paddr_offset = 0x0 xc: detail: virt_offset = 0x0 xc: detail: virt_kstart = 0x0 xc: detail: virt_kend = 0x566d18 xc: detail: virt_entry = 0x0 xc: detail: p2m_base = 0xffffffffffffffff domainbuilder: detail: xc_dom_parse_elf_kernel: xen-3.0-x86_64: 0x0 -> 0x566d18 domainbuilder: detail: xc_dom_mem_init: mem 32 MB, pages 0x2000 pages, 4k each domainbuilder: detail: xc_dom_mem_init: 0x2000 pages domainbuilder: detail: xc_dom_boot_mem_init: called domainbuilder: detail: x86_compat: guest xen-3.0-x86_64, address size 64 domainbuilder: detail: xc_dom_build_image: called domainbuilder: detail: xc_dom_alloc_segment: kernel : 0x0 -> 0x567000 (pfn 0x0 + 0x567 pages) domainbuilder: detail: xc_dom_pfn_to_ptr: domU mapping: pfn 0x0+0x567 at 0x7ffc10181000 xc: detail: elf_load_binary: phdr 0 at 0x0x7ffc10181000 -> 0x0x7ffc106e7d18 domainbuilder: detail: xc_dom_alloc_segment: phys2mach : 0x567000 -> 0x577000 (pfn 0x567 + 0x10 pages) domainbuilder: detail: xc_dom_pfn_to_ptr: domU mapping: pfn 0x567+0x10 at 0x7ffc10171000 domainbuilder: detail: xc_dom_alloc_page : start info : 0x577000 (pfn 0x577) domainbuilder: detail: xc_dom_alloc_page : xenstore : 0x578000 (pfn 0x578) domainbuilder: detail: xc_dom_alloc_page : console : 0x579000 (pfn 0x579) domainbuilder: detail: nr_page_tables: 0x0000ffffffffffff/48: 0x0000000000000000 -> 0x0000ffffffffffff, 1 table(s) domainbuilder: detail: nr_page_tables: 0x0000007fffffffff/39: 0x0000000000000000 -> 0x0000007fffffffff, 1 table(s) domainbuilder: detail: nr_page_tables: 0x000000003fffffff/30: 0x0000000000000000 -> 0x000000003fffffff, 1 table(s) domainbuilder: detail: nr_page_tables: 0x00000000001fffff/21: 0x0000000000000000 -> 0x00000000007fffff, 4 table(s) domainbuilder: detail: xc_dom_alloc_segment: page tables : 0x57a000 -> 0x581000 (pfn 0x57a + 0x7 pages) domainbuilder: detail: xc_dom_pfn_to_ptr: domU mapping: pfn 0x57a+0x7 at 0x7ffc1016a000 domainbuilder: detail: xc_dom_alloc_page : boot stack : 0x581000 (pfn 0x581) domainbuilder: detail: xc_dom_build_image : virt_alloc_end : 0x582000 domainbuilder: detail: xc_dom_build_image : virt_pgtab_end : 0x800000 domainbuilder: detail: xc_dom_boot_image: called domainbuilder: detail: arch_setup_bootearly: doing nothing domainbuilder: detail: xc_dom_compat_check: supported guest type: xen-3.0-x86_64 <= matches domainbuilder: detail: xc_dom_compat_check: supported guest type: xen-3.0-x86_32p domainbuilder: detail: xc_dom_compat_check: supported guest type: hvm-3.0-x86_32 domainbuilder: detail: xc_dom_compat_check: supported guest type: hvm-3.0-x86_32p domainbuilder: detail: xc_dom_compat_check: supported guest type: hvm-3.0-x86_64 domainbuilder: detail: xc_dom_update_guest_p2m: dst 64bit, pages 0x2000 domainbuilder: detail: clear_page: pfn 0x579, mfn 0x1f58fd domainbuilder: detail: clear_page: pfn 0x578, mfn 0x1f58fe domainbuilder: detail: xc_dom_pfn_to_ptr: domU mapping: pfn 0x577+0x1 at 0x7ffc10167000 domainbuilder: detail: start_info_x86_64: called domainbuilder: detail: setup_hypercall_page: vaddr=0x2000 pfn=0x2 domainbuilder: detail: domain builder memory footprint domainbuilder: detail: allocated domainbuilder: detail: malloc : 8586 kB domainbuilder: detail: anon mmap : 0 bytes domainbuilder: detail: mapped domainbuilder: detail: file mmap : 826 kB domainbuilder: detail: domU mmap : 5628 kB domainbuilder: detail: arch_setup_bootlate: shared_info: pfn 0x0, mfn 0xd7d0e domainbuilder: detail: shared_info_x86_64: called domainbuilder: detail: vcpu_x86_64: called domainbuilder: detail: vcpu_x86_64: cr3: pfn 0x57a mfn 0x1f58fc domainbuilder: detail: launch_vm: called, ctxt=0x7fff20e44ba0 domainbuilder: detail: xc_dom_release: called libxl: debug: libxl_device.c:229:libxl__device_disk_set_backend: Disk vdev=xvda spec.backend=phy libxl: debug: libxl_event.c:512:libxl__ev_xswatch_register: watch w=0x257da68 wpath=/local/domain/0/backend/vbd/8/51712/state token=3/1: register slotnum=3 libxl: debug: libxl_event.c:457:watchfd_callback: watch w=0x257da68 wpath=/local/domain/0/backend/vbd/8/51712/state token=3/1: event epath=/local/domain/0/backend/vbd/8/51712/state libxl: debug: libxl_event.c:600:devstate_watch_callback: backend /local/domain/0/backend/vbd/8/51712/state wanted state 2 still waiting state 1 libxl: debug: libxl_event.c:457:watchfd_callback: watch w=0x257da68 wpath=/local/domain/0/backend/vbd/8/51712/state token=3/1: event epath=/local/domain/0/backend/vbd/8/51712/state libxl: debug: libxl_event.c:596:devstate_watch_callback: backend /local/domain/0/backend/vbd/8/51712/state wanted state 2 ok libxl: debug: libxl_event.c:549:libxl__ev_xswatch_deregister: watch w=0x257da68 wpath=/local/domain/0/backend/vbd/8/51712/state token=3/1: deregister slotnum=3 libxl: debug: libxl_event.c:561:libxl__ev_xswatch_deregister: watch w=0x257da68: deregister unregistered libxl: debug: libxl_device.c:917:device_hotplug: calling hotplug script: /etc/xen/scripts/block add libxl: debug: libxl_dm.c:1142:libxl__spawn_local_dm: Spawning device-model /usr/lib/xen-4.2/bin/qemu-dm with arguments: libxl: debug: libxl_dm.c:1144:libxl__spawn_local_dm: /usr/lib/xen-4.2/bin/qemu-dm libxl: debug: libxl_dm.c:1144:libxl__spawn_local_dm: -d libxl: debug: libxl_dm.c:1144:libxl__spawn_local_dm: 8 libxl: debug: libxl_dm.c:1144:libxl__spawn_local_dm: -domain-name libxl: debug: libxl_dm.c:1144:libxl__spawn_local_dm: wxp-00-dm libxl: debug: libxl_dm.c:1144:libxl__spawn_local_dm: -vnc libxl: debug: libxl_dm.c:1144:libxl__spawn_local_dm: 0.0.0.0:0,password libxl: debug: libxl_dm.c:1144:libxl__spawn_local_dm: -M libxl: debug: libxl_dm.c:1144:libxl__spawn_local_dm: xenpv libxl: debug: libxl_event.c:512:libxl__ev_xswatch_register: watch w=0x2579908 wpath=/local/domain/0/device-model/8/state token=3/2: register slotnum=3 libxl: debug: libxl_event.c:457:watchfd_callback: watch w=0x2579908 wpath=/local/domain/0/device-model/8/state token=3/2: event epath=/local/domain/0/device-model/8/state libxl: debug: libxl_event.c:457:watchfd_callback: watch w=0x2579908 wpath=/local/domain/0/device-model/8/state token=3/2: event epath=/local/domain/0/device-model/8/state libxl: debug: libxl_event.c:549:libxl__ev_xswatch_deregister: watch w=0x2579908 wpath=/local/domain/0/device-model/8/state token=3/2: deregister slotnum=3 libxl: debug: libxl_event.c:561:libxl__ev_xswatch_deregister: watch w=0x2579908: deregister unregistered libxl: debug: libxl_event.c:512:libxl__ev_xswatch_register: watch w=0x25812e8 wpath=/local/domain/0/backend/vif/8/0/state token=3/3: register slotnum=3 libxl: debug: libxl_event.c:457:watchfd_callback: watch w=0x25812e8 wpath=/local/domain/0/backend/vif/8/0/state token=3/3: event epath=/local/domain/0/backend/vif/8/0/state libxl: debug: libxl_event.c:600:devstate_watch_callback: backend /local/domain/0/backend/vif/8/0/state wanted state 2 still waiting state 1 libxl: debug: libxl_event.c:457:watchfd_callback: watch w=0x25812e8 wpath=/local/domain/0/backend/vif/8/0/state token=3/3: event epath=/local/domain/0/backend/vif/8/0/state libxl: debug: libxl_event.c:596:devstate_watch_callback: backend /local/domain/0/backend/vif/8/0/state wanted state 2 ok libxl: debug: libxl_event.c:549:libxl__ev_xswatch_deregister: watch w=0x25812e8 wpath=/local/domain/0/backend/vif/8/0/state token=3/3: deregister slotnum=3 libxl: debug: libxl_event.c:561:libxl__ev_xswatch_deregister: watch w=0x25812e8: deregister unregistered libxl: debug: libxl_device.c:917:device_hotplug: calling hotplug script: /etc/xen/scripts/vif-bridge online libxl: debug: libxl_event.c:512:libxl__ev_xswatch_register: watch w=0x2581e78 wpath=/local/domain/0/backend/vif/7/0/state token=3/4: register slotnum=3 libxl: debug: libxl_event.c:457:watchfd_callback: watch w=0x2581e78 wpath=/local/domain/0/backend/vif/7/0/state token=3/4: event epath=/local/domain/0/backend/vif/7/0/state libxl: debug: libxl_event.c:600:devstate_watch_callback: backend /local/domain/0/backend/vif/7/0/state wanted state 2 still waiting state 1 libxl: debug: libxl_event.c:457:watchfd_callback: watch w=0x2581e78 wpath=/local/domain/0/backend/vif/7/0/state token=3/4: event epath=/local/domain/0/backend/vif/7/0/state libxl: debug: libxl_event.c:596:devstate_watch_callback: backend /local/domain/0/backend/vif/7/0/state wanted state 2 ok libxl: debug: libxl_event.c:549:libxl__ev_xswatch_deregister: watch w=0x2581e78 wpath=/local/domain/0/backend/vif/7/0/state token=3/4: deregister slotnum=3 libxl: debug: libxl_event.c:561:libxl__ev_xswatch_deregister: watch w=0x2581e78: deregister unregistered libxl: debug: libxl_device.c:917:device_hotplug: calling hotplug script: /etc/xen/scripts/vif-bridge online libxl: debug: libxl_event.c:1667:libxl__ao_progress_report: ao 0x2578f40: progress report: ignored libxl: debug: libxl_event.c:1499:libxl__ao_complete: ao 0x2578f40: complete, rc=0 libxl: debug: libxl_event.c:1471:libxl__ao__destroy: ao 0x2578f40: destroy Daemon running with PID 4294 xc: debug: hypercall buffer: total allocations:813 total releases:813 xc: debug: hypercall buffer: current allocations:0 maximum allocations:4 xc: debug: hypercall buffer: cache current size:4 xc: debug: hypercall buffer: cache hits:799 misses:4 toobig:10 Cheers, Sylvain _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Tue Feb 19 14:59:11 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 19 Feb 2013 14:59: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 1U7oeA-0000JK-Vo; Tue, 19 Feb 2013 14:58:18 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U7oe9-0000J3-HR for xen-users@lists.xen.org; Tue, 19 Feb 2013 14:58:17 +0000 Received: from [85.158.137.99:57178] by server-13.bemta-3.messagelabs.com id 1A/00-20653-80393215; Tue, 19 Feb 2013 14:58:16 +0000 X-Env-Sender: s.munaut@whatever-company.com X-Msg-Ref: server-7.tower-217.messagelabs.com!1361285894!12258503!1 X-Originating-IP: [209.85.214.42] X-SpamReason: No, hits=0.3 required=7.0 tests=RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 19562 invoked from network); 19 Feb 2013 14:58:15 -0000 Received: from mail-bk0-f42.google.com (HELO mail-bk0-f42.google.com) (209.85.214.42) by server-7.tower-217.messagelabs.com with RC4-SHA encrypted SMTP; 19 Feb 2013 14:58:15 -0000 Received: by mail-bk0-f42.google.com with SMTP id jk7so3084753bkc.15 for ; Tue, 19 Feb 2013 06:58:14 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-received:date:message-id:subject:from:to :content-type:x-gm-message-state; bh=mCwA7WYrS7LdKHDFVz+KhR5BY+cQ2EAhGtNldSua3Ss=; b=JtNYVTxAYfK25c1c9wmxXu6Li4cefCeZyLgz6tlYnHbVeqp4ooSlVvNrApK4sxc1aw sr6QbXBEaGBU6snu6LJe5n69eUXTwW1OyJPmb3jYDtBp7BU7Xbw2wtrBbmWtnGafpmEU DdGJVpC699EFkrtbx70g3YTmQgyr4/k92aJg6SYFFG9qmo2H7bYJz09CEOlumhT74o6l v7CgziRkkSqOsDLarnXd27r7+8hzggRNtPcRgYSpBJhCEkwQuBK/AlOv7jg6eArlOhBL Vyl3smm50ZUZKLrzPtRHHOIFUzJB7c9UgX3kvaoTtlgqKPRA1TS8WohZXAN1Olqwi6JX Rc+w== MIME-Version: 1.0 X-Received: by 10.204.145.195 with SMTP id e3mr6801625bkv.27.1361285894490; Tue, 19 Feb 2013 06:58:14 -0800 (PST) Received: by 10.205.137.141 with HTTP; Tue, 19 Feb 2013 06:58:14 -0800 (PST) Date: Tue, 19 Feb 2013 15:58:14 +0100 Message-ID: From: Sylvain Munaut To: xen-users@lists.xen.org X-Gm-Message-State: ALoCoQmWzUwbj1YWimSZmqOeDbDfX91nsSwGIvcKSkiyoykum0mhRcBIgCMpolLPbTulDJAx/aeh Subject: [Xen-users] Xen 4.1.2 - stub domains for IO. Not working ? X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: 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 use stub domains for IO for HVM domains, under Xen 4.1.2 with xl toolstack The domain works fine with either qemu-xen-traditional or qemu upstream, but I'd like to try stub domains. If I understand the doc correctly just adding "device_model_stubdomain_override = 1" to the config should do the trick. However doing that doesn't really work. - qemu-dm is still started in the dom0 which AFAIU shouldn't be the case. - There is a xxx-dm domain that starts so that's a good sign, however they both stay stuck like : wxp-00 7 1531 1 ------ 0.0 wxp-00-dm 8 32 1 ---sc- 0.0 Here's the xl -vvv log : root@smallbox:/etc/xen # xl -vvv create vm-wxp-00 Parsing config from vm-wxp-00 libxl: debug: libxl_create.c:1174:do_domain_create: ao 0x2578f40: create: how=(nil) callback=(nil) poller=0x2578820 libxl: debug: libxl_device.c:229:libxl__device_disk_set_backend: Disk vdev=xvda spec.backend=unknown libxl: debug: libxl_device.c:265:libxl__device_disk_set_backend: Disk vdev=xvda, 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=0x2579310: deregister unregistered libxl: debug: libxl_numa.c:435:libxl__get_numa_candidate: New best NUMA placement candidate found: nr_nodes=1, nr_cpus=2, nr_vcpus=4, free_memkb=7321 libxl: detail: libxl_dom.c:192:numa_place_domain: NUMA placement candidate with 1 nodes, 2 cpus and 7321 KB free selected xc: detail: elf_parse_binary: phdr: paddr=0x100000 memsz=0x9dda8 xc: detail: elf_parse_binary: memory: 0x100000 -> 0x19dda8 xc: info: VIRTUAL MEMORY ARRANGEMENT: Loader: 0000000000100000->000000000019dda8 TOTAL: 0000000000000000->000000005f800000 ENTRY ADDRESS: 0000000000100608 xc: info: PHYSICAL MEMORY ALLOCATION: 4KB PAGES: 0x0000000000000200 2MB PAGES: 0x00000000000002fb 1GB PAGES: 0x0000000000000000 xc: detail: elf_load_binary: phdr 0 at 0x0x7ffc12f5d000 -> 0x0x7ffc12ff1c35 libxl: debug: libxl_device.c:229:libxl__device_disk_set_backend: Disk vdev=xvda spec.backend=phy libxl: debug: libxl_event.c:512:libxl__ev_xswatch_register: watch w=0x257a918 wpath=/local/domain/0/backend/vbd/7/51712/state token=3/0: register slotnum=3 libxl: debug: libxl_create.c:1187:do_domain_create: ao 0x2578f40: inprogress: poller=0x2578820, flags=i libxl: debug: libxl_event.c:457:watchfd_callback: watch w=0x257a918 wpath=/local/domain/0/backend/vbd/7/51712/state token=3/0: event epath=/local/domain/0/backend/vbd/7/51712/state libxl: debug: libxl_event.c:600:devstate_watch_callback: backend /local/domain/0/backend/vbd/7/51712/state wanted state 2 still waiting state 1 libxl: debug: libxl_event.c:457:watchfd_callback: watch w=0x257a918 wpath=/local/domain/0/backend/vbd/7/51712/state token=3/0: event epath=/local/domain/0/backend/vbd/7/51712/state libxl: debug: libxl_event.c:596:devstate_watch_callback: backend /local/domain/0/backend/vbd/7/51712/state wanted state 2 ok libxl: debug: libxl_event.c:549:libxl__ev_xswatch_deregister: watch w=0x257a918 wpath=/local/domain/0/backend/vbd/7/51712/state token=3/0: deregister slotnum=3 libxl: debug: libxl_event.c:561:libxl__ev_xswatch_deregister: watch w=0x257a918: deregister unregistered libxl: debug: libxl_device.c:917:device_hotplug: calling hotplug script: /etc/xen/scripts/block add libxl: debug: libxl_numa.c:435:libxl__get_numa_candidate: New best NUMA placement candidate found: nr_nodes=1, nr_cpus=2, nr_vcpus=5, free_memkb=5783 libxl: detail: libxl_dom.c:192:numa_place_domain: NUMA placement candidate with 1 nodes, 2 cpus and 5783 KB free selected domainbuilder: detail: xc_dom_allocate: cmdline=" -d 7", features="" libxl: debug: libxl_dom.c:380:libxl__build_pv: pv kernel mapped 0 path /usr/lib/xen-4.2/boot/ioemu-stubdom.gz domainbuilder: detail: xc_dom_kernel_file: filename="/usr/lib/xen-4.2/boot/ioemu-stubdom.gz" domainbuilder: detail: xc_dom_malloc_filemap : 826 kB domainbuilder: detail: xc_dom_malloc : 8487 kB domainbuilder: detail: xc_dom_do_gunzip: unzip ok, 0xce974 -> 0x849cc3 domainbuilder: detail: xc_dom_boot_xen_init: ver 4.2, 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 domainbuilder: detail: xc_dom_parse_image: called domainbuilder: detail: xc_dom_find_loader: trying multiboot-binary loader ... domainbuilder: detail: loader probe failed domainbuilder: detail: xc_dom_find_loader: trying Linux bzImage loader ... domainbuilder: detail: xc_dom_probe_bzimage_kernel: kernel is not a bzImage domainbuilder: detail: loader probe failed domainbuilder: detail: xc_dom_find_loader: trying ELF-generic loader ... domainbuilder: detail: loader probe OK xc: detail: elf_parse_binary: phdr: paddr=0x0 memsz=0x566d18 xc: detail: elf_parse_binary: memory: 0x0 -> 0x566d18 xc: detail: elf_xen_parse: __xen_guest: "GUEST_OS=Mini-OS,XEN_VER=xen-3.0,VIRT_BASE=0x0,ELF_PADDR_OFFSET=0x0,HYPERCALL_PAGE=0x2,LOADER=generic" xc: detail: elf_xen_parse_guest_info: GUEST_OS="Mini-OS" xc: detail: elf_xen_parse_guest_info: XEN_VER="xen-3.0" xc: detail: elf_xen_parse_guest_info: VIRT_BASE="0x0" xc: detail: elf_xen_parse_guest_info: ELF_PADDR_OFFSET="0x0" xc: detail: elf_xen_parse_guest_info: HYPERCALL_PAGE="0x2" xc: detail: elf_xen_parse_guest_info: LOADER="generic" xc: detail: elf_xen_addr_calc_check: addresses: xc: detail: virt_base = 0x0 xc: detail: elf_paddr_offset = 0x0 xc: detail: virt_offset = 0x0 xc: detail: virt_kstart = 0x0 xc: detail: virt_kend = 0x566d18 xc: detail: virt_entry = 0x0 xc: detail: p2m_base = 0xffffffffffffffff domainbuilder: detail: xc_dom_parse_elf_kernel: xen-3.0-x86_64: 0x0 -> 0x566d18 domainbuilder: detail: xc_dom_mem_init: mem 32 MB, pages 0x2000 pages, 4k each domainbuilder: detail: xc_dom_mem_init: 0x2000 pages domainbuilder: detail: xc_dom_boot_mem_init: called domainbuilder: detail: x86_compat: guest xen-3.0-x86_64, address size 64 domainbuilder: detail: xc_dom_build_image: called domainbuilder: detail: xc_dom_alloc_segment: kernel : 0x0 -> 0x567000 (pfn 0x0 + 0x567 pages) domainbuilder: detail: xc_dom_pfn_to_ptr: domU mapping: pfn 0x0+0x567 at 0x7ffc10181000 xc: detail: elf_load_binary: phdr 0 at 0x0x7ffc10181000 -> 0x0x7ffc106e7d18 domainbuilder: detail: xc_dom_alloc_segment: phys2mach : 0x567000 -> 0x577000 (pfn 0x567 + 0x10 pages) domainbuilder: detail: xc_dom_pfn_to_ptr: domU mapping: pfn 0x567+0x10 at 0x7ffc10171000 domainbuilder: detail: xc_dom_alloc_page : start info : 0x577000 (pfn 0x577) domainbuilder: detail: xc_dom_alloc_page : xenstore : 0x578000 (pfn 0x578) domainbuilder: detail: xc_dom_alloc_page : console : 0x579000 (pfn 0x579) domainbuilder: detail: nr_page_tables: 0x0000ffffffffffff/48: 0x0000000000000000 -> 0x0000ffffffffffff, 1 table(s) domainbuilder: detail: nr_page_tables: 0x0000007fffffffff/39: 0x0000000000000000 -> 0x0000007fffffffff, 1 table(s) domainbuilder: detail: nr_page_tables: 0x000000003fffffff/30: 0x0000000000000000 -> 0x000000003fffffff, 1 table(s) domainbuilder: detail: nr_page_tables: 0x00000000001fffff/21: 0x0000000000000000 -> 0x00000000007fffff, 4 table(s) domainbuilder: detail: xc_dom_alloc_segment: page tables : 0x57a000 -> 0x581000 (pfn 0x57a + 0x7 pages) domainbuilder: detail: xc_dom_pfn_to_ptr: domU mapping: pfn 0x57a+0x7 at 0x7ffc1016a000 domainbuilder: detail: xc_dom_alloc_page : boot stack : 0x581000 (pfn 0x581) domainbuilder: detail: xc_dom_build_image : virt_alloc_end : 0x582000 domainbuilder: detail: xc_dom_build_image : virt_pgtab_end : 0x800000 domainbuilder: detail: xc_dom_boot_image: called domainbuilder: detail: arch_setup_bootearly: doing nothing domainbuilder: detail: xc_dom_compat_check: supported guest type: xen-3.0-x86_64 <= matches domainbuilder: detail: xc_dom_compat_check: supported guest type: xen-3.0-x86_32p domainbuilder: detail: xc_dom_compat_check: supported guest type: hvm-3.0-x86_32 domainbuilder: detail: xc_dom_compat_check: supported guest type: hvm-3.0-x86_32p domainbuilder: detail: xc_dom_compat_check: supported guest type: hvm-3.0-x86_64 domainbuilder: detail: xc_dom_update_guest_p2m: dst 64bit, pages 0x2000 domainbuilder: detail: clear_page: pfn 0x579, mfn 0x1f58fd domainbuilder: detail: clear_page: pfn 0x578, mfn 0x1f58fe domainbuilder: detail: xc_dom_pfn_to_ptr: domU mapping: pfn 0x577+0x1 at 0x7ffc10167000 domainbuilder: detail: start_info_x86_64: called domainbuilder: detail: setup_hypercall_page: vaddr=0x2000 pfn=0x2 domainbuilder: detail: domain builder memory footprint domainbuilder: detail: allocated domainbuilder: detail: malloc : 8586 kB domainbuilder: detail: anon mmap : 0 bytes domainbuilder: detail: mapped domainbuilder: detail: file mmap : 826 kB domainbuilder: detail: domU mmap : 5628 kB domainbuilder: detail: arch_setup_bootlate: shared_info: pfn 0x0, mfn 0xd7d0e domainbuilder: detail: shared_info_x86_64: called domainbuilder: detail: vcpu_x86_64: called domainbuilder: detail: vcpu_x86_64: cr3: pfn 0x57a mfn 0x1f58fc domainbuilder: detail: launch_vm: called, ctxt=0x7fff20e44ba0 domainbuilder: detail: xc_dom_release: called libxl: debug: libxl_device.c:229:libxl__device_disk_set_backend: Disk vdev=xvda spec.backend=phy libxl: debug: libxl_event.c:512:libxl__ev_xswatch_register: watch w=0x257da68 wpath=/local/domain/0/backend/vbd/8/51712/state token=3/1: register slotnum=3 libxl: debug: libxl_event.c:457:watchfd_callback: watch w=0x257da68 wpath=/local/domain/0/backend/vbd/8/51712/state token=3/1: event epath=/local/domain/0/backend/vbd/8/51712/state libxl: debug: libxl_event.c:600:devstate_watch_callback: backend /local/domain/0/backend/vbd/8/51712/state wanted state 2 still waiting state 1 libxl: debug: libxl_event.c:457:watchfd_callback: watch w=0x257da68 wpath=/local/domain/0/backend/vbd/8/51712/state token=3/1: event epath=/local/domain/0/backend/vbd/8/51712/state libxl: debug: libxl_event.c:596:devstate_watch_callback: backend /local/domain/0/backend/vbd/8/51712/state wanted state 2 ok libxl: debug: libxl_event.c:549:libxl__ev_xswatch_deregister: watch w=0x257da68 wpath=/local/domain/0/backend/vbd/8/51712/state token=3/1: deregister slotnum=3 libxl: debug: libxl_event.c:561:libxl__ev_xswatch_deregister: watch w=0x257da68: deregister unregistered libxl: debug: libxl_device.c:917:device_hotplug: calling hotplug script: /etc/xen/scripts/block add libxl: debug: libxl_dm.c:1142:libxl__spawn_local_dm: Spawning device-model /usr/lib/xen-4.2/bin/qemu-dm with arguments: libxl: debug: libxl_dm.c:1144:libxl__spawn_local_dm: /usr/lib/xen-4.2/bin/qemu-dm libxl: debug: libxl_dm.c:1144:libxl__spawn_local_dm: -d libxl: debug: libxl_dm.c:1144:libxl__spawn_local_dm: 8 libxl: debug: libxl_dm.c:1144:libxl__spawn_local_dm: -domain-name libxl: debug: libxl_dm.c:1144:libxl__spawn_local_dm: wxp-00-dm libxl: debug: libxl_dm.c:1144:libxl__spawn_local_dm: -vnc libxl: debug: libxl_dm.c:1144:libxl__spawn_local_dm: 0.0.0.0:0,password libxl: debug: libxl_dm.c:1144:libxl__spawn_local_dm: -M libxl: debug: libxl_dm.c:1144:libxl__spawn_local_dm: xenpv libxl: debug: libxl_event.c:512:libxl__ev_xswatch_register: watch w=0x2579908 wpath=/local/domain/0/device-model/8/state token=3/2: register slotnum=3 libxl: debug: libxl_event.c:457:watchfd_callback: watch w=0x2579908 wpath=/local/domain/0/device-model/8/state token=3/2: event epath=/local/domain/0/device-model/8/state libxl: debug: libxl_event.c:457:watchfd_callback: watch w=0x2579908 wpath=/local/domain/0/device-model/8/state token=3/2: event epath=/local/domain/0/device-model/8/state libxl: debug: libxl_event.c:549:libxl__ev_xswatch_deregister: watch w=0x2579908 wpath=/local/domain/0/device-model/8/state token=3/2: deregister slotnum=3 libxl: debug: libxl_event.c:561:libxl__ev_xswatch_deregister: watch w=0x2579908: deregister unregistered libxl: debug: libxl_event.c:512:libxl__ev_xswatch_register: watch w=0x25812e8 wpath=/local/domain/0/backend/vif/8/0/state token=3/3: register slotnum=3 libxl: debug: libxl_event.c:457:watchfd_callback: watch w=0x25812e8 wpath=/local/domain/0/backend/vif/8/0/state token=3/3: event epath=/local/domain/0/backend/vif/8/0/state libxl: debug: libxl_event.c:600:devstate_watch_callback: backend /local/domain/0/backend/vif/8/0/state wanted state 2 still waiting state 1 libxl: debug: libxl_event.c:457:watchfd_callback: watch w=0x25812e8 wpath=/local/domain/0/backend/vif/8/0/state token=3/3: event epath=/local/domain/0/backend/vif/8/0/state libxl: debug: libxl_event.c:596:devstate_watch_callback: backend /local/domain/0/backend/vif/8/0/state wanted state 2 ok libxl: debug: libxl_event.c:549:libxl__ev_xswatch_deregister: watch w=0x25812e8 wpath=/local/domain/0/backend/vif/8/0/state token=3/3: deregister slotnum=3 libxl: debug: libxl_event.c:561:libxl__ev_xswatch_deregister: watch w=0x25812e8: deregister unregistered libxl: debug: libxl_device.c:917:device_hotplug: calling hotplug script: /etc/xen/scripts/vif-bridge online libxl: debug: libxl_event.c:512:libxl__ev_xswatch_register: watch w=0x2581e78 wpath=/local/domain/0/backend/vif/7/0/state token=3/4: register slotnum=3 libxl: debug: libxl_event.c:457:watchfd_callback: watch w=0x2581e78 wpath=/local/domain/0/backend/vif/7/0/state token=3/4: event epath=/local/domain/0/backend/vif/7/0/state libxl: debug: libxl_event.c:600:devstate_watch_callback: backend /local/domain/0/backend/vif/7/0/state wanted state 2 still waiting state 1 libxl: debug: libxl_event.c:457:watchfd_callback: watch w=0x2581e78 wpath=/local/domain/0/backend/vif/7/0/state token=3/4: event epath=/local/domain/0/backend/vif/7/0/state libxl: debug: libxl_event.c:596:devstate_watch_callback: backend /local/domain/0/backend/vif/7/0/state wanted state 2 ok libxl: debug: libxl_event.c:549:libxl__ev_xswatch_deregister: watch w=0x2581e78 wpath=/local/domain/0/backend/vif/7/0/state token=3/4: deregister slotnum=3 libxl: debug: libxl_event.c:561:libxl__ev_xswatch_deregister: watch w=0x2581e78: deregister unregistered libxl: debug: libxl_device.c:917:device_hotplug: calling hotplug script: /etc/xen/scripts/vif-bridge online libxl: debug: libxl_event.c:1667:libxl__ao_progress_report: ao 0x2578f40: progress report: ignored libxl: debug: libxl_event.c:1499:libxl__ao_complete: ao 0x2578f40: complete, rc=0 libxl: debug: libxl_event.c:1471:libxl__ao__destroy: ao 0x2578f40: destroy Daemon running with PID 4294 xc: debug: hypercall buffer: total allocations:813 total releases:813 xc: debug: hypercall buffer: current allocations:0 maximum allocations:4 xc: debug: hypercall buffer: cache current size:4 xc: debug: hypercall buffer: cache hits:799 misses:4 toobig:10 Cheers, Sylvain _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Tue Feb 19 15:00:00 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 19 Feb 2013 15: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 1U7of6-0000Q3-ML; Tue, 19 Feb 2013 14:59:16 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U7of5-0000Po-2P for xen-users@lists.xen.org; Tue, 19 Feb 2013 14:59:15 +0000 Received: from [85.158.139.211:20735] by server-13.bemta-5.messagelabs.com id D3/35-06769-24393215; Tue, 19 Feb 2013 14:59:14 +0000 X-Env-Sender: s.munaut@whatever-company.com X-Msg-Ref: server-14.tower-206.messagelabs.com!1361285952!18196427!1 X-Originating-IP: [209.85.214.51] X-SpamReason: No, hits=0.3 required=7.0 tests=RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 6242 invoked from network); 19 Feb 2013 14:59:13 -0000 Received: from mail-bk0-f51.google.com (HELO mail-bk0-f51.google.com) (209.85.214.51) by server-14.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 19 Feb 2013 14:59:13 -0000 Received: by mail-bk0-f51.google.com with SMTP id ik5so3138980bkc.38 for ; Tue, 19 Feb 2013 06:59:12 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-received:date:message-id:subject:from:to :content-type:x-gm-message-state; bh=/dXT28vLdtLTqih0NL70b22a36LRsnvQedLq1TfLvmc=; b=DsJfGyVlNwE3Jq650mZ5u+VYKyJA5DSHzJ1Ky776+o5+nU1Yfih+v8F07C1SrYNUrB eqe2+lzN+nMocZqIjQ5B6b6xN2BlRQSk7mRIU1FjerXGaYOsorWECwtHb0RJXDWl1aCz dt+y0pCalfc7HG+K8vZf/Of7SX1BRRS2IleWYXDJhxfPkUHMZKxStPq2p5+kWqy2jPsO a8OJ2+uWsoWdnxIMSR7x3RtS8rdqOzqcX2UEebp2AGABMGGERRXNDUuSFCg86TvgGR0H uNjf6/d2n+/p5RXikZ3JwpV2ZM/C/0aT8wOP6mIvUavK16m5pWQdLxjROxCz7OJtuAYU S19A== MIME-Version: 1.0 X-Received: by 10.205.138.148 with SMTP id is20mr6812660bkc.45.1361285952563; Tue, 19 Feb 2013 06:59:12 -0800 (PST) Received: by 10.205.137.141 with HTTP; Tue, 19 Feb 2013 06:59:12 -0800 (PST) Date: Tue, 19 Feb 2013 15:59:12 +0100 Message-ID: From: Sylvain Munaut To: xen-users@lists.xen.org X-Gm-Message-State: ALoCoQlWq9oGnuWNeZP+xoxPVkChrT90SLc3YjDTBRK38aHrqyK9vvTsrVUZZUT4TKzLKYuoIibZ Subject: [Xen-users] Xen 4.2.x - stub domains for IO. Not working ? X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: 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 trying to use stub domains for IO for HVM domains, under Xen 4.1.2 > with xl toolstack I meant using Xen-4.2.1 ... Cheers, Sylvain _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Tue Feb 19 15:00:00 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 19 Feb 2013 15: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 1U7of6-0000Q3-ML; Tue, 19 Feb 2013 14:59:16 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U7of5-0000Po-2P for xen-users@lists.xen.org; Tue, 19 Feb 2013 14:59:15 +0000 Received: from [85.158.139.211:20735] by server-13.bemta-5.messagelabs.com id D3/35-06769-24393215; Tue, 19 Feb 2013 14:59:14 +0000 X-Env-Sender: s.munaut@whatever-company.com X-Msg-Ref: server-14.tower-206.messagelabs.com!1361285952!18196427!1 X-Originating-IP: [209.85.214.51] X-SpamReason: No, hits=0.3 required=7.0 tests=RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 6242 invoked from network); 19 Feb 2013 14:59:13 -0000 Received: from mail-bk0-f51.google.com (HELO mail-bk0-f51.google.com) (209.85.214.51) by server-14.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 19 Feb 2013 14:59:13 -0000 Received: by mail-bk0-f51.google.com with SMTP id ik5so3138980bkc.38 for ; Tue, 19 Feb 2013 06:59:12 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-received:date:message-id:subject:from:to :content-type:x-gm-message-state; bh=/dXT28vLdtLTqih0NL70b22a36LRsnvQedLq1TfLvmc=; b=DsJfGyVlNwE3Jq650mZ5u+VYKyJA5DSHzJ1Ky776+o5+nU1Yfih+v8F07C1SrYNUrB eqe2+lzN+nMocZqIjQ5B6b6xN2BlRQSk7mRIU1FjerXGaYOsorWECwtHb0RJXDWl1aCz dt+y0pCalfc7HG+K8vZf/Of7SX1BRRS2IleWYXDJhxfPkUHMZKxStPq2p5+kWqy2jPsO a8OJ2+uWsoWdnxIMSR7x3RtS8rdqOzqcX2UEebp2AGABMGGERRXNDUuSFCg86TvgGR0H uNjf6/d2n+/p5RXikZ3JwpV2ZM/C/0aT8wOP6mIvUavK16m5pWQdLxjROxCz7OJtuAYU S19A== MIME-Version: 1.0 X-Received: by 10.205.138.148 with SMTP id is20mr6812660bkc.45.1361285952563; Tue, 19 Feb 2013 06:59:12 -0800 (PST) Received: by 10.205.137.141 with HTTP; Tue, 19 Feb 2013 06:59:12 -0800 (PST) Date: Tue, 19 Feb 2013 15:59:12 +0100 Message-ID: From: Sylvain Munaut To: xen-users@lists.xen.org X-Gm-Message-State: ALoCoQlWq9oGnuWNeZP+xoxPVkChrT90SLc3YjDTBRK38aHrqyK9vvTsrVUZZUT4TKzLKYuoIibZ Subject: [Xen-users] Xen 4.2.x - stub domains for IO. Not working ? X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: 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 trying to use stub domains for IO for HVM domains, under Xen 4.1.2 > with xl toolstack I meant using Xen-4.2.1 ... Cheers, Sylvain _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Tue Feb 19 15:02:35 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 19 Feb 2013 15:02: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 1U7ohe-0000nL-H2; Tue, 19 Feb 2013 15:01:54 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U7ohd-0000n5-23 for xen-users@lists.xen.org; Tue, 19 Feb 2013 15:01:53 +0000 Received: from [85.158.143.99:46373] by server-3.bemta-4.messagelabs.com id 39/1E-08920-0E393215; Tue, 19 Feb 2013 15:01:52 +0000 X-Env-Sender: Ian.Campbell@citrix.com X-Msg-Ref: server-12.tower-216.messagelabs.com!1361286111!22952628!1 X-Originating-IP: [46.33.159.39] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNDYuMzMuMTU5LjM5ID0+IDIzNTM5\n X-StarScan-Received: X-StarScan-Version: 6.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 21120 invoked from network); 19 Feb 2013 15:01:51 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (46.33.159.39) by server-12.tower-216.messagelabs.com with RC4-SHA encrypted SMTP; 19 Feb 2013 15:01:51 -0000 X-IronPort-AV: E=Sophos;i="4.84,696,1355097600"; d="scan'208";a="1613051" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 19 Feb 2013 15:01:51 +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.297.1; Tue, 19 Feb 2013 15:01:51 +0000 Message-ID: <1361286109.1051.119.camel@zakaz.uk.xensource.com> From: Ian Campbell To: Sylvain Munaut Date: Tue, 19 Feb 2013 15:01:49 +0000 In-Reply-To: References: Organization: Citrix Systems, Inc. X-Mailer: Evolution 3.4.4-1 MIME-Version: 1.0 Cc: "xen-users@lists.xen.org" Subject: Re: [Xen-users] Xen 4.1.2 - stub domains for IO. Not working ? X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: 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, 2013-02-19 at 14:58 +0000, Sylvain Munaut wrote: > Hi, > > I'm trying to use stub domains for IO for HVM domains, under Xen 4.1.2 > with xl toolstack > > The domain works fine with either qemu-xen-traditional or qemu > upstream, but I'd like to try stub domains. > > If I understand the doc correctly just adding > "device_model_stubdomain_override = 1" to the config should do the > trick. NB this only currently works with qemu-xen-trad, not the upstream version. > > However doing that doesn't really work. > > - qemu-dm is still started in the dom0 which AFAIU shouldn't be the case. This is normal, since the qemu-dm in dom0 provides some PV services (e.g. frame buffer backend) to the stubdomain. > - There is a xxx-dm domain that starts so that's a good sign, however > they both stay stuck like : > > wxp-00 7 1531 1 ------ 0.0 > wxp-00-dm 8 32 1 ---sc- 0.0 The 'c' in the status indicates that the stub domain has crashed. There may be a clue as to why in the Xen console log or you may find something use on the stubdom console, I think you can "xl console wxp-00-dm" to see that, or you can enable console logging as described in http://wiki.xen.org/wiki/Reporting_Bugs_against_Xen#Guest_console_logs Ian. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Tue Feb 19 15:02:35 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 19 Feb 2013 15:02: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 1U7ohe-0000nL-H2; Tue, 19 Feb 2013 15:01:54 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U7ohd-0000n5-23 for xen-users@lists.xen.org; Tue, 19 Feb 2013 15:01:53 +0000 Received: from [85.158.143.99:46373] by server-3.bemta-4.messagelabs.com id 39/1E-08920-0E393215; Tue, 19 Feb 2013 15:01:52 +0000 X-Env-Sender: Ian.Campbell@citrix.com X-Msg-Ref: server-12.tower-216.messagelabs.com!1361286111!22952628!1 X-Originating-IP: [46.33.159.39] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNDYuMzMuMTU5LjM5ID0+IDIzNTM5\n X-StarScan-Received: X-StarScan-Version: 6.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 21120 invoked from network); 19 Feb 2013 15:01:51 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (46.33.159.39) by server-12.tower-216.messagelabs.com with RC4-SHA encrypted SMTP; 19 Feb 2013 15:01:51 -0000 X-IronPort-AV: E=Sophos;i="4.84,696,1355097600"; d="scan'208";a="1613051" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 19 Feb 2013 15:01:51 +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.297.1; Tue, 19 Feb 2013 15:01:51 +0000 Message-ID: <1361286109.1051.119.camel@zakaz.uk.xensource.com> From: Ian Campbell To: Sylvain Munaut Date: Tue, 19 Feb 2013 15:01:49 +0000 In-Reply-To: References: Organization: Citrix Systems, Inc. X-Mailer: Evolution 3.4.4-1 MIME-Version: 1.0 Cc: "xen-users@lists.xen.org" Subject: Re: [Xen-users] Xen 4.1.2 - stub domains for IO. Not working ? X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: 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, 2013-02-19 at 14:58 +0000, Sylvain Munaut wrote: > Hi, > > I'm trying to use stub domains for IO for HVM domains, under Xen 4.1.2 > with xl toolstack > > The domain works fine with either qemu-xen-traditional or qemu > upstream, but I'd like to try stub domains. > > If I understand the doc correctly just adding > "device_model_stubdomain_override = 1" to the config should do the > trick. NB this only currently works with qemu-xen-trad, not the upstream version. > > However doing that doesn't really work. > > - qemu-dm is still started in the dom0 which AFAIU shouldn't be the case. This is normal, since the qemu-dm in dom0 provides some PV services (e.g. frame buffer backend) to the stubdomain. > - There is a xxx-dm domain that starts so that's a good sign, however > they both stay stuck like : > > wxp-00 7 1531 1 ------ 0.0 > wxp-00-dm 8 32 1 ---sc- 0.0 The 'c' in the status indicates that the stub domain has crashed. There may be a clue as to why in the Xen console log or you may find something use on the stubdom console, I think you can "xl console wxp-00-dm" to see that, or you can enable console logging as described in http://wiki.xen.org/wiki/Reporting_Bugs_against_Xen#Guest_console_logs Ian. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Tue Feb 19 15:30:24 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 19 Feb 2013 15:30: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 1U7p8d-0003SA-2P; Tue, 19 Feb 2013 15:29:47 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U7p8b-0003Rw-Eq for xen-users@lists.xen.org; Tue, 19 Feb 2013 15:29:45 +0000 Received: from [85.158.143.99:30420] by server-1.bemta-4.messagelabs.com id 19/3C-08839-86A93215; Tue, 19 Feb 2013 15:29:44 +0000 X-Env-Sender: s.munaut@whatever-company.com X-Msg-Ref: server-16.tower-216.messagelabs.com!1361287746!16767112!1 X-Originating-IP: [209.85.214.53] X-SpamReason: No, hits=0.3 required=7.0 tests=RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 419 invoked from network); 19 Feb 2013 15:29:07 -0000 Received: from mail-bk0-f53.google.com (HELO mail-bk0-f53.google.com) (209.85.214.53) by server-16.tower-216.messagelabs.com with RC4-SHA encrypted SMTP; 19 Feb 2013 15:29:07 -0000 Received: by mail-bk0-f53.google.com with SMTP id j10so3076229bkw.40 for ; Tue, 19 Feb 2013 07:29:06 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type:x-gm-message-state; bh=iTj3s5PpGS24OcpJ3bG7txD5llBPeRwHr/xgseAv5yI=; b=X7quVpiRGwKhzgcfTLesL6EfPSdExubfdDsizrDxGGpC6JfpWOrqJOBEofQPtHHrxc rsQeRkM/fARkOyCGdJxEgSVIzADl1kd9m9Hki9E7+JlXMbA2vKaGhwqQLM0vspXyiOQj 956LC46Ay7nhNklFcQW0TJA8DN9LuSP6QpeP2DL/97119IhqG207JzGFLMiyPo/Hh7RT AxNGaH3u27vTj58CBdLOC4k27vdY8KIVuaIhJvz9kFgcEXdGCJ1LnZGctn+O4OSVY7YM WeVTEqEjWVD4rUzKzd6wT+awbtXsIu1ydreJD9wn42KOLuzIesad0T7U6axeYXcdhmv6 Uj+g== MIME-Version: 1.0 X-Received: by 10.205.138.148 with SMTP id is20mr6882194bkc.45.1361287746074; Tue, 19 Feb 2013 07:29:06 -0800 (PST) Received: by 10.205.137.141 with HTTP; Tue, 19 Feb 2013 07:29:05 -0800 (PST) In-Reply-To: <1361286109.1051.119.camel@zakaz.uk.xensource.com> References: <1361286109.1051.119.camel@zakaz.uk.xensource.com> Date: Tue, 19 Feb 2013 16:29:05 +0100 Message-ID: From: Sylvain Munaut To: Ian Campbell X-Gm-Message-State: ALoCoQl7UpRgyW2L4Be4ZTvu4gk1FD7qV73BbVn9Si94j2oAzrCHB1eR1RBPVpH2vpiWxmJr0aej Cc: "xen-users@lists.xen.org" Subject: Re: [Xen-users] Xen 4.1.2 - stub domains for IO. Not working ? X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: 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 Ian, > NB this only currently works with qemu-xen-trad, not the upstream > version. Ok, not a problem. I have both installed and working in this setup. >> - qemu-dm is still started in the dom0 which AFAIU shouldn't be the case. > > This is normal, since the qemu-dm in dom0 provides some PV services > (e.g. frame buffer backend) to the stubdomain. Ah ok, true I didn't think of that. > The 'c' in the status indicates that the stub domain has crashed. > > There may be a clue as to why in the Xen console log or you may find > something use on the stubdom console, I think you can "xl console > wxp-00-dm" to see that, or you can enable console logging as described > in > http://wiki.xen.org/wiki/Reporting_Bugs_against_Xen#Guest_console_logs I enabled console logging and checked that it worked using a PV domain. Unfortunately the main domain only creates and empty log file and the -dm domain doesn't create anything at all. I tried attaching to console, but that didn't help There is also no errors reported in the 'xl dmesg' output or the linux 'dmesg' output either. Cheers, Sylvain _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Tue Feb 19 15:30:24 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 19 Feb 2013 15:30: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 1U7p8d-0003SA-2P; Tue, 19 Feb 2013 15:29:47 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U7p8b-0003Rw-Eq for xen-users@lists.xen.org; Tue, 19 Feb 2013 15:29:45 +0000 Received: from [85.158.143.99:30420] by server-1.bemta-4.messagelabs.com id 19/3C-08839-86A93215; Tue, 19 Feb 2013 15:29:44 +0000 X-Env-Sender: s.munaut@whatever-company.com X-Msg-Ref: server-16.tower-216.messagelabs.com!1361287746!16767112!1 X-Originating-IP: [209.85.214.53] X-SpamReason: No, hits=0.3 required=7.0 tests=RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 419 invoked from network); 19 Feb 2013 15:29:07 -0000 Received: from mail-bk0-f53.google.com (HELO mail-bk0-f53.google.com) (209.85.214.53) by server-16.tower-216.messagelabs.com with RC4-SHA encrypted SMTP; 19 Feb 2013 15:29:07 -0000 Received: by mail-bk0-f53.google.com with SMTP id j10so3076229bkw.40 for ; Tue, 19 Feb 2013 07:29:06 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type:x-gm-message-state; bh=iTj3s5PpGS24OcpJ3bG7txD5llBPeRwHr/xgseAv5yI=; b=X7quVpiRGwKhzgcfTLesL6EfPSdExubfdDsizrDxGGpC6JfpWOrqJOBEofQPtHHrxc rsQeRkM/fARkOyCGdJxEgSVIzADl1kd9m9Hki9E7+JlXMbA2vKaGhwqQLM0vspXyiOQj 956LC46Ay7nhNklFcQW0TJA8DN9LuSP6QpeP2DL/97119IhqG207JzGFLMiyPo/Hh7RT AxNGaH3u27vTj58CBdLOC4k27vdY8KIVuaIhJvz9kFgcEXdGCJ1LnZGctn+O4OSVY7YM WeVTEqEjWVD4rUzKzd6wT+awbtXsIu1ydreJD9wn42KOLuzIesad0T7U6axeYXcdhmv6 Uj+g== MIME-Version: 1.0 X-Received: by 10.205.138.148 with SMTP id is20mr6882194bkc.45.1361287746074; Tue, 19 Feb 2013 07:29:06 -0800 (PST) Received: by 10.205.137.141 with HTTP; Tue, 19 Feb 2013 07:29:05 -0800 (PST) In-Reply-To: <1361286109.1051.119.camel@zakaz.uk.xensource.com> References: <1361286109.1051.119.camel@zakaz.uk.xensource.com> Date: Tue, 19 Feb 2013 16:29:05 +0100 Message-ID: From: Sylvain Munaut To: Ian Campbell X-Gm-Message-State: ALoCoQl7UpRgyW2L4Be4ZTvu4gk1FD7qV73BbVn9Si94j2oAzrCHB1eR1RBPVpH2vpiWxmJr0aej Cc: "xen-users@lists.xen.org" Subject: Re: [Xen-users] Xen 4.1.2 - stub domains for IO. Not working ? X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: 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 Ian, > NB this only currently works with qemu-xen-trad, not the upstream > version. Ok, not a problem. I have both installed and working in this setup. >> - qemu-dm is still started in the dom0 which AFAIU shouldn't be the case. > > This is normal, since the qemu-dm in dom0 provides some PV services > (e.g. frame buffer backend) to the stubdomain. Ah ok, true I didn't think of that. > The 'c' in the status indicates that the stub domain has crashed. > > There may be a clue as to why in the Xen console log or you may find > something use on the stubdom console, I think you can "xl console > wxp-00-dm" to see that, or you can enable console logging as described > in > http://wiki.xen.org/wiki/Reporting_Bugs_against_Xen#Guest_console_logs I enabled console logging and checked that it worked using a PV domain. Unfortunately the main domain only creates and empty log file and the -dm domain doesn't create anything at all. I tried attaching to console, but that didn't help There is also no errors reported in the 'xl dmesg' output or the linux 'dmesg' output either. Cheers, Sylvain _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Tue Feb 19 20:27:55 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 19 Feb 2013 20:27: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 1U7tlm-0002m2-FC; Tue, 19 Feb 2013 20:26:30 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U7tlk-0002ln-N8; Tue, 19 Feb 2013 20:26:28 +0000 Received: from [85.158.143.35:58052] by server-3.bemta-4.messagelabs.com id F8/77-08920-3FFD3215; Tue, 19 Feb 2013 20:26:27 +0000 X-Env-Sender: pasik@iki.fi X-Msg-Ref: server-6.tower-21.messagelabs.com!1361305582!15616319!1 X-Originating-IP: [192.89.123.25] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogMTkyLjg5LjEyMy4yNSA9PiA0Njg3NjA=\n X-StarScan-Received: X-StarScan-Version: 6.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 10966 invoked from network); 19 Feb 2013 20:26:23 -0000 Received: from smtp.tele.fi (HELO smtp.tele.fi) (192.89.123.25) by server-6.tower-21.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 19 Feb 2013 20:26:23 -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 4EA4D104D; Tue, 19 Feb 2013 22:26:22 +0200 (EET) Received: by ydin.reaktio.net (Postfix, from userid 1001) id 0DBDDF4017; Tue, 19 Feb 2013 22:26:22 +0200 (EET) Date: Tue, 19 Feb 2013 22:26:21 +0200 From: Pasi =?iso-8859-1?Q?K=E4rkk=E4inen?= To: xen-devel@lists.xen.org Message-ID: <20130219202621.GF8912@reaktio.net> MIME-Version: 1.0 Content-Disposition: inline User-Agent: Mutt/1.5.20 (2009-06-14) Cc: xen-users@lists.xen.org Subject: [Xen-users] Xen SR-IOV 10 Gbit/sec NIC Virtual Function PCI passthru tutorial on EL5 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 Hello, I wrote a tutorial about doing Xen SR-IOV Virtual Function (VF) PCI passthru with Intel 10 Gbit/sec ixgbe NICs with RHEL5/CentOS5 Xen dom0. The tutorial shows how to use the SR-IOV VFs on the following VMs: - RHEL5/CentOS5 PV domU. - RHEL5/CentOS5 HVM guest. - RHEL6/CentOS6 HVM guest. http://wiki.xen.org/wiki/RHEL5_CentOS5_Xen_Intel_SR-IOV_NIC_Virtual_Function_VF_PCI_Passthru_Tutorial I'm planning to create another tutorial in the future using more recent dom0 distro, most probably CentOS 6 Xen dom0. Hopefully this is useful for people :) -- Pasi _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Tue Feb 19 20:27:55 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 19 Feb 2013 20:27: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 1U7tlm-0002m2-FC; Tue, 19 Feb 2013 20:26:30 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U7tlk-0002ln-N8; Tue, 19 Feb 2013 20:26:28 +0000 Received: from [85.158.143.35:58052] by server-3.bemta-4.messagelabs.com id F8/77-08920-3FFD3215; Tue, 19 Feb 2013 20:26:27 +0000 X-Env-Sender: pasik@iki.fi X-Msg-Ref: server-6.tower-21.messagelabs.com!1361305582!15616319!1 X-Originating-IP: [192.89.123.25] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogMTkyLjg5LjEyMy4yNSA9PiA0Njg3NjA=\n X-StarScan-Received: X-StarScan-Version: 6.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 10966 invoked from network); 19 Feb 2013 20:26:23 -0000 Received: from smtp.tele.fi (HELO smtp.tele.fi) (192.89.123.25) by server-6.tower-21.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 19 Feb 2013 20:26:23 -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 4EA4D104D; Tue, 19 Feb 2013 22:26:22 +0200 (EET) Received: by ydin.reaktio.net (Postfix, from userid 1001) id 0DBDDF4017; Tue, 19 Feb 2013 22:26:22 +0200 (EET) Date: Tue, 19 Feb 2013 22:26:21 +0200 From: Pasi =?iso-8859-1?Q?K=E4rkk=E4inen?= To: xen-devel@lists.xen.org Message-ID: <20130219202621.GF8912@reaktio.net> MIME-Version: 1.0 Content-Disposition: inline User-Agent: Mutt/1.5.20 (2009-06-14) Cc: xen-users@lists.xen.org Subject: [Xen-users] Xen SR-IOV 10 Gbit/sec NIC Virtual Function PCI passthru tutorial on EL5 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 Hello, I wrote a tutorial about doing Xen SR-IOV Virtual Function (VF) PCI passthru with Intel 10 Gbit/sec ixgbe NICs with RHEL5/CentOS5 Xen dom0. The tutorial shows how to use the SR-IOV VFs on the following VMs: - RHEL5/CentOS5 PV domU. - RHEL5/CentOS5 HVM guest. - RHEL6/CentOS6 HVM guest. http://wiki.xen.org/wiki/RHEL5_CentOS5_Xen_Intel_SR-IOV_NIC_Virtual_Function_VF_PCI_Passthru_Tutorial I'm planning to create another tutorial in the future using more recent dom0 distro, most probably CentOS 6 Xen dom0. Hopefully this is useful for people :) -- Pasi _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Wed Feb 20 09:19:01 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 20 Feb 2013 09: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 1U85ny-00082v-F1; Wed, 20 Feb 2013 09:17:34 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U85nw-00082i-E9 for xen-users@lists.xen.org; Wed, 20 Feb 2013 09:17:32 +0000 Received: from [193.109.254.147:61714] by server-9.bemta-14.messagelabs.com id 75/9F-30867-BA494215; Wed, 20 Feb 2013 09:17:31 +0000 X-Env-Sender: Ian.Campbell@citrix.com X-Msg-Ref: server-14.tower-27.messagelabs.com!1361351799!1772422!1 X-Originating-IP: [46.33.159.39] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNDYuMzMuMTU5LjM5ID0+IDIyODQ4\n X-StarScan-Received: X-StarScan-Version: 6.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 26034 invoked from network); 20 Feb 2013 09:16:39 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (46.33.159.39) by server-14.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 20 Feb 2013 09:16:39 -0000 X-IronPort-AV: E=Sophos;i="4.84,699,1355097600"; d="scan'208";a="1641973" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 20 Feb 2013 09:16: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.297.1; Wed, 20 Feb 2013 09:16:39 +0000 Message-ID: <1361351798.1051.142.camel@zakaz.uk.xensource.com> From: Ian Campbell To: Sylvain Munaut Date: Wed, 20 Feb 2013 09:16:38 +0000 In-Reply-To: References: <1361286109.1051.119.camel@zakaz.uk.xensource.com> Organization: Citrix Systems, Inc. X-Mailer: Evolution 3.4.4-1 MIME-Version: 1.0 Cc: "xen-users@lists.xen.org" Subject: Re: [Xen-users] Xen 4.1.2 - stub domains for IO. Not working ? X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: 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, 2013-02-19 at 15:29 +0000, Sylvain Munaut wrote: > > The 'c' in the status indicates that the stub domain has crashed. > > > > There may be a clue as to why in the Xen console log or you may find > > something use on the stubdom console, I think you can "xl console > > wxp-00-dm" to see that, or you can enable console logging as described > > in > > http://wiki.xen.org/wiki/Reporting_Bugs_against_Xen#Guest_console_logs > > I enabled console logging and checked that it worked using a PV domain. > > Unfortunately the main domain only creates and empty log file and the > -dm domain doesn't create anything at all. > I tried attaching to console, but that didn't help > > There is also no errors reported in the 'xl dmesg' output or the linux > 'dmesg' output either. Odd for the crash to be totally silent in all the logs. You may need "loglvl=all guest_loglvl=all" on your hypervisor command line. Failing that rebuilding the hypervisor with "debug=y" (passed on the make command line) might expose something useful. Lastly you could try running /usr/lib*/xen/bin/xenctx on the dm domain, which might give you an IP address which can be related to the kernel binary image with gdb or addr2line etc. Ian. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Wed Feb 20 09:19:01 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 20 Feb 2013 09: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 1U85ny-00082v-F1; Wed, 20 Feb 2013 09:17:34 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U85nw-00082i-E9 for xen-users@lists.xen.org; Wed, 20 Feb 2013 09:17:32 +0000 Received: from [193.109.254.147:61714] by server-9.bemta-14.messagelabs.com id 75/9F-30867-BA494215; Wed, 20 Feb 2013 09:17:31 +0000 X-Env-Sender: Ian.Campbell@citrix.com X-Msg-Ref: server-14.tower-27.messagelabs.com!1361351799!1772422!1 X-Originating-IP: [46.33.159.39] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNDYuMzMuMTU5LjM5ID0+IDIyODQ4\n X-StarScan-Received: X-StarScan-Version: 6.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 26034 invoked from network); 20 Feb 2013 09:16:39 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (46.33.159.39) by server-14.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 20 Feb 2013 09:16:39 -0000 X-IronPort-AV: E=Sophos;i="4.84,699,1355097600"; d="scan'208";a="1641973" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 20 Feb 2013 09:16: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.297.1; Wed, 20 Feb 2013 09:16:39 +0000 Message-ID: <1361351798.1051.142.camel@zakaz.uk.xensource.com> From: Ian Campbell To: Sylvain Munaut Date: Wed, 20 Feb 2013 09:16:38 +0000 In-Reply-To: References: <1361286109.1051.119.camel@zakaz.uk.xensource.com> Organization: Citrix Systems, Inc. X-Mailer: Evolution 3.4.4-1 MIME-Version: 1.0 Cc: "xen-users@lists.xen.org" Subject: Re: [Xen-users] Xen 4.1.2 - stub domains for IO. Not working ? X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: 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, 2013-02-19 at 15:29 +0000, Sylvain Munaut wrote: > > The 'c' in the status indicates that the stub domain has crashed. > > > > There may be a clue as to why in the Xen console log or you may find > > something use on the stubdom console, I think you can "xl console > > wxp-00-dm" to see that, or you can enable console logging as described > > in > > http://wiki.xen.org/wiki/Reporting_Bugs_against_Xen#Guest_console_logs > > I enabled console logging and checked that it worked using a PV domain. > > Unfortunately the main domain only creates and empty log file and the > -dm domain doesn't create anything at all. > I tried attaching to console, but that didn't help > > There is also no errors reported in the 'xl dmesg' output or the linux > 'dmesg' output either. Odd for the crash to be totally silent in all the logs. You may need "loglvl=all guest_loglvl=all" on your hypervisor command line. Failing that rebuilding the hypervisor with "debug=y" (passed on the make command line) might expose something useful. Lastly you could try running /usr/lib*/xen/bin/xenctx on the dm domain, which might give you an IP address which can be related to the kernel binary image with gdb or addr2line etc. Ian. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Wed Feb 20 10:49:33 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 20 Feb 2013 10:49: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 1U87Dc-0001RU-Gd; Wed, 20 Feb 2013 10:48:08 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U87Db-0001RM-Ev for xen-users@lists.xen.org; Wed, 20 Feb 2013 10:48:07 +0000 Received: from [85.158.139.211:12404] by server-15.bemta-5.messagelabs.com id 85/6D-18914-6E9A4215; Wed, 20 Feb 2013 10:48:06 +0000 X-Env-Sender: mliebherr99@googlemail.com X-Msg-Ref: server-16.tower-206.messagelabs.com!1361357232!18415837!1 X-Originating-IP: [74.125.82.181] X-SpamReason: No, hits=0.6 required=7.0 tests=MAILTO_TO_SPAM_ADDR, RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 28507 invoked from network); 20 Feb 2013 10:47:13 -0000 Received: from mail-we0-f181.google.com (HELO mail-we0-f181.google.com) (74.125.82.181) by server-16.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 20 Feb 2013 10:47:13 -0000 Received: by mail-we0-f181.google.com with SMTP id t44so6400100wey.12 for ; Wed, 20 Feb 2013 02:47:12 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=sJh3MJf31aAfmJ8qfeM5kvFwG0ID/4F+pSnysEtmSt8=; b=WZXbWvRXNOVLtSUb+pgrw061y7LvQW7Kc1fjXxDqh/JEW9rPvwVJtpyUn3A4S6M62y 9uI3T1qou4m4iZtWPr5urp0E0p9LkuuOtIZQLFwtuIMAShGFDbBkP0i7wWw1kUBnMIt8 N17w62nhnZDRcrxen4yOdnCAKLEhmzrfIdtuEWp8/d0wxOQECEYjwDay2JDNO7wszs9/ SgGxc+DjuHis9Lw32/Q09QFDRvRJGxVcAY3BdkvPNYcvliW+VH38TFt5lydMXzZYhqYN VlZZ8NClNaefrpWvlv209jVcnnqPiw1NQIrBfjTZDKxpy4neTW20out/HgeRqCsgjT1q qdgw== MIME-Version: 1.0 X-Received: by 10.194.108.101 with SMTP id hj5mr32694319wjb.6.1361357230208; Wed, 20 Feb 2013 02:47:10 -0800 (PST) Received: by 10.227.100.194 with HTTP; Wed, 20 Feb 2013 02:47:10 -0800 (PST) In-Reply-To: References: Date: Wed, 20 Feb 2013 11:47:10 +0100 Message-ID: From: ml ml To: T Cc: xen-users@lists.xen.org Subject: Re: [Xen-users] Kernel Error with Debian Squeeze, DRBD, 3.2.0-0.bpo.4-amd64 and Xen4.0 X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org That seems to fix it. Thanks! Is this an official bug or feature? On Mon, Feb 18, 2013 at 3:47 PM, T wrote: >> From: ml ml >> Date: 2013/2/18 >> Subject: [Xen-users] Kernel Error with Debian Squeeze, DRBD, >> 3.2.0-0.bpo.4-amd64 and Xen4.0 >> To: xen-users@lists.xen.org >> >> >> Hello List, >> >> i am running Debian Squeeze and i installed DRBD, 3.2.0-0.bpo.4-amd64 >> and Xen4.0 from the Backports. >> >> Sometimes i get such ugly Kernel message: >> [257318.441757] BUG: unable to handle kernel paging request at ffff880025f19000 >> > > Check if your cpu has xsaveopt instruction: > http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=695658 > > -- > T _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Wed Feb 20 10:49:33 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 20 Feb 2013 10:49: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 1U87Dc-0001RU-Gd; Wed, 20 Feb 2013 10:48:08 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U87Db-0001RM-Ev for xen-users@lists.xen.org; Wed, 20 Feb 2013 10:48:07 +0000 Received: from [85.158.139.211:12404] by server-15.bemta-5.messagelabs.com id 85/6D-18914-6E9A4215; Wed, 20 Feb 2013 10:48:06 +0000 X-Env-Sender: mliebherr99@googlemail.com X-Msg-Ref: server-16.tower-206.messagelabs.com!1361357232!18415837!1 X-Originating-IP: [74.125.82.181] X-SpamReason: No, hits=0.6 required=7.0 tests=MAILTO_TO_SPAM_ADDR, RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 28507 invoked from network); 20 Feb 2013 10:47:13 -0000 Received: from mail-we0-f181.google.com (HELO mail-we0-f181.google.com) (74.125.82.181) by server-16.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 20 Feb 2013 10:47:13 -0000 Received: by mail-we0-f181.google.com with SMTP id t44so6400100wey.12 for ; Wed, 20 Feb 2013 02:47:12 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=sJh3MJf31aAfmJ8qfeM5kvFwG0ID/4F+pSnysEtmSt8=; b=WZXbWvRXNOVLtSUb+pgrw061y7LvQW7Kc1fjXxDqh/JEW9rPvwVJtpyUn3A4S6M62y 9uI3T1qou4m4iZtWPr5urp0E0p9LkuuOtIZQLFwtuIMAShGFDbBkP0i7wWw1kUBnMIt8 N17w62nhnZDRcrxen4yOdnCAKLEhmzrfIdtuEWp8/d0wxOQECEYjwDay2JDNO7wszs9/ SgGxc+DjuHis9Lw32/Q09QFDRvRJGxVcAY3BdkvPNYcvliW+VH38TFt5lydMXzZYhqYN VlZZ8NClNaefrpWvlv209jVcnnqPiw1NQIrBfjTZDKxpy4neTW20out/HgeRqCsgjT1q qdgw== MIME-Version: 1.0 X-Received: by 10.194.108.101 with SMTP id hj5mr32694319wjb.6.1361357230208; Wed, 20 Feb 2013 02:47:10 -0800 (PST) Received: by 10.227.100.194 with HTTP; Wed, 20 Feb 2013 02:47:10 -0800 (PST) In-Reply-To: References: Date: Wed, 20 Feb 2013 11:47:10 +0100 Message-ID: From: ml ml To: T Cc: xen-users@lists.xen.org Subject: Re: [Xen-users] Kernel Error with Debian Squeeze, DRBD, 3.2.0-0.bpo.4-amd64 and Xen4.0 X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org That seems to fix it. Thanks! Is this an official bug or feature? On Mon, Feb 18, 2013 at 3:47 PM, T wrote: >> From: ml ml >> Date: 2013/2/18 >> Subject: [Xen-users] Kernel Error with Debian Squeeze, DRBD, >> 3.2.0-0.bpo.4-amd64 and Xen4.0 >> To: xen-users@lists.xen.org >> >> >> Hello List, >> >> i am running Debian Squeeze and i installed DRBD, 3.2.0-0.bpo.4-amd64 >> and Xen4.0 from the Backports. >> >> Sometimes i get such ugly Kernel message: >> [257318.441757] BUG: unable to handle kernel paging request at ffff880025f19000 >> > > Check if your cpu has xsaveopt instruction: > http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=695658 > > -- > T _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Wed Feb 20 11:59:09 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 20 Feb 2013 11:59: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 1U88JI-0003zj-Fe; Wed, 20 Feb 2013 11:58:04 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U88JG-0003zd-KB for xen-users@lists.xen.org; Wed, 20 Feb 2013 11:58:03 +0000 Received: from [85.158.137.99:3397] by server-4.bemta-3.messagelabs.com id EE/6D-17521-94AB4215; Wed, 20 Feb 2013 11:58:01 +0000 X-Env-Sender: agya.naila@gmail.com X-Msg-Ref: server-10.tower-217.messagelabs.com!1361361469!17026131!1 X-Originating-IP: [74.125.82.53] 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.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 11740 invoked from network); 20 Feb 2013 11:57:53 -0000 Received: from mail-wg0-f53.google.com (HELO mail-wg0-f53.google.com) (74.125.82.53) by server-10.tower-217.messagelabs.com with RC4-SHA encrypted SMTP; 20 Feb 2013 11:57:53 -0000 Received: by mail-wg0-f53.google.com with SMTP id fn15so6558068wgb.32 for ; Wed, 20 Feb 2013 03:57:18 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=03zLrLTGaCKJvdH2GS52Ia1G9A9ZwwYFuSuS7JlsROo=; b=dQLBnz//pNnqUpBL8TsesFf+C1ooLUthgzbbF7HbvHjhIaNvM/7TKRLDvBu72X3zhJ lw5II2Cp7SG/COxvUnw28X7ZKf2qlz/6ezJUS9cTFcyB+1zXKDRc1WyOSy/eERIT0rfn IT0Jjdq/DbKhZ/XgCc85DI2M/4n+DudC00jfRFUVnj7bK2AFbk61bJAHaTVcD9ffpYci j/r8jcdcoGSSnpJKcoGCJp8s6w3l7RZ7W7NpUMjMzhdBc7b6BuvG+/wM+aDxOsmsBeqC s3azuAmJ38yK7hh0K3xMToHRoJrdczNcg/d5GFmAdSoMwt8osX+lNawajaovuAbmUlNo N1mA== MIME-Version: 1.0 X-Received: by 10.180.8.197 with SMTP id t5mr33524227wia.27.1361361438696; Wed, 20 Feb 2013 03:57:18 -0800 (PST) Received: by 10.216.236.13 with HTTP; Wed, 20 Feb 2013 03:57:18 -0800 (PST) In-Reply-To: References: Date: Wed, 20 Feb 2013 12:57:18 +0100 Message-ID: From: agya naila To: Andrew Eross Cc: rshriram@cs.ubc.ca, "xen-users@lists.xen.org" Subject: Re: [Xen-users] Remus dom0 network buffering X-BeenThere: xen-users@lists.xen.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="===============6431603293988160045==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============6431603293988160045== Content-Type: multipart/alternative; boundary=f46d04428240f6e5c904d626a801 --f46d04428240f6e5c904d626a801 Content-Type: text/plain; charset=ISO-8859-1 Hello All, I am trying this patch on my machine Ubuntu 12.04 AMD64 both for Dom0 and DomU with Xen 4.2.2-pre compiling from sources also DRBD 8.3.11 but unfortunately it seem didn't work since I still got the message WARNING: suspend event channel unavailable, falling back to slow xenstore signalling. Regards, Agya On Tue, Feb 19, 2013 at 12:39 PM, Andrew Eross wrote: > Hi all, > > To close off on this, Shriram's patch worked great, thank you. > > So Ubuntu 12.10's standard generic kernel is now working fine as a dom0 > for Remus with Xen 4.1.4 (with the patch from this thread). > > I wrote up my full install instructions here: > > http://wiki.xen.org/wiki/Install_Xen_4.1.4_with_Remus_and_DRBD_on_Ubuntu_12.10 > > I also took a shot at a number of updates to: > http://wiki.xen.org/wiki/Remus > > And added these pages: > http://wiki.xen.org/wiki/Remus_PV_domU_requirements > http://wiki.xen.org/wiki/Remus_dom0_requirements > > Feedback very welcome, a lot of that information was a bit old, so I did > my best. > > Cheers, > Andrew > > > On Mon, Feb 18, 2013 at 8:26 PM, Shriram Rajagopalan wrote: > >> ah darn. Yes, the 3.5 kernel has sch_plug in it. Unfortunately, the >> technique to initialize the sch_plug module is bit >> different with the module thats already mainline. You ll have to patch >> the qdisc.py python module. I ll submit the >> patch to xen devel soon. >> Mean while, can you try the patch below and see if it works ? >> >> Secondly, you said you were writing a blog about how you set it up. >> One of the remus users created a wiki >> remusha.wikidot.com, which has a whole tutorial on how to setup remus >> with Debian Squeeze. I have been under fire >> lately for a host of remus issues. It would be great if you could post >> your experiences on the wiki too. >> (http://remusha.wikidot.com/system:join) >> >> thanks >> shriram >> >> --- >> diff -r 6435f1edf24e tools/python/xen/remus/qdisc.py >> --- a/tools/python/xen/remus/qdisc.py Tue Jul 17 19:23:30 2012 -0400 >> +++ b/tools/python/xen/remus/qdisc.py Mon Feb 18 18:25:22 2013 -0500 >> @@ -1,6 +1,9 @@ >> import socket, struct >> >> import netlink >> +import platform >> + >> +kernelversion = platform.platform(terse=True).split("-")[1].split(".") >> >> qdisc_kinds = {} >> >> @@ -150,9 +153,14 @@ >> TC_PLUG_RELEASE = 1 >> >> class PlugQdisc(Qdisc): >> - fmt = 'I' >> >> def __init__(self, qdict=None): >> + if int(kernelversion[0]) >= 3 and int(kernelversion[1]) >= 4: >> + self.fmt = 'iI' >> + self.limit = 10000 >> + else: >> + self.fmt = 'I' >> + >> if not qdict: >> qdict = {'kind': 'plug', >> 'handle': TC_H_ROOT} >> @@ -161,7 +169,10 @@ >> self.action = 0 >> >> def pack(self): >> - return struct.pack(self.fmt, self.action) >> + if int(kernelversion[0]) >= 3 and int(kernelversion[1]) >= 4: >> + return struct.pack(self.fmt, self.action, self.limit) >> + else: >> + return struct.pack(self.fmt, self.action) >> >> def parse(self, args): >> if not args: >> > > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xen.org > http://lists.xen.org/xen-users > --f46d04428240f6e5c904d626a801 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Hello All,

I am trying this patch on my machine Ubuntu 1= 2.04 AMD64 both for Dom0 and DomU with Xen 4.2.2-pre compiling from sources= also DRBD 8.3.11 but unfortunately it seem didn't work since I still g= ot the message=A0WARNING: s= uspend event channel unavailable, falling back to slow xenstore signalling.= =A0

Regards,

Agya

On Tue, Feb 19, 2013 at 12:39 PM, Andrew Ero= ss <eross@locatrix.com> wrote:
Hi all,

To close off on this, Shriram's patch worked= great, thank you.

So Ubuntu 12.10's standard = generic kernel is now working fine as a dom0 for Remus with Xen 4.1.4 (with= the patch from this thread).

I wrote up my full install instructions here:
http://wiki.xen.org/wiki/Install_Xen_4.1= .4_with_Remus_and_DRBD_on_Ubuntu_12.10

I also took a shot at a number of updates to:
http://wiki.x= en.org/wiki/Remus

And added these pages:
Feedback very welcome, a lot of that information was a bit old,= so I did my best.

Cheers,
Andrew


On Mon, F= eb 18, 2013 at 8:26 PM, Shriram Rajagopalan <rshriram@cs.ubc.ca>= wrote:
ah darn. Yes, the 3.5 kernel has sch_plug in= it. Unfortunately, the
technique to initialize the sch_plug module is bit
different with the module thats already mainline. You ll have to patch
the qdisc.py python module. I ll submit the
patch to xen devel soon.
Mean while, can you try the patch below and see if it works ?

Secondly, you said you were writing a blog about how you set it up.
One of the remus users created a wiki
remusha.wikidot.co= m, which has a whole tutorial on how to setup remus
with Debian Squeeze. I have been under fire
lately for a host of remus issues. It would be great if you could post
your experiences on the wiki too.
(http:= //remusha.wikidot.com/system:join)

thanks
shriram

---
diff -r 6435f1edf24e tools/python/xen/remus/qdisc.py
--- a/tools/python/xen/remus/qdisc.py =A0 Tue Jul 17 19:23:30 2012 -0400 +++ b/tools/python/xen/remus/qdisc.py =A0 Mon Feb 18 18:25:22 2013 -0500 @@ -1,6 +1,9 @@
=A0import socket, struct

=A0import netlink
+import platform
+
+kernelversion =3D platform.platform(terse=3DTrue).split("-")[1].= split(".")

=A0qdisc_kinds =3D {}

@@ -150,9 +153,14 @@
=A0TC_PLUG_RELEASE =3D 1

=A0class PlugQdisc(Qdisc):
- =A0 =A0fmt =3D 'I'

=A0 =A0 =A0def __init__(self, qdict=3DNone):
+ =A0 =A0 =A0 =A0if int(kernelversion[0]) >=3D 3 and int(kernelversion[1= ]) >=3D 4:
+ =A0 =A0 =A0 =A0 =A0 =A0self.fmt =3D 'iI'
+ =A0 =A0 =A0 =A0 =A0 =A0self.limit =3D 10000
+ =A0 =A0 =A0 =A0else:
+ =A0 =A0 =A0 =A0 =A0 =A0self.fmt =3D 'I'
+
=A0 =A0 =A0 =A0 =A0if not qdict:
=A0 =A0 =A0 =A0 =A0 =A0 =A0qdict =3D {'kind': 'plug',
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 'handle': TC_H_ROOT} @@ -161,7 +169,10 @@
=A0 =A0 =A0 =A0 =A0self.action =3D 0

=A0 =A0 =A0def pack(self):
- =A0 =A0 =A0 =A0return struct.pack(self.fmt, self.action)
+ =A0 =A0 =A0 =A0if int(kernelversion[0]) >=3D 3 and int(kernelversion[1= ]) >=3D 4:
+ =A0 =A0 =A0 =A0 =A0 =A0return struct.pack(self.fmt, self.action, self.lim= it)
+ =A0 =A0 =A0 =A0else:
+ =A0 =A0 =A0 =A0 =A0 =A0return struct.pack(self.fmt, self.action)

=A0 =A0 =A0def parse(self, args):
=A0 =A0 =A0 =A0 =A0if not args:


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

--f46d04428240f6e5c904d626a801-- --===============6431603293988160045== 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 --===============6431603293988160045==-- From xen-users-bounces@lists.xen.org Wed Feb 20 11:59:09 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 20 Feb 2013 11:59: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 1U88JI-0003zj-Fe; Wed, 20 Feb 2013 11:58:04 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U88JG-0003zd-KB for xen-users@lists.xen.org; Wed, 20 Feb 2013 11:58:03 +0000 Received: from [85.158.137.99:3397] by server-4.bemta-3.messagelabs.com id EE/6D-17521-94AB4215; Wed, 20 Feb 2013 11:58:01 +0000 X-Env-Sender: agya.naila@gmail.com X-Msg-Ref: server-10.tower-217.messagelabs.com!1361361469!17026131!1 X-Originating-IP: [74.125.82.53] 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.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 11740 invoked from network); 20 Feb 2013 11:57:53 -0000 Received: from mail-wg0-f53.google.com (HELO mail-wg0-f53.google.com) (74.125.82.53) by server-10.tower-217.messagelabs.com with RC4-SHA encrypted SMTP; 20 Feb 2013 11:57:53 -0000 Received: by mail-wg0-f53.google.com with SMTP id fn15so6558068wgb.32 for ; Wed, 20 Feb 2013 03:57:18 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=03zLrLTGaCKJvdH2GS52Ia1G9A9ZwwYFuSuS7JlsROo=; b=dQLBnz//pNnqUpBL8TsesFf+C1ooLUthgzbbF7HbvHjhIaNvM/7TKRLDvBu72X3zhJ lw5II2Cp7SG/COxvUnw28X7ZKf2qlz/6ezJUS9cTFcyB+1zXKDRc1WyOSy/eERIT0rfn IT0Jjdq/DbKhZ/XgCc85DI2M/4n+DudC00jfRFUVnj7bK2AFbk61bJAHaTVcD9ffpYci j/r8jcdcoGSSnpJKcoGCJp8s6w3l7RZ7W7NpUMjMzhdBc7b6BuvG+/wM+aDxOsmsBeqC s3azuAmJ38yK7hh0K3xMToHRoJrdczNcg/d5GFmAdSoMwt8osX+lNawajaovuAbmUlNo N1mA== MIME-Version: 1.0 X-Received: by 10.180.8.197 with SMTP id t5mr33524227wia.27.1361361438696; Wed, 20 Feb 2013 03:57:18 -0800 (PST) Received: by 10.216.236.13 with HTTP; Wed, 20 Feb 2013 03:57:18 -0800 (PST) In-Reply-To: References: Date: Wed, 20 Feb 2013 12:57:18 +0100 Message-ID: From: agya naila To: Andrew Eross Cc: rshriram@cs.ubc.ca, "xen-users@lists.xen.org" Subject: Re: [Xen-users] Remus dom0 network buffering X-BeenThere: xen-users@lists.xen.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="===============6431603293988160045==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============6431603293988160045== Content-Type: multipart/alternative; boundary=f46d04428240f6e5c904d626a801 --f46d04428240f6e5c904d626a801 Content-Type: text/plain; charset=ISO-8859-1 Hello All, I am trying this patch on my machine Ubuntu 12.04 AMD64 both for Dom0 and DomU with Xen 4.2.2-pre compiling from sources also DRBD 8.3.11 but unfortunately it seem didn't work since I still got the message WARNING: suspend event channel unavailable, falling back to slow xenstore signalling. Regards, Agya On Tue, Feb 19, 2013 at 12:39 PM, Andrew Eross wrote: > Hi all, > > To close off on this, Shriram's patch worked great, thank you. > > So Ubuntu 12.10's standard generic kernel is now working fine as a dom0 > for Remus with Xen 4.1.4 (with the patch from this thread). > > I wrote up my full install instructions here: > > http://wiki.xen.org/wiki/Install_Xen_4.1.4_with_Remus_and_DRBD_on_Ubuntu_12.10 > > I also took a shot at a number of updates to: > http://wiki.xen.org/wiki/Remus > > And added these pages: > http://wiki.xen.org/wiki/Remus_PV_domU_requirements > http://wiki.xen.org/wiki/Remus_dom0_requirements > > Feedback very welcome, a lot of that information was a bit old, so I did > my best. > > Cheers, > Andrew > > > On Mon, Feb 18, 2013 at 8:26 PM, Shriram Rajagopalan wrote: > >> ah darn. Yes, the 3.5 kernel has sch_plug in it. Unfortunately, the >> technique to initialize the sch_plug module is bit >> different with the module thats already mainline. You ll have to patch >> the qdisc.py python module. I ll submit the >> patch to xen devel soon. >> Mean while, can you try the patch below and see if it works ? >> >> Secondly, you said you were writing a blog about how you set it up. >> One of the remus users created a wiki >> remusha.wikidot.com, which has a whole tutorial on how to setup remus >> with Debian Squeeze. I have been under fire >> lately for a host of remus issues. It would be great if you could post >> your experiences on the wiki too. >> (http://remusha.wikidot.com/system:join) >> >> thanks >> shriram >> >> --- >> diff -r 6435f1edf24e tools/python/xen/remus/qdisc.py >> --- a/tools/python/xen/remus/qdisc.py Tue Jul 17 19:23:30 2012 -0400 >> +++ b/tools/python/xen/remus/qdisc.py Mon Feb 18 18:25:22 2013 -0500 >> @@ -1,6 +1,9 @@ >> import socket, struct >> >> import netlink >> +import platform >> + >> +kernelversion = platform.platform(terse=True).split("-")[1].split(".") >> >> qdisc_kinds = {} >> >> @@ -150,9 +153,14 @@ >> TC_PLUG_RELEASE = 1 >> >> class PlugQdisc(Qdisc): >> - fmt = 'I' >> >> def __init__(self, qdict=None): >> + if int(kernelversion[0]) >= 3 and int(kernelversion[1]) >= 4: >> + self.fmt = 'iI' >> + self.limit = 10000 >> + else: >> + self.fmt = 'I' >> + >> if not qdict: >> qdict = {'kind': 'plug', >> 'handle': TC_H_ROOT} >> @@ -161,7 +169,10 @@ >> self.action = 0 >> >> def pack(self): >> - return struct.pack(self.fmt, self.action) >> + if int(kernelversion[0]) >= 3 and int(kernelversion[1]) >= 4: >> + return struct.pack(self.fmt, self.action, self.limit) >> + else: >> + return struct.pack(self.fmt, self.action) >> >> def parse(self, args): >> if not args: >> > > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xen.org > http://lists.xen.org/xen-users > --f46d04428240f6e5c904d626a801 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Hello All,

I am trying this patch on my machine Ubuntu 1= 2.04 AMD64 both for Dom0 and DomU with Xen 4.2.2-pre compiling from sources= also DRBD 8.3.11 but unfortunately it seem didn't work since I still g= ot the message=A0WARNING: s= uspend event channel unavailable, falling back to slow xenstore signalling.= =A0

Regards,

Agya

On Tue, Feb 19, 2013 at 12:39 PM, Andrew Ero= ss <eross@locatrix.com> wrote:
Hi all,

To close off on this, Shriram's patch worked= great, thank you.

So Ubuntu 12.10's standard = generic kernel is now working fine as a dom0 for Remus with Xen 4.1.4 (with= the patch from this thread).

I wrote up my full install instructions here:
http://wiki.xen.org/wiki/Install_Xen_4.1= .4_with_Remus_and_DRBD_on_Ubuntu_12.10

I also took a shot at a number of updates to:
http://wiki.x= en.org/wiki/Remus

And added these pages:
Feedback very welcome, a lot of that information was a bit old,= so I did my best.

Cheers,
Andrew


On Mon, F= eb 18, 2013 at 8:26 PM, Shriram Rajagopalan <rshriram@cs.ubc.ca>= wrote:
ah darn. Yes, the 3.5 kernel has sch_plug in= it. Unfortunately, the
technique to initialize the sch_plug module is bit
different with the module thats already mainline. You ll have to patch
the qdisc.py python module. I ll submit the
patch to xen devel soon.
Mean while, can you try the patch below and see if it works ?

Secondly, you said you were writing a blog about how you set it up.
One of the remus users created a wiki
remusha.wikidot.co= m, which has a whole tutorial on how to setup remus
with Debian Squeeze. I have been under fire
lately for a host of remus issues. It would be great if you could post
your experiences on the wiki too.
(http:= //remusha.wikidot.com/system:join)

thanks
shriram

---
diff -r 6435f1edf24e tools/python/xen/remus/qdisc.py
--- a/tools/python/xen/remus/qdisc.py =A0 Tue Jul 17 19:23:30 2012 -0400 +++ b/tools/python/xen/remus/qdisc.py =A0 Mon Feb 18 18:25:22 2013 -0500 @@ -1,6 +1,9 @@
=A0import socket, struct

=A0import netlink
+import platform
+
+kernelversion =3D platform.platform(terse=3DTrue).split("-")[1].= split(".")

=A0qdisc_kinds =3D {}

@@ -150,9 +153,14 @@
=A0TC_PLUG_RELEASE =3D 1

=A0class PlugQdisc(Qdisc):
- =A0 =A0fmt =3D 'I'

=A0 =A0 =A0def __init__(self, qdict=3DNone):
+ =A0 =A0 =A0 =A0if int(kernelversion[0]) >=3D 3 and int(kernelversion[1= ]) >=3D 4:
+ =A0 =A0 =A0 =A0 =A0 =A0self.fmt =3D 'iI'
+ =A0 =A0 =A0 =A0 =A0 =A0self.limit =3D 10000
+ =A0 =A0 =A0 =A0else:
+ =A0 =A0 =A0 =A0 =A0 =A0self.fmt =3D 'I'
+
=A0 =A0 =A0 =A0 =A0if not qdict:
=A0 =A0 =A0 =A0 =A0 =A0 =A0qdict =3D {'kind': 'plug',
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 'handle': TC_H_ROOT} @@ -161,7 +169,10 @@
=A0 =A0 =A0 =A0 =A0self.action =3D 0

=A0 =A0 =A0def pack(self):
- =A0 =A0 =A0 =A0return struct.pack(self.fmt, self.action)
+ =A0 =A0 =A0 =A0if int(kernelversion[0]) >=3D 3 and int(kernelversion[1= ]) >=3D 4:
+ =A0 =A0 =A0 =A0 =A0 =A0return struct.pack(self.fmt, self.action, self.lim= it)
+ =A0 =A0 =A0 =A0else:
+ =A0 =A0 =A0 =A0 =A0 =A0return struct.pack(self.fmt, self.action)

=A0 =A0 =A0def parse(self, args):
=A0 =A0 =A0 =A0 =A0if not args:


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

--f46d04428240f6e5c904d626a801-- --===============6431603293988160045== 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 --===============6431603293988160045==-- From xen-users-bounces@lists.xen.org Wed Feb 20 12:03:28 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 20 Feb 2013 12:03: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 1U88NX-0004V4-4F; Wed, 20 Feb 2013 12:02:27 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U88NV-0004Ug-3t for xen-users@lists.xen.org; Wed, 20 Feb 2013 12:02:25 +0000 Received: from [85.158.139.83:35099] by server-15.bemta-5.messagelabs.com id D1/CB-18914-05BB4215; Wed, 20 Feb 2013 12:02:24 +0000 X-Env-Sender: eross@corp.locatrix.com X-Msg-Ref: server-12.tower-182.messagelabs.com!1361361720!28098716!1 X-Originating-IP: [209.85.223.170] 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.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 30486 invoked from network); 20 Feb 2013 12:02:02 -0000 Received: from mail-ie0-f170.google.com (HELO mail-ie0-f170.google.com) (209.85.223.170) by server-12.tower-182.messagelabs.com with RC4-SHA encrypted SMTP; 20 Feb 2013 12:02:02 -0000 Received: by mail-ie0-f170.google.com with SMTP id c11so9945761ieb.29 for ; Wed, 20 Feb 2013 04:02:00 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=x-received:mime-version:in-reply-to:references:from:date:message-id :subject:to:cc:content-type:x-gm-message-state; bh=GN4W32N2gZZue20y70oCZ4Rkhz+QxFQ7Q3uXvxh7MJ0=; b=iIvpWheFqF/V4G9dReIR1iQNVSglhfE0TnmpX7aN8vJ6e/pdvKB3CvgON9RSrFhzqw kAjF3quErgrNaNuavcLTMCX7rZSikowMkxVtsYe2hSkzpMeDLJvyTPTR+gSBPH5RDegF 8YvDuFHloqhssidEfL9Tknxsuu3W269KH86jpCBVIFP4Q+b/0eTyF5a0joAFJCh7wxky d9xO7m+NKAG43aLQjMqb4/UH9ofpZxy4T06as7kVN/dIYN2xMNSC88SNO6PkNOXlj3wd 8Z8hHf5gDbauQjovBmFhs1sOHdGdc7Td/spvMnUDWW4JMmhyeyD58y1qdatUBXSffKvV K40w== X-Received: by 10.50.196.199 with SMTP id io7mr5397620igc.76.1361361720118; Wed, 20 Feb 2013 04:02:00 -0800 (PST) MIME-Version: 1.0 Received: by 10.64.9.103 with HTTP; Wed, 20 Feb 2013 04:01:40 -0800 (PST) In-Reply-To: References: From: Andrew Eross Date: Wed, 20 Feb 2013 09:01:40 -0300 Message-ID: To: agya naila X-Gm-Message-State: ALoCoQk62fco6SwWvyaaotIRipqlDB+ZU9wDJtyNifB+kfDMoE7dwLxgc49Kx/Dzd2SVTikAk3nn Cc: rshriram@cs.ubc.ca, "xen-users@lists.xen.org" Subject: Re: [Xen-users] Remus dom0 network buffering X-BeenThere: xen-users@lists.xen.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="===============8505064255335359760==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============8505064255335359760== Content-Type: multipart/alternative; boundary=14dae934076fbd0c8104d626b96e --14dae934076fbd0c8104d626b96e Content-Type: text/plain; charset=ISO-8859-1 Hi Agya, This patch doesn't fix the 'suspend event channel' issue, it just fixes the crash from the first e-mail in this thread. Please see this wiki page: http://wiki.xen.org/wiki/Remus_PV_domU_requirements That discusses the suspend event channel issue. Cheers, Andrew On Wed, Feb 20, 2013 at 8:57 AM, agya naila wrote: > Hello All, > > I am trying this patch on my machine Ubuntu 12.04 AMD64 both for Dom0 and > DomU with Xen 4.2.2-pre compiling from sources also DRBD 8.3.11 but > unfortunately it seem didn't work since I still got the message WARNING: > suspend event channel unavailable, falling back to slow xenstore > signalling. > > Regards, > > Agya > > On Tue, Feb 19, 2013 at 12:39 PM, Andrew Eross wrote: > >> Hi all, >> >> To close off on this, Shriram's patch worked great, thank you. >> >> So Ubuntu 12.10's standard generic kernel is now working fine as a dom0 >> for Remus with Xen 4.1.4 (with the patch from this thread). >> >> I wrote up my full install instructions here: >> >> http://wiki.xen.org/wiki/Install_Xen_4.1.4_with_Remus_and_DRBD_on_Ubuntu_12.10 >> >> I also took a shot at a number of updates to: >> http://wiki.xen.org/wiki/Remus >> >> And added these pages: >> http://wiki.xen.org/wiki/Remus_PV_domU_requirements >> http://wiki.xen.org/wiki/Remus_dom0_requirements >> >> Feedback very welcome, a lot of that information was a bit old, so I did >> my best. >> >> Cheers, >> Andrew >> >> >> On Mon, Feb 18, 2013 at 8:26 PM, Shriram Rajagopalan wrote: >> >>> ah darn. Yes, the 3.5 kernel has sch_plug in it. Unfortunately, the >>> technique to initialize the sch_plug module is bit >>> different with the module thats already mainline. You ll have to patch >>> the qdisc.py python module. I ll submit the >>> patch to xen devel soon. >>> Mean while, can you try the patch below and see if it works ? >>> >>> Secondly, you said you were writing a blog about how you set it up. >>> One of the remus users created a wiki >>> remusha.wikidot.com, which has a whole tutorial on how to setup remus >>> with Debian Squeeze. I have been under fire >>> lately for a host of remus issues. It would be great if you could post >>> your experiences on the wiki too. >>> (http://remusha.wikidot.com/system:join) >>> >>> thanks >>> shriram >>> >>> --- >>> diff -r 6435f1edf24e tools/python/xen/remus/qdisc.py >>> --- a/tools/python/xen/remus/qdisc.py Tue Jul 17 19:23:30 2012 -0400 >>> +++ b/tools/python/xen/remus/qdisc.py Mon Feb 18 18:25:22 2013 -0500 >>> @@ -1,6 +1,9 @@ >>> import socket, struct >>> >>> import netlink >>> +import platform >>> + >>> +kernelversion = platform.platform(terse=True).split("-")[1].split(".") >>> >>> qdisc_kinds = {} >>> >>> @@ -150,9 +153,14 @@ >>> TC_PLUG_RELEASE = 1 >>> >>> class PlugQdisc(Qdisc): >>> - fmt = 'I' >>> >>> def __init__(self, qdict=None): >>> + if int(kernelversion[0]) >= 3 and int(kernelversion[1]) >= 4: >>> + self.fmt = 'iI' >>> + self.limit = 10000 >>> + else: >>> + self.fmt = 'I' >>> + >>> if not qdict: >>> qdict = {'kind': 'plug', >>> 'handle': TC_H_ROOT} >>> @@ -161,7 +169,10 @@ >>> self.action = 0 >>> >>> def pack(self): >>> - return struct.pack(self.fmt, self.action) >>> + if int(kernelversion[0]) >= 3 and int(kernelversion[1]) >= 4: >>> + return struct.pack(self.fmt, self.action, self.limit) >>> + else: >>> + return struct.pack(self.fmt, self.action) >>> >>> def parse(self, args): >>> if not args: >>> >> >> >> _______________________________________________ >> Xen-users mailing list >> Xen-users@lists.xen.org >> http://lists.xen.org/xen-users >> > > --14dae934076fbd0c8104d626b96e Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Hi Agya,

This patch doesn't fix the 'suspend eve= nt channel' issue, it just fixes the crash from the first e-mail in thi= s thread.


That discusses the suspend event channel issue.

Cheers,
Andrew


On Wed, Feb 20, 2013 at 8:57 AM, agya naila = <agya.naila@gm= ail.com> wrote:
Hello All,

I am trying th= is patch on my machine Ubuntu 12.04 AMD64 both for Dom0 and DomU with Xen 4= .2.2-pre compiling from sources also DRBD 8.3.11 but unfortunately it seem = didn't work since I still got the message=A0WARNING: susp= end event channel unavailable, falling back to slow xenstore signalling.=A0=

Regards= ,

A= gya

On Tue, Feb 19, 2013 = at 12:39 PM, Andrew Eross <eross@locatrix.com> wrote:
Hi all,

To close off on this, Shriram's patch worked= great, thank you.

So Ubuntu 12.10's standard = generic kernel is now working fine as a dom0 for Remus with Xen 4.1.4 (with= the patch from this thread).

I wrote up my full install instructions here:
http://wiki.xen.org/wiki/Install_Xen_4.1= .4_with_Remus_and_DRBD_on_Ubuntu_12.10

I also took a shot at a number of updates to:
http://wiki.x= en.org/wiki/Remus

And added these pages:
Feedback very welcome, a lot of that information was a bit old,= so I did my best.

Cheers,
Andrew

=

On Mon, Feb 18, 2013 at 8:26 PM, Shrira= m Rajagopalan <rshriram@cs.ubc.ca> wrote:
ah darn. Yes, the 3.5 kernel has sch_plug in= it. Unfortunately, the
technique to initialize the sch_plug module is bit
different with the module thats already mainline. You ll have to patch
the qdisc.py python module. I ll submit the
patch to xen devel soon.
Mean while, can you try the patch below and see if it works ?

Secondly, you said you were writing a blog about how you set it up.
One of the remus users created a wiki
remusha.wikidot.co= m, which has a whole tutorial on how to setup remus
with Debian Squeeze. I have been under fire
lately for a host of remus issues. It would be great if you could post
your experiences on the wiki too.
(http:= //remusha.wikidot.com/system:join)

thanks
shriram

---
diff -r 6435f1edf24e tools/python/xen/remus/qdisc.py
--- a/tools/python/xen/remus/qdisc.py =A0 Tue Jul 17 19:23:30 2012 -0400 +++ b/tools/python/xen/remus/qdisc.py =A0 Mon Feb 18 18:25:22 2013 -0500 @@ -1,6 +1,9 @@
=A0import socket, struct

=A0import netlink
+import platform
+
+kernelversion =3D platform.platform(terse=3DTrue).split("-")[1].= split(".")

=A0qdisc_kinds =3D {}

@@ -150,9 +153,14 @@
=A0TC_PLUG_RELEASE =3D 1

=A0class PlugQdisc(Qdisc):
- =A0 =A0fmt =3D 'I'

=A0 =A0 =A0def __init__(self, qdict=3DNone):
+ =A0 =A0 =A0 =A0if int(kernelversion[0]) >=3D 3 and int(kernelversion[1= ]) >=3D 4:
+ =A0 =A0 =A0 =A0 =A0 =A0self.fmt =3D 'iI'
+ =A0 =A0 =A0 =A0 =A0 =A0self.limit =3D 10000
+ =A0 =A0 =A0 =A0else:
+ =A0 =A0 =A0 =A0 =A0 =A0self.fmt =3D 'I'
+
=A0 =A0 =A0 =A0 =A0if not qdict:
=A0 =A0 =A0 =A0 =A0 =A0 =A0qdict =3D {'kind': 'plug',
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 'handle': TC_H_ROOT} @@ -161,7 +169,10 @@
=A0 =A0 =A0 =A0 =A0self.action =3D 0

=A0 =A0 =A0def pack(self):
- =A0 =A0 =A0 =A0return struct.pack(self.fmt, self.action)
+ =A0 =A0 =A0 =A0if int(kernelversion[0]) >=3D 3 and int(kernelversion[1= ]) >=3D 4:
+ =A0 =A0 =A0 =A0 =A0 =A0return struct.pack(self.fmt, self.action, self.lim= it)
+ =A0 =A0 =A0 =A0else:
+ =A0 =A0 =A0 =A0 =A0 =A0return struct.pack(self.fmt, self.action)

=A0 =A0 =A0def parse(self, args):
=A0 =A0 =A0 =A0 =A0if not args:


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


--14dae934076fbd0c8104d626b96e-- --===============8505064255335359760== 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 --===============8505064255335359760==-- From xen-users-bounces@lists.xen.org Wed Feb 20 12:03:28 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 20 Feb 2013 12:03: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 1U88NX-0004V4-4F; Wed, 20 Feb 2013 12:02:27 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U88NV-0004Ug-3t for xen-users@lists.xen.org; Wed, 20 Feb 2013 12:02:25 +0000 Received: from [85.158.139.83:35099] by server-15.bemta-5.messagelabs.com id D1/CB-18914-05BB4215; Wed, 20 Feb 2013 12:02:24 +0000 X-Env-Sender: eross@corp.locatrix.com X-Msg-Ref: server-12.tower-182.messagelabs.com!1361361720!28098716!1 X-Originating-IP: [209.85.223.170] 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.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 30486 invoked from network); 20 Feb 2013 12:02:02 -0000 Received: from mail-ie0-f170.google.com (HELO mail-ie0-f170.google.com) (209.85.223.170) by server-12.tower-182.messagelabs.com with RC4-SHA encrypted SMTP; 20 Feb 2013 12:02:02 -0000 Received: by mail-ie0-f170.google.com with SMTP id c11so9945761ieb.29 for ; Wed, 20 Feb 2013 04:02:00 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=x-received:mime-version:in-reply-to:references:from:date:message-id :subject:to:cc:content-type:x-gm-message-state; bh=GN4W32N2gZZue20y70oCZ4Rkhz+QxFQ7Q3uXvxh7MJ0=; b=iIvpWheFqF/V4G9dReIR1iQNVSglhfE0TnmpX7aN8vJ6e/pdvKB3CvgON9RSrFhzqw kAjF3quErgrNaNuavcLTMCX7rZSikowMkxVtsYe2hSkzpMeDLJvyTPTR+gSBPH5RDegF 8YvDuFHloqhssidEfL9Tknxsuu3W269KH86jpCBVIFP4Q+b/0eTyF5a0joAFJCh7wxky d9xO7m+NKAG43aLQjMqb4/UH9ofpZxy4T06as7kVN/dIYN2xMNSC88SNO6PkNOXlj3wd 8Z8hHf5gDbauQjovBmFhs1sOHdGdc7Td/spvMnUDWW4JMmhyeyD58y1qdatUBXSffKvV K40w== X-Received: by 10.50.196.199 with SMTP id io7mr5397620igc.76.1361361720118; Wed, 20 Feb 2013 04:02:00 -0800 (PST) MIME-Version: 1.0 Received: by 10.64.9.103 with HTTP; Wed, 20 Feb 2013 04:01:40 -0800 (PST) In-Reply-To: References: From: Andrew Eross Date: Wed, 20 Feb 2013 09:01:40 -0300 Message-ID: To: agya naila X-Gm-Message-State: ALoCoQk62fco6SwWvyaaotIRipqlDB+ZU9wDJtyNifB+kfDMoE7dwLxgc49Kx/Dzd2SVTikAk3nn Cc: rshriram@cs.ubc.ca, "xen-users@lists.xen.org" Subject: Re: [Xen-users] Remus dom0 network buffering X-BeenThere: xen-users@lists.xen.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="===============8505064255335359760==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============8505064255335359760== Content-Type: multipart/alternative; boundary=14dae934076fbd0c8104d626b96e --14dae934076fbd0c8104d626b96e Content-Type: text/plain; charset=ISO-8859-1 Hi Agya, This patch doesn't fix the 'suspend event channel' issue, it just fixes the crash from the first e-mail in this thread. Please see this wiki page: http://wiki.xen.org/wiki/Remus_PV_domU_requirements That discusses the suspend event channel issue. Cheers, Andrew On Wed, Feb 20, 2013 at 8:57 AM, agya naila wrote: > Hello All, > > I am trying this patch on my machine Ubuntu 12.04 AMD64 both for Dom0 and > DomU with Xen 4.2.2-pre compiling from sources also DRBD 8.3.11 but > unfortunately it seem didn't work since I still got the message WARNING: > suspend event channel unavailable, falling back to slow xenstore > signalling. > > Regards, > > Agya > > On Tue, Feb 19, 2013 at 12:39 PM, Andrew Eross wrote: > >> Hi all, >> >> To close off on this, Shriram's patch worked great, thank you. >> >> So Ubuntu 12.10's standard generic kernel is now working fine as a dom0 >> for Remus with Xen 4.1.4 (with the patch from this thread). >> >> I wrote up my full install instructions here: >> >> http://wiki.xen.org/wiki/Install_Xen_4.1.4_with_Remus_and_DRBD_on_Ubuntu_12.10 >> >> I also took a shot at a number of updates to: >> http://wiki.xen.org/wiki/Remus >> >> And added these pages: >> http://wiki.xen.org/wiki/Remus_PV_domU_requirements >> http://wiki.xen.org/wiki/Remus_dom0_requirements >> >> Feedback very welcome, a lot of that information was a bit old, so I did >> my best. >> >> Cheers, >> Andrew >> >> >> On Mon, Feb 18, 2013 at 8:26 PM, Shriram Rajagopalan wrote: >> >>> ah darn. Yes, the 3.5 kernel has sch_plug in it. Unfortunately, the >>> technique to initialize the sch_plug module is bit >>> different with the module thats already mainline. You ll have to patch >>> the qdisc.py python module. I ll submit the >>> patch to xen devel soon. >>> Mean while, can you try the patch below and see if it works ? >>> >>> Secondly, you said you were writing a blog about how you set it up. >>> One of the remus users created a wiki >>> remusha.wikidot.com, which has a whole tutorial on how to setup remus >>> with Debian Squeeze. I have been under fire >>> lately for a host of remus issues. It would be great if you could post >>> your experiences on the wiki too. >>> (http://remusha.wikidot.com/system:join) >>> >>> thanks >>> shriram >>> >>> --- >>> diff -r 6435f1edf24e tools/python/xen/remus/qdisc.py >>> --- a/tools/python/xen/remus/qdisc.py Tue Jul 17 19:23:30 2012 -0400 >>> +++ b/tools/python/xen/remus/qdisc.py Mon Feb 18 18:25:22 2013 -0500 >>> @@ -1,6 +1,9 @@ >>> import socket, struct >>> >>> import netlink >>> +import platform >>> + >>> +kernelversion = platform.platform(terse=True).split("-")[1].split(".") >>> >>> qdisc_kinds = {} >>> >>> @@ -150,9 +153,14 @@ >>> TC_PLUG_RELEASE = 1 >>> >>> class PlugQdisc(Qdisc): >>> - fmt = 'I' >>> >>> def __init__(self, qdict=None): >>> + if int(kernelversion[0]) >= 3 and int(kernelversion[1]) >= 4: >>> + self.fmt = 'iI' >>> + self.limit = 10000 >>> + else: >>> + self.fmt = 'I' >>> + >>> if not qdict: >>> qdict = {'kind': 'plug', >>> 'handle': TC_H_ROOT} >>> @@ -161,7 +169,10 @@ >>> self.action = 0 >>> >>> def pack(self): >>> - return struct.pack(self.fmt, self.action) >>> + if int(kernelversion[0]) >= 3 and int(kernelversion[1]) >= 4: >>> + return struct.pack(self.fmt, self.action, self.limit) >>> + else: >>> + return struct.pack(self.fmt, self.action) >>> >>> def parse(self, args): >>> if not args: >>> >> >> >> _______________________________________________ >> Xen-users mailing list >> Xen-users@lists.xen.org >> http://lists.xen.org/xen-users >> > > --14dae934076fbd0c8104d626b96e Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Hi Agya,

This patch doesn't fix the 'suspend eve= nt channel' issue, it just fixes the crash from the first e-mail in thi= s thread.


That discusses the suspend event channel issue.

Cheers,
Andrew


On Wed, Feb 20, 2013 at 8:57 AM, agya naila = <agya.naila@gm= ail.com> wrote:
Hello All,

I am trying th= is patch on my machine Ubuntu 12.04 AMD64 both for Dom0 and DomU with Xen 4= .2.2-pre compiling from sources also DRBD 8.3.11 but unfortunately it seem = didn't work since I still got the message=A0WARNING: susp= end event channel unavailable, falling back to slow xenstore signalling.=A0=

Regards= ,

A= gya

On Tue, Feb 19, 2013 = at 12:39 PM, Andrew Eross <eross@locatrix.com> wrote:
Hi all,

To close off on this, Shriram's patch worked= great, thank you.

So Ubuntu 12.10's standard = generic kernel is now working fine as a dom0 for Remus with Xen 4.1.4 (with= the patch from this thread).

I wrote up my full install instructions here:
http://wiki.xen.org/wiki/Install_Xen_4.1= .4_with_Remus_and_DRBD_on_Ubuntu_12.10

I also took a shot at a number of updates to:
http://wiki.x= en.org/wiki/Remus

And added these pages:
Feedback very welcome, a lot of that information was a bit old,= so I did my best.

Cheers,
Andrew

=

On Mon, Feb 18, 2013 at 8:26 PM, Shrira= m Rajagopalan <rshriram@cs.ubc.ca> wrote:
ah darn. Yes, the 3.5 kernel has sch_plug in= it. Unfortunately, the
technique to initialize the sch_plug module is bit
different with the module thats already mainline. You ll have to patch
the qdisc.py python module. I ll submit the
patch to xen devel soon.
Mean while, can you try the patch below and see if it works ?

Secondly, you said you were writing a blog about how you set it up.
One of the remus users created a wiki
remusha.wikidot.co= m, which has a whole tutorial on how to setup remus
with Debian Squeeze. I have been under fire
lately for a host of remus issues. It would be great if you could post
your experiences on the wiki too.
(http:= //remusha.wikidot.com/system:join)

thanks
shriram

---
diff -r 6435f1edf24e tools/python/xen/remus/qdisc.py
--- a/tools/python/xen/remus/qdisc.py =A0 Tue Jul 17 19:23:30 2012 -0400 +++ b/tools/python/xen/remus/qdisc.py =A0 Mon Feb 18 18:25:22 2013 -0500 @@ -1,6 +1,9 @@
=A0import socket, struct

=A0import netlink
+import platform
+
+kernelversion =3D platform.platform(terse=3DTrue).split("-")[1].= split(".")

=A0qdisc_kinds =3D {}

@@ -150,9 +153,14 @@
=A0TC_PLUG_RELEASE =3D 1

=A0class PlugQdisc(Qdisc):
- =A0 =A0fmt =3D 'I'

=A0 =A0 =A0def __init__(self, qdict=3DNone):
+ =A0 =A0 =A0 =A0if int(kernelversion[0]) >=3D 3 and int(kernelversion[1= ]) >=3D 4:
+ =A0 =A0 =A0 =A0 =A0 =A0self.fmt =3D 'iI'
+ =A0 =A0 =A0 =A0 =A0 =A0self.limit =3D 10000
+ =A0 =A0 =A0 =A0else:
+ =A0 =A0 =A0 =A0 =A0 =A0self.fmt =3D 'I'
+
=A0 =A0 =A0 =A0 =A0if not qdict:
=A0 =A0 =A0 =A0 =A0 =A0 =A0qdict =3D {'kind': 'plug',
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 'handle': TC_H_ROOT} @@ -161,7 +169,10 @@
=A0 =A0 =A0 =A0 =A0self.action =3D 0

=A0 =A0 =A0def pack(self):
- =A0 =A0 =A0 =A0return struct.pack(self.fmt, self.action)
+ =A0 =A0 =A0 =A0if int(kernelversion[0]) >=3D 3 and int(kernelversion[1= ]) >=3D 4:
+ =A0 =A0 =A0 =A0 =A0 =A0return struct.pack(self.fmt, self.action, self.lim= it)
+ =A0 =A0 =A0 =A0else:
+ =A0 =A0 =A0 =A0 =A0 =A0return struct.pack(self.fmt, self.action)

=A0 =A0 =A0def parse(self, args):
=A0 =A0 =A0 =A0 =A0if not args:


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


--14dae934076fbd0c8104d626b96e-- --===============8505064255335359760== 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 --===============8505064255335359760==-- From xen-users-bounces@lists.xen.org Wed Feb 20 12:15:11 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 20 Feb 2013 12:15: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 1U88Yz-0005Qi-M7; Wed, 20 Feb 2013 12:14:17 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U88Yx-0005Qa-Bm for xen-users@lists.xen.org; Wed, 20 Feb 2013 12:14:15 +0000 Received: from [85.158.139.211:29496] by server-7.bemta-5.messagelabs.com id 76/EE-11121-61EB4215; Wed, 20 Feb 2013 12:14:14 +0000 X-Env-Sender: agya.naila@gmail.com X-Msg-Ref: server-8.tower-206.messagelabs.com!1361362436!18374007!1 X-Originating-IP: [74.125.82.50] 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.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 7291 invoked from network); 20 Feb 2013 12:13:56 -0000 Received: from mail-wg0-f50.google.com (HELO mail-wg0-f50.google.com) (74.125.82.50) by server-8.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 20 Feb 2013 12:13:56 -0000 Received: by mail-wg0-f50.google.com with SMTP id es5so6232144wgb.17 for ; Wed, 20 Feb 2013 04:13:56 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=sN5LiTCuqEUUMpx4rrSMliYbknulF7YoWAqSRs0GUAE=; b=WstoE1z1wZfdu+rpkyNivt8Fln11kG+CawhQ+SfpHFV+fKAAdk6zmURA+za919jWrU F0hDseQgoYAqMpFu6F7nAI5okiA7qQCTHOpNM8FyiiS3+s1ojrTLJgpzLbcKqcABfNu1 PZHrjl/WczA2wikj6KBL22zIJ8lwDH5aaJYrWcePHsjOev83seawKRS5Fiy33pfIF4mg HypdWz3Iq1b500N/nk/PnenpXJvabQwHt4u0BzZx6ffRyfuvh/vPXQDL4AwGD3pnqgvM zb597TMEACFDEegtF6Bf4pMOPhL2FoOKNSdweh9Q0t/A3wYsGjFyR761jfgTc5Fl9N1n oTAg== MIME-Version: 1.0 X-Received: by 10.180.85.97 with SMTP id g1mr34186946wiz.29.1361362436048; Wed, 20 Feb 2013 04:13:56 -0800 (PST) Received: by 10.216.236.13 with HTTP; Wed, 20 Feb 2013 04:13:55 -0800 (PST) In-Reply-To: References: Date: Wed, 20 Feb 2013 13:13:55 +0100 Message-ID: From: agya naila To: Andrew Eross Cc: rshriram@cs.ubc.ca, "xen-users@lists.xen.org" Subject: Re: [Xen-users] Remus dom0 network buffering X-BeenThere: xen-users@lists.xen.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="===============7131213750767599653==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============7131213750767599653== Content-Type: multipart/alternative; boundary=f46d0444036c69485f04d626e4bf --f46d0444036c69485f04d626e4bf Content-Type: text/plain; charset=ISO-8859-1 Aha, sorry to mix it :), its clear now. Regards, Agya On Wed, Feb 20, 2013 at 1:01 PM, Andrew Eross wrote: > Hi Agya, > > This patch doesn't fix the 'suspend event channel' issue, it just fixes > the crash from the first e-mail in this thread. > > Please see this wiki page: > http://wiki.xen.org/wiki/Remus_PV_domU_requirements > > That discusses the suspend event channel issue. > > Cheers, > Andrew > > > On Wed, Feb 20, 2013 at 8:57 AM, agya naila wrote: > >> Hello All, >> >> I am trying this patch on my machine Ubuntu 12.04 AMD64 both for Dom0 and >> DomU with Xen 4.2.2-pre compiling from sources also DRBD 8.3.11 but >> unfortunately it seem didn't work since I still got the message WARNING: >> suspend event channel unavailable, falling back to slow xenstore >> signalling. >> >> Regards, >> >> Agya >> >> On Tue, Feb 19, 2013 at 12:39 PM, Andrew Eross wrote: >> >>> Hi all, >>> >>> To close off on this, Shriram's patch worked great, thank you. >>> >>> So Ubuntu 12.10's standard generic kernel is now working fine as a dom0 >>> for Remus with Xen 4.1.4 (with the patch from this thread). >>> >>> I wrote up my full install instructions here: >>> >>> http://wiki.xen.org/wiki/Install_Xen_4.1.4_with_Remus_and_DRBD_on_Ubuntu_12.10 >>> >>> I also took a shot at a number of updates to: >>> http://wiki.xen.org/wiki/Remus >>> >>> And added these pages: >>> http://wiki.xen.org/wiki/Remus_PV_domU_requirements >>> http://wiki.xen.org/wiki/Remus_dom0_requirements >>> >>> Feedback very welcome, a lot of that information was a bit old, so I did >>> my best. >>> >>> Cheers, >>> Andrew >>> >>> >>> On Mon, Feb 18, 2013 at 8:26 PM, Shriram Rajagopalan >> > wrote: >>> >>>> ah darn. Yes, the 3.5 kernel has sch_plug in it. Unfortunately, the >>>> technique to initialize the sch_plug module is bit >>>> different with the module thats already mainline. You ll have to patch >>>> the qdisc.py python module. I ll submit the >>>> patch to xen devel soon. >>>> Mean while, can you try the patch below and see if it works ? >>>> >>>> Secondly, you said you were writing a blog about how you set it up. >>>> One of the remus users created a wiki >>>> remusha.wikidot.com, which has a whole tutorial on how to setup remus >>>> with Debian Squeeze. I have been under fire >>>> lately for a host of remus issues. It would be great if you could post >>>> your experiences on the wiki too. >>>> (http://remusha.wikidot.com/system:join) >>>> >>>> thanks >>>> shriram >>>> >>>> --- >>>> diff -r 6435f1edf24e tools/python/xen/remus/qdisc.py >>>> --- a/tools/python/xen/remus/qdisc.py Tue Jul 17 19:23:30 2012 -0400 >>>> +++ b/tools/python/xen/remus/qdisc.py Mon Feb 18 18:25:22 2013 -0500 >>>> @@ -1,6 +1,9 @@ >>>> import socket, struct >>>> >>>> import netlink >>>> +import platform >>>> + >>>> +kernelversion = platform.platform(terse=True).split("-")[1].split(".") >>>> >>>> qdisc_kinds = {} >>>> >>>> @@ -150,9 +153,14 @@ >>>> TC_PLUG_RELEASE = 1 >>>> >>>> class PlugQdisc(Qdisc): >>>> - fmt = 'I' >>>> >>>> def __init__(self, qdict=None): >>>> + if int(kernelversion[0]) >= 3 and int(kernelversion[1]) >= 4: >>>> + self.fmt = 'iI' >>>> + self.limit = 10000 >>>> + else: >>>> + self.fmt = 'I' >>>> + >>>> if not qdict: >>>> qdict = {'kind': 'plug', >>>> 'handle': TC_H_ROOT} >>>> @@ -161,7 +169,10 @@ >>>> self.action = 0 >>>> >>>> def pack(self): >>>> - return struct.pack(self.fmt, self.action) >>>> + if int(kernelversion[0]) >= 3 and int(kernelversion[1]) >= 4: >>>> + return struct.pack(self.fmt, self.action, self.limit) >>>> + else: >>>> + return struct.pack(self.fmt, self.action) >>>> >>>> def parse(self, args): >>>> if not args: >>>> >>> >>> >>> _______________________________________________ >>> Xen-users mailing list >>> Xen-users@lists.xen.org >>> http://lists.xen.org/xen-users >>> >> >> > --f46d0444036c69485f04d626e4bf Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Aha, sorry to mix it :), its clear now.

Regards,

Agya

On Wed, Feb 20, 20= 13 at 1:01 PM, Andrew Eross <eross@locatrix.com> wrote:
Hi Agya,

This patch doesn= 't fix the 'suspend event channel' issue, it just fixes the cra= sh from the first e-mail in this thread.


That discusses the suspend event channel issue.

Cheers,
Andrew


On Wed, Feb 20, 2013 a= t 8:57 AM, agya naila <agya.naila@gmail.com> wrote:
Hello All,

I am trying th= is patch on my machine Ubuntu 12.04 AMD64 both for Dom0 and DomU with Xen 4= .2.2-pre compiling from sources also DRBD 8.3.11 but unfortunately it seem = didn't work since I still got the message=A0WARNING: susp= end event channel unavailable, falling back to slow xenstore signalling.=A0=

Regards= ,

A= gya

On Tue, Feb 19, 2013 at 12:39 PM, = Andrew Eross <eross@locatrix.com> wrote:
Hi all,

To close off on this, Shriram's patch worked= great, thank you.

So Ubuntu 12.10's standard = generic kernel is now working fine as a dom0 for Remus with Xen 4.1.4 (with= the patch from this thread).

I wrote up my full install instructions here:
http://wiki.xen.org/wiki/Install_Xen_4.1= .4_with_Remus_and_DRBD_on_Ubuntu_12.10

I also took a shot at a number of updates to:
http://wiki.x= en.org/wiki/Remus

And added these pages:
Feedback very welcome, a lot of that information was a bit old,= so I did my best.

Cheers,
Andrew

=

On Mon, Feb 18, 2013 at 8:26 PM, Shrira= m Rajagopalan <rshriram@cs.ubc.ca> wrote:
ah darn. Yes, the 3.5 kernel has sch_plug in= it. Unfortunately, the
technique to initialize the sch_plug module is bit
different with the module thats already mainline. You ll have to patch
the qdisc.py python module. I ll submit the
patch to xen devel soon.
Mean while, can you try the patch below and see if it works ?

Secondly, you said you were writing a blog about how you set it up.
One of the remus users created a wiki
remusha.wikidot.co= m, which has a whole tutorial on how to setup remus
with Debian Squeeze. I have been under fire
lately for a host of remus issues. It would be great if you could post
your experiences on the wiki too.
(http:= //remusha.wikidot.com/system:join)

thanks
shriram

---
diff -r 6435f1edf24e tools/python/xen/remus/qdisc.py
--- a/tools/python/xen/remus/qdisc.py =A0 Tue Jul 17 19:23:30 2012 -0400 +++ b/tools/python/xen/remus/qdisc.py =A0 Mon Feb 18 18:25:22 2013 -0500 @@ -1,6 +1,9 @@
=A0import socket, struct

=A0import netlink
+import platform
+
+kernelversion =3D platform.platform(terse=3DTrue).split("-")[1].= split(".")

=A0qdisc_kinds =3D {}

@@ -150,9 +153,14 @@
=A0TC_PLUG_RELEASE =3D 1

=A0class PlugQdisc(Qdisc):
- =A0 =A0fmt =3D 'I'

=A0 =A0 =A0def __init__(self, qdict=3DNone):
+ =A0 =A0 =A0 =A0if int(kernelversion[0]) >=3D 3 and int(kernelversion[1= ]) >=3D 4:
+ =A0 =A0 =A0 =A0 =A0 =A0self.fmt =3D 'iI'
+ =A0 =A0 =A0 =A0 =A0 =A0self.limit =3D 10000
+ =A0 =A0 =A0 =A0else:
+ =A0 =A0 =A0 =A0 =A0 =A0self.fmt =3D 'I'
+
=A0 =A0 =A0 =A0 =A0if not qdict:
=A0 =A0 =A0 =A0 =A0 =A0 =A0qdict =3D {'kind': 'plug',
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 'handle': TC_H_ROOT} @@ -161,7 +169,10 @@
=A0 =A0 =A0 =A0 =A0self.action =3D 0

=A0 =A0 =A0def pack(self):
- =A0 =A0 =A0 =A0return struct.pack(self.fmt, self.action)
+ =A0 =A0 =A0 =A0if int(kernelversion[0]) >=3D 3 and int(kernelversion[1= ]) >=3D 4:
+ =A0 =A0 =A0 =A0 =A0 =A0return struct.pack(self.fmt, self.action, self.lim= it)
+ =A0 =A0 =A0 =A0else:
+ =A0 =A0 =A0 =A0 =A0 =A0return struct.pack(self.fmt, self.action)

=A0 =A0 =A0def parse(self, args):
=A0 =A0 =A0 =A0 =A0if not args:


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



--f46d0444036c69485f04d626e4bf-- --===============7131213750767599653== 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 --===============7131213750767599653==-- From xen-users-bounces@lists.xen.org Wed Feb 20 12:15:11 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 20 Feb 2013 12:15: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 1U88Yz-0005Qi-M7; Wed, 20 Feb 2013 12:14:17 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U88Yx-0005Qa-Bm for xen-users@lists.xen.org; Wed, 20 Feb 2013 12:14:15 +0000 Received: from [85.158.139.211:29496] by server-7.bemta-5.messagelabs.com id 76/EE-11121-61EB4215; Wed, 20 Feb 2013 12:14:14 +0000 X-Env-Sender: agya.naila@gmail.com X-Msg-Ref: server-8.tower-206.messagelabs.com!1361362436!18374007!1 X-Originating-IP: [74.125.82.50] 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.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 7291 invoked from network); 20 Feb 2013 12:13:56 -0000 Received: from mail-wg0-f50.google.com (HELO mail-wg0-f50.google.com) (74.125.82.50) by server-8.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 20 Feb 2013 12:13:56 -0000 Received: by mail-wg0-f50.google.com with SMTP id es5so6232144wgb.17 for ; Wed, 20 Feb 2013 04:13:56 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=sN5LiTCuqEUUMpx4rrSMliYbknulF7YoWAqSRs0GUAE=; b=WstoE1z1wZfdu+rpkyNivt8Fln11kG+CawhQ+SfpHFV+fKAAdk6zmURA+za919jWrU F0hDseQgoYAqMpFu6F7nAI5okiA7qQCTHOpNM8FyiiS3+s1ojrTLJgpzLbcKqcABfNu1 PZHrjl/WczA2wikj6KBL22zIJ8lwDH5aaJYrWcePHsjOev83seawKRS5Fiy33pfIF4mg HypdWz3Iq1b500N/nk/PnenpXJvabQwHt4u0BzZx6ffRyfuvh/vPXQDL4AwGD3pnqgvM zb597TMEACFDEegtF6Bf4pMOPhL2FoOKNSdweh9Q0t/A3wYsGjFyR761jfgTc5Fl9N1n oTAg== MIME-Version: 1.0 X-Received: by 10.180.85.97 with SMTP id g1mr34186946wiz.29.1361362436048; Wed, 20 Feb 2013 04:13:56 -0800 (PST) Received: by 10.216.236.13 with HTTP; Wed, 20 Feb 2013 04:13:55 -0800 (PST) In-Reply-To: References: Date: Wed, 20 Feb 2013 13:13:55 +0100 Message-ID: From: agya naila To: Andrew Eross Cc: rshriram@cs.ubc.ca, "xen-users@lists.xen.org" Subject: Re: [Xen-users] Remus dom0 network buffering X-BeenThere: xen-users@lists.xen.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="===============7131213750767599653==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============7131213750767599653== Content-Type: multipart/alternative; boundary=f46d0444036c69485f04d626e4bf --f46d0444036c69485f04d626e4bf Content-Type: text/plain; charset=ISO-8859-1 Aha, sorry to mix it :), its clear now. Regards, Agya On Wed, Feb 20, 2013 at 1:01 PM, Andrew Eross wrote: > Hi Agya, > > This patch doesn't fix the 'suspend event channel' issue, it just fixes > the crash from the first e-mail in this thread. > > Please see this wiki page: > http://wiki.xen.org/wiki/Remus_PV_domU_requirements > > That discusses the suspend event channel issue. > > Cheers, > Andrew > > > On Wed, Feb 20, 2013 at 8:57 AM, agya naila wrote: > >> Hello All, >> >> I am trying this patch on my machine Ubuntu 12.04 AMD64 both for Dom0 and >> DomU with Xen 4.2.2-pre compiling from sources also DRBD 8.3.11 but >> unfortunately it seem didn't work since I still got the message WARNING: >> suspend event channel unavailable, falling back to slow xenstore >> signalling. >> >> Regards, >> >> Agya >> >> On Tue, Feb 19, 2013 at 12:39 PM, Andrew Eross wrote: >> >>> Hi all, >>> >>> To close off on this, Shriram's patch worked great, thank you. >>> >>> So Ubuntu 12.10's standard generic kernel is now working fine as a dom0 >>> for Remus with Xen 4.1.4 (with the patch from this thread). >>> >>> I wrote up my full install instructions here: >>> >>> http://wiki.xen.org/wiki/Install_Xen_4.1.4_with_Remus_and_DRBD_on_Ubuntu_12.10 >>> >>> I also took a shot at a number of updates to: >>> http://wiki.xen.org/wiki/Remus >>> >>> And added these pages: >>> http://wiki.xen.org/wiki/Remus_PV_domU_requirements >>> http://wiki.xen.org/wiki/Remus_dom0_requirements >>> >>> Feedback very welcome, a lot of that information was a bit old, so I did >>> my best. >>> >>> Cheers, >>> Andrew >>> >>> >>> On Mon, Feb 18, 2013 at 8:26 PM, Shriram Rajagopalan >> > wrote: >>> >>>> ah darn. Yes, the 3.5 kernel has sch_plug in it. Unfortunately, the >>>> technique to initialize the sch_plug module is bit >>>> different with the module thats already mainline. You ll have to patch >>>> the qdisc.py python module. I ll submit the >>>> patch to xen devel soon. >>>> Mean while, can you try the patch below and see if it works ? >>>> >>>> Secondly, you said you were writing a blog about how you set it up. >>>> One of the remus users created a wiki >>>> remusha.wikidot.com, which has a whole tutorial on how to setup remus >>>> with Debian Squeeze. I have been under fire >>>> lately for a host of remus issues. It would be great if you could post >>>> your experiences on the wiki too. >>>> (http://remusha.wikidot.com/system:join) >>>> >>>> thanks >>>> shriram >>>> >>>> --- >>>> diff -r 6435f1edf24e tools/python/xen/remus/qdisc.py >>>> --- a/tools/python/xen/remus/qdisc.py Tue Jul 17 19:23:30 2012 -0400 >>>> +++ b/tools/python/xen/remus/qdisc.py Mon Feb 18 18:25:22 2013 -0500 >>>> @@ -1,6 +1,9 @@ >>>> import socket, struct >>>> >>>> import netlink >>>> +import platform >>>> + >>>> +kernelversion = platform.platform(terse=True).split("-")[1].split(".") >>>> >>>> qdisc_kinds = {} >>>> >>>> @@ -150,9 +153,14 @@ >>>> TC_PLUG_RELEASE = 1 >>>> >>>> class PlugQdisc(Qdisc): >>>> - fmt = 'I' >>>> >>>> def __init__(self, qdict=None): >>>> + if int(kernelversion[0]) >= 3 and int(kernelversion[1]) >= 4: >>>> + self.fmt = 'iI' >>>> + self.limit = 10000 >>>> + else: >>>> + self.fmt = 'I' >>>> + >>>> if not qdict: >>>> qdict = {'kind': 'plug', >>>> 'handle': TC_H_ROOT} >>>> @@ -161,7 +169,10 @@ >>>> self.action = 0 >>>> >>>> def pack(self): >>>> - return struct.pack(self.fmt, self.action) >>>> + if int(kernelversion[0]) >= 3 and int(kernelversion[1]) >= 4: >>>> + return struct.pack(self.fmt, self.action, self.limit) >>>> + else: >>>> + return struct.pack(self.fmt, self.action) >>>> >>>> def parse(self, args): >>>> if not args: >>>> >>> >>> >>> _______________________________________________ >>> Xen-users mailing list >>> Xen-users@lists.xen.org >>> http://lists.xen.org/xen-users >>> >> >> > --f46d0444036c69485f04d626e4bf Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Aha, sorry to mix it :), its clear now.

Regards,

Agya

On Wed, Feb 20, 20= 13 at 1:01 PM, Andrew Eross <eross@locatrix.com> wrote:
Hi Agya,

This patch doesn= 't fix the 'suspend event channel' issue, it just fixes the cra= sh from the first e-mail in this thread.


That discusses the suspend event channel issue.

Cheers,
Andrew


On Wed, Feb 20, 2013 a= t 8:57 AM, agya naila <agya.naila@gmail.com> wrote:
Hello All,

I am trying th= is patch on my machine Ubuntu 12.04 AMD64 both for Dom0 and DomU with Xen 4= .2.2-pre compiling from sources also DRBD 8.3.11 but unfortunately it seem = didn't work since I still got the message=A0WARNING: susp= end event channel unavailable, falling back to slow xenstore signalling.=A0=

Regards= ,

A= gya

On Tue, Feb 19, 2013 at 12:39 PM, = Andrew Eross <eross@locatrix.com> wrote:
Hi all,

To close off on this, Shriram's patch worked= great, thank you.

So Ubuntu 12.10's standard = generic kernel is now working fine as a dom0 for Remus with Xen 4.1.4 (with= the patch from this thread).

I wrote up my full install instructions here:
http://wiki.xen.org/wiki/Install_Xen_4.1= .4_with_Remus_and_DRBD_on_Ubuntu_12.10

I also took a shot at a number of updates to:
http://wiki.x= en.org/wiki/Remus

And added these pages:
Feedback very welcome, a lot of that information was a bit old,= so I did my best.

Cheers,
Andrew

=

On Mon, Feb 18, 2013 at 8:26 PM, Shrira= m Rajagopalan <rshriram@cs.ubc.ca> wrote:
ah darn. Yes, the 3.5 kernel has sch_plug in= it. Unfortunately, the
technique to initialize the sch_plug module is bit
different with the module thats already mainline. You ll have to patch
the qdisc.py python module. I ll submit the
patch to xen devel soon.
Mean while, can you try the patch below and see if it works ?

Secondly, you said you were writing a blog about how you set it up.
One of the remus users created a wiki
remusha.wikidot.co= m, which has a whole tutorial on how to setup remus
with Debian Squeeze. I have been under fire
lately for a host of remus issues. It would be great if you could post
your experiences on the wiki too.
(http:= //remusha.wikidot.com/system:join)

thanks
shriram

---
diff -r 6435f1edf24e tools/python/xen/remus/qdisc.py
--- a/tools/python/xen/remus/qdisc.py =A0 Tue Jul 17 19:23:30 2012 -0400 +++ b/tools/python/xen/remus/qdisc.py =A0 Mon Feb 18 18:25:22 2013 -0500 @@ -1,6 +1,9 @@
=A0import socket, struct

=A0import netlink
+import platform
+
+kernelversion =3D platform.platform(terse=3DTrue).split("-")[1].= split(".")

=A0qdisc_kinds =3D {}

@@ -150,9 +153,14 @@
=A0TC_PLUG_RELEASE =3D 1

=A0class PlugQdisc(Qdisc):
- =A0 =A0fmt =3D 'I'

=A0 =A0 =A0def __init__(self, qdict=3DNone):
+ =A0 =A0 =A0 =A0if int(kernelversion[0]) >=3D 3 and int(kernelversion[1= ]) >=3D 4:
+ =A0 =A0 =A0 =A0 =A0 =A0self.fmt =3D 'iI'
+ =A0 =A0 =A0 =A0 =A0 =A0self.limit =3D 10000
+ =A0 =A0 =A0 =A0else:
+ =A0 =A0 =A0 =A0 =A0 =A0self.fmt =3D 'I'
+
=A0 =A0 =A0 =A0 =A0if not qdict:
=A0 =A0 =A0 =A0 =A0 =A0 =A0qdict =3D {'kind': 'plug',
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 'handle': TC_H_ROOT} @@ -161,7 +169,10 @@
=A0 =A0 =A0 =A0 =A0self.action =3D 0

=A0 =A0 =A0def pack(self):
- =A0 =A0 =A0 =A0return struct.pack(self.fmt, self.action)
+ =A0 =A0 =A0 =A0if int(kernelversion[0]) >=3D 3 and int(kernelversion[1= ]) >=3D 4:
+ =A0 =A0 =A0 =A0 =A0 =A0return struct.pack(self.fmt, self.action, self.lim= it)
+ =A0 =A0 =A0 =A0else:
+ =A0 =A0 =A0 =A0 =A0 =A0return struct.pack(self.fmt, self.action)

=A0 =A0 =A0def parse(self, args):
=A0 =A0 =A0 =A0 =A0if not args:


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



--f46d0444036c69485f04d626e4bf-- --===============7131213750767599653== 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 --===============7131213750767599653==-- From xen-users-bounces@lists.xen.org Wed Feb 20 14:20:02 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 20 Feb 2013 14:20: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 1U8AVM-00081p-8p; Wed, 20 Feb 2013 14:18:40 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U8AVL-00081k-Bv for xen-users@lists.xen.org; Wed, 20 Feb 2013 14:18:39 +0000 Received: from [85.158.139.211:38215] by server-2.bemta-5.messagelabs.com id CD/76-16911-E3BD4215; Wed, 20 Feb 2013 14:18:38 +0000 X-Env-Sender: digvijaych@gmail.com X-Msg-Ref: server-7.tower-206.messagelabs.com!1361369893!17976365!1 X-Originating-IP: [209.85.215.52] 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.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 4153 invoked from network); 20 Feb 2013 14:18:14 -0000 Received: from mail-la0-f52.google.com (HELO mail-la0-f52.google.com) (209.85.215.52) by server-7.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 20 Feb 2013 14:18:14 -0000 Received: by mail-la0-f52.google.com with SMTP id fs12so7622705lab.39 for ; Wed, 20 Feb 2013 06:18:12 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:date:message-id:subject:from:to :content-type; bh=PYHc3k1ktrCCPIX6tYoSim2ytPbNhAaS+bIEdzIgy1o=; b=vsZ3MQO6qM50nra+DGXxLC7TZE1qH352kaypDicDupViJN8iC2myNPen76Gn8oE6pW SSh22Qt/AAZbwTdRJVbQu0kBSKW3i/56FjwLQ9nYDih1bdmPOvoV8TYCrxotcyUqnZLr kLDuynaskvPEZX5rmPtciu2450BKDdihlNsDsqhIqbNBPmjHv6gxQAgZg65Sw50PFIgd Wn4aLZzVn5XIZZnLhhqDRrp8wmEgVV5KKZd4ECeY1xDivPKOZU+tcKuHtuv+SIjpKoKb b8fxsPnTo+FoMtssQ7QLMKcvzvf7Nez1lSxCFfNGMc4aQbI6+DYbti9RvungEEPnYAme oiVw== MIME-Version: 1.0 X-Received: by 10.152.46.17 with SMTP id r17mr17953630lam.47.1361369891979; Wed, 20 Feb 2013 06:18:11 -0800 (PST) Received: by 10.112.101.65 with HTTP; Wed, 20 Feb 2013 06:18:11 -0800 (PST) Date: Wed, 20 Feb 2013 19:48:11 +0530 Message-ID: From: digvijay chauhan To: xen-users@lists.xen.org Subject: [Xen-users] how to understand code of live migration X-BeenThere: xen-users@lists.xen.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="===============2955959017180153379==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============2955959017180153379== Content-Type: multipart/alternative; boundary=bcaec5524106d1c0a704d628a023 --bcaec5524106d1c0a704d628a023 Content-Type: text/plain; charset=ISO-8859-1 Hello, I am doing my project on live migration using xen.If I want to start understanding the code so that i can do aalittle bit of improvement then how can i start it. regards, DigvijaySIngh --bcaec5524106d1c0a704d628a023 Content-Type: text/html; charset=ISO-8859-1 Hello, I am doing my project on live migration using xen.If I want to start understanding the code so that i can do aalittle bit of improvement then how can i start it.

regards,
DigvijaySIngh
--bcaec5524106d1c0a704d628a023-- --===============2955959017180153379== 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 --===============2955959017180153379==-- From xen-users-bounces@lists.xen.org Wed Feb 20 14:20:02 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 20 Feb 2013 14:20: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 1U8AVM-00081p-8p; Wed, 20 Feb 2013 14:18:40 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U8AVL-00081k-Bv for xen-users@lists.xen.org; Wed, 20 Feb 2013 14:18:39 +0000 Received: from [85.158.139.211:38215] by server-2.bemta-5.messagelabs.com id CD/76-16911-E3BD4215; Wed, 20 Feb 2013 14:18:38 +0000 X-Env-Sender: digvijaych@gmail.com X-Msg-Ref: server-7.tower-206.messagelabs.com!1361369893!17976365!1 X-Originating-IP: [209.85.215.52] 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.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 4153 invoked from network); 20 Feb 2013 14:18:14 -0000 Received: from mail-la0-f52.google.com (HELO mail-la0-f52.google.com) (209.85.215.52) by server-7.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 20 Feb 2013 14:18:14 -0000 Received: by mail-la0-f52.google.com with SMTP id fs12so7622705lab.39 for ; Wed, 20 Feb 2013 06:18:12 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:date:message-id:subject:from:to :content-type; bh=PYHc3k1ktrCCPIX6tYoSim2ytPbNhAaS+bIEdzIgy1o=; b=vsZ3MQO6qM50nra+DGXxLC7TZE1qH352kaypDicDupViJN8iC2myNPen76Gn8oE6pW SSh22Qt/AAZbwTdRJVbQu0kBSKW3i/56FjwLQ9nYDih1bdmPOvoV8TYCrxotcyUqnZLr kLDuynaskvPEZX5rmPtciu2450BKDdihlNsDsqhIqbNBPmjHv6gxQAgZg65Sw50PFIgd Wn4aLZzVn5XIZZnLhhqDRrp8wmEgVV5KKZd4ECeY1xDivPKOZU+tcKuHtuv+SIjpKoKb b8fxsPnTo+FoMtssQ7QLMKcvzvf7Nez1lSxCFfNGMc4aQbI6+DYbti9RvungEEPnYAme oiVw== MIME-Version: 1.0 X-Received: by 10.152.46.17 with SMTP id r17mr17953630lam.47.1361369891979; Wed, 20 Feb 2013 06:18:11 -0800 (PST) Received: by 10.112.101.65 with HTTP; Wed, 20 Feb 2013 06:18:11 -0800 (PST) Date: Wed, 20 Feb 2013 19:48:11 +0530 Message-ID: From: digvijay chauhan To: xen-users@lists.xen.org Subject: [Xen-users] how to understand code of live migration X-BeenThere: xen-users@lists.xen.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="===============2955959017180153379==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============2955959017180153379== Content-Type: multipart/alternative; boundary=bcaec5524106d1c0a704d628a023 --bcaec5524106d1c0a704d628a023 Content-Type: text/plain; charset=ISO-8859-1 Hello, I am doing my project on live migration using xen.If I want to start understanding the code so that i can do aalittle bit of improvement then how can i start it. regards, DigvijaySIngh --bcaec5524106d1c0a704d628a023 Content-Type: text/html; charset=ISO-8859-1 Hello, I am doing my project on live migration using xen.If I want to start understanding the code so that i can do aalittle bit of improvement then how can i start it.

regards,
DigvijaySIngh
--bcaec5524106d1c0a704d628a023-- --===============2955959017180153379== 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 --===============2955959017180153379==-- From xen-users-bounces@lists.xen.org Wed Feb 20 15:34:15 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 20 Feb 2013 15:34: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 1U8BfC-00013Z-WB; Wed, 20 Feb 2013 15:32:54 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U8BfC-00013T-8Z for xen-users@lists.xen.org; Wed, 20 Feb 2013 15:32:54 +0000 Received: from [85.158.139.211:25327] by server-10.bemta-5.messagelabs.com id C2/3F-04697-5ACE4215; Wed, 20 Feb 2013 15:32:53 +0000 X-Env-Sender: s.munaut@whatever-company.com X-Msg-Ref: server-12.tower-206.messagelabs.com!1361374372!18378399!1 X-Originating-IP: [209.85.214.51] X-SpamReason: No, hits=0.3 required=7.0 tests=RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 26116 invoked from network); 20 Feb 2013 15:32:52 -0000 Received: from mail-bk0-f51.google.com (HELO mail-bk0-f51.google.com) (209.85.214.51) by server-12.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 20 Feb 2013 15:32:52 -0000 Received: by mail-bk0-f51.google.com with SMTP id ik5so3628984bkc.24 for ; Wed, 20 Feb 2013 07:32:52 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type:x-gm-message-state; bh=10q4T50bAlKjqLmLLLecAM5eyoM0kNeaNKotKVXXWHI=; b=Wliuf71YKN8LLFxXWNFr7VuFbwLGIMZRTqp4K8AhM6OLNlN+7OoqPW2xZdrTF3+Vdq ri8E6qd4wRI9BZic9jH4kMdS0JVvP5UhltVic7+B98OI+fy/jRvBFf1ZSWVTZp5pnku/ 7ZB6Y/s0oW+kOydwc1jB1u5QmlgwdV3IAtB19kzkZmhcBQ4gHtzikj1PYN6vj++nxhin E6Z1Eb3ZaOZ/BPUP8Yk+dwnb8GzRAF66unLRYwzfX1DYTpp7rIQOUkWFjNfntZesrwyI J3u/K2gxFDHdAeBH+31nwXmurSDfd1TuatR8eb4pk6QgFSywiCKSNb7JmjqO9/1c2Ia5 sBFA== MIME-Version: 1.0 X-Received: by 10.205.138.148 with SMTP id is20mr8922969bkc.45.1361374372366; Wed, 20 Feb 2013 07:32:52 -0800 (PST) Received: by 10.205.137.141 with HTTP; Wed, 20 Feb 2013 07:32:52 -0800 (PST) In-Reply-To: <1361351798.1051.142.camel@zakaz.uk.xensource.com> References: <1361286109.1051.119.camel@zakaz.uk.xensource.com> <1361351798.1051.142.camel@zakaz.uk.xensource.com> Date: Wed, 20 Feb 2013 16:32:52 +0100 Message-ID: From: Sylvain Munaut To: Ian Campbell X-Gm-Message-State: ALoCoQnnMaYur61DN6C128PE/u7RPja9SEOJ2MYNDIzRuQGsvAStq2ta0IxnbN427VgT1U/N5z7s Cc: "xen-users@lists.xen.org" Subject: Re: [Xen-users] Xen 4.1.2 - stub domains for IO. Not working ? X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: 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, > Odd for the crash to be totally silent in all the logs. When I tried to replace the binary xen.gz and ioemu-stubdom.gz with debug=y version, it started working. It seems it might be linked to the debian build system that produces a ioemu-stubdom.gz which is much smaller than the one produced by a 'normal' ( ./configure && make ) complilation. I'm looking into that. In any case, thanks for the help, now I have a lead to follow. Cheers, Sylvain _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Wed Feb 20 15:34:15 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 20 Feb 2013 15:34: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 1U8BfC-00013Z-WB; Wed, 20 Feb 2013 15:32:54 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U8BfC-00013T-8Z for xen-users@lists.xen.org; Wed, 20 Feb 2013 15:32:54 +0000 Received: from [85.158.139.211:25327] by server-10.bemta-5.messagelabs.com id C2/3F-04697-5ACE4215; Wed, 20 Feb 2013 15:32:53 +0000 X-Env-Sender: s.munaut@whatever-company.com X-Msg-Ref: server-12.tower-206.messagelabs.com!1361374372!18378399!1 X-Originating-IP: [209.85.214.51] X-SpamReason: No, hits=0.3 required=7.0 tests=RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 26116 invoked from network); 20 Feb 2013 15:32:52 -0000 Received: from mail-bk0-f51.google.com (HELO mail-bk0-f51.google.com) (209.85.214.51) by server-12.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 20 Feb 2013 15:32:52 -0000 Received: by mail-bk0-f51.google.com with SMTP id ik5so3628984bkc.24 for ; Wed, 20 Feb 2013 07:32:52 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type:x-gm-message-state; bh=10q4T50bAlKjqLmLLLecAM5eyoM0kNeaNKotKVXXWHI=; b=Wliuf71YKN8LLFxXWNFr7VuFbwLGIMZRTqp4K8AhM6OLNlN+7OoqPW2xZdrTF3+Vdq ri8E6qd4wRI9BZic9jH4kMdS0JVvP5UhltVic7+B98OI+fy/jRvBFf1ZSWVTZp5pnku/ 7ZB6Y/s0oW+kOydwc1jB1u5QmlgwdV3IAtB19kzkZmhcBQ4gHtzikj1PYN6vj++nxhin E6Z1Eb3ZaOZ/BPUP8Yk+dwnb8GzRAF66unLRYwzfX1DYTpp7rIQOUkWFjNfntZesrwyI J3u/K2gxFDHdAeBH+31nwXmurSDfd1TuatR8eb4pk6QgFSywiCKSNb7JmjqO9/1c2Ia5 sBFA== MIME-Version: 1.0 X-Received: by 10.205.138.148 with SMTP id is20mr8922969bkc.45.1361374372366; Wed, 20 Feb 2013 07:32:52 -0800 (PST) Received: by 10.205.137.141 with HTTP; Wed, 20 Feb 2013 07:32:52 -0800 (PST) In-Reply-To: <1361351798.1051.142.camel@zakaz.uk.xensource.com> References: <1361286109.1051.119.camel@zakaz.uk.xensource.com> <1361351798.1051.142.camel@zakaz.uk.xensource.com> Date: Wed, 20 Feb 2013 16:32:52 +0100 Message-ID: From: Sylvain Munaut To: Ian Campbell X-Gm-Message-State: ALoCoQnnMaYur61DN6C128PE/u7RPja9SEOJ2MYNDIzRuQGsvAStq2ta0IxnbN427VgT1U/N5z7s Cc: "xen-users@lists.xen.org" Subject: Re: [Xen-users] Xen 4.1.2 - stub domains for IO. Not working ? X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: 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, > Odd for the crash to be totally silent in all the logs. When I tried to replace the binary xen.gz and ioemu-stubdom.gz with debug=y version, it started working. It seems it might be linked to the debian build system that produces a ioemu-stubdom.gz which is much smaller than the one produced by a 'normal' ( ./configure && make ) complilation. I'm looking into that. In any case, thanks for the help, now I have a lead to follow. Cheers, Sylvain _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Thu Feb 21 03:00:35 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 21 Feb 2013 03:00: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 1U8MNI-0001z6-C2; Thu, 21 Feb 2013 02:59:08 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U8MNH-0001yy-8i for xen-users@lists.xen.org; Thu, 21 Feb 2013 02:59:07 +0000 Received: from [85.158.139.83:10595] by server-4.bemta-5.messagelabs.com id 4D/55-29496-A7D85215; Thu, 21 Feb 2013 02:59:06 +0000 X-Env-Sender: jaceksburghardt@gmail.com X-Msg-Ref: server-9.tower-182.messagelabs.com!1361415544!27518829!1 X-Originating-IP: [209.85.223.182] 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.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 13748 invoked from network); 21 Feb 2013 02:59:05 -0000 Received: from mail-ie0-f182.google.com (HELO mail-ie0-f182.google.com) (209.85.223.182) by server-9.tower-182.messagelabs.com with RC4-SHA encrypted SMTP; 21 Feb 2013 02:59:05 -0000 Received: by mail-ie0-f182.google.com with SMTP id k14so10806413iea.13 for ; Wed, 20 Feb 2013 18:59:04 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:date:message-id:subject:from:to :content-type; bh=tHOYVrrpO4UhizhoR7zcpZJ710vl0YsEz1NjO7bUCAw=; b=i3RLbxzac+k0c+jMBy0NWef4Z6v9uf3OftpGkCi4nYSdj5KmKQPLu/Rgc6OhmICYQV 963fYC6hO+IociRv+GKlT36ZUsh2ylRgjphfQSnAKoHrN7m09NnJhNVuICmAN6T77uwp 1ZHQjX4ViyzhjA0UzEJum7f8b+hxkzPWc/Vqj6q3aLV/oeX+Rq+59dtnpK9cVzeiT6Bw SSwKe8OFUxU16GweVHuOMiDPNQsWG/+N1T4tGDIntEYsOe3VDpM82FnU3FPnsh51QsMN 7xp0FgW0dF5KANYNurEJq40jeDiI4GXdHpZabjzmwyjhLFSnBuci/6fRjLzwXGb1VAhE Sl0A== MIME-Version: 1.0 X-Received: by 10.50.196.130 with SMTP id im2mr11904151igc.90.1361415543977; Wed, 20 Feb 2013 18:59:03 -0800 (PST) Received: by 10.42.41.5 with HTTP; Wed, 20 Feb 2013 18:59:03 -0800 (PST) Date: Wed, 20 Feb 2013 19:59:03 -0700 Message-ID: From: jacek burghardt To: xen-users Subject: [Xen-users] couple xen 4.3 issues X-BeenThere: xen-users@lists.xen.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="===============0550747239112201064==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============0550747239112201064== Content-Type: multipart/alternative; boundary=14dae9341071e3f72504d63341ec --14dae9341071e3f72504d63341ec Content-Type: text/plain; charset=ISO-8859-1 Can someone point me in right direction how I can patch qemu at compile time ? I am getting this error and there is patch for it. How I can apply it Fix generating qemu-doc.html with texinfo 5 LC_ALL=C makeinfo --no-headers --no-split --number-sections --html qemu-doc.texi -o qemu-doc.html ./qemu-options.texi:1521: unknown command `list' ./qemu-options.texi:1521: table requires an argument: the formatter for @item ./qemu-options.texi:1521: warning: @table has text but no @item Also I am getting this qemu-system-i38[1197]: segfault at 1 ip 00007f27e112c330 sp 00007fff29e96fc0 error 4 in qemu-system-i386[7f27e0fec000+3bb000] Does anyone knows what is causing this ? --14dae9341071e3f72504d63341ec Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Can someone point me in right direction how I can patch qemu at compile tim= e ?
I am getting this error and there is patch for it. How I can apply = it

Fix generating qemu-doc.html with texinfo 5

LC_ALL=3DC makeinfo --no-headers --no-split --number-sections --html=
=20
qemu-doc.texi -o qemu-doc.html
./qemu-options.texi:1521: unknown command `list'
./qemu-options.texi:1521: table requires an argument: the formatter for @it=
em
./qemu-options.texi:1521: warning: @table has text but no @item
Also I a=
m getting this 
qemu-system-i38[1197]: segfault at 1 ip 00007f27e112c330=
 sp 00007fff29e96fc0 error 4 in qemu-system-i386[7f27e0fec000+3bb000]

Does anyone knows what is causing this ?
--14dae9341071e3f72504d63341ec-- --===============0550747239112201064== 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 --===============0550747239112201064==-- From xen-users-bounces@lists.xen.org Thu Feb 21 03:00:35 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 21 Feb 2013 03:00: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 1U8MNI-0001z6-C2; Thu, 21 Feb 2013 02:59:08 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U8MNH-0001yy-8i for xen-users@lists.xen.org; Thu, 21 Feb 2013 02:59:07 +0000 Received: from [85.158.139.83:10595] by server-4.bemta-5.messagelabs.com id 4D/55-29496-A7D85215; Thu, 21 Feb 2013 02:59:06 +0000 X-Env-Sender: jaceksburghardt@gmail.com X-Msg-Ref: server-9.tower-182.messagelabs.com!1361415544!27518829!1 X-Originating-IP: [209.85.223.182] 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.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 13748 invoked from network); 21 Feb 2013 02:59:05 -0000 Received: from mail-ie0-f182.google.com (HELO mail-ie0-f182.google.com) (209.85.223.182) by server-9.tower-182.messagelabs.com with RC4-SHA encrypted SMTP; 21 Feb 2013 02:59:05 -0000 Received: by mail-ie0-f182.google.com with SMTP id k14so10806413iea.13 for ; Wed, 20 Feb 2013 18:59:04 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:date:message-id:subject:from:to :content-type; bh=tHOYVrrpO4UhizhoR7zcpZJ710vl0YsEz1NjO7bUCAw=; b=i3RLbxzac+k0c+jMBy0NWef4Z6v9uf3OftpGkCi4nYSdj5KmKQPLu/Rgc6OhmICYQV 963fYC6hO+IociRv+GKlT36ZUsh2ylRgjphfQSnAKoHrN7m09NnJhNVuICmAN6T77uwp 1ZHQjX4ViyzhjA0UzEJum7f8b+hxkzPWc/Vqj6q3aLV/oeX+Rq+59dtnpK9cVzeiT6Bw SSwKe8OFUxU16GweVHuOMiDPNQsWG/+N1T4tGDIntEYsOe3VDpM82FnU3FPnsh51QsMN 7xp0FgW0dF5KANYNurEJq40jeDiI4GXdHpZabjzmwyjhLFSnBuci/6fRjLzwXGb1VAhE Sl0A== MIME-Version: 1.0 X-Received: by 10.50.196.130 with SMTP id im2mr11904151igc.90.1361415543977; Wed, 20 Feb 2013 18:59:03 -0800 (PST) Received: by 10.42.41.5 with HTTP; Wed, 20 Feb 2013 18:59:03 -0800 (PST) Date: Wed, 20 Feb 2013 19:59:03 -0700 Message-ID: From: jacek burghardt To: xen-users Subject: [Xen-users] couple xen 4.3 issues X-BeenThere: xen-users@lists.xen.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="===============0550747239112201064==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============0550747239112201064== Content-Type: multipart/alternative; boundary=14dae9341071e3f72504d63341ec --14dae9341071e3f72504d63341ec Content-Type: text/plain; charset=ISO-8859-1 Can someone point me in right direction how I can patch qemu at compile time ? I am getting this error and there is patch for it. How I can apply it Fix generating qemu-doc.html with texinfo 5 LC_ALL=C makeinfo --no-headers --no-split --number-sections --html qemu-doc.texi -o qemu-doc.html ./qemu-options.texi:1521: unknown command `list' ./qemu-options.texi:1521: table requires an argument: the formatter for @item ./qemu-options.texi:1521: warning: @table has text but no @item Also I am getting this qemu-system-i38[1197]: segfault at 1 ip 00007f27e112c330 sp 00007fff29e96fc0 error 4 in qemu-system-i386[7f27e0fec000+3bb000] Does anyone knows what is causing this ? --14dae9341071e3f72504d63341ec Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Can someone point me in right direction how I can patch qemu at compile tim= e ?
I am getting this error and there is patch for it. How I can apply = it

Fix generating qemu-doc.html with texinfo 5

LC_ALL=3DC makeinfo --no-headers --no-split --number-sections --html=
=20
qemu-doc.texi -o qemu-doc.html
./qemu-options.texi:1521: unknown command `list'
./qemu-options.texi:1521: table requires an argument: the formatter for @it=
em
./qemu-options.texi:1521: warning: @table has text but no @item
Also I a=
m getting this 
qemu-system-i38[1197]: segfault at 1 ip 00007f27e112c330=
 sp 00007fff29e96fc0 error 4 in qemu-system-i386[7f27e0fec000+3bb000]

Does anyone knows what is causing this ?
--14dae9341071e3f72504d63341ec-- --===============0550747239112201064== 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 --===============0550747239112201064==-- From xen-users-bounces@lists.xen.org Thu Feb 21 04:55:46 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 21 Feb 2013 04: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 1U8OAe-0003fQ-6L; Thu, 21 Feb 2013 04:54:12 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U8HQM-0001yS-G7 for xen-users@lists.xen.org; Wed, 20 Feb 2013 21:41:58 +0000 Received: from [85.158.137.99:32622] by server-7.bemta-3.messagelabs.com id B0/04-10367-52345215; Wed, 20 Feb 2013 21:41:57 +0000 X-Env-Sender: Dale.Galekovic@pace.com X-Msg-Ref: server-3.tower-217.messagelabs.com!1361396515!12233850!1 X-Originating-IP: [65.55.88.13] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 29393 invoked from network); 20 Feb 2013 21:41:57 -0000 Received: from tx2ehsobe003.messaging.microsoft.com (HELO tx2outboundpool.messaging.microsoft.com) (65.55.88.13) by server-3.tower-217.messagelabs.com with AES128-SHA encrypted SMTP; 20 Feb 2013 21:41:57 -0000 Received: from mail62-tx2-R.bigfish.com (10.9.14.244) by TX2EHSOBE010.bigfish.com (10.9.40.30) with Microsoft SMTP Server id 14.1.225.23; Wed, 20 Feb 2013 21:41:55 +0000 Received: from mail62-tx2 (localhost [127.0.0.1]) by mail62-tx2-R.bigfish.com (Postfix) with ESMTP id 48F3D2E00FC for ; Wed, 20 Feb 2013 21:41:55 +0000 (UTC) X-Forefront-Antispam-Report: CIP:157.56.232.213; KIP:(null); UIP:(null); IPV:NLI; H:BLUPRD0511HT004.namprd05.prod.outlook.com; RD:none; EFVD:NLI X-SpamScore: -1 X-BigFish: PS-1(zz1443Izz1f42h1ee6h1de0h1202h1e76h1d1ah1d2ahzzz2dh2a8h668h839h93fhd25hf0ah1288h12a5h12a9h12bdh137ah13b6h1441h1504h1537h153bh15d0h162dh1631h1758h18e1h1946h19b5h19ceh1155h) Received: from mail62-tx2 (localhost.localdomain [127.0.0.1]) by mail62-tx2 (MessageSwitch) id 136139651472779_6119; Wed, 20 Feb 2013 21:41:54 +0000 (UTC) Received: from TX2EHSMHS017.bigfish.com (unknown [10.9.14.242]) by mail62-tx2.bigfish.com (Postfix) with ESMTP id 0CECD26007F for ; Wed, 20 Feb 2013 21:41:54 +0000 (UTC) Received: from BLUPRD0511HT004.namprd05.prod.outlook.com (157.56.232.213) by TX2EHSMHS017.bigfish.com (10.9.99.117) with Microsoft SMTP Server (TLS) id 14.1.225.23; Wed, 20 Feb 2013 21:41:53 +0000 Received: from BLUPRD0511MB426.namprd05.prod.outlook.com ([169.254.12.246]) by BLUPRD0511HT004.namprd05.prod.outlook.com ([10.255.135.167]) with mapi id 14.16.0263.000; Wed, 20 Feb 2013 21:41:53 +0000 From: Dale Galekovic To: "xen-users@lists.xen.org" Thread-Topic: [Xen-users] Problem building Tools Xen 4.2 Thread-Index: Ac4LvFSnAP6IHeNcTPuUmK8jVqw1AwCwSjcAABVXM8AANqz3kA== Date: Wed, 20 Feb 2013 21:41:52 +0000 Message-ID: <374DD7FF31C7AB4EA7E0B48BD2049C821F9BE083@BLUPRD0511MB426.namprd05.prod.outlook.com> References: <374DD7FF31C7AB4EA7E0B48BD2049C821F9BBB71@BLUPRD0511MB426.namprd05.prod.outlook.com> <1361263538.1051.52.camel@zakaz.uk.xensource.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [209.156.171.253] MIME-Version: 1.0 X-OriginatorOrg: pace.com X-Mailman-Approved-At: Thu, 21 Feb 2013 04:54:10 +0000 Subject: [Xen-users] FW: Problem building Tools Xen 4.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 Everything seems to be up and running but the Graphical User Interface (GUI) has no login screen just a circle. The system is up... I can ssh or vnc in to the system ... It's a Dell Optiplex 990 I7 ... It seems to stop loading the GUI ... Ideas ?? Also trying to create a virtual Win7 machine and getting the following error [root@Dales-xen-server xen]# xm create win7-64.cfg Using config file "./win7-64.cfg". Error: Errors were found at line 1 while processing ./win7-64.cfg: kernel = "/usr/lib/xen/boot/hvmloader" Thanks in advance Dale G. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Thu Feb 21 04:55:46 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 21 Feb 2013 04: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 1U8OAe-0003fQ-6L; Thu, 21 Feb 2013 04:54:12 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U8HQM-0001yS-G7 for xen-users@lists.xen.org; Wed, 20 Feb 2013 21:41:58 +0000 Received: from [85.158.137.99:32622] by server-7.bemta-3.messagelabs.com id B0/04-10367-52345215; Wed, 20 Feb 2013 21:41:57 +0000 X-Env-Sender: Dale.Galekovic@pace.com X-Msg-Ref: server-3.tower-217.messagelabs.com!1361396515!12233850!1 X-Originating-IP: [65.55.88.13] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 29393 invoked from network); 20 Feb 2013 21:41:57 -0000 Received: from tx2ehsobe003.messaging.microsoft.com (HELO tx2outboundpool.messaging.microsoft.com) (65.55.88.13) by server-3.tower-217.messagelabs.com with AES128-SHA encrypted SMTP; 20 Feb 2013 21:41:57 -0000 Received: from mail62-tx2-R.bigfish.com (10.9.14.244) by TX2EHSOBE010.bigfish.com (10.9.40.30) with Microsoft SMTP Server id 14.1.225.23; Wed, 20 Feb 2013 21:41:55 +0000 Received: from mail62-tx2 (localhost [127.0.0.1]) by mail62-tx2-R.bigfish.com (Postfix) with ESMTP id 48F3D2E00FC for ; Wed, 20 Feb 2013 21:41:55 +0000 (UTC) X-Forefront-Antispam-Report: CIP:157.56.232.213; KIP:(null); UIP:(null); IPV:NLI; H:BLUPRD0511HT004.namprd05.prod.outlook.com; RD:none; EFVD:NLI X-SpamScore: -1 X-BigFish: PS-1(zz1443Izz1f42h1ee6h1de0h1202h1e76h1d1ah1d2ahzzz2dh2a8h668h839h93fhd25hf0ah1288h12a5h12a9h12bdh137ah13b6h1441h1504h1537h153bh15d0h162dh1631h1758h18e1h1946h19b5h19ceh1155h) Received: from mail62-tx2 (localhost.localdomain [127.0.0.1]) by mail62-tx2 (MessageSwitch) id 136139651472779_6119; Wed, 20 Feb 2013 21:41:54 +0000 (UTC) Received: from TX2EHSMHS017.bigfish.com (unknown [10.9.14.242]) by mail62-tx2.bigfish.com (Postfix) with ESMTP id 0CECD26007F for ; Wed, 20 Feb 2013 21:41:54 +0000 (UTC) Received: from BLUPRD0511HT004.namprd05.prod.outlook.com (157.56.232.213) by TX2EHSMHS017.bigfish.com (10.9.99.117) with Microsoft SMTP Server (TLS) id 14.1.225.23; Wed, 20 Feb 2013 21:41:53 +0000 Received: from BLUPRD0511MB426.namprd05.prod.outlook.com ([169.254.12.246]) by BLUPRD0511HT004.namprd05.prod.outlook.com ([10.255.135.167]) with mapi id 14.16.0263.000; Wed, 20 Feb 2013 21:41:53 +0000 From: Dale Galekovic To: "xen-users@lists.xen.org" Thread-Topic: [Xen-users] Problem building Tools Xen 4.2 Thread-Index: Ac4LvFSnAP6IHeNcTPuUmK8jVqw1AwCwSjcAABVXM8AANqz3kA== Date: Wed, 20 Feb 2013 21:41:52 +0000 Message-ID: <374DD7FF31C7AB4EA7E0B48BD2049C821F9BE083@BLUPRD0511MB426.namprd05.prod.outlook.com> References: <374DD7FF31C7AB4EA7E0B48BD2049C821F9BBB71@BLUPRD0511MB426.namprd05.prod.outlook.com> <1361263538.1051.52.camel@zakaz.uk.xensource.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [209.156.171.253] MIME-Version: 1.0 X-OriginatorOrg: pace.com X-Mailman-Approved-At: Thu, 21 Feb 2013 04:54:10 +0000 Subject: [Xen-users] FW: Problem building Tools Xen 4.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 Everything seems to be up and running but the Graphical User Interface (GUI) has no login screen just a circle. The system is up... I can ssh or vnc in to the system ... It's a Dell Optiplex 990 I7 ... It seems to stop loading the GUI ... Ideas ?? Also trying to create a virtual Win7 machine and getting the following error [root@Dales-xen-server xen]# xm create win7-64.cfg Using config file "./win7-64.cfg". Error: Errors were found at line 1 while processing ./win7-64.cfg: kernel = "/usr/lib/xen/boot/hvmloader" Thanks in advance Dale G. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Thu Feb 21 08:22:39 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 21 Feb 2013 08:22: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 1U8RP2-0006xt-9a; Thu, 21 Feb 2013 08:21:16 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U8RP0-0006xn-Ns for xen-users@lists.xen.org; Thu, 21 Feb 2013 08:21:14 +0000 Received: from [85.158.139.211:2329] by server-11.bemta-5.messagelabs.com id E8/62-19159-AF8D5215; Thu, 21 Feb 2013 08:21:14 +0000 X-Env-Sender: james@dingwall.me.uk X-Msg-Ref: server-15.tower-206.messagelabs.com!1361434873!18586636!1 X-Originating-IP: [81.103.221.49] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 19156 invoked from network); 21 Feb 2013 08:21:13 -0000 Received: from mtaout03-winn.ispmail.ntl.com (HELO mtaout03-winn.ispmail.ntl.com) (81.103.221.49) by server-15.tower-206.messagelabs.com with SMTP; 21 Feb 2013 08:21:13 -0000 Received: from know-smtpout-1.server.virginmedia.net ([62.254.123.1]) by mtaout03-winn.ispmail.ntl.com (InterMail vM.7.08.04.00 201-2186-134-20080326) with ESMTP id <20130221082112.DNHS1579.mtaout03-winn.ispmail.ntl.com@know-smtpout-1.server.virginmedia.net> for ; Thu, 21 Feb 2013 08:21:12 +0000 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 1U8ROg-0005ow-S0 for xen-users@lists.xen.org; Thu, 21 Feb 2013 08:20:55 +0000 Received: (qmail 22872 invoked from network); 21 Feb 2013 08:20:54 -0000 Received: from behemoth.dingwall.me.uk (192.168.1.5) by mail0.xen.dingwall.me.uk with SMTP; 21 Feb 2013 08:20:54 -0000 Received: by behemoth.dingwall.me.uk (Postfix, from userid 1000) id A53FBD08C20; Thu, 21 Feb 2013 08:20:54 +0000 (GMT) Date: Thu, 21 Feb 2013 08:20:54 +0000 From: James Dingwall To: Dale Galekovic Message-ID: <20130221082054.GA1226@dingwall.me.uk> References: <374DD7FF31C7AB4EA7E0B48BD2049C821F9BBB71@BLUPRD0511MB426.namprd05.prod.outlook.com> <1361263538.1051.52.camel@zakaz.uk.xensource.com> <374DD7FF31C7AB4EA7E0B48BD2049C821F9BE083@BLUPRD0511MB426.namprd05.prod.outlook.com> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <374DD7FF31C7AB4EA7E0B48BD2049C821F9BE083@BLUPRD0511MB426.namprd05.prod.outlook.com> User-Agent: Mutt/1.5.21 (2010-09-15) X-Cloudmark-Analysis: v=1.1 cv=AUhbpHVS+xhHrj9wLCYAQoYnFLYUZdbP8UM0GmH2jwk= c=1 sm=0 a=wom5GMh1gUkA:10 a=mudGjsIINg4A:10 a=kj9zAlcOel0A:10 a=f0u3QA159R8VpMQk02EA:9 a=CjuIK1q_8ugA:10 a=HpAAvcLHHh0Zw7uRqdWCyQ==:117 Cc: "xen-users@lists.xen.org" Subject: Re: [Xen-users] FW: Problem building Tools Xen 4.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 > Also trying to create a virtual Win7 machine and getting the following error > > [root@Dales-xen-server xen]# xm create win7-64.cfg > Using config file "./win7-64.cfg". > Error: Errors were found at line 1 while processing ./win7-64.cfg: > kernel = "/usr/lib/xen/boot/hvmloader" I don't think this line is needed. The options I used to start a Windows guest with a stubdom are: # The domain build function. Default is 'generic' (pv) alternately 'hvm'. builder = "hvm" # If the builder is HVM the following options are available: # Add optimisations to support Windows HVM guests viridian = 1 # Use a stubdom for the device emulation for HVM device_model_stubdomain_override = 1 # For HVM pick the boot order for the emualted BIOS # boot on floppy (a), hard disk (c), Network (n) or CD-ROM (d) # default: hard disk, cd-rom, floppy boot = "c" Regards, James _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Thu Feb 21 08:22:39 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 21 Feb 2013 08:22: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 1U8RP2-0006xt-9a; Thu, 21 Feb 2013 08:21:16 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U8RP0-0006xn-Ns for xen-users@lists.xen.org; Thu, 21 Feb 2013 08:21:14 +0000 Received: from [85.158.139.211:2329] by server-11.bemta-5.messagelabs.com id E8/62-19159-AF8D5215; Thu, 21 Feb 2013 08:21:14 +0000 X-Env-Sender: james@dingwall.me.uk X-Msg-Ref: server-15.tower-206.messagelabs.com!1361434873!18586636!1 X-Originating-IP: [81.103.221.49] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 19156 invoked from network); 21 Feb 2013 08:21:13 -0000 Received: from mtaout03-winn.ispmail.ntl.com (HELO mtaout03-winn.ispmail.ntl.com) (81.103.221.49) by server-15.tower-206.messagelabs.com with SMTP; 21 Feb 2013 08:21:13 -0000 Received: from know-smtpout-1.server.virginmedia.net ([62.254.123.1]) by mtaout03-winn.ispmail.ntl.com (InterMail vM.7.08.04.00 201-2186-134-20080326) with ESMTP id <20130221082112.DNHS1579.mtaout03-winn.ispmail.ntl.com@know-smtpout-1.server.virginmedia.net> for ; Thu, 21 Feb 2013 08:21:12 +0000 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 1U8ROg-0005ow-S0 for xen-users@lists.xen.org; Thu, 21 Feb 2013 08:20:55 +0000 Received: (qmail 22872 invoked from network); 21 Feb 2013 08:20:54 -0000 Received: from behemoth.dingwall.me.uk (192.168.1.5) by mail0.xen.dingwall.me.uk with SMTP; 21 Feb 2013 08:20:54 -0000 Received: by behemoth.dingwall.me.uk (Postfix, from userid 1000) id A53FBD08C20; Thu, 21 Feb 2013 08:20:54 +0000 (GMT) Date: Thu, 21 Feb 2013 08:20:54 +0000 From: James Dingwall To: Dale Galekovic Message-ID: <20130221082054.GA1226@dingwall.me.uk> References: <374DD7FF31C7AB4EA7E0B48BD2049C821F9BBB71@BLUPRD0511MB426.namprd05.prod.outlook.com> <1361263538.1051.52.camel@zakaz.uk.xensource.com> <374DD7FF31C7AB4EA7E0B48BD2049C821F9BE083@BLUPRD0511MB426.namprd05.prod.outlook.com> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <374DD7FF31C7AB4EA7E0B48BD2049C821F9BE083@BLUPRD0511MB426.namprd05.prod.outlook.com> User-Agent: Mutt/1.5.21 (2010-09-15) X-Cloudmark-Analysis: v=1.1 cv=AUhbpHVS+xhHrj9wLCYAQoYnFLYUZdbP8UM0GmH2jwk= c=1 sm=0 a=wom5GMh1gUkA:10 a=mudGjsIINg4A:10 a=kj9zAlcOel0A:10 a=f0u3QA159R8VpMQk02EA:9 a=CjuIK1q_8ugA:10 a=HpAAvcLHHh0Zw7uRqdWCyQ==:117 Cc: "xen-users@lists.xen.org" Subject: Re: [Xen-users] FW: Problem building Tools Xen 4.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 > Also trying to create a virtual Win7 machine and getting the following error > > [root@Dales-xen-server xen]# xm create win7-64.cfg > Using config file "./win7-64.cfg". > Error: Errors were found at line 1 while processing ./win7-64.cfg: > kernel = "/usr/lib/xen/boot/hvmloader" I don't think this line is needed. The options I used to start a Windows guest with a stubdom are: # The domain build function. Default is 'generic' (pv) alternately 'hvm'. builder = "hvm" # If the builder is HVM the following options are available: # Add optimisations to support Windows HVM guests viridian = 1 # Use a stubdom for the device emulation for HVM device_model_stubdomain_override = 1 # For HVM pick the boot order for the emualted BIOS # boot on floppy (a), hard disk (c), Network (n) or CD-ROM (d) # default: hard disk, cd-rom, floppy boot = "c" Regards, James _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Thu Feb 21 09:21:01 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 21 Feb 2013 09:21: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 1U8SJn-0008DL-HV; Thu, 21 Feb 2013 09:19:55 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U8SJl-0008DG-M5 for xen-users@lists.xen.org; Thu, 21 Feb 2013 09:19:54 +0000 Received: from [85.158.137.99:26601] by server-13.bemta-3.messagelabs.com id 6B/9B-20653-8B6E5215; Thu, 21 Feb 2013 09:19:52 +0000 X-Env-Sender: mailinglists.tech@gmail.com X-Msg-Ref: server-10.tower-217.messagelabs.com!1361438326!17189983!1 X-Originating-IP: [209.85.128.54] 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.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 20981 invoked from network); 21 Feb 2013 09:18:48 -0000 Received: from mail-qe0-f54.google.com (HELO mail-qe0-f54.google.com) (209.85.128.54) by server-10.tower-217.messagelabs.com with RC4-SHA encrypted SMTP; 21 Feb 2013 09:18:48 -0000 Received: by mail-qe0-f54.google.com with SMTP id f6so75467qej.41 for ; Thu, 21 Feb 2013 01:18:46 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:date:message-id:subject:from:to :content-type; bh=GBsUTo9GPH+BVOrsteW9kCEIMnVjW3N8EdZorGvzL+0=; b=k+afF7tl6oyn5aOVYmcFe0yrvF3M/959yyllgnzOvK2v6cAJIQsVWKVihywclf9F2l ZZEmlcdN8a162RnvG2AmhtOS3rS0I16FHAGvZp9OkOBgefRVYMtwAc858qnLlWhipDpJ HlCwjuuvJyXP4fZISWFTHp6QuX+mhAlHsVbR9oVQL2GGoq5SN3AGRVt/kzDq0COoCvCu 8zIbf2U2ZiZwzkjg1n70FL7LqwREDC0iaIQKMyXQCMMoqU0dYCF1q8xqyfm9+6+QxBO5 1IPJUbz2JeWJR+GYNSXrhheHm3Yj8QFAck6ylPifqmxgyIci16SPXKLEhVXg2wSQfwfM FIWw== MIME-Version: 1.0 X-Received: by 10.224.108.74 with SMTP id e10mr4170427qap.83.1361438326544; Thu, 21 Feb 2013 01:18:46 -0800 (PST) Received: by 10.49.110.70 with HTTP; Thu, 21 Feb 2013 01:18:46 -0800 (PST) Date: Thu, 21 Feb 2013 10:18:46 +0100 Message-ID: From: tech mailinglists To: xen-users , freebsd-xen@lists.freebsd.org Subject: [Xen-users] Trouble booting FreeBSD i386 PV 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="===============6916070302324878623==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============6916070302324878623== Content-Type: multipart/alternative; boundary=20cf3074b36ad67c9904d6388f5b --20cf3074b36ad67c9904d6388f5b Content-Type: text/plain; charset=ISO-8859-1 Hello all, I have created a FreeBSD PV DomU image formatted with ZFS. I compiled FreeBSD with KERNCONF=XEN for the kernel and the normal world and distribution target. Then I transfered it to a Debian Dom0 with Xen 4.2.1. I tried to boot the image befor I migrate it to LVM and I now get teh following output: Parsing config from freebsd-test.cfg libxl: error: libxl_dm.c:1212:device_model_spawn_outcome: domain 12 device model: spawn failed (rc=-3) libxl: error: libxl_qmp.c:641:libxl__qmp_initialize: Connection error: No such file or directory Daemon running with PID 3451 WARNING: loader(8) metadata is missing! GDB: no debug ports present KDB: debugger backends: ddb KDB: current backend: ddb APIC: Using the MPTable enumerator. SMP: Added CPU 0 (BSP) Copyright (c) 1992-2012 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD is a registered trademark of The FreeBSD Foundation. FreeBSD 9.1-RELEASE #0: Wed Feb 20 14:16:03 CET 2013 root@build:/usr/obj/usr/src/sys/XEN i386 WARNING: WITNESS option enabled, expect reduced performance. Xen reported: 3341.754 MHz processor. Timecounter "ixen" frequency 1953125 Hz quality 0 CPU: Intel(R) Core(TM) i7 CPU 975 @ 3.33GHz (3341.75-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x106a5 Family = 6 Model = 1a Stepping = 5 Features=0xbfe3fbff Features2=0x98e3bd AMD Features=0x28100000 AMD Features2=0x1 Data TLB: 4 KB pages, 4-way set associative, 64 entries 1st-level data cache: 32 KB, 8-way set associative, 64 byte line size L2 cache: 256 kbytes, 8-way associative, 64 bytes/line real memory = 2147483648 (2048 MB) Physical memory chunk(s): 0x0000000000a58000 - 0x000000007d995fff, 2096357376 bytes (511806 pages) avail memory = 2092105728 (1995 MB) INTR: Adding local APIC 0 as a target ULE: setup cpu 0 [XEN] IPI cpu=0 irq=128 vector=RESCHEDULE_VECTOR (0) [XEN] IPI cpu=0 irq=129 vector=CALL_FUNCTION_VECTOR (1) Event-channel device installed. io: random: mem: Pentium Pro MTRR support enabled null: nfslock: pseudo-device [XEN] xen_rtc_probe: probing Hypervisor RTC clock rtc0: on motherboard [XEN] xen_rtc_attach: attaching Hypervisor RTC clock rtc0: registered as a time-of-day clock (resolution 1000000us, adjustment 0.500000000s) xenstore0: on motherboard Grant table initialized xc0: on motherboard Device configuration finished. procfs registered Event timer "ixen" quality 600 Timecounters tick every 10.000 msec lo0: bpf attached xenbusb_front0: on xenstore0 xenbusb_add_device: Device device/suspend/event-channel ignored. State 6 xenbusb_back0: on xenstore0 xctrl0: on xenstore0 [XEN] hypervisor wallclock nudged; nudging TOD. run_interrupt_driven_hooks: still waiting after 60 seconds for xenbus_free_evtchn run_interrupt_driven_hooks: still waiting after 120 seconds for xenbus_free_evtchn run_interrupt_driven_hooks: still waiting after 180 seconds for xenbus_free_evtchn run_interrupt_driven_hooks: still waiting after 240 seconds for xenbus_free_evtchn run_interrupt_driven_hooks: still waiting after 300 seconds for xenbus_free_evtchn panic: run_interrupt_driven_config_hooks: waited too long cpuid = 0 KDB: enter: panic [ thread pid 0 tid 100000 ] Stopped at kdb_enter+0x3a: movl $0,kdb_why db> My configuration looks like this: kernel = '/home/test/kernel/kernel' extra = 'boot_verbose=1,kern.hz=100' vcpus = '1' memory = '512' disk = [ 'file:/home/test/disk.img,hda1,w', ] name = 'freebsd' #vif = [ 'mac=00:50:56:00:2A:9F,bridge=xenbr0' ] on_poweroff = 'destroy' on_reboot = 'restart' on_crash = 'restart' Can someone tell me what's going wrong and how I could solve this? I also saw other boot parameters aspecially the vfs.root.mountfrom but I don't know what is needed to define here wehn I have ZFS. I also have just a zpool and not a partition in the classic way on the image. So much questions. Would be great when someone coudl help me out. Best Regards --20cf3074b36ad67c9904d6388f5b Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Hello all,

I have created a FreeBSD = PV DomU image=20 formatted with ZFS. I compiled FreeBSD with KERNCONF=3DXEN for the kernel= =20 and the normal world and distribution target. Then I transfered it to a=20 Debian Dom0 with Xen 4.2.1.

I tried to boot the image befor I = migrate it to LVM and I now get teh following output:

Parsing config= from freebsd-test.cfg
libxl: error: libxl_dm.c:1212:device_model_spawn_= outcome: domain 12 device model: spawn failed (rc=3D-3)
libxl: error: libxl_qmp.c:641:libxl__qmp_initialize: Connection error: No s= uch file or directory
Daemon running with PID 3451
WARNING: loader(8)= metadata is missing!
GDB: no debug ports present
KDB: debugger backe= nds: ddb
KDB: current backend: ddb
APIC: Using the MPTable enumerator.
SMP: Ad= ded CPU 0 (BSP)
Copyright (c) 1992-2012 The FreeBSD Project.
Copyrigh= t (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
=A0=A0= =A0=A0=A0=A0=A0 The Regents of the University of California. All rights res= erved.
FreeBSD is a registered trademark of The FreeBSD Foundation.
FreeBSD 9.1= -RELEASE #0: Wed Feb 20 14:16:03 CET 2013
=A0=A0=A0 root@build:/usr/obj/= usr/src/sys/XEN i386
WARNING: WITNESS option enabled, expect reduced per= formance.
Xen reported: 3341.754 MHz processor.
Timecounter "ixen" frequ= ency 1953125 Hz quality 0
CPU: Intel(R) Core(TM) i7 CPU=A0=A0=A0=A0=A0= =A0=A0=A0 975=A0 @ 3.33GHz (3341.75-MHz 686-class CPU)
=A0 Origin =3D &q= uot;GenuineIntel"=A0 Id =3D 0x106a5=A0 Family =3D 6=A0 Model =3D 1a=A0= Stepping =3D 5
=A0 =20 Features=3D0xbfe3fbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,P= GE,MCA,CMOV,PAT,PSE36,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE>
=A0 F= eatures2=3D0x98e3bd<SSE3,DTES64,MON,DS_CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,P= DCM,SSE4.1,SSE4.2,POPCNT>
=A0 AMD Features=3D0x28100000<NX,RDTSCP,LM>
=A0 AMD Features2=3D0x= 1<LAHF>

Data TLB: 4 KB pages, 4-way set associative, 64 entrie= s
1st-level data cache: 32 KB, 8-way set associative, 64 byte line size<= br>L2 cache: 256 kbytes, 8-way associative, 64 bytes/line
real memory=A0 =3D 2147483648 (2048 MB)
Physical memory chunk(s):
0x0= 000000000a58000 - 0x000000007d995fff, 2096357376 bytes (511806 pages)
av= ail memory =3D 2092105728 (1995 MB)
INTR: Adding local APIC 0 as a targe= t
ULE: setup cpu 0
[XEN] IPI cpu=3D0 irq=3D128 vector=3DRESCHEDULE_VECTOR = (0)
[XEN] IPI cpu=3D0 irq=3D129 vector=3DCALL_FUNCTION_VECTOR (1)
Eve= nt-channel device installed.
io: <I/O>
random: <entropy sour= ce, Software, Yarrow>
mem: <memory>
Pentium Pro MTRR support enabled
null: <null d= evice, zero device>
nfslock: pseudo-device
[XEN] xen_rtc_probe: pr= obing Hypervisor RTC clock
rtc0: <Xen Hypervisor Clock> on motherb= oard
[XEN] xen_rtc_attach: attaching Hypervisor RTC clock
rtc0: registered as= a time-of-day clock (resolution 1000000us, adjustment 0.500000000s)
xen= store0: <XenStore> on motherboard
Grant table initialized
xc0: = <Xen Console> on motherboard
Device configuration finished.
procfs registered
Event timer "ix= en" quality 600
Timecounters tick every 10.000 msec
lo0: bpf att= ached
xenbusb_front0: <Xen Frontend Devices> on xenstore0
xenbu= sb_add_device: Device device/suspend/event-channel ignored. State 6
xenbusb_back0: <Xen Backend Devices> on xenstore0
xctrl0: <Xen = Control Device> on xenstore0
[XEN] hypervisor wallclock nudged; nudgi= ng TOD.
run_interrupt_driven_hooks: still waiting after 60 seconds for x= enbus_free_evtchn
run_interrupt_driven_hooks: still waiting after 120 seconds for xenbus_free= _evtchn
run_interrupt_driven_hooks: still waiting after 180 seconds for = xenbus_free_evtchn
run_interrupt_driven_hooks: still waiting after 240 s= econds for xenbus_free_evtchn
run_interrupt_driven_hooks: still waiting after 300 seconds for xenbus_free= _evtchn
panic: run_interrupt_driven_config_hooks: waited too long
cpu= id =3D 0
KDB: enter: panic
[ thread pid 0 tid 100000 ]
Stopped at= =A0=A0=A0=A0=A0 kdb_enter+0x3a: movl=A0=A0=A0 $0,kdb_why
db>

My configuration looks like this:

kernel =3D = 9;/home/test/kernel/kernel'
extra =3D 'boot_verbose=3D1,kern.hz= =3D100'
vcpus =3D '1'
memory =3D '512'
disk = =3D [
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 'file:/hom= e/test/disk.img,hda1,w',
=A0=A0=A0=A0=A0=A0 ]
name =3D 'freebsd'
#vif =3D [ 'mac= =3D00:50:56:00:2A:9F,bridge=3Dxenbr0' ]
on_poweroff =3D 'destroy= '
on_reboot =3D 'restart'
on_crash =3D 'restart'<= br>
Can someone tell me what's going wrong and how I could sol= ve this? I also saw other boot parameters aspecially the 
vfs.root.mountfrom=
 but I don't know what is needed to define here wehn I have ZFS. I also=
 have just a zpool and not a partition in the classic way on the image.


So much questions. W=
ould be great when someone coudl help me out.

Best Regards
--20cf3074b36ad67c9904d6388f5b-- --===============6916070302324878623== 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 --===============6916070302324878623==-- From xen-users-bounces@lists.xen.org Thu Feb 21 09:21:01 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 21 Feb 2013 09:21: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 1U8SJn-0008DL-HV; Thu, 21 Feb 2013 09:19:55 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U8SJl-0008DG-M5 for xen-users@lists.xen.org; Thu, 21 Feb 2013 09:19:54 +0000 Received: from [85.158.137.99:26601] by server-13.bemta-3.messagelabs.com id 6B/9B-20653-8B6E5215; Thu, 21 Feb 2013 09:19:52 +0000 X-Env-Sender: mailinglists.tech@gmail.com X-Msg-Ref: server-10.tower-217.messagelabs.com!1361438326!17189983!1 X-Originating-IP: [209.85.128.54] 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.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 20981 invoked from network); 21 Feb 2013 09:18:48 -0000 Received: from mail-qe0-f54.google.com (HELO mail-qe0-f54.google.com) (209.85.128.54) by server-10.tower-217.messagelabs.com with RC4-SHA encrypted SMTP; 21 Feb 2013 09:18:48 -0000 Received: by mail-qe0-f54.google.com with SMTP id f6so75467qej.41 for ; Thu, 21 Feb 2013 01:18:46 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:date:message-id:subject:from:to :content-type; bh=GBsUTo9GPH+BVOrsteW9kCEIMnVjW3N8EdZorGvzL+0=; b=k+afF7tl6oyn5aOVYmcFe0yrvF3M/959yyllgnzOvK2v6cAJIQsVWKVihywclf9F2l ZZEmlcdN8a162RnvG2AmhtOS3rS0I16FHAGvZp9OkOBgefRVYMtwAc858qnLlWhipDpJ HlCwjuuvJyXP4fZISWFTHp6QuX+mhAlHsVbR9oVQL2GGoq5SN3AGRVt/kzDq0COoCvCu 8zIbf2U2ZiZwzkjg1n70FL7LqwREDC0iaIQKMyXQCMMoqU0dYCF1q8xqyfm9+6+QxBO5 1IPJUbz2JeWJR+GYNSXrhheHm3Yj8QFAck6ylPifqmxgyIci16SPXKLEhVXg2wSQfwfM FIWw== MIME-Version: 1.0 X-Received: by 10.224.108.74 with SMTP id e10mr4170427qap.83.1361438326544; Thu, 21 Feb 2013 01:18:46 -0800 (PST) Received: by 10.49.110.70 with HTTP; Thu, 21 Feb 2013 01:18:46 -0800 (PST) Date: Thu, 21 Feb 2013 10:18:46 +0100 Message-ID: From: tech mailinglists To: xen-users , freebsd-xen@lists.freebsd.org Subject: [Xen-users] Trouble booting FreeBSD i386 PV 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="===============6916070302324878623==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============6916070302324878623== Content-Type: multipart/alternative; boundary=20cf3074b36ad67c9904d6388f5b --20cf3074b36ad67c9904d6388f5b Content-Type: text/plain; charset=ISO-8859-1 Hello all, I have created a FreeBSD PV DomU image formatted with ZFS. I compiled FreeBSD with KERNCONF=XEN for the kernel and the normal world and distribution target. Then I transfered it to a Debian Dom0 with Xen 4.2.1. I tried to boot the image befor I migrate it to LVM and I now get teh following output: Parsing config from freebsd-test.cfg libxl: error: libxl_dm.c:1212:device_model_spawn_outcome: domain 12 device model: spawn failed (rc=-3) libxl: error: libxl_qmp.c:641:libxl__qmp_initialize: Connection error: No such file or directory Daemon running with PID 3451 WARNING: loader(8) metadata is missing! GDB: no debug ports present KDB: debugger backends: ddb KDB: current backend: ddb APIC: Using the MPTable enumerator. SMP: Added CPU 0 (BSP) Copyright (c) 1992-2012 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD is a registered trademark of The FreeBSD Foundation. FreeBSD 9.1-RELEASE #0: Wed Feb 20 14:16:03 CET 2013 root@build:/usr/obj/usr/src/sys/XEN i386 WARNING: WITNESS option enabled, expect reduced performance. Xen reported: 3341.754 MHz processor. Timecounter "ixen" frequency 1953125 Hz quality 0 CPU: Intel(R) Core(TM) i7 CPU 975 @ 3.33GHz (3341.75-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x106a5 Family = 6 Model = 1a Stepping = 5 Features=0xbfe3fbff Features2=0x98e3bd AMD Features=0x28100000 AMD Features2=0x1 Data TLB: 4 KB pages, 4-way set associative, 64 entries 1st-level data cache: 32 KB, 8-way set associative, 64 byte line size L2 cache: 256 kbytes, 8-way associative, 64 bytes/line real memory = 2147483648 (2048 MB) Physical memory chunk(s): 0x0000000000a58000 - 0x000000007d995fff, 2096357376 bytes (511806 pages) avail memory = 2092105728 (1995 MB) INTR: Adding local APIC 0 as a target ULE: setup cpu 0 [XEN] IPI cpu=0 irq=128 vector=RESCHEDULE_VECTOR (0) [XEN] IPI cpu=0 irq=129 vector=CALL_FUNCTION_VECTOR (1) Event-channel device installed. io: random: mem: Pentium Pro MTRR support enabled null: nfslock: pseudo-device [XEN] xen_rtc_probe: probing Hypervisor RTC clock rtc0: on motherboard [XEN] xen_rtc_attach: attaching Hypervisor RTC clock rtc0: registered as a time-of-day clock (resolution 1000000us, adjustment 0.500000000s) xenstore0: on motherboard Grant table initialized xc0: on motherboard Device configuration finished. procfs registered Event timer "ixen" quality 600 Timecounters tick every 10.000 msec lo0: bpf attached xenbusb_front0: on xenstore0 xenbusb_add_device: Device device/suspend/event-channel ignored. State 6 xenbusb_back0: on xenstore0 xctrl0: on xenstore0 [XEN] hypervisor wallclock nudged; nudging TOD. run_interrupt_driven_hooks: still waiting after 60 seconds for xenbus_free_evtchn run_interrupt_driven_hooks: still waiting after 120 seconds for xenbus_free_evtchn run_interrupt_driven_hooks: still waiting after 180 seconds for xenbus_free_evtchn run_interrupt_driven_hooks: still waiting after 240 seconds for xenbus_free_evtchn run_interrupt_driven_hooks: still waiting after 300 seconds for xenbus_free_evtchn panic: run_interrupt_driven_config_hooks: waited too long cpuid = 0 KDB: enter: panic [ thread pid 0 tid 100000 ] Stopped at kdb_enter+0x3a: movl $0,kdb_why db> My configuration looks like this: kernel = '/home/test/kernel/kernel' extra = 'boot_verbose=1,kern.hz=100' vcpus = '1' memory = '512' disk = [ 'file:/home/test/disk.img,hda1,w', ] name = 'freebsd' #vif = [ 'mac=00:50:56:00:2A:9F,bridge=xenbr0' ] on_poweroff = 'destroy' on_reboot = 'restart' on_crash = 'restart' Can someone tell me what's going wrong and how I could solve this? I also saw other boot parameters aspecially the vfs.root.mountfrom but I don't know what is needed to define here wehn I have ZFS. I also have just a zpool and not a partition in the classic way on the image. So much questions. Would be great when someone coudl help me out. Best Regards --20cf3074b36ad67c9904d6388f5b Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Hello all,

I have created a FreeBSD = PV DomU image=20 formatted with ZFS. I compiled FreeBSD with KERNCONF=3DXEN for the kernel= =20 and the normal world and distribution target. Then I transfered it to a=20 Debian Dom0 with Xen 4.2.1.

I tried to boot the image befor I = migrate it to LVM and I now get teh following output:

Parsing config= from freebsd-test.cfg
libxl: error: libxl_dm.c:1212:device_model_spawn_= outcome: domain 12 device model: spawn failed (rc=3D-3)
libxl: error: libxl_qmp.c:641:libxl__qmp_initialize: Connection error: No s= uch file or directory
Daemon running with PID 3451
WARNING: loader(8)= metadata is missing!
GDB: no debug ports present
KDB: debugger backe= nds: ddb
KDB: current backend: ddb
APIC: Using the MPTable enumerator.
SMP: Ad= ded CPU 0 (BSP)
Copyright (c) 1992-2012 The FreeBSD Project.
Copyrigh= t (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
=A0=A0= =A0=A0=A0=A0=A0 The Regents of the University of California. All rights res= erved.
FreeBSD is a registered trademark of The FreeBSD Foundation.
FreeBSD 9.1= -RELEASE #0: Wed Feb 20 14:16:03 CET 2013
=A0=A0=A0 root@build:/usr/obj/= usr/src/sys/XEN i386
WARNING: WITNESS option enabled, expect reduced per= formance.
Xen reported: 3341.754 MHz processor.
Timecounter "ixen" frequ= ency 1953125 Hz quality 0
CPU: Intel(R) Core(TM) i7 CPU=A0=A0=A0=A0=A0= =A0=A0=A0 975=A0 @ 3.33GHz (3341.75-MHz 686-class CPU)
=A0 Origin =3D &q= uot;GenuineIntel"=A0 Id =3D 0x106a5=A0 Family =3D 6=A0 Model =3D 1a=A0= Stepping =3D 5
=A0 =20 Features=3D0xbfe3fbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,P= GE,MCA,CMOV,PAT,PSE36,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE>
=A0 F= eatures2=3D0x98e3bd<SSE3,DTES64,MON,DS_CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,P= DCM,SSE4.1,SSE4.2,POPCNT>
=A0 AMD Features=3D0x28100000<NX,RDTSCP,LM>
=A0 AMD Features2=3D0x= 1<LAHF>

Data TLB: 4 KB pages, 4-way set associative, 64 entrie= s
1st-level data cache: 32 KB, 8-way set associative, 64 byte line size<= br>L2 cache: 256 kbytes, 8-way associative, 64 bytes/line
real memory=A0 =3D 2147483648 (2048 MB)
Physical memory chunk(s):
0x0= 000000000a58000 - 0x000000007d995fff, 2096357376 bytes (511806 pages)
av= ail memory =3D 2092105728 (1995 MB)
INTR: Adding local APIC 0 as a targe= t
ULE: setup cpu 0
[XEN] IPI cpu=3D0 irq=3D128 vector=3DRESCHEDULE_VECTOR = (0)
[XEN] IPI cpu=3D0 irq=3D129 vector=3DCALL_FUNCTION_VECTOR (1)
Eve= nt-channel device installed.
io: <I/O>
random: <entropy sour= ce, Software, Yarrow>
mem: <memory>
Pentium Pro MTRR support enabled
null: <null d= evice, zero device>
nfslock: pseudo-device
[XEN] xen_rtc_probe: pr= obing Hypervisor RTC clock
rtc0: <Xen Hypervisor Clock> on motherb= oard
[XEN] xen_rtc_attach: attaching Hypervisor RTC clock
rtc0: registered as= a time-of-day clock (resolution 1000000us, adjustment 0.500000000s)
xen= store0: <XenStore> on motherboard
Grant table initialized
xc0: = <Xen Console> on motherboard
Device configuration finished.
procfs registered
Event timer "ix= en" quality 600
Timecounters tick every 10.000 msec
lo0: bpf att= ached
xenbusb_front0: <Xen Frontend Devices> on xenstore0
xenbu= sb_add_device: Device device/suspend/event-channel ignored. State 6
xenbusb_back0: <Xen Backend Devices> on xenstore0
xctrl0: <Xen = Control Device> on xenstore0
[XEN] hypervisor wallclock nudged; nudgi= ng TOD.
run_interrupt_driven_hooks: still waiting after 60 seconds for x= enbus_free_evtchn
run_interrupt_driven_hooks: still waiting after 120 seconds for xenbus_free= _evtchn
run_interrupt_driven_hooks: still waiting after 180 seconds for = xenbus_free_evtchn
run_interrupt_driven_hooks: still waiting after 240 s= econds for xenbus_free_evtchn
run_interrupt_driven_hooks: still waiting after 300 seconds for xenbus_free= _evtchn
panic: run_interrupt_driven_config_hooks: waited too long
cpu= id =3D 0
KDB: enter: panic
[ thread pid 0 tid 100000 ]
Stopped at= =A0=A0=A0=A0=A0 kdb_enter+0x3a: movl=A0=A0=A0 $0,kdb_why
db>

My configuration looks like this:

kernel =3D = 9;/home/test/kernel/kernel'
extra =3D 'boot_verbose=3D1,kern.hz= =3D100'
vcpus =3D '1'
memory =3D '512'
disk = =3D [
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 'file:/hom= e/test/disk.img,hda1,w',
=A0=A0=A0=A0=A0=A0 ]
name =3D 'freebsd'
#vif =3D [ 'mac= =3D00:50:56:00:2A:9F,bridge=3Dxenbr0' ]
on_poweroff =3D 'destroy= '
on_reboot =3D 'restart'
on_crash =3D 'restart'<= br>
Can someone tell me what's going wrong and how I could sol= ve this? I also saw other boot parameters aspecially the 
vfs.root.mountfrom=
 but I don't know what is needed to define here wehn I have ZFS. I also=
 have just a zpool and not a partition in the classic way on the image.


So much questions. W=
ould be great when someone coudl help me out.

Best Regards
--20cf3074b36ad67c9904d6388f5b-- --===============6916070302324878623== 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 --===============6916070302324878623==-- From xen-users-bounces@lists.xen.org Thu Feb 21 12:49:17 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 21 Feb 2013 12:49: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 1U8VZJ-0006nY-C3; Thu, 21 Feb 2013 12:48:09 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U8Q6p-0005QE-Pk for xen-users@lists.xen.org; Thu, 21 Feb 2013 06:58:23 +0000 Received: from [85.158.139.211:63083] by server-2.bemta-5.messagelabs.com id B6/70-16911-F85C5215; Thu, 21 Feb 2013 06:58:23 +0000 X-Env-Sender: krishansethi@curaj.ac.in X-Msg-Ref: server-4.tower-206.messagelabs.com!1361429902!18541271!1 X-Originating-IP: [209.85.217.181] X-SpamReason: No, hits=0.4 required=7.0 tests=HTML_50_60,HTML_MESSAGE, RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 12678 invoked from network); 21 Feb 2013 06:58:22 -0000 Received: from mail-lb0-f181.google.com (HELO mail-lb0-f181.google.com) (209.85.217.181) by server-4.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 21 Feb 2013 06:58:22 -0000 Received: by mail-lb0-f181.google.com with SMTP id gm6so6629791lbb.12 for ; Wed, 20 Feb 2013 22:58:21 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-received:date:message-id:subject:from:to :content-type:x-gm-message-state; bh=qo8YNIOWqDVRhBejEDctjiFVvtj8uK/k4HUZqsOQG/o=; b=Z9kCxwfxY7KfATLGshOYtrL8rzI3sggk4LFCUiUhwY/Znp832E++gniK/fa/1kL515 AmzBE0ZHMS8isR8FlI3SMSguaxjXYC4G/RfYNPb5w+U+rJgJ28lMDIyroEqSnQuSNB3Q CdBMoAK55U1J4w8/+02kQBzvlvfcjdcD+GEMznizkMx/qwuodGASw2Wjb5HshIvq2LF+ BmPEtfp3rGn6JLT765LJou2NL5fMW9ahyOHiJaR4gGRftSaOB7F4lYVHIrnUD7DNT7vA swat1Btw7ETPCIHog0vvYMpQX6seqG0b2DSS2w6+XCZv+UcQOD49sUfh7dk4QjcN5GaD bbRQ== MIME-Version: 1.0 X-Received: by 10.112.28.101 with SMTP id a5mr9878218lbh.0.1361429901598; Wed, 20 Feb 2013 22:58:21 -0800 (PST) Received: by 10.112.100.69 with HTTP; Wed, 20 Feb 2013 22:58:21 -0800 (PST) Date: Thu, 21 Feb 2013 12:28:21 +0530 Message-ID: From: Krishan Sethi To: xen-users@lists.xen.org X-Gm-Message-State: ALoCoQmsSg8wcX3FTRc6KDzEuMadFG0SKyup4EUd56Ai2lb4OrbNZH+QY1FdZv6SHXftJx0vkU/P X-Mailman-Approved-At: Thu, 21 Feb 2013 12:48:07 +0000 Subject: [Xen-users] Regarding Xen installation X-BeenThere: xen-users@lists.xen.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="===============4802570640270155604==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============4802570640270155604== Content-Type: multipart/alternative; boundary=bcaec5555450abdfbe04d63699ea --bcaec5555450abdfbe04d63699ea Content-Type: text/plain; charset=ISO-8859-1 hi i am krishan sethi, a research scholar. I am doing my research in VM migration and trying for install the xen form source code in UBUNTU-12.04. I installed and build the xen and running in dom0. Now i want to load the DomU by xen-tools. but it's not happening. Can anybody tell me the actual and detailed procedure to load domU by xen-tools. Thanks and Regards -- Krishan Sethi Mtech, Computer Science & Engineering Central University of Rajasthan, kishangarh, Ajmer +91-9785673863 --bcaec5555450abdfbe04d63699ea Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable --bcaec5555450abdfbe04d63699ea-- --===============4802570640270155604== 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 --===============4802570640270155604==-- From xen-users-bounces@lists.xen.org Thu Feb 21 12:49:17 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 21 Feb 2013 12:49: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 1U8VZJ-0006nY-C3; Thu, 21 Feb 2013 12:48:09 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U8Q6p-0005QE-Pk for xen-users@lists.xen.org; Thu, 21 Feb 2013 06:58:23 +0000 Received: from [85.158.139.211:63083] by server-2.bemta-5.messagelabs.com id B6/70-16911-F85C5215; Thu, 21 Feb 2013 06:58:23 +0000 X-Env-Sender: krishansethi@curaj.ac.in X-Msg-Ref: server-4.tower-206.messagelabs.com!1361429902!18541271!1 X-Originating-IP: [209.85.217.181] X-SpamReason: No, hits=0.4 required=7.0 tests=HTML_50_60,HTML_MESSAGE, RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 12678 invoked from network); 21 Feb 2013 06:58:22 -0000 Received: from mail-lb0-f181.google.com (HELO mail-lb0-f181.google.com) (209.85.217.181) by server-4.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 21 Feb 2013 06:58:22 -0000 Received: by mail-lb0-f181.google.com with SMTP id gm6so6629791lbb.12 for ; Wed, 20 Feb 2013 22:58:21 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-received:date:message-id:subject:from:to :content-type:x-gm-message-state; bh=qo8YNIOWqDVRhBejEDctjiFVvtj8uK/k4HUZqsOQG/o=; b=Z9kCxwfxY7KfATLGshOYtrL8rzI3sggk4LFCUiUhwY/Znp832E++gniK/fa/1kL515 AmzBE0ZHMS8isR8FlI3SMSguaxjXYC4G/RfYNPb5w+U+rJgJ28lMDIyroEqSnQuSNB3Q CdBMoAK55U1J4w8/+02kQBzvlvfcjdcD+GEMznizkMx/qwuodGASw2Wjb5HshIvq2LF+ BmPEtfp3rGn6JLT765LJou2NL5fMW9ahyOHiJaR4gGRftSaOB7F4lYVHIrnUD7DNT7vA swat1Btw7ETPCIHog0vvYMpQX6seqG0b2DSS2w6+XCZv+UcQOD49sUfh7dk4QjcN5GaD bbRQ== MIME-Version: 1.0 X-Received: by 10.112.28.101 with SMTP id a5mr9878218lbh.0.1361429901598; Wed, 20 Feb 2013 22:58:21 -0800 (PST) Received: by 10.112.100.69 with HTTP; Wed, 20 Feb 2013 22:58:21 -0800 (PST) Date: Thu, 21 Feb 2013 12:28:21 +0530 Message-ID: From: Krishan Sethi To: xen-users@lists.xen.org X-Gm-Message-State: ALoCoQmsSg8wcX3FTRc6KDzEuMadFG0SKyup4EUd56Ai2lb4OrbNZH+QY1FdZv6SHXftJx0vkU/P X-Mailman-Approved-At: Thu, 21 Feb 2013 12:48:07 +0000 Subject: [Xen-users] Regarding Xen installation X-BeenThere: xen-users@lists.xen.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="===============4802570640270155604==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============4802570640270155604== Content-Type: multipart/alternative; boundary=bcaec5555450abdfbe04d63699ea --bcaec5555450abdfbe04d63699ea Content-Type: text/plain; charset=ISO-8859-1 hi i am krishan sethi, a research scholar. I am doing my research in VM migration and trying for install the xen form source code in UBUNTU-12.04. I installed and build the xen and running in dom0. Now i want to load the DomU by xen-tools. but it's not happening. Can anybody tell me the actual and detailed procedure to load domU by xen-tools. Thanks and Regards -- Krishan Sethi Mtech, Computer Science & Engineering Central University of Rajasthan, kishangarh, Ajmer +91-9785673863 --bcaec5555450abdfbe04d63699ea Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
hi

i am krishan sethi, a resea= rch scholar. I am doing my research in VM migration and trying for install = the xen form source code in UBUNTU-12.04. I installed and build the xen and= running in dom0.

Now i want to load the DomU by xen-tools. but it's not happen= ing.

Can anybody tell me the actual and detailed procedure to = load domU by xen-tools.


Thanks and Regards
--
Krishan = Sethi
<= span style=3D"background-color:#ffffcc">Mtech, Computer Science & Engineering=
Central Universi= ty of Rajasthan, kishangarh, Ajmer
+91-9785673863
hi

i am krishan sethi, a resea= rch scholar. I am doing my research in VM migration and trying for install = the xen form source code in UBUNTU-12.04. I installed and build the xen and= running in dom0.

Now i want to load the DomU by xen-tools. but it's not happen= ing.

Can anybody tell me the actual and detailed procedure to = load domU by xen-tools.


Thanks and Regards
--
Krishan = Sethi
<= span style=3D"background-color:#ffffcc">Mtech, Computer Science & Engineering=
Central Universi= ty of Rajasthan, kishangarh, Ajmer
+91-9785673863
--bcaec5555450abdfbe04d63699ea-- --===============4802570640270155604== 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 --===============4802570640270155604==-- From xen-users-bounces@lists.xen.org Thu Feb 21 12:49:17 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 21 Feb 2013 12:49: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 1U8VZJ-0006nh-VV; Thu, 21 Feb 2013 12:48:09 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U8Reb-0007Mm-Ov for xen-users@lists.xen.org; Thu, 21 Feb 2013 08:37:21 +0000 Received: from [85.158.139.83:42976] by server-4.bemta-5.messagelabs.com id 52/19-29496-0CCD5215; Thu, 21 Feb 2013 08:37:20 +0000 X-Env-Sender: ydev@cs.utah.edu X-Msg-Ref: server-9.tower-182.messagelabs.com!1361435839!27550605!1 X-Originating-IP: [155.98.64.241] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 18220 invoked from network); 21 Feb 2013 08:37:20 -0000 Received: from rio.cs.utah.edu (HELO mail-svr1.cs.utah.edu) (155.98.64.241) by server-9.tower-182.messagelabs.com with SMTP; 21 Feb 2013 08:37:20 -0000 Received: from localhost (localhost [127.0.0.1]) by mail-svr1.cs.utah.edu (Postfix) with ESMTP id 043D26500D0 for ; Thu, 21 Feb 2013 01:37:19 -0700 (MST) X-Virus-Scanned: amavisd-new at cs.utah.edu Received: from mail-svr1.cs.utah.edu ([127.0.0.1]) by localhost (mail-svr1.cs.utah.edu [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SvYrDFuiqlPe; Thu, 21 Feb 2013 01:37:18 -0700 (MST) Received: from [192.168.1.37] (c-76-23-15-81.hsd1.ut.comcast.net [76.23.15.81]) by smtps.cs.utah.edu (Postfix) with ESMTPSA id 69E356500C7; Thu, 21 Feb 2013 01:37:18 -0700 (MST) Message-ID: <5125DCBB.2080305@cs.utah.edu> Date: Thu, 21 Feb 2013 01:37:15 -0700 From: Yathindra User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130215 Thunderbird/17.0.3 MIME-Version: 1.0 To: "xen-users@lists.xen.org" X-Mailman-Approved-At: Thu, 21 Feb 2013 12:48:07 +0000 Cc: Yathindra Naik Subject: [Xen-users] Issuing hypercalls from Linux 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: , 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 defined a new hypercall in Xen hypervisor. It is similar to do_domctl() in that I pass a single argument and use XEN_GUEST_HANDLE() to retrieve the arguments. Its currently working fine under Xen-4.3-unstable. Now I want to invoke this hypercall via Linux-3.7.5 Guest. How do I go about doing this. Thanks, Yathi _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Thu Feb 21 12:49:17 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 21 Feb 2013 12:49: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 1U8VZJ-0006nh-VV; Thu, 21 Feb 2013 12:48:09 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U8Reb-0007Mm-Ov for xen-users@lists.xen.org; Thu, 21 Feb 2013 08:37:21 +0000 Received: from [85.158.139.83:42976] by server-4.bemta-5.messagelabs.com id 52/19-29496-0CCD5215; Thu, 21 Feb 2013 08:37:20 +0000 X-Env-Sender: ydev@cs.utah.edu X-Msg-Ref: server-9.tower-182.messagelabs.com!1361435839!27550605!1 X-Originating-IP: [155.98.64.241] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 18220 invoked from network); 21 Feb 2013 08:37:20 -0000 Received: from rio.cs.utah.edu (HELO mail-svr1.cs.utah.edu) (155.98.64.241) by server-9.tower-182.messagelabs.com with SMTP; 21 Feb 2013 08:37:20 -0000 Received: from localhost (localhost [127.0.0.1]) by mail-svr1.cs.utah.edu (Postfix) with ESMTP id 043D26500D0 for ; Thu, 21 Feb 2013 01:37:19 -0700 (MST) X-Virus-Scanned: amavisd-new at cs.utah.edu Received: from mail-svr1.cs.utah.edu ([127.0.0.1]) by localhost (mail-svr1.cs.utah.edu [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SvYrDFuiqlPe; Thu, 21 Feb 2013 01:37:18 -0700 (MST) Received: from [192.168.1.37] (c-76-23-15-81.hsd1.ut.comcast.net [76.23.15.81]) by smtps.cs.utah.edu (Postfix) with ESMTPSA id 69E356500C7; Thu, 21 Feb 2013 01:37:18 -0700 (MST) Message-ID: <5125DCBB.2080305@cs.utah.edu> Date: Thu, 21 Feb 2013 01:37:15 -0700 From: Yathindra User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130215 Thunderbird/17.0.3 MIME-Version: 1.0 To: "xen-users@lists.xen.org" X-Mailman-Approved-At: Thu, 21 Feb 2013 12:48:07 +0000 Cc: Yathindra Naik Subject: [Xen-users] Issuing hypercalls from Linux 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: , 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 defined a new hypercall in Xen hypervisor. It is similar to do_domctl() in that I pass a single argument and use XEN_GUEST_HANDLE() to retrieve the arguments. Its currently working fine under Xen-4.3-unstable. Now I want to invoke this hypercall via Linux-3.7.5 Guest. How do I go about doing this. Thanks, Yathi _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Thu Feb 21 14:24:54 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 21 Feb 2013 14:24: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 1U8X3u-000436-TM; Thu, 21 Feb 2013 14:23:50 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U8X3s-00042E-6w; Thu, 21 Feb 2013 14:23:48 +0000 Received: from [85.158.139.211:17022] by server-3.bemta-5.messagelabs.com id 9E/AD-07037-3FD26215; Thu, 21 Feb 2013 14:23:47 +0000 X-Env-Sender: iwj@xenbits.xen.org X-Msg-Ref: server-14.tower-206.messagelabs.com!1361456621!18549606!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.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 30770 invoked from network); 21 Feb 2013 14:23:42 -0000 Received: from mail.xen.org (HELO mail.xen.org) (50.57.168.107) by server-14.tower-206.messagelabs.com with AES256-SHA encrypted SMTP; 21 Feb 2013 14:23:42 -0000 Received: from xenbits.xen.org ([50.57.170.242]) by mail.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U8X3c-000207-Ah; Thu, 21 Feb 2013 14:23:32 +0000 Received: from iwj by xenbits.xen.org with local (Exim 4.72) (envelope-from ) id 1U8X3b-0007ni-Cw; Thu, 21 Feb 2013 14:23:31 +0000 Date: Thu, 21 Feb 2013 14:23:31 +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 36 (CVE-2013-0153) - interrupt remap entries shared and old ones not cleared on AMD IOMMUs X-BeenThere: xen-users@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-2013-0153 / XSA-36 version 4 interrupt remap entries shared and old ones not cleared on AMD IOMMUs UPDATES IN VERSION 4 ==================== Updated patches, to deal with a boot time crash resulting from the earlier changes on systems with firmware broken in a way not previously accounted for. ISSUE DESCRIPTION ================= To avoid an erratum in early hardware, the Xen AMD IOMMU code by default chooses to use a single interrupt remapping table for the whole system. This sharing implies that any guest with a passed through PCI device that is bus mastering capable can inject interrupts into other guests, including domain 0. Furthermore, regardless of whether a shared interrupt remapping table is in use, old entries are not always cleared, providing opportunities (which accumulate over time) for guests to inject interrupts into other guests, again including domain 0. In a typical Xen system many devices are owned by domain 0 or driver domains, leaving them vulnerable to such an attack. Such a DoS is likely to have an impact on other guests running in the system. IMPACT ====== A malicious domain which is given access to a physical PCI device can mount a denial of service attack affecting the whole system. VULNERABLE SYSTEMS ================== Xen versions 3.3 onwards are vulnerable. Earlier Xen versions do not implement interrupt remapping, and hence do not support secure AMD-Vi PCI passthrough in any case. Only systems using AMD-Vi for PCI passthrough are vulnerable. Any domain which is given access to a PCI device can take advantage of this vulnerability. MITIGATION ========== This issue can be avoided by not assigning PCI devices to untrusted guests. In Xen versions 4.1.3 and above the sharing of the interrupt remapping table (and hence the more severe part of this problem) can be avoided by passing "iommu=amd-iommu-perdev-intremap" as a command line option to the hypervisor. This option is not fully functional on earlier hypervisors. RESOLUTION ========== Applying the appropriate attached patch resolves this issue. Note that on certain systems (SP5100 chipsets with erratum 28 present, or such with broken IVRS ACPI table) these patches will result in the IOMMU not being enabled anymore. This should be dealt with by a BIOS update, if available. Alternatively the check can be overridden by specifying "iommu=no-amd-iommu-perdev-intremap" on the Xen command line ("iommu=amd-iommu-global-intremap" on 4.1.x), at the price of re-opening the security hole addressed by these patches. xsa36-unstable.patch Xen unstable xsa36-4.2.patch Xen 4.2.x xsa36-4.1.patch Xen 4.1.x $ sha256sum xsa36*.patch 4bdc0f1f94f82c6bc6c777971f22ef915215b72b98b29f9064e4df65c0efc6f4 xsa36-4.1.patch dd32ecaa84edbf6d11241045f40ba53ec4a3bc6c24f719bc21204067c4eb8964 xsa36-4.2.patch 7c0b3a1b332a24a830c7a436b065943f60c54cd5b7e746c440e2992a7b5cfe41 xsa36-unstable.patch $ Incremental patches on top of what was provided in version 3 can also be taken from the respective mercurial trees: http://xenbits.xen.org/hg/xen-unstable.hg/rev/e68f14b9e739 http://xenbits.xen.org/hg/staging/xen-4.2-testing.hg/rev/6a03b38b9cd6 http://xenbits.xen.org/hg/staging/xen-4.1-testing.hg/rev/4d522221fa77 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) iQEcBAEBAgAGBQJRJf98AAoJEIP+FMlX6CvZ5ocH/jNY92kLw7BOencxa9R3TGTn 20O0+j1id+xi2vjVVF2xm2SJ7g/6Egx5WURUfy2cu+I8GdDHKmRrp3Vkazltzcnd 6AlI5aiPC2H1rFkU0FpneRk3mrluABLZO8Q5YcSJs24hwqded0W+SivH63aInki/ PsDGoBu8HUjYMWjXyqCJVJIGToLS9ApaQ8+iTylWb1ZocRm2VcPS8yJI7z82kj3A zRNADG36oAFawSJsE9z3ykVoYv9UYckOaWkaXh7jZPHAvIjvP2wLb9gmMkMXbIOP ICpJJFf0w7oW6KTY3g9n8CxUMBMoUw/9Fv+CQBzOf0ZZY/vIE8q65A0NhCcWixo= =vmpB -----END PGP SIGNATURE----- --=separator Content-Type: application/octet-stream; name="xsa36-4.1.patch" Content-Disposition: attachment; filename="xsa36-4.1.patch" Content-Transfer-Encoding: base64 QUNQSTogYWNwaV90YWJsZV9wYXJzZSgpIHNob3VsZCByZXR1cm4gaGFuZGxl cidzIGVycm9yIGNvZGUKCkN1cnJlbnRseSwgdGhlIGVycm9yIGNvZGUgcmV0 dXJuZWQgYnkgYWNwaV90YWJsZV9wYXJzZSgpJ3MgaGFuZGxlcgppcyBpZ25v cmVkLiBUaGlzIHBhdGNoIHdpbGwgcHJvcGFnYXRlIGhhbmRsZXIncyByZXR1 cm4gdmFsdWUgdG8KYWNwaV90YWJsZV9wYXJzZSgpJ3MgY2FsbGVyLgoKQU1E LElPTU1VOiBDbGVhbiB1cCBvbGQgZW50cmllcyBpbiByZW1hcHBpbmcgdGFi bGVzIHdoZW4gY3JlYXRpbmcgbmV3CmludGVycnVwdCBtYXBwaW5nLgoKV2hl biBjaGFuZ2luZyB0aGUgYWZmaW5pdHkgb2YgYW4gSVJRIGFzc29jaWF0ZWQg d2l0aCBhIHBhc3NlZAp0aHJvdWdoIFBDSSBkZXZpY2UsIGNsZWFyIHByZXZp b3VzIG1hcHBpbmcuCgpJbiBhZGRpdGlvbiwgYmVjYXVzZSBzb21lIEJJT1Nl cyBtYXkgaW5jb3JyZWN0bHkgcHJvZ3JhbSBJVlJTCmVudHJpZXMgZm9yIElP QVBJQyB0cnkgdG8gY2hlY2sgZm9yIGVudHJ5J3MgY29uc2lzdGVuY3kuIFNw ZWNpZmljYWxseSwKaWYgY29uZmxpY3RpbmcgZW50cmllcyBhcmUgZm91bmQg ZGlzYWJsZSBJT01NVSBpZiBwZXItZGV2aWNlCnJlbWFwcGluZyB0YWJsZSBp cyB1c2VkLiBJZiBlbnRyaWVzIHJlZmVyIHRvIGJvZ3VzIElPQVBJQyBJRHMK ZGlzYWJsZSBJT01NVSB1bmNvbmRpdGlvbmFsbHkKCkFNRCxJT01NVTogRGlz YWJsZSBJT01NVSBpZiBTQVRBIENvbWJpbmVkIG1vZGUgaXMgb24KCkFNRCdz IFNQNTEwMCBjaGlwc2V0IGNhbiBiZSBwbGFjZWQgaW50byBTQVRBIENvbWJp bmVkIG1vZGUKdGhhdCBtYXkgY2F1c2UgcHJldmVudCBkb20wIGZyb20gYm9v dGluZyB3aGVuIElPTU1VIGlzCmVuYWJsZWQgYW5kIHBlci1kZXZpY2UgaW50 ZXJydXB0IHJlbWFwcGluZyB0YWJsZSBpcyB1c2VkLgpXaGlsZSBTUDUxMDAg ZXJyYXR1bSAyOCByZXF1aXJlcyBCSU9TZXMgdG8gZGlzYWJsZSB0aGlzIG1v ZGUsCnNvbWUgbWF5IHN0aWxsIHVzZSBpdC4KClRoaXMgcGF0Y2ggY2hlY2tz IHdoZXRoZXIgdGhpcyBtb2RlIGlzIG9uIGFuZCwgaWYgcGVyLWRldmljZQp0 YWJsZSBpcyBpbiB1c2UsIGRpc2FibGVzIElPTU1VLgoKQU1ELElPTU1VOiBN YWtlIHBlci1kZXZpY2UgaW50ZXJydXB0IHJlbWFwcGluZyB0YWJsZSBkZWZh dWx0CgpVc2luZyBnbG9iYWwgaW50ZXJydXB0IHJlbWFwcGluZyB0YWJsZSBt YXkgYmUgaW5zZWN1cmUsIGFzCmRlc2NyaWJlZCBieSBYU0EtMzYuIFRoaXMg cGF0Y2ggbWFrZXMgcGVyLWRldmljZSBtb2RlIGRlZmF1bHQuCgpUaGlzIGlz IFhTQS0zNiAvIENWRS0yMDEzLTAxNTMuCgpTaWduZWQtb2ZmLWJ5OiBKYW4g QmV1bGljaCA8amJldWxpY2hAc3VzZS5jb20+ClNpZ25lZC1vZmYtYnk6IEJv cmlzIE9zdHJvdnNreSA8Ym9yaXMub3N0cm92c2t5QGFtZC5jb20+CgpBTUQg SU9NTVU6IGFsc28gc3BvdCBtaXNzaW5nIElPLUFQSUMgZW50cmllcyBpbiBJ VlJTIHRhYmxlCgpBcGFydCBmcm9tIGRlYWxpbmcgZHVwbGljYXRlIGNvbmZs aWN0aW5nIGVudHJpZXMsIHdlIGFsc28gaGF2ZSB0bwpoYW5kbGUgZmlybXdh cmUgb21pdHRpbmcgSU8tQVBJQyBlbnRyaWVzIGluIElWUlMgYWx0b2dldGhl ci4gTm90IGRvaW5nCnNvIGhhcyByZXN1bHRlZCBpbiBjL3MgMjY1MTc6NjAx MTM5ZTJiMGRiIHRvIGNyYXNoIHN1Y2ggc3lzdGVtcyBkdXJpbmcKYm9vdCAo d2hlcmVhcyB3aXRoIHRoZSBjaGFuZ2UgaGVyZSB0aGUgSU9NTVUgZ2V0cyBk aXNhYmxlZCBqdXN0IGFzIGlzCmJlaW5nIGRvbmUgaW4gdGhlIG90aGVyIGNh c2VzLCBpLmUuIHVubGVzcyBnbG9iYWwgdGFibGVzIGFyZSBiZWluZwp1c2Vk KS4KCkRlYnVnZ2luZyB0aGlzIGlzc3VlIGhhcyBhbHNvIHBvaW50ZWQgb3V0 IHRoYXQgdGhlIGRlYnVnIGxvZyBvdXRwdXQgaXMKcHJldHR5IHVnbHkgdG8g bG9vayBhdCAtIGNvbnNvbGlkYXRlIHRoZSBvdXRwdXQsIGFuZCBhZGQgb25l IGV4dHJhCml0ZW0gZm9yIHRoZSBJVkhEIHNwZWNpYWwgZW50cmllcywgc28g dGhhdCBmdXR1cmUgaXNzdWVzIGFyZSBlYXNpZXIKdG8gYW5hbHl6ZS4KClNp Z25lZC1vZmYtYnk6IEphbiBCZXVsaWNoIDxqYmV1bGljaEBzdXNlLmNvbT4K VGVzdGVkLWJ5OiBTYW5kZXIgRWlrZWxlbmJvb20gPGxpbnV4QGVpa2VsZW5i b29tLml0PgoKLS0tIGEveGVuL2FyY2gveDg2L2lycS5jCisrKyBiL3hlbi9h cmNoL3g4Ni9pcnEuYwpAQCAtMTY3Nyw5ICsxNjc3LDYgQEAgaW50IG1hcF9k b21haW5fcGlycSgKICAgICAgICAgZC0+YXJjaC5waXJxX2lycVtwaXJxXSA9 IGlycTsKICAgICAgICAgZC0+YXJjaC5pcnFfcGlycVtpcnFdID0gcGlycTsK ICAgICAgICAgc3Bpbl91bmxvY2tfaXJxcmVzdG9yZSgmZGVzYy0+bG9jaywg ZmxhZ3MpOwotCi0gICAgICAgIGlmICggb3B0X2lycV92ZWN0b3JfbWFwID09 IE9QVF9JUlFfVkVDVE9SX01BUF9QRVJERVYgKQotICAgICAgICAgICAgcHJp bnRrKFhFTkxPR19JTkZPICJQZXItZGV2aWNlIHZlY3RvciBtYXBzIGZvciBH U0lzIG5vdCBpbXBsZW1lbnRlZCB5ZXQuXG4iKTsKICAgICB9CiAKIGRvbmU6 Ci0tLSBhL3hlbi9kcml2ZXJzL2FjcGkvdGFibGVzLmMKKysrIGIveGVuL2Ry aXZlcnMvYWNwaS90YWJsZXMuYwpAQCAtMjY3LDcgKzI2Nyw3IEBAIGFjcGlf dGFibGVfcGFyc2VfbWFkdChlbnVtIGFjcGlfbWFkdF90eXAKICAqIEBoYW5k bGVyOiBoYW5kbGVyIHRvIHJ1bgogICoKICAqIFNjYW4gdGhlIEFDUEkgU3lz dGVtIERlc2NyaXB0b3IgVGFibGUgKFNURCkgZm9yIGEgdGFibGUgbWF0Y2hp bmcgQGlkLAotICogcnVuIEBoYW5kbGVyIG9uIGl0LiAgUmV0dXJuIDAgaWYg dGFibGUgZm91bmQsIHJldHVybiBvbiBpZiBub3QuCisgKiBydW4gQGhhbmRs ZXIgb24gaXQuCiAgKi8KIGludCBhY3BpX3RhYmxlX3BhcnNlKGNoYXIgKmlk LCBhY3BpX3RhYmxlX2hhbmRsZXIgaGFuZGxlcikKIHsKQEAgLTI4Miw4ICsy ODIsNyBAQCBpbnQgYWNwaV90YWJsZV9wYXJzZShjaGFyICppZCwgYWNwaV90 YWJsCiAJCWFjcGlfZ2V0X3RhYmxlKGlkLCAwLCAmdGFibGUpOwogCiAJaWYg KHRhYmxlKSB7Ci0JCWhhbmRsZXIodGFibGUpOwotCQlyZXR1cm4gMDsKKwkJ cmV0dXJuIGhhbmRsZXIodGFibGUpOwogCX0gZWxzZQogCQlyZXR1cm4gMTsK IH0KLS0tIGEveGVuL2RyaXZlcnMvcGFzc3Rocm91Z2gvYW1kL2lvbW11X2Fj cGkuYworKysgYi94ZW4vZHJpdmVycy9wYXNzdGhyb3VnaC9hbWQvaW9tbXVf YWNwaS5jCkBAIC0yMSw2ICsyMSw3IEBACiAjaW5jbHVkZSA8eGVuL2NvbmZp Zy5oPgogI2luY2x1ZGUgPHhlbi9lcnJuby5oPgogI2luY2x1ZGUgPGFzbS9h cGljZGVmLmg+CisjaW5jbHVkZSA8YXNtL2lvX2FwaWMuaD4KICNpbmNsdWRl IDxhc20vYW1kLWlvbW11Lmg+CiAjaW5jbHVkZSA8YXNtL2h2bS9zdm0vYW1k LWlvbW11LXByb3RvLmg+CiAjaW5jbHVkZSA8YXNtL2h2bS9zdm0vYW1kLWlv bW11LWFjcGkuaD4KQEAgLTI5LDcgKzMwLDYgQEAgZXh0ZXJuIHVuc2lnbmVk IGxvbmcgYW1kX2lvbW11X3BhZ2VfZW50cgogZXh0ZXJuIHVuc2lnbmVkIHNo b3J0IGl2cnNfYmRmX2VudHJpZXM7CiBleHRlcm4gc3RydWN0IGl2cnNfbWFw cGluZ3MgKml2cnNfbWFwcGluZ3M7CiBleHRlcm4gdW5zaWduZWQgc2hvcnQg bGFzdF9iZGY7Ci1leHRlcm4gaW50IGlvYXBpY19iZGZbTUFYX0lPX0FQSUNT XTsKIGV4dGVybiB2b2lkICpzaGFyZWRfaW50cmVtYXBfdGFibGU7CiAKIHN0 YXRpYyB2b2lkIGFkZF9pdnJzX21hcHBpbmdfZW50cnkoCkBAIC02MzYsNiAr NjM2LDcgQEAgc3RhdGljIHUxNiBfX2luaXQgcGFyc2VfaXZoZF9kZXZpY2Vf c3BlYwogICAgIHUxNiBoZWFkZXJfbGVuZ3RoLCB1MTYgYmxvY2tfbGVuZ3Ro LCBzdHJ1Y3QgYW1kX2lvbW11ICppb21tdSkKIHsKICAgICB1MTYgZGV2X2xl bmd0aCwgYmRmOworICAgIGludCBhcGljOwogCiAgICAgZGV2X2xlbmd0aCA9 IHNpemVvZihzdHJ1Y3QgYWNwaV9pdmhkX2RldmljZV9zcGVjaWFsKTsKICAg ICBpZiAoIGhlYWRlcl9sZW5ndGggPCAoYmxvY2tfbGVuZ3RoICsgZGV2X2xl bmd0aCkgKQpAQCAtNjUyLDkgKzY1Myw1OCBAQCBzdGF0aWMgdTE2IF9faW5p dCBwYXJzZV9pdmhkX2RldmljZV9zcGVjCiAgICAgfQogCiAgICAgYWRkX2l2 cnNfbWFwcGluZ19lbnRyeShiZGYsIGJkZiwgaXZoZF9kZXZpY2UtPmhlYWRl ci5mbGFncywgaW9tbXUpOwotICAgIC8qIHNldCBkZXZpY2UgaWQgb2YgaW9h cGljICovCi0gICAgaW9hcGljX2JkZltpdmhkX2RldmljZS0+c3BlY2lhbC5o YW5kbGVdID0gYmRmOwotICAgIHJldHVybiBkZXZfbGVuZ3RoOworCisgICAg aWYgKCBpdmhkX2RldmljZS0+c3BlY2lhbC52YXJpZXR5ICE9IDEgLyogQUNQ SV9JVkhEX0lPQVBJQyAqLyApCisgICAgeworICAgICAgICBpZiAoIGl2aGRf ZGV2aWNlLT5zcGVjaWFsLnZhcmlldHkgIT0gMiAvKiBBQ1BJX0lWSERfSFBF VCAqLyApCisgICAgICAgICAgICBwcmludGsoWEVOTE9HX0VSUiAiVW5yZWNv Z25pemVkIElWSEQgc3BlY2lhbCB2YXJpZXR5ICUjeFxuIiwKKyAgICAgICAg ICAgICAgICAgICBpdmhkX2RldmljZS0+c3BlY2lhbC52YXJpZXR5KTsKKyAg ICAgICAgcmV0dXJuIGRldl9sZW5ndGg7CisgICAgfQorCisgICAgLyoKKyAg ICAgKiBTb21lIEJJT1NlcyBoYXZlIElPQVBJQyBicm9rZW4gZW50cmllcyBz byB3ZSBjaGVjayBmb3IgSVZSUworICAgICAqIGNvbnNpc3RlbmN5IGhlcmUg LS0tIHdoZXRoZXIgZW50cnkncyBJT0FQSUMgSUQgaXMgdmFsaWQgYW5kCisg ICAgICogd2hldGhlciB0aGVyZSBhcmUgY29uZmxpY3RpbmcvZHVwbGljYXRl ZCBlbnRyaWVzLgorICAgICAqLworICAgIGZvciAoIGFwaWMgPSAwOyBhcGlj IDwgbnJfaW9hcGljczsgYXBpYysrICkKKyAgICB7CisgICAgICAgIGlmICgg SU9fQVBJQ19JRChhcGljKSAhPSBpdmhkX2RldmljZS0+c3BlY2lhbC5oYW5k bGUgKQorICAgICAgICAgICAgY29udGludWU7CisKKyAgICAgICAgaWYgKCBp b2FwaWNfYmRmW2l2aGRfZGV2aWNlLT5zcGVjaWFsLmhhbmRsZV0ucGluX3Nl dHVwICkKKyAgICAgICAgeworICAgICAgICAgICAgaWYgKCBpb2FwaWNfYmRm W2l2aGRfZGV2aWNlLT5zcGVjaWFsLmhhbmRsZV0uYmRmID09IGJkZiApCisg ICAgICAgICAgICAgICAgQU1EX0lPTU1VX0RFQlVHKCJJVkhEIFdhcm5pbmc6 IER1cGxpY2F0ZSBJTy1BUElDICUjeCBlbnRyaWVzXG4iLAorICAgICAgICAg ICAgICAgICAgICAgICAgICAgICAgICBpdmhkX2RldmljZS0+c3BlY2lhbC5o YW5kbGUpOworICAgICAgICAgICAgZWxzZQorICAgICAgICAgICAgeworICAg ICAgICAgICAgICAgIHByaW50ayhYRU5MT0dfRVJSICJJVkhEIEVycm9yOiBD b25mbGljdGluZyBJTy1BUElDICUjeCBlbnRyaWVzXG4iLAorICAgICAgICAg ICAgICAgICAgICAgICBpdmhkX2RldmljZS0+c3BlY2lhbC5oYW5kbGUpOwor ICAgICAgICAgICAgICAgIGlmICggYW1kX2lvbW11X3BlcmRldl9pbnRyZW1h cCApCisgICAgICAgICAgICAgICAgICAgIHJldHVybiAwOworICAgICAgICAg ICAgfQorICAgICAgICB9CisgICAgICAgIGVsc2UKKyAgICAgICAgeworICAg ICAgICAgICAgLyogc2V0IGRldmljZSBpZCBvZiBpb2FwaWMgKi8KKyAgICAg ICAgICAgIGlvYXBpY19iZGZbaXZoZF9kZXZpY2UtPnNwZWNpYWwuaGFuZGxl XS5iZGYgPSBiZGY7CisKKyAgICAgICAgICAgIGlvYXBpY19iZGZbaXZoZF9k ZXZpY2UtPnNwZWNpYWwuaGFuZGxlXS5waW5fc2V0dXAgPSB4emFsbG9jX2Fy cmF5KAorICAgICAgICAgICAgICAgIHVuc2lnbmVkIGxvbmcsIEJJVFNfVE9f TE9OR1MobnJfaW9hcGljX3JlZ2lzdGVyc1thcGljXSkpOworICAgICAgICAg ICAgaWYgKCBucl9pb2FwaWNfcmVnaXN0ZXJzW2FwaWNdICYmCisgICAgICAg ICAgICAgICAgICFpb2FwaWNfYmRmW0lPX0FQSUNfSUQoYXBpYyldLnBpbl9z ZXR1cCApCisgICAgICAgICAgICB7CisgICAgICAgICAgICAgICAgcHJpbnRr KFhFTkxPR19FUlIgIklWSEQgRXJyb3I6IE91dCBvZiBtZW1vcnlcbiIpOwor ICAgICAgICAgICAgICAgIHJldHVybiAwOworICAgICAgICAgICAgfQorICAg ICAgICB9CisgICAgICAgIHJldHVybiBkZXZfbGVuZ3RoOworICAgIH0KKwor ICAgIHByaW50ayhYRU5MT0dfRVJSICJJVkhEIEVycm9yOiBJbnZhbGlkIElP LUFQSUMgJSN4XG4iLAorICAgICAgICAgICBpdmhkX2RldmljZS0+c3BlY2lh bC5oYW5kbGUpOworICAgIHJldHVybiAwOwogfQogCiBzdGF0aWMgaW50IF9f aW5pdCBwYXJzZV9pdmhkX2Jsb2NrKHN0cnVjdCBhY3BpX2l2aGRfYmxvY2tf aGVhZGVyICppdmhkX2Jsb2NrKQpAQCAtODE3LDYgKzg2Nyw3IEBAIHN0YXRp YyBpbnQgX19pbml0IHBhcnNlX2l2cnNfdGFibGUoc3RydWMKIHsKICAgICBz dHJ1Y3QgYWNwaV9pdnJzX2Jsb2NrX2hlYWRlciAqaXZyc19ibG9jazsKICAg ICB1bnNpZ25lZCBsb25nIGxlbmd0aDsKKyAgICB1bnNpZ25lZCBpbnQgYXBp YzsKICAgICBpbnQgZXJyb3IgPSAwOwogICAgIHN0cnVjdCBhY3BpX3RhYmxl X2hlYWRlciAqdGFibGUgPSAoc3RydWN0IGFjcGlfdGFibGVfaGVhZGVyICop X3RhYmxlOwogCkBAIC04NTEsNiArOTAyLDI5IEBAIHN0YXRpYyBpbnQgX19p bml0IHBhcnNlX2l2cnNfdGFibGUoc3RydWMKICAgICAgICAgbGVuZ3RoICs9 IGl2cnNfYmxvY2stPmxlbmd0aDsKICAgICB9CiAKKyAgICAvKiBFYWNoIElP LUFQSUMgbXVzdCBoYXZlIGJlZW4gbWVudGlvbmVkIGluIHRoZSB0YWJsZS4g Ki8KKyAgICBmb3IgKCBhcGljID0gMDsgIWVycm9yICYmIGFwaWMgPCBucl9p b2FwaWNzOyArK2FwaWMgKQorICAgIHsKKyAgICAgICAgaWYgKCAhbnJfaW9h cGljX3JlZ2lzdGVyc1thcGljXSB8fAorICAgICAgICAgICAgIGlvYXBpY19i ZGZbSU9fQVBJQ19JRChhcGljKV0ucGluX3NldHVwICkKKyAgICAgICAgICAg IGNvbnRpbnVlOworCisgICAgICAgIHByaW50ayhYRU5MT0dfRVJSICJJVkhE IEVycm9yOiBubyBpbmZvcm1hdGlvbiBmb3IgSU8tQVBJQyAlI3hcbiIsCisg ICAgICAgICAgICAgICBJT19BUElDX0lEKGFwaWMpKTsKKyAgICAgICAgaWYg KCBhbWRfaW9tbXVfcGVyZGV2X2ludHJlbWFwICkKKyAgICAgICAgICAgIGVy cm9yID0gLUVOWElPOworICAgICAgICBlbHNlCisgICAgICAgIHsKKyAgICAg ICAgICAgIGlvYXBpY19iZGZbSU9fQVBJQ19JRChhcGljKV0ucGluX3NldHVw ID0geHphbGxvY19hcnJheSgKKyAgICAgICAgICAgICAgICB1bnNpZ25lZCBs b25nLCBCSVRTX1RPX0xPTkdTKG5yX2lvYXBpY19yZWdpc3RlcnNbYXBpY10p KTsKKyAgICAgICAgICAgIGlmICggIWlvYXBpY19iZGZbSU9fQVBJQ19JRChh cGljKV0ucGluX3NldHVwICkKKyAgICAgICAgICAgIHsKKyAgICAgICAgICAg ICAgICBwcmludGsoWEVOTE9HX0VSUiAiSVZIRCBFcnJvcjogT3V0IG9mIG1l bW9yeVxuIik7CisgICAgICAgICAgICAgICAgZXJyb3IgPSAtRU5PTUVNOwor ICAgICAgICAgICAgfQorICAgICAgICB9CisgICAgfQorCiAgICAgcmV0dXJu IGVycm9yOwogfQogCi0tLSBhL3hlbi9kcml2ZXJzL3Bhc3N0aHJvdWdoL2Ft ZC9pb21tdV9pbml0LmMKKysrIGIveGVuL2RyaXZlcnMvcGFzc3Rocm91Z2gv YW1kL2lvbW11X2luaXQuYwpAQCAtODk3LDEyICs4OTcsNDUgQEAgc3RhdGlj IGludCBfX2luaXQgYW1kX2lvbW11X3NldHVwX2RldmljZQogICAgIHJldHVy biAwOwogfQogCisvKiBDaGVjayB3aGV0aGVyIFNQNTEwMCBTQVRBIENvbWJp bmVkIG1vZGUgaXMgb24gKi8KK3N0YXRpYyBib29sX3QgX19pbml0IGFtZF9z cDUxMDBfZXJyYXR1bTI4KHZvaWQpCit7CisgICAgdTMyIGJ1cywgaWQ7Cisg ICAgdTE2IHZlbmRvcl9pZCwgZGV2X2lkOworICAgIHU4IGJ5dGU7CisKKyAg ICBmb3IgKGJ1cyA9IDA7IGJ1cyA8IDI1NjsgYnVzKyspCisgICAgeworICAg ICAgICBpZCA9IHBjaV9jb25mX3JlYWQzMihidXMsIDB4MTQsIDAsIFBDSV9W RU5ET1JfSUQpOworCisgICAgICAgIHZlbmRvcl9pZCA9IGlkICYgMHhmZmZm OworICAgICAgICBkZXZfaWQgPSAoaWQgPj4gMTYpICYgMHhmZmZmOworCisg ICAgICAgIC8qIFNQNTEwMCBTTUJ1cyBtb2R1bGUgc2V0cyBDb21iaW5lZCBt b2RlIG9uICovCisgICAgICAgIGlmICh2ZW5kb3JfaWQgIT0gMHgxMDAyIHx8 IGRldl9pZCAhPSAweDQzODUpCisgICAgICAgICAgICBjb250aW51ZTsKKwor ICAgICAgICBieXRlID0gcGNpX2NvbmZfcmVhZDgoYnVzLCAweDE0LCAwLCAw eGFkKTsKKyAgICAgICAgaWYgKCAoYnl0ZSA+PiAzKSAmIDEgKQorICAgICAg ICB7CisgICAgICAgICAgICBwcmludGsoWEVOTE9HX1dBUk5JTkcgIkFNRC1W aTogU1A1MTAwIGVycmF0dW0gMjggZGV0ZWN0ZWQsIGRpc2FibGluZyBJT01N VS5cbiIKKyAgICAgICAgICAgICAgICAgICAiSWYgcG9zc2libGUsIGRpc2Fi bGUgU0FUQSBDb21iaW5lZCBtb2RlIGluIEJJT1Mgb3IgY29udGFjdCB5b3Vy IHZlbmRvciBmb3IgQklPUyB1cGRhdGUuXG4iKTsKKyAgICAgICAgICAgIHJl dHVybiAxOworICAgICAgICB9CisgICAgfQorCisgICAgcmV0dXJuIDA7Cit9 CisKIGludCBfX2luaXQgYW1kX2lvbW11X2luaXQodm9pZCkKIHsKICAgICBz dHJ1Y3QgYW1kX2lvbW11ICppb21tdTsKIAogICAgIEJVR19PTiggIWlvbW11 X2ZvdW5kKCkgKTsKIAorICAgIGlmICggYW1kX2lvbW11X3BlcmRldl9pbnRy ZW1hcCAmJiBhbWRfc3A1MTAwX2VycmF0dW0yOCgpICkKKyAgICAgICAgZ290 byBlcnJvcl9vdXQ7CisKICAgICBpcnFfdG9faW9tbXUgPSB4bWFsbG9jX2Fy cmF5KHN0cnVjdCBhbWRfaW9tbXUgKiwgbnJfaXJxcyk7CiAgICAgaWYgKCBp cnFfdG9faW9tbXUgPT0gTlVMTCApCiAgICAgICAgIGdvdG8gZXJyb3Jfb3V0 OwotLS0gYS94ZW4vZHJpdmVycy9wYXNzdGhyb3VnaC9hbWQvaW9tbXVfaW50 ci5jCisrKyBiL3hlbi9kcml2ZXJzL3Bhc3N0aHJvdWdoL2FtZC9pb21tdV9p bnRyLmMKQEAgLTI3LDcgKzI3LDcgQEAKICNkZWZpbmUgSU5UUkVNQVBfTEVO R1RIIDB4QgogI2RlZmluZSBJTlRSRU1BUF9FTlRSSUVTICgxIDw8IElOVFJF TUFQX0xFTkdUSCkKIAotaW50IGlvYXBpY19iZGZbTUFYX0lPX0FQSUNTXTsK K3N0cnVjdCBpb2FwaWNfYmRmIGlvYXBpY19iZGZbTUFYX0lPX0FQSUNTXTsK IGV4dGVybiBzdHJ1Y3QgaXZyc19tYXBwaW5ncyAqaXZyc19tYXBwaW5nczsK IGV4dGVybiB1bnNpZ25lZCBzaG9ydCBpdnJzX2JkZl9lbnRyaWVzOwogdm9p ZCAqc2hhcmVkX2ludHJlbWFwX3RhYmxlOwpAQCAtMTE3LDEyICsxMTcsMTIg QEAgdm9pZCBpbnZhbGlkYXRlX2ludGVycnVwdF90YWJsZShzdHJ1Y3QgYQog c3RhdGljIHZvaWQgdXBkYXRlX2ludHJlbWFwX2VudHJ5X2Zyb21faW9hcGlj KAogICAgIGludCBiZGYsCiAgICAgc3RydWN0IGFtZF9pb21tdSAqaW9tbXUs Ci0gICAgc3RydWN0IElPX0FQSUNfcm91dGVfZW50cnkgKmlvYXBpY19ydGUp CisgICAgY29uc3Qgc3RydWN0IElPX0FQSUNfcm91dGVfZW50cnkgKnJ0ZSwK KyAgICBjb25zdCBzdHJ1Y3QgSU9fQVBJQ19yb3V0ZV9lbnRyeSAqb2xkX3J0 ZSkKIHsKICAgICB1bnNpZ25lZCBsb25nIGZsYWdzOwogICAgIHUzMiogZW50 cnk7CiAgICAgdTggZGVsaXZlcnlfbW9kZSwgZGVzdCwgdmVjdG9yLCBkZXN0 X21vZGU7Ci0gICAgc3RydWN0IElPX0FQSUNfcm91dGVfZW50cnkgKnJ0ZSA9 IGlvYXBpY19ydGU7CiAgICAgaW50IHJlcV9pZDsKICAgICBzcGlubG9ja190 ICpsb2NrOwogICAgIGludCBvZmZzZXQ7CkBAIC0xMzgsNiArMTM4LDE0IEBA IHN0YXRpYyB2b2lkIHVwZGF0ZV9pbnRyZW1hcF9lbnRyeV9mcm9tX2kKICAg ICBzcGluX2xvY2tfaXJxc2F2ZShsb2NrLCBmbGFncyk7CiAKICAgICBvZmZz ZXQgPSBnZXRfaW50cmVtYXBfb2Zmc2V0KHZlY3RvciwgZGVsaXZlcnlfbW9k ZSk7CisgICAgaWYgKCBvbGRfcnRlICkKKyAgICB7CisgICAgICAgIGludCBv bGRfb2Zmc2V0ID0gZ2V0X2ludHJlbWFwX29mZnNldChvbGRfcnRlLT52ZWN0 b3IsCisgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg ICAgICBvbGRfcnRlLT5kZWxpdmVyeV9tb2RlKTsKKworICAgICAgICBpZiAo IG9mZnNldCAhPSBvbGRfb2Zmc2V0ICkKKyAgICAgICAgICAgIGZyZWVfaW50 cmVtYXBfZW50cnkoYmRmLCBvbGRfb2Zmc2V0KTsKKyAgICB9CiAgICAgZW50 cnkgPSAodTMyKilnZXRfaW50cmVtYXBfZW50cnkocmVxX2lkLCBvZmZzZXQp OwogICAgIHVwZGF0ZV9pbnRyZW1hcF9lbnRyeShlbnRyeSwgdmVjdG9yLCBk ZWxpdmVyeV9tb2RlLCBkZXN0X21vZGUsIGRlc3QpOwogCkBAIC0xNzYsNyAr MTg0LDcgQEAgaW50IF9faW5pdCBhbWRfaW9tbXVfc2V0dXBfaW9hcGljX3Jl bWFwcAogICAgICAgICAgICAgICAgIGNvbnRpbnVlOwogCiAgICAgICAgICAg ICAvKiBnZXQgZGV2aWNlIGlkIG9mIGlvYXBpYyBkZXZpY2VzICovCi0gICAg ICAgICAgICBiZGYgPSBpb2FwaWNfYmRmW0lPX0FQSUNfSUQoYXBpYyldOwor ICAgICAgICAgICAgYmRmID0gaW9hcGljX2JkZltJT19BUElDX0lEKGFwaWMp XS5iZGY7CiAgICAgICAgICAgICBpb21tdSA9IGZpbmRfaW9tbXVfZm9yX2Rl dmljZShiZGYpOwogICAgICAgICAgICAgaWYgKCAhaW9tbXUgKQogICAgICAg ICAgICAgewpAQCAtMjA3LDYgKzIxNSw3IEBAIGludCBfX2luaXQgYW1kX2lv bW11X3NldHVwX2lvYXBpY19yZW1hcHAKICAgICAgICAgICAgICAgICBmbHVz aF9jb21tYW5kX2J1ZmZlcihpb21tdSk7CiAgICAgICAgICAgICAgICAgc3Bp bl91bmxvY2tfaXJxcmVzdG9yZSgmaW9tbXUtPmxvY2ssIGZsYWdzKTsKICAg ICAgICAgICAgIH0KKyAgICAgICAgICAgIHNldF9iaXQocGluLCBpb2FwaWNf YmRmW0lPX0FQSUNfSUQoYXBpYyldLnBpbl9zZXR1cCk7CiAgICAgICAgIH0K ICAgICB9CiAgICAgcmV0dXJuIDA7CkBAIC0yMTgsNiArMjI3LDcgQEAgdm9p ZCBhbWRfaW9tbXVfaW9hcGljX3VwZGF0ZV9pcmUoCiAgICAgc3RydWN0IElP X0FQSUNfcm91dGVfZW50cnkgb2xkX3J0ZSA9IHsgMCB9OwogICAgIHN0cnVj dCBJT19BUElDX3JvdXRlX2VudHJ5IG5ld19ydGUgPSB7IDAgfTsKICAgICB1 bnNpZ25lZCBpbnQgcnRlX2xvID0gKHJlZyAmIDEpID8gcmVnIC0gMSA6IHJl ZzsKKyAgICB1bnNpZ25lZCBpbnQgcGluID0gKHJlZyAtIDB4MTApIC8gMjsK ICAgICBpbnQgc2F2ZWRfbWFzaywgYmRmOwogICAgIHN0cnVjdCBhbWRfaW9t bXUgKmlvbW11OwogCkBAIC0yMjgsNyArMjM4LDcgQEAgdm9pZCBhbWRfaW9t bXVfaW9hcGljX3VwZGF0ZV9pcmUoCiAgICAgfQogCiAgICAgLyogZ2V0IGRl dmljZSBpZCBvZiBpb2FwaWMgZGV2aWNlcyAqLwotICAgIGJkZiA9IGlvYXBp Y19iZGZbSU9fQVBJQ19JRChhcGljKV07CisgICAgYmRmID0gaW9hcGljX2Jk ZltJT19BUElDX0lEKGFwaWMpXS5iZGY7CiAgICAgaW9tbXUgPSBmaW5kX2lv bW11X2Zvcl9kZXZpY2UoYmRmKTsKICAgICBpZiAoICFpb21tdSApCiAgICAg ewpAQCAtMjU0LDYgKzI2NCwxNCBAQCB2b2lkIGFtZF9pb21tdV9pb2FwaWNf dXBkYXRlX2lyZSgKICAgICAgICAgKigoKHUzMiAqKSZuZXdfcnRlKSArIDEp ID0gdmFsdWU7CiAgICAgfQogCisgICAgaWYgKCBuZXdfcnRlLm1hc2sgJiYK KyAgICAgICAgICF0ZXN0X2JpdChwaW4sIGlvYXBpY19iZGZbSU9fQVBJQ19J RChhcGljKV0ucGluX3NldHVwKSApCisgICAgeworICAgICAgICBBU1NFUlQo c2F2ZWRfbWFzayk7CisgICAgICAgIF9faW9fYXBpY193cml0ZShhcGljLCBy ZWcsIHZhbHVlKTsKKyAgICAgICAgcmV0dXJuOworICAgIH0KKwogICAgIC8q IG1hc2sgdGhlIGludGVycnVwdCB3aGlsZSB3ZSBjaGFuZ2UgdGhlIGludHJl bWFwIHRhYmxlICovCiAgICAgaWYgKCAhc2F2ZWRfbWFzayApCiAgICAgewpA QCAtMjYyLDcgKzI4MCwxMSBAQCB2b2lkIGFtZF9pb21tdV9pb2FwaWNfdXBk YXRlX2lyZSgKICAgICB9CiAKICAgICAvKiBVcGRhdGUgaW50ZXJydXB0IHJl bWFwcGluZyBlbnRyeSAqLwotICAgIHVwZGF0ZV9pbnRyZW1hcF9lbnRyeV9m cm9tX2lvYXBpYyhiZGYsIGlvbW11LCAmbmV3X3J0ZSk7CisgICAgdXBkYXRl X2ludHJlbWFwX2VudHJ5X2Zyb21faW9hcGljKAorICAgICAgICBiZGYsIGlv bW11LCAmbmV3X3J0ZSwKKyAgICAgICAgdGVzdF9hbmRfc2V0X2JpdChwaW4s CisgICAgICAgICAgICAgICAgICAgICAgICAgaW9hcGljX2JkZltJT19BUElD X0lEKGFwaWMpXS5waW5fc2V0dXApID8gJm9sZF9ydGUKKyAgICAgICAgICAg ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg ICAgICAgICAgOiBOVUxMKTsKIAogICAgIC8qIEZvcndhcmQgd3JpdGUgYWNj ZXNzIHRvIElPLUFQSUMgUlRFICovCiAgICAgX19pb19hcGljX3dyaXRlKGFw aWMsIHJlZywgdmFsdWUpOwpAQCAtMzczLDYgKzM5NSwxMiBAQCB2b2lkIGFt ZF9pb21tdV9tc2lfbXNnX3VwZGF0ZV9pcmUoCiAgICAgICAgIHJldHVybjsK ICAgICB9CiAKKyAgICBpZiAoIG1zaV9kZXNjLT5yZW1hcF9pbmRleCA+PSAw ICkKKyAgICAgICAgdXBkYXRlX2ludHJlbWFwX2VudHJ5X2Zyb21fbXNpX21z Zyhpb21tdSwgcGRldiwgbXNpX2Rlc2MsIE5VTEwpOworCisgICAgaWYgKCAh bXNnICkKKyAgICAgICAgcmV0dXJuOworCiAgICAgdXBkYXRlX2ludHJlbWFw X2VudHJ5X2Zyb21fbXNpX21zZyhpb21tdSwgcGRldiwgbXNpX2Rlc2MsIG1z Zyk7CiB9CiAKLS0tIGEveGVuL2RyaXZlcnMvcGFzc3Rocm91Z2gvYW1kL3Bj aV9hbWRfaW9tbXUuYworKysgYi94ZW4vZHJpdmVycy9wYXNzdGhyb3VnaC9h bWQvcGNpX2FtZF9pb21tdS5jCkBAIC0xOTUsNiArMTk1LDggQEAgaW50IF9f aW5pdCBhbWRfaW92X2RldGVjdCh2b2lkKQogICAgIHsKICAgICAgICAgcHJp bnRrKCJBTUQtVmk6IE5vdCBvdmVycmlkaW5nIGlycV92ZWN0b3JfbWFwIHNl dHRpbmdcbiIpOwogICAgIH0KKyAgICBpZiAoICFhbWRfaW9tbXVfcGVyZGV2 X2ludHJlbWFwICkKKyAgICAgICAgcHJpbnRrKFhFTkxPR19XQVJOSU5HICJB TUQtVmk6IFVzaW5nIGdsb2JhbCBpbnRlcnJ1cHQgcmVtYXAgdGFibGUgaXMg bm90IHJlY29tbWVuZGVkIChzZWUgWFNBLTM2KSFcbiIpOwogICAgIHJldHVy biBzY2FuX3BjaV9kZXZpY2VzKCk7CiB9CiAKLS0tIGEveGVuL2RyaXZlcnMv cGFzc3Rocm91Z2gvaW9tbXUuYworKysgYi94ZW4vZHJpdmVycy9wYXNzdGhy b3VnaC9pb21tdS5jCkBAIC00OSw3ICs0OSw3IEBAIGJvb2xfdCBfX3JlYWRf bW9zdGx5IGlvbW11X3FpbnZhbCA9IDE7CiBib29sX3QgX19yZWFkX21vc3Rs eSBpb21tdV9pbnRyZW1hcCA9IDE7CiBib29sX3QgX19yZWFkX21vc3RseSBp b21tdV9oYXBfcHRfc2hhcmU7CiBib29sX3QgX19yZWFkX21vc3RseSBhbWRf aW9tbXVfZGVidWc7Ci1ib29sX3QgX19yZWFkX21vc3RseSBhbWRfaW9tbXVf cGVyZGV2X2ludHJlbWFwOworYm9vbF90IF9fcmVhZF9tb3N0bHkgYW1kX2lv bW11X3BlcmRldl9pbnRyZW1hcCA9IDE7CiAKIHN0YXRpYyB2b2lkIF9faW5p dCBwYXJzZV9pb21tdV9wYXJhbShjaGFyICpzKQogewpAQCAtNzgsNiArNzgs OCBAQCBzdGF0aWMgdm9pZCBfX2luaXQgcGFyc2VfaW9tbXVfcGFyYW0oY2hh CiAgICAgICAgICAgICBhbWRfaW9tbXVfZGVidWcgPSAxOwogICAgICAgICBl bHNlIGlmICggIXN0cmNtcChzLCAiYW1kLWlvbW11LXBlcmRldi1pbnRyZW1h cCIpICkKICAgICAgICAgICAgIGFtZF9pb21tdV9wZXJkZXZfaW50cmVtYXAg PSAxOworICAgICAgICBlbHNlIGlmICggIXN0cmNtcChzLCAiYW1kLWlvbW11 LWdsb2JhbC1pbnRyZW1hcCIpICkKKyAgICAgICAgICAgIGFtZF9pb21tdV9w ZXJkZXZfaW50cmVtYXAgPSAwOwogICAgICAgICBlbHNlIGlmICggIXN0cmNt cChzLCAiZG9tMC1wYXNzdGhyb3VnaCIpICkKICAgICAgICAgICAgIGlvbW11 X3Bhc3N0aHJvdWdoID0gMTsKICAgICAgICAgZWxzZSBpZiAoICFzdHJjbXAo cywgImRvbTAtc3RyaWN0IikgKQotLS0gYS94ZW4vaW5jbHVkZS9hc20teDg2 L2h2bS9zdm0vYW1kLWlvbW11LXByb3RvLmgKKysrIGIveGVuL2luY2x1ZGUv YXNtLXg4Ni9odm0vc3ZtL2FtZC1pb21tdS1wcm90by5oCkBAIC04OCw2ICs4 OCwxMSBAQCB2b2lkIGFtZF9pb21tdV9yZWFkX21zaV9mcm9tX2lyZSgKIHVu c2lnbmVkIGludCBhbWRfaW9tbXVfcmVhZF9pb2FwaWNfZnJvbV9pcmUoCiAg ICAgdW5zaWduZWQgaW50IGFwaWMsIHVuc2lnbmVkIGludCByZWcpOwogCitl eHRlcm4gc3RydWN0IGlvYXBpY19iZGYgeworICAgIHUxNiBiZGY7CisgICAg dW5zaWduZWQgbG9uZyAqcGluX3NldHVwOworfSBpb2FwaWNfYmRmW107CisK IC8qIHBvd2VyIG1hbmFnZW1lbnQgc3VwcG9ydCAqLwogdm9pZCBhbWRfaW9t bXVfcmVzdW1lKHZvaWQpOwogdm9pZCBhbWRfaW9tbXVfc3VzcGVuZCh2b2lk KTsK --=separator Content-Type: application/octet-stream; name="xsa36-4.2.patch" Content-Disposition: attachment; filename="xsa36-4.2.patch" Content-Transfer-Encoding: base64 QUNQSTogYWNwaV90YWJsZV9wYXJzZSgpIHNob3VsZCByZXR1cm4gaGFuZGxl cidzIGVycm9yIGNvZGUKCkN1cnJlbnRseSwgdGhlIGVycm9yIGNvZGUgcmV0 dXJuZWQgYnkgYWNwaV90YWJsZV9wYXJzZSgpJ3MgaGFuZGxlcgppcyBpZ25v cmVkLiBUaGlzIHBhdGNoIHdpbGwgcHJvcGFnYXRlIGhhbmRsZXIncyByZXR1 cm4gdmFsdWUgdG8KYWNwaV90YWJsZV9wYXJzZSgpJ3MgY2FsbGVyLgoKQU1E LElPTU1VOiBDbGVhbiB1cCBvbGQgZW50cmllcyBpbiByZW1hcHBpbmcgdGFi bGVzIHdoZW4gY3JlYXRpbmcgbmV3CmludGVycnVwdCBtYXBwaW5nLgoKV2hl biBjaGFuZ2luZyB0aGUgYWZmaW5pdHkgb2YgYW4gSVJRIGFzc29jaWF0ZWQg d2l0aCBhIHBhc3NlZAp0aHJvdWdoIFBDSSBkZXZpY2UsIGNsZWFyIHByZXZp b3VzIG1hcHBpbmcuCgpJbiBhZGRpdGlvbiwgYmVjYXVzZSBzb21lIEJJT1Nl cyBtYXkgaW5jb3JyZWN0bHkgcHJvZ3JhbSBJVlJTCmVudHJpZXMgZm9yIElP QVBJQyB0cnkgdG8gY2hlY2sgZm9yIGVudHJ5J3MgY29uc2lzdGVuY3kuIFNw ZWNpZmljYWxseSwKaWYgY29uZmxpY3RpbmcgZW50cmllcyBhcmUgZm91bmQg ZGlzYWJsZSBJT01NVSBpZiBwZXItZGV2aWNlCnJlbWFwcGluZyB0YWJsZSBp cyB1c2VkLiBJZiBlbnRyaWVzIHJlZmVyIHRvIGJvZ3VzIElPQVBJQyBJRHMK ZGlzYWJsZSBJT01NVSB1bmNvbmRpdGlvbmFsbHkKCkFNRCxJT01NVTogRGlz YWJsZSBJT01NVSBpZiBTQVRBIENvbWJpbmVkIG1vZGUgaXMgb24KCkFNRCdz IFNQNTEwMCBjaGlwc2V0IGNhbiBiZSBwbGFjZWQgaW50byBTQVRBIENvbWJp bmVkIG1vZGUKdGhhdCBtYXkgY2F1c2UgcHJldmVudCBkb20wIGZyb20gYm9v dGluZyB3aGVuIElPTU1VIGlzCmVuYWJsZWQgYW5kIHBlci1kZXZpY2UgaW50 ZXJydXB0IHJlbWFwcGluZyB0YWJsZSBpcyB1c2VkLgpXaGlsZSBTUDUxMDAg ZXJyYXR1bSAyOCByZXF1aXJlcyBCSU9TZXMgdG8gZGlzYWJsZSB0aGlzIG1v ZGUsCnNvbWUgbWF5IHN0aWxsIHVzZSBpdC4KClRoaXMgcGF0Y2ggY2hlY2tz IHdoZXRoZXIgdGhpcyBtb2RlIGlzIG9uIGFuZCwgaWYgcGVyLWRldmljZQp0 YWJsZSBpcyBpbiB1c2UsIGRpc2FibGVzIElPTU1VLgoKQU1ELElPTU1VOiBN YWtlIHBlci1kZXZpY2UgaW50ZXJydXB0IHJlbWFwcGluZyB0YWJsZSBkZWZh dWx0CgpVc2luZyBnbG9iYWwgaW50ZXJydXB0IHJlbWFwcGluZyB0YWJsZSBt YXkgYmUgaW5zZWN1cmUsIGFzCmRlc2NyaWJlZCBieSBYU0EtMzYuIFRoaXMg cGF0Y2ggbWFrZXMgcGVyLWRldmljZSBtb2RlIGRlZmF1bHQuCgpUaGlzIGlz IFhTQS0zNiAvIENWRS0yMDEzLTAxNTMuCgpTaWduZWQtb2ZmLWJ5OiBKYW4g QmV1bGljaCA8amJldWxpY2hAc3VzZS5jb20+ClNpZ25lZC1vZmYtYnk6IEJv cmlzIE9zdHJvdnNreSA8Ym9yaXMub3N0cm92c2t5QGFtZC5jb20+CgpBTUQg SU9NTVU6IGFsc28gc3BvdCBtaXNzaW5nIElPLUFQSUMgZW50cmllcyBpbiBJ VlJTIHRhYmxlCgpBcGFydCBmcm9tIGRlYWxpbmcgZHVwbGljYXRlIGNvbmZs aWN0aW5nIGVudHJpZXMsIHdlIGFsc28gaGF2ZSB0bwpoYW5kbGUgZmlybXdh cmUgb21pdHRpbmcgSU8tQVBJQyBlbnRyaWVzIGluIElWUlMgYWx0b2dldGhl ci4gTm90IGRvaW5nCnNvIGhhcyByZXN1bHRlZCBpbiBjL3MgMjY1MTc6NjAx MTM5ZTJiMGRiIHRvIGNyYXNoIHN1Y2ggc3lzdGVtcyBkdXJpbmcKYm9vdCAo d2hlcmVhcyB3aXRoIHRoZSBjaGFuZ2UgaGVyZSB0aGUgSU9NTVUgZ2V0cyBk aXNhYmxlZCBqdXN0IGFzIGlzCmJlaW5nIGRvbmUgaW4gdGhlIG90aGVyIGNh c2VzLCBpLmUuIHVubGVzcyBnbG9iYWwgdGFibGVzIGFyZSBiZWluZwp1c2Vk KS4KCkRlYnVnZ2luZyB0aGlzIGlzc3VlIGhhcyBhbHNvIHBvaW50ZWQgb3V0 IHRoYXQgdGhlIGRlYnVnIGxvZyBvdXRwdXQgaXMKcHJldHR5IHVnbHkgdG8g bG9vayBhdCAtIGNvbnNvbGlkYXRlIHRoZSBvdXRwdXQsIGFuZCBhZGQgb25l IGV4dHJhCml0ZW0gZm9yIHRoZSBJVkhEIHNwZWNpYWwgZW50cmllcywgc28g dGhhdCBmdXR1cmUgaXNzdWVzIGFyZSBlYXNpZXIKdG8gYW5hbHl6ZS4KClNp Z25lZC1vZmYtYnk6IEphbiBCZXVsaWNoIDxqYmV1bGljaEBzdXNlLmNvbT4K VGVzdGVkLWJ5OiBTYW5kZXIgRWlrZWxlbmJvb20gPGxpbnV4QGVpa2VsZW5i b29tLml0PgoKLS0tIGEveGVuL2FyY2gveDg2L2lycS5jCisrKyBiL3hlbi9h cmNoL3g4Ni9pcnEuYwpAQCAtMTk0Miw5ICsxOTQyLDYgQEAgaW50IG1hcF9k b21haW5fcGlycSgKICAgICAgICAgc3Bpbl9sb2NrX2lycXNhdmUoJmRlc2Mt PmxvY2ssIGZsYWdzKTsKICAgICAgICAgc2V0X2RvbWFpbl9pcnFfcGlycShk LCBpcnEsIGluZm8pOwogICAgICAgICBzcGluX3VubG9ja19pcnFyZXN0b3Jl KCZkZXNjLT5sb2NrLCBmbGFncyk7Ci0KLSAgICAgICAgaWYgKCBvcHRfaXJx X3ZlY3Rvcl9tYXAgPT0gT1BUX0lSUV9WRUNUT1JfTUFQX1BFUkRFViApCi0g ICAgICAgICAgICBwcmludGsoWEVOTE9HX0lORk8gIlBlci1kZXZpY2UgdmVj dG9yIG1hcHMgZm9yIEdTSXMgbm90IGltcGxlbWVudGVkIHlldC5cbiIpOwog ICAgIH0KIAogZG9uZToKLS0tIGEveGVuL2RyaXZlcnMvYWNwaS90YWJsZXMu YworKysgYi94ZW4vZHJpdmVycy9hY3BpL3RhYmxlcy5jCkBAIC0yNjcsNyAr MjY3LDcgQEAgYWNwaV90YWJsZV9wYXJzZV9tYWR0KGVudW0gYWNwaV9tYWR0 X3R5cAogICogQGhhbmRsZXI6IGhhbmRsZXIgdG8gcnVuCiAgKgogICogU2Nh biB0aGUgQUNQSSBTeXN0ZW0gRGVzY3JpcHRvciBUYWJsZSAoU1REKSBmb3Ig YSB0YWJsZSBtYXRjaGluZyBAaWQsCi0gKiBydW4gQGhhbmRsZXIgb24gaXQu ICBSZXR1cm4gMCBpZiB0YWJsZSBmb3VuZCwgcmV0dXJuIG9uIGlmIG5vdC4K KyAqIHJ1biBAaGFuZGxlciBvbiBpdC4KICAqLwogaW50IF9faW5pdCBhY3Bp X3RhYmxlX3BhcnNlKGNoYXIgKmlkLCBhY3BpX3RhYmxlX2hhbmRsZXIgaGFu ZGxlcikKIHsKQEAgLTI4Miw4ICsyODIsNyBAQCBpbnQgX19pbml0IGFjcGlf dGFibGVfcGFyc2UoY2hhciAqaWQsIGFjCiAJCWFjcGlfZ2V0X3RhYmxlKGlk LCAwLCAmdGFibGUpOwogCiAJaWYgKHRhYmxlKSB7Ci0JCWhhbmRsZXIodGFi bGUpOwotCQlyZXR1cm4gMDsKKwkJcmV0dXJuIGhhbmRsZXIodGFibGUpOwog CX0gZWxzZQogCQlyZXR1cm4gMTsKIH0KLS0tIGEveGVuL2RyaXZlcnMvcGFz c3Rocm91Z2gvYW1kL2lvbW11X2FjcGkuYworKysgYi94ZW4vZHJpdmVycy9w YXNzdGhyb3VnaC9hbWQvaW9tbXVfYWNwaS5jCkBAIC0yMiw2ICsyMiw3IEBA CiAjaW5jbHVkZSA8eGVuL2Vycm5vLmg+CiAjaW5jbHVkZSA8eGVuL2FjcGku aD4KICNpbmNsdWRlIDxhc20vYXBpY2RlZi5oPgorI2luY2x1ZGUgPGFzbS9p b19hcGljLmg+CiAjaW5jbHVkZSA8YXNtL2FtZC1pb21tdS5oPgogI2luY2x1 ZGUgPGFzbS9odm0vc3ZtL2FtZC1pb21tdS1wcm90by5oPgogCkBAIC02MzUs NiArNjM2LDcgQEAgc3RhdGljIHUxNiBfX2luaXQgcGFyc2VfaXZoZF9kZXZp Y2Vfc3BlYwogICAgIHUxNiBoZWFkZXJfbGVuZ3RoLCB1MTYgYmxvY2tfbGVu Z3RoLCBzdHJ1Y3QgYW1kX2lvbW11ICppb21tdSkKIHsKICAgICB1MTYgZGV2 X2xlbmd0aCwgYmRmOworICAgIGludCBhcGljOwogCiAgICAgZGV2X2xlbmd0 aCA9IHNpemVvZigqc3BlY2lhbCk7CiAgICAgaWYgKCBoZWFkZXJfbGVuZ3Ro IDwgKGJsb2NrX2xlbmd0aCArIGRldl9sZW5ndGgpICkKQEAgLTY1MSwxMCAr NjUzLDU5IEBAIHN0YXRpYyB1MTYgX19pbml0IHBhcnNlX2l2aGRfZGV2aWNl X3NwZWMKICAgICB9CiAKICAgICBhZGRfaXZyc19tYXBwaW5nX2VudHJ5KGJk ZiwgYmRmLCBzcGVjaWFsLT5oZWFkZXIuZGF0YV9zZXR0aW5nLCBpb21tdSk7 Ci0gICAgLyogc2V0IGRldmljZSBpZCBvZiBpb2FwaWMgKi8KLSAgICBpb2Fw aWNfc2JkZltzcGVjaWFsLT5oYW5kbGVdLmJkZiA9IGJkZjsKLSAgICBpb2Fw aWNfc2JkZltzcGVjaWFsLT5oYW5kbGVdLnNlZyA9IHNlZzsKLSAgICByZXR1 cm4gZGV2X2xlbmd0aDsKKworICAgIGlmICggc3BlY2lhbC0+dmFyaWV0eSAh PSBBQ1BJX0lWSERfSU9BUElDICkKKyAgICB7CisgICAgICAgIGlmICggc3Bl Y2lhbC0+dmFyaWV0eSAhPSBBQ1BJX0lWSERfSFBFVCApCisgICAgICAgICAg ICBwcmludGsoWEVOTE9HX0VSUiAiVW5yZWNvZ25pemVkIElWSEQgc3BlY2lh bCB2YXJpZXR5ICUjeFxuIiwKKyAgICAgICAgICAgICAgICAgICBzcGVjaWFs LT52YXJpZXR5KTsKKyAgICAgICAgcmV0dXJuIGRldl9sZW5ndGg7CisgICAg fQorCisgICAgLyoKKyAgICAgKiBTb21lIEJJT1NlcyBoYXZlIElPQVBJQyBi cm9rZW4gZW50cmllcyBzbyB3ZSBjaGVjayBmb3IgSVZSUworICAgICAqIGNv bnNpc3RlbmN5IGhlcmUgLS0tIHdoZXRoZXIgZW50cnkncyBJT0FQSUMgSUQg aXMgdmFsaWQgYW5kCisgICAgICogd2hldGhlciB0aGVyZSBhcmUgY29uZmxp Y3RpbmcvZHVwbGljYXRlZCBlbnRyaWVzLgorICAgICAqLworICAgIGZvciAo IGFwaWMgPSAwOyBhcGljIDwgbnJfaW9hcGljczsgYXBpYysrICkKKyAgICB7 CisgICAgICAgIGlmICggSU9fQVBJQ19JRChhcGljKSAhPSBzcGVjaWFsLT5o YW5kbGUgKQorICAgICAgICAgICAgY29udGludWU7CisKKyAgICAgICAgaWYg KCBpb2FwaWNfc2JkZltzcGVjaWFsLT5oYW5kbGVdLnBpbl9zZXR1cCApCisg ICAgICAgIHsKKyAgICAgICAgICAgIGlmICggaW9hcGljX3NiZGZbc3BlY2lh bC0+aGFuZGxlXS5iZGYgPT0gYmRmICYmCisgICAgICAgICAgICAgICAgIGlv YXBpY19zYmRmW3NwZWNpYWwtPmhhbmRsZV0uc2VnID09IHNlZyApCisgICAg ICAgICAgICAgICAgQU1EX0lPTU1VX0RFQlVHKCJJVkhEIFdhcm5pbmc6IER1 cGxpY2F0ZSBJTy1BUElDICUjeCBlbnRyaWVzXG4iLAorICAgICAgICAgICAg ICAgICAgICAgICAgICAgICAgICBzcGVjaWFsLT5oYW5kbGUpOworICAgICAg ICAgICAgZWxzZQorICAgICAgICAgICAgeworICAgICAgICAgICAgICAgIHBy aW50ayhYRU5MT0dfRVJSICJJVkhEIEVycm9yOiBDb25mbGljdGluZyBJTy1B UElDICUjeCBlbnRyaWVzXG4iLAorICAgICAgICAgICAgICAgICAgICAgICBz cGVjaWFsLT5oYW5kbGUpOworICAgICAgICAgICAgICAgIGlmICggYW1kX2lv bW11X3BlcmRldl9pbnRyZW1hcCApCisgICAgICAgICAgICAgICAgICAgIHJl dHVybiAwOworICAgICAgICAgICAgfQorICAgICAgICB9CisgICAgICAgIGVs c2UKKyAgICAgICAgeworICAgICAgICAgICAgLyogc2V0IGRldmljZSBpZCBv ZiBpb2FwaWMgKi8KKyAgICAgICAgICAgIGlvYXBpY19zYmRmW3NwZWNpYWwt PmhhbmRsZV0uYmRmID0gYmRmOworICAgICAgICAgICAgaW9hcGljX3NiZGZb c3BlY2lhbC0+aGFuZGxlXS5zZWcgPSBzZWc7CisKKyAgICAgICAgICAgIGlv YXBpY19zYmRmW3NwZWNpYWwtPmhhbmRsZV0ucGluX3NldHVwID0geHphbGxv Y19hcnJheSgKKyAgICAgICAgICAgICAgICB1bnNpZ25lZCBsb25nLCBCSVRT X1RPX0xPTkdTKG5yX2lvYXBpY19lbnRyaWVzW2FwaWNdKSk7CisgICAgICAg ICAgICBpZiAoIG5yX2lvYXBpY19lbnRyaWVzW2FwaWNdICYmCisgICAgICAg ICAgICAgICAgICFpb2FwaWNfc2JkZltJT19BUElDX0lEKGFwaWMpXS5waW5f c2V0dXAgKQorICAgICAgICAgICAgeworICAgICAgICAgICAgICAgIHByaW50 ayhYRU5MT0dfRVJSICJJVkhEIEVycm9yOiBPdXQgb2YgbWVtb3J5XG4iKTsK KyAgICAgICAgICAgICAgICByZXR1cm4gMDsKKyAgICAgICAgICAgIH0KKyAg ICAgICAgfQorICAgICAgICByZXR1cm4gZGV2X2xlbmd0aDsKKyAgICB9CisK KyAgICBwcmludGsoWEVOTE9HX0VSUiAiSVZIRCBFcnJvcjogSW52YWxpZCBJ Ty1BUElDICUjeFxuIiwgc3BlY2lhbC0+aGFuZGxlKTsKKyAgICByZXR1cm4g MDsKIH0KIAogc3RhdGljIGludCBfX2luaXQgcGFyc2VfaXZoZF9ibG9jayhj b25zdCBzdHJ1Y3QgYWNwaV9pdnJzX2hhcmR3YXJlICppdmhkX2Jsb2NrKQpA QCAtODE4LDYgKzg2OSw3IEBAIHN0YXRpYyBpbnQgX19pbml0IHBhcnNlX2l2 cnNfdGFibGUoc3RydWMKIHsKICAgICBjb25zdCBzdHJ1Y3QgYWNwaV9pdnJz X2hlYWRlciAqaXZyc19ibG9jazsKICAgICB1bnNpZ25lZCBsb25nIGxlbmd0 aDsKKyAgICB1bnNpZ25lZCBpbnQgYXBpYzsKICAgICBpbnQgZXJyb3IgPSAw OwogCiAgICAgQlVHX09OKCF0YWJsZSk7CkBAIC04NTAsNiArOTAyLDI5IEBA IHN0YXRpYyBpbnQgX19pbml0IHBhcnNlX2l2cnNfdGFibGUoc3RydWMKICAg ICAgICAgbGVuZ3RoICs9IGl2cnNfYmxvY2stPmxlbmd0aDsKICAgICB9CiAK KyAgICAvKiBFYWNoIElPLUFQSUMgbXVzdCBoYXZlIGJlZW4gbWVudGlvbmVk IGluIHRoZSB0YWJsZS4gKi8KKyAgICBmb3IgKCBhcGljID0gMDsgIWVycm9y ICYmIGFwaWMgPCBucl9pb2FwaWNzOyArK2FwaWMgKQorICAgIHsKKyAgICAg ICAgaWYgKCAhbnJfaW9hcGljX2VudHJpZXNbYXBpY10gfHwKKyAgICAgICAg ICAgICBpb2FwaWNfc2JkZltJT19BUElDX0lEKGFwaWMpXS5waW5fc2V0dXAg KQorICAgICAgICAgICAgY29udGludWU7CisKKyAgICAgICAgcHJpbnRrKFhF TkxPR19FUlIgIklWSEQgRXJyb3I6IG5vIGluZm9ybWF0aW9uIGZvciBJTy1B UElDICUjeFxuIiwKKyAgICAgICAgICAgICAgIElPX0FQSUNfSUQoYXBpYykp OworICAgICAgICBpZiAoIGFtZF9pb21tdV9wZXJkZXZfaW50cmVtYXAgKQor ICAgICAgICAgICAgZXJyb3IgPSAtRU5YSU87CisgICAgICAgIGVsc2UKKyAg ICAgICAgeworICAgICAgICAgICAgaW9hcGljX3NiZGZbSU9fQVBJQ19JRChh cGljKV0ucGluX3NldHVwID0geHphbGxvY19hcnJheSgKKyAgICAgICAgICAg ICAgICB1bnNpZ25lZCBsb25nLCBCSVRTX1RPX0xPTkdTKG5yX2lvYXBpY19l bnRyaWVzW2FwaWNdKSk7CisgICAgICAgICAgICBpZiAoICFpb2FwaWNfc2Jk ZltJT19BUElDX0lEKGFwaWMpXS5waW5fc2V0dXAgKQorICAgICAgICAgICAg eworICAgICAgICAgICAgICAgIHByaW50ayhYRU5MT0dfRVJSICJJVkhEIEVy cm9yOiBPdXQgb2YgbWVtb3J5XG4iKTsKKyAgICAgICAgICAgICAgICBlcnJv ciA9IC1FTk9NRU07CisgICAgICAgICAgICB9CisgICAgICAgIH0KKyAgICB9 CisKICAgICByZXR1cm4gZXJyb3I7CiB9CiAKLS0tIGEveGVuL2RyaXZlcnMv cGFzc3Rocm91Z2gvYW1kL2lvbW11X2luaXQuYworKysgYi94ZW4vZHJpdmVy cy9wYXNzdGhyb3VnaC9hbWQvaW9tbXVfaW5pdC5jCkBAIC0xMTI2LDEyICsx MTI2LDQ1IEBAIHN0YXRpYyBpbnQgX19pbml0IGFtZF9pb21tdV9zZXR1cF9k ZXZpY2UKICAgICByZXR1cm4gMDsKIH0KIAorLyogQ2hlY2sgd2hldGhlciBT UDUxMDAgU0FUQSBDb21iaW5lZCBtb2RlIGlzIG9uICovCitzdGF0aWMgYm9v bF90IF9faW5pdCBhbWRfc3A1MTAwX2VycmF0dW0yOCh2b2lkKQoreworICAg IHUzMiBidXMsIGlkOworICAgIHUxNiB2ZW5kb3JfaWQsIGRldl9pZDsKKyAg ICB1OCBieXRlOworCisgICAgZm9yIChidXMgPSAwOyBidXMgPCAyNTY7IGJ1 cysrKQorICAgIHsKKyAgICAgICAgaWQgPSBwY2lfY29uZl9yZWFkMzIoMCwg YnVzLCAweDE0LCAwLCBQQ0lfVkVORE9SX0lEKTsKKworICAgICAgICB2ZW5k b3JfaWQgPSBpZCAmIDB4ZmZmZjsKKyAgICAgICAgZGV2X2lkID0gKGlkID4+ IDE2KSAmIDB4ZmZmZjsKKworICAgICAgICAvKiBTUDUxMDAgU01CdXMgbW9k dWxlIHNldHMgQ29tYmluZWQgbW9kZSBvbiAqLworICAgICAgICBpZiAodmVu ZG9yX2lkICE9IDB4MTAwMiB8fCBkZXZfaWQgIT0gMHg0Mzg1KQorICAgICAg ICAgICAgY29udGludWU7CisKKyAgICAgICAgYnl0ZSA9IHBjaV9jb25mX3Jl YWQ4KDAsIGJ1cywgMHgxNCwgMCwgMHhhZCk7CisgICAgICAgIGlmICggKGJ5 dGUgPj4gMykgJiAxICkKKyAgICAgICAgeworICAgICAgICAgICAgcHJpbnRr KFhFTkxPR19XQVJOSU5HICJBTUQtVmk6IFNQNTEwMCBlcnJhdHVtIDI4IGRl dGVjdGVkLCBkaXNhYmxpbmcgSU9NTVUuXG4iCisgICAgICAgICAgICAgICAg ICAgIklmIHBvc3NpYmxlLCBkaXNhYmxlIFNBVEEgQ29tYmluZWQgbW9kZSBp biBCSU9TIG9yIGNvbnRhY3QgeW91ciB2ZW5kb3IgZm9yIEJJT1MgdXBkYXRl LlxuIik7CisgICAgICAgICAgICByZXR1cm4gMTsKKyAgICAgICAgfQorICAg IH0KKworICAgIHJldHVybiAwOworfQorCiBpbnQgX19pbml0IGFtZF9pb21t dV9pbml0KHZvaWQpCiB7CiAgICAgc3RydWN0IGFtZF9pb21tdSAqaW9tbXU7 CiAKICAgICBCVUdfT04oICFpb21tdV9mb3VuZCgpICk7CiAKKyAgICBpZiAo IGFtZF9pb21tdV9wZXJkZXZfaW50cmVtYXAgJiYgYW1kX3NwNTEwMF9lcnJh dHVtMjgoKSApCisgICAgICAgIGdvdG8gZXJyb3Jfb3V0OworCiAgICAgaXZy c19iZGZfZW50cmllcyA9IGFtZF9pb21tdV9nZXRfaXZyc19kZXZfZW50cmll cygpOwogCiAgICAgaWYgKCAhaXZyc19iZGZfZW50cmllcyApCi0tLSBhL3hl bi9kcml2ZXJzL3Bhc3N0aHJvdWdoL2FtZC9pb21tdV9pbnRyLmMKKysrIGIv eGVuL2RyaXZlcnMvcGFzc3Rocm91Z2gvYW1kL2lvbW11X2ludHIuYwpAQCAt OTksMTIgKzk5LDEyIEBAIHN0YXRpYyB2b2lkIHVwZGF0ZV9pbnRyZW1hcF9l bnRyeSh1MzIqIGUKIHN0YXRpYyB2b2lkIHVwZGF0ZV9pbnRyZW1hcF9lbnRy eV9mcm9tX2lvYXBpYygKICAgICBpbnQgYmRmLAogICAgIHN0cnVjdCBhbWRf aW9tbXUgKmlvbW11LAotICAgIHN0cnVjdCBJT19BUElDX3JvdXRlX2VudHJ5 ICppb2FwaWNfcnRlKQorICAgIGNvbnN0IHN0cnVjdCBJT19BUElDX3JvdXRl X2VudHJ5ICpydGUsCisgICAgY29uc3Qgc3RydWN0IElPX0FQSUNfcm91dGVf ZW50cnkgKm9sZF9ydGUpCiB7CiAgICAgdW5zaWduZWQgbG9uZyBmbGFnczsK ICAgICB1MzIqIGVudHJ5OwogICAgIHU4IGRlbGl2ZXJ5X21vZGUsIGRlc3Qs IHZlY3RvciwgZGVzdF9tb2RlOwotICAgIHN0cnVjdCBJT19BUElDX3JvdXRl X2VudHJ5ICpydGUgPSBpb2FwaWNfcnRlOwogICAgIGludCByZXFfaWQ7CiAg ICAgc3BpbmxvY2tfdCAqbG9jazsKICAgICBpbnQgb2Zmc2V0OwpAQCAtMTIw LDYgKzEyMCwxNCBAQCBzdGF0aWMgdm9pZCB1cGRhdGVfaW50cmVtYXBfZW50 cnlfZnJvbV9pCiAgICAgc3Bpbl9sb2NrX2lycXNhdmUobG9jaywgZmxhZ3Mp OwogCiAgICAgb2Zmc2V0ID0gZ2V0X2ludHJlbWFwX29mZnNldCh2ZWN0b3Is IGRlbGl2ZXJ5X21vZGUpOworICAgIGlmICggb2xkX3J0ZSApCisgICAgewor ICAgICAgICBpbnQgb2xkX29mZnNldCA9IGdldF9pbnRyZW1hcF9vZmZzZXQo b2xkX3J0ZS0+dmVjdG9yLAorICAgICAgICAgICAgICAgICAgICAgICAgICAg ICAgICAgICAgICAgICAgICAgb2xkX3J0ZS0+ZGVsaXZlcnlfbW9kZSk7CisK KyAgICAgICAgaWYgKCBvZmZzZXQgIT0gb2xkX29mZnNldCApCisgICAgICAg ICAgICBmcmVlX2ludHJlbWFwX2VudHJ5KGlvbW11LT5zZWcsIGJkZiwgb2xk X29mZnNldCk7CisgICAgfQogICAgIGVudHJ5ID0gKHUzMiopZ2V0X2ludHJl bWFwX2VudHJ5KGlvbW11LT5zZWcsIHJlcV9pZCwgb2Zmc2V0KTsKICAgICB1 cGRhdGVfaW50cmVtYXBfZW50cnkoZW50cnksIHZlY3RvciwgZGVsaXZlcnlf bW9kZSwgZGVzdF9tb2RlLCBkZXN0KTsKIApAQCAtMTg4LDYgKzE5Niw3IEBA IGludCBfX2luaXQgYW1kX2lvbW11X3NldHVwX2lvYXBpY19yZW1hcHAKICAg ICAgICAgICAgICAgICBhbWRfaW9tbXVfZmx1c2hfaW50cmVtYXAoaW9tbXUs IHJlcV9pZCk7CiAgICAgICAgICAgICAgICAgc3Bpbl91bmxvY2tfaXJxcmVz dG9yZSgmaW9tbXUtPmxvY2ssIGZsYWdzKTsKICAgICAgICAgICAgIH0KKyAg ICAgICAgICAgIHNldF9iaXQocGluLCBpb2FwaWNfc2JkZltJT19BUElDX0lE KGFwaWMpXS5waW5fc2V0dXApOwogICAgICAgICB9CiAgICAgfQogICAgIHJl dHVybiAwOwpAQCAtMTk5LDYgKzIwOCw3IEBAIHZvaWQgYW1kX2lvbW11X2lv YXBpY191cGRhdGVfaXJlKAogICAgIHN0cnVjdCBJT19BUElDX3JvdXRlX2Vu dHJ5IG9sZF9ydGUgPSB7IDAgfTsKICAgICBzdHJ1Y3QgSU9fQVBJQ19yb3V0 ZV9lbnRyeSBuZXdfcnRlID0geyAwIH07CiAgICAgdW5zaWduZWQgaW50IHJ0 ZV9sbyA9IChyZWcgJiAxKSA/IHJlZyAtIDEgOiByZWc7CisgICAgdW5zaWdu ZWQgaW50IHBpbiA9IChyZWcgLSAweDEwKSAvIDI7CiAgICAgaW50IHNhdmVk X21hc2ssIHNlZywgYmRmOwogICAgIHN0cnVjdCBhbWRfaW9tbXUgKmlvbW11 OwogCkBAIC0yMzYsNiArMjQ2LDE0IEBAIHZvaWQgYW1kX2lvbW11X2lvYXBp Y191cGRhdGVfaXJlKAogICAgICAgICAqKCgodTMyICopJm5ld19ydGUpICsg MSkgPSB2YWx1ZTsKICAgICB9CiAKKyAgICBpZiAoIG5ld19ydGUubWFzayAm JgorICAgICAgICAgIXRlc3RfYml0KHBpbiwgaW9hcGljX3NiZGZbSU9fQVBJ Q19JRChhcGljKV0ucGluX3NldHVwKSApCisgICAgeworICAgICAgICBBU1NF UlQoc2F2ZWRfbWFzayk7CisgICAgICAgIF9faW9fYXBpY193cml0ZShhcGlj LCByZWcsIHZhbHVlKTsKKyAgICAgICAgcmV0dXJuOworICAgIH0KKwogICAg IC8qIG1hc2sgdGhlIGludGVycnVwdCB3aGlsZSB3ZSBjaGFuZ2UgdGhlIGlu dHJlbWFwIHRhYmxlICovCiAgICAgaWYgKCAhc2F2ZWRfbWFzayApCiAgICAg ewpAQCAtMjQ0LDcgKzI2MiwxMSBAQCB2b2lkIGFtZF9pb21tdV9pb2FwaWNf dXBkYXRlX2lyZSgKICAgICB9CiAKICAgICAvKiBVcGRhdGUgaW50ZXJydXB0 IHJlbWFwcGluZyBlbnRyeSAqLwotICAgIHVwZGF0ZV9pbnRyZW1hcF9lbnRy eV9mcm9tX2lvYXBpYyhiZGYsIGlvbW11LCAmbmV3X3J0ZSk7CisgICAgdXBk YXRlX2ludHJlbWFwX2VudHJ5X2Zyb21faW9hcGljKAorICAgICAgICBiZGYs IGlvbW11LCAmbmV3X3J0ZSwKKyAgICAgICAgdGVzdF9hbmRfc2V0X2JpdChw aW4sCisgICAgICAgICAgICAgICAgICAgICAgICAgaW9hcGljX3NiZGZbSU9f QVBJQ19JRChhcGljKV0ucGluX3NldHVwKSA/ICZvbGRfcnRlCisgICAgICAg ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg ICAgICAgICAgICAgICA6IE5VTEwpOwogCiAgICAgLyogRm9yd2FyZCB3cml0 ZSBhY2Nlc3MgdG8gSU8tQVBJQyBSVEUgKi8KICAgICBfX2lvX2FwaWNfd3Jp dGUoYXBpYywgcmVnLCB2YWx1ZSk7CkBAIC0zNTQsNiArMzc2LDEyIEBAIHZv aWQgYW1kX2lvbW11X21zaV9tc2dfdXBkYXRlX2lyZSgKICAgICAgICAgcmV0 dXJuOwogICAgIH0KIAorICAgIGlmICggbXNpX2Rlc2MtPnJlbWFwX2luZGV4 ID49IDAgKQorICAgICAgICB1cGRhdGVfaW50cmVtYXBfZW50cnlfZnJvbV9t c2lfbXNnKGlvbW11LCBwZGV2LCBtc2lfZGVzYywgTlVMTCk7CisKKyAgICBp ZiAoICFtc2cgKQorICAgICAgICByZXR1cm47CisKICAgICB1cGRhdGVfaW50 cmVtYXBfZW50cnlfZnJvbV9tc2lfbXNnKGlvbW11LCBwZGV2LCBtc2lfZGVz YywgbXNnKTsKIH0KIAotLS0gYS94ZW4vZHJpdmVycy9wYXNzdGhyb3VnaC9h bWQvcGNpX2FtZF9pb21tdS5jCisrKyBiL3hlbi9kcml2ZXJzL3Bhc3N0aHJv dWdoL2FtZC9wY2lfYW1kX2lvbW11LmMKQEAgLTIwNSw2ICsyMDUsOCBAQCBp bnQgX19pbml0IGFtZF9pb3ZfZGV0ZWN0KHZvaWQpCiAgICAgewogICAgICAg ICBwcmludGsoIkFNRC1WaTogTm90IG92ZXJyaWRpbmcgaXJxX3ZlY3Rvcl9t YXAgc2V0dGluZ1xuIik7CiAgICAgfQorICAgIGlmICggIWFtZF9pb21tdV9w ZXJkZXZfaW50cmVtYXAgKQorICAgICAgICBwcmludGsoWEVOTE9HX1dBUk5J TkcgIkFNRC1WaTogVXNpbmcgZ2xvYmFsIGludGVycnVwdCByZW1hcCB0YWJs ZSBpcyBub3QgcmVjb21tZW5kZWQgKHNlZSBYU0EtMzYpIVxuIik7CiAgICAg cmV0dXJuIHNjYW5fcGNpX2RldmljZXMoKTsKIH0KIAotLS0gYS94ZW4vZHJp dmVycy9wYXNzdGhyb3VnaC9pb21tdS5jCisrKyBiL3hlbi9kcml2ZXJzL3Bh c3N0aHJvdWdoL2lvbW11LmMKQEAgLTUyLDcgKzUyLDcgQEAgYm9vbF90IF9f cmVhZF9tb3N0bHkgaW9tbXVfcWludmFsID0gMTsKIGJvb2xfdCBfX3JlYWRf bW9zdGx5IGlvbW11X2ludHJlbWFwID0gMTsKIGJvb2xfdCBfX3JlYWRfbW9z dGx5IGlvbW11X2hhcF9wdF9zaGFyZSA9IDE7CiBib29sX3QgX19yZWFkX21v c3RseSBpb21tdV9kZWJ1ZzsKLWJvb2xfdCBfX3JlYWRfbW9zdGx5IGFtZF9p b21tdV9wZXJkZXZfaW50cmVtYXA7Citib29sX3QgX19yZWFkX21vc3RseSBh bWRfaW9tbXVfcGVyZGV2X2ludHJlbWFwID0gMTsKIAogREVGSU5FX1BFUl9D UFUoYm9vbF90LCBpb21tdV9kb250X2ZsdXNoX2lvdGxiKTsKIAotLS0gYS94 ZW4vaW5jbHVkZS9hc20teDg2L2h2bS9zdm0vYW1kLWlvbW11LXByb3RvLmgK KysrIGIveGVuL2luY2x1ZGUvYXNtLXg4Ni9odm0vc3ZtL2FtZC1pb21tdS1w cm90by5oCkBAIC0xMDAsNiArMTAwLDcgQEAgdm9pZCBhbWRfaW9tbXVfcmVh ZF9tc2lfZnJvbV9pcmUoCiAKIGV4dGVybiBzdHJ1Y3QgaW9hcGljX3NiZGYg ewogICAgIHUxNiBiZGYsIHNlZzsKKyAgICB1bnNpZ25lZCBsb25nICpwaW5f c2V0dXA7CiB9IGlvYXBpY19zYmRmW01BWF9JT19BUElDU107CiBleHRlcm4g dm9pZCAqc2hhcmVkX2ludHJlbWFwX3RhYmxlOwogCg== --=separator Content-Type: application/octet-stream; name="xsa36-unstable.patch" Content-Disposition: attachment; filename="xsa36-unstable.patch" Content-Transfer-Encoding: base64 QUNQSTogYWNwaV90YWJsZV9wYXJzZSgpIHNob3VsZCByZXR1cm4gaGFuZGxl cidzIGVycm9yIGNvZGUKCkN1cnJlbnRseSwgdGhlIGVycm9yIGNvZGUgcmV0 dXJuZWQgYnkgYWNwaV90YWJsZV9wYXJzZSgpJ3MgaGFuZGxlcgppcyBpZ25v cmVkLiBUaGlzIHBhdGNoIHdpbGwgcHJvcGFnYXRlIGhhbmRsZXIncyByZXR1 cm4gdmFsdWUgdG8KYWNwaV90YWJsZV9wYXJzZSgpJ3MgY2FsbGVyLgoKQU1E LElPTU1VOiBDbGVhbiB1cCBvbGQgZW50cmllcyBpbiByZW1hcHBpbmcgdGFi bGVzIHdoZW4gY3JlYXRpbmcgbmV3CmludGVycnVwdCBtYXBwaW5nLgoKV2hl biBjaGFuZ2luZyB0aGUgYWZmaW5pdHkgb2YgYW4gSVJRIGFzc29jaWF0ZWQg d2l0aCBhIHBhc3NlZAp0aHJvdWdoIFBDSSBkZXZpY2UsIGNsZWFyIHByZXZp b3VzIG1hcHBpbmcuCgpJbiBhZGRpdGlvbiwgYmVjYXVzZSBzb21lIEJJT1Nl cyBtYXkgaW5jb3JyZWN0bHkgcHJvZ3JhbSBJVlJTCmVudHJpZXMgZm9yIElP QVBJQyB0cnkgdG8gY2hlY2sgZm9yIGVudHJ5J3MgY29uc2lzdGVuY3kuIFNw ZWNpZmljYWxseSwKaWYgY29uZmxpY3RpbmcgZW50cmllcyBhcmUgZm91bmQg ZGlzYWJsZSBJT01NVSBpZiBwZXItZGV2aWNlCnJlbWFwcGluZyB0YWJsZSBp cyB1c2VkLiBJZiBlbnRyaWVzIHJlZmVyIHRvIGJvZ3VzIElPQVBJQyBJRHMK ZGlzYWJsZSBJT01NVSB1bmNvbmRpdGlvbmFsbHkKCkFNRCxJT01NVTogRGlz YWJsZSBJT01NVSBpZiBTQVRBIENvbWJpbmVkIG1vZGUgaXMgb24KCkFNRCdz IFNQNTEwMCBjaGlwc2V0IGNhbiBiZSBwbGFjZWQgaW50byBTQVRBIENvbWJp bmVkIG1vZGUKdGhhdCBtYXkgY2F1c2UgcHJldmVudCBkb20wIGZyb20gYm9v dGluZyB3aGVuIElPTU1VIGlzCmVuYWJsZWQgYW5kIHBlci1kZXZpY2UgaW50 ZXJydXB0IHJlbWFwcGluZyB0YWJsZSBpcyB1c2VkLgpXaGlsZSBTUDUxMDAg ZXJyYXR1bSAyOCByZXF1aXJlcyBCSU9TZXMgdG8gZGlzYWJsZSB0aGlzIG1v ZGUsCnNvbWUgbWF5IHN0aWxsIHVzZSBpdC4KClRoaXMgcGF0Y2ggY2hlY2tz IHdoZXRoZXIgdGhpcyBtb2RlIGlzIG9uIGFuZCwgaWYgcGVyLWRldmljZQp0 YWJsZSBpcyBpbiB1c2UsIGRpc2FibGVzIElPTU1VLgoKQU1ELElPTU1VOiBN YWtlIHBlci1kZXZpY2UgaW50ZXJydXB0IHJlbWFwcGluZyB0YWJsZSBkZWZh dWx0CgpVc2luZyBnbG9iYWwgaW50ZXJydXB0IHJlbWFwcGluZyB0YWJsZSBt YXkgYmUgaW5zZWN1cmUsIGFzCmRlc2NyaWJlZCBieSBYU0EtMzYuIFRoaXMg cGF0Y2ggbWFrZXMgcGVyLWRldmljZSBtb2RlIGRlZmF1bHQuCgpUaGlzIGlz IFhTQS0zNiAvIENWRS0yMDEzLTAxNTMuCgpTaWduZWQtb2ZmLWJ5OiBKYW4g QmV1bGljaCA8amJldWxpY2hAc3VzZS5jb20+ClNpZ25lZC1vZmYtYnk6IEJv cmlzIE9zdHJvdnNreSA8Ym9yaXMub3N0cm92c2t5QGFtZC5jb20+CgpBTUQg SU9NTVU6IGFsc28gc3BvdCBtaXNzaW5nIElPLUFQSUMgZW50cmllcyBpbiBJ VlJTIHRhYmxlCgpBcGFydCBmcm9tIGRlYWxpbmcgZHVwbGljYXRlIGNvbmZs aWN0aW5nIGVudHJpZXMsIHdlIGFsc28gaGF2ZSB0bwpoYW5kbGUgZmlybXdh cmUgb21pdHRpbmcgSU8tQVBJQyBlbnRyaWVzIGluIElWUlMgYWx0b2dldGhl ci4gTm90IGRvaW5nCnNvIGhhcyByZXN1bHRlZCBpbiBjL3MgMjY1MTc6NjAx MTM5ZTJiMGRiIHRvIGNyYXNoIHN1Y2ggc3lzdGVtcyBkdXJpbmcKYm9vdCAo d2hlcmVhcyB3aXRoIHRoZSBjaGFuZ2UgaGVyZSB0aGUgSU9NTVUgZ2V0cyBk aXNhYmxlZCBqdXN0IGFzIGlzCmJlaW5nIGRvbmUgaW4gdGhlIG90aGVyIGNh c2VzLCBpLmUuIHVubGVzcyBnbG9iYWwgdGFibGVzIGFyZSBiZWluZwp1c2Vk KS4KCkRlYnVnZ2luZyB0aGlzIGlzc3VlIGhhcyBhbHNvIHBvaW50ZWQgb3V0 IHRoYXQgdGhlIGRlYnVnIGxvZyBvdXRwdXQgaXMKcHJldHR5IHVnbHkgdG8g bG9vayBhdCAtIGNvbnNvbGlkYXRlIHRoZSBvdXRwdXQsIGFuZCBhZGQgb25l IGV4dHJhCml0ZW0gZm9yIHRoZSBJVkhEIHNwZWNpYWwgZW50cmllcywgc28g dGhhdCBmdXR1cmUgaXNzdWVzIGFyZSBlYXNpZXIKdG8gYW5hbHl6ZS4KClNp Z25lZC1vZmYtYnk6IEphbiBCZXVsaWNoIDxqYmV1bGljaEBzdXNlLmNvbT4K VGVzdGVkLWJ5OiBTYW5kZXIgRWlrZWxlbmJvb20gPGxpbnV4QGVpa2VsZW5i b29tLml0PgoKLS0tIGEveGVuL2FyY2gveDg2L2lycS5jCisrKyBiL3hlbi9h cmNoL3g4Ni9pcnEuYwpAQCAtMTk0Myw5ICsxOTQzLDYgQEAgaW50IG1hcF9k b21haW5fcGlycSgKICAgICAgICAgc3Bpbl9sb2NrX2lycXNhdmUoJmRlc2Mt PmxvY2ssIGZsYWdzKTsKICAgICAgICAgc2V0X2RvbWFpbl9pcnFfcGlycShk LCBpcnEsIGluZm8pOwogICAgICAgICBzcGluX3VubG9ja19pcnFyZXN0b3Jl KCZkZXNjLT5sb2NrLCBmbGFncyk7Ci0KLSAgICAgICAgaWYgKCBvcHRfaXJx X3ZlY3Rvcl9tYXAgPT0gT1BUX0lSUV9WRUNUT1JfTUFQX1BFUkRFViApCi0g ICAgICAgICAgICBwcmludGsoWEVOTE9HX0lORk8gIlBlci1kZXZpY2UgdmVj dG9yIG1hcHMgZm9yIEdTSXMgbm90IGltcGxlbWVudGVkIHlldC5cbiIpOwog ICAgIH0KIAogZG9uZToKLS0tIGEveGVuL2RyaXZlcnMvYWNwaS90YWJsZXMu YworKysgYi94ZW4vZHJpdmVycy9hY3BpL3RhYmxlcy5jCkBAIC0yNjUsNyAr MjY1LDcgQEAgYWNwaV90YWJsZV9wYXJzZV9tYWR0KGVudW0gYWNwaV9tYWR0 X3R5cAogICogQGhhbmRsZXI6IGhhbmRsZXIgdG8gcnVuCiAgKgogICogU2Nh biB0aGUgQUNQSSBTeXN0ZW0gRGVzY3JpcHRvciBUYWJsZSAoU1REKSBmb3Ig YSB0YWJsZSBtYXRjaGluZyBAaWQsCi0gKiBydW4gQGhhbmRsZXIgb24gaXQu ICBSZXR1cm4gMCBpZiB0YWJsZSBmb3VuZCwgcmV0dXJuIG9uIGlmIG5vdC4K KyAqIHJ1biBAaGFuZGxlciBvbiBpdC4KICAqLwogaW50IF9faW5pdCBhY3Bp X3RhYmxlX3BhcnNlKGNoYXIgKmlkLCBhY3BpX3RhYmxlX2hhbmRsZXIgaGFu ZGxlcikKIHsKQEAgLTI4MCw4ICsyODAsNyBAQCBpbnQgX19pbml0IGFjcGlf dGFibGVfcGFyc2UoY2hhciAqaWQsIGFjCiAJCWFjcGlfZ2V0X3RhYmxlKGlk LCAwLCAmdGFibGUpOwogCiAJaWYgKHRhYmxlKSB7Ci0JCWhhbmRsZXIodGFi bGUpOwotCQlyZXR1cm4gMDsKKwkJcmV0dXJuIGhhbmRsZXIodGFibGUpOwog CX0gZWxzZQogCQlyZXR1cm4gMTsKIH0KLS0tIGEveGVuL2RyaXZlcnMvcGFz c3Rocm91Z2gvYW1kL2lvbW11X2FjcGkuYworKysgYi94ZW4vZHJpdmVycy9w YXNzdGhyb3VnaC9hbWQvaW9tbXVfYWNwaS5jCkBAIC0yMiw2ICsyMiw3IEBA CiAjaW5jbHVkZSA8eGVuL2Vycm5vLmg+CiAjaW5jbHVkZSA8eGVuL2FjcGku aD4KICNpbmNsdWRlIDxhc20vYXBpY2RlZi5oPgorI2luY2x1ZGUgPGFzbS9p b19hcGljLmg+CiAjaW5jbHVkZSA8YXNtL2FtZC1pb21tdS5oPgogI2luY2x1 ZGUgPGFzbS9odm0vc3ZtL2FtZC1pb21tdS1wcm90by5oPgogCkBAIC02Mzcs NiArNjM4LDcgQEAgc3RhdGljIHUxNiBfX2luaXQgcGFyc2VfaXZoZF9kZXZp Y2Vfc3BlYwogICAgIHUxNiBoZWFkZXJfbGVuZ3RoLCB1MTYgYmxvY2tfbGVu Z3RoLCBzdHJ1Y3QgYW1kX2lvbW11ICppb21tdSkKIHsKICAgICB1MTYgZGV2 X2xlbmd0aCwgYmRmOworICAgIGludCBhcGljOwogCiAgICAgZGV2X2xlbmd0 aCA9IHNpemVvZigqc3BlY2lhbCk7CiAgICAgaWYgKCBoZWFkZXJfbGVuZ3Ro IDwgKGJsb2NrX2xlbmd0aCArIGRldl9sZW5ndGgpICkKQEAgLTY1Nyw5ICs2 NTksNTMgQEAgc3RhdGljIHUxNiBfX2luaXQgcGFyc2VfaXZoZF9kZXZpY2Vf c3BlYwogICAgIHN3aXRjaCAoIHNwZWNpYWwtPnZhcmlldHkgKQogICAgIHsK ICAgICBjYXNlIEFDUElfSVZIRF9JT0FQSUM6Ci0gICAgLyogc2V0IGRldmlj ZSBpZCBvZiBpb2FwaWMgKi8KLSAgICAgICAgaW9hcGljX3NiZGZbc3BlY2lh bC0+aGFuZGxlXS5iZGYgPSBiZGY7Ci0gICAgICAgIGlvYXBpY19zYmRmW3Nw ZWNpYWwtPmhhbmRsZV0uc2VnID0gc2VnOworICAgICAgICAvKgorICAgICAg ICAgKiBTb21lIEJJT1NlcyBoYXZlIElPQVBJQyBicm9rZW4gZW50cmllcyBz byB3ZSBjaGVjayBmb3IgSVZSUworICAgICAgICAgKiBjb25zaXN0ZW5jeSBo ZXJlIC0tLSB3aGV0aGVyIGVudHJ5J3MgSU9BUElDIElEIGlzIHZhbGlkIGFu ZAorICAgICAgICAgKiB3aGV0aGVyIHRoZXJlIGFyZSBjb25mbGljdGluZy9k dXBsaWNhdGVkIGVudHJpZXMuCisgICAgICAgICAqLworICAgICAgICBmb3Ig KCBhcGljID0gMDsgYXBpYyA8IG5yX2lvYXBpY3M7IGFwaWMrKyApCisgICAg ICAgIHsKKyAgICAgICAgICAgIGlmICggSU9fQVBJQ19JRChhcGljKSAhPSBz cGVjaWFsLT5oYW5kbGUgKQorICAgICAgICAgICAgICAgIGNvbnRpbnVlOwor CisgICAgICAgICAgICBpZiAoIGlvYXBpY19zYmRmW3NwZWNpYWwtPmhhbmRs ZV0ucGluX3NldHVwICkKKyAgICAgICAgICAgIHsKKyAgICAgICAgICAgICAg ICBpZiAoIGlvYXBpY19zYmRmW3NwZWNpYWwtPmhhbmRsZV0uYmRmID09IGJk ZiAmJgorICAgICAgICAgICAgICAgICAgICAgaW9hcGljX3NiZGZbc3BlY2lh bC0+aGFuZGxlXS5zZWcgPT0gc2VnICkKKyAgICAgICAgICAgICAgICAgICAg QU1EX0lPTU1VX0RFQlVHKCJJVkhEIFdhcm5pbmc6IER1cGxpY2F0ZSBJTy1B UElDICUjeCBlbnRyaWVzXG4iLAorICAgICAgICAgICAgICAgICAgICAgICAg ICAgICAgICAgICAgc3BlY2lhbC0+aGFuZGxlKTsKKyAgICAgICAgICAgICAg ICBlbHNlCisgICAgICAgICAgICAgICAgeworICAgICAgICAgICAgICAgICAg ICBwcmludGsoWEVOTE9HX0VSUiAiSVZIRCBFcnJvcjogQ29uZmxpY3Rpbmcg SU8tQVBJQyAlI3ggZW50cmllc1xuIiwKKyAgICAgICAgICAgICAgICAgICAg ICAgICAgIHNwZWNpYWwtPmhhbmRsZSk7CisgICAgICAgICAgICAgICAgICAg IGlmICggYW1kX2lvbW11X3BlcmRldl9pbnRyZW1hcCApCisgICAgICAgICAg ICAgICAgICAgICAgICByZXR1cm4gMDsKKyAgICAgICAgICAgICAgICB9Cisg ICAgICAgICAgICB9CisgICAgICAgICAgICBlbHNlCisgICAgICAgICAgICB7 CisgICAgICAgICAgICAgICAgLyogc2V0IGRldmljZSBpZCBvZiBpb2FwaWMg Ki8KKyAgICAgICAgICAgICAgICBpb2FwaWNfc2JkZltzcGVjaWFsLT5oYW5k bGVdLmJkZiA9IGJkZjsKKyAgICAgICAgICAgICAgICBpb2FwaWNfc2JkZltz cGVjaWFsLT5oYW5kbGVdLnNlZyA9IHNlZzsKKworICAgICAgICAgICAgICAg IGlvYXBpY19zYmRmW3NwZWNpYWwtPmhhbmRsZV0ucGluX3NldHVwID0geHph bGxvY19hcnJheSgKKyAgICAgICAgICAgICAgICAgICAgdW5zaWduZWQgbG9u ZywgQklUU19UT19MT05HUyhucl9pb2FwaWNfZW50cmllc1thcGljXSkpOwor ICAgICAgICAgICAgICAgIGlmICggbnJfaW9hcGljX2VudHJpZXNbYXBpY10g JiYKKyAgICAgICAgICAgICAgICAgICAgICFpb2FwaWNfc2JkZltJT19BUElD X0lEKGFwaWMpXS5waW5fc2V0dXAgKQorICAgICAgICAgICAgICAgIHsKKyAg ICAgICAgICAgICAgICAgICAgcHJpbnRrKFhFTkxPR19FUlIgIklWSEQgRXJy b3I6IE91dCBvZiBtZW1vcnlcbiIpOworICAgICAgICAgICAgICAgICAgICBy ZXR1cm4gMDsKKyAgICAgICAgICAgICAgICB9CisgICAgICAgICAgICB9Cisg ICAgICAgICAgICBicmVhazsKKyAgICAgICAgfQorICAgICAgICBpZiAoIGFw aWMgPT0gbnJfaW9hcGljcyApCisgICAgICAgIHsKKyAgICAgICAgICAgIHBy aW50ayhYRU5MT0dfRVJSICJJVkhEIEVycm9yOiBJbnZhbGlkIElPLUFQSUMg JSN4XG4iLAorICAgICAgICAgICAgICAgICAgIHNwZWNpYWwtPmhhbmRsZSk7 CisgICAgICAgICAgICByZXR1cm4gMDsKKyAgICAgICAgfQogICAgICAgICBi cmVhazsKICAgICBjYXNlIEFDUElfSVZIRF9IUEVUOgogICAgICAgICAvKiBz ZXQgZGV2aWNlIGlkIG9mIGhwZXQgKi8KQEAgLTg0NCw2ICs4OTAsNyBAQCBz dGF0aWMgaW50IF9faW5pdCBwYXJzZV9pdnJzX3RhYmxlKHN0cnVjCiB7CiAg ICAgY29uc3Qgc3RydWN0IGFjcGlfaXZyc19oZWFkZXIgKml2cnNfYmxvY2s7 CiAgICAgdW5zaWduZWQgbG9uZyBsZW5ndGg7CisgICAgdW5zaWduZWQgaW50 IGFwaWM7CiAgICAgaW50IGVycm9yID0gMDsKIAogICAgIEJVR19PTighdGFi bGUpOwpAQCAtODc2LDYgKzkyMywyOSBAQCBzdGF0aWMgaW50IF9faW5pdCBw YXJzZV9pdnJzX3RhYmxlKHN0cnVjCiAgICAgICAgIGxlbmd0aCArPSBpdnJz X2Jsb2NrLT5sZW5ndGg7CiAgICAgfQogCisgICAgLyogRWFjaCBJTy1BUElD IG11c3QgaGF2ZSBiZWVuIG1lbnRpb25lZCBpbiB0aGUgdGFibGUuICovCisg ICAgZm9yICggYXBpYyA9IDA7ICFlcnJvciAmJiBhcGljIDwgbnJfaW9hcGlj czsgKythcGljICkKKyAgICB7CisgICAgICAgIGlmICggIW5yX2lvYXBpY19l bnRyaWVzW2FwaWNdIHx8CisgICAgICAgICAgICAgaW9hcGljX3NiZGZbSU9f QVBJQ19JRChhcGljKV0ucGluX3NldHVwICkKKyAgICAgICAgICAgIGNvbnRp bnVlOworCisgICAgICAgIHByaW50ayhYRU5MT0dfRVJSICJJVkhEIEVycm9y OiBubyBpbmZvcm1hdGlvbiBmb3IgSU8tQVBJQyAlI3hcbiIsCisgICAgICAg ICAgICAgICBJT19BUElDX0lEKGFwaWMpKTsKKyAgICAgICAgaWYgKCBhbWRf aW9tbXVfcGVyZGV2X2ludHJlbWFwICkKKyAgICAgICAgICAgIGVycm9yID0g LUVOWElPOworICAgICAgICBlbHNlCisgICAgICAgIHsKKyAgICAgICAgICAg IGlvYXBpY19zYmRmW0lPX0FQSUNfSUQoYXBpYyldLnBpbl9zZXR1cCA9IHh6 YWxsb2NfYXJyYXkoCisgICAgICAgICAgICAgICAgdW5zaWduZWQgbG9uZywg QklUU19UT19MT05HUyhucl9pb2FwaWNfZW50cmllc1thcGljXSkpOworICAg ICAgICAgICAgaWYgKCAhaW9hcGljX3NiZGZbSU9fQVBJQ19JRChhcGljKV0u cGluX3NldHVwICkKKyAgICAgICAgICAgIHsKKyAgICAgICAgICAgICAgICBw cmludGsoWEVOTE9HX0VSUiAiSVZIRCBFcnJvcjogT3V0IG9mIG1lbW9yeVxu Iik7CisgICAgICAgICAgICAgICAgZXJyb3IgPSAtRU5PTUVNOworICAgICAg ICAgICAgfQorICAgICAgICB9CisgICAgfQorCiAgICAgcmV0dXJuIGVycm9y OwogfQogCi0tLSBhL3hlbi9kcml2ZXJzL3Bhc3N0aHJvdWdoL2FtZC9pb21t dV9pbml0LmMKKysrIGIveGVuL2RyaXZlcnMvcGFzc3Rocm91Z2gvYW1kL2lv bW11X2luaXQuYwpAQCAtMTEyMCwxMiArMTEyMCw0NSBAQCBzdGF0aWMgaW50 IF9faW5pdCBhbWRfaW9tbXVfc2V0dXBfZGV2aWNlCiAgICAgcmV0dXJuIDA7 CiB9CiAKKy8qIENoZWNrIHdoZXRoZXIgU1A1MTAwIFNBVEEgQ29tYmluZWQg bW9kZSBpcyBvbiAqLworc3RhdGljIGJvb2xfdCBfX2luaXQgYW1kX3NwNTEw MF9lcnJhdHVtMjgodm9pZCkKK3sKKyAgICB1MzIgYnVzLCBpZDsKKyAgICB1 MTYgdmVuZG9yX2lkLCBkZXZfaWQ7CisgICAgdTggYnl0ZTsKKworICAgIGZv ciAoYnVzID0gMDsgYnVzIDwgMjU2OyBidXMrKykKKyAgICB7CisgICAgICAg IGlkID0gcGNpX2NvbmZfcmVhZDMyKDAsIGJ1cywgMHgxNCwgMCwgUENJX1ZF TkRPUl9JRCk7CisKKyAgICAgICAgdmVuZG9yX2lkID0gaWQgJiAweGZmZmY7 CisgICAgICAgIGRldl9pZCA9IChpZCA+PiAxNikgJiAweGZmZmY7CisKKyAg ICAgICAgLyogU1A1MTAwIFNNQnVzIG1vZHVsZSBzZXRzIENvbWJpbmVkIG1v ZGUgb24gKi8KKyAgICAgICAgaWYgKHZlbmRvcl9pZCAhPSAweDEwMDIgfHwg ZGV2X2lkICE9IDB4NDM4NSkKKyAgICAgICAgICAgIGNvbnRpbnVlOworCisg ICAgICAgIGJ5dGUgPSBwY2lfY29uZl9yZWFkOCgwLCBidXMsIDB4MTQsIDAs IDB4YWQpOworICAgICAgICBpZiAoIChieXRlID4+IDMpICYgMSApCisgICAg ICAgIHsKKyAgICAgICAgICAgIHByaW50ayhYRU5MT0dfV0FSTklORyAiQU1E LVZpOiBTUDUxMDAgZXJyYXR1bSAyOCBkZXRlY3RlZCwgZGlzYWJsaW5nIElP TU1VLlxuIgorICAgICAgICAgICAgICAgICAgICJJZiBwb3NzaWJsZSwgZGlz YWJsZSBTQVRBIENvbWJpbmVkIG1vZGUgaW4gQklPUyBvciBjb250YWN0IHlv dXIgdmVuZG9yIGZvciBCSU9TIHVwZGF0ZS5cbiIpOworICAgICAgICAgICAg cmV0dXJuIDE7CisgICAgICAgIH0KKyAgICB9CisKKyAgICByZXR1cm4gMDsK K30KKwogaW50IF9faW5pdCBhbWRfaW9tbXVfaW5pdCh2b2lkKQogewogICAg IHN0cnVjdCBhbWRfaW9tbXUgKmlvbW11OwogCiAgICAgQlVHX09OKCAhaW9t bXVfZm91bmQoKSApOwogCisgICAgaWYgKCBhbWRfaW9tbXVfcGVyZGV2X2lu dHJlbWFwICYmIGFtZF9zcDUxMDBfZXJyYXR1bTI4KCkgKQorICAgICAgICBn b3RvIGVycm9yX291dDsKKwogICAgIGl2cnNfYmRmX2VudHJpZXMgPSBhbWRf aW9tbXVfZ2V0X2l2cnNfZGV2X2VudHJpZXMoKTsKIAogICAgIGlmICggIWl2 cnNfYmRmX2VudHJpZXMgKQotLS0gYS94ZW4vZHJpdmVycy9wYXNzdGhyb3Vn aC9hbWQvaW9tbXVfaW50ci5jCisrKyBiL3hlbi9kcml2ZXJzL3Bhc3N0aHJv dWdoL2FtZC9pb21tdV9pbnRyLmMKQEAgLTEwMCwxMiArMTAwLDEyIEBAIHN0 YXRpYyB2b2lkIHVwZGF0ZV9pbnRyZW1hcF9lbnRyeSh1MzIqIGUKIHN0YXRp YyB2b2lkIHVwZGF0ZV9pbnRyZW1hcF9lbnRyeV9mcm9tX2lvYXBpYygKICAg ICBpbnQgYmRmLAogICAgIHN0cnVjdCBhbWRfaW9tbXUgKmlvbW11LAotICAg IHN0cnVjdCBJT19BUElDX3JvdXRlX2VudHJ5ICppb2FwaWNfcnRlKQorICAg IGNvbnN0IHN0cnVjdCBJT19BUElDX3JvdXRlX2VudHJ5ICpydGUsCisgICAg Y29uc3Qgc3RydWN0IElPX0FQSUNfcm91dGVfZW50cnkgKm9sZF9ydGUpCiB7 CiAgICAgdW5zaWduZWQgbG9uZyBmbGFnczsKICAgICB1MzIqIGVudHJ5Owog ICAgIHU4IGRlbGl2ZXJ5X21vZGUsIGRlc3QsIHZlY3RvciwgZGVzdF9tb2Rl OwotICAgIHN0cnVjdCBJT19BUElDX3JvdXRlX2VudHJ5ICpydGUgPSBpb2Fw aWNfcnRlOwogICAgIGludCByZXFfaWQ7CiAgICAgc3BpbmxvY2tfdCAqbG9j azsKICAgICBpbnQgb2Zmc2V0OwpAQCAtMTIxLDYgKzEyMSwxNCBAQCBzdGF0 aWMgdm9pZCB1cGRhdGVfaW50cmVtYXBfZW50cnlfZnJvbV9pCiAgICAgc3Bp bl9sb2NrX2lycXNhdmUobG9jaywgZmxhZ3MpOwogCiAgICAgb2Zmc2V0ID0g Z2V0X2ludHJlbWFwX29mZnNldCh2ZWN0b3IsIGRlbGl2ZXJ5X21vZGUpOwor ICAgIGlmICggb2xkX3J0ZSApCisgICAgeworICAgICAgICBpbnQgb2xkX29m ZnNldCA9IGdldF9pbnRyZW1hcF9vZmZzZXQob2xkX3J0ZS0+dmVjdG9yLAor ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg b2xkX3J0ZS0+ZGVsaXZlcnlfbW9kZSk7CisKKyAgICAgICAgaWYgKCBvZmZz ZXQgIT0gb2xkX29mZnNldCApCisgICAgICAgICAgICBmcmVlX2ludHJlbWFw X2VudHJ5KGlvbW11LT5zZWcsIGJkZiwgb2xkX29mZnNldCk7CisgICAgfQog ICAgIGVudHJ5ID0gKHUzMiopZ2V0X2ludHJlbWFwX2VudHJ5KGlvbW11LT5z ZWcsIHJlcV9pZCwgb2Zmc2V0KTsKICAgICB1cGRhdGVfaW50cmVtYXBfZW50 cnkoZW50cnksIHZlY3RvciwgZGVsaXZlcnlfbW9kZSwgZGVzdF9tb2RlLCBk ZXN0KTsKIApAQCAtMTg5LDYgKzE5Nyw3IEBAIGludCBfX2luaXQgYW1kX2lv bW11X3NldHVwX2lvYXBpY19yZW1hcHAKICAgICAgICAgICAgICAgICBhbWRf aW9tbXVfZmx1c2hfaW50cmVtYXAoaW9tbXUsIHJlcV9pZCk7CiAgICAgICAg ICAgICAgICAgc3Bpbl91bmxvY2tfaXJxcmVzdG9yZSgmaW9tbXUtPmxvY2ss IGZsYWdzKTsKICAgICAgICAgICAgIH0KKyAgICAgICAgICAgIHNldF9iaXQo cGluLCBpb2FwaWNfc2JkZltJT19BUElDX0lEKGFwaWMpXS5waW5fc2V0dXAp OwogICAgICAgICB9CiAgICAgfQogICAgIHJldHVybiAwOwpAQCAtMjAwLDYg KzIwOSw3IEBAIHZvaWQgYW1kX2lvbW11X2lvYXBpY191cGRhdGVfaXJlKAog ICAgIHN0cnVjdCBJT19BUElDX3JvdXRlX2VudHJ5IG9sZF9ydGUgPSB7IDAg fTsKICAgICBzdHJ1Y3QgSU9fQVBJQ19yb3V0ZV9lbnRyeSBuZXdfcnRlID0g eyAwIH07CiAgICAgdW5zaWduZWQgaW50IHJ0ZV9sbyA9IChyZWcgJiAxKSA/ IHJlZyAtIDEgOiByZWc7CisgICAgdW5zaWduZWQgaW50IHBpbiA9IChyZWcg LSAweDEwKSAvIDI7CiAgICAgaW50IHNhdmVkX21hc2ssIHNlZywgYmRmOwog ICAgIHN0cnVjdCBhbWRfaW9tbXUgKmlvbW11OwogCkBAIC0yMzcsNiArMjQ3 LDE0IEBAIHZvaWQgYW1kX2lvbW11X2lvYXBpY191cGRhdGVfaXJlKAogICAg ICAgICAqKCgodTMyICopJm5ld19ydGUpICsgMSkgPSB2YWx1ZTsKICAgICB9 CiAKKyAgICBpZiAoIG5ld19ydGUubWFzayAmJgorICAgICAgICAgIXRlc3Rf Yml0KHBpbiwgaW9hcGljX3NiZGZbSU9fQVBJQ19JRChhcGljKV0ucGluX3Nl dHVwKSApCisgICAgeworICAgICAgICBBU1NFUlQoc2F2ZWRfbWFzayk7Cisg ICAgICAgIF9faW9fYXBpY193cml0ZShhcGljLCByZWcsIHZhbHVlKTsKKyAg ICAgICAgcmV0dXJuOworICAgIH0KKwogICAgIC8qIG1hc2sgdGhlIGludGVy cnVwdCB3aGlsZSB3ZSBjaGFuZ2UgdGhlIGludHJlbWFwIHRhYmxlICovCiAg ICAgaWYgKCAhc2F2ZWRfbWFzayApCiAgICAgewpAQCAtMjQ1LDcgKzI2Mywx MSBAQCB2b2lkIGFtZF9pb21tdV9pb2FwaWNfdXBkYXRlX2lyZSgKICAgICB9 CiAKICAgICAvKiBVcGRhdGUgaW50ZXJydXB0IHJlbWFwcGluZyBlbnRyeSAq LwotICAgIHVwZGF0ZV9pbnRyZW1hcF9lbnRyeV9mcm9tX2lvYXBpYyhiZGYs IGlvbW11LCAmbmV3X3J0ZSk7CisgICAgdXBkYXRlX2ludHJlbWFwX2VudHJ5 X2Zyb21faW9hcGljKAorICAgICAgICBiZGYsIGlvbW11LCAmbmV3X3J0ZSwK KyAgICAgICAgdGVzdF9hbmRfc2V0X2JpdChwaW4sCisgICAgICAgICAgICAg ICAgICAgICAgICAgaW9hcGljX3NiZGZbSU9fQVBJQ19JRChhcGljKV0ucGlu X3NldHVwKSA/ICZvbGRfcnRlCisgICAgICAgICAgICAgICAgICAgICAgICAg ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICA6IE5V TEwpOwogCiAgICAgLyogRm9yd2FyZCB3cml0ZSBhY2Nlc3MgdG8gSU8tQVBJ QyBSVEUgKi8KICAgICBfX2lvX2FwaWNfd3JpdGUoYXBpYywgcmVnLCB2YWx1 ZSk7CkBAIC0zNTYsNiArMzc4LDEyIEBAIHZvaWQgYW1kX2lvbW11X21zaV9t c2dfdXBkYXRlX2lyZSgKICAgICAgICAgcmV0dXJuOwogICAgIH0KIAorICAg IGlmICggbXNpX2Rlc2MtPnJlbWFwX2luZGV4ID49IDAgKQorICAgICAgICB1 cGRhdGVfaW50cmVtYXBfZW50cnlfZnJvbV9tc2lfbXNnKGlvbW11LCBiZGYs IG1zaV9kZXNjLCBOVUxMKTsKKworICAgIGlmICggIW1zZyApCisgICAgICAg IHJldHVybjsKKwogICAgIHVwZGF0ZV9pbnRyZW1hcF9lbnRyeV9mcm9tX21z aV9tc2coaW9tbXUsIGJkZiwgbXNpX2Rlc2MsIG1zZyk7CiB9CiAKLS0tIGEv eGVuL2RyaXZlcnMvcGFzc3Rocm91Z2gvYW1kL3BjaV9hbWRfaW9tbXUuYwor KysgYi94ZW4vZHJpdmVycy9wYXNzdGhyb3VnaC9hbWQvcGNpX2FtZF9pb21t dS5jCkBAIC0yMDgsNiArMjA4LDggQEAgaW50IF9faW5pdCBhbWRfaW92X2Rl dGVjdCh2b2lkKQogICAgIHsKICAgICAgICAgcHJpbnRrKCJBTUQtVmk6IE5v dCBvdmVycmlkaW5nIGlycV92ZWN0b3JfbWFwIHNldHRpbmdcbiIpOwogICAg IH0KKyAgICBpZiAoICFhbWRfaW9tbXVfcGVyZGV2X2ludHJlbWFwICkKKyAg ICAgICAgcHJpbnRrKFhFTkxPR19XQVJOSU5HICJBTUQtVmk6IFVzaW5nIGds b2JhbCBpbnRlcnJ1cHQgcmVtYXAgdGFibGUgaXMgbm90IHJlY29tbWVuZGVk IChzZWUgWFNBLTM2KSFcbiIpOwogICAgIHJldHVybiBzY2FuX3BjaV9kZXZp Y2VzKCk7CiB9CiAKLS0tIGEveGVuL2RyaXZlcnMvcGFzc3Rocm91Z2gvaW9t bXUuYworKysgYi94ZW4vZHJpdmVycy9wYXNzdGhyb3VnaC9pb21tdS5jCkBA IC01Myw3ICs1Myw3IEBAIGJvb2xfdCBfX3JlYWRfbW9zdGx5IGlvbW11X3Fp bnZhbCA9IDE7CiBib29sX3QgX19yZWFkX21vc3RseSBpb21tdV9pbnRyZW1h cCA9IDE7CiBib29sX3QgX19yZWFkX21vc3RseSBpb21tdV9oYXBfcHRfc2hh cmUgPSAxOwogYm9vbF90IF9fcmVhZF9tb3N0bHkgaW9tbXVfZGVidWc7Ci1i b29sX3QgX19yZWFkX21vc3RseSBhbWRfaW9tbXVfcGVyZGV2X2ludHJlbWFw OworYm9vbF90IF9fcmVhZF9tb3N0bHkgYW1kX2lvbW11X3BlcmRldl9pbnRy ZW1hcCA9IDE7CiAKIERFRklORV9QRVJfQ1BVKGJvb2xfdCwgaW9tbXVfZG9u dF9mbHVzaF9pb3RsYik7CiAKLS0tIGEveGVuL2luY2x1ZGUvYXNtLXg4Ni9o dm0vc3ZtL2FtZC1pb21tdS1wcm90by5oCisrKyBiL3hlbi9pbmNsdWRlL2Fz bS14ODYvaHZtL3N2bS9hbWQtaW9tbXUtcHJvdG8uaApAQCAtMTAxLDYgKzEw MSw3IEBAIGludCBhbWRfc2V0dXBfaHBldF9tc2koc3RydWN0IG1zaV9kZXNj ICoKIAogZXh0ZXJuIHN0cnVjdCBpb2FwaWNfc2JkZiB7CiAgICAgdTE2IGJk Ziwgc2VnOworICAgIHVuc2lnbmVkIGxvbmcgKnBpbl9zZXR1cDsKIH0gaW9h cGljX3NiZGZbTUFYX0lPX0FQSUNTXTsKIGV4dGVybiB2b2lkICpzaGFyZWRf aW50cmVtYXBfdGFibGU7CiAK --=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 Feb 21 14:24:54 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 21 Feb 2013 14:24: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 1U8X3u-000436-TM; Thu, 21 Feb 2013 14:23:50 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U8X3s-00042E-6w; Thu, 21 Feb 2013 14:23:48 +0000 Received: from [85.158.139.211:17022] by server-3.bemta-5.messagelabs.com id 9E/AD-07037-3FD26215; Thu, 21 Feb 2013 14:23:47 +0000 X-Env-Sender: iwj@xenbits.xen.org X-Msg-Ref: server-14.tower-206.messagelabs.com!1361456621!18549606!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.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 30770 invoked from network); 21 Feb 2013 14:23:42 -0000 Received: from mail.xen.org (HELO mail.xen.org) (50.57.168.107) by server-14.tower-206.messagelabs.com with AES256-SHA encrypted SMTP; 21 Feb 2013 14:23:42 -0000 Received: from xenbits.xen.org ([50.57.170.242]) by mail.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U8X3c-000207-Ah; Thu, 21 Feb 2013 14:23:32 +0000 Received: from iwj by xenbits.xen.org with local (Exim 4.72) (envelope-from ) id 1U8X3b-0007ni-Cw; Thu, 21 Feb 2013 14:23:31 +0000 Date: Thu, 21 Feb 2013 14:23:31 +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 36 (CVE-2013-0153) - interrupt remap entries shared and old ones not cleared on AMD IOMMUs X-BeenThere: xen-users@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-2013-0153 / XSA-36 version 4 interrupt remap entries shared and old ones not cleared on AMD IOMMUs UPDATES IN VERSION 4 ==================== Updated patches, to deal with a boot time crash resulting from the earlier changes on systems with firmware broken in a way not previously accounted for. ISSUE DESCRIPTION ================= To avoid an erratum in early hardware, the Xen AMD IOMMU code by default chooses to use a single interrupt remapping table for the whole system. This sharing implies that any guest with a passed through PCI device that is bus mastering capable can inject interrupts into other guests, including domain 0. Furthermore, regardless of whether a shared interrupt remapping table is in use, old entries are not always cleared, providing opportunities (which accumulate over time) for guests to inject interrupts into other guests, again including domain 0. In a typical Xen system many devices are owned by domain 0 or driver domains, leaving them vulnerable to such an attack. Such a DoS is likely to have an impact on other guests running in the system. IMPACT ====== A malicious domain which is given access to a physical PCI device can mount a denial of service attack affecting the whole system. VULNERABLE SYSTEMS ================== Xen versions 3.3 onwards are vulnerable. Earlier Xen versions do not implement interrupt remapping, and hence do not support secure AMD-Vi PCI passthrough in any case. Only systems using AMD-Vi for PCI passthrough are vulnerable. Any domain which is given access to a PCI device can take advantage of this vulnerability. MITIGATION ========== This issue can be avoided by not assigning PCI devices to untrusted guests. In Xen versions 4.1.3 and above the sharing of the interrupt remapping table (and hence the more severe part of this problem) can be avoided by passing "iommu=amd-iommu-perdev-intremap" as a command line option to the hypervisor. This option is not fully functional on earlier hypervisors. RESOLUTION ========== Applying the appropriate attached patch resolves this issue. Note that on certain systems (SP5100 chipsets with erratum 28 present, or such with broken IVRS ACPI table) these patches will result in the IOMMU not being enabled anymore. This should be dealt with by a BIOS update, if available. Alternatively the check can be overridden by specifying "iommu=no-amd-iommu-perdev-intremap" on the Xen command line ("iommu=amd-iommu-global-intremap" on 4.1.x), at the price of re-opening the security hole addressed by these patches. xsa36-unstable.patch Xen unstable xsa36-4.2.patch Xen 4.2.x xsa36-4.1.patch Xen 4.1.x $ sha256sum xsa36*.patch 4bdc0f1f94f82c6bc6c777971f22ef915215b72b98b29f9064e4df65c0efc6f4 xsa36-4.1.patch dd32ecaa84edbf6d11241045f40ba53ec4a3bc6c24f719bc21204067c4eb8964 xsa36-4.2.patch 7c0b3a1b332a24a830c7a436b065943f60c54cd5b7e746c440e2992a7b5cfe41 xsa36-unstable.patch $ Incremental patches on top of what was provided in version 3 can also be taken from the respective mercurial trees: http://xenbits.xen.org/hg/xen-unstable.hg/rev/e68f14b9e739 http://xenbits.xen.org/hg/staging/xen-4.2-testing.hg/rev/6a03b38b9cd6 http://xenbits.xen.org/hg/staging/xen-4.1-testing.hg/rev/4d522221fa77 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) iQEcBAEBAgAGBQJRJf98AAoJEIP+FMlX6CvZ5ocH/jNY92kLw7BOencxa9R3TGTn 20O0+j1id+xi2vjVVF2xm2SJ7g/6Egx5WURUfy2cu+I8GdDHKmRrp3Vkazltzcnd 6AlI5aiPC2H1rFkU0FpneRk3mrluABLZO8Q5YcSJs24hwqded0W+SivH63aInki/ PsDGoBu8HUjYMWjXyqCJVJIGToLS9ApaQ8+iTylWb1ZocRm2VcPS8yJI7z82kj3A zRNADG36oAFawSJsE9z3ykVoYv9UYckOaWkaXh7jZPHAvIjvP2wLb9gmMkMXbIOP ICpJJFf0w7oW6KTY3g9n8CxUMBMoUw/9Fv+CQBzOf0ZZY/vIE8q65A0NhCcWixo= =vmpB -----END PGP SIGNATURE----- --=separator Content-Type: application/octet-stream; name="xsa36-4.1.patch" Content-Disposition: attachment; filename="xsa36-4.1.patch" Content-Transfer-Encoding: base64 QUNQSTogYWNwaV90YWJsZV9wYXJzZSgpIHNob3VsZCByZXR1cm4gaGFuZGxl cidzIGVycm9yIGNvZGUKCkN1cnJlbnRseSwgdGhlIGVycm9yIGNvZGUgcmV0 dXJuZWQgYnkgYWNwaV90YWJsZV9wYXJzZSgpJ3MgaGFuZGxlcgppcyBpZ25v cmVkLiBUaGlzIHBhdGNoIHdpbGwgcHJvcGFnYXRlIGhhbmRsZXIncyByZXR1 cm4gdmFsdWUgdG8KYWNwaV90YWJsZV9wYXJzZSgpJ3MgY2FsbGVyLgoKQU1E LElPTU1VOiBDbGVhbiB1cCBvbGQgZW50cmllcyBpbiByZW1hcHBpbmcgdGFi bGVzIHdoZW4gY3JlYXRpbmcgbmV3CmludGVycnVwdCBtYXBwaW5nLgoKV2hl biBjaGFuZ2luZyB0aGUgYWZmaW5pdHkgb2YgYW4gSVJRIGFzc29jaWF0ZWQg d2l0aCBhIHBhc3NlZAp0aHJvdWdoIFBDSSBkZXZpY2UsIGNsZWFyIHByZXZp b3VzIG1hcHBpbmcuCgpJbiBhZGRpdGlvbiwgYmVjYXVzZSBzb21lIEJJT1Nl cyBtYXkgaW5jb3JyZWN0bHkgcHJvZ3JhbSBJVlJTCmVudHJpZXMgZm9yIElP QVBJQyB0cnkgdG8gY2hlY2sgZm9yIGVudHJ5J3MgY29uc2lzdGVuY3kuIFNw ZWNpZmljYWxseSwKaWYgY29uZmxpY3RpbmcgZW50cmllcyBhcmUgZm91bmQg ZGlzYWJsZSBJT01NVSBpZiBwZXItZGV2aWNlCnJlbWFwcGluZyB0YWJsZSBp cyB1c2VkLiBJZiBlbnRyaWVzIHJlZmVyIHRvIGJvZ3VzIElPQVBJQyBJRHMK ZGlzYWJsZSBJT01NVSB1bmNvbmRpdGlvbmFsbHkKCkFNRCxJT01NVTogRGlz YWJsZSBJT01NVSBpZiBTQVRBIENvbWJpbmVkIG1vZGUgaXMgb24KCkFNRCdz IFNQNTEwMCBjaGlwc2V0IGNhbiBiZSBwbGFjZWQgaW50byBTQVRBIENvbWJp bmVkIG1vZGUKdGhhdCBtYXkgY2F1c2UgcHJldmVudCBkb20wIGZyb20gYm9v dGluZyB3aGVuIElPTU1VIGlzCmVuYWJsZWQgYW5kIHBlci1kZXZpY2UgaW50 ZXJydXB0IHJlbWFwcGluZyB0YWJsZSBpcyB1c2VkLgpXaGlsZSBTUDUxMDAg ZXJyYXR1bSAyOCByZXF1aXJlcyBCSU9TZXMgdG8gZGlzYWJsZSB0aGlzIG1v ZGUsCnNvbWUgbWF5IHN0aWxsIHVzZSBpdC4KClRoaXMgcGF0Y2ggY2hlY2tz IHdoZXRoZXIgdGhpcyBtb2RlIGlzIG9uIGFuZCwgaWYgcGVyLWRldmljZQp0 YWJsZSBpcyBpbiB1c2UsIGRpc2FibGVzIElPTU1VLgoKQU1ELElPTU1VOiBN YWtlIHBlci1kZXZpY2UgaW50ZXJydXB0IHJlbWFwcGluZyB0YWJsZSBkZWZh dWx0CgpVc2luZyBnbG9iYWwgaW50ZXJydXB0IHJlbWFwcGluZyB0YWJsZSBt YXkgYmUgaW5zZWN1cmUsIGFzCmRlc2NyaWJlZCBieSBYU0EtMzYuIFRoaXMg cGF0Y2ggbWFrZXMgcGVyLWRldmljZSBtb2RlIGRlZmF1bHQuCgpUaGlzIGlz IFhTQS0zNiAvIENWRS0yMDEzLTAxNTMuCgpTaWduZWQtb2ZmLWJ5OiBKYW4g QmV1bGljaCA8amJldWxpY2hAc3VzZS5jb20+ClNpZ25lZC1vZmYtYnk6IEJv cmlzIE9zdHJvdnNreSA8Ym9yaXMub3N0cm92c2t5QGFtZC5jb20+CgpBTUQg SU9NTVU6IGFsc28gc3BvdCBtaXNzaW5nIElPLUFQSUMgZW50cmllcyBpbiBJ VlJTIHRhYmxlCgpBcGFydCBmcm9tIGRlYWxpbmcgZHVwbGljYXRlIGNvbmZs aWN0aW5nIGVudHJpZXMsIHdlIGFsc28gaGF2ZSB0bwpoYW5kbGUgZmlybXdh cmUgb21pdHRpbmcgSU8tQVBJQyBlbnRyaWVzIGluIElWUlMgYWx0b2dldGhl ci4gTm90IGRvaW5nCnNvIGhhcyByZXN1bHRlZCBpbiBjL3MgMjY1MTc6NjAx MTM5ZTJiMGRiIHRvIGNyYXNoIHN1Y2ggc3lzdGVtcyBkdXJpbmcKYm9vdCAo d2hlcmVhcyB3aXRoIHRoZSBjaGFuZ2UgaGVyZSB0aGUgSU9NTVUgZ2V0cyBk aXNhYmxlZCBqdXN0IGFzIGlzCmJlaW5nIGRvbmUgaW4gdGhlIG90aGVyIGNh c2VzLCBpLmUuIHVubGVzcyBnbG9iYWwgdGFibGVzIGFyZSBiZWluZwp1c2Vk KS4KCkRlYnVnZ2luZyB0aGlzIGlzc3VlIGhhcyBhbHNvIHBvaW50ZWQgb3V0 IHRoYXQgdGhlIGRlYnVnIGxvZyBvdXRwdXQgaXMKcHJldHR5IHVnbHkgdG8g bG9vayBhdCAtIGNvbnNvbGlkYXRlIHRoZSBvdXRwdXQsIGFuZCBhZGQgb25l IGV4dHJhCml0ZW0gZm9yIHRoZSBJVkhEIHNwZWNpYWwgZW50cmllcywgc28g dGhhdCBmdXR1cmUgaXNzdWVzIGFyZSBlYXNpZXIKdG8gYW5hbHl6ZS4KClNp Z25lZC1vZmYtYnk6IEphbiBCZXVsaWNoIDxqYmV1bGljaEBzdXNlLmNvbT4K VGVzdGVkLWJ5OiBTYW5kZXIgRWlrZWxlbmJvb20gPGxpbnV4QGVpa2VsZW5i b29tLml0PgoKLS0tIGEveGVuL2FyY2gveDg2L2lycS5jCisrKyBiL3hlbi9h cmNoL3g4Ni9pcnEuYwpAQCAtMTY3Nyw5ICsxNjc3LDYgQEAgaW50IG1hcF9k b21haW5fcGlycSgKICAgICAgICAgZC0+YXJjaC5waXJxX2lycVtwaXJxXSA9 IGlycTsKICAgICAgICAgZC0+YXJjaC5pcnFfcGlycVtpcnFdID0gcGlycTsK ICAgICAgICAgc3Bpbl91bmxvY2tfaXJxcmVzdG9yZSgmZGVzYy0+bG9jaywg ZmxhZ3MpOwotCi0gICAgICAgIGlmICggb3B0X2lycV92ZWN0b3JfbWFwID09 IE9QVF9JUlFfVkVDVE9SX01BUF9QRVJERVYgKQotICAgICAgICAgICAgcHJp bnRrKFhFTkxPR19JTkZPICJQZXItZGV2aWNlIHZlY3RvciBtYXBzIGZvciBH U0lzIG5vdCBpbXBsZW1lbnRlZCB5ZXQuXG4iKTsKICAgICB9CiAKIGRvbmU6 Ci0tLSBhL3hlbi9kcml2ZXJzL2FjcGkvdGFibGVzLmMKKysrIGIveGVuL2Ry aXZlcnMvYWNwaS90YWJsZXMuYwpAQCAtMjY3LDcgKzI2Nyw3IEBAIGFjcGlf dGFibGVfcGFyc2VfbWFkdChlbnVtIGFjcGlfbWFkdF90eXAKICAqIEBoYW5k bGVyOiBoYW5kbGVyIHRvIHJ1bgogICoKICAqIFNjYW4gdGhlIEFDUEkgU3lz dGVtIERlc2NyaXB0b3IgVGFibGUgKFNURCkgZm9yIGEgdGFibGUgbWF0Y2hp bmcgQGlkLAotICogcnVuIEBoYW5kbGVyIG9uIGl0LiAgUmV0dXJuIDAgaWYg dGFibGUgZm91bmQsIHJldHVybiBvbiBpZiBub3QuCisgKiBydW4gQGhhbmRs ZXIgb24gaXQuCiAgKi8KIGludCBhY3BpX3RhYmxlX3BhcnNlKGNoYXIgKmlk LCBhY3BpX3RhYmxlX2hhbmRsZXIgaGFuZGxlcikKIHsKQEAgLTI4Miw4ICsy ODIsNyBAQCBpbnQgYWNwaV90YWJsZV9wYXJzZShjaGFyICppZCwgYWNwaV90 YWJsCiAJCWFjcGlfZ2V0X3RhYmxlKGlkLCAwLCAmdGFibGUpOwogCiAJaWYg KHRhYmxlKSB7Ci0JCWhhbmRsZXIodGFibGUpOwotCQlyZXR1cm4gMDsKKwkJ cmV0dXJuIGhhbmRsZXIodGFibGUpOwogCX0gZWxzZQogCQlyZXR1cm4gMTsK IH0KLS0tIGEveGVuL2RyaXZlcnMvcGFzc3Rocm91Z2gvYW1kL2lvbW11X2Fj cGkuYworKysgYi94ZW4vZHJpdmVycy9wYXNzdGhyb3VnaC9hbWQvaW9tbXVf YWNwaS5jCkBAIC0yMSw2ICsyMSw3IEBACiAjaW5jbHVkZSA8eGVuL2NvbmZp Zy5oPgogI2luY2x1ZGUgPHhlbi9lcnJuby5oPgogI2luY2x1ZGUgPGFzbS9h cGljZGVmLmg+CisjaW5jbHVkZSA8YXNtL2lvX2FwaWMuaD4KICNpbmNsdWRl IDxhc20vYW1kLWlvbW11Lmg+CiAjaW5jbHVkZSA8YXNtL2h2bS9zdm0vYW1k LWlvbW11LXByb3RvLmg+CiAjaW5jbHVkZSA8YXNtL2h2bS9zdm0vYW1kLWlv bW11LWFjcGkuaD4KQEAgLTI5LDcgKzMwLDYgQEAgZXh0ZXJuIHVuc2lnbmVk IGxvbmcgYW1kX2lvbW11X3BhZ2VfZW50cgogZXh0ZXJuIHVuc2lnbmVkIHNo b3J0IGl2cnNfYmRmX2VudHJpZXM7CiBleHRlcm4gc3RydWN0IGl2cnNfbWFw cGluZ3MgKml2cnNfbWFwcGluZ3M7CiBleHRlcm4gdW5zaWduZWQgc2hvcnQg bGFzdF9iZGY7Ci1leHRlcm4gaW50IGlvYXBpY19iZGZbTUFYX0lPX0FQSUNT XTsKIGV4dGVybiB2b2lkICpzaGFyZWRfaW50cmVtYXBfdGFibGU7CiAKIHN0 YXRpYyB2b2lkIGFkZF9pdnJzX21hcHBpbmdfZW50cnkoCkBAIC02MzYsNiAr NjM2LDcgQEAgc3RhdGljIHUxNiBfX2luaXQgcGFyc2VfaXZoZF9kZXZpY2Vf c3BlYwogICAgIHUxNiBoZWFkZXJfbGVuZ3RoLCB1MTYgYmxvY2tfbGVuZ3Ro LCBzdHJ1Y3QgYW1kX2lvbW11ICppb21tdSkKIHsKICAgICB1MTYgZGV2X2xl bmd0aCwgYmRmOworICAgIGludCBhcGljOwogCiAgICAgZGV2X2xlbmd0aCA9 IHNpemVvZihzdHJ1Y3QgYWNwaV9pdmhkX2RldmljZV9zcGVjaWFsKTsKICAg ICBpZiAoIGhlYWRlcl9sZW5ndGggPCAoYmxvY2tfbGVuZ3RoICsgZGV2X2xl bmd0aCkgKQpAQCAtNjUyLDkgKzY1Myw1OCBAQCBzdGF0aWMgdTE2IF9faW5p dCBwYXJzZV9pdmhkX2RldmljZV9zcGVjCiAgICAgfQogCiAgICAgYWRkX2l2 cnNfbWFwcGluZ19lbnRyeShiZGYsIGJkZiwgaXZoZF9kZXZpY2UtPmhlYWRl ci5mbGFncywgaW9tbXUpOwotICAgIC8qIHNldCBkZXZpY2UgaWQgb2YgaW9h cGljICovCi0gICAgaW9hcGljX2JkZltpdmhkX2RldmljZS0+c3BlY2lhbC5o YW5kbGVdID0gYmRmOwotICAgIHJldHVybiBkZXZfbGVuZ3RoOworCisgICAg aWYgKCBpdmhkX2RldmljZS0+c3BlY2lhbC52YXJpZXR5ICE9IDEgLyogQUNQ SV9JVkhEX0lPQVBJQyAqLyApCisgICAgeworICAgICAgICBpZiAoIGl2aGRf ZGV2aWNlLT5zcGVjaWFsLnZhcmlldHkgIT0gMiAvKiBBQ1BJX0lWSERfSFBF VCAqLyApCisgICAgICAgICAgICBwcmludGsoWEVOTE9HX0VSUiAiVW5yZWNv Z25pemVkIElWSEQgc3BlY2lhbCB2YXJpZXR5ICUjeFxuIiwKKyAgICAgICAg ICAgICAgICAgICBpdmhkX2RldmljZS0+c3BlY2lhbC52YXJpZXR5KTsKKyAg ICAgICAgcmV0dXJuIGRldl9sZW5ndGg7CisgICAgfQorCisgICAgLyoKKyAg ICAgKiBTb21lIEJJT1NlcyBoYXZlIElPQVBJQyBicm9rZW4gZW50cmllcyBz byB3ZSBjaGVjayBmb3IgSVZSUworICAgICAqIGNvbnNpc3RlbmN5IGhlcmUg LS0tIHdoZXRoZXIgZW50cnkncyBJT0FQSUMgSUQgaXMgdmFsaWQgYW5kCisg ICAgICogd2hldGhlciB0aGVyZSBhcmUgY29uZmxpY3RpbmcvZHVwbGljYXRl ZCBlbnRyaWVzLgorICAgICAqLworICAgIGZvciAoIGFwaWMgPSAwOyBhcGlj IDwgbnJfaW9hcGljczsgYXBpYysrICkKKyAgICB7CisgICAgICAgIGlmICgg SU9fQVBJQ19JRChhcGljKSAhPSBpdmhkX2RldmljZS0+c3BlY2lhbC5oYW5k bGUgKQorICAgICAgICAgICAgY29udGludWU7CisKKyAgICAgICAgaWYgKCBp b2FwaWNfYmRmW2l2aGRfZGV2aWNlLT5zcGVjaWFsLmhhbmRsZV0ucGluX3Nl dHVwICkKKyAgICAgICAgeworICAgICAgICAgICAgaWYgKCBpb2FwaWNfYmRm W2l2aGRfZGV2aWNlLT5zcGVjaWFsLmhhbmRsZV0uYmRmID09IGJkZiApCisg ICAgICAgICAgICAgICAgQU1EX0lPTU1VX0RFQlVHKCJJVkhEIFdhcm5pbmc6 IER1cGxpY2F0ZSBJTy1BUElDICUjeCBlbnRyaWVzXG4iLAorICAgICAgICAg ICAgICAgICAgICAgICAgICAgICAgICBpdmhkX2RldmljZS0+c3BlY2lhbC5o YW5kbGUpOworICAgICAgICAgICAgZWxzZQorICAgICAgICAgICAgeworICAg ICAgICAgICAgICAgIHByaW50ayhYRU5MT0dfRVJSICJJVkhEIEVycm9yOiBD b25mbGljdGluZyBJTy1BUElDICUjeCBlbnRyaWVzXG4iLAorICAgICAgICAg ICAgICAgICAgICAgICBpdmhkX2RldmljZS0+c3BlY2lhbC5oYW5kbGUpOwor ICAgICAgICAgICAgICAgIGlmICggYW1kX2lvbW11X3BlcmRldl9pbnRyZW1h cCApCisgICAgICAgICAgICAgICAgICAgIHJldHVybiAwOworICAgICAgICAg ICAgfQorICAgICAgICB9CisgICAgICAgIGVsc2UKKyAgICAgICAgeworICAg ICAgICAgICAgLyogc2V0IGRldmljZSBpZCBvZiBpb2FwaWMgKi8KKyAgICAg ICAgICAgIGlvYXBpY19iZGZbaXZoZF9kZXZpY2UtPnNwZWNpYWwuaGFuZGxl XS5iZGYgPSBiZGY7CisKKyAgICAgICAgICAgIGlvYXBpY19iZGZbaXZoZF9k ZXZpY2UtPnNwZWNpYWwuaGFuZGxlXS5waW5fc2V0dXAgPSB4emFsbG9jX2Fy cmF5KAorICAgICAgICAgICAgICAgIHVuc2lnbmVkIGxvbmcsIEJJVFNfVE9f TE9OR1MobnJfaW9hcGljX3JlZ2lzdGVyc1thcGljXSkpOworICAgICAgICAg ICAgaWYgKCBucl9pb2FwaWNfcmVnaXN0ZXJzW2FwaWNdICYmCisgICAgICAg ICAgICAgICAgICFpb2FwaWNfYmRmW0lPX0FQSUNfSUQoYXBpYyldLnBpbl9z ZXR1cCApCisgICAgICAgICAgICB7CisgICAgICAgICAgICAgICAgcHJpbnRr KFhFTkxPR19FUlIgIklWSEQgRXJyb3I6IE91dCBvZiBtZW1vcnlcbiIpOwor ICAgICAgICAgICAgICAgIHJldHVybiAwOworICAgICAgICAgICAgfQorICAg ICAgICB9CisgICAgICAgIHJldHVybiBkZXZfbGVuZ3RoOworICAgIH0KKwor ICAgIHByaW50ayhYRU5MT0dfRVJSICJJVkhEIEVycm9yOiBJbnZhbGlkIElP LUFQSUMgJSN4XG4iLAorICAgICAgICAgICBpdmhkX2RldmljZS0+c3BlY2lh bC5oYW5kbGUpOworICAgIHJldHVybiAwOwogfQogCiBzdGF0aWMgaW50IF9f aW5pdCBwYXJzZV9pdmhkX2Jsb2NrKHN0cnVjdCBhY3BpX2l2aGRfYmxvY2tf aGVhZGVyICppdmhkX2Jsb2NrKQpAQCAtODE3LDYgKzg2Nyw3IEBAIHN0YXRp YyBpbnQgX19pbml0IHBhcnNlX2l2cnNfdGFibGUoc3RydWMKIHsKICAgICBz dHJ1Y3QgYWNwaV9pdnJzX2Jsb2NrX2hlYWRlciAqaXZyc19ibG9jazsKICAg ICB1bnNpZ25lZCBsb25nIGxlbmd0aDsKKyAgICB1bnNpZ25lZCBpbnQgYXBp YzsKICAgICBpbnQgZXJyb3IgPSAwOwogICAgIHN0cnVjdCBhY3BpX3RhYmxl X2hlYWRlciAqdGFibGUgPSAoc3RydWN0IGFjcGlfdGFibGVfaGVhZGVyICop X3RhYmxlOwogCkBAIC04NTEsNiArOTAyLDI5IEBAIHN0YXRpYyBpbnQgX19p bml0IHBhcnNlX2l2cnNfdGFibGUoc3RydWMKICAgICAgICAgbGVuZ3RoICs9 IGl2cnNfYmxvY2stPmxlbmd0aDsKICAgICB9CiAKKyAgICAvKiBFYWNoIElP LUFQSUMgbXVzdCBoYXZlIGJlZW4gbWVudGlvbmVkIGluIHRoZSB0YWJsZS4g Ki8KKyAgICBmb3IgKCBhcGljID0gMDsgIWVycm9yICYmIGFwaWMgPCBucl9p b2FwaWNzOyArK2FwaWMgKQorICAgIHsKKyAgICAgICAgaWYgKCAhbnJfaW9h cGljX3JlZ2lzdGVyc1thcGljXSB8fAorICAgICAgICAgICAgIGlvYXBpY19i ZGZbSU9fQVBJQ19JRChhcGljKV0ucGluX3NldHVwICkKKyAgICAgICAgICAg IGNvbnRpbnVlOworCisgICAgICAgIHByaW50ayhYRU5MT0dfRVJSICJJVkhE IEVycm9yOiBubyBpbmZvcm1hdGlvbiBmb3IgSU8tQVBJQyAlI3hcbiIsCisg ICAgICAgICAgICAgICBJT19BUElDX0lEKGFwaWMpKTsKKyAgICAgICAgaWYg KCBhbWRfaW9tbXVfcGVyZGV2X2ludHJlbWFwICkKKyAgICAgICAgICAgIGVy cm9yID0gLUVOWElPOworICAgICAgICBlbHNlCisgICAgICAgIHsKKyAgICAg ICAgICAgIGlvYXBpY19iZGZbSU9fQVBJQ19JRChhcGljKV0ucGluX3NldHVw ID0geHphbGxvY19hcnJheSgKKyAgICAgICAgICAgICAgICB1bnNpZ25lZCBs b25nLCBCSVRTX1RPX0xPTkdTKG5yX2lvYXBpY19yZWdpc3RlcnNbYXBpY10p KTsKKyAgICAgICAgICAgIGlmICggIWlvYXBpY19iZGZbSU9fQVBJQ19JRChh cGljKV0ucGluX3NldHVwICkKKyAgICAgICAgICAgIHsKKyAgICAgICAgICAg ICAgICBwcmludGsoWEVOTE9HX0VSUiAiSVZIRCBFcnJvcjogT3V0IG9mIG1l bW9yeVxuIik7CisgICAgICAgICAgICAgICAgZXJyb3IgPSAtRU5PTUVNOwor ICAgICAgICAgICAgfQorICAgICAgICB9CisgICAgfQorCiAgICAgcmV0dXJu IGVycm9yOwogfQogCi0tLSBhL3hlbi9kcml2ZXJzL3Bhc3N0aHJvdWdoL2Ft ZC9pb21tdV9pbml0LmMKKysrIGIveGVuL2RyaXZlcnMvcGFzc3Rocm91Z2gv YW1kL2lvbW11X2luaXQuYwpAQCAtODk3LDEyICs4OTcsNDUgQEAgc3RhdGlj IGludCBfX2luaXQgYW1kX2lvbW11X3NldHVwX2RldmljZQogICAgIHJldHVy biAwOwogfQogCisvKiBDaGVjayB3aGV0aGVyIFNQNTEwMCBTQVRBIENvbWJp bmVkIG1vZGUgaXMgb24gKi8KK3N0YXRpYyBib29sX3QgX19pbml0IGFtZF9z cDUxMDBfZXJyYXR1bTI4KHZvaWQpCit7CisgICAgdTMyIGJ1cywgaWQ7Cisg ICAgdTE2IHZlbmRvcl9pZCwgZGV2X2lkOworICAgIHU4IGJ5dGU7CisKKyAg ICBmb3IgKGJ1cyA9IDA7IGJ1cyA8IDI1NjsgYnVzKyspCisgICAgeworICAg ICAgICBpZCA9IHBjaV9jb25mX3JlYWQzMihidXMsIDB4MTQsIDAsIFBDSV9W RU5ET1JfSUQpOworCisgICAgICAgIHZlbmRvcl9pZCA9IGlkICYgMHhmZmZm OworICAgICAgICBkZXZfaWQgPSAoaWQgPj4gMTYpICYgMHhmZmZmOworCisg ICAgICAgIC8qIFNQNTEwMCBTTUJ1cyBtb2R1bGUgc2V0cyBDb21iaW5lZCBt b2RlIG9uICovCisgICAgICAgIGlmICh2ZW5kb3JfaWQgIT0gMHgxMDAyIHx8 IGRldl9pZCAhPSAweDQzODUpCisgICAgICAgICAgICBjb250aW51ZTsKKwor ICAgICAgICBieXRlID0gcGNpX2NvbmZfcmVhZDgoYnVzLCAweDE0LCAwLCAw eGFkKTsKKyAgICAgICAgaWYgKCAoYnl0ZSA+PiAzKSAmIDEgKQorICAgICAg ICB7CisgICAgICAgICAgICBwcmludGsoWEVOTE9HX1dBUk5JTkcgIkFNRC1W aTogU1A1MTAwIGVycmF0dW0gMjggZGV0ZWN0ZWQsIGRpc2FibGluZyBJT01N VS5cbiIKKyAgICAgICAgICAgICAgICAgICAiSWYgcG9zc2libGUsIGRpc2Fi bGUgU0FUQSBDb21iaW5lZCBtb2RlIGluIEJJT1Mgb3IgY29udGFjdCB5b3Vy IHZlbmRvciBmb3IgQklPUyB1cGRhdGUuXG4iKTsKKyAgICAgICAgICAgIHJl dHVybiAxOworICAgICAgICB9CisgICAgfQorCisgICAgcmV0dXJuIDA7Cit9 CisKIGludCBfX2luaXQgYW1kX2lvbW11X2luaXQodm9pZCkKIHsKICAgICBz dHJ1Y3QgYW1kX2lvbW11ICppb21tdTsKIAogICAgIEJVR19PTiggIWlvbW11 X2ZvdW5kKCkgKTsKIAorICAgIGlmICggYW1kX2lvbW11X3BlcmRldl9pbnRy ZW1hcCAmJiBhbWRfc3A1MTAwX2VycmF0dW0yOCgpICkKKyAgICAgICAgZ290 byBlcnJvcl9vdXQ7CisKICAgICBpcnFfdG9faW9tbXUgPSB4bWFsbG9jX2Fy cmF5KHN0cnVjdCBhbWRfaW9tbXUgKiwgbnJfaXJxcyk7CiAgICAgaWYgKCBp cnFfdG9faW9tbXUgPT0gTlVMTCApCiAgICAgICAgIGdvdG8gZXJyb3Jfb3V0 OwotLS0gYS94ZW4vZHJpdmVycy9wYXNzdGhyb3VnaC9hbWQvaW9tbXVfaW50 ci5jCisrKyBiL3hlbi9kcml2ZXJzL3Bhc3N0aHJvdWdoL2FtZC9pb21tdV9p bnRyLmMKQEAgLTI3LDcgKzI3LDcgQEAKICNkZWZpbmUgSU5UUkVNQVBfTEVO R1RIIDB4QgogI2RlZmluZSBJTlRSRU1BUF9FTlRSSUVTICgxIDw8IElOVFJF TUFQX0xFTkdUSCkKIAotaW50IGlvYXBpY19iZGZbTUFYX0lPX0FQSUNTXTsK K3N0cnVjdCBpb2FwaWNfYmRmIGlvYXBpY19iZGZbTUFYX0lPX0FQSUNTXTsK IGV4dGVybiBzdHJ1Y3QgaXZyc19tYXBwaW5ncyAqaXZyc19tYXBwaW5nczsK IGV4dGVybiB1bnNpZ25lZCBzaG9ydCBpdnJzX2JkZl9lbnRyaWVzOwogdm9p ZCAqc2hhcmVkX2ludHJlbWFwX3RhYmxlOwpAQCAtMTE3LDEyICsxMTcsMTIg QEAgdm9pZCBpbnZhbGlkYXRlX2ludGVycnVwdF90YWJsZShzdHJ1Y3QgYQog c3RhdGljIHZvaWQgdXBkYXRlX2ludHJlbWFwX2VudHJ5X2Zyb21faW9hcGlj KAogICAgIGludCBiZGYsCiAgICAgc3RydWN0IGFtZF9pb21tdSAqaW9tbXUs Ci0gICAgc3RydWN0IElPX0FQSUNfcm91dGVfZW50cnkgKmlvYXBpY19ydGUp CisgICAgY29uc3Qgc3RydWN0IElPX0FQSUNfcm91dGVfZW50cnkgKnJ0ZSwK KyAgICBjb25zdCBzdHJ1Y3QgSU9fQVBJQ19yb3V0ZV9lbnRyeSAqb2xkX3J0 ZSkKIHsKICAgICB1bnNpZ25lZCBsb25nIGZsYWdzOwogICAgIHUzMiogZW50 cnk7CiAgICAgdTggZGVsaXZlcnlfbW9kZSwgZGVzdCwgdmVjdG9yLCBkZXN0 X21vZGU7Ci0gICAgc3RydWN0IElPX0FQSUNfcm91dGVfZW50cnkgKnJ0ZSA9 IGlvYXBpY19ydGU7CiAgICAgaW50IHJlcV9pZDsKICAgICBzcGlubG9ja190 ICpsb2NrOwogICAgIGludCBvZmZzZXQ7CkBAIC0xMzgsNiArMTM4LDE0IEBA IHN0YXRpYyB2b2lkIHVwZGF0ZV9pbnRyZW1hcF9lbnRyeV9mcm9tX2kKICAg ICBzcGluX2xvY2tfaXJxc2F2ZShsb2NrLCBmbGFncyk7CiAKICAgICBvZmZz ZXQgPSBnZXRfaW50cmVtYXBfb2Zmc2V0KHZlY3RvciwgZGVsaXZlcnlfbW9k ZSk7CisgICAgaWYgKCBvbGRfcnRlICkKKyAgICB7CisgICAgICAgIGludCBv bGRfb2Zmc2V0ID0gZ2V0X2ludHJlbWFwX29mZnNldChvbGRfcnRlLT52ZWN0 b3IsCisgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg ICAgICBvbGRfcnRlLT5kZWxpdmVyeV9tb2RlKTsKKworICAgICAgICBpZiAo IG9mZnNldCAhPSBvbGRfb2Zmc2V0ICkKKyAgICAgICAgICAgIGZyZWVfaW50 cmVtYXBfZW50cnkoYmRmLCBvbGRfb2Zmc2V0KTsKKyAgICB9CiAgICAgZW50 cnkgPSAodTMyKilnZXRfaW50cmVtYXBfZW50cnkocmVxX2lkLCBvZmZzZXQp OwogICAgIHVwZGF0ZV9pbnRyZW1hcF9lbnRyeShlbnRyeSwgdmVjdG9yLCBk ZWxpdmVyeV9tb2RlLCBkZXN0X21vZGUsIGRlc3QpOwogCkBAIC0xNzYsNyAr MTg0LDcgQEAgaW50IF9faW5pdCBhbWRfaW9tbXVfc2V0dXBfaW9hcGljX3Jl bWFwcAogICAgICAgICAgICAgICAgIGNvbnRpbnVlOwogCiAgICAgICAgICAg ICAvKiBnZXQgZGV2aWNlIGlkIG9mIGlvYXBpYyBkZXZpY2VzICovCi0gICAg ICAgICAgICBiZGYgPSBpb2FwaWNfYmRmW0lPX0FQSUNfSUQoYXBpYyldOwor ICAgICAgICAgICAgYmRmID0gaW9hcGljX2JkZltJT19BUElDX0lEKGFwaWMp XS5iZGY7CiAgICAgICAgICAgICBpb21tdSA9IGZpbmRfaW9tbXVfZm9yX2Rl dmljZShiZGYpOwogICAgICAgICAgICAgaWYgKCAhaW9tbXUgKQogICAgICAg ICAgICAgewpAQCAtMjA3LDYgKzIxNSw3IEBAIGludCBfX2luaXQgYW1kX2lv bW11X3NldHVwX2lvYXBpY19yZW1hcHAKICAgICAgICAgICAgICAgICBmbHVz aF9jb21tYW5kX2J1ZmZlcihpb21tdSk7CiAgICAgICAgICAgICAgICAgc3Bp bl91bmxvY2tfaXJxcmVzdG9yZSgmaW9tbXUtPmxvY2ssIGZsYWdzKTsKICAg ICAgICAgICAgIH0KKyAgICAgICAgICAgIHNldF9iaXQocGluLCBpb2FwaWNf YmRmW0lPX0FQSUNfSUQoYXBpYyldLnBpbl9zZXR1cCk7CiAgICAgICAgIH0K ICAgICB9CiAgICAgcmV0dXJuIDA7CkBAIC0yMTgsNiArMjI3LDcgQEAgdm9p ZCBhbWRfaW9tbXVfaW9hcGljX3VwZGF0ZV9pcmUoCiAgICAgc3RydWN0IElP X0FQSUNfcm91dGVfZW50cnkgb2xkX3J0ZSA9IHsgMCB9OwogICAgIHN0cnVj dCBJT19BUElDX3JvdXRlX2VudHJ5IG5ld19ydGUgPSB7IDAgfTsKICAgICB1 bnNpZ25lZCBpbnQgcnRlX2xvID0gKHJlZyAmIDEpID8gcmVnIC0gMSA6IHJl ZzsKKyAgICB1bnNpZ25lZCBpbnQgcGluID0gKHJlZyAtIDB4MTApIC8gMjsK ICAgICBpbnQgc2F2ZWRfbWFzaywgYmRmOwogICAgIHN0cnVjdCBhbWRfaW9t bXUgKmlvbW11OwogCkBAIC0yMjgsNyArMjM4LDcgQEAgdm9pZCBhbWRfaW9t bXVfaW9hcGljX3VwZGF0ZV9pcmUoCiAgICAgfQogCiAgICAgLyogZ2V0IGRl dmljZSBpZCBvZiBpb2FwaWMgZGV2aWNlcyAqLwotICAgIGJkZiA9IGlvYXBp Y19iZGZbSU9fQVBJQ19JRChhcGljKV07CisgICAgYmRmID0gaW9hcGljX2Jk ZltJT19BUElDX0lEKGFwaWMpXS5iZGY7CiAgICAgaW9tbXUgPSBmaW5kX2lv bW11X2Zvcl9kZXZpY2UoYmRmKTsKICAgICBpZiAoICFpb21tdSApCiAgICAg ewpAQCAtMjU0LDYgKzI2NCwxNCBAQCB2b2lkIGFtZF9pb21tdV9pb2FwaWNf dXBkYXRlX2lyZSgKICAgICAgICAgKigoKHUzMiAqKSZuZXdfcnRlKSArIDEp ID0gdmFsdWU7CiAgICAgfQogCisgICAgaWYgKCBuZXdfcnRlLm1hc2sgJiYK KyAgICAgICAgICF0ZXN0X2JpdChwaW4sIGlvYXBpY19iZGZbSU9fQVBJQ19J RChhcGljKV0ucGluX3NldHVwKSApCisgICAgeworICAgICAgICBBU1NFUlQo c2F2ZWRfbWFzayk7CisgICAgICAgIF9faW9fYXBpY193cml0ZShhcGljLCBy ZWcsIHZhbHVlKTsKKyAgICAgICAgcmV0dXJuOworICAgIH0KKwogICAgIC8q IG1hc2sgdGhlIGludGVycnVwdCB3aGlsZSB3ZSBjaGFuZ2UgdGhlIGludHJl bWFwIHRhYmxlICovCiAgICAgaWYgKCAhc2F2ZWRfbWFzayApCiAgICAgewpA QCAtMjYyLDcgKzI4MCwxMSBAQCB2b2lkIGFtZF9pb21tdV9pb2FwaWNfdXBk YXRlX2lyZSgKICAgICB9CiAKICAgICAvKiBVcGRhdGUgaW50ZXJydXB0IHJl bWFwcGluZyBlbnRyeSAqLwotICAgIHVwZGF0ZV9pbnRyZW1hcF9lbnRyeV9m cm9tX2lvYXBpYyhiZGYsIGlvbW11LCAmbmV3X3J0ZSk7CisgICAgdXBkYXRl X2ludHJlbWFwX2VudHJ5X2Zyb21faW9hcGljKAorICAgICAgICBiZGYsIGlv bW11LCAmbmV3X3J0ZSwKKyAgICAgICAgdGVzdF9hbmRfc2V0X2JpdChwaW4s CisgICAgICAgICAgICAgICAgICAgICAgICAgaW9hcGljX2JkZltJT19BUElD X0lEKGFwaWMpXS5waW5fc2V0dXApID8gJm9sZF9ydGUKKyAgICAgICAgICAg ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg ICAgICAgICAgOiBOVUxMKTsKIAogICAgIC8qIEZvcndhcmQgd3JpdGUgYWNj ZXNzIHRvIElPLUFQSUMgUlRFICovCiAgICAgX19pb19hcGljX3dyaXRlKGFw aWMsIHJlZywgdmFsdWUpOwpAQCAtMzczLDYgKzM5NSwxMiBAQCB2b2lkIGFt ZF9pb21tdV9tc2lfbXNnX3VwZGF0ZV9pcmUoCiAgICAgICAgIHJldHVybjsK ICAgICB9CiAKKyAgICBpZiAoIG1zaV9kZXNjLT5yZW1hcF9pbmRleCA+PSAw ICkKKyAgICAgICAgdXBkYXRlX2ludHJlbWFwX2VudHJ5X2Zyb21fbXNpX21z Zyhpb21tdSwgcGRldiwgbXNpX2Rlc2MsIE5VTEwpOworCisgICAgaWYgKCAh bXNnICkKKyAgICAgICAgcmV0dXJuOworCiAgICAgdXBkYXRlX2ludHJlbWFw X2VudHJ5X2Zyb21fbXNpX21zZyhpb21tdSwgcGRldiwgbXNpX2Rlc2MsIG1z Zyk7CiB9CiAKLS0tIGEveGVuL2RyaXZlcnMvcGFzc3Rocm91Z2gvYW1kL3Bj aV9hbWRfaW9tbXUuYworKysgYi94ZW4vZHJpdmVycy9wYXNzdGhyb3VnaC9h bWQvcGNpX2FtZF9pb21tdS5jCkBAIC0xOTUsNiArMTk1LDggQEAgaW50IF9f aW5pdCBhbWRfaW92X2RldGVjdCh2b2lkKQogICAgIHsKICAgICAgICAgcHJp bnRrKCJBTUQtVmk6IE5vdCBvdmVycmlkaW5nIGlycV92ZWN0b3JfbWFwIHNl dHRpbmdcbiIpOwogICAgIH0KKyAgICBpZiAoICFhbWRfaW9tbXVfcGVyZGV2 X2ludHJlbWFwICkKKyAgICAgICAgcHJpbnRrKFhFTkxPR19XQVJOSU5HICJB TUQtVmk6IFVzaW5nIGdsb2JhbCBpbnRlcnJ1cHQgcmVtYXAgdGFibGUgaXMg bm90IHJlY29tbWVuZGVkIChzZWUgWFNBLTM2KSFcbiIpOwogICAgIHJldHVy biBzY2FuX3BjaV9kZXZpY2VzKCk7CiB9CiAKLS0tIGEveGVuL2RyaXZlcnMv cGFzc3Rocm91Z2gvaW9tbXUuYworKysgYi94ZW4vZHJpdmVycy9wYXNzdGhy b3VnaC9pb21tdS5jCkBAIC00OSw3ICs0OSw3IEBAIGJvb2xfdCBfX3JlYWRf bW9zdGx5IGlvbW11X3FpbnZhbCA9IDE7CiBib29sX3QgX19yZWFkX21vc3Rs eSBpb21tdV9pbnRyZW1hcCA9IDE7CiBib29sX3QgX19yZWFkX21vc3RseSBp b21tdV9oYXBfcHRfc2hhcmU7CiBib29sX3QgX19yZWFkX21vc3RseSBhbWRf aW9tbXVfZGVidWc7Ci1ib29sX3QgX19yZWFkX21vc3RseSBhbWRfaW9tbXVf cGVyZGV2X2ludHJlbWFwOworYm9vbF90IF9fcmVhZF9tb3N0bHkgYW1kX2lv bW11X3BlcmRldl9pbnRyZW1hcCA9IDE7CiAKIHN0YXRpYyB2b2lkIF9faW5p dCBwYXJzZV9pb21tdV9wYXJhbShjaGFyICpzKQogewpAQCAtNzgsNiArNzgs OCBAQCBzdGF0aWMgdm9pZCBfX2luaXQgcGFyc2VfaW9tbXVfcGFyYW0oY2hh CiAgICAgICAgICAgICBhbWRfaW9tbXVfZGVidWcgPSAxOwogICAgICAgICBl bHNlIGlmICggIXN0cmNtcChzLCAiYW1kLWlvbW11LXBlcmRldi1pbnRyZW1h cCIpICkKICAgICAgICAgICAgIGFtZF9pb21tdV9wZXJkZXZfaW50cmVtYXAg PSAxOworICAgICAgICBlbHNlIGlmICggIXN0cmNtcChzLCAiYW1kLWlvbW11 LWdsb2JhbC1pbnRyZW1hcCIpICkKKyAgICAgICAgICAgIGFtZF9pb21tdV9w ZXJkZXZfaW50cmVtYXAgPSAwOwogICAgICAgICBlbHNlIGlmICggIXN0cmNt cChzLCAiZG9tMC1wYXNzdGhyb3VnaCIpICkKICAgICAgICAgICAgIGlvbW11 X3Bhc3N0aHJvdWdoID0gMTsKICAgICAgICAgZWxzZSBpZiAoICFzdHJjbXAo cywgImRvbTAtc3RyaWN0IikgKQotLS0gYS94ZW4vaW5jbHVkZS9hc20teDg2 L2h2bS9zdm0vYW1kLWlvbW11LXByb3RvLmgKKysrIGIveGVuL2luY2x1ZGUv YXNtLXg4Ni9odm0vc3ZtL2FtZC1pb21tdS1wcm90by5oCkBAIC04OCw2ICs4 OCwxMSBAQCB2b2lkIGFtZF9pb21tdV9yZWFkX21zaV9mcm9tX2lyZSgKIHVu c2lnbmVkIGludCBhbWRfaW9tbXVfcmVhZF9pb2FwaWNfZnJvbV9pcmUoCiAg ICAgdW5zaWduZWQgaW50IGFwaWMsIHVuc2lnbmVkIGludCByZWcpOwogCitl eHRlcm4gc3RydWN0IGlvYXBpY19iZGYgeworICAgIHUxNiBiZGY7CisgICAg dW5zaWduZWQgbG9uZyAqcGluX3NldHVwOworfSBpb2FwaWNfYmRmW107CisK IC8qIHBvd2VyIG1hbmFnZW1lbnQgc3VwcG9ydCAqLwogdm9pZCBhbWRfaW9t bXVfcmVzdW1lKHZvaWQpOwogdm9pZCBhbWRfaW9tbXVfc3VzcGVuZCh2b2lk KTsK --=separator Content-Type: application/octet-stream; name="xsa36-4.2.patch" Content-Disposition: attachment; filename="xsa36-4.2.patch" Content-Transfer-Encoding: base64 QUNQSTogYWNwaV90YWJsZV9wYXJzZSgpIHNob3VsZCByZXR1cm4gaGFuZGxl cidzIGVycm9yIGNvZGUKCkN1cnJlbnRseSwgdGhlIGVycm9yIGNvZGUgcmV0 dXJuZWQgYnkgYWNwaV90YWJsZV9wYXJzZSgpJ3MgaGFuZGxlcgppcyBpZ25v cmVkLiBUaGlzIHBhdGNoIHdpbGwgcHJvcGFnYXRlIGhhbmRsZXIncyByZXR1 cm4gdmFsdWUgdG8KYWNwaV90YWJsZV9wYXJzZSgpJ3MgY2FsbGVyLgoKQU1E LElPTU1VOiBDbGVhbiB1cCBvbGQgZW50cmllcyBpbiByZW1hcHBpbmcgdGFi bGVzIHdoZW4gY3JlYXRpbmcgbmV3CmludGVycnVwdCBtYXBwaW5nLgoKV2hl biBjaGFuZ2luZyB0aGUgYWZmaW5pdHkgb2YgYW4gSVJRIGFzc29jaWF0ZWQg d2l0aCBhIHBhc3NlZAp0aHJvdWdoIFBDSSBkZXZpY2UsIGNsZWFyIHByZXZp b3VzIG1hcHBpbmcuCgpJbiBhZGRpdGlvbiwgYmVjYXVzZSBzb21lIEJJT1Nl cyBtYXkgaW5jb3JyZWN0bHkgcHJvZ3JhbSBJVlJTCmVudHJpZXMgZm9yIElP QVBJQyB0cnkgdG8gY2hlY2sgZm9yIGVudHJ5J3MgY29uc2lzdGVuY3kuIFNw ZWNpZmljYWxseSwKaWYgY29uZmxpY3RpbmcgZW50cmllcyBhcmUgZm91bmQg ZGlzYWJsZSBJT01NVSBpZiBwZXItZGV2aWNlCnJlbWFwcGluZyB0YWJsZSBp cyB1c2VkLiBJZiBlbnRyaWVzIHJlZmVyIHRvIGJvZ3VzIElPQVBJQyBJRHMK ZGlzYWJsZSBJT01NVSB1bmNvbmRpdGlvbmFsbHkKCkFNRCxJT01NVTogRGlz YWJsZSBJT01NVSBpZiBTQVRBIENvbWJpbmVkIG1vZGUgaXMgb24KCkFNRCdz IFNQNTEwMCBjaGlwc2V0IGNhbiBiZSBwbGFjZWQgaW50byBTQVRBIENvbWJp bmVkIG1vZGUKdGhhdCBtYXkgY2F1c2UgcHJldmVudCBkb20wIGZyb20gYm9v dGluZyB3aGVuIElPTU1VIGlzCmVuYWJsZWQgYW5kIHBlci1kZXZpY2UgaW50 ZXJydXB0IHJlbWFwcGluZyB0YWJsZSBpcyB1c2VkLgpXaGlsZSBTUDUxMDAg ZXJyYXR1bSAyOCByZXF1aXJlcyBCSU9TZXMgdG8gZGlzYWJsZSB0aGlzIG1v ZGUsCnNvbWUgbWF5IHN0aWxsIHVzZSBpdC4KClRoaXMgcGF0Y2ggY2hlY2tz IHdoZXRoZXIgdGhpcyBtb2RlIGlzIG9uIGFuZCwgaWYgcGVyLWRldmljZQp0 YWJsZSBpcyBpbiB1c2UsIGRpc2FibGVzIElPTU1VLgoKQU1ELElPTU1VOiBN YWtlIHBlci1kZXZpY2UgaW50ZXJydXB0IHJlbWFwcGluZyB0YWJsZSBkZWZh dWx0CgpVc2luZyBnbG9iYWwgaW50ZXJydXB0IHJlbWFwcGluZyB0YWJsZSBt YXkgYmUgaW5zZWN1cmUsIGFzCmRlc2NyaWJlZCBieSBYU0EtMzYuIFRoaXMg cGF0Y2ggbWFrZXMgcGVyLWRldmljZSBtb2RlIGRlZmF1bHQuCgpUaGlzIGlz IFhTQS0zNiAvIENWRS0yMDEzLTAxNTMuCgpTaWduZWQtb2ZmLWJ5OiBKYW4g QmV1bGljaCA8amJldWxpY2hAc3VzZS5jb20+ClNpZ25lZC1vZmYtYnk6IEJv cmlzIE9zdHJvdnNreSA8Ym9yaXMub3N0cm92c2t5QGFtZC5jb20+CgpBTUQg SU9NTVU6IGFsc28gc3BvdCBtaXNzaW5nIElPLUFQSUMgZW50cmllcyBpbiBJ VlJTIHRhYmxlCgpBcGFydCBmcm9tIGRlYWxpbmcgZHVwbGljYXRlIGNvbmZs aWN0aW5nIGVudHJpZXMsIHdlIGFsc28gaGF2ZSB0bwpoYW5kbGUgZmlybXdh cmUgb21pdHRpbmcgSU8tQVBJQyBlbnRyaWVzIGluIElWUlMgYWx0b2dldGhl ci4gTm90IGRvaW5nCnNvIGhhcyByZXN1bHRlZCBpbiBjL3MgMjY1MTc6NjAx MTM5ZTJiMGRiIHRvIGNyYXNoIHN1Y2ggc3lzdGVtcyBkdXJpbmcKYm9vdCAo d2hlcmVhcyB3aXRoIHRoZSBjaGFuZ2UgaGVyZSB0aGUgSU9NTVUgZ2V0cyBk aXNhYmxlZCBqdXN0IGFzIGlzCmJlaW5nIGRvbmUgaW4gdGhlIG90aGVyIGNh c2VzLCBpLmUuIHVubGVzcyBnbG9iYWwgdGFibGVzIGFyZSBiZWluZwp1c2Vk KS4KCkRlYnVnZ2luZyB0aGlzIGlzc3VlIGhhcyBhbHNvIHBvaW50ZWQgb3V0 IHRoYXQgdGhlIGRlYnVnIGxvZyBvdXRwdXQgaXMKcHJldHR5IHVnbHkgdG8g bG9vayBhdCAtIGNvbnNvbGlkYXRlIHRoZSBvdXRwdXQsIGFuZCBhZGQgb25l IGV4dHJhCml0ZW0gZm9yIHRoZSBJVkhEIHNwZWNpYWwgZW50cmllcywgc28g dGhhdCBmdXR1cmUgaXNzdWVzIGFyZSBlYXNpZXIKdG8gYW5hbHl6ZS4KClNp Z25lZC1vZmYtYnk6IEphbiBCZXVsaWNoIDxqYmV1bGljaEBzdXNlLmNvbT4K VGVzdGVkLWJ5OiBTYW5kZXIgRWlrZWxlbmJvb20gPGxpbnV4QGVpa2VsZW5i b29tLml0PgoKLS0tIGEveGVuL2FyY2gveDg2L2lycS5jCisrKyBiL3hlbi9h cmNoL3g4Ni9pcnEuYwpAQCAtMTk0Miw5ICsxOTQyLDYgQEAgaW50IG1hcF9k b21haW5fcGlycSgKICAgICAgICAgc3Bpbl9sb2NrX2lycXNhdmUoJmRlc2Mt PmxvY2ssIGZsYWdzKTsKICAgICAgICAgc2V0X2RvbWFpbl9pcnFfcGlycShk LCBpcnEsIGluZm8pOwogICAgICAgICBzcGluX3VubG9ja19pcnFyZXN0b3Jl KCZkZXNjLT5sb2NrLCBmbGFncyk7Ci0KLSAgICAgICAgaWYgKCBvcHRfaXJx X3ZlY3Rvcl9tYXAgPT0gT1BUX0lSUV9WRUNUT1JfTUFQX1BFUkRFViApCi0g ICAgICAgICAgICBwcmludGsoWEVOTE9HX0lORk8gIlBlci1kZXZpY2UgdmVj dG9yIG1hcHMgZm9yIEdTSXMgbm90IGltcGxlbWVudGVkIHlldC5cbiIpOwog ICAgIH0KIAogZG9uZToKLS0tIGEveGVuL2RyaXZlcnMvYWNwaS90YWJsZXMu YworKysgYi94ZW4vZHJpdmVycy9hY3BpL3RhYmxlcy5jCkBAIC0yNjcsNyAr MjY3LDcgQEAgYWNwaV90YWJsZV9wYXJzZV9tYWR0KGVudW0gYWNwaV9tYWR0 X3R5cAogICogQGhhbmRsZXI6IGhhbmRsZXIgdG8gcnVuCiAgKgogICogU2Nh biB0aGUgQUNQSSBTeXN0ZW0gRGVzY3JpcHRvciBUYWJsZSAoU1REKSBmb3Ig YSB0YWJsZSBtYXRjaGluZyBAaWQsCi0gKiBydW4gQGhhbmRsZXIgb24gaXQu ICBSZXR1cm4gMCBpZiB0YWJsZSBmb3VuZCwgcmV0dXJuIG9uIGlmIG5vdC4K KyAqIHJ1biBAaGFuZGxlciBvbiBpdC4KICAqLwogaW50IF9faW5pdCBhY3Bp X3RhYmxlX3BhcnNlKGNoYXIgKmlkLCBhY3BpX3RhYmxlX2hhbmRsZXIgaGFu ZGxlcikKIHsKQEAgLTI4Miw4ICsyODIsNyBAQCBpbnQgX19pbml0IGFjcGlf dGFibGVfcGFyc2UoY2hhciAqaWQsIGFjCiAJCWFjcGlfZ2V0X3RhYmxlKGlk LCAwLCAmdGFibGUpOwogCiAJaWYgKHRhYmxlKSB7Ci0JCWhhbmRsZXIodGFi bGUpOwotCQlyZXR1cm4gMDsKKwkJcmV0dXJuIGhhbmRsZXIodGFibGUpOwog CX0gZWxzZQogCQlyZXR1cm4gMTsKIH0KLS0tIGEveGVuL2RyaXZlcnMvcGFz c3Rocm91Z2gvYW1kL2lvbW11X2FjcGkuYworKysgYi94ZW4vZHJpdmVycy9w YXNzdGhyb3VnaC9hbWQvaW9tbXVfYWNwaS5jCkBAIC0yMiw2ICsyMiw3IEBA CiAjaW5jbHVkZSA8eGVuL2Vycm5vLmg+CiAjaW5jbHVkZSA8eGVuL2FjcGku aD4KICNpbmNsdWRlIDxhc20vYXBpY2RlZi5oPgorI2luY2x1ZGUgPGFzbS9p b19hcGljLmg+CiAjaW5jbHVkZSA8YXNtL2FtZC1pb21tdS5oPgogI2luY2x1 ZGUgPGFzbS9odm0vc3ZtL2FtZC1pb21tdS1wcm90by5oPgogCkBAIC02MzUs NiArNjM2LDcgQEAgc3RhdGljIHUxNiBfX2luaXQgcGFyc2VfaXZoZF9kZXZp Y2Vfc3BlYwogICAgIHUxNiBoZWFkZXJfbGVuZ3RoLCB1MTYgYmxvY2tfbGVu Z3RoLCBzdHJ1Y3QgYW1kX2lvbW11ICppb21tdSkKIHsKICAgICB1MTYgZGV2 X2xlbmd0aCwgYmRmOworICAgIGludCBhcGljOwogCiAgICAgZGV2X2xlbmd0 aCA9IHNpemVvZigqc3BlY2lhbCk7CiAgICAgaWYgKCBoZWFkZXJfbGVuZ3Ro IDwgKGJsb2NrX2xlbmd0aCArIGRldl9sZW5ndGgpICkKQEAgLTY1MSwxMCAr NjUzLDU5IEBAIHN0YXRpYyB1MTYgX19pbml0IHBhcnNlX2l2aGRfZGV2aWNl X3NwZWMKICAgICB9CiAKICAgICBhZGRfaXZyc19tYXBwaW5nX2VudHJ5KGJk ZiwgYmRmLCBzcGVjaWFsLT5oZWFkZXIuZGF0YV9zZXR0aW5nLCBpb21tdSk7 Ci0gICAgLyogc2V0IGRldmljZSBpZCBvZiBpb2FwaWMgKi8KLSAgICBpb2Fw aWNfc2JkZltzcGVjaWFsLT5oYW5kbGVdLmJkZiA9IGJkZjsKLSAgICBpb2Fw aWNfc2JkZltzcGVjaWFsLT5oYW5kbGVdLnNlZyA9IHNlZzsKLSAgICByZXR1 cm4gZGV2X2xlbmd0aDsKKworICAgIGlmICggc3BlY2lhbC0+dmFyaWV0eSAh PSBBQ1BJX0lWSERfSU9BUElDICkKKyAgICB7CisgICAgICAgIGlmICggc3Bl Y2lhbC0+dmFyaWV0eSAhPSBBQ1BJX0lWSERfSFBFVCApCisgICAgICAgICAg ICBwcmludGsoWEVOTE9HX0VSUiAiVW5yZWNvZ25pemVkIElWSEQgc3BlY2lh bCB2YXJpZXR5ICUjeFxuIiwKKyAgICAgICAgICAgICAgICAgICBzcGVjaWFs LT52YXJpZXR5KTsKKyAgICAgICAgcmV0dXJuIGRldl9sZW5ndGg7CisgICAg fQorCisgICAgLyoKKyAgICAgKiBTb21lIEJJT1NlcyBoYXZlIElPQVBJQyBi cm9rZW4gZW50cmllcyBzbyB3ZSBjaGVjayBmb3IgSVZSUworICAgICAqIGNv bnNpc3RlbmN5IGhlcmUgLS0tIHdoZXRoZXIgZW50cnkncyBJT0FQSUMgSUQg aXMgdmFsaWQgYW5kCisgICAgICogd2hldGhlciB0aGVyZSBhcmUgY29uZmxp Y3RpbmcvZHVwbGljYXRlZCBlbnRyaWVzLgorICAgICAqLworICAgIGZvciAo IGFwaWMgPSAwOyBhcGljIDwgbnJfaW9hcGljczsgYXBpYysrICkKKyAgICB7 CisgICAgICAgIGlmICggSU9fQVBJQ19JRChhcGljKSAhPSBzcGVjaWFsLT5o YW5kbGUgKQorICAgICAgICAgICAgY29udGludWU7CisKKyAgICAgICAgaWYg KCBpb2FwaWNfc2JkZltzcGVjaWFsLT5oYW5kbGVdLnBpbl9zZXR1cCApCisg ICAgICAgIHsKKyAgICAgICAgICAgIGlmICggaW9hcGljX3NiZGZbc3BlY2lh bC0+aGFuZGxlXS5iZGYgPT0gYmRmICYmCisgICAgICAgICAgICAgICAgIGlv YXBpY19zYmRmW3NwZWNpYWwtPmhhbmRsZV0uc2VnID09IHNlZyApCisgICAg ICAgICAgICAgICAgQU1EX0lPTU1VX0RFQlVHKCJJVkhEIFdhcm5pbmc6IER1 cGxpY2F0ZSBJTy1BUElDICUjeCBlbnRyaWVzXG4iLAorICAgICAgICAgICAg ICAgICAgICAgICAgICAgICAgICBzcGVjaWFsLT5oYW5kbGUpOworICAgICAg ICAgICAgZWxzZQorICAgICAgICAgICAgeworICAgICAgICAgICAgICAgIHBy aW50ayhYRU5MT0dfRVJSICJJVkhEIEVycm9yOiBDb25mbGljdGluZyBJTy1B UElDICUjeCBlbnRyaWVzXG4iLAorICAgICAgICAgICAgICAgICAgICAgICBz cGVjaWFsLT5oYW5kbGUpOworICAgICAgICAgICAgICAgIGlmICggYW1kX2lv bW11X3BlcmRldl9pbnRyZW1hcCApCisgICAgICAgICAgICAgICAgICAgIHJl dHVybiAwOworICAgICAgICAgICAgfQorICAgICAgICB9CisgICAgICAgIGVs c2UKKyAgICAgICAgeworICAgICAgICAgICAgLyogc2V0IGRldmljZSBpZCBv ZiBpb2FwaWMgKi8KKyAgICAgICAgICAgIGlvYXBpY19zYmRmW3NwZWNpYWwt PmhhbmRsZV0uYmRmID0gYmRmOworICAgICAgICAgICAgaW9hcGljX3NiZGZb c3BlY2lhbC0+aGFuZGxlXS5zZWcgPSBzZWc7CisKKyAgICAgICAgICAgIGlv YXBpY19zYmRmW3NwZWNpYWwtPmhhbmRsZV0ucGluX3NldHVwID0geHphbGxv Y19hcnJheSgKKyAgICAgICAgICAgICAgICB1bnNpZ25lZCBsb25nLCBCSVRT X1RPX0xPTkdTKG5yX2lvYXBpY19lbnRyaWVzW2FwaWNdKSk7CisgICAgICAg ICAgICBpZiAoIG5yX2lvYXBpY19lbnRyaWVzW2FwaWNdICYmCisgICAgICAg ICAgICAgICAgICFpb2FwaWNfc2JkZltJT19BUElDX0lEKGFwaWMpXS5waW5f c2V0dXAgKQorICAgICAgICAgICAgeworICAgICAgICAgICAgICAgIHByaW50 ayhYRU5MT0dfRVJSICJJVkhEIEVycm9yOiBPdXQgb2YgbWVtb3J5XG4iKTsK KyAgICAgICAgICAgICAgICByZXR1cm4gMDsKKyAgICAgICAgICAgIH0KKyAg ICAgICAgfQorICAgICAgICByZXR1cm4gZGV2X2xlbmd0aDsKKyAgICB9CisK KyAgICBwcmludGsoWEVOTE9HX0VSUiAiSVZIRCBFcnJvcjogSW52YWxpZCBJ Ty1BUElDICUjeFxuIiwgc3BlY2lhbC0+aGFuZGxlKTsKKyAgICByZXR1cm4g MDsKIH0KIAogc3RhdGljIGludCBfX2luaXQgcGFyc2VfaXZoZF9ibG9jayhj b25zdCBzdHJ1Y3QgYWNwaV9pdnJzX2hhcmR3YXJlICppdmhkX2Jsb2NrKQpA QCAtODE4LDYgKzg2OSw3IEBAIHN0YXRpYyBpbnQgX19pbml0IHBhcnNlX2l2 cnNfdGFibGUoc3RydWMKIHsKICAgICBjb25zdCBzdHJ1Y3QgYWNwaV9pdnJz X2hlYWRlciAqaXZyc19ibG9jazsKICAgICB1bnNpZ25lZCBsb25nIGxlbmd0 aDsKKyAgICB1bnNpZ25lZCBpbnQgYXBpYzsKICAgICBpbnQgZXJyb3IgPSAw OwogCiAgICAgQlVHX09OKCF0YWJsZSk7CkBAIC04NTAsNiArOTAyLDI5IEBA IHN0YXRpYyBpbnQgX19pbml0IHBhcnNlX2l2cnNfdGFibGUoc3RydWMKICAg ICAgICAgbGVuZ3RoICs9IGl2cnNfYmxvY2stPmxlbmd0aDsKICAgICB9CiAK KyAgICAvKiBFYWNoIElPLUFQSUMgbXVzdCBoYXZlIGJlZW4gbWVudGlvbmVk IGluIHRoZSB0YWJsZS4gKi8KKyAgICBmb3IgKCBhcGljID0gMDsgIWVycm9y ICYmIGFwaWMgPCBucl9pb2FwaWNzOyArK2FwaWMgKQorICAgIHsKKyAgICAg ICAgaWYgKCAhbnJfaW9hcGljX2VudHJpZXNbYXBpY10gfHwKKyAgICAgICAg ICAgICBpb2FwaWNfc2JkZltJT19BUElDX0lEKGFwaWMpXS5waW5fc2V0dXAg KQorICAgICAgICAgICAgY29udGludWU7CisKKyAgICAgICAgcHJpbnRrKFhF TkxPR19FUlIgIklWSEQgRXJyb3I6IG5vIGluZm9ybWF0aW9uIGZvciBJTy1B UElDICUjeFxuIiwKKyAgICAgICAgICAgICAgIElPX0FQSUNfSUQoYXBpYykp OworICAgICAgICBpZiAoIGFtZF9pb21tdV9wZXJkZXZfaW50cmVtYXAgKQor ICAgICAgICAgICAgZXJyb3IgPSAtRU5YSU87CisgICAgICAgIGVsc2UKKyAg ICAgICAgeworICAgICAgICAgICAgaW9hcGljX3NiZGZbSU9fQVBJQ19JRChh cGljKV0ucGluX3NldHVwID0geHphbGxvY19hcnJheSgKKyAgICAgICAgICAg ICAgICB1bnNpZ25lZCBsb25nLCBCSVRTX1RPX0xPTkdTKG5yX2lvYXBpY19l bnRyaWVzW2FwaWNdKSk7CisgICAgICAgICAgICBpZiAoICFpb2FwaWNfc2Jk ZltJT19BUElDX0lEKGFwaWMpXS5waW5fc2V0dXAgKQorICAgICAgICAgICAg eworICAgICAgICAgICAgICAgIHByaW50ayhYRU5MT0dfRVJSICJJVkhEIEVy cm9yOiBPdXQgb2YgbWVtb3J5XG4iKTsKKyAgICAgICAgICAgICAgICBlcnJv ciA9IC1FTk9NRU07CisgICAgICAgICAgICB9CisgICAgICAgIH0KKyAgICB9 CisKICAgICByZXR1cm4gZXJyb3I7CiB9CiAKLS0tIGEveGVuL2RyaXZlcnMv cGFzc3Rocm91Z2gvYW1kL2lvbW11X2luaXQuYworKysgYi94ZW4vZHJpdmVy cy9wYXNzdGhyb3VnaC9hbWQvaW9tbXVfaW5pdC5jCkBAIC0xMTI2LDEyICsx MTI2LDQ1IEBAIHN0YXRpYyBpbnQgX19pbml0IGFtZF9pb21tdV9zZXR1cF9k ZXZpY2UKICAgICByZXR1cm4gMDsKIH0KIAorLyogQ2hlY2sgd2hldGhlciBT UDUxMDAgU0FUQSBDb21iaW5lZCBtb2RlIGlzIG9uICovCitzdGF0aWMgYm9v bF90IF9faW5pdCBhbWRfc3A1MTAwX2VycmF0dW0yOCh2b2lkKQoreworICAg IHUzMiBidXMsIGlkOworICAgIHUxNiB2ZW5kb3JfaWQsIGRldl9pZDsKKyAg ICB1OCBieXRlOworCisgICAgZm9yIChidXMgPSAwOyBidXMgPCAyNTY7IGJ1 cysrKQorICAgIHsKKyAgICAgICAgaWQgPSBwY2lfY29uZl9yZWFkMzIoMCwg YnVzLCAweDE0LCAwLCBQQ0lfVkVORE9SX0lEKTsKKworICAgICAgICB2ZW5k b3JfaWQgPSBpZCAmIDB4ZmZmZjsKKyAgICAgICAgZGV2X2lkID0gKGlkID4+ IDE2KSAmIDB4ZmZmZjsKKworICAgICAgICAvKiBTUDUxMDAgU01CdXMgbW9k dWxlIHNldHMgQ29tYmluZWQgbW9kZSBvbiAqLworICAgICAgICBpZiAodmVu ZG9yX2lkICE9IDB4MTAwMiB8fCBkZXZfaWQgIT0gMHg0Mzg1KQorICAgICAg ICAgICAgY29udGludWU7CisKKyAgICAgICAgYnl0ZSA9IHBjaV9jb25mX3Jl YWQ4KDAsIGJ1cywgMHgxNCwgMCwgMHhhZCk7CisgICAgICAgIGlmICggKGJ5 dGUgPj4gMykgJiAxICkKKyAgICAgICAgeworICAgICAgICAgICAgcHJpbnRr KFhFTkxPR19XQVJOSU5HICJBTUQtVmk6IFNQNTEwMCBlcnJhdHVtIDI4IGRl dGVjdGVkLCBkaXNhYmxpbmcgSU9NTVUuXG4iCisgICAgICAgICAgICAgICAg ICAgIklmIHBvc3NpYmxlLCBkaXNhYmxlIFNBVEEgQ29tYmluZWQgbW9kZSBp biBCSU9TIG9yIGNvbnRhY3QgeW91ciB2ZW5kb3IgZm9yIEJJT1MgdXBkYXRl LlxuIik7CisgICAgICAgICAgICByZXR1cm4gMTsKKyAgICAgICAgfQorICAg IH0KKworICAgIHJldHVybiAwOworfQorCiBpbnQgX19pbml0IGFtZF9pb21t dV9pbml0KHZvaWQpCiB7CiAgICAgc3RydWN0IGFtZF9pb21tdSAqaW9tbXU7 CiAKICAgICBCVUdfT04oICFpb21tdV9mb3VuZCgpICk7CiAKKyAgICBpZiAo IGFtZF9pb21tdV9wZXJkZXZfaW50cmVtYXAgJiYgYW1kX3NwNTEwMF9lcnJh dHVtMjgoKSApCisgICAgICAgIGdvdG8gZXJyb3Jfb3V0OworCiAgICAgaXZy c19iZGZfZW50cmllcyA9IGFtZF9pb21tdV9nZXRfaXZyc19kZXZfZW50cmll cygpOwogCiAgICAgaWYgKCAhaXZyc19iZGZfZW50cmllcyApCi0tLSBhL3hl bi9kcml2ZXJzL3Bhc3N0aHJvdWdoL2FtZC9pb21tdV9pbnRyLmMKKysrIGIv eGVuL2RyaXZlcnMvcGFzc3Rocm91Z2gvYW1kL2lvbW11X2ludHIuYwpAQCAt OTksMTIgKzk5LDEyIEBAIHN0YXRpYyB2b2lkIHVwZGF0ZV9pbnRyZW1hcF9l bnRyeSh1MzIqIGUKIHN0YXRpYyB2b2lkIHVwZGF0ZV9pbnRyZW1hcF9lbnRy eV9mcm9tX2lvYXBpYygKICAgICBpbnQgYmRmLAogICAgIHN0cnVjdCBhbWRf aW9tbXUgKmlvbW11LAotICAgIHN0cnVjdCBJT19BUElDX3JvdXRlX2VudHJ5 ICppb2FwaWNfcnRlKQorICAgIGNvbnN0IHN0cnVjdCBJT19BUElDX3JvdXRl X2VudHJ5ICpydGUsCisgICAgY29uc3Qgc3RydWN0IElPX0FQSUNfcm91dGVf ZW50cnkgKm9sZF9ydGUpCiB7CiAgICAgdW5zaWduZWQgbG9uZyBmbGFnczsK ICAgICB1MzIqIGVudHJ5OwogICAgIHU4IGRlbGl2ZXJ5X21vZGUsIGRlc3Qs IHZlY3RvciwgZGVzdF9tb2RlOwotICAgIHN0cnVjdCBJT19BUElDX3JvdXRl X2VudHJ5ICpydGUgPSBpb2FwaWNfcnRlOwogICAgIGludCByZXFfaWQ7CiAg ICAgc3BpbmxvY2tfdCAqbG9jazsKICAgICBpbnQgb2Zmc2V0OwpAQCAtMTIw LDYgKzEyMCwxNCBAQCBzdGF0aWMgdm9pZCB1cGRhdGVfaW50cmVtYXBfZW50 cnlfZnJvbV9pCiAgICAgc3Bpbl9sb2NrX2lycXNhdmUobG9jaywgZmxhZ3Mp OwogCiAgICAgb2Zmc2V0ID0gZ2V0X2ludHJlbWFwX29mZnNldCh2ZWN0b3Is IGRlbGl2ZXJ5X21vZGUpOworICAgIGlmICggb2xkX3J0ZSApCisgICAgewor ICAgICAgICBpbnQgb2xkX29mZnNldCA9IGdldF9pbnRyZW1hcF9vZmZzZXQo b2xkX3J0ZS0+dmVjdG9yLAorICAgICAgICAgICAgICAgICAgICAgICAgICAg ICAgICAgICAgICAgICAgICAgb2xkX3J0ZS0+ZGVsaXZlcnlfbW9kZSk7CisK KyAgICAgICAgaWYgKCBvZmZzZXQgIT0gb2xkX29mZnNldCApCisgICAgICAg ICAgICBmcmVlX2ludHJlbWFwX2VudHJ5KGlvbW11LT5zZWcsIGJkZiwgb2xk X29mZnNldCk7CisgICAgfQogICAgIGVudHJ5ID0gKHUzMiopZ2V0X2ludHJl bWFwX2VudHJ5KGlvbW11LT5zZWcsIHJlcV9pZCwgb2Zmc2V0KTsKICAgICB1 cGRhdGVfaW50cmVtYXBfZW50cnkoZW50cnksIHZlY3RvciwgZGVsaXZlcnlf bW9kZSwgZGVzdF9tb2RlLCBkZXN0KTsKIApAQCAtMTg4LDYgKzE5Niw3IEBA IGludCBfX2luaXQgYW1kX2lvbW11X3NldHVwX2lvYXBpY19yZW1hcHAKICAg ICAgICAgICAgICAgICBhbWRfaW9tbXVfZmx1c2hfaW50cmVtYXAoaW9tbXUs IHJlcV9pZCk7CiAgICAgICAgICAgICAgICAgc3Bpbl91bmxvY2tfaXJxcmVz dG9yZSgmaW9tbXUtPmxvY2ssIGZsYWdzKTsKICAgICAgICAgICAgIH0KKyAg ICAgICAgICAgIHNldF9iaXQocGluLCBpb2FwaWNfc2JkZltJT19BUElDX0lE KGFwaWMpXS5waW5fc2V0dXApOwogICAgICAgICB9CiAgICAgfQogICAgIHJl dHVybiAwOwpAQCAtMTk5LDYgKzIwOCw3IEBAIHZvaWQgYW1kX2lvbW11X2lv YXBpY191cGRhdGVfaXJlKAogICAgIHN0cnVjdCBJT19BUElDX3JvdXRlX2Vu dHJ5IG9sZF9ydGUgPSB7IDAgfTsKICAgICBzdHJ1Y3QgSU9fQVBJQ19yb3V0 ZV9lbnRyeSBuZXdfcnRlID0geyAwIH07CiAgICAgdW5zaWduZWQgaW50IHJ0 ZV9sbyA9IChyZWcgJiAxKSA/IHJlZyAtIDEgOiByZWc7CisgICAgdW5zaWdu ZWQgaW50IHBpbiA9IChyZWcgLSAweDEwKSAvIDI7CiAgICAgaW50IHNhdmVk X21hc2ssIHNlZywgYmRmOwogICAgIHN0cnVjdCBhbWRfaW9tbXUgKmlvbW11 OwogCkBAIC0yMzYsNiArMjQ2LDE0IEBAIHZvaWQgYW1kX2lvbW11X2lvYXBp Y191cGRhdGVfaXJlKAogICAgICAgICAqKCgodTMyICopJm5ld19ydGUpICsg MSkgPSB2YWx1ZTsKICAgICB9CiAKKyAgICBpZiAoIG5ld19ydGUubWFzayAm JgorICAgICAgICAgIXRlc3RfYml0KHBpbiwgaW9hcGljX3NiZGZbSU9fQVBJ Q19JRChhcGljKV0ucGluX3NldHVwKSApCisgICAgeworICAgICAgICBBU1NF UlQoc2F2ZWRfbWFzayk7CisgICAgICAgIF9faW9fYXBpY193cml0ZShhcGlj LCByZWcsIHZhbHVlKTsKKyAgICAgICAgcmV0dXJuOworICAgIH0KKwogICAg IC8qIG1hc2sgdGhlIGludGVycnVwdCB3aGlsZSB3ZSBjaGFuZ2UgdGhlIGlu dHJlbWFwIHRhYmxlICovCiAgICAgaWYgKCAhc2F2ZWRfbWFzayApCiAgICAg ewpAQCAtMjQ0LDcgKzI2MiwxMSBAQCB2b2lkIGFtZF9pb21tdV9pb2FwaWNf dXBkYXRlX2lyZSgKICAgICB9CiAKICAgICAvKiBVcGRhdGUgaW50ZXJydXB0 IHJlbWFwcGluZyBlbnRyeSAqLwotICAgIHVwZGF0ZV9pbnRyZW1hcF9lbnRy eV9mcm9tX2lvYXBpYyhiZGYsIGlvbW11LCAmbmV3X3J0ZSk7CisgICAgdXBk YXRlX2ludHJlbWFwX2VudHJ5X2Zyb21faW9hcGljKAorICAgICAgICBiZGYs IGlvbW11LCAmbmV3X3J0ZSwKKyAgICAgICAgdGVzdF9hbmRfc2V0X2JpdChw aW4sCisgICAgICAgICAgICAgICAgICAgICAgICAgaW9hcGljX3NiZGZbSU9f QVBJQ19JRChhcGljKV0ucGluX3NldHVwKSA/ICZvbGRfcnRlCisgICAgICAg ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg ICAgICAgICAgICAgICA6IE5VTEwpOwogCiAgICAgLyogRm9yd2FyZCB3cml0 ZSBhY2Nlc3MgdG8gSU8tQVBJQyBSVEUgKi8KICAgICBfX2lvX2FwaWNfd3Jp dGUoYXBpYywgcmVnLCB2YWx1ZSk7CkBAIC0zNTQsNiArMzc2LDEyIEBAIHZv aWQgYW1kX2lvbW11X21zaV9tc2dfdXBkYXRlX2lyZSgKICAgICAgICAgcmV0 dXJuOwogICAgIH0KIAorICAgIGlmICggbXNpX2Rlc2MtPnJlbWFwX2luZGV4 ID49IDAgKQorICAgICAgICB1cGRhdGVfaW50cmVtYXBfZW50cnlfZnJvbV9t c2lfbXNnKGlvbW11LCBwZGV2LCBtc2lfZGVzYywgTlVMTCk7CisKKyAgICBp ZiAoICFtc2cgKQorICAgICAgICByZXR1cm47CisKICAgICB1cGRhdGVfaW50 cmVtYXBfZW50cnlfZnJvbV9tc2lfbXNnKGlvbW11LCBwZGV2LCBtc2lfZGVz YywgbXNnKTsKIH0KIAotLS0gYS94ZW4vZHJpdmVycy9wYXNzdGhyb3VnaC9h bWQvcGNpX2FtZF9pb21tdS5jCisrKyBiL3hlbi9kcml2ZXJzL3Bhc3N0aHJv dWdoL2FtZC9wY2lfYW1kX2lvbW11LmMKQEAgLTIwNSw2ICsyMDUsOCBAQCBp bnQgX19pbml0IGFtZF9pb3ZfZGV0ZWN0KHZvaWQpCiAgICAgewogICAgICAg ICBwcmludGsoIkFNRC1WaTogTm90IG92ZXJyaWRpbmcgaXJxX3ZlY3Rvcl9t YXAgc2V0dGluZ1xuIik7CiAgICAgfQorICAgIGlmICggIWFtZF9pb21tdV9w ZXJkZXZfaW50cmVtYXAgKQorICAgICAgICBwcmludGsoWEVOTE9HX1dBUk5J TkcgIkFNRC1WaTogVXNpbmcgZ2xvYmFsIGludGVycnVwdCByZW1hcCB0YWJs ZSBpcyBub3QgcmVjb21tZW5kZWQgKHNlZSBYU0EtMzYpIVxuIik7CiAgICAg cmV0dXJuIHNjYW5fcGNpX2RldmljZXMoKTsKIH0KIAotLS0gYS94ZW4vZHJp dmVycy9wYXNzdGhyb3VnaC9pb21tdS5jCisrKyBiL3hlbi9kcml2ZXJzL3Bh c3N0aHJvdWdoL2lvbW11LmMKQEAgLTUyLDcgKzUyLDcgQEAgYm9vbF90IF9f cmVhZF9tb3N0bHkgaW9tbXVfcWludmFsID0gMTsKIGJvb2xfdCBfX3JlYWRf bW9zdGx5IGlvbW11X2ludHJlbWFwID0gMTsKIGJvb2xfdCBfX3JlYWRfbW9z dGx5IGlvbW11X2hhcF9wdF9zaGFyZSA9IDE7CiBib29sX3QgX19yZWFkX21v c3RseSBpb21tdV9kZWJ1ZzsKLWJvb2xfdCBfX3JlYWRfbW9zdGx5IGFtZF9p b21tdV9wZXJkZXZfaW50cmVtYXA7Citib29sX3QgX19yZWFkX21vc3RseSBh bWRfaW9tbXVfcGVyZGV2X2ludHJlbWFwID0gMTsKIAogREVGSU5FX1BFUl9D UFUoYm9vbF90LCBpb21tdV9kb250X2ZsdXNoX2lvdGxiKTsKIAotLS0gYS94 ZW4vaW5jbHVkZS9hc20teDg2L2h2bS9zdm0vYW1kLWlvbW11LXByb3RvLmgK KysrIGIveGVuL2luY2x1ZGUvYXNtLXg4Ni9odm0vc3ZtL2FtZC1pb21tdS1w cm90by5oCkBAIC0xMDAsNiArMTAwLDcgQEAgdm9pZCBhbWRfaW9tbXVfcmVh ZF9tc2lfZnJvbV9pcmUoCiAKIGV4dGVybiBzdHJ1Y3QgaW9hcGljX3NiZGYg ewogICAgIHUxNiBiZGYsIHNlZzsKKyAgICB1bnNpZ25lZCBsb25nICpwaW5f c2V0dXA7CiB9IGlvYXBpY19zYmRmW01BWF9JT19BUElDU107CiBleHRlcm4g dm9pZCAqc2hhcmVkX2ludHJlbWFwX3RhYmxlOwogCg== --=separator Content-Type: application/octet-stream; name="xsa36-unstable.patch" Content-Disposition: attachment; filename="xsa36-unstable.patch" Content-Transfer-Encoding: base64 QUNQSTogYWNwaV90YWJsZV9wYXJzZSgpIHNob3VsZCByZXR1cm4gaGFuZGxl cidzIGVycm9yIGNvZGUKCkN1cnJlbnRseSwgdGhlIGVycm9yIGNvZGUgcmV0 dXJuZWQgYnkgYWNwaV90YWJsZV9wYXJzZSgpJ3MgaGFuZGxlcgppcyBpZ25v cmVkLiBUaGlzIHBhdGNoIHdpbGwgcHJvcGFnYXRlIGhhbmRsZXIncyByZXR1 cm4gdmFsdWUgdG8KYWNwaV90YWJsZV9wYXJzZSgpJ3MgY2FsbGVyLgoKQU1E LElPTU1VOiBDbGVhbiB1cCBvbGQgZW50cmllcyBpbiByZW1hcHBpbmcgdGFi bGVzIHdoZW4gY3JlYXRpbmcgbmV3CmludGVycnVwdCBtYXBwaW5nLgoKV2hl biBjaGFuZ2luZyB0aGUgYWZmaW5pdHkgb2YgYW4gSVJRIGFzc29jaWF0ZWQg d2l0aCBhIHBhc3NlZAp0aHJvdWdoIFBDSSBkZXZpY2UsIGNsZWFyIHByZXZp b3VzIG1hcHBpbmcuCgpJbiBhZGRpdGlvbiwgYmVjYXVzZSBzb21lIEJJT1Nl cyBtYXkgaW5jb3JyZWN0bHkgcHJvZ3JhbSBJVlJTCmVudHJpZXMgZm9yIElP QVBJQyB0cnkgdG8gY2hlY2sgZm9yIGVudHJ5J3MgY29uc2lzdGVuY3kuIFNw ZWNpZmljYWxseSwKaWYgY29uZmxpY3RpbmcgZW50cmllcyBhcmUgZm91bmQg ZGlzYWJsZSBJT01NVSBpZiBwZXItZGV2aWNlCnJlbWFwcGluZyB0YWJsZSBp cyB1c2VkLiBJZiBlbnRyaWVzIHJlZmVyIHRvIGJvZ3VzIElPQVBJQyBJRHMK ZGlzYWJsZSBJT01NVSB1bmNvbmRpdGlvbmFsbHkKCkFNRCxJT01NVTogRGlz YWJsZSBJT01NVSBpZiBTQVRBIENvbWJpbmVkIG1vZGUgaXMgb24KCkFNRCdz IFNQNTEwMCBjaGlwc2V0IGNhbiBiZSBwbGFjZWQgaW50byBTQVRBIENvbWJp bmVkIG1vZGUKdGhhdCBtYXkgY2F1c2UgcHJldmVudCBkb20wIGZyb20gYm9v dGluZyB3aGVuIElPTU1VIGlzCmVuYWJsZWQgYW5kIHBlci1kZXZpY2UgaW50 ZXJydXB0IHJlbWFwcGluZyB0YWJsZSBpcyB1c2VkLgpXaGlsZSBTUDUxMDAg ZXJyYXR1bSAyOCByZXF1aXJlcyBCSU9TZXMgdG8gZGlzYWJsZSB0aGlzIG1v ZGUsCnNvbWUgbWF5IHN0aWxsIHVzZSBpdC4KClRoaXMgcGF0Y2ggY2hlY2tz IHdoZXRoZXIgdGhpcyBtb2RlIGlzIG9uIGFuZCwgaWYgcGVyLWRldmljZQp0 YWJsZSBpcyBpbiB1c2UsIGRpc2FibGVzIElPTU1VLgoKQU1ELElPTU1VOiBN YWtlIHBlci1kZXZpY2UgaW50ZXJydXB0IHJlbWFwcGluZyB0YWJsZSBkZWZh dWx0CgpVc2luZyBnbG9iYWwgaW50ZXJydXB0IHJlbWFwcGluZyB0YWJsZSBt YXkgYmUgaW5zZWN1cmUsIGFzCmRlc2NyaWJlZCBieSBYU0EtMzYuIFRoaXMg cGF0Y2ggbWFrZXMgcGVyLWRldmljZSBtb2RlIGRlZmF1bHQuCgpUaGlzIGlz IFhTQS0zNiAvIENWRS0yMDEzLTAxNTMuCgpTaWduZWQtb2ZmLWJ5OiBKYW4g QmV1bGljaCA8amJldWxpY2hAc3VzZS5jb20+ClNpZ25lZC1vZmYtYnk6IEJv cmlzIE9zdHJvdnNreSA8Ym9yaXMub3N0cm92c2t5QGFtZC5jb20+CgpBTUQg SU9NTVU6IGFsc28gc3BvdCBtaXNzaW5nIElPLUFQSUMgZW50cmllcyBpbiBJ VlJTIHRhYmxlCgpBcGFydCBmcm9tIGRlYWxpbmcgZHVwbGljYXRlIGNvbmZs aWN0aW5nIGVudHJpZXMsIHdlIGFsc28gaGF2ZSB0bwpoYW5kbGUgZmlybXdh cmUgb21pdHRpbmcgSU8tQVBJQyBlbnRyaWVzIGluIElWUlMgYWx0b2dldGhl ci4gTm90IGRvaW5nCnNvIGhhcyByZXN1bHRlZCBpbiBjL3MgMjY1MTc6NjAx MTM5ZTJiMGRiIHRvIGNyYXNoIHN1Y2ggc3lzdGVtcyBkdXJpbmcKYm9vdCAo d2hlcmVhcyB3aXRoIHRoZSBjaGFuZ2UgaGVyZSB0aGUgSU9NTVUgZ2V0cyBk aXNhYmxlZCBqdXN0IGFzIGlzCmJlaW5nIGRvbmUgaW4gdGhlIG90aGVyIGNh c2VzLCBpLmUuIHVubGVzcyBnbG9iYWwgdGFibGVzIGFyZSBiZWluZwp1c2Vk KS4KCkRlYnVnZ2luZyB0aGlzIGlzc3VlIGhhcyBhbHNvIHBvaW50ZWQgb3V0 IHRoYXQgdGhlIGRlYnVnIGxvZyBvdXRwdXQgaXMKcHJldHR5IHVnbHkgdG8g bG9vayBhdCAtIGNvbnNvbGlkYXRlIHRoZSBvdXRwdXQsIGFuZCBhZGQgb25l IGV4dHJhCml0ZW0gZm9yIHRoZSBJVkhEIHNwZWNpYWwgZW50cmllcywgc28g dGhhdCBmdXR1cmUgaXNzdWVzIGFyZSBlYXNpZXIKdG8gYW5hbHl6ZS4KClNp Z25lZC1vZmYtYnk6IEphbiBCZXVsaWNoIDxqYmV1bGljaEBzdXNlLmNvbT4K VGVzdGVkLWJ5OiBTYW5kZXIgRWlrZWxlbmJvb20gPGxpbnV4QGVpa2VsZW5i b29tLml0PgoKLS0tIGEveGVuL2FyY2gveDg2L2lycS5jCisrKyBiL3hlbi9h cmNoL3g4Ni9pcnEuYwpAQCAtMTk0Myw5ICsxOTQzLDYgQEAgaW50IG1hcF9k b21haW5fcGlycSgKICAgICAgICAgc3Bpbl9sb2NrX2lycXNhdmUoJmRlc2Mt PmxvY2ssIGZsYWdzKTsKICAgICAgICAgc2V0X2RvbWFpbl9pcnFfcGlycShk LCBpcnEsIGluZm8pOwogICAgICAgICBzcGluX3VubG9ja19pcnFyZXN0b3Jl KCZkZXNjLT5sb2NrLCBmbGFncyk7Ci0KLSAgICAgICAgaWYgKCBvcHRfaXJx X3ZlY3Rvcl9tYXAgPT0gT1BUX0lSUV9WRUNUT1JfTUFQX1BFUkRFViApCi0g ICAgICAgICAgICBwcmludGsoWEVOTE9HX0lORk8gIlBlci1kZXZpY2UgdmVj dG9yIG1hcHMgZm9yIEdTSXMgbm90IGltcGxlbWVudGVkIHlldC5cbiIpOwog ICAgIH0KIAogZG9uZToKLS0tIGEveGVuL2RyaXZlcnMvYWNwaS90YWJsZXMu YworKysgYi94ZW4vZHJpdmVycy9hY3BpL3RhYmxlcy5jCkBAIC0yNjUsNyAr MjY1LDcgQEAgYWNwaV90YWJsZV9wYXJzZV9tYWR0KGVudW0gYWNwaV9tYWR0 X3R5cAogICogQGhhbmRsZXI6IGhhbmRsZXIgdG8gcnVuCiAgKgogICogU2Nh biB0aGUgQUNQSSBTeXN0ZW0gRGVzY3JpcHRvciBUYWJsZSAoU1REKSBmb3Ig YSB0YWJsZSBtYXRjaGluZyBAaWQsCi0gKiBydW4gQGhhbmRsZXIgb24gaXQu ICBSZXR1cm4gMCBpZiB0YWJsZSBmb3VuZCwgcmV0dXJuIG9uIGlmIG5vdC4K KyAqIHJ1biBAaGFuZGxlciBvbiBpdC4KICAqLwogaW50IF9faW5pdCBhY3Bp X3RhYmxlX3BhcnNlKGNoYXIgKmlkLCBhY3BpX3RhYmxlX2hhbmRsZXIgaGFu ZGxlcikKIHsKQEAgLTI4MCw4ICsyODAsNyBAQCBpbnQgX19pbml0IGFjcGlf dGFibGVfcGFyc2UoY2hhciAqaWQsIGFjCiAJCWFjcGlfZ2V0X3RhYmxlKGlk LCAwLCAmdGFibGUpOwogCiAJaWYgKHRhYmxlKSB7Ci0JCWhhbmRsZXIodGFi bGUpOwotCQlyZXR1cm4gMDsKKwkJcmV0dXJuIGhhbmRsZXIodGFibGUpOwog CX0gZWxzZQogCQlyZXR1cm4gMTsKIH0KLS0tIGEveGVuL2RyaXZlcnMvcGFz c3Rocm91Z2gvYW1kL2lvbW11X2FjcGkuYworKysgYi94ZW4vZHJpdmVycy9w YXNzdGhyb3VnaC9hbWQvaW9tbXVfYWNwaS5jCkBAIC0yMiw2ICsyMiw3IEBA CiAjaW5jbHVkZSA8eGVuL2Vycm5vLmg+CiAjaW5jbHVkZSA8eGVuL2FjcGku aD4KICNpbmNsdWRlIDxhc20vYXBpY2RlZi5oPgorI2luY2x1ZGUgPGFzbS9p b19hcGljLmg+CiAjaW5jbHVkZSA8YXNtL2FtZC1pb21tdS5oPgogI2luY2x1 ZGUgPGFzbS9odm0vc3ZtL2FtZC1pb21tdS1wcm90by5oPgogCkBAIC02Mzcs NiArNjM4LDcgQEAgc3RhdGljIHUxNiBfX2luaXQgcGFyc2VfaXZoZF9kZXZp Y2Vfc3BlYwogICAgIHUxNiBoZWFkZXJfbGVuZ3RoLCB1MTYgYmxvY2tfbGVu Z3RoLCBzdHJ1Y3QgYW1kX2lvbW11ICppb21tdSkKIHsKICAgICB1MTYgZGV2 X2xlbmd0aCwgYmRmOworICAgIGludCBhcGljOwogCiAgICAgZGV2X2xlbmd0 aCA9IHNpemVvZigqc3BlY2lhbCk7CiAgICAgaWYgKCBoZWFkZXJfbGVuZ3Ro IDwgKGJsb2NrX2xlbmd0aCArIGRldl9sZW5ndGgpICkKQEAgLTY1Nyw5ICs2 NTksNTMgQEAgc3RhdGljIHUxNiBfX2luaXQgcGFyc2VfaXZoZF9kZXZpY2Vf c3BlYwogICAgIHN3aXRjaCAoIHNwZWNpYWwtPnZhcmlldHkgKQogICAgIHsK ICAgICBjYXNlIEFDUElfSVZIRF9JT0FQSUM6Ci0gICAgLyogc2V0IGRldmlj ZSBpZCBvZiBpb2FwaWMgKi8KLSAgICAgICAgaW9hcGljX3NiZGZbc3BlY2lh bC0+aGFuZGxlXS5iZGYgPSBiZGY7Ci0gICAgICAgIGlvYXBpY19zYmRmW3Nw ZWNpYWwtPmhhbmRsZV0uc2VnID0gc2VnOworICAgICAgICAvKgorICAgICAg ICAgKiBTb21lIEJJT1NlcyBoYXZlIElPQVBJQyBicm9rZW4gZW50cmllcyBz byB3ZSBjaGVjayBmb3IgSVZSUworICAgICAgICAgKiBjb25zaXN0ZW5jeSBo ZXJlIC0tLSB3aGV0aGVyIGVudHJ5J3MgSU9BUElDIElEIGlzIHZhbGlkIGFu ZAorICAgICAgICAgKiB3aGV0aGVyIHRoZXJlIGFyZSBjb25mbGljdGluZy9k dXBsaWNhdGVkIGVudHJpZXMuCisgICAgICAgICAqLworICAgICAgICBmb3Ig KCBhcGljID0gMDsgYXBpYyA8IG5yX2lvYXBpY3M7IGFwaWMrKyApCisgICAg ICAgIHsKKyAgICAgICAgICAgIGlmICggSU9fQVBJQ19JRChhcGljKSAhPSBz cGVjaWFsLT5oYW5kbGUgKQorICAgICAgICAgICAgICAgIGNvbnRpbnVlOwor CisgICAgICAgICAgICBpZiAoIGlvYXBpY19zYmRmW3NwZWNpYWwtPmhhbmRs ZV0ucGluX3NldHVwICkKKyAgICAgICAgICAgIHsKKyAgICAgICAgICAgICAg ICBpZiAoIGlvYXBpY19zYmRmW3NwZWNpYWwtPmhhbmRsZV0uYmRmID09IGJk ZiAmJgorICAgICAgICAgICAgICAgICAgICAgaW9hcGljX3NiZGZbc3BlY2lh bC0+aGFuZGxlXS5zZWcgPT0gc2VnICkKKyAgICAgICAgICAgICAgICAgICAg QU1EX0lPTU1VX0RFQlVHKCJJVkhEIFdhcm5pbmc6IER1cGxpY2F0ZSBJTy1B UElDICUjeCBlbnRyaWVzXG4iLAorICAgICAgICAgICAgICAgICAgICAgICAg ICAgICAgICAgICAgc3BlY2lhbC0+aGFuZGxlKTsKKyAgICAgICAgICAgICAg ICBlbHNlCisgICAgICAgICAgICAgICAgeworICAgICAgICAgICAgICAgICAg ICBwcmludGsoWEVOTE9HX0VSUiAiSVZIRCBFcnJvcjogQ29uZmxpY3Rpbmcg SU8tQVBJQyAlI3ggZW50cmllc1xuIiwKKyAgICAgICAgICAgICAgICAgICAg ICAgICAgIHNwZWNpYWwtPmhhbmRsZSk7CisgICAgICAgICAgICAgICAgICAg IGlmICggYW1kX2lvbW11X3BlcmRldl9pbnRyZW1hcCApCisgICAgICAgICAg ICAgICAgICAgICAgICByZXR1cm4gMDsKKyAgICAgICAgICAgICAgICB9Cisg ICAgICAgICAgICB9CisgICAgICAgICAgICBlbHNlCisgICAgICAgICAgICB7 CisgICAgICAgICAgICAgICAgLyogc2V0IGRldmljZSBpZCBvZiBpb2FwaWMg Ki8KKyAgICAgICAgICAgICAgICBpb2FwaWNfc2JkZltzcGVjaWFsLT5oYW5k bGVdLmJkZiA9IGJkZjsKKyAgICAgICAgICAgICAgICBpb2FwaWNfc2JkZltz cGVjaWFsLT5oYW5kbGVdLnNlZyA9IHNlZzsKKworICAgICAgICAgICAgICAg IGlvYXBpY19zYmRmW3NwZWNpYWwtPmhhbmRsZV0ucGluX3NldHVwID0geHph bGxvY19hcnJheSgKKyAgICAgICAgICAgICAgICAgICAgdW5zaWduZWQgbG9u ZywgQklUU19UT19MT05HUyhucl9pb2FwaWNfZW50cmllc1thcGljXSkpOwor ICAgICAgICAgICAgICAgIGlmICggbnJfaW9hcGljX2VudHJpZXNbYXBpY10g JiYKKyAgICAgICAgICAgICAgICAgICAgICFpb2FwaWNfc2JkZltJT19BUElD X0lEKGFwaWMpXS5waW5fc2V0dXAgKQorICAgICAgICAgICAgICAgIHsKKyAg ICAgICAgICAgICAgICAgICAgcHJpbnRrKFhFTkxPR19FUlIgIklWSEQgRXJy b3I6IE91dCBvZiBtZW1vcnlcbiIpOworICAgICAgICAgICAgICAgICAgICBy ZXR1cm4gMDsKKyAgICAgICAgICAgICAgICB9CisgICAgICAgICAgICB9Cisg ICAgICAgICAgICBicmVhazsKKyAgICAgICAgfQorICAgICAgICBpZiAoIGFw aWMgPT0gbnJfaW9hcGljcyApCisgICAgICAgIHsKKyAgICAgICAgICAgIHBy aW50ayhYRU5MT0dfRVJSICJJVkhEIEVycm9yOiBJbnZhbGlkIElPLUFQSUMg JSN4XG4iLAorICAgICAgICAgICAgICAgICAgIHNwZWNpYWwtPmhhbmRsZSk7 CisgICAgICAgICAgICByZXR1cm4gMDsKKyAgICAgICAgfQogICAgICAgICBi cmVhazsKICAgICBjYXNlIEFDUElfSVZIRF9IUEVUOgogICAgICAgICAvKiBz ZXQgZGV2aWNlIGlkIG9mIGhwZXQgKi8KQEAgLTg0NCw2ICs4OTAsNyBAQCBz dGF0aWMgaW50IF9faW5pdCBwYXJzZV9pdnJzX3RhYmxlKHN0cnVjCiB7CiAg ICAgY29uc3Qgc3RydWN0IGFjcGlfaXZyc19oZWFkZXIgKml2cnNfYmxvY2s7 CiAgICAgdW5zaWduZWQgbG9uZyBsZW5ndGg7CisgICAgdW5zaWduZWQgaW50 IGFwaWM7CiAgICAgaW50IGVycm9yID0gMDsKIAogICAgIEJVR19PTighdGFi bGUpOwpAQCAtODc2LDYgKzkyMywyOSBAQCBzdGF0aWMgaW50IF9faW5pdCBw YXJzZV9pdnJzX3RhYmxlKHN0cnVjCiAgICAgICAgIGxlbmd0aCArPSBpdnJz X2Jsb2NrLT5sZW5ndGg7CiAgICAgfQogCisgICAgLyogRWFjaCBJTy1BUElD IG11c3QgaGF2ZSBiZWVuIG1lbnRpb25lZCBpbiB0aGUgdGFibGUuICovCisg ICAgZm9yICggYXBpYyA9IDA7ICFlcnJvciAmJiBhcGljIDwgbnJfaW9hcGlj czsgKythcGljICkKKyAgICB7CisgICAgICAgIGlmICggIW5yX2lvYXBpY19l bnRyaWVzW2FwaWNdIHx8CisgICAgICAgICAgICAgaW9hcGljX3NiZGZbSU9f QVBJQ19JRChhcGljKV0ucGluX3NldHVwICkKKyAgICAgICAgICAgIGNvbnRp bnVlOworCisgICAgICAgIHByaW50ayhYRU5MT0dfRVJSICJJVkhEIEVycm9y OiBubyBpbmZvcm1hdGlvbiBmb3IgSU8tQVBJQyAlI3hcbiIsCisgICAgICAg ICAgICAgICBJT19BUElDX0lEKGFwaWMpKTsKKyAgICAgICAgaWYgKCBhbWRf aW9tbXVfcGVyZGV2X2ludHJlbWFwICkKKyAgICAgICAgICAgIGVycm9yID0g LUVOWElPOworICAgICAgICBlbHNlCisgICAgICAgIHsKKyAgICAgICAgICAg IGlvYXBpY19zYmRmW0lPX0FQSUNfSUQoYXBpYyldLnBpbl9zZXR1cCA9IHh6 YWxsb2NfYXJyYXkoCisgICAgICAgICAgICAgICAgdW5zaWduZWQgbG9uZywg QklUU19UT19MT05HUyhucl9pb2FwaWNfZW50cmllc1thcGljXSkpOworICAg ICAgICAgICAgaWYgKCAhaW9hcGljX3NiZGZbSU9fQVBJQ19JRChhcGljKV0u cGluX3NldHVwICkKKyAgICAgICAgICAgIHsKKyAgICAgICAgICAgICAgICBw cmludGsoWEVOTE9HX0VSUiAiSVZIRCBFcnJvcjogT3V0IG9mIG1lbW9yeVxu Iik7CisgICAgICAgICAgICAgICAgZXJyb3IgPSAtRU5PTUVNOworICAgICAg ICAgICAgfQorICAgICAgICB9CisgICAgfQorCiAgICAgcmV0dXJuIGVycm9y OwogfQogCi0tLSBhL3hlbi9kcml2ZXJzL3Bhc3N0aHJvdWdoL2FtZC9pb21t dV9pbml0LmMKKysrIGIveGVuL2RyaXZlcnMvcGFzc3Rocm91Z2gvYW1kL2lv bW11X2luaXQuYwpAQCAtMTEyMCwxMiArMTEyMCw0NSBAQCBzdGF0aWMgaW50 IF9faW5pdCBhbWRfaW9tbXVfc2V0dXBfZGV2aWNlCiAgICAgcmV0dXJuIDA7 CiB9CiAKKy8qIENoZWNrIHdoZXRoZXIgU1A1MTAwIFNBVEEgQ29tYmluZWQg bW9kZSBpcyBvbiAqLworc3RhdGljIGJvb2xfdCBfX2luaXQgYW1kX3NwNTEw MF9lcnJhdHVtMjgodm9pZCkKK3sKKyAgICB1MzIgYnVzLCBpZDsKKyAgICB1 MTYgdmVuZG9yX2lkLCBkZXZfaWQ7CisgICAgdTggYnl0ZTsKKworICAgIGZv ciAoYnVzID0gMDsgYnVzIDwgMjU2OyBidXMrKykKKyAgICB7CisgICAgICAg IGlkID0gcGNpX2NvbmZfcmVhZDMyKDAsIGJ1cywgMHgxNCwgMCwgUENJX1ZF TkRPUl9JRCk7CisKKyAgICAgICAgdmVuZG9yX2lkID0gaWQgJiAweGZmZmY7 CisgICAgICAgIGRldl9pZCA9IChpZCA+PiAxNikgJiAweGZmZmY7CisKKyAg ICAgICAgLyogU1A1MTAwIFNNQnVzIG1vZHVsZSBzZXRzIENvbWJpbmVkIG1v ZGUgb24gKi8KKyAgICAgICAgaWYgKHZlbmRvcl9pZCAhPSAweDEwMDIgfHwg ZGV2X2lkICE9IDB4NDM4NSkKKyAgICAgICAgICAgIGNvbnRpbnVlOworCisg ICAgICAgIGJ5dGUgPSBwY2lfY29uZl9yZWFkOCgwLCBidXMsIDB4MTQsIDAs IDB4YWQpOworICAgICAgICBpZiAoIChieXRlID4+IDMpICYgMSApCisgICAg ICAgIHsKKyAgICAgICAgICAgIHByaW50ayhYRU5MT0dfV0FSTklORyAiQU1E LVZpOiBTUDUxMDAgZXJyYXR1bSAyOCBkZXRlY3RlZCwgZGlzYWJsaW5nIElP TU1VLlxuIgorICAgICAgICAgICAgICAgICAgICJJZiBwb3NzaWJsZSwgZGlz YWJsZSBTQVRBIENvbWJpbmVkIG1vZGUgaW4gQklPUyBvciBjb250YWN0IHlv dXIgdmVuZG9yIGZvciBCSU9TIHVwZGF0ZS5cbiIpOworICAgICAgICAgICAg cmV0dXJuIDE7CisgICAgICAgIH0KKyAgICB9CisKKyAgICByZXR1cm4gMDsK K30KKwogaW50IF9faW5pdCBhbWRfaW9tbXVfaW5pdCh2b2lkKQogewogICAg IHN0cnVjdCBhbWRfaW9tbXUgKmlvbW11OwogCiAgICAgQlVHX09OKCAhaW9t bXVfZm91bmQoKSApOwogCisgICAgaWYgKCBhbWRfaW9tbXVfcGVyZGV2X2lu dHJlbWFwICYmIGFtZF9zcDUxMDBfZXJyYXR1bTI4KCkgKQorICAgICAgICBn b3RvIGVycm9yX291dDsKKwogICAgIGl2cnNfYmRmX2VudHJpZXMgPSBhbWRf aW9tbXVfZ2V0X2l2cnNfZGV2X2VudHJpZXMoKTsKIAogICAgIGlmICggIWl2 cnNfYmRmX2VudHJpZXMgKQotLS0gYS94ZW4vZHJpdmVycy9wYXNzdGhyb3Vn aC9hbWQvaW9tbXVfaW50ci5jCisrKyBiL3hlbi9kcml2ZXJzL3Bhc3N0aHJv dWdoL2FtZC9pb21tdV9pbnRyLmMKQEAgLTEwMCwxMiArMTAwLDEyIEBAIHN0 YXRpYyB2b2lkIHVwZGF0ZV9pbnRyZW1hcF9lbnRyeSh1MzIqIGUKIHN0YXRp YyB2b2lkIHVwZGF0ZV9pbnRyZW1hcF9lbnRyeV9mcm9tX2lvYXBpYygKICAg ICBpbnQgYmRmLAogICAgIHN0cnVjdCBhbWRfaW9tbXUgKmlvbW11LAotICAg IHN0cnVjdCBJT19BUElDX3JvdXRlX2VudHJ5ICppb2FwaWNfcnRlKQorICAg IGNvbnN0IHN0cnVjdCBJT19BUElDX3JvdXRlX2VudHJ5ICpydGUsCisgICAg Y29uc3Qgc3RydWN0IElPX0FQSUNfcm91dGVfZW50cnkgKm9sZF9ydGUpCiB7 CiAgICAgdW5zaWduZWQgbG9uZyBmbGFnczsKICAgICB1MzIqIGVudHJ5Owog ICAgIHU4IGRlbGl2ZXJ5X21vZGUsIGRlc3QsIHZlY3RvciwgZGVzdF9tb2Rl OwotICAgIHN0cnVjdCBJT19BUElDX3JvdXRlX2VudHJ5ICpydGUgPSBpb2Fw aWNfcnRlOwogICAgIGludCByZXFfaWQ7CiAgICAgc3BpbmxvY2tfdCAqbG9j azsKICAgICBpbnQgb2Zmc2V0OwpAQCAtMTIxLDYgKzEyMSwxNCBAQCBzdGF0 aWMgdm9pZCB1cGRhdGVfaW50cmVtYXBfZW50cnlfZnJvbV9pCiAgICAgc3Bp bl9sb2NrX2lycXNhdmUobG9jaywgZmxhZ3MpOwogCiAgICAgb2Zmc2V0ID0g Z2V0X2ludHJlbWFwX29mZnNldCh2ZWN0b3IsIGRlbGl2ZXJ5X21vZGUpOwor ICAgIGlmICggb2xkX3J0ZSApCisgICAgeworICAgICAgICBpbnQgb2xkX29m ZnNldCA9IGdldF9pbnRyZW1hcF9vZmZzZXQob2xkX3J0ZS0+dmVjdG9yLAor ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg b2xkX3J0ZS0+ZGVsaXZlcnlfbW9kZSk7CisKKyAgICAgICAgaWYgKCBvZmZz ZXQgIT0gb2xkX29mZnNldCApCisgICAgICAgICAgICBmcmVlX2ludHJlbWFw X2VudHJ5KGlvbW11LT5zZWcsIGJkZiwgb2xkX29mZnNldCk7CisgICAgfQog ICAgIGVudHJ5ID0gKHUzMiopZ2V0X2ludHJlbWFwX2VudHJ5KGlvbW11LT5z ZWcsIHJlcV9pZCwgb2Zmc2V0KTsKICAgICB1cGRhdGVfaW50cmVtYXBfZW50 cnkoZW50cnksIHZlY3RvciwgZGVsaXZlcnlfbW9kZSwgZGVzdF9tb2RlLCBk ZXN0KTsKIApAQCAtMTg5LDYgKzE5Nyw3IEBAIGludCBfX2luaXQgYW1kX2lv bW11X3NldHVwX2lvYXBpY19yZW1hcHAKICAgICAgICAgICAgICAgICBhbWRf aW9tbXVfZmx1c2hfaW50cmVtYXAoaW9tbXUsIHJlcV9pZCk7CiAgICAgICAg ICAgICAgICAgc3Bpbl91bmxvY2tfaXJxcmVzdG9yZSgmaW9tbXUtPmxvY2ss IGZsYWdzKTsKICAgICAgICAgICAgIH0KKyAgICAgICAgICAgIHNldF9iaXQo cGluLCBpb2FwaWNfc2JkZltJT19BUElDX0lEKGFwaWMpXS5waW5fc2V0dXAp OwogICAgICAgICB9CiAgICAgfQogICAgIHJldHVybiAwOwpAQCAtMjAwLDYg KzIwOSw3IEBAIHZvaWQgYW1kX2lvbW11X2lvYXBpY191cGRhdGVfaXJlKAog ICAgIHN0cnVjdCBJT19BUElDX3JvdXRlX2VudHJ5IG9sZF9ydGUgPSB7IDAg fTsKICAgICBzdHJ1Y3QgSU9fQVBJQ19yb3V0ZV9lbnRyeSBuZXdfcnRlID0g eyAwIH07CiAgICAgdW5zaWduZWQgaW50IHJ0ZV9sbyA9IChyZWcgJiAxKSA/ IHJlZyAtIDEgOiByZWc7CisgICAgdW5zaWduZWQgaW50IHBpbiA9IChyZWcg LSAweDEwKSAvIDI7CiAgICAgaW50IHNhdmVkX21hc2ssIHNlZywgYmRmOwog ICAgIHN0cnVjdCBhbWRfaW9tbXUgKmlvbW11OwogCkBAIC0yMzcsNiArMjQ3 LDE0IEBAIHZvaWQgYW1kX2lvbW11X2lvYXBpY191cGRhdGVfaXJlKAogICAg ICAgICAqKCgodTMyICopJm5ld19ydGUpICsgMSkgPSB2YWx1ZTsKICAgICB9 CiAKKyAgICBpZiAoIG5ld19ydGUubWFzayAmJgorICAgICAgICAgIXRlc3Rf Yml0KHBpbiwgaW9hcGljX3NiZGZbSU9fQVBJQ19JRChhcGljKV0ucGluX3Nl dHVwKSApCisgICAgeworICAgICAgICBBU1NFUlQoc2F2ZWRfbWFzayk7Cisg ICAgICAgIF9faW9fYXBpY193cml0ZShhcGljLCByZWcsIHZhbHVlKTsKKyAg ICAgICAgcmV0dXJuOworICAgIH0KKwogICAgIC8qIG1hc2sgdGhlIGludGVy cnVwdCB3aGlsZSB3ZSBjaGFuZ2UgdGhlIGludHJlbWFwIHRhYmxlICovCiAg ICAgaWYgKCAhc2F2ZWRfbWFzayApCiAgICAgewpAQCAtMjQ1LDcgKzI2Mywx MSBAQCB2b2lkIGFtZF9pb21tdV9pb2FwaWNfdXBkYXRlX2lyZSgKICAgICB9 CiAKICAgICAvKiBVcGRhdGUgaW50ZXJydXB0IHJlbWFwcGluZyBlbnRyeSAq LwotICAgIHVwZGF0ZV9pbnRyZW1hcF9lbnRyeV9mcm9tX2lvYXBpYyhiZGYs IGlvbW11LCAmbmV3X3J0ZSk7CisgICAgdXBkYXRlX2ludHJlbWFwX2VudHJ5 X2Zyb21faW9hcGljKAorICAgICAgICBiZGYsIGlvbW11LCAmbmV3X3J0ZSwK KyAgICAgICAgdGVzdF9hbmRfc2V0X2JpdChwaW4sCisgICAgICAgICAgICAg ICAgICAgICAgICAgaW9hcGljX3NiZGZbSU9fQVBJQ19JRChhcGljKV0ucGlu X3NldHVwKSA/ICZvbGRfcnRlCisgICAgICAgICAgICAgICAgICAgICAgICAg ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICA6IE5V TEwpOwogCiAgICAgLyogRm9yd2FyZCB3cml0ZSBhY2Nlc3MgdG8gSU8tQVBJ QyBSVEUgKi8KICAgICBfX2lvX2FwaWNfd3JpdGUoYXBpYywgcmVnLCB2YWx1 ZSk7CkBAIC0zNTYsNiArMzc4LDEyIEBAIHZvaWQgYW1kX2lvbW11X21zaV9t c2dfdXBkYXRlX2lyZSgKICAgICAgICAgcmV0dXJuOwogICAgIH0KIAorICAg IGlmICggbXNpX2Rlc2MtPnJlbWFwX2luZGV4ID49IDAgKQorICAgICAgICB1 cGRhdGVfaW50cmVtYXBfZW50cnlfZnJvbV9tc2lfbXNnKGlvbW11LCBiZGYs IG1zaV9kZXNjLCBOVUxMKTsKKworICAgIGlmICggIW1zZyApCisgICAgICAg IHJldHVybjsKKwogICAgIHVwZGF0ZV9pbnRyZW1hcF9lbnRyeV9mcm9tX21z aV9tc2coaW9tbXUsIGJkZiwgbXNpX2Rlc2MsIG1zZyk7CiB9CiAKLS0tIGEv eGVuL2RyaXZlcnMvcGFzc3Rocm91Z2gvYW1kL3BjaV9hbWRfaW9tbXUuYwor KysgYi94ZW4vZHJpdmVycy9wYXNzdGhyb3VnaC9hbWQvcGNpX2FtZF9pb21t dS5jCkBAIC0yMDgsNiArMjA4LDggQEAgaW50IF9faW5pdCBhbWRfaW92X2Rl dGVjdCh2b2lkKQogICAgIHsKICAgICAgICAgcHJpbnRrKCJBTUQtVmk6IE5v dCBvdmVycmlkaW5nIGlycV92ZWN0b3JfbWFwIHNldHRpbmdcbiIpOwogICAg IH0KKyAgICBpZiAoICFhbWRfaW9tbXVfcGVyZGV2X2ludHJlbWFwICkKKyAg ICAgICAgcHJpbnRrKFhFTkxPR19XQVJOSU5HICJBTUQtVmk6IFVzaW5nIGds b2JhbCBpbnRlcnJ1cHQgcmVtYXAgdGFibGUgaXMgbm90IHJlY29tbWVuZGVk IChzZWUgWFNBLTM2KSFcbiIpOwogICAgIHJldHVybiBzY2FuX3BjaV9kZXZp Y2VzKCk7CiB9CiAKLS0tIGEveGVuL2RyaXZlcnMvcGFzc3Rocm91Z2gvaW9t bXUuYworKysgYi94ZW4vZHJpdmVycy9wYXNzdGhyb3VnaC9pb21tdS5jCkBA IC01Myw3ICs1Myw3IEBAIGJvb2xfdCBfX3JlYWRfbW9zdGx5IGlvbW11X3Fp bnZhbCA9IDE7CiBib29sX3QgX19yZWFkX21vc3RseSBpb21tdV9pbnRyZW1h cCA9IDE7CiBib29sX3QgX19yZWFkX21vc3RseSBpb21tdV9oYXBfcHRfc2hh cmUgPSAxOwogYm9vbF90IF9fcmVhZF9tb3N0bHkgaW9tbXVfZGVidWc7Ci1i b29sX3QgX19yZWFkX21vc3RseSBhbWRfaW9tbXVfcGVyZGV2X2ludHJlbWFw OworYm9vbF90IF9fcmVhZF9tb3N0bHkgYW1kX2lvbW11X3BlcmRldl9pbnRy ZW1hcCA9IDE7CiAKIERFRklORV9QRVJfQ1BVKGJvb2xfdCwgaW9tbXVfZG9u dF9mbHVzaF9pb3RsYik7CiAKLS0tIGEveGVuL2luY2x1ZGUvYXNtLXg4Ni9o dm0vc3ZtL2FtZC1pb21tdS1wcm90by5oCisrKyBiL3hlbi9pbmNsdWRlL2Fz bS14ODYvaHZtL3N2bS9hbWQtaW9tbXUtcHJvdG8uaApAQCAtMTAxLDYgKzEw MSw3IEBAIGludCBhbWRfc2V0dXBfaHBldF9tc2koc3RydWN0IG1zaV9kZXNj ICoKIAogZXh0ZXJuIHN0cnVjdCBpb2FwaWNfc2JkZiB7CiAgICAgdTE2IGJk Ziwgc2VnOworICAgIHVuc2lnbmVkIGxvbmcgKnBpbl9zZXR1cDsKIH0gaW9h cGljX3NiZGZbTUFYX0lPX0FQSUNTXTsKIGV4dGVybiB2b2lkICpzaGFyZWRf aW50cmVtYXBfdGFibGU7CiAK --=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 Feb 21 14:41:24 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 21 Feb 2013 14:41: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 1U8XK5-0005vf-MY; Thu, 21 Feb 2013 14:40:33 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U8XK3-0005vY-Kc for xen-users@lists.xen.org; Thu, 21 Feb 2013 14:40:31 +0000 Received: from [85.158.138.51:47278] by server-9.bemta-3.messagelabs.com id E5/3C-09484-ED136215; Thu, 21 Feb 2013 14:40:30 +0000 X-Env-Sender: cdelorme@gmail.com X-Msg-Ref: server-2.tower-174.messagelabs.com!1361457620!27530666!1 X-Originating-IP: [209.85.212.50] X-SpamReason: No, hits=0.9 required=7.0 tests=HTML_40_50,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14, ML_RADAR_SPEW_LINKS_32, RCVD_BY_IP, spamassassin: X-StarScan-Received: X-StarScan-Version: 6.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 28778 invoked from network); 21 Feb 2013 14:40:21 -0000 Received: from mail-vb0-f50.google.com (HELO mail-vb0-f50.google.com) (209.85.212.50) by server-2.tower-174.messagelabs.com with RC4-SHA encrypted SMTP; 21 Feb 2013 14:40:21 -0000 Received: by mail-vb0-f50.google.com with SMTP id ft2so5709275vbb.37 for ; Thu, 21 Feb 2013 06:40:18 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=ACbYBfg1N6mxAbIqyzIAoZiPiOzJH4f0JyaVHAPiObo=; b=gCFhFubu9hh1QIx3e2hhODXAE0XoaxZqcy30tsM6Gx2L7+PZgZ1Xil70XZAGpiRBtZ nwHyWBvjQUGeDHJodhjnhfykWFoz8QcGNLOExiJFUgoG4QkwbCj6FRhNSJt1TYsv8vwC tbubTyMOqPbW2euRHtpsizUEaOFVTpdxz2cNEBPQkJyZ4nCfUy5K+TvBs2Hi7eUrgA9i j7L5Lvy/fVeZXTB26rBlN5oC/WIDq9Qxlv6OSOtE8MLQplKsglkDOdbvbHIM0Piiuf2W rnN2Q4iw/SKcc5jCul0qWvH7hRwKmT3CmOJz69bRpfkhY8TKBsujZlq8T3Mt1AwUj4tr 3Wkg== MIME-Version: 1.0 X-Received: by 10.52.38.234 with SMTP id j10mr28138717vdk.0.1361457618354; Thu, 21 Feb 2013 06:40:18 -0800 (PST) Received: by 10.58.32.199 with HTTP; Thu, 21 Feb 2013 06:40:18 -0800 (PST) In-Reply-To: References: Date: Thu, 21 Feb 2013 09:40:18 -0500 Message-ID: From: Casey DeLorme To: Krishan Sethi Cc: "xen-users@lists.xen.org" Subject: Re: [Xen-users] Regarding Xen installation X-BeenThere: xen-users@lists.xen.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="===============2041387132666880338==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============2041387132666880338== Content-Type: multipart/alternative; boundary=bcaec51d27f6b801bb04d63d0d92 --bcaec51d27f6b801bb04d63d0d92 Content-Type: text/plain; charset=UTF-8 Hello Krishan, Glad to see a fellow student researcher. > Now i want to load the DomU by xen-tools. but it's not happening. > Not to deter you from getting answers here, but the xen-tools package is maintained by a different team with their own mailing list and may be better equipped to help. You can find there lists here: http://xen-tools.org/software/xen-tools/lists.html > Can anybody tell me the actual and detailed procedure to load domU by > xen-tools. > The website for xen-tools did not specify which version of Xen the xen-tools package is compatible with, and given that the current release of Ubuntu does not have a Xen 4.2 package it is very possible that xen-tools will not work as expected. http://packages.ubuntu.com/search?keywords=xen&searchon=names My understanding is it just simplifies the creation of domain configuration files using Perl scripts to accept input. My advice would be to read the Xen 4.2 Man Pages, as these configuration files can easily be created in a text editor and run using the toolstack that comes with xen: http://wiki.xen.org/wiki/Xen_4.2_Man_Pages http://xenbits.xen.org/docs/4.2-testing/man/xl.cfg.5.html ~Casey --bcaec51d27f6b801bb04d63d0d92 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

Hello Krishan,

G= lad to see a fellow student researcher.
=C2=A0
Now i want to load the DomU by xen-tools. but it's not= happening.

Not to deter you= from getting answers here, but the xen-tools package is maintained by a di= fferent team with their own mailing list and may be better equipped to help= . =C2=A0You can find there lists here:

= =C2=A0
Can anybody tell me the actual and detailed pro= cedure to load domU by xen-tools.

The website for xen-tools did not specify which version of Xen the xen-to= ols package is compatible with, and given that the current release of Ubunt= u does not have a Xen 4.2 package it is very possible that xen-tools will n= ot work as expected.



My understanding is it just simplifies the creation of domain configur= ation files using Perl scripts to accept input. =C2=A0My advice would be to= read the Xen 4.2 Man Pages, as these configuration files can easily be cre= ated in a text editor and run using the toolstack that comes with xen:


~Casey

--bcaec51d27f6b801bb04d63d0d92-- --===============2041387132666880338== 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 --===============2041387132666880338==-- From xen-users-bounces@lists.xen.org Thu Feb 21 14:41:24 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 21 Feb 2013 14:41: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 1U8XK5-0005vf-MY; Thu, 21 Feb 2013 14:40:33 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U8XK3-0005vY-Kc for xen-users@lists.xen.org; Thu, 21 Feb 2013 14:40:31 +0000 Received: from [85.158.138.51:47278] by server-9.bemta-3.messagelabs.com id E5/3C-09484-ED136215; Thu, 21 Feb 2013 14:40:30 +0000 X-Env-Sender: cdelorme@gmail.com X-Msg-Ref: server-2.tower-174.messagelabs.com!1361457620!27530666!1 X-Originating-IP: [209.85.212.50] X-SpamReason: No, hits=0.9 required=7.0 tests=HTML_40_50,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14, ML_RADAR_SPEW_LINKS_32, RCVD_BY_IP, spamassassin: X-StarScan-Received: X-StarScan-Version: 6.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 28778 invoked from network); 21 Feb 2013 14:40:21 -0000 Received: from mail-vb0-f50.google.com (HELO mail-vb0-f50.google.com) (209.85.212.50) by server-2.tower-174.messagelabs.com with RC4-SHA encrypted SMTP; 21 Feb 2013 14:40:21 -0000 Received: by mail-vb0-f50.google.com with SMTP id ft2so5709275vbb.37 for ; Thu, 21 Feb 2013 06:40:18 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=ACbYBfg1N6mxAbIqyzIAoZiPiOzJH4f0JyaVHAPiObo=; b=gCFhFubu9hh1QIx3e2hhODXAE0XoaxZqcy30tsM6Gx2L7+PZgZ1Xil70XZAGpiRBtZ nwHyWBvjQUGeDHJodhjnhfykWFoz8QcGNLOExiJFUgoG4QkwbCj6FRhNSJt1TYsv8vwC tbubTyMOqPbW2euRHtpsizUEaOFVTpdxz2cNEBPQkJyZ4nCfUy5K+TvBs2Hi7eUrgA9i j7L5Lvy/fVeZXTB26rBlN5oC/WIDq9Qxlv6OSOtE8MLQplKsglkDOdbvbHIM0Piiuf2W rnN2Q4iw/SKcc5jCul0qWvH7hRwKmT3CmOJz69bRpfkhY8TKBsujZlq8T3Mt1AwUj4tr 3Wkg== MIME-Version: 1.0 X-Received: by 10.52.38.234 with SMTP id j10mr28138717vdk.0.1361457618354; Thu, 21 Feb 2013 06:40:18 -0800 (PST) Received: by 10.58.32.199 with HTTP; Thu, 21 Feb 2013 06:40:18 -0800 (PST) In-Reply-To: References: Date: Thu, 21 Feb 2013 09:40:18 -0500 Message-ID: From: Casey DeLorme To: Krishan Sethi Cc: "xen-users@lists.xen.org" Subject: Re: [Xen-users] Regarding Xen installation X-BeenThere: xen-users@lists.xen.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="===============2041387132666880338==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============2041387132666880338== Content-Type: multipart/alternative; boundary=bcaec51d27f6b801bb04d63d0d92 --bcaec51d27f6b801bb04d63d0d92 Content-Type: text/plain; charset=UTF-8 Hello Krishan, Glad to see a fellow student researcher. > Now i want to load the DomU by xen-tools. but it's not happening. > Not to deter you from getting answers here, but the xen-tools package is maintained by a different team with their own mailing list and may be better equipped to help. You can find there lists here: http://xen-tools.org/software/xen-tools/lists.html > Can anybody tell me the actual and detailed procedure to load domU by > xen-tools. > The website for xen-tools did not specify which version of Xen the xen-tools package is compatible with, and given that the current release of Ubuntu does not have a Xen 4.2 package it is very possible that xen-tools will not work as expected. http://packages.ubuntu.com/search?keywords=xen&searchon=names My understanding is it just simplifies the creation of domain configuration files using Perl scripts to accept input. My advice would be to read the Xen 4.2 Man Pages, as these configuration files can easily be created in a text editor and run using the toolstack that comes with xen: http://wiki.xen.org/wiki/Xen_4.2_Man_Pages http://xenbits.xen.org/docs/4.2-testing/man/xl.cfg.5.html ~Casey --bcaec51d27f6b801bb04d63d0d92 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

Hello Krishan,

G= lad to see a fellow student researcher.
=C2=A0
Now i want to load the DomU by xen-tools. but it's not= happening.

Not to deter you= from getting answers here, but the xen-tools package is maintained by a di= fferent team with their own mailing list and may be better equipped to help= . =C2=A0You can find there lists here:

= =C2=A0
Can anybody tell me the actual and detailed pro= cedure to load domU by xen-tools.

The website for xen-tools did not specify which version of Xen the xen-to= ols package is compatible with, and given that the current release of Ubunt= u does not have a Xen 4.2 package it is very possible that xen-tools will n= ot work as expected.



My understanding is it just simplifies the creation of domain configur= ation files using Perl scripts to accept input. =C2=A0My advice would be to= read the Xen 4.2 Man Pages, as these configuration files can easily be cre= ated in a text editor and run using the toolstack that comes with xen:


~Casey

--bcaec51d27f6b801bb04d63d0d92-- --===============2041387132666880338== 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 --===============2041387132666880338==-- From xen-users-bounces@lists.xen.org Thu Feb 21 14:54:54 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 21 Feb 2013 14:54: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 1U8XX1-0006lV-Tc; Thu, 21 Feb 2013 14:53:55 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U8XX0-0006lQ-Ff for xen-users@lists.xen.org; Thu, 21 Feb 2013 14:53:54 +0000 Received: from [193.109.254.147:27025] by server-15.bemta-14.messagelabs.com id BE/C5-24599-10536215; Thu, 21 Feb 2013 14:53:53 +0000 X-Env-Sender: wei.liu2@citrix.com X-Msg-Ref: server-14.tower-27.messagelabs.com!1361458431!1954237!1 X-Originating-IP: [66.165.176.63] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjYuMTY1LjE3Ni42MyA9PiAzMDM3OTg=\n X-StarScan-Received: X-StarScan-Version: 6.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 7651 invoked from network); 21 Feb 2013 14:53:53 -0000 Received: from smtp02.citrix.com (HELO SMTP02.CITRIX.COM) (66.165.176.63) by server-14.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 21 Feb 2013 14:53:53 -0000 X-IronPort-AV: E=Sophos;i="4.84,709,1355097600"; d="scan'208";a="8316244" Received: from accessns.citrite.net (HELO FTLPEX01CL03.citrite.net) ([10.9.154.239]) by FTLPIPO02.CITRIX.COM with ESMTP/TLS/AES128-SHA; 21 Feb 2013 14:53:51 +0000 Received: from ukmail1.uk.xensource.com (10.80.16.128) by smtprelay.citrix.com (10.13.107.80) with Microsoft SMTP Server id 14.2.318.1; Thu, 21 Feb 2013 09:53:51 -0500 Received: from zion.uk.xensource.com ([10.80.2.73]) by ukmail1.uk.xensource.com with esmtp (Exim 4.69) (envelope-from ) id 1U8XWw-0006us-Ix; Thu, 21 Feb 2013 14:53:50 +0000 Message-ID: <1361458430.2937.36.camel@zion.uk.xensource.com> From: Wei Liu To: Krishan Sethi Date: Thu, 21 Feb 2013 14:53:50 +0000 In-Reply-To: References: X-Mailer: Evolution 3.6.3 (3.6.3-2.fc18) MIME-Version: 1.0 Cc: "xen-users@lists.xen.org" , wei.liu2@citrix.com Subject: Re: [Xen-users] Regarding Xen installation X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: 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, 2013-02-21 at 06:58 +0000, Krishan Sethi wrote: > hi > > > i am krishan sethi, a research scholar. I am doing my research in VM > migration and trying for install the xen form source code in > UBUNTU-12.04. I installed and build the xen and running in dom0. > > > Now i want to load the DomU by xen-tools. but it's not happening. > > > Can anybody tell me the actual and detailed procedure to load domU by > xen-tools. > > A nice write-up from Dario. http://blog.xen.org/index.php/2013/01/24/using-xen-tools-on-fedora/ Wei _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Thu Feb 21 14:54:54 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 21 Feb 2013 14:54: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 1U8XX1-0006lV-Tc; Thu, 21 Feb 2013 14:53:55 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U8XX0-0006lQ-Ff for xen-users@lists.xen.org; Thu, 21 Feb 2013 14:53:54 +0000 Received: from [193.109.254.147:27025] by server-15.bemta-14.messagelabs.com id BE/C5-24599-10536215; Thu, 21 Feb 2013 14:53:53 +0000 X-Env-Sender: wei.liu2@citrix.com X-Msg-Ref: server-14.tower-27.messagelabs.com!1361458431!1954237!1 X-Originating-IP: [66.165.176.63] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjYuMTY1LjE3Ni42MyA9PiAzMDM3OTg=\n X-StarScan-Received: X-StarScan-Version: 6.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 7651 invoked from network); 21 Feb 2013 14:53:53 -0000 Received: from smtp02.citrix.com (HELO SMTP02.CITRIX.COM) (66.165.176.63) by server-14.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 21 Feb 2013 14:53:53 -0000 X-IronPort-AV: E=Sophos;i="4.84,709,1355097600"; d="scan'208";a="8316244" Received: from accessns.citrite.net (HELO FTLPEX01CL03.citrite.net) ([10.9.154.239]) by FTLPIPO02.CITRIX.COM with ESMTP/TLS/AES128-SHA; 21 Feb 2013 14:53:51 +0000 Received: from ukmail1.uk.xensource.com (10.80.16.128) by smtprelay.citrix.com (10.13.107.80) with Microsoft SMTP Server id 14.2.318.1; Thu, 21 Feb 2013 09:53:51 -0500 Received: from zion.uk.xensource.com ([10.80.2.73]) by ukmail1.uk.xensource.com with esmtp (Exim 4.69) (envelope-from ) id 1U8XWw-0006us-Ix; Thu, 21 Feb 2013 14:53:50 +0000 Message-ID: <1361458430.2937.36.camel@zion.uk.xensource.com> From: Wei Liu To: Krishan Sethi Date: Thu, 21 Feb 2013 14:53:50 +0000 In-Reply-To: References: X-Mailer: Evolution 3.6.3 (3.6.3-2.fc18) MIME-Version: 1.0 Cc: "xen-users@lists.xen.org" , wei.liu2@citrix.com Subject: Re: [Xen-users] Regarding Xen installation X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: 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, 2013-02-21 at 06:58 +0000, Krishan Sethi wrote: > hi > > > i am krishan sethi, a research scholar. I am doing my research in VM > migration and trying for install the xen form source code in > UBUNTU-12.04. I installed and build the xen and running in dom0. > > > Now i want to load the DomU by xen-tools. but it's not happening. > > > Can anybody tell me the actual and detailed procedure to load domU by > xen-tools. > > A nice write-up from Dario. http://blog.xen.org/index.php/2013/01/24/using-xen-tools-on-fedora/ Wei _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Thu Feb 21 15:12:09 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 21 Feb 2013 15:12: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 1U8Xny-0000MR-B5; Thu, 21 Feb 2013 15:11:26 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U8Xnx-0000MG-6Y for xen-users@lists.xen.org; Thu, 21 Feb 2013 15:11:25 +0000 Received: from [85.158.139.211:52136] by server-13.bemta-5.messagelabs.com id C7/17-06769-C1936215; Thu, 21 Feb 2013 15:11:24 +0000 X-Env-Sender: eross@corp.locatrix.com X-Msg-Ref: server-14.tower-206.messagelabs.com!1361459481!18559425!1 X-Originating-IP: [209.85.223.170] 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.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 18884 invoked from network); 21 Feb 2013 15:11:23 -0000 Received: from mail-ie0-f170.google.com (HELO mail-ie0-f170.google.com) (209.85.223.170) by server-14.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 21 Feb 2013 15:11:23 -0000 Received: by mail-ie0-f170.google.com with SMTP id c11so11589797ieb.29 for ; Thu, 21 Feb 2013 07:11:21 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=x-received:mime-version:in-reply-to:references:from:date:message-id :subject:to:cc:content-type:x-gm-message-state; bh=+Grsus4Xo+PGN85gh6PYuROD9f6B/rKyQLwvqy0bkIg=; b=lF2w4WFm0q+yH46Ut59XKOsK9iBlNBhI2HBXV0A/yv4bBQOjJB1WchKYI1xklVJbYv 8ZwqnsOhkKitim1twkVlt1aQhr6gxgteyBPeD3BuptMqzjuN4cXnVUMgcXErkOCFPdXl gzqatD2hFYuJKUrj6vb5NsuC4HBz0dDmO5kxIDWWlThScgsdRAQYPon6CjDplIGd+CFv AYL+10pd7tjyD32Kv7VtqqtTiKELKMnKaGEsW69+wdHkW0/o3c2N7L5OdMmEwHQOT0PW Qb3Hluxen38Kz5ZX10TS0M59wBS6t1NFvYrdlDQZ5/s/LUVvP9zO76jO3Wuxg8oXuv7d FH5w== X-Received: by 10.50.208.40 with SMTP id mb8mr6582560igc.91.1361459481555; Thu, 21 Feb 2013 07:11:21 -0800 (PST) MIME-Version: 1.0 Received: by 10.64.9.103 with HTTP; Thu, 21 Feb 2013 07:11:01 -0800 (PST) In-Reply-To: <1361281294.8796.YahooMailNeo@web171304.mail.ir2.yahoo.com> References: <51229E41.2090103@yahoo.co.uk> <1361281294.8796.YahooMailNeo@web171304.mail.ir2.yahoo.com> From: Andrew Eross Date: Thu, 21 Feb 2013 12:11:01 -0300 Message-ID: To: Ian Murray X-Gm-Message-State: ALoCoQluAwqBhehc93U2V62Mc1T2jyMg/iOYwc62HrneJ7LG2CRtbP9/Ff6OD6lNiIVBaSEXQm6c Cc: "xen-users@lists.xen.org" Subject: Re: [Xen-users] Xen 4.2.1 unable to get domain type for domid X-BeenThere: xen-users@lists.xen.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="===============6978641024122638514==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============6978641024122638514== Content-Type: multipart/alternative; boundary=14dae9340345c6341904d63d7cce --14dae9340345c6341904d63d7cce Content-Type: text/plain; charset=ISO-8859-1 Hi Ian, Yep, confirmed, exact same images as you: 8525c3e8d6131ae462ba85b935a70bae vmlinuz f1f36dbfe47ebda085f41394dd079d09 initrd.gz And I tried a very similar config: name = "ubuntu-calendar-test" memory = 1024 disk = ['phy:/dev/mapper/center-calendar,xvda,w'] vif = [ 'mac=00:16:31:55:1c:82' ] kernel = "/root/ubuntu1204/vmlinuz" ramdisk = "/root/ubuntu1204/initrd.gz" vcpus = 2 on_reboot = 'destroy' on_crash = 'destroy' Unfortunately still not able to launch this VM, very strange! xl create /etc/xen/ubuntu-calendar-test.cfg -c # Parsing config from /etc/xen/ubuntu-calendar-test.cfg Daemon running with PID 28828 xenconsole: Could not read tty from store: No such file or directory libxl: error: libxl_exec.c:118:libxl_report_child_exitstatus: console child [0] exited with error status 2 # cat /var/log/xen/xl-ubuntu-calendar-test.log # Waiting for domain ubuntu-calendar-test (domid 2) to die [pid 27391] Domain 2 has shut down, reason code 3 0x3 Action for shutdown reason code 3 is destroy Domain 2 needs to be cleaned up: destroying the domain Done. Exiting now # I'm glad I can create VMs with "xen-create-image", but still this is strange... any possible other ideas? Thanks much, Andrew On Tue, Feb 19, 2013 at 10:41 AM, Ian Murray wrote: > > > >Hi Ian, > > > > > >Thanks for the feedback - > > > No problem. > > > > > > >I'm still a little wary that perhaps there's a bug in xl since the > netboot image should've worked I think, but happy that this method does > work. > > > > > > > I've just tried it again with 12.04.2 xen boot images and all went well. > Here is my config file... > > name = "ubuntu-calendar-test" > memory = 1024 > disk = ['phy:/dev/VG1/ubuntu-calendar-test,xvda,w' ] > vif = [ 'mac=00:16:31:55:1c:82' ] > kernel = "/root/xen/ubuntu1204/vmlinuz" > ramdisk = "/root/xen/ubuntu1204/initrd.gz" > vcpus = 2 > on_reboot = 'destroy' > on_crash = 'destroy' > > > Are you sure there is no problem with your images? Here is are md5 hashes > for the two files I used (12.04.2, 32bit as far as I remember)... > > f1f36dbfe47ebda085f41394dd079d09 initrd.gz > 8525c3e8d6131ae462ba85b935a70bae vmlinuz > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xen.org > http://lists.xen.org/xen-users > --14dae9340345c6341904d63d7cce Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Hi Ian,

Yep, confirmed, exact same images as you:
<= div>
8525c3e8d6131ae462ba85b935a70bae =A0vmlinuz
f1f36dbfe47ebda085f41394dd079d09 =A0initrd.gz

A= nd I tried a very similar config:

name =A0 =A0 =A0=3D "ubuntu-calendar-test&quo= t;
memory =A0 =A0=3D 1024
disk =A0 =A0 =A0=3D ['phy= :/dev/mapper/center-calendar,xvda,w']
vif =3D [ 'mac=3D00= :16:31:55:1c:82' ]
kernel =A0 =A0=3D "/root/ubuntu1204/vmlinuz"
ramdi= sk =A0 =3D "/root/ubuntu1204/initrd.gz"
vcpus =A0 =A0 = =3D 2
on_reboot =3D 'destroy'
on_crash =A0=3D &= #39;destroy'

Unfortunately still not able to launch this VM, v= ery strange!

xl create /etc/xen/ubuntu-calend= ar-test.cfg -c
#
Parsing config from /etc/xen/ubuntu-ca= lendar-test.cfg
Daemon running with PID 28828
xenconsole: Could not read tty= from store: No such file or directory
libxl: error: libxl_exec.c= :118:libxl_report_child_exitstatus: console child [0] exited with error sta= tus 2
#

cat /var/log/xen/xl-ubuntu-calen= dar-test.log
#
Waiting for domain ubuntu-calendar-test = (domid 2) to die [pid 27391]
Domain 2 has shut down, reason code = 3 0x3
Action for shutdown reason code 3 is destroy
Domain 2 needs = to be cleaned up: destroying the domain
Done. Exiting now
#

I'm glad I can create VMs with &quo= t;xen-create-image&q= uot;, but still this is strange... any possible other ideas?

Thanks much,<= /span>
Andrew

On Tue, Feb 19, 2013 at 10:41 AM, Ian Murray <m= urrayie@yahoo.co.uk> wrote:


>Hi Ian,
>
>
>Thanks for the feedback -


No problem.

>
>
>I'm still a little wary that perhaps there's a bug in xl since = the netboot image should've worked I think, but happy that this method = does work.
>
>


I've just tried it again with 12.04.2 xen boot images and all wen= t well. Here is my config file...

name=A0=A0=A0=A0=A0 =3D "ubuntu-calendar-test"
memory=A0=A0=A0 =3D 1024
disk=A0=A0=A0=A0=A0 =3D ['phy:/dev/VG1/ubuntu-calendar-test,xvda,w'= ]
vif =3D [ 'mac=3D00:16:31:55:1c:82' ]
kernel=A0=A0=A0 =3D "/root/xen/ubuntu1204/vmlinuz"
ramdisk=A0=A0 =3D "/root/xen/ubuntu1204/initrd.gz"
vcpus=A0=A0=A0=A0 =3D 2
on_reboot =3D 'destroy'
on_crash=A0 =3D 'destroy'


Are you sure there is no problem with your images? Here is are md5 hashes f= or the two files I used (12.04.2, 32bit as far as I remember)...

f1f36dbfe47ebda085f41394dd079d09=A0 initrd.gz
8525c3e8d6131ae462ba85b935a70bae=A0 vmlinuz

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

--14dae9340345c6341904d63d7cce-- --===============6978641024122638514== 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 --===============6978641024122638514==-- From xen-users-bounces@lists.xen.org Thu Feb 21 15:12:09 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 21 Feb 2013 15:12: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 1U8Xny-0000MR-B5; Thu, 21 Feb 2013 15:11:26 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U8Xnx-0000MG-6Y for xen-users@lists.xen.org; Thu, 21 Feb 2013 15:11:25 +0000 Received: from [85.158.139.211:52136] by server-13.bemta-5.messagelabs.com id C7/17-06769-C1936215; Thu, 21 Feb 2013 15:11:24 +0000 X-Env-Sender: eross@corp.locatrix.com X-Msg-Ref: server-14.tower-206.messagelabs.com!1361459481!18559425!1 X-Originating-IP: [209.85.223.170] 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.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 18884 invoked from network); 21 Feb 2013 15:11:23 -0000 Received: from mail-ie0-f170.google.com (HELO mail-ie0-f170.google.com) (209.85.223.170) by server-14.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 21 Feb 2013 15:11:23 -0000 Received: by mail-ie0-f170.google.com with SMTP id c11so11589797ieb.29 for ; Thu, 21 Feb 2013 07:11:21 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=x-received:mime-version:in-reply-to:references:from:date:message-id :subject:to:cc:content-type:x-gm-message-state; bh=+Grsus4Xo+PGN85gh6PYuROD9f6B/rKyQLwvqy0bkIg=; b=lF2w4WFm0q+yH46Ut59XKOsK9iBlNBhI2HBXV0A/yv4bBQOjJB1WchKYI1xklVJbYv 8ZwqnsOhkKitim1twkVlt1aQhr6gxgteyBPeD3BuptMqzjuN4cXnVUMgcXErkOCFPdXl gzqatD2hFYuJKUrj6vb5NsuC4HBz0dDmO5kxIDWWlThScgsdRAQYPon6CjDplIGd+CFv AYL+10pd7tjyD32Kv7VtqqtTiKELKMnKaGEsW69+wdHkW0/o3c2N7L5OdMmEwHQOT0PW Qb3Hluxen38Kz5ZX10TS0M59wBS6t1NFvYrdlDQZ5/s/LUVvP9zO76jO3Wuxg8oXuv7d FH5w== X-Received: by 10.50.208.40 with SMTP id mb8mr6582560igc.91.1361459481555; Thu, 21 Feb 2013 07:11:21 -0800 (PST) MIME-Version: 1.0 Received: by 10.64.9.103 with HTTP; Thu, 21 Feb 2013 07:11:01 -0800 (PST) In-Reply-To: <1361281294.8796.YahooMailNeo@web171304.mail.ir2.yahoo.com> References: <51229E41.2090103@yahoo.co.uk> <1361281294.8796.YahooMailNeo@web171304.mail.ir2.yahoo.com> From: Andrew Eross Date: Thu, 21 Feb 2013 12:11:01 -0300 Message-ID: To: Ian Murray X-Gm-Message-State: ALoCoQluAwqBhehc93U2V62Mc1T2jyMg/iOYwc62HrneJ7LG2CRtbP9/Ff6OD6lNiIVBaSEXQm6c Cc: "xen-users@lists.xen.org" Subject: Re: [Xen-users] Xen 4.2.1 unable to get domain type for domid X-BeenThere: xen-users@lists.xen.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="===============6978641024122638514==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============6978641024122638514== Content-Type: multipart/alternative; boundary=14dae9340345c6341904d63d7cce --14dae9340345c6341904d63d7cce Content-Type: text/plain; charset=ISO-8859-1 Hi Ian, Yep, confirmed, exact same images as you: 8525c3e8d6131ae462ba85b935a70bae vmlinuz f1f36dbfe47ebda085f41394dd079d09 initrd.gz And I tried a very similar config: name = "ubuntu-calendar-test" memory = 1024 disk = ['phy:/dev/mapper/center-calendar,xvda,w'] vif = [ 'mac=00:16:31:55:1c:82' ] kernel = "/root/ubuntu1204/vmlinuz" ramdisk = "/root/ubuntu1204/initrd.gz" vcpus = 2 on_reboot = 'destroy' on_crash = 'destroy' Unfortunately still not able to launch this VM, very strange! xl create /etc/xen/ubuntu-calendar-test.cfg -c # Parsing config from /etc/xen/ubuntu-calendar-test.cfg Daemon running with PID 28828 xenconsole: Could not read tty from store: No such file or directory libxl: error: libxl_exec.c:118:libxl_report_child_exitstatus: console child [0] exited with error status 2 # cat /var/log/xen/xl-ubuntu-calendar-test.log # Waiting for domain ubuntu-calendar-test (domid 2) to die [pid 27391] Domain 2 has shut down, reason code 3 0x3 Action for shutdown reason code 3 is destroy Domain 2 needs to be cleaned up: destroying the domain Done. Exiting now # I'm glad I can create VMs with "xen-create-image", but still this is strange... any possible other ideas? Thanks much, Andrew On Tue, Feb 19, 2013 at 10:41 AM, Ian Murray wrote: > > > >Hi Ian, > > > > > >Thanks for the feedback - > > > No problem. > > > > > > >I'm still a little wary that perhaps there's a bug in xl since the > netboot image should've worked I think, but happy that this method does > work. > > > > > > > I've just tried it again with 12.04.2 xen boot images and all went well. > Here is my config file... > > name = "ubuntu-calendar-test" > memory = 1024 > disk = ['phy:/dev/VG1/ubuntu-calendar-test,xvda,w' ] > vif = [ 'mac=00:16:31:55:1c:82' ] > kernel = "/root/xen/ubuntu1204/vmlinuz" > ramdisk = "/root/xen/ubuntu1204/initrd.gz" > vcpus = 2 > on_reboot = 'destroy' > on_crash = 'destroy' > > > Are you sure there is no problem with your images? Here is are md5 hashes > for the two files I used (12.04.2, 32bit as far as I remember)... > > f1f36dbfe47ebda085f41394dd079d09 initrd.gz > 8525c3e8d6131ae462ba85b935a70bae vmlinuz > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xen.org > http://lists.xen.org/xen-users > --14dae9340345c6341904d63d7cce Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Hi Ian,

Yep, confirmed, exact same images as you:
<= div>
8525c3e8d6131ae462ba85b935a70bae =A0vmlinuz
f1f36dbfe47ebda085f41394dd079d09 =A0initrd.gz

A= nd I tried a very similar config:

name =A0 =A0 =A0=3D "ubuntu-calendar-test&quo= t;
memory =A0 =A0=3D 1024
disk =A0 =A0 =A0=3D ['phy= :/dev/mapper/center-calendar,xvda,w']
vif =3D [ 'mac=3D00= :16:31:55:1c:82' ]
kernel =A0 =A0=3D "/root/ubuntu1204/vmlinuz"
ramdi= sk =A0 =3D "/root/ubuntu1204/initrd.gz"
vcpus =A0 =A0 = =3D 2
on_reboot =3D 'destroy'
on_crash =A0=3D &= #39;destroy'

Unfortunately still not able to launch this VM, v= ery strange!

xl create /etc/xen/ubuntu-calend= ar-test.cfg -c
#
Parsing config from /etc/xen/ubuntu-ca= lendar-test.cfg
Daemon running with PID 28828
xenconsole: Could not read tty= from store: No such file or directory
libxl: error: libxl_exec.c= :118:libxl_report_child_exitstatus: console child [0] exited with error sta= tus 2
#

cat /var/log/xen/xl-ubuntu-calen= dar-test.log
#
Waiting for domain ubuntu-calendar-test = (domid 2) to die [pid 27391]
Domain 2 has shut down, reason code = 3 0x3
Action for shutdown reason code 3 is destroy
Domain 2 needs = to be cleaned up: destroying the domain
Done. Exiting now
#

I'm glad I can create VMs with &quo= t;xen-create-image&q= uot;, but still this is strange... any possible other ideas?

Thanks much,<= /span>
Andrew

On Tue, Feb 19, 2013 at 10:41 AM, Ian Murray <m= urrayie@yahoo.co.uk> wrote:


>Hi Ian,
>
>
>Thanks for the feedback -


No problem.

>
>
>I'm still a little wary that perhaps there's a bug in xl since = the netboot image should've worked I think, but happy that this method = does work.
>
>


I've just tried it again with 12.04.2 xen boot images and all wen= t well. Here is my config file...

name=A0=A0=A0=A0=A0 =3D "ubuntu-calendar-test"
memory=A0=A0=A0 =3D 1024
disk=A0=A0=A0=A0=A0 =3D ['phy:/dev/VG1/ubuntu-calendar-test,xvda,w'= ]
vif =3D [ 'mac=3D00:16:31:55:1c:82' ]
kernel=A0=A0=A0 =3D "/root/xen/ubuntu1204/vmlinuz"
ramdisk=A0=A0 =3D "/root/xen/ubuntu1204/initrd.gz"
vcpus=A0=A0=A0=A0 =3D 2
on_reboot =3D 'destroy'
on_crash=A0 =3D 'destroy'


Are you sure there is no problem with your images? Here is are md5 hashes f= or the two files I used (12.04.2, 32bit as far as I remember)...

f1f36dbfe47ebda085f41394dd079d09=A0 initrd.gz
8525c3e8d6131ae462ba85b935a70bae=A0 vmlinuz

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

--14dae9340345c6341904d63d7cce-- --===============6978641024122638514== 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 --===============6978641024122638514==-- From xen-users-bounces@lists.xen.org Thu Feb 21 15:54:40 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 21 Feb 2013 15: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 1U8YSw-0004dP-5V; Thu, 21 Feb 2013 15:53:46 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U8YSu-0004cv-JS for xen-users@lists.xen.org; Thu, 21 Feb 2013 15:53:44 +0000 Received: from [85.158.143.99:29902] by server-3.bemta-4.messagelabs.com id F0/9E-02186-70346215; Thu, 21 Feb 2013 15:53:43 +0000 X-Env-Sender: jaceksburghardt@gmail.com X-Msg-Ref: server-8.tower-216.messagelabs.com!1361462001!18811766!1 X-Originating-IP: [209.85.210.176] 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.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 16545 invoked from network); 21 Feb 2013 15:53:43 -0000 Received: from mail-ia0-f176.google.com (HELO mail-ia0-f176.google.com) (209.85.210.176) by server-8.tower-216.messagelabs.com with RC4-SHA encrypted SMTP; 21 Feb 2013 15:53:43 -0000 Received: by mail-ia0-f176.google.com with SMTP id i18so8115277iac.7 for ; Thu, 21 Feb 2013 07:53:03 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:date:message-id:subject:from:to :content-type; bh=dpedRTb/+SV0StLNYe2UeYKbjAuqrXFJyi70thsoWFU=; b=DE7b6d8TRoVmYtJ0jTzFODZfRkDRSXyitdzgmYd7jhMo9XnHptfGAHVN+5bENEZFLk J4Rcj3loxS6SNg9y80uIocZs/LS5Fu/IXtHGqZx/+R8upDbPTWHTLtbeDRMCI6qw55jb /kdDbjSSYHx4SCTlI5f0ycc+TFv9GPggslnIWEnkIFggRP5Ck5JdIsZZ/a7U0j96dGfT xM+Nf53jZanLDTudGpVpg+MFT1wAGxlTM8KW1c9LOpcW+zgRQdaqg0lYfsIDvjHFHZ+k dxHVB1ZJ+jjzt103HT7e5K9sZ79clZSvLlwv9RkFY2+L2JuvrHiOkDqyomN74NR/mtPB ZiNw== MIME-Version: 1.0 X-Received: by 10.50.17.163 with SMTP id p3mr7014074igd.90.1361461982984; Thu, 21 Feb 2013 07:53:02 -0800 (PST) Received: by 10.42.41.5 with HTTP; Thu, 21 Feb 2013 07:53:02 -0800 (PST) Date: Thu, 21 Feb 2013 08:53:02 -0700 Message-ID: From: jacek burghardt To: xen-users Subject: [Xen-users] xen 4.3 bug X-BeenThere: xen-users@lists.xen.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="===============3858681499291981377==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============3858681499291981377== Content-Type: multipart/alternative; boundary=14dae93407cfdef87804d63e1183 --14dae93407cfdef87804d63e1183 Content-Type: text/plain; charset=ISO-8859-1 The arch linux upgraded texinfo to texinfo 5 I am getting this error message qemu-options.texi:1495: unknown command `list'. There is patch for it. Can someone tell me how long before this patch http://patchwork.ozlabs.org/patch/222131/ is applied to qemu that xen 4.3 is using ? --14dae93407cfdef87804d63e1183 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable The arch linux upgraded=A0texinfo to texinfo 5
I am getting this error message=A0qemu-options.texi:1495: unknown command `= list'. There is patch for it. Can=A0someone=A0tell me how long before t= his patch=A0
http://patchwork.ozlabs.org/patch/222131/ is applied to qemu that xen= 4.3 is using ?=A0
--14dae93407cfdef87804d63e1183-- --===============3858681499291981377== 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 --===============3858681499291981377==-- From xen-users-bounces@lists.xen.org Thu Feb 21 15:54:40 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 21 Feb 2013 15: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 1U8YSw-0004dP-5V; Thu, 21 Feb 2013 15:53:46 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U8YSu-0004cv-JS for xen-users@lists.xen.org; Thu, 21 Feb 2013 15:53:44 +0000 Received: from [85.158.143.99:29902] by server-3.bemta-4.messagelabs.com id F0/9E-02186-70346215; Thu, 21 Feb 2013 15:53:43 +0000 X-Env-Sender: jaceksburghardt@gmail.com X-Msg-Ref: server-8.tower-216.messagelabs.com!1361462001!18811766!1 X-Originating-IP: [209.85.210.176] 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.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 16545 invoked from network); 21 Feb 2013 15:53:43 -0000 Received: from mail-ia0-f176.google.com (HELO mail-ia0-f176.google.com) (209.85.210.176) by server-8.tower-216.messagelabs.com with RC4-SHA encrypted SMTP; 21 Feb 2013 15:53:43 -0000 Received: by mail-ia0-f176.google.com with SMTP id i18so8115277iac.7 for ; Thu, 21 Feb 2013 07:53:03 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:date:message-id:subject:from:to :content-type; bh=dpedRTb/+SV0StLNYe2UeYKbjAuqrXFJyi70thsoWFU=; b=DE7b6d8TRoVmYtJ0jTzFODZfRkDRSXyitdzgmYd7jhMo9XnHptfGAHVN+5bENEZFLk J4Rcj3loxS6SNg9y80uIocZs/LS5Fu/IXtHGqZx/+R8upDbPTWHTLtbeDRMCI6qw55jb /kdDbjSSYHx4SCTlI5f0ycc+TFv9GPggslnIWEnkIFggRP5Ck5JdIsZZ/a7U0j96dGfT xM+Nf53jZanLDTudGpVpg+MFT1wAGxlTM8KW1c9LOpcW+zgRQdaqg0lYfsIDvjHFHZ+k dxHVB1ZJ+jjzt103HT7e5K9sZ79clZSvLlwv9RkFY2+L2JuvrHiOkDqyomN74NR/mtPB ZiNw== MIME-Version: 1.0 X-Received: by 10.50.17.163 with SMTP id p3mr7014074igd.90.1361461982984; Thu, 21 Feb 2013 07:53:02 -0800 (PST) Received: by 10.42.41.5 with HTTP; Thu, 21 Feb 2013 07:53:02 -0800 (PST) Date: Thu, 21 Feb 2013 08:53:02 -0700 Message-ID: From: jacek burghardt To: xen-users Subject: [Xen-users] xen 4.3 bug X-BeenThere: xen-users@lists.xen.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="===============3858681499291981377==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============3858681499291981377== Content-Type: multipart/alternative; boundary=14dae93407cfdef87804d63e1183 --14dae93407cfdef87804d63e1183 Content-Type: text/plain; charset=ISO-8859-1 The arch linux upgraded texinfo to texinfo 5 I am getting this error message qemu-options.texi:1495: unknown command `list'. There is patch for it. Can someone tell me how long before this patch http://patchwork.ozlabs.org/patch/222131/ is applied to qemu that xen 4.3 is using ? --14dae93407cfdef87804d63e1183 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable The arch linux upgraded=A0texinfo to texinfo 5
I am getting this error message=A0qemu-options.texi:1495: unknown command `= list'. There is patch for it. Can=A0someone=A0tell me how long before t= his patch=A0
http://patchwork.ozlabs.org/patch/222131/ is applied to qemu that xen= 4.3 is using ?=A0
--14dae93407cfdef87804d63e1183-- --===============3858681499291981377== 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 --===============3858681499291981377==-- From xen-users-bounces@lists.xen.org Thu Feb 21 16:14:44 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 21 Feb 2013 16:14: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 1U8YmU-0007Sq-Gj; Thu, 21 Feb 2013 16:13:58 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U8YmS-0007SY-G7 for xen-users@lists.xensource.com; Thu, 21 Feb 2013 16:13:56 +0000 Received: from [85.158.138.51:57993] by server-15.bemta-3.messagelabs.com id F8/66-25405-DB746215; Thu, 21 Feb 2013 16:13:49 +0000 X-Env-Sender: Chethu2288@gmail.com X-Msg-Ref: server-10.tower-174.messagelabs.com!1361463227!24546316!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.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 31368 invoked from network); 21 Feb 2013 16:13:48 -0000 Received: from sam.nabble.com (HELO sam.nabble.com) (216.139.236.26) by server-10.tower-174.messagelabs.com with AES256-SHA encrypted SMTP; 21 Feb 2013 16:13:48 -0000 Received: from [192.168.236.26] (helo=sam.nabble.com) by sam.nabble.com with esmtp (Exim 4.72) (envelope-from ) id 1U8YmI-0002Ex-6f for xen-users@lists.xensource.com; Thu, 21 Feb 2013 08:13:46 -0800 Date: Thu, 21 Feb 2013 08:13:46 -0800 (PST) From: Lakshman Jayaraju To: xen-users@lists.xensource.com Message-ID: <1361463226200-5714370.post@n5.nabble.com> MIME-Version: 1.0 Subject: [Xen-users] Does IDTR value changes in Guest Domians??? X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: 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, AM trying to fetch the IDT(Interrupt Descriptor Table) Base address using the following program in domU PV Guest. #include #include #include MODULE_LICENSE("GPL"); static inline void *sidt(void) { unsigned int ptr[2]; __asm__ volatile ("sidt (%0)": : "a"(((char *) ptr)+2)); retrun (void *) ptr[1]; } static int __init hello_init(void) { printk(KERN_INFO "%p",sidt()); printk(KERN_INFO "Hello World!!!\n"); return 0; } static void __exit hello_cleanup(void) { printk(KERN_INFO "Cleaning up the module!!!\n"); } module_init(hello_init); module_exit(hello_cleanup); On every insmod of this module, its displaying different base address. But limit remains the same(i.e., 255) Is this usual??? Or Is my program logic wrong??? Regards, Lakshman Jayaraju -- View this message in context: http://xen.1045712.n5.nabble.com/Does-IDTR-value-changes-in-Guest-Domians-tp5714370.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 Thu Feb 21 16:14:44 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 21 Feb 2013 16:14: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 1U8YmU-0007Sq-Gj; Thu, 21 Feb 2013 16:13:58 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U8YmS-0007SY-G7 for xen-users@lists.xensource.com; Thu, 21 Feb 2013 16:13:56 +0000 Received: from [85.158.138.51:57993] by server-15.bemta-3.messagelabs.com id F8/66-25405-DB746215; Thu, 21 Feb 2013 16:13:49 +0000 X-Env-Sender: Chethu2288@gmail.com X-Msg-Ref: server-10.tower-174.messagelabs.com!1361463227!24546316!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.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 31368 invoked from network); 21 Feb 2013 16:13:48 -0000 Received: from sam.nabble.com (HELO sam.nabble.com) (216.139.236.26) by server-10.tower-174.messagelabs.com with AES256-SHA encrypted SMTP; 21 Feb 2013 16:13:48 -0000 Received: from [192.168.236.26] (helo=sam.nabble.com) by sam.nabble.com with esmtp (Exim 4.72) (envelope-from ) id 1U8YmI-0002Ex-6f for xen-users@lists.xensource.com; Thu, 21 Feb 2013 08:13:46 -0800 Date: Thu, 21 Feb 2013 08:13:46 -0800 (PST) From: Lakshman Jayaraju To: xen-users@lists.xensource.com Message-ID: <1361463226200-5714370.post@n5.nabble.com> MIME-Version: 1.0 Subject: [Xen-users] Does IDTR value changes in Guest Domians??? X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: 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, AM trying to fetch the IDT(Interrupt Descriptor Table) Base address using the following program in domU PV Guest. #include #include #include MODULE_LICENSE("GPL"); static inline void *sidt(void) { unsigned int ptr[2]; __asm__ volatile ("sidt (%0)": : "a"(((char *) ptr)+2)); retrun (void *) ptr[1]; } static int __init hello_init(void) { printk(KERN_INFO "%p",sidt()); printk(KERN_INFO "Hello World!!!\n"); return 0; } static void __exit hello_cleanup(void) { printk(KERN_INFO "Cleaning up the module!!!\n"); } module_init(hello_init); module_exit(hello_cleanup); On every insmod of this module, its displaying different base address. But limit remains the same(i.e., 255) Is this usual??? Or Is my program logic wrong??? Regards, Lakshman Jayaraju -- View this message in context: http://xen.1045712.n5.nabble.com/Does-IDTR-value-changes-in-Guest-Domians-tp5714370.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 Thu Feb 21 17:12:49 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 21 Feb 2013 17:12: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 1U8ZgS-00033m-Ui; Thu, 21 Feb 2013 17:11:48 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U8ZgR-00033e-FH for xen-users@lists.xen.org; Thu, 21 Feb 2013 17:11:47 +0000 Received: from [193.109.254.147:42761] by server-16.bemta-14.messagelabs.com id F8/04-25906-25556215; Thu, 21 Feb 2013 17:11:46 +0000 X-Env-Sender: wei.liu2@citrix.com X-Msg-Ref: server-13.tower-27.messagelabs.com!1361466702!8733663!1 X-Originating-IP: [66.165.176.89] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjYuMTY1LjE3Ni44OSA9PiAyMDAzNjg=\n X-StarScan-Received: X-StarScan-Version: 6.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 24983 invoked from network); 21 Feb 2013 17:11:44 -0000 Received: from smtp.citrix.com (HELO SMTP.CITRIX.COM) (66.165.176.89) by server-13.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 21 Feb 2013 17:11:44 -0000 X-IronPort-AV: E=Sophos;i="4.84,710,1355097600"; d="scan'208";a="8795526" Received: from accessns.citrite.net (HELO FTLPEX01CL03.citrite.net) ([10.9.154.239]) by FTLPIPO01.CITRIX.COM with ESMTP/TLS/AES128-SHA; 21 Feb 2013 17:11:42 +0000 Received: from ukmail1.uk.xensource.com (10.80.16.128) by smtprelay.citrix.com (10.13.107.80) with Microsoft SMTP Server id 14.2.318.1; Thu, 21 Feb 2013 12:11:41 -0500 Received: from zion.uk.xensource.com ([10.80.2.73]) by ukmail1.uk.xensource.com with esmtp (Exim 4.69) (envelope-from ) id 1U8ZgL-0000cv-CO; Thu, 21 Feb 2013 17:11:41 +0000 Message-ID: <1361466701.2937.41.camel@zion.uk.xensource.com> From: Wei Liu To: jacek burghardt Date: Thu, 21 Feb 2013 17:11:41 +0000 In-Reply-To: References: X-Mailer: Evolution 3.6.3 (3.6.3-2.fc18) MIME-Version: 1.0 Cc: xen-users , wei.liu2@citrix.com Subject: Re: [Xen-users] xen 4.3 bug X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: 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, 2013-02-21 at 15:53 +0000, jacek burghardt wrote: > The arch linux upgraded texinfo to texinfo 5 > I am getting this error message qemu-options.texi:1495: unknown > command `list'. There is patch for it. Can someone tell me how long > before this patch > http://patchwork.ozlabs.org/patch/222131/ is applied to qemu that xen > 4.3 is using ? Strictly speaking, this is *not* a Xen bug. Textinfo is to be blamed because it breaks things that previously work. :-( Anyway, I've sent a patch to xen-devel with you CC'ed. Please try that patch. Wei. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Thu Feb 21 17:12:49 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 21 Feb 2013 17:12: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 1U8ZgS-00033m-Ui; Thu, 21 Feb 2013 17:11:48 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U8ZgR-00033e-FH for xen-users@lists.xen.org; Thu, 21 Feb 2013 17:11:47 +0000 Received: from [193.109.254.147:42761] by server-16.bemta-14.messagelabs.com id F8/04-25906-25556215; Thu, 21 Feb 2013 17:11:46 +0000 X-Env-Sender: wei.liu2@citrix.com X-Msg-Ref: server-13.tower-27.messagelabs.com!1361466702!8733663!1 X-Originating-IP: [66.165.176.89] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjYuMTY1LjE3Ni44OSA9PiAyMDAzNjg=\n X-StarScan-Received: X-StarScan-Version: 6.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 24983 invoked from network); 21 Feb 2013 17:11:44 -0000 Received: from smtp.citrix.com (HELO SMTP.CITRIX.COM) (66.165.176.89) by server-13.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 21 Feb 2013 17:11:44 -0000 X-IronPort-AV: E=Sophos;i="4.84,710,1355097600"; d="scan'208";a="8795526" Received: from accessns.citrite.net (HELO FTLPEX01CL03.citrite.net) ([10.9.154.239]) by FTLPIPO01.CITRIX.COM with ESMTP/TLS/AES128-SHA; 21 Feb 2013 17:11:42 +0000 Received: from ukmail1.uk.xensource.com (10.80.16.128) by smtprelay.citrix.com (10.13.107.80) with Microsoft SMTP Server id 14.2.318.1; Thu, 21 Feb 2013 12:11:41 -0500 Received: from zion.uk.xensource.com ([10.80.2.73]) by ukmail1.uk.xensource.com with esmtp (Exim 4.69) (envelope-from ) id 1U8ZgL-0000cv-CO; Thu, 21 Feb 2013 17:11:41 +0000 Message-ID: <1361466701.2937.41.camel@zion.uk.xensource.com> From: Wei Liu To: jacek burghardt Date: Thu, 21 Feb 2013 17:11:41 +0000 In-Reply-To: References: X-Mailer: Evolution 3.6.3 (3.6.3-2.fc18) MIME-Version: 1.0 Cc: xen-users , wei.liu2@citrix.com Subject: Re: [Xen-users] xen 4.3 bug X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: 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, 2013-02-21 at 15:53 +0000, jacek burghardt wrote: > The arch linux upgraded texinfo to texinfo 5 > I am getting this error message qemu-options.texi:1495: unknown > command `list'. There is patch for it. Can someone tell me how long > before this patch > http://patchwork.ozlabs.org/patch/222131/ is applied to qemu that xen > 4.3 is using ? Strictly speaking, this is *not* a Xen bug. Textinfo is to be blamed because it breaks things that previously work. :-( Anyway, I've sent a patch to xen-devel with you CC'ed. Please try that patch. Wei. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Thu Feb 21 17:36:05 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 21 Feb 2013 17:36: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 1U8a2y-0004Xc-AO; Thu, 21 Feb 2013 17:35:04 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U8a2w-0004XT-VW for xen-users@lists.xen.org; Thu, 21 Feb 2013 17:35:03 +0000 Received: from [193.109.254.147:52260] by server-9.bemta-14.messagelabs.com id 5E/19-30867-6CA56215; Thu, 21 Feb 2013 17:35:02 +0000 X-Env-Sender: jason.vas.dias@gmail.com X-Msg-Ref: server-13.tower-27.messagelabs.com!1361467767!8735461!1 X-Originating-IP: [74.125.83.50] 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.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 8790 invoked from network); 21 Feb 2013 17:29:28 -0000 Received: from mail-ee0-f50.google.com (HELO mail-ee0-f50.google.com) (74.125.83.50) by server-13.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 21 Feb 2013 17:29:28 -0000 Received: by mail-ee0-f50.google.com with SMTP id e51so4874904eek.9 for ; Thu, 21 Feb 2013 09:29:26 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:date:message-id:subject:from:to :content-type; bh=+9M5q5NCAPGpY7aZFatX/Rncrm5jws8zghyO/L1YmTU=; b=hyEJK6f26VCY6064OyHNtP2EjXhGOkaTzgSFhaw5ul0tL7QaFlzVAo9uWL3S9uoIcJ M52+rLaZcE9rNMq1798OVbHz3nceMuA7i5NYR6JbDAH7xujvyr9RUG7zzcXlK3gRjDJC Cfavs+7JiwK8sJ5GD/ZZRFY75O4fNAIn5kArQYJOmDwBP8s+fXurG1iP42QWoDIp61K0 r/IS+xBBRdo56OpYdbYKG34b4vtaKlhB69i54+W+opuHke7FUFi2NGcKt+nfk8rnQyMn 5FvLU+dy9JjZGSPWtS3abinJ129YWeEeQTuh00rGb4ERKTs56KdimY3IWRn5fmcBUKjL cpsQ== MIME-Version: 1.0 X-Received: by 10.14.211.132 with SMTP id w4mr81888750eeo.36.1361467766432; Thu, 21 Feb 2013 09:29:26 -0800 (PST) Received: by 10.223.73.204 with HTTP; Thu, 21 Feb 2013 09:29:26 -0800 (PST) Date: Thu, 21 Feb 2013 17:29:26 +0000 Message-ID: From: Jason Vas Dias To: xen-users@lists.xen.org Subject: [Xen-users] help please - running a guest from an iSCSI disk ? getting more diagnostics than "cannot make domain: -3" ? how to make domain0 "privileged" ? X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: 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 day - This is my first post to this list , and I'm new to Xen - any help on this issue would be much appreciated . I downloaded, built and installed xen-4.2.1 (hypervisor and tools) on an x86_64 ArchLinux box updated to latest software as of today. I am trying to bring up a Linux guest from a remote iSCSI disk. The iSCSI-initiator (open-iscsi) logs in to the remote target OK and makes it available as /dev/sde , on which is a bootable linux distribution . containing /boot/vmlinuz* etc. I can mount this iSCSI disk rw OK on the domain_0 host - so presumably I should be able to boot up a guest domain from it ? I modified the domain_0 host's boot arguments to boot Xen OK : multiboot /boot/xen.gz dom0_mem=1024M loglvl=all guest_loglvl=all module /boot/vmlinuz-linux root=/dev/sda2 ro debug module /boot/initramfs-linux.img and made an /etc/xen/${domain}.cfg file: # # xl.cfg(1) file for booting the iSCSI share: # name="$domain" #vcpus=1 #uuid="ceb083a2-feaa-45b0-afe2-3bd44eb4d8c3" memory=1024 on_poweroff="destroy" on_reboot="destroy" disk=["/dev/sde,raw,hda,rw"] vif=["mac=00:09:3d:13:0d:57,model=tg3,bridge=xenbr0"] kernel="/boot/vmlinuz-2.6.39-300.26.1.el6uek.x86_64" ramdisk="/boot/initramfs-2.6.39-300.26.1.el6uek.x86_64.img" Is the disk line OK ? Anything else wrong with this file ? But attempting to create the domain , as root, fails: # xl -vvv create -c /etc/xen/${domain}.cfg Parsing config from ${domain}.cfg libxl: debug: libxl_create.c:1174:do_domain_create: ao 0x119c890: create: how=(nil) callback=(nil) poller=0x119c920 libxl: error: libxl_create.c:420:libxl__domain_make: domain creation fail libxl: error: libxl_create.c:646:initiate_domain_create: cannot make domain: -3 libxl: error: libxl.c:1394:libxl__destroy_domid: non-existant domain -1 libxl: error: libxl.c:1358:domain_destroy_callback: unable to destroy guest with domid 4294967295 libxl: error: libxl_create.c:1153:domcreate_destruction_cb: unable to destroy domain 4294967295 following failed creation libxl: debug: libxl_event.c:1499:libxl__ao_complete: ao 0x119c890: complete, rc=-3 libxl: debug: libxl_create.c:1187:do_domain_create: ao 0x119c890: inprogress: poller=0x119c920, flags=ic libxl: debug: libxl_event.c:1471:libxl__ao__destroy: ao 0x119c890: destroy xc: debug: hypercall buffer: total allocations:5 total releases:5 xc: debug: hypercall buffer: current allocations:0 maximum allocations:2 xc: debug: hypercall buffer: cache current size:2 xc: debug: hypercall buffer: cache hits:3 misses:2 toobig:0 Even though I've enabled all possible log messages in Xen with ' loglvl=all guest_loglvl=all' (or have I?) I don't see any log messages about this failed attempt to create a domain at all , in dmesg output or in the system log. Tracing this command in gdb shows the hypervisor command is returning -1, with errno set to 1 (EPERM) : libxl: debug: libxl_create.c:1174:do_domain_create: ao 0x622890: create: how=(nil) callback=(nil) poller=0x622920 Breakpoint 2, xc_domain_create (xch=0x622240, ssidref=0, handle=handle@entry=0x7fffffffe1b0 "\316\260\203\242\376\252E\260\257\342;\324N\264\330\303\031", flags=flags@entry=0, pdomid=pdomid@entry=0x7fffffffe28c) at xc_domain.c:33 33 { (gdb) n 37 domctl.cmd = XEN_DOMCTL_createdomain; (gdb) 38 domctl.domain = (domid_t)*pdomid; (gdb) 39 domctl.u.createdomain.ssidref = ssidref; (gdb) 40 domctl.u.createdomain.flags = flags; (gdb) 41 memcpy(domctl.u.createdomain.handle, handle, sizeof(xen_domain_handle_t)); (gdb) 42 if ( (err = do_domctl(xch, &domctl)) != 0 ) (gdb) s do_domctl (domctl=0x7fffffffe0a0, xch=0x622240) at xc_private.h:239 239 DECLARE_HYPERCALL_BOUNCE(domctl, sizeof(*domctl), XC_HYPERCALL_BUFFER_BOUNCE_BOTH); (gdb) n 241 domctl->interface_version = XEN_DOMCTL_INTERFACE_VERSION; (gdb) 243 if ( xc_hypercall_bounce_pre(xch, domctl) ) (gdb) 249 hypercall.op = __HYPERVISOR_domctl; (gdb) 250 hypercall.arg[0] = HYPERCALL_BUFFER_AS_ARG(domctl); (gdb) 252 if ( (ret = do_xen_hypercall(xch, &hypercall)) < 0 ) (gdb) s do_xen_hypercall (xch=xch@entry=0x622240, hypercall=hypercall@entry=0x7fffffffe070) at xc_private.c:246 246 return xch->ops->u.privcmd.hypercall(xch, xch->ops_handle, hypercall); (gdb) s linux_privcmd_hypercall (xch=, h=9, hypercall=0x7fffffffe070) at xc_linux_osdep.c:116 116 return ioctl(fd, IOCTL_PRIVCMD_HYPERCALL, hypercall); (gdb) fin Run till exit from #0 linux_privcmd_hypercall (xch=, h=9, hypercall=0x7fffffffe070) at xc_linux_osdep.c:116 do_xen_hypercall (xch=xch@entry=0x622240, hypercall=hypercall@entry=0x7fffffffe070) at xc_private.c:247 247 } Value returned is $3 = -1 (gdb) fin Run till exit from #0 do_xen_hypercall (xch=xch@entry=0x622240, hypercall=hypercall@entry=0x7fffffffe070) at xc_private.c:247 0x00007ffff775b340 in do_domctl (domctl=0x7fffffffe0a0, xch=0x622240) at xc_private.h:252 252 if ( (ret = do_xen_hypercall(xch, &hypercall)) < 0 ) Value returned is $4 = -1 (gdb) p errno $5 = 1 Any ideas how to get this working, or on where I could get better diagnostics ? I'm guessing this is caused by this code in arch/x86/platform_hypercall.c : ret_t do_platform_op(XEN_GUEST_HANDLE(xen_platform_op_t) u_xenpf_op) { ret_t ret = 0; struct xen_platform_op curop, *op = &curop; if ( !IS_PRIV(current->domain) ) return -EPERM; So how do I make the IS_PRIV macro return non-zero for my domain_0 , ie. set d->is_privileged / make my domain0 into a "privileged" domain ? What is meant by "privileged" in this context ? There seems to be no documentation on this issue in any manual page installed by xen's 'make install' , or anywhere else I could find. Thanks in advance for any replies, Regards, Jason _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Thu Feb 21 17:36:05 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 21 Feb 2013 17:36: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 1U8a2y-0004Xc-AO; Thu, 21 Feb 2013 17:35:04 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U8a2w-0004XT-VW for xen-users@lists.xen.org; Thu, 21 Feb 2013 17:35:03 +0000 Received: from [193.109.254.147:52260] by server-9.bemta-14.messagelabs.com id 5E/19-30867-6CA56215; Thu, 21 Feb 2013 17:35:02 +0000 X-Env-Sender: jason.vas.dias@gmail.com X-Msg-Ref: server-13.tower-27.messagelabs.com!1361467767!8735461!1 X-Originating-IP: [74.125.83.50] 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.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 8790 invoked from network); 21 Feb 2013 17:29:28 -0000 Received: from mail-ee0-f50.google.com (HELO mail-ee0-f50.google.com) (74.125.83.50) by server-13.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 21 Feb 2013 17:29:28 -0000 Received: by mail-ee0-f50.google.com with SMTP id e51so4874904eek.9 for ; Thu, 21 Feb 2013 09:29:26 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:date:message-id:subject:from:to :content-type; bh=+9M5q5NCAPGpY7aZFatX/Rncrm5jws8zghyO/L1YmTU=; b=hyEJK6f26VCY6064OyHNtP2EjXhGOkaTzgSFhaw5ul0tL7QaFlzVAo9uWL3S9uoIcJ M52+rLaZcE9rNMq1798OVbHz3nceMuA7i5NYR6JbDAH7xujvyr9RUG7zzcXlK3gRjDJC Cfavs+7JiwK8sJ5GD/ZZRFY75O4fNAIn5kArQYJOmDwBP8s+fXurG1iP42QWoDIp61K0 r/IS+xBBRdo56OpYdbYKG34b4vtaKlhB69i54+W+opuHke7FUFi2NGcKt+nfk8rnQyMn 5FvLU+dy9JjZGSPWtS3abinJ129YWeEeQTuh00rGb4ERKTs56KdimY3IWRn5fmcBUKjL cpsQ== MIME-Version: 1.0 X-Received: by 10.14.211.132 with SMTP id w4mr81888750eeo.36.1361467766432; Thu, 21 Feb 2013 09:29:26 -0800 (PST) Received: by 10.223.73.204 with HTTP; Thu, 21 Feb 2013 09:29:26 -0800 (PST) Date: Thu, 21 Feb 2013 17:29:26 +0000 Message-ID: From: Jason Vas Dias To: xen-users@lists.xen.org Subject: [Xen-users] help please - running a guest from an iSCSI disk ? getting more diagnostics than "cannot make domain: -3" ? how to make domain0 "privileged" ? X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: 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 day - This is my first post to this list , and I'm new to Xen - any help on this issue would be much appreciated . I downloaded, built and installed xen-4.2.1 (hypervisor and tools) on an x86_64 ArchLinux box updated to latest software as of today. I am trying to bring up a Linux guest from a remote iSCSI disk. The iSCSI-initiator (open-iscsi) logs in to the remote target OK and makes it available as /dev/sde , on which is a bootable linux distribution . containing /boot/vmlinuz* etc. I can mount this iSCSI disk rw OK on the domain_0 host - so presumably I should be able to boot up a guest domain from it ? I modified the domain_0 host's boot arguments to boot Xen OK : multiboot /boot/xen.gz dom0_mem=1024M loglvl=all guest_loglvl=all module /boot/vmlinuz-linux root=/dev/sda2 ro debug module /boot/initramfs-linux.img and made an /etc/xen/${domain}.cfg file: # # xl.cfg(1) file for booting the iSCSI share: # name="$domain" #vcpus=1 #uuid="ceb083a2-feaa-45b0-afe2-3bd44eb4d8c3" memory=1024 on_poweroff="destroy" on_reboot="destroy" disk=["/dev/sde,raw,hda,rw"] vif=["mac=00:09:3d:13:0d:57,model=tg3,bridge=xenbr0"] kernel="/boot/vmlinuz-2.6.39-300.26.1.el6uek.x86_64" ramdisk="/boot/initramfs-2.6.39-300.26.1.el6uek.x86_64.img" Is the disk line OK ? Anything else wrong with this file ? But attempting to create the domain , as root, fails: # xl -vvv create -c /etc/xen/${domain}.cfg Parsing config from ${domain}.cfg libxl: debug: libxl_create.c:1174:do_domain_create: ao 0x119c890: create: how=(nil) callback=(nil) poller=0x119c920 libxl: error: libxl_create.c:420:libxl__domain_make: domain creation fail libxl: error: libxl_create.c:646:initiate_domain_create: cannot make domain: -3 libxl: error: libxl.c:1394:libxl__destroy_domid: non-existant domain -1 libxl: error: libxl.c:1358:domain_destroy_callback: unable to destroy guest with domid 4294967295 libxl: error: libxl_create.c:1153:domcreate_destruction_cb: unable to destroy domain 4294967295 following failed creation libxl: debug: libxl_event.c:1499:libxl__ao_complete: ao 0x119c890: complete, rc=-3 libxl: debug: libxl_create.c:1187:do_domain_create: ao 0x119c890: inprogress: poller=0x119c920, flags=ic libxl: debug: libxl_event.c:1471:libxl__ao__destroy: ao 0x119c890: destroy xc: debug: hypercall buffer: total allocations:5 total releases:5 xc: debug: hypercall buffer: current allocations:0 maximum allocations:2 xc: debug: hypercall buffer: cache current size:2 xc: debug: hypercall buffer: cache hits:3 misses:2 toobig:0 Even though I've enabled all possible log messages in Xen with ' loglvl=all guest_loglvl=all' (or have I?) I don't see any log messages about this failed attempt to create a domain at all , in dmesg output or in the system log. Tracing this command in gdb shows the hypervisor command is returning -1, with errno set to 1 (EPERM) : libxl: debug: libxl_create.c:1174:do_domain_create: ao 0x622890: create: how=(nil) callback=(nil) poller=0x622920 Breakpoint 2, xc_domain_create (xch=0x622240, ssidref=0, handle=handle@entry=0x7fffffffe1b0 "\316\260\203\242\376\252E\260\257\342;\324N\264\330\303\031", flags=flags@entry=0, pdomid=pdomid@entry=0x7fffffffe28c) at xc_domain.c:33 33 { (gdb) n 37 domctl.cmd = XEN_DOMCTL_createdomain; (gdb) 38 domctl.domain = (domid_t)*pdomid; (gdb) 39 domctl.u.createdomain.ssidref = ssidref; (gdb) 40 domctl.u.createdomain.flags = flags; (gdb) 41 memcpy(domctl.u.createdomain.handle, handle, sizeof(xen_domain_handle_t)); (gdb) 42 if ( (err = do_domctl(xch, &domctl)) != 0 ) (gdb) s do_domctl (domctl=0x7fffffffe0a0, xch=0x622240) at xc_private.h:239 239 DECLARE_HYPERCALL_BOUNCE(domctl, sizeof(*domctl), XC_HYPERCALL_BUFFER_BOUNCE_BOTH); (gdb) n 241 domctl->interface_version = XEN_DOMCTL_INTERFACE_VERSION; (gdb) 243 if ( xc_hypercall_bounce_pre(xch, domctl) ) (gdb) 249 hypercall.op = __HYPERVISOR_domctl; (gdb) 250 hypercall.arg[0] = HYPERCALL_BUFFER_AS_ARG(domctl); (gdb) 252 if ( (ret = do_xen_hypercall(xch, &hypercall)) < 0 ) (gdb) s do_xen_hypercall (xch=xch@entry=0x622240, hypercall=hypercall@entry=0x7fffffffe070) at xc_private.c:246 246 return xch->ops->u.privcmd.hypercall(xch, xch->ops_handle, hypercall); (gdb) s linux_privcmd_hypercall (xch=, h=9, hypercall=0x7fffffffe070) at xc_linux_osdep.c:116 116 return ioctl(fd, IOCTL_PRIVCMD_HYPERCALL, hypercall); (gdb) fin Run till exit from #0 linux_privcmd_hypercall (xch=, h=9, hypercall=0x7fffffffe070) at xc_linux_osdep.c:116 do_xen_hypercall (xch=xch@entry=0x622240, hypercall=hypercall@entry=0x7fffffffe070) at xc_private.c:247 247 } Value returned is $3 = -1 (gdb) fin Run till exit from #0 do_xen_hypercall (xch=xch@entry=0x622240, hypercall=hypercall@entry=0x7fffffffe070) at xc_private.c:247 0x00007ffff775b340 in do_domctl (domctl=0x7fffffffe0a0, xch=0x622240) at xc_private.h:252 252 if ( (ret = do_xen_hypercall(xch, &hypercall)) < 0 ) Value returned is $4 = -1 (gdb) p errno $5 = 1 Any ideas how to get this working, or on where I could get better diagnostics ? I'm guessing this is caused by this code in arch/x86/platform_hypercall.c : ret_t do_platform_op(XEN_GUEST_HANDLE(xen_platform_op_t) u_xenpf_op) { ret_t ret = 0; struct xen_platform_op curop, *op = &curop; if ( !IS_PRIV(current->domain) ) return -EPERM; So how do I make the IS_PRIV macro return non-zero for my domain_0 , ie. set d->is_privileged / make my domain0 into a "privileged" domain ? What is meant by "privileged" in this context ? There seems to be no documentation on this issue in any manual page installed by xen's 'make install' , or anywhere else I could find. Thanks in advance for any replies, Regards, Jason _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Thu Feb 21 18:54:35 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 21 Feb 2013 18:54: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 1U8bGo-00019Y-2O; Thu, 21 Feb 2013 18:53:26 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U8bGm-00019T-At for xen-users@lists.xen.org; Thu, 21 Feb 2013 18:53:24 +0000 Received: from [85.158.143.99:53833] by server-1.bemta-4.messagelabs.com id 65/5F-06203-32D66215; Thu, 21 Feb 2013 18:53:23 +0000 X-Env-Sender: jason.vas.dias@gmail.com X-Msg-Ref: server-16.tower-216.messagelabs.com!1361472800!17163850!1 X-Originating-IP: [74.125.83.49] 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.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 25802 invoked from network); 21 Feb 2013 18:53:20 -0000 Received: from mail-ee0-f49.google.com (HELO mail-ee0-f49.google.com) (74.125.83.49) by server-16.tower-216.messagelabs.com with RC4-SHA encrypted SMTP; 21 Feb 2013 18:53:20 -0000 Received: by mail-ee0-f49.google.com with SMTP id d41so49847eek.22 for ; Thu, 21 Feb 2013 10:53:20 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:content-type; bh=hz3xUMqcX3wnNK+Cu8ZHXjWIRF9whlZx6La44110Dqo=; b=06dnlde1141f8yXhX6qWv7xK5wo0e2xWFMQ3M6amnRVRFlPDstNxp+XB2TCEV4l/cF 6r2623VW2pEMzPQboARmSMv2OjgF9A6gj1a4vDdcY9M/qOGy1Adg0/+pynCBgQYPjg/O LOHLnlq8iD+UBQbZhnctNZiLCajuRFutKVK8XHoNECl2O65l+lhuNlaelBeoTeVspFvI hPbV5j53d6wCwWFvpxMSlYnv3/j2veBqspeSy40DJgZzGOt4BDGetBFq+7XPmFmB9ZHw 9dGH+bhuXetc3B3hnxJ0EKJ8BmHShtiWOsvP4WeKx32EAl9jvi6jCB68HZ0Qfyjox+ll QPOQ== MIME-Version: 1.0 X-Received: by 10.14.4.69 with SMTP id 45mr84178767eei.0.1361472800228; Thu, 21 Feb 2013 10:53:20 -0800 (PST) Received: by 10.223.73.204 with HTTP; Thu, 21 Feb 2013 10:53:20 -0800 (PST) In-Reply-To: References: Date: Thu, 21 Feb 2013 18:53:20 +0000 Message-ID: From: Jason Vas Dias To: xen-users@lists.xen.org Subject: Re: [Xen-users] help please - running a guest from an iSCSI disk ? getting more diagnostics than "cannot make domain: -3" ? how to make domain0 "privileged" ? X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org Aha! Finally I discovered 'xl dmesg' and saw 'Xen does not allow DomU creation on this CPU for security reasons.' o why not give an option to make Xen write to the standard kernel log, so I could have found this message with 'dmesg' ? It is far from obvious from the documentation that this the only way of seeing Xen log messages . It appears the dom0 CPU has AMD Errata 121 - see: http://lists.xen.org/archives/html/xen-announce/2012-06/msg00002.html But since both my dom0 kernel (3.7.9-1-ARCH) and my domU kernel (2.6.39-300.26.1.el6uek) apparently have the fix for this errata , I added 'allow_unsafe' to the Xen dom0 boot command line, and I'm now able to progress beyond the EPERM issue . It would have been nice if Xen or xl could have emitted some log message other than 'cannot make domain: -3', particularly when it was Xen itself that was refusing to allow the domain creation to proceed . It would also have been nice if Xen could have recognized that it was running kernels with the fix for this issue, and NOT silently disabled domain creation. Regards, Jason On Thu, Feb 21, 2013 at 5:29 PM, Jason Vas Dias wrote: > Good day - > > This is my first post to this list , and I'm new to Xen - any help on > this issue would be much appreciated . > > I downloaded, built and installed xen-4.2.1 (hypervisor and tools) on > an x86_64 ArchLinux box > updated to latest software as of today. > > I am trying to bring up a Linux guest from a remote iSCSI disk. > > The iSCSI-initiator (open-iscsi) logs in to the remote target OK and > makes it available as /dev/sde , > on which is a bootable linux distribution . containing /boot/vmlinuz* etc. > I can mount this iSCSI disk rw OK on the domain_0 host - so presumably > I should be able to > boot up a guest domain from it ? > > I modified the domain_0 host's boot arguments to boot Xen OK : > > multiboot /boot/xen.gz dom0_mem=1024M loglvl=all guest_loglvl=all > module /boot/vmlinuz-linux root=/dev/sda2 ro debug > module /boot/initramfs-linux.img > > and made an /etc/xen/${domain}.cfg file: > # > # xl.cfg(1) file for booting the iSCSI share: > # > name="$domain" > #vcpus=1 > #uuid="ceb083a2-feaa-45b0-afe2-3bd44eb4d8c3" > memory=1024 > on_poweroff="destroy" > on_reboot="destroy" > disk=["/dev/sde,raw,hda,rw"] > vif=["mac=00:09:3d:13:0d:57,model=tg3,bridge=xenbr0"] > kernel="/boot/vmlinuz-2.6.39-300.26.1.el6uek.x86_64" > ramdisk="/boot/initramfs-2.6.39-300.26.1.el6uek.x86_64.img" > > Is the disk line OK ? Anything else wrong with this file ? > > But attempting to create the domain , as root, fails: > # xl -vvv create -c /etc/xen/${domain}.cfg > Parsing config from ${domain}.cfg > libxl: debug: libxl_create.c:1174:do_domain_create: ao 0x119c890: > create: how=(nil) callback=(nil) poller=0x119c920 > libxl: error: libxl_create.c:420:libxl__domain_make: domain creation fail > libxl: error: libxl_create.c:646:initiate_domain_create: cannot make domain: -3 > libxl: error: libxl.c:1394:libxl__destroy_domid: non-existant domain -1 > libxl: error: libxl.c:1358:domain_destroy_callback: unable to destroy > guest with domid 4294967295 > libxl: error: libxl_create.c:1153:domcreate_destruction_cb: unable to > destroy domain 4294967295 following failed creation > libxl: debug: libxl_event.c:1499:libxl__ao_complete: ao 0x119c890: > complete, rc=-3 > libxl: debug: libxl_create.c:1187:do_domain_create: ao 0x119c890: > inprogress: poller=0x119c920, flags=ic > libxl: debug: libxl_event.c:1471:libxl__ao__destroy: ao 0x119c890: destroy > xc: debug: hypercall buffer: total allocations:5 total releases:5 > xc: debug: hypercall buffer: current allocations:0 maximum allocations:2 > xc: debug: hypercall buffer: cache current size:2 > xc: debug: hypercall buffer: cache hits:3 misses:2 toobig:0 > > Even though I've enabled all possible log messages in Xen with ' > loglvl=all guest_loglvl=all' (or have I?) > I don't see any log messages about this failed attempt to create a > domain at all , in dmesg output or > in the system log. > > Tracing this command in gdb shows the hypervisor command is returning > -1, with errno set to 1 (EPERM) : > > libxl: debug: libxl_create.c:1174:do_domain_create: ao 0x622890: > create: how=(nil) callback=(nil) poller=0x622920 > > Breakpoint 2, xc_domain_create (xch=0x622240, ssidref=0, > handle=handle@entry=0x7fffffffe1b0 > "\316\260\203\242\376\252E\260\257\342;\324N\264\330\303\031", > flags=flags@entry=0, pdomid=pdomid@entry=0x7fffffffe28c) at xc_domain.c:33 > 33 { > (gdb) n > 37 domctl.cmd = XEN_DOMCTL_createdomain; > (gdb) > 38 domctl.domain = (domid_t)*pdomid; > (gdb) > 39 domctl.u.createdomain.ssidref = ssidref; > (gdb) > 40 domctl.u.createdomain.flags = flags; > (gdb) > 41 memcpy(domctl.u.createdomain.handle, handle, > sizeof(xen_domain_handle_t)); > (gdb) > 42 if ( (err = do_domctl(xch, &domctl)) != 0 ) > (gdb) s > do_domctl (domctl=0x7fffffffe0a0, xch=0x622240) at xc_private.h:239 > 239 DECLARE_HYPERCALL_BOUNCE(domctl, sizeof(*domctl), > XC_HYPERCALL_BUFFER_BOUNCE_BOTH); > (gdb) n > 241 domctl->interface_version = XEN_DOMCTL_INTERFACE_VERSION; > (gdb) > 243 if ( xc_hypercall_bounce_pre(xch, domctl) ) > (gdb) > 249 hypercall.op = __HYPERVISOR_domctl; > (gdb) > 250 hypercall.arg[0] = HYPERCALL_BUFFER_AS_ARG(domctl); > (gdb) > 252 if ( (ret = do_xen_hypercall(xch, &hypercall)) < 0 ) > (gdb) s > do_xen_hypercall (xch=xch@entry=0x622240, > hypercall=hypercall@entry=0x7fffffffe070) at xc_private.c:246 > 246 return xch->ops->u.privcmd.hypercall(xch, xch->ops_handle, > hypercall); > (gdb) s > linux_privcmd_hypercall (xch=, h=9, > hypercall=0x7fffffffe070) at xc_linux_osdep.c:116 > 116 return ioctl(fd, IOCTL_PRIVCMD_HYPERCALL, hypercall); > (gdb) fin > Run till exit from #0 linux_privcmd_hypercall (xch=, > h=9, hypercall=0x7fffffffe070) at xc_linux_osdep.c:116 > do_xen_hypercall (xch=xch@entry=0x622240, > hypercall=hypercall@entry=0x7fffffffe070) at xc_private.c:247 > 247 } > Value returned is $3 = -1 > (gdb) fin > Run till exit from #0 do_xen_hypercall (xch=xch@entry=0x622240, > hypercall=hypercall@entry=0x7fffffffe070) at xc_private.c:247 > 0x00007ffff775b340 in do_domctl (domctl=0x7fffffffe0a0, xch=0x622240) > at xc_private.h:252 > 252 if ( (ret = do_xen_hypercall(xch, &hypercall)) < 0 ) > Value returned is $4 = -1 > (gdb) p errno > $5 = 1 > > Any ideas how to get this working, or on where I could get better > diagnostics ? > > I'm guessing this is caused by this code in arch/x86/platform_hypercall.c : > > ret_t do_platform_op(XEN_GUEST_HANDLE(xen_platform_op_t) u_xenpf_op) > { > ret_t ret = 0; > struct xen_platform_op curop, *op = &curop; > > if ( !IS_PRIV(current->domain) ) > return -EPERM; > > So how do I make the IS_PRIV macro return non-zero for my domain_0 , > ie. set d->is_privileged / > make my domain0 into a "privileged" domain ? What is meant by > "privileged" in this context ? > > There seems to be no documentation on this issue in any manual page > installed by xen's 'make install' , > or anywhere else I could find. > > Thanks in advance for any replies, > Regards, Jason _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Thu Feb 21 18:54:35 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 21 Feb 2013 18:54: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 1U8bGo-00019Y-2O; Thu, 21 Feb 2013 18:53:26 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U8bGm-00019T-At for xen-users@lists.xen.org; Thu, 21 Feb 2013 18:53:24 +0000 Received: from [85.158.143.99:53833] by server-1.bemta-4.messagelabs.com id 65/5F-06203-32D66215; Thu, 21 Feb 2013 18:53:23 +0000 X-Env-Sender: jason.vas.dias@gmail.com X-Msg-Ref: server-16.tower-216.messagelabs.com!1361472800!17163850!1 X-Originating-IP: [74.125.83.49] 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.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 25802 invoked from network); 21 Feb 2013 18:53:20 -0000 Received: from mail-ee0-f49.google.com (HELO mail-ee0-f49.google.com) (74.125.83.49) by server-16.tower-216.messagelabs.com with RC4-SHA encrypted SMTP; 21 Feb 2013 18:53:20 -0000 Received: by mail-ee0-f49.google.com with SMTP id d41so49847eek.22 for ; Thu, 21 Feb 2013 10:53:20 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:content-type; bh=hz3xUMqcX3wnNK+Cu8ZHXjWIRF9whlZx6La44110Dqo=; b=06dnlde1141f8yXhX6qWv7xK5wo0e2xWFMQ3M6amnRVRFlPDstNxp+XB2TCEV4l/cF 6r2623VW2pEMzPQboARmSMv2OjgF9A6gj1a4vDdcY9M/qOGy1Adg0/+pynCBgQYPjg/O LOHLnlq8iD+UBQbZhnctNZiLCajuRFutKVK8XHoNECl2O65l+lhuNlaelBeoTeVspFvI hPbV5j53d6wCwWFvpxMSlYnv3/j2veBqspeSy40DJgZzGOt4BDGetBFq+7XPmFmB9ZHw 9dGH+bhuXetc3B3hnxJ0EKJ8BmHShtiWOsvP4WeKx32EAl9jvi6jCB68HZ0Qfyjox+ll QPOQ== MIME-Version: 1.0 X-Received: by 10.14.4.69 with SMTP id 45mr84178767eei.0.1361472800228; Thu, 21 Feb 2013 10:53:20 -0800 (PST) Received: by 10.223.73.204 with HTTP; Thu, 21 Feb 2013 10:53:20 -0800 (PST) In-Reply-To: References: Date: Thu, 21 Feb 2013 18:53:20 +0000 Message-ID: From: Jason Vas Dias To: xen-users@lists.xen.org Subject: Re: [Xen-users] help please - running a guest from an iSCSI disk ? getting more diagnostics than "cannot make domain: -3" ? how to make domain0 "privileged" ? X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org Aha! Finally I discovered 'xl dmesg' and saw 'Xen does not allow DomU creation on this CPU for security reasons.' o why not give an option to make Xen write to the standard kernel log, so I could have found this message with 'dmesg' ? It is far from obvious from the documentation that this the only way of seeing Xen log messages . It appears the dom0 CPU has AMD Errata 121 - see: http://lists.xen.org/archives/html/xen-announce/2012-06/msg00002.html But since both my dom0 kernel (3.7.9-1-ARCH) and my domU kernel (2.6.39-300.26.1.el6uek) apparently have the fix for this errata , I added 'allow_unsafe' to the Xen dom0 boot command line, and I'm now able to progress beyond the EPERM issue . It would have been nice if Xen or xl could have emitted some log message other than 'cannot make domain: -3', particularly when it was Xen itself that was refusing to allow the domain creation to proceed . It would also have been nice if Xen could have recognized that it was running kernels with the fix for this issue, and NOT silently disabled domain creation. Regards, Jason On Thu, Feb 21, 2013 at 5:29 PM, Jason Vas Dias wrote: > Good day - > > This is my first post to this list , and I'm new to Xen - any help on > this issue would be much appreciated . > > I downloaded, built and installed xen-4.2.1 (hypervisor and tools) on > an x86_64 ArchLinux box > updated to latest software as of today. > > I am trying to bring up a Linux guest from a remote iSCSI disk. > > The iSCSI-initiator (open-iscsi) logs in to the remote target OK and > makes it available as /dev/sde , > on which is a bootable linux distribution . containing /boot/vmlinuz* etc. > I can mount this iSCSI disk rw OK on the domain_0 host - so presumably > I should be able to > boot up a guest domain from it ? > > I modified the domain_0 host's boot arguments to boot Xen OK : > > multiboot /boot/xen.gz dom0_mem=1024M loglvl=all guest_loglvl=all > module /boot/vmlinuz-linux root=/dev/sda2 ro debug > module /boot/initramfs-linux.img > > and made an /etc/xen/${domain}.cfg file: > # > # xl.cfg(1) file for booting the iSCSI share: > # > name="$domain" > #vcpus=1 > #uuid="ceb083a2-feaa-45b0-afe2-3bd44eb4d8c3" > memory=1024 > on_poweroff="destroy" > on_reboot="destroy" > disk=["/dev/sde,raw,hda,rw"] > vif=["mac=00:09:3d:13:0d:57,model=tg3,bridge=xenbr0"] > kernel="/boot/vmlinuz-2.6.39-300.26.1.el6uek.x86_64" > ramdisk="/boot/initramfs-2.6.39-300.26.1.el6uek.x86_64.img" > > Is the disk line OK ? Anything else wrong with this file ? > > But attempting to create the domain , as root, fails: > # xl -vvv create -c /etc/xen/${domain}.cfg > Parsing config from ${domain}.cfg > libxl: debug: libxl_create.c:1174:do_domain_create: ao 0x119c890: > create: how=(nil) callback=(nil) poller=0x119c920 > libxl: error: libxl_create.c:420:libxl__domain_make: domain creation fail > libxl: error: libxl_create.c:646:initiate_domain_create: cannot make domain: -3 > libxl: error: libxl.c:1394:libxl__destroy_domid: non-existant domain -1 > libxl: error: libxl.c:1358:domain_destroy_callback: unable to destroy > guest with domid 4294967295 > libxl: error: libxl_create.c:1153:domcreate_destruction_cb: unable to > destroy domain 4294967295 following failed creation > libxl: debug: libxl_event.c:1499:libxl__ao_complete: ao 0x119c890: > complete, rc=-3 > libxl: debug: libxl_create.c:1187:do_domain_create: ao 0x119c890: > inprogress: poller=0x119c920, flags=ic > libxl: debug: libxl_event.c:1471:libxl__ao__destroy: ao 0x119c890: destroy > xc: debug: hypercall buffer: total allocations:5 total releases:5 > xc: debug: hypercall buffer: current allocations:0 maximum allocations:2 > xc: debug: hypercall buffer: cache current size:2 > xc: debug: hypercall buffer: cache hits:3 misses:2 toobig:0 > > Even though I've enabled all possible log messages in Xen with ' > loglvl=all guest_loglvl=all' (or have I?) > I don't see any log messages about this failed attempt to create a > domain at all , in dmesg output or > in the system log. > > Tracing this command in gdb shows the hypervisor command is returning > -1, with errno set to 1 (EPERM) : > > libxl: debug: libxl_create.c:1174:do_domain_create: ao 0x622890: > create: how=(nil) callback=(nil) poller=0x622920 > > Breakpoint 2, xc_domain_create (xch=0x622240, ssidref=0, > handle=handle@entry=0x7fffffffe1b0 > "\316\260\203\242\376\252E\260\257\342;\324N\264\330\303\031", > flags=flags@entry=0, pdomid=pdomid@entry=0x7fffffffe28c) at xc_domain.c:33 > 33 { > (gdb) n > 37 domctl.cmd = XEN_DOMCTL_createdomain; > (gdb) > 38 domctl.domain = (domid_t)*pdomid; > (gdb) > 39 domctl.u.createdomain.ssidref = ssidref; > (gdb) > 40 domctl.u.createdomain.flags = flags; > (gdb) > 41 memcpy(domctl.u.createdomain.handle, handle, > sizeof(xen_domain_handle_t)); > (gdb) > 42 if ( (err = do_domctl(xch, &domctl)) != 0 ) > (gdb) s > do_domctl (domctl=0x7fffffffe0a0, xch=0x622240) at xc_private.h:239 > 239 DECLARE_HYPERCALL_BOUNCE(domctl, sizeof(*domctl), > XC_HYPERCALL_BUFFER_BOUNCE_BOTH); > (gdb) n > 241 domctl->interface_version = XEN_DOMCTL_INTERFACE_VERSION; > (gdb) > 243 if ( xc_hypercall_bounce_pre(xch, domctl) ) > (gdb) > 249 hypercall.op = __HYPERVISOR_domctl; > (gdb) > 250 hypercall.arg[0] = HYPERCALL_BUFFER_AS_ARG(domctl); > (gdb) > 252 if ( (ret = do_xen_hypercall(xch, &hypercall)) < 0 ) > (gdb) s > do_xen_hypercall (xch=xch@entry=0x622240, > hypercall=hypercall@entry=0x7fffffffe070) at xc_private.c:246 > 246 return xch->ops->u.privcmd.hypercall(xch, xch->ops_handle, > hypercall); > (gdb) s > linux_privcmd_hypercall (xch=, h=9, > hypercall=0x7fffffffe070) at xc_linux_osdep.c:116 > 116 return ioctl(fd, IOCTL_PRIVCMD_HYPERCALL, hypercall); > (gdb) fin > Run till exit from #0 linux_privcmd_hypercall (xch=, > h=9, hypercall=0x7fffffffe070) at xc_linux_osdep.c:116 > do_xen_hypercall (xch=xch@entry=0x622240, > hypercall=hypercall@entry=0x7fffffffe070) at xc_private.c:247 > 247 } > Value returned is $3 = -1 > (gdb) fin > Run till exit from #0 do_xen_hypercall (xch=xch@entry=0x622240, > hypercall=hypercall@entry=0x7fffffffe070) at xc_private.c:247 > 0x00007ffff775b340 in do_domctl (domctl=0x7fffffffe0a0, xch=0x622240) > at xc_private.h:252 > 252 if ( (ret = do_xen_hypercall(xch, &hypercall)) < 0 ) > Value returned is $4 = -1 > (gdb) p errno > $5 = 1 > > Any ideas how to get this working, or on where I could get better > diagnostics ? > > I'm guessing this is caused by this code in arch/x86/platform_hypercall.c : > > ret_t do_platform_op(XEN_GUEST_HANDLE(xen_platform_op_t) u_xenpf_op) > { > ret_t ret = 0; > struct xen_platform_op curop, *op = &curop; > > if ( !IS_PRIV(current->domain) ) > return -EPERM; > > So how do I make the IS_PRIV macro return non-zero for my domain_0 , > ie. set d->is_privileged / > make my domain0 into a "privileged" domain ? What is meant by > "privileged" in this context ? > > There seems to be no documentation on this issue in any manual page > installed by xen's 'make install' , > or anywhere else I could find. > > Thanks in advance for any replies, > Regards, Jason _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Thu Feb 21 19:25:47 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 21 Feb 2013 19:25: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 1U8bl6-0002Cp-5u; Thu, 21 Feb 2013 19:24:44 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U8bl3-0002Cj-LW for xen-users@lists.xen.org; Thu, 21 Feb 2013 19:24:42 +0000 Received: from [85.158.138.51:8098] by server-1.bemta-3.messagelabs.com id A1/3D-08955-87476215; Thu, 21 Feb 2013 19:24:40 +0000 X-Env-Sender: jason.vas.dias@gmail.com X-Msg-Ref: server-15.tower-174.messagelabs.com!1361474679!26863847!1 X-Originating-IP: [74.125.83.44] 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.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 26756 invoked from network); 21 Feb 2013 19:24:39 -0000 Received: from mail-ee0-f44.google.com (HELO mail-ee0-f44.google.com) (74.125.83.44) by server-15.tower-174.messagelabs.com with RC4-SHA encrypted SMTP; 21 Feb 2013 19:24:39 -0000 Received: by mail-ee0-f44.google.com with SMTP id l10so4828894eei.17 for ; Thu, 21 Feb 2013 11:24:39 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:content-type; bh=SVNVGRGYccw+Szv+//qE7fWPiGs8hxtRsTvKe1kfJqA=; b=YH6ZqOpO7quwjPe3tlAofjDtLtMXJkJG3oPPKWzfC52s7E5Ktvt4ORGJwUUQcOqaBm TUX7foYIyG4gg20DYFCTNH2SiKrv40zG+6kQg4igAw+by6cV2QnwIV1MMT9TkKlZsVyJ ad8CVXPekva2hAWcSiJKAtQFT1THJsaC9nc4IcvEUCWVZV+IKvrp8WQKuySNwCeActDe kL/OtaLk/wkAOJ/9ifNZQh/uI7OGMPRXX/3ZAaqVIFt/ypm9wA4hUGwObv9aQIaRAljo 4hvKZghsQ/1+HhGd6reXU1CTZgeJseyzdx0poHmhY0wAiTyLcicyFBMrF5YlLBLynCXJ LD/g== MIME-Version: 1.0 X-Received: by 10.14.223.69 with SMTP id u45mr83622218eep.23.1361474679086; Thu, 21 Feb 2013 11:24:39 -0800 (PST) Received: by 10.223.73.204 with HTTP; Thu, 21 Feb 2013 11:24:38 -0800 (PST) In-Reply-To: References: Date: Thu, 21 Feb 2013 19:24:38 +0000 Message-ID: From: Jason Vas Dias To: xen-users@lists.xen.org Subject: Re: [Xen-users] help please - running a guest from an iSCSI disk ? getting more diagnostics than "cannot make domain: -3" ? how to make domain0 "privileged" ? X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: 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 beginning to conclude that Xen is not of sufficient code quality to be useful. Firstly, my 'xl create' command returns a 0 exit status, meaning success, but yet no domain is created or can be attached to or listed with 'xl list' : # xl create my_domain.cfg Parsing config from my_domain.cfg Daemon running with PID 1436 # echo $? 0 # xl list Name ID Mem VCPUs State Time(s) Domain-0 0 1024 2 r----- 35.5 This appears to be due to this error message in 'xl dmesg' output : (XEN) Dom5 may compromise security on this CPU. (XEN) traps.c:2584:d5 Domain attempted WRMSR 00000000c0010004 from 0x0000000000000000 to 0x000000000000abcd. >From reading the source, the traps.c message appears to indicate an error condition, but you would not know this from the log message. Anyone know how to avoid this unhandled WRMSR ? Code that silently ignores and does not report error conditions does not get my vote of confidence. Can anyone convince me that Xen is of sufficient quality to be used ? Regards, Jason On Thu, Feb 21, 2013 at 6:53 PM, Jason Vas Dias wrote: > Aha! Finally I discovered 'xl dmesg' and saw > 'Xen does not allow DomU creation on this CPU for security reasons.' > > o why not give an option to make Xen write to the standard kernel > log, so I could have found this message with 'dmesg' ? > It is far from obvious from the documentation that this the only > way of seeing Xen log messages . > > It appears the dom0 CPU has AMD Errata 121 - see: > http://lists.xen.org/archives/html/xen-announce/2012-06/msg00002.html > > But since both my dom0 kernel (3.7.9-1-ARCH) and my domU kernel > (2.6.39-300.26.1.el6uek) apparently have the fix for this > errata , I added 'allow_unsafe' to the Xen dom0 boot command line, > and I'm now able to progress beyond the EPERM issue . > It would have been nice if Xen or xl could have emitted some log > message other than 'cannot make domain: -3', particularly > when it was Xen itself that was refusing to allow the domain creation > to proceed . > It would also have been nice if Xen could have recognized that it was > running kernels with the fix for this issue, and NOT silently > disabled domain creation. > > Regards, > Jason > > On Thu, Feb 21, 2013 at 5:29 PM, Jason Vas Dias > wrote: >> Good day - >> >> This is my first post to this list , and I'm new to Xen - any help on >> this issue would be much appreciated . >> >> I downloaded, built and installed xen-4.2.1 (hypervisor and tools) on >> an x86_64 ArchLinux box >> updated to latest software as of today. >> >> I am trying to bring up a Linux guest from a remote iSCSI disk. >> >> The iSCSI-initiator (open-iscsi) logs in to the remote target OK and >> makes it available as /dev/sde , >> on which is a bootable linux distribution . containing /boot/vmlinuz* etc. >> I can mount this iSCSI disk rw OK on the domain_0 host - so presumably >> I should be able to >> boot up a guest domain from it ? >> >> I modified the domain_0 host's boot arguments to boot Xen OK : >> >> multiboot /boot/xen.gz dom0_mem=1024M loglvl=all guest_loglvl=all >> module /boot/vmlinuz-linux root=/dev/sda2 ro debug >> module /boot/initramfs-linux.img >> >> and made an /etc/xen/${domain}.cfg file: >> # >> # xl.cfg(1) file for booting the iSCSI share: >> # >> name="$domain" >> #vcpus=1 >> #uuid="ceb083a2-feaa-45b0-afe2-3bd44eb4d8c3" >> memory=1024 >> on_poweroff="destroy" >> on_reboot="destroy" >> disk=["/dev/sde,raw,hda,rw"] >> vif=["mac=00:09:3d:13:0d:57,model=tg3,bridge=xenbr0"] >> kernel="/boot/vmlinuz-2.6.39-300.26.1.el6uek.x86_64" >> ramdisk="/boot/initramfs-2.6.39-300.26.1.el6uek.x86_64.img" >> >> Is the disk line OK ? Anything else wrong with this file ? >> >> But attempting to create the domain , as root, fails: >> # xl -vvv create -c /etc/xen/${domain}.cfg >> Parsing config from ${domain}.cfg >> libxl: debug: libxl_create.c:1174:do_domain_create: ao 0x119c890: >> create: how=(nil) callback=(nil) poller=0x119c920 >> libxl: error: libxl_create.c:420:libxl__domain_make: domain creation fail >> libxl: error: libxl_create.c:646:initiate_domain_create: cannot make domain: -3 >> libxl: error: libxl.c:1394:libxl__destroy_domid: non-existant domain -1 >> libxl: error: libxl.c:1358:domain_destroy_callback: unable to destroy >> guest with domid 4294967295 >> libxl: error: libxl_create.c:1153:domcreate_destruction_cb: unable to >> destroy domain 4294967295 following failed creation >> libxl: debug: libxl_event.c:1499:libxl__ao_complete: ao 0x119c890: >> complete, rc=-3 >> libxl: debug: libxl_create.c:1187:do_domain_create: ao 0x119c890: >> inprogress: poller=0x119c920, flags=ic >> libxl: debug: libxl_event.c:1471:libxl__ao__destroy: ao 0x119c890: destroy >> xc: debug: hypercall buffer: total allocations:5 total releases:5 >> xc: debug: hypercall buffer: current allocations:0 maximum allocations:2 >> xc: debug: hypercall buffer: cache current size:2 >> xc: debug: hypercall buffer: cache hits:3 misses:2 toobig:0 >> >> Even though I've enabled all possible log messages in Xen with ' >> loglvl=all guest_loglvl=all' (or have I?) >> I don't see any log messages about this failed attempt to create a >> domain at all , in dmesg output or >> in the system log. >> >> Tracing this command in gdb shows the hypervisor command is returning >> -1, with errno set to 1 (EPERM) : >> >> libxl: debug: libxl_create.c:1174:do_domain_create: ao 0x622890: >> create: how=(nil) callback=(nil) poller=0x622920 >> >> Breakpoint 2, xc_domain_create (xch=0x622240, ssidref=0, >> handle=handle@entry=0x7fffffffe1b0 >> "\316\260\203\242\376\252E\260\257\342;\324N\264\330\303\031", >> flags=flags@entry=0, pdomid=pdomid@entry=0x7fffffffe28c) at xc_domain.c:33 >> 33 { >> (gdb) n >> 37 domctl.cmd = XEN_DOMCTL_createdomain; >> (gdb) >> 38 domctl.domain = (domid_t)*pdomid; >> (gdb) >> 39 domctl.u.createdomain.ssidref = ssidref; >> (gdb) >> 40 domctl.u.createdomain.flags = flags; >> (gdb) >> 41 memcpy(domctl.u.createdomain.handle, handle, >> sizeof(xen_domain_handle_t)); >> (gdb) >> 42 if ( (err = do_domctl(xch, &domctl)) != 0 ) >> (gdb) s >> do_domctl (domctl=0x7fffffffe0a0, xch=0x622240) at xc_private.h:239 >> 239 DECLARE_HYPERCALL_BOUNCE(domctl, sizeof(*domctl), >> XC_HYPERCALL_BUFFER_BOUNCE_BOTH); >> (gdb) n >> 241 domctl->interface_version = XEN_DOMCTL_INTERFACE_VERSION; >> (gdb) >> 243 if ( xc_hypercall_bounce_pre(xch, domctl) ) >> (gdb) >> 249 hypercall.op = __HYPERVISOR_domctl; >> (gdb) >> 250 hypercall.arg[0] = HYPERCALL_BUFFER_AS_ARG(domctl); >> (gdb) >> 252 if ( (ret = do_xen_hypercall(xch, &hypercall)) < 0 ) >> (gdb) s >> do_xen_hypercall (xch=xch@entry=0x622240, >> hypercall=hypercall@entry=0x7fffffffe070) at xc_private.c:246 >> 246 return xch->ops->u.privcmd.hypercall(xch, xch->ops_handle, >> hypercall); >> (gdb) s >> linux_privcmd_hypercall (xch=, h=9, >> hypercall=0x7fffffffe070) at xc_linux_osdep.c:116 >> 116 return ioctl(fd, IOCTL_PRIVCMD_HYPERCALL, hypercall); >> (gdb) fin >> Run till exit from #0 linux_privcmd_hypercall (xch=, >> h=9, hypercall=0x7fffffffe070) at xc_linux_osdep.c:116 >> do_xen_hypercall (xch=xch@entry=0x622240, >> hypercall=hypercall@entry=0x7fffffffe070) at xc_private.c:247 >> 247 } >> Value returned is $3 = -1 >> (gdb) fin >> Run till exit from #0 do_xen_hypercall (xch=xch@entry=0x622240, >> hypercall=hypercall@entry=0x7fffffffe070) at xc_private.c:247 >> 0x00007ffff775b340 in do_domctl (domctl=0x7fffffffe0a0, xch=0x622240) >> at xc_private.h:252 >> 252 if ( (ret = do_xen_hypercall(xch, &hypercall)) < 0 ) >> Value returned is $4 = -1 >> (gdb) p errno >> $5 = 1 >> >> Any ideas how to get this working, or on where I could get better >> diagnostics ? >> >> I'm guessing this is caused by this code in arch/x86/platform_hypercall.c : >> >> ret_t do_platform_op(XEN_GUEST_HANDLE(xen_platform_op_t) u_xenpf_op) >> { >> ret_t ret = 0; >> struct xen_platform_op curop, *op = &curop; >> >> if ( !IS_PRIV(current->domain) ) >> return -EPERM; >> >> So how do I make the IS_PRIV macro return non-zero for my domain_0 , >> ie. set d->is_privileged / >> make my domain0 into a "privileged" domain ? What is meant by >> "privileged" in this context ? >> >> There seems to be no documentation on this issue in any manual page >> installed by xen's 'make install' , >> or anywhere else I could find. >> >> Thanks in advance for any replies, >> Regards, Jason _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Thu Feb 21 19:25:47 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 21 Feb 2013 19:25: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 1U8bl6-0002Cp-5u; Thu, 21 Feb 2013 19:24:44 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U8bl3-0002Cj-LW for xen-users@lists.xen.org; Thu, 21 Feb 2013 19:24:42 +0000 Received: from [85.158.138.51:8098] by server-1.bemta-3.messagelabs.com id A1/3D-08955-87476215; Thu, 21 Feb 2013 19:24:40 +0000 X-Env-Sender: jason.vas.dias@gmail.com X-Msg-Ref: server-15.tower-174.messagelabs.com!1361474679!26863847!1 X-Originating-IP: [74.125.83.44] 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.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 26756 invoked from network); 21 Feb 2013 19:24:39 -0000 Received: from mail-ee0-f44.google.com (HELO mail-ee0-f44.google.com) (74.125.83.44) by server-15.tower-174.messagelabs.com with RC4-SHA encrypted SMTP; 21 Feb 2013 19:24:39 -0000 Received: by mail-ee0-f44.google.com with SMTP id l10so4828894eei.17 for ; Thu, 21 Feb 2013 11:24:39 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:content-type; bh=SVNVGRGYccw+Szv+//qE7fWPiGs8hxtRsTvKe1kfJqA=; b=YH6ZqOpO7quwjPe3tlAofjDtLtMXJkJG3oPPKWzfC52s7E5Ktvt4ORGJwUUQcOqaBm TUX7foYIyG4gg20DYFCTNH2SiKrv40zG+6kQg4igAw+by6cV2QnwIV1MMT9TkKlZsVyJ ad8CVXPekva2hAWcSiJKAtQFT1THJsaC9nc4IcvEUCWVZV+IKvrp8WQKuySNwCeActDe kL/OtaLk/wkAOJ/9ifNZQh/uI7OGMPRXX/3ZAaqVIFt/ypm9wA4hUGwObv9aQIaRAljo 4hvKZghsQ/1+HhGd6reXU1CTZgeJseyzdx0poHmhY0wAiTyLcicyFBMrF5YlLBLynCXJ LD/g== MIME-Version: 1.0 X-Received: by 10.14.223.69 with SMTP id u45mr83622218eep.23.1361474679086; Thu, 21 Feb 2013 11:24:39 -0800 (PST) Received: by 10.223.73.204 with HTTP; Thu, 21 Feb 2013 11:24:38 -0800 (PST) In-Reply-To: References: Date: Thu, 21 Feb 2013 19:24:38 +0000 Message-ID: From: Jason Vas Dias To: xen-users@lists.xen.org Subject: Re: [Xen-users] help please - running a guest from an iSCSI disk ? getting more diagnostics than "cannot make domain: -3" ? how to make domain0 "privileged" ? X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: 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 beginning to conclude that Xen is not of sufficient code quality to be useful. Firstly, my 'xl create' command returns a 0 exit status, meaning success, but yet no domain is created or can be attached to or listed with 'xl list' : # xl create my_domain.cfg Parsing config from my_domain.cfg Daemon running with PID 1436 # echo $? 0 # xl list Name ID Mem VCPUs State Time(s) Domain-0 0 1024 2 r----- 35.5 This appears to be due to this error message in 'xl dmesg' output : (XEN) Dom5 may compromise security on this CPU. (XEN) traps.c:2584:d5 Domain attempted WRMSR 00000000c0010004 from 0x0000000000000000 to 0x000000000000abcd. >From reading the source, the traps.c message appears to indicate an error condition, but you would not know this from the log message. Anyone know how to avoid this unhandled WRMSR ? Code that silently ignores and does not report error conditions does not get my vote of confidence. Can anyone convince me that Xen is of sufficient quality to be used ? Regards, Jason On Thu, Feb 21, 2013 at 6:53 PM, Jason Vas Dias wrote: > Aha! Finally I discovered 'xl dmesg' and saw > 'Xen does not allow DomU creation on this CPU for security reasons.' > > o why not give an option to make Xen write to the standard kernel > log, so I could have found this message with 'dmesg' ? > It is far from obvious from the documentation that this the only > way of seeing Xen log messages . > > It appears the dom0 CPU has AMD Errata 121 - see: > http://lists.xen.org/archives/html/xen-announce/2012-06/msg00002.html > > But since both my dom0 kernel (3.7.9-1-ARCH) and my domU kernel > (2.6.39-300.26.1.el6uek) apparently have the fix for this > errata , I added 'allow_unsafe' to the Xen dom0 boot command line, > and I'm now able to progress beyond the EPERM issue . > It would have been nice if Xen or xl could have emitted some log > message other than 'cannot make domain: -3', particularly > when it was Xen itself that was refusing to allow the domain creation > to proceed . > It would also have been nice if Xen could have recognized that it was > running kernels with the fix for this issue, and NOT silently > disabled domain creation. > > Regards, > Jason > > On Thu, Feb 21, 2013 at 5:29 PM, Jason Vas Dias > wrote: >> Good day - >> >> This is my first post to this list , and I'm new to Xen - any help on >> this issue would be much appreciated . >> >> I downloaded, built and installed xen-4.2.1 (hypervisor and tools) on >> an x86_64 ArchLinux box >> updated to latest software as of today. >> >> I am trying to bring up a Linux guest from a remote iSCSI disk. >> >> The iSCSI-initiator (open-iscsi) logs in to the remote target OK and >> makes it available as /dev/sde , >> on which is a bootable linux distribution . containing /boot/vmlinuz* etc. >> I can mount this iSCSI disk rw OK on the domain_0 host - so presumably >> I should be able to >> boot up a guest domain from it ? >> >> I modified the domain_0 host's boot arguments to boot Xen OK : >> >> multiboot /boot/xen.gz dom0_mem=1024M loglvl=all guest_loglvl=all >> module /boot/vmlinuz-linux root=/dev/sda2 ro debug >> module /boot/initramfs-linux.img >> >> and made an /etc/xen/${domain}.cfg file: >> # >> # xl.cfg(1) file for booting the iSCSI share: >> # >> name="$domain" >> #vcpus=1 >> #uuid="ceb083a2-feaa-45b0-afe2-3bd44eb4d8c3" >> memory=1024 >> on_poweroff="destroy" >> on_reboot="destroy" >> disk=["/dev/sde,raw,hda,rw"] >> vif=["mac=00:09:3d:13:0d:57,model=tg3,bridge=xenbr0"] >> kernel="/boot/vmlinuz-2.6.39-300.26.1.el6uek.x86_64" >> ramdisk="/boot/initramfs-2.6.39-300.26.1.el6uek.x86_64.img" >> >> Is the disk line OK ? Anything else wrong with this file ? >> >> But attempting to create the domain , as root, fails: >> # xl -vvv create -c /etc/xen/${domain}.cfg >> Parsing config from ${domain}.cfg >> libxl: debug: libxl_create.c:1174:do_domain_create: ao 0x119c890: >> create: how=(nil) callback=(nil) poller=0x119c920 >> libxl: error: libxl_create.c:420:libxl__domain_make: domain creation fail >> libxl: error: libxl_create.c:646:initiate_domain_create: cannot make domain: -3 >> libxl: error: libxl.c:1394:libxl__destroy_domid: non-existant domain -1 >> libxl: error: libxl.c:1358:domain_destroy_callback: unable to destroy >> guest with domid 4294967295 >> libxl: error: libxl_create.c:1153:domcreate_destruction_cb: unable to >> destroy domain 4294967295 following failed creation >> libxl: debug: libxl_event.c:1499:libxl__ao_complete: ao 0x119c890: >> complete, rc=-3 >> libxl: debug: libxl_create.c:1187:do_domain_create: ao 0x119c890: >> inprogress: poller=0x119c920, flags=ic >> libxl: debug: libxl_event.c:1471:libxl__ao__destroy: ao 0x119c890: destroy >> xc: debug: hypercall buffer: total allocations:5 total releases:5 >> xc: debug: hypercall buffer: current allocations:0 maximum allocations:2 >> xc: debug: hypercall buffer: cache current size:2 >> xc: debug: hypercall buffer: cache hits:3 misses:2 toobig:0 >> >> Even though I've enabled all possible log messages in Xen with ' >> loglvl=all guest_loglvl=all' (or have I?) >> I don't see any log messages about this failed attempt to create a >> domain at all , in dmesg output or >> in the system log. >> >> Tracing this command in gdb shows the hypervisor command is returning >> -1, with errno set to 1 (EPERM) : >> >> libxl: debug: libxl_create.c:1174:do_domain_create: ao 0x622890: >> create: how=(nil) callback=(nil) poller=0x622920 >> >> Breakpoint 2, xc_domain_create (xch=0x622240, ssidref=0, >> handle=handle@entry=0x7fffffffe1b0 >> "\316\260\203\242\376\252E\260\257\342;\324N\264\330\303\031", >> flags=flags@entry=0, pdomid=pdomid@entry=0x7fffffffe28c) at xc_domain.c:33 >> 33 { >> (gdb) n >> 37 domctl.cmd = XEN_DOMCTL_createdomain; >> (gdb) >> 38 domctl.domain = (domid_t)*pdomid; >> (gdb) >> 39 domctl.u.createdomain.ssidref = ssidref; >> (gdb) >> 40 domctl.u.createdomain.flags = flags; >> (gdb) >> 41 memcpy(domctl.u.createdomain.handle, handle, >> sizeof(xen_domain_handle_t)); >> (gdb) >> 42 if ( (err = do_domctl(xch, &domctl)) != 0 ) >> (gdb) s >> do_domctl (domctl=0x7fffffffe0a0, xch=0x622240) at xc_private.h:239 >> 239 DECLARE_HYPERCALL_BOUNCE(domctl, sizeof(*domctl), >> XC_HYPERCALL_BUFFER_BOUNCE_BOTH); >> (gdb) n >> 241 domctl->interface_version = XEN_DOMCTL_INTERFACE_VERSION; >> (gdb) >> 243 if ( xc_hypercall_bounce_pre(xch, domctl) ) >> (gdb) >> 249 hypercall.op = __HYPERVISOR_domctl; >> (gdb) >> 250 hypercall.arg[0] = HYPERCALL_BUFFER_AS_ARG(domctl); >> (gdb) >> 252 if ( (ret = do_xen_hypercall(xch, &hypercall)) < 0 ) >> (gdb) s >> do_xen_hypercall (xch=xch@entry=0x622240, >> hypercall=hypercall@entry=0x7fffffffe070) at xc_private.c:246 >> 246 return xch->ops->u.privcmd.hypercall(xch, xch->ops_handle, >> hypercall); >> (gdb) s >> linux_privcmd_hypercall (xch=, h=9, >> hypercall=0x7fffffffe070) at xc_linux_osdep.c:116 >> 116 return ioctl(fd, IOCTL_PRIVCMD_HYPERCALL, hypercall); >> (gdb) fin >> Run till exit from #0 linux_privcmd_hypercall (xch=, >> h=9, hypercall=0x7fffffffe070) at xc_linux_osdep.c:116 >> do_xen_hypercall (xch=xch@entry=0x622240, >> hypercall=hypercall@entry=0x7fffffffe070) at xc_private.c:247 >> 247 } >> Value returned is $3 = -1 >> (gdb) fin >> Run till exit from #0 do_xen_hypercall (xch=xch@entry=0x622240, >> hypercall=hypercall@entry=0x7fffffffe070) at xc_private.c:247 >> 0x00007ffff775b340 in do_domctl (domctl=0x7fffffffe0a0, xch=0x622240) >> at xc_private.h:252 >> 252 if ( (ret = do_xen_hypercall(xch, &hypercall)) < 0 ) >> Value returned is $4 = -1 >> (gdb) p errno >> $5 = 1 >> >> Any ideas how to get this working, or on where I could get better >> diagnostics ? >> >> I'm guessing this is caused by this code in arch/x86/platform_hypercall.c : >> >> ret_t do_platform_op(XEN_GUEST_HANDLE(xen_platform_op_t) u_xenpf_op) >> { >> ret_t ret = 0; >> struct xen_platform_op curop, *op = &curop; >> >> if ( !IS_PRIV(current->domain) ) >> return -EPERM; >> >> So how do I make the IS_PRIV macro return non-zero for my domain_0 , >> ie. set d->is_privileged / >> make my domain0 into a "privileged" domain ? What is meant by >> "privileged" in this context ? >> >> There seems to be no documentation on this issue in any manual page >> installed by xen's 'make install' , >> or anywhere else I could find. >> >> Thanks in advance for any replies, >> Regards, Jason _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Thu Feb 21 19:36:00 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 21 Feb 2013 19:36: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 1U8bv2-0002io-Mm; Thu, 21 Feb 2013 19:35:00 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U8bv1-0002ij-8O for xen-users@lists.xen.org; Thu, 21 Feb 2013 19:34:59 +0000 Received: from [85.158.138.51:6409] by server-16.bemta-3.messagelabs.com id DE/E8-02727-2E676215; Thu, 21 Feb 2013 19:34:58 +0000 X-Env-Sender: amore@xetus.com X-Msg-Ref: server-9.tower-174.messagelabs.com!1361475296!28673983!1 X-Originating-IP: [67.192.241.185] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjcuMTkyLjI0MS4xODUgPT4gMTUxMjM1\n X-StarScan-Received: X-StarScan-Version: 6.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 4514 invoked from network); 21 Feb 2013 19:34:57 -0000 Received: from smtp185.dfw.emailsrvr.com (HELO smtp185.dfw.emailsrvr.com) (67.192.241.185) by server-9.tower-174.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 21 Feb 2013 19:34:57 -0000 Received: from smtp8.relay.dfw1a.emailsrvr.com (localhost.localdomain [127.0.0.1]) by smtp8.relay.dfw1a.emailsrvr.com (SMTP Server) with ESMTP id 49E2F96A2 for ; Thu, 21 Feb 2013 14:34:56 -0500 (EST) X-SMTPDoctor-Processed: csmtpprox 2.7.4 Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp8.relay.dfw1a.emailsrvr.com (SMTP Server) with ESMTP id 42A9E961C for ; Thu, 21 Feb 2013 14:34:56 -0500 (EST) X-Virus-Scanned: OK Received: by smtp8.relay.dfw1a.emailsrvr.com (Authenticated sender: amore-AT-xetus.com) with ESMTPSA id C25C178326 for ; Thu, 21 Feb 2013 14:34:49 -0500 (EST) From: Amit More Date: Thu, 21 Feb 2013 11:34:47 -0800 Message-Id: To: xen-users@lists.xen.org Mime-Version: 1.0 (Apple Message framework v1085) X-Mailer: Apple Mail (2.1085) Subject: [Xen-users] Error Starting Virtual Machines on XCP X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: 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 have XCP 1.1.0-50674c running on a Dell PowerEdge 2950 system with a couple of virtual machines running on it. The virtual machines that are currently running are working fine, however I cannot start the virtual machines are are currently powered off. The error in the XenCenter (version 6) logs says "Internal error: Device.PV_Vnc.Failed_to_start". I also tried to start the virtual machine using xe command but to no avail. I have tried to start different virtual machines on the same XCP hosts, and I get the same error (mentioned above) every time I try to start a virtual machine. The XCP system tries to start the virtual machine for about 20-25 minutes before giving up. I haven't added or removed any hardware from the Dell PowerEdge system on which XCP is running. The only modifications to the virtual machines were adding (and removing) network interfaces. I also suspect that if I take the running virtual machines down, I won't be able to bring them back up again. I searched the internet for answers, but couldn't find any convincing ones. Any help would be greatly appreciated. Thanks, Amit _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Thu Feb 21 19:36:00 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 21 Feb 2013 19:36: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 1U8bv2-0002io-Mm; Thu, 21 Feb 2013 19:35:00 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U8bv1-0002ij-8O for xen-users@lists.xen.org; Thu, 21 Feb 2013 19:34:59 +0000 Received: from [85.158.138.51:6409] by server-16.bemta-3.messagelabs.com id DE/E8-02727-2E676215; Thu, 21 Feb 2013 19:34:58 +0000 X-Env-Sender: amore@xetus.com X-Msg-Ref: server-9.tower-174.messagelabs.com!1361475296!28673983!1 X-Originating-IP: [67.192.241.185] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjcuMTkyLjI0MS4xODUgPT4gMTUxMjM1\n X-StarScan-Received: X-StarScan-Version: 6.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 4514 invoked from network); 21 Feb 2013 19:34:57 -0000 Received: from smtp185.dfw.emailsrvr.com (HELO smtp185.dfw.emailsrvr.com) (67.192.241.185) by server-9.tower-174.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 21 Feb 2013 19:34:57 -0000 Received: from smtp8.relay.dfw1a.emailsrvr.com (localhost.localdomain [127.0.0.1]) by smtp8.relay.dfw1a.emailsrvr.com (SMTP Server) with ESMTP id 49E2F96A2 for ; Thu, 21 Feb 2013 14:34:56 -0500 (EST) X-SMTPDoctor-Processed: csmtpprox 2.7.4 Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp8.relay.dfw1a.emailsrvr.com (SMTP Server) with ESMTP id 42A9E961C for ; Thu, 21 Feb 2013 14:34:56 -0500 (EST) X-Virus-Scanned: OK Received: by smtp8.relay.dfw1a.emailsrvr.com (Authenticated sender: amore-AT-xetus.com) with ESMTPSA id C25C178326 for ; Thu, 21 Feb 2013 14:34:49 -0500 (EST) From: Amit More Date: Thu, 21 Feb 2013 11:34:47 -0800 Message-Id: To: xen-users@lists.xen.org Mime-Version: 1.0 (Apple Message framework v1085) X-Mailer: Apple Mail (2.1085) Subject: [Xen-users] Error Starting Virtual Machines on XCP X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: 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 have XCP 1.1.0-50674c running on a Dell PowerEdge 2950 system with a couple of virtual machines running on it. The virtual machines that are currently running are working fine, however I cannot start the virtual machines are are currently powered off. The error in the XenCenter (version 6) logs says "Internal error: Device.PV_Vnc.Failed_to_start". I also tried to start the virtual machine using xe command but to no avail. I have tried to start different virtual machines on the same XCP hosts, and I get the same error (mentioned above) every time I try to start a virtual machine. The XCP system tries to start the virtual machine for about 20-25 minutes before giving up. I haven't added or removed any hardware from the Dell PowerEdge system on which XCP is running. The only modifications to the virtual machines were adding (and removing) network interfaces. I also suspect that if I take the running virtual machines down, I won't be able to bring them back up again. I searched the internet for answers, but couldn't find any convincing ones. Any help would be greatly appreciated. Thanks, Amit _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Thu Feb 21 20:48:40 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 21 Feb 2013 20:48: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 1U8d3B-0004Dq-4R; Thu, 21 Feb 2013 20:47:29 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U8d3A-0004Dl-2v for xen-users@lists.xen.org; Thu, 21 Feb 2013 20:47:28 +0000 Received: from [193.109.254.147:33123] by server-13.bemta-14.messagelabs.com id EA/D2-30639-FD786215; Thu, 21 Feb 2013 20:47:27 +0000 X-Env-Sender: jaceksburghardt@gmail.com X-Msg-Ref: server-3.tower-27.messagelabs.com!1361479604!8658730!1 X-Originating-IP: [209.85.223.170] X-SpamReason: No, hits=3.1 required=7.0 tests=HTML_00_10,HTML_MESSAGE, HTML_SHORT_LENGTH,ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 29557 invoked from network); 21 Feb 2013 20:46:46 -0000 Received: from mail-ie0-f170.google.com (HELO mail-ie0-f170.google.com) (209.85.223.170) by server-3.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 21 Feb 2013 20:46:46 -0000 Received: by mail-ie0-f170.google.com with SMTP id c11so11916489ieb.1 for ; Thu, 21 Feb 2013 12:46:44 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:date:message-id:subject:from:to :content-type; bh=WQR/fQmr8bcTGoG+Xkd6QHfp6BtY5oTD9TDqnr7/YVE=; b=gHXQh4599/G/PMPQO7WlBu5ox5z+1pUg92AuEnRRXFAwv9R1oawHFoDrZdFZN7SLp3 FsADmC0ppWfQr622b2WlHuMfgjmj0sNH+5H5DcgdGoJ0FLdb4d2FME+gWPeV6UbnzicI HvykoyEF2i462Lx1kwVtRqIDsUsPpl466/gTYqNMtoF3GCx6mfGwxDuygLb6rzH216pr ZB7H6cdjK2pZqt7N/lERiTGDroU2KN1e3FgiaaQ+0xXWKdo3nW4/E78dL9+Rp4s7XjkU sDHU2r4RkH22EUmojLklsyjonHfVmM8L20Q87lQ+uIvvYT/MJ3MfX15ITLSg9oz0UlNq Wg5Q== MIME-Version: 1.0 X-Received: by 10.50.77.230 with SMTP id v6mr13355194igw.29.1361479604288; Thu, 21 Feb 2013 12:46:44 -0800 (PST) Received: by 10.42.41.5 with HTTP; Thu, 21 Feb 2013 12:46:44 -0800 (PST) Date: Thu, 21 Feb 2013 13:46:44 -0700 Message-ID: From: jacek burghardt To: xen-users Subject: [Xen-users] qemu-system-i386 on 64 bit system X-BeenThere: xen-users@lists.xen.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="===============3618402475190137440==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============3618402475190137440== Content-Type: multipart/alternative; boundary=e89a8f3ba87f2ebe1004d6422c02 --e89a8f3ba87f2ebe1004d6422c02 Content-Type: text/plain; charset=ISO-8859-1 I have qemu-system-i386 that crashes when I setup to use qemu-xen. Also why is xen defaulting qemu to i386 and disbles 64 bit ? --e89a8f3ba87f2ebe1004d6422c02 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable I have=A0qemu-system-i386 =A0that crashes when I setup to use qemu-xen. Als= o why is xen defaulting qemu to i386 and disbles 64 bit ?=A0 --e89a8f3ba87f2ebe1004d6422c02-- --===============3618402475190137440== 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 --===============3618402475190137440==-- From xen-users-bounces@lists.xen.org Thu Feb 21 20:48:40 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 21 Feb 2013 20:48: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 1U8d3B-0004Dq-4R; Thu, 21 Feb 2013 20:47:29 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U8d3A-0004Dl-2v for xen-users@lists.xen.org; Thu, 21 Feb 2013 20:47:28 +0000 Received: from [193.109.254.147:33123] by server-13.bemta-14.messagelabs.com id EA/D2-30639-FD786215; Thu, 21 Feb 2013 20:47:27 +0000 X-Env-Sender: jaceksburghardt@gmail.com X-Msg-Ref: server-3.tower-27.messagelabs.com!1361479604!8658730!1 X-Originating-IP: [209.85.223.170] X-SpamReason: No, hits=3.1 required=7.0 tests=HTML_00_10,HTML_MESSAGE, HTML_SHORT_LENGTH,ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 29557 invoked from network); 21 Feb 2013 20:46:46 -0000 Received: from mail-ie0-f170.google.com (HELO mail-ie0-f170.google.com) (209.85.223.170) by server-3.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 21 Feb 2013 20:46:46 -0000 Received: by mail-ie0-f170.google.com with SMTP id c11so11916489ieb.1 for ; Thu, 21 Feb 2013 12:46:44 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:date:message-id:subject:from:to :content-type; bh=WQR/fQmr8bcTGoG+Xkd6QHfp6BtY5oTD9TDqnr7/YVE=; b=gHXQh4599/G/PMPQO7WlBu5ox5z+1pUg92AuEnRRXFAwv9R1oawHFoDrZdFZN7SLp3 FsADmC0ppWfQr622b2WlHuMfgjmj0sNH+5H5DcgdGoJ0FLdb4d2FME+gWPeV6UbnzicI HvykoyEF2i462Lx1kwVtRqIDsUsPpl466/gTYqNMtoF3GCx6mfGwxDuygLb6rzH216pr ZB7H6cdjK2pZqt7N/lERiTGDroU2KN1e3FgiaaQ+0xXWKdo3nW4/E78dL9+Rp4s7XjkU sDHU2r4RkH22EUmojLklsyjonHfVmM8L20Q87lQ+uIvvYT/MJ3MfX15ITLSg9oz0UlNq Wg5Q== MIME-Version: 1.0 X-Received: by 10.50.77.230 with SMTP id v6mr13355194igw.29.1361479604288; Thu, 21 Feb 2013 12:46:44 -0800 (PST) Received: by 10.42.41.5 with HTTP; Thu, 21 Feb 2013 12:46:44 -0800 (PST) Date: Thu, 21 Feb 2013 13:46:44 -0700 Message-ID: From: jacek burghardt To: xen-users Subject: [Xen-users] qemu-system-i386 on 64 bit system X-BeenThere: xen-users@lists.xen.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="===============3618402475190137440==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============3618402475190137440== Content-Type: multipart/alternative; boundary=e89a8f3ba87f2ebe1004d6422c02 --e89a8f3ba87f2ebe1004d6422c02 Content-Type: text/plain; charset=ISO-8859-1 I have qemu-system-i386 that crashes when I setup to use qemu-xen. Also why is xen defaulting qemu to i386 and disbles 64 bit ? --e89a8f3ba87f2ebe1004d6422c02 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable I have=A0qemu-system-i386 =A0that crashes when I setup to use qemu-xen. Als= o why is xen defaulting qemu to i386 and disbles 64 bit ?=A0 --e89a8f3ba87f2ebe1004d6422c02-- --===============3618402475190137440== 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 --===============3618402475190137440==-- From xen-users-bounces@lists.xen.org Thu Feb 21 21:32:05 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 21 Feb 2013 21: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 1U8djO-0005Bn-4e; Thu, 21 Feb 2013 21:31:06 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U8djL-0005Bi-Q9 for xen-users@lists.xen.org; Thu, 21 Feb 2013 21:31:04 +0000 Received: from [85.158.137.99:15515] by server-14.bemta-3.messagelabs.com id 5F/9F-23533-21296215; Thu, 21 Feb 2013 21:30:58 +0000 X-Env-Sender: cdelorme@gmail.com X-Msg-Ref: server-2.tower-217.messagelabs.com!1361482246!17374502!1 X-Originating-IP: [209.85.220.178] X-SpamReason: No, hits=1.2 required=7.0 tests=HTML_20_30,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14, ML_RADAR_SPEW_LINKS_8, RCVD_BY_IP, spamassassin: , async_handler: YXN5bmNfZGVsYXk6IDcwNDcyMDAgKHRpbWVvdXQp\n X-StarScan-Received: X-StarScan-Version: 6.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 4244 invoked from network); 21 Feb 2013 21:30:47 -0000 Received: from mail-vc0-f178.google.com (HELO mail-vc0-f178.google.com) (209.85.220.178) by server-2.tower-217.messagelabs.com with RC4-SHA encrypted SMTP; 21 Feb 2013 21:30:47 -0000 Received: by mail-vc0-f178.google.com with SMTP id m8so6060181vcd.37 for ; Thu, 21 Feb 2013 13:30:46 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=cLCZ0D6DR0vWsSotLoR3yYZIIghFY7ucu7pobnFojoM=; b=MR1jE4G3yCPbf0q08IZ2npNnd4thjyCpQBwjJTAoqN2lWuxqwLHfYLC26VDJNmkTOX OW6UPK9QSaqvpdhZMIdgM81bN+Ii0kkzy0Wk0ttYvPsOS0bqH315E3sTKkD8Hn011gOz 2lVrdWHro9tkBZC1MoIGIzZ8EisCl1LtUjKlujAJJ5RKm9+n8hY9WXTHgXXTMWgAQF1f n+bUPygfsJd6rqQepdb8Fordpyhx77ZNABjS67ekq9WaP0f5LO6eromu+Bf5P+cghvYB vzZCjWOjccnCWNeByhdG0pYVffzt9iL5ecnbufxkWQ3ExYdbZEiNzuKacyQaipgxFk54 Ulxw== MIME-Version: 1.0 X-Received: by 10.52.38.234 with SMTP id j10mr29872834vdk.0.1361482245942; Thu, 21 Feb 2013 13:30:45 -0800 (PST) Received: by 10.58.32.199 with HTTP; Thu, 21 Feb 2013 13:30:45 -0800 (PST) In-Reply-To: References: Date: Thu, 21 Feb 2013 16:30:45 -0500 Message-ID: From: Casey DeLorme To: Jason Vas Dias Cc: "xen-users@lists.xen.org" Subject: Re: [Xen-users] help please - running a guest from an iSCSI disk ? getting more diagnostics than "cannot make domain: -3" ? how to make domain0 "privileged" ? X-BeenThere: xen-users@lists.xen.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="===============4898653245967660928==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============4898653245967660928== Content-Type: multipart/alternative; boundary=bcaec51d27f6a32e6604d642c950 --bcaec51d27f6a32e6604d642c950 Content-Type: text/plain; charset=UTF-8 Hello Jason, Looking at your configuration, was the kernel built to be PV Compatible ( http://sanifool.wordpress.com/2013/01/09/booting-up-a-domu-on-xen-4-2/). The disk line looks fine provided you wanted to pass the whole disk to your PVM (including it's partition table etc). Also if you have it mounted while trying to launch the PVM that may throw warnings or errors. Is it possible you are missing the bootloader ( http://xenbits.xen.org/docs/4.2-testing/man/xl.cfg.5.html)? I don't believe it would affect your ability to launch the PVM, but the I am unfamiliar with your vif device model, and the mac address isn't in the suggested Xen range ( http://xenbits.xen.org/docs/4.2-testing/misc/xl-network-configuration.html). If you are looking for more detailed diagnostics, you might check that the xen-debug kernel flag is set (and rebuild your ramdisk or kernel). Logging must vary by distribution as I almost never see non-kernel software log its errors to dmesg (/var/log/messages), but most will place logs into the same directory and organize them by file or folder. In Xen's case it uses your toolstacks command xl dmesg (/var/logs/xen/). --- On Thu, Feb 21, 2013 at 2:24 PM, Jason Vas Dias wrote: > I'm beginning to conclude that Xen is not of sufficient code quality > to be useful. > > Firstly, my 'xl create' command returns a 0 exit status, meaning > success, but yet no domain > is created or can be attached to or listed with 'xl list' : > > # xl create my_domain.cfg > Parsing config from my_domain.cfg > Daemon running with PID 1436 > # echo $? > 0 > # xl list > Name ID Mem VCPUs State > Time(s) > Domain-0 0 1024 2 r----- > 35.5 > > This appears to be due to this error message in 'xl dmesg' output : > > (XEN) Dom5 may compromise security on this CPU. > (XEN) traps.c:2584:d5 Domain attempted WRMSR 00000000c0010004 from > 0x0000000000000000 to 0x000000000000abcd. > > From reading the source, the traps.c message appears to indicate an > error condition, but you would not know this from the log message. > > Have you checked all of the log files in /var/logs/xen/? Pretty sure that so long as the configuration itself doesn't contain syntactical errors and the command to qemu goes through that xl will assume it did its job. Is it possible xl create is launching the domains just fine (hence code 0), and they are failing at a different stage (eg qemu during boot due to configuration problems)? Anyone know how to avoid this unhandled WRMSR ? > > Code that silently ignores and does not report error conditions does > not get my vote of confidence. > > Can anyone convince me that Xen is of sufficient quality to be used ? > > Plenty of well known companies are using Xen, but I don't believe they are using the very latest stable release (4.2.1). AFAIK 4.2.1 is not available as a package in any stable operating systems yet. Stable release of code does not guarantee it will be compatible without plenty of configuration based on your choice of Dom0. However I am under the assumption that you are not using it for production purposes given your choices (Xen 4.2.1 and ArchLinux don't exactly point to concerns with stability or desirable ease of operation as a priority). If that is the case then as a personal user I can say that I have had great success using Xen 4.2 on Debain Wheezy for several months now. However I have not dabbled in many of the areas you are (such as iSCSI, PVM's and programmatic domain control). However, even with my limited experience, I can easily conclude that because Xen can be used for such a wide variety of purposes it becomes that much harder to ensure functionality as factors that can influence success tend to cover a wide range (host hardware, Xen version, installed packages and package versions, Dom0 distro and version, etc). Hope these answers will help you identify the problem. ~Casey --bcaec51d27f6a32e6604d642c950 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

Hello Jason,

= Looking at your configuration, was the kernel built to be PV Compatible (http://sanifool.wordpress.com/2013/01/09/booting-up-a-domu-on-xen-4-2= /).

The disk line looks fine provided you wanted to pass th= e whole disk to your PVM (including it's partition table etc). =C2=A0Al= so if you have it mounted while trying to launch the PVM that may throw war= nings or errors.

Is it possible you are missing the bootloader (http://xenbi= ts.xen.org/docs/4.2-testing/man/xl.cfg.5.html)?

I don't believe it would affect your ability to launch the PVM, but the= I am unfamiliar with your vif device model, and the mac address isn't = in the suggested Xen range (http://xenbits.xen.org/docs/4.2-tes= ting/misc/xl-network-configuration.html).


If you are looking for more detailed dia= gnostics, you might check that the xen-debug kernel flag is set (and rebuil= d your ramdisk or kernel).


Logging = must vary by distribution as I almost never see non-kernel software log its= errors to dmesg (/var/log/messages), but most will place logs into the sam= e directory and organize them by file or folder. =C2=A0In Xen's case it= uses your toolstacks command xl dmesg (/var/logs/xen/).

---


On Thu, Feb 21, 2013 at 2:24 PM, Jason Vas Dias <= jason.vas.dias@gmail.com> wrote:
I'm beginning to conclude that Xen is not of sufficien= t code quality
to be useful.

Firstly, =C2=A0my 'xl create' command returns a 0 exit status, mean= ing
success, but yet no domain
is created or can be attached to or listed with 'xl list' :

# xl create my_domain.cfg
Parsing config from my_domain.cfg
Daemon running with PID 1436
# echo $?
0
# xl list
Name =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0ID =C2= =A0 Mem VCPUs =C2=A0 =C2=A0 =C2=A0State =C2=A0 Time(s)
Domain-0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 0 =C2=A01024 = =C2=A0 =C2=A0 2 =C2=A0 =C2=A0 r----- =C2=A0 =C2=A0 =C2=A035.5

This appears to be due to this error message in 'xl dmesg' output :=

(XEN) Dom5 may compromise security on this CPU.
(XEN) traps.c:2584:d5 Domain attempted WRMSR 00000000c0010004 from
0x0000000000000000 to 0x000000000000abcd.

>From reading the source, the traps.c message appears to indicate an
error condition, but you would not know this from the log message.

Have you checked all of the log files in /var/lo= gs/xen/?

Pretty sure that so long as the conf= iguration itself doesn't contain syntactical errors and the command to = qemu goes through that xl will assume it did its job.

Is it possible xl create is launching the domains= just fine (hence code 0), and they are failing at a different stage (eg qe= mu during boot due to configuration problems)?

Anyone know how to avoid this unhandled WRMSR ?

Code that silently ignores and does not report error conditions does
not get my vote of confidence.

Can anyone convince me that Xen is of sufficient quality to be used ?

Plenty of well known companies are using Xen, but I d= on't believe they are using the very latest stable release (4.2.1). =C2= =A0AFAIK 4.2.1 is not available as a package in any stable operating system= s yet. =C2=A0Stable release of code does not=C2=A0guarantee=C2=A0it will be= compatible without plenty of configuration based on your choice of Dom0.

However I am under the assumption that you a= re not using it for production purposes given your choices (Xen 4.2.1 and A= rchLinux don't exactly point to concerns with stability or desirable ea= se of operation as a priority). =C2=A0If that is the case then as a persona= l user I can say that I have had great success using Xen 4.2 on Debain Whee= zy for several months now. =C2=A0However I have not dabbled in many of the = areas you are (such as iSCSI, PVM's and programmatic domain control).

However, even with my limited experience, I can easily = conclude that because Xen can be used for such a wide variety of purposes i= t becomes that much harder to ensure functionality as factors that can infl= uence success tend to cover a wide range (host hardware, Xen version, insta= lled packages and package versions, Dom0 distro and version, etc).


Hope these answers will help you identif= y the problem.

~Casey
--bcaec51d27f6a32e6604d642c950-- --===============4898653245967660928== 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 --===============4898653245967660928==-- From xen-users-bounces@lists.xen.org Thu Feb 21 21:32:05 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 21 Feb 2013 21: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 1U8djO-0005Bn-4e; Thu, 21 Feb 2013 21:31:06 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U8djL-0005Bi-Q9 for xen-users@lists.xen.org; Thu, 21 Feb 2013 21:31:04 +0000 Received: from [85.158.137.99:15515] by server-14.bemta-3.messagelabs.com id 5F/9F-23533-21296215; Thu, 21 Feb 2013 21:30:58 +0000 X-Env-Sender: cdelorme@gmail.com X-Msg-Ref: server-2.tower-217.messagelabs.com!1361482246!17374502!1 X-Originating-IP: [209.85.220.178] X-SpamReason: No, hits=1.2 required=7.0 tests=HTML_20_30,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14, ML_RADAR_SPEW_LINKS_8, RCVD_BY_IP, spamassassin: , async_handler: YXN5bmNfZGVsYXk6IDcwNDcyMDAgKHRpbWVvdXQp\n X-StarScan-Received: X-StarScan-Version: 6.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 4244 invoked from network); 21 Feb 2013 21:30:47 -0000 Received: from mail-vc0-f178.google.com (HELO mail-vc0-f178.google.com) (209.85.220.178) by server-2.tower-217.messagelabs.com with RC4-SHA encrypted SMTP; 21 Feb 2013 21:30:47 -0000 Received: by mail-vc0-f178.google.com with SMTP id m8so6060181vcd.37 for ; Thu, 21 Feb 2013 13:30:46 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=cLCZ0D6DR0vWsSotLoR3yYZIIghFY7ucu7pobnFojoM=; b=MR1jE4G3yCPbf0q08IZ2npNnd4thjyCpQBwjJTAoqN2lWuxqwLHfYLC26VDJNmkTOX OW6UPK9QSaqvpdhZMIdgM81bN+Ii0kkzy0Wk0ttYvPsOS0bqH315E3sTKkD8Hn011gOz 2lVrdWHro9tkBZC1MoIGIzZ8EisCl1LtUjKlujAJJ5RKm9+n8hY9WXTHgXXTMWgAQF1f n+bUPygfsJd6rqQepdb8Fordpyhx77ZNABjS67ekq9WaP0f5LO6eromu+Bf5P+cghvYB vzZCjWOjccnCWNeByhdG0pYVffzt9iL5ecnbufxkWQ3ExYdbZEiNzuKacyQaipgxFk54 Ulxw== MIME-Version: 1.0 X-Received: by 10.52.38.234 with SMTP id j10mr29872834vdk.0.1361482245942; Thu, 21 Feb 2013 13:30:45 -0800 (PST) Received: by 10.58.32.199 with HTTP; Thu, 21 Feb 2013 13:30:45 -0800 (PST) In-Reply-To: References: Date: Thu, 21 Feb 2013 16:30:45 -0500 Message-ID: From: Casey DeLorme To: Jason Vas Dias Cc: "xen-users@lists.xen.org" Subject: Re: [Xen-users] help please - running a guest from an iSCSI disk ? getting more diagnostics than "cannot make domain: -3" ? how to make domain0 "privileged" ? X-BeenThere: xen-users@lists.xen.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="===============4898653245967660928==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============4898653245967660928== Content-Type: multipart/alternative; boundary=bcaec51d27f6a32e6604d642c950 --bcaec51d27f6a32e6604d642c950 Content-Type: text/plain; charset=UTF-8 Hello Jason, Looking at your configuration, was the kernel built to be PV Compatible ( http://sanifool.wordpress.com/2013/01/09/booting-up-a-domu-on-xen-4-2/). The disk line looks fine provided you wanted to pass the whole disk to your PVM (including it's partition table etc). Also if you have it mounted while trying to launch the PVM that may throw warnings or errors. Is it possible you are missing the bootloader ( http://xenbits.xen.org/docs/4.2-testing/man/xl.cfg.5.html)? I don't believe it would affect your ability to launch the PVM, but the I am unfamiliar with your vif device model, and the mac address isn't in the suggested Xen range ( http://xenbits.xen.org/docs/4.2-testing/misc/xl-network-configuration.html). If you are looking for more detailed diagnostics, you might check that the xen-debug kernel flag is set (and rebuild your ramdisk or kernel). Logging must vary by distribution as I almost never see non-kernel software log its errors to dmesg (/var/log/messages), but most will place logs into the same directory and organize them by file or folder. In Xen's case it uses your toolstacks command xl dmesg (/var/logs/xen/). --- On Thu, Feb 21, 2013 at 2:24 PM, Jason Vas Dias wrote: > I'm beginning to conclude that Xen is not of sufficient code quality > to be useful. > > Firstly, my 'xl create' command returns a 0 exit status, meaning > success, but yet no domain > is created or can be attached to or listed with 'xl list' : > > # xl create my_domain.cfg > Parsing config from my_domain.cfg > Daemon running with PID 1436 > # echo $? > 0 > # xl list > Name ID Mem VCPUs State > Time(s) > Domain-0 0 1024 2 r----- > 35.5 > > This appears to be due to this error message in 'xl dmesg' output : > > (XEN) Dom5 may compromise security on this CPU. > (XEN) traps.c:2584:d5 Domain attempted WRMSR 00000000c0010004 from > 0x0000000000000000 to 0x000000000000abcd. > > From reading the source, the traps.c message appears to indicate an > error condition, but you would not know this from the log message. > > Have you checked all of the log files in /var/logs/xen/? Pretty sure that so long as the configuration itself doesn't contain syntactical errors and the command to qemu goes through that xl will assume it did its job. Is it possible xl create is launching the domains just fine (hence code 0), and they are failing at a different stage (eg qemu during boot due to configuration problems)? Anyone know how to avoid this unhandled WRMSR ? > > Code that silently ignores and does not report error conditions does > not get my vote of confidence. > > Can anyone convince me that Xen is of sufficient quality to be used ? > > Plenty of well known companies are using Xen, but I don't believe they are using the very latest stable release (4.2.1). AFAIK 4.2.1 is not available as a package in any stable operating systems yet. Stable release of code does not guarantee it will be compatible without plenty of configuration based on your choice of Dom0. However I am under the assumption that you are not using it for production purposes given your choices (Xen 4.2.1 and ArchLinux don't exactly point to concerns with stability or desirable ease of operation as a priority). If that is the case then as a personal user I can say that I have had great success using Xen 4.2 on Debain Wheezy for several months now. However I have not dabbled in many of the areas you are (such as iSCSI, PVM's and programmatic domain control). However, even with my limited experience, I can easily conclude that because Xen can be used for such a wide variety of purposes it becomes that much harder to ensure functionality as factors that can influence success tend to cover a wide range (host hardware, Xen version, installed packages and package versions, Dom0 distro and version, etc). Hope these answers will help you identify the problem. ~Casey --bcaec51d27f6a32e6604d642c950 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

Hello Jason,

= Looking at your configuration, was the kernel built to be PV Compatible (http://sanifool.wordpress.com/2013/01/09/booting-up-a-domu-on-xen-4-2= /).

The disk line looks fine provided you wanted to pass th= e whole disk to your PVM (including it's partition table etc). =C2=A0Al= so if you have it mounted while trying to launch the PVM that may throw war= nings or errors.

Is it possible you are missing the bootloader (http://xenbi= ts.xen.org/docs/4.2-testing/man/xl.cfg.5.html)?

I don't believe it would affect your ability to launch the PVM, but the= I am unfamiliar with your vif device model, and the mac address isn't = in the suggested Xen range (http://xenbits.xen.org/docs/4.2-tes= ting/misc/xl-network-configuration.html).


If you are looking for more detailed dia= gnostics, you might check that the xen-debug kernel flag is set (and rebuil= d your ramdisk or kernel).


Logging = must vary by distribution as I almost never see non-kernel software log its= errors to dmesg (/var/log/messages), but most will place logs into the sam= e directory and organize them by file or folder. =C2=A0In Xen's case it= uses your toolstacks command xl dmesg (/var/logs/xen/).

---


On Thu, Feb 21, 2013 at 2:24 PM, Jason Vas Dias <= jason.vas.dias@gmail.com> wrote:
I'm beginning to conclude that Xen is not of sufficien= t code quality
to be useful.

Firstly, =C2=A0my 'xl create' command returns a 0 exit status, mean= ing
success, but yet no domain
is created or can be attached to or listed with 'xl list' :

# xl create my_domain.cfg
Parsing config from my_domain.cfg
Daemon running with PID 1436
# echo $?
0
# xl list
Name =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0ID =C2= =A0 Mem VCPUs =C2=A0 =C2=A0 =C2=A0State =C2=A0 Time(s)
Domain-0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 0 =C2=A01024 = =C2=A0 =C2=A0 2 =C2=A0 =C2=A0 r----- =C2=A0 =C2=A0 =C2=A035.5

This appears to be due to this error message in 'xl dmesg' output :=

(XEN) Dom5 may compromise security on this CPU.
(XEN) traps.c:2584:d5 Domain attempted WRMSR 00000000c0010004 from
0x0000000000000000 to 0x000000000000abcd.

>From reading the source, the traps.c message appears to indicate an
error condition, but you would not know this from the log message.

Have you checked all of the log files in /var/lo= gs/xen/?

Pretty sure that so long as the conf= iguration itself doesn't contain syntactical errors and the command to = qemu goes through that xl will assume it did its job.

Is it possible xl create is launching the domains= just fine (hence code 0), and they are failing at a different stage (eg qe= mu during boot due to configuration problems)?

Anyone know how to avoid this unhandled WRMSR ?

Code that silently ignores and does not report error conditions does
not get my vote of confidence.

Can anyone convince me that Xen is of sufficient quality to be used ?

Plenty of well known companies are using Xen, but I d= on't believe they are using the very latest stable release (4.2.1). =C2= =A0AFAIK 4.2.1 is not available as a package in any stable operating system= s yet. =C2=A0Stable release of code does not=C2=A0guarantee=C2=A0it will be= compatible without plenty of configuration based on your choice of Dom0.

However I am under the assumption that you a= re not using it for production purposes given your choices (Xen 4.2.1 and A= rchLinux don't exactly point to concerns with stability or desirable ea= se of operation as a priority). =C2=A0If that is the case then as a persona= l user I can say that I have had great success using Xen 4.2 on Debain Whee= zy for several months now. =C2=A0However I have not dabbled in many of the = areas you are (such as iSCSI, PVM's and programmatic domain control).

However, even with my limited experience, I can easily = conclude that because Xen can be used for such a wide variety of purposes i= t becomes that much harder to ensure functionality as factors that can infl= uence success tend to cover a wide range (host hardware, Xen version, insta= lled packages and package versions, Dom0 distro and version, etc).


Hope these answers will help you identif= y the problem.

~Casey
--bcaec51d27f6a32e6604d642c950-- --===============4898653245967660928== 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 --===============4898653245967660928==-- From xen-users-bounces@lists.xen.org Thu Feb 21 23:12:02 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 21 Feb 2013 23:12: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 1U8fHl-0007RR-KS; Thu, 21 Feb 2013 23:10:41 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U8fHj-0007RL-Fs for xen-users@lists.xen.org; Thu, 21 Feb 2013 23:10:39 +0000 Received: from [85.158.138.51:36864] by server-16.bemta-3.messagelabs.com id E8/0D-02727-E69A6215; Thu, 21 Feb 2013 23:10:38 +0000 X-Env-Sender: murrayie@yahoo.co.uk X-Msg-Ref: server-10.tower-174.messagelabs.com!1361488235!24590780!1 X-Originating-IP: [77.238.189.68] X-SpamReason: No, hits=0.0 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, spamassassin: X-StarScan-Received: X-StarScan-Version: 6.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 29700 invoked from network); 21 Feb 2013 23:10:35 -0000 Received: from nm15.bullet.mail.ird.yahoo.com (HELO nm15.bullet.mail.ird.yahoo.com) (77.238.189.68) by server-10.tower-174.messagelabs.com with SMTP; 21 Feb 2013 23:10:35 -0000 Received: from [212.82.105.224] by nm15.bullet.mail.ird.yahoo.com with NNFMP; 21 Feb 2013 23:10:34 -0000 Received: from [217.146.188.63] by tm20.bullet.mail.ird.yahoo.com with NNFMP; 21 Feb 2013 23:10:34 -0000 Received: from [127.0.0.1] by smtp105.mail.ird.yahoo.com with NNFMP; 21 Feb 2013 23:10:34 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.co.uk; s=s1024; t=1361488234; bh=LwULXQPUFzC1+7lcJpwtOMCCunj0UCOxYevePMdMtis=; 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:CC:Subject:References:In-Reply-To:Content-Type:Content-Transfer-Encoding; b=Ymo2vAPsSSR7taeu8g8pxbn1tdsYBtEaa0x8A1SLFqoAOug5ln8yKHh6MCXhUT/W6UsVONsEhPFUGR/ctczOh07UX/FNl0zX1KYgyVxIi8jMQM08DbkJDeqmAuGaHWAo6thBuzF4A1AHucLF5DEk9FTmVDoZ8LhA9xYu4oil5Jo= X-Yahoo-Newman-Id: 755158.45457.bm@smtp105.mail.ird.yahoo.com X-Yahoo-Newman-Property: ymail-3 X-YMail-OSG: VXxYLrUVM1mva2SKHrOBoA0VX4wE8TbpOsVsfudy_zcWl1n fNpU1FTijqu9ZvOVzYBGzLz_jlmFIGTsqehnh3aFURiS53I_cBYDAbd7NqsK .xyswk5WpkcTKRO_dUzrTvrIGUwTwzbodHhULfinYP0Pee.CiN7KMtGO906e .nHb1PR7e3tUSw6ilWu___duveXGlJjJ.VskGzMpFZVlmmoI_EDoHhVJswJz aye8HHanNUMqNdVbBNoqVWAzLeVgOxlfgd89c.Gl1zq.WUH4XF4euReUkHER oHF32ei89Wn2iiYucUGs_U_MpbPmWD5ZRnslGMxFCAeMmSZd20efy4A8Gilo QPxqocNNAU6BTlmywr84Tes5k3mBo.c_8pn_pbns4QWdk2y0b_jjTIULk1so i29tLAgrNkmALLrT5EW3W1XhWWZItMobU43LnFCAtW9plmlzYTQ-- X-Yahoo-SMTP: P.LfrmaswBDlKN6tCvtOaEZlSVsY Received: from [192.168.1.136] (murrayie@109.157.15.99 with plain) by smtp105.mail.ird.yahoo.com with SMTP; 21 Feb 2013 15:10:34 -0800 PST Message-ID: <5126A96A.6020105@yahoo.co.uk> Date: Thu, 21 Feb 2013 23:10:34 +0000 From: Ian User-Agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/20130106 Thunderbird/17.0.2 MIME-Version: 1.0 To: Andrew Eross References: <51229E41.2090103@yahoo.co.uk> <1361281294.8796.YahooMailNeo@web171304.mail.ir2.yahoo.com> In-Reply-To: Cc: "xen-users@lists.xen.org" Subject: Re: [Xen-users] Xen 4.2.1 unable to get domain type for domid X-BeenThere: xen-users@lists.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 21/02/13 15:11, Andrew Eross wrote: > Hi Ian, > > Yep, confirmed, exact same images as you: > > 8525c3e8d6131ae462ba85b935a70bae vmlinuz > f1f36dbfe47ebda085f41394dd079d09 initrd.gz > > And I tried a very similar config: > > name = "ubuntu-calendar-test" > memory = 1024 > disk = ['phy:/dev/mapper/center-calendar,xvda,w'] > vif = [ 'mac=00:16:31:55:1c:82' ] > kernel = "/root/ubuntu1204/vmlinuz" > ramdisk = "/root/ubuntu1204/initrd.gz" > vcpus = 2 > on_reboot = 'destroy' > on_crash = 'destroy' > > Unfortunately still not able to launch this VM, very strange! > > xl create /etc/xen/ubuntu-calendar-test.cfg -c > # > Parsing config from /etc/xen/ubuntu-calendar-test.cfg > Daemon running with PID 28828 > xenconsole: Could not read tty from store: No such file or directory > libxl: error: libxl_exec.c:118:libxl_report_child_exitstatus: console > child [0] exited with error status 2 > # > > cat /var/log/xen/xl-ubuntu-calendar-test.log > # > Waiting for domain ubuntu-calendar-test (domid 2) to die [pid 27391] > Domain 2 has shut down, reason code 3 0x3 > Action for shutdown reason code 3 is destroy > Domain 2 needs to be cleaned up: destroying the domain > Done. Exiting now > # > I am sure I had this once but can't for the life of me remember what was wrong. You did use... make install-tools PYTHON_PREFIX_ARG= ? _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Thu Feb 21 23:12:02 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 21 Feb 2013 23:12: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 1U8fHl-0007RR-KS; Thu, 21 Feb 2013 23:10:41 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U8fHj-0007RL-Fs for xen-users@lists.xen.org; Thu, 21 Feb 2013 23:10:39 +0000 Received: from [85.158.138.51:36864] by server-16.bemta-3.messagelabs.com id E8/0D-02727-E69A6215; Thu, 21 Feb 2013 23:10:38 +0000 X-Env-Sender: murrayie@yahoo.co.uk X-Msg-Ref: server-10.tower-174.messagelabs.com!1361488235!24590780!1 X-Originating-IP: [77.238.189.68] X-SpamReason: No, hits=0.0 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, spamassassin: X-StarScan-Received: X-StarScan-Version: 6.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 29700 invoked from network); 21 Feb 2013 23:10:35 -0000 Received: from nm15.bullet.mail.ird.yahoo.com (HELO nm15.bullet.mail.ird.yahoo.com) (77.238.189.68) by server-10.tower-174.messagelabs.com with SMTP; 21 Feb 2013 23:10:35 -0000 Received: from [212.82.105.224] by nm15.bullet.mail.ird.yahoo.com with NNFMP; 21 Feb 2013 23:10:34 -0000 Received: from [217.146.188.63] by tm20.bullet.mail.ird.yahoo.com with NNFMP; 21 Feb 2013 23:10:34 -0000 Received: from [127.0.0.1] by smtp105.mail.ird.yahoo.com with NNFMP; 21 Feb 2013 23:10:34 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.co.uk; s=s1024; t=1361488234; bh=LwULXQPUFzC1+7lcJpwtOMCCunj0UCOxYevePMdMtis=; 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:CC:Subject:References:In-Reply-To:Content-Type:Content-Transfer-Encoding; b=Ymo2vAPsSSR7taeu8g8pxbn1tdsYBtEaa0x8A1SLFqoAOug5ln8yKHh6MCXhUT/W6UsVONsEhPFUGR/ctczOh07UX/FNl0zX1KYgyVxIi8jMQM08DbkJDeqmAuGaHWAo6thBuzF4A1AHucLF5DEk9FTmVDoZ8LhA9xYu4oil5Jo= X-Yahoo-Newman-Id: 755158.45457.bm@smtp105.mail.ird.yahoo.com X-Yahoo-Newman-Property: ymail-3 X-YMail-OSG: VXxYLrUVM1mva2SKHrOBoA0VX4wE8TbpOsVsfudy_zcWl1n fNpU1FTijqu9ZvOVzYBGzLz_jlmFIGTsqehnh3aFURiS53I_cBYDAbd7NqsK .xyswk5WpkcTKRO_dUzrTvrIGUwTwzbodHhULfinYP0Pee.CiN7KMtGO906e .nHb1PR7e3tUSw6ilWu___duveXGlJjJ.VskGzMpFZVlmmoI_EDoHhVJswJz aye8HHanNUMqNdVbBNoqVWAzLeVgOxlfgd89c.Gl1zq.WUH4XF4euReUkHER oHF32ei89Wn2iiYucUGs_U_MpbPmWD5ZRnslGMxFCAeMmSZd20efy4A8Gilo QPxqocNNAU6BTlmywr84Tes5k3mBo.c_8pn_pbns4QWdk2y0b_jjTIULk1so i29tLAgrNkmALLrT5EW3W1XhWWZItMobU43LnFCAtW9plmlzYTQ-- X-Yahoo-SMTP: P.LfrmaswBDlKN6tCvtOaEZlSVsY Received: from [192.168.1.136] (murrayie@109.157.15.99 with plain) by smtp105.mail.ird.yahoo.com with SMTP; 21 Feb 2013 15:10:34 -0800 PST Message-ID: <5126A96A.6020105@yahoo.co.uk> Date: Thu, 21 Feb 2013 23:10:34 +0000 From: Ian User-Agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/20130106 Thunderbird/17.0.2 MIME-Version: 1.0 To: Andrew Eross References: <51229E41.2090103@yahoo.co.uk> <1361281294.8796.YahooMailNeo@web171304.mail.ir2.yahoo.com> In-Reply-To: Cc: "xen-users@lists.xen.org" Subject: Re: [Xen-users] Xen 4.2.1 unable to get domain type for domid X-BeenThere: xen-users@lists.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 21/02/13 15:11, Andrew Eross wrote: > Hi Ian, > > Yep, confirmed, exact same images as you: > > 8525c3e8d6131ae462ba85b935a70bae vmlinuz > f1f36dbfe47ebda085f41394dd079d09 initrd.gz > > And I tried a very similar config: > > name = "ubuntu-calendar-test" > memory = 1024 > disk = ['phy:/dev/mapper/center-calendar,xvda,w'] > vif = [ 'mac=00:16:31:55:1c:82' ] > kernel = "/root/ubuntu1204/vmlinuz" > ramdisk = "/root/ubuntu1204/initrd.gz" > vcpus = 2 > on_reboot = 'destroy' > on_crash = 'destroy' > > Unfortunately still not able to launch this VM, very strange! > > xl create /etc/xen/ubuntu-calendar-test.cfg -c > # > Parsing config from /etc/xen/ubuntu-calendar-test.cfg > Daemon running with PID 28828 > xenconsole: Could not read tty from store: No such file or directory > libxl: error: libxl_exec.c:118:libxl_report_child_exitstatus: console > child [0] exited with error status 2 > # > > cat /var/log/xen/xl-ubuntu-calendar-test.log > # > Waiting for domain ubuntu-calendar-test (domid 2) to die [pid 27391] > Domain 2 has shut down, reason code 3 0x3 > Action for shutdown reason code 3 is destroy > Domain 2 needs to be cleaned up: destroying the domain > Done. Exiting now > # > I am sure I had this once but can't for the life of me remember what was wrong. You did use... make install-tools PYTHON_PREFIX_ARG= ? _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Thu Feb 21 23:35:24 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 21 Feb 2013 23:35: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 1U8feI-00088l-U4; Thu, 21 Feb 2013 23:33:58 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U8feH-00088g-LR for xen-users@lists.xen.org; Thu, 21 Feb 2013 23:33:58 +0000 Received: from [85.158.138.51:48819] by server-11.bemta-3.messagelabs.com id 09/7C-10249-4EEA6215; Thu, 21 Feb 2013 23:33:56 +0000 X-Env-Sender: daniel.farrell@gmail.com X-Msg-Ref: server-10.tower-174.messagelabs.com!1361489633!24592643!1 X-Originating-IP: [209.85.220.52] X-SpamReason: No, hits=1.1 required=7.0 tests=HTML_20_30,HTML_MESSAGE, MIME_QP_LONG_LINE, ML_RADAR_SPEW_LINKS_14, UPPERCASE_25_50, spamassassin: X-StarScan-Received: X-StarScan-Version: 6.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 17293 invoked from network); 21 Feb 2013 23:33:55 -0000 Received: from mail-pa0-f52.google.com (HELO mail-pa0-f52.google.com) (209.85.220.52) by server-10.tower-174.messagelabs.com with RC4-SHA encrypted SMTP; 21 Feb 2013 23:33:55 -0000 Received: by mail-pa0-f52.google.com with SMTP id fb1so105260pad.25 for ; Thu, 21 Feb 2013 15:33:53 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:from:content-type:subject:message-id:date:to :mime-version:x-mailer; bh=Jnm0DAOOJW3nCpUi+SYIpHcGSztfadl4uv9a1Jaz3d4=; b=DXKvVFCCA9Pd6D231ELBFc44AhuSTOjwe05ZlSsIdkhdmWSHVLmOwhEKvbWwJ//iFy 2Ts9E+NIXm1aOga86bodmvYGCNN9MWCN8qPnUy9bcdXYMt2BziQp+OP91iinxdLXMWVE hfL1LveAqA2v/b3PQ3EFkYSFctdBRAzgzCOZmGagvovfWQGoIXsb+7Qy5aQqHsmjkf/6 NEENPHPbtMsTiv/pP/9wokgMNZSeKcQ/XawxQE/40PGbSJQJV2LkhWOufwGsObuqBv5y x8+GSETOUx07Z+AnXNZIL/YQgUIpoSsaqM+in8z4s0Z42KPt+Qqy6jveeAsU+6CN7Ps5 Og8g== X-Received: by 10.68.58.3 with SMTP id m3mr57207527pbq.69.1361489633078; Thu, 21 Feb 2013 15:33:53 -0800 (PST) Received: from lady-lula-belle.home (pool-108-0-220-206.lsanca.fios.verizon.net. [108.0.220.206]) by mx.google.com with ESMTPS id qf7sm273230pbb.2.2013.02.21.15.33.50 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 21 Feb 2013 15:33:51 -0800 (PST) From: Daniel Farrell Message-Id: <4551BC87-2C3B-474A-9A79-66ADDB1FC95D@gmail.com> Date: Thu, 21 Feb 2013 15:33:49 -0800 To: "xen-users@lists.xen.org" Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\)) X-Mailer: Apple Mail (2.1499) Subject: [Xen-users] Install issues for dome as a driver domain for secondary nic with 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="===============8077815174856685164==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============8077815174856685164== Content-Type: multipart/alternative; boundary="Apple-Mail=_B3B17B3B-825C-460E-93C4-DEFDA42A4CC2" --Apple-Mail=_B3B17B3B-825C-460E-93C4-DEFDA42A4CC2 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii Hi everyone, I am attempting to setup a domU connected to my secondary nic with = pci-passthrough, which I plan to use as a firewall for future domU's. = For my dom0 I am using ubuntu 12.10 and have recompiled the kernel to = include all the xen parts. ( In dom0 ) # cat /boot/config-3.5.7.4 | grep -i xen CONFIG_XEN=3Dy CONFIG_XEN_DOM0=3Dy CONFIG_XEN_PRIVILEGED_GUEST=3Dy CONFIG_XEN_PVHVM=3Dy CONFIG_XEN_MAX_DOMAIN_MEMORY=3D500 CONFIG_XEN_SAVE_RESTORE=3Dy CONFIG_PCI_XEN=3Dy CONFIG_XEN_PCIDEV_FRONTEND=3Dy CONFIG_XEN_BLKDEV_FRONTEND=3Dy CONFIG_XEN_BLKDEV_BACKEND=3Dm CONFIG_NETXEN_NIC=3Dy CONFIG_XEN_NETDEV_FRONTEND=3Dy CONFIG_XEN_NETDEV_BACKEND=3Dy CONFIG_HVC_XEN=3Dy CONFIG_HVC_XEN_FRONTEND=3Dy # Xen driver support CONFIG_XEN_BALLOON=3Dy CONFIG_XEN_SELFBALLOONING=3Dy CONFIG_XEN_BALLOON_MEMORY_HOTPLUG=3Dy CONFIG_XEN_SCRUB_PAGES=3Dy CONFIG_XEN_DEV_EVTCHN=3Dy CONFIG_XEN_BACKEND=3Dy CONFIG_XENFS=3Dy CONFIG_XEN_COMPAT_XENFS=3Dy CONFIG_XEN_SYS_HYPERVISOR=3Dy CONFIG_XEN_XENBUS_FRONTEND=3Dy CONFIG_XEN_GNTDEV=3Dy CONFIG_XEN_GRANT_DEV_ALLOC=3Dy CONFIG_SWIOTLB_XEN=3Dy CONFIG_XEN_TMEM=3Dy CONFIG_XEN_PCIDEV_BACKEND=3Dy CONFIG_XEN_PRIVCMD=3Dy CONFIG_XEN_ACPI_PROCESSOR=3Dy My /etc/default/grub file has: GRUB_CMDLINE_LINUX=3D"apparmor=3D0 xen-pciback.hide=3D(02:01.0)" GRUB_CMDLINE_XEN=3D"dom0_mem=3D384M,max:384M dom0_max_vcpus=3D1 = no-bootscrub" In /etc/xen/xl.conf run_hotplug_scripts=3D0 because I eventually want to have additional domU's connect the firewall = as a backend # xl pci-assignable-list 0000:02:01.0 This is the correct BDF for my second nic, so I believe that I have = pci-passthrough setup correctly. I have a second 20g disk at /dev/sdb that I will be using for the lvm = setup # lvm pvcreate /dev/sdb # lvm vgcreate DomUs /dev/sdb # lvm lvcreate -L 10g -n firewall DomUs # mkfs.ext4 /dev/DomUs/firewall I have downloaded initrd.gz and vmlinuz from = http://mirror.anl.gov/pub/ubuntu/dists/quantal/main/installer-amd64/curren= t/images/netboot/xen/ and although there is no md5 entry for the two = files in = http://mirror.anl.gov/pub/ubuntu/dists/quantal/main/installer-amd64/curren= t/images/MD5SUMS I don't think my problem has to do with corruption = because I have redownloaded these two files multiple times. This is what I have for /etc/xen/firewall.cfg name =3D "firewall" memory =3D 512 disk =3D ['phy:/dev/DomUs/firewall,xvda,w'] pci =3D ['0000:02:01.0'] vif =3D ['script=3Dvif-nat'] kernel =3D "/var/lib/xen/images/ubuntu12.10-netboot/vmlinuz" ramdisk =3D "/var/lib/xen/images/ubuntu12.10-netboot/initrd.gz" extra =3D "debian-installer/exit/always_halt=3Dtrue -- console=3Dhvc0 -- = iommu=3Dsoft" The installer begins and then fails while trying to connect to the = internet. For right now I am running this all inside of VMware Fusion = with two network adapters set in bridge mode. My router is running DHCP = and my dom0 has no issues receiving an IP address, so I thought the same = would be true for eth1. I have also tried manually assigning an ip, = both manually inside of the installer and also with vif =3D ['ip=3D"192.168.1.30, NETMASK=3D"255.255.255.0", = GATEWAY=3D"192.168.1.1, script=3Dvif-nat"'] After aborting the install i see: # cat /var/log/xen/xl-firewall.log=20 Waiting for domain firewall (domid 1) to die [pid 1250] Domain 1 has shut down, reason code 0 0x0 Action for shutdown reason code 0 is destroy Domain 1 needs to be cleaned up: destroying the domain libxl: error: libxl_device.c:1085:libxl__wait_for_backend: Backend = /local/domain/0/backend/pci/1/0 not ready Done. Exiting now I feel like I am missing a step or basic setting somewhere. Any = suggestions would be greatly appreciated.=20 - Danny= --Apple-Mail=_B3B17B3B-825C-460E-93C4-DEFDA42A4CC2 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=us-ascii Hi = everyone,

I am attempting to setup a domU connected = to my secondary nic with pci-passthrough, which I plan to use as a = firewall for future domU's.  For my dom0 I am using ubuntu 12.10 = and have recompiled the kernel to include all the xen = parts.

( In dom0 )
# = cat /boot/config-3.5.7.4 | grep -i = xen
CONFIG_XEN=3Dy
CONFIG_XEN_DOM0=3Dy
= CONFIG_XEN_PRIVILEGED_GUEST=3Dy
CONFIG_XEN_PVHVM=3Dy
C= ONFIG_XEN_MAX_DOMAIN_MEMORY=3D500
CONFIG_XEN_SAVE_RESTORE=3Dy
CONFIG_PCI_XEN=3Dy
CONFIG_XEN_PCIDEV_FRONTEND=3Dy
<= div>CONFIG_XEN_BLKDEV_FRONTEND=3Dy
CONFIG_XEN_BLKDEV_BACKEND=3Dm=
CONFIG_NETXEN_NIC=3Dy
CONFIG_XEN_NETDEV_FRONTEND=3Dy<= /div>
CONFIG_XEN_NETDEV_BACKEND=3Dy
CONFIG_HVC_XEN=3Dy
=
CONFIG_HVC_XEN_FRONTEND=3Dy
# Xen driver = support
CONFIG_XEN_BALLOON=3Dy
CONFIG_XEN_SELFBALLOONI= NG=3Dy
CONFIG_XEN_BALLOON_MEMORY_HOTPLUG=3Dy
CONFIG_XE= N_SCRUB_PAGES=3Dy
CONFIG_XEN_DEV_EVTCHN=3Dy
CONFIG_XEN= _BACKEND=3Dy
CONFIG_XENFS=3Dy
CONFIG_XEN_COMPAT_XENFS=3D= y
CONFIG_XEN_SYS_HYPERVISOR=3Dy
CONFIG_XEN_XENBUS_FRON= TEND=3Dy
CONFIG_XEN_GNTDEV=3Dy
CONFIG_XEN_GRANT_DEV_AL= LOC=3Dy
CONFIG_SWIOTLB_XEN=3Dy
CONFIG_XEN_TMEM=3Dy
CONFIG_XEN_PCIDEV_BACKEND=3Dy
CONFIG_XEN_PRIVCMD=3Dy
CONFIG_XEN_ACPI_PROCESSOR=3Dy

My = /etc/default/grub file = has:
GRUB_CMDLINE_LINUX=3D"apparmor=3D0 = xen-pciback.hide=3D(02:01.0)"
GRUB_CMDLINE_XEN=3D"dom0_mem=3D384= M,max:384M dom0_max_vcpus=3D1 = no-bootscrub"

In = /etc/xen/xl.conf
run_hotplug_scripts=3D0
because I = eventually want to have additional domU's connect the firewall as a = backend

# xl = pci-assignable-list
0000:02:01.0

This = is the correct BDF for my second nic, so I believe that I have = pci-passthrough setup correctly.

I have a = second 20g disk at /dev/sdb that I will be using for the lvm = setup
# lvm pvcreate /dev/sdb
# lvm vgcreate = DomUs /dev/sdb
# lvm lvcreate -L 10g -n firewall = DomUs
# mkfs.ext4 = /dev/DomUs/firewall

I have downloaded initrd.gz = and vmlinuz from http://mirror.anl.gov/pub/ubuntu/dists/quan= tal/main/installer-amd64/current/images/netboot/xen/ and = although there is no md5 entry for the two files in http://mirror.anl.gov/pub/ubuntu/dists/quantal/m= ain/installer-amd64/current/images/MD5SUMS I don't think my = problem has to do with corruption because I have redownloaded these two = files multiple times.

This is what I have for = /etc/xen/firewall.cfg

name =3D = "firewall"
memory =3D 512
disk =3D = ['phy:/dev/DomUs/firewall,xvda,w']
pci =3D ['0000:02:01.0']
vif =3D = ['script=3Dvif-nat']
kernel =3D = "/var/lib/xen/images/ubuntu12.10-netboot/vmlinuz"
ramdisk =3D = "/var/lib/xen/images/ubuntu12.10-netboot/initrd.gz"
extra =3D = "debian-installer/exit/always_halt=3Dtrue -- console=3Dhvc0 -- = iommu=3Dsoft"

The installer begins and then = fails while trying to connect to the internet.  For right = now I am running this all inside of VMware Fusion with two network = adapters set in bridge mode.  My router is running DHCP and my dom0 = has no issues receiving an IP address, so I thought the same would be = true for eth1.  I have also tried manually assigning an ip, both = manually inside of the installer and also = with

vif =3D ['ip=3D"192.168.1.30, = NETMASK=3D"255.255.255.0", GATEWAY=3D"192.168.1.1, = script=3Dvif-nat"']

After aborting the install = i see:
# = cat /var/log/xen/xl-firewall.log 
Waiting for domain = firewall (domid 1) to die [pid 1250]
Domain 1 has shut down, reason = code 0 0x0
Action for shutdown reason code 0 is destroy
Domain 1 = needs to be cleaned up: destroying the domain
libxl: error: = libxl_device.c:1085:libxl__wait_for_backend: Backend = /local/domain/0/backend/pci/1/0 not ready
Done. Exiting = now

I feel like I am missing a step or basic setting = somewhere.  Any suggestions would be greatly = appreciated. 

 - = Danny
= --Apple-Mail=_B3B17B3B-825C-460E-93C4-DEFDA42A4CC2-- --===============8077815174856685164== 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 --===============8077815174856685164==-- From xen-users-bounces@lists.xen.org Thu Feb 21 23:35:24 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 21 Feb 2013 23:35: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 1U8feI-00088l-U4; Thu, 21 Feb 2013 23:33:58 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U8feH-00088g-LR for xen-users@lists.xen.org; Thu, 21 Feb 2013 23:33:58 +0000 Received: from [85.158.138.51:48819] by server-11.bemta-3.messagelabs.com id 09/7C-10249-4EEA6215; Thu, 21 Feb 2013 23:33:56 +0000 X-Env-Sender: daniel.farrell@gmail.com X-Msg-Ref: server-10.tower-174.messagelabs.com!1361489633!24592643!1 X-Originating-IP: [209.85.220.52] X-SpamReason: No, hits=1.1 required=7.0 tests=HTML_20_30,HTML_MESSAGE, MIME_QP_LONG_LINE, ML_RADAR_SPEW_LINKS_14, UPPERCASE_25_50, spamassassin: X-StarScan-Received: X-StarScan-Version: 6.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 17293 invoked from network); 21 Feb 2013 23:33:55 -0000 Received: from mail-pa0-f52.google.com (HELO mail-pa0-f52.google.com) (209.85.220.52) by server-10.tower-174.messagelabs.com with RC4-SHA encrypted SMTP; 21 Feb 2013 23:33:55 -0000 Received: by mail-pa0-f52.google.com with SMTP id fb1so105260pad.25 for ; Thu, 21 Feb 2013 15:33:53 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:from:content-type:subject:message-id:date:to :mime-version:x-mailer; bh=Jnm0DAOOJW3nCpUi+SYIpHcGSztfadl4uv9a1Jaz3d4=; b=DXKvVFCCA9Pd6D231ELBFc44AhuSTOjwe05ZlSsIdkhdmWSHVLmOwhEKvbWwJ//iFy 2Ts9E+NIXm1aOga86bodmvYGCNN9MWCN8qPnUy9bcdXYMt2BziQp+OP91iinxdLXMWVE hfL1LveAqA2v/b3PQ3EFkYSFctdBRAzgzCOZmGagvovfWQGoIXsb+7Qy5aQqHsmjkf/6 NEENPHPbtMsTiv/pP/9wokgMNZSeKcQ/XawxQE/40PGbSJQJV2LkhWOufwGsObuqBv5y x8+GSETOUx07Z+AnXNZIL/YQgUIpoSsaqM+in8z4s0Z42KPt+Qqy6jveeAsU+6CN7Ps5 Og8g== X-Received: by 10.68.58.3 with SMTP id m3mr57207527pbq.69.1361489633078; Thu, 21 Feb 2013 15:33:53 -0800 (PST) Received: from lady-lula-belle.home (pool-108-0-220-206.lsanca.fios.verizon.net. [108.0.220.206]) by mx.google.com with ESMTPS id qf7sm273230pbb.2.2013.02.21.15.33.50 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 21 Feb 2013 15:33:51 -0800 (PST) From: Daniel Farrell Message-Id: <4551BC87-2C3B-474A-9A79-66ADDB1FC95D@gmail.com> Date: Thu, 21 Feb 2013 15:33:49 -0800 To: "xen-users@lists.xen.org" Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\)) X-Mailer: Apple Mail (2.1499) Subject: [Xen-users] Install issues for dome as a driver domain for secondary nic with 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="===============8077815174856685164==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============8077815174856685164== Content-Type: multipart/alternative; boundary="Apple-Mail=_B3B17B3B-825C-460E-93C4-DEFDA42A4CC2" --Apple-Mail=_B3B17B3B-825C-460E-93C4-DEFDA42A4CC2 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii Hi everyone, I am attempting to setup a domU connected to my secondary nic with = pci-passthrough, which I plan to use as a firewall for future domU's. = For my dom0 I am using ubuntu 12.10 and have recompiled the kernel to = include all the xen parts. ( In dom0 ) # cat /boot/config-3.5.7.4 | grep -i xen CONFIG_XEN=3Dy CONFIG_XEN_DOM0=3Dy CONFIG_XEN_PRIVILEGED_GUEST=3Dy CONFIG_XEN_PVHVM=3Dy CONFIG_XEN_MAX_DOMAIN_MEMORY=3D500 CONFIG_XEN_SAVE_RESTORE=3Dy CONFIG_PCI_XEN=3Dy CONFIG_XEN_PCIDEV_FRONTEND=3Dy CONFIG_XEN_BLKDEV_FRONTEND=3Dy CONFIG_XEN_BLKDEV_BACKEND=3Dm CONFIG_NETXEN_NIC=3Dy CONFIG_XEN_NETDEV_FRONTEND=3Dy CONFIG_XEN_NETDEV_BACKEND=3Dy CONFIG_HVC_XEN=3Dy CONFIG_HVC_XEN_FRONTEND=3Dy # Xen driver support CONFIG_XEN_BALLOON=3Dy CONFIG_XEN_SELFBALLOONING=3Dy CONFIG_XEN_BALLOON_MEMORY_HOTPLUG=3Dy CONFIG_XEN_SCRUB_PAGES=3Dy CONFIG_XEN_DEV_EVTCHN=3Dy CONFIG_XEN_BACKEND=3Dy CONFIG_XENFS=3Dy CONFIG_XEN_COMPAT_XENFS=3Dy CONFIG_XEN_SYS_HYPERVISOR=3Dy CONFIG_XEN_XENBUS_FRONTEND=3Dy CONFIG_XEN_GNTDEV=3Dy CONFIG_XEN_GRANT_DEV_ALLOC=3Dy CONFIG_SWIOTLB_XEN=3Dy CONFIG_XEN_TMEM=3Dy CONFIG_XEN_PCIDEV_BACKEND=3Dy CONFIG_XEN_PRIVCMD=3Dy CONFIG_XEN_ACPI_PROCESSOR=3Dy My /etc/default/grub file has: GRUB_CMDLINE_LINUX=3D"apparmor=3D0 xen-pciback.hide=3D(02:01.0)" GRUB_CMDLINE_XEN=3D"dom0_mem=3D384M,max:384M dom0_max_vcpus=3D1 = no-bootscrub" In /etc/xen/xl.conf run_hotplug_scripts=3D0 because I eventually want to have additional domU's connect the firewall = as a backend # xl pci-assignable-list 0000:02:01.0 This is the correct BDF for my second nic, so I believe that I have = pci-passthrough setup correctly. I have a second 20g disk at /dev/sdb that I will be using for the lvm = setup # lvm pvcreate /dev/sdb # lvm vgcreate DomUs /dev/sdb # lvm lvcreate -L 10g -n firewall DomUs # mkfs.ext4 /dev/DomUs/firewall I have downloaded initrd.gz and vmlinuz from = http://mirror.anl.gov/pub/ubuntu/dists/quantal/main/installer-amd64/curren= t/images/netboot/xen/ and although there is no md5 entry for the two = files in = http://mirror.anl.gov/pub/ubuntu/dists/quantal/main/installer-amd64/curren= t/images/MD5SUMS I don't think my problem has to do with corruption = because I have redownloaded these two files multiple times. This is what I have for /etc/xen/firewall.cfg name =3D "firewall" memory =3D 512 disk =3D ['phy:/dev/DomUs/firewall,xvda,w'] pci =3D ['0000:02:01.0'] vif =3D ['script=3Dvif-nat'] kernel =3D "/var/lib/xen/images/ubuntu12.10-netboot/vmlinuz" ramdisk =3D "/var/lib/xen/images/ubuntu12.10-netboot/initrd.gz" extra =3D "debian-installer/exit/always_halt=3Dtrue -- console=3Dhvc0 -- = iommu=3Dsoft" The installer begins and then fails while trying to connect to the = internet. For right now I am running this all inside of VMware Fusion = with two network adapters set in bridge mode. My router is running DHCP = and my dom0 has no issues receiving an IP address, so I thought the same = would be true for eth1. I have also tried manually assigning an ip, = both manually inside of the installer and also with vif =3D ['ip=3D"192.168.1.30, NETMASK=3D"255.255.255.0", = GATEWAY=3D"192.168.1.1, script=3Dvif-nat"'] After aborting the install i see: # cat /var/log/xen/xl-firewall.log=20 Waiting for domain firewall (domid 1) to die [pid 1250] Domain 1 has shut down, reason code 0 0x0 Action for shutdown reason code 0 is destroy Domain 1 needs to be cleaned up: destroying the domain libxl: error: libxl_device.c:1085:libxl__wait_for_backend: Backend = /local/domain/0/backend/pci/1/0 not ready Done. Exiting now I feel like I am missing a step or basic setting somewhere. Any = suggestions would be greatly appreciated.=20 - Danny= --Apple-Mail=_B3B17B3B-825C-460E-93C4-DEFDA42A4CC2 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=us-ascii Hi = everyone,

I am attempting to setup a domU connected = to my secondary nic with pci-passthrough, which I plan to use as a = firewall for future domU's.  For my dom0 I am using ubuntu 12.10 = and have recompiled the kernel to include all the xen = parts.

( In dom0 )
# = cat /boot/config-3.5.7.4 | grep -i = xen
CONFIG_XEN=3Dy
CONFIG_XEN_DOM0=3Dy
= CONFIG_XEN_PRIVILEGED_GUEST=3Dy
CONFIG_XEN_PVHVM=3Dy
C= ONFIG_XEN_MAX_DOMAIN_MEMORY=3D500
CONFIG_XEN_SAVE_RESTORE=3Dy
CONFIG_PCI_XEN=3Dy
CONFIG_XEN_PCIDEV_FRONTEND=3Dy
<= div>CONFIG_XEN_BLKDEV_FRONTEND=3Dy
CONFIG_XEN_BLKDEV_BACKEND=3Dm=
CONFIG_NETXEN_NIC=3Dy
CONFIG_XEN_NETDEV_FRONTEND=3Dy<= /div>
CONFIG_XEN_NETDEV_BACKEND=3Dy
CONFIG_HVC_XEN=3Dy
=
CONFIG_HVC_XEN_FRONTEND=3Dy
# Xen driver = support
CONFIG_XEN_BALLOON=3Dy
CONFIG_XEN_SELFBALLOONI= NG=3Dy
CONFIG_XEN_BALLOON_MEMORY_HOTPLUG=3Dy
CONFIG_XE= N_SCRUB_PAGES=3Dy
CONFIG_XEN_DEV_EVTCHN=3Dy
CONFIG_XEN= _BACKEND=3Dy
CONFIG_XENFS=3Dy
CONFIG_XEN_COMPAT_XENFS=3D= y
CONFIG_XEN_SYS_HYPERVISOR=3Dy
CONFIG_XEN_XENBUS_FRON= TEND=3Dy
CONFIG_XEN_GNTDEV=3Dy
CONFIG_XEN_GRANT_DEV_AL= LOC=3Dy
CONFIG_SWIOTLB_XEN=3Dy
CONFIG_XEN_TMEM=3Dy
CONFIG_XEN_PCIDEV_BACKEND=3Dy
CONFIG_XEN_PRIVCMD=3Dy
CONFIG_XEN_ACPI_PROCESSOR=3Dy

My = /etc/default/grub file = has:
GRUB_CMDLINE_LINUX=3D"apparmor=3D0 = xen-pciback.hide=3D(02:01.0)"
GRUB_CMDLINE_XEN=3D"dom0_mem=3D384= M,max:384M dom0_max_vcpus=3D1 = no-bootscrub"

In = /etc/xen/xl.conf
run_hotplug_scripts=3D0
because I = eventually want to have additional domU's connect the firewall as a = backend

# xl = pci-assignable-list
0000:02:01.0

This = is the correct BDF for my second nic, so I believe that I have = pci-passthrough setup correctly.

I have a = second 20g disk at /dev/sdb that I will be using for the lvm = setup
# lvm pvcreate /dev/sdb
# lvm vgcreate = DomUs /dev/sdb
# lvm lvcreate -L 10g -n firewall = DomUs
# mkfs.ext4 = /dev/DomUs/firewall

I have downloaded initrd.gz = and vmlinuz from http://mirror.anl.gov/pub/ubuntu/dists/quan= tal/main/installer-amd64/current/images/netboot/xen/ and = although there is no md5 entry for the two files in http://mirror.anl.gov/pub/ubuntu/dists/quantal/m= ain/installer-amd64/current/images/MD5SUMS I don't think my = problem has to do with corruption because I have redownloaded these two = files multiple times.

This is what I have for = /etc/xen/firewall.cfg

name =3D = "firewall"
memory =3D 512
disk =3D = ['phy:/dev/DomUs/firewall,xvda,w']
pci =3D ['0000:02:01.0']
vif =3D = ['script=3Dvif-nat']
kernel =3D = "/var/lib/xen/images/ubuntu12.10-netboot/vmlinuz"
ramdisk =3D = "/var/lib/xen/images/ubuntu12.10-netboot/initrd.gz"
extra =3D = "debian-installer/exit/always_halt=3Dtrue -- console=3Dhvc0 -- = iommu=3Dsoft"

The installer begins and then = fails while trying to connect to the internet.  For right = now I am running this all inside of VMware Fusion with two network = adapters set in bridge mode.  My router is running DHCP and my dom0 = has no issues receiving an IP address, so I thought the same would be = true for eth1.  I have also tried manually assigning an ip, both = manually inside of the installer and also = with

vif =3D ['ip=3D"192.168.1.30, = NETMASK=3D"255.255.255.0", GATEWAY=3D"192.168.1.1, = script=3Dvif-nat"']

After aborting the install = i see:
# = cat /var/log/xen/xl-firewall.log 
Waiting for domain = firewall (domid 1) to die [pid 1250]
Domain 1 has shut down, reason = code 0 0x0
Action for shutdown reason code 0 is destroy
Domain 1 = needs to be cleaned up: destroying the domain
libxl: error: = libxl_device.c:1085:libxl__wait_for_backend: Backend = /local/domain/0/backend/pci/1/0 not ready
Done. Exiting = now

I feel like I am missing a step or basic setting = somewhere.  Any suggestions would be greatly = appreciated. 

 - = Danny
= --Apple-Mail=_B3B17B3B-825C-460E-93C4-DEFDA42A4CC2-- --===============8077815174856685164== 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 --===============8077815174856685164==-- From xen-users-bounces@lists.xen.org Fri Feb 22 01:54:23 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 22 Feb 2013 01:54: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 1U8hou-00067b-2O; Fri, 22 Feb 2013 01:53:04 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U8hor-00067W-JI for xen-users@lists.xen.org; Fri, 22 Feb 2013 01:53:01 +0000 Received: from [193.109.254.147:37986] by server-11.bemta-14.messagelabs.com id 6A/38-30685-C7FC6215; Fri, 22 Feb 2013 01:53:00 +0000 X-Env-Sender: eross@corp.locatrix.com X-Msg-Ref: server-8.tower-27.messagelabs.com!1361497979!9299102!1 X-Originating-IP: [74.125.83.44] 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.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 29010 invoked from network); 22 Feb 2013 01:52:59 -0000 Received: from mail-ee0-f44.google.com (HELO mail-ee0-f44.google.com) (74.125.83.44) by server-8.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 22 Feb 2013 01:52:59 -0000 Received: by mail-ee0-f44.google.com with SMTP id l10so65804eei.31 for ; Thu, 21 Feb 2013 17:52:59 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=x-received:mime-version:in-reply-to:references:from:date:message-id :subject:to:cc:content-type:x-gm-message-state; bh=dr/s5T3Np3leN1jcEwvG3iZAZZbPV6/nM1Wl8OYiXks=; b=TlcjTN3mGgp8z4niA/0gNsD1JT6ugSDHoh4mnZs9OSNewcXV7HBUT5D6tqrFXgYCaD 0AvE1gEO0p9M9dsKKH9TRyRDdKe0hhvEQzmYsIDyA6Ozxz7lZLl5p5lc1NrUaLdeNpH+ 6LRL+zngzZ5yUD6okROiMDfMEEE8r+XkR2bdg77A+SM4MyxOSINK9b8k7RgeazHvv1UK 8ZxZNtpxWg19Augg7vg/DYoZO0JGbdJqXGoE1UN9qF9/IXxaXLBtmwEhs7C5ocmgk2aE G3LzVqEYwwreOqdVfsRBiMsn0qDquNcNKxPwOj2JNlcY9gmSxMYvgIOc8PLhaMKE1Eu2 MWKA== X-Received: by 10.14.178.69 with SMTP id e45mr919064eem.9.1361497979173; Thu, 21 Feb 2013 17:52:59 -0800 (PST) MIME-Version: 1.0 Received: by 10.223.199.194 with HTTP; Thu, 21 Feb 2013 17:52:38 -0800 (PST) In-Reply-To: <5126A96A.6020105@yahoo.co.uk> References: <51229E41.2090103@yahoo.co.uk> <1361281294.8796.YahooMailNeo@web171304.mail.ir2.yahoo.com> <5126A96A.6020105@yahoo.co.uk> From: Andrew Eross Date: Thu, 21 Feb 2013 22:52:38 -0300 Message-ID: To: Ian X-Gm-Message-State: ALoCoQmCfVl+CzsjUAEYkIf8NS1cI0cTq/BfxtSOkMrMEGnPKaxuXoEDs26eqYZmaN1K3hlon7vV Cc: "xen-users@lists.xen.org" Subject: Re: [Xen-users] Xen 4.2.1 unable to get domain type for domid X-BeenThere: xen-users@lists.xen.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="===============5465460567959443394==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============5465460567959443394== Content-Type: multipart/alternative; boundary=047d7b622440697c5c04d6467391 --047d7b622440697c5c04d6467391 Content-Type: text/plain; charset=ISO-8859-1 Hi Ian, I think so!, or sorta =) To be exact, this is what my build/install steps looked like: git clone git://xenbits.xen.org/xen.git cd xen ./configure vi ./.config # PYTHON_PREFIX_ARG=--install-layout=deb # make world make deb cd ./dist ./install.sh What do you think? On Thu, Feb 21, 2013 at 8:10 PM, Ian wrote: > On 21/02/13 15:11, Andrew Eross wrote: > >> Hi Ian, >> >> Yep, confirmed, exact same images as you: >> >> 8525c3e8d6131ae462ba85b935a70b**ae vmlinuz >> f1f36dbfe47ebda085f41394dd079d**09 initrd.gz >> >> And I tried a very similar config: >> >> name = "ubuntu-calendar-test" >> memory = 1024 >> disk = ['phy:/dev/mapper/center-**calendar,xvda,w'] >> vif = [ 'mac=00:16:31:55:1c:82' ] >> kernel = "/root/ubuntu1204/vmlinuz" >> ramdisk = "/root/ubuntu1204/initrd.gz" >> vcpus = 2 >> on_reboot = 'destroy' >> on_crash = 'destroy' >> >> Unfortunately still not able to launch this VM, very strange! >> >> xl create /etc/xen/ubuntu-calendar-test.**cfg -c >> # >> Parsing config from /etc/xen/ubuntu-calendar-test.**cfg >> Daemon running with PID 28828 >> xenconsole: Could not read tty from store: No such file or directory >> libxl: error: libxl_exec.c:118:libxl_report_**child_exitstatus: console >> child [0] exited with error status 2 >> # >> >> cat /var/log/xen/xl-ubuntu-**calendar-test.log >> # >> Waiting for domain ubuntu-calendar-test (domid 2) to die [pid 27391] >> Domain 2 has shut down, reason code 3 0x3 >> Action for shutdown reason code 3 is destroy >> Domain 2 needs to be cleaned up: destroying the domain >> Done. Exiting now >> # >> >> > I am sure I had this once but can't for the life of me remember what was > wrong. > > You did use... make install-tools PYTHON_PREFIX_ARG= ? > --047d7b622440697c5c04d6467391 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Hi Ian,

I think so!, or sorta =3D)

<= div>To be exact, this is what my build/install steps looked like:

git clone git://xenbits.xen.org/xen.git
cd xen
./configure
vi ./.config
#
<= div>PYTHON_PREFIX_ARG=3D--install-layout=3Ddeb
#
make w= orld
make deb
cd ./dist
./install.sh

What do you think?

On Thu, Feb 21, 2013 at 8:10 PM, Ian <murrayie@yahoo.co.uk>= ; wrote:
On 2= 1/02/13 15:11, Andrew Eross wrote:
Hi Ian,

Yep, confirmed, exact same images as you:

8525c3e8d6131ae462ba85b935a70bae =A0vmlinuz
f1f36dbfe47ebda085f41394dd079d09 =A0initrd.gz

And I tried a very similar config:

name =A0 =A0 =A0=3D "ubuntu-calendar-test"
memory =A0 =A0=3D 1024
disk =A0 =A0 =A0=3D ['phy:/dev/mapper/center-calendar,xvda,w'= ;]
vif =3D [ 'mac=3D00:16:31:55:1c:82' ]
kernel =A0 =A0=3D "/root/ubuntu1204/vmlinuz"
ramdisk =A0 =3D "/root/ubuntu1204/initrd.gz"
vcpus =A0 =A0 =3D 2
on_reboot =3D 'destroy'
on_crash =A0=3D 'destroy'

Unfortunately still not able to launch this VM, very strange!

xl create /etc/xen/ubuntu-calendar-test.cfg -c
#
Parsing config from /etc/xen/ubuntu-calendar-test.cfg
Daemon running with PID 28828
xenconsole: Could not read tty from store: No such file or directory
libxl: error: libxl_exec.c:118:libxl_report_child_exitstatus: consol= e child [0] exited with error status 2
#

cat /var/log/xen/xl-ubuntu-calendar-test.log
#
Waiting for domain ubuntu-calendar-test (domid 2) to die [pid 27391]
Domain 2 has shut down, reason code 3 0x3
Action for shutdown reason code 3 is destroy
Domain 2 needs to be cleaned up: destroying the domain
Done. Exiting now
#


I am sure I had this once but can't for the life of me remember what wa= s wrong.

You did use... make install-tools PYTHON_PREFIX_ARG=3D =A0?

--047d7b622440697c5c04d6467391-- --===============5465460567959443394== 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 --===============5465460567959443394==-- From xen-users-bounces@lists.xen.org Fri Feb 22 01:54:23 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 22 Feb 2013 01:54: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 1U8hou-00067b-2O; Fri, 22 Feb 2013 01:53:04 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U8hor-00067W-JI for xen-users@lists.xen.org; Fri, 22 Feb 2013 01:53:01 +0000 Received: from [193.109.254.147:37986] by server-11.bemta-14.messagelabs.com id 6A/38-30685-C7FC6215; Fri, 22 Feb 2013 01:53:00 +0000 X-Env-Sender: eross@corp.locatrix.com X-Msg-Ref: server-8.tower-27.messagelabs.com!1361497979!9299102!1 X-Originating-IP: [74.125.83.44] 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.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 29010 invoked from network); 22 Feb 2013 01:52:59 -0000 Received: from mail-ee0-f44.google.com (HELO mail-ee0-f44.google.com) (74.125.83.44) by server-8.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 22 Feb 2013 01:52:59 -0000 Received: by mail-ee0-f44.google.com with SMTP id l10so65804eei.31 for ; Thu, 21 Feb 2013 17:52:59 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=x-received:mime-version:in-reply-to:references:from:date:message-id :subject:to:cc:content-type:x-gm-message-state; bh=dr/s5T3Np3leN1jcEwvG3iZAZZbPV6/nM1Wl8OYiXks=; b=TlcjTN3mGgp8z4niA/0gNsD1JT6ugSDHoh4mnZs9OSNewcXV7HBUT5D6tqrFXgYCaD 0AvE1gEO0p9M9dsKKH9TRyRDdKe0hhvEQzmYsIDyA6Ozxz7lZLl5p5lc1NrUaLdeNpH+ 6LRL+zngzZ5yUD6okROiMDfMEEE8r+XkR2bdg77A+SM4MyxOSINK9b8k7RgeazHvv1UK 8ZxZNtpxWg19Augg7vg/DYoZO0JGbdJqXGoE1UN9qF9/IXxaXLBtmwEhs7C5ocmgk2aE G3LzVqEYwwreOqdVfsRBiMsn0qDquNcNKxPwOj2JNlcY9gmSxMYvgIOc8PLhaMKE1Eu2 MWKA== X-Received: by 10.14.178.69 with SMTP id e45mr919064eem.9.1361497979173; Thu, 21 Feb 2013 17:52:59 -0800 (PST) MIME-Version: 1.0 Received: by 10.223.199.194 with HTTP; Thu, 21 Feb 2013 17:52:38 -0800 (PST) In-Reply-To: <5126A96A.6020105@yahoo.co.uk> References: <51229E41.2090103@yahoo.co.uk> <1361281294.8796.YahooMailNeo@web171304.mail.ir2.yahoo.com> <5126A96A.6020105@yahoo.co.uk> From: Andrew Eross Date: Thu, 21 Feb 2013 22:52:38 -0300 Message-ID: To: Ian X-Gm-Message-State: ALoCoQmCfVl+CzsjUAEYkIf8NS1cI0cTq/BfxtSOkMrMEGnPKaxuXoEDs26eqYZmaN1K3hlon7vV Cc: "xen-users@lists.xen.org" Subject: Re: [Xen-users] Xen 4.2.1 unable to get domain type for domid X-BeenThere: xen-users@lists.xen.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="===============5465460567959443394==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============5465460567959443394== Content-Type: multipart/alternative; boundary=047d7b622440697c5c04d6467391 --047d7b622440697c5c04d6467391 Content-Type: text/plain; charset=ISO-8859-1 Hi Ian, I think so!, or sorta =) To be exact, this is what my build/install steps looked like: git clone git://xenbits.xen.org/xen.git cd xen ./configure vi ./.config # PYTHON_PREFIX_ARG=--install-layout=deb # make world make deb cd ./dist ./install.sh What do you think? On Thu, Feb 21, 2013 at 8:10 PM, Ian wrote: > On 21/02/13 15:11, Andrew Eross wrote: > >> Hi Ian, >> >> Yep, confirmed, exact same images as you: >> >> 8525c3e8d6131ae462ba85b935a70b**ae vmlinuz >> f1f36dbfe47ebda085f41394dd079d**09 initrd.gz >> >> And I tried a very similar config: >> >> name = "ubuntu-calendar-test" >> memory = 1024 >> disk = ['phy:/dev/mapper/center-**calendar,xvda,w'] >> vif = [ 'mac=00:16:31:55:1c:82' ] >> kernel = "/root/ubuntu1204/vmlinuz" >> ramdisk = "/root/ubuntu1204/initrd.gz" >> vcpus = 2 >> on_reboot = 'destroy' >> on_crash = 'destroy' >> >> Unfortunately still not able to launch this VM, very strange! >> >> xl create /etc/xen/ubuntu-calendar-test.**cfg -c >> # >> Parsing config from /etc/xen/ubuntu-calendar-test.**cfg >> Daemon running with PID 28828 >> xenconsole: Could not read tty from store: No such file or directory >> libxl: error: libxl_exec.c:118:libxl_report_**child_exitstatus: console >> child [0] exited with error status 2 >> # >> >> cat /var/log/xen/xl-ubuntu-**calendar-test.log >> # >> Waiting for domain ubuntu-calendar-test (domid 2) to die [pid 27391] >> Domain 2 has shut down, reason code 3 0x3 >> Action for shutdown reason code 3 is destroy >> Domain 2 needs to be cleaned up: destroying the domain >> Done. Exiting now >> # >> >> > I am sure I had this once but can't for the life of me remember what was > wrong. > > You did use... make install-tools PYTHON_PREFIX_ARG= ? > --047d7b622440697c5c04d6467391 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Hi Ian,

I think so!, or sorta =3D)

<= div>To be exact, this is what my build/install steps looked like:

git clone git://xenbits.xen.org/xen.git
cd xen
./configure
vi ./.config
#
<= div>PYTHON_PREFIX_ARG=3D--install-layout=3Ddeb
#
make w= orld
make deb
cd ./dist
./install.sh

What do you think?

On Thu, Feb 21, 2013 at 8:10 PM, Ian <murrayie@yahoo.co.uk>= ; wrote:
On 2= 1/02/13 15:11, Andrew Eross wrote:
Hi Ian,

Yep, confirmed, exact same images as you:

8525c3e8d6131ae462ba85b935a70bae =A0vmlinuz
f1f36dbfe47ebda085f41394dd079d09 =A0initrd.gz

And I tried a very similar config:

name =A0 =A0 =A0=3D "ubuntu-calendar-test"
memory =A0 =A0=3D 1024
disk =A0 =A0 =A0=3D ['phy:/dev/mapper/center-calendar,xvda,w'= ;]
vif =3D [ 'mac=3D00:16:31:55:1c:82' ]
kernel =A0 =A0=3D "/root/ubuntu1204/vmlinuz"
ramdisk =A0 =3D "/root/ubuntu1204/initrd.gz"
vcpus =A0 =A0 =3D 2
on_reboot =3D 'destroy'
on_crash =A0=3D 'destroy'

Unfortunately still not able to launch this VM, very strange!

xl create /etc/xen/ubuntu-calendar-test.cfg -c
#
Parsing config from /etc/xen/ubuntu-calendar-test.cfg
Daemon running with PID 28828
xenconsole: Could not read tty from store: No such file or directory
libxl: error: libxl_exec.c:118:libxl_report_child_exitstatus: consol= e child [0] exited with error status 2
#

cat /var/log/xen/xl-ubuntu-calendar-test.log
#
Waiting for domain ubuntu-calendar-test (domid 2) to die [pid 27391]
Domain 2 has shut down, reason code 3 0x3
Action for shutdown reason code 3 is destroy
Domain 2 needs to be cleaned up: destroying the domain
Done. Exiting now
#


I am sure I had this once but can't for the life of me remember what wa= s wrong.

You did use... make install-tools PYTHON_PREFIX_ARG=3D =A0?

--047d7b622440697c5c04d6467391-- --===============5465460567959443394== 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 --===============5465460567959443394==-- From xen-users-bounces@lists.xen.org Fri Feb 22 02:32:17 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 22 Feb 2013 02:32: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 1U8iPc-0007CR-FZ; Fri, 22 Feb 2013 02:31:00 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U8iPa-0007A0-E9 for xen-users@lists.xen.org; Fri, 22 Feb 2013 02:30:58 +0000 Received: from [85.158.143.99:31278] by server-1.bemta-4.messagelabs.com id CA/FE-06203-168D6215; Fri, 22 Feb 2013 02:30:57 +0000 X-Env-Sender: murrayie@yahoo.co.uk X-Msg-Ref: server-13.tower-216.messagelabs.com!1361500256!27721448!1 X-Originating-IP: [77.238.189.76] X-SpamReason: No, hits=0.6 required=7.0 tests=HTML_40_50,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 19216 invoked from network); 22 Feb 2013 02:30:56 -0000 Received: from nm19.bullet.mail.ird.yahoo.com (HELO nm19.bullet.mail.ird.yahoo.com) (77.238.189.76) by server-13.tower-216.messagelabs.com with SMTP; 22 Feb 2013 02:30:56 -0000 Received: from [77.238.189.56] by nm19.bullet.mail.ird.yahoo.com with NNFMP; 22 Feb 2013 02:30:56 -0000 Received: from [217.146.188.152] by tm9.bullet.mail.ird.yahoo.com with NNFMP; 22 Feb 2013 02:30:56 -0000 Received: from [127.0.0.1] by smtp110.mail.ird.yahoo.com with NNFMP; 22 Feb 2013 02:30:56 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.co.uk; s=s1024; t=1361500255; bh=TWXxQDEd84rM3ZyFBn3rop8JBIFYeASTWoOLvIJAbT0=; 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:CC:Subject:References:In-Reply-To:Content-Type; b=WcIt/fUapoW5kHc1FH8Y9G7lSVXwRFYRGZbOIPEoMFGN1jRNW7Xn11NoRoGVT00f4s90qhiEiCpca9Z/kBDmt1xFeuZLipu5zoUMmjaEn2sx7Mj/AByd5wd4nIVrHR2TIzYTq9BWe/JSM7XJMbypCLM2dPj0uJvqJ2YzQGG/Yys= X-Yahoo-Newman-Id: 999246.48809.bm@smtp110.mail.ird.yahoo.com X-Yahoo-Newman-Property: ymail-3 X-YMail-OSG: 6lj2O6kVM1lC8Ij30x1snbyfhBiM9IwEh.ES1aRvSPodgyu ph7wNyz6Ni4bCFlEZmw.QtHuDlSASiMS0tvTl4BoOvS2udYZMt4aOYrAAqis rCDQxh.wjMrG.pJYaYXf4g66UEhOotK1oFJVie8DRpURQP0glk2YMvH.2i7o FOVtNOzabtBdLqEwhHRzymrk1jeRZvAyXPQMdn_dbwo6lgxjXNign2tp9b54 6Gvzx_jRyUf4jMR0qkEUaAZZKWNbSfnWR2jLhlfsvkxOn1rlRFASDQjRQvxz hXQ9SkcuxC2kCnTDfIlnuLDYub2_7lHKPI9QU2XZ2oscopmTBck_qOle83U_ zwTgNGFlEg.uCmaEpUbtCgUYDNGHPDsG3TnEpXED3ZogV_tJN97V8Pl.96Ga .9goAHPcJlTdDD9tFc0y4ccjXCtYguXTqlNO9aIkje3yxenGfrevVYyXQ1X0 4JTE7hPExNdYJ8LMgoruj.GvQqOBEghjJrb_ynEYrN2_RuX_D1ledWC9Djmo 0TP_eC1kJ_z6dRux_7bVjkA-- X-Yahoo-SMTP: P.LfrmaswBDlKN6tCvtOaEZlSVsY Received: from [192.168.1.136] (murrayie@109.157.15.99 with plain) by smtp110.mail.ird.yahoo.com with SMTP; 21 Feb 2013 18:30:55 -0800 PST Message-ID: <5126D860.4060100@yahoo.co.uk> Date: Fri, 22 Feb 2013 02:30:56 +0000 From: Ian User-Agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/20130106 Thunderbird/17.0.2 MIME-Version: 1.0 To: Andrew Eross References: <51229E41.2090103@yahoo.co.uk> <1361281294.8796.YahooMailNeo@web171304.mail.ir2.yahoo.com> <5126A96A.6020105@yahoo.co.uk> In-Reply-To: Cc: "xen-users@lists.xen.org" Subject: Re: [Xen-users] Xen 4.2.1 unable to get domain type for domid X-BeenThere: xen-users@lists.xen.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="===============3255954583347947031==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org This is a multi-part message in MIME format. --===============3255954583347947031== Content-Type: multipart/alternative; boundary="------------050200000808070904020101" This is a multi-part message in MIME format. --------------050200000808070904020101 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit On 22/02/13 01:52, Andrew Eross wrote: > Hi Ian, > > I think so!, or sorta =) > > To be exact, this is what my build/install steps looked like: > > git clone git://xenbits.xen.org/xen.git > cd xen > ./configure > vi ./.config > # > PYTHON_PREFIX_ARG=--install-layout=deb > # > make world > make deb > cd ./dist > ./install.sh > > What do you think? > I think I had the error you had when 64 bits libs went in the wrong place. See if this applies to you. From the Wiki... Library Installation Directory Xen 4.2 onwards defaults to installing libraries into /usr/lib by default. Users on systems which use /usr/lib64 for 64-bit libraries should use the --libdir option. e.g: $ ./configure --libdir=/usr/lib64 Also from the wiki, the python_prefix_arg needs to be blank like below for certain dists due to a bug. Well, as far as I remember, I normally get the release bundle, then... ./configure --libdir=/usr/lib64 make xen (I think) make stubdom (I think) make tools (I think) make install-xen make install-stubdom (I think) make install-tools PYTHON_PREFIX_ARG= make install-docs update-rc.d xencommons defaults update-rc.d xendomains defaults fiddle about with grub, fix xendomains, insert network bridge script somewhere, etc... --------------050200000808070904020101 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit
On 22/02/13 01:52, Andrew Eross wrote:
Hi Ian,

I think so!, or sorta =)

To be exact, this is what my build/install steps looked like:

git clone git://xenbits.xen.org/xen.git
cd xen
./configure
vi ./.config
#
PYTHON_PREFIX_ARG=--install-layout=deb
#
make world
make deb
cd ./dist
./install.sh

What do you think?

I think I had the error you had when 64 bits libs went in the wrong place. See if this applies to you. From the Wiki...

Library Installation Directory

Xen 4.2 onwards defaults to installing libraries into /usr/lib by default. Users on systems which use /usr/lib64 for 64-bit libraries should use the --libdir option. e.g: 

$ ./configure --libdir=/usr/lib64


Also from the wiki, the python_prefix_arg needs to be blank like below for certain dists due to a bug.


Well, as far as I remember, I normally get the release bundle, then...

./configure --libdir=/usr/lib64
make xen (I think)
make stubdom (I think)
make tools (I think)
make install-xen
make install-stubdom (I think)
make install-tools PYTHON_PREFIX_ARG=
make install-docs

update-rc.d xencommons defaults
update-rc.d xendomains defaults

fiddle about with grub, fix xendomains, insert network bridge script somewhere, etc...




--------------050200000808070904020101-- --===============3255954583347947031== 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 --===============3255954583347947031==-- From xen-users-bounces@lists.xen.org Fri Feb 22 02:32:17 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 22 Feb 2013 02:32: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 1U8iPc-0007CR-FZ; Fri, 22 Feb 2013 02:31:00 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U8iPa-0007A0-E9 for xen-users@lists.xen.org; Fri, 22 Feb 2013 02:30:58 +0000 Received: from [85.158.143.99:31278] by server-1.bemta-4.messagelabs.com id CA/FE-06203-168D6215; Fri, 22 Feb 2013 02:30:57 +0000 X-Env-Sender: murrayie@yahoo.co.uk X-Msg-Ref: server-13.tower-216.messagelabs.com!1361500256!27721448!1 X-Originating-IP: [77.238.189.76] X-SpamReason: No, hits=0.6 required=7.0 tests=HTML_40_50,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 19216 invoked from network); 22 Feb 2013 02:30:56 -0000 Received: from nm19.bullet.mail.ird.yahoo.com (HELO nm19.bullet.mail.ird.yahoo.com) (77.238.189.76) by server-13.tower-216.messagelabs.com with SMTP; 22 Feb 2013 02:30:56 -0000 Received: from [77.238.189.56] by nm19.bullet.mail.ird.yahoo.com with NNFMP; 22 Feb 2013 02:30:56 -0000 Received: from [217.146.188.152] by tm9.bullet.mail.ird.yahoo.com with NNFMP; 22 Feb 2013 02:30:56 -0000 Received: from [127.0.0.1] by smtp110.mail.ird.yahoo.com with NNFMP; 22 Feb 2013 02:30:56 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.co.uk; s=s1024; t=1361500255; bh=TWXxQDEd84rM3ZyFBn3rop8JBIFYeASTWoOLvIJAbT0=; 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:CC:Subject:References:In-Reply-To:Content-Type; b=WcIt/fUapoW5kHc1FH8Y9G7lSVXwRFYRGZbOIPEoMFGN1jRNW7Xn11NoRoGVT00f4s90qhiEiCpca9Z/kBDmt1xFeuZLipu5zoUMmjaEn2sx7Mj/AByd5wd4nIVrHR2TIzYTq9BWe/JSM7XJMbypCLM2dPj0uJvqJ2YzQGG/Yys= X-Yahoo-Newman-Id: 999246.48809.bm@smtp110.mail.ird.yahoo.com X-Yahoo-Newman-Property: ymail-3 X-YMail-OSG: 6lj2O6kVM1lC8Ij30x1snbyfhBiM9IwEh.ES1aRvSPodgyu ph7wNyz6Ni4bCFlEZmw.QtHuDlSASiMS0tvTl4BoOvS2udYZMt4aOYrAAqis rCDQxh.wjMrG.pJYaYXf4g66UEhOotK1oFJVie8DRpURQP0glk2YMvH.2i7o FOVtNOzabtBdLqEwhHRzymrk1jeRZvAyXPQMdn_dbwo6lgxjXNign2tp9b54 6Gvzx_jRyUf4jMR0qkEUaAZZKWNbSfnWR2jLhlfsvkxOn1rlRFASDQjRQvxz hXQ9SkcuxC2kCnTDfIlnuLDYub2_7lHKPI9QU2XZ2oscopmTBck_qOle83U_ zwTgNGFlEg.uCmaEpUbtCgUYDNGHPDsG3TnEpXED3ZogV_tJN97V8Pl.96Ga .9goAHPcJlTdDD9tFc0y4ccjXCtYguXTqlNO9aIkje3yxenGfrevVYyXQ1X0 4JTE7hPExNdYJ8LMgoruj.GvQqOBEghjJrb_ynEYrN2_RuX_D1ledWC9Djmo 0TP_eC1kJ_z6dRux_7bVjkA-- X-Yahoo-SMTP: P.LfrmaswBDlKN6tCvtOaEZlSVsY Received: from [192.168.1.136] (murrayie@109.157.15.99 with plain) by smtp110.mail.ird.yahoo.com with SMTP; 21 Feb 2013 18:30:55 -0800 PST Message-ID: <5126D860.4060100@yahoo.co.uk> Date: Fri, 22 Feb 2013 02:30:56 +0000 From: Ian User-Agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/20130106 Thunderbird/17.0.2 MIME-Version: 1.0 To: Andrew Eross References: <51229E41.2090103@yahoo.co.uk> <1361281294.8796.YahooMailNeo@web171304.mail.ir2.yahoo.com> <5126A96A.6020105@yahoo.co.uk> In-Reply-To: Cc: "xen-users@lists.xen.org" Subject: Re: [Xen-users] Xen 4.2.1 unable to get domain type for domid X-BeenThere: xen-users@lists.xen.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="===============3255954583347947031==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org This is a multi-part message in MIME format. --===============3255954583347947031== Content-Type: multipart/alternative; boundary="------------050200000808070904020101" This is a multi-part message in MIME format. --------------050200000808070904020101 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit On 22/02/13 01:52, Andrew Eross wrote: > Hi Ian, > > I think so!, or sorta =) > > To be exact, this is what my build/install steps looked like: > > git clone git://xenbits.xen.org/xen.git > cd xen > ./configure > vi ./.config > # > PYTHON_PREFIX_ARG=--install-layout=deb > # > make world > make deb > cd ./dist > ./install.sh > > What do you think? > I think I had the error you had when 64 bits libs went in the wrong place. See if this applies to you. From the Wiki... Library Installation Directory Xen 4.2 onwards defaults to installing libraries into /usr/lib by default. Users on systems which use /usr/lib64 for 64-bit libraries should use the --libdir option. e.g: $ ./configure --libdir=/usr/lib64 Also from the wiki, the python_prefix_arg needs to be blank like below for certain dists due to a bug. Well, as far as I remember, I normally get the release bundle, then... ./configure --libdir=/usr/lib64 make xen (I think) make stubdom (I think) make tools (I think) make install-xen make install-stubdom (I think) make install-tools PYTHON_PREFIX_ARG= make install-docs update-rc.d xencommons defaults update-rc.d xendomains defaults fiddle about with grub, fix xendomains, insert network bridge script somewhere, etc... --------------050200000808070904020101 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit
On 22/02/13 01:52, Andrew Eross wrote:
Hi Ian,

I think so!, or sorta =)

To be exact, this is what my build/install steps looked like:

git clone git://xenbits.xen.org/xen.git
cd xen
./configure
vi ./.config
#
PYTHON_PREFIX_ARG=--install-layout=deb
#
make world
make deb
cd ./dist
./install.sh

What do you think?

I think I had the error you had when 64 bits libs went in the wrong place. See if this applies to you. From the Wiki...

Library Installation Directory

Xen 4.2 onwards defaults to installing libraries into /usr/lib by default. Users on systems which use /usr/lib64 for 64-bit libraries should use the --libdir option. e.g: 

$ ./configure --libdir=/usr/lib64


Also from the wiki, the python_prefix_arg needs to be blank like below for certain dists due to a bug.


Well, as far as I remember, I normally get the release bundle, then...

./configure --libdir=/usr/lib64
make xen (I think)
make stubdom (I think)
make tools (I think)
make install-xen
make install-stubdom (I think)
make install-tools PYTHON_PREFIX_ARG=
make install-docs

update-rc.d xencommons defaults
update-rc.d xendomains defaults

fiddle about with grub, fix xendomains, insert network bridge script somewhere, etc...




--------------050200000808070904020101-- --===============3255954583347947031== 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 --===============3255954583347947031==-- From xen-users-bounces@lists.xen.org Fri Feb 22 08:37:18 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 22 Feb 2013 08:37: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 1U8o70-0006Mo-Ns; Fri, 22 Feb 2013 08:36:10 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U8o6y-0006MT-NR; Fri, 22 Feb 2013 08:36:08 +0000 Received: from [85.158.139.83:47821] by server-16.bemta-5.messagelabs.com id 71/52-14948-7FD27215; Fri, 22 Feb 2013 08:36:07 +0000 X-Env-Sender: Ian.Campbell@citrix.com X-Msg-Ref: server-13.tower-182.messagelabs.com!1361522153!27891089!1 X-Originating-IP: [46.33.159.39] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNDYuMzMuMTU5LjM5ID0+IDIzNDMy\n X-StarScan-Received: X-StarScan-Version: 6.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 5891 invoked from network); 22 Feb 2013 08:35:54 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (46.33.159.39) by server-13.tower-182.messagelabs.com with RC4-SHA encrypted SMTP; 22 Feb 2013 08:35:54 -0000 X-IronPort-AV: E=Sophos;i="4.84,714,1355097600"; d="scan'208";a="1770539" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 22 Feb 2013 08:35: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.297.1; Fri, 22 Feb 2013 08:35:53 +0000 Message-ID: <1361522152.26546.97.camel@zakaz.uk.xensource.com> From: Ian Campbell To: Amit More Date: Fri, 22 Feb 2013 08:35:52 +0000 In-Reply-To: References: Organization: Citrix Systems, Inc. X-Mailer: Evolution 3.4.4-1 MIME-Version: 1.0 Cc: "xen-users@lists.xen.org" , xen-api@lists.xen.org Subject: Re: [Xen-users] Error Starting Virtual Machines on XCP X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: 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 Amit, Questions about XCP are generally better asked on the (badly named) xen-api@ list. I've CCd it for you here. Cheers, Ian. On Thu, 2013-02-21 at 19:34 +0000, Amit More wrote: > Hi All, > > I have XCP 1.1.0-50674c running on a Dell PowerEdge 2950 system with a > couple of virtual machines running on it. The virtual machines that > are currently running are working fine, however I cannot start the > virtual machines are are currently powered off. The error in the > XenCenter (version 6) logs says "Internal error: > Device.PV_Vnc.Failed_to_start". I also tried to start the virtual > machine using xe command but to no avail. I have tried to start > different virtual machines on the same XCP hosts, and I get the same > error (mentioned above) every time I try to start a virtual machine. > The XCP system tries to start the virtual machine for about 20-25 > minutes before giving up. > > I haven't added or removed any hardware from the Dell PowerEdge system > on which XCP is running. The only modifications to the virtual > machines were adding (and removing) network interfaces. I also suspect > that if I take the running virtual machines down, I won't be able to > bring them back up again. > > I searched the internet for answers, but couldn't find any convincing > ones. Any help would be greatly appreciated. > > Thanks, > Amit > _______________________________________________ > 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 Feb 22 08:37:18 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 22 Feb 2013 08:37: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 1U8o70-0006Mo-Ns; Fri, 22 Feb 2013 08:36:10 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U8o6y-0006MT-NR; Fri, 22 Feb 2013 08:36:08 +0000 Received: from [85.158.139.83:47821] by server-16.bemta-5.messagelabs.com id 71/52-14948-7FD27215; Fri, 22 Feb 2013 08:36:07 +0000 X-Env-Sender: Ian.Campbell@citrix.com X-Msg-Ref: server-13.tower-182.messagelabs.com!1361522153!27891089!1 X-Originating-IP: [46.33.159.39] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNDYuMzMuMTU5LjM5ID0+IDIzNDMy\n X-StarScan-Received: X-StarScan-Version: 6.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 5891 invoked from network); 22 Feb 2013 08:35:54 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (46.33.159.39) by server-13.tower-182.messagelabs.com with RC4-SHA encrypted SMTP; 22 Feb 2013 08:35:54 -0000 X-IronPort-AV: E=Sophos;i="4.84,714,1355097600"; d="scan'208";a="1770539" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 22 Feb 2013 08:35: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.297.1; Fri, 22 Feb 2013 08:35:53 +0000 Message-ID: <1361522152.26546.97.camel@zakaz.uk.xensource.com> From: Ian Campbell To: Amit More Date: Fri, 22 Feb 2013 08:35:52 +0000 In-Reply-To: References: Organization: Citrix Systems, Inc. X-Mailer: Evolution 3.4.4-1 MIME-Version: 1.0 Cc: "xen-users@lists.xen.org" , xen-api@lists.xen.org Subject: Re: [Xen-users] Error Starting Virtual Machines on XCP X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: 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 Amit, Questions about XCP are generally better asked on the (badly named) xen-api@ list. I've CCd it for you here. Cheers, Ian. On Thu, 2013-02-21 at 19:34 +0000, Amit More wrote: > Hi All, > > I have XCP 1.1.0-50674c running on a Dell PowerEdge 2950 system with a > couple of virtual machines running on it. The virtual machines that > are currently running are working fine, however I cannot start the > virtual machines are are currently powered off. The error in the > XenCenter (version 6) logs says "Internal error: > Device.PV_Vnc.Failed_to_start". I also tried to start the virtual > machine using xe command but to no avail. I have tried to start > different virtual machines on the same XCP hosts, and I get the same > error (mentioned above) every time I try to start a virtual machine. > The XCP system tries to start the virtual machine for about 20-25 > minutes before giving up. > > I haven't added or removed any hardware from the Dell PowerEdge system > on which XCP is running. The only modifications to the virtual > machines were adding (and removing) network interfaces. I also suspect > that if I take the running virtual machines down, I won't be able to > bring them back up again. > > I searched the internet for answers, but couldn't find any convincing > ones. Any help would be greatly appreciated. > > Thanks, > Amit > _______________________________________________ > 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 Feb 22 08:46:49 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 22 Feb 2013 08:46: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 1U8oGV-00071n-Eh; Fri, 22 Feb 2013 08:45:59 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U8oGU-00071d-38 for xen-users@lists.xen.org; Fri, 22 Feb 2013 08:45:58 +0000 Received: from [193.109.254.147:38130] by server-8.bemta-14.messagelabs.com id 41/EB-17325-54037215; Fri, 22 Feb 2013 08:45:57 +0000 X-Env-Sender: Ian.Campbell@citrix.com X-Msg-Ref: server-12.tower-27.messagelabs.com!1361522314!9270255!1 X-Originating-IP: [46.33.159.39] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNDYuMzMuMTU5LjM5ID0+IDIzNDMy\n X-StarScan-Received: X-StarScan-Version: 6.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 9747 invoked from network); 22 Feb 2013 08:38:35 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (46.33.159.39) by server-12.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 22 Feb 2013 08:38:35 -0000 X-IronPort-AV: E=Sophos;i="4.84,714,1355097600"; d="scan'208";a="1770620" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 22 Feb 2013 08:38:35 +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.297.1; Fri, 22 Feb 2013 08:38:34 +0000 Message-ID: <1361522313.26546.100.camel@zakaz.uk.xensource.com> From: Ian Campbell To: jacek burghardt Date: Fri, 22 Feb 2013 08:38:33 +0000 In-Reply-To: References: Organization: Citrix Systems, Inc. X-Mailer: Evolution 3.4.4-1 MIME-Version: 1.0 Cc: xen-users Subject: Re: [Xen-users] qemu-system-i386 on 64 bit system X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: 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, 2013-02-21 at 20:46 +0000, jacek burghardt wrote: > I have qemu-system-i386 that crashes when I setup to use qemu-xen. In the absence of any logs or further details about your configuration (versions, cfg etc) I don't see how you expect anyone to answer this. > Also why is xen defaulting qemu to i386 and disbles 64 bit ? Xen doesn't use any of the CPU emulation features of qemu, those are provided by the hardware and some small amount of emulation in the hypervisor itself. What Xen gets from qemu is the hardware models (e.g. IDE devices, network devices etc) which are independent from the CPU. So the choice of i386 or x86_64 is pretty much arbitrary and we happen to use i386, but we still support 64-bit. Ian. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Fri Feb 22 08:46:49 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 22 Feb 2013 08:46: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 1U8oGV-00071n-Eh; Fri, 22 Feb 2013 08:45:59 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U8oGU-00071d-38 for xen-users@lists.xen.org; Fri, 22 Feb 2013 08:45:58 +0000 Received: from [193.109.254.147:38130] by server-8.bemta-14.messagelabs.com id 41/EB-17325-54037215; Fri, 22 Feb 2013 08:45:57 +0000 X-Env-Sender: Ian.Campbell@citrix.com X-Msg-Ref: server-12.tower-27.messagelabs.com!1361522314!9270255!1 X-Originating-IP: [46.33.159.39] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNDYuMzMuMTU5LjM5ID0+IDIzNDMy\n X-StarScan-Received: X-StarScan-Version: 6.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 9747 invoked from network); 22 Feb 2013 08:38:35 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (46.33.159.39) by server-12.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 22 Feb 2013 08:38:35 -0000 X-IronPort-AV: E=Sophos;i="4.84,714,1355097600"; d="scan'208";a="1770620" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 22 Feb 2013 08:38:35 +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.297.1; Fri, 22 Feb 2013 08:38:34 +0000 Message-ID: <1361522313.26546.100.camel@zakaz.uk.xensource.com> From: Ian Campbell To: jacek burghardt Date: Fri, 22 Feb 2013 08:38:33 +0000 In-Reply-To: References: Organization: Citrix Systems, Inc. X-Mailer: Evolution 3.4.4-1 MIME-Version: 1.0 Cc: xen-users Subject: Re: [Xen-users] qemu-system-i386 on 64 bit system X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: 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, 2013-02-21 at 20:46 +0000, jacek burghardt wrote: > I have qemu-system-i386 that crashes when I setup to use qemu-xen. In the absence of any logs or further details about your configuration (versions, cfg etc) I don't see how you expect anyone to answer this. > Also why is xen defaulting qemu to i386 and disbles 64 bit ? Xen doesn't use any of the CPU emulation features of qemu, those are provided by the hardware and some small amount of emulation in the hypervisor itself. What Xen gets from qemu is the hardware models (e.g. IDE devices, network devices etc) which are independent from the CPU. So the choice of i386 or x86_64 is pretty much arbitrary and we happen to use i386, but we still support 64-bit. Ian. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Fri Feb 22 16:25:05 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 22 Feb 2013 16:25: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 1U8vPO-0000Er-Vf; Fri, 22 Feb 2013 16:23:38 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U8vPN-0000Em-BU for xen-users@lists.xen.org; Fri, 22 Feb 2013 16:23:37 +0000 Received: from [193.109.254.147:41985] by server-15.bemta-14.messagelabs.com id B7/88-24599-88B97215; Fri, 22 Feb 2013 16:23:36 +0000 X-Env-Sender: jaceksburghardt@gmail.com X-Msg-Ref: server-4.tower-27.messagelabs.com!1361550214!8700062!1 X-Originating-IP: [209.85.210.181] 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.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 15403 invoked from network); 22 Feb 2013 16:23:36 -0000 Received: from mail-ia0-f181.google.com (HELO mail-ia0-f181.google.com) (209.85.210.181) by server-4.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 22 Feb 2013 16:23:36 -0000 Received: by mail-ia0-f181.google.com with SMTP id e16so663418iaa.40 for ; Fri, 22 Feb 2013 08:23:34 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:date:message-id:subject:from:to :content-type; bh=0dWhWYWOOOhhYGFip5lRVH/+xHSfUid/ID8RrUrV7Bo=; b=KMQ3vINP+x5JBk9B7F/Ly/BnB6PdcdEB3p5If5OMvHLqhOxRXe3P+1EDn1OwsiK6MB QQeQ7yH1YACkpbpydvm1irDOFzYgu1+UCRuDe3mgNsJxE9u3z3KBW/75s+5M+1EfYkZw 0JNzDv8baJYwEGN/QaO3Ym6n22PVBsXfEfguhM3StAhzXy7/EoGI4qeqFYGaTqqsIJSh xaEzfOOJfDUfCgkBQltJoik+dPthZ2J1n2rhPTsvflwxyQHO66Coc/uPt+sKWv/sVyAy 9Zi3wZUcVtkODV/hnPKwkj+ojGgD1NBo3x1fJLlEPff447L5lL/GqCd4UbQyyPlciwRg Is6g== MIME-Version: 1.0 X-Received: by 10.42.133.133 with SMTP id h5mr1001512ict.45.1361550214434; Fri, 22 Feb 2013 08:23:34 -0800 (PST) Received: by 10.42.41.5 with HTTP; Fri, 22 Feb 2013 08:23:34 -0800 (PST) Date: Fri, 22 Feb 2013 09:23:34 -0700 Message-ID: From: jacek burghardt To: xen-users Subject: [Xen-users] failed to add gnttab to physmap X-BeenThere: xen-users@lists.xen.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="===============7605358509559342253==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============7605358509559342253== Content-Type: multipart/alternative; boundary=90e6ba5bc09de00e7d04d6529ceb --90e6ba5bc09de00e7d04d6529ceb Content-Type: text/plain; charset=ISO-8859-1 I have two dell servers running arch linux and xen 4.3 One of them had after installing lates xen 4.3 had been showing this error message" failed to add gnttab to physmap " I reverted back to git pull from 02/17/13 and virtual machines start fine. Can sommone point me in righ direction what could be causing the error message --90e6ba5bc09de00e7d04d6529ceb Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable I have two dell servers running arch linux and xen 4.3 One of them had afte= r installing lates xen 4.3 had been=A0showing=A0this error message" fa= iled to add gnttab to physmap " I reverted back to git pull from 02/17= /13 and virtual machines start fine. Can sommone point me in righ direction= what=A0could=A0be causing the error message=A0 --90e6ba5bc09de00e7d04d6529ceb-- --===============7605358509559342253== 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 --===============7605358509559342253==-- From xen-users-bounces@lists.xen.org Fri Feb 22 16:25:05 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 22 Feb 2013 16:25: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 1U8vPO-0000Er-Vf; Fri, 22 Feb 2013 16:23:38 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U8vPN-0000Em-BU for xen-users@lists.xen.org; Fri, 22 Feb 2013 16:23:37 +0000 Received: from [193.109.254.147:41985] by server-15.bemta-14.messagelabs.com id B7/88-24599-88B97215; Fri, 22 Feb 2013 16:23:36 +0000 X-Env-Sender: jaceksburghardt@gmail.com X-Msg-Ref: server-4.tower-27.messagelabs.com!1361550214!8700062!1 X-Originating-IP: [209.85.210.181] 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.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 15403 invoked from network); 22 Feb 2013 16:23:36 -0000 Received: from mail-ia0-f181.google.com (HELO mail-ia0-f181.google.com) (209.85.210.181) by server-4.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 22 Feb 2013 16:23:36 -0000 Received: by mail-ia0-f181.google.com with SMTP id e16so663418iaa.40 for ; Fri, 22 Feb 2013 08:23:34 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:date:message-id:subject:from:to :content-type; bh=0dWhWYWOOOhhYGFip5lRVH/+xHSfUid/ID8RrUrV7Bo=; b=KMQ3vINP+x5JBk9B7F/Ly/BnB6PdcdEB3p5If5OMvHLqhOxRXe3P+1EDn1OwsiK6MB QQeQ7yH1YACkpbpydvm1irDOFzYgu1+UCRuDe3mgNsJxE9u3z3KBW/75s+5M+1EfYkZw 0JNzDv8baJYwEGN/QaO3Ym6n22PVBsXfEfguhM3StAhzXy7/EoGI4qeqFYGaTqqsIJSh xaEzfOOJfDUfCgkBQltJoik+dPthZ2J1n2rhPTsvflwxyQHO66Coc/uPt+sKWv/sVyAy 9Zi3wZUcVtkODV/hnPKwkj+ojGgD1NBo3x1fJLlEPff447L5lL/GqCd4UbQyyPlciwRg Is6g== MIME-Version: 1.0 X-Received: by 10.42.133.133 with SMTP id h5mr1001512ict.45.1361550214434; Fri, 22 Feb 2013 08:23:34 -0800 (PST) Received: by 10.42.41.5 with HTTP; Fri, 22 Feb 2013 08:23:34 -0800 (PST) Date: Fri, 22 Feb 2013 09:23:34 -0700 Message-ID: From: jacek burghardt To: xen-users Subject: [Xen-users] failed to add gnttab to physmap X-BeenThere: xen-users@lists.xen.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="===============7605358509559342253==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============7605358509559342253== Content-Type: multipart/alternative; boundary=90e6ba5bc09de00e7d04d6529ceb --90e6ba5bc09de00e7d04d6529ceb Content-Type: text/plain; charset=ISO-8859-1 I have two dell servers running arch linux and xen 4.3 One of them had after installing lates xen 4.3 had been showing this error message" failed to add gnttab to physmap " I reverted back to git pull from 02/17/13 and virtual machines start fine. Can sommone point me in righ direction what could be causing the error message --90e6ba5bc09de00e7d04d6529ceb Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable I have two dell servers running arch linux and xen 4.3 One of them had afte= r installing lates xen 4.3 had been=A0showing=A0this error message" fa= iled to add gnttab to physmap " I reverted back to git pull from 02/17= /13 and virtual machines start fine. Can sommone point me in righ direction= what=A0could=A0be causing the error message=A0 --90e6ba5bc09de00e7d04d6529ceb-- --===============7605358509559342253== 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 --===============7605358509559342253==-- From xen-users-bounces@lists.xen.org Fri Feb 22 16:41:51 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 22 Feb 2013 16:41: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 1U8vfu-0001D2-GA; Fri, 22 Feb 2013 16:40:42 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U8vft-0001Cp-1V for xen-users@lists.xen.org; Fri, 22 Feb 2013 16:40:41 +0000 Received: from [85.158.139.211:19657] by server-2.bemta-5.messagelabs.com id 61/A0-16911-78F97215; Fri, 22 Feb 2013 16:40:39 +0000 X-Env-Sender: roger.pau@citrix.com X-Msg-Ref: server-8.tower-206.messagelabs.com!1361551238!18802365!1 X-Originating-IP: [46.33.159.39] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNDYuMzMuMTU5LjM5ID0+IDIzNzIy\n X-StarScan-Received: X-StarScan-Version: 6.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 30316 invoked from network); 22 Feb 2013 16:40:38 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (46.33.159.39) by server-8.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 22 Feb 2013 16:40:38 -0000 X-IronPort-AV: E=Sophos;i="4.84,717,1355097600"; d="scan'208";a="1794463" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 22 Feb 2013 16:40:26 +0000 Received: from Roger-2.local (10.30.249.242) by LONPMAILMX01.citrite.net (10.30.203.162) with Microsoft SMTP Server id 8.3.297.1; Fri, 22 Feb 2013 16:40:24 +0000 Message-ID: <51279FA1.2090809@citrix.com> Date: Fri, 22 Feb 2013 17:41:05 +0100 From: =?ISO-8859-1?Q?Roger_Pau_Monn=E9?= User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130216 Thunderbird/17.0.3 MIME-Version: 1.0 To: tech mailinglists References: In-Reply-To: Cc: xen-users , "freebsd-xen@lists.freebsd.org" Subject: Re: [Xen-users] Trouble booting FreeBSD i386 PV 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: 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 21/02/13 10:18, tech mailinglists wrote: > Hello all, > > I have created a FreeBSD PV DomU image formatted with ZFS. I compiled > FreeBSD with KERNCONF=XEN for the kernel and the normal world and > distribution target. Then I transfered it to a Debian Dom0 with Xen 4.2.1. > > I tried to boot the image befor I migrate it to LVM and I now get teh > following output: > > Parsing config from freebsd-test.cfg > libxl: error: libxl_dm.c:1212:device_model_spawn_outcome: domain 12 > device model: spawn failed (rc=-3) > libxl: error: libxl_qmp.c:641:libxl__qmp_initialize: Connection error: > No such file or directory > Daemon running with PID 3451 > WARNING: loader(8) metadata is missing! > GDB: no debug ports present > KDB: debugger backends: ddb > KDB: current backend: ddb > APIC: Using the MPTable enumerator. > SMP: Added CPU 0 (BSP) > Copyright (c) 1992-2012 The FreeBSD Project. > Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 > The Regents of the University of California. All rights reserved. > FreeBSD is a registered trademark of The FreeBSD Foundation. > FreeBSD 9.1-RELEASE #0: Wed Feb 20 14:16:03 CET 2013 > root@build:/usr/obj/usr/src/sys/XEN i386 > WARNING: WITNESS option enabled, expect reduced performance. > Xen reported: 3341.754 MHz processor. > Timecounter "ixen" frequency 1953125 Hz quality 0 > CPU: Intel(R) Core(TM) i7 CPU 975 @ 3.33GHz (3341.75-MHz > 686-class CPU) > Origin = "GenuineIntel" Id = 0x106a5 Family = 6 Model = 1a > Stepping = 5 > > Features=0xbfe3fbff > > Features2=0x98e3bd > AMD Features=0x28100000 > AMD Features2=0x1 > > Data TLB: 4 KB pages, 4-way set associative, 64 entries > 1st-level data cache: 32 KB, 8-way set associative, 64 byte line size > L2 cache: 256 kbytes, 8-way associative, 64 bytes/line > real memory = 2147483648 (2048 MB) > Physical memory chunk(s): > 0x0000000000a58000 - 0x000000007d995fff, 2096357376 bytes (511806 pages) > avail memory = 2092105728 (1995 MB) > INTR: Adding local APIC 0 as a target > ULE: setup cpu 0 > [XEN] IPI cpu=0 irq=128 vector=RESCHEDULE_VECTOR (0) > [XEN] IPI cpu=0 irq=129 vector=CALL_FUNCTION_VECTOR (1) > Event-channel device installed. > io: > random: > mem: > Pentium Pro MTRR support enabled > null: > nfslock: pseudo-device > [XEN] xen_rtc_probe: probing Hypervisor RTC clock > rtc0: on motherboard > [XEN] xen_rtc_attach: attaching Hypervisor RTC clock > rtc0: registered as a time-of-day clock (resolution 1000000us, > adjustment 0.500000000s) > xenstore0: on motherboard > Grant table initialized > xc0: on motherboard > Device configuration finished. > procfs registered > Event timer "ixen" quality 600 > Timecounters tick every 10.000 msec > lo0: bpf attached > xenbusb_front0: on xenstore0 > xenbusb_add_device: Device device/suspend/event-channel ignored. State 6 > xenbusb_back0: on xenstore0 > xctrl0: on xenstore0 > [XEN] hypervisor wallclock nudged; nudging TOD. > run_interrupt_driven_hooks: still waiting after 60 seconds for > xenbus_free_evtchn > run_interrupt_driven_hooks: still waiting after 120 seconds for > xenbus_free_evtchn > run_interrupt_driven_hooks: still waiting after 180 seconds for > xenbus_free_evtchn > run_interrupt_driven_hooks: still waiting after 240 seconds for > xenbus_free_evtchn > run_interrupt_driven_hooks: still waiting after 300 seconds for > xenbus_free_evtchn > panic: run_interrupt_driven_config_hooks: waited too long > cpuid = 0 > KDB: enter: panic > [ thread pid 0 tid 100000 ] > Stopped at kdb_enter+0x3a: movl $0,kdb_why > db> Hello, I can tell you PVHVM (XENHVM) works fine with Xen 4.2.1 and -unstable (both 9.1 and HEAD), but I'm afraid I haven't got time to test Xen PV (i386) yet. Can you check if this is a regression in the FreeBSD kernel or Xen itself? Regards, Roger. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Fri Feb 22 16:41:51 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 22 Feb 2013 16:41: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 1U8vfu-0001D2-GA; Fri, 22 Feb 2013 16:40:42 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U8vft-0001Cp-1V for xen-users@lists.xen.org; Fri, 22 Feb 2013 16:40:41 +0000 Received: from [85.158.139.211:19657] by server-2.bemta-5.messagelabs.com id 61/A0-16911-78F97215; Fri, 22 Feb 2013 16:40:39 +0000 X-Env-Sender: roger.pau@citrix.com X-Msg-Ref: server-8.tower-206.messagelabs.com!1361551238!18802365!1 X-Originating-IP: [46.33.159.39] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNDYuMzMuMTU5LjM5ID0+IDIzNzIy\n X-StarScan-Received: X-StarScan-Version: 6.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 30316 invoked from network); 22 Feb 2013 16:40:38 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (46.33.159.39) by server-8.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 22 Feb 2013 16:40:38 -0000 X-IronPort-AV: E=Sophos;i="4.84,717,1355097600"; d="scan'208";a="1794463" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 22 Feb 2013 16:40:26 +0000 Received: from Roger-2.local (10.30.249.242) by LONPMAILMX01.citrite.net (10.30.203.162) with Microsoft SMTP Server id 8.3.297.1; Fri, 22 Feb 2013 16:40:24 +0000 Message-ID: <51279FA1.2090809@citrix.com> Date: Fri, 22 Feb 2013 17:41:05 +0100 From: =?ISO-8859-1?Q?Roger_Pau_Monn=E9?= User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130216 Thunderbird/17.0.3 MIME-Version: 1.0 To: tech mailinglists References: In-Reply-To: Cc: xen-users , "freebsd-xen@lists.freebsd.org" Subject: Re: [Xen-users] Trouble booting FreeBSD i386 PV 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: 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 21/02/13 10:18, tech mailinglists wrote: > Hello all, > > I have created a FreeBSD PV DomU image formatted with ZFS. I compiled > FreeBSD with KERNCONF=XEN for the kernel and the normal world and > distribution target. Then I transfered it to a Debian Dom0 with Xen 4.2.1. > > I tried to boot the image befor I migrate it to LVM and I now get teh > following output: > > Parsing config from freebsd-test.cfg > libxl: error: libxl_dm.c:1212:device_model_spawn_outcome: domain 12 > device model: spawn failed (rc=-3) > libxl: error: libxl_qmp.c:641:libxl__qmp_initialize: Connection error: > No such file or directory > Daemon running with PID 3451 > WARNING: loader(8) metadata is missing! > GDB: no debug ports present > KDB: debugger backends: ddb > KDB: current backend: ddb > APIC: Using the MPTable enumerator. > SMP: Added CPU 0 (BSP) > Copyright (c) 1992-2012 The FreeBSD Project. > Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 > The Regents of the University of California. All rights reserved. > FreeBSD is a registered trademark of The FreeBSD Foundation. > FreeBSD 9.1-RELEASE #0: Wed Feb 20 14:16:03 CET 2013 > root@build:/usr/obj/usr/src/sys/XEN i386 > WARNING: WITNESS option enabled, expect reduced performance. > Xen reported: 3341.754 MHz processor. > Timecounter "ixen" frequency 1953125 Hz quality 0 > CPU: Intel(R) Core(TM) i7 CPU 975 @ 3.33GHz (3341.75-MHz > 686-class CPU) > Origin = "GenuineIntel" Id = 0x106a5 Family = 6 Model = 1a > Stepping = 5 > > Features=0xbfe3fbff > > Features2=0x98e3bd > AMD Features=0x28100000 > AMD Features2=0x1 > > Data TLB: 4 KB pages, 4-way set associative, 64 entries > 1st-level data cache: 32 KB, 8-way set associative, 64 byte line size > L2 cache: 256 kbytes, 8-way associative, 64 bytes/line > real memory = 2147483648 (2048 MB) > Physical memory chunk(s): > 0x0000000000a58000 - 0x000000007d995fff, 2096357376 bytes (511806 pages) > avail memory = 2092105728 (1995 MB) > INTR: Adding local APIC 0 as a target > ULE: setup cpu 0 > [XEN] IPI cpu=0 irq=128 vector=RESCHEDULE_VECTOR (0) > [XEN] IPI cpu=0 irq=129 vector=CALL_FUNCTION_VECTOR (1) > Event-channel device installed. > io: > random: > mem: > Pentium Pro MTRR support enabled > null: > nfslock: pseudo-device > [XEN] xen_rtc_probe: probing Hypervisor RTC clock > rtc0: on motherboard > [XEN] xen_rtc_attach: attaching Hypervisor RTC clock > rtc0: registered as a time-of-day clock (resolution 1000000us, > adjustment 0.500000000s) > xenstore0: on motherboard > Grant table initialized > xc0: on motherboard > Device configuration finished. > procfs registered > Event timer "ixen" quality 600 > Timecounters tick every 10.000 msec > lo0: bpf attached > xenbusb_front0: on xenstore0 > xenbusb_add_device: Device device/suspend/event-channel ignored. State 6 > xenbusb_back0: on xenstore0 > xctrl0: on xenstore0 > [XEN] hypervisor wallclock nudged; nudging TOD. > run_interrupt_driven_hooks: still waiting after 60 seconds for > xenbus_free_evtchn > run_interrupt_driven_hooks: still waiting after 120 seconds for > xenbus_free_evtchn > run_interrupt_driven_hooks: still waiting after 180 seconds for > xenbus_free_evtchn > run_interrupt_driven_hooks: still waiting after 240 seconds for > xenbus_free_evtchn > run_interrupt_driven_hooks: still waiting after 300 seconds for > xenbus_free_evtchn > panic: run_interrupt_driven_config_hooks: waited too long > cpuid = 0 > KDB: enter: panic > [ thread pid 0 tid 100000 ] > Stopped at kdb_enter+0x3a: movl $0,kdb_why > db> Hello, I can tell you PVHVM (XENHVM) works fine with Xen 4.2.1 and -unstable (both 9.1 and HEAD), but I'm afraid I haven't got time to test Xen PV (i386) yet. Can you check if this is a regression in the FreeBSD kernel or Xen itself? Regards, Roger. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Fri Feb 22 18:32:09 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 22 Feb 2013 18:32: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 1U8xOe-000317-UN; Fri, 22 Feb 2013 18:31:00 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U8xOc-00030I-Ih for xen-users@lists.xen.org; Fri, 22 Feb 2013 18:30:59 +0000 Received: from [85.158.139.83:49697] by server-11.bemta-5.messagelabs.com id C3/69-19159-169B7215; Fri, 22 Feb 2013 18:30:57 +0000 X-Env-Sender: mailinglists.tech@gmail.com X-Msg-Ref: server-4.tower-182.messagelabs.com!1361557852!25797540!1 X-Originating-IP: [209.85.216.175] 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.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 8609 invoked from network); 22 Feb 2013 18:30:53 -0000 Received: from mail-qc0-f175.google.com (HELO mail-qc0-f175.google.com) (209.85.216.175) by server-4.tower-182.messagelabs.com with RC4-SHA encrypted SMTP; 22 Feb 2013 18:30:53 -0000 Received: by mail-qc0-f175.google.com with SMTP id j3so412515qcs.34 for ; Fri, 22 Feb 2013 10:30:52 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=bnWFkB453+CDMZyr4SPX4jIkV8i7xFFBD6ZUSw8HfIY=; b=QYRT6XrziraP7tHE50wG5/mQsNSOCXYvfjC3BZl5OmQsY0NSHytQJLtJ2VDc8PFEI7 /nAXMs5S+r9AUBEvYNHQM+h1/9jNAmrtPISswwTbDjvtukHc4DaplWhsTklgwaIG76ec C6qZKbKf2y7Usxfr7QNsWL+hqvv/bTIa3pXnNWjKbfa/z+m/qRG4xMVgpdn1sLpz6T72 GvIyOF16Vzejf01Fz4dBBKIpaqjss9C8DF2uJjTiFTceBK1TGZ6dKbXkU6eIy/cOKbx6 MnBRXOS0WFtUgJe7Rvue1oydId8s1NIVIjfHbwW8XttX9vHe3dkbDKOpSUERbP4Xc8zb oqhQ== MIME-Version: 1.0 X-Received: by 10.224.213.71 with SMTP id gv7mr1622912qab.72.1361557852348; Fri, 22 Feb 2013 10:30:52 -0800 (PST) Received: by 10.49.110.70 with HTTP; Fri, 22 Feb 2013 10:30:52 -0800 (PST) In-Reply-To: <51279FA1.2090809@citrix.com> References: <51279FA1.2090809@citrix.com> Date: Fri, 22 Feb 2013 19:30:52 +0100 Message-ID: From: tech mailinglists To: =?ISO-8859-1?Q?Roger_Pau_Monn=E9?= Cc: xen-users , "freebsd-xen@lists.freebsd.org" Subject: Re: [Xen-users] Trouble booting FreeBSD i386 PV 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="===============5294607674502398409==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============5294607674502398409== Content-Type: multipart/alternative; boundary=20cf300fb13f2189ab04d65464b3 --20cf300fb13f2189ab04d65464b3 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Hello Roger, I tried a further thing in the kernel configuration. I remove the option KBD_INSTALL_CDEV and now I am no longer getting dropped to a minimal console. The boot now looks like this: Parsing config from /root/xen/freebsd-test.cfg libxl: error: libxl_dm.c:1212:device_model_spawn_outcome: domain 20 device model: spawn failed (rc=3D-3) libxl: error: libxl_qmp.c:641:libxl__qmp_initialize: Connection error: No such file or directory Daemon running with PID 4383 WARNING: loader(8) metadata is missing! GDB: no debug ports present KDB: debugger backends: ddb KDB: current backend: ddb APIC: Using the MPTable enumerator. SMP: Added CPU 0 (BSP) Copyright (c) 1992-2012 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD is a registered trademark of The FreeBSD Foundation. FreeBSD 9.1-RELEASE #1 r247145M: Fri Feb 22 18:26:55 CET 2013 root@build:/usr/obj/usr/src/sys/XEN i386 Xen reported: 3341.754 MHz processor. Timecounter "ixen" frequency 1953125 Hz quality 0 CPU: Intel(R) Core(TM) i7 CPU 975 @ 3.33GHz (3341.75-MHz 686-class CPU) Origin =3D "GenuineIntel" Id =3D 0x106a5 Family =3D 6 Model =3D 1a St= epping =3D 5 Features=3D0xbfe3fbff Features2=3D0x98e3bd AMD Features=3D0x28100000 AMD Features2=3D0x1 Data TLB: 4 KB pages, 4-way set associative, 64 entries 1st-level data cache: 32 KB, 8-way set associative, 64 byte line size L2 cache: 256 kbytes, 8-way associative, 64 bytes/line real memory =3D 536870912 (512 MB) Physical memory chunk(s): 0x0000000000670000 - 0x000000001f628fff, 519802880 bytes (126905 pages) avail memory =3D 516833280 (492 MB) INTR: Adding local APIC 0 as a target ULE: setup cpu 0 [XEN] IPI cpu=3D0 irq=3D128 vector=3DRESCHEDULE_VECTOR (0) [XEN] IPI cpu=3D0 irq=3D129 vector=3DCALL_FUNCTION_VECTOR (1) Event-channel device installed. random: io: mem: Pentium Pro MTRR support enabled null: nfslock: pseudo-device [XEN] xen_rtc_probe: probing Hypervisor RTC clock rtc0: on motherboard [XEN] xen_rtc_attach: attaching Hypervisor RTC clock rtc0: registered as a time-of-day clock (resolution 1000000us, adjustment 0.500000000s) xenstore0: on motherboard Grant table initialized xc0: on motherboard Device configuration finished. procfs registered Event timer "ixen" quality 600 Timecounters tick every 10.000 msec lo0: bpf attached xenbusb_front0: on xenstore0 xenbusb_add_device: Device device/suspend/event-channel ignored. State 6 xn0: at device/vif/0 on xenbusb_front0 xn0: bpf attached xn0: Ethernet address: 00:16:3e:44:b1:b9 xenbusb_back0: on xenstore0 xctrl0: on xenstore0 xn0: backend features: feature-sg feature-gso-tcp4 [XEN] hypervisor wallclock nudged; nudging TOD. run_interrupt_driven_hooks: still waiting after 60 seconds for xenbus_free_evtchn [XEN] hypervisor wallclock nudged; nudging TOD. run_interrupt_driven_hooks: still waiting after 120 seconds for xenbus_free_evtchn run_interrupt_driven_hooks: still waiting after 180 seconds for xenbus_free_evtchn run_interrupt_driven_hooks: still waiting after 240 seconds for xenbus_free_evtchn run_interrupt_driven_hooks: still waiting after 300 seconds for xenbus_free_evtchn [XEN] hypervisor wallclock nudged; nudging TOD. [XEN] hypervisor wallclock nudged; nudging TOD. [XEN] hypervisor wallclock nudged; nudging TOD. I will test HVM and PVHVM but in the past I had no problems with this. It would be greate to have pure PV mode. The only thing which confuses me is the libxl related error on the domain creation: Parsing config from /root/xen/freebsd-test.cfg libxl: error: libxl_dm.c:1212:device_model_spawn_outcome: domain 20 device model: spawn failed (rc=3D-3) libxl: error: libxl_qmp.c:641:libxl__qmp_initialize: Connection error: No such file or directory I know that in a few cases PV guests have QEmu process but I can not say while this failes. Eventually there is something not compiled in, into Xen or the toolstack? I saw that you have made a talk on FOSDEM about BSD and PVH. I downloaded the slide PDF but I am not able to open the document. It says that the document is corrupted. Am I doing a mistake? Or is there a problem with the document on the FOSDEM page. Best Regards 2013/2/22 Roger Pau Monn=E9 > On 21/02/13 10:18, tech mailinglists wrote: > > Hello all, > > > > I have created a FreeBSD PV DomU image formatted with ZFS. I compiled > > FreeBSD with KERNCONF=3DXEN for the kernel and the normal world and > > distribution target. Then I transfered it to a Debian Dom0 with Xen > 4.2.1. > > > > I tried to boot the image befor I migrate it to LVM and I now get teh > > following output: > > > > Parsing config from freebsd-test.cfg > > libxl: error: libxl_dm.c:1212:device_model_spawn_outcome: domain 12 > > device model: spawn failed (rc=3D-3) > > libxl: error: libxl_qmp.c:641:libxl__qmp_initialize: Connection error: > > No such file or directory > > Daemon running with PID 3451 > > WARNING: loader(8) metadata is missing! > > GDB: no debug ports present > > KDB: debugger backends: ddb > > KDB: current backend: ddb > > APIC: Using the MPTable enumerator. > > SMP: Added CPU 0 (BSP) > > Copyright (c) 1992-2012 The FreeBSD Project. > > Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 199= 4 > > The Regents of the University of California. All rights reserve= d. > > FreeBSD is a registered trademark of The FreeBSD Foundation. > > FreeBSD 9.1-RELEASE #0: Wed Feb 20 14:16:03 CET 2013 > > root@build:/usr/obj/usr/src/sys/XEN i386 > > WARNING: WITNESS option enabled, expect reduced performance. > > Xen reported: 3341.754 MHz processor. > > Timecounter "ixen" frequency 1953125 Hz quality 0 > > CPU: Intel(R) Core(TM) i7 CPU 975 @ 3.33GHz (3341.75-MHz > > 686-class CPU) > > Origin =3D "GenuineIntel" Id =3D 0x106a5 Family =3D 6 Model =3D 1a > > Stepping =3D 5 > > > > > Features=3D0xbfe3fbff > > > > > Features2=3D0x98e3bd > > AMD Features=3D0x28100000 > > AMD Features2=3D0x1 > > > > Data TLB: 4 KB pages, 4-way set associative, 64 entries > > 1st-level data cache: 32 KB, 8-way set associative, 64 byte line size > > L2 cache: 256 kbytes, 8-way associative, 64 bytes/line > > real memory =3D 2147483648 (2048 MB) > > Physical memory chunk(s): > > 0x0000000000a58000 - 0x000000007d995fff, 2096357376 bytes (511806 pages= ) > > avail memory =3D 2092105728 (1995 MB) > > INTR: Adding local APIC 0 as a target > > ULE: setup cpu 0 > > [XEN] IPI cpu=3D0 irq=3D128 vector=3DRESCHEDULE_VECTOR (0) > > [XEN] IPI cpu=3D0 irq=3D129 vector=3DCALL_FUNCTION_VECTOR (1) > > Event-channel device installed. > > io: > > random: > > mem: > > Pentium Pro MTRR support enabled > > null: > > nfslock: pseudo-device > > [XEN] xen_rtc_probe: probing Hypervisor RTC clock > > rtc0: on motherboard > > [XEN] xen_rtc_attach: attaching Hypervisor RTC clock > > rtc0: registered as a time-of-day clock (resolution 1000000us, > > adjustment 0.500000000s) > > xenstore0: on motherboard > > Grant table initialized > > xc0: on motherboard > > Device configuration finished. > > procfs registered > > Event timer "ixen" quality 600 > > Timecounters tick every 10.000 msec > > lo0: bpf attached > > xenbusb_front0: on xenstore0 > > xenbusb_add_device: Device device/suspend/event-channel ignored. State = 6 > > xenbusb_back0: on xenstore0 > > xctrl0: on xenstore0 > > [XEN] hypervisor wallclock nudged; nudging TOD. > > run_interrupt_driven_hooks: still waiting after 60 seconds for > > xenbus_free_evtchn > > run_interrupt_driven_hooks: still waiting after 120 seconds for > > xenbus_free_evtchn > > run_interrupt_driven_hooks: still waiting after 180 seconds for > > xenbus_free_evtchn > > run_interrupt_driven_hooks: still waiting after 240 seconds for > > xenbus_free_evtchn > > run_interrupt_driven_hooks: still waiting after 300 seconds for > > xenbus_free_evtchn > > panic: run_interrupt_driven_config_hooks: waited too long > > cpuid =3D 0 > > KDB: enter: panic > > [ thread pid 0 tid 100000 ] > > Stopped at kdb_enter+0x3a: movl $0,kdb_why > > db> > > Hello, > > I can tell you PVHVM (XENHVM) works fine with Xen 4.2.1 and -unstable > (both 9.1 and HEAD), but I'm afraid I haven't got time to test Xen PV > (i386) yet. > > Can you check if this is a regression in the FreeBSD kernel or Xen itself= ? > > Regards, Roger. > --20cf300fb13f2189ab04d65464b3 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Hello Roger,


I tried a further = thing in the kernel configuration. I remove the option KBD_INSTALL_CDEV and= now I am no longer getting dropped to a minimal console. The boot now look= s like this:

Parsing config from /root/xen/freebsd-test.cfg
libxl: error: libxl_d= m.c:1212:device_model_spawn_outcome: domain 20 device model: spawn failed (= rc=3D-3)
libxl: error: libxl_qmp.c:641:libxl__qmp_initialize: Connection= error: No such file or directory
Daemon running with PID 4383
WARNING: loader(8) metadata is missing!
= GDB: no debug ports present
KDB: debugger backends: ddb
KDB: current = backend: ddb
APIC: Using the MPTable enumerator.
SMP: Added CPU 0 (BS= P)
Copyright (c) 1992-2012 The FreeBSD Project.
Copyright (c) 1979, 1980, 1= 983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
=A0=A0=A0=A0=A0=A0=A0 The = Regents of the University of California. All rights reserved.
FreeBSD is= a registered trademark of The FreeBSD Foundation.
FreeBSD 9.1-RELEASE #1 r247145M: Fri Feb 22 18:26:55 CET 2013
=A0=A0=A0 = root@build:/usr/obj/usr/src/sys/XEN i386
Xen reported: 3341.754 MHz proc= essor.
Timecounter "ixen" frequency 1953125 Hz quality 0
CP= U: Intel(R) Core(TM) i7 CPU=A0=A0=A0=A0=A0=A0=A0=A0 975=A0 @ 3.33GHz (3341.= 75-MHz 686-class CPU)
=A0 Origin =3D "GenuineIntel"=A0 Id =3D 0x106a5=A0 Family =3D 6= =A0 Model =3D 1a=A0 Stepping =3D 5
=A0 Features=3D0xbfe3fbff<FPU,VME,= DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,DTS,ACPI,MM= X,FXSR,SSE,SSE2,SS,HTT,TM,PBE>
=A0 Features2=3D0x98e3bd<SSE3,DTES64,MON,DS_CPL,VMX,EST,TM2,SSSE3,CX16,x= TPR,PDCM,SSE4.1,SSE4.2,POPCNT>
=A0 AMD Features=3D0x28100000<NX,RD= TSCP,LM>
=A0 AMD Features2=3D0x1<LAHF>

Data TLB: 4 KB pa= ges, 4-way set associative, 64 entries
1st-level data cache: 32 KB, 8-way set associative, 64 byte line size
L2= cache: 256 kbytes, 8-way associative, 64 bytes/line
real memory=A0 =3D = 536870912 (512 MB)
Physical memory chunk(s):
0x0000000000670000 - 0x0= 00000001f628fff, 519802880 bytes (126905 pages)
avail memory =3D 516833280 (492 MB)
INTR: Adding local APIC 0 as a targe= t
ULE: setup cpu 0
[XEN] IPI cpu=3D0 irq=3D128 vector=3DRESCHEDULE_VE= CTOR (0)
[XEN] IPI cpu=3D0 irq=3D129 vector=3DCALL_FUNCTION_VECTOR (1)Event-channel device installed.
random: <entropy source, Software, Yarrow>
io: <I/O>
mem:= <memory>
Pentium Pro MTRR support enabled
null: <null devic= e, zero device>
nfslock: pseudo-device
[XEN] xen_rtc_probe: probin= g Hypervisor RTC clock
rtc0: <Xen Hypervisor Clock> on motherboard
[XEN] xen_rtc_attach: = attaching Hypervisor RTC clock
rtc0: registered as a time-of-day clock (= resolution 1000000us, adjustment 0.500000000s)
xenstore0: <XenStore&g= t; on motherboard
Grant table initialized
xc0: <Xen Console> on motherboard
Devic= e configuration finished.
procfs registered
Event timer "ixen&qu= ot; quality 600
Timecounters tick every 10.000 msec
lo0: bpf attached=
xenbusb_front0: <Xen Frontend Devices> on xenstore0
xenbusb_add_de= vice: Device device/suspend/event-channel ignored. State 6
xn0: <Virt= ual Network Interface> at device/vif/0 on xenbusb_front0
xn0: bpf att= ached
xn0: Ethernet address: 00:16:3e:44:b1:b9
xenbusb_back0: <Xen Backend = Devices> on xenstore0
xctrl0: <Xen Control Device> on xenstore0=
xn0: backend features: feature-sg feature-gso-tcp4
[XEN] hypervisor = wallclock nudged; nudging TOD.
run_interrupt_driven_hooks: still waiting after 60 seconds for xenbus_free_= evtchn
[XEN] hypervisor wallclock nudged; nudging TOD.
run_interrupt_= driven_hooks: still waiting after 120 seconds for xenbus_free_evtchn
run_interrupt_driven_hooks: still waiting after 180 seconds for xenbus_free= _evtchn
run_interrupt_driven_hooks: still waiting after 240 seconds for = xenbus_free_evtchn
run_interrupt_driven_hooks: still waiting after 300 s= econds for xenbus_free_evtchn
[XEN] hypervisor wallclock nudged; nudging TOD.
[XEN] hypervisor wallclo= ck nudged; nudging TOD.
[XEN] hypervisor wallclock nudged; nudging TOD.<= br>
I will test HVM and PVHVM but in the past I had no proble= ms with this. It would be greate to have pure PV mode. The only thing which= confuses me is the libxl related error on the domain creation:

Parsing config from /root/xen/freebsd-test.cfg
libxl: err= or: libxl_dm.c:1212:device_model_spawn_outcome: domain 20 device model: spa= wn failed (rc=3D-3)
libxl: error: libxl_qmp.c:641:libxl__qmp_initialize:= Connection error: No such file or directory

I know that in a few cases PV guests have QEmu process but I= can not say while this failes. Eventually there is something not compiled = in, into Xen or the toolstack?

I saw that you have made a= talk on FOSDEM about BSD and PVH. I downloaded the slide PDF but I am not = able to open the document. It says that the document is corrupted. Am I doi= ng a mistake? Or is there a problem with the document on the FOSDEM page.
Best Regards

<= br>
2013/2/22 Roger Pau Monn=E9 <roger.pau@ci= trix.com>
On 2= 1/02/13 10:18, tech mailinglists wrote:
> Hello all,
>
> I have created a FreeBSD PV DomU image formatted with ZFS. I compiled<= br> > FreeBSD with KERNCONF=3DXEN for the kernel and the normal world and > distribution target. Then I transfered it to a Debian Dom0 with Xen 4.= 2.1.
>
> I tried to boot the image befor I migrate it to LVM and I now get teh<= br> > following output:
>
> Parsing config from freebsd-test.cfg
> libxl: error: libxl_dm.c:1212:device_model_spawn_outcome: domain 12 > device model: spawn failed (rc=3D-3)
> libxl: error: libxl_qmp.c:641:libxl__qmp_initialize: Connection error:=
> No such file or directory
> Daemon running with PID 3451
> WARNING: loader(8) metadata is missing!
> GDB: no debug ports present
> KDB: debugger backends: ddb
> KDB: current backend: ddb
> APIC: Using the MPTable enumerator.
> SMP: Added CPU 0 (BSP)
> Copyright (c) 1992-2012 The FreeBSD Project.
> Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 19= 94
> =A0 =A0 =A0 =A0 The Regents of the University of California. All right= s reserved.
> FreeBSD is a registered trademark of The FreeBSD Foundation.
> FreeBSD 9.1-RELEASE #0: Wed Feb 20 14:16:03 CET 2013
> =A0 =A0 root@build:/usr/obj/usr/src/sys/XEN i386
> WARNING: WITNESS option enabled, expect reduced performance.
> Xen reported: 3341.754 MHz processor.
> Timecounter "ixen" frequency 1953125 Hz quality 0
> CPU: Intel(R) Core(TM) i7 CPU =A0 =A0 =A0 =A0 975 =A0@ 3.33GHz (3341.7= 5-MHz
> 686-class CPU)
> =A0 Origin =3D "GenuineIntel" =A0Id =3D 0x106a5 =A0Family = =3D 6 =A0Model =3D 1a
> Stepping =3D 5
>
> Features=3D0xbfe3fbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,M= TRR,PGE,MCA,CMOV,PAT,PSE36,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE>
>
> Features2=3D0x98e3bd<SSE3,DTES64,MON,DS_CPL,VMX,EST,TM2,SSSE3,CX16,= xTPR,PDCM,SSE4.1,SSE4.2,POPCNT>
> =A0 AMD Features=3D0x28100000<NX,RDTSCP,LM>
> =A0 AMD Features2=3D0x1<LAHF>
>
> Data TLB: 4 KB pages, 4-way set associative, 64 entries
> 1st-level data cache: 32 KB, 8-way set associative, 64 byte line size<= br> > L2 cache: 256 kbytes, 8-way associative, 64 bytes/line
> real memory =A0=3D 2147483648 (2048 MB)
> Physical memory chunk(s):
> 0x0000000000a58000 - 0x000000007d995fff, 2096357376 bytes (511806 page= s)
> avail memory =3D 2092105728 (1995 MB)
> INTR: Adding local APIC 0 as a target
> ULE: setup cpu 0
> [XEN] IPI cpu=3D0 irq=3D128 vector=3DRESCHEDULE_VECTOR (0)
> [XEN] IPI cpu=3D0 irq=3D129 vector=3DCALL_FUNCTION_VECTOR (1)
> Event-channel device installed.
> io: <I/O>
> random: <entropy source, Software, Yarrow>
> mem: <memory>
> Pentium Pro MTRR support enabled
> null: <null device, zero device>
> nfslock: pseudo-device
> [XEN] xen_rtc_probe: probing Hypervisor RTC clock
> rtc0: <Xen Hypervisor Clock> on motherboard
> [XEN] xen_rtc_attach: attaching Hypervisor RTC clock
> rtc0: registered as a time-of-day clock (resolution 1000000us,
> adjustment 0.500000000s)
> xenstore0: <XenStore> on motherboard
> Grant table initialized
> xc0: <Xen Console> on motherboard
> Device configuration finished.
> procfs registered
> Event timer "ixen" quality 600
> Timecounters tick every 10.000 msec
> lo0: bpf attached
> xenbusb_front0: <Xen Frontend Devices> on xenstore0
> xenbusb_add_device: Device device/suspend/event-channel ignored. State= 6
> xenbusb_back0: <Xen Backend Devices> on xenstore0
> xctrl0: <Xen Control Device> on xenstore0
> [XEN] hypervisor wallclock nudged; nudging TOD.
> run_interrupt_driven_hooks: still waiting after 60 seconds for
> xenbus_free_evtchn
> run_interrupt_driven_hooks: still waiting after 120 seconds for
> xenbus_free_evtchn
> run_interrupt_driven_hooks: still waiting after 180 seconds for
> xenbus_free_evtchn
> run_interrupt_driven_hooks: still waiting after 240 seconds for
> xenbus_free_evtchn
> run_interrupt_driven_hooks: still waiting after 300 seconds for
> xenbus_free_evtchn
> panic: run_interrupt_driven_config_hooks: waited too long
> cpuid =3D 0
> KDB: enter: panic
> [ thread pid 0 tid 100000 ]
> Stopped at =A0 =A0 =A0kdb_enter+0x3a: movl =A0 =A0$0,kdb_why
> db>

Hello,

I can tell you PVHVM (XENHVM) works fine with Xen 4.2.1 and -unstable
(both 9.1 and HEAD), but I'm afraid I haven't got time to test Xen = PV
(i386) yet.

Can you check if this is a regression in the FreeBSD kernel or Xen itself?<= br>
Regards, Roger.

--20cf300fb13f2189ab04d65464b3-- --===============5294607674502398409== 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 --===============5294607674502398409==-- From xen-users-bounces@lists.xen.org Fri Feb 22 18:32:09 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 22 Feb 2013 18:32: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 1U8xOe-000317-UN; Fri, 22 Feb 2013 18:31:00 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U8xOc-00030I-Ih for xen-users@lists.xen.org; Fri, 22 Feb 2013 18:30:59 +0000 Received: from [85.158.139.83:49697] by server-11.bemta-5.messagelabs.com id C3/69-19159-169B7215; Fri, 22 Feb 2013 18:30:57 +0000 X-Env-Sender: mailinglists.tech@gmail.com X-Msg-Ref: server-4.tower-182.messagelabs.com!1361557852!25797540!1 X-Originating-IP: [209.85.216.175] 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.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 8609 invoked from network); 22 Feb 2013 18:30:53 -0000 Received: from mail-qc0-f175.google.com (HELO mail-qc0-f175.google.com) (209.85.216.175) by server-4.tower-182.messagelabs.com with RC4-SHA encrypted SMTP; 22 Feb 2013 18:30:53 -0000 Received: by mail-qc0-f175.google.com with SMTP id j3so412515qcs.34 for ; Fri, 22 Feb 2013 10:30:52 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=bnWFkB453+CDMZyr4SPX4jIkV8i7xFFBD6ZUSw8HfIY=; b=QYRT6XrziraP7tHE50wG5/mQsNSOCXYvfjC3BZl5OmQsY0NSHytQJLtJ2VDc8PFEI7 /nAXMs5S+r9AUBEvYNHQM+h1/9jNAmrtPISswwTbDjvtukHc4DaplWhsTklgwaIG76ec C6qZKbKf2y7Usxfr7QNsWL+hqvv/bTIa3pXnNWjKbfa/z+m/qRG4xMVgpdn1sLpz6T72 GvIyOF16Vzejf01Fz4dBBKIpaqjss9C8DF2uJjTiFTceBK1TGZ6dKbXkU6eIy/cOKbx6 MnBRXOS0WFtUgJe7Rvue1oydId8s1NIVIjfHbwW8XttX9vHe3dkbDKOpSUERbP4Xc8zb oqhQ== MIME-Version: 1.0 X-Received: by 10.224.213.71 with SMTP id gv7mr1622912qab.72.1361557852348; Fri, 22 Feb 2013 10:30:52 -0800 (PST) Received: by 10.49.110.70 with HTTP; Fri, 22 Feb 2013 10:30:52 -0800 (PST) In-Reply-To: <51279FA1.2090809@citrix.com> References: <51279FA1.2090809@citrix.com> Date: Fri, 22 Feb 2013 19:30:52 +0100 Message-ID: From: tech mailinglists To: =?ISO-8859-1?Q?Roger_Pau_Monn=E9?= Cc: xen-users , "freebsd-xen@lists.freebsd.org" Subject: Re: [Xen-users] Trouble booting FreeBSD i386 PV 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="===============5294607674502398409==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============5294607674502398409== Content-Type: multipart/alternative; boundary=20cf300fb13f2189ab04d65464b3 --20cf300fb13f2189ab04d65464b3 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Hello Roger, I tried a further thing in the kernel configuration. I remove the option KBD_INSTALL_CDEV and now I am no longer getting dropped to a minimal console. The boot now looks like this: Parsing config from /root/xen/freebsd-test.cfg libxl: error: libxl_dm.c:1212:device_model_spawn_outcome: domain 20 device model: spawn failed (rc=3D-3) libxl: error: libxl_qmp.c:641:libxl__qmp_initialize: Connection error: No such file or directory Daemon running with PID 4383 WARNING: loader(8) metadata is missing! GDB: no debug ports present KDB: debugger backends: ddb KDB: current backend: ddb APIC: Using the MPTable enumerator. SMP: Added CPU 0 (BSP) Copyright (c) 1992-2012 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD is a registered trademark of The FreeBSD Foundation. FreeBSD 9.1-RELEASE #1 r247145M: Fri Feb 22 18:26:55 CET 2013 root@build:/usr/obj/usr/src/sys/XEN i386 Xen reported: 3341.754 MHz processor. Timecounter "ixen" frequency 1953125 Hz quality 0 CPU: Intel(R) Core(TM) i7 CPU 975 @ 3.33GHz (3341.75-MHz 686-class CPU) Origin =3D "GenuineIntel" Id =3D 0x106a5 Family =3D 6 Model =3D 1a St= epping =3D 5 Features=3D0xbfe3fbff Features2=3D0x98e3bd AMD Features=3D0x28100000 AMD Features2=3D0x1 Data TLB: 4 KB pages, 4-way set associative, 64 entries 1st-level data cache: 32 KB, 8-way set associative, 64 byte line size L2 cache: 256 kbytes, 8-way associative, 64 bytes/line real memory =3D 536870912 (512 MB) Physical memory chunk(s): 0x0000000000670000 - 0x000000001f628fff, 519802880 bytes (126905 pages) avail memory =3D 516833280 (492 MB) INTR: Adding local APIC 0 as a target ULE: setup cpu 0 [XEN] IPI cpu=3D0 irq=3D128 vector=3DRESCHEDULE_VECTOR (0) [XEN] IPI cpu=3D0 irq=3D129 vector=3DCALL_FUNCTION_VECTOR (1) Event-channel device installed. random: io: mem: Pentium Pro MTRR support enabled null: nfslock: pseudo-device [XEN] xen_rtc_probe: probing Hypervisor RTC clock rtc0: on motherboard [XEN] xen_rtc_attach: attaching Hypervisor RTC clock rtc0: registered as a time-of-day clock (resolution 1000000us, adjustment 0.500000000s) xenstore0: on motherboard Grant table initialized xc0: on motherboard Device configuration finished. procfs registered Event timer "ixen" quality 600 Timecounters tick every 10.000 msec lo0: bpf attached xenbusb_front0: on xenstore0 xenbusb_add_device: Device device/suspend/event-channel ignored. State 6 xn0: at device/vif/0 on xenbusb_front0 xn0: bpf attached xn0: Ethernet address: 00:16:3e:44:b1:b9 xenbusb_back0: on xenstore0 xctrl0: on xenstore0 xn0: backend features: feature-sg feature-gso-tcp4 [XEN] hypervisor wallclock nudged; nudging TOD. run_interrupt_driven_hooks: still waiting after 60 seconds for xenbus_free_evtchn [XEN] hypervisor wallclock nudged; nudging TOD. run_interrupt_driven_hooks: still waiting after 120 seconds for xenbus_free_evtchn run_interrupt_driven_hooks: still waiting after 180 seconds for xenbus_free_evtchn run_interrupt_driven_hooks: still waiting after 240 seconds for xenbus_free_evtchn run_interrupt_driven_hooks: still waiting after 300 seconds for xenbus_free_evtchn [XEN] hypervisor wallclock nudged; nudging TOD. [XEN] hypervisor wallclock nudged; nudging TOD. [XEN] hypervisor wallclock nudged; nudging TOD. I will test HVM and PVHVM but in the past I had no problems with this. It would be greate to have pure PV mode. The only thing which confuses me is the libxl related error on the domain creation: Parsing config from /root/xen/freebsd-test.cfg libxl: error: libxl_dm.c:1212:device_model_spawn_outcome: domain 20 device model: spawn failed (rc=3D-3) libxl: error: libxl_qmp.c:641:libxl__qmp_initialize: Connection error: No such file or directory I know that in a few cases PV guests have QEmu process but I can not say while this failes. Eventually there is something not compiled in, into Xen or the toolstack? I saw that you have made a talk on FOSDEM about BSD and PVH. I downloaded the slide PDF but I am not able to open the document. It says that the document is corrupted. Am I doing a mistake? Or is there a problem with the document on the FOSDEM page. Best Regards 2013/2/22 Roger Pau Monn=E9 > On 21/02/13 10:18, tech mailinglists wrote: > > Hello all, > > > > I have created a FreeBSD PV DomU image formatted with ZFS. I compiled > > FreeBSD with KERNCONF=3DXEN for the kernel and the normal world and > > distribution target. Then I transfered it to a Debian Dom0 with Xen > 4.2.1. > > > > I tried to boot the image befor I migrate it to LVM and I now get teh > > following output: > > > > Parsing config from freebsd-test.cfg > > libxl: error: libxl_dm.c:1212:device_model_spawn_outcome: domain 12 > > device model: spawn failed (rc=3D-3) > > libxl: error: libxl_qmp.c:641:libxl__qmp_initialize: Connection error: > > No such file or directory > > Daemon running with PID 3451 > > WARNING: loader(8) metadata is missing! > > GDB: no debug ports present > > KDB: debugger backends: ddb > > KDB: current backend: ddb > > APIC: Using the MPTable enumerator. > > SMP: Added CPU 0 (BSP) > > Copyright (c) 1992-2012 The FreeBSD Project. > > Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 199= 4 > > The Regents of the University of California. All rights reserve= d. > > FreeBSD is a registered trademark of The FreeBSD Foundation. > > FreeBSD 9.1-RELEASE #0: Wed Feb 20 14:16:03 CET 2013 > > root@build:/usr/obj/usr/src/sys/XEN i386 > > WARNING: WITNESS option enabled, expect reduced performance. > > Xen reported: 3341.754 MHz processor. > > Timecounter "ixen" frequency 1953125 Hz quality 0 > > CPU: Intel(R) Core(TM) i7 CPU 975 @ 3.33GHz (3341.75-MHz > > 686-class CPU) > > Origin =3D "GenuineIntel" Id =3D 0x106a5 Family =3D 6 Model =3D 1a > > Stepping =3D 5 > > > > > Features=3D0xbfe3fbff > > > > > Features2=3D0x98e3bd > > AMD Features=3D0x28100000 > > AMD Features2=3D0x1 > > > > Data TLB: 4 KB pages, 4-way set associative, 64 entries > > 1st-level data cache: 32 KB, 8-way set associative, 64 byte line size > > L2 cache: 256 kbytes, 8-way associative, 64 bytes/line > > real memory =3D 2147483648 (2048 MB) > > Physical memory chunk(s): > > 0x0000000000a58000 - 0x000000007d995fff, 2096357376 bytes (511806 pages= ) > > avail memory =3D 2092105728 (1995 MB) > > INTR: Adding local APIC 0 as a target > > ULE: setup cpu 0 > > [XEN] IPI cpu=3D0 irq=3D128 vector=3DRESCHEDULE_VECTOR (0) > > [XEN] IPI cpu=3D0 irq=3D129 vector=3DCALL_FUNCTION_VECTOR (1) > > Event-channel device installed. > > io: > > random: > > mem: > > Pentium Pro MTRR support enabled > > null: > > nfslock: pseudo-device > > [XEN] xen_rtc_probe: probing Hypervisor RTC clock > > rtc0: on motherboard > > [XEN] xen_rtc_attach: attaching Hypervisor RTC clock > > rtc0: registered as a time-of-day clock (resolution 1000000us, > > adjustment 0.500000000s) > > xenstore0: on motherboard > > Grant table initialized > > xc0: on motherboard > > Device configuration finished. > > procfs registered > > Event timer "ixen" quality 600 > > Timecounters tick every 10.000 msec > > lo0: bpf attached > > xenbusb_front0: on xenstore0 > > xenbusb_add_device: Device device/suspend/event-channel ignored. State = 6 > > xenbusb_back0: on xenstore0 > > xctrl0: on xenstore0 > > [XEN] hypervisor wallclock nudged; nudging TOD. > > run_interrupt_driven_hooks: still waiting after 60 seconds for > > xenbus_free_evtchn > > run_interrupt_driven_hooks: still waiting after 120 seconds for > > xenbus_free_evtchn > > run_interrupt_driven_hooks: still waiting after 180 seconds for > > xenbus_free_evtchn > > run_interrupt_driven_hooks: still waiting after 240 seconds for > > xenbus_free_evtchn > > run_interrupt_driven_hooks: still waiting after 300 seconds for > > xenbus_free_evtchn > > panic: run_interrupt_driven_config_hooks: waited too long > > cpuid =3D 0 > > KDB: enter: panic > > [ thread pid 0 tid 100000 ] > > Stopped at kdb_enter+0x3a: movl $0,kdb_why > > db> > > Hello, > > I can tell you PVHVM (XENHVM) works fine with Xen 4.2.1 and -unstable > (both 9.1 and HEAD), but I'm afraid I haven't got time to test Xen PV > (i386) yet. > > Can you check if this is a regression in the FreeBSD kernel or Xen itself= ? > > Regards, Roger. > --20cf300fb13f2189ab04d65464b3 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Hello Roger,


I tried a further = thing in the kernel configuration. I remove the option KBD_INSTALL_CDEV and= now I am no longer getting dropped to a minimal console. The boot now look= s like this:

Parsing config from /root/xen/freebsd-test.cfg
libxl: error: libxl_d= m.c:1212:device_model_spawn_outcome: domain 20 device model: spawn failed (= rc=3D-3)
libxl: error: libxl_qmp.c:641:libxl__qmp_initialize: Connection= error: No such file or directory
Daemon running with PID 4383
WARNING: loader(8) metadata is missing!
= GDB: no debug ports present
KDB: debugger backends: ddb
KDB: current = backend: ddb
APIC: Using the MPTable enumerator.
SMP: Added CPU 0 (BS= P)
Copyright (c) 1992-2012 The FreeBSD Project.
Copyright (c) 1979, 1980, 1= 983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
=A0=A0=A0=A0=A0=A0=A0 The = Regents of the University of California. All rights reserved.
FreeBSD is= a registered trademark of The FreeBSD Foundation.
FreeBSD 9.1-RELEASE #1 r247145M: Fri Feb 22 18:26:55 CET 2013
=A0=A0=A0 = root@build:/usr/obj/usr/src/sys/XEN i386
Xen reported: 3341.754 MHz proc= essor.
Timecounter "ixen" frequency 1953125 Hz quality 0
CP= U: Intel(R) Core(TM) i7 CPU=A0=A0=A0=A0=A0=A0=A0=A0 975=A0 @ 3.33GHz (3341.= 75-MHz 686-class CPU)
=A0 Origin =3D "GenuineIntel"=A0 Id =3D 0x106a5=A0 Family =3D 6= =A0 Model =3D 1a=A0 Stepping =3D 5
=A0 Features=3D0xbfe3fbff<FPU,VME,= DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,DTS,ACPI,MM= X,FXSR,SSE,SSE2,SS,HTT,TM,PBE>
=A0 Features2=3D0x98e3bd<SSE3,DTES64,MON,DS_CPL,VMX,EST,TM2,SSSE3,CX16,x= TPR,PDCM,SSE4.1,SSE4.2,POPCNT>
=A0 AMD Features=3D0x28100000<NX,RD= TSCP,LM>
=A0 AMD Features2=3D0x1<LAHF>

Data TLB: 4 KB pa= ges, 4-way set associative, 64 entries
1st-level data cache: 32 KB, 8-way set associative, 64 byte line size
L2= cache: 256 kbytes, 8-way associative, 64 bytes/line
real memory=A0 =3D = 536870912 (512 MB)
Physical memory chunk(s):
0x0000000000670000 - 0x0= 00000001f628fff, 519802880 bytes (126905 pages)
avail memory =3D 516833280 (492 MB)
INTR: Adding local APIC 0 as a targe= t
ULE: setup cpu 0
[XEN] IPI cpu=3D0 irq=3D128 vector=3DRESCHEDULE_VE= CTOR (0)
[XEN] IPI cpu=3D0 irq=3D129 vector=3DCALL_FUNCTION_VECTOR (1)Event-channel device installed.
random: <entropy source, Software, Yarrow>
io: <I/O>
mem:= <memory>
Pentium Pro MTRR support enabled
null: <null devic= e, zero device>
nfslock: pseudo-device
[XEN] xen_rtc_probe: probin= g Hypervisor RTC clock
rtc0: <Xen Hypervisor Clock> on motherboard
[XEN] xen_rtc_attach: = attaching Hypervisor RTC clock
rtc0: registered as a time-of-day clock (= resolution 1000000us, adjustment 0.500000000s)
xenstore0: <XenStore&g= t; on motherboard
Grant table initialized
xc0: <Xen Console> on motherboard
Devic= e configuration finished.
procfs registered
Event timer "ixen&qu= ot; quality 600
Timecounters tick every 10.000 msec
lo0: bpf attached=
xenbusb_front0: <Xen Frontend Devices> on xenstore0
xenbusb_add_de= vice: Device device/suspend/event-channel ignored. State 6
xn0: <Virt= ual Network Interface> at device/vif/0 on xenbusb_front0
xn0: bpf att= ached
xn0: Ethernet address: 00:16:3e:44:b1:b9
xenbusb_back0: <Xen Backend = Devices> on xenstore0
xctrl0: <Xen Control Device> on xenstore0=
xn0: backend features: feature-sg feature-gso-tcp4
[XEN] hypervisor = wallclock nudged; nudging TOD.
run_interrupt_driven_hooks: still waiting after 60 seconds for xenbus_free_= evtchn
[XEN] hypervisor wallclock nudged; nudging TOD.
run_interrupt_= driven_hooks: still waiting after 120 seconds for xenbus_free_evtchn
run_interrupt_driven_hooks: still waiting after 180 seconds for xenbus_free= _evtchn
run_interrupt_driven_hooks: still waiting after 240 seconds for = xenbus_free_evtchn
run_interrupt_driven_hooks: still waiting after 300 s= econds for xenbus_free_evtchn
[XEN] hypervisor wallclock nudged; nudging TOD.
[XEN] hypervisor wallclo= ck nudged; nudging TOD.
[XEN] hypervisor wallclock nudged; nudging TOD.<= br>
I will test HVM and PVHVM but in the past I had no proble= ms with this. It would be greate to have pure PV mode. The only thing which= confuses me is the libxl related error on the domain creation:

Parsing config from /root/xen/freebsd-test.cfg
libxl: err= or: libxl_dm.c:1212:device_model_spawn_outcome: domain 20 device model: spa= wn failed (rc=3D-3)
libxl: error: libxl_qmp.c:641:libxl__qmp_initialize:= Connection error: No such file or directory

I know that in a few cases PV guests have QEmu process but I= can not say while this failes. Eventually there is something not compiled = in, into Xen or the toolstack?

I saw that you have made a= talk on FOSDEM about BSD and PVH. I downloaded the slide PDF but I am not = able to open the document. It says that the document is corrupted. Am I doi= ng a mistake? Or is there a problem with the document on the FOSDEM page.
Best Regards

<= br>
2013/2/22 Roger Pau Monn=E9 <roger.pau@ci= trix.com>
On 2= 1/02/13 10:18, tech mailinglists wrote:
> Hello all,
>
> I have created a FreeBSD PV DomU image formatted with ZFS. I compiled<= br> > FreeBSD with KERNCONF=3DXEN for the kernel and the normal world and > distribution target. Then I transfered it to a Debian Dom0 with Xen 4.= 2.1.
>
> I tried to boot the image befor I migrate it to LVM and I now get teh<= br> > following output:
>
> Parsing config from freebsd-test.cfg
> libxl: error: libxl_dm.c:1212:device_model_spawn_outcome: domain 12 > device model: spawn failed (rc=3D-3)
> libxl: error: libxl_qmp.c:641:libxl__qmp_initialize: Connection error:=
> No such file or directory
> Daemon running with PID 3451
> WARNING: loader(8) metadata is missing!
> GDB: no debug ports present
> KDB: debugger backends: ddb
> KDB: current backend: ddb
> APIC: Using the MPTable enumerator.
> SMP: Added CPU 0 (BSP)
> Copyright (c) 1992-2012 The FreeBSD Project.
> Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 19= 94
> =A0 =A0 =A0 =A0 The Regents of the University of California. All right= s reserved.
> FreeBSD is a registered trademark of The FreeBSD Foundation.
> FreeBSD 9.1-RELEASE #0: Wed Feb 20 14:16:03 CET 2013
> =A0 =A0 root@build:/usr/obj/usr/src/sys/XEN i386
> WARNING: WITNESS option enabled, expect reduced performance.
> Xen reported: 3341.754 MHz processor.
> Timecounter "ixen" frequency 1953125 Hz quality 0
> CPU: Intel(R) Core(TM) i7 CPU =A0 =A0 =A0 =A0 975 =A0@ 3.33GHz (3341.7= 5-MHz
> 686-class CPU)
> =A0 Origin =3D "GenuineIntel" =A0Id =3D 0x106a5 =A0Family = =3D 6 =A0Model =3D 1a
> Stepping =3D 5
>
> Features=3D0xbfe3fbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,M= TRR,PGE,MCA,CMOV,PAT,PSE36,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE>
>
> Features2=3D0x98e3bd<SSE3,DTES64,MON,DS_CPL,VMX,EST,TM2,SSSE3,CX16,= xTPR,PDCM,SSE4.1,SSE4.2,POPCNT>
> =A0 AMD Features=3D0x28100000<NX,RDTSCP,LM>
> =A0 AMD Features2=3D0x1<LAHF>
>
> Data TLB: 4 KB pages, 4-way set associative, 64 entries
> 1st-level data cache: 32 KB, 8-way set associative, 64 byte line size<= br> > L2 cache: 256 kbytes, 8-way associative, 64 bytes/line
> real memory =A0=3D 2147483648 (2048 MB)
> Physical memory chunk(s):
> 0x0000000000a58000 - 0x000000007d995fff, 2096357376 bytes (511806 page= s)
> avail memory =3D 2092105728 (1995 MB)
> INTR: Adding local APIC 0 as a target
> ULE: setup cpu 0
> [XEN] IPI cpu=3D0 irq=3D128 vector=3DRESCHEDULE_VECTOR (0)
> [XEN] IPI cpu=3D0 irq=3D129 vector=3DCALL_FUNCTION_VECTOR (1)
> Event-channel device installed.
> io: <I/O>
> random: <entropy source, Software, Yarrow>
> mem: <memory>
> Pentium Pro MTRR support enabled
> null: <null device, zero device>
> nfslock: pseudo-device
> [XEN] xen_rtc_probe: probing Hypervisor RTC clock
> rtc0: <Xen Hypervisor Clock> on motherboard
> [XEN] xen_rtc_attach: attaching Hypervisor RTC clock
> rtc0: registered as a time-of-day clock (resolution 1000000us,
> adjustment 0.500000000s)
> xenstore0: <XenStore> on motherboard
> Grant table initialized
> xc0: <Xen Console> on motherboard
> Device configuration finished.
> procfs registered
> Event timer "ixen" quality 600
> Timecounters tick every 10.000 msec
> lo0: bpf attached
> xenbusb_front0: <Xen Frontend Devices> on xenstore0
> xenbusb_add_device: Device device/suspend/event-channel ignored. State= 6
> xenbusb_back0: <Xen Backend Devices> on xenstore0
> xctrl0: <Xen Control Device> on xenstore0
> [XEN] hypervisor wallclock nudged; nudging TOD.
> run_interrupt_driven_hooks: still waiting after 60 seconds for
> xenbus_free_evtchn
> run_interrupt_driven_hooks: still waiting after 120 seconds for
> xenbus_free_evtchn
> run_interrupt_driven_hooks: still waiting after 180 seconds for
> xenbus_free_evtchn
> run_interrupt_driven_hooks: still waiting after 240 seconds for
> xenbus_free_evtchn
> run_interrupt_driven_hooks: still waiting after 300 seconds for
> xenbus_free_evtchn
> panic: run_interrupt_driven_config_hooks: waited too long
> cpuid =3D 0
> KDB: enter: panic
> [ thread pid 0 tid 100000 ]
> Stopped at =A0 =A0 =A0kdb_enter+0x3a: movl =A0 =A0$0,kdb_why
> db>

Hello,

I can tell you PVHVM (XENHVM) works fine with Xen 4.2.1 and -unstable
(both 9.1 and HEAD), but I'm afraid I haven't got time to test Xen = PV
(i386) yet.

Can you check if this is a regression in the FreeBSD kernel or Xen itself?<= br>
Regards, Roger.

--20cf300fb13f2189ab04d65464b3-- --===============5294607674502398409== 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 --===============5294607674502398409==-- From xen-users-bounces@lists.xen.org Fri Feb 22 19:13:42 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 22 Feb 2013 19:13: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 1U8y2p-0005Fq-SH; Fri, 22 Feb 2013 19:12:31 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U8y2n-0005Fl-V8 for xen-users@lists.xen.org; Fri, 22 Feb 2013 19:12:30 +0000 Received: from [85.158.143.99:14522] by server-1.bemta-4.messagelabs.com id 7E/D6-06203-D13C7215; Fri, 22 Feb 2013 19:12:29 +0000 X-Env-Sender: jason.vas.dias@gmail.com X-Msg-Ref: server-10.tower-216.messagelabs.com!1361560335!21332413!1 X-Originating-IP: [209.85.215.174] 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: YXN5bmNfZGVsYXk6IDcwNDUyMjggKHRpbWVvdXQp\n X-StarScan-Received: X-StarScan-Version: 6.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 32447 invoked from network); 22 Feb 2013 19:12:15 -0000 Received: from mail-ea0-f174.google.com (HELO mail-ea0-f174.google.com) (209.85.215.174) by server-10.tower-216.messagelabs.com with RC4-SHA encrypted SMTP; 22 Feb 2013 19:12:15 -0000 Received: by mail-ea0-f174.google.com with SMTP id 1so412996eaa.19 for ; Fri, 22 Feb 2013 11:12:15 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=7y88KVoxqqXYfexWfR9r+xrlx3titQkO7K9144nZXNE=; b=mkTp+GN8gVJw+2ZPQ6RU4RfX/EdM4I6HpaniY87oGfLYTHfwk1bjp2NVjzNbDFzoRo 7BPKNCxv31s39XXi9b61Ti3NYG9YEZM374KB0HMUuYkzBtFtFYMsdafbkTn+c0GDIrbV DoFWekndwnF9PjgSmsu+/AAIPmrl4KisiU0vdJflaGc0f6piBfvxlxpmTN3lvVSjsm8H XiziI7BpZJ9JEmS2/QKhuW3p26fYBzrpqY7JSVMNjlvgY1QtGssR8rDINXKMsKhCQ98q nbpchA6WRZnwm0eK9i/cwYYHf4gPLVd3Vboli6vAsd5pVN8a2NECuwqcTr1N5KN5puPy dJpw== MIME-Version: 1.0 X-Received: by 10.14.175.129 with SMTP id z1mr9465296eel.7.1361560334889; Fri, 22 Feb 2013 11:12:14 -0800 (PST) Received: by 10.223.73.204 with HTTP; Fri, 22 Feb 2013 11:12:14 -0800 (PST) In-Reply-To: References: Date: Fri, 22 Feb 2013 19:12:14 +0000 Message-ID: From: Jason Vas Dias To: Casey DeLorme Cc: "xen-users@lists.xen.org" Subject: Re: [Xen-users] help please - running a guest from an iSCSI disk ? getting more diagnostics than "cannot make domain: -3" ? how to make domain0 "privileged" ? X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: 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 Casey - many thanks for your informative response ! - I've now got it working , with a number of caveats / gotchas, detailed below: On Thu, Feb 21, 2013 at 9:30 PM, Casey DeLorme wrote: > > Hello Jason, > > Looking at your configuration, was the kernel built to be PV Compatible > (http://sanifool.wordpress.com/2013/01/09/booting-up-a-domu-on-xen-4-2/). > Yes, the configuration arguments of the latest ArchLinux kernel ( 3.7.9-1-ARCH) check out for Xen . > The disk line looks fine provided you wanted to pass the whole disk to your > PVM (including it's partition table etc). Also if you have it mounted while > trying to launch the PVM that may throw warnings or errors. > > Is it possible you are missing the bootloader > (http://xenbits.xen.org/docs/4.2-testing/man/xl.cfg.5.html)? > Yes, that was confusing - I first gave xl just 'kernel="/boot/vmlinuz..." , but then xl complained it couldn't find the kernel, so I mounted the iSCSI share and gave xl the full path to the kernel ; but then I saw your post and specified the "bootloader="pygrub"' setting, which did not work until the fix for this bug is built into libxl : Bug 1844 - xl coredumps whenever any "bootloader=" setting is used in an xl.cfg file Having fixed that, then I came up against a number of disk issues - No setting for the disk 'vdev' field seemed to have any effect - ie. sda , sda6, hda, sdc (the real device name) - the guest OS could not see that device. Happily, with the dracut 'rdshell' argument supported by the guest OS, I was able to get it into initramfs debug mode, and saw the disk on /dev/xvdc - this appears to be the only usable setting for the root= kernel argument - it is now booting from this. Perhaps this is just because I'm using the default initramfs file and did not build one with the extra devices ? > I don't believe it would affect your ability to launch the PVM, but the I am > unfamiliar with your vif device model, and the mac address isn't in the > suggested Xen range > (http://xenbits.xen.org/docs/4.2-testing/misc/xl-network-configuration.html). > Yes, I should have read that document more closely - the setting that works is vif=["bridge=eth0"] Then, with the default 'peth0' bridge created by default on ArchLinux, I get : # brctl show bridge name bridge id STP enabled interfaces eth0 8000.00093d130d57 no peth0 vif22.0 > > If you are looking for more detailed diagnostics, you might check that the > xen-debug kernel flag is set (and rebuild your ramdisk or kernel). > > > Logging must vary by distribution as I almost never see non-kernel software > log its errors to dmesg (/var/log/messages), but most will place logs into > the same directory and organize them by file or folder. In Xen's case it > uses your toolstacks command xl dmesg (/var/logs/xen/). > Yes, but my point was that xl should not silently fail because of the errata-121 issue without telling the user - perhaps, if xl finds domain creation failed, it could automatically do its dmesg stuff and dump the Xen log messages to stderr ? Also, in many cases when domain creation failed because of the above issues, xl returned a 0 exit status - it really should be returning >0 in these cases. > --- > > > On Thu, Feb 21, 2013 at 2:24 PM, Jason Vas Dias > wrote: >> >> I'm beginning to conclude that Xen is not of sufficient code quality >> to be useful. >> >> Firstly, my 'xl create' command returns a 0 exit status, meaning >> success, but yet no domain >> is created or can be attached to or listed with 'xl list' : >> >> # xl create my_domain.cfg >> Parsing config from my_domain.cfg >> Daemon running with PID 1436 >> # echo $? >> 0 >> # xl list >> Name ID Mem VCPUs State >> Time(s) >> Domain-0 0 1024 2 r----- >> 35.5 >> >> This appears to be due to this error message in 'xl dmesg' output : >> >> (XEN) Dom5 may compromise security on this CPU. >> (XEN) traps.c:2584:d5 Domain attempted WRMSR 00000000c0010004 from >> 0x0000000000000000 to 0x000000000000abcd. >> >> From reading the source, the traps.c message appears to indicate an >> error condition, but you would not know this from the log message. >> > Have you checked all of the log files in /var/logs/xen/? > > Pretty sure that so long as the configuration itself doesn't contain > syntactical errors and the command to qemu goes through that xl will assume > it did its job. > > Is it possible xl create is launching the domains just fine (hence code 0), > and they are failing at a different stage (eg qemu during boot due to > configuration problems)? But then xl should not be returning '0' . > >> Anyone know how to avoid this unhandled WRMSR ? >> >> Code that silently ignores and does not report error conditions does >> not get my vote of confidence. >> >> Can anyone convince me that Xen is of sufficient quality to be used ? >> > Plenty of well known companies are using Xen, but I don't believe they are > using the very latest stable release (4.2.1). AFAIK 4.2.1 is not available > as a package in any stable operating systems yet. Stable release of code > does not guarantee it will be compatible without plenty of configuration > based on your choice of Dom0. > OK - I prefer to use latest available versions of everything so at least I know all known bugs are fixed, and I can help find new bugs. > However I am under the assumption that you are not using it for production > purposes given your choices (Xen 4.2.1 and ArchLinux don't exactly point to > concerns with stability or desirable ease of operation as a priority). If > that is the case then as a personal user I can say that I have had great > success using Xen 4.2 on Debain Wheezy for several months now. However I > have not dabbled in many of the areas you are (such as iSCSI, PVM's and > programmatic domain control). > > However, even with my limited experience, I can easily conclude that because > Xen can be used for such a wide variety of purposes it becomes that much > harder to ensure functionality as factors that can influence success tend to > cover a wide range (host hardware, Xen version, installed packages and > package versions, Dom0 distro and version, etc). > > > Hope these answers will help you identify the problem. > > ~Casey I'm trying to use Xen for our testing server - in a "semi-production" / backend environment - where we produce software that claims to run on @30 different OS-es, and we don't have 30 physical servers, I'm setting up one server to be able to boot each different supported OS with Xen, for testing purposes. Now at least I've got one working ... only 30 more to go ! Thank You & Regards, Jason _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Fri Feb 22 19:13:42 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 22 Feb 2013 19:13: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 1U8y2p-0005Fq-SH; Fri, 22 Feb 2013 19:12:31 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U8y2n-0005Fl-V8 for xen-users@lists.xen.org; Fri, 22 Feb 2013 19:12:30 +0000 Received: from [85.158.143.99:14522] by server-1.bemta-4.messagelabs.com id 7E/D6-06203-D13C7215; Fri, 22 Feb 2013 19:12:29 +0000 X-Env-Sender: jason.vas.dias@gmail.com X-Msg-Ref: server-10.tower-216.messagelabs.com!1361560335!21332413!1 X-Originating-IP: [209.85.215.174] 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: YXN5bmNfZGVsYXk6IDcwNDUyMjggKHRpbWVvdXQp\n X-StarScan-Received: X-StarScan-Version: 6.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 32447 invoked from network); 22 Feb 2013 19:12:15 -0000 Received: from mail-ea0-f174.google.com (HELO mail-ea0-f174.google.com) (209.85.215.174) by server-10.tower-216.messagelabs.com with RC4-SHA encrypted SMTP; 22 Feb 2013 19:12:15 -0000 Received: by mail-ea0-f174.google.com with SMTP id 1so412996eaa.19 for ; Fri, 22 Feb 2013 11:12:15 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=7y88KVoxqqXYfexWfR9r+xrlx3titQkO7K9144nZXNE=; b=mkTp+GN8gVJw+2ZPQ6RU4RfX/EdM4I6HpaniY87oGfLYTHfwk1bjp2NVjzNbDFzoRo 7BPKNCxv31s39XXi9b61Ti3NYG9YEZM374KB0HMUuYkzBtFtFYMsdafbkTn+c0GDIrbV DoFWekndwnF9PjgSmsu+/AAIPmrl4KisiU0vdJflaGc0f6piBfvxlxpmTN3lvVSjsm8H XiziI7BpZJ9JEmS2/QKhuW3p26fYBzrpqY7JSVMNjlvgY1QtGssR8rDINXKMsKhCQ98q nbpchA6WRZnwm0eK9i/cwYYHf4gPLVd3Vboli6vAsd5pVN8a2NECuwqcTr1N5KN5puPy dJpw== MIME-Version: 1.0 X-Received: by 10.14.175.129 with SMTP id z1mr9465296eel.7.1361560334889; Fri, 22 Feb 2013 11:12:14 -0800 (PST) Received: by 10.223.73.204 with HTTP; Fri, 22 Feb 2013 11:12:14 -0800 (PST) In-Reply-To: References: Date: Fri, 22 Feb 2013 19:12:14 +0000 Message-ID: From: Jason Vas Dias To: Casey DeLorme Cc: "xen-users@lists.xen.org" Subject: Re: [Xen-users] help please - running a guest from an iSCSI disk ? getting more diagnostics than "cannot make domain: -3" ? how to make domain0 "privileged" ? X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: 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 Casey - many thanks for your informative response ! - I've now got it working , with a number of caveats / gotchas, detailed below: On Thu, Feb 21, 2013 at 9:30 PM, Casey DeLorme wrote: > > Hello Jason, > > Looking at your configuration, was the kernel built to be PV Compatible > (http://sanifool.wordpress.com/2013/01/09/booting-up-a-domu-on-xen-4-2/). > Yes, the configuration arguments of the latest ArchLinux kernel ( 3.7.9-1-ARCH) check out for Xen . > The disk line looks fine provided you wanted to pass the whole disk to your > PVM (including it's partition table etc). Also if you have it mounted while > trying to launch the PVM that may throw warnings or errors. > > Is it possible you are missing the bootloader > (http://xenbits.xen.org/docs/4.2-testing/man/xl.cfg.5.html)? > Yes, that was confusing - I first gave xl just 'kernel="/boot/vmlinuz..." , but then xl complained it couldn't find the kernel, so I mounted the iSCSI share and gave xl the full path to the kernel ; but then I saw your post and specified the "bootloader="pygrub"' setting, which did not work until the fix for this bug is built into libxl : Bug 1844 - xl coredumps whenever any "bootloader=" setting is used in an xl.cfg file Having fixed that, then I came up against a number of disk issues - No setting for the disk 'vdev' field seemed to have any effect - ie. sda , sda6, hda, sdc (the real device name) - the guest OS could not see that device. Happily, with the dracut 'rdshell' argument supported by the guest OS, I was able to get it into initramfs debug mode, and saw the disk on /dev/xvdc - this appears to be the only usable setting for the root= kernel argument - it is now booting from this. Perhaps this is just because I'm using the default initramfs file and did not build one with the extra devices ? > I don't believe it would affect your ability to launch the PVM, but the I am > unfamiliar with your vif device model, and the mac address isn't in the > suggested Xen range > (http://xenbits.xen.org/docs/4.2-testing/misc/xl-network-configuration.html). > Yes, I should have read that document more closely - the setting that works is vif=["bridge=eth0"] Then, with the default 'peth0' bridge created by default on ArchLinux, I get : # brctl show bridge name bridge id STP enabled interfaces eth0 8000.00093d130d57 no peth0 vif22.0 > > If you are looking for more detailed diagnostics, you might check that the > xen-debug kernel flag is set (and rebuild your ramdisk or kernel). > > > Logging must vary by distribution as I almost never see non-kernel software > log its errors to dmesg (/var/log/messages), but most will place logs into > the same directory and organize them by file or folder. In Xen's case it > uses your toolstacks command xl dmesg (/var/logs/xen/). > Yes, but my point was that xl should not silently fail because of the errata-121 issue without telling the user - perhaps, if xl finds domain creation failed, it could automatically do its dmesg stuff and dump the Xen log messages to stderr ? Also, in many cases when domain creation failed because of the above issues, xl returned a 0 exit status - it really should be returning >0 in these cases. > --- > > > On Thu, Feb 21, 2013 at 2:24 PM, Jason Vas Dias > wrote: >> >> I'm beginning to conclude that Xen is not of sufficient code quality >> to be useful. >> >> Firstly, my 'xl create' command returns a 0 exit status, meaning >> success, but yet no domain >> is created or can be attached to or listed with 'xl list' : >> >> # xl create my_domain.cfg >> Parsing config from my_domain.cfg >> Daemon running with PID 1436 >> # echo $? >> 0 >> # xl list >> Name ID Mem VCPUs State >> Time(s) >> Domain-0 0 1024 2 r----- >> 35.5 >> >> This appears to be due to this error message in 'xl dmesg' output : >> >> (XEN) Dom5 may compromise security on this CPU. >> (XEN) traps.c:2584:d5 Domain attempted WRMSR 00000000c0010004 from >> 0x0000000000000000 to 0x000000000000abcd. >> >> From reading the source, the traps.c message appears to indicate an >> error condition, but you would not know this from the log message. >> > Have you checked all of the log files in /var/logs/xen/? > > Pretty sure that so long as the configuration itself doesn't contain > syntactical errors and the command to qemu goes through that xl will assume > it did its job. > > Is it possible xl create is launching the domains just fine (hence code 0), > and they are failing at a different stage (eg qemu during boot due to > configuration problems)? But then xl should not be returning '0' . > >> Anyone know how to avoid this unhandled WRMSR ? >> >> Code that silently ignores and does not report error conditions does >> not get my vote of confidence. >> >> Can anyone convince me that Xen is of sufficient quality to be used ? >> > Plenty of well known companies are using Xen, but I don't believe they are > using the very latest stable release (4.2.1). AFAIK 4.2.1 is not available > as a package in any stable operating systems yet. Stable release of code > does not guarantee it will be compatible without plenty of configuration > based on your choice of Dom0. > OK - I prefer to use latest available versions of everything so at least I know all known bugs are fixed, and I can help find new bugs. > However I am under the assumption that you are not using it for production > purposes given your choices (Xen 4.2.1 and ArchLinux don't exactly point to > concerns with stability or desirable ease of operation as a priority). If > that is the case then as a personal user I can say that I have had great > success using Xen 4.2 on Debain Wheezy for several months now. However I > have not dabbled in many of the areas you are (such as iSCSI, PVM's and > programmatic domain control). > > However, even with my limited experience, I can easily conclude that because > Xen can be used for such a wide variety of purposes it becomes that much > harder to ensure functionality as factors that can influence success tend to > cover a wide range (host hardware, Xen version, installed packages and > package versions, Dom0 distro and version, etc). > > > Hope these answers will help you identify the problem. > > ~Casey I'm trying to use Xen for our testing server - in a "semi-production" / backend environment - where we produce software that claims to run on @30 different OS-es, and we don't have 30 physical servers, I'm setting up one server to be able to boot each different supported OS with Xen, for testing purposes. Now at least I've got one working ... only 30 more to go ! Thank You & Regards, Jason _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Sat Feb 23 08:14:14 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sat, 23 Feb 2013 08:14: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 1U9ADi-0000xP-Em; Sat, 23 Feb 2013 08:12:34 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U9ADh-0000xK-2l for xen-users@lists.xen.org; Sat, 23 Feb 2013 08:12:33 +0000 Received: from [85.158.143.99:31896] by server-2.bemta-4.messagelabs.com id D0/94-12656-FE978215; Sat, 23 Feb 2013 08:12:31 +0000 X-Env-Sender: roger.pau@citrix.com X-Msg-Ref: server-12.tower-216.messagelabs.com!1361607150!23581999!1 X-Originating-IP: [46.33.159.39] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNDYuMzMuMTU5LjM5ID0+IDIzOTQ1\n X-StarScan-Received: X-StarScan-Version: 6.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 25612 invoked from network); 23 Feb 2013 08:12:30 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (46.33.159.39) by server-12.tower-216.messagelabs.com with RC4-SHA encrypted SMTP; 23 Feb 2013 08:12:30 -0000 X-IronPort-AV: E=Sophos;i="4.84,721,1355097600"; d="scan'208";a="1808927" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 23 Feb 2013 08:12:30 +0000 Received: from Roger-2.local (10.30.249.242) by LONPMAILMX01.citrite.net (10.30.203.162) with Microsoft SMTP Server id 8.3.297.1; Sat, 23 Feb 2013 08:12:29 +0000 Message-ID: <51287A18.7040200@citrix.com> Date: Sat, 23 Feb 2013 09:13:12 +0100 From: =?ISO-8859-1?Q?Roger_Pau_Monn=E9?= User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130216 Thunderbird/17.0.3 MIME-Version: 1.0 To: tech mailinglists References: <51279FA1.2090809@citrix.com> In-Reply-To: Cc: xen-users , "freebsd-xen@lists.freebsd.org" Subject: Re: [Xen-users] Trouble booting FreeBSD i386 PV 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: 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 22/02/13 19:30, tech mailinglists wrote: > Hello Roger, > > > I tried a further thing in the kernel configuration. I remove the option > KBD_INSTALL_CDEV and now I am no longer getting dropped to a minimal > console. The boot now looks like this: > > Parsing config from /root/xen/freebsd-test.cfg > libxl: error: libxl_dm.c:1212:device_model_spawn_outcome: domain 20 > device model: spawn failed (rc=-3) > libxl: error: libxl_qmp.c:641:libxl__qmp_initialize: Connection error: > No such file or directory > Daemon running with PID 4383 > WARNING: loader(8) metadata is missing! > GDB: no debug ports present > KDB: debugger backends: ddb > KDB: current backend: ddb > APIC: Using the MPTable enumerator. > SMP: Added CPU 0 (BSP) > Copyright (c) 1992-2012 The FreeBSD Project. > Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 > The Regents of the University of California. All rights reserved. > FreeBSD is a registered trademark of The FreeBSD Foundation. > FreeBSD 9.1-RELEASE #1 r247145M: Fri Feb 22 18:26:55 CET 2013 > root@build:/usr/obj/usr/src/sys/XEN i386 > Xen reported: 3341.754 MHz processor. > Timecounter "ixen" frequency 1953125 Hz quality 0 > CPU: Intel(R) Core(TM) i7 CPU 975 @ 3.33GHz (3341.75-MHz > 686-class CPU) > Origin = "GenuineIntel" Id = 0x106a5 Family = 6 Model = 1a > Stepping = 5 > > Features=0xbfe3fbff > > Features2=0x98e3bd > AMD Features=0x28100000 > AMD Features2=0x1 > > Data TLB: 4 KB pages, 4-way set associative, 64 entries > 1st-level data cache: 32 KB, 8-way set associative, 64 byte line size > L2 cache: 256 kbytes, 8-way associative, 64 bytes/line > real memory = 536870912 (512 MB) > Physical memory chunk(s): > 0x0000000000670000 - 0x000000001f628fff, 519802880 bytes (126905 pages) > avail memory = 516833280 (492 MB) > INTR: Adding local APIC 0 as a target > ULE: setup cpu 0 > [XEN] IPI cpu=0 irq=128 vector=RESCHEDULE_VECTOR (0) > [XEN] IPI cpu=0 irq=129 vector=CALL_FUNCTION_VECTOR (1) > Event-channel device installed. > random: > io: > mem: > Pentium Pro MTRR support enabled > null: > nfslock: pseudo-device > [XEN] xen_rtc_probe: probing Hypervisor RTC clock > rtc0: on motherboard > [XEN] xen_rtc_attach: attaching Hypervisor RTC clock > rtc0: registered as a time-of-day clock (resolution 1000000us, > adjustment 0.500000000s) > xenstore0: on motherboard > Grant table initialized > xc0: on motherboard > Device configuration finished. > procfs registered > Event timer "ixen" quality 600 > Timecounters tick every 10.000 msec > lo0: bpf attached > xenbusb_front0: on xenstore0 > xenbusb_add_device: Device device/suspend/event-channel ignored. State 6 > xn0: at device/vif/0 on xenbusb_front0 > xn0: bpf attached > xn0: Ethernet address: 00:16:3e:44:b1:b9 > xenbusb_back0: on xenstore0 > xctrl0: on xenstore0 > xn0: backend features: feature-sg feature-gso-tcp4 > [XEN] hypervisor wallclock nudged; nudging TOD. > run_interrupt_driven_hooks: still waiting after 60 seconds for > xenbus_free_evtchn > [XEN] hypervisor wallclock nudged; nudging TOD. > run_interrupt_driven_hooks: still waiting after 120 seconds for > xenbus_free_evtchn > run_interrupt_driven_hooks: still waiting after 180 seconds for > xenbus_free_evtchn > run_interrupt_driven_hooks: still waiting after 240 seconds for > xenbus_free_evtchn > run_interrupt_driven_hooks: still waiting after 300 seconds for > xenbus_free_evtchn > [XEN] hypervisor wallclock nudged; nudging TOD. > [XEN] hypervisor wallclock nudged; nudging TOD. > [XEN] hypervisor wallclock nudged; nudging TOD. > > I will test HVM and PVHVM but in the past I had no problems with this. > It would be greate to have pure PV mode. The only thing which confuses > me is the libxl related error on the domain creation: > > Parsing config from /root/xen/freebsd-test.cfg > libxl: error: libxl_dm.c:1212:device_model_spawn_outcome: domain 20 > device model: spawn failed (rc=-3) > libxl: error: libxl_qmp.c:641:libxl__qmp_initialize: Connection error: > No such file or directory > > I know that in a few cases PV guests have QEmu process but I can not say > while this failes. Eventually there is something not compiled in, into > Xen or the toolstack? PV guests use Qemu to provide a block backend for raw file images, so if Qemu fails to start your PV guest won't we able to access the hard drive, that could be the reason why the FreeBSD PV guest is unable to boot. Could you check Qemu log in /var/log/xen/qemu-dm-freebsd.log? > > I saw that you have made a talk on FOSDEM about BSD and PVH. I > downloaded the slide PDF but I am not able to open the document. It says > that the document is corrupted. Am I doing a mistake? Or is there a > problem with the document on the FOSDEM page. I've just checked and the slides look OK to me, I'm able to open them without problems. SHA1 sum: 0b0070149e0b4cf0b5557230793acccd1291ccde new_xen_paravirt_mode.pdf _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Sat Feb 23 08:14:14 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sat, 23 Feb 2013 08:14: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 1U9ADi-0000xP-Em; Sat, 23 Feb 2013 08:12:34 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U9ADh-0000xK-2l for xen-users@lists.xen.org; Sat, 23 Feb 2013 08:12:33 +0000 Received: from [85.158.143.99:31896] by server-2.bemta-4.messagelabs.com id D0/94-12656-FE978215; Sat, 23 Feb 2013 08:12:31 +0000 X-Env-Sender: roger.pau@citrix.com X-Msg-Ref: server-12.tower-216.messagelabs.com!1361607150!23581999!1 X-Originating-IP: [46.33.159.39] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNDYuMzMuMTU5LjM5ID0+IDIzOTQ1\n X-StarScan-Received: X-StarScan-Version: 6.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 25612 invoked from network); 23 Feb 2013 08:12:30 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (46.33.159.39) by server-12.tower-216.messagelabs.com with RC4-SHA encrypted SMTP; 23 Feb 2013 08:12:30 -0000 X-IronPort-AV: E=Sophos;i="4.84,721,1355097600"; d="scan'208";a="1808927" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 23 Feb 2013 08:12:30 +0000 Received: from Roger-2.local (10.30.249.242) by LONPMAILMX01.citrite.net (10.30.203.162) with Microsoft SMTP Server id 8.3.297.1; Sat, 23 Feb 2013 08:12:29 +0000 Message-ID: <51287A18.7040200@citrix.com> Date: Sat, 23 Feb 2013 09:13:12 +0100 From: =?ISO-8859-1?Q?Roger_Pau_Monn=E9?= User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130216 Thunderbird/17.0.3 MIME-Version: 1.0 To: tech mailinglists References: <51279FA1.2090809@citrix.com> In-Reply-To: Cc: xen-users , "freebsd-xen@lists.freebsd.org" Subject: Re: [Xen-users] Trouble booting FreeBSD i386 PV 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: 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 22/02/13 19:30, tech mailinglists wrote: > Hello Roger, > > > I tried a further thing in the kernel configuration. I remove the option > KBD_INSTALL_CDEV and now I am no longer getting dropped to a minimal > console. The boot now looks like this: > > Parsing config from /root/xen/freebsd-test.cfg > libxl: error: libxl_dm.c:1212:device_model_spawn_outcome: domain 20 > device model: spawn failed (rc=-3) > libxl: error: libxl_qmp.c:641:libxl__qmp_initialize: Connection error: > No such file or directory > Daemon running with PID 4383 > WARNING: loader(8) metadata is missing! > GDB: no debug ports present > KDB: debugger backends: ddb > KDB: current backend: ddb > APIC: Using the MPTable enumerator. > SMP: Added CPU 0 (BSP) > Copyright (c) 1992-2012 The FreeBSD Project. > Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 > The Regents of the University of California. All rights reserved. > FreeBSD is a registered trademark of The FreeBSD Foundation. > FreeBSD 9.1-RELEASE #1 r247145M: Fri Feb 22 18:26:55 CET 2013 > root@build:/usr/obj/usr/src/sys/XEN i386 > Xen reported: 3341.754 MHz processor. > Timecounter "ixen" frequency 1953125 Hz quality 0 > CPU: Intel(R) Core(TM) i7 CPU 975 @ 3.33GHz (3341.75-MHz > 686-class CPU) > Origin = "GenuineIntel" Id = 0x106a5 Family = 6 Model = 1a > Stepping = 5 > > Features=0xbfe3fbff > > Features2=0x98e3bd > AMD Features=0x28100000 > AMD Features2=0x1 > > Data TLB: 4 KB pages, 4-way set associative, 64 entries > 1st-level data cache: 32 KB, 8-way set associative, 64 byte line size > L2 cache: 256 kbytes, 8-way associative, 64 bytes/line > real memory = 536870912 (512 MB) > Physical memory chunk(s): > 0x0000000000670000 - 0x000000001f628fff, 519802880 bytes (126905 pages) > avail memory = 516833280 (492 MB) > INTR: Adding local APIC 0 as a target > ULE: setup cpu 0 > [XEN] IPI cpu=0 irq=128 vector=RESCHEDULE_VECTOR (0) > [XEN] IPI cpu=0 irq=129 vector=CALL_FUNCTION_VECTOR (1) > Event-channel device installed. > random: > io: > mem: > Pentium Pro MTRR support enabled > null: > nfslock: pseudo-device > [XEN] xen_rtc_probe: probing Hypervisor RTC clock > rtc0: on motherboard > [XEN] xen_rtc_attach: attaching Hypervisor RTC clock > rtc0: registered as a time-of-day clock (resolution 1000000us, > adjustment 0.500000000s) > xenstore0: on motherboard > Grant table initialized > xc0: on motherboard > Device configuration finished. > procfs registered > Event timer "ixen" quality 600 > Timecounters tick every 10.000 msec > lo0: bpf attached > xenbusb_front0: on xenstore0 > xenbusb_add_device: Device device/suspend/event-channel ignored. State 6 > xn0: at device/vif/0 on xenbusb_front0 > xn0: bpf attached > xn0: Ethernet address: 00:16:3e:44:b1:b9 > xenbusb_back0: on xenstore0 > xctrl0: on xenstore0 > xn0: backend features: feature-sg feature-gso-tcp4 > [XEN] hypervisor wallclock nudged; nudging TOD. > run_interrupt_driven_hooks: still waiting after 60 seconds for > xenbus_free_evtchn > [XEN] hypervisor wallclock nudged; nudging TOD. > run_interrupt_driven_hooks: still waiting after 120 seconds for > xenbus_free_evtchn > run_interrupt_driven_hooks: still waiting after 180 seconds for > xenbus_free_evtchn > run_interrupt_driven_hooks: still waiting after 240 seconds for > xenbus_free_evtchn > run_interrupt_driven_hooks: still waiting after 300 seconds for > xenbus_free_evtchn > [XEN] hypervisor wallclock nudged; nudging TOD. > [XEN] hypervisor wallclock nudged; nudging TOD. > [XEN] hypervisor wallclock nudged; nudging TOD. > > I will test HVM and PVHVM but in the past I had no problems with this. > It would be greate to have pure PV mode. The only thing which confuses > me is the libxl related error on the domain creation: > > Parsing config from /root/xen/freebsd-test.cfg > libxl: error: libxl_dm.c:1212:device_model_spawn_outcome: domain 20 > device model: spawn failed (rc=-3) > libxl: error: libxl_qmp.c:641:libxl__qmp_initialize: Connection error: > No such file or directory > > I know that in a few cases PV guests have QEmu process but I can not say > while this failes. Eventually there is something not compiled in, into > Xen or the toolstack? PV guests use Qemu to provide a block backend for raw file images, so if Qemu fails to start your PV guest won't we able to access the hard drive, that could be the reason why the FreeBSD PV guest is unable to boot. Could you check Qemu log in /var/log/xen/qemu-dm-freebsd.log? > > I saw that you have made a talk on FOSDEM about BSD and PVH. I > downloaded the slide PDF but I am not able to open the document. It says > that the document is corrupted. Am I doing a mistake? Or is there a > problem with the document on the FOSDEM page. I've just checked and the slides look OK to me, I'm able to open them without problems. SHA1 sum: 0b0070149e0b4cf0b5557230793acccd1291ccde new_xen_paravirt_mode.pdf _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Sat Feb 23 09:59:25 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sat, 23 Feb 2013 09:59: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 1U9Brj-00043h-5A; Sat, 23 Feb 2013 09:57:59 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U9Brh-00043c-2C for xen-users@lists.xensource.com; Sat, 23 Feb 2013 09:57:57 +0000 Received: from [85.158.139.211:41598] by server-12.bemta-5.messagelabs.com id 11/46-20195-4A298215; Sat, 23 Feb 2013 09:57:56 +0000 X-Env-Sender: mlg-hessigheim@gmx.de X-Msg-Ref: server-14.tower-206.messagelabs.com!1361613475!18825537!1 X-Originating-IP: [212.227.17.20] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogMjEyLjIyNy4xNy4yMCA9PiAxNzkwOQ==\n, ML_RADAR_SPEW_LINKS_14,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 8856 invoked from network); 23 Feb 2013 09:57:55 -0000 Received: from mout.gmx.net (HELO mout.gmx.net) (212.227.17.20) by server-14.tower-206.messagelabs.com with SMTP; 23 Feb 2013 09:57:55 -0000 Received: from mailout-de.gmx.net ([10.1.76.1]) by mrigmx.server.lan (mrigmx001) with ESMTP (Nemesis) id 0MN7As-1UBNjH2tDc-006d7X for ; Sat, 23 Feb 2013 10:57:55 +0100 Received: (qmail invoked by alias); 23 Feb 2013 09:57:55 -0000 Received: from HSI-KBW-078-042-066-159.hsi3.kabel-badenwuerttemberg.de (EHLO [192.168.2.163]) [78.42.66.159] by mail.gmx.net (mp001) with SMTP; 23 Feb 2013 10:57:55 +0100 X-Authenticated: #12881343 X-Provags-ID: V01U2FsdGVkX1/6cWsAHon67dlhGO3t7TNKedTY/bmV+jFg+J02Cy zbRYLS2olrDUeZ Message-ID: <512892A1.1090008@gmx.de> Date: Sat, 23 Feb 2013 10:57:53 +0100 From: Martin Lang User-Agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/20130106 Thunderbird/17.0.2 MIME-Version: 1.0 To: Ian Campbell References: <511F6E82.8040107@gmx.de> <1361183374.31407.129.camel@zakaz.uk.xensource.com> In-Reply-To: <1361183374.31407.129.camel@zakaz.uk.xensource.com> X-Y-GMX-Trusted: 0 Cc: xen-users@lists.xensource.com Subject: Re: [Xen-users] Boot problem with Debian Squeeza and Xen X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: mlg-hessigheim@gmx.de 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 It is an Athlon XP system running on an Elitegroup K7S5A board. Adding "lapic" as boot option did the job. Thank you On 02/18/2013 11:29 AM, Ian Campbell wrote: > On Sat, 2013-02-16 at 11:33 +0000, Martin Lang wrote: >> Hi all, >> >> I just upgraded my Debian/Etch with Xen3.3 machine to Debian/Squeeze >> Xen4.0 and now have problems with starting the Dom0 kernel. I always get >> the error message: Kernel panic not syncing: the kernel parameter noapic >> is incompatible with xen. > Is this the literal message? I've grepped the kernel and hypervisor > source and cannot find it anywhere. Please can you collect the actual > logs from the system. > http://wiki.xen.org/wiki/Reporting_Bugs_against_Xen#Host_console_logs > > What sort of processor does this system have? > >> My grub.cfg is: >> >> menuentry 'Debian GNU/Linux, with Linux 2.6.32-5-xen-686 and XEN >> 4.0-i386' --cl$ >> insmod part_msdos >> insmod ext2 >> set root='(hd0,msdos1)' >> search --no-floppy --fs-uuid --set >> 743d959f-5054-441f-b68d-32d9970bb8ab >> echo 'Loading Linux 2.6.32-5-xen-686 ...' >> multiboot /boot/xen-4.0-i386.gz noreboot placeholder >> module /boot/vmlinuz-2.6.32-5-xen-686 placeholder >> root=UUID=743d959f-5$ >> echo 'Loading initial ramdisk ...' >> module /boot/initrd.img-2.6.32-5-xen-686 >> >> >> I already tried the boot parameters: noapic nolapic acpi=off in the line >> mulitboot .... and module /boot/vmlinuz line. > The message is complaining about the presence of "noapic" not its > absence, so I hope you also tried without. > > Ian. > > _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Sat Feb 23 09:59:25 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sat, 23 Feb 2013 09:59: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 1U9Brj-00043h-5A; Sat, 23 Feb 2013 09:57:59 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U9Brh-00043c-2C for xen-users@lists.xensource.com; Sat, 23 Feb 2013 09:57:57 +0000 Received: from [85.158.139.211:41598] by server-12.bemta-5.messagelabs.com id 11/46-20195-4A298215; Sat, 23 Feb 2013 09:57:56 +0000 X-Env-Sender: mlg-hessigheim@gmx.de X-Msg-Ref: server-14.tower-206.messagelabs.com!1361613475!18825537!1 X-Originating-IP: [212.227.17.20] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogMjEyLjIyNy4xNy4yMCA9PiAxNzkwOQ==\n, ML_RADAR_SPEW_LINKS_14,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 8856 invoked from network); 23 Feb 2013 09:57:55 -0000 Received: from mout.gmx.net (HELO mout.gmx.net) (212.227.17.20) by server-14.tower-206.messagelabs.com with SMTP; 23 Feb 2013 09:57:55 -0000 Received: from mailout-de.gmx.net ([10.1.76.1]) by mrigmx.server.lan (mrigmx001) with ESMTP (Nemesis) id 0MN7As-1UBNjH2tDc-006d7X for ; Sat, 23 Feb 2013 10:57:55 +0100 Received: (qmail invoked by alias); 23 Feb 2013 09:57:55 -0000 Received: from HSI-KBW-078-042-066-159.hsi3.kabel-badenwuerttemberg.de (EHLO [192.168.2.163]) [78.42.66.159] by mail.gmx.net (mp001) with SMTP; 23 Feb 2013 10:57:55 +0100 X-Authenticated: #12881343 X-Provags-ID: V01U2FsdGVkX1/6cWsAHon67dlhGO3t7TNKedTY/bmV+jFg+J02Cy zbRYLS2olrDUeZ Message-ID: <512892A1.1090008@gmx.de> Date: Sat, 23 Feb 2013 10:57:53 +0100 From: Martin Lang User-Agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/20130106 Thunderbird/17.0.2 MIME-Version: 1.0 To: Ian Campbell References: <511F6E82.8040107@gmx.de> <1361183374.31407.129.camel@zakaz.uk.xensource.com> In-Reply-To: <1361183374.31407.129.camel@zakaz.uk.xensource.com> X-Y-GMX-Trusted: 0 Cc: xen-users@lists.xensource.com Subject: Re: [Xen-users] Boot problem with Debian Squeeza and Xen X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: mlg-hessigheim@gmx.de 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 It is an Athlon XP system running on an Elitegroup K7S5A board. Adding "lapic" as boot option did the job. Thank you On 02/18/2013 11:29 AM, Ian Campbell wrote: > On Sat, 2013-02-16 at 11:33 +0000, Martin Lang wrote: >> Hi all, >> >> I just upgraded my Debian/Etch with Xen3.3 machine to Debian/Squeeze >> Xen4.0 and now have problems with starting the Dom0 kernel. I always get >> the error message: Kernel panic not syncing: the kernel parameter noapic >> is incompatible with xen. > Is this the literal message? I've grepped the kernel and hypervisor > source and cannot find it anywhere. Please can you collect the actual > logs from the system. > http://wiki.xen.org/wiki/Reporting_Bugs_against_Xen#Host_console_logs > > What sort of processor does this system have? > >> My grub.cfg is: >> >> menuentry 'Debian GNU/Linux, with Linux 2.6.32-5-xen-686 and XEN >> 4.0-i386' --cl$ >> insmod part_msdos >> insmod ext2 >> set root='(hd0,msdos1)' >> search --no-floppy --fs-uuid --set >> 743d959f-5054-441f-b68d-32d9970bb8ab >> echo 'Loading Linux 2.6.32-5-xen-686 ...' >> multiboot /boot/xen-4.0-i386.gz noreboot placeholder >> module /boot/vmlinuz-2.6.32-5-xen-686 placeholder >> root=UUID=743d959f-5$ >> echo 'Loading initial ramdisk ...' >> module /boot/initrd.img-2.6.32-5-xen-686 >> >> >> I already tried the boot parameters: noapic nolapic acpi=off in the line >> mulitboot .... and module /boot/vmlinuz line. > The message is complaining about the presence of "noapic" not its > absence, so I hope you also tried without. > > Ian. > > _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Sat Feb 23 16:22:26 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sat, 23 Feb 2013 16:22: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 1U9HqN-00053q-0I; Sat, 23 Feb 2013 16:20:59 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U9HqL-00053l-5A for xen-users@lists.xen.org; Sat, 23 Feb 2013 16:20:57 +0000 Received: from [85.158.139.83:26763] by server-6.bemta-5.messagelabs.com id ED/4F-01489-86CE8215; Sat, 23 Feb 2013 16:20:56 +0000 X-Env-Sender: jaceksburghardt@gmail.com X-Msg-Ref: server-6.tower-182.messagelabs.com!1361636453!24709404!1 X-Originating-IP: [209.85.210.175] 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.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 15613 invoked from network); 23 Feb 2013 16:20:55 -0000 Received: from mail-ia0-f175.google.com (HELO mail-ia0-f175.google.com) (209.85.210.175) by server-6.tower-182.messagelabs.com with RC4-SHA encrypted SMTP; 23 Feb 2013 16:20:55 -0000 Received: by mail-ia0-f175.google.com with SMTP id r4so1403950iaj.34 for ; Sat, 23 Feb 2013 08:20:53 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:date:message-id:subject:from:to :content-type; bh=757chyx+VXH/F/dQlQO9Npfw9vI2Fgoe8HxAXx1PFSE=; b=yGt6TyVu6EN7YpA3tIMSW612G6DzUEIuuItEW+FHLaDkSyoFz2NobWgpxvoF+nSXbN O4lCuso2OfNTc//npmetcWdoXL3rOlyKKEgENT9r5UD2UCRDQlbxmvnnnMfV30AvgRhn uz6Czts+n6SJwe/LO7CeiWiHFHS6POx9kst2JswscIxuOWqTwEX1EuMsyq3rXAE4a1cq D54eQNeL9Dygrefi/ZkAKYRopEf2UFbzOg/0Cu9gcVarC0m9UAMqdv8elJfZgvnlamwM EFqTEtI5ESzFJ5xHT35RDL43RGAFPJg//TBdl+Ns0HUEJGbyFv5XJKcyPI+szKUgJZVM Ts0Q== MIME-Version: 1.0 X-Received: by 10.42.201.73 with SMTP id ez9mr2317808icb.29.1361636453697; Sat, 23 Feb 2013 08:20:53 -0800 (PST) Received: by 10.42.41.5 with HTTP; Sat, 23 Feb 2013 08:20:53 -0800 (PST) Date: Sat, 23 Feb 2013 09:20:53 -0700 Message-ID: From: jacek burghardt To: xen-users Subject: [Xen-users] unable to start 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="===============2842323128763253554==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============2842323128763253554== Content-Type: multipart/alternative; boundary=20cf301cc49822c6ef04d666b189 --20cf301cc49822c6ef04d666b189 Content-Type: text/plain; charset=ISO-8859-1 When I try to start hvm I get this error message. I belive that path is wrong some. Can someone point me were I can look to fix this issue xc: detail: elf_load_binary: phdr 0 at 0x0x7f06a4000000 -> 0x0x7f06a40959d5 libxl: error: libxl_dom.c:612:libxl__build_hvm: hvm building failed libxl: error: libxl_create.c:885:domcreate_rebuild_done: cannot (re-)build domain: -3 libxl: error: libxl_dm.c:1250:libxl__destroy_device_model: could not find device-model's pid for dom 10 libxl: error: libxl.c:1414:libxl__destroy_domid: libxl__destroy_device_model failed for 10 libxl: debug: libxl_event.c:1569:libxl__ao_complete: ao 0x1e88300: complete, rc=-3 libxl: debug: libxl_create.c:1227:do_domain_create: ao 0x1e88300: inprogress: poller=0x1e88ee0, flags=ic libxl: debug: libxl_event.c:1541:libxl__ao__destroy: ao 0x1e88300: destroy xc: debug: hypercall buffer: total allocations:1171 total releases:1171 xc: debug: hypercall buffer: current allocations:0 maximum allocations:4 xc: debug: hypercall buffer: cache current size:4 xc: debug: hypercall buffer: cache hits:1163 misses:4 toobig:4 --20cf301cc49822c6ef04d666b189 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable When I try to start hvm I get this error message. I belive that path is wro= ng some. Can someone point me were I can look to fix this issue
xc: det= ail: elf_load_binary: phdr 0 at 0x0x7f06a4000000 -> 0x0x7f06a40959d5
libxl: error: libxl_dom.c:612:libxl__build_hvm: hvm building failed
libx= l: error: libxl_create.c:885:domcreate_rebuild_done: cannot (re-)build doma= in: -3
libxl: error: libxl_dm.c:1250:libxl__destroy_device_model: could = not find device-model's pid for dom 10
libxl: error: libxl.c:1414:libxl__destroy_domid: libxl__destroy_device_mode= l failed for 10
libxl: debug: libxl_event.c:1569:libxl__ao_complete: ao = 0x1e88300: complete, rc=3D-3
libxl: debug: libxl_create.c:1227:do_domain= _create: ao 0x1e88300: inprogress: poller=3D0x1e88ee0, flags=3Dic
libxl: debug: libxl_event.c:1541:libxl__ao__destroy: ao 0x1e88300: destroy<= br>xc: debug: hypercall buffer: total allocations:1171 total releases:1171<= br>xc: debug: hypercall buffer: current allocations:0 maximum allocations:4=
xc: debug: hypercall buffer: cache current size:4
xc: debug: hypercall b= uffer: cache hits:1163 misses:4 toobig:4

--20cf301cc49822c6ef04d666b189-- --===============2842323128763253554== 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 --===============2842323128763253554==-- From xen-users-bounces@lists.xen.org Sat Feb 23 16:22:26 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sat, 23 Feb 2013 16:22: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 1U9HqN-00053q-0I; Sat, 23 Feb 2013 16:20:59 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U9HqL-00053l-5A for xen-users@lists.xen.org; Sat, 23 Feb 2013 16:20:57 +0000 Received: from [85.158.139.83:26763] by server-6.bemta-5.messagelabs.com id ED/4F-01489-86CE8215; Sat, 23 Feb 2013 16:20:56 +0000 X-Env-Sender: jaceksburghardt@gmail.com X-Msg-Ref: server-6.tower-182.messagelabs.com!1361636453!24709404!1 X-Originating-IP: [209.85.210.175] 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.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 15613 invoked from network); 23 Feb 2013 16:20:55 -0000 Received: from mail-ia0-f175.google.com (HELO mail-ia0-f175.google.com) (209.85.210.175) by server-6.tower-182.messagelabs.com with RC4-SHA encrypted SMTP; 23 Feb 2013 16:20:55 -0000 Received: by mail-ia0-f175.google.com with SMTP id r4so1403950iaj.34 for ; Sat, 23 Feb 2013 08:20:53 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:date:message-id:subject:from:to :content-type; bh=757chyx+VXH/F/dQlQO9Npfw9vI2Fgoe8HxAXx1PFSE=; b=yGt6TyVu6EN7YpA3tIMSW612G6DzUEIuuItEW+FHLaDkSyoFz2NobWgpxvoF+nSXbN O4lCuso2OfNTc//npmetcWdoXL3rOlyKKEgENT9r5UD2UCRDQlbxmvnnnMfV30AvgRhn uz6Czts+n6SJwe/LO7CeiWiHFHS6POx9kst2JswscIxuOWqTwEX1EuMsyq3rXAE4a1cq D54eQNeL9Dygrefi/ZkAKYRopEf2UFbzOg/0Cu9gcVarC0m9UAMqdv8elJfZgvnlamwM EFqTEtI5ESzFJ5xHT35RDL43RGAFPJg//TBdl+Ns0HUEJGbyFv5XJKcyPI+szKUgJZVM Ts0Q== MIME-Version: 1.0 X-Received: by 10.42.201.73 with SMTP id ez9mr2317808icb.29.1361636453697; Sat, 23 Feb 2013 08:20:53 -0800 (PST) Received: by 10.42.41.5 with HTTP; Sat, 23 Feb 2013 08:20:53 -0800 (PST) Date: Sat, 23 Feb 2013 09:20:53 -0700 Message-ID: From: jacek burghardt To: xen-users Subject: [Xen-users] unable to start 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="===============2842323128763253554==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============2842323128763253554== Content-Type: multipart/alternative; boundary=20cf301cc49822c6ef04d666b189 --20cf301cc49822c6ef04d666b189 Content-Type: text/plain; charset=ISO-8859-1 When I try to start hvm I get this error message. I belive that path is wrong some. Can someone point me were I can look to fix this issue xc: detail: elf_load_binary: phdr 0 at 0x0x7f06a4000000 -> 0x0x7f06a40959d5 libxl: error: libxl_dom.c:612:libxl__build_hvm: hvm building failed libxl: error: libxl_create.c:885:domcreate_rebuild_done: cannot (re-)build domain: -3 libxl: error: libxl_dm.c:1250:libxl__destroy_device_model: could not find device-model's pid for dom 10 libxl: error: libxl.c:1414:libxl__destroy_domid: libxl__destroy_device_model failed for 10 libxl: debug: libxl_event.c:1569:libxl__ao_complete: ao 0x1e88300: complete, rc=-3 libxl: debug: libxl_create.c:1227:do_domain_create: ao 0x1e88300: inprogress: poller=0x1e88ee0, flags=ic libxl: debug: libxl_event.c:1541:libxl__ao__destroy: ao 0x1e88300: destroy xc: debug: hypercall buffer: total allocations:1171 total releases:1171 xc: debug: hypercall buffer: current allocations:0 maximum allocations:4 xc: debug: hypercall buffer: cache current size:4 xc: debug: hypercall buffer: cache hits:1163 misses:4 toobig:4 --20cf301cc49822c6ef04d666b189 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable When I try to start hvm I get this error message. I belive that path is wro= ng some. Can someone point me were I can look to fix this issue
xc: det= ail: elf_load_binary: phdr 0 at 0x0x7f06a4000000 -> 0x0x7f06a40959d5
libxl: error: libxl_dom.c:612:libxl__build_hvm: hvm building failed
libx= l: error: libxl_create.c:885:domcreate_rebuild_done: cannot (re-)build doma= in: -3
libxl: error: libxl_dm.c:1250:libxl__destroy_device_model: could = not find device-model's pid for dom 10
libxl: error: libxl.c:1414:libxl__destroy_domid: libxl__destroy_device_mode= l failed for 10
libxl: debug: libxl_event.c:1569:libxl__ao_complete: ao = 0x1e88300: complete, rc=3D-3
libxl: debug: libxl_create.c:1227:do_domain= _create: ao 0x1e88300: inprogress: poller=3D0x1e88ee0, flags=3Dic
libxl: debug: libxl_event.c:1541:libxl__ao__destroy: ao 0x1e88300: destroy<= br>xc: debug: hypercall buffer: total allocations:1171 total releases:1171<= br>xc: debug: hypercall buffer: current allocations:0 maximum allocations:4=
xc: debug: hypercall buffer: cache current size:4
xc: debug: hypercall b= uffer: cache hits:1163 misses:4 toobig:4

--20cf301cc49822c6ef04d666b189-- --===============2842323128763253554== 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 --===============2842323128763253554==-- From xen-users-bounces@lists.xen.org Sat Feb 23 18:36:23 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sat, 23 Feb 2013 18:36: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 1U9Jvr-00083i-UE; Sat, 23 Feb 2013 18:34:47 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U9Jvq-00083d-Cj for xen-users@lists.xen.org; Sat, 23 Feb 2013 18:34:46 +0000 Received: from [85.158.143.99:27103] by server-3.bemta-4.messagelabs.com id E7/66-02186-5CB09215; Sat, 23 Feb 2013 18:34:45 +0000 X-Env-Sender: mailinglists.tech@gmail.com X-Msg-Ref: server-2.tower-216.messagelabs.com!1361644482!22039612!1 X-Originating-IP: [209.85.216.47] 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.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 28035 invoked from network); 23 Feb 2013 18:34:43 -0000 Received: from mail-qa0-f47.google.com (HELO mail-qa0-f47.google.com) (209.85.216.47) by server-2.tower-216.messagelabs.com with RC4-SHA encrypted SMTP; 23 Feb 2013 18:34:43 -0000 Received: by mail-qa0-f47.google.com with SMTP id j8so918607qah.20 for ; Sat, 23 Feb 2013 10:34:42 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=dQ6x8H+asmEjTEnGgt4p9JoyP1jAyPoUFfS+pSb7v0A=; b=r6Bh/jOng/RX2W0ejG2PBvQJv2XB5HP3yhlG2vu4znSiwIZazGJh5/AhLlqjbR5OJX 5c18QpJOyksXfiu0ZEptyyJEL+4K1jJeGDCmOybhgNBHBqM9kxcasFXzuAQstTeNow5n BcddGcrZxII6yWw5yirzuyVgt7Q3kmAJG5WIZFYA01bXkaAQVVqSlU9x7/t+9v9YpgWI yjIsNErH45RgEpt2UbY23nYSWaYReqEhep9kwDh0JNzjHETgme9UvypTRdGui3lpXc5T dkWfSrusylZhK5N4uo/IWXqx5g2Vh/dJQqX21wVihJHEQcZkFJEXGmEj6KT2sdvraJyA F8MQ== MIME-Version: 1.0 X-Received: by 10.224.108.74 with SMTP id e10mr3613157qap.83.1361644482573; Sat, 23 Feb 2013 10:34:42 -0800 (PST) Received: by 10.49.110.70 with HTTP; Sat, 23 Feb 2013 10:34:42 -0800 (PST) In-Reply-To: <51287A18.7040200@citrix.com> References: <51279FA1.2090809@citrix.com> <51287A18.7040200@citrix.com> Date: Sat, 23 Feb 2013 19:34:42 +0100 Message-ID: From: tech mailinglists To: =?ISO-8859-1?Q?Roger_Pau_Monn=E9?= Cc: xen-users , "freebsd-xen@lists.freebsd.org" Subject: Re: [Xen-users] Trouble booting FreeBSD i386 PV 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="===============6248004445428048175==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============6248004445428048175== Content-Type: multipart/alternative; boundary=20cf3074b36ab1bf1004d6688fb4 --20cf3074b36ab1bf1004d6688fb4 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable I was able to fix the Qemu problem. I simply had to install a dependency which was needed by Qemu. The problem doesn't appeared earlier because the Linux PV guests seem to need no qemu. I think it's related to the disk notation which is used there (xvda) so kernel xen block driver is used and in the FreeBSD case (hda) so the IDE emulation of qemu is used. I am now have trouble to boot the guest with PV-GRUB. So I have a ZFS disk and I searched on the web and found this on GitHub: https://github.com/aszeszo/pv-grub It's PV-GRUB with ZFS and it can read the disk but I can not boot. The first thing is how can I cross compile a single component in the Xen build system to get a 32bit variant and not a 64bit variant as yet? And can I load FreeBSD with GRUB actually? I saw that Chainloading would be needed so I would have to boot the loader or zfsloader with GRUB but this failes with the following error: xc: error: panic: xc_dom_core.c:587: xc_dom_find_loader: no loader found: Invalid kernel xc_dom_parse_image returned -1 close(3) Error 9: Unknown boot failure So would be great when there can be found a solution for this problem. Best Regards 2013/2/23 Roger Pau Monn=E9 > On 22/02/13 19:30, tech mailinglists wrote: > > Hello Roger, > > > > > > I tried a further thing in the kernel configuration. I remove the optio= n > > KBD_INSTALL_CDEV and now I am no longer getting dropped to a minimal > > console. The boot now looks like this: > > > > Parsing config from /root/xen/freebsd-test.cfg > > libxl: error: libxl_dm.c:1212:device_model_spawn_outcome: domain 20 > > device model: spawn failed (rc=3D-3) > > libxl: error: libxl_qmp.c:641:libxl__qmp_initialize: Connection error: > > No such file or directory > > Daemon running with PID 4383 > > WARNING: loader(8) metadata is missing! > > GDB: no debug ports present > > KDB: debugger backends: ddb > > KDB: current backend: ddb > > APIC: Using the MPTable enumerator. > > SMP: Added CPU 0 (BSP) > > Copyright (c) 1992-2012 The FreeBSD Project. > > Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 199= 4 > > The Regents of the University of California. All rights reserve= d. > > FreeBSD is a registered trademark of The FreeBSD Foundation. > > FreeBSD 9.1-RELEASE #1 r247145M: Fri Feb 22 18:26:55 CET 2013 > > root@build:/usr/obj/usr/src/sys/XEN i386 > > Xen reported: 3341.754 MHz processor. > > Timecounter "ixen" frequency 1953125 Hz quality 0 > > CPU: Intel(R) Core(TM) i7 CPU 975 @ 3.33GHz (3341.75-MHz > > 686-class CPU) > > Origin =3D "GenuineIntel" Id =3D 0x106a5 Family =3D 6 Model =3D 1a > > Stepping =3D 5 > > > > > Features=3D0xbfe3fbff > > > > > Features2=3D0x98e3bd > > AMD Features=3D0x28100000 > > AMD Features2=3D0x1 > > > > Data TLB: 4 KB pages, 4-way set associative, 64 entries > > 1st-level data cache: 32 KB, 8-way set associative, 64 byte line size > > L2 cache: 256 kbytes, 8-way associative, 64 bytes/line > > real memory =3D 536870912 (512 MB) > > Physical memory chunk(s): > > 0x0000000000670000 - 0x000000001f628fff, 519802880 bytes (126905 pages) > > avail memory =3D 516833280 (492 MB) > > INTR: Adding local APIC 0 as a target > > ULE: setup cpu 0 > > [XEN] IPI cpu=3D0 irq=3D128 vector=3DRESCHEDULE_VECTOR (0) > > [XEN] IPI cpu=3D0 irq=3D129 vector=3DCALL_FUNCTION_VECTOR (1) > > Event-channel device installed. > > random: > > io: > > mem: > > Pentium Pro MTRR support enabled > > null: > > nfslock: pseudo-device > > [XEN] xen_rtc_probe: probing Hypervisor RTC clock > > rtc0: on motherboard > > [XEN] xen_rtc_attach: attaching Hypervisor RTC clock > > rtc0: registered as a time-of-day clock (resolution 1000000us, > > adjustment 0.500000000s) > > xenstore0: on motherboard > > Grant table initialized > > xc0: on motherboard > > Device configuration finished. > > procfs registered > > Event timer "ixen" quality 600 > > Timecounters tick every 10.000 msec > > lo0: bpf attached > > xenbusb_front0: on xenstore0 > > xenbusb_add_device: Device device/suspend/event-channel ignored. State = 6 > > xn0: at device/vif/0 on xenbusb_front0 > > xn0: bpf attached > > xn0: Ethernet address: 00:16:3e:44:b1:b9 > > xenbusb_back0: on xenstore0 > > xctrl0: on xenstore0 > > xn0: backend features: feature-sg feature-gso-tcp4 > > [XEN] hypervisor wallclock nudged; nudging TOD. > > run_interrupt_driven_hooks: still waiting after 60 seconds for > > xenbus_free_evtchn > > [XEN] hypervisor wallclock nudged; nudging TOD. > > run_interrupt_driven_hooks: still waiting after 120 seconds for > > xenbus_free_evtchn > > run_interrupt_driven_hooks: still waiting after 180 seconds for > > xenbus_free_evtchn > > run_interrupt_driven_hooks: still waiting after 240 seconds for > > xenbus_free_evtchn > > run_interrupt_driven_hooks: still waiting after 300 seconds for > > xenbus_free_evtchn > > [XEN] hypervisor wallclock nudged; nudging TOD. > > [XEN] hypervisor wallclock nudged; nudging TOD. > > [XEN] hypervisor wallclock nudged; nudging TOD. > > > > I will test HVM and PVHVM but in the past I had no problems with this. > > It would be greate to have pure PV mode. The only thing which confuses > > me is the libxl related error on the domain creation: > > > > Parsing config from /root/xen/freebsd-test.cfg > > libxl: error: libxl_dm.c:1212:device_model_spawn_outcome: domain 20 > > device model: spawn failed (rc=3D-3) > > libxl: error: libxl_qmp.c:641:libxl__qmp_initialize: Connection error: > > No such file or directory > > > > I know that in a few cases PV guests have QEmu process but I can not sa= y > > while this failes. Eventually there is something not compiled in, into > > Xen or the toolstack? > > PV guests use Qemu to provide a block backend for raw file images, so if > Qemu fails to start your PV guest won't we able to access the hard > drive, that could be the reason why the FreeBSD PV guest is unable to > boot. Could you check Qemu log in /var/log/xen/qemu-dm-freebsd.log? > > > > > I saw that you have made a talk on FOSDEM about BSD and PVH. I > > downloaded the slide PDF but I am not able to open the document. It say= s > > that the document is corrupted. Am I doing a mistake? Or is there a > > problem with the document on the FOSDEM page. > > I've just checked and the slides look OK to me, I'm able to open them > without problems. SHA1 sum: > > 0b0070149e0b4cf0b5557230793acccd1291ccde new_xen_paravirt_mode.pdf > > --20cf3074b36ab1bf1004d6688fb4 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
I was able to fix the Qemu problem. I = simply had to install a dependency which was needed by Qemu. The problem do= esn't appeared earlier because the Linux PV guests seem to need no qemu= . I think it's related to the disk notation which is used there (xvda) = so kernel xen block driver is used and in the FreeBSD case (hda) so the IDE= emulation of qemu is used.

I am now have trouble to boot the guest with PV-GRUB. So I have a ZFS d= isk and I searched on the web and found this on GitHub: https://github.com/aszeszo/pv-grub

It's PV-GRUB with ZFS and it can read the disk but I can not boot= . The first thing is how can I cross compile a single component in the Xen = build system to get a 32bit variant and not a 64bit variant as yet?

And can I load FreeBSD with GRUB actually? I saw that Chainloadin= g would be needed so I would have to boot the loader or zfsloader with GRUB= but this failes with the following error:

xc: error: panic: xc_dom_= core.c:587: xc_dom_find_loader: no loader found: Invalid kernel
xc_dom_parse_image returned -1
close(3)

Error 9: Unknown boot fai= lure


So would be great when there can be found a solution = for this problem.

Best Regards


2013/2/23 Roger Pau Monn=E9 <roger.p= au@citrix.com>
On 22/02/13 19:30, tech mailinglist= s wrote:
> Hello Roger,
>
>
> I tried a further thing in the kernel configuration. I remove the opti= on
> KBD_INSTALL_CDEV and now I am no longer getting dropped to a minimal > console. The boot now looks like this:
>
> Parsing config from /root/xen/freebsd-test.cfg
> libxl: error: libxl_dm.c:1212:device_model_spawn_outcome: domain 20 > device model: spawn failed (rc=3D-3)
> libxl: error: libxl_qmp.c:641:libxl__qmp_initialize: Connection error:=
> No such file or directory
> Daemon running with PID 4383
> WARNING: loader(8) metadata is missing!
> GDB: no debug ports present
> KDB: debugger backends: ddb
> KDB: current backend: ddb
> APIC: Using the MPTable enumerator.
> SMP: Added CPU 0 (BSP)
> Copyright (c) 1992-2012 The FreeBSD Project.
> Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 19= 94
> =A0 =A0 =A0 =A0 The Regents of the University of California. All right= s reserved.
> FreeBSD is a registered trademark of The FreeBSD Foundation.
> FreeBSD 9.1-RELEASE #1 r247145M: Fri Feb 22 18:26:55 CET 2013
> =A0 =A0 root@build:/usr/obj/usr/src/sys/XEN i386
> Xen reported: 3341.754 MHz processor.
> Timecounter "ixen" frequency 1953125 Hz quality 0
> CPU: Intel(R) Core(TM) i7 CPU =A0 =A0 =A0 =A0 975 =A0@ 3.33GHz (3341.7= 5-MHz
> 686-class CPU)
> =A0 Origin =3D "GenuineIntel" =A0Id =3D 0x106a5 =A0Family = =3D 6 =A0Model =3D 1a
> Stepping =3D 5
>
> Features=3D0xbfe3fbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,M= TRR,PGE,MCA,CMOV,PAT,PSE36,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE>
>
> Features2=3D0x98e3bd<SSE3,DTES64,MON,DS_CPL,VMX,EST,TM2,SSSE3,CX16,= xTPR,PDCM,SSE4.1,SSE4.2,POPCNT>
> =A0 AMD Features=3D0x28100000<NX,RDTSCP,LM>
> =A0 AMD Features2=3D0x1<LAHF>
>
> Data TLB: 4 KB pages, 4-way set associative, 64 entries
> 1st-level data cache: 32 KB, 8-way set associative, 64 byte line size<= br> > L2 cache: 256 kbytes, 8-way associative, 64 bytes/line
> real memory =A0=3D 536870912 (512 MB)
> Physical memory chunk(s):
> 0x0000000000670000 - 0x000000001f628fff, 519802880 bytes (126905 pages= )
> avail memory =3D 516833280 (492 MB)
> INTR: Adding local APIC 0 as a target
> ULE: setup cpu 0
> [XEN] IPI cpu=3D0 irq=3D128 vector=3DRESCHEDULE_VECTOR (0)
> [XEN] IPI cpu=3D0 irq=3D129 vector=3DCALL_FUNCTION_VECTOR (1)
> Event-channel device installed.
> random: <entropy source, Software, Yarrow>
> io: <I/O>
> mem: <memory>
> Pentium Pro MTRR support enabled
> null: <null device, zero device>
> nfslock: pseudo-device
> [XEN] xen_rtc_probe: probing Hypervisor RTC clock
> rtc0: <Xen Hypervisor Clock> on motherboard
> [XEN] xen_rtc_attach: attaching Hypervisor RTC clock
> rtc0: registered as a time-of-day clock (resolution 1000000us,
> adjustment 0.500000000s)
> xenstore0: <XenStore> on motherboard
> Grant table initialized
> xc0: <Xen Console> on motherboard
> Device configuration finished.
> procfs registered
> Event timer "ixen" quality 600
> Timecounters tick every 10.000 msec
> lo0: bpf attached
> xenbusb_front0: <Xen Frontend Devices> on xenstore0
> xenbusb_add_device: Device device/suspend/event-channel ignored. State= 6
> xn0: <Virtual Network Interface> at device/vif/0 on xenbusb_fron= t0
> xn0: bpf attached
> xn0: Ethernet address: 00:16:3e:44:b1:b9
> xenbusb_back0: <Xen Backend Devices> on xenstore0
> xctrl0: <Xen Control Device> on xenstore0
> xn0: backend features: feature-sg feature-gso-tcp4
> [XEN] hypervisor wallclock nudged; nudging TOD.
> run_interrupt_driven_hooks: still waiting after 60 seconds for
> xenbus_free_evtchn
> [XEN] hypervisor wallclock nudged; nudging TOD.
> run_interrupt_driven_hooks: still waiting after 120 seconds for
> xenbus_free_evtchn
> run_interrupt_driven_hooks: still waiting after 180 seconds for
> xenbus_free_evtchn
> run_interrupt_driven_hooks: still waiting after 240 seconds for
> xenbus_free_evtchn
> run_interrupt_driven_hooks: still waiting after 300 seconds for
> xenbus_free_evtchn
> [XEN] hypervisor wallclock nudged; nudging TOD.
> [XEN] hypervisor wallclock nudged; nudging TOD.
> [XEN] hypervisor wallclock nudged; nudging TOD.
>
> I will test HVM and PVHVM but in the past I had no problems with this.=
> It would be greate to have pure PV mode. The only thing which confuses=
> me is the libxl related error on the domain creation:
>
> Parsing config from /root/xen/freebsd-test.cfg
> libxl: error: libxl_dm.c:1212:device_model_spawn_outcome: domain 20 > device model: spawn failed (rc=3D-3)
> libxl: error: libxl_qmp.c:641:libxl__qmp_initialize: Connection error:=
> No such file or directory
>
> I know that in a few cases PV guests have QEmu process but I can not s= ay
> while this failes. Eventually there is something not compiled in, into=
> Xen or the toolstack?

PV guests use Qemu to provide a block backend for raw file imag= es, so if
Qemu fails to start your PV guest won't we able to access the hard
drive, that could be the reason why the FreeBSD PV guest is unable to
boot. Could you check Qemu log in /var/log/xen/qemu-dm-freebsd.log?

>
> I saw that you have made a talk on FOSDEM about BSD and PVH. I
> downloaded the slide PDF but I am not able to open the document. It sa= ys
> that the document is corrupted. Am I doing a mistake? Or is there a > problem with the document on the FOSDEM page.

I've just checked and the slides look OK to me, I'm able to o= pen them
without problems. SHA1 sum:

0b0070149e0b4cf0b5557230793acccd1291ccde =A0new_xen_paravirt_mode.pdf


--20cf3074b36ab1bf1004d6688fb4-- --===============6248004445428048175== 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 --===============6248004445428048175==-- From xen-users-bounces@lists.xen.org Sat Feb 23 18:36:23 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sat, 23 Feb 2013 18:36: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 1U9Jvr-00083i-UE; Sat, 23 Feb 2013 18:34:47 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U9Jvq-00083d-Cj for xen-users@lists.xen.org; Sat, 23 Feb 2013 18:34:46 +0000 Received: from [85.158.143.99:27103] by server-3.bemta-4.messagelabs.com id E7/66-02186-5CB09215; Sat, 23 Feb 2013 18:34:45 +0000 X-Env-Sender: mailinglists.tech@gmail.com X-Msg-Ref: server-2.tower-216.messagelabs.com!1361644482!22039612!1 X-Originating-IP: [209.85.216.47] 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.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 28035 invoked from network); 23 Feb 2013 18:34:43 -0000 Received: from mail-qa0-f47.google.com (HELO mail-qa0-f47.google.com) (209.85.216.47) by server-2.tower-216.messagelabs.com with RC4-SHA encrypted SMTP; 23 Feb 2013 18:34:43 -0000 Received: by mail-qa0-f47.google.com with SMTP id j8so918607qah.20 for ; Sat, 23 Feb 2013 10:34:42 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=dQ6x8H+asmEjTEnGgt4p9JoyP1jAyPoUFfS+pSb7v0A=; b=r6Bh/jOng/RX2W0ejG2PBvQJv2XB5HP3yhlG2vu4znSiwIZazGJh5/AhLlqjbR5OJX 5c18QpJOyksXfiu0ZEptyyJEL+4K1jJeGDCmOybhgNBHBqM9kxcasFXzuAQstTeNow5n BcddGcrZxII6yWw5yirzuyVgt7Q3kmAJG5WIZFYA01bXkaAQVVqSlU9x7/t+9v9YpgWI yjIsNErH45RgEpt2UbY23nYSWaYReqEhep9kwDh0JNzjHETgme9UvypTRdGui3lpXc5T dkWfSrusylZhK5N4uo/IWXqx5g2Vh/dJQqX21wVihJHEQcZkFJEXGmEj6KT2sdvraJyA F8MQ== MIME-Version: 1.0 X-Received: by 10.224.108.74 with SMTP id e10mr3613157qap.83.1361644482573; Sat, 23 Feb 2013 10:34:42 -0800 (PST) Received: by 10.49.110.70 with HTTP; Sat, 23 Feb 2013 10:34:42 -0800 (PST) In-Reply-To: <51287A18.7040200@citrix.com> References: <51279FA1.2090809@citrix.com> <51287A18.7040200@citrix.com> Date: Sat, 23 Feb 2013 19:34:42 +0100 Message-ID: From: tech mailinglists To: =?ISO-8859-1?Q?Roger_Pau_Monn=E9?= Cc: xen-users , "freebsd-xen@lists.freebsd.org" Subject: Re: [Xen-users] Trouble booting FreeBSD i386 PV 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="===============6248004445428048175==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============6248004445428048175== Content-Type: multipart/alternative; boundary=20cf3074b36ab1bf1004d6688fb4 --20cf3074b36ab1bf1004d6688fb4 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable I was able to fix the Qemu problem. I simply had to install a dependency which was needed by Qemu. The problem doesn't appeared earlier because the Linux PV guests seem to need no qemu. I think it's related to the disk notation which is used there (xvda) so kernel xen block driver is used and in the FreeBSD case (hda) so the IDE emulation of qemu is used. I am now have trouble to boot the guest with PV-GRUB. So I have a ZFS disk and I searched on the web and found this on GitHub: https://github.com/aszeszo/pv-grub It's PV-GRUB with ZFS and it can read the disk but I can not boot. The first thing is how can I cross compile a single component in the Xen build system to get a 32bit variant and not a 64bit variant as yet? And can I load FreeBSD with GRUB actually? I saw that Chainloading would be needed so I would have to boot the loader or zfsloader with GRUB but this failes with the following error: xc: error: panic: xc_dom_core.c:587: xc_dom_find_loader: no loader found: Invalid kernel xc_dom_parse_image returned -1 close(3) Error 9: Unknown boot failure So would be great when there can be found a solution for this problem. Best Regards 2013/2/23 Roger Pau Monn=E9 > On 22/02/13 19:30, tech mailinglists wrote: > > Hello Roger, > > > > > > I tried a further thing in the kernel configuration. I remove the optio= n > > KBD_INSTALL_CDEV and now I am no longer getting dropped to a minimal > > console. The boot now looks like this: > > > > Parsing config from /root/xen/freebsd-test.cfg > > libxl: error: libxl_dm.c:1212:device_model_spawn_outcome: domain 20 > > device model: spawn failed (rc=3D-3) > > libxl: error: libxl_qmp.c:641:libxl__qmp_initialize: Connection error: > > No such file or directory > > Daemon running with PID 4383 > > WARNING: loader(8) metadata is missing! > > GDB: no debug ports present > > KDB: debugger backends: ddb > > KDB: current backend: ddb > > APIC: Using the MPTable enumerator. > > SMP: Added CPU 0 (BSP) > > Copyright (c) 1992-2012 The FreeBSD Project. > > Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 199= 4 > > The Regents of the University of California. All rights reserve= d. > > FreeBSD is a registered trademark of The FreeBSD Foundation. > > FreeBSD 9.1-RELEASE #1 r247145M: Fri Feb 22 18:26:55 CET 2013 > > root@build:/usr/obj/usr/src/sys/XEN i386 > > Xen reported: 3341.754 MHz processor. > > Timecounter "ixen" frequency 1953125 Hz quality 0 > > CPU: Intel(R) Core(TM) i7 CPU 975 @ 3.33GHz (3341.75-MHz > > 686-class CPU) > > Origin =3D "GenuineIntel" Id =3D 0x106a5 Family =3D 6 Model =3D 1a > > Stepping =3D 5 > > > > > Features=3D0xbfe3fbff > > > > > Features2=3D0x98e3bd > > AMD Features=3D0x28100000 > > AMD Features2=3D0x1 > > > > Data TLB: 4 KB pages, 4-way set associative, 64 entries > > 1st-level data cache: 32 KB, 8-way set associative, 64 byte line size > > L2 cache: 256 kbytes, 8-way associative, 64 bytes/line > > real memory =3D 536870912 (512 MB) > > Physical memory chunk(s): > > 0x0000000000670000 - 0x000000001f628fff, 519802880 bytes (126905 pages) > > avail memory =3D 516833280 (492 MB) > > INTR: Adding local APIC 0 as a target > > ULE: setup cpu 0 > > [XEN] IPI cpu=3D0 irq=3D128 vector=3DRESCHEDULE_VECTOR (0) > > [XEN] IPI cpu=3D0 irq=3D129 vector=3DCALL_FUNCTION_VECTOR (1) > > Event-channel device installed. > > random: > > io: > > mem: > > Pentium Pro MTRR support enabled > > null: > > nfslock: pseudo-device > > [XEN] xen_rtc_probe: probing Hypervisor RTC clock > > rtc0: on motherboard > > [XEN] xen_rtc_attach: attaching Hypervisor RTC clock > > rtc0: registered as a time-of-day clock (resolution 1000000us, > > adjustment 0.500000000s) > > xenstore0: on motherboard > > Grant table initialized > > xc0: on motherboard > > Device configuration finished. > > procfs registered > > Event timer "ixen" quality 600 > > Timecounters tick every 10.000 msec > > lo0: bpf attached > > xenbusb_front0: on xenstore0 > > xenbusb_add_device: Device device/suspend/event-channel ignored. State = 6 > > xn0: at device/vif/0 on xenbusb_front0 > > xn0: bpf attached > > xn0: Ethernet address: 00:16:3e:44:b1:b9 > > xenbusb_back0: on xenstore0 > > xctrl0: on xenstore0 > > xn0: backend features: feature-sg feature-gso-tcp4 > > [XEN] hypervisor wallclock nudged; nudging TOD. > > run_interrupt_driven_hooks: still waiting after 60 seconds for > > xenbus_free_evtchn > > [XEN] hypervisor wallclock nudged; nudging TOD. > > run_interrupt_driven_hooks: still waiting after 120 seconds for > > xenbus_free_evtchn > > run_interrupt_driven_hooks: still waiting after 180 seconds for > > xenbus_free_evtchn > > run_interrupt_driven_hooks: still waiting after 240 seconds for > > xenbus_free_evtchn > > run_interrupt_driven_hooks: still waiting after 300 seconds for > > xenbus_free_evtchn > > [XEN] hypervisor wallclock nudged; nudging TOD. > > [XEN] hypervisor wallclock nudged; nudging TOD. > > [XEN] hypervisor wallclock nudged; nudging TOD. > > > > I will test HVM and PVHVM but in the past I had no problems with this. > > It would be greate to have pure PV mode. The only thing which confuses > > me is the libxl related error on the domain creation: > > > > Parsing config from /root/xen/freebsd-test.cfg > > libxl: error: libxl_dm.c:1212:device_model_spawn_outcome: domain 20 > > device model: spawn failed (rc=3D-3) > > libxl: error: libxl_qmp.c:641:libxl__qmp_initialize: Connection error: > > No such file or directory > > > > I know that in a few cases PV guests have QEmu process but I can not sa= y > > while this failes. Eventually there is something not compiled in, into > > Xen or the toolstack? > > PV guests use Qemu to provide a block backend for raw file images, so if > Qemu fails to start your PV guest won't we able to access the hard > drive, that could be the reason why the FreeBSD PV guest is unable to > boot. Could you check Qemu log in /var/log/xen/qemu-dm-freebsd.log? > > > > > I saw that you have made a talk on FOSDEM about BSD and PVH. I > > downloaded the slide PDF but I am not able to open the document. It say= s > > that the document is corrupted. Am I doing a mistake? Or is there a > > problem with the document on the FOSDEM page. > > I've just checked and the slides look OK to me, I'm able to open them > without problems. SHA1 sum: > > 0b0070149e0b4cf0b5557230793acccd1291ccde new_xen_paravirt_mode.pdf > > --20cf3074b36ab1bf1004d6688fb4 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
I was able to fix the Qemu problem. I = simply had to install a dependency which was needed by Qemu. The problem do= esn't appeared earlier because the Linux PV guests seem to need no qemu= . I think it's related to the disk notation which is used there (xvda) = so kernel xen block driver is used and in the FreeBSD case (hda) so the IDE= emulation of qemu is used.

I am now have trouble to boot the guest with PV-GRUB. So I have a ZFS d= isk and I searched on the web and found this on GitHub: https://github.com/aszeszo/pv-grub

It's PV-GRUB with ZFS and it can read the disk but I can not boot= . The first thing is how can I cross compile a single component in the Xen = build system to get a 32bit variant and not a 64bit variant as yet?

And can I load FreeBSD with GRUB actually? I saw that Chainloadin= g would be needed so I would have to boot the loader or zfsloader with GRUB= but this failes with the following error:

xc: error: panic: xc_dom_= core.c:587: xc_dom_find_loader: no loader found: Invalid kernel
xc_dom_parse_image returned -1
close(3)

Error 9: Unknown boot fai= lure


So would be great when there can be found a solution = for this problem.

Best Regards


2013/2/23 Roger Pau Monn=E9 <roger.p= au@citrix.com>
On 22/02/13 19:30, tech mailinglist= s wrote:
> Hello Roger,
>
>
> I tried a further thing in the kernel configuration. I remove the opti= on
> KBD_INSTALL_CDEV and now I am no longer getting dropped to a minimal > console. The boot now looks like this:
>
> Parsing config from /root/xen/freebsd-test.cfg
> libxl: error: libxl_dm.c:1212:device_model_spawn_outcome: domain 20 > device model: spawn failed (rc=3D-3)
> libxl: error: libxl_qmp.c:641:libxl__qmp_initialize: Connection error:=
> No such file or directory
> Daemon running with PID 4383
> WARNING: loader(8) metadata is missing!
> GDB: no debug ports present
> KDB: debugger backends: ddb
> KDB: current backend: ddb
> APIC: Using the MPTable enumerator.
> SMP: Added CPU 0 (BSP)
> Copyright (c) 1992-2012 The FreeBSD Project.
> Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 19= 94
> =A0 =A0 =A0 =A0 The Regents of the University of California. All right= s reserved.
> FreeBSD is a registered trademark of The FreeBSD Foundation.
> FreeBSD 9.1-RELEASE #1 r247145M: Fri Feb 22 18:26:55 CET 2013
> =A0 =A0 root@build:/usr/obj/usr/src/sys/XEN i386
> Xen reported: 3341.754 MHz processor.
> Timecounter "ixen" frequency 1953125 Hz quality 0
> CPU: Intel(R) Core(TM) i7 CPU =A0 =A0 =A0 =A0 975 =A0@ 3.33GHz (3341.7= 5-MHz
> 686-class CPU)
> =A0 Origin =3D "GenuineIntel" =A0Id =3D 0x106a5 =A0Family = =3D 6 =A0Model =3D 1a
> Stepping =3D 5
>
> Features=3D0xbfe3fbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,M= TRR,PGE,MCA,CMOV,PAT,PSE36,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE>
>
> Features2=3D0x98e3bd<SSE3,DTES64,MON,DS_CPL,VMX,EST,TM2,SSSE3,CX16,= xTPR,PDCM,SSE4.1,SSE4.2,POPCNT>
> =A0 AMD Features=3D0x28100000<NX,RDTSCP,LM>
> =A0 AMD Features2=3D0x1<LAHF>
>
> Data TLB: 4 KB pages, 4-way set associative, 64 entries
> 1st-level data cache: 32 KB, 8-way set associative, 64 byte line size<= br> > L2 cache: 256 kbytes, 8-way associative, 64 bytes/line
> real memory =A0=3D 536870912 (512 MB)
> Physical memory chunk(s):
> 0x0000000000670000 - 0x000000001f628fff, 519802880 bytes (126905 pages= )
> avail memory =3D 516833280 (492 MB)
> INTR: Adding local APIC 0 as a target
> ULE: setup cpu 0
> [XEN] IPI cpu=3D0 irq=3D128 vector=3DRESCHEDULE_VECTOR (0)
> [XEN] IPI cpu=3D0 irq=3D129 vector=3DCALL_FUNCTION_VECTOR (1)
> Event-channel device installed.
> random: <entropy source, Software, Yarrow>
> io: <I/O>
> mem: <memory>
> Pentium Pro MTRR support enabled
> null: <null device, zero device>
> nfslock: pseudo-device
> [XEN] xen_rtc_probe: probing Hypervisor RTC clock
> rtc0: <Xen Hypervisor Clock> on motherboard
> [XEN] xen_rtc_attach: attaching Hypervisor RTC clock
> rtc0: registered as a time-of-day clock (resolution 1000000us,
> adjustment 0.500000000s)
> xenstore0: <XenStore> on motherboard
> Grant table initialized
> xc0: <Xen Console> on motherboard
> Device configuration finished.
> procfs registered
> Event timer "ixen" quality 600
> Timecounters tick every 10.000 msec
> lo0: bpf attached
> xenbusb_front0: <Xen Frontend Devices> on xenstore0
> xenbusb_add_device: Device device/suspend/event-channel ignored. State= 6
> xn0: <Virtual Network Interface> at device/vif/0 on xenbusb_fron= t0
> xn0: bpf attached
> xn0: Ethernet address: 00:16:3e:44:b1:b9
> xenbusb_back0: <Xen Backend Devices> on xenstore0
> xctrl0: <Xen Control Device> on xenstore0
> xn0: backend features: feature-sg feature-gso-tcp4
> [XEN] hypervisor wallclock nudged; nudging TOD.
> run_interrupt_driven_hooks: still waiting after 60 seconds for
> xenbus_free_evtchn
> [XEN] hypervisor wallclock nudged; nudging TOD.
> run_interrupt_driven_hooks: still waiting after 120 seconds for
> xenbus_free_evtchn
> run_interrupt_driven_hooks: still waiting after 180 seconds for
> xenbus_free_evtchn
> run_interrupt_driven_hooks: still waiting after 240 seconds for
> xenbus_free_evtchn
> run_interrupt_driven_hooks: still waiting after 300 seconds for
> xenbus_free_evtchn
> [XEN] hypervisor wallclock nudged; nudging TOD.
> [XEN] hypervisor wallclock nudged; nudging TOD.
> [XEN] hypervisor wallclock nudged; nudging TOD.
>
> I will test HVM and PVHVM but in the past I had no problems with this.=
> It would be greate to have pure PV mode. The only thing which confuses=
> me is the libxl related error on the domain creation:
>
> Parsing config from /root/xen/freebsd-test.cfg
> libxl: error: libxl_dm.c:1212:device_model_spawn_outcome: domain 20 > device model: spawn failed (rc=3D-3)
> libxl: error: libxl_qmp.c:641:libxl__qmp_initialize: Connection error:=
> No such file or directory
>
> I know that in a few cases PV guests have QEmu process but I can not s= ay
> while this failes. Eventually there is something not compiled in, into=
> Xen or the toolstack?

PV guests use Qemu to provide a block backend for raw file imag= es, so if
Qemu fails to start your PV guest won't we able to access the hard
drive, that could be the reason why the FreeBSD PV guest is unable to
boot. Could you check Qemu log in /var/log/xen/qemu-dm-freebsd.log?

>
> I saw that you have made a talk on FOSDEM about BSD and PVH. I
> downloaded the slide PDF but I am not able to open the document. It sa= ys
> that the document is corrupted. Am I doing a mistake? Or is there a > problem with the document on the FOSDEM page.

I've just checked and the slides look OK to me, I'm able to o= pen them
without problems. SHA1 sum:

0b0070149e0b4cf0b5557230793acccd1291ccde =A0new_xen_paravirt_mode.pdf


--20cf3074b36ab1bf1004d6688fb4-- --===============6248004445428048175== 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 --===============6248004445428048175==-- From xen-users-bounces@lists.xen.org Sat Feb 23 21:26:55 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sat, 23 Feb 2013 21:26: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 1U9MbL-0003L7-Hk; Sat, 23 Feb 2013 21:25:47 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U96aw-0001hs-GY for xen-users@lists.xen.org; Sat, 23 Feb 2013 04:20:18 +0000 Received: from [193.109.254.147:30295] by server-1.bemta-14.messagelabs.com id 18/5F-29874-18348215; Sat, 23 Feb 2013 04:20:17 +0000 X-Env-Sender: ydev@cs.utah.edu X-Msg-Ref: server-15.tower-27.messagelabs.com!1361593216!2469688!1 X-Originating-IP: [155.98.64.241] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 16681 invoked from network); 23 Feb 2013 04:20:16 -0000 Received: from rio.cs.utah.edu (HELO mail-svr1.cs.utah.edu) (155.98.64.241) by server-15.tower-27.messagelabs.com with SMTP; 23 Feb 2013 04:20:16 -0000 Received: from localhost (localhost [127.0.0.1]) by mail-svr1.cs.utah.edu (Postfix) with ESMTP id 7EBB16500D0 for ; Fri, 22 Feb 2013 21:20:15 -0700 (MST) X-Virus-Scanned: amavisd-new at cs.utah.edu Received: from mail-svr1.cs.utah.edu ([127.0.0.1]) by localhost (mail-svr1.cs.utah.edu [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BCoFiL0YpiXN; Fri, 22 Feb 2013 21:20:15 -0700 (MST) Received: from [192.168.1.40] (c-76-23-15-81.hsd1.ut.comcast.net [76.23.15.81]) by smtps.cs.utah.edu (Postfix) with ESMTPSA id EA2DF6500B9; Fri, 22 Feb 2013 21:20:14 -0700 (MST) Message-ID: <51284379.3070608@cs.utah.edu> Date: Fri, 22 Feb 2013 21:20:09 -0700 From: Yathindra User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130215 Thunderbird/17.0.3 MIME-Version: 1.0 To: "xen-users@lists.xen.org" References: <5125DCBB.2080305@cs.utah.edu> In-Reply-To: <5125DCBB.2080305@cs.utah.edu> X-Mailman-Approved-At: Sat, 23 Feb 2013 21:25:44 +0000 Cc: Yathindra Naik Subject: Re: [Xen-users] Issuing hypercalls from Linux 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: , 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 2/21/2013 1:37 AM, Yathindra wrote: > Hi, > > I have defined a new hypercall in Xen hypervisor. It is similar to > do_domctl() > in that I pass a single argument and use XEN_GUEST_HANDLE() to > retrieve the > arguments. Its currently working fine under Xen-4.3-unstable. > > Now I want to invoke this hypercall via Linux-3.7.5 Guest. How do I go > about > doing this. > > Thanks, > Yathi Hi, I followed a approach similar to do_physdev_op in Linux-3.7.5. I have a similar set of files under include/xen/interface/ directory. After plumbing everything when I execute my hypercall via Linux, I get -14 (EFAULT) as the return value. I added printk's on the Xen side to see if the hypercall is reaching Xen but it does not. Any general direction regarding this would be very helpful. Thanks, Yathi _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Sat Feb 23 21:26:55 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sat, 23 Feb 2013 21:26: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 1U9MbL-0003L7-Hk; Sat, 23 Feb 2013 21:25:47 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U96aw-0001hs-GY for xen-users@lists.xen.org; Sat, 23 Feb 2013 04:20:18 +0000 Received: from [193.109.254.147:30295] by server-1.bemta-14.messagelabs.com id 18/5F-29874-18348215; Sat, 23 Feb 2013 04:20:17 +0000 X-Env-Sender: ydev@cs.utah.edu X-Msg-Ref: server-15.tower-27.messagelabs.com!1361593216!2469688!1 X-Originating-IP: [155.98.64.241] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 16681 invoked from network); 23 Feb 2013 04:20:16 -0000 Received: from rio.cs.utah.edu (HELO mail-svr1.cs.utah.edu) (155.98.64.241) by server-15.tower-27.messagelabs.com with SMTP; 23 Feb 2013 04:20:16 -0000 Received: from localhost (localhost [127.0.0.1]) by mail-svr1.cs.utah.edu (Postfix) with ESMTP id 7EBB16500D0 for ; Fri, 22 Feb 2013 21:20:15 -0700 (MST) X-Virus-Scanned: amavisd-new at cs.utah.edu Received: from mail-svr1.cs.utah.edu ([127.0.0.1]) by localhost (mail-svr1.cs.utah.edu [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BCoFiL0YpiXN; Fri, 22 Feb 2013 21:20:15 -0700 (MST) Received: from [192.168.1.40] (c-76-23-15-81.hsd1.ut.comcast.net [76.23.15.81]) by smtps.cs.utah.edu (Postfix) with ESMTPSA id EA2DF6500B9; Fri, 22 Feb 2013 21:20:14 -0700 (MST) Message-ID: <51284379.3070608@cs.utah.edu> Date: Fri, 22 Feb 2013 21:20:09 -0700 From: Yathindra User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130215 Thunderbird/17.0.3 MIME-Version: 1.0 To: "xen-users@lists.xen.org" References: <5125DCBB.2080305@cs.utah.edu> In-Reply-To: <5125DCBB.2080305@cs.utah.edu> X-Mailman-Approved-At: Sat, 23 Feb 2013 21:25:44 +0000 Cc: Yathindra Naik Subject: Re: [Xen-users] Issuing hypercalls from Linux 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: , 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 2/21/2013 1:37 AM, Yathindra wrote: > Hi, > > I have defined a new hypercall in Xen hypervisor. It is similar to > do_domctl() > in that I pass a single argument and use XEN_GUEST_HANDLE() to > retrieve the > arguments. Its currently working fine under Xen-4.3-unstable. > > Now I want to invoke this hypercall via Linux-3.7.5 Guest. How do I go > about > doing this. > > Thanks, > Yathi Hi, I followed a approach similar to do_physdev_op in Linux-3.7.5. I have a similar set of files under include/xen/interface/ directory. After plumbing everything when I execute my hypercall via Linux, I get -14 (EFAULT) as the return value. I added printk's on the Xen side to see if the hypercall is reaching Xen but it does not. Any general direction regarding this would be very helpful. Thanks, Yathi _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Sat Feb 23 21:26:55 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sat, 23 Feb 2013 21:26: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 1U9MbK-0003Ky-UD; Sat, 23 Feb 2013 21:25:46 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U90C4-0001xt-UK for xen-users@lists.xensource.com; Fri, 22 Feb 2013 21:30:13 +0000 Received: from [193.109.254.147:59105] by server-5.bemta-14.messagelabs.com id E6/83-21539-463E7215; Fri, 22 Feb 2013 21:30:12 +0000 X-Env-Sender: turbo124@gmail.com X-Msg-Ref: server-2.tower-27.messagelabs.com!1361568609!8692240!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.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 8625 invoked from network); 22 Feb 2013 21:30:10 -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; 22 Feb 2013 21:30:10 -0000 Received: from [192.168.236.26] (helo=sam.nabble.com) by sam.nabble.com with esmtp (Exim 4.72) (envelope-from ) id 1U90C0-00020u-J7 for xen-users@lists.xensource.com; Fri, 22 Feb 2013 13:30:08 -0800 Date: Fri, 22 Feb 2013 13:30:08 -0800 (PST) From: turbo124 To: xen-users@lists.xensource.com Message-ID: <1361568608559-5714392.post@n5.nabble.com> In-Reply-To: <4F385393.4040709@skow.net> References: <4F385393.4040709@skow.net> MIME-Version: 1.0 X-Mailman-Approved-At: Sat, 23 Feb 2013 21:25:44 +0000 Subject: Re: [Xen-users] Announcement: Xen Cloud Control System X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: 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 Vern, Would you like help with this project? We would be happy to assist in building on the work you have done. -- View this message in context: http://xen.1045712.n5.nabble.com/Announcement-Xen-Cloud-Control-System-tp5477835p5714392.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 Feb 23 21:26:55 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sat, 23 Feb 2013 21:26: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 1U9MbK-0003Ky-UD; Sat, 23 Feb 2013 21:25:46 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U90C4-0001xt-UK for xen-users@lists.xensource.com; Fri, 22 Feb 2013 21:30:13 +0000 Received: from [193.109.254.147:59105] by server-5.bemta-14.messagelabs.com id E6/83-21539-463E7215; Fri, 22 Feb 2013 21:30:12 +0000 X-Env-Sender: turbo124@gmail.com X-Msg-Ref: server-2.tower-27.messagelabs.com!1361568609!8692240!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.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 8625 invoked from network); 22 Feb 2013 21:30:10 -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; 22 Feb 2013 21:30:10 -0000 Received: from [192.168.236.26] (helo=sam.nabble.com) by sam.nabble.com with esmtp (Exim 4.72) (envelope-from ) id 1U90C0-00020u-J7 for xen-users@lists.xensource.com; Fri, 22 Feb 2013 13:30:08 -0800 Date: Fri, 22 Feb 2013 13:30:08 -0800 (PST) From: turbo124 To: xen-users@lists.xensource.com Message-ID: <1361568608559-5714392.post@n5.nabble.com> In-Reply-To: <4F385393.4040709@skow.net> References: <4F385393.4040709@skow.net> MIME-Version: 1.0 X-Mailman-Approved-At: Sat, 23 Feb 2013 21:25:44 +0000 Subject: Re: [Xen-users] Announcement: Xen Cloud Control System X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: 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 Vern, Would you like help with this project? We would be happy to assist in building on the work you have done. -- View this message in context: http://xen.1045712.n5.nabble.com/Announcement-Xen-Cloud-Control-System-tp5477835p5714392.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 Feb 23 21:26:55 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sat, 23 Feb 2013 21:26: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 1U9MbK-0003Kp-BT; Sat, 23 Feb 2013 21:25:46 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U8ugB-0006Vn-LH for xen-users@lists.xen.org; Fri, 22 Feb 2013 15:36:55 +0000 Received: from [85.158.139.211:13684] by server-8.bemta-5.messagelabs.com id 24/04-19075-69097215; Fri, 22 Feb 2013 15:36:54 +0000 X-Env-Sender: sisakmihaly@gmail.com X-Msg-Ref: server-12.tower-206.messagelabs.com!1361547402!18172984!1 X-Originating-IP: [209.85.219.54] 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.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 24469 invoked from network); 22 Feb 2013 15:36:43 -0000 Received: from mail-oa0-f54.google.com (HELO mail-oa0-f54.google.com) (209.85.219.54) by server-12.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 22 Feb 2013 15:36:43 -0000 Received: by mail-oa0-f54.google.com with SMTP id n12so706693oag.41 for ; Fri, 22 Feb 2013 07:36:42 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:date:message-id:subject:from:to :content-type; bh=8Gz+ES176tWLY4whQu1vdX+BgkNOP2vCMwMXC3e276w=; b=FC/uNEWkt5yv2StmdxPVcsUPmvmX8NDmlHxx/Du9s9fI2fOJaLd7r97KvSUrDajAZw S+zHfMalT87ZbxIkpgxA6WQmptHx0iu6KZTM7S+j2pM6hMpFIfWiet+kWoEZGHA2M78B fLj6NedUU1jp06+ayHLGjuUHHlI7DPk1crX1nHPeAoQRn2QfmIzbZlZ1Vj4vqt7auSvN E49vd1Ap+gFQgWijyd7tM0hCfLTN2GYQD8JUzmDLs1m4tO4tBEjf0JRq+MSGF5PtEASy l+DuovJI6V/+NUG5vt7FiVOsDYjlUvbxQTR7f2bk6vmWCmkRv/+MjVI6mmQClgFY64gK gxog== MIME-Version: 1.0 X-Received: by 10.60.169.178 with SMTP id af18mr944464oec.133.1361547402123; Fri, 22 Feb 2013 07:36:42 -0800 (PST) Received: by 10.60.65.70 with HTTP; Fri, 22 Feb 2013 07:36:41 -0800 (PST) Date: Fri, 22 Feb 2013 16:36:41 +0100 Message-ID: From: =?ISO-8859-1?B?TWlo4Wx5IFNpc+Fr?= To: xen-users@lists.xen.org X-Mailman-Approved-At: Sat, 23 Feb 2013 21:25:44 +0000 Subject: [Xen-users] domU Ubuntu 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 Hi everyone, The recent release of Stream for Ubuntu made me consider a "gaming Ubuntu" domU. I would prefer gaming on GNU/Linux mainly to show my support towards "Steam for Linux". I've got one domU, a HVM Windows 7, I use it for gaming only. I passed my HD6850 to it and it works perfectly. I had a hard time configuring it but in the end I'm very satisfied with it. I supposed I could make an Ubuntu install. I read that GNU/Linux can run in PV mode for better performance but as I understand PV machines can't accept PCI passthrough. So I decided I'll use Xen HVM. First I tried Xubuntu 12.10 (I don't like Unity that much). It recognized that it was running on Xen HVM but I couldn't log in after the install. Never mind, I tried Xubuntu 12.04.2. I installed it and it looked fine without passthrough. But I couldn't managed to pass my PCI cards and video card to it. I tried it one by one, all together, with or without gfx_passthru=1 I even tried installing it with a full config file, all stuff passed to if from the very beginning. All I got when I tried to pass my graphics card was a black screen. The Windows domU works perfectly, so my system is capable of passing trough the VGA. Is there any tutorials for this stuff? I tried to Google it but I couldn't find anything. Can it be the AMD video driver for Ubuntu is missing? I'm using the HDMI output of my card. Isn't Ubuntu supposed to use a general VESA driver in this case? Am I missing something trivial? My cfg file: http://pastebin.com/brkmU7Dd Dom0: Debian testing, 3.4.14 kernel, Xen 4.2.0 release Thanks in advance for any replies, - Misi _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Sat Feb 23 21:26:55 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sat, 23 Feb 2013 21:26: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 1U9MbK-0003Kp-BT; Sat, 23 Feb 2013 21:25:46 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U8ugB-0006Vn-LH for xen-users@lists.xen.org; Fri, 22 Feb 2013 15:36:55 +0000 Received: from [85.158.139.211:13684] by server-8.bemta-5.messagelabs.com id 24/04-19075-69097215; Fri, 22 Feb 2013 15:36:54 +0000 X-Env-Sender: sisakmihaly@gmail.com X-Msg-Ref: server-12.tower-206.messagelabs.com!1361547402!18172984!1 X-Originating-IP: [209.85.219.54] 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.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 24469 invoked from network); 22 Feb 2013 15:36:43 -0000 Received: from mail-oa0-f54.google.com (HELO mail-oa0-f54.google.com) (209.85.219.54) by server-12.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 22 Feb 2013 15:36:43 -0000 Received: by mail-oa0-f54.google.com with SMTP id n12so706693oag.41 for ; Fri, 22 Feb 2013 07:36:42 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:date:message-id:subject:from:to :content-type; bh=8Gz+ES176tWLY4whQu1vdX+BgkNOP2vCMwMXC3e276w=; b=FC/uNEWkt5yv2StmdxPVcsUPmvmX8NDmlHxx/Du9s9fI2fOJaLd7r97KvSUrDajAZw S+zHfMalT87ZbxIkpgxA6WQmptHx0iu6KZTM7S+j2pM6hMpFIfWiet+kWoEZGHA2M78B fLj6NedUU1jp06+ayHLGjuUHHlI7DPk1crX1nHPeAoQRn2QfmIzbZlZ1Vj4vqt7auSvN E49vd1Ap+gFQgWijyd7tM0hCfLTN2GYQD8JUzmDLs1m4tO4tBEjf0JRq+MSGF5PtEASy l+DuovJI6V/+NUG5vt7FiVOsDYjlUvbxQTR7f2bk6vmWCmkRv/+MjVI6mmQClgFY64gK gxog== MIME-Version: 1.0 X-Received: by 10.60.169.178 with SMTP id af18mr944464oec.133.1361547402123; Fri, 22 Feb 2013 07:36:42 -0800 (PST) Received: by 10.60.65.70 with HTTP; Fri, 22 Feb 2013 07:36:41 -0800 (PST) Date: Fri, 22 Feb 2013 16:36:41 +0100 Message-ID: From: =?ISO-8859-1?B?TWlo4Wx5IFNpc+Fr?= To: xen-users@lists.xen.org X-Mailman-Approved-At: Sat, 23 Feb 2013 21:25:44 +0000 Subject: [Xen-users] domU Ubuntu 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 Hi everyone, The recent release of Stream for Ubuntu made me consider a "gaming Ubuntu" domU. I would prefer gaming on GNU/Linux mainly to show my support towards "Steam for Linux". I've got one domU, a HVM Windows 7, I use it for gaming only. I passed my HD6850 to it and it works perfectly. I had a hard time configuring it but in the end I'm very satisfied with it. I supposed I could make an Ubuntu install. I read that GNU/Linux can run in PV mode for better performance but as I understand PV machines can't accept PCI passthrough. So I decided I'll use Xen HVM. First I tried Xubuntu 12.10 (I don't like Unity that much). It recognized that it was running on Xen HVM but I couldn't log in after the install. Never mind, I tried Xubuntu 12.04.2. I installed it and it looked fine without passthrough. But I couldn't managed to pass my PCI cards and video card to it. I tried it one by one, all together, with or without gfx_passthru=1 I even tried installing it with a full config file, all stuff passed to if from the very beginning. All I got when I tried to pass my graphics card was a black screen. The Windows domU works perfectly, so my system is capable of passing trough the VGA. Is there any tutorials for this stuff? I tried to Google it but I couldn't find anything. Can it be the AMD video driver for Ubuntu is missing? I'm using the HDMI output of my card. Isn't Ubuntu supposed to use a general VESA driver in this case? Am I missing something trivial? My cfg file: http://pastebin.com/brkmU7Dd Dom0: Debian testing, 3.4.14 kernel, Xen 4.2.0 release Thanks in advance for any replies, - Misi _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Sat Feb 23 21:26:55 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sat, 23 Feb 2013 21:26: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 1U9MbJ-0003Kg-Oh; Sat, 23 Feb 2013 21:25:45 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U8pQ1-0000wy-6j for xen-users@lists.xen.org; Fri, 22 Feb 2013 09:59:53 +0000 Received: from [85.158.139.83:46790] by server-14.bemta-5.messagelabs.com id 11/40-06967-89147215; Fri, 22 Feb 2013 09:59:52 +0000 X-Env-Sender: krishansethi@curaj.ac.in X-Msg-Ref: server-12.tower-182.messagelabs.com!1361527191!28444822!1 X-Originating-IP: [209.85.217.173] X-SpamReason: No, hits=0.4 required=7.0 tests=HTML_50_60,HTML_MESSAGE, RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 7958 invoked from network); 22 Feb 2013 09:59:51 -0000 Received: from mail-lb0-f173.google.com (HELO mail-lb0-f173.google.com) (209.85.217.173) by server-12.tower-182.messagelabs.com with RC4-SHA encrypted SMTP; 22 Feb 2013 09:59:51 -0000 Received: by mail-lb0-f173.google.com with SMTP id gf7so438116lbb.18 for ; Fri, 22 Feb 2013 01:59:51 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-received:date:message-id:subject:from:to :content-type:x-gm-message-state; bh=rdyPQTwFhFsm5Wp41IJ0PEkkaBYzEHhWj1l5EPG3ZVk=; b=FodK8rvVTZvT6bQ8+J/tIJfG9Jft4wAvRK1qSrvYduK3sm0bzF1YzNBDBjYF2M8j6T /EzTAobs9vji+fsxQoPPvt6Dg5o6+0BgA6HwbQrYdCVME8I9ZvHW5MJXH7QgDS6SrJtl dcDpBfh1BsHrpBHTCDq5gpvwnwkfUZFCpXdrcWveYpgcPe+Kas91CO/lIpD6l75dTdDV fhgZzZ/ZSEsuLTNkzXsuGIidyJyzrj3yw9wp+u5AYxJkbIT0S/9vv6CQoEmy90nENAgO WiD3rGHU18sHcmThDCcBSoPiStd+U+VNEJ6QmR+UQPmlgWa4RtgOKZoKkiqUB3kVFmZn HsZQ== MIME-Version: 1.0 X-Received: by 10.152.148.133 with SMTP id ts5mr1254623lab.2.1361527191062; Fri, 22 Feb 2013 01:59:51 -0800 (PST) Received: by 10.112.100.69 with HTTP; Fri, 22 Feb 2013 01:59:50 -0800 (PST) Date: Fri, 22 Feb 2013 15:29:50 +0530 Message-ID: From: Krishan Sethi To: xen-users@lists.xen.org X-Gm-Message-State: ALoCoQlo0CufkKnOE0Pg5bIFyUDNvdct54ZTaK3RIxg5GzcAE9HcC/RApNzL/dwubTCrEdin0iJm X-Mailman-Approved-At: Sat, 23 Feb 2013 21:25:44 +0000 Subject: [Xen-users] regarding 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="===============7950396125174683679==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============7950396125174683679== Content-Type: multipart/alternative; boundary=e89a8f2346bd9349b104d64d4092 --e89a8f2346bd9349b104d64d4092 Content-Type: text/plain; charset=ISO-8859-1 hi i hava to modify the xen source code(code for VM migration). i want to study the xen-4.2 source code and want to understand how its working, control flow,. but i didn't found any effective and detailed doc of it. please help me to start this. specifically i have to study the migration code only. can extra code be directly added to xen source code? -- Krishan Sethi Mtech, Computer Science & Engineering Central University of Rajasthan, kishangarh, Ajmer +91-9785673863 --e89a8f2346bd9349b104d64d4092 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
hi

i hava to modify the xen source = code(code for VM migration). i want to study the xen-4.2 source code and wa= nt to understand how its working, control flow,. but i didn't found any= effective and detailed doc of it.

please help me to start this. specifically i have to study the mi= gration code only. can extra code be directly added to xen source code? =A0=

--
Krishan = Sethi
Mtech, Com= puter Science & Engineering
Central University of Raja= sthan, kishangarh, Ajmer
+91-9785673863
--e89a8f2346bd9349b104d64d4092-- --===============7950396125174683679== 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 --===============7950396125174683679==-- From xen-users-bounces@lists.xen.org Sat Feb 23 21:26:55 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sat, 23 Feb 2013 21:26: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 1U9MbJ-0003Kg-Oh; Sat, 23 Feb 2013 21:25:45 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U8pQ1-0000wy-6j for xen-users@lists.xen.org; Fri, 22 Feb 2013 09:59:53 +0000 Received: from [85.158.139.83:46790] by server-14.bemta-5.messagelabs.com id 11/40-06967-89147215; Fri, 22 Feb 2013 09:59:52 +0000 X-Env-Sender: krishansethi@curaj.ac.in X-Msg-Ref: server-12.tower-182.messagelabs.com!1361527191!28444822!1 X-Originating-IP: [209.85.217.173] X-SpamReason: No, hits=0.4 required=7.0 tests=HTML_50_60,HTML_MESSAGE, RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 7958 invoked from network); 22 Feb 2013 09:59:51 -0000 Received: from mail-lb0-f173.google.com (HELO mail-lb0-f173.google.com) (209.85.217.173) by server-12.tower-182.messagelabs.com with RC4-SHA encrypted SMTP; 22 Feb 2013 09:59:51 -0000 Received: by mail-lb0-f173.google.com with SMTP id gf7so438116lbb.18 for ; Fri, 22 Feb 2013 01:59:51 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-received:date:message-id:subject:from:to :content-type:x-gm-message-state; bh=rdyPQTwFhFsm5Wp41IJ0PEkkaBYzEHhWj1l5EPG3ZVk=; b=FodK8rvVTZvT6bQ8+J/tIJfG9Jft4wAvRK1qSrvYduK3sm0bzF1YzNBDBjYF2M8j6T /EzTAobs9vji+fsxQoPPvt6Dg5o6+0BgA6HwbQrYdCVME8I9ZvHW5MJXH7QgDS6SrJtl dcDpBfh1BsHrpBHTCDq5gpvwnwkfUZFCpXdrcWveYpgcPe+Kas91CO/lIpD6l75dTdDV fhgZzZ/ZSEsuLTNkzXsuGIidyJyzrj3yw9wp+u5AYxJkbIT0S/9vv6CQoEmy90nENAgO WiD3rGHU18sHcmThDCcBSoPiStd+U+VNEJ6QmR+UQPmlgWa4RtgOKZoKkiqUB3kVFmZn HsZQ== MIME-Version: 1.0 X-Received: by 10.152.148.133 with SMTP id ts5mr1254623lab.2.1361527191062; Fri, 22 Feb 2013 01:59:51 -0800 (PST) Received: by 10.112.100.69 with HTTP; Fri, 22 Feb 2013 01:59:50 -0800 (PST) Date: Fri, 22 Feb 2013 15:29:50 +0530 Message-ID: From: Krishan Sethi To: xen-users@lists.xen.org X-Gm-Message-State: ALoCoQlo0CufkKnOE0Pg5bIFyUDNvdct54ZTaK3RIxg5GzcAE9HcC/RApNzL/dwubTCrEdin0iJm X-Mailman-Approved-At: Sat, 23 Feb 2013 21:25:44 +0000 Subject: [Xen-users] regarding 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="===============7950396125174683679==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============7950396125174683679== Content-Type: multipart/alternative; boundary=e89a8f2346bd9349b104d64d4092 --e89a8f2346bd9349b104d64d4092 Content-Type: text/plain; charset=ISO-8859-1 hi i hava to modify the xen source code(code for VM migration). i want to study the xen-4.2 source code and want to understand how its working, control flow,. but i didn't found any effective and detailed doc of it. please help me to start this. specifically i have to study the migration code only. can extra code be directly added to xen source code? -- Krishan Sethi Mtech, Computer Science & Engineering Central University of Rajasthan, kishangarh, Ajmer +91-9785673863 --e89a8f2346bd9349b104d64d4092 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
hi

i hava to modify the xen source = code(code for VM migration). i want to study the xen-4.2 source code and wa= nt to understand how its working, control flow,. but i didn't found any= effective and detailed doc of it.

please help me to start this. specifically i have to study the mi= gration code only. can extra code be directly added to xen source code? =A0=

--
Krishan = Sethi
Mtech, Com= puter Science & Engineering
Central University of Raja= sthan, kishangarh, Ajmer
+91-9785673863
--e89a8f2346bd9349b104d64d4092-- --===============7950396125174683679== 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 --===============7950396125174683679==-- From xen-users-bounces@lists.xen.org Sat Feb 23 21:26:56 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sat, 23 Feb 2013 21:26: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 1U9MbM-0003LG-63; Sat, 23 Feb 2013 21:25:48 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U98Px-0005NX-Bo for xen-users@lists.xensource.com; Sat, 23 Feb 2013 06:17:05 +0000 Received: from [85.158.137.99:47171] by server-11.bemta-3.messagelabs.com id F3/B9-10249-CDE58215; Sat, 23 Feb 2013 06:17:00 +0000 X-Env-Sender: liuhuan123123123@yahoo.com X-Msg-Ref: server-12.tower-217.messagelabs.com!1361600218!14429714!1 X-Originating-IP: [216.139.236.26] X-SpamReason: No, hits=2.5 required=7.0 tests=FORGED_YAHOO_RCVD, FROM_ENDS_IN_NUMS,ML_RADAR_SPEW_LINKS_14,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 3489 invoked from network); 23 Feb 2013 06:16:59 -0000 Received: from sam.nabble.com (HELO sam.nabble.com) (216.139.236.26) by server-12.tower-217.messagelabs.com with AES256-SHA encrypted SMTP; 23 Feb 2013 06:16:59 -0000 Received: from [192.168.236.26] (helo=sam.nabble.com) by sam.nabble.com with esmtp (Exim 4.72) (envelope-from ) id 1U98Pp-0001Me-N8 for xen-users@lists.xensource.com; Fri, 22 Feb 2013 22:16:57 -0800 Date: Fri, 22 Feb 2013 22:16:57 -0800 (PST) From: liuhuan To: xen-users@lists.xensource.com Message-ID: <1361600217703-5714393.post@n5.nabble.com> In-Reply-To: <1351069976947-5712103.post@n5.nabble.com> References: <1351069976947-5712103.post@n5.nabble.com> MIME-Version: 1.0 X-Mailman-Approved-At: Sat, 23 Feb 2013 21:25:44 +0000 Subject: Re: [Xen-users] Xwindows or Freenx in a guest domain X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org The Antipodal able Star quick breach is one brace of shoes that the sports activities person's ft would love. The ox even although copy acceptance to the shoes are bifold vulcanized and accept average and crabbed abutment to achieve assertive the actuality that ft are http://swagconverse.net/One-Star-Converse-shoes-category-8.html one star converse padded, adequate and accurate for quick action sports. The soles accommodate a abundant anchor on able floors as able-bodied as the shoes are as contemporary as sports activities shoes can get. The Antipodal Chuck Taylor All Star basal Tops aphotic shoes arise sleek, thin, alive and fast. These aphotic shoes are amazingly contemporary and will be the acceptable sports activities shoes. -- View this message in context: http://xen.1045712.n5.nabble.com/Xwindows-or-Freenx-in-a-guest-domain-tp2556589p5714393.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 Feb 23 21:26:56 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sat, 23 Feb 2013 21:26: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 1U9MbM-0003LG-63; Sat, 23 Feb 2013 21:25:48 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U98Px-0005NX-Bo for xen-users@lists.xensource.com; Sat, 23 Feb 2013 06:17:05 +0000 Received: from [85.158.137.99:47171] by server-11.bemta-3.messagelabs.com id F3/B9-10249-CDE58215; Sat, 23 Feb 2013 06:17:00 +0000 X-Env-Sender: liuhuan123123123@yahoo.com X-Msg-Ref: server-12.tower-217.messagelabs.com!1361600218!14429714!1 X-Originating-IP: [216.139.236.26] X-SpamReason: No, hits=2.5 required=7.0 tests=FORGED_YAHOO_RCVD, FROM_ENDS_IN_NUMS,ML_RADAR_SPEW_LINKS_14,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 3489 invoked from network); 23 Feb 2013 06:16:59 -0000 Received: from sam.nabble.com (HELO sam.nabble.com) (216.139.236.26) by server-12.tower-217.messagelabs.com with AES256-SHA encrypted SMTP; 23 Feb 2013 06:16:59 -0000 Received: from [192.168.236.26] (helo=sam.nabble.com) by sam.nabble.com with esmtp (Exim 4.72) (envelope-from ) id 1U98Pp-0001Me-N8 for xen-users@lists.xensource.com; Fri, 22 Feb 2013 22:16:57 -0800 Date: Fri, 22 Feb 2013 22:16:57 -0800 (PST) From: liuhuan To: xen-users@lists.xensource.com Message-ID: <1361600217703-5714393.post@n5.nabble.com> In-Reply-To: <1351069976947-5712103.post@n5.nabble.com> References: <1351069976947-5712103.post@n5.nabble.com> MIME-Version: 1.0 X-Mailman-Approved-At: Sat, 23 Feb 2013 21:25:44 +0000 Subject: Re: [Xen-users] Xwindows or Freenx in a guest domain X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org The Antipodal able Star quick breach is one brace of shoes that the sports activities person's ft would love. The ox even although copy acceptance to the shoes are bifold vulcanized and accept average and crabbed abutment to achieve assertive the actuality that ft are http://swagconverse.net/One-Star-Converse-shoes-category-8.html one star converse padded, adequate and accurate for quick action sports. The soles accommodate a abundant anchor on able floors as able-bodied as the shoes are as contemporary as sports activities shoes can get. The Antipodal Chuck Taylor All Star basal Tops aphotic shoes arise sleek, thin, alive and fast. These aphotic shoes are amazingly contemporary and will be the acceptable sports activities shoes. -- View this message in context: http://xen.1045712.n5.nabble.com/Xwindows-or-Freenx-in-a-guest-domain-tp2556589p5714393.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 Sun Feb 24 01:14:44 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sun, 24 Feb 2013 01:14: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 1U9Q9c-00055X-7H; Sun, 24 Feb 2013 01:13:24 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U9Q9a-00055S-8W for xen-users@lists.xen.org; Sun, 24 Feb 2013 01:13:22 +0000 Received: from [85.158.138.51:53888] by server-16.bemta-3.messagelabs.com id 5A/56-02727-E2969215; Sun, 24 Feb 2013 01:13:18 +0000 X-Env-Sender: matthias.kannenberg@googlemail.com X-Msg-Ref: server-9.tower-174.messagelabs.com!1361668397!28951535!1 X-Originating-IP: [209.85.215.48] X-SpamReason: No, hits=0.3 required=7.0 tests=RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 8921 invoked from network); 24 Feb 2013 01:13:18 -0000 Received: from mail-la0-f48.google.com (HELO mail-la0-f48.google.com) (209.85.215.48) by server-9.tower-174.messagelabs.com with RC4-SHA encrypted SMTP; 24 Feb 2013 01:13:18 -0000 Received: by mail-la0-f48.google.com with SMTP id fq13so1650740lab.21 for ; Sat, 23 Feb 2013 17:13:17 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=20120113; h=x-received:mime-version:in-reply-to:references:from:date:message-id :subject:to:cc:content-type; bh=SJNXhc1PhPlNLoKJMdoO5gwz8hE8Y/Xe6KayVAE1xEE=; b=JHbwzqYi2wnrTXqIu2g573Zk1k2phSDLRzPlw2Y324ihjj4M9hwWRqY+BOaYtXUmul bkf/dGUMzmT76JTH8hv3azI8hCSpXFIrHPCPLYz/J4sFnP1nhN9ZwfxZJAa+IfBYob1V lVSKrgQ0nXqxdqHc3CoUGSZL2RRRd9gr6/aW/8MqFRO9C3rT5Cr/W+B914gLRkAgRshn g8AtWZakayzpAzMOkd5FKWNqPeIosSD10NSuV3cj+pZfRSJceO5FdqsWLsI/V3HXXV18 eF3vMd3kD+Du0nue3w3bapyig+yymq8JjnwJ6CvDLglkpBe+bHj2/uLZP6G+AmOIABNA ZGGQ== X-Received: by 10.112.10.138 with SMTP id i10mr2770310lbb.24.1361668397331; Sat, 23 Feb 2013 17:13:17 -0800 (PST) MIME-Version: 1.0 Received: by 10.114.23.132 with HTTP; Sat, 23 Feb 2013 17:12:57 -0800 (PST) In-Reply-To: References: From: Matthias Date: Sun, 24 Feb 2013 02:12:57 +0100 Message-ID: To: Krishan Sethi Cc: xen-users@lists.xen.org Subject: Re: [Xen-users] regarding 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 Well, for the code itself you can simply clone one of xen gits repositories, that make whatever change you want and build / use it localy. You can find the different repositories here: http://wiki.xen.org/wiki/Xen_Repositories For documentation, i am not aware of any actual code documentation outside of the comments you find in the code itself. For standard documentation, there is always the wiki, this mailing list and the documentation packages.. this is a good start: http://xen.org/support/documentation.html 2013/2/22 Krishan Sethi : > hi > > i hava to modify the xen source code(code for VM migration). i want to study > the xen-4.2 source code and want to understand how its working, control > flow,. but i didn't found any effective and detailed doc of it. > > please help me to start this. specifically i have to study the migration > code only. can extra code be directly added to xen source code? > > -- > Krishan Sethi > Mtech, Computer Science & Engineering > Central University of Rajasthan, kishangarh, Ajmer > +91-9785673863 > > _______________________________________________ > 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 Feb 24 01:14:44 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sun, 24 Feb 2013 01:14: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 1U9Q9c-00055X-7H; Sun, 24 Feb 2013 01:13:24 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U9Q9a-00055S-8W for xen-users@lists.xen.org; Sun, 24 Feb 2013 01:13:22 +0000 Received: from [85.158.138.51:53888] by server-16.bemta-3.messagelabs.com id 5A/56-02727-E2969215; Sun, 24 Feb 2013 01:13:18 +0000 X-Env-Sender: matthias.kannenberg@googlemail.com X-Msg-Ref: server-9.tower-174.messagelabs.com!1361668397!28951535!1 X-Originating-IP: [209.85.215.48] X-SpamReason: No, hits=0.3 required=7.0 tests=RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 8921 invoked from network); 24 Feb 2013 01:13:18 -0000 Received: from mail-la0-f48.google.com (HELO mail-la0-f48.google.com) (209.85.215.48) by server-9.tower-174.messagelabs.com with RC4-SHA encrypted SMTP; 24 Feb 2013 01:13:18 -0000 Received: by mail-la0-f48.google.com with SMTP id fq13so1650740lab.21 for ; Sat, 23 Feb 2013 17:13:17 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=20120113; h=x-received:mime-version:in-reply-to:references:from:date:message-id :subject:to:cc:content-type; bh=SJNXhc1PhPlNLoKJMdoO5gwz8hE8Y/Xe6KayVAE1xEE=; b=JHbwzqYi2wnrTXqIu2g573Zk1k2phSDLRzPlw2Y324ihjj4M9hwWRqY+BOaYtXUmul bkf/dGUMzmT76JTH8hv3azI8hCSpXFIrHPCPLYz/J4sFnP1nhN9ZwfxZJAa+IfBYob1V lVSKrgQ0nXqxdqHc3CoUGSZL2RRRd9gr6/aW/8MqFRO9C3rT5Cr/W+B914gLRkAgRshn g8AtWZakayzpAzMOkd5FKWNqPeIosSD10NSuV3cj+pZfRSJceO5FdqsWLsI/V3HXXV18 eF3vMd3kD+Du0nue3w3bapyig+yymq8JjnwJ6CvDLglkpBe+bHj2/uLZP6G+AmOIABNA ZGGQ== X-Received: by 10.112.10.138 with SMTP id i10mr2770310lbb.24.1361668397331; Sat, 23 Feb 2013 17:13:17 -0800 (PST) MIME-Version: 1.0 Received: by 10.114.23.132 with HTTP; Sat, 23 Feb 2013 17:12:57 -0800 (PST) In-Reply-To: References: From: Matthias Date: Sun, 24 Feb 2013 02:12:57 +0100 Message-ID: To: Krishan Sethi Cc: xen-users@lists.xen.org Subject: Re: [Xen-users] regarding 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 Well, for the code itself you can simply clone one of xen gits repositories, that make whatever change you want and build / use it localy. You can find the different repositories here: http://wiki.xen.org/wiki/Xen_Repositories For documentation, i am not aware of any actual code documentation outside of the comments you find in the code itself. For standard documentation, there is always the wiki, this mailing list and the documentation packages.. this is a good start: http://xen.org/support/documentation.html 2013/2/22 Krishan Sethi : > hi > > i hava to modify the xen source code(code for VM migration). i want to study > the xen-4.2 source code and want to understand how its working, control > flow,. but i didn't found any effective and detailed doc of it. > > please help me to start this. specifically i have to study the migration > code only. can extra code be directly added to xen source code? > > -- > Krishan Sethi > Mtech, Computer Science & Engineering > Central University of Rajasthan, kishangarh, Ajmer > +91-9785673863 > > _______________________________________________ > 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 Feb 24 13:33:35 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sun, 24 Feb 2013 13:33: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 1U9bgT-0003Uo-Ni; Sun, 24 Feb 2013 13:32:05 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U9bgR-0003Uh-UD for xen-users@lists.xen.org; Sun, 24 Feb 2013 13:32:04 +0000 Received: from [85.158.143.99:55969] by server-3.bemta-4.messagelabs.com id 75/4E-02186-3561A215; Sun, 24 Feb 2013 13:32:03 +0000 X-Env-Sender: tosterman@gmail.com X-Msg-Ref: server-5.tower-216.messagelabs.com!1361712721!28443781!1 X-Originating-IP: [209.85.210.179] 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.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 30561 invoked from network); 24 Feb 2013 13:32:02 -0000 Received: from mail-ia0-f179.google.com (HELO mail-ia0-f179.google.com) (209.85.210.179) by server-5.tower-216.messagelabs.com with RC4-SHA encrypted SMTP; 24 Feb 2013 13:32:02 -0000 Received: by mail-ia0-f179.google.com with SMTP id x24so1783695iak.10 for ; Sun, 24 Feb 2013 05:32:00 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:reply-to:date:message-id:subject:from:to :content-type; bh=IHZuhJrJs6rLeJrau1IoKlOYVe8S8mMnkEvurY6r0IA=; b=rwKpx399sAz4KqzreZwutu6xe7MOnkf0SNSWYPxou4TnjP1+DCwC2RcqhZGyv3Z1lR 0h7lHj3Z8RQ82YCSOLJ3JQXDR+UDVlfWU4soERPCdBZtPs0onYe1VkWufpLaFiBatKZF 8dno90ENPimJi5IbBirow2/CVl+i6dBO85I0hPwssfqXuwiBa9eiqQCqfYATelUwk4ip DbWRD6lfwjrvciB1sKCd5Orm3dL3ubc4wx4A9ywe5QQykToKuksH/jDp8GE4IfgZ2P5m 2F7RhWHexs64bZrc1GjJGPF8iwjlUxYknObTgr8JWkLqI1LKoQazbWZpI94Uh4B2ZRQM rQzQ== MIME-Version: 1.0 X-Received: by 10.50.185.137 with SMTP id fc9mr1982377igc.109.1361712720627; Sun, 24 Feb 2013 05:32:00 -0800 (PST) Received: by 10.64.60.136 with HTTP; Sun, 24 Feb 2013 05:32:00 -0800 (PST) Date: Sun, 24 Feb 2013 08:32:00 -0500 Message-ID: From: Travis Osterman To: xen-users@lists.xen.org Subject: [Xen-users] pv guest fails to start after 4.2 upgrade X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: travis@wsor.net List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: 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 running xen on gentoo (3.7.0 hardened) and upgraded from 4.1 to 4.2 yesterday as 4.2 is marked as stable in the portage tree. Afterwards, I cannot start my guests and get the following error (currently running 4.2.1). Any help in troubleshooting would be greatly appreciated. Thanks in advance. -- T # xl create -c /data/xen/prime.pv libxl: error: libxl_dm.c:1212:device_model_spawn_outcome: domain 3 device model: spawn failed (rc=-3) libxl: error: libxl_qmp.c:641:libxl__qmp_initialize: Connection error: No such file or directory Daemon running with PID 8701 Xen Minimal OS! start_info: 0xd9f000(VA) nr_pages: 0x80000 shared_inf: 0xba892000(MA) pt_base: 0xda2000(VA) nr_pt_frames: 0xb mfn_list: 0x99f000(VA) mod_start: 0x0(VA) mod_len: 0 flags: 0x0 cmd_line: (hd0,0)/grub/menu.lst xencons=tty iommu=soft stack: 0x95e960-0x97e960 MM: Init _text: 0x0(VA) _etext: 0x6e8d4(VA) _erodata: 0x88000(VA) _edata: 0x90c80(VA) stack start: 0x95e960(VA) _end: 0x99ef60(VA) start_pfn: db0 max_pfn: 80000 Mapping memory range 0x1000000 - 0x80000000 setting 0x0-0x88000 readonly skipped 0x1000 MM: Initialise page allocator for 11a9000(11a9000)-80000000(80000000) MM: done Demand map pfns at 80001000-2080001000. Heap resides at 2080002000-4080002000. Initialising timer interface Initialising console ... done. gnttab_table mapped at 0x80001000. Initialising scheduler Thread "Idle": pointer: 0x2080002050, stack: 0x15d0000 Initialising xenbus Thread "xenstore": pointer: 0x2080002800, stack: 0x15e0000 Dummy main: start_info=0x97ea60 Thread "main": pointer: 0x2080002fb0, stack: 0x15f0000 Thread "pcifront": pointer: 0x2080003760, stack: 0x1600000 "main" "(hd0,0)/grub/menu.lst" "xencons=tty" "iommu=soft" pcifront_watches: waiting for backend path to appear device/pci/0/backend vbd 51712 is hd0 ******************* BLKFRONT for device/vbd/51712 ********** backend at /local/domain/0/backend/qdisk/3/51712 ================== ATTACHMENTS ============================ xl -vvv create -c /data/xen/prime.pv http://pastebin.com/92PW3QRH xl dmesg http://pastebin.com/ba2Xxv7w emerge --info (system info) http://pastebin.com/VKSfKjCW ================== ATTACHMENTS ============================ _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Sun Feb 24 13:33:35 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sun, 24 Feb 2013 13:33: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 1U9bgT-0003Uo-Ni; Sun, 24 Feb 2013 13:32:05 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U9bgR-0003Uh-UD for xen-users@lists.xen.org; Sun, 24 Feb 2013 13:32:04 +0000 Received: from [85.158.143.99:55969] by server-3.bemta-4.messagelabs.com id 75/4E-02186-3561A215; Sun, 24 Feb 2013 13:32:03 +0000 X-Env-Sender: tosterman@gmail.com X-Msg-Ref: server-5.tower-216.messagelabs.com!1361712721!28443781!1 X-Originating-IP: [209.85.210.179] 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.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 30561 invoked from network); 24 Feb 2013 13:32:02 -0000 Received: from mail-ia0-f179.google.com (HELO mail-ia0-f179.google.com) (209.85.210.179) by server-5.tower-216.messagelabs.com with RC4-SHA encrypted SMTP; 24 Feb 2013 13:32:02 -0000 Received: by mail-ia0-f179.google.com with SMTP id x24so1783695iak.10 for ; Sun, 24 Feb 2013 05:32:00 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:reply-to:date:message-id:subject:from:to :content-type; bh=IHZuhJrJs6rLeJrau1IoKlOYVe8S8mMnkEvurY6r0IA=; b=rwKpx399sAz4KqzreZwutu6xe7MOnkf0SNSWYPxou4TnjP1+DCwC2RcqhZGyv3Z1lR 0h7lHj3Z8RQ82YCSOLJ3JQXDR+UDVlfWU4soERPCdBZtPs0onYe1VkWufpLaFiBatKZF 8dno90ENPimJi5IbBirow2/CVl+i6dBO85I0hPwssfqXuwiBa9eiqQCqfYATelUwk4ip DbWRD6lfwjrvciB1sKCd5Orm3dL3ubc4wx4A9ywe5QQykToKuksH/jDp8GE4IfgZ2P5m 2F7RhWHexs64bZrc1GjJGPF8iwjlUxYknObTgr8JWkLqI1LKoQazbWZpI94Uh4B2ZRQM rQzQ== MIME-Version: 1.0 X-Received: by 10.50.185.137 with SMTP id fc9mr1982377igc.109.1361712720627; Sun, 24 Feb 2013 05:32:00 -0800 (PST) Received: by 10.64.60.136 with HTTP; Sun, 24 Feb 2013 05:32:00 -0800 (PST) Date: Sun, 24 Feb 2013 08:32:00 -0500 Message-ID: From: Travis Osterman To: xen-users@lists.xen.org Subject: [Xen-users] pv guest fails to start after 4.2 upgrade X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: travis@wsor.net List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: 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 running xen on gentoo (3.7.0 hardened) and upgraded from 4.1 to 4.2 yesterday as 4.2 is marked as stable in the portage tree. Afterwards, I cannot start my guests and get the following error (currently running 4.2.1). Any help in troubleshooting would be greatly appreciated. Thanks in advance. -- T # xl create -c /data/xen/prime.pv libxl: error: libxl_dm.c:1212:device_model_spawn_outcome: domain 3 device model: spawn failed (rc=-3) libxl: error: libxl_qmp.c:641:libxl__qmp_initialize: Connection error: No such file or directory Daemon running with PID 8701 Xen Minimal OS! start_info: 0xd9f000(VA) nr_pages: 0x80000 shared_inf: 0xba892000(MA) pt_base: 0xda2000(VA) nr_pt_frames: 0xb mfn_list: 0x99f000(VA) mod_start: 0x0(VA) mod_len: 0 flags: 0x0 cmd_line: (hd0,0)/grub/menu.lst xencons=tty iommu=soft stack: 0x95e960-0x97e960 MM: Init _text: 0x0(VA) _etext: 0x6e8d4(VA) _erodata: 0x88000(VA) _edata: 0x90c80(VA) stack start: 0x95e960(VA) _end: 0x99ef60(VA) start_pfn: db0 max_pfn: 80000 Mapping memory range 0x1000000 - 0x80000000 setting 0x0-0x88000 readonly skipped 0x1000 MM: Initialise page allocator for 11a9000(11a9000)-80000000(80000000) MM: done Demand map pfns at 80001000-2080001000. Heap resides at 2080002000-4080002000. Initialising timer interface Initialising console ... done. gnttab_table mapped at 0x80001000. Initialising scheduler Thread "Idle": pointer: 0x2080002050, stack: 0x15d0000 Initialising xenbus Thread "xenstore": pointer: 0x2080002800, stack: 0x15e0000 Dummy main: start_info=0x97ea60 Thread "main": pointer: 0x2080002fb0, stack: 0x15f0000 Thread "pcifront": pointer: 0x2080003760, stack: 0x1600000 "main" "(hd0,0)/grub/menu.lst" "xencons=tty" "iommu=soft" pcifront_watches: waiting for backend path to appear device/pci/0/backend vbd 51712 is hd0 ******************* BLKFRONT for device/vbd/51712 ********** backend at /local/domain/0/backend/qdisk/3/51712 ================== ATTACHMENTS ============================ xl -vvv create -c /data/xen/prime.pv http://pastebin.com/92PW3QRH xl dmesg http://pastebin.com/ba2Xxv7w emerge --info (system info) http://pastebin.com/VKSfKjCW ================== ATTACHMENTS ============================ _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Sun Feb 24 14:38:48 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sun, 24 Feb 2013 14:38: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 1U9chb-0004qS-Bz; Sun, 24 Feb 2013 14:37:19 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U9chZ-0004qN-3S for xen-users@lists.xen.org; Sun, 24 Feb 2013 14:37:17 +0000 Received: from [85.158.139.83:9429] by server-14.bemta-5.messagelabs.com id FD/0C-06967-C952A215; Sun, 24 Feb 2013 14:37:16 +0000 X-Env-Sender: mailinglists.tech@gmail.com X-Msg-Ref: server-5.tower-182.messagelabs.com!1361716633!28721681!1 X-Originating-IP: [209.85.128.49] 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.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 804 invoked from network); 24 Feb 2013 14:37:14 -0000 Received: from mail-qe0-f49.google.com (HELO mail-qe0-f49.google.com) (209.85.128.49) by server-5.tower-182.messagelabs.com with RC4-SHA encrypted SMTP; 24 Feb 2013 14:37:14 -0000 Received: by mail-qe0-f49.google.com with SMTP id q19so1111364qeb.36 for ; Sun, 24 Feb 2013 06:37:13 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=DEufgCOhBkimPAgbFd+ouvQhMwNyK28Si6rPtkvQ2ko=; b=hxiFgerBflT6NTangDlbo1Hs4i4yk8eNz/EJnNEOxuZDyv1v0LztcfVYRkfdkDcZyL Hxg0ERLeMK+Q+CveGBGNbtmNkIr5K4ALi1Pva8sUDIW42n8fWn8rEX7tlhz68JM09gcz 1TeT+wk8nmOCd4gBXb3n3Y1vlgz4dSLPOK8dMYEFJsapROfO/XOHPcH/DSTYVhHtdO/K Xg7YDYbATrIFkY55QdKiPsGePAgEtjVgSnCYZQaW8V7Xxdaj6uUCMgSdSxg54gUiviVj ETXhSzCTJvzLjC2KifjB1+nIScdTICXa2B2RptpCjucvZkF8T/bEqrOmes/Y0yg0bh1p C3rg== MIME-Version: 1.0 X-Received: by 10.229.111.154 with SMTP id s26mr1589110qcp.57.1361716630483; Sun, 24 Feb 2013 06:37:10 -0800 (PST) Received: by 10.49.110.70 with HTTP; Sun, 24 Feb 2013 06:37:10 -0800 (PST) In-Reply-To: References: Date: Sun, 24 Feb 2013 15:37:10 +0100 Message-ID: From: tech mailinglists To: travis@wsor.net Cc: xen-users Subject: Re: [Xen-users] pv guest fails to start after 4.2 upgrade X-BeenThere: xen-users@lists.xen.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="===============3974404023876977511==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============3974404023876977511== Content-Type: multipart/alternative; boundary=0023544710880c52fd04d6795ce5 --0023544710880c52fd04d6795ce5 Content-Type: text/plain; charset=ISO-8859-1 Hello Travis, pleas check /var/log/xen/domainname-dm.log. I think that Qemu is needed in this case of a PV guest. I had the same problem yesterday and the reason was that I forgot to install a special dependency in my case libsdl. In my case the boot stucked at some point and it wasn't obvious that it was related to that. Eventually something in the portage package is wrong. Hope this would help. Best Regards 2013/2/24 Travis Osterman > I'm running xen on gentoo (3.7.0 hardened) and upgraded from 4.1 to > 4.2 yesterday as 4.2 is marked as stable in the portage tree. > Afterwards, I cannot start my guests and get the following error > (currently running 4.2.1). Any help in troubleshooting would be > greatly appreciated. Thanks in advance. > > -- T > > # xl create -c /data/xen/prime.pv > libxl: error: libxl_dm.c:1212:device_model_spawn_outcome: domain 3 > device model: spawn failed (rc=-3) > libxl: error: libxl_qmp.c:641:libxl__qmp_initialize: Connection error: > No such file or directory > Daemon running with PID 8701 > Xen Minimal OS! > start_info: 0xd9f000(VA) > nr_pages: 0x80000 > shared_inf: 0xba892000(MA) > pt_base: 0xda2000(VA) > nr_pt_frames: 0xb > mfn_list: 0x99f000(VA) > mod_start: 0x0(VA) > mod_len: 0 > flags: 0x0 > cmd_line: (hd0,0)/grub/menu.lst xencons=tty iommu=soft > stack: 0x95e960-0x97e960 > MM: Init > _text: 0x0(VA) > _etext: 0x6e8d4(VA) > _erodata: 0x88000(VA) > _edata: 0x90c80(VA) > stack start: 0x95e960(VA) > _end: 0x99ef60(VA) > start_pfn: db0 > max_pfn: 80000 > Mapping memory range 0x1000000 - 0x80000000 > setting 0x0-0x88000 readonly > skipped 0x1000 > MM: Initialise page allocator for 11a9000(11a9000)-80000000(80000000) > MM: done > Demand map pfns at 80001000-2080001000. > Heap resides at 2080002000-4080002000. > Initialising timer interface > Initialising console ... done. > gnttab_table mapped at 0x80001000. > Initialising scheduler > Thread "Idle": pointer: 0x2080002050, stack: 0x15d0000 > Initialising xenbus > Thread "xenstore": pointer: 0x2080002800, stack: 0x15e0000 > Dummy main: start_info=0x97ea60 > Thread "main": pointer: 0x2080002fb0, stack: 0x15f0000 > Thread "pcifront": pointer: 0x2080003760, stack: 0x1600000 > "main" "(hd0,0)/grub/menu.lst" "xencons=tty" "iommu=soft" > pcifront_watches: waiting for backend path to appear device/pci/0/backend > vbd 51712 is hd0 > ******************* BLKFRONT for device/vbd/51712 ********** > > > backend at /local/domain/0/backend/qdisk/3/51712 > > ================== ATTACHMENTS ============================ > > xl -vvv create -c /data/xen/prime.pv > http://pastebin.com/92PW3QRH > > xl dmesg > http://pastebin.com/ba2Xxv7w > > emerge --info (system info) > http://pastebin.com/VKSfKjCW > > ================== ATTACHMENTS ============================ > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xen.org > http://lists.xen.org/xen-users > --0023544710880c52fd04d6795ce5 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Hello Travis,

pleas check /var/log/= xen/domainname-dm.log. I think that Qemu is needed in this case of a PV gue= st. I had the same problem yesterday and the reason was that I forgot to in= stall a special dependency in my case libsdl. In my case the boot stucked a= t some point and it wasn't obvious that it was related to that.

Eventually something in the portage package is wrong. Hope this w= ould help.

Best Regards


=
2013/2/24 Travis Osterman <= tosterman@gmail.co= m>
I'm running xen on gentoo (3.7.0 hardene= d) and upgraded from 4.1 to
4.2 yesterday as 4.2 is marked as stable in the portage tree.
Afterwards, I cannot start my guests and get the following error
(currently running 4.2.1). =A0Any help in troubleshooting would be
greatly appreciated. =A0Thanks in advance.

-- T

# xl create -c /data/xen/prime.pv
libxl: error: libxl_dm.c:1212:device_model_spawn_outcome: domain 3
device model: spawn failed (rc=3D-3)
libxl: error: libxl_qmp.c:641:libxl__qmp_initialize: Connection error:
No such file or directory
Daemon running with PID 8701
Xen Minimal OS!
=A0 start_info: 0xd9f000(VA)
=A0 =A0 nr_pages: 0x80000
=A0 shared_inf: 0xba892000(MA)
=A0 =A0 =A0pt_base: 0xda2000(VA)
nr_pt_frames: 0xb
=A0 =A0 mfn_list: 0x99f000(VA)
=A0 =A0mod_start: 0x0(VA)
=A0 =A0 =A0mod_len: 0
=A0 =A0 =A0 =A0flags: 0x0
=A0 =A0 cmd_line: (hd0,0)/grub/menu.lst xencons=3Dtty iommu=3Dsoft
=A0 stack: =A0 =A0 =A00x95e960-0x97e960
MM: Init
=A0 =A0 =A0 _text: 0x0(VA)
=A0 =A0 =A0_etext: 0x6e8d4(VA)
=A0 =A0_erodata: 0x88000(VA)
=A0 =A0 =A0_edata: 0x90c80(VA)
stack start: 0x95e960(VA)
=A0 =A0 =A0 =A0_end: 0x99ef60(VA)
=A0 start_pfn: db0
=A0 =A0 max_pfn: 80000
Mapping memory range 0x1000000 - 0x80000000
setting 0x0-0x88000 readonly
skipped 0x1000
MM: Initialise page allocator for 11a9000(11a9000)-80000000(80000000)
MM: done
Demand map pfns at 80001000-2080001000.
Heap resides at 2080002000-4080002000.
Initialising timer interface
Initialising console ... done.
gnttab_table mapped at 0x80001000.
Initialising scheduler
Thread "Idle": pointer: 0x2080002050, stack: 0x15d0000
Initialising xenbus
Thread "xenstore": pointer: 0x2080002800, stack: 0x15e0000
Dummy main: start_info=3D0x97ea60
Thread "main": pointer: 0x2080002fb0, stack: 0x15f0000
Thread "pcifront": pointer: 0x2080003760, stack: 0x1600000
"main" "(hd0,0)/grub/menu.lst" "xencons=3Dtty"= ; "iommu=3Dsoft"
pcifront_watches: waiting for backend path to appear device/pci/0/backend vbd 51712 is hd0
******************* BLKFRONT for device/vbd/51712 **********


backend at /local/domain/0/backend/qdisk/3/51712

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D ATTACHMENTS =3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D

xl -vvv create -c /data/xen/prime.pv
http://pastebin.= com/92PW3QRH

xl dmesg
http://pastebin.= com/ba2Xxv7w

emerge --info (system info)
http://pastebin.= com/VKSfKjCW

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D ATTACHMENTS =3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D

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

--0023544710880c52fd04d6795ce5-- --===============3974404023876977511== 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 --===============3974404023876977511==-- From xen-users-bounces@lists.xen.org Sun Feb 24 14:38:48 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sun, 24 Feb 2013 14:38: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 1U9chb-0004qS-Bz; Sun, 24 Feb 2013 14:37:19 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U9chZ-0004qN-3S for xen-users@lists.xen.org; Sun, 24 Feb 2013 14:37:17 +0000 Received: from [85.158.139.83:9429] by server-14.bemta-5.messagelabs.com id FD/0C-06967-C952A215; Sun, 24 Feb 2013 14:37:16 +0000 X-Env-Sender: mailinglists.tech@gmail.com X-Msg-Ref: server-5.tower-182.messagelabs.com!1361716633!28721681!1 X-Originating-IP: [209.85.128.49] 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.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 804 invoked from network); 24 Feb 2013 14:37:14 -0000 Received: from mail-qe0-f49.google.com (HELO mail-qe0-f49.google.com) (209.85.128.49) by server-5.tower-182.messagelabs.com with RC4-SHA encrypted SMTP; 24 Feb 2013 14:37:14 -0000 Received: by mail-qe0-f49.google.com with SMTP id q19so1111364qeb.36 for ; Sun, 24 Feb 2013 06:37:13 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=DEufgCOhBkimPAgbFd+ouvQhMwNyK28Si6rPtkvQ2ko=; b=hxiFgerBflT6NTangDlbo1Hs4i4yk8eNz/EJnNEOxuZDyv1v0LztcfVYRkfdkDcZyL Hxg0ERLeMK+Q+CveGBGNbtmNkIr5K4ALi1Pva8sUDIW42n8fWn8rEX7tlhz68JM09gcz 1TeT+wk8nmOCd4gBXb3n3Y1vlgz4dSLPOK8dMYEFJsapROfO/XOHPcH/DSTYVhHtdO/K Xg7YDYbATrIFkY55QdKiPsGePAgEtjVgSnCYZQaW8V7Xxdaj6uUCMgSdSxg54gUiviVj ETXhSzCTJvzLjC2KifjB1+nIScdTICXa2B2RptpCjucvZkF8T/bEqrOmes/Y0yg0bh1p C3rg== MIME-Version: 1.0 X-Received: by 10.229.111.154 with SMTP id s26mr1589110qcp.57.1361716630483; Sun, 24 Feb 2013 06:37:10 -0800 (PST) Received: by 10.49.110.70 with HTTP; Sun, 24 Feb 2013 06:37:10 -0800 (PST) In-Reply-To: References: Date: Sun, 24 Feb 2013 15:37:10 +0100 Message-ID: From: tech mailinglists To: travis@wsor.net Cc: xen-users Subject: Re: [Xen-users] pv guest fails to start after 4.2 upgrade X-BeenThere: xen-users@lists.xen.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="===============3974404023876977511==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============3974404023876977511== Content-Type: multipart/alternative; boundary=0023544710880c52fd04d6795ce5 --0023544710880c52fd04d6795ce5 Content-Type: text/plain; charset=ISO-8859-1 Hello Travis, pleas check /var/log/xen/domainname-dm.log. I think that Qemu is needed in this case of a PV guest. I had the same problem yesterday and the reason was that I forgot to install a special dependency in my case libsdl. In my case the boot stucked at some point and it wasn't obvious that it was related to that. Eventually something in the portage package is wrong. Hope this would help. Best Regards 2013/2/24 Travis Osterman > I'm running xen on gentoo (3.7.0 hardened) and upgraded from 4.1 to > 4.2 yesterday as 4.2 is marked as stable in the portage tree. > Afterwards, I cannot start my guests and get the following error > (currently running 4.2.1). Any help in troubleshooting would be > greatly appreciated. Thanks in advance. > > -- T > > # xl create -c /data/xen/prime.pv > libxl: error: libxl_dm.c:1212:device_model_spawn_outcome: domain 3 > device model: spawn failed (rc=-3) > libxl: error: libxl_qmp.c:641:libxl__qmp_initialize: Connection error: > No such file or directory > Daemon running with PID 8701 > Xen Minimal OS! > start_info: 0xd9f000(VA) > nr_pages: 0x80000 > shared_inf: 0xba892000(MA) > pt_base: 0xda2000(VA) > nr_pt_frames: 0xb > mfn_list: 0x99f000(VA) > mod_start: 0x0(VA) > mod_len: 0 > flags: 0x0 > cmd_line: (hd0,0)/grub/menu.lst xencons=tty iommu=soft > stack: 0x95e960-0x97e960 > MM: Init > _text: 0x0(VA) > _etext: 0x6e8d4(VA) > _erodata: 0x88000(VA) > _edata: 0x90c80(VA) > stack start: 0x95e960(VA) > _end: 0x99ef60(VA) > start_pfn: db0 > max_pfn: 80000 > Mapping memory range 0x1000000 - 0x80000000 > setting 0x0-0x88000 readonly > skipped 0x1000 > MM: Initialise page allocator for 11a9000(11a9000)-80000000(80000000) > MM: done > Demand map pfns at 80001000-2080001000. > Heap resides at 2080002000-4080002000. > Initialising timer interface > Initialising console ... done. > gnttab_table mapped at 0x80001000. > Initialising scheduler > Thread "Idle": pointer: 0x2080002050, stack: 0x15d0000 > Initialising xenbus > Thread "xenstore": pointer: 0x2080002800, stack: 0x15e0000 > Dummy main: start_info=0x97ea60 > Thread "main": pointer: 0x2080002fb0, stack: 0x15f0000 > Thread "pcifront": pointer: 0x2080003760, stack: 0x1600000 > "main" "(hd0,0)/grub/menu.lst" "xencons=tty" "iommu=soft" > pcifront_watches: waiting for backend path to appear device/pci/0/backend > vbd 51712 is hd0 > ******************* BLKFRONT for device/vbd/51712 ********** > > > backend at /local/domain/0/backend/qdisk/3/51712 > > ================== ATTACHMENTS ============================ > > xl -vvv create -c /data/xen/prime.pv > http://pastebin.com/92PW3QRH > > xl dmesg > http://pastebin.com/ba2Xxv7w > > emerge --info (system info) > http://pastebin.com/VKSfKjCW > > ================== ATTACHMENTS ============================ > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xen.org > http://lists.xen.org/xen-users > --0023544710880c52fd04d6795ce5 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Hello Travis,

pleas check /var/log/= xen/domainname-dm.log. I think that Qemu is needed in this case of a PV gue= st. I had the same problem yesterday and the reason was that I forgot to in= stall a special dependency in my case libsdl. In my case the boot stucked a= t some point and it wasn't obvious that it was related to that.

Eventually something in the portage package is wrong. Hope this w= ould help.

Best Regards


=
2013/2/24 Travis Osterman <= tosterman@gmail.co= m>
I'm running xen on gentoo (3.7.0 hardene= d) and upgraded from 4.1 to
4.2 yesterday as 4.2 is marked as stable in the portage tree.
Afterwards, I cannot start my guests and get the following error
(currently running 4.2.1). =A0Any help in troubleshooting would be
greatly appreciated. =A0Thanks in advance.

-- T

# xl create -c /data/xen/prime.pv
libxl: error: libxl_dm.c:1212:device_model_spawn_outcome: domain 3
device model: spawn failed (rc=3D-3)
libxl: error: libxl_qmp.c:641:libxl__qmp_initialize: Connection error:
No such file or directory
Daemon running with PID 8701
Xen Minimal OS!
=A0 start_info: 0xd9f000(VA)
=A0 =A0 nr_pages: 0x80000
=A0 shared_inf: 0xba892000(MA)
=A0 =A0 =A0pt_base: 0xda2000(VA)
nr_pt_frames: 0xb
=A0 =A0 mfn_list: 0x99f000(VA)
=A0 =A0mod_start: 0x0(VA)
=A0 =A0 =A0mod_len: 0
=A0 =A0 =A0 =A0flags: 0x0
=A0 =A0 cmd_line: (hd0,0)/grub/menu.lst xencons=3Dtty iommu=3Dsoft
=A0 stack: =A0 =A0 =A00x95e960-0x97e960
MM: Init
=A0 =A0 =A0 _text: 0x0(VA)
=A0 =A0 =A0_etext: 0x6e8d4(VA)
=A0 =A0_erodata: 0x88000(VA)
=A0 =A0 =A0_edata: 0x90c80(VA)
stack start: 0x95e960(VA)
=A0 =A0 =A0 =A0_end: 0x99ef60(VA)
=A0 start_pfn: db0
=A0 =A0 max_pfn: 80000
Mapping memory range 0x1000000 - 0x80000000
setting 0x0-0x88000 readonly
skipped 0x1000
MM: Initialise page allocator for 11a9000(11a9000)-80000000(80000000)
MM: done
Demand map pfns at 80001000-2080001000.
Heap resides at 2080002000-4080002000.
Initialising timer interface
Initialising console ... done.
gnttab_table mapped at 0x80001000.
Initialising scheduler
Thread "Idle": pointer: 0x2080002050, stack: 0x15d0000
Initialising xenbus
Thread "xenstore": pointer: 0x2080002800, stack: 0x15e0000
Dummy main: start_info=3D0x97ea60
Thread "main": pointer: 0x2080002fb0, stack: 0x15f0000
Thread "pcifront": pointer: 0x2080003760, stack: 0x1600000
"main" "(hd0,0)/grub/menu.lst" "xencons=3Dtty"= ; "iommu=3Dsoft"
pcifront_watches: waiting for backend path to appear device/pci/0/backend vbd 51712 is hd0
******************* BLKFRONT for device/vbd/51712 **********


backend at /local/domain/0/backend/qdisk/3/51712

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D ATTACHMENTS =3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D

xl -vvv create -c /data/xen/prime.pv
http://pastebin.= com/92PW3QRH

xl dmesg
http://pastebin.= com/ba2Xxv7w

emerge --info (system info)
http://pastebin.= com/VKSfKjCW

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D ATTACHMENTS =3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D

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

--0023544710880c52fd04d6795ce5-- --===============3974404023876977511== 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 --===============3974404023876977511==-- From xen-users-bounces@lists.xen.org Sun Feb 24 17:12:31 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sun, 24 Feb 2013 17:12: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 1U9f6U-0000RG-UN; Sun, 24 Feb 2013 17:11:10 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U9f6T-0000OR-5a for xen-users@lists.xen.org; Sun, 24 Feb 2013 17:11:09 +0000 Received: from [85.158.143.99:26015] by server-2.bemta-4.messagelabs.com id 9D/3F-12656-CA94A215; Sun, 24 Feb 2013 17:11:08 +0000 X-Env-Sender: tosterman@gmail.com X-Msg-Ref: server-14.tower-216.messagelabs.com!1361725866!18535715!1 X-Originating-IP: [209.85.210.169] 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.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 29541 invoked from network); 24 Feb 2013 17:11:07 -0000 Received: from mail-ia0-f169.google.com (HELO mail-ia0-f169.google.com) (209.85.210.169) by server-14.tower-216.messagelabs.com with RC4-SHA encrypted SMTP; 24 Feb 2013 17:11:07 -0000 Received: by mail-ia0-f169.google.com with SMTP id j5so1891703iaf.0 for ; Sun, 24 Feb 2013 09:11:06 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:reply-to:in-reply-to:references:date :message-id:subject:from:to:content-type; bh=R4aDVzmt9wTxNs9po97JG83+wlV7Py72UREzxC5H8t0=; b=P41r6G8RMNtckflVjAkW0PnTSlMV9TRALIMRTqDUwhmhamGopiy6JU9ovCnmUw0X0e az5uGgCTtJnJNKBa+378yzcfj0/Xc7jdK1Acx3BAjcLR6RItsfRKMNWs1C4ikw7nBkNh YPjU6+aggQcDBpfrhrKf8Dmqdv+70JeyQ6MCbBl3tnU3U1JUMz9ImR8iQX4pxlCyubTB uchCAEzG8R1HedAy9m8d4w6uPeC1sjPe0JyP2U8+pJ+WPrtBfg/0tq75mH4Pn6lPb5K+ 6F2BClsP2tzW+4ggTxnAEGXI6EtoBX9hed6Z+1iUhjJ376XE2uaX3A/tO+TmFdRSthKW /0Ug== MIME-Version: 1.0 X-Received: by 10.50.185.137 with SMTP id fc9mr2195282igc.109.1361725865995; Sun, 24 Feb 2013 09:11:05 -0800 (PST) Received: by 10.64.60.136 with HTTP; Sun, 24 Feb 2013 09:11:05 -0800 (PST) In-Reply-To: References: Date: Sun, 24 Feb 2013 12:11:05 -0500 Message-ID: From: Travis Osterman To: xen-users Subject: Re: [Xen-users] pv guest fails to start after 4.2 upgrade X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: travis@wsor.net List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: 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 running xen on gentoo (3.7.0 hardened) and upgraded from 4.1 to >> 4.2 yesterday as 4.2 is marked as stable in the portage tree. >> Afterwards, I cannot start my guests and get the following error >> (currently running 4.2.1). Any help in troubleshooting would be >> greatly appreciated. Thanks in advance. >> >> -- T >> >> # xl create -c /data/xen/prime.pv >> libxl: error: libxl_dm.c:1212:device_model_spawn_outcome: domain 3 >> device model: spawn failed (rc=-3) >> libxl: error: libxl_qmp.c:641:libxl__qmp_initialize: Connection error: >> No such file or directory >> Daemon running with PID 8701 ... >> >> ================== ATTACHMENTS ============================ >> >> xl -vvv create -c /data/xen/prime.pv >> http://pastebin.com/92PW3QRH >> >> xl dmesg >> http://pastebin.com/ba2Xxv7w >> >> emerge --info (system info) >> http://pastebin.com/VKSfKjCW >> > Hello Travis, > > pleas check /var/log/xen/domainname-dm.log. I think that Qemu is needed in > this case of a PV guest. I had the same problem yesterday and the reason was > that I forgot to install a special dependency in my case libsdl. In my case > the boot stucked at some point and it wasn't obvious that it was related to > that. > > Eventually something in the portage package is wrong. Hope this would help. > > Best Regards > > I have media-libs/libsdl-1.2.15-r2 installed. No change after rebuilding. Here is the guest log: # cat /var/log/xen/xl-prime.log Waiting for domain prime (domid 8) to die [pid 14679] libxl: debug: libxl_event.c:512:libxl__ev_xswatch_register: watch w=0x626cf0 wpath=@releaseDomain token=3/0: register slotnum=3 libxl: debug: libxl_event.c:457:watchfd_callback: watch w=0x626cf0 wpath=@releaseDomain token=3/0: event epath=@releaseDomain libxl: debug: libxl.c:1015:domain_death_xswatch_callback: [evg=0x624fe0:8] from domid=8 nentries=1 rc=1 libxl: debug: libxl.c:1026:domain_death_xswatch_callback: [evg=0x624fe0:8] got=domaininfos[0] got->domain=8 libxl: debug: libxl.c:1053:domain_death_xswatch_callback: exists shutdown_reported=0 dominf.flags=ffff0020 libxl: debug: libxl.c:1019:domain_death_xswatch_callback: [evg=0] all reported libxl: debug: libxl.c:1083:domain_death_xswatch_callback: domain death search done Thanks again. -- T _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Sun Feb 24 17:12:31 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sun, 24 Feb 2013 17:12: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 1U9f6U-0000RG-UN; Sun, 24 Feb 2013 17:11:10 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U9f6T-0000OR-5a for xen-users@lists.xen.org; Sun, 24 Feb 2013 17:11:09 +0000 Received: from [85.158.143.99:26015] by server-2.bemta-4.messagelabs.com id 9D/3F-12656-CA94A215; Sun, 24 Feb 2013 17:11:08 +0000 X-Env-Sender: tosterman@gmail.com X-Msg-Ref: server-14.tower-216.messagelabs.com!1361725866!18535715!1 X-Originating-IP: [209.85.210.169] 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.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 29541 invoked from network); 24 Feb 2013 17:11:07 -0000 Received: from mail-ia0-f169.google.com (HELO mail-ia0-f169.google.com) (209.85.210.169) by server-14.tower-216.messagelabs.com with RC4-SHA encrypted SMTP; 24 Feb 2013 17:11:07 -0000 Received: by mail-ia0-f169.google.com with SMTP id j5so1891703iaf.0 for ; Sun, 24 Feb 2013 09:11:06 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:reply-to:in-reply-to:references:date :message-id:subject:from:to:content-type; bh=R4aDVzmt9wTxNs9po97JG83+wlV7Py72UREzxC5H8t0=; b=P41r6G8RMNtckflVjAkW0PnTSlMV9TRALIMRTqDUwhmhamGopiy6JU9ovCnmUw0X0e az5uGgCTtJnJNKBa+378yzcfj0/Xc7jdK1Acx3BAjcLR6RItsfRKMNWs1C4ikw7nBkNh YPjU6+aggQcDBpfrhrKf8Dmqdv+70JeyQ6MCbBl3tnU3U1JUMz9ImR8iQX4pxlCyubTB uchCAEzG8R1HedAy9m8d4w6uPeC1sjPe0JyP2U8+pJ+WPrtBfg/0tq75mH4Pn6lPb5K+ 6F2BClsP2tzW+4ggTxnAEGXI6EtoBX9hed6Z+1iUhjJ376XE2uaX3A/tO+TmFdRSthKW /0Ug== MIME-Version: 1.0 X-Received: by 10.50.185.137 with SMTP id fc9mr2195282igc.109.1361725865995; Sun, 24 Feb 2013 09:11:05 -0800 (PST) Received: by 10.64.60.136 with HTTP; Sun, 24 Feb 2013 09:11:05 -0800 (PST) In-Reply-To: References: Date: Sun, 24 Feb 2013 12:11:05 -0500 Message-ID: From: Travis Osterman To: xen-users Subject: Re: [Xen-users] pv guest fails to start after 4.2 upgrade X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: travis@wsor.net List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: 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 running xen on gentoo (3.7.0 hardened) and upgraded from 4.1 to >> 4.2 yesterday as 4.2 is marked as stable in the portage tree. >> Afterwards, I cannot start my guests and get the following error >> (currently running 4.2.1). Any help in troubleshooting would be >> greatly appreciated. Thanks in advance. >> >> -- T >> >> # xl create -c /data/xen/prime.pv >> libxl: error: libxl_dm.c:1212:device_model_spawn_outcome: domain 3 >> device model: spawn failed (rc=-3) >> libxl: error: libxl_qmp.c:641:libxl__qmp_initialize: Connection error: >> No such file or directory >> Daemon running with PID 8701 ... >> >> ================== ATTACHMENTS ============================ >> >> xl -vvv create -c /data/xen/prime.pv >> http://pastebin.com/92PW3QRH >> >> xl dmesg >> http://pastebin.com/ba2Xxv7w >> >> emerge --info (system info) >> http://pastebin.com/VKSfKjCW >> > Hello Travis, > > pleas check /var/log/xen/domainname-dm.log. I think that Qemu is needed in > this case of a PV guest. I had the same problem yesterday and the reason was > that I forgot to install a special dependency in my case libsdl. In my case > the boot stucked at some point and it wasn't obvious that it was related to > that. > > Eventually something in the portage package is wrong. Hope this would help. > > Best Regards > > I have media-libs/libsdl-1.2.15-r2 installed. No change after rebuilding. Here is the guest log: # cat /var/log/xen/xl-prime.log Waiting for domain prime (domid 8) to die [pid 14679] libxl: debug: libxl_event.c:512:libxl__ev_xswatch_register: watch w=0x626cf0 wpath=@releaseDomain token=3/0: register slotnum=3 libxl: debug: libxl_event.c:457:watchfd_callback: watch w=0x626cf0 wpath=@releaseDomain token=3/0: event epath=@releaseDomain libxl: debug: libxl.c:1015:domain_death_xswatch_callback: [evg=0x624fe0:8] from domid=8 nentries=1 rc=1 libxl: debug: libxl.c:1026:domain_death_xswatch_callback: [evg=0x624fe0:8] got=domaininfos[0] got->domain=8 libxl: debug: libxl.c:1053:domain_death_xswatch_callback: exists shutdown_reported=0 dominf.flags=ffff0020 libxl: debug: libxl.c:1019:domain_death_xswatch_callback: [evg=0] all reported libxl: debug: libxl.c:1083:domain_death_xswatch_callback: domain death search done Thanks again. -- T _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Sun Feb 24 17:13:01 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sun, 24 Feb 2013 17:13: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 1U9f7G-0000TR-Jo; Sun, 24 Feb 2013 17:11:58 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U9f7F-0000TF-FL for xen-users@lists.xen.org; Sun, 24 Feb 2013 17:11:57 +0000 Received: from [85.158.137.99:33159] by server-1.bemta-3.messagelabs.com id BE/33-08955-CD94A215; Sun, 24 Feb 2013 17:11:56 +0000 X-Env-Sender: mailinglists.tech@gmail.com X-Msg-Ref: server-16.tower-217.messagelabs.com!1361725915!17113870!1 X-Originating-IP: [209.85.215.170] X-SpamReason: No, hits=0.2 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, RCVD_ILLEGAL_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 27343 invoked from network); 24 Feb 2013 17:11:55 -0000 Received: from mail-ea0-f170.google.com (HELO mail-ea0-f170.google.com) (209.85.215.170) by server-16.tower-217.messagelabs.com with RC4-SHA encrypted SMTP; 24 Feb 2013 17:11:55 -0000 Received: by mail-ea0-f170.google.com with SMTP id a11so932080eaa.29 for ; Sun, 24 Feb 2013 09:11:55 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=JfbsiYOkhhB8O0z17i1Mt7eou9iQ8+XdR9IIYEWquuA=; b=jEsNOesFnFlJdGiBAqTyV03uNlan4dICtT7mPhyPSHn/MyEKdJSuEQkSIlNraIGMuR YIfb2MjKgqXcgd5glKnfU3AyIHO+BQWHyOae2lWkZ9sM/fCqf2Xbgsjb17YjTRmAzx4u wg6pyJhkHJB4/6ZbHxq2B2aFj0gPnkMSP8R6wCkB00LFynojJ+1GAgi8eeKTRSpIbr5v bU+vtB3h7fjQUlEEdapZ86Nrw9EZakJs5+qZpLummK7krqTV9V/TcnduG94FoW+CzzqX ErZPibNOqxT4D7LZG0GkmiehYHpyZER2hsgLNiaPICdsg6vy4GZHdUHdzqPwFGtKXMLe LZuQ== X-Received: by 10.14.213.199 with SMTP id a47mr30078140eep.31.1361725915343; Sun, 24 Feb 2013 09:11:55 -0800 (PST) Received: from [127.0.0.1] (ashlynn.lippux.de. [5.9.218.242]) by mx.google.com with ESMTPS id q5sm14391557eeo.17.2013.02.24.09.11.52 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sun, 24 Feb 2013 09:11:54 -0800 (PST) Message-ID: <512A49D5.2040905@gmail.com> Date: Sun, 24 Feb 2013 18:11:49 +0100 From: tech mailinglists User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130215 Thunderbird/17.0.3 MIME-Version: 1.0 To: =?ISO-8859-15?Q?Roger_Pau_Monn=E9?= References: <51279FA1.2090809@citrix.com> <51287A18.7040200@citrix.com> In-Reply-To: <51287A18.7040200@citrix.com> Cc: xen-users Subject: Re: [Xen-users] Trouble booting FreeBSD i386 PV 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: quoted-printable Content-Type: text/plain; charset="iso-8859-15"; Format="flowed" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org Am 23.02.2013 09:13, schrieb Roger Pau Monn=E9: > On 22/02/13 19:30, tech mailinglists wrote: >> Hello Roger, >> >> >> I tried a further thing in the kernel configuration. I remove the option >> KBD_INSTALL_CDEV and now I am no longer getting dropped to a minimal >> console. The boot now looks like this: >> >> Parsing config from /root/xen/freebsd-test.cfg >> libxl: error: libxl_dm.c:1212:device_model_spawn_outcome: domain 20 >> device model: spawn failed (rc=3D-3) >> libxl: error: libxl_qmp.c:641:libxl__qmp_initialize: Connection error: >> No such file or directory >> Daemon running with PID 4383 >> WARNING: loader(8) metadata is missing! >> GDB: no debug ports present >> KDB: debugger backends: ddb >> KDB: current backend: ddb >> APIC: Using the MPTable enumerator. >> SMP: Added CPU 0 (BSP) >> Copyright (c) 1992-2012 The FreeBSD Project. >> Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 >> The Regents of the University of California. All rights reserve= d. >> FreeBSD is a registered trademark of The FreeBSD Foundation. >> FreeBSD 9.1-RELEASE #1 r247145M: Fri Feb 22 18:26:55 CET 2013 >> root@build:/usr/obj/usr/src/sys/XEN i386 >> Xen reported: 3341.754 MHz processor. >> Timecounter "ixen" frequency 1953125 Hz quality 0 >> CPU: Intel(R) Core(TM) i7 CPU 975 @ 3.33GHz (3341.75-MHz >> 686-class CPU) >> Origin =3D "GenuineIntel" Id =3D 0x106a5 Family =3D 6 Model =3D 1a >> Stepping =3D 5 >> = >> Features=3D0xbfe3fbff >> = >> Features2=3D0x98e3bd >> AMD Features=3D0x28100000 >> AMD Features2=3D0x1 >> >> Data TLB: 4 KB pages, 4-way set associative, 64 entries >> 1st-level data cache: 32 KB, 8-way set associative, 64 byte line size >> L2 cache: 256 kbytes, 8-way associative, 64 bytes/line >> real memory =3D 536870912 (512 MB) >> Physical memory chunk(s): >> 0x0000000000670000 - 0x000000001f628fff, 519802880 bytes (126905 pages) >> avail memory =3D 516833280 (492 MB) >> INTR: Adding local APIC 0 as a target >> ULE: setup cpu 0 >> [XEN] IPI cpu=3D0 irq=3D128 vector=3DRESCHEDULE_VECTOR (0) >> [XEN] IPI cpu=3D0 irq=3D129 vector=3DCALL_FUNCTION_VECTOR (1) >> Event-channel device installed. >> random: >> io: >> mem: >> Pentium Pro MTRR support enabled >> null: >> nfslock: pseudo-device >> [XEN] xen_rtc_probe: probing Hypervisor RTC clock >> rtc0: on motherboard >> [XEN] xen_rtc_attach: attaching Hypervisor RTC clock >> rtc0: registered as a time-of-day clock (resolution 1000000us, >> adjustment 0.500000000s) >> xenstore0: on motherboard >> Grant table initialized >> xc0: on motherboard >> Device configuration finished. >> procfs registered >> Event timer "ixen" quality 600 >> Timecounters tick every 10.000 msec >> lo0: bpf attached >> xenbusb_front0: on xenstore0 >> xenbusb_add_device: Device device/suspend/event-channel ignored. State 6 >> xn0: at device/vif/0 on xenbusb_front0 >> xn0: bpf attached >> xn0: Ethernet address: 00:16:3e:44:b1:b9 >> xenbusb_back0: on xenstore0 >> xctrl0: on xenstore0 >> xn0: backend features: feature-sg feature-gso-tcp4 >> [XEN] hypervisor wallclock nudged; nudging TOD. >> run_interrupt_driven_hooks: still waiting after 60 seconds for >> xenbus_free_evtchn >> [XEN] hypervisor wallclock nudged; nudging TOD. >> run_interrupt_driven_hooks: still waiting after 120 seconds for >> xenbus_free_evtchn >> run_interrupt_driven_hooks: still waiting after 180 seconds for >> xenbus_free_evtchn >> run_interrupt_driven_hooks: still waiting after 240 seconds for >> xenbus_free_evtchn >> run_interrupt_driven_hooks: still waiting after 300 seconds for >> xenbus_free_evtchn >> [XEN] hypervisor wallclock nudged; nudging TOD. >> [XEN] hypervisor wallclock nudged; nudging TOD. >> [XEN] hypervisor wallclock nudged; nudging TOD. >> >> I will test HVM and PVHVM but in the past I had no problems with this. >> It would be greate to have pure PV mode. The only thing which confuses >> me is the libxl related error on the domain creation: >> >> Parsing config from /root/xen/freebsd-test.cfg >> libxl: error: libxl_dm.c:1212:device_model_spawn_outcome: domain 20 >> device model: spawn failed (rc=3D-3) >> libxl: error: libxl_qmp.c:641:libxl__qmp_initialize: Connection error: >> No such file or directory >> >> I know that in a few cases PV guests have QEmu process but I can not say >> while this failes. Eventually there is something not compiled in, into >> Xen or the toolstack? > PV guests use Qemu to provide a block backend for raw file images, so if > Qemu fails to start your PV guest won't we able to access the hard > drive, that could be the reason why the FreeBSD PV guest is unable to > boot. Could you check Qemu log in /var/log/xen/qemu-dm-freebsd.log? > >> I saw that you have made a talk on FOSDEM about BSD and PVH. I >> downloaded the slide PDF but I am not able to open the document. It says >> that the document is corrupted. Am I doing a mistake? Or is there a >> problem with the document on the FOSDEM page. > I've just checked and the slides look OK to me, I'm able to open them > without problems. SHA1 sum: > > 0b0070149e0b4cf0b5557230793acccd1291ccde new_xen_paravirt_mode.pdf > I was able to fix the Qemu related problem, it was simply a missing = dependency. After I installed this I could start the guest to the point = that it can't find the root partition (ZFS). I thought that I have to do = it with PV-GRUB but the normal PV-GRUB don't support ZFS so I searched = and found this on github: https://github.com/aszeszo/pv-grub I was able to cross compile this to x86_32 and so it can read the ZFS = disk. But when I try to boot the kernel from /boot/kernel/kernel I get = into the mountroot prompt. And when I try chainloading (I read that this = would be the only way) I get this error: xc: error: panic: xc_dom_core.c:587: xc_dom_find_loader: no loader = found: Invalid kernel xc_dom_parse_image returned -1 close(3) Error 9: Unknown boot failure So is there a way to parse a kernel parameter to help the kernel to find = the ZFS volume or can a loader so like (/boot/loader, /boot/zfsloader) = be loaded with PV-GRUB? Would be great when someone could help me I think I am not far away to = have a working PV FreeBSD DomU with a filesystem which is support by = FreeBSD and Linux so this would be very great. Best Regards _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Sun Feb 24 17:13:01 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sun, 24 Feb 2013 17:13: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 1U9f7G-0000TR-Jo; Sun, 24 Feb 2013 17:11:58 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U9f7F-0000TF-FL for xen-users@lists.xen.org; Sun, 24 Feb 2013 17:11:57 +0000 Received: from [85.158.137.99:33159] by server-1.bemta-3.messagelabs.com id BE/33-08955-CD94A215; Sun, 24 Feb 2013 17:11:56 +0000 X-Env-Sender: mailinglists.tech@gmail.com X-Msg-Ref: server-16.tower-217.messagelabs.com!1361725915!17113870!1 X-Originating-IP: [209.85.215.170] X-SpamReason: No, hits=0.2 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, RCVD_ILLEGAL_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 27343 invoked from network); 24 Feb 2013 17:11:55 -0000 Received: from mail-ea0-f170.google.com (HELO mail-ea0-f170.google.com) (209.85.215.170) by server-16.tower-217.messagelabs.com with RC4-SHA encrypted SMTP; 24 Feb 2013 17:11:55 -0000 Received: by mail-ea0-f170.google.com with SMTP id a11so932080eaa.29 for ; Sun, 24 Feb 2013 09:11:55 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=JfbsiYOkhhB8O0z17i1Mt7eou9iQ8+XdR9IIYEWquuA=; b=jEsNOesFnFlJdGiBAqTyV03uNlan4dICtT7mPhyPSHn/MyEKdJSuEQkSIlNraIGMuR YIfb2MjKgqXcgd5glKnfU3AyIHO+BQWHyOae2lWkZ9sM/fCqf2Xbgsjb17YjTRmAzx4u wg6pyJhkHJB4/6ZbHxq2B2aFj0gPnkMSP8R6wCkB00LFynojJ+1GAgi8eeKTRSpIbr5v bU+vtB3h7fjQUlEEdapZ86Nrw9EZakJs5+qZpLummK7krqTV9V/TcnduG94FoW+CzzqX ErZPibNOqxT4D7LZG0GkmiehYHpyZER2hsgLNiaPICdsg6vy4GZHdUHdzqPwFGtKXMLe LZuQ== X-Received: by 10.14.213.199 with SMTP id a47mr30078140eep.31.1361725915343; Sun, 24 Feb 2013 09:11:55 -0800 (PST) Received: from [127.0.0.1] (ashlynn.lippux.de. [5.9.218.242]) by mx.google.com with ESMTPS id q5sm14391557eeo.17.2013.02.24.09.11.52 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sun, 24 Feb 2013 09:11:54 -0800 (PST) Message-ID: <512A49D5.2040905@gmail.com> Date: Sun, 24 Feb 2013 18:11:49 +0100 From: tech mailinglists User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130215 Thunderbird/17.0.3 MIME-Version: 1.0 To: =?ISO-8859-15?Q?Roger_Pau_Monn=E9?= References: <51279FA1.2090809@citrix.com> <51287A18.7040200@citrix.com> In-Reply-To: <51287A18.7040200@citrix.com> Cc: xen-users Subject: Re: [Xen-users] Trouble booting FreeBSD i386 PV 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: quoted-printable Content-Type: text/plain; charset="iso-8859-15"; Format="flowed" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org Am 23.02.2013 09:13, schrieb Roger Pau Monn=E9: > On 22/02/13 19:30, tech mailinglists wrote: >> Hello Roger, >> >> >> I tried a further thing in the kernel configuration. I remove the option >> KBD_INSTALL_CDEV and now I am no longer getting dropped to a minimal >> console. The boot now looks like this: >> >> Parsing config from /root/xen/freebsd-test.cfg >> libxl: error: libxl_dm.c:1212:device_model_spawn_outcome: domain 20 >> device model: spawn failed (rc=3D-3) >> libxl: error: libxl_qmp.c:641:libxl__qmp_initialize: Connection error: >> No such file or directory >> Daemon running with PID 4383 >> WARNING: loader(8) metadata is missing! >> GDB: no debug ports present >> KDB: debugger backends: ddb >> KDB: current backend: ddb >> APIC: Using the MPTable enumerator. >> SMP: Added CPU 0 (BSP) >> Copyright (c) 1992-2012 The FreeBSD Project. >> Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 >> The Regents of the University of California. All rights reserve= d. >> FreeBSD is a registered trademark of The FreeBSD Foundation. >> FreeBSD 9.1-RELEASE #1 r247145M: Fri Feb 22 18:26:55 CET 2013 >> root@build:/usr/obj/usr/src/sys/XEN i386 >> Xen reported: 3341.754 MHz processor. >> Timecounter "ixen" frequency 1953125 Hz quality 0 >> CPU: Intel(R) Core(TM) i7 CPU 975 @ 3.33GHz (3341.75-MHz >> 686-class CPU) >> Origin =3D "GenuineIntel" Id =3D 0x106a5 Family =3D 6 Model =3D 1a >> Stepping =3D 5 >> = >> Features=3D0xbfe3fbff >> = >> Features2=3D0x98e3bd >> AMD Features=3D0x28100000 >> AMD Features2=3D0x1 >> >> Data TLB: 4 KB pages, 4-way set associative, 64 entries >> 1st-level data cache: 32 KB, 8-way set associative, 64 byte line size >> L2 cache: 256 kbytes, 8-way associative, 64 bytes/line >> real memory =3D 536870912 (512 MB) >> Physical memory chunk(s): >> 0x0000000000670000 - 0x000000001f628fff, 519802880 bytes (126905 pages) >> avail memory =3D 516833280 (492 MB) >> INTR: Adding local APIC 0 as a target >> ULE: setup cpu 0 >> [XEN] IPI cpu=3D0 irq=3D128 vector=3DRESCHEDULE_VECTOR (0) >> [XEN] IPI cpu=3D0 irq=3D129 vector=3DCALL_FUNCTION_VECTOR (1) >> Event-channel device installed. >> random: >> io: >> mem: >> Pentium Pro MTRR support enabled >> null: >> nfslock: pseudo-device >> [XEN] xen_rtc_probe: probing Hypervisor RTC clock >> rtc0: on motherboard >> [XEN] xen_rtc_attach: attaching Hypervisor RTC clock >> rtc0: registered as a time-of-day clock (resolution 1000000us, >> adjustment 0.500000000s) >> xenstore0: on motherboard >> Grant table initialized >> xc0: on motherboard >> Device configuration finished. >> procfs registered >> Event timer "ixen" quality 600 >> Timecounters tick every 10.000 msec >> lo0: bpf attached >> xenbusb_front0: on xenstore0 >> xenbusb_add_device: Device device/suspend/event-channel ignored. State 6 >> xn0: at device/vif/0 on xenbusb_front0 >> xn0: bpf attached >> xn0: Ethernet address: 00:16:3e:44:b1:b9 >> xenbusb_back0: on xenstore0 >> xctrl0: on xenstore0 >> xn0: backend features: feature-sg feature-gso-tcp4 >> [XEN] hypervisor wallclock nudged; nudging TOD. >> run_interrupt_driven_hooks: still waiting after 60 seconds for >> xenbus_free_evtchn >> [XEN] hypervisor wallclock nudged; nudging TOD. >> run_interrupt_driven_hooks: still waiting after 120 seconds for >> xenbus_free_evtchn >> run_interrupt_driven_hooks: still waiting after 180 seconds for >> xenbus_free_evtchn >> run_interrupt_driven_hooks: still waiting after 240 seconds for >> xenbus_free_evtchn >> run_interrupt_driven_hooks: still waiting after 300 seconds for >> xenbus_free_evtchn >> [XEN] hypervisor wallclock nudged; nudging TOD. >> [XEN] hypervisor wallclock nudged; nudging TOD. >> [XEN] hypervisor wallclock nudged; nudging TOD. >> >> I will test HVM and PVHVM but in the past I had no problems with this. >> It would be greate to have pure PV mode. The only thing which confuses >> me is the libxl related error on the domain creation: >> >> Parsing config from /root/xen/freebsd-test.cfg >> libxl: error: libxl_dm.c:1212:device_model_spawn_outcome: domain 20 >> device model: spawn failed (rc=3D-3) >> libxl: error: libxl_qmp.c:641:libxl__qmp_initialize: Connection error: >> No such file or directory >> >> I know that in a few cases PV guests have QEmu process but I can not say >> while this failes. Eventually there is something not compiled in, into >> Xen or the toolstack? > PV guests use Qemu to provide a block backend for raw file images, so if > Qemu fails to start your PV guest won't we able to access the hard > drive, that could be the reason why the FreeBSD PV guest is unable to > boot. Could you check Qemu log in /var/log/xen/qemu-dm-freebsd.log? > >> I saw that you have made a talk on FOSDEM about BSD and PVH. I >> downloaded the slide PDF but I am not able to open the document. It says >> that the document is corrupted. Am I doing a mistake? Or is there a >> problem with the document on the FOSDEM page. > I've just checked and the slides look OK to me, I'm able to open them > without problems. SHA1 sum: > > 0b0070149e0b4cf0b5557230793acccd1291ccde new_xen_paravirt_mode.pdf > I was able to fix the Qemu related problem, it was simply a missing = dependency. After I installed this I could start the guest to the point = that it can't find the root partition (ZFS). I thought that I have to do = it with PV-GRUB but the normal PV-GRUB don't support ZFS so I searched = and found this on github: https://github.com/aszeszo/pv-grub I was able to cross compile this to x86_32 and so it can read the ZFS = disk. But when I try to boot the kernel from /boot/kernel/kernel I get = into the mountroot prompt. And when I try chainloading (I read that this = would be the only way) I get this error: xc: error: panic: xc_dom_core.c:587: xc_dom_find_loader: no loader = found: Invalid kernel xc_dom_parse_image returned -1 close(3) Error 9: Unknown boot failure So is there a way to parse a kernel parameter to help the kernel to find = the ZFS volume or can a loader so like (/boot/loader, /boot/zfsloader) = be loaded with PV-GRUB? Would be great when someone could help me I think I am not far away to = have a working PV FreeBSD DomU with a filesystem which is support by = FreeBSD and Linux so this would be very great. Best Regards _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Sun Feb 24 21:59:31 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sun, 24 Feb 2013 21:59: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 1U9ja3-00068t-HJ; Sun, 24 Feb 2013 21:57:59 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U9ja1-00068o-SB for xen-users@lists.xen.org; Sun, 24 Feb 2013 21:57:58 +0000 Received: from [193.109.254.147:35185] by server-15.bemta-14.messagelabs.com id 38/D2-24599-5EC8A215; Sun, 24 Feb 2013 21:57:57 +0000 X-Env-Sender: tosterman@gmail.com X-Msg-Ref: server-3.tower-27.messagelabs.com!1361743068!8954968!1 X-Originating-IP: [209.85.210.180] 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.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 10090 invoked from network); 24 Feb 2013 21:57:50 -0000 Received: from mail-ia0-f180.google.com (HELO mail-ia0-f180.google.com) (209.85.210.180) by server-3.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 24 Feb 2013 21:57:50 -0000 Received: by mail-ia0-f180.google.com with SMTP id f27so1933440iae.39 for ; Sun, 24 Feb 2013 13:57:48 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:reply-to:in-reply-to:references:date :message-id:subject:from:to:content-type; bh=BBOh0elhhdlJh2dz3BtinQGS3IsOHtieJGk8g9j2rh8=; b=CMERzb/j3y3LRcoIPeOG4OsRJgCb1bIQVXOi6iE4HdZmMp5BCMlZAfOM8cvKkbRSn1 g896EAhxzNTT/WacDjasTevY2yZNwxCk71X6dnXWfloLrnLQc1a9OJdAPx+nudYtBiCG IiY5kICYdTH0Nviz9L84no+WVbwZv8FdSM0PE/pffrmAp0t53pMMoi2Se22/saeDguBY ILT1le7CDfxRlN1Q7UfK1twj40doOLJZtzywCcKUic3TvlzVL6EYGE+rpIMWlvcQnQUe 94CD2I/SZO6+QIxW+E8nSpwVwYHp4Jio81KN1qP15kTF4v5Gy4Pt+WCrkf9G9GjPTKBn BrWg== MIME-Version: 1.0 X-Received: by 10.50.197.131 with SMTP id iu3mr2443291igc.109.1361743068252; Sun, 24 Feb 2013 13:57:48 -0800 (PST) Received: by 10.64.60.136 with HTTP; Sun, 24 Feb 2013 13:57:48 -0800 (PST) In-Reply-To: References: Date: Sun, 24 Feb 2013 16:57:48 -0500 Message-ID: From: Travis Osterman To: xen-users Subject: Re: [Xen-users] pv guest fails to start after 4.2 upgrade X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: travis@wsor.net List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: 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 running xen on gentoo (3.7.0 hardened) and upgraded from 4.1 to >>> 4.2 yesterday as 4.2 is marked as stable in the portage tree. >>> Afterwards, I cannot start my guests and get the following error >>> (currently running 4.2.1). Any help in troubleshooting would be >>> greatly appreciated. Thanks in advance. >>> >>> -- T >>> >>> # xl create -c /data/xen/prime.pv >>> libxl: error: libxl_dm.c:1212:device_model_spawn_outcome: domain 3 >>> device model: spawn failed (rc=-3) >>> libxl: error: libxl_qmp.c:641:libxl__qmp_initialize: Connection error: >>> No such file or directory >>> Daemon running with PID 8701 > ... >>> >>> ================== ATTACHMENTS ============================ >>> >>> xl -vvv create -c /data/xen/prime.pv >>> http://pastebin.com/92PW3QRH >>> >>> xl dmesg >>> http://pastebin.com/ba2Xxv7w >>> >>> emerge --info (system info) >>> http://pastebin.com/VKSfKjCW >>> >> Hello Travis, >> >> pleas check /var/log/xen/domainname-dm.log. ... reason was >> that I forgot to install a special dependency in my case libsdl > > I have media-libs/libsdl-1.2.15-r2 installed. No change after rebuilding. > > Here is the guest log: > > # cat /var/log/xen/xl-prime.log > Waiting for domain prime (domid 8) to die [pid 14679] > libxl: debug: libxl_event.c:512:libxl__ev_xswatch_register: watch > w=0x626cf0 wpath=@releaseDomain token=3/0: register slotnum=3 > libxl: debug: libxl_event.c:457:watchfd_callback: watch w=0x626cf0 > wpath=@releaseDomain token=3/0: event epath=@releaseDomain > libxl: debug: libxl.c:1015:domain_death_xswatch_callback: > [evg=0x624fe0:8] from domid=8 nentries=1 rc=1 > libxl: debug: libxl.c:1026:domain_death_xswatch_callback: > [evg=0x624fe0:8] got=domaininfos[0] got->domain=8 > libxl: debug: libxl.c:1053:domain_death_xswatch_callback: exists > shutdown_reported=0 dominf.flags=ffff0020 > libxl: debug: libxl.c:1019:domain_death_xswatch_callback: [evg=0] all reported > libxl: debug: libxl.c:1083:domain_death_xswatch_callback: domain death > search done I also tried to take pvgrub out of the picture so I mounted the image and copied my initrd and kernel to the dom0 file system and updated my config with the appropriate ramdisk and kernel lines. Full output without pvgrub http://pastebin.com/c7VWWwXk Which dropped me in a shell asking for my root partition (progress). No /dev/xvd? or /dev/sd? listed so I shut down the guest and mounted my disk as a physical device (via loopback) instead of image. Here was a the change: /data/xen/prime.pv (-)disk = ['file:/data/xen/prime.img,xvda,w'] (+)disk = ['phy:/dev/loop0p2,xvda,w'] (-)kernel = "/usr/lib/xen/boot/pv-grub-x86_64.gz" (+)kernel = "/data/xen/kernel-genkernel-x86_64-3.7.5-hardened-2013-02-18-1632" (+)ramdisk = "/data/xen/initramfs-genkernel-x86_64-3.7.5-hardened-2013-02-18-1632" Anyone have any guess why xen-tools 4.2.1 isn't able to read my disk image files? Everything worked in 4.1. Thanks. -- T _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Sun Feb 24 21:59:31 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sun, 24 Feb 2013 21:59: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 1U9ja3-00068t-HJ; Sun, 24 Feb 2013 21:57:59 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U9ja1-00068o-SB for xen-users@lists.xen.org; Sun, 24 Feb 2013 21:57:58 +0000 Received: from [193.109.254.147:35185] by server-15.bemta-14.messagelabs.com id 38/D2-24599-5EC8A215; Sun, 24 Feb 2013 21:57:57 +0000 X-Env-Sender: tosterman@gmail.com X-Msg-Ref: server-3.tower-27.messagelabs.com!1361743068!8954968!1 X-Originating-IP: [209.85.210.180] 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.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 10090 invoked from network); 24 Feb 2013 21:57:50 -0000 Received: from mail-ia0-f180.google.com (HELO mail-ia0-f180.google.com) (209.85.210.180) by server-3.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 24 Feb 2013 21:57:50 -0000 Received: by mail-ia0-f180.google.com with SMTP id f27so1933440iae.39 for ; Sun, 24 Feb 2013 13:57:48 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:reply-to:in-reply-to:references:date :message-id:subject:from:to:content-type; bh=BBOh0elhhdlJh2dz3BtinQGS3IsOHtieJGk8g9j2rh8=; b=CMERzb/j3y3LRcoIPeOG4OsRJgCb1bIQVXOi6iE4HdZmMp5BCMlZAfOM8cvKkbRSn1 g896EAhxzNTT/WacDjasTevY2yZNwxCk71X6dnXWfloLrnLQc1a9OJdAPx+nudYtBiCG IiY5kICYdTH0Nviz9L84no+WVbwZv8FdSM0PE/pffrmAp0t53pMMoi2Se22/saeDguBY ILT1le7CDfxRlN1Q7UfK1twj40doOLJZtzywCcKUic3TvlzVL6EYGE+rpIMWlvcQnQUe 94CD2I/SZO6+QIxW+E8nSpwVwYHp4Jio81KN1qP15kTF4v5Gy4Pt+WCrkf9G9GjPTKBn BrWg== MIME-Version: 1.0 X-Received: by 10.50.197.131 with SMTP id iu3mr2443291igc.109.1361743068252; Sun, 24 Feb 2013 13:57:48 -0800 (PST) Received: by 10.64.60.136 with HTTP; Sun, 24 Feb 2013 13:57:48 -0800 (PST) In-Reply-To: References: Date: Sun, 24 Feb 2013 16:57:48 -0500 Message-ID: From: Travis Osterman To: xen-users Subject: Re: [Xen-users] pv guest fails to start after 4.2 upgrade X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: travis@wsor.net List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: 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 running xen on gentoo (3.7.0 hardened) and upgraded from 4.1 to >>> 4.2 yesterday as 4.2 is marked as stable in the portage tree. >>> Afterwards, I cannot start my guests and get the following error >>> (currently running 4.2.1). Any help in troubleshooting would be >>> greatly appreciated. Thanks in advance. >>> >>> -- T >>> >>> # xl create -c /data/xen/prime.pv >>> libxl: error: libxl_dm.c:1212:device_model_spawn_outcome: domain 3 >>> device model: spawn failed (rc=-3) >>> libxl: error: libxl_qmp.c:641:libxl__qmp_initialize: Connection error: >>> No such file or directory >>> Daemon running with PID 8701 > ... >>> >>> ================== ATTACHMENTS ============================ >>> >>> xl -vvv create -c /data/xen/prime.pv >>> http://pastebin.com/92PW3QRH >>> >>> xl dmesg >>> http://pastebin.com/ba2Xxv7w >>> >>> emerge --info (system info) >>> http://pastebin.com/VKSfKjCW >>> >> Hello Travis, >> >> pleas check /var/log/xen/domainname-dm.log. ... reason was >> that I forgot to install a special dependency in my case libsdl > > I have media-libs/libsdl-1.2.15-r2 installed. No change after rebuilding. > > Here is the guest log: > > # cat /var/log/xen/xl-prime.log > Waiting for domain prime (domid 8) to die [pid 14679] > libxl: debug: libxl_event.c:512:libxl__ev_xswatch_register: watch > w=0x626cf0 wpath=@releaseDomain token=3/0: register slotnum=3 > libxl: debug: libxl_event.c:457:watchfd_callback: watch w=0x626cf0 > wpath=@releaseDomain token=3/0: event epath=@releaseDomain > libxl: debug: libxl.c:1015:domain_death_xswatch_callback: > [evg=0x624fe0:8] from domid=8 nentries=1 rc=1 > libxl: debug: libxl.c:1026:domain_death_xswatch_callback: > [evg=0x624fe0:8] got=domaininfos[0] got->domain=8 > libxl: debug: libxl.c:1053:domain_death_xswatch_callback: exists > shutdown_reported=0 dominf.flags=ffff0020 > libxl: debug: libxl.c:1019:domain_death_xswatch_callback: [evg=0] all reported > libxl: debug: libxl.c:1083:domain_death_xswatch_callback: domain death > search done I also tried to take pvgrub out of the picture so I mounted the image and copied my initrd and kernel to the dom0 file system and updated my config with the appropriate ramdisk and kernel lines. Full output without pvgrub http://pastebin.com/c7VWWwXk Which dropped me in a shell asking for my root partition (progress). No /dev/xvd? or /dev/sd? listed so I shut down the guest and mounted my disk as a physical device (via loopback) instead of image. Here was a the change: /data/xen/prime.pv (-)disk = ['file:/data/xen/prime.img,xvda,w'] (+)disk = ['phy:/dev/loop0p2,xvda,w'] (-)kernel = "/usr/lib/xen/boot/pv-grub-x86_64.gz" (+)kernel = "/data/xen/kernel-genkernel-x86_64-3.7.5-hardened-2013-02-18-1632" (+)ramdisk = "/data/xen/initramfs-genkernel-x86_64-3.7.5-hardened-2013-02-18-1632" Anyone have any guess why xen-tools 4.2.1 isn't able to read my disk image files? Everything worked in 4.1. Thanks. -- T _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Sun Feb 24 22:30:29 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sun, 24 Feb 2013 22:30: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 1U9k49-00078t-TG; Sun, 24 Feb 2013 22:29:05 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U9ikH-0005Ht-SL; Sun, 24 Feb 2013 21:04:30 +0000 Received: from [85.158.139.83:53723] by server-15.bemta-5.messagelabs.com id 20/58-18914-D508A215; Sun, 24 Feb 2013 21:04:29 +0000 X-Env-Sender: greg@wind.enjellic.com X-Msg-Ref: server-7.tower-182.messagelabs.com!1361739867!23549157!1 X-Originating-IP: [76.10.64.91] X-SpamReason: No, hits=0.5 required=7.0 tests=BODY_RANDOM_LONG X-StarScan-Received: X-StarScan-Version: 6.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 2962 invoked from network); 24 Feb 2013 21:04:28 -0000 Received: from wind.enjellic.com (HELO wind.enjellic.com) (76.10.64.91) by server-7.tower-182.messagelabs.com with SMTP; 24 Feb 2013 21:04:28 -0000 Received: from wind.enjellic.com (localhost [127.0.0.1]) by wind.enjellic.com (8.14.3/8.14.3) with ESMTP id r1OL3tLL030829; Sun, 24 Feb 2013 15:03:55 -0600 Received: (from greg@localhost) by wind.enjellic.com (8.14.3/8.14.3/Submit) id r1OL3tAg030828; Sun, 24 Feb 2013 15:03:55 -0600 Date: Sun, 24 Feb 2013 15:03:55 -0600 From: "Dr. Greg Wettstein" Message-Id: <201302242103.r1OL3tAg030828@wind.enjellic.com> X-Mailer: Mail User's Shell (7.2.6-ESD1.0 03/31/2012) To: xen-users@lists.xen.org, xen-devel@lists.xen.org, scst-devel@lists.sourceforge.net X-Greylist: Sender passed SPF test, not delayed by milter-greylist-4.2.3 (wind.enjellic.com [0.0.0.0]); Sun, 24 Feb 2013 15:03:55 -0600 (CST) X-Mailman-Approved-At: Sun, 24 Feb 2013 22:29:04 +0000 Subject: [Xen-users] Xen-SAN release. X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: xen@enjellic.com List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , MIME-Version: 1.0 Content-Type: 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 afternoon, hope the weekend is going well for everyone. Izzy the Golden Retriever, on behalf of Enjellic Systems Development, would like to announce the release of the Xen-SAN system. This is a package which provides hotplug support and documentation for allowing Xen DomU guests to participate as first class initiators in a Storage Area Network (SAN). The package can be downloaded from the following URL: ftp://ftp.enjellic.com/pub/xen/Xen-SAN-0.1.0.tar.gz This implementation provides support for dynamic creation and termination of SAN connections at the request of the XL toolstack. The block devices implemented by these connections are exported by the blkback interface to the guests. This allows storage for Xen guests to be managed as any other initiator in a SAN environment with the advantage of the guest requiring no knowledge of SAN implementation mechanics. Due to interest in the package and development and testing deadlines this release contains support only for iSCSI initiators. NPIV support for fibre-channel SAN's is under testing and will be included in a subsequent release. The package has been tested extensively with the following components: Xen 4.2.1 open-iscsi 2.0.873 kernel.org Linux 3.4.x Dom0/DomU SCST 2.2.x target implementation The goal of the sub-system is to operate as standalone hotplug scripts. A small modification is required to extend lock coverage in the 'block' script. A modified 'block' script, which has been tested to function identically to the script released with the Xen sources, is included. This package WILL NOT function properly with the default script. Since development in and function of the Linux/Xen hotplug environment is best described as 'intrigueing' we are interested in feedback on issues which may exist outside our customized storage and virtualization environment. Due to the complexity of the sub-systems involved users are STRONGLY recommended to review the included documentation. We hope the open-storage and virtualization communities find this to be a useful contribution to the eco-system. Greg and Izzy As always, Dr. G.W. Wettstein, Ph.D. Enjellic Systems Development, LLC. 4206 N. 19th Ave. Specializing in information infra-structure Fargo, ND 58102 development. PH: 701-281-1686 FAX: 701-281-3949 EMAIL: greg@enjellic.com ------------------------------------------------------------------------------ "Don't worry about people stealing your ideas. If your ideas are any good, you'll have to ram them down people's throats." -- Howard Aiken _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Sun Feb 24 22:30:29 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sun, 24 Feb 2013 22:30: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 1U9k49-00078t-TG; Sun, 24 Feb 2013 22:29:05 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U9ikH-0005Ht-SL; Sun, 24 Feb 2013 21:04:30 +0000 Received: from [85.158.139.83:53723] by server-15.bemta-5.messagelabs.com id 20/58-18914-D508A215; Sun, 24 Feb 2013 21:04:29 +0000 X-Env-Sender: greg@wind.enjellic.com X-Msg-Ref: server-7.tower-182.messagelabs.com!1361739867!23549157!1 X-Originating-IP: [76.10.64.91] X-SpamReason: No, hits=0.5 required=7.0 tests=BODY_RANDOM_LONG X-StarScan-Received: X-StarScan-Version: 6.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 2962 invoked from network); 24 Feb 2013 21:04:28 -0000 Received: from wind.enjellic.com (HELO wind.enjellic.com) (76.10.64.91) by server-7.tower-182.messagelabs.com with SMTP; 24 Feb 2013 21:04:28 -0000 Received: from wind.enjellic.com (localhost [127.0.0.1]) by wind.enjellic.com (8.14.3/8.14.3) with ESMTP id r1OL3tLL030829; Sun, 24 Feb 2013 15:03:55 -0600 Received: (from greg@localhost) by wind.enjellic.com (8.14.3/8.14.3/Submit) id r1OL3tAg030828; Sun, 24 Feb 2013 15:03:55 -0600 Date: Sun, 24 Feb 2013 15:03:55 -0600 From: "Dr. Greg Wettstein" Message-Id: <201302242103.r1OL3tAg030828@wind.enjellic.com> X-Mailer: Mail User's Shell (7.2.6-ESD1.0 03/31/2012) To: xen-users@lists.xen.org, xen-devel@lists.xen.org, scst-devel@lists.sourceforge.net X-Greylist: Sender passed SPF test, not delayed by milter-greylist-4.2.3 (wind.enjellic.com [0.0.0.0]); Sun, 24 Feb 2013 15:03:55 -0600 (CST) X-Mailman-Approved-At: Sun, 24 Feb 2013 22:29:04 +0000 Subject: [Xen-users] Xen-SAN release. X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: xen@enjellic.com List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , MIME-Version: 1.0 Content-Type: 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 afternoon, hope the weekend is going well for everyone. Izzy the Golden Retriever, on behalf of Enjellic Systems Development, would like to announce the release of the Xen-SAN system. This is a package which provides hotplug support and documentation for allowing Xen DomU guests to participate as first class initiators in a Storage Area Network (SAN). The package can be downloaded from the following URL: ftp://ftp.enjellic.com/pub/xen/Xen-SAN-0.1.0.tar.gz This implementation provides support for dynamic creation and termination of SAN connections at the request of the XL toolstack. The block devices implemented by these connections are exported by the blkback interface to the guests. This allows storage for Xen guests to be managed as any other initiator in a SAN environment with the advantage of the guest requiring no knowledge of SAN implementation mechanics. Due to interest in the package and development and testing deadlines this release contains support only for iSCSI initiators. NPIV support for fibre-channel SAN's is under testing and will be included in a subsequent release. The package has been tested extensively with the following components: Xen 4.2.1 open-iscsi 2.0.873 kernel.org Linux 3.4.x Dom0/DomU SCST 2.2.x target implementation The goal of the sub-system is to operate as standalone hotplug scripts. A small modification is required to extend lock coverage in the 'block' script. A modified 'block' script, which has been tested to function identically to the script released with the Xen sources, is included. This package WILL NOT function properly with the default script. Since development in and function of the Linux/Xen hotplug environment is best described as 'intrigueing' we are interested in feedback on issues which may exist outside our customized storage and virtualization environment. Due to the complexity of the sub-systems involved users are STRONGLY recommended to review the included documentation. We hope the open-storage and virtualization communities find this to be a useful contribution to the eco-system. Greg and Izzy As always, Dr. G.W. Wettstein, Ph.D. Enjellic Systems Development, LLC. 4206 N. 19th Ave. Specializing in information infra-structure Fargo, ND 58102 development. PH: 701-281-1686 FAX: 701-281-3949 EMAIL: greg@enjellic.com ------------------------------------------------------------------------------ "Don't worry about people stealing your ideas. If your ideas are any good, you'll have to ram them down people's throats." -- Howard Aiken _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Mon Feb 25 08:10:15 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 25 Feb 2013 08:10: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 1U9t79-0007PK-DH; Mon, 25 Feb 2013 08:08:47 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U9t78-0007PF-1k for xen-users@lists.xen.org; Mon, 25 Feb 2013 08:08:46 +0000 Received: from [85.158.138.51:42592] by server-11.bemta-3.messagelabs.com id 8F/3C-10249-C0C1B215; Mon, 25 Feb 2013 08:08:44 +0000 X-Env-Sender: mailing.son@gmail.com X-Msg-Ref: server-4.tower-174.messagelabs.com!1361779706!28989270!1 X-Originating-IP: [74.125.83.54] 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.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 28578 invoked from network); 25 Feb 2013 08:08:27 -0000 Received: from mail-ee0-f54.google.com (HELO mail-ee0-f54.google.com) (74.125.83.54) by server-4.tower-174.messagelabs.com with RC4-SHA encrypted SMTP; 25 Feb 2013 08:08:27 -0000 Received: by mail-ee0-f54.google.com with SMTP id c41so1226404eek.41 for ; Mon, 25 Feb 2013 00:08:26 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:date:message-id:subject:from:to :content-type; bh=wkhI26XlgunDXAOtymwIsojEl3QoFaUpjDm75BabYw8=; b=qlqMTKwvhV85ntvM03X9DkeL87A4nlQJN8yNArnbc5N+1Ie86UabxwagWKPPYlcZC5 FhN3jGHW6Sl3T8x+QR+MCPalrOa4K696ZEb/Ch9F6ds5Jbz3LAxmQONG/EffKCp1imjF gTaxZZx0+0o6bXLyUGwfdRaf+2wIX1sGnuO2xkhN/+CLUqwMeE5KbG2j7I751oe6/s9h +pjUvIJBZFkIniWq/9RFDA3Y5rYVspDTvgrxc5AOZVRpQzu+g4CdXESRkBP6OLgzAcg8 ZPhqGnFH5b+3LDTSnwNHGfosr940JfQv88c8l3Otn2Gtyyhslk+DRDI2VUqZJZTDh/3z tkJA== MIME-Version: 1.0 X-Received: by 10.14.218.71 with SMTP id j47mr36118610eep.28.1361779706587; Mon, 25 Feb 2013 00:08:26 -0800 (PST) Received: by 10.14.69.4 with HTTP; Mon, 25 Feb 2013 00:08:26 -0800 (PST) Date: Mon, 25 Feb 2013 17:08:26 +0900 Message-ID: From: Andrew Son To: xen-users@lists.xen.org Subject: [Xen-users] Hypervisor-mode(Intel VT-x) 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 Hi All, I confused with hypervisor-mode(Intel VT-x) and HVM. Does only HVM guest use hypervisor-mode? PV guest does not use Intel VT-x. Thanks, Andrew Son _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Mon Feb 25 08:10:15 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 25 Feb 2013 08:10: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 1U9t79-0007PK-DH; Mon, 25 Feb 2013 08:08:47 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U9t78-0007PF-1k for xen-users@lists.xen.org; Mon, 25 Feb 2013 08:08:46 +0000 Received: from [85.158.138.51:42592] by server-11.bemta-3.messagelabs.com id 8F/3C-10249-C0C1B215; Mon, 25 Feb 2013 08:08:44 +0000 X-Env-Sender: mailing.son@gmail.com X-Msg-Ref: server-4.tower-174.messagelabs.com!1361779706!28989270!1 X-Originating-IP: [74.125.83.54] 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.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 28578 invoked from network); 25 Feb 2013 08:08:27 -0000 Received: from mail-ee0-f54.google.com (HELO mail-ee0-f54.google.com) (74.125.83.54) by server-4.tower-174.messagelabs.com with RC4-SHA encrypted SMTP; 25 Feb 2013 08:08:27 -0000 Received: by mail-ee0-f54.google.com with SMTP id c41so1226404eek.41 for ; Mon, 25 Feb 2013 00:08:26 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:date:message-id:subject:from:to :content-type; bh=wkhI26XlgunDXAOtymwIsojEl3QoFaUpjDm75BabYw8=; b=qlqMTKwvhV85ntvM03X9DkeL87A4nlQJN8yNArnbc5N+1Ie86UabxwagWKPPYlcZC5 FhN3jGHW6Sl3T8x+QR+MCPalrOa4K696ZEb/Ch9F6ds5Jbz3LAxmQONG/EffKCp1imjF gTaxZZx0+0o6bXLyUGwfdRaf+2wIX1sGnuO2xkhN/+CLUqwMeE5KbG2j7I751oe6/s9h +pjUvIJBZFkIniWq/9RFDA3Y5rYVspDTvgrxc5AOZVRpQzu+g4CdXESRkBP6OLgzAcg8 ZPhqGnFH5b+3LDTSnwNHGfosr940JfQv88c8l3Otn2Gtyyhslk+DRDI2VUqZJZTDh/3z tkJA== MIME-Version: 1.0 X-Received: by 10.14.218.71 with SMTP id j47mr36118610eep.28.1361779706587; Mon, 25 Feb 2013 00:08:26 -0800 (PST) Received: by 10.14.69.4 with HTTP; Mon, 25 Feb 2013 00:08:26 -0800 (PST) Date: Mon, 25 Feb 2013 17:08:26 +0900 Message-ID: From: Andrew Son To: xen-users@lists.xen.org Subject: [Xen-users] Hypervisor-mode(Intel VT-x) 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 Hi All, I confused with hypervisor-mode(Intel VT-x) and HVM. Does only HVM guest use hypervisor-mode? PV guest does not use Intel VT-x. Thanks, Andrew Son _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Mon Feb 25 09:24:28 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 25 Feb 2013 09:24: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 1U9uHA-00013H-4b; Mon, 25 Feb 2013 09:23:12 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U9uH9-00013B-MK for xen-users@lists.xen.org; Mon, 25 Feb 2013 09:23:11 +0000 Received: from [85.158.143.99:62489] by server-3.bemta-4.messagelabs.com id AF/EC-02186-E7D2B215; Mon, 25 Feb 2013 09:23:10 +0000 X-Env-Sender: Ian.Campbell@citrix.com X-Msg-Ref: server-12.tower-216.messagelabs.com!1361784187!23774995!1 X-Originating-IP: [46.33.159.39] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNDYuMzMuMTU5LjM5ID0+IDIzOTg5\n X-StarScan-Received: X-StarScan-Version: 6.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 15059 invoked from network); 25 Feb 2013 09:23:07 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (46.33.159.39) by server-12.tower-216.messagelabs.com with RC4-SHA encrypted SMTP; 25 Feb 2013 09:23:07 -0000 X-IronPort-AV: E=Sophos;i="4.84,733,1355097600"; d="scan'208";a="1829879" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 25 Feb 2013 09:23:08 +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.297.1; Mon, 25 Feb 2013 09:23:07 +0000 Message-ID: <1361784186.26546.161.camel@zakaz.uk.xensource.com> From: Ian Campbell To: Yathindra Date: Mon, 25 Feb 2013 09:23:06 +0000 In-Reply-To: <51284379.3070608@cs.utah.edu> References: <5125DCBB.2080305@cs.utah.edu> <51284379.3070608@cs.utah.edu> Organization: Citrix Systems, Inc. X-Mailer: Evolution 3.4.4-1 MIME-Version: 1.0 Cc: "xen-users@lists.xen.org" Subject: Re: [Xen-users] Issuing hypercalls from Linux 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: , Content-Type: 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, 2013-02-23 at 04:20 +0000, Yathindra wrote: > On 2/21/2013 1:37 AM, Yathindra wrote: > > Hi, > > > > I have defined a new hypercall in Xen hypervisor. It is similar to > > do_domctl() > > in that I pass a single argument and use XEN_GUEST_HANDLE() to > > retrieve the > > arguments. Its currently working fine under Xen-4.3-unstable. > > > > Now I want to invoke this hypercall via Linux-3.7.5 Guest. How do I go > > about > > doing this. > > > > Thanks, > > Yathi > Hi, > > I followed a approach similar to do_physdev_op in Linux-3.7.5. > I have a similar set of files under include/xen/interface/ directory. > After plumbing everything when I execute my hypercall via Linux, > I get -14 (EFAULT) as the return value. I added printk's on the Xen > side to see if the hypercall is reaching Xen but it does not. > > Any general direction regarding this would be very helpful. EFAULT usually means that one of the pointers which you passed to the hypercall was not to correctly mapped memory. It might be useful to post your code for both sides of the equation (Linux & Xen). Ian. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Mon Feb 25 09:24:28 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 25 Feb 2013 09:24: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 1U9uHA-00013H-4b; Mon, 25 Feb 2013 09:23:12 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U9uH9-00013B-MK for xen-users@lists.xen.org; Mon, 25 Feb 2013 09:23:11 +0000 Received: from [85.158.143.99:62489] by server-3.bemta-4.messagelabs.com id AF/EC-02186-E7D2B215; Mon, 25 Feb 2013 09:23:10 +0000 X-Env-Sender: Ian.Campbell@citrix.com X-Msg-Ref: server-12.tower-216.messagelabs.com!1361784187!23774995!1 X-Originating-IP: [46.33.159.39] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNDYuMzMuMTU5LjM5ID0+IDIzOTg5\n X-StarScan-Received: X-StarScan-Version: 6.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 15059 invoked from network); 25 Feb 2013 09:23:07 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (46.33.159.39) by server-12.tower-216.messagelabs.com with RC4-SHA encrypted SMTP; 25 Feb 2013 09:23:07 -0000 X-IronPort-AV: E=Sophos;i="4.84,733,1355097600"; d="scan'208";a="1829879" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 25 Feb 2013 09:23:08 +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.297.1; Mon, 25 Feb 2013 09:23:07 +0000 Message-ID: <1361784186.26546.161.camel@zakaz.uk.xensource.com> From: Ian Campbell To: Yathindra Date: Mon, 25 Feb 2013 09:23:06 +0000 In-Reply-To: <51284379.3070608@cs.utah.edu> References: <5125DCBB.2080305@cs.utah.edu> <51284379.3070608@cs.utah.edu> Organization: Citrix Systems, Inc. X-Mailer: Evolution 3.4.4-1 MIME-Version: 1.0 Cc: "xen-users@lists.xen.org" Subject: Re: [Xen-users] Issuing hypercalls from Linux 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: , Content-Type: 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, 2013-02-23 at 04:20 +0000, Yathindra wrote: > On 2/21/2013 1:37 AM, Yathindra wrote: > > Hi, > > > > I have defined a new hypercall in Xen hypervisor. It is similar to > > do_domctl() > > in that I pass a single argument and use XEN_GUEST_HANDLE() to > > retrieve the > > arguments. Its currently working fine under Xen-4.3-unstable. > > > > Now I want to invoke this hypercall via Linux-3.7.5 Guest. How do I go > > about > > doing this. > > > > Thanks, > > Yathi > Hi, > > I followed a approach similar to do_physdev_op in Linux-3.7.5. > I have a similar set of files under include/xen/interface/ directory. > After plumbing everything when I execute my hypercall via Linux, > I get -14 (EFAULT) as the return value. I added printk's on the Xen > side to see if the hypercall is reaching Xen but it does not. > > Any general direction regarding this would be very helpful. EFAULT usually means that one of the pointers which you passed to the hypercall was not to correctly mapped memory. It might be useful to post your code for both sides of the equation (Linux & Xen). Ian. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Mon Feb 25 09:32:44 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 25 Feb 2013 09:32: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 1U9uPT-0001ha-58; Mon, 25 Feb 2013 09:31:47 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U9uPS-0001hQ-7v for xen-users@lists.xen.org; Mon, 25 Feb 2013 09:31:46 +0000 Received: from [85.158.139.211:28468] by server-7.bemta-5.messagelabs.com id 3A/49-12441-18F2B215; Mon, 25 Feb 2013 09:31:45 +0000 X-Env-Sender: Ian.Campbell@citrix.com X-Msg-Ref: server-12.tower-206.messagelabs.com!1361784656!18440780!2 X-Originating-IP: [46.33.159.39] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNDYuMzMuMTU5LjM5ID0+IDIzOTg5\n X-StarScan-Received: X-StarScan-Version: 6.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 17543 invoked from network); 25 Feb 2013 09:30:58 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (46.33.159.39) by server-12.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 25 Feb 2013 09:30:58 -0000 X-IronPort-AV: E=Sophos;i="4.84,733,1355097600"; d="scan'208";a="1830193" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 25 Feb 2013 09:30: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.297.1; Mon, 25 Feb 2013 09:30:58 +0000 Message-ID: <1361784656.26546.166.camel@zakaz.uk.xensource.com> From: Ian Campbell To: Andrew Son Date: Mon, 25 Feb 2013 09:30:56 +0000 In-Reply-To: References: Organization: Citrix Systems, Inc. X-Mailer: Evolution 3.4.4-1 MIME-Version: 1.0 Cc: "xen-users@lists.xen.org" Subject: Re: [Xen-users] Hypervisor-mode(Intel VT-x) 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, 2013-02-25 at 08:08 +0000, Andrew Son wrote: > Hi All, > > I confused with hypervisor-mode(Intel VT-x) and HVM. > Does only HVM guest use hypervisor-mode? > PV guest does not use Intel VT-x. Correct, at the moment only HVM guests use the hardware virtualisatiopn extensions. However work is underway to enable a new PV mode called PVH which will enable PV guests to also take advantage of hardware when appropriate. http://blog.xen.org/index.php/2012/09/21/xensummit-sessions-new-pvh-virtualisation-mode-for-arm-cortex-a15arm-servers-and-x86/ An initial version of PVH ought to be available in the forthcoming 4.3 release. Ian. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Mon Feb 25 09:32:44 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 25 Feb 2013 09:32: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 1U9uPT-0001ha-58; Mon, 25 Feb 2013 09:31:47 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U9uPS-0001hQ-7v for xen-users@lists.xen.org; Mon, 25 Feb 2013 09:31:46 +0000 Received: from [85.158.139.211:28468] by server-7.bemta-5.messagelabs.com id 3A/49-12441-18F2B215; Mon, 25 Feb 2013 09:31:45 +0000 X-Env-Sender: Ian.Campbell@citrix.com X-Msg-Ref: server-12.tower-206.messagelabs.com!1361784656!18440780!2 X-Originating-IP: [46.33.159.39] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNDYuMzMuMTU5LjM5ID0+IDIzOTg5\n X-StarScan-Received: X-StarScan-Version: 6.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 17543 invoked from network); 25 Feb 2013 09:30:58 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (46.33.159.39) by server-12.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 25 Feb 2013 09:30:58 -0000 X-IronPort-AV: E=Sophos;i="4.84,733,1355097600"; d="scan'208";a="1830193" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 25 Feb 2013 09:30: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.297.1; Mon, 25 Feb 2013 09:30:58 +0000 Message-ID: <1361784656.26546.166.camel@zakaz.uk.xensource.com> From: Ian Campbell To: Andrew Son Date: Mon, 25 Feb 2013 09:30:56 +0000 In-Reply-To: References: Organization: Citrix Systems, Inc. X-Mailer: Evolution 3.4.4-1 MIME-Version: 1.0 Cc: "xen-users@lists.xen.org" Subject: Re: [Xen-users] Hypervisor-mode(Intel VT-x) 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, 2013-02-25 at 08:08 +0000, Andrew Son wrote: > Hi All, > > I confused with hypervisor-mode(Intel VT-x) and HVM. > Does only HVM guest use hypervisor-mode? > PV guest does not use Intel VT-x. Correct, at the moment only HVM guests use the hardware virtualisatiopn extensions. However work is underway to enable a new PV mode called PVH which will enable PV guests to also take advantage of hardware when appropriate. http://blog.xen.org/index.php/2012/09/21/xensummit-sessions-new-pvh-virtualisation-mode-for-arm-cortex-a15arm-servers-and-x86/ An initial version of PVH ought to be available in the forthcoming 4.3 release. Ian. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Mon Feb 25 09:33:25 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 25 Feb 2013 09:33: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 1U9uQL-0001mR-RK; Mon, 25 Feb 2013 09:32:41 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U9uQK-0001m5-96 for xen-users@lists.xen.org; Mon, 25 Feb 2013 09:32:40 +0000 Received: from [85.158.139.211:44708] by server-14.bemta-5.messagelabs.com id B7/1C-13158-7BF2B215; Mon, 25 Feb 2013 09:32:39 +0000 X-Env-Sender: Ian.Campbell@citrix.com X-Msg-Ref: server-12.tower-206.messagelabs.com!1361784656!18440780!1 X-Originating-IP: [46.33.159.39] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNDYuMzMuMTU5LjM5ID0+IDIzOTg5\n X-StarScan-Received: X-StarScan-Version: 6.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 17256 invoked from network); 25 Feb 2013 09:30:56 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (46.33.159.39) by server-12.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 25 Feb 2013 09:30:56 -0000 X-IronPort-AV: E=Sophos;i="4.84,733,1355097600"; d="scan'208";a="1830192" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 25 Feb 2013 09:30: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.297.1; Mon, 25 Feb 2013 09:30:55 +0000 Message-ID: <1361784654.26546.165.camel@zakaz.uk.xensource.com> From: Ian Campbell To: "travis@wsor.net" Date: Mon, 25 Feb 2013 09:30:54 +0000 In-Reply-To: References: Organization: Citrix Systems, Inc. X-Mailer: Evolution 3.4.4-1 MIME-Version: 1.0 Cc: xen-users Subject: Re: [Xen-users] pv guest fails to start after 4.2 upgrade X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: 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, 2013-02-24 at 21:57 +0000, Travis Osterman wrote: > I also tried to take pvgrub out of the picture so I mounted the image > and copied my initrd and kernel to the dom0 file system and updated my > config with the appropriate ramdisk and kernel lines. > > Full output without pvgrub > http://pastebin.com/c7VWWwXk > > Which dropped me in a shell asking for my root partition (progress). Looks like your disk backend isn't getting setup. xl seems to want to use qemu for this. Does /usr/lib/xen/bin/qemu-system-i386 exist? Is there a qemu process running while the guest is booting? Do you get any logs in the /var/log/xen/*dm*.log relating to this domain? > Anyone have any guess why xen-tools 4.2.1 isn't able to read my disk > image files? Everything worked in 4.1. Were you using xl or xm with Xen 4.1? Ian. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Mon Feb 25 09:33:25 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 25 Feb 2013 09:33: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 1U9uQL-0001mR-RK; Mon, 25 Feb 2013 09:32:41 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U9uQK-0001m5-96 for xen-users@lists.xen.org; Mon, 25 Feb 2013 09:32:40 +0000 Received: from [85.158.139.211:44708] by server-14.bemta-5.messagelabs.com id B7/1C-13158-7BF2B215; Mon, 25 Feb 2013 09:32:39 +0000 X-Env-Sender: Ian.Campbell@citrix.com X-Msg-Ref: server-12.tower-206.messagelabs.com!1361784656!18440780!1 X-Originating-IP: [46.33.159.39] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNDYuMzMuMTU5LjM5ID0+IDIzOTg5\n X-StarScan-Received: X-StarScan-Version: 6.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 17256 invoked from network); 25 Feb 2013 09:30:56 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (46.33.159.39) by server-12.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 25 Feb 2013 09:30:56 -0000 X-IronPort-AV: E=Sophos;i="4.84,733,1355097600"; d="scan'208";a="1830192" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 25 Feb 2013 09:30: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.297.1; Mon, 25 Feb 2013 09:30:55 +0000 Message-ID: <1361784654.26546.165.camel@zakaz.uk.xensource.com> From: Ian Campbell To: "travis@wsor.net" Date: Mon, 25 Feb 2013 09:30:54 +0000 In-Reply-To: References: Organization: Citrix Systems, Inc. X-Mailer: Evolution 3.4.4-1 MIME-Version: 1.0 Cc: xen-users Subject: Re: [Xen-users] pv guest fails to start after 4.2 upgrade X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: 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, 2013-02-24 at 21:57 +0000, Travis Osterman wrote: > I also tried to take pvgrub out of the picture so I mounted the image > and copied my initrd and kernel to the dom0 file system and updated my > config with the appropriate ramdisk and kernel lines. > > Full output without pvgrub > http://pastebin.com/c7VWWwXk > > Which dropped me in a shell asking for my root partition (progress). Looks like your disk backend isn't getting setup. xl seems to want to use qemu for this. Does /usr/lib/xen/bin/qemu-system-i386 exist? Is there a qemu process running while the guest is booting? Do you get any logs in the /var/log/xen/*dm*.log relating to this domain? > Anyone have any guess why xen-tools 4.2.1 isn't able to read my disk > image files? Everything worked in 4.1. Were you using xl or xm with Xen 4.1? Ian. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Mon Feb 25 09:57:58 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 25 Feb 2013 09:57: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 1U9uo7-0003Ga-Go; Mon, 25 Feb 2013 09:57:15 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U9uo5-0003G2-Mo; Mon, 25 Feb 2013 09:57:13 +0000 Received: from [85.158.139.211:49977] by server-15.bemta-5.messagelabs.com id CF/72-22815-8753B215; Mon, 25 Feb 2013 09:57:12 +0000 X-Env-Sender: wei.liu2@citrix.com X-Msg-Ref: server-10.tower-206.messagelabs.com!1361786230!18217806!1 X-Originating-IP: [66.165.176.89] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjYuMTY1LjE3Ni44OSA9PiAyMDEwNDY=\n X-StarScan-Received: X-StarScan-Version: 6.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 3747 invoked from network); 25 Feb 2013 09:57:11 -0000 Received: from smtp.citrix.com (HELO SMTP.CITRIX.COM) (66.165.176.89) by server-10.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 25 Feb 2013 09:57:11 -0000 X-IronPort-AV: E=Sophos;i="4.84,733,1355097600"; d="scan'208";a="9335508" Received: from accessns.citrite.net (HELO FTLPEX01CL01.citrite.net) ([10.9.154.239]) by FTLPIPO01.CITRIX.COM with ESMTP/TLS/AES128-SHA; 25 Feb 2013 09:57:09 +0000 Received: from ukmail1.uk.xensource.com (10.80.16.128) by smtprelay.citrix.com (10.13.107.78) with Microsoft SMTP Server id 14.2.318.1; Mon, 25 Feb 2013 04:57:09 -0500 Received: from zion.uk.xensource.com ([10.80.2.73]) by ukmail1.uk.xensource.com with esmtp (Exim 4.69) (envelope-from ) id 1U9uo1-0002u6-1j; Mon, 25 Feb 2013 09:57:09 +0000 Message-ID: <1361786229.2109.15.camel@zion.uk.xensource.com> From: Wei Liu To: , , xen-arm , "xen-users@lists.xen.org" Date: Mon, 25 Feb 2013 09:57:09 +0000 X-Mailer: Evolution 3.6.3 (3.6.3-2.fc18) MIME-Version: 1.0 Cc: Lars Kurth , wei.liu2@citrix.com Subject: [Xen-users] Xen Documentation Day: Feb 25th X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: 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 Just a quick reminder that today is Xen documentation day! Join us on freenode #xendocs to improve Xen documentation! ********************* * 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! Wei. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Mon Feb 25 09:57:58 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 25 Feb 2013 09:57: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 1U9uo7-0003Ga-Go; Mon, 25 Feb 2013 09:57:15 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U9uo5-0003G2-Mo; Mon, 25 Feb 2013 09:57:13 +0000 Received: from [85.158.139.211:49977] by server-15.bemta-5.messagelabs.com id CF/72-22815-8753B215; Mon, 25 Feb 2013 09:57:12 +0000 X-Env-Sender: wei.liu2@citrix.com X-Msg-Ref: server-10.tower-206.messagelabs.com!1361786230!18217806!1 X-Originating-IP: [66.165.176.89] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjYuMTY1LjE3Ni44OSA9PiAyMDEwNDY=\n X-StarScan-Received: X-StarScan-Version: 6.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 3747 invoked from network); 25 Feb 2013 09:57:11 -0000 Received: from smtp.citrix.com (HELO SMTP.CITRIX.COM) (66.165.176.89) by server-10.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 25 Feb 2013 09:57:11 -0000 X-IronPort-AV: E=Sophos;i="4.84,733,1355097600"; d="scan'208";a="9335508" Received: from accessns.citrite.net (HELO FTLPEX01CL01.citrite.net) ([10.9.154.239]) by FTLPIPO01.CITRIX.COM with ESMTP/TLS/AES128-SHA; 25 Feb 2013 09:57:09 +0000 Received: from ukmail1.uk.xensource.com (10.80.16.128) by smtprelay.citrix.com (10.13.107.78) with Microsoft SMTP Server id 14.2.318.1; Mon, 25 Feb 2013 04:57:09 -0500 Received: from zion.uk.xensource.com ([10.80.2.73]) by ukmail1.uk.xensource.com with esmtp (Exim 4.69) (envelope-from ) id 1U9uo1-0002u6-1j; Mon, 25 Feb 2013 09:57:09 +0000 Message-ID: <1361786229.2109.15.camel@zion.uk.xensource.com> From: Wei Liu To: , , xen-arm , "xen-users@lists.xen.org" Date: Mon, 25 Feb 2013 09:57:09 +0000 X-Mailer: Evolution 3.6.3 (3.6.3-2.fc18) MIME-Version: 1.0 Cc: Lars Kurth , wei.liu2@citrix.com Subject: [Xen-users] Xen Documentation Day: Feb 25th X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: 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 Just a quick reminder that today is Xen documentation day! Join us on freenode #xendocs to improve Xen documentation! ********************* * 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! Wei. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Mon Feb 25 13:51:19 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 25 Feb 2013 13:51: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 1U9yRR-0003mo-7g; Mon, 25 Feb 2013 13:50:05 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U9yRP-0003mi-Ll for xen-users@lists.xen.org; Mon, 25 Feb 2013 13:50:03 +0000 Received: from [85.158.137.99:19089] by server-10.bemta-3.messagelabs.com id 00/52-10609-A0C6B215; Mon, 25 Feb 2013 13:50:02 +0000 X-Env-Sender: simon.gabor1@hotmail.hu X-Msg-Ref: server-12.tower-217.messagelabs.com!1361800201!14679257!1 X-Originating-IP: [65.55.111.102] X-SpamReason: No, hits=0.4 required=7.0 tests=FORGED_HOTMAIL_RCVD, HTML_60_70,HTML_MESSAGE,ML_RADAR_SPEW_LINKS_1,ML_RADAR_SPEW_LINKS_12, ML_RADAR_SPEW_LINKS_14,MSGID_FROM_MTA_HEADER,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 19223 invoked from network); 25 Feb 2013 13:50:01 -0000 Received: from blu0-omc2-s27.blu0.hotmail.com (HELO blu0-omc2-s27.blu0.hotmail.com) (65.55.111.102) by server-12.tower-217.messagelabs.com with SMTP; 25 Feb 2013 13:50:01 -0000 Received: from BLU0-SMTP163 ([65.55.111.72]) by blu0-omc2-s27.blu0.hotmail.com with Microsoft SMTPSVC(6.0.3790.4675); Mon, 25 Feb 2013 05:50:01 -0800 X-EIP: [qJc364p5ErmpepcJVXNRwlWpR+fJlB21] X-Originating-Email: [simon.gabor1@hotmail.hu] Message-ID: Received: from pikovax ([86.101.124.149]) by BLU0-SMTP163.phx.gbl over TLS secured channel with Microsoft SMTPSVC(6.0.3790.4675); Mon, 25 Feb 2013 05:50:00 -0800 From: Simon Gabor To: Date: Mon, 25 Feb 2013 14:49:57 +0100 MIME-Version: 1.0 X-Priority: 3 X-MSMail-Priority: Normal Importance: Normal X-Mailer: Microsoft Windows Live Mail 16.4.3505.912 X-MimeOLE: Produced By Microsoft MimeOLE V16.4.3505.912 X-OriginalArrivalTime: 25 Feb 2013 13:50:01.0214 (UTC) FILETIME=[01BA71E0:01CE135F] Subject: [Xen-users] Solaris 11.1 PV boot problem - do_bys_alloc_contig X-BeenThere: xen-users@lists.xen.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="===============5473651015066559245==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============5473651015066559245== Content-Type: multipart/alternative; boundary="----=_NextPart_000_0012_01CE1367.615199A0" ------=_NextPart_000_0012_01CE1367.615199A0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hi, I am unable to boot paravirtualised Solaris 11.1 x86_64 domU-s. The = brief error message is: # xl create /xen/configs/stan_pv -c Parsing config from /xen/configs/stan_pv Daemon running with PID 6135 do_bys_alloc_contig: 'align' 0x40816f40 is less than MMU_PAGESIZE = 0x40816f80 Press any key to reboot. Resetting... My config works fine with any tried versions of Solaris 11, but all = Solaris11.1 failing, including the install ISO image, or all my virtual machines I upgraded from Solaris 11 to 11.1. # xl =E2=80=93vvv create /xen/configs/stan_pv =E2=80=93c = http://pastebin.com/CF4Stqn8 # xl dmesg = http://pastebin.com/Ym2vKS5L # xl info = http://pastebin.com/eVT4reG2 # cat /xen/configs/stan_pv = http://pastebin.com/cN1qh0Le Xen version is 4.2.1, I have compiled it from source. I tried xen Gentoo = ebuild 4.2.0, the result is the same. When I switch back to HVM the problem does not rise, all works fine. But = I would like to use PV as before (Sol11). Could you recommend something to solve this problem? Thanks in advance, Gabor ------=_NextPart_000_0012_01CE1367.615199A0 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi,
 
I am unable to boot paravirtualised Solaris 11.1 x86_64 domU-s. The = brief=20 error message is:
# xl create /xen/configs/stan_pv -c
Parsing config from /xen/configs/stan_pv
Daemon running with PID 6135
do_bys_alloc_contig: 'align' 0x40816f40 is less than MMU_PAGESIZE=20 0x40816f80
Press any key to reboot.
Resetting...
 
My config works fine with any tried versions of Solaris 11, but all = Solaris11.1 failing, including the install ISO image, or
all my virtual machines I upgraded from Solaris 11 to 11.1.
 
# xl =E2=80=93vvv create /xen/configs/stan_pv=20 =E2=80=93c        http://pastebin.com/CF4Stqn8
# xl=20 dmesg           &n= bsp;           &nb= sp;           &nbs= p;            = ;       =20 http://pastebin.com/Ym2vKS5L
# xl=20 info           &nb= sp;           &nbs= p;            = ;            =            =20 http://pastebin.com/eVT4reG2
# cat=20 /xen/configs/stan_pv         = ;            =        =20 http://pastebin.com/cN1qh0Le
 
Xen version is 4.2.1, I have compiled it from source. I tried xen = Gentoo=20 ebuild 4.2.0, the result is the same.
When I switch back to HVM the problem does not rise, all works = fine. But I=20 would like to use PV as before (Sol11).
 
Could you recommend something to solve this problem?
 
Thanks in advance,
 
Gabor
 
------=_NextPart_000_0012_01CE1367.615199A0-- --===============5473651015066559245== 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 --===============5473651015066559245==-- From xen-users-bounces@lists.xen.org Mon Feb 25 13:51:19 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 25 Feb 2013 13:51: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 1U9yRR-0003mo-7g; Mon, 25 Feb 2013 13:50:05 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U9yRP-0003mi-Ll for xen-users@lists.xen.org; Mon, 25 Feb 2013 13:50:03 +0000 Received: from [85.158.137.99:19089] by server-10.bemta-3.messagelabs.com id 00/52-10609-A0C6B215; Mon, 25 Feb 2013 13:50:02 +0000 X-Env-Sender: simon.gabor1@hotmail.hu X-Msg-Ref: server-12.tower-217.messagelabs.com!1361800201!14679257!1 X-Originating-IP: [65.55.111.102] X-SpamReason: No, hits=0.4 required=7.0 tests=FORGED_HOTMAIL_RCVD, HTML_60_70,HTML_MESSAGE,ML_RADAR_SPEW_LINKS_1,ML_RADAR_SPEW_LINKS_12, ML_RADAR_SPEW_LINKS_14,MSGID_FROM_MTA_HEADER,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 19223 invoked from network); 25 Feb 2013 13:50:01 -0000 Received: from blu0-omc2-s27.blu0.hotmail.com (HELO blu0-omc2-s27.blu0.hotmail.com) (65.55.111.102) by server-12.tower-217.messagelabs.com with SMTP; 25 Feb 2013 13:50:01 -0000 Received: from BLU0-SMTP163 ([65.55.111.72]) by blu0-omc2-s27.blu0.hotmail.com with Microsoft SMTPSVC(6.0.3790.4675); Mon, 25 Feb 2013 05:50:01 -0800 X-EIP: [qJc364p5ErmpepcJVXNRwlWpR+fJlB21] X-Originating-Email: [simon.gabor1@hotmail.hu] Message-ID: Received: from pikovax ([86.101.124.149]) by BLU0-SMTP163.phx.gbl over TLS secured channel with Microsoft SMTPSVC(6.0.3790.4675); Mon, 25 Feb 2013 05:50:00 -0800 From: Simon Gabor To: Date: Mon, 25 Feb 2013 14:49:57 +0100 MIME-Version: 1.0 X-Priority: 3 X-MSMail-Priority: Normal Importance: Normal X-Mailer: Microsoft Windows Live Mail 16.4.3505.912 X-MimeOLE: Produced By Microsoft MimeOLE V16.4.3505.912 X-OriginalArrivalTime: 25 Feb 2013 13:50:01.0214 (UTC) FILETIME=[01BA71E0:01CE135F] Subject: [Xen-users] Solaris 11.1 PV boot problem - do_bys_alloc_contig X-BeenThere: xen-users@lists.xen.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="===============5473651015066559245==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============5473651015066559245== Content-Type: multipart/alternative; boundary="----=_NextPart_000_0012_01CE1367.615199A0" ------=_NextPart_000_0012_01CE1367.615199A0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hi, I am unable to boot paravirtualised Solaris 11.1 x86_64 domU-s. The = brief error message is: # xl create /xen/configs/stan_pv -c Parsing config from /xen/configs/stan_pv Daemon running with PID 6135 do_bys_alloc_contig: 'align' 0x40816f40 is less than MMU_PAGESIZE = 0x40816f80 Press any key to reboot. Resetting... My config works fine with any tried versions of Solaris 11, but all = Solaris11.1 failing, including the install ISO image, or all my virtual machines I upgraded from Solaris 11 to 11.1. # xl =E2=80=93vvv create /xen/configs/stan_pv =E2=80=93c = http://pastebin.com/CF4Stqn8 # xl dmesg = http://pastebin.com/Ym2vKS5L # xl info = http://pastebin.com/eVT4reG2 # cat /xen/configs/stan_pv = http://pastebin.com/cN1qh0Le Xen version is 4.2.1, I have compiled it from source. I tried xen Gentoo = ebuild 4.2.0, the result is the same. When I switch back to HVM the problem does not rise, all works fine. But = I would like to use PV as before (Sol11). Could you recommend something to solve this problem? Thanks in advance, Gabor ------=_NextPart_000_0012_01CE1367.615199A0 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi,
 
I am unable to boot paravirtualised Solaris 11.1 x86_64 domU-s. The = brief=20 error message is:
# xl create /xen/configs/stan_pv -c
Parsing config from /xen/configs/stan_pv
Daemon running with PID 6135
do_bys_alloc_contig: 'align' 0x40816f40 is less than MMU_PAGESIZE=20 0x40816f80
Press any key to reboot.
Resetting...
 
My config works fine with any tried versions of Solaris 11, but all = Solaris11.1 failing, including the install ISO image, or
all my virtual machines I upgraded from Solaris 11 to 11.1.
 
# xl =E2=80=93vvv create /xen/configs/stan_pv=20 =E2=80=93c        http://pastebin.com/CF4Stqn8
# xl=20 dmesg           &n= bsp;           &nb= sp;           &nbs= p;            = ;       =20 http://pastebin.com/Ym2vKS5L
# xl=20 info           &nb= sp;           &nbs= p;            = ;            =            =20 http://pastebin.com/eVT4reG2
# cat=20 /xen/configs/stan_pv         = ;            =        =20 http://pastebin.com/cN1qh0Le
 
Xen version is 4.2.1, I have compiled it from source. I tried xen = Gentoo=20 ebuild 4.2.0, the result is the same.
When I switch back to HVM the problem does not rise, all works = fine. But I=20 would like to use PV as before (Sol11).
 
Could you recommend something to solve this problem?
 
Thanks in advance,
 
Gabor
 
------=_NextPart_000_0012_01CE1367.615199A0-- --===============5473651015066559245== 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 --===============5473651015066559245==-- From xen-users-bounces@lists.xen.org Mon Feb 25 14:44:43 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 25 Feb 2013 14: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 1U9zH6-0005gE-HM; Mon, 25 Feb 2013 14:43:28 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U9zH4-0005g7-Pc for xen-users@lists.xen.org; Mon, 25 Feb 2013 14:43:27 +0000 Received: from [85.158.139.83:41948] by server-9.bemta-5.messagelabs.com id A3/AA-08547-D887B215; Mon, 25 Feb 2013 14:43:25 +0000 X-Env-Sender: tosterman@gmail.com X-Msg-Ref: server-15.tower-182.messagelabs.com!1361803378!28717060!1 X-Originating-IP: [209.85.223.174] 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.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 20861 invoked from network); 25 Feb 2013 14:42:59 -0000 Received: from mail-ie0-f174.google.com (HELO mail-ie0-f174.google.com) (209.85.223.174) by server-15.tower-182.messagelabs.com with RC4-SHA encrypted SMTP; 25 Feb 2013 14:42:59 -0000 Received: by mail-ie0-f174.google.com with SMTP id k10so3098552iea.5 for ; Mon, 25 Feb 2013 06:42:57 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:reply-to:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=N38/GLMRXqpXuWUEFfgX4DID0DjzU7C2FPlRDK9MSfk=; b=KFo7aD9HzLkQzpOEJDUI+zYL0wjzE0KOoEhdJCulm/0zLeLYQWqfjDSzORMdUMpR04 cdAG8cJrZOE+jf8lbEijcxAIT6XzeraHwmR97+WMQmIWasJ4VsOHpYpxA5hD9Ikj7B65 Bve0zJi/Hz7cTQcvyDuu0ZyEDgbeOVS55nqXb9cipbs7kA2mwDH6Or8O47BumEia3tZ4 yBWKPc2a/FuFG6W/rtBMFiqalG9ON8GPyan3pUFchGHpNMl1hm+Yp4DscQuVXqXPMkNC 8fk1Wpu61edzdRPxvR4BhSuY2peX73b8FbLfbbbpbTihLnuPigzfLJNgKzGVNpEX677H 9QXA== MIME-Version: 1.0 X-Received: by 10.50.217.230 with SMTP id pb6mr3567211igc.43.1361803377900; Mon, 25 Feb 2013 06:42:57 -0800 (PST) Received: by 10.64.60.136 with HTTP; Mon, 25 Feb 2013 06:42:57 -0800 (PST) In-Reply-To: <1361784654.26546.165.camel@zakaz.uk.xensource.com> References: <1361784654.26546.165.camel@zakaz.uk.xensource.com> Date: Mon, 25 Feb 2013 09:42:57 -0500 Message-ID: From: Travis Osterman To: xen-users Cc: Ian Campbell Subject: Re: [Xen-users] pv guest fails to start after 4.2 upgrade X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: travis@wsor.net List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: 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, Feb 25, 2013 at 4:30 AM, Ian Campbell wrote: > On Sun, 2013-02-24 at 21:57 +0000, Travis Osterman wrote: >> I also tried to take pvgrub out of the picture so I mounted the image >> and copied my initrd and kernel to the dom0 file system and updated my >> config with the appropriate ramdisk and kernel lines. >> >> Full output without pvgrub >> http://pastebin.com/c7VWWwXk >> >> Which dropped me in a shell asking for my root partition (progress). Ian, thanks for the help, here are the answers. > Does /usr/lib/xen/bin/qemu-system-i386 exist? yes # ls /usr/lib/xen/bin/qemu-system-i386 /usr/lib/xen/bin/qemu-system-i386 > Is there a qemu process running while the guest is booting? No. If I mount the image to a loopback device and boot the domain, I also do not have a qemu process (althought I'm not sure if I'm supposed to at that point. > Do you get any logs in the /var/log/xen/*dm*.log relating to this domain? # cat /var/log/xen/qemu-dm-prime.log bind(unix:/var/run/xen/qmp-libxl-4): No such file or directory chardev: opening backend "socket" failed: No such file or directory # ls /var/run/xen* /var/run/xenconsoled.pid /var/run/xenstored.pid /var/run/xenstored: socket socket_ro > Were you using xl or xm with Xen 4.1? xl So it looks like the lack of /var/run/xen/qmp-libxl-4 is contributing ... any idea where to head next? Thanks again. -- T _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Mon Feb 25 14:44:43 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 25 Feb 2013 14: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 1U9zH6-0005gE-HM; Mon, 25 Feb 2013 14:43:28 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U9zH4-0005g7-Pc for xen-users@lists.xen.org; Mon, 25 Feb 2013 14:43:27 +0000 Received: from [85.158.139.83:41948] by server-9.bemta-5.messagelabs.com id A3/AA-08547-D887B215; Mon, 25 Feb 2013 14:43:25 +0000 X-Env-Sender: tosterman@gmail.com X-Msg-Ref: server-15.tower-182.messagelabs.com!1361803378!28717060!1 X-Originating-IP: [209.85.223.174] 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.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 20861 invoked from network); 25 Feb 2013 14:42:59 -0000 Received: from mail-ie0-f174.google.com (HELO mail-ie0-f174.google.com) (209.85.223.174) by server-15.tower-182.messagelabs.com with RC4-SHA encrypted SMTP; 25 Feb 2013 14:42:59 -0000 Received: by mail-ie0-f174.google.com with SMTP id k10so3098552iea.5 for ; Mon, 25 Feb 2013 06:42:57 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:reply-to:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=N38/GLMRXqpXuWUEFfgX4DID0DjzU7C2FPlRDK9MSfk=; b=KFo7aD9HzLkQzpOEJDUI+zYL0wjzE0KOoEhdJCulm/0zLeLYQWqfjDSzORMdUMpR04 cdAG8cJrZOE+jf8lbEijcxAIT6XzeraHwmR97+WMQmIWasJ4VsOHpYpxA5hD9Ikj7B65 Bve0zJi/Hz7cTQcvyDuu0ZyEDgbeOVS55nqXb9cipbs7kA2mwDH6Or8O47BumEia3tZ4 yBWKPc2a/FuFG6W/rtBMFiqalG9ON8GPyan3pUFchGHpNMl1hm+Yp4DscQuVXqXPMkNC 8fk1Wpu61edzdRPxvR4BhSuY2peX73b8FbLfbbbpbTihLnuPigzfLJNgKzGVNpEX677H 9QXA== MIME-Version: 1.0 X-Received: by 10.50.217.230 with SMTP id pb6mr3567211igc.43.1361803377900; Mon, 25 Feb 2013 06:42:57 -0800 (PST) Received: by 10.64.60.136 with HTTP; Mon, 25 Feb 2013 06:42:57 -0800 (PST) In-Reply-To: <1361784654.26546.165.camel@zakaz.uk.xensource.com> References: <1361784654.26546.165.camel@zakaz.uk.xensource.com> Date: Mon, 25 Feb 2013 09:42:57 -0500 Message-ID: From: Travis Osterman To: xen-users Cc: Ian Campbell Subject: Re: [Xen-users] pv guest fails to start after 4.2 upgrade X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: travis@wsor.net List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: 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, Feb 25, 2013 at 4:30 AM, Ian Campbell wrote: > On Sun, 2013-02-24 at 21:57 +0000, Travis Osterman wrote: >> I also tried to take pvgrub out of the picture so I mounted the image >> and copied my initrd and kernel to the dom0 file system and updated my >> config with the appropriate ramdisk and kernel lines. >> >> Full output without pvgrub >> http://pastebin.com/c7VWWwXk >> >> Which dropped me in a shell asking for my root partition (progress). Ian, thanks for the help, here are the answers. > Does /usr/lib/xen/bin/qemu-system-i386 exist? yes # ls /usr/lib/xen/bin/qemu-system-i386 /usr/lib/xen/bin/qemu-system-i386 > Is there a qemu process running while the guest is booting? No. If I mount the image to a loopback device and boot the domain, I also do not have a qemu process (althought I'm not sure if I'm supposed to at that point. > Do you get any logs in the /var/log/xen/*dm*.log relating to this domain? # cat /var/log/xen/qemu-dm-prime.log bind(unix:/var/run/xen/qmp-libxl-4): No such file or directory chardev: opening backend "socket" failed: No such file or directory # ls /var/run/xen* /var/run/xenconsoled.pid /var/run/xenstored.pid /var/run/xenstored: socket socket_ro > Were you using xl or xm with Xen 4.1? xl So it looks like the lack of /var/run/xen/qmp-libxl-4 is contributing ... any idea where to head next? Thanks again. -- T _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Mon Feb 25 15:22:45 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 25 Feb 2013 15:22: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 1U9zsD-0006yD-HK; Mon, 25 Feb 2013 15:21:49 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U9zsB-0006y8-Sn for xen-users@lists.xen.org; Mon, 25 Feb 2013 15:21:48 +0000 Received: from [85.158.139.83:25470] by server-11.bemta-5.messagelabs.com id 85/03-27486-B818B215; Mon, 25 Feb 2013 15:21:47 +0000 X-Env-Sender: Ian.Campbell@citrix.com X-Msg-Ref: server-14.tower-182.messagelabs.com!1361805706!24496135!1 X-Originating-IP: [46.33.159.39] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNDYuMzMuMTU5LjM5ID0+IDIzOTg5\n X-StarScan-Received: X-StarScan-Version: 6.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 3707 invoked from network); 25 Feb 2013 15:21:46 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (46.33.159.39) by server-14.tower-182.messagelabs.com with RC4-SHA encrypted SMTP; 25 Feb 2013 15:21:46 -0000 X-IronPort-AV: E=Sophos;i="4.84,735,1355097600"; d="scan'208";a="1847333" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 25 Feb 2013 15:20:46 +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.297.1; Mon, 25 Feb 2013 15:20:45 +0000 Message-ID: <1361805642.26546.184.camel@zakaz.uk.xensource.com> From: Ian Campbell To: "travis@wsor.net" Date: Mon, 25 Feb 2013 15:20:42 +0000 In-Reply-To: References: <1361784654.26546.165.camel@zakaz.uk.xensource.com> Organization: Citrix Systems, Inc. X-Mailer: Evolution 3.4.4-1 MIME-Version: 1.0 Cc: xen-users Subject: Re: [Xen-users] pv guest fails to start after 4.2 upgrade X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: 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, 2013-02-25 at 14:42 +0000, Travis Osterman wrote: > On Mon, Feb 25, 2013 at 4:30 AM, Ian Campbell wrote: > > On Sun, 2013-02-24 at 21:57 +0000, Travis Osterman wrote: > >> I also tried to take pvgrub out of the picture so I mounted the image > >> and copied my initrd and kernel to the dom0 file system and updated my > >> config with the appropriate ramdisk and kernel lines. > >> > >> Full output without pvgrub > >> http://pastebin.com/c7VWWwXk > >> > >> Which dropped me in a shell asking for my root partition (progress). > > Ian, thanks for the help, here are the answers. > > > Does /usr/lib/xen/bin/qemu-system-i386 exist? > > yes > # ls /usr/lib/xen/bin/qemu-system-i386 > /usr/lib/xen/bin/qemu-system-i386 > > > Is there a qemu process running while the guest is booting? > > No. If I mount the image to a loopback device and boot the domain, I > also do not have a qemu process (althought I'm not sure if I'm > supposed to at that point. I don't think so, in the loopback case you will be using the in-kernel blkback driver. Only with file:// would you expect the qemu-base qdisk (or blktap, which your logs indicate you don't have) > > Do you get any logs in the /var/log/xen/*dm*.log relating to this domain? > > # cat /var/log/xen/qemu-dm-prime.log > bind(unix:/var/run/xen/qmp-libxl-4): No such file or directory > chardev: opening backend "socket" failed: No such file or directory > > # ls /var/run/xen* > /var/run/xenconsoled.pid /var/run/xenstored.pid > > /var/run/xenstored: > socket socket_ro > > > Were you using xl or xm with Xen 4.1? > > xl > > So it looks like the lack of /var/run/xen/qmp-libxl-4 is contributing > ... any idea where to head next? Thanks again. I expect either libxl should have created this or qemu should, since qemu is complaining I assume libxl should have done it... Ah, you are missing the /var/run/xen/ directory so it is failing to create the socket, if you create the directory does it work? Although even if so it is obviously still a bug that libxl doesn't handle that error... Ian. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Mon Feb 25 15:22:45 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 25 Feb 2013 15:22: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 1U9zsD-0006yD-HK; Mon, 25 Feb 2013 15:21:49 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U9zsB-0006y8-Sn for xen-users@lists.xen.org; Mon, 25 Feb 2013 15:21:48 +0000 Received: from [85.158.139.83:25470] by server-11.bemta-5.messagelabs.com id 85/03-27486-B818B215; Mon, 25 Feb 2013 15:21:47 +0000 X-Env-Sender: Ian.Campbell@citrix.com X-Msg-Ref: server-14.tower-182.messagelabs.com!1361805706!24496135!1 X-Originating-IP: [46.33.159.39] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNDYuMzMuMTU5LjM5ID0+IDIzOTg5\n X-StarScan-Received: X-StarScan-Version: 6.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 3707 invoked from network); 25 Feb 2013 15:21:46 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (46.33.159.39) by server-14.tower-182.messagelabs.com with RC4-SHA encrypted SMTP; 25 Feb 2013 15:21:46 -0000 X-IronPort-AV: E=Sophos;i="4.84,735,1355097600"; d="scan'208";a="1847333" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 25 Feb 2013 15:20:46 +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.297.1; Mon, 25 Feb 2013 15:20:45 +0000 Message-ID: <1361805642.26546.184.camel@zakaz.uk.xensource.com> From: Ian Campbell To: "travis@wsor.net" Date: Mon, 25 Feb 2013 15:20:42 +0000 In-Reply-To: References: <1361784654.26546.165.camel@zakaz.uk.xensource.com> Organization: Citrix Systems, Inc. X-Mailer: Evolution 3.4.4-1 MIME-Version: 1.0 Cc: xen-users Subject: Re: [Xen-users] pv guest fails to start after 4.2 upgrade X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: 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, 2013-02-25 at 14:42 +0000, Travis Osterman wrote: > On Mon, Feb 25, 2013 at 4:30 AM, Ian Campbell wrote: > > On Sun, 2013-02-24 at 21:57 +0000, Travis Osterman wrote: > >> I also tried to take pvgrub out of the picture so I mounted the image > >> and copied my initrd and kernel to the dom0 file system and updated my > >> config with the appropriate ramdisk and kernel lines. > >> > >> Full output without pvgrub > >> http://pastebin.com/c7VWWwXk > >> > >> Which dropped me in a shell asking for my root partition (progress). > > Ian, thanks for the help, here are the answers. > > > Does /usr/lib/xen/bin/qemu-system-i386 exist? > > yes > # ls /usr/lib/xen/bin/qemu-system-i386 > /usr/lib/xen/bin/qemu-system-i386 > > > Is there a qemu process running while the guest is booting? > > No. If I mount the image to a loopback device and boot the domain, I > also do not have a qemu process (althought I'm not sure if I'm > supposed to at that point. I don't think so, in the loopback case you will be using the in-kernel blkback driver. Only with file:// would you expect the qemu-base qdisk (or blktap, which your logs indicate you don't have) > > Do you get any logs in the /var/log/xen/*dm*.log relating to this domain? > > # cat /var/log/xen/qemu-dm-prime.log > bind(unix:/var/run/xen/qmp-libxl-4): No such file or directory > chardev: opening backend "socket" failed: No such file or directory > > # ls /var/run/xen* > /var/run/xenconsoled.pid /var/run/xenstored.pid > > /var/run/xenstored: > socket socket_ro > > > Were you using xl or xm with Xen 4.1? > > xl > > So it looks like the lack of /var/run/xen/qmp-libxl-4 is contributing > ... any idea where to head next? Thanks again. I expect either libxl should have created this or qemu should, since qemu is complaining I assume libxl should have done it... Ah, you are missing the /var/run/xen/ directory so it is failing to create the socket, if you create the directory does it work? Although even if so it is obviously still a bug that libxl doesn't handle that error... Ian. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Mon Feb 25 15:25:18 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 25 Feb 2013 15:25: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 1U9zua-000759-BB; Mon, 25 Feb 2013 15:24:16 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U9zuY-00074y-ND for xen-users@lists.xen.org; Mon, 25 Feb 2013 15:24:14 +0000 Received: from [85.158.138.51:8664] by server-11.bemta-3.messagelabs.com id D1/D7-10249-D128B215; Mon, 25 Feb 2013 15:24:13 +0000 X-Env-Sender: jep@obrien-pifer.com X-Msg-Ref: server-3.tower-174.messagelabs.com!1361805852!21011784!1 X-Originating-IP: [75.180.132.120] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: QmFkIElQOiA3NS4xODAuMTMyLjEyMCA9PiA5OTIwNw==\n,sa_preprocessor: QmFkIElQOiA3NS4xODAuMTMyLjEyMCA9PiA5OTIwNw==\n X-StarScan-Received: X-StarScan-Version: 6.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 8559 invoked from network); 25 Feb 2013 15:24:12 -0000 Received: from cdptpa-omtalb.mail.rr.com (HELO cdptpa-omtalb.mail.rr.com) (75.180.132.120) by server-3.tower-174.messagelabs.com with SMTP; 25 Feb 2013 15:24:12 -0000 X-Authority-Analysis: v=2.0 cv=XL2yuHdE c=1 sm=0 a=khvKJusKvADddYwUSfUZmw==:17 a=s-1hg7RLGykA:10 a=zopZFYjvPDYA:10 a=u769Oq3-vAwA:10 a=i7z8CvP5fyYA:10 a=8nJEP1OIZ-IA:10 a=oZXU78TAAAAA:8 a=iTPvVhlw94UA:10 a=ahZqYPGVh96QI-fWcSUA:9 a=wPNLvfGTeEIA:10 a=khvKJusKvADddYwUSfUZmw==:117 X-Cloudmark-Score: 0 X-Authenticated-User: X-Originating-IP: 96.10.171.230 Received: from [96.10.171.230] ([96.10.171.230:57990] helo=mailserver.obrien-pifer.com) by cdptpa-oedge04.mail.rr.com (envelope-from ) (ecelerity 2.2.3.46 r()) with ESMTP id 70/72-25887-9128B215; Mon, 25 Feb 2013 15:24:11 +0000 Received: from [10.99.1.24] ([10.99.1.24]) (authenticated bits=0) by mailserver.obrien-pifer.com (8.13.8/8.13.8) with ESMTP id r1PFOFWv017041 for ; Mon, 25 Feb 2013 10:24:15 -0500 Message-ID: <512B8216.70105@obrien-pifer.com> Date: Mon, 25 Feb 2013 10:24:06 -0500 From: James Pifer User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130215 Thunderbird/17.0.3 MIME-Version: 1.0 To: xen-users@lists.xen.org Subject: [Xen-users] Convert Debian 6 from HVM to PV X-BeenThere: xen-users@lists.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 have a couple Debian 6 HVM VMs. From what I've read, Debian 6's standard kernels have pv_ops already enabled. I'd like to convert these to pv for the following reasons (Assuming both of are valid expectations): 1) so the VMs use pv for the NICs 2) so the VMs properly respond to shutdown/reboot commands from xm I'm having trouble converting them. I believe need to convert the menu from something like this: root (hd0,0) kernel /xen.gz-2.6.18-53.1.14.el5 module /vmlinuz-2.6.18-53.1.14.el5xen ro root=LABEL=/ module /myinitrd.img to something like this: root (hd0,0) kernel /vmlinuz-2.6.18-53.1.14.el5xen ro root=LABEL=/ initrd /myinitrd.img The Debian 6 VMs I have appear to use grub2, which is a pain in the rear as far as I can tell. I expect there are good reasons for it, but being able to modify a menu.lst makes this transition much easier. The top of the file says to use /etc/grub.d and settings from /etc/default/grub to update grub.cfg, but I can't figure out how they build the menu section. Here's the menu section of grub.cfg. Can anyone give me some help on changing this to the proper form for booting pv? ### BEGIN /etc/grub.d/10_linux ### menuentry 'Debian GNU/Linux, with Linux 2.6.32-5-686' --class debian --class gnu-linux --class gnu --class os { insmod part_msdos insmod ext2 set root='(hd0,msdos1)' search --no-floppy --fs-uuid --set 8d0d1b45-e312-49ee-9213-50651e18f259 echo 'Loading Linux 2.6.32-5-686 ...' linux /boot/vmlinuz-2.6.32-5-686 root=UUID=8d0d1b45-e312-49ee-9213-50651e18f259 ro quiet echo 'Loading initial ramdisk ...' initrd /boot/initrd.img-2.6.32-5-686 } Any help is appreciated. Thanks, James _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Mon Feb 25 15:25:18 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 25 Feb 2013 15:25: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 1U9zua-000759-BB; Mon, 25 Feb 2013 15:24:16 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U9zuY-00074y-ND for xen-users@lists.xen.org; Mon, 25 Feb 2013 15:24:14 +0000 Received: from [85.158.138.51:8664] by server-11.bemta-3.messagelabs.com id D1/D7-10249-D128B215; Mon, 25 Feb 2013 15:24:13 +0000 X-Env-Sender: jep@obrien-pifer.com X-Msg-Ref: server-3.tower-174.messagelabs.com!1361805852!21011784!1 X-Originating-IP: [75.180.132.120] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: QmFkIElQOiA3NS4xODAuMTMyLjEyMCA9PiA5OTIwNw==\n,sa_preprocessor: QmFkIElQOiA3NS4xODAuMTMyLjEyMCA9PiA5OTIwNw==\n X-StarScan-Received: X-StarScan-Version: 6.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 8559 invoked from network); 25 Feb 2013 15:24:12 -0000 Received: from cdptpa-omtalb.mail.rr.com (HELO cdptpa-omtalb.mail.rr.com) (75.180.132.120) by server-3.tower-174.messagelabs.com with SMTP; 25 Feb 2013 15:24:12 -0000 X-Authority-Analysis: v=2.0 cv=XL2yuHdE c=1 sm=0 a=khvKJusKvADddYwUSfUZmw==:17 a=s-1hg7RLGykA:10 a=zopZFYjvPDYA:10 a=u769Oq3-vAwA:10 a=i7z8CvP5fyYA:10 a=8nJEP1OIZ-IA:10 a=oZXU78TAAAAA:8 a=iTPvVhlw94UA:10 a=ahZqYPGVh96QI-fWcSUA:9 a=wPNLvfGTeEIA:10 a=khvKJusKvADddYwUSfUZmw==:117 X-Cloudmark-Score: 0 X-Authenticated-User: X-Originating-IP: 96.10.171.230 Received: from [96.10.171.230] ([96.10.171.230:57990] helo=mailserver.obrien-pifer.com) by cdptpa-oedge04.mail.rr.com (envelope-from ) (ecelerity 2.2.3.46 r()) with ESMTP id 70/72-25887-9128B215; Mon, 25 Feb 2013 15:24:11 +0000 Received: from [10.99.1.24] ([10.99.1.24]) (authenticated bits=0) by mailserver.obrien-pifer.com (8.13.8/8.13.8) with ESMTP id r1PFOFWv017041 for ; Mon, 25 Feb 2013 10:24:15 -0500 Message-ID: <512B8216.70105@obrien-pifer.com> Date: Mon, 25 Feb 2013 10:24:06 -0500 From: James Pifer User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130215 Thunderbird/17.0.3 MIME-Version: 1.0 To: xen-users@lists.xen.org Subject: [Xen-users] Convert Debian 6 from HVM to PV X-BeenThere: xen-users@lists.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 have a couple Debian 6 HVM VMs. From what I've read, Debian 6's standard kernels have pv_ops already enabled. I'd like to convert these to pv for the following reasons (Assuming both of are valid expectations): 1) so the VMs use pv for the NICs 2) so the VMs properly respond to shutdown/reboot commands from xm I'm having trouble converting them. I believe need to convert the menu from something like this: root (hd0,0) kernel /xen.gz-2.6.18-53.1.14.el5 module /vmlinuz-2.6.18-53.1.14.el5xen ro root=LABEL=/ module /myinitrd.img to something like this: root (hd0,0) kernel /vmlinuz-2.6.18-53.1.14.el5xen ro root=LABEL=/ initrd /myinitrd.img The Debian 6 VMs I have appear to use grub2, which is a pain in the rear as far as I can tell. I expect there are good reasons for it, but being able to modify a menu.lst makes this transition much easier. The top of the file says to use /etc/grub.d and settings from /etc/default/grub to update grub.cfg, but I can't figure out how they build the menu section. Here's the menu section of grub.cfg. Can anyone give me some help on changing this to the proper form for booting pv? ### BEGIN /etc/grub.d/10_linux ### menuentry 'Debian GNU/Linux, with Linux 2.6.32-5-686' --class debian --class gnu-linux --class gnu --class os { insmod part_msdos insmod ext2 set root='(hd0,msdos1)' search --no-floppy --fs-uuid --set 8d0d1b45-e312-49ee-9213-50651e18f259 echo 'Loading Linux 2.6.32-5-686 ...' linux /boot/vmlinuz-2.6.32-5-686 root=UUID=8d0d1b45-e312-49ee-9213-50651e18f259 ro quiet echo 'Loading initial ramdisk ...' initrd /boot/initrd.img-2.6.32-5-686 } Any help is appreciated. Thanks, James _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Mon Feb 25 15:29:28 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 25 Feb 2013 15:29: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 1U9zyu-0007N2-AZ; Mon, 25 Feb 2013 15:28:44 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U9zys-0007Ml-GZ for xen-users@lists.xen.org; Mon, 25 Feb 2013 15:28:42 +0000 Received: from [85.158.139.83:46531] by server-15.bemta-5.messagelabs.com id 98/C5-22815-9238B215; Mon, 25 Feb 2013 15:28:41 +0000 X-Env-Sender: Ian.Campbell@citrix.com X-Msg-Ref: server-5.tower-182.messagelabs.com!1361806114!28884648!1 X-Originating-IP: [46.33.159.39] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNDYuMzMuMTU5LjM5ID0+IDIzOTg5\n X-StarScan-Received: X-StarScan-Version: 6.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 22502 invoked from network); 25 Feb 2013 15:28:35 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (46.33.159.39) by server-5.tower-182.messagelabs.com with RC4-SHA encrypted SMTP; 25 Feb 2013 15:28:35 -0000 X-IronPort-AV: E=Sophos;i="4.84,735,1355097600"; d="scan'208";a="1847728" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 25 Feb 2013 15:28:35 +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.297.1; Mon, 25 Feb 2013 15:28:34 +0000 Message-ID: <1361806106.26546.187.camel@zakaz.uk.xensource.com> From: Ian Campbell To: James Pifer Date: Mon, 25 Feb 2013 15:28:26 +0000 In-Reply-To: <512B8216.70105@obrien-pifer.com> References: <512B8216.70105@obrien-pifer.com> Organization: Citrix Systems, Inc. X-Mailer: Evolution 3.4.4-1 MIME-Version: 1.0 Cc: "xen-users@lists.xen.org" Subject: Re: [Xen-users] Convert Debian 6 from HVM to PV X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: 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, 2013-02-25 at 15:24 +0000, James Pifer wrote: > I'm having trouble converting them. I believe need to convert the menu > from something like this: > root (hd0,0) > kernel /xen.gz-2.6.18-53.1.14.el5 > module /vmlinuz-2.6.18-53.1.14.el5xen ro root=LABEL=/ > module /myinitrd.img > > to something like this: > root (hd0,0) > kernel /vmlinuz-2.6.18-53.1.14.el5xen ro root=LABEL=/ > initrd /myinitrd.img This isn't strictly necessary since pygrub will happily ignore the first xen.gz line and in any case this syntax is specific to RH, under Debian in a guest with grub the entries will be similar to the second form anyway. > The Debian 6 VMs I have appear to use grub2, which is a pain in the rear > as far as I can tell. I expect there are good reasons for it, but being > able to modify a menu.lst makes this transition much easier. The top of > the file says to use /etc/grub.d and settings from /etc/default/grub to > update grub.cfg, but I can't figure out how they build the menu section. update-grub runs the scripts under /etc/grub.d. > Here's the menu section of grub.cfg. Can anyone give me some help on > changing this to the proper form for booting pv? > > ### BEGIN /etc/grub.d/10_linux ### > menuentry 'Debian GNU/Linux, with Linux 2.6.32-5-686' --class debian > --class gnu-linux --class gnu --class os { > insmod part_msdos > insmod ext2 > set root='(hd0,msdos1)' > search --no-floppy --fs-uuid --set > 8d0d1b45-e312-49ee-9213-50651e18f259 > echo 'Loading Linux 2.6.32-5-686 ...' > linux /boot/vmlinuz-2.6.32-5-686 > root=UUID=8d0d1b45-e312-49ee-9213-50651e18f259 ro quiet > echo 'Loading initial ramdisk ...' > initrd /boot/initrd.img-2.6.32-5-686 > } This already looks correct, except you need to install the 686-bigmem kernel flavour and not the -686 flavour to get Xen support. Ian. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Mon Feb 25 15:29:28 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 25 Feb 2013 15:29: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 1U9zyu-0007N2-AZ; Mon, 25 Feb 2013 15:28:44 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U9zys-0007Ml-GZ for xen-users@lists.xen.org; Mon, 25 Feb 2013 15:28:42 +0000 Received: from [85.158.139.83:46531] by server-15.bemta-5.messagelabs.com id 98/C5-22815-9238B215; Mon, 25 Feb 2013 15:28:41 +0000 X-Env-Sender: Ian.Campbell@citrix.com X-Msg-Ref: server-5.tower-182.messagelabs.com!1361806114!28884648!1 X-Originating-IP: [46.33.159.39] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNDYuMzMuMTU5LjM5ID0+IDIzOTg5\n X-StarScan-Received: X-StarScan-Version: 6.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 22502 invoked from network); 25 Feb 2013 15:28:35 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (46.33.159.39) by server-5.tower-182.messagelabs.com with RC4-SHA encrypted SMTP; 25 Feb 2013 15:28:35 -0000 X-IronPort-AV: E=Sophos;i="4.84,735,1355097600"; d="scan'208";a="1847728" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 25 Feb 2013 15:28:35 +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.297.1; Mon, 25 Feb 2013 15:28:34 +0000 Message-ID: <1361806106.26546.187.camel@zakaz.uk.xensource.com> From: Ian Campbell To: James Pifer Date: Mon, 25 Feb 2013 15:28:26 +0000 In-Reply-To: <512B8216.70105@obrien-pifer.com> References: <512B8216.70105@obrien-pifer.com> Organization: Citrix Systems, Inc. X-Mailer: Evolution 3.4.4-1 MIME-Version: 1.0 Cc: "xen-users@lists.xen.org" Subject: Re: [Xen-users] Convert Debian 6 from HVM to PV X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: 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, 2013-02-25 at 15:24 +0000, James Pifer wrote: > I'm having trouble converting them. I believe need to convert the menu > from something like this: > root (hd0,0) > kernel /xen.gz-2.6.18-53.1.14.el5 > module /vmlinuz-2.6.18-53.1.14.el5xen ro root=LABEL=/ > module /myinitrd.img > > to something like this: > root (hd0,0) > kernel /vmlinuz-2.6.18-53.1.14.el5xen ro root=LABEL=/ > initrd /myinitrd.img This isn't strictly necessary since pygrub will happily ignore the first xen.gz line and in any case this syntax is specific to RH, under Debian in a guest with grub the entries will be similar to the second form anyway. > The Debian 6 VMs I have appear to use grub2, which is a pain in the rear > as far as I can tell. I expect there are good reasons for it, but being > able to modify a menu.lst makes this transition much easier. The top of > the file says to use /etc/grub.d and settings from /etc/default/grub to > update grub.cfg, but I can't figure out how they build the menu section. update-grub runs the scripts under /etc/grub.d. > Here's the menu section of grub.cfg. Can anyone give me some help on > changing this to the proper form for booting pv? > > ### BEGIN /etc/grub.d/10_linux ### > menuentry 'Debian GNU/Linux, with Linux 2.6.32-5-686' --class debian > --class gnu-linux --class gnu --class os { > insmod part_msdos > insmod ext2 > set root='(hd0,msdos1)' > search --no-floppy --fs-uuid --set > 8d0d1b45-e312-49ee-9213-50651e18f259 > echo 'Loading Linux 2.6.32-5-686 ...' > linux /boot/vmlinuz-2.6.32-5-686 > root=UUID=8d0d1b45-e312-49ee-9213-50651e18f259 ro quiet > echo 'Loading initial ramdisk ...' > initrd /boot/initrd.img-2.6.32-5-686 > } This already looks correct, except you need to install the 686-bigmem kernel flavour and not the -686 flavour to get Xen support. Ian. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Mon Feb 25 15:40:28 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 25 Feb 2013 15: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 1UA09K-00082Y-Oh; Mon, 25 Feb 2013 15:39:30 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UA09J-00082T-G8 for xen-users@lists.xen.org; Mon, 25 Feb 2013 15:39:29 +0000 Received: from [85.158.143.99:11523] by server-3.bemta-4.messagelabs.com id E6/47-02186-0B58B215; Mon, 25 Feb 2013 15:39:28 +0000 X-Env-Sender: jep@obrien-pifer.com X-Msg-Ref: server-16.tower-216.messagelabs.com!1361806767!17651347!1 X-Originating-IP: [75.180.132.120] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: QmFkIElQOiA3NS4xODAuMTMyLjEyMCA9PiA5OTIwNw==\n,sa_preprocessor: QmFkIElQOiA3NS4xODAuMTMyLjEyMCA9PiA5OTIwNw==\n X-StarScan-Received: X-StarScan-Version: 6.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 3640 invoked from network); 25 Feb 2013 15:39:27 -0000 Received: from cdptpa-omtalb.mail.rr.com (HELO cdptpa-omtalb.mail.rr.com) (75.180.132.120) by server-16.tower-216.messagelabs.com with SMTP; 25 Feb 2013 15:39:27 -0000 X-Authority-Analysis: v=2.0 cv=cYNQXw/M c=1 sm=0 a=khvKJusKvADddYwUSfUZmw==:17 a=s-1hg7RLGykA:10 a=zopZFYjvPDYA:10 a=k2oRjC8FvpoA:10 a=i7z8CvP5fyYA:10 a=IkcTkHD0fZMA:10 a=oZXU78TAAAAA:8 a=lsQzyE-9icYA:10 a=ouWR-Ea6SF9mT73WuhoA:9 a=QEXdDO2ut3YA:10 a=khvKJusKvADddYwUSfUZmw==:117 X-Cloudmark-Score: 0 X-Authenticated-User: X-Originating-IP: 96.10.171.230 Received: from [96.10.171.230] ([96.10.171.230:58060] helo=mailserver.obrien-pifer.com) by cdptpa-oedge03.mail.rr.com (envelope-from ) (ecelerity 2.2.3.46 r()) with ESMTP id C9/87-11869-8A58B215; Mon, 25 Feb 2013 15:39:27 +0000 Received: from [10.99.1.24] ([10.99.1.24]) (authenticated bits=0) by mailserver.obrien-pifer.com (8.13.8/8.13.8) with ESMTP id r1PFdQtA017173; Mon, 25 Feb 2013 10:39:26 -0500 Message-ID: <512B85A5.1060801@obrien-pifer.com> Date: Mon, 25 Feb 2013 10:39:17 -0500 From: James Pifer User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130215 Thunderbird/17.0.3 MIME-Version: 1.0 To: Ian Campbell References: <512B8216.70105@obrien-pifer.com> <1361806106.26546.187.camel@zakaz.uk.xensource.com> In-Reply-To: <1361806106.26546.187.camel@zakaz.uk.xensource.com> Cc: "xen-users@lists.xen.org" Subject: Re: [Xen-users] Convert Debian 6 from HVM to PV X-BeenThere: xen-users@lists.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 > This already looks correct, except you need to install the 686-bigmem > kernel flavour and not the -686 flavour to get Xen support. > > Ian. > Ian, Thanks for the quick response. If I understand you correctly, if I install 686-bigmem kernel then pygrub should happily boot it? Might be jumping the gun, but how do I make 686-bigmem the default after installing or will that happen automatically being the last kernel installed? (yes, my example menu was from a centos machine) Thanks again, James _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Mon Feb 25 15:40:28 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 25 Feb 2013 15: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 1UA09K-00082Y-Oh; Mon, 25 Feb 2013 15:39:30 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UA09J-00082T-G8 for xen-users@lists.xen.org; Mon, 25 Feb 2013 15:39:29 +0000 Received: from [85.158.143.99:11523] by server-3.bemta-4.messagelabs.com id E6/47-02186-0B58B215; Mon, 25 Feb 2013 15:39:28 +0000 X-Env-Sender: jep@obrien-pifer.com X-Msg-Ref: server-16.tower-216.messagelabs.com!1361806767!17651347!1 X-Originating-IP: [75.180.132.120] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: QmFkIElQOiA3NS4xODAuMTMyLjEyMCA9PiA5OTIwNw==\n,sa_preprocessor: QmFkIElQOiA3NS4xODAuMTMyLjEyMCA9PiA5OTIwNw==\n X-StarScan-Received: X-StarScan-Version: 6.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 3640 invoked from network); 25 Feb 2013 15:39:27 -0000 Received: from cdptpa-omtalb.mail.rr.com (HELO cdptpa-omtalb.mail.rr.com) (75.180.132.120) by server-16.tower-216.messagelabs.com with SMTP; 25 Feb 2013 15:39:27 -0000 X-Authority-Analysis: v=2.0 cv=cYNQXw/M c=1 sm=0 a=khvKJusKvADddYwUSfUZmw==:17 a=s-1hg7RLGykA:10 a=zopZFYjvPDYA:10 a=k2oRjC8FvpoA:10 a=i7z8CvP5fyYA:10 a=IkcTkHD0fZMA:10 a=oZXU78TAAAAA:8 a=lsQzyE-9icYA:10 a=ouWR-Ea6SF9mT73WuhoA:9 a=QEXdDO2ut3YA:10 a=khvKJusKvADddYwUSfUZmw==:117 X-Cloudmark-Score: 0 X-Authenticated-User: X-Originating-IP: 96.10.171.230 Received: from [96.10.171.230] ([96.10.171.230:58060] helo=mailserver.obrien-pifer.com) by cdptpa-oedge03.mail.rr.com (envelope-from ) (ecelerity 2.2.3.46 r()) with ESMTP id C9/87-11869-8A58B215; Mon, 25 Feb 2013 15:39:27 +0000 Received: from [10.99.1.24] ([10.99.1.24]) (authenticated bits=0) by mailserver.obrien-pifer.com (8.13.8/8.13.8) with ESMTP id r1PFdQtA017173; Mon, 25 Feb 2013 10:39:26 -0500 Message-ID: <512B85A5.1060801@obrien-pifer.com> Date: Mon, 25 Feb 2013 10:39:17 -0500 From: James Pifer User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130215 Thunderbird/17.0.3 MIME-Version: 1.0 To: Ian Campbell References: <512B8216.70105@obrien-pifer.com> <1361806106.26546.187.camel@zakaz.uk.xensource.com> In-Reply-To: <1361806106.26546.187.camel@zakaz.uk.xensource.com> Cc: "xen-users@lists.xen.org" Subject: Re: [Xen-users] Convert Debian 6 from HVM to PV X-BeenThere: xen-users@lists.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 > This already looks correct, except you need to install the 686-bigmem > kernel flavour and not the -686 flavour to get Xen support. > > Ian. > Ian, Thanks for the quick response. If I understand you correctly, if I install 686-bigmem kernel then pygrub should happily boot it? Might be jumping the gun, but how do I make 686-bigmem the default after installing or will that happen automatically being the last kernel installed? (yes, my example menu was from a centos machine) Thanks again, James _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Mon Feb 25 15:45:36 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 25 Feb 2013 15:45: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 1UA0EV-0000Jq-3q; Mon, 25 Feb 2013 15:44:51 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UA0ET-0000JX-2E for xen-users@lists.xen.org; Mon, 25 Feb 2013 15:44:49 +0000 Received: from [85.158.139.83:50119] by server-2.bemta-5.messagelabs.com id 5A/D3-23989-0F68B215; Mon, 25 Feb 2013 15:44:48 +0000 X-Env-Sender: Ian.Campbell@citrix.com X-Msg-Ref: server-10.tower-182.messagelabs.com!1361807087!29109108!1 X-Originating-IP: [46.33.159.39] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNDYuMzMuMTU5LjM5ID0+IDIzOTg5\n X-StarScan-Received: X-StarScan-Version: 6.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 8259 invoked from network); 25 Feb 2013 15:44:47 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (46.33.159.39) by server-10.tower-182.messagelabs.com with RC4-SHA encrypted SMTP; 25 Feb 2013 15:44:47 -0000 X-IronPort-AV: E=Sophos;i="4.84,735,1355097600"; d="scan'208";a="1848444" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 25 Feb 2013 15:44: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.297.1; Mon, 25 Feb 2013 15:44:47 +0000 Message-ID: <1361807084.26546.194.camel@zakaz.uk.xensource.com> From: Ian Campbell To: James Pifer Date: Mon, 25 Feb 2013 15:44:44 +0000 In-Reply-To: <512B85A5.1060801@obrien-pifer.com> References: <512B8216.70105@obrien-pifer.com> <1361806106.26546.187.camel@zakaz.uk.xensource.com> <512B85A5.1060801@obrien-pifer.com> Organization: Citrix Systems, Inc. X-Mailer: Evolution 3.4.4-1 MIME-Version: 1.0 Cc: "xen-users@lists.xen.org" Subject: Re: [Xen-users] Convert Debian 6 from HVM to PV X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: 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, 2013-02-25 at 15:39 +0000, James Pifer wrote: > Thanks for the quick response. If I understand you correctly, if I > install 686-bigmem kernel then pygrub should happily boot it? Yes. > Might be jumping the gun, but how do I make 686-bigmem the default after > installing or will that happen automatically being the last kernel > installed? Well, I would uninstall the others. But pygrub is interactive so you can just select the one you want. I expect you could also set /etc/default/grub:GRUB_DEFAULT to the index of the entry to boot. You can also pass --entry=N to pygrub via the bootloader_args option in your guest 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 Feb 25 15:45:36 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 25 Feb 2013 15:45: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 1UA0EV-0000Jq-3q; Mon, 25 Feb 2013 15:44:51 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UA0ET-0000JX-2E for xen-users@lists.xen.org; Mon, 25 Feb 2013 15:44:49 +0000 Received: from [85.158.139.83:50119] by server-2.bemta-5.messagelabs.com id 5A/D3-23989-0F68B215; Mon, 25 Feb 2013 15:44:48 +0000 X-Env-Sender: Ian.Campbell@citrix.com X-Msg-Ref: server-10.tower-182.messagelabs.com!1361807087!29109108!1 X-Originating-IP: [46.33.159.39] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNDYuMzMuMTU5LjM5ID0+IDIzOTg5\n X-StarScan-Received: X-StarScan-Version: 6.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 8259 invoked from network); 25 Feb 2013 15:44:47 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (46.33.159.39) by server-10.tower-182.messagelabs.com with RC4-SHA encrypted SMTP; 25 Feb 2013 15:44:47 -0000 X-IronPort-AV: E=Sophos;i="4.84,735,1355097600"; d="scan'208";a="1848444" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 25 Feb 2013 15:44: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.297.1; Mon, 25 Feb 2013 15:44:47 +0000 Message-ID: <1361807084.26546.194.camel@zakaz.uk.xensource.com> From: Ian Campbell To: James Pifer Date: Mon, 25 Feb 2013 15:44:44 +0000 In-Reply-To: <512B85A5.1060801@obrien-pifer.com> References: <512B8216.70105@obrien-pifer.com> <1361806106.26546.187.camel@zakaz.uk.xensource.com> <512B85A5.1060801@obrien-pifer.com> Organization: Citrix Systems, Inc. X-Mailer: Evolution 3.4.4-1 MIME-Version: 1.0 Cc: "xen-users@lists.xen.org" Subject: Re: [Xen-users] Convert Debian 6 from HVM to PV X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: 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, 2013-02-25 at 15:39 +0000, James Pifer wrote: > Thanks for the quick response. If I understand you correctly, if I > install 686-bigmem kernel then pygrub should happily boot it? Yes. > Might be jumping the gun, but how do I make 686-bigmem the default after > installing or will that happen automatically being the last kernel > installed? Well, I would uninstall the others. But pygrub is interactive so you can just select the one you want. I expect you could also set /etc/default/grub:GRUB_DEFAULT to the index of the entry to boot. You can also pass --entry=N to pygrub via the bootloader_args option in your guest 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 Feb 25 16:30:52 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 25 Feb 2013 16:30: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 1UA0wI-0003fG-6I; Mon, 25 Feb 2013 16:30:06 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UA0wH-0003em-5Q for xen-users@lists.xen.org; Mon, 25 Feb 2013 16:30:05 +0000 Received: from [85.158.138.51:45264] by server-10.bemta-3.messagelabs.com id 33/FF-10609-C819B215; Mon, 25 Feb 2013 16:30:04 +0000 X-Env-Sender: jep@obrien-pifer.com X-Msg-Ref: server-16.tower-174.messagelabs.com!1361809803!29038598!1 X-Originating-IP: [75.180.132.120] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: QmFkIElQOiA3NS4xODAuMTMyLjEyMCA9PiA5OTIwNw==\n,sa_preprocessor: QmFkIElQOiA3NS4xODAuMTMyLjEyMCA9PiA5OTIwNw==\n X-StarScan-Received: X-StarScan-Version: 6.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 13650 invoked from network); 25 Feb 2013 16:30:03 -0000 Received: from cdptpa-omtalb.mail.rr.com (HELO cdptpa-omtalb.mail.rr.com) (75.180.132.120) by server-16.tower-174.messagelabs.com with SMTP; 25 Feb 2013 16:30:03 -0000 X-Authority-Analysis: v=2.0 cv=XL2yuHdE c=1 sm=0 a=khvKJusKvADddYwUSfUZmw==:17 a=s-1hg7RLGykA:10 a=zopZFYjvPDYA:10 a=k2oRjC8FvpoA:10 a=i7z8CvP5fyYA:10 a=IkcTkHD0fZMA:10 a=oZXU78TAAAAA:8 a=lsQzyE-9icYA:10 a=A2wPb1XKGpuKD34g36gA:9 a=QEXdDO2ut3YA:10 a=khvKJusKvADddYwUSfUZmw==:117 X-Cloudmark-Score: 0 X-Authenticated-User: X-Originating-IP: 96.10.171.230 Received: from [96.10.171.230] ([96.10.171.230:58269] helo=mailserver.obrien-pifer.com) by cdptpa-oedge04.mail.rr.com (envelope-from ) (ecelerity 2.2.3.46 r()) with ESMTP id D0/AF-25887-7819B215; Mon, 25 Feb 2013 16:30:01 +0000 Received: from [10.99.1.24] ([10.99.1.24]) (authenticated bits=0) by mailserver.obrien-pifer.com (8.13.8/8.13.8) with ESMTP id r1PGU5OL017832; Mon, 25 Feb 2013 11:30:05 -0500 Message-ID: <512B9184.1090307@obrien-pifer.com> Date: Mon, 25 Feb 2013 11:29:56 -0500 From: James Pifer User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130215 Thunderbird/17.0.3 MIME-Version: 1.0 To: Ian Campbell References: <512B8216.70105@obrien-pifer.com> <1361806106.26546.187.camel@zakaz.uk.xensource.com> <512B85A5.1060801@obrien-pifer.com> <1361807084.26546.194.camel@zakaz.uk.xensource.com> In-Reply-To: <1361807084.26546.194.camel@zakaz.uk.xensource.com> Cc: "xen-users@lists.xen.org" Subject: Re: [Xen-users] Convert Debian 6 from HVM to PV X-BeenThere: xen-users@lists.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 2/25/2013 10:44 AM, Ian Campbell wrote: > On Mon, 2013-02-25 at 15:39 +0000, James Pifer wrote: >> Thanks for the quick response. If I understand you correctly, if I >> install 686-bigmem kernel then pygrub should happily boot it? > Yes. > >> Might be jumping the gun, but how do I make 686-bigmem the default after >> installing or will that happen automatically being the last kernel >> installed? > Well, I would uninstall the others. > > But pygrub is interactive so you can just select the one you want. I > expect you could also set /etc/default/grub:GRUB_DEFAULT to the index of > the entry to boot. You can also pass --entry=N to pygrub via the > bootloader_args option in your guest configuration. > > Ian. > Ian, Worked great. Thanks for the help! James _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Mon Feb 25 16:30:52 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 25 Feb 2013 16:30: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 1UA0wI-0003fG-6I; Mon, 25 Feb 2013 16:30:06 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UA0wH-0003em-5Q for xen-users@lists.xen.org; Mon, 25 Feb 2013 16:30:05 +0000 Received: from [85.158.138.51:45264] by server-10.bemta-3.messagelabs.com id 33/FF-10609-C819B215; Mon, 25 Feb 2013 16:30:04 +0000 X-Env-Sender: jep@obrien-pifer.com X-Msg-Ref: server-16.tower-174.messagelabs.com!1361809803!29038598!1 X-Originating-IP: [75.180.132.120] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: QmFkIElQOiA3NS4xODAuMTMyLjEyMCA9PiA5OTIwNw==\n,sa_preprocessor: QmFkIElQOiA3NS4xODAuMTMyLjEyMCA9PiA5OTIwNw==\n X-StarScan-Received: X-StarScan-Version: 6.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 13650 invoked from network); 25 Feb 2013 16:30:03 -0000 Received: from cdptpa-omtalb.mail.rr.com (HELO cdptpa-omtalb.mail.rr.com) (75.180.132.120) by server-16.tower-174.messagelabs.com with SMTP; 25 Feb 2013 16:30:03 -0000 X-Authority-Analysis: v=2.0 cv=XL2yuHdE c=1 sm=0 a=khvKJusKvADddYwUSfUZmw==:17 a=s-1hg7RLGykA:10 a=zopZFYjvPDYA:10 a=k2oRjC8FvpoA:10 a=i7z8CvP5fyYA:10 a=IkcTkHD0fZMA:10 a=oZXU78TAAAAA:8 a=lsQzyE-9icYA:10 a=A2wPb1XKGpuKD34g36gA:9 a=QEXdDO2ut3YA:10 a=khvKJusKvADddYwUSfUZmw==:117 X-Cloudmark-Score: 0 X-Authenticated-User: X-Originating-IP: 96.10.171.230 Received: from [96.10.171.230] ([96.10.171.230:58269] helo=mailserver.obrien-pifer.com) by cdptpa-oedge04.mail.rr.com (envelope-from ) (ecelerity 2.2.3.46 r()) with ESMTP id D0/AF-25887-7819B215; Mon, 25 Feb 2013 16:30:01 +0000 Received: from [10.99.1.24] ([10.99.1.24]) (authenticated bits=0) by mailserver.obrien-pifer.com (8.13.8/8.13.8) with ESMTP id r1PGU5OL017832; Mon, 25 Feb 2013 11:30:05 -0500 Message-ID: <512B9184.1090307@obrien-pifer.com> Date: Mon, 25 Feb 2013 11:29:56 -0500 From: James Pifer User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130215 Thunderbird/17.0.3 MIME-Version: 1.0 To: Ian Campbell References: <512B8216.70105@obrien-pifer.com> <1361806106.26546.187.camel@zakaz.uk.xensource.com> <512B85A5.1060801@obrien-pifer.com> <1361807084.26546.194.camel@zakaz.uk.xensource.com> In-Reply-To: <1361807084.26546.194.camel@zakaz.uk.xensource.com> Cc: "xen-users@lists.xen.org" Subject: Re: [Xen-users] Convert Debian 6 from HVM to PV X-BeenThere: xen-users@lists.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 2/25/2013 10:44 AM, Ian Campbell wrote: > On Mon, 2013-02-25 at 15:39 +0000, James Pifer wrote: >> Thanks for the quick response. If I understand you correctly, if I >> install 686-bigmem kernel then pygrub should happily boot it? > Yes. > >> Might be jumping the gun, but how do I make 686-bigmem the default after >> installing or will that happen automatically being the last kernel >> installed? > Well, I would uninstall the others. > > But pygrub is interactive so you can just select the one you want. I > expect you could also set /etc/default/grub:GRUB_DEFAULT to the index of > the entry to boot. You can also pass --entry=N to pygrub via the > bootloader_args option in your guest configuration. > > Ian. > Ian, Worked great. Thanks for the help! James _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Mon Feb 25 16:55:31 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 25 Feb 2013 16:55: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 1UA1K3-0005x1-7N; Mon, 25 Feb 2013 16:54:39 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U9t5V-0007On-4S for xen-users@lists.xen.org; Mon, 25 Feb 2013 08:07:05 +0000 Received: from [85.158.137.99:58329] by server-7.bemta-3.messagelabs.com id 5B/CE-10367-8AB1B215; Mon, 25 Feb 2013 08:07:04 +0000 X-Env-Sender: choonho.son@gmail.com X-Msg-Ref: server-3.tower-217.messagelabs.com!1361779614!12248472!1 X-Originating-IP: [209.85.128.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.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 12589 invoked from network); 25 Feb 2013 08:06:55 -0000 Received: from mail-qe0-f43.google.com (HELO mail-qe0-f43.google.com) (209.85.128.43) by server-3.tower-217.messagelabs.com with RC4-SHA encrypted SMTP; 25 Feb 2013 08:06:55 -0000 Received: by mail-qe0-f43.google.com with SMTP id s14so1410510qeb.30 for ; Mon, 25 Feb 2013 00:06:53 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:date:message-id:subject:from:to :content-type; bh=pH1Ex2UP3w9NZDKEZEVtRVWQOolL7JMtrIeiALMQnvE=; b=QalmwIuZ2M2WK3yvVgZIoc6LQP+nK2ZPme+dZWLr9MoUovqAb8K0nyfp0gq/jAs7Ah z+3YCRnp/GbF0r0mNY3yrO6SHIomfuMym1EHRauc2uZ25gUOLoVxKnHErntIWnqNpUix DlZ+GruJxCW9+Z265aPQj1tLaqGvtovobYjL1NBeIxy/px2F8qoTJTvQ/90GQ5pmN7C+ 8YeDEQk12JVT4TuYNSVkMnCvk+TJsqMpaddHdo9G+dY+3ch4VVve1dGKN4Rcgf+ugQsT Iad8TG1cScq+jaS26kWInc4vzcK6BvnWnel0ACFYW0o8CAnTwtwf/1sNtxtL53LLBHYv jX3w== MIME-Version: 1.0 X-Received: by 10.224.86.206 with SMTP id t14mr10049005qal.90.1361779613758; Mon, 25 Feb 2013 00:06:53 -0800 (PST) Received: by 10.49.119.230 with HTTP; Mon, 25 Feb 2013 00:06:53 -0800 (PST) Date: Mon, 25 Feb 2013 17:06:53 +0900 Message-ID: From: Choonho Son To: xen-users X-Mailman-Approved-At: Mon, 25 Feb 2013 16:54:37 +0000 Subject: [Xen-users] Hypervisor-mode(Intel VT-x) 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 Hi All, I confused with hypervisor-mode(Intel VT-x) and HVM. Does only HVM guest use hypervisor-mode? PV guest does not use Intel VT-x. Thanks, _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Mon Feb 25 16:55:31 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 25 Feb 2013 16:55: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 1UA1K3-0005x1-7N; Mon, 25 Feb 2013 16:54:39 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U9t5V-0007On-4S for xen-users@lists.xen.org; Mon, 25 Feb 2013 08:07:05 +0000 Received: from [85.158.137.99:58329] by server-7.bemta-3.messagelabs.com id 5B/CE-10367-8AB1B215; Mon, 25 Feb 2013 08:07:04 +0000 X-Env-Sender: choonho.son@gmail.com X-Msg-Ref: server-3.tower-217.messagelabs.com!1361779614!12248472!1 X-Originating-IP: [209.85.128.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.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 12589 invoked from network); 25 Feb 2013 08:06:55 -0000 Received: from mail-qe0-f43.google.com (HELO mail-qe0-f43.google.com) (209.85.128.43) by server-3.tower-217.messagelabs.com with RC4-SHA encrypted SMTP; 25 Feb 2013 08:06:55 -0000 Received: by mail-qe0-f43.google.com with SMTP id s14so1410510qeb.30 for ; Mon, 25 Feb 2013 00:06:53 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:date:message-id:subject:from:to :content-type; bh=pH1Ex2UP3w9NZDKEZEVtRVWQOolL7JMtrIeiALMQnvE=; b=QalmwIuZ2M2WK3yvVgZIoc6LQP+nK2ZPme+dZWLr9MoUovqAb8K0nyfp0gq/jAs7Ah z+3YCRnp/GbF0r0mNY3yrO6SHIomfuMym1EHRauc2uZ25gUOLoVxKnHErntIWnqNpUix DlZ+GruJxCW9+Z265aPQj1tLaqGvtovobYjL1NBeIxy/px2F8qoTJTvQ/90GQ5pmN7C+ 8YeDEQk12JVT4TuYNSVkMnCvk+TJsqMpaddHdo9G+dY+3ch4VVve1dGKN4Rcgf+ugQsT Iad8TG1cScq+jaS26kWInc4vzcK6BvnWnel0ACFYW0o8CAnTwtwf/1sNtxtL53LLBHYv jX3w== MIME-Version: 1.0 X-Received: by 10.224.86.206 with SMTP id t14mr10049005qal.90.1361779613758; Mon, 25 Feb 2013 00:06:53 -0800 (PST) Received: by 10.49.119.230 with HTTP; Mon, 25 Feb 2013 00:06:53 -0800 (PST) Date: Mon, 25 Feb 2013 17:06:53 +0900 Message-ID: From: Choonho Son To: xen-users X-Mailman-Approved-At: Mon, 25 Feb 2013 16:54:37 +0000 Subject: [Xen-users] Hypervisor-mode(Intel VT-x) 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 Hi All, I confused with hypervisor-mode(Intel VT-x) and HVM. Does only HVM guest use hypervisor-mode? PV guest does not use Intel VT-x. Thanks, _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Mon Feb 25 17:22:18 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 25 Feb 2013 17:22: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 1UA1k1-0008Ke-On; Mon, 25 Feb 2013 17:21:29 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UA1jz-0008KZ-Ho for xen-users@lists.xen.org; Mon, 25 Feb 2013 17:21:27 +0000 Received: from [85.158.143.99:15519] by server-2.bemta-4.messagelabs.com id B2/C1-12656-69D9B215; Mon, 25 Feb 2013 17:21:26 +0000 X-Env-Sender: tosterman@gmail.com X-Msg-Ref: server-2.tower-216.messagelabs.com!1361812884!22305316!1 X-Originating-IP: [209.85.223.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.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 6091 invoked from network); 25 Feb 2013 17:21:26 -0000 Received: from mail-ie0-f171.google.com (HELO mail-ie0-f171.google.com) (209.85.223.171) by server-2.tower-216.messagelabs.com with RC4-SHA encrypted SMTP; 25 Feb 2013 17:21:26 -0000 Received: by mail-ie0-f171.google.com with SMTP id 10so3378802ied.16 for ; Mon, 25 Feb 2013 09:21:24 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:reply-to:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=fHcUrZUxHbRLvTNy0IYXm13+EwHfmS/4LHzsZWjJKaw=; b=bYs6uMdkWWJCZfKYB15cRLrKC/PliolCPW++96bet7fxBxUGvwhV4CCHk4fQpqKGpW 8bwGJcc9pUWDirLawTjdYaAJkAD94XpbAKuHkd5rWVGfhC1aeApF0VEmPYIAh8xLAYxi gPSOVz3VDdHE3lJeVO0gBWG+S89iMYw0/2827icGYeVfNTmzE8Oq+MOcaMOU1KWj3BkA YxFyS2nDWckYXDObB647W7HEJ51/Q5Zc+gvRooVh5g4XrnoU813PwO5vWu8nQQM1vYdy R7erorF+C2+DKTDCmbE+KJMHMmmbM58Bacc7CXpvjebCsBT68BmYIqFDZSkuBCFBNCNM 3Ppg== MIME-Version: 1.0 X-Received: by 10.50.88.168 with SMTP id bh8mr3739972igb.67.1361812884365; Mon, 25 Feb 2013 09:21:24 -0800 (PST) Received: by 10.64.60.136 with HTTP; Mon, 25 Feb 2013 09:21:24 -0800 (PST) In-Reply-To: <1361805642.26546.184.camel@zakaz.uk.xensource.com> References: <1361784654.26546.165.camel@zakaz.uk.xensource.com> <1361805642.26546.184.camel@zakaz.uk.xensource.com> Date: Mon, 25 Feb 2013 12:21:24 -0500 Message-ID: From: Travis Osterman To: xen-users Cc: Ian Campbell Subject: Re: [Xen-users] pv guest fails to start after 4.2 upgrade X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: travis@wsor.net List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: 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 also tried to take pvgrub out of the picture so I mounted the image >> >> and copied my initrd and kernel to the dom0 file system and updated my >> >> config with the appropriate ramdisk and kernel lines. >> >> >> >> Full output without pvgrub >> >> http://pastebin.com/c7VWWwXk >> >> >> >> Which dropped me in a shell asking for my root partition (progress). >> >> # cat /var/log/xen/qemu-dm-prime.log >> bind(unix:/var/run/xen/qmp-libxl-4): No such file or directory >> chardev: opening backend "socket" failed: No such file or directory >> >> # ls /var/run/xen* >> /var/run/xenconsoled.pid /var/run/xenstored.pid >> >> /var/run/xenstored: >> socket socket_ro > > Ah, you are missing the /var/run/xen/ directory so it is failing to > create the socket, if you create the directory does it work? Although > even if so it is obviously still a bug that libxl doesn't handle that > error... Ian, I can confirm the manually creating /var/run/xen fixes the problem. I updated my bug report here https://bugs.gentoo.org/show_bug.cgi?id=459082 Thank you for the help. -- T _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Mon Feb 25 17:22:18 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 25 Feb 2013 17:22: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 1UA1k1-0008Ke-On; Mon, 25 Feb 2013 17:21:29 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UA1jz-0008KZ-Ho for xen-users@lists.xen.org; Mon, 25 Feb 2013 17:21:27 +0000 Received: from [85.158.143.99:15519] by server-2.bemta-4.messagelabs.com id B2/C1-12656-69D9B215; Mon, 25 Feb 2013 17:21:26 +0000 X-Env-Sender: tosterman@gmail.com X-Msg-Ref: server-2.tower-216.messagelabs.com!1361812884!22305316!1 X-Originating-IP: [209.85.223.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.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 6091 invoked from network); 25 Feb 2013 17:21:26 -0000 Received: from mail-ie0-f171.google.com (HELO mail-ie0-f171.google.com) (209.85.223.171) by server-2.tower-216.messagelabs.com with RC4-SHA encrypted SMTP; 25 Feb 2013 17:21:26 -0000 Received: by mail-ie0-f171.google.com with SMTP id 10so3378802ied.16 for ; Mon, 25 Feb 2013 09:21:24 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:reply-to:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=fHcUrZUxHbRLvTNy0IYXm13+EwHfmS/4LHzsZWjJKaw=; b=bYs6uMdkWWJCZfKYB15cRLrKC/PliolCPW++96bet7fxBxUGvwhV4CCHk4fQpqKGpW 8bwGJcc9pUWDirLawTjdYaAJkAD94XpbAKuHkd5rWVGfhC1aeApF0VEmPYIAh8xLAYxi gPSOVz3VDdHE3lJeVO0gBWG+S89iMYw0/2827icGYeVfNTmzE8Oq+MOcaMOU1KWj3BkA YxFyS2nDWckYXDObB647W7HEJ51/Q5Zc+gvRooVh5g4XrnoU813PwO5vWu8nQQM1vYdy R7erorF+C2+DKTDCmbE+KJMHMmmbM58Bacc7CXpvjebCsBT68BmYIqFDZSkuBCFBNCNM 3Ppg== MIME-Version: 1.0 X-Received: by 10.50.88.168 with SMTP id bh8mr3739972igb.67.1361812884365; Mon, 25 Feb 2013 09:21:24 -0800 (PST) Received: by 10.64.60.136 with HTTP; Mon, 25 Feb 2013 09:21:24 -0800 (PST) In-Reply-To: <1361805642.26546.184.camel@zakaz.uk.xensource.com> References: <1361784654.26546.165.camel@zakaz.uk.xensource.com> <1361805642.26546.184.camel@zakaz.uk.xensource.com> Date: Mon, 25 Feb 2013 12:21:24 -0500 Message-ID: From: Travis Osterman To: xen-users Cc: Ian Campbell Subject: Re: [Xen-users] pv guest fails to start after 4.2 upgrade X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: travis@wsor.net List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: 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 also tried to take pvgrub out of the picture so I mounted the image >> >> and copied my initrd and kernel to the dom0 file system and updated my >> >> config with the appropriate ramdisk and kernel lines. >> >> >> >> Full output without pvgrub >> >> http://pastebin.com/c7VWWwXk >> >> >> >> Which dropped me in a shell asking for my root partition (progress). >> >> # cat /var/log/xen/qemu-dm-prime.log >> bind(unix:/var/run/xen/qmp-libxl-4): No such file or directory >> chardev: opening backend "socket" failed: No such file or directory >> >> # ls /var/run/xen* >> /var/run/xenconsoled.pid /var/run/xenstored.pid >> >> /var/run/xenstored: >> socket socket_ro > > Ah, you are missing the /var/run/xen/ directory so it is failing to > create the socket, if you create the directory does it work? Although > even if so it is obviously still a bug that libxl doesn't handle that > error... Ian, I can confirm the manually creating /var/run/xen fixes the problem. I updated my bug report here https://bugs.gentoo.org/show_bug.cgi?id=459082 Thank you for the help. -- T _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Mon Feb 25 18:28:33 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 25 Feb 2013 18:28: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 1UA2lu-0001yu-2N; Mon, 25 Feb 2013 18:27:30 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UA2ls-0001ya-1J; Mon, 25 Feb 2013 18:27:28 +0000 Received: from [193.109.254.147:52115] by server-2.bemta-14.messagelabs.com id 52/E3-16277-F0DAB215; Mon, 25 Feb 2013 18:27:27 +0000 X-Env-Sender: grantmasterflash@gmail.com X-Msg-Ref: server-11.tower-27.messagelabs.com!1361816845!2846180!1 X-Originating-IP: [209.85.215.41] X-SpamReason: No, hits=0.4 required=7.0 tests=HTML_30_40,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14, ML_RADAR_SPEW_LINKS_23, RCVD_BY_IP, spamassassin: X-StarScan-Received: X-StarScan-Version: 6.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 32314 invoked from network); 25 Feb 2013 18:27:25 -0000 Received: from mail-la0-f41.google.com (HELO mail-la0-f41.google.com) (209.85.215.41) by server-11.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 25 Feb 2013 18:27:25 -0000 Received: by mail-la0-f41.google.com with SMTP id fo12so3016878lab.28 for ; Mon, 25 Feb 2013 10:27:25 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:mime-version:in-reply-to:references:from:date:message-id :subject:to:cc:content-type; bh=0/KKQuwkSTDaMUCbXz960Iev6E33gHckPTNTDE56nOw=; b=Qc0ewAPBBcUY4Ed6BEWzcZL5JkaSfKgJTF1WhMQKBapXR2Z5COYZXii9eNlEXjNq/6 xFkRviaNJvvrU5ErL4LzAgyXLSnnaJd9Kx92/CkZQPC0a5L4wQodaVFjpCmrrmY3DO5q U+jsraiPbv4GykVlxY6kGqlS3CP9/DTpa4lNnD+i+R8Q+MC6bET53cFggo68IBHoTXtx Xhjfg/BTQg8Bo10DL/WAycmsEK+mVZtvW5lf4zQ0o9N5bobliorluSPtaL8jflJhq8PW iiiMAc6SI0qoL4yP0/s2bCesrUvfIiO9Li8jVAoV2nt+9ULuvF2jfzRMdXKMgyezv/Cn TTIg== X-Received: by 10.152.125.239 with SMTP id mt15mr10803714lab.26.1361816844947; Mon, 25 Feb 2013 10:27:24 -0800 (PST) MIME-Version: 1.0 Received: by 10.114.22.198 with HTTP; Mon, 25 Feb 2013 10:26:43 -0800 (PST) In-Reply-To: <1361786229.2109.15.camel@zion.uk.xensource.com> References: <1361786229.2109.15.camel@zion.uk.xensource.com> From: Grant McWilliams Date: Mon, 25 Feb 2013 10:26:43 -0800 Message-ID: To: Wei Liu Cc: xen-arm , "xen-users@lists.xen.org" , xen-api@lists.xen.org, Lars Kurth , xen-devel@lists.xen.org Subject: Re: [Xen-users] Xen Documentation Day: Feb 25th X-BeenThere: xen-users@lists.xen.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="===============8671470412639322294==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============8671470412639322294== Content-Type: multipart/alternative; boundary=f46d04426b664ad30904d690b195 --f46d04426b664ad30904d690b195 Content-Type: text/plain; charset=UTF-8 On Mon, Feb 25, 2013 at 1:57 AM, Wei Liu wrote: > Hi all > > Just a quick reminder that today is Xen documentation day! Join us on > freenode #xendocs to improve Xen documentation! > > ********************* > * 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! > > > Wei. > We have two Xen Document Days one week apart? Grant McWilliams http://grantmcwilliams.com/ Some people, when confronted with a problem, think "I know, I'll use Windows." Now they have two problems. --f46d04426b664ad30904d690b195 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On Mon, Feb 25, 2013 at 1:57 AM, Wei Liu <wei.liu2@citrix.com> wrote:
Hi all

Just a quick reminder that today is Xen documentation day! Join us on
freenode #xendocs to improve Xen documentation!

*********************
* 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 cour= se,
you can work on anything you like: the list just provides suggestions.

How do I participate?
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

- Join us on IRC: freenode channel #xendocs
- Tell people what you intend to work on (to avoid doing something
=C2=A0 somebody else is already working on)
- Fix some documentation
- Help others
- And above all: have fun!


Wei.

We have two Xen Document Days one = week apart?


Grant McWilliams
http://grantmcwilliams.com/

Some people, when confronted with a problem, think "I know, I'= ll use Windows."=C2=A0
Now they have two problems.
= =C2=A0
--f46d04426b664ad30904d690b195-- --===============8671470412639322294== 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 --===============8671470412639322294==-- From xen-users-bounces@lists.xen.org Mon Feb 25 18:28:33 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 25 Feb 2013 18:28: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 1UA2lu-0001yu-2N; Mon, 25 Feb 2013 18:27:30 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UA2ls-0001ya-1J; Mon, 25 Feb 2013 18:27:28 +0000 Received: from [193.109.254.147:52115] by server-2.bemta-14.messagelabs.com id 52/E3-16277-F0DAB215; Mon, 25 Feb 2013 18:27:27 +0000 X-Env-Sender: grantmasterflash@gmail.com X-Msg-Ref: server-11.tower-27.messagelabs.com!1361816845!2846180!1 X-Originating-IP: [209.85.215.41] X-SpamReason: No, hits=0.4 required=7.0 tests=HTML_30_40,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14, ML_RADAR_SPEW_LINKS_23, RCVD_BY_IP, spamassassin: X-StarScan-Received: X-StarScan-Version: 6.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 32314 invoked from network); 25 Feb 2013 18:27:25 -0000 Received: from mail-la0-f41.google.com (HELO mail-la0-f41.google.com) (209.85.215.41) by server-11.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 25 Feb 2013 18:27:25 -0000 Received: by mail-la0-f41.google.com with SMTP id fo12so3016878lab.28 for ; Mon, 25 Feb 2013 10:27:25 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:mime-version:in-reply-to:references:from:date:message-id :subject:to:cc:content-type; bh=0/KKQuwkSTDaMUCbXz960Iev6E33gHckPTNTDE56nOw=; b=Qc0ewAPBBcUY4Ed6BEWzcZL5JkaSfKgJTF1WhMQKBapXR2Z5COYZXii9eNlEXjNq/6 xFkRviaNJvvrU5ErL4LzAgyXLSnnaJd9Kx92/CkZQPC0a5L4wQodaVFjpCmrrmY3DO5q U+jsraiPbv4GykVlxY6kGqlS3CP9/DTpa4lNnD+i+R8Q+MC6bET53cFggo68IBHoTXtx Xhjfg/BTQg8Bo10DL/WAycmsEK+mVZtvW5lf4zQ0o9N5bobliorluSPtaL8jflJhq8PW iiiMAc6SI0qoL4yP0/s2bCesrUvfIiO9Li8jVAoV2nt+9ULuvF2jfzRMdXKMgyezv/Cn TTIg== X-Received: by 10.152.125.239 with SMTP id mt15mr10803714lab.26.1361816844947; Mon, 25 Feb 2013 10:27:24 -0800 (PST) MIME-Version: 1.0 Received: by 10.114.22.198 with HTTP; Mon, 25 Feb 2013 10:26:43 -0800 (PST) In-Reply-To: <1361786229.2109.15.camel@zion.uk.xensource.com> References: <1361786229.2109.15.camel@zion.uk.xensource.com> From: Grant McWilliams Date: Mon, 25 Feb 2013 10:26:43 -0800 Message-ID: To: Wei Liu Cc: xen-arm , "xen-users@lists.xen.org" , xen-api@lists.xen.org, Lars Kurth , xen-devel@lists.xen.org Subject: Re: [Xen-users] Xen Documentation Day: Feb 25th X-BeenThere: xen-users@lists.xen.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="===============8671470412639322294==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============8671470412639322294== Content-Type: multipart/alternative; boundary=f46d04426b664ad30904d690b195 --f46d04426b664ad30904d690b195 Content-Type: text/plain; charset=UTF-8 On Mon, Feb 25, 2013 at 1:57 AM, Wei Liu wrote: > Hi all > > Just a quick reminder that today is Xen documentation day! Join us on > freenode #xendocs to improve Xen documentation! > > ********************* > * 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! > > > Wei. > We have two Xen Document Days one week apart? Grant McWilliams http://grantmcwilliams.com/ Some people, when confronted with a problem, think "I know, I'll use Windows." Now they have two problems. --f46d04426b664ad30904d690b195 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On Mon, Feb 25, 2013 at 1:57 AM, Wei Liu <wei.liu2@citrix.com> wrote:
Hi all

Just a quick reminder that today is Xen documentation day! Join us on
freenode #xendocs to improve Xen documentation!

*********************
* 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 cour= se,
you can work on anything you like: the list just provides suggestions.

How do I participate?
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

- Join us on IRC: freenode channel #xendocs
- Tell people what you intend to work on (to avoid doing something
=C2=A0 somebody else is already working on)
- Fix some documentation
- Help others
- And above all: have fun!


Wei.

We have two Xen Document Days one = week apart?


Grant McWilliams
http://grantmcwilliams.com/

Some people, when confronted with a problem, think "I know, I'= ll use Windows."=C2=A0
Now they have two problems.
= =C2=A0
--f46d04426b664ad30904d690b195-- --===============8671470412639322294== 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 --===============8671470412639322294==-- From xen-users-bounces@lists.xen.org Mon Feb 25 18:32:37 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 25 Feb 2013 18:32: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 1UA2px-0002Ry-Sa; Mon, 25 Feb 2013 18:31:41 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UA2pv-0002RJ-FY; Mon, 25 Feb 2013 18:31:39 +0000 Received: from [85.158.138.51:50512] by server-13.bemta-3.messagelabs.com id 79/AA-20653-A0EAB215; Mon, 25 Feb 2013 18:31:38 +0000 X-Env-Sender: wei.liu2@citrix.com X-Msg-Ref: server-10.tower-174.messagelabs.com!1361817095!23716840!1 X-Originating-IP: [66.165.176.63] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjYuMTY1LjE3Ni42MyA9PiAzMDM5NzE=\n X-StarScan-Received: X-StarScan-Version: 6.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 28695 invoked from network); 25 Feb 2013 18:31:37 -0000 Received: from smtp02.citrix.com (HELO SMTP02.CITRIX.COM) (66.165.176.63) by server-10.tower-174.messagelabs.com with RC4-SHA encrypted SMTP; 25 Feb 2013 18:31:37 -0000 X-IronPort-AV: E=Sophos;i="4.84,736,1355097600"; d="scan'208";a="8990160" Received: from accessns.citrite.net (HELO FTLPEX01CL03.citrite.net) ([10.9.154.239]) by FTLPIPO02.CITRIX.COM with ESMTP/TLS/AES128-SHA; 25 Feb 2013 18:31:35 +0000 Received: from ukmail1.uk.xensource.com (10.80.16.128) by smtprelay.citrix.com (10.13.107.80) with Microsoft SMTP Server id 14.2.318.1; Mon, 25 Feb 2013 13:31:34 -0500 Received: from zion.uk.xensource.com ([10.80.2.73]) by ukmail1.uk.xensource.com with esmtp (Exim 4.69) (envelope-from ) id 1UA2pq-0004SX-Qh; Mon, 25 Feb 2013 18:31:34 +0000 Message-ID: <1361817094.2109.36.camel@zion.uk.xensource.com> From: Wei Liu To: Grant McWilliams Date: Mon, 25 Feb 2013 18:31:34 +0000 In-Reply-To: References: <1361786229.2109.15.camel@zion.uk.xensource.com> X-Mailer: Evolution 3.6.3 (3.6.3-2.fc18) MIME-Version: 1.0 Cc: Lars Kurth , wei.liu2@citrix.com, "xen-devel@lists.xen.org" , "xen-users@lists.xen.org" , xen-arm , "xen-api@lists.xen.org" Subject: Re: [Xen-users] Xen Documentation Day: Feb 25th X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: 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, 2013-02-25 at 18:26 +0000, Grant McWilliams wrote: > > We have two Xen Document Days one week apart? No. We remind people of the Xen Docsday one week before. And we also send another email when it is happening. :-) Regards Wei. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Mon Feb 25 18:32:37 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 25 Feb 2013 18:32: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 1UA2px-0002Ry-Sa; Mon, 25 Feb 2013 18:31:41 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UA2pv-0002RJ-FY; Mon, 25 Feb 2013 18:31:39 +0000 Received: from [85.158.138.51:50512] by server-13.bemta-3.messagelabs.com id 79/AA-20653-A0EAB215; Mon, 25 Feb 2013 18:31:38 +0000 X-Env-Sender: wei.liu2@citrix.com X-Msg-Ref: server-10.tower-174.messagelabs.com!1361817095!23716840!1 X-Originating-IP: [66.165.176.63] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjYuMTY1LjE3Ni42MyA9PiAzMDM5NzE=\n X-StarScan-Received: X-StarScan-Version: 6.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 28695 invoked from network); 25 Feb 2013 18:31:37 -0000 Received: from smtp02.citrix.com (HELO SMTP02.CITRIX.COM) (66.165.176.63) by server-10.tower-174.messagelabs.com with RC4-SHA encrypted SMTP; 25 Feb 2013 18:31:37 -0000 X-IronPort-AV: E=Sophos;i="4.84,736,1355097600"; d="scan'208";a="8990160" Received: from accessns.citrite.net (HELO FTLPEX01CL03.citrite.net) ([10.9.154.239]) by FTLPIPO02.CITRIX.COM with ESMTP/TLS/AES128-SHA; 25 Feb 2013 18:31:35 +0000 Received: from ukmail1.uk.xensource.com (10.80.16.128) by smtprelay.citrix.com (10.13.107.80) with Microsoft SMTP Server id 14.2.318.1; Mon, 25 Feb 2013 13:31:34 -0500 Received: from zion.uk.xensource.com ([10.80.2.73]) by ukmail1.uk.xensource.com with esmtp (Exim 4.69) (envelope-from ) id 1UA2pq-0004SX-Qh; Mon, 25 Feb 2013 18:31:34 +0000 Message-ID: <1361817094.2109.36.camel@zion.uk.xensource.com> From: Wei Liu To: Grant McWilliams Date: Mon, 25 Feb 2013 18:31:34 +0000 In-Reply-To: References: <1361786229.2109.15.camel@zion.uk.xensource.com> X-Mailer: Evolution 3.6.3 (3.6.3-2.fc18) MIME-Version: 1.0 Cc: Lars Kurth , wei.liu2@citrix.com, "xen-devel@lists.xen.org" , "xen-users@lists.xen.org" , xen-arm , "xen-api@lists.xen.org" Subject: Re: [Xen-users] Xen Documentation Day: Feb 25th X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: 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, 2013-02-25 at 18:26 +0000, Grant McWilliams wrote: > > We have two Xen Document Days one week apart? No. We remind people of the Xen Docsday one week before. And we also send another email when it is happening. :-) Regards Wei. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Mon Feb 25 18:43:12 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 25 Feb 2013 18: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 1UA30M-0003RX-Mr; Mon, 25 Feb 2013 18:42:26 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UA30L-0003RP-CB for xen-users@lists.xen.org; Mon, 25 Feb 2013 18:42:25 +0000 Received: from [85.158.139.211:3405] by server-10.bemta-5.messagelabs.com id 56/44-23714-090BB215; Mon, 25 Feb 2013 18:42:24 +0000 X-Env-Sender: ecosoft13@gmail.com X-Msg-Ref: server-2.tower-206.messagelabs.com!1361817702!19196314!1 X-Originating-IP: [209.85.220.196] 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.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 20039 invoked from network); 25 Feb 2013 18:42:23 -0000 Received: from mail-vc0-f196.google.com (HELO mail-vc0-f196.google.com) (209.85.220.196) by server-2.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 25 Feb 2013 18:42:23 -0000 Received: by mail-vc0-f196.google.com with SMTP id fy7so43435vcb.7 for ; Mon, 25 Feb 2013 10:41:23 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:date:message-id:subject:from:to :content-type; bh=ygfrAeF/icuy+Gek0+sGOEqNyQqvBK8nKzEFY673wfg=; b=D6v3dTgpYH0zxb/j8qfYAH+eSl288gdzaG6wiHjUXygIbdPQGvlJ/aXytLLvbLjZHK q9UtEVyFUQU8IiBNSisJNWgzG9ggw9QEpAL1olDgHhxNz2aHvuHpZt/7cvfKkgOfVo4h 6FsoPLA0jJE7e1pcduYvvbw4S6wLN+oqoW9yAM3Ct8DdsVHcyKTCUMEpVM5lRUel4rfS tCzQnWduKpsrWnFnTiJb4Wi52E7nvzyE/+E5DfW2xjMjSzktl009iUluS3hbSPeqq8fX bvWrlZ36n8aIvCb6NsFdKvBZBHGDGuTkFJqS/szk8QRD2WSFgwj+CTYbR3VS+FCZnvhb 4w0g== MIME-Version: 1.0 X-Received: by 10.58.45.168 with SMTP id o8mr7227941vem.3.1361817683046; Mon, 25 Feb 2013 10:41:23 -0800 (PST) Received: by 10.221.13.194 with HTTP; Mon, 25 Feb 2013 10:41:22 -0800 (PST) Date: Mon, 25 Feb 2013 12:41:22 -0600 Message-ID: From: Yaodong Yang To: xen-users@lists.xen.org Subject: [Xen-users] Xen Domain U can not install (on Ubuntu.) X-BeenThere: xen-users@lists.xen.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="===============1596669217726953793==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============1596669217726953793== Content-Type: multipart/alternative; boundary=089e01182a583f67b904d690e3bd --089e01182a583f67b904d690e3bd Content-Type: text/plain; charset=ISO-8859-1 Hi everyone, I'm a phd student and I'm doing research in vm field. I'm sorry that I met a problem with domain U install. I followed the instruction from the Xen-Ubuntu page: https://help.ubuntu.com/community/Xen. When I was installing the domain U (also a Ubuntu image), I was told the dhcp does not work. If I choose not to configure dhcp, then I was asked to choose a mirror. But in fact, I already download the image in disk. I donot know how to fix it. Could anyone give me some suggestion? I appreciate it very much! yaodong --089e01182a583f67b904d690e3bd Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Hi everyone,

I'm a phd studen= t and I'm doing research in vm field.

I'm sorry that I met a problem with domain U install. I followed th= e instruction from the Xen-Ubuntu page:

When = I was installing the domain U (also a Ubuntu image), I was told the dhcp do= es not work. If I choose not to configure dhcp, then I was asked to choose = a mirror. But in fact, I already download the image in disk. I donot know h= ow to fix it.

Could anyone give me some suggestion? I app= reciate it very much!

yaodong
--089e01182a583f67b904d690e3bd-- --===============1596669217726953793== 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 --===============1596669217726953793==-- From xen-users-bounces@lists.xen.org Mon Feb 25 18:43:12 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 25 Feb 2013 18: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 1UA30M-0003RX-Mr; Mon, 25 Feb 2013 18:42:26 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UA30L-0003RP-CB for xen-users@lists.xen.org; Mon, 25 Feb 2013 18:42:25 +0000 Received: from [85.158.139.211:3405] by server-10.bemta-5.messagelabs.com id 56/44-23714-090BB215; Mon, 25 Feb 2013 18:42:24 +0000 X-Env-Sender: ecosoft13@gmail.com X-Msg-Ref: server-2.tower-206.messagelabs.com!1361817702!19196314!1 X-Originating-IP: [209.85.220.196] 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.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 20039 invoked from network); 25 Feb 2013 18:42:23 -0000 Received: from mail-vc0-f196.google.com (HELO mail-vc0-f196.google.com) (209.85.220.196) by server-2.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 25 Feb 2013 18:42:23 -0000 Received: by mail-vc0-f196.google.com with SMTP id fy7so43435vcb.7 for ; Mon, 25 Feb 2013 10:41:23 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:date:message-id:subject:from:to :content-type; bh=ygfrAeF/icuy+Gek0+sGOEqNyQqvBK8nKzEFY673wfg=; b=D6v3dTgpYH0zxb/j8qfYAH+eSl288gdzaG6wiHjUXygIbdPQGvlJ/aXytLLvbLjZHK q9UtEVyFUQU8IiBNSisJNWgzG9ggw9QEpAL1olDgHhxNz2aHvuHpZt/7cvfKkgOfVo4h 6FsoPLA0jJE7e1pcduYvvbw4S6wLN+oqoW9yAM3Ct8DdsVHcyKTCUMEpVM5lRUel4rfS tCzQnWduKpsrWnFnTiJb4Wi52E7nvzyE/+E5DfW2xjMjSzktl009iUluS3hbSPeqq8fX bvWrlZ36n8aIvCb6NsFdKvBZBHGDGuTkFJqS/szk8QRD2WSFgwj+CTYbR3VS+FCZnvhb 4w0g== MIME-Version: 1.0 X-Received: by 10.58.45.168 with SMTP id o8mr7227941vem.3.1361817683046; Mon, 25 Feb 2013 10:41:23 -0800 (PST) Received: by 10.221.13.194 with HTTP; Mon, 25 Feb 2013 10:41:22 -0800 (PST) Date: Mon, 25 Feb 2013 12:41:22 -0600 Message-ID: From: Yaodong Yang To: xen-users@lists.xen.org Subject: [Xen-users] Xen Domain U can not install (on Ubuntu.) X-BeenThere: xen-users@lists.xen.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="===============1596669217726953793==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============1596669217726953793== Content-Type: multipart/alternative; boundary=089e01182a583f67b904d690e3bd --089e01182a583f67b904d690e3bd Content-Type: text/plain; charset=ISO-8859-1 Hi everyone, I'm a phd student and I'm doing research in vm field. I'm sorry that I met a problem with domain U install. I followed the instruction from the Xen-Ubuntu page: https://help.ubuntu.com/community/Xen. When I was installing the domain U (also a Ubuntu image), I was told the dhcp does not work. If I choose not to configure dhcp, then I was asked to choose a mirror. But in fact, I already download the image in disk. I donot know how to fix it. Could anyone give me some suggestion? I appreciate it very much! yaodong --089e01182a583f67b904d690e3bd Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Hi everyone,

I'm a phd studen= t and I'm doing research in vm field.

I'm sorry that I met a problem with domain U install. I followed th= e instruction from the Xen-Ubuntu page:

When = I was installing the domain U (also a Ubuntu image), I was told the dhcp do= es not work. If I choose not to configure dhcp, then I was asked to choose = a mirror. But in fact, I already download the image in disk. I donot know h= ow to fix it.

Could anyone give me some suggestion? I app= reciate it very much!

yaodong
--089e01182a583f67b904d690e3bd-- --===============1596669217726953793== 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 --===============1596669217726953793==-- From xen-users-bounces@lists.xen.org Mon Feb 25 22:49:42 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 25 Feb 2013 22:49: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 1UA6q4-0003el-1T; Mon, 25 Feb 2013 22:48:04 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UA6q2-0003eg-HP for xen-users@lists.xen.org; Mon, 25 Feb 2013 22:48:02 +0000 Received: from [85.158.137.99:61216] by server-5.bemta-3.messagelabs.com id 99/BB-04457-12AEB215; Mon, 25 Feb 2013 22:48:01 +0000 X-Env-Sender: tosterman@gmail.com X-Msg-Ref: server-7.tower-217.messagelabs.com!1361832477!12910361!1 X-Originating-IP: [209.85.223.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.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 8481 invoked from network); 25 Feb 2013 22:47:58 -0000 Received: from mail-ie0-f173.google.com (HELO mail-ie0-f173.google.com) (209.85.223.173) by server-7.tower-217.messagelabs.com with RC4-SHA encrypted SMTP; 25 Feb 2013 22:47:58 -0000 Received: by mail-ie0-f173.google.com with SMTP id 9so3785197iec.32 for ; Mon, 25 Feb 2013 14:47:57 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:reply-to:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=jOc1xG4j7N3DigT7y0xj/tNXLAeqG0mnIGXIwaY5NfI=; b=zzAmtoKngjIm7EqHJaXs0hmRSvyFfxdFWF8JqJ7HI8p/CdrcfNiHqzFxqcWdaOiDKC 9FyUrhmmskOUmw3IIwEcktY4I60JVSD4NsOBc70C5cvuJr3de6TSYXMKJE3EyvL9GRIP DLwMU2z3Ly4qJa1h3ym2sHH6roLwA5wmMRrSpLecf+QFSSefmSxYDjXrj+M0qxRlFl1y UVH/vLHX+j6WfUba5vrANjbTYie8t5AnSpEGG8JYd96Dr4y7tfFRDxWK5p9qcv5xteUm 3wE0M9i4ZcSHynTSHQ5bDG3Ojt2ADUrFuYrTs+jamJf4FtTmQ1falGTynDIANZglr4Ze zdtQ== MIME-Version: 1.0 X-Received: by 10.50.170.36 with SMTP id aj4mr4213846igc.67.1361832476884; Mon, 25 Feb 2013 14:47:56 -0800 (PST) Received: by 10.64.60.136 with HTTP; Mon, 25 Feb 2013 14:47:56 -0800 (PST) In-Reply-To: References: <1361784654.26546.165.camel@zakaz.uk.xensource.com> <1361805642.26546.184.camel@zakaz.uk.xensource.com> Date: Mon, 25 Feb 2013 17:47:56 -0500 Message-ID: From: Travis Osterman To: xen-users Cc: Ian Campbell Subject: Re: [Xen-users] pv guest fails to start after 4.2 upgrade X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: travis@wsor.net List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: 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 also tried to take pvgrub out of the picture so I mounted the image >>> >> and copied my initrd and kernel to the dom0 file system and updated my >>> >> config with the appropriate ramdisk and kernel lines. >>> >> >>> >> Full output without pvgrub >>> >> http://pastebin.com/c7VWWwXk >>> >> >>> >> Which dropped me in a shell asking for my root partition (progress). >>> >>> # cat /var/log/xen/qemu-dm-prime.log >>> bind(unix:/var/run/xen/qmp-libxl-4): No such file or directory >>> chardev: opening backend "socket" failed: No such file or directory >>> >>> # ls /var/run/xen* >>> /var/run/xenconsoled.pid /var/run/xenstored.pid >>> >>> /var/run/xenstored: >>> socket socket_ro >> >> Ah, you are missing the /var/run/xen/ directory so it is failing to >> create the socket, if you create the directory does it work? Although >> even if so it is obviously still a bug that libxl doesn't handle that >> error... > > Ian, > > I can confirm the manually creating /var/run/xen fixes the problem. I > updated my bug report here > https://bugs.gentoo.org/show_bug.cgi?id=459082 > > Thank you for the help. > Similar error not solved by the above on a domain using pygrub (pvgrub works) /var/log/xen/qemu-dm-domain.log /var/tmp/portage/app-emulation/xen-tools-4.1.1-r6/work/xen-4.1.1/tools/ioemu-qemu-xen/hw/xen_blktap. c:628: Init blktap pipes Could not open /var/run/tap/qemu-read-2 Again loop device works fine. -- T _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Mon Feb 25 22:49:42 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 25 Feb 2013 22:49: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 1UA6q4-0003el-1T; Mon, 25 Feb 2013 22:48:04 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UA6q2-0003eg-HP for xen-users@lists.xen.org; Mon, 25 Feb 2013 22:48:02 +0000 Received: from [85.158.137.99:61216] by server-5.bemta-3.messagelabs.com id 99/BB-04457-12AEB215; Mon, 25 Feb 2013 22:48:01 +0000 X-Env-Sender: tosterman@gmail.com X-Msg-Ref: server-7.tower-217.messagelabs.com!1361832477!12910361!1 X-Originating-IP: [209.85.223.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.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 8481 invoked from network); 25 Feb 2013 22:47:58 -0000 Received: from mail-ie0-f173.google.com (HELO mail-ie0-f173.google.com) (209.85.223.173) by server-7.tower-217.messagelabs.com with RC4-SHA encrypted SMTP; 25 Feb 2013 22:47:58 -0000 Received: by mail-ie0-f173.google.com with SMTP id 9so3785197iec.32 for ; Mon, 25 Feb 2013 14:47:57 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:reply-to:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=jOc1xG4j7N3DigT7y0xj/tNXLAeqG0mnIGXIwaY5NfI=; b=zzAmtoKngjIm7EqHJaXs0hmRSvyFfxdFWF8JqJ7HI8p/CdrcfNiHqzFxqcWdaOiDKC 9FyUrhmmskOUmw3IIwEcktY4I60JVSD4NsOBc70C5cvuJr3de6TSYXMKJE3EyvL9GRIP DLwMU2z3Ly4qJa1h3ym2sHH6roLwA5wmMRrSpLecf+QFSSefmSxYDjXrj+M0qxRlFl1y UVH/vLHX+j6WfUba5vrANjbTYie8t5AnSpEGG8JYd96Dr4y7tfFRDxWK5p9qcv5xteUm 3wE0M9i4ZcSHynTSHQ5bDG3Ojt2ADUrFuYrTs+jamJf4FtTmQ1falGTynDIANZglr4Ze zdtQ== MIME-Version: 1.0 X-Received: by 10.50.170.36 with SMTP id aj4mr4213846igc.67.1361832476884; Mon, 25 Feb 2013 14:47:56 -0800 (PST) Received: by 10.64.60.136 with HTTP; Mon, 25 Feb 2013 14:47:56 -0800 (PST) In-Reply-To: References: <1361784654.26546.165.camel@zakaz.uk.xensource.com> <1361805642.26546.184.camel@zakaz.uk.xensource.com> Date: Mon, 25 Feb 2013 17:47:56 -0500 Message-ID: From: Travis Osterman To: xen-users Cc: Ian Campbell Subject: Re: [Xen-users] pv guest fails to start after 4.2 upgrade X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: travis@wsor.net List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: 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 also tried to take pvgrub out of the picture so I mounted the image >>> >> and copied my initrd and kernel to the dom0 file system and updated my >>> >> config with the appropriate ramdisk and kernel lines. >>> >> >>> >> Full output without pvgrub >>> >> http://pastebin.com/c7VWWwXk >>> >> >>> >> Which dropped me in a shell asking for my root partition (progress). >>> >>> # cat /var/log/xen/qemu-dm-prime.log >>> bind(unix:/var/run/xen/qmp-libxl-4): No such file or directory >>> chardev: opening backend "socket" failed: No such file or directory >>> >>> # ls /var/run/xen* >>> /var/run/xenconsoled.pid /var/run/xenstored.pid >>> >>> /var/run/xenstored: >>> socket socket_ro >> >> Ah, you are missing the /var/run/xen/ directory so it is failing to >> create the socket, if you create the directory does it work? Although >> even if so it is obviously still a bug that libxl doesn't handle that >> error... > > Ian, > > I can confirm the manually creating /var/run/xen fixes the problem. I > updated my bug report here > https://bugs.gentoo.org/show_bug.cgi?id=459082 > > Thank you for the help. > Similar error not solved by the above on a domain using pygrub (pvgrub works) /var/log/xen/qemu-dm-domain.log /var/tmp/portage/app-emulation/xen-tools-4.1.1-r6/work/xen-4.1.1/tools/ioemu-qemu-xen/hw/xen_blktap. c:628: Init blktap pipes Could not open /var/run/tap/qemu-read-2 Again loop device works fine. -- T _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Tue Feb 26 04:19:25 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 26 Feb 2013 04:19: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 1UABzL-0000Qw-VD; Tue, 26 Feb 2013 04:17:59 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UABzJ-0000Qj-Ta; Tue, 26 Feb 2013 04:17:58 +0000 Received: from [85.158.137.99:44315] by server-3.bemta-3.messagelabs.com id E4/F2-31070-4773C215; Tue, 26 Feb 2013 04:17:56 +0000 X-Env-Sender: gizmochicken@gmail.com X-Msg-Ref: server-5.tower-217.messagelabs.com!1361852274!13330296!1 X-Originating-IP: [209.85.128.49] 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.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 17718 invoked from network); 26 Feb 2013 04:17:56 -0000 Received: from mail-qe0-f49.google.com (HELO mail-qe0-f49.google.com) (209.85.128.49) by server-5.tower-217.messagelabs.com with RC4-SHA encrypted SMTP; 26 Feb 2013 04:17:56 -0000 Received: by mail-qe0-f49.google.com with SMTP id 1so337378qec.36 for ; Mon, 25 Feb 2013 20:17:54 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:date:message-id:subject:from:to :content-type; bh=9dnfvv3NPCtZINeuHgBjCkm873sAbxI8h1bjsYx9mKo=; b=NFLnFl7vGlZ88Ug51kSqn7B69NqpaOXDTPbXbU/GBNYr97oVejUlT77YqGVAOjja05 BAlUFvkrKudX0e76U9GJxorWq7i/tXvf6dmuf1WaOoISCPr5wFSLV4FKR4wDNQFWWfkN AAdFH6mfGNDeaoD5ZNXnt0UjK0fabEaAuP8OheNt+CUiXYUnuc13IjPm5TxaIfkYUzsZ XizW9vxpXaUnnwqH6VCIqTG8W+ytppRyZzH5KMh+pCHtJXbj96KKIzy9bOBEsdNGTqUN kXKAP+GjydvzAt9GNZamoVkVrbhvhSkvpuwq5okRH8/Rka8tRxYUEicUCB33+I/W+cFy ftfw== MIME-Version: 1.0 X-Received: by 10.49.24.135 with SMTP id u7mr17773916qef.4.1361852274687; Mon, 25 Feb 2013 20:17:54 -0800 (PST) Received: by 10.49.104.166 with HTTP; Mon, 25 Feb 2013 20:17:54 -0800 (PST) Date: Mon, 25 Feb 2013 23:17:54 -0500 Message-ID: From: Gizmo Chicken To: xen-api@lists.xen.org, xen-users@lists.xen.org Subject: [Xen-users] XCP 1.6: GPU passthrough with Ubuntu 12.10 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: , Content-Type: multipart/mixed; boundary="===============1213431565577920918==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============1213431565577920918== Content-Type: multipart/alternative; boundary=047d7b6dc3bc11c60a04d698f101 --047d7b6dc3bc11c60a04d698f101 Content-Type: text/plain; charset=ISO-8859-1 I have a Radeon HD 6670 GPU and an IOMMU enabled motherboard. With that GPU and motherboard, I had absolutely no trouble getting GPU passthrough to work with XCP 1.6 and a Windows 7 guest. It just worked! And after some trial and error (mostly error), I was able to get GPU passthrough working with XCP 1.6 and an Ubuntu 12.04 HVM guest. But with Ubuntu 12.10 and 13.04 HVM guests, I have had absolutely no luck at all in getting GPU passthrough to work. Has anyone out there had any luck getting GPU passthrough to work with a Radeon GPU and an Ubuntu 12.10 (or 13.04) HVM guest? If you've had any luck getting GPU passthrough to work with a Radeon GPU and an Ubuntu 12.10 (or 13.04) HVM guest, would you please provide a few tips, such as what driver was used and what edits, if any, were made to any relevant guest configuration files? Thanks in advance for any help provided. Best regards, GizmoChicken --047d7b6dc3bc11c60a04d698f101 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable I have a Radeon HD 6670 GPU and an IOMMU enabled motherboard.=A0 With that = GPU and motherboard, I had absolutely no trouble getting GPU passthrough to= work with XCP 1.6 and a Windows 7 guest. It just worked!=A0 And after some= trial and error (mostly error), I was able to get GPU passthrough working = with XCP 1.6 and an Ubuntu 12.04 HVM guest.=A0

But with Ubuntu 12.10 and 13.04 HVM guests, I have had absolutely no lu= ck at all in getting GPU passthrough to work.

Has anyone out there h= ad any luck getting GPU passthrough to work with a Radeon GPU and an Ubuntu= 12.10 (or 13.04) HVM guest?

If you've had any luck getting GPU passthrough to work with a Radeo= n GPU and an Ubuntu 12.10 (or 13.04) HVM guest, would you please provide a = few tips, such as what driver was used and what edits, if any, were made to= any relevant guest configuration files?

Thanks in advance for any help provided.

Best regards,
GizmoC= hicken

--047d7b6dc3bc11c60a04d698f101-- --===============1213431565577920918== 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 --===============1213431565577920918==-- From xen-users-bounces@lists.xen.org Tue Feb 26 04:19:25 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 26 Feb 2013 04:19: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 1UABzL-0000Qw-VD; Tue, 26 Feb 2013 04:17:59 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UABzJ-0000Qj-Ta; Tue, 26 Feb 2013 04:17:58 +0000 Received: from [85.158.137.99:44315] by server-3.bemta-3.messagelabs.com id E4/F2-31070-4773C215; Tue, 26 Feb 2013 04:17:56 +0000 X-Env-Sender: gizmochicken@gmail.com X-Msg-Ref: server-5.tower-217.messagelabs.com!1361852274!13330296!1 X-Originating-IP: [209.85.128.49] 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.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 17718 invoked from network); 26 Feb 2013 04:17:56 -0000 Received: from mail-qe0-f49.google.com (HELO mail-qe0-f49.google.com) (209.85.128.49) by server-5.tower-217.messagelabs.com with RC4-SHA encrypted SMTP; 26 Feb 2013 04:17:56 -0000 Received: by mail-qe0-f49.google.com with SMTP id 1so337378qec.36 for ; Mon, 25 Feb 2013 20:17:54 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:date:message-id:subject:from:to :content-type; bh=9dnfvv3NPCtZINeuHgBjCkm873sAbxI8h1bjsYx9mKo=; b=NFLnFl7vGlZ88Ug51kSqn7B69NqpaOXDTPbXbU/GBNYr97oVejUlT77YqGVAOjja05 BAlUFvkrKudX0e76U9GJxorWq7i/tXvf6dmuf1WaOoISCPr5wFSLV4FKR4wDNQFWWfkN AAdFH6mfGNDeaoD5ZNXnt0UjK0fabEaAuP8OheNt+CUiXYUnuc13IjPm5TxaIfkYUzsZ XizW9vxpXaUnnwqH6VCIqTG8W+ytppRyZzH5KMh+pCHtJXbj96KKIzy9bOBEsdNGTqUN kXKAP+GjydvzAt9GNZamoVkVrbhvhSkvpuwq5okRH8/Rka8tRxYUEicUCB33+I/W+cFy ftfw== MIME-Version: 1.0 X-Received: by 10.49.24.135 with SMTP id u7mr17773916qef.4.1361852274687; Mon, 25 Feb 2013 20:17:54 -0800 (PST) Received: by 10.49.104.166 with HTTP; Mon, 25 Feb 2013 20:17:54 -0800 (PST) Date: Mon, 25 Feb 2013 23:17:54 -0500 Message-ID: From: Gizmo Chicken To: xen-api@lists.xen.org, xen-users@lists.xen.org Subject: [Xen-users] XCP 1.6: GPU passthrough with Ubuntu 12.10 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: , Content-Type: multipart/mixed; boundary="===============1213431565577920918==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============1213431565577920918== Content-Type: multipart/alternative; boundary=047d7b6dc3bc11c60a04d698f101 --047d7b6dc3bc11c60a04d698f101 Content-Type: text/plain; charset=ISO-8859-1 I have a Radeon HD 6670 GPU and an IOMMU enabled motherboard. With that GPU and motherboard, I had absolutely no trouble getting GPU passthrough to work with XCP 1.6 and a Windows 7 guest. It just worked! And after some trial and error (mostly error), I was able to get GPU passthrough working with XCP 1.6 and an Ubuntu 12.04 HVM guest. But with Ubuntu 12.10 and 13.04 HVM guests, I have had absolutely no luck at all in getting GPU passthrough to work. Has anyone out there had any luck getting GPU passthrough to work with a Radeon GPU and an Ubuntu 12.10 (or 13.04) HVM guest? If you've had any luck getting GPU passthrough to work with a Radeon GPU and an Ubuntu 12.10 (or 13.04) HVM guest, would you please provide a few tips, such as what driver was used and what edits, if any, were made to any relevant guest configuration files? Thanks in advance for any help provided. Best regards, GizmoChicken --047d7b6dc3bc11c60a04d698f101 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable I have a Radeon HD 6670 GPU and an IOMMU enabled motherboard.=A0 With that = GPU and motherboard, I had absolutely no trouble getting GPU passthrough to= work with XCP 1.6 and a Windows 7 guest. It just worked!=A0 And after some= trial and error (mostly error), I was able to get GPU passthrough working = with XCP 1.6 and an Ubuntu 12.04 HVM guest.=A0

But with Ubuntu 12.10 and 13.04 HVM guests, I have had absolutely no lu= ck at all in getting GPU passthrough to work.

Has anyone out there h= ad any luck getting GPU passthrough to work with a Radeon GPU and an Ubuntu= 12.10 (or 13.04) HVM guest?

If you've had any luck getting GPU passthrough to work with a Radeo= n GPU and an Ubuntu 12.10 (or 13.04) HVM guest, would you please provide a = few tips, such as what driver was used and what edits, if any, were made to= any relevant guest configuration files?

Thanks in advance for any help provided.

Best regards,
GizmoC= hicken

--047d7b6dc3bc11c60a04d698f101-- --===============1213431565577920918== 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 --===============1213431565577920918==-- From xen-users-bounces@lists.xen.org Tue Feb 26 06:47:13 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 26 Feb 2013 06:47: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 1UAEIC-00058R-Il; Tue, 26 Feb 2013 06:45:36 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UAEIB-000587-Hu; Tue, 26 Feb 2013 06:45:35 +0000 Received: from [85.158.139.83:43281] by server-10.bemta-5.messagelabs.com id 96/C1-23714-E0A5C215; Tue, 26 Feb 2013 06:45:34 +0000 X-Env-Sender: grantmasterflash@gmail.com X-Msg-Ref: server-6.tower-182.messagelabs.com!1361861132!25036484!1 X-Originating-IP: [209.85.215.44] 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.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 20161 invoked from network); 26 Feb 2013 06:45:33 -0000 Received: from mail-la0-f44.google.com (HELO mail-la0-f44.google.com) (209.85.215.44) by server-6.tower-182.messagelabs.com with RC4-SHA encrypted SMTP; 26 Feb 2013 06:45:33 -0000 Received: by mail-la0-f44.google.com with SMTP id eb20so3540543lab.3 for ; Mon, 25 Feb 2013 22:45:32 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:mime-version:in-reply-to:references:from:date:message-id :subject:to:cc:content-type; bh=HO+cRTB0vq8Tn2Fx/Qwxm5me0O3Ex2oqtahvvepFLvM=; b=LhB7wawzwvuYecekrKiGDg7WLAtw98HlyXC2mbbrMUG718jvjUfzP4Uah6z54zt/yt 13b9zIH0kw6WVOzJJcbvK86z6TYNTLeNs+mr3nMVc25DveuhqSIARksKXRq5z4uMVnz+ 01N0kiyFsYt03giKuSIvpgq5bSkuGJNiAAejDKlVCkebFh4Mxm6b2mQlV/VM/F6QIx2u TIbrR/8TxiXq0ty2da9EniSZAAIlpOLl3rnxkPPHR4hb7ctsaHrX7XOJUTelgWdS8JCv AF5+iEN8mMYV4vlPvbVGxHFfJQnLyPwx+/4iW2uvl9Q2ZrNhe5EhahIKZc1HrQNvBBUU 2e4Q== X-Received: by 10.152.108.1 with SMTP id hg1mr12250088lab.12.1361861132586; Mon, 25 Feb 2013 22:45:32 -0800 (PST) MIME-Version: 1.0 Received: by 10.114.22.198 with HTTP; Mon, 25 Feb 2013 22:44:52 -0800 (PST) In-Reply-To: <1361817094.2109.36.camel@zion.uk.xensource.com> References: <1361786229.2109.15.camel@zion.uk.xensource.com> <1361817094.2109.36.camel@zion.uk.xensource.com> From: Grant McWilliams Date: Mon, 25 Feb 2013 22:44:52 -0800 Message-ID: To: Wei Liu Cc: xen-arm , "xen-users@lists.xen.org" , "xen-api@lists.xen.org" , Lars Kurth , "xen-devel@lists.xen.org" Subject: Re: [Xen-users] Xen Documentation Day: Feb 25th X-BeenThere: xen-users@lists.xen.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="===============8620897407141534915==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============8620897407141534915== Content-Type: multipart/alternative; boundary=bcaec54ee2240a96e204d69b017d --bcaec54ee2240a96e204d69b017d Content-Type: text/plain; charset=UTF-8 On Mon, Feb 25, 2013 at 10:31 AM, Wei Liu wrote: > On Mon, 2013-02-25 at 18:26 +0000, Grant McWilliams wrote: > > > > We have two Xen Document Days one week apart? > > > No. We remind people of the Xen Docsday one week before. And we also > send another email when it is happening. :-) > > > Regards > Wei. > > > Oh, so it's the same message from a week ago? I'm not sure that was very clear by reading it. I missed it but it's not because of this, I was really busy writing documentation... ;-) Grant McWilliams --bcaec54ee2240a96e204d69b017d Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On Mon, Feb 25, 2013 at 10:31 AM, Wei Liu <wei.liu2@citrix.com> wrote:
On Mon, 2013-02-25 at 18:26 +0000, Grant McWilliams wrote= :
>
> We have two Xen Document Days one week apart?


No. We remind people of the Xen Docsday one week before. And we also<= br> send another email when it is happening. :-)


Regards
Wei.


Oh, so it's the same message from a we= ek ago? I'm not sure that was very clear by reading it.=C2=A0
I mis= sed it but it's not because of this, I was really busy writing document= ation... ;-)

Grant McWilliams
--bcaec54ee2240a96e204d69b017d-- --===============8620897407141534915== 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 --===============8620897407141534915==-- From xen-users-bounces@lists.xen.org Tue Feb 26 06:47:13 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 26 Feb 2013 06:47: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 1UAEIC-00058R-Il; Tue, 26 Feb 2013 06:45:36 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UAEIB-000587-Hu; Tue, 26 Feb 2013 06:45:35 +0000 Received: from [85.158.139.83:43281] by server-10.bemta-5.messagelabs.com id 96/C1-23714-E0A5C215; Tue, 26 Feb 2013 06:45:34 +0000 X-Env-Sender: grantmasterflash@gmail.com X-Msg-Ref: server-6.tower-182.messagelabs.com!1361861132!25036484!1 X-Originating-IP: [209.85.215.44] 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.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 20161 invoked from network); 26 Feb 2013 06:45:33 -0000 Received: from mail-la0-f44.google.com (HELO mail-la0-f44.google.com) (209.85.215.44) by server-6.tower-182.messagelabs.com with RC4-SHA encrypted SMTP; 26 Feb 2013 06:45:33 -0000 Received: by mail-la0-f44.google.com with SMTP id eb20so3540543lab.3 for ; Mon, 25 Feb 2013 22:45:32 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:mime-version:in-reply-to:references:from:date:message-id :subject:to:cc:content-type; bh=HO+cRTB0vq8Tn2Fx/Qwxm5me0O3Ex2oqtahvvepFLvM=; b=LhB7wawzwvuYecekrKiGDg7WLAtw98HlyXC2mbbrMUG718jvjUfzP4Uah6z54zt/yt 13b9zIH0kw6WVOzJJcbvK86z6TYNTLeNs+mr3nMVc25DveuhqSIARksKXRq5z4uMVnz+ 01N0kiyFsYt03giKuSIvpgq5bSkuGJNiAAejDKlVCkebFh4Mxm6b2mQlV/VM/F6QIx2u TIbrR/8TxiXq0ty2da9EniSZAAIlpOLl3rnxkPPHR4hb7ctsaHrX7XOJUTelgWdS8JCv AF5+iEN8mMYV4vlPvbVGxHFfJQnLyPwx+/4iW2uvl9Q2ZrNhe5EhahIKZc1HrQNvBBUU 2e4Q== X-Received: by 10.152.108.1 with SMTP id hg1mr12250088lab.12.1361861132586; Mon, 25 Feb 2013 22:45:32 -0800 (PST) MIME-Version: 1.0 Received: by 10.114.22.198 with HTTP; Mon, 25 Feb 2013 22:44:52 -0800 (PST) In-Reply-To: <1361817094.2109.36.camel@zion.uk.xensource.com> References: <1361786229.2109.15.camel@zion.uk.xensource.com> <1361817094.2109.36.camel@zion.uk.xensource.com> From: Grant McWilliams Date: Mon, 25 Feb 2013 22:44:52 -0800 Message-ID: To: Wei Liu Cc: xen-arm , "xen-users@lists.xen.org" , "xen-api@lists.xen.org" , Lars Kurth , "xen-devel@lists.xen.org" Subject: Re: [Xen-users] Xen Documentation Day: Feb 25th X-BeenThere: xen-users@lists.xen.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="===============8620897407141534915==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============8620897407141534915== Content-Type: multipart/alternative; boundary=bcaec54ee2240a96e204d69b017d --bcaec54ee2240a96e204d69b017d Content-Type: text/plain; charset=UTF-8 On Mon, Feb 25, 2013 at 10:31 AM, Wei Liu wrote: > On Mon, 2013-02-25 at 18:26 +0000, Grant McWilliams wrote: > > > > We have two Xen Document Days one week apart? > > > No. We remind people of the Xen Docsday one week before. And we also > send another email when it is happening. :-) > > > Regards > Wei. > > > Oh, so it's the same message from a week ago? I'm not sure that was very clear by reading it. I missed it but it's not because of this, I was really busy writing documentation... ;-) Grant McWilliams --bcaec54ee2240a96e204d69b017d Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On Mon, Feb 25, 2013 at 10:31 AM, Wei Liu <wei.liu2@citrix.com> wrote:
On Mon, 2013-02-25 at 18:26 +0000, Grant McWilliams wrote= :
>
> We have two Xen Document Days one week apart?


No. We remind people of the Xen Docsday one week before. And we also<= br> send another email when it is happening. :-)


Regards
Wei.


Oh, so it's the same message from a we= ek ago? I'm not sure that was very clear by reading it.=C2=A0
I mis= sed it but it's not because of this, I was really busy writing document= ation... ;-)

Grant McWilliams
--bcaec54ee2240a96e204d69b017d-- --===============8620897407141534915== 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 --===============8620897407141534915==-- From xen-users-bounces@lists.xen.org Tue Feb 26 08:13:15 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 26 Feb 2013 08:13: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 1UAFdn-0000Cz-IG; Tue, 26 Feb 2013 08:11:59 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UAFdl-0000Cu-OE for xen-users@lists.xen.org; Tue, 26 Feb 2013 08:11:57 +0000 Received: from [85.158.139.83:29216] by server-1.bemta-5.messagelabs.com id EE/7E-14063-C4E6C215; Tue, 26 Feb 2013 08:11:56 +0000 X-Env-Sender: Ian.Campbell@citrix.com X-Msg-Ref: server-15.tower-182.messagelabs.com!1361866316!28824440!1 X-Originating-IP: [46.33.159.39] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNDYuMzMuMTU5LjM5ID0+IDI0MDA5\n X-StarScan-Received: X-StarScan-Version: 6.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 26727 invoked from network); 26 Feb 2013 08:11:56 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (46.33.159.39) by server-15.tower-182.messagelabs.com with RC4-SHA encrypted SMTP; 26 Feb 2013 08:11:56 -0000 X-IronPort-AV: E=Sophos;i="4.84,739,1355097600"; d="scan'208";a="1881124" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 26 Feb 2013 08:11:56 +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.297.1; Tue, 26 Feb 2013 08:11:55 +0000 Message-ID: <1361866314.11431.23.camel@dagon.hellion.org.uk> From: Ian Campbell To: "travis@wsor.net" Date: Tue, 26 Feb 2013 08:11:54 +0000 In-Reply-To: References: <1361784654.26546.165.camel@zakaz.uk.xensource.com> <1361805642.26546.184.camel@zakaz.uk.xensource.com> Organization: Citrix Systems, Inc. X-Mailer: Evolution 3.4.4-1 MIME-Version: 1.0 Cc: xen-users Subject: Re: [Xen-users] pv guest fails to start after 4.2 upgrade X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: 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, 2013-02-25 at 22:47 +0000, Travis Osterman wrote: > >>> >> I also tried to take pvgrub out of the picture so I mounted the image > >>> >> and copied my initrd and kernel to the dom0 file system and updated my > >>> >> config with the appropriate ramdisk and kernel lines. > >>> >> > >>> >> Full output without pvgrub > >>> >> http://pastebin.com/c7VWWwXk > >>> >> > >>> >> Which dropped me in a shell asking for my root partition (progress). > >>> > >>> # cat /var/log/xen/qemu-dm-prime.log > >>> bind(unix:/var/run/xen/qmp-libxl-4): No such file or directory > >>> chardev: opening backend "socket" failed: No such file or directory > >>> > >>> # ls /var/run/xen* > >>> /var/run/xenconsoled.pid /var/run/xenstored.pid > >>> > >>> /var/run/xenstored: > >>> socket socket_ro > >> > >> Ah, you are missing the /var/run/xen/ directory so it is failing to > >> create the socket, if you create the directory does it work? Although > >> even if so it is obviously still a bug that libxl doesn't handle that > >> error... > > > > Ian, > > > > I can confirm the manually creating /var/run/xen fixes the problem. I > > updated my bug report here > > https://bugs.gentoo.org/show_bug.cgi?id=459082 > > > > Thank you for the help. > > > > Similar error not solved by the above on a domain using pygrub (pvgrub works) > > /var/log/xen/qemu-dm-domain.log > /var/tmp/portage/app-emulation/xen-tools-4.1.1-r6/work/xen-4.1.1/tools/ioemu-qemu-xen/hw/xen_blktap. > c:628: Init blktap pipes > Could not open /var/run/tap/qemu-read-2 Do you have /var/run/tap ? I'm a bit surprised to see the qemu tap support getting activated, I didn't think it was used for anything there days. Ian. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Tue Feb 26 08:13:15 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 26 Feb 2013 08:13: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 1UAFdn-0000Cz-IG; Tue, 26 Feb 2013 08:11:59 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UAFdl-0000Cu-OE for xen-users@lists.xen.org; Tue, 26 Feb 2013 08:11:57 +0000 Received: from [85.158.139.83:29216] by server-1.bemta-5.messagelabs.com id EE/7E-14063-C4E6C215; Tue, 26 Feb 2013 08:11:56 +0000 X-Env-Sender: Ian.Campbell@citrix.com X-Msg-Ref: server-15.tower-182.messagelabs.com!1361866316!28824440!1 X-Originating-IP: [46.33.159.39] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNDYuMzMuMTU5LjM5ID0+IDI0MDA5\n X-StarScan-Received: X-StarScan-Version: 6.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 26727 invoked from network); 26 Feb 2013 08:11:56 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (46.33.159.39) by server-15.tower-182.messagelabs.com with RC4-SHA encrypted SMTP; 26 Feb 2013 08:11:56 -0000 X-IronPort-AV: E=Sophos;i="4.84,739,1355097600"; d="scan'208";a="1881124" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 26 Feb 2013 08:11:56 +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.297.1; Tue, 26 Feb 2013 08:11:55 +0000 Message-ID: <1361866314.11431.23.camel@dagon.hellion.org.uk> From: Ian Campbell To: "travis@wsor.net" Date: Tue, 26 Feb 2013 08:11:54 +0000 In-Reply-To: References: <1361784654.26546.165.camel@zakaz.uk.xensource.com> <1361805642.26546.184.camel@zakaz.uk.xensource.com> Organization: Citrix Systems, Inc. X-Mailer: Evolution 3.4.4-1 MIME-Version: 1.0 Cc: xen-users Subject: Re: [Xen-users] pv guest fails to start after 4.2 upgrade X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: 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, 2013-02-25 at 22:47 +0000, Travis Osterman wrote: > >>> >> I also tried to take pvgrub out of the picture so I mounted the image > >>> >> and copied my initrd and kernel to the dom0 file system and updated my > >>> >> config with the appropriate ramdisk and kernel lines. > >>> >> > >>> >> Full output without pvgrub > >>> >> http://pastebin.com/c7VWWwXk > >>> >> > >>> >> Which dropped me in a shell asking for my root partition (progress). > >>> > >>> # cat /var/log/xen/qemu-dm-prime.log > >>> bind(unix:/var/run/xen/qmp-libxl-4): No such file or directory > >>> chardev: opening backend "socket" failed: No such file or directory > >>> > >>> # ls /var/run/xen* > >>> /var/run/xenconsoled.pid /var/run/xenstored.pid > >>> > >>> /var/run/xenstored: > >>> socket socket_ro > >> > >> Ah, you are missing the /var/run/xen/ directory so it is failing to > >> create the socket, if you create the directory does it work? Although > >> even if so it is obviously still a bug that libxl doesn't handle that > >> error... > > > > Ian, > > > > I can confirm the manually creating /var/run/xen fixes the problem. I > > updated my bug report here > > https://bugs.gentoo.org/show_bug.cgi?id=459082 > > > > Thank you for the help. > > > > Similar error not solved by the above on a domain using pygrub (pvgrub works) > > /var/log/xen/qemu-dm-domain.log > /var/tmp/portage/app-emulation/xen-tools-4.1.1-r6/work/xen-4.1.1/tools/ioemu-qemu-xen/hw/xen_blktap. > c:628: Init blktap pipes > Could not open /var/run/tap/qemu-read-2 Do you have /var/run/tap ? I'm a bit surprised to see the qemu tap support getting activated, I didn't think it was used for anything there days. Ian. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Tue Feb 26 09:05:38 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 26 Feb 2013 09:05: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 1UAGSg-0001X4-Ic; Tue, 26 Feb 2013 09:04:34 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UAGSe-0001Wx-Fv for xen-users@lists.xen.org; Tue, 26 Feb 2013 09:04:32 +0000 Received: from [85.158.137.99:9906] by server-11.bemta-3.messagelabs.com id C9/BC-10249-F9A7C215; Tue, 26 Feb 2013 09:04:31 +0000 X-Env-Sender: tolga@ozses.net X-Msg-Ref: server-14.tower-217.messagelabs.com!1361869468!18071147!1 X-Originating-IP: [74.125.83.42] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 18677 invoked from network); 26 Feb 2013 09:04:28 -0000 Received: from mail-ee0-f42.google.com (HELO mail-ee0-f42.google.com) (74.125.83.42) by server-14.tower-217.messagelabs.com with RC4-SHA encrypted SMTP; 26 Feb 2013 09:04:28 -0000 Received: by mail-ee0-f42.google.com with SMTP id b47so2132620eek.29 for ; Tue, 26 Feb 2013 01:04:28 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=x-received:message-id:date:from:user-agent:mime-version:to:subject :content-type:content-transfer-encoding:x-gm-message-state; bh=OkuvvF5FtKch5AhED6kljKIKUkjs7ODOog1FuC9i4Q0=; b=k+edWSlVKqWqmUUVGuI0a7rhDJOruL/qk/D4tXfX6dxJekM7xn+99BvEfmda4pXG8r cphDdDA3ir11tEw8Wmt35nJAihnRmopDCplEX5dPkECHySLOkHBZRT8kcs2IInlK0n2J AoTs3wlsWeBHEd/7FxD8J7lJeIF5uqdTJeSXKk40Hia3zloDoNSMc99WLmGAYH/INgBd r9vAoSYYUYdD6NZ5BSc5qWUmOiofQzyeSdMSESmHft/JhpoNvIGYeSlRmMby2V1EiSbO K8Zds744wKu25UATbO7Ry1yu5Imz2so5YYY6zIYm7hEhG+z3kqcQAgWjvVCx35c/X/i7 n2IA== X-Received: by 10.14.220.135 with SMTP id o7mr48384434eep.3.1361869468471; Tue, 26 Feb 2013 01:04:28 -0800 (PST) Received: from [10.18.1.25] ([193.255.135.254]) by mx.google.com with ESMTPS id a1sm345215eep.2.2013.02.26.01.04.26 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 26 Feb 2013 01:04:27 -0800 (PST) Message-ID: <512C7A9D.4040906@ozses.net> Date: Tue, 26 Feb 2013 11:04:29 +0200 From: =?ISO-8859-1?Q?Muzaffer_Tolga_=D6zses?= User-Agent: Mozilla/5.0 (X11; Linux i686; rv:16.0) Gecko/20121028 Thunderbird/16.0.2 MIME-Version: 1.0 To: xen-users X-Gm-Message-State: ALoCoQmLtSd5odAcFsEZ7gmV/kF/IaNbQndeU+IctelFmHTdc0kHgi2ESmOvAa0TwvoWVFDDDtw2 Subject: [Xen-users] Kernel switch X-BeenThere: xen-users@lists.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 don't know if this is the appropriate place. I had installed Xen a long time ago, and now I need to switch kernels. However when I do that, I get "/bin/sh: error while loading shared libraries: libc.so.6: cannot open object file: No such file or directory". I also upgraded the kernel, and I get the same message. why am I getting that? I've got /lib/i386-linux-gnu/libc.so.6 Regards, _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Tue Feb 26 09:05:38 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 26 Feb 2013 09:05: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 1UAGSg-0001X4-Ic; Tue, 26 Feb 2013 09:04:34 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UAGSe-0001Wx-Fv for xen-users@lists.xen.org; Tue, 26 Feb 2013 09:04:32 +0000 Received: from [85.158.137.99:9906] by server-11.bemta-3.messagelabs.com id C9/BC-10249-F9A7C215; Tue, 26 Feb 2013 09:04:31 +0000 X-Env-Sender: tolga@ozses.net X-Msg-Ref: server-14.tower-217.messagelabs.com!1361869468!18071147!1 X-Originating-IP: [74.125.83.42] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 18677 invoked from network); 26 Feb 2013 09:04:28 -0000 Received: from mail-ee0-f42.google.com (HELO mail-ee0-f42.google.com) (74.125.83.42) by server-14.tower-217.messagelabs.com with RC4-SHA encrypted SMTP; 26 Feb 2013 09:04:28 -0000 Received: by mail-ee0-f42.google.com with SMTP id b47so2132620eek.29 for ; Tue, 26 Feb 2013 01:04:28 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=x-received:message-id:date:from:user-agent:mime-version:to:subject :content-type:content-transfer-encoding:x-gm-message-state; bh=OkuvvF5FtKch5AhED6kljKIKUkjs7ODOog1FuC9i4Q0=; b=k+edWSlVKqWqmUUVGuI0a7rhDJOruL/qk/D4tXfX6dxJekM7xn+99BvEfmda4pXG8r cphDdDA3ir11tEw8Wmt35nJAihnRmopDCplEX5dPkECHySLOkHBZRT8kcs2IInlK0n2J AoTs3wlsWeBHEd/7FxD8J7lJeIF5uqdTJeSXKk40Hia3zloDoNSMc99WLmGAYH/INgBd r9vAoSYYUYdD6NZ5BSc5qWUmOiofQzyeSdMSESmHft/JhpoNvIGYeSlRmMby2V1EiSbO K8Zds744wKu25UATbO7Ry1yu5Imz2so5YYY6zIYm7hEhG+z3kqcQAgWjvVCx35c/X/i7 n2IA== X-Received: by 10.14.220.135 with SMTP id o7mr48384434eep.3.1361869468471; Tue, 26 Feb 2013 01:04:28 -0800 (PST) Received: from [10.18.1.25] ([193.255.135.254]) by mx.google.com with ESMTPS id a1sm345215eep.2.2013.02.26.01.04.26 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 26 Feb 2013 01:04:27 -0800 (PST) Message-ID: <512C7A9D.4040906@ozses.net> Date: Tue, 26 Feb 2013 11:04:29 +0200 From: =?ISO-8859-1?Q?Muzaffer_Tolga_=D6zses?= User-Agent: Mozilla/5.0 (X11; Linux i686; rv:16.0) Gecko/20121028 Thunderbird/16.0.2 MIME-Version: 1.0 To: xen-users X-Gm-Message-State: ALoCoQmLtSd5odAcFsEZ7gmV/kF/IaNbQndeU+IctelFmHTdc0kHgi2ESmOvAa0TwvoWVFDDDtw2 Subject: [Xen-users] Kernel switch X-BeenThere: xen-users@lists.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 don't know if this is the appropriate place. I had installed Xen a long time ago, and now I need to switch kernels. However when I do that, I get "/bin/sh: error while loading shared libraries: libc.so.6: cannot open object file: No such file or directory". I also upgraded the kernel, and I get the same message. why am I getting that? I've got /lib/i386-linux-gnu/libc.so.6 Regards, _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Tue Feb 26 10:24:55 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 26 Feb 2013 10: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 1UAHh9-0004FO-Bi; Tue, 26 Feb 2013 10:23:35 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UAHh8-0004FD-8S for xen-users@lists.xen.org; Tue, 26 Feb 2013 10:23:34 +0000 Received: from [85.158.143.99:15959] by server-3.bemta-4.messagelabs.com id 7A/B0-02186-52D8C215; Tue, 26 Feb 2013 10:23:33 +0000 X-Env-Sender: Ian.Campbell@citrix.com X-Msg-Ref: server-16.tower-216.messagelabs.com!1361874117!17772906!1 X-Originating-IP: [46.33.159.39] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNDYuMzMuMTU5LjM5ID0+IDI0MTk1\n X-StarScan-Received: X-StarScan-Version: 6.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 2817 invoked from network); 26 Feb 2013 10:21:57 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (46.33.159.39) by server-16.tower-216.messagelabs.com with RC4-SHA encrypted SMTP; 26 Feb 2013 10:21:57 -0000 X-IronPort-AV: E=Sophos;i="4.84,739,1355097600"; d="scan'208";a="1889326" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 26 Feb 2013 10:21: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.297.1; Tue, 26 Feb 2013 10:21:57 +0000 Message-ID: <1361874116.26546.256.camel@zakaz.uk.xensource.com> From: Ian Campbell To: Yaodong Yang Date: Tue, 26 Feb 2013 10:21:56 +0000 In-Reply-To: References: Organization: Citrix Systems, Inc. X-Mailer: Evolution 3.4.4-1 MIME-Version: 1.0 Cc: "xen-users@lists.xen.org" Subject: Re: [Xen-users] Xen Domain U can not install (on Ubuntu.) X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: 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, 2013-02-25 at 18:41 +0000, Yaodong Yang wrote: > When I was installing the domain U (also a Ubuntu image), I was told > the dhcp does not work. If I choose not to configure dhcp, then I was > asked to choose a mirror. But in fact, I already download the image in > disk. Which exact disk have you downloaded? Please provide your guest configuration file. Ian. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Tue Feb 26 10:24:55 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 26 Feb 2013 10: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 1UAHh9-0004FO-Bi; Tue, 26 Feb 2013 10:23:35 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UAHh8-0004FD-8S for xen-users@lists.xen.org; Tue, 26 Feb 2013 10:23:34 +0000 Received: from [85.158.143.99:15959] by server-3.bemta-4.messagelabs.com id 7A/B0-02186-52D8C215; Tue, 26 Feb 2013 10:23:33 +0000 X-Env-Sender: Ian.Campbell@citrix.com X-Msg-Ref: server-16.tower-216.messagelabs.com!1361874117!17772906!1 X-Originating-IP: [46.33.159.39] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNDYuMzMuMTU5LjM5ID0+IDI0MTk1\n X-StarScan-Received: X-StarScan-Version: 6.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 2817 invoked from network); 26 Feb 2013 10:21:57 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (46.33.159.39) by server-16.tower-216.messagelabs.com with RC4-SHA encrypted SMTP; 26 Feb 2013 10:21:57 -0000 X-IronPort-AV: E=Sophos;i="4.84,739,1355097600"; d="scan'208";a="1889326" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 26 Feb 2013 10:21: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.297.1; Tue, 26 Feb 2013 10:21:57 +0000 Message-ID: <1361874116.26546.256.camel@zakaz.uk.xensource.com> From: Ian Campbell To: Yaodong Yang Date: Tue, 26 Feb 2013 10:21:56 +0000 In-Reply-To: References: Organization: Citrix Systems, Inc. X-Mailer: Evolution 3.4.4-1 MIME-Version: 1.0 Cc: "xen-users@lists.xen.org" Subject: Re: [Xen-users] Xen Domain U can not install (on Ubuntu.) X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: 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, 2013-02-25 at 18:41 +0000, Yaodong Yang wrote: > When I was installing the domain U (also a Ubuntu image), I was told > the dhcp does not work. If I choose not to configure dhcp, then I was > asked to choose a mirror. But in fact, I already download the image in > disk. Which exact disk have you downloaded? Please provide your guest configuration file. Ian. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Tue Feb 26 12:42:14 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 26 Feb 2013 12:42: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 1UAJqH-0007eU-Dh; Tue, 26 Feb 2013 12:41:09 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UA4v4-0008D6-Pl for xen-users@lists.xen.org; Mon, 25 Feb 2013 20:45:07 +0000 Received: from [85.158.137.99:26501] by server-7.bemta-3.messagelabs.com id 00/03-10367-D4DCB215; Mon, 25 Feb 2013 20:45:01 +0000 X-Env-Sender: ydev@cs.utah.edu X-Msg-Ref: server-9.tower-217.messagelabs.com!1361825098!14875587!1 X-Originating-IP: [155.98.64.241] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 26539 invoked from network); 25 Feb 2013 20:45:00 -0000 Received: from mail-svr1.cs.utah.edu (HELO mail-svr1.cs.utah.edu) (155.98.64.241) by server-9.tower-217.messagelabs.com with SMTP; 25 Feb 2013 20:45:00 -0000 Received: from localhost (localhost [127.0.0.1]) by mail-svr1.cs.utah.edu (Postfix) with ESMTP id B6B2E6500AE; Mon, 25 Feb 2013 13:44:52 -0700 (MST) X-Virus-Scanned: amavisd-new at cs.utah.edu Received: from mail-svr1.cs.utah.edu ([127.0.0.1]) by localhost (mail-svr1.cs.utah.edu [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Ir-PUiY+AMPe; Mon, 25 Feb 2013 13:44:52 -0700 (MST) Received: from [128.110.69.71] (128-110-69-71.uconnect.utah.edu [128.110.69.71]) by smtps.cs.utah.edu (Postfix) with ESMTPSA id 508606500AF; Mon, 25 Feb 2013 13:44:52 -0700 (MST) Message-ID: <512BCD3D.2080208@cs.utah.edu> Date: Mon, 25 Feb 2013 13:44:45 -0700 From: Yathindra User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130215 Thunderbird/17.0.3 MIME-Version: 1.0 To: Ian Campbell References: <5125DCBB.2080305@cs.utah.edu> <51284379.3070608@cs.utah.edu> <1361784186.26546.161.camel@zakaz.uk.xensource.com> In-Reply-To: <1361784186.26546.161.camel@zakaz.uk.xensource.com> X-Mailman-Approved-At: Tue, 26 Feb 2013 12:41:08 +0000 Cc: "xen-users@lists.xen.org" Subject: Re: [Xen-users] Issuing hypercalls from Linux 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: , 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 2/25/2013 2:23 AM, Ian Campbell wrote: > On Sat, 2013-02-23 at 04:20 +0000, Yathindra wrote: >> On 2/21/2013 1:37 AM, Yathindra wrote: >>> Hi, >>> >>> I have defined a new hypercall in Xen hypervisor. It is similar to >>> do_domctl() >>> in that I pass a single argument and use XEN_GUEST_HANDLE() to >>> retrieve the >>> arguments. Its currently working fine under Xen-4.3-unstable. >>> >>> Now I want to invoke this hypercall via Linux-3.7.5 Guest. How do I go >>> about >>> doing this. >>> >>> Thanks, >>> Yathi >> Hi, >> >> I followed a approach similar to do_physdev_op in Linux-3.7.5. >> I have a similar set of files under include/xen/interface/ directory. >> After plumbing everything when I execute my hypercall via Linux, >> I get -14 (EFAULT) as the return value. I added printk's on the Xen >> side to see if the hypercall is reaching Xen but it does not. >> >> Any general direction regarding this would be very helpful. > EFAULT usually means that one of the pointers which you passed to the > hypercall was not to correctly mapped memory. > > It might be useful to post your code for both sides of the equation > (Linux & Xen). > > Ian. I was passing incorrect arguments and hence the copy_from_guest() failed with -EFAULT. Sorry about spamming, it was a silly mistake. Thanks for the reply Ian. - Yathi _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Tue Feb 26 12:42:14 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 26 Feb 2013 12:42: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 1UAJqH-0007eU-Dh; Tue, 26 Feb 2013 12:41:09 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UA4v4-0008D6-Pl for xen-users@lists.xen.org; Mon, 25 Feb 2013 20:45:07 +0000 Received: from [85.158.137.99:26501] by server-7.bemta-3.messagelabs.com id 00/03-10367-D4DCB215; Mon, 25 Feb 2013 20:45:01 +0000 X-Env-Sender: ydev@cs.utah.edu X-Msg-Ref: server-9.tower-217.messagelabs.com!1361825098!14875587!1 X-Originating-IP: [155.98.64.241] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 26539 invoked from network); 25 Feb 2013 20:45:00 -0000 Received: from mail-svr1.cs.utah.edu (HELO mail-svr1.cs.utah.edu) (155.98.64.241) by server-9.tower-217.messagelabs.com with SMTP; 25 Feb 2013 20:45:00 -0000 Received: from localhost (localhost [127.0.0.1]) by mail-svr1.cs.utah.edu (Postfix) with ESMTP id B6B2E6500AE; Mon, 25 Feb 2013 13:44:52 -0700 (MST) X-Virus-Scanned: amavisd-new at cs.utah.edu Received: from mail-svr1.cs.utah.edu ([127.0.0.1]) by localhost (mail-svr1.cs.utah.edu [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Ir-PUiY+AMPe; Mon, 25 Feb 2013 13:44:52 -0700 (MST) Received: from [128.110.69.71] (128-110-69-71.uconnect.utah.edu [128.110.69.71]) by smtps.cs.utah.edu (Postfix) with ESMTPSA id 508606500AF; Mon, 25 Feb 2013 13:44:52 -0700 (MST) Message-ID: <512BCD3D.2080208@cs.utah.edu> Date: Mon, 25 Feb 2013 13:44:45 -0700 From: Yathindra User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130215 Thunderbird/17.0.3 MIME-Version: 1.0 To: Ian Campbell References: <5125DCBB.2080305@cs.utah.edu> <51284379.3070608@cs.utah.edu> <1361784186.26546.161.camel@zakaz.uk.xensource.com> In-Reply-To: <1361784186.26546.161.camel@zakaz.uk.xensource.com> X-Mailman-Approved-At: Tue, 26 Feb 2013 12:41:08 +0000 Cc: "xen-users@lists.xen.org" Subject: Re: [Xen-users] Issuing hypercalls from Linux 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: , 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 2/25/2013 2:23 AM, Ian Campbell wrote: > On Sat, 2013-02-23 at 04:20 +0000, Yathindra wrote: >> On 2/21/2013 1:37 AM, Yathindra wrote: >>> Hi, >>> >>> I have defined a new hypercall in Xen hypervisor. It is similar to >>> do_domctl() >>> in that I pass a single argument and use XEN_GUEST_HANDLE() to >>> retrieve the >>> arguments. Its currently working fine under Xen-4.3-unstable. >>> >>> Now I want to invoke this hypercall via Linux-3.7.5 Guest. How do I go >>> about >>> doing this. >>> >>> Thanks, >>> Yathi >> Hi, >> >> I followed a approach similar to do_physdev_op in Linux-3.7.5. >> I have a similar set of files under include/xen/interface/ directory. >> After plumbing everything when I execute my hypercall via Linux, >> I get -14 (EFAULT) as the return value. I added printk's on the Xen >> side to see if the hypercall is reaching Xen but it does not. >> >> Any general direction regarding this would be very helpful. > EFAULT usually means that one of the pointers which you passed to the > hypercall was not to correctly mapped memory. > > It might be useful to post your code for both sides of the equation > (Linux & Xen). > > Ian. I was passing incorrect arguments and hence the copy_from_guest() failed with -EFAULT. Sorry about spamming, it was a silly mistake. Thanks for the reply Ian. - Yathi _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Tue Feb 26 13:12:40 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 26 Feb 2013 13:12: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 1UAKJr-0000sU-6O; Tue, 26 Feb 2013 13:11:43 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UAKJq-0000sJ-6E for xen-users@lists.xen.org; Tue, 26 Feb 2013 13:11:42 +0000 Received: from [85.158.139.211:59037] by server-8.bemta-5.messagelabs.com id AC/FE-05790-D84BC215; Tue, 26 Feb 2013 13:11:41 +0000 X-Env-Sender: udo_the_man@yahoo.de X-Msg-Ref: server-16.tower-206.messagelabs.com!1361884300!19377891!1 X-Originating-IP: [77.238.189.64] X-SpamReason: No, hits=0.0 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, spamassassin: X-StarScan-Received: X-StarScan-Version: 6.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 19696 invoked from network); 26 Feb 2013 13:11:40 -0000 Received: from nm11.bullet.mail.ird.yahoo.com (HELO nm11.bullet.mail.ird.yahoo.com) (77.238.189.64) by server-16.tower-206.messagelabs.com with SMTP; 26 Feb 2013 13:11:40 -0000 Received: from [77.238.189.232] by nm11.bullet.mail.ird.yahoo.com with NNFMP; 26 Feb 2013 13:11:40 -0000 Received: from [46.228.39.59] by tm13.bullet.mail.ird.yahoo.com with NNFMP; 26 Feb 2013 13:11:40 -0000 Received: from [127.0.0.1] by smtp192.mail.ir2.yahoo.com with NNFMP; 26 Feb 2013 13:11:40 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.de; s=s1024; t=1361884300; bh=/J21Y7ptf60lTMWYbY84a5kbeiSghfxgYVXwnYGWFpk=; 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=sYFlS4FxuvZs8ZUM7Z7WknAvlTabOfC17wRP0Aa/7eDLCluTFaox++sj4EatRDaR5J5Lnxg4gf0mGR+eSoCJ9Gf3YzQAg+BKbURGJEeyDF6mjngXgl7HdCHX3/LCAXyB2St6ku1qMtxbChLZMzRTJObCZ3nGUryfuLUDmcGmEso= X-Yahoo-Newman-Id: 314129.2216.bm@smtp192.mail.ir2.yahoo.com X-Yahoo-Newman-Property: ymail-3 X-YMail-OSG: MZDm7R0VM1m5VjLqEs4Qr.P2_vQ2mXp5W06kDNQOsN1tdOa OGPQyepF54_g_mp52pCJZv8kD_EzuA63UpMkgbTAv128rETOt4q6cVQK1lgz 24FPcWVXU2bo79Epwp5.a6kv6CJB5mKeNcoB9ZDJEBQYXvPUHS.3cLaKx6k. 4DtPEtlbce9d6eA.96mXD9lIr.JseAVRHlamCFeLuzyqhjt3BeJWZIqhy1V0 vX1__W9dmZDHf7D.W3WZc9M7pMSalFJdfTH6ekKSbZJWLr8V3kLO25Sg4qv0 MC9WbZ4.Ck4OQKaAjep0AT.LqBdgONjUSZFy9qzeYemsjP3GsP1l0Ipoh5Qw wXzBbVUzC5Scc9STK.FitrLZ3sZOZTc0vBFLYhDODVEFm5JodMtVLdZax98z vc9zCGi.3bFNsStQ6Nn7pZSSorXP4.W_gZ3RaGfWBch.BCkIZFfwN5iVC2JA _8vNmrzkT26lgk95IU0Mwbr4m4F2yv6brLGmJpIyzANBWCUMCiZPIaqX_mq. wp1hWZ4Qvd7aur4V0dQ-- X-Yahoo-SMTP: qrLXS16swBA_RQ4sRvWxpRdQza3SvvBC Received: from [130.83.40.195] (udo_the_man@130.83.40.195 with plain) by smtp192.mail.ir2.yahoo.com with SMTP; 26 Feb 2013 13:11:40 +0000 UTC Message-ID: <512CB48C.4010904@yahoo.de> Date: Tue, 26 Feb 2013 14:11:40 +0100 From: Udo User-Agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/20130106 Thunderbird/17.0.2 MIME-Version: 1.0 To: xen-users@lists.xen.org Subject: [Xen-users] Problems to start Ubuntu as 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 Hi, my Dom0 is an Ubuntu 12.04 64Bit and Xen starts without problems. I would like to have the same Ubuntu (12.04 or 10.04) as a PV. I have done the following: 1. Get the vmlinuz and initrd.gz from : http://archive.ubuntu.com/ubuntu/dists/... 2. lvcreate -L 10G -n vm1 /dev/lvm 3. My cfg file is: name = "vm1" memory = 1024 disk = ['phy:/dev/lvm/vm1,xvda,w'] vif = ['bridge=xenbr0'] kernel = "/var/lib/xen/images/ubuntu-netboot-12.04/vmlinuz" ramdisk = "/var/lib/xen/images/ubuntu-netboot-12.04/initrd.gz" extra = "debian-installer/exit/always_halt=true -- console=hvc0" 4. xl create -c vm1.cfg The installation finish every time without any errors. 5. Change vm1.cfg file: name = "vm1" memory = 1024 disk = ['phy:/dev/lvm/vm1,xvda,w'] vif = ['bridge=xenbr0'] #kernel = "/var/lib/xen/images/ubuntu-netboot-12.04/vmlinuz" #ramdisk = "/var/lib/xen/images/ubuntu-netboot-12.04/initrd.gz" #extra = "debian-installer/exit/always_halt=true -- console=hvc0"| bootloader = "pygrub" 6. xl create vm1.cfg -> var/log/xen/xl.vm1.log Waiting for domain vm1 (domid 1) to die Domain 1 is dead Action for shutdown reason code 0 is destroy Domain 1 needs to be cleaned up: destroying the domain Done. Exiting now I have also done the same way using Ubuntu 10.04 files (vmlinuz, initrd.gz) and get the same error. Does anybody have an idea what I'm doing wrong? Thanx! _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Tue Feb 26 13:12:40 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 26 Feb 2013 13:12: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 1UAKJr-0000sU-6O; Tue, 26 Feb 2013 13:11:43 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UAKJq-0000sJ-6E for xen-users@lists.xen.org; Tue, 26 Feb 2013 13:11:42 +0000 Received: from [85.158.139.211:59037] by server-8.bemta-5.messagelabs.com id AC/FE-05790-D84BC215; Tue, 26 Feb 2013 13:11:41 +0000 X-Env-Sender: udo_the_man@yahoo.de X-Msg-Ref: server-16.tower-206.messagelabs.com!1361884300!19377891!1 X-Originating-IP: [77.238.189.64] X-SpamReason: No, hits=0.0 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, spamassassin: X-StarScan-Received: X-StarScan-Version: 6.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 19696 invoked from network); 26 Feb 2013 13:11:40 -0000 Received: from nm11.bullet.mail.ird.yahoo.com (HELO nm11.bullet.mail.ird.yahoo.com) (77.238.189.64) by server-16.tower-206.messagelabs.com with SMTP; 26 Feb 2013 13:11:40 -0000 Received: from [77.238.189.232] by nm11.bullet.mail.ird.yahoo.com with NNFMP; 26 Feb 2013 13:11:40 -0000 Received: from [46.228.39.59] by tm13.bullet.mail.ird.yahoo.com with NNFMP; 26 Feb 2013 13:11:40 -0000 Received: from [127.0.0.1] by smtp192.mail.ir2.yahoo.com with NNFMP; 26 Feb 2013 13:11:40 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.de; s=s1024; t=1361884300; bh=/J21Y7ptf60lTMWYbY84a5kbeiSghfxgYVXwnYGWFpk=; 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=sYFlS4FxuvZs8ZUM7Z7WknAvlTabOfC17wRP0Aa/7eDLCluTFaox++sj4EatRDaR5J5Lnxg4gf0mGR+eSoCJ9Gf3YzQAg+BKbURGJEeyDF6mjngXgl7HdCHX3/LCAXyB2St6ku1qMtxbChLZMzRTJObCZ3nGUryfuLUDmcGmEso= X-Yahoo-Newman-Id: 314129.2216.bm@smtp192.mail.ir2.yahoo.com X-Yahoo-Newman-Property: ymail-3 X-YMail-OSG: MZDm7R0VM1m5VjLqEs4Qr.P2_vQ2mXp5W06kDNQOsN1tdOa OGPQyepF54_g_mp52pCJZv8kD_EzuA63UpMkgbTAv128rETOt4q6cVQK1lgz 24FPcWVXU2bo79Epwp5.a6kv6CJB5mKeNcoB9ZDJEBQYXvPUHS.3cLaKx6k. 4DtPEtlbce9d6eA.96mXD9lIr.JseAVRHlamCFeLuzyqhjt3BeJWZIqhy1V0 vX1__W9dmZDHf7D.W3WZc9M7pMSalFJdfTH6ekKSbZJWLr8V3kLO25Sg4qv0 MC9WbZ4.Ck4OQKaAjep0AT.LqBdgONjUSZFy9qzeYemsjP3GsP1l0Ipoh5Qw wXzBbVUzC5Scc9STK.FitrLZ3sZOZTc0vBFLYhDODVEFm5JodMtVLdZax98z vc9zCGi.3bFNsStQ6Nn7pZSSorXP4.W_gZ3RaGfWBch.BCkIZFfwN5iVC2JA _8vNmrzkT26lgk95IU0Mwbr4m4F2yv6brLGmJpIyzANBWCUMCiZPIaqX_mq. wp1hWZ4Qvd7aur4V0dQ-- X-Yahoo-SMTP: qrLXS16swBA_RQ4sRvWxpRdQza3SvvBC Received: from [130.83.40.195] (udo_the_man@130.83.40.195 with plain) by smtp192.mail.ir2.yahoo.com with SMTP; 26 Feb 2013 13:11:40 +0000 UTC Message-ID: <512CB48C.4010904@yahoo.de> Date: Tue, 26 Feb 2013 14:11:40 +0100 From: Udo User-Agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/20130106 Thunderbird/17.0.2 MIME-Version: 1.0 To: xen-users@lists.xen.org Subject: [Xen-users] Problems to start Ubuntu as 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 Hi, my Dom0 is an Ubuntu 12.04 64Bit and Xen starts without problems. I would like to have the same Ubuntu (12.04 or 10.04) as a PV. I have done the following: 1. Get the vmlinuz and initrd.gz from : http://archive.ubuntu.com/ubuntu/dists/... 2. lvcreate -L 10G -n vm1 /dev/lvm 3. My cfg file is: name = "vm1" memory = 1024 disk = ['phy:/dev/lvm/vm1,xvda,w'] vif = ['bridge=xenbr0'] kernel = "/var/lib/xen/images/ubuntu-netboot-12.04/vmlinuz" ramdisk = "/var/lib/xen/images/ubuntu-netboot-12.04/initrd.gz" extra = "debian-installer/exit/always_halt=true -- console=hvc0" 4. xl create -c vm1.cfg The installation finish every time without any errors. 5. Change vm1.cfg file: name = "vm1" memory = 1024 disk = ['phy:/dev/lvm/vm1,xvda,w'] vif = ['bridge=xenbr0'] #kernel = "/var/lib/xen/images/ubuntu-netboot-12.04/vmlinuz" #ramdisk = "/var/lib/xen/images/ubuntu-netboot-12.04/initrd.gz" #extra = "debian-installer/exit/always_halt=true -- console=hvc0"| bootloader = "pygrub" 6. xl create vm1.cfg -> var/log/xen/xl.vm1.log Waiting for domain vm1 (domid 1) to die Domain 1 is dead Action for shutdown reason code 0 is destroy Domain 1 needs to be cleaned up: destroying the domain Done. Exiting now I have also done the same way using Ubuntu 10.04 files (vmlinuz, initrd.gz) and get the same error. Does anybody have an idea what I'm doing wrong? Thanx! _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Tue Feb 26 14:09:11 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 26 Feb 2013 14:09: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 1UALCV-0002TT-2L; Tue, 26 Feb 2013 14:08:11 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UALCT-0002TO-Dp for xen-users@lists.xen.org; Tue, 26 Feb 2013 14:08:09 +0000 Received: from [193.109.254.147:42873] by server-14.bemta-14.messagelabs.com id 1C/48-02031-8C1CC215; Tue, 26 Feb 2013 14:08:08 +0000 X-Env-Sender: tosterman@gmail.com X-Msg-Ref: server-12.tower-27.messagelabs.com!1361887441!9736231!1 X-Originating-IP: [209.85.223.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.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 21833 invoked from network); 26 Feb 2013 14:04:03 -0000 Received: from mail-ie0-f173.google.com (HELO mail-ie0-f173.google.com) (209.85.223.173) by server-12.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 26 Feb 2013 14:04:03 -0000 Received: by mail-ie0-f173.google.com with SMTP id 9so4474284iec.18 for ; Tue, 26 Feb 2013 06:04:01 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:reply-to:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=HV+iz5uEKo4fjnjnmshbbjjIjjyv+YkXNKjNVOCsiTo=; b=rHe3iQdSE8eaYjspEfyCni+PAdc5Co6AH/2fAXRbQNQZmyPvwpdaH8bvAJy54xGhzc 7TkS/c2l3QQ5TQJV5560d6ibGfgh5BtpawSBs2rUC4Sg9c37sZN30ywURuSy7s7QeTKx bn5mWXZMKjCUUrOyeyD5qq1NYI1cxuy8E3WvWkG9D53UPy93bjH7vbbFddOcDxI29Hbj 2FeJwr+5SJgcK7tRrP7LJYotwCt4AoH+s+LitdpdjtEbJlsrqz/J+1rW1WGfXb6XRjQJ ktlUHEtTUlDRiNu/XI/HOah7wdttqFJu09bebpF5D9Mf1oPdbqlCjiOWYznBNvB1+6eX F9cA== MIME-Version: 1.0 X-Received: by 10.50.212.3 with SMTP id ng3mr5471743igc.43.1361887441622; Tue, 26 Feb 2013 06:04:01 -0800 (PST) Received: by 10.64.60.136 with HTTP; Tue, 26 Feb 2013 06:04:01 -0800 (PST) In-Reply-To: <1361866314.11431.23.camel@dagon.hellion.org.uk> References: <1361784654.26546.165.camel@zakaz.uk.xensource.com> <1361805642.26546.184.camel@zakaz.uk.xensource.com> <1361866314.11431.23.camel@dagon.hellion.org.uk> Date: Tue, 26 Feb 2013 09:04:01 -0500 Message-ID: From: Travis Osterman To: xen-users Cc: Ian Campbell Subject: Re: [Xen-users] pv guest fails to start after 4.2 upgrade X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: travis@wsor.net List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: 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, Feb 26, 2013 at 3:11 AM, Ian Campbell wrote: > On Mon, 2013-02-25 at 22:47 +0000, Travis Osterman wrote: >> >>> >> I also tried to take pvgrub out of the picture so I mounted the image >> >>> >> and copied my initrd and kernel to the dom0 file system and updated my >> >>> >> config with the appropriate ramdisk and kernel lines. >> >>> >> >> >>> >> Full output without pvgrub >> >>> >> http://pastebin.com/c7VWWwXk >> >>> >> >> >>> >> Which dropped me in a shell asking for my root partition (progress). >> >>> >> >>> # cat /var/log/xen/qemu-dm-prime.log >> >>> bind(unix:/var/run/xen/qmp-libxl-4): No such file or directory >> >>> chardev: opening backend "socket" failed: No such file or directory >> >>> >> >>> # ls /var/run/xen* >> >>> /var/run/xenconsoled.pid /var/run/xenstored.pid >> >>> >> >>> /var/run/xenstored: >> >>> socket socket_ro >> >> >> >> Ah, you are missing the /var/run/xen/ directory so it is failing to >> >> create the socket, if you create the directory does it work? Although >> >> even if so it is obviously still a bug that libxl doesn't handle that >> >> error... >> > >> > Ian, >> > >> > I can confirm the manually creating /var/run/xen fixes the problem. I >> > updated my bug report here >> > https://bugs.gentoo.org/show_bug.cgi?id=459082 >> > >> > Thank you for the help. >> > >> >> Similar error not solved by the above on a domain using pygrub (pvgrub works) >> >> /var/log/xen/qemu-dm-domain.log >> /var/tmp/portage/app-emulation/xen-tools-4.1.1-r6/work/xen-4.1.1/tools/ioemu-qemu-xen/hw/xen_blktap. >> c:628: Init blktap pipes >> Could not open /var/run/tap/qemu-read-2 > > Do you have /var/run/tap ? > > I'm a bit surprised to see the qemu tap support getting activated, I > didn't think it was used for anything there days. > > Ian. > > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xen.org > http://lists.xen.org/xen-users I didn't have it, but created the directory as before. That didn't seem to fix things this time. I'm not familar with tap but here are the open tap libraries on my system currently. # lsof | grep -i tap xl 8451 root mem REG 253,0 30400 1462266 /usr/lib64/libblktapctl.so.1.0.0 xl 8451 8452 root mem REG 253,0 30400 1462266 /usr/lib64/libblktapctl.so.1.0.0 xl 18198 root mem REG 253,0 30400 1462266 /usr/lib64/libblktapctl.so.1.0.0 xl 18198 18199 root mem REG 253,0 30400 1462266 /usr/lib64/libblktapctl.so.1.0.0 qemu-dm 18580 root mem REG 253,0 18152 1462242 /usr/lib64/libblktap.so.3.0.0 qemu-dm 18580 18582 root mem REG 253,0 18152 1462242 /usr/lib64/libblktap.so.3.0.0 qemu-dm 18580 18583 root mem REG 253,0 18152 1462242 /usr/lib64/libblktap.so.3.0.0 xl 18671 root mem REG 253,0 30400 1462266 /usr/lib64/libblktapctl.so.1.0.0 xl 18671 18672 root mem REG 253,0 30400 1462266 /usr/lib64/libblktapctl.so.1.0.0 The 4.2 series of ebuilds really did a number on my setup (which had been previously working in 4.1). Here is the summary of changes I've noticed with the upgrade: pvgrub + file:/*.img: mkdir /var/run/xen does not get created so added a script to /etc/local.d as workaround (fixes) and didn't need /var/run/tap created pygrub + file:/*.img:also seems to want /var/run/tap, after creating that, still no xvda. I didnt' get a chance to troubleshoot that any further as I wasn't home last evening and wanted to leave the domain up with /dev/loop hvm + file:/*.img: a windows domain would no boot normally even after the above directories were created /var/log/*dm*.log Using xvda for guest's hda Strip off blktap sub-type prefix to /tank/xen/dev/winxp.img (drv 'aio') Using file /tank/xen/dev/winxp.img in read-write mode That looks like the disk was being loaded fine. I was able to log in via safe mode and found the gplpv drivers wouldn't load (which worked fine in 4.1). I'm getting around the pygrub and hvm currently by manually creating /dev/loop devices and using phy:/dev/loop in my disk config line. I'll try to give some more debug information later. I'm not sure if others are having problems but wish 4.2 hadn't been unmasked in portage quite yet. -- T _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Tue Feb 26 14:09:11 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 26 Feb 2013 14:09: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 1UALCV-0002TT-2L; Tue, 26 Feb 2013 14:08:11 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UALCT-0002TO-Dp for xen-users@lists.xen.org; Tue, 26 Feb 2013 14:08:09 +0000 Received: from [193.109.254.147:42873] by server-14.bemta-14.messagelabs.com id 1C/48-02031-8C1CC215; Tue, 26 Feb 2013 14:08:08 +0000 X-Env-Sender: tosterman@gmail.com X-Msg-Ref: server-12.tower-27.messagelabs.com!1361887441!9736231!1 X-Originating-IP: [209.85.223.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.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 21833 invoked from network); 26 Feb 2013 14:04:03 -0000 Received: from mail-ie0-f173.google.com (HELO mail-ie0-f173.google.com) (209.85.223.173) by server-12.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 26 Feb 2013 14:04:03 -0000 Received: by mail-ie0-f173.google.com with SMTP id 9so4474284iec.18 for ; Tue, 26 Feb 2013 06:04:01 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:reply-to:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=HV+iz5uEKo4fjnjnmshbbjjIjjyv+YkXNKjNVOCsiTo=; b=rHe3iQdSE8eaYjspEfyCni+PAdc5Co6AH/2fAXRbQNQZmyPvwpdaH8bvAJy54xGhzc 7TkS/c2l3QQ5TQJV5560d6ibGfgh5BtpawSBs2rUC4Sg9c37sZN30ywURuSy7s7QeTKx bn5mWXZMKjCUUrOyeyD5qq1NYI1cxuy8E3WvWkG9D53UPy93bjH7vbbFddOcDxI29Hbj 2FeJwr+5SJgcK7tRrP7LJYotwCt4AoH+s+LitdpdjtEbJlsrqz/J+1rW1WGfXb6XRjQJ ktlUHEtTUlDRiNu/XI/HOah7wdttqFJu09bebpF5D9Mf1oPdbqlCjiOWYznBNvB1+6eX F9cA== MIME-Version: 1.0 X-Received: by 10.50.212.3 with SMTP id ng3mr5471743igc.43.1361887441622; Tue, 26 Feb 2013 06:04:01 -0800 (PST) Received: by 10.64.60.136 with HTTP; Tue, 26 Feb 2013 06:04:01 -0800 (PST) In-Reply-To: <1361866314.11431.23.camel@dagon.hellion.org.uk> References: <1361784654.26546.165.camel@zakaz.uk.xensource.com> <1361805642.26546.184.camel@zakaz.uk.xensource.com> <1361866314.11431.23.camel@dagon.hellion.org.uk> Date: Tue, 26 Feb 2013 09:04:01 -0500 Message-ID: From: Travis Osterman To: xen-users Cc: Ian Campbell Subject: Re: [Xen-users] pv guest fails to start after 4.2 upgrade X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: travis@wsor.net List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: 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, Feb 26, 2013 at 3:11 AM, Ian Campbell wrote: > On Mon, 2013-02-25 at 22:47 +0000, Travis Osterman wrote: >> >>> >> I also tried to take pvgrub out of the picture so I mounted the image >> >>> >> and copied my initrd and kernel to the dom0 file system and updated my >> >>> >> config with the appropriate ramdisk and kernel lines. >> >>> >> >> >>> >> Full output without pvgrub >> >>> >> http://pastebin.com/c7VWWwXk >> >>> >> >> >>> >> Which dropped me in a shell asking for my root partition (progress). >> >>> >> >>> # cat /var/log/xen/qemu-dm-prime.log >> >>> bind(unix:/var/run/xen/qmp-libxl-4): No such file or directory >> >>> chardev: opening backend "socket" failed: No such file or directory >> >>> >> >>> # ls /var/run/xen* >> >>> /var/run/xenconsoled.pid /var/run/xenstored.pid >> >>> >> >>> /var/run/xenstored: >> >>> socket socket_ro >> >> >> >> Ah, you are missing the /var/run/xen/ directory so it is failing to >> >> create the socket, if you create the directory does it work? Although >> >> even if so it is obviously still a bug that libxl doesn't handle that >> >> error... >> > >> > Ian, >> > >> > I can confirm the manually creating /var/run/xen fixes the problem. I >> > updated my bug report here >> > https://bugs.gentoo.org/show_bug.cgi?id=459082 >> > >> > Thank you for the help. >> > >> >> Similar error not solved by the above on a domain using pygrub (pvgrub works) >> >> /var/log/xen/qemu-dm-domain.log >> /var/tmp/portage/app-emulation/xen-tools-4.1.1-r6/work/xen-4.1.1/tools/ioemu-qemu-xen/hw/xen_blktap. >> c:628: Init blktap pipes >> Could not open /var/run/tap/qemu-read-2 > > Do you have /var/run/tap ? > > I'm a bit surprised to see the qemu tap support getting activated, I > didn't think it was used for anything there days. > > Ian. > > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xen.org > http://lists.xen.org/xen-users I didn't have it, but created the directory as before. That didn't seem to fix things this time. I'm not familar with tap but here are the open tap libraries on my system currently. # lsof | grep -i tap xl 8451 root mem REG 253,0 30400 1462266 /usr/lib64/libblktapctl.so.1.0.0 xl 8451 8452 root mem REG 253,0 30400 1462266 /usr/lib64/libblktapctl.so.1.0.0 xl 18198 root mem REG 253,0 30400 1462266 /usr/lib64/libblktapctl.so.1.0.0 xl 18198 18199 root mem REG 253,0 30400 1462266 /usr/lib64/libblktapctl.so.1.0.0 qemu-dm 18580 root mem REG 253,0 18152 1462242 /usr/lib64/libblktap.so.3.0.0 qemu-dm 18580 18582 root mem REG 253,0 18152 1462242 /usr/lib64/libblktap.so.3.0.0 qemu-dm 18580 18583 root mem REG 253,0 18152 1462242 /usr/lib64/libblktap.so.3.0.0 xl 18671 root mem REG 253,0 30400 1462266 /usr/lib64/libblktapctl.so.1.0.0 xl 18671 18672 root mem REG 253,0 30400 1462266 /usr/lib64/libblktapctl.so.1.0.0 The 4.2 series of ebuilds really did a number on my setup (which had been previously working in 4.1). Here is the summary of changes I've noticed with the upgrade: pvgrub + file:/*.img: mkdir /var/run/xen does not get created so added a script to /etc/local.d as workaround (fixes) and didn't need /var/run/tap created pygrub + file:/*.img:also seems to want /var/run/tap, after creating that, still no xvda. I didnt' get a chance to troubleshoot that any further as I wasn't home last evening and wanted to leave the domain up with /dev/loop hvm + file:/*.img: a windows domain would no boot normally even after the above directories were created /var/log/*dm*.log Using xvda for guest's hda Strip off blktap sub-type prefix to /tank/xen/dev/winxp.img (drv 'aio') Using file /tank/xen/dev/winxp.img in read-write mode That looks like the disk was being loaded fine. I was able to log in via safe mode and found the gplpv drivers wouldn't load (which worked fine in 4.1). I'm getting around the pygrub and hvm currently by manually creating /dev/loop devices and using phy:/dev/loop in my disk config line. I'll try to give some more debug information later. I'm not sure if others are having problems but wish 4.2 hadn't been unmasked in portage quite yet. -- T _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Tue Feb 26 14:56:49 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 26 Feb 2013 14:56: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 1UALwe-0004GG-Mn; Tue, 26 Feb 2013 14:55:52 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UALwd-0004GB-Kg for xen-users@lists.xen.org; Tue, 26 Feb 2013 14:55:51 +0000 Received: from [85.158.137.99:21655] by server-12.bemta-3.messagelabs.com id 00/A0-05889-6FCCC215; Tue, 26 Feb 2013 14:55:50 +0000 X-Env-Sender: Ian.Campbell@citrix.com X-Msg-Ref: server-11.tower-217.messagelabs.com!1361890544!17333870!1 X-Originating-IP: [46.33.159.39] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNDYuMzMuMTU5LjM5ID0+IDI0MTk1\n X-StarScan-Received: X-StarScan-Version: 6.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 31845 invoked from network); 26 Feb 2013 14:55:45 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (46.33.159.39) by server-11.tower-217.messagelabs.com with RC4-SHA encrypted SMTP; 26 Feb 2013 14:55:45 -0000 X-IronPort-AV: E=Sophos;i="4.84,740,1355097600"; d="scan'208";a="1905969" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 26 Feb 2013 14:55: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.297.1; Tue, 26 Feb 2013 14:55:44 +0000 Message-ID: <1361890542.26546.298.camel@zakaz.uk.xensource.com> From: Ian Campbell To: "travis@wsor.net" Date: Tue, 26 Feb 2013 14:55:42 +0000 In-Reply-To: References: <1361784654.26546.165.camel@zakaz.uk.xensource.com> <1361805642.26546.184.camel@zakaz.uk.xensource.com> <1361866314.11431.23.camel@dagon.hellion.org.uk> Organization: Citrix Systems, Inc. X-Mailer: Evolution 3.4.4-1 MIME-Version: 1.0 Cc: xen-users Subject: Re: [Xen-users] pv guest fails to start after 4.2 upgrade X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: 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, 2013-02-26 at 14:04 +0000, Travis Osterman wrote: > > I'm a bit surprised to see the qemu tap support getting activated, I > > didn't think it was used for anything there days. > I didn't have it, but created the directory as before. That didn't > seem to fix things this time. I'm not familar with tap but here are > the open tap libraries on my system currently. So I asked around and there is basically no way the qemu-xen-trad blktap module should be active for any reason in a Xen 4.2 system with xl. That is the deadest of dead code... Could you send a full set of logs (xl -vvv create, /var/log/xen/*) and your guest config for this new issue please. Ian. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Tue Feb 26 14:56:49 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 26 Feb 2013 14:56: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 1UALwe-0004GG-Mn; Tue, 26 Feb 2013 14:55:52 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UALwd-0004GB-Kg for xen-users@lists.xen.org; Tue, 26 Feb 2013 14:55:51 +0000 Received: from [85.158.137.99:21655] by server-12.bemta-3.messagelabs.com id 00/A0-05889-6FCCC215; Tue, 26 Feb 2013 14:55:50 +0000 X-Env-Sender: Ian.Campbell@citrix.com X-Msg-Ref: server-11.tower-217.messagelabs.com!1361890544!17333870!1 X-Originating-IP: [46.33.159.39] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNDYuMzMuMTU5LjM5ID0+IDI0MTk1\n X-StarScan-Received: X-StarScan-Version: 6.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 31845 invoked from network); 26 Feb 2013 14:55:45 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (46.33.159.39) by server-11.tower-217.messagelabs.com with RC4-SHA encrypted SMTP; 26 Feb 2013 14:55:45 -0000 X-IronPort-AV: E=Sophos;i="4.84,740,1355097600"; d="scan'208";a="1905969" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 26 Feb 2013 14:55: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.297.1; Tue, 26 Feb 2013 14:55:44 +0000 Message-ID: <1361890542.26546.298.camel@zakaz.uk.xensource.com> From: Ian Campbell To: "travis@wsor.net" Date: Tue, 26 Feb 2013 14:55:42 +0000 In-Reply-To: References: <1361784654.26546.165.camel@zakaz.uk.xensource.com> <1361805642.26546.184.camel@zakaz.uk.xensource.com> <1361866314.11431.23.camel@dagon.hellion.org.uk> Organization: Citrix Systems, Inc. X-Mailer: Evolution 3.4.4-1 MIME-Version: 1.0 Cc: xen-users Subject: Re: [Xen-users] pv guest fails to start after 4.2 upgrade X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: 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, 2013-02-26 at 14:04 +0000, Travis Osterman wrote: > > I'm a bit surprised to see the qemu tap support getting activated, I > > didn't think it was used for anything there days. > I didn't have it, but created the directory as before. That didn't > seem to fix things this time. I'm not familar with tap but here are > the open tap libraries on my system currently. So I asked around and there is basically no way the qemu-xen-trad blktap module should be active for any reason in a Xen 4.2 system with xl. That is the deadest of dead code... Could you send a full set of logs (xl -vvv create, /var/log/xen/*) and your guest config for this new issue please. Ian. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Tue Feb 26 17:15:22 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 26 Feb 2013 17:15: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 1UAO6S-0003Rg-AB; Tue, 26 Feb 2013 17:14:08 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UAO6Q-0003RJ-Lc for xen-users@lists.xen.org; Tue, 26 Feb 2013 17:14:07 +0000 Received: from [85.158.139.83:13438] by server-16.bemta-5.messagelabs.com id BB/DD-02543-E5DEC215; Tue, 26 Feb 2013 17:14:06 +0000 X-Env-Sender: thelists@gmail.com X-Msg-Ref: server-15.tower-182.messagelabs.com!1361898841!28933949!1 X-Originating-IP: [209.85.160.51] 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.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 32248 invoked from network); 26 Feb 2013 17:14:03 -0000 Received: from mail-pb0-f51.google.com (HELO mail-pb0-f51.google.com) (209.85.160.51) by server-15.tower-182.messagelabs.com with RC4-SHA encrypted SMTP; 26 Feb 2013 17:14:03 -0000 Received: by mail-pb0-f51.google.com with SMTP id un15so2478372pbc.10 for ; Tue, 26 Feb 2013 09:14:01 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:date:message-id:subject:from:to :content-type; bh=VnKRsWNH3rt02Z99lUc4NQiv3eDxq3zT1Hq/zoMjaNM=; b=HkM4oiONC9jDcMAVTsWNvg7VGjuuxH15MptxraR54ORODJFvIPTtCHAhQbRONnzOVc qZ1mKGN2euiNhfPmVqT85VZG+2c7c74trqMmvLUfus3jRIq+Hj63KeVWXMkxFpdrUkmw AP6ITzrEcpPM6hMdnFMpt1AfkJBEANnN35tHTjajFVzdB71K4RJU/B+IcKyGWQrMdHiZ LNPt+Xq4/GBYu+ARLqGIzjHjFQCHQeCBeo+MG7BVcZ3D7Qdu+jTY1HDZ1KA9BRkxhOyi h7cPa8jZETRPGXmwCnHLnmPqXYgHDG61ipMLIVVz5LHWh9AZ0PDLNdWgkfmHiflIahz7 f05w== MIME-Version: 1.0 X-Received: by 10.66.27.169 with SMTP id u9mr2644245pag.197.1361898841326; Tue, 26 Feb 2013 09:14:01 -0800 (PST) Received: by 10.68.204.66 with HTTP; Tue, 26 Feb 2013 09:14:01 -0800 (PST) Date: Tue, 26 Feb 2013 12:14:01 -0500 Message-ID: From: mailing lists To: xen-users@lists.xen.org Subject: [Xen-users] Dom0 OOM, page allocation failure X-BeenThere: xen-users@lists.xen.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="===============3162068003129592651==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============3162068003129592651== Content-Type: multipart/alternative; boundary=bcaec52becf1a850b904d6a3c849 --bcaec52becf1a850b904d6a3c849 Content-Type: text/plain; charset=ISO-8859-1 Hello, I'm running into some trouble with what appear on the surface to be OOM issues in Dom0, but I'm not seeing any other evidence. This typically happens during periods of high I/O, and has occurred during RAID initial sync, and mkfs.ext4ing (as a test, no intention to keep ext4 on this array). I've found some older posts citing very similar circumstances, however they all seem to be resolved with an updated kernel in the 2.6 tree. There was one post on a Linode board which made reference to the issue being resolved for only 32-bit Dom0s. Otherwise, I'm fairly stuck. Information below regarding HW / SW of my configuration, as well as the lines from dmesg from the start of the issue until current. Also, I have two very similar systems with the exact same software (but differing hardware), however the problem only occurs for me on the machine below. The biggest difference between the two machines is that one that fails (Box A) has 10 x 2TB drives, while the one that did not has only 6 x 750GB drives. Finally, without the Xen loaded (booting directly to kernel 3.7.8+), I do not see the errors. Any insight would be appreciated! The setup; Hardware: Processor: Intel Xeon E5-1650 RAM: 56GB total (memtests clean) System drive: 32GB SSD -- 4GB swap on the SSD Storage drives: 10 x 2TB drives in a software RAID-6 array (mdadm --create /dev/md0 -l6 -n10 -x0 /dev/sd[bcdefghijk]) Software: OS: Centos 6.3, 64-bit Kernel: 3.7.8 Xen: 4.2.1 Grub boot line: title CentOS (3.7.8+) root (hd0,0) kernel /xen-4.2.1.gz dummy=dummy dom0_mem=4096M noreboot module /vmlinuz-3.7.8+ dummy=dummy nopat root=/dev/mapper/vg_xxxx-lv_root nomodeset rd_NO_LUKS LANG=en_US.UTF-8 rd_LVM_LV=vg_xxxx/lv_swap SYSFONT=latarcyrheb-sun16 crashkernel=auto rd_LVM_LV=vg_xxxx/lv_root KEYBOARDTYPE=pc KEYTABLE=us rd_NO_DM rhgb showopts console=tty0 module /initrd-3.7.8+.img Memory status immediately following issue: free -m total used free shared buffers cached Mem: 3115 2420 695 0 34 29 -/+ buffers/cache: 2356 758 Swap: 4095 24 4071 Error logs: kernel: md127_raid6: page allocation failure: order:0, mode:0x200000 kernel: Pid: 623, comm: md127_raid6 Not tainted 3.7.8+ #7 kernel: Call Trace: kernel: [] warn_alloc_failed+0xf3/0x140 kernel: [] __alloc_pages_slowpath+0x4b0/0x7b0 kernel: [] ? __alloc_pages_slowpath+0x4b0/0x7b0 kernel: [] __alloc_pages_nodemask+0x21a/0x230 kernel: [] ? __alloc_pages_nodemask+0x21a/0x230 kernel: [] kmem_getpages+0x64/0x190 kernel: [] fallback_alloc+0x197/0x260 kernel: [] ____cache_alloc_node+0x9a/0x160 kernel: [] kmem_cache_alloc+0x12b/0x230 kernel: [] ? dma_pool_alloc+0xc7/0xf0 kernel: [] ioat2_alloc_ring_ent+0x64/0xc0 [ioatdma] kernel: [] reshape_ring+0x143/0x350 [ioatdma] kernel: [] ioat2_check_space_lock+0xe7/0x220 [ioatdma] kernel: [] ioat2_dma_prep_memcpy_lock+0x61/0x270 [ioatdma] kernel: [] async_memcpy+0x20b/0x2c4 [async_memcpy] kernel: [] async_copy_data+0x9d/0x150 [raid456] kernel: [] ops_run_biodrain+0x198/0x1d0 [raid456] kernel: [] __raid_run_ops+0x4e8/0x660 [raid456] kernel: [] ? ops_run_io+0x29/0x740 [raid456] kernel: [] ? handle_stripe_dirtying+0x335/0x450 [raid456] kernel: [] handle_stripe+0x903/0xec0 [raid456] kernel: [] ? pvclock_clocksource_read+0x58/0xd0 kernel: [] handle_active_stripes+0x19a/0x280 [raid456] kernel: [] raid5d+0x1f8/0x350 [raid456] kernel: [] ? xen_clocksource_read+0x20/0x30 kernel: [] ? _raw_spin_unlock_irqrestore+0x1e/0x30 kernel: [] md_thread+0x117/0x150 kernel: [] ? wake_up_bit+0x40/0x40 kernel: [] ? md_rdev_init+0x110/0x110 kernel: [] kthread+0xce/0xe0 kernel: [] ? xen_end_context_switch+0x1e/0x30 kernel: [] ? kthread_freezable_should_stop+0x70/0x70 kernel: [] ret_from_fork+0x7c/0xb0 kernel: [] ? kthread_freezable_should_stop+0x70/0x70 kernel: Mem-Info: kernel: Node 0 DMA per-cpu: kernel: CPU 0: hi: 0, btch: 1 usd: 0 kernel: CPU 1: hi: 0, btch: 1 usd: 0 kernel: CPU 2: hi: 0, btch: 1 usd: 0 kernel: CPU 3: hi: 0, btch: 1 usd: 0 kernel: CPU 4: hi: 0, btch: 1 usd: 0 kernel: CPU 5: hi: 0, btch: 1 usd: 0 kernel: CPU 6: hi: 0, btch: 1 usd: 0 kernel: CPU 7: hi: 0, btch: 1 usd: 0 kernel: Node 0 DMA32 per-cpu: kernel: CPU 0: hi: 186, btch: 31 usd: 0 kernel: CPU 1: hi: 186, btch: 31 usd: 0 kernel: CPU 2: hi: 186, btch: 31 usd: 13 kernel: CPU 3: hi: 186, btch: 31 usd: 0 kernel: CPU 4: hi: 186, btch: 31 usd: 30 kernel: CPU 5: hi: 186, btch: 31 usd: 0 kernel: CPU 6: hi: 186, btch: 31 usd: 0 kernel: CPU 7: hi: 186, btch: 31 usd: 0 kernel: Node 0 Normal per-cpu: kernel: CPU 0: hi: 186, btch: 31 usd: 0 kernel: CPU 1: hi: 186, btch: 31 usd: 0 kernel: CPU 2: hi: 186, btch: 31 usd: 0 kernel: CPU 3: hi: 186, btch: 31 usd: 0 kernel: CPU 4: hi: 186, btch: 31 usd: 30 kernel: CPU 5: hi: 186, btch: 31 usd: 0 kernel: CPU 6: hi: 186, btch: 31 usd: 0 kernel: CPU 7: hi: 186, btch: 31 usd: 0 kernel: active_anon:26829 inactive_anon:8320 isolated_anon:0 kernel: active_file:17836 inactive_file:422075 isolated_file:0 kernel: unevictable:1 dirty:3843 writeback:84236 unstable:0 kernel: free:64174 slab_reclaimable:14968 slab_unreclaimable:35363 kernel: mapped:3896 shmem:77 pagetables:2034 bounce:0 kernel: free_cma:0 kernel: Node 0 DMA free:15836kB min:8kB low:8kB high:12kB active_anon:0kB inactive_anon:0kB active_file:0kB inactive_file:0kB unevictable:0kB isolated(anon):0kB isolated(file):0kB present:15612kB mlocked:0kB dirty:0kB writeback:0kB mapped:0kB shmem:0kB slab_reclaimable:0kB slab_unreclaimable:0kB kernel_stack:0kB pagetables:0kB unstable:0kB bounce:0kB free_cma:0kB writeback_tmp:0kB pages_scanned:0 all_unreclaimable? yes kernel: lowmem_reserve[]: 0 1948 56488 56488 kernel: Node 0 DMA32 free:218864kB min:1048kB low:1308kB high:1572kB active_anon:97264kB inactive_anon:32512kB active_file:29592kB inactive_file:1492496kB unevictable:0kB isolated(anon):0kB isolated(file):0kB present:1995492kB mlocked:0kB dirty:13532kB writeback:142000kB mapped:40kB shmem:0kB slab_reclaimable:22544kB slab_unreclaimable:22616kB kernel_stack:16kB pagetables:1128kB unstable:0kB bounce:0kB free_cma:0kB writeback_tmp:0kB pages_scanned:0 all_unreclaimable? no kernel: lowmem_reserve[]: 0 0 54540 54540 kernel: Node 0 Normal free:21996kB min:29364kB low:36704kB high:44044kB active_anon:10052kB inactive_anon:768kB active_file:41752kB inactive_file:195804kB unevictable:4kB isolated(anon):0kB isolated(file):0kB present:55848960kB mlocked:4kB dirty:1840kB writeback:194944kB mapped:15544kB shmem:308kB slab_reclaimable:37328kB slab_unreclaimable:118836kB kernel_stack:2040kB pagetables:7008kB unstable:0kB bounce:0kB free_cma:0kB writeback_tmp:0kB pages_scanned:0 all_unreclaimable? no kernel: lowmem_reserve[]: 0 0 0 0 kernel: Node 0 DMA: 1*4kB 1*8kB 1*16kB 0*32kB 1*64kB 1*128kB 1*256kB 0*512kB 1*1024kB 1*2048kB 3*4096kB = 15836kB kernel: Node 0 DMA32: 2474*4kB 1928*8kB 1171*16kB 597*32kB 415*64kB 181*128kB 100*256kB 61*512kB 30*1024kB 9*2048kB 0*4096kB = 218872kB kernel: Node 0 Normal: 3589*4kB 608*8kB 0*16kB 1*32kB 0*64kB 1*128kB 1*256kB 1*512kB 1*1024kB 1*2048kB 0*4096kB = 23220kB kernel: 444756 total pagecache pages kernel: 4704 pages in swap cache kernel: Swap cache stats: add 130487, delete 125783, find 902/1215 kernel: Free swap = 3684144kB kernel: Total swap = 4194300kB kernel: 14680048 pages RAM kernel: 13882525 pages reserved kernel: 1271965 pages shared kernel: 282031 pages non-shared kernel: SLAB: Unable to allocate memory on node 0 (gfp=0x0) kernel: cache: ioat2, object size: 128, order: 0 kernel: node 0: slabs: 6672/6672, objs: 200160/200160, free: 0 kernel: md127_raid6: page allocation failure: order:0, mode:0x0 kernel: Pid: 623, comm: md127_raid6 Not tainted 3.7.8+ #7 kernel: Call Trace: kernel: [] warn_alloc_failed+0xf3/0x140 kernel: [] ? __wake_up+0x53/0x70 kernel: [] __alloc_pages_slowpath+0x4b0/0x7b0 kernel: [] __alloc_pages_nodemask+0x21a/0x230 kernel: [] alloc_pages_current+0xb6/0x120 kernel: [] __get_free_pages+0xe/0x50 kernel: [] xen_swiotlb_alloc_coherent+0x51/0x180 kernel: [] ? kmem_cache_alloc_trace+0xb3/0x230 kernel: [] pool_alloc_page+0xc5/0x1d0 kernel: [] dma_pool_alloc+0x7a/0xf0 kernel: [] ioat2_alloc_ring_ent+0x3a/0xc0 [ioatdma] kernel: [] reshape_ring+0x143/0x350 [ioatdma] kernel: [] ioat2_check_space_lock+0xe7/0x220 [ioatdma] kernel: [] ? error_exit+0x2a/0x60 kernel: [] ioat2_dma_prep_memcpy_lock+0x61/0x270 [ioatdma] kernel: [] async_memcpy+0x20b/0x2c4 [async_memcpy] kernel: [] async_copy_data+0x9d/0x150 [raid456] kernel: [] ops_run_biodrain+0x198/0x1d0 [raid456] kernel: [] __raid_run_ops+0x4e8/0x660 [raid456] kernel: [] ? ops_run_io+0x29/0x740 [raid456] kernel: [] ? schedule_reconstruction+0x68/0x210 [raid456] kernel: [] ? pvclock_clocksource_read+0x58/0xd0 kernel: [] ? handle_stripe_dirtying+0x335/0x450 [raid456] kernel: [] handle_stripe+0x903/0xec0 [raid456] kernel: [] ? xen_hypercall_xen_version+0xa/0x20 kernel: [] ? pvclock_clocksource_read+0x58/0xd0 kernel: [] handle_active_stripes+0x19a/0x280 [raid456] kernel: [] raid5d+0x1f8/0x350 [raid456] kernel: [] ? xen_clocksource_read+0x20/0x30 kernel: [] ? _raw_spin_unlock_irqrestore+0x1e/0x30 kernel: [] md_thread+0x117/0x150 kernel: [] ? wake_up_bit+0x40/0x40 kernel: [] ? md_rdev_init+0x110/0x110 kernel: [] kthread+0xce/0xe0 kernel: [] ? xen_end_context_switch+0x1e/0x30 kernel: [] ? kthread_freezable_should_stop+0x70/0x70 kernel: [] ret_from_fork+0x7c/0xb0 kernel: [] ? kthread_freezable_should_stop+0x70/0x70 kernel: Mem-Info: kernel: Node 0 DMA per-cpu: kernel: CPU 0: hi: 0, btch: 1 usd: 0 kernel: CPU 1: hi: 0, btch: 1 usd: 0 kernel: CPU 2: hi: 0, btch: 1 usd: 0 kernel: CPU 3: hi: 0, btch: 1 usd: 0 kernel: CPU 4: hi: 0, btch: 1 usd: 0 kernel: CPU 5: hi: 0, btch: 1 usd: 0 kernel: CPU 6: hi: 0, btch: 1 usd: 0 kernel: CPU 7: hi: 0, btch: 1 usd: 0 kernel: Node 0 DMA32 per-cpu: kernel: CPU 0: hi: 186, btch: 31 usd: 65 kernel: CPU 1: hi: 186, btch: 31 usd: 0 kernel: CPU 2: hi: 186, btch: 31 usd: 170 kernel: CPU 3: hi: 186, btch: 31 usd: 1 kernel: CPU 4: hi: 186, btch: 31 usd: 65 kernel: CPU 5: hi: 186, btch: 31 usd: 82 kernel: CPU 6: hi: 186, btch: 31 usd: 34 kernel: CPU 7: hi: 186, btch: 31 usd: 54 kernel: Node 0 Normal per-cpu: kernel: CPU 0: hi: 186, btch: 31 usd: 30 kernel: CPU 1: hi: 186, btch: 31 usd: 0 kernel: CPU 2: hi: 186, btch: 31 usd: 160 kernel: CPU 3: hi: 186, btch: 31 usd: 22 kernel: CPU 4: hi: 186, btch: 31 usd: 55 kernel: CPU 5: hi: 186, btch: 31 usd: 57 kernel: CPU 6: hi: 186, btch: 31 usd: 15 kernel: CPU 7: hi: 186, btch: 31 usd: 15 kernel: active_anon:6981 inactive_anon:2555 isolated_anon:0 kernel: active_file:17876 inactive_file:94621 isolated_file:0 kernel: unevictable:1 dirty:38 writeback:94542 unstable:0 kernel: free:64120 slab_reclaimable:7901 slab_unreclaimable:279561 kernel: mapped:3873 shmem:57 pagetables:2028 bounce:0 kernel: free_cma:0 kernel: Node 0 DMA free:15836kB min:8kB low:8kB high:12kB active_anon:0kB inactive_anon:0kB active_file:0kB inactive_file:0kB unevictable:0kB isolated(anon):0kB isolated(file):0kB present:15612kB mlocked:0kB dirty:0kB writeback:0kB mapped:0kB shmem:0kB slab_reclaimable:0kB slab_unreclaimable:0kB kernel_stack:0kB pagetables:0kB unstable:0kB bounce:0kB free_cma:0kB writeback_tmp:0kB pages_scanned:0 all_unreclaimable? yes kernel: lowmem_reserve[]: 0 1948 56488 56488 kernel: Node 0 DMA32 free:218900kB min:1048kB low:1308kB high:1572kB active_anon:27660kB inactive_anon:9832kB active_file:29652kB inactive_file:243504kB unevictable:0kB isolated(anon):0kB isolated(file):0kB present:1995492kB mlocked:0kB dirty:152kB writeback:243344kB mapped:212kB shmem:172kB slab_reclaimable:9528kB slab_unreclaimable:939408kB kernel_stack:32kB pagetables:1148kB unstable:0kB bounce:0kB free_cma:0kB writeback_tmp:0kB pages_scanned:50103 all_unreclaimable? no kernel: lowmem_reserve[]: 0 0 54540 54540 kernel: Node 0 Normal free:21744kB min:29364kB low:36704kB high:44044kB active_anon:264kB inactive_anon:388kB active_file:41852kB inactive_file:134980kB unevictable:4kB isolated(anon):0kB isolated(file):0kB present:55848960kB mlocked:4kB dirty:0kB writeback:134824kB mapped:15280kB shmem:56kB slab_reclaimable:22076kB slab_unreclaimable:178836kB kernel_stack:2032kB pagetables:6964kB unstable:0kB bounce:0kB free_cma:0kB writeback_tmp:0kB pages_scanned:289419 all_unreclaimable? yes kernel: lowmem_reserve[]: 0 0 0 0 kernel: Node 0 DMA: 1*4kB 1*8kB 1*16kB 0*32kB 1*64kB 1*128kB 1*256kB 0*512kB 1*1024kB 1*2048kB 3*4096kB = 15836kB kernel: Node 0 DMA32: 3280*4kB 2835*8kB 1386*16kB 551*32kB 315*64kB 183*128kB 105*256kB 64*512kB 37*1024kB 1*2048kB 0*4096kB = 218776kB kernel: Node 0 Normal: 4468*4kB 0*8kB 0*16kB 1*32kB 2*64kB 1*128kB 0*256kB 1*512kB 1*1024kB 1*2048kB 0*4096kB = 21744kB kernel: 114447 total pagecache pages kernel: 1877 pages in swap cache kernel: Swap cache stats: add 158328, delete 156451, find 3052/3981 kernel: Free swap = 3593000kB kernel: Total swap = 4194300kB kernel: 14680048 pages RAM kernel: 13882525 pages reserved kernel: 943705 pages shared kernel: 608751 pages non-shared init: tty (/dev/tty2) main process ended, respawning init: tty (/dev/tty2) main process ended, respawning Thanks, Bill --bcaec52becf1a850b904d6a3c849 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Hello,

I'm running into some trouble with what appea= r on the surface to be OOM issues in Dom0, but I'm not seeing any other= evidence. =A0This typically happens during periods of high I/O, and has oc= curred during RAID initial sync, and mkfs.ext4ing (as a test, no intention = to keep ext4 on this array). =A0I've found some older posts citing very= similar circumstances, however they all seem to be resolved with an update= d kernel in the 2.6 tree. =A0There was one post on a Linode board which mad= e reference to the issue being resolved for only 32-bit Dom0s. =A0Otherwise= , I'm fairly stuck. =A0Information below regarding HW / SW of my config= uration, as well as the lines from dmesg from the start of the issue until = current.

Also, I have two very similar systems with the exact sa= me software (but differing hardware), however the problem only occurs for m= e on the machine below. =A0The biggest difference between the two machines = is that one that fails (Box A) has 10 x 2TB drives, while the one that did = not has only 6 x 750GB drives. =A0Finally, without the Xen loaded (booting = directly to kernel 3.7.8+), I do not see the errors.

Any insight would be appreciated!

<= div>The setup;
Hardware:
=A0 Processor: Intel Xeon E5-1= 650
=A0 RAM: 56GB total (memtests clean)
=A0 System dri= ve: 32GB SSD
=A0 -- 4GB swap on the SSD
=A0 Storage drives: 10 x 2TB driv= es in a software RAID-6 array (mdadm --create /dev/md0 -l6 -n10 -x0 /dev/sd= [bcdefghijk])

Software:
=A0 OS: Centos 6= .3, 64-bit
=A0 Kernel: 3.7.8
=A0 Xen: 4.2.1
=A0=A0
=

Grub boot line:
=A0 title Cent= OS (3.7.8+)
=A0 =A0 =A0 =A0 =A0 root (hd0,0)
=A0 =A0 = =A0 =A0 =A0 kernel /xen-4.2.1.gz dummy=3Ddummy dom0_mem=3D4096M noreboot
=A0 =A0 =A0 =A0 =A0 module /vmlinuz-3.7.8+ dummy=3Ddummy nopat root=3D= /dev/mapper/vg_xxxx-lv_root nomodeset rd_NO_LUKS LANG=3Den_US.UTF-8 rd_LVM_= LV=3Dvg_xxxx/lv_swap =A0 SYSFONT=3Dlatarcyrheb-sun16 crashkernel=3Dauto rd_= LVM_LV=3Dvg_xxxx/lv_root =A0KEYBOARDTYPE=3Dpc KEYTABLE=3Dus rd_NO_DM rhgb s= howopts console=3Dtty0
=A0 =A0 =A0 =A0 =A0 module /initrd-3.7.8+.img

Memory status immediately following issue:
=A0 free -= m
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0total =A0 =A0 =A0 used =A0 =A0 = =A0 free =A0 =A0 shared =A0 =A0buffers =A0 =A0 cached
=A0 Mem: =A0 =A0 =A0 =A0 =A03115 =A0 =A0 =A0 2420 =A0 =A0 =A0 =A0695 = =A0 =A0 =A0 =A0 =A00 =A0 =A0 =A0 =A0 34 =A0 =A0 =A0 =A0 29
=A0 -/= + buffers/cache: =A0 =A0 =A0 2356 =A0 =A0 =A0 =A0758
=A0 Swap: = =A0 =A0 =A0 =A0 4095 =A0 =A0 =A0 =A0 24 =A0 =A0 =A0 4071

Error logs:
kernel: md127_raid6: page allocation = failure: order:0, mode:0x200000
kernel: Pid: 623, comm: md127_rai= d6 Not tainted 3.7.8+ #7
kernel: Call Trace:
kernel: [&= lt;ffffffff81117a93>] warn_alloc_failed+0xf3/0x140
kernel: [<ffffffff8111aa90>] __alloc_pages_slowpath+0x4b0/0x7b0<= /div>
kernel: [<ffffffff8111aa90>] ? __alloc_pages_slowpath+0x4b0= /0x7b0
kernel: [<ffffffff8111afaa>] __alloc_pages_nodemask+= 0x21a/0x230
kernel: [<ffffffff8111afaa>] ? __alloc_pages_nodemask+0x21a/0x23= 0
kernel: [<ffffffff8115c9d4>] kmem_getpages+0x64/0x190
kernel: [<ffffffff8115d787>] fallback_alloc+0x197/0x260
kernel: [<ffffffff8115d52a>] ____cache_alloc_node+0x9a/0x160
kernel: [<ffffffff8115defb>] kmem_cache_alloc+0x12b/0x230
kernel: [<ffffffff81150907>] ? dma_pool_alloc+0xc7/0xf0
kernel: [<ffffffffa018bea4>] ioat2_alloc_ring_ent+0x64/0xc0 [ioa= tdma]
kernel: [<ffffffffa018c043>] reshape_ring+0x143/0x350= [ioatdma]
kernel: [<ffffffffa018c337>] ioat2_check_space_l= ock+0xe7/0x220 [ioatdma]
kernel: [<ffffffffa018c4d1>] ioat2_dma_prep_memcpy_lock+0x61/0x2= 70 [ioatdma]
kernel: [<ffffffffa002720b>] async_memcpy+0x20= b/0x2c4 [async_memcpy]
kernel: [<ffffffffa00e34dd>] async_c= opy_data+0x9d/0x150 [raid456]
kernel: [<ffffffffa00e3728>] ops_run_biodrain+0x198/0x1d0 [raid4= 56]
kernel: [<ffffffffa00e4688>] __raid_run_ops+0x4e8/0x660= [raid456]
kernel: [<ffffffffa00e81a9>] ? ops_run_io+0x29/0= x740 [raid456]
kernel: [<ffffffffa00e1685>] ? handle_stripe_dirtying+0x335/0x45= 0 [raid456]
kernel: [<ffffffffa00e91c3>] handle_stripe+0x90= 3/0xec0 [raid456]
kernel: [<ffffffff81044298>] ? pvclock_cl= ocksource_read+0x58/0xd0
kernel: [<ffffffffa00e9afa>] handle_active_stripes+0x19a/0x280 [= raid456]
kernel: [<ffffffffa00e9dd8>] raid5d+0x1f8/0x350 [r= aid456]
kernel: [<ffffffff8100a350>] ? xen_clocksource_read= +0x20/0x30
kernel: [<ffffffff8156d23e>] ? _raw_spin_unlock_irqrestore+0x1e/= 0x30
kernel: [<ffffffff8144e5f7>] md_thread+0x117/0x150
kernel: [<ffffffff810789e0>] ? wake_up_bit+0x40/0x40
kernel: [<ffffffff8144e4e0>] ? md_rdev_init+0x110/0x110
kernel: [<ffffffff8107828e>] kthread+0xce/0xe0
kernel: [&= lt;ffffffff8100382e>] ? xen_end_context_switch+0x1e/0x30
kerne= l: [<ffffffff810781c0>] ? kthread_freezable_should_stop+0x70/0x70
kernel: [<ffffffff81575cec>] ret_from_fork+0x7c/0xb0
k= ernel: [<ffffffff810781c0>] ? kthread_freezable_should_stop+0x70/0x70=
kernel: Mem-Info:
kernel: Node 0 DMA per-cpu:
kernel: CPU =A0 =A00: hi: =A0 =A00, btch: =A0 1 usd: =A0 0
k= ernel: CPU =A0 =A01: hi: =A0 =A00, btch: =A0 1 usd: =A0 0
kernel:= CPU =A0 =A02: hi: =A0 =A00, btch: =A0 1 usd: =A0 0
kernel: CPU = =A0 =A03: hi: =A0 =A00, btch: =A0 1 usd: =A0 0
kernel: CPU =A0 =A04: hi: =A0 =A00, btch: =A0 1 usd: =A0 0
k= ernel: CPU =A0 =A05: hi: =A0 =A00, btch: =A0 1 usd: =A0 0
kernel:= CPU =A0 =A06: hi: =A0 =A00, btch: =A0 1 usd: =A0 0
kernel: CPU = =A0 =A07: hi: =A0 =A00, btch: =A0 1 usd: =A0 0
kernel: Node 0 DMA32 per-cpu:
kernel: CPU =A0 =A00: hi: =A01= 86, btch: =A031 usd: =A0 0
kernel: CPU =A0 =A01: hi: =A0186, btch= : =A031 usd: =A0 0
kernel: CPU =A0 =A02: hi: =A0186, btch: =A031 = usd: =A013
kernel: CPU =A0 =A03: hi: =A0186, btch: =A031 usd: =A0= 0
kernel: CPU =A0 =A04: hi: =A0186, btch: =A031 usd: =A030
ker= nel: CPU =A0 =A05: hi: =A0186, btch: =A031 usd: =A0 0
kernel: CPU= =A0 =A06: hi: =A0186, btch: =A031 usd: =A0 0
kernel: CPU =A0 =A0= 7: hi: =A0186, btch: =A031 usd: =A0 0
kernel: Node 0 Normal per-cpu:
kernel: CPU =A0 =A00: hi: =A0= 186, btch: =A031 usd: =A0 0
kernel: CPU =A0 =A01: hi: =A0186, btc= h: =A031 usd: =A0 0
kernel: CPU =A0 =A02: hi: =A0186, btch: =A031= usd: =A0 0
kernel: CPU =A0 =A03: hi: =A0186, btch: =A031 usd: = =A0 0
kernel: CPU =A0 =A04: hi: =A0186, btch: =A031 usd: =A030
ker= nel: CPU =A0 =A05: hi: =A0186, btch: =A031 usd: =A0 0
kernel: CPU= =A0 =A06: hi: =A0186, btch: =A031 usd: =A0 0
kernel: CPU =A0 =A0= 7: hi: =A0186, btch: =A031 usd: =A0 0
kernel: active_anon:26829 inactive_anon:8320 isolated_anon:0
kernel: active_file:17836 inactive_file:422075 isolated_file:0
k= ernel: unevictable:1 dirty:3843 writeback:84236 unstable:0
kernel= : free:64174 slab_reclaimable:14968 slab_unreclaimable:35363
kernel: mapped:3896 shmem:77 pagetables:2034 bounce:0
kernel= : free_cma:0
kernel: Node 0 DMA free:15836kB min:8kB low:8kB high= :12kB active_anon:0kB inactive_anon:0kB active_file:0kB inactive_file:0kB u= nevictable:0kB isolated(anon):0kB isolated(file):0kB present:15612kB mlocke= d:0kB dirty:0kB writeback:0kB mapped:0kB shmem:0kB slab_reclaimable:0kB sla= b_unreclaimable:0kB kernel_stack:0kB pagetables:0kB unstable:0kB bounce:0kB= free_cma:0kB writeback_tmp:0kB pages_scanned:0 all_unreclaimable? yes
kernel: lowmem_reserve[]: 0 1948 56488 56488
kernel: Node 0 = DMA32 free:218864kB min:1048kB low:1308kB high:1572kB active_anon:97264kB i= nactive_anon:32512kB active_file:29592kB inactive_file:1492496kB unevictabl= e:0kB isolated(anon):0kB isolated(file):0kB present:1995492kB mlocked:0kB d= irty:13532kB writeback:142000kB mapped:40kB shmem:0kB slab_reclaimable:2254= 4kB slab_unreclaimable:22616kB kernel_stack:16kB pagetables:1128kB unstable= :0kB bounce:0kB free_cma:0kB writeback_tmp:0kB pages_scanned:0 all_unreclai= mable? no
kernel: lowmem_reserve[]: 0 0 54540 54540
kernel: Node 0 Nor= mal free:21996kB min:29364kB low:36704kB high:44044kB active_anon:10052kB i= nactive_anon:768kB active_file:41752kB inactive_file:195804kB unevictable:4= kB isolated(anon):0kB isolated(file):0kB present:55848960kB mlocked:4kB dir= ty:1840kB writeback:194944kB mapped:15544kB shmem:308kB slab_reclaimable:37= 328kB slab_unreclaimable:118836kB kernel_stack:2040kB pagetables:7008kB uns= table:0kB bounce:0kB free_cma:0kB writeback_tmp:0kB pages_scanned:0 all_unr= eclaimable? no
kernel: lowmem_reserve[]: 0 0 0 0
kernel: Node 0 DMA: 1*4kB = 1*8kB 1*16kB 0*32kB 1*64kB 1*128kB 1*256kB 0*512kB 1*1024kB 1*2048kB 3*4096= kB =3D 15836kB
kernel: Node 0 DMA32: 2474*4kB 1928*8kB 1171*16kB = 597*32kB 415*64kB 181*128kB 100*256kB 61*512kB 30*1024kB 9*2048kB 0*4096kB = =3D 218872kB
kernel: Node 0 Normal: 3589*4kB 608*8kB 0*16kB 1*32kB 0*64kB 1*128kB 1= *256kB 1*512kB 1*1024kB 1*2048kB 0*4096kB =3D 23220kB
kernel: 444= 756 total pagecache pages
kernel: 4704 pages in swap cache
kernel: Swap cache stats: add 130487, delete 125783, find 902/1215
kernel: Free swap =A0=3D 3684144kB
kernel: Total swap =3D = 4194300kB
kernel: 14680048 pages RAM
kernel: 13882525 p= ages reserved
kernel: 1271965 pages shared
kernel: 282031 pages non-shared=
kernel: SLAB: Unable to allocate memory on node 0 (gfp=3D0x0)
kernel: =A0cache: ioat2, object size: 128, order: 0
kerne= l: =A0node 0: slabs: 6672/6672, objs: 200160/200160, free: 0
kernel: md127_raid6: page allocation failure: order:0, mode:0x0
<= div>kernel: Pid: 623, comm: md127_raid6 Not tainted 3.7.8+ #7
ker= nel: Call Trace:
kernel: [<ffffffff81117a93>] warn_alloc_fa= iled+0xf3/0x140
kernel: [<ffffffff81084ea3>] ? __wake_up+0x53/0x70
ker= nel: [<ffffffff8111aa90>] __alloc_pages_slowpath+0x4b0/0x7b0
kernel: [<ffffffff8111afaa>] __alloc_pages_nodemask+0x21a/0x230
kernel: [<ffffffff811571b6>] alloc_pages_current+0xb6/0x120
kernel: [<ffffffff8111778e>] __get_free_pages+0xe/0x50
kernel: [<ffffffff8130c4e1>] xen_swiotlb_alloc_coherent+0x51/0x180<= /div>
kernel: [<ffffffff8115dc53>] ? kmem_cache_alloc_trace+0xb3/0x230=
kernel: [<ffffffff81150735>] pool_alloc_page+0xc5/0x1d0
kernel: [<ffffffff811508ba>] dma_pool_alloc+0x7a/0xf0
kernel: [<ffffffffa018be7a>] ioat2_alloc_ring_ent+0x3a/0xc0 [ioa= tdma]
kernel: [<ffffffffa018c043>] reshape_ring+0x143/0x350= [ioatdma]
kernel: [<ffffffffa018c337>] ioat2_check_space_l= ock+0xe7/0x220 [ioatdma]
kernel: [<ffffffff8156dcfa>] ? error_exit+0x2a/0x60
ke= rnel: [<ffffffffa018c4d1>] ioat2_dma_prep_memcpy_lock+0x61/0x270 [ioa= tdma]
kernel: [<ffffffffa002720b>] async_memcpy+0x20b/0x2c4= [async_memcpy]
kernel: [<ffffffffa00e34dd>] async_copy_data+0x9d/0x150 [raid456= ]
kernel: [<ffffffffa00e3728>] ops_run_biodrain+0x198/0x1d0= [raid456]
kernel: [<ffffffffa00e4688>] __raid_run_ops+0x4e= 8/0x660 [raid456]
kernel: [<ffffffffa00e81a9>] ? ops_run_io+0x29/0x740 [raid456]
kernel: [<ffffffffa00e11a8>] ? schedule_reconstruction+0x68/= 0x210 [raid456]
kernel: [<ffffffff81044298>] ? pvclock_cloc= ksource_read+0x58/0xd0
kernel: [<ffffffffa00e1685>] ? handle_stripe_dirtying+0x335/0x45= 0 [raid456]
kernel: [<ffffffffa00e91c3>] handle_stripe+0x90= 3/0xec0 [raid456]
kernel: [<ffffffff8100122a>] ? xen_hyperc= all_xen_version+0xa/0x20
kernel: [<ffffffff81044298>] ? pvclock_clocksource_read+0x58/0xd= 0
kernel: [<ffffffffa00e9afa>] handle_active_stripes+0x19a/= 0x280 [raid456]
kernel: [<ffffffffa00e9dd8>] raid5d+0x1f8/0= x350 [raid456]
kernel: [<ffffffff8100a350>] ? xen_clocksource_read+0x20/0x30
kernel: [<ffffffff8156d23e>] ? _raw_spin_unlock_irqrestore+0x= 1e/0x30
kernel: [<ffffffff8144e5f7>] md_thread+0x117/0x150<= /div>
kernel: [<ffffffff810789e0>] ? wake_up_bit+0x40/0x40
k= ernel: [<ffffffff8144e4e0>] ? md_rdev_init+0x110/0x110
kern= el: [<ffffffff8107828e>] kthread+0xce/0xe0
kernel: [<fff= fffff8100382e>] ? xen_end_context_switch+0x1e/0x30
kernel: [<ffffffff810781c0>] ? kthread_freezable_should_stop+0x7= 0/0x70
kernel: [<ffffffff81575cec>] ret_from_fork+0x7c/0xb0=
kernel: [<ffffffff810781c0>] ? kthread_freezable_should_st= op+0x70/0x70
kernel: Mem-Info:
kernel: Node 0 DMA per-cpu:
kern= el: CPU =A0 =A00: hi: =A0 =A00, btch: =A0 1 usd: =A0 0
kernel: CP= U =A0 =A01: hi: =A0 =A00, btch: =A0 1 usd: =A0 0
kernel: CPU =A0 = =A02: hi: =A0 =A00, btch: =A0 1 usd: =A0 0
kernel: CPU =A0 =A03: hi: =A0 =A00, btch: =A0 1 usd: =A0 0
k= ernel: CPU =A0 =A04: hi: =A0 =A00, btch: =A0 1 usd: =A0 0
kernel:= CPU =A0 =A05: hi: =A0 =A00, btch: =A0 1 usd: =A0 0
kernel: CPU = =A0 =A06: hi: =A0 =A00, btch: =A0 1 usd: =A0 0
kernel: CPU =A0 =A07: hi: =A0 =A00, btch: =A0 1 usd: =A0 0
k= ernel: Node 0 DMA32 per-cpu:
kernel: CPU =A0 =A00: hi: =A0186, bt= ch: =A031 usd: =A065
kernel: CPU =A0 =A01: hi: =A0186, btch: =A03= 1 usd: =A0 0
kernel: CPU =A0 =A02: hi: =A0186, btch: =A031 usd: 1= 70
kernel: CPU =A0 =A03: hi: =A0186, btch: =A031 usd: =A0 1
ker= nel: CPU =A0 =A04: hi: =A0186, btch: =A031 usd: =A065
kernel: CPU= =A0 =A05: hi: =A0186, btch: =A031 usd: =A082
kernel: CPU =A0 =A0= 6: hi: =A0186, btch: =A031 usd: =A034
kernel: CPU =A0 =A07: hi: =A0186, btch: =A031 usd: =A054
ker= nel: Node 0 Normal per-cpu:
kernel: CPU =A0 =A00: hi: =A0186, btc= h: =A031 usd: =A030
kernel: CPU =A0 =A01: hi: =A0186, btch: =A031= usd: =A0 0
kernel: CPU =A0 =A02: hi: =A0186, btch: =A031 usd: 16= 0
kernel: CPU =A0 =A03: hi: =A0186, btch: =A031 usd: =A022
ker= nel: CPU =A0 =A04: hi: =A0186, btch: =A031 usd: =A055
kernel: CPU= =A0 =A05: hi: =A0186, btch: =A031 usd: =A057
kernel: CPU =A0 =A0= 6: hi: =A0186, btch: =A031 usd: =A015
kernel: CPU =A0 =A07: hi: =A0186, btch: =A031 usd: =A015
ker= nel: active_anon:6981 inactive_anon:2555 isolated_anon:0
kernel: = active_file:17876 inactive_file:94621 isolated_file:0
kernel: une= victable:1 dirty:38 writeback:94542 unstable:0
kernel: free:64120 slab_reclaimable:7901 slab_unreclaimable:279561
kernel: mapped:3873 shmem:57 pagetables:2028 bounce:0
kern= el: free_cma:0
kernel: Node 0 DMA free:15836kB min:8kB low:8kB hi= gh:12kB active_anon:0kB inactive_anon:0kB active_file:0kB inactive_file:0kB= unevictable:0kB isolated(anon):0kB isolated(file):0kB present:15612kB mloc= ked:0kB dirty:0kB writeback:0kB mapped:0kB shmem:0kB slab_reclaimable:0kB s= lab_unreclaimable:0kB kernel_stack:0kB pagetables:0kB unstable:0kB bounce:0= kB free_cma:0kB writeback_tmp:0kB pages_scanned:0 all_unreclaimable? yes
kernel: lowmem_reserve[]: 0 1948 56488 56488
kernel: Node 0 = DMA32 free:218900kB min:1048kB low:1308kB high:1572kB active_anon:27660kB i= nactive_anon:9832kB active_file:29652kB inactive_file:243504kB unevictable:= 0kB isolated(anon):0kB isolated(file):0kB present:1995492kB mlocked:0kB dir= ty:152kB writeback:243344kB mapped:212kB shmem:172kB slab_reclaimable:9528k= B slab_unreclaimable:939408kB kernel_stack:32kB pagetables:1148kB unstable:= 0kB bounce:0kB free_cma:0kB writeback_tmp:0kB pages_scanned:50103 all_unrec= laimable? no
kernel: lowmem_reserve[]: 0 0 54540 54540
kernel: Node 0 Nor= mal free:21744kB min:29364kB low:36704kB high:44044kB active_anon:264kB ina= ctive_anon:388kB active_file:41852kB inactive_file:134980kB unevictable:4kB= isolated(anon):0kB isolated(file):0kB present:55848960kB mlocked:4kB dirty= :0kB writeback:134824kB mapped:15280kB shmem:56kB slab_reclaimable:22076kB = slab_unreclaimable:178836kB kernel_stack:2032kB pagetables:6964kB unstable:= 0kB bounce:0kB free_cma:0kB writeback_tmp:0kB pages_scanned:289419 all_unre= claimable? yes
kernel: lowmem_reserve[]: 0 0 0 0
kernel: Node 0 DMA: 1*4kB = 1*8kB 1*16kB 0*32kB 1*64kB 1*128kB 1*256kB 0*512kB 1*1024kB 1*2048kB 3*4096= kB =3D 15836kB
kernel: Node 0 DMA32: 3280*4kB 2835*8kB 1386*16kB = 551*32kB 315*64kB 183*128kB 105*256kB 64*512kB 37*1024kB 1*2048kB 0*4096kB = =3D 218776kB
kernel: Node 0 Normal: 4468*4kB 0*8kB 0*16kB 1*32kB 2*64kB 1*128kB 0*2= 56kB 1*512kB 1*1024kB 1*2048kB 0*4096kB =3D 21744kB
kernel: 11444= 7 total pagecache pages
kernel: 1877 pages in swap cache
kernel: Swap cache stats: add 158328, delete 156451, find 3052/3981
kernel: Free swap =A0=3D 3593000kB
kernel: Total swap =3D 4194= 300kB
kernel: 14680048 pages RAM
kernel: 13882525 pages= reserved
kernel: 943705 pages shared
kernel: 608751 pages non-shared<= /div>
init: tty (/dev/tty2) main process ended, respawning
in= it: tty (/dev/tty2) main process ended, respawning

Thanks,
Bill

--bcaec52becf1a850b904d6a3c849-- --===============3162068003129592651== 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 --===============3162068003129592651==-- From xen-users-bounces@lists.xen.org Tue Feb 26 17:15:22 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 26 Feb 2013 17:15: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 1UAO6S-0003Rg-AB; Tue, 26 Feb 2013 17:14:08 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UAO6Q-0003RJ-Lc for xen-users@lists.xen.org; Tue, 26 Feb 2013 17:14:07 +0000 Received: from [85.158.139.83:13438] by server-16.bemta-5.messagelabs.com id BB/DD-02543-E5DEC215; Tue, 26 Feb 2013 17:14:06 +0000 X-Env-Sender: thelists@gmail.com X-Msg-Ref: server-15.tower-182.messagelabs.com!1361898841!28933949!1 X-Originating-IP: [209.85.160.51] 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.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 32248 invoked from network); 26 Feb 2013 17:14:03 -0000 Received: from mail-pb0-f51.google.com (HELO mail-pb0-f51.google.com) (209.85.160.51) by server-15.tower-182.messagelabs.com with RC4-SHA encrypted SMTP; 26 Feb 2013 17:14:03 -0000 Received: by mail-pb0-f51.google.com with SMTP id un15so2478372pbc.10 for ; Tue, 26 Feb 2013 09:14:01 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:date:message-id:subject:from:to :content-type; bh=VnKRsWNH3rt02Z99lUc4NQiv3eDxq3zT1Hq/zoMjaNM=; b=HkM4oiONC9jDcMAVTsWNvg7VGjuuxH15MptxraR54ORODJFvIPTtCHAhQbRONnzOVc qZ1mKGN2euiNhfPmVqT85VZG+2c7c74trqMmvLUfus3jRIq+Hj63KeVWXMkxFpdrUkmw AP6ITzrEcpPM6hMdnFMpt1AfkJBEANnN35tHTjajFVzdB71K4RJU/B+IcKyGWQrMdHiZ LNPt+Xq4/GBYu+ARLqGIzjHjFQCHQeCBeo+MG7BVcZ3D7Qdu+jTY1HDZ1KA9BRkxhOyi h7cPa8jZETRPGXmwCnHLnmPqXYgHDG61ipMLIVVz5LHWh9AZ0PDLNdWgkfmHiflIahz7 f05w== MIME-Version: 1.0 X-Received: by 10.66.27.169 with SMTP id u9mr2644245pag.197.1361898841326; Tue, 26 Feb 2013 09:14:01 -0800 (PST) Received: by 10.68.204.66 with HTTP; Tue, 26 Feb 2013 09:14:01 -0800 (PST) Date: Tue, 26 Feb 2013 12:14:01 -0500 Message-ID: From: mailing lists To: xen-users@lists.xen.org Subject: [Xen-users] Dom0 OOM, page allocation failure X-BeenThere: xen-users@lists.xen.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="===============3162068003129592651==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============3162068003129592651== Content-Type: multipart/alternative; boundary=bcaec52becf1a850b904d6a3c849 --bcaec52becf1a850b904d6a3c849 Content-Type: text/plain; charset=ISO-8859-1 Hello, I'm running into some trouble with what appear on the surface to be OOM issues in Dom0, but I'm not seeing any other evidence. This typically happens during periods of high I/O, and has occurred during RAID initial sync, and mkfs.ext4ing (as a test, no intention to keep ext4 on this array). I've found some older posts citing very similar circumstances, however they all seem to be resolved with an updated kernel in the 2.6 tree. There was one post on a Linode board which made reference to the issue being resolved for only 32-bit Dom0s. Otherwise, I'm fairly stuck. Information below regarding HW / SW of my configuration, as well as the lines from dmesg from the start of the issue until current. Also, I have two very similar systems with the exact same software (but differing hardware), however the problem only occurs for me on the machine below. The biggest difference between the two machines is that one that fails (Box A) has 10 x 2TB drives, while the one that did not has only 6 x 750GB drives. Finally, without the Xen loaded (booting directly to kernel 3.7.8+), I do not see the errors. Any insight would be appreciated! The setup; Hardware: Processor: Intel Xeon E5-1650 RAM: 56GB total (memtests clean) System drive: 32GB SSD -- 4GB swap on the SSD Storage drives: 10 x 2TB drives in a software RAID-6 array (mdadm --create /dev/md0 -l6 -n10 -x0 /dev/sd[bcdefghijk]) Software: OS: Centos 6.3, 64-bit Kernel: 3.7.8 Xen: 4.2.1 Grub boot line: title CentOS (3.7.8+) root (hd0,0) kernel /xen-4.2.1.gz dummy=dummy dom0_mem=4096M noreboot module /vmlinuz-3.7.8+ dummy=dummy nopat root=/dev/mapper/vg_xxxx-lv_root nomodeset rd_NO_LUKS LANG=en_US.UTF-8 rd_LVM_LV=vg_xxxx/lv_swap SYSFONT=latarcyrheb-sun16 crashkernel=auto rd_LVM_LV=vg_xxxx/lv_root KEYBOARDTYPE=pc KEYTABLE=us rd_NO_DM rhgb showopts console=tty0 module /initrd-3.7.8+.img Memory status immediately following issue: free -m total used free shared buffers cached Mem: 3115 2420 695 0 34 29 -/+ buffers/cache: 2356 758 Swap: 4095 24 4071 Error logs: kernel: md127_raid6: page allocation failure: order:0, mode:0x200000 kernel: Pid: 623, comm: md127_raid6 Not tainted 3.7.8+ #7 kernel: Call Trace: kernel: [] warn_alloc_failed+0xf3/0x140 kernel: [] __alloc_pages_slowpath+0x4b0/0x7b0 kernel: [] ? __alloc_pages_slowpath+0x4b0/0x7b0 kernel: [] __alloc_pages_nodemask+0x21a/0x230 kernel: [] ? __alloc_pages_nodemask+0x21a/0x230 kernel: [] kmem_getpages+0x64/0x190 kernel: [] fallback_alloc+0x197/0x260 kernel: [] ____cache_alloc_node+0x9a/0x160 kernel: [] kmem_cache_alloc+0x12b/0x230 kernel: [] ? dma_pool_alloc+0xc7/0xf0 kernel: [] ioat2_alloc_ring_ent+0x64/0xc0 [ioatdma] kernel: [] reshape_ring+0x143/0x350 [ioatdma] kernel: [] ioat2_check_space_lock+0xe7/0x220 [ioatdma] kernel: [] ioat2_dma_prep_memcpy_lock+0x61/0x270 [ioatdma] kernel: [] async_memcpy+0x20b/0x2c4 [async_memcpy] kernel: [] async_copy_data+0x9d/0x150 [raid456] kernel: [] ops_run_biodrain+0x198/0x1d0 [raid456] kernel: [] __raid_run_ops+0x4e8/0x660 [raid456] kernel: [] ? ops_run_io+0x29/0x740 [raid456] kernel: [] ? handle_stripe_dirtying+0x335/0x450 [raid456] kernel: [] handle_stripe+0x903/0xec0 [raid456] kernel: [] ? pvclock_clocksource_read+0x58/0xd0 kernel: [] handle_active_stripes+0x19a/0x280 [raid456] kernel: [] raid5d+0x1f8/0x350 [raid456] kernel: [] ? xen_clocksource_read+0x20/0x30 kernel: [] ? _raw_spin_unlock_irqrestore+0x1e/0x30 kernel: [] md_thread+0x117/0x150 kernel: [] ? wake_up_bit+0x40/0x40 kernel: [] ? md_rdev_init+0x110/0x110 kernel: [] kthread+0xce/0xe0 kernel: [] ? xen_end_context_switch+0x1e/0x30 kernel: [] ? kthread_freezable_should_stop+0x70/0x70 kernel: [] ret_from_fork+0x7c/0xb0 kernel: [] ? kthread_freezable_should_stop+0x70/0x70 kernel: Mem-Info: kernel: Node 0 DMA per-cpu: kernel: CPU 0: hi: 0, btch: 1 usd: 0 kernel: CPU 1: hi: 0, btch: 1 usd: 0 kernel: CPU 2: hi: 0, btch: 1 usd: 0 kernel: CPU 3: hi: 0, btch: 1 usd: 0 kernel: CPU 4: hi: 0, btch: 1 usd: 0 kernel: CPU 5: hi: 0, btch: 1 usd: 0 kernel: CPU 6: hi: 0, btch: 1 usd: 0 kernel: CPU 7: hi: 0, btch: 1 usd: 0 kernel: Node 0 DMA32 per-cpu: kernel: CPU 0: hi: 186, btch: 31 usd: 0 kernel: CPU 1: hi: 186, btch: 31 usd: 0 kernel: CPU 2: hi: 186, btch: 31 usd: 13 kernel: CPU 3: hi: 186, btch: 31 usd: 0 kernel: CPU 4: hi: 186, btch: 31 usd: 30 kernel: CPU 5: hi: 186, btch: 31 usd: 0 kernel: CPU 6: hi: 186, btch: 31 usd: 0 kernel: CPU 7: hi: 186, btch: 31 usd: 0 kernel: Node 0 Normal per-cpu: kernel: CPU 0: hi: 186, btch: 31 usd: 0 kernel: CPU 1: hi: 186, btch: 31 usd: 0 kernel: CPU 2: hi: 186, btch: 31 usd: 0 kernel: CPU 3: hi: 186, btch: 31 usd: 0 kernel: CPU 4: hi: 186, btch: 31 usd: 30 kernel: CPU 5: hi: 186, btch: 31 usd: 0 kernel: CPU 6: hi: 186, btch: 31 usd: 0 kernel: CPU 7: hi: 186, btch: 31 usd: 0 kernel: active_anon:26829 inactive_anon:8320 isolated_anon:0 kernel: active_file:17836 inactive_file:422075 isolated_file:0 kernel: unevictable:1 dirty:3843 writeback:84236 unstable:0 kernel: free:64174 slab_reclaimable:14968 slab_unreclaimable:35363 kernel: mapped:3896 shmem:77 pagetables:2034 bounce:0 kernel: free_cma:0 kernel: Node 0 DMA free:15836kB min:8kB low:8kB high:12kB active_anon:0kB inactive_anon:0kB active_file:0kB inactive_file:0kB unevictable:0kB isolated(anon):0kB isolated(file):0kB present:15612kB mlocked:0kB dirty:0kB writeback:0kB mapped:0kB shmem:0kB slab_reclaimable:0kB slab_unreclaimable:0kB kernel_stack:0kB pagetables:0kB unstable:0kB bounce:0kB free_cma:0kB writeback_tmp:0kB pages_scanned:0 all_unreclaimable? yes kernel: lowmem_reserve[]: 0 1948 56488 56488 kernel: Node 0 DMA32 free:218864kB min:1048kB low:1308kB high:1572kB active_anon:97264kB inactive_anon:32512kB active_file:29592kB inactive_file:1492496kB unevictable:0kB isolated(anon):0kB isolated(file):0kB present:1995492kB mlocked:0kB dirty:13532kB writeback:142000kB mapped:40kB shmem:0kB slab_reclaimable:22544kB slab_unreclaimable:22616kB kernel_stack:16kB pagetables:1128kB unstable:0kB bounce:0kB free_cma:0kB writeback_tmp:0kB pages_scanned:0 all_unreclaimable? no kernel: lowmem_reserve[]: 0 0 54540 54540 kernel: Node 0 Normal free:21996kB min:29364kB low:36704kB high:44044kB active_anon:10052kB inactive_anon:768kB active_file:41752kB inactive_file:195804kB unevictable:4kB isolated(anon):0kB isolated(file):0kB present:55848960kB mlocked:4kB dirty:1840kB writeback:194944kB mapped:15544kB shmem:308kB slab_reclaimable:37328kB slab_unreclaimable:118836kB kernel_stack:2040kB pagetables:7008kB unstable:0kB bounce:0kB free_cma:0kB writeback_tmp:0kB pages_scanned:0 all_unreclaimable? no kernel: lowmem_reserve[]: 0 0 0 0 kernel: Node 0 DMA: 1*4kB 1*8kB 1*16kB 0*32kB 1*64kB 1*128kB 1*256kB 0*512kB 1*1024kB 1*2048kB 3*4096kB = 15836kB kernel: Node 0 DMA32: 2474*4kB 1928*8kB 1171*16kB 597*32kB 415*64kB 181*128kB 100*256kB 61*512kB 30*1024kB 9*2048kB 0*4096kB = 218872kB kernel: Node 0 Normal: 3589*4kB 608*8kB 0*16kB 1*32kB 0*64kB 1*128kB 1*256kB 1*512kB 1*1024kB 1*2048kB 0*4096kB = 23220kB kernel: 444756 total pagecache pages kernel: 4704 pages in swap cache kernel: Swap cache stats: add 130487, delete 125783, find 902/1215 kernel: Free swap = 3684144kB kernel: Total swap = 4194300kB kernel: 14680048 pages RAM kernel: 13882525 pages reserved kernel: 1271965 pages shared kernel: 282031 pages non-shared kernel: SLAB: Unable to allocate memory on node 0 (gfp=0x0) kernel: cache: ioat2, object size: 128, order: 0 kernel: node 0: slabs: 6672/6672, objs: 200160/200160, free: 0 kernel: md127_raid6: page allocation failure: order:0, mode:0x0 kernel: Pid: 623, comm: md127_raid6 Not tainted 3.7.8+ #7 kernel: Call Trace: kernel: [] warn_alloc_failed+0xf3/0x140 kernel: [] ? __wake_up+0x53/0x70 kernel: [] __alloc_pages_slowpath+0x4b0/0x7b0 kernel: [] __alloc_pages_nodemask+0x21a/0x230 kernel: [] alloc_pages_current+0xb6/0x120 kernel: [] __get_free_pages+0xe/0x50 kernel: [] xen_swiotlb_alloc_coherent+0x51/0x180 kernel: [] ? kmem_cache_alloc_trace+0xb3/0x230 kernel: [] pool_alloc_page+0xc5/0x1d0 kernel: [] dma_pool_alloc+0x7a/0xf0 kernel: [] ioat2_alloc_ring_ent+0x3a/0xc0 [ioatdma] kernel: [] reshape_ring+0x143/0x350 [ioatdma] kernel: [] ioat2_check_space_lock+0xe7/0x220 [ioatdma] kernel: [] ? error_exit+0x2a/0x60 kernel: [] ioat2_dma_prep_memcpy_lock+0x61/0x270 [ioatdma] kernel: [] async_memcpy+0x20b/0x2c4 [async_memcpy] kernel: [] async_copy_data+0x9d/0x150 [raid456] kernel: [] ops_run_biodrain+0x198/0x1d0 [raid456] kernel: [] __raid_run_ops+0x4e8/0x660 [raid456] kernel: [] ? ops_run_io+0x29/0x740 [raid456] kernel: [] ? schedule_reconstruction+0x68/0x210 [raid456] kernel: [] ? pvclock_clocksource_read+0x58/0xd0 kernel: [] ? handle_stripe_dirtying+0x335/0x450 [raid456] kernel: [] handle_stripe+0x903/0xec0 [raid456] kernel: [] ? xen_hypercall_xen_version+0xa/0x20 kernel: [] ? pvclock_clocksource_read+0x58/0xd0 kernel: [] handle_active_stripes+0x19a/0x280 [raid456] kernel: [] raid5d+0x1f8/0x350 [raid456] kernel: [] ? xen_clocksource_read+0x20/0x30 kernel: [] ? _raw_spin_unlock_irqrestore+0x1e/0x30 kernel: [] md_thread+0x117/0x150 kernel: [] ? wake_up_bit+0x40/0x40 kernel: [] ? md_rdev_init+0x110/0x110 kernel: [] kthread+0xce/0xe0 kernel: [] ? xen_end_context_switch+0x1e/0x30 kernel: [] ? kthread_freezable_should_stop+0x70/0x70 kernel: [] ret_from_fork+0x7c/0xb0 kernel: [] ? kthread_freezable_should_stop+0x70/0x70 kernel: Mem-Info: kernel: Node 0 DMA per-cpu: kernel: CPU 0: hi: 0, btch: 1 usd: 0 kernel: CPU 1: hi: 0, btch: 1 usd: 0 kernel: CPU 2: hi: 0, btch: 1 usd: 0 kernel: CPU 3: hi: 0, btch: 1 usd: 0 kernel: CPU 4: hi: 0, btch: 1 usd: 0 kernel: CPU 5: hi: 0, btch: 1 usd: 0 kernel: CPU 6: hi: 0, btch: 1 usd: 0 kernel: CPU 7: hi: 0, btch: 1 usd: 0 kernel: Node 0 DMA32 per-cpu: kernel: CPU 0: hi: 186, btch: 31 usd: 65 kernel: CPU 1: hi: 186, btch: 31 usd: 0 kernel: CPU 2: hi: 186, btch: 31 usd: 170 kernel: CPU 3: hi: 186, btch: 31 usd: 1 kernel: CPU 4: hi: 186, btch: 31 usd: 65 kernel: CPU 5: hi: 186, btch: 31 usd: 82 kernel: CPU 6: hi: 186, btch: 31 usd: 34 kernel: CPU 7: hi: 186, btch: 31 usd: 54 kernel: Node 0 Normal per-cpu: kernel: CPU 0: hi: 186, btch: 31 usd: 30 kernel: CPU 1: hi: 186, btch: 31 usd: 0 kernel: CPU 2: hi: 186, btch: 31 usd: 160 kernel: CPU 3: hi: 186, btch: 31 usd: 22 kernel: CPU 4: hi: 186, btch: 31 usd: 55 kernel: CPU 5: hi: 186, btch: 31 usd: 57 kernel: CPU 6: hi: 186, btch: 31 usd: 15 kernel: CPU 7: hi: 186, btch: 31 usd: 15 kernel: active_anon:6981 inactive_anon:2555 isolated_anon:0 kernel: active_file:17876 inactive_file:94621 isolated_file:0 kernel: unevictable:1 dirty:38 writeback:94542 unstable:0 kernel: free:64120 slab_reclaimable:7901 slab_unreclaimable:279561 kernel: mapped:3873 shmem:57 pagetables:2028 bounce:0 kernel: free_cma:0 kernel: Node 0 DMA free:15836kB min:8kB low:8kB high:12kB active_anon:0kB inactive_anon:0kB active_file:0kB inactive_file:0kB unevictable:0kB isolated(anon):0kB isolated(file):0kB present:15612kB mlocked:0kB dirty:0kB writeback:0kB mapped:0kB shmem:0kB slab_reclaimable:0kB slab_unreclaimable:0kB kernel_stack:0kB pagetables:0kB unstable:0kB bounce:0kB free_cma:0kB writeback_tmp:0kB pages_scanned:0 all_unreclaimable? yes kernel: lowmem_reserve[]: 0 1948 56488 56488 kernel: Node 0 DMA32 free:218900kB min:1048kB low:1308kB high:1572kB active_anon:27660kB inactive_anon:9832kB active_file:29652kB inactive_file:243504kB unevictable:0kB isolated(anon):0kB isolated(file):0kB present:1995492kB mlocked:0kB dirty:152kB writeback:243344kB mapped:212kB shmem:172kB slab_reclaimable:9528kB slab_unreclaimable:939408kB kernel_stack:32kB pagetables:1148kB unstable:0kB bounce:0kB free_cma:0kB writeback_tmp:0kB pages_scanned:50103 all_unreclaimable? no kernel: lowmem_reserve[]: 0 0 54540 54540 kernel: Node 0 Normal free:21744kB min:29364kB low:36704kB high:44044kB active_anon:264kB inactive_anon:388kB active_file:41852kB inactive_file:134980kB unevictable:4kB isolated(anon):0kB isolated(file):0kB present:55848960kB mlocked:4kB dirty:0kB writeback:134824kB mapped:15280kB shmem:56kB slab_reclaimable:22076kB slab_unreclaimable:178836kB kernel_stack:2032kB pagetables:6964kB unstable:0kB bounce:0kB free_cma:0kB writeback_tmp:0kB pages_scanned:289419 all_unreclaimable? yes kernel: lowmem_reserve[]: 0 0 0 0 kernel: Node 0 DMA: 1*4kB 1*8kB 1*16kB 0*32kB 1*64kB 1*128kB 1*256kB 0*512kB 1*1024kB 1*2048kB 3*4096kB = 15836kB kernel: Node 0 DMA32: 3280*4kB 2835*8kB 1386*16kB 551*32kB 315*64kB 183*128kB 105*256kB 64*512kB 37*1024kB 1*2048kB 0*4096kB = 218776kB kernel: Node 0 Normal: 4468*4kB 0*8kB 0*16kB 1*32kB 2*64kB 1*128kB 0*256kB 1*512kB 1*1024kB 1*2048kB 0*4096kB = 21744kB kernel: 114447 total pagecache pages kernel: 1877 pages in swap cache kernel: Swap cache stats: add 158328, delete 156451, find 3052/3981 kernel: Free swap = 3593000kB kernel: Total swap = 4194300kB kernel: 14680048 pages RAM kernel: 13882525 pages reserved kernel: 943705 pages shared kernel: 608751 pages non-shared init: tty (/dev/tty2) main process ended, respawning init: tty (/dev/tty2) main process ended, respawning Thanks, Bill --bcaec52becf1a850b904d6a3c849 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Hello,

I'm running into some trouble with what appea= r on the surface to be OOM issues in Dom0, but I'm not seeing any other= evidence. =A0This typically happens during periods of high I/O, and has oc= curred during RAID initial sync, and mkfs.ext4ing (as a test, no intention = to keep ext4 on this array). =A0I've found some older posts citing very= similar circumstances, however they all seem to be resolved with an update= d kernel in the 2.6 tree. =A0There was one post on a Linode board which mad= e reference to the issue being resolved for only 32-bit Dom0s. =A0Otherwise= , I'm fairly stuck. =A0Information below regarding HW / SW of my config= uration, as well as the lines from dmesg from the start of the issue until = current.

Also, I have two very similar systems with the exact sa= me software (but differing hardware), however the problem only occurs for m= e on the machine below. =A0The biggest difference between the two machines = is that one that fails (Box A) has 10 x 2TB drives, while the one that did = not has only 6 x 750GB drives. =A0Finally, without the Xen loaded (booting = directly to kernel 3.7.8+), I do not see the errors.

Any insight would be appreciated!

<= div>The setup;
Hardware:
=A0 Processor: Intel Xeon E5-1= 650
=A0 RAM: 56GB total (memtests clean)
=A0 System dri= ve: 32GB SSD
=A0 -- 4GB swap on the SSD
=A0 Storage drives: 10 x 2TB driv= es in a software RAID-6 array (mdadm --create /dev/md0 -l6 -n10 -x0 /dev/sd= [bcdefghijk])

Software:
=A0 OS: Centos 6= .3, 64-bit
=A0 Kernel: 3.7.8
=A0 Xen: 4.2.1
=A0=A0
=

Grub boot line:
=A0 title Cent= OS (3.7.8+)
=A0 =A0 =A0 =A0 =A0 root (hd0,0)
=A0 =A0 = =A0 =A0 =A0 kernel /xen-4.2.1.gz dummy=3Ddummy dom0_mem=3D4096M noreboot
=A0 =A0 =A0 =A0 =A0 module /vmlinuz-3.7.8+ dummy=3Ddummy nopat root=3D= /dev/mapper/vg_xxxx-lv_root nomodeset rd_NO_LUKS LANG=3Den_US.UTF-8 rd_LVM_= LV=3Dvg_xxxx/lv_swap =A0 SYSFONT=3Dlatarcyrheb-sun16 crashkernel=3Dauto rd_= LVM_LV=3Dvg_xxxx/lv_root =A0KEYBOARDTYPE=3Dpc KEYTABLE=3Dus rd_NO_DM rhgb s= howopts console=3Dtty0
=A0 =A0 =A0 =A0 =A0 module /initrd-3.7.8+.img

Memory status immediately following issue:
=A0 free -= m
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0total =A0 =A0 =A0 used =A0 =A0 = =A0 free =A0 =A0 shared =A0 =A0buffers =A0 =A0 cached
=A0 Mem: =A0 =A0 =A0 =A0 =A03115 =A0 =A0 =A0 2420 =A0 =A0 =A0 =A0695 = =A0 =A0 =A0 =A0 =A00 =A0 =A0 =A0 =A0 34 =A0 =A0 =A0 =A0 29
=A0 -/= + buffers/cache: =A0 =A0 =A0 2356 =A0 =A0 =A0 =A0758
=A0 Swap: = =A0 =A0 =A0 =A0 4095 =A0 =A0 =A0 =A0 24 =A0 =A0 =A0 4071

Error logs:
kernel: md127_raid6: page allocation = failure: order:0, mode:0x200000
kernel: Pid: 623, comm: md127_rai= d6 Not tainted 3.7.8+ #7
kernel: Call Trace:
kernel: [&= lt;ffffffff81117a93>] warn_alloc_failed+0xf3/0x140
kernel: [<ffffffff8111aa90>] __alloc_pages_slowpath+0x4b0/0x7b0<= /div>
kernel: [<ffffffff8111aa90>] ? __alloc_pages_slowpath+0x4b0= /0x7b0
kernel: [<ffffffff8111afaa>] __alloc_pages_nodemask+= 0x21a/0x230
kernel: [<ffffffff8111afaa>] ? __alloc_pages_nodemask+0x21a/0x23= 0
kernel: [<ffffffff8115c9d4>] kmem_getpages+0x64/0x190
kernel: [<ffffffff8115d787>] fallback_alloc+0x197/0x260
kernel: [<ffffffff8115d52a>] ____cache_alloc_node+0x9a/0x160
kernel: [<ffffffff8115defb>] kmem_cache_alloc+0x12b/0x230
kernel: [<ffffffff81150907>] ? dma_pool_alloc+0xc7/0xf0
kernel: [<ffffffffa018bea4>] ioat2_alloc_ring_ent+0x64/0xc0 [ioa= tdma]
kernel: [<ffffffffa018c043>] reshape_ring+0x143/0x350= [ioatdma]
kernel: [<ffffffffa018c337>] ioat2_check_space_l= ock+0xe7/0x220 [ioatdma]
kernel: [<ffffffffa018c4d1>] ioat2_dma_prep_memcpy_lock+0x61/0x2= 70 [ioatdma]
kernel: [<ffffffffa002720b>] async_memcpy+0x20= b/0x2c4 [async_memcpy]
kernel: [<ffffffffa00e34dd>] async_c= opy_data+0x9d/0x150 [raid456]
kernel: [<ffffffffa00e3728>] ops_run_biodrain+0x198/0x1d0 [raid4= 56]
kernel: [<ffffffffa00e4688>] __raid_run_ops+0x4e8/0x660= [raid456]
kernel: [<ffffffffa00e81a9>] ? ops_run_io+0x29/0= x740 [raid456]
kernel: [<ffffffffa00e1685>] ? handle_stripe_dirtying+0x335/0x45= 0 [raid456]
kernel: [<ffffffffa00e91c3>] handle_stripe+0x90= 3/0xec0 [raid456]
kernel: [<ffffffff81044298>] ? pvclock_cl= ocksource_read+0x58/0xd0
kernel: [<ffffffffa00e9afa>] handle_active_stripes+0x19a/0x280 [= raid456]
kernel: [<ffffffffa00e9dd8>] raid5d+0x1f8/0x350 [r= aid456]
kernel: [<ffffffff8100a350>] ? xen_clocksource_read= +0x20/0x30
kernel: [<ffffffff8156d23e>] ? _raw_spin_unlock_irqrestore+0x1e/= 0x30
kernel: [<ffffffff8144e5f7>] md_thread+0x117/0x150
kernel: [<ffffffff810789e0>] ? wake_up_bit+0x40/0x40
kernel: [<ffffffff8144e4e0>] ? md_rdev_init+0x110/0x110
kernel: [<ffffffff8107828e>] kthread+0xce/0xe0
kernel: [&= lt;ffffffff8100382e>] ? xen_end_context_switch+0x1e/0x30
kerne= l: [<ffffffff810781c0>] ? kthread_freezable_should_stop+0x70/0x70
kernel: [<ffffffff81575cec>] ret_from_fork+0x7c/0xb0
k= ernel: [<ffffffff810781c0>] ? kthread_freezable_should_stop+0x70/0x70=
kernel: Mem-Info:
kernel: Node 0 DMA per-cpu:
kernel: CPU =A0 =A00: hi: =A0 =A00, btch: =A0 1 usd: =A0 0
k= ernel: CPU =A0 =A01: hi: =A0 =A00, btch: =A0 1 usd: =A0 0
kernel:= CPU =A0 =A02: hi: =A0 =A00, btch: =A0 1 usd: =A0 0
kernel: CPU = =A0 =A03: hi: =A0 =A00, btch: =A0 1 usd: =A0 0
kernel: CPU =A0 =A04: hi: =A0 =A00, btch: =A0 1 usd: =A0 0
k= ernel: CPU =A0 =A05: hi: =A0 =A00, btch: =A0 1 usd: =A0 0
kernel:= CPU =A0 =A06: hi: =A0 =A00, btch: =A0 1 usd: =A0 0
kernel: CPU = =A0 =A07: hi: =A0 =A00, btch: =A0 1 usd: =A0 0
kernel: Node 0 DMA32 per-cpu:
kernel: CPU =A0 =A00: hi: =A01= 86, btch: =A031 usd: =A0 0
kernel: CPU =A0 =A01: hi: =A0186, btch= : =A031 usd: =A0 0
kernel: CPU =A0 =A02: hi: =A0186, btch: =A031 = usd: =A013
kernel: CPU =A0 =A03: hi: =A0186, btch: =A031 usd: =A0= 0
kernel: CPU =A0 =A04: hi: =A0186, btch: =A031 usd: =A030
ker= nel: CPU =A0 =A05: hi: =A0186, btch: =A031 usd: =A0 0
kernel: CPU= =A0 =A06: hi: =A0186, btch: =A031 usd: =A0 0
kernel: CPU =A0 =A0= 7: hi: =A0186, btch: =A031 usd: =A0 0
kernel: Node 0 Normal per-cpu:
kernel: CPU =A0 =A00: hi: =A0= 186, btch: =A031 usd: =A0 0
kernel: CPU =A0 =A01: hi: =A0186, btc= h: =A031 usd: =A0 0
kernel: CPU =A0 =A02: hi: =A0186, btch: =A031= usd: =A0 0
kernel: CPU =A0 =A03: hi: =A0186, btch: =A031 usd: = =A0 0
kernel: CPU =A0 =A04: hi: =A0186, btch: =A031 usd: =A030
ker= nel: CPU =A0 =A05: hi: =A0186, btch: =A031 usd: =A0 0
kernel: CPU= =A0 =A06: hi: =A0186, btch: =A031 usd: =A0 0
kernel: CPU =A0 =A0= 7: hi: =A0186, btch: =A031 usd: =A0 0
kernel: active_anon:26829 inactive_anon:8320 isolated_anon:0
kernel: active_file:17836 inactive_file:422075 isolated_file:0
k= ernel: unevictable:1 dirty:3843 writeback:84236 unstable:0
kernel= : free:64174 slab_reclaimable:14968 slab_unreclaimable:35363
kernel: mapped:3896 shmem:77 pagetables:2034 bounce:0
kernel= : free_cma:0
kernel: Node 0 DMA free:15836kB min:8kB low:8kB high= :12kB active_anon:0kB inactive_anon:0kB active_file:0kB inactive_file:0kB u= nevictable:0kB isolated(anon):0kB isolated(file):0kB present:15612kB mlocke= d:0kB dirty:0kB writeback:0kB mapped:0kB shmem:0kB slab_reclaimable:0kB sla= b_unreclaimable:0kB kernel_stack:0kB pagetables:0kB unstable:0kB bounce:0kB= free_cma:0kB writeback_tmp:0kB pages_scanned:0 all_unreclaimable? yes
kernel: lowmem_reserve[]: 0 1948 56488 56488
kernel: Node 0 = DMA32 free:218864kB min:1048kB low:1308kB high:1572kB active_anon:97264kB i= nactive_anon:32512kB active_file:29592kB inactive_file:1492496kB unevictabl= e:0kB isolated(anon):0kB isolated(file):0kB present:1995492kB mlocked:0kB d= irty:13532kB writeback:142000kB mapped:40kB shmem:0kB slab_reclaimable:2254= 4kB slab_unreclaimable:22616kB kernel_stack:16kB pagetables:1128kB unstable= :0kB bounce:0kB free_cma:0kB writeback_tmp:0kB pages_scanned:0 all_unreclai= mable? no
kernel: lowmem_reserve[]: 0 0 54540 54540
kernel: Node 0 Nor= mal free:21996kB min:29364kB low:36704kB high:44044kB active_anon:10052kB i= nactive_anon:768kB active_file:41752kB inactive_file:195804kB unevictable:4= kB isolated(anon):0kB isolated(file):0kB present:55848960kB mlocked:4kB dir= ty:1840kB writeback:194944kB mapped:15544kB shmem:308kB slab_reclaimable:37= 328kB slab_unreclaimable:118836kB kernel_stack:2040kB pagetables:7008kB uns= table:0kB bounce:0kB free_cma:0kB writeback_tmp:0kB pages_scanned:0 all_unr= eclaimable? no
kernel: lowmem_reserve[]: 0 0 0 0
kernel: Node 0 DMA: 1*4kB = 1*8kB 1*16kB 0*32kB 1*64kB 1*128kB 1*256kB 0*512kB 1*1024kB 1*2048kB 3*4096= kB =3D 15836kB
kernel: Node 0 DMA32: 2474*4kB 1928*8kB 1171*16kB = 597*32kB 415*64kB 181*128kB 100*256kB 61*512kB 30*1024kB 9*2048kB 0*4096kB = =3D 218872kB
kernel: Node 0 Normal: 3589*4kB 608*8kB 0*16kB 1*32kB 0*64kB 1*128kB 1= *256kB 1*512kB 1*1024kB 1*2048kB 0*4096kB =3D 23220kB
kernel: 444= 756 total pagecache pages
kernel: 4704 pages in swap cache
kernel: Swap cache stats: add 130487, delete 125783, find 902/1215
kernel: Free swap =A0=3D 3684144kB
kernel: Total swap =3D = 4194300kB
kernel: 14680048 pages RAM
kernel: 13882525 p= ages reserved
kernel: 1271965 pages shared
kernel: 282031 pages non-shared=
kernel: SLAB: Unable to allocate memory on node 0 (gfp=3D0x0)
kernel: =A0cache: ioat2, object size: 128, order: 0
kerne= l: =A0node 0: slabs: 6672/6672, objs: 200160/200160, free: 0
kernel: md127_raid6: page allocation failure: order:0, mode:0x0
<= div>kernel: Pid: 623, comm: md127_raid6 Not tainted 3.7.8+ #7
ker= nel: Call Trace:
kernel: [<ffffffff81117a93>] warn_alloc_fa= iled+0xf3/0x140
kernel: [<ffffffff81084ea3>] ? __wake_up+0x53/0x70
ker= nel: [<ffffffff8111aa90>] __alloc_pages_slowpath+0x4b0/0x7b0
kernel: [<ffffffff8111afaa>] __alloc_pages_nodemask+0x21a/0x230
kernel: [<ffffffff811571b6>] alloc_pages_current+0xb6/0x120
kernel: [<ffffffff8111778e>] __get_free_pages+0xe/0x50
kernel: [<ffffffff8130c4e1>] xen_swiotlb_alloc_coherent+0x51/0x180<= /div>
kernel: [<ffffffff8115dc53>] ? kmem_cache_alloc_trace+0xb3/0x230=
kernel: [<ffffffff81150735>] pool_alloc_page+0xc5/0x1d0
kernel: [<ffffffff811508ba>] dma_pool_alloc+0x7a/0xf0
kernel: [<ffffffffa018be7a>] ioat2_alloc_ring_ent+0x3a/0xc0 [ioa= tdma]
kernel: [<ffffffffa018c043>] reshape_ring+0x143/0x350= [ioatdma]
kernel: [<ffffffffa018c337>] ioat2_check_space_l= ock+0xe7/0x220 [ioatdma]
kernel: [<ffffffff8156dcfa>] ? error_exit+0x2a/0x60
ke= rnel: [<ffffffffa018c4d1>] ioat2_dma_prep_memcpy_lock+0x61/0x270 [ioa= tdma]
kernel: [<ffffffffa002720b>] async_memcpy+0x20b/0x2c4= [async_memcpy]
kernel: [<ffffffffa00e34dd>] async_copy_data+0x9d/0x150 [raid456= ]
kernel: [<ffffffffa00e3728>] ops_run_biodrain+0x198/0x1d0= [raid456]
kernel: [<ffffffffa00e4688>] __raid_run_ops+0x4e= 8/0x660 [raid456]
kernel: [<ffffffffa00e81a9>] ? ops_run_io+0x29/0x740 [raid456]
kernel: [<ffffffffa00e11a8>] ? schedule_reconstruction+0x68/= 0x210 [raid456]
kernel: [<ffffffff81044298>] ? pvclock_cloc= ksource_read+0x58/0xd0
kernel: [<ffffffffa00e1685>] ? handle_stripe_dirtying+0x335/0x45= 0 [raid456]
kernel: [<ffffffffa00e91c3>] handle_stripe+0x90= 3/0xec0 [raid456]
kernel: [<ffffffff8100122a>] ? xen_hyperc= all_xen_version+0xa/0x20
kernel: [<ffffffff81044298>] ? pvclock_clocksource_read+0x58/0xd= 0
kernel: [<ffffffffa00e9afa>] handle_active_stripes+0x19a/= 0x280 [raid456]
kernel: [<ffffffffa00e9dd8>] raid5d+0x1f8/0= x350 [raid456]
kernel: [<ffffffff8100a350>] ? xen_clocksource_read+0x20/0x30
kernel: [<ffffffff8156d23e>] ? _raw_spin_unlock_irqrestore+0x= 1e/0x30
kernel: [<ffffffff8144e5f7>] md_thread+0x117/0x150<= /div>
kernel: [<ffffffff810789e0>] ? wake_up_bit+0x40/0x40
k= ernel: [<ffffffff8144e4e0>] ? md_rdev_init+0x110/0x110
kern= el: [<ffffffff8107828e>] kthread+0xce/0xe0
kernel: [<fff= fffff8100382e>] ? xen_end_context_switch+0x1e/0x30
kernel: [<ffffffff810781c0>] ? kthread_freezable_should_stop+0x7= 0/0x70
kernel: [<ffffffff81575cec>] ret_from_fork+0x7c/0xb0=
kernel: [<ffffffff810781c0>] ? kthread_freezable_should_st= op+0x70/0x70
kernel: Mem-Info:
kernel: Node 0 DMA per-cpu:
kern= el: CPU =A0 =A00: hi: =A0 =A00, btch: =A0 1 usd: =A0 0
kernel: CP= U =A0 =A01: hi: =A0 =A00, btch: =A0 1 usd: =A0 0
kernel: CPU =A0 = =A02: hi: =A0 =A00, btch: =A0 1 usd: =A0 0
kernel: CPU =A0 =A03: hi: =A0 =A00, btch: =A0 1 usd: =A0 0
k= ernel: CPU =A0 =A04: hi: =A0 =A00, btch: =A0 1 usd: =A0 0
kernel:= CPU =A0 =A05: hi: =A0 =A00, btch: =A0 1 usd: =A0 0
kernel: CPU = =A0 =A06: hi: =A0 =A00, btch: =A0 1 usd: =A0 0
kernel: CPU =A0 =A07: hi: =A0 =A00, btch: =A0 1 usd: =A0 0
k= ernel: Node 0 DMA32 per-cpu:
kernel: CPU =A0 =A00: hi: =A0186, bt= ch: =A031 usd: =A065
kernel: CPU =A0 =A01: hi: =A0186, btch: =A03= 1 usd: =A0 0
kernel: CPU =A0 =A02: hi: =A0186, btch: =A031 usd: 1= 70
kernel: CPU =A0 =A03: hi: =A0186, btch: =A031 usd: =A0 1
ker= nel: CPU =A0 =A04: hi: =A0186, btch: =A031 usd: =A065
kernel: CPU= =A0 =A05: hi: =A0186, btch: =A031 usd: =A082
kernel: CPU =A0 =A0= 6: hi: =A0186, btch: =A031 usd: =A034
kernel: CPU =A0 =A07: hi: =A0186, btch: =A031 usd: =A054
ker= nel: Node 0 Normal per-cpu:
kernel: CPU =A0 =A00: hi: =A0186, btc= h: =A031 usd: =A030
kernel: CPU =A0 =A01: hi: =A0186, btch: =A031= usd: =A0 0
kernel: CPU =A0 =A02: hi: =A0186, btch: =A031 usd: 16= 0
kernel: CPU =A0 =A03: hi: =A0186, btch: =A031 usd: =A022
ker= nel: CPU =A0 =A04: hi: =A0186, btch: =A031 usd: =A055
kernel: CPU= =A0 =A05: hi: =A0186, btch: =A031 usd: =A057
kernel: CPU =A0 =A0= 6: hi: =A0186, btch: =A031 usd: =A015
kernel: CPU =A0 =A07: hi: =A0186, btch: =A031 usd: =A015
ker= nel: active_anon:6981 inactive_anon:2555 isolated_anon:0
kernel: = active_file:17876 inactive_file:94621 isolated_file:0
kernel: une= victable:1 dirty:38 writeback:94542 unstable:0
kernel: free:64120 slab_reclaimable:7901 slab_unreclaimable:279561
kernel: mapped:3873 shmem:57 pagetables:2028 bounce:0
kern= el: free_cma:0
kernel: Node 0 DMA free:15836kB min:8kB low:8kB hi= gh:12kB active_anon:0kB inactive_anon:0kB active_file:0kB inactive_file:0kB= unevictable:0kB isolated(anon):0kB isolated(file):0kB present:15612kB mloc= ked:0kB dirty:0kB writeback:0kB mapped:0kB shmem:0kB slab_reclaimable:0kB s= lab_unreclaimable:0kB kernel_stack:0kB pagetables:0kB unstable:0kB bounce:0= kB free_cma:0kB writeback_tmp:0kB pages_scanned:0 all_unreclaimable? yes
kernel: lowmem_reserve[]: 0 1948 56488 56488
kernel: Node 0 = DMA32 free:218900kB min:1048kB low:1308kB high:1572kB active_anon:27660kB i= nactive_anon:9832kB active_file:29652kB inactive_file:243504kB unevictable:= 0kB isolated(anon):0kB isolated(file):0kB present:1995492kB mlocked:0kB dir= ty:152kB writeback:243344kB mapped:212kB shmem:172kB slab_reclaimable:9528k= B slab_unreclaimable:939408kB kernel_stack:32kB pagetables:1148kB unstable:= 0kB bounce:0kB free_cma:0kB writeback_tmp:0kB pages_scanned:50103 all_unrec= laimable? no
kernel: lowmem_reserve[]: 0 0 54540 54540
kernel: Node 0 Nor= mal free:21744kB min:29364kB low:36704kB high:44044kB active_anon:264kB ina= ctive_anon:388kB active_file:41852kB inactive_file:134980kB unevictable:4kB= isolated(anon):0kB isolated(file):0kB present:55848960kB mlocked:4kB dirty= :0kB writeback:134824kB mapped:15280kB shmem:56kB slab_reclaimable:22076kB = slab_unreclaimable:178836kB kernel_stack:2032kB pagetables:6964kB unstable:= 0kB bounce:0kB free_cma:0kB writeback_tmp:0kB pages_scanned:289419 all_unre= claimable? yes
kernel: lowmem_reserve[]: 0 0 0 0
kernel: Node 0 DMA: 1*4kB = 1*8kB 1*16kB 0*32kB 1*64kB 1*128kB 1*256kB 0*512kB 1*1024kB 1*2048kB 3*4096= kB =3D 15836kB
kernel: Node 0 DMA32: 3280*4kB 2835*8kB 1386*16kB = 551*32kB 315*64kB 183*128kB 105*256kB 64*512kB 37*1024kB 1*2048kB 0*4096kB = =3D 218776kB
kernel: Node 0 Normal: 4468*4kB 0*8kB 0*16kB 1*32kB 2*64kB 1*128kB 0*2= 56kB 1*512kB 1*1024kB 1*2048kB 0*4096kB =3D 21744kB
kernel: 11444= 7 total pagecache pages
kernel: 1877 pages in swap cache
kernel: Swap cache stats: add 158328, delete 156451, find 3052/3981
kernel: Free swap =A0=3D 3593000kB
kernel: Total swap =3D 4194= 300kB
kernel: 14680048 pages RAM
kernel: 13882525 pages= reserved
kernel: 943705 pages shared
kernel: 608751 pages non-shared<= /div>
init: tty (/dev/tty2) main process ended, respawning
in= it: tty (/dev/tty2) main process ended, respawning

Thanks,
Bill

--bcaec52becf1a850b904d6a3c849-- --===============3162068003129592651== 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 --===============3162068003129592651==-- From xen-users-bounces@lists.xen.org Tue Feb 26 23:53:19 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 26 Feb 2013 23:53: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 1UAUJK-0005d5-QN; Tue, 26 Feb 2013 23:51:50 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UAUJJ-0005d0-09 for xen-users@lists.xen.org; Tue, 26 Feb 2013 23:51:49 +0000 Received: from [85.158.137.99:31811] by server-4.bemta-3.messagelabs.com id 9A/4F-17521-49A4D215; Tue, 26 Feb 2013 23:51:48 +0000 X-Env-Sender: kate_mparmpop@hotmail.com X-Msg-Ref: server-3.tower-217.messagelabs.com!1361922707!12618214!1 X-Originating-IP: [65.55.111.113] X-SpamReason: No, hits=0.1 required=7.0 tests=FORGED_HOTMAIL_RCVD, ML_RADAR_SPEW_LINKS_12,ML_RADAR_SPEW_LINKS_14,MSGID_FROM_MTA_HEADER, spamassassin: X-StarScan-Received: X-StarScan-Version: 6.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 5424 invoked from network); 26 Feb 2013 23:51:47 -0000 Received: from blu0-omc2-s38.blu0.hotmail.com (HELO blu0-omc2-s38.blu0.hotmail.com) (65.55.111.113) by server-3.tower-217.messagelabs.com with SMTP; 26 Feb 2013 23:51:47 -0000 Received: from BLU0-SMTP111 ([65.55.111.71]) by blu0-omc2-s38.blu0.hotmail.com with Microsoft SMTPSVC(6.0.3790.4675); Tue, 26 Feb 2013 15:51:46 -0800 X-EIP: [R2Q5kdaJ5hYGlrvEotziPlq/5/6eyLSD] X-Originating-Email: [kate_mparmpop@hotmail.com] Message-ID: Received: from [192.168.0.100] ([82.139.117.118]) by BLU0-SMTP111.phx.gbl over TLS secured channel with Microsoft SMTPSVC(6.0.3790.4675); Tue, 26 Feb 2013 15:51:45 -0800 Date: Wed, 27 Feb 2013 00:51:42 +0100 From: Katerina Mparmpopoulou User-Agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/20130221 Thunderbird/17.0.3 MIME-Version: 1.0 To: xen-users@lists.xen.org X-Enigmail-Version: 1.5 X-OriginalArrivalTime: 26 Feb 2013 23:51:45.0221 (UTC) FILETIME=[3BCE7750:01CE147C] Subject: [Xen-users] Xen 4.2 - Security on Live Migration X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: 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 Hello all, I've recently switch from Xen 4.1 to 4.2.1 and from xm/xend to xl/libxl toolstack as well. Although Xen 4.1 did not support Secure Live Migration by default, I could modify the /etc/xen/xend-config.sxp file giving any level of security I wanted, either allow only specific hosts, or using ssl and adjusting my private key and the certificate. #### e x a m p l e #### ###### uncommented modules in /etc/xen/xend-config.sxp ###### ##### ###### (xend-relocation-ssl-server yes) (xend-relocation-ssl-port 8003) (xend-relocation-server-ssl-key-file server.key) (xend-relocation-server-ssl-cert-file server.crt) (xend-relocation-ssl yes) Xen 4.2 - - uses xl by default [By default xl relies on ssh as a transport mechanism between the two hosts.] - - and also Xen daemon configuration file (xend-config.sxp ) is officially deprecated My question is, Is there any way that I can control the level of security in Xen 4.2 considering Live Migration? Should I look in specific libxl files?? Katerina -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQEcBAEBAgAGBQJRLUqFAAoJEIrShLVVnSKr6BUH/i9unhmMJMDMDOC2yO5SA0dX s/lju/k0QI37gDRNOvf8TI85FbuGGyaN/PHpAn8ElbVi3sRFIuMbTg824EYuTcmW 5SmfQay7igHiqb8VxLYAaeVgWTpRpLpI22w+X2NFjs9TPghdNH/s3RVJUg1jdo0M +KpzvDM4eH1t8LSG8weMsPGAzoeP017ri4DKR6YG7gLbUy6WKG+E4MnOZT3FYI1j +i1duavyPirX3LjbW+vSvFNu60O2ze2dDPjZKwXbs/buUzH7hkiazdplfSlXG589 7s3bt3kA/NvZ64QT+chThHwW/GjKc5gNTinr/s0jxD8dTqwPndqHWdH/VQEc/qc= =hvsE -----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 Tue Feb 26 23:53:19 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 26 Feb 2013 23:53: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 1UAUJK-0005d5-QN; Tue, 26 Feb 2013 23:51:50 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UAUJJ-0005d0-09 for xen-users@lists.xen.org; Tue, 26 Feb 2013 23:51:49 +0000 Received: from [85.158.137.99:31811] by server-4.bemta-3.messagelabs.com id 9A/4F-17521-49A4D215; Tue, 26 Feb 2013 23:51:48 +0000 X-Env-Sender: kate_mparmpop@hotmail.com X-Msg-Ref: server-3.tower-217.messagelabs.com!1361922707!12618214!1 X-Originating-IP: [65.55.111.113] X-SpamReason: No, hits=0.1 required=7.0 tests=FORGED_HOTMAIL_RCVD, ML_RADAR_SPEW_LINKS_12,ML_RADAR_SPEW_LINKS_14,MSGID_FROM_MTA_HEADER, spamassassin: X-StarScan-Received: X-StarScan-Version: 6.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 5424 invoked from network); 26 Feb 2013 23:51:47 -0000 Received: from blu0-omc2-s38.blu0.hotmail.com (HELO blu0-omc2-s38.blu0.hotmail.com) (65.55.111.113) by server-3.tower-217.messagelabs.com with SMTP; 26 Feb 2013 23:51:47 -0000 Received: from BLU0-SMTP111 ([65.55.111.71]) by blu0-omc2-s38.blu0.hotmail.com with Microsoft SMTPSVC(6.0.3790.4675); Tue, 26 Feb 2013 15:51:46 -0800 X-EIP: [R2Q5kdaJ5hYGlrvEotziPlq/5/6eyLSD] X-Originating-Email: [kate_mparmpop@hotmail.com] Message-ID: Received: from [192.168.0.100] ([82.139.117.118]) by BLU0-SMTP111.phx.gbl over TLS secured channel with Microsoft SMTPSVC(6.0.3790.4675); Tue, 26 Feb 2013 15:51:45 -0800 Date: Wed, 27 Feb 2013 00:51:42 +0100 From: Katerina Mparmpopoulou User-Agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/20130221 Thunderbird/17.0.3 MIME-Version: 1.0 To: xen-users@lists.xen.org X-Enigmail-Version: 1.5 X-OriginalArrivalTime: 26 Feb 2013 23:51:45.0221 (UTC) FILETIME=[3BCE7750:01CE147C] Subject: [Xen-users] Xen 4.2 - Security on Live Migration X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: 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 Hello all, I've recently switch from Xen 4.1 to 4.2.1 and from xm/xend to xl/libxl toolstack as well. Although Xen 4.1 did not support Secure Live Migration by default, I could modify the /etc/xen/xend-config.sxp file giving any level of security I wanted, either allow only specific hosts, or using ssl and adjusting my private key and the certificate. #### e x a m p l e #### ###### uncommented modules in /etc/xen/xend-config.sxp ###### ##### ###### (xend-relocation-ssl-server yes) (xend-relocation-ssl-port 8003) (xend-relocation-server-ssl-key-file server.key) (xend-relocation-server-ssl-cert-file server.crt) (xend-relocation-ssl yes) Xen 4.2 - - uses xl by default [By default xl relies on ssh as a transport mechanism between the two hosts.] - - and also Xen daemon configuration file (xend-config.sxp ) is officially deprecated My question is, Is there any way that I can control the level of security in Xen 4.2 considering Live Migration? Should I look in specific libxl files?? Katerina -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQEcBAEBAgAGBQJRLUqFAAoJEIrShLVVnSKr6BUH/i9unhmMJMDMDOC2yO5SA0dX s/lju/k0QI37gDRNOvf8TI85FbuGGyaN/PHpAn8ElbVi3sRFIuMbTg824EYuTcmW 5SmfQay7igHiqb8VxLYAaeVgWTpRpLpI22w+X2NFjs9TPghdNH/s3RVJUg1jdo0M +KpzvDM4eH1t8LSG8weMsPGAzoeP017ri4DKR6YG7gLbUy6WKG+E4MnOZT3FYI1j +i1duavyPirX3LjbW+vSvFNu60O2ze2dDPjZKwXbs/buUzH7hkiazdplfSlXG589 7s3bt3kA/NvZ64QT+chThHwW/GjKc5gNTinr/s0jxD8dTqwPndqHWdH/VQEc/qc= =hvsE -----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 Wed Feb 27 01:53:37 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 27 Feb 2013 01:53: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 1UAWBm-0002nT-Co; Wed, 27 Feb 2013 01:52:10 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UAVVB-0002RD-Hz for xen-users@lists.xensource.com; Wed, 27 Feb 2013 01:08:09 +0000 Received: from [85.158.139.83:24622] by server-7.bemta-5.messagelabs.com id 2E/CE-12441-87C5D215; Wed, 27 Feb 2013 01:08:08 +0000 X-Env-Sender: dswartz@druber.com X-Msg-Ref: server-4.tower-182.messagelabs.com!1361927286!26374878!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.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 1336 invoked from network); 27 Feb 2013 01:08:08 -0000 Received: from sam.nabble.com (HELO sam.nabble.com) (216.139.236.26) by server-4.tower-182.messagelabs.com with AES256-SHA encrypted SMTP; 27 Feb 2013 01:08:08 -0000 Received: from [192.168.236.26] (helo=sam.nabble.com) by sam.nabble.com with esmtp (Exim 4.72) (envelope-from ) id 1UAVV7-00005h-JR for xen-users@lists.xensource.com; Tue, 26 Feb 2013 17:08:05 -0800 Date: Tue, 26 Feb 2013 17:08:05 -0800 (PST) From: danswartz To: xen-users@lists.xensource.com Message-ID: <1361927285562-5714476.post@n5.nabble.com> In-Reply-To: <20121028133544.GY8912@reaktio.net> References: <20121028133544.GY8912@reaktio.net> MIME-Version: 1.0 X-Mailman-Approved-At: Wed, 27 Feb 2013 01:52:08 +0000 Subject: Re: [Xen-users] [Xen-API] XCP 1.6 beta Ram restriction for pci passthrough to pv Ubuntu 12.04 template X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: 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, Pasi. Can you say which kernel version(s) have this fix? I have looked as recently as 3.8 kernels and don't see anything in the xen-pcifront.c file that looks related to this (although it's possible it's elsewhere?) Like the OP I am using Ubuntu 12.04 with a 3.2.0-xx kernel and got bit by this. I was working around it with an HVM, but my HBA (an LSI HBA) would get a MPT BIOS fault on boot, requiring 'hit any key to continue', which is obviously not acceptable for unattended operation :) I would dearly love a 64-bit dom0, since I want to serve up data via NFS/CIFS from a ZFS dom0, but restricting that to 3GB is a major showstopper. -- View this message in context: http://xen.1045712.n5.nabble.com/XCP-1-6-beta-Ram-restriction-for-pci-passthrough-to-pv-Ubuntu-12-04-template-tp5712107p5714476.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 Feb 27 01:53:37 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 27 Feb 2013 01:53: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 1UAWBm-0002nT-Co; Wed, 27 Feb 2013 01:52:10 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UAVVB-0002RD-Hz for xen-users@lists.xensource.com; Wed, 27 Feb 2013 01:08:09 +0000 Received: from [85.158.139.83:24622] by server-7.bemta-5.messagelabs.com id 2E/CE-12441-87C5D215; Wed, 27 Feb 2013 01:08:08 +0000 X-Env-Sender: dswartz@druber.com X-Msg-Ref: server-4.tower-182.messagelabs.com!1361927286!26374878!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.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 1336 invoked from network); 27 Feb 2013 01:08:08 -0000 Received: from sam.nabble.com (HELO sam.nabble.com) (216.139.236.26) by server-4.tower-182.messagelabs.com with AES256-SHA encrypted SMTP; 27 Feb 2013 01:08:08 -0000 Received: from [192.168.236.26] (helo=sam.nabble.com) by sam.nabble.com with esmtp (Exim 4.72) (envelope-from ) id 1UAVV7-00005h-JR for xen-users@lists.xensource.com; Tue, 26 Feb 2013 17:08:05 -0800 Date: Tue, 26 Feb 2013 17:08:05 -0800 (PST) From: danswartz To: xen-users@lists.xensource.com Message-ID: <1361927285562-5714476.post@n5.nabble.com> In-Reply-To: <20121028133544.GY8912@reaktio.net> References: <20121028133544.GY8912@reaktio.net> MIME-Version: 1.0 X-Mailman-Approved-At: Wed, 27 Feb 2013 01:52:08 +0000 Subject: Re: [Xen-users] [Xen-API] XCP 1.6 beta Ram restriction for pci passthrough to pv Ubuntu 12.04 template X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: 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, Pasi. Can you say which kernel version(s) have this fix? I have looked as recently as 3.8 kernels and don't see anything in the xen-pcifront.c file that looks related to this (although it's possible it's elsewhere?) Like the OP I am using Ubuntu 12.04 with a 3.2.0-xx kernel and got bit by this. I was working around it with an HVM, but my HBA (an LSI HBA) would get a MPT BIOS fault on boot, requiring 'hit any key to continue', which is obviously not acceptable for unattended operation :) I would dearly love a 64-bit dom0, since I want to serve up data via NFS/CIFS from a ZFS dom0, but restricting that to 3GB is a major showstopper. -- View this message in context: http://xen.1045712.n5.nabble.com/XCP-1-6-beta-Ram-restriction-for-pci-passthrough-to-pv-Ubuntu-12-04-template-tp5712107p5714476.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 Feb 27 03:52:18 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 27 Feb 2013 03:52: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 1UAY2U-0004QW-CI; Wed, 27 Feb 2013 03:50:42 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UAY2T-0004QR-4s for xen-users@lists.xen.org; Wed, 27 Feb 2013 03:50:41 +0000 Received: from [193.109.254.147:56154] by server-13.bemta-14.messagelabs.com id DC/3E-30639-0928D215; Wed, 27 Feb 2013 03:50:40 +0000 X-Env-Sender: jaceksburghardt@gmail.com X-Msg-Ref: server-16.tower-27.messagelabs.com!1361937037!9687322!1 X-Originating-IP: [209.85.210.175] X-SpamReason: No, hits=3.1 required=7.0 tests=HTML_00_10,HTML_MESSAGE, HTML_SHORT_LENGTH,ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 23812 invoked from network); 27 Feb 2013 03:50:39 -0000 Received: from mail-ia0-f175.google.com (HELO mail-ia0-f175.google.com) (209.85.210.175) by server-16.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 27 Feb 2013 03:50:39 -0000 Received: by mail-ia0-f175.google.com with SMTP id r4so96936iaj.20 for ; Tue, 26 Feb 2013 19:50:37 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:date:message-id:subject:from:to :content-type; bh=Lv+8CbIQcgrcmu9lFXIa/PvfglQl0No0egtuA7J1kQE=; b=WsPawbFIeoBFWJ953t46TeHKRA8GztI/TIQlbdJOVGFL3LUBJ0p6GGqdEGFQ2btlYV EmmrH/pqWxEw4tP3t8hYCrCUqy5Iud4oWVgwOjBiBiebFEl4D7+oiXctdUgjs6/Q0iyK ZIZbYVJkELlK8SWszQ6bLUu3zvpjHvjvmwWQMsS+oZUi/UiAldGEzbgOlhT9fmOmbwQl eIKuBNJiPd4xq5BOQOq6U/li3e7u1ThQp0v1lDBD4pk25PplMB2Hq+kHkglB891neyHV YViAzxaCN94UXQ79VuBhpv5A6ncjCfN0687RX2BNAuGaoLh13io81TnFfjG/fuDwYvnr RAtQ== MIME-Version: 1.0 X-Received: by 10.50.17.163 with SMTP id p3mr307734igd.90.1361937037567; Tue, 26 Feb 2013 19:50:37 -0800 (PST) Received: by 10.42.41.5 with HTTP; Tue, 26 Feb 2013 19:50:37 -0800 (PST) Date: Tue, 26 Feb 2013 20:50:37 -0700 Message-ID: From: jacek burghardt To: xen-users Subject: [Xen-users] xenstored /local/domain X-BeenThere: xen-users@lists.xen.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="===============6905097875406061787==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============6905097875406061787== Content-Type: multipart/alternative; boundary=14dae93407cf54b28304d6acad18 --14dae93407cf54b28304d6acad18 Content-Type: text/plain; charset=ISO-8859-1 Can somone tell me where is local/domain created ? --14dae93407cf54b28304d6acad18 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Can somone tell me where=A0 is local/domain created ?
--14dae93407cf54b28304d6acad18-- --===============6905097875406061787== 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 --===============6905097875406061787==-- From xen-users-bounces@lists.xen.org Wed Feb 27 03:52:18 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 27 Feb 2013 03:52: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 1UAY2U-0004QW-CI; Wed, 27 Feb 2013 03:50:42 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UAY2T-0004QR-4s for xen-users@lists.xen.org; Wed, 27 Feb 2013 03:50:41 +0000 Received: from [193.109.254.147:56154] by server-13.bemta-14.messagelabs.com id DC/3E-30639-0928D215; Wed, 27 Feb 2013 03:50:40 +0000 X-Env-Sender: jaceksburghardt@gmail.com X-Msg-Ref: server-16.tower-27.messagelabs.com!1361937037!9687322!1 X-Originating-IP: [209.85.210.175] X-SpamReason: No, hits=3.1 required=7.0 tests=HTML_00_10,HTML_MESSAGE, HTML_SHORT_LENGTH,ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 23812 invoked from network); 27 Feb 2013 03:50:39 -0000 Received: from mail-ia0-f175.google.com (HELO mail-ia0-f175.google.com) (209.85.210.175) by server-16.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 27 Feb 2013 03:50:39 -0000 Received: by mail-ia0-f175.google.com with SMTP id r4so96936iaj.20 for ; Tue, 26 Feb 2013 19:50:37 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:date:message-id:subject:from:to :content-type; bh=Lv+8CbIQcgrcmu9lFXIa/PvfglQl0No0egtuA7J1kQE=; b=WsPawbFIeoBFWJ953t46TeHKRA8GztI/TIQlbdJOVGFL3LUBJ0p6GGqdEGFQ2btlYV EmmrH/pqWxEw4tP3t8hYCrCUqy5Iud4oWVgwOjBiBiebFEl4D7+oiXctdUgjs6/Q0iyK ZIZbYVJkELlK8SWszQ6bLUu3zvpjHvjvmwWQMsS+oZUi/UiAldGEzbgOlhT9fmOmbwQl eIKuBNJiPd4xq5BOQOq6U/li3e7u1ThQp0v1lDBD4pk25PplMB2Hq+kHkglB891neyHV YViAzxaCN94UXQ79VuBhpv5A6ncjCfN0687RX2BNAuGaoLh13io81TnFfjG/fuDwYvnr RAtQ== MIME-Version: 1.0 X-Received: by 10.50.17.163 with SMTP id p3mr307734igd.90.1361937037567; Tue, 26 Feb 2013 19:50:37 -0800 (PST) Received: by 10.42.41.5 with HTTP; Tue, 26 Feb 2013 19:50:37 -0800 (PST) Date: Tue, 26 Feb 2013 20:50:37 -0700 Message-ID: From: jacek burghardt To: xen-users Subject: [Xen-users] xenstored /local/domain X-BeenThere: xen-users@lists.xen.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="===============6905097875406061787==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============6905097875406061787== Content-Type: multipart/alternative; boundary=14dae93407cf54b28304d6acad18 --14dae93407cf54b28304d6acad18 Content-Type: text/plain; charset=ISO-8859-1 Can somone tell me where is local/domain created ? --14dae93407cf54b28304d6acad18 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Can somone tell me where=A0 is local/domain created ?
--14dae93407cf54b28304d6acad18-- --===============6905097875406061787== 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 --===============6905097875406061787==-- From xen-users-bounces@lists.xen.org Wed Feb 27 06:42:45 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 27 Feb 2013 06: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 1UAahl-0006ts-43; Wed, 27 Feb 2013 06:41:29 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UAahi-0006tn-VU for xen-users@lists.xen.org; Wed, 27 Feb 2013 06:41:27 +0000 Received: from [193.109.254.147:56302] by server-14.bemta-14.messagelabs.com id FD/70-02031-69AAD215; Wed, 27 Feb 2013 06:41:26 +0000 X-Env-Sender: epretorious@yahoo.com X-Msg-Ref: server-12.tower-27.messagelabs.com!1361947284!9820776!1 X-Originating-IP: [98.138.90.82] X-SpamReason: No, hits=0.0 required=7.0 tests=ML_RADAR_SPEW_LINKS_12, ML_RADAR_SPEW_LINKS_14,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 12500 invoked from network); 27 Feb 2013 06:41:25 -0000 Received: from nm19.bullet.mail.ne1.yahoo.com (HELO nm19.bullet.mail.ne1.yahoo.com) (98.138.90.82) by server-12.tower-27.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 27 Feb 2013 06:41:25 -0000 Received: from [98.138.90.52] by nm19.bullet.mail.ne1.yahoo.com with NNFMP; 27 Feb 2013 06:41:23 -0000 Received: from [98.138.89.171] by tm5.bullet.mail.ne1.yahoo.com with NNFMP; 27 Feb 2013 06:41:23 -0000 Received: from [127.0.0.1] by omp1027.mail.ne1.yahoo.com with NNFMP; 27 Feb 2013 06:41:23 -0000 X-Yahoo-Newman-Property: ymail-3 X-Yahoo-Newman-Id: 825197.98100.bm@omp1027.mail.ne1.yahoo.com Received: (qmail 4400 invoked by uid 60001); 27 Feb 2013 06:41:23 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1361947283; bh=Fi8DWFGyaM5ZenU3bAgoym61fg4CHxvIxVLuJAlqM4U=; h=X-YMail-OSG:Received:X-Rocket-MIMEInfo:X-Mailer:Message-ID:Date:From:Reply-To:Subject:To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=5uHhytrMIZd+WUnzdd4r4JEQ25MB6XGXVNcxabx0OtQvJSmZyrkG1LfQm0OBDuIpKmAaKw3FmR1LQhRybzhnTr8kZ0As1OtnETZc2u03P+hZFufd9LPElSdc6y0rA3HrZG9GcYH2sQGWy8Pyk5loVDOlEiRIqftvzdcKu+AiQM4= DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=X-YMail-OSG:Received:X-Rocket-MIMEInfo:X-Mailer:Message-ID:Date:From:Reply-To:Subject:To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=jibm2GOIxbPbhjLs63ucxlgQvpVs8R1Si67s5+cMfuQYocT8XDIdVXttLK/jXIahhkXkR6nHJ6zN2DCJyLaYIR19JypA4ypffPUwML1au3yn4e1rLJatTxalSogpofxcbfuzgvZABhVqUwIC4kYlDmDf4/LrwbNLYY17vX1Exac=; X-YMail-OSG: 9kytMHkVM1k9wlmXiieOb3Eg0pWp8lVjsuEPKWqtLm1ZZ5O w.ATa.xpXr74HNBaDnhoO25REPqE23tT.gWY8gfMSI5YQ36xfDi6oeQddJxO RehlYHm1reu.ATX7fYsK8_rBJE8sKoJLEpdJ4Xmax.zGstUGGJDNy2JorlKL UkxkbHq.pAAs3gAVwraSbAV_fqh8oYMnZSKm3bMQGQmw7Fz4ta7ePy_17le4 lO1V0n.FxzfU8aieDNobph5q2Oo2fi5ogOCGGVP2jk.cG9SLGxx5G67PK43r P4gvLzN1YFxewq3aGr7d3cyBDk_dYw96exInNSPH3nITYDSg.GN1aXIr6qIR x5w1OIpmvTqtsPcYwqyYILvUyb5lvBs5qYQoP0J253sWh1UslCa6vhzHjuDc M2aPOHrtA.ZmRCOBjbKjKZOFKaQekTd8xJTA3g2j5uqCsI2Nhv6OFiqzcs0v mNSQ5kQwap50Hia4zQqAUN.WzoD.PK1U0LFU033eo61r7MqWvULtl6f.28ns ._nOr Received: from [74.197.253.230] by web126006.mail.ne1.yahoo.com via HTTP; Tue, 26 Feb 2013 22:41:23 PST X-Rocket-MIMEInfo: 001.001, SSBoYXZlIGEgYml0IG9mIGEgcXVhbmRyeTogSSd2ZSBtaWdyYXRlZCB0d28gUFZNJ3MgYXdheSBmcm9tIHRoZSBTdVNFLWJhc2VkIGhvc3Qgc3lzdGVtIGJ1dCB0aGV5IHBlcnNpc3QgaW4gWGVuZCBldmVuIHRob3VnaC4uLgoKwqAqIHRoZXkgYXJlIG5vdCBhY3RpdmUgb24gdGhlIGhvc3Q7IArCoCogdGhleSdyZSBub3QgaW4gWGVuU3RvcmUgKC92YXIvbGliL3hlbnN0b3JlL3RkYiksIGFuZDsgCsKgKiB0aGVyZSBhcmUgbm8gY29uZmlndXJhdGlvbiBmaWxlcyBmb3IgdGhlIFZNJ3MgKGluIC9ldGMveGVuL3YBMAEBAQE- X-Mailer: YahooMailWebService/0.8.135.514 Message-ID: <1361947283.3095.YahooMailNeo@web126006.mail.ne1.yahoo.com> Date: Tue, 26 Feb 2013 22:41:23 -0800 (PST) From: Eric To: "xen-users@lists.xen.org" MIME-Version: 1.0 Subject: [Xen-users] Mysterious PVM's X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: Eric 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 I have a bit of a quandry: I've migrated two PVM's away from the SuSE-based= host system but they persist in Xend even though... =A0* they are not active on the host; = =A0* they're not in XenStore (/var/lib/xenstore/tdb), and; = =A0* there are no configuration files for the VM's (in /etc/xen/vm): > xen2:~ # ls /etc/xen/vm > sles11-1=A0=A0sles11-1.xml xen2:~ # xm list > Name=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0= =A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0ID=A0=A0 Mem VCPUs=A0=A0= =A0=A0=A0=A0State=A0=A0 Time(s) > Domain-0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0= =A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 0=A0=A0 502=A0=A0=A0=A0 2=A0= =A0=A0=A0 r-----=A0=A0 6185.1 > oracle1=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0= =A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0786=A0=A0=A0=A0= 1=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A015.3 > oracle2=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0= =A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0786=A0=A0=A0=A0= 1=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A014.0 > = > xen2:~ # xenstore-ls | grep "name =3D " = > name =3D "Domain-0" > name =3D "Pool-0" = > pool_name =3D "Pool-0" > name =3D "Domain-0" And, in fact, the PVM's can still be restarted even though... =A0 =A0* there are no configuration files stored locally (in /etc/xen/vm) and =A0* there's no information stored in XenStore. >=A0 xen2:~ # xm list >=A0 Name=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0= =A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 ID=A0=A0 Mem VCPUs=A0= =A0=A0=A0=A0 State=A0=A0 Time(s) >=A0 Domain-0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0= =A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 0=A0=A0 502=A0=A0=A0=A0 2= =A0=A0=A0=A0 r-----=A0=A0=A0=A0 40.1 >=A0 oracle1=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0= =A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 786=A0=A0=A0= =A0 1=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 18.2 >=A0 oracle2=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0= =A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 786=A0=A0=A0= =A0 1=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 16.9 >=A0 = >=A0 xen2:~ # xm start oracle1 >=A0 = >=A0 xen2:~ # xm start oracle2 >=A0 = >=A0 xen2:~ # xm list >=A0 Name=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0= =A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 ID=A0=A0 Mem VCPUs=A0= =A0=A0=A0=A0 State=A0=A0 Time(s) >=A0 Domain-0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0= =A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 0=A0=A0 502=A0=A0=A0=A0 2= =A0=A0=A0=A0 r-----=A0=A0=A0=A0 62.8 >=A0 oracle1=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=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=A0=A0 786=A0=A0=A0=A0 1= =A0=A0=A0=A0 ------=A0=A0=A0=A0 10.8 >=A0 oracle2=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0= =A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 2=A0=A0 786=A0=A0=A0=A0 1= =A0=A0=A0=A0 r-----=A0=A0=A0=A0=A0 2.8 Where is this configurationo information being stored? = Eric Pretorious Truckee, CA _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Wed Feb 27 06:42:45 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 27 Feb 2013 06: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 1UAahl-0006ts-43; Wed, 27 Feb 2013 06:41:29 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UAahi-0006tn-VU for xen-users@lists.xen.org; Wed, 27 Feb 2013 06:41:27 +0000 Received: from [193.109.254.147:56302] by server-14.bemta-14.messagelabs.com id FD/70-02031-69AAD215; Wed, 27 Feb 2013 06:41:26 +0000 X-Env-Sender: epretorious@yahoo.com X-Msg-Ref: server-12.tower-27.messagelabs.com!1361947284!9820776!1 X-Originating-IP: [98.138.90.82] X-SpamReason: No, hits=0.0 required=7.0 tests=ML_RADAR_SPEW_LINKS_12, ML_RADAR_SPEW_LINKS_14,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 12500 invoked from network); 27 Feb 2013 06:41:25 -0000 Received: from nm19.bullet.mail.ne1.yahoo.com (HELO nm19.bullet.mail.ne1.yahoo.com) (98.138.90.82) by server-12.tower-27.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 27 Feb 2013 06:41:25 -0000 Received: from [98.138.90.52] by nm19.bullet.mail.ne1.yahoo.com with NNFMP; 27 Feb 2013 06:41:23 -0000 Received: from [98.138.89.171] by tm5.bullet.mail.ne1.yahoo.com with NNFMP; 27 Feb 2013 06:41:23 -0000 Received: from [127.0.0.1] by omp1027.mail.ne1.yahoo.com with NNFMP; 27 Feb 2013 06:41:23 -0000 X-Yahoo-Newman-Property: ymail-3 X-Yahoo-Newman-Id: 825197.98100.bm@omp1027.mail.ne1.yahoo.com Received: (qmail 4400 invoked by uid 60001); 27 Feb 2013 06:41:23 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1361947283; bh=Fi8DWFGyaM5ZenU3bAgoym61fg4CHxvIxVLuJAlqM4U=; h=X-YMail-OSG:Received:X-Rocket-MIMEInfo:X-Mailer:Message-ID:Date:From:Reply-To:Subject:To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=5uHhytrMIZd+WUnzdd4r4JEQ25MB6XGXVNcxabx0OtQvJSmZyrkG1LfQm0OBDuIpKmAaKw3FmR1LQhRybzhnTr8kZ0As1OtnETZc2u03P+hZFufd9LPElSdc6y0rA3HrZG9GcYH2sQGWy8Pyk5loVDOlEiRIqftvzdcKu+AiQM4= DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=X-YMail-OSG:Received:X-Rocket-MIMEInfo:X-Mailer:Message-ID:Date:From:Reply-To:Subject:To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=jibm2GOIxbPbhjLs63ucxlgQvpVs8R1Si67s5+cMfuQYocT8XDIdVXttLK/jXIahhkXkR6nHJ6zN2DCJyLaYIR19JypA4ypffPUwML1au3yn4e1rLJatTxalSogpofxcbfuzgvZABhVqUwIC4kYlDmDf4/LrwbNLYY17vX1Exac=; X-YMail-OSG: 9kytMHkVM1k9wlmXiieOb3Eg0pWp8lVjsuEPKWqtLm1ZZ5O w.ATa.xpXr74HNBaDnhoO25REPqE23tT.gWY8gfMSI5YQ36xfDi6oeQddJxO RehlYHm1reu.ATX7fYsK8_rBJE8sKoJLEpdJ4Xmax.zGstUGGJDNy2JorlKL UkxkbHq.pAAs3gAVwraSbAV_fqh8oYMnZSKm3bMQGQmw7Fz4ta7ePy_17le4 lO1V0n.FxzfU8aieDNobph5q2Oo2fi5ogOCGGVP2jk.cG9SLGxx5G67PK43r P4gvLzN1YFxewq3aGr7d3cyBDk_dYw96exInNSPH3nITYDSg.GN1aXIr6qIR x5w1OIpmvTqtsPcYwqyYILvUyb5lvBs5qYQoP0J253sWh1UslCa6vhzHjuDc M2aPOHrtA.ZmRCOBjbKjKZOFKaQekTd8xJTA3g2j5uqCsI2Nhv6OFiqzcs0v mNSQ5kQwap50Hia4zQqAUN.WzoD.PK1U0LFU033eo61r7MqWvULtl6f.28ns ._nOr Received: from [74.197.253.230] by web126006.mail.ne1.yahoo.com via HTTP; Tue, 26 Feb 2013 22:41:23 PST X-Rocket-MIMEInfo: 001.001, SSBoYXZlIGEgYml0IG9mIGEgcXVhbmRyeTogSSd2ZSBtaWdyYXRlZCB0d28gUFZNJ3MgYXdheSBmcm9tIHRoZSBTdVNFLWJhc2VkIGhvc3Qgc3lzdGVtIGJ1dCB0aGV5IHBlcnNpc3QgaW4gWGVuZCBldmVuIHRob3VnaC4uLgoKwqAqIHRoZXkgYXJlIG5vdCBhY3RpdmUgb24gdGhlIGhvc3Q7IArCoCogdGhleSdyZSBub3QgaW4gWGVuU3RvcmUgKC92YXIvbGliL3hlbnN0b3JlL3RkYiksIGFuZDsgCsKgKiB0aGVyZSBhcmUgbm8gY29uZmlndXJhdGlvbiBmaWxlcyBmb3IgdGhlIFZNJ3MgKGluIC9ldGMveGVuL3YBMAEBAQE- X-Mailer: YahooMailWebService/0.8.135.514 Message-ID: <1361947283.3095.YahooMailNeo@web126006.mail.ne1.yahoo.com> Date: Tue, 26 Feb 2013 22:41:23 -0800 (PST) From: Eric To: "xen-users@lists.xen.org" MIME-Version: 1.0 Subject: [Xen-users] Mysterious PVM's X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: Eric 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 I have a bit of a quandry: I've migrated two PVM's away from the SuSE-based= host system but they persist in Xend even though... =A0* they are not active on the host; = =A0* they're not in XenStore (/var/lib/xenstore/tdb), and; = =A0* there are no configuration files for the VM's (in /etc/xen/vm): > xen2:~ # ls /etc/xen/vm > sles11-1=A0=A0sles11-1.xml xen2:~ # xm list > Name=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0= =A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0ID=A0=A0 Mem VCPUs=A0=A0= =A0=A0=A0=A0State=A0=A0 Time(s) > Domain-0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0= =A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 0=A0=A0 502=A0=A0=A0=A0 2=A0= =A0=A0=A0 r-----=A0=A0 6185.1 > oracle1=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0= =A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0786=A0=A0=A0=A0= 1=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A015.3 > oracle2=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0= =A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0786=A0=A0=A0=A0= 1=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A014.0 > = > xen2:~ # xenstore-ls | grep "name =3D " = > name =3D "Domain-0" > name =3D "Pool-0" = > pool_name =3D "Pool-0" > name =3D "Domain-0" And, in fact, the PVM's can still be restarted even though... =A0 =A0* there are no configuration files stored locally (in /etc/xen/vm) and =A0* there's no information stored in XenStore. >=A0 xen2:~ # xm list >=A0 Name=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0= =A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 ID=A0=A0 Mem VCPUs=A0= =A0=A0=A0=A0 State=A0=A0 Time(s) >=A0 Domain-0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0= =A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 0=A0=A0 502=A0=A0=A0=A0 2= =A0=A0=A0=A0 r-----=A0=A0=A0=A0 40.1 >=A0 oracle1=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0= =A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 786=A0=A0=A0= =A0 1=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 18.2 >=A0 oracle2=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0= =A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 786=A0=A0=A0= =A0 1=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 16.9 >=A0 = >=A0 xen2:~ # xm start oracle1 >=A0 = >=A0 xen2:~ # xm start oracle2 >=A0 = >=A0 xen2:~ # xm list >=A0 Name=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0= =A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 ID=A0=A0 Mem VCPUs=A0= =A0=A0=A0=A0 State=A0=A0 Time(s) >=A0 Domain-0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0= =A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 0=A0=A0 502=A0=A0=A0=A0 2= =A0=A0=A0=A0 r-----=A0=A0=A0=A0 62.8 >=A0 oracle1=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=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=A0=A0 786=A0=A0=A0=A0 1= =A0=A0=A0=A0 ------=A0=A0=A0=A0 10.8 >=A0 oracle2=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0= =A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 2=A0=A0 786=A0=A0=A0=A0 1= =A0=A0=A0=A0 r-----=A0=A0=A0=A0=A0 2.8 Where is this configurationo information being stored? = Eric Pretorious Truckee, CA _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Wed Feb 27 06:47:28 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 27 Feb 2013 06:47: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 1UAamc-00074w-7C; Wed, 27 Feb 2013 06:46:30 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UAama-00074p-PW for xen-users@lists.xen.org; Wed, 27 Feb 2013 06:46:29 +0000 Received: from [193.109.254.147:32323] by server-1.bemta-14.messagelabs.com id 4C/FD-29874-4CBAD215; Wed, 27 Feb 2013 06:46:28 +0000 X-Env-Sender: epretorious@yahoo.com X-Msg-Ref: server-4.tower-27.messagelabs.com!1361947582!9182169!1 X-Originating-IP: [98.138.91.151] X-SpamReason: No, hits=0.0 required=7.0 tests=ML_RADAR_SPEW_LINKS_12, ML_RADAR_SPEW_LINKS_14,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 3437 invoked from network); 27 Feb 2013 06:46:24 -0000 Received: from nm21-vm3.bullet.mail.ne1.yahoo.com (HELO nm21-vm3.bullet.mail.ne1.yahoo.com) (98.138.91.151) by server-4.tower-27.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 27 Feb 2013 06:46:24 -0000 Received: from [98.138.90.51] by nm21.bullet.mail.ne1.yahoo.com with NNFMP; 27 Feb 2013 06:46:22 -0000 Received: from [98.138.226.168] by tm4.bullet.mail.ne1.yahoo.com with NNFMP; 27 Feb 2013 06:46:22 -0000 Received: from [127.0.0.1] by omp1069.mail.ne1.yahoo.com with NNFMP; 27 Feb 2013 06:46:22 -0000 X-Yahoo-Newman-Property: ymail-3 X-Yahoo-Newman-Id: 546269.71329.bm@omp1069.mail.ne1.yahoo.com Received: (qmail 66378 invoked by uid 60001); 27 Feb 2013 06:46:22 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1361947582; bh=p9EJ3x4vWxl7+D8ilqNGtoyhoQpn68HKkQDvICvmSJQ=; h=X-YMail-OSG:Received:X-Rocket-MIMEInfo:X-Mailer:Message-ID:Date:From:Reply-To:Subject:To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=RFspaJX0Zd+B7mIbfYiJB1RP2Cuy7ucBeY+804iX9ZtK+mvsA4wAXfRDlqiYvSKkxZYr5tD26Hs+cFIKRyhSlx0ca9tATHLQg/SpVd+qMz4pNK+gyQh+aW6orIvqTkoSjRJyEQAOmfALpRt+b1XfkBjA9e2YY4jiSZSh9hsLXXo= DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=X-YMail-OSG:Received:X-Rocket-MIMEInfo:X-Mailer:Message-ID:Date:From:Reply-To:Subject:To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=nVIVOfJ9zy41V9mV47YlhLOP5/sJv9qMe9C8F/+Tzbcf7fLgiT93YchgwWrm+kguOQ9MdMHNhMpeNIAcZ6jjl1rk2a1dl40AvpsHHEqoGzYd30ifeMEWxSXaSJ0SSfmR3BcrCxIF2WRY6aPgTrJN3/SZqvqVoQWn11qg5+FtHRI=; X-YMail-OSG: zaRCpKcVM1kWbOIx9_gN4QbhfoplGH6Zdt7PUOziTdyntWG hhunUBtFmY7uHcOVJSjcmB9BkwT459psiG6VTm4OLnsCd4BQzRk3IRmTPRup CgS5ugMP.4IzEndqjkKlDNGABv9_XKd8yH5w00bju1Tll_XT.BxuStplPNhE CCRbnyZPB67MPRQkGGCLEdYYKf51ZNz30hA2MmEJeCblPYD0puebF9UNd0LI m9V74ZRr8xfwOTUFGHcrn4BUjNXw2DfBi9pdw5kBCDPy_L.1kC.IX5MR0DE2 5VIii9tw0_PmaltquOuieYRXxq3MNEfI_I_JHq3RAT5SbLv2SUN.2aGBw8Fh KGAMhh.7Cd_zNpolXZSFZTq6.g9RnpQw1kw8JjEjCTo42LanXMxhHBcRc8zk q87Z3snLQ3ce4UfKleeIO6oi7cIMIWR8rAVAB4I2G7JvZS2qIn2c3GCjnfz5 nmFyvxIuuEqDz3nRioTfKihnsaQJbDFqURQK2ICyJoiYBu1MD1BH9wxteELW BDuHkp1nPjvWc93r5baACJdoH.ErMmOEGLWho8UjPKNveUqXTggXt4uDCnp6 SWSo1Eg6npNSGN1k09WVs_CWaXuZmoRCcCH0AGz4jRpmYKxgxqTcxvmqYjqo 9e94eTjcKkG0NJ5.q Received: from [74.197.253.230] by web126001.mail.ne1.yahoo.com via HTTP; Tue, 26 Feb 2013 22:46:22 PST X-Rocket-MIMEInfo: 001.001, SSBjcmVhdGVkIGEgY291cGxlIG9mIE9MNi1VMyBQVk0ncyBvbiBhIFN1U0UtWGVuIGhvc3QgKHVzaW5nIHZpcnQtaW5zdGFsbCkgYW5kIG1hbnVhbGx5IG1pZ3JhdGVkIHRoZSBWTSdzIHRvIG15IE9yYWNsZSBWTSBTZXJ2ZXIgaG9zdC4gVGhlIG1pZ3JhdGlvbiB3YXMgc3VjY2Vzc2Z1bC4gSG93ZXZlciwgdGhlIFZNJ3MgYXJlbid0IHBlcnNpc3RlbnQuIGkuZS4sIHRoZSBWTSdzIHdvbid0IHN1cnZpdmUgYSByZWJvb3Q6Cgo.wqAgW3Jvb3RAeGVuMyB.XSMgeG0gbGlzdAo.wqAgTmFtZcKgwqDCoMKgwqDCoAEwAQEBAQ-- X-Mailer: YahooMailWebService/0.8.135.514 Message-ID: <1361947582.56015.YahooMailNeo@web126001.mail.ne1.yahoo.com> Date: Tue, 26 Feb 2013 22:46:22 -0800 (PST) From: Eric To: "xen-users@lists.xen.org" MIME-Version: 1.0 Subject: [Xen-users] VM Persistence? X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: Eric 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 I created a couple of OL6-U3 PVM's on a SuSE-Xen host (using virt-install) = and manually migrated the VM's to my Oracle VM Server host. The migration w= as successful. However, the VM's aren't persistent. i.e., the VM's won't su= rvive a reboot: >=A0 [root@xen3 ~]# xm list >=A0 Name=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0= =A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 ID=A0=A0 Mem VCPUs=A0= =A0=A0=A0=A0 State=A0=A0 Time(s) >=A0 Domain-0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0= =A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 0=A0=A0 568=A0=A0=A0=A0 2= =A0=A0=A0=A0 r-----=A0 34467.9 >=A0 oracle1=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=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=A0=A0 786=A0=A0=A0=A0 1= =A0=A0=A0=A0 -b----=A0=A0=A0=A0 58.2 >=A0 oracle2=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0= =A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 3=A0=A0 786=A0=A0=A0=A0 1= =A0=A0=A0=A0 -b----=A0=A0=A0=A0 58.2 >=A0=A0 = >=A0 [root@xen3 ~]# xenstore-ls | grep '=A0=A0 name =3D' >=A0=A0=A0=A0 name =3D "Domain-0" >=A0=A0=A0=A0 name =3D "oracle1" >=A0=A0=A0=A0 name =3D "oracle2" >=A0=A0=A0=A0 name =3D "Pool-0" >=A0=A0 = >=A0 [root@xen3 ~]# xm shutdown oracle1 >=A0 [root@xen3 ~]# xm shutdown oracle2 >=A0=A0 = >=A0 [root@xen3 ~]# xm list >=A0 Name=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0= =A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 ID=A0=A0 Mem VCPUs=A0= =A0=A0=A0=A0 State=A0=A0 Time(s) >=A0 Domain-0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0= =A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 0=A0=A0 568=A0=A0=A0=A0 2= =A0=A0=A0=A0 r-----=A0 34564.1 >=A0=A0 = >=A0 [root@xen3 ~]# xm start oracle1 >=A0 Error: Domain 'oracle1' does not exist. I've noticed that there aren't any configuration files in /etc/xen: >=A0 [root@xen3 ~]# ls -1 /etc/xen >=A0 auto >=A0 cpupool >=A0 README >=A0 README.incompatibilities >=A0 scripts >=A0 xend-config.sxp >=A0 xend-pci-permissive.sxp >=A0 xend-pci-quirks.sxp >=A0 xl.conf >=A0 xm-config.xml >=A0 xmexample1 >=A0 xmexample2 >=A0 xmexample3 >=A0 xmexample.hvm >=A0 xmexample.hvm-stubdom >=A0 xmexample.nbd >=A0 xmexample.pv-grub >=A0 xmexample.vti > = >=A0 [root@xen3 ~]# ls -1 /etc/xen/auto/ ...and that if I try the method recommended in Chapter 5.3, Configuring a V= irtual Machine by Modifying its Xend Settings, of the SuSE manual Virtualiz= ation with Xen, Xend complains: >=A0 [root@xen3 ~]# xm new -F ~/oracle1.cfg >=A0 Unexpected error: exceptions.ImportError >=A0=A0 = >=A0 Please report to xen-devel@lists.xensource.com >=A0 Traceback (most recent call last): >=A0=A0=A0 File "/usr/sbin/xm", line 7, in ? >=A0=A0=A0=A0=A0 main.main(sys.argv) >=A0=A0=A0 File "/usr/lib64/python2.4/site-packages/xen/xm/main.py", line 3= 983, in main >=A0=A0=A0=A0=A0 _, rc =3D _run_cmd(cmd, cmd_name, args) >=A0=A0=A0 File "/usr/lib64/python2.4/site-packages/xen/xm/main.py", line 4= 007, in _run_cmd >=A0=A0=A0=A0=A0 return True, cmd(args) >=A0=A0=A0 File "", line 1, in >=A0=A0=A0 File "/usr/lib64/python2.4/site-packages/xen/xm/main.py", line 1= 518, in xm_importcommand >=A0=A0=A0=A0=A0 cmd =3D __import__(command, globals(), locals(), 'xen.xm') >=A0=A0=A0 File "/usr/lib64/python2.4/site-packages/xen/xm/new.py", line 26= , in ? >=A0=A0=A0=A0=A0 from xen.xm.xenapi_create import * >=A0=A0=A0 File "/usr/lib64/python2.4/site-packages/xen/xm/xenapi_create.py= ", line 25, in ? >=A0=A0=A0=A0=A0 from lxml import etree >=A0 ImportError: No module named lxml How can I make these VM's persistent? Eric Pretorious Truckee, CA _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Wed Feb 27 06:47:28 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 27 Feb 2013 06:47: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 1UAamc-00074w-7C; Wed, 27 Feb 2013 06:46:30 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UAama-00074p-PW for xen-users@lists.xen.org; Wed, 27 Feb 2013 06:46:29 +0000 Received: from [193.109.254.147:32323] by server-1.bemta-14.messagelabs.com id 4C/FD-29874-4CBAD215; Wed, 27 Feb 2013 06:46:28 +0000 X-Env-Sender: epretorious@yahoo.com X-Msg-Ref: server-4.tower-27.messagelabs.com!1361947582!9182169!1 X-Originating-IP: [98.138.91.151] X-SpamReason: No, hits=0.0 required=7.0 tests=ML_RADAR_SPEW_LINKS_12, ML_RADAR_SPEW_LINKS_14,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 3437 invoked from network); 27 Feb 2013 06:46:24 -0000 Received: from nm21-vm3.bullet.mail.ne1.yahoo.com (HELO nm21-vm3.bullet.mail.ne1.yahoo.com) (98.138.91.151) by server-4.tower-27.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 27 Feb 2013 06:46:24 -0000 Received: from [98.138.90.51] by nm21.bullet.mail.ne1.yahoo.com with NNFMP; 27 Feb 2013 06:46:22 -0000 Received: from [98.138.226.168] by tm4.bullet.mail.ne1.yahoo.com with NNFMP; 27 Feb 2013 06:46:22 -0000 Received: from [127.0.0.1] by omp1069.mail.ne1.yahoo.com with NNFMP; 27 Feb 2013 06:46:22 -0000 X-Yahoo-Newman-Property: ymail-3 X-Yahoo-Newman-Id: 546269.71329.bm@omp1069.mail.ne1.yahoo.com Received: (qmail 66378 invoked by uid 60001); 27 Feb 2013 06:46:22 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1361947582; bh=p9EJ3x4vWxl7+D8ilqNGtoyhoQpn68HKkQDvICvmSJQ=; h=X-YMail-OSG:Received:X-Rocket-MIMEInfo:X-Mailer:Message-ID:Date:From:Reply-To:Subject:To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=RFspaJX0Zd+B7mIbfYiJB1RP2Cuy7ucBeY+804iX9ZtK+mvsA4wAXfRDlqiYvSKkxZYr5tD26Hs+cFIKRyhSlx0ca9tATHLQg/SpVd+qMz4pNK+gyQh+aW6orIvqTkoSjRJyEQAOmfALpRt+b1XfkBjA9e2YY4jiSZSh9hsLXXo= DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=X-YMail-OSG:Received:X-Rocket-MIMEInfo:X-Mailer:Message-ID:Date:From:Reply-To:Subject:To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=nVIVOfJ9zy41V9mV47YlhLOP5/sJv9qMe9C8F/+Tzbcf7fLgiT93YchgwWrm+kguOQ9MdMHNhMpeNIAcZ6jjl1rk2a1dl40AvpsHHEqoGzYd30ifeMEWxSXaSJ0SSfmR3BcrCxIF2WRY6aPgTrJN3/SZqvqVoQWn11qg5+FtHRI=; X-YMail-OSG: zaRCpKcVM1kWbOIx9_gN4QbhfoplGH6Zdt7PUOziTdyntWG hhunUBtFmY7uHcOVJSjcmB9BkwT459psiG6VTm4OLnsCd4BQzRk3IRmTPRup CgS5ugMP.4IzEndqjkKlDNGABv9_XKd8yH5w00bju1Tll_XT.BxuStplPNhE CCRbnyZPB67MPRQkGGCLEdYYKf51ZNz30hA2MmEJeCblPYD0puebF9UNd0LI m9V74ZRr8xfwOTUFGHcrn4BUjNXw2DfBi9pdw5kBCDPy_L.1kC.IX5MR0DE2 5VIii9tw0_PmaltquOuieYRXxq3MNEfI_I_JHq3RAT5SbLv2SUN.2aGBw8Fh KGAMhh.7Cd_zNpolXZSFZTq6.g9RnpQw1kw8JjEjCTo42LanXMxhHBcRc8zk q87Z3snLQ3ce4UfKleeIO6oi7cIMIWR8rAVAB4I2G7JvZS2qIn2c3GCjnfz5 nmFyvxIuuEqDz3nRioTfKihnsaQJbDFqURQK2ICyJoiYBu1MD1BH9wxteELW BDuHkp1nPjvWc93r5baACJdoH.ErMmOEGLWho8UjPKNveUqXTggXt4uDCnp6 SWSo1Eg6npNSGN1k09WVs_CWaXuZmoRCcCH0AGz4jRpmYKxgxqTcxvmqYjqo 9e94eTjcKkG0NJ5.q Received: from [74.197.253.230] by web126001.mail.ne1.yahoo.com via HTTP; Tue, 26 Feb 2013 22:46:22 PST X-Rocket-MIMEInfo: 001.001, SSBjcmVhdGVkIGEgY291cGxlIG9mIE9MNi1VMyBQVk0ncyBvbiBhIFN1U0UtWGVuIGhvc3QgKHVzaW5nIHZpcnQtaW5zdGFsbCkgYW5kIG1hbnVhbGx5IG1pZ3JhdGVkIHRoZSBWTSdzIHRvIG15IE9yYWNsZSBWTSBTZXJ2ZXIgaG9zdC4gVGhlIG1pZ3JhdGlvbiB3YXMgc3VjY2Vzc2Z1bC4gSG93ZXZlciwgdGhlIFZNJ3MgYXJlbid0IHBlcnNpc3RlbnQuIGkuZS4sIHRoZSBWTSdzIHdvbid0IHN1cnZpdmUgYSByZWJvb3Q6Cgo.wqAgW3Jvb3RAeGVuMyB.XSMgeG0gbGlzdAo.wqAgTmFtZcKgwqDCoMKgwqDCoAEwAQEBAQ-- X-Mailer: YahooMailWebService/0.8.135.514 Message-ID: <1361947582.56015.YahooMailNeo@web126001.mail.ne1.yahoo.com> Date: Tue, 26 Feb 2013 22:46:22 -0800 (PST) From: Eric To: "xen-users@lists.xen.org" MIME-Version: 1.0 Subject: [Xen-users] VM Persistence? X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: Eric 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 I created a couple of OL6-U3 PVM's on a SuSE-Xen host (using virt-install) = and manually migrated the VM's to my Oracle VM Server host. The migration w= as successful. However, the VM's aren't persistent. i.e., the VM's won't su= rvive a reboot: >=A0 [root@xen3 ~]# xm list >=A0 Name=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0= =A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 ID=A0=A0 Mem VCPUs=A0= =A0=A0=A0=A0 State=A0=A0 Time(s) >=A0 Domain-0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0= =A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 0=A0=A0 568=A0=A0=A0=A0 2= =A0=A0=A0=A0 r-----=A0 34467.9 >=A0 oracle1=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=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=A0=A0 786=A0=A0=A0=A0 1= =A0=A0=A0=A0 -b----=A0=A0=A0=A0 58.2 >=A0 oracle2=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0= =A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 3=A0=A0 786=A0=A0=A0=A0 1= =A0=A0=A0=A0 -b----=A0=A0=A0=A0 58.2 >=A0=A0 = >=A0 [root@xen3 ~]# xenstore-ls | grep '=A0=A0 name =3D' >=A0=A0=A0=A0 name =3D "Domain-0" >=A0=A0=A0=A0 name =3D "oracle1" >=A0=A0=A0=A0 name =3D "oracle2" >=A0=A0=A0=A0 name =3D "Pool-0" >=A0=A0 = >=A0 [root@xen3 ~]# xm shutdown oracle1 >=A0 [root@xen3 ~]# xm shutdown oracle2 >=A0=A0 = >=A0 [root@xen3 ~]# xm list >=A0 Name=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0= =A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 ID=A0=A0 Mem VCPUs=A0= =A0=A0=A0=A0 State=A0=A0 Time(s) >=A0 Domain-0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0= =A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 0=A0=A0 568=A0=A0=A0=A0 2= =A0=A0=A0=A0 r-----=A0 34564.1 >=A0=A0 = >=A0 [root@xen3 ~]# xm start oracle1 >=A0 Error: Domain 'oracle1' does not exist. I've noticed that there aren't any configuration files in /etc/xen: >=A0 [root@xen3 ~]# ls -1 /etc/xen >=A0 auto >=A0 cpupool >=A0 README >=A0 README.incompatibilities >=A0 scripts >=A0 xend-config.sxp >=A0 xend-pci-permissive.sxp >=A0 xend-pci-quirks.sxp >=A0 xl.conf >=A0 xm-config.xml >=A0 xmexample1 >=A0 xmexample2 >=A0 xmexample3 >=A0 xmexample.hvm >=A0 xmexample.hvm-stubdom >=A0 xmexample.nbd >=A0 xmexample.pv-grub >=A0 xmexample.vti > = >=A0 [root@xen3 ~]# ls -1 /etc/xen/auto/ ...and that if I try the method recommended in Chapter 5.3, Configuring a V= irtual Machine by Modifying its Xend Settings, of the SuSE manual Virtualiz= ation with Xen, Xend complains: >=A0 [root@xen3 ~]# xm new -F ~/oracle1.cfg >=A0 Unexpected error: exceptions.ImportError >=A0=A0 = >=A0 Please report to xen-devel@lists.xensource.com >=A0 Traceback (most recent call last): >=A0=A0=A0 File "/usr/sbin/xm", line 7, in ? >=A0=A0=A0=A0=A0 main.main(sys.argv) >=A0=A0=A0 File "/usr/lib64/python2.4/site-packages/xen/xm/main.py", line 3= 983, in main >=A0=A0=A0=A0=A0 _, rc =3D _run_cmd(cmd, cmd_name, args) >=A0=A0=A0 File "/usr/lib64/python2.4/site-packages/xen/xm/main.py", line 4= 007, in _run_cmd >=A0=A0=A0=A0=A0 return True, cmd(args) >=A0=A0=A0 File "", line 1, in >=A0=A0=A0 File "/usr/lib64/python2.4/site-packages/xen/xm/main.py", line 1= 518, in xm_importcommand >=A0=A0=A0=A0=A0 cmd =3D __import__(command, globals(), locals(), 'xen.xm') >=A0=A0=A0 File "/usr/lib64/python2.4/site-packages/xen/xm/new.py", line 26= , in ? >=A0=A0=A0=A0=A0 from xen.xm.xenapi_create import * >=A0=A0=A0 File "/usr/lib64/python2.4/site-packages/xen/xm/xenapi_create.py= ", line 25, in ? >=A0=A0=A0=A0=A0 from lxml import etree >=A0 ImportError: No module named lxml How can I make these VM's persistent? Eric Pretorious Truckee, CA _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Wed Feb 27 06:55:38 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 27 Feb 2013 06:55: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 1UAauW-0007Ss-Ec; Wed, 27 Feb 2013 06:54:40 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UAauV-0007Sj-2x for xen-users@lists.xen.org; Wed, 27 Feb 2013 06:54:39 +0000 Received: from [85.158.139.211:60360] by server-12.bemta-5.messagelabs.com id 3E/50-11486-EADAD215; Wed, 27 Feb 2013 06:54:38 +0000 X-Env-Sender: epretorious@yahoo.com X-Msg-Ref: server-13.tower-206.messagelabs.com!1361948070!15481675!1 X-Originating-IP: [98.138.90.63] 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_6, spamassassin: X-StarScan-Received: X-StarScan-Version: 6.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 12161 invoked from network); 27 Feb 2013 06:54:37 -0000 Received: from unknown (HELO nm29-vm1.bullet.mail.ne1.yahoo.com) (98.138.90.63) by server-13.tower-206.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 27 Feb 2013 06:54:37 -0000 Received: from [98.138.226.179] by nm29.bullet.mail.ne1.yahoo.com with NNFMP; 27 Feb 2013 06:53:25 -0000 Received: from [98.138.89.172] by tm14.bullet.mail.ne1.yahoo.com with NNFMP; 27 Feb 2013 06:53:25 -0000 Received: from [127.0.0.1] by omp1028.mail.ne1.yahoo.com with NNFMP; 27 Feb 2013 06:53:25 -0000 X-Yahoo-Newman-Property: ymail-3 X-Yahoo-Newman-Id: 637846.27623.bm@omp1028.mail.ne1.yahoo.com Received: (qmail 26301 invoked by uid 60001); 27 Feb 2013 06:53:25 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1361948005; bh=I+Pk/OySJRfH1NBhV3eT8g1Ym+FrCmi41W83XaoOM4c=; h=X-YMail-OSG:Received:X-Rocket-MIMEInfo:X-Mailer:References:Message-ID:Date:From:Reply-To:Subject:To:In-Reply-To:MIME-Version:Content-Type; b=M64OUC2lHdCJAF7EBHW1awEYn46Wy15u++i0DxcUAMBQgLbm2Qplkjq956+VDHqdazNTNF6IeTcEJ/hDDinpzRp1hKjWQSsFe4VEgZ8VxJSRjL/PQ0YdZCJUrvgBENZTZBZC0GlVlYd3/AVEzs/lZ7x9u3hUQHeHe1tTAZ0YiYQ= DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=X-YMail-OSG:Received:X-Rocket-MIMEInfo:X-Mailer:References:Message-ID:Date:From:Reply-To:Subject:To:In-Reply-To:MIME-Version:Content-Type; b=NzGG0aa1WXcd5SvMne0z6lz1hoVavrQwgHqr296aRtzlUVVz/MDGdekk3DeFUpV6f9PRPBa7YO+QJ6WcaYAMq8GiEBvSypzhGK19O/PPZzSMgdtvJctwFwrXjQ1FoM809qupwHCihQBQCiIyMB//mZ11TwMuqoo6i0H7ud/j2Pg=; X-YMail-OSG: wrKkwL4VM1mHO.yq2K8TdTqxwInXcTpgv9YsBytOglHuEuA l2WQG1h_uYdwBMpD3aUJYK2cShuTb299uB0XoM.j2xzbKrymrgCB6pxwKeyx 0VmaF4tVMdSUCmEHwZtBKdtA0uUA0cq1X0cSHbKu4hooQE1tFvHy2q_n_SaH sQYS1sKFamrfJs25DHewcjwVknEBmpEUeoDNtHONT90FcAYeldEfKTz7SY4U haFsCYXN.JoN5c6fLujT8tQRMAzX8B1jsEzr6eWJ7TVXWqFhinsklooqvEeS FqhmRm1uzN5WbvQBxuybJiGIVPRPHPrNjobzbzWYJLxO32KCqB_SATs5clyo NCdWA0HZnEDd0uVOXIKHWj3w1UJsqaDj4NGV5GpdFpzhzUs4Dim6NKr.rPmp avG9lbpECytvHrp1_JlfInbIhoErHxwkhFX1DAKTX8rodzCOwqlekwCSd7yh X4bagr3WSMGlkEQ_fzp_5kjk8mbNjAj5d2dE9NBVhNX.kLzCyZxpgK_B5.Yp 51GU.iNGXSQlCE3e4MCnV6G3kVt7ZpM5wRA_aTGpz8U0qmRAoEZ4_d6En9Ui 104y_Lkh36RhEs.KWRfHprCraspN9.FQIf72dfVWwqPJ3MLIdDuANBiVjlwx xDq_MN0_cmLyZY1GX1YU19BKC Received: from [74.197.253.230] by web126006.mail.ne1.yahoo.com via HTTP; Tue, 26 Feb 2013 22:53:25 PST X-Rocket-MIMEInfo: 001.001, SmFjZWs6CgovbG9jYWwvZG9tYWluIGlzbid0IGNyZWF0ZWQgYW55d2hlcmUuIEl0J3MgYSBuYW1lc3BhY2UgaW4gdGhlIFhlblN0b3JlIGRhdGFiYXNlICgvdmFyL2xpYi94ZW5zdG9yZS90ZGIpLgoKVGhpcyBleGNlcnB0IChmcm9tIHRoZSBQcmVudGljZSBIYWxsIGJvb2sgIlJ1bm5pbmcgWGVuIC0gQSBIYW5kcy1PbiBHdWlkZSB0byB0aGUgQXJ0IG9mIFZpcnR1YWxpemF0aW9uKSB3aWxsIGRvIGEgYmV0dGVyIGpvYiBvZiBleHBsYWluaW5nIHRoaXMgZmVhdHVyZSB0aGFuIEkgZXZlciBjb3VsZDogaHR0cDoBMAEBAQE- X-Mailer: YahooMailWebService/0.8.135.514 References: Message-ID: <1361948005.25966.YahooMailNeo@web126006.mail.ne1.yahoo.com> Date: Tue, 26 Feb 2013 22:53:25 -0800 (PST) From: Eric To: jacek burghardt , xen-users In-Reply-To: MIME-Version: 1.0 Subject: Re: [Xen-users] xenstored /local/domain X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: Eric List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1787538241283983781==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============1787538241283983781== Content-Type: multipart/alternative; boundary="1702328891-234375053-1361948005=:25966" --1702328891-234375053-1361948005=:25966 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Jacek:=0A=0A/local/domain isn't created anywhere. It's a namespace in the X= enStore database (/var/lib/xenstore/tdb).=0A=0AThis excerpt (from the Prent= ice Hall book "Running Xen - A Hands-On Guide to the Art of Virtualization)= will do a better job of explaining this feature than I ever could: http://= www.informit.com/articles/article.aspx?p=3D1187966&seqNum=3D1=0A=0AHTH,=0AE= ric Pretorious=0ATruckee, CA=0A=0A=0A=0A=0A=0A>____________________________= ____=0A> From: jacek burghardt =0A>To: xen-users= =0A>Sent: Tuesday, February 26, 2013 7:50 PM=0A>= Subject: [Xen-users] xenstored /local/domain=0A> =0A>=0A>Can somone tell me= where=A0 is local/domain created ?=0A>=0A>________________________________= _______________=0A>Xen-users mailing list=0A>Xen-users@lists.xen.org=0A>htt= p://lists.xen.org/xen-users=0A>=0A> --1702328891-234375053-1361948005=:25966 Content-Type: text/html; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable
Jacek:
/local/domain isn't created anywhere. It's a namespace in the XenStore= database (/var/lib/xenstore/tdb).

This excerpt (from the Prentice H= all book "Running Xen - A Hands-On Guide to the Art of Virtualization) will= do a better job of explaining this feature than I ever could: http://www.i= nformit.com/articles/article.aspx?p=3D1187966&seqNum=3D1

HTH,Eric Pretorious
Truckee, CA


From: jacek burghardt <jaceksbur= ghardt@gmail.com>
To: xen-users <xen-users@lists.xen.org>
Sent: Tuesday, February 26, 2013 7:50 PM
Subject: [Xen-users] xenstored /= local/domain

=0A
Can somone= tell me where  is local/domain created ?
=0A

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

=
--1702328891-234375053-1361948005=:25966-- --===============1787538241283983781== 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 --===============1787538241283983781==-- From xen-users-bounces@lists.xen.org Wed Feb 27 06:55:38 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 27 Feb 2013 06:55: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 1UAauW-0007Ss-Ec; Wed, 27 Feb 2013 06:54:40 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UAauV-0007Sj-2x for xen-users@lists.xen.org; Wed, 27 Feb 2013 06:54:39 +0000 Received: from [85.158.139.211:60360] by server-12.bemta-5.messagelabs.com id 3E/50-11486-EADAD215; Wed, 27 Feb 2013 06:54:38 +0000 X-Env-Sender: epretorious@yahoo.com X-Msg-Ref: server-13.tower-206.messagelabs.com!1361948070!15481675!1 X-Originating-IP: [98.138.90.63] 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_6, spamassassin: X-StarScan-Received: X-StarScan-Version: 6.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 12161 invoked from network); 27 Feb 2013 06:54:37 -0000 Received: from unknown (HELO nm29-vm1.bullet.mail.ne1.yahoo.com) (98.138.90.63) by server-13.tower-206.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 27 Feb 2013 06:54:37 -0000 Received: from [98.138.226.179] by nm29.bullet.mail.ne1.yahoo.com with NNFMP; 27 Feb 2013 06:53:25 -0000 Received: from [98.138.89.172] by tm14.bullet.mail.ne1.yahoo.com with NNFMP; 27 Feb 2013 06:53:25 -0000 Received: from [127.0.0.1] by omp1028.mail.ne1.yahoo.com with NNFMP; 27 Feb 2013 06:53:25 -0000 X-Yahoo-Newman-Property: ymail-3 X-Yahoo-Newman-Id: 637846.27623.bm@omp1028.mail.ne1.yahoo.com Received: (qmail 26301 invoked by uid 60001); 27 Feb 2013 06:53:25 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1361948005; bh=I+Pk/OySJRfH1NBhV3eT8g1Ym+FrCmi41W83XaoOM4c=; h=X-YMail-OSG:Received:X-Rocket-MIMEInfo:X-Mailer:References:Message-ID:Date:From:Reply-To:Subject:To:In-Reply-To:MIME-Version:Content-Type; b=M64OUC2lHdCJAF7EBHW1awEYn46Wy15u++i0DxcUAMBQgLbm2Qplkjq956+VDHqdazNTNF6IeTcEJ/hDDinpzRp1hKjWQSsFe4VEgZ8VxJSRjL/PQ0YdZCJUrvgBENZTZBZC0GlVlYd3/AVEzs/lZ7x9u3hUQHeHe1tTAZ0YiYQ= DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=X-YMail-OSG:Received:X-Rocket-MIMEInfo:X-Mailer:References:Message-ID:Date:From:Reply-To:Subject:To:In-Reply-To:MIME-Version:Content-Type; b=NzGG0aa1WXcd5SvMne0z6lz1hoVavrQwgHqr296aRtzlUVVz/MDGdekk3DeFUpV6f9PRPBa7YO+QJ6WcaYAMq8GiEBvSypzhGK19O/PPZzSMgdtvJctwFwrXjQ1FoM809qupwHCihQBQCiIyMB//mZ11TwMuqoo6i0H7ud/j2Pg=; X-YMail-OSG: wrKkwL4VM1mHO.yq2K8TdTqxwInXcTpgv9YsBytOglHuEuA l2WQG1h_uYdwBMpD3aUJYK2cShuTb299uB0XoM.j2xzbKrymrgCB6pxwKeyx 0VmaF4tVMdSUCmEHwZtBKdtA0uUA0cq1X0cSHbKu4hooQE1tFvHy2q_n_SaH sQYS1sKFamrfJs25DHewcjwVknEBmpEUeoDNtHONT90FcAYeldEfKTz7SY4U haFsCYXN.JoN5c6fLujT8tQRMAzX8B1jsEzr6eWJ7TVXWqFhinsklooqvEeS FqhmRm1uzN5WbvQBxuybJiGIVPRPHPrNjobzbzWYJLxO32KCqB_SATs5clyo NCdWA0HZnEDd0uVOXIKHWj3w1UJsqaDj4NGV5GpdFpzhzUs4Dim6NKr.rPmp avG9lbpECytvHrp1_JlfInbIhoErHxwkhFX1DAKTX8rodzCOwqlekwCSd7yh X4bagr3WSMGlkEQ_fzp_5kjk8mbNjAj5d2dE9NBVhNX.kLzCyZxpgK_B5.Yp 51GU.iNGXSQlCE3e4MCnV6G3kVt7ZpM5wRA_aTGpz8U0qmRAoEZ4_d6En9Ui 104y_Lkh36RhEs.KWRfHprCraspN9.FQIf72dfVWwqPJ3MLIdDuANBiVjlwx xDq_MN0_cmLyZY1GX1YU19BKC Received: from [74.197.253.230] by web126006.mail.ne1.yahoo.com via HTTP; Tue, 26 Feb 2013 22:53:25 PST X-Rocket-MIMEInfo: 001.001, SmFjZWs6CgovbG9jYWwvZG9tYWluIGlzbid0IGNyZWF0ZWQgYW55d2hlcmUuIEl0J3MgYSBuYW1lc3BhY2UgaW4gdGhlIFhlblN0b3JlIGRhdGFiYXNlICgvdmFyL2xpYi94ZW5zdG9yZS90ZGIpLgoKVGhpcyBleGNlcnB0IChmcm9tIHRoZSBQcmVudGljZSBIYWxsIGJvb2sgIlJ1bm5pbmcgWGVuIC0gQSBIYW5kcy1PbiBHdWlkZSB0byB0aGUgQXJ0IG9mIFZpcnR1YWxpemF0aW9uKSB3aWxsIGRvIGEgYmV0dGVyIGpvYiBvZiBleHBsYWluaW5nIHRoaXMgZmVhdHVyZSB0aGFuIEkgZXZlciBjb3VsZDogaHR0cDoBMAEBAQE- X-Mailer: YahooMailWebService/0.8.135.514 References: Message-ID: <1361948005.25966.YahooMailNeo@web126006.mail.ne1.yahoo.com> Date: Tue, 26 Feb 2013 22:53:25 -0800 (PST) From: Eric To: jacek burghardt , xen-users In-Reply-To: MIME-Version: 1.0 Subject: Re: [Xen-users] xenstored /local/domain X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: Eric List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1787538241283983781==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============1787538241283983781== Content-Type: multipart/alternative; boundary="1702328891-234375053-1361948005=:25966" --1702328891-234375053-1361948005=:25966 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Jacek:=0A=0A/local/domain isn't created anywhere. It's a namespace in the X= enStore database (/var/lib/xenstore/tdb).=0A=0AThis excerpt (from the Prent= ice Hall book "Running Xen - A Hands-On Guide to the Art of Virtualization)= will do a better job of explaining this feature than I ever could: http://= www.informit.com/articles/article.aspx?p=3D1187966&seqNum=3D1=0A=0AHTH,=0AE= ric Pretorious=0ATruckee, CA=0A=0A=0A=0A=0A=0A>____________________________= ____=0A> From: jacek burghardt =0A>To: xen-users= =0A>Sent: Tuesday, February 26, 2013 7:50 PM=0A>= Subject: [Xen-users] xenstored /local/domain=0A> =0A>=0A>Can somone tell me= where=A0 is local/domain created ?=0A>=0A>________________________________= _______________=0A>Xen-users mailing list=0A>Xen-users@lists.xen.org=0A>htt= p://lists.xen.org/xen-users=0A>=0A> --1702328891-234375053-1361948005=:25966 Content-Type: text/html; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable
Jacek:
/local/domain isn't created anywhere. It's a namespace in the XenStore= database (/var/lib/xenstore/tdb).

This excerpt (from the Prentice H= all book "Running Xen - A Hands-On Guide to the Art of Virtualization) will= do a better job of explaining this feature than I ever could: http://www.i= nformit.com/articles/article.aspx?p=3D1187966&seqNum=3D1

HTH,Eric Pretorious
Truckee, CA


From: jacek burghardt <jaceksbur= ghardt@gmail.com>
To: xen-users <xen-users@lists.xen.org>
Sent: Tuesday, February 26, 2013 7:50 PM
Subject: [Xen-users] xenstored /= local/domain

=0A
Can somone= tell me where  is local/domain created ?
=0A

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

=
--1702328891-234375053-1361948005=:25966-- --===============1787538241283983781== 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 --===============1787538241283983781==-- From xen-users-bounces@lists.xen.org Wed Feb 27 08:54:57 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 27 Feb 2013 08:54: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 1UAcln-0002BP-DX; Wed, 27 Feb 2013 08:53:47 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UAcll-0002BG-Ar for xen-users@lists.xen.org; Wed, 27 Feb 2013 08:53:45 +0000 Received: from [85.158.139.83:38055] by server-3.bemta-5.messagelabs.com id 11/4A-17256-899CD215; Wed, 27 Feb 2013 08:53:44 +0000 X-Env-Sender: Ian.Campbell@citrix.com X-Msg-Ref: server-16.tower-182.messagelabs.com!1361955223!21828512!1 X-Originating-IP: [46.33.159.39] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNDYuMzMuMTU5LjM5ID0+IDI0MzQ0\n X-StarScan-Received: X-StarScan-Version: 6.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 26570 invoked from network); 27 Feb 2013 08:53:43 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (46.33.159.39) by server-16.tower-182.messagelabs.com with RC4-SHA encrypted SMTP; 27 Feb 2013 08:53:43 -0000 X-IronPort-AV: E=Sophos;i="4.84,746,1355097600"; d="scan'208";a="1940031" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 27 Feb 2013 08:53:43 +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.297.1; Wed, 27 Feb 2013 08:53:43 +0000 Message-ID: <1361955223.11431.32.camel@dagon.hellion.org.uk> From: Ian Campbell To: Katerina Mparmpopoulou Date: Wed, 27 Feb 2013 08:53:43 +0000 In-Reply-To: References: Organization: Citrix Systems, Inc. X-Mailer: Evolution 3.4.4-1 MIME-Version: 1.0 Cc: "xen-users@lists.xen.org" Subject: Re: [Xen-users] Xen 4.2 - Security on Live Migration X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: 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, 2013-02-26 at 23:51 +0000, Katerina Mparmpopoulou wrote: > Is there any way that I can control the level of > security in Xen 4.2 considering Live Migration? Should I look in > specific libxl files?? The migration protocol is specific to the toolstack (xl) not the lower layer library (libxl, which is intended to be shared by all toolstacks). Check out the xl manpage, in particular the -e option to xl migrate, which lets you specify any command you like to act as the transport. Ian. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Wed Feb 27 08:54:57 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 27 Feb 2013 08:54: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 1UAcln-0002BP-DX; Wed, 27 Feb 2013 08:53:47 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UAcll-0002BG-Ar for xen-users@lists.xen.org; Wed, 27 Feb 2013 08:53:45 +0000 Received: from [85.158.139.83:38055] by server-3.bemta-5.messagelabs.com id 11/4A-17256-899CD215; Wed, 27 Feb 2013 08:53:44 +0000 X-Env-Sender: Ian.Campbell@citrix.com X-Msg-Ref: server-16.tower-182.messagelabs.com!1361955223!21828512!1 X-Originating-IP: [46.33.159.39] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNDYuMzMuMTU5LjM5ID0+IDI0MzQ0\n X-StarScan-Received: X-StarScan-Version: 6.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 26570 invoked from network); 27 Feb 2013 08:53:43 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (46.33.159.39) by server-16.tower-182.messagelabs.com with RC4-SHA encrypted SMTP; 27 Feb 2013 08:53:43 -0000 X-IronPort-AV: E=Sophos;i="4.84,746,1355097600"; d="scan'208";a="1940031" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 27 Feb 2013 08:53:43 +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.297.1; Wed, 27 Feb 2013 08:53:43 +0000 Message-ID: <1361955223.11431.32.camel@dagon.hellion.org.uk> From: Ian Campbell To: Katerina Mparmpopoulou Date: Wed, 27 Feb 2013 08:53:43 +0000 In-Reply-To: References: Organization: Citrix Systems, Inc. X-Mailer: Evolution 3.4.4-1 MIME-Version: 1.0 Cc: "xen-users@lists.xen.org" Subject: Re: [Xen-users] Xen 4.2 - Security on Live Migration X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: 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, 2013-02-26 at 23:51 +0000, Katerina Mparmpopoulou wrote: > Is there any way that I can control the level of > security in Xen 4.2 considering Live Migration? Should I look in > specific libxl files?? The migration protocol is specific to the toolstack (xl) not the lower layer library (libxl, which is intended to be shared by all toolstacks). Check out the xl manpage, in particular the -e option to xl migrate, which lets you specify any command you like to act as the transport. Ian. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Wed Feb 27 09:30:37 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 27 Feb 2013 09:30: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 1UAdKK-0003ED-BZ; Wed, 27 Feb 2013 09:29:28 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UAdKI-0003E3-CW for xen-users@lists.xen.org; Wed, 27 Feb 2013 09:29:26 +0000 Received: from [85.158.139.211:49470] by server-4.bemta-5.messagelabs.com id 03/02-01980-5F1DD215; Wed, 27 Feb 2013 09:29:25 +0000 X-Env-Sender: kate_mparmpop@hotmail.com X-Msg-Ref: server-14.tower-206.messagelabs.com!1361957357!19408001!1 X-Originating-IP: [65.55.111.83] X-SpamReason: No, hits=0.1 required=7.0 tests=FORGED_HOTMAIL_RCVD, ML_RADAR_SPEW_LINKS_12,ML_RADAR_SPEW_LINKS_14,MSGID_FROM_MTA_HEADER, spamassassin: X-StarScan-Received: X-StarScan-Version: 6.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 31592 invoked from network); 27 Feb 2013 09:29:18 -0000 Received: from blu0-omc2-s8.blu0.hotmail.com (HELO blu0-omc2-s8.blu0.hotmail.com) (65.55.111.83) by server-14.tower-206.messagelabs.com with SMTP; 27 Feb 2013 09:29:18 -0000 Received: from BLU0-SMTP434 ([65.55.111.72]) by blu0-omc2-s8.blu0.hotmail.com with Microsoft SMTPSVC(6.0.3790.4675); Wed, 27 Feb 2013 01:29:17 -0800 X-EIP: [73qD8r5f29iXt44iULePOSsz9bIkGmD0] X-Originating-Email: [kate_mparmpop@hotmail.com] Message-ID: Received: from [192.168.0.100] ([82.139.117.118]) by BLU0-SMTP434.phx.gbl over TLS secured channel with Microsoft SMTPSVC(6.0.3790.4675); Wed, 27 Feb 2013 01:29:15 -0800 Date: Wed, 27 Feb 2013 10:29:13 +0100 From: Katerina Mparmpopoulou User-Agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/20130221 Thunderbird/17.0.3 MIME-Version: 1.0 To: Ian Campbell References: <1361955223.11431.32.camel@dagon.hellion.org.uk> In-Reply-To: <1361955223.11431.32.camel@dagon.hellion.org.uk> X-Enigmail-Version: 1.5 X-OriginalArrivalTime: 27 Feb 2013 09:29:16.0060 (UTC) FILETIME=[E950E5C0:01CE14CC] Cc: "xen-users@lists.xen.org" Subject: Re: [Xen-users] Xen 4.2 - Security on Live Migration X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: 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 Hello Ian, Thanks for the quick reply, > Check out the xl manpage, in particular the -e option to xl > migrate, which lets you specify any command you like to act as the > transport. I have checked already the xl manpage and also the migrate subcommand. I thought that the -s sshcommand was the most relevant for me, but still i don't know how i can use it efficiently. If i want to place my own ssl key and my own certificate when i'm migrating a vm in another physical machine, how should I use the command?? Regards, Katerina -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQEcBAEBAgAGBQJRLdHpAAoJEIrShLVVnSKrBlIH/0w4FUW1n4bsnJyBOl71MMZV mPdzRumLHz7k3rtjnu87yxaQbNQYwlm3YMs5pJs3/44LGepp+mRj2Ixx86VhfJw0 qySpAt48Yy/ZVA5gmIJB/S79M7CXtHtBfcgh7DFy9U1CvWVFqdkqUxvxoBUEfpsH plzOHerp0EQ/Mpf/hYMm/bJvwQxv8XSvExQcWWKmlpE4bdhFIEtzQqOepH/2S0rw hgdF2tGVdMlljRPizIFOZF1kgTtkZ5BwBwwr6fD0R86jGEiDFeLFGS0m0O614whI kMxxpB8ZFiYzxO1G5+g/K3eohaphO0iWe23upYA72d7l4PpgRe6jQX2EvfDPXk8= =BLnp -----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 Wed Feb 27 09:30:37 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 27 Feb 2013 09:30: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 1UAdKK-0003ED-BZ; Wed, 27 Feb 2013 09:29:28 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UAdKI-0003E3-CW for xen-users@lists.xen.org; Wed, 27 Feb 2013 09:29:26 +0000 Received: from [85.158.139.211:49470] by server-4.bemta-5.messagelabs.com id 03/02-01980-5F1DD215; Wed, 27 Feb 2013 09:29:25 +0000 X-Env-Sender: kate_mparmpop@hotmail.com X-Msg-Ref: server-14.tower-206.messagelabs.com!1361957357!19408001!1 X-Originating-IP: [65.55.111.83] X-SpamReason: No, hits=0.1 required=7.0 tests=FORGED_HOTMAIL_RCVD, ML_RADAR_SPEW_LINKS_12,ML_RADAR_SPEW_LINKS_14,MSGID_FROM_MTA_HEADER, spamassassin: X-StarScan-Received: X-StarScan-Version: 6.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 31592 invoked from network); 27 Feb 2013 09:29:18 -0000 Received: from blu0-omc2-s8.blu0.hotmail.com (HELO blu0-omc2-s8.blu0.hotmail.com) (65.55.111.83) by server-14.tower-206.messagelabs.com with SMTP; 27 Feb 2013 09:29:18 -0000 Received: from BLU0-SMTP434 ([65.55.111.72]) by blu0-omc2-s8.blu0.hotmail.com with Microsoft SMTPSVC(6.0.3790.4675); Wed, 27 Feb 2013 01:29:17 -0800 X-EIP: [73qD8r5f29iXt44iULePOSsz9bIkGmD0] X-Originating-Email: [kate_mparmpop@hotmail.com] Message-ID: Received: from [192.168.0.100] ([82.139.117.118]) by BLU0-SMTP434.phx.gbl over TLS secured channel with Microsoft SMTPSVC(6.0.3790.4675); Wed, 27 Feb 2013 01:29:15 -0800 Date: Wed, 27 Feb 2013 10:29:13 +0100 From: Katerina Mparmpopoulou User-Agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/20130221 Thunderbird/17.0.3 MIME-Version: 1.0 To: Ian Campbell References: <1361955223.11431.32.camel@dagon.hellion.org.uk> In-Reply-To: <1361955223.11431.32.camel@dagon.hellion.org.uk> X-Enigmail-Version: 1.5 X-OriginalArrivalTime: 27 Feb 2013 09:29:16.0060 (UTC) FILETIME=[E950E5C0:01CE14CC] Cc: "xen-users@lists.xen.org" Subject: Re: [Xen-users] Xen 4.2 - Security on Live Migration X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: 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 Hello Ian, Thanks for the quick reply, > Check out the xl manpage, in particular the -e option to xl > migrate, which lets you specify any command you like to act as the > transport. I have checked already the xl manpage and also the migrate subcommand. I thought that the -s sshcommand was the most relevant for me, but still i don't know how i can use it efficiently. If i want to place my own ssl key and my own certificate when i'm migrating a vm in another physical machine, how should I use the command?? Regards, Katerina -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQEcBAEBAgAGBQJRLdHpAAoJEIrShLVVnSKrBlIH/0w4FUW1n4bsnJyBOl71MMZV mPdzRumLHz7k3rtjnu87yxaQbNQYwlm3YMs5pJs3/44LGepp+mRj2Ixx86VhfJw0 qySpAt48Yy/ZVA5gmIJB/S79M7CXtHtBfcgh7DFy9U1CvWVFqdkqUxvxoBUEfpsH plzOHerp0EQ/Mpf/hYMm/bJvwQxv8XSvExQcWWKmlpE4bdhFIEtzQqOepH/2S0rw hgdF2tGVdMlljRPizIFOZF1kgTtkZ5BwBwwr6fD0R86jGEiDFeLFGS0m0O614whI kMxxpB8ZFiYzxO1G5+g/K3eohaphO0iWe23upYA72d7l4PpgRe6jQX2EvfDPXk8= =BLnp -----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 Wed Feb 27 10:42:21 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 27 Feb 2013 10:42: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 1UAeRt-000600-TT; Wed, 27 Feb 2013 10:41:21 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UAeRs-0005zq-Br for xen-users@lists.xen.org; Wed, 27 Feb 2013 10:41:20 +0000 Received: from [85.158.143.99:27226] by server-2.bemta-4.messagelabs.com id 54/70-12656-FC2ED215; Wed, 27 Feb 2013 10:41:19 +0000 X-Env-Sender: Ian.Campbell@citrix.com X-Msg-Ref: server-13.tower-216.messagelabs.com!1361961650!28487623!1 X-Originating-IP: [46.33.159.39] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNDYuMzMuMTU5LjM5ID0+IDI0NTI3\n X-StarScan-Received: X-StarScan-Version: 6.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 7883 invoked from network); 27 Feb 2013 10:40:50 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (46.33.159.39) by server-13.tower-216.messagelabs.com with RC4-SHA encrypted SMTP; 27 Feb 2013 10:40:50 -0000 X-IronPort-AV: E=Sophos;i="4.84,746,1355097600"; d="scan'208";a="1946225" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 27 Feb 2013 10:40:50 +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.297.1; Wed, 27 Feb 2013 10:40:49 +0000 Message-ID: <1361961648.26546.338.camel@zakaz.uk.xensource.com> From: Ian Campbell To: Katerina Mparmpopoulou Date: Wed, 27 Feb 2013 10:40:48 +0000 In-Reply-To: References: <1361955223.11431.32.camel@dagon.hellion.org.uk> Organization: Citrix Systems, Inc. X-Mailer: Evolution 3.4.4-1 MIME-Version: 1.0 Cc: "xen-users@lists.xen.org" Subject: Re: [Xen-users] Xen 4.2 - Security on Live Migration X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: 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, 2013-02-27 at 09:29 +0000, Katerina Mparmpopoulou wrote: > Hello Ian, > > Thanks for the quick reply, > > > Check out the xl manpage, in particular the -e option to xl > > migrate, which lets you specify any command you like to act as the > > transport. > > I have checked already the xl manpage and also the migrate subcommand. > > I thought that the -s sshcommand was the most relevant for me, but > still i don't know how i can use it efficiently. Sorry. I meant -s, I didn't have the manpage handy when I wrote -e. > > If i want to place my own ssl key and my own certificate when i'm > migrating a vm in another physical machine, how should I use the command?? You need to pass a command which will connect its stdin/stdout over the communication channel of your choice to the stdin/stdout of "xl migrate-receive" running on the target host. How you setup that communication channel and arrange for that process on the remote machine is up to you to arrange in that command. For example you could reasonably trivially build something out of netcat and ssh which did secure authentication and but insecure data transfer. If you want to do something with SSL certs then I expect you will wantto find an ssl capable netcat type thing, I think openssl has such mechanisms in it. Or you could write your own client/server pair, etc etc. Ian. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Wed Feb 27 10:42:21 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 27 Feb 2013 10:42: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 1UAeRt-000600-TT; Wed, 27 Feb 2013 10:41:21 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UAeRs-0005zq-Br for xen-users@lists.xen.org; Wed, 27 Feb 2013 10:41:20 +0000 Received: from [85.158.143.99:27226] by server-2.bemta-4.messagelabs.com id 54/70-12656-FC2ED215; Wed, 27 Feb 2013 10:41:19 +0000 X-Env-Sender: Ian.Campbell@citrix.com X-Msg-Ref: server-13.tower-216.messagelabs.com!1361961650!28487623!1 X-Originating-IP: [46.33.159.39] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNDYuMzMuMTU5LjM5ID0+IDI0NTI3\n X-StarScan-Received: X-StarScan-Version: 6.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 7883 invoked from network); 27 Feb 2013 10:40:50 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (46.33.159.39) by server-13.tower-216.messagelabs.com with RC4-SHA encrypted SMTP; 27 Feb 2013 10:40:50 -0000 X-IronPort-AV: E=Sophos;i="4.84,746,1355097600"; d="scan'208";a="1946225" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 27 Feb 2013 10:40:50 +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.297.1; Wed, 27 Feb 2013 10:40:49 +0000 Message-ID: <1361961648.26546.338.camel@zakaz.uk.xensource.com> From: Ian Campbell To: Katerina Mparmpopoulou Date: Wed, 27 Feb 2013 10:40:48 +0000 In-Reply-To: References: <1361955223.11431.32.camel@dagon.hellion.org.uk> Organization: Citrix Systems, Inc. X-Mailer: Evolution 3.4.4-1 MIME-Version: 1.0 Cc: "xen-users@lists.xen.org" Subject: Re: [Xen-users] Xen 4.2 - Security on Live Migration X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: 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, 2013-02-27 at 09:29 +0000, Katerina Mparmpopoulou wrote: > Hello Ian, > > Thanks for the quick reply, > > > Check out the xl manpage, in particular the -e option to xl > > migrate, which lets you specify any command you like to act as the > > transport. > > I have checked already the xl manpage and also the migrate subcommand. > > I thought that the -s sshcommand was the most relevant for me, but > still i don't know how i can use it efficiently. Sorry. I meant -s, I didn't have the manpage handy when I wrote -e. > > If i want to place my own ssl key and my own certificate when i'm > migrating a vm in another physical machine, how should I use the command?? You need to pass a command which will connect its stdin/stdout over the communication channel of your choice to the stdin/stdout of "xl migrate-receive" running on the target host. How you setup that communication channel and arrange for that process on the remote machine is up to you to arrange in that command. For example you could reasonably trivially build something out of netcat and ssh which did secure authentication and but insecure data transfer. If you want to do something with SSL certs then I expect you will wantto find an ssl capable netcat type thing, I think openssl has such mechanisms in it. Or you could write your own client/server pair, etc etc. Ian. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Wed Feb 27 12:16:26 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 27 Feb 2013 12:16: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 1UAfui-0002P3-1T; Wed, 27 Feb 2013 12:15:12 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UAfug-0002Oy-6T for xen-users@lists.xen.org; Wed, 27 Feb 2013 12:15:10 +0000 Received: from [85.158.139.211:15692] by server-9.bemta-5.messagelabs.com id 43/5E-08547-DC8FD215; Wed, 27 Feb 2013 12:15:09 +0000 X-Env-Sender: povder@gmail.com X-Msg-Ref: server-9.tower-206.messagelabs.com!1361967307!17875756!1 X-Originating-IP: [209.85.128.175] 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.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 313 invoked from network); 27 Feb 2013 12:15:08 -0000 Received: from mail-ve0-f175.google.com (HELO mail-ve0-f175.google.com) (209.85.128.175) by server-9.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 27 Feb 2013 12:15:08 -0000 Received: by mail-ve0-f175.google.com with SMTP id cy12so458583veb.6 for ; Wed, 27 Feb 2013 04:15:07 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:mime-version:from:date:message-id:subject:to :content-type; bh=2V5i967ffWOE1cIeYrCVfnGhcqHioErUf9qYq+TBlh4=; b=ev6P4PXjtiEPe/FcRWKD2k4opGHTHvyGVkYCewFkSbnZJdqrqEaqPM9Y5GFmroqQUN qrsK4Ox323IqTy8M0nNjLnLIqKiJ99qTQt/sYSetxpwr6kHOSetSIcMGBjqCf3Gn33uC f0tXS2UbFIBrfOhJDMvWL/eUZ8lP0bDihZUnvxyZ/z/ObEfUgSaQFU3EBPZHs1Gj641q KJUvJ/uzDON9b2+9qFFWz2IDNijVKS5Ai1fSCfXNWydF5hmcMoqFnyaZhvvO0mzHr8OJ AFXnP7yuDBFpvRs2Hvmh/CEfRQTH37/+EnjqscsoypRI2S3GMBu93qBxGegPju5OD9Pf L2Hg== X-Received: by 10.52.33.68 with SMTP id p4mr646223vdi.125.1361967307124; Wed, 27 Feb 2013 04:15:07 -0800 (PST) MIME-Version: 1.0 Received: by 10.58.203.106 with HTTP; Wed, 27 Feb 2013 04:14:47 -0800 (PST) From: povder Date: Wed, 27 Feb 2013 13:14:47 +0100 Message-ID: To: xen-users@lists.xen.org Subject: [Xen-users] VGA passthrough radeon 4850 as primary card X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: 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'm trying to enable VGA passthrough in linux domU without success. I want to pass through AMD Radeon HD 4850 - 03:00.0 VGA compatible controller: Advanced Micro Devices [AMD] nee ATI RV770 [Radeon HD 4850] as a _primary_ VGA for the VM. Nothing is showing up on the monitor that I have connected to graphics card's HDMI port. I have IOMMU enabled. I searched mailing lists and I don't know what to think about it. There is some information about ATI cards passthrough as primary VGA, some patches were posted but that was long time ago so my first question is: Is passthrough of ATI devices as primary VGA supposed to work now in Xen 4.2.1 without patches? My second question is: How can i debug the problem? I can't access domU through SSH after it's created. When I set gfx_passthru to 0 it's starting normally. How can I tell what went wrong? When I create domU I get this in logs: dm-command: hot insert pass-through pci dev register_real_device: Assigning real physical device 03:00.0 ... 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: 0x3:0x0.0x0 pt_register_regions: IO region registered (size=0x10000000 base_addr=0xd000000c) pt_register_regions: IO region registered (size=0x00010000 base_addr=0xfe7f0004) pt_register_regions: IO region registered (size=0x00000100 base_addr=0x0000d001) pt_register_regions: Expansion ROM registered (size=0x00020000 base_addr=0xfe7c0002) pci_intx: intx=1 register_real_device: Real physical device 03:00.0 registered successfuly! I'm using Xen 4.2.1 and xl toolstack. I have the following in VM config file: builder = "hvm" gfx_passthru = 1 pci = ['03:00.0','03:00.1'] vm config file: full domU log: http://pastebin.com/raw.php?i=rc9xWcDJ part of lspci -vvv: http://pastebin.com/raw.php?i=wZXcJU7j xl info: http://pastebin.com/raw.php?i=zDrdNm9u xl dmesg: http://pastebin.com/raw.php?i=SmJ7MrB1 Please help. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Wed Feb 27 12:16:26 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 27 Feb 2013 12:16: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 1UAfui-0002P3-1T; Wed, 27 Feb 2013 12:15:12 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UAfug-0002Oy-6T for xen-users@lists.xen.org; Wed, 27 Feb 2013 12:15:10 +0000 Received: from [85.158.139.211:15692] by server-9.bemta-5.messagelabs.com id 43/5E-08547-DC8FD215; Wed, 27 Feb 2013 12:15:09 +0000 X-Env-Sender: povder@gmail.com X-Msg-Ref: server-9.tower-206.messagelabs.com!1361967307!17875756!1 X-Originating-IP: [209.85.128.175] 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.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 313 invoked from network); 27 Feb 2013 12:15:08 -0000 Received: from mail-ve0-f175.google.com (HELO mail-ve0-f175.google.com) (209.85.128.175) by server-9.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 27 Feb 2013 12:15:08 -0000 Received: by mail-ve0-f175.google.com with SMTP id cy12so458583veb.6 for ; Wed, 27 Feb 2013 04:15:07 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:mime-version:from:date:message-id:subject:to :content-type; bh=2V5i967ffWOE1cIeYrCVfnGhcqHioErUf9qYq+TBlh4=; b=ev6P4PXjtiEPe/FcRWKD2k4opGHTHvyGVkYCewFkSbnZJdqrqEaqPM9Y5GFmroqQUN qrsK4Ox323IqTy8M0nNjLnLIqKiJ99qTQt/sYSetxpwr6kHOSetSIcMGBjqCf3Gn33uC f0tXS2UbFIBrfOhJDMvWL/eUZ8lP0bDihZUnvxyZ/z/ObEfUgSaQFU3EBPZHs1Gj641q KJUvJ/uzDON9b2+9qFFWz2IDNijVKS5Ai1fSCfXNWydF5hmcMoqFnyaZhvvO0mzHr8OJ AFXnP7yuDBFpvRs2Hvmh/CEfRQTH37/+EnjqscsoypRI2S3GMBu93qBxGegPju5OD9Pf L2Hg== X-Received: by 10.52.33.68 with SMTP id p4mr646223vdi.125.1361967307124; Wed, 27 Feb 2013 04:15:07 -0800 (PST) MIME-Version: 1.0 Received: by 10.58.203.106 with HTTP; Wed, 27 Feb 2013 04:14:47 -0800 (PST) From: povder Date: Wed, 27 Feb 2013 13:14:47 +0100 Message-ID: To: xen-users@lists.xen.org Subject: [Xen-users] VGA passthrough radeon 4850 as primary card X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: 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'm trying to enable VGA passthrough in linux domU without success. I want to pass through AMD Radeon HD 4850 - 03:00.0 VGA compatible controller: Advanced Micro Devices [AMD] nee ATI RV770 [Radeon HD 4850] as a _primary_ VGA for the VM. Nothing is showing up on the monitor that I have connected to graphics card's HDMI port. I have IOMMU enabled. I searched mailing lists and I don't know what to think about it. There is some information about ATI cards passthrough as primary VGA, some patches were posted but that was long time ago so my first question is: Is passthrough of ATI devices as primary VGA supposed to work now in Xen 4.2.1 without patches? My second question is: How can i debug the problem? I can't access domU through SSH after it's created. When I set gfx_passthru to 0 it's starting normally. How can I tell what went wrong? When I create domU I get this in logs: dm-command: hot insert pass-through pci dev register_real_device: Assigning real physical device 03:00.0 ... 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: 0x3:0x0.0x0 pt_register_regions: IO region registered (size=0x10000000 base_addr=0xd000000c) pt_register_regions: IO region registered (size=0x00010000 base_addr=0xfe7f0004) pt_register_regions: IO region registered (size=0x00000100 base_addr=0x0000d001) pt_register_regions: Expansion ROM registered (size=0x00020000 base_addr=0xfe7c0002) pci_intx: intx=1 register_real_device: Real physical device 03:00.0 registered successfuly! I'm using Xen 4.2.1 and xl toolstack. I have the following in VM config file: builder = "hvm" gfx_passthru = 1 pci = ['03:00.0','03:00.1'] vm config file: full domU log: http://pastebin.com/raw.php?i=rc9xWcDJ part of lspci -vvv: http://pastebin.com/raw.php?i=wZXcJU7j xl info: http://pastebin.com/raw.php?i=zDrdNm9u xl dmesg: http://pastebin.com/raw.php?i=SmJ7MrB1 Please help. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Wed Feb 27 12:59:23 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 27 Feb 2013 12:59: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 1UAgaV-0004ae-Ar; Wed, 27 Feb 2013 12:58:23 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UAgaT-0004aW-KY for xen-users@lists.xen.org; Wed, 27 Feb 2013 12:58:21 +0000 Received: from [85.158.139.83:59213] by server-1.bemta-5.messagelabs.com id 87/BB-14063-CE20E215; Wed, 27 Feb 2013 12:58:20 +0000 X-Env-Sender: kate_mparmpop@hotmail.com X-Msg-Ref: server-3.tower-182.messagelabs.com!1361969892!29253952!1 X-Originating-IP: [65.55.111.112] X-SpamReason: No, hits=0.6 required=7.0 tests=BODY_RANDOM_LONG, FORGED_HOTMAIL_RCVD,ML_RADAR_SPEW_LINKS_12,ML_RADAR_SPEW_LINKS_14, MSGID_FROM_MTA_HEADER,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 9708 invoked from network); 27 Feb 2013 12:58:12 -0000 Received: from blu0-omc2-s37.blu0.hotmail.com (HELO blu0-omc2-s37.blu0.hotmail.com) (65.55.111.112) by server-3.tower-182.messagelabs.com with SMTP; 27 Feb 2013 12:58:12 -0000 Received: from BLU0-SMTP102 ([65.55.111.73]) by blu0-omc2-s37.blu0.hotmail.com with Microsoft SMTPSVC(6.0.3790.4675); Wed, 27 Feb 2013 04:58:12 -0800 X-EIP: [2TFLbc1Mf6DEONA2x3LcgdNhGL/Y1BNN] X-Originating-Email: [kate_mparmpop@hotmail.com] Message-ID: Received: from [192.168.0.100] ([82.139.117.118]) by BLU0-SMTP102.phx.gbl over TLS secured channel with Microsoft SMTPSVC(6.0.3790.4675); Wed, 27 Feb 2013 04:58:09 -0800 Date: Wed, 27 Feb 2013 13:58:07 +0100 From: Katerina Mparmpopoulou User-Agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/20130221 Thunderbird/17.0.3 MIME-Version: 1.0 To: Ian Campbell References: <1361955223.11431.32.camel@dagon.hellion.org.uk> <1361961648.26546.338.camel@zakaz.uk.xensource.com> In-Reply-To: <1361961648.26546.338.camel@zakaz.uk.xensource.com> X-Enigmail-Version: 1.5 X-OriginalArrivalTime: 27 Feb 2013 12:58:09.0903 (UTC) FILETIME=[18118FF0:01CE14EA] Cc: "xen-users@lists.xen.org" Subject: Re: [Xen-users] Xen 4.2 - Security on Live Migration X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: 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 Hello Ian, Thx again for your information, i'm quite unfamiliar with that and i'm still can't get it. On 02/27/2013 11:40 AM, Ian Campbell wrote: > On Wed, 2013-02-27 at 09:29 +0000, Katerina Mparmpopoulou wrote: >> If i want to place my own ssl key and my own certificate when >> i'm migrating a vm in another physical machine, how should I use >> the command?? > > You need to pass a command which will connect its stdin/stdout over > the communication channel of your choice to the stdin/stdout of > "xl migrate-receive" running on the target host. How you setup > that communication channel and arrange for that process on the > remote machine is up to you to arrange in that command. > you mean that everything need to be done in: xl migrate -s where sshcommand is the stdin/stdout of another command? > For example you could reasonably trivially build something out of > netcat and ssh which did secure authentication and but insecure > data transfer. > > If you want to do something with SSL certs then I expect you will > wantto find an ssl capable netcat type thing, I think openssl has > such mechanisms in it. Or you could write your own client/server > pair, etc etc. I have already created my client/server pairs, but i don't know in which file to place/save them. Namely, xl migrate-receive command from which file retrieves these keys? Where are the default pair (If there is any)? In previous version I could create client/server pairs and I used to save them in etc/xen/xend-config.sxp, like this: (xend-relocation-server-ssl-key-file my_server.key) (xend-relocation-server-ssl-cert-file my_server.crt) Now do I need to run the migrate command every time along with these pair? For example like this? $xl migrate -s /etc/ssh/keys/my_server.key /etc/ssh/keys/my_server.crt -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQEcBAEBAgAGBQJRLgLfAAoJEIrShLVVnSKrPHcIAJ6lEO8kNZA1imy6Yg2XqgvK ZhSpG6WfWRH1Fp7fBWB1oaE1lYt1Mhoyzknkpi8JOlIq5M4eJqn+bRyG5/IZwNdT e1M0JsTdtDqNoqBx4Q2ijSadS3b4Vc764ZHKH5W2PRkgU+9C0cX12QmZw4/oVC+G GHqgOljtjQbnUb9tmkyTu/DhMUp+Ge/HKxx0d+k84QcaXvu22Nj8F4cQRa8Zgn0B gWqNVOxxajVFITDrCWZl1KXm3r8/dMCclmeo9RCxwC/qvrvlp0VzaWcZ0F0Tn7gW TL+r/fiWJ1gej7UswtN7Y3XTuZY02F5c5dRDf+U8oKqEd4E/OPpP8nxWarLNPjs= =mk2U -----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 Wed Feb 27 12:59:23 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 27 Feb 2013 12:59: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 1UAgaV-0004ae-Ar; Wed, 27 Feb 2013 12:58:23 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UAgaT-0004aW-KY for xen-users@lists.xen.org; Wed, 27 Feb 2013 12:58:21 +0000 Received: from [85.158.139.83:59213] by server-1.bemta-5.messagelabs.com id 87/BB-14063-CE20E215; Wed, 27 Feb 2013 12:58:20 +0000 X-Env-Sender: kate_mparmpop@hotmail.com X-Msg-Ref: server-3.tower-182.messagelabs.com!1361969892!29253952!1 X-Originating-IP: [65.55.111.112] X-SpamReason: No, hits=0.6 required=7.0 tests=BODY_RANDOM_LONG, FORGED_HOTMAIL_RCVD,ML_RADAR_SPEW_LINKS_12,ML_RADAR_SPEW_LINKS_14, MSGID_FROM_MTA_HEADER,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 9708 invoked from network); 27 Feb 2013 12:58:12 -0000 Received: from blu0-omc2-s37.blu0.hotmail.com (HELO blu0-omc2-s37.blu0.hotmail.com) (65.55.111.112) by server-3.tower-182.messagelabs.com with SMTP; 27 Feb 2013 12:58:12 -0000 Received: from BLU0-SMTP102 ([65.55.111.73]) by blu0-omc2-s37.blu0.hotmail.com with Microsoft SMTPSVC(6.0.3790.4675); Wed, 27 Feb 2013 04:58:12 -0800 X-EIP: [2TFLbc1Mf6DEONA2x3LcgdNhGL/Y1BNN] X-Originating-Email: [kate_mparmpop@hotmail.com] Message-ID: Received: from [192.168.0.100] ([82.139.117.118]) by BLU0-SMTP102.phx.gbl over TLS secured channel with Microsoft SMTPSVC(6.0.3790.4675); Wed, 27 Feb 2013 04:58:09 -0800 Date: Wed, 27 Feb 2013 13:58:07 +0100 From: Katerina Mparmpopoulou User-Agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/20130221 Thunderbird/17.0.3 MIME-Version: 1.0 To: Ian Campbell References: <1361955223.11431.32.camel@dagon.hellion.org.uk> <1361961648.26546.338.camel@zakaz.uk.xensource.com> In-Reply-To: <1361961648.26546.338.camel@zakaz.uk.xensource.com> X-Enigmail-Version: 1.5 X-OriginalArrivalTime: 27 Feb 2013 12:58:09.0903 (UTC) FILETIME=[18118FF0:01CE14EA] Cc: "xen-users@lists.xen.org" Subject: Re: [Xen-users] Xen 4.2 - Security on Live Migration X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: 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 Hello Ian, Thx again for your information, i'm quite unfamiliar with that and i'm still can't get it. On 02/27/2013 11:40 AM, Ian Campbell wrote: > On Wed, 2013-02-27 at 09:29 +0000, Katerina Mparmpopoulou wrote: >> If i want to place my own ssl key and my own certificate when >> i'm migrating a vm in another physical machine, how should I use >> the command?? > > You need to pass a command which will connect its stdin/stdout over > the communication channel of your choice to the stdin/stdout of > "xl migrate-receive" running on the target host. How you setup > that communication channel and arrange for that process on the > remote machine is up to you to arrange in that command. > you mean that everything need to be done in: xl migrate -s where sshcommand is the stdin/stdout of another command? > For example you could reasonably trivially build something out of > netcat and ssh which did secure authentication and but insecure > data transfer. > > If you want to do something with SSL certs then I expect you will > wantto find an ssl capable netcat type thing, I think openssl has > such mechanisms in it. Or you could write your own client/server > pair, etc etc. I have already created my client/server pairs, but i don't know in which file to place/save them. Namely, xl migrate-receive command from which file retrieves these keys? Where are the default pair (If there is any)? In previous version I could create client/server pairs and I used to save them in etc/xen/xend-config.sxp, like this: (xend-relocation-server-ssl-key-file my_server.key) (xend-relocation-server-ssl-cert-file my_server.crt) Now do I need to run the migrate command every time along with these pair? For example like this? $xl migrate -s /etc/ssh/keys/my_server.key /etc/ssh/keys/my_server.crt -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQEcBAEBAgAGBQJRLgLfAAoJEIrShLVVnSKrPHcIAJ6lEO8kNZA1imy6Yg2XqgvK ZhSpG6WfWRH1Fp7fBWB1oaE1lYt1Mhoyzknkpi8JOlIq5M4eJqn+bRyG5/IZwNdT e1M0JsTdtDqNoqBx4Q2ijSadS3b4Vc764ZHKH5W2PRkgU+9C0cX12QmZw4/oVC+G GHqgOljtjQbnUb9tmkyTu/DhMUp+Ge/HKxx0d+k84QcaXvu22Nj8F4cQRa8Zgn0B gWqNVOxxajVFITDrCWZl1KXm3r8/dMCclmeo9RCxwC/qvrvlp0VzaWcZ0F0Tn7gW TL+r/fiWJ1gej7UswtN7Y3XTuZY02F5c5dRDf+U8oKqEd4E/OPpP8nxWarLNPjs= =mk2U -----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 Wed Feb 27 13:13:34 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 27 Feb 2013 13:13: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 1UAgoG-00056U-2e; Wed, 27 Feb 2013 13:12:36 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UAgoF-00056N-63 for xen-users@lists.xen.org; Wed, 27 Feb 2013 13:12:35 +0000 Received: from [85.158.143.99:45136] by server-3.bemta-4.messagelabs.com id A8/DD-02186-2460E215; Wed, 27 Feb 2013 13:12:34 +0000 X-Env-Sender: Ian.Campbell@citrix.com X-Msg-Ref: server-9.tower-216.messagelabs.com!1361970752!29505855!1 X-Originating-IP: [46.33.159.39] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNDYuMzMuMTU5LjM5ID0+IDI0NTI3\n X-StarScan-Received: X-StarScan-Version: 6.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 6675 invoked from network); 27 Feb 2013 13:12:32 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (46.33.159.39) by server-9.tower-216.messagelabs.com with RC4-SHA encrypted SMTP; 27 Feb 2013 13:12:32 -0000 X-IronPort-AV: E=Sophos;i="4.84,747,1355097600"; d="scan'208";a="1954372" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 27 Feb 2013 13:12:32 +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.297.1; Wed, 27 Feb 2013 13:12:31 +0000 Message-ID: <1361970750.26546.375.camel@zakaz.uk.xensource.com> From: Ian Campbell To: Katerina Mparmpopoulou Date: Wed, 27 Feb 2013 13:12:30 +0000 In-Reply-To: References: <1361955223.11431.32.camel@dagon.hellion.org.uk> <1361961648.26546.338.camel@zakaz.uk.xensource.com> Organization: Citrix Systems, Inc. X-Mailer: Evolution 3.4.4-1 MIME-Version: 1.0 Cc: "xen-users@lists.xen.org" Subject: Re: [Xen-users] Xen 4.2 - Security on Live Migration X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: 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, 2013-02-27 at 12:58 +0000, Katerina Mparmpopoulou wrote: > Hello Ian, > > Thx again for your information, i'm quite unfamiliar with that and i'm > still can't get it. > > On 02/27/2013 11:40 AM, Ian Campbell wrote: > > On Wed, 2013-02-27 at 09:29 +0000, Katerina Mparmpopoulou wrote: > > >> If i want to place my own ssl key and my own certificate when > >> i'm migrating a vm in another physical machine, how should I use > >> the command?? > > > > You need to pass a command which will connect its stdin/stdout over > > the communication channel of your choice to the stdin/stdout of > > "xl migrate-receive" running on the target host. How you setup > > that communication channel and arrange for that process on the > > remote machine is up to you to arrange in that command. > > > > you mean that everything need to be done in: > > xl migrate -s > > where sshcommand is the stdin/stdout of another command? sshcommand *is* a to be run, which has a stdin/stdout. > > For example you could reasonably trivially build something out of > > netcat and ssh which did secure authentication and but insecure > > data transfer. > > > > If you want to do something with SSL certs then I expect you will > > wantto find an ssl capable netcat type thing, I think openssl has > > such mechanisms in it. Or you could write your own client/server > > pair, etc etc. > > I have already created my client/server pairs, but i don't know in > which file to place/save them. Namely, xl migrate-receive command from > which file retrieves these keys? Where are the default pair (If there > is any)? > > In previous version I could create client/server pairs and I used to > save them in etc/xen/xend-config.sxp, like this: > > (xend-relocation-server-ssl-key-file my_server.key) > (xend-relocation-server-ssl-cert-file my_server.crt) I'm afraid that xl doesn't have equivalent functionality. TBH I didn't even know xend did. However you can construct equivalent functionality with the sshcommand thing, by writing your own simple client and server, which is what I am talking about. > Now do I need to run the migrate command every time along with these > pair? For example like this? > > $xl migrate -s /etc/ssh/keys/my_server.key /etc/ssh/keys/my_server.crt > Your sshcommand would need to encode knowledge about my_server.key and .crt, either directly or through its own configuration file. Ian. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Wed Feb 27 13:13:34 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 27 Feb 2013 13:13: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 1UAgoG-00056U-2e; Wed, 27 Feb 2013 13:12:36 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UAgoF-00056N-63 for xen-users@lists.xen.org; Wed, 27 Feb 2013 13:12:35 +0000 Received: from [85.158.143.99:45136] by server-3.bemta-4.messagelabs.com id A8/DD-02186-2460E215; Wed, 27 Feb 2013 13:12:34 +0000 X-Env-Sender: Ian.Campbell@citrix.com X-Msg-Ref: server-9.tower-216.messagelabs.com!1361970752!29505855!1 X-Originating-IP: [46.33.159.39] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNDYuMzMuMTU5LjM5ID0+IDI0NTI3\n X-StarScan-Received: X-StarScan-Version: 6.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 6675 invoked from network); 27 Feb 2013 13:12:32 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (46.33.159.39) by server-9.tower-216.messagelabs.com with RC4-SHA encrypted SMTP; 27 Feb 2013 13:12:32 -0000 X-IronPort-AV: E=Sophos;i="4.84,747,1355097600"; d="scan'208";a="1954372" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 27 Feb 2013 13:12:32 +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.297.1; Wed, 27 Feb 2013 13:12:31 +0000 Message-ID: <1361970750.26546.375.camel@zakaz.uk.xensource.com> From: Ian Campbell To: Katerina Mparmpopoulou Date: Wed, 27 Feb 2013 13:12:30 +0000 In-Reply-To: References: <1361955223.11431.32.camel@dagon.hellion.org.uk> <1361961648.26546.338.camel@zakaz.uk.xensource.com> Organization: Citrix Systems, Inc. X-Mailer: Evolution 3.4.4-1 MIME-Version: 1.0 Cc: "xen-users@lists.xen.org" Subject: Re: [Xen-users] Xen 4.2 - Security on Live Migration X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: 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, 2013-02-27 at 12:58 +0000, Katerina Mparmpopoulou wrote: > Hello Ian, > > Thx again for your information, i'm quite unfamiliar with that and i'm > still can't get it. > > On 02/27/2013 11:40 AM, Ian Campbell wrote: > > On Wed, 2013-02-27 at 09:29 +0000, Katerina Mparmpopoulou wrote: > > >> If i want to place my own ssl key and my own certificate when > >> i'm migrating a vm in another physical machine, how should I use > >> the command?? > > > > You need to pass a command which will connect its stdin/stdout over > > the communication channel of your choice to the stdin/stdout of > > "xl migrate-receive" running on the target host. How you setup > > that communication channel and arrange for that process on the > > remote machine is up to you to arrange in that command. > > > > you mean that everything need to be done in: > > xl migrate -s > > where sshcommand is the stdin/stdout of another command? sshcommand *is* a to be run, which has a stdin/stdout. > > For example you could reasonably trivially build something out of > > netcat and ssh which did secure authentication and but insecure > > data transfer. > > > > If you want to do something with SSL certs then I expect you will > > wantto find an ssl capable netcat type thing, I think openssl has > > such mechanisms in it. Or you could write your own client/server > > pair, etc etc. > > I have already created my client/server pairs, but i don't know in > which file to place/save them. Namely, xl migrate-receive command from > which file retrieves these keys? Where are the default pair (If there > is any)? > > In previous version I could create client/server pairs and I used to > save them in etc/xen/xend-config.sxp, like this: > > (xend-relocation-server-ssl-key-file my_server.key) > (xend-relocation-server-ssl-cert-file my_server.crt) I'm afraid that xl doesn't have equivalent functionality. TBH I didn't even know xend did. However you can construct equivalent functionality with the sshcommand thing, by writing your own simple client and server, which is what I am talking about. > Now do I need to run the migrate command every time along with these > pair? For example like this? > > $xl migrate -s /etc/ssh/keys/my_server.key /etc/ssh/keys/my_server.crt > Your sshcommand would need to encode knowledge about my_server.key and .crt, either directly or through its own configuration file. Ian. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Wed Feb 27 19:42:25 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 27 Feb 2013 19:42: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 1UAmsF-0003k9-6E; Wed, 27 Feb 2013 19:41:07 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UAmsD-0003j4-Vo for xen-users@lists.xen.org; Wed, 27 Feb 2013 19:41:06 +0000 Received: from [85.158.139.83:50832] by server-16.bemta-5.messagelabs.com id 57/CE-02543-1516E215; Wed, 27 Feb 2013 19:41:05 +0000 X-Env-Sender: david.olsen@isprime.com X-Msg-Ref: server-16.tower-182.messagelabs.com!1361994063!21958896!1 X-Originating-IP: [64.188.48.178] X-SpamReason: No, hits=0.5 required=7.0 tests=BODY_RANDOM_LONG X-StarScan-Received: X-StarScan-Version: 6.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 30301 invoked from network); 27 Feb 2013 19:41:03 -0000 Received: from pony.isprime.com (HELO pony.isprime.com) (64.188.48.178) by server-16.tower-182.messagelabs.com with SMTP; 27 Feb 2013 19:41:03 -0000 Received: from localhost (unknown [64.111.209.247]) by pony.isprime.com (Postfix) with ESMTPSA id C3E191D205B3 for ; Wed, 27 Feb 2013 14:41:02 -0500 (EST) Date: Wed, 27 Feb 2013 14:37:52 -0500 From: David Olsen To: xen-users@lists.xen.org Message-ID: <20130227193752.GA641@isprime.com> MIME-Version: 1.0 Content-Disposition: inline User-Agent: Mutt/1.5.21 (2010-09-15) Subject: [Xen-users] kernel BUG at drivers/net/xen-netfront.c:305 X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: 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, I've been having an issue with a particular DomU on a server. The Dom0 runs other instances just fine, this particular instance will run just fine for a few hours to a few days, then it will just die out with the following error: --- kernel BUG at drivers/net/xen-netfront.c:305! invalid opcode: 0000 [#1] SMP Modules linked in: CPU 0 Pid: 0, comm: swapper/0 Not tainted 3.6.6-gentoo #1 RIP: e030:[] [] xennet_alloc_rx_buffers+0x1d7/0x2fe RSP: e02b:ffff88006da03d80 EFLAGS: 00010286 RAX: 00000000000001ff RBX: ffff880066f88000 RCX: 0000000000000001 RDX: 0000000000000057 RSI: 0000000000000000 RDI: 0000000000004fc0 RBP: 000000000cc1323f R08: 0000000000000000 R09: 00000000000038df R10: 00000000000004f1 R11: 0000000000003431 R12: 000000000cc13257 R13: ffff8800669c0600 R14: 00000000000004fc R15: 0000000000000057 FS: 00007fcb35820740(0000) GS:ffff88006da00000(0000) knlGS:0000000000000000 CS: e033 DS: 0000 ES: 0000 CR0: 000000008005003b CR2: 00007fcb3052e260 CR3: 000000005aa3a000 CR4: 0000000000042660 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400 Process swapper/0 (pid: 0, threadinfo ffffffff81586000, task ffffffff81599410) Stack: 0000000000000056 0000001864b24900 ffff880066f89430 ffff880066f89c80 ffff880066f88000 0000000000000001 ffff880066f88758 ffff88006da18d30 ffff880066f88000 0000000000000000 ffff88006da03e28 ffffffff812c2a61 Call Trace: [] ? xennet_poll+0xa0a/0xa98 [] ? hrtimer_interrupt+0x112/0x1c9 [] ? net_rx_action+0x6e/0x139 [] ? __do_softirq+0x9c/0x145 [] ? __xen_evtchn_do_upcall+0x1b0/0x1ed [] ? call_softirq+0x1c/0x30 [] ? do_softirq+0x3c/0x7a [] ? irq_exit+0x42/0x9a [] ? xen_evtchn_do_upcall+0x27/0x32 [] ? xen_do_hypervisor_callback+0x1e/0x30 [] ? hypercall_page+0x3aa/0x1000 [] ? hypercall_page+0x3aa/0x1000 [] ? xen_safe_halt+0xc/0x13 [] ? default_idle+0x23/0x3f [] ? cpu_idle+0x60/0xa2 [] ? start_kernel+0x32e/0x339 [] ? repair_env_string+0x54/0x54 [] ? xen_start_kernel+0x465/0x46b Code: 45 08 49 c7 45 08 00 00 00 00 48 89 42 08 48 89 10 41 0f b6 d7 49 89 5d 20 48 8d 82 a8 01 00 00 48 83 bc c3 40 07 00 00 00 74 02 <0f> 0b 48 8b 7c 24 18 4c 89 ac c3 40 07 00 00 48 89 14 24 e8 e2 RIP [] xennet_alloc_rx_buffers+0x1d7/0x2fe RSP ---[ end trace 77f364e88037c131 ]--- Kernel panic - not syncing: Fatal exception in interrupt --- Here's the config for that instance: kernel = "/xen/kernels/kernel-linux-3.6.11-domU" memory = 6144 maxmem = 16384 maxvcpus = 24 vcpus = 2 name = "REDACTED" disk = ['phy:/dev/vg/REDACTED-root,sda1,w','phy:/dev/swap/REDACTED-swap,sdb1,w'] root = "/dev/xvda1 ro" extra = "console=hvc0 xencons=tty" vif = [ 'bridge=eth0,mac=00:16:3e:52:ca:47', 'bridge=eth1,mac=00:16:3e:d4:b7:d8' ] It's just a basic LAMP setup, with the MySQL being external to the instance. Running xen version 4.2.0 on a Gentoo Linux box. Let me know if the error looks familiar to anyone, or if there is any more information I can provide. -d _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Wed Feb 27 19:42:25 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 27 Feb 2013 19:42: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 1UAmsF-0003k9-6E; Wed, 27 Feb 2013 19:41:07 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UAmsD-0003j4-Vo for xen-users@lists.xen.org; Wed, 27 Feb 2013 19:41:06 +0000 Received: from [85.158.139.83:50832] by server-16.bemta-5.messagelabs.com id 57/CE-02543-1516E215; Wed, 27 Feb 2013 19:41:05 +0000 X-Env-Sender: david.olsen@isprime.com X-Msg-Ref: server-16.tower-182.messagelabs.com!1361994063!21958896!1 X-Originating-IP: [64.188.48.178] X-SpamReason: No, hits=0.5 required=7.0 tests=BODY_RANDOM_LONG X-StarScan-Received: X-StarScan-Version: 6.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 30301 invoked from network); 27 Feb 2013 19:41:03 -0000 Received: from pony.isprime.com (HELO pony.isprime.com) (64.188.48.178) by server-16.tower-182.messagelabs.com with SMTP; 27 Feb 2013 19:41:03 -0000 Received: from localhost (unknown [64.111.209.247]) by pony.isprime.com (Postfix) with ESMTPSA id C3E191D205B3 for ; Wed, 27 Feb 2013 14:41:02 -0500 (EST) Date: Wed, 27 Feb 2013 14:37:52 -0500 From: David Olsen To: xen-users@lists.xen.org Message-ID: <20130227193752.GA641@isprime.com> MIME-Version: 1.0 Content-Disposition: inline User-Agent: Mutt/1.5.21 (2010-09-15) Subject: [Xen-users] kernel BUG at drivers/net/xen-netfront.c:305 X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: 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, I've been having an issue with a particular DomU on a server. The Dom0 runs other instances just fine, this particular instance will run just fine for a few hours to a few days, then it will just die out with the following error: --- kernel BUG at drivers/net/xen-netfront.c:305! invalid opcode: 0000 [#1] SMP Modules linked in: CPU 0 Pid: 0, comm: swapper/0 Not tainted 3.6.6-gentoo #1 RIP: e030:[] [] xennet_alloc_rx_buffers+0x1d7/0x2fe RSP: e02b:ffff88006da03d80 EFLAGS: 00010286 RAX: 00000000000001ff RBX: ffff880066f88000 RCX: 0000000000000001 RDX: 0000000000000057 RSI: 0000000000000000 RDI: 0000000000004fc0 RBP: 000000000cc1323f R08: 0000000000000000 R09: 00000000000038df R10: 00000000000004f1 R11: 0000000000003431 R12: 000000000cc13257 R13: ffff8800669c0600 R14: 00000000000004fc R15: 0000000000000057 FS: 00007fcb35820740(0000) GS:ffff88006da00000(0000) knlGS:0000000000000000 CS: e033 DS: 0000 ES: 0000 CR0: 000000008005003b CR2: 00007fcb3052e260 CR3: 000000005aa3a000 CR4: 0000000000042660 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400 Process swapper/0 (pid: 0, threadinfo ffffffff81586000, task ffffffff81599410) Stack: 0000000000000056 0000001864b24900 ffff880066f89430 ffff880066f89c80 ffff880066f88000 0000000000000001 ffff880066f88758 ffff88006da18d30 ffff880066f88000 0000000000000000 ffff88006da03e28 ffffffff812c2a61 Call Trace: [] ? xennet_poll+0xa0a/0xa98 [] ? hrtimer_interrupt+0x112/0x1c9 [] ? net_rx_action+0x6e/0x139 [] ? __do_softirq+0x9c/0x145 [] ? __xen_evtchn_do_upcall+0x1b0/0x1ed [] ? call_softirq+0x1c/0x30 [] ? do_softirq+0x3c/0x7a [] ? irq_exit+0x42/0x9a [] ? xen_evtchn_do_upcall+0x27/0x32 [] ? xen_do_hypervisor_callback+0x1e/0x30 [] ? hypercall_page+0x3aa/0x1000 [] ? hypercall_page+0x3aa/0x1000 [] ? xen_safe_halt+0xc/0x13 [] ? default_idle+0x23/0x3f [] ? cpu_idle+0x60/0xa2 [] ? start_kernel+0x32e/0x339 [] ? repair_env_string+0x54/0x54 [] ? xen_start_kernel+0x465/0x46b Code: 45 08 49 c7 45 08 00 00 00 00 48 89 42 08 48 89 10 41 0f b6 d7 49 89 5d 20 48 8d 82 a8 01 00 00 48 83 bc c3 40 07 00 00 00 74 02 <0f> 0b 48 8b 7c 24 18 4c 89 ac c3 40 07 00 00 48 89 14 24 e8 e2 RIP [] xennet_alloc_rx_buffers+0x1d7/0x2fe RSP ---[ end trace 77f364e88037c131 ]--- Kernel panic - not syncing: Fatal exception in interrupt --- Here's the config for that instance: kernel = "/xen/kernels/kernel-linux-3.6.11-domU" memory = 6144 maxmem = 16384 maxvcpus = 24 vcpus = 2 name = "REDACTED" disk = ['phy:/dev/vg/REDACTED-root,sda1,w','phy:/dev/swap/REDACTED-swap,sdb1,w'] root = "/dev/xvda1 ro" extra = "console=hvc0 xencons=tty" vif = [ 'bridge=eth0,mac=00:16:3e:52:ca:47', 'bridge=eth1,mac=00:16:3e:d4:b7:d8' ] It's just a basic LAMP setup, with the MySQL being external to the instance. Running xen version 4.2.0 on a Gentoo Linux box. Let me know if the error looks familiar to anyone, or if there is any more information I can provide. -d _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Wed Feb 27 19:42:30 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 27 Feb 2013 19:42: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 1UAmsW-0003mu-SL; Wed, 27 Feb 2013 19:41:24 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UAmsV-0003mo-AE for xen-users@lists.xen.org; Wed, 27 Feb 2013 19:41:23 +0000 Received: from [85.158.139.83:55807] by server-13.bemta-5.messagelabs.com id 0F/D2-16871-2616E215; Wed, 27 Feb 2013 19:41:22 +0000 X-Env-Sender: s.munaut@whatever-company.com X-Msg-Ref: server-5.tower-182.messagelabs.com!1361994081!27584414!1 X-Originating-IP: [209.85.214.42] X-SpamReason: No, hits=0.3 required=7.0 tests=RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 25729 invoked from network); 27 Feb 2013 19:41:22 -0000 Received: from mail-bk0-f42.google.com (HELO mail-bk0-f42.google.com) (209.85.214.42) by server-5.tower-182.messagelabs.com with RC4-SHA encrypted SMTP; 27 Feb 2013 19:41:22 -0000 Received: by mail-bk0-f42.google.com with SMTP id jk7so459615bkc.29 for ; Wed, 27 Feb 2013 11:41:21 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type:x-gm-message-state; bh=5F7MrsOkM5YFDrmBT0cZxd0ZrmXE2y/5E/FdZUu4seg=; b=Tg5X8tYbXzVHPed3L/hFU5OImF0DxBMs5sOArStosE7m1Q30nHyIVywdN/udZ5fRwt ZSLlRhG7PMcYCZrV0eC4J/0vBox3u1dGvYwc2REpJJEieXgIOOYahFFifLvnnbxllThh uJdPfxiZfBI/SmcrC0pqzrboKiNUPgZspRp8mlaz00o23/+GpRTtFg3PhmOxi+5khiBs AZdrVZBmF0aN0aKr5VkuDduLlWYW5UF+Buq98d4ShhT2jGJpoLvd23NABradh0l6pRSJ upau7jTLbkfwYqZ3jxdQwsR5KT+9HO6wx6gVRouXxgXpJdk3UmBm7M73JCpJ/if8aMVy Fbmw== MIME-Version: 1.0 X-Received: by 10.204.5.140 with SMTP id 12mr1368512bkv.18.1361994081667; Wed, 27 Feb 2013 11:41:21 -0800 (PST) Received: by 10.205.137.141 with HTTP; Wed, 27 Feb 2013 11:41:21 -0800 (PST) In-Reply-To: References: <1361955223.11431.32.camel@dagon.hellion.org.uk> <1361961648.26546.338.camel@zakaz.uk.xensource.com> Date: Wed, 27 Feb 2013 20:41:21 +0100 Message-ID: From: Sylvain Munaut To: Katerina Mparmpopoulou X-Gm-Message-State: ALoCoQm5iN6PCt3ljj7E/Ivq+VB++8sPa7Q6eVdZtITZD/NCT2rCdpQ5CJb0Re2GsMqyNvalZJPh Cc: "xen-users@lists.xen.org" , Ian Campbell Subject: Re: [Xen-users] Xen 4.2 - Security on Live Migration X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: 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, > In previous version I could create client/server pairs and I used to > save them in etc/xen/xend-config.sxp, like this: > > (xend-relocation-server-ssl-key-file my_server.key) > (xend-relocation-server-ssl-cert-file my_server.crt) Did you actually check the code to see what it does ? AFAICT, it just setups a SSL server using those, but it does no validation whatsoever that the client that connects is using a valid cert, nor does the client check anything about the server certificate ... Cheers, Sylvain _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Wed Feb 27 19:42:30 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 27 Feb 2013 19:42: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 1UAmsW-0003mu-SL; Wed, 27 Feb 2013 19:41:24 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UAmsV-0003mo-AE for xen-users@lists.xen.org; Wed, 27 Feb 2013 19:41:23 +0000 Received: from [85.158.139.83:55807] by server-13.bemta-5.messagelabs.com id 0F/D2-16871-2616E215; Wed, 27 Feb 2013 19:41:22 +0000 X-Env-Sender: s.munaut@whatever-company.com X-Msg-Ref: server-5.tower-182.messagelabs.com!1361994081!27584414!1 X-Originating-IP: [209.85.214.42] X-SpamReason: No, hits=0.3 required=7.0 tests=RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 25729 invoked from network); 27 Feb 2013 19:41:22 -0000 Received: from mail-bk0-f42.google.com (HELO mail-bk0-f42.google.com) (209.85.214.42) by server-5.tower-182.messagelabs.com with RC4-SHA encrypted SMTP; 27 Feb 2013 19:41:22 -0000 Received: by mail-bk0-f42.google.com with SMTP id jk7so459615bkc.29 for ; Wed, 27 Feb 2013 11:41:21 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type:x-gm-message-state; bh=5F7MrsOkM5YFDrmBT0cZxd0ZrmXE2y/5E/FdZUu4seg=; b=Tg5X8tYbXzVHPed3L/hFU5OImF0DxBMs5sOArStosE7m1Q30nHyIVywdN/udZ5fRwt ZSLlRhG7PMcYCZrV0eC4J/0vBox3u1dGvYwc2REpJJEieXgIOOYahFFifLvnnbxllThh uJdPfxiZfBI/SmcrC0pqzrboKiNUPgZspRp8mlaz00o23/+GpRTtFg3PhmOxi+5khiBs AZdrVZBmF0aN0aKr5VkuDduLlWYW5UF+Buq98d4ShhT2jGJpoLvd23NABradh0l6pRSJ upau7jTLbkfwYqZ3jxdQwsR5KT+9HO6wx6gVRouXxgXpJdk3UmBm7M73JCpJ/if8aMVy Fbmw== MIME-Version: 1.0 X-Received: by 10.204.5.140 with SMTP id 12mr1368512bkv.18.1361994081667; Wed, 27 Feb 2013 11:41:21 -0800 (PST) Received: by 10.205.137.141 with HTTP; Wed, 27 Feb 2013 11:41:21 -0800 (PST) In-Reply-To: References: <1361955223.11431.32.camel@dagon.hellion.org.uk> <1361961648.26546.338.camel@zakaz.uk.xensource.com> Date: Wed, 27 Feb 2013 20:41:21 +0100 Message-ID: From: Sylvain Munaut To: Katerina Mparmpopoulou X-Gm-Message-State: ALoCoQm5iN6PCt3ljj7E/Ivq+VB++8sPa7Q6eVdZtITZD/NCT2rCdpQ5CJb0Re2GsMqyNvalZJPh Cc: "xen-users@lists.xen.org" , Ian Campbell Subject: Re: [Xen-users] Xen 4.2 - Security on Live Migration X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: 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, > In previous version I could create client/server pairs and I used to > save them in etc/xen/xend-config.sxp, like this: > > (xend-relocation-server-ssl-key-file my_server.key) > (xend-relocation-server-ssl-cert-file my_server.crt) Did you actually check the code to see what it does ? AFAICT, it just setups a SSL server using those, but it does no validation whatsoever that the client that connects is using a valid cert, nor does the client check anything about the server certificate ... Cheers, Sylvain _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Wed Feb 27 20:22:52 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 27 Feb 2013 20:22: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 1UAnVj-0005TN-8D; Wed, 27 Feb 2013 20:21:55 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UAnVh-0005TI-HZ for xen-users@lists.xen.org; Wed, 27 Feb 2013 20:21:53 +0000 Received: from [193.109.254.147:42621] by server-12.bemta-14.messagelabs.com id D5/33-32582-0EA6E215; Wed, 27 Feb 2013 20:21:52 +0000 X-Env-Sender: kate_mparmpop@hotmail.com X-Msg-Ref: server-4.tower-27.messagelabs.com!1361996510!9279792!1 X-Originating-IP: [65.55.111.91] X-SpamReason: No, hits=0.6 required=7.0 tests=BODY_RANDOM_LONG, FORGED_HOTMAIL_RCVD,ML_RADAR_SPEW_LINKS_12,ML_RADAR_SPEW_LINKS_14, MSGID_FROM_MTA_HEADER,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 27779 invoked from network); 27 Feb 2013 20:21:51 -0000 Received: from blu0-omc2-s16.blu0.hotmail.com (HELO blu0-omc2-s16.blu0.hotmail.com) (65.55.111.91) by server-4.tower-27.messagelabs.com with SMTP; 27 Feb 2013 20:21:51 -0000 Received: from BLU0-SMTP227 ([65.55.111.73]) by blu0-omc2-s16.blu0.hotmail.com with Microsoft SMTPSVC(6.0.3790.4675); Wed, 27 Feb 2013 12:21:48 -0800 X-EIP: [7XxmeCb1uXshoY/LcmYnE8MSMnMkHU5r] X-Originating-Email: [kate_mparmpop@hotmail.com] Message-ID: Received: from [192.168.0.100] ([82.139.117.118]) by BLU0-SMTP227.phx.gbl over TLS secured channel with Microsoft SMTPSVC(6.0.3790.4675); Wed, 27 Feb 2013 12:21:46 -0800 Date: Wed, 27 Feb 2013 21:21:44 +0100 From: Katerina Mparmpopoulou User-Agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/20130221 Thunderbird/17.0.3 MIME-Version: 1.0 To: Sylvain Munaut References: <1361955223.11431.32.camel@dagon.hellion.org.uk> <1361961648.26546.338.camel@zakaz.uk.xensource.com> In-Reply-To: X-Enigmail-Version: 1.5 X-OriginalArrivalTime: 27 Feb 2013 20:21:46.0819 (UTC) FILETIME=[10FCA130:01CE1528] Cc: "xen-users@lists.xen.org" , Ian Campbell Subject: Re: [Xen-users] Xen 4.2 - Security on Live Migration X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: 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 02/27/2013 08:41 PM, Sylvain Munaut wrote: > Hi, > >> In previous version I could create client/server pairs and I used >> to save them in etc/xen/xend-config.sxp, like this: >> >> (xend-relocation-server-ssl-key-file my_server.key) >> (xend-relocation-server-ssl-cert-file my_server.crt) > > Did you actually check the code to see what it does ? > > AFAICT, it just setups a SSL server using those, but it does no > validation whatsoever that the client that connects is using a > valid cert, nor does the client check anything about the server > certificate ... > > Cheers, > > Sylvain Hi Sylvain, thx for your reply! actually i didn't check any code because it is mentioned in the man file of xend-config.sxp: "Note that relocation is currently unsecured and is very dangerous if left enabled. No authentication is performed, and very little sanity checking takes place. Enable at your own risk." http://xenbits.xen.org/docs/unstable/man/xend-config.sxp.5.html Now that I have switched to Xen-4.2.1 i'm searching from where i could modify security options considering live migration, like allowing only specific hosts or using ssl. Katerina -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQEcBAEBAgAGBQJRLmrYAAoJEIrShLVVnSKrjbEH/RytkqLkrdpbZB1L5sakq4vs eyxArVvoYgws+VxKVygcBa7hkoceZvmMXtpJmdKI3qWag/ivv1hyFy1aOPuuRSmv XplMxlpvhHKnw0fsY7kCQ1kD+ooeE8s/ttYcSwjJRCex0qQ6LDBZYuldQxWWEop7 uM6063dWg6xnA0LIbo1pd9yNaub7A9I+F9fsiQHLFNWH42L7VKQeWUncsZ0tn24p Z32kueGKFbYWIVdRi0ngucLgqyW+d31+nWpOttMyX/k1PhWNhfKhbQN6NNU2xaiS CjpBILXxm68y8zSAMZbW1m/7dWQ0veq0sBNIKbwh/0nzG9DWo+zWIuCLkmh0584= =hFVR -----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 Wed Feb 27 20:22:52 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 27 Feb 2013 20:22: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 1UAnVj-0005TN-8D; Wed, 27 Feb 2013 20:21:55 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UAnVh-0005TI-HZ for xen-users@lists.xen.org; Wed, 27 Feb 2013 20:21:53 +0000 Received: from [193.109.254.147:42621] by server-12.bemta-14.messagelabs.com id D5/33-32582-0EA6E215; Wed, 27 Feb 2013 20:21:52 +0000 X-Env-Sender: kate_mparmpop@hotmail.com X-Msg-Ref: server-4.tower-27.messagelabs.com!1361996510!9279792!1 X-Originating-IP: [65.55.111.91] X-SpamReason: No, hits=0.6 required=7.0 tests=BODY_RANDOM_LONG, FORGED_HOTMAIL_RCVD,ML_RADAR_SPEW_LINKS_12,ML_RADAR_SPEW_LINKS_14, MSGID_FROM_MTA_HEADER,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 27779 invoked from network); 27 Feb 2013 20:21:51 -0000 Received: from blu0-omc2-s16.blu0.hotmail.com (HELO blu0-omc2-s16.blu0.hotmail.com) (65.55.111.91) by server-4.tower-27.messagelabs.com with SMTP; 27 Feb 2013 20:21:51 -0000 Received: from BLU0-SMTP227 ([65.55.111.73]) by blu0-omc2-s16.blu0.hotmail.com with Microsoft SMTPSVC(6.0.3790.4675); Wed, 27 Feb 2013 12:21:48 -0800 X-EIP: [7XxmeCb1uXshoY/LcmYnE8MSMnMkHU5r] X-Originating-Email: [kate_mparmpop@hotmail.com] Message-ID: Received: from [192.168.0.100] ([82.139.117.118]) by BLU0-SMTP227.phx.gbl over TLS secured channel with Microsoft SMTPSVC(6.0.3790.4675); Wed, 27 Feb 2013 12:21:46 -0800 Date: Wed, 27 Feb 2013 21:21:44 +0100 From: Katerina Mparmpopoulou User-Agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/20130221 Thunderbird/17.0.3 MIME-Version: 1.0 To: Sylvain Munaut References: <1361955223.11431.32.camel@dagon.hellion.org.uk> <1361961648.26546.338.camel@zakaz.uk.xensource.com> In-Reply-To: X-Enigmail-Version: 1.5 X-OriginalArrivalTime: 27 Feb 2013 20:21:46.0819 (UTC) FILETIME=[10FCA130:01CE1528] Cc: "xen-users@lists.xen.org" , Ian Campbell Subject: Re: [Xen-users] Xen 4.2 - Security on Live Migration X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: 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 02/27/2013 08:41 PM, Sylvain Munaut wrote: > Hi, > >> In previous version I could create client/server pairs and I used >> to save them in etc/xen/xend-config.sxp, like this: >> >> (xend-relocation-server-ssl-key-file my_server.key) >> (xend-relocation-server-ssl-cert-file my_server.crt) > > Did you actually check the code to see what it does ? > > AFAICT, it just setups a SSL server using those, but it does no > validation whatsoever that the client that connects is using a > valid cert, nor does the client check anything about the server > certificate ... > > Cheers, > > Sylvain Hi Sylvain, thx for your reply! actually i didn't check any code because it is mentioned in the man file of xend-config.sxp: "Note that relocation is currently unsecured and is very dangerous if left enabled. No authentication is performed, and very little sanity checking takes place. Enable at your own risk." http://xenbits.xen.org/docs/unstable/man/xend-config.sxp.5.html Now that I have switched to Xen-4.2.1 i'm searching from where i could modify security options considering live migration, like allowing only specific hosts or using ssl. Katerina -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQEcBAEBAgAGBQJRLmrYAAoJEIrShLVVnSKrjbEH/RytkqLkrdpbZB1L5sakq4vs eyxArVvoYgws+VxKVygcBa7hkoceZvmMXtpJmdKI3qWag/ivv1hyFy1aOPuuRSmv XplMxlpvhHKnw0fsY7kCQ1kD+ooeE8s/ttYcSwjJRCex0qQ6LDBZYuldQxWWEop7 uM6063dWg6xnA0LIbo1pd9yNaub7A9I+F9fsiQHLFNWH42L7VKQeWUncsZ0tn24p Z32kueGKFbYWIVdRi0ngucLgqyW+d31+nWpOttMyX/k1PhWNhfKhbQN6NNU2xaiS CjpBILXxm68y8zSAMZbW1m/7dWQ0veq0sBNIKbwh/0nzG9DWo+zWIuCLkmh0584= =hFVR -----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 Wed Feb 27 21:33:18 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 27 Feb 2013 21:33: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 1UAobj-0006kT-L7; Wed, 27 Feb 2013 21:32:11 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UAobh-0006kO-Ic for xen-users@lists.xen.org; Wed, 27 Feb 2013 21:32:09 +0000 Received: from [193.109.254.147:13687] by server-16.bemta-14.messagelabs.com id 35/8C-25906-85B7E215; Wed, 27 Feb 2013 21:32:08 +0000 X-Env-Sender: matthias.kannenberg@googlemail.com X-Msg-Ref: server-4.tower-27.messagelabs.com!1362000727!9285030!1 X-Originating-IP: [74.125.82.179] X-SpamReason: No, hits=0.3 required=7.0 tests=RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 13900 invoked from network); 27 Feb 2013 21:32:07 -0000 Received: from mail-we0-f179.google.com (HELO mail-we0-f179.google.com) (74.125.82.179) by server-4.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 27 Feb 2013 21:32:07 -0000 Received: by mail-we0-f179.google.com with SMTP id p43so923507wea.24 for ; Wed, 27 Feb 2013 13:32:07 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=20120113; h=x-received:mime-version:in-reply-to:references:from:date:message-id :subject:to:cc:content-type; bh=FfJTz2LDCkOPl6B0U7ua584xc/+7qtbLkHD4MQddHzM=; b=KbblQgyO9i6MusiKLkoC+fEKpZ/Q4qUD8Rdh24g7O3OzgSM78Fud2ddhHva1UOd9/l 5u9dUWQLSlfHcgCkcszeXEl7QrDrYWNqv6NEPk8dNHBMiSDKHxrCPgYvosumFLzK41Oo siA8bfMfudT0P3NPNmDPB1voNMmD9fJSL9AdNiFll//mKRc/iOzCHs7ZbsO0/VS4eH64 zeNjhHBmK5qmm7kAr/3XMVFvzcJveCobrx0qxQ5A62avpVu6SDH96MlRAQxzARIC9dXL zLO2gEbX7C2qns+6R5Rj8k4YiiqWOAnJkXY4bwHi36miNLIBTH1NmN6z3SaTl56hkZAA R9CQ== X-Received: by 10.194.57.206 with SMTP id k14mr6824506wjq.26.1362000727275; Wed, 27 Feb 2013 13:32:07 -0800 (PST) MIME-Version: 1.0 Received: by 10.194.118.167 with HTTP; Wed, 27 Feb 2013 13:31:47 -0800 (PST) In-Reply-To: References: From: Matthias Date: Wed, 27 Feb 2013 22:31:47 +0100 Message-ID: To: povder Cc: xen-users@lists.xen.org Subject: Re: [Xen-users] VGA passthrough radeon 4850 as primary card X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: 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 there any special reason you use primary passthrough? because using the ati vga as secondary is A LOT easier and simpler (and as stable and performant). To be honest, i never got primary passthrough to work with any of my radeon cards, but secondary works quite well for 2,5 years now. So my advice: use secondary, boot and install domU normally, then install the catalyst driver and reboot. Within the start-process, it will automatically switch to the right vga near the end of the boot and as an additional benefit you can use the vnc view as additional input device if you for example don't have pci-passthrough for input devices or want a remote interface anyway (with for example a mediacenter). 2013/2/27 povder : > Hi all > > I'm trying to enable VGA passthrough in linux domU without success. I > want to pass through AMD Radeon HD 4850 - 03:00.0 VGA compatible > controller: Advanced Micro Devices [AMD] nee ATI RV770 [Radeon HD > 4850] as a _primary_ VGA for the VM. Nothing is showing up on the > monitor that I have connected to graphics card's HDMI port. I have > IOMMU enabled. I searched mailing lists and I don't know what to think > about it. There is some information about ATI cards passthrough as > primary VGA, some patches were posted but that was long time ago so my > first question is: > Is passthrough of ATI devices as primary VGA supposed to work now in > Xen 4.2.1 without patches? > > My second question is: > How can i debug the problem? I can't access domU through SSH after > it's created. When I set gfx_passthru to 0 it's starting normally. How > can I tell what went wrong? > > When I create domU I get this in logs: > dm-command: hot insert pass-through pci dev > register_real_device: Assigning real physical device 03:00.0 ... > 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: 0x3:0x0.0x0 > pt_register_regions: IO region registered (size=0x10000000 base_addr=0xd000000c) > pt_register_regions: IO region registered (size=0x00010000 base_addr=0xfe7f0004) > pt_register_regions: IO region registered (size=0x00000100 base_addr=0x0000d001) > pt_register_regions: Expansion ROM registered (size=0x00020000 > base_addr=0xfe7c0002) > pci_intx: intx=1 > register_real_device: Real physical device 03:00.0 registered successfuly! > > I'm using Xen 4.2.1 and xl toolstack. I have the following in VM config file: > > builder = "hvm" > gfx_passthru = 1 > pci = ['03:00.0','03:00.1'] > > vm config file: > full domU log: http://pastebin.com/raw.php?i=rc9xWcDJ > part of lspci -vvv: http://pastebin.com/raw.php?i=wZXcJU7j > xl info: http://pastebin.com/raw.php?i=zDrdNm9u > xl dmesg: http://pastebin.com/raw.php?i=SmJ7MrB1 > > Please help. > > _______________________________________________ > 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 Feb 27 21:33:18 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 27 Feb 2013 21:33: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 1UAobj-0006kT-L7; Wed, 27 Feb 2013 21:32:11 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UAobh-0006kO-Ic for xen-users@lists.xen.org; Wed, 27 Feb 2013 21:32:09 +0000 Received: from [193.109.254.147:13687] by server-16.bemta-14.messagelabs.com id 35/8C-25906-85B7E215; Wed, 27 Feb 2013 21:32:08 +0000 X-Env-Sender: matthias.kannenberg@googlemail.com X-Msg-Ref: server-4.tower-27.messagelabs.com!1362000727!9285030!1 X-Originating-IP: [74.125.82.179] X-SpamReason: No, hits=0.3 required=7.0 tests=RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 13900 invoked from network); 27 Feb 2013 21:32:07 -0000 Received: from mail-we0-f179.google.com (HELO mail-we0-f179.google.com) (74.125.82.179) by server-4.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 27 Feb 2013 21:32:07 -0000 Received: by mail-we0-f179.google.com with SMTP id p43so923507wea.24 for ; Wed, 27 Feb 2013 13:32:07 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=20120113; h=x-received:mime-version:in-reply-to:references:from:date:message-id :subject:to:cc:content-type; bh=FfJTz2LDCkOPl6B0U7ua584xc/+7qtbLkHD4MQddHzM=; b=KbblQgyO9i6MusiKLkoC+fEKpZ/Q4qUD8Rdh24g7O3OzgSM78Fud2ddhHva1UOd9/l 5u9dUWQLSlfHcgCkcszeXEl7QrDrYWNqv6NEPk8dNHBMiSDKHxrCPgYvosumFLzK41Oo siA8bfMfudT0P3NPNmDPB1voNMmD9fJSL9AdNiFll//mKRc/iOzCHs7ZbsO0/VS4eH64 zeNjhHBmK5qmm7kAr/3XMVFvzcJveCobrx0qxQ5A62avpVu6SDH96MlRAQxzARIC9dXL zLO2gEbX7C2qns+6R5Rj8k4YiiqWOAnJkXY4bwHi36miNLIBTH1NmN6z3SaTl56hkZAA R9CQ== X-Received: by 10.194.57.206 with SMTP id k14mr6824506wjq.26.1362000727275; Wed, 27 Feb 2013 13:32:07 -0800 (PST) MIME-Version: 1.0 Received: by 10.194.118.167 with HTTP; Wed, 27 Feb 2013 13:31:47 -0800 (PST) In-Reply-To: References: From: Matthias Date: Wed, 27 Feb 2013 22:31:47 +0100 Message-ID: To: povder Cc: xen-users@lists.xen.org Subject: Re: [Xen-users] VGA passthrough radeon 4850 as primary card X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: 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 there any special reason you use primary passthrough? because using the ati vga as secondary is A LOT easier and simpler (and as stable and performant). To be honest, i never got primary passthrough to work with any of my radeon cards, but secondary works quite well for 2,5 years now. So my advice: use secondary, boot and install domU normally, then install the catalyst driver and reboot. Within the start-process, it will automatically switch to the right vga near the end of the boot and as an additional benefit you can use the vnc view as additional input device if you for example don't have pci-passthrough for input devices or want a remote interface anyway (with for example a mediacenter). 2013/2/27 povder : > Hi all > > I'm trying to enable VGA passthrough in linux domU without success. I > want to pass through AMD Radeon HD 4850 - 03:00.0 VGA compatible > controller: Advanced Micro Devices [AMD] nee ATI RV770 [Radeon HD > 4850] as a _primary_ VGA for the VM. Nothing is showing up on the > monitor that I have connected to graphics card's HDMI port. I have > IOMMU enabled. I searched mailing lists and I don't know what to think > about it. There is some information about ATI cards passthrough as > primary VGA, some patches were posted but that was long time ago so my > first question is: > Is passthrough of ATI devices as primary VGA supposed to work now in > Xen 4.2.1 without patches? > > My second question is: > How can i debug the problem? I can't access domU through SSH after > it's created. When I set gfx_passthru to 0 it's starting normally. How > can I tell what went wrong? > > When I create domU I get this in logs: > dm-command: hot insert pass-through pci dev > register_real_device: Assigning real physical device 03:00.0 ... > 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: 0x3:0x0.0x0 > pt_register_regions: IO region registered (size=0x10000000 base_addr=0xd000000c) > pt_register_regions: IO region registered (size=0x00010000 base_addr=0xfe7f0004) > pt_register_regions: IO region registered (size=0x00000100 base_addr=0x0000d001) > pt_register_regions: Expansion ROM registered (size=0x00020000 > base_addr=0xfe7c0002) > pci_intx: intx=1 > register_real_device: Real physical device 03:00.0 registered successfuly! > > I'm using Xen 4.2.1 and xl toolstack. I have the following in VM config file: > > builder = "hvm" > gfx_passthru = 1 > pci = ['03:00.0','03:00.1'] > > vm config file: > full domU log: http://pastebin.com/raw.php?i=rc9xWcDJ > part of lspci -vvv: http://pastebin.com/raw.php?i=wZXcJU7j > xl info: http://pastebin.com/raw.php?i=zDrdNm9u > xl dmesg: http://pastebin.com/raw.php?i=SmJ7MrB1 > > Please help. > > _______________________________________________ > 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 Feb 28 01:56:19 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 28 Feb 2013 01:56: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 1UAsi2-0007nO-Ar; Thu, 28 Feb 2013 01:54:58 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UAsi0-0007nJ-Sv for xen-users@lists.xen.org; Thu, 28 Feb 2013 01:54:57 +0000 Received: from [85.158.137.99:38102] by server-8.bemta-3.messagelabs.com id 48/CD-20604-FE8BE215; Thu, 28 Feb 2013 01:54:55 +0000 X-Env-Sender: mailing.son@gmail.com X-Msg-Ref: server-6.tower-217.messagelabs.com!1362016495!13346450!1 X-Originating-IP: [74.125.83.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.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 31159 invoked from network); 28 Feb 2013 01:54:55 -0000 Received: from mail-ee0-f52.google.com (HELO mail-ee0-f52.google.com) (74.125.83.52) by server-6.tower-217.messagelabs.com with RC4-SHA encrypted SMTP; 28 Feb 2013 01:54:55 -0000 Received: by mail-ee0-f52.google.com with SMTP id b15so1012805eek.39 for ; Wed, 27 Feb 2013 17:54:55 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:date:message-id:subject:from:to :content-type; bh=wn79IrsRY6kJqMl4SRhAaiR7kDLcwiY4c9C8RSWaDZM=; b=O49bDu/Me9wT1FV8hExomFgfrJojWIuWf0GdJbsRFIZSGc6uUGc4agTW+8ibkDUqwl EF6WfjL6wPFXdvfD5ihXoTzmWNlThC/Vxtvan2uv88iUK8QjfA+NFesMS4F7MRPYrlbq 9D/0V2LxQNon1oHKuRRsZzPJeLNO40JXs3djO+ql6OdJyLFNGYQEeEhvulB7kMXLhykd cvgap/oAqDPSgBm8ZkM42XGsYLwFPF3INhafd9Cz9YKnLC96GLTddvf6m4RG33oI4s6o dbN+2/GSsh8q7LBgMzGk6ENIFdzyPK2pwqjN6VuoqaO93US5DO0+Rn9xJxJc84lqR7sX wlMw== MIME-Version: 1.0 X-Received: by 10.14.207.200 with SMTP id n48mr11847673eeo.4.1362016495267; Wed, 27 Feb 2013 17:54:55 -0800 (PST) Received: by 10.15.90.129 with HTTP; Wed, 27 Feb 2013 17:54:55 -0800 (PST) Date: Thu, 28 Feb 2013 10:54:55 +0900 Message-ID: From: Andrew Son To: xen-users@lists.xen.org Subject: [Xen-users] [Question] How can I know CPU ring information? X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: 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, In a para-virtualization, 32bit guest OS runs in ring 1, and hypervisor runs in ring 0. My question is that: 1) Does guest OS know that my kernel run in ring 1? 2) If so, does hypervisor inform this when guest OS boot? 3) and, where is the ring information, or cpu register? Thanks, Choonho Son _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Thu Feb 28 01:56:19 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 28 Feb 2013 01:56: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 1UAsi2-0007nO-Ar; Thu, 28 Feb 2013 01:54:58 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UAsi0-0007nJ-Sv for xen-users@lists.xen.org; Thu, 28 Feb 2013 01:54:57 +0000 Received: from [85.158.137.99:38102] by server-8.bemta-3.messagelabs.com id 48/CD-20604-FE8BE215; Thu, 28 Feb 2013 01:54:55 +0000 X-Env-Sender: mailing.son@gmail.com X-Msg-Ref: server-6.tower-217.messagelabs.com!1362016495!13346450!1 X-Originating-IP: [74.125.83.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.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 31159 invoked from network); 28 Feb 2013 01:54:55 -0000 Received: from mail-ee0-f52.google.com (HELO mail-ee0-f52.google.com) (74.125.83.52) by server-6.tower-217.messagelabs.com with RC4-SHA encrypted SMTP; 28 Feb 2013 01:54:55 -0000 Received: by mail-ee0-f52.google.com with SMTP id b15so1012805eek.39 for ; Wed, 27 Feb 2013 17:54:55 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:date:message-id:subject:from:to :content-type; bh=wn79IrsRY6kJqMl4SRhAaiR7kDLcwiY4c9C8RSWaDZM=; b=O49bDu/Me9wT1FV8hExomFgfrJojWIuWf0GdJbsRFIZSGc6uUGc4agTW+8ibkDUqwl EF6WfjL6wPFXdvfD5ihXoTzmWNlThC/Vxtvan2uv88iUK8QjfA+NFesMS4F7MRPYrlbq 9D/0V2LxQNon1oHKuRRsZzPJeLNO40JXs3djO+ql6OdJyLFNGYQEeEhvulB7kMXLhykd cvgap/oAqDPSgBm8ZkM42XGsYLwFPF3INhafd9Cz9YKnLC96GLTddvf6m4RG33oI4s6o dbN+2/GSsh8q7LBgMzGk6ENIFdzyPK2pwqjN6VuoqaO93US5DO0+Rn9xJxJc84lqR7sX wlMw== MIME-Version: 1.0 X-Received: by 10.14.207.200 with SMTP id n48mr11847673eeo.4.1362016495267; Wed, 27 Feb 2013 17:54:55 -0800 (PST) Received: by 10.15.90.129 with HTTP; Wed, 27 Feb 2013 17:54:55 -0800 (PST) Date: Thu, 28 Feb 2013 10:54:55 +0900 Message-ID: From: Andrew Son To: xen-users@lists.xen.org Subject: [Xen-users] [Question] How can I know CPU ring information? X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: 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, In a para-virtualization, 32bit guest OS runs in ring 1, and hypervisor runs in ring 0. My question is that: 1) Does guest OS know that my kernel run in ring 1? 2) If so, does hypervisor inform this when guest OS boot? 3) and, where is the ring information, or cpu register? Thanks, Choonho Son _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Thu Feb 28 04:45:19 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 28 Feb 2013 04:45: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 1UAvLf-0001od-Od; Thu, 28 Feb 2013 04:44:03 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UAvLd-0001oY-TZ for xen-users@lists.xen.org; Thu, 28 Feb 2013 04:44:02 +0000 Received: from [85.158.139.211:59497] by server-1.bemta-5.messagelabs.com id 72/DC-14063-190EE215; Thu, 28 Feb 2013 04:44:01 +0000 X-Env-Sender: ecosoft13@gmail.com X-Msg-Ref: server-13.tower-206.messagelabs.com!1362026636!15664501!1 X-Originating-IP: [209.85.128.179] 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.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 24415 invoked from network); 28 Feb 2013 04:43:57 -0000 Received: from mail-ve0-f179.google.com (HELO mail-ve0-f179.google.com) (209.85.128.179) by server-13.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 28 Feb 2013 04:43:57 -0000 Received: by mail-ve0-f179.google.com with SMTP id da11so1399421veb.10 for ; Wed, 27 Feb 2013 20:43:55 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=o7ZkTY8MpOV2KAPch0MRk3QnqaXDBZ4GEj858Uvqo7o=; b=gC2gcFeZmKBfhXcS6COAcPtLPcbxqwzl5yAeT0DRtH7kUOohBK+UT42UDDsceIysfg l9XvP32wVufXGBqaBRbUr3iTySjoYqpt5eQLFhV2dvgpiPRiJnBsEGsM4ES5n5gT1O8z AF7NqVl5aTS3Gv4n3Mg1OemYShdDuTrr5/whHaHDaaxUX84ig+OUOtK6lQnDXhSbOpvS Wg9BJ9q5vT+7KJ3XBVXfM6aS28vlwSOmbRnsgJePThcRSk6WzrLeSeYHhAE1lYcnNHTI 24GTOEdTS06bN1+duQo4rEVDArXNSEr7UY8nqpxvFEgsyXeSV/jksTpWAylMoksNMqi6 7RkQ== MIME-Version: 1.0 X-Received: by 10.220.8.75 with SMTP id g11mr1915200vcg.60.1362026635786; Wed, 27 Feb 2013 20:43:55 -0800 (PST) Received: by 10.221.13.194 with HTTP; Wed, 27 Feb 2013 20:43:55 -0800 (PST) In-Reply-To: <1361874116.26546.256.camel@zakaz.uk.xensource.com> References: <1361874116.26546.256.camel@zakaz.uk.xensource.com> Date: Wed, 27 Feb 2013 22:43:55 -0600 Message-ID: From: Yaodong Yang To: Ian Campbell Cc: "xen-users@lists.xen.org" Subject: Re: [Xen-users] Xen Domain U can not install (on Ubuntu.) X-BeenThere: xen-users@lists.xen.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="===============8392410125714685154==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============8392410125714685154== Content-Type: multipart/alternative; boundary=bcaec54b4568cd06fe04d6c1892a --bcaec54b4568cd06fe04d6c1892a Content-Type: text/plain; charset=ISO-8859-1 Hello Ian, I download the following disk. On Tue, Feb 26, 2013 at 4:21 AM, Ian Campbell wrote: > On Mon, 2013-02-25 at 18:41 +0000, Yaodong Yang wrote: > > > > When I was installing the domain U (also a Ubuntu image), I was told > > the dhcp does not work. If I choose not to configure dhcp, then I was > > asked to choose a mirror. But in fact, I already download the image in > > disk. > > Which exact disk have you downloaded? > > I download the following disk images. sudo wget http://mirror.anl.gov/pub/ubuntu/dists/precise/main/installer-amd64/current/images/netboot/xen/initrd.gzsudo wget http://mirror.anl.gov/pub/ubuntu/dists/precise/main/installer-amd64/current/images/netboot/xen/vmlinuz > Please provide your guest configuration file. > my guest configuration file is the same as that tutorial. > name = "ubuntu"memory = 256disk = ['phy:/dev//ubuntu,xvda,w']vif = [' ']kernel = "/var/lib/xen/images/ubuntu-netboot/vmlinuz"ramdisk = "/var/lib/xen/images/ubuntu-netboot/initrd.gz"extra = "debian-installer/exit/always_halt=true -- console=hvc0" > > Ian. > > > I think it's related to the bridge network setting. I searched online and still have no idea about it. Thanks for your help! Yaodong --bcaec54b4568cd06fe04d6c1892a Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable 
Hello Ian,
I download the following disk.


On Tue,= Feb 26, 2013 at 4:21 AM, Ian Campbell <Ian.Campbell@citrix.com&= gt; wrote:
On Mon, 2013-02-25 at 18:41 +0000, Yaodo= ng Yang wrote:


> When I was installing the domain U (also a Ubuntu image), I was told > the dhcp does not work. If I choose not to configure dhcp, then I was<= br> > asked to choose a mirror. But in fact, I already download the image in=
> disk.

Which exact disk have you downloaded?

I download the following disk images.=A0
<= div>
sudo wget http://mirror.anl.gov/p=
ub/ubuntu/dists/precise/main/installer-amd64/current/images/netboot/xen/ini=
trd.gz
sudo wget http://mirror.=
anl.gov/pub/ubuntu/dists/precise/main/installer-amd64/current/images/netboo=
t/xen/vmlinuz
=A0
Please provide your guest configuration file.
=A0
my guest configuration file is the same as that tutorial.=A0
name =3D "ubuntu"

memory =3D 256

disk =3D ['phy:/dev/<VG>/ubuntu,xvda,w']
vif =3D [' ']

kernel =3D "/var/lib/xen/images/ubuntu-netboot/vmlinuz"=
;
ramdisk =3D "/var/lib/xen/images/ubuntu-netboot/initrd.gz&q=
uot;
extra =3D "debian-installer/exit/always_halt=3Dtrue -- conso=
le=3Dhvc0"
Ian.


I think it's related to the bridge net= work setting. I searched online and still have no idea about it.

Thanks for= your help!

Yaodong
--bcaec54b4568cd06fe04d6c1892a-- --===============8392410125714685154== 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 --===============8392410125714685154==-- From xen-users-bounces@lists.xen.org Thu Feb 28 04:45:19 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 28 Feb 2013 04:45: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 1UAvLf-0001od-Od; Thu, 28 Feb 2013 04:44:03 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UAvLd-0001oY-TZ for xen-users@lists.xen.org; Thu, 28 Feb 2013 04:44:02 +0000 Received: from [85.158.139.211:59497] by server-1.bemta-5.messagelabs.com id 72/DC-14063-190EE215; Thu, 28 Feb 2013 04:44:01 +0000 X-Env-Sender: ecosoft13@gmail.com X-Msg-Ref: server-13.tower-206.messagelabs.com!1362026636!15664501!1 X-Originating-IP: [209.85.128.179] 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.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 24415 invoked from network); 28 Feb 2013 04:43:57 -0000 Received: from mail-ve0-f179.google.com (HELO mail-ve0-f179.google.com) (209.85.128.179) by server-13.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 28 Feb 2013 04:43:57 -0000 Received: by mail-ve0-f179.google.com with SMTP id da11so1399421veb.10 for ; Wed, 27 Feb 2013 20:43:55 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=o7ZkTY8MpOV2KAPch0MRk3QnqaXDBZ4GEj858Uvqo7o=; b=gC2gcFeZmKBfhXcS6COAcPtLPcbxqwzl5yAeT0DRtH7kUOohBK+UT42UDDsceIysfg l9XvP32wVufXGBqaBRbUr3iTySjoYqpt5eQLFhV2dvgpiPRiJnBsEGsM4ES5n5gT1O8z AF7NqVl5aTS3Gv4n3Mg1OemYShdDuTrr5/whHaHDaaxUX84ig+OUOtK6lQnDXhSbOpvS Wg9BJ9q5vT+7KJ3XBVXfM6aS28vlwSOmbRnsgJePThcRSk6WzrLeSeYHhAE1lYcnNHTI 24GTOEdTS06bN1+duQo4rEVDArXNSEr7UY8nqpxvFEgsyXeSV/jksTpWAylMoksNMqi6 7RkQ== MIME-Version: 1.0 X-Received: by 10.220.8.75 with SMTP id g11mr1915200vcg.60.1362026635786; Wed, 27 Feb 2013 20:43:55 -0800 (PST) Received: by 10.221.13.194 with HTTP; Wed, 27 Feb 2013 20:43:55 -0800 (PST) In-Reply-To: <1361874116.26546.256.camel@zakaz.uk.xensource.com> References: <1361874116.26546.256.camel@zakaz.uk.xensource.com> Date: Wed, 27 Feb 2013 22:43:55 -0600 Message-ID: From: Yaodong Yang To: Ian Campbell Cc: "xen-users@lists.xen.org" Subject: Re: [Xen-users] Xen Domain U can not install (on Ubuntu.) X-BeenThere: xen-users@lists.xen.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="===============8392410125714685154==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============8392410125714685154== Content-Type: multipart/alternative; boundary=bcaec54b4568cd06fe04d6c1892a --bcaec54b4568cd06fe04d6c1892a Content-Type: text/plain; charset=ISO-8859-1 Hello Ian, I download the following disk. On Tue, Feb 26, 2013 at 4:21 AM, Ian Campbell wrote: > On Mon, 2013-02-25 at 18:41 +0000, Yaodong Yang wrote: > > > > When I was installing the domain U (also a Ubuntu image), I was told > > the dhcp does not work. If I choose not to configure dhcp, then I was > > asked to choose a mirror. But in fact, I already download the image in > > disk. > > Which exact disk have you downloaded? > > I download the following disk images. sudo wget http://mirror.anl.gov/pub/ubuntu/dists/precise/main/installer-amd64/current/images/netboot/xen/initrd.gzsudo wget http://mirror.anl.gov/pub/ubuntu/dists/precise/main/installer-amd64/current/images/netboot/xen/vmlinuz > Please provide your guest configuration file. > my guest configuration file is the same as that tutorial. > name = "ubuntu"memory = 256disk = ['phy:/dev//ubuntu,xvda,w']vif = [' ']kernel = "/var/lib/xen/images/ubuntu-netboot/vmlinuz"ramdisk = "/var/lib/xen/images/ubuntu-netboot/initrd.gz"extra = "debian-installer/exit/always_halt=true -- console=hvc0" > > Ian. > > > I think it's related to the bridge network setting. I searched online and still have no idea about it. Thanks for your help! Yaodong --bcaec54b4568cd06fe04d6c1892a Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable 
Hello Ian,
I download the following disk.


On Tue,= Feb 26, 2013 at 4:21 AM, Ian Campbell <Ian.Campbell@citrix.com&= gt; wrote:
On Mon, 2013-02-25 at 18:41 +0000, Yaodo= ng Yang wrote:


> When I was installing the domain U (also a Ubuntu image), I was told > the dhcp does not work. If I choose not to configure dhcp, then I was<= br> > asked to choose a mirror. But in fact, I already download the image in=
> disk.

Which exact disk have you downloaded?

I download the following disk images.=A0
<= div>
sudo wget http://mirror.anl.gov/p=
ub/ubuntu/dists/precise/main/installer-amd64/current/images/netboot/xen/ini=
trd.gz
sudo wget http://mirror.=
anl.gov/pub/ubuntu/dists/precise/main/installer-amd64/current/images/netboo=
t/xen/vmlinuz
=A0
Please provide your guest configuration file.
=A0
my guest configuration file is the same as that tutorial.=A0
name =3D "ubuntu"

memory =3D 256

disk =3D ['phy:/dev/<VG>/ubuntu,xvda,w']
vif =3D [' ']

kernel =3D "/var/lib/xen/images/ubuntu-netboot/vmlinuz"=
;
ramdisk =3D "/var/lib/xen/images/ubuntu-netboot/initrd.gz&q=
uot;
extra =3D "debian-installer/exit/always_halt=3Dtrue -- conso=
le=3Dhvc0"
Ian.


I think it's related to the bridge net= work setting. I searched online and still have no idea about it.

Thanks for= your help!

Yaodong
--bcaec54b4568cd06fe04d6c1892a-- --===============8392410125714685154== 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 --===============8392410125714685154==-- From xen-users-bounces@lists.xen.org Thu Feb 28 06:57:23 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 28 Feb 2013 06:57: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 1UAxPa-0004Cm-Mi; Thu, 28 Feb 2013 06:56:14 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UAxPY-0004Ch-Ls for xen-users@lists.xen.org; Thu, 28 Feb 2013 06:56:12 +0000 Received: from [85.158.137.99:48271] by server-6.bemta-3.messagelabs.com id 67/64-11048-B8FFE215; Thu, 28 Feb 2013 06:56:11 +0000 X-Env-Sender: Ian.Campbell@citrix.com X-Msg-Ref: server-12.tower-217.messagelabs.com!1362034568!15086248!1 X-Originating-IP: [46.33.159.39] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNDYuMzMuMTU5LjM5ID0+IDI0NjEw\n X-StarScan-Received: X-StarScan-Version: 6.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 3816 invoked from network); 28 Feb 2013 06:56:08 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (46.33.159.39) by server-12.tower-217.messagelabs.com with RC4-SHA encrypted SMTP; 28 Feb 2013 06:56:08 -0000 X-IronPort-AV: E=Sophos;i="4.84,753,1355097600"; d="scan'208";a="1992423" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 28 Feb 2013 06:56:07 +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.297.1; Thu, 28 Feb 2013 06:56:06 +0000 Message-ID: <1362034566.23384.10.camel@dagon.hellion.org.uk> From: Ian Campbell To: Yaodong Yang Date: Thu, 28 Feb 2013 06:56:06 +0000 In-Reply-To: References: <1361874116.26546.256.camel@zakaz.uk.xensource.com> Organization: Citrix Systems, Inc. X-Mailer: Evolution 3.4.4-1 MIME-Version: 1.0 Cc: "xen-users@lists.xen.org" Subject: Re: [Xen-users] Xen Domain U can not install (on Ubuntu.) X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: 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, 2013-02-28 at 04:43 +0000, Yaodong Yang wrote: > I download the following disk images. > sudo wget http://mirror.anl.gov/pub/ubuntu/dists/precise/main/installer-amd64/current/images/netboot/xen/initrd.gz > sudo wget http://mirror.anl.gov/pub/ubuntu/dists/precise/main/installer-amd64/current/images/netboot/xen/vmlinuz These are not disks, they are a netboot kernel and initrd. There are no actual Ubuntu packages included with these so to install you will also need access to a mirror. > I think it's related to the bridge network setting. I searched online > and still have no idea about it. Please see: http://wiki.xen.org/wiki/Xen_Networking http://wiki.xen.org/wiki/Host_Configuration/Networking If you think bridge networking is an issue then it would have been useful to provide your host networking configuration, e.g. the output of "brctl show" and the content of /etc/network/interfaces. Ian. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Thu Feb 28 06:57:23 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 28 Feb 2013 06:57: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 1UAxPa-0004Cm-Mi; Thu, 28 Feb 2013 06:56:14 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UAxPY-0004Ch-Ls for xen-users@lists.xen.org; Thu, 28 Feb 2013 06:56:12 +0000 Received: from [85.158.137.99:48271] by server-6.bemta-3.messagelabs.com id 67/64-11048-B8FFE215; Thu, 28 Feb 2013 06:56:11 +0000 X-Env-Sender: Ian.Campbell@citrix.com X-Msg-Ref: server-12.tower-217.messagelabs.com!1362034568!15086248!1 X-Originating-IP: [46.33.159.39] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNDYuMzMuMTU5LjM5ID0+IDI0NjEw\n X-StarScan-Received: X-StarScan-Version: 6.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 3816 invoked from network); 28 Feb 2013 06:56:08 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (46.33.159.39) by server-12.tower-217.messagelabs.com with RC4-SHA encrypted SMTP; 28 Feb 2013 06:56:08 -0000 X-IronPort-AV: E=Sophos;i="4.84,753,1355097600"; d="scan'208";a="1992423" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 28 Feb 2013 06:56:07 +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.297.1; Thu, 28 Feb 2013 06:56:06 +0000 Message-ID: <1362034566.23384.10.camel@dagon.hellion.org.uk> From: Ian Campbell To: Yaodong Yang Date: Thu, 28 Feb 2013 06:56:06 +0000 In-Reply-To: References: <1361874116.26546.256.camel@zakaz.uk.xensource.com> Organization: Citrix Systems, Inc. X-Mailer: Evolution 3.4.4-1 MIME-Version: 1.0 Cc: "xen-users@lists.xen.org" Subject: Re: [Xen-users] Xen Domain U can not install (on Ubuntu.) X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: 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, 2013-02-28 at 04:43 +0000, Yaodong Yang wrote: > I download the following disk images. > sudo wget http://mirror.anl.gov/pub/ubuntu/dists/precise/main/installer-amd64/current/images/netboot/xen/initrd.gz > sudo wget http://mirror.anl.gov/pub/ubuntu/dists/precise/main/installer-amd64/current/images/netboot/xen/vmlinuz These are not disks, they are a netboot kernel and initrd. There are no actual Ubuntu packages included with these so to install you will also need access to a mirror. > I think it's related to the bridge network setting. I searched online > and still have no idea about it. Please see: http://wiki.xen.org/wiki/Xen_Networking http://wiki.xen.org/wiki/Host_Configuration/Networking If you think bridge networking is an issue then it would have been useful to provide your host networking configuration, e.g. the output of "brctl show" and the content of /etc/network/interfaces. Ian. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Thu Feb 28 07:28:01 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 28 Feb 2013 07:28: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 1UAxtE-000503-EZ; Thu, 28 Feb 2013 07:26:52 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UAxtD-0004zI-Kb for xen-users@lists.xen.org; Thu, 28 Feb 2013 07:26:51 +0000 Received: from [85.158.138.51:32634] by server-4.bemta-3.messagelabs.com id A7/17-21470-AB60F215; Thu, 28 Feb 2013 07:26:50 +0000 X-Env-Sender: flokeshw24@gmail.com X-Msg-Ref: server-6.tower-174.messagelabs.com!1362036409!19841963!1 X-Originating-IP: [74.125.82.46] 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.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 29424 invoked from network); 28 Feb 2013 07:26:50 -0000 Received: from mail-wg0-f46.google.com (HELO mail-wg0-f46.google.com) (74.125.82.46) by server-6.tower-174.messagelabs.com with RC4-SHA encrypted SMTP; 28 Feb 2013 07:26:50 -0000 Received: by mail-wg0-f46.google.com with SMTP id fg15so1164287wgb.13 for ; Wed, 27 Feb 2013 23:26:36 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:date:message-id:subject:from:to :content-type; bh=4lvGmiLhTypfzGcbka4TZcRiEWEsdXz+ti8SYEKbDfo=; b=zflEauTc8Kb3jJF5r7ZcxkxBjaJl30/v9P81FUMVo2beJtW7vlcrvE35q3SC0/4Xrb Ryan0quB5htYg7DTinTO0KUHj5OfvX6BqHpmliskcDr47Hig66t1gzHeWhH6Kk14didM Am/0fq6DtOHVnH9Qo/lGnwf09mgABZByAQCX0KTlLoCS9ag4wUfln2Zn5tzojjVyg+ih czbdPrnOESsBlcMH2GZfA2jA1X74psVIz9Ok3qndP/15D2Hf93wFThonfhVC2ct9udje vtCEHVquLtEBgIed1zgX/XSBkeRy3b1/jLgGwV8pf9yo9MsOe/YDneELwu+TQ6PIJmHz gkfQ== MIME-Version: 1.0 X-Received: by 10.194.76.37 with SMTP id h5mr8928568wjw.21.1362036396462; Wed, 27 Feb 2013 23:26:36 -0800 (PST) Received: by 10.194.134.73 with HTTP; Wed, 27 Feb 2013 23:26:36 -0800 (PST) Date: Thu, 28 Feb 2013 12:56:36 +0530 Message-ID: From: Lokesh Walase To: xen-users@lists.xen.org Subject: [Xen-users] After VM migration , shows entry at both destination & 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="===============3189930221639042897==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============3189930221639042897== Content-Type: multipart/alternative; boundary=047d7bb03bc49518c604d6c3cf25 --047d7bb03bc49518c604d6c3cf25 Content-Type: text/plain; charset=ISO-8859-1 Hello, I have installed xen-hypervisor-4.1-amd64 successfully on 4 hosts (with Ubuntu-12.04 as dom0). I tried live migration of a virtual machine from one host to another via command line : xm migrate -l ( host_ip_adrress is static-ip ) The problems are : 1. During migration, I can see the entry of the VM appearing in the Virtual Machine Manager (VMM) of destination host. 2. After migration is complete, both the source as well as the destination host show the entry for corresponding VM in VMM. 3. After reboot, the destination host does not show migrated VM, but the entry on the source host stays as it was previously. So basically after reboot, the migrated VM stays on host only. --047d7bb03bc49518c604d6c3cf25 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Hello,
=A0=A0=A0=A0=A0=A0 I have installed=20 xen-hypervisor-4.1-amd64 successfully on 4 hosts (with Ubuntu-12.04 as=20 dom0).
=A0=A0=A0=A0=A0=A0 I tried live migration of a virtual machine f= rom one host to=20 another via command line : xm migrate -l <domain_id> <host_ip_addr= ess>
=A0=A0=A0=A0=A0=A0 ( host_ip_adrress is static-ip )

The p= roblems are :

=A0 =A0 =A0=A0 1. During migration, I can see the entry of the VM app= earing in the Virtual Machine Manager (VMM) of destination host.
= =A0 =A0 =A0=A0 2. After migration is complete, both the source as well as the= =20 destination host show the entry for corresponding VM in VMM.
=A0=A0=A0=A0=A0=A0 3. After reboot, the destination host does not sho= w=A0 migrated VM, but the entry on the source host stays as it=20 was previously.
=A0=A0=A0=A0=A0=A0=A0 So basically after reboot, the mi= grated VM stays on host only.
--047d7bb03bc49518c604d6c3cf25-- --===============3189930221639042897== 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 --===============3189930221639042897==-- From xen-users-bounces@lists.xen.org Thu Feb 28 07:28:01 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 28 Feb 2013 07:28: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 1UAxtE-000503-EZ; Thu, 28 Feb 2013 07:26:52 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UAxtD-0004zI-Kb for xen-users@lists.xen.org; Thu, 28 Feb 2013 07:26:51 +0000 Received: from [85.158.138.51:32634] by server-4.bemta-3.messagelabs.com id A7/17-21470-AB60F215; Thu, 28 Feb 2013 07:26:50 +0000 X-Env-Sender: flokeshw24@gmail.com X-Msg-Ref: server-6.tower-174.messagelabs.com!1362036409!19841963!1 X-Originating-IP: [74.125.82.46] 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.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 29424 invoked from network); 28 Feb 2013 07:26:50 -0000 Received: from mail-wg0-f46.google.com (HELO mail-wg0-f46.google.com) (74.125.82.46) by server-6.tower-174.messagelabs.com with RC4-SHA encrypted SMTP; 28 Feb 2013 07:26:50 -0000 Received: by mail-wg0-f46.google.com with SMTP id fg15so1164287wgb.13 for ; Wed, 27 Feb 2013 23:26:36 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:date:message-id:subject:from:to :content-type; bh=4lvGmiLhTypfzGcbka4TZcRiEWEsdXz+ti8SYEKbDfo=; b=zflEauTc8Kb3jJF5r7ZcxkxBjaJl30/v9P81FUMVo2beJtW7vlcrvE35q3SC0/4Xrb Ryan0quB5htYg7DTinTO0KUHj5OfvX6BqHpmliskcDr47Hig66t1gzHeWhH6Kk14didM Am/0fq6DtOHVnH9Qo/lGnwf09mgABZByAQCX0KTlLoCS9ag4wUfln2Zn5tzojjVyg+ih czbdPrnOESsBlcMH2GZfA2jA1X74psVIz9Ok3qndP/15D2Hf93wFThonfhVC2ct9udje vtCEHVquLtEBgIed1zgX/XSBkeRy3b1/jLgGwV8pf9yo9MsOe/YDneELwu+TQ6PIJmHz gkfQ== MIME-Version: 1.0 X-Received: by 10.194.76.37 with SMTP id h5mr8928568wjw.21.1362036396462; Wed, 27 Feb 2013 23:26:36 -0800 (PST) Received: by 10.194.134.73 with HTTP; Wed, 27 Feb 2013 23:26:36 -0800 (PST) Date: Thu, 28 Feb 2013 12:56:36 +0530 Message-ID: From: Lokesh Walase To: xen-users@lists.xen.org Subject: [Xen-users] After VM migration , shows entry at both destination & 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="===============3189930221639042897==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============3189930221639042897== Content-Type: multipart/alternative; boundary=047d7bb03bc49518c604d6c3cf25 --047d7bb03bc49518c604d6c3cf25 Content-Type: text/plain; charset=ISO-8859-1 Hello, I have installed xen-hypervisor-4.1-amd64 successfully on 4 hosts (with Ubuntu-12.04 as dom0). I tried live migration of a virtual machine from one host to another via command line : xm migrate -l ( host_ip_adrress is static-ip ) The problems are : 1. During migration, I can see the entry of the VM appearing in the Virtual Machine Manager (VMM) of destination host. 2. After migration is complete, both the source as well as the destination host show the entry for corresponding VM in VMM. 3. After reboot, the destination host does not show migrated VM, but the entry on the source host stays as it was previously. So basically after reboot, the migrated VM stays on host only. --047d7bb03bc49518c604d6c3cf25 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Hello,
=A0=A0=A0=A0=A0=A0 I have installed=20 xen-hypervisor-4.1-amd64 successfully on 4 hosts (with Ubuntu-12.04 as=20 dom0).
=A0=A0=A0=A0=A0=A0 I tried live migration of a virtual machine f= rom one host to=20 another via command line : xm migrate -l <domain_id> <host_ip_addr= ess>
=A0=A0=A0=A0=A0=A0 ( host_ip_adrress is static-ip )

The p= roblems are :

=A0 =A0 =A0=A0 1. During migration, I can see the entry of the VM app= earing in the Virtual Machine Manager (VMM) of destination host.
= =A0 =A0 =A0=A0 2. After migration is complete, both the source as well as the= =20 destination host show the entry for corresponding VM in VMM.
=A0=A0=A0=A0=A0=A0 3. After reboot, the destination host does not sho= w=A0 migrated VM, but the entry on the source host stays as it=20 was previously.
=A0=A0=A0=A0=A0=A0=A0 So basically after reboot, the mi= grated VM stays on host only.
--047d7bb03bc49518c604d6c3cf25-- --===============3189930221639042897== 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 --===============3189930221639042897==-- From xen-users-bounces@lists.xen.org Thu Feb 28 09:16:27 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 28 Feb 2013 09:16: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 1UAza7-0002fN-9W; Thu, 28 Feb 2013 09:15:15 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UAza6-0002fI-D7 for xen-users@lists.xen.org; Thu, 28 Feb 2013 09:15:14 +0000 Received: from [85.158.138.51:35667] by server-13.bemta-3.messagelabs.com id B2/D4-25744-1202F215; Thu, 28 Feb 2013 09:15:13 +0000 X-Env-Sender: povder@gmail.com X-Msg-Ref: server-4.tower-174.messagelabs.com!1362042909!29527837!1 X-Originating-IP: [209.85.220.178] 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.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 16937 invoked from network); 28 Feb 2013 09:15:11 -0000 Received: from mail-vc0-f178.google.com (HELO mail-vc0-f178.google.com) (209.85.220.178) by server-4.tower-174.messagelabs.com with RC4-SHA encrypted SMTP; 28 Feb 2013 09:15:11 -0000 Received: by mail-vc0-f178.google.com with SMTP id m8so1048693vcd.37 for ; Thu, 28 Feb 2013 01:15:09 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:mime-version:in-reply-to:references:from:date:message-id :subject:to:cc:content-type; bh=S+vgP7+j2+dw9f51GniIbheFgjmzbLkZmdh2XxrUPJU=; b=ksPyi5k+E7mrG49CDv34V0l2QTlVGUvkXJ2ug2eiLSwS46t0PVxK+/Fi9OmBZDkzWI ZP5xphD6OZnD+UX1NKftOUwtrFkR4i73iO6a9ZbM51eRXkzayTDibTbSYVymKm13xq6R Kb6Strh7pwwAL47Rj1SeW8xxNFzSZaxYmj6tZtNhMO87TIPV4uRvoaYr56OXJrB83Bew NysgIMXVgZq/G6J/jTpQCnePOCDUIeP0FhIardNf357hJyYT4rl1g85xGk6IKJNCqx2C 8Rfx/QmMGNAWgVy3hmeLPMzGX7/ioryPlUNjbsowtG+gePYu1BtzHB5aDoASaeeYc4Of PV8w== X-Received: by 10.220.150.83 with SMTP id x19mr2208980vcv.25.1362042909569; Thu, 28 Feb 2013 01:15:09 -0800 (PST) MIME-Version: 1.0 Received: by 10.58.203.106 with HTTP; Thu, 28 Feb 2013 01:14:49 -0800 (PST) In-Reply-To: References: From: povder Date: Thu, 28 Feb 2013 10:14:49 +0100 Message-ID: To: Matthias Cc: xen-users@lists.xen.org Subject: Re: [Xen-users] VGA passthrough radeon 4850 as primary card X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: 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 your reply. I guess I'll give up the idea of passing through Radeon VGA as primary card. I was trying to pass through it as primary because I couldn't get it to work as secondary because I wasn't using catalyst drivers - now it's working with catalyst drivers :) I have another problem now, but it's probably not xen related. When I run glxinfo I get: X Error of failed request: BadRequest (invalid request code or no such operation) Major opcode of failed request: 139 (ATIFGLEXTENSION) Minor opcode of failed request: 66 () Serial number of failed request: 13 Current serial number in output stream: 13 _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Thu Feb 28 09:16:27 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 28 Feb 2013 09:16: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 1UAza7-0002fN-9W; Thu, 28 Feb 2013 09:15:15 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UAza6-0002fI-D7 for xen-users@lists.xen.org; Thu, 28 Feb 2013 09:15:14 +0000 Received: from [85.158.138.51:35667] by server-13.bemta-3.messagelabs.com id B2/D4-25744-1202F215; Thu, 28 Feb 2013 09:15:13 +0000 X-Env-Sender: povder@gmail.com X-Msg-Ref: server-4.tower-174.messagelabs.com!1362042909!29527837!1 X-Originating-IP: [209.85.220.178] 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.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 16937 invoked from network); 28 Feb 2013 09:15:11 -0000 Received: from mail-vc0-f178.google.com (HELO mail-vc0-f178.google.com) (209.85.220.178) by server-4.tower-174.messagelabs.com with RC4-SHA encrypted SMTP; 28 Feb 2013 09:15:11 -0000 Received: by mail-vc0-f178.google.com with SMTP id m8so1048693vcd.37 for ; Thu, 28 Feb 2013 01:15:09 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:mime-version:in-reply-to:references:from:date:message-id :subject:to:cc:content-type; bh=S+vgP7+j2+dw9f51GniIbheFgjmzbLkZmdh2XxrUPJU=; b=ksPyi5k+E7mrG49CDv34V0l2QTlVGUvkXJ2ug2eiLSwS46t0PVxK+/Fi9OmBZDkzWI ZP5xphD6OZnD+UX1NKftOUwtrFkR4i73iO6a9ZbM51eRXkzayTDibTbSYVymKm13xq6R Kb6Strh7pwwAL47Rj1SeW8xxNFzSZaxYmj6tZtNhMO87TIPV4uRvoaYr56OXJrB83Bew NysgIMXVgZq/G6J/jTpQCnePOCDUIeP0FhIardNf357hJyYT4rl1g85xGk6IKJNCqx2C 8Rfx/QmMGNAWgVy3hmeLPMzGX7/ioryPlUNjbsowtG+gePYu1BtzHB5aDoASaeeYc4Of PV8w== X-Received: by 10.220.150.83 with SMTP id x19mr2208980vcv.25.1362042909569; Thu, 28 Feb 2013 01:15:09 -0800 (PST) MIME-Version: 1.0 Received: by 10.58.203.106 with HTTP; Thu, 28 Feb 2013 01:14:49 -0800 (PST) In-Reply-To: References: From: povder Date: Thu, 28 Feb 2013 10:14:49 +0100 Message-ID: To: Matthias Cc: xen-users@lists.xen.org Subject: Re: [Xen-users] VGA passthrough radeon 4850 as primary card X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: 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 your reply. I guess I'll give up the idea of passing through Radeon VGA as primary card. I was trying to pass through it as primary because I couldn't get it to work as secondary because I wasn't using catalyst drivers - now it's working with catalyst drivers :) I have another problem now, but it's probably not xen related. When I run glxinfo I get: X Error of failed request: BadRequest (invalid request code or no such operation) Major opcode of failed request: 139 (ATIFGLEXTENSION) Minor opcode of failed request: 66 () Serial number of failed request: 13 Current serial number in output stream: 13 _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Thu Feb 28 10:04:37 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 28 Feb 2013 10:04: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 1UB0Kq-0004dm-OP; Thu, 28 Feb 2013 10:03:32 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UB0Kp-0004dg-6J for xen-users@lists.xen.org; Thu, 28 Feb 2013 10:03:31 +0000 Received: from [85.158.139.83:54587] by server-14.bemta-5.messagelabs.com id EC/CF-13158-27B2F215; Thu, 28 Feb 2013 10:03:30 +0000 X-Env-Sender: peter.maloney@brockmann-consult.de X-Msg-Ref: server-14.tower-182.messagelabs.com!1362045809!25056067!1 X-Originating-IP: [212.227.126.186] X-SpamReason: No, hits=1.8 required=7.0 tests=sa_preprocessor: QmFkIElQOiAyMTIuMjI3LjEyNi4xODYgPT4gNTk3ODQ=\n,sa_preprocessor: QmFkIElQOiAyMTIuMjI3LjEyNi4xODYgPT4gNTk3ODQ=\n,RATWARE_GECKO_BUILD X-StarScan-Received: X-StarScan-Version: 6.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 16223 invoked from network); 28 Feb 2013 10:03:29 -0000 Received: from moutng.kundenserver.de (HELO moutng.kundenserver.de) (212.227.126.186) by server-14.tower-182.messagelabs.com with RC4-SHA encrypted SMTP; 28 Feb 2013 10:03:29 -0000 Received: from [10.3.0.26] ([141.4.215.32]) by mrelayeu.kundenserver.de (node=mrbap0) with ESMTP (Nemesis) id 0MUTUB-1UJ0ew0O03-00RSiq; Thu, 28 Feb 2013 11:03:29 +0100 Message-ID: <512F2B70.4080306@brockmann-consult.de> Date: Thu, 28 Feb 2013 11:03:28 +0100 From: Peter Maloney User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/17.0 Thunderbird/17.0 MIME-Version: 1.0 To: xen-users@lists.xen.org References: In-Reply-To: X-Enigmail-Version: 1.5 X-Provags-ID: V02:K0:swLAU3E2s2PkQssQ1a79nPt2I1992wjprbkARVP3B4Z sASYxkzoAah4dhalLKK9ni21u9L51HNshvm6cF0M22+uY+ZW4k LZmWczZUgCgfUOZkwPJ/853lIA1cQqpACEj7jVpjwY5rcwLPp6 Qfr57mM1f4JP9HU9ogUDbA4ZrZktheMdj40wczZb8DX6Tnpvlh Vhdeo6ZHGrKXUh9SR2kUi+FO6oiI6vJgjTmdDNgHtrlYsksJ34 ERgFi34bV4Cys/BuWg+qFyNUNK5O3Mr55gkKtaGMBnML5wdRM5 FuPIWCQ1rbJ3fLFTG80haxY1OlqHLMNoahnohNCTHeS53kw17v ExeAQ8fMTj81dAmLmEo1a52rkLh0jWJalD/9cxApC Subject: Re: [Xen-users] VGA passthrough radeon 4850 as primary card X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org Sounds like some wiki editing was needed.... So I added a note "Remember to install the graphics drivers in the DomU first, before expecting secondary passthrough to work." to these 2 pages: http://wiki.xen.org/wiki/Xen_VGA_Passthrough_Tested_Adapters http://wiki.xen.org/wiki/Xen_VGA_Passthrough#Using_Xen_VGA_graphics_passthru This page http://wiki.xen.org/wiki/SecondaryGPUPassthrough already said "After you have a defined stable DomU, enable the "pci" in the DomU config and install the necessary drivers. " but that's confusing, saying to add pci, then install drivers, so I added "Secondary passthrough may not work before installing the graphics driver." And on a side note, I have found people trying to get primary passthrough to work anyway, because Linux DomUs don't work very well with secondary passthrough. You will see the video from the monitor plugged into the GPU, but 3d things won't work in X. ps. I found win8 to work without installing drivers first. One time it even worked in the CD installer... to my surprise, duplicating the output to both VNC and the monitor. On 2013-02-28 10:14, povder wrote: > Thanks for your reply. I guess I'll give up the idea of passing > through Radeon VGA as primary card. I was trying to pass through it as > primary because I couldn't get it to work as secondary because I > wasn't using catalyst drivers - now it's working with catalyst drivers > :) > > I have another problem now, but it's probably not xen related. When I > run glxinfo I get: > > X Error of failed request: BadRequest (invalid request code or no > such operation) > Major opcode of failed request: 139 (ATIFGLEXTENSION) > Minor opcode of failed request: 66 () > Serial number of failed request: 13 > Current serial number in output stream: 13 > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xen.org > http://lists.xen.org/xen-users -- -------------------------------------------- Peter Maloney Brockmann Consult Max-Planck-Str. 2 21502 Geesthacht Germany Tel: +49 4152 889 300 Fax: +49 4152 889 333 E-mail: peter.maloney@brockmann-consult.de Internet: http://www.brockmann-consult.de -------------------------------------------- _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Thu Feb 28 10:04:37 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 28 Feb 2013 10:04: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 1UB0Kq-0004dm-OP; Thu, 28 Feb 2013 10:03:32 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UB0Kp-0004dg-6J for xen-users@lists.xen.org; Thu, 28 Feb 2013 10:03:31 +0000 Received: from [85.158.139.83:54587] by server-14.bemta-5.messagelabs.com id EC/CF-13158-27B2F215; Thu, 28 Feb 2013 10:03:30 +0000 X-Env-Sender: peter.maloney@brockmann-consult.de X-Msg-Ref: server-14.tower-182.messagelabs.com!1362045809!25056067!1 X-Originating-IP: [212.227.126.186] X-SpamReason: No, hits=1.8 required=7.0 tests=sa_preprocessor: QmFkIElQOiAyMTIuMjI3LjEyNi4xODYgPT4gNTk3ODQ=\n,sa_preprocessor: QmFkIElQOiAyMTIuMjI3LjEyNi4xODYgPT4gNTk3ODQ=\n,RATWARE_GECKO_BUILD X-StarScan-Received: X-StarScan-Version: 6.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 16223 invoked from network); 28 Feb 2013 10:03:29 -0000 Received: from moutng.kundenserver.de (HELO moutng.kundenserver.de) (212.227.126.186) by server-14.tower-182.messagelabs.com with RC4-SHA encrypted SMTP; 28 Feb 2013 10:03:29 -0000 Received: from [10.3.0.26] ([141.4.215.32]) by mrelayeu.kundenserver.de (node=mrbap0) with ESMTP (Nemesis) id 0MUTUB-1UJ0ew0O03-00RSiq; Thu, 28 Feb 2013 11:03:29 +0100 Message-ID: <512F2B70.4080306@brockmann-consult.de> Date: Thu, 28 Feb 2013 11:03:28 +0100 From: Peter Maloney User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/17.0 Thunderbird/17.0 MIME-Version: 1.0 To: xen-users@lists.xen.org References: In-Reply-To: X-Enigmail-Version: 1.5 X-Provags-ID: V02:K0:swLAU3E2s2PkQssQ1a79nPt2I1992wjprbkARVP3B4Z sASYxkzoAah4dhalLKK9ni21u9L51HNshvm6cF0M22+uY+ZW4k LZmWczZUgCgfUOZkwPJ/853lIA1cQqpACEj7jVpjwY5rcwLPp6 Qfr57mM1f4JP9HU9ogUDbA4ZrZktheMdj40wczZb8DX6Tnpvlh Vhdeo6ZHGrKXUh9SR2kUi+FO6oiI6vJgjTmdDNgHtrlYsksJ34 ERgFi34bV4Cys/BuWg+qFyNUNK5O3Mr55gkKtaGMBnML5wdRM5 FuPIWCQ1rbJ3fLFTG80haxY1OlqHLMNoahnohNCTHeS53kw17v ExeAQ8fMTj81dAmLmEo1a52rkLh0jWJalD/9cxApC Subject: Re: [Xen-users] VGA passthrough radeon 4850 as primary card X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org Sounds like some wiki editing was needed.... So I added a note "Remember to install the graphics drivers in the DomU first, before expecting secondary passthrough to work." to these 2 pages: http://wiki.xen.org/wiki/Xen_VGA_Passthrough_Tested_Adapters http://wiki.xen.org/wiki/Xen_VGA_Passthrough#Using_Xen_VGA_graphics_passthru This page http://wiki.xen.org/wiki/SecondaryGPUPassthrough already said "After you have a defined stable DomU, enable the "pci" in the DomU config and install the necessary drivers. " but that's confusing, saying to add pci, then install drivers, so I added "Secondary passthrough may not work before installing the graphics driver." And on a side note, I have found people trying to get primary passthrough to work anyway, because Linux DomUs don't work very well with secondary passthrough. You will see the video from the monitor plugged into the GPU, but 3d things won't work in X. ps. I found win8 to work without installing drivers first. One time it even worked in the CD installer... to my surprise, duplicating the output to both VNC and the monitor. On 2013-02-28 10:14, povder wrote: > Thanks for your reply. I guess I'll give up the idea of passing > through Radeon VGA as primary card. I was trying to pass through it as > primary because I couldn't get it to work as secondary because I > wasn't using catalyst drivers - now it's working with catalyst drivers > :) > > I have another problem now, but it's probably not xen related. When I > run glxinfo I get: > > X Error of failed request: BadRequest (invalid request code or no > such operation) > Major opcode of failed request: 139 (ATIFGLEXTENSION) > Minor opcode of failed request: 66 () > Serial number of failed request: 13 > Current serial number in output stream: 13 > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xen.org > http://lists.xen.org/xen-users -- -------------------------------------------- Peter Maloney Brockmann Consult Max-Planck-Str. 2 21502 Geesthacht Germany Tel: +49 4152 889 300 Fax: +49 4152 889 333 E-mail: peter.maloney@brockmann-consult.de Internet: http://www.brockmann-consult.de -------------------------------------------- _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Thu Feb 28 11:32:36 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 28 Feb 2013 11:32: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 1UB1i8-00033L-1x; Thu, 28 Feb 2013 11:31:40 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UB1i5-00032i-Rg for xen-users@lists.xen.org; Thu, 28 Feb 2013 11:31:38 +0000 Received: from [85.158.138.51:57153] by server-12.bemta-3.messagelabs.com id 58/F2-01357-4104F215; Thu, 28 Feb 2013 11:31:32 +0000 X-Env-Sender: agya.naila@gmail.com X-Msg-Ref: server-12.tower-174.messagelabs.com!1362050995!20311747!1 X-Originating-IP: [74.125.82.178] X-SpamReason: No, hits=1.4 required=7.0 tests=BODY_RANDOM_LONG, HTML_40_50, HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14, RCVD_BY_IP, spamassassin: X-StarScan-Received: X-StarScan-Version: 6.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 781 invoked from network); 28 Feb 2013 11:29:56 -0000 Received: from mail-we0-f178.google.com (HELO mail-we0-f178.google.com) (74.125.82.178) by server-12.tower-174.messagelabs.com with RC4-SHA encrypted SMTP; 28 Feb 2013 11:29:56 -0000 Received: by mail-we0-f178.google.com with SMTP id u7so123277wey.9 for ; Thu, 28 Feb 2013 03:29:55 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=IGp3hkfEocq+SJcB2NOHPzMcW02NksxuZ/s7LtUQRho=; b=Gibm9P9uajQLyLHXxhuB36RnKZo57vyUe4a9RH7ThSSvje4S9GzZkbQXdmais0H7g/ OKt6ThR4rNVp21efswbf+7yVLharenK3FTodqenSMzRrCccaRr86yaPLPqToQ1tk9YO/ zMB1rTHr95g0p8ZWPmeXvacidl/4YZAPIVOq1qagN9mgWBsB8bNIg8YkUWoxoguf67Nz O747HOp1YIR3m7cq8/ARrK9ULKwV6KvfnyYAGemq5SxyTRhxkmfaQeyp7XRs6ajHe1Rk HX0uqyjOE+lUzEkFIBZhgeP5O3y/46g9XQs093cjagsMrP4PICP2mFTRlM6nmKq5bvxj X5Gw== MIME-Version: 1.0 X-Received: by 10.194.63.240 with SMTP id j16mr10104688wjs.45.1362050995767; Thu, 28 Feb 2013 03:29:55 -0800 (PST) Received: by 10.216.236.13 with HTTP; Thu, 28 Feb 2013 03:29:55 -0800 (PST) In-Reply-To: References: Date: Thu, 28 Feb 2013 12:29:55 +0100 Message-ID: From: agya naila To: Andrew Eross Content-Type: multipart/mixed; boundary=047d7ba97b72c4ced304d6c73540 Cc: rshriram@cs.ubc.ca, "xen-users@lists.xen.org" Subject: Re: [Xen-users] Remus dom0 network buffering X-BeenThere: xen-users@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 --047d7ba97b72c4ced304d6c73540 Content-Type: multipart/alternative; boundary=047d7ba97b72c4cecf04d6c7353e --047d7ba97b72c4cecf04d6c7353e Content-Type: text/plain; charset=ISO-8859-1 Hi Andrew and Shiram, I am keep trying this setting using my machine that I mention earlier in this email thread. I have using remus with network buffering and no network buffering. with no network buffering #remus --no-net with network buffering #remus However, when I observed the jitter graph result of my data it seem there is no buffering impact on my traffic flow, enclosed both the graph result. I only observed RTP packet and observed the jitter. What I could understand the graph with network protection will doesn't have flow until x time when the buffer released, in this case default value 100ms. Y axis is time and X axis is jitter. Both of command above running without error except suspend event channel issue that we discussed earlier. Please suggest. Regards, Agya On Wed, Feb 20, 2013 at 1:13 PM, agya naila wrote: > Aha, sorry to mix it :), its clear now. > > Regards, > > Agya > > > On Wed, Feb 20, 2013 at 1:01 PM, Andrew Eross wrote: > >> Hi Agya, >> >> This patch doesn't fix the 'suspend event channel' issue, it just fixes >> the crash from the first e-mail in this thread. >> >> Please see this wiki page: >> http://wiki.xen.org/wiki/Remus_PV_domU_requirements >> >> That discusses the suspend event channel issue. >> >> Cheers, >> Andrew >> >> >> On Wed, Feb 20, 2013 at 8:57 AM, agya naila wrote: >> >>> Hello All, >>> >>> I am trying this patch on my machine Ubuntu 12.04 AMD64 both for Dom0 >>> and DomU with Xen 4.2.2-pre compiling from sources also DRBD 8.3.11 but >>> unfortunately it seem didn't work since I still got the message WARNING: >>> suspend event channel unavailable, falling back to slow xenstore >>> signalling. >>> >>> Regards, >>> >>> Agya >>> >>> On Tue, Feb 19, 2013 at 12:39 PM, Andrew Eross wrote: >>> >>>> Hi all, >>>> >>>> To close off on this, Shriram's patch worked great, thank you. >>>> >>>> So Ubuntu 12.10's standard generic kernel is now working fine as a dom0 >>>> for Remus with Xen 4.1.4 (with the patch from this thread). >>>> >>>> I wrote up my full install instructions here: >>>> >>>> http://wiki.xen.org/wiki/Install_Xen_4.1.4_with_Remus_and_DRBD_on_Ubuntu_12.10 >>>> >>>> I also took a shot at a number of updates to: >>>> http://wiki.xen.org/wiki/Remus >>>> >>>> And added these pages: >>>> http://wiki.xen.org/wiki/Remus_PV_domU_requirements >>>> http://wiki.xen.org/wiki/Remus_dom0_requirements >>>> >>>> Feedback very welcome, a lot of that information was a bit old, so I >>>> did my best. >>>> >>>> Cheers, >>>> Andrew >>>> >>>> >>>> On Mon, Feb 18, 2013 at 8:26 PM, Shriram Rajagopalan < >>>> rshriram@cs.ubc.ca> wrote: >>>> >>>>> ah darn. Yes, the 3.5 kernel has sch_plug in it. Unfortunately, the >>>>> technique to initialize the sch_plug module is bit >>>>> different with the module thats already mainline. You ll have to patch >>>>> the qdisc.py python module. I ll submit the >>>>> patch to xen devel soon. >>>>> Mean while, can you try the patch below and see if it works ? >>>>> >>>>> Secondly, you said you were writing a blog about how you set it up. >>>>> One of the remus users created a wiki >>>>> remusha.wikidot.com, which has a whole tutorial on how to setup remus >>>>> with Debian Squeeze. I have been under fire >>>>> lately for a host of remus issues. It would be great if you could post >>>>> your experiences on the wiki too. >>>>> (http://remusha.wikidot.com/system:join) >>>>> >>>>> thanks >>>>> shriram >>>>> >>>>> --- >>>>> diff -r 6435f1edf24e tools/python/xen/remus/qdisc.py >>>>> --- a/tools/python/xen/remus/qdisc.py Tue Jul 17 19:23:30 2012 -0400 >>>>> +++ b/tools/python/xen/remus/qdisc.py Mon Feb 18 18:25:22 2013 -0500 >>>>> @@ -1,6 +1,9 @@ >>>>> import socket, struct >>>>> >>>>> import netlink >>>>> +import platform >>>>> + >>>>> +kernelversion = platform.platform(terse=True).split("-")[1].split(".") >>>>> >>>>> qdisc_kinds = {} >>>>> >>>>> @@ -150,9 +153,14 @@ >>>>> TC_PLUG_RELEASE = 1 >>>>> >>>>> class PlugQdisc(Qdisc): >>>>> - fmt = 'I' >>>>> >>>>> def __init__(self, qdict=None): >>>>> + if int(kernelversion[0]) >= 3 and int(kernelversion[1]) >= 4: >>>>> + self.fmt = 'iI' >>>>> + self.limit = 10000 >>>>> + else: >>>>> + self.fmt = 'I' >>>>> + >>>>> if not qdict: >>>>> qdict = {'kind': 'plug', >>>>> 'handle': TC_H_ROOT} >>>>> @@ -161,7 +169,10 @@ >>>>> self.action = 0 >>>>> >>>>> def pack(self): >>>>> - return struct.pack(self.fmt, self.action) >>>>> + if int(kernelversion[0]) >= 3 and int(kernelversion[1]) >= 4: >>>>> + return struct.pack(self.fmt, self.action, self.limit) >>>>> + else: >>>>> + return struct.pack(self.fmt, self.action) >>>>> >>>>> def parse(self, args): >>>>> if not args: >>>>> >>>> >>>> >>>> _______________________________________________ >>>> Xen-users mailing list >>>> Xen-users@lists.xen.org >>>> http://lists.xen.org/xen-users >>>> >>> >>> >> > --047d7ba97b72c4cecf04d6c7353e Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Hi Andrew and Shiram,

I am keep trying this setting usin= g my machine that I mention earlier in this email thread.
I have = using remus with network buffering and no network buffering.

with no network buffering
#remus --no-net <vm> &= lt;backup target>

with network buffering
<= div>#remus <vm> <backup target>

However, when I observed= the jitter graph result of my data it seem there is no buffering impact on= my traffic flow, enclosed both the graph result. I only observed RTP packe= t and observed the jitter. What I could understand the graph with network p= rotection will doesn't have flow until x time when the buffer released,= in this case default value 100ms. Y axis is time and X axis is jitter.

Both of command above running without error except =A0s= uspend event channel issue that we discussed earlier. Please suggest.
=

Regards,

Agya

On Wed, Feb 20, 2013 at 1:13 PM, agya naila <agya.naila@gmail.com> wrote:
Aha, sorry to mix it :), its clear now.

Regards,

Agya


On Wed, Feb 20, 2013 at 1:01 PM, Andrew Eross <eross@locatrix.com> wrote:
Hi Agya,

This patch doesn= 't fix the 'suspend event channel' issue, it just fixes the cra= sh from the first e-mail in this thread.


That discusses the suspend event channel issue.

Cheers,
Andrew


On Wed, Feb 20, 2013 at 8:57 AM, agya naila <agy= a.naila@gmail.com> wrote:
Hello All,

I am trying th= is patch on my machine Ubuntu 12.04 AMD64 both for Dom0 and DomU with Xen 4= .2.2-pre compiling from sources also DRBD 8.3.11 but unfortunately it seem = didn't work since I still got the message=A0WARNING: susp= end event channel unavailable, falling back to slow xenstore signalling.=A0=

Regards= ,

A= gya

On Tue, Feb 19, 2013 at 12:39 PM, = Andrew Eross <eross@locatrix.com> wrote:
Hi all,

To close off on this, Shriram's patch worked= great, thank you.

So Ubuntu 12.10's standard = generic kernel is now working fine as a dom0 for Remus with Xen 4.1.4 (with= the patch from this thread).

I wrote up my full install instructions here:
http://wiki.xen.org/wiki/Install_Xen_4.1= .4_with_Remus_and_DRBD_on_Ubuntu_12.10

I also took a shot at a number of updates to:
http://wiki.x= en.org/wiki/Remus

And added these pages:
Feedback very welcome, a lot of that information was a bit old,= so I did my best.

Cheers,
Andrew

=

On Mon, Feb 18, 2013 at 8:26 PM, Shrira= m Rajagopalan <rshriram@cs.ubc.ca> wrote:
ah darn. Yes, the 3.5 kernel has sch_plug in= it. Unfortunately, the
technique to initialize the sch_plug module is bit
different with the module thats already mainline. You ll have to patch
the qdisc.py python module. I ll submit the
patch to xen devel soon.
Mean while, can you try the patch below and see if it works ?

Secondly, you said you were writing a blog about how you set it up.
One of the remus users created a wiki
remusha.wikidot.co= m, which has a whole tutorial on how to setup remus
with Debian Squeeze. I have been under fire
lately for a host of remus issues. It would be great if you could post
your experiences on the wiki too.
(http:= //remusha.wikidot.com/system:join)

thanks
shriram

---
diff -r 6435f1edf24e tools/python/xen/remus/qdisc.py
--- a/tools/python/xen/remus/qdisc.py =A0 Tue Jul 17 19:23:30 2012 -0400 +++ b/tools/python/xen/remus/qdisc.py =A0 Mon Feb 18 18:25:22 2013 -0500 @@ -1,6 +1,9 @@
=A0import socket, struct

=A0import netlink
+import platform
+
+kernelversion =3D platform.platform(terse=3DTrue).split("-")[1].= split(".")

=A0qdisc_kinds =3D {}

@@ -150,9 +153,14 @@
=A0TC_PLUG_RELEASE =3D 1

=A0class PlugQdisc(Qdisc):
- =A0 =A0fmt =3D 'I'

=A0 =A0 =A0def __init__(self, qdict=3DNone):
+ =A0 =A0 =A0 =A0if int(kernelversion[0]) >=3D 3 and int(kernelversion[1= ]) >=3D 4:
+ =A0 =A0 =A0 =A0 =A0 =A0self.fmt =3D 'iI'
+ =A0 =A0 =A0 =A0 =A0 =A0self.limit =3D 10000
+ =A0 =A0 =A0 =A0else:
+ =A0 =A0 =A0 =A0 =A0 =A0self.fmt =3D 'I'
+
=A0 =A0 =A0 =A0 =A0if not qdict:
=A0 =A0 =A0 =A0 =A0 =A0 =A0qdict =3D {'kind': 'plug',
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 'handle': TC_H_ROOT} @@ -161,7 +169,10 @@
=A0 =A0 =A0 =A0 =A0self.action =3D 0

=A0 =A0 =A0def pack(self):
- =A0 =A0 =A0 =A0return struct.pack(self.fmt, self.action)
+ =A0 =A0 =A0 =A0if int(kernelversion[0]) >=3D 3 and int(kernelversion[1= ]) >=3D 4:
+ =A0 =A0 =A0 =A0 =A0 =A0return struct.pack(self.fmt, self.action, self.lim= it)
+ =A0 =A0 =A0 =A0else:
+ =A0 =A0 =A0 =A0 =A0 =A0return struct.pack(self.fmt, self.action)

=A0 =A0 =A0def parse(self, args):
=A0 =A0 =A0 =A0 =A0if not args:


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




--047d7ba97b72c4cecf04d6c7353e-- --047d7ba97b72c4ced304d6c73540 Content-Type: image/png; name="net_protect.png" Content-Disposition: attachment; filename="net_protect.png" Content-Transfer-Encoding: base64 X-Attachment-Id: f_hdpttjuh0 iVBORw0KGgoAAAANSUhEUgAAAo8AAADICAYAAACJUguGAAAAA3NCSVQICAjb4U/gAAAAAXNSR0IA rs4c6QAAAARnQU1BAACxjwv8YQUAAAAJcEhZcwAADsQAAA7EAZUrDhsAACimSURBVHhe7Z09bytL 0piLr6NNX/8F8gSCgs1sUxtsKh4YUKTIgAz4BRWKyQWuAAV7AQE6B0qo8DAxlAoOlIjcdAMRsIHN CAUiYYcO/RPo7hkOORxx2NMzPd8PL4R7yOmurnqqe1isnu7urNVLeEEAAhCAAAQgAAEIQCABgX9J UIYiEIAABCAAAQhAAAIQ8AgQPNIRIAABCEAAAhCAAAQSEyB4TIyKghCAAAQgAAEIQAACBI/0AQhA AAIQgAAEIACBxAQIHhOjoiAEIAABCEAAAhCAAMEjfQACEIAABCAAAQjUicDsWjqdM3lahZVeydNZ R32u/65llqM9BI85wkU0BCAAAQhAAAIQcEdgEyC+igwjQldPVzI6nYregXE5XsjgOr/wkeDRnUeR BAEIQAACEIAABHIk0JWb97Wsf11EQ0d5e5nL8OLc+7z7/VL6k9fcso8Ejzm6GNEQgAAEIAABCEAg fwJL+Zj35aS3aan7TU5lIZ/etPZMrvUU9+xJzrwp7Y7opOTq6Wwzxd2Rs+38d3jq2y936EXwmL9H aQECEIAABCAAgQYS+Otf/7oNwPxnDQ//3d7eFmD9qXzrxjUzl9G9yLOa0l5PhzIZdORKnr0pbv1+ Pnr0s5Szx+3Ut772y09kfnkRPBbgTpqAAAQgAAEIQKB5BP7xj3/4AZjh7+HhoQDjg0zjoab6Mn6+ ES+2PL9Qz0v25fL7JtL03m/q9k7UdPcglIkkeCzAcTQBAQhAAAIQgAAEiibQk5N+qM3VpwoHj2Ui Y/Tr3si7CoSfVV4ymN4m81i0L2kPAhCAAAQgAAEI5E6gK2qNjIwe/YcUV28vMh9eSMyss1Gb7s27 WrHdl4X/0OSXF9PWRoQUgAAEIAABCEAAAlUgECxoGchE1HOMPfWM5dmT6BCve/Ms48XAyxj2Xi5l GffA4jEzvP0j/ec2e6NTubs5/BBlR83Tr6uAAx0gAAEIQAACEIBAnQjoIKuNYRSZxzr1UnSFAAQg AAEIQAACJRMgeCzZATQPAQhAAAIQgAAE6kSA4LFO3kJXCEAAAhCAAAQgUDIBgseSHUDzEIAABCAA AQhAoE4EWhI8+quTcjwjvCI+b4udFcGNGhCAAAQgAIEWEmhE8Di73i1V1z70zmvMECl68tQKqt1Z j37PsJVrW77I/hfYuDtK6TrzAeou7T0kK+rnInnRFgQgAAEIQAACPoFGBI/nv9TRQO+bY3ccebbf 7+/OenQks2pi+uPl9kil5Xghg072ADJPG/Pwc576IhsCEIAABCDQRAKVDB6/ZJ28TSvDgc1MrlVm MEguehkp740/bdsbzUWd+n0ge+jX87NtZ/J0eON038+XdzLuT2RwNIMZbNYZyAx0PKyHrV2BPYez g9oWZcNTsKHngcDP42awc9Oruzd36mzLibz6J6PHyLaz1xcdV2fT8OpJzkIHyV/P4n2483MwFI/J DqbwLXzexBGOTRCAAAQgAAHHBCoZPHbVGTv9yet2GlUd0Sh9Fcj5gY2OR/SZjUO5+HLuTldu3tfe kToynHpZtffQ7uiTwb2cLP0DzKdDtTP75hifw0x7cvM8VnrcxwaZs+uejE79dvSfl73zdno/rIed XTr4OSB/L4hWNoxEpl77v/aPIdKB42Ah4+W7xGwQv2+2x7QvJ73g46jsY/rEc49ntAlSe8qAbQZ0 KnL/Jt+P+HCndBI++jeEjc8djy7EQQACEIAABBpIoJLBo3S/qeO8g2BxJeqIRrm7G27PWEx7ZuNw ugukzi+GogR6R/rEvtQB4Xc6yLzyj/7Ze6mM2f2kL+PfdhGsl72bv8hbnFAbu1Zv8jIfyjR0vJCf HVxI+KjJ4TQSNGolP1U2zyZwVFVmjyOZ9y/le+gkoj3ZCfWxYjR7VV4eho4/OpdfSR8/SKiPtc8b OMgxCQIQgAAEIOCSQDWDR5VD82M7HYUt5eNUHe7dOxF5eVNBnA4m5zL8mnZ0yWUr6/zXVAWEI7k6 OMe9OVdyO+2qz5o89rKwa/mhTq2Mvnpy0p/Lx/K4qROVjvxa92ud+ai3PcNysBjL8ljgllofA6P+ iWyTnTYeTK2PTSOUhYA9gd9//92+EjUgAIHaEtg9WuY/wnZ7e1tbW5IqXtHgUURnBuc6WFTZqYWe S+1+l0vRWT0VTKqMXEGxo+KosmFTpcvoUd6+UFWZwc2UdTB1vV4fnyZObJcKltXke+SlbQ9PLR92 83Cqp9DlcMY0VCW8YMa44Ci1PgZG8w/18yDFK7U+KdqiCgQsCPz8+dOiNEUhAIG6E9h9//uPsD08 PNTdJKP+lQ0eVfToTQE/vi7k9JueS+3Kt1OVdXtUU51DlYk0mWaakjbVD18//81bPDPSC3GClw5m 1Wf3R1fdqMJRPZLatZEfXrCzerqXSWRqOc6M7s2zjGUkvQxbFu3JTqpP2F4TI81C5Wp3DNXiFu+Z 0c3rmA+T6mPjZ8pCAAIQgAAEIGAkUN3g0Zu6nstkcrrNMuqs3WSinpIzpB29hSlqqrl3YK9GI5GD BdSCEL14Zj+aUotzlnL5spv69VLXoeDnsB5J7dKLUNSU+WbVuJbde7k8PrX8RT+/fnS/ytQMDPp8 tVfbcIyRyup6KdKAoVrc8uxvuWT2YVY+6ShQCwIQgAAEINB2Ah2VYl23HQL2QwACEHBFQP/Q47bq iiZyIFBtAm0d7xXOPFa7w6AdBCAAAQhAAAIQaCMBgsc2eh2bIQABCEAAAhCAQEoCBI8pwVENAhCA AAQgAAEItJEAwWMbvY7NEIAABCAAAQhAICUBgseU4KgGAQhAIAkBNg1PQokyEIBAnQgQPNbJW+gK AQhUlkBckMim4ZV1GYpBAAIpCbBVT0pwVIMABCAQJhBs2RHduqOtW3nQOyDQBgJtHd9kHtvQu61s XMnTWUdcHUzjN52HTCujKAwBCEAAAhCAgCMCFQ4edcBxJsHpf7Nr1wGNI4KIqRSB1dOZdNxGvlb2 ld2+lbIUhgAEIAABCKQgUOHgcSkf81PxjrVWmavPRV9OeiksrGiVXIKM2bV0OtcyS2FzLvqk0KNx VTL4pHEsMAgCEIAABBpBoJrBo/eFO5CJ+m+gz4vu9GQ0n6sjkHeZSJ/+TK476rMnXV6XCwInf5rU /yz8uR+I+hlNXTd8PVwn3M6BKVetX+gMay/w2sqK6rjfT4KyV/Is61/nojOq+5kyvz3/PGpLXc9/ qWPRLuT1i83xfTWqz65kmE/EptWTnG3tjWSEj10LhHv+DWSa+B5icIixL6c3motszgPfnukdq1NM //H0C/efsI/i+lZM+yl80og7C0ZAAAIQaAmB6PfF7e1t8y3XZ1tX8jUdrqU/Xi+1csvxuh/8e0/Z 6Xooos7mHq6noc+nQ/XZcPfJctzfyVISx/1wneC9rIMqh8qHxK3XUd0i7R/i6cnUuu4JUiW1rHB9 bav012PfcEtdQy17cr6yCUrE6rNtM9BB49e6B4wV85Av9ln5/uj7ymvjNmV9OzzTPXt3sgMbY/ka 9dmn7emzL8yo737/0TZEbA/JO963NqyiPt5BP+qTSo5DlEpMQI9v/Qr+H1SMvk8skIIQgEDlCbR1 fFcz86hzbp8LkdNv4s1aLz9E5ZNiX8PpLzkPrqos0/2kL+Pftp9I9+ZOhvMXedPJvM1rV6cr3y9V mDWcikoEeq/ut1OR+YcsE/92mMjrkblind3rvVyKCqm8bOPe6/xChirDGtRfvb3IvH8p3z3D/Vcq Xbs38q7bm4rK3u5PZR/VZ9vmu9xsdPD4yUI+PX7n8uv9xveLZvX9UvoBq9mrsmQod0HFSFn5VBnL wULGy53spIiH0zh9TBKO6PuFr/pg9aksDR6X2PSFxafKAetryfpWrEZHfGKyguvNIcC+j83xJZZA oK0EKhk86qnc8PRjZzBRwdxIeqGp4uMO01Pc4WlHPQWe00sHBMuxLAZ+e9up0lBz3Zt3WV6+SE9P hX5ZzHEuFypdN/Gix5W8vcxleLcLzlJrHUzVDkSm61BwrQO+o/rEtTiXj000vTdN3xvtB/b9E4l7 NHUyipRNbZyuuNPHJOaovtHK3W8qdAwCZfVgxKvqOcGPGK9shr51xCcmG7jeHALs+9gcX2IJBNpK oJLB4/mvtajpQT37qOeBRE1FqhnspaxDGa/jDhuqgMmvu/uzz3Yl7hRBRkml+U5HvYPb3OiAzbPl 5P5LkHn+21j6k1eZrd7kZT6Ui0hyMrEeXsHNs4q9D7nz7N8PHANZx/Q53N5mwZJ6HrA3Ot3xVYGz ytvuXkcyttqfqriMrp78TF6mV8IFVCZ9ozp4mcddgDiYqL60ly1O07eS+SQTDipDAAIQgAAECiJQ yeDRX129I7D8mKvkT2ge9xic7ne57E/kPtjjJzPIruhZbD8zqF46e6QzoQdfPTnZi6S+FgqCtme5 2mUhA52v1JT18GI3BW+ru7fQ41UujgSNUZEH9VGFJoPdopTV071MIlPpgZzZYyibuJmC37FXQVMk W9y9eZaxqCzyNgObjG9SfTy9gmnmA/z29D3EVz8ioR5h2P3oCAXfSftWuP0UPrF1O+UhAAEIQAAC RRKoaPCoEQSZpf1A0gynKzfvS7l86e2vmE085f21hfNfUxluVvB2dEZPp0W30VN4Za5aFX66e3by mK5e0LbNaPnPXc7VivJhlrSjt7L3cKbRxG1fH/XM6PRSXjZT/16mMcj6qjamw2AVfEfuT8bqKcfg pZ4v9FKLAft7OXmOTsFr//g8gyn+o3w3oofTO/k4pE/EMP8ZTBWcBo8QHNX3ABVdXgYxfcfctw61 n9YnJp9xHQIQgAAEIFAGAY4nLIM6bVoQ0Fvg9OTjbr1d0GRR2brodjFR6BEJ/Qzu/clS3rcLgazF UqEFBJIeT9jW48xa0AUwsYUE2jqeK5x5bGEvxOTSCehHJPYXyNhmvks3AQUgAAEIQAACuRIgeMwV L8LrRuD811LGi/C0dU9eLsk61s2PddKXrXvq5C10hQAENAGmrekHEIAABBwQSDttnXbaSwedP378 cKA5IiAAgbQE0o7ftO1VpR7BY1U8gR4QgECtCRQdPLb1S6vWnQTlG0egreOQaevGdWUMggAEIAAB CEAAAvkRIHjMjy2SIQABCEAAAhCAQOMIEDw2zqUYBAEIQAACEIAABPIjQPCYH1skQwACECiMAKu2 C0NNQxBoPQGCx9Z3AQBAAAJVIpA2CPz582eVzEAXCLSGgF40E/67vb1tvO2stm68izEQAhAogoCr 1dZJV29GyyWtVwQL2oBAWwi0ddyReWxLD8dOCEAAAhCAAAQg4IAAwaMDiIiAAAQgAAEIQAACbSFA 8NgWT2MnBCAAAQhAAAIQcECA4NEBRERAAAIQgAAEIACBthAgeGyLp7ETAhBoFYG0q7ZbBQljIQCB VAQIHlNhoxIEIACBYgikDQLZuqcY/9AKBNpIgK162uh1bIYABJwTyGurnritQExb9bR1CxHnjkUg BI4QaOs4I/PIsIAABCAAAQhAAAIQSEyA4DExKgpCAAIQgAAEIAABCBA80gcgAAEIJCCQ9tnDBKIp AgEIQKBWBAgea+UulIUABMoiUPcFKAS/ZfUc2oVA8wiwYKZ5PsUiCEAgBwKmB+OrvmDGpH8OyBAJ gcYTaOu4IvPY+K6NgRCAAAQgAAEIQMAdAYJHdyyRBAEIQAACEIBAywjo7GP47/b2tvEEmLZuvIsx EAIQcEHAND3FtLULysiAQL0ImO4L9bImubZkHpOzoiQEIAABCEAAAhBoPQGCx9Z3AQBAAAJtJMDq 6zZ6HZsh4IYAwaMbjkiBAAQgUCsCdd96KC/YBNV5kUVukwgQPDbJm9gCAQhAoGIE6haMRYPquulf MfejTkMJsGCmoY7FLAhAwC0B04PxdVswY7LHFb2gHR2E/fjxw5XY3OREuRTFKTeDEJwrgbb2DzKP uXYrhEMAAhCoB4G8M2xMk9ejH6AlBJIQIHhMQokyEIAABBpOIGtwl3fw2XD8mAeBWhFg2rpW7kJZ CECgLAKm6am6T1ub7DNxj6sfx8Ukr6zrTFuXRb6e7WYdN/W0WoTMY109h94QgAAEakygrpnKuupd 466C6hUkQPBYQaegEgQgAIGyCeQdJNV1VXPW6f2y/Ur7EHBBgODRBUVkQAACEGgYgaKDpKLba5i7 MKduBFZPchY+E/vsSVZfbFjJ01lwbva1zLbXbT93D4fg0T1TJEIAAhCAQEYCeWc+M6pHdQg4IDCU 6Xota/33fiPdiMTV05WMTqfe9eV4IYNrP3y0/dyBol9EEDzmQRWZEIAABCCQiQCZyEz4qFx7Ait5 e5nL8OLcs6T7/VL6k1eVfbT9PB8QBI/5cEUqBCAAgUYRIBN42J1waVQ3L9iYiQy8qeszefoyZ72U j3lfTnoblbrf5FQW8rmy/VzXn8m1bmO2myrXSczV05lq258WP9sqEJ4S78gm2UnmseCeQXMQgAAE GkGATOBhN8KlEd07kxFBAHbs/7e3t/ttdG/kfTNlvRyLjHrhZxqDoqfyLTqX7V2y/VzXmcvoXuRZ tzkdymTQkSt59qfM1fv56NF/pnL2uJ0q19d++YlPgsdMPYTKEIAABCAAAQhAIETAC8AMfw8PD7HM ujd3MvSyitEihz7TZWw/13X6Mn7ePFd5fqHa68vl901k6r3fyOydqOnxQSgTSfBIZ4cABCAAgZoS YHq4po5D7ZQEenLSD1VdfarwTmccbT+3bH6TEX1WeUmdSWXa2pJfmuLc3NJQow4EIAABMwGmh82M mlCijd+js+uBTPqX4icCN88nrrqi1sjI6HGzwvrtRebDCzlXa7LtPk/XK7o372qFd18WX9OhnkAW zKTjerAWNzc7mG28SdgRojQEIFA3AtzXsnmsHd+j+4tSBouxLA9s1dO9eZbxYuBlAHsvl7LcPIBo +7mVR2bX20U0vdGp3N0cfOhSONvaiurhwvpm8ePHDw+4fu6BVzIC8ErGiVLVIGDqr00729r2jGfb s61N8k3X8+oVpnZtr+elZ1PlmsZZ1eyum76u+JF5dECyHb+UHIBCBAQgAAFHBNqa4Wur3Y66DWIc EahU8Ni0QdE0exz1uS9iopzglhdp5EKgOQTa+qO9rXY3p+c2w5JKBY9VHxS2QU3V7alKF45ygltV PIMeEIAABIohEPf9avu9G2ibtl4x1ta/lUo981j1ZweyPtOTd3cJnr3Mux1X8pM+I+aqPeRAIAsB 0/0paX+2fWbOdN8JbMoq17Z+lKVJT1v5tuWz+DZc17ZdU3nX92VTP3TFoWg5ScdPUr2K4lRUO0nt LqpcpTKPRRldVjt5/xIiY1eWZ2kXAhAom0De99e09uV9X66q3Wl5Ua8eBCodPDZtUOR9E6lHl7PX smn9wJ5As2rgz2b5syrWtPX+2la7q9Lv2qpHpYNHBkVbu+W+3fSDZvUD/Nksf2INBIokkPbHJwsz 3Xqp0sFj1NTA+Wk7j1t0SIMABCAAgaoSqOr3RFX1KsqPWe1P++OThZluPVyr4DFwftrO4xZddmlZ B5FJg7zlm9qv63W41dVz6A2BHYGqfk/krVfV7l9RfVzbXzV72zIGaxU8Ns0prgdRlE8gv2mDK297 8vaL636cNw9X+rreisOVXsiBQJMIVO3+lbc+ruRnuY/qFdfhv9vb2yZ1qYO2VHqrnrgtEMpaGp/3 VhRZe1vVeJnsSbo1g2krDFM7ttej7bneasNWH1P5ssaDSa/o9aT+tpVbVHkT56T2mfqz6Xpgr6lc 3tfj/JvW70XrG9dv8tbD1I9M/dlWP5O8vK+b9I32Z1N503VX4yPpfT+rP/Pmn5f8RmQes/xiyAss cptDwNUv2+YQwRII1I9AVb8nqqpX/TzsVmPu+8d5NiJ4bIqTuYm4HfxIgwAEIBAQqOr3RN568b3C GMiDQCOCR1dgyh5ked9EopzKtrcpfnNlhys5dfdr3fV35UfkQMAFgaK/V1zojIzqE2jEM4+unlEz PbuQ9zOPpvZN3cn2mces7Zn0MV3P6xkxU7um66ZnapI+C2Nqx9V1k76u2skqJ62/s7brqr5pvKS1 z+Q/030nsM9WTtbyUa4mPbO257p+XL9w3Y6tPFN/tZVn6rem9rJeN+kb7b+m8qbreY2HuPt+2Xyz +idt/UZmHvmlZdcdXGd6XMuzsyb/0nXrX033R/4epwUIFEcg7/Gat/ziSBXbUt3u+3nTaWTmMe0v AVO9on9Z22a40mYeTXbbdsKk8vLK1NhyM2VQkv7SteXkqrxJv6T+cKWPKaNjq29Wf7qyy8Qxr/5s uu/klWkx+ck0blxnlEz62F439dOyuCbtZ670czU+0vJ03U9ccTH1p7h28uZZFfmNzDxG4db1l1bZ v3TglmyY1pVTMuvKL1X2OCifABpAAAIQqBaBVmQeTb/kkv6CMGUATL9Usl43dR3Xmcek3AK9ggxR 0npFZ2pM/Fz9Yk3ajqtytv3KVbu2clz527ZdV+VN/dqVfSZ/uuqnpnZM16Ncy74/mvQ1+a8qXE16 2tppKu9qfJB5zJtkteS3IvNYLeTptSkrw5W03apmiJLqn94z9apZdx51179evQVtm06A8dR0D+dj Xyszj2lXTVXtl7Xpl39cJiT6C9vWLtMvTNMvZ1P7pl/KWa+bhlJW+UU/o5dVXxMPV9fzysy50s8k x9Sv87LPND7LypiZ7j9lj3PTuDDdx8rimrSf5aWfaRzYXk/qB1fjJy8uScehLZ+6lm9l8Ji2E5jq mQaJ6+ummzfBo0/IdDNOyjHtTSnvm0PWfpW3fnkHEUXrbwo6svrDVD9tPzTJtb1uGjd5+91W36T3 gaxyXdc3cc67vazjy6Sf635S1PiIaycrr7rUZ9q6Lp6qkJ5Mc1TIGQ5Uqbs/666/AxciAgLOCDCe nKFstCAyjyH3mn6Zknk8nskzZTrjfkGbfpm6vm6aVi66vax3GNf6ZtWnKpk513YkvT+49ofpvlNU piWp/VUZ5yY/mPppWVxtOZvszHo96zgytU/mMSvhcuoTPBI8xk7rxgWDpi8z083P9c3CdHMyXY/7 ssvry8P1UDfZZ3vdtX5F+ztv/U1Bhy1v2/J59cu0esTpU7Tfs+pfFa6m+6etnVnLZx1PpvZd95Oi /Gjq91m5Vb0+09ZV9xD6QaBgAnWftqq7/gW7m+YgcJQA48ncQXSAHP67vb01V6p5CTKPZB7JPEYG semXctbrpmlz23tKVn1M9W31KTszZ8rcpLXHJDdppt7E23S9qMxKUj1MGZiiuJj0NfmvKlxNetra 6bq87fgxtU/m0ZZoNcqTeayGH9CiRQSquh9mi1yAqRCAAAQgkIEAwWMGeFSFgAsCVZ8Wqrp+Jh/U XX+TfVyHQJEEGE9F0q5uW0xbh3xjO13gOt1uSu/b6hc3XWTS23Q9Tg9Te9FhUJXprDi9yprGsr1d 2PabrOVt9bPtT1n1M9VP+9hA0vFnaj/r9bL6ZVL7qzrOTfpXhatJz6z9x3V90/3A1J7r+0NRfoxr x8SjKdfJPDbFk9gBAQgkIsBjA4kwUQgCiQiQiUyEqXGFCB4b51IMqjuBqt+Mq65f3f2P/hCoEwF+ jNXJW+50JXh0xxJJEHBCoOo346rr58QJCIEABCAAgVgCBI90DghUnEDVM31V16/i7kU9CEAAArUj QPBYO5ehcNsIVD3TV3X92tZfsBcCEIBA3gQIHvMmjHwIQAACEIAABCDQIAIEjw1yJqZAAAIQgAAE IACBvAkQPOZNGPkQgAAEIAABCECgQQQIHhvkTEyBAAQgAAEIQAACeRMgeMybMPIhAAEIQAACEIBA gwgQPDbImZgCAQhAAAIQgECxBPQRjOG/29vbYhUooTWCxxKg0yQEIAABCEAAAs0gsF6vJfz38PDQ DMOOWEHw2HgXYyAEIAABCEAAAhBwR4Dg0R1LJEEAAhCAAAQgAIHGEyB4bLyLMRACEIAABCAAAQi4 I0Dw6I4lkiAAAQhAAAIQgEDjCRA8Nt7FGAgBCEAAAhCAAATcESB4dMcSSRCAAAQgAAEIQKDxBAge G+9iDIQABCAAAQhAAALuCBA8umOJJAhAAAIQgAAEINB4AgSPjXcxBkIAAhCAAAQgAAF3BAge3bFE EgQgAAEIQAACEGg8AYLHxrsYAyEAAQhAAAIQgIA7AgSP7lgiCQIQgAAEIAABCDSeAMFj412MgRCA AAQgAAEIQMAdAYJHdyyRBAEIQAACEIAABBpPgOCx8S7GQAhAAAIQgAAE8iLQ6XQk/Hd7e5tXU5WR S/BYGVegCAQgAAEIQAACdSOwXq8l/Pfw8FA3E6z1JXi0RkYFCEAAAhCAAAQg0F4CBI/t9T2WQwAC EIAABCAAAWsCBI/WyKgAAQhAAAIQgAAE2kuA4LG9vsdyCEAAAhCAAAQgYE2A4NEaGRUgAAEIQAAC EIBAewkQPLbX91gOAQhAAAIQgAAErAkQPFojowIEIAABCEAAAhBoLwGCx/b6HsshAAEIQAACEICA NQGCR2tkVIAABCAAAQhAAALtJUDw2F7fYzkEIAABCEAAAo0lsJKns+DoxGuZObQzU/D4+++/76kS fe9QT0RBAAIQgAAEIAABCCQksHq6ktHp1Ds6cTleyODaXfhoFTxGg8OfP3/umRB9n9A+ikEAAhCA AAQgAAEIOCOwkreXuQwvzj2J3e+X0p+8Oss+/ru/qVdSXf/5z3/KX/7yl23xP/3pT0ffJ5UblDPJ C64nLZdUbly5qP7RdqP1XOtlkmfSL46XSW/TdVsOcf0gL3+auMXpn7S/2Mp3XT6p38uyp+r+Nvnf pL/pumt/m8ZbVfxs0jNvLrbyTX4si6upf9raWXR52/uT7feNyZ6i/Ba088cff4hFGGUbFmUo/z/l v//b/5GTv/03+Y//qsT86/+T//XH/5B/+S/6/UyuO/9V/rf3b91E+L2e6v738p/+7Q/Rtv3f//A3 +c+9r2p0VDpznUE7qkIAAhCAAAQgAIFWEjg/P5e///3vRtv1zO3Dw4OxnLsCOiB8lYv1L/Fzj/r9 vZws3+WmG/535NryWjqvF7L+5deKeyWetv7x44d0OsGDl/wfFvQB+gB9gD5AH6APtLsP/PnPf/ae KTT9FRs4BiHfQj5XluFo70RNbw/k7Ol4xdIyj3rAuUx6Is+yg0SKww9+NgToLza0Dkz5cP/LBJD+ lwmflwji+zc9Q9f80mtyrKaefr4SedaZRlVu9SRnvQ+58zKRRzKPuqxX/Ex6I/XM5HQth5KQiTOP +RiHVAhAAAIQgAAEIAABtwS6otbIyOjRX2G9enuR+fBiM4Xdk5P+XD6WmxZnrzKJNN69eVcrtPuy iEldEjy69RbSIAABCEAAAhCAQOkEujfPMl4MvExz7+VSltsUYldu7oYyGWweOXgVGQbaztQzj5tH FHujU7nz0pZfX0xbx7jXdVoaednGEfzgZ0OA/mJD68AXA9OamQDS/zLha920ejZa5dQuLfOoF+C4 fLVNnkt2Wlbb+Lm2F39kI4A/qsUPf+APGwKu+0sz5ennDPcXF5kWpcT7QMs6E8OaFhsXWpctLfNo rSkV9gi4/mUL3mwE8Ec2fq5r4w/XRLPJwx/Z+LmujT9cE00iL7pIJUmduDIuZaXTo7TMYzp1qQUB CEAAAhCAAAQgUCYBgscy6dM2BCAAAQhAAAL1J7Baie2Witro2XVHdkdOR6aj9fY6wUX9782099nT Z+m8CB5LdwEKQAACEIAABCBQWwI6sHtcyuF1yWGr5jLq7Z571HHh+YVa9fzqb6cjasucRV/k5c0P Q/X2OnKizwZUQWVvJKdqz0W9P+ezvHzZWqdodgSPRROnPQhAAAIQgAAEmkHA23x7JHN1Ksvh04au VegXvPoyXu5Oo/F2ztEnuiw+vazl7HUhl3dqc8aXN/V+JTp2vPyuQtLVpwoqx/Lb5sTA7s3dbmud kigSPJYEnmYhAAEIQAACEKg5ge6NvC/HMhwvY44oDM6WjrGz+10uVSbxbTWT18WlfD/X7z9kuXpT n6r35nRmKQAJHkvBTqMQgAAEIAABCDSCgAogf/u2TPXMo6jJbn0SzMvVvSwuv6t3+v1CXh8/dNrR nwrvfpPT+Ug2h8WoowPvmbZuRMfBCAhAAAIQgAAEWkuge36e4JnHw3i6Onqcb6aodayo3i8magp7 m3Y8l1/T3YkwVyojuT0RpiTi7PNYEviszbJPV1aCbuvjD7c8s0rDH1kJuq2PP9zyzCoNf2QlmLW+ XlU92MseDtVimO3pgVnFF1CfaesCINMEBCAAAQhAAAIQ2BEILZ7xsorhhTXV50TwWH0foSEEIAAB CEAAAk0lcH6hpqEX8plmo8iSmBA8lgQ+a7Ouz/7Mqk/b6+OPavUA/IE/qkWgWtowPnL2h+2G4Wp/ x0k/tLI6tCF4p6Mzkit5OgtvJq70n11L5+wp5SKd7PbzzGN2hkiAAAQgAAEIQAACak9GvWH4N3k/ +gBj5JnH4VTW2/KRc6tVkHj2+Zu8f3uUzuvFtpw+meb1orznJMk80tkhAAEIQAACEIBAVgJpNgxX e0T2J6+7jcT1huBq6fX2JJrBROYfS30UjQy35fSekLtNw7OqnaY+wWMaatSBAAQgAAEIQAACYQJp NgxXdZ7HC7l/Cj/wOJSpOoZQH0Xo/XlZyXP5bVNO7/Po7wlZ3ovgsTz2tAwBCEAAAhCAQJMIpNgw XB83eDq6Ei9+1BuCq0189oNJH5C3H+TLozy+nMrdTZmhowjBYyU6rf8wrH8uZsxy/b0HaFW57YOy CepWwsaaKqEfSu6c+YPa+MIXRkRpC5j8wPhISzZDvXB/jzzMf1Aq4yMD7CNVE/iB8ZEP+hip9huG 66yiyOhKL4BRG4KrqWw1b707K/t6czq2d5ThRCanF6pUuS+Cx3L5e62vnq5kdKoemFXp6aVKSw+C jvJFt1Aq+/3GS1knr1sBQ2ulwuaG/CqJd/LHF3k42MYPjI88PBArc/Ym8ryZVkuwTx3jIyfvJPYD 4yMnD6QQqwLE9buEk4fdm3dZb77XRU9/f5m21s105eY9mMZO0azDKgSPDmGmE7WSt5e5DC/83xE6 Lb338OxRoVnqptO2PbWCQXqR0GR8kRCUZTFbP4TF4xNL2HbFz292X37GferwhR1ci9JWfmB8WJCl 6BECBI+ld4+lfMz7ctLbKOI97xC3WehEBt7UdjCNeqxugqmM0m1vkgL4onxvMj5K84FeIRrep+6L IoyPQnxz1A+Mj0J80JJGCB4r4ehT+WZ69jWUxvYfhwiejYypO3vcToXr6fA6nZlZCZekUgJfpMLm ohLjwwXFlDLUD9WrkZze+Y/SxL8YHykBJ6x2xA+Mj4QMKZaUAMFjUlK5lrM7lkivzNodZRRTt3ei pr8HcpZspUeu1rVHOL6ogq8ZH8V6YXbd836omn+gMj7y9ExSPzA+8vRCe2QTPJbu656c9ENKeBuE JshEelWO1N380nyWK2/FVuwanNLtb4oC+KJ6nsQneftk9XQmAwmfjhHXIr7I0xfJ/RDWAp/k6ZOm yyZ4LN3DXdFbN40e/aX4q7cXmQ+DZfj6mKKv28TMrgebczCP1fUN0yu4luO+LOp04nrpPjEpcMgv +MJEzf11xod7phYS1fZJvZdLWX5JOTI+LChmL2rlB30kMt8f2aEjQW8Pw6t0Asu1iu/WqjuupT9e L7f6TNdD6a/Hy9D1L2Vi6k6Hvjzvb7hWu9XzsiIQYb7HPfBLVCC+sEKcqHASPzA+EqF0WuiAX9QY GXo3GsaHU9RHhSXxA+OjOH+0p6WONpUYGgIQgAAEIAABCEAAAkkIMG2dhBJlIAABCEAAAhCAAAQ8 AgSPdAQIQAACEIAABCAAgcQE/j/xBF7k79kK8wAAAABJRU5ErkJggg== --047d7ba97b72c4ced304d6c73540 Content-Type: image/png; name="no_net_protect.png" Content-Disposition: attachment; filename="no_net_protect.png" Content-Transfer-Encoding: base64 X-Attachment-Id: f_hdpttjy31 iVBORw0KGgoAAAANSUhEUgAAAoYAAADICAYAAAB1RyBMAAAAA3NCSVQICAjb4U/gAAAAAXNSR0IA rs4c6QAAAARnQU1BAACxjwv8YQUAAAAJcEhZcwAADsQAAA7EAZUrDhsAACnASURBVHhe7Z07byNL lqCPZq12Z/8CWYYgo73ZpdpoVywsIEvWABpgB5QpOhe4AmT0BQSoCuVQZtFZyBXGkCOp3TZEYNcW ZBSJXXPN/QnciHyQyWQmIyMz8v3lhXBLyogTJ74TkXnyxOtorS7hggAEIAABCEAAAhDoPYF/6j0B AEAAAhCAAAQgAAEIeARwDGkIEIAABCAAAQhAAAI4hrQBCEAAAhCAAAQgAIEtASKGtAYIQAACEIAA BCAAASKGtAEIQAACEIAABCAAASKGtAEIQAACEIAABCDQPAJvV3J0dCoPq6hqK3k4PVJ/1z9X8lai 1gwllwgX0RCAAAQgAAEIQCAbgcD5exaZxDKsHi5levIqeofB5exDxlfluYY4htmsRSoIQAACEIAA BCBQIoGBXL+vZf3zPO4WysvTQibnZ97fB18vZDR/Li1qiGNYookRDQEIQAACEIAABIoRWMrnYiTH w0DK4IucyIf88oaa3+RKDzu/PcipN8x8JDqYuHo4DYadj+R0MyYdHY720yVdOIbFrEVuCECgZwTe rtTDt8RhnJ7hpLoQaCyBv/71rxvnyp/bl/xzc3NTQR1O5MsgrZiFTO9EHtUw8/p1IvPxkVzKozfs rH9fTH/40cW3H5vhaH3vpx+A3LtwDCswJ0VAoHkE/C9H/Btby7zJ81zN//GGdFwwjHzBnz4oifpK +putnqSHAASKEvjHP/7hO1eGn/v7+6JFZcgfRgiTko5k9ngtnt94dq7mJ47k4mvgRXq/B3mHx2oI ehyJIOIYZgBPki4T8CI96otvG1b3a+uF3HN6SK5kFtGhbJuFddx+LRdfEeeyvkmyPJ03jpZDQm/P Mh/N5LeUL23rkvQX/GIir/rF8x482JP+Zi1YBQfKYpBDF7JAAAJFCAzleBTJv/qlXL1DEcSUsgbX 8q6eNY8qnhgOOSelJGJYxFbkbR2B0Wi0Das70r4MmY5UcyZmNFtuvpq9FXElb5dQVPGznxFHq6iw SP43FS4cXXz1v8xdXaNjCacObUQm/c2yvLIYWKpBcghAoDCBgaj1JjL94U8KXL08yWJyLnm/TwfX 72pl80g+/EmKexeOYWGDIaBVBC5uZTaaG5b6707QNe4ZVUimX9ZwuhA1MWQT0dyLgnn7WkUjdXrC cXQo+JDOweTkBy0jZQ+sxH2zki07uL5VQxNzefYnrfgTn/dkp+mTXF+/JAP31XZytf+1my5rfx7g IdnhkLDP1GcU30PMr+vzPDJEs8GTli9hqFlzDiKZno3Halx6MZWhLlNFrZP+ZmaTbINdBhnq6LWB 2ByqnJH0Vj0TUBYCjSEQPqfG6gmr5g0OtyMfg+tHmX3474jh04Us0yYIHqpLpI8Ppydye53yiavG zrkg0AsCag7uWkW+1uvlbD2S0Vr/U1/qy2ktEzWY5/+2Vh9Skd+D+zJZhymisLLJXOv5v/syRzNV WpIOnlJKx22Zy9lkrYKd662a0fsmnV/Xak+stZoZF6mDn8eT9zpR97Y84o1hU8fwxg6/dNlbpvsM d5n7gg8z8svx7OenXk8CfmZZJj7B/QiDuC6BgmuJ2GzTVuJtacM5wjhkp1lHZcR/90HEysnGZte+ 8TymOmq+aX2iF48HKgmBPQLKx+olFSKGjflSQJHKCKh5FrcT9TV2GU72j5S8epEnPecr8jXmR8gO TfxV+Q/KfJA7FWmaRSameTIXT/KSHMlX8vR2BGFUbqX2sBK5vVVaBKH/naGEjDpPXn/uDz38UlG4 8YfMlu+S9vEYt8vbj6ksRhcSzm3W93dkZ9RnR66KBh5kpOf2KStsv3DP5Gc4J8/UcDLqM3ndMjg7 V27ox69gMUgQzbxLHkaO5svUVkz6xu+b2ATpE+0bk5Vax9icpcGXk1j9bZUmPQQg0FYCOIZttRx6 FyJw9vNVOWZTudw9c0hk+akC+PFLT/xdyOfycJGpMr1swbDAZqhODxUcus7E902056j2sDpR80nU ijJ5elHOinYUt5udFtF5PlVOXgaSi+lwM8w4/pjJ8pBTlpuhgVHeeXe59Yl/MCQNIyfBM7eVDMhj SWzbj2UJO/uiqUFzvfT65IvbuZSWKpEcAhCohwCOYT3cKbV2AiriFOzv9BLVRS/n39Mttrloqu4p Mr30wcrTnW0PDkfpdNRqoR1BFS370DubDr7Khegoo9ZnIsEm+CIFdFZDyWoSsprUnBQ9jdQzuvhk s3o2jUNufQyMFp/KRc5x5dZnW5Yfob3NGFWNbESbQ93kLPbtx6poL2K4dT7H892ouZUsEkMAAq0m gGPYavOhfCECZ795C1GmeuFHeGnnK7Y4ZfVwp7Yo2R06TfcN02XexaOTcSE7Q5fqpt5/Sg03/3hW GxN4O5sO5MuJikb9UMOq0RVpBXX2JjWLWgDhaqFBVn2i9Q3ypDLy9uKay/a+WnAR3Y4mzi7KNqs+ qUaNRWhj6ebj7UKV3bai7aXWFPmrdPS+SGrY/nCcOFEFE5tCnSDIrKOqE/8cVv8nYdqBi3KQAQEI NJ4AjmHjTYSC5RFQ51I+zmIRQn1WpRpmDlYIb1aAZZ3Pppy3ZJlLuXjaDsd6qz8jjo139mWwOnW7 z6IeTl7IfH6yiQ7qKOJ8rmbbbcKFmo4DnYM6x/d4zMferM9+fXWeQ4xUNNYLbYYM7+Q42NA1md2O Z1jMpsEcxR3kG/Fq7uiriuPq1YN6taBa6fcaaSve9IKwLQ0/5VZFqe0vExt7iXs5zn7Kq/grHjc/ ZewD6UBVREAAAuUSONJLbsotAukQgAAE2ktAbyEz/LxVB9vn3TWs+XX36qi3wIg4tXq7m7vjpbxn XZXU/GqiIQSsCOiPpD66SEQMrZoJiSEAgX4RODyM3BUWy081nWJnsclKfn10pXbUAwIQsCFAxNCG FmkhAAEIdJKA3lh3qI7n21ZOLzgiWthJY1OpjAT6GjHEMczYQEgGAQhAAAIQgEB/CPTVMWQouT9t nJpCAAIQgAAEIACBgwRwDGkgEIAABCAAAQhAIIFA/Pzwm5ubznNiKLnzJqaCEIAABCAAAQjYEmAo 2ZYY6SEAAQhAAAIQgAAEOkWAoeROmZPKQAAC5RPQK3iPxNVBMb6+ZcgsnwQlQAAC3SOAY9g9m1Kj VAL65bs9vkxv4Ov25Q76QwT0JspHAK+9kdRth7rLr90AKACBhhPAMWy4gVDPJYGlfC5OxDt2WEVo fn2M5HjoUj6yXBIoxYF4u1JHvl1JcHqxlbql6GOlQUcTF7BJR4lQLQjUSgDHsFb8FF4ZAe/lM5a5 +m/snQerN/NdqKN3dQTxTa6O1P8fdBp9L3Qc/OG97aq0qEMRRh913jCNvh/Ns41OJg4Vap0i59F6 jsdGVjSvLaVwWDKqW1zeobollVdEpp93qHdPDs4NPnQmc8jhUh69Y+h0ZHc30ujL82VY2kGdCbxe n8vzjp0P843rs019gO/qQU4j5w7vBEoP3QuFe+01tFnCMPNO20likNR+DtghVaeUvuHpF+0bURul ta2U8nPYxLZHkB4CELAgoM9K5oJALwi8TtYymq2XurLL2XoU/nv9up6IqDPDJ+pf2+t1ov422f5l ORtt8ysps1E0T/i7rMMsSekj4tbruD6x8vPbJNRltJ55ldVFResS3I/X7WD5JpnxMjTiKK/g9x0A uzX00ms7xNNoTlHdtO0krJutHSJlenL27R6mSNVnY/stXz9t2H5Ue9q0rTgHv62pU0WCYsK0fj28 qnv13cpWErb3QuWibceoTwLn3YZo1He3b+g6xOoekXe43xjagcEm+fsEOSFgT0A/j/p4ETG0cKJJ 2m4CK334a3ge7PJTIqd/eRWbvP6Us7CKKoJyNx/J7LfNX2RwfSuTxZO86EBVcG3zDOTrhXIzJq+i glzeNfhyIrL4lGVmbHN5zjPGmSJ/8vou196wucjZuXJHPn6p+Jq6Vi/ytJjIa6io1lXXTT7kV6Ru SWLTZWbjlYZCR+WGTxei3CUvSrhznZ0r3bZsVi9PshhdyNegbru2s7DD4FredXmvoqLIu8PLB/XZ 2H7Ld5ffmfx8v5ZQvcHXCxmF7eDtWdVkIrehYVSLi6aVXyrSOP6Q2XIrO2vzidomqz2D1pGu7147 1+3nl2op4ZSMoJ1v2laxdqAaYqpNsnIgHQQgUIwAjmExfuRuCQE9HBkdyjwaz5XTNpVhZCh3vyp6 qDk6XKaHoku69AtxOZOPsV9e0lDr7lCz78gk/c2oYYJTLDKU49FCPpUXm0umV2h+XoPrd1lePMlQ D0/uLVA5E+3Xzj2veSUvTwuZ3G4dL2N9071Rf7h3LPK6jnwUeI7yIX3SBPr89LXDcDjd/QgZHSva ydd8Gkubu3K+PUJ9TGIO6hvPPPii3MLtR8Tbs+oV4QdXwXagwKXaxFQH7kMAAm4I4Bi64YiUhhM4 +7kWNcSlRyn12ICooT81qryUdSSys18FFVXTEaWdH/tITmY0YbREhbBOpsO9FdPaWdnq4jsySX8z ljc8FhXbjF16YY6/GCeXTE9aMV5hucvjuz3n+Oy3mYzmz/IWRDvPY0FFY513EgRzA4efcuvZdtcp DJMe0ie5vGAxk5p/N5yebNuOcvh3eB+IIuv2qZLL9PLBj+4WujIurjLpG9fBixhuPwLG893oc752 kM0mhXCQGQIQyEQAxzATJhK1n4BehbytxfJzoYIckbHIeAUHX+ViNJc7b4GDi2sgemTZj3qpS0dG dNQy8dLROxdlpsgI6jaOROZWD3cyjw3PWmmQlVc45HhAeOiQPcrlNnoYyr9Uw8iT8+2Qv5WSKrG3 aOJZzg84hHtNIXDId/RRiebj7QKPQ/zefkSigMGw+LZdKYcoFrUeXD/KTFQ0e2OfbG0nqz5e/Q7Y YUffJL464qymTMQ/UrykedpBDpvYmp30EIBAdgI4htlZkbL1BMIIyq6TmFytgVy/L+Xiabi7+vLg 0PNhQGc/X2USrMo90tEqHcIMr51VnmrF9Ml2rqJ77LpuEV3UcKo3v+9g9NSkhZmXP9dOOTwpQ+WJ DtlmvqE/d3ChVpJPioQLvRWwyRFCYw21g7jRR80/fb2Qp2CqgRchDPmpMl4n4er3I7k7nqlYanip OYVeSDBsV3dy/BgfFt/aJ5xScLDtBKInr7fymaRPrGJ7djiobwIVnV7GKf0iRzsoYBOTzbgPAQjY E+CsZHtm5IAABCDQIAJ6G5ihfN6uNwufylRuszAn8iGh5/DeHS/lfbOopkwNkA2BaghwVnI1nCkF AhCAAARaTEBPw9hdbJIlAt/iCqM6BHpGgKHknhmc6kIAAhAoQuDs51JmH9Gh5KE8XRAtLMKUvM0l EN/I/ebmprnKOtKMoWRHIBEDAQhAAAIQgEB3CDCU3B1bUhMIQAACEIAABCAAgRwEGErOAY0sEIAA BCAAAQhAoIsEcAwdW/X33393LBFxEIAABCAAAQhAoBoCzDF0zLmvcxIcY0QcBCAAAQhAoFYCfX2f EzGstdlROAQgAAEIQAACEGgOARzD5tgCTSAAAQhAAAIQgECtBHAMK8LP3MOKQFMMBCAAAQhAAAK5 CTDHMDe65IxpcxL6OlfBMV7EQQACEIAABCoh0Nf3NhHDSpoXhUAAAhCAAAQgAIHmE8AxLNlGDCGX DBjxEIAABCAAAQg4I8BQsjOUvqB46Dn8va8hacd4EQcBCEAAAhCohEBf39tEDCtpXhQCAQhAAAIQ gAAEmk8Ax7D5NkJDCEAAAhCAAAQgUAkBHMNKMO8XwtzDmsBTLAQgAAEIQAACqQRwDGtqHN+/f3da ssnRNN13qgzCIAABCEAAAh0goOcZRn9ubm46UKvDVWDxiWMTZ1184npSa5o87RB++/Ztb1GM42oj DgIQgAAEINApAq7f022Bg2Po2FJNcwxZFe3YwIiDAAQgAIFeEOirY8hQci+aN5WEAAQgAAEIQAAC ZgI4hmZGpIAABCAAAQhAAAK9IIBj2BAzd31xSNfr15BmhBoQgAAEIACBQgSYY1gI337mvHMMi85l SMvflDmGRevn2EyIgwAEIAABCBwk0Nf3FhHDnnYMIng9NTzVhgAEIAABCBwgQMTQcfNoS8Sw6i+h qstzbFbEQQACEIBAzwj09b1FxLBnDZ3qQgACEIAABCAAgTQCOIa0DQhAAAIQgAAEIAABjwCOYUMb QtfnAHa9fg1tVqgFAQhAAAIQOEiAOYaOG4irOYa2cxtsVyXbyi+KKY1LKDc8uq9oOeSHAAQgAAEI uCBQ9XvShc4uZBAxdEGxAzLqjuB9//69AxSpAgQgAAEIQKDdBIgYOrZfWyOGZX8ZmSKGZZfv2MyI gwAEIACBjhPo63uJiGHHGzbVgwAEIAABCEAgHwHtHEZ/bm5u8glqUS4cw5YYq+6h3pZgQk0IQAAC EICAMwLr9VqiP/f3985kN1UQQ8mOLVPWULIppF108YlJflFMDCUXJUh+CEAAAhCokkDZ78Uq62JT FhFDG1qkrYwAEdLKUFMQBCAAAQhAYEMAx5DGkEigbseMVco0TAhAAAIQgED1BBhKdsy8K0PJrkPo tkPJrst3bGbEQQACEIBAxwn09T1ExLDjDbuq6tUdYayqnpQDAQi4I8Bzwx1LJEHAFQEihq5IBnL6 GjE0fVkRMXTc0BAHgQ4QMD03OlBFqtBiAn1tn0QMW9xom6B6VV/8VZXTBKboAIGuE6A/d93Cu/XD 3u2yNxHDFHvFz+7NepZv3yKGYX1NX1ZFI4Ym+e3qdmgLgX4TyPrc6Del7tQ+/vzO+j6tm0Bf3ztE DFNaXnxVbN9XyfLFV/cjivIh0H0CPGe6ZeM0e/b9fdp0KxMxTLGQKcKVZtiuRgxtN9CO8zHxtL3f 9I6FfhCAgEhaZCgtYtjXCE1X20pWOzc1gtjX9kjEsKs9knpBAAIQqJkAkaGaDdCS4jvXTlYPcho9 Y/n0QVZ7tljJw2l4DvOVvG3u2/7dvZFxDN0zRWIFBBhyqgAyRUAAAhCAQE4CE3kNz1l+v5ZBTMrq 4VKmJ6/eOczL2YeMr3zX0PbvOZU7mA3HsAyqyCydQNlfmDiepZuQAiBQOwH6ee0m6KkCK3l5Wsjk /Myr/+DrhYzmzypqaPv3cvDhGJbDFaktJ1C249lyPKgPgU4QoJ8304zdcNjnMvaGk0/lYW8ceSmf i5EcDwP+gy9yIh/ya2X7d53/Ta50GW/b4WsdfFw9nKqy/aHq040C0WHqIwmClHuNAMewmf0CrSAA AQj0nkDVDkLV5fXewCkAsjrsVdgrdK4O/f/m5ma3JoNreQ+GkZczkekwOocwTHoiX+Ljy94t27/r PAuZ3ok86jJfJzIfH8mlPHrD1Pr3xfSHP4fx7cdm+Frf++kHLHEM6YgQyEOgigdQHr3IA4EuE8jq ILhiUHV5rvTuq5wq7OU5V4af+/v7VBMMrm9l4kUD40mS/qbT2P5d5xnJ7DGYx3h2rsobycXXwOv0 fg9kDo/VkPU4EkHEMexr3+lFvct23Kp4APXCUFQSAhCAQEkEyn4PuFN7KMejiLTVL+W66Uih7d8t NQoimY8qnqgjoAwlW/IjebsI4Lg1217teWA3myPaQaCPBLI+P5r4Hni7Gst8dCF+AC+YD7gaiFpv ItMfwUrklydZTM7lTK1dtvt7vtYwuH5XK6FH8rEfxvQEdmaOYdaGkw8juSAAgSIEwgc2/bQIRfJW 3X6qLg8LJxOwdfjqtdvuAo/xx0yWCdvVDK4fZfYx9iJ3w6cLWQYT/mz/btVm3q42C1KG0xO5vU6c 5CidOfnE9VmMppM40ozBySfJZEw8Xd+36iwJiU36FJXft/ycjds3i/v1tT0xydTvXJ9EUXV5fWsF WU8+yWuHrO/bvNxdt7e8elSdrzMRwzg42y+MqsFTXrsJ1PtF2m52aA8BCECgSgI8r+1od9YxtMNA 6q4RKPtBwIeHmxZTtp3caIkUCECgzQR4XttZD8fQjhepW0Kg6w+CrjhUXbdTS7pLa9XsSj9orQFQ vJMEeuMY8gDpZPvtbaW66lDV3U/rLt91g+5afeqeMtR1nq7bH/LaSaCzi09Mk1lN5sqbP+tkWJN8 0/24/mVP8raVb9LPVD/X9032LqqvfmF8+/bNtpjc6V0vtsqtSMaMeSehZxTvLFnXJpvXXR/b50bR fm/bEKouz1a/ePqqnzNF9c3b7012CfXK+77NWq+6+09WPV2n603EMKmDuYaJvOYSKPtLv+4IXt3l N9fyaBYl4LofuJaHtQ4ToJ/TQqog0FvHkA5WRfNqThnYuzm2aJMmXXN88vaDNA555ZXVBrpmLxOn vtXXxIP7bgj01jF0gw8pEGgmga68MOquR9Mcn7paW1s4VK1n09pn3frU1T4p1y0BHEO3PJEGAY9A 3Q/o+Auybn3yNouqX/R59Wxavqz2zpquafVrij5Na59N06cpdkIPOwK9XXximlSadfJrHHfeybCm 8mz1DfWqavKvrX629XWd3jSJ23V5dt3SnLqofuYS3KZw1Q7darUvzcS17PJdyc/LO6180yKSvPlM vIveN/EsKt/03DOVb3vfVl9b+a7T522HpnrG32+277us9dR6xC/97ri/v88qopXpiBi20mwoXZRA 37+siRTla0Fw87m1hUNb9MzXGovngo+Z4Xq9luhP151CTQTH0NwuSAGBzhFo61Bz3S+yrn9QZOXb Fg5V65mVX1UPlDR9wr9XzaeqelNOMQIMJafwyxrKjmdnKDkZqIln3fez2tE0hJF23zR0bduNy+Zl q48pfdlDSqbys9635erariY9s5bnirepvZuGUk1D0La8i6Yvu5+beJjsa7rvqv5p7cNUvu19V+3Q 1I7i7dTEKWs9yrZnVj2qTodjiGPoETB1JFPHNHUgW/lVp2/bC6NsPrYPIpPDUvYLwlbftPRFubrS I6t+pnSu6pP1g9fUj2xf4EX1r/u55Lo9FOVh4l+WvkX1Nr1/TPUytQNTP3LNpenyGEpuuoXQDwI1 ELAdEqtrSMpWz7JRVq1P1eWVza9r8ttmn7bp27X20pT6EDEkYkjEMKENuP7CjcszRdhMD4iy9TN9 Ycf1N6UvK2JoKtfE0RThKsrZtnxTepM+tpETW3km+SaepvwmfYreN+lXVL4pv8m+pvsm+ab7tvxN +pjul9Xv4/Uoq16uny8mXk25T8SwKZZAj14RqCvC5gpy2/V3xQE5EOgyASKIXbZuet1wDPtpd2oN ASsCbXlBNE3PpuljZXQS955AW3cv6L3hCgLAMSwIkOwQcEGg6Q5EWyKEaXrWxbct3Fy0YWSYCdTV Ds2aZUtBe87Gqe2pmGOYYsGsczXi2bOu3jPJN903lRver2qOh2kuhqk+dd838axaP9ODpWp9bMtL 42krp2j6eD+om6upfNN9Ew/X/T6NX9pzxdSPXOtn4tH055LJ3iaeeevv6r1g0t9VOWl2zPu+Nelt +9zIKq8t6YgYtsVS6AkBCBQmUHfEpu7yCwNEAAQg0HkCOIadNzEVbCMBHIhyrFb3UFjd5ZdDFal5 CdDP85IjX5kEGEpOoWsK0acZJW9o21Se7ZBI2UM2Jvmuh0Bs+dimb7q+Tdcva/u0tUvR9E1vp7YP dxMPU31N+YsO2ZnaqWv98tYnrkdTfje1B9v6muzpSp7pfVi0HFM9bNuViXNae8iar+3pWhcx5Aur 7U0O/SEAgZAAzzPaAgQg0DQCrXMMGYppWhNCHwhAIC8Bnmd5yXUzHx8K3bRr22rVOsewbYDRFwIQ gEBWAjgGWUl1Mx0fCs2zqx7Gjv7c3Nw0T0nHGrVujqHtXIO0uQJZ50Sl5U+zA3MMk8m4nmPiWl5c a9fyi8prun5Z+1NRDrb54/03q55Znxu2+timt7W7qb55y8/6XDPp61q/vPVpin1N+pt4mvKb3pe2 +U39J03fouWY6mHbrrL6Ubb1zSq36emIGDbdQugHAQhAAAIQgAAEKiLQGMeQIZSKLE4xEIAABCAA AQhAIIVAYxxDzmSkjUIAAhCAAAQgAIF6CTTGMYxjYBJuvQ2D0iEAAQhAAAIQ6B+BxjqG/TMFNYYA BCAAAQhAAAL1EsAxrJc/pUMAAhCAAAQgAIHGEMAxbIwpUAQCEIAABCAAAQjUS6B2x5DVyPU2AEqH AAQgAAEIQAACIYHaHUMWmdAYIQABCEAAAhCAQDMI1O4YNgMDWkAAAhCAAAQgAAEI4BjSBiAAAQhA AAIQgAAEPAI4hjQECEAAAhCAAAQgAAEcQ9oABCAAAQhAAAIQgMCWABFDWgMEIAABCEAAAhBIIHB0 dCTRn5ubm85zwjHsvImpIAQgAAEIQAACeQis12uJ/tzf3+cR06o8OIatMhfKQgACEIAABCAAgfII 4BiWxxbJEIAABCAAAQhAoFUEcAxbZS6UhQAEIAABCEAAAuURwDEsjy2SIQABCEAAAhCAQKsI4Bi2 ylwoCwEIQAACEIAABMojgGNYHlskQwACEIAABCAAgVYRwDFslblQFgIQgAAEIAABCJRHAMewPLZI hgAEIAABCEAAAq0igGPYKnOhLAQgAAEIQAACECiPAI5heWyRDAEIQAACEIAABFpFoHTH8Pfff28V EJSFAAQgAAEIQAACfSVQumP4/fv3vrKl3hCAAAQgAAEIQKBVBEp3DFtFA2UhAAEIQAACEIBAjwng GPbY+FQdAhCAAAQgAAEIRAngGNIeIAABCEAAAhCAQAKBo6Mjif7c3Nx0nhOOYedNTAUhAAEIQAAC EMhDYL1eS/Tn/v4+j5hW5cExbJW5UBYCEIAABCAAAQiURwDHsDy2SIYABCAAAQhAAAKtIuDMMWS/ wlbZHWUhAAEIQAACEIDAHgFnjiH7FdK6IAABCEAAAhCAQLsJOHMM240B7SEAAQhAAAIQgAAEcAxp AxCAAAQgAAEIQAACHgEcQxoCBCAAAQhAAAIQgACOIW0AAhCAAAQgAAEIQGBLgIghrQECEIAABCAA AQhAgIghbQACEIAABCAAAQi0j8BKHk7D4/qu5M1hBawjhuxX6JA+oiAAAQhAAAIQgIAlgdXDpUxP Xr3j+pazDxlfuXMNrR1D9iu0tB7JIQABCEAAAhCAgDMCK3l5Wsjk/MyTOPh6IaP5s7Oo4X/6m7ps dP3Tn/4kf/nLX/ay2P49FBDmi+e3lWfKb7ofr5Bt+nh9bOtnKi+NR1q5VZWfZj9bnrb1d52+6fo2 Xb+s7dO13UzyTP2g6Vxt9TPV18Qr63M3b793rV/e+pie1025b2t/Ew/X/E2+Q9b3u0nvou3S9HxK q8cff/whli6SCYmj+/9T/se//x85/tt/l//yz0rkP/8/+V9//If807/q39/k6ujf5H97/9bFRX/X w8//Wf7rv/8hum7/91/+Jv9tuK/SkQpDrh1pihgIQAACEIAABCDQCQJnZ2fy97//3VgXPcXu/v7e mM5dAu3sPcv5+qf4MUP9+50cL9/lehD9d+ze8kqOns9l/dPPlXZlHkr+9u2bHB2FEx35PyxoA7QB 2gBtgDZAG+huG/jzn//szeEz/VTrFIbu3If8Wlm6msNjNeQ8ltOHwxlrjRjqDuUyYIk8y0YSSw4/ +NkQoL3Y0EoYruH5Vwgg7a8QPi/Qw/u3GMP6cush4UuRRx0hVFqsHuR0+Cm3XgTxQMRQp/WSn8pw quYovq4lKXiYOWJYHwBKhgAEIAABCEAAAhDwCQxErTeR6Q9/JfLq5UkWk/NgWHkox6OFfC4DVm/P Mo9hG1y/q5XMI/lICTniGNLOIAABCEAAAhCAQIsIDK4fZfYx9iK/w6cLWW5CfwO5vp3IfBwM8T+L TMJ6vak5hsGUwOH0RG69cOP+xVDygYZAqL1YL4Ef/GwI0F5saCU8zBkaLASQ9lcIX++GpovRanbu WiOGekGLy6tv8lyy07L6xs91fbFHMQLYo1n8sAf2sCHgur00Xd4uGz2vb3cRjmmBRzpbLetUDOtD bExjnbbWiKG1tmTYIeD6Cxe8xQhgj2L8XOfGHq6JFpOHPYrxc50be7gkGl/wUUS2S1n59Kg1YphP ZXJBAAIQgAAEIAABCJRBAMewDKrIhAAEIAABCECgGwRWK7HdMlBX/O3qSLZHGMeGiPUWM+FN/e9g KPr04VftzHAMazcBCkAAAhCAAAQg0EgC2mn7sVQbxJiuhUyH23mG2uc7O1erg5/9LWVEbRvzMRJ5 evFdTL3FjBzr8+iUwzicyonaU1DvK/koT3vby5hKdn0fx9A1UeRBAAIQgAAEINB+At7G0VNZqNNC kk+4uVJuXXiNZLbcnpLi7R6jTxr5+OVFG9+eP+TiVm0++PSifl+J9gsvvip3c/VLOYwz+S04pW5w fbvdXqYmgjiGNYGnWAhAAAIQgAAEGkxgcC3vy5lMZsuUY/HCs4pT6jD4KhcqAviyepPnjwv5eqZ/ /5Tl6kX9Vf1uDkPWAgfHsBbsFAoBCEAAAhCAQOMJKOfwty/LXHMMwxNKni7v5OPiqxqO1ieWfMjz j08dLvSHpwdf5GQxleAQE3Vc3R1DyY1vFCgIAQhAAAIQgEBvCQzOzjLMMUzGM9Bn1y2CYWPtB6rf P+ZqWHkTLjyTn6/bk0ouVSRxc1JJTcTZx7Am8C6KZR8qFxTdycAe7li6kIQ9XFB0JwN7uGPpQhL2 cEExSYZefTzeifpN1MKSzYl1ZRXrUC5DyQ5hIgoCEIAABCAAgb4TiCxE8aKB0UUqzWeDY9h8G6Eh BCAAAQhAAAJtJHB2roaGP+RXno0Qa6ovjmFN4F0U6/osSRc69VkG9miW9bEH9mgWgWZpQ//IaQ/b za7V/oXzUWQFcmQz66MjHUlcycNpdCNspdfblRydPuRc8JKzXpFszDEszhAJEIAABCAAAQh0nYC3 2fUXeT84YTA2x3DyKutN+tg5yMoBPP31m7x/+SFHz+ebdPrElOfz+uYlEjHsekOmfhCAAAQgAAEI FCOQZ7NrtQfiaP683QRbb2atlihvTkgZz2XxudRHpMhkk07vebjd8LqY0vly4xjm40YuCEAAAhCA AAT6QiDPZtcqz+PsQ+4eohMMJ/Kqjr7Tx995P1408Ux+C9LpfQz9PQ/ru3AM62NPyRCAAAQgAAEI tIVAjs2u9RF3J9NL8XxDvZm12shm11H0K+/td/j0Q348ncjtdZ1uoQiOYWMapD8B1T+PMWVp+86k VZVuMzk1Q97G1LOFiuiJwEenfsc2XtjCiChvApMd6B95yRbIF23vsQn0iVLpHwVgH8iawQ70Dyfo 7Te71tFAkemlXkyiNrNWw8tqLHl79vJVcNqyd3zeXOYn5ypVvReOYb38N6WvHi5leqImqarQ8lKF lMdhY9nTLxKGfr/2ws3Z8zaksq1RI3jYPkvmneixRRnGtbED/aMMC6TKfHsReQyGxDLs10b/KMk6 me1A/yjJAhGxyvlbv0s06De4fpd18L4WPSS9N5Sssw/k+j0cWi5fy0Ml4BjWyz8ofSUvTwuZnPvf CTqkvDNh9aCORfI2ovINViLsqOcZdcQWGUFZJrO1Q1Q8NrGEbZf87Hr7AjTu14Yt7OBapLayA/3D gmwvk+IYNsLsS/lcjOR4GCjjzUNI2xBzLmNvuDkc2jyUN8PwQiPq3xUlsEX9lqR/1GYDveIyul/b niL0j0psc9AO9I9KbNDyQnAMG2PAE/limm8aCUH70xTCuYgped9+bIan9RB1m85qbIxZrBXBFtbI XGWgf7gimUOO+gi9nMrJrT+9Jf2if+SAa5HlgB3oHxYc+50Ux7Ax9rc7MkevdNoes5OSd3ishqTH cppt1URjSLRbEWzRBPvRP6q1wtvV0PsINX980j/KtExWO9A/yrRC+2XjGDbChkM5HkUU8TbBzBBB 9LIcyBt8IT7KpbcCKnU9SyMYdEEJbNE8K2KTsm2yejiVsURPd0grEVuUaYvsdohqgU3KtElbZeMY NsJyA9FbGE1/+MvWVy9PspiES9b1ETr7W6W8XY2D8xcP5fUrp1dELWcj+WjTKd6NsMshJZLsgi2q Nxv9o3rmkRLVFkLDpwtZ7oUK6R+V2sXKDvooXt4fldqnbYWpuWdcjSCwXCvfba3az1pGs/Vyo9Pr eiKj9WwZub+XJiXv68SX5/1M1mq3dS4rAjHmO9xDu8QFYgsrxJkSZ7ED/SMTSqeJEuyi+sjEe9DQ P5yiPigsix3oH9XZo/0lHekqtM2ZRV8IQAACEIAABCAAAfcEGEp2zxSJEIAABCAAAQhAoJUEcAxb aTaUhgAEIAABCEAAAu4J/H+FhOPE1VgHMgAAAABJRU5ErkJggg== --047d7ba97b72c4ced304d6c73540 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 --047d7ba97b72c4ced304d6c73540-- From xen-users-bounces@lists.xen.org Thu Feb 28 11:32:36 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 28 Feb 2013 11:32: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 1UB1i8-00033L-1x; Thu, 28 Feb 2013 11:31:40 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UB1i5-00032i-Rg for xen-users@lists.xen.org; Thu, 28 Feb 2013 11:31:38 +0000 Received: from [85.158.138.51:57153] by server-12.bemta-3.messagelabs.com id 58/F2-01357-4104F215; Thu, 28 Feb 2013 11:31:32 +0000 X-Env-Sender: agya.naila@gmail.com X-Msg-Ref: server-12.tower-174.messagelabs.com!1362050995!20311747!1 X-Originating-IP: [74.125.82.178] X-SpamReason: No, hits=1.4 required=7.0 tests=BODY_RANDOM_LONG, HTML_40_50, HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14, RCVD_BY_IP, spamassassin: X-StarScan-Received: X-StarScan-Version: 6.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 781 invoked from network); 28 Feb 2013 11:29:56 -0000 Received: from mail-we0-f178.google.com (HELO mail-we0-f178.google.com) (74.125.82.178) by server-12.tower-174.messagelabs.com with RC4-SHA encrypted SMTP; 28 Feb 2013 11:29:56 -0000 Received: by mail-we0-f178.google.com with SMTP id u7so123277wey.9 for ; Thu, 28 Feb 2013 03:29:55 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=IGp3hkfEocq+SJcB2NOHPzMcW02NksxuZ/s7LtUQRho=; b=Gibm9P9uajQLyLHXxhuB36RnKZo57vyUe4a9RH7ThSSvje4S9GzZkbQXdmais0H7g/ OKt6ThR4rNVp21efswbf+7yVLharenK3FTodqenSMzRrCccaRr86yaPLPqToQ1tk9YO/ zMB1rTHr95g0p8ZWPmeXvacidl/4YZAPIVOq1qagN9mgWBsB8bNIg8YkUWoxoguf67Nz O747HOp1YIR3m7cq8/ARrK9ULKwV6KvfnyYAGemq5SxyTRhxkmfaQeyp7XRs6ajHe1Rk HX0uqyjOE+lUzEkFIBZhgeP5O3y/46g9XQs093cjagsMrP4PICP2mFTRlM6nmKq5bvxj X5Gw== MIME-Version: 1.0 X-Received: by 10.194.63.240 with SMTP id j16mr10104688wjs.45.1362050995767; Thu, 28 Feb 2013 03:29:55 -0800 (PST) Received: by 10.216.236.13 with HTTP; Thu, 28 Feb 2013 03:29:55 -0800 (PST) In-Reply-To: References: Date: Thu, 28 Feb 2013 12:29:55 +0100 Message-ID: From: agya naila To: Andrew Eross Content-Type: multipart/mixed; boundary=047d7ba97b72c4ced304d6c73540 Cc: rshriram@cs.ubc.ca, "xen-users@lists.xen.org" Subject: Re: [Xen-users] Remus dom0 network buffering X-BeenThere: xen-users@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 --047d7ba97b72c4ced304d6c73540 Content-Type: multipart/alternative; boundary=047d7ba97b72c4cecf04d6c7353e --047d7ba97b72c4cecf04d6c7353e Content-Type: text/plain; charset=ISO-8859-1 Hi Andrew and Shiram, I am keep trying this setting using my machine that I mention earlier in this email thread. I have using remus with network buffering and no network buffering. with no network buffering #remus --no-net with network buffering #remus However, when I observed the jitter graph result of my data it seem there is no buffering impact on my traffic flow, enclosed both the graph result. I only observed RTP packet and observed the jitter. What I could understand the graph with network protection will doesn't have flow until x time when the buffer released, in this case default value 100ms. Y axis is time and X axis is jitter. Both of command above running without error except suspend event channel issue that we discussed earlier. Please suggest. Regards, Agya On Wed, Feb 20, 2013 at 1:13 PM, agya naila wrote: > Aha, sorry to mix it :), its clear now. > > Regards, > > Agya > > > On Wed, Feb 20, 2013 at 1:01 PM, Andrew Eross wrote: > >> Hi Agya, >> >> This patch doesn't fix the 'suspend event channel' issue, it just fixes >> the crash from the first e-mail in this thread. >> >> Please see this wiki page: >> http://wiki.xen.org/wiki/Remus_PV_domU_requirements >> >> That discusses the suspend event channel issue. >> >> Cheers, >> Andrew >> >> >> On Wed, Feb 20, 2013 at 8:57 AM, agya naila wrote: >> >>> Hello All, >>> >>> I am trying this patch on my machine Ubuntu 12.04 AMD64 both for Dom0 >>> and DomU with Xen 4.2.2-pre compiling from sources also DRBD 8.3.11 but >>> unfortunately it seem didn't work since I still got the message WARNING: >>> suspend event channel unavailable, falling back to slow xenstore >>> signalling. >>> >>> Regards, >>> >>> Agya >>> >>> On Tue, Feb 19, 2013 at 12:39 PM, Andrew Eross wrote: >>> >>>> Hi all, >>>> >>>> To close off on this, Shriram's patch worked great, thank you. >>>> >>>> So Ubuntu 12.10's standard generic kernel is now working fine as a dom0 >>>> for Remus with Xen 4.1.4 (with the patch from this thread). >>>> >>>> I wrote up my full install instructions here: >>>> >>>> http://wiki.xen.org/wiki/Install_Xen_4.1.4_with_Remus_and_DRBD_on_Ubuntu_12.10 >>>> >>>> I also took a shot at a number of updates to: >>>> http://wiki.xen.org/wiki/Remus >>>> >>>> And added these pages: >>>> http://wiki.xen.org/wiki/Remus_PV_domU_requirements >>>> http://wiki.xen.org/wiki/Remus_dom0_requirements >>>> >>>> Feedback very welcome, a lot of that information was a bit old, so I >>>> did my best. >>>> >>>> Cheers, >>>> Andrew >>>> >>>> >>>> On Mon, Feb 18, 2013 at 8:26 PM, Shriram Rajagopalan < >>>> rshriram@cs.ubc.ca> wrote: >>>> >>>>> ah darn. Yes, the 3.5 kernel has sch_plug in it. Unfortunately, the >>>>> technique to initialize the sch_plug module is bit >>>>> different with the module thats already mainline. You ll have to patch >>>>> the qdisc.py python module. I ll submit the >>>>> patch to xen devel soon. >>>>> Mean while, can you try the patch below and see if it works ? >>>>> >>>>> Secondly, you said you were writing a blog about how you set it up. >>>>> One of the remus users created a wiki >>>>> remusha.wikidot.com, which has a whole tutorial on how to setup remus >>>>> with Debian Squeeze. I have been under fire >>>>> lately for a host of remus issues. It would be great if you could post >>>>> your experiences on the wiki too. >>>>> (http://remusha.wikidot.com/system:join) >>>>> >>>>> thanks >>>>> shriram >>>>> >>>>> --- >>>>> diff -r 6435f1edf24e tools/python/xen/remus/qdisc.py >>>>> --- a/tools/python/xen/remus/qdisc.py Tue Jul 17 19:23:30 2012 -0400 >>>>> +++ b/tools/python/xen/remus/qdisc.py Mon Feb 18 18:25:22 2013 -0500 >>>>> @@ -1,6 +1,9 @@ >>>>> import socket, struct >>>>> >>>>> import netlink >>>>> +import platform >>>>> + >>>>> +kernelversion = platform.platform(terse=True).split("-")[1].split(".") >>>>> >>>>> qdisc_kinds = {} >>>>> >>>>> @@ -150,9 +153,14 @@ >>>>> TC_PLUG_RELEASE = 1 >>>>> >>>>> class PlugQdisc(Qdisc): >>>>> - fmt = 'I' >>>>> >>>>> def __init__(self, qdict=None): >>>>> + if int(kernelversion[0]) >= 3 and int(kernelversion[1]) >= 4: >>>>> + self.fmt = 'iI' >>>>> + self.limit = 10000 >>>>> + else: >>>>> + self.fmt = 'I' >>>>> + >>>>> if not qdict: >>>>> qdict = {'kind': 'plug', >>>>> 'handle': TC_H_ROOT} >>>>> @@ -161,7 +169,10 @@ >>>>> self.action = 0 >>>>> >>>>> def pack(self): >>>>> - return struct.pack(self.fmt, self.action) >>>>> + if int(kernelversion[0]) >= 3 and int(kernelversion[1]) >= 4: >>>>> + return struct.pack(self.fmt, self.action, self.limit) >>>>> + else: >>>>> + return struct.pack(self.fmt, self.action) >>>>> >>>>> def parse(self, args): >>>>> if not args: >>>>> >>>> >>>> >>>> _______________________________________________ >>>> Xen-users mailing list >>>> Xen-users@lists.xen.org >>>> http://lists.xen.org/xen-users >>>> >>> >>> >> > --047d7ba97b72c4cecf04d6c7353e Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Hi Andrew and Shiram,

I am keep trying this setting usin= g my machine that I mention earlier in this email thread.
I have = using remus with network buffering and no network buffering.

with no network buffering
#remus --no-net <vm> &= lt;backup target>

with network buffering
<= div>#remus <vm> <backup target>

However, when I observed= the jitter graph result of my data it seem there is no buffering impact on= my traffic flow, enclosed both the graph result. I only observed RTP packe= t and observed the jitter. What I could understand the graph with network p= rotection will doesn't have flow until x time when the buffer released,= in this case default value 100ms. Y axis is time and X axis is jitter.

Both of command above running without error except =A0s= uspend event channel issue that we discussed earlier. Please suggest.
=

Regards,

Agya

On Wed, Feb 20, 2013 at 1:13 PM, agya naila <agya.naila@gmail.com> wrote:
Aha, sorry to mix it :), its clear now.

Regards,

Agya


On Wed, Feb 20, 2013 at 1:01 PM, Andrew Eross <eross@locatrix.com> wrote:
Hi Agya,

This patch doesn= 't fix the 'suspend event channel' issue, it just fixes the cra= sh from the first e-mail in this thread.


That discusses the suspend event channel issue.

Cheers,
Andrew


On Wed, Feb 20, 2013 at 8:57 AM, agya naila <agy= a.naila@gmail.com> wrote:
Hello All,

I am trying th= is patch on my machine Ubuntu 12.04 AMD64 both for Dom0 and DomU with Xen 4= .2.2-pre compiling from sources also DRBD 8.3.11 but unfortunately it seem = didn't work since I still got the message=A0WARNING: susp= end event channel unavailable, falling back to slow xenstore signalling.=A0=

Regards= ,

A= gya

On Tue, Feb 19, 2013 at 12:39 PM, = Andrew Eross <eross@locatrix.com> wrote:
Hi all,

To close off on this, Shriram's patch worked= great, thank you.

So Ubuntu 12.10's standard = generic kernel is now working fine as a dom0 for Remus with Xen 4.1.4 (with= the patch from this thread).

I wrote up my full install instructions here:
http://wiki.xen.org/wiki/Install_Xen_4.1= .4_with_Remus_and_DRBD_on_Ubuntu_12.10

I also took a shot at a number of updates to:
http://wiki.x= en.org/wiki/Remus

And added these pages:
Feedback very welcome, a lot of that information was a bit old,= so I did my best.

Cheers,
Andrew

=

On Mon, Feb 18, 2013 at 8:26 PM, Shrira= m Rajagopalan <rshriram@cs.ubc.ca> wrote:
ah darn. Yes, the 3.5 kernel has sch_plug in= it. Unfortunately, the
technique to initialize the sch_plug module is bit
different with the module thats already mainline. You ll have to patch
the qdisc.py python module. I ll submit the
patch to xen devel soon.
Mean while, can you try the patch below and see if it works ?

Secondly, you said you were writing a blog about how you set it up.
One of the remus users created a wiki
remusha.wikidot.co= m, which has a whole tutorial on how to setup remus
with Debian Squeeze. I have been under fire
lately for a host of remus issues. It would be great if you could post
your experiences on the wiki too.
(http:= //remusha.wikidot.com/system:join)

thanks
shriram

---
diff -r 6435f1edf24e tools/python/xen/remus/qdisc.py
--- a/tools/python/xen/remus/qdisc.py =A0 Tue Jul 17 19:23:30 2012 -0400 +++ b/tools/python/xen/remus/qdisc.py =A0 Mon Feb 18 18:25:22 2013 -0500 @@ -1,6 +1,9 @@
=A0import socket, struct

=A0import netlink
+import platform
+
+kernelversion =3D platform.platform(terse=3DTrue).split("-")[1].= split(".")

=A0qdisc_kinds =3D {}

@@ -150,9 +153,14 @@
=A0TC_PLUG_RELEASE =3D 1

=A0class PlugQdisc(Qdisc):
- =A0 =A0fmt =3D 'I'

=A0 =A0 =A0def __init__(self, qdict=3DNone):
+ =A0 =A0 =A0 =A0if int(kernelversion[0]) >=3D 3 and int(kernelversion[1= ]) >=3D 4:
+ =A0 =A0 =A0 =A0 =A0 =A0self.fmt =3D 'iI'
+ =A0 =A0 =A0 =A0 =A0 =A0self.limit =3D 10000
+ =A0 =A0 =A0 =A0else:
+ =A0 =A0 =A0 =A0 =A0 =A0self.fmt =3D 'I'
+
=A0 =A0 =A0 =A0 =A0if not qdict:
=A0 =A0 =A0 =A0 =A0 =A0 =A0qdict =3D {'kind': 'plug',
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 'handle': TC_H_ROOT} @@ -161,7 +169,10 @@
=A0 =A0 =A0 =A0 =A0self.action =3D 0

=A0 =A0 =A0def pack(self):
- =A0 =A0 =A0 =A0return struct.pack(self.fmt, self.action)
+ =A0 =A0 =A0 =A0if int(kernelversion[0]) >=3D 3 and int(kernelversion[1= ]) >=3D 4:
+ =A0 =A0 =A0 =A0 =A0 =A0return struct.pack(self.fmt, self.action, self.lim= it)
+ =A0 =A0 =A0 =A0else:
+ =A0 =A0 =A0 =A0 =A0 =A0return struct.pack(self.fmt, self.action)

=A0 =A0 =A0def parse(self, args):
=A0 =A0 =A0 =A0 =A0if not args:


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




--047d7ba97b72c4cecf04d6c7353e-- --047d7ba97b72c4ced304d6c73540 Content-Type: image/png; name="net_protect.png" Content-Disposition: attachment; filename="net_protect.png" Content-Transfer-Encoding: base64 X-Attachment-Id: f_hdpttjuh0 iVBORw0KGgoAAAANSUhEUgAAAo8AAADICAYAAACJUguGAAAAA3NCSVQICAjb4U/gAAAAAXNSR0IA rs4c6QAAAARnQU1BAACxjwv8YQUAAAAJcEhZcwAADsQAAA7EAZUrDhsAACimSURBVHhe7Z09bytL 0piLr6NNX/8F8gSCgs1sUxtsKh4YUKTIgAz4BRWKyQWuAAV7AQE6B0qo8DAxlAoOlIjcdAMRsIHN CAUiYYcO/RPo7hkOORxx2NMzPd8PL4R7yOmurnqqe1isnu7urNVLeEEAAhCAAAQgAAEIQCABgX9J UIYiEIAABCAAAQhAAAIQ8AgQPNIRIAABCEAAAhCAAAQSEyB4TIyKghCAAAQgAAEIQAACBI/0AQhA AAIQgAAEIACBxAQIHhOjoiAEIAABCEAAAhCAAMEjfQACEIAABCAAAQjUicDsWjqdM3lahZVeydNZ R32u/65llqM9BI85wkU0BCAAAQhAAAIQcEdgEyC+igwjQldPVzI6nYregXE5XsjgOr/wkeDRnUeR BAEIQAACEIAABHIk0JWb97Wsf11EQ0d5e5nL8OLc+7z7/VL6k9fcso8Ejzm6GNEQgAAEIAABCEAg fwJL+Zj35aS3aan7TU5lIZ/etPZMrvUU9+xJzrwp7Y7opOTq6Wwzxd2Rs+38d3jq2y936EXwmL9H aQECEIAABCAAgQYS+Otf/7oNwPxnDQ//3d7eFmD9qXzrxjUzl9G9yLOa0l5PhzIZdORKnr0pbv1+ Pnr0s5Szx+3Ut772y09kfnkRPBbgTpqAAAQgAAEIQKB5BP7xj3/4AZjh7+HhoQDjg0zjoab6Mn6+ ES+2PL9Qz0v25fL7JtL03m/q9k7UdPcglIkkeCzAcTQBAQhAAAIQgAAEiibQk5N+qM3VpwoHj2Ui Y/Tr3si7CoSfVV4ymN4m81i0L2kPAhCAAAQgAAEI5E6gK2qNjIwe/YcUV28vMh9eSMyss1Gb7s27 WrHdl4X/0OSXF9PWRoQUgAAEIAABCEAAAlUgECxoGchE1HOMPfWM5dmT6BCve/Ms48XAyxj2Xi5l GffA4jEzvP0j/ec2e6NTubs5/BBlR83Tr6uAAx0gAAEIQAACEIBAnQjoIKuNYRSZxzr1UnSFAAQg AAEIQAACJRMgeCzZATQPAQhAAAIQgAAE6kSA4LFO3kJXCEAAAhCAAAQgUDIBgseSHUDzEIAABCAA AQhAoE4EWhI8+quTcjwjvCI+b4udFcGNGhCAAAQgAIEWEmhE8Di73i1V1z70zmvMECl68tQKqt1Z j37PsJVrW77I/hfYuDtK6TrzAeou7T0kK+rnInnRFgQgAAEIQAACPoFGBI/nv9TRQO+bY3ccebbf 7+/OenQks2pi+uPl9kil5Xghg072ADJPG/Pwc576IhsCEIAABCDQRAKVDB6/ZJ28TSvDgc1MrlVm MEguehkp740/bdsbzUWd+n0ge+jX87NtZ/J0eON038+XdzLuT2RwNIMZbNYZyAx0PKyHrV2BPYez g9oWZcNTsKHngcDP42awc9Oruzd36mzLibz6J6PHyLaz1xcdV2fT8OpJzkIHyV/P4n2483MwFI/J DqbwLXzexBGOTRCAAAQgAAHHBCoZPHbVGTv9yet2GlUd0Sh9Fcj5gY2OR/SZjUO5+HLuTldu3tfe kToynHpZtffQ7uiTwb2cLP0DzKdDtTP75hifw0x7cvM8VnrcxwaZs+uejE79dvSfl73zdno/rIed XTr4OSB/L4hWNoxEpl77v/aPIdKB42Ah4+W7xGwQv2+2x7QvJ73g46jsY/rEc49ntAlSe8qAbQZ0 KnL/Jt+P+HCndBI++jeEjc8djy7EQQACEIAABBpIoJLBo3S/qeO8g2BxJeqIRrm7G27PWEx7ZuNw ugukzi+GogR6R/rEvtQB4Xc6yLzyj/7Ze6mM2f2kL+PfdhGsl72bv8hbnFAbu1Zv8jIfyjR0vJCf HVxI+KjJ4TQSNGolP1U2zyZwVFVmjyOZ9y/le+gkoj3ZCfWxYjR7VV4eho4/OpdfSR8/SKiPtc8b OMgxCQIQgAAEIOCSQDWDR5VD82M7HYUt5eNUHe7dOxF5eVNBnA4m5zL8mnZ0yWUr6/zXVAWEI7k6 OMe9OVdyO+2qz5o89rKwa/mhTq2Mvnpy0p/Lx/K4qROVjvxa92ud+ai3PcNysBjL8ljgllofA6P+ iWyTnTYeTK2PTSOUhYA9gd9//92+EjUgAIHaEtg9WuY/wnZ7e1tbW5IqXtHgUURnBuc6WFTZqYWe S+1+l0vRWT0VTKqMXEGxo+KosmFTpcvoUd6+UFWZwc2UdTB1vV4fnyZObJcKltXke+SlbQ9PLR92 83Cqp9DlcMY0VCW8YMa44Ci1PgZG8w/18yDFK7U+KdqiCgQsCPz8+dOiNEUhAIG6E9h9//uPsD08 PNTdJKP+lQ0eVfToTQE/vi7k9JueS+3Kt1OVdXtUU51DlYk0mWaakjbVD18//81bPDPSC3GClw5m 1Wf3R1fdqMJRPZLatZEfXrCzerqXSWRqOc6M7s2zjGUkvQxbFu3JTqpP2F4TI81C5Wp3DNXiFu+Z 0c3rmA+T6mPjZ8pCAAIQgAAEIGAkUN3g0Zu6nstkcrrNMuqs3WSinpIzpB29hSlqqrl3YK9GI5GD BdSCEL14Zj+aUotzlnL5spv69VLXoeDnsB5J7dKLUNSU+WbVuJbde7k8PrX8RT+/fnS/ytQMDPp8 tVfbcIyRyup6KdKAoVrc8uxvuWT2YVY+6ShQCwIQgAAEINB2Ah2VYl23HQL2QwACEHBFQP/Q47bq iiZyIFBtAm0d7xXOPFa7w6AdBCAAAQhAAAIQaCMBgsc2eh2bIQABCEAAAhCAQEoCBI8pwVENAhCA AAQgAAEItJEAwWMbvY7NEIAABCAAAQhAICUBgseU4KgGAQhAIAkBNg1PQokyEIBAnQgQPNbJW+gK AQhUlkBckMim4ZV1GYpBAAIpCbBVT0pwVIMABCAQJhBs2RHduqOtW3nQOyDQBgJtHd9kHtvQu61s XMnTWUdcHUzjN52HTCujKAwBCEAAAhCAgCMCFQ4edcBxJsHpf7Nr1wGNI4KIqRSB1dOZdNxGvlb2 ld2+lbIUhgAEIAABCKQgUOHgcSkf81PxjrVWmavPRV9OeiksrGiVXIKM2bV0OtcyS2FzLvqk0KNx VTL4pHEsMAgCEIAABBpBoJrBo/eFO5CJ+m+gz4vu9GQ0n6sjkHeZSJ/+TK476rMnXV6XCwInf5rU /yz8uR+I+hlNXTd8PVwn3M6BKVetX+gMay/w2sqK6rjfT4KyV/Is61/nojOq+5kyvz3/PGpLXc9/ qWPRLuT1i83xfTWqz65kmE/EptWTnG3tjWSEj10LhHv+DWSa+B5icIixL6c3motszgPfnukdq1NM //H0C/efsI/i+lZM+yl80og7C0ZAAAIQaAmB6PfF7e1t8y3XZ1tX8jUdrqU/Xi+1csvxuh/8e0/Z 6Xooos7mHq6noc+nQ/XZcPfJctzfyVISx/1wneC9rIMqh8qHxK3XUd0i7R/i6cnUuu4JUiW1rHB9 bav012PfcEtdQy17cr6yCUrE6rNtM9BB49e6B4wV85Av9ln5/uj7ymvjNmV9OzzTPXt3sgMbY/ka 9dmn7emzL8yo737/0TZEbA/JO963NqyiPt5BP+qTSo5DlEpMQI9v/Qr+H1SMvk8skIIQgEDlCbR1 fFcz86hzbp8LkdNv4s1aLz9E5ZNiX8PpLzkPrqos0/2kL+Pftp9I9+ZOhvMXedPJvM1rV6cr3y9V mDWcikoEeq/ut1OR+YcsE/92mMjrkblind3rvVyKCqm8bOPe6/xChirDGtRfvb3IvH8p3z3D/Vcq Xbs38q7bm4rK3u5PZR/VZ9vmu9xsdPD4yUI+PX7n8uv9xveLZvX9UvoBq9mrsmQod0HFSFn5VBnL wULGy53spIiH0zh9TBKO6PuFr/pg9aksDR6X2PSFxafKAetryfpWrEZHfGKyguvNIcC+j83xJZZA oK0EKhk86qnc8PRjZzBRwdxIeqGp4uMO01Pc4WlHPQWe00sHBMuxLAZ+e9up0lBz3Zt3WV6+SE9P hX5ZzHEuFypdN/Gix5W8vcxleLcLzlJrHUzVDkSm61BwrQO+o/rEtTiXj000vTdN3xvtB/b9E4l7 NHUyipRNbZyuuNPHJOaovtHK3W8qdAwCZfVgxKvqOcGPGK9shr51xCcmG7jeHALs+9gcX2IJBNpK oJLB4/mvtajpQT37qOeBRE1FqhnspaxDGa/jDhuqgMmvu/uzz3Yl7hRBRkml+U5HvYPb3OiAzbPl 5P5LkHn+21j6k1eZrd7kZT6Ui0hyMrEeXsHNs4q9D7nz7N8PHANZx/Q53N5mwZJ6HrA3Ot3xVYGz ytvuXkcyttqfqriMrp78TF6mV8IFVCZ9ozp4mcddgDiYqL60ly1O07eS+SQTDipDAAIQgAAECiJQ yeDRX129I7D8mKvkT2ge9xic7ne57E/kPtjjJzPIruhZbD8zqF46e6QzoQdfPTnZi6S+FgqCtme5 2mUhA52v1JT18GI3BW+ru7fQ41UujgSNUZEH9VGFJoPdopTV071MIlPpgZzZYyibuJmC37FXQVMk W9y9eZaxqCzyNgObjG9SfTy9gmnmA/z29D3EVz8ioR5h2P3oCAXfSftWuP0UPrF1O+UhAAEIQAAC RRKoaPCoEQSZpf1A0gynKzfvS7l86e2vmE085f21hfNfUxluVvB2dEZPp0W30VN4Za5aFX66e3by mK5e0LbNaPnPXc7VivJhlrSjt7L3cKbRxG1fH/XM6PRSXjZT/16mMcj6qjamw2AVfEfuT8bqKcfg pZ4v9FKLAft7OXmOTsFr//g8gyn+o3w3oofTO/k4pE/EMP8ZTBWcBo8QHNX3ABVdXgYxfcfctw61 n9YnJp9xHQIQgAAEIFAGAY4nLIM6bVoQ0Fvg9OTjbr1d0GRR2brodjFR6BEJ/Qzu/clS3rcLgazF UqEFBJIeT9jW48xa0AUwsYUE2jqeK5x5bGEvxOTSCehHJPYXyNhmvks3AQUgAAEIQAACuRIgeMwV L8LrRuD811LGi/C0dU9eLsk61s2PddKXrXvq5C10hQAENAGmrekHEIAABBwQSDttnXbaSwedP378 cKA5IiAAgbQE0o7ftO1VpR7BY1U8gR4QgECtCRQdPLb1S6vWnQTlG0egreOQaevGdWUMggAEIAAB CEAAAvkRIHjMjy2SIQABCEAAAhCAQOMIEDw2zqUYBAEIQAACEIAABPIjQPCYH1skQwACECiMAKu2 C0NNQxBoPQGCx9Z3AQBAAAJVIpA2CPz582eVzEAXCLSGgF40E/67vb1tvO2stm68izEQAhAogoCr 1dZJV29GyyWtVwQL2oBAWwi0ddyReWxLD8dOCEAAAhCAAAQg4IAAwaMDiIiAAAQgAAEIQAACbSFA 8NgWT2MnBCAAAQhAAAIQcECA4NEBRERAAAIQgAAEIACBthAgeGyLp7ETAhBoFYG0q7ZbBQljIQCB VAQIHlNhoxIEIACBYgikDQLZuqcY/9AKBNpIgK162uh1bIYABJwTyGurnritQExb9bR1CxHnjkUg BI4QaOs4I/PIsIAABCAAAQhAAAIQSEyA4DExKgpCAAIQgAAEIAABCBA80gcgAAEIJCCQ9tnDBKIp AgEIQKBWBAgea+UulIUABMoiUPcFKAS/ZfUc2oVA8wiwYKZ5PsUiCEAgBwKmB+OrvmDGpH8OyBAJ gcYTaOu4IvPY+K6NgRCAAAQgAAEIQMAdAYJHdyyRBAEIQAACEIBAywjo7GP47/b2tvEEmLZuvIsx EAIQcEHAND3FtLULysiAQL0ImO4L9bImubZkHpOzoiQEIAABCEAAAhBoPQGCx9Z3AQBAAAJtJMDq 6zZ6HZsh4IYAwaMbjkiBAAQgUCsCdd96KC/YBNV5kUVukwgQPDbJm9gCAQhAoGIE6haMRYPquulf MfejTkMJsGCmoY7FLAhAwC0B04PxdVswY7LHFb2gHR2E/fjxw5XY3OREuRTFKTeDEJwrgbb2DzKP uXYrhEMAAhCoB4G8M2xMk9ejH6AlBJIQIHhMQokyEIAABBpOIGtwl3fw2XD8mAeBWhFg2rpW7kJZ CECgLAKm6am6T1ub7DNxj6sfx8Ukr6zrTFuXRb6e7WYdN/W0WoTMY109h94QgAAEakygrpnKuupd 466C6hUkQPBYQaegEgQgAIGyCeQdJNV1VXPW6f2y/Ur7EHBBgODRBUVkQAACEGgYgaKDpKLba5i7 MKduBFZPchY+E/vsSVZfbFjJ01lwbva1zLbXbT93D4fg0T1TJEIAAhCAQEYCeWc+M6pHdQg4IDCU 6Xota/33fiPdiMTV05WMTqfe9eV4IYNrP3y0/dyBol9EEDzmQRWZEIAABCCQiQCZyEz4qFx7Ait5 e5nL8OLcs6T7/VL6k1eVfbT9PB8QBI/5cEUqBCAAgUYRIBN42J1waVQ3L9iYiQy8qeszefoyZ72U j3lfTnoblbrf5FQW8rmy/VzXn8m1bmO2myrXSczV05lq258WP9sqEJ4S78gm2UnmseCeQXMQgAAE GkGATOBhN8KlEd07kxFBAHbs/7e3t/ttdG/kfTNlvRyLjHrhZxqDoqfyLTqX7V2y/VzXmcvoXuRZ tzkdymTQkSt59qfM1fv56NF/pnL2uJ0q19d++YlPgsdMPYTKEIAABCAAAQhAIETAC8AMfw8PD7HM ujd3MvSyitEihz7TZWw/13X6Mn7ePFd5fqHa68vl901k6r3fyOydqOnxQSgTSfBIZ4cABCAAgZoS YHq4po5D7ZQEenLSD1VdfarwTmccbT+3bH6TEX1WeUmdSWXa2pJfmuLc3NJQow4EIAABMwGmh82M mlCijd+js+uBTPqX4icCN88nrrqi1sjI6HGzwvrtRebDCzlXa7LtPk/XK7o372qFd18WX9OhnkAW zKTjerAWNzc7mG28SdgRojQEIFA3AtzXsnmsHd+j+4tSBouxLA9s1dO9eZbxYuBlAHsvl7LcPIBo +7mVR2bX20U0vdGp3N0cfOhSONvaiurhwvpm8ePHDw+4fu6BVzIC8ErGiVLVIGDqr00729r2jGfb s61N8k3X8+oVpnZtr+elZ1PlmsZZ1eyum76u+JF5dECyHb+UHIBCBAQgAAFHBNqa4Wur3Y66DWIc EahU8Ni0QdE0exz1uS9iopzglhdp5EKgOQTa+qO9rXY3p+c2w5JKBY9VHxS2QU3V7alKF45ygltV PIMeEIAABIohEPf9avu9G2ibtl4x1ta/lUo981j1ZweyPtOTd3cJnr3Mux1X8pM+I+aqPeRAIAsB 0/0paX+2fWbOdN8JbMoq17Z+lKVJT1v5tuWz+DZc17ZdU3nX92VTP3TFoWg5ScdPUr2K4lRUO0nt LqpcpTKPRRldVjt5/xIiY1eWZ2kXAhAom0De99e09uV9X66q3Wl5Ua8eBCodPDZtUOR9E6lHl7PX smn9wJ5As2rgz2b5syrWtPX+2la7q9Lv2qpHpYNHBkVbu+W+3fSDZvUD/Nksf2INBIokkPbHJwsz 3Xqp0sFj1NTA+Wk7j1t0SIMABCAAgaoSqOr3RFX1KsqPWe1P++OThZluPVyr4DFwftrO4xZddmlZ B5FJg7zlm9qv63W41dVz6A2BHYGqfk/krVfV7l9RfVzbXzV72zIGaxU8Ns0prgdRlE8gv2mDK297 8vaL636cNw9X+rreisOVXsiBQJMIVO3+lbc+ruRnuY/qFdfhv9vb2yZ1qYO2VHqrnrgtEMpaGp/3 VhRZe1vVeJnsSbo1g2krDFM7ttej7bneasNWH1P5ssaDSa/o9aT+tpVbVHkT56T2mfqz6Xpgr6lc 3tfj/JvW70XrG9dv8tbD1I9M/dlWP5O8vK+b9I32Z1N503VX4yPpfT+rP/Pmn5f8RmQes/xiyAss cptDwNUv2+YQwRII1I9AVb8nqqpX/TzsVmPu+8d5NiJ4bIqTuYm4HfxIgwAEIBAQqOr3RN568b3C GMiDQCOCR1dgyh5ked9EopzKtrcpfnNlhys5dfdr3fV35UfkQMAFgaK/V1zojIzqE2jEM4+unlEz PbuQ9zOPpvZN3cn2mces7Zn0MV3P6xkxU7um66ZnapI+C2Nqx9V1k76u2skqJ62/s7brqr5pvKS1 z+Q/030nsM9WTtbyUa4mPbO257p+XL9w3Y6tPFN/tZVn6rem9rJeN+kb7b+m8qbreY2HuPt+2Xyz +idt/UZmHvmlZdcdXGd6XMuzsyb/0nXrX033R/4epwUIFEcg7/Gat/ziSBXbUt3u+3nTaWTmMe0v AVO9on9Z22a40mYeTXbbdsKk8vLK1NhyM2VQkv7SteXkqrxJv6T+cKWPKaNjq29Wf7qyy8Qxr/5s uu/klWkx+ck0blxnlEz62F439dOyuCbtZ670czU+0vJ03U9ccTH1p7h28uZZFfmNzDxG4db1l1bZ v3TglmyY1pVTMuvKL1X2OCifABpAAAIQqBaBVmQeTb/kkv6CMGUATL9Usl43dR3Xmcek3AK9ggxR 0npFZ2pM/Fz9Yk3ajqtytv3KVbu2clz527ZdV+VN/dqVfSZ/uuqnpnZM16Ncy74/mvQ1+a8qXE16 2tppKu9qfJB5zJtkteS3IvNYLeTptSkrw5W03apmiJLqn94z9apZdx51179evQVtm06A8dR0D+dj Xyszj2lXTVXtl7Xpl39cJiT6C9vWLtMvTNMvZ1P7pl/KWa+bhlJW+UU/o5dVXxMPV9fzysy50s8k x9Sv87LPND7LypiZ7j9lj3PTuDDdx8rimrSf5aWfaRzYXk/qB1fjJy8uScehLZ+6lm9l8Ji2E5jq mQaJ6+ummzfBo0/IdDNOyjHtTSnvm0PWfpW3fnkHEUXrbwo6svrDVD9tPzTJtb1uGjd5+91W36T3 gaxyXdc3cc67vazjy6Sf635S1PiIaycrr7rUZ9q6Lp6qkJ5Mc1TIGQ5Uqbs/666/AxciAgLOCDCe nKFstCAyjyH3mn6Zknk8nskzZTrjfkGbfpm6vm6aVi66vax3GNf6ZtWnKpk513YkvT+49ofpvlNU piWp/VUZ5yY/mPppWVxtOZvszHo96zgytU/mMSvhcuoTPBI8xk7rxgWDpi8z083P9c3CdHMyXY/7 ssvry8P1UDfZZ3vdtX5F+ztv/U1Bhy1v2/J59cu0esTpU7Tfs+pfFa6m+6etnVnLZx1PpvZd95Oi /Gjq91m5Vb0+09ZV9xD6QaBgAnWftqq7/gW7m+YgcJQA48ncQXSAHP67vb01V6p5CTKPZB7JPEYG semXctbrpmlz23tKVn1M9W31KTszZ8rcpLXHJDdppt7E23S9qMxKUj1MGZiiuJj0NfmvKlxNetra 6bq87fgxtU/m0ZZoNcqTeayGH9CiRQSquh9mi1yAqRCAAAQgkIEAwWMGeFSFgAsCVZ8Wqrp+Jh/U XX+TfVyHQJEEGE9F0q5uW0xbh3xjO13gOt1uSu/b6hc3XWTS23Q9Tg9Te9FhUJXprDi9yprGsr1d 2PabrOVt9bPtT1n1M9VP+9hA0vFnaj/r9bL6ZVL7qzrOTfpXhatJz6z9x3V90/3A1J7r+0NRfoxr x8SjKdfJPDbFk9gBAQgkIsBjA4kwUQgCiQiQiUyEqXGFCB4b51IMqjuBqt+Mq65f3f2P/hCoEwF+ jNXJW+50JXh0xxJJEHBCoOo346rr58QJCIEABCAAgVgCBI90DghUnEDVM31V16/i7kU9CEAAArUj QPBYO5ehcNsIVD3TV3X92tZfsBcCEIBA3gQIHvMmjHwIQAACEIAABCDQIAIEjw1yJqZAAAIQgAAE IACBvAkQPOZNGPkQgAAEIAABCECgQQQIHhvkTEyBAAQgAAEIQAACeRMgeMybMPIhAAEIQAACEIBA gwgQPDbImZgCAQhAAAIQgECxBPQRjOG/29vbYhUooTWCxxKg0yQEIAABCEAAAs0gsF6vJfz38PDQ DMOOWEHw2HgXYyAEIAABCEAAAhBwR4Dg0R1LJEEAAhCAAAQgAIHGEyB4bLyLMRACEIAABCAAAQi4 I0Dw6I4lkiAAAQhAAAIQgEDjCRA8Nt7FGAgBCEAAAhCAAATcESB4dMcSSRCAAAQgAAEIQKDxBAge G+9iDIQABCAAAQhAAALuCBA8umOJJAhAAAIQgAAEINB4AgSPjXcxBkIAAhCAAAQgAAF3BAge3bFE EgQgAAEIQAACEGg8AYLHxrsYAyEAAQhAAAIQgIA7AgSP7lgiCQIQgAAEIAABCDSeAMFj412MgRCA AAQgAAEIQMAdAYJHdyyRBAEIQAACEIAABBpPgOCx8S7GQAhAAAIQgAAE8iLQ6XQk/Hd7e5tXU5WR S/BYGVegCAQgAAEIQAACdSOwXq8l/Pfw8FA3E6z1JXi0RkYFCEAAAhCAAAQg0F4CBI/t9T2WQwAC EIAABCAAAWsCBI/WyKgAAQhAAAIQgAAE2kuA4LG9vsdyCEAAAhCAAAQgYE2A4NEaGRUgAAEIQAAC EIBAewkQPLbX91gOAQhAAAIQgAAErAkQPFojowIEIAABCEAAAhBoLwGCx/b6HsshAAEIQAACEICA NQGCR2tkVIAABCAAAQhAAALtJUDw2F7fYzkEIAABCEAAAo0lsJKns+DoxGuZObQzU/D4+++/76kS fe9QT0RBAAIQgAAEIAABCCQksHq6ktHp1Ds6cTleyODaXfhoFTxGg8OfP3/umRB9n9A+ikEAAhCA AAQgAAEIOCOwkreXuQwvzj2J3e+X0p+8Oss+/ru/qVdSXf/5z3/KX/7yl23xP/3pT0ffJ5UblDPJ C64nLZdUbly5qP7RdqP1XOtlkmfSL46XSW/TdVsOcf0gL3+auMXpn7S/2Mp3XT6p38uyp+r+Nvnf pL/pumt/m8ZbVfxs0jNvLrbyTX4si6upf9raWXR52/uT7feNyZ6i/Ba088cff4hFGGUbFmUo/z/l v//b/5GTv/03+Y//qsT86/+T//XH/5B/+S/6/UyuO/9V/rf3b91E+L2e6v738p/+7Q/Rtv3f//A3 +c+9r2p0VDpznUE7qkIAAhCAAAQgAIFWEjg/P5e///3vRtv1zO3Dw4OxnLsCOiB8lYv1L/Fzj/r9 vZws3+WmG/535NryWjqvF7L+5deKeyWetv7x44d0OsGDl/wfFvQB+gB9gD5AH6APtLsP/PnPf/ae KTT9FRs4BiHfQj5XluFo70RNbw/k7Ol4xdIyj3rAuUx6Is+yg0SKww9+NgToLza0Dkz5cP/LBJD+ lwmflwji+zc9Q9f80mtyrKaefr4SedaZRlVu9SRnvQ+58zKRRzKPuqxX/Ex6I/XM5HQth5KQiTOP +RiHVAhAAAIQgAAEIAABtwS6otbIyOjRX2G9enuR+fBiM4Xdk5P+XD6WmxZnrzKJNN69eVcrtPuy iEldEjy69RbSIAABCEAAAhCAQOkEujfPMl4MvExz7+VSltsUYldu7oYyGWweOXgVGQbaztQzj5tH FHujU7nz0pZfX0xbx7jXdVoaednGEfzgZ0OA/mJD68AXA9OamQDS/zLha920ejZa5dQuLfOoF+C4 fLVNnkt2Wlbb+Lm2F39kI4A/qsUPf+APGwKu+0sz5ennDPcXF5kWpcT7QMs6E8OaFhsXWpctLfNo rSkV9gi4/mUL3mwE8Ec2fq5r4w/XRLPJwx/Z+LmujT9cE00iL7pIJUmduDIuZaXTo7TMYzp1qQUB CEAAAhCAAAQgUCYBgscy6dM2BCAAAQhAAAL1J7Baie2Witro2XVHdkdOR6aj9fY6wUX9782099nT Z+m8CB5LdwEKQAACEIAABCBQWwI6sHtcyuF1yWGr5jLq7Z571HHh+YVa9fzqb6cjasucRV/k5c0P Q/X2OnKizwZUQWVvJKdqz0W9P+ezvHzZWqdodgSPRROnPQhAAAIQgAAEmkHA23x7JHN1Ksvh04au VegXvPoyXu5Oo/F2ztEnuiw+vazl7HUhl3dqc8aXN/V+JTp2vPyuQtLVpwoqx/Lb5sTA7s3dbmud kigSPJYEnmYhAAEIQAACEKg5ge6NvC/HMhwvY44oDM6WjrGz+10uVSbxbTWT18WlfD/X7z9kuXpT n6r35nRmKQAJHkvBTqMQgAAEIAABCDSCgAogf/u2TPXMo6jJbn0SzMvVvSwuv6t3+v1CXh8/dNrR nwrvfpPT+Ug2h8WoowPvmbZuRMfBCAhAAAIQgAAEWkuge36e4JnHw3i6Onqcb6aodayo3i8magp7 m3Y8l1/T3YkwVyojuT0RpiTi7PNYEviszbJPV1aCbuvjD7c8s0rDH1kJuq2PP9zyzCoNf2QlmLW+ XlU92MseDtVimO3pgVnFF1CfaesCINMEBCAAAQhAAAIQ2BEILZ7xsorhhTXV50TwWH0foSEEIAAB CEAAAk0lcH6hpqEX8plmo8iSmBA8lgQ+a7Ouz/7Mqk/b6+OPavUA/IE/qkWgWtowPnL2h+2G4Wp/ x0k/tLI6tCF4p6Mzkit5OgtvJq70n11L5+wp5SKd7PbzzGN2hkiAAAQgAAEIQAACak9GvWH4N3k/ +gBj5JnH4VTW2/KRc6tVkHj2+Zu8f3uUzuvFtpw+meb1orznJMk80tkhAAEIQAACEIBAVgJpNgxX e0T2J6+7jcT1huBq6fX2JJrBROYfS30UjQy35fSekLtNw7OqnaY+wWMaatSBAAQgAAEIQAACYQJp NgxXdZ7HC7l/Cj/wOJSpOoZQH0Xo/XlZyXP5bVNO7/Po7wlZ3ovgsTz2tAwBCEAAAhCAQJMIpNgw XB83eDq6Ei9+1BuCq0189oNJH5C3H+TLozy+nMrdTZmhowjBYyU6rf8wrH8uZsxy/b0HaFW57YOy CepWwsaaKqEfSu6c+YPa+MIXRkRpC5j8wPhISzZDvXB/jzzMf1Aq4yMD7CNVE/iB8ZEP+hip9huG 66yiyOhKL4BRG4KrqWw1b707K/t6czq2d5ThRCanF6pUuS+Cx3L5e62vnq5kdKoemFXp6aVKSw+C jvJFt1Aq+/3GS1knr1sBQ2ulwuaG/CqJd/LHF3k42MYPjI88PBArc/Ym8ryZVkuwTx3jIyfvJPYD 4yMnD6QQqwLE9buEk4fdm3dZb77XRU9/f5m21s105eY9mMZO0azDKgSPDmGmE7WSt5e5DC/83xE6 Lb338OxRoVnqptO2PbWCQXqR0GR8kRCUZTFbP4TF4xNL2HbFz292X37GferwhR1ci9JWfmB8WJCl 6BECBI+ld4+lfMz7ctLbKOI97xC3WehEBt7UdjCNeqxugqmM0m1vkgL4onxvMj5K84FeIRrep+6L IoyPQnxz1A+Mj0J80JJGCB4r4ehT+WZ69jWUxvYfhwiejYypO3vcToXr6fA6nZlZCZekUgJfpMLm ohLjwwXFlDLUD9WrkZze+Y/SxL8YHykBJ6x2xA+Mj4QMKZaUAMFjUlK5lrM7lkivzNodZRRTt3ei pr8HcpZspUeu1rVHOL6ogq8ZH8V6YXbd836omn+gMj7y9ExSPzA+8vRCe2QTPJbu656c9ENKeBuE JshEelWO1N380nyWK2/FVuwanNLtb4oC+KJ6nsQneftk9XQmAwmfjhHXIr7I0xfJ/RDWAp/k6ZOm yyZ4LN3DXdFbN40e/aX4q7cXmQ+DZfj6mKKv28TMrgebczCP1fUN0yu4luO+LOp04nrpPjEpcMgv +MJEzf11xod7phYS1fZJvZdLWX5JOTI+LChmL2rlB30kMt8f2aEjQW8Pw6t0Asu1iu/WqjuupT9e L7f6TNdD6a/Hy9D1L2Vi6k6Hvjzvb7hWu9XzsiIQYb7HPfBLVCC+sEKcqHASPzA+EqF0WuiAX9QY GXo3GsaHU9RHhSXxA+OjOH+0p6WONpUYGgIQgAAEIAABCEAAAkkIMG2dhBJlIAABCEAAAhCAAAQ8 AgSPdAQIQAACEIAABCAAgcQE/j/xBF7k79kK8wAAAABJRU5ErkJggg== --047d7ba97b72c4ced304d6c73540 Content-Type: image/png; name="no_net_protect.png" Content-Disposition: attachment; filename="no_net_protect.png" Content-Transfer-Encoding: base64 X-Attachment-Id: f_hdpttjy31 iVBORw0KGgoAAAANSUhEUgAAAoYAAADICAYAAAB1RyBMAAAAA3NCSVQICAjb4U/gAAAAAXNSR0IA rs4c6QAAAARnQU1BAACxjwv8YQUAAAAJcEhZcwAADsQAAA7EAZUrDhsAACnASURBVHhe7Z07byNL lqCPZq12Z/8CWYYgo73ZpdpoVywsIEvWABpgB5QpOhe4AmT0BQSoCuVQZtFZyBXGkCOp3TZEYNcW ZBSJXXPN/QnciHyQyWQmIyMz8v3lhXBLyogTJ74TkXnyxOtorS7hggAEIAABCEAAAhDoPYF/6j0B AEAAAhCAAAQgAAEIeARwDGkIEIAABCAAAQhAAAI4hrQBCEAAAhCAAAQgAIEtASKGtAYIQAACEIAA BCAAASKGtAEIQAACEIAABCAAASKGtAEIQAACEIAABCDQPAJvV3J0dCoPq6hqK3k4PVJ/1z9X8lai 1gwllwgX0RCAAAQgAAEIQCAbgcD5exaZxDKsHi5levIqeofB5exDxlfluYY4htmsRSoIQAACEIAA BCBQIoGBXL+vZf3zPO4WysvTQibnZ97fB18vZDR/Li1qiGNYookRDQEIQAACEIAABIoRWMrnYiTH w0DK4IucyIf88oaa3+RKDzu/PcipN8x8JDqYuHo4DYadj+R0MyYdHY720yVdOIbFrEVuCECgZwTe rtTDt8RhnJ7hpLoQaCyBv/71rxvnyp/bl/xzc3NTQR1O5MsgrZiFTO9EHtUw8/p1IvPxkVzKozfs rH9fTH/40cW3H5vhaH3vpx+A3LtwDCswJ0VAoHkE/C9H/Btby7zJ81zN//GGdFwwjHzBnz4oifpK +putnqSHAASKEvjHP/7hO1eGn/v7+6JFZcgfRgiTko5k9ngtnt94dq7mJ47k4mvgRXq/B3mHx2oI ehyJIOIYZgBPki4T8CI96otvG1b3a+uF3HN6SK5kFtGhbJuFddx+LRdfEeeyvkmyPJ03jpZDQm/P Mh/N5LeUL23rkvQX/GIir/rF8x482JP+Zi1YBQfKYpBDF7JAAAJFCAzleBTJv/qlXL1DEcSUsgbX 8q6eNY8qnhgOOSelJGJYxFbkbR2B0Wi0Das70r4MmY5UcyZmNFtuvpq9FXElb5dQVPGznxFHq6iw SP43FS4cXXz1v8xdXaNjCacObUQm/c2yvLIYWKpBcghAoDCBgaj1JjL94U8KXL08yWJyLnm/TwfX 72pl80g+/EmKexeOYWGDIaBVBC5uZTaaG5b6707QNe4ZVUimX9ZwuhA1MWQT0dyLgnn7WkUjdXrC cXQo+JDOweTkBy0jZQ+sxH2zki07uL5VQxNzefYnrfgTn/dkp+mTXF+/JAP31XZytf+1my5rfx7g IdnhkLDP1GcU30PMr+vzPDJEs8GTli9hqFlzDiKZno3Halx6MZWhLlNFrZP+ZmaTbINdBhnq6LWB 2ByqnJH0Vj0TUBYCjSEQPqfG6gmr5g0OtyMfg+tHmX3474jh04Us0yYIHqpLpI8Ppydye53yiavG zrkg0AsCag7uWkW+1uvlbD2S0Vr/U1/qy2ktEzWY5/+2Vh9Skd+D+zJZhymisLLJXOv5v/syRzNV WpIOnlJKx22Zy9lkrYKd662a0fsmnV/Xak+stZoZF6mDn8eT9zpR97Y84o1hU8fwxg6/dNlbpvsM d5n7gg8z8svx7OenXk8CfmZZJj7B/QiDuC6BgmuJ2GzTVuJtacM5wjhkp1lHZcR/90HEysnGZte+ 8TymOmq+aX2iF48HKgmBPQLKx+olFSKGjflSQJHKCKh5FrcT9TV2GU72j5S8epEnPecr8jXmR8gO TfxV+Q/KfJA7FWmaRSameTIXT/KSHMlX8vR2BGFUbqX2sBK5vVVaBKH/naGEjDpPXn/uDz38UlG4 8YfMlu+S9vEYt8vbj6ksRhcSzm3W93dkZ9RnR66KBh5kpOf2KStsv3DP5Gc4J8/UcDLqM3ndMjg7 V27ox69gMUgQzbxLHkaO5svUVkz6xu+b2ATpE+0bk5Vax9icpcGXk1j9bZUmPQQg0FYCOIZttRx6 FyJw9vNVOWZTudw9c0hk+akC+PFLT/xdyOfycJGpMr1swbDAZqhODxUcus7E902056j2sDpR80nU ijJ5elHOinYUt5udFtF5PlVOXgaSi+lwM8w4/pjJ8pBTlpuhgVHeeXe59Yl/MCQNIyfBM7eVDMhj SWzbj2UJO/uiqUFzvfT65IvbuZSWKpEcAhCohwCOYT3cKbV2AiriFOzv9BLVRS/n39Mttrloqu4p Mr30wcrTnW0PDkfpdNRqoR1BFS370DubDr7Khegoo9ZnIsEm+CIFdFZDyWoSsprUnBQ9jdQzuvhk s3o2jUNufQyMFp/KRc5x5dZnW5Yfob3NGFWNbESbQ93kLPbtx6poL2K4dT7H892ouZUsEkMAAq0m gGPYavOhfCECZ795C1GmeuFHeGnnK7Y4ZfVwp7Yo2R06TfcN02XexaOTcSE7Q5fqpt5/Sg03/3hW GxN4O5sO5MuJikb9UMOq0RVpBXX2JjWLWgDhaqFBVn2i9Q3ypDLy9uKay/a+WnAR3Y4mzi7KNqs+ qUaNRWhj6ebj7UKV3bai7aXWFPmrdPS+SGrY/nCcOFEFE5tCnSDIrKOqE/8cVv8nYdqBi3KQAQEI NJ4AjmHjTYSC5RFQ51I+zmIRQn1WpRpmDlYIb1aAZZ3Pppy3ZJlLuXjaDsd6qz8jjo139mWwOnW7 z6IeTl7IfH6yiQ7qKOJ8rmbbbcKFmo4DnYM6x/d4zMferM9+fXWeQ4xUNNYLbYYM7+Q42NA1md2O Z1jMpsEcxR3kG/Fq7uiriuPq1YN6taBa6fcaaSve9IKwLQ0/5VZFqe0vExt7iXs5zn7Kq/grHjc/ ZewD6UBVREAAAuUSONJLbsotAukQgAAE2ktAbyEz/LxVB9vn3TWs+XX36qi3wIg4tXq7m7vjpbxn XZXU/GqiIQSsCOiPpD66SEQMrZoJiSEAgX4RODyM3BUWy081nWJnsclKfn10pXbUAwIQsCFAxNCG FmkhAAEIdJKA3lh3qI7n21ZOLzgiWthJY1OpjAT6GjHEMczYQEgGAQhAAAIQgEB/CPTVMWQouT9t nJpCAAIQgAAEIACBgwRwDGkgEIAABCAAAQhAIIFA/Pzwm5ubznNiKLnzJqaCEIAABCAAAQjYEmAo 2ZYY6SEAAQhAAAIQgAAEOkWAoeROmZPKQAAC5RPQK3iPxNVBMb6+ZcgsnwQlQAAC3SOAY9g9m1Kj VAL65bs9vkxv4Ov25Q76QwT0JspHAK+9kdRth7rLr90AKACBhhPAMWy4gVDPJYGlfC5OxDt2WEVo fn2M5HjoUj6yXBIoxYF4u1JHvl1JcHqxlbql6GOlQUcTF7BJR4lQLQjUSgDHsFb8FF4ZAe/lM5a5 +m/snQerN/NdqKN3dQTxTa6O1P8fdBp9L3Qc/OG97aq0qEMRRh913jCNvh/Ns41OJg4Vap0i59F6 jsdGVjSvLaVwWDKqW1zeobollVdEpp93qHdPDs4NPnQmc8jhUh69Y+h0ZHc30ujL82VY2kGdCbxe n8vzjp0P843rs019gO/qQU4j5w7vBEoP3QuFe+01tFnCMPNO20likNR+DtghVaeUvuHpF+0bURul ta2U8nPYxLZHkB4CELAgoM9K5oJALwi8TtYymq2XurLL2XoU/nv9up6IqDPDJ+pf2+t1ov422f5l ORtt8ysps1E0T/i7rMMsSekj4tbruD6x8vPbJNRltJ55ldVFResS3I/X7WD5JpnxMjTiKK/g9x0A uzX00ms7xNNoTlHdtO0krJutHSJlenL27R6mSNVnY/stXz9t2H5Ue9q0rTgHv62pU0WCYsK0fj28 qnv13cpWErb3QuWibceoTwLn3YZo1He3b+g6xOoekXe43xjagcEm+fsEOSFgT0A/j/p4ETG0cKJJ 2m4CK334a3ge7PJTIqd/eRWbvP6Us7CKKoJyNx/J7LfNX2RwfSuTxZO86EBVcG3zDOTrhXIzJq+i glzeNfhyIrL4lGVmbHN5zjPGmSJ/8vou196wucjZuXJHPn6p+Jq6Vi/ytJjIa6io1lXXTT7kV6Ru SWLTZWbjlYZCR+WGTxei3CUvSrhznZ0r3bZsVi9PshhdyNegbru2s7DD4FredXmvoqLIu8PLB/XZ 2H7Ld5ffmfx8v5ZQvcHXCxmF7eDtWdVkIrehYVSLi6aVXyrSOP6Q2XIrO2vzidomqz2D1pGu7147 1+3nl2op4ZSMoJ1v2laxdqAaYqpNsnIgHQQgUIwAjmExfuRuCQE9HBkdyjwaz5XTNpVhZCh3vyp6 qDk6XKaHoku69AtxOZOPsV9e0lDr7lCz78gk/c2oYYJTLDKU49FCPpUXm0umV2h+XoPrd1lePMlQ D0/uLVA5E+3Xzj2veSUvTwuZ3G4dL2N9071Rf7h3LPK6jnwUeI7yIX3SBPr89LXDcDjd/QgZHSva ydd8Gkubu3K+PUJ9TGIO6hvPPPii3MLtR8Tbs+oV4QdXwXagwKXaxFQH7kMAAm4I4Bi64YiUhhM4 +7kWNcSlRyn12ICooT81qryUdSSys18FFVXTEaWdH/tITmY0YbREhbBOpsO9FdPaWdnq4jsySX8z ljc8FhXbjF16YY6/GCeXTE9aMV5hucvjuz3n+Oy3mYzmz/IWRDvPY0FFY513EgRzA4efcuvZdtcp DJMe0ie5vGAxk5p/N5yebNuOcvh3eB+IIuv2qZLL9PLBj+4WujIurjLpG9fBixhuPwLG893oc752 kM0mhXCQGQIQyEQAxzATJhK1n4BehbytxfJzoYIckbHIeAUHX+ViNJc7b4GDi2sgemTZj3qpS0dG dNQy8dLROxdlpsgI6jaOROZWD3cyjw3PWmmQlVc45HhAeOiQPcrlNnoYyr9Uw8iT8+2Qv5WSKrG3 aOJZzg84hHtNIXDId/RRiebj7QKPQ/zefkSigMGw+LZdKYcoFrUeXD/KTFQ0e2OfbG0nqz5e/Q7Y YUffJL464qymTMQ/UrykedpBDpvYmp30EIBAdgI4htlZkbL1BMIIyq6TmFytgVy/L+Xiabi7+vLg 0PNhQGc/X2USrMo90tEqHcIMr51VnmrF9Ml2rqJ77LpuEV3UcKo3v+9g9NSkhZmXP9dOOTwpQ+WJ DtlmvqE/d3ChVpJPioQLvRWwyRFCYw21g7jRR80/fb2Qp2CqgRchDPmpMl4n4er3I7k7nqlYanip OYVeSDBsV3dy/BgfFt/aJ5xScLDtBKInr7fymaRPrGJ7djiobwIVnV7GKf0iRzsoYBOTzbgPAQjY E+CsZHtm5IAABCDQIAJ6G5ihfN6uNwufylRuszAn8iGh5/DeHS/lfbOopkwNkA2BaghwVnI1nCkF AhCAAARaTEBPw9hdbJIlAt/iCqM6BHpGgKHknhmc6kIAAhAoQuDs51JmH9Gh5KE8XRAtLMKUvM0l EN/I/ebmprnKOtKMoWRHIBEDAQhAAAIQgEB3CDCU3B1bUhMIQAACEIAABCAAgRwEGErOAY0sEIAA BCAAAQhAoIsEcAwdW/X33393LBFxEIAABCAAAQhAoBoCzDF0zLmvcxIcY0QcBCAAAQhAoFYCfX2f EzGstdlROAQgAAEIQAACEGgOARzD5tgCTSAAAQhAAAIQgECtBHAMK8LP3MOKQFMMBCAAAQhAAAK5 CTDHMDe65IxpcxL6OlfBMV7EQQACEIAABCoh0Nf3NhHDSpoXhUAAAhCAAAQgAIHmE8AxLNlGDCGX DBjxEIAABCAAAQg4I8BQsjOUvqB46Dn8va8hacd4EQcBCEAAAhCohEBf39tEDCtpXhQCAQhAAAIQ gAAEmk8Ax7D5NkJDCEAAAhCAAAQgUAkBHMNKMO8XwtzDmsBTLAQgAAEIQAACqQRwDGtqHN+/f3da ssnRNN13qgzCIAABCEAAAh0goOcZRn9ubm46UKvDVWDxiWMTZ1184npSa5o87RB++/Ztb1GM42oj DgIQgAAEINApAq7f022Bg2Po2FJNcwxZFe3YwIiDAAQgAIFeEOirY8hQci+aN5WEAAQgAAEIQAAC ZgI4hmZGpIAABCAAAQhAAAK9IIBj2BAzd31xSNfr15BmhBoQgAAEIACBQgSYY1gI337mvHMMi85l SMvflDmGRevn2EyIgwAEIAABCBwk0Nf3FhHDnnYMIng9NTzVhgAEIAABCBwgQMTQcfNoS8Sw6i+h qstzbFbEQQACEIBAzwj09b1FxLBnDZ3qQgACEIAABCAAgTQCOIa0DQhAAAIQgAAEIAABjwCOYUMb QtfnAHa9fg1tVqgFAQhAAAIQOEiAOYaOG4irOYa2cxtsVyXbyi+KKY1LKDc8uq9oOeSHAAQgAAEI uCBQ9XvShc4uZBAxdEGxAzLqjuB9//69AxSpAgQgAAEIQKDdBIgYOrZfWyOGZX8ZmSKGZZfv2MyI gwAEIACBjhPo63uJiGHHGzbVgwAEIAABCEAgHwHtHEZ/bm5u8glqUS4cw5YYq+6h3pZgQk0IQAAC EICAMwLr9VqiP/f3985kN1UQQ8mOLVPWULIppF108YlJflFMDCUXJUh+CEAAAhCokkDZ78Uq62JT FhFDG1qkrYwAEdLKUFMQBCAAAQhAYEMAx5DGkEigbseMVco0TAhAAAIQgED1BBhKdsy8K0PJrkPo tkPJrst3bGbEQQACEIBAxwn09T1ExLDjDbuq6tUdYayqnpQDAQi4I8Bzwx1LJEHAFQEihq5IBnL6 GjE0fVkRMXTc0BAHgQ4QMD03OlBFqtBiAn1tn0QMW9xom6B6VV/8VZXTBKboAIGuE6A/d93Cu/XD 3u2yNxHDFHvFz+7NepZv3yKGYX1NX1ZFI4Ym+e3qdmgLgX4TyPrc6Del7tQ+/vzO+j6tm0Bf3ztE DFNaXnxVbN9XyfLFV/cjivIh0H0CPGe6ZeM0e/b9fdp0KxMxTLGQKcKVZtiuRgxtN9CO8zHxtL3f 9I6FfhCAgEhaZCgtYtjXCE1X20pWOzc1gtjX9kjEsKs9knpBAAIQqJkAkaGaDdCS4jvXTlYPcho9 Y/n0QVZ7tljJw2l4DvOVvG3u2/7dvZFxDN0zRWIFBBhyqgAyRUAAAhCAQE4CE3kNz1l+v5ZBTMrq 4VKmJ6/eOczL2YeMr3zX0PbvOZU7mA3HsAyqyCydQNlfmDiepZuQAiBQOwH6ee0m6KkCK3l5Wsjk /Myr/+DrhYzmzypqaPv3cvDhGJbDFaktJ1C249lyPKgPgU4QoJ8304zdcNjnMvaGk0/lYW8ceSmf i5EcDwP+gy9yIh/ya2X7d53/Ta50GW/b4WsdfFw9nKqy/aHq040C0WHqIwmClHuNAMewmf0CrSAA AQj0nkDVDkLV5fXewCkAsjrsVdgrdK4O/f/m5ma3JoNreQ+GkZczkekwOocwTHoiX+Ljy94t27/r PAuZ3ok86jJfJzIfH8mlPHrD1Pr3xfSHP4fx7cdm+Frf++kHLHEM6YgQyEOgigdQHr3IA4EuE8jq ILhiUHV5rvTuq5wq7OU5V4af+/v7VBMMrm9l4kUD40mS/qbT2P5d5xnJ7DGYx3h2rsobycXXwOv0 fg9kDo/VkPU4EkHEMexr3+lFvct23Kp4APXCUFQSAhCAQEkEyn4PuFN7KMejiLTVL+W66Uih7d8t NQoimY8qnqgjoAwlW/IjebsI4Lg1217teWA3myPaQaCPBLI+P5r4Hni7Gst8dCF+AC+YD7gaiFpv ItMfwUrklydZTM7lTK1dtvt7vtYwuH5XK6FH8rEfxvQEdmaOYdaGkw8juSAAgSIEwgc2/bQIRfJW 3X6qLg8LJxOwdfjqtdvuAo/xx0yWCdvVDK4fZfYx9iJ3w6cLWQYT/mz/btVm3q42C1KG0xO5vU6c 5CidOfnE9VmMppM40ozBySfJZEw8Xd+36iwJiU36FJXft/ycjds3i/v1tT0xydTvXJ9EUXV5fWsF WU8+yWuHrO/bvNxdt7e8elSdrzMRwzg42y+MqsFTXrsJ1PtF2m52aA8BCECgSgI8r+1od9YxtMNA 6q4RKPtBwIeHmxZTtp3caIkUCECgzQR4XttZD8fQjhepW0Kg6w+CrjhUXbdTS7pLa9XsSj9orQFQ vJMEeuMY8gDpZPvtbaW66lDV3U/rLt91g+5afeqeMtR1nq7bH/LaSaCzi09Mk1lN5sqbP+tkWJN8 0/24/mVP8raVb9LPVD/X9032LqqvfmF8+/bNtpjc6V0vtsqtSMaMeSehZxTvLFnXJpvXXR/b50bR fm/bEKouz1a/ePqqnzNF9c3b7012CfXK+77NWq+6+09WPV2n603EMKmDuYaJvOYSKPtLv+4IXt3l N9fyaBYl4LofuJaHtQ4ToJ/TQqog0FvHkA5WRfNqThnYuzm2aJMmXXN88vaDNA555ZXVBrpmLxOn vtXXxIP7bgj01jF0gw8pEGgmga68MOquR9Mcn7paW1s4VK1n09pn3frU1T4p1y0BHEO3PJEGAY9A 3Q/o+Auybn3yNouqX/R59Wxavqz2zpquafVrij5Na59N06cpdkIPOwK9XXximlSadfJrHHfeybCm 8mz1DfWqavKvrX629XWd3jSJ23V5dt3SnLqofuYS3KZw1Q7darUvzcS17PJdyc/LO6180yKSvPlM vIveN/EsKt/03DOVb3vfVl9b+a7T522HpnrG32+277us9dR6xC/97ri/v88qopXpiBi20mwoXZRA 37+siRTla0Fw87m1hUNb9MzXGovngo+Z4Xq9luhP151CTQTH0NwuSAGBzhFo61Bz3S+yrn9QZOXb Fg5V65mVX1UPlDR9wr9XzaeqelNOMQIMJafwyxrKjmdnKDkZqIln3fez2tE0hJF23zR0bduNy+Zl q48pfdlDSqbys9635erariY9s5bnirepvZuGUk1D0La8i6Yvu5+beJjsa7rvqv5p7cNUvu19V+3Q 1I7i7dTEKWs9yrZnVj2qTodjiGPoETB1JFPHNHUgW/lVp2/bC6NsPrYPIpPDUvYLwlbftPRFubrS I6t+pnSu6pP1g9fUj2xf4EX1r/u55Lo9FOVh4l+WvkX1Nr1/TPUytQNTP3LNpenyGEpuuoXQDwI1 ELAdEqtrSMpWz7JRVq1P1eWVza9r8ttmn7bp27X20pT6EDEkYkjEMKENuP7CjcszRdhMD4iy9TN9 Ycf1N6UvK2JoKtfE0RThKsrZtnxTepM+tpETW3km+SaepvwmfYreN+lXVL4pv8m+pvsm+ab7tvxN +pjul9Xv4/Uoq16uny8mXk25T8SwKZZAj14RqCvC5gpy2/V3xQE5EOgyASKIXbZuet1wDPtpd2oN ASsCbXlBNE3PpuljZXQS955AW3cv6L3hCgLAMSwIkOwQcEGg6Q5EWyKEaXrWxbct3Fy0YWSYCdTV Ds2aZUtBe87Gqe2pmGOYYsGsczXi2bOu3jPJN903lRver2qOh2kuhqk+dd838axaP9ODpWp9bMtL 42krp2j6eD+om6upfNN9Ew/X/T6NX9pzxdSPXOtn4tH055LJ3iaeeevv6r1g0t9VOWl2zPu+Nelt +9zIKq8t6YgYtsVS6AkBCBQmUHfEpu7yCwNEAAQg0HkCOIadNzEVbCMBHIhyrFb3UFjd5ZdDFal5 CdDP85IjX5kEGEpOoWsK0acZJW9o21Se7ZBI2UM2Jvmuh0Bs+dimb7q+Tdcva/u0tUvR9E1vp7YP dxMPU31N+YsO2ZnaqWv98tYnrkdTfje1B9v6muzpSp7pfVi0HFM9bNuViXNae8iar+3pWhcx5Aur 7U0O/SEAgZAAzzPaAgQg0DQCrXMMGYppWhNCHwhAIC8Bnmd5yXUzHx8K3bRr22rVOsewbYDRFwIQ gEBWAjgGWUl1Mx0fCs2zqx7Gjv7c3Nw0T0nHGrVujqHtXIO0uQJZ50Sl5U+zA3MMk8m4nmPiWl5c a9fyi8prun5Z+1NRDrb54/03q55Znxu2+timt7W7qb55y8/6XDPp61q/vPVpin1N+pt4mvKb3pe2 +U39J03fouWY6mHbrrL6Ubb1zSq36emIGDbdQugHAQhAAAIQgAAEKiLQGMeQIZSKLE4xEIAABCAA AQhAIIVAYxxDzmSkjUIAAhCAAAQgAIF6CTTGMYxjYBJuvQ2D0iEAAQhAAAIQ6B+BxjqG/TMFNYYA BCAAAQhAAAL1EsAxrJc/pUMAAhCAAAQgAIHGEMAxbIwpUAQCEIAABCAAAQjUS6B2x5DVyPU2AEqH AAQgAAEIQAACIYHaHUMWmdAYIQABCEAAAhCAQDMI1O4YNgMDWkAAAhCAAAQgAAEI4BjSBiAAAQhA AAIQgAAEPAI4hjQECEAAAhCAAAQgAAEcQ9oABCAAAQhAAAIQgMCWABFDWgMEIAABCEAAAhBIIHB0 dCTRn5ubm85zwjHsvImpIAQgAAEIQAACeQis12uJ/tzf3+cR06o8OIatMhfKQgACEIAABCAAgfII 4BiWxxbJEIAABCAAAQhAoFUEcAxbZS6UhQAEIAABCEAAAuURwDEsjy2SIQABCEAAAhCAQKsI4Bi2 ylwoCwEIQAACEIAABMojgGNYHlskQwACEIAABCAAgVYRwDFslblQFgIQgAAEIAABCJRHAMewPLZI hgAEIAABCEAAAq0igGPYKnOhLAQgAAEIQAACECiPAI5heWyRDAEIQAACEIAABFpFoHTH8Pfff28V EJSFAAQgAAEIQAACfSVQumP4/fv3vrKl3hCAAAQgAAEIQKBVBEp3DFtFA2UhAAEIQAACEIBAjwng GPbY+FQdAhCAAAQgAAEIRAngGNIeIAABCEAAAhCAQAKBo6Mjif7c3Nx0nhOOYedNTAUhAAEIQAAC EMhDYL1eS/Tn/v4+j5hW5cExbJW5UBYCEIAABCAAAQiURwDHsDy2SIYABCAAAQhAAAKtIuDMMWS/ wlbZHWUhAAEIQAACEIDAHgFnjiH7FdK6IAABCEAAAhCAQLsJOHMM240B7SEAAQhAAAIQgAAEcAxp AxCAAAQgAAEIQAACHgEcQxoCBCAAAQhAAAIQgACOIW0AAhCAAAQgAAEIQGBLgIghrQECEIAABCAA AQhAgIghbQACEIAABCAAAQi0j8BKHk7D4/qu5M1hBawjhuxX6JA+oiAAAQhAAAIQgIAlgdXDpUxP Xr3j+pazDxlfuXMNrR1D9iu0tB7JIQABCEAAAhCAgDMCK3l5Wsjk/MyTOPh6IaP5s7Oo4X/6m7ps dP3Tn/4kf/nLX/ay2P49FBDmi+e3lWfKb7ofr5Bt+nh9bOtnKi+NR1q5VZWfZj9bnrb1d52+6fo2 Xb+s7dO13UzyTP2g6Vxt9TPV18Qr63M3b793rV/e+pie1025b2t/Ew/X/E2+Q9b3u0nvou3S9HxK q8cff/whli6SCYmj+/9T/se//x85/tt/l//yz0rkP/8/+V9//If807/q39/k6ujf5H97/9bFRX/X w8//Wf7rv/8hum7/91/+Jv9tuK/SkQpDrh1pihgIQAACEIAABCDQCQJnZ2fy97//3VgXPcXu/v7e mM5dAu3sPcv5+qf4MUP9+50cL9/lehD9d+ze8kqOns9l/dPPlXZlHkr+9u2bHB2FEx35PyxoA7QB 2gBtgDZAG+huG/jzn//szeEz/VTrFIbu3If8Wlm6msNjNeQ8ltOHwxlrjRjqDuUyYIk8y0YSSw4/ +NkQoL3Y0EoYruH5Vwgg7a8QPi/Qw/u3GMP6cush4UuRRx0hVFqsHuR0+Cm3XgTxQMRQp/WSn8pw quYovq4lKXiYOWJYHwBKhgAEIAABCEAAAhDwCQxErTeR6Q9/JfLq5UkWk/NgWHkox6OFfC4DVm/P Mo9hG1y/q5XMI/lICTniGNLOIAABCEAAAhCAQIsIDK4fZfYx9iK/w6cLWW5CfwO5vp3IfBwM8T+L TMJ6vak5hsGUwOH0RG69cOP+xVDygYZAqL1YL4Ef/GwI0F5saCU8zBkaLASQ9lcIX++GpovRanbu WiOGekGLy6tv8lyy07L6xs91fbFHMQLYo1n8sAf2sCHgur00Xd4uGz2vb3cRjmmBRzpbLetUDOtD bExjnbbWiKG1tmTYIeD6Cxe8xQhgj2L8XOfGHq6JFpOHPYrxc50be7gkGl/wUUS2S1n59Kg1YphP ZXJBAAIQgAAEIAABCJRBAMewDKrIhAAEIAABCECgGwRWK7HdMlBX/O3qSLZHGMeGiPUWM+FN/e9g KPr04VftzHAMazcBCkAAAhCAAAQg0EgC2mn7sVQbxJiuhUyH23mG2uc7O1erg5/9LWVEbRvzMRJ5 evFdTL3FjBzr8+iUwzicyonaU1DvK/koT3vby5hKdn0fx9A1UeRBAAIQgAAEINB+At7G0VNZqNNC kk+4uVJuXXiNZLbcnpLi7R6jTxr5+OVFG9+eP+TiVm0++PSifl+J9gsvvip3c/VLOYwz+S04pW5w fbvdXqYmgjiGNYGnWAhAAAIQgAAEGkxgcC3vy5lMZsuUY/HCs4pT6jD4KhcqAviyepPnjwv5eqZ/ /5Tl6kX9Vf1uDkPWAgfHsBbsFAoBCEAAAhCAQOMJKOfwty/LXHMMwxNKni7v5OPiqxqO1ieWfMjz j08dLvSHpwdf5GQxleAQE3Vc3R1DyY1vFCgIAQhAAAIQgEBvCQzOzjLMMUzGM9Bn1y2CYWPtB6rf P+ZqWHkTLjyTn6/bk0ouVSRxc1JJTcTZx7Am8C6KZR8qFxTdycAe7li6kIQ9XFB0JwN7uGPpQhL2 cEExSYZefTzeifpN1MKSzYl1ZRXrUC5DyQ5hIgoCEIAABCAAgb4TiCxE8aKB0UUqzWeDY9h8G6Eh BCAAAQhAAAJtJHB2roaGP+RXno0Qa6ovjmFN4F0U6/osSRc69VkG9miW9bEH9mgWgWZpQ//IaQ/b za7V/oXzUWQFcmQz66MjHUlcycNpdCNspdfblRydPuRc8JKzXpFszDEszhAJEIAABCAAAQh0nYC3 2fUXeT84YTA2x3DyKutN+tg5yMoBPP31m7x/+SFHz+ebdPrElOfz+uYlEjHsekOmfhCAAAQgAAEI FCOQZ7NrtQfiaP683QRbb2atlihvTkgZz2XxudRHpMhkk07vebjd8LqY0vly4xjm40YuCEAAAhCA AAT6QiDPZtcqz+PsQ+4eohMMJ/Kqjr7Tx995P1408Ux+C9LpfQz9PQ/ru3AM62NPyRCAAAQgAAEI tIVAjs2u9RF3J9NL8XxDvZm12shm11H0K+/td/j0Q348ncjtdZ1uoQiOYWMapD8B1T+PMWVp+86k VZVuMzk1Q97G1LOFiuiJwEenfsc2XtjCiChvApMd6B95yRbIF23vsQn0iVLpHwVgH8iawQ70Dyfo 7Te71tFAkemlXkyiNrNWw8tqLHl79vJVcNqyd3zeXOYn5ypVvReOYb38N6WvHi5leqImqarQ8lKF lMdhY9nTLxKGfr/2ws3Z8zaksq1RI3jYPkvmneixRRnGtbED/aMMC6TKfHsReQyGxDLs10b/KMk6 me1A/yjJAhGxyvlbv0s06De4fpd18L4WPSS9N5Sssw/k+j0cWi5fy0Ml4BjWyz8ofSUvTwuZnPvf CTqkvDNh9aCORfI2ovINViLsqOcZdcQWGUFZJrO1Q1Q8NrGEbZf87Hr7AjTu14Yt7OBapLayA/3D gmwvk+IYNsLsS/lcjOR4GCjjzUNI2xBzLmNvuDkc2jyUN8PwQiPq3xUlsEX9lqR/1GYDveIyul/b niL0j0psc9AO9I9KbNDyQnAMG2PAE/limm8aCUH70xTCuYgped9+bIan9RB1m85qbIxZrBXBFtbI XGWgf7gimUOO+gi9nMrJrT+9Jf2if+SAa5HlgB3oHxYc+50Ux7Ax9rc7MkevdNoes5OSd3ishqTH cppt1URjSLRbEWzRBPvRP6q1wtvV0PsINX980j/KtExWO9A/yrRC+2XjGDbChkM5HkUU8TbBzBBB 9LIcyBt8IT7KpbcCKnU9SyMYdEEJbNE8K2KTsm2yejiVsURPd0grEVuUaYvsdohqgU3KtElbZeMY NsJyA9FbGE1/+MvWVy9PspiES9b1ETr7W6W8XY2D8xcP5fUrp1dELWcj+WjTKd6NsMshJZLsgi2q Nxv9o3rmkRLVFkLDpwtZ7oUK6R+V2sXKDvooXt4fldqnbYWpuWdcjSCwXCvfba3az1pGs/Vyo9Pr eiKj9WwZub+XJiXv68SX5/1M1mq3dS4rAjHmO9xDu8QFYgsrxJkSZ7ED/SMTSqeJEuyi+sjEe9DQ P5yiPigsix3oH9XZo/0lHekqtM2ZRV8IQAACEIAABCAAAfcEGEp2zxSJEIAABCAAAQhAoJUEcAxb aTaUhgAEIAABCEAAAu4J/H+FhOPE1VgHMgAAAABJRU5ErkJggg== --047d7ba97b72c4ced304d6c73540 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 --047d7ba97b72c4ced304d6c73540-- From xen-users-bounces@lists.xen.org Thu Feb 28 12:26:07 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 28 Feb 2013 12:26: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 1UB2Xr-0007KP-6h; Thu, 28 Feb 2013 12:25:07 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UB2Xp-0007K4-79 for xen-users@lists.xen.org; Thu, 28 Feb 2013 12:25:05 +0000 Received: from [85.158.139.83:63580] by server-10.bemta-5.messagelabs.com id 9B/E0-23714-0AC4F215; Thu, 28 Feb 2013 12:25:04 +0000 X-Env-Sender: agya.naila@gmail.com X-Msg-Ref: server-4.tower-182.messagelabs.com!1362054296!26696831!1 X-Originating-IP: [74.125.82.41] X-SpamReason: No, hits=0.9 required=7.0 tests=BODY_RANDOM_LONG, HTML_50_60, HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14, RCVD_BY_IP, spamassassin: X-StarScan-Received: X-StarScan-Version: 6.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 27989 invoked from network); 28 Feb 2013 12:24:59 -0000 Received: from mail-wg0-f41.google.com (HELO mail-wg0-f41.google.com) (74.125.82.41) by server-4.tower-182.messagelabs.com with RC4-SHA encrypted SMTP; 28 Feb 2013 12:24:59 -0000 Received: by mail-wg0-f41.google.com with SMTP id ds1so6235833wgb.4 for ; Thu, 28 Feb 2013 04:24:56 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=xpwgpiviHL/LV8yrJfL61/7UUNnOazfZ57wQNzs1rdA=; b=bK52KcE5M96Q/dGVSV7uSRjlJGyh0Ju0Zjp4zQpoGmdkLdMno3YLg/UNl5MUxbz+4L toBf41vWmn0ClCTtvhR1dE3kZtAnWKK6PdDgFGbNi7OQ5ujCPo4tlp8ZUcWjxPn/wKq/ BBFKzljiWt3odeQXYZc1TGoNBr9kQ8A7QvgSfCmozh50VplWwXkH/0YPk7NFWQ0/HWMc 3Cq7m6ieQPdbuV0BUscO6Kb6WAy4cR2v3qxLXHyjxSrHBT0twYVSsLJhQpkMknkpf5yG n8z8TjBHWsCL7H29x3BuV3Muzm2QOltZT6Cf4q0pr4gxfkDW3LDBYQoK1hinSsnya948 j/Vw== MIME-Version: 1.0 X-Received: by 10.181.11.164 with SMTP id ej4mr10232882wid.29.1362054296528; Thu, 28 Feb 2013 04:24:56 -0800 (PST) Received: by 10.216.236.13 with HTTP; Thu, 28 Feb 2013 04:24:56 -0800 (PST) In-Reply-To: References: Date: Thu, 28 Feb 2013 13:24:56 +0100 Message-ID: From: agya naila To: Andrew Eross Cc: rshriram@cs.ubc.ca, "xen-users@lists.xen.org" Subject: Re: [Xen-users] Remus dom0 network buffering X-BeenThere: xen-users@lists.xen.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="===============2016549467175595897==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============2016549467175595897== Content-Type: multipart/alternative; boundary=f46d0438914b826e7704d6c7fa06 --f46d0438914b826e7704d6c7fa06 Content-Type: text/plain; charset=ISO-8859-1 Here my lsmod, #lsmod Module Size Used by xt_tcpudp 12603 1 xt_physdev 12587 4 iptable_filter 12810 1 ip_tables 27473 1 iptable_filter x_tables 29846 4 xt_tcpudp,xt_physdev,iptable_filter,ip_tables drbd 303888 4 blktap 25553 0 xen_pciback 48131 0 xen_netback 27854 0 [permanent] xen_blkback 23363 0 [permanent] xen_gntalloc 13321 0 xen_gntdev 17676 1 xen_evtchn 13172 2 xenfs 18311 1 bridge 90989 0 stp 12931 1 bridge dm_multipath 23230 0 radeon 804372 2 joydev 17693 0 ttm 76949 1 radeon drm_kms_helper 46978 1 radeon drm 242038 4 radeon,ttm,drm_kms_helper i2c_algo_bit 13423 1 radeon bnep 18281 2 parport_pc 32866 0 shpchp 37277 0 bluetooth 180104 7 bnep ppdev 17113 0 mac_hid 13253 0 e752x_edac 18564 0 edac_core 53746 3 e752x_edac ifb 12896 0 act_mirred 13038 0 cls_u32 17060 0 cls_tcindex 13058 0 cls_basic 12946 0 sch_ingress 12866 0 sch_prio 13231 0 sch_plug 12654 0 lp 17799 0 parport 46562 3 parport_pc,ppdev,lp dm_snapshot 39031 3 usbhid 47199 0 hid 99559 1 usbhid usb_storage 49198 0 mptspi 22921 21 mptscsih 44882 1 mptspi mptbase 103162 2 mptspi,mptscsih tg3 152032 0 Regards, Agya On Thu, Feb 28, 2013 at 12:29 PM, agya naila wrote: > Hi Andrew and Shiram, > > I am keep trying this setting using my machine that I mention earlier in > this email thread. > I have using remus with network buffering and no network buffering. > > with no network buffering > #remus --no-net > > with network buffering > #remus > > However, when I observed the jitter graph result of my data it seem there > is no buffering impact on my traffic flow, enclosed both the graph result. > I only observed RTP packet and observed the jitter. What I could understand > the graph with network protection will doesn't have flow until x time when > the buffer released, in this case default value 100ms. Y axis is time and X > axis is jitter. > > Both of command above running without error except suspend event channel > issue that we discussed earlier. Please suggest. > > Regards, > > Agya > > On Wed, Feb 20, 2013 at 1:13 PM, agya naila wrote: > >> Aha, sorry to mix it :), its clear now. >> >> Regards, >> >> Agya >> >> >> On Wed, Feb 20, 2013 at 1:01 PM, Andrew Eross wrote: >> >>> Hi Agya, >>> >>> This patch doesn't fix the 'suspend event channel' issue, it just fixes >>> the crash from the first e-mail in this thread. >>> >>> Please see this wiki page: >>> http://wiki.xen.org/wiki/Remus_PV_domU_requirements >>> >>> That discusses the suspend event channel issue. >>> >>> Cheers, >>> Andrew >>> >>> >>> On Wed, Feb 20, 2013 at 8:57 AM, agya naila wrote: >>> >>>> Hello All, >>>> >>>> I am trying this patch on my machine Ubuntu 12.04 AMD64 both for Dom0 >>>> and DomU with Xen 4.2.2-pre compiling from sources also DRBD 8.3.11 but >>>> unfortunately it seem didn't work since I still got the message WARNING: >>>> suspend event channel unavailable, falling back to slow xenstore >>>> signalling. >>>> >>>> Regards, >>>> >>>> Agya >>>> >>>> On Tue, Feb 19, 2013 at 12:39 PM, Andrew Eross wrote: >>>> >>>>> Hi all, >>>>> >>>>> To close off on this, Shriram's patch worked great, thank you. >>>>> >>>>> So Ubuntu 12.10's standard generic kernel is now working fine as a >>>>> dom0 for Remus with Xen 4.1.4 (with the patch from this thread). >>>>> >>>>> I wrote up my full install instructions here: >>>>> >>>>> http://wiki.xen.org/wiki/Install_Xen_4.1.4_with_Remus_and_DRBD_on_Ubuntu_12.10 >>>>> >>>>> I also took a shot at a number of updates to: >>>>> http://wiki.xen.org/wiki/Remus >>>>> >>>>> And added these pages: >>>>> http://wiki.xen.org/wiki/Remus_PV_domU_requirements >>>>> http://wiki.xen.org/wiki/Remus_dom0_requirements >>>>> >>>>> Feedback very welcome, a lot of that information was a bit old, so I >>>>> did my best. >>>>> >>>>> Cheers, >>>>> Andrew >>>>> >>>>> >>>>> On Mon, Feb 18, 2013 at 8:26 PM, Shriram Rajagopalan < >>>>> rshriram@cs.ubc.ca> wrote: >>>>> >>>>>> ah darn. Yes, the 3.5 kernel has sch_plug in it. Unfortunately, the >>>>>> technique to initialize the sch_plug module is bit >>>>>> different with the module thats already mainline. You ll have to patch >>>>>> the qdisc.py python module. I ll submit the >>>>>> patch to xen devel soon. >>>>>> Mean while, can you try the patch below and see if it works ? >>>>>> >>>>>> Secondly, you said you were writing a blog about how you set it up. >>>>>> One of the remus users created a wiki >>>>>> remusha.wikidot.com, which has a whole tutorial on how to setup remus >>>>>> with Debian Squeeze. I have been under fire >>>>>> lately for a host of remus issues. It would be great if you could post >>>>>> your experiences on the wiki too. >>>>>> (http://remusha.wikidot.com/system:join) >>>>>> >>>>>> thanks >>>>>> shriram >>>>>> >>>>>> --- >>>>>> diff -r 6435f1edf24e tools/python/xen/remus/qdisc.py >>>>>> --- a/tools/python/xen/remus/qdisc.py Tue Jul 17 19:23:30 2012 -0400 >>>>>> +++ b/tools/python/xen/remus/qdisc.py Mon Feb 18 18:25:22 2013 -0500 >>>>>> @@ -1,6 +1,9 @@ >>>>>> import socket, struct >>>>>> >>>>>> import netlink >>>>>> +import platform >>>>>> + >>>>>> +kernelversion = >>>>>> platform.platform(terse=True).split("-")[1].split(".") >>>>>> >>>>>> qdisc_kinds = {} >>>>>> >>>>>> @@ -150,9 +153,14 @@ >>>>>> TC_PLUG_RELEASE = 1 >>>>>> >>>>>> class PlugQdisc(Qdisc): >>>>>> - fmt = 'I' >>>>>> >>>>>> def __init__(self, qdict=None): >>>>>> + if int(kernelversion[0]) >= 3 and int(kernelversion[1]) >= 4: >>>>>> + self.fmt = 'iI' >>>>>> + self.limit = 10000 >>>>>> + else: >>>>>> + self.fmt = 'I' >>>>>> + >>>>>> if not qdict: >>>>>> qdict = {'kind': 'plug', >>>>>> 'handle': TC_H_ROOT} >>>>>> @@ -161,7 +169,10 @@ >>>>>> self.action = 0 >>>>>> >>>>>> def pack(self): >>>>>> - return struct.pack(self.fmt, self.action) >>>>>> + if int(kernelversion[0]) >= 3 and int(kernelversion[1]) >= 4: >>>>>> + return struct.pack(self.fmt, self.action, self.limit) >>>>>> + else: >>>>>> + return struct.pack(self.fmt, self.action) >>>>>> >>>>>> def parse(self, args): >>>>>> if not args: >>>>>> >>>>> >>>>> >>>>> _______________________________________________ >>>>> Xen-users mailing list >>>>> Xen-users@lists.xen.org >>>>> http://lists.xen.org/xen-users >>>>> >>>> >>>> >>> >> > --f46d0438914b826e7704d6c7fa06 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Here my lsmod,

=A0#lsmod
Mo= dule =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0Size =A0Used by
xt_tcpudp= =A0 =A0 =A0 =A0 =A0 =A0 =A012603 =A01
xt_physdev =A0 =A0 =A0 =A0 =A0 =A0 12587 =A04
iptable_filter= =A0 =A0 =A0 =A0 12810 =A01
ip_tables =A0 =A0 =A0 =A0 =A0 =A0 =A0= 27473 =A01 iptable_filter
x_tables =A0 =A0 =A0 =A0 =A0 =A0 =A0 29= 846 =A04 xt_tcpudp,xt_physdev,iptable_filter,ip_tables
drbd =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0303888 =A04
blktap = =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 25553 =A00
xen_pciback =A0 =A0 = =A0 =A0 =A0 =A048131 =A00
xen_netback =A0 =A0 =A0 =A0 =A0 =A02785= 4 =A00 [permanent]
xen_blkback =A0 =A0 =A0 =A0 =A0 =A023363 =A00 = [permanent]
xen_gntalloc =A0 =A0 =A0 =A0 =A0 13321 =A00
xen_gntdev =A0 = =A0 =A0 =A0 =A0 =A0 17676 =A01
xen_evtchn =A0 =A0 =A0 =A0 =A0 =A0= 13172 =A02
xenfs =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A018311 =A01
bridge =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 90989 =A00
stp = =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A012931 =A01 bridge
dm_multipath =A0 =A0 =A0 =A0 =A0 23230 =A00
radeon =A0 =A0 = =A0 =A0 =A0 =A0 =A0 =A0804372 =A02
joydev =A0 =A0 =A0 =A0 =A0 =A0= =A0 =A0 17693 =A00
ttm =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A076= 949 =A01 radeon
drm_kms_helper =A0 =A0 =A0 =A0 46978 =A01 radeon<= /div>
drm =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 242038 =A04 radeon,ttm,drm_kms= _helper
i2c_algo_bit =A0 =A0 =A0 =A0 =A0 13423 =A01 radeon
<= div>bnep =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 18281 =A02
parport_p= c =A0 =A0 =A0 =A0 =A0 =A0 32866 =A00
shpchp =A0 =A0 =A0 =A0 =A0 = =A0 =A0 =A0 37277 =A00
bluetooth =A0 =A0 =A0 =A0 =A0 =A0 180104 =A07 bnep
ppdev =A0= =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A017113 =A00
mac_hid =A0 =A0 =A0 = =A0 =A0 =A0 =A0 =A013253 =A00
e752x_edac =A0 =A0 =A0 =A0 =A0 =A0 = 18564 =A00
edac_core =A0 =A0 =A0 =A0 =A0 =A0 =A053746 =A03 e752x_= edac
ifb =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A012896 =A00
act_mi= rred =A0 =A0 =A0 =A0 =A0 =A0 13038 =A00
cls_u32 =A0 =A0 =A0 =A0 = =A0 =A0 =A0 =A017060 =A00
cls_tcindex =A0 =A0 =A0 =A0 =A0 =A01305= 8 =A00
cls_basic =A0 =A0 =A0 =A0 =A0 =A0 =A012946 =A00
= sch_ingress =A0 =A0 =A0 =A0 =A0 =A012866 =A00
sch_prio =A0 =A0 =A0 =A0 =A0 =A0 =A0 13231 =A00
sch_plug =A0= =A0 =A0 =A0 =A0 =A0 =A0 12654 =A00
lp =A0 =A0 =A0 =A0 =A0 =A0 = =A0 =A0 =A0 =A0 17799 =A00
parport =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A046562 =A03 parport_pc,ppdev,lp
dm_snapshot =A0 =A0 =A0 =A0 =A0= =A039031 =A03
usbhid =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 47199 =A00
hid =A0 = =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A099559 =A01 usbhid
usb_storage = =A0 =A0 =A0 =A0 =A0 =A049198 =A00
mptspi =A0 =A0 =A0 =A0 =A0 =A0 = =A0 =A0 22921 =A021
mptscsih =A0 =A0 =A0 =A0 =A0 =A0 =A0 44882 = =A01 mptspi
mptbase =A0 =A0 =A0 =A0 =A0 =A0 =A0 103162 =A02 mptspi,mptscsih
<= div>tg3 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 152032 =A00


Regards,

Agya

=
On Thu, Feb 28, 2013 at 12:29 PM, agya naila <agya.naila@gmail.com> wrote:
Hi Andrew and Shiram,

I a= m keep trying this setting using my machine that I mention earlier in this = email thread.
I have using remus with network buffering and no network buffering.

with no network buffering
#remus --no-net <vm> &= lt;backup target>

with network buffering
<= div>#remus <vm> <backup target>

However, when I observed= the jitter graph result of my data it seem there is no buffering impact on= my traffic flow, enclosed both the graph result. I only observed RTP packe= t and observed the jitter. What I could understand the graph with network p= rotection will doesn't have flow until x time when the buffer released,= in this case default value 100ms. Y axis is time and X axis is jitter.

Both of command above running without error except =A0s= uspend event channel issue that we discussed earlier. Please suggest.
=

Regards,

Agya

On Wed, Feb 20, 2013 at 1:13 PM, agya naila <agya.naila@gmail.com> wrote:
Aha, sorry to mix it :), its clear now.

Regards,

Agya


On Wed, = Feb 20, 2013 at 1:01 PM, Andrew Eross <eross@locatrix.com> = wrote:
Hi Agya,

This patch doesn= 't fix the 'suspend event channel' issue, it just fixes the cra= sh from the first e-mail in this thread.


That discusses the suspend event channel issue.

Cheers,
Andrew


On Wed, Feb 20, 2013 at 8:57 AM, agya naila <agy= a.naila@gmail.com> wrote:
Hello All,

I am trying th= is patch on my machine Ubuntu 12.04 AMD64 both for Dom0 and DomU with Xen 4= .2.2-pre compiling from sources also DRBD 8.3.11 but unfortunately it seem = didn't work since I still got the message=A0WARNING: susp= end event channel unavailable, falling back to slow xenstore signalling.=A0=

Regards= ,

A= gya

On Tue, Feb 19, 2013 at 12:39 PM, = Andrew Eross <eross@locatrix.com> wrote:
Hi all,

To close off on this, Shriram's patch worked= great, thank you.

So Ubuntu 12.10's standard = generic kernel is now working fine as a dom0 for Remus with Xen 4.1.4 (with= the patch from this thread).

I wrote up my full install instructions here:
http://wiki.xen.org/wiki/Install_Xen_4.1= .4_with_Remus_and_DRBD_on_Ubuntu_12.10

I also took a shot at a number of updates to:
http://wiki.x= en.org/wiki/Remus

And added these pages:
Feedback very welcome, a lot of that information was a bit old,= so I did my best.

Cheers,
Andrew

=

On Mon, Feb 18, 2013 at 8:26 PM, Shrira= m Rajagopalan <rshriram@cs.ubc.ca> wrote:
ah darn. Yes, the 3.5 kernel has sch_plug in= it. Unfortunately, the
technique to initialize the sch_plug module is bit
different with the module thats already mainline. You ll have to patch
the qdisc.py python module. I ll submit the
patch to xen devel soon.
Mean while, can you try the patch below and see if it works ?

Secondly, you said you were writing a blog about how you set it up.
One of the remus users created a wiki
remusha.wikidot.co= m, which has a whole tutorial on how to setup remus
with Debian Squeeze. I have been under fire
lately for a host of remus issues. It would be great if you could post
your experiences on the wiki too.
(http:= //remusha.wikidot.com/system:join)

thanks
shriram

---
diff -r 6435f1edf24e tools/python/xen/remus/qdisc.py
--- a/tools/python/xen/remus/qdisc.py =A0 Tue Jul 17 19:23:30 2012 -0400 +++ b/tools/python/xen/remus/qdisc.py =A0 Mon Feb 18 18:25:22 2013 -0500 @@ -1,6 +1,9 @@
=A0import socket, struct

=A0import netlink
+import platform
+
+kernelversion =3D platform.platform(terse=3DTrue).split("-")[1].= split(".")

=A0qdisc_kinds =3D {}

@@ -150,9 +153,14 @@
=A0TC_PLUG_RELEASE =3D 1

=A0class PlugQdisc(Qdisc):
- =A0 =A0fmt =3D 'I'

=A0 =A0 =A0def __init__(self, qdict=3DNone):
+ =A0 =A0 =A0 =A0if int(kernelversion[0]) >=3D 3 and int(kernelversion[1= ]) >=3D 4:
+ =A0 =A0 =A0 =A0 =A0 =A0self.fmt =3D 'iI'
+ =A0 =A0 =A0 =A0 =A0 =A0self.limit =3D 10000
+ =A0 =A0 =A0 =A0else:
+ =A0 =A0 =A0 =A0 =A0 =A0self.fmt =3D 'I'
+
=A0 =A0 =A0 =A0 =A0if not qdict:
=A0 =A0 =A0 =A0 =A0 =A0 =A0qdict =3D {'kind': 'plug',
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 'handle': TC_H_ROOT} @@ -161,7 +169,10 @@
=A0 =A0 =A0 =A0 =A0self.action =3D 0

=A0 =A0 =A0def pack(self):
- =A0 =A0 =A0 =A0return struct.pack(self.fmt, self.action)
+ =A0 =A0 =A0 =A0if int(kernelversion[0]) >=3D 3 and int(kernelversion[1= ]) >=3D 4:
+ =A0 =A0 =A0 =A0 =A0 =A0return struct.pack(self.fmt, self.action, self.lim= it)
+ =A0 =A0 =A0 =A0else:
+ =A0 =A0 =A0 =A0 =A0 =A0return struct.pack(self.fmt, self.action)

=A0 =A0 =A0def parse(self, args):
=A0 =A0 =A0 =A0 =A0if not args:


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





--f46d0438914b826e7704d6c7fa06-- --===============2016549467175595897== 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 --===============2016549467175595897==-- From xen-users-bounces@lists.xen.org Thu Feb 28 12:26:07 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 28 Feb 2013 12:26: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 1UB2Xr-0007KP-6h; Thu, 28 Feb 2013 12:25:07 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UB2Xp-0007K4-79 for xen-users@lists.xen.org; Thu, 28 Feb 2013 12:25:05 +0000 Received: from [85.158.139.83:63580] by server-10.bemta-5.messagelabs.com id 9B/E0-23714-0AC4F215; Thu, 28 Feb 2013 12:25:04 +0000 X-Env-Sender: agya.naila@gmail.com X-Msg-Ref: server-4.tower-182.messagelabs.com!1362054296!26696831!1 X-Originating-IP: [74.125.82.41] X-SpamReason: No, hits=0.9 required=7.0 tests=BODY_RANDOM_LONG, HTML_50_60, HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14, RCVD_BY_IP, spamassassin: X-StarScan-Received: X-StarScan-Version: 6.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 27989 invoked from network); 28 Feb 2013 12:24:59 -0000 Received: from mail-wg0-f41.google.com (HELO mail-wg0-f41.google.com) (74.125.82.41) by server-4.tower-182.messagelabs.com with RC4-SHA encrypted SMTP; 28 Feb 2013 12:24:59 -0000 Received: by mail-wg0-f41.google.com with SMTP id ds1so6235833wgb.4 for ; Thu, 28 Feb 2013 04:24:56 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=xpwgpiviHL/LV8yrJfL61/7UUNnOazfZ57wQNzs1rdA=; b=bK52KcE5M96Q/dGVSV7uSRjlJGyh0Ju0Zjp4zQpoGmdkLdMno3YLg/UNl5MUxbz+4L toBf41vWmn0ClCTtvhR1dE3kZtAnWKK6PdDgFGbNi7OQ5ujCPo4tlp8ZUcWjxPn/wKq/ BBFKzljiWt3odeQXYZc1TGoNBr9kQ8A7QvgSfCmozh50VplWwXkH/0YPk7NFWQ0/HWMc 3Cq7m6ieQPdbuV0BUscO6Kb6WAy4cR2v3qxLXHyjxSrHBT0twYVSsLJhQpkMknkpf5yG n8z8TjBHWsCL7H29x3BuV3Muzm2QOltZT6Cf4q0pr4gxfkDW3LDBYQoK1hinSsnya948 j/Vw== MIME-Version: 1.0 X-Received: by 10.181.11.164 with SMTP id ej4mr10232882wid.29.1362054296528; Thu, 28 Feb 2013 04:24:56 -0800 (PST) Received: by 10.216.236.13 with HTTP; Thu, 28 Feb 2013 04:24:56 -0800 (PST) In-Reply-To: References: Date: Thu, 28 Feb 2013 13:24:56 +0100 Message-ID: From: agya naila To: Andrew Eross Cc: rshriram@cs.ubc.ca, "xen-users@lists.xen.org" Subject: Re: [Xen-users] Remus dom0 network buffering X-BeenThere: xen-users@lists.xen.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="===============2016549467175595897==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============2016549467175595897== Content-Type: multipart/alternative; boundary=f46d0438914b826e7704d6c7fa06 --f46d0438914b826e7704d6c7fa06 Content-Type: text/plain; charset=ISO-8859-1 Here my lsmod, #lsmod Module Size Used by xt_tcpudp 12603 1 xt_physdev 12587 4 iptable_filter 12810 1 ip_tables 27473 1 iptable_filter x_tables 29846 4 xt_tcpudp,xt_physdev,iptable_filter,ip_tables drbd 303888 4 blktap 25553 0 xen_pciback 48131 0 xen_netback 27854 0 [permanent] xen_blkback 23363 0 [permanent] xen_gntalloc 13321 0 xen_gntdev 17676 1 xen_evtchn 13172 2 xenfs 18311 1 bridge 90989 0 stp 12931 1 bridge dm_multipath 23230 0 radeon 804372 2 joydev 17693 0 ttm 76949 1 radeon drm_kms_helper 46978 1 radeon drm 242038 4 radeon,ttm,drm_kms_helper i2c_algo_bit 13423 1 radeon bnep 18281 2 parport_pc 32866 0 shpchp 37277 0 bluetooth 180104 7 bnep ppdev 17113 0 mac_hid 13253 0 e752x_edac 18564 0 edac_core 53746 3 e752x_edac ifb 12896 0 act_mirred 13038 0 cls_u32 17060 0 cls_tcindex 13058 0 cls_basic 12946 0 sch_ingress 12866 0 sch_prio 13231 0 sch_plug 12654 0 lp 17799 0 parport 46562 3 parport_pc,ppdev,lp dm_snapshot 39031 3 usbhid 47199 0 hid 99559 1 usbhid usb_storage 49198 0 mptspi 22921 21 mptscsih 44882 1 mptspi mptbase 103162 2 mptspi,mptscsih tg3 152032 0 Regards, Agya On Thu, Feb 28, 2013 at 12:29 PM, agya naila wrote: > Hi Andrew and Shiram, > > I am keep trying this setting using my machine that I mention earlier in > this email thread. > I have using remus with network buffering and no network buffering. > > with no network buffering > #remus --no-net > > with network buffering > #remus > > However, when I observed the jitter graph result of my data it seem there > is no buffering impact on my traffic flow, enclosed both the graph result. > I only observed RTP packet and observed the jitter. What I could understand > the graph with network protection will doesn't have flow until x time when > the buffer released, in this case default value 100ms. Y axis is time and X > axis is jitter. > > Both of command above running without error except suspend event channel > issue that we discussed earlier. Please suggest. > > Regards, > > Agya > > On Wed, Feb 20, 2013 at 1:13 PM, agya naila wrote: > >> Aha, sorry to mix it :), its clear now. >> >> Regards, >> >> Agya >> >> >> On Wed, Feb 20, 2013 at 1:01 PM, Andrew Eross wrote: >> >>> Hi Agya, >>> >>> This patch doesn't fix the 'suspend event channel' issue, it just fixes >>> the crash from the first e-mail in this thread. >>> >>> Please see this wiki page: >>> http://wiki.xen.org/wiki/Remus_PV_domU_requirements >>> >>> That discusses the suspend event channel issue. >>> >>> Cheers, >>> Andrew >>> >>> >>> On Wed, Feb 20, 2013 at 8:57 AM, agya naila wrote: >>> >>>> Hello All, >>>> >>>> I am trying this patch on my machine Ubuntu 12.04 AMD64 both for Dom0 >>>> and DomU with Xen 4.2.2-pre compiling from sources also DRBD 8.3.11 but >>>> unfortunately it seem didn't work since I still got the message WARNING: >>>> suspend event channel unavailable, falling back to slow xenstore >>>> signalling. >>>> >>>> Regards, >>>> >>>> Agya >>>> >>>> On Tue, Feb 19, 2013 at 12:39 PM, Andrew Eross wrote: >>>> >>>>> Hi all, >>>>> >>>>> To close off on this, Shriram's patch worked great, thank you. >>>>> >>>>> So Ubuntu 12.10's standard generic kernel is now working fine as a >>>>> dom0 for Remus with Xen 4.1.4 (with the patch from this thread). >>>>> >>>>> I wrote up my full install instructions here: >>>>> >>>>> http://wiki.xen.org/wiki/Install_Xen_4.1.4_with_Remus_and_DRBD_on_Ubuntu_12.10 >>>>> >>>>> I also took a shot at a number of updates to: >>>>> http://wiki.xen.org/wiki/Remus >>>>> >>>>> And added these pages: >>>>> http://wiki.xen.org/wiki/Remus_PV_domU_requirements >>>>> http://wiki.xen.org/wiki/Remus_dom0_requirements >>>>> >>>>> Feedback very welcome, a lot of that information was a bit old, so I >>>>> did my best. >>>>> >>>>> Cheers, >>>>> Andrew >>>>> >>>>> >>>>> On Mon, Feb 18, 2013 at 8:26 PM, Shriram Rajagopalan < >>>>> rshriram@cs.ubc.ca> wrote: >>>>> >>>>>> ah darn. Yes, the 3.5 kernel has sch_plug in it. Unfortunately, the >>>>>> technique to initialize the sch_plug module is bit >>>>>> different with the module thats already mainline. You ll have to patch >>>>>> the qdisc.py python module. I ll submit the >>>>>> patch to xen devel soon. >>>>>> Mean while, can you try the patch below and see if it works ? >>>>>> >>>>>> Secondly, you said you were writing a blog about how you set it up. >>>>>> One of the remus users created a wiki >>>>>> remusha.wikidot.com, which has a whole tutorial on how to setup remus >>>>>> with Debian Squeeze. I have been under fire >>>>>> lately for a host of remus issues. It would be great if you could post >>>>>> your experiences on the wiki too. >>>>>> (http://remusha.wikidot.com/system:join) >>>>>> >>>>>> thanks >>>>>> shriram >>>>>> >>>>>> --- >>>>>> diff -r 6435f1edf24e tools/python/xen/remus/qdisc.py >>>>>> --- a/tools/python/xen/remus/qdisc.py Tue Jul 17 19:23:30 2012 -0400 >>>>>> +++ b/tools/python/xen/remus/qdisc.py Mon Feb 18 18:25:22 2013 -0500 >>>>>> @@ -1,6 +1,9 @@ >>>>>> import socket, struct >>>>>> >>>>>> import netlink >>>>>> +import platform >>>>>> + >>>>>> +kernelversion = >>>>>> platform.platform(terse=True).split("-")[1].split(".") >>>>>> >>>>>> qdisc_kinds = {} >>>>>> >>>>>> @@ -150,9 +153,14 @@ >>>>>> TC_PLUG_RELEASE = 1 >>>>>> >>>>>> class PlugQdisc(Qdisc): >>>>>> - fmt = 'I' >>>>>> >>>>>> def __init__(self, qdict=None): >>>>>> + if int(kernelversion[0]) >= 3 and int(kernelversion[1]) >= 4: >>>>>> + self.fmt = 'iI' >>>>>> + self.limit = 10000 >>>>>> + else: >>>>>> + self.fmt = 'I' >>>>>> + >>>>>> if not qdict: >>>>>> qdict = {'kind': 'plug', >>>>>> 'handle': TC_H_ROOT} >>>>>> @@ -161,7 +169,10 @@ >>>>>> self.action = 0 >>>>>> >>>>>> def pack(self): >>>>>> - return struct.pack(self.fmt, self.action) >>>>>> + if int(kernelversion[0]) >= 3 and int(kernelversion[1]) >= 4: >>>>>> + return struct.pack(self.fmt, self.action, self.limit) >>>>>> + else: >>>>>> + return struct.pack(self.fmt, self.action) >>>>>> >>>>>> def parse(self, args): >>>>>> if not args: >>>>>> >>>>> >>>>> >>>>> _______________________________________________ >>>>> Xen-users mailing list >>>>> Xen-users@lists.xen.org >>>>> http://lists.xen.org/xen-users >>>>> >>>> >>>> >>> >> > --f46d0438914b826e7704d6c7fa06 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Here my lsmod,

=A0#lsmod
Mo= dule =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0Size =A0Used by
xt_tcpudp= =A0 =A0 =A0 =A0 =A0 =A0 =A012603 =A01
xt_physdev =A0 =A0 =A0 =A0 =A0 =A0 12587 =A04
iptable_filter= =A0 =A0 =A0 =A0 12810 =A01
ip_tables =A0 =A0 =A0 =A0 =A0 =A0 =A0= 27473 =A01 iptable_filter
x_tables =A0 =A0 =A0 =A0 =A0 =A0 =A0 29= 846 =A04 xt_tcpudp,xt_physdev,iptable_filter,ip_tables
drbd =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0303888 =A04
blktap = =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 25553 =A00
xen_pciback =A0 =A0 = =A0 =A0 =A0 =A048131 =A00
xen_netback =A0 =A0 =A0 =A0 =A0 =A02785= 4 =A00 [permanent]
xen_blkback =A0 =A0 =A0 =A0 =A0 =A023363 =A00 = [permanent]
xen_gntalloc =A0 =A0 =A0 =A0 =A0 13321 =A00
xen_gntdev =A0 = =A0 =A0 =A0 =A0 =A0 17676 =A01
xen_evtchn =A0 =A0 =A0 =A0 =A0 =A0= 13172 =A02
xenfs =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A018311 =A01
bridge =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 90989 =A00
stp = =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A012931 =A01 bridge
dm_multipath =A0 =A0 =A0 =A0 =A0 23230 =A00
radeon =A0 =A0 = =A0 =A0 =A0 =A0 =A0 =A0804372 =A02
joydev =A0 =A0 =A0 =A0 =A0 =A0= =A0 =A0 17693 =A00
ttm =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A076= 949 =A01 radeon
drm_kms_helper =A0 =A0 =A0 =A0 46978 =A01 radeon<= /div>
drm =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 242038 =A04 radeon,ttm,drm_kms= _helper
i2c_algo_bit =A0 =A0 =A0 =A0 =A0 13423 =A01 radeon
<= div>bnep =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 18281 =A02
parport_p= c =A0 =A0 =A0 =A0 =A0 =A0 32866 =A00
shpchp =A0 =A0 =A0 =A0 =A0 = =A0 =A0 =A0 37277 =A00
bluetooth =A0 =A0 =A0 =A0 =A0 =A0 180104 =A07 bnep
ppdev =A0= =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A017113 =A00
mac_hid =A0 =A0 =A0 = =A0 =A0 =A0 =A0 =A013253 =A00
e752x_edac =A0 =A0 =A0 =A0 =A0 =A0 = 18564 =A00
edac_core =A0 =A0 =A0 =A0 =A0 =A0 =A053746 =A03 e752x_= edac
ifb =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A012896 =A00
act_mi= rred =A0 =A0 =A0 =A0 =A0 =A0 13038 =A00
cls_u32 =A0 =A0 =A0 =A0 = =A0 =A0 =A0 =A017060 =A00
cls_tcindex =A0 =A0 =A0 =A0 =A0 =A01305= 8 =A00
cls_basic =A0 =A0 =A0 =A0 =A0 =A0 =A012946 =A00
= sch_ingress =A0 =A0 =A0 =A0 =A0 =A012866 =A00
sch_prio =A0 =A0 =A0 =A0 =A0 =A0 =A0 13231 =A00
sch_plug =A0= =A0 =A0 =A0 =A0 =A0 =A0 12654 =A00
lp =A0 =A0 =A0 =A0 =A0 =A0 = =A0 =A0 =A0 =A0 17799 =A00
parport =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A046562 =A03 parport_pc,ppdev,lp
dm_snapshot =A0 =A0 =A0 =A0 =A0= =A039031 =A03
usbhid =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 47199 =A00
hid =A0 = =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A099559 =A01 usbhid
usb_storage = =A0 =A0 =A0 =A0 =A0 =A049198 =A00
mptspi =A0 =A0 =A0 =A0 =A0 =A0 = =A0 =A0 22921 =A021
mptscsih =A0 =A0 =A0 =A0 =A0 =A0 =A0 44882 = =A01 mptspi
mptbase =A0 =A0 =A0 =A0 =A0 =A0 =A0 103162 =A02 mptspi,mptscsih
<= div>tg3 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 152032 =A00


Regards,

Agya

=
On Thu, Feb 28, 2013 at 12:29 PM, agya naila <agya.naila@gmail.com> wrote:
Hi Andrew and Shiram,

I a= m keep trying this setting using my machine that I mention earlier in this = email thread.
I have using remus with network buffering and no network buffering.

with no network buffering
#remus --no-net <vm> &= lt;backup target>

with network buffering
<= div>#remus <vm> <backup target>

However, when I observed= the jitter graph result of my data it seem there is no buffering impact on= my traffic flow, enclosed both the graph result. I only observed RTP packe= t and observed the jitter. What I could understand the graph with network p= rotection will doesn't have flow until x time when the buffer released,= in this case default value 100ms. Y axis is time and X axis is jitter.

Both of command above running without error except =A0s= uspend event channel issue that we discussed earlier. Please suggest.
=

Regards,

Agya

On Wed, Feb 20, 2013 at 1:13 PM, agya naila <agya.naila@gmail.com> wrote:
Aha, sorry to mix it :), its clear now.

Regards,

Agya


On Wed, = Feb 20, 2013 at 1:01 PM, Andrew Eross <eross@locatrix.com> = wrote:
Hi Agya,

This patch doesn= 't fix the 'suspend event channel' issue, it just fixes the cra= sh from the first e-mail in this thread.


That discusses the suspend event channel issue.

Cheers,
Andrew


On Wed, Feb 20, 2013 at 8:57 AM, agya naila <agy= a.naila@gmail.com> wrote:
Hello All,

I am trying th= is patch on my machine Ubuntu 12.04 AMD64 both for Dom0 and DomU with Xen 4= .2.2-pre compiling from sources also DRBD 8.3.11 but unfortunately it seem = didn't work since I still got the message=A0WARNING: susp= end event channel unavailable, falling back to slow xenstore signalling.=A0=

Regards= ,

A= gya

On Tue, Feb 19, 2013 at 12:39 PM, = Andrew Eross <eross@locatrix.com> wrote:
Hi all,

To close off on this, Shriram's patch worked= great, thank you.

So Ubuntu 12.10's standard = generic kernel is now working fine as a dom0 for Remus with Xen 4.1.4 (with= the patch from this thread).

I wrote up my full install instructions here:
http://wiki.xen.org/wiki/Install_Xen_4.1= .4_with_Remus_and_DRBD_on_Ubuntu_12.10

I also took a shot at a number of updates to:
http://wiki.x= en.org/wiki/Remus

And added these pages:
Feedback very welcome, a lot of that information was a bit old,= so I did my best.

Cheers,
Andrew

=

On Mon, Feb 18, 2013 at 8:26 PM, Shrira= m Rajagopalan <rshriram@cs.ubc.ca> wrote:
ah darn. Yes, the 3.5 kernel has sch_plug in= it. Unfortunately, the
technique to initialize the sch_plug module is bit
different with the module thats already mainline. You ll have to patch
the qdisc.py python module. I ll submit the
patch to xen devel soon.
Mean while, can you try the patch below and see if it works ?

Secondly, you said you were writing a blog about how you set it up.
One of the remus users created a wiki
remusha.wikidot.co= m, which has a whole tutorial on how to setup remus
with Debian Squeeze. I have been under fire
lately for a host of remus issues. It would be great if you could post
your experiences on the wiki too.
(http:= //remusha.wikidot.com/system:join)

thanks
shriram

---
diff -r 6435f1edf24e tools/python/xen/remus/qdisc.py
--- a/tools/python/xen/remus/qdisc.py =A0 Tue Jul 17 19:23:30 2012 -0400 +++ b/tools/python/xen/remus/qdisc.py =A0 Mon Feb 18 18:25:22 2013 -0500 @@ -1,6 +1,9 @@
=A0import socket, struct

=A0import netlink
+import platform
+
+kernelversion =3D platform.platform(terse=3DTrue).split("-")[1].= split(".")

=A0qdisc_kinds =3D {}

@@ -150,9 +153,14 @@
=A0TC_PLUG_RELEASE =3D 1

=A0class PlugQdisc(Qdisc):
- =A0 =A0fmt =3D 'I'

=A0 =A0 =A0def __init__(self, qdict=3DNone):
+ =A0 =A0 =A0 =A0if int(kernelversion[0]) >=3D 3 and int(kernelversion[1= ]) >=3D 4:
+ =A0 =A0 =A0 =A0 =A0 =A0self.fmt =3D 'iI'
+ =A0 =A0 =A0 =A0 =A0 =A0self.limit =3D 10000
+ =A0 =A0 =A0 =A0else:
+ =A0 =A0 =A0 =A0 =A0 =A0self.fmt =3D 'I'
+
=A0 =A0 =A0 =A0 =A0if not qdict:
=A0 =A0 =A0 =A0 =A0 =A0 =A0qdict =3D {'kind': 'plug',
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 'handle': TC_H_ROOT} @@ -161,7 +169,10 @@
=A0 =A0 =A0 =A0 =A0self.action =3D 0

=A0 =A0 =A0def pack(self):
- =A0 =A0 =A0 =A0return struct.pack(self.fmt, self.action)
+ =A0 =A0 =A0 =A0if int(kernelversion[0]) >=3D 3 and int(kernelversion[1= ]) >=3D 4:
+ =A0 =A0 =A0 =A0 =A0 =A0return struct.pack(self.fmt, self.action, self.lim= it)
+ =A0 =A0 =A0 =A0else:
+ =A0 =A0 =A0 =A0 =A0 =A0return struct.pack(self.fmt, self.action)

=A0 =A0 =A0def parse(self, args):
=A0 =A0 =A0 =A0 =A0if not args:


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





--f46d0438914b826e7704d6c7fa06-- --===============2016549467175595897== 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 --===============2016549467175595897==-- From xen-users-bounces@lists.xen.org Thu Feb 28 14:55:54 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 28 Feb 2013 14:55: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 1UB4sf-0007h9-J3; Thu, 28 Feb 2013 14:54:45 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UB4sd-0007gw-Ku for xen-users@lists.xen.org; Thu, 28 Feb 2013 14:54:43 +0000 Received: from [85.158.137.99:47810] by server-11.bemta-3.messagelabs.com id 96/77-01263-2BF6F215; Thu, 28 Feb 2013 14:54:42 +0000 X-Env-Sender: rshriram@cs.ubc.ca X-Msg-Ref: server-8.tower-217.messagelabs.com!1362063269!13108007!1 X-Originating-IP: [142.103.6.52] X-SpamReason: No, hits=0.8 required=7.0 tests=BODY_RANDOM_LONG, ML_RADAR_SPEW_LINKS_8,RCVD_BY_IP,spamassassin: ,async_handler: YXN5bmNfZGVsYXk6IDcwNDU1MjkgKHRpbWVvdXQp\n X-StarScan-Received: X-StarScan-Version: 6.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 12081 invoked from network); 28 Feb 2013 14:54:31 -0000 Received: from smtp.cs.ubc.ca (HELO smtp.cs.ubc.ca) (142.103.6.52) by server-8.tower-217.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 28 Feb 2013 14:54:31 -0000 Received: from mail-ie0-f181.google.com (mail-ie0-f181.google.com [209.85.223.181]) (authenticated bits=0) by smtp.cs.ubc.ca (8.14.5/8.13.6) with ESMTP id r1SEsR7F001052 (version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=FAIL) for ; Thu, 28 Feb 2013 06:54:28 -0800 Received: by mail-ie0-f181.google.com with SMTP id 17so2167520iea.12 for ; Thu, 28 Feb 2013 06:54:26 -0800 (PST) X-Received: by 10.50.214.67 with SMTP id ny3mr10055574igc.13.1362063266495; Thu, 28 Feb 2013 06:54:26 -0800 (PST) MIME-Version: 1.0 Received: by 10.43.2.67 with HTTP; Thu, 28 Feb 2013 06:53:46 -0800 (PST) In-Reply-To: References: From: Shriram Rajagopalan Date: Thu, 28 Feb 2013 09:53:46 -0500 Message-ID: To: agya naila Cc: "xen-users@lists.xen.org" , Andrew Eross Subject: Re: [Xen-users] Remus dom0 network buffering X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: rshriram@cs.ubc.ca List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org start with a simple test. Ping command. Remember that suspend/resume also takes some time away from the VM. If you are using the slow version of suspend/resume, then that alone could take 10ms or more (to simply suspend/resume). I am not sure if you installed remus from the distribution repo (ubuntu or whatever) or if you compiled from source. If you used a repo version, then you might have to write a script to parse the remus output (PROF: suspend at ..) to see how long a VM remains suspended. On Thu, Feb 28, 2013 at 7:24 AM, agya naila wrote: > Here my lsmod, > > #lsmod > Module Size Used by > xt_tcpudp 12603 1 > xt_physdev 12587 4 > iptable_filter 12810 1 > ip_tables 27473 1 iptable_filter > x_tables 29846 4 > xt_tcpudp,xt_physdev,iptable_filter,ip_tables > drbd 303888 4 > blktap 25553 0 > xen_pciback 48131 0 > xen_netback 27854 0 [permanent] > xen_blkback 23363 0 [permanent] > xen_gntalloc 13321 0 > xen_gntdev 17676 1 > xen_evtchn 13172 2 > xenfs 18311 1 > bridge 90989 0 > stp 12931 1 bridge > dm_multipath 23230 0 > radeon 804372 2 > joydev 17693 0 > ttm 76949 1 radeon > drm_kms_helper 46978 1 radeon > drm 242038 4 radeon,ttm,drm_kms_helper > i2c_algo_bit 13423 1 radeon > bnep 18281 2 > parport_pc 32866 0 > shpchp 37277 0 > bluetooth 180104 7 bnep > ppdev 17113 0 > mac_hid 13253 0 > e752x_edac 18564 0 > edac_core 53746 3 e752x_edac > ifb 12896 0 > act_mirred 13038 0 > cls_u32 17060 0 > cls_tcindex 13058 0 > cls_basic 12946 0 > sch_ingress 12866 0 > sch_prio 13231 0 > sch_plug 12654 0 > lp 17799 0 > parport 46562 3 parport_pc,ppdev,lp > dm_snapshot 39031 3 > usbhid 47199 0 > hid 99559 1 usbhid > usb_storage 49198 0 > mptspi 22921 21 > mptscsih 44882 1 mptspi > mptbase 103162 2 mptspi,mptscsih > tg3 152032 0 > > > Regards, > > Agya > > On Thu, Feb 28, 2013 at 12:29 PM, agya naila wrote: >> >> Hi Andrew and Shiram, >> >> I am keep trying this setting using my machine that I mention earlier in >> this email thread. >> I have using remus with network buffering and no network buffering. >> >> with no network buffering >> #remus --no-net >> >> with network buffering >> #remus >> >> However, when I observed the jitter graph result of my data it seem there >> is no buffering impact on my traffic flow, enclosed both the graph result. I >> only observed RTP packet and observed the jitter. What I could understand >> the graph with network protection will doesn't have flow until x time when >> the buffer released, in this case default value 100ms. Y axis is time and X >> axis is jitter. >> >> Both of command above running without error except suspend event channel >> issue that we discussed earlier. Please suggest. >> >> Regards, >> >> Agya >> >> On Wed, Feb 20, 2013 at 1:13 PM, agya naila wrote: >>> >>> Aha, sorry to mix it :), its clear now. >>> >>> Regards, >>> >>> Agya >>> >>> >>> On Wed, Feb 20, 2013 at 1:01 PM, Andrew Eross wrote: >>>> >>>> Hi Agya, >>>> >>>> This patch doesn't fix the 'suspend event channel' issue, it just fixes >>>> the crash from the first e-mail in this thread. >>>> >>>> Please see this wiki page: >>>> http://wiki.xen.org/wiki/Remus_PV_domU_requirements >>>> >>>> That discusses the suspend event channel issue. >>>> >>>> Cheers, >>>> Andrew >>>> >>>> >>>> On Wed, Feb 20, 2013 at 8:57 AM, agya naila >>>> wrote: >>>>> >>>>> Hello All, >>>>> >>>>> I am trying this patch on my machine Ubuntu 12.04 AMD64 both for Dom0 >>>>> and DomU with Xen 4.2.2-pre compiling from sources also DRBD 8.3.11 but >>>>> unfortunately it seem didn't work since I still got the message WARNING: >>>>> suspend event channel unavailable, falling back to slow xenstore signalling. >>>>> >>>>> Regards, >>>>> >>>>> Agya >>>>> >>>>> On Tue, Feb 19, 2013 at 12:39 PM, Andrew Eross >>>>> wrote: >>>>>> >>>>>> Hi all, >>>>>> >>>>>> To close off on this, Shriram's patch worked great, thank you. >>>>>> >>>>>> So Ubuntu 12.10's standard generic kernel is now working fine as a >>>>>> dom0 for Remus with Xen 4.1.4 (with the patch from this thread). >>>>>> >>>>>> I wrote up my full install instructions here: >>>>>> >>>>>> http://wiki.xen.org/wiki/Install_Xen_4.1.4_with_Remus_and_DRBD_on_Ubuntu_12.10 >>>>>> >>>>>> I also took a shot at a number of updates to: >>>>>> http://wiki.xen.org/wiki/Remus >>>>>> >>>>>> And added these pages: >>>>>> http://wiki.xen.org/wiki/Remus_PV_domU_requirements >>>>>> http://wiki.xen.org/wiki/Remus_dom0_requirements >>>>>> >>>>>> Feedback very welcome, a lot of that information was a bit old, so I >>>>>> did my best. >>>>>> >>>>>> Cheers, >>>>>> Andrew >>>>>> >>>>>> >>>>>> On Mon, Feb 18, 2013 at 8:26 PM, Shriram Rajagopalan >>>>>> wrote: >>>>>>> >>>>>>> ah darn. Yes, the 3.5 kernel has sch_plug in it. Unfortunately, the >>>>>>> technique to initialize the sch_plug module is bit >>>>>>> different with the module thats already mainline. You ll have to >>>>>>> patch >>>>>>> the qdisc.py python module. I ll submit the >>>>>>> patch to xen devel soon. >>>>>>> Mean while, can you try the patch below and see if it works ? >>>>>>> >>>>>>> Secondly, you said you were writing a blog about how you set it up. >>>>>>> One of the remus users created a wiki >>>>>>> remusha.wikidot.com, which has a whole tutorial on how to setup remus >>>>>>> with Debian Squeeze. I have been under fire >>>>>>> lately for a host of remus issues. It would be great if you could >>>>>>> post >>>>>>> your experiences on the wiki too. >>>>>>> (http://remusha.wikidot.com/system:join) >>>>>>> >>>>>>> thanks >>>>>>> shriram >>>>>>> >>>>>>> --- >>>>>>> diff -r 6435f1edf24e tools/python/xen/remus/qdisc.py >>>>>>> --- a/tools/python/xen/remus/qdisc.py Tue Jul 17 19:23:30 2012 >>>>>>> -0400 >>>>>>> +++ b/tools/python/xen/remus/qdisc.py Mon Feb 18 18:25:22 2013 >>>>>>> -0500 >>>>>>> @@ -1,6 +1,9 @@ >>>>>>> import socket, struct >>>>>>> >>>>>>> import netlink >>>>>>> +import platform >>>>>>> + >>>>>>> +kernelversion = >>>>>>> platform.platform(terse=True).split("-")[1].split(".") >>>>>>> >>>>>>> qdisc_kinds = {} >>>>>>> >>>>>>> @@ -150,9 +153,14 @@ >>>>>>> TC_PLUG_RELEASE = 1 >>>>>>> >>>>>>> class PlugQdisc(Qdisc): >>>>>>> - fmt = 'I' >>>>>>> >>>>>>> def __init__(self, qdict=None): >>>>>>> + if int(kernelversion[0]) >= 3 and int(kernelversion[1]) >= >>>>>>> 4: >>>>>>> + self.fmt = 'iI' >>>>>>> + self.limit = 10000 >>>>>>> + else: >>>>>>> + self.fmt = 'I' >>>>>>> + >>>>>>> if not qdict: >>>>>>> qdict = {'kind': 'plug', >>>>>>> 'handle': TC_H_ROOT} >>>>>>> @@ -161,7 +169,10 @@ >>>>>>> self.action = 0 >>>>>>> >>>>>>> def pack(self): >>>>>>> - return struct.pack(self.fmt, self.action) >>>>>>> + if int(kernelversion[0]) >= 3 and int(kernelversion[1]) >= >>>>>>> 4: >>>>>>> + return struct.pack(self.fmt, self.action, self.limit) >>>>>>> + else: >>>>>>> + return struct.pack(self.fmt, self.action) >>>>>>> >>>>>>> def parse(self, args): >>>>>>> if not args: >>>>>> >>>>>> >>>>>> >>>>>> _______________________________________________ >>>>>> 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 Feb 28 14:55:54 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 28 Feb 2013 14:55: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 1UB4sf-0007h9-J3; Thu, 28 Feb 2013 14:54:45 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UB4sd-0007gw-Ku for xen-users@lists.xen.org; Thu, 28 Feb 2013 14:54:43 +0000 Received: from [85.158.137.99:47810] by server-11.bemta-3.messagelabs.com id 96/77-01263-2BF6F215; Thu, 28 Feb 2013 14:54:42 +0000 X-Env-Sender: rshriram@cs.ubc.ca X-Msg-Ref: server-8.tower-217.messagelabs.com!1362063269!13108007!1 X-Originating-IP: [142.103.6.52] X-SpamReason: No, hits=0.8 required=7.0 tests=BODY_RANDOM_LONG, ML_RADAR_SPEW_LINKS_8,RCVD_BY_IP,spamassassin: ,async_handler: YXN5bmNfZGVsYXk6IDcwNDU1MjkgKHRpbWVvdXQp\n X-StarScan-Received: X-StarScan-Version: 6.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 12081 invoked from network); 28 Feb 2013 14:54:31 -0000 Received: from smtp.cs.ubc.ca (HELO smtp.cs.ubc.ca) (142.103.6.52) by server-8.tower-217.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 28 Feb 2013 14:54:31 -0000 Received: from mail-ie0-f181.google.com (mail-ie0-f181.google.com [209.85.223.181]) (authenticated bits=0) by smtp.cs.ubc.ca (8.14.5/8.13.6) with ESMTP id r1SEsR7F001052 (version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=FAIL) for ; Thu, 28 Feb 2013 06:54:28 -0800 Received: by mail-ie0-f181.google.com with SMTP id 17so2167520iea.12 for ; Thu, 28 Feb 2013 06:54:26 -0800 (PST) X-Received: by 10.50.214.67 with SMTP id ny3mr10055574igc.13.1362063266495; Thu, 28 Feb 2013 06:54:26 -0800 (PST) MIME-Version: 1.0 Received: by 10.43.2.67 with HTTP; Thu, 28 Feb 2013 06:53:46 -0800 (PST) In-Reply-To: References: From: Shriram Rajagopalan Date: Thu, 28 Feb 2013 09:53:46 -0500 Message-ID: To: agya naila Cc: "xen-users@lists.xen.org" , Andrew Eross Subject: Re: [Xen-users] Remus dom0 network buffering X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: rshriram@cs.ubc.ca List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org start with a simple test. Ping command. Remember that suspend/resume also takes some time away from the VM. If you are using the slow version of suspend/resume, then that alone could take 10ms or more (to simply suspend/resume). I am not sure if you installed remus from the distribution repo (ubuntu or whatever) or if you compiled from source. If you used a repo version, then you might have to write a script to parse the remus output (PROF: suspend at ..) to see how long a VM remains suspended. On Thu, Feb 28, 2013 at 7:24 AM, agya naila wrote: > Here my lsmod, > > #lsmod > Module Size Used by > xt_tcpudp 12603 1 > xt_physdev 12587 4 > iptable_filter 12810 1 > ip_tables 27473 1 iptable_filter > x_tables 29846 4 > xt_tcpudp,xt_physdev,iptable_filter,ip_tables > drbd 303888 4 > blktap 25553 0 > xen_pciback 48131 0 > xen_netback 27854 0 [permanent] > xen_blkback 23363 0 [permanent] > xen_gntalloc 13321 0 > xen_gntdev 17676 1 > xen_evtchn 13172 2 > xenfs 18311 1 > bridge 90989 0 > stp 12931 1 bridge > dm_multipath 23230 0 > radeon 804372 2 > joydev 17693 0 > ttm 76949 1 radeon > drm_kms_helper 46978 1 radeon > drm 242038 4 radeon,ttm,drm_kms_helper > i2c_algo_bit 13423 1 radeon > bnep 18281 2 > parport_pc 32866 0 > shpchp 37277 0 > bluetooth 180104 7 bnep > ppdev 17113 0 > mac_hid 13253 0 > e752x_edac 18564 0 > edac_core 53746 3 e752x_edac > ifb 12896 0 > act_mirred 13038 0 > cls_u32 17060 0 > cls_tcindex 13058 0 > cls_basic 12946 0 > sch_ingress 12866 0 > sch_prio 13231 0 > sch_plug 12654 0 > lp 17799 0 > parport 46562 3 parport_pc,ppdev,lp > dm_snapshot 39031 3 > usbhid 47199 0 > hid 99559 1 usbhid > usb_storage 49198 0 > mptspi 22921 21 > mptscsih 44882 1 mptspi > mptbase 103162 2 mptspi,mptscsih > tg3 152032 0 > > > Regards, > > Agya > > On Thu, Feb 28, 2013 at 12:29 PM, agya naila wrote: >> >> Hi Andrew and Shiram, >> >> I am keep trying this setting using my machine that I mention earlier in >> this email thread. >> I have using remus with network buffering and no network buffering. >> >> with no network buffering >> #remus --no-net >> >> with network buffering >> #remus >> >> However, when I observed the jitter graph result of my data it seem there >> is no buffering impact on my traffic flow, enclosed both the graph result. I >> only observed RTP packet and observed the jitter. What I could understand >> the graph with network protection will doesn't have flow until x time when >> the buffer released, in this case default value 100ms. Y axis is time and X >> axis is jitter. >> >> Both of command above running without error except suspend event channel >> issue that we discussed earlier. Please suggest. >> >> Regards, >> >> Agya >> >> On Wed, Feb 20, 2013 at 1:13 PM, agya naila wrote: >>> >>> Aha, sorry to mix it :), its clear now. >>> >>> Regards, >>> >>> Agya >>> >>> >>> On Wed, Feb 20, 2013 at 1:01 PM, Andrew Eross wrote: >>>> >>>> Hi Agya, >>>> >>>> This patch doesn't fix the 'suspend event channel' issue, it just fixes >>>> the crash from the first e-mail in this thread. >>>> >>>> Please see this wiki page: >>>> http://wiki.xen.org/wiki/Remus_PV_domU_requirements >>>> >>>> That discusses the suspend event channel issue. >>>> >>>> Cheers, >>>> Andrew >>>> >>>> >>>> On Wed, Feb 20, 2013 at 8:57 AM, agya naila >>>> wrote: >>>>> >>>>> Hello All, >>>>> >>>>> I am trying this patch on my machine Ubuntu 12.04 AMD64 both for Dom0 >>>>> and DomU with Xen 4.2.2-pre compiling from sources also DRBD 8.3.11 but >>>>> unfortunately it seem didn't work since I still got the message WARNING: >>>>> suspend event channel unavailable, falling back to slow xenstore signalling. >>>>> >>>>> Regards, >>>>> >>>>> Agya >>>>> >>>>> On Tue, Feb 19, 2013 at 12:39 PM, Andrew Eross >>>>> wrote: >>>>>> >>>>>> Hi all, >>>>>> >>>>>> To close off on this, Shriram's patch worked great, thank you. >>>>>> >>>>>> So Ubuntu 12.10's standard generic kernel is now working fine as a >>>>>> dom0 for Remus with Xen 4.1.4 (with the patch from this thread). >>>>>> >>>>>> I wrote up my full install instructions here: >>>>>> >>>>>> http://wiki.xen.org/wiki/Install_Xen_4.1.4_with_Remus_and_DRBD_on_Ubuntu_12.10 >>>>>> >>>>>> I also took a shot at a number of updates to: >>>>>> http://wiki.xen.org/wiki/Remus >>>>>> >>>>>> And added these pages: >>>>>> http://wiki.xen.org/wiki/Remus_PV_domU_requirements >>>>>> http://wiki.xen.org/wiki/Remus_dom0_requirements >>>>>> >>>>>> Feedback very welcome, a lot of that information was a bit old, so I >>>>>> did my best. >>>>>> >>>>>> Cheers, >>>>>> Andrew >>>>>> >>>>>> >>>>>> On Mon, Feb 18, 2013 at 8:26 PM, Shriram Rajagopalan >>>>>> wrote: >>>>>>> >>>>>>> ah darn. Yes, the 3.5 kernel has sch_plug in it. Unfortunately, the >>>>>>> technique to initialize the sch_plug module is bit >>>>>>> different with the module thats already mainline. You ll have to >>>>>>> patch >>>>>>> the qdisc.py python module. I ll submit the >>>>>>> patch to xen devel soon. >>>>>>> Mean while, can you try the patch below and see if it works ? >>>>>>> >>>>>>> Secondly, you said you were writing a blog about how you set it up. >>>>>>> One of the remus users created a wiki >>>>>>> remusha.wikidot.com, which has a whole tutorial on how to setup remus >>>>>>> with Debian Squeeze. I have been under fire >>>>>>> lately for a host of remus issues. It would be great if you could >>>>>>> post >>>>>>> your experiences on the wiki too. >>>>>>> (http://remusha.wikidot.com/system:join) >>>>>>> >>>>>>> thanks >>>>>>> shriram >>>>>>> >>>>>>> --- >>>>>>> diff -r 6435f1edf24e tools/python/xen/remus/qdisc.py >>>>>>> --- a/tools/python/xen/remus/qdisc.py Tue Jul 17 19:23:30 2012 >>>>>>> -0400 >>>>>>> +++ b/tools/python/xen/remus/qdisc.py Mon Feb 18 18:25:22 2013 >>>>>>> -0500 >>>>>>> @@ -1,6 +1,9 @@ >>>>>>> import socket, struct >>>>>>> >>>>>>> import netlink >>>>>>> +import platform >>>>>>> + >>>>>>> +kernelversion = >>>>>>> platform.platform(terse=True).split("-")[1].split(".") >>>>>>> >>>>>>> qdisc_kinds = {} >>>>>>> >>>>>>> @@ -150,9 +153,14 @@ >>>>>>> TC_PLUG_RELEASE = 1 >>>>>>> >>>>>>> class PlugQdisc(Qdisc): >>>>>>> - fmt = 'I' >>>>>>> >>>>>>> def __init__(self, qdict=None): >>>>>>> + if int(kernelversion[0]) >= 3 and int(kernelversion[1]) >= >>>>>>> 4: >>>>>>> + self.fmt = 'iI' >>>>>>> + self.limit = 10000 >>>>>>> + else: >>>>>>> + self.fmt = 'I' >>>>>>> + >>>>>>> if not qdict: >>>>>>> qdict = {'kind': 'plug', >>>>>>> 'handle': TC_H_ROOT} >>>>>>> @@ -161,7 +169,10 @@ >>>>>>> self.action = 0 >>>>>>> >>>>>>> def pack(self): >>>>>>> - return struct.pack(self.fmt, self.action) >>>>>>> + if int(kernelversion[0]) >= 3 and int(kernelversion[1]) >= >>>>>>> 4: >>>>>>> + return struct.pack(self.fmt, self.action, self.limit) >>>>>>> + else: >>>>>>> + return struct.pack(self.fmt, self.action) >>>>>>> >>>>>>> def parse(self, args): >>>>>>> if not args: >>>>>> >>>>>> >>>>>> >>>>>> _______________________________________________ >>>>>> 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 Feb 28 15:54:21 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 28 Feb 2013 15:54: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 1UB5nM-00027B-JT; Thu, 28 Feb 2013 15:53:20 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UB5nK-00026y-Q5 for xen-users@lists.xen.org; Thu, 28 Feb 2013 15:53:18 +0000 Received: from [85.158.137.99:52632] by server-9.bemta-3.messagelabs.com id DF/90-32531-96D7F215; Thu, 28 Feb 2013 15:53:13 +0000 X-Env-Sender: jaceksburghardt@gmail.com X-Msg-Ref: server-13.tower-217.messagelabs.com!1362066791!568660!1 X-Originating-IP: [209.85.223.173] X-SpamReason: No, hits=1.9 required=7.0 tests=HTML_MESSAGE, HTML_SHORT_LENGTH,ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 20552 invoked from network); 28 Feb 2013 15:53:12 -0000 Received: from mail-ie0-f173.google.com (HELO mail-ie0-f173.google.com) (209.85.223.173) by server-13.tower-217.messagelabs.com with RC4-SHA encrypted SMTP; 28 Feb 2013 15:53:12 -0000 Received: by mail-ie0-f173.google.com with SMTP id 9so2255235iec.4 for ; Thu, 28 Feb 2013 07:53:11 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:date:message-id:subject:from:to :content-type; bh=tc16LLYYZAikMWKbD4En5UZWGovYYZwADj4JwSLsKrI=; b=uL/9WAQ3FemfZ/aZ0QzbV3UZnU/nYi1j8kBYJM0DpaEitJYTe0MBgaAnrQ7+NqVqxO b1UIsCzJd3fYtIl96cGGKUDTZLXKruvaX8s8CzkxNUu8MN+DIMOPOB8DHkn0Nmh1f4iY uwJipHS1fS1QZE0OcVTiTdlVa8/e3IOXtmmiZZ8Rjg+rPZwWxS+uDZVJWu17ShXmIdiG vu4qH95krb/yvb7ekHGDFImVQHPN4wzpphWHHVYTcudl3P1yE/PzLbXsjRalyWRPQtiH 3Y1fc8MulosHlhHhca9MLoIyC93OjrJG8ZPhHZJMi+qqF+ljM7uEloglniQRBmOHJVE2 PD4g== MIME-Version: 1.0 X-Received: by 10.50.17.163 with SMTP id p3mr3883587igd.90.1362066791189; Thu, 28 Feb 2013 07:53:11 -0800 (PST) Received: by 10.42.41.5 with HTTP; Thu, 28 Feb 2013 07:53:10 -0800 (PST) Date: Thu, 28 Feb 2013 08:53:10 -0700 Message-ID: From: jacek burghardt To: xen-users Subject: [Xen-users] xen 4.3 unstable and spice protocol X-BeenThere: xen-users@lists.xen.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="===============2031641717182005665==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============2031641717182005665== Content-Type: multipart/alternative; boundary=14dae93407cf3fd38b04d6cae305 --14dae93407cf3fd38b04d6cae305 Content-Type: text/plain; charset=ISO-8859-1 I wonder if there is package for any of Linux distribution that is compiled on xen-4.3 unstable with spice protocol? --14dae93407cf3fd38b04d6cae305 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable I wonder if there is package for any of=A0Linux=A0distribution that is comp= iled on xen-4.3 unstable with spice protocol?=A0 --14dae93407cf3fd38b04d6cae305-- --===============2031641717182005665== 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 --===============2031641717182005665==-- From xen-users-bounces@lists.xen.org Thu Feb 28 15:54:21 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 28 Feb 2013 15:54: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 1UB5nM-00027B-JT; Thu, 28 Feb 2013 15:53:20 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UB5nK-00026y-Q5 for xen-users@lists.xen.org; Thu, 28 Feb 2013 15:53:18 +0000 Received: from [85.158.137.99:52632] by server-9.bemta-3.messagelabs.com id DF/90-32531-96D7F215; Thu, 28 Feb 2013 15:53:13 +0000 X-Env-Sender: jaceksburghardt@gmail.com X-Msg-Ref: server-13.tower-217.messagelabs.com!1362066791!568660!1 X-Originating-IP: [209.85.223.173] X-SpamReason: No, hits=1.9 required=7.0 tests=HTML_MESSAGE, HTML_SHORT_LENGTH,ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 20552 invoked from network); 28 Feb 2013 15:53:12 -0000 Received: from mail-ie0-f173.google.com (HELO mail-ie0-f173.google.com) (209.85.223.173) by server-13.tower-217.messagelabs.com with RC4-SHA encrypted SMTP; 28 Feb 2013 15:53:12 -0000 Received: by mail-ie0-f173.google.com with SMTP id 9so2255235iec.4 for ; Thu, 28 Feb 2013 07:53:11 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:date:message-id:subject:from:to :content-type; bh=tc16LLYYZAikMWKbD4En5UZWGovYYZwADj4JwSLsKrI=; b=uL/9WAQ3FemfZ/aZ0QzbV3UZnU/nYi1j8kBYJM0DpaEitJYTe0MBgaAnrQ7+NqVqxO b1UIsCzJd3fYtIl96cGGKUDTZLXKruvaX8s8CzkxNUu8MN+DIMOPOB8DHkn0Nmh1f4iY uwJipHS1fS1QZE0OcVTiTdlVa8/e3IOXtmmiZZ8Rjg+rPZwWxS+uDZVJWu17ShXmIdiG vu4qH95krb/yvb7ekHGDFImVQHPN4wzpphWHHVYTcudl3P1yE/PzLbXsjRalyWRPQtiH 3Y1fc8MulosHlhHhca9MLoIyC93OjrJG8ZPhHZJMi+qqF+ljM7uEloglniQRBmOHJVE2 PD4g== MIME-Version: 1.0 X-Received: by 10.50.17.163 with SMTP id p3mr3883587igd.90.1362066791189; Thu, 28 Feb 2013 07:53:11 -0800 (PST) Received: by 10.42.41.5 with HTTP; Thu, 28 Feb 2013 07:53:10 -0800 (PST) Date: Thu, 28 Feb 2013 08:53:10 -0700 Message-ID: From: jacek burghardt To: xen-users Subject: [Xen-users] xen 4.3 unstable and spice protocol X-BeenThere: xen-users@lists.xen.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="===============2031641717182005665==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============2031641717182005665== Content-Type: multipart/alternative; boundary=14dae93407cf3fd38b04d6cae305 --14dae93407cf3fd38b04d6cae305 Content-Type: text/plain; charset=ISO-8859-1 I wonder if there is package for any of Linux distribution that is compiled on xen-4.3 unstable with spice protocol? --14dae93407cf3fd38b04d6cae305 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable I wonder if there is package for any of=A0Linux=A0distribution that is comp= iled on xen-4.3 unstable with spice protocol?=A0 --14dae93407cf3fd38b04d6cae305-- --===============2031641717182005665== 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 --===============2031641717182005665==-- From xen-users-bounces@lists.xen.org Thu Feb 28 16:42:13 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 28 Feb 2013 16:42: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 1UB6Xl-0006Ay-NS; Thu, 28 Feb 2013 16:41:17 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UB6Xj-0006Aj-Oi for xen-users@lists.xen.org; Thu, 28 Feb 2013 16:41:16 +0000 Received: from [85.158.137.99:64834] by server-2.bemta-3.messagelabs.com id 33/3F-05208-6A88F215; Thu, 28 Feb 2013 16:41:10 +0000 X-Env-Sender: agya.naila@gmail.com X-Msg-Ref: server-12.tower-217.messagelabs.com!1362069655!15201293!1 X-Originating-IP: [74.125.82.42] X-SpamReason: No, hits=1.4 required=7.0 tests=BODY_RANDOM_LONG, HTML_40_50,HTML_MESSAGE,ML_RADAR_SPEW_LINKS_14,ML_RADAR_SPEW_LINKS_8, RCVD_BY_IP,spamassassin: ,async_handler: YXN5bmNfZGVsYXk6IDcwNDY3MzggKHRpbWVvdXQp\n X-StarScan-Received: X-StarScan-Version: 6.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 17706 invoked from network); 28 Feb 2013 16:40:55 -0000 Received: from mail-wg0-f42.google.com (HELO mail-wg0-f42.google.com) (74.125.82.42) by server-12.tower-217.messagelabs.com with RC4-SHA encrypted SMTP; 28 Feb 2013 16:40:55 -0000 Received: by mail-wg0-f42.google.com with SMTP id 12so6471486wgh.1 for ; Thu, 28 Feb 2013 08:40:55 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=493tYLoZROPX6XD34oUp0JV0/26vZQ4siR5fO8O81Lw=; b=OjU+6OUjSURAzrTLP+Iki6aWszv9YPy3fKcQvo8IeGlrAaIg5p7TTkl8w3bOD+vegR ulayJHMBl6yZoZuOw+ATk9yoWfBt8snKNZKSWvAG4Ed0VL+JeMd53u5L7XlszBNYFN4t PcB8QR3JomTADeqNstEfPdGdqcRDKMknA5i2fGvJowkOCuZrt0q9cNIv8AzdTPJHW/CQ OFTLgIgAn5lzvPfrwLmJE8QYHmyX2A8l2kjsK/WrcPsSeq/c/tIs3YI8QMc9VNZrZLCc cX6O4w9jkkhDqmfJxo/BDO3AqDOpLTIK+xsL48W7o3xnoHdHdtceJaR7Rjc9mCmG1jkl qarQ== MIME-Version: 1.0 X-Received: by 10.180.78.35 with SMTP id y3mr11911054wiw.22.1362069654940; Thu, 28 Feb 2013 08:40:54 -0800 (PST) Received: by 10.216.236.13 with HTTP; Thu, 28 Feb 2013 08:40:54 -0800 (PST) In-Reply-To: References: Date: Thu, 28 Feb 2013 17:40:54 +0100 Message-ID: From: agya naila To: rshriram@cs.ubc.ca Cc: "xen-users@lists.xen.org" , Andrew Eross Subject: Re: [Xen-users] Remus dom0 network buffering X-BeenThere: xen-users@lists.xen.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="===============3993726516882215221==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============3993726516882215221== Content-Type: multipart/alternative; boundary=f46d043c7b84f1323704d6cb8dfb --f46d043c7b84f1323704d6cb8dfb Content-Type: text/plain; charset=ISO-8859-1 Hi Shriram, Thank you for reply, I am using Xen version: 4.2.2-pre compiled from sources with kernel 3.2.0-29-generic ~$ dmesg | grep Xen\ version [ 0.000000] Xen version: 4.2.2-pre (preserve-AD) ~$ uname -a Linux comp1 3.2.0-29-generic #46-Ubuntu SMP Fri Jul 27 17:03:23 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux I have try to do simple measurement with ping command but still didn't got satisfying result. Ping domU no migration : C:\Users\rdc>ping 192.168.129.55 -t Pinging 192.168.129.55 with 32 bytes of data: Reply from 192.168.129.55: bytes=32 time=1ms TTL=64 Reply from 192.168.129.55: bytes=32 time<1ms TTL=64 Reply from 192.168.129.55: bytes=32 time<1ms TTL=64 Reply from 192.168.129.55: bytes=32 time<1ms TTL=64 Reply from 192.168.129.55: bytes=32 time=1ms TTL=64 Reply from 192.168.129.55: bytes=32 time=1ms TTL=64 Reply from 192.168.129.55: bytes=32 time<1ms TTL=64 Reply from 192.168.129.55: bytes=32 time<1ms TTL=64 Reply from 192.168.129.55: bytes=32 time<1ms TTL=64 Reply from 192.168.129.55: bytes=32 time<1ms TTL=64 Reply from 192.168.129.55: bytes=32 time=2ms TTL=64 Reply from 192.168.129.55: bytes=32 time=1ms TTL=64 Reply from 192.168.129.55: bytes=32 time=1ms TTL=64 Reply from 192.168.129.55: bytes=32 time=3ms TTL=64 Reply from 192.168.129.55: bytes=32 time<1ms TTL=64 Reply from 192.168.129.55: bytes=32 time<1ms TTL=64 Reply from 192.168.129.55: bytes=32 time<1ms TTL=64 Reply from 192.168.129.55: bytes=32 time<1ms TTL=64 Reply from 192.168.129.55: bytes=32 time<1ms TTL=64 Reply from 192.168.129.55: bytes=32 time<1ms TTL=64 Reply from 192.168.129.55: bytes=32 time=4ms TTL=64 Ping domU with migration but without network bufering : C:\Users\rdc>ping 192.168.129.55 -t Pinging 192.168.129.55 with 32 bytes of data: Reply from 192.168.129.55: bytes=32 time=7ms TTL=64 Reply from 192.168.129.55: bytes=32 time=8ms TTL=64 Reply from 192.168.129.55: bytes=32 time=1ms TTL=64 Reply from 192.168.129.55: bytes=32 time=1ms TTL=64 Reply from 192.168.129.55: bytes=32 time=11ms TTL=64 Reply from 192.168.129.55: bytes=32 time=3ms TTL=64 Reply from 192.168.129.55: bytes=32 time<1ms TTL=64 Reply from 192.168.129.55: bytes=32 time=3ms TTL=64 Reply from 192.168.129.55: bytes=32 time<1ms TTL=64 Reply from 192.168.129.55: bytes=32 time<1ms TTL=64 Reply from 192.168.129.55: bytes=32 time<1ms TTL=64 Reply from 192.168.129.55: bytes=32 time=3ms TTL=64 Reply from 192.168.129.55: bytes=32 time<1ms TTL=64 Reply from 192.168.129.55: bytes=32 time<1ms TTL=64 Reply from 192.168.129.55: bytes=32 time<1ms TTL=64 Reply from 192.168.129.55: bytes=32 time=2ms TTL=64 Reply from 192.168.129.55: bytes=32 time<1ms TTL=64 Reply from 192.168.129.55: bytes=32 time<1ms TTL=64 Reply from 192.168.129.55: bytes=32 time<1ms TTL=64 Reply from 192.168.129.55: bytes=32 time<1ms TTL=64 Reply from 192.168.129.55: bytes=32 time<1ms TTL=64 Reply from 192.168.129.55: bytes=32 time=2ms TTL=64 Reply from 192.168.129.55: bytes=32 time<1ms TTL=64 Reply from 192.168.129.55: bytes=32 time=12ms TTL=64 Ping domU with migration and network bufering : C:\Users\rdc>ping 192.168.129.55 -t Pinging 192.168.129.55 with 32 bytes of data: Reply from 192.168.129.55: bytes=32 time=1ms TTL=64 Reply from 192.168.129.55: bytes=32 time<1ms TTL=64 Reply from 192.168.129.55: bytes=32 time=6ms TTL=64 Reply from 192.168.129.55: bytes=32 time<1ms TTL=64 Reply from 192.168.129.55: bytes=32 time<1ms TTL=64 Reply from 192.168.129.55: bytes=32 time=1ms TTL=64 Reply from 192.168.129.55: bytes=32 time<1ms TTL=64 Reply from 192.168.129.55: bytes=32 time<1ms TTL=64 Reply from 192.168.129.55: bytes=32 time<1ms TTL=64 Reply from 192.168.129.55: bytes=32 time<1ms TTL=64 Reply from 192.168.129.55: bytes=32 time<1ms TTL=64 Reply from 192.168.129.55: bytes=32 time=4ms TTL=64 Reply from 192.168.129.55: bytes=32 time<1ms TTL=64 Reply from 192.168.129.55: bytes=32 time=1ms TTL=64 Reply from 192.168.129.55: bytes=32 time<1ms TTL=64 Reply from 192.168.129.55: bytes=32 time<1ms TTL=64 Reply from 192.168.129.55: bytes=32 time<1ms TTL=64 Reply from 192.168.129.55: bytes=32 time<1ms TTL=64 Reply from 192.168.129.55: bytes=32 time<1ms TTL=64 Reply from 192.168.129.55: bytes=32 time<1ms TTL=64 Reply from 192.168.129.55: bytes=32 time<1ms TTL=64 Here some sampe of remus output (with network buffering) : user1@comp1:~$ sudo remus 1 10.10.10.3 WARNING: suspend event channel unavailable, falling back to slow xenstore signalling PROF: suspending at 1362068953.644729 PROF: resumed at 1362068953.658836 PROF: flushed memory at 1362068953.669453 PROF: suspending at 1362068953.854217 PROF: resumed at 1362068953.868208 PROF: flushed memory at 1362068953.877483 PROF: suspending at 1362068954.063650 PROF: resumed at 1362068954.08 Could you point out something? Regards, Agya On Thu, Feb 28, 2013 at 3:53 PM, Shriram Rajagopalan wrote: > start with a simple test. Ping command. > Remember that suspend/resume also takes some time away from the VM. > If you are using the slow version of suspend/resume, then that alone could > take > 10ms or more (to simply suspend/resume). > > I am not sure if you installed remus from the distribution repo > (ubuntu or whatever) > or if you compiled from source. If you used a repo version, then you > might have to > write a script to parse the remus output (PROF: suspend at ..) to see > how long a VM remains > suspended. > > > On Thu, Feb 28, 2013 at 7:24 AM, agya naila wrote: > > Here my lsmod, > > > > #lsmod > > Module Size Used by > > xt_tcpudp 12603 1 > > xt_physdev 12587 4 > > iptable_filter 12810 1 > > ip_tables 27473 1 iptable_filter > > x_tables 29846 4 > > xt_tcpudp,xt_physdev,iptable_filter,ip_tables > > drbd 303888 4 > > blktap 25553 0 > > xen_pciback 48131 0 > > xen_netback 27854 0 [permanent] > > xen_blkback 23363 0 [permanent] > > xen_gntalloc 13321 0 > > xen_gntdev 17676 1 > > xen_evtchn 13172 2 > > xenfs 18311 1 > > bridge 90989 0 > > stp 12931 1 bridge > > dm_multipath 23230 0 > > radeon 804372 2 > > joydev 17693 0 > > ttm 76949 1 radeon > > drm_kms_helper 46978 1 radeon > > drm 242038 4 radeon,ttm,drm_kms_helper > > i2c_algo_bit 13423 1 radeon > > bnep 18281 2 > > parport_pc 32866 0 > > shpchp 37277 0 > > bluetooth 180104 7 bnep > > ppdev 17113 0 > > mac_hid 13253 0 > > e752x_edac 18564 0 > > edac_core 53746 3 e752x_edac > > ifb 12896 0 > > act_mirred 13038 0 > > cls_u32 17060 0 > > cls_tcindex 13058 0 > > cls_basic 12946 0 > > sch_ingress 12866 0 > > sch_prio 13231 0 > > sch_plug 12654 0 > > lp 17799 0 > > parport 46562 3 parport_pc,ppdev,lp > > dm_snapshot 39031 3 > > usbhid 47199 0 > > hid 99559 1 usbhid > > usb_storage 49198 0 > > mptspi 22921 21 > > mptscsih 44882 1 mptspi > > mptbase 103162 2 mptspi,mptscsih > > tg3 152032 0 > > > > > > Regards, > > > > Agya > > > > On Thu, Feb 28, 2013 at 12:29 PM, agya naila > wrote: > >> > >> Hi Andrew and Shiram, > >> > >> I am keep trying this setting using my machine that I mention earlier in > >> this email thread. > >> I have using remus with network buffering and no network buffering. > >> > >> with no network buffering > >> #remus --no-net > >> > >> with network buffering > >> #remus > >> > >> However, when I observed the jitter graph result of my data it seem > there > >> is no buffering impact on my traffic flow, enclosed both the graph > result. I > >> only observed RTP packet and observed the jitter. What I could > understand > >> the graph with network protection will doesn't have flow until x time > when > >> the buffer released, in this case default value 100ms. Y axis is time > and X > >> axis is jitter. > >> > >> Both of command above running without error except suspend event > channel > >> issue that we discussed earlier. Please suggest. > >> > >> Regards, > >> > >> Agya > >> > >> On Wed, Feb 20, 2013 at 1:13 PM, agya naila > wrote: > >>> > >>> Aha, sorry to mix it :), its clear now. > >>> > >>> Regards, > >>> > >>> Agya > >>> > >>> > >>> On Wed, Feb 20, 2013 at 1:01 PM, Andrew Eross > wrote: > >>>> > >>>> Hi Agya, > >>>> > >>>> This patch doesn't fix the 'suspend event channel' issue, it just > fixes > >>>> the crash from the first e-mail in this thread. > >>>> > >>>> Please see this wiki page: > >>>> http://wiki.xen.org/wiki/Remus_PV_domU_requirements > >>>> > >>>> That discusses the suspend event channel issue. > >>>> > >>>> Cheers, > >>>> Andrew > >>>> > >>>> > >>>> On Wed, Feb 20, 2013 at 8:57 AM, agya naila > >>>> wrote: > >>>>> > >>>>> Hello All, > >>>>> > >>>>> I am trying this patch on my machine Ubuntu 12.04 AMD64 both for Dom0 > >>>>> and DomU with Xen 4.2.2-pre compiling from sources also DRBD 8.3.11 > but > >>>>> unfortunately it seem didn't work since I still got the message > WARNING: > >>>>> suspend event channel unavailable, falling back to slow xenstore > signalling. > >>>>> > >>>>> Regards, > >>>>> > >>>>> Agya > >>>>> > >>>>> On Tue, Feb 19, 2013 at 12:39 PM, Andrew Eross > >>>>> wrote: > >>>>>> > >>>>>> Hi all, > >>>>>> > >>>>>> To close off on this, Shriram's patch worked great, thank you. > >>>>>> > >>>>>> So Ubuntu 12.10's standard generic kernel is now working fine as a > >>>>>> dom0 for Remus with Xen 4.1.4 (with the patch from this thread). > >>>>>> > >>>>>> I wrote up my full install instructions here: > >>>>>> > >>>>>> > http://wiki.xen.org/wiki/Install_Xen_4.1.4_with_Remus_and_DRBD_on_Ubuntu_12.10 > >>>>>> > >>>>>> I also took a shot at a number of updates to: > >>>>>> http://wiki.xen.org/wiki/Remus > >>>>>> > >>>>>> And added these pages: > >>>>>> http://wiki.xen.org/wiki/Remus_PV_domU_requirements > >>>>>> http://wiki.xen.org/wiki/Remus_dom0_requirements > >>>>>> > >>>>>> Feedback very welcome, a lot of that information was a bit old, so I > >>>>>> did my best. > >>>>>> > >>>>>> Cheers, > >>>>>> Andrew > >>>>>> > >>>>>> > >>>>>> On Mon, Feb 18, 2013 at 8:26 PM, Shriram Rajagopalan > >>>>>> wrote: > >>>>>>> > >>>>>>> ah darn. Yes, the 3.5 kernel has sch_plug in it. Unfortunately, the > >>>>>>> technique to initialize the sch_plug module is bit > >>>>>>> different with the module thats already mainline. You ll have to > >>>>>>> patch > >>>>>>> the qdisc.py python module. I ll submit the > >>>>>>> patch to xen devel soon. > >>>>>>> Mean while, can you try the patch below and see if it works ? > >>>>>>> > >>>>>>> Secondly, you said you were writing a blog about how you set it up. > >>>>>>> One of the remus users created a wiki > >>>>>>> remusha.wikidot.com, which has a whole tutorial on how to setup > remus > >>>>>>> with Debian Squeeze. I have been under fire > >>>>>>> lately for a host of remus issues. It would be great if you could > >>>>>>> post > >>>>>>> your experiences on the wiki too. > >>>>>>> (http://remusha.wikidot.com/system:join) > >>>>>>> > >>>>>>> thanks > >>>>>>> shriram > >>>>>>> > >>>>>>> --- > >>>>>>> diff -r 6435f1edf24e tools/python/xen/remus/qdisc.py > >>>>>>> --- a/tools/python/xen/remus/qdisc.py Tue Jul 17 19:23:30 2012 > >>>>>>> -0400 > >>>>>>> +++ b/tools/python/xen/remus/qdisc.py Mon Feb 18 18:25:22 2013 > >>>>>>> -0500 > >>>>>>> @@ -1,6 +1,9 @@ > >>>>>>> import socket, struct > >>>>>>> > >>>>>>> import netlink > >>>>>>> +import platform > >>>>>>> + > >>>>>>> +kernelversion = > >>>>>>> platform.platform(terse=True).split("-")[1].split(".") > >>>>>>> > >>>>>>> qdisc_kinds = {} > >>>>>>> > >>>>>>> @@ -150,9 +153,14 @@ > >>>>>>> TC_PLUG_RELEASE = 1 > >>>>>>> > >>>>>>> class PlugQdisc(Qdisc): > >>>>>>> - fmt = 'I' > >>>>>>> > >>>>>>> def __init__(self, qdict=None): > >>>>>>> + if int(kernelversion[0]) >= 3 and int(kernelversion[1]) >= > >>>>>>> 4: > >>>>>>> + self.fmt = 'iI' > >>>>>>> + self.limit = 10000 > >>>>>>> + else: > >>>>>>> + self.fmt = 'I' > >>>>>>> + > >>>>>>> if not qdict: > >>>>>>> qdict = {'kind': 'plug', > >>>>>>> 'handle': TC_H_ROOT} > >>>>>>> @@ -161,7 +169,10 @@ > >>>>>>> self.action = 0 > >>>>>>> > >>>>>>> def pack(self): > >>>>>>> - return struct.pack(self.fmt, self.action) > >>>>>>> + if int(kernelversion[0]) >= 3 and int(kernelversion[1]) >= > >>>>>>> 4: > >>>>>>> + return struct.pack(self.fmt, self.action, self.limit) > >>>>>>> + else: > >>>>>>> + return struct.pack(self.fmt, self.action) > >>>>>>> > >>>>>>> def parse(self, args): > >>>>>>> if not args: > >>>>>> > >>>>>> > >>>>>> > >>>>>> _______________________________________________ > >>>>>> Xen-users mailing list > >>>>>> Xen-users@lists.xen.org > >>>>>> http://lists.xen.org/xen-users > >>>>> > >>>>> > >>>> > >>> > >> > > > --f46d043c7b84f1323704d6cb8dfb Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Hi Shriram,

Thank you for reply, I am using =A0Xen versi= on: 4.2.2-pre compiled from sources with kernel 3.2.0-29-generic
=
~$ dmesg | grep Xen\ version
[ =A0 =A00.00000= 0] Xen version: 4.2.2-pre (preserve-AD)

~$ uname -a
Linux comp1 3.2.0-29-generic= #46-Ubuntu SMP Fri Jul 27 17:03:23 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux=

I have try to do simple measurement with pi= ng command but still didn't got satisfying result.

Ping domU no migration :
C:\Users\rdc>= ;ping 192.168.129.55 -t

Pinging 192.168.129.55 wit= h 32 bytes of data:
Reply from = 192.168.129.55: bytes=3D32 time=3D1ms TTL=3D64
Reply from 192.168.129.55: bytes= =3D32 time<1ms TTL=3D64
Reply from 192.168.129.55: bytes=3D32 time<1ms TTL=3D64
Reply = from 192.168.129.55: bytes=3D32 time&= lt;1ms TTL=3D64
Reply from 192.168.129.55: bytes= =3D32 time=3D1ms TTL=3D64
Reply from 192.168.129.55: bytes=3D32 time=3D1ms TTL=3D64
Reply fr= om 192.168.129.55: bytes=3D32 time<= ;1ms TTL=3D64
Reply from 192.168.129.55: bytes= =3D32 time<1ms TTL=3D64
Reply from 192.168.129.55: bytes=3D32 time<1ms TTL=3D64
Reply = from 192.168.129.55: bytes=3D32 time&= lt;1ms TTL=3D64
Reply from 192.168.129.55: bytes= =3D32 time=3D2ms TTL=3D64
Reply from 192.168.129.55: bytes=3D32 time=3D1ms TTL=3D64
Reply fr= om 192.168.129.55: bytes=3D32 time=3D= 1ms TTL=3D64
Reply from 192.168.129.55: bytes= =3D32 time=3D3ms TTL=3D64
Reply from 192.168.129.55: bytes=3D32 time<1ms TTL=3D64
Reply f= rom 192.168.129.55: bytes=3D32 time&l= t;1ms TTL=3D64
Reply from 192.168.129.55: bytes= =3D32 time<1ms TTL=3D64
Reply from 192.168.129.55: bytes=3D32 time<1ms TTL=3D64
Reply = from 192.168.129.55: bytes=3D32 time&= lt;1ms TTL=3D64
Reply from 192.168.129.55: bytes= =3D32 time<1ms TTL=3D64
Reply from 192.168.129.55: bytes=3D32 time=3D4ms TTL=3D64
<= br>
Ping domU with migration but without network bufering :
C:\Users\rdc>ping 192.168.129.55 -t

P= inging 192.168.129.55 with 32 bytes of data:
Reply from 192.168.129.55: bytes=3D32 time=3D7ms TTL=3D= 64
Reply from 192.168.129.55: bytes= =3D32 time=3D8ms TTL=3D64
Reply from 192.168.129.55: bytes=3D32 time=3D1ms TTL=3D64
Reply fr= om 192.168.129.55: bytes=3D32 time=3D= 1ms TTL=3D64
Reply from 192.168.129.55: bytes= =3D32 time=3D11ms TTL=3D64
Reply from 192.168.129.55: bytes=3D32 time=3D3ms TTL=3D64
Reply f= rom 192.168.129.55: bytes=3D32 time&l= t;1ms TTL=3D64
Reply from 192.168.129.55: bytes= =3D32 time=3D3ms TTL=3D64
Reply from 192.168.129.55: bytes=3D32 time<1ms TTL=3D64
Reply f= rom 192.168.129.55: bytes=3D32 time&l= t;1ms TTL=3D64
Reply from 192.168.129.55: bytes= =3D32 time<1ms TTL=3D64
Reply from 192.168.129.55: bytes=3D32 time=3D3ms TTL=3D64
Reply f= rom 192.168.129.55: bytes=3D32 time&l= t;1ms TTL=3D64
Reply from 192.168.129.55: bytes= =3D32 time<1ms TTL=3D64
Reply from 192.168.129.55: bytes=3D32 time<1ms TTL=3D64
Reply = from 192.168.129.55: bytes=3D32 time= =3D2ms TTL=3D64
Reply from 192.168.129.55: bytes= =3D32 time<1ms TTL=3D64
Reply from 192.168.129.55: bytes=3D32 time<1ms TTL=3D64
Reply = from 192.168.129.55: bytes=3D32 time&= lt;1ms TTL=3D64
Reply from 192.168.129.55: bytes= =3D32 time<1ms TTL=3D64
Reply from 192.168.129.55: bytes=3D32 time<1ms TTL=3D64
Reply = from 192.168.129.55: bytes=3D32 time= =3D2ms TTL=3D64
Reply from 192.168.129.55: bytes= =3D32 time<1ms TTL=3D64
Reply from 192.168.129.55: bytes=3D32 time=3D12ms TTL=3D64


Ping domU with migration and network bufering :
C= :\Users\rdc>ping 192.168.129.55 -t

P= inging 192.168.129.55 with 32 bytes of data:
Reply from 192.168.129.55: bytes=3D32 time=3D1ms TTL=3D= 64
Reply from 192.168.129.55: bytes= =3D32 time<1ms TTL=3D64
Reply from 192.168.129.55: bytes=3D32 time=3D6ms TTL=3D64
Reply f= rom 192.168.129.55: bytes=3D32 time&l= t;1ms TTL=3D64
Reply from 192.168.129.55: bytes= =3D32 time<1ms TTL=3D64
Reply from 192.168.129.55: bytes=3D32 time=3D1ms TTL=3D64
Reply f= rom 192.168.129.55: bytes=3D32 time&l= t;1ms TTL=3D64
Reply from 192.168.129.55: bytes= =3D32 time<1ms TTL=3D64
Reply from 192.168.129.55: bytes=3D32 time<1ms TTL=3D64
Reply = from 192.168.129.55: bytes=3D32 time&= lt;1ms TTL=3D64
Reply from 192.168.129.55: bytes= =3D32 time<1ms TTL=3D64
Reply from 192.168.129.55: bytes=3D32 time=3D4ms TTL=3D64
Reply f= rom 192.168.129.55: bytes=3D32 time&l= t;1ms TTL=3D64
Reply from 192.168.129.55: bytes= =3D32 time=3D1ms TTL=3D64
Reply from 192.168.129.55: bytes=3D32 time<1ms TTL=3D64
Reply f= rom 192.168.129.55: bytes=3D32 time&l= t;1ms TTL=3D64
Reply from 192.168.129.55: bytes= =3D32 time<1ms TTL=3D64
Reply from 192.168.129.55: bytes=3D32 time<1ms TTL=3D64
Reply = from 192.168.129.55: bytes=3D32 time&= lt;1ms TTL=3D64
Reply from 192.168.129.55: bytes= =3D32 time<1ms TTL=3D64
Reply from 192.168.129.55: bytes=3D32 time<1ms TTL=3D64
=
Here some sampe of remus output (with network buffering) :
<= div>user1@comp1:~$ sudo remus 1 10.10.10.3
WARNING: suspend event= channel unavailable, falling back to slow xenstore signalling
PROF: suspending at 1362068953.644729
PROF: resumed at 1362068953= .658836
PROF: flushed memory at 1362068953.669453
PROF:= suspending at 1362068953.854217
PROF: resumed at 1362068953.8682= 08
PROF: flushed memory at 1362068953.877483
PROF: suspending a= t 1362068954.063650
PROF: resumed at 1362068954.08

Could you point out something?

Regards,

Agya


<= div class=3D"gmail_quote">On Thu, Feb 28, 2013 at 3:53 PM, Shriram Rajagopa= lan <rshriram@cs.ubc.ca> wrote:
start with a simple test. Ping command.
Remember that suspend/resume also takes some time away from the VM.
If you are using the slow version of suspend/resume, then that alone could = take
10ms or more (to simply suspend/resume).

I am not sure if you installed remus from the distribution repo
(ubuntu or whatever)
or if you compiled from source. If you used a repo version, then you
might have to
write a script to parse the remus output (PROF: suspend at ..) to see
how long a VM remains
suspended.


On Thu, Feb 28, 2013 at 7:24 AM, agya naila <agya.naila@gmail.com> wrote:
> Here my lsmod,
>
> =A0#lsmod
> Module =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0Size =A0Used by
> xt_tcpudp =A0 =A0 =A0 =A0 =A0 =A0 =A012603 =A01
> xt_physdev =A0 =A0 =A0 =A0 =A0 =A0 12587 =A04
> iptable_filter =A0 =A0 =A0 =A0 12810 =A01
> ip_tables =A0 =A0 =A0 =A0 =A0 =A0 =A027473 =A01 iptable_filter
> x_tables =A0 =A0 =A0 =A0 =A0 =A0 =A0 29846 =A04
> xt_tcpudp,xt_physdev,iptable_filter,ip_tables
> drbd =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0303888 =A04
> blktap =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 25553 =A00
> xen_pciback =A0 =A0 =A0 =A0 =A0 =A048131 =A00
> xen_netback =A0 =A0 =A0 =A0 =A0 =A027854 =A00 [permanent]
> xen_blkback =A0 =A0 =A0 =A0 =A0 =A023363 =A00 [permanent]
> xen_gntalloc =A0 =A0 =A0 =A0 =A0 13321 =A00
> xen_gntdev =A0 =A0 =A0 =A0 =A0 =A0 17676 =A01
> xen_evtchn =A0 =A0 =A0 =A0 =A0 =A0 13172 =A02
> xenfs =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A018311 =A01
> bridge =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 90989 =A00
> stp =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A012931 =A01 bridge
> dm_multipath =A0 =A0 =A0 =A0 =A0 23230 =A00
> radeon =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0804372 =A02
> joydev =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 17693 =A00
> ttm =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A076949 =A01 radeon
> drm_kms_helper =A0 =A0 =A0 =A0 46978 =A01 radeon
> drm =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 242038 =A04 radeon,ttm,drm_kms= _helper
> i2c_algo_bit =A0 =A0 =A0 =A0 =A0 13423 =A01 radeon
> bnep =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 18281 =A02
> parport_pc =A0 =A0 =A0 =A0 =A0 =A0 32866 =A00
> shpchp =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 37277 =A00
> bluetooth =A0 =A0 =A0 =A0 =A0 =A0 180104 =A07 bnep
> ppdev =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A017113 =A00
> mac_hid =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A013253 =A00
> e752x_edac =A0 =A0 =A0 =A0 =A0 =A0 18564 =A00
> edac_core =A0 =A0 =A0 =A0 =A0 =A0 =A053746 =A03 e752x_edac
> ifb =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A012896 =A00
> act_mirred =A0 =A0 =A0 =A0 =A0 =A0 13038 =A00
> cls_u32 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A017060 =A00
> cls_tcindex =A0 =A0 =A0 =A0 =A0 =A013058 =A00
> cls_basic =A0 =A0 =A0 =A0 =A0 =A0 =A012946 =A00
> sch_ingress =A0 =A0 =A0 =A0 =A0 =A012866 =A00
> sch_prio =A0 =A0 =A0 =A0 =A0 =A0 =A0 13231 =A00
> sch_plug =A0 =A0 =A0 =A0 =A0 =A0 =A0 12654 =A00
> lp =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 17799 =A00
> parport =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A046562 =A03 parport_pc,ppdev,lp<= br> > dm_snapshot =A0 =A0 =A0 =A0 =A0 =A039031 =A03
> usbhid =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 47199 =A00
> hid =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A099559 =A01 usbhid
> usb_storage =A0 =A0 =A0 =A0 =A0 =A049198 =A00
> mptspi =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 22921 =A021
> mptscsih =A0 =A0 =A0 =A0 =A0 =A0 =A0 44882 =A01 mptspi
> mptbase =A0 =A0 =A0 =A0 =A0 =A0 =A0 103162 =A02 mptspi,mptscsih
> tg3 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 152032 =A00
>
>
> Regards,
>
> Agya
>
> On Thu, Feb 28, 2013 at 12:29 PM, agya naila <agya.naila@gmail.com> wrote:
>>
>> Hi Andrew and Shiram,
>>
>> I am keep trying this setting using my machine that I mention earl= ier in
>> this email thread.
>> I have using remus with network buffering and no network buffering= .
>>
>> with no network buffering
>> #remus --no-net <vm> <backup target>
>>
>> with network buffering
>> #remus <vm> <backup target>
>>
>> However, when I observed the jitter graph result of my data it see= m there
>> is no buffering impact on my traffic flow, enclosed both the graph= result. I
>> only observed RTP packet and observed the jitter. What I could und= erstand
>> the graph with network protection will doesn't have flow until= x time when
>> the buffer released, in this case default value 100ms. Y axis is t= ime and X
>> axis is jitter.
>>
>> Both of command above running without error except =A0suspend even= t channel
>> issue that we discussed earlier. Please suggest.
>>
>> Regards,
>>
>> Agya
>>
>> On Wed, Feb 20, 2013 at 1:13 PM, agya naila <agya.naila@gmail.com> wrote:
>>>
>>> Aha, sorry to mix it :), its clear now.
>>>
>>> Regards,
>>>
>>> Agya
>>>
>>>
>>> On Wed, Feb 20, 2013 at 1:01 PM, Andrew Eross <eross@locatrix.com> wrote:
>>>>
>>>> Hi Agya,
>>>>
>>>> This patch doesn't fix the 'suspend event channel&= #39; issue, it just fixes
>>>> the crash from the first e-mail in this thread.
>>>>
>>>> Please see this wiki page:
>>>> http://wiki.xen.org/wiki/Remus_PV_domU_requirements=
>>>>
>>>> That discusses the suspend event channel issue.
>>>>
>>>> Cheers,
>>>> Andrew
>>>>
>>>>
>>>> On Wed, Feb 20, 2013 at 8:57 AM, agya naila <agya.naila@gmail.com>
>>>> wrote:
>>>>>
>>>>> Hello All,
>>>>>
>>>>> I am trying this patch on my machine Ubuntu 12.04 AMD6= 4 both for Dom0
>>>>> and DomU with Xen 4.2.2-pre compiling from sources als= o DRBD 8.3.11 but
>>>>> unfortunately it seem didn't work since I still go= t the message WARNING:
>>>>> suspend event channel unavailable, falling back to slo= w xenstore signalling.
>>>>>
>>>>> Regards,
>>>>>
>>>>> Agya
>>>>>
>>>>> On Tue, Feb 19, 2013 at 12:39 PM, Andrew Eross <eross@locatrix.com>
>>>>> wrote:
>>>>>>
>>>>>> Hi all,
>>>>>>
>>>>>> To close off on this, Shriram's patch worked g= reat, thank you.
>>>>>>
>>>>>> So Ubuntu 12.10's standard generic kernel is n= ow working fine as a
>>>>>> dom0 for Remus with Xen 4.1.4 (with the patch from= this thread).
>>>>>>
>>>>>> I wrote up my full install instructions here:
>>>>>>
>>>>>> http://wiki.xen.= org/wiki/Install_Xen_4.1.4_with_Remus_and_DRBD_on_Ubuntu_12.10
>>>>>>
>>>>>> I also took a shot at a number of updates to:
>>>>>> http://wiki.xen.org/wiki/Remus
>>>>>>
>>>>>> And added these pages:
>>>>>> http://wiki.xen.org/wiki/Remus_PV_domU_requ= irements
>>>>>> http://wiki.xen.org/wiki/Remus_dom0_requiremen= ts
>>>>>>
>>>>>> Feedback very welcome, a lot of that information w= as a bit old, so I
>>>>>> did my best.
>>>>>>
>>>>>> Cheers,
>>>>>> Andrew
>>>>>>
>>>>>>
>>>>>> On Mon, Feb 18, 2013 at 8:26 PM, Shriram Rajagopal= an
>>>>>> <rshriram= @cs.ubc.ca> wrote:
>>>>>>>
>>>>>>> ah darn. Yes, the 3.5 kernel has sch_plug in i= t. Unfortunately, the
>>>>>>> technique to initialize the sch_plug module is= bit
>>>>>>> different with the module thats already mainli= ne. You ll have to
>>>>>>> patch
>>>>>>> the qdisc.py python module. I ll submit the >>>>>>> patch to xen devel soon.
>>>>>>> Mean while, can you try the patch below and se= e if it works ?
>>>>>>>
>>>>>>> Secondly, you said you were writing a blog abo= ut how you set it up.
>>>>>>> One of the remus users created a wiki
>>>>>>> remusha.wikidot.com, which has a whole tutorial on how to s= etup remus
>>>>>>> with Debian Squeeze. I have been under fire >>>>>>> lately for a host of remus issues. It would be= great if you could
>>>>>>> post
>>>>>>> your experiences on the wiki too.
>>>>>>> (http://remusha.wikidot.com/system:join)
>>>>>>>
>>>>>>> thanks
>>>>>>> shriram
>>>>>>>
>>>>>>> ---
>>>>>>> diff -r 6435f1edf24e tools/python/xen/remus/qd= isc.py
>>>>>>> --- a/tools/python/xen/remus/qdisc.py =A0 Tue = Jul 17 19:23:30 2012
>>>>>>> -0400
>>>>>>> +++ b/tools/python/xen/remus/qdisc.py =A0 Mon = Feb 18 18:25:22 2013
>>>>>>> -0500
>>>>>>> @@ -1,6 +1,9 @@
>>>>>>> =A0import socket, struct
>>>>>>>
>>>>>>> =A0import netlink
>>>>>>> +import platform
>>>>>>> +
>>>>>>> +kernelversion =3D
>>>>>>> platform.platform(terse=3DTrue).split("-&= quot;)[1].split(".")
>>>>>>>
>>>>>>> =A0qdisc_kinds =3D {}
>>>>>>>
>>>>>>> @@ -150,9 +153,14 @@
>>>>>>> =A0TC_PLUG_RELEASE =3D 1
>>>>>>>
>>>>>>> =A0class PlugQdisc(Qdisc):
>>>>>>> - =A0 =A0fmt =3D 'I'
>>>>>>>
>>>>>>> =A0 =A0 =A0def __init__(self, qdict=3DNone): >>>>>>> + =A0 =A0 =A0 =A0if int(kernelversion[0]) >= =3D 3 and int(kernelversion[1]) >=3D
>>>>>>> 4:
>>>>>>> + =A0 =A0 =A0 =A0 =A0 =A0self.fmt =3D 'iI&= #39;
>>>>>>> + =A0 =A0 =A0 =A0 =A0 =A0self.limit =3D 10000<= br> >>>>>>> + =A0 =A0 =A0 =A0else:
>>>>>>> + =A0 =A0 =A0 =A0 =A0 =A0self.fmt =3D 'I&#= 39;
>>>>>>> +
>>>>>>> =A0 =A0 =A0 =A0 =A0if not qdict:
>>>>>>> =A0 =A0 =A0 =A0 =A0 =A0 =A0qdict =3D {'kin= d': 'plug',
>>>>>>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 &#= 39;handle': TC_H_ROOT}
>>>>>>> @@ -161,7 +169,10 @@
>>>>>>> =A0 =A0 =A0 =A0 =A0self.action =3D 0
>>>>>>>
>>>>>>> =A0 =A0 =A0def pack(self):
>>>>>>> - =A0 =A0 =A0 =A0return struct.pack(self.fmt, = self.action)
>>>>>>> + =A0 =A0 =A0 =A0if int(kernelversion[0]) >= =3D 3 and int(kernelversion[1]) >=3D
>>>>>>> 4:
>>>>>>> + =A0 =A0 =A0 =A0 =A0 =A0return struct.pack(se= lf.fmt, self.action, self.limit)
>>>>>>> + =A0 =A0 =A0 =A0else:
>>>>>>> + =A0 =A0 =A0 =A0 =A0 =A0return struct.pack(se= lf.fmt, self.action)
>>>>>>>
>>>>>>> =A0 =A0 =A0def parse(self, args):
>>>>>>> =A0 =A0 =A0 =A0 =A0if not args:
>>>>>>
>>>>>>
>>>>>>
>>>>>> _______________________________________________ >>>>>> Xen-users mailing list
>>>>>> Xen-use= rs@lists.xen.org
>>>>>> http://lists.xen.org/xen-users
>>>>>
>>>>>
>>>>
>>>
>>
>

--f46d043c7b84f1323704d6cb8dfb-- --===============3993726516882215221== 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 --===============3993726516882215221==-- From xen-users-bounces@lists.xen.org Thu Feb 28 16:42:13 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 28 Feb 2013 16:42: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 1UB6Xl-0006Ay-NS; Thu, 28 Feb 2013 16:41:17 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UB6Xj-0006Aj-Oi for xen-users@lists.xen.org; Thu, 28 Feb 2013 16:41:16 +0000 Received: from [85.158.137.99:64834] by server-2.bemta-3.messagelabs.com id 33/3F-05208-6A88F215; Thu, 28 Feb 2013 16:41:10 +0000 X-Env-Sender: agya.naila@gmail.com X-Msg-Ref: server-12.tower-217.messagelabs.com!1362069655!15201293!1 X-Originating-IP: [74.125.82.42] X-SpamReason: No, hits=1.4 required=7.0 tests=BODY_RANDOM_LONG, HTML_40_50,HTML_MESSAGE,ML_RADAR_SPEW_LINKS_14,ML_RADAR_SPEW_LINKS_8, RCVD_BY_IP,spamassassin: ,async_handler: YXN5bmNfZGVsYXk6IDcwNDY3MzggKHRpbWVvdXQp\n X-StarScan-Received: X-StarScan-Version: 6.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 17706 invoked from network); 28 Feb 2013 16:40:55 -0000 Received: from mail-wg0-f42.google.com (HELO mail-wg0-f42.google.com) (74.125.82.42) by server-12.tower-217.messagelabs.com with RC4-SHA encrypted SMTP; 28 Feb 2013 16:40:55 -0000 Received: by mail-wg0-f42.google.com with SMTP id 12so6471486wgh.1 for ; Thu, 28 Feb 2013 08:40:55 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=493tYLoZROPX6XD34oUp0JV0/26vZQ4siR5fO8O81Lw=; b=OjU+6OUjSURAzrTLP+Iki6aWszv9YPy3fKcQvo8IeGlrAaIg5p7TTkl8w3bOD+vegR ulayJHMBl6yZoZuOw+ATk9yoWfBt8snKNZKSWvAG4Ed0VL+JeMd53u5L7XlszBNYFN4t PcB8QR3JomTADeqNstEfPdGdqcRDKMknA5i2fGvJowkOCuZrt0q9cNIv8AzdTPJHW/CQ OFTLgIgAn5lzvPfrwLmJE8QYHmyX2A8l2kjsK/WrcPsSeq/c/tIs3YI8QMc9VNZrZLCc cX6O4w9jkkhDqmfJxo/BDO3AqDOpLTIK+xsL48W7o3xnoHdHdtceJaR7Rjc9mCmG1jkl qarQ== MIME-Version: 1.0 X-Received: by 10.180.78.35 with SMTP id y3mr11911054wiw.22.1362069654940; Thu, 28 Feb 2013 08:40:54 -0800 (PST) Received: by 10.216.236.13 with HTTP; Thu, 28 Feb 2013 08:40:54 -0800 (PST) In-Reply-To: References: Date: Thu, 28 Feb 2013 17:40:54 +0100 Message-ID: From: agya naila To: rshriram@cs.ubc.ca Cc: "xen-users@lists.xen.org" , Andrew Eross Subject: Re: [Xen-users] Remus dom0 network buffering X-BeenThere: xen-users@lists.xen.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="===============3993726516882215221==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============3993726516882215221== Content-Type: multipart/alternative; boundary=f46d043c7b84f1323704d6cb8dfb --f46d043c7b84f1323704d6cb8dfb Content-Type: text/plain; charset=ISO-8859-1 Hi Shriram, Thank you for reply, I am using Xen version: 4.2.2-pre compiled from sources with kernel 3.2.0-29-generic ~$ dmesg | grep Xen\ version [ 0.000000] Xen version: 4.2.2-pre (preserve-AD) ~$ uname -a Linux comp1 3.2.0-29-generic #46-Ubuntu SMP Fri Jul 27 17:03:23 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux I have try to do simple measurement with ping command but still didn't got satisfying result. Ping domU no migration : C:\Users\rdc>ping 192.168.129.55 -t Pinging 192.168.129.55 with 32 bytes of data: Reply from 192.168.129.55: bytes=32 time=1ms TTL=64 Reply from 192.168.129.55: bytes=32 time<1ms TTL=64 Reply from 192.168.129.55: bytes=32 time<1ms TTL=64 Reply from 192.168.129.55: bytes=32 time<1ms TTL=64 Reply from 192.168.129.55: bytes=32 time=1ms TTL=64 Reply from 192.168.129.55: bytes=32 time=1ms TTL=64 Reply from 192.168.129.55: bytes=32 time<1ms TTL=64 Reply from 192.168.129.55: bytes=32 time<1ms TTL=64 Reply from 192.168.129.55: bytes=32 time<1ms TTL=64 Reply from 192.168.129.55: bytes=32 time<1ms TTL=64 Reply from 192.168.129.55: bytes=32 time=2ms TTL=64 Reply from 192.168.129.55: bytes=32 time=1ms TTL=64 Reply from 192.168.129.55: bytes=32 time=1ms TTL=64 Reply from 192.168.129.55: bytes=32 time=3ms TTL=64 Reply from 192.168.129.55: bytes=32 time<1ms TTL=64 Reply from 192.168.129.55: bytes=32 time<1ms TTL=64 Reply from 192.168.129.55: bytes=32 time<1ms TTL=64 Reply from 192.168.129.55: bytes=32 time<1ms TTL=64 Reply from 192.168.129.55: bytes=32 time<1ms TTL=64 Reply from 192.168.129.55: bytes=32 time<1ms TTL=64 Reply from 192.168.129.55: bytes=32 time=4ms TTL=64 Ping domU with migration but without network bufering : C:\Users\rdc>ping 192.168.129.55 -t Pinging 192.168.129.55 with 32 bytes of data: Reply from 192.168.129.55: bytes=32 time=7ms TTL=64 Reply from 192.168.129.55: bytes=32 time=8ms TTL=64 Reply from 192.168.129.55: bytes=32 time=1ms TTL=64 Reply from 192.168.129.55: bytes=32 time=1ms TTL=64 Reply from 192.168.129.55: bytes=32 time=11ms TTL=64 Reply from 192.168.129.55: bytes=32 time=3ms TTL=64 Reply from 192.168.129.55: bytes=32 time<1ms TTL=64 Reply from 192.168.129.55: bytes=32 time=3ms TTL=64 Reply from 192.168.129.55: bytes=32 time<1ms TTL=64 Reply from 192.168.129.55: bytes=32 time<1ms TTL=64 Reply from 192.168.129.55: bytes=32 time<1ms TTL=64 Reply from 192.168.129.55: bytes=32 time=3ms TTL=64 Reply from 192.168.129.55: bytes=32 time<1ms TTL=64 Reply from 192.168.129.55: bytes=32 time<1ms TTL=64 Reply from 192.168.129.55: bytes=32 time<1ms TTL=64 Reply from 192.168.129.55: bytes=32 time=2ms TTL=64 Reply from 192.168.129.55: bytes=32 time<1ms TTL=64 Reply from 192.168.129.55: bytes=32 time<1ms TTL=64 Reply from 192.168.129.55: bytes=32 time<1ms TTL=64 Reply from 192.168.129.55: bytes=32 time<1ms TTL=64 Reply from 192.168.129.55: bytes=32 time<1ms TTL=64 Reply from 192.168.129.55: bytes=32 time=2ms TTL=64 Reply from 192.168.129.55: bytes=32 time<1ms TTL=64 Reply from 192.168.129.55: bytes=32 time=12ms TTL=64 Ping domU with migration and network bufering : C:\Users\rdc>ping 192.168.129.55 -t Pinging 192.168.129.55 with 32 bytes of data: Reply from 192.168.129.55: bytes=32 time=1ms TTL=64 Reply from 192.168.129.55: bytes=32 time<1ms TTL=64 Reply from 192.168.129.55: bytes=32 time=6ms TTL=64 Reply from 192.168.129.55: bytes=32 time<1ms TTL=64 Reply from 192.168.129.55: bytes=32 time<1ms TTL=64 Reply from 192.168.129.55: bytes=32 time=1ms TTL=64 Reply from 192.168.129.55: bytes=32 time<1ms TTL=64 Reply from 192.168.129.55: bytes=32 time<1ms TTL=64 Reply from 192.168.129.55: bytes=32 time<1ms TTL=64 Reply from 192.168.129.55: bytes=32 time<1ms TTL=64 Reply from 192.168.129.55: bytes=32 time<1ms TTL=64 Reply from 192.168.129.55: bytes=32 time=4ms TTL=64 Reply from 192.168.129.55: bytes=32 time<1ms TTL=64 Reply from 192.168.129.55: bytes=32 time=1ms TTL=64 Reply from 192.168.129.55: bytes=32 time<1ms TTL=64 Reply from 192.168.129.55: bytes=32 time<1ms TTL=64 Reply from 192.168.129.55: bytes=32 time<1ms TTL=64 Reply from 192.168.129.55: bytes=32 time<1ms TTL=64 Reply from 192.168.129.55: bytes=32 time<1ms TTL=64 Reply from 192.168.129.55: bytes=32 time<1ms TTL=64 Reply from 192.168.129.55: bytes=32 time<1ms TTL=64 Here some sampe of remus output (with network buffering) : user1@comp1:~$ sudo remus 1 10.10.10.3 WARNING: suspend event channel unavailable, falling back to slow xenstore signalling PROF: suspending at 1362068953.644729 PROF: resumed at 1362068953.658836 PROF: flushed memory at 1362068953.669453 PROF: suspending at 1362068953.854217 PROF: resumed at 1362068953.868208 PROF: flushed memory at 1362068953.877483 PROF: suspending at 1362068954.063650 PROF: resumed at 1362068954.08 Could you point out something? Regards, Agya On Thu, Feb 28, 2013 at 3:53 PM, Shriram Rajagopalan wrote: > start with a simple test. Ping command. > Remember that suspend/resume also takes some time away from the VM. > If you are using the slow version of suspend/resume, then that alone could > take > 10ms or more (to simply suspend/resume). > > I am not sure if you installed remus from the distribution repo > (ubuntu or whatever) > or if you compiled from source. If you used a repo version, then you > might have to > write a script to parse the remus output (PROF: suspend at ..) to see > how long a VM remains > suspended. > > > On Thu, Feb 28, 2013 at 7:24 AM, agya naila wrote: > > Here my lsmod, > > > > #lsmod > > Module Size Used by > > xt_tcpudp 12603 1 > > xt_physdev 12587 4 > > iptable_filter 12810 1 > > ip_tables 27473 1 iptable_filter > > x_tables 29846 4 > > xt_tcpudp,xt_physdev,iptable_filter,ip_tables > > drbd 303888 4 > > blktap 25553 0 > > xen_pciback 48131 0 > > xen_netback 27854 0 [permanent] > > xen_blkback 23363 0 [permanent] > > xen_gntalloc 13321 0 > > xen_gntdev 17676 1 > > xen_evtchn 13172 2 > > xenfs 18311 1 > > bridge 90989 0 > > stp 12931 1 bridge > > dm_multipath 23230 0 > > radeon 804372 2 > > joydev 17693 0 > > ttm 76949 1 radeon > > drm_kms_helper 46978 1 radeon > > drm 242038 4 radeon,ttm,drm_kms_helper > > i2c_algo_bit 13423 1 radeon > > bnep 18281 2 > > parport_pc 32866 0 > > shpchp 37277 0 > > bluetooth 180104 7 bnep > > ppdev 17113 0 > > mac_hid 13253 0 > > e752x_edac 18564 0 > > edac_core 53746 3 e752x_edac > > ifb 12896 0 > > act_mirred 13038 0 > > cls_u32 17060 0 > > cls_tcindex 13058 0 > > cls_basic 12946 0 > > sch_ingress 12866 0 > > sch_prio 13231 0 > > sch_plug 12654 0 > > lp 17799 0 > > parport 46562 3 parport_pc,ppdev,lp > > dm_snapshot 39031 3 > > usbhid 47199 0 > > hid 99559 1 usbhid > > usb_storage 49198 0 > > mptspi 22921 21 > > mptscsih 44882 1 mptspi > > mptbase 103162 2 mptspi,mptscsih > > tg3 152032 0 > > > > > > Regards, > > > > Agya > > > > On Thu, Feb 28, 2013 at 12:29 PM, agya naila > wrote: > >> > >> Hi Andrew and Shiram, > >> > >> I am keep trying this setting using my machine that I mention earlier in > >> this email thread. > >> I have using remus with network buffering and no network buffering. > >> > >> with no network buffering > >> #remus --no-net > >> > >> with network buffering > >> #remus > >> > >> However, when I observed the jitter graph result of my data it seem > there > >> is no buffering impact on my traffic flow, enclosed both the graph > result. I > >> only observed RTP packet and observed the jitter. What I could > understand > >> the graph with network protection will doesn't have flow until x time > when > >> the buffer released, in this case default value 100ms. Y axis is time > and X > >> axis is jitter. > >> > >> Both of command above running without error except suspend event > channel > >> issue that we discussed earlier. Please suggest. > >> > >> Regards, > >> > >> Agya > >> > >> On Wed, Feb 20, 2013 at 1:13 PM, agya naila > wrote: > >>> > >>> Aha, sorry to mix it :), its clear now. > >>> > >>> Regards, > >>> > >>> Agya > >>> > >>> > >>> On Wed, Feb 20, 2013 at 1:01 PM, Andrew Eross > wrote: > >>>> > >>>> Hi Agya, > >>>> > >>>> This patch doesn't fix the 'suspend event channel' issue, it just > fixes > >>>> the crash from the first e-mail in this thread. > >>>> > >>>> Please see this wiki page: > >>>> http://wiki.xen.org/wiki/Remus_PV_domU_requirements > >>>> > >>>> That discusses the suspend event channel issue. > >>>> > >>>> Cheers, > >>>> Andrew > >>>> > >>>> > >>>> On Wed, Feb 20, 2013 at 8:57 AM, agya naila > >>>> wrote: > >>>>> > >>>>> Hello All, > >>>>> > >>>>> I am trying this patch on my machine Ubuntu 12.04 AMD64 both for Dom0 > >>>>> and DomU with Xen 4.2.2-pre compiling from sources also DRBD 8.3.11 > but > >>>>> unfortunately it seem didn't work since I still got the message > WARNING: > >>>>> suspend event channel unavailable, falling back to slow xenstore > signalling. > >>>>> > >>>>> Regards, > >>>>> > >>>>> Agya > >>>>> > >>>>> On Tue, Feb 19, 2013 at 12:39 PM, Andrew Eross > >>>>> wrote: > >>>>>> > >>>>>> Hi all, > >>>>>> > >>>>>> To close off on this, Shriram's patch worked great, thank you. > >>>>>> > >>>>>> So Ubuntu 12.10's standard generic kernel is now working fine as a > >>>>>> dom0 for Remus with Xen 4.1.4 (with the patch from this thread). > >>>>>> > >>>>>> I wrote up my full install instructions here: > >>>>>> > >>>>>> > http://wiki.xen.org/wiki/Install_Xen_4.1.4_with_Remus_and_DRBD_on_Ubuntu_12.10 > >>>>>> > >>>>>> I also took a shot at a number of updates to: > >>>>>> http://wiki.xen.org/wiki/Remus > >>>>>> > >>>>>> And added these pages: > >>>>>> http://wiki.xen.org/wiki/Remus_PV_domU_requirements > >>>>>> http://wiki.xen.org/wiki/Remus_dom0_requirements > >>>>>> > >>>>>> Feedback very welcome, a lot of that information was a bit old, so I > >>>>>> did my best. > >>>>>> > >>>>>> Cheers, > >>>>>> Andrew > >>>>>> > >>>>>> > >>>>>> On Mon, Feb 18, 2013 at 8:26 PM, Shriram Rajagopalan > >>>>>> wrote: > >>>>>>> > >>>>>>> ah darn. Yes, the 3.5 kernel has sch_plug in it. Unfortunately, the > >>>>>>> technique to initialize the sch_plug module is bit > >>>>>>> different with the module thats already mainline. You ll have to > >>>>>>> patch > >>>>>>> the qdisc.py python module. I ll submit the > >>>>>>> patch to xen devel soon. > >>>>>>> Mean while, can you try the patch below and see if it works ? > >>>>>>> > >>>>>>> Secondly, you said you were writing a blog about how you set it up. > >>>>>>> One of the remus users created a wiki > >>>>>>> remusha.wikidot.com, which has a whole tutorial on how to setup > remus > >>>>>>> with Debian Squeeze. I have been under fire > >>>>>>> lately for a host of remus issues. It would be great if you could > >>>>>>> post > >>>>>>> your experiences on the wiki too. > >>>>>>> (http://remusha.wikidot.com/system:join) > >>>>>>> > >>>>>>> thanks > >>>>>>> shriram > >>>>>>> > >>>>>>> --- > >>>>>>> diff -r 6435f1edf24e tools/python/xen/remus/qdisc.py > >>>>>>> --- a/tools/python/xen/remus/qdisc.py Tue Jul 17 19:23:30 2012 > >>>>>>> -0400 > >>>>>>> +++ b/tools/python/xen/remus/qdisc.py Mon Feb 18 18:25:22 2013 > >>>>>>> -0500 > >>>>>>> @@ -1,6 +1,9 @@ > >>>>>>> import socket, struct > >>>>>>> > >>>>>>> import netlink > >>>>>>> +import platform > >>>>>>> + > >>>>>>> +kernelversion = > >>>>>>> platform.platform(terse=True).split("-")[1].split(".") > >>>>>>> > >>>>>>> qdisc_kinds = {} > >>>>>>> > >>>>>>> @@ -150,9 +153,14 @@ > >>>>>>> TC_PLUG_RELEASE = 1 > >>>>>>> > >>>>>>> class PlugQdisc(Qdisc): > >>>>>>> - fmt = 'I' > >>>>>>> > >>>>>>> def __init__(self, qdict=None): > >>>>>>> + if int(kernelversion[0]) >= 3 and int(kernelversion[1]) >= > >>>>>>> 4: > >>>>>>> + self.fmt = 'iI' > >>>>>>> + self.limit = 10000 > >>>>>>> + else: > >>>>>>> + self.fmt = 'I' > >>>>>>> + > >>>>>>> if not qdict: > >>>>>>> qdict = {'kind': 'plug', > >>>>>>> 'handle': TC_H_ROOT} > >>>>>>> @@ -161,7 +169,10 @@ > >>>>>>> self.action = 0 > >>>>>>> > >>>>>>> def pack(self): > >>>>>>> - return struct.pack(self.fmt, self.action) > >>>>>>> + if int(kernelversion[0]) >= 3 and int(kernelversion[1]) >= > >>>>>>> 4: > >>>>>>> + return struct.pack(self.fmt, self.action, self.limit) > >>>>>>> + else: > >>>>>>> + return struct.pack(self.fmt, self.action) > >>>>>>> > >>>>>>> def parse(self, args): > >>>>>>> if not args: > >>>>>> > >>>>>> > >>>>>> > >>>>>> _______________________________________________ > >>>>>> Xen-users mailing list > >>>>>> Xen-users@lists.xen.org > >>>>>> http://lists.xen.org/xen-users > >>>>> > >>>>> > >>>> > >>> > >> > > > --f46d043c7b84f1323704d6cb8dfb Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Hi Shriram,

Thank you for reply, I am using =A0Xen versi= on: 4.2.2-pre compiled from sources with kernel 3.2.0-29-generic
=
~$ dmesg | grep Xen\ version
[ =A0 =A00.00000= 0] Xen version: 4.2.2-pre (preserve-AD)

~$ uname -a
Linux comp1 3.2.0-29-generic= #46-Ubuntu SMP Fri Jul 27 17:03:23 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux=

I have try to do simple measurement with pi= ng command but still didn't got satisfying result.

Ping domU no migration :
C:\Users\rdc>= ;ping 192.168.129.55 -t

Pinging 192.168.129.55 wit= h 32 bytes of data:
Reply from = 192.168.129.55: bytes=3D32 time=3D1ms TTL=3D64
Reply from 192.168.129.55: bytes= =3D32 time<1ms TTL=3D64
Reply from 192.168.129.55: bytes=3D32 time<1ms TTL=3D64
Reply = from 192.168.129.55: bytes=3D32 time&= lt;1ms TTL=3D64
Reply from 192.168.129.55: bytes= =3D32 time=3D1ms TTL=3D64
Reply from 192.168.129.55: bytes=3D32 time=3D1ms TTL=3D64
Reply fr= om 192.168.129.55: bytes=3D32 time<= ;1ms TTL=3D64
Reply from 192.168.129.55: bytes= =3D32 time<1ms TTL=3D64
Reply from 192.168.129.55: bytes=3D32 time<1ms TTL=3D64
Reply = from 192.168.129.55: bytes=3D32 time&= lt;1ms TTL=3D64
Reply from 192.168.129.55: bytes= =3D32 time=3D2ms TTL=3D64
Reply from 192.168.129.55: bytes=3D32 time=3D1ms TTL=3D64
Reply fr= om 192.168.129.55: bytes=3D32 time=3D= 1ms TTL=3D64
Reply from 192.168.129.55: bytes= =3D32 time=3D3ms TTL=3D64
Reply from 192.168.129.55: bytes=3D32 time<1ms TTL=3D64
Reply f= rom 192.168.129.55: bytes=3D32 time&l= t;1ms TTL=3D64
Reply from 192.168.129.55: bytes= =3D32 time<1ms TTL=3D64
Reply from 192.168.129.55: bytes=3D32 time<1ms TTL=3D64
Reply = from 192.168.129.55: bytes=3D32 time&= lt;1ms TTL=3D64
Reply from 192.168.129.55: bytes= =3D32 time<1ms TTL=3D64
Reply from 192.168.129.55: bytes=3D32 time=3D4ms TTL=3D64
<= br>
Ping domU with migration but without network bufering :
C:\Users\rdc>ping 192.168.129.55 -t

P= inging 192.168.129.55 with 32 bytes of data:
Reply from 192.168.129.55: bytes=3D32 time=3D7ms TTL=3D= 64
Reply from 192.168.129.55: bytes= =3D32 time=3D8ms TTL=3D64
Reply from 192.168.129.55: bytes=3D32 time=3D1ms TTL=3D64
Reply fr= om 192.168.129.55: bytes=3D32 time=3D= 1ms TTL=3D64
Reply from 192.168.129.55: bytes= =3D32 time=3D11ms TTL=3D64
Reply from 192.168.129.55: bytes=3D32 time=3D3ms TTL=3D64
Reply f= rom 192.168.129.55: bytes=3D32 time&l= t;1ms TTL=3D64
Reply from 192.168.129.55: bytes= =3D32 time=3D3ms TTL=3D64
Reply from 192.168.129.55: bytes=3D32 time<1ms TTL=3D64
Reply f= rom 192.168.129.55: bytes=3D32 time&l= t;1ms TTL=3D64
Reply from 192.168.129.55: bytes= =3D32 time<1ms TTL=3D64
Reply from 192.168.129.55: bytes=3D32 time=3D3ms TTL=3D64
Reply f= rom 192.168.129.55: bytes=3D32 time&l= t;1ms TTL=3D64
Reply from 192.168.129.55: bytes= =3D32 time<1ms TTL=3D64
Reply from 192.168.129.55: bytes=3D32 time<1ms TTL=3D64
Reply = from 192.168.129.55: bytes=3D32 time= =3D2ms TTL=3D64
Reply from 192.168.129.55: bytes= =3D32 time<1ms TTL=3D64
Reply from 192.168.129.55: bytes=3D32 time<1ms TTL=3D64
Reply = from 192.168.129.55: bytes=3D32 time&= lt;1ms TTL=3D64
Reply from 192.168.129.55: bytes= =3D32 time<1ms TTL=3D64
Reply from 192.168.129.55: bytes=3D32 time<1ms TTL=3D64
Reply = from 192.168.129.55: bytes=3D32 time= =3D2ms TTL=3D64
Reply from 192.168.129.55: bytes= =3D32 time<1ms TTL=3D64
Reply from 192.168.129.55: bytes=3D32 time=3D12ms TTL=3D64


Ping domU with migration and network bufering :
C= :\Users\rdc>ping 192.168.129.55 -t

P= inging 192.168.129.55 with 32 bytes of data:
Reply from 192.168.129.55: bytes=3D32 time=3D1ms TTL=3D= 64
Reply from 192.168.129.55: bytes= =3D32 time<1ms TTL=3D64
Reply from 192.168.129.55: bytes=3D32 time=3D6ms TTL=3D64
Reply f= rom 192.168.129.55: bytes=3D32 time&l= t;1ms TTL=3D64
Reply from 192.168.129.55: bytes= =3D32 time<1ms TTL=3D64
Reply from 192.168.129.55: bytes=3D32 time=3D1ms TTL=3D64
Reply f= rom 192.168.129.55: bytes=3D32 time&l= t;1ms TTL=3D64
Reply from 192.168.129.55: bytes= =3D32 time<1ms TTL=3D64
Reply from 192.168.129.55: bytes=3D32 time<1ms TTL=3D64
Reply = from 192.168.129.55: bytes=3D32 time&= lt;1ms TTL=3D64
Reply from 192.168.129.55: bytes= =3D32 time<1ms TTL=3D64
Reply from 192.168.129.55: bytes=3D32 time=3D4ms TTL=3D64
Reply f= rom 192.168.129.55: bytes=3D32 time&l= t;1ms TTL=3D64
Reply from 192.168.129.55: bytes= =3D32 time=3D1ms TTL=3D64
Reply from 192.168.129.55: bytes=3D32 time<1ms TTL=3D64
Reply f= rom 192.168.129.55: bytes=3D32 time&l= t;1ms TTL=3D64
Reply from 192.168.129.55: bytes= =3D32 time<1ms TTL=3D64
Reply from 192.168.129.55: bytes=3D32 time<1ms TTL=3D64
Reply = from 192.168.129.55: bytes=3D32 time&= lt;1ms TTL=3D64
Reply from 192.168.129.55: bytes= =3D32 time<1ms TTL=3D64
Reply from 192.168.129.55: bytes=3D32 time<1ms TTL=3D64
=
Here some sampe of remus output (with network buffering) :
<= div>user1@comp1:~$ sudo remus 1 10.10.10.3
WARNING: suspend event= channel unavailable, falling back to slow xenstore signalling
PROF: suspending at 1362068953.644729
PROF: resumed at 1362068953= .658836
PROF: flushed memory at 1362068953.669453
PROF:= suspending at 1362068953.854217
PROF: resumed at 1362068953.8682= 08
PROF: flushed memory at 1362068953.877483
PROF: suspending a= t 1362068954.063650
PROF: resumed at 1362068954.08

Could you point out something?

Regards,

Agya


<= div class=3D"gmail_quote">On Thu, Feb 28, 2013 at 3:53 PM, Shriram Rajagopa= lan <rshriram@cs.ubc.ca> wrote:
start with a simple test. Ping command.
Remember that suspend/resume also takes some time away from the VM.
If you are using the slow version of suspend/resume, then that alone could = take
10ms or more (to simply suspend/resume).

I am not sure if you installed remus from the distribution repo
(ubuntu or whatever)
or if you compiled from source. If you used a repo version, then you
might have to
write a script to parse the remus output (PROF: suspend at ..) to see
how long a VM remains
suspended.


On Thu, Feb 28, 2013 at 7:24 AM, agya naila <agya.naila@gmail.com> wrote:
> Here my lsmod,
>
> =A0#lsmod
> Module =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0Size =A0Used by
> xt_tcpudp =A0 =A0 =A0 =A0 =A0 =A0 =A012603 =A01
> xt_physdev =A0 =A0 =A0 =A0 =A0 =A0 12587 =A04
> iptable_filter =A0 =A0 =A0 =A0 12810 =A01
> ip_tables =A0 =A0 =A0 =A0 =A0 =A0 =A027473 =A01 iptable_filter
> x_tables =A0 =A0 =A0 =A0 =A0 =A0 =A0 29846 =A04
> xt_tcpudp,xt_physdev,iptable_filter,ip_tables
> drbd =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0303888 =A04
> blktap =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 25553 =A00
> xen_pciback =A0 =A0 =A0 =A0 =A0 =A048131 =A00
> xen_netback =A0 =A0 =A0 =A0 =A0 =A027854 =A00 [permanent]
> xen_blkback =A0 =A0 =A0 =A0 =A0 =A023363 =A00 [permanent]
> xen_gntalloc =A0 =A0 =A0 =A0 =A0 13321 =A00
> xen_gntdev =A0 =A0 =A0 =A0 =A0 =A0 17676 =A01
> xen_evtchn =A0 =A0 =A0 =A0 =A0 =A0 13172 =A02
> xenfs =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A018311 =A01
> bridge =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 90989 =A00
> stp =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A012931 =A01 bridge
> dm_multipath =A0 =A0 =A0 =A0 =A0 23230 =A00
> radeon =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0804372 =A02
> joydev =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 17693 =A00
> ttm =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A076949 =A01 radeon
> drm_kms_helper =A0 =A0 =A0 =A0 46978 =A01 radeon
> drm =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 242038 =A04 radeon,ttm,drm_kms= _helper
> i2c_algo_bit =A0 =A0 =A0 =A0 =A0 13423 =A01 radeon
> bnep =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 18281 =A02
> parport_pc =A0 =A0 =A0 =A0 =A0 =A0 32866 =A00
> shpchp =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 37277 =A00
> bluetooth =A0 =A0 =A0 =A0 =A0 =A0 180104 =A07 bnep
> ppdev =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A017113 =A00
> mac_hid =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A013253 =A00
> e752x_edac =A0 =A0 =A0 =A0 =A0 =A0 18564 =A00
> edac_core =A0 =A0 =A0 =A0 =A0 =A0 =A053746 =A03 e752x_edac
> ifb =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A012896 =A00
> act_mirred =A0 =A0 =A0 =A0 =A0 =A0 13038 =A00
> cls_u32 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A017060 =A00
> cls_tcindex =A0 =A0 =A0 =A0 =A0 =A013058 =A00
> cls_basic =A0 =A0 =A0 =A0 =A0 =A0 =A012946 =A00
> sch_ingress =A0 =A0 =A0 =A0 =A0 =A012866 =A00
> sch_prio =A0 =A0 =A0 =A0 =A0 =A0 =A0 13231 =A00
> sch_plug =A0 =A0 =A0 =A0 =A0 =A0 =A0 12654 =A00
> lp =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 17799 =A00
> parport =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A046562 =A03 parport_pc,ppdev,lp<= br> > dm_snapshot =A0 =A0 =A0 =A0 =A0 =A039031 =A03
> usbhid =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 47199 =A00
> hid =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A099559 =A01 usbhid
> usb_storage =A0 =A0 =A0 =A0 =A0 =A049198 =A00
> mptspi =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 22921 =A021
> mptscsih =A0 =A0 =A0 =A0 =A0 =A0 =A0 44882 =A01 mptspi
> mptbase =A0 =A0 =A0 =A0 =A0 =A0 =A0 103162 =A02 mptspi,mptscsih
> tg3 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 152032 =A00
>
>
> Regards,
>
> Agya
>
> On Thu, Feb 28, 2013 at 12:29 PM, agya naila <agya.naila@gmail.com> wrote:
>>
>> Hi Andrew and Shiram,
>>
>> I am keep trying this setting using my machine that I mention earl= ier in
>> this email thread.
>> I have using remus with network buffering and no network buffering= .
>>
>> with no network buffering
>> #remus --no-net <vm> <backup target>
>>
>> with network buffering
>> #remus <vm> <backup target>
>>
>> However, when I observed the jitter graph result of my data it see= m there
>> is no buffering impact on my traffic flow, enclosed both the graph= result. I
>> only observed RTP packet and observed the jitter. What I could und= erstand
>> the graph with network protection will doesn't have flow until= x time when
>> the buffer released, in this case default value 100ms. Y axis is t= ime and X
>> axis is jitter.
>>
>> Both of command above running without error except =A0suspend even= t channel
>> issue that we discussed earlier. Please suggest.
>>
>> Regards,
>>
>> Agya
>>
>> On Wed, Feb 20, 2013 at 1:13 PM, agya naila <agya.naila@gmail.com> wrote:
>>>
>>> Aha, sorry to mix it :), its clear now.
>>>
>>> Regards,
>>>
>>> Agya
>>>
>>>
>>> On Wed, Feb 20, 2013 at 1:01 PM, Andrew Eross <eross@locatrix.com> wrote:
>>>>
>>>> Hi Agya,
>>>>
>>>> This patch doesn't fix the 'suspend event channel&= #39; issue, it just fixes
>>>> the crash from the first e-mail in this thread.
>>>>
>>>> Please see this wiki page:
>>>> http://wiki.xen.org/wiki/Remus_PV_domU_requirements=
>>>>
>>>> That discusses the suspend event channel issue.
>>>>
>>>> Cheers,
>>>> Andrew
>>>>
>>>>
>>>> On Wed, Feb 20, 2013 at 8:57 AM, agya naila <agya.naila@gmail.com>
>>>> wrote:
>>>>>
>>>>> Hello All,
>>>>>
>>>>> I am trying this patch on my machine Ubuntu 12.04 AMD6= 4 both for Dom0
>>>>> and DomU with Xen 4.2.2-pre compiling from sources als= o DRBD 8.3.11 but
>>>>> unfortunately it seem didn't work since I still go= t the message WARNING:
>>>>> suspend event channel unavailable, falling back to slo= w xenstore signalling.
>>>>>
>>>>> Regards,
>>>>>
>>>>> Agya
>>>>>
>>>>> On Tue, Feb 19, 2013 at 12:39 PM, Andrew Eross <eross@locatrix.com>
>>>>> wrote:
>>>>>>
>>>>>> Hi all,
>>>>>>
>>>>>> To close off on this, Shriram's patch worked g= reat, thank you.
>>>>>>
>>>>>> So Ubuntu 12.10's standard generic kernel is n= ow working fine as a
>>>>>> dom0 for Remus with Xen 4.1.4 (with the patch from= this thread).
>>>>>>
>>>>>> I wrote up my full install instructions here:
>>>>>>
>>>>>> http://wiki.xen.= org/wiki/Install_Xen_4.1.4_with_Remus_and_DRBD_on_Ubuntu_12.10
>>>>>>
>>>>>> I also took a shot at a number of updates to:
>>>>>> http://wiki.xen.org/wiki/Remus
>>>>>>
>>>>>> And added these pages:
>>>>>> http://wiki.xen.org/wiki/Remus_PV_domU_requ= irements
>>>>>> http://wiki.xen.org/wiki/Remus_dom0_requiremen= ts
>>>>>>
>>>>>> Feedback very welcome, a lot of that information w= as a bit old, so I
>>>>>> did my best.
>>>>>>
>>>>>> Cheers,
>>>>>> Andrew
>>>>>>
>>>>>>
>>>>>> On Mon, Feb 18, 2013 at 8:26 PM, Shriram Rajagopal= an
>>>>>> <rshriram= @cs.ubc.ca> wrote:
>>>>>>>
>>>>>>> ah darn. Yes, the 3.5 kernel has sch_plug in i= t. Unfortunately, the
>>>>>>> technique to initialize the sch_plug module is= bit
>>>>>>> different with the module thats already mainli= ne. You ll have to
>>>>>>> patch
>>>>>>> the qdisc.py python module. I ll submit the >>>>>>> patch to xen devel soon.
>>>>>>> Mean while, can you try the patch below and se= e if it works ?
>>>>>>>
>>>>>>> Secondly, you said you were writing a blog abo= ut how you set it up.
>>>>>>> One of the remus users created a wiki
>>>>>>> remusha.wikidot.com, which has a whole tutorial on how to s= etup remus
>>>>>>> with Debian Squeeze. I have been under fire >>>>>>> lately for a host of remus issues. It would be= great if you could
>>>>>>> post
>>>>>>> your experiences on the wiki too.
>>>>>>> (http://remusha.wikidot.com/system:join)
>>>>>>>
>>>>>>> thanks
>>>>>>> shriram
>>>>>>>
>>>>>>> ---
>>>>>>> diff -r 6435f1edf24e tools/python/xen/remus/qd= isc.py
>>>>>>> --- a/tools/python/xen/remus/qdisc.py =A0 Tue = Jul 17 19:23:30 2012
>>>>>>> -0400
>>>>>>> +++ b/tools/python/xen/remus/qdisc.py =A0 Mon = Feb 18 18:25:22 2013
>>>>>>> -0500
>>>>>>> @@ -1,6 +1,9 @@
>>>>>>> =A0import socket, struct
>>>>>>>
>>>>>>> =A0import netlink
>>>>>>> +import platform
>>>>>>> +
>>>>>>> +kernelversion =3D
>>>>>>> platform.platform(terse=3DTrue).split("-&= quot;)[1].split(".")
>>>>>>>
>>>>>>> =A0qdisc_kinds =3D {}
>>>>>>>
>>>>>>> @@ -150,9 +153,14 @@
>>>>>>> =A0TC_PLUG_RELEASE =3D 1
>>>>>>>
>>>>>>> =A0class PlugQdisc(Qdisc):
>>>>>>> - =A0 =A0fmt =3D 'I'
>>>>>>>
>>>>>>> =A0 =A0 =A0def __init__(self, qdict=3DNone): >>>>>>> + =A0 =A0 =A0 =A0if int(kernelversion[0]) >= =3D 3 and int(kernelversion[1]) >=3D
>>>>>>> 4:
>>>>>>> + =A0 =A0 =A0 =A0 =A0 =A0self.fmt =3D 'iI&= #39;
>>>>>>> + =A0 =A0 =A0 =A0 =A0 =A0self.limit =3D 10000<= br> >>>>>>> + =A0 =A0 =A0 =A0else:
>>>>>>> + =A0 =A0 =A0 =A0 =A0 =A0self.fmt =3D 'I&#= 39;
>>>>>>> +
>>>>>>> =A0 =A0 =A0 =A0 =A0if not qdict:
>>>>>>> =A0 =A0 =A0 =A0 =A0 =A0 =A0qdict =3D {'kin= d': 'plug',
>>>>>>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 &#= 39;handle': TC_H_ROOT}
>>>>>>> @@ -161,7 +169,10 @@
>>>>>>> =A0 =A0 =A0 =A0 =A0self.action =3D 0
>>>>>>>
>>>>>>> =A0 =A0 =A0def pack(self):
>>>>>>> - =A0 =A0 =A0 =A0return struct.pack(self.fmt, = self.action)
>>>>>>> + =A0 =A0 =A0 =A0if int(kernelversion[0]) >= =3D 3 and int(kernelversion[1]) >=3D
>>>>>>> 4:
>>>>>>> + =A0 =A0 =A0 =A0 =A0 =A0return struct.pack(se= lf.fmt, self.action, self.limit)
>>>>>>> + =A0 =A0 =A0 =A0else:
>>>>>>> + =A0 =A0 =A0 =A0 =A0 =A0return struct.pack(se= lf.fmt, self.action)
>>>>>>>
>>>>>>> =A0 =A0 =A0def parse(self, args):
>>>>>>> =A0 =A0 =A0 =A0 =A0if not args:
>>>>>>
>>>>>>
>>>>>>
>>>>>> _______________________________________________ >>>>>> Xen-users mailing list
>>>>>> Xen-use= rs@lists.xen.org
>>>>>> http://lists.xen.org/xen-users
>>>>>
>>>>>
>>>>
>>>
>>
>

--f46d043c7b84f1323704d6cb8dfb-- --===============3993726516882215221== 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 --===============3993726516882215221==-- From xen-users-bounces@lists.xen.org Thu Feb 28 19:16:25 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 28 Feb 2013 19:16: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 1UB8wd-0001TE-VG; Thu, 28 Feb 2013 19:15:07 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UB5LD-0000xH-66 for xen-users@lists.xen.org; Thu, 28 Feb 2013 15:24:15 +0000 Received: from [85.158.138.51:20208] by server-2.bemta-3.messagelabs.com id D5/F0-05208-E967F215; Thu, 28 Feb 2013 15:24:14 +0000 X-Env-Sender: syllopsium@syllopsium.co.uk X-Msg-Ref: server-15.tower-174.messagelabs.com!1362065053!27942317!1 X-Originating-IP: [74.125.82.182] X-SpamReason: No, hits=3.4 required=7.0 tests=HTML_00_10,HTML_MESSAGE, HTML_TAG_BALANCE_HEAD X-StarScan-Received: X-StarScan-Version: 6.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 7600 invoked from network); 28 Feb 2013 15:24:13 -0000 Received: from mail-we0-f182.google.com (HELO mail-we0-f182.google.com) (74.125.82.182) by server-15.tower-174.messagelabs.com with RC4-SHA encrypted SMTP; 28 Feb 2013 15:24:13 -0000 Received: by mail-we0-f182.google.com with SMTP id t57so1607033wey.41 for ; Thu, 28 Feb 2013 07:24:13 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=x-received:user-agent:mime-version:content-type:subject:from:date :to:message-id:x-gm-message-state; bh=9/uXW4tj4GkOZ5XBRhp9Xf4zpzVzm/Rs1nGQhGT09zo=; b=X2DHlF8lnLUZgwZrpBII6NVkND57Gsnogx5lj0hNQ4VTHGq4cQqzTn6Lplj8XVQk/D HCOkvbyC6VxQ4nI7JNQ0ZgSN+lCoFANVqqwDj2c0ZUgHTZShzEGoFtdoD7MKqa5dfyAT atVJveKsvPBuKkbbHRTcXlwPmqs+c56yz0BmmUAATAHjAltSM2pODiQy7+RMV/HpJAWz aQruiWYbZBXpNlyxdt35svGu3VrY2R5n8BwTA9rcqIAImDESUmhr1X8DjlwHkVaJFYD9 MM0bwTYUaJzg6ES+CPcbgikhASfvQURFc9Z1EyI6caQKmnSdYzhEZEWQZLe23Z1L8jK0 9Wrw== X-Received: by 10.180.74.131 with SMTP id t3mr33735462wiv.23.1362065052774; Thu, 28 Feb 2013 07:24:12 -0800 (PST) Received: from [10.138.73.192] (dab-bhx2-h-19-3.dab.02.net. [82.132.233.73]) by mx.google.com with ESMTPS id n2sm34010587wiy.6.2013.02.28.07.24.10 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 28 Feb 2013 07:24:11 -0800 (PST) User-Agent: K-9 Mail for Android MIME-Version: 1.0 From: Peter Kay Date: Thu, 28 Feb 2013 15:24:03 +0000 To: xen-users@lists.xen.org Message-ID: <77429df2-90f1-4485-85ac-b06e4b5f1904@email.android.com> X-Gm-Message-State: ALoCoQmJUcimtIw8FUYo57joHjyWAyGNbdRKg8ZF+/RB7ttTq0ST/epEj+nl49CIB4pBu4idl69Y X-Mailman-Approved-At: Thu, 28 Feb 2013 19:15:07 +0000 Subject: [Xen-users] Passthrough on SH3210/1:1 mapping X-BeenThere: xen-users@lists.xen.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="===============3682859403059585449==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============3682859403059585449== Content-Type: multipart/alternative; boundary="----SWZJGBMK00EDW35E8DJUKHK2L1QE3B" ------SWZJGBMK00EDW35E8DJUKHK2L1QE3B Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Does anyone have experience of passthrough on the SH3210/SH3200 (specifically the 3210SHLC). I know it does work as Esx5.1 can pass through the embedded G200e display adapter. I've set the passthrough option on pciback but the devices always have different PCI numbers in the VM. Does it make any difference that pciback is a module! (running Debian Wheezy x64, makes no difference whether I use 4.2 or 4.3 unstable. I'm trying to pass through a Radeon 6950 although given the absence of SLAT this might not be a great idea.. Any advice is welcome, particularly diagnosing why the pciback passthrough option seems not to be working. The dmesg seems to indicate it's ok ------SWZJGBMK00EDW35E8DJUKHK2L1QE3B Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: 8bit Does anyone have experience of passthrough on the SH3210/SH3200 (specifically the 3210SHLC). I know it does work as Esx5.1 can pass through the embedded G200e display adapter.

I've set the passthrough option on pciback but the devices always have different PCI numbers in the VM. Does it make any difference that pciback is a module! (running Debian Wheezy x64, makes no difference whether I use 4.2 or 4.3 unstable.

I'm trying to pass through a Radeon 6950 although given the absence of SLAT this might not be a great idea..

Any advice is welcome, particularly diagnosing why the pciback passthrough option seems not to be working. The dmesg seems to indicate it's ok ------SWZJGBMK00EDW35E8DJUKHK2L1QE3B-- --===============3682859403059585449== 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 --===============3682859403059585449==-- From xen-users-bounces@lists.xen.org Thu Feb 28 19:16:25 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 28 Feb 2013 19:16: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 1UB8wd-0001TE-VG; Thu, 28 Feb 2013 19:15:07 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UB5LD-0000xH-66 for xen-users@lists.xen.org; Thu, 28 Feb 2013 15:24:15 +0000 Received: from [85.158.138.51:20208] by server-2.bemta-3.messagelabs.com id D5/F0-05208-E967F215; Thu, 28 Feb 2013 15:24:14 +0000 X-Env-Sender: syllopsium@syllopsium.co.uk X-Msg-Ref: server-15.tower-174.messagelabs.com!1362065053!27942317!1 X-Originating-IP: [74.125.82.182] X-SpamReason: No, hits=3.4 required=7.0 tests=HTML_00_10,HTML_MESSAGE, HTML_TAG_BALANCE_HEAD X-StarScan-Received: X-StarScan-Version: 6.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 7600 invoked from network); 28 Feb 2013 15:24:13 -0000 Received: from mail-we0-f182.google.com (HELO mail-we0-f182.google.com) (74.125.82.182) by server-15.tower-174.messagelabs.com with RC4-SHA encrypted SMTP; 28 Feb 2013 15:24:13 -0000 Received: by mail-we0-f182.google.com with SMTP id t57so1607033wey.41 for ; Thu, 28 Feb 2013 07:24:13 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=x-received:user-agent:mime-version:content-type:subject:from:date :to:message-id:x-gm-message-state; bh=9/uXW4tj4GkOZ5XBRhp9Xf4zpzVzm/Rs1nGQhGT09zo=; b=X2DHlF8lnLUZgwZrpBII6NVkND57Gsnogx5lj0hNQ4VTHGq4cQqzTn6Lplj8XVQk/D HCOkvbyC6VxQ4nI7JNQ0ZgSN+lCoFANVqqwDj2c0ZUgHTZShzEGoFtdoD7MKqa5dfyAT atVJveKsvPBuKkbbHRTcXlwPmqs+c56yz0BmmUAATAHjAltSM2pODiQy7+RMV/HpJAWz aQruiWYbZBXpNlyxdt35svGu3VrY2R5n8BwTA9rcqIAImDESUmhr1X8DjlwHkVaJFYD9 MM0bwTYUaJzg6ES+CPcbgikhASfvQURFc9Z1EyI6caQKmnSdYzhEZEWQZLe23Z1L8jK0 9Wrw== X-Received: by 10.180.74.131 with SMTP id t3mr33735462wiv.23.1362065052774; Thu, 28 Feb 2013 07:24:12 -0800 (PST) Received: from [10.138.73.192] (dab-bhx2-h-19-3.dab.02.net. [82.132.233.73]) by mx.google.com with ESMTPS id n2sm34010587wiy.6.2013.02.28.07.24.10 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 28 Feb 2013 07:24:11 -0800 (PST) User-Agent: K-9 Mail for Android MIME-Version: 1.0 From: Peter Kay Date: Thu, 28 Feb 2013 15:24:03 +0000 To: xen-users@lists.xen.org Message-ID: <77429df2-90f1-4485-85ac-b06e4b5f1904@email.android.com> X-Gm-Message-State: ALoCoQmJUcimtIw8FUYo57joHjyWAyGNbdRKg8ZF+/RB7ttTq0ST/epEj+nl49CIB4pBu4idl69Y X-Mailman-Approved-At: Thu, 28 Feb 2013 19:15:07 +0000 Subject: [Xen-users] Passthrough on SH3210/1:1 mapping X-BeenThere: xen-users@lists.xen.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="===============3682859403059585449==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============3682859403059585449== Content-Type: multipart/alternative; boundary="----SWZJGBMK00EDW35E8DJUKHK2L1QE3B" ------SWZJGBMK00EDW35E8DJUKHK2L1QE3B Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Does anyone have experience of passthrough on the SH3210/SH3200 (specifically the 3210SHLC). I know it does work as Esx5.1 can pass through the embedded G200e display adapter. I've set the passthrough option on pciback but the devices always have different PCI numbers in the VM. Does it make any difference that pciback is a module! (running Debian Wheezy x64, makes no difference whether I use 4.2 or 4.3 unstable. I'm trying to pass through a Radeon 6950 although given the absence of SLAT this might not be a great idea.. Any advice is welcome, particularly diagnosing why the pciback passthrough option seems not to be working. The dmesg seems to indicate it's ok ------SWZJGBMK00EDW35E8DJUKHK2L1QE3B Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: 8bit Does anyone have experience of passthrough on the SH3210/SH3200 (specifically the 3210SHLC). I know it does work as Esx5.1 can pass through the embedded G200e display adapter.

I've set the passthrough option on pciback but the devices always have different PCI numbers in the VM. Does it make any difference that pciback is a module! (running Debian Wheezy x64, makes no difference whether I use 4.2 or 4.3 unstable.

I'm trying to pass through a Radeon 6950 although given the absence of SLAT this might not be a great idea..

Any advice is welcome, particularly diagnosing why the pciback passthrough option seems not to be working. The dmesg seems to indicate it's ok ------SWZJGBMK00EDW35E8DJUKHK2L1QE3B-- --===============3682859403059585449== 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 --===============3682859403059585449==-- From xen-users-bounces@lists.xen.org Thu Feb 28 20:07:29 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 28 Feb 2013 20:07: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 1UB9kF-0002hf-Ul; Thu, 28 Feb 2013 20:06:23 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UB9kD-0002ha-M5 for xen-users@lists.xen.org; Thu, 28 Feb 2013 20:06:21 +0000 Received: from [85.158.137.99:26877] by server-11.bemta-3.messagelabs.com id 15/12-01263-CB8BF215; Thu, 28 Feb 2013 20:06:20 +0000 X-Env-Sender: zootboysean@gmail.com X-Msg-Ref: server-13.tower-217.messagelabs.com!1362081980!605279!1 X-Originating-IP: [74.125.82.42] 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.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 6266 invoked from network); 28 Feb 2013 20:06:20 -0000 Received: from mail-wg0-f42.google.com (HELO mail-wg0-f42.google.com) (74.125.82.42) by server-13.tower-217.messagelabs.com with RC4-SHA encrypted SMTP; 28 Feb 2013 20:06:20 -0000 Received: by mail-wg0-f42.google.com with SMTP id 12so6646857wgh.5 for ; Thu, 28 Feb 2013 12:06:20 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=pVg0F508SYTSqw/ed7xQxRWJTZqfw1t13vCBBXMyU7c=; b=OmJ2QuiZUnpRVnsZu8vNCh3inZBwdvvKWQgcBuvbKu2BhCv2df93ItrVF3T2+qS/DF bCizAYDKOJ4KtZ4hUdlbSbsg5UZIhBP8whHml2CoDNDTZonnznOTu8X8nuwUNjDfN0J0 /V2VmfXkfT7N1cYrdR4iz7GWLowbrpv29tb0u9yy8/qor0ScDszGBkGghcCRjN0mActw HxXNtAoJTwjT0TWgKTd36TPSs6byeRfMK4qkwSH4sysT81TYsAOV0ceY2wr+t5nitzO4 8TTxb1GKnBQApVGwracLgmFR2J7ESPZ8X37ncqsQ61c4tB1OzTFZ2a3oXEWkdA42Jji4 Qy5g== MIME-Version: 1.0 X-Received: by 10.180.97.233 with SMTP id ed9mr35076311wib.32.1362081979982; Thu, 28 Feb 2013 12:06:19 -0800 (PST) Received: by 10.216.120.193 with HTTP; Thu, 28 Feb 2013 12:06:19 -0800 (PST) Received: by 10.216.120.193 with HTTP; Thu, 28 Feb 2013 12:06:19 -0800 (PST) In-Reply-To: References: Date: Thu, 28 Feb 2013 15:06:19 -0500 Message-ID: From: Sean Greenslade To: jacek burghardt Cc: xen-users Subject: Re: [Xen-users] xen 4.3 unstable and spice protocol X-BeenThere: xen-users@lists.xen.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="===============4296480975954441808==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============4296480975954441808== Content-Type: multipart/alternative; boundary=f46d044306aa92785804d6ce6ccf --f46d044306aa92785804d6ce6ccf Content-Type: text/plain; charset=UTF-8 On Feb 28, 2013 10:56 AM, "jacek burghardt" wrote: > > I wonder if there is package for any of Linux distribution that is compiled on xen-4.3 unstable with spice protocol? > I would suspect most distros wouldn't package the unstable branch as it updates so frequently. Archlinux has an AUR package that builds the latest unstable from source automatically, so you could modify the build script to include spice (if it doesn't already, I don't know as I don't use spice). --f46d044306aa92785804d6ce6ccf Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable


On Feb 28, 2013 10:56 AM, "jacek burghardt" <jaceksburghardt@gmail.com> wrote:
>
> I wonder if there is package for any of=C2=A0Linux=C2=A0distribution t= hat is compiled on xen-4.3 unstable with spice protocol?=C2=A0
>

I would suspect most distros wouldn't package the unstable branch as= it updates so frequently. Archlinux has an AUR package that builds the lat= est unstable from source automatically, so you could modify the build scrip= t to include spice (if it doesn't already, I don't know as I don= 9;t use spice).

--f46d044306aa92785804d6ce6ccf-- --===============4296480975954441808== 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 --===============4296480975954441808==-- From xen-users-bounces@lists.xen.org Thu Feb 28 20:07:29 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 28 Feb 2013 20:07: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 1UB9kF-0002hf-Ul; Thu, 28 Feb 2013 20:06:23 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UB9kD-0002ha-M5 for xen-users@lists.xen.org; Thu, 28 Feb 2013 20:06:21 +0000 Received: from [85.158.137.99:26877] by server-11.bemta-3.messagelabs.com id 15/12-01263-CB8BF215; Thu, 28 Feb 2013 20:06:20 +0000 X-Env-Sender: zootboysean@gmail.com X-Msg-Ref: server-13.tower-217.messagelabs.com!1362081980!605279!1 X-Originating-IP: [74.125.82.42] 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.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 6266 invoked from network); 28 Feb 2013 20:06:20 -0000 Received: from mail-wg0-f42.google.com (HELO mail-wg0-f42.google.com) (74.125.82.42) by server-13.tower-217.messagelabs.com with RC4-SHA encrypted SMTP; 28 Feb 2013 20:06:20 -0000 Received: by mail-wg0-f42.google.com with SMTP id 12so6646857wgh.5 for ; Thu, 28 Feb 2013 12:06:20 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=pVg0F508SYTSqw/ed7xQxRWJTZqfw1t13vCBBXMyU7c=; b=OmJ2QuiZUnpRVnsZu8vNCh3inZBwdvvKWQgcBuvbKu2BhCv2df93ItrVF3T2+qS/DF bCizAYDKOJ4KtZ4hUdlbSbsg5UZIhBP8whHml2CoDNDTZonnznOTu8X8nuwUNjDfN0J0 /V2VmfXkfT7N1cYrdR4iz7GWLowbrpv29tb0u9yy8/qor0ScDszGBkGghcCRjN0mActw HxXNtAoJTwjT0TWgKTd36TPSs6byeRfMK4qkwSH4sysT81TYsAOV0ceY2wr+t5nitzO4 8TTxb1GKnBQApVGwracLgmFR2J7ESPZ8X37ncqsQ61c4tB1OzTFZ2a3oXEWkdA42Jji4 Qy5g== MIME-Version: 1.0 X-Received: by 10.180.97.233 with SMTP id ed9mr35076311wib.32.1362081979982; Thu, 28 Feb 2013 12:06:19 -0800 (PST) Received: by 10.216.120.193 with HTTP; Thu, 28 Feb 2013 12:06:19 -0800 (PST) Received: by 10.216.120.193 with HTTP; Thu, 28 Feb 2013 12:06:19 -0800 (PST) In-Reply-To: References: Date: Thu, 28 Feb 2013 15:06:19 -0500 Message-ID: From: Sean Greenslade To: jacek burghardt Cc: xen-users Subject: Re: [Xen-users] xen 4.3 unstable and spice protocol X-BeenThere: xen-users@lists.xen.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="===============4296480975954441808==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============4296480975954441808== Content-Type: multipart/alternative; boundary=f46d044306aa92785804d6ce6ccf --f46d044306aa92785804d6ce6ccf Content-Type: text/plain; charset=UTF-8 On Feb 28, 2013 10:56 AM, "jacek burghardt" wrote: > > I wonder if there is package for any of Linux distribution that is compiled on xen-4.3 unstable with spice protocol? > I would suspect most distros wouldn't package the unstable branch as it updates so frequently. Archlinux has an AUR package that builds the latest unstable from source automatically, so you could modify the build script to include spice (if it doesn't already, I don't know as I don't use spice). --f46d044306aa92785804d6ce6ccf Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable


On Feb 28, 2013 10:56 AM, "jacek burghardt" <jaceksburghardt@gmail.com> wrote:
>
> I wonder if there is package for any of=C2=A0Linux=C2=A0distribution t= hat is compiled on xen-4.3 unstable with spice protocol?=C2=A0
>

I would suspect most distros wouldn't package the unstable branch as= it updates so frequently. Archlinux has an AUR package that builds the lat= est unstable from source automatically, so you could modify the build scrip= t to include spice (if it doesn't already, I don't know as I don= 9;t use spice).

--f46d044306aa92785804d6ce6ccf-- --===============4296480975954441808== 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 --===============4296480975954441808==-- From xen-users-bounces@lists.xen.org Thu Feb 28 20:43:39 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 28 Feb 2013 20:43: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 1UBAJB-0003hL-Qs; Thu, 28 Feb 2013 20:42:29 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UBAJA-0003hF-Ce for xen-users@lists.xen.org; Thu, 28 Feb 2013 20:42:28 +0000 Received: from [85.158.137.99:14903] by server-10.bemta-3.messagelabs.com id 13/BE-19664-331CF215; Thu, 28 Feb 2013 20:42:27 +0000 X-Env-Sender: epretorious@yahoo.com X-Msg-Ref: server-15.tower-217.messagelabs.com!1362084145!16295491!1 X-Originating-IP: [98.138.91.142] X-SpamReason: No, hits=0.9 required=7.0 tests=HTML_40_50,HTML_MESSAGE, MAILTO_TO_SPAM_ADDR,ML_RADAR_SPEW_LINKS_12,ML_RADAR_SPEW_LINKS_14, ML_RADAR_SPEW_LINKS_6,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 17453 invoked from network); 28 Feb 2013 20:42:26 -0000 Received: from nm12-vm3.bullet.mail.ne1.yahoo.com (HELO nm12-vm3.bullet.mail.ne1.yahoo.com) (98.138.91.142) by server-15.tower-217.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 28 Feb 2013 20:42:26 -0000 Received: from [98.138.90.52] by nm12.bullet.mail.ne1.yahoo.com with NNFMP; 28 Feb 2013 20:42:24 -0000 Received: from [98.138.226.169] by tm5.bullet.mail.ne1.yahoo.com with NNFMP; 28 Feb 2013 20:42:24 -0000 Received: from [127.0.0.1] by omp1070.mail.ne1.yahoo.com with NNFMP; 28 Feb 2013 20:42:24 -0000 X-Yahoo-Newman-Property: ymail-3 X-Yahoo-Newman-Id: 772454.85059.bm@omp1070.mail.ne1.yahoo.com Received: (qmail 56897 invoked by uid 60001); 28 Feb 2013 20:42:24 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1362084144; bh=A69qbJ7BcGEklj9tZJVc/+nR8m0V8BHAMXsUV+Qa9Ls=; h=X-YMail-OSG:Received:X-Rocket-MIMEInfo:X-Mailer:References:Message-ID:Date:From:Reply-To:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type; b=TuzIf703cYma92s2vgo6YGi16N4axyCeGaRX3BmIwK22+y4bxPlRPQCJqspRnaUWpJBUVMgi2kUxfoYxXAhmIXszG7UwgVMjTUF4jkUn0Yv0ogWnB1fVU4gu8Dabj1rzfujmIsnOdjgavNEdk1GtvNG+15UmheYqHyJcHkcZeGg= DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=X-YMail-OSG:Received:X-Rocket-MIMEInfo:X-Mailer:References:Message-ID:Date:From:Reply-To:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type; b=wcnBLAr7Muj0v2WkylIzHa7SAo4aUBmtABVigcFoTKg4oXo8qW2zFR/A6l8c4gB06EKBv1feeaA8Cu4pbLQDUlarvRS+Um5IGhgNtvflsKr+5yNkX5E77hngmO+EyQwK/E5C0ODlFLj0fnrPKL3m1efoxl2DD+Ud5tGj7PfnA0o=; X-YMail-OSG: ft1E12wVM1nKMG4Dc59It6zOLJ5CKFrrtrOhP9QYT4z.5e6 q3.E.fN_y6XWhdBtdx4vIEZ1Mrl2gg.5F0Y_3U4Vgxa.2xRp7BeIwctt6dMJ mUIsbsLUMYStMQfZeZxt7f53rcLWpW095R3h57jSaKPXRhomEc2bMdDq0md3 D17fTFFl0pygazLYt7yuQ8eAEnRMP8YHLA0u.zBNk4aKGDVaOvqnMB47kZ6c F8Z2nb0DVVYdTXyBGRjyl7cvC1XF6S_6HkEOzLWiy_GI49TY1Dk9M8ZQUDyH bn2VtEsQutfdXHveFV8jQl9OEKdwUXpHFeBScC0c_XaAJHs4Z1ny0prtR2cV V73k2JNWDxaED.ckR3qwD1Wf1CFYnN9HdbkSxKnTpiNYgYH6mgQnc0qW1wIl Jh1oEtYEqKglqGJCqXfKm.INZcFrBOnGPu2jQY.KW8onQsq1j.UHJAp1NTPJ Kn7z4igNNVb4SzS30XnySivDkn7ZsriSm07ZfY4Jpa.WnBBo8U9M51X6ggNm J8dkllwcw855naXmZVSpjJcGjw5w- Received: from [74.197.253.230] by web126001.mail.ne1.yahoo.com via HTTP; Thu, 28 Feb 2013 12:42:23 PST X-Rocket-MIMEInfo: 001.001, TG9rZXNoOgoKVGhlIGZpcnN0IG9yZGVyIG9mIGJ1c2luZXNzIGlzIHRvIGRldGVybWluZSB3aHkgdGhlIG1pZ3JhdGlvbiBmYWlsZWQuCgpDaGVjayB0aGUgZmlsZXMgeGVuZC5sb2cgJiB4ZW5kLWRlYnVnLmxvZyAobG9jYXRlZCBpbiAvdmFyL2xvZy94ZW4vKSB0byBzZWUgd2h5IHRoZSBtaWdyYXRpb24gZmFpbGVkIHRvIGNvbXBsZXRlIHN1Y2Nlc3NmdWxseS4gKEhpbnQ6IEkgc29tZXRpbWVzIHdhdGNoIHRoZXNlIGZpbGVzIFtvbiB0aGUgZGVzdGluYXRpb25dIHVzaW5nICAvdXNyL2Jpbi90YWlsIHdpdGgBMAEBAQE- X-Mailer: YahooMailWebService/0.8.135.514 References: Message-ID: <1362084143.47326.YahooMailNeo@web126001.mail.ne1.yahoo.com> Date: Thu, 28 Feb 2013 12:42:23 -0800 (PST) From: Eric To: "xen-users@lists.xen.org" In-Reply-To: MIME-Version: 1.0 Cc: Lokesh Walase Subject: Re: [Xen-users] After VM migration , shows entry at both destination & host X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: Eric List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============6437979433882301732==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============6437979433882301732== Content-Type: multipart/alternative; boundary="28998604-649596623-1362084143=:47326" --28998604-649596623-1362084143=:47326 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Lokesh:=0A=0AThe first order of business is to determine why the migration = failed.=0A=0ACheck the files xend.log & xend-debug.log (located in /var/log= /xen/) to see why the migration failed to complete successfully. (Hint: I s= ometimes watch these files [on the destination] using /usr/bin/tail with t= he --follow flag to see the entries as they're added in real-time.)=0A=0AHT= H,=0AEric Pretorious=0ATruckee, CA=0A=0A=0A=0A=0A=0A>______________________= __________=0A> From: Lokesh Walase =0A>To: xen-users@= lists.xen.org =0A>Sent: Wednesday, February 27, 2013 11:26 PM=0A>Subject: [= Xen-users] After VM migration , shows entry at both destination & host=0A> = =0A>=0A>Hello,=0A>=A0=A0=A0=A0=A0=A0 I have installed =0Axen-hypervisor-4.1= -amd64 successfully on 4 hosts (with Ubuntu-12.04 as =0Adom0). =0A>=A0=A0= =A0=A0=A0=A0 I tried live migration of a virtual machine from one host to = =0Aanother via command line : xm migrate -l = =0A>=A0=A0=A0=A0=A0=A0 ( host_ip_adrress is static-ip )=0A>=0A>The problems= are : =0A>=0A>=A0 =A0 =A0=A0 1. During migration, I can see the entry of t= he VM appearing in the Virtual Machine Manager (VMM) of destination host.= =0A>=A0 =A0 =A0=A0 2. After migration is complete, both the source as well = as the =0Adestination host show the entry for corresponding VM in VMM.=0A>= =A0=A0=A0=A0=A0=A0 3. After reboot, the destination host does not show=A0 m= igrated VM, but the entry on the source host stays as it =0Awas previously.= =0A>=A0=A0=A0=A0=A0=A0=A0 So basically after reboot, the migrated VM stays= on host only.=0A>=0A>_______________________________________________=0A>Xe= n-users mailing list=0A>Xen-users@lists.xen.org=0A>http://lists.xen.org/xen= -users=0A>=0A> --28998604-649596623-1362084143=:47326 Content-Type: text/html; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable
Lokesh:
The first order of business is to determine why the migration failed.=

Check the files xend.log & xend-debug.log (located in /var/log/= xen/) to see why the migration failed to complete successfully. (Hint: I so= metimes watch these files [on the destination] using /usr/bin/tail with th= e --follow flag to see the entries as they're added in real-time.)

H= TH,
Eric Pretorious
Truckee, CA

<= br>
= From: Lokesh Walase <flokeshw24@= gmail.com>
To: xen-= users@lists.xen.org
Sent:= Wednesday, February 27, 2013 11:26 PM
Subject: [Xen-users] After VM migration , shows entry = at both destination & host

=0A
Hello,
     &= nbsp; I have installed =0Axen-hypervisor-4.1-amd64 successfully on 4 hosts = (with Ubuntu-12.04 as =0Adom0).
       I = tried live migration of a virtual machine from one host to =0Aanother via c= ommand line : xm migrate -l <domain_id> <host_ip_address>
&n= bsp;      ( host_ip_adrress is static-ip )

= The problems are :

=0A=0A
       1. During= migration, I can see the entry of the VM appearing in the Virtual Machine = Manager (VMM) of destination host.
 =0A      2= . After migration is complete, both the source as well as the =0Adestinatio= n host show the entry for corresponding VM in VMM.
=0A=0A
 &nb= sp;     3. After reboot, the destination host does not = show  migrated VM, but the entry on the source host stays as it =0Awas= previously.
        So basically af= ter reboot, the migrated VM stays on host only.
=0A

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

=
--28998604-649596623-1362084143=:47326-- --===============6437979433882301732== 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 --===============6437979433882301732==-- From xen-users-bounces@lists.xen.org Thu Feb 28 20:43:39 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 28 Feb 2013 20:43: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 1UBAJB-0003hL-Qs; Thu, 28 Feb 2013 20:42:29 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UBAJA-0003hF-Ce for xen-users@lists.xen.org; Thu, 28 Feb 2013 20:42:28 +0000 Received: from [85.158.137.99:14903] by server-10.bemta-3.messagelabs.com id 13/BE-19664-331CF215; Thu, 28 Feb 2013 20:42:27 +0000 X-Env-Sender: epretorious@yahoo.com X-Msg-Ref: server-15.tower-217.messagelabs.com!1362084145!16295491!1 X-Originating-IP: [98.138.91.142] X-SpamReason: No, hits=0.9 required=7.0 tests=HTML_40_50,HTML_MESSAGE, MAILTO_TO_SPAM_ADDR,ML_RADAR_SPEW_LINKS_12,ML_RADAR_SPEW_LINKS_14, ML_RADAR_SPEW_LINKS_6,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 17453 invoked from network); 28 Feb 2013 20:42:26 -0000 Received: from nm12-vm3.bullet.mail.ne1.yahoo.com (HELO nm12-vm3.bullet.mail.ne1.yahoo.com) (98.138.91.142) by server-15.tower-217.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 28 Feb 2013 20:42:26 -0000 Received: from [98.138.90.52] by nm12.bullet.mail.ne1.yahoo.com with NNFMP; 28 Feb 2013 20:42:24 -0000 Received: from [98.138.226.169] by tm5.bullet.mail.ne1.yahoo.com with NNFMP; 28 Feb 2013 20:42:24 -0000 Received: from [127.0.0.1] by omp1070.mail.ne1.yahoo.com with NNFMP; 28 Feb 2013 20:42:24 -0000 X-Yahoo-Newman-Property: ymail-3 X-Yahoo-Newman-Id: 772454.85059.bm@omp1070.mail.ne1.yahoo.com Received: (qmail 56897 invoked by uid 60001); 28 Feb 2013 20:42:24 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1362084144; bh=A69qbJ7BcGEklj9tZJVc/+nR8m0V8BHAMXsUV+Qa9Ls=; h=X-YMail-OSG:Received:X-Rocket-MIMEInfo:X-Mailer:References:Message-ID:Date:From:Reply-To:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type; b=TuzIf703cYma92s2vgo6YGi16N4axyCeGaRX3BmIwK22+y4bxPlRPQCJqspRnaUWpJBUVMgi2kUxfoYxXAhmIXszG7UwgVMjTUF4jkUn0Yv0ogWnB1fVU4gu8Dabj1rzfujmIsnOdjgavNEdk1GtvNG+15UmheYqHyJcHkcZeGg= DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=X-YMail-OSG:Received:X-Rocket-MIMEInfo:X-Mailer:References:Message-ID:Date:From:Reply-To:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type; b=wcnBLAr7Muj0v2WkylIzHa7SAo4aUBmtABVigcFoTKg4oXo8qW2zFR/A6l8c4gB06EKBv1feeaA8Cu4pbLQDUlarvRS+Um5IGhgNtvflsKr+5yNkX5E77hngmO+EyQwK/E5C0ODlFLj0fnrPKL3m1efoxl2DD+Ud5tGj7PfnA0o=; X-YMail-OSG: ft1E12wVM1nKMG4Dc59It6zOLJ5CKFrrtrOhP9QYT4z.5e6 q3.E.fN_y6XWhdBtdx4vIEZ1Mrl2gg.5F0Y_3U4Vgxa.2xRp7BeIwctt6dMJ mUIsbsLUMYStMQfZeZxt7f53rcLWpW095R3h57jSaKPXRhomEc2bMdDq0md3 D17fTFFl0pygazLYt7yuQ8eAEnRMP8YHLA0u.zBNk4aKGDVaOvqnMB47kZ6c F8Z2nb0DVVYdTXyBGRjyl7cvC1XF6S_6HkEOzLWiy_GI49TY1Dk9M8ZQUDyH bn2VtEsQutfdXHveFV8jQl9OEKdwUXpHFeBScC0c_XaAJHs4Z1ny0prtR2cV V73k2JNWDxaED.ckR3qwD1Wf1CFYnN9HdbkSxKnTpiNYgYH6mgQnc0qW1wIl Jh1oEtYEqKglqGJCqXfKm.INZcFrBOnGPu2jQY.KW8onQsq1j.UHJAp1NTPJ Kn7z4igNNVb4SzS30XnySivDkn7ZsriSm07ZfY4Jpa.WnBBo8U9M51X6ggNm J8dkllwcw855naXmZVSpjJcGjw5w- Received: from [74.197.253.230] by web126001.mail.ne1.yahoo.com via HTTP; Thu, 28 Feb 2013 12:42:23 PST X-Rocket-MIMEInfo: 001.001, TG9rZXNoOgoKVGhlIGZpcnN0IG9yZGVyIG9mIGJ1c2luZXNzIGlzIHRvIGRldGVybWluZSB3aHkgdGhlIG1pZ3JhdGlvbiBmYWlsZWQuCgpDaGVjayB0aGUgZmlsZXMgeGVuZC5sb2cgJiB4ZW5kLWRlYnVnLmxvZyAobG9jYXRlZCBpbiAvdmFyL2xvZy94ZW4vKSB0byBzZWUgd2h5IHRoZSBtaWdyYXRpb24gZmFpbGVkIHRvIGNvbXBsZXRlIHN1Y2Nlc3NmdWxseS4gKEhpbnQ6IEkgc29tZXRpbWVzIHdhdGNoIHRoZXNlIGZpbGVzIFtvbiB0aGUgZGVzdGluYXRpb25dIHVzaW5nICAvdXNyL2Jpbi90YWlsIHdpdGgBMAEBAQE- X-Mailer: YahooMailWebService/0.8.135.514 References: Message-ID: <1362084143.47326.YahooMailNeo@web126001.mail.ne1.yahoo.com> Date: Thu, 28 Feb 2013 12:42:23 -0800 (PST) From: Eric To: "xen-users@lists.xen.org" In-Reply-To: MIME-Version: 1.0 Cc: Lokesh Walase Subject: Re: [Xen-users] After VM migration , shows entry at both destination & host X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: Eric List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============6437979433882301732==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============6437979433882301732== Content-Type: multipart/alternative; boundary="28998604-649596623-1362084143=:47326" --28998604-649596623-1362084143=:47326 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Lokesh:=0A=0AThe first order of business is to determine why the migration = failed.=0A=0ACheck the files xend.log & xend-debug.log (located in /var/log= /xen/) to see why the migration failed to complete successfully. (Hint: I s= ometimes watch these files [on the destination] using /usr/bin/tail with t= he --follow flag to see the entries as they're added in real-time.)=0A=0AHT= H,=0AEric Pretorious=0ATruckee, CA=0A=0A=0A=0A=0A=0A>______________________= __________=0A> From: Lokesh Walase =0A>To: xen-users@= lists.xen.org =0A>Sent: Wednesday, February 27, 2013 11:26 PM=0A>Subject: [= Xen-users] After VM migration , shows entry at both destination & host=0A> = =0A>=0A>Hello,=0A>=A0=A0=A0=A0=A0=A0 I have installed =0Axen-hypervisor-4.1= -amd64 successfully on 4 hosts (with Ubuntu-12.04 as =0Adom0). =0A>=A0=A0= =A0=A0=A0=A0 I tried live migration of a virtual machine from one host to = =0Aanother via command line : xm migrate -l = =0A>=A0=A0=A0=A0=A0=A0 ( host_ip_adrress is static-ip )=0A>=0A>The problems= are : =0A>=0A>=A0 =A0 =A0=A0 1. During migration, I can see the entry of t= he VM appearing in the Virtual Machine Manager (VMM) of destination host.= =0A>=A0 =A0 =A0=A0 2. After migration is complete, both the source as well = as the =0Adestination host show the entry for corresponding VM in VMM.=0A>= =A0=A0=A0=A0=A0=A0 3. After reboot, the destination host does not show=A0 m= igrated VM, but the entry on the source host stays as it =0Awas previously.= =0A>=A0=A0=A0=A0=A0=A0=A0 So basically after reboot, the migrated VM stays= on host only.=0A>=0A>_______________________________________________=0A>Xe= n-users mailing list=0A>Xen-users@lists.xen.org=0A>http://lists.xen.org/xen= -users=0A>=0A> --28998604-649596623-1362084143=:47326 Content-Type: text/html; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable
Lokesh:
The first order of business is to determine why the migration failed.=

Check the files xend.log & xend-debug.log (located in /var/log/= xen/) to see why the migration failed to complete successfully. (Hint: I so= metimes watch these files [on the destination] using /usr/bin/tail with th= e --follow flag to see the entries as they're added in real-time.)

H= TH,
Eric Pretorious
Truckee, CA

<= br>
= From: Lokesh Walase <flokeshw24@= gmail.com>
To: xen-= users@lists.xen.org
Sent:= Wednesday, February 27, 2013 11:26 PM
Subject: [Xen-users] After VM migration , shows entry = at both destination & host

=0A
Hello,
     &= nbsp; I have installed =0Axen-hypervisor-4.1-amd64 successfully on 4 hosts = (with Ubuntu-12.04 as =0Adom0).
       I = tried live migration of a virtual machine from one host to =0Aanother via c= ommand line : xm migrate -l <domain_id> <host_ip_address>
&n= bsp;      ( host_ip_adrress is static-ip )

= The problems are :

=0A=0A
       1. During= migration, I can see the entry of the VM appearing in the Virtual Machine = Manager (VMM) of destination host.
 =0A      2= . After migration is complete, both the source as well as the =0Adestinatio= n host show the entry for corresponding VM in VMM.
=0A=0A
 &nb= sp;     3. After reboot, the destination host does not = show  migrated VM, but the entry on the source host stays as it =0Awas= previously.
        So basically af= ter reboot, the migrated VM stays on host only.
=0A

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

=
--28998604-649596623-1362084143=:47326-- --===============6437979433882301732== 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 --===============6437979433882301732==-- From xen-users-bounces@lists.xen.org Thu Feb 28 21:47:38 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 28 Feb 2013 21:47: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 1UBBJ2-000547-SQ; Thu, 28 Feb 2013 21:46:24 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UBBJ1-000542-9Q for xen-users@lists.xen.org; Thu, 28 Feb 2013 21:46:23 +0000 Received: from [85.158.143.99:16008] by server-2.bemta-4.messagelabs.com id 88/FF-12656-E20DF215; Thu, 28 Feb 2013 21:46:22 +0000 X-Env-Sender: tosterman@gmail.com X-Msg-Ref: server-3.tower-216.messagelabs.com!1362087979!29098573!1 X-Originating-IP: [209.85.210.181] 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.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 28107 invoked from network); 28 Feb 2013 21:46:20 -0000 Received: from mail-ia0-f181.google.com (HELO mail-ia0-f181.google.com) (209.85.210.181) by server-3.tower-216.messagelabs.com with RC4-SHA encrypted SMTP; 28 Feb 2013 21:46:20 -0000 Received: by mail-ia0-f181.google.com with SMTP id w33so2004541iag.26 for ; Thu, 28 Feb 2013 13:46:18 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:reply-to:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=v04qzgTyBSpXRdGlq3ZsE9PgzteRO7+lI/6zrvas2cQ=; b=lOxvQS4h8iCW2RVKHcV6cOKJrqktOQed8tbVfdQ8JDTZcADl400cGavXxRfrv0/Skr tFx0jYarfk7hdVjUiJ01UyJnC4Wk2NvjgRoH2NMh3fC+AYCfGeFwAJB2HSUZsV0u5k+a cMqIGTqPIBSwu7jYQagXDQetgVmdECs6eBpBeIqHgdizJy7A6pjPdLo6XUmFdzg3cCjd BEVWGuz5rSEqnnDNbB4ZynC7LA7lIP4iFeS0IhnKMWQgW81J3KrlTg6T/OUmWN4O3JOa 20mkCyFg+zGuZ30ZK5L8LXKYc3BI14b6lOgzMMtR+cW7vUvxZB2FvVr2ncMW1OtBTgsm WauQ== MIME-Version: 1.0 X-Received: by 10.43.134.202 with SMTP id id10mr4297166icc.46.1362087978642; Thu, 28 Feb 2013 13:46:18 -0800 (PST) Received: by 10.64.60.136 with HTTP; Thu, 28 Feb 2013 13:46:18 -0800 (PST) In-Reply-To: <1361890542.26546.298.camel@zakaz.uk.xensource.com> References: <1361784654.26546.165.camel@zakaz.uk.xensource.com> <1361805642.26546.184.camel@zakaz.uk.xensource.com> <1361866314.11431.23.camel@dagon.hellion.org.uk> <1361890542.26546.298.camel@zakaz.uk.xensource.com> Date: Thu, 28 Feb 2013 16:46:18 -0500 Message-ID: From: Travis Osterman To: xen-users Cc: Ian Campbell Subject: Re: [Xen-users] pv guest fails to start after 4.2 upgrade X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: travis@wsor.net List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org > So I asked around and there is basically no way the qemu-xen-trad blktap > module should be active for any reason in a Xen 4.2 system with xl. That > is the deadest of dead code... > > Could you send a full set of logs (xl -vvv create, /var/log/xen/*) and > your guest config for this new issue please. Here is the full report from a freshly rebooted server. /* * Fresh reboot, all xl-related services off */ # emerge --info http://pastebin.com/XBK7fwXm # lsof -X | grep -i tap (nothing) # ls -R /var/run/{xen,tap} /var/run/tap: /var/run/xen: # ps -e | grep "xl\|qemu\|xen" 48 ? 00:00:00 xenwatch 49 ? 00:00:00 xenbus 713 ? 00:00:00 xen_pciback_wor /* * bringing up xenstored */ # /etc/init.d/xenstored start * Starting xenstored daemon ... * Setting domain0 name record # lsof -X | grep -i tap (nothing) # ls -R /var/run/{xen,tap} /var/run/tap: st /var/run/xen: # ps -e | grep "xl\|qemu\|xen" 48 ? 00:00:00 xenwatch 49 ? 00:00:00 xenbus 713 ? 00:00:00 xen_pciback_wor 9264 ? 00:00:00 xenstored /* * bringing up xenconsoled (previously in default runlevel) */ # /etc/init.d/xenconsoled start * Starting xenconsoled daemon ... [ ok ] # lsof -X | grep -i tap # ls -R /var/run/{xen,tap} /var/run/tap: /var/run/xen: xen ~ # ps -e | grep "xl\|qemu\|xen" 48 ? 00:00:00 xenwatch 49 ? 00:00:00 xenbus 713 ? 00:00:00 xen_pciback_wor 9264 ? 00:00:00 xenstored 9288 ? 00:00:00 xenconsoled /* * just dom0 started */ # xl list Name ID Mem VCPUs State Time(s) Domain-0 0 32106 8 r----- 52.7 # xl info http://pastebin.com/fx0F4cbm # xl dmesg http://pastebin.com/cX9b3Yt5 # grep ^[^[:space:]*#] /data/xen/prime.pv name = "prime" memory = 2048 vcpus=8 vif=['bridge=xenbr0,mac=00:16:3E:1F:B8:0E,ip=192.168.1.1'] disk = ['file:/data/xen/prime.img,xvda,w'] kernel = "/usr/lib/xen/boot/pv-grub-x86_64.gz" extra = "(hd0,0)/grub/menu.lst xencons=tty iommu=soft" on_poweroff = 'destroy' on_reboot = 'restart' on_crash = 'restart' /* * PV using pvgrub (with manually creating /var/run/xen */ # xl -vvv create /data/xen/prime.pv http://pastebin.com/FMTWAqJd # xl list Name ID Mem VCPUs State Time(s) Domain-0 0 29606 8 r----- 56.4 prime 1 2048 8 -b---- 33.9 /* * I needed to attach a couple NICs to finish brining my router online */ # xl pci-attach prime 0000:01:00.0 # xl pci-attach prime 0000:0a:00.0 /* * libblktapctl is up now */ # lsof -X | grep -i tap xl 9387 root mem REG 253,0 30400 1462266 /usr/lib64/libblktapctl.so.1.0.0 xl 9387 9388 root mem REG 253,0 30400 1462266 /usr/lib64/libblktapctl.so.1.0.0 # ls -R /var/run/{xen,tap} /var/run/tap: /var/run/xen: qmp-libxl-1 # ps -e | grep "xl\|qemu\|xen" 48 ? 00:00:00 xenwatch 49 ? 00:00:00 xenbus 713 ? 00:00:00 xen_pciback_wor 9264 ? 00:00:00 xenstored 9288 ? 00:00:00 xenconsoled 9327 ? 00:00:00 qemu-system-i38 9387 ? 00:00:00 xl # ls -1 /var/log/xen/*prime*.log /var/log/xen/qemu-dm-prime.log /var/log/xen/xl-prime.log # cat /var/log/xen/qemu-dm-prime.log xen ~ # cat /var/log/xen/xl-prime.log Waiting for domain prime (domid 1) to die [pid 9387] libxl: debug: libxl_event.c:512:libxl__ev_xswatch_register: watch w=0x627c10 wpath=@releaseDomain token=3/0: register slotnum=3 libxl: debug: libxl_event.c:457:watchfd_callback: watch w=0x627c10 wpath=@releaseDomain token=3/0: event epath=@releaseDomain libxl: debug: libxl.c:1015:domain_death_xswatch_callback: [evg=0x6299d0:1] from domid=1 nentries=1 rc=1 libxl: debug: libxl.c:1026:domain_death_xswatch_callback: [evg=0x6299d0:1] got=domaininfos[0] got->domain=1 libxl: debug: libxl.c:1053:domain_death_xswatch_callback: exists shutdown_reported=0 dominf.flags=ffff0020 libxl: debug: libxl.c:1019:domain_death_xswatch_callback: [evg=0] all reported libxl: debug: libxl.c:1083:domain_death_xswatch_callback: domain death search done /************************************************************************* * PV with pygrub */ # grep ^[^[:space:]*#] /tank/xen/config/spot.pv.orig name = "spot" memory = 2048 bootloader = "pygrub" vcpus=4 vif=['bridge=xenbr0,mac=00:16:3E:21:56:66,ip=192.168.1.30'] disk = ['file:/tank/xen/dev/spot.img,xvda,w'] # which pygrub /usr/bin/pygrub /* * boot via pygrub using img file */ # xl -vvv create /tank/xen/config/spot.pv.orig http://pastebin.com/x1GHPXTP /* * in the console */ http://pastebin.com/kiGchPx7 Key type dns_resolver registered registered taskstats version 1 XENBUS: Waiting for devices to initialise: 25s...20s...15s...10s...5s...0s...235s...230s...225s...220s...215s...210s... ............ :: Scanning for raid10...raid10 loaded. :: Scanning for linear...linear loaded. :: Scanning for multipath...multipath loaded. :: Scanning for e1000...e1000 loaded. :: Scanning for tg3...libphy, tg3 loaded. :: Scanning for scsi_transport_iscsi...scsi_transport_iscsi loaded. :: Scanning for libiscsi...libiscsi loaded. :: Scanning for cbc...cbc loaded. :: Scanning for aes-x86_64...aes-x86_64 loaded. :: Scanning for xts...gf128mul, xts loaded. >> Hint: Use parameter scandelay[=seconds] if you need waiting here >> Determining root device... !! Block device /dev/xvda2 is not a valid root device... !! Could not find the root block device in . Please specify another value or: press Enter for the same, type "shell" for a shell, or "q" to skip... root block device() :: shell # ls /dev/sd* ls: /dev/sd*: No such file or directory # ls /dev/hd* ls: /dev/hd*: No such file or directory # ls /dev/xv* ls: /dev/xv*: No such file or directory # exit /* * Logs */ # ls -1 /var/log/xen/*spot*.log /var/log/xen/qemu-dm-spot.log /var/log/xen/xl-spot.log # cat /var/log/xen/qemu-dm-spot.log (empty) # cat /var/log/xen/xl-spot.log Waiting for domain spot (domid 2) to die [pid 9749] libxl: debug: libxl_event.c:512:libxl__ev_xswatch_register: watch w=0x628a30 wpath=@releaseDomain token=3/0: register slotnum=3 libxl: debug: libxl_event.c:457:watchfd_callback: watch w=0x628a30 wpath=@releaseDomain token=3/0: event epath=@releaseDomain libxl: debug: libxl.c:1015:domain_death_xswatch_callback: [evg=0x625020:2] from domid=2 nentries=1 rc=1 libxl: debug: libxl.c:1026:domain_death_xswatch_callback: [evg=0x625020:2] got=domaininfos[0] got->domain=2 libxl: debug: libxl.c:1053:domain_death_xswatch_callback: exists shutdown_reported=0 dominf.flags=ffff0020 libxl: debug: libxl.c:1019:domain_death_xswatch_callback: [evg=0] all reported libxl: debug: libxl.c:1083:domain_death_xswatch_callback: domain death search done /* * loop workaround */ # losetup /dev/loop0 /tank/xen/dev/spot.img # xl -vvv create /tank/xen/config/spot.pv http://pastebin.com/nDmmftqA (works fine) I hope this helps. Sorry for the long email. -- T _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Thu Feb 28 21:47:38 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 28 Feb 2013 21:47: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 1UBBJ2-000547-SQ; Thu, 28 Feb 2013 21:46:24 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UBBJ1-000542-9Q for xen-users@lists.xen.org; Thu, 28 Feb 2013 21:46:23 +0000 Received: from [85.158.143.99:16008] by server-2.bemta-4.messagelabs.com id 88/FF-12656-E20DF215; Thu, 28 Feb 2013 21:46:22 +0000 X-Env-Sender: tosterman@gmail.com X-Msg-Ref: server-3.tower-216.messagelabs.com!1362087979!29098573!1 X-Originating-IP: [209.85.210.181] 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.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 28107 invoked from network); 28 Feb 2013 21:46:20 -0000 Received: from mail-ia0-f181.google.com (HELO mail-ia0-f181.google.com) (209.85.210.181) by server-3.tower-216.messagelabs.com with RC4-SHA encrypted SMTP; 28 Feb 2013 21:46:20 -0000 Received: by mail-ia0-f181.google.com with SMTP id w33so2004541iag.26 for ; Thu, 28 Feb 2013 13:46:18 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:reply-to:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=v04qzgTyBSpXRdGlq3ZsE9PgzteRO7+lI/6zrvas2cQ=; b=lOxvQS4h8iCW2RVKHcV6cOKJrqktOQed8tbVfdQ8JDTZcADl400cGavXxRfrv0/Skr tFx0jYarfk7hdVjUiJ01UyJnC4Wk2NvjgRoH2NMh3fC+AYCfGeFwAJB2HSUZsV0u5k+a cMqIGTqPIBSwu7jYQagXDQetgVmdECs6eBpBeIqHgdizJy7A6pjPdLo6XUmFdzg3cCjd BEVWGuz5rSEqnnDNbB4ZynC7LA7lIP4iFeS0IhnKMWQgW81J3KrlTg6T/OUmWN4O3JOa 20mkCyFg+zGuZ30ZK5L8LXKYc3BI14b6lOgzMMtR+cW7vUvxZB2FvVr2ncMW1OtBTgsm WauQ== MIME-Version: 1.0 X-Received: by 10.43.134.202 with SMTP id id10mr4297166icc.46.1362087978642; Thu, 28 Feb 2013 13:46:18 -0800 (PST) Received: by 10.64.60.136 with HTTP; Thu, 28 Feb 2013 13:46:18 -0800 (PST) In-Reply-To: <1361890542.26546.298.camel@zakaz.uk.xensource.com> References: <1361784654.26546.165.camel@zakaz.uk.xensource.com> <1361805642.26546.184.camel@zakaz.uk.xensource.com> <1361866314.11431.23.camel@dagon.hellion.org.uk> <1361890542.26546.298.camel@zakaz.uk.xensource.com> Date: Thu, 28 Feb 2013 16:46:18 -0500 Message-ID: From: Travis Osterman To: xen-users Cc: Ian Campbell Subject: Re: [Xen-users] pv guest fails to start after 4.2 upgrade X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: travis@wsor.net List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org > So I asked around and there is basically no way the qemu-xen-trad blktap > module should be active for any reason in a Xen 4.2 system with xl. That > is the deadest of dead code... > > Could you send a full set of logs (xl -vvv create, /var/log/xen/*) and > your guest config for this new issue please. Here is the full report from a freshly rebooted server. /* * Fresh reboot, all xl-related services off */ # emerge --info http://pastebin.com/XBK7fwXm # lsof -X | grep -i tap (nothing) # ls -R /var/run/{xen,tap} /var/run/tap: /var/run/xen: # ps -e | grep "xl\|qemu\|xen" 48 ? 00:00:00 xenwatch 49 ? 00:00:00 xenbus 713 ? 00:00:00 xen_pciback_wor /* * bringing up xenstored */ # /etc/init.d/xenstored start * Starting xenstored daemon ... * Setting domain0 name record # lsof -X | grep -i tap (nothing) # ls -R /var/run/{xen,tap} /var/run/tap: st /var/run/xen: # ps -e | grep "xl\|qemu\|xen" 48 ? 00:00:00 xenwatch 49 ? 00:00:00 xenbus 713 ? 00:00:00 xen_pciback_wor 9264 ? 00:00:00 xenstored /* * bringing up xenconsoled (previously in default runlevel) */ # /etc/init.d/xenconsoled start * Starting xenconsoled daemon ... [ ok ] # lsof -X | grep -i tap # ls -R /var/run/{xen,tap} /var/run/tap: /var/run/xen: xen ~ # ps -e | grep "xl\|qemu\|xen" 48 ? 00:00:00 xenwatch 49 ? 00:00:00 xenbus 713 ? 00:00:00 xen_pciback_wor 9264 ? 00:00:00 xenstored 9288 ? 00:00:00 xenconsoled /* * just dom0 started */ # xl list Name ID Mem VCPUs State Time(s) Domain-0 0 32106 8 r----- 52.7 # xl info http://pastebin.com/fx0F4cbm # xl dmesg http://pastebin.com/cX9b3Yt5 # grep ^[^[:space:]*#] /data/xen/prime.pv name = "prime" memory = 2048 vcpus=8 vif=['bridge=xenbr0,mac=00:16:3E:1F:B8:0E,ip=192.168.1.1'] disk = ['file:/data/xen/prime.img,xvda,w'] kernel = "/usr/lib/xen/boot/pv-grub-x86_64.gz" extra = "(hd0,0)/grub/menu.lst xencons=tty iommu=soft" on_poweroff = 'destroy' on_reboot = 'restart' on_crash = 'restart' /* * PV using pvgrub (with manually creating /var/run/xen */ # xl -vvv create /data/xen/prime.pv http://pastebin.com/FMTWAqJd # xl list Name ID Mem VCPUs State Time(s) Domain-0 0 29606 8 r----- 56.4 prime 1 2048 8 -b---- 33.9 /* * I needed to attach a couple NICs to finish brining my router online */ # xl pci-attach prime 0000:01:00.0 # xl pci-attach prime 0000:0a:00.0 /* * libblktapctl is up now */ # lsof -X | grep -i tap xl 9387 root mem REG 253,0 30400 1462266 /usr/lib64/libblktapctl.so.1.0.0 xl 9387 9388 root mem REG 253,0 30400 1462266 /usr/lib64/libblktapctl.so.1.0.0 # ls -R /var/run/{xen,tap} /var/run/tap: /var/run/xen: qmp-libxl-1 # ps -e | grep "xl\|qemu\|xen" 48 ? 00:00:00 xenwatch 49 ? 00:00:00 xenbus 713 ? 00:00:00 xen_pciback_wor 9264 ? 00:00:00 xenstored 9288 ? 00:00:00 xenconsoled 9327 ? 00:00:00 qemu-system-i38 9387 ? 00:00:00 xl # ls -1 /var/log/xen/*prime*.log /var/log/xen/qemu-dm-prime.log /var/log/xen/xl-prime.log # cat /var/log/xen/qemu-dm-prime.log xen ~ # cat /var/log/xen/xl-prime.log Waiting for domain prime (domid 1) to die [pid 9387] libxl: debug: libxl_event.c:512:libxl__ev_xswatch_register: watch w=0x627c10 wpath=@releaseDomain token=3/0: register slotnum=3 libxl: debug: libxl_event.c:457:watchfd_callback: watch w=0x627c10 wpath=@releaseDomain token=3/0: event epath=@releaseDomain libxl: debug: libxl.c:1015:domain_death_xswatch_callback: [evg=0x6299d0:1] from domid=1 nentries=1 rc=1 libxl: debug: libxl.c:1026:domain_death_xswatch_callback: [evg=0x6299d0:1] got=domaininfos[0] got->domain=1 libxl: debug: libxl.c:1053:domain_death_xswatch_callback: exists shutdown_reported=0 dominf.flags=ffff0020 libxl: debug: libxl.c:1019:domain_death_xswatch_callback: [evg=0] all reported libxl: debug: libxl.c:1083:domain_death_xswatch_callback: domain death search done /************************************************************************* * PV with pygrub */ # grep ^[^[:space:]*#] /tank/xen/config/spot.pv.orig name = "spot" memory = 2048 bootloader = "pygrub" vcpus=4 vif=['bridge=xenbr0,mac=00:16:3E:21:56:66,ip=192.168.1.30'] disk = ['file:/tank/xen/dev/spot.img,xvda,w'] # which pygrub /usr/bin/pygrub /* * boot via pygrub using img file */ # xl -vvv create /tank/xen/config/spot.pv.orig http://pastebin.com/x1GHPXTP /* * in the console */ http://pastebin.com/kiGchPx7 Key type dns_resolver registered registered taskstats version 1 XENBUS: Waiting for devices to initialise: 25s...20s...15s...10s...5s...0s...235s...230s...225s...220s...215s...210s... ............ :: Scanning for raid10...raid10 loaded. :: Scanning for linear...linear loaded. :: Scanning for multipath...multipath loaded. :: Scanning for e1000...e1000 loaded. :: Scanning for tg3...libphy, tg3 loaded. :: Scanning for scsi_transport_iscsi...scsi_transport_iscsi loaded. :: Scanning for libiscsi...libiscsi loaded. :: Scanning for cbc...cbc loaded. :: Scanning for aes-x86_64...aes-x86_64 loaded. :: Scanning for xts...gf128mul, xts loaded. >> Hint: Use parameter scandelay[=seconds] if you need waiting here >> Determining root device... !! Block device /dev/xvda2 is not a valid root device... !! Could not find the root block device in . Please specify another value or: press Enter for the same, type "shell" for a shell, or "q" to skip... root block device() :: shell # ls /dev/sd* ls: /dev/sd*: No such file or directory # ls /dev/hd* ls: /dev/hd*: No such file or directory # ls /dev/xv* ls: /dev/xv*: No such file or directory # exit /* * Logs */ # ls -1 /var/log/xen/*spot*.log /var/log/xen/qemu-dm-spot.log /var/log/xen/xl-spot.log # cat /var/log/xen/qemu-dm-spot.log (empty) # cat /var/log/xen/xl-spot.log Waiting for domain spot (domid 2) to die [pid 9749] libxl: debug: libxl_event.c:512:libxl__ev_xswatch_register: watch w=0x628a30 wpath=@releaseDomain token=3/0: register slotnum=3 libxl: debug: libxl_event.c:457:watchfd_callback: watch w=0x628a30 wpath=@releaseDomain token=3/0: event epath=@releaseDomain libxl: debug: libxl.c:1015:domain_death_xswatch_callback: [evg=0x625020:2] from domid=2 nentries=1 rc=1 libxl: debug: libxl.c:1026:domain_death_xswatch_callback: [evg=0x625020:2] got=domaininfos[0] got->domain=2 libxl: debug: libxl.c:1053:domain_death_xswatch_callback: exists shutdown_reported=0 dominf.flags=ffff0020 libxl: debug: libxl.c:1019:domain_death_xswatch_callback: [evg=0] all reported libxl: debug: libxl.c:1083:domain_death_xswatch_callback: domain death search done /* * loop workaround */ # losetup /dev/loop0 /tank/xen/dev/spot.img # xl -vvv create /tank/xen/config/spot.pv http://pastebin.com/nDmmftqA (works fine) I hope this helps. Sorry for the long email. -- T _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Thu Feb 28 21:47:49 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 28 Feb 2013 21:47: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 1UBBJH-00055P-UQ; Thu, 28 Feb 2013 21:46:39 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UBBJG-00055C-BW for xen-users@lists.xen.org; Thu, 28 Feb 2013 21:46:38 +0000 Received: from [193.109.254.147:63406] by server-4.bemta-14.messagelabs.com id 4A/5F-20719-D30DF215; Thu, 28 Feb 2013 21:46:37 +0000 X-Env-Sender: knockknock@gmail.com X-Msg-Ref: server-8.tower-27.messagelabs.com!1362087995!9347889!1 X-Originating-IP: [74.125.82.178] X-SpamReason: No, hits=0.3 required=7.0 tests=RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 6611 invoked from network); 28 Feb 2013 21:46:36 -0000 Received: from mail-we0-f178.google.com (HELO mail-we0-f178.google.com) (74.125.82.178) by server-8.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 28 Feb 2013 21:46:36 -0000 Received: by mail-we0-f178.google.com with SMTP id u7so704851wey.9 for ; Thu, 28 Feb 2013 13:46:35 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:mime-version:sender:from:date:x-google-sender-auth :message-id:subject:to:content-type; bh=6gpt32WLjF46t41edvsO/NHW5n/JEkRt4uvbuKcf0dc=; b=tKZ1L5Vtm7tekJG6Z0G3Pw7+2I3VVFtlZ4hN+w+co8SApF15DfPQAXQHXaS6iSQdMi 0VkJhRPfAk9G2mAK8uyj8/o6H5CwaHgdcW/lypX+0VlRwUO4A0uMRzkPyh6oceDYcNh+ Zw5XfYcZW+AXt0kBmAM2TZz92CJ1H44dRhTLHPCSq7sKOARK9gdXTVeV07Cpt5GUX7fF 0nAei/7ZqB8++KNrzaOkOrJUFhg1q/ELZ/ICv0VN55rSW1KZV1NrdUAOGF81P9nzNs0V XmG3A1X+ugkmDI7nGUdLB4VktM+H7pLQKsglw6PGAbWb35u7D6wZehiiThIWIRl+Nreq Y6sA== X-Received: by 10.194.119.68 with SMTP id ks4mr13884985wjb.3.1362087995662; Thu, 28 Feb 2013 13:46:35 -0800 (PST) MIME-Version: 1.0 Received: by 10.194.26.166 with HTTP; Thu, 28 Feb 2013 13:46:15 -0800 (PST) From: Eric Shelton Date: Thu, 28 Feb 2013 16:46:15 -0500 X-Google-Sender-Auth: dtG-ciGWABczvyEu6_Wj9iNvcjU Message-ID: To: xen-users@lists.xen.org Subject: Re: [Xen-users] VGA passthrough radeon 4850 as primary card X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org After looking high and low for a solution for primary PCI passthrough, I found the below patch works perfectly for doing primary passthrough of my 6570 adapter (it was also fine with a 5450 I was using previously): http://lists.xen.org/archives/html/xen-devel/2012-12/msg00009.html Note that I am running Xen 4.3-unstable and Linux kernel 3.7.8 on an AMD platform. I never tried it on 4.2. One tricky part is applying the patch at the right time, as QEMU is dynamically downloaded. During "make tools" I wait until right after the git download of qemu-traditional, CTRL-Z the make session to pause it, apply the patch against qemu-traditional, and then "fg" the make session to let it continue. Since QEMU is built first in tools, you don't have to wait long. Apparently the Radeon cards are doing some oddball things in PCI config space and one of the MMIO's. The above patch (which is based on a much older original patch) implements these quirks, taking into account any MMIO address translation, and implements the intrinsic IO and MMIO regions for a primary VGA device. Additionally, it ensures that the VGA rom is executed properly. The patch is only good against qemu-traditional, although I think the same techniques could be readily implemented in qemu-unstable. In fact, one of their developers recently put out a patch essentially doing this: http://lists.nongnu.org/archive/html/qemu-devel/2013-02/msg02759.html The patch was worked far and away better than any of the other schemes I have seen discussed. I can boot into a clean HVM, see a regular BIOS POST, run the Win 7 install disc, and install the Catalyst drivers (although sometimes the driver install will have issues). There is no need to do any tricks with installing with the emulated Cirrus video and then rebooting without it later - you can just start right off with a passthrough setup. Running the provided script for unbinding and binding, I can repeatedly shut down Windows, get back to a functional text console, and start up the Windows HVM again without rebooting (with some solutions, this does not work, and can even take down the system, unless you do things like eject the video card in Windows, etc.). Also the accompanying HDMI audio PCI device is also passed through and streams audio successfully. With this, I can run my HVM as an HTPC (although HDCP still blocks protected content playback), which was one of my goals with this system. I am also doing passthrough of one of my USB controllers to provide me with a keyboard and mouse, and ultimately a USB HDMI-CEC adapter. If you use the above patch, I think you should be able to painlessly implement primary VGA PCI passthrough with a Radeon card (assuming you're up for compiling Xen). If the patch is cleaned up a little more (issues include: (1) I don't think it instantiates the 0x3C0-DF VGA IO range for non-IGD/non-ATI cards, (2) it may try to implement the VGA ranges for all cards - not just the primary (observance of the VGA/ISA enable bits may help this), and (3) there may be a few too many hard-coded values), it would be nice to see this formally incorporated into 4.3, as it works very nicely. > Is there any special reason you use primary passthrough? because using > the ati vga as secondary is A LOT easier and simpler (and as stable > and performant). To be honest, i never got primary passthrough to work > with any of my radeon cards, but secondary works quite well for 2,5 > years now. > > So my advice: use secondary, boot and install domU normally, then > install the catalyst driver and reboot. Within the start-process, it > will automatically switch to the right vga near the end of the boot > and as an additional benefit you can use the vnc view as additional > input device if you for example don't have pci-passthrough for input > devices or want a remote interface anyway (with for example a > mediacenter). > > 2013/2/27 povder : > > Hi all > > > > I'm trying to enable VGA passthrough in linux domU without success. I > > want to pass through AMD Radeon HD 4850 - 03:00.0 VGA compatible > > controller: Advanced Micro Devices [AMD] nee ATI RV770 [Radeon HD > > 4850] as a _primary_ VGA for the VM. Nothing is showing up on the > > monitor that I have connected to graphics card's HDMI port. I have > > IOMMU enabled. I searched mailing lists and I don't know what to think > > about it. There is some information about ATI cards passthrough as > > primary VGA, some patches were posted but that was long time ago so my > > first question is: > > Is passthrough of ATI devices as primary VGA supposed to work now in > > Xen 4.2.1 without patches? > > > > My second question is: > > How can i debug the problem? I can't access domU through SSH after > > it's created. When I set gfx_passthru to 0 it's starting normally. How > > can I tell what went wrong? > > > > When I create domU I get this in logs: > > dm-command: hot insert pass-through pci dev > > register_real_device: Assigning real physical device 03:00.0 ... > > 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: 0x3:0x0.0x0 > > pt_register_regions: IO region registered (size=0x10000000 > > base_addr=0xd000000c) > > pt_register_regions: IO region registered (size=0x00010000 > > base_addr=0xfe7f0004) > > pt_register_regions: IO region registered (size=0x00000100 > > base_addr=0x0000d001) > > pt_register_regions: Expansion ROM registered (size=0x00020000 > > base_addr=0xfe7c0002) > > pci_intx: intx=1 > > register_real_device: Real physical device 03:00.0 registered successfuly! > > > > I'm using Xen 4.2.1 and xl toolstack. I have the following in VM config file: > > > > builder = "hvm" > > gfx_passthru = 1 > > pci = ['03:00.0','03:00.1'] > > > > vm config file: > > full domU log: http://pastebin.com/raw.php?i=rc9xWcDJ > > part of lspci -vvv: http://pastebin.com/raw.php?i=wZXcJU7j > > xl info: http://pastebin.com/raw.php?i=zDrdNm9u > > xl dmesg: http://pastebin.com/raw.php?i=SmJ7MrB1 > > > > Please help. > > > > _______________________________________________ > > Xen-users mailing list > > Xen-users@xxxxxxxxxxxxx > > http://lists.xen.org/xen-users > > _______________________________________________ > Xen-users mailing list > Xen-users@xxxxxxxxxxxxx > 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 Feb 28 21:47:49 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 28 Feb 2013 21:47: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 1UBBJH-00055P-UQ; Thu, 28 Feb 2013 21:46:39 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UBBJG-00055C-BW for xen-users@lists.xen.org; Thu, 28 Feb 2013 21:46:38 +0000 Received: from [193.109.254.147:63406] by server-4.bemta-14.messagelabs.com id 4A/5F-20719-D30DF215; Thu, 28 Feb 2013 21:46:37 +0000 X-Env-Sender: knockknock@gmail.com X-Msg-Ref: server-8.tower-27.messagelabs.com!1362087995!9347889!1 X-Originating-IP: [74.125.82.178] X-SpamReason: No, hits=0.3 required=7.0 tests=RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 6611 invoked from network); 28 Feb 2013 21:46:36 -0000 Received: from mail-we0-f178.google.com (HELO mail-we0-f178.google.com) (74.125.82.178) by server-8.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 28 Feb 2013 21:46:36 -0000 Received: by mail-we0-f178.google.com with SMTP id u7so704851wey.9 for ; Thu, 28 Feb 2013 13:46:35 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:mime-version:sender:from:date:x-google-sender-auth :message-id:subject:to:content-type; bh=6gpt32WLjF46t41edvsO/NHW5n/JEkRt4uvbuKcf0dc=; b=tKZ1L5Vtm7tekJG6Z0G3Pw7+2I3VVFtlZ4hN+w+co8SApF15DfPQAXQHXaS6iSQdMi 0VkJhRPfAk9G2mAK8uyj8/o6H5CwaHgdcW/lypX+0VlRwUO4A0uMRzkPyh6oceDYcNh+ Zw5XfYcZW+AXt0kBmAM2TZz92CJ1H44dRhTLHPCSq7sKOARK9gdXTVeV07Cpt5GUX7fF 0nAei/7ZqB8++KNrzaOkOrJUFhg1q/ELZ/ICv0VN55rSW1KZV1NrdUAOGF81P9nzNs0V XmG3A1X+ugkmDI7nGUdLB4VktM+H7pLQKsglw6PGAbWb35u7D6wZehiiThIWIRl+Nreq Y6sA== X-Received: by 10.194.119.68 with SMTP id ks4mr13884985wjb.3.1362087995662; Thu, 28 Feb 2013 13:46:35 -0800 (PST) MIME-Version: 1.0 Received: by 10.194.26.166 with HTTP; Thu, 28 Feb 2013 13:46:15 -0800 (PST) From: Eric Shelton Date: Thu, 28 Feb 2013 16:46:15 -0500 X-Google-Sender-Auth: dtG-ciGWABczvyEu6_Wj9iNvcjU Message-ID: To: xen-users@lists.xen.org Subject: Re: [Xen-users] VGA passthrough radeon 4850 as primary card X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org After looking high and low for a solution for primary PCI passthrough, I found the below patch works perfectly for doing primary passthrough of my 6570 adapter (it was also fine with a 5450 I was using previously): http://lists.xen.org/archives/html/xen-devel/2012-12/msg00009.html Note that I am running Xen 4.3-unstable and Linux kernel 3.7.8 on an AMD platform. I never tried it on 4.2. One tricky part is applying the patch at the right time, as QEMU is dynamically downloaded. During "make tools" I wait until right after the git download of qemu-traditional, CTRL-Z the make session to pause it, apply the patch against qemu-traditional, and then "fg" the make session to let it continue. Since QEMU is built first in tools, you don't have to wait long. Apparently the Radeon cards are doing some oddball things in PCI config space and one of the MMIO's. The above patch (which is based on a much older original patch) implements these quirks, taking into account any MMIO address translation, and implements the intrinsic IO and MMIO regions for a primary VGA device. Additionally, it ensures that the VGA rom is executed properly. The patch is only good against qemu-traditional, although I think the same techniques could be readily implemented in qemu-unstable. In fact, one of their developers recently put out a patch essentially doing this: http://lists.nongnu.org/archive/html/qemu-devel/2013-02/msg02759.html The patch was worked far and away better than any of the other schemes I have seen discussed. I can boot into a clean HVM, see a regular BIOS POST, run the Win 7 install disc, and install the Catalyst drivers (although sometimes the driver install will have issues). There is no need to do any tricks with installing with the emulated Cirrus video and then rebooting without it later - you can just start right off with a passthrough setup. Running the provided script for unbinding and binding, I can repeatedly shut down Windows, get back to a functional text console, and start up the Windows HVM again without rebooting (with some solutions, this does not work, and can even take down the system, unless you do things like eject the video card in Windows, etc.). Also the accompanying HDMI audio PCI device is also passed through and streams audio successfully. With this, I can run my HVM as an HTPC (although HDCP still blocks protected content playback), which was one of my goals with this system. I am also doing passthrough of one of my USB controllers to provide me with a keyboard and mouse, and ultimately a USB HDMI-CEC adapter. If you use the above patch, I think you should be able to painlessly implement primary VGA PCI passthrough with a Radeon card (assuming you're up for compiling Xen). If the patch is cleaned up a little more (issues include: (1) I don't think it instantiates the 0x3C0-DF VGA IO range for non-IGD/non-ATI cards, (2) it may try to implement the VGA ranges for all cards - not just the primary (observance of the VGA/ISA enable bits may help this), and (3) there may be a few too many hard-coded values), it would be nice to see this formally incorporated into 4.3, as it works very nicely. > Is there any special reason you use primary passthrough? because using > the ati vga as secondary is A LOT easier and simpler (and as stable > and performant). To be honest, i never got primary passthrough to work > with any of my radeon cards, but secondary works quite well for 2,5 > years now. > > So my advice: use secondary, boot and install domU normally, then > install the catalyst driver and reboot. Within the start-process, it > will automatically switch to the right vga near the end of the boot > and as an additional benefit you can use the vnc view as additional > input device if you for example don't have pci-passthrough for input > devices or want a remote interface anyway (with for example a > mediacenter). > > 2013/2/27 povder : > > Hi all > > > > I'm trying to enable VGA passthrough in linux domU without success. I > > want to pass through AMD Radeon HD 4850 - 03:00.0 VGA compatible > > controller: Advanced Micro Devices [AMD] nee ATI RV770 [Radeon HD > > 4850] as a _primary_ VGA for the VM. Nothing is showing up on the > > monitor that I have connected to graphics card's HDMI port. I have > > IOMMU enabled. I searched mailing lists and I don't know what to think > > about it. There is some information about ATI cards passthrough as > > primary VGA, some patches were posted but that was long time ago so my > > first question is: > > Is passthrough of ATI devices as primary VGA supposed to work now in > > Xen 4.2.1 without patches? > > > > My second question is: > > How can i debug the problem? I can't access domU through SSH after > > it's created. When I set gfx_passthru to 0 it's starting normally. How > > can I tell what went wrong? > > > > When I create domU I get this in logs: > > dm-command: hot insert pass-through pci dev > > register_real_device: Assigning real physical device 03:00.0 ... > > 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: 0x3:0x0.0x0 > > pt_register_regions: IO region registered (size=0x10000000 > > base_addr=0xd000000c) > > pt_register_regions: IO region registered (size=0x00010000 > > base_addr=0xfe7f0004) > > pt_register_regions: IO region registered (size=0x00000100 > > base_addr=0x0000d001) > > pt_register_regions: Expansion ROM registered (size=0x00020000 > > base_addr=0xfe7c0002) > > pci_intx: intx=1 > > register_real_device: Real physical device 03:00.0 registered successfuly! > > > > I'm using Xen 4.2.1 and xl toolstack. I have the following in VM config file: > > > > builder = "hvm" > > gfx_passthru = 1 > > pci = ['03:00.0','03:00.1'] > > > > vm config file: > > full domU log: http://pastebin.com/raw.php?i=rc9xWcDJ > > part of lspci -vvv: http://pastebin.com/raw.php?i=wZXcJU7j > > xl info: http://pastebin.com/raw.php?i=zDrdNm9u > > xl dmesg: http://pastebin.com/raw.php?i=SmJ7MrB1 > > > > Please help. > > > > _______________________________________________ > > Xen-users mailing list > > Xen-users@xxxxxxxxxxxxx > > http://lists.xen.org/xen-users > > _______________________________________________ > Xen-users mailing list > Xen-users@xxxxxxxxxxxxx > 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 Feb 28 22:25:59 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 28 Feb 2013 22:25: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 1UBBuL-0006VZ-QP; Thu, 28 Feb 2013 22:24:57 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UBBuJ-0006VU-Md for xen-users@lists.xen.org; Thu, 28 Feb 2013 22:24:55 +0000 Received: from [193.109.254.147:43533] by server-8.bemta-14.messagelabs.com id D0/2A-17325-739DF215; Thu, 28 Feb 2013 22:24:55 +0000 X-Env-Sender: murrayie@yahoo.co.uk X-Msg-Ref: server-10.tower-27.messagelabs.com!1362090269!4853797!1 X-Originating-IP: [77.238.189.63] X-SpamReason: No, hits=0.0 required=7.0 tests=HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 14965 invoked from network); 28 Feb 2013 22:24:31 -0000 Received: from nm6.bullet.mail.ird.yahoo.com (HELO nm6.bullet.mail.ird.yahoo.com) (77.238.189.63) by server-10.tower-27.messagelabs.com with SMTP; 28 Feb 2013 22:24:31 -0000 Received: from [212.82.105.244] by nm6.bullet.mail.ird.yahoo.com with NNFMP; 28 Feb 2013 22:24:29 -0000 Received: from [46.228.39.71] by tm16.bullet.mail.ird.yahoo.com with NNFMP; 28 Feb 2013 22:24:29 -0000 Received: from [127.0.0.1] by smtp108.mail.ir2.yahoo.com with NNFMP; 28 Feb 2013 22:24:29 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.co.uk; s=s1024; t=1362090269; bh=ga4Y2lSwXzIjeze/h35SIeJ/nwx2cQHFXanv7bGOW6A=; 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:References:In-Reply-To:Content-Type; b=kI80Lk/ULBKXoPubH+Wg6iHJdJ6lXhRsdjufUpq61+zS+Oiv5kPur3Ne92vfI3DQv0K+TXULuqBT12zVC1NXpfJ3I4xLx37sL0al+hSAT6EJyFCUoWhOSu7cCWsD0GmlNCGsPZVxYFvSPvalLTdEc9rFD1YieWMoLM3+mBoT84I= X-Yahoo-Newman-Id: 133802.74425.bm@smtp108.mail.ir2.yahoo.com X-Yahoo-Newman-Property: ymail-3 X-YMail-OSG: bCRXHyMVM1kwRl3QMZf18kjgHqRd8.4oDNyJAw3EC_Ust2o aGhtSGkDu3OhOGq3odKDpaV3.VB80EF5vLjZNDUfwTfK52O8Rjw58.H6iNYE 4j5br89Ea0QIY0zk8uVRyKtCSj4p2l5SktgXUTwWYzpXUIIcEUzm247Iy4DY cJTHsJh3zWcw0LBROlNnBTlLqd06pwYPMvnEf0HzkiVgtKpwi3q7SulErClJ oQdRI28WZ.tEHeXW08P9Ih2IdANM7Frlcwgabz2.LC_NYm5oLTG4L_Wot.Fj ErlSvOOwtyXNxPeR77qPM.WdwqkwGbKk6sM4JxJT1GjKvrvv.H1KSKDPVtmU ObIRd535K7JdENzL1MXZ_kmzwrZXs9TiFAgBdlQmKvX1Gzb2Er2gE8AidM5I pVT5_QIrXC8xjj08qYBST3vA2EOVst.5mFToS5HXYZQaYFuF1Cg-- X-Yahoo-SMTP: P.LfrmaswBDlKN6tCvtOaEZlSVsY Received: from [192.168.1.136] (murrayie@109.157.15.99 with plain) by smtp108.mail.ir2.yahoo.com with SMTP; 28 Feb 2013 22:24:28 +0000 UTC Message-ID: <512FD91C.4060803@yahoo.co.uk> Date: Thu, 28 Feb 2013 22:24:28 +0000 From: Ian User-Agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/20130221 Thunderbird/17.0.3 MIME-Version: 1.0 To: xen-users@lists.xen.org References: <1361874116.26546.256.camel@zakaz.uk.xensource.com> In-Reply-To: Subject: Re: [Xen-users] Xen Domain U can not install (on Ubuntu.) X-BeenThere: xen-users@lists.xen.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="===============3890240170407986976==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org This is a multi-part message in MIME format. --===============3890240170407986976== Content-Type: multipart/alternative; boundary="------------070300030602030008090403" This is a multi-part message in MIME format. --------------070300030602030008090403 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit > > I think it's related to the bridge network setting. I searched online > and still have no idea about it. > Although this against official advice, I find the old network bridge script works just fine, so I slip it into xencommons like so ... do_start () { /etc/xen/scripts/network-bridge start just run it manually (as root) if you want to see if it helps. > Thanks for your help! > > Yaodong > > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xen.org > http://lists.xen.org/xen-users --------------070300030602030008090403 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit

I think it's related to the bridge network setting. I searched online and still have no idea about it.



Although this against official advice, I find the old network bridge script works just fine, so I slip it into xencommons like so
...

do_start () {
/etc/xen/scripts/network-bridge start
 

just run it manually (as root) if you want to see if it helps.



Thanks for your help!

Yaodong


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

--------------070300030602030008090403-- --===============3890240170407986976== 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 --===============3890240170407986976==-- From xen-users-bounces@lists.xen.org Thu Feb 28 22:25:59 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 28 Feb 2013 22:25: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 1UBBuL-0006VZ-QP; Thu, 28 Feb 2013 22:24:57 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UBBuJ-0006VU-Md for xen-users@lists.xen.org; Thu, 28 Feb 2013 22:24:55 +0000 Received: from [193.109.254.147:43533] by server-8.bemta-14.messagelabs.com id D0/2A-17325-739DF215; Thu, 28 Feb 2013 22:24:55 +0000 X-Env-Sender: murrayie@yahoo.co.uk X-Msg-Ref: server-10.tower-27.messagelabs.com!1362090269!4853797!1 X-Originating-IP: [77.238.189.63] X-SpamReason: No, hits=0.0 required=7.0 tests=HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 14965 invoked from network); 28 Feb 2013 22:24:31 -0000 Received: from nm6.bullet.mail.ird.yahoo.com (HELO nm6.bullet.mail.ird.yahoo.com) (77.238.189.63) by server-10.tower-27.messagelabs.com with SMTP; 28 Feb 2013 22:24:31 -0000 Received: from [212.82.105.244] by nm6.bullet.mail.ird.yahoo.com with NNFMP; 28 Feb 2013 22:24:29 -0000 Received: from [46.228.39.71] by tm16.bullet.mail.ird.yahoo.com with NNFMP; 28 Feb 2013 22:24:29 -0000 Received: from [127.0.0.1] by smtp108.mail.ir2.yahoo.com with NNFMP; 28 Feb 2013 22:24:29 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.co.uk; s=s1024; t=1362090269; bh=ga4Y2lSwXzIjeze/h35SIeJ/nwx2cQHFXanv7bGOW6A=; 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:References:In-Reply-To:Content-Type; b=kI80Lk/ULBKXoPubH+Wg6iHJdJ6lXhRsdjufUpq61+zS+Oiv5kPur3Ne92vfI3DQv0K+TXULuqBT12zVC1NXpfJ3I4xLx37sL0al+hSAT6EJyFCUoWhOSu7cCWsD0GmlNCGsPZVxYFvSPvalLTdEc9rFD1YieWMoLM3+mBoT84I= X-Yahoo-Newman-Id: 133802.74425.bm@smtp108.mail.ir2.yahoo.com X-Yahoo-Newman-Property: ymail-3 X-YMail-OSG: bCRXHyMVM1kwRl3QMZf18kjgHqRd8.4oDNyJAw3EC_Ust2o aGhtSGkDu3OhOGq3odKDpaV3.VB80EF5vLjZNDUfwTfK52O8Rjw58.H6iNYE 4j5br89Ea0QIY0zk8uVRyKtCSj4p2l5SktgXUTwWYzpXUIIcEUzm247Iy4DY cJTHsJh3zWcw0LBROlNnBTlLqd06pwYPMvnEf0HzkiVgtKpwi3q7SulErClJ oQdRI28WZ.tEHeXW08P9Ih2IdANM7Frlcwgabz2.LC_NYm5oLTG4L_Wot.Fj ErlSvOOwtyXNxPeR77qPM.WdwqkwGbKk6sM4JxJT1GjKvrvv.H1KSKDPVtmU ObIRd535K7JdENzL1MXZ_kmzwrZXs9TiFAgBdlQmKvX1Gzb2Er2gE8AidM5I pVT5_QIrXC8xjj08qYBST3vA2EOVst.5mFToS5HXYZQaYFuF1Cg-- X-Yahoo-SMTP: P.LfrmaswBDlKN6tCvtOaEZlSVsY Received: from [192.168.1.136] (murrayie@109.157.15.99 with plain) by smtp108.mail.ir2.yahoo.com with SMTP; 28 Feb 2013 22:24:28 +0000 UTC Message-ID: <512FD91C.4060803@yahoo.co.uk> Date: Thu, 28 Feb 2013 22:24:28 +0000 From: Ian User-Agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/20130221 Thunderbird/17.0.3 MIME-Version: 1.0 To: xen-users@lists.xen.org References: <1361874116.26546.256.camel@zakaz.uk.xensource.com> In-Reply-To: Subject: Re: [Xen-users] Xen Domain U can not install (on Ubuntu.) X-BeenThere: xen-users@lists.xen.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="===============3890240170407986976==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org This is a multi-part message in MIME format. --===============3890240170407986976== Content-Type: multipart/alternative; boundary="------------070300030602030008090403" This is a multi-part message in MIME format. --------------070300030602030008090403 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit > > I think it's related to the bridge network setting. I searched online > and still have no idea about it. > Although this against official advice, I find the old network bridge script works just fine, so I slip it into xencommons like so ... do_start () { /etc/xen/scripts/network-bridge start just run it manually (as root) if you want to see if it helps. > Thanks for your help! > > Yaodong > > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xen.org > http://lists.xen.org/xen-users --------------070300030602030008090403 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit

I think it's related to the bridge network setting. I searched online and still have no idea about it.



Although this against official advice, I find the old network bridge script works just fine, so I slip it into xencommons like so
...

do_start () {
/etc/xen/scripts/network-bridge start
 

just run it manually (as root) if you want to see if it helps.



Thanks for your help!

Yaodong


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

--------------070300030602030008090403-- --===============3890240170407986976== 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 --===============3890240170407986976==--