From xen-users-bounces@lists.xen.org Fri Jan 01 10:49:41 2016 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 01 Jan 2016 10:49: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 1aExG2-0006un-IK; Fri, 01 Jan 2016 10:48:30 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1aExG0-0006ui-Uj for xen-users@lists.xen.org; Fri, 01 Jan 2016 10:48:29 +0000 Received: from [193.109.254.147] by server-5.bemta-14.messagelabs.com id 18/13-00475-C7956865; Fri, 01 Jan 2016 10:48:28 +0000 X-Env-Sender: a9121431@gmail.com X-Msg-Ref: server-11.tower-27.messagelabs.com!1451645306!14130648!1 X-Originating-IP: [209.85.218.65] X-SpamReason: No, hits=0.6 required=7.0 tests=MAILTO_TO_SPAM_ADDR, RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 7.35.1; banners=-,-,- X-VirusChecked: Checked Received: (qmail 58420 invoked from network); 1 Jan 2016 10:48:27 -0000 Received: from mail-oi0-f65.google.com (HELO mail-oi0-f65.google.com) (209.85.218.65) by server-11.tower-27.messagelabs.com with AES128-GCM-SHA256 encrypted SMTP; 1 Jan 2016 10:48:27 -0000 Received: by mail-oi0-f65.google.com with SMTP id o62so20738000oif.1 for ; Fri, 01 Jan 2016 02:48:27 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; bh=d6lfL6so5SJQ5jIZNnAUD2dFpFA0N7LhyLvfYykGzFo=; b=EmX3Hg+9LA2KezBu9SrXGuIFKvU+EoVfbI2w8dZii3qTfb519Rzx6aS+V4mSYz3BTm 55h0hd8vHcAW7rqfeJqgz+8w2EBzFrzVvWTALS7+mlNZy5bDIYR1+w8rjMBvxTu+l98y fySBrTR47EUqiVXrP0S8YlJvzPQ7g/XZ0jVMgRyDgcHZwvFDqDzlCmSWsmdM3wQRQCcl d6Fd91+o3/Y0htD7PKKTOmFDukS5+4byLfXy9kUaDUVhpCclJulew+Vd97D26xhtCf56 NGLZ/XUZXyxxuRXOBo8g5jVk0u9dvuQQFvFkIhBhvI/aDpnTsmdciTaWmf0qRp6YKCmI BFng== MIME-Version: 1.0 X-Received: by 10.202.85.194 with SMTP id j185mr47532588oib.107.1451645305752; Fri, 01 Jan 2016 02:48:25 -0800 (PST) Received: by 10.182.153.233 with HTTP; Fri, 1 Jan 2016 02:48:25 -0800 (PST) In-Reply-To: <20151230160147.88486qsc1m9vm1kw@vfemail.net> References: <20151230160147.88486qsc1m9vm1kw@vfemail.net> Date: Fri, 1 Jan 2016 18:48:25 +0800 Message-ID: From: John Mok To: "xen-users@lists.xen.org" Subject: Re: [Xen-users] PCI Passthrough of iwlwifi adapter into Windows HVM failed to start X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org >Just to confirm, are you certain that the driver in question really does work when it is running on baremetal ....? Yes, the driver works on baremetal, but not try on other virtualization passthrough. >I'm just guessing here, but does dmesg/journalctl have anything to say on the Dom0 side? In particular, an error about the driver >attempting to write to read-only configuration space could indicate that you need the "permissive=1" flag. See http://wiki.xenproject.org/wiki/Xen_PCI_Passthrough#PV_guests_and_PCI_quirks I do not see anything complaining driver failing to write to read-only configuration space. But somehow the Windows 7 HVM guest could not bring up the Intel AC 7265 driver with error code 10 (fail to start). As the driver could run on baremetal, it should be a Xen PCI passthrough problem. I hope someone could advise how to solve the problem, or point me to the right direction. Thanks a lot. John Mok On Thu, Dec 31, 2015 at 6:01 AM, wrote: > Quoting "John Mok" : > >> Hi, >> >> I am using Xen 4.4.1 on Debian Jessie on Lenovo ThinkPad X250. >> >> I succeeded to passthrough the Intel AC 7265 adapter to the Windows >> HVM. However, when I installed the Intel driver (with embedded >> firmware), the device failed to start with code 10. >> >> I tried to switch between GPL PV driver and SuSE VMDP 2.2, and it made >> no difference. >> >> I hope someone could point me how to pass through and make the Intel >> AC 7265 adapter working on the Windows HVM. >> >> Thanks a lot. >> >> John Mok >> >> _______________________________________________ >> Xen-users mailing list >> Xen-users@lists.xen.org >> http://lists.xen.org/xen-users >> >> > > Just to confirm, are you certain that the driver in question really does > work when it is running on baremetal or some other virtualization? I.e. this > problem really is Xen related, and not a problem with the driver, OS, or > device itself? > > I'm just guessing here, but does dmesg/journalctl have anything to say on > the Dom0 side? In particular, an error about the driver attempting to write > to read-only configuration space could indicate that you need the > "permissive=1" flag. See > http://wiki.xenproject.org/wiki/Xen_PCI_Passthrough#PV_guests_and_PCI_quirks > > > ------------------------------------------------- > > ONLY AT VFEmail! - Use our Metadata Mitigator to keep your email out of the > NSA's hands! > $24.95 ONETIME Lifetime accounts with Privacy Features! 15GB disk! No > bandwidth quotas! > Commercial and Bulk Mail Options! _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Fri Jan 01 10:49:41 2016 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 01 Jan 2016 10:49: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 1aExG2-0006un-IK; Fri, 01 Jan 2016 10:48:30 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1aExG0-0006ui-Uj for xen-users@lists.xen.org; Fri, 01 Jan 2016 10:48:29 +0000 Received: from [193.109.254.147] by server-5.bemta-14.messagelabs.com id 18/13-00475-C7956865; Fri, 01 Jan 2016 10:48:28 +0000 X-Env-Sender: a9121431@gmail.com X-Msg-Ref: server-11.tower-27.messagelabs.com!1451645306!14130648!1 X-Originating-IP: [209.85.218.65] X-SpamReason: No, hits=0.6 required=7.0 tests=MAILTO_TO_SPAM_ADDR, RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 7.35.1; banners=-,-,- X-VirusChecked: Checked Received: (qmail 58420 invoked from network); 1 Jan 2016 10:48:27 -0000 Received: from mail-oi0-f65.google.com (HELO mail-oi0-f65.google.com) (209.85.218.65) by server-11.tower-27.messagelabs.com with AES128-GCM-SHA256 encrypted SMTP; 1 Jan 2016 10:48:27 -0000 Received: by mail-oi0-f65.google.com with SMTP id o62so20738000oif.1 for ; Fri, 01 Jan 2016 02:48:27 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; bh=d6lfL6so5SJQ5jIZNnAUD2dFpFA0N7LhyLvfYykGzFo=; b=EmX3Hg+9LA2KezBu9SrXGuIFKvU+EoVfbI2w8dZii3qTfb519Rzx6aS+V4mSYz3BTm 55h0hd8vHcAW7rqfeJqgz+8w2EBzFrzVvWTALS7+mlNZy5bDIYR1+w8rjMBvxTu+l98y fySBrTR47EUqiVXrP0S8YlJvzPQ7g/XZ0jVMgRyDgcHZwvFDqDzlCmSWsmdM3wQRQCcl d6Fd91+o3/Y0htD7PKKTOmFDukS5+4byLfXy9kUaDUVhpCclJulew+Vd97D26xhtCf56 NGLZ/XUZXyxxuRXOBo8g5jVk0u9dvuQQFvFkIhBhvI/aDpnTsmdciTaWmf0qRp6YKCmI BFng== MIME-Version: 1.0 X-Received: by 10.202.85.194 with SMTP id j185mr47532588oib.107.1451645305752; Fri, 01 Jan 2016 02:48:25 -0800 (PST) Received: by 10.182.153.233 with HTTP; Fri, 1 Jan 2016 02:48:25 -0800 (PST) In-Reply-To: <20151230160147.88486qsc1m9vm1kw@vfemail.net> References: <20151230160147.88486qsc1m9vm1kw@vfemail.net> Date: Fri, 1 Jan 2016 18:48:25 +0800 Message-ID: From: John Mok To: "xen-users@lists.xen.org" Subject: Re: [Xen-users] PCI Passthrough of iwlwifi adapter into Windows HVM failed to start X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org >Just to confirm, are you certain that the driver in question really does work when it is running on baremetal ....? Yes, the driver works on baremetal, but not try on other virtualization passthrough. >I'm just guessing here, but does dmesg/journalctl have anything to say on the Dom0 side? In particular, an error about the driver >attempting to write to read-only configuration space could indicate that you need the "permissive=1" flag. See http://wiki.xenproject.org/wiki/Xen_PCI_Passthrough#PV_guests_and_PCI_quirks I do not see anything complaining driver failing to write to read-only configuration space. But somehow the Windows 7 HVM guest could not bring up the Intel AC 7265 driver with error code 10 (fail to start). As the driver could run on baremetal, it should be a Xen PCI passthrough problem. I hope someone could advise how to solve the problem, or point me to the right direction. Thanks a lot. John Mok On Thu, Dec 31, 2015 at 6:01 AM, wrote: > Quoting "John Mok" : > >> Hi, >> >> I am using Xen 4.4.1 on Debian Jessie on Lenovo ThinkPad X250. >> >> I succeeded to passthrough the Intel AC 7265 adapter to the Windows >> HVM. However, when I installed the Intel driver (with embedded >> firmware), the device failed to start with code 10. >> >> I tried to switch between GPL PV driver and SuSE VMDP 2.2, and it made >> no difference. >> >> I hope someone could point me how to pass through and make the Intel >> AC 7265 adapter working on the Windows HVM. >> >> Thanks a lot. >> >> John Mok >> >> _______________________________________________ >> Xen-users mailing list >> Xen-users@lists.xen.org >> http://lists.xen.org/xen-users >> >> > > Just to confirm, are you certain that the driver in question really does > work when it is running on baremetal or some other virtualization? I.e. this > problem really is Xen related, and not a problem with the driver, OS, or > device itself? > > I'm just guessing here, but does dmesg/journalctl have anything to say on > the Dom0 side? In particular, an error about the driver attempting to write > to read-only configuration space could indicate that you need the > "permissive=1" flag. See > http://wiki.xenproject.org/wiki/Xen_PCI_Passthrough#PV_guests_and_PCI_quirks > > > ------------------------------------------------- > > ONLY AT VFEmail! - Use our Metadata Mitigator to keep your email out of the > NSA's hands! > $24.95 ONETIME Lifetime accounts with Privacy Features! 15GB disk! No > bandwidth quotas! > Commercial and Bulk Mail Options! _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Fri Jan 01 14:23:05 2016 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 01 Jan 2016 14:23: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 1aF0aT-00026j-9S; Fri, 01 Jan 2016 14:21:49 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1aF0aR-00026e-Hn for xen-users@lists.xen.org; Fri, 01 Jan 2016 14:21:47 +0000 Received: from [193.109.254.147] by server-5.bemta-14.messagelabs.com id 5F/1B-00475-A7B86865; Fri, 01 Jan 2016 14:21:46 +0000 X-Env-Sender: zir_blazer@hotmail.com X-Msg-Ref: server-7.tower-27.messagelabs.com!1451658102!14179044!1 X-Originating-IP: [65.55.90.145] X-SpamReason: No, hits=0.7 required=7.0 tests=FORGED_HOTMAIL_RCVD, HTML_40_50,HTML_MESSAGE X-StarScan-Received: X-StarScan-Version: 7.35.1; banners=-,-,- X-VirusChecked: Checked Received: (qmail 22996 invoked from network); 1 Jan 2016 14:21:44 -0000 Received: from snt004-omc3s6.hotmail.com (HELO SNT004-OMC3S6.hotmail.com) (65.55.90.145) by server-7.tower-27.messagelabs.com with AES256-SHA256 encrypted SMTP; 1 Jan 2016 14:21:44 -0000 Received: from SNT151-W70 ([65.55.90.137]) by SNT004-OMC3S6.hotmail.com over TLS secured channel with Microsoft SMTPSVC(7.5.7601.23008); Fri, 1 Jan 2016 06:21:42 -0800 X-TMN: [UEJAJWMEpPAeYfbb6fbv2D9tMespqWOr] X-Originating-Email: [zir_blazer@hotmail.com] Message-ID: From: Zir Blazer To: John Mok , "xen-users@lists.xen.org" Date: Fri, 1 Jan 2016 11:21:42 -0300 Importance: Normal In-Reply-To: References: , <20151230160147.88486qsc1m9vm1kw@vfemail.net>, MIME-Version: 1.0 X-OriginalArrivalTime: 01 Jan 2016 14:21:42.0390 (UTC) FILETIME=[BC86E160:01D1449F] Subject: Re: [Xen-users] PCI Passthrough of iwlwifi adapter into Windows HVM failed to start X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============8831894930968922607==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============8831894930968922607== Content-Type: multipart/alternative; boundary="_fc968c2a-0fd8-4e5a-827b-46410faf044f_" --_fc968c2a-0fd8-4e5a-827b-46410faf044f_ Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable > >> Hi=2C > >> > >> I am using Xen 4.4.1 on Debian Jessie on Lenovo ThinkPad X250. Before doing anything=2C try at least with Xen 4.5+. The 4.4 version had a = PCI Passthrough regression that made it totally broken for some users. Don'= t try too hard to figure out why you can't get it working if you don't test= with other Xen versions (4.3 or 4.5 worked for me=2C 4.4 did not=2C and 4.= 6 I didn't tested)=2C trust me. = --_fc968c2a-0fd8-4e5a-827b-46410faf044f_ Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable


>=3B >=3B>=3B= Hi=2C
>=3B >=3B>=3B
>=3B >=3B>=3B I am using Xen 4.4.1 o= n Debian Jessie on Lenovo ThinkPad X250.

Befor= e doing anything=2C try at least with Xen 4.5+. The 4.4 version had a PCI P= assthrough regression that made it totally broken for some users. Don't try= too hard to figure out why you can't get it working if you don't test with= other Xen versions (4.3 or 4.5 worked for me=2C 4.4 did not=2C and 4.6 I d= idn't tested)=2C trust me.
= --_fc968c2a-0fd8-4e5a-827b-46410faf044f_-- --===============8831894930968922607== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users --===============8831894930968922607==-- From xen-users-bounces@lists.xen.org Fri Jan 01 14:23:05 2016 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 01 Jan 2016 14:23: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 1aF0aT-00026j-9S; Fri, 01 Jan 2016 14:21:49 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1aF0aR-00026e-Hn for xen-users@lists.xen.org; Fri, 01 Jan 2016 14:21:47 +0000 Received: from [193.109.254.147] by server-5.bemta-14.messagelabs.com id 5F/1B-00475-A7B86865; Fri, 01 Jan 2016 14:21:46 +0000 X-Env-Sender: zir_blazer@hotmail.com X-Msg-Ref: server-7.tower-27.messagelabs.com!1451658102!14179044!1 X-Originating-IP: [65.55.90.145] X-SpamReason: No, hits=0.7 required=7.0 tests=FORGED_HOTMAIL_RCVD, HTML_40_50,HTML_MESSAGE X-StarScan-Received: X-StarScan-Version: 7.35.1; banners=-,-,- X-VirusChecked: Checked Received: (qmail 22996 invoked from network); 1 Jan 2016 14:21:44 -0000 Received: from snt004-omc3s6.hotmail.com (HELO SNT004-OMC3S6.hotmail.com) (65.55.90.145) by server-7.tower-27.messagelabs.com with AES256-SHA256 encrypted SMTP; 1 Jan 2016 14:21:44 -0000 Received: from SNT151-W70 ([65.55.90.137]) by SNT004-OMC3S6.hotmail.com over TLS secured channel with Microsoft SMTPSVC(7.5.7601.23008); Fri, 1 Jan 2016 06:21:42 -0800 X-TMN: [UEJAJWMEpPAeYfbb6fbv2D9tMespqWOr] X-Originating-Email: [zir_blazer@hotmail.com] Message-ID: From: Zir Blazer To: John Mok , "xen-users@lists.xen.org" Date: Fri, 1 Jan 2016 11:21:42 -0300 Importance: Normal In-Reply-To: References: , <20151230160147.88486qsc1m9vm1kw@vfemail.net>, MIME-Version: 1.0 X-OriginalArrivalTime: 01 Jan 2016 14:21:42.0390 (UTC) FILETIME=[BC86E160:01D1449F] Subject: Re: [Xen-users] PCI Passthrough of iwlwifi adapter into Windows HVM failed to start X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============8831894930968922607==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============8831894930968922607== Content-Type: multipart/alternative; boundary="_fc968c2a-0fd8-4e5a-827b-46410faf044f_" --_fc968c2a-0fd8-4e5a-827b-46410faf044f_ Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable > >> Hi=2C > >> > >> I am using Xen 4.4.1 on Debian Jessie on Lenovo ThinkPad X250. Before doing anything=2C try at least with Xen 4.5+. The 4.4 version had a = PCI Passthrough regression that made it totally broken for some users. Don'= t try too hard to figure out why you can't get it working if you don't test= with other Xen versions (4.3 or 4.5 worked for me=2C 4.4 did not=2C and 4.= 6 I didn't tested)=2C trust me. = --_fc968c2a-0fd8-4e5a-827b-46410faf044f_ Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable


>=3B >=3B>=3B= Hi=2C
>=3B >=3B>=3B
>=3B >=3B>=3B I am using Xen 4.4.1 o= n Debian Jessie on Lenovo ThinkPad X250.

Befor= e doing anything=2C try at least with Xen 4.5+. The 4.4 version had a PCI P= assthrough regression that made it totally broken for some users. Don't try= too hard to figure out why you can't get it working if you don't test with= other Xen versions (4.3 or 4.5 worked for me=2C 4.4 did not=2C and 4.6 I d= idn't tested)=2C trust me.
= --_fc968c2a-0fd8-4e5a-827b-46410faf044f_-- --===============8831894930968922607== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users --===============8831894930968922607==-- From xen-users-bounces@lists.xen.org Fri Jan 01 15:08:47 2016 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 01 Jan 2016 15:08: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 1aF1JX-000328-Nu; Fri, 01 Jan 2016 15:08:23 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1aF1JW-000323-Da for xen-users@lists.xen.org; Fri, 01 Jan 2016 15:08:22 +0000 Received: from [85.158.137.68] by server-4.bemta-3.messagelabs.com id 4A/96-09570-56696865; Fri, 01 Jan 2016 15:08:21 +0000 X-Env-Sender: sm8ax1@vfemail.net X-Msg-Ref: server-12.tower-31.messagelabs.com!1451660897!13425207!1 X-Originating-IP: [199.16.11.132] X-SpamReason: No, hits=1.2 required=7.0 tests=BODY_RANDOM_LONG, MAILTO_TO_SPAM_ADDR,MIME_QP_LONG_LINE,RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 7.35.1; banners=-,-,- X-VirusChecked: Checked Received: (qmail 59930 invoked from network); 1 Jan 2016 15:08:18 -0000 Received: from onethreetwo.vfemail.net (HELO vfemail.net) (199.16.11.132) by server-12.tower-31.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 1 Jan 2016 15:08:18 -0000 Received: (qmail 4196 invoked by uid 89); 1 Jan 2016 15:08:13 -0000 Received: from localhost (HELO freequeue.vfemail.net) (127.0.0.1) by localhost with (DHE-RSA-AES256-SHA encrypted) SMTP; 1 Jan 2016 15:08:12 -0000 Received: (qmail 83398 invoked by uid 89); 1 Jan 2016 13:36:25 -0000 Received: by simscan 1.3.1 ppid: 83394, pid: 83396, t: 0.0024s scanners:none Received: from unknown (HELO smtp102-2.vfemail.net) (172.16.100.62) by FreeQueue with SMTP; 1 Jan 2016 13:36:25 -0000 Received: (qmail 7772 invoked by uid 89); 1 Jan 2016 13:36:25 -0000 Received: by simscan 1.4.0 ppid: 7765, pid: 7768, t: 0.0345s scanners:none Received: from unknown (HELO localhost) (c204YXgxQHZmZW1haWwubmV0@172.16.100.93) by 172.16.100.62 with ESMTPA; 1 Jan 2016 13:36:25 -0000 Received: from 46.148.18.34 ([46.148.18.34]) by vfemail.net (Horde Framework) with HTTP; Fri, 01 Jan 2016 07:36:25 -0600 Message-ID: <20160101073625.17404r82zk0rl3qc@vfemail.net> Date: Fri, 01 Jan 2016 07:36:25 -0600 From: sm8ax1@vfemail.net To: "John Mok" References: <20151230160147.88486qsc1m9vm1kw@vfemail.net> In-Reply-To: MIME-Version: 1.0 Content-Disposition: inline User-Agent: Internet Messaging Program (IMP) H3 (4.2) X-VFEmail-Originating-IP: 46.148.18.34 X-VFEmail-AntiSpam: Notify admin@vfemail.net of any spam, and include VFEmail headers Cc: "xen-users@lists.xen.org" Subject: Re: [Xen-users] PCI Passthrough of iwlwifi adapter into Windows HVM failed to start X-BeenThere: xen-users@lists.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 Quoting "John Mok" : >> Just to confirm, are you certain that the driver in question really >> does work when it is running on baremetal ....? > > Yes, the driver works on baremetal, but not try on other > virtualization passthrough. > >> I'm just guessing here, but does dmesg/journalctl have anything to >> say on the Dom0 side? In particular, an error about the driver >> >attempting to write to read-only configuration space could >> indicate that you need the "permissive=1" flag. See >> http://wiki.xenproject.org/wiki/Xen_PCI_Passthrough#PV_guests_and_PCI_quirks > > I do not see anything complaining driver failing to write to read-only > configuration space. But somehow the Windows 7 HVM guest could not > bring up the Intel AC 7265 driver with error code 10 (fail to start). > > As the driver could run on baremetal, it should be a Xen PCI > passthrough problem. > > I hope someone could advise how to solve the problem, or point me to > the right direction. > > Thanks a lot. > > John Mok My mistake, the "permissive" flag only applies to PV guests. Once again I'm just guessing, but you could try blacklisting the module (iwlwifi) for the adapter on the Dom0. Make sure `lsmod | grep iwlwifi` outputs something, just to make sure that module isn't built into the kernel, then run `echo blacklist iwlwifi >> /etc/modprobe.d/blacklist` and reboot. Check your distro's documentation for blacklisting modules if that doesn't work. From what I understand, some devices can't be reinitialized (and won't work) by the DomU driver after they've already been initialized on the Dom0. Blacklisting the module should prevent it from being initialized before being passed through to the DomU. If that doesn't work, it's worth reading this page in full: http://wiki.xenproject.org/wiki/Xen_PCI_Passthrough and mentioning your distro, Xen version, and hardware (e.g. whether you have an IOMMU or not). ------------------------------------------------- ONLY AT VFEmail! - Use our Metadata Mitigator to keep your email out of the NSA's hands! $24.95 ONETIME Lifetime accounts with Privacy Features! 15GB disk! No bandwidth quotas! Commercial and Bulk Mail Options! _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Fri Jan 01 15:08:47 2016 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 01 Jan 2016 15:08: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 1aF1JX-000328-Nu; Fri, 01 Jan 2016 15:08:23 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1aF1JW-000323-Da for xen-users@lists.xen.org; Fri, 01 Jan 2016 15:08:22 +0000 Received: from [85.158.137.68] by server-4.bemta-3.messagelabs.com id 4A/96-09570-56696865; Fri, 01 Jan 2016 15:08:21 +0000 X-Env-Sender: sm8ax1@vfemail.net X-Msg-Ref: server-12.tower-31.messagelabs.com!1451660897!13425207!1 X-Originating-IP: [199.16.11.132] X-SpamReason: No, hits=1.2 required=7.0 tests=BODY_RANDOM_LONG, MAILTO_TO_SPAM_ADDR,MIME_QP_LONG_LINE,RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 7.35.1; banners=-,-,- X-VirusChecked: Checked Received: (qmail 59930 invoked from network); 1 Jan 2016 15:08:18 -0000 Received: from onethreetwo.vfemail.net (HELO vfemail.net) (199.16.11.132) by server-12.tower-31.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 1 Jan 2016 15:08:18 -0000 Received: (qmail 4196 invoked by uid 89); 1 Jan 2016 15:08:13 -0000 Received: from localhost (HELO freequeue.vfemail.net) (127.0.0.1) by localhost with (DHE-RSA-AES256-SHA encrypted) SMTP; 1 Jan 2016 15:08:12 -0000 Received: (qmail 83398 invoked by uid 89); 1 Jan 2016 13:36:25 -0000 Received: by simscan 1.3.1 ppid: 83394, pid: 83396, t: 0.0024s scanners:none Received: from unknown (HELO smtp102-2.vfemail.net) (172.16.100.62) by FreeQueue with SMTP; 1 Jan 2016 13:36:25 -0000 Received: (qmail 7772 invoked by uid 89); 1 Jan 2016 13:36:25 -0000 Received: by simscan 1.4.0 ppid: 7765, pid: 7768, t: 0.0345s scanners:none Received: from unknown (HELO localhost) (c204YXgxQHZmZW1haWwubmV0@172.16.100.93) by 172.16.100.62 with ESMTPA; 1 Jan 2016 13:36:25 -0000 Received: from 46.148.18.34 ([46.148.18.34]) by vfemail.net (Horde Framework) with HTTP; Fri, 01 Jan 2016 07:36:25 -0600 Message-ID: <20160101073625.17404r82zk0rl3qc@vfemail.net> Date: Fri, 01 Jan 2016 07:36:25 -0600 From: sm8ax1@vfemail.net To: "John Mok" References: <20151230160147.88486qsc1m9vm1kw@vfemail.net> In-Reply-To: MIME-Version: 1.0 Content-Disposition: inline User-Agent: Internet Messaging Program (IMP) H3 (4.2) X-VFEmail-Originating-IP: 46.148.18.34 X-VFEmail-AntiSpam: Notify admin@vfemail.net of any spam, and include VFEmail headers Cc: "xen-users@lists.xen.org" Subject: Re: [Xen-users] PCI Passthrough of iwlwifi adapter into Windows HVM failed to start X-BeenThere: xen-users@lists.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 Quoting "John Mok" : >> Just to confirm, are you certain that the driver in question really >> does work when it is running on baremetal ....? > > Yes, the driver works on baremetal, but not try on other > virtualization passthrough. > >> I'm just guessing here, but does dmesg/journalctl have anything to >> say on the Dom0 side? In particular, an error about the driver >> >attempting to write to read-only configuration space could >> indicate that you need the "permissive=1" flag. See >> http://wiki.xenproject.org/wiki/Xen_PCI_Passthrough#PV_guests_and_PCI_quirks > > I do not see anything complaining driver failing to write to read-only > configuration space. But somehow the Windows 7 HVM guest could not > bring up the Intel AC 7265 driver with error code 10 (fail to start). > > As the driver could run on baremetal, it should be a Xen PCI > passthrough problem. > > I hope someone could advise how to solve the problem, or point me to > the right direction. > > Thanks a lot. > > John Mok My mistake, the "permissive" flag only applies to PV guests. Once again I'm just guessing, but you could try blacklisting the module (iwlwifi) for the adapter on the Dom0. Make sure `lsmod | grep iwlwifi` outputs something, just to make sure that module isn't built into the kernel, then run `echo blacklist iwlwifi >> /etc/modprobe.d/blacklist` and reboot. Check your distro's documentation for blacklisting modules if that doesn't work. From what I understand, some devices can't be reinitialized (and won't work) by the DomU driver after they've already been initialized on the Dom0. Blacklisting the module should prevent it from being initialized before being passed through to the DomU. If that doesn't work, it's worth reading this page in full: http://wiki.xenproject.org/wiki/Xen_PCI_Passthrough and mentioning your distro, Xen version, and hardware (e.g. whether you have an IOMMU or not). ------------------------------------------------- ONLY AT VFEmail! - Use our Metadata Mitigator to keep your email out of the NSA's hands! $24.95 ONETIME Lifetime accounts with Privacy Features! 15GB disk! No bandwidth quotas! Commercial and Bulk Mail Options! _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Sun Jan 03 00:46:30 2016 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sun, 03 Jan 2016 00:46: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 1aFWnP-0000ww-CJ; Sun, 03 Jan 2016 00:45:19 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1aFWnN-0000wr-Nd for xen-users@lists.xen.org; Sun, 03 Jan 2016 00:45:17 +0000 Received: from [85.158.139.211] by server-13.bemta-5.messagelabs.com id 9F/9A-06091-C1F68865; Sun, 03 Jan 2016 00:45:16 +0000 X-Env-Sender: ray@aarden.us X-Msg-Ref: server-7.tower-206.messagelabs.com!1451781912!13363897!1 X-Originating-IP: [173.201.193.235] X-SpamReason: No, hits=0.7 required=7.0 tests=sa_preprocessor: QmFkIElQOiAxNzMuMjAxLjE5My4yMzUgPT4gNDE0NzM=\n,sa_preprocessor: QmFkIElQOiAxNzMuMjAxLjE5My4yMzUgPT4gNDE0NzM=\n,FORGED_HOTMAIL_RCVD, HTML_40_50,HTML_MESSAGE X-StarScan-Received: X-StarScan-Version: 7.35.1; banners=-,-,- X-VirusChecked: Checked Received: (qmail 54819 invoked from network); 3 Jan 2016 00:45:14 -0000 Received: from p3plsmtpa09-06.prod.phx3.secureserver.net (HELO p3plsmtpa09-06.prod.phx3.secureserver.net) (173.201.193.235) by server-7.tower-206.messagelabs.com with DHE-RSA-AES128-SHA encrypted SMTP; 3 Jan 2016 00:45:14 -0000 Received: from mail.hotmail.com ([157.56.23.13]) by p3plsmtpa09-06.prod.phx3.secureserver.net with id 1ClC1s0010Gwn7901ClCGx; Sat, 02 Jan 2016 17:45:12 -0700 Received: from COL128-W93 ([157.56.23.7]) by COL004-WSS1S6.hotmail.com over TLS secured channel with Microsoft SMTPSVC(7.5.7601.23008); Sat, 2 Jan 2016 16:45:11 -0800 X-TMN: [M2Xa/qVfxuBydvFf5CcR2p//USzXQauC] Message-ID: From: Ray To: "xen-users@lists.xen.org" Date: Sat, 2 Jan 2016 18:45:10 -0600 Importance: Normal MIME-Version: 1.0 X-OriginalArrivalTime: 03 Jan 2016 00:45:11.0573 (UTC) FILETIME=[008CF450:01D145C0] Subject: [Xen-users] PV Install Errors "No CDROM" X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============5639358428976026075==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============5639358428976026075== Content-Type: multipart/alternative; boundary="_986af3bd-dacd-4777-b7d5-ce203c91358c_" --_986af3bd-dacd-4777-b7d5-ce203c91358c_ Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable I would like to install a PV guest but get a failure about detecting a CDRO= M. The steps taken are: 1. Import existing disk image=2C xen (paravirt). 2. Storage path /home/user3/Downloads/debian-8.2.0-amd64-CD-1.iso=2C (copi= ed from http://cdimage.debian.org/debian-cd/8.2.0/amd64/iso-cd/)=2C OS type= "Linux"=2C Version "Debian Wheezy (or later). 3. Memory 1 GB=2C CPUs "1". 4. Advanced options: "Virtual network (default)=2C Fixed MAC address. =20 Virtual Machine Manager (It does not report a version) During=0A= installation at "Detect and mount CD-ROM"=2C it reports "No common CD-ROM= =0A= drive was detected" and then asks about loading CD-ROM drivers from =0A= removable media. Both "Yes" and "No" fail as there is no CD-ROM drive =0A= on this laptop. =20 release : 3.16.0-4-amd64 version : #1 SMP Debian 3.16.7-ckt11-1+deb8u5 (2015-10-09) machine : x86_64 xen_version : 4.4.1 xen_caps : xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32 hvm-= 3.0-x86_32p hvm-3.0-x86_64=20 What might I do to resolve this? Thanks in advance=2C Ray = --_986af3bd-dacd-4777-b7d5-ce203c91358c_ Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
I would like to install a PV gue= st but get a failure about detecting a CDROM.

The steps taken are:1. =3B Import existing disk image=2C xen (paravirt).
2. =3B St= orage path /home/user3/Downloads/debian-8.2.0-amd64-CD-1.iso=2C (copied fro= m http://cdimage.debian.org/debian-cd/8.2.0/am= d64/iso-cd/)=2C OS type "Linux"=2C Version "Debian Wheezy (or later).3. =3B Memory 1 GB=2C CPUs "1".
4. =3B Advanced options: = =3B "Virtual network (default)=2C Fixed MAC address. =3B


Vi= rtual Machine Manager (It does not report a version)
During=0A= installation at "Detect and mount CD-ROM"=2C it reports "No common CD-ROM= =0A= drive was detected" and then asks about loading CD-ROM drivers from =0A= removable media. =3B Both "Yes" and "No" fail as there is no CD-ROM dri= ve =0A= on this laptop. =3B

release =3B =3B =3B =3B&nbs= p=3B =3B =3B =3B =3B =3B =3B =3B =3B = =3B =3B : 3.16.0-4-amd64
version =3B =3B =3B =3B&nbs= p=3B =3B =3B =3B =3B =3B =3B =3B =3B = =3B =3B : #1 SMP Debian 3.16.7-ckt11-1+deb8u5 (2015-10-09)
machine&n= bsp=3B =3B =3B =3B =3B =3B =3B =3B =3B = =3B =3B =3B =3B =3B =3B : x86_64
xen_version =3B=  =3B =3B =3B =3B =3B =3B =3B =3B =3B&nb= sp=3B : 4.4.1
xen_caps =3B =3B =3B =3B =3B =3B&n= bsp=3B =3B =3B =3B =3B =3B =3B =3B : xen-3.0-x8= 6_64 xen-3.0-x86_32p hvm-3.0-x86_32 hvm-3.0-x86_32p hvm-3.0-x86_64

= What might I do to resolve this?

Thanks in advance=2C
Ray
= --_986af3bd-dacd-4777-b7d5-ce203c91358c_-- --===============5639358428976026075== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users --===============5639358428976026075==-- From xen-users-bounces@lists.xen.org Sun Jan 03 00:46:30 2016 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sun, 03 Jan 2016 00:46: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 1aFWnP-0000ww-CJ; Sun, 03 Jan 2016 00:45:19 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1aFWnN-0000wr-Nd for xen-users@lists.xen.org; Sun, 03 Jan 2016 00:45:17 +0000 Received: from [85.158.139.211] by server-13.bemta-5.messagelabs.com id 9F/9A-06091-C1F68865; Sun, 03 Jan 2016 00:45:16 +0000 X-Env-Sender: ray@aarden.us X-Msg-Ref: server-7.tower-206.messagelabs.com!1451781912!13363897!1 X-Originating-IP: [173.201.193.235] X-SpamReason: No, hits=0.7 required=7.0 tests=sa_preprocessor: QmFkIElQOiAxNzMuMjAxLjE5My4yMzUgPT4gNDE0NzM=\n,sa_preprocessor: QmFkIElQOiAxNzMuMjAxLjE5My4yMzUgPT4gNDE0NzM=\n,FORGED_HOTMAIL_RCVD, HTML_40_50,HTML_MESSAGE X-StarScan-Received: X-StarScan-Version: 7.35.1; banners=-,-,- X-VirusChecked: Checked Received: (qmail 54819 invoked from network); 3 Jan 2016 00:45:14 -0000 Received: from p3plsmtpa09-06.prod.phx3.secureserver.net (HELO p3plsmtpa09-06.prod.phx3.secureserver.net) (173.201.193.235) by server-7.tower-206.messagelabs.com with DHE-RSA-AES128-SHA encrypted SMTP; 3 Jan 2016 00:45:14 -0000 Received: from mail.hotmail.com ([157.56.23.13]) by p3plsmtpa09-06.prod.phx3.secureserver.net with id 1ClC1s0010Gwn7901ClCGx; Sat, 02 Jan 2016 17:45:12 -0700 Received: from COL128-W93 ([157.56.23.7]) by COL004-WSS1S6.hotmail.com over TLS secured channel with Microsoft SMTPSVC(7.5.7601.23008); Sat, 2 Jan 2016 16:45:11 -0800 X-TMN: [M2Xa/qVfxuBydvFf5CcR2p//USzXQauC] Message-ID: From: Ray To: "xen-users@lists.xen.org" Date: Sat, 2 Jan 2016 18:45:10 -0600 Importance: Normal MIME-Version: 1.0 X-OriginalArrivalTime: 03 Jan 2016 00:45:11.0573 (UTC) FILETIME=[008CF450:01D145C0] Subject: [Xen-users] PV Install Errors "No CDROM" X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============5639358428976026075==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============5639358428976026075== Content-Type: multipart/alternative; boundary="_986af3bd-dacd-4777-b7d5-ce203c91358c_" --_986af3bd-dacd-4777-b7d5-ce203c91358c_ Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable I would like to install a PV guest but get a failure about detecting a CDRO= M. The steps taken are: 1. Import existing disk image=2C xen (paravirt). 2. Storage path /home/user3/Downloads/debian-8.2.0-amd64-CD-1.iso=2C (copi= ed from http://cdimage.debian.org/debian-cd/8.2.0/amd64/iso-cd/)=2C OS type= "Linux"=2C Version "Debian Wheezy (or later). 3. Memory 1 GB=2C CPUs "1". 4. Advanced options: "Virtual network (default)=2C Fixed MAC address. =20 Virtual Machine Manager (It does not report a version) During=0A= installation at "Detect and mount CD-ROM"=2C it reports "No common CD-ROM= =0A= drive was detected" and then asks about loading CD-ROM drivers from =0A= removable media. Both "Yes" and "No" fail as there is no CD-ROM drive =0A= on this laptop. =20 release : 3.16.0-4-amd64 version : #1 SMP Debian 3.16.7-ckt11-1+deb8u5 (2015-10-09) machine : x86_64 xen_version : 4.4.1 xen_caps : xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32 hvm-= 3.0-x86_32p hvm-3.0-x86_64=20 What might I do to resolve this? Thanks in advance=2C Ray = --_986af3bd-dacd-4777-b7d5-ce203c91358c_ Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
I would like to install a PV gue= st but get a failure about detecting a CDROM.

The steps taken are:1. =3B Import existing disk image=2C xen (paravirt).
2. =3B St= orage path /home/user3/Downloads/debian-8.2.0-amd64-CD-1.iso=2C (copied fro= m http://cdimage.debian.org/debian-cd/8.2.0/am= d64/iso-cd/)=2C OS type "Linux"=2C Version "Debian Wheezy (or later).3. =3B Memory 1 GB=2C CPUs "1".
4. =3B Advanced options: = =3B "Virtual network (default)=2C Fixed MAC address. =3B


Vi= rtual Machine Manager (It does not report a version)
During=0A= installation at "Detect and mount CD-ROM"=2C it reports "No common CD-ROM= =0A= drive was detected" and then asks about loading CD-ROM drivers from =0A= removable media. =3B Both "Yes" and "No" fail as there is no CD-ROM dri= ve =0A= on this laptop. =3B

release =3B =3B =3B =3B&nbs= p=3B =3B =3B =3B =3B =3B =3B =3B =3B = =3B =3B : 3.16.0-4-amd64
version =3B =3B =3B =3B&nbs= p=3B =3B =3B =3B =3B =3B =3B =3B =3B = =3B =3B : #1 SMP Debian 3.16.7-ckt11-1+deb8u5 (2015-10-09)
machine&n= bsp=3B =3B =3B =3B =3B =3B =3B =3B =3B = =3B =3B =3B =3B =3B =3B : x86_64
xen_version =3B=  =3B =3B =3B =3B =3B =3B =3B =3B =3B&nb= sp=3B : 4.4.1
xen_caps =3B =3B =3B =3B =3B =3B&n= bsp=3B =3B =3B =3B =3B =3B =3B =3B : xen-3.0-x8= 6_64 xen-3.0-x86_32p hvm-3.0-x86_32 hvm-3.0-x86_32p hvm-3.0-x86_64

= What might I do to resolve this?

Thanks in advance=2C
Ray
= --_986af3bd-dacd-4777-b7d5-ce203c91358c_-- --===============5639358428976026075== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users --===============5639358428976026075==-- From xen-users-bounces@lists.xen.org Sun Jan 03 16:37:13 2016 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sun, 03 Jan 2016 16:37: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 1aFld8-00061I-Ru; Sun, 03 Jan 2016 16:35:42 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1aFld6-00061D-Sd for xen-users@lists.xen.org; Sun, 03 Jan 2016 16:35:41 +0000 Received: from [85.158.139.211] by server-6.bemta-5.messagelabs.com id E6/44-22089-CDD49865; Sun, 03 Jan 2016 16:35:40 +0000 X-Env-Sender: ray@aarden.us X-Msg-Ref: server-14.tower-206.messagelabs.com!1451838935!13356989!1 X-Originating-IP: [173.201.192.231] X-SpamReason: No, hits=0.4 required=7.0 tests=sa_preprocessor: QmFkIElQOiAxNzMuMjAxLjE5Mi4yMzEgPT4gMTE4NDgx\n,sa_preprocessor: QmFkIElQOiAxNzMuMjAxLjE5Mi4yMzEgPT4gMTE4NDgx\n,FORGED_HOTMAIL_RCVD, HTML_60_70,HTML_MESSAGE X-StarScan-Received: X-StarScan-Version: 7.35.1; banners=-,-,- X-VirusChecked: Checked Received: (qmail 50566 invoked from network); 3 Jan 2016 16:35:37 -0000 Received: from p3plsmtpa07-02.prod.phx3.secureserver.net (HELO p3plsmtpa07-02.prod.phx3.secureserver.net) (173.201.192.231) by server-14.tower-206.messagelabs.com with DHE-RSA-AES128-SHA encrypted SMTP; 3 Jan 2016 16:35:37 -0000 Received: from mail.hotmail.com ([157.56.23.8]) by p3plsmtpa07-02.prod.phx3.secureserver.net with id 1Uba1s0040AURRp01UbaqL; Sun, 03 Jan 2016 09:35:35 -0700 Received: from COL128-W37 ([157.56.23.7]) by COL004-WSS1S1.hotmail.com over TLS secured channel with Microsoft SMTPSVC(7.5.7601.23008); Sun, 3 Jan 2016 08:35:34 -0800 X-TMN: [XwvEO7OkIL38FB5zVl0spu4EmMckIuh3] Message-ID: From: Ray To: "xen-users@lists.xen.org" Date: Sun, 3 Jan 2016 10:35:33 -0600 Importance: Normal In-Reply-To: References: MIME-Version: 1.0 X-OriginalArrivalTime: 03 Jan 2016 16:35:34.0452 (UTC) FILETIME=[C4D5C740:01D14644] Subject: [Xen-users] PV Install Errors "No CDROM" X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============8216317762399225130==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============8216317762399225130== Content-Type: multipart/alternative; boundary="_29094481-159c-415a-af64-68e553d808c1_" --_29094481-159c-415a-af64-68e553d808c1_ Content-Type: text/plain; charset="koi8-r" Content-Transfer-Encoding: quoted-printable > Subject: [Xen-users] PV Install Errors "No CDROM" > Message-ID: >=20 > I would like to install a PV guest but get a failure about detecting a CD= ROM. >=20 > The steps taken are: > 1. Import existing disk image=2C xen (paravirt). > 2. Storage path /home/user3/Downloads/debian-8.2.0-amd64-CD-1.iso=2C (co= pied from http://cdimage.debian.org/debian-cd/8.2.0/amd64/iso-cd/)=2C OS ty= pe "Linux"=2C Version "Debian Wheezy (or later). > 3. Memory 1 GB=2C CPUs "1". > 4. Advanced options: "Virtual network (default)=2C Fixed MAC address. = =20 >=20 >=20 > Virtual Machine Manager (It does not report a version) > During > installation at "Detect and mount CD-ROM"=2C it reports "No common CD-RO= M > drive was detected" and then asks about loading CD-ROM drivers from=20 > removable media. Both "Yes" and "No" fail as there is no CD-ROM drive=20 > on this laptop. =20 >=20 > release : 3.16.0-4-amd64 > version : #1 SMP Debian 3.16.7-ckt11-1+deb8u5 (2015-10-09) > machine : x86_64 > xen_version : 4.4.1 > xen_caps : xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32 hv= m-3.0-x86_32p hvm-3.0-x86_64=20 >=20 > What might I do to resolve this? >=20 > Thanks in advance=2C > Ray > =20 I found two problems with my process. To use the local copy from the above= Debian site=2C the image type must be fullvirt and the source must be loca= l and not CDROM. =20 But it failed at a different point this time. While it was loading additio= nal software I received two error messages: /tmp/O0nBXJSb.iso.part could not be saved=2C because the source file could = not be read. Try again later=2C or contact the server administrator. There is not enough room on the disk to save /tmp/O0nBXJSb.iso.part. Remov= e unnecessary files from the disk and try again=2C or try saving in a diffe= rent location. The 'not enough room' may be coming from my selection of storage space. Th= e default was 8 GB=2C but when I selected it=2C the system complained that = there was only 2.1 GB available. So I change it to 2 GB. The is 1 GB of R= AM set. =20 I have searched for the O0nBXjSB file with no luck so I don't know what can= be increased to achieve more space for the vms. I have created 1 failed v= m via the command line and 3 failed vms via virt machine manager. I do not= know where there are stored or how to remove them to free up the associate= d space. Virtual Machine Manager has a delete function but I don't know th= e scope of it. I used it and found that the selections I made resulted in = deleting the iso I used to install the associated vm (and other vms). =20 Here's: @mymach:~$ df -h Filesystem Size Used Avail Use% Mounted= on /dev/dm-0 8.2G 3.4G 4.3G 45% / udev 10M 0 10M 0% /dev tmpfs 956M 9.4M 947M 1% /run tmpfs 2.4G 14M 2.4G 1% /dev= /shm tmpfs 5.0M 4.0K 5.0M 1% /run= /lock tmpfs 2.4G 0 2.4G 0% /sys= /fs/cgroup /dev/sda1 236M 49M 176M 22% /boot /dev/mapper/xenvg-xenlv 32G 48M 32G 1% /xenfs /dev/mapper/mymach--vg-home 4.8G 1.9G 2.7G 41% /home /dev/mapper/mymach--vg-tmp 360M 2.1M 335M 1% /tmp /dev/mapper/mymach--vg-var 2.7G 1.6G 991M 62% /var tmpfs 478M 4.0K 478M 1% /run= /user/118 tmpfs 478M 20K 478M 1% /run= /user/1003 @mymach:~$ lsblk NAME MAJ:MIN RM SIZE RO TYPE MOU= NTPOINT sda 8:0 0 477G 0 di= sk=20 =86=80sda1 8:1 0 243M 0 = part /boot =86=80sda2 8:2 0 1K 0 = part=20 =86=80sda5 8:5 0 57.9G 0 = part=20 =81 =86=80mymach--vg-root 254:0 0 8.4G 0 lvm / =81 =86=80mymach--vg-var 254:4 0 2.8G 0 lvm /va= r =81 =86=80mymach--vg-swap_1 254:5 0 31.9G 0 lvlsm [SWAP= ] =81 =86=80mymach--vg-tmp 254:6 0 380M 0 lvm /tmp =81 =84=80mymach--vg-home 254:7 0 5G 0 lvm /home =84=80sda6 8:6 0 418.8G 0= part=20 =86=80xenvg-xenlv 254:1 0 32G 0 lvm = /xenfs =86=80xenvg-test01--pv--guest--swap 254:2 0 128M 0 lvm =20 =84=80xenvg-test01--pv--guest--disk 254:3 0 4G 0 lvm =20 How do I make space for the vms? =20 How might I better set-up/manage the disk space on this laptop? Thanks in advance=2C Ray = --_29094481-159c-415a-af64-68e553d808c1_ Content-Type: text/html; charset="koi8-r" Content-Transfer-Encoding: quoted-printable


>=3B Subject: [Xe= n-users] PV Install Errors "No CDROM"
>=3B Message-ID: <=3BCOL128-W9= 3B872733A75B6FCA8DA8AA5F10@phx.gbl>=3B
>=3B
>=3B I would like = to install a PV guest but get a failure about detecting a CDROM.
>=3B =
>=3B The steps taken are:
>=3B 1. Import existing disk image=2C= xen (paravirt).
>=3B 2. Storage path /home/user3/Downloads/debian-8.= 2.0-amd64-CD-1.iso=2C (copied from http://cdimage.debian.org/debian-cd/8.2.= 0/amd64/iso-cd/)=2C OS type "Linux"=2C Version "Debian Wheezy (or later).>=3B 3. Memory 1 GB=2C CPUs "1".
>=3B 4. Advanced options: "Vir= tual network (default)=2C Fixed MAC address.
>=3B
>=3B
>= =3B Virtual Machine Manager (It does not report a version)
>=3B During=
>=3B installation at "Detect and mount CD-ROM"=2C it reports "No com= mon CD-ROM
>=3B drive was detected" and then asks about loading CD-RO= M drivers from
>=3B removable media. Both "Yes" and "No" fail as the= re is no CD-ROM drive
>=3B on this laptop.
>=3B
>=3B rel= ease : 3.16.0-4-amd64
>=3B version : #1 = SMP Debian 3.16.7-ckt11-1+deb8u5 (2015-10-09)
>=3B machine = : x86_64
>=3B xen_version : 4.4.1
>=3B xen_caps = : xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32 hvm-3.0-x86_32p= hvm-3.0-x86_64
>=3B
>=3B What might I do to resolve this?
&= gt=3B
>=3B Thanks in advance=2C
>=3B Ray
>=3B <= br>I found two problems with my process. =3B To use the local copy from= the above Debian site=2C the image type must be fullvirt and the source mu= st be local and not CDROM. =3B

But it failed at a different poi= nt this time. =3B While it was loading additional software I received t= wo error messages:

/tmp/O0nBXJSb.iso.part could not be s= aved=2C because the source file could not be read. =3B Try again later= =2C or contact the server administrator.

There is not enough room on= the disk to save /tmp/O0nBXJSb.iso.part. =3B Remove unnecessary files = from the disk and try again=2C or try saving in a different location.

The 'not enough room' may be coming from my selection of sto= rage space. =3B The default was 8 GB=2C but when I selected it=2C the s= ystem complained that there was only 2.1 GB available. =3B So I change = it to 2 GB. =3B The is 1 GB of RAM set. =3B

I have searched= for the O0nBXjSB file with no luck so I don't know what can be increased t= o achieve more space for the vms. =3B I have created 1 failed vm via th= e command line and 3 failed vms via virt machine manager. =3B I do not = know where there are stored or how to remove them to free up the associated= space. =3B Virtual Machine Manager has a delete function but I don't k= now the scope of it. =3B I used it and found that the selections I made= resulted in deleting the iso I used to install the associated vm (and othe= r vms). =3B

Here's:
@mymach:~$ df -h
Filesystem =3B&n= bsp=3B =3B =3B =3B =3B =3B =3B =3B =3B = =3B =3B =3B =3B =3B =3B =3B =3B =3B =3B=  =3B =3B =3B =3B =3B =3B =3B =3B =3B&nb= sp=3B =3B =3B =3B =3B =3B Size =3B Used Avail Use% = Mounted on
/dev/dm-0 =3B =3B =3B =3B =3B =3B&nbs= p=3B =3B =3B =3B =3B =3B =3B =3B =3B = =3B =3B =3B =3B =3B =3B =3B =3B =3B =3B=  =3B =3B =3B =3B =3B =3B =3B =3B =3B&nb= sp=3B 8.2G =3B 3.4G =3B 4.3G =3B 45% /
udev =3B =3B&= nbsp=3B =3B =3B =3B =3B =3B =3B =3B =3B&nbs= p=3B =3B =3B =3B =3B =3B =3B =3B =3B = =3B =3B =3B =3B =3B =3B =3B =3B =3B =3B=  =3B =3B =3B =3B =3B =3B =3B =3B =3B&nb= sp=3B =3B =3B =3B =3B 10M =3B =3B =3B =3B 0=  =3B =3B 10M =3B =3B 0% /dev
tmpfs =3B =3B = =3B =3B =3B =3B =3B =3B =3B =3B =3B =3B=  =3B =3B =3B =3B =3B =3B =3B =3B =3B&nb= sp=3B =3B =3B =3B =3B =3B =3B =3B =3B = =3B =3B =3B =3B =3B =3B =3B =3B =3B =3B=  =3B 956M =3B 9.4M =3B 947M =3B =3B 1% /run
tmpfs&nb= sp=3B =3B =3B =3B =3B =3B =3B =3B =3B = =3B =3B =3B =3B =3B =3B =3B =3B =3B =3B=  =3B =3B =3B =3B =3B =3B =3B =3B =3B&nb= sp=3B =3B =3B =3B =3B =3B =3B =3B =3B = =3B =3B =3B =3B =3B =3B 2.4G =3B =3B 14M = =3B 2.4G =3B =3B 1% /dev/shm
tmpfs =3B =3B =3B = =3B =3B =3B =3B =3B =3B =3B =3B =3B =3B=  =3B =3B =3B =3B =3B =3B =3B =3B =3B&nb= sp=3B =3B =3B =3B =3B =3B =3B =3B =3B = =3B =3B =3B =3B =3B =3B =3B =3B =3B =3B=  =3B =3B 5.0M =3B 4.0K =3B 5.0M =3B =3B 1% /run/loc= k
tmpfs =3B =3B =3B =3B =3B =3B =3B =3B&= nbsp=3B =3B =3B =3B =3B =3B =3B =3B =3B&nbs= p=3B =3B =3B =3B =3B =3B =3B =3B =3B = =3B =3B =3B =3B =3B =3B =3B =3B =3B =3B=  =3B =3B =3B =3B =3B =3B =3B 2.4G =3B = =3B =3B =3B 0 =3B 2.4G =3B =3B 0% /sys/fs/cgroup
/de= v/sda1 =3B =3B =3B =3B =3B =3B =3B =3B = =3B =3B =3B =3B =3B =3B =3B =3B =3B =3B=  =3B =3B =3B =3B =3B =3B =3B =3B =3B&nb= sp=3B =3B =3B =3B =3B =3B =3B =3B =3B 236M&= nbsp=3B =3B 49M =3B 176M =3B 22% /boot
/dev/mapper/xenvg-xen= lv =3B =3B =3B =3B =3B =3B =3B =3B =3B&= nbsp=3B =3B =3B =3B =3B 32G =3B =3B 48M =3B&nbs= p=3B 32G =3B =3B 1% /xenfs
/dev/mapper/mymach--vg-home =3B&n= bsp=3B 4.8G =3B 1.9G =3B 2.7G =3B 41% /home
/dev/mapper/myma= ch--vg-tmp =3B =3B =3B 360M =3B 2.1M =3B 335M =3B&n= bsp=3B 1% /tmp
/dev/mapper/mymach--vg-var =3B =3B =3B = =3B =3B =3B 2.7G =3B 1.6G =3B 991M =3B 62% /var
tmpf= s =3B =3B =3B =3B =3B =3B =3B =3B =3B&n= bsp=3B =3B =3B =3B =3B =3B =3B =3B =3B = =3B =3B =3B =3B =3B =3B =3B =3B =3B =3B=  =3B =3B =3B =3B =3B =3B =3B =3B =3B&nb= sp=3B =3B =3B =3B =3B =3B 478M =3B 4.0K =3B 478= M =3B =3B 1% /run/user/118
tmpfs =3B =3B =3B =3B=  =3B =3B =3B =3B =3B =3B =3B =3B =3B&nb= sp=3B =3B =3B =3B =3B =3B =3B =3B =3B = =3B =3B =3B =3B =3B =3B =3B =3B =3B =3B=  =3B =3B =3B =3B =3B =3B =3B =3B =3B&nb= sp=3B =3B 478M =3B =3B 20K =3B 478M =3B =3B 1% /run= /user/1003

@mymach:~$ lsblk
NAME =3B =3B =3B =3B&= nbsp=3B =3B =3B =3B =3B =3B =3B =3B =3B&nbs= p=3B =3B =3B =3B =3B =3B =3B =3B =3B = =3B =3B =3B =3B =3B =3B =3B =3B =3B =3B=  =3B =3B =3B =3B =3B =3B =3B =3B =3B MA= J:MIN RM =3B =3B SIZE RO TYPE MOUNTPOINT
sda =3B =3B&nbs= p=3B =3B =3B =3B =3B =3B =3B =3B =3B = =3B =3B =3B =3B =3B =3B =3B =3B =3B =3B=  =3B =3B =3B =3B =3B =3B =3B =3B =3B&nb= sp=3B  =3B  =3B  =3B  =3B  =3B  =3B  =3B  = =3B  =3B =3B 8:0 =3B =3B =3B 0 =3B =3B 477G&nbs= p=3B 0 disk
=86=80sda1 =3B =3B =3B =3B =3B =3B&= nbsp=3B =3B =3B =3B =3B =3B =3B =3B =3B&nbs= p=3B =3B =3B =3B =3B =3B =3B =3B =3B = =3B =3B =3B =3B =3B =3B =3B =3B =3B =3B=  =3B =3B =3B =3B =3B =3B =3B =3B =3B&nb= sp=3B =3B 8:1 =3B =3B =3B 0 =3B =3B 243M =3B 0 = part /boot
=86=80sda2 =3B =3B =3B =3B =3B =3B&nb= sp=3B =3B =3B =3B =3B =3B =3B =3B =3B = =3B =3B =3B =3B =3B =3B =3B =3B =3B =3B=  =3B =3B =3B =3B =3B =3B =3B =3B =3B&nb= sp=3B =3B =3B =3B =3B =3B =3B =3B =3B = =3B =3B 8:2 =3B =3B =3B 0 =3B =3B =3B =3B 1= K =3B 0 part
=86=80sda5 =3B =3B =3B =3B =3B&nbs= p=3B =3B =3B =3B =3B =3B =3B =3B =3B = =3B =3B =3B =3B =3B =3B =3B =3B =3B =3B=  =3B =3B =3B =3B =3B =3B =3B =3B =3B&nb= sp=3B =3B =3B =3B =3B =3B =3B =3B =3B = =3B =3B =3B 8:5 =3B =3B =3B 0 =3B 57.9G =3B 0 p= art
=81 =86=80mymach--vg-root =3B =3B =3B =3B =3B&n= bsp=3B =3B =3B =3B =3B =3B =3B =3B =3B = =3B =3B =3B =3B =3B 254:0 =3B =3B =3B 0 =3B=  =3B 8.4G =3B 0 lvm =3B /
=81 =86=80mymach--vg-var =3B&n= bsp=3B =3B =3B =3B =3B =3B =3B =3B =3B = =3B =3B =3B =3B =3B =3B =3B =3B =3B =3B=  =3B 254:4 =3B =3B =3B 0 =3B =3B 2.8G =3B 0 lvm=  =3B /var
=81 =86=80mymach--vg-swap_1 =3B =3B =3B = =3B =3B =3B =3B =3B =3B =3B =3B =3B =3B=  =3B 254:5 =3B =3B =3B 0 =3B 31.9G =3B 0 lvlsm = =3B [SWAP]
=81 =86=80mymach--vg-tmp =3B =3B =3B =3B = =3B =3B =3B =3B =3B =3B =3B =3B =3B =3B=  =3B =3B =3B =3B =3B =3B 254:6 =3B =3B = =3B 0 =3B =3B 380M =3B 0 lvm =3B /tmp
=81 =84=80mymach--= vg-home =3B =3B =3B =3B =3B =3B =3B =3B&nbs= p=3B =3B =3B =3B =3B =3B =3B =3B =3B 254:7&= nbsp=3B =3B =3B 0 =3B =3B =3B =3B 5G =3B 0 lvm&= nbsp=3B /home
=84=80sda6 =3B =3B =3B =3B =3B =3B=  =3B =3B =3B =3B =3B =3B =3B =3B =3B&nb= sp=3B =3B =3B =3B =3B =3B =3B =3B =3B = =3B =3B =3B =3B =3B =3B =3B =3B =3B =3B=  =3B =3B =3B =3B =3B =3B =3B =3B =3B&nb= sp=3B =3B =3B 8:6 =3B =3B =3B 0 418.8G =3B 0 part <= br> =3B =86=80xenvg-xenlv =3B =3B =3B =3B =3B = =3B =3B =3B =3B =3B =3B =3B =3B =3B =3B=  =3B =3B =3B =3B =3B =3B =3B =3B =3B&nb= sp=3B =3B =3B =3B =3B 254:1 =3B =3B =3B 0 = =3B =3B =3B 32G =3B 0 lvm =3B /xenfs
 =3B =86=80xenv= g-test01--pv--guest--swap 254:2 =3B =3B =3B 0 =3B =3B 1= 28M =3B 0 lvm =3B
 =3B =84=80xenvg-test01--pv--guest--disk&= nbsp=3B =3B 254:3 =3B =3B =3B 0 =3B =3B =3B&nbs= p=3B 4G =3B 0 lvm =3B


How do I make space for the vms?&= nbsp=3B

How might I better set-up/manage the disk space on this lap= top?

Thanks in advance=2C
Ray
= --_29094481-159c-415a-af64-68e553d808c1_-- --===============8216317762399225130== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users --===============8216317762399225130==-- From xen-users-bounces@lists.xen.org Sun Jan 03 16:37:13 2016 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sun, 03 Jan 2016 16:37: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 1aFld8-00061I-Ru; Sun, 03 Jan 2016 16:35:42 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1aFld6-00061D-Sd for xen-users@lists.xen.org; Sun, 03 Jan 2016 16:35:41 +0000 Received: from [85.158.139.211] by server-6.bemta-5.messagelabs.com id E6/44-22089-CDD49865; Sun, 03 Jan 2016 16:35:40 +0000 X-Env-Sender: ray@aarden.us X-Msg-Ref: server-14.tower-206.messagelabs.com!1451838935!13356989!1 X-Originating-IP: [173.201.192.231] X-SpamReason: No, hits=0.4 required=7.0 tests=sa_preprocessor: QmFkIElQOiAxNzMuMjAxLjE5Mi4yMzEgPT4gMTE4NDgx\n,sa_preprocessor: QmFkIElQOiAxNzMuMjAxLjE5Mi4yMzEgPT4gMTE4NDgx\n,FORGED_HOTMAIL_RCVD, HTML_60_70,HTML_MESSAGE X-StarScan-Received: X-StarScan-Version: 7.35.1; banners=-,-,- X-VirusChecked: Checked Received: (qmail 50566 invoked from network); 3 Jan 2016 16:35:37 -0000 Received: from p3plsmtpa07-02.prod.phx3.secureserver.net (HELO p3plsmtpa07-02.prod.phx3.secureserver.net) (173.201.192.231) by server-14.tower-206.messagelabs.com with DHE-RSA-AES128-SHA encrypted SMTP; 3 Jan 2016 16:35:37 -0000 Received: from mail.hotmail.com ([157.56.23.8]) by p3plsmtpa07-02.prod.phx3.secureserver.net with id 1Uba1s0040AURRp01UbaqL; Sun, 03 Jan 2016 09:35:35 -0700 Received: from COL128-W37 ([157.56.23.7]) by COL004-WSS1S1.hotmail.com over TLS secured channel with Microsoft SMTPSVC(7.5.7601.23008); Sun, 3 Jan 2016 08:35:34 -0800 X-TMN: [XwvEO7OkIL38FB5zVl0spu4EmMckIuh3] Message-ID: From: Ray To: "xen-users@lists.xen.org" Date: Sun, 3 Jan 2016 10:35:33 -0600 Importance: Normal In-Reply-To: References: MIME-Version: 1.0 X-OriginalArrivalTime: 03 Jan 2016 16:35:34.0452 (UTC) FILETIME=[C4D5C740:01D14644] Subject: [Xen-users] PV Install Errors "No CDROM" X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============8216317762399225130==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============8216317762399225130== Content-Type: multipart/alternative; boundary="_29094481-159c-415a-af64-68e553d808c1_" --_29094481-159c-415a-af64-68e553d808c1_ Content-Type: text/plain; charset="koi8-r" Content-Transfer-Encoding: quoted-printable > Subject: [Xen-users] PV Install Errors "No CDROM" > Message-ID: >=20 > I would like to install a PV guest but get a failure about detecting a CD= ROM. >=20 > The steps taken are: > 1. Import existing disk image=2C xen (paravirt). > 2. Storage path /home/user3/Downloads/debian-8.2.0-amd64-CD-1.iso=2C (co= pied from http://cdimage.debian.org/debian-cd/8.2.0/amd64/iso-cd/)=2C OS ty= pe "Linux"=2C Version "Debian Wheezy (or later). > 3. Memory 1 GB=2C CPUs "1". > 4. Advanced options: "Virtual network (default)=2C Fixed MAC address. = =20 >=20 >=20 > Virtual Machine Manager (It does not report a version) > During > installation at "Detect and mount CD-ROM"=2C it reports "No common CD-RO= M > drive was detected" and then asks about loading CD-ROM drivers from=20 > removable media. Both "Yes" and "No" fail as there is no CD-ROM drive=20 > on this laptop. =20 >=20 > release : 3.16.0-4-amd64 > version : #1 SMP Debian 3.16.7-ckt11-1+deb8u5 (2015-10-09) > machine : x86_64 > xen_version : 4.4.1 > xen_caps : xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32 hv= m-3.0-x86_32p hvm-3.0-x86_64=20 >=20 > What might I do to resolve this? >=20 > Thanks in advance=2C > Ray > =20 I found two problems with my process. To use the local copy from the above= Debian site=2C the image type must be fullvirt and the source must be loca= l and not CDROM. =20 But it failed at a different point this time. While it was loading additio= nal software I received two error messages: /tmp/O0nBXJSb.iso.part could not be saved=2C because the source file could = not be read. Try again later=2C or contact the server administrator. There is not enough room on the disk to save /tmp/O0nBXJSb.iso.part. Remov= e unnecessary files from the disk and try again=2C or try saving in a diffe= rent location. The 'not enough room' may be coming from my selection of storage space. Th= e default was 8 GB=2C but when I selected it=2C the system complained that = there was only 2.1 GB available. So I change it to 2 GB. The is 1 GB of R= AM set. =20 I have searched for the O0nBXjSB file with no luck so I don't know what can= be increased to achieve more space for the vms. I have created 1 failed v= m via the command line and 3 failed vms via virt machine manager. I do not= know where there are stored or how to remove them to free up the associate= d space. Virtual Machine Manager has a delete function but I don't know th= e scope of it. I used it and found that the selections I made resulted in = deleting the iso I used to install the associated vm (and other vms). =20 Here's: @mymach:~$ df -h Filesystem Size Used Avail Use% Mounted= on /dev/dm-0 8.2G 3.4G 4.3G 45% / udev 10M 0 10M 0% /dev tmpfs 956M 9.4M 947M 1% /run tmpfs 2.4G 14M 2.4G 1% /dev= /shm tmpfs 5.0M 4.0K 5.0M 1% /run= /lock tmpfs 2.4G 0 2.4G 0% /sys= /fs/cgroup /dev/sda1 236M 49M 176M 22% /boot /dev/mapper/xenvg-xenlv 32G 48M 32G 1% /xenfs /dev/mapper/mymach--vg-home 4.8G 1.9G 2.7G 41% /home /dev/mapper/mymach--vg-tmp 360M 2.1M 335M 1% /tmp /dev/mapper/mymach--vg-var 2.7G 1.6G 991M 62% /var tmpfs 478M 4.0K 478M 1% /run= /user/118 tmpfs 478M 20K 478M 1% /run= /user/1003 @mymach:~$ lsblk NAME MAJ:MIN RM SIZE RO TYPE MOU= NTPOINT sda 8:0 0 477G 0 di= sk=20 =86=80sda1 8:1 0 243M 0 = part /boot =86=80sda2 8:2 0 1K 0 = part=20 =86=80sda5 8:5 0 57.9G 0 = part=20 =81 =86=80mymach--vg-root 254:0 0 8.4G 0 lvm / =81 =86=80mymach--vg-var 254:4 0 2.8G 0 lvm /va= r =81 =86=80mymach--vg-swap_1 254:5 0 31.9G 0 lvlsm [SWAP= ] =81 =86=80mymach--vg-tmp 254:6 0 380M 0 lvm /tmp =81 =84=80mymach--vg-home 254:7 0 5G 0 lvm /home =84=80sda6 8:6 0 418.8G 0= part=20 =86=80xenvg-xenlv 254:1 0 32G 0 lvm = /xenfs =86=80xenvg-test01--pv--guest--swap 254:2 0 128M 0 lvm =20 =84=80xenvg-test01--pv--guest--disk 254:3 0 4G 0 lvm =20 How do I make space for the vms? =20 How might I better set-up/manage the disk space on this laptop? Thanks in advance=2C Ray = --_29094481-159c-415a-af64-68e553d808c1_ Content-Type: text/html; charset="koi8-r" Content-Transfer-Encoding: quoted-printable


>=3B Subject: [Xe= n-users] PV Install Errors "No CDROM"
>=3B Message-ID: <=3BCOL128-W9= 3B872733A75B6FCA8DA8AA5F10@phx.gbl>=3B
>=3B
>=3B I would like = to install a PV guest but get a failure about detecting a CDROM.
>=3B =
>=3B The steps taken are:
>=3B 1. Import existing disk image=2C= xen (paravirt).
>=3B 2. Storage path /home/user3/Downloads/debian-8.= 2.0-amd64-CD-1.iso=2C (copied from http://cdimage.debian.org/debian-cd/8.2.= 0/amd64/iso-cd/)=2C OS type "Linux"=2C Version "Debian Wheezy (or later).>=3B 3. Memory 1 GB=2C CPUs "1".
>=3B 4. Advanced options: "Vir= tual network (default)=2C Fixed MAC address.
>=3B
>=3B
>= =3B Virtual Machine Manager (It does not report a version)
>=3B During=
>=3B installation at "Detect and mount CD-ROM"=2C it reports "No com= mon CD-ROM
>=3B drive was detected" and then asks about loading CD-RO= M drivers from
>=3B removable media. Both "Yes" and "No" fail as the= re is no CD-ROM drive
>=3B on this laptop.
>=3B
>=3B rel= ease : 3.16.0-4-amd64
>=3B version : #1 = SMP Debian 3.16.7-ckt11-1+deb8u5 (2015-10-09)
>=3B machine = : x86_64
>=3B xen_version : 4.4.1
>=3B xen_caps = : xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32 hvm-3.0-x86_32p= hvm-3.0-x86_64
>=3B
>=3B What might I do to resolve this?
&= gt=3B
>=3B Thanks in advance=2C
>=3B Ray
>=3B <= br>I found two problems with my process. =3B To use the local copy from= the above Debian site=2C the image type must be fullvirt and the source mu= st be local and not CDROM. =3B

But it failed at a different poi= nt this time. =3B While it was loading additional software I received t= wo error messages:

/tmp/O0nBXJSb.iso.part could not be s= aved=2C because the source file could not be read. =3B Try again later= =2C or contact the server administrator.

There is not enough room on= the disk to save /tmp/O0nBXJSb.iso.part. =3B Remove unnecessary files = from the disk and try again=2C or try saving in a different location.

The 'not enough room' may be coming from my selection of sto= rage space. =3B The default was 8 GB=2C but when I selected it=2C the s= ystem complained that there was only 2.1 GB available. =3B So I change = it to 2 GB. =3B The is 1 GB of RAM set. =3B

I have searched= for the O0nBXjSB file with no luck so I don't know what can be increased t= o achieve more space for the vms. =3B I have created 1 failed vm via th= e command line and 3 failed vms via virt machine manager. =3B I do not = know where there are stored or how to remove them to free up the associated= space. =3B Virtual Machine Manager has a delete function but I don't k= now the scope of it. =3B I used it and found that the selections I made= resulted in deleting the iso I used to install the associated vm (and othe= r vms). =3B

Here's:
@mymach:~$ df -h
Filesystem =3B&n= bsp=3B =3B =3B =3B =3B =3B =3B =3B =3B = =3B =3B =3B =3B =3B =3B =3B =3B =3B =3B=  =3B =3B =3B =3B =3B =3B =3B =3B =3B&nb= sp=3B =3B =3B =3B =3B =3B Size =3B Used Avail Use% = Mounted on
/dev/dm-0 =3B =3B =3B =3B =3B =3B&nbs= p=3B =3B =3B =3B =3B =3B =3B =3B =3B = =3B =3B =3B =3B =3B =3B =3B =3B =3B =3B=  =3B =3B =3B =3B =3B =3B =3B =3B =3B&nb= sp=3B 8.2G =3B 3.4G =3B 4.3G =3B 45% /
udev =3B =3B&= nbsp=3B =3B =3B =3B =3B =3B =3B =3B =3B&nbs= p=3B =3B =3B =3B =3B =3B =3B =3B =3B = =3B =3B =3B =3B =3B =3B =3B =3B =3B =3B=  =3B =3B =3B =3B =3B =3B =3B =3B =3B&nb= sp=3B =3B =3B =3B =3B 10M =3B =3B =3B =3B 0=  =3B =3B 10M =3B =3B 0% /dev
tmpfs =3B =3B = =3B =3B =3B =3B =3B =3B =3B =3B =3B =3B=  =3B =3B =3B =3B =3B =3B =3B =3B =3B&nb= sp=3B =3B =3B =3B =3B =3B =3B =3B =3B = =3B =3B =3B =3B =3B =3B =3B =3B =3B =3B=  =3B 956M =3B 9.4M =3B 947M =3B =3B 1% /run
tmpfs&nb= sp=3B =3B =3B =3B =3B =3B =3B =3B =3B = =3B =3B =3B =3B =3B =3B =3B =3B =3B =3B=  =3B =3B =3B =3B =3B =3B =3B =3B =3B&nb= sp=3B =3B =3B =3B =3B =3B =3B =3B =3B = =3B =3B =3B =3B =3B =3B 2.4G =3B =3B 14M = =3B 2.4G =3B =3B 1% /dev/shm
tmpfs =3B =3B =3B = =3B =3B =3B =3B =3B =3B =3B =3B =3B =3B=  =3B =3B =3B =3B =3B =3B =3B =3B =3B&nb= sp=3B =3B =3B =3B =3B =3B =3B =3B =3B = =3B =3B =3B =3B =3B =3B =3B =3B =3B =3B=  =3B =3B 5.0M =3B 4.0K =3B 5.0M =3B =3B 1% /run/loc= k
tmpfs =3B =3B =3B =3B =3B =3B =3B =3B&= nbsp=3B =3B =3B =3B =3B =3B =3B =3B =3B&nbs= p=3B =3B =3B =3B =3B =3B =3B =3B =3B = =3B =3B =3B =3B =3B =3B =3B =3B =3B =3B=  =3B =3B =3B =3B =3B =3B =3B 2.4G =3B = =3B =3B =3B 0 =3B 2.4G =3B =3B 0% /sys/fs/cgroup
/de= v/sda1 =3B =3B =3B =3B =3B =3B =3B =3B = =3B =3B =3B =3B =3B =3B =3B =3B =3B =3B=  =3B =3B =3B =3B =3B =3B =3B =3B =3B&nb= sp=3B =3B =3B =3B =3B =3B =3B =3B =3B 236M&= nbsp=3B =3B 49M =3B 176M =3B 22% /boot
/dev/mapper/xenvg-xen= lv =3B =3B =3B =3B =3B =3B =3B =3B =3B&= nbsp=3B =3B =3B =3B =3B 32G =3B =3B 48M =3B&nbs= p=3B 32G =3B =3B 1% /xenfs
/dev/mapper/mymach--vg-home =3B&n= bsp=3B 4.8G =3B 1.9G =3B 2.7G =3B 41% /home
/dev/mapper/myma= ch--vg-tmp =3B =3B =3B 360M =3B 2.1M =3B 335M =3B&n= bsp=3B 1% /tmp
/dev/mapper/mymach--vg-var =3B =3B =3B = =3B =3B =3B 2.7G =3B 1.6G =3B 991M =3B 62% /var
tmpf= s =3B =3B =3B =3B =3B =3B =3B =3B =3B&n= bsp=3B =3B =3B =3B =3B =3B =3B =3B =3B = =3B =3B =3B =3B =3B =3B =3B =3B =3B =3B=  =3B =3B =3B =3B =3B =3B =3B =3B =3B&nb= sp=3B =3B =3B =3B =3B =3B 478M =3B 4.0K =3B 478= M =3B =3B 1% /run/user/118
tmpfs =3B =3B =3B =3B=  =3B =3B =3B =3B =3B =3B =3B =3B =3B&nb= sp=3B =3B =3B =3B =3B =3B =3B =3B =3B = =3B =3B =3B =3B =3B =3B =3B =3B =3B =3B=  =3B =3B =3B =3B =3B =3B =3B =3B =3B&nb= sp=3B =3B 478M =3B =3B 20K =3B 478M =3B =3B 1% /run= /user/1003

@mymach:~$ lsblk
NAME =3B =3B =3B =3B&= nbsp=3B =3B =3B =3B =3B =3B =3B =3B =3B&nbs= p=3B =3B =3B =3B =3B =3B =3B =3B =3B = =3B =3B =3B =3B =3B =3B =3B =3B =3B =3B=  =3B =3B =3B =3B =3B =3B =3B =3B =3B MA= J:MIN RM =3B =3B SIZE RO TYPE MOUNTPOINT
sda =3B =3B&nbs= p=3B =3B =3B =3B =3B =3B =3B =3B =3B = =3B =3B =3B =3B =3B =3B =3B =3B =3B =3B=  =3B =3B =3B =3B =3B =3B =3B =3B =3B&nb= sp=3B  =3B  =3B  =3B  =3B  =3B  =3B  =3B  = =3B  =3B =3B 8:0 =3B =3B =3B 0 =3B =3B 477G&nbs= p=3B 0 disk
=86=80sda1 =3B =3B =3B =3B =3B =3B&= nbsp=3B =3B =3B =3B =3B =3B =3B =3B =3B&nbs= p=3B =3B =3B =3B =3B =3B =3B =3B =3B = =3B =3B =3B =3B =3B =3B =3B =3B =3B =3B=  =3B =3B =3B =3B =3B =3B =3B =3B =3B&nb= sp=3B =3B 8:1 =3B =3B =3B 0 =3B =3B 243M =3B 0 = part /boot
=86=80sda2 =3B =3B =3B =3B =3B =3B&nb= sp=3B =3B =3B =3B =3B =3B =3B =3B =3B = =3B =3B =3B =3B =3B =3B =3B =3B =3B =3B=  =3B =3B =3B =3B =3B =3B =3B =3B =3B&nb= sp=3B =3B =3B =3B =3B =3B =3B =3B =3B = =3B =3B 8:2 =3B =3B =3B 0 =3B =3B =3B =3B 1= K =3B 0 part
=86=80sda5 =3B =3B =3B =3B =3B&nbs= p=3B =3B =3B =3B =3B =3B =3B =3B =3B = =3B =3B =3B =3B =3B =3B =3B =3B =3B =3B=  =3B =3B =3B =3B =3B =3B =3B =3B =3B&nb= sp=3B =3B =3B =3B =3B =3B =3B =3B =3B = =3B =3B =3B 8:5 =3B =3B =3B 0 =3B 57.9G =3B 0 p= art
=81 =86=80mymach--vg-root =3B =3B =3B =3B =3B&n= bsp=3B =3B =3B =3B =3B =3B =3B =3B =3B = =3B =3B =3B =3B =3B 254:0 =3B =3B =3B 0 =3B=  =3B 8.4G =3B 0 lvm =3B /
=81 =86=80mymach--vg-var =3B&n= bsp=3B =3B =3B =3B =3B =3B =3B =3B =3B = =3B =3B =3B =3B =3B =3B =3B =3B =3B =3B=  =3B 254:4 =3B =3B =3B 0 =3B =3B 2.8G =3B 0 lvm=  =3B /var
=81 =86=80mymach--vg-swap_1 =3B =3B =3B = =3B =3B =3B =3B =3B =3B =3B =3B =3B =3B=  =3B 254:5 =3B =3B =3B 0 =3B 31.9G =3B 0 lvlsm = =3B [SWAP]
=81 =86=80mymach--vg-tmp =3B =3B =3B =3B = =3B =3B =3B =3B =3B =3B =3B =3B =3B =3B=  =3B =3B =3B =3B =3B =3B 254:6 =3B =3B = =3B 0 =3B =3B 380M =3B 0 lvm =3B /tmp
=81 =84=80mymach--= vg-home =3B =3B =3B =3B =3B =3B =3B =3B&nbs= p=3B =3B =3B =3B =3B =3B =3B =3B =3B 254:7&= nbsp=3B =3B =3B 0 =3B =3B =3B =3B 5G =3B 0 lvm&= nbsp=3B /home
=84=80sda6 =3B =3B =3B =3B =3B =3B=  =3B =3B =3B =3B =3B =3B =3B =3B =3B&nb= sp=3B =3B =3B =3B =3B =3B =3B =3B =3B = =3B =3B =3B =3B =3B =3B =3B =3B =3B =3B=  =3B =3B =3B =3B =3B =3B =3B =3B =3B&nb= sp=3B =3B =3B 8:6 =3B =3B =3B 0 418.8G =3B 0 part <= br> =3B =86=80xenvg-xenlv =3B =3B =3B =3B =3B = =3B =3B =3B =3B =3B =3B =3B =3B =3B =3B=  =3B =3B =3B =3B =3B =3B =3B =3B =3B&nb= sp=3B =3B =3B =3B =3B 254:1 =3B =3B =3B 0 = =3B =3B =3B 32G =3B 0 lvm =3B /xenfs
 =3B =86=80xenv= g-test01--pv--guest--swap 254:2 =3B =3B =3B 0 =3B =3B 1= 28M =3B 0 lvm =3B
 =3B =84=80xenvg-test01--pv--guest--disk&= nbsp=3B =3B 254:3 =3B =3B =3B 0 =3B =3B =3B&nbs= p=3B 4G =3B 0 lvm =3B


How do I make space for the vms?&= nbsp=3B

How might I better set-up/manage the disk space on this lap= top?

Thanks in advance=2C
Ray
= --_29094481-159c-415a-af64-68e553d808c1_-- --===============8216317762399225130== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users --===============8216317762399225130==-- From xen-users-bounces@lists.xen.org Sun Jan 03 18:02:01 2016 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sun, 03 Jan 2016 18:02: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 1aFmxt-0007bJ-22; Sun, 03 Jan 2016 18:01:13 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1aFmxq-0007bD-Uv for xen-users@lists.xen.org; Sun, 03 Jan 2016 18:01:11 +0000 Received: from [85.158.139.211] by server-15.bemta-5.messagelabs.com id 27/16-16870-6E169865; Sun, 03 Jan 2016 18:01:10 +0000 X-Env-Sender: a9121431@gmail.com X-Msg-Ref: server-5.tower-206.messagelabs.com!1451844067!13686466!1 X-Originating-IP: [209.85.214.195] X-SpamReason: No, hits=0.3 required=7.0 tests=RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 7.35.1; banners=-,-,- X-VirusChecked: Checked Received: (qmail 19891 invoked from network); 3 Jan 2016 18:01:08 -0000 Received: from mail-ob0-f195.google.com (HELO mail-ob0-f195.google.com) (209.85.214.195) by server-5.tower-206.messagelabs.com with AES128-GCM-SHA256 encrypted SMTP; 3 Jan 2016 18:01:08 -0000 Received: by mail-ob0-f195.google.com with SMTP id wz2so12158383obc.0 for ; Sun, 03 Jan 2016 10:01:07 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=mxCu7YL/O/PAWET71/qp1wdsdNFGH+2//yAz5JADsFo=; b=hrW7X75+o2CRIjEzU1ol35fWfkclLHSReAo2vAFJhcD1Qc431pkq12sI2YGxskJSoW 4rJkNgV04Jtcz6YQfW6zsV0CPmnU6wKbNzgxsasLD8RPe7STkM++6A/74wG9BLvJWmk8 ko/DO3dx28R+vIbXoWXp/dS/rJqBfEp+kBVFoXoC75zX9bocGSzPL51ktHdjvXOair3r FBuUsIQwcm3eQbA3Do+2ZsVro6fBQnspOwH+Och9Z3FSCGju3uDwYEyHJ6kw85Ol6YiE vZZfRFuV3EUklDHbNt30WA2vp8GZ1IXwg2CEuEcYyitBSHZlP/EVStvpPP9nJwQHrjZR IRyA== MIME-Version: 1.0 X-Received: by 10.182.60.170 with SMTP id i10mr56050196obr.62.1451844066748; Sun, 03 Jan 2016 10:01:06 -0800 (PST) Received: by 10.182.153.233 with HTTP; Sun, 3 Jan 2016 10:01:06 -0800 (PST) In-Reply-To: References: <20151230160147.88486qsc1m9vm1kw@vfemail.net> Date: Mon, 4 Jan 2016 02:01:06 +0800 Message-ID: From: John Mok To: "xen-users@lists.xen.org" Subject: Re: [Xen-users] PCI Passthrough of iwlwifi adapter into Windows HVM failed to start X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org Hi, I tried to use Xen 4.6.0 and PCI Passthrough also failed. Any idea why the driver in Windows HVM could not start? Thanks a lot. John Mok On Fri, Jan 1, 2016 at 10:21 PM, Zir Blazer wrote: > > >> >> Hi, >> >> >> >> I am using Xen 4.4.1 on Debian Jessie on Lenovo ThinkPad X250. > > Before doing anything, try at least with Xen 4.5+. The 4.4 version had a PCI > Passthrough regression that made it totally broken for some users. Don't try > too hard to figure out why you can't get it working if you don't test with > other Xen versions (4.3 or 4.5 worked for me, 4.4 did not, and 4.6 I didn't > tested), trust me. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Sun Jan 03 18:02:01 2016 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sun, 03 Jan 2016 18:02: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 1aFmxt-0007bJ-22; Sun, 03 Jan 2016 18:01:13 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1aFmxq-0007bD-Uv for xen-users@lists.xen.org; Sun, 03 Jan 2016 18:01:11 +0000 Received: from [85.158.139.211] by server-15.bemta-5.messagelabs.com id 27/16-16870-6E169865; Sun, 03 Jan 2016 18:01:10 +0000 X-Env-Sender: a9121431@gmail.com X-Msg-Ref: server-5.tower-206.messagelabs.com!1451844067!13686466!1 X-Originating-IP: [209.85.214.195] X-SpamReason: No, hits=0.3 required=7.0 tests=RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 7.35.1; banners=-,-,- X-VirusChecked: Checked Received: (qmail 19891 invoked from network); 3 Jan 2016 18:01:08 -0000 Received: from mail-ob0-f195.google.com (HELO mail-ob0-f195.google.com) (209.85.214.195) by server-5.tower-206.messagelabs.com with AES128-GCM-SHA256 encrypted SMTP; 3 Jan 2016 18:01:08 -0000 Received: by mail-ob0-f195.google.com with SMTP id wz2so12158383obc.0 for ; Sun, 03 Jan 2016 10:01:07 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=mxCu7YL/O/PAWET71/qp1wdsdNFGH+2//yAz5JADsFo=; b=hrW7X75+o2CRIjEzU1ol35fWfkclLHSReAo2vAFJhcD1Qc431pkq12sI2YGxskJSoW 4rJkNgV04Jtcz6YQfW6zsV0CPmnU6wKbNzgxsasLD8RPe7STkM++6A/74wG9BLvJWmk8 ko/DO3dx28R+vIbXoWXp/dS/rJqBfEp+kBVFoXoC75zX9bocGSzPL51ktHdjvXOair3r FBuUsIQwcm3eQbA3Do+2ZsVro6fBQnspOwH+Och9Z3FSCGju3uDwYEyHJ6kw85Ol6YiE vZZfRFuV3EUklDHbNt30WA2vp8GZ1IXwg2CEuEcYyitBSHZlP/EVStvpPP9nJwQHrjZR IRyA== MIME-Version: 1.0 X-Received: by 10.182.60.170 with SMTP id i10mr56050196obr.62.1451844066748; Sun, 03 Jan 2016 10:01:06 -0800 (PST) Received: by 10.182.153.233 with HTTP; Sun, 3 Jan 2016 10:01:06 -0800 (PST) In-Reply-To: References: <20151230160147.88486qsc1m9vm1kw@vfemail.net> Date: Mon, 4 Jan 2016 02:01:06 +0800 Message-ID: From: John Mok To: "xen-users@lists.xen.org" Subject: Re: [Xen-users] PCI Passthrough of iwlwifi adapter into Windows HVM failed to start X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org Hi, I tried to use Xen 4.6.0 and PCI Passthrough also failed. Any idea why the driver in Windows HVM could not start? Thanks a lot. John Mok On Fri, Jan 1, 2016 at 10:21 PM, Zir Blazer wrote: > > >> >> Hi, >> >> >> >> I am using Xen 4.4.1 on Debian Jessie on Lenovo ThinkPad X250. > > Before doing anything, try at least with Xen 4.5+. The 4.4 version had a PCI > Passthrough regression that made it totally broken for some users. Don't try > too hard to figure out why you can't get it working if you don't test with > other Xen versions (4.3 or 4.5 worked for me, 4.4 did not, and 4.6 I didn't > tested), trust me. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Sun Jan 03 18:09:04 2016 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sun, 03 Jan 2016 18: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 1aFn5I-0007sl-OT; Sun, 03 Jan 2016 18:08:52 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1aFn5H-0007sa-L8 for xen-users@lists.xen.org; Sun, 03 Jan 2016 18:08:51 +0000 Received: from [85.158.139.211] by server-2.bemta-5.messagelabs.com id 85/9E-31450-2B369865; Sun, 03 Jan 2016 18:08:50 +0000 X-Env-Sender: a9121431@gmail.com X-Msg-Ref: server-10.tower-206.messagelabs.com!1451844526!13652364!1 X-Originating-IP: [209.85.218.43] X-SpamReason: No, hits=1.1 required=7.0 tests=BODY_RANDOM_LONG, MAILTO_TO_SPAM_ADDR,RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 7.35.1; banners=-,-,- X-VirusChecked: Checked Received: (qmail 30102 invoked from network); 3 Jan 2016 18:08:47 -0000 Received: from mail-oi0-f43.google.com (HELO mail-oi0-f43.google.com) (209.85.218.43) by server-10.tower-206.messagelabs.com with AES128-GCM-SHA256 encrypted SMTP; 3 Jan 2016 18:08:47 -0000 Received: by mail-oi0-f43.google.com with SMTP id o62so239369719oif.3 for ; Sun, 03 Jan 2016 10:08:47 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=um9O72xO3HCLuysYNLNaW7MzuDa9aWl/LRts4TDgfVU=; b=xBiQQ65qAzPMZ+6ZmJPeUuvrm7f4XetY+Vjb1mjvA+OZ2Eow5Hb/RAwEW2tM/uBK1f KprYp/EzaVMazWfg45Xe9mtaSprCnDZgxU5tvFerbvLci4x3hBbYS/AcvCPfdTCDfrud gBOk+B8FcRGy53dMnW1A8swrK3FwxC6W3XHC9ebGJ3vj9Dh737tp+mVnx+cuWk21YyDq LLsNtP7HbomaokLIWBm5d7xnbkmR+29j4mXAhtXtXHiGBke+gNL11iJm7cNnwFsFogdp avMa+2iRTGn3fdEQu3c6O0u/JJj6FxC5FmmwtkNbCTixyN2cwmVew5q597EI9eafi9jy ntsA== MIME-Version: 1.0 X-Received: by 10.202.66.86 with SMTP id p83mr37706007oia.138.1451844526419; Sun, 03 Jan 2016 10:08:46 -0800 (PST) Received: by 10.182.153.233 with HTTP; Sun, 3 Jan 2016 10:08:46 -0800 (PST) In-Reply-To: <20160101073625.17404r82zk0rl3qc@vfemail.net> References: <20151230160147.88486qsc1m9vm1kw@vfemail.net> <20160101073625.17404r82zk0rl3qc@vfemail.net> Date: Mon, 4 Jan 2016 02:08:46 +0800 Message-ID: From: John Mok To: "xen-users@lists.xen.org" Subject: Re: [Xen-users] PCI Passthrough of iwlwifi adapter into Windows HVM failed to start X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: 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 what I understand, some devices can't be reinitialized (and won't work) by the DomU driver after they've already been initialized on >the Dom0. Blacklisting the module should prevent it from being initialized before being passed through to the DomU. The driver iwlwifi was compiled as a module and I can see it using lsmod. The module has been preceeded by the xen-pciback, such that the xen-pciback is loaded first, and I use the command, xl pci-assignable-list, and the WiFi PCI device, i.e. 0030:00.0, appears. >If that doesn't work, it's worth reading this page in full: http://wiki.xenproject.org/wiki/Xen_PCI_Passthrough and mentioning your distro, >Xen version, and hardware (e.g. whether you have an IOMMU or not). In Xen 4.0.x, I succeeded to pass through LSI SAS controller to Windows HVM. I had read through http://wiki.xenproject.org/wiki/Xen_PCI_Passthrough, and the hardware ThinkPad x250 has VT-d support in BIOS. Any idea why the driver in Windows HVM could not start? Thanks a lot. John Mok On Fri, Jan 1, 2016 at 9:36 PM, wrote: > Quoting "John Mok" : > >>> Just to confirm, are you certain that the driver in question really does >>> work when it is running on baremetal ....? >> >> >> Yes, the driver works on baremetal, but not try on other >> virtualization passthrough. >> >>> I'm just guessing here, but does dmesg/journalctl have anything to say on >>> the Dom0 side? In particular, an error about the driver >attempting to write >>> to read-only configuration space could indicate that you need the >>> "permissive=1" flag. See >>> http://wiki.xenproject.org/wiki/Xen_PCI_Passthrough#PV_guests_and_PCI_quirks >> >> >> I do not see anything complaining driver failing to write to read-only >> configuration space. But somehow the Windows 7 HVM guest could not >> bring up the Intel AC 7265 driver with error code 10 (fail to start). >> >> As the driver could run on baremetal, it should be a Xen PCI >> passthrough problem. >> >> I hope someone could advise how to solve the problem, or point me to >> the right direction. >> >> Thanks a lot. >> >> John Mok > > > My mistake, the "permissive" flag only applies to PV guests. > > Once again I'm just guessing, but you could try blacklisting the module > (iwlwifi) for the adapter on the Dom0. Make sure `lsmod | grep iwlwifi` > outputs something, just to make sure that module isn't built into the > kernel, then run `echo blacklist iwlwifi >> /etc/modprobe.d/blacklist` and > reboot. Check your distro's documentation for blacklisting modules if that > doesn't work. > > From what I understand, some devices can't be reinitialized (and won't work) > by the DomU driver after they've already been initialized on the Dom0. > Blacklisting the module should prevent it from being initialized before > being passed through to the DomU. > > If that doesn't work, it's worth reading this page in full: > http://wiki.xenproject.org/wiki/Xen_PCI_Passthrough and mentioning your > distro, Xen version, and hardware (e.g. whether you have an IOMMU or not). > > > ------------------------------------------------- > > ONLY AT VFEmail! - Use our Metadata Mitigator to keep your email out of the > NSA's hands! > $24.95 ONETIME Lifetime accounts with Privacy Features! 15GB disk! No > bandwidth quotas! > Commercial and Bulk Mail Options! _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Sun Jan 03 18:09:04 2016 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sun, 03 Jan 2016 18: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 1aFn5I-0007sl-OT; Sun, 03 Jan 2016 18:08:52 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1aFn5H-0007sa-L8 for xen-users@lists.xen.org; Sun, 03 Jan 2016 18:08:51 +0000 Received: from [85.158.139.211] by server-2.bemta-5.messagelabs.com id 85/9E-31450-2B369865; Sun, 03 Jan 2016 18:08:50 +0000 X-Env-Sender: a9121431@gmail.com X-Msg-Ref: server-10.tower-206.messagelabs.com!1451844526!13652364!1 X-Originating-IP: [209.85.218.43] X-SpamReason: No, hits=1.1 required=7.0 tests=BODY_RANDOM_LONG, MAILTO_TO_SPAM_ADDR,RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 7.35.1; banners=-,-,- X-VirusChecked: Checked Received: (qmail 30102 invoked from network); 3 Jan 2016 18:08:47 -0000 Received: from mail-oi0-f43.google.com (HELO mail-oi0-f43.google.com) (209.85.218.43) by server-10.tower-206.messagelabs.com with AES128-GCM-SHA256 encrypted SMTP; 3 Jan 2016 18:08:47 -0000 Received: by mail-oi0-f43.google.com with SMTP id o62so239369719oif.3 for ; Sun, 03 Jan 2016 10:08:47 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=um9O72xO3HCLuysYNLNaW7MzuDa9aWl/LRts4TDgfVU=; b=xBiQQ65qAzPMZ+6ZmJPeUuvrm7f4XetY+Vjb1mjvA+OZ2Eow5Hb/RAwEW2tM/uBK1f KprYp/EzaVMazWfg45Xe9mtaSprCnDZgxU5tvFerbvLci4x3hBbYS/AcvCPfdTCDfrud gBOk+B8FcRGy53dMnW1A8swrK3FwxC6W3XHC9ebGJ3vj9Dh737tp+mVnx+cuWk21YyDq LLsNtP7HbomaokLIWBm5d7xnbkmR+29j4mXAhtXtXHiGBke+gNL11iJm7cNnwFsFogdp avMa+2iRTGn3fdEQu3c6O0u/JJj6FxC5FmmwtkNbCTixyN2cwmVew5q597EI9eafi9jy ntsA== MIME-Version: 1.0 X-Received: by 10.202.66.86 with SMTP id p83mr37706007oia.138.1451844526419; Sun, 03 Jan 2016 10:08:46 -0800 (PST) Received: by 10.182.153.233 with HTTP; Sun, 3 Jan 2016 10:08:46 -0800 (PST) In-Reply-To: <20160101073625.17404r82zk0rl3qc@vfemail.net> References: <20151230160147.88486qsc1m9vm1kw@vfemail.net> <20160101073625.17404r82zk0rl3qc@vfemail.net> Date: Mon, 4 Jan 2016 02:08:46 +0800 Message-ID: From: John Mok To: "xen-users@lists.xen.org" Subject: Re: [Xen-users] PCI Passthrough of iwlwifi adapter into Windows HVM failed to start X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: 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 what I understand, some devices can't be reinitialized (and won't work) by the DomU driver after they've already been initialized on >the Dom0. Blacklisting the module should prevent it from being initialized before being passed through to the DomU. The driver iwlwifi was compiled as a module and I can see it using lsmod. The module has been preceeded by the xen-pciback, such that the xen-pciback is loaded first, and I use the command, xl pci-assignable-list, and the WiFi PCI device, i.e. 0030:00.0, appears. >If that doesn't work, it's worth reading this page in full: http://wiki.xenproject.org/wiki/Xen_PCI_Passthrough and mentioning your distro, >Xen version, and hardware (e.g. whether you have an IOMMU or not). In Xen 4.0.x, I succeeded to pass through LSI SAS controller to Windows HVM. I had read through http://wiki.xenproject.org/wiki/Xen_PCI_Passthrough, and the hardware ThinkPad x250 has VT-d support in BIOS. Any idea why the driver in Windows HVM could not start? Thanks a lot. John Mok On Fri, Jan 1, 2016 at 9:36 PM, wrote: > Quoting "John Mok" : > >>> Just to confirm, are you certain that the driver in question really does >>> work when it is running on baremetal ....? >> >> >> Yes, the driver works on baremetal, but not try on other >> virtualization passthrough. >> >>> I'm just guessing here, but does dmesg/journalctl have anything to say on >>> the Dom0 side? In particular, an error about the driver >attempting to write >>> to read-only configuration space could indicate that you need the >>> "permissive=1" flag. See >>> http://wiki.xenproject.org/wiki/Xen_PCI_Passthrough#PV_guests_and_PCI_quirks >> >> >> I do not see anything complaining driver failing to write to read-only >> configuration space. But somehow the Windows 7 HVM guest could not >> bring up the Intel AC 7265 driver with error code 10 (fail to start). >> >> As the driver could run on baremetal, it should be a Xen PCI >> passthrough problem. >> >> I hope someone could advise how to solve the problem, or point me to >> the right direction. >> >> Thanks a lot. >> >> John Mok > > > My mistake, the "permissive" flag only applies to PV guests. > > Once again I'm just guessing, but you could try blacklisting the module > (iwlwifi) for the adapter on the Dom0. Make sure `lsmod | grep iwlwifi` > outputs something, just to make sure that module isn't built into the > kernel, then run `echo blacklist iwlwifi >> /etc/modprobe.d/blacklist` and > reboot. Check your distro's documentation for blacklisting modules if that > doesn't work. > > From what I understand, some devices can't be reinitialized (and won't work) > by the DomU driver after they've already been initialized on the Dom0. > Blacklisting the module should prevent it from being initialized before > being passed through to the DomU. > > If that doesn't work, it's worth reading this page in full: > http://wiki.xenproject.org/wiki/Xen_PCI_Passthrough and mentioning your > distro, Xen version, and hardware (e.g. whether you have an IOMMU or not). > > > ------------------------------------------------- > > ONLY AT VFEmail! - Use our Metadata Mitigator to keep your email out of the > NSA's hands! > $24.95 ONETIME Lifetime accounts with Privacy Features! 15GB disk! No > bandwidth quotas! > Commercial and Bulk Mail Options! _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Sun Jan 03 22:48:18 2016 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sun, 03 Jan 2016 22:48: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 1aFrQm-0004DJ-B2; Sun, 03 Jan 2016 22:47:20 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1aFrQk-0004DE-Px for xen-users@lists.xen.org; Sun, 03 Jan 2016 22:47:18 +0000 Received: from [85.158.139.211] by server-3.bemta-5.messagelabs.com id 6A/25-13487-6F4A9865; Sun, 03 Jan 2016 22:47:18 +0000 X-Env-Sender: atul.droid@gmail.com X-Msg-Ref: server-7.tower-206.messagelabs.com!1451861237!13443600!1 X-Originating-IP: [74.125.82.51] X-SpamReason: No, hits=1.2 required=7.0 tests=HTML_10_20,HTML_MESSAGE, RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 7.35.1; banners=-,-,- X-VirusChecked: Checked Received: (qmail 42562 invoked from network); 3 Jan 2016 22:47:17 -0000 Received: from mail-wm0-f51.google.com (HELO mail-wm0-f51.google.com) (74.125.82.51) by server-7.tower-206.messagelabs.com with AES128-GCM-SHA256 encrypted SMTP; 3 Jan 2016 22:47:17 -0000 Received: by mail-wm0-f51.google.com with SMTP id f206so190534886wmf.0 for ; Sun, 03 Jan 2016 14:47:17 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:from:date:message-id:subject:to:content-type; bh=nHTEuthCCfKD/XpCseIk4/vlyktKB1Ry6OOBiY6V1fs=; b=DII+xmQjyp6lpOnQcZG0XleG8c1JprvsBFzRPmwzSnMh6iMEmJUJryL3aVKAGPSqo9 L8jvyUM0ylXGJEQ1Uo3txhB5EgO7bSqn3eoDeqK8s57WgTGhsBHGpFwBgrwmc2x3ozz5 vYKVbKCJjOcu8i5SFy1Nt3+M6qGTagc5SPyYztvlPY7EJiUZSGoatmageE3ScQfhG2Vj YsU9Xv/S/peq67TSdFcdYO6qn8n1tnCRY+HGBHi4fH0nU6Vjcc4r2oYxZj/1YGDm6ir4 cpAouMrlkS+pYytPlooNajUgcrtnVVgo5q8iF10vzBPJYt2/suAfNErIBrkBa2izvAfb +9Xw== X-Received: by 10.28.92.17 with SMTP id q17mr92181641wmb.40.1451861236935; Sun, 03 Jan 2016 14:47:16 -0800 (PST) MIME-Version: 1.0 Received: by 10.194.119.101 with HTTP; Sun, 3 Jan 2016 14:46:57 -0800 (PST) From: Atul Raut Date: Sun, 3 Jan 2016 14:46:57 -0800 Message-ID: To: xen-users@lists.xen.org Subject: [Xen-users] DOMu failed to launch X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============9162151855429381744==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============9162151855429381744== Content-Type: multipart/alternative; boundary=001a1146df064a709f052875c95a --001a1146df064a709f052875c95a Content-Type: text/plain; charset=UTF-8 Hi, I am getting below error logs on DOMu creation. I am using ARMv7 platform & Xen-4.6. Do I need to enable LPAE for DOM0 ? Please suggest any pointers. domainbuilder: detail: setup_pgtables_arm: called domainbuilder: detail: clear_page: pfn 0x39000, mfn 0x39000 domainbuilder: detail: clear_page: pfn 0x39001, mfn 0x39001 domainbuilder: detail: start_info_arm: called domainbuilder: detail: domain builder memory footprint domainbuilder: detail: allocated domainbuilder: detail: malloc : 389 kB domainbuilder: detail: anon mmap : 0 bytes domainbuilder: detail: mapped domainbuilder: detail: file mmap : 22314 kB domainbuilder: detail: domU mmap : 22324 kB domainbuilder: detail: vcpu_arm64: called domainbuilder: detail: DTB 47fff000 domainbuilder: detail: Initial state CPSR 0x1c5 PC 0x40080000 domainbuilder: detail: launch_vm: called, ctxt=0x7f903de004 domainbuilder: detail: xc_dom_gnttab_hvm_seed: called, pfn=0x38000 domainbuilder: detail: xc_dom_release: called (XEN) grant_table.c:411:d0v1 Bad flags (0) or dom (0). (expected dom 0) Regards, rax --001a1146df064a709f052875c95a Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Hi,

I am getting below error logs o= n DOMu creation.
I am using ARMv7 platform & Xen-4.6.
Do I need t= o enable LPAE for DOM0 ?
Please suggest any pointers.

domainbuil= der: detail: setup_pgtables_arm: called
domainbuilder: detail: clear_pag= e: pfn 0x39000, mfn 0x39000
domainbuilder: detail: clear_page: pfn 0x390= 01, mfn 0x39001
domainbuilder: detail: start_info_arm: called
domainb= uilder: detail: domain builder memory footprint
domainbuilder: detail:= =C2=A0=C2=A0=C2=A0 allocated
domainbuilder: detail:=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0 malloc=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0=C2=A0 : 389 kB
domainbuilder: detail:=C2=A0=C2=A0=C2=A0= =C2=A0=C2=A0=C2=A0 anon mmap=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0 : 0 bytes
domainbuilder: detail:=C2=A0=C2=A0=C2=A0 mapped
d= omainbuilder: detail:=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 file mmap=C2=A0= =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 : 22314 kB
domainbuilde= r: detail:=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 domU mmap=C2=A0=C2=A0=C2=A0= =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 : 22324 kB
domainbuilder: detail: v= cpu_arm64: called
domainbuilder: detail: DTB 47fff000
domainbuilder: = detail: Initial state CPSR 0x1c5 PC 0x40080000
domainbuilder: detail: la= unch_vm: called, ctxt=3D0x7f903de004
domainbuilder: detail: xc_dom_gntta= b_hvm_seed: called, pfn=3D0x38000
domainbuilder: detail: xc_dom_release:= called
(XEN) grant_table.c:411:d0v1 Bad flags (0) or dom (0). (expected= dom 0)



Regards,
rax
--001a1146df064a709f052875c95a-- --===============9162151855429381744== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users --===============9162151855429381744==-- From xen-users-bounces@lists.xen.org Sun Jan 03 22:48:18 2016 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sun, 03 Jan 2016 22:48: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 1aFrQm-0004DJ-B2; Sun, 03 Jan 2016 22:47:20 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1aFrQk-0004DE-Px for xen-users@lists.xen.org; Sun, 03 Jan 2016 22:47:18 +0000 Received: from [85.158.139.211] by server-3.bemta-5.messagelabs.com id 6A/25-13487-6F4A9865; Sun, 03 Jan 2016 22:47:18 +0000 X-Env-Sender: atul.droid@gmail.com X-Msg-Ref: server-7.tower-206.messagelabs.com!1451861237!13443600!1 X-Originating-IP: [74.125.82.51] X-SpamReason: No, hits=1.2 required=7.0 tests=HTML_10_20,HTML_MESSAGE, RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 7.35.1; banners=-,-,- X-VirusChecked: Checked Received: (qmail 42562 invoked from network); 3 Jan 2016 22:47:17 -0000 Received: from mail-wm0-f51.google.com (HELO mail-wm0-f51.google.com) (74.125.82.51) by server-7.tower-206.messagelabs.com with AES128-GCM-SHA256 encrypted SMTP; 3 Jan 2016 22:47:17 -0000 Received: by mail-wm0-f51.google.com with SMTP id f206so190534886wmf.0 for ; Sun, 03 Jan 2016 14:47:17 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:from:date:message-id:subject:to:content-type; bh=nHTEuthCCfKD/XpCseIk4/vlyktKB1Ry6OOBiY6V1fs=; b=DII+xmQjyp6lpOnQcZG0XleG8c1JprvsBFzRPmwzSnMh6iMEmJUJryL3aVKAGPSqo9 L8jvyUM0ylXGJEQ1Uo3txhB5EgO7bSqn3eoDeqK8s57WgTGhsBHGpFwBgrwmc2x3ozz5 vYKVbKCJjOcu8i5SFy1Nt3+M6qGTagc5SPyYztvlPY7EJiUZSGoatmageE3ScQfhG2Vj YsU9Xv/S/peq67TSdFcdYO6qn8n1tnCRY+HGBHi4fH0nU6Vjcc4r2oYxZj/1YGDm6ir4 cpAouMrlkS+pYytPlooNajUgcrtnVVgo5q8iF10vzBPJYt2/suAfNErIBrkBa2izvAfb +9Xw== X-Received: by 10.28.92.17 with SMTP id q17mr92181641wmb.40.1451861236935; Sun, 03 Jan 2016 14:47:16 -0800 (PST) MIME-Version: 1.0 Received: by 10.194.119.101 with HTTP; Sun, 3 Jan 2016 14:46:57 -0800 (PST) From: Atul Raut Date: Sun, 3 Jan 2016 14:46:57 -0800 Message-ID: To: xen-users@lists.xen.org Subject: [Xen-users] DOMu failed to launch X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============9162151855429381744==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============9162151855429381744== Content-Type: multipart/alternative; boundary=001a1146df064a709f052875c95a --001a1146df064a709f052875c95a Content-Type: text/plain; charset=UTF-8 Hi, I am getting below error logs on DOMu creation. I am using ARMv7 platform & Xen-4.6. Do I need to enable LPAE for DOM0 ? Please suggest any pointers. domainbuilder: detail: setup_pgtables_arm: called domainbuilder: detail: clear_page: pfn 0x39000, mfn 0x39000 domainbuilder: detail: clear_page: pfn 0x39001, mfn 0x39001 domainbuilder: detail: start_info_arm: called domainbuilder: detail: domain builder memory footprint domainbuilder: detail: allocated domainbuilder: detail: malloc : 389 kB domainbuilder: detail: anon mmap : 0 bytes domainbuilder: detail: mapped domainbuilder: detail: file mmap : 22314 kB domainbuilder: detail: domU mmap : 22324 kB domainbuilder: detail: vcpu_arm64: called domainbuilder: detail: DTB 47fff000 domainbuilder: detail: Initial state CPSR 0x1c5 PC 0x40080000 domainbuilder: detail: launch_vm: called, ctxt=0x7f903de004 domainbuilder: detail: xc_dom_gnttab_hvm_seed: called, pfn=0x38000 domainbuilder: detail: xc_dom_release: called (XEN) grant_table.c:411:d0v1 Bad flags (0) or dom (0). (expected dom 0) Regards, rax --001a1146df064a709f052875c95a Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Hi,

I am getting below error logs o= n DOMu creation.
I am using ARMv7 platform & Xen-4.6.
Do I need t= o enable LPAE for DOM0 ?
Please suggest any pointers.

domainbuil= der: detail: setup_pgtables_arm: called
domainbuilder: detail: clear_pag= e: pfn 0x39000, mfn 0x39000
domainbuilder: detail: clear_page: pfn 0x390= 01, mfn 0x39001
domainbuilder: detail: start_info_arm: called
domainb= uilder: detail: domain builder memory footprint
domainbuilder: detail:= =C2=A0=C2=A0=C2=A0 allocated
domainbuilder: detail:=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0 malloc=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0=C2=A0 : 389 kB
domainbuilder: detail:=C2=A0=C2=A0=C2=A0= =C2=A0=C2=A0=C2=A0 anon mmap=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0 : 0 bytes
domainbuilder: detail:=C2=A0=C2=A0=C2=A0 mapped
d= omainbuilder: detail:=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 file mmap=C2=A0= =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 : 22314 kB
domainbuilde= r: detail:=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 domU mmap=C2=A0=C2=A0=C2=A0= =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 : 22324 kB
domainbuilder: detail: v= cpu_arm64: called
domainbuilder: detail: DTB 47fff000
domainbuilder: = detail: Initial state CPSR 0x1c5 PC 0x40080000
domainbuilder: detail: la= unch_vm: called, ctxt=3D0x7f903de004
domainbuilder: detail: xc_dom_gntta= b_hvm_seed: called, pfn=3D0x38000
domainbuilder: detail: xc_dom_release:= called
(XEN) grant_table.c:411:d0v1 Bad flags (0) or dom (0). (expected= dom 0)



Regards,
rax
--001a1146df064a709f052875c95a-- --===============9162151855429381744== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users --===============9162151855429381744==-- From xen-users-bounces@lists.xen.org Mon Jan 04 11:39:21 2016 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 04 Jan 2016 11:39: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 1aG3Sq-0002XN-Jw; Mon, 04 Jan 2016 11:38:16 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1aG3Sp-0002X9-8U for xen-users@lists.xen.org; Mon, 04 Jan 2016 11:38:15 +0000 Received: from [193.109.254.147] by server-6.bemta-14.messagelabs.com id 64/39-16618-6A95A865; Mon, 04 Jan 2016 11:38:14 +0000 X-Env-Sender: prvs=8049774f7=Ian.Campbell@citrix.com X-Msg-Ref: server-7.tower-27.messagelabs.com!1451907490!14535081!1 X-Originating-IP: [66.165.176.89] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjYuMTY1LjE3Ni44OSA9PiAyMDMwMDc=\n, received_headers: No Received headers X-StarScan-Received: X-StarScan-Version: 7.35.1; banners=-,-,- X-VirusChecked: Checked Received: (qmail 2075 invoked from network); 4 Jan 2016 11:38:11 -0000 Received: from smtp.citrix.com (HELO SMTP.CITRIX.COM) (66.165.176.89) by server-7.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 4 Jan 2016 11:38:11 -0000 X-IronPort-AV: E=Sophos;i="5.20,520,1444694400"; d="scan'208";a="322701362" Message-ID: <1451907382.13361.37.camel@citrix.com> From: Ian Campbell To: Andreas Pflug , Date: Mon, 4 Jan 2016 11:36:22 +0000 In-Reply-To: <56812352.8060500@pse-consulting.de> References: <56812352.8060500@pse-consulting.de> X-Mailer: Evolution 3.18.2-1 MIME-Version: 1.0 X-DLP: MIA2 Subject: [Xen-users] Missing libvirt+libxl functionality (Was: Re: Programmatic administration of Xen machines) X-BeenThere: xen-users@lists.xen.org X-Mailman-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 U29ycnkgdG8gaGlqYWNrIHRoaXMgdGhyZWFkLgoKT24gTW9uLCAyMDE1LTEyLTI4IGF0IDEyOjU2 ICswMTAwLCBBbmRyZWFzIFBmbHVnIHdyb3RlOgo+IAo+IEFjdHVhbGx5LCBJIGZpbmQgdmlyc2gg YSBiYWQgaWRlYSBzaW5jZSBpdHMgc3VwcG9ydCBmb3IgdGhlIG5ldyB4bAo+IGludGVyZmFjZSBp c24ndCBmZWF0dXJlIGNvbXBsZXRlIGFzIHRoZSBvbGQgeG0gaW50ZXJmYWNlIHdhcy4gSSBoYWQg dG8KPiByZWFsaXplIHRoaXMgdGhlIGhhcmQgd2F5IHdoZW4gbXkgdmlyc2ggYmFzZWQgcHl0aG9u IHRvb2xzIGRpZG4ndCB3b3JrCj4gYXMgZXhwZWN0ZWQgYWZ0ZXIgdXBncmFkaW5nIGZyb20geG0g dG8geGwuCgpOb3RlIHRoYXQgdmlyc2ggc3BlYWtzIHRvIGxpYnhsIGRpcmVjdGx5LCBub3Qgdmlh IHhsLgoKUGxlYXNlIGNhbiB5b3UgbGlzdCB0aGUgZnVuY3Rpb25hbGl0eSBvZiBsaWJ2aXJ0J3Mg bGlieGwgYmFja2VkIHdoaWNoIGlzCm1pc3NpbmcgY29tcGFyZWQgdG8gdGhlIG9sZCB4ZW5kIGJh c2VkIG9uZT/CoAoKSWFuLgoKX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f X19fX19fX18KWGVuLXVzZXJzIG1haWxpbmcgbGlzdApYZW4tdXNlcnNAbGlzdHMueGVuLm9yZwpo dHRwOi8vbGlzdHMueGVuLm9yZy94ZW4tdXNlcnM= From xen-users-bounces@lists.xen.org Mon Jan 04 11:39:21 2016 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 04 Jan 2016 11:39: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 1aG3Sq-0002XN-Jw; Mon, 04 Jan 2016 11:38:16 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1aG3Sp-0002X9-8U for xen-users@lists.xen.org; Mon, 04 Jan 2016 11:38:15 +0000 Received: from [193.109.254.147] by server-6.bemta-14.messagelabs.com id 64/39-16618-6A95A865; Mon, 04 Jan 2016 11:38:14 +0000 X-Env-Sender: prvs=8049774f7=Ian.Campbell@citrix.com X-Msg-Ref: server-7.tower-27.messagelabs.com!1451907490!14535081!1 X-Originating-IP: [66.165.176.89] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjYuMTY1LjE3Ni44OSA9PiAyMDMwMDc=\n, received_headers: No Received headers X-StarScan-Received: X-StarScan-Version: 7.35.1; banners=-,-,- X-VirusChecked: Checked Received: (qmail 2075 invoked from network); 4 Jan 2016 11:38:11 -0000 Received: from smtp.citrix.com (HELO SMTP.CITRIX.COM) (66.165.176.89) by server-7.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 4 Jan 2016 11:38:11 -0000 X-IronPort-AV: E=Sophos;i="5.20,520,1444694400"; d="scan'208";a="322701362" Message-ID: <1451907382.13361.37.camel@citrix.com> From: Ian Campbell To: Andreas Pflug , Date: Mon, 4 Jan 2016 11:36:22 +0000 In-Reply-To: <56812352.8060500@pse-consulting.de> References: <56812352.8060500@pse-consulting.de> X-Mailer: Evolution 3.18.2-1 MIME-Version: 1.0 X-DLP: MIA2 Subject: [Xen-users] Missing libvirt+libxl functionality (Was: Re: Programmatic administration of Xen machines) X-BeenThere: xen-users@lists.xen.org X-Mailman-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 U29ycnkgdG8gaGlqYWNrIHRoaXMgdGhyZWFkLgoKT24gTW9uLCAyMDE1LTEyLTI4IGF0IDEyOjU2 ICswMTAwLCBBbmRyZWFzIFBmbHVnIHdyb3RlOgo+IAo+IEFjdHVhbGx5LCBJIGZpbmQgdmlyc2gg YSBiYWQgaWRlYSBzaW5jZSBpdHMgc3VwcG9ydCBmb3IgdGhlIG5ldyB4bAo+IGludGVyZmFjZSBp c24ndCBmZWF0dXJlIGNvbXBsZXRlIGFzIHRoZSBvbGQgeG0gaW50ZXJmYWNlIHdhcy4gSSBoYWQg dG8KPiByZWFsaXplIHRoaXMgdGhlIGhhcmQgd2F5IHdoZW4gbXkgdmlyc2ggYmFzZWQgcHl0aG9u IHRvb2xzIGRpZG4ndCB3b3JrCj4gYXMgZXhwZWN0ZWQgYWZ0ZXIgdXBncmFkaW5nIGZyb20geG0g dG8geGwuCgpOb3RlIHRoYXQgdmlyc2ggc3BlYWtzIHRvIGxpYnhsIGRpcmVjdGx5LCBub3Qgdmlh IHhsLgoKUGxlYXNlIGNhbiB5b3UgbGlzdCB0aGUgZnVuY3Rpb25hbGl0eSBvZiBsaWJ2aXJ0J3Mg bGlieGwgYmFja2VkIHdoaWNoIGlzCm1pc3NpbmcgY29tcGFyZWQgdG8gdGhlIG9sZCB4ZW5kIGJh c2VkIG9uZT/CoAoKSWFuLgoKX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f X19fX19fX18KWGVuLXVzZXJzIG1haWxpbmcgbGlzdApYZW4tdXNlcnNAbGlzdHMueGVuLm9yZwpo dHRwOi8vbGlzdHMueGVuLm9yZy94ZW4tdXNlcnM= From xen-users-bounces@lists.xen.org Mon Jan 04 11:48:22 2016 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 04 Jan 2016 11:48: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 1aG3cQ-0003lI-99; Mon, 04 Jan 2016 11:48:10 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1aG3cO-0003ku-QB for xen-users@lists.xen.org; Mon, 04 Jan 2016 11:48:08 +0000 Received: from [85.158.143.35] by server-1.bemta-4.messagelabs.com id 2E/EE-21571-8FB5A865; Mon, 04 Jan 2016 11:48:08 +0000 X-Env-Sender: pgadmin@pse-consulting.de X-Msg-Ref: server-13.tower-21.messagelabs.com!1451908084!6663218!1 X-Originating-IP: [217.72.192.74] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 7.35.1; banners=-,-,- X-VirusChecked: Checked Received: (qmail 25755 invoked from network); 4 Jan 2016 11:48:04 -0000 Received: from mout.kundenserver.de (HELO mout.kundenserver.de) (217.72.192.74) by server-13.tower-21.messagelabs.com with DHE-RSA-AES256-GCM-SHA384 encrypted SMTP; 4 Jan 2016 11:48:04 -0000 Received: from pse.homenet.org ([88.70.250.61]) by mrelayeu.kundenserver.de (mreue102) with ESMTPSA (Nemesis) id 0M40x8-1ZxyT411aE-00rYva; Mon, 04 Jan 2016 12:48:00 +0100 Received: from [192.168.0.8] (helo=pse8.fritz.box) by pse.homenet.org with esmtp (Exim 4.84) (envelope-from ) id 1aG3cE-0006fV-JK; Mon, 04 Jan 2016 12:47:58 +0100 To: Ian Campbell , xen-users@lists.xen.org References: <56812352.8060500@pse-consulting.de> <1451907382.13361.37.camel@citrix.com> From: Andreas Pflug Message-ID: <568A5BEE.9090808@pse-consulting.de> Date: Mon, 4 Jan 2016 12:47:58 +0100 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:38.0) Gecko/20100101 Thunderbird/38.5.0 MIME-Version: 1.0 In-Reply-To: <1451907382.13361.37.camel@citrix.com> X-Provags-ID: V03:K0:2LP0/eweaqN4JQVFLXaVjS9Rhwo99HL7aX5d5spTLf3ZcrMJkPJ /VN/LUDCNxPNUGJfrFUrlkCLyxo4K/hq3PCoSUDeJw5Oj3JGy4E06ImX8yxU5hFU+iA4xwt qOSWiqxHU1HcviynpIubwGwhGsqPugQfSN8RHJUnmcFDZIADFOoAdx1IsYhN9H0NyXmkAXK XEsXmP9kLRiCQ6BgzifAA== X-UI-Out-Filterresults: notjunk:1;V01:K0:DYGlK5oys+Y=:3gPXRwfR196ACaf5u7dvae Cv/JcnSjLy34cgi0MjTGk//1sOhzTQyGOOvO0haipjtPkskzUp+7GhF1AVzCfTbmrF3KcVaR+ 62kgczuJ10n8xjNMLkl/SFXw4aI8ngUmGD3p0Ks+ur+l7MSGI7MfBkTiL+5hpx6wQc+kANd/s nYY1/tqTcW4aNxFCcSCj+MgfEy7w7LSpwaR0c4befGJiXSj4spyT3OZ0CIbVUgd9tBacpvlif yN5KHaCVPx0/SU0/HDrzzHiyKmJHQhql9LZYZkxS7AJZ7JZ7Eznnqu8sJlnUGAXJ0Ek5ixbZJ vk2XQTR/+3yjI4OE8slLfYdXjHAuRNirFTNHlB7xkqrqUwfmE2/P98GEvUORazAK86QyZe8wh zxWvxS1seB1+cPQgCvetVP6J7r4Mm+3xUQq6esxVjiZ9EiJBDLIqGvs/zUYiTcKgK1Lgum8qd kjAeGgQFol1VMG2Pzf0HY95JS3CYmh7yYm3hitDnW0cmU7WucRpg3crjfngOAxjjYxUtB1C8L WixJNazgAWDcPeWP7Xa9VMy6lKI0sgJ3Efu4/+kEP5DfacJsbte4oRu1kQTTKUguG3nbNzaRT 6dGFCmhhtmgzSsuMC852l9uUr3zLuvCwgnQpoqW948orV76h8Fp2bd3cqEoX0zhtBuWoKMzPh Bdl1w8VvxVSH4sbqvD5MiuHWg6lJ1nhxIElupX4YCHeul6oJWwvZ3Ar2xCus9GsUq5/PauLux nCfa15O9mFg+7Ion Subject: Re: [Xen-users] Missing libvirt+libxl functionality (Was: Re: Programmatic administration of Xen machines) X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: 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 04.01.16 um 12:36 schrieb Ian Campbell: > Sorry to hijack this thread. > > On Mon, 2015-12-28 at 12:56 +0100, Andreas Pflug wrote: >> Actually, I find virsh a bad idea since its support for the new xl >> interface isn't feature complete as the old xm interface was. I had to >> realize this the hard way when my virsh based python tools didn't work >> as expected after upgrading from xm to xl. > Note that virsh speaks to libxl directly, not via xl. > > Please can you list the functionality of libvirt's libxl backed which is > missing compared to the old xend based one? libvirt only handles domains created through it, i.e. using xl at the same time is incompatible. Since dom0 can't be created using libvirt, it's missing from "virsh list" in any case. libvirt stores its own state, not using libxl/xenstore stuff. Regards, Andreas _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Mon Jan 04 11:48:22 2016 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 04 Jan 2016 11:48: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 1aG3cQ-0003lI-99; Mon, 04 Jan 2016 11:48:10 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1aG3cO-0003ku-QB for xen-users@lists.xen.org; Mon, 04 Jan 2016 11:48:08 +0000 Received: from [85.158.143.35] by server-1.bemta-4.messagelabs.com id 2E/EE-21571-8FB5A865; Mon, 04 Jan 2016 11:48:08 +0000 X-Env-Sender: pgadmin@pse-consulting.de X-Msg-Ref: server-13.tower-21.messagelabs.com!1451908084!6663218!1 X-Originating-IP: [217.72.192.74] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 7.35.1; banners=-,-,- X-VirusChecked: Checked Received: (qmail 25755 invoked from network); 4 Jan 2016 11:48:04 -0000 Received: from mout.kundenserver.de (HELO mout.kundenserver.de) (217.72.192.74) by server-13.tower-21.messagelabs.com with DHE-RSA-AES256-GCM-SHA384 encrypted SMTP; 4 Jan 2016 11:48:04 -0000 Received: from pse.homenet.org ([88.70.250.61]) by mrelayeu.kundenserver.de (mreue102) with ESMTPSA (Nemesis) id 0M40x8-1ZxyT411aE-00rYva; Mon, 04 Jan 2016 12:48:00 +0100 Received: from [192.168.0.8] (helo=pse8.fritz.box) by pse.homenet.org with esmtp (Exim 4.84) (envelope-from ) id 1aG3cE-0006fV-JK; Mon, 04 Jan 2016 12:47:58 +0100 To: Ian Campbell , xen-users@lists.xen.org References: <56812352.8060500@pse-consulting.de> <1451907382.13361.37.camel@citrix.com> From: Andreas Pflug Message-ID: <568A5BEE.9090808@pse-consulting.de> Date: Mon, 4 Jan 2016 12:47:58 +0100 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:38.0) Gecko/20100101 Thunderbird/38.5.0 MIME-Version: 1.0 In-Reply-To: <1451907382.13361.37.camel@citrix.com> X-Provags-ID: V03:K0:2LP0/eweaqN4JQVFLXaVjS9Rhwo99HL7aX5d5spTLf3ZcrMJkPJ /VN/LUDCNxPNUGJfrFUrlkCLyxo4K/hq3PCoSUDeJw5Oj3JGy4E06ImX8yxU5hFU+iA4xwt qOSWiqxHU1HcviynpIubwGwhGsqPugQfSN8RHJUnmcFDZIADFOoAdx1IsYhN9H0NyXmkAXK XEsXmP9kLRiCQ6BgzifAA== X-UI-Out-Filterresults: notjunk:1;V01:K0:DYGlK5oys+Y=:3gPXRwfR196ACaf5u7dvae Cv/JcnSjLy34cgi0MjTGk//1sOhzTQyGOOvO0haipjtPkskzUp+7GhF1AVzCfTbmrF3KcVaR+ 62kgczuJ10n8xjNMLkl/SFXw4aI8ngUmGD3p0Ks+ur+l7MSGI7MfBkTiL+5hpx6wQc+kANd/s nYY1/tqTcW4aNxFCcSCj+MgfEy7w7LSpwaR0c4befGJiXSj4spyT3OZ0CIbVUgd9tBacpvlif yN5KHaCVPx0/SU0/HDrzzHiyKmJHQhql9LZYZkxS7AJZ7JZ7Eznnqu8sJlnUGAXJ0Ek5ixbZJ vk2XQTR/+3yjI4OE8slLfYdXjHAuRNirFTNHlB7xkqrqUwfmE2/P98GEvUORazAK86QyZe8wh zxWvxS1seB1+cPQgCvetVP6J7r4Mm+3xUQq6esxVjiZ9EiJBDLIqGvs/zUYiTcKgK1Lgum8qd kjAeGgQFol1VMG2Pzf0HY95JS3CYmh7yYm3hitDnW0cmU7WucRpg3crjfngOAxjjYxUtB1C8L WixJNazgAWDcPeWP7Xa9VMy6lKI0sgJ3Efu4/+kEP5DfacJsbte4oRu1kQTTKUguG3nbNzaRT 6dGFCmhhtmgzSsuMC852l9uUr3zLuvCwgnQpoqW948orV76h8Fp2bd3cqEoX0zhtBuWoKMzPh Bdl1w8VvxVSH4sbqvD5MiuHWg6lJ1nhxIElupX4YCHeul6oJWwvZ3Ar2xCus9GsUq5/PauLux nCfa15O9mFg+7Ion Subject: Re: [Xen-users] Missing libvirt+libxl functionality (Was: Re: Programmatic administration of Xen machines) X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: 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 04.01.16 um 12:36 schrieb Ian Campbell: > Sorry to hijack this thread. > > On Mon, 2015-12-28 at 12:56 +0100, Andreas Pflug wrote: >> Actually, I find virsh a bad idea since its support for the new xl >> interface isn't feature complete as the old xm interface was. I had to >> realize this the hard way when my virsh based python tools didn't work >> as expected after upgrading from xm to xl. > Note that virsh speaks to libxl directly, not via xl. > > Please can you list the functionality of libvirt's libxl backed which is > missing compared to the old xend based one? libvirt only handles domains created through it, i.e. using xl at the same time is incompatible. Since dom0 can't be created using libvirt, it's missing from "virsh list" in any case. libvirt stores its own state, not using libxl/xenstore stuff. Regards, Andreas _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Mon Jan 04 11:50:52 2016 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 04 Jan 2016 11:50: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 1aG3ev-00048W-88; Mon, 04 Jan 2016 11:50:45 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1aG3eu-00047c-1O for xen-users@lists.xen.org; Mon, 04 Jan 2016 11:50:44 +0000 Received: from [193.109.254.147] by server-4.bemta-14.messagelabs.com id 0D/07-10715-39C5A865; Mon, 04 Jan 2016 11:50:43 +0000 X-Env-Sender: prvs=8049774f7=Ian.Campbell@citrix.com X-Msg-Ref: server-6.tower-27.messagelabs.com!1451908241!14573402!1 X-Originating-IP: [66.165.176.89] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjYuMTY1LjE3Ni44OSA9PiAyMDMwMDc=\n, received_headers: No Received headers X-StarScan-Received: X-StarScan-Version: 7.35.1; banners=-,-,- X-VirusChecked: Checked Received: (qmail 13595 invoked from network); 4 Jan 2016 11:50:42 -0000 Received: from smtp.citrix.com (HELO SMTP.CITRIX.COM) (66.165.176.89) by server-6.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 4 Jan 2016 11:50:42 -0000 X-IronPort-AV: E=Sophos;i="5.20,520,1444694400"; d="scan'208";a="322702666" Message-ID: <1451908133.13361.44.camel@citrix.com> From: Ian Campbell To: Atul Raut , Date: Mon, 4 Jan 2016 11:48:53 +0000 In-Reply-To: References: X-Mailer: Evolution 3.18.2-1 MIME-Version: 1.0 X-DLP: MIA1 Subject: Re: [Xen-users] DOMu failed to launch X-BeenThere: xen-users@lists.xen.org X-Mailman-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 T24gU3VuLCAyMDE2LTAxLTAzIGF0IDE0OjQ2IC0wODAwLCBBdHVsIFJhdXQgd3JvdGU6Cj4gSGks Cj4gCj4gSSBhbSBnZXR0aW5nIGJlbG93IGVycm9yIGxvZ3Mgb24gRE9NdSBjcmVhdGlvbi4KPiBJ IGFtIHVzaW5nIEFSTXY3IHBsYXRmb3JtICYgWGVuLTQuNi4KPiBEbyBJIG5lZWQgdG8gZW5hYmxl IExQQUUgZm9yIERPTTAgPwoKTm90IGluIGdlbmVyYWwsIHVubGVzcyB0aGUgZG9tYWluIGhhcyA+ NEdCIFJBTS4KCj4gUGxlYXNlIHN1Z2dlc3QgYW55IHBvaW50ZXJzLiAKClBsZWFzZSBwcm92aWRl IHlvdXIgZ3Vlc3QgY2ZnIGZpbGUgYXMgd2VsbCBhcyB0aGUgZnVsbCBvdXRwdXQgb2YgInhsIC12 dnYKY3JlYXRlIDxjZmc+IiAodGhlIC12dnYgbWFrZXMgaXQgdmVyeSB2ZXJib3NlKS4KCj4gCj4g ZG9tYWluYnVpbGRlcjogZGV0YWlsOiBzZXR1cF9wZ3RhYmxlc19hcm06IGNhbGxlZAo+IGRvbWFp bmJ1aWxkZXI6IGRldGFpbDogY2xlYXJfcGFnZTogcGZuIDB4MzkwMDAsIG1mbiAweDM5MDAwCj4g ZG9tYWluYnVpbGRlcjogZGV0YWlsOiBjbGVhcl9wYWdlOiBwZm4gMHgzOTAwMSwgbWZuIDB4Mzkw MDEKPiBkb21haW5idWlsZGVyOiBkZXRhaWw6IHN0YXJ0X2luZm9fYXJtOiBjYWxsZWQKPiBkb21h aW5idWlsZGVyOiBkZXRhaWw6IGRvbWFpbiBidWlsZGVyIG1lbW9yeSBmb290cHJpbnQKPiBkb21h aW5idWlsZGVyOiBkZXRhaWw6wqDCoMKgIGFsbG9jYXRlZAo+IGRvbWFpbmJ1aWxkZXI6IGRldGFp bDrCoMKgwqDCoMKgwqAgbWFsbG9jwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgIDogMzg5IGtCCj4g ZG9tYWluYnVpbGRlcjogZGV0YWlsOsKgwqDCoMKgwqDCoCBhbm9uIG1tYXDCoMKgwqDCoMKgwqDC oMKgwqAgOiAwIGJ5dGVzCj4gZG9tYWluYnVpbGRlcjogZGV0YWlsOsKgwqDCoCBtYXBwZWQKPiBk b21haW5idWlsZGVyOiBkZXRhaWw6wqDCoMKgwqDCoMKgIGZpbGUgbW1hcMKgwqDCoMKgwqDCoMKg wqDCoCA6IDIyMzE0IGtCCj4gZG9tYWluYnVpbGRlcjogZGV0YWlsOsKgwqDCoMKgwqDCoCBkb21V IG1tYXDCoMKgwqDCoMKgwqDCoMKgwqAgOiAyMjMyNCBrQgo+IGRvbWFpbmJ1aWxkZXI6IGRldGFp bDogdmNwdV9hcm02NDogY2FsbGVkCj4gZG9tYWluYnVpbGRlcjogZGV0YWlsOiBEVEIgNDdmZmYw MDAKPiBkb21haW5idWlsZGVyOiBkZXRhaWw6IEluaXRpYWwgc3RhdGUgQ1BTUiAweDFjNSBQQyAw eDQwMDgwMDAwCj4gZG9tYWluYnVpbGRlcjogZGV0YWlsOiBsYXVuY2hfdm06IGNhbGxlZCwgY3R4 dD0weDdmOTAzZGUwMDQKPiBkb21haW5idWlsZGVyOiBkZXRhaWw6IHhjX2RvbV9nbnR0YWJfaHZt X3NlZWQ6IGNhbGxlZCwgcGZuPTB4MzgwMDAKPiBkb21haW5idWlsZGVyOiBkZXRhaWw6IHhjX2Rv bV9yZWxlYXNlOiBjYWxsZWQKPiAoWEVOKSBncmFudF90YWJsZS5jOjQxMTpkMHYxIEJhZCBmbGFn cyAoMCkgb3IgZG9tICgwKS4gKGV4cGVjdGVkIGRvbSAwKQo+IAo+IAo+IAo+IFJlZ2FyZHMsCj4g cmF4Cj4gX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KPiBY ZW4tdXNlcnMgbWFpbGluZyBsaXN0Cj4gWGVuLXVzZXJzQGxpc3RzLnhlbi5vcmcKPiBodHRwOi8v bGlzdHMueGVuLm9yZy94ZW4tdXNlcnMKCl9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f X19fX19fX19fX19fX19fClhlbi11c2VycyBtYWlsaW5nIGxpc3QKWGVuLXVzZXJzQGxpc3RzLnhl bi5vcmcKaHR0cDovL2xpc3RzLnhlbi5vcmcveGVuLXVzZXJz From xen-users-bounces@lists.xen.org Mon Jan 04 11:50:52 2016 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 04 Jan 2016 11:50: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 1aG3ev-00048W-88; Mon, 04 Jan 2016 11:50:45 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1aG3eu-00047c-1O for xen-users@lists.xen.org; Mon, 04 Jan 2016 11:50:44 +0000 Received: from [193.109.254.147] by server-4.bemta-14.messagelabs.com id 0D/07-10715-39C5A865; Mon, 04 Jan 2016 11:50:43 +0000 X-Env-Sender: prvs=8049774f7=Ian.Campbell@citrix.com X-Msg-Ref: server-6.tower-27.messagelabs.com!1451908241!14573402!1 X-Originating-IP: [66.165.176.89] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjYuMTY1LjE3Ni44OSA9PiAyMDMwMDc=\n, received_headers: No Received headers X-StarScan-Received: X-StarScan-Version: 7.35.1; banners=-,-,- X-VirusChecked: Checked Received: (qmail 13595 invoked from network); 4 Jan 2016 11:50:42 -0000 Received: from smtp.citrix.com (HELO SMTP.CITRIX.COM) (66.165.176.89) by server-6.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 4 Jan 2016 11:50:42 -0000 X-IronPort-AV: E=Sophos;i="5.20,520,1444694400"; d="scan'208";a="322702666" Message-ID: <1451908133.13361.44.camel@citrix.com> From: Ian Campbell To: Atul Raut , Date: Mon, 4 Jan 2016 11:48:53 +0000 In-Reply-To: References: X-Mailer: Evolution 3.18.2-1 MIME-Version: 1.0 X-DLP: MIA1 Subject: Re: [Xen-users] DOMu failed to launch X-BeenThere: xen-users@lists.xen.org X-Mailman-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 T24gU3VuLCAyMDE2LTAxLTAzIGF0IDE0OjQ2IC0wODAwLCBBdHVsIFJhdXQgd3JvdGU6Cj4gSGks Cj4gCj4gSSBhbSBnZXR0aW5nIGJlbG93IGVycm9yIGxvZ3Mgb24gRE9NdSBjcmVhdGlvbi4KPiBJ IGFtIHVzaW5nIEFSTXY3IHBsYXRmb3JtICYgWGVuLTQuNi4KPiBEbyBJIG5lZWQgdG8gZW5hYmxl IExQQUUgZm9yIERPTTAgPwoKTm90IGluIGdlbmVyYWwsIHVubGVzcyB0aGUgZG9tYWluIGhhcyA+ NEdCIFJBTS4KCj4gUGxlYXNlIHN1Z2dlc3QgYW55IHBvaW50ZXJzLiAKClBsZWFzZSBwcm92aWRl IHlvdXIgZ3Vlc3QgY2ZnIGZpbGUgYXMgd2VsbCBhcyB0aGUgZnVsbCBvdXRwdXQgb2YgInhsIC12 dnYKY3JlYXRlIDxjZmc+IiAodGhlIC12dnYgbWFrZXMgaXQgdmVyeSB2ZXJib3NlKS4KCj4gCj4g ZG9tYWluYnVpbGRlcjogZGV0YWlsOiBzZXR1cF9wZ3RhYmxlc19hcm06IGNhbGxlZAo+IGRvbWFp bmJ1aWxkZXI6IGRldGFpbDogY2xlYXJfcGFnZTogcGZuIDB4MzkwMDAsIG1mbiAweDM5MDAwCj4g ZG9tYWluYnVpbGRlcjogZGV0YWlsOiBjbGVhcl9wYWdlOiBwZm4gMHgzOTAwMSwgbWZuIDB4Mzkw MDEKPiBkb21haW5idWlsZGVyOiBkZXRhaWw6IHN0YXJ0X2luZm9fYXJtOiBjYWxsZWQKPiBkb21h aW5idWlsZGVyOiBkZXRhaWw6IGRvbWFpbiBidWlsZGVyIG1lbW9yeSBmb290cHJpbnQKPiBkb21h aW5idWlsZGVyOiBkZXRhaWw6wqDCoMKgIGFsbG9jYXRlZAo+IGRvbWFpbmJ1aWxkZXI6IGRldGFp bDrCoMKgwqDCoMKgwqAgbWFsbG9jwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgIDogMzg5IGtCCj4g ZG9tYWluYnVpbGRlcjogZGV0YWlsOsKgwqDCoMKgwqDCoCBhbm9uIG1tYXDCoMKgwqDCoMKgwqDC oMKgwqAgOiAwIGJ5dGVzCj4gZG9tYWluYnVpbGRlcjogZGV0YWlsOsKgwqDCoCBtYXBwZWQKPiBk b21haW5idWlsZGVyOiBkZXRhaWw6wqDCoMKgwqDCoMKgIGZpbGUgbW1hcMKgwqDCoMKgwqDCoMKg wqDCoCA6IDIyMzE0IGtCCj4gZG9tYWluYnVpbGRlcjogZGV0YWlsOsKgwqDCoMKgwqDCoCBkb21V IG1tYXDCoMKgwqDCoMKgwqDCoMKgwqAgOiAyMjMyNCBrQgo+IGRvbWFpbmJ1aWxkZXI6IGRldGFp bDogdmNwdV9hcm02NDogY2FsbGVkCj4gZG9tYWluYnVpbGRlcjogZGV0YWlsOiBEVEIgNDdmZmYw MDAKPiBkb21haW5idWlsZGVyOiBkZXRhaWw6IEluaXRpYWwgc3RhdGUgQ1BTUiAweDFjNSBQQyAw eDQwMDgwMDAwCj4gZG9tYWluYnVpbGRlcjogZGV0YWlsOiBsYXVuY2hfdm06IGNhbGxlZCwgY3R4 dD0weDdmOTAzZGUwMDQKPiBkb21haW5idWlsZGVyOiBkZXRhaWw6IHhjX2RvbV9nbnR0YWJfaHZt X3NlZWQ6IGNhbGxlZCwgcGZuPTB4MzgwMDAKPiBkb21haW5idWlsZGVyOiBkZXRhaWw6IHhjX2Rv bV9yZWxlYXNlOiBjYWxsZWQKPiAoWEVOKSBncmFudF90YWJsZS5jOjQxMTpkMHYxIEJhZCBmbGFn cyAoMCkgb3IgZG9tICgwKS4gKGV4cGVjdGVkIGRvbSAwKQo+IAo+IAo+IAo+IFJlZ2FyZHMsCj4g cmF4Cj4gX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KPiBY ZW4tdXNlcnMgbWFpbGluZyBsaXN0Cj4gWGVuLXVzZXJzQGxpc3RzLnhlbi5vcmcKPiBodHRwOi8v bGlzdHMueGVuLm9yZy94ZW4tdXNlcnMKCl9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f X19fX19fX19fX19fX19fClhlbi11c2VycyBtYWlsaW5nIGxpc3QKWGVuLXVzZXJzQGxpc3RzLnhl bi5vcmcKaHR0cDovL2xpc3RzLnhlbi5vcmcveGVuLXVzZXJz From xen-users-bounces@lists.xen.org Mon Jan 04 12:15:53 2016 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 04 Jan 2016 12:15: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 1aG42q-0006J8-5L; Mon, 04 Jan 2016 12:15:28 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1aG42o-0006J3-HE for xen-users@lists.xen.org; Mon, 04 Jan 2016 12:15:26 +0000 Received: from [85.158.137.68] by server-1.bemta-3.messagelabs.com id E0/B8-14715-D526A865; Mon, 04 Jan 2016 12:15:25 +0000 X-Env-Sender: prvs=8049774f7=Ian.Campbell@citrix.com X-Msg-Ref: server-8.tower-31.messagelabs.com!1451909723!13920406!1 X-Originating-IP: [66.165.176.89] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjYuMTY1LjE3Ni44OSA9PiAyMDMwMDc=\n, received_headers: No Received headers X-StarScan-Received: X-StarScan-Version: 7.35.1; banners=-,-,- X-VirusChecked: Checked Received: (qmail 9872 invoked from network); 4 Jan 2016 12:15:24 -0000 Received: from smtp.citrix.com (HELO SMTP.CITRIX.COM) (66.165.176.89) by server-8.tower-31.messagelabs.com with RC4-SHA encrypted SMTP; 4 Jan 2016 12:15:24 -0000 X-IronPort-AV: E=Sophos;i="5.20,520,1444694400"; d="scan'208";a="322705968" Message-ID: <1451909615.13361.46.camel@citrix.com> From: Ian Campbell To: Andreas Pflug , Date: Mon, 4 Jan 2016 12:13:35 +0000 In-Reply-To: <568A5BEE.9090808@pse-consulting.de> References: <56812352.8060500@pse-consulting.de> <1451907382.13361.37.camel@citrix.com> <568A5BEE.9090808@pse-consulting.de> X-Mailer: Evolution 3.18.2-1 MIME-Version: 1.0 X-DLP: MIA2 Subject: Re: [Xen-users] Missing libvirt+libxl functionality (Was: Re: Programmatic administration of Xen machines) X-BeenThere: xen-users@lists.xen.org X-Mailman-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 T24gTW9uLCAyMDE2LTAxLTA0IGF0IDEyOjQ3ICswMTAwLCBBbmRyZWFzIFBmbHVnIHdyb3RlOgo+ IEFtIDA0LjAxLjE2IHVtIDEyOjM2IHNjaHJpZWIgSWFuIENhbXBiZWxsOgo+ID4gU29ycnkgdG8g aGlqYWNrIHRoaXMgdGhyZWFkLgo+ID4gCj4gPiBPbiBNb24sIDIwMTUtMTItMjggYXQgMTI6NTYg KzAxMDAsIEFuZHJlYXMgUGZsdWcgd3JvdGU6Cj4gPiA+IEFjdHVhbGx5LCBJIGZpbmQgdmlyc2gg YSBiYWQgaWRlYSBzaW5jZSBpdHMgc3VwcG9ydCBmb3IgdGhlIG5ldyB4bAo+ID4gPiBpbnRlcmZh Y2UgaXNuJ3QgZmVhdHVyZSBjb21wbGV0ZSBhcyB0aGUgb2xkIHhtIGludGVyZmFjZSB3YXMuIEkg aGFkCj4gPiA+IHRvCj4gPiA+IHJlYWxpemUgdGhpcyB0aGUgaGFyZCB3YXkgd2hlbiBteSB2aXJz aCBiYXNlZCBweXRob24gdG9vbHMgZGlkbid0Cj4gPiA+IHdvcmsKPiA+ID4gYXMgZXhwZWN0ZWQg YWZ0ZXIgdXBncmFkaW5nIGZyb20geG0gdG8geGwuCj4gPiBOb3RlIHRoYXQgdmlyc2ggc3BlYWtz IHRvIGxpYnhsIGRpcmVjdGx5LCBub3QgdmlhIHhsLgo+ID4gCj4gPiBQbGVhc2UgY2FuIHlvdSBs aXN0IHRoZSBmdW5jdGlvbmFsaXR5IG9mIGxpYnZpcnQncyBsaWJ4bCBiYWNrZWQgd2hpY2gKPiA+ IGlzCj4gPiBtaXNzaW5nIGNvbXBhcmVkIHRvIHRoZSBvbGQgeGVuZCBiYXNlZCBvbmU/IAo+IAo+ IGxpYnZpcnQgb25seSBoYW5kbGVzIGRvbWFpbnMgY3JlYXRlZCB0aHJvdWdoIGl0LCBpLmUuIHVz aW5nIHhsIGF0IHRoZQo+IHNhbWUgdGltZSBpcyBpbmNvbXBhdGlibGUuIFNpbmNlIGRvbTAgY2Fu J3QgYmUgY3JlYXRlZCB1c2luZyBsaWJ2aXJ0LAo+IGl0J3MgbWlzc2luZyBmcm9tICJ2aXJzaCBs aXN0IiBpbiBhbnkgY2FzZS4KClRoaXMgd29ya3MgZm9yIG1lIHdpdGggYSByZWFzb25hYmx5IG1v ZGVybiBzZXQgb2YgYml0czoKCiAgICByb290QG1hcmlsaXRoLW4wICAgIDp+IyB2aXJzaCBsaXN0 CiAgICDCoElkwqDCoMKgwqBOYW1lwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKg wqDCoMKgwqDCoMKgwqDCoMKgU3RhdGUKICAgIC0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0KICAgIMKgMMKgwqDCoMKgwqBEb21haW4tMMKgwqDCoMKg wqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqBydW5uaW5nCiAgICDCoDEzwqDC oMKgwqBkwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDC oMKgwqDCoMKgcnVubmluZwoKSXQgcHJvYmFibHkgcmVxdWlyZXMgdGhlIGNvcnJlY3QgcnVubmlu ZyBvZiB4ZW4taW5pdC1kb20wIGR1cmluZyBib290CihsaWtlbHkgdmlhIHRoZSB4ZW5jb21tb25z IGluaXRzY3JpcHQpLgoKSSBjb3VsZCBiZWxpZXZlIGl0IHdhcyBicm9rZW4gYXQgc29tZSBwb2lu dCBpbiBoaXN0b3J5IHRob3VnaC4KCj4gIGxpYnZpcnQgc3RvcmVzIGl0cyBvd24gc3RhdGUsIG5v dCB1c2luZyBsaWJ4bC94ZW5zdG9yZSBzdHVmZi4KClBsZWFzZSBjYW4geW91IGVsYWJvcmF0ZS4K Cklhbi4KCl9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fClhl bi11c2VycyBtYWlsaW5nIGxpc3QKWGVuLXVzZXJzQGxpc3RzLnhlbi5vcmcKaHR0cDovL2xpc3Rz Lnhlbi5vcmcveGVuLXVzZXJz From xen-users-bounces@lists.xen.org Mon Jan 04 12:15:53 2016 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 04 Jan 2016 12:15: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 1aG42q-0006J8-5L; Mon, 04 Jan 2016 12:15:28 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1aG42o-0006J3-HE for xen-users@lists.xen.org; Mon, 04 Jan 2016 12:15:26 +0000 Received: from [85.158.137.68] by server-1.bemta-3.messagelabs.com id E0/B8-14715-D526A865; Mon, 04 Jan 2016 12:15:25 +0000 X-Env-Sender: prvs=8049774f7=Ian.Campbell@citrix.com X-Msg-Ref: server-8.tower-31.messagelabs.com!1451909723!13920406!1 X-Originating-IP: [66.165.176.89] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjYuMTY1LjE3Ni44OSA9PiAyMDMwMDc=\n, received_headers: No Received headers X-StarScan-Received: X-StarScan-Version: 7.35.1; banners=-,-,- X-VirusChecked: Checked Received: (qmail 9872 invoked from network); 4 Jan 2016 12:15:24 -0000 Received: from smtp.citrix.com (HELO SMTP.CITRIX.COM) (66.165.176.89) by server-8.tower-31.messagelabs.com with RC4-SHA encrypted SMTP; 4 Jan 2016 12:15:24 -0000 X-IronPort-AV: E=Sophos;i="5.20,520,1444694400"; d="scan'208";a="322705968" Message-ID: <1451909615.13361.46.camel@citrix.com> From: Ian Campbell To: Andreas Pflug , Date: Mon, 4 Jan 2016 12:13:35 +0000 In-Reply-To: <568A5BEE.9090808@pse-consulting.de> References: <56812352.8060500@pse-consulting.de> <1451907382.13361.37.camel@citrix.com> <568A5BEE.9090808@pse-consulting.de> X-Mailer: Evolution 3.18.2-1 MIME-Version: 1.0 X-DLP: MIA2 Subject: Re: [Xen-users] Missing libvirt+libxl functionality (Was: Re: Programmatic administration of Xen machines) X-BeenThere: xen-users@lists.xen.org X-Mailman-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 T24gTW9uLCAyMDE2LTAxLTA0IGF0IDEyOjQ3ICswMTAwLCBBbmRyZWFzIFBmbHVnIHdyb3RlOgo+ IEFtIDA0LjAxLjE2IHVtIDEyOjM2IHNjaHJpZWIgSWFuIENhbXBiZWxsOgo+ID4gU29ycnkgdG8g aGlqYWNrIHRoaXMgdGhyZWFkLgo+ID4gCj4gPiBPbiBNb24sIDIwMTUtMTItMjggYXQgMTI6NTYg KzAxMDAsIEFuZHJlYXMgUGZsdWcgd3JvdGU6Cj4gPiA+IEFjdHVhbGx5LCBJIGZpbmQgdmlyc2gg YSBiYWQgaWRlYSBzaW5jZSBpdHMgc3VwcG9ydCBmb3IgdGhlIG5ldyB4bAo+ID4gPiBpbnRlcmZh Y2UgaXNuJ3QgZmVhdHVyZSBjb21wbGV0ZSBhcyB0aGUgb2xkIHhtIGludGVyZmFjZSB3YXMuIEkg aGFkCj4gPiA+IHRvCj4gPiA+IHJlYWxpemUgdGhpcyB0aGUgaGFyZCB3YXkgd2hlbiBteSB2aXJz aCBiYXNlZCBweXRob24gdG9vbHMgZGlkbid0Cj4gPiA+IHdvcmsKPiA+ID4gYXMgZXhwZWN0ZWQg YWZ0ZXIgdXBncmFkaW5nIGZyb20geG0gdG8geGwuCj4gPiBOb3RlIHRoYXQgdmlyc2ggc3BlYWtz IHRvIGxpYnhsIGRpcmVjdGx5LCBub3QgdmlhIHhsLgo+ID4gCj4gPiBQbGVhc2UgY2FuIHlvdSBs aXN0IHRoZSBmdW5jdGlvbmFsaXR5IG9mIGxpYnZpcnQncyBsaWJ4bCBiYWNrZWQgd2hpY2gKPiA+ IGlzCj4gPiBtaXNzaW5nIGNvbXBhcmVkIHRvIHRoZSBvbGQgeGVuZCBiYXNlZCBvbmU/IAo+IAo+ IGxpYnZpcnQgb25seSBoYW5kbGVzIGRvbWFpbnMgY3JlYXRlZCB0aHJvdWdoIGl0LCBpLmUuIHVz aW5nIHhsIGF0IHRoZQo+IHNhbWUgdGltZSBpcyBpbmNvbXBhdGlibGUuIFNpbmNlIGRvbTAgY2Fu J3QgYmUgY3JlYXRlZCB1c2luZyBsaWJ2aXJ0LAo+IGl0J3MgbWlzc2luZyBmcm9tICJ2aXJzaCBs aXN0IiBpbiBhbnkgY2FzZS4KClRoaXMgd29ya3MgZm9yIG1lIHdpdGggYSByZWFzb25hYmx5IG1v ZGVybiBzZXQgb2YgYml0czoKCiAgICByb290QG1hcmlsaXRoLW4wICAgIDp+IyB2aXJzaCBsaXN0 CiAgICDCoElkwqDCoMKgwqBOYW1lwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKg wqDCoMKgwqDCoMKgwqDCoMKgU3RhdGUKICAgIC0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0KICAgIMKgMMKgwqDCoMKgwqBEb21haW4tMMKgwqDCoMKg wqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqBydW5uaW5nCiAgICDCoDEzwqDC oMKgwqBkwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDC oMKgwqDCoMKgcnVubmluZwoKSXQgcHJvYmFibHkgcmVxdWlyZXMgdGhlIGNvcnJlY3QgcnVubmlu ZyBvZiB4ZW4taW5pdC1kb20wIGR1cmluZyBib290CihsaWtlbHkgdmlhIHRoZSB4ZW5jb21tb25z IGluaXRzY3JpcHQpLgoKSSBjb3VsZCBiZWxpZXZlIGl0IHdhcyBicm9rZW4gYXQgc29tZSBwb2lu dCBpbiBoaXN0b3J5IHRob3VnaC4KCj4gIGxpYnZpcnQgc3RvcmVzIGl0cyBvd24gc3RhdGUsIG5v dCB1c2luZyBsaWJ4bC94ZW5zdG9yZSBzdHVmZi4KClBsZWFzZSBjYW4geW91IGVsYWJvcmF0ZS4K Cklhbi4KCl9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fClhl bi11c2VycyBtYWlsaW5nIGxpc3QKWGVuLXVzZXJzQGxpc3RzLnhlbi5vcmcKaHR0cDovL2xpc3Rz Lnhlbi5vcmcveGVuLXVzZXJz From xen-users-bounces@lists.xen.org Mon Jan 04 12:31:46 2016 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 04 Jan 2016 12: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 1aG4IP-00077I-6H; Mon, 04 Jan 2016 12:31:33 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1aG4IN-000773-5y for xen-users@lists.xen.org; Mon, 04 Jan 2016 12:31:31 +0000 Received: from [85.158.139.211] by server-11.bemta-5.messagelabs.com id 1D/A5-24494-2266A865; Mon, 04 Jan 2016 12:31:30 +0000 X-Env-Sender: pgadmin@pse-consulting.de X-Msg-Ref: server-8.tower-206.messagelabs.com!1451910689!13550733!1 X-Originating-IP: [217.72.192.73] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 7.35.1; banners=-,-,- X-VirusChecked: Checked Received: (qmail 1445 invoked from network); 4 Jan 2016 12:31:29 -0000 Received: from mout.kundenserver.de (HELO mout.kundenserver.de) (217.72.192.73) by server-8.tower-206.messagelabs.com with DHE-RSA-AES256-GCM-SHA384 encrypted SMTP; 4 Jan 2016 12:31:29 -0000 Received: from pse.homenet.org ([88.70.250.61]) by mrelayeu.kundenserver.de (mreue104) with ESMTPSA (Nemesis) id 0MNLx3-1aIZON0u0v-006tcB; Mon, 04 Jan 2016 13:31:22 +0100 Received: from [192.168.0.8] (helo=pse8.fritz.box) by pse.homenet.org with esmtp (Exim 4.84) (envelope-from ) id 1aG4IC-0007RI-Mb; Mon, 04 Jan 2016 13:31:20 +0100 To: Ian Campbell , xen-users@lists.xen.org References: <56812352.8060500@pse-consulting.de> <1451907382.13361.37.camel@citrix.com> <568A5BEE.9090808@pse-consulting.de> <1451909615.13361.46.camel@citrix.com> From: Andreas Pflug X-Enigmail-Draft-Status: N1110 Message-ID: <568A6618.5@pse-consulting.de> Date: Mon, 4 Jan 2016 13:31:20 +0100 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:38.0) Gecko/20100101 Thunderbird/38.5.0 MIME-Version: 1.0 In-Reply-To: <1451909615.13361.46.camel@citrix.com> X-Provags-ID: V03:K0:gVGBmlpd2/3/y/jAe+xlnqHycjwmG16r/IttgcGs451LTSKDpEC oRR0mEx38o9wTUSUg/Daj2ikdfJqiihoHK6QVqrJXgrkFtClOD+EMMadVeoFTC2uncE/RWD nEpJ3MaJkRai6HVY35OW+ZpPGcaGbbje9P5v/s12MZpqP6If7/qnnItIt4GT159AA0q2saA qFUoi3RAZza8U//itfKlA== X-UI-Out-Filterresults: notjunk:1;V01:K0:OU4XDDLyOxQ=:ysklGkpiAcguWvnAntL1oj lf/jGrZxvRqZC8VVLaBdQ6M3kWeCiQj2089ZKIQVcF6trY5jV61CO5muWNkvPmjmZvgjkywQB N62M0OUoHkGmrs7rQqIc/YJplreUCW4VgZamL4txhnIKf3U4ZlYwcAk9db484A79mfQOvoYr8 gZfiwi0/BXzoq9ojSGx62Tl6LakaAdK4dRgHxYdr8gtvdRmrR44nZD82QCY/R+m68hkBW1KlQ EqfbU7ZEBaCpc7TreBlqbA4oQ8mxu02MrzMfRnmqOCEcG3S0J+G6JYtLJwbF+VYiLdmX5029U fkxAHktHuJt9AOMP3Q2rWkrXfhnHPUDqOO03fLMPakjUmzUQp+kTKLgNehQ21CoB80GtSpVmR X2n2iit7PqEcRgAiyY2NerWrhrOISrid2Dzpn9nSCCvr80IwzfKBELu2bGeD21OcEn0RTZzNw qO+2XfdO9/KEBc8h8ElZcbXraWzBzQoIRlBjeE9YJyQ1nlksrUqZOSSWQHNzHnJgW6V7E7Poe vUbMRrd3kh3xgKgmgNw832IGILm+2vGTxPWGm/fqgwCl/X70zS9UL024sEiP+TveZBa8Jsn4P VoSpMHv0cSVld7YOY0c8u36W3uluGcX62788aJXsHbMO5FIWWIty3urHWXA9vLj4XcWvNHLBW qFXeEPTwyB7+F77EBAe4tSUxBsiOAvaI90Ks+zPtjpLXD9AKCEPCaFrqIb2Z471kqv6LDfWkJ J9KVNvAzMOzBRnhB Subject: Re: [Xen-users] Missing libvirt+libxl functionality (Was: Re: Programmatic administration of Xen machines) X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: 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 04.01.16 um 13:13 schrieb Ian Campbell: > On Mon, 2016-01-04 at 12:47 +0100, Andreas Pflug wrote: >> Am 04.01.16 um 12:36 schrieb Ian Campbell: >>> Sorry to hijack this thread. >>> >>> On Mon, 2015-12-28 at 12:56 +0100, Andreas Pflug wrote: >>>> Actually, I find virsh a bad idea since its support for the new xl >>>> interface isn't feature complete as the old xm interface was. I had >>>> to >>>> realize this the hard way when my virsh based python tools didn't >>>> work >>>> as expected after upgrading from xm to xl. >>> Note that virsh speaks to libxl directly, not via xl. >>> >>> Please can you list the functionality of libvirt's libxl backed which >>> is >>> missing compared to the old xend based one? >> libvirt only handles domains created through it, i.e. using xl at the >> same time is incompatible. Since dom0 can't be created using libvirt, >> it's missing from "virsh list" in any case. > This works for me with a reasonably modern set of bits: > > root@marilith-n0 :~# virsh list > Id Name State > ---------------------------------------------------- > 0 Domain-0 running > 13 d running > > It probably requires the correct running of xen-init-dom0 during boot > (likely via the xencommons initscript). > > I could believe it was broken at some point in history though. > >> libvirt stores its own state, not using libxl/xenstore stuff. > Please can you elaborate. I tested on Debian with 4.4.1 and xl toolstack. See the author's blog post: https://blog.xenproject.org/2014/01/17/libvirt-support-for-xens-new-libxenlight-toolstack/ I had even more trouble, e.g. I wasn't able to use non-standard block scripts (neither via /etc/xen/scripts/block-XXX nor via a script parameter) which are mandatory for me. Regards, Andreas > > Ian. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Mon Jan 04 12:31:46 2016 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 04 Jan 2016 12: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 1aG4IP-00077I-6H; Mon, 04 Jan 2016 12:31:33 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1aG4IN-000773-5y for xen-users@lists.xen.org; Mon, 04 Jan 2016 12:31:31 +0000 Received: from [85.158.139.211] by server-11.bemta-5.messagelabs.com id 1D/A5-24494-2266A865; Mon, 04 Jan 2016 12:31:30 +0000 X-Env-Sender: pgadmin@pse-consulting.de X-Msg-Ref: server-8.tower-206.messagelabs.com!1451910689!13550733!1 X-Originating-IP: [217.72.192.73] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 7.35.1; banners=-,-,- X-VirusChecked: Checked Received: (qmail 1445 invoked from network); 4 Jan 2016 12:31:29 -0000 Received: from mout.kundenserver.de (HELO mout.kundenserver.de) (217.72.192.73) by server-8.tower-206.messagelabs.com with DHE-RSA-AES256-GCM-SHA384 encrypted SMTP; 4 Jan 2016 12:31:29 -0000 Received: from pse.homenet.org ([88.70.250.61]) by mrelayeu.kundenserver.de (mreue104) with ESMTPSA (Nemesis) id 0MNLx3-1aIZON0u0v-006tcB; Mon, 04 Jan 2016 13:31:22 +0100 Received: from [192.168.0.8] (helo=pse8.fritz.box) by pse.homenet.org with esmtp (Exim 4.84) (envelope-from ) id 1aG4IC-0007RI-Mb; Mon, 04 Jan 2016 13:31:20 +0100 To: Ian Campbell , xen-users@lists.xen.org References: <56812352.8060500@pse-consulting.de> <1451907382.13361.37.camel@citrix.com> <568A5BEE.9090808@pse-consulting.de> <1451909615.13361.46.camel@citrix.com> From: Andreas Pflug X-Enigmail-Draft-Status: N1110 Message-ID: <568A6618.5@pse-consulting.de> Date: Mon, 4 Jan 2016 13:31:20 +0100 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:38.0) Gecko/20100101 Thunderbird/38.5.0 MIME-Version: 1.0 In-Reply-To: <1451909615.13361.46.camel@citrix.com> X-Provags-ID: V03:K0:gVGBmlpd2/3/y/jAe+xlnqHycjwmG16r/IttgcGs451LTSKDpEC oRR0mEx38o9wTUSUg/Daj2ikdfJqiihoHK6QVqrJXgrkFtClOD+EMMadVeoFTC2uncE/RWD nEpJ3MaJkRai6HVY35OW+ZpPGcaGbbje9P5v/s12MZpqP6If7/qnnItIt4GT159AA0q2saA qFUoi3RAZza8U//itfKlA== X-UI-Out-Filterresults: notjunk:1;V01:K0:OU4XDDLyOxQ=:ysklGkpiAcguWvnAntL1oj lf/jGrZxvRqZC8VVLaBdQ6M3kWeCiQj2089ZKIQVcF6trY5jV61CO5muWNkvPmjmZvgjkywQB N62M0OUoHkGmrs7rQqIc/YJplreUCW4VgZamL4txhnIKf3U4ZlYwcAk9db484A79mfQOvoYr8 gZfiwi0/BXzoq9ojSGx62Tl6LakaAdK4dRgHxYdr8gtvdRmrR44nZD82QCY/R+m68hkBW1KlQ EqfbU7ZEBaCpc7TreBlqbA4oQ8mxu02MrzMfRnmqOCEcG3S0J+G6JYtLJwbF+VYiLdmX5029U fkxAHktHuJt9AOMP3Q2rWkrXfhnHPUDqOO03fLMPakjUmzUQp+kTKLgNehQ21CoB80GtSpVmR X2n2iit7PqEcRgAiyY2NerWrhrOISrid2Dzpn9nSCCvr80IwzfKBELu2bGeD21OcEn0RTZzNw qO+2XfdO9/KEBc8h8ElZcbXraWzBzQoIRlBjeE9YJyQ1nlksrUqZOSSWQHNzHnJgW6V7E7Poe vUbMRrd3kh3xgKgmgNw832IGILm+2vGTxPWGm/fqgwCl/X70zS9UL024sEiP+TveZBa8Jsn4P VoSpMHv0cSVld7YOY0c8u36W3uluGcX62788aJXsHbMO5FIWWIty3urHWXA9vLj4XcWvNHLBW qFXeEPTwyB7+F77EBAe4tSUxBsiOAvaI90Ks+zPtjpLXD9AKCEPCaFrqIb2Z471kqv6LDfWkJ J9KVNvAzMOzBRnhB Subject: Re: [Xen-users] Missing libvirt+libxl functionality (Was: Re: Programmatic administration of Xen machines) X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: 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 04.01.16 um 13:13 schrieb Ian Campbell: > On Mon, 2016-01-04 at 12:47 +0100, Andreas Pflug wrote: >> Am 04.01.16 um 12:36 schrieb Ian Campbell: >>> Sorry to hijack this thread. >>> >>> On Mon, 2015-12-28 at 12:56 +0100, Andreas Pflug wrote: >>>> Actually, I find virsh a bad idea since its support for the new xl >>>> interface isn't feature complete as the old xm interface was. I had >>>> to >>>> realize this the hard way when my virsh based python tools didn't >>>> work >>>> as expected after upgrading from xm to xl. >>> Note that virsh speaks to libxl directly, not via xl. >>> >>> Please can you list the functionality of libvirt's libxl backed which >>> is >>> missing compared to the old xend based one? >> libvirt only handles domains created through it, i.e. using xl at the >> same time is incompatible. Since dom0 can't be created using libvirt, >> it's missing from "virsh list" in any case. > This works for me with a reasonably modern set of bits: > > root@marilith-n0 :~# virsh list > Id Name State > ---------------------------------------------------- > 0 Domain-0 running > 13 d running > > It probably requires the correct running of xen-init-dom0 during boot > (likely via the xencommons initscript). > > I could believe it was broken at some point in history though. > >> libvirt stores its own state, not using libxl/xenstore stuff. > Please can you elaborate. I tested on Debian with 4.4.1 and xl toolstack. See the author's blog post: https://blog.xenproject.org/2014/01/17/libvirt-support-for-xens-new-libxenlight-toolstack/ I had even more trouble, e.g. I wasn't able to use non-standard block scripts (neither via /etc/xen/scripts/block-XXX nor via a script parameter) which are mandatory for me. Regards, Andreas > > Ian. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Mon Jan 04 12:39:55 2016 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 04 Jan 2016 12:39: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 1aG4QB-0007cP-95; Mon, 04 Jan 2016 12:39:35 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1aG4Q9-0007c9-7u; Mon, 04 Jan 2016 12:39:33 +0000 Received: from [85.158.137.68] by server-9.bemta-3.messagelabs.com id 07/F7-03066-4086A865; Mon, 04 Jan 2016 12:39:32 +0000 X-Env-Sender: prvs=8049774f7=Ian.Campbell@citrix.com X-Msg-Ref: server-2.tower-31.messagelabs.com!1451911170!13778481!1 X-Originating-IP: [66.165.176.63] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjYuMTY1LjE3Ni42MyA9PiAzMDYwNDg=\n, received_headers: No Received headers X-StarScan-Received: X-StarScan-Version: 7.35.1; banners=-,-,- X-VirusChecked: Checked Received: (qmail 12731 invoked from network); 4 Jan 2016 12:39:31 -0000 Received: from smtp02.citrix.com (HELO SMTP02.CITRIX.COM) (66.165.176.63) by server-2.tower-31.messagelabs.com with RC4-SHA encrypted SMTP; 4 Jan 2016 12:39:31 -0000 X-IronPort-AV: E=Sophos;i="5.20,520,1444694400"; d="scan'208";a="328839335" Message-ID: <1451911062.13361.60.camel@citrix.com> From: Ian Campbell To: Andreas Pflug , Date: Mon, 4 Jan 2016 12:37:42 +0000 In-Reply-To: <568A6618.5@pse-consulting.de> References: <56812352.8060500@pse-consulting.de> <1451907382.13361.37.camel@citrix.com> <568A5BEE.9090808@pse-consulting.de> <1451909615.13361.46.camel@citrix.com> <568A6618.5@pse-consulting.de> X-Mailer: Evolution 3.18.2-1 MIME-Version: 1.0 X-DLP: MIA1 Cc: Jim Fehlig , xen-devel Subject: Re: [Xen-users] Missing libvirt+libxl functionality (Was: Re: Programmatic administration of Xen machines) X-BeenThere: xen-users@lists.xen.org X-Mailman-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 T24gTW9uLCAyMDE2LTAxLTA0IGF0IDEzOjMxICswMTAwLCBBbmRyZWFzIFBmbHVnIHdyb3RlOgo+ IEFtIDA0LjAxLjE2IHVtIDEzOjEzIHNjaHJpZWIgSWFuIENhbXBiZWxsOgo+ID4gT24gTW9uLCAy MDE2LTAxLTA0IGF0IDEyOjQ3ICswMTAwLCBBbmRyZWFzIFBmbHVnIHdyb3RlOgo+ID4gPiBBbSAw NC4wMS4xNiB1bSAxMjozNiBzY2hyaWViIElhbiBDYW1wYmVsbDoKPiA+ID4gPiBTb3JyeSB0byBo aWphY2sgdGhpcyB0aHJlYWQuCj4gPiA+ID4gCj4gPiA+ID4gT24gTW9uLCAyMDE1LTEyLTI4IGF0 IDEyOjU2ICswMTAwLCBBbmRyZWFzIFBmbHVnIHdyb3RlOgo+ID4gPiA+ID4gQWN0dWFsbHksIEkg ZmluZCB2aXJzaCBhIGJhZCBpZGVhIHNpbmNlIGl0cyBzdXBwb3J0IGZvciB0aGUgbmV3Cj4gPiA+ ID4gPiB4bAo+ID4gPiA+ID4gaW50ZXJmYWNlIGlzbid0IGZlYXR1cmUgY29tcGxldGUgYXMgdGhl IG9sZCB4bSBpbnRlcmZhY2Ugd2FzLiBJCj4gPiA+ID4gPiBoYWQKPiA+ID4gPiA+IHRvCj4gPiA+ ID4gPiByZWFsaXplIHRoaXMgdGhlIGhhcmQgd2F5IHdoZW4gbXkgdmlyc2ggYmFzZWQgcHl0aG9u IHRvb2xzIGRpZG4ndAo+ID4gPiA+ID4gd29yawo+ID4gPiA+ID4gYXMgZXhwZWN0ZWQgYWZ0ZXIg dXBncmFkaW5nIGZyb20geG0gdG8geGwuCj4gPiA+ID4gTm90ZSB0aGF0IHZpcnNoIHNwZWFrcyB0 byBsaWJ4bCBkaXJlY3RseSwgbm90IHZpYSB4bC4KPiA+ID4gPiAKPiA+ID4gPiBQbGVhc2UgY2Fu IHlvdSBsaXN0IHRoZSBmdW5jdGlvbmFsaXR5IG9mIGxpYnZpcnQncyBsaWJ4bCBiYWNrZWQKPiA+ ID4gPiB3aGljaAo+ID4gPiA+IGlzCj4gPiA+ID4gbWlzc2luZyBjb21wYXJlZCB0byB0aGUgb2xk IHhlbmQgYmFzZWQgb25lPyAKPiA+ID4gbGlidmlydCBvbmx5IGhhbmRsZXMgZG9tYWlucyBjcmVh dGVkIHRocm91Z2ggaXQsIGkuZS4gdXNpbmcgeGwgYXQgdGhlCj4gPiA+IHNhbWUgdGltZSBpcyBp bmNvbXBhdGlibGUuIFNpbmNlIGRvbTAgY2FuJ3QgYmUgY3JlYXRlZCB1c2luZyBsaWJ2aXJ0LAo+ ID4gPiBpdCdzIG1pc3NpbmcgZnJvbSAidmlyc2ggbGlzdCIgaW4gYW55IGNhc2UuCj4gPiBUaGlz IHdvcmtzIGZvciBtZSB3aXRoIGEgcmVhc29uYWJseSBtb2Rlcm4gc2V0IG9mIGJpdHM6Cj4gPiAK PiA+IMKgwqDCoMKgcm9vdEBtYXJpbGl0aC1uMMKgwqDCoMKgOn4jIHZpcnNoIGxpc3QKPiA+IMKg wqDCoMKgwqBJZMKgwqDCoMKgTmFtZcKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDC oMKgwqDCoMKgwqDCoMKgwqDCoFN0YXRlCj4gPiDCoMKgwqDCoC0tLS0tLS0tLS0tLS0tLS0tLS0t LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0KPiA+IMKgwqDCoMKgwqAwwqDCoMKgwqDC oERvbWFpbi0wwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoHJ1 bm5pbmcKPiA+IMKgwqDCoMKgwqAxM8KgwqDCoMKgZMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKg wqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoHJ1bm5pbmcKPiA+IAo+ID4gSXQgcHJv YmFibHkgcmVxdWlyZXMgdGhlIGNvcnJlY3QgcnVubmluZyBvZiB4ZW4taW5pdC1kb20wIGR1cmlu ZyBib290Cj4gPiAobGlrZWx5IHZpYSB0aGUgeGVuY29tbW9ucyBpbml0c2NyaXB0KS4KPiA+IAo+ ID4gSSBjb3VsZCBiZWxpZXZlIGl0IHdhcyBicm9rZW4gYXQgc29tZSBwb2ludCBpbiBoaXN0b3J5 IHRob3VnaC4KPiA+IAo+ID4gPiDCoGxpYnZpcnQgc3RvcmVzIGl0cyBvd24gc3RhdGUsIG5vdCB1 c2luZyBsaWJ4bC94ZW5zdG9yZSBzdHVmZi4KPiA+IFBsZWFzZSBjYW4geW91IGVsYWJvcmF0ZS4K PiBJIHRlc3RlZCBvbiBEZWJpYW4gd2l0aCA0LjQuMSBhbmQgeGwgdG9vbHN0YWNrLiBTZWUgdGhl IGF1dGhvcidzIGJsb2cKPiBwb3N0Ogo+IGh0dHBzOi8vYmxvZy54ZW5wcm9qZWN0Lm9yZy8yMDE0 LzAxLzE3L2xpYnZpcnQtc3VwcG9ydC1mb3IteGVucy1uZXctCj4gbGlieGVubGlnaHQtdG9vbHN0 YWNrLwoKSSB0aGluayB0aGF0IHBhcnRpY3VsYXIgYXNwZWN0IG9mIHRoZSBibG9nIHBvc3QgaXMg bm8gbG9uZ2VyIHZhbGlkLCBhdApsZWFzdCBBRkFJQ1Qgd2l0aCBtb2Rlcm4gbGlidmlydC4KCj4g SSBoYWQgZXZlbiBtb3JlIHRyb3VibGUsIGUuZy4gSSB3YXNuJ3QgYWJsZSB0byB1c2Ugbm9uLXN0 YW5kYXJkIGJsb2NrCj4gc2NyaXB0cyAobmVpdGhlciB2aWEgL2V0Yy94ZW4vc2NyaXB0cy9ibG9j ay1YWFggbm9yIHZpYSBhIHNjcmlwdAo+IHBhcmFtZXRlcikgd2hpY2ggYXJlIG1hbmRhdG9yeSBm b3IgbWUuCgpMb29raW5nIGF0IHRoZSBjb2RlIGl0IHNlZW1zIGxpa2UgdGhpcyBpcyBzdGlsbCBt aXNzaW5nLgoKQ29weWluZyB0aGUgZGV2ZWwgbGlzdCBhbmQgbWFpbnRhaW5lciBpbiBjYXNlIEkn dmUgZWl0aGVyIG1pc3NlZCBzb21ldGhpbmcKb3IgdGhlcmUgaXMgYSByZWFzb24gZm9yIHRoaXMg KG90aGVyIHRoYW4gInN0aWxsIG9uIHRoZSBUT0RPIGxpc3QiLCB3aGljaCBJCmV4cGVjdCBpcyBt b3N0IGxpa2VseSkuCgpJZiB5b3UgZmluZCBvdGhlciBzaG9ydGNvbWluZ3Mgb2YgbGlidmlydCB3 aXRoIGxpYnhsIHRoZW4gSSBzdXBwb3NlIHRoZQpiZXN0IHdheSB0byBhcHByb2FjaCB0aGVtIHdv dWxkIGJlIHRvIHJlcG9ydCB0aGVtIGFzIGJ1Z3M6CiAgICBodHRwOi8vd2lraS54ZW4ub3JnL3dp a2kvUmVwb3J0aW5nX0J1Z3NfYWdhaW5zdF9YZW4KCihJIGRvbid0IGtub3cgaWYgSmltIG9yIGxp YnZpcnQgcHJlZmVycyBzb21lIG90aGVyIG1lYW5zIG9mIGRvaW5nIHNvKS4KCklhbi4KCl9fX19f X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fClhlbi11c2VycyBtYWls aW5nIGxpc3QKWGVuLXVzZXJzQGxpc3RzLnhlbi5vcmcKaHR0cDovL2xpc3RzLnhlbi5vcmcveGVu LXVzZXJz From xen-users-bounces@lists.xen.org Mon Jan 04 12:39:55 2016 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 04 Jan 2016 12:39: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 1aG4QB-0007cP-95; Mon, 04 Jan 2016 12:39:35 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1aG4Q9-0007c9-7u; Mon, 04 Jan 2016 12:39:33 +0000 Received: from [85.158.137.68] by server-9.bemta-3.messagelabs.com id 07/F7-03066-4086A865; Mon, 04 Jan 2016 12:39:32 +0000 X-Env-Sender: prvs=8049774f7=Ian.Campbell@citrix.com X-Msg-Ref: server-2.tower-31.messagelabs.com!1451911170!13778481!1 X-Originating-IP: [66.165.176.63] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjYuMTY1LjE3Ni42MyA9PiAzMDYwNDg=\n, received_headers: No Received headers X-StarScan-Received: X-StarScan-Version: 7.35.1; banners=-,-,- X-VirusChecked: Checked Received: (qmail 12731 invoked from network); 4 Jan 2016 12:39:31 -0000 Received: from smtp02.citrix.com (HELO SMTP02.CITRIX.COM) (66.165.176.63) by server-2.tower-31.messagelabs.com with RC4-SHA encrypted SMTP; 4 Jan 2016 12:39:31 -0000 X-IronPort-AV: E=Sophos;i="5.20,520,1444694400"; d="scan'208";a="328839335" Message-ID: <1451911062.13361.60.camel@citrix.com> From: Ian Campbell To: Andreas Pflug , Date: Mon, 4 Jan 2016 12:37:42 +0000 In-Reply-To: <568A6618.5@pse-consulting.de> References: <56812352.8060500@pse-consulting.de> <1451907382.13361.37.camel@citrix.com> <568A5BEE.9090808@pse-consulting.de> <1451909615.13361.46.camel@citrix.com> <568A6618.5@pse-consulting.de> X-Mailer: Evolution 3.18.2-1 MIME-Version: 1.0 X-DLP: MIA1 Cc: Jim Fehlig , xen-devel Subject: Re: [Xen-users] Missing libvirt+libxl functionality (Was: Re: Programmatic administration of Xen machines) X-BeenThere: xen-users@lists.xen.org X-Mailman-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 T24gTW9uLCAyMDE2LTAxLTA0IGF0IDEzOjMxICswMTAwLCBBbmRyZWFzIFBmbHVnIHdyb3RlOgo+ IEFtIDA0LjAxLjE2IHVtIDEzOjEzIHNjaHJpZWIgSWFuIENhbXBiZWxsOgo+ID4gT24gTW9uLCAy MDE2LTAxLTA0IGF0IDEyOjQ3ICswMTAwLCBBbmRyZWFzIFBmbHVnIHdyb3RlOgo+ID4gPiBBbSAw NC4wMS4xNiB1bSAxMjozNiBzY2hyaWViIElhbiBDYW1wYmVsbDoKPiA+ID4gPiBTb3JyeSB0byBo aWphY2sgdGhpcyB0aHJlYWQuCj4gPiA+ID4gCj4gPiA+ID4gT24gTW9uLCAyMDE1LTEyLTI4IGF0 IDEyOjU2ICswMTAwLCBBbmRyZWFzIFBmbHVnIHdyb3RlOgo+ID4gPiA+ID4gQWN0dWFsbHksIEkg ZmluZCB2aXJzaCBhIGJhZCBpZGVhIHNpbmNlIGl0cyBzdXBwb3J0IGZvciB0aGUgbmV3Cj4gPiA+ ID4gPiB4bAo+ID4gPiA+ID4gaW50ZXJmYWNlIGlzbid0IGZlYXR1cmUgY29tcGxldGUgYXMgdGhl IG9sZCB4bSBpbnRlcmZhY2Ugd2FzLiBJCj4gPiA+ID4gPiBoYWQKPiA+ID4gPiA+IHRvCj4gPiA+ ID4gPiByZWFsaXplIHRoaXMgdGhlIGhhcmQgd2F5IHdoZW4gbXkgdmlyc2ggYmFzZWQgcHl0aG9u IHRvb2xzIGRpZG4ndAo+ID4gPiA+ID4gd29yawo+ID4gPiA+ID4gYXMgZXhwZWN0ZWQgYWZ0ZXIg dXBncmFkaW5nIGZyb20geG0gdG8geGwuCj4gPiA+ID4gTm90ZSB0aGF0IHZpcnNoIHNwZWFrcyB0 byBsaWJ4bCBkaXJlY3RseSwgbm90IHZpYSB4bC4KPiA+ID4gPiAKPiA+ID4gPiBQbGVhc2UgY2Fu IHlvdSBsaXN0IHRoZSBmdW5jdGlvbmFsaXR5IG9mIGxpYnZpcnQncyBsaWJ4bCBiYWNrZWQKPiA+ ID4gPiB3aGljaAo+ID4gPiA+IGlzCj4gPiA+ID4gbWlzc2luZyBjb21wYXJlZCB0byB0aGUgb2xk IHhlbmQgYmFzZWQgb25lPyAKPiA+ID4gbGlidmlydCBvbmx5IGhhbmRsZXMgZG9tYWlucyBjcmVh dGVkIHRocm91Z2ggaXQsIGkuZS4gdXNpbmcgeGwgYXQgdGhlCj4gPiA+IHNhbWUgdGltZSBpcyBp bmNvbXBhdGlibGUuIFNpbmNlIGRvbTAgY2FuJ3QgYmUgY3JlYXRlZCB1c2luZyBsaWJ2aXJ0LAo+ ID4gPiBpdCdzIG1pc3NpbmcgZnJvbSAidmlyc2ggbGlzdCIgaW4gYW55IGNhc2UuCj4gPiBUaGlz IHdvcmtzIGZvciBtZSB3aXRoIGEgcmVhc29uYWJseSBtb2Rlcm4gc2V0IG9mIGJpdHM6Cj4gPiAK PiA+IMKgwqDCoMKgcm9vdEBtYXJpbGl0aC1uMMKgwqDCoMKgOn4jIHZpcnNoIGxpc3QKPiA+IMKg wqDCoMKgwqBJZMKgwqDCoMKgTmFtZcKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDC oMKgwqDCoMKgwqDCoMKgwqDCoFN0YXRlCj4gPiDCoMKgwqDCoC0tLS0tLS0tLS0tLS0tLS0tLS0t LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0KPiA+IMKgwqDCoMKgwqAwwqDCoMKgwqDC oERvbWFpbi0wwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoHJ1 bm5pbmcKPiA+IMKgwqDCoMKgwqAxM8KgwqDCoMKgZMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKg wqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoHJ1bm5pbmcKPiA+IAo+ID4gSXQgcHJv YmFibHkgcmVxdWlyZXMgdGhlIGNvcnJlY3QgcnVubmluZyBvZiB4ZW4taW5pdC1kb20wIGR1cmlu ZyBib290Cj4gPiAobGlrZWx5IHZpYSB0aGUgeGVuY29tbW9ucyBpbml0c2NyaXB0KS4KPiA+IAo+ ID4gSSBjb3VsZCBiZWxpZXZlIGl0IHdhcyBicm9rZW4gYXQgc29tZSBwb2ludCBpbiBoaXN0b3J5 IHRob3VnaC4KPiA+IAo+ID4gPiDCoGxpYnZpcnQgc3RvcmVzIGl0cyBvd24gc3RhdGUsIG5vdCB1 c2luZyBsaWJ4bC94ZW5zdG9yZSBzdHVmZi4KPiA+IFBsZWFzZSBjYW4geW91IGVsYWJvcmF0ZS4K PiBJIHRlc3RlZCBvbiBEZWJpYW4gd2l0aCA0LjQuMSBhbmQgeGwgdG9vbHN0YWNrLiBTZWUgdGhl IGF1dGhvcidzIGJsb2cKPiBwb3N0Ogo+IGh0dHBzOi8vYmxvZy54ZW5wcm9qZWN0Lm9yZy8yMDE0 LzAxLzE3L2xpYnZpcnQtc3VwcG9ydC1mb3IteGVucy1uZXctCj4gbGlieGVubGlnaHQtdG9vbHN0 YWNrLwoKSSB0aGluayB0aGF0IHBhcnRpY3VsYXIgYXNwZWN0IG9mIHRoZSBibG9nIHBvc3QgaXMg bm8gbG9uZ2VyIHZhbGlkLCBhdApsZWFzdCBBRkFJQ1Qgd2l0aCBtb2Rlcm4gbGlidmlydC4KCj4g SSBoYWQgZXZlbiBtb3JlIHRyb3VibGUsIGUuZy4gSSB3YXNuJ3QgYWJsZSB0byB1c2Ugbm9uLXN0 YW5kYXJkIGJsb2NrCj4gc2NyaXB0cyAobmVpdGhlciB2aWEgL2V0Yy94ZW4vc2NyaXB0cy9ibG9j ay1YWFggbm9yIHZpYSBhIHNjcmlwdAo+IHBhcmFtZXRlcikgd2hpY2ggYXJlIG1hbmRhdG9yeSBm b3IgbWUuCgpMb29raW5nIGF0IHRoZSBjb2RlIGl0IHNlZW1zIGxpa2UgdGhpcyBpcyBzdGlsbCBt aXNzaW5nLgoKQ29weWluZyB0aGUgZGV2ZWwgbGlzdCBhbmQgbWFpbnRhaW5lciBpbiBjYXNlIEkn dmUgZWl0aGVyIG1pc3NlZCBzb21ldGhpbmcKb3IgdGhlcmUgaXMgYSByZWFzb24gZm9yIHRoaXMg KG90aGVyIHRoYW4gInN0aWxsIG9uIHRoZSBUT0RPIGxpc3QiLCB3aGljaCBJCmV4cGVjdCBpcyBt b3N0IGxpa2VseSkuCgpJZiB5b3UgZmluZCBvdGhlciBzaG9ydGNvbWluZ3Mgb2YgbGlidmlydCB3 aXRoIGxpYnhsIHRoZW4gSSBzdXBwb3NlIHRoZQpiZXN0IHdheSB0byBhcHByb2FjaCB0aGVtIHdv dWxkIGJlIHRvIHJlcG9ydCB0aGVtIGFzIGJ1Z3M6CiAgICBodHRwOi8vd2lraS54ZW4ub3JnL3dp a2kvUmVwb3J0aW5nX0J1Z3NfYWdhaW5zdF9YZW4KCihJIGRvbid0IGtub3cgaWYgSmltIG9yIGxp YnZpcnQgcHJlZmVycyBzb21lIG90aGVyIG1lYW5zIG9mIGRvaW5nIHNvKS4KCklhbi4KCl9fX19f X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fClhlbi11c2VycyBtYWls aW5nIGxpc3QKWGVuLXVzZXJzQGxpc3RzLnhlbi5vcmcKaHR0cDovL2xpc3RzLnhlbi5vcmcveGVu LXVzZXJz From xen-users-bounces@lists.xen.org Mon Jan 04 12:45:11 2016 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 04 Jan 2016 12:45:11 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1aG4VP-0008Az-TT; Mon, 04 Jan 2016 12:44:59 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1aG4VN-0008Ap-TD for xen-users@lists.xen.org; Mon, 04 Jan 2016 12:44:58 +0000 Received: from [85.158.139.211] by server-17.bemta-5.messagelabs.com id 06/20-21901-9496A865; Mon, 04 Jan 2016 12:44:57 +0000 X-Env-Sender: prvs=8049774f7=Ian.Campbell@citrix.com X-Msg-Ref: server-11.tower-206.messagelabs.com!1451911495!13816809!1 X-Originating-IP: [66.165.176.89] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjYuMTY1LjE3Ni44OSA9PiAyMDMwMDc=\n, received_headers: No Received headers X-StarScan-Received: X-StarScan-Version: 7.35.1; banners=-,-,- X-VirusChecked: Checked Received: (qmail 47811 invoked from network); 4 Jan 2016 12:44:56 -0000 Received: from smtp.citrix.com (HELO SMTP.CITRIX.COM) (66.165.176.89) by server-11.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 4 Jan 2016 12:44:56 -0000 X-IronPort-AV: E=Sophos;i="5.20,520,1444694400"; d="scan'208";a="322710382" Message-ID: <1451911387.13361.65.camel@citrix.com> From: Ian Campbell To: Carl Patenaude Poulin , Date: Mon, 4 Jan 2016 12:43:07 +0000 In-Reply-To: References: X-Mailer: Evolution 3.18.2-1 MIME-Version: 1.0 X-DLP: MIA1 Subject: Re: [Xen-users] Programmatic administration of Xen machines X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/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, 2015-12-26 at 16:18 -0500, Carl Patenaude Poulin wrote: > Hi all, > > I'd like to programmatically administer Xen machines. Ideally, I'd > need some sort of API or command-line tool that I can use to check > if a domain is paused, collect console output, etc. I started by > using xl, but the output it produces generally isn't suitable for > machine consumption. At least for some options (e.g. xl list) you can request JSON formatted output. For collecting console output you can configure xenconsoled to log all guest output to files under /var/log/xen/console: http://wiki.xen.org/wiki/Reporting_Bugs_against_Xen#Guest_console_logs Not sure if that meets your requirements (this support is independent of the toolstack). > I'm wondering what solution you'd suggest. My first intuition is to > use virsh, is that a good idea? Contrary to what others have said, I think this (both virsh as a CLI and the libvirt RPC interface which underlies it) is a valid avenue to investigate and evaluate against your requirements. libvirt support for Xen via the libxl backend is far more complete than it was a couple of years ago and we think it should be usable for most cases. If you trip across any bugs or missing features then please do report back to us. Ian. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Mon Jan 04 12:45:11 2016 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 04 Jan 2016 12:45:11 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1aG4VP-0008Az-TT; Mon, 04 Jan 2016 12:44:59 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1aG4VN-0008Ap-TD for xen-users@lists.xen.org; Mon, 04 Jan 2016 12:44:58 +0000 Received: from [85.158.139.211] by server-17.bemta-5.messagelabs.com id 06/20-21901-9496A865; Mon, 04 Jan 2016 12:44:57 +0000 X-Env-Sender: prvs=8049774f7=Ian.Campbell@citrix.com X-Msg-Ref: server-11.tower-206.messagelabs.com!1451911495!13816809!1 X-Originating-IP: [66.165.176.89] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjYuMTY1LjE3Ni44OSA9PiAyMDMwMDc=\n, received_headers: No Received headers X-StarScan-Received: X-StarScan-Version: 7.35.1; banners=-,-,- X-VirusChecked: Checked Received: (qmail 47811 invoked from network); 4 Jan 2016 12:44:56 -0000 Received: from smtp.citrix.com (HELO SMTP.CITRIX.COM) (66.165.176.89) by server-11.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 4 Jan 2016 12:44:56 -0000 X-IronPort-AV: E=Sophos;i="5.20,520,1444694400"; d="scan'208";a="322710382" Message-ID: <1451911387.13361.65.camel@citrix.com> From: Ian Campbell To: Carl Patenaude Poulin , Date: Mon, 4 Jan 2016 12:43:07 +0000 In-Reply-To: References: X-Mailer: Evolution 3.18.2-1 MIME-Version: 1.0 X-DLP: MIA1 Subject: Re: [Xen-users] Programmatic administration of Xen machines X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/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, 2015-12-26 at 16:18 -0500, Carl Patenaude Poulin wrote: > Hi all, > > I'd like to programmatically administer Xen machines. Ideally, I'd > need some sort of API or command-line tool that I can use to check > if a domain is paused, collect console output, etc. I started by > using xl, but the output it produces generally isn't suitable for > machine consumption. At least for some options (e.g. xl list) you can request JSON formatted output. For collecting console output you can configure xenconsoled to log all guest output to files under /var/log/xen/console: http://wiki.xen.org/wiki/Reporting_Bugs_against_Xen#Guest_console_logs Not sure if that meets your requirements (this support is independent of the toolstack). > I'm wondering what solution you'd suggest. My first intuition is to > use virsh, is that a good idea? Contrary to what others have said, I think this (both virsh as a CLI and the libvirt RPC interface which underlies it) is a valid avenue to investigate and evaluate against your requirements. libvirt support for Xen via the libxl backend is far more complete than it was a couple of years ago and we think it should be usable for most cases. If you trip across any bugs or missing features then please do report back to us. Ian. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Mon Jan 04 13:00:20 2016 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 04 Jan 2016 13:00: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 1aG4jv-0000gG-Ip; Mon, 04 Jan 2016 12:59:59 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1aG4ju-0000gB-3c for xen-users@lists.xen.org; Mon, 04 Jan 2016 12:59:58 +0000 Received: from [85.158.139.211] by server-4.bemta-5.messagelabs.com id 3E/06-24856-DCC6A865; Mon, 04 Jan 2016 12:59:57 +0000 X-Env-Sender: pgadmin@pse-consulting.de X-Msg-Ref: server-10.tower-206.messagelabs.com!1451912394!13789417!1 X-Originating-IP: [212.227.126.187] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: QmFkIElQOiAyMTIuMjI3LjEyNi4xODcgPT4gNjc1NDE=\n,sa_preprocessor: QmFkIElQOiAyMTIuMjI3LjEyNi4xODcgPT4gNjc1NDE=\n X-StarScan-Received: X-StarScan-Version: 7.35.1; banners=-,-,- X-VirusChecked: Checked Received: (qmail 8164 invoked from network); 4 Jan 2016 12:59:54 -0000 Received: from mout.kundenserver.de (HELO mout.kundenserver.de) (212.227.126.187) by server-10.tower-206.messagelabs.com with DHE-RSA-AES256-GCM-SHA384 encrypted SMTP; 4 Jan 2016 12:59:54 -0000 Received: from pse.homenet.org ([88.70.250.61]) by mrelayeu.kundenserver.de (mreue004) with ESMTPSA (Nemesis) id 0MTKyZ-1ahC7302xL-00SMs4 for ; Mon, 04 Jan 2016 13:59:54 +0100 Received: from [192.168.0.8] (helo=pse8.fritz.box) by pse.homenet.org with esmtp (Exim 4.84) (envelope-from ) id 1aG4jp-0007vO-1m for xen-users@lists.xen.org; Mon, 04 Jan 2016 13:59:53 +0100 To: xen-users@lists.xen.org References: <1451911387.13361.65.camel@citrix.com> From: Andreas Pflug Message-ID: <568A6CC8.3050208@pse-consulting.de> Date: Mon, 4 Jan 2016 13:59:52 +0100 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:38.0) Gecko/20100101 Thunderbird/38.5.0 MIME-Version: 1.0 In-Reply-To: <1451911387.13361.65.camel@citrix.com> X-Provags-ID: V03:K0:a4D6uv6/N/jvUwr9KLJz89gqOr2tSzWjpwGPp5AKbKAbRiTMPOq tf83e1j5vcuhPWPgDshd0nG2BWgxy1FufBu3hOmQR2boDKEKC5zpuXeJS167DaUotHYtZmx j3g8LfZbg5FQVeRksHh1BFfLs7wMlaSJ/UqzOkfoZrmH/pOL3BcWKX9wtAe+jlN7QRi5lQx f0VbJP+aODB9Quk4OCK/w== X-UI-Out-Filterresults: notjunk:1;V01:K0:4RGiQIyB0JU=:a70u3tWi9f4Z+9Si9sZRIw 4E5gZcQ8MPF/F3JFV0hsiF8+BR78QnswBsUzepuh+ZBDw9zSZ6Fp03zl7dDxk0AFLAsdYholq RtqoD6kL3YGP7my7Wdv3ipQk1Ti8jiBWL2EDDzsupKzaK8nRIhkvfDMZbHQrgV16+7i1WSDVV 8LHEfzaREVGL54jRryKkTVE2CcoMNl0nqaVz8OeMHakV1A0ACP9mK/nlzjpBuPutupzu4yv5s lrDIbODx8mZFFLC2qxDc3xnWNPhJV2makRrpk0A3w3mJbRzYofTgAr4/1kNWfHEro5FoRpN0b raO62I6ncfgTkJpOqt73Km4kHoAiZcGdGNescnLPwY/04m2nL2zggNXz2PWXSL29h1SuEKcjK kKPo0XulSfOiV4q9XvAxAHZrfKwLxXQxwYkAJRDnrnakxWrX5npWL/CJ3wqKa3QPbpsQINKta 9MOMFzsyu+EEwh6O7oXPquKrBr7xeljTBAX5AdZSfUJ8eFn6GDIvcSLV3o7ZZ+MxYOV4JOgsS 4h8UZkXohgg9ffsv4bHLOpoY9Ejbta4xqVdXe68Ez3z5qzU0rUKoYvK5r2ByUoGg8/hwz7eos /eGnYtQu1u0doCefojqhCWrTCVfiDCfrMiobuELIGEXnSLVFsE0jIFkcqEgrYoJ+/UMBx7d7p KRj0eXZ7paohIuSkuWaloVjPMcF3cYyFREXfeEH/ucudnwARo/57tHg/QA0tBsdlfQe3a4+Ht et9oO0f0RmW2aW70 Subject: Re: [Xen-users] Programmatic administration of Xen machines X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: 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 04.01.16 um 13:43 schrieb Ian Campbell: > On Sat, 2015-12-26 at 16:18 -0500, Carl Patenaude Poulin wrote: >> Hi all, >> >> I'd like to programmatically administer Xen machines. Ideally, I'd >> need some sort of API or command-line tool that I can use to check >> if a domain is paused, collect console output, etc. I started by >> using xl, but the output it produces generally isn't suitable for >> machine consumption. > At least for some options (e.g. xl list) you can request JSON formatted > output. > > For collecting console output you can configure xenconsoled to log all > guest output to files under /var/log/xen/console: > http://wiki.xen.org/wiki/Reporting_Bugs_against_Xen#Guest_console_logs > Not sure if that meets your requirements (this support is independent of > the toolstack). > >> I'm wondering what solution you'd suggest. My first intuition is to >> use virsh, is that a good idea? > Contrary to what others have said, I think this (both virsh as a CLI and > the libvirt RPC interface which underlies it) is a valid avenue to > investigate and evaluate against your requirements. > > libvirt support for Xen via the libxl backend is far more complete than it > was a couple of years ago and we think it should be usable for most cases. > If you trip across any bugs or missing features then please do report back > to us. Methinks tracking a separate status is a fundamental design flaw. Might have been a little easier to implement initially, but a fine source of headache down the line. Regards, Andreas _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Mon Jan 04 13:00:20 2016 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 04 Jan 2016 13:00: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 1aG4jv-0000gG-Ip; Mon, 04 Jan 2016 12:59:59 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1aG4ju-0000gB-3c for xen-users@lists.xen.org; Mon, 04 Jan 2016 12:59:58 +0000 Received: from [85.158.139.211] by server-4.bemta-5.messagelabs.com id 3E/06-24856-DCC6A865; Mon, 04 Jan 2016 12:59:57 +0000 X-Env-Sender: pgadmin@pse-consulting.de X-Msg-Ref: server-10.tower-206.messagelabs.com!1451912394!13789417!1 X-Originating-IP: [212.227.126.187] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: QmFkIElQOiAyMTIuMjI3LjEyNi4xODcgPT4gNjc1NDE=\n,sa_preprocessor: QmFkIElQOiAyMTIuMjI3LjEyNi4xODcgPT4gNjc1NDE=\n X-StarScan-Received: X-StarScan-Version: 7.35.1; banners=-,-,- X-VirusChecked: Checked Received: (qmail 8164 invoked from network); 4 Jan 2016 12:59:54 -0000 Received: from mout.kundenserver.de (HELO mout.kundenserver.de) (212.227.126.187) by server-10.tower-206.messagelabs.com with DHE-RSA-AES256-GCM-SHA384 encrypted SMTP; 4 Jan 2016 12:59:54 -0000 Received: from pse.homenet.org ([88.70.250.61]) by mrelayeu.kundenserver.de (mreue004) with ESMTPSA (Nemesis) id 0MTKyZ-1ahC7302xL-00SMs4 for ; Mon, 04 Jan 2016 13:59:54 +0100 Received: from [192.168.0.8] (helo=pse8.fritz.box) by pse.homenet.org with esmtp (Exim 4.84) (envelope-from ) id 1aG4jp-0007vO-1m for xen-users@lists.xen.org; Mon, 04 Jan 2016 13:59:53 +0100 To: xen-users@lists.xen.org References: <1451911387.13361.65.camel@citrix.com> From: Andreas Pflug Message-ID: <568A6CC8.3050208@pse-consulting.de> Date: Mon, 4 Jan 2016 13:59:52 +0100 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:38.0) Gecko/20100101 Thunderbird/38.5.0 MIME-Version: 1.0 In-Reply-To: <1451911387.13361.65.camel@citrix.com> X-Provags-ID: V03:K0:a4D6uv6/N/jvUwr9KLJz89gqOr2tSzWjpwGPp5AKbKAbRiTMPOq tf83e1j5vcuhPWPgDshd0nG2BWgxy1FufBu3hOmQR2boDKEKC5zpuXeJS167DaUotHYtZmx j3g8LfZbg5FQVeRksHh1BFfLs7wMlaSJ/UqzOkfoZrmH/pOL3BcWKX9wtAe+jlN7QRi5lQx f0VbJP+aODB9Quk4OCK/w== X-UI-Out-Filterresults: notjunk:1;V01:K0:4RGiQIyB0JU=:a70u3tWi9f4Z+9Si9sZRIw 4E5gZcQ8MPF/F3JFV0hsiF8+BR78QnswBsUzepuh+ZBDw9zSZ6Fp03zl7dDxk0AFLAsdYholq RtqoD6kL3YGP7my7Wdv3ipQk1Ti8jiBWL2EDDzsupKzaK8nRIhkvfDMZbHQrgV16+7i1WSDVV 8LHEfzaREVGL54jRryKkTVE2CcoMNl0nqaVz8OeMHakV1A0ACP9mK/nlzjpBuPutupzu4yv5s lrDIbODx8mZFFLC2qxDc3xnWNPhJV2makRrpk0A3w3mJbRzYofTgAr4/1kNWfHEro5FoRpN0b raO62I6ncfgTkJpOqt73Km4kHoAiZcGdGNescnLPwY/04m2nL2zggNXz2PWXSL29h1SuEKcjK kKPo0XulSfOiV4q9XvAxAHZrfKwLxXQxwYkAJRDnrnakxWrX5npWL/CJ3wqKa3QPbpsQINKta 9MOMFzsyu+EEwh6O7oXPquKrBr7xeljTBAX5AdZSfUJ8eFn6GDIvcSLV3o7ZZ+MxYOV4JOgsS 4h8UZkXohgg9ffsv4bHLOpoY9Ejbta4xqVdXe68Ez3z5qzU0rUKoYvK5r2ByUoGg8/hwz7eos /eGnYtQu1u0doCefojqhCWrTCVfiDCfrMiobuELIGEXnSLVFsE0jIFkcqEgrYoJ+/UMBx7d7p KRj0eXZ7paohIuSkuWaloVjPMcF3cYyFREXfeEH/ucudnwARo/57tHg/QA0tBsdlfQe3a4+Ht et9oO0f0RmW2aW70 Subject: Re: [Xen-users] Programmatic administration of Xen machines X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: 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 04.01.16 um 13:43 schrieb Ian Campbell: > On Sat, 2015-12-26 at 16:18 -0500, Carl Patenaude Poulin wrote: >> Hi all, >> >> I'd like to programmatically administer Xen machines. Ideally, I'd >> need some sort of API or command-line tool that I can use to check >> if a domain is paused, collect console output, etc. I started by >> using xl, but the output it produces generally isn't suitable for >> machine consumption. > At least for some options (e.g. xl list) you can request JSON formatted > output. > > For collecting console output you can configure xenconsoled to log all > guest output to files under /var/log/xen/console: > http://wiki.xen.org/wiki/Reporting_Bugs_against_Xen#Guest_console_logs > Not sure if that meets your requirements (this support is independent of > the toolstack). > >> I'm wondering what solution you'd suggest. My first intuition is to >> use virsh, is that a good idea? > Contrary to what others have said, I think this (both virsh as a CLI and > the libvirt RPC interface which underlies it) is a valid avenue to > investigate and evaluate against your requirements. > > libvirt support for Xen via the libxl backend is far more complete than it > was a couple of years ago and we think it should be usable for most cases. > If you trip across any bugs or missing features then please do report back > to us. Methinks tracking a separate status is a fundamental design flaw. Might have been a little easier to implement initially, but a fine source of headache down the line. Regards, Andreas _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Mon Jan 04 13:40:45 2016 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 04 Jan 2016 13: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 1aG5Mg-0002pH-GW; Mon, 04 Jan 2016 13:40:02 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1aG5Md-0002oQ-VA; Mon, 04 Jan 2016 13:40:00 +0000 Received: from [85.158.137.68] by server-5.bemta-3.messagelabs.com id 6B/A6-07651-F267A865; Mon, 04 Jan 2016 13:39:59 +0000 X-Env-Sender: prvs=8049774f7=Ian.Campbell@citrix.com X-Msg-Ref: server-9.tower-31.messagelabs.com!1451914795!1197649!1 X-Originating-IP: [66.165.176.63] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjYuMTY1LjE3Ni42MyA9PiAzMDYwNDg=\n, received_headers: No Received headers X-StarScan-Received: X-StarScan-Version: 7.35.1; banners=-,-,- X-VirusChecked: Checked Received: (qmail 29094 invoked from network); 4 Jan 2016 13:39:56 -0000 Received: from smtp02.citrix.com (HELO SMTP02.CITRIX.COM) (66.165.176.63) by server-9.tower-31.messagelabs.com with RC4-SHA encrypted SMTP; 4 Jan 2016 13:39:56 -0000 X-IronPort-AV: E=Sophos;i="5.20,520,1444694400"; d="scan'208";a="328848956" Message-ID: <1451914686.13361.91.camel@citrix.com> From: Ian Campbell To: Andre Fucs , Xen-users , xen-devel , Stefano Stabellini , Anthony Perard Date: Mon, 4 Jan 2016 13:38:06 +0000 In-Reply-To: <1434848639.1126606.1450523891769.JavaMail.yahoo@mail.yahoo.com> References: <1450439438.4053.218.camel@citrix.com> <1434848639.1126606.1450523891769.JavaMail.yahoo@mail.yahoo.com> X-Mailer: Evolution 3.18.2-1 MIME-Version: 1.0 X-DLP: MIA2 Subject: Re: [Xen-users] Crashes on image file backed VMs X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org T24gU2F0LCAyMDE1LTEyLTE5IGF0IDExOjE4ICswMDAwLCBBbmRyZSBGdWNzIHdyb3RlOgo+IElh biwKPiAKPiBUaGFua3MgZm9yIHRoZSByZXBseS4gCj4gCj4gY29yZWR1bXBjdGzCoGdiZCBQSURf T0ZfUFJPQ0VTUyBwcmludGVkIHRoZSBmb2xsb3dpbmc6CgpBIFNJR0JVUyBpbiBRRU1VJ3MgYmxr X2hhbmRsZV9yZXF1ZXN0cywgaG93IGV4Y2l0aW5nIQoKQ29weWluZyB4ZW4tZGV2ZWwgYW5kIHNv bWUgcmVsZXZhbnQgbWFpbnRhaW5lcnMsIHN0YXJ0IG9mIHRocmVhZCBpcwpodHRwOi8vbGlzdHMu eGVuLm9yZy9hcmNoaXZlcy9odG1sL3hlbi11c2Vycy8yMDE1LTEyL21zZzAwMDczLmh0bWwKRnJv bSB0aGF0LCB0aGlzIGlzIFhlbiA0LjUuMSBvbiBhcmNoIExpbnV4LgoKQW5kcmUsIGNvdWxkIHlv dSB0YWtlIGEgbG9vayB1bmRlciAvdmFyL2xvZy94ZW4gZm9yIGxvZ3MgcmVsYXRpbmcgdG8gYQpk b21haW4gdG8gd2hpY2ggdGhpcyBoYXMgaGFwcGVuZWQsIGluIHBhcnRpY3VsYXIgdGhlIHFlbXUg bG9nLiBJdCB3b3VsZAphbHNvIGJlIHVzZWZ1bCB0byBzZWUgdGhlIGNvcnJlc3BvbmRpbmcgZ3Vl c3QgY2ZnIGZpbGUgSSBleHBlY3QuCgpJYW4uCgo+IFsuLi5dCgo+IHdhcm5pbmc6IENvdWxkIG5v dCBsb2FkIHNoYXJlZCBsaWJyYXJ5IHN5bWJvbHMgZm9yIGxpbnV4LXZkc28uc28uMS4KPiBEbyB5 b3UgbmVlZCAic2V0IHNvbGliLXNlYXJjaC1wYXRoIiBvciAic2V0IHN5c3Jvb3QiPwo+IFtUaHJl YWQgZGVidWdnaW5nIHVzaW5nIGxpYnRocmVhZF9kYiBlbmFibGVkXQo+IFVzaW5nIGhvc3QgbGli dGhyZWFkX2RiIGxpYnJhcnkgIi91c3IvbGliL2xpYnRocmVhZF9kYi5zby4xIi4KPiBDb3JlIHdh cyBnZW5lcmF0ZWQgYnkgYC91c3IvbGliL3hlbi9iaW4vcWVtdS1zeXN0ZW0taTM4NiAteGVuLWRv bWlkIDExCj4gLWNoYXJkZXYgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAg wqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAK PiDCoCDCoCDCoCDCoCDCoCDCoCDCoHNvY2tldCxpZD1saWJ4bC1jbWQscGEnLgo+IFByb2dyYW0g dGVybWluYXRlZCB3aXRoIHNpZ25hbCBTSUdCVVMsIEJ1cyBlcnJvci4KPiAjMCDCoDB4MDAwMDU1 YjI3NmE2MThmZCBpbiBibGtfaGFuZGxlX3JlcXVlc3RzIChibGtkZXY9MHg1NWIyNzdjNDlhYjAp Cj4gwqAgwqAgYXQgL2hvbWUveGFmdWNzL3hlbi9zcmMveGVuLTQuNS4xL3Rvb2xzL3FlbXUtCj4g eGVuL2h3L2Jsb2NrL3hlbl9kaXNrLmM6Njk5Cj4gNjk5IMKgIMKgIHJwID0gYmxrZGV2LT5yaW5n cy5jb21tb24uc3JpbmctPnJlcV9wcm9kOwo+IFtDdXJyZW50IHRocmVhZCBpcyAxIChUaHJlYWQg MHg3ZjY4ZWQwOTA5YzAgKExXUCAxMDEzNCkpXQo+IChnZGIpIGJ0Cj4gIzAgwqAweDAwMDA1NWIy NzZhNjE4ZmQgaW4gYmxrX2hhbmRsZV9yZXF1ZXN0cyAoYmxrZGV2PTB4NTViMjc3YzQ5YWIwKSBh dAo+IC9ob21lL3hhZnVjcy94ZW4vc3JjL3hlbi00LjUuMS90b29scy9xZW11LXhlbi9ody9ibG9j ay94ZW5fZGlzay5jOjY5OQo+ICMxIMKgYmxrX2JoIChvcGFxdWU9MHg1NWIyNzdjNDlhYjApIGF0 IC9ob21lL3hhZnVjcy94ZW4vc3JjL3hlbi0KPiA0LjUuMS90b29scy9xZW11LXhlbi9ody9ibG9j ay94ZW5fZGlzay5jOjczOAo+ICMyIMKgMHgwMDAwNTViMjc2OWU2MmQzIGluIGFpb19iaF9wb2xs IChjdHg9Y3R4QGVudHJ5PTB4NTViMjc3YzM0NjAwKSBhdAo+IC9ob21lL3hhZnVjcy94ZW4vc3Jj L3hlbi00LjUuMS90b29scy9xZW11LXhlbi9hc3luYy5jOjgxCj4gIzMgwqAweDAwMDA1NWIyNzY5 ZTVlZmMgaW4gYWlvX3BvbGwgKGN0eD0weDU1YjI3N2MzNDYwMCwgYmxvY2tpbmc9YmxvY2tpbmcK PiBAZW50cnk9ZmFsc2UpIGF0IC9ob21lL3hhZnVjcy94ZW4vc3JjL3hlbi00LjUuMS90b29scy9x ZW11LXhlbi9haW8tCj4gcG9zaXguYzoxODgKPiAjNCDCoDB4MDAwMDU1YjI3NjllNjEwMyBpbiBh aW9fY3R4X2Rpc3BhdGNoIChzb3VyY2U9PG9wdGltaXplZCBvdXQ+LAo+IGNhbGxiYWNrPTxvcHRp bWl6ZWQgb3V0PiwgdXNlcl9kYXRhPTxvcHRpbWl6ZWQgb3V0PikKPiDCoCDCoCBhdCAvaG9tZS94 YWZ1Y3MveGVuL3NyYy94ZW4tNC41LjEvdG9vbHMvcWVtdS14ZW4vYXN5bmMuYzoyMTEKPiAjNSDC oDB4MDAwMDdmNjhlYmY5OGRjNyBpbiBnX21haW5fY29udGV4dF9kaXNwYXRjaCAoKSBmcm9tCj4g L3Vzci9saWIvbGliZ2xpYi0yLjAuc28uMAo+ICM2IMKgMHgwMDAwNTViMjc2YjA2NmIxIGluIGds aWJfcG9sbGZkc19wb2xsICgpIGF0Cj4gL2hvbWUveGFmdWNzL3hlbi9zcmMveGVuLTQuNS4xL3Rv b2xzL3FlbXUteGVuL21haW4tbG9vcC5jOjE5MAo+ICM3IMKgb3NfaG9zdF9tYWluX2xvb3Bfd2Fp dCAodGltZW91dD08b3B0aW1pemVkIG91dD4pIGF0Cj4gL2hvbWUveGFmdWNzL3hlbi9zcmMveGVu LTQuNS4xL3Rvb2xzL3FlbXUteGVuL21haW4tbG9vcC5jOjIzNQo+ICM4IMKgbWFpbl9sb29wX3dh aXQgKG5vbmJsb2NraW5nPTxvcHRpbWl6ZWQgb3V0PikgYXQKPiAvaG9tZS94YWZ1Y3MveGVuL3Ny Yy94ZW4tNC41LjEvdG9vbHMvcWVtdS14ZW4vbWFpbi1sb29wLmM6NDg0Cj4gIzkgwqAweDAwMDA1 NWIyNzZiNzdlMDkgaW4gbWFpbl9sb29wICgpIGF0IC9ob21lL3hhZnVjcy94ZW4vc3JjL3hlbi0K PiA0LjUuMS90b29scy9xZW11LXhlbi92bC5jOjIwNTYKPiAjMTAgbWFpbiAoYXJnYz08b3B0aW1p emVkIG91dD4sIGFyZ3Y9PG9wdGltaXplZCBvdXQ+LCBlbnZwPTxvcHRpbWl6ZWQKPiBvdXQ+KSBh dCAvaG9tZS94YWZ1Y3MveGVuL3NyYy94ZW4tNC41LjEvdG9vbHMvcWVtdS14ZW4vdmwuYzo0NTM1 Cj4gKGdkYikgdGhyZWFkIDEKPiBbU3dpdGNoaW5nIHRvIHRocmVhZCAxIChUaHJlYWQgMHg3ZjY4 ZWQwOTA5YzAgKExXUCAxMDEzNCkpXQo+ICMwIMKgMHgwMDAwNTViMjc2YTYxOGZkIGluIGJsa19o YW5kbGVfcmVxdWVzdHMgKGJsa2Rldj0weDU1YjI3N2M0OWFiMCkgYXQKPiAvaG9tZS94YWZ1Y3Mv eGVuL3NyYy94ZW4tNC41LjEvdG9vbHMvcWVtdS14ZW4vaHcvYmxvY2sveGVuX2Rpc2suYzo2OTkK PiA2OTkgwqAgwqAgcnAgPSBibGtkZXYtPnJpbmdzLmNvbW1vbi5zcmluZy0+cmVxX3Byb2Q7Cj4g Cj4gCgpfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXwpYZW4t dXNlcnMgbWFpbGluZyBsaXN0Clhlbi11c2Vyc0BsaXN0cy54ZW4ub3JnCmh0dHA6Ly9saXN0cy54 ZW4ub3JnL3hlbi11c2Vycw== From xen-users-bounces@lists.xen.org Mon Jan 04 13:40:45 2016 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 04 Jan 2016 13: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 1aG5Mg-0002pH-GW; Mon, 04 Jan 2016 13:40:02 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1aG5Md-0002oQ-VA; Mon, 04 Jan 2016 13:40:00 +0000 Received: from [85.158.137.68] by server-5.bemta-3.messagelabs.com id 6B/A6-07651-F267A865; Mon, 04 Jan 2016 13:39:59 +0000 X-Env-Sender: prvs=8049774f7=Ian.Campbell@citrix.com X-Msg-Ref: server-9.tower-31.messagelabs.com!1451914795!1197649!1 X-Originating-IP: [66.165.176.63] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjYuMTY1LjE3Ni42MyA9PiAzMDYwNDg=\n, received_headers: No Received headers X-StarScan-Received: X-StarScan-Version: 7.35.1; banners=-,-,- X-VirusChecked: Checked Received: (qmail 29094 invoked from network); 4 Jan 2016 13:39:56 -0000 Received: from smtp02.citrix.com (HELO SMTP02.CITRIX.COM) (66.165.176.63) by server-9.tower-31.messagelabs.com with RC4-SHA encrypted SMTP; 4 Jan 2016 13:39:56 -0000 X-IronPort-AV: E=Sophos;i="5.20,520,1444694400"; d="scan'208";a="328848956" Message-ID: <1451914686.13361.91.camel@citrix.com> From: Ian Campbell To: Andre Fucs , Xen-users , xen-devel , Stefano Stabellini , Anthony Perard Date: Mon, 4 Jan 2016 13:38:06 +0000 In-Reply-To: <1434848639.1126606.1450523891769.JavaMail.yahoo@mail.yahoo.com> References: <1450439438.4053.218.camel@citrix.com> <1434848639.1126606.1450523891769.JavaMail.yahoo@mail.yahoo.com> X-Mailer: Evolution 3.18.2-1 MIME-Version: 1.0 X-DLP: MIA2 Subject: Re: [Xen-users] Crashes on image file backed VMs X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org T24gU2F0LCAyMDE1LTEyLTE5IGF0IDExOjE4ICswMDAwLCBBbmRyZSBGdWNzIHdyb3RlOgo+IElh biwKPiAKPiBUaGFua3MgZm9yIHRoZSByZXBseS4gCj4gCj4gY29yZWR1bXBjdGzCoGdiZCBQSURf T0ZfUFJPQ0VTUyBwcmludGVkIHRoZSBmb2xsb3dpbmc6CgpBIFNJR0JVUyBpbiBRRU1VJ3MgYmxr X2hhbmRsZV9yZXF1ZXN0cywgaG93IGV4Y2l0aW5nIQoKQ29weWluZyB4ZW4tZGV2ZWwgYW5kIHNv bWUgcmVsZXZhbnQgbWFpbnRhaW5lcnMsIHN0YXJ0IG9mIHRocmVhZCBpcwpodHRwOi8vbGlzdHMu eGVuLm9yZy9hcmNoaXZlcy9odG1sL3hlbi11c2Vycy8yMDE1LTEyL21zZzAwMDczLmh0bWwKRnJv bSB0aGF0LCB0aGlzIGlzIFhlbiA0LjUuMSBvbiBhcmNoIExpbnV4LgoKQW5kcmUsIGNvdWxkIHlv dSB0YWtlIGEgbG9vayB1bmRlciAvdmFyL2xvZy94ZW4gZm9yIGxvZ3MgcmVsYXRpbmcgdG8gYQpk b21haW4gdG8gd2hpY2ggdGhpcyBoYXMgaGFwcGVuZWQsIGluIHBhcnRpY3VsYXIgdGhlIHFlbXUg bG9nLiBJdCB3b3VsZAphbHNvIGJlIHVzZWZ1bCB0byBzZWUgdGhlIGNvcnJlc3BvbmRpbmcgZ3Vl c3QgY2ZnIGZpbGUgSSBleHBlY3QuCgpJYW4uCgo+IFsuLi5dCgo+IHdhcm5pbmc6IENvdWxkIG5v dCBsb2FkIHNoYXJlZCBsaWJyYXJ5IHN5bWJvbHMgZm9yIGxpbnV4LXZkc28uc28uMS4KPiBEbyB5 b3UgbmVlZCAic2V0IHNvbGliLXNlYXJjaC1wYXRoIiBvciAic2V0IHN5c3Jvb3QiPwo+IFtUaHJl YWQgZGVidWdnaW5nIHVzaW5nIGxpYnRocmVhZF9kYiBlbmFibGVkXQo+IFVzaW5nIGhvc3QgbGli dGhyZWFkX2RiIGxpYnJhcnkgIi91c3IvbGliL2xpYnRocmVhZF9kYi5zby4xIi4KPiBDb3JlIHdh cyBnZW5lcmF0ZWQgYnkgYC91c3IvbGliL3hlbi9iaW4vcWVtdS1zeXN0ZW0taTM4NiAteGVuLWRv bWlkIDExCj4gLWNoYXJkZXYgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAg wqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAK PiDCoCDCoCDCoCDCoCDCoCDCoCDCoHNvY2tldCxpZD1saWJ4bC1jbWQscGEnLgo+IFByb2dyYW0g dGVybWluYXRlZCB3aXRoIHNpZ25hbCBTSUdCVVMsIEJ1cyBlcnJvci4KPiAjMCDCoDB4MDAwMDU1 YjI3NmE2MThmZCBpbiBibGtfaGFuZGxlX3JlcXVlc3RzIChibGtkZXY9MHg1NWIyNzdjNDlhYjAp Cj4gwqAgwqAgYXQgL2hvbWUveGFmdWNzL3hlbi9zcmMveGVuLTQuNS4xL3Rvb2xzL3FlbXUtCj4g eGVuL2h3L2Jsb2NrL3hlbl9kaXNrLmM6Njk5Cj4gNjk5IMKgIMKgIHJwID0gYmxrZGV2LT5yaW5n cy5jb21tb24uc3JpbmctPnJlcV9wcm9kOwo+IFtDdXJyZW50IHRocmVhZCBpcyAxIChUaHJlYWQg MHg3ZjY4ZWQwOTA5YzAgKExXUCAxMDEzNCkpXQo+IChnZGIpIGJ0Cj4gIzAgwqAweDAwMDA1NWIy NzZhNjE4ZmQgaW4gYmxrX2hhbmRsZV9yZXF1ZXN0cyAoYmxrZGV2PTB4NTViMjc3YzQ5YWIwKSBh dAo+IC9ob21lL3hhZnVjcy94ZW4vc3JjL3hlbi00LjUuMS90b29scy9xZW11LXhlbi9ody9ibG9j ay94ZW5fZGlzay5jOjY5OQo+ICMxIMKgYmxrX2JoIChvcGFxdWU9MHg1NWIyNzdjNDlhYjApIGF0 IC9ob21lL3hhZnVjcy94ZW4vc3JjL3hlbi0KPiA0LjUuMS90b29scy9xZW11LXhlbi9ody9ibG9j ay94ZW5fZGlzay5jOjczOAo+ICMyIMKgMHgwMDAwNTViMjc2OWU2MmQzIGluIGFpb19iaF9wb2xs IChjdHg9Y3R4QGVudHJ5PTB4NTViMjc3YzM0NjAwKSBhdAo+IC9ob21lL3hhZnVjcy94ZW4vc3Jj L3hlbi00LjUuMS90b29scy9xZW11LXhlbi9hc3luYy5jOjgxCj4gIzMgwqAweDAwMDA1NWIyNzY5 ZTVlZmMgaW4gYWlvX3BvbGwgKGN0eD0weDU1YjI3N2MzNDYwMCwgYmxvY2tpbmc9YmxvY2tpbmcK PiBAZW50cnk9ZmFsc2UpIGF0IC9ob21lL3hhZnVjcy94ZW4vc3JjL3hlbi00LjUuMS90b29scy9x ZW11LXhlbi9haW8tCj4gcG9zaXguYzoxODgKPiAjNCDCoDB4MDAwMDU1YjI3NjllNjEwMyBpbiBh aW9fY3R4X2Rpc3BhdGNoIChzb3VyY2U9PG9wdGltaXplZCBvdXQ+LAo+IGNhbGxiYWNrPTxvcHRp bWl6ZWQgb3V0PiwgdXNlcl9kYXRhPTxvcHRpbWl6ZWQgb3V0PikKPiDCoCDCoCBhdCAvaG9tZS94 YWZ1Y3MveGVuL3NyYy94ZW4tNC41LjEvdG9vbHMvcWVtdS14ZW4vYXN5bmMuYzoyMTEKPiAjNSDC oDB4MDAwMDdmNjhlYmY5OGRjNyBpbiBnX21haW5fY29udGV4dF9kaXNwYXRjaCAoKSBmcm9tCj4g L3Vzci9saWIvbGliZ2xpYi0yLjAuc28uMAo+ICM2IMKgMHgwMDAwNTViMjc2YjA2NmIxIGluIGds aWJfcG9sbGZkc19wb2xsICgpIGF0Cj4gL2hvbWUveGFmdWNzL3hlbi9zcmMveGVuLTQuNS4xL3Rv b2xzL3FlbXUteGVuL21haW4tbG9vcC5jOjE5MAo+ICM3IMKgb3NfaG9zdF9tYWluX2xvb3Bfd2Fp dCAodGltZW91dD08b3B0aW1pemVkIG91dD4pIGF0Cj4gL2hvbWUveGFmdWNzL3hlbi9zcmMveGVu LTQuNS4xL3Rvb2xzL3FlbXUteGVuL21haW4tbG9vcC5jOjIzNQo+ICM4IMKgbWFpbl9sb29wX3dh aXQgKG5vbmJsb2NraW5nPTxvcHRpbWl6ZWQgb3V0PikgYXQKPiAvaG9tZS94YWZ1Y3MveGVuL3Ny Yy94ZW4tNC41LjEvdG9vbHMvcWVtdS14ZW4vbWFpbi1sb29wLmM6NDg0Cj4gIzkgwqAweDAwMDA1 NWIyNzZiNzdlMDkgaW4gbWFpbl9sb29wICgpIGF0IC9ob21lL3hhZnVjcy94ZW4vc3JjL3hlbi0K PiA0LjUuMS90b29scy9xZW11LXhlbi92bC5jOjIwNTYKPiAjMTAgbWFpbiAoYXJnYz08b3B0aW1p emVkIG91dD4sIGFyZ3Y9PG9wdGltaXplZCBvdXQ+LCBlbnZwPTxvcHRpbWl6ZWQKPiBvdXQ+KSBh dCAvaG9tZS94YWZ1Y3MveGVuL3NyYy94ZW4tNC41LjEvdG9vbHMvcWVtdS14ZW4vdmwuYzo0NTM1 Cj4gKGdkYikgdGhyZWFkIDEKPiBbU3dpdGNoaW5nIHRvIHRocmVhZCAxIChUaHJlYWQgMHg3ZjY4 ZWQwOTA5YzAgKExXUCAxMDEzNCkpXQo+ICMwIMKgMHgwMDAwNTViMjc2YTYxOGZkIGluIGJsa19o YW5kbGVfcmVxdWVzdHMgKGJsa2Rldj0weDU1YjI3N2M0OWFiMCkgYXQKPiAvaG9tZS94YWZ1Y3Mv eGVuL3NyYy94ZW4tNC41LjEvdG9vbHMvcWVtdS14ZW4vaHcvYmxvY2sveGVuX2Rpc2suYzo2OTkK PiA2OTkgwqAgwqAgcnAgPSBibGtkZXYtPnJpbmdzLmNvbW1vbi5zcmluZy0+cmVxX3Byb2Q7Cj4g Cj4gCgpfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXwpYZW4t dXNlcnMgbWFpbGluZyBsaXN0Clhlbi11c2Vyc0BsaXN0cy54ZW4ub3JnCmh0dHA6Ly9saXN0cy54 ZW4ub3JnL3hlbi11c2Vycw== From xen-users-bounces@lists.xen.org Mon Jan 04 14:48:51 2016 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 04 Jan 2016 14:48: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 1aG6Qh-0007zQ-V1; Mon, 04 Jan 2016 14:48:15 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1aG6Qf-0007zG-Mq for xen-users@lists.xen.org; Mon, 04 Jan 2016 14:48:13 +0000 Received: from [193.109.254.147] by server-9.bemta-14.messagelabs.com id CD/9F-13475-C268A865; Mon, 04 Jan 2016 14:48:12 +0000 X-Env-Sender: sm8ax1@vfemail.net X-Msg-Ref: server-16.tower-27.messagelabs.com!1451918888!14528714!1 X-Originating-IP: [199.16.11.132] X-SpamReason: No, hits=1.2 required=7.0 tests=BODY_RANDOM_LONG, MAILTO_TO_SPAM_ADDR,MIME_QP_LONG_LINE,RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 7.35.1; banners=-,-,- X-VirusChecked: Checked Received: (qmail 15454 invoked from network); 4 Jan 2016 14:48:09 -0000 Received: from onethreetwo.vfemail.net (HELO vfemail.net) (199.16.11.132) by server-16.tower-27.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 4 Jan 2016 14:48:09 -0000 Received: (qmail 72557 invoked by uid 89); 4 Jan 2016 14:48:08 -0000 Received: from localhost (HELO freequeue.vfemail.net) (127.0.0.1) by localhost with (DHE-RSA-AES256-SHA encrypted) SMTP; 4 Jan 2016 14:48:08 -0000 Received: (qmail 42779 invoked by uid 89); 4 Jan 2016 13:05:26 -0000 Received: by simscan 1.3.1 ppid: 42775, pid: 42777, t: 0.0024s scanners:none Received: from unknown (HELO smtp102-2.vfemail.net) (172.16.100.62) by FreeQueue with SMTP; 4 Jan 2016 13:05:26 -0000 Received: (qmail 11119 invoked by uid 89); 4 Jan 2016 13:05:26 -0000 Received: by simscan 1.4.0 ppid: 11113, pid: 11116, t: 0.0360s scanners:none Received: from unknown (HELO localhost) (c204YXgxQHZmZW1haWwubmV0@172.16.100.137) by 172.16.100.62 with ESMTPA; 4 Jan 2016 13:05:26 -0000 Received: from 46.148.18.34 ([46.148.18.34]) by vfemail.net (Horde Framework) with HTTP; Mon, 04 Jan 2016 07:05:25 -0600 Message-ID: <20160104070525.87995669zhz26hwk@vfemail.net> Date: Mon, 04 Jan 2016 07:05:25 -0600 From: sm8ax1@vfemail.net To: "John Mok" References: <20151230160147.88486qsc1m9vm1kw@vfemail.net> <20160101073625.17404r82zk0rl3qc@vfemail.net> In-Reply-To: MIME-Version: 1.0 Content-Disposition: inline User-Agent: Internet Messaging Program (IMP) H3 (4.2) X-VFEmail-Originating-IP: 46.148.18.34 X-VFEmail-AntiSpam: Notify admin@vfemail.net of any spam, and include VFEmail headers Cc: "xen-users@lists.xen.org" Subject: Re: [Xen-users] PCI Passthrough of iwlwifi adapter into Windows HVM failed to start X-BeenThere: xen-users@lists.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 Quoting "John Mok" : >> From what I understand, some devices can't be reinitialized (and >> won't work) by the DomU driver after they've already been >> initialized on >the Dom0. Blacklisting the module should prevent it >> from being initialized before being passed through to the DomU. > > The driver iwlwifi was compiled as a module and I can see it using > lsmod. The module has been preceeded by the xen-pciback, such that the > xen-pciback is loaded first, and I use the command, xl > pci-assignable-list, and the WiFi PCI device, i.e. 0030:00.0, appears. Even if xen-pciback is loaded first, iwlwifi is probably still binding to and initializing the card until pci-assignable-add rebinds it to xen-pciback. The problem being that iwlwifi might not properly de-initialize the card when it is unloaded. You can check what driver is currently bound to the card with `lspci -v`. If you blacklist iwlwifi on the Dom0, the card's state should be unmodified when it is passed to the DomU. It's a long shot, but it might be worth trying. Also, have you tried passing the card to a Linux HVM? At this point, we don't know if the problem is with the Windows equivalent of xen-pcifront (or the emulated PCI bus; I'm not sure how PCI passthrough works on HVMs exactly), or the hypervisor or xen-pciback. Trying some different DomUs might help us identify a pattern. >> If that doesn't work, it's worth reading this page in full: >> http://wiki.xenproject.org/wiki/Xen_PCI_Passthrough and mentioning >> your distro, >Xen version, and hardware (e.g. whether you have an >> IOMMU or not). > > In Xen 4.0.x, I succeeded to pass through LSI SAS controller to > Windows HVM. I had read through > http://wiki.xenproject.org/wiki/Xen_PCI_Passthrough, and the hardware > ThinkPad x250 has VT-d support in BIOS. > > Any idea why the driver in Windows HVM could not start? > > Thanks a lot. > > John Mok ------------------------------------------------- ONLY AT VFEmail! - Use our Metadata Mitigator to keep your email out of the NSA's hands! $24.95 ONETIME Lifetime accounts with Privacy Features! 15GB disk! No bandwidth quotas! Commercial and Bulk Mail Options! _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Mon Jan 04 14:48:51 2016 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 04 Jan 2016 14:48: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 1aG6Qh-0007zQ-V1; Mon, 04 Jan 2016 14:48:15 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1aG6Qf-0007zG-Mq for xen-users@lists.xen.org; Mon, 04 Jan 2016 14:48:13 +0000 Received: from [193.109.254.147] by server-9.bemta-14.messagelabs.com id CD/9F-13475-C268A865; Mon, 04 Jan 2016 14:48:12 +0000 X-Env-Sender: sm8ax1@vfemail.net X-Msg-Ref: server-16.tower-27.messagelabs.com!1451918888!14528714!1 X-Originating-IP: [199.16.11.132] X-SpamReason: No, hits=1.2 required=7.0 tests=BODY_RANDOM_LONG, MAILTO_TO_SPAM_ADDR,MIME_QP_LONG_LINE,RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 7.35.1; banners=-,-,- X-VirusChecked: Checked Received: (qmail 15454 invoked from network); 4 Jan 2016 14:48:09 -0000 Received: from onethreetwo.vfemail.net (HELO vfemail.net) (199.16.11.132) by server-16.tower-27.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 4 Jan 2016 14:48:09 -0000 Received: (qmail 72557 invoked by uid 89); 4 Jan 2016 14:48:08 -0000 Received: from localhost (HELO freequeue.vfemail.net) (127.0.0.1) by localhost with (DHE-RSA-AES256-SHA encrypted) SMTP; 4 Jan 2016 14:48:08 -0000 Received: (qmail 42779 invoked by uid 89); 4 Jan 2016 13:05:26 -0000 Received: by simscan 1.3.1 ppid: 42775, pid: 42777, t: 0.0024s scanners:none Received: from unknown (HELO smtp102-2.vfemail.net) (172.16.100.62) by FreeQueue with SMTP; 4 Jan 2016 13:05:26 -0000 Received: (qmail 11119 invoked by uid 89); 4 Jan 2016 13:05:26 -0000 Received: by simscan 1.4.0 ppid: 11113, pid: 11116, t: 0.0360s scanners:none Received: from unknown (HELO localhost) (c204YXgxQHZmZW1haWwubmV0@172.16.100.137) by 172.16.100.62 with ESMTPA; 4 Jan 2016 13:05:26 -0000 Received: from 46.148.18.34 ([46.148.18.34]) by vfemail.net (Horde Framework) with HTTP; Mon, 04 Jan 2016 07:05:25 -0600 Message-ID: <20160104070525.87995669zhz26hwk@vfemail.net> Date: Mon, 04 Jan 2016 07:05:25 -0600 From: sm8ax1@vfemail.net To: "John Mok" References: <20151230160147.88486qsc1m9vm1kw@vfemail.net> <20160101073625.17404r82zk0rl3qc@vfemail.net> In-Reply-To: MIME-Version: 1.0 Content-Disposition: inline User-Agent: Internet Messaging Program (IMP) H3 (4.2) X-VFEmail-Originating-IP: 46.148.18.34 X-VFEmail-AntiSpam: Notify admin@vfemail.net of any spam, and include VFEmail headers Cc: "xen-users@lists.xen.org" Subject: Re: [Xen-users] PCI Passthrough of iwlwifi adapter into Windows HVM failed to start X-BeenThere: xen-users@lists.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 Quoting "John Mok" : >> From what I understand, some devices can't be reinitialized (and >> won't work) by the DomU driver after they've already been >> initialized on >the Dom0. Blacklisting the module should prevent it >> from being initialized before being passed through to the DomU. > > The driver iwlwifi was compiled as a module and I can see it using > lsmod. The module has been preceeded by the xen-pciback, such that the > xen-pciback is loaded first, and I use the command, xl > pci-assignable-list, and the WiFi PCI device, i.e. 0030:00.0, appears. Even if xen-pciback is loaded first, iwlwifi is probably still binding to and initializing the card until pci-assignable-add rebinds it to xen-pciback. The problem being that iwlwifi might not properly de-initialize the card when it is unloaded. You can check what driver is currently bound to the card with `lspci -v`. If you blacklist iwlwifi on the Dom0, the card's state should be unmodified when it is passed to the DomU. It's a long shot, but it might be worth trying. Also, have you tried passing the card to a Linux HVM? At this point, we don't know if the problem is with the Windows equivalent of xen-pcifront (or the emulated PCI bus; I'm not sure how PCI passthrough works on HVMs exactly), or the hypervisor or xen-pciback. Trying some different DomUs might help us identify a pattern. >> If that doesn't work, it's worth reading this page in full: >> http://wiki.xenproject.org/wiki/Xen_PCI_Passthrough and mentioning >> your distro, >Xen version, and hardware (e.g. whether you have an >> IOMMU or not). > > In Xen 4.0.x, I succeeded to pass through LSI SAS controller to > Windows HVM. I had read through > http://wiki.xenproject.org/wiki/Xen_PCI_Passthrough, and the hardware > ThinkPad x250 has VT-d support in BIOS. > > Any idea why the driver in Windows HVM could not start? > > Thanks a lot. > > John Mok ------------------------------------------------- ONLY AT VFEmail! - Use our Metadata Mitigator to keep your email out of the NSA's hands! $24.95 ONETIME Lifetime accounts with Privacy Features! 15GB disk! No bandwidth quotas! Commercial and Bulk Mail Options! _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Mon Jan 04 17:29:10 2016 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 04 Jan 2016 17:29: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 1aG8vg-0006Su-3K; Mon, 04 Jan 2016 17:28:24 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1aG8vd-0006SO-NC; Mon, 04 Jan 2016 17:28:21 +0000 Received: from [193.109.254.147] by server-5.bemta-14.messagelabs.com id 1E/5B-00475-4BBAA865; Mon, 04 Jan 2016 17:28:20 +0000 X-Env-Sender: prvs=80452ccb6=Stefano.Stabellini@citrix.com X-Msg-Ref: server-8.tower-27.messagelabs.com!1451928498!10855411!1 X-Originating-IP: [66.165.176.89] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjYuMTY1LjE3Ni44OSA9PiAyMDMwMDc=\n, received_headers: No Received headers X-StarScan-Received: X-StarScan-Version: 7.35.1; banners=-,-,- X-VirusChecked: Checked Received: (qmail 18252 invoked from network); 4 Jan 2016 17:28:20 -0000 Received: from smtp.citrix.com (HELO SMTP.CITRIX.COM) (66.165.176.89) by server-8.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 4 Jan 2016 17:28:20 -0000 X-IronPort-AV: E=Sophos;i="5.20,521,1444694400"; d="scan'208";a="322775130" Date: Mon, 4 Jan 2016 17:27:38 +0000 From: Stefano Stabellini X-X-Sender: sstabellini@kaball.uk.xensource.com To: Ian Campbell In-Reply-To: <1451914686.13361.91.camel@citrix.com> Message-ID: References: <1450439438.4053.218.camel@citrix.com> <1434848639.1126606.1450523891769.JavaMail.yahoo@mail.yahoo.com> <1451914686.13361.91.camel@citrix.com> User-Agent: Alpine 2.02 (DEB 1266 2009-07-14) MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="1342847746-1325454957-1451928465=:27577" X-DLP: MIA2 Cc: Anthony Perard , Xen-users , Stefano Stabellini , Andre Fucs , xen-devel Subject: Re: [Xen-users] Crashes on image file backed VMs X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --1342847746-1325454957-1451928465=:27577 Content-Type: text/plain; charset="UTF-8" Content-Length: 4172 Content-Transfer-Encoding: quoted-printable On Mon, 4 Jan 2016, Ian Campbell wrote: > On Sat, 2015-12-19 at 11:18 +0000, Andre Fucs wrote: > > Ian, > > > > Thanks for the reply. > > > > coredumpctl=C2=A0gbd PID_OF_PROCESS printed the following: > > A SIGBUS in QEMU's blk_handle_requests, how exciting! > > Copying xen-devel and some relevant maintainers, start of thread is > http://lists.xen.org/archives/html/xen-users/2015-12/msg00073.html > >From that, this is Xen 4.5.1 on arch Linux. > > Andre, could you take a look under /var/log/xen for logs relating to a > domain to which this has happened, in particular the qemu log. It would > also be useful to see the corresponding guest cfg file I expect. It's good that you can reproduce the bug. What kernel are you using in Dom0=3F What underlying storage are you using for the guest VMs (local disk, nfs, iscsi, etc)=3F Can you reproduce the bug with a more recent QEMU=3F For example: git://git.qemu.org/qemu.git v2.5.0 no need to update Xen for this test, just compile QEMU separately, I just do: ./configure --enable-xen --target-list=3Di386-softmmu --disable-kvm make cp i386-softmmu/qemu-system-i386 /usr/lib/xen/bin Thanks for your help! > > [...] > > > warning: Could not load shared library symbols for linux-vdso.so.1. > > Do you need "set solib-search-path" or "set sysroot"=3F > > [Thread debugging using libthread_db enabled] > > Using host libthread_db library "/usr/lib/libthread_db.so.1". > > Core was generated by `/usr/lib/xen/bin/qemu-system-i386 -xen-domid 11 > > -chardev =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=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=A0socket,id=3Dlibxl-cmd,pa'. > > Program terminated with signal SIGBUS, Bus error. > > #0 =C2=A00x000055b276a618fd in blk_handle_requests (blkdev=3D0x55b277c49ab0) > > =C2=A0 =C2=A0 at /home/xafucs/xen/src/xen-4.5.1/tools/qemu- > > xen/hw/block/xen_disk.c:699 > > 699 =C2=A0 =C2=A0 rp =3D blkdev->rings.common.sring->req_prod; > > [Current thread is 1 (Thread 0x7f68ed0909c0 (LWP 10134))] > > (gdb) bt > > #0 =C2=A00x000055b276a618fd in blk_handle_requests (blkdev=3D0x55b277c49ab0) at > > /home/xafucs/xen/src/xen-4.5.1/tools/qemu-xen/hw/block/xen_disk.c:699 > > #1 =C2=A0blk_bh (opaque=3D0x55b277c49ab0) at /home/xafucs/xen/src/xen- > > 4.5.1/tools/qemu-xen/hw/block/xen_disk.c:738 > > #2 =C2=A00x000055b2769e62d3 in aio_bh_poll (ctx=3Dctx@entry=3D0x55b277c34600) at > > /home/xafucs/xen/src/xen-4.5.1/tools/qemu-xen/async.c:81 > > #3 =C2=A00x000055b2769e5efc in aio_poll (ctx=3D0x55b277c34600, blocking=3Dblocking > > @entry=3Dfalse) at /home/xafucs/xen/src/xen-4.5.1/tools/qemu-xen/aio- > > posix.c:188 > > #4 =C2=A00x000055b2769e6103 in aio_ctx_dispatch (source=3D, > > callback=3D, user_data=3D) > > =C2=A0 =C2=A0 at /home/xafucs/xen/src/xen-4.5.1/tools/qemu-xen/async.c:211 > > #5 =C2=A00x00007f68ebf98dc7 in g_main_context_dispatch () from > > /usr/lib/libglib-2.0.so.0 > > #6 =C2=A00x000055b276b066b1 in glib_pollfds_poll () at > > /home/xafucs/xen/src/xen-4.5.1/tools/qemu-xen/main-loop.c:190 > > #7 =C2=A0os_host_main_loop_wait (timeout=3D) at > > /home/xafucs/xen/src/xen-4.5.1/tools/qemu-xen/main-loop.c:235 > > #8 =C2=A0main_loop_wait (nonblocking=3D) at > > /home/xafucs/xen/src/xen-4.5.1/tools/qemu-xen/main-loop.c:484 > > #9 =C2=A00x000055b276b77e09 in main_loop () at /home/xafucs/xen/src/xen- > > 4.5.1/tools/qemu-xen/vl.c:2056 > > #10 main (argc=3D, argv=3D, envp=3D > out>) at /home/xafucs/xen/src/xen-4.5.1/tools/qemu-xen/vl.c:4535 > > (gdb) thread 1 > > [Switching to thread 1 (Thread 0x7f68ed0909c0 (LWP 10134))] > > #0 =C2=A00x000055b276a618fd in blk_handle_requests (blkdev=3D0x55b277c49ab0) at > > /home/xafucs/xen/src/xen-4.5.1/tools/qemu-xen/hw/block/xen_disk.c:699 > > 699 =C2=A0 =C2=A0 rp =3D blkdev->rings.common.sring->req_prod; > > > > > --1342847746-1325454957-1451928465=:27577 Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users --1342847746-1325454957-1451928465=:27577-- From xen-users-bounces@lists.xen.org Mon Jan 04 17:29:10 2016 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 04 Jan 2016 17:29: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 1aG8vg-0006Su-3K; Mon, 04 Jan 2016 17:28:24 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1aG8vd-0006SO-NC; Mon, 04 Jan 2016 17:28:21 +0000 Received: from [193.109.254.147] by server-5.bemta-14.messagelabs.com id 1E/5B-00475-4BBAA865; Mon, 04 Jan 2016 17:28:20 +0000 X-Env-Sender: prvs=80452ccb6=Stefano.Stabellini@citrix.com X-Msg-Ref: server-8.tower-27.messagelabs.com!1451928498!10855411!1 X-Originating-IP: [66.165.176.89] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjYuMTY1LjE3Ni44OSA9PiAyMDMwMDc=\n, received_headers: No Received headers X-StarScan-Received: X-StarScan-Version: 7.35.1; banners=-,-,- X-VirusChecked: Checked Received: (qmail 18252 invoked from network); 4 Jan 2016 17:28:20 -0000 Received: from smtp.citrix.com (HELO SMTP.CITRIX.COM) (66.165.176.89) by server-8.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 4 Jan 2016 17:28:20 -0000 X-IronPort-AV: E=Sophos;i="5.20,521,1444694400"; d="scan'208";a="322775130" Date: Mon, 4 Jan 2016 17:27:38 +0000 From: Stefano Stabellini X-X-Sender: sstabellini@kaball.uk.xensource.com To: Ian Campbell In-Reply-To: <1451914686.13361.91.camel@citrix.com> Message-ID: References: <1450439438.4053.218.camel@citrix.com> <1434848639.1126606.1450523891769.JavaMail.yahoo@mail.yahoo.com> <1451914686.13361.91.camel@citrix.com> User-Agent: Alpine 2.02 (DEB 1266 2009-07-14) MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="1342847746-1325454957-1451928465=:27577" X-DLP: MIA2 Cc: Anthony Perard , Xen-users , Stefano Stabellini , Andre Fucs , xen-devel Subject: Re: [Xen-users] Crashes on image file backed VMs X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --1342847746-1325454957-1451928465=:27577 Content-Type: text/plain; charset="UTF-8" Content-Length: 4172 Content-Transfer-Encoding: quoted-printable On Mon, 4 Jan 2016, Ian Campbell wrote: > On Sat, 2015-12-19 at 11:18 +0000, Andre Fucs wrote: > > Ian, > > > > Thanks for the reply. > > > > coredumpctl=C2=A0gbd PID_OF_PROCESS printed the following: > > A SIGBUS in QEMU's blk_handle_requests, how exciting! > > Copying xen-devel and some relevant maintainers, start of thread is > http://lists.xen.org/archives/html/xen-users/2015-12/msg00073.html > >From that, this is Xen 4.5.1 on arch Linux. > > Andre, could you take a look under /var/log/xen for logs relating to a > domain to which this has happened, in particular the qemu log. It would > also be useful to see the corresponding guest cfg file I expect. It's good that you can reproduce the bug. What kernel are you using in Dom0=3F What underlying storage are you using for the guest VMs (local disk, nfs, iscsi, etc)=3F Can you reproduce the bug with a more recent QEMU=3F For example: git://git.qemu.org/qemu.git v2.5.0 no need to update Xen for this test, just compile QEMU separately, I just do: ./configure --enable-xen --target-list=3Di386-softmmu --disable-kvm make cp i386-softmmu/qemu-system-i386 /usr/lib/xen/bin Thanks for your help! > > [...] > > > warning: Could not load shared library symbols for linux-vdso.so.1. > > Do you need "set solib-search-path" or "set sysroot"=3F > > [Thread debugging using libthread_db enabled] > > Using host libthread_db library "/usr/lib/libthread_db.so.1". > > Core was generated by `/usr/lib/xen/bin/qemu-system-i386 -xen-domid 11 > > -chardev =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=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=A0socket,id=3Dlibxl-cmd,pa'. > > Program terminated with signal SIGBUS, Bus error. > > #0 =C2=A00x000055b276a618fd in blk_handle_requests (blkdev=3D0x55b277c49ab0) > > =C2=A0 =C2=A0 at /home/xafucs/xen/src/xen-4.5.1/tools/qemu- > > xen/hw/block/xen_disk.c:699 > > 699 =C2=A0 =C2=A0 rp =3D blkdev->rings.common.sring->req_prod; > > [Current thread is 1 (Thread 0x7f68ed0909c0 (LWP 10134))] > > (gdb) bt > > #0 =C2=A00x000055b276a618fd in blk_handle_requests (blkdev=3D0x55b277c49ab0) at > > /home/xafucs/xen/src/xen-4.5.1/tools/qemu-xen/hw/block/xen_disk.c:699 > > #1 =C2=A0blk_bh (opaque=3D0x55b277c49ab0) at /home/xafucs/xen/src/xen- > > 4.5.1/tools/qemu-xen/hw/block/xen_disk.c:738 > > #2 =C2=A00x000055b2769e62d3 in aio_bh_poll (ctx=3Dctx@entry=3D0x55b277c34600) at > > /home/xafucs/xen/src/xen-4.5.1/tools/qemu-xen/async.c:81 > > #3 =C2=A00x000055b2769e5efc in aio_poll (ctx=3D0x55b277c34600, blocking=3Dblocking > > @entry=3Dfalse) at /home/xafucs/xen/src/xen-4.5.1/tools/qemu-xen/aio- > > posix.c:188 > > #4 =C2=A00x000055b2769e6103 in aio_ctx_dispatch (source=3D, > > callback=3D, user_data=3D) > > =C2=A0 =C2=A0 at /home/xafucs/xen/src/xen-4.5.1/tools/qemu-xen/async.c:211 > > #5 =C2=A00x00007f68ebf98dc7 in g_main_context_dispatch () from > > /usr/lib/libglib-2.0.so.0 > > #6 =C2=A00x000055b276b066b1 in glib_pollfds_poll () at > > /home/xafucs/xen/src/xen-4.5.1/tools/qemu-xen/main-loop.c:190 > > #7 =C2=A0os_host_main_loop_wait (timeout=3D) at > > /home/xafucs/xen/src/xen-4.5.1/tools/qemu-xen/main-loop.c:235 > > #8 =C2=A0main_loop_wait (nonblocking=3D) at > > /home/xafucs/xen/src/xen-4.5.1/tools/qemu-xen/main-loop.c:484 > > #9 =C2=A00x000055b276b77e09 in main_loop () at /home/xafucs/xen/src/xen- > > 4.5.1/tools/qemu-xen/vl.c:2056 > > #10 main (argc=3D, argv=3D, envp=3D > out>) at /home/xafucs/xen/src/xen-4.5.1/tools/qemu-xen/vl.c:4535 > > (gdb) thread 1 > > [Switching to thread 1 (Thread 0x7f68ed0909c0 (LWP 10134))] > > #0 =C2=A00x000055b276a618fd in blk_handle_requests (blkdev=3D0x55b277c49ab0) at > > /home/xafucs/xen/src/xen-4.5.1/tools/qemu-xen/hw/block/xen_disk.c:699 > > 699 =C2=A0 =C2=A0 rp =3D blkdev->rings.common.sring->req_prod; > > > > > --1342847746-1325454957-1451928465=:27577 Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users --1342847746-1325454957-1451928465=:27577-- From xen-users-bounces@lists.xen.org Mon Jan 04 21:25:29 2016 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 04 Jan 2016 21:25: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 1aGCc7-0006PY-Rr; Mon, 04 Jan 2016 21:24:27 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1aGCc5-0006PM-Ra for xen-users@lists.xen.org; Mon, 04 Jan 2016 21:24:26 +0000 Received: from [193.109.254.147] by server-14.bemta-14.messagelabs.com id 13/B7-07165-903EA865; Mon, 04 Jan 2016 21:24:25 +0000 X-Env-Sender: hultz.jon@solute.us X-Msg-Ref: server-10.tower-27.messagelabs.com!1451942659!14671738!1 X-Originating-IP: [207.46.100.82] X-SpamReason: No, hits=0.8 required=7.0 tests=BODY_RANDOM_LONG, HTML_60_70,HTML_MESSAGE X-StarScan-Received: X-StarScan-Version: 7.35.1; banners=-,-,- X-VirusChecked: Checked Received: (qmail 6271 invoked from network); 4 Jan 2016 21:24:21 -0000 Received: from mail-by2on0082.outbound.protection.outlook.com (HELO na01-by2-obe.outbound.protection.outlook.com) (207.46.100.82) by server-10.tower-27.messagelabs.com with AES256-SHA256 encrypted SMTP; 4 Jan 2016 21:24:21 -0000 Received: from SN1PR0501MB2013.namprd05.prod.outlook.com (10.163.223.30) by SN1PR0501MB2015.namprd05.prod.outlook.com (10.163.227.12) with Microsoft SMTP Server (TLS) id 15.1.361.13; Mon, 4 Jan 2016 21:24:17 +0000 Received: from SN1PR0501MB2013.namprd05.prod.outlook.com ([10.163.223.30]) by SN1PR0501MB2013.namprd05.prod.outlook.com ([10.163.223.30]) with mapi id 15.01.0361.006; Mon, 4 Jan 2016 21:24:17 +0000 From: "Hultz, Jon" To: "xen-users@lists.xen.org" Thread-Topic: EFI booting Thread-Index: AdFHNh5VATkBh6RjSH+8NyBLXh2Bvw== Date: Mon, 4 Jan 2016 21:24:17 +0000 Message-ID: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [68.15.20.31] x-microsoft-exchange-diagnostics: 1; SN1PR0501MB2015; 5:8QEug9AwrCIeDO8Q9UmKFWqjLyqxUJxy8R0iQ87kyFrIRZMKnHFlzoupeioxuaIP1+YuUPzGFy8mbVh5MF++Ez1S5c+QoYfu37O6h4px1IGVCDmlvYvvWhKFqTjGOnyVaIBKJabmnwPx6hsf6gYV/w==; 24:xt0k/rMvLqsJ5uEY74AaSJhxLcMF7eaLQtpc6xWF4I5bJBO2rFAt7LQRG7frcA5puheCBlHm9QI5aEbLHnDRsw0R9tCHuY4Ypf1qF82IdSk= x-microsoft-antispam: UriScan:;BCL:0;PCL:0;RULEID:;SRVR:SN1PR0501MB2015; x-microsoft-antispam-prvs: x-exchange-antispam-report-test: UriScan:; x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(601004)(2401047)(5005006)(8121501046)(520078)(3002001)(10201501046); SRVR:SN1PR0501MB2015; BCL:0; PCL:0; RULEID:; SRVR:SN1PR0501MB2015; x-forefront-prvs: 08118EFC2B x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(6009001)(189002)(41584004)(199003)(586003)(790700001)(19625215002)(2501003)(105586002)(106356001)(50986999)(54356999)(19580395003)(81156007)(5001960100002)(92566002)(101416001)(229853001)(122556002)(107886002)(97736004)(16236675004)(102836003)(189998001)(2351001)(99286002)(5890100001)(76576001)(110136002)(5003600100002)(3846002)(33656002)(19300405004)(10400500002)(74316001)(221733001)(66066001)(6116002)(1220700001)(40100003)(87936001)(5002640100001)(74482002)(15975445007)(5008740100001)(1096002)(5004730100002)(11100500001)(450100001)(2900100001)(77096005)(86362001)(80162004)(80862005); DIR:OUT; SFP:1101; SCL:1; SRVR:SN1PR0501MB2015; H:SN1PR0501MB2013.namprd05.prod.outlook.com; FPR:; SPF:None; PTR:InfoNoRecords; MX:1; A:1; LANG:en; received-spf: None (protection.outlook.com: solute.us does not designate permitted sender hosts) spamdiagnosticoutput: 1:23 spamdiagnosticmetadata: NSPM MIME-Version: 1.0 X-OriginatorOrg: solute.us X-MS-Exchange-CrossTenant-originalarrivaltime: 04 Jan 2016 21:24:17.5104 (UTC) X-MS-Exchange-CrossTenant-fromentityheader: Hosted X-MS-Exchange-CrossTenant-id: abbadff2-c16f-45d3-a093-2c0a01ac3014 X-MS-Exchange-Transport-CrossTenantHeadersStamped: SN1PR0501MB2015 Subject: [Xen-users] EFI booting X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============7501753812833588249==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============7501753812833588249== Content-Language: en-US Content-Type: multipart/alternative; boundary="_000_SN1PR0501MB2013B6EC7867658DB57A3D88FCF20SN1PR0501MB2013_" --_000_SN1PR0501MB2013B6EC7867658DB57A3D88FCF20SN1PR0501MB2013_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hello, I am attempting to run an EFI boot with xen 4.5.2. I have attempted this on= FreeBSD 11 and Ubunut server 14.04. On both OS models upon reboot the serv= er will not find the OS. On ubuntu there is a ramdisk error and no OS found= . While on FreeBSD 11 the OS is not found in /boot/xen. I attempted to install from source code and found that it will come back up= on reboot but when I install xen tools to the latest version the OS is agai= n non-bootable. Is there any support for EFI booting on either of these systems. I cannot f= ind any documentation that supports either of these OS models. This is for a research project and if EFI is not working on either model co= uld someone point me to the article on this Regards, Jon Hultz Network Engineer SOLUTE 4250 Pacific Highway, Suite 211 San Diego, CA 92110 Office (619) 758-9900 Fax (619) 758-9910 CONFIDENTIALITY NOTICE: This e-mail and any attachments are intended solely= for the use of the individual or entity to whom it is addressed. It may co= ntain information that is privileged, confidential and exempt, or protected= from disclosure under applicable law. If the reader of this message is not= the intended recipient or the employee or agent responsible for delivering= it to the intended recipient, you are hereby notified that any review, use= , disclosure, distribution, or copying of this communication is strictly pr= ohibited. If you have received this communication in error, please notify t= he sender immediately and destroy all copies and attachments. --_000_SN1PR0501MB2013B6EC7867658DB57A3D88FCF20SN1PR0501MB2013_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Hello,

I am attempting to run an EFI boot with xe= n 4.5.2. I have attempted this on FreeBSD 11 and Ubunut server 14.04. On bo= th OS models upon reboot the server will not find the OS. On ubuntu there i= s a ramdisk error and no OS found. While on FreeBSD 11 the OS is not found in /boot/xen. 

I attempted to install from source code an= d found that it will come back upon reboot but when I install xen tools to = the latest version the OS is again non-bootable. 

Is there any support for EFI booting on ei= ther of these systems. I cannot find any documentation that supports either= of these OS models. 

This is for a research project and if EFI = is not working on either model could someone point me to the article on thi= s 

 

Regards,

   &n= bsp;            = ;            &n= bsp;            = ;            &n= bsp;  

Jon Hultz

Network Engineer

 

SOLUTE<= /o:p>

4250 Pacific Highwa= y, Suite 211

San Diego, CA 92110=

Office (619) 758-99= 00

Fax (619) 758-9910<= /span>

 <= /o:p>

CONFIDENTIALITY NOTI= CE: This e-mail and any attachments are intended solely for the use of the = individual or entity to whom it is addressed. It may contain information th= at is privileged, confidential and exempt, or protected from disclosure under applicable law. If the reader of this m= essage is not the intended recipient or the employee or agent responsible f= or delivering it to the intended recipient, you are hereby notified that an= y review, use, disclosure, distribution, or copying of this communication is strictly prohibited. If you have recei= ved this communication in error, please notify the sender immediately and d= estroy all copies and attachments.

 

 

--_000_SN1PR0501MB2013B6EC7867658DB57A3D88FCF20SN1PR0501MB2013_-- --===============7501753812833588249== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users --===============7501753812833588249==-- From xen-users-bounces@lists.xen.org Mon Jan 04 21:25:29 2016 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 04 Jan 2016 21:25: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 1aGCc7-0006PY-Rr; Mon, 04 Jan 2016 21:24:27 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1aGCc5-0006PM-Ra for xen-users@lists.xen.org; Mon, 04 Jan 2016 21:24:26 +0000 Received: from [193.109.254.147] by server-14.bemta-14.messagelabs.com id 13/B7-07165-903EA865; Mon, 04 Jan 2016 21:24:25 +0000 X-Env-Sender: hultz.jon@solute.us X-Msg-Ref: server-10.tower-27.messagelabs.com!1451942659!14671738!1 X-Originating-IP: [207.46.100.82] X-SpamReason: No, hits=0.8 required=7.0 tests=BODY_RANDOM_LONG, HTML_60_70,HTML_MESSAGE X-StarScan-Received: X-StarScan-Version: 7.35.1; banners=-,-,- X-VirusChecked: Checked Received: (qmail 6271 invoked from network); 4 Jan 2016 21:24:21 -0000 Received: from mail-by2on0082.outbound.protection.outlook.com (HELO na01-by2-obe.outbound.protection.outlook.com) (207.46.100.82) by server-10.tower-27.messagelabs.com with AES256-SHA256 encrypted SMTP; 4 Jan 2016 21:24:21 -0000 Received: from SN1PR0501MB2013.namprd05.prod.outlook.com (10.163.223.30) by SN1PR0501MB2015.namprd05.prod.outlook.com (10.163.227.12) with Microsoft SMTP Server (TLS) id 15.1.361.13; Mon, 4 Jan 2016 21:24:17 +0000 Received: from SN1PR0501MB2013.namprd05.prod.outlook.com ([10.163.223.30]) by SN1PR0501MB2013.namprd05.prod.outlook.com ([10.163.223.30]) with mapi id 15.01.0361.006; Mon, 4 Jan 2016 21:24:17 +0000 From: "Hultz, Jon" To: "xen-users@lists.xen.org" Thread-Topic: EFI booting Thread-Index: AdFHNh5VATkBh6RjSH+8NyBLXh2Bvw== Date: Mon, 4 Jan 2016 21:24:17 +0000 Message-ID: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [68.15.20.31] x-microsoft-exchange-diagnostics: 1; SN1PR0501MB2015; 5:8QEug9AwrCIeDO8Q9UmKFWqjLyqxUJxy8R0iQ87kyFrIRZMKnHFlzoupeioxuaIP1+YuUPzGFy8mbVh5MF++Ez1S5c+QoYfu37O6h4px1IGVCDmlvYvvWhKFqTjGOnyVaIBKJabmnwPx6hsf6gYV/w==; 24:xt0k/rMvLqsJ5uEY74AaSJhxLcMF7eaLQtpc6xWF4I5bJBO2rFAt7LQRG7frcA5puheCBlHm9QI5aEbLHnDRsw0R9tCHuY4Ypf1qF82IdSk= x-microsoft-antispam: UriScan:;BCL:0;PCL:0;RULEID:;SRVR:SN1PR0501MB2015; x-microsoft-antispam-prvs: x-exchange-antispam-report-test: UriScan:; x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(601004)(2401047)(5005006)(8121501046)(520078)(3002001)(10201501046); SRVR:SN1PR0501MB2015; BCL:0; PCL:0; RULEID:; SRVR:SN1PR0501MB2015; x-forefront-prvs: 08118EFC2B x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(6009001)(189002)(41584004)(199003)(586003)(790700001)(19625215002)(2501003)(105586002)(106356001)(50986999)(54356999)(19580395003)(81156007)(5001960100002)(92566002)(101416001)(229853001)(122556002)(107886002)(97736004)(16236675004)(102836003)(189998001)(2351001)(99286002)(5890100001)(76576001)(110136002)(5003600100002)(3846002)(33656002)(19300405004)(10400500002)(74316001)(221733001)(66066001)(6116002)(1220700001)(40100003)(87936001)(5002640100001)(74482002)(15975445007)(5008740100001)(1096002)(5004730100002)(11100500001)(450100001)(2900100001)(77096005)(86362001)(80162004)(80862005); DIR:OUT; SFP:1101; SCL:1; SRVR:SN1PR0501MB2015; H:SN1PR0501MB2013.namprd05.prod.outlook.com; FPR:; SPF:None; PTR:InfoNoRecords; MX:1; A:1; LANG:en; received-spf: None (protection.outlook.com: solute.us does not designate permitted sender hosts) spamdiagnosticoutput: 1:23 spamdiagnosticmetadata: NSPM MIME-Version: 1.0 X-OriginatorOrg: solute.us X-MS-Exchange-CrossTenant-originalarrivaltime: 04 Jan 2016 21:24:17.5104 (UTC) X-MS-Exchange-CrossTenant-fromentityheader: Hosted X-MS-Exchange-CrossTenant-id: abbadff2-c16f-45d3-a093-2c0a01ac3014 X-MS-Exchange-Transport-CrossTenantHeadersStamped: SN1PR0501MB2015 Subject: [Xen-users] EFI booting X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============7501753812833588249==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============7501753812833588249== Content-Language: en-US Content-Type: multipart/alternative; boundary="_000_SN1PR0501MB2013B6EC7867658DB57A3D88FCF20SN1PR0501MB2013_" --_000_SN1PR0501MB2013B6EC7867658DB57A3D88FCF20SN1PR0501MB2013_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hello, I am attempting to run an EFI boot with xen 4.5.2. I have attempted this on= FreeBSD 11 and Ubunut server 14.04. On both OS models upon reboot the serv= er will not find the OS. On ubuntu there is a ramdisk error and no OS found= . While on FreeBSD 11 the OS is not found in /boot/xen. I attempted to install from source code and found that it will come back up= on reboot but when I install xen tools to the latest version the OS is agai= n non-bootable. Is there any support for EFI booting on either of these systems. I cannot f= ind any documentation that supports either of these OS models. This is for a research project and if EFI is not working on either model co= uld someone point me to the article on this Regards, Jon Hultz Network Engineer SOLUTE 4250 Pacific Highway, Suite 211 San Diego, CA 92110 Office (619) 758-9900 Fax (619) 758-9910 CONFIDENTIALITY NOTICE: This e-mail and any attachments are intended solely= for the use of the individual or entity to whom it is addressed. It may co= ntain information that is privileged, confidential and exempt, or protected= from disclosure under applicable law. If the reader of this message is not= the intended recipient or the employee or agent responsible for delivering= it to the intended recipient, you are hereby notified that any review, use= , disclosure, distribution, or copying of this communication is strictly pr= ohibited. If you have received this communication in error, please notify t= he sender immediately and destroy all copies and attachments. --_000_SN1PR0501MB2013B6EC7867658DB57A3D88FCF20SN1PR0501MB2013_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Hello,

I am attempting to run an EFI boot with xe= n 4.5.2. I have attempted this on FreeBSD 11 and Ubunut server 14.04. On bo= th OS models upon reboot the server will not find the OS. On ubuntu there i= s a ramdisk error and no OS found. While on FreeBSD 11 the OS is not found in /boot/xen. 

I attempted to install from source code an= d found that it will come back upon reboot but when I install xen tools to = the latest version the OS is again non-bootable. 

Is there any support for EFI booting on ei= ther of these systems. I cannot find any documentation that supports either= of these OS models. 

This is for a research project and if EFI = is not working on either model could someone point me to the article on thi= s 

 

Regards,

   &n= bsp;            = ;            &n= bsp;            = ;            &n= bsp;  

Jon Hultz

Network Engineer

 

SOLUTE<= /o:p>

4250 Pacific Highwa= y, Suite 211

San Diego, CA 92110=

Office (619) 758-99= 00

Fax (619) 758-9910<= /span>

 <= /o:p>

CONFIDENTIALITY NOTI= CE: This e-mail and any attachments are intended solely for the use of the = individual or entity to whom it is addressed. It may contain information th= at is privileged, confidential and exempt, or protected from disclosure under applicable law. If the reader of this m= essage is not the intended recipient or the employee or agent responsible f= or delivering it to the intended recipient, you are hereby notified that an= y review, use, disclosure, distribution, or copying of this communication is strictly prohibited. If you have recei= ved this communication in error, please notify the sender immediately and d= estroy all copies and attachments.

 

 

--_000_SN1PR0501MB2013B6EC7867658DB57A3D88FCF20SN1PR0501MB2013_-- --===============7501753812833588249== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users --===============7501753812833588249==-- From xen-users-bounces@lists.xen.org Mon Jan 04 22:31:41 2016 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 04 Jan 2016 22:31: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 1aGDe4-000267-Fh; Mon, 04 Jan 2016 22:30:32 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1aGDe2-000262-Js for xen-users@lists.xen.org; Mon, 04 Jan 2016 22:30:30 +0000 Received: from [85.158.137.68] by server-4.bemta-3.messagelabs.com id AE/FF-09570-582FA865; Mon, 04 Jan 2016 22:30:29 +0000 X-Env-Sender: zir_blazer@hotmail.com X-Msg-Ref: server-15.tower-31.messagelabs.com!1451946627!13592888!1 X-Originating-IP: [65.55.90.99] X-SpamReason: No, hits=1.8 required=7.0 tests=BODY_RANDOM_LONG, FORGED_HOTMAIL_RCVD,HTML_00_10,HTML_MESSAGE X-StarScan-Received: X-StarScan-Version: 7.35.1; banners=-,-,- X-VirusChecked: Checked Received: (qmail 4674 invoked from network); 4 Jan 2016 22:30:28 -0000 Received: from snt004-omc2s24.hotmail.com (HELO SNT004-OMC2S24.hotmail.com) (65.55.90.99) by server-15.tower-31.messagelabs.com with AES256-SHA256 encrypted SMTP; 4 Jan 2016 22:30:28 -0000 Received: from SNT151-W61 ([65.55.90.72]) by SNT004-OMC2S24.hotmail.com over TLS secured channel with Microsoft SMTPSVC(7.5.7601.23008); Mon, 4 Jan 2016 14:30:26 -0800 X-TMN: [BhE54uhAjTUhldGChCePVYFi77kAyL+HvxrDUfhVGB8=] X-Originating-Email: [zir_blazer@hotmail.com] Message-ID: From: Zir Blazer To: "Hultz, Jon" , "xen-users@lists.xen.org" Date: Mon, 4 Jan 2016 19:30:26 -0300 Importance: Normal In-Reply-To: References: MIME-Version: 1.0 X-OriginalArrivalTime: 04 Jan 2016 22:30:26.0915 (UTC) FILETIME=[828B8B30:01D1473F] Subject: Re: [Xen-users] EFI booting X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============7015981420674119176==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============7015981420674119176== Content-Type: multipart/alternative; boundary="_f46d76a2-de46-4766-8341-be53817068c0_" --_f46d76a2-de46-4766-8341-be53817068c0_ Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable >> Hello=2C=0A= >>=0A= >> I am attempting to run an EFI boot with xen 4.5.2. I have attempted this= on FreeBSD 11 and Ubunut server 14.04. On both OS models upon reboot the s= erver will not find the OS. On ubuntu there is a ramdisk=0A= >> error and no OS found. While on FreeBSD 11 the OS is not found in /boot/= xen. =0A= >>=0A= >> I attempted to install from source code and found that it will come back= upon reboot but when I install xen tools to the latest version the OS is a= gain non-bootable. =0A= >>=0A= >> Is there any support for EFI booting on either of these systems. I canno= t find any documentation that supports either of these OS models. =0A= >>=0A= >> This is for a research project and if EFI is not working on either model= could someone point me to the article on this =0A= =0A= =0A= Since its not for Ubuntu=2C I can't really specifically help you=2C only ge= neralities. Check my old guide for Arch Linux (Its outdated and you can't d= o the full procedure with it any longer if you want to test it)=2C it may g= ive you some tips:=0A= =0A= http://pastebin.com/2WF2PCcz=0A= =0A= You need to make sure than you have binutils compiled with x86_64-pep suppo= rt (No idea if Ubuntu has it by default)=2C or otherwise will have to build= and install it. Then you compile Xen=2C grab the correct xen.efi file and = put it at /boot=2C create a xen.cfg file with the proper boot parameters of= the Dom0 host=2C then finally=2C add it to your UEFI Boot Manager (Be it G= ummiboot/systemd-boot or GRUB) to load xen.efi.=0A= I absolutely recommend you to try with Gummiboot instead of GRUB=2C since G= RUB needed some patches to get it working (The multiboot protocol I think) = and I don't know if it already works out of the box.=0A= =0A= =0A= Also=2C it may not be your specific scenario but may be related. I hear som= e comments that latest binutils somehow broke compatibility with x86_64-pep= / i386pep=2C or something along those lines=2C so you needed to apply a pa= tch somewhere to get it working again. Check Arch Linux AUR xen package com= ments and this mail:=0A= =0A= https://aur.archlinux.org/packages/xen/=0A= https://lists.01.org/pipermail/igvt-g/2015-November/000137.html=0A= =0A= = --_f46d76a2-de46-4766-8341-be53817068c0_ Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
>> Hello=2C=0A= >>=0A= >>=A0I am attempting to run an EFI boot with xen 4.5.2. I have attempted th= is on FreeBSD 11 and Ubunut server 14.04. On both OS models upon reboot the= server will not find the OS. On ubuntu there is a ramdisk=0A= >> error and=A0no=A0OS found. While on FreeBSD 11 the OS is not found in /b= oot/xen.=A0=0A= >>=0A= >>=A0I attempted to install from source code and found that it will come ba= ck upon reboot but when I install xen tools to the latest version the OS is= again non-bootable.=A0=0A= >>=0A= >>=A0Is there any support for EFI booting on either of these systems. I can= not find any documentation that supports either of these OS models.=A0=0A= >>=0A= >>=A0This is for a research project and if EFI is not working on either mod= el could someone point me to the article on this=A0=0A= =A0=0A= =0A= Since its not for Ubuntu=2C I can't really specifically help you=2C only ge= neralities. Check my old guide for Arch Linux (Its outdated and you can't d= o the full procedure with it any longer if you want to test it)=2C it may g= ive you some tips:=0A= =0A= http://pastebin.com/2WF2PCcz=0A= =0A= You need to make sure than you have binutils compiled with x86_64-pep suppo= rt (No idea if Ubuntu has it by default)=2C or otherwise will have to build= and install it. Then you compile Xen=2C grab the correct xen.efi file and = put it at /boot=2C create a xen.cfg file with the proper boot parameters of= the Dom0 host=2C then finally=2C add it to your UEFI Boot Manager (Be it G= ummiboot/systemd-boot or GRUB) to load xen.efi.=0A= I absolutely recommend you to try with Gummiboot instead of GRUB=2C since G= RUB needed some patches to get it working (The multiboot protocol I think) = and I don't know if it already works out of the box.=0A= =0A= =0A= Also=2C it may not be your specific scenario but may be related. I hear som= e comments that latest binutils somehow broke compatibility with x86_64-pep= / i386pep=2C or something along those lines=2C so you needed to apply a pa= tch somewhere to get it working again. Check Arch Linux AUR xen package com= ments and this mail:=0A= =0A= https://aur.archlinux.org/packages/xen/=0A= https://lists.01.org/pipermail/igvt-g/2015-November/000137.html=0A= =0A=
= --_f46d76a2-de46-4766-8341-be53817068c0_-- --===============7015981420674119176== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users --===============7015981420674119176==-- From xen-users-bounces@lists.xen.org Mon Jan 04 22:31:41 2016 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 04 Jan 2016 22:31: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 1aGDe4-000267-Fh; Mon, 04 Jan 2016 22:30:32 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1aGDe2-000262-Js for xen-users@lists.xen.org; Mon, 04 Jan 2016 22:30:30 +0000 Received: from [85.158.137.68] by server-4.bemta-3.messagelabs.com id AE/FF-09570-582FA865; Mon, 04 Jan 2016 22:30:29 +0000 X-Env-Sender: zir_blazer@hotmail.com X-Msg-Ref: server-15.tower-31.messagelabs.com!1451946627!13592888!1 X-Originating-IP: [65.55.90.99] X-SpamReason: No, hits=1.8 required=7.0 tests=BODY_RANDOM_LONG, FORGED_HOTMAIL_RCVD,HTML_00_10,HTML_MESSAGE X-StarScan-Received: X-StarScan-Version: 7.35.1; banners=-,-,- X-VirusChecked: Checked Received: (qmail 4674 invoked from network); 4 Jan 2016 22:30:28 -0000 Received: from snt004-omc2s24.hotmail.com (HELO SNT004-OMC2S24.hotmail.com) (65.55.90.99) by server-15.tower-31.messagelabs.com with AES256-SHA256 encrypted SMTP; 4 Jan 2016 22:30:28 -0000 Received: from SNT151-W61 ([65.55.90.72]) by SNT004-OMC2S24.hotmail.com over TLS secured channel with Microsoft SMTPSVC(7.5.7601.23008); Mon, 4 Jan 2016 14:30:26 -0800 X-TMN: [BhE54uhAjTUhldGChCePVYFi77kAyL+HvxrDUfhVGB8=] X-Originating-Email: [zir_blazer@hotmail.com] Message-ID: From: Zir Blazer To: "Hultz, Jon" , "xen-users@lists.xen.org" Date: Mon, 4 Jan 2016 19:30:26 -0300 Importance: Normal In-Reply-To: References: MIME-Version: 1.0 X-OriginalArrivalTime: 04 Jan 2016 22:30:26.0915 (UTC) FILETIME=[828B8B30:01D1473F] Subject: Re: [Xen-users] EFI booting X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============7015981420674119176==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============7015981420674119176== Content-Type: multipart/alternative; boundary="_f46d76a2-de46-4766-8341-be53817068c0_" --_f46d76a2-de46-4766-8341-be53817068c0_ Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable >> Hello=2C=0A= >>=0A= >> I am attempting to run an EFI boot with xen 4.5.2. I have attempted this= on FreeBSD 11 and Ubunut server 14.04. On both OS models upon reboot the s= erver will not find the OS. On ubuntu there is a ramdisk=0A= >> error and no OS found. While on FreeBSD 11 the OS is not found in /boot/= xen. =0A= >>=0A= >> I attempted to install from source code and found that it will come back= upon reboot but when I install xen tools to the latest version the OS is a= gain non-bootable. =0A= >>=0A= >> Is there any support for EFI booting on either of these systems. I canno= t find any documentation that supports either of these OS models. =0A= >>=0A= >> This is for a research project and if EFI is not working on either model= could someone point me to the article on this =0A= =0A= =0A= Since its not for Ubuntu=2C I can't really specifically help you=2C only ge= neralities. Check my old guide for Arch Linux (Its outdated and you can't d= o the full procedure with it any longer if you want to test it)=2C it may g= ive you some tips:=0A= =0A= http://pastebin.com/2WF2PCcz=0A= =0A= You need to make sure than you have binutils compiled with x86_64-pep suppo= rt (No idea if Ubuntu has it by default)=2C or otherwise will have to build= and install it. Then you compile Xen=2C grab the correct xen.efi file and = put it at /boot=2C create a xen.cfg file with the proper boot parameters of= the Dom0 host=2C then finally=2C add it to your UEFI Boot Manager (Be it G= ummiboot/systemd-boot or GRUB) to load xen.efi.=0A= I absolutely recommend you to try with Gummiboot instead of GRUB=2C since G= RUB needed some patches to get it working (The multiboot protocol I think) = and I don't know if it already works out of the box.=0A= =0A= =0A= Also=2C it may not be your specific scenario but may be related. I hear som= e comments that latest binutils somehow broke compatibility with x86_64-pep= / i386pep=2C or something along those lines=2C so you needed to apply a pa= tch somewhere to get it working again. Check Arch Linux AUR xen package com= ments and this mail:=0A= =0A= https://aur.archlinux.org/packages/xen/=0A= https://lists.01.org/pipermail/igvt-g/2015-November/000137.html=0A= =0A= = --_f46d76a2-de46-4766-8341-be53817068c0_ Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
>> Hello=2C=0A= >>=0A= >>=A0I am attempting to run an EFI boot with xen 4.5.2. I have attempted th= is on FreeBSD 11 and Ubunut server 14.04. On both OS models upon reboot the= server will not find the OS. On ubuntu there is a ramdisk=0A= >> error and=A0no=A0OS found. While on FreeBSD 11 the OS is not found in /b= oot/xen.=A0=0A= >>=0A= >>=A0I attempted to install from source code and found that it will come ba= ck upon reboot but when I install xen tools to the latest version the OS is= again non-bootable.=A0=0A= >>=0A= >>=A0Is there any support for EFI booting on either of these systems. I can= not find any documentation that supports either of these OS models.=A0=0A= >>=0A= >>=A0This is for a research project and if EFI is not working on either mod= el could someone point me to the article on this=A0=0A= =A0=0A= =0A= Since its not for Ubuntu=2C I can't really specifically help you=2C only ge= neralities. Check my old guide for Arch Linux (Its outdated and you can't d= o the full procedure with it any longer if you want to test it)=2C it may g= ive you some tips:=0A= =0A= http://pastebin.com/2WF2PCcz=0A= =0A= You need to make sure than you have binutils compiled with x86_64-pep suppo= rt (No idea if Ubuntu has it by default)=2C or otherwise will have to build= and install it. Then you compile Xen=2C grab the correct xen.efi file and = put it at /boot=2C create a xen.cfg file with the proper boot parameters of= the Dom0 host=2C then finally=2C add it to your UEFI Boot Manager (Be it G= ummiboot/systemd-boot or GRUB) to load xen.efi.=0A= I absolutely recommend you to try with Gummiboot instead of GRUB=2C since G= RUB needed some patches to get it working (The multiboot protocol I think) = and I don't know if it already works out of the box.=0A= =0A= =0A= Also=2C it may not be your specific scenario but may be related. I hear som= e comments that latest binutils somehow broke compatibility with x86_64-pep= / i386pep=2C or something along those lines=2C so you needed to apply a pa= tch somewhere to get it working again. Check Arch Linux AUR xen package com= ments and this mail:=0A= =0A= https://aur.archlinux.org/packages/xen/=0A= https://lists.01.org/pipermail/igvt-g/2015-November/000137.html=0A= =0A=
= --_f46d76a2-de46-4766-8341-be53817068c0_-- --===============7015981420674119176== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users --===============7015981420674119176==-- From xen-users-bounces@lists.xen.org Mon Jan 04 22:44:34 2016 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 04 Jan 2016 22:44: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 1aGDrO-00030w-GZ; Mon, 04 Jan 2016 22:44:18 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1aGDrM-00030p-2Q for xen-users@lists.xen.org; Mon, 04 Jan 2016 22:44:16 +0000 Received: from [193.109.254.147] by server-9.bemta-14.messagelabs.com id FA/B9-13475-FB5FA865; Mon, 04 Jan 2016 22:44:15 +0000 X-Env-Sender: jakhead@gmail.com X-Msg-Ref: server-4.tower-27.messagelabs.com!1451947451!13722495!1 X-Originating-IP: [209.85.217.174] X-SpamReason: No, hits=1.7 required=7.0 tests=BODY_RANDOM_LONG, HTML_20_30,HTML_MESSAGE,RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 7.35.1; banners=-,-,- X-VirusChecked: Checked Received: (qmail 2171 invoked from network); 4 Jan 2016 22:44:11 -0000 Received: from mail-lb0-f174.google.com (HELO mail-lb0-f174.google.com) (209.85.217.174) by server-4.tower-27.messagelabs.com with AES128-GCM-SHA256 encrypted SMTP; 4 Jan 2016 22:44:11 -0000 Received: by mail-lb0-f174.google.com with SMTP id sv6so158891934lbb.0 for ; Mon, 04 Jan 2016 14:44:11 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=Z2IZ+9PxW1fNFgdcfWxrNH2cTFvqmIiCKm5+vS9dvnA=; b=r/6+vyF23pvCidrD+uTpoSHJ7BNvVekYhsWtfHWuN5TOjH4QyfgnHVxcq0/qC7whg7 V31fdtKSyrVp3xuR13/QNAAcQkrP/Xyd1YCNlljgujihatYqKbe4EdRNh616Egqc9vrm wV+uh+KnEEH/1yG/++Ez3P/+oeFA2rHDg3GPmdD4Z5RFVROtxcxgggE6A0KAV76No+rb 7N6FelLE2ykdsOAQCvmsvfOsMwDihGfDH+wN85UKCIxKoY1iUH6T9qEV5XB64ioCnEJ3 +8X6Piib11oM5uVXqSmUMz6M5LRuavZGrcWQPpEEQeq0fONVzA+uiog7n2qY/lWbUZ5I fjMg== MIME-Version: 1.0 X-Received: by 10.112.199.74 with SMTP id ji10mr11696105lbc.105.1451947450882; Mon, 04 Jan 2016 14:44:10 -0800 (PST) Received: by 10.25.212.10 with HTTP; Mon, 4 Jan 2016 14:44:10 -0800 (PST) In-Reply-To: References: Date: Mon, 4 Jan 2016 16:44:10 -0600 Message-ID: From: CF To: Zir Blazer Cc: "Hultz, Jon" , "xen-users@lists.xen.org" Subject: Re: [Xen-users] EFI booting X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============7383534832090343092==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============7383534832090343092== Content-Type: multipart/alternative; boundary=001a11c2ae9e0ae4b5052889dc3e --001a11c2ae9e0ae4b5052889dc3e Content-Type: text/plain; charset=UTF-8 For what it's worth, I struggled trying to downgrade binutils to compile a pep enabled version for about a week until resolving to chainload through efi enabled grub. If chainloading is acceptable for your scenario, it's much less headache. On Mon, Jan 4, 2016 at 4:30 PM, Zir Blazer wrote: > >> Hello, >> >> I am attempting to run an EFI boot with xen 4.5.2. I have > attempted this on FreeBSD 11 and Ubunut server 14.04. On both OS models > upon reboot the server will not find the OS. On ubuntu there is a ramdisk > >> error and no OS found. While on FreeBSD 11 the OS is not found in > /boot/xen. >> >> I attempted to install from source code and found that it > will come back upon reboot but when I install xen tools to the latest > version the OS is again non-bootable. >> >> Is there any support for EFI > booting on either of these systems. I cannot find any documentation that > supports either of these OS models. >> >> This is for a research project > and if EFI is not working on either model could someone point me to the > article on this Since its not for Ubuntu, I can't really specifically > help you, only generalities. Check my old guide for Arch Linux (Its > outdated and you can't do the full procedure with it any longer if you want > to test it), it may give you some tips: http://pastebin.com/2WF2PCcz You > need to make sure than you have binutils compiled with x86_64-pep support > (No idea if Ubuntu has it by default), or otherwise will have to build and > install it. Then you compile Xen, grab the correct xen.efi file and put it > at /boot, create a xen.cfg file with the proper boot parameters of the Dom0 > host, then finally, add it to your UEFI Boot Manager (Be it > Gummiboot/systemd-boot or GRUB) to load xen.efi. I absolutely recommend you > to try with Gummiboot instead of GRUB, since GRUB needed some patches to > get it working (The multiboot protocol I think) and I don't know if it > already works out of the box. Also, it may not be your specific scenario > but may be related. I hear some comments that latest binutils somehow broke > compatibility with x86_64-pep / i386pep, or something along those lines, so > you needed to apply a patch somewhere to get it working again. Check Arch > Linux AUR xen package comments and this mail: > https://aur.archlinux.org/packages/xen/ > https://lists.01.org/pipermail/igvt-g/2015-November/000137.html > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xen.org > http://lists.xen.org/xen-users > --001a11c2ae9e0ae4b5052889dc3e Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
For what it's worth, I struggled trying to downgrade b= inutils to compile a pep enabled version for about a week until resolving t= o chainload through efi enabled grub. If chainloading is acceptable for you= r scenario, it's much less headache.

On Mon, Jan 4, 2016 at 4:30 PM, Zir Blazer= <zir_blazer@hotmail.com> wrote:
>> Hello, >> >>=C2=A0I am attempting to run an EFI boot with xen 4.5.2. I have att= empted this on FreeBSD 11 and Ubunut server 14.04. On both OS models upon r= eboot the server will not find the OS. On ubuntu there is a ramdisk >> error and=C2=A0no=C2=A0OS found. While on FreeBSD 11 the OS is not= found in /boot/xen.=C2=A0 >> >>=C2=A0I attempted to install from source code and found that it wil= l come back upon reboot but when I install xen tools to the latest version = the OS is again non-bootable.=C2=A0 >> >>=C2=A0Is there any support for EFI booting on either of these syste= ms. I cannot find any documentation that supports either of these OS models= .=C2=A0 >> >>=C2=A0This is for a research project and if EFI is not working on e= ither model could someone point me to the article on this=C2=A0 =C2=A0 Since its not for Ubuntu, I can't really specifically help you, only ge= neralities. Check my old guide for Arch Linux (Its outdated and you can'= ;t do the full procedure with it any longer if you want to test it), it may= give you some tips: http://pastebin.= com/2WF2PCcz You need to make sure than you have binutils compiled with x86_64-pep suppo= rt (No idea if Ubuntu has it by default), or otherwise will have to build a= nd install it. Then you compile Xen, grab the correct xen.efi file and put = it at /boot, create a xen.cfg file with the proper boot parameters of the D= om0 host, then finally, add it to your UEFI Boot Manager (Be it Gummiboot/s= ystemd-boot or GRUB) to load xen.efi. I absolutely recommend you to try with Gummiboot instead of GRUB, since GRU= B needed some patches to get it working (The multiboot protocol I think) an= d I don't know if it already works out of the box. Also, it may not be your specific scenario but may be related. I hear some = comments that latest binutils somehow broke compatibility with x86_64-pep /= i386pep, or something along those lines, so you needed to apply a patch so= mewhere to get it working again. Check Arch Linux AUR xen package comments = and this mail: https= ://aur.archlinux.org/packages/xen/ https://lists.01.org/pipermail/igvt-g/2015-November/0001= 37.html

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

--001a11c2ae9e0ae4b5052889dc3e-- --===============7383534832090343092== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users --===============7383534832090343092==-- From xen-users-bounces@lists.xen.org Mon Jan 04 22:44:34 2016 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 04 Jan 2016 22:44: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 1aGDrO-00030w-GZ; Mon, 04 Jan 2016 22:44:18 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1aGDrM-00030p-2Q for xen-users@lists.xen.org; Mon, 04 Jan 2016 22:44:16 +0000 Received: from [193.109.254.147] by server-9.bemta-14.messagelabs.com id FA/B9-13475-FB5FA865; Mon, 04 Jan 2016 22:44:15 +0000 X-Env-Sender: jakhead@gmail.com X-Msg-Ref: server-4.tower-27.messagelabs.com!1451947451!13722495!1 X-Originating-IP: [209.85.217.174] X-SpamReason: No, hits=1.7 required=7.0 tests=BODY_RANDOM_LONG, HTML_20_30,HTML_MESSAGE,RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 7.35.1; banners=-,-,- X-VirusChecked: Checked Received: (qmail 2171 invoked from network); 4 Jan 2016 22:44:11 -0000 Received: from mail-lb0-f174.google.com (HELO mail-lb0-f174.google.com) (209.85.217.174) by server-4.tower-27.messagelabs.com with AES128-GCM-SHA256 encrypted SMTP; 4 Jan 2016 22:44:11 -0000 Received: by mail-lb0-f174.google.com with SMTP id sv6so158891934lbb.0 for ; Mon, 04 Jan 2016 14:44:11 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=Z2IZ+9PxW1fNFgdcfWxrNH2cTFvqmIiCKm5+vS9dvnA=; b=r/6+vyF23pvCidrD+uTpoSHJ7BNvVekYhsWtfHWuN5TOjH4QyfgnHVxcq0/qC7whg7 V31fdtKSyrVp3xuR13/QNAAcQkrP/Xyd1YCNlljgujihatYqKbe4EdRNh616Egqc9vrm wV+uh+KnEEH/1yG/++Ez3P/+oeFA2rHDg3GPmdD4Z5RFVROtxcxgggE6A0KAV76No+rb 7N6FelLE2ykdsOAQCvmsvfOsMwDihGfDH+wN85UKCIxKoY1iUH6T9qEV5XB64ioCnEJ3 +8X6Piib11oM5uVXqSmUMz6M5LRuavZGrcWQPpEEQeq0fONVzA+uiog7n2qY/lWbUZ5I fjMg== MIME-Version: 1.0 X-Received: by 10.112.199.74 with SMTP id ji10mr11696105lbc.105.1451947450882; Mon, 04 Jan 2016 14:44:10 -0800 (PST) Received: by 10.25.212.10 with HTTP; Mon, 4 Jan 2016 14:44:10 -0800 (PST) In-Reply-To: References: Date: Mon, 4 Jan 2016 16:44:10 -0600 Message-ID: From: CF To: Zir Blazer Cc: "Hultz, Jon" , "xen-users@lists.xen.org" Subject: Re: [Xen-users] EFI booting X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============7383534832090343092==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============7383534832090343092== Content-Type: multipart/alternative; boundary=001a11c2ae9e0ae4b5052889dc3e --001a11c2ae9e0ae4b5052889dc3e Content-Type: text/plain; charset=UTF-8 For what it's worth, I struggled trying to downgrade binutils to compile a pep enabled version for about a week until resolving to chainload through efi enabled grub. If chainloading is acceptable for your scenario, it's much less headache. On Mon, Jan 4, 2016 at 4:30 PM, Zir Blazer wrote: > >> Hello, >> >> I am attempting to run an EFI boot with xen 4.5.2. I have > attempted this on FreeBSD 11 and Ubunut server 14.04. On both OS models > upon reboot the server will not find the OS. On ubuntu there is a ramdisk > >> error and no OS found. While on FreeBSD 11 the OS is not found in > /boot/xen. >> >> I attempted to install from source code and found that it > will come back upon reboot but when I install xen tools to the latest > version the OS is again non-bootable. >> >> Is there any support for EFI > booting on either of these systems. I cannot find any documentation that > supports either of these OS models. >> >> This is for a research project > and if EFI is not working on either model could someone point me to the > article on this Since its not for Ubuntu, I can't really specifically > help you, only generalities. Check my old guide for Arch Linux (Its > outdated and you can't do the full procedure with it any longer if you want > to test it), it may give you some tips: http://pastebin.com/2WF2PCcz You > need to make sure than you have binutils compiled with x86_64-pep support > (No idea if Ubuntu has it by default), or otherwise will have to build and > install it. Then you compile Xen, grab the correct xen.efi file and put it > at /boot, create a xen.cfg file with the proper boot parameters of the Dom0 > host, then finally, add it to your UEFI Boot Manager (Be it > Gummiboot/systemd-boot or GRUB) to load xen.efi. I absolutely recommend you > to try with Gummiboot instead of GRUB, since GRUB needed some patches to > get it working (The multiboot protocol I think) and I don't know if it > already works out of the box. Also, it may not be your specific scenario > but may be related. I hear some comments that latest binutils somehow broke > compatibility with x86_64-pep / i386pep, or something along those lines, so > you needed to apply a patch somewhere to get it working again. Check Arch > Linux AUR xen package comments and this mail: > https://aur.archlinux.org/packages/xen/ > https://lists.01.org/pipermail/igvt-g/2015-November/000137.html > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xen.org > http://lists.xen.org/xen-users > --001a11c2ae9e0ae4b5052889dc3e Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
For what it's worth, I struggled trying to downgrade b= inutils to compile a pep enabled version for about a week until resolving t= o chainload through efi enabled grub. If chainloading is acceptable for you= r scenario, it's much less headache.

On Mon, Jan 4, 2016 at 4:30 PM, Zir Blazer= <zir_blazer@hotmail.com> wrote:
>> Hello, >> >>=C2=A0I am attempting to run an EFI boot with xen 4.5.2. I have att= empted this on FreeBSD 11 and Ubunut server 14.04. On both OS models upon r= eboot the server will not find the OS. On ubuntu there is a ramdisk >> error and=C2=A0no=C2=A0OS found. While on FreeBSD 11 the OS is not= found in /boot/xen.=C2=A0 >> >>=C2=A0I attempted to install from source code and found that it wil= l come back upon reboot but when I install xen tools to the latest version = the OS is again non-bootable.=C2=A0 >> >>=C2=A0Is there any support for EFI booting on either of these syste= ms. I cannot find any documentation that supports either of these OS models= .=C2=A0 >> >>=C2=A0This is for a research project and if EFI is not working on e= ither model could someone point me to the article on this=C2=A0 =C2=A0 Since its not for Ubuntu, I can't really specifically help you, only ge= neralities. Check my old guide for Arch Linux (Its outdated and you can'= ;t do the full procedure with it any longer if you want to test it), it may= give you some tips: http://pastebin.= com/2WF2PCcz You need to make sure than you have binutils compiled with x86_64-pep suppo= rt (No idea if Ubuntu has it by default), or otherwise will have to build a= nd install it. Then you compile Xen, grab the correct xen.efi file and put = it at /boot, create a xen.cfg file with the proper boot parameters of the D= om0 host, then finally, add it to your UEFI Boot Manager (Be it Gummiboot/s= ystemd-boot or GRUB) to load xen.efi. I absolutely recommend you to try with Gummiboot instead of GRUB, since GRU= B needed some patches to get it working (The multiboot protocol I think) an= d I don't know if it already works out of the box. Also, it may not be your specific scenario but may be related. I hear some = comments that latest binutils somehow broke compatibility with x86_64-pep /= i386pep, or something along those lines, so you needed to apply a patch so= mewhere to get it working again. Check Arch Linux AUR xen package comments = and this mail: https= ://aur.archlinux.org/packages/xen/ https://lists.01.org/pipermail/igvt-g/2015-November/0001= 37.html

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

--001a11c2ae9e0ae4b5052889dc3e-- --===============7383534832090343092== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users --===============7383534832090343092==-- From xen-users-bounces@lists.xen.org Mon Jan 04 22:44:55 2016 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 04 Jan 2016 22:44: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 1aGDry-00034p-Fq; Mon, 04 Jan 2016 22:44:54 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1aGDrx-00034X-32 for xen-users@lists.xen.org; Mon, 04 Jan 2016 22:44:53 +0000 Received: from [85.158.137.68] by server-12.bemta-3.messagelabs.com id 66/B9-14900-4E5FA865; Mon, 04 Jan 2016 22:44:52 +0000 X-Env-Sender: zir_blazer@hotmail.com X-Msg-Ref: server-6.tower-31.messagelabs.com!1451947487!13902660!1 X-Originating-IP: [65.55.90.82] X-SpamReason: No, hits=1.5 required=7.0 tests=BODY_RANDOM_LONG, FORGED_HOTMAIL_RCVD,HTML_20_30,HTML_MESSAGE X-StarScan-Received: X-StarScan-Version: 7.35.1; banners=-,-,- X-VirusChecked: Checked Received: (qmail 9794 invoked from network); 4 Jan 2016 22:44:49 -0000 Received: from snt004-omc2s7.hotmail.com (HELO SNT004-OMC2S7.hotmail.com) (65.55.90.82) by server-6.tower-31.messagelabs.com with AES256-SHA256 encrypted SMTP; 4 Jan 2016 22:44:49 -0000 Received: from SNT151-W52 ([65.55.90.73]) by SNT004-OMC2S7.hotmail.com over TLS secured channel with Microsoft SMTPSVC(7.5.7601.23008); Mon, 4 Jan 2016 14:44:47 -0800 X-TMN: [jvmBD9KuEkunF7iq7bJ+JBgqF4rHee85qxMoXzZahfw=] X-Originating-Email: [zir_blazer@hotmail.com] Message-ID: From: Zir Blazer To: "hultz.jon@solute.us" , "xen-users@lists.xen.org" Date: Mon, 4 Jan 2016 19:44:47 -0300 Importance: Normal In-Reply-To: References: , MIME-Version: 1.0 X-OriginalArrivalTime: 04 Jan 2016 22:44:47.0748 (UTC) FILETIME=[83A43C40:01D14741] Subject: [Xen-users] FW: EFI booting X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============5637239696110991452==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============5637239696110991452== Content-Type: multipart/alternative; boundary="_64744a46-8e35-4e5a-81c9-d4f12aae1020_" --_64744a46-8e35-4e5a-81c9-d4f12aae1020_ Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Resent because it didn't had proper line wrapping so it looks horrible. =0A= =0A= =0A= >> Hello=2C>>>> I am attempting to run an EFI boot with xen 4.5.2. I have a= ttempted this on FreeBSD 11 and Ubunut server 14.04. On both OS models upon= reboot the server will not find the OS. On ubuntu there is a ramdisk>> err= or and no OS found. While on FreeBSD 11 the OS is not found in /boot/xen.>>= >> I attempted to install from source code and found that it will come back= upon reboot but when I install xen tools to the latest version the OS is a= gain non-bootable. =0A= >>=0A= >> Is there any support for EFI booting on either of these systems. I canno= t find any documentation that supports either of these OS models.>>>> This = is for a research project and if EFI is not working on either model could s= omeone point me to the article on this Since its not for Ubuntu=2C I can't really specifically help you=2C only ge= neralities. Check my old guide for Arch Linux (Its outdated and you can't d= o the full procedure with it any longer if you want to test it)=2C it may g= ive you some tips:http://pastebin.com/2WF2PCcz You need to make sure than you have binutils compiled with x86_64-pep suppo= rt (No idea if Ubuntu has it by default)=2C or otherwise will have to build= and install it. Then you compile Xen=2C grab the correct xen.efi file and = put it at /boot=2C create a xen.cfg file with the proper boot parameters of= the Dom0 host=2C then finally=2C add it to your UEFI Boot Manager (Be it G= ummiboot/systemd-boot or GRUB) to load xen.efi. That is usually the correct= procedure.I absolutely recommend you to try with Gummiboot instead of GRUB= =2C since GRUB needed some patches to get it working (The multiboot protoco= l I think) and I don't know if it already works out of the box. Also=2C it may not be your specific scenario but may be related. I hear som= e comments that latest binutils somehow broke compatibility with x86_64-pep= / i386pep=2C or something along those lines=2C so you needed to apply a pa= tch somewhere to get it working again. Check Arch Linux AUR xen package com= ments and this mail:https://aur.archlinux.org/packages/xen/https://lists.01= .org/pipermail/igvt-g/2015-November/000137.html=0A= =0A= = --_64744a46-8e35-4e5a-81c9-d4f12aae1020_ Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
Resent because it didn't had pro= per line wrapping so it looks horrible.


=0A= =0A= =0A=
>=3B>=3B Hello=2C
>=3B>=3B
>=3B>=3B =3BI am attempting to run an EFI boot= with xen 4.5.2. I have attempted this on FreeBSD 11 and Ubunut server 14.0= 4. On both OS models upon reboot the server will not find the OS. On ubuntu= there is a ramdisk
>=3B>=3B error and =3Bno&= nbsp=3BOS found. While on FreeBSD 11 the OS is not found in /boot/xen.
>=3B>=3B
>=3B>=3B =3BI = attempted to install from source code and found that it will come back upon= reboot but when I install xen tools to the latest version the OS is again = non-bootable. =3B=0A= >=3B>=3B=0A= >=3B>=3B =3BIs there any support for EFI booting on either of these= systems. I cannot find any documentation that supports either of these OS = models.
>=3B>=3B
>=3B>= =3B =3BThis is for a research project and if EFI is not working on eith= er model could someone point me to the article on this

Since its not for Ubuntu=2C I can't really spe= cifically help you=2C only generalities. Check my old guide for Arch Linux = (Its outdated and you can't do the full procedure with it any longer if you= want to test it)=2C it may give you some tips:
http:= //pastebin.com/2WF2PCcz

Yo= u need to make sure than you have binutils compiled with x86_64-pep support= (No idea if Ubuntu has it by default)=2C or otherwise will have to build a= nd install it. Then you compile Xen=2C grab the correct xen.efi file and pu= t it at /boot=2C create a xen.cfg file with the proper boot parameters of t= he Dom0 host=2C then finally=2C add it to your UEFI Boot Manager (Be it Gum= miboot/systemd-boot or GRUB) to load xen.efi. That is usually the correct p= rocedure.
I absolutely recommend you to try with Gumm= iboot instead of GRUB=2C since GRUB needed some patches to get it working (= The multiboot protocol I think) and I don't know if it already works out of= the box.

Also=2C it may n= ot be your specific scenario but may be related. I hear some comments that = latest binutils somehow broke compatibility with x86_64-pep / i386pep=2C or= something along those lines=2C so you needed to apply a patch somewhere to= get it working again. Check Arch Linux AUR xen package comments and this m= ail:
https://aur.archlinux.org/packages/xen/
https://lists.01.org/pipermail/igvt-g/2015-November/000137.ht= ml=0A= =0A=
= --_64744a46-8e35-4e5a-81c9-d4f12aae1020_-- --===============5637239696110991452== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users --===============5637239696110991452==-- From xen-users-bounces@lists.xen.org Mon Jan 04 22:44:55 2016 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 04 Jan 2016 22:44: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 1aGDry-00034p-Fq; Mon, 04 Jan 2016 22:44:54 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1aGDrx-00034X-32 for xen-users@lists.xen.org; Mon, 04 Jan 2016 22:44:53 +0000 Received: from [85.158.137.68] by server-12.bemta-3.messagelabs.com id 66/B9-14900-4E5FA865; Mon, 04 Jan 2016 22:44:52 +0000 X-Env-Sender: zir_blazer@hotmail.com X-Msg-Ref: server-6.tower-31.messagelabs.com!1451947487!13902660!1 X-Originating-IP: [65.55.90.82] X-SpamReason: No, hits=1.5 required=7.0 tests=BODY_RANDOM_LONG, FORGED_HOTMAIL_RCVD,HTML_20_30,HTML_MESSAGE X-StarScan-Received: X-StarScan-Version: 7.35.1; banners=-,-,- X-VirusChecked: Checked Received: (qmail 9794 invoked from network); 4 Jan 2016 22:44:49 -0000 Received: from snt004-omc2s7.hotmail.com (HELO SNT004-OMC2S7.hotmail.com) (65.55.90.82) by server-6.tower-31.messagelabs.com with AES256-SHA256 encrypted SMTP; 4 Jan 2016 22:44:49 -0000 Received: from SNT151-W52 ([65.55.90.73]) by SNT004-OMC2S7.hotmail.com over TLS secured channel with Microsoft SMTPSVC(7.5.7601.23008); Mon, 4 Jan 2016 14:44:47 -0800 X-TMN: [jvmBD9KuEkunF7iq7bJ+JBgqF4rHee85qxMoXzZahfw=] X-Originating-Email: [zir_blazer@hotmail.com] Message-ID: From: Zir Blazer To: "hultz.jon@solute.us" , "xen-users@lists.xen.org" Date: Mon, 4 Jan 2016 19:44:47 -0300 Importance: Normal In-Reply-To: References: , MIME-Version: 1.0 X-OriginalArrivalTime: 04 Jan 2016 22:44:47.0748 (UTC) FILETIME=[83A43C40:01D14741] Subject: [Xen-users] FW: EFI booting X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============5637239696110991452==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============5637239696110991452== Content-Type: multipart/alternative; boundary="_64744a46-8e35-4e5a-81c9-d4f12aae1020_" --_64744a46-8e35-4e5a-81c9-d4f12aae1020_ Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Resent because it didn't had proper line wrapping so it looks horrible. =0A= =0A= =0A= >> Hello=2C>>>> I am attempting to run an EFI boot with xen 4.5.2. I have a= ttempted this on FreeBSD 11 and Ubunut server 14.04. On both OS models upon= reboot the server will not find the OS. On ubuntu there is a ramdisk>> err= or and no OS found. While on FreeBSD 11 the OS is not found in /boot/xen.>>= >> I attempted to install from source code and found that it will come back= upon reboot but when I install xen tools to the latest version the OS is a= gain non-bootable. =0A= >>=0A= >> Is there any support for EFI booting on either of these systems. I canno= t find any documentation that supports either of these OS models.>>>> This = is for a research project and if EFI is not working on either model could s= omeone point me to the article on this Since its not for Ubuntu=2C I can't really specifically help you=2C only ge= neralities. Check my old guide for Arch Linux (Its outdated and you can't d= o the full procedure with it any longer if you want to test it)=2C it may g= ive you some tips:http://pastebin.com/2WF2PCcz You need to make sure than you have binutils compiled with x86_64-pep suppo= rt (No idea if Ubuntu has it by default)=2C or otherwise will have to build= and install it. Then you compile Xen=2C grab the correct xen.efi file and = put it at /boot=2C create a xen.cfg file with the proper boot parameters of= the Dom0 host=2C then finally=2C add it to your UEFI Boot Manager (Be it G= ummiboot/systemd-boot or GRUB) to load xen.efi. That is usually the correct= procedure.I absolutely recommend you to try with Gummiboot instead of GRUB= =2C since GRUB needed some patches to get it working (The multiboot protoco= l I think) and I don't know if it already works out of the box. Also=2C it may not be your specific scenario but may be related. I hear som= e comments that latest binutils somehow broke compatibility with x86_64-pep= / i386pep=2C or something along those lines=2C so you needed to apply a pa= tch somewhere to get it working again. Check Arch Linux AUR xen package com= ments and this mail:https://aur.archlinux.org/packages/xen/https://lists.01= .org/pipermail/igvt-g/2015-November/000137.html=0A= =0A= = --_64744a46-8e35-4e5a-81c9-d4f12aae1020_ Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
Resent because it didn't had pro= per line wrapping so it looks horrible.


=0A= =0A= =0A=
>=3B>=3B Hello=2C
>=3B>=3B
>=3B>=3B =3BI am attempting to run an EFI boot= with xen 4.5.2. I have attempted this on FreeBSD 11 and Ubunut server 14.0= 4. On both OS models upon reboot the server will not find the OS. On ubuntu= there is a ramdisk
>=3B>=3B error and =3Bno&= nbsp=3BOS found. While on FreeBSD 11 the OS is not found in /boot/xen.
>=3B>=3B
>=3B>=3B =3BI = attempted to install from source code and found that it will come back upon= reboot but when I install xen tools to the latest version the OS is again = non-bootable. =3B=0A= >=3B>=3B=0A= >=3B>=3B =3BIs there any support for EFI booting on either of these= systems. I cannot find any documentation that supports either of these OS = models.
>=3B>=3B
>=3B>= =3B =3BThis is for a research project and if EFI is not working on eith= er model could someone point me to the article on this

Since its not for Ubuntu=2C I can't really spe= cifically help you=2C only generalities. Check my old guide for Arch Linux = (Its outdated and you can't do the full procedure with it any longer if you= want to test it)=2C it may give you some tips:
http:= //pastebin.com/2WF2PCcz

Yo= u need to make sure than you have binutils compiled with x86_64-pep support= (No idea if Ubuntu has it by default)=2C or otherwise will have to build a= nd install it. Then you compile Xen=2C grab the correct xen.efi file and pu= t it at /boot=2C create a xen.cfg file with the proper boot parameters of t= he Dom0 host=2C then finally=2C add it to your UEFI Boot Manager (Be it Gum= miboot/systemd-boot or GRUB) to load xen.efi. That is usually the correct p= rocedure.
I absolutely recommend you to try with Gumm= iboot instead of GRUB=2C since GRUB needed some patches to get it working (= The multiboot protocol I think) and I don't know if it already works out of= the box.

Also=2C it may n= ot be your specific scenario but may be related. I hear some comments that = latest binutils somehow broke compatibility with x86_64-pep / i386pep=2C or= something along those lines=2C so you needed to apply a patch somewhere to= get it working again. Check Arch Linux AUR xen package comments and this m= ail:
https://aur.archlinux.org/packages/xen/
https://lists.01.org/pipermail/igvt-g/2015-November/000137.ht= ml=0A= =0A=
= --_64744a46-8e35-4e5a-81c9-d4f12aae1020_-- --===============5637239696110991452== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users --===============5637239696110991452==-- From xen-users-bounces@lists.xen.org Tue Jan 05 09:35:27 2016 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 05 Jan 2016 09:35: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 1aGO0a-0006ri-16; Tue, 05 Jan 2016 09:34:28 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1aGO0Y-0006rd-Hm for xen-users@lists.xen.org; Tue, 05 Jan 2016 09:34:26 +0000 Received: from [193.109.254.147] by server-2.bemta-14.messagelabs.com id 90/3E-12889-12E8B865; Tue, 05 Jan 2016 09:34:25 +0000 X-Env-Sender: ara4sh@hotmail.com X-Msg-Ref: server-8.tower-27.messagelabs.com!1451986463!10974947!1 X-Originating-IP: [65.54.190.93] X-SpamReason: No, hits=0.7 required=7.0 tests=FORGED_HOTMAIL_RCVD, HTML_40_50,HTML_MESSAGE X-StarScan-Received: X-StarScan-Version: 7.35.1; banners=-,-,- X-VirusChecked: Checked Received: (qmail 29665 invoked from network); 5 Jan 2016 09:34:24 -0000 Received: from bay004-omc2s18.hotmail.com (HELO BAY004-OMC2S18.hotmail.com) (65.54.190.93) by server-8.tower-27.messagelabs.com with AES256-SHA256 encrypted SMTP; 5 Jan 2016 09:34:24 -0000 Received: from BAY178-W30 ([65.54.190.125]) by BAY004-OMC2S18.hotmail.com over TLS secured channel with Microsoft SMTPSVC(7.5.7601.23008); Tue, 5 Jan 2016 01:34:22 -0800 X-TMN: [93oJaOsdsKzb2Gt03SrvjtLVaT/w5GHR] X-Originating-Email: [ara4sh@hotmail.com] Message-ID: From: Arash Shams To: "xen-users@lists.xen.org" Date: Tue, 5 Jan 2016 09:34:21 +0000 Importance: Normal MIME-Version: 1.0 X-OriginalArrivalTime: 05 Jan 2016 09:34:22.0949 (UTC) FILETIME=[42ABF150:01D1479C] Subject: [Xen-users] Alpha digital OpenUnix 4.0b emulation X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============3199426850759150985==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============3199426850759150985== Content-Type: multipart/alternative; boundary="_2f86b6ce-2bab-4d97-b246-72390fdabafb_" --_2f86b6ce-2bab-4d97-b246-72390fdabafb_ Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hello=20 After i find out qemu/kvm cant emulate 4.0b and start supporting alpha from= version 4.0f i decide to try xen .=20 is there any chance to emulate this kind of device using xen ? https://en.wikipedia.org/wiki/Tru64_UNIX thank you=20 = --_2f86b6ce-2bab-4d97-b246-72390fdabafb_ Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
Hello

After i find out q= emu/kvm cant emulate 4.0b and start supporting alpha from version 4.0f i de= cide to try xen .
is there any chance to emulate this kind of device us= ing xen ?
https://en.wikipedia.org/wiki/Tru64_UNIX


thank you =
= --_2f86b6ce-2bab-4d97-b246-72390fdabafb_-- --===============3199426850759150985== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users --===============3199426850759150985==-- From xen-users-bounces@lists.xen.org Tue Jan 05 09:35:27 2016 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 05 Jan 2016 09:35: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 1aGO0a-0006ri-16; Tue, 05 Jan 2016 09:34:28 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1aGO0Y-0006rd-Hm for xen-users@lists.xen.org; Tue, 05 Jan 2016 09:34:26 +0000 Received: from [193.109.254.147] by server-2.bemta-14.messagelabs.com id 90/3E-12889-12E8B865; Tue, 05 Jan 2016 09:34:25 +0000 X-Env-Sender: ara4sh@hotmail.com X-Msg-Ref: server-8.tower-27.messagelabs.com!1451986463!10974947!1 X-Originating-IP: [65.54.190.93] X-SpamReason: No, hits=0.7 required=7.0 tests=FORGED_HOTMAIL_RCVD, HTML_40_50,HTML_MESSAGE X-StarScan-Received: X-StarScan-Version: 7.35.1; banners=-,-,- X-VirusChecked: Checked Received: (qmail 29665 invoked from network); 5 Jan 2016 09:34:24 -0000 Received: from bay004-omc2s18.hotmail.com (HELO BAY004-OMC2S18.hotmail.com) (65.54.190.93) by server-8.tower-27.messagelabs.com with AES256-SHA256 encrypted SMTP; 5 Jan 2016 09:34:24 -0000 Received: from BAY178-W30 ([65.54.190.125]) by BAY004-OMC2S18.hotmail.com over TLS secured channel with Microsoft SMTPSVC(7.5.7601.23008); Tue, 5 Jan 2016 01:34:22 -0800 X-TMN: [93oJaOsdsKzb2Gt03SrvjtLVaT/w5GHR] X-Originating-Email: [ara4sh@hotmail.com] Message-ID: From: Arash Shams To: "xen-users@lists.xen.org" Date: Tue, 5 Jan 2016 09:34:21 +0000 Importance: Normal MIME-Version: 1.0 X-OriginalArrivalTime: 05 Jan 2016 09:34:22.0949 (UTC) FILETIME=[42ABF150:01D1479C] Subject: [Xen-users] Alpha digital OpenUnix 4.0b emulation X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============3199426850759150985==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============3199426850759150985== Content-Type: multipart/alternative; boundary="_2f86b6ce-2bab-4d97-b246-72390fdabafb_" --_2f86b6ce-2bab-4d97-b246-72390fdabafb_ Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hello=20 After i find out qemu/kvm cant emulate 4.0b and start supporting alpha from= version 4.0f i decide to try xen .=20 is there any chance to emulate this kind of device using xen ? https://en.wikipedia.org/wiki/Tru64_UNIX thank you=20 = --_2f86b6ce-2bab-4d97-b246-72390fdabafb_ Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
Hello

After i find out q= emu/kvm cant emulate 4.0b and start supporting alpha from version 4.0f i de= cide to try xen .
is there any chance to emulate this kind of device us= ing xen ?
https://en.wikipedia.org/wiki/Tru64_UNIX


thank you =
= --_2f86b6ce-2bab-4d97-b246-72390fdabafb_-- --===============3199426850759150985== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users --===============3199426850759150985==-- From xen-users-bounces@lists.xen.org Tue Jan 05 10:45:37 2016 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 05 Jan 2016 10:45: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 1aGP6X-0001vh-G5; Tue, 05 Jan 2016 10:44:41 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1aGP6V-0001vb-UB for xen-users@lists.xen.org; Tue, 05 Jan 2016 10:44:40 +0000 Received: from [85.158.143.35] by server-3.bemta-4.messagelabs.com id EE/75-31122-79E9B865; Tue, 05 Jan 2016 10:44:39 +0000 X-Env-Sender: prvs=80598d8b9=Ian.Campbell@citrix.com X-Msg-Ref: server-6.tower-21.messagelabs.com!1451990675!8459530!1 X-Originating-IP: [66.165.176.63] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjYuMTY1LjE3Ni42MyA9PiAzMDYwNDg=\n, received_headers: No Received headers X-StarScan-Received: X-StarScan-Version: 7.35.1; banners=-,-,- X-VirusChecked: Checked Received: (qmail 29536 invoked from network); 5 Jan 2016 10:44:36 -0000 Received: from smtp02.citrix.com (HELO SMTP02.CITRIX.COM) (66.165.176.63) by server-6.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 5 Jan 2016 10:44:36 -0000 X-IronPort-AV: E=Sophos;i="5.20,524,1444694400"; d="scan'208";a="329054497" Message-ID: <1451990566.13361.219.camel@citrix.com> From: Ian Campbell To: Arash Shams , "xen-users@lists.xen.org" Date: Tue, 5 Jan 2016 10:42:46 +0000 In-Reply-To: References: X-Mailer: Evolution 3.18.2-1 MIME-Version: 1.0 X-DLP: MIA1 Subject: Re: [Xen-users] Alpha digital OpenUnix 4.0b emulation X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/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, 2016-01-05 at 09:34 +0000, Arash Shams wrote: > Hello > > After i find out qemu/kvm cant emulate 4.0b and start supporting alpha > from version 4.0f i decide to try xen . > is there any chance to emulate this kind of device using xen ? > https://en.wikipedia.org/wiki/Tru64_UNIX Xen doesn't do ISA emulation, only virtualisation of the underlying ISA of the platform. It currently runs on x86 and ARM and has in the past run on IA64 and PPC, but AFAIK it has never been ported to Alpha. KVM is in much the same situation as Xen in this regard, since it uses the underlying CPU ISA, but I would expect regular QEMU without KVM to at least have a stab at emulating an Alpha, given the existence of qemu-system-alpha in the Debian packages ;-) Whether QEMU can emulate any particular Alpha platform which Tru64 supports I can't say. Ian. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Tue Jan 05 10:45:37 2016 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 05 Jan 2016 10:45: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 1aGP6X-0001vh-G5; Tue, 05 Jan 2016 10:44:41 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1aGP6V-0001vb-UB for xen-users@lists.xen.org; Tue, 05 Jan 2016 10:44:40 +0000 Received: from [85.158.143.35] by server-3.bemta-4.messagelabs.com id EE/75-31122-79E9B865; Tue, 05 Jan 2016 10:44:39 +0000 X-Env-Sender: prvs=80598d8b9=Ian.Campbell@citrix.com X-Msg-Ref: server-6.tower-21.messagelabs.com!1451990675!8459530!1 X-Originating-IP: [66.165.176.63] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjYuMTY1LjE3Ni42MyA9PiAzMDYwNDg=\n, received_headers: No Received headers X-StarScan-Received: X-StarScan-Version: 7.35.1; banners=-,-,- X-VirusChecked: Checked Received: (qmail 29536 invoked from network); 5 Jan 2016 10:44:36 -0000 Received: from smtp02.citrix.com (HELO SMTP02.CITRIX.COM) (66.165.176.63) by server-6.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 5 Jan 2016 10:44:36 -0000 X-IronPort-AV: E=Sophos;i="5.20,524,1444694400"; d="scan'208";a="329054497" Message-ID: <1451990566.13361.219.camel@citrix.com> From: Ian Campbell To: Arash Shams , "xen-users@lists.xen.org" Date: Tue, 5 Jan 2016 10:42:46 +0000 In-Reply-To: References: X-Mailer: Evolution 3.18.2-1 MIME-Version: 1.0 X-DLP: MIA1 Subject: Re: [Xen-users] Alpha digital OpenUnix 4.0b emulation X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/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, 2016-01-05 at 09:34 +0000, Arash Shams wrote: > Hello > > After i find out qemu/kvm cant emulate 4.0b and start supporting alpha > from version 4.0f i decide to try xen . > is there any chance to emulate this kind of device using xen ? > https://en.wikipedia.org/wiki/Tru64_UNIX Xen doesn't do ISA emulation, only virtualisation of the underlying ISA of the platform. It currently runs on x86 and ARM and has in the past run on IA64 and PPC, but AFAIK it has never been ported to Alpha. KVM is in much the same situation as Xen in this regard, since it uses the underlying CPU ISA, but I would expect regular QEMU without KVM to at least have a stab at emulating an Alpha, given the existence of qemu-system-alpha in the Debian packages ;-) Whether QEMU can emulate any particular Alpha platform which Tru64 supports I can't say. Ian. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Wed Jan 06 21:34:13 2016 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 06 Jan 2016 21:34: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 1aGvha-0000ap-4p; Wed, 06 Jan 2016 21:33:06 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1aGvhY-0000aj-91 for Xen-users@lists.xen.org; Wed, 06 Jan 2016 21:33:04 +0000 Received: from [193.109.254.147] by server-8.bemta-14.messagelabs.com id FB/FA-24450-F088D865; Wed, 06 Jan 2016 21:33:03 +0000 X-Env-Sender: alvin@Iplink.net X-Msg-Ref: server-4.tower-27.messagelabs.com!1452115982!14191671!1 X-Originating-IP: [192.139.81.184] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 7.35.1; banners=-,-,- X-VirusChecked: Checked Received: (qmail 61167 invoked from network); 6 Jan 2016 21:33:02 -0000 Received: from imap.iplink.net (HELO smtp.iplink.net) (192.139.81.184) by server-4.tower-27.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 6 Jan 2016 21:33:02 -0000 Received: from alvinsworkstation.netvel.net (unknown [206.108.5.187]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by smtp.iplink.net (Postfix) with ESMTP id E2E2CEDE3F0 for ; Wed, 6 Jan 2016 16:32:47 -0500 (EST) From: Alvin Starr To: Xen-users@lists.xen.org Message-ID: <568D87FF.1070205@Iplink.net> Date: Wed, 6 Jan 2016 16:32:47 -0500 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.3.0 MIME-Version: 1.0 Subject: [Xen-users] MCA/MCE and EDAC. X-BeenThere: xen-users@lists.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 an AMD system that kicks out a correctable memory error on occasion and I can see it in the xen-dmesg. How would I get the errors propagated up into dom0 via EDAC since that is the only error mechanism supported by the AMD cpus? -- Alvin Starr || voice: (905)513-7688 Netvel Inc. || Cell: (416)806-0133 alvin@netvel.net || _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Wed Jan 06 21:34:13 2016 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 06 Jan 2016 21:34: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 1aGvhe-0000b1-Rr; Wed, 06 Jan 2016 21:33:10 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1aGvhd-0000aw-KQ for Xen-users@lists.xen.org; Wed, 06 Jan 2016 21:33:09 +0000 Received: from [85.158.137.68] by server-1.bemta-3.messagelabs.com id 51/21-02745-4188D865; Wed, 06 Jan 2016 21:33:08 +0000 X-Env-Sender: alvin@Iplink.net X-Msg-Ref: server-14.tower-31.messagelabs.com!1452115985!14325213!1 X-Originating-IP: [192.139.81.184] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 7.35.1; banners=-,-,- X-VirusChecked: Checked Received: (qmail 32678 invoked from network); 6 Jan 2016 21:33:06 -0000 Received: from imap.iplink.net (HELO smtp.iplink.net) (192.139.81.184) by server-14.tower-31.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 6 Jan 2016 21:33:06 -0000 Received: from alvinsworkstation.netvel.net (unknown [206.108.5.187]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by smtp.iplink.net (Postfix) with ESMTP id 251DBEDE3F0 for ; Wed, 6 Jan 2016 16:33:05 -0500 (EST) From: Alvin Starr To: Xen-users@lists.xen.org Message-ID: <568D8811.4010201@Iplink.net> Date: Wed, 6 Jan 2016 16:33:05 -0500 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.3.0 MIME-Version: 1.0 Subject: [Xen-users] Dom0 and NUMA. X-BeenThere: xen-users@lists.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 How would I pass the NUMA config to Dom0. It seems that xen flattens the config so all the processors are my xencmdline is set to: loglvl=info guest_loglvl=info com1=115200,8n1,0x3e8,5 console=com1,vga nmi=dom0 dom0_nodes=0,1,2,3 numa=on sched_smt_power_savings=true -- Alvin Starr || voice: (905)513-7688 Netvel Inc. || Cell: (416)806-0133 alvin@netvel.net || _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Wed Jan 06 21:34:13 2016 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 06 Jan 2016 21:34: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 1aGvha-0000ap-4p; Wed, 06 Jan 2016 21:33:06 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1aGvhY-0000aj-91 for Xen-users@lists.xen.org; Wed, 06 Jan 2016 21:33:04 +0000 Received: from [193.109.254.147] by server-8.bemta-14.messagelabs.com id FB/FA-24450-F088D865; Wed, 06 Jan 2016 21:33:03 +0000 X-Env-Sender: alvin@Iplink.net X-Msg-Ref: server-4.tower-27.messagelabs.com!1452115982!14191671!1 X-Originating-IP: [192.139.81.184] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 7.35.1; banners=-,-,- X-VirusChecked: Checked Received: (qmail 61167 invoked from network); 6 Jan 2016 21:33:02 -0000 Received: from imap.iplink.net (HELO smtp.iplink.net) (192.139.81.184) by server-4.tower-27.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 6 Jan 2016 21:33:02 -0000 Received: from alvinsworkstation.netvel.net (unknown [206.108.5.187]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by smtp.iplink.net (Postfix) with ESMTP id E2E2CEDE3F0 for ; Wed, 6 Jan 2016 16:32:47 -0500 (EST) From: Alvin Starr To: Xen-users@lists.xen.org Message-ID: <568D87FF.1070205@Iplink.net> Date: Wed, 6 Jan 2016 16:32:47 -0500 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.3.0 MIME-Version: 1.0 Subject: [Xen-users] MCA/MCE and EDAC. X-BeenThere: xen-users@lists.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 an AMD system that kicks out a correctable memory error on occasion and I can see it in the xen-dmesg. How would I get the errors propagated up into dom0 via EDAC since that is the only error mechanism supported by the AMD cpus? -- Alvin Starr || voice: (905)513-7688 Netvel Inc. || Cell: (416)806-0133 alvin@netvel.net || _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Wed Jan 06 21:34:13 2016 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 06 Jan 2016 21:34: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 1aGvhe-0000b1-Rr; Wed, 06 Jan 2016 21:33:10 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1aGvhd-0000aw-KQ for Xen-users@lists.xen.org; Wed, 06 Jan 2016 21:33:09 +0000 Received: from [85.158.137.68] by server-1.bemta-3.messagelabs.com id 51/21-02745-4188D865; Wed, 06 Jan 2016 21:33:08 +0000 X-Env-Sender: alvin@Iplink.net X-Msg-Ref: server-14.tower-31.messagelabs.com!1452115985!14325213!1 X-Originating-IP: [192.139.81.184] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 7.35.1; banners=-,-,- X-VirusChecked: Checked Received: (qmail 32678 invoked from network); 6 Jan 2016 21:33:06 -0000 Received: from imap.iplink.net (HELO smtp.iplink.net) (192.139.81.184) by server-14.tower-31.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 6 Jan 2016 21:33:06 -0000 Received: from alvinsworkstation.netvel.net (unknown [206.108.5.187]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by smtp.iplink.net (Postfix) with ESMTP id 251DBEDE3F0 for ; Wed, 6 Jan 2016 16:33:05 -0500 (EST) From: Alvin Starr To: Xen-users@lists.xen.org Message-ID: <568D8811.4010201@Iplink.net> Date: Wed, 6 Jan 2016 16:33:05 -0500 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.3.0 MIME-Version: 1.0 Subject: [Xen-users] Dom0 and NUMA. X-BeenThere: xen-users@lists.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 How would I pass the NUMA config to Dom0. It seems that xen flattens the config so all the processors are my xencmdline is set to: loglvl=info guest_loglvl=info com1=115200,8n1,0x3e8,5 console=com1,vga nmi=dom0 dom0_nodes=0,1,2,3 numa=on sched_smt_power_savings=true -- Alvin Starr || voice: (905)513-7688 Netvel Inc. || Cell: (416)806-0133 alvin@netvel.net || _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Thu Jan 07 07:01:48 2016 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 07 Jan 2016 07:01: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 1aH4Yz-00041N-Da; Thu, 07 Jan 2016 07:00:49 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1aH4Yx-000415-1W for Xen-users@lists.xen.org; Thu, 07 Jan 2016 07:00:47 +0000 Received: from [85.158.143.35] by server-3.bemta-4.messagelabs.com id 79/13-31122-E1D0E865; Thu, 07 Jan 2016 07:00:46 +0000 X-Env-Sender: van.freenix@gmail.com X-Msg-Ref: server-6.tower-21.messagelabs.com!1452150044!8786387!1 X-Originating-IP: [209.85.220.44] X-SpamReason: No, hits=0.5 required=7.0 tests=BODY_RANDOM_LONG X-StarScan-Received: X-StarScan-Version: 7.35.1; banners=-,-,- X-VirusChecked: Checked Received: (qmail 27058 invoked from network); 7 Jan 2016 07:00:45 -0000 Received: from mail-pa0-f44.google.com (HELO mail-pa0-f44.google.com) (209.85.220.44) by server-6.tower-21.messagelabs.com with AES128-GCM-SHA256 encrypted SMTP; 7 Jan 2016 07:00:45 -0000 Received: by mail-pa0-f44.google.com with SMTP id cy9so251384049pac.0 for ; Wed, 06 Jan 2016 23:00:45 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=date:from:to:cc:subject:message-id:mime-version:content-type :content-disposition:user-agent; bh=nvi7DKpOZidEy+coSH/zfcZQMsJ5b3WbOy+OaItyrGA=; b=ZWn2uk2zyAJMwCc/qRttTTw5xaPEOyMrQVrsoinGpvL7xgIuxow6IC9Auyd5oKsf+T 3N1ontYSrLWoQbp+rlBSc771MQ/d21SA13B6ZqA3Pz6yRRSu8C94ugb3fbhunTVk4ifp Twk7U9H/LIQMAv+9A1Zjc16V6UoXebZPRzVMeYjMFwtqzd9Mwzn5O9Si4gOXdiZnHCog Qjpm7C3ijK6O01Mfaiu4w7YfstYCbE08QxLP6T2nlPkV9vqUaCdEejvzwhQItUvHAE+Y VvQ8/Qba4/H3WLlaxH/kDHlgtj+46bAy8eyNf0Pu+c3iNwW/RQ6+1ngoKAiORTG2a44J OKww== X-Received: by 10.66.248.106 with SMTP id yl10mr146686640pac.140.1452150044337; Wed, 06 Jan 2016 23:00:44 -0800 (PST) Received: from linux-7smt.suse (gate-zmy3.freescale.com. [192.88.167.1]) by smtp.googlemail.com with ESMTPSA id hz8sm149431740pac.10.2016.01.06.23.00.42 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 06 Jan 2016 23:00:43 -0800 (PST) Date: Thu, 7 Jan 2016 14:50:16 +0800 From: Peng Fan To: Xen-users@lists.xen.org Message-ID: <20160107065013.GA29626@linux-7smt.suse> MIME-Version: 1.0 Content-Disposition: inline User-Agent: Mutt/1.5.24 (2015-08-30) Cc: van.freenix@gmail.com Subject: [Xen-users] SMMU Question for passthrough device X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: 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 experts, There are two linux os running on my ARM64 platform. Now I want to passthrough a platform device(sd controller) to DomU to let DomU can directly access the external SD card. The sd controller supports DMA. The sd controller driver work well in Host Linux. So I have a question how DomU DMA interacts with SMMU and finally access memory? There are 3 dma_map_ops in linux arch/arm64/mm/dma-mapping.c static struct dma_map_ops iommu_dma_ops static struct dma_map_ops swiotlb_dma_ops struct dma_map_ops dummy_dma_ops Since smmu will be assigned to XEN, linux kernel will not use iommu_dma_ops. So swiotlb_dma_ops will be used for DomU. But I can not find out how swiotlb_dma_ops interacts with SMMU. I checked xen/driver/passthrough/arm/smmu.c and find arm_smmu_map_page has such a checking code "BUG_ON(!is_domain_direct_mapped(d));", so to my case, only dom0 can use smmu, and DomU is not 1:1 mapping. I am confused about how DomU can DMA through SMMU. There also one in arch/arm/xen/mm.c struct dma_map_ops xen_swiotlb_dma_ops This one seems only is used in Dom0. Then Dom0 linux kernel defaults does not use iommu, how can I use iommu for Dom0? I have the dts with SMMU and XEN can detect the SMMU, but dom0 use swiotlb, can you help explain how dom0 dma work through smmu? Thanks, Peng. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Thu Jan 07 07:01:48 2016 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 07 Jan 2016 07:01: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 1aH4Yz-00041N-Da; Thu, 07 Jan 2016 07:00:49 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1aH4Yx-000415-1W for Xen-users@lists.xen.org; Thu, 07 Jan 2016 07:00:47 +0000 Received: from [85.158.143.35] by server-3.bemta-4.messagelabs.com id 79/13-31122-E1D0E865; Thu, 07 Jan 2016 07:00:46 +0000 X-Env-Sender: van.freenix@gmail.com X-Msg-Ref: server-6.tower-21.messagelabs.com!1452150044!8786387!1 X-Originating-IP: [209.85.220.44] X-SpamReason: No, hits=0.5 required=7.0 tests=BODY_RANDOM_LONG X-StarScan-Received: X-StarScan-Version: 7.35.1; banners=-,-,- X-VirusChecked: Checked Received: (qmail 27058 invoked from network); 7 Jan 2016 07:00:45 -0000 Received: from mail-pa0-f44.google.com (HELO mail-pa0-f44.google.com) (209.85.220.44) by server-6.tower-21.messagelabs.com with AES128-GCM-SHA256 encrypted SMTP; 7 Jan 2016 07:00:45 -0000 Received: by mail-pa0-f44.google.com with SMTP id cy9so251384049pac.0 for ; Wed, 06 Jan 2016 23:00:45 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=date:from:to:cc:subject:message-id:mime-version:content-type :content-disposition:user-agent; bh=nvi7DKpOZidEy+coSH/zfcZQMsJ5b3WbOy+OaItyrGA=; b=ZWn2uk2zyAJMwCc/qRttTTw5xaPEOyMrQVrsoinGpvL7xgIuxow6IC9Auyd5oKsf+T 3N1ontYSrLWoQbp+rlBSc771MQ/d21SA13B6ZqA3Pz6yRRSu8C94ugb3fbhunTVk4ifp Twk7U9H/LIQMAv+9A1Zjc16V6UoXebZPRzVMeYjMFwtqzd9Mwzn5O9Si4gOXdiZnHCog Qjpm7C3ijK6O01Mfaiu4w7YfstYCbE08QxLP6T2nlPkV9vqUaCdEejvzwhQItUvHAE+Y VvQ8/Qba4/H3WLlaxH/kDHlgtj+46bAy8eyNf0Pu+c3iNwW/RQ6+1ngoKAiORTG2a44J OKww== X-Received: by 10.66.248.106 with SMTP id yl10mr146686640pac.140.1452150044337; Wed, 06 Jan 2016 23:00:44 -0800 (PST) Received: from linux-7smt.suse (gate-zmy3.freescale.com. [192.88.167.1]) by smtp.googlemail.com with ESMTPSA id hz8sm149431740pac.10.2016.01.06.23.00.42 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 06 Jan 2016 23:00:43 -0800 (PST) Date: Thu, 7 Jan 2016 14:50:16 +0800 From: Peng Fan To: Xen-users@lists.xen.org Message-ID: <20160107065013.GA29626@linux-7smt.suse> MIME-Version: 1.0 Content-Disposition: inline User-Agent: Mutt/1.5.24 (2015-08-30) Cc: van.freenix@gmail.com Subject: [Xen-users] SMMU Question for passthrough device X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: 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 experts, There are two linux os running on my ARM64 platform. Now I want to passthrough a platform device(sd controller) to DomU to let DomU can directly access the external SD card. The sd controller supports DMA. The sd controller driver work well in Host Linux. So I have a question how DomU DMA interacts with SMMU and finally access memory? There are 3 dma_map_ops in linux arch/arm64/mm/dma-mapping.c static struct dma_map_ops iommu_dma_ops static struct dma_map_ops swiotlb_dma_ops struct dma_map_ops dummy_dma_ops Since smmu will be assigned to XEN, linux kernel will not use iommu_dma_ops. So swiotlb_dma_ops will be used for DomU. But I can not find out how swiotlb_dma_ops interacts with SMMU. I checked xen/driver/passthrough/arm/smmu.c and find arm_smmu_map_page has such a checking code "BUG_ON(!is_domain_direct_mapped(d));", so to my case, only dom0 can use smmu, and DomU is not 1:1 mapping. I am confused about how DomU can DMA through SMMU. There also one in arch/arm/xen/mm.c struct dma_map_ops xen_swiotlb_dma_ops This one seems only is used in Dom0. Then Dom0 linux kernel defaults does not use iommu, how can I use iommu for Dom0? I have the dts with SMMU and XEN can detect the SMMU, but dom0 use swiotlb, can you help explain how dom0 dma work through smmu? Thanks, Peng. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Thu Jan 07 10:51:42 2016 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 07 Jan 2016 10:51: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 1aH89W-00075a-5E; Thu, 07 Jan 2016 10:50:46 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1aH89U-00075V-0Z for xen-users@lists.xen.org; Thu, 07 Jan 2016 10:50:44 +0000 Received: from [85.158.137.68] by server-14.bemta-3.messagelabs.com id F3/AD-02975-3034E865; Thu, 07 Jan 2016 10:50:43 +0000 X-Env-Sender: prvs=807a36095=Ian.Campbell@citrix.com X-Msg-Ref: server-5.tower-31.messagelabs.com!1452163840!14465642!1 X-Originating-IP: [66.165.176.63] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjYuMTY1LjE3Ni42MyA9PiAzMDYwNDg=\n, received_headers: No Received headers X-StarScan-Received: X-StarScan-Version: 7.35.1; banners=-,-,- X-VirusChecked: Checked Received: (qmail 15249 invoked from network); 7 Jan 2016 10:50:41 -0000 Received: from smtp02.citrix.com (HELO SMTP02.CITRIX.COM) (66.165.176.63) by server-5.tower-31.messagelabs.com with RC4-SHA encrypted SMTP; 7 Jan 2016 10:50:41 -0000 X-IronPort-AV: E=Sophos;i="5.20,532,1444694400"; d="cfg'?txt'?scan'208";a="329549080" Message-ID: <1452163727.21055.183.camel@citrix.com> From: Ian Campbell To: Atul Raut Date: Thu, 7 Jan 2016 10:48:47 +0000 In-Reply-To: References: Content-Type: multipart/mixed; boundary="=-Sr1YUXDVLIsNfWmGapeO" X-Mailer: Evolution 3.18.2-1 MIME-Version: 1.0 X-DLP: MIA1 Cc: xen-users Subject: Re: [Xen-users] DOMu failed to launch X-BeenThere: xen-users@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 --=-Sr1YUXDVLIsNfWmGapeO Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Please keep the discussion on list and avoid HTML mails. I didn't see anything confidentially looking in the logs so I've copied the list for you this time. On Wed, 2016-01-06 at 23:44 -0800, Atul Raut wrote: > Hi Ian, >=20 > This is regarding my queries - http://comments.gmane.org/gmane.comp.emula > tors.xen.user/86055=C2=A0;=20 > Sorry I didnt got mail, where you answer. >=20 > Please find Attachment of my DomU config file & failure logs. > libxl: verbose: libxl_create.c:101:libxl__domain_build_info_setdefault: q= emu-xen is unavailable, use qemu-xen-traditional instead: No such file or d= irectory I'm unsure why the tools think you need a qemu, AFAICT your configuration doesn't. I'd suggest removing the serial=3Dpty since that may be confusing things and is meaningless for an ARM domain (it is specific to x86/HVM guests) > libxl: debug: libxl_create.c:945:initiate_domain_create: running bootload= er > libxl: debug: libxl_bootloader.c:330:libxl__bootloader_run: no bootloader= configured, using user supplied kernel > libxl: debug: libxl_event.c:691:libxl__ev_xswatch_deregister: watch w=3D0= x435cf0: deregister unregistered > domainbuilder: detail: xc_dom_allocate: cmdline=3D"earlycon=3Dxenboot hos= tname=3DVM1 console=3Dhvc1 root=3D/dev/ram nosoftlockup rcu_cpu_stall_suppr= ess=3D1", features=3D"(null)" > libxl: debug: libxl_dom.c:631:libxl__build_pv: pv kernel mapped 0 path /b= oot/Image > domainbuilder: detail: xc_dom_kernel_file: filename=3D"/boot/Image" > domainbuilder: detail: ATUL - xc_dom_malloc_filemap: failed (on file `/bo= ot/Image') > domainbuilder: detail: xc_dom_malloc_filemap=C2=A0=C2=A0=C2=A0=C2=A0: 202= 33 kB > domainbuilder: detail: xc_dom_ramdisk_file: filename=3D"/boot/rootfs.cpio= .gz" > domainbuilder: detail: ATUL - xc_dom_malloc_filemap: failed (on file `/bo= ot/rootfs.cpio.gz') These two "ATUL - ... failed" messages: If it has failed why is it continuing? Have you patched the source in some ways? > domainbuilder: detail: xc_dom_malloc_filemap=C2=A0=C2=A0=C2=A0=C2=A0: 208= 0 kB > domainbuilder: detail: xc_dom_boot_xen_init: ver 4.6, caps xen-3.0-aarch6= 4 xen-3.0-armv7l > domainbuilder: detail: xc_dom_rambase_init: RAM starts at 40000 > 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 zImage (ARM64) lo= ader ... > domainbuilder: detail: loader probe OK > domainbuilder: detail: xc_dom_parse_zimage64_kernel: called > domainbuilder: detail: xc_dom_parse_zimage64_kernel: xen-3.0-aarch64: 0x4= 0080000 -> 0x41442620 > libxl: debug: libxl_arm.c:776:libxl__arch_domain_init_hw_description: con= structing DTB for Xen version 4.6 guest > libxl: debug: libxl_arm.c:777:libxl__arch_domain_init_hw_description:=C2= =A0=C2=A0- vGIC version: V3 > libxl: debug: libxl_arm.c:273:make_chosen_node: /chosen/bootargs =3D earl= ycon=3Dxenboot hostname=3DVM1 console=3Dhvc1 root=3D/dev/ram nosoftlockup r= cu_cpu_stall_suppress=3D1 > libxl: debug: libxl_arm.c:280:make_chosen_node: /chosen adding placeholde= r linux,initrd properties > libxl: debug: libxl_arm.c:380:make_memory_nodes: Creating placeholder nod= e /memory@40000000 > libxl: debug: libxl_arm.c:380:make_memory_nodes: Creating placeholder nod= e /memory@200000000 > libxl: debug: libxl_arm.c:871:libxl__arch_domain_init_hw_description: fdt= total size 1442 > domainbuilder: detail: xc_dom_devicetree_mem: called > domainbuilder: detail: xc_dom_mem_init: mem 128 MB, pages 0x8000 pages, 4= k each > domainbuilder: detail: xc_dom_mem_init: 0x8000 pages > domainbuilder: detail: xc_dom_boot_mem_init: called > domainbuilder: detail: set_mode: guest xen-3.0-aarch64, address size 64 > domainbuilder: detail: xc_dom_malloc=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0= =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0: 256 kB > domainbuilder: detail: populate_guest_memory: populating RAM @ 0000000040= 000000-0000000048000000 (128MB) > domainbuilder: detail: populate_one_size: populated 0x40/0x40 entries wit= h shift 9 > domainbuilder: detail: arch_setup_meminit: placing boot modules at 0x47df= 6000 > domainbuilder: detail: arch_setup_meminit: ramdisk: 0x47df6000 -> 0x47fff= 000 > domainbuilder: detail: arch_setup_meminit: devicetree: 0x47fff000 -> 0x48= 000000 > libxl: debug: libxl_arm.c:936:libxl__arch_domain_finalise_hw_description:= /chosen updating initrd properties to cover 47df6000-47fff000 > libxl: debug: libxl_arm.c:902:finalise_one_memory_node: Populating placeh= older node /memory@40000000 > libxl: debug: libxl_arm.c:896:finalise_one_memory_node: Nopping out place= holder node /memory@200000000 > domainbuilder: detail: xc_dom_build_image: called > domainbuilder: detail: xc_dom_alloc_segment:=C2=A0=C2=A0=C2=A0kernel=C2= =A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0: 0x40080000 -> 0x41443000=C2=A0=C2= =A0(pfn 0x40080 + 0x13c3 pages) > domainbuilder: detail: xc_dom_malloc=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0= =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0: 118 kB > domainbuilder: detail: xc_dom_pfn_to_ptr_retcount: domU mapping: pfn 0x40= 080+0x13c3 at 0x7f8d6e0000 > domainbuilder: detail: xc_dom_load_zimage_kernel: called > domainbuilder: detail: xc_dom_load_zimage_kernel: kernel seg 0x40080000-0= x41443000 > domainbuilder: detail: xc_dom_load_zimage_kernel: copy 20719136 bytes fro= m blob 0x7f8eced000 to dst 0x7f8d6e0000 > domainbuilder: detail: xc_dom_alloc_segment:=C2=A0=C2=A0=C2=A0ramdisk=C2= =A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0: 0x47df6000 -> 0x47fff000=C2=A0=C2=A0(pfn= 0x47df6 + 0x209 pages) > domainbuilder: detail: xc_dom_pfn_to_ptr_retcount: domU mapping: pfn 0x47= df6+0x209 at 0x7f8d4d7000 > domainbuilder: detail: xc_dom_alloc_segment:=C2=A0=C2=A0=C2=A0devicetree= =C2=A0=C2=A0=C2=A0: 0x47fff000 -> 0x48000000=C2=A0=C2=A0(pfn 0x47fff + 0x1 = pages) > domainbuilder: detail: xc_dom_pfn_to_ptr_retcount: domU mapping: pfn 0x47= fff+0x1 at 0x7f903dc000 > domainbuilder: detail: alloc_magic_pages: called > domainbuilder: detail: count_pgtables_arm: called > domainbuilder: detail: xc_dom_build_image=C2=A0=C2=A0: virt_alloc_end : 0= x48000000 > domainbuilder: detail: xc_dom_build_image=C2=A0=C2=A0: virt_pgtab_end : 0= x0 > 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= -aarch64 <=3D matches > domainbuilder: detail: xc_dom_compat_check: supported guest type: xen-3.0= -armv7l > domainbuilder: detail: setup_pgtables_arm: called > domainbuilder: detail: clear_page: pfn 0x39000, mfn 0x39000 > domainbuilder: detail: clear_page: pfn 0x39001, mfn 0x39001 > domainbuilder: detail: start_info_arm: called > domainbuilder: detail: domain builder memory footprint > domainbuilder: detail:=C2=A0=C2=A0=C2=A0=C2=A0allocated > domainbuilder: detail:=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0malloc=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= : 389 kB > domainbuilder: detail:=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0anon mmap= =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0: 0 bytes > domainbuilder: detail:=C2=A0=C2=A0=C2=A0=C2=A0mapped > domainbuilder: detail:=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0file mmap= =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0: 22314 kB > domainbuilder: detail:=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0domU mmap= =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0: 22324 kB > domainbuilder: detail: vcpu_arm64: called > domainbuilder: detail: DTB 47fff000 > domainbuilder: detail: Initial state CPSR 0x1c5 PC 0x40080000 > domainbuilder: detail: launch_vm: called, ctxt=3D0x7f903de004 > domainbuilder: detail: xc_dom_gnttab_hvm_seed: called, pfn=3D0x38000 > domainbuilder: detail: xc_dom_release: called > (XEN) grant_table.c:411:d0v1 Bad flags (0) or dom (0). (expected dom 0) Line 411 of this file in 4.6 isn't this log message (which appears to be around line 523. What exact version of Xen are you running? Have you patched it in any way? > libxl: debug: libxl_event.c:2193:libxl__ao_progress_report: ao 0x435300: = progress report: callback queued aop=3D0x4398d0 > libxl: debug: libxl_event.c:1874:libxl__ao_complete: ao 0x435300: complet= e, rc=3D0 > libxl: debug: libxl_event.c:1410:egc_run_callbacks: ao 0x435300: progress= report: callback aop=3D0x4398d0 > libxl: debug: libxl_create.c:1583:do_domain_create: ao 0x435300: inprogre= ss: poller=3D0x434ba0, flags=3Dic > libxl: debug: libxl_event.c:1843:libxl__ao__destroy: ao 0x435300: destroy > xenconsole: Could not read tty from store: Success --=-Sr1YUXDVLIsNfWmGapeO Content-Disposition: attachment; filename="vm1.cfg" Content-Type: text/plain; name="vm1.cfg"; charset="us-ascii" Content-Transfer-Encoding: 7bit # Guest name name = "VM1" # Guest console serial = 'pty' # 128-bit UUID for the domain as a hexadecimal number. # Use "uuidgen" to generate one if required. # The default behavior is to generate a new UUID each time the guest is started. #uuid = "XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX" # Kernel image to boot kernel = "/boot/Image" # Ramdisk (optional) ramdisk = "/boot/rootfs.cpio.gz" # Kernel command line options extra = "earlycon=xenboot hostname=VM1 console=hvc1 root=/dev/ram rw init=/init nosoftlockup rcu_cpu_stall_suppress=1" # Initial memory allocation (MB) memory = 128 # Maximum memory (MB) # If this is greater than `memory' then the slack will start ballooned # (this assumes guest kernel support for ballooning) #maxmem = 512 # Number of VCPUS vcpus = 1 --=-Sr1YUXDVLIsNfWmGapeO Content-Disposition: attachment; filename="DomU_failure_logs.txt" Content-Type: text/plain; name="DomU_failure_logs.txt"; charset="us-ascii" Content-Transfer-Encoding: 7bit libxl: verbose: libxl_create.c:101:libxl__domain_build_info_setdefault: qemu-xen is unavailable, use qemu-xen-traditional instead: No such file or directory libxl: debug: libxl_create.c:945:initiate_domain_create: running bootloader libxl: debug: libxl_bootloader.c:330:libxl__bootloader_run: no bootloader configured, using user supplied kernel libxl: debug: libxl_event.c:691:libxl__ev_xswatch_deregister: watch w=0x435cf0: deregister unregistered domainbuilder: detail: xc_dom_allocate: cmdline="earlycon=xenboot hostname=VM1 console=hvc1 root=/dev/ram nosoftlockup rcu_cpu_stall_suppress=1", features="(null)" libxl: debug: libxl_dom.c:631:libxl__build_pv: pv kernel mapped 0 path /boot/Image domainbuilder: detail: xc_dom_kernel_file: filename="/boot/Image" domainbuilder: detail: ATUL - xc_dom_malloc_filemap: failed (on file `/boot/Image') domainbuilder: detail: xc_dom_malloc_filemap : 20233 kB domainbuilder: detail: xc_dom_ramdisk_file: filename="/boot/rootfs.cpio.gz" domainbuilder: detail: ATUL - xc_dom_malloc_filemap: failed (on file `/boot/rootfs.cpio.gz') domainbuilder: detail: xc_dom_malloc_filemap : 2080 kB domainbuilder: detail: xc_dom_boot_xen_init: ver 4.6, caps xen-3.0-aarch64 xen-3.0-armv7l domainbuilder: detail: xc_dom_rambase_init: RAM starts at 40000 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 zImage (ARM64) loader ... domainbuilder: detail: loader probe OK domainbuilder: detail: xc_dom_parse_zimage64_kernel: called domainbuilder: detail: xc_dom_parse_zimage64_kernel: xen-3.0-aarch64: 0x40080000 -> 0x41442620 libxl: debug: libxl_arm.c:776:libxl__arch_domain_init_hw_description: constructing DTB for Xen version 4.6 guest libxl: debug: libxl_arm.c:777:libxl__arch_domain_init_hw_description: - vGIC version: V3 libxl: debug: libxl_arm.c:273:make_chosen_node: /chosen/bootargs = earlycon=xenboot hostname=VM1 console=hvc1 root=/dev/ram nosoftlockup rcu_cpu_stall_suppress=1 libxl: debug: libxl_arm.c:280:make_chosen_node: /chosen adding placeholder linux,initrd properties libxl: debug: libxl_arm.c:380:make_memory_nodes: Creating placeholder node /memory@40000000 libxl: debug: libxl_arm.c:380:make_memory_nodes: Creating placeholder node /memory@200000000 libxl: debug: libxl_arm.c:871:libxl__arch_domain_init_hw_description: fdt total size 1442 domainbuilder: detail: xc_dom_devicetree_mem: called domainbuilder: detail: xc_dom_mem_init: mem 128 MB, pages 0x8000 pages, 4k each domainbuilder: detail: xc_dom_mem_init: 0x8000 pages domainbuilder: detail: xc_dom_boot_mem_init: called domainbuilder: detail: set_mode: guest xen-3.0-aarch64, address size 64 domainbuilder: detail: xc_dom_malloc : 256 kB domainbuilder: detail: populate_guest_memory: populating RAM @ 0000000040000000-0000000048000000 (128MB) domainbuilder: detail: populate_one_size: populated 0x40/0x40 entries with shift 9 domainbuilder: detail: arch_setup_meminit: placing boot modules at 0x47df6000 domainbuilder: detail: arch_setup_meminit: ramdisk: 0x47df6000 -> 0x47fff000 domainbuilder: detail: arch_setup_meminit: devicetree: 0x47fff000 -> 0x48000000 libxl: debug: libxl_arm.c:936:libxl__arch_domain_finalise_hw_description: /chosen updating initrd properties to cover 47df6000-47fff000 libxl: debug: libxl_arm.c:902:finalise_one_memory_node: Populating placeholder node /memory@40000000 libxl: debug: libxl_arm.c:896:finalise_one_memory_node: Nopping out placeholder node /memory@200000000 domainbuilder: detail: xc_dom_build_image: called domainbuilder: detail: xc_dom_alloc_segment: kernel : 0x40080000 -> 0x41443000 (pfn 0x40080 + 0x13c3 pages) domainbuilder: detail: xc_dom_malloc : 118 kB domainbuilder: detail: xc_dom_pfn_to_ptr_retcount: domU mapping: pfn 0x40080+0x13c3 at 0x7f8d6e0000 domainbuilder: detail: xc_dom_load_zimage_kernel: called domainbuilder: detail: xc_dom_load_zimage_kernel: kernel seg 0x40080000-0x41443000 domainbuilder: detail: xc_dom_load_zimage_kernel: copy 20719136 bytes from blob 0x7f8eced000 to dst 0x7f8d6e0000 domainbuilder: detail: xc_dom_alloc_segment: ramdisk : 0x47df6000 -> 0x47fff000 (pfn 0x47df6 + 0x209 pages) domainbuilder: detail: xc_dom_pfn_to_ptr_retcount: domU mapping: pfn 0x47df6+0x209 at 0x7f8d4d7000 domainbuilder: detail: xc_dom_alloc_segment: devicetree : 0x47fff000 -> 0x48000000 (pfn 0x47fff + 0x1 pages) domainbuilder: detail: xc_dom_pfn_to_ptr_retcount: domU mapping: pfn 0x47fff+0x1 at 0x7f903dc000 domainbuilder: detail: alloc_magic_pages: called domainbuilder: detail: count_pgtables_arm: called domainbuilder: detail: xc_dom_build_image : virt_alloc_end : 0x48000000 domainbuilder: detail: xc_dom_build_image : virt_pgtab_end : 0x0 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-aarch64 <= matches domainbuilder: detail: xc_dom_compat_check: supported guest type: xen-3.0-armv7l domainbuilder: detail: setup_pgtables_arm: called domainbuilder: detail: clear_page: pfn 0x39000, mfn 0x39000 domainbuilder: detail: clear_page: pfn 0x39001, mfn 0x39001 domainbuilder: detail: start_info_arm: called domainbuilder: detail: domain builder memory footprint domainbuilder: detail: allocated domainbuilder: detail: malloc : 389 kB domainbuilder: detail: anon mmap : 0 bytes domainbuilder: detail: mapped domainbuilder: detail: file mmap : 22314 kB domainbuilder: detail: domU mmap : 22324 kB domainbuilder: detail: vcpu_arm64: called domainbuilder: detail: DTB 47fff000 domainbuilder: detail: Initial state CPSR 0x1c5 PC 0x40080000 domainbuilder: detail: launch_vm: called, ctxt=0x7f903de004 domainbuilder: detail: xc_dom_gnttab_hvm_seed: called, pfn=0x38000 domainbuilder: detail: xc_dom_release: called (XEN) grant_table.c:411:d0v1 Bad flags (0) or dom (0). (expected dom 0) libxl: debug: libxl_event.c:2193:libxl__ao_progress_report: ao 0x435300: progress report: callback queued aop=0x4398d0 libxl: debug: libxl_event.c:1874:libxl__ao_complete: ao 0x435300: complete, rc=0 libxl: debug: libxl_event.c:1410:egc_run_callbacks: ao 0x435300: progress report: callback aop=0x4398d0 libxl: debug: libxl_create.c:1583:do_domain_create: ao 0x435300: inprogress: poller=0x434ba0, flags=ic libxl: debug: libxl_event.c:1843:libxl__ao__destroy: ao 0x435300: destroy xenconsole: Could not read tty from store: Success --=-Sr1YUXDVLIsNfWmGapeO Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users --=-Sr1YUXDVLIsNfWmGapeO-- From xen-users-bounces@lists.xen.org Thu Jan 07 10:51:42 2016 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 07 Jan 2016 10:51: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 1aH89W-00075a-5E; Thu, 07 Jan 2016 10:50:46 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1aH89U-00075V-0Z for xen-users@lists.xen.org; Thu, 07 Jan 2016 10:50:44 +0000 Received: from [85.158.137.68] by server-14.bemta-3.messagelabs.com id F3/AD-02975-3034E865; Thu, 07 Jan 2016 10:50:43 +0000 X-Env-Sender: prvs=807a36095=Ian.Campbell@citrix.com X-Msg-Ref: server-5.tower-31.messagelabs.com!1452163840!14465642!1 X-Originating-IP: [66.165.176.63] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjYuMTY1LjE3Ni42MyA9PiAzMDYwNDg=\n, received_headers: No Received headers X-StarScan-Received: X-StarScan-Version: 7.35.1; banners=-,-,- X-VirusChecked: Checked Received: (qmail 15249 invoked from network); 7 Jan 2016 10:50:41 -0000 Received: from smtp02.citrix.com (HELO SMTP02.CITRIX.COM) (66.165.176.63) by server-5.tower-31.messagelabs.com with RC4-SHA encrypted SMTP; 7 Jan 2016 10:50:41 -0000 X-IronPort-AV: E=Sophos;i="5.20,532,1444694400"; d="cfg'?txt'?scan'208";a="329549080" Message-ID: <1452163727.21055.183.camel@citrix.com> From: Ian Campbell To: Atul Raut Date: Thu, 7 Jan 2016 10:48:47 +0000 In-Reply-To: References: Content-Type: multipart/mixed; boundary="=-Sr1YUXDVLIsNfWmGapeO" X-Mailer: Evolution 3.18.2-1 MIME-Version: 1.0 X-DLP: MIA1 Cc: xen-users Subject: Re: [Xen-users] DOMu failed to launch X-BeenThere: xen-users@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 --=-Sr1YUXDVLIsNfWmGapeO Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Please keep the discussion on list and avoid HTML mails. I didn't see anything confidentially looking in the logs so I've copied the list for you this time. On Wed, 2016-01-06 at 23:44 -0800, Atul Raut wrote: > Hi Ian, >=20 > This is regarding my queries - http://comments.gmane.org/gmane.comp.emula > tors.xen.user/86055=C2=A0;=20 > Sorry I didnt got mail, where you answer. >=20 > Please find Attachment of my DomU config file & failure logs. > libxl: verbose: libxl_create.c:101:libxl__domain_build_info_setdefault: q= emu-xen is unavailable, use qemu-xen-traditional instead: No such file or d= irectory I'm unsure why the tools think you need a qemu, AFAICT your configuration doesn't. I'd suggest removing the serial=3Dpty since that may be confusing things and is meaningless for an ARM domain (it is specific to x86/HVM guests) > libxl: debug: libxl_create.c:945:initiate_domain_create: running bootload= er > libxl: debug: libxl_bootloader.c:330:libxl__bootloader_run: no bootloader= configured, using user supplied kernel > libxl: debug: libxl_event.c:691:libxl__ev_xswatch_deregister: watch w=3D0= x435cf0: deregister unregistered > domainbuilder: detail: xc_dom_allocate: cmdline=3D"earlycon=3Dxenboot hos= tname=3DVM1 console=3Dhvc1 root=3D/dev/ram nosoftlockup rcu_cpu_stall_suppr= ess=3D1", features=3D"(null)" > libxl: debug: libxl_dom.c:631:libxl__build_pv: pv kernel mapped 0 path /b= oot/Image > domainbuilder: detail: xc_dom_kernel_file: filename=3D"/boot/Image" > domainbuilder: detail: ATUL - xc_dom_malloc_filemap: failed (on file `/bo= ot/Image') > domainbuilder: detail: xc_dom_malloc_filemap=C2=A0=C2=A0=C2=A0=C2=A0: 202= 33 kB > domainbuilder: detail: xc_dom_ramdisk_file: filename=3D"/boot/rootfs.cpio= .gz" > domainbuilder: detail: ATUL - xc_dom_malloc_filemap: failed (on file `/bo= ot/rootfs.cpio.gz') These two "ATUL - ... failed" messages: If it has failed why is it continuing? Have you patched the source in some ways? > domainbuilder: detail: xc_dom_malloc_filemap=C2=A0=C2=A0=C2=A0=C2=A0: 208= 0 kB > domainbuilder: detail: xc_dom_boot_xen_init: ver 4.6, caps xen-3.0-aarch6= 4 xen-3.0-armv7l > domainbuilder: detail: xc_dom_rambase_init: RAM starts at 40000 > 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 zImage (ARM64) lo= ader ... > domainbuilder: detail: loader probe OK > domainbuilder: detail: xc_dom_parse_zimage64_kernel: called > domainbuilder: detail: xc_dom_parse_zimage64_kernel: xen-3.0-aarch64: 0x4= 0080000 -> 0x41442620 > libxl: debug: libxl_arm.c:776:libxl__arch_domain_init_hw_description: con= structing DTB for Xen version 4.6 guest > libxl: debug: libxl_arm.c:777:libxl__arch_domain_init_hw_description:=C2= =A0=C2=A0- vGIC version: V3 > libxl: debug: libxl_arm.c:273:make_chosen_node: /chosen/bootargs =3D earl= ycon=3Dxenboot hostname=3DVM1 console=3Dhvc1 root=3D/dev/ram nosoftlockup r= cu_cpu_stall_suppress=3D1 > libxl: debug: libxl_arm.c:280:make_chosen_node: /chosen adding placeholde= r linux,initrd properties > libxl: debug: libxl_arm.c:380:make_memory_nodes: Creating placeholder nod= e /memory@40000000 > libxl: debug: libxl_arm.c:380:make_memory_nodes: Creating placeholder nod= e /memory@200000000 > libxl: debug: libxl_arm.c:871:libxl__arch_domain_init_hw_description: fdt= total size 1442 > domainbuilder: detail: xc_dom_devicetree_mem: called > domainbuilder: detail: xc_dom_mem_init: mem 128 MB, pages 0x8000 pages, 4= k each > domainbuilder: detail: xc_dom_mem_init: 0x8000 pages > domainbuilder: detail: xc_dom_boot_mem_init: called > domainbuilder: detail: set_mode: guest xen-3.0-aarch64, address size 64 > domainbuilder: detail: xc_dom_malloc=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0= =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0: 256 kB > domainbuilder: detail: populate_guest_memory: populating RAM @ 0000000040= 000000-0000000048000000 (128MB) > domainbuilder: detail: populate_one_size: populated 0x40/0x40 entries wit= h shift 9 > domainbuilder: detail: arch_setup_meminit: placing boot modules at 0x47df= 6000 > domainbuilder: detail: arch_setup_meminit: ramdisk: 0x47df6000 -> 0x47fff= 000 > domainbuilder: detail: arch_setup_meminit: devicetree: 0x47fff000 -> 0x48= 000000 > libxl: debug: libxl_arm.c:936:libxl__arch_domain_finalise_hw_description:= /chosen updating initrd properties to cover 47df6000-47fff000 > libxl: debug: libxl_arm.c:902:finalise_one_memory_node: Populating placeh= older node /memory@40000000 > libxl: debug: libxl_arm.c:896:finalise_one_memory_node: Nopping out place= holder node /memory@200000000 > domainbuilder: detail: xc_dom_build_image: called > domainbuilder: detail: xc_dom_alloc_segment:=C2=A0=C2=A0=C2=A0kernel=C2= =A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0: 0x40080000 -> 0x41443000=C2=A0=C2= =A0(pfn 0x40080 + 0x13c3 pages) > domainbuilder: detail: xc_dom_malloc=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0= =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0: 118 kB > domainbuilder: detail: xc_dom_pfn_to_ptr_retcount: domU mapping: pfn 0x40= 080+0x13c3 at 0x7f8d6e0000 > domainbuilder: detail: xc_dom_load_zimage_kernel: called > domainbuilder: detail: xc_dom_load_zimage_kernel: kernel seg 0x40080000-0= x41443000 > domainbuilder: detail: xc_dom_load_zimage_kernel: copy 20719136 bytes fro= m blob 0x7f8eced000 to dst 0x7f8d6e0000 > domainbuilder: detail: xc_dom_alloc_segment:=C2=A0=C2=A0=C2=A0ramdisk=C2= =A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0: 0x47df6000 -> 0x47fff000=C2=A0=C2=A0(pfn= 0x47df6 + 0x209 pages) > domainbuilder: detail: xc_dom_pfn_to_ptr_retcount: domU mapping: pfn 0x47= df6+0x209 at 0x7f8d4d7000 > domainbuilder: detail: xc_dom_alloc_segment:=C2=A0=C2=A0=C2=A0devicetree= =C2=A0=C2=A0=C2=A0: 0x47fff000 -> 0x48000000=C2=A0=C2=A0(pfn 0x47fff + 0x1 = pages) > domainbuilder: detail: xc_dom_pfn_to_ptr_retcount: domU mapping: pfn 0x47= fff+0x1 at 0x7f903dc000 > domainbuilder: detail: alloc_magic_pages: called > domainbuilder: detail: count_pgtables_arm: called > domainbuilder: detail: xc_dom_build_image=C2=A0=C2=A0: virt_alloc_end : 0= x48000000 > domainbuilder: detail: xc_dom_build_image=C2=A0=C2=A0: virt_pgtab_end : 0= x0 > 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= -aarch64 <=3D matches > domainbuilder: detail: xc_dom_compat_check: supported guest type: xen-3.0= -armv7l > domainbuilder: detail: setup_pgtables_arm: called > domainbuilder: detail: clear_page: pfn 0x39000, mfn 0x39000 > domainbuilder: detail: clear_page: pfn 0x39001, mfn 0x39001 > domainbuilder: detail: start_info_arm: called > domainbuilder: detail: domain builder memory footprint > domainbuilder: detail:=C2=A0=C2=A0=C2=A0=C2=A0allocated > domainbuilder: detail:=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0malloc=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= : 389 kB > domainbuilder: detail:=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0anon mmap= =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0: 0 bytes > domainbuilder: detail:=C2=A0=C2=A0=C2=A0=C2=A0mapped > domainbuilder: detail:=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0file mmap= =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0: 22314 kB > domainbuilder: detail:=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0domU mmap= =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0: 22324 kB > domainbuilder: detail: vcpu_arm64: called > domainbuilder: detail: DTB 47fff000 > domainbuilder: detail: Initial state CPSR 0x1c5 PC 0x40080000 > domainbuilder: detail: launch_vm: called, ctxt=3D0x7f903de004 > domainbuilder: detail: xc_dom_gnttab_hvm_seed: called, pfn=3D0x38000 > domainbuilder: detail: xc_dom_release: called > (XEN) grant_table.c:411:d0v1 Bad flags (0) or dom (0). (expected dom 0) Line 411 of this file in 4.6 isn't this log message (which appears to be around line 523. What exact version of Xen are you running? Have you patched it in any way? > libxl: debug: libxl_event.c:2193:libxl__ao_progress_report: ao 0x435300: = progress report: callback queued aop=3D0x4398d0 > libxl: debug: libxl_event.c:1874:libxl__ao_complete: ao 0x435300: complet= e, rc=3D0 > libxl: debug: libxl_event.c:1410:egc_run_callbacks: ao 0x435300: progress= report: callback aop=3D0x4398d0 > libxl: debug: libxl_create.c:1583:do_domain_create: ao 0x435300: inprogre= ss: poller=3D0x434ba0, flags=3Dic > libxl: debug: libxl_event.c:1843:libxl__ao__destroy: ao 0x435300: destroy > xenconsole: Could not read tty from store: Success --=-Sr1YUXDVLIsNfWmGapeO Content-Disposition: attachment; filename="vm1.cfg" Content-Type: text/plain; name="vm1.cfg"; charset="us-ascii" Content-Transfer-Encoding: 7bit # Guest name name = "VM1" # Guest console serial = 'pty' # 128-bit UUID for the domain as a hexadecimal number. # Use "uuidgen" to generate one if required. # The default behavior is to generate a new UUID each time the guest is started. #uuid = "XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX" # Kernel image to boot kernel = "/boot/Image" # Ramdisk (optional) ramdisk = "/boot/rootfs.cpio.gz" # Kernel command line options extra = "earlycon=xenboot hostname=VM1 console=hvc1 root=/dev/ram rw init=/init nosoftlockup rcu_cpu_stall_suppress=1" # Initial memory allocation (MB) memory = 128 # Maximum memory (MB) # If this is greater than `memory' then the slack will start ballooned # (this assumes guest kernel support for ballooning) #maxmem = 512 # Number of VCPUS vcpus = 1 --=-Sr1YUXDVLIsNfWmGapeO Content-Disposition: attachment; filename="DomU_failure_logs.txt" Content-Type: text/plain; name="DomU_failure_logs.txt"; charset="us-ascii" Content-Transfer-Encoding: 7bit libxl: verbose: libxl_create.c:101:libxl__domain_build_info_setdefault: qemu-xen is unavailable, use qemu-xen-traditional instead: No such file or directory libxl: debug: libxl_create.c:945:initiate_domain_create: running bootloader libxl: debug: libxl_bootloader.c:330:libxl__bootloader_run: no bootloader configured, using user supplied kernel libxl: debug: libxl_event.c:691:libxl__ev_xswatch_deregister: watch w=0x435cf0: deregister unregistered domainbuilder: detail: xc_dom_allocate: cmdline="earlycon=xenboot hostname=VM1 console=hvc1 root=/dev/ram nosoftlockup rcu_cpu_stall_suppress=1", features="(null)" libxl: debug: libxl_dom.c:631:libxl__build_pv: pv kernel mapped 0 path /boot/Image domainbuilder: detail: xc_dom_kernel_file: filename="/boot/Image" domainbuilder: detail: ATUL - xc_dom_malloc_filemap: failed (on file `/boot/Image') domainbuilder: detail: xc_dom_malloc_filemap : 20233 kB domainbuilder: detail: xc_dom_ramdisk_file: filename="/boot/rootfs.cpio.gz" domainbuilder: detail: ATUL - xc_dom_malloc_filemap: failed (on file `/boot/rootfs.cpio.gz') domainbuilder: detail: xc_dom_malloc_filemap : 2080 kB domainbuilder: detail: xc_dom_boot_xen_init: ver 4.6, caps xen-3.0-aarch64 xen-3.0-armv7l domainbuilder: detail: xc_dom_rambase_init: RAM starts at 40000 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 zImage (ARM64) loader ... domainbuilder: detail: loader probe OK domainbuilder: detail: xc_dom_parse_zimage64_kernel: called domainbuilder: detail: xc_dom_parse_zimage64_kernel: xen-3.0-aarch64: 0x40080000 -> 0x41442620 libxl: debug: libxl_arm.c:776:libxl__arch_domain_init_hw_description: constructing DTB for Xen version 4.6 guest libxl: debug: libxl_arm.c:777:libxl__arch_domain_init_hw_description: - vGIC version: V3 libxl: debug: libxl_arm.c:273:make_chosen_node: /chosen/bootargs = earlycon=xenboot hostname=VM1 console=hvc1 root=/dev/ram nosoftlockup rcu_cpu_stall_suppress=1 libxl: debug: libxl_arm.c:280:make_chosen_node: /chosen adding placeholder linux,initrd properties libxl: debug: libxl_arm.c:380:make_memory_nodes: Creating placeholder node /memory@40000000 libxl: debug: libxl_arm.c:380:make_memory_nodes: Creating placeholder node /memory@200000000 libxl: debug: libxl_arm.c:871:libxl__arch_domain_init_hw_description: fdt total size 1442 domainbuilder: detail: xc_dom_devicetree_mem: called domainbuilder: detail: xc_dom_mem_init: mem 128 MB, pages 0x8000 pages, 4k each domainbuilder: detail: xc_dom_mem_init: 0x8000 pages domainbuilder: detail: xc_dom_boot_mem_init: called domainbuilder: detail: set_mode: guest xen-3.0-aarch64, address size 64 domainbuilder: detail: xc_dom_malloc : 256 kB domainbuilder: detail: populate_guest_memory: populating RAM @ 0000000040000000-0000000048000000 (128MB) domainbuilder: detail: populate_one_size: populated 0x40/0x40 entries with shift 9 domainbuilder: detail: arch_setup_meminit: placing boot modules at 0x47df6000 domainbuilder: detail: arch_setup_meminit: ramdisk: 0x47df6000 -> 0x47fff000 domainbuilder: detail: arch_setup_meminit: devicetree: 0x47fff000 -> 0x48000000 libxl: debug: libxl_arm.c:936:libxl__arch_domain_finalise_hw_description: /chosen updating initrd properties to cover 47df6000-47fff000 libxl: debug: libxl_arm.c:902:finalise_one_memory_node: Populating placeholder node /memory@40000000 libxl: debug: libxl_arm.c:896:finalise_one_memory_node: Nopping out placeholder node /memory@200000000 domainbuilder: detail: xc_dom_build_image: called domainbuilder: detail: xc_dom_alloc_segment: kernel : 0x40080000 -> 0x41443000 (pfn 0x40080 + 0x13c3 pages) domainbuilder: detail: xc_dom_malloc : 118 kB domainbuilder: detail: xc_dom_pfn_to_ptr_retcount: domU mapping: pfn 0x40080+0x13c3 at 0x7f8d6e0000 domainbuilder: detail: xc_dom_load_zimage_kernel: called domainbuilder: detail: xc_dom_load_zimage_kernel: kernel seg 0x40080000-0x41443000 domainbuilder: detail: xc_dom_load_zimage_kernel: copy 20719136 bytes from blob 0x7f8eced000 to dst 0x7f8d6e0000 domainbuilder: detail: xc_dom_alloc_segment: ramdisk : 0x47df6000 -> 0x47fff000 (pfn 0x47df6 + 0x209 pages) domainbuilder: detail: xc_dom_pfn_to_ptr_retcount: domU mapping: pfn 0x47df6+0x209 at 0x7f8d4d7000 domainbuilder: detail: xc_dom_alloc_segment: devicetree : 0x47fff000 -> 0x48000000 (pfn 0x47fff + 0x1 pages) domainbuilder: detail: xc_dom_pfn_to_ptr_retcount: domU mapping: pfn 0x47fff+0x1 at 0x7f903dc000 domainbuilder: detail: alloc_magic_pages: called domainbuilder: detail: count_pgtables_arm: called domainbuilder: detail: xc_dom_build_image : virt_alloc_end : 0x48000000 domainbuilder: detail: xc_dom_build_image : virt_pgtab_end : 0x0 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-aarch64 <= matches domainbuilder: detail: xc_dom_compat_check: supported guest type: xen-3.0-armv7l domainbuilder: detail: setup_pgtables_arm: called domainbuilder: detail: clear_page: pfn 0x39000, mfn 0x39000 domainbuilder: detail: clear_page: pfn 0x39001, mfn 0x39001 domainbuilder: detail: start_info_arm: called domainbuilder: detail: domain builder memory footprint domainbuilder: detail: allocated domainbuilder: detail: malloc : 389 kB domainbuilder: detail: anon mmap : 0 bytes domainbuilder: detail: mapped domainbuilder: detail: file mmap : 22314 kB domainbuilder: detail: domU mmap : 22324 kB domainbuilder: detail: vcpu_arm64: called domainbuilder: detail: DTB 47fff000 domainbuilder: detail: Initial state CPSR 0x1c5 PC 0x40080000 domainbuilder: detail: launch_vm: called, ctxt=0x7f903de004 domainbuilder: detail: xc_dom_gnttab_hvm_seed: called, pfn=0x38000 domainbuilder: detail: xc_dom_release: called (XEN) grant_table.c:411:d0v1 Bad flags (0) or dom (0). (expected dom 0) libxl: debug: libxl_event.c:2193:libxl__ao_progress_report: ao 0x435300: progress report: callback queued aop=0x4398d0 libxl: debug: libxl_event.c:1874:libxl__ao_complete: ao 0x435300: complete, rc=0 libxl: debug: libxl_event.c:1410:egc_run_callbacks: ao 0x435300: progress report: callback aop=0x4398d0 libxl: debug: libxl_create.c:1583:do_domain_create: ao 0x435300: inprogress: poller=0x434ba0, flags=ic libxl: debug: libxl_event.c:1843:libxl__ao__destroy: ao 0x435300: destroy xenconsole: Could not read tty from store: Success --=-Sr1YUXDVLIsNfWmGapeO Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users --=-Sr1YUXDVLIsNfWmGapeO-- From xen-users-bounces@lists.xen.org Thu Jan 07 11:42:12 2016 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 07 Jan 2016 11:42: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 1aH8wL-0001Um-Ov; Thu, 07 Jan 2016 11:41:13 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1aH8wJ-0001UO-Gc for Xen-users@lists.xen.org; Thu, 07 Jan 2016 11:41:11 +0000 Received: from [85.158.137.68] by server-8.bemta-3.messagelabs.com id E5/8D-31069-6DE4E865; Thu, 07 Jan 2016 11:41:10 +0000 X-Env-Sender: xikangjie@360.cn X-Msg-Ref: server-9.tower-31.messagelabs.com!1452166865!1818612!1 X-Originating-IP: [123.125.82.7] X-SpamReason: No, hits=-1.2 required=7.0 tests=HTML_90_100,HTML_MESSAGE, MIME_BASE64_TEXT,ML_RADAR_FP_R_14,spamassassin: X-StarScan-Received: X-StarScan-Version: 7.35.1; banners=-,-,- X-VirusChecked: Checked Received: (qmail 5473 invoked from network); 7 Jan 2016 11:41:07 -0000 Received: from mtabjsc2.360.cn (HELO mtabjsc2.360.cn) (123.125.82.7) by server-9.tower-31.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 7 Jan 2016 11:41:07 -0000 Received: from CAS2.corp.qihoo.net (cas2.corp.qihoo.net [220.181.158.130]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by mtabjsc2.360.cn (QHMAIL) with ESMTP id 5FCCC6B044A for ; Thu, 7 Jan 2016 19:32:17 +0800 (CST) Received: from EX01.corp.qihoo.net ([fe80::1c65:facd:d8aa:c20a]) by CAS2.corp.qihoo.net ([220.181.158.130]) with mapi id 14.02.0342.003; Thu, 7 Jan 2016 19:41:02 +0800 From: =?gb2312?B?z6+/tb3c?= To: "Xen-users@lists.xen.org" Thread-Topic: how to use xl create domains concurrently ? Thread-Index: AdFJQCwOro3+apnOTreceLfUindv4A== Date: Thu, 7 Jan 2016 11:41:02 +0000 Message-ID: <21D42A94174EE345809CF640696801D501B7FBEA@EX01.corp.qihoo.net> Accept-Language: zh-CN, en-US Content-Language: zh-CN X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.18.32.32] MIME-Version: 1.0 Subject: [Xen-users] how to use xl create domains concurrently ? X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============8373188664250110593==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============8373188664250110593== Content-Language: zh-CN Content-Type: multipart/alternative; boundary="_000_21D42A94174EE345809CF640696801D501B7FBEAEX01corpqihoone_" --_000_21D42A94174EE345809CF640696801D501B7FBEAEX01corpqihoone_ Content-Type: text/plain; charset="gb2312" Content-Transfer-Encoding: base64 SGksDQoNCkkgYW0gdXNpbmcgWGVuLTQuNS4xIG9uIENlbnRPUy02LjWjrCBJIGZpbmQgeGwgY3Jl YXRlIGRvbWFpbnMgc2VyaWFsbHksDQpzbyBpZiBJIGNyZWF0ZSBvbmUgZG9tYWluLCBpdCB0YWtl cyBhYm91dCA0IHNlY29uZHMsIGNyZWF0ZSAxMCBkb21haW5zLA0KaXQgd2lsbCB0YWtlcyBhYm91 dCA0MCBzZWNvbmRzLCBpdCBpcyB0b28gbG9uZywgaXMgdGhlcmUgYW55IHdheSB0byBjcmVhdGUN CmRvbWFpbnMgY29uY3VycmVudGx5ID8gb3IgYW55IHdheSB0byBjcmVhdGUgbXVsdGlwbGUgZG9t YWlucyBpbiBsZXNzIHRpbWU/DQoNClRoYW5rcyBpbiBhZHZhbmNlLA0KDQpYaSBLYW5namllDQo= --_000_21D42A94174EE345809CF640696801D501B7FBEAEX01corpqihoone_ Content-Type: text/html; charset="gb2312" Content-Transfer-Encoding: quoted-printable

= Hi,

=  

= I am using Xen-4.5.1 on CentOS-6.5=A3=AC I find xl create domains serially,

= so if I create one domain, it takes about 4 seconds, create 10 domains,

= it will takes about 40 seconds, it is too long, is there any way to create<= o:p>

= domains concurrently ? or any way to create multiple domains in less time?<= o:p>

=  

= Thanks in advance,

=  

= Xi Kangjie

--_000_21D42A94174EE345809CF640696801D501B7FBEAEX01corpqihoone_-- --===============8373188664250110593== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users --===============8373188664250110593==-- From xen-users-bounces@lists.xen.org Thu Jan 07 11:42:12 2016 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 07 Jan 2016 11:42: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 1aH8wL-0001Um-Ov; Thu, 07 Jan 2016 11:41:13 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1aH8wJ-0001UO-Gc for Xen-users@lists.xen.org; Thu, 07 Jan 2016 11:41:11 +0000 Received: from [85.158.137.68] by server-8.bemta-3.messagelabs.com id E5/8D-31069-6DE4E865; Thu, 07 Jan 2016 11:41:10 +0000 X-Env-Sender: xikangjie@360.cn X-Msg-Ref: server-9.tower-31.messagelabs.com!1452166865!1818612!1 X-Originating-IP: [123.125.82.7] X-SpamReason: No, hits=-1.2 required=7.0 tests=HTML_90_100,HTML_MESSAGE, MIME_BASE64_TEXT,ML_RADAR_FP_R_14,spamassassin: X-StarScan-Received: X-StarScan-Version: 7.35.1; banners=-,-,- X-VirusChecked: Checked Received: (qmail 5473 invoked from network); 7 Jan 2016 11:41:07 -0000 Received: from mtabjsc2.360.cn (HELO mtabjsc2.360.cn) (123.125.82.7) by server-9.tower-31.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 7 Jan 2016 11:41:07 -0000 Received: from CAS2.corp.qihoo.net (cas2.corp.qihoo.net [220.181.158.130]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by mtabjsc2.360.cn (QHMAIL) with ESMTP id 5FCCC6B044A for ; Thu, 7 Jan 2016 19:32:17 +0800 (CST) Received: from EX01.corp.qihoo.net ([fe80::1c65:facd:d8aa:c20a]) by CAS2.corp.qihoo.net ([220.181.158.130]) with mapi id 14.02.0342.003; Thu, 7 Jan 2016 19:41:02 +0800 From: =?gb2312?B?z6+/tb3c?= To: "Xen-users@lists.xen.org" Thread-Topic: how to use xl create domains concurrently ? Thread-Index: AdFJQCwOro3+apnOTreceLfUindv4A== Date: Thu, 7 Jan 2016 11:41:02 +0000 Message-ID: <21D42A94174EE345809CF640696801D501B7FBEA@EX01.corp.qihoo.net> Accept-Language: zh-CN, en-US Content-Language: zh-CN X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.18.32.32] MIME-Version: 1.0 Subject: [Xen-users] how to use xl create domains concurrently ? X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============8373188664250110593==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============8373188664250110593== Content-Language: zh-CN Content-Type: multipart/alternative; boundary="_000_21D42A94174EE345809CF640696801D501B7FBEAEX01corpqihoone_" --_000_21D42A94174EE345809CF640696801D501B7FBEAEX01corpqihoone_ Content-Type: text/plain; charset="gb2312" Content-Transfer-Encoding: base64 SGksDQoNCkkgYW0gdXNpbmcgWGVuLTQuNS4xIG9uIENlbnRPUy02LjWjrCBJIGZpbmQgeGwgY3Jl YXRlIGRvbWFpbnMgc2VyaWFsbHksDQpzbyBpZiBJIGNyZWF0ZSBvbmUgZG9tYWluLCBpdCB0YWtl cyBhYm91dCA0IHNlY29uZHMsIGNyZWF0ZSAxMCBkb21haW5zLA0KaXQgd2lsbCB0YWtlcyBhYm91 dCA0MCBzZWNvbmRzLCBpdCBpcyB0b28gbG9uZywgaXMgdGhlcmUgYW55IHdheSB0byBjcmVhdGUN CmRvbWFpbnMgY29uY3VycmVudGx5ID8gb3IgYW55IHdheSB0byBjcmVhdGUgbXVsdGlwbGUgZG9t YWlucyBpbiBsZXNzIHRpbWU/DQoNClRoYW5rcyBpbiBhZHZhbmNlLA0KDQpYaSBLYW5namllDQo= --_000_21D42A94174EE345809CF640696801D501B7FBEAEX01corpqihoone_ Content-Type: text/html; charset="gb2312" Content-Transfer-Encoding: quoted-printable

= Hi,

=  

= I am using Xen-4.5.1 on CentOS-6.5=A3=AC I find xl create domains serially,

= so if I create one domain, it takes about 4 seconds, create 10 domains,

= it will takes about 40 seconds, it is too long, is there any way to create<= o:p>

= domains concurrently ? or any way to create multiple domains in less time?<= o:p>

=  

= Thanks in advance,

=  

= Xi Kangjie

--_000_21D42A94174EE345809CF640696801D501B7FBEAEX01corpqihoone_-- --===============8373188664250110593== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users --===============8373188664250110593==-- From xen-users-bounces@lists.xen.org Thu Jan 07 11:56:36 2016 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 07 Jan 2016 11:56: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 1aH9B1-0002mn-5J; Thu, 07 Jan 2016 11:56:23 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1aH9Az-0002mf-3C for Xen-users@lists.xen.org; Thu, 07 Jan 2016 11:56:21 +0000 Received: from [85.158.143.35] by server-1.bemta-4.messagelabs.com id DB/AF-09708-4625E865; Thu, 07 Jan 2016 11:56:20 +0000 X-Env-Sender: prvs=807a36095=Ian.Campbell@citrix.com X-Msg-Ref: server-8.tower-21.messagelabs.com!1452167778!8840750!1 X-Originating-IP: [66.165.176.89] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjYuMTY1LjE3Ni44OSA9PiAyMDMwMDc=\n, received_headers: No Received headers X-StarScan-Received: X-StarScan-Version: 7.35.1; banners=-,-,- X-VirusChecked: Checked Received: (qmail 8103 invoked from network); 7 Jan 2016 11:56:19 -0000 Received: from smtp.citrix.com (HELO SMTP.CITRIX.COM) (66.165.176.89) by server-8.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 7 Jan 2016 11:56:19 -0000 X-IronPort-AV: E=Sophos;i="5.20,532,1444694400"; d="scan'208";a="323404758" Message-ID: <1452167664.21055.200.camel@citrix.com> From: Ian Campbell To: =?UTF-8?Q?=E5=B8=AD=E5=BA=B7=E6=9D=B0?= , "Xen-users@lists.xen.org" Date: Thu, 7 Jan 2016 11:54:24 +0000 In-Reply-To: <21D42A94174EE345809CF640696801D501B7FBEA@EX01.corp.qihoo.net> References: <21D42A94174EE345809CF640696801D501B7FBEA@EX01.corp.qihoo.net> X-Mailer: Evolution 3.18.2-1 MIME-Version: 1.0 X-DLP: MIA2 Subject: Re: [Xen-users] how to use xl create domains concurrently ? X-BeenThere: xen-users@lists.xen.org X-Mailman-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 T24gVGh1LCAyMDE2LTAxLTA3IGF0IDExOjQxICswMDAwLCDluK3lurfmnbAgd3JvdGU6Cj4gSGks Cj4gwqAKPiBJIGFtIHVzaW5nIFhlbi00LjUuMSBvbiBDZW50T1MtNi4177yMIEkgZmluZCB4bCBj cmVhdGUgZG9tYWlucyBzZXJpYWxseSwKPiBzbyBpZiBJIGNyZWF0ZSBvbmUgZG9tYWluLCBpdCB0 YWtlcyBhYm91dCA0IHNlY29uZHMsIGNyZWF0ZSAxMCBkb21haW5zLAo+IGl0IHdpbGwgdGFrZXMg YWJvdXQgNDAgc2Vjb25kcywgaXQgaXMgdG9vIGxvbmcsIGlzIHRoZXJlIGFueSB3YXkgdG8gY3Jl YXRlCj4gZG9tYWlucyBjb25jdXJyZW50bHkgPyBvciBhbnkgd2F5IHRvIGNyZWF0ZSBtdWx0aXBs ZSBkb21haW5zIGluIGxlc3MgdGltZT8KCnhsIGhhcyBhdCBsZWFzdCBvbmUgYmlnIGxvY2sgYXJv dW5kIGRvbWFpbiBjcmVhdGlvbiAodG8gZG8gd2l0aCBkb20wIG1lbW9yeQpiYWxsb29uaW5nIElJ UkMpLCB0aGVyZSBtYXkgYWxzbyBiZSBvdGhlcnMgaW4geGwgYW5kIGxpYnhsLgoKUmVzb2x2aW5n IHRoaXMgaGFzIGJlZW4gYSBsb25nIHN0YW5kaW5nIFRPRE8gZGV2ZWxvcG1lbnQgaXRlbSwgYnV0 IEFGQUlLIG5vCmJvZHkgaXMgd29ya2luZyBvbiBpdC4KCklmIHlvdSBhcmUgaW50ZXJlc3RlZCBp biB0YWNrbGluZyB0aGlzIHByb2JsZW0gdGhlbiBJIHdvdWxkIHN1Z2dlc3QKYnJpbmdpbmcgaXQg dXAgb24geGVuLWRldmVsIHdoZXJlIGhvcGVmdWxseSBvdGhlciBmb2xrcyB3aWxsIHJlbWVtYmVy IG1vcmUKb2YgdGhlIGRldGFpbHMgcmVnYXJkaW5nIHRoZSBjdXJyZW50IHNpdHVhdGlvbiBhbmQg cGxhbm5lZCBpbXByb3ZlbWVudHMuCgpJYW4uCgoKX19fX19fX19fX19fX19fX19fX19fX19fX19f X19fX19fX19fX19fX19fX19fX18KWGVuLXVzZXJzIG1haWxpbmcgbGlzdApYZW4tdXNlcnNAbGlz dHMueGVuLm9yZwpodHRwOi8vbGlzdHMueGVuLm9yZy94ZW4tdXNlcnM= From xen-users-bounces@lists.xen.org Thu Jan 07 11:56:36 2016 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 07 Jan 2016 11:56: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 1aH9B1-0002mn-5J; Thu, 07 Jan 2016 11:56:23 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1aH9Az-0002mf-3C for Xen-users@lists.xen.org; Thu, 07 Jan 2016 11:56:21 +0000 Received: from [85.158.143.35] by server-1.bemta-4.messagelabs.com id DB/AF-09708-4625E865; Thu, 07 Jan 2016 11:56:20 +0000 X-Env-Sender: prvs=807a36095=Ian.Campbell@citrix.com X-Msg-Ref: server-8.tower-21.messagelabs.com!1452167778!8840750!1 X-Originating-IP: [66.165.176.89] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjYuMTY1LjE3Ni44OSA9PiAyMDMwMDc=\n, received_headers: No Received headers X-StarScan-Received: X-StarScan-Version: 7.35.1; banners=-,-,- X-VirusChecked: Checked Received: (qmail 8103 invoked from network); 7 Jan 2016 11:56:19 -0000 Received: from smtp.citrix.com (HELO SMTP.CITRIX.COM) (66.165.176.89) by server-8.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 7 Jan 2016 11:56:19 -0000 X-IronPort-AV: E=Sophos;i="5.20,532,1444694400"; d="scan'208";a="323404758" Message-ID: <1452167664.21055.200.camel@citrix.com> From: Ian Campbell To: =?UTF-8?Q?=E5=B8=AD=E5=BA=B7=E6=9D=B0?= , "Xen-users@lists.xen.org" Date: Thu, 7 Jan 2016 11:54:24 +0000 In-Reply-To: <21D42A94174EE345809CF640696801D501B7FBEA@EX01.corp.qihoo.net> References: <21D42A94174EE345809CF640696801D501B7FBEA@EX01.corp.qihoo.net> X-Mailer: Evolution 3.18.2-1 MIME-Version: 1.0 X-DLP: MIA2 Subject: Re: [Xen-users] how to use xl create domains concurrently ? X-BeenThere: xen-users@lists.xen.org X-Mailman-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 T24gVGh1LCAyMDE2LTAxLTA3IGF0IDExOjQxICswMDAwLCDluK3lurfmnbAgd3JvdGU6Cj4gSGks Cj4gwqAKPiBJIGFtIHVzaW5nIFhlbi00LjUuMSBvbiBDZW50T1MtNi4177yMIEkgZmluZCB4bCBj cmVhdGUgZG9tYWlucyBzZXJpYWxseSwKPiBzbyBpZiBJIGNyZWF0ZSBvbmUgZG9tYWluLCBpdCB0 YWtlcyBhYm91dCA0IHNlY29uZHMsIGNyZWF0ZSAxMCBkb21haW5zLAo+IGl0IHdpbGwgdGFrZXMg YWJvdXQgNDAgc2Vjb25kcywgaXQgaXMgdG9vIGxvbmcsIGlzIHRoZXJlIGFueSB3YXkgdG8gY3Jl YXRlCj4gZG9tYWlucyBjb25jdXJyZW50bHkgPyBvciBhbnkgd2F5IHRvIGNyZWF0ZSBtdWx0aXBs ZSBkb21haW5zIGluIGxlc3MgdGltZT8KCnhsIGhhcyBhdCBsZWFzdCBvbmUgYmlnIGxvY2sgYXJv dW5kIGRvbWFpbiBjcmVhdGlvbiAodG8gZG8gd2l0aCBkb20wIG1lbW9yeQpiYWxsb29uaW5nIElJ UkMpLCB0aGVyZSBtYXkgYWxzbyBiZSBvdGhlcnMgaW4geGwgYW5kIGxpYnhsLgoKUmVzb2x2aW5n IHRoaXMgaGFzIGJlZW4gYSBsb25nIHN0YW5kaW5nIFRPRE8gZGV2ZWxvcG1lbnQgaXRlbSwgYnV0 IEFGQUlLIG5vCmJvZHkgaXMgd29ya2luZyBvbiBpdC4KCklmIHlvdSBhcmUgaW50ZXJlc3RlZCBp biB0YWNrbGluZyB0aGlzIHByb2JsZW0gdGhlbiBJIHdvdWxkIHN1Z2dlc3QKYnJpbmdpbmcgaXQg dXAgb24geGVuLWRldmVsIHdoZXJlIGhvcGVmdWxseSBvdGhlciBmb2xrcyB3aWxsIHJlbWVtYmVy IG1vcmUKb2YgdGhlIGRldGFpbHMgcmVnYXJkaW5nIHRoZSBjdXJyZW50IHNpdHVhdGlvbiBhbmQg cGxhbm5lZCBpbXByb3ZlbWVudHMuCgpJYW4uCgoKX19fX19fX19fX19fX19fX19fX19fX19fX19f X19fX19fX19fX19fX19fX19fX18KWGVuLXVzZXJzIG1haWxpbmcgbGlzdApYZW4tdXNlcnNAbGlz dHMueGVuLm9yZwpodHRwOi8vbGlzdHMueGVuLm9yZy94ZW4tdXNlcnM= From xen-users-bounces@lists.xen.org Thu Jan 07 12:00:06 2016 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 07 Jan 2016 12:00: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 1aH9ES-0002zT-Eo; Thu, 07 Jan 2016 11:59:56 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1aH9ER-0002zK-AG for Xen-users@lists.xen.org; Thu, 07 Jan 2016 11:59:55 +0000 Received: from [85.158.143.35] by server-1.bemta-4.messagelabs.com id 28/44-09708-A335E865; Thu, 07 Jan 2016 11:59:54 +0000 X-Env-Sender: linux@thehobsons.co.uk X-Msg-Ref: server-16.tower-21.messagelabs.com!1452167993!4459583!1 X-Originating-IP: [81.174.135.208] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 7.35.1; banners=-,-,- X-VirusChecked: Checked Received: (qmail 31101 invoked from network); 7 Jan 2016 11:59:54 -0000 Received: from patsy.thehobsons.co.uk (HELO patsy.thehobsons.co.uk) (81.174.135.208) by server-16.tower-21.messagelabs.com with DHE-RSA-AES256-GCM-SHA384 encrypted SMTP; 7 Jan 2016 11:59:54 -0000 X-Virus-Scanned: Debian amavisd-new at patsy.thehobsons.co.uk Received: from [192.168.7.10] (wifi2.furness.net [195.8.169.130]) by patsy.thehobsons.co.uk (Postfix) with ESMTPSA id DFDC81A074 for ; Thu, 7 Jan 2016 11:59:49 +0000 (UTC) Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\)) From: Simon Hobson In-Reply-To: <21D42A94174EE345809CF640696801D501B7FBEA@EX01.corp.qihoo.net> Date: Thu, 7 Jan 2016 11:59:43 +0000 Message-Id: References: <21D42A94174EE345809CF640696801D501B7FBEA@EX01.corp.qihoo.net> To: "xen-users@lists.xen.org" X-Mailer: Apple Mail (2.1510) Subject: Re: [Xen-users] how to use xl create domains concurrently ? X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: 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 find xl create domains serially, > so if I create one domain, it takes about 4 seconds, create 10 domains, > it will takes about 40 seconds, it is too long, is there any way to create > domains concurrently ? xl create ... & xl create ... & That should get you your terminal back straight away - I've no idea if there are any locking issues to be aware of. > or any way to create multiple domains in less time? I suspect that with the general overhead of creating domains, it might not make much difference. Sometimes, doing things in parallel can take longer than doing them serially. YMMV. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Thu Jan 07 12:00:06 2016 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 07 Jan 2016 12:00: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 1aH9ES-0002zT-Eo; Thu, 07 Jan 2016 11:59:56 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1aH9ER-0002zK-AG for Xen-users@lists.xen.org; Thu, 07 Jan 2016 11:59:55 +0000 Received: from [85.158.143.35] by server-1.bemta-4.messagelabs.com id 28/44-09708-A335E865; Thu, 07 Jan 2016 11:59:54 +0000 X-Env-Sender: linux@thehobsons.co.uk X-Msg-Ref: server-16.tower-21.messagelabs.com!1452167993!4459583!1 X-Originating-IP: [81.174.135.208] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 7.35.1; banners=-,-,- X-VirusChecked: Checked Received: (qmail 31101 invoked from network); 7 Jan 2016 11:59:54 -0000 Received: from patsy.thehobsons.co.uk (HELO patsy.thehobsons.co.uk) (81.174.135.208) by server-16.tower-21.messagelabs.com with DHE-RSA-AES256-GCM-SHA384 encrypted SMTP; 7 Jan 2016 11:59:54 -0000 X-Virus-Scanned: Debian amavisd-new at patsy.thehobsons.co.uk Received: from [192.168.7.10] (wifi2.furness.net [195.8.169.130]) by patsy.thehobsons.co.uk (Postfix) with ESMTPSA id DFDC81A074 for ; Thu, 7 Jan 2016 11:59:49 +0000 (UTC) Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\)) From: Simon Hobson In-Reply-To: <21D42A94174EE345809CF640696801D501B7FBEA@EX01.corp.qihoo.net> Date: Thu, 7 Jan 2016 11:59:43 +0000 Message-Id: References: <21D42A94174EE345809CF640696801D501B7FBEA@EX01.corp.qihoo.net> To: "xen-users@lists.xen.org" X-Mailer: Apple Mail (2.1510) Subject: Re: [Xen-users] how to use xl create domains concurrently ? X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: 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 find xl create domains serially, > so if I create one domain, it takes about 4 seconds, create 10 domains, > it will takes about 40 seconds, it is too long, is there any way to create > domains concurrently ? xl create ... & xl create ... & That should get you your terminal back straight away - I've no idea if there are any locking issues to be aware of. > or any way to create multiple domains in less time? I suspect that with the general overhead of creating domains, it might not make much difference. Sometimes, doing things in parallel can take longer than doing them serially. YMMV. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Thu Jan 07 13:55:39 2016 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 07 Jan 2016 13:55: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 1aHB1W-0001n2-VZ; Thu, 07 Jan 2016 13:54:42 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1aGvgJ-0000Zx-Re for Xen-users@lists.xen.org; Wed, 06 Jan 2016 21:31:47 +0000 Received: from [85.158.143.35] by server-3.bemta-4.messagelabs.com id FB/A6-31122-3C78D865; Wed, 06 Jan 2016 21:31:47 +0000 X-Env-Sender: alvin@netvel.net X-Msg-Ref: server-8.tower-21.messagelabs.com!1452115903!8732385!1 X-Originating-IP: [54.236.96.217] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 7.35.1; banners=-,-,- X-VirusChecked: Checked Received: (qmail 5311 invoked from network); 6 Jan 2016 21:31:44 -0000 Received: from mail.netvel.net (HELO mail.netvel.net) (54.236.96.217) by server-8.tower-21.messagelabs.com with DHE-RSA-AES256-GCM-SHA384 encrypted SMTP; 6 Jan 2016 21:31:44 -0000 Received: from alvinsworkstation.netvel.net (unknown [206.108.5.187]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by mail.netvel.net (Postfix) with ESMTPSA id 53C3340642 for ; Wed, 6 Jan 2016 16:32:27 -0500 (EST) To: Xen-users@lists.xen.org From: Alvin Starr Message-ID: <568D87BE.9010708@netvel.net> Date: Wed, 6 Jan 2016 16:31:42 -0500 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.3.0 MIME-Version: 1.0 X-Mailman-Approved-At: Thu, 07 Jan 2016 13:54:40 +0000 Subject: [Xen-users] Dom0 and NUMA. X-BeenThere: xen-users@lists.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 How would I pass the NUMA config to Dom0. It seems that xen flattens the config so all the processors are my xencmdline is set to: loglvl=info guest_loglvl=info com1=115200,8n1,0x3e8,5 console=com1,vga nmi=dom0 dom0_nodes=0,1,2,3 numa=on sched_smt_power_savings=true -- Alvin Starr || voice: (905)513-7688 Netvel Inc. || Cell: (416)806-0133 alvin@netvel.net || _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Thu Jan 07 13:55:39 2016 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 07 Jan 2016 13:55: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 1aHB1W-0001mp-2q; Thu, 07 Jan 2016 13:54:42 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1aGut1-0007S6-O9 for Xen-users@lists.xen.org; Wed, 06 Jan 2016 20:40:51 +0000 Received: from [85.158.143.35] by server-3.bemta-4.messagelabs.com id 34/1E-31122-3DB7D865; Wed, 06 Jan 2016 20:40:51 +0000 X-Env-Sender: alvin@netvel.net X-Msg-Ref: server-4.tower-21.messagelabs.com!1452112847!8729686!1 X-Originating-IP: [54.236.96.217] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 7.35.1; banners=-,-,- X-VirusChecked: Checked Received: (qmail 50125 invoked from network); 6 Jan 2016 20:40:48 -0000 Received: from mail.netvel.net (HELO mail.netvel.net) (54.236.96.217) by server-4.tower-21.messagelabs.com with DHE-RSA-AES256-GCM-SHA384 encrypted SMTP; 6 Jan 2016 20:40:48 -0000 Received: from alvinsworkstation.netvel.net (unknown [206.108.5.187]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by mail.netvel.net (Postfix) with ESMTPSA id 4AA4F40642 for ; Wed, 6 Jan 2016 15:41:31 -0500 (EST) To: Xen-users@lists.xen.org From: Alvin Starr Message-ID: <568D7BCE.1070707@netvel.net> Date: Wed, 6 Jan 2016 15:40:46 -0500 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.3.0 MIME-Version: 1.0 X-Mailman-Approved-At: Thu, 07 Jan 2016 13:54:39 +0000 Subject: [Xen-users] MCA/MCE and EDAC. X-BeenThere: xen-users@lists.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 an AMD system that kicks out a correctable memory error on occasion and I can see it in the xen-dmesg. How would I get the errors propagated up into dom0 via EDAC since that is the only error mechanism supported by the AMD cpus? -- Alvin Starr || voice: (905)513-7688 Netvel Inc. || Cell: (416)806-0133 alvin@netvel.net || _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Thu Jan 07 13:55:39 2016 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 07 Jan 2016 13:55: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 1aHB1W-0001n2-VZ; Thu, 07 Jan 2016 13:54:42 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1aGvgJ-0000Zx-Re for Xen-users@lists.xen.org; Wed, 06 Jan 2016 21:31:47 +0000 Received: from [85.158.143.35] by server-3.bemta-4.messagelabs.com id FB/A6-31122-3C78D865; Wed, 06 Jan 2016 21:31:47 +0000 X-Env-Sender: alvin@netvel.net X-Msg-Ref: server-8.tower-21.messagelabs.com!1452115903!8732385!1 X-Originating-IP: [54.236.96.217] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 7.35.1; banners=-,-,- X-VirusChecked: Checked Received: (qmail 5311 invoked from network); 6 Jan 2016 21:31:44 -0000 Received: from mail.netvel.net (HELO mail.netvel.net) (54.236.96.217) by server-8.tower-21.messagelabs.com with DHE-RSA-AES256-GCM-SHA384 encrypted SMTP; 6 Jan 2016 21:31:44 -0000 Received: from alvinsworkstation.netvel.net (unknown [206.108.5.187]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by mail.netvel.net (Postfix) with ESMTPSA id 53C3340642 for ; Wed, 6 Jan 2016 16:32:27 -0500 (EST) To: Xen-users@lists.xen.org From: Alvin Starr Message-ID: <568D87BE.9010708@netvel.net> Date: Wed, 6 Jan 2016 16:31:42 -0500 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.3.0 MIME-Version: 1.0 X-Mailman-Approved-At: Thu, 07 Jan 2016 13:54:40 +0000 Subject: [Xen-users] Dom0 and NUMA. X-BeenThere: xen-users@lists.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 How would I pass the NUMA config to Dom0. It seems that xen flattens the config so all the processors are my xencmdline is set to: loglvl=info guest_loglvl=info com1=115200,8n1,0x3e8,5 console=com1,vga nmi=dom0 dom0_nodes=0,1,2,3 numa=on sched_smt_power_savings=true -- Alvin Starr || voice: (905)513-7688 Netvel Inc. || Cell: (416)806-0133 alvin@netvel.net || _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Thu Jan 07 13:55:39 2016 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 07 Jan 2016 13:55: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 1aHB1W-0001mp-2q; Thu, 07 Jan 2016 13:54:42 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1aGut1-0007S6-O9 for Xen-users@lists.xen.org; Wed, 06 Jan 2016 20:40:51 +0000 Received: from [85.158.143.35] by server-3.bemta-4.messagelabs.com id 34/1E-31122-3DB7D865; Wed, 06 Jan 2016 20:40:51 +0000 X-Env-Sender: alvin@netvel.net X-Msg-Ref: server-4.tower-21.messagelabs.com!1452112847!8729686!1 X-Originating-IP: [54.236.96.217] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 7.35.1; banners=-,-,- X-VirusChecked: Checked Received: (qmail 50125 invoked from network); 6 Jan 2016 20:40:48 -0000 Received: from mail.netvel.net (HELO mail.netvel.net) (54.236.96.217) by server-4.tower-21.messagelabs.com with DHE-RSA-AES256-GCM-SHA384 encrypted SMTP; 6 Jan 2016 20:40:48 -0000 Received: from alvinsworkstation.netvel.net (unknown [206.108.5.187]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by mail.netvel.net (Postfix) with ESMTPSA id 4AA4F40642 for ; Wed, 6 Jan 2016 15:41:31 -0500 (EST) To: Xen-users@lists.xen.org From: Alvin Starr Message-ID: <568D7BCE.1070707@netvel.net> Date: Wed, 6 Jan 2016 15:40:46 -0500 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.3.0 MIME-Version: 1.0 X-Mailman-Approved-At: Thu, 07 Jan 2016 13:54:39 +0000 Subject: [Xen-users] MCA/MCE and EDAC. X-BeenThere: xen-users@lists.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 an AMD system that kicks out a correctable memory error on occasion and I can see it in the xen-dmesg. How would I get the errors propagated up into dom0 via EDAC since that is the only error mechanism supported by the AMD cpus? -- Alvin Starr || voice: (905)513-7688 Netvel Inc. || Cell: (416)806-0133 alvin@netvel.net || _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Thu Jan 07 14:00:26 2016 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 07 Jan 2016 14: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 1aHB6s-0002IS-Fk; Thu, 07 Jan 2016 14:00:14 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1aHB6q-0002IK-OT for Xen-users@lists.xen.org; Thu, 07 Jan 2016 14:00:12 +0000 Received: from [85.158.143.35] by server-2.bemta-4.messagelabs.com id 83/D5-08977-C6F6E865; Thu, 07 Jan 2016 14:00:12 +0000 X-Env-Sender: prvs=807a36095=Ian.Campbell@citrix.com X-Msg-Ref: server-5.tower-21.messagelabs.com!1452175209!8897117!1 X-Originating-IP: [66.165.176.89] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjYuMTY1LjE3Ni44OSA9PiAyMDMwMDc=\n, received_headers: No Received headers X-StarScan-Received: X-StarScan-Version: 7.35.1; banners=-,-,- X-VirusChecked: Checked Received: (qmail 13221 invoked from network); 7 Jan 2016 14:00:11 -0000 Received: from smtp.citrix.com (HELO SMTP.CITRIX.COM) (66.165.176.89) by server-5.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 7 Jan 2016 14:00:11 -0000 X-IronPort-AV: E=Sophos;i="5.20,533,1444694400"; d="scan'208";a="323428627" Message-ID: <1452175207.21055.219.camel@citrix.com> From: Ian Campbell To: Peng Fan , Date: Thu, 7 Jan 2016 14:00:07 +0000 In-Reply-To: <20160107065013.GA29626@linux-7smt.suse> References: <20160107065013.GA29626@linux-7smt.suse> X-Mailer: Evolution 3.18.2-1 MIME-Version: 1.0 X-DLP: MIA1 Subject: Re: [Xen-users] SMMU Question for passthrough device X-BeenThere: xen-users@lists.xen.org X-Mailman-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 T24gVGh1LCAyMDE2LTAxLTA3IGF0IDE0OjUwICswODAwLCBQZW5nIEZhbiB3cm90ZToKPiBIaSBl eHBlcnRzLAo+IAo+IFRoZXJlIGFyZSB0d28gbGludXggb3MgcnVubmluZyBvbiBteSBBUk02NCBw bGF0Zm9ybS4gTm93IEkgd2FudCB0byBwYXNzdGhyb3VnaAo+IGEgcGxhdGZvcm0gZGV2aWNlKHNk IGNvbnRyb2xsZXIpIHRvIERvbVUgdG8gbGV0IERvbVUgY2FuIGRpcmVjdGx5IGFjY2VzcyB0aGUK PiBleHRlcm5hbCBTRCBjYXJkLiBUaGUgc2QgY29udHJvbGxlciBzdXBwb3J0cyBETUEuIFRoZSBz ZCBjb250cm9sbGVyIGRyaXZlcgo+IHdvcmsgd2VsbCBpbiBIb3N0IExpbnV4Lgo+IAo+IFNvIEkg aGF2ZSBhIHF1ZXN0aW9uIGhvdyBEb21VIERNQSBpbnRlcmFjdHMgd2l0aCBTTU1VIGFuZCBmaW5h bGx5IGFjY2Vzcwo+IG1lbW9yeT8KCkknbSBub3QgdGVycmlibHkgZmFtaWxpYXIgd2l0aCB0aGUg U01NVSBzdHVmZiBvbiBYZW4sIGJ1dCBJIHNoYWxsIHRyeS4KCj4gVGhlcmUgYXJlIDMgZG1hX21h cF9vcHMgaW4gbGludXggYXJjaC9hcm02NC9tbS9kbWEtbWFwcGluZy5jCj4gc3RhdGljIHN0cnVj dCBkbWFfbWFwX29wcyBpb21tdV9kbWFfb3BzCj4gc3RhdGljIHN0cnVjdCBkbWFfbWFwX29wcyBz d2lvdGxiX2RtYV9vcHMKPiBzdHJ1Y3QgZG1hX21hcF9vcHMgZHVtbXlfZG1hX29wcwo+IAo+IFNp bmNlIHNtbXUgd2lsbCBiZSBhc3NpZ25lZCB0byBYRU4sIGxpbnV4IGtlcm5lbCB3aWxsIG5vdCB1 c2UKPiBpb21tdV9kbWFfb3BzLiBTbyBzd2lvdGxiX2RtYV9vcHMgd2lsbCBiZSB1c2VkIGZvciBE b21VLiBCdXQgSSBjYW4gbm90IGZpbmQKPiBvdXQgaG93IHN3aW90bGJfZG1hX29wcyBpbnRlcmFj dHMgd2l0aCBTTU1VLgoKQUZBSUsgaXQgZG9lc24ndCwgWGVuIHVzZXMgdGhlIFNNTVUgYW5kIGl0 IGlzIHVuYXZhaWxhYmxlIHRvIGd1ZXN0cy4gV2UKZG9uJ3QgY3VycmVudGx5IHN1cHBvcnQgYW55 IG9mIHRoZSBzdGFnZSAxKzIgdmFyaWFudHMgb2YgdGhlIFNNTVUgQUZBSUsuCgo+IEkgY2hlY2tl ZCB4ZW4vZHJpdmVyL3Bhc3N0aHJvdWdoL2FybS9zbW11LmMgYW5kIGZpbmQgYXJtX3NtbXVfbWFw X3BhZ2UgaGFzCj4gc3VjaCBhIGNoZWNraW5nIGNvZGUgIkJVR19PTighaXNfZG9tYWluX2RpcmVj dF9tYXBwZWQoZCkpOyIsIHNvIHRvIG15IGNhc2UsCj4gb25seSBkb20wIGNhbiB1c2Ugc21tdSwg YW5kIERvbVUgaXMgbm90IDE6MSBtYXBwaW5nLgoKSGF2ZSB5b3UgYWN0dWFsbHkgaGl0IHRoaXMg QlVHX09OPwoKQWNjb3JkaW5nIHRvIHRoZSBjb21tZW50IHRoaXMgZnVuY3Rpb24gaXMgb25seSBj YWxsZWQgZm9yIGRpcmVjdCBtYXBwZWQKZG9tYWlucywgYW5kIG15IHJlYWRpbmcgb2YgYWxsIHRo cmVlIG9mIHRoZSBjYWxsZXJzLCB2aWEgaW9tbXVfbWFwX3BhZ2UsIGlzCnRoYXQgdGhleSBhcmUg Z2F0ZWQgb24gZ250dGFiX25lZWRfaW9tbXVfbWFwcGluZyhsZCkgd2hpY2ggb24gQVJNIGlzOgoK I2RlZmluZSBnbnR0YWJfbmVlZF9pb21tdV9tYXBwaW5nKGQpwqDCoMKgwqDCoMKgwqDCoMKgwqDC oMKgwqDCoMKgwqDCoMKgwqDCoFwKwqDCoMKgwqAoaXNfZG9tYWluX2RpcmVjdF9tYXBwZWQoZCkg JiYgbmVlZF9pb21tdShkKSkKCj4gSSBhbSBjb25mdXNlZCBhYm91dCBob3cgRG9tVSBjYW4gRE1B IHRocm91Z2ggU01NVS4KCkhhdmUgeW91IHNlZW4gZG9jcy9taXNjL2FybS9wYXNzdGhyb3VnaC50 eHQgaW4gdGhlIFhlbiB0cmVlPyBUaGUgcHJvY2VzcyBpcwphIGJpdCBtYW51YWwgYnV0IEkgYmVs aWV2ZSB0aGF0IGlmIHlvdSBmb2xsb3cgc29tZXRoaW5nIGFsb25nIHRob3NlIGxpbmVzCnRoZW4g dGhpbmdzIHNob3VsZCB3b3JrLgoKSWFuLgoKCl9fX19fX19fX19fX19fX19fX19fX19fX19fX19f X19fX19fX19fX19fX19fX19fClhlbi11c2VycyBtYWlsaW5nIGxpc3QKWGVuLXVzZXJzQGxpc3Rz Lnhlbi5vcmcKaHR0cDovL2xpc3RzLnhlbi5vcmcveGVuLXVzZXJz From xen-users-bounces@lists.xen.org Thu Jan 07 14:00:26 2016 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 07 Jan 2016 14: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 1aHB6s-0002IS-Fk; Thu, 07 Jan 2016 14:00:14 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1aHB6q-0002IK-OT for Xen-users@lists.xen.org; Thu, 07 Jan 2016 14:00:12 +0000 Received: from [85.158.143.35] by server-2.bemta-4.messagelabs.com id 83/D5-08977-C6F6E865; Thu, 07 Jan 2016 14:00:12 +0000 X-Env-Sender: prvs=807a36095=Ian.Campbell@citrix.com X-Msg-Ref: server-5.tower-21.messagelabs.com!1452175209!8897117!1 X-Originating-IP: [66.165.176.89] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjYuMTY1LjE3Ni44OSA9PiAyMDMwMDc=\n, received_headers: No Received headers X-StarScan-Received: X-StarScan-Version: 7.35.1; banners=-,-,- X-VirusChecked: Checked Received: (qmail 13221 invoked from network); 7 Jan 2016 14:00:11 -0000 Received: from smtp.citrix.com (HELO SMTP.CITRIX.COM) (66.165.176.89) by server-5.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 7 Jan 2016 14:00:11 -0000 X-IronPort-AV: E=Sophos;i="5.20,533,1444694400"; d="scan'208";a="323428627" Message-ID: <1452175207.21055.219.camel@citrix.com> From: Ian Campbell To: Peng Fan , Date: Thu, 7 Jan 2016 14:00:07 +0000 In-Reply-To: <20160107065013.GA29626@linux-7smt.suse> References: <20160107065013.GA29626@linux-7smt.suse> X-Mailer: Evolution 3.18.2-1 MIME-Version: 1.0 X-DLP: MIA1 Subject: Re: [Xen-users] SMMU Question for passthrough device X-BeenThere: xen-users@lists.xen.org X-Mailman-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 T24gVGh1LCAyMDE2LTAxLTA3IGF0IDE0OjUwICswODAwLCBQZW5nIEZhbiB3cm90ZToKPiBIaSBl eHBlcnRzLAo+IAo+IFRoZXJlIGFyZSB0d28gbGludXggb3MgcnVubmluZyBvbiBteSBBUk02NCBw bGF0Zm9ybS4gTm93IEkgd2FudCB0byBwYXNzdGhyb3VnaAo+IGEgcGxhdGZvcm0gZGV2aWNlKHNk IGNvbnRyb2xsZXIpIHRvIERvbVUgdG8gbGV0IERvbVUgY2FuIGRpcmVjdGx5IGFjY2VzcyB0aGUK PiBleHRlcm5hbCBTRCBjYXJkLiBUaGUgc2QgY29udHJvbGxlciBzdXBwb3J0cyBETUEuIFRoZSBz ZCBjb250cm9sbGVyIGRyaXZlcgo+IHdvcmsgd2VsbCBpbiBIb3N0IExpbnV4Lgo+IAo+IFNvIEkg aGF2ZSBhIHF1ZXN0aW9uIGhvdyBEb21VIERNQSBpbnRlcmFjdHMgd2l0aCBTTU1VIGFuZCBmaW5h bGx5IGFjY2Vzcwo+IG1lbW9yeT8KCkknbSBub3QgdGVycmlibHkgZmFtaWxpYXIgd2l0aCB0aGUg U01NVSBzdHVmZiBvbiBYZW4sIGJ1dCBJIHNoYWxsIHRyeS4KCj4gVGhlcmUgYXJlIDMgZG1hX21h cF9vcHMgaW4gbGludXggYXJjaC9hcm02NC9tbS9kbWEtbWFwcGluZy5jCj4gc3RhdGljIHN0cnVj dCBkbWFfbWFwX29wcyBpb21tdV9kbWFfb3BzCj4gc3RhdGljIHN0cnVjdCBkbWFfbWFwX29wcyBz d2lvdGxiX2RtYV9vcHMKPiBzdHJ1Y3QgZG1hX21hcF9vcHMgZHVtbXlfZG1hX29wcwo+IAo+IFNp bmNlIHNtbXUgd2lsbCBiZSBhc3NpZ25lZCB0byBYRU4sIGxpbnV4IGtlcm5lbCB3aWxsIG5vdCB1 c2UKPiBpb21tdV9kbWFfb3BzLiBTbyBzd2lvdGxiX2RtYV9vcHMgd2lsbCBiZSB1c2VkIGZvciBE b21VLiBCdXQgSSBjYW4gbm90IGZpbmQKPiBvdXQgaG93IHN3aW90bGJfZG1hX29wcyBpbnRlcmFj dHMgd2l0aCBTTU1VLgoKQUZBSUsgaXQgZG9lc24ndCwgWGVuIHVzZXMgdGhlIFNNTVUgYW5kIGl0 IGlzIHVuYXZhaWxhYmxlIHRvIGd1ZXN0cy4gV2UKZG9uJ3QgY3VycmVudGx5IHN1cHBvcnQgYW55 IG9mIHRoZSBzdGFnZSAxKzIgdmFyaWFudHMgb2YgdGhlIFNNTVUgQUZBSUsuCgo+IEkgY2hlY2tl ZCB4ZW4vZHJpdmVyL3Bhc3N0aHJvdWdoL2FybS9zbW11LmMgYW5kIGZpbmQgYXJtX3NtbXVfbWFw X3BhZ2UgaGFzCj4gc3VjaCBhIGNoZWNraW5nIGNvZGUgIkJVR19PTighaXNfZG9tYWluX2RpcmVj dF9tYXBwZWQoZCkpOyIsIHNvIHRvIG15IGNhc2UsCj4gb25seSBkb20wIGNhbiB1c2Ugc21tdSwg YW5kIERvbVUgaXMgbm90IDE6MSBtYXBwaW5nLgoKSGF2ZSB5b3UgYWN0dWFsbHkgaGl0IHRoaXMg QlVHX09OPwoKQWNjb3JkaW5nIHRvIHRoZSBjb21tZW50IHRoaXMgZnVuY3Rpb24gaXMgb25seSBj YWxsZWQgZm9yIGRpcmVjdCBtYXBwZWQKZG9tYWlucywgYW5kIG15IHJlYWRpbmcgb2YgYWxsIHRo cmVlIG9mIHRoZSBjYWxsZXJzLCB2aWEgaW9tbXVfbWFwX3BhZ2UsIGlzCnRoYXQgdGhleSBhcmUg Z2F0ZWQgb24gZ250dGFiX25lZWRfaW9tbXVfbWFwcGluZyhsZCkgd2hpY2ggb24gQVJNIGlzOgoK I2RlZmluZSBnbnR0YWJfbmVlZF9pb21tdV9tYXBwaW5nKGQpwqDCoMKgwqDCoMKgwqDCoMKgwqDC oMKgwqDCoMKgwqDCoMKgwqDCoFwKwqDCoMKgwqAoaXNfZG9tYWluX2RpcmVjdF9tYXBwZWQoZCkg JiYgbmVlZF9pb21tdShkKSkKCj4gSSBhbSBjb25mdXNlZCBhYm91dCBob3cgRG9tVSBjYW4gRE1B IHRocm91Z2ggU01NVS4KCkhhdmUgeW91IHNlZW4gZG9jcy9taXNjL2FybS9wYXNzdGhyb3VnaC50 eHQgaW4gdGhlIFhlbiB0cmVlPyBUaGUgcHJvY2VzcyBpcwphIGJpdCBtYW51YWwgYnV0IEkgYmVs aWV2ZSB0aGF0IGlmIHlvdSBmb2xsb3cgc29tZXRoaW5nIGFsb25nIHRob3NlIGxpbmVzCnRoZW4g dGhpbmdzIHNob3VsZCB3b3JrLgoKSWFuLgoKCl9fX19fX19fX19fX19fX19fX19fX19fX19fX19f X19fX19fX19fX19fX19fX19fClhlbi11c2VycyBtYWlsaW5nIGxpc3QKWGVuLXVzZXJzQGxpc3Rz Lnhlbi5vcmcKaHR0cDovL2xpc3RzLnhlbi5vcmcveGVuLXVzZXJz From xen-users-bounces@lists.xen.org Fri Jan 08 02:00:58 2016 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 08 Jan 2016 02:00: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 1aHMKm-0003WP-PA; Fri, 08 Jan 2016 01:59:20 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1aHMKk-0003WK-Sr for Xen-users@lists.xen.org; Fri, 08 Jan 2016 01:59:18 +0000 Received: from [85.158.143.35] by server-2.bemta-4.messagelabs.com id D8/12-08977-6F71F865; Fri, 08 Jan 2016 01:59:18 +0000 X-Env-Sender: van.freenix@gmail.com X-Msg-Ref: server-3.tower-21.messagelabs.com!1452218356!8529365!1 X-Originating-IP: [209.85.192.170] X-SpamReason: No, hits=0.5 required=7.0 tests=BODY_RANDOM_LONG X-StarScan-Received: X-StarScan-Version: 7.35.1; banners=-,-,- X-VirusChecked: Checked Received: (qmail 33904 invoked from network); 8 Jan 2016 01:59:17 -0000 Received: from mail-pf0-f170.google.com (HELO mail-pf0-f170.google.com) (209.85.192.170) by server-3.tower-21.messagelabs.com with AES128-GCM-SHA256 encrypted SMTP; 8 Jan 2016 01:59:17 -0000 Received: by mail-pf0-f170.google.com with SMTP id e65so2093035pfe.0 for ; Thu, 07 Jan 2016 17:59:17 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=date:from:to:cc:subject:message-id:references:mime-version :content-type:content-disposition:content-transfer-encoding :in-reply-to:user-agent; bh=56nreofxMW58LkvY2PXw+krK1pMocrJXU9EZB/OqNQE=; b=Qa/mo0iObxk0B5TCbjnZSnJyVK2NcJCmo7Z3I5yATtmx7pwEyH+DoXD6OoRXAX0rjN 7Z+FgsnnSsz0/LCI+brzmrlcVPfZI+vPbqAUypeOZu2s8PNd3pU7ohZdec/lhhyb3SQT Vu505kYYLcyZTVhBGzI4sQ2oSuF6P0ebSXDRjHBcHuJchQ04BMiGFPXFHRBv1RmG2oO+ sY/sX1rEw3wCE9h4MtB2avBBQPsiXcyQ8h0MZOR+5jObAplSbdvY00dFdjhfeqwZV+ME t+4Z4qysh+JSkhD9+7uKN2xElKlgi02UZr9XdnjRgdfHJZnfXUina6bYAwjMIcauQi+x gq4g== X-Received: by 10.98.11.151 with SMTP id 23mr876909pfl.93.1452218356007; Thu, 07 Jan 2016 17:59:16 -0800 (PST) Received: from linux-7smt.suse (gate-zmy3.freescale.com. [192.88.167.1]) by smtp.googlemail.com with ESMTPSA id sm8sm9135001pac.43.2016.01.07.17.59.13 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 07 Jan 2016 17:59:15 -0800 (PST) Date: Fri, 8 Jan 2016 09:57:33 +0800 From: Peng Fan To: Ian Campbell Message-ID: <20160108015728.GA3320@linux-7smt.suse> References: <20160107065013.GA29626@linux-7smt.suse> <1452175207.21055.219.camel@citrix.com> MIME-Version: 1.0 Content-Length: 2857 Content-Disposition: inline In-Reply-To: <1452175207.21055.219.camel@citrix.com> User-Agent: Mutt/1.5.24 (2015-08-30) Cc: Xen-users@lists.xen.org Subject: Re: [Xen-users] SMMU Question for passthrough device X-BeenThere: xen-users@lists.xen.org X-Mailman-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 Ian, Thanks for you reply. On Thu, Jan 07, 2016 at 02:00:07PM +0000, Ian Campbell wrote: >On Thu, 2016-01-07 at 14:50 +0800, Peng Fan wrote: >> Hi experts, >> = >> There are two linux os running on my ARM64 platform. Now I want to passt= hrough >> a platform device(sd controller) to DomU to let DomU can directly access= the >> external SD card. The sd controller supports DMA. The sd controller driv= er >> work well in Host Linux. >> = >> So I have a question how DomU DMA interacts with SMMU and finally access >> memory? > >I'm not terribly familiar with the SMMU stuff on Xen, but I shall try. > >> There are 3 dma_map_ops in linux arch/arm64/mm/dma-mapping.c >> static struct dma_map_ops iommu_dma_ops >> static struct dma_map_ops swiotlb_dma_ops >> struct dma_map_ops dummy_dma_ops >> = >> Since smmu will be assigned to XEN, linux kernel will not use >> iommu_dma_ops. So swiotlb_dma_ops will be used for DomU. But I can not f= ind >> out how swiotlb_dma_ops interacts with SMMU. > >AFAIK it doesn't, Xen uses the SMMU and it is unavailable to guests. We >don't currently support any of the stage 1+2 variants of the SMMU AFAIK. Yeah. I got that XEN uses the SMMU hardware. I just want to know how DomU let XEN build SMMU stage 2 mapping for passthrough dma-enable devi= ce and finally do DMA. I can not find out the code path. > >> I checked xen/driver/passthrough/arm/smmu.c and find arm_smmu_map_page h= as >> such a checking code "BUG_ON(!is_domain_direct_mapped(d));", so to my ca= se, >> only dom0 can use smmu, and DomU is not 1:1 mapping. > >Have you actually hit this BUG_ON? > >According to the comment this function is only called for direct mapped >domains, and my reading of all three of the callers, via iommu_map_page, is >that they are gated on gnttab_need_iommu_mapping(ld) which on ARM is: > >#define gnttab_need_iommu_mapping(d)=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0= =A0=A0=A0=A0=A0=A0=A0=A0\ >=A0=A0=A0=A0(is_domain_direct_mapped(d) && need_iommu(d)) I not hit the BUG_ON. I am reading the code and try to understand the inter= nals. gnttab_map_grant_ref -> __gnttab_map_grant_ref -> iommu_map_page -> smmu ma= p page So If DomU want to do DMA for a passthrough platform device or PCI device, then we should write a new PV driver to let Dom0 do the DMA to/from device? > >> I am confused about how DomU can DMA through SMMU. > >Have you seen docs/misc/arm/passthrough.txt in the Xen tree? The process is >a bit manual but I believe that if you follow something along those lines >then things should work. Yeah. I have read it. And I can passthrough a simple device to DomU without DMA and SMMU. I am just trying to understand the internals of DMA/SMMU for = XEN. Thanks, Peng. > >Ian. > _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Fri Jan 08 02:00:58 2016 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 08 Jan 2016 02:00: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 1aHMKm-0003WP-PA; Fri, 08 Jan 2016 01:59:20 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1aHMKk-0003WK-Sr for Xen-users@lists.xen.org; Fri, 08 Jan 2016 01:59:18 +0000 Received: from [85.158.143.35] by server-2.bemta-4.messagelabs.com id D8/12-08977-6F71F865; Fri, 08 Jan 2016 01:59:18 +0000 X-Env-Sender: van.freenix@gmail.com X-Msg-Ref: server-3.tower-21.messagelabs.com!1452218356!8529365!1 X-Originating-IP: [209.85.192.170] X-SpamReason: No, hits=0.5 required=7.0 tests=BODY_RANDOM_LONG X-StarScan-Received: X-StarScan-Version: 7.35.1; banners=-,-,- X-VirusChecked: Checked Received: (qmail 33904 invoked from network); 8 Jan 2016 01:59:17 -0000 Received: from mail-pf0-f170.google.com (HELO mail-pf0-f170.google.com) (209.85.192.170) by server-3.tower-21.messagelabs.com with AES128-GCM-SHA256 encrypted SMTP; 8 Jan 2016 01:59:17 -0000 Received: by mail-pf0-f170.google.com with SMTP id e65so2093035pfe.0 for ; Thu, 07 Jan 2016 17:59:17 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=date:from:to:cc:subject:message-id:references:mime-version :content-type:content-disposition:content-transfer-encoding :in-reply-to:user-agent; bh=56nreofxMW58LkvY2PXw+krK1pMocrJXU9EZB/OqNQE=; b=Qa/mo0iObxk0B5TCbjnZSnJyVK2NcJCmo7Z3I5yATtmx7pwEyH+DoXD6OoRXAX0rjN 7Z+FgsnnSsz0/LCI+brzmrlcVPfZI+vPbqAUypeOZu2s8PNd3pU7ohZdec/lhhyb3SQT Vu505kYYLcyZTVhBGzI4sQ2oSuF6P0ebSXDRjHBcHuJchQ04BMiGFPXFHRBv1RmG2oO+ sY/sX1rEw3wCE9h4MtB2avBBQPsiXcyQ8h0MZOR+5jObAplSbdvY00dFdjhfeqwZV+ME t+4Z4qysh+JSkhD9+7uKN2xElKlgi02UZr9XdnjRgdfHJZnfXUina6bYAwjMIcauQi+x gq4g== X-Received: by 10.98.11.151 with SMTP id 23mr876909pfl.93.1452218356007; Thu, 07 Jan 2016 17:59:16 -0800 (PST) Received: from linux-7smt.suse (gate-zmy3.freescale.com. [192.88.167.1]) by smtp.googlemail.com with ESMTPSA id sm8sm9135001pac.43.2016.01.07.17.59.13 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 07 Jan 2016 17:59:15 -0800 (PST) Date: Fri, 8 Jan 2016 09:57:33 +0800 From: Peng Fan To: Ian Campbell Message-ID: <20160108015728.GA3320@linux-7smt.suse> References: <20160107065013.GA29626@linux-7smt.suse> <1452175207.21055.219.camel@citrix.com> MIME-Version: 1.0 Content-Length: 2857 Content-Disposition: inline In-Reply-To: <1452175207.21055.219.camel@citrix.com> User-Agent: Mutt/1.5.24 (2015-08-30) Cc: Xen-users@lists.xen.org Subject: Re: [Xen-users] SMMU Question for passthrough device X-BeenThere: xen-users@lists.xen.org X-Mailman-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 Ian, Thanks for you reply. On Thu, Jan 07, 2016 at 02:00:07PM +0000, Ian Campbell wrote: >On Thu, 2016-01-07 at 14:50 +0800, Peng Fan wrote: >> Hi experts, >> = >> There are two linux os running on my ARM64 platform. Now I want to passt= hrough >> a platform device(sd controller) to DomU to let DomU can directly access= the >> external SD card. The sd controller supports DMA. The sd controller driv= er >> work well in Host Linux. >> = >> So I have a question how DomU DMA interacts with SMMU and finally access >> memory? > >I'm not terribly familiar with the SMMU stuff on Xen, but I shall try. > >> There are 3 dma_map_ops in linux arch/arm64/mm/dma-mapping.c >> static struct dma_map_ops iommu_dma_ops >> static struct dma_map_ops swiotlb_dma_ops >> struct dma_map_ops dummy_dma_ops >> = >> Since smmu will be assigned to XEN, linux kernel will not use >> iommu_dma_ops. So swiotlb_dma_ops will be used for DomU. But I can not f= ind >> out how swiotlb_dma_ops interacts with SMMU. > >AFAIK it doesn't, Xen uses the SMMU and it is unavailable to guests. We >don't currently support any of the stage 1+2 variants of the SMMU AFAIK. Yeah. I got that XEN uses the SMMU hardware. I just want to know how DomU let XEN build SMMU stage 2 mapping for passthrough dma-enable devi= ce and finally do DMA. I can not find out the code path. > >> I checked xen/driver/passthrough/arm/smmu.c and find arm_smmu_map_page h= as >> such a checking code "BUG_ON(!is_domain_direct_mapped(d));", so to my ca= se, >> only dom0 can use smmu, and DomU is not 1:1 mapping. > >Have you actually hit this BUG_ON? > >According to the comment this function is only called for direct mapped >domains, and my reading of all three of the callers, via iommu_map_page, is >that they are gated on gnttab_need_iommu_mapping(ld) which on ARM is: > >#define gnttab_need_iommu_mapping(d)=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0= =A0=A0=A0=A0=A0=A0=A0=A0\ >=A0=A0=A0=A0(is_domain_direct_mapped(d) && need_iommu(d)) I not hit the BUG_ON. I am reading the code and try to understand the inter= nals. gnttab_map_grant_ref -> __gnttab_map_grant_ref -> iommu_map_page -> smmu ma= p page So If DomU want to do DMA for a passthrough platform device or PCI device, then we should write a new PV driver to let Dom0 do the DMA to/from device? > >> I am confused about how DomU can DMA through SMMU. > >Have you seen docs/misc/arm/passthrough.txt in the Xen tree? The process is >a bit manual but I believe that if you follow something along those lines >then things should work. Yeah. I have read it. And I can passthrough a simple device to DomU without DMA and SMMU. I am just trying to understand the internals of DMA/SMMU for = XEN. Thanks, Peng. > >Ian. > _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Fri Jan 08 04:47:35 2016 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 08 Jan 2016 04:47: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 1aHOwZ-0000p1-Ok; Fri, 08 Jan 2016 04:46:31 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1aHOwZ-0000ow-2H for xen-users@lists.xen.org; Fri, 08 Jan 2016 04:46:31 +0000 Received: from [193.109.254.147] by server-8.bemta-14.messagelabs.com id B2/F3-24450-62F3F865; Fri, 08 Jan 2016 04:46:30 +0000 X-Env-Sender: pavan.maddamsetti@gmail.com X-Msg-Ref: server-10.tower-27.messagelabs.com!1452228388!15453078!1 X-Originating-IP: [209.85.160.182] X-SpamReason: No, hits=0.8 required=7.0 tests=BODY_RANDOM_LONG, RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 7.35.1; banners=-,-,- X-VirusChecked: Checked Received: (qmail 35520 invoked from network); 8 Jan 2016 04:46:29 -0000 Received: from mail-yk0-f182.google.com (HELO mail-yk0-f182.google.com) (209.85.160.182) by server-10.tower-27.messagelabs.com with AES128-GCM-SHA256 encrypted SMTP; 8 Jan 2016 04:46:29 -0000 Received: by mail-yk0-f182.google.com with SMTP id a85so273446974ykb.1 for ; Thu, 07 Jan 2016 20:46:29 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=+OOCdZ4EHG9ED0nIpnVcNGwnAwNKXYCiYtAfR2u4VIc=; b=LXGbOWuEJjH/sx+QyW3JPvzyKOKuQCL5RKLSoLH/Yc+RuA2VKPISAiY/ewpCvzYict 1MQDW8wGf6hGQe5vNAp0buvhCL1xIjP/X2cI544fekKlva35gacA9RdBj0RCviYMoJd+ kfg4xfzOsMC8de6+g5k9IZSFFC8laHHA49l55+YzaZApfe+IEBqgD89tp4RdtxeRBJWQ xu6OeL5J26JizsyrVk9GkK00m2LEXiG+P1sjtXQWl5GdIF6gQiv5CD/hGAubGSl8imYp YJQVs8Qj+718P/g3k5DkzE+26jUF8S+B74QetJqFRQv3pw6PvtrGlq8sWlVPXtwxtHTg AfKQ== MIME-Version: 1.0 X-Received: by 10.13.217.214 with SMTP id b205mr89150059ywe.48.1452228388240; Thu, 07 Jan 2016 20:46:28 -0800 (PST) Received: by 10.13.234.12 with HTTP; Thu, 7 Jan 2016 20:46:28 -0800 (PST) Date: Fri, 8 Jan 2016 10:16:28 +0530 Message-ID: From: Pavan Maddamsetti To: xen-users@lists.xen.org Subject: [Xen-users] VLAN guest networking: near 100% packet loss X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: 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 all, I am new to the mailing list and have come here to request assistance with a networking issue. My setup consists of Debian 8 on both dom0 and domU, and the machine is connected to a VLAN tagged port on the switch meaning that the host must be VLAN-aware. Dom0 has internet reachability but domU is only able to establish connections to hosts on the LAN; pings sent to external machines come back with virtually 100% packet loss but it is unlikely a routing issue because sometimes one or two packets get through. Dom0 network configuration is: auto xenbr0 iface xenbr0 inet manual bridge_ports eth1 bridge_stp off bridge_waitport 0 bridge_fd 0 auto xenbr0.4 iface xenbr0.4 inet static address 192.168.4.13 broadcast 192.168.4.255 netmask 255.255.255.0 gateway 192.168.4.1 vlan-raw-device xenbr0 The configuration file in /etc/xen/ contains the line: vif = ['bridge=xenbr0,mac=00:16:3e:40:27:fa,ip=192.168.4.21'] Now here is the domU network configuration. auto eth0 iface eth0 inet static address 192.168.4.21 broadcast 192.168.4.255 netmask 255.255.255.0 gateway 192.168.4.1 After restarting networking we can see the default routes and ARP tables. On dom0: # route -n Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 0.0.0.0 192.168.4.1 0.0.0.0 UG 0 0 0 xenbr0.4 192.168.4.0 0.0.0.0 255.255.255.0 U 0 0 0 xenbr0.4 # arp -n Address HWtype HWaddress Flags Mask Iface 192.168.4.21 (incomplete) xenbr0.4 192.168.4.21 ether 00:16:3e:40:27:fa C xenbr0 192.168.4.1 ether 00:00:5e:00:01:05 C xenbr0.4 192.168.4.2 ether 00:17:7c:41:7c:ce C xenbr0.4 DomU: # route -n Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 0.0.0.0 192.168.4.1 0.0.0.0 UG 0 0 0 eth0 192.168.4.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0 # arp -n Address HWtype HWaddress Flags Mask Iface 192.168.4.1 ether 20:47:47:8c:d0:4c C eth0 So what happens if I ping 192.168.4.1 from domU and run tcpdump on dom0? On dom0: # tcpdump -vv host 192.168.4.21 tcpdump: listening on xenbr0, link-type EN10MB (Ethernet), capture size 262144 bytes 11:14:57.603076 IP (tos 0x0, ttl 64, id 55216, offset 0, flags [DF], proto ICMP (1), length 84) domU > 192.168.4.1: ICMP echo request, id 725, seq 1, length 64 11:14:57.603086 IP (tos 0x0, ttl 63, id 55216, offset 0, flags [DF], proto ICMP (1), length 84) domU > 192.168.4.1: ICMP echo request, id 725, seq 1, length 64 11:14:57.621871 ARP, Ethernet (len 6), IPv4 (len 4), Request who-has domU tell 192.168.4.1, length 46 ... 8 packets captured 11 packets received by filter 0 packets dropped by kernel DomU: # ping 192.168.4.1 PING 192.168.4.1 (192.168.4.1) 56(84) bytes of data. ^C --- 192.168.4.1 ping statistics --- 148 packets transmitted, 0 received, 100% packet loss, time 147000ms Does anyone have experience configuring VLANs with the bridge interface? -- cant [kant]: hypocritical and sanctimonious talk, typically of a moral, religious, or political nature _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Fri Jan 08 04:47:35 2016 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 08 Jan 2016 04:47: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 1aHOwZ-0000p1-Ok; Fri, 08 Jan 2016 04:46:31 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1aHOwZ-0000ow-2H for xen-users@lists.xen.org; Fri, 08 Jan 2016 04:46:31 +0000 Received: from [193.109.254.147] by server-8.bemta-14.messagelabs.com id B2/F3-24450-62F3F865; Fri, 08 Jan 2016 04:46:30 +0000 X-Env-Sender: pavan.maddamsetti@gmail.com X-Msg-Ref: server-10.tower-27.messagelabs.com!1452228388!15453078!1 X-Originating-IP: [209.85.160.182] X-SpamReason: No, hits=0.8 required=7.0 tests=BODY_RANDOM_LONG, RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 7.35.1; banners=-,-,- X-VirusChecked: Checked Received: (qmail 35520 invoked from network); 8 Jan 2016 04:46:29 -0000 Received: from mail-yk0-f182.google.com (HELO mail-yk0-f182.google.com) (209.85.160.182) by server-10.tower-27.messagelabs.com with AES128-GCM-SHA256 encrypted SMTP; 8 Jan 2016 04:46:29 -0000 Received: by mail-yk0-f182.google.com with SMTP id a85so273446974ykb.1 for ; Thu, 07 Jan 2016 20:46:29 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=+OOCdZ4EHG9ED0nIpnVcNGwnAwNKXYCiYtAfR2u4VIc=; b=LXGbOWuEJjH/sx+QyW3JPvzyKOKuQCL5RKLSoLH/Yc+RuA2VKPISAiY/ewpCvzYict 1MQDW8wGf6hGQe5vNAp0buvhCL1xIjP/X2cI544fekKlva35gacA9RdBj0RCviYMoJd+ kfg4xfzOsMC8de6+g5k9IZSFFC8laHHA49l55+YzaZApfe+IEBqgD89tp4RdtxeRBJWQ xu6OeL5J26JizsyrVk9GkK00m2LEXiG+P1sjtXQWl5GdIF6gQiv5CD/hGAubGSl8imYp YJQVs8Qj+718P/g3k5DkzE+26jUF8S+B74QetJqFRQv3pw6PvtrGlq8sWlVPXtwxtHTg AfKQ== MIME-Version: 1.0 X-Received: by 10.13.217.214 with SMTP id b205mr89150059ywe.48.1452228388240; Thu, 07 Jan 2016 20:46:28 -0800 (PST) Received: by 10.13.234.12 with HTTP; Thu, 7 Jan 2016 20:46:28 -0800 (PST) Date: Fri, 8 Jan 2016 10:16:28 +0530 Message-ID: From: Pavan Maddamsetti To: xen-users@lists.xen.org Subject: [Xen-users] VLAN guest networking: near 100% packet loss X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: 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 all, I am new to the mailing list and have come here to request assistance with a networking issue. My setup consists of Debian 8 on both dom0 and domU, and the machine is connected to a VLAN tagged port on the switch meaning that the host must be VLAN-aware. Dom0 has internet reachability but domU is only able to establish connections to hosts on the LAN; pings sent to external machines come back with virtually 100% packet loss but it is unlikely a routing issue because sometimes one or two packets get through. Dom0 network configuration is: auto xenbr0 iface xenbr0 inet manual bridge_ports eth1 bridge_stp off bridge_waitport 0 bridge_fd 0 auto xenbr0.4 iface xenbr0.4 inet static address 192.168.4.13 broadcast 192.168.4.255 netmask 255.255.255.0 gateway 192.168.4.1 vlan-raw-device xenbr0 The configuration file in /etc/xen/ contains the line: vif = ['bridge=xenbr0,mac=00:16:3e:40:27:fa,ip=192.168.4.21'] Now here is the domU network configuration. auto eth0 iface eth0 inet static address 192.168.4.21 broadcast 192.168.4.255 netmask 255.255.255.0 gateway 192.168.4.1 After restarting networking we can see the default routes and ARP tables. On dom0: # route -n Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 0.0.0.0 192.168.4.1 0.0.0.0 UG 0 0 0 xenbr0.4 192.168.4.0 0.0.0.0 255.255.255.0 U 0 0 0 xenbr0.4 # arp -n Address HWtype HWaddress Flags Mask Iface 192.168.4.21 (incomplete) xenbr0.4 192.168.4.21 ether 00:16:3e:40:27:fa C xenbr0 192.168.4.1 ether 00:00:5e:00:01:05 C xenbr0.4 192.168.4.2 ether 00:17:7c:41:7c:ce C xenbr0.4 DomU: # route -n Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 0.0.0.0 192.168.4.1 0.0.0.0 UG 0 0 0 eth0 192.168.4.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0 # arp -n Address HWtype HWaddress Flags Mask Iface 192.168.4.1 ether 20:47:47:8c:d0:4c C eth0 So what happens if I ping 192.168.4.1 from domU and run tcpdump on dom0? On dom0: # tcpdump -vv host 192.168.4.21 tcpdump: listening on xenbr0, link-type EN10MB (Ethernet), capture size 262144 bytes 11:14:57.603076 IP (tos 0x0, ttl 64, id 55216, offset 0, flags [DF], proto ICMP (1), length 84) domU > 192.168.4.1: ICMP echo request, id 725, seq 1, length 64 11:14:57.603086 IP (tos 0x0, ttl 63, id 55216, offset 0, flags [DF], proto ICMP (1), length 84) domU > 192.168.4.1: ICMP echo request, id 725, seq 1, length 64 11:14:57.621871 ARP, Ethernet (len 6), IPv4 (len 4), Request who-has domU tell 192.168.4.1, length 46 ... 8 packets captured 11 packets received by filter 0 packets dropped by kernel DomU: # ping 192.168.4.1 PING 192.168.4.1 (192.168.4.1) 56(84) bytes of data. ^C --- 192.168.4.1 ping statistics --- 148 packets transmitted, 0 received, 100% packet loss, time 147000ms Does anyone have experience configuring VLANs with the bridge interface? -- cant [kant]: hypocritical and sanctimonious talk, typically of a moral, religious, or political nature _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Fri Jan 08 06:52:37 2016 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 08 Jan 2016 06:52: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 1aHQtT-0005pm-P2; Fri, 08 Jan 2016 06:51:27 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1aHQtR-0005pX-Ua; Fri, 08 Jan 2016 06:51:26 +0000 Received: from [193.109.254.147] by server-7.bemta-14.messagelabs.com id 1C/1B-28221-D6C5F865; Fri, 08 Jan 2016 06:51:25 +0000 X-Env-Sender: olaf@aepfle.de X-Msg-Ref: server-16.tower-27.messagelabs.com!1452235884!15389910!1 X-Originating-IP: [195.135.220.15] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 7.35.1; banners=-,-,- X-VirusChecked: Checked Received: (qmail 55975 invoked from network); 8 Jan 2016 06:51:24 -0000 Received: from mx2.suse.de (HELO mx2.suse.de) (195.135.220.15) by server-16.tower-27.messagelabs.com with DHE-RSA-CAMELLIA256-SHA encrypted SMTP; 8 Jan 2016 06:51:24 -0000 X-Virus-Scanned: by amavisd-new at test-mx.suse.de Received: from relay1.suse.de (charybdis-ext.suse.de [195.135.220.254]) by mx2.suse.de (Postfix) with ESMTP id B8A73AAB4; Fri, 8 Jan 2016 06:51:22 +0000 (UTC) Date: Fri, 8 Jan 2016 07:51:22 +0100 From: Olaf Hering To: Jim Fehlig Message-ID: <20160108065122.GA22648@gmail.com> References: <56812352.8060500@pse-consulting.de> <1451907382.13361.37.camel@citrix.com> <568A5BEE.9090808@pse-consulting.de> <1451909615.13361.46.camel@citrix.com> <568A6618.5@pse-consulting.de> <1451911062.13361.60.camel@citrix.com> <568F4EF9.2090609@suse.com> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <568F4EF9.2090609@suse.com> User-Agent: Mutt/1.5.24 (6550) Cc: xen-users@lists.xen.org, xen-devel , Olaf Hering , Ian Campbell , Andreas Pflug Subject: Re: [Xen-users] [Xen-devel] Missing libvirt+libxl functionality (Was: Re: Programmatic administration of Xen machines) X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/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, Jan 07, Jim Fehlig wrote: > The 'iscsi:iqn.2006-09.de.suse@0ac47ee2-216e-452a-a341-a12624cd0225' blob was > passed wholesale to xend, which would eat it and "do the right thing". AFAIK, > libxl is not that forgiving. I've cc'd Olaf on this thread since we recently > discussed how libvirt+libxl might support external block scripts. As I recall, > we didn't have an novel ideas. I think the "raw" string is known to libvirts libxl driver. It could do a strncmp() and fill also ->script. Then libxl would call that thing by itself, libvirt does not need to know about such internals. Of course that would mean an additional "script=$path" is still not supported by libvirt. But thats not a loss because whoever is relying on can just copy its own file into XEN_SCRIPT_DIR. After all only our own dmmd thing requires a script because that is its whole purpose (carry the block configuration along with the vm configuration). Olaf _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Fri Jan 08 06:52:37 2016 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 08 Jan 2016 06:52: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 1aHQtT-0005pm-P2; Fri, 08 Jan 2016 06:51:27 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1aHQtR-0005pX-Ua; Fri, 08 Jan 2016 06:51:26 +0000 Received: from [193.109.254.147] by server-7.bemta-14.messagelabs.com id 1C/1B-28221-D6C5F865; Fri, 08 Jan 2016 06:51:25 +0000 X-Env-Sender: olaf@aepfle.de X-Msg-Ref: server-16.tower-27.messagelabs.com!1452235884!15389910!1 X-Originating-IP: [195.135.220.15] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 7.35.1; banners=-,-,- X-VirusChecked: Checked Received: (qmail 55975 invoked from network); 8 Jan 2016 06:51:24 -0000 Received: from mx2.suse.de (HELO mx2.suse.de) (195.135.220.15) by server-16.tower-27.messagelabs.com with DHE-RSA-CAMELLIA256-SHA encrypted SMTP; 8 Jan 2016 06:51:24 -0000 X-Virus-Scanned: by amavisd-new at test-mx.suse.de Received: from relay1.suse.de (charybdis-ext.suse.de [195.135.220.254]) by mx2.suse.de (Postfix) with ESMTP id B8A73AAB4; Fri, 8 Jan 2016 06:51:22 +0000 (UTC) Date: Fri, 8 Jan 2016 07:51:22 +0100 From: Olaf Hering To: Jim Fehlig Message-ID: <20160108065122.GA22648@gmail.com> References: <56812352.8060500@pse-consulting.de> <1451907382.13361.37.camel@citrix.com> <568A5BEE.9090808@pse-consulting.de> <1451909615.13361.46.camel@citrix.com> <568A6618.5@pse-consulting.de> <1451911062.13361.60.camel@citrix.com> <568F4EF9.2090609@suse.com> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <568F4EF9.2090609@suse.com> User-Agent: Mutt/1.5.24 (6550) Cc: xen-users@lists.xen.org, xen-devel , Olaf Hering , Ian Campbell , Andreas Pflug Subject: Re: [Xen-users] [Xen-devel] Missing libvirt+libxl functionality (Was: Re: Programmatic administration of Xen machines) X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/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, Jan 07, Jim Fehlig wrote: > The 'iscsi:iqn.2006-09.de.suse@0ac47ee2-216e-452a-a341-a12624cd0225' blob was > passed wholesale to xend, which would eat it and "do the right thing". AFAIK, > libxl is not that forgiving. I've cc'd Olaf on this thread since we recently > discussed how libvirt+libxl might support external block scripts. As I recall, > we didn't have an novel ideas. I think the "raw" string is known to libvirts libxl driver. It could do a strncmp() and fill also ->script. Then libxl would call that thing by itself, libvirt does not need to know about such internals. Of course that would mean an additional "script=$path" is still not supported by libvirt. But thats not a loss because whoever is relying on can just copy its own file into XEN_SCRIPT_DIR. After all only our own dmmd thing requires a script because that is its whole purpose (carry the block configuration along with the vm configuration). Olaf _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Fri Jan 08 07:58:30 2016 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 08 Jan 2016 07:58: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 1aHRvO-0008C8-SQ; Fri, 08 Jan 2016 07:57:30 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1aHRvN-0008C2-Eo for xen-users@lists.xen.org; Fri, 08 Jan 2016 07:57:29 +0000 Received: from [85.158.137.68] by server-2.bemta-3.messagelabs.com id 88/EA-21201-8EB6F865; Fri, 08 Jan 2016 07:57:28 +0000 X-Env-Sender: linux@thehobsons.co.uk X-Msg-Ref: server-11.tower-31.messagelabs.com!1452239847!14040803!1 X-Originating-IP: [81.174.135.208] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 7.35.1; banners=-,-,- X-VirusChecked: Checked Received: (qmail 1712 invoked from network); 8 Jan 2016 07:57:27 -0000 Received: from patsy.thehobsons.co.uk (HELO patsy.thehobsons.co.uk) (81.174.135.208) by server-11.tower-31.messagelabs.com with DHE-RSA-AES256-GCM-SHA384 encrypted SMTP; 8 Jan 2016 07:57:27 -0000 X-Virus-Scanned: Debian amavisd-new at patsy.thehobsons.co.uk Received: from simons-macbookpro.lan (magpiehouse.plus.com [80.229.10.150]) by patsy.thehobsons.co.uk (Postfix) with ESMTPSA id E839F1A074 for ; Fri, 8 Jan 2016 07:57:22 +0000 (UTC) Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\)) From: Simon Hobson In-Reply-To: Date: Fri, 8 Jan 2016 07:57:22 +0000 Message-Id: <19C2C25B-B0E5-4F13-998E-BCB0D4A88922@thehobsons.co.uk> References: To: "xen-users@lists.xen.org" X-Mailer: Apple Mail (2.1510) Subject: Re: [Xen-users] VLAN guest networking: near 100% packet loss X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org Pavan Maddamsetti wrote: > I am new to the mailing list Welcome > My setup consists of Debian 8 on both dom0 > and domU, and the machine is connected to a VLAN tagged port on the > switch meaning that the host must be VLAN-aware. > > Dom0 has internet reachability but domU is only able to establish > connections to hosts on the LAN; pings sent to external machines come > back with virtually 100% packet loss but it is unlikely a routing > issue because sometimes one or two packets get through. > > Dom0 network configuration is: > > auto xenbr0 > iface xenbr0 inet manual > bridge_ports eth1 > bridge_stp off > bridge_waitport 0 > bridge_fd 0 > > auto xenbr0.4 > iface xenbr0.4 inet static > address 192.168.4.13 > broadcast 192.168.4.255 > netmask 255.255.255.0 > gateway 192.168.4.1 > vlan-raw-device xenbr0 I'm no expert but I was under the impression that the bridging (not sure whether that's the host side or the Xen us of it) doesn't support VLAN tagging within the virtual switch. I have a host using a VLAN trunk like you describe, but what I've done is build a separate bridge for each VLAN : auto pethint ethmgmt iface pethint inet manual iface ethmgmt inet manual bridge_ports pethint bridge_stp off bridge_waitport 0 bridge_fd 0 auto pethint.36 ethfttc iface pethint.36 inet manual vlan-raw-device pethint iface ethfttc inet manual bridge_ports pethint.36 bridge_stp off bridge_waitport 0 bridge_fd 0 So I end up (with this snippet) with ethmgmt which is connected to the untagged management VLAN, and ethfttc which is connected to VLAN 36 (for my FTTC modem). I then connect guests to whichever networks they need with multiple virtual nics : vif = [ 'bridge=ethext,vifname=intgateext', 'bridge=ethint,vifname=intgateint', 'bridge=ethwifi,vifname=intgatewifi', 'bridge=ethmgmt,vifname=intgatemgmt', 'bridge=ethfttc,vifname=intgatefttc' ] So this links my router to the outside, lan, management VLAN, and guest WiFi networks. If you search the archives, there's been some discussion regarding the use of virtualswitch to provide tagged networking within Dom0 so you can trunk the VLANs to DomUs over one port. I've not played with that. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Fri Jan 08 07:58:30 2016 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 08 Jan 2016 07:58: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 1aHRvO-0008C8-SQ; Fri, 08 Jan 2016 07:57:30 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1aHRvN-0008C2-Eo for xen-users@lists.xen.org; Fri, 08 Jan 2016 07:57:29 +0000 Received: from [85.158.137.68] by server-2.bemta-3.messagelabs.com id 88/EA-21201-8EB6F865; Fri, 08 Jan 2016 07:57:28 +0000 X-Env-Sender: linux@thehobsons.co.uk X-Msg-Ref: server-11.tower-31.messagelabs.com!1452239847!14040803!1 X-Originating-IP: [81.174.135.208] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 7.35.1; banners=-,-,- X-VirusChecked: Checked Received: (qmail 1712 invoked from network); 8 Jan 2016 07:57:27 -0000 Received: from patsy.thehobsons.co.uk (HELO patsy.thehobsons.co.uk) (81.174.135.208) by server-11.tower-31.messagelabs.com with DHE-RSA-AES256-GCM-SHA384 encrypted SMTP; 8 Jan 2016 07:57:27 -0000 X-Virus-Scanned: Debian amavisd-new at patsy.thehobsons.co.uk Received: from simons-macbookpro.lan (magpiehouse.plus.com [80.229.10.150]) by patsy.thehobsons.co.uk (Postfix) with ESMTPSA id E839F1A074 for ; Fri, 8 Jan 2016 07:57:22 +0000 (UTC) Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\)) From: Simon Hobson In-Reply-To: Date: Fri, 8 Jan 2016 07:57:22 +0000 Message-Id: <19C2C25B-B0E5-4F13-998E-BCB0D4A88922@thehobsons.co.uk> References: To: "xen-users@lists.xen.org" X-Mailer: Apple Mail (2.1510) Subject: Re: [Xen-users] VLAN guest networking: near 100% packet loss X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org Pavan Maddamsetti wrote: > I am new to the mailing list Welcome > My setup consists of Debian 8 on both dom0 > and domU, and the machine is connected to a VLAN tagged port on the > switch meaning that the host must be VLAN-aware. > > Dom0 has internet reachability but domU is only able to establish > connections to hosts on the LAN; pings sent to external machines come > back with virtually 100% packet loss but it is unlikely a routing > issue because sometimes one or two packets get through. > > Dom0 network configuration is: > > auto xenbr0 > iface xenbr0 inet manual > bridge_ports eth1 > bridge_stp off > bridge_waitport 0 > bridge_fd 0 > > auto xenbr0.4 > iface xenbr0.4 inet static > address 192.168.4.13 > broadcast 192.168.4.255 > netmask 255.255.255.0 > gateway 192.168.4.1 > vlan-raw-device xenbr0 I'm no expert but I was under the impression that the bridging (not sure whether that's the host side or the Xen us of it) doesn't support VLAN tagging within the virtual switch. I have a host using a VLAN trunk like you describe, but what I've done is build a separate bridge for each VLAN : auto pethint ethmgmt iface pethint inet manual iface ethmgmt inet manual bridge_ports pethint bridge_stp off bridge_waitport 0 bridge_fd 0 auto pethint.36 ethfttc iface pethint.36 inet manual vlan-raw-device pethint iface ethfttc inet manual bridge_ports pethint.36 bridge_stp off bridge_waitport 0 bridge_fd 0 So I end up (with this snippet) with ethmgmt which is connected to the untagged management VLAN, and ethfttc which is connected to VLAN 36 (for my FTTC modem). I then connect guests to whichever networks they need with multiple virtual nics : vif = [ 'bridge=ethext,vifname=intgateext', 'bridge=ethint,vifname=intgateint', 'bridge=ethwifi,vifname=intgatewifi', 'bridge=ethmgmt,vifname=intgatemgmt', 'bridge=ethfttc,vifname=intgatefttc' ] So this links my router to the outside, lan, management VLAN, and guest WiFi networks. If you search the archives, there's been some discussion regarding the use of virtualswitch to provide tagged networking within Dom0 so you can trunk the VLANs to DomUs over one port. I've not played with that. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Fri Jan 08 08:02:07 2016 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 08 Jan 2016 08:02: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 1aHRzl-0000fw-2E; Fri, 08 Jan 2016 08:02:01 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1aHRzj-0000fm-Fd for xen-users@lists.xen.org; Fri, 08 Jan 2016 08:01:59 +0000 Received: from [193.109.254.147] by server-8.bemta-14.messagelabs.com id 87/FE-24450-6FC6F865; Fri, 08 Jan 2016 08:01:58 +0000 X-Env-Sender: fajar@fajar.net X-Msg-Ref: server-16.tower-27.messagelabs.com!1452240114!15402033!1 X-Originating-IP: [209.85.213.171] X-SpamReason: No, hits=0.3 required=7.0 tests=RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 7.35.1; banners=-,-,- X-VirusChecked: Checked Received: (qmail 13493 invoked from network); 8 Jan 2016 08:01:55 -0000 Received: from mail-ig0-f171.google.com (HELO mail-ig0-f171.google.com) (209.85.213.171) by server-16.tower-27.messagelabs.com with AES128-GCM-SHA256 encrypted SMTP; 8 Jan 2016 08:01:55 -0000 Received: by mail-ig0-f171.google.com with SMTP id z14so70247506igp.0 for ; Fri, 08 Jan 2016 00:01:55 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=7efYJZgIZn+Ns0WWhiTZFV+WstgCTEGqQcuumzMyaUE=; b=Hx7aoTgnXvZyKxj+anOXXrKI0Qr2EQejDviKCCxysP2SaVugnaDk2FUWZXcmTteTOP MJO+Z36Xu2EE8PQ6hphAsnSV95+Rf4gopF3AMUJU8XRrftWvsFrc07YxcpRuDrHG5iPm 64dNSWx0h2SNVwr8Lk3MkgzSKyzw+VMbxD0idsM0UGc+olJ+/tIiD7DHqI7wp9JHDlw8 Ljs9eO9ARO0N/SXD9Pw61QI0MpVnDNiERHRxf9KfYFS3GIq7lLuaduAJ9t9Hk58VcipS T+qN2QfYUgVoCclHrcF2fFRkyIwDPAkxp4GXhi1/KjV3JFdgyl/93HtSz2wzbU1VrIbX dtug== X-Gm-Message-State: ALoCoQnpK9trPO98eE+0qxoVSq/kpJlIPCKGvzN+pjW9s3nTUlT/T8XK5ikrz+9D6x4zs0sFtePJegpCS5az2tjGZfzY54QkVA== MIME-Version: 1.0 X-Received: by 10.50.18.114 with SMTP id v18mr20874974igd.34.1452240114065; Fri, 08 Jan 2016 00:01:54 -0800 (PST) Received: by 10.36.203.69 with HTTP; Fri, 8 Jan 2016 00:01:54 -0800 (PST) In-Reply-To: References: Date: Fri, 8 Jan 2016 15:01:54 +0700 Message-ID: From: "Fajar A. Nugraha" To: Pavan Maddamsetti Cc: "xen-users@lists.xen.org" Subject: Re: [Xen-users] VLAN guest networking: near 100% packet loss X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/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, Jan 8, 2016 at 11:46 AM, Pavan Maddamsetti wrote: > Dom0 network configuration is: > > auto xenbr0 > iface xenbr0 inet manual > bridge_ports eth1 > bridge_stp off > bridge_waitport 0 > bridge_fd 0 > > auto xenbr0.4 > iface xenbr0.4 inet static > address 192.168.4.13 > broadcast 192.168.4.255 > netmask 255.255.255.0 > gateway 192.168.4.1 > vlan-raw-device xenbr0 so xenbr0 -> the bridge, trunk xenbr0.4 -> a vlan created on top of the bridge? > The configuration file in /etc/xen/ contains the line: > > vif = ['bridge=xenbr0,mac=00:16:3e:40:27:fa,ip=192.168.4.21'] you bridge the guest to xenbr0 > auto eth0 > iface eth0 inet static > address 192.168.4.21 > broadcast 192.168.4.255 > netmask 255.255.255.0 > gateway 192.168.4.1 ... and yet you tell it to use the same geteway as as xenbr0.4. Obviously that won't work. > Does anyone have experience configuring VLANs with the bridge interface? Either: - bridge the TRUNK, do NOT create the vlan interface (xenbr0.4) in the host, and create the vlan interface in the guest (eth0.4). OR - create a vlan interface on the host (eth0.4), and then create a bridge on TOP of that (e.g. xenbr4), and configure the guest interface (eth0) the way you did -- Fajar _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Fri Jan 08 08:02:07 2016 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 08 Jan 2016 08:02: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 1aHRzl-0000fw-2E; Fri, 08 Jan 2016 08:02:01 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1aHRzj-0000fm-Fd for xen-users@lists.xen.org; Fri, 08 Jan 2016 08:01:59 +0000 Received: from [193.109.254.147] by server-8.bemta-14.messagelabs.com id 87/FE-24450-6FC6F865; Fri, 08 Jan 2016 08:01:58 +0000 X-Env-Sender: fajar@fajar.net X-Msg-Ref: server-16.tower-27.messagelabs.com!1452240114!15402033!1 X-Originating-IP: [209.85.213.171] X-SpamReason: No, hits=0.3 required=7.0 tests=RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 7.35.1; banners=-,-,- X-VirusChecked: Checked Received: (qmail 13493 invoked from network); 8 Jan 2016 08:01:55 -0000 Received: from mail-ig0-f171.google.com (HELO mail-ig0-f171.google.com) (209.85.213.171) by server-16.tower-27.messagelabs.com with AES128-GCM-SHA256 encrypted SMTP; 8 Jan 2016 08:01:55 -0000 Received: by mail-ig0-f171.google.com with SMTP id z14so70247506igp.0 for ; Fri, 08 Jan 2016 00:01:55 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=7efYJZgIZn+Ns0WWhiTZFV+WstgCTEGqQcuumzMyaUE=; b=Hx7aoTgnXvZyKxj+anOXXrKI0Qr2EQejDviKCCxysP2SaVugnaDk2FUWZXcmTteTOP MJO+Z36Xu2EE8PQ6hphAsnSV95+Rf4gopF3AMUJU8XRrftWvsFrc07YxcpRuDrHG5iPm 64dNSWx0h2SNVwr8Lk3MkgzSKyzw+VMbxD0idsM0UGc+olJ+/tIiD7DHqI7wp9JHDlw8 Ljs9eO9ARO0N/SXD9Pw61QI0MpVnDNiERHRxf9KfYFS3GIq7lLuaduAJ9t9Hk58VcipS T+qN2QfYUgVoCclHrcF2fFRkyIwDPAkxp4GXhi1/KjV3JFdgyl/93HtSz2wzbU1VrIbX dtug== X-Gm-Message-State: ALoCoQnpK9trPO98eE+0qxoVSq/kpJlIPCKGvzN+pjW9s3nTUlT/T8XK5ikrz+9D6x4zs0sFtePJegpCS5az2tjGZfzY54QkVA== MIME-Version: 1.0 X-Received: by 10.50.18.114 with SMTP id v18mr20874974igd.34.1452240114065; Fri, 08 Jan 2016 00:01:54 -0800 (PST) Received: by 10.36.203.69 with HTTP; Fri, 8 Jan 2016 00:01:54 -0800 (PST) In-Reply-To: References: Date: Fri, 8 Jan 2016 15:01:54 +0700 Message-ID: From: "Fajar A. Nugraha" To: Pavan Maddamsetti Cc: "xen-users@lists.xen.org" Subject: Re: [Xen-users] VLAN guest networking: near 100% packet loss X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/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, Jan 8, 2016 at 11:46 AM, Pavan Maddamsetti wrote: > Dom0 network configuration is: > > auto xenbr0 > iface xenbr0 inet manual > bridge_ports eth1 > bridge_stp off > bridge_waitport 0 > bridge_fd 0 > > auto xenbr0.4 > iface xenbr0.4 inet static > address 192.168.4.13 > broadcast 192.168.4.255 > netmask 255.255.255.0 > gateway 192.168.4.1 > vlan-raw-device xenbr0 so xenbr0 -> the bridge, trunk xenbr0.4 -> a vlan created on top of the bridge? > The configuration file in /etc/xen/ contains the line: > > vif = ['bridge=xenbr0,mac=00:16:3e:40:27:fa,ip=192.168.4.21'] you bridge the guest to xenbr0 > auto eth0 > iface eth0 inet static > address 192.168.4.21 > broadcast 192.168.4.255 > netmask 255.255.255.0 > gateway 192.168.4.1 ... and yet you tell it to use the same geteway as as xenbr0.4. Obviously that won't work. > Does anyone have experience configuring VLANs with the bridge interface? Either: - bridge the TRUNK, do NOT create the vlan interface (xenbr0.4) in the host, and create the vlan interface in the guest (eth0.4). OR - create a vlan interface on the host (eth0.4), and then create a bridge on TOP of that (e.g. xenbr4), and configure the guest interface (eth0) the way you did -- Fajar _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Fri Jan 08 10:04:59 2016 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 08 Jan 2016 10:04:59 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1aHTuA-0006HM-Lp; Fri, 08 Jan 2016 10:04:22 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1aHTu9-0006HH-Jl for xen-users@lists.xen.org; Fri, 08 Jan 2016 10:04:21 +0000 Received: from [193.109.254.147] by server-1.bemta-14.messagelabs.com id 38/7B-28791-4A98F865; Fri, 08 Jan 2016 10:04:20 +0000 X-Env-Sender: prvs=80839a509=Ian.Campbell@citrix.com X-Msg-Ref: server-16.tower-27.messagelabs.com!1452247451!15433440!1 X-Originating-IP: [66.165.176.63] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjYuMTY1LjE3Ni42MyA9PiAzMDYwNDg=\n, received_headers: No Received headers X-StarScan-Received: X-StarScan-Version: 7.35.1; banners=-,-,- X-VirusChecked: Checked Received: (qmail 15435 invoked from network); 8 Jan 2016 10:04:12 -0000 Received: from smtp02.citrix.com (HELO SMTP02.CITRIX.COM) (66.165.176.63) by server-16.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 8 Jan 2016 10:04:12 -0000 X-IronPort-AV: E=Sophos;i="5.20,537,1444694400"; d="scan'208";a="329815414" Message-ID: <1452247450.21055.300.camel@citrix.com> From: Ian Campbell To: Simon Hobson , "xen-users@lists.xen.org" Date: Fri, 8 Jan 2016 10:04:10 +0000 In-Reply-To: <19C2C25B-B0E5-4F13-998E-BCB0D4A88922@thehobsons.co.uk> References: <19C2C25B-B0E5-4F13-998E-BCB0D4A88922@thehobsons.co.uk> X-Mailer: Evolution 3.18.2-1 MIME-Version: 1.0 X-DLP: MIA2 Cc: Pavan Maddamsetti Subject: Re: [Xen-users] VLAN guest networking: near 100% packet loss X-BeenThere: xen-users@lists.xen.org X-Mailman-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 Q0MtaW5nIHRoZSBPL1AsIGFzIGlzIHVzdWFsbHkgb24gdGhlIFhlbiBsaXN0cy4KCsKgT24gRnJp LCAyMDE2LTAxLTA4IGF0IDA3OjU3ICswMDAwLCBTaW1vbiBIb2Jzb24gd3JvdGU6Cj4gUGF2YW4g TWFkZGFtc2V0dGkgPHBhdmFuLm1hZGRhbXNldHRpQGdtYWlsLmNvbT4gd3JvdGU6Cj4gCj4gPiBJ IGFtIG5ldyB0byB0aGUgbWFpbGluZyBsaXN0Cj4gCj4gV2VsY29tZQo+IAo+IAo+ID4gTXkgc2V0 dXAgY29uc2lzdHMgb2YgRGViaWFuIDggb24gYm90aCBkb20wCj4gPiBhbmQgZG9tVSwgYW5kIHRo ZSBtYWNoaW5lIGlzIGNvbm5lY3RlZCB0byBhIFZMQU4gdGFnZ2VkIHBvcnQgb24gdGhlCj4gPiBz d2l0Y2ggbWVhbmluZyB0aGF0IHRoZSBob3N0IG11c3QgYmUgVkxBTi1hd2FyZS4KPiA+IAo+ID4g RG9tMCBoYXMgaW50ZXJuZXQgcmVhY2hhYmlsaXR5IGJ1dCBkb21VIGlzIG9ubHkgYWJsZSB0byBl c3RhYmxpc2gKPiA+IGNvbm5lY3Rpb25zIHRvIGhvc3RzIG9uIHRoZSBMQU47IHBpbmdzIHNlbnQg dG8gZXh0ZXJuYWwgbWFjaGluZXMgY29tZQo+ID4gYmFjayB3aXRoIHZpcnR1YWxseSAxMDAlIHBh Y2tldCBsb3NzIGJ1dCBpdCBpcyB1bmxpa2VseSBhIHJvdXRpbmcKPiA+IGlzc3VlIGJlY2F1c2Ug c29tZXRpbWVzIG9uZSBvciB0d28gcGFja2V0cyBnZXQgdGhyb3VnaC4KPiA+IAo+ID4gRG9tMCBu ZXR3b3JrIGNvbmZpZ3VyYXRpb24gaXM6Cj4gPiAKPiA+IGF1dG8geGVuYnIwCj4gPiBpZmFjZSB4 ZW5icjAgaW5ldCBtYW51YWwKPiA+IMKgwqDCoGJyaWRnZV9wb3J0cyBldGgxCj4gPiDCoMKgwqBi cmlkZ2Vfc3RwIG9mZgo+ID4gwqDCoMKgYnJpZGdlX3dhaXRwb3J0IDAKPiA+IMKgwqDCoGJyaWRn ZV9mZCAwCj4gPiAKPiA+IGF1dG8geGVuYnIwLjQKPiA+IGlmYWNlIHhlbmJyMC40IGluZXQgc3Rh dGljCj4gPiDCoMKgwqBhZGRyZXNzIDE5Mi4xNjguNC4xMwo+ID4gwqDCoMKgYnJvYWRjYXN0IDE5 Mi4xNjguNC4yNTUKPiA+IMKgwqDCoG5ldG1hc2sgMjU1LjI1NS4yNTUuMAo+ID4gwqDCoMKgZ2F0 ZXdheSAxOTIuMTY4LjQuMQo+ID4gwqDCoMKgdmxhbi1yYXctZGV2aWNlIHhlbmJyMAo+IAo+IEkn bSBubyBleHBlcnQgYnV0IEkgd2FzIHVuZGVyIHRoZSBpbXByZXNzaW9uIHRoYXQgdGhlIGJyaWRn aW5nIChub3Qgc3VyZQo+IHdoZXRoZXIgdGhhdCdzIHRoZSBob3N0IHNpZGUgb3IgdGhlIFhlbiB1 cyBvZiBpdCkgZG9lc24ndCBzdXBwb3J0IFZMQU4KPiB0YWdnaW5nIHdpdGhpbiB0aGUgdmlydHVh bCBzd2l0Y2guCgpGV0lXIEkgaGFkIHRoZSBzYW1lIGltcHJlc3Npb24uIElmIEkgd2FzIGRvaW5n IHRoaXMgSSB3b3VsZCBtYWtlIHhlbmJyMC40CnVzZSBldGgwLjQgYXMgdGhlIHVuZGVybHlpbmcg ZGV2aWNlIGFuZCB1c2UgeGVuYnIwLjQgaW4gbXkgZ3Vlc3QgY29uZmlnLgoKT3IgYXMgRmFqYXIg ZXhwbGFpbmVkIHlvdSBjb3VsZCBhbHNvIGV4cG9zZSB0aGUgVkxBTiB0cnVuayBhbGwgdGhlIHdh eSB0bwp0aGUgZ3Vlc3QgYW5kIGRvIHRoZSB0YWdnaW5nIHRoZXJlLgoKPiAgSSBoYXZlIGEgaG9z dCB1c2luZyBhIFZMQU4gdHJ1bmsgbGlrZSB5b3UgZGVzY3JpYmUsIGJ1dCB3aGF0IEkndmUgZG9u ZQo+IGlzIGJ1aWxkIGEgc2VwYXJhdGUgYnJpZGdlIGZvciBlYWNoIFZMQU4gOgoKSW4geW91ciBu YW1pbmcgc2NoZW1lIHBldGgqIGFyZSB3aGF0IHdvdWxkIGJlIGRlZmF1bHQgYmUgZXRoKiAoZS5n LiBwZXRoaW50Cm1pZ2h0IGhhdmUgYmVlbiBldGgwIGF0IHNvbWUgcG9pbnQpIGFuZCBldGgqIGFy ZSB0aGUgbmFtZXMgb2YgeW91ciBicmlkZ2UKZGV2aWNlcz8gKEp1c3QgdG8gaGVscCBQYXZhbiB0 cmFuc2xhdGUsIGl0J3MgYWxzbyBob3cgc21lIG9sZGVyIHZlcnNpb25zIG9mClhlbiBkaWQgdGhp bmdzIGJ5IGRlZmF1bHQpCgpTZWUgYWxzb8KgaHR0cDovL3dpa2kueGVuLm9yZy93aWtpL0hvc3RD b25maWd1cmF0aW9uL05ldHdvcmtpbmfCoGZvciBzb21lCmV4YW1wbGVzLgoKSWFuLgoKX19fX19f X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KWGVuLXVzZXJzIG1haWxp bmcgbGlzdApYZW4tdXNlcnNAbGlzdHMueGVuLm9yZwpodHRwOi8vbGlzdHMueGVuLm9yZy94ZW4t dXNlcnM= From xen-users-bounces@lists.xen.org Fri Jan 08 10:04:59 2016 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 08 Jan 2016 10:04:59 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1aHTuA-0006HM-Lp; Fri, 08 Jan 2016 10:04:22 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1aHTu9-0006HH-Jl for xen-users@lists.xen.org; Fri, 08 Jan 2016 10:04:21 +0000 Received: from [193.109.254.147] by server-1.bemta-14.messagelabs.com id 38/7B-28791-4A98F865; Fri, 08 Jan 2016 10:04:20 +0000 X-Env-Sender: prvs=80839a509=Ian.Campbell@citrix.com X-Msg-Ref: server-16.tower-27.messagelabs.com!1452247451!15433440!1 X-Originating-IP: [66.165.176.63] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjYuMTY1LjE3Ni42MyA9PiAzMDYwNDg=\n, received_headers: No Received headers X-StarScan-Received: X-StarScan-Version: 7.35.1; banners=-,-,- X-VirusChecked: Checked Received: (qmail 15435 invoked from network); 8 Jan 2016 10:04:12 -0000 Received: from smtp02.citrix.com (HELO SMTP02.CITRIX.COM) (66.165.176.63) by server-16.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 8 Jan 2016 10:04:12 -0000 X-IronPort-AV: E=Sophos;i="5.20,537,1444694400"; d="scan'208";a="329815414" Message-ID: <1452247450.21055.300.camel@citrix.com> From: Ian Campbell To: Simon Hobson , "xen-users@lists.xen.org" Date: Fri, 8 Jan 2016 10:04:10 +0000 In-Reply-To: <19C2C25B-B0E5-4F13-998E-BCB0D4A88922@thehobsons.co.uk> References: <19C2C25B-B0E5-4F13-998E-BCB0D4A88922@thehobsons.co.uk> X-Mailer: Evolution 3.18.2-1 MIME-Version: 1.0 X-DLP: MIA2 Cc: Pavan Maddamsetti Subject: Re: [Xen-users] VLAN guest networking: near 100% packet loss X-BeenThere: xen-users@lists.xen.org X-Mailman-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 Q0MtaW5nIHRoZSBPL1AsIGFzIGlzIHVzdWFsbHkgb24gdGhlIFhlbiBsaXN0cy4KCsKgT24gRnJp LCAyMDE2LTAxLTA4IGF0IDA3OjU3ICswMDAwLCBTaW1vbiBIb2Jzb24gd3JvdGU6Cj4gUGF2YW4g TWFkZGFtc2V0dGkgPHBhdmFuLm1hZGRhbXNldHRpQGdtYWlsLmNvbT4gd3JvdGU6Cj4gCj4gPiBJ IGFtIG5ldyB0byB0aGUgbWFpbGluZyBsaXN0Cj4gCj4gV2VsY29tZQo+IAo+IAo+ID4gTXkgc2V0 dXAgY29uc2lzdHMgb2YgRGViaWFuIDggb24gYm90aCBkb20wCj4gPiBhbmQgZG9tVSwgYW5kIHRo ZSBtYWNoaW5lIGlzIGNvbm5lY3RlZCB0byBhIFZMQU4gdGFnZ2VkIHBvcnQgb24gdGhlCj4gPiBz d2l0Y2ggbWVhbmluZyB0aGF0IHRoZSBob3N0IG11c3QgYmUgVkxBTi1hd2FyZS4KPiA+IAo+ID4g RG9tMCBoYXMgaW50ZXJuZXQgcmVhY2hhYmlsaXR5IGJ1dCBkb21VIGlzIG9ubHkgYWJsZSB0byBl c3RhYmxpc2gKPiA+IGNvbm5lY3Rpb25zIHRvIGhvc3RzIG9uIHRoZSBMQU47IHBpbmdzIHNlbnQg dG8gZXh0ZXJuYWwgbWFjaGluZXMgY29tZQo+ID4gYmFjayB3aXRoIHZpcnR1YWxseSAxMDAlIHBh Y2tldCBsb3NzIGJ1dCBpdCBpcyB1bmxpa2VseSBhIHJvdXRpbmcKPiA+IGlzc3VlIGJlY2F1c2Ug c29tZXRpbWVzIG9uZSBvciB0d28gcGFja2V0cyBnZXQgdGhyb3VnaC4KPiA+IAo+ID4gRG9tMCBu ZXR3b3JrIGNvbmZpZ3VyYXRpb24gaXM6Cj4gPiAKPiA+IGF1dG8geGVuYnIwCj4gPiBpZmFjZSB4 ZW5icjAgaW5ldCBtYW51YWwKPiA+IMKgwqDCoGJyaWRnZV9wb3J0cyBldGgxCj4gPiDCoMKgwqBi cmlkZ2Vfc3RwIG9mZgo+ID4gwqDCoMKgYnJpZGdlX3dhaXRwb3J0IDAKPiA+IMKgwqDCoGJyaWRn ZV9mZCAwCj4gPiAKPiA+IGF1dG8geGVuYnIwLjQKPiA+IGlmYWNlIHhlbmJyMC40IGluZXQgc3Rh dGljCj4gPiDCoMKgwqBhZGRyZXNzIDE5Mi4xNjguNC4xMwo+ID4gwqDCoMKgYnJvYWRjYXN0IDE5 Mi4xNjguNC4yNTUKPiA+IMKgwqDCoG5ldG1hc2sgMjU1LjI1NS4yNTUuMAo+ID4gwqDCoMKgZ2F0 ZXdheSAxOTIuMTY4LjQuMQo+ID4gwqDCoMKgdmxhbi1yYXctZGV2aWNlIHhlbmJyMAo+IAo+IEkn bSBubyBleHBlcnQgYnV0IEkgd2FzIHVuZGVyIHRoZSBpbXByZXNzaW9uIHRoYXQgdGhlIGJyaWRn aW5nIChub3Qgc3VyZQo+IHdoZXRoZXIgdGhhdCdzIHRoZSBob3N0IHNpZGUgb3IgdGhlIFhlbiB1 cyBvZiBpdCkgZG9lc24ndCBzdXBwb3J0IFZMQU4KPiB0YWdnaW5nIHdpdGhpbiB0aGUgdmlydHVh bCBzd2l0Y2guCgpGV0lXIEkgaGFkIHRoZSBzYW1lIGltcHJlc3Npb24uIElmIEkgd2FzIGRvaW5n IHRoaXMgSSB3b3VsZCBtYWtlIHhlbmJyMC40CnVzZSBldGgwLjQgYXMgdGhlIHVuZGVybHlpbmcg ZGV2aWNlIGFuZCB1c2UgeGVuYnIwLjQgaW4gbXkgZ3Vlc3QgY29uZmlnLgoKT3IgYXMgRmFqYXIg ZXhwbGFpbmVkIHlvdSBjb3VsZCBhbHNvIGV4cG9zZSB0aGUgVkxBTiB0cnVuayBhbGwgdGhlIHdh eSB0bwp0aGUgZ3Vlc3QgYW5kIGRvIHRoZSB0YWdnaW5nIHRoZXJlLgoKPiAgSSBoYXZlIGEgaG9z dCB1c2luZyBhIFZMQU4gdHJ1bmsgbGlrZSB5b3UgZGVzY3JpYmUsIGJ1dCB3aGF0IEkndmUgZG9u ZQo+IGlzIGJ1aWxkIGEgc2VwYXJhdGUgYnJpZGdlIGZvciBlYWNoIFZMQU4gOgoKSW4geW91ciBu YW1pbmcgc2NoZW1lIHBldGgqIGFyZSB3aGF0IHdvdWxkIGJlIGRlZmF1bHQgYmUgZXRoKiAoZS5n LiBwZXRoaW50Cm1pZ2h0IGhhdmUgYmVlbiBldGgwIGF0IHNvbWUgcG9pbnQpIGFuZCBldGgqIGFy ZSB0aGUgbmFtZXMgb2YgeW91ciBicmlkZ2UKZGV2aWNlcz8gKEp1c3QgdG8gaGVscCBQYXZhbiB0 cmFuc2xhdGUsIGl0J3MgYWxzbyBob3cgc21lIG9sZGVyIHZlcnNpb25zIG9mClhlbiBkaWQgdGhp bmdzIGJ5IGRlZmF1bHQpCgpTZWUgYWxzb8KgaHR0cDovL3dpa2kueGVuLm9yZy93aWtpL0hvc3RD b25maWd1cmF0aW9uL05ldHdvcmtpbmfCoGZvciBzb21lCmV4YW1wbGVzLgoKSWFuLgoKX19fX19f X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KWGVuLXVzZXJzIG1haWxp bmcgbGlzdApYZW4tdXNlcnNAbGlzdHMueGVuLm9yZwpodHRwOi8vbGlzdHMueGVuLm9yZy94ZW4t dXNlcnM= From xen-users-bounces@lists.xen.org Fri Jan 08 10:42:55 2016 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 08 Jan 2016 10:42: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 1aHUV5-0007nG-4w; Fri, 08 Jan 2016 10:42:31 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1aHUV2-0007nB-V2 for xen-users@lists.xen.org; Fri, 08 Jan 2016 10:42:29 +0000 Received: from [85.158.143.35] by server-2.bemta-4.messagelabs.com id 9D/A7-08977-4929F865; Fri, 08 Jan 2016 10:42:28 +0000 X-Env-Sender: linux@thehobsons.co.uk X-Msg-Ref: server-12.tower-21.messagelabs.com!1452249745!9144696!1 X-Originating-IP: [81.174.135.208] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 7.35.1; banners=-,-,- X-VirusChecked: Checked Received: (qmail 40177 invoked from network); 8 Jan 2016 10:42:25 -0000 Received: from patsy.thehobsons.co.uk (HELO patsy.thehobsons.co.uk) (81.174.135.208) by server-12.tower-21.messagelabs.com with DHE-RSA-AES256-GCM-SHA384 encrypted SMTP; 8 Jan 2016 10:42:25 -0000 X-Virus-Scanned: Debian amavisd-new at patsy.thehobsons.co.uk Received: from [192.168.7.10] (wifi2.furness.net [195.8.169.130]) by patsy.thehobsons.co.uk (Postfix) with ESMTPSA id D42E21A074 for ; Fri, 8 Jan 2016 10:42:21 +0000 (UTC) Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\)) From: Simon Hobson In-Reply-To: <1452247450.21055.300.camel@citrix.com> Date: Fri, 8 Jan 2016 10:42:19 +0000 Message-Id: <40C52470-C069-44B4-AF70-2E25C75B3975@thehobsons.co.uk> References: <19C2C25B-B0E5-4F13-998E-BCB0D4A88922@thehobsons.co.uk> <1452247450.21055.300.camel@citrix.com> To: "xen-users@lists.xen.org" X-Mailer: Apple Mail (2.1510) Subject: Re: [Xen-users] VLAN guest networking: near 100% packet loss X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org Ian Campbell wrote: > In your naming scheme peth* are what would be default be eth* (e.g. pethint > might have been eth0 at some point) and eth* are the names of your bridge > devices? (Just to help Pavan translate, it's also how sme older versions of > Xen did things by default) Ah yes, I use udev rules (/etc/udev/rules.d/70-persistent-net.rules on Debian Wheezy*) to set the physical interfaces to peth and then name my bridges eth. Eg : # PCI device 0x14e4:0x165b (tg3) SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="b4:99:ba:xx:xx:xx", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="peth0" I also use names rather than numbers (eg ethlan rather than eth2) as it makes it much easier keeping track of what's connected to where when there are multiple networks involved. * Given that Debian have given in to having the system bastardised, I've no idea what it may or may not be called in Debian Jessie or what hoops you may have to jump through to keep "meaningful" device names. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Fri Jan 08 10:42:55 2016 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 08 Jan 2016 10:42: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 1aHUV5-0007nG-4w; Fri, 08 Jan 2016 10:42:31 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1aHUV2-0007nB-V2 for xen-users@lists.xen.org; Fri, 08 Jan 2016 10:42:29 +0000 Received: from [85.158.143.35] by server-2.bemta-4.messagelabs.com id 9D/A7-08977-4929F865; Fri, 08 Jan 2016 10:42:28 +0000 X-Env-Sender: linux@thehobsons.co.uk X-Msg-Ref: server-12.tower-21.messagelabs.com!1452249745!9144696!1 X-Originating-IP: [81.174.135.208] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 7.35.1; banners=-,-,- X-VirusChecked: Checked Received: (qmail 40177 invoked from network); 8 Jan 2016 10:42:25 -0000 Received: from patsy.thehobsons.co.uk (HELO patsy.thehobsons.co.uk) (81.174.135.208) by server-12.tower-21.messagelabs.com with DHE-RSA-AES256-GCM-SHA384 encrypted SMTP; 8 Jan 2016 10:42:25 -0000 X-Virus-Scanned: Debian amavisd-new at patsy.thehobsons.co.uk Received: from [192.168.7.10] (wifi2.furness.net [195.8.169.130]) by patsy.thehobsons.co.uk (Postfix) with ESMTPSA id D42E21A074 for ; Fri, 8 Jan 2016 10:42:21 +0000 (UTC) Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\)) From: Simon Hobson In-Reply-To: <1452247450.21055.300.camel@citrix.com> Date: Fri, 8 Jan 2016 10:42:19 +0000 Message-Id: <40C52470-C069-44B4-AF70-2E25C75B3975@thehobsons.co.uk> References: <19C2C25B-B0E5-4F13-998E-BCB0D4A88922@thehobsons.co.uk> <1452247450.21055.300.camel@citrix.com> To: "xen-users@lists.xen.org" X-Mailer: Apple Mail (2.1510) Subject: Re: [Xen-users] VLAN guest networking: near 100% packet loss X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org Ian Campbell wrote: > In your naming scheme peth* are what would be default be eth* (e.g. pethint > might have been eth0 at some point) and eth* are the names of your bridge > devices? (Just to help Pavan translate, it's also how sme older versions of > Xen did things by default) Ah yes, I use udev rules (/etc/udev/rules.d/70-persistent-net.rules on Debian Wheezy*) to set the physical interfaces to peth and then name my bridges eth. Eg : # PCI device 0x14e4:0x165b (tg3) SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="b4:99:ba:xx:xx:xx", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="peth0" I also use names rather than numbers (eg ethlan rather than eth2) as it makes it much easier keeping track of what's connected to where when there are multiple networks involved. * Given that Debian have given in to having the system bastardised, I've no idea what it may or may not be called in Debian Jessie or what hoops you may have to jump through to keep "meaningful" device names. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Fri Jan 08 12:19:57 2016 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 08 Jan 2016 12:19: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 1aHW0I-0003gs-8H; Fri, 08 Jan 2016 12:18:50 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1aHQ02-0003UJ-Iu; Fri, 08 Jan 2016 05:54:10 +0000 Received: from [85.158.137.68] by server-6.bemta-3.messagelabs.com id 2B/40-29649-10F4F865; Fri, 08 Jan 2016 05:54:09 +0000 X-Env-Sender: jfehlig@suse.com X-Msg-Ref: server-15.tower-31.messagelabs.com!1452232446!14282144!1 X-Originating-IP: [137.65.250.81] X-SpamReason: No, hits=0.5 required=7.0 tests=BODY_RANDOM_LONG X-StarScan-Received: X-StarScan-Version: 7.35.1; banners=-,-,- X-VirusChecked: Checked Received: (qmail 27773 invoked from network); 8 Jan 2016 05:54:08 -0000 Received: from smtp2.provo.novell.com (HELO smtp2.provo.novell.com) (137.65.250.81) by server-15.tower-31.messagelabs.com with DHE-RSA-AES256-GCM-SHA384 encrypted SMTP; 8 Jan 2016 05:54:08 -0000 Received: from [192.168.0.28] (prv-ext-foundry1int.gns.novell.com [137.65.251.240]) by smtp2.provo.novell.com with ESMTP (TLS encrypted); Thu, 07 Jan 2016 22:54:03 -0700 Message-ID: <568F4EF9.2090609@suse.com> Date: Thu, 07 Jan 2016 22:54:01 -0700 From: Jim Fehlig User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.7.0 MIME-Version: 1.0 To: Ian Campbell , Andreas Pflug , xen-users@lists.xen.org References: <56812352.8060500@pse-consulting.de> <1451907382.13361.37.camel@citrix.com> <568A5BEE.9090808@pse-consulting.de> <1451909615.13361.46.camel@citrix.com> <568A6618.5@pse-consulting.de> <1451911062.13361.60.camel@citrix.com> In-Reply-To: <1451911062.13361.60.camel@citrix.com> X-Mailman-Approved-At: Fri, 08 Jan 2016 12:18:49 +0000 Cc: Olaf Hering , xen-devel Subject: Re: [Xen-users] Missing libvirt+libxl functionality (Was: Re: Programmatic administration of Xen machines) X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/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/04/2016 05:37 AM, Ian Campbell wrote: > On Mon, 2016-01-04 at 13:31 +0100, Andreas Pflug wrote: >> Am 04.01.16 um 13:13 schrieb Ian Campbell: >>> On Mon, 2016-01-04 at 12:47 +0100, Andreas Pflug wrote: >>>> Am 04.01.16 um 12:36 schrieb Ian Campbell: >>>>> Sorry to hijack this thread. >>>>> >>>>> On Mon, 2015-12-28 at 12:56 +0100, Andreas Pflug wrote: >>>>>> Actually, I find virsh a bad idea since its support for the new >>>>>> xl >>>>>> interface isn't feature complete as the old xm interface was. I >>>>>> had >>>>>> to >>>>>> realize this the hard way when my virsh based python tools didn't >>>>>> work >>>>>> as expected after upgrading from xm to xl. >>>>> Note that virsh speaks to libxl directly, not via xl. >>>>> >>>>> Please can you list the functionality of libvirt's libxl backed >>>>> which >>>>> is >>>>> missing compared to the old xend based one? >>>> libvirt only handles domains created through it, i.e. using xl at the >>>> same time is incompatible. Since dom0 can't be created using libvirt, >>>> it's missing from "virsh list" in any case. >>> This works for me with a reasonably modern set of bits: >>> >>> root@marilith-n0 :~# virsh list >>> Id Name State >>> ---------------------------------------------------- >>> 0 Domain-0 running >>> 13 d running >>> >>> It probably requires the correct running of xen-init-dom0 during boot >>> (likely via the xencommons initscript). >>> >>> I could believe it was broken at some point in history though. >>> >>>> libvirt stores its own state, not using libxl/xenstore stuff. >>> Please can you elaborate. >> I tested on Debian with 4.4.1 and xl toolstack. See the author's blog >> post: >> https://blog.xenproject.org/2014/01/17/libvirt-support-for-xens-new- >> libxenlight-toolstack/ > I think that particular aspect of the blog post is no longer valid, at > least AFAICT with modern libvirt. Commit 45697fe5 added dom0 management support to the libvirt libxl driver. libvirt >= 1.2.18 contains the commit. > >> I had even more trouble, e.g. I wasn't able to use non-standard block >> scripts (neither via /etc/xen/scripts/block-XXX nor via a script >> parameter) which are mandatory for me. > Looking at the code it seems like this is still missing. > > Copying the devel list and maintainer in case I've either missed something > or there is a reason for this (other than "still on the TODO list", which I > expect is most likely). It is on a TODO list, but I'm not sure how to solve it :-/. Unlike the libxl_device_disk struct, the corresponding libvirt struct does not support a 'script' field, and I doubt it ever will. Repeated attempts to add a