I've done a little digging, and have found some coalesce errors = in SM.log. Pastebin link below:

Before exporting the snapshot, the scripts sets t= he is-a-template parameter to false, essentially making the snapshot a func= tional VM in its own rite. Could this be confusing the coalesce tool? If so= , why only now and only on this server?

Help would be=C2=A0appreciated... The export has hung (= last modified time 06:33) and, based on previous experience, the only solut= ion is a host reboot.

I'm having trouble with a VM running on XCP= 1.1 (installed from CD). From time to time, a scripted backup (which perfo= rms a snapshot, exports it to an XVA, removes snapshot), gets itself "= stuck" in at the exports phase. I've checked the target disk twice= for errors (negative) and so I can only assume some internal XCP process i= s conflicting. The export does take quite a while, as we're exporting o= ver 300GB over USB, so it's more than feasible some coalesce task attem= pts to run.

Strangely, this problem occurs on only one of nearly a = dozen XCP installations, all running this backup script.

I've done a little digging, and have found some coalesce errors = in SM.log. Pastebin link below:

http://pastebi= n.com/e9UirM20

Help would be=C2=A0appreciated... The export has hung (= last modified time 06:33) and, based on previous experience, the only solut= ion is a host reboot.

--00504502da096d04cc04b80c5dbe-- --===============4256909180812410830== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ xen-api mailing list xen-api@lists.xensource.com http://lists.xensource.com/mailman/listinfo/xen-api --===============4256909180812410830==-- From xen-api-bounces@lists.xensource.com Fri Feb 03 13:42:58 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 03 Feb 2012 13:42: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 1RtJPf-000234-Ct; Fri, 03 Feb 2012 13:42:51 +0000 Received: from mail182.messagelabs.com ([85.158.139.83]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1RtJPd-00022g-Oq; Fri, 03 Feb 2012 13:42:50 +0000 X-Env-Sender: lars.kurth.xen@gmail.com X-Msg-Ref: server-13.tower-182.messagelabs.com!1328276562!13046231!1 X-Originating-IP: [209.85.212.171] X-SpamReason: No, hits=0.3 required=7.0 tests=HTML_MESSAGE,RCVD_BY_IP X-StarScan-Version: 6.5.5; banners=-,-,- X-VirusChecked: Checked Received: (qmail 21262 invoked from network); 3 Feb 2012 13:42:42 -0000 Received: from mail-wi0-f171.google.com (HELO mail-wi0-f171.google.com) (209.85.212.171) by server-13.tower-182.messagelabs.com with RC4-SHA encrypted SMTP; 3 Feb 2012 13:42:42 -0000 Received: by wibhm2 with SMTP id hm2so7261341wib.30 for ; Fri, 03 Feb 2012 05:42:42 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=sender:message-id:date:from:user-agent:mime-version:to:subject :content-type; bh=rXJSwMJJcdGbI5GWy5kM1PwYR/7sBouCMtRkaP3Q76I=; b=rrNsi7pEC3K8eivaQS84H7FeQTF0yuOWEa+suHdoVum6fgvYXNp+230/gS2ZSV4v6v l1lpR+X7Uqf1/2Bi25p4/JzDi7hHitELQFvafFvPJSXhhvFJnitaaDfGqR2kdwEokcbx wrvqRaYFbAcZVgAML0aoY+HXQfAK06BjvNOOQ= Received: by 10.180.89.71 with SMTP id bm7mr24788379wib.20.1328276562323; Fri, 03 Feb 2012 05:42:42 -0800 (PST) Received: from [172.16.26.10] (d54C6D43E.access.telenet.be. [84.198.212.62]) by mx.google.com with ESMTPS id hc10sm6629996wib.8.2012.02.03.05.42.38 (version=SSLv3 cipher=OTHER); Fri, 03 Feb 2012 05:42:41 -0800 (PST) Message-ID: <4F2BE44B.5030003@xen.org> Date: Fri, 03 Feb 2012 13:42:35 +0000 From: Lars Kurth User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:9.0) Gecko/20111222 Thunderbird/9.0.1 MIME-Version: 1.0 To: "xen-devel@lists.xensource.com" , "xen-users@lists.xensource.com" , "xen-api@lists.xensource.com" , "xen-arm@lists.xensource.com" Subject: [Xen-API] Give us feedback for the new Xen.org site X-BeenThere: xen-api@lists.xensource.com X-Mailman-Version: 2.1.13 Precedence: list List-Id: Discussion of API issues surrounding Xen List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============8060068836106055534==" Sender: xen-api-bounces@lists.xensource.com Errors-To: xen-api-bounces@lists.xensource.com This is a multi-part message in MIME format. --===============8060068836106055534== Content-Type: multipart/alternative; boundary="------------070106040103040206070901" This is a multi-part message in MIME format. --------------070106040103040206070901 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Dear Community Members, I am finally able to build a new website for Xen.org. The aim of this work is to create an engaging and integrated community web site that invites participation and acts as a portal for Xen users, developers and companies in the eco-system. You can give input on the site by going to http://wiki.xen.org/wiki/New_Xen_Website The new site will have several main areas: The home page, which mainly acts as an aggregator for news and activity happening in the community. This should make it easier for newcomers to Xen, to have a brief look and get a feeling of the vibrancy of the Xen community.There is actually a lot of activity today: it is merely obscured and hidden as the activity is dispersed to many places. The home page will also provide a window into the new Xen.org blog, as well as sections for Xen events, etc. An area for users. This area will provide information about Xen and Xen projects, will help you learn about Xen, will point people to downloads and Linux/Unix distributions that contain Xen, will help you find documentation,will help you get help and support, etc. Xen has traditionally been a very developer focused community.As a consequence we have not supported our users that well. I have some open questions in this area, where I will be looking for your input. For example: is there a preference for mailing lists, forums, or stackoverflow like functionality? How should we best link to Linux distributions and other projects that distribute Xen? An eco-system area: this is essentially a searchable directory of product and projects that use Xen, modify Xen, build on top of Xen, distribute Xen, etc. It is also a directory of research around Xen and services such as consultancy, training, hosting and cloud vendors that are built on top of Xen. This section will be fairly interactive: the intention is that if you are a vendor, you can add an entry to the directory which will be approved by a moderator moderator before publication. As a user of the directory, you can rate, recommend, comment on vendors, products, projects, etc. An area for developers: this contains project descriptions, links to downloads, codelines, information about governance, mailing lists, etc. Other changes: the site will have the capability to register users. Generally, all areas of the site will be accessible without any user account, except for areas where you need to write to the site and identification is thus necessary. We envisage that we will be able to implement single sign-on capability for the new site and at least theXen wiki. There will be user profiles that allow you to provide information about how you use Xen, but ultimately you only have to provide what you are comfortable with. The idea is for example that I can implement functionality such as the old community spotlight section by just maintaining a list of profile names. Name, pictures, bio, etc. would be managed and maintained by you. I am also looking at capabilities, such as being able to send newsletters, to registered site users. *Where I need your input* ** We will consult you on questions such as look and feel, on a new or revamped Xen logo, on new panda's, on navigation, on some of the headlines and taglines. In some areas we do not quite know what you want from Xen.org: e.g. should we have a user mailing list, user fora and/or support forum functionality similar to stackoverflow? Should we make the developer mailing lists accessible via the website? I also wanted to get views on whether it is OK to require logging into the site before you download a Xen or XCP binary. My thinking is that this is not good, but that it is OK to ask you nicely to sign in and/or create an account before you download. Having some information about its users is important to maintain the long term health of an open source project: today Xen has very little information about its users. Mainly,because we never asked. Providing information is an easy way how you can give something back to the community. Another area where we will consult you is on how we migrate you from existing systems to the new one. Is it OK, to migrate existing users to the new site (using some kind of opt-out or activation scheme)? Is it not, etc.? Links to feedback sheets, mockups, etc. can be found here: http://wiki.xen.org/wiki/New_Xen_Website Looking forward to hear from you Best Regards Lars ** --------------070106040103040206070901 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit

Dear Community Members,

I am finally able to build a new website for Xen.org. The aim of this work is to create an engaging and integrated community web site that invites participation and acts as a portal for Xen users, developers and companies in the eco-system. You can give input on the site by going to http://wiki.xen.org/wiki/New_Xen_Website

The new site will have several main areas:

The home page, which mainly acts as an aggregator for news and activity happening in the community. This should make it easier for newcomers to Xen, to have a brief look and get a feeling of the vibrancy of the Xen community. There is actually a lot of activity today: it is merely obscured and hidden as the activity is dispersed to many places. The home page will also provide a window into the new Xen.org blog, as well as sections for Xen events, etc.

An area for users. This area will provide information about Xen and Xen projects, will help you learn about Xen, will point people to downloads and Linux/Unix distributions that contain Xen, will help you find documentation, will help you get help and support, etc. Xen has traditionally been a very developer focused community. As a consequence we have not supported our users that well. I have some open questions in this area, where I will be looking for your input. For example: is there a preference for mailing lists, forums, or stackoverflow like functionality? How should we best link to Linux distributions and other projects that distribute Xen?

An eco-system area: this is essentially a searchable directory of product and projects that use Xen, modify Xen, build on top of Xen, distribute Xen, etc. It is also a directory of research around Xen and services such as consultancy, training, hosting and cloud vendors that are built on top of Xen. This section will be fairly interactive: the intention is that if you are a vendor, you can add an entry to the directory which will be approved by a moderator moderator before publication. As a user of the directory, you can rate, recommend, comment on vendors, products, projects, etc.

An area for developers: this contains project descriptions, links to downloads, codelines, information about governance, mailing lists, etc.

Other changes: the site will have the capability to register users. Generally, all areas of the site will be accessible without any user account, except for areas where you need to write to the site and identification is thus necessary. We envisage that we will be able to implement single sign-on capability for the new site and at least the Xen wiki. There will be user profiles that allow you to provide information about how you use Xen, but ultimately you only have to provide what you are comfortable with. The idea is for example that I can implement functionality such as the old community spotlight section by just maintaining a list of profile names. Name, pictures, bio, etc. would be managed and maintained by you. I am also looking at capabilities, such as being able to send newsletters, to registered site users.

Where I need your input

We will consult you on questions such as look and feel, on a new or revamped Xen logo, on new panda's, on navigation, on some of the headlines and taglines.

In some areas we do not quite know what you want from Xen.org: e.g. should we have a user mailing list, user fora and/or support forum functionality similar to stackoverflow? Should we make the developer mailing lists accessible via the website?

I also wanted to get views on whether it is OK to require logging into the site before you download a Xen or XCP binary. My thinking is that this is not good, but that it is OK to ask you nicely to sign in and/or create an account before you download. Having some information about its users is important to maintain the long term health of an open source project: today Xen has very little information about its users. Mainly, because we never asked. Providing information is an easy way how you can give something back to the community.

Another area where we will consult you is on how we migrate you from existing systems to the new one. Is it OK, to migrate existing users to the new site (using some kind of opt-out or activation scheme)? Is it not, etc.?

Links to feedback sheets, mockups, etc. can be found here: http://wiki.xen.org/wiki/New_Xen_Website

Looking forward to hear from you

Best Regards
Lars

Dear Community Members,

The new site will have several main areas:

An area for developers: this contains project descriptions, links to downloads, codelines, information about governance, mailing lists, etc.

Where I need your input

We will consult you on questions such as look and feel, on a new or revamped Xen logo, on new panda's, on navigation, on some of the headlines and taglines.

Links to feedback sheets, mockups, etc. can be found here: http://wiki.xen.org/wiki/New_Xen_Website

Looking forward to hear from you

Best Regards
Lars

--------------070106040103040206070901-- --===============8060068836106055534== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ xen-api mailing list xen-api@lists.xensource.com http://lists.xensource.com/mailman/listinfo/xen-api --===============8060068836106055534==-- From xen-api-bounces@lists.xensource.com Fri Feb 03 14:01:07 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 03 Feb 2012 14:01: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 1RtJhI-00044C-Tu; Fri, 03 Feb 2012 14:01:04 +0000 Received: from mail174.messagelabs.com ([85.158.138.51]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1RlxKT-0005i6-57 for xen-api@lists.xensource.com; Sat, 14 Jan 2012 06:43:05 +0000 X-Env-Sender: thomas@goirand.fr X-Msg-Ref: server-2.tower-174.messagelabs.com!1326523377!9062786!1 X-Originating-IP: [117.121.247.104] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Version: 6.4.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 32277 invoked from network); 14 Jan 2012 06:42:58 -0000 Received: from mx.atlanta.gplhost.com (HELO mx.atlanta.gplhost.com) (117.121.247.104) by server-2.tower-174.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 14 Jan 2012 06:42:58 -0000 Received: from mx.atlanta.gplhost.com (localhost.localdomain [127.0.0.1]) by mx.atlanta.gplhost.com (Postfix) with ESMTP id 108B9FE435; Sat, 14 Jan 2012 06:43:18 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha1; c=simple; d=goirand.fr; h=message-id :date:from:mime-version:to:cc:subject:references:in-reply-to :content-type:content-transfer-encoding; s=postfix; bh=hNRWQhLtF zbLg7dh5jbRdZiXUBU=; b=BDFr4QeMTn76CXIdDy88DQZxBoxhmEwFoBR05HWTi MUaqGgtYOElHpAo7E7ecL4GnhbiVFQWtIDy4oCwnAjhKLh7nIs2AcoH/aP5RZwGg WVSIY1UoUD6kP5qFyLKJCCq066Vd2Ng1kkF6IoHSAP6iaeWOhge6bhguTOZwjZM4 bM= DomainKey-Signature: a=rsa-sha1; c=simple; d=goirand.fr; h=message-id :date:from:mime-version:to:cc:subject:references:in-reply-to :content-type:content-transfer-encoding; q=dns; s=postfix; b=byz OzsivyEXIhF732YkhOoNBw9mw0swHtJDi74/6NN6Wi00nw1U6BKgdMUNV2/8/oBw ey9jC6PS0yNOhaBO5VdP588wAw+arU1GKBjCgCU+RSWlpkbXTmblgXzrbIGvrD71 wzEqXv0M3DXzzWI92KOofDC+cOEE7M91ciLNVQBU= Received: from [127.0.0.1] (atl.apt-proxy.gplhost.com [117.121.247.20]) by mx.atlanta.gplhost.com (Postfix) with ESMTPA id DFA5DFE434; Sat, 14 Jan 2012 06:43:16 +0000 (UTC) Message-ID: <4F1123EE.9080906@goirand.fr> Date: Sat, 14 Jan 2012 14:42:54 +0800 From: Thomas Goirand User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.16) Gecko/20111110 Icedove/3.0.11 MIME-Version: 1.0 To: George Shuklin References: <4F108BFC.6030308@gmail.com> In-Reply-To: <4F108BFC.6030308@gmail.com> X-Enigmail-Version: 1.0.1 X-Mailman-Approved-At: Fri, 03 Feb 2012 14:01:01 +0000 Cc: "xen-api@lists.xensource.com" Subject: Re: [Xen-API] [XCP] [kronos] missed nfs-common dependence X-BeenThere: xen-api@lists.xensource.com X-Mailman-Version: 2.1.13 Precedence: list List-Id: Discussion of API issues surrounding Xen List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-api-bounces@lists.xensource.com Errors-To: xen-api-bounces@lists.xensource.com On 01/14/2012 03:54 AM, George Shuklin wrote: > Good day. > > Package xcp-storage-manager has no dependence on nfs-common. Without > that package very non-intuitive error appear during type=nfs sr creation: > > Error code: SR_BACKEND_FAILURE_72 > Error parameters: , Required NFS server version unsupported > [opterr=rpcinfo failed or timed out: return code 2], > > (and some idea - may be it can be rational to split SM to few packages > - main, with refcounter and so on, and individual packages for every > type? We don't need samba for systems without SMB, we don't need nfs > for systems, who don't use NFS and so on. Making one big package is Hi, There's no absolute needs for NFS. You well may be using Samba instead (which I do, I'm used to setting-up Samba share, I'm less confident with NFS). Adding a new Depends: would *force* everyone to install nfs-common, which isn't something we want to do (NFS isn't strictly needed). In the Debian package which I uploaded to SID, xcp-storage-managers already has a Recommends: lvm2, nfs-common. I think that's really enough. Remember: everything that is in the Recommends section will be installed by default, unless you *manually* decide to not install recommended software, either by using the --no-install-recommends on the apt-get command line, or by adding this as an option in your /etc/apt/apt.conf.d with something like that: APT { Install-Recommends "false"; } So I think everything is fine by default, and that we have nothing to change. Please let me know if you don't agree, and explain why you think I'm wrong here. Best regards, Thomas Goirand (zigo) _______________________________________________ xen-api mailing list xen-api@lists.xensource.com http://lists.xensource.com/mailman/listinfo/xen-api From xen-api-bounces@lists.xensource.com Fri Feb 03 14:01:07 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 03 Feb 2012 14:01: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 1RtJhI-00044C-Tu; Fri, 03 Feb 2012 14:01:04 +0000 Received: from mail174.messagelabs.com ([85.158.138.51]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1RlxKT-0005i6-57 for xen-api@lists.xensource.com; Sat, 14 Jan 2012 06:43:05 +0000 X-Env-Sender: thomas@goirand.fr X-Msg-Ref: server-2.tower-174.messagelabs.com!1326523377!9062786!1 X-Originating-IP: [117.121.247.104] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Version: 6.4.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 32277 invoked from network); 14 Jan 2012 06:42:58 -0000 Received: from mx.atlanta.gplhost.com (HELO mx.atlanta.gplhost.com) (117.121.247.104) by server-2.tower-174.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 14 Jan 2012 06:42:58 -0000 Received: from mx.atlanta.gplhost.com (localhost.localdomain [127.0.0.1]) by mx.atlanta.gplhost.com (Postfix) with ESMTP id 108B9FE435; Sat, 14 Jan 2012 06:43:18 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha1; c=simple; d=goirand.fr; h=message-id :date:from:mime-version:to:cc:subject:references:in-reply-to :content-type:content-transfer-encoding; s=postfix; bh=hNRWQhLtF zbLg7dh5jbRdZiXUBU=; b=BDFr4QeMTn76CXIdDy88DQZxBoxhmEwFoBR05HWTi MUaqGgtYOElHpAo7E7ecL4GnhbiVFQWtIDy4oCwnAjhKLh7nIs2AcoH/aP5RZwGg WVSIY1UoUD6kP5qFyLKJCCq066Vd2Ng1kkF6IoHSAP6iaeWOhge6bhguTOZwjZM4 bM= DomainKey-Signature: a=rsa-sha1; c=simple; d=goirand.fr; h=message-id :date:from:mime-version:to:cc:subject:references:in-reply-to :content-type:content-transfer-encoding; q=dns; s=postfix; b=byz OzsivyEXIhF732YkhOoNBw9mw0swHtJDi74/6NN6Wi00nw1U6BKgdMUNV2/8/oBw ey9jC6PS0yNOhaBO5VdP588wAw+arU1GKBjCgCU+RSWlpkbXTmblgXzrbIGvrD71 wzEqXv0M3DXzzWI92KOofDC+cOEE7M91ciLNVQBU= Received: from [127.0.0.1] (atl.apt-proxy.gplhost.com [117.121.247.20]) by mx.atlanta.gplhost.com (Postfix) with ESMTPA id DFA5DFE434; Sat, 14 Jan 2012 06:43:16 +0000 (UTC) Message-ID: <4F1123EE.9080906@goirand.fr> Date: Sat, 14 Jan 2012 14:42:54 +0800 From: Thomas Goirand User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.16) Gecko/20111110 Icedove/3.0.11 MIME-Version: 1.0 To: George Shuklin References: <4F108BFC.6030308@gmail.com> In-Reply-To: <4F108BFC.6030308@gmail.com> X-Enigmail-Version: 1.0.1 X-Mailman-Approved-At: Fri, 03 Feb 2012 14:01:01 +0000 Cc: "xen-api@lists.xensource.com" Subject: Re: [Xen-API] [XCP] [kronos] missed nfs-common dependence X-BeenThere: xen-api@lists.xensource.com X-Mailman-Version: 2.1.13 Precedence: list List-Id: Discussion of API issues surrounding Xen List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-api-bounces@lists.xensource.com Errors-To: xen-api-bounces@lists.xensource.com On 01/14/2012 03:54 AM, George Shuklin wrote: > Good day. > > Package xcp-storage-manager has no dependence on nfs-common. Without > that package very non-intuitive error appear during type=nfs sr creation: > > Error code: SR_BACKEND_FAILURE_72 > Error parameters: , Required NFS server version unsupported > [opterr=rpcinfo failed or timed out: return code 2], > > (and some idea - may be it can be rational to split SM to few packages > - main, with refcounter and so on, and individual packages for every > type? We don't need samba for systems without SMB, we don't need nfs > for systems, who don't use NFS and so on. Making one big package is Hi, There's no absolute needs for NFS. You well may be using Samba instead (which I do, I'm used to setting-up Samba share, I'm less confident with NFS). Adding a new Depends: would *force* everyone to install nfs-common, which isn't something we want to do (NFS isn't strictly needed). In the Debian package which I uploaded to SID, xcp-storage-managers already has a Recommends: lvm2, nfs-common. I think that's really enough. Remember: everything that is in the Recommends section will be installed by default, unless you *manually* decide to not install recommended software, either by using the --no-install-recommends on the apt-get command line, or by adding this as an option in your /etc/apt/apt.conf.d with something like that: APT { Install-Recommends "false"; } So I think everything is fine by default, and that we have nothing to change. Please let me know if you don't agree, and explain why you think I'm wrong here. Best regards, Thomas Goirand (zigo) _______________________________________________ xen-api mailing list xen-api@lists.xensource.com http://lists.xensource.com/mailman/listinfo/xen-api From xen-api-bounces@lists.xensource.com Fri Feb 03 14:01:07 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 03 Feb 2012 14:01: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 1RtJhI-000442-Q2; Fri, 03 Feb 2012 14:01:04 +0000 Received: from mail21.messagelabs.com ([85.158.143.35]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1RkTxb-0008II-9k for xen-api@lists.xensource.com; Tue, 10 Jan 2012 05:09:23 +0000 X-Env-Sender: thomas@goirand.fr X-Msg-Ref: server-10.tower-21.messagelabs.com!1326172155!7910008!1 X-Originating-IP: [117.121.247.104] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Version: 6.4.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 30405 invoked from network); 10 Jan 2012 05:09:16 -0000 Received: from mx.atlanta.gplhost.com (HELO mx.atlanta.gplhost.com) (117.121.247.104) by server-10.tower-21.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 10 Jan 2012 05:09:16 -0000 Received: from mx.atlanta.gplhost.com (localhost.localdomain [127.0.0.1]) by mx.atlanta.gplhost.com (Postfix) with ESMTP id D869CB4234 for ; Tue, 10 Jan 2012 05:09:19 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha1; c=simple; d=goirand.fr; h=message-id :date:from:mime-version:to:subject:references:in-reply-to :content-type:content-transfer-encoding; s=postfix; bh=kpyrYuH04 jS3R3dNJG12ml0Bq98=; b=xFqNmkfQXSFY4VrtsUKD7ltmlvhqektjnyoZUU6oY Waflba7QsiQsyk+Nk6ZjzCS82SYpMKSn7InJb7nmGaJ2oV3+bFpSnBXeHAZJpnfg 2S5pCbYoYpj1Oo/szAv11ZpC/Cb/yP1vIJt5PQfQ2yU/6zc3+3hCJ1cpaP8utdJr wQ= DomainKey-Signature: a=rsa-sha1; c=simple; d=goirand.fr; h=message-id :date:from:mime-version:to:subject:references:in-reply-to :content-type:content-transfer-encoding; q=dns; s=postfix; b=vqU Fhd58Q7Le14MelHCXSR+g5oibE+BDinKFjt62hyGVSt2On7ocblxWdMIeZsaxQl5 JvLFmylEm2FclICRb7E/lBBzKSC1a+dKjax3Ni12wzwod0cqUOg48QSdDS7GfnFs 7V+AbahO7rG8CpHV55TVYjdpI6fxHa5sC1oVsW6o= Received: from [127.0.0.1] (atl.apt-proxy.gplhost.com [117.121.247.20]) by mx.atlanta.gplhost.com (Postfix) with ESMTPA id 73714B4233 for ; Tue, 10 Jan 2012 05:09:18 +0000 (UTC) Message-ID: <4F0BC7F5.7040204@goirand.fr> Date: Tue, 10 Jan 2012 13:09:09 +0800 From: Thomas Goirand Organization: GPLHost User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.16) Gecko/20111110 Icedove/3.0.11 MIME-Version: 1.0 To: xen-api References: In-Reply-To: X-Enigmail-Version: 1.0.1 X-Mailman-Approved-At: Fri, 03 Feb 2012 14:01:01 +0000 Subject: Re: [Xen-API] Query regarding console of VM X-BeenThere: xen-api@lists.xensource.com X-Mailman-Version: 2.1.13 Precedence: list List-Id: Discussion of API issues surrounding Xen List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-api-bounces@lists.xensource.com Errors-To: xen-api-bounces@lists.xensource.com On 01/09/2012 02:22 AM, Medhavini Buchade wrote: > Hello everyone, > > Thank you to all those who answered my doubts. Your suggestions were > really helpful and now I have completely created a "Debian Lenny VM". Lenny will be end of life in less than a month. You'd better considering not using it anymore. > Although the VM creation is complete and I can see the shell in > "openxenmanager"; I am unable to view the console in "developer xen > api". Whenever I try to see the console of that VM it gives me error > as "load: class com.citrix.xenserver.console.Initialize.class not > found". Have I missed something? Can anyone please guide me through > the steps which will help me to view the console of the VM? > > Thank you very much. > Which version of XCP / XenServer do you use? I was very surprised, after we added the hack so that we can use /etc/xcp/xapi_version_override, to see that the console now works with OpenXenManager running on Kronos (xcp-xapi in Debian SID). :) Thomas _______________________________________________ xen-api mailing list xen-api@lists.xensource.com http://lists.xensource.com/mailman/listinfo/xen-api From xen-api-bounces@lists.xensource.com Fri Feb 03 14:01:07 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 03 Feb 2012 14:01: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 1RtJhI-000442-Q2; Fri, 03 Feb 2012 14:01:04 +0000 Received: from mail21.messagelabs.com ([85.158.143.35]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1RkTxb-0008II-9k for xen-api@lists.xensource.com; Tue, 10 Jan 2012 05:09:23 +0000 X-Env-Sender: thomas@goirand.fr X-Msg-Ref: server-10.tower-21.messagelabs.com!1326172155!7910008!1 X-Originating-IP: [117.121.247.104] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Version: 6.4.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 30405 invoked from network); 10 Jan 2012 05:09:16 -0000 Received: from mx.atlanta.gplhost.com (HELO mx.atlanta.gplhost.com) (117.121.247.104) by server-10.tower-21.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 10 Jan 2012 05:09:16 -0000 Received: from mx.atlanta.gplhost.com (localhost.localdomain [127.0.0.1]) by mx.atlanta.gplhost.com (Postfix) with ESMTP id D869CB4234 for ; Tue, 10 Jan 2012 05:09:19 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha1; c=simple; d=goirand.fr; h=message-id :date:from:mime-version:to:subject:references:in-reply-to :content-type:content-transfer-encoding; s=postfix; bh=kpyrYuH04 jS3R3dNJG12ml0Bq98=; b=xFqNmkfQXSFY4VrtsUKD7ltmlvhqektjnyoZUU6oY Waflba7QsiQsyk+Nk6ZjzCS82SYpMKSn7InJb7nmGaJ2oV3+bFpSnBXeHAZJpnfg 2S5pCbYoYpj1Oo/szAv11ZpC/Cb/yP1vIJt5PQfQ2yU/6zc3+3hCJ1cpaP8utdJr wQ= DomainKey-Signature: a=rsa-sha1; c=simple; d=goirand.fr; h=message-id :date:from:mime-version:to:subject:references:in-reply-to :content-type:content-transfer-encoding; q=dns; s=postfix; b=vqU Fhd58Q7Le14MelHCXSR+g5oibE+BDinKFjt62hyGVSt2On7ocblxWdMIeZsaxQl5 JvLFmylEm2FclICRb7E/lBBzKSC1a+dKjax3Ni12wzwod0cqUOg48QSdDS7GfnFs 7V+AbahO7rG8CpHV55TVYjdpI6fxHa5sC1oVsW6o= Received: from [127.0.0.1] (atl.apt-proxy.gplhost.com [117.121.247.20]) by mx.atlanta.gplhost.com (Postfix) with ESMTPA id 73714B4233 for ; Tue, 10 Jan 2012 05:09:18 +0000 (UTC) Message-ID: <4F0BC7F5.7040204@goirand.fr> Date: Tue, 10 Jan 2012 13:09:09 +0800 From: Thomas Goirand Organization: GPLHost User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.16) Gecko/20111110 Icedove/3.0.11 MIME-Version: 1.0 To: xen-api References: In-Reply-To: X-Enigmail-Version: 1.0.1 X-Mailman-Approved-At: Fri, 03 Feb 2012 14:01:01 +0000 Subject: Re: [Xen-API] Query regarding console of VM X-BeenThere: xen-api@lists.xensource.com X-Mailman-Version: 2.1.13 Precedence: list List-Id: Discussion of API issues surrounding Xen List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-api-bounces@lists.xensource.com Errors-To: xen-api-bounces@lists.xensource.com On 01/09/2012 02:22 AM, Medhavini Buchade wrote: > Hello everyone, > > Thank you to all those who answered my doubts. Your suggestions were > really helpful and now I have completely created a "Debian Lenny VM". Lenny will be end of life in less than a month. You'd better considering not using it anymore. > Although the VM creation is complete and I can see the shell in > "openxenmanager"; I am unable to view the console in "developer xen > api". Whenever I try to see the console of that VM it gives me error > as "load: class com.citrix.xenserver.console.Initialize.class not > found". Have I missed something? Can anyone please guide me through > the steps which will help me to view the console of the VM? > > Thank you very much. > Which version of XCP / XenServer do you use? I was very surprised, after we added the hack so that we can use /etc/xcp/xapi_version_override, to see that the console now works with OpenXenManager running on Kronos (xcp-xapi in Debian SID). :) Thomas _______________________________________________ xen-api mailing list xen-api@lists.xensource.com http://lists.xensource.com/mailman/listinfo/xen-api From xen-api-bounces@lists.xensource.com Fri Feb 03 14:01:08 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 03 Feb 2012 14:01:08 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1RtJhJ-00044h-Bj; Fri, 03 Feb 2012 14:01:05 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Rrn2u-0006DD-SU for xen-api@lists.xensource.com; Mon, 30 Jan 2012 08:57:05 +0000 Received: from [85.158.138.51:44615] by server-9.bemta-3.messagelabs.com id A4/6B-31168-F5B562F4; Mon, 30 Jan 2012 08:57:03 +0000 X-Env-Sender: royger@gmail.com X-Msg-Ref: server-14.tower-174.messagelabs.com!1327913820!10990632!1 X-Originating-IP: [209.85.210.43] X-SpamReason: No, hits=0.3 required=7.0 tests=RCVD_BY_IP X-StarScan-Version: 6.5.5; banners=-,-,- X-VirusChecked: Checked Received: (qmail 6452 invoked from network); 30 Jan 2012 08:57:03 -0000 Received: from mail-pz0-f43.google.com (HELO mail-pz0-f43.google.com) (209.85.210.43) by server-14.tower-174.messagelabs.com with RC4-SHA encrypted SMTP; 30 Jan 2012 08:57:03 -0000 Received: by dajs34 with SMTP id s34so31118514daj.30 for ; Mon, 30 Jan 2012 00:57:00 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=EEthFWJNLun9mkGam7hwSSFwkmM+HZm98/cEo2U4CP0=; b=VhBz+kC30NOCGF+DWiMIpHx7DQL5erBCM9ia48fQJ/3gh1GrqM05DVqSC0eRvhV8sH Ex+1Do4a8TIKlDls0iesPRyUCB3PeWyiOxrQFgODxjBB3nK3pY0VVRSxzTFil/Bb6C0D D06JBPzaZyIL/Xiw6szJzkez6XjteNqPWtHao= MIME-Version: 1.0 Received: by 10.68.219.69 with SMTP id pm5mr40630725pbc.5.1327913820040; Mon, 30 Jan 2012 00:57:00 -0800 (PST) Received: by 10.142.252.8 with HTTP; Mon, 30 Jan 2012 00:56:59 -0800 (PST) In-Reply-To: <4F1473A2.4060103@xen.org> References: <4F1473A2.4060103@xen.org> Date: Mon, 30 Jan 2012 09:56:59 +0100 X-Google-Sender-Auth: _eYPWKktNYrQl8lZ9aXTtRBxK9w Message-ID: From: =?UTF-8?Q?Roger_Pau_Monn=C3=A9?= To: Lars Kurth X-Mailman-Approved-At: Fri, 03 Feb 2012 14:01:01 +0000 Cc: xen-arm@lists.xensource.com, "xen-devel@lists.xensource.com" , "xen-users@lists.xensource.com" , "xen-api@lists.xensource.com" Subject: Re: [Xen-API] [Xen-devel] Xen Document Days for Jan, Feb & March : Looking for input on dates and a couple volunteers X-BeenThere: xen-api@lists.xensource.com X-Mailman-Version: 2.1.13 Precedence: list List-Id: Discussion of API issues surrounding Xen List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-api-bounces@lists.xensource.com Errors-To: xen-api-bounces@lists.xensource.com 2012/1/16 Lars Kurth : > Hi everybody, > > I have been asked when we should hold the next Xen Document Day. Rather than > going through this every single month, I am proposing dates until March. > I.e. > - January 30, 2012 Is this still on? > - Feb 27, 2012 > - March 26, 2012 > Please go to the Xen Document Days etherpad page > (http://openetherpad.org/TSPGIEOBiS) to propose a new date or to vote for a > day. > > I also listed items that could be worked on, on the etherpad page (and > removed stuff which has been done). Feel free to add to it. It is actually > quite incredible how much we (and YOU) did in the last two Xen Document > Days. I wanted to thank everybody who was involved! > > I am also looking for a couple of volunteers (moderators), in particular in > Asia and/or Australia and in the US who commit to being on the #xendocday > IRC channels for a few hours and points other participates to this document > and generally provides advice. If you are interested, please also sign up on > the Xen Document Days etherpad page. > > Best Regards > Lars > > > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xensource.com > http://lists.xensource.com/xen-devel _______________________________________________ xen-api mailing list xen-api@lists.xensource.com http://lists.xensource.com/mailman/listinfo/xen-api From xen-api-bounces@lists.xensource.com Fri Feb 03 14:01:08 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 03 Feb 2012 14:01:08 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1RtJhJ-00044h-Bj; Fri, 03 Feb 2012 14:01:05 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Rrn2u-0006DD-SU for xen-api@lists.xensource.com; Mon, 30 Jan 2012 08:57:05 +0000 Received: from [85.158.138.51:44615] by server-9.bemta-3.messagelabs.com id A4/6B-31168-F5B562F4; Mon, 30 Jan 2012 08:57:03 +0000 X-Env-Sender: royger@gmail.com X-Msg-Ref: server-14.tower-174.messagelabs.com!1327913820!10990632!1 X-Originating-IP: [209.85.210.43] X-SpamReason: No, hits=0.3 required=7.0 tests=RCVD_BY_IP X-StarScan-Version: 6.5.5; banners=-,-,- X-VirusChecked: Checked Received: (qmail 6452 invoked from network); 30 Jan 2012 08:57:03 -0000 Received: from mail-pz0-f43.google.com (HELO mail-pz0-f43.google.com) (209.85.210.43) by server-14.tower-174.messagelabs.com with RC4-SHA encrypted SMTP; 30 Jan 2012 08:57:03 -0000 Received: by dajs34 with SMTP id s34so31118514daj.30 for ; Mon, 30 Jan 2012 00:57:00 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=EEthFWJNLun9mkGam7hwSSFwkmM+HZm98/cEo2U4CP0=; b=VhBz+kC30NOCGF+DWiMIpHx7DQL5erBCM9ia48fQJ/3gh1GrqM05DVqSC0eRvhV8sH Ex+1Do4a8TIKlDls0iesPRyUCB3PeWyiOxrQFgODxjBB3nK3pY0VVRSxzTFil/Bb6C0D D06JBPzaZyIL/Xiw6szJzkez6XjteNqPWtHao= MIME-Version: 1.0 Received: by 10.68.219.69 with SMTP id pm5mr40630725pbc.5.1327913820040; Mon, 30 Jan 2012 00:57:00 -0800 (PST) Received: by 10.142.252.8 with HTTP; Mon, 30 Jan 2012 00:56:59 -0800 (PST) In-Reply-To: <4F1473A2.4060103@xen.org> References: <4F1473A2.4060103@xen.org> Date: Mon, 30 Jan 2012 09:56:59 +0100 X-Google-Sender-Auth: _eYPWKktNYrQl8lZ9aXTtRBxK9w Message-ID: From: =?UTF-8?Q?Roger_Pau_Monn=C3=A9?= To: Lars Kurth X-Mailman-Approved-At: Fri, 03 Feb 2012 14:01:01 +0000 Cc: xen-arm@lists.xensource.com, "xen-devel@lists.xensource.com" , "xen-users@lists.xensource.com" , "xen-api@lists.xensource.com" Subject: Re: [Xen-API] [Xen-devel] Xen Document Days for Jan, Feb & March : Looking for input on dates and a couple volunteers X-BeenThere: xen-api@lists.xensource.com X-Mailman-Version: 2.1.13 Precedence: list List-Id: Discussion of API issues surrounding Xen List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-api-bounces@lists.xensource.com Errors-To: xen-api-bounces@lists.xensource.com 2012/1/16 Lars Kurth : > Hi everybody, > > I have been asked when we should hold the next Xen Document Day. Rather than > going through this every single month, I am proposing dates until March. > I.e. > - January 30, 2012 Is this still on? > - Feb 27, 2012 > - March 26, 2012 > Please go to the Xen Document Days etherpad page > (http://openetherpad.org/TSPGIEOBiS) to propose a new date or to vote for a > day. > > I also listed items that could be worked on, on the etherpad page (and > removed stuff which has been done). Feel free to add to it. It is actually > quite incredible how much we (and YOU) did in the last two Xen Document > Days. I wanted to thank everybody who was involved! > > I am also looking for a couple of volunteers (moderators), in particular in > Asia and/or Australia and in the US who commit to being on the #xendocday > IRC channels for a few hours and points other participates to this document > and generally provides advice. If you are interested, please also sign up on > the Xen Document Days etherpad page. > > Best Regards > Lars > > > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xensource.com > http://lists.xensource.com/xen-devel _______________________________________________ xen-api mailing list xen-api@lists.xensource.com http://lists.xensource.com/mailman/listinfo/xen-api From xen-api-bounces@lists.xensource.com Fri Feb 03 14:01:08 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 03 Feb 2012 14:01:08 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1RtJhJ-00044n-Fl; Fri, 03 Feb 2012 14:01:05 +0000 Received: from mail27.messagelabs.com ([193.109.254.147]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1RrtlJ-0006UQ-TX; Mon, 30 Jan 2012 16:07:22 +0000 X-Env-Sender: florian.heigl@gmail.com X-Msg-Ref: server-9.tower-27.messagelabs.com!1327939595!62300387!1 X-Originating-IP: [209.85.210.171] X-SpamReason: No, hits=0.3 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, RCVD_BY_IP,spamassassin: X-StarScan-Version: 6.5.5; banners=-,-,- X-VirusChecked: Checked Received: (qmail 1313 invoked from network); 30 Jan 2012 16:06:36 -0000 Received: from mail-iy0-f171.google.com (HELO mail-iy0-f171.google.com) (209.85.210.171) by server-9.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 30 Jan 2012 16:06:36 -0000 Received: by iaeh11 with SMTP id h11so38440944iae.30 for ; Mon, 30 Jan 2012 08:07:18 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=a8+w8u3X3eDm9PbeRFjwf+8qU1elBnhqSJCilIwoRao=; b=fo1IQ0XQ8Vwo6zvp1pPiU6K1VIpSbw5cb8m3ikQEAm5sSFpJLd3m4BuhfYWx6t7C4k wasE45C2Y6alGFZIKagWBOgMX41eyEGGIX6LeV53B7AkQeBWxecgBeY1r0x9oWjj3tUb xCtQXE2FfuUDuHc6UOxsQq8Kuq+A7O4UAEqHo= MIME-Version: 1.0 Received: by 10.42.145.132 with SMTP id f4mr14543icv.42.1327939638766; Mon, 30 Jan 2012 08:07:18 -0800 (PST) Received: by 10.231.8.37 with HTTP; Mon, 30 Jan 2012 08:07:18 -0800 (PST) In-Reply-To: <4F2666DC.7080601@xen.org> References: <4F1473A2.4060103@xen.org> <4F2666DC.7080601@xen.org> Date: Mon, 30 Jan 2012 17:07:18 +0100 Message-ID: From: Florian Heigl To: Lars Kurth X-Mailman-Approved-At: Fri, 03 Feb 2012 14:01:01 +0000 Cc: =?ISO-8859-1?Q?Roger_Pau_Monn=E9?= , xen-arm@lists.xensource.com, "xen-devel@lists.xensource.com" , "xen-users@lists.xensource.com" , "xen-api@lists.xensource.com" Subject: Re: [Xen-API] [Xen-users] [Xen-devel] Xen Document Days for Jan, Feb & March : Looking for input on dates and a couple volunteers X-BeenThere: xen-api@lists.xensource.com X-Mailman-Version: 2.1.13 Precedence: list List-Id: Discussion of API issues surrounding Xen List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Sender: xen-api-bounces@lists.xensource.com Errors-To: xen-api-bounces@lists.xensource.com Hi all, 2012/1/30 Lars Kurth : > On 30/01/2012 08:56, Roger Pau Monn=E9 wrote: >>> I have been asked when we should hold the next Xen Document Day. Rather >>> than >>> going through this every single month, I am proposing dates until March. >>> I.e. >>> - January 30, 2012 >> >> Is this still on? >> > I didn't get any feedback. Going forward, I think we should always hold :(( > these on the last Monday of the month, starting from Feb. Would it be possible to insert (i.e. quarterly) an extra doc day that is on a bank holiday or weekend for us with dayjobs? Of course it won't be fun if it's just me, but there got to be some more people interested!!! Florian -- = the purpose of libvirt is to provide an abstraction layer hiding all xen features added since 2006 until they were finally understood and copied by the kvm devs. _______________________________________________ xen-api mailing list xen-api@lists.xensource.com http://lists.xensource.com/mailman/listinfo/xen-api From xen-api-bounces@lists.xensource.com Fri Feb 03 14:01:08 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 03 Feb 2012 14:01:08 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1RtJhJ-00044n-Fl; Fri, 03 Feb 2012 14:01:05 +0000 Received: from mail27.messagelabs.com ([193.109.254.147]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1RrtlJ-0006UQ-TX; Mon, 30 Jan 2012 16:07:22 +0000 X-Env-Sender: florian.heigl@gmail.com X-Msg-Ref: server-9.tower-27.messagelabs.com!1327939595!62300387!1 X-Originating-IP: [209.85.210.171] X-SpamReason: No, hits=0.3 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, RCVD_BY_IP,spamassassin: X-StarScan-Version: 6.5.5; banners=-,-,- X-VirusChecked: Checked Received: (qmail 1313 invoked from network); 30 Jan 2012 16:06:36 -0000 Received: from mail-iy0-f171.google.com (HELO mail-iy0-f171.google.com) (209.85.210.171) by server-9.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 30 Jan 2012 16:06:36 -0000 Received: by iaeh11 with SMTP id h11so38440944iae.30 for ; Mon, 30 Jan 2012 08:07:18 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=a8+w8u3X3eDm9PbeRFjwf+8qU1elBnhqSJCilIwoRao=; b=fo1IQ0XQ8Vwo6zvp1pPiU6K1VIpSbw5cb8m3ikQEAm5sSFpJLd3m4BuhfYWx6t7C4k wasE45C2Y6alGFZIKagWBOgMX41eyEGGIX6LeV53B7AkQeBWxecgBeY1r0x9oWjj3tUb xCtQXE2FfuUDuHc6UOxsQq8Kuq+A7O4UAEqHo= MIME-Version: 1.0 Received: by 10.42.145.132 with SMTP id f4mr14543icv.42.1327939638766; Mon, 30 Jan 2012 08:07:18 -0800 (PST) Received: by 10.231.8.37 with HTTP; Mon, 30 Jan 2012 08:07:18 -0800 (PST) In-Reply-To: <4F2666DC.7080601@xen.org> References: <4F1473A2.4060103@xen.org> <4F2666DC.7080601@xen.org> Date: Mon, 30 Jan 2012 17:07:18 +0100 Message-ID: From: Florian Heigl To: Lars Kurth X-Mailman-Approved-At: Fri, 03 Feb 2012 14:01:01 +0000 Cc: =?ISO-8859-1?Q?Roger_Pau_Monn=E9?= , xen-arm@lists.xensource.com, "xen-devel@lists.xensource.com" , "xen-users@lists.xensource.com" , "xen-api@lists.xensource.com" Subject: Re: [Xen-API] [Xen-users] [Xen-devel] Xen Document Days for Jan, Feb & March : Looking for input on dates and a couple volunteers X-BeenThere: xen-api@lists.xensource.com X-Mailman-Version: 2.1.13 Precedence: list List-Id: Discussion of API issues surrounding Xen List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Sender: xen-api-bounces@lists.xensource.com Errors-To: xen-api-bounces@lists.xensource.com Hi all, 2012/1/30 Lars Kurth : > On 30/01/2012 08:56, Roger Pau Monn=E9 wrote: >>> I have been asked when we should hold the next Xen Document Day. Rather >>> than >>> going through this every single month, I am proposing dates until March. >>> I.e. >>> - January 30, 2012 >> >> Is this still on? >> > I didn't get any feedback. Going forward, I think we should always hold :(( > these on the last Monday of the month, starting from Feb. Would it be possible to insert (i.e. quarterly) an extra doc day that is on a bank holiday or weekend for us with dayjobs? Of course it won't be fun if it's just me, but there got to be some more people interested!!! Florian -- = the purpose of libvirt is to provide an abstraction layer hiding all xen features added since 2006 until they were finally understood and copied by the kvm devs. _______________________________________________ xen-api mailing list xen-api@lists.xensource.com http://lists.xensource.com/mailman/listinfo/xen-api From xen-api-bounces@lists.xensource.com Fri Feb 03 14:01:08 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 03 Feb 2012 14:01:08 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1RtJhI-00043t-LL; Fri, 03 Feb 2012 14:01:04 +0000 Received: from mail27.messagelabs.com ([193.109.254.147]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1RiU4r-0001F4-FW for xen-api@lists.xensource.com; Wed, 04 Jan 2012 16:52:37 +0000 X-Env-Sender: thomas@goirand.fr X-Msg-Ref: server-10.tower-27.messagelabs.com!1325695911!49020401!1 X-Originating-IP: [117.121.247.104] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Version: 6.4.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 22428 invoked from network); 4 Jan 2012 16:51:52 -0000 Received: from mx.atlanta.gplhost.com (HELO mx.atlanta.gplhost.com) (117.121.247.104) by server-10.tower-27.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 4 Jan 2012 16:51:52 -0000 Received: from mx.atlanta.gplhost.com (localhost.localdomain [127.0.0.1]) by mx.atlanta.gplhost.com (Postfix) with ESMTP id 68ECDFE4BF for ; Wed, 4 Jan 2012 16:52:35 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha1; c=simple; d=goirand.fr; h=message-id :date:from:mime-version:to:subject:references:in-reply-to :content-type:content-transfer-encoding; s=postfix; bh=B23DXTLT6 szJf8cdPi4g3In5HRs=; b=lFRIr7RcTqiPnlJdcjXszB1f0QYSueolO4BU4ubhC t541C+mThhdmekK7rvVtIVAKfn0CHdCC0S4wXU4UvI4Li45LWIC5IGY0TW83dsOg Syl2a1tcGlVKAr/BJVHnykRk1PN/mC/F6usFvldlAz/dTnHJWjUg9JZOOkDLGSe/ GI= DomainKey-Signature: a=rsa-sha1; c=simple; d=goirand.fr; h=message-id :date:from:mime-version:to:subject:references:in-reply-to :content-type:content-transfer-encoding; q=dns; s=postfix; b=Q5W 12QPbYFrwg83QuPM0npw6in+WUQyXlnOfPxIrRSkbvtcJ1WFNyA9yyAo/crSTYSP 1IW1dkgX/Yf9Up4e77ErCFjwF50GTd9PcAV9FeBwj3FwAe3M3UbJdsoS084gCwlU QpzlRFVYV5C7bqD8iXxdO7AMd7BrzzbUa0nqQVN4= Received: from [127.0.0.1] (atl.apt-proxy.gplhost.com [117.121.247.20]) by mx.atlanta.gplhost.com (Postfix) with ESMTPA id 6B945FE142 for ; Wed, 4 Jan 2012 16:52:33 +0000 (UTC) Message-ID: <4F0483CF.50705@goirand.fr> Date: Thu, 05 Jan 2012 00:52:31 +0800 From: Thomas Goirand Organization: GPLHost User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.16) Gecko/20111110 Icedove/3.0.11 MIME-Version: 1.0 To: "xen-api@lists.xensource.com" References: <4F0397BD.60703@selectel.ru> In-Reply-To: <4F0397BD.60703@selectel.ru> X-Enigmail-Version: 1.0.1 X-Mailman-Approved-At: Fri, 03 Feb 2012 14:01:01 +0000 Subject: Re: [Xen-API] [kronos] [XCP] [BUG] wrong paths in xcp-xapi init.d script X-BeenThere: xen-api@lists.xensource.com X-Mailman-Version: 2.1.13 Precedence: list List-Id: Discussion of API issues surrounding Xen List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-api-bounces@lists.xensource.com Errors-To: xen-api-bounces@lists.xensource.com On 01/04/2012 08:05 AM, George Shuklin wrote: > Solution: > > Fix path to correct one. > > --- /tmp/etc/init.d/xcp-xapi 2011-12-12 15:41:13.000000000 +0400 > +++ /etc/init.d/xcp-xapi 2012-01-04 04:03:49.326368996 +0400 > @@ -95,8 +95,8 @@ > # Check whether the md5 of the create-templates binary matches > the one > # used previously. If not, recreate the templates. > if ! md5sum -c --status $TEMPLATES_MD5_STAMP ; then > - /usr/lib/xcp/lib/regenerate-templates start > - md5sum /usr/lib/xcp/lib/create_templates > $TEMPLATES_MD5_STAMP > + /usr/lib/xen-common/xapi/libexec/regenerate-templates start > + md5sum /usr/lib/xen-common/xapi/libexec/create_templates > >$TEMPLATES_MD5_STAMP > fi > } This has already been fixed in the Git (and in Debian), and the solution was to package regenerate-templates / create_templates in /usr/lib/xcp/lib rather than changing the init.d script. Cheers, Thomas _______________________________________________ xen-api mailing list xen-api@lists.xensource.com http://lists.xensource.com/mailman/listinfo/xen-api From xen-api-bounces@lists.xensource.com Fri Feb 03 14:01:08 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 03 Feb 2012 14:01:08 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1RtJhI-00043t-LL; Fri, 03 Feb 2012 14:01:04 +0000 Received: from mail27.messagelabs.com ([193.109.254.147]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1RiU4r-0001F4-FW for xen-api@lists.xensource.com; Wed, 04 Jan 2012 16:52:37 +0000 X-Env-Sender: thomas@goirand.fr X-Msg-Ref: server-10.tower-27.messagelabs.com!1325695911!49020401!1 X-Originating-IP: [117.121.247.104] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Version: 6.4.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 22428 invoked from network); 4 Jan 2012 16:51:52 -0000 Received: from mx.atlanta.gplhost.com (HELO mx.atlanta.gplhost.com) (117.121.247.104) by server-10.tower-27.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 4 Jan 2012 16:51:52 -0000 Received: from mx.atlanta.gplhost.com (localhost.localdomain [127.0.0.1]) by mx.atlanta.gplhost.com (Postfix) with ESMTP id 68ECDFE4BF for ; Wed, 4 Jan 2012 16:52:35 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha1; c=simple; d=goirand.fr; h=message-id :date:from:mime-version:to:subject:references:in-reply-to :content-type:content-transfer-encoding; s=postfix; bh=B23DXTLT6 szJf8cdPi4g3In5HRs=; b=lFRIr7RcTqiPnlJdcjXszB1f0QYSueolO4BU4ubhC t541C+mThhdmekK7rvVtIVAKfn0CHdCC0S4wXU4UvI4Li45LWIC5IGY0TW83dsOg Syl2a1tcGlVKAr/BJVHnykRk1PN/mC/F6usFvldlAz/dTnHJWjUg9JZOOkDLGSe/ GI= DomainKey-Signature: a=rsa-sha1; c=simple; d=goirand.fr; h=message-id :date:from:mime-version:to:subject:references:in-reply-to :content-type:content-transfer-encoding; q=dns; s=postfix; b=Q5W 12QPbYFrwg83QuPM0npw6in+WUQyXlnOfPxIrRSkbvtcJ1WFNyA9yyAo/crSTYSP 1IW1dkgX/Yf9Up4e77ErCFjwF50GTd9PcAV9FeBwj3FwAe3M3UbJdsoS084gCwlU QpzlRFVYV5C7bqD8iXxdO7AMd7BrzzbUa0nqQVN4= Received: from [127.0.0.1] (atl.apt-proxy.gplhost.com [117.121.247.20]) by mx.atlanta.gplhost.com (Postfix) with ESMTPA id 6B945FE142 for ; Wed, 4 Jan 2012 16:52:33 +0000 (UTC) Message-ID: <4F0483CF.50705@goirand.fr> Date: Thu, 05 Jan 2012 00:52:31 +0800 From: Thomas Goirand Organization: GPLHost User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.16) Gecko/20111110 Icedove/3.0.11 MIME-Version: 1.0 To: "xen-api@lists.xensource.com" References: <4F0397BD.60703@selectel.ru> In-Reply-To: <4F0397BD.60703@selectel.ru> X-Enigmail-Version: 1.0.1 X-Mailman-Approved-At: Fri, 03 Feb 2012 14:01:01 +0000 Subject: Re: [Xen-API] [kronos] [XCP] [BUG] wrong paths in xcp-xapi init.d script X-BeenThere: xen-api@lists.xensource.com X-Mailman-Version: 2.1.13 Precedence: list List-Id: Discussion of API issues surrounding Xen List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-api-bounces@lists.xensource.com Errors-To: xen-api-bounces@lists.xensource.com On 01/04/2012 08:05 AM, George Shuklin wrote: > Solution: > > Fix path to correct one. > > --- /tmp/etc/init.d/xcp-xapi 2011-12-12 15:41:13.000000000 +0400 > +++ /etc/init.d/xcp-xapi 2012-01-04 04:03:49.326368996 +0400 > @@ -95,8 +95,8 @@ > # Check whether the md5 of the create-templates binary matches > the one > # used previously. If not, recreate the templates. > if ! md5sum -c --status $TEMPLATES_MD5_STAMP ; then > - /usr/lib/xcp/lib/regenerate-templates start > - md5sum /usr/lib/xcp/lib/create_templates > $TEMPLATES_MD5_STAMP > + /usr/lib/xen-common/xapi/libexec/regenerate-templates start > + md5sum /usr/lib/xen-common/xapi/libexec/create_templates > >$TEMPLATES_MD5_STAMP > fi > } This has already been fixed in the Git (and in Debian), and the solution was to package regenerate-templates / create_templates in /usr/lib/xcp/lib rather than changing the init.d script. Cheers, Thomas _______________________________________________ xen-api mailing list xen-api@lists.xensource.com http://lists.xensource.com/mailman/listinfo/xen-api From xen-api-bounces@lists.xensource.com Fri Feb 03 14:01:08 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 03 Feb 2012 14:01:08 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1RtJhI-00043n-HA; Fri, 03 Feb 2012 14:01:04 +0000 Received: from mail21.messagelabs.com ([85.158.143.35]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Ri8Xg-0000lM-0I; Tue, 03 Jan 2012 17:52:56 +0000 X-Env-Sender: darnok@68k.org X-Msg-Ref: server-8.tower-21.messagelabs.com!1325613165!10356503!1 X-Originating-IP: [206.212.254.10] X-SpamReason: No, hits=0.5 required=7.0 tests=BODY_RANDOM_LONG X-StarScan-Version: 6.4.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 6538 invoked from network); 3 Jan 2012 17:52:47 -0000 Received: from andromeda.dapyr.net (HELO andromeda.dapyr.net) (206.212.254.10) by server-8.tower-21.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 3 Jan 2012 17:52:47 -0000 Received: from andromeda.dapyr.net (darnok@localhost [127.0.0.1]) by andromeda.dapyr.net (8.13.4/8.13.4/Debian-3sarge3) with ESMTP id q03HqhYQ005729 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 3 Jan 2012 12:52:43 -0500 Received: (from darnok@localhost) by andromeda.dapyr.net (8.13.4/8.13.4/Submit) id q03Hqh5S005727; Tue, 3 Jan 2012 12:52:43 -0500 Date: Tue, 3 Jan 2012 13:52:43 -0400 From: Konrad Rzeszutek Wilk To: R J Message-ID: <20120103175243.GE749@andromeda.dapyr.net> References: Mime-Version: 1.0 Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.9i X-Mailman-Approved-At: Fri, 03 Feb 2012 14:01:01 +0000 Cc: xen-devel@lists.xensource.com, xen-users@lists.xensource.com, xen-api@lists.xensource.com Subject: Re: [Xen-API] [Xen-devel] BalloonWorkerThread issue X-BeenThere: xen-api@lists.xensource.com X-Mailman-Version: 2.1.13 Precedence: list List-Id: Discussion of API issues surrounding Xen List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-api-bounces@lists.xensource.com Errors-To: xen-api-bounces@lists.xensource.com On Thu, Dec 29, 2011 at 11:28:59PM +0530, R J wrote: > Hello List, > > Merry Christmas to all !! > > Basically I'm trying to boot a Windows 2008R2 DC HVM with 90GB static max > memory and 32GB static min. > > The node config is Dell M610 with X5660 and 96GB RAM and its running XCP 1.1 > > Many times the node crashes while booting HVM. Sometimes I get success. Node? Meaning dom0? Or the guest? Are you using dom0_mem=max:X argument? > I have attached the HVM boot log of successful start. Many times the node > hangs as soon as the BalloonWorkerThread is activated. Which PV driver is this? Is this with the other ones: GPL one, Citrix, Novell, and Oracle as well? > > In attached txt the ballon inflation rate is constant 4090 > *XENUTIL: BalloonWorkerThread: inflated balloon by 4090 page(s) in 7924ms > (2064k/s) * > > till the time it starts, the inflation rate shoots to 12554884 and the VM > is live. > *XENUTIL: BalloonWorkerThread: inflated balloon by 12554884 page(s) in > 32604ms (91243k/s) * > *XENUTIL: BalloonWorkerThread: de-activating * > *XENUTIL: XenevtchnMapResources setting callback irq to 11 * > > > Can some one help me understand the *BalloonWorkerThread *behavior ?* > > > *Many thanks, > Rushi > Dec 29 23:08:01 n4 xenguest: Determined the following parameters from xenstore: > Dec 29 23:08:01 n4 xenguest: vcpu/number:16 vcpu/weight:0 vcpu/cap:0 nx: 1 viridian: 1 apic: 1 acpi: 1 pae: 1 acpi_s4: 0 acpi_s3: 0 > Dec 29 23:08:01 n4 xenguest: vcpu/0/affinity:0 > Dec 29 23:08:01 n4 xenguest: vcpu/1/affinity:0 > Dec 29 23:08:01 n4 xenguest: vcpu/2/affinity:0 > Dec 29 23:08:01 n4 xenguest: vcpu/3/affinity:0 > Dec 29 23:08:01 n4 xenguest: vcpu/4/affinity:0 > Dec 29 23:08:01 n4 xenguest: vcpu/5/affinity:0 > Dec 29 23:08:01 n4 xenguest: vcpu/6/affinity:0 > Dec 29 23:08:01 n4 xenguest: vcpu/7/affinity:0 > Dec 29 23:08:01 n4 xenguest: vcpu/8/affinity:0 > Dec 29 23:08:01 n4 xenguest: vcpu/9/affinity:0 > Dec 29 23:08:01 n4 xenguest: vcpu/10/affinity:0 > Dec 29 23:08:01 n4 xenguest: vcpu/11/affinity:0 > Dec 29 23:08:01 n4 xenguest: vcpu/12/affinity:0 > Dec 29 23:08:01 n4 xenguest: vcpu/13/affinity:0 > Dec 29 23:08:01 n4 xenguest: vcpu/14/affinity:0 > Dec 29 23:08:01 n4 xenguest: vcpu/15/affinity:0 > Dec 29 23:08:14 n4 tapdisk[18204]: tapdisk-control: init, 10 x 4k buffers > Dec 29 23:08:14 n4 tapdisk[18204]: I/O queue driver: lio > Dec 29 23:08:14 n4 tapdisk[18204]: tapdisk-log: started, level 0 > Dec 29 23:08:14 n4 tapdisk[18204]: received 'attach' message (uuid = 0) > Dec 29 23:08:14 n4 tapdisk[18204]: sending 'attach response' message (uuid = 0) > Dec 29 23:08:14 n4 tapdisk[18204]: received 'open' message (uuid = 0) > Dec 29 23:08:14 n4 tapdisk[18204]: Loading driver 'vhd' for vbd 0 /dev/VG_XenStorage-49740841-8056-06e2-373b-ec72084f6fb0/VHD-62c5a501-d662-4d38-a75c-a280e2929297 0x00000000 > Dec 29 23:08:14 n4 tapdisk[18204]: /dev/VG_XenStorage-49740841-8056-06e2-373b-ec72084f6fb0/VHD-62c5a501-d662-4d38-a75c-a280e2929297 version: tap 0x00010003, b: 15360, a: 307, f: 26, n: 1268376 > Dec 29 23:08:14 n4 tapdisk[18204]: opened image /dev/VG_XenStorage-49740841-8056-06e2-373b-ec72084f6fb0/VHD-62c5a501-d662-4d38-a75c-a280e2929297 (1 users, state: 0x00000001, type: 4) > Dec 29 23:08:14 n4 tapdisk[18204]: /dev/mapper/VG_XenStorage--49740841--8056--06e2--373b--ec72084f6fb0-VHD--8eae906c--8f44--4618--a850--3aaa5293408b version: tap 0x00010003, b: 15360, a: 3331, f: 3307, n: 0 > Dec 29 23:08:14 n4 tapdisk[18204]: opened image /dev/mapper/VG_XenStorage--49740841--8056--06e2--373b--ec72084f6fb0-VHD--8eae906c--8f44--4618--a850--3aaa5293408b (1 users, state: 0x00000003, type: 4) > Dec 29 23:08:14 n4 tapdisk[18204]: VBD CHAIN: > Dec 29 23:08:14 n4 tapdisk[18204]: /dev/VG_XenStorage-49740841-8056-06e2-373b-ec72084f6fb0/VHD-62c5a501-d662-4d38-a75c-a280e2929297: type:vhd(4) storage:lvm(3) > Dec 29 23:08:14 n4 tapdisk[18204]: /dev/mapper/VG_XenStorage--49740841--8056--06e2--373b--ec72084f6fb0-VHD--8eae906c--8f44--4618--a850--3aaa5293408b: type:vhd(4) storage:lvm(3) > Dec 29 23:08:14 n4 tapdisk[18204]: sending 'open response' message (uuid = 0) > Dec 29 23:08:14 n4 vbd.uevent[add](backend/vbd/18/768): wrote /xapi/18/hotplug/vbd/768/hotplug = 'online' > Dec 29 23:08:15 n4 vbd.uevent[add](backend/vbd/18/5696): wrote /xapi/18/hotplug/vbd/5696/hotplug = 'online' > Dec 29 23:08:15 n4 ovs-vsctl: 00001|vsctl|INFO|Called as /usr/bin/ovs-vsctl list-ports xapi9 > Dec 29 23:08:15 n4 ovs-vsctl: 00001|vsctl|INFO|Called as /usr/bin/ovs-vsctl --timeout=30 -- --if-exists del-port vif18.0 -- add-port xapi9 vif18.0 -- set interface vif18.0 "external-ids:\"xs-vm-uuid\"=\"6591a403-0eba-30b4-96a6-e02a7db0607a\"" -- set interface vif18.0 "external-ids:\"xs-vif-uuid\"=\"3be54e6d-6d13-b04b-6735-24831e5169e5\"" -- set interface vif18.0 "external-ids:\"xs-network-uuid\"=\"7051ef99-4fcb-fa61-a10e-f98456e12e90\"" -- set interface vif18.0 "external-ids:\"attached-mac\"=\"d6:6d:60:7e:45:52\"" > Dec 29 23:08:15 n4 qemu.18: domid: 18 > Dec 29 23:08:15 n4 qemu.18: qemu: the number of cpus is 16 > Dec 29 23:08:15 n4 qemu.18: -videoram option does not work with cirrus vga device model. Videoram set to 4M. > Dec 29 23:08:15 n4 HVM18[18302]: Guest uuid = 6591a403-0eba-30b4-96a6-e02a7db0607a > Dec 29 23:08:15 n4 HVM18[18302]: Watching /local/domain/18/logdirty/next-active > Dec 29 23:08:15 n4 HVM18[18302]: Watching /local/domain/0/device-model/18/command > Dec 29 23:08:15 n4 HVM18[18302]: char device redirected to /dev/pts/2 > Dec 29 23:08:15 n4 HVM18[18302]: char device redirected to /dev/pts/3 > Dec 29 23:08:15 n4 HVM18[18302]: qemu_map_cache_init nr_buckets = 4000 size 327680 > Dec 29 23:08:15 n4 HVM18[18302]: shared page at pfn feffd > Dec 29 23:08:15 n4 HVM18[18302]: buffered io page at pfn feffb > Dec 29 23:08:15 n4 HVM18[18302]: Time offset set 0 > Dec 29 23:08:15 n4 HVM18[18302]: pci_register_device: 00:00:00 (i440FX) > Dec 29 23:08:15 n4 HVM18[18302]: pci_register_device: 00:01:00 (PIIX3) > Dec 29 23:08:15 n4 HVM18[18302]: pci_register_device: 00:02:00 (Cirrus VGA) > Dec 29 23:08:15 n4 HVM18[18302]: populating video RAM at ff000000 > Dec 29 23:08:15 n4 HVM18[18302]: mapping video RAM from ff000000 > Dec 29 23:08:15 n4 HVM18[18302]: pci_register_device: 00:03:00 (xen-platform) > Dec 29 23:08:15 n4 HVM18[18302]: xs_read(/vm/6591a403-0eba-30b4-96a6-e02a7db0607a/log-throttling): read error > Dec 29 23:08:15 n4 HVM18[18302]: ROM memory area now RW > Dec 29 23:08:15 n4 HVM18[18302]: pci_register_device: 00:04:00 (RTL8139) > Dec 29 23:08:15 n4 HVM18[18302]: pci_register_device: 00:01:01 (PIIX3 IDE) > Dec 29 23:08:15 n4 HVM18[18302]: pci_register_device: 00:01:02 (USB-UHCI) > Dec 29 23:08:15 n4 HVM18[18302]: pci_register_device: 00:01:03 (PIIX4 ACPI) > Dec 29 23:08:15 n4 HVM18[18302]: xs_read(/local/domain/0/device-model/18/xen_extended_power_mgmt): read error > Dec 29 23:08:15 n4 HVM18[18302]: releasing VM > Dec 29 23:08:15 n4 HVM18[18302]: xs_read(): vncpasswd get error. /vm/6591a403-0eba-30b4-96a6-e02a7db0607a/vncpasswd. > Dec 29 23:08:15 n4 HVM18[18302]: I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 > Dec 29 17:38:15 n4 last message repeated 2 times > Dec 29 17:38:15 n4 HVM18[18302]: Triggered log-dirty buffer switch > Dec 29 17:38:15 n4 HVM18[18302]: I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 > Dec 29 17:38:15 n4 HVM18[18302]: medium change watch on `hdd' (index: 1): > Dec 29 17:38:15 n4 HVM18[18302]: I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 > Dec 29 17:38:15 n4 last message repeated 11 times > Dec 29 17:38:16 n4 HVM18[18302]: cirrus vga map change while on lfb mode > Dec 29 23:08:16 n4 ovs-vsctl: 00001|vsctl|INFO|Called as /usr/bin/ovs-vsctl --timeout=30 -- --if-exists del-port tap18.0 -- add-port xapi9 tap18.0 > Dec 29 17:38:16 n4 HVM18[18302]: mapping vram to f0000000 - f0400000 > Dec 29 17:38:17 n4 HVM18[18302]: ROM memory area now RW > Dec 29 17:38:17 n4 HVM18[18302]: ROM memory area now RO > Dec 29 17:38:18 n4 HVM18[18302]: cirrus: blanking the screen line_offset=3072 height=768 > Dec 29 17:38:34 n4 HVM18[18302]: cirrus: blanking the screen line_offset=1024 height=768 > Dec 29 17:38:37 n4 HVM18[18302]: UNPLUG: protocol version set to 1 (drivers not blacklisted) > Dec 29 17:38:37 n4 HVM18[18302]: UNPLUG: protocol 1 active > Dec 29 17:38:37 n4 HVM18[18302]: UNPLUG: product_id: 1 build_number: 30876 > Dec 29 17:38:37 n4 HVM18[18302]: UNPLUG: drivers not blacklisted > Dec 29 17:38:37 n4 HVM18[18302]: ide_unplug_harddisk: drive 0 > Dec 29 17:38:37 n4 HVM18[18302]: pci_dev_unplug: 00:04:00 > Dec 29 17:38:37 n4 HVM18[18302]: net_tap_shutdown: model=tap,name=tap.0 > Dec 29 23:08:38 n4 ovs-vsctl: 00001|vsctl|INFO|Called as /usr/bin/ovs-vsctl --timeout=30 -- --if-exists del-port tap18.0 > Dec 29 17:38:38 n4 HVM18[18302]: XEVTCHN: InstallDumpDeviceCallback: version mismatch (255 != 1) > Dec 29 17:38:38 n4 HVM18[18302]: XEVTCHN: XenevtchnAddDevice: FDO = 0xFFFFFA8044323970 > Dec 29 17:38:38 n4 HVM18[18302]: XEVTCHN: Initialized tracing provider > Dec 29 17:38:38 n4 HVM18[18302]: XEVTCHN: StartDeviceFdo: ====> > Dec 29 17:38:38 n4 HVM18[18302]: XENUTIL: XEVTCHN: IO hole: [00000000fbfa6000,00000000fc000000) mapped at FFFFF88002965000 > Dec 29 17:38:38 n4 HVM18[18302]: net_tap_shutdown: model=tap,name=tap.0 > Dec 29 17:38:38 n4 HVM18[18302]: XENUTIL: KERNEL: 6.1 (build 7600) platform WIN32_NT > Dec 29 17:38:38 n4 HVM18[18302]: XENUTIL: SP: NONE > Dec 29 17:38:38 n4 HVM18[18302]: XENUTIL: SUITES: > Dec 29 17:38:38 n4 HVM18[18302]: XENUTIL: - TERMINAL > Dec 29 17:38:38 n4 HVM18[18302]: XENUTIL: - DATACENTER > Dec 29 17:38:38 n4 HVM18[18302]: XENUTIL: - SINGLEUSERTS > Dec 29 17:38:38 n4 HVM18[18302]: XENUTIL: TYPE: SERVER > Dec 29 17:38:38 n4 HVM18[18302]: XENUTIL: PV DRIVERS: VERSION: 5.6.0 BUILD: 30876 (Apr 30 2010.06:57:01) > Dec 29 17:38:38 n4 HVM18[18302]: XENUTIL: 64-bit HVM > Dec 29 17:38:38 n4 HVM18[18302]: net_tap_shutdown: model=tap,name=tap.0 > Dec 29 17:38:38 n4 HVM18[18302]: XENUTIL: ExpandGrantTable: GRANT TABLE 0: (0 - 511) at FFFFF88002966000 (fbfa7000) > Dec 29 17:38:38 n4 HVM18[18302]: XENUTIL: XenEnterprise product string is present > Dec 29 17:38:39 n4 HVM18[18302]: XENUTIL: PHYSICAL MEMORY: TOP = 00000016.8fc00000 > Dec 29 17:38:39 n4 HVM18[18302]: XENUTIL: BalloonTargetChanged: 94371840k -> 43792384k > Dec 29 17:38:39 n4 HVM18[18302]: XENUTIL: BalloonWorkerThread: activating > Dec 29 17:38:47 n4 HVM18[18302]: XENUTIL: WARNING: BalloonReleasePfnArray: ran for more than 2230ms > Dec 29 17:38:47 n4 HVM18[18302]: XENUTIL: BalloonWorkerThread: inflated balloon by 4090 page(s) in 7924ms (2064k/s) > Dec 29 17:38:47 n4 HVM18[18302]: XENUTIL: BalloonWorkerThread: pausing for 1s (target = 43792384k, current = 94355480k) > Dec 29 17:38:57 n4 HVM18[18302]: XENUTIL: WARNING: BalloonReleasePfnArray: ran for more than 1794ms > Dec 29 17:38:57 n4 HVM18[18302]: XENUTIL: BalloonWorkerThread: inflated balloon by 4090 page(s) in 9157ms (1786k/s) > Dec 29 17:38:57 n4 HVM18[18302]: XENUTIL: BalloonWorkerThread: pausing for 1s (target = 43792384k, current = 94339120k) > Dec 29 17:39:13 n4 HVM18[18302]: XENUTIL: WARNING: BalloonReleasePfnArray: ran for more than 5070ms > Dec 29 17:39:13 n4 HVM18[18302]: XENUTIL: BalloonWorkerThread: inflated balloon by 4090 page(s) in 14601ms (1120k/s) > Dec 29 17:39:13 n4 HVM18[18302]: XENUTIL: BalloonWorkerThread: pausing for 1s (target = 43792384k, current = 94322760k) > Dec 29 17:39:30 n4 HVM18[18302]: XENUTIL: WARNING: BalloonReleasePfnArray: ran for more than 4321ms > Dec 29 17:39:30 n4 HVM18[18302]: XENUTIL: BalloonWorkerThread: inflated balloon by 4090 page(s) in 16052ms (1019k/s) > Dec 29 17:39:30 n4 HVM18[18302]: XENUTIL: BalloonWorkerThread: pausing for 1s (target = 43792384k, current = 94306400k) > Dec 29 17:39:40 n4 HVM18[18302]: XENUTIL: WARNING: BalloonPodSweep: HYPERVISOR_memory_op(XENMEM_pod_sweep, ...) failed (fffffff4) > Dec 29 17:39:46 n4 HVM18[18302]: XENUTIL: WARNING: BalloonReleasePfnArray: ran for more than 6099ms > Dec 29 17:39:46 n4 HVM18[18302]: XENUTIL: BalloonWorkerThread: inflated balloon by 4090 page(s) in 15132ms (1081k/s) > Dec 29 17:39:46 n4 HVM18[18302]: XENUTIL: BalloonWorkerThread: pausing for 1s (target = 43792384k, current = 94290040k) > Dec 29 17:40:04 n4 HVM18[18302]: XENUTIL: WARNING: BalloonReleasePfnArray: ran for more than 4492ms > Dec 29 17:40:04 n4 HVM18[18302]: XENUTIL: BalloonWorkerThread: inflated balloon by 4090 page(s) in 17206ms (950k/s) > Dec 29 17:40:04 n4 HVM18[18302]: XENUTIL: BalloonWorkerThread: pausing for 1s (target = 43792384k, current = 94273680k) > Dec 29 17:40:16 n4 HVM18[18302]: XENUTIL: WARNING: BalloonReleasePfnArray: ran for more than 2043ms > Dec 29 17:40:16 n4 HVM18[18302]: XENUTIL: BalloonWorkerThread: inflated balloon by 4090 page(s) in 11294ms (1448k/s) > Dec 29 17:40:16 n4 HVM18[18302]: XENUTIL: BalloonWorkerThread: pausing for 1s (target = 43792384k, current = 94257320k) > Dec 29 17:40:27 n4 HVM18[18302]: XENUTIL: WARNING: BalloonPodSweep: HYPERVISOR_memory_op(XENMEM_pod_sweep, ...) failed (fffffff4) > Dec 29 17:40:32 n4 HVM18[18302]: XENUTIL: WARNING: BalloonReleasePfnArray: ran for more than 5179ms > Dec 29 17:40:32 n4 HVM18[18302]: XENUTIL: BalloonWorkerThread: inflated balloon by 4090 page(s) in 15100ms (1083k/s) > Dec 29 17:40:32 n4 HVM18[18302]: XENUTIL: BalloonWorkerThread: pausing for 1s (target = 43792384k, current = 94240960k) > Dec 29 17:40:46 n4 HVM18[18302]: XENUTIL: WARNING: BalloonReleasePfnArray: ran for more than 2230ms > Dec 29 17:40:46 n4 HVM18[18302]: XENUTIL: BalloonWorkerThread: inflated balloon by 4090 page(s) in 12870ms (1271k/s) > Dec 29 17:40:46 n4 HVM18[18302]: XENUTIL: BalloonWorkerThread: pausing for 1s (target = 43792384k, current = 94224600k) > Dec 29 17:41:01 n4 HVM18[18302]: XENUTIL: WARNING: BalloonReleasePfnArray: ran for more than 5350ms > Dec 29 17:41:01 n4 HVM18[18302]: XENUTIL: BalloonWorkerThread: inflated balloon by 4090 page(s) in 13228ms (1236k/s) > Dec 29 17:41:01 n4 HVM18[18302]: XENUTIL: BalloonWorkerThread: pausing for 1s (target = 43792384k, current = 94208240k) > Dec 29 17:41:14 n4 HVM18[18302]: XENUTIL: WARNING: BalloonPodSweep: HYPERVISOR_memory_op(XENMEM_pod_sweep, ...) failed (fffffff4) > Dec 29 17:41:17 n4 HVM18[18302]: XENUTIL: WARNING: BalloonReleasePfnArray: ran for more than 3026ms > Dec 29 17:41:17 n4 HVM18[18302]: XENUTIL: BalloonWorkerThread: inflated balloon by 4090 page(s) in 15490ms (1056k/s) > Dec 29 17:41:17 n4 HVM18[18302]: XENUTIL: BalloonWorkerThread: pausing for 1s (target = 43792384k, current = 94191880k) > Dec 29 17:41:31 n4 HVM18[18302]: XENUTIL: WARNING: BalloonReleasePfnArray: ran for more than 3151ms > Dec 29 17:41:31 n4 HVM18[18302]: XENUTIL: BalloonWorkerThread: inflated balloon by 4090 page(s) in 13291ms (1230k/s) > Dec 29 17:41:31 n4 HVM18[18302]: XENUTIL: BalloonWorkerThread: pausing for 1s (target = 43792384k, current = 94175520k) > Dec 29 17:41:49 n4 HVM18[18302]: XENUTIL: WARNING: BalloonReleasePfnArray: ran for more than 5553ms > Dec 29 17:41:49 n4 HVM18[18302]: XENUTIL: BalloonWorkerThread: inflated balloon by 4090 page(s) in 16832ms (971k/s) > Dec 29 17:41:49 n4 HVM18[18302]: XENUTIL: BalloonWorkerThread: pausing for 1s (target = 43792384k, current = 94159160k) > Dec 29 17:42:08 n4 HVM18[18302]: XENUTIL: WARNING: BalloonReleasePfnArray: ran for more than 6754ms > Dec 29 17:42:08 n4 HVM18[18302]: XENUTIL: BalloonWorkerThread: inflated balloon by 4090 page(s) in 18111ms (903k/s) > Dec 29 17:42:08 n4 HVM18[18302]: XENUTIL: BalloonWorkerThread: pausing for 1s (target = 43792384k, current = 94142800k) > Dec 29 17:42:28 n4 HVM18[18302]: XENUTIL: WARNING: BalloonReleasePfnArray: ran for more than 3244ms > Dec 29 17:42:28 n4 HVM18[18302]: XENUTIL: BalloonWorkerThread: inflated balloon by 4090 page(s) in 18392ms (889k/s) > Dec 29 17:42:28 n4 HVM18[18302]: XENUTIL: BalloonWorkerThread: pausing for 1s (target = 43792384k, current = 94126440k) > Dec 29 17:42:47 n4 HVM18[18302]: XENUTIL: WARNING: BalloonReleasePfnArray: ran for more than 5725ms > Dec 29 17:42:47 n4 HVM18[18302]: XENUTIL: BalloonWorkerThread: inflated balloon by 4090 page(s) in 18454ms (886k/s) > Dec 29 17:42:47 n4 HVM18[18302]: XENUTIL: BalloonWorkerThread: pausing for 1s (target = 43792384k, current = 94110080k) > Dec 29 17:43:08 n4 HVM18[18302]: XENUTIL: WARNING: BalloonReleasePfnArray: ran for more than 4243ms > Dec 29 17:43:08 n4 HVM18[18302]: XENUTIL: BalloonWorkerThread: inflated balloon by 4090 page(s) in 19453ms (841k/s) > Dec 29 17:43:08 n4 HVM18[18302]: XENUTIL: BalloonWorkerThread: pausing for 1s (target = 43792384k, current = 94093720k) > Dec 29 17:43:26 n4 HVM18[18302]: XENUTIL: WARNING: BalloonReleasePfnArray: ran for more than 5241ms > Dec 29 17:43:26 n4 HVM18[18302]: XENUTIL: BalloonWorkerThread: inflated balloon by 4090 page(s) in 17206ms (950k/s) > Dec 29 17:43:26 n4 HVM18[18302]: XENUTIL: BalloonWorkerThread: pausing for 1s (target = 43792384k, current = 94077360k) > Dec 29 17:43:44 n4 HVM18[18302]: XENUTIL: WARNING: BalloonReleasePfnArray: ran for more than 1996ms > Dec 29 17:43:44 n4 HVM18[18302]: XENUTIL: BalloonWorkerThread: inflated balloon by 4090 page(s) in 17253ms (948k/s) > Dec 29 17:43:44 n4 HVM18[18302]: XENUTIL: BalloonWorkerThread: pausing for 1s (target = 43792384k, current = 94061000k) > Dec 29 17:44:02 n4 HVM18[18302]: XENUTIL: WARNING: BalloonReleasePfnArray: ran for more than 4773ms > Dec 29 17:44:02 n4 HVM18[18302]: XENUTIL: BalloonWorkerThread: inflated balloon by 4090 page(s) in 16286ms (1004k/s) > Dec 29 17:44:02 n4 HVM18[18302]: XENUTIL: BalloonWorkerThread: pausing for 1s (target = 43792384k, current = 94044640k) > Dec 29 17:44:24 n4 HVM18[18302]: XENUTIL: WARNING: BalloonReleasePfnArray: ran for more than 2152ms > Dec 29 17:44:24 n4 HVM18[18302]: XENUTIL: BalloonWorkerThread: inflated balloon by 4090 page(s) in 21231ms (770k/s) > Dec 29 17:44:24 n4 HVM18[18302]: XENUTIL: BalloonWorkerThread: pausing for 1s (target = 43792384k, current = 94028280k) > Dec 29 17:44:40 n4 HVM18[18302]: XENUTIL: WARNING: BalloonPodSweep: HYPERVISOR_memory_op(XENMEM_pod_sweep, ...) failed (fffffff4) > Dec 29 17:44:42 n4 HVM18[18302]: XENUTIL: WARNING: BalloonReleasePfnArray: ran for more than 2199ms > Dec 29 17:44:42 n4 HVM18[18302]: XENUTIL: BalloonWorkerThread: inflated balloon by 4090 page(s) in 17331ms (943k/s) > Dec 29 17:44:42 n4 HVM18[18302]: XENUTIL: BalloonWorkerThread: pausing for 1s (target = 43792384k, current = 94011920k) > Dec 29 17:45:16 n4 HVM18[18302]: XENUTIL: BalloonWorkerThread: inflated balloon by 12554884 page(s) in 32604ms (91243k/s) > Dec 29 17:45:16 n4 HVM18[18302]: XENUTIL: BalloonWorkerThread: de-activating > Dec 29 17:45:16 n4 HVM18[18302]: XENUTIL: XenevtchnMapResources setting callback irq to 11 > Dec 29 17:45:16 n4 HVM18[18302]: XEVTCHN: PV init. done > Dec 29 17:45:16 n4 HVM18[18302]: XENUTIL: BalloonTargetChanged: 43792384k -> 48911360k > Dec 29 17:45:16 n4 HVM18[18302]: XENUTIL: BalloonWorkerThread: activating > Dec 29 17:45:16 n4 HVM18[18302]: XEVTCHN: Detected new device vif/0. > Dec 29 17:45:16 n4 HVM18[18302]: XEVTCHN: closing device/vif/0... > Dec 29 17:45:16 n4 HVM18[18302]: XEVTCHN: device/vif/0 closed > Dec 29 17:45:16 n4 HVM18[18302]: XEVTCHN: StartDeviceFdo: <==== (00000000) > Dec 29 17:45:17 n4 HVM18[18302]: XENUTIL: BalloonWorkerThread: deflated balloon by 1279744 page(s) in 998ms (825660k/s) > Dec 29 17:45:17 n4 HVM18[18302]: XENUTIL: BalloonWorkerThread: de-activating > Dec 29 17:45:18 n4 HVM18[18302]: XENVBD: XENVBD in NORMAL mode. > Dec 29 17:45:18 n4 HVM18[18302]: XENVBD: XenvbdAddDevice: FDO = 0xFFFFFA804434B060 > Dec 29 17:45:18 n4 HVM18[18302]: XENUTIL: WARNING: IO hole already initialized by XEVTCHN > Dec 29 17:45:18 n4 HVM18[18302]: XENUTIL: WARNING: Bugcheck callback already installed > Dec 29 17:45:18 n4 HVM18[18302]: XENUTIL: WARNING: Bugcheck reason callback already installed > Dec 29 17:45:18 n4 HVM18[18302]: XENVBD: RescanThread: starting > Dec 29 17:45:18 n4 HVM18[18302]: XENUTIL: XenvbdHwInitialize setting callback irq to 30 > Dec 29 17:45:19 n4 HVM18[18302]: XENVBD: DeviceRelationsFdo: scanning targets... > Dec 29 17:45:19 n4 HVM18[18302]: XENVBD: XenbusFindVbds: found new disk (VBD 768) > Dec 29 17:45:19 n4 HVM18[18302]: XENVBD: XenbusFindVbds: ignoring cdrom (VBD 5696) > Dec 29 17:45:19 n4 HVM18[18302]: XENVBD: target 0: claiming frontend... > Dec 29 17:45:19 n4 HVM18[18302]: XENVBD: target 0: successfuly claimed device/vbd/768 > Dec 29 17:45:19 n4 HVM18[18302]: XENVBD: target 0: synthesising inquiry data: default page > Dec 29 17:45:19 n4 HVM18[18302]: XENVBD: target 0: unit serial number = '62c5a501-d662-4d ' > Dec 29 17:45:19 n4 HVM18[18302]: XENVBD: target 0: device identifier[0]: CodeSet: 'Ascii' Type: 'VendorId' Assocation: 'Device' > Dec 29 17:45:19 n4 HVM18[18302]: XENVBD: target 0: device identifier[0]: Length = 45 Data = 'XENSRC 62c5a501-d662-4d38-a75c-a280e2929297 ' > Dec 29 17:45:19 n4 HVM18[18302]: XENVBD: target 0: closing frontend... > Dec 29 17:45:19 n4 HVM18[18302]: XENVBD: target 0: backend is closed > Dec 29 17:45:19 n4 HVM18[18302]: XENVBD: target 0: created > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xensource.com > http://lists.xensource.com/xen-devel _______________________________________________ xen-api mailing list xen-api@lists.xensource.com http://lists.xensource.com/mailman/listinfo/xen-api From xen-api-bounces@lists.xensource.com Fri Feb 03 14:01:08 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 03 Feb 2012 14:01:08 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1RtJhI-00043n-HA; Fri, 03 Feb 2012 14:01:04 +0000 Received: from mail21.messagelabs.com ([85.158.143.35]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Ri8Xg-0000lM-0I; Tue, 03 Jan 2012 17:52:56 +0000 X-Env-Sender: darnok@68k.org X-Msg-Ref: server-8.tower-21.messagelabs.com!1325613165!10356503!1 X-Originating-IP: [206.212.254.10] X-SpamReason: No, hits=0.5 required=7.0 tests=BODY_RANDOM_LONG X-StarScan-Version: 6.4.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 6538 invoked from network); 3 Jan 2012 17:52:47 -0000 Received: from andromeda.dapyr.net (HELO andromeda.dapyr.net) (206.212.254.10) by server-8.tower-21.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 3 Jan 2012 17:52:47 -0000 Received: from andromeda.dapyr.net (darnok@localhost [127.0.0.1]) by andromeda.dapyr.net (8.13.4/8.13.4/Debian-3sarge3) with ESMTP id q03HqhYQ005729 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 3 Jan 2012 12:52:43 -0500 Received: (from darnok@localhost) by andromeda.dapyr.net (8.13.4/8.13.4/Submit) id q03Hqh5S005727; Tue, 3 Jan 2012 12:52:43 -0500 Date: Tue, 3 Jan 2012 13:52:43 -0400 From: Konrad Rzeszutek Wilk To: R J Message-ID: <20120103175243.GE749@andromeda.dapyr.net> References: Mime-Version: 1.0 Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.9i X-Mailman-Approved-At: Fri, 03 Feb 2012 14:01:01 +0000 Cc: xen-devel@lists.xensource.com, xen-users@lists.xensource.com, xen-api@lists.xensource.com Subject: Re: [Xen-API] [Xen-devel] BalloonWorkerThread issue X-BeenThere: xen-api@lists.xensource.com X-Mailman-Version: 2.1.13 Precedence: list List-Id: Discussion of API issues surrounding Xen List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-api-bounces@lists.xensource.com Errors-To: xen-api-bounces@lists.xensource.com On Thu, Dec 29, 2011 at 11:28:59PM +0530, R J wrote: > Hello List, > > Merry Christmas to all !! > > Basically I'm trying to boot a Windows 2008R2 DC HVM with 90GB static max > memory and 32GB static min. > > The node config is Dell M610 with X5660 and 96GB RAM and its running XCP 1.1 > > Many times the node crashes while booting HVM. Sometimes I get success. Node? Meaning dom0? Or the guest? Are you using dom0_mem=max:X argument? > I have attached the HVM boot log of successful start. Many times the node > hangs as soon as the BalloonWorkerThread is activated. Which PV driver is this? Is this with the other ones: GPL one, Citrix, Novell, and Oracle as well? > > In attached txt the ballon inflation rate is constant 4090 > *XENUTIL: BalloonWorkerThread: inflated balloon by 4090 page(s) in 7924ms > (2064k/s) * > > till the time it starts, the inflation rate shoots to 12554884 and the VM > is live. > *XENUTIL: BalloonWorkerThread: inflated balloon by 12554884 page(s) in > 32604ms (91243k/s) * > *XENUTIL: BalloonWorkerThread: de-activating * > *XENUTIL: XenevtchnMapResources setting callback irq to 11 * > > > Can some one help me understand the *BalloonWorkerThread *behavior ?* > > > *Many thanks, > Rushi > Dec 29 23:08:01 n4 xenguest: Determined the following parameters from xenstore: > Dec 29 23:08:01 n4 xenguest: vcpu/number:16 vcpu/weight:0 vcpu/cap:0 nx: 1 viridian: 1 apic: 1 acpi: 1 pae: 1 acpi_s4: 0 acpi_s3: 0 > Dec 29 23:08:01 n4 xenguest: vcpu/0/affinity:0 > Dec 29 23:08:01 n4 xenguest: vcpu/1/affinity:0 > Dec 29 23:08:01 n4 xenguest: vcpu/2/affinity:0 > Dec 29 23:08:01 n4 xenguest: vcpu/3/affinity:0 > Dec 29 23:08:01 n4 xenguest: vcpu/4/affinity:0 > Dec 29 23:08:01 n4 xenguest: vcpu/5/affinity:0 > Dec 29 23:08:01 n4 xenguest: vcpu/6/affinity:0 > Dec 29 23:08:01 n4 xenguest: vcpu/7/affinity:0 > Dec 29 23:08:01 n4 xenguest: vcpu/8/affinity:0 > Dec 29 23:08:01 n4 xenguest: vcpu/9/affinity:0 > Dec 29 23:08:01 n4 xenguest: vcpu/10/affinity:0 > Dec 29 23:08:01 n4 xenguest: vcpu/11/affinity:0 > Dec 29 23:08:01 n4 xenguest: vcpu/12/affinity:0 > Dec 29 23:08:01 n4 xenguest: vcpu/13/affinity:0 > Dec 29 23:08:01 n4 xenguest: vcpu/14/affinity:0 > Dec 29 23:08:01 n4 xenguest: vcpu/15/affinity:0 > Dec 29 23:08:14 n4 tapdisk[18204]: tapdisk-control: init, 10 x 4k buffers > Dec 29 23:08:14 n4 tapdisk[18204]: I/O queue driver: lio > Dec 29 23:08:14 n4 tapdisk[18204]: tapdisk-log: started, level 0 > Dec 29 23:08:14 n4 tapdisk[18204]: received 'attach' message (uuid = 0) > Dec 29 23:08:14 n4 tapdisk[18204]: sending 'attach response' message (uuid = 0) > Dec 29 23:08:14 n4 tapdisk[18204]: received 'open' message (uuid = 0) > Dec 29 23:08:14 n4 tapdisk[18204]: Loading driver 'vhd' for vbd 0 /dev/VG_XenStorage-49740841-8056-06e2-373b-ec72084f6fb0/VHD-62c5a501-d662-4d38-a75c-a280e2929297 0x00000000 > Dec 29 23:08:14 n4 tapdisk[18204]: /dev/VG_XenStorage-49740841-8056-06e2-373b-ec72084f6fb0/VHD-62c5a501-d662-4d38-a75c-a280e2929297 version: tap 0x00010003, b: 15360, a: 307, f: 26, n: 1268376 > Dec 29 23:08:14 n4 tapdisk[18204]: opened image /dev/VG_XenStorage-49740841-8056-06e2-373b-ec72084f6fb0/VHD-62c5a501-d662-4d38-a75c-a280e2929297 (1 users, state: 0x00000001, type: 4) > Dec 29 23:08:14 n4 tapdisk[18204]: /dev/mapper/VG_XenStorage--49740841--8056--06e2--373b--ec72084f6fb0-VHD--8eae906c--8f44--4618--a850--3aaa5293408b version: tap 0x00010003, b: 15360, a: 3331, f: 3307, n: 0 > Dec 29 23:08:14 n4 tapdisk[18204]: opened image /dev/mapper/VG_XenStorage--49740841--8056--06e2--373b--ec72084f6fb0-VHD--8eae906c--8f44--4618--a850--3aaa5293408b (1 users, state: 0x00000003, type: 4) > Dec 29 23:08:14 n4 tapdisk[18204]: VBD CHAIN: > Dec 29 23:08:14 n4 tapdisk[18204]: /dev/VG_XenStorage-49740841-8056-06e2-373b-ec72084f6fb0/VHD-62c5a501-d662-4d38-a75c-a280e2929297: type:vhd(4) storage:lvm(3) > Dec 29 23:08:14 n4 tapdisk[18204]: /dev/mapper/VG_XenStorage--49740841--8056--06e2--373b--ec72084f6fb0-VHD--8eae906c--8f44--4618--a850--3aaa5293408b: type:vhd(4) storage:lvm(3) > Dec 29 23:08:14 n4 tapdisk[18204]: sending 'open response' message (uuid = 0) > Dec 29 23:08:14 n4 vbd.uevent[add](backend/vbd/18/768): wrote /xapi/18/hotplug/vbd/768/hotplug = 'online' > Dec 29 23:08:15 n4 vbd.uevent[add](backend/vbd/18/5696): wrote /xapi/18/hotplug/vbd/5696/hotplug = 'online' > Dec 29 23:08:15 n4 ovs-vsctl: 00001|vsctl|INFO|Called as /usr/bin/ovs-vsctl list-ports xapi9 > Dec 29 23:08:15 n4 ovs-vsctl: 00001|vsctl|INFO|Called as /usr/bin/ovs-vsctl --timeout=30 -- --if-exists del-port vif18.0 -- add-port xapi9 vif18.0 -- set interface vif18.0 "external-ids:\"xs-vm-uuid\"=\"6591a403-0eba-30b4-96a6-e02a7db0607a\"" -- set interface vif18.0 "external-ids:\"xs-vif-uuid\"=\"3be54e6d-6d13-b04b-6735-24831e5169e5\"" -- set interface vif18.0 "external-ids:\"xs-network-uuid\"=\"7051ef99-4fcb-fa61-a10e-f98456e12e90\"" -- set interface vif18.0 "external-ids:\"attached-mac\"=\"d6:6d:60:7e:45:52\"" > Dec 29 23:08:15 n4 qemu.18: domid: 18 > Dec 29 23:08:15 n4 qemu.18: qemu: the number of cpus is 16 > Dec 29 23:08:15 n4 qemu.18: -videoram option does not work with cirrus vga device model. Videoram set to 4M. > Dec 29 23:08:15 n4 HVM18[18302]: Guest uuid = 6591a403-0eba-30b4-96a6-e02a7db0607a > Dec 29 23:08:15 n4 HVM18[18302]: Watching /local/domain/18/logdirty/next-active > Dec 29 23:08:15 n4 HVM18[18302]: Watching /local/domain/0/device-model/18/command > Dec 29 23:08:15 n4 HVM18[18302]: char device redirected to /dev/pts/2 > Dec 29 23:08:15 n4 HVM18[18302]: char device redirected to /dev/pts/3 > Dec 29 23:08:15 n4 HVM18[18302]: qemu_map_cache_init nr_buckets = 4000 size 327680 > Dec 29 23:08:15 n4 HVM18[18302]: shared page at pfn feffd > Dec 29 23:08:15 n4 HVM18[18302]: buffered io page at pfn feffb > Dec 29 23:08:15 n4 HVM18[18302]: Time offset set 0 > Dec 29 23:08:15 n4 HVM18[18302]: pci_register_device: 00:00:00 (i440FX) > Dec 29 23:08:15 n4 HVM18[18302]: pci_register_device: 00:01:00 (PIIX3) > Dec 29 23:08:15 n4 HVM18[18302]: pci_register_device: 00:02:00 (Cirrus VGA) > Dec 29 23:08:15 n4 HVM18[18302]: populating video RAM at ff000000 > Dec 29 23:08:15 n4 HVM18[18302]: mapping video RAM from ff000000 > Dec 29 23:08:15 n4 HVM18[18302]: pci_register_device: 00:03:00 (xen-platform) > Dec 29 23:08:15 n4 HVM18[18302]: xs_read(/vm/6591a403-0eba-30b4-96a6-e02a7db0607a/log-throttling): read error > Dec 29 23:08:15 n4 HVM18[18302]: ROM memory area now RW > Dec 29 23:08:15 n4 HVM18[18302]: pci_register_device: 00:04:00 (RTL8139) > Dec 29 23:08:15 n4 HVM18[18302]: pci_register_device: 00:01:01 (PIIX3 IDE) > Dec 29 23:08:15 n4 HVM18[18302]: pci_register_device: 00:01:02 (USB-UHCI) > Dec 29 23:08:15 n4 HVM18[18302]: pci_register_device: 00:01:03 (PIIX4 ACPI) > Dec 29 23:08:15 n4 HVM18[18302]: xs_read(/local/domain/0/device-model/18/xen_extended_power_mgmt): read error > Dec 29 23:08:15 n4 HVM18[18302]: releasing VM > Dec 29 23:08:15 n4 HVM18[18302]: xs_read(): vncpasswd get error. /vm/6591a403-0eba-30b4-96a6-e02a7db0607a/vncpasswd. > Dec 29 23:08:15 n4 HVM18[18302]: I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 > Dec 29 17:38:15 n4 last message repeated 2 times > Dec 29 17:38:15 n4 HVM18[18302]: Triggered log-dirty buffer switch > Dec 29 17:38:15 n4 HVM18[18302]: I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 > Dec 29 17:38:15 n4 HVM18[18302]: medium change watch on `hdd' (index: 1): > Dec 29 17:38:15 n4 HVM18[18302]: I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 > Dec 29 17:38:15 n4 last message repeated 11 times > Dec 29 17:38:16 n4 HVM18[18302]: cirrus vga map change while on lfb mode > Dec 29 23:08:16 n4 ovs-vsctl: 00001|vsctl|INFO|Called as /usr/bin/ovs-vsctl --timeout=30 -- --if-exists del-port tap18.0 -- add-port xapi9 tap18.0 > Dec 29 17:38:16 n4 HVM18[18302]: mapping vram to f0000000 - f0400000 > Dec 29 17:38:17 n4 HVM18[18302]: ROM memory area now RW > Dec 29 17:38:17 n4 HVM18[18302]: ROM memory area now RO > Dec 29 17:38:18 n4 HVM18[18302]: cirrus: blanking the screen line_offset=3072 height=768 > Dec 29 17:38:34 n4 HVM18[18302]: cirrus: blanking the screen line_offset=1024 height=768 > Dec 29 17:38:37 n4 HVM18[18302]: UNPLUG: protocol version set to 1 (drivers not blacklisted) > Dec 29 17:38:37 n4 HVM18[18302]: UNPLUG: protocol 1 active > Dec 29 17:38:37 n4 HVM18[18302]: UNPLUG: product_id: 1 build_number: 30876 > Dec 29 17:38:37 n4 HVM18[18302]: UNPLUG: drivers not blacklisted > Dec 29 17:38:37 n4 HVM18[18302]: ide_unplug_harddisk: drive 0 > Dec 29 17:38:37 n4 HVM18[18302]: pci_dev_unplug: 00:04:00 > Dec 29 17:38:37 n4 HVM18[18302]: net_tap_shutdown: model=tap,name=tap.0 > Dec 29 23:08:38 n4 ovs-vsctl: 00001|vsctl|INFO|Called as /usr/bin/ovs-vsctl --timeout=30 -- --if-exists del-port tap18.0 > Dec 29 17:38:38 n4 HVM18[18302]: XEVTCHN: InstallDumpDeviceCallback: version mismatch (255 != 1) > Dec 29 17:38:38 n4 HVM18[18302]: XEVTCHN: XenevtchnAddDevice: FDO = 0xFFFFFA8044323970 > Dec 29 17:38:38 n4 HVM18[18302]: XEVTCHN: Initialized tracing provider > Dec 29 17:38:38 n4 HVM18[18302]: XEVTCHN: StartDeviceFdo: ====> > Dec 29 17:38:38 n4 HVM18[18302]: XENUTIL: XEVTCHN: IO hole: [00000000fbfa6000,00000000fc000000) mapped at FFFFF88002965000 > Dec 29 17:38:38 n4 HVM18[18302]: net_tap_shutdown: model=tap,name=tap.0 > Dec 29 17:38:38 n4 HVM18[18302]: XENUTIL: KERNEL: 6.1 (build 7600) platform WIN32_NT > Dec 29 17:38:38 n4 HVM18[18302]: XENUTIL: SP: NONE > Dec 29 17:38:38 n4 HVM18[18302]: XENUTIL: SUITES: > Dec 29 17:38:38 n4 HVM18[18302]: XENUTIL: - TERMINAL > Dec 29 17:38:38 n4 HVM18[18302]: XENUTIL: - DATACENTER > Dec 29 17:38:38 n4 HVM18[18302]: XENUTIL: - SINGLEUSERTS > Dec 29 17:38:38 n4 HVM18[18302]: XENUTIL: TYPE: SERVER > Dec 29 17:38:38 n4 HVM18[18302]: XENUTIL: PV DRIVERS: VERSION: 5.6.0 BUILD: 30876 (Apr 30 2010.06:57:01) > Dec 29 17:38:38 n4 HVM18[18302]: XENUTIL: 64-bit HVM > Dec 29 17:38:38 n4 HVM18[18302]: net_tap_shutdown: model=tap,name=tap.0 > Dec 29 17:38:38 n4 HVM18[18302]: XENUTIL: ExpandGrantTable: GRANT TABLE 0: (0 - 511) at FFFFF88002966000 (fbfa7000) > Dec 29 17:38:38 n4 HVM18[18302]: XENUTIL: XenEnterprise product string is present > Dec 29 17:38:39 n4 HVM18[18302]: XENUTIL: PHYSICAL MEMORY: TOP = 00000016.8fc00000 > Dec 29 17:38:39 n4 HVM18[18302]: XENUTIL: BalloonTargetChanged: 94371840k -> 43792384k > Dec 29 17:38:39 n4 HVM18[18302]: XENUTIL: BalloonWorkerThread: activating > Dec 29 17:38:47 n4 HVM18[18302]: XENUTIL: WARNING: BalloonReleasePfnArray: ran for more than 2230ms > Dec 29 17:38:47 n4 HVM18[18302]: XENUTIL: BalloonWorkerThread: inflated balloon by 4090 page(s) in 7924ms (2064k/s) > Dec 29 17:38:47 n4 HVM18[18302]: XENUTIL: BalloonWorkerThread: pausing for 1s (target = 43792384k, current = 94355480k) > Dec 29 17:38:57 n4 HVM18[18302]: XENUTIL: WARNING: BalloonReleasePfnArray: ran for more than 1794ms > Dec 29 17:38:57 n4 HVM18[18302]: XENUTIL: BalloonWorkerThread: inflated balloon by 4090 page(s) in 9157ms (1786k/s) > Dec 29 17:38:57 n4 HVM18[18302]: XENUTIL: BalloonWorkerThread: pausing for 1s (target = 43792384k, current = 94339120k) > Dec 29 17:39:13 n4 HVM18[18302]: XENUTIL: WARNING: BalloonReleasePfnArray: ran for more than 5070ms > Dec 29 17:39:13 n4 HVM18[18302]: XENUTIL: BalloonWorkerThread: inflated balloon by 4090 page(s) in 14601ms (1120k/s) > Dec 29 17:39:13 n4 HVM18[18302]: XENUTIL: BalloonWorkerThread: pausing for 1s (target = 43792384k, current = 94322760k) > Dec 29 17:39:30 n4 HVM18[18302]: XENUTIL: WARNING: BalloonReleasePfnArray: ran for more than 4321ms > Dec 29 17:39:30 n4 HVM18[18302]: XENUTIL: BalloonWorkerThread: inflated balloon by 4090 page(s) in 16052ms (1019k/s) > Dec 29 17:39:30 n4 HVM18[18302]: XENUTIL: BalloonWorkerThread: pausing for 1s (target = 43792384k, current = 94306400k) > Dec 29 17:39:40 n4 HVM18[18302]: XENUTIL: WARNING: BalloonPodSweep: HYPERVISOR_memory_op(XENMEM_pod_sweep, ...) failed (fffffff4) > Dec 29 17:39:46 n4 HVM18[18302]: XENUTIL: WARNING: BalloonReleasePfnArray: ran for more than 6099ms > Dec 29 17:39:46 n4 HVM18[18302]: XENUTIL: BalloonWorkerThread: inflated balloon by 4090 page(s) in 15132ms (1081k/s) > Dec 29 17:39:46 n4 HVM18[18302]: XENUTIL: BalloonWorkerThread: pausing for 1s (target = 43792384k, current = 94290040k) > Dec 29 17:40:04 n4 HVM18[18302]: XENUTIL: WARNING: BalloonReleasePfnArray: ran for more than 4492ms > Dec 29 17:40:04 n4 HVM18[18302]: XENUTIL: BalloonWorkerThread: inflated balloon by 4090 page(s) in 17206ms (950k/s) > Dec 29 17:40:04 n4 HVM18[18302]: XENUTIL: BalloonWorkerThread: pausing for 1s (target = 43792384k, current = 94273680k) > Dec 29 17:40:16 n4 HVM18[18302]: XENUTIL: WARNING: BalloonReleasePfnArray: ran for more than 2043ms > Dec 29 17:40:16 n4 HVM18[18302]: XENUTIL: BalloonWorkerThread: inflated balloon by 4090 page(s) in 11294ms (1448k/s) > Dec 29 17:40:16 n4 HVM18[18302]: XENUTIL: BalloonWorkerThread: pausing for 1s (target = 43792384k, current = 94257320k) > Dec 29 17:40:27 n4 HVM18[18302]: XENUTIL: WARNING: BalloonPodSweep: HYPERVISOR_memory_op(XENMEM_pod_sweep, ...) failed (fffffff4) > Dec 29 17:40:32 n4 HVM18[18302]: XENUTIL: WARNING: BalloonReleasePfnArray: ran for more than 5179ms > Dec 29 17:40:32 n4 HVM18[18302]: XENUTIL: BalloonWorkerThread: inflated balloon by 4090 page(s) in 15100ms (1083k/s) > Dec 29 17:40:32 n4 HVM18[18302]: XENUTIL: BalloonWorkerThread: pausing for 1s (target = 43792384k, current = 94240960k) > Dec 29 17:40:46 n4 HVM18[18302]: XENUTIL: WARNING: BalloonReleasePfnArray: ran for more than 2230ms > Dec 29 17:40:46 n4 HVM18[18302]: XENUTIL: BalloonWorkerThread: inflated balloon by 4090 page(s) in 12870ms (1271k/s) > Dec 29 17:40:46 n4 HVM18[18302]: XENUTIL: BalloonWorkerThread: pausing for 1s (target = 43792384k, current = 94224600k) > Dec 29 17:41:01 n4 HVM18[18302]: XENUTIL: WARNING: BalloonReleasePfnArray: ran for more than 5350ms > Dec 29 17:41:01 n4 HVM18[18302]: XENUTIL: BalloonWorkerThread: inflated balloon by 4090 page(s) in 13228ms (1236k/s) > Dec 29 17:41:01 n4 HVM18[18302]: XENUTIL: BalloonWorkerThread: pausing for 1s (target = 43792384k, current = 94208240k) > Dec 29 17:41:14 n4 HVM18[18302]: XENUTIL: WARNING: BalloonPodSweep: HYPERVISOR_memory_op(XENMEM_pod_sweep, ...) failed (fffffff4) > Dec 29 17:41:17 n4 HVM18[18302]: XENUTIL: WARNING: BalloonReleasePfnArray: ran for more than 3026ms > Dec 29 17:41:17 n4 HVM18[18302]: XENUTIL: BalloonWorkerThread: inflated balloon by 4090 page(s) in 15490ms (1056k/s) > Dec 29 17:41:17 n4 HVM18[18302]: XENUTIL: BalloonWorkerThread: pausing for 1s (target = 43792384k, current = 94191880k) > Dec 29 17:41:31 n4 HVM18[18302]: XENUTIL: WARNING: BalloonReleasePfnArray: ran for more than 3151ms > Dec 29 17:41:31 n4 HVM18[18302]: XENUTIL: BalloonWorkerThread: inflated balloon by 4090 page(s) in 13291ms (1230k/s) > Dec 29 17:41:31 n4 HVM18[18302]: XENUTIL: BalloonWorkerThread: pausing for 1s (target = 43792384k, current = 94175520k) > Dec 29 17:41:49 n4 HVM18[18302]: XENUTIL: WARNING: BalloonReleasePfnArray: ran for more than 5553ms > Dec 29 17:41:49 n4 HVM18[18302]: XENUTIL: BalloonWorkerThread: inflated balloon by 4090 page(s) in 16832ms (971k/s) > Dec 29 17:41:49 n4 HVM18[18302]: XENUTIL: BalloonWorkerThread: pausing for 1s (target = 43792384k, current = 94159160k) > Dec 29 17:42:08 n4 HVM18[18302]: XENUTIL: WARNING: BalloonReleasePfnArray: ran for more than 6754ms > Dec 29 17:42:08 n4 HVM18[18302]: XENUTIL: BalloonWorkerThread: inflated balloon by 4090 page(s) in 18111ms (903k/s) > Dec 29 17:42:08 n4 HVM18[18302]: XENUTIL: BalloonWorkerThread: pausing for 1s (target = 43792384k, current = 94142800k) > Dec 29 17:42:28 n4 HVM18[18302]: XENUTIL: WARNING: BalloonReleasePfnArray: ran for more than 3244ms > Dec 29 17:42:28 n4 HVM18[18302]: XENUTIL: BalloonWorkerThread: inflated balloon by 4090 page(s) in 18392ms (889k/s) > Dec 29 17:42:28 n4 HVM18[18302]: XENUTIL: BalloonWorkerThread: pausing for 1s (target = 43792384k, current = 94126440k) > Dec 29 17:42:47 n4 HVM18[18302]: XENUTIL: WARNING: BalloonReleasePfnArray: ran for more than 5725ms > Dec 29 17:42:47 n4 HVM18[18302]: XENUTIL: BalloonWorkerThread: inflated balloon by 4090 page(s) in 18454ms (886k/s) > Dec 29 17:42:47 n4 HVM18[18302]: XENUTIL: BalloonWorkerThread: pausing for 1s (target = 43792384k, current = 94110080k) > Dec 29 17:43:08 n4 HVM18[18302]: XENUTIL: WARNING: BalloonReleasePfnArray: ran for more than 4243ms > Dec 29 17:43:08 n4 HVM18[18302]: XENUTIL: BalloonWorkerThread: inflated balloon by 4090 page(s) in 19453ms (841k/s) > Dec 29 17:43:08 n4 HVM18[18302]: XENUTIL: BalloonWorkerThread: pausing for 1s (target = 43792384k, current = 94093720k) > Dec 29 17:43:26 n4 HVM18[18302]: XENUTIL: WARNING: BalloonReleasePfnArray: ran for more than 5241ms > Dec 29 17:43:26 n4 HVM18[18302]: XENUTIL: BalloonWorkerThread: inflated balloon by 4090 page(s) in 17206ms (950k/s) > Dec 29 17:43:26 n4 HVM18[18302]: XENUTIL: BalloonWorkerThread: pausing for 1s (target = 43792384k, current = 94077360k) > Dec 29 17:43:44 n4 HVM18[18302]: XENUTIL: WARNING: BalloonReleasePfnArray: ran for more than 1996ms > Dec 29 17:43:44 n4 HVM18[18302]: XENUTIL: BalloonWorkerThread: inflated balloon by 4090 page(s) in 17253ms (948k/s) > Dec 29 17:43:44 n4 HVM18[18302]: XENUTIL: BalloonWorkerThread: pausing for 1s (target = 43792384k, current = 94061000k) > Dec 29 17:44:02 n4 HVM18[18302]: XENUTIL: WARNING: BalloonReleasePfnArray: ran for more than 4773ms > Dec 29 17:44:02 n4 HVM18[18302]: XENUTIL: BalloonWorkerThread: inflated balloon by 4090 page(s) in 16286ms (1004k/s) > Dec 29 17:44:02 n4 HVM18[18302]: XENUTIL: BalloonWorkerThread: pausing for 1s (target = 43792384k, current = 94044640k) > Dec 29 17:44:24 n4 HVM18[18302]: XENUTIL: WARNING: BalloonReleasePfnArray: ran for more than 2152ms > Dec 29 17:44:24 n4 HVM18[18302]: XENUTIL: BalloonWorkerThread: inflated balloon by 4090 page(s) in 21231ms (770k/s) > Dec 29 17:44:24 n4 HVM18[18302]: XENUTIL: BalloonWorkerThread: pausing for 1s (target = 43792384k, current = 94028280k) > Dec 29 17:44:40 n4 HVM18[18302]: XENUTIL: WARNING: BalloonPodSweep: HYPERVISOR_memory_op(XENMEM_pod_sweep, ...) failed (fffffff4) > Dec 29 17:44:42 n4 HVM18[18302]: XENUTIL: WARNING: BalloonReleasePfnArray: ran for more than 2199ms > Dec 29 17:44:42 n4 HVM18[18302]: XENUTIL: BalloonWorkerThread: inflated balloon by 4090 page(s) in 17331ms (943k/s) > Dec 29 17:44:42 n4 HVM18[18302]: XENUTIL: BalloonWorkerThread: pausing for 1s (target = 43792384k, current = 94011920k) > Dec 29 17:45:16 n4 HVM18[18302]: XENUTIL: BalloonWorkerThread: inflated balloon by 12554884 page(s) in 32604ms (91243k/s) > Dec 29 17:45:16 n4 HVM18[18302]: XENUTIL: BalloonWorkerThread: de-activating > Dec 29 17:45:16 n4 HVM18[18302]: XENUTIL: XenevtchnMapResources setting callback irq to 11 > Dec 29 17:45:16 n4 HVM18[18302]: XEVTCHN: PV init. done > Dec 29 17:45:16 n4 HVM18[18302]: XENUTIL: BalloonTargetChanged: 43792384k -> 48911360k > Dec 29 17:45:16 n4 HVM18[18302]: XENUTIL: BalloonWorkerThread: activating > Dec 29 17:45:16 n4 HVM18[18302]: XEVTCHN: Detected new device vif/0. > Dec 29 17:45:16 n4 HVM18[18302]: XEVTCHN: closing device/vif/0... > Dec 29 17:45:16 n4 HVM18[18302]: XEVTCHN: device/vif/0 closed > Dec 29 17:45:16 n4 HVM18[18302]: XEVTCHN: StartDeviceFdo: <==== (00000000) > Dec 29 17:45:17 n4 HVM18[18302]: XENUTIL: BalloonWorkerThread: deflated balloon by 1279744 page(s) in 998ms (825660k/s) > Dec 29 17:45:17 n4 HVM18[18302]: XENUTIL: BalloonWorkerThread: de-activating > Dec 29 17:45:18 n4 HVM18[18302]: XENVBD: XENVBD in NORMAL mode. > Dec 29 17:45:18 n4 HVM18[18302]: XENVBD: XenvbdAddDevice: FDO = 0xFFFFFA804434B060 > Dec 29 17:45:18 n4 HVM18[18302]: XENUTIL: WARNING: IO hole already initialized by XEVTCHN > Dec 29 17:45:18 n4 HVM18[18302]: XENUTIL: WARNING: Bugcheck callback already installed > Dec 29 17:45:18 n4 HVM18[18302]: XENUTIL: WARNING: Bugcheck reason callback already installed > Dec 29 17:45:18 n4 HVM18[18302]: XENVBD: RescanThread: starting > Dec 29 17:45:18 n4 HVM18[18302]: XENUTIL: XenvbdHwInitialize setting callback irq to 30 > Dec 29 17:45:19 n4 HVM18[18302]: XENVBD: DeviceRelationsFdo: scanning targets... > Dec 29 17:45:19 n4 HVM18[18302]: XENVBD: XenbusFindVbds: found new disk (VBD 768) > Dec 29 17:45:19 n4 HVM18[18302]: XENVBD: XenbusFindVbds: ignoring cdrom (VBD 5696) > Dec 29 17:45:19 n4 HVM18[18302]: XENVBD: target 0: claiming frontend... > Dec 29 17:45:19 n4 HVM18[18302]: XENVBD: target 0: successfuly claimed device/vbd/768 > Dec 29 17:45:19 n4 HVM18[18302]: XENVBD: target 0: synthesising inquiry data: default page > Dec 29 17:45:19 n4 HVM18[18302]: XENVBD: target 0: unit serial number = '62c5a501-d662-4d ' > Dec 29 17:45:19 n4 HVM18[18302]: XENVBD: target 0: device identifier[0]: CodeSet: 'Ascii' Type: 'VendorId' Assocation: 'Device' > Dec 29 17:45:19 n4 HVM18[18302]: XENVBD: target 0: device identifier[0]: Length = 45 Data = 'XENSRC 62c5a501-d662-4d38-a75c-a280e2929297 ' > Dec 29 17:45:19 n4 HVM18[18302]: XENVBD: target 0: closing frontend... > Dec 29 17:45:19 n4 HVM18[18302]: XENVBD: target 0: backend is closed > Dec 29 17:45:19 n4 HVM18[18302]: XENVBD: target 0: created > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xensource.com > http://lists.xensource.com/xen-devel _______________________________________________ xen-api mailing list xen-api@lists.xensource.com http://lists.xensource.com/mailman/listinfo/xen-api From xen-api-bounces@lists.xensource.com Fri Feb 03 14:01:08 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 03 Feb 2012 14:01:08 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1RtJhJ-00044L-2j; Fri, 03 Feb 2012 14:01:05 +0000 Received: from mail174.messagelabs.com ([85.158.138.51]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1RmMWA-0004AS-Fj for xen-api@lists.xensource.com; Sun, 15 Jan 2012 09:36:50 +0000 X-Env-Sender: thomas@goirand.fr X-Msg-Ref: server-3.tower-174.messagelabs.com!1326620202!9124071!1 X-Originating-IP: [117.121.247.104] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Version: 6.4.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 23731 invoked from network); 15 Jan 2012 09:36:44 -0000 Received: from mx.atlanta.gplhost.com (HELO mx.atlanta.gplhost.com) (117.121.247.104) by server-3.tower-174.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 15 Jan 2012 09:36:44 -0000 Received: from mx.atlanta.gplhost.com (localhost.localdomain [127.0.0.1]) by mx.atlanta.gplhost.com (Postfix) with ESMTP id 9B37F34013 for ; Sun, 15 Jan 2012 09:37:06 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha1; c=simple; d=goirand.fr; h=message-id :date:from:mime-version:to:subject:references:in-reply-to :content-type:content-transfer-encoding; s=postfix; bh=VGotbtR8z uWIndtGu7ccGyMfoxg=; b=LpllG18kUc+AiJhULqRkv6u5DbaECCQONA+bU0YD3 cj0F/D9d7TXsRLm20uoVnb4nqXuQL569jve3OwETFW6BrHzReDASSDLBsHSPxxXG duLW9e/8wG60cs0B/jWxJvcgO3nYzqKBW1SJPxOkJXbadbof85og9y+mTrIec9VN Yc= DomainKey-Signature: a=rsa-sha1; c=simple; d=goirand.fr; h=message-id :date:from:mime-version:to:subject:references:in-reply-to :content-type:content-transfer-encoding; q=dns; s=postfix; b=TxP bm5yB3E0c+EvJI8yUmq9/LD9Q29VMRmUVFZpWCaVjfB1K/goPOEJKuQmwZvdvMny dJIP10zLPmtcG/zCAx8i0yfKHe/iLTZE+goOyFAWC6N1wjI1ChvShwafKIJjra6b vguuvCZXEN5sF5T2cIhlPnUH9bZU1WlVIWGQAYGM= Received: from [127.0.0.1] (atl.apt-proxy.gplhost.com [117.121.247.20]) by mx.atlanta.gplhost.com (Postfix) with ESMTPA id E4AA234010 for ; Sun, 15 Jan 2012 09:37:05 +0000 (UTC) Message-ID: <4F129E27.6030004@goirand.fr> Date: Sun, 15 Jan 2012 17:36:39 +0800 From: Thomas Goirand Organization: GPLHost User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.16) Gecko/20111110 Icedove/3.0.11 MIME-Version: 1.0 To: "xen-api@lists.xensource.com" References: <4F108BFC.6030308@gmail.com> <4F1123EE.9080906@goirand.fr> <4F11D7D9.3020000@gmail.com> In-Reply-To: <4F11D7D9.3020000@gmail.com> X-Enigmail-Version: 1.0.1 X-Mailman-Approved-At: Fri, 03 Feb 2012 14:01:01 +0000 Subject: Re: [Xen-API] [XCP] [kronos] missed nfs-common dependence X-BeenThere: xen-api@lists.xensource.com X-Mailman-Version: 2.1.13 Precedence: list List-Id: Discussion of API issues surrounding Xen List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-api-bounces@lists.xensource.com Errors-To: xen-api-bounces@lists.xensource.com On 01/15/2012 03:30 AM, George Shuklin wrote: > OK, sorry, miss that. > > But idea to split packages to separate SM's is still actual. If you > install storage-manager, you expect it will provide same as normal XCP > (xe sr-create and it works), but this is not completely true: You will > need to set up some other packages, so using hard dependence for > something like xcp-storage-manager-nfs and suggest for > xcp-strorage-manager-nfs in dependence of xcp-storage-manager will be > better, IMHO. IMO (and that's the one of many Debian contributors and developers), you expect users to read the README.Debian which documents all this. I just added few lines about it in it. Now, if we have a separate xcp-storage-manager-nfs and xcp-storage-manager-samba, then these wouldn't be mandatory (eg: not hard dependencies), so it wouldn't change anything. Best would be if xe-mount-iso-sr was checking if there is the needed software installed by default, and was throwing a nice error message telling what to do (eg: apt-get install) if the relevant packages are missing. Thomas P.S: No need to Cc: me, I'm registered to the list. _______________________________________________ xen-api mailing list xen-api@lists.xensource.com http://lists.xensource.com/mailman/listinfo/xen-api From xen-api-bounces@lists.xensource.com Fri Feb 03 14:01:08 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 03 Feb 2012 14:01:08 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1RtJhJ-00044L-2j; Fri, 03 Feb 2012 14:01:05 +0000 Received: from mail174.messagelabs.com ([85.158.138.51]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1RmMWA-0004AS-Fj for xen-api@lists.xensource.com; Sun, 15 Jan 2012 09:36:50 +0000 X-Env-Sender: thomas@goirand.fr X-Msg-Ref: server-3.tower-174.messagelabs.com!1326620202!9124071!1 X-Originating-IP: [117.121.247.104] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Version: 6.4.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 23731 invoked from network); 15 Jan 2012 09:36:44 -0000 Received: from mx.atlanta.gplhost.com (HELO mx.atlanta.gplhost.com) (117.121.247.104) by server-3.tower-174.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 15 Jan 2012 09:36:44 -0000 Received: from mx.atlanta.gplhost.com (localhost.localdomain [127.0.0.1]) by mx.atlanta.gplhost.com (Postfix) with ESMTP id 9B37F34013 for ; Sun, 15 Jan 2012 09:37:06 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha1; c=simple; d=goirand.fr; h=message-id :date:from:mime-version:to:subject:references:in-reply-to :content-type:content-transfer-encoding; s=postfix; bh=VGotbtR8z uWIndtGu7ccGyMfoxg=; b=LpllG18kUc+AiJhULqRkv6u5DbaECCQONA+bU0YD3 cj0F/D9d7TXsRLm20uoVnb4nqXuQL569jve3OwETFW6BrHzReDASSDLBsHSPxxXG duLW9e/8wG60cs0B/jWxJvcgO3nYzqKBW1SJPxOkJXbadbof85og9y+mTrIec9VN Yc= DomainKey-Signature: a=rsa-sha1; c=simple; d=goirand.fr; h=message-id :date:from:mime-version:to:subject:references:in-reply-to :content-type:content-transfer-encoding; q=dns; s=postfix; b=TxP bm5yB3E0c+EvJI8yUmq9/LD9Q29VMRmUVFZpWCaVjfB1K/goPOEJKuQmwZvdvMny dJIP10zLPmtcG/zCAx8i0yfKHe/iLTZE+goOyFAWC6N1wjI1ChvShwafKIJjra6b vguuvCZXEN5sF5T2cIhlPnUH9bZU1WlVIWGQAYGM= Received: from [127.0.0.1] (atl.apt-proxy.gplhost.com [117.121.247.20]) by mx.atlanta.gplhost.com (Postfix) with ESMTPA id E4AA234010 for ; Sun, 15 Jan 2012 09:37:05 +0000 (UTC) Message-ID: <4F129E27.6030004@goirand.fr> Date: Sun, 15 Jan 2012 17:36:39 +0800 From: Thomas Goirand Organization: GPLHost User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.16) Gecko/20111110 Icedove/3.0.11 MIME-Version: 1.0 To: "xen-api@lists.xensource.com" References: <4F108BFC.6030308@gmail.com> <4F1123EE.9080906@goirand.fr> <4F11D7D9.3020000@gmail.com> In-Reply-To: <4F11D7D9.3020000@gmail.com> X-Enigmail-Version: 1.0.1 X-Mailman-Approved-At: Fri, 03 Feb 2012 14:01:01 +0000 Subject: Re: [Xen-API] [XCP] [kronos] missed nfs-common dependence X-BeenThere: xen-api@lists.xensource.com X-Mailman-Version: 2.1.13 Precedence: list List-Id: Discussion of API issues surrounding Xen List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-api-bounces@lists.xensource.com Errors-To: xen-api-bounces@lists.xensource.com On 01/15/2012 03:30 AM, George Shuklin wrote: > OK, sorry, miss that. > > But idea to split packages to separate SM's is still actual. If you > install storage-manager, you expect it will provide same as normal XCP > (xe sr-create and it works), but this is not completely true: You will > need to set up some other packages, so using hard dependence for > something like xcp-storage-manager-nfs and suggest for > xcp-strorage-manager-nfs in dependence of xcp-storage-manager will be > better, IMHO. IMO (and that's the one of many Debian contributors and developers), you expect users to read the README.Debian which documents all this. I just added few lines about it in it. Now, if we have a separate xcp-storage-manager-nfs and xcp-storage-manager-samba, then these wouldn't be mandatory (eg: not hard dependencies), so it wouldn't change anything. Best would be if xe-mount-iso-sr was checking if there is the needed software installed by default, and was throwing a nice error message telling what to do (eg: apt-get install) if the relevant packages are missing. Thomas P.S: No need to Cc: me, I'm registered to the list. _______________________________________________ xen-api mailing list xen-api@lists.xensource.com http://lists.xensource.com/mailman/listinfo/xen-api From xen-api-bounces@lists.xensource.com Fri Feb 03 14:01:08 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 03 Feb 2012 14:01:08 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1RtJhJ-00044X-79; Fri, 03 Feb 2012 14:01:05 +0000 Received: from mail27.messagelabs.com ([193.109.254.147]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1RpMKo-0008JQ-CJ for xen-api@lists.xensource.com; Mon, 23 Jan 2012 16:01:30 +0000 X-Env-Sender: ka@eta.name X-Msg-Ref: server-14.tower-27.messagelabs.com!1327334354!49723801!1 X-Originating-IP: [109.169.0.45] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Version: 6.5.5; banners=-,-,- X-VirusChecked: Checked Received: (qmail 1469 invoked from network); 23 Jan 2012 15:59:14 -0000 Received: from zion.eta.name (HELO zion.eta.name) (109.169.0.45) by server-14.tower-27.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 23 Jan 2012 15:59:14 -0000 Received: from [2.93.235.140] (helo=[10.77.0.77]) by zion.eta.name with Jah power (TLSv1:AES256-SHA:256) (Iron. Lion. Zion) (envelope-from ) id [No devil labels] for xen-api@lists.xensource.com; Mon, 23 Jan 2012 20:01:23 +0400 Message-ID: <4F1D8486.3020606@eta.name> Date: Mon, 23 Jan 2012 20:02:14 +0400 From: ka User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:9.0) Gecko/20111222 Thunderbird/9.0.1 MIME-Version: 1.0 To: xen-api@lists.xensource.com X-Mailman-Approved-At: Fri, 03 Feb 2012 14:01:01 +0000 Subject: [Xen-API] VM_REVERT_FAILED X-BeenThere: xen-api@lists.xensource.com X-Mailman-Version: 2.1.13 Precedence: list List-Id: Discussion of API issues surrounding Xen List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Sender: xen-api-bounces@lists.xensource.com Errors-To: xen-api-bounces@lists.xensource.com Hello. I use ZFS-based NFS storage for xen. I am trying to get safe backup throuhg Xen API with following algorithm: Before create ZFS snapshot I create XEN VM snapshot, export VM metadata and do ZFS snapshot. After this I delete snapshot and its VDI. But when I try to revert VM, I have strange behavior of VM.revert operation. I rollback my ZFS storage, unregister VM, import VM metadata, rescan SR and try to call VM.revert function. Its return VM_REVERT_FAILED message. *The strangeness of the fact that when I ignore VM_REVERT_FAILED exception and try to repeat VM.revert call - it works fine.* I mean that second call of VM.revert works without error (There is no pause between them). Any idea? What can I do to get more information about reason of this error? -- Many thanks in advance. _______________________________________________ xen-api mailing list xen-api@lists.xensource.com http://lists.xensource.com/mailman/listinfo/xen-api From xen-api-bounces@lists.xensource.com Fri Feb 03 14:01:08 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 03 Feb 2012 14:01:08 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1RtJhJ-00044X-79; Fri, 03 Feb 2012 14:01:05 +0000 Received: from mail27.messagelabs.com ([193.109.254.147]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1RpMKo-0008JQ-CJ for xen-api@lists.xensource.com; Mon, 23 Jan 2012 16:01:30 +0000 X-Env-Sender: ka@eta.name X-Msg-Ref: server-14.tower-27.messagelabs.com!1327334354!49723801!1 X-Originating-IP: [109.169.0.45] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Version: 6.5.5; banners=-,-,- X-VirusChecked: Checked Received: (qmail 1469 invoked from network); 23 Jan 2012 15:59:14 -0000 Received: from zion.eta.name (HELO zion.eta.name) (109.169.0.45) by server-14.tower-27.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 23 Jan 2012 15:59:14 -0000 Received: from [2.93.235.140] (helo=[10.77.0.77]) by zion.eta.name with Jah power (TLSv1:AES256-SHA:256) (Iron. Lion. Zion) (envelope-from ) id [No devil labels] for xen-api@lists.xensource.com; Mon, 23 Jan 2012 20:01:23 +0400 Message-ID: <4F1D8486.3020606@eta.name> Date: Mon, 23 Jan 2012 20:02:14 +0400 From: ka User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:9.0) Gecko/20111222 Thunderbird/9.0.1 MIME-Version: 1.0 To: xen-api@lists.xensource.com X-Mailman-Approved-At: Fri, 03 Feb 2012 14:01:01 +0000 Subject: [Xen-API] VM_REVERT_FAILED X-BeenThere: xen-api@lists.xensource.com X-Mailman-Version: 2.1.13 Precedence: list List-Id: Discussion of API issues surrounding Xen List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Sender: xen-api-bounces@lists.xensource.com Errors-To: xen-api-bounces@lists.xensource.com Hello. I use ZFS-based NFS storage for xen. I am trying to get safe backup throuhg Xen API with following algorithm: Before create ZFS snapshot I create XEN VM snapshot, export VM metadata and do ZFS snapshot. After this I delete snapshot and its VDI. But when I try to revert VM, I have strange behavior of VM.revert operation. I rollback my ZFS storage, unregister VM, import VM metadata, rescan SR and try to call VM.revert function. Its return VM_REVERT_FAILED message. *The strangeness of the fact that when I ignore VM_REVERT_FAILED exception and try to repeat VM.revert call - it works fine.* I mean that second call of VM.revert works without error (There is no pause between them). Any idea? What can I do to get more information about reason of this error? -- Many thanks in advance. _______________________________________________ xen-api mailing list xen-api@lists.xensource.com http://lists.xensource.com/mailman/listinfo/xen-api From xen-api-bounces@lists.xensource.com Fri Feb 03 14:01:08 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 03 Feb 2012 14:01:08 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1RtJhI-00043f-Cy; Fri, 03 Feb 2012 14:01:04 +0000 Received: from mail27.messagelabs.com ([193.109.254.147]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Ri1TD-000227-5e for xen-api@lists.xensource.com; Tue, 03 Jan 2012 10:19:51 +0000 X-Env-Sender: thomas@goirand.fr X-Msg-Ref: server-10.tower-27.messagelabs.com!1325585942!48822966!1 X-Originating-IP: [117.121.247.104] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Version: 6.4.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 17128 invoked from network); 3 Jan 2012 10:19:03 -0000 Received: from mx.atlanta.gplhost.com (HELO mx.atlanta.gplhost.com) (117.121.247.104) by server-10.tower-27.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 3 Jan 2012 10:19:03 -0000 Received: from mx.atlanta.gplhost.com (localhost.localdomain [127.0.0.1]) by mx.atlanta.gplhost.com (Postfix) with ESMTP id 48F0B3404C; Tue, 3 Jan 2012 10:19:51 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha1; c=simple; d=goirand.fr; h=message-id :date:from:mime-version:to:cc:subject:references:in-reply-to :content-type:content-transfer-encoding; s=postfix; bh=FZKKV2nL5 5tWSepveEaGNdoDV88=; b=HFQ+61FeyxJwSfUlSTuudl0ka0aSkq5bRenooSp31 amnOWYHdku328wn83B5KaPn/5cQJ/p36xzmt9Gmspci+XkgtD6BuZGRrfZsyeuRy N5pFynJnbClvBAa8820HE6v939qPvuNnDSUcisvf6iZHhdGoZYJB+ZzL129x8itg T0= DomainKey-Signature: a=rsa-sha1; c=simple; d=goirand.fr; h=message-id :date:from:mime-version:to:cc:subject:references:in-reply-to :content-type:content-transfer-encoding; q=dns; s=postfix; b=VNM 4+0ng+rIRSRF5objNxpwyjQIZoyt7ecmzpzzjWWvq23ziZoE/C1vhhKfmeGLJo7G nXufEasZFloNsWIZ2aQnmL8w7QTWtR/vvYzY4IVFiWr7lKTB7ZurbSOGsjsL/WMF q6KEhqKwuUoJtP5uECiVYw4PCWfTyzexAI3OqILM= Received: from [127.0.0.1] (atl.apt-proxy.gplhost.com [117.121.247.20]) by mx.atlanta.gplhost.com (Postfix) with ESMTPA id 3BA8F34013; Tue, 3 Jan 2012 10:19:47 +0000 (UTC) Message-ID: <4F02D63B.3070202@goirand.fr> Date: Tue, 03 Jan 2012 18:19:39 +0800 From: Thomas Goirand Organization: GPLHost User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.16) Gecko/20111110 Icedove/3.0.11 MIME-Version: 1.0 To: Deepak Garg References: <67EF18FDCA335F489B366120481AB6C5EE119349AA@BANPMAILBOX01.citrite.net> In-Reply-To: <67EF18FDCA335F489B366120481AB6C5EE119349AA@BANPMAILBOX01.citrite.net> X-Enigmail-Version: 1.0.1 X-Mailman-Approved-At: Fri, 03 Feb 2012 14:01:01 +0000 Cc: "xen-api@lists.xensource.com" Subject: Re: [Xen-API] Regarding Project Kronos: Problems faced and feedbacks X-BeenThere: xen-api@lists.xensource.com X-Mailman-Version: 2.1.13 Precedence: list List-Id: Discussion of API issues surrounding Xen List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-api-bounces@lists.xensource.com Errors-To: xen-api-bounces@lists.xensource.com Hi Deepak, I'm the Debian Developer who helped with the packaging and who uploaded XCP into Debian SID. I'm also working with XCP and OpenStack, and last week, I did some tests with it, using only the packages from SID. The packages are in good shape, but there's still few things to fix, like having a python-xenapi package (already committed to the Git, but not yet uploaded to SID), and have the OpenStack packages depend on it. Now, let me reply to your questions. On 12/27/2011 01:12 PM, Deepak Garg wrote: > a. After adding the repos to /etc/apt/sources.list mentioned in the wiki, I tried apt-get update. I get > the following error: > "W: GPG error: http://ppa.launchpad.net oneiric Release: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 79B578FB9273A937". > But the xcp toolstack was installed properly after that. > I see no error here, but a *warning*, which is different. The issue is that the repository isn't signed. I'm not sure how to fix that in Launchpad, but for a custom private repo, that's not so hard to do. Anyway, I believe you should just ignore this warning. > b. After setting up xenbr0, I had setup the xensource inventory in /etc/xcp/xensource-inventory as per > the wiki. But there was already a /etc/xcp/inventory file with half of the settings, so I had updated that too. > So, please update the wiki if 'xensource-inventory' is not the right filename. > Right, the new file really is /etc/xcp/inventory, and there's nothing to touch in it. It's correct by default. > c. The cmd given in wiki "service xapi status" doesn't seem to be working. Instead the correct cmd seems > to be "service xcp-xapi status" which works as desired. So I have updated the wiki with the new cmd. > Right, the init.d script has been renamed to match the package name. > d. The actual problem I am facing ( and unresolved ) is with the following cmd in > link: http://wiki.xen.org/wiki/Using_XCP_-_preparing_the_toolstack > "xe sr-create type=ext device-config:device=/dev/sda10 name-label=ext" > I get the error: "The SR could not be connected because the driver was not recognised. > driver: ext" > (I have /dev/sda10 as a logical partition formatted with ext3) > I'm not sure with the instructions on the wiki, but what I've written in here works: http://anonscm.debian.org/gitweb/?p=pkg-xen/xen-api.git;a=blob;f=debian/README.Debian;h=c342ef1829d0190ef764a9f8e259db6a60325d48;hb=57892b47dd730ea6e7a1db9e98a934122ebe0876 This will be packaged in the xcp-xapi package at the next upload. Last, I would suggest you to try using plain Debian SID rather than Ubuntu, since that's where the developments are done (Ubuntu just imports what we do in SID). Cheers, Thomas _______________________________________________ xen-api mailing list xen-api@lists.xensource.com http://lists.xensource.com/mailman/listinfo/xen-api From xen-api-bounces@lists.xensource.com Fri Feb 03 14:01:08 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 03 Feb 2012 14:01:08 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1RtJhI-00043f-Cy; Fri, 03 Feb 2012 14:01:04 +0000 Received: from mail27.messagelabs.com ([193.109.254.147]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Ri1TD-000227-5e for xen-api@lists.xensource.com; Tue, 03 Jan 2012 10:19:51 +0000 X-Env-Sender: thomas@goirand.fr X-Msg-Ref: server-10.tower-27.messagelabs.com!1325585942!48822966!1 X-Originating-IP: [117.121.247.104] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Version: 6.4.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 17128 invoked from network); 3 Jan 2012 10:19:03 -0000 Received: from mx.atlanta.gplhost.com (HELO mx.atlanta.gplhost.com) (117.121.247.104) by server-10.tower-27.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 3 Jan 2012 10:19:03 -0000 Received: from mx.atlanta.gplhost.com (localhost.localdomain [127.0.0.1]) by mx.atlanta.gplhost.com (Postfix) with ESMTP id 48F0B3404C; Tue, 3 Jan 2012 10:19:51 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha1; c=simple; d=goirand.fr; h=message-id :date:from:mime-version:to:cc:subject:references:in-reply-to :content-type:content-transfer-encoding; s=postfix; bh=FZKKV2nL5 5tWSepveEaGNdoDV88=; b=HFQ+61FeyxJwSfUlSTuudl0ka0aSkq5bRenooSp31 amnOWYHdku328wn83B5KaPn/5cQJ/p36xzmt9Gmspci+XkgtD6BuZGRrfZsyeuRy N5pFynJnbClvBAa8820HE6v939qPvuNnDSUcisvf6iZHhdGoZYJB+ZzL129x8itg T0= DomainKey-Signature: a=rsa-sha1; c=simple; d=goirand.fr; h=message-id :date:from:mime-version:to:cc:subject:references:in-reply-to :content-type:content-transfer-encoding; q=dns; s=postfix; b=VNM 4+0ng+rIRSRF5objNxpwyjQIZoyt7ecmzpzzjWWvq23ziZoE/C1vhhKfmeGLJo7G nXufEasZFloNsWIZ2aQnmL8w7QTWtR/vvYzY4IVFiWr7lKTB7ZurbSOGsjsL/WMF q6KEhqKwuUoJtP5uECiVYw4PCWfTyzexAI3OqILM= Received: from [127.0.0.1] (atl.apt-proxy.gplhost.com [117.121.247.20]) by mx.atlanta.gplhost.com (Postfix) with ESMTPA id 3BA8F34013; Tue, 3 Jan 2012 10:19:47 +0000 (UTC) Message-ID: <4F02D63B.3070202@goirand.fr> Date: Tue, 03 Jan 2012 18:19:39 +0800 From: Thomas Goirand Organization: GPLHost User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.16) Gecko/20111110 Icedove/3.0.11 MIME-Version: 1.0 To: Deepak Garg References: <67EF18FDCA335F489B366120481AB6C5EE119349AA@BANPMAILBOX01.citrite.net> In-Reply-To: <67EF18FDCA335F489B366120481AB6C5EE119349AA@BANPMAILBOX01.citrite.net> X-Enigmail-Version: 1.0.1 X-Mailman-Approved-At: Fri, 03 Feb 2012 14:01:01 +0000 Cc: "xen-api@lists.xensource.com" Subject: Re: [Xen-API] Regarding Project Kronos: Problems faced and feedbacks X-BeenThere: xen-api@lists.xensource.com X-Mailman-Version: 2.1.13 Precedence: list List-Id: Discussion of API issues surrounding Xen List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-api-bounces@lists.xensource.com Errors-To: xen-api-bounces@lists.xensource.com Hi Deepak, I'm the Debian Developer who helped with the packaging and who uploaded XCP into Debian SID. I'm also working with XCP and OpenStack, and last week, I did some tests with it, using only the packages from SID. The packages are in good shape, but there's still few things to fix, like having a python-xenapi package (already committed to the Git, but not yet uploaded to SID), and have the OpenStack packages depend on it. Now, let me reply to your questions. On 12/27/2011 01:12 PM, Deepak Garg wrote: > a. After adding the repos to /etc/apt/sources.list mentioned in the wiki, I tried apt-get update. I get > the following error: > "W: GPG error: http://ppa.launchpad.net oneiric Release: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 79B578FB9273A937". > But the xcp toolstack was installed properly after that. > I see no error here, but a *warning*, which is different. The issue is that the repository isn't signed. I'm not sure how to fix that in Launchpad, but for a custom private repo, that's not so hard to do. Anyway, I believe you should just ignore this warning. > b. After setting up xenbr0, I had setup the xensource inventory in /etc/xcp/xensource-inventory as per > the wiki. But there was already a /etc/xcp/inventory file with half of the settings, so I had updated that too. > So, please update the wiki if 'xensource-inventory' is not the right filename. > Right, the new file really is /etc/xcp/inventory, and there's nothing to touch in it. It's correct by default. > c. The cmd given in wiki "service xapi status" doesn't seem to be working. Instead the correct cmd seems > to be "service xcp-xapi status" which works as desired. So I have updated the wiki with the new cmd. > Right, the init.d script has been renamed to match the package name. > d. The actual problem I am facing ( and unresolved ) is with the following cmd in > link: http://wiki.xen.org/wiki/Using_XCP_-_preparing_the_toolstack > "xe sr-create type=ext device-config:device=/dev/sda10 name-label=ext" > I get the error: "The SR could not be connected because the driver was not recognised. > driver: ext" > (I have /dev/sda10 as a logical partition formatted with ext3) > I'm not sure with the instructions on the wiki, but what I've written in here works: http://anonscm.debian.org/gitweb/?p=pkg-xen/xen-api.git;a=blob;f=debian/README.Debian;h=c342ef1829d0190ef764a9f8e259db6a60325d48;hb=57892b47dd730ea6e7a1db9e98a934122ebe0876 This will be packaged in the xcp-xapi package at the next upload. Last, I would suggest you to try using plain Debian SID rather than Ubuntu, since that's where the developments are done (Ubuntu just imports what we do in SID). Cheers, Thomas _______________________________________________ xen-api mailing list xen-api@lists.xensource.com http://lists.xensource.com/mailman/listinfo/xen-api From xen-api-bounces@lists.xensource.com Sat Feb 11 19:15:21 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sat, 11 Feb 2012 19:15:21 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1RwIPb-0003wN-7R; Sat, 11 Feb 2012 19:15:07 +0000 Received: from mail216.messagelabs.com ([85.158.143.99]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1RwIPZ-0003wD-6t; Sat, 11 Feb 2012 19:15:05 +0000 X-Env-Sender: wannes321@gmail.com X-Msg-Ref: server-14.tower-216.messagelabs.com!1328987698!13858192!1 X-Originating-IP: [74.125.82.43] X-SpamReason: No, hits=0.3 required=7.0 tests=HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Version: 6.5.5; banners=-,-,- X-VirusChecked: Checked Received: (qmail 12545 invoked from network); 11 Feb 2012 19:14:58 -0000 Received: from mail-ww0-f43.google.com (HELO mail-ww0-f43.google.com) (74.125.82.43) by server-14.tower-216.messagelabs.com with RC4-SHA encrypted SMTP; 11 Feb 2012 19:14:58 -0000 Received: by wgbdr13 with SMTP id dr13so3358277wgb.24 for ; Sat, 11 Feb 2012 11:14:58 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=from:content-type:subject:date:message-id:to:mime-version:x-mailer; bh=pwvG7oGhOKJWNfDVnoXBo59h8Du1OiRoTF07XORDyag=; b=aVO62Mz3LHPpS0KIzXU8hvEoSN/7qikZF/44mKfY3fWlFqHL8B9yRW+MKw+K9EXy6G 5810p3tKwRfroptEquoTJ97HiyXhHUSvgHjwgIGOmvx9hHWGGylNwaERhRVbkhw7S5bX DoARP2UQdtVR+rRs0GMBpuWApm/92gFcojLHY= Received: by 10.180.78.130 with SMTP id b2mr10011335wix.1.1328987697233; Sat, 11 Feb 2012 11:14:57 -0800 (PST) Received: from [172.16.223.52] (151.20-241-81.adsl-dyn.isp.belgacom.be. [81.241.20.151]) by mx.google.com with ESMTPS id hb10sm29961652wib.10.2012.02.11.11.14.54 (version=TLSv1/SSLv3 cipher=OTHER); Sat, 11 Feb 2012 11:14:56 -0800 (PST) From: Wannes De Smet Date: Sat, 11 Feb 2012 20:14:52 +0100 Message-Id: To: xen-api@lists.xensource.com, xen-users@lists.xensource.com Mime-Version: 1.0 (Apple Message framework v1257) X-Mailer: Apple Mail (2.1257) Subject: [Xen-API] Announcing XenMaster X-BeenThere: xen-api@lists.xensource.com X-Mailman-Version: 2.1.13 Precedence: list List-Id: Discussion of API issues surrounding Xen List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============4516901266380225288==" Sender: xen-api-bounces@lists.xensource.com Errors-To: xen-api-bounces@lists.xensource.com --===============4516901266380225288== Content-Type: multipart/alternative; boundary="Apple-Mail=_FB3F3A77-CC5D-44D0-BAE8-13045D16074C" --Apple-Mail=_FB3F3A77-CC5D-44D0-BAE8-13045D16074C Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii We're happy to announce XenMaster, which has the ambitious goal to = become the de facto frontend for Xen with XCP. We've had the opportunity to present our project to some of the Xen/XCP = developers and now it's time to announce the project to a larger public. XenMaster, in short, is a HTML5 frontend coupled to a Java backend = delivering a rich UI for Xen, targeted at end users. At the moment, one is able to successfully add NFS ISO repositories and = iSCSI/NFS storage repositories (iSCSI currently only works on XenServer = 5.6), create a HVM VM and control it via a VNC shell.=20 Development thus far has been carried out by Jorgen Evens, frontend lead = and Wannes De Smet, project lead and backend developer. Of course, we = now would like to welcome you in becoming a tester and/or contributor!=20= You can find more information at xen-master.org, to install and = configure XenMaster. If you'd like to help and have experience in = developing Java and/or Javascript, load the source in your favorite IDE = and have at it! If you have any questions at all, we'll be happy to answer them here or = through GitHub. We hope to welcome you in using XenMaster! Jorgen Evens Wannes De Smet XenMaster=20= --Apple-Mail=_FB3F3A77-CC5D-44D0-BAE8-13045D16074C Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=us-ascii We're happy to announce XenMaster, which has = the ambitious goalto become the de facto frontend for Xen with = XCP.

We've had the opportunity to present our = project to some of the Xen/XCP developers and now it's time to announce = the project to a larger public.
XenMaster, in short, is a HTML5 = frontend coupled to a Java backend delivering a rich UI for Xen, = targeted at end users.
At the moment, one is able to successfully add = NFS ISO repositories and iSCSI/NFS storage repositories (iSCSI currently = only works on XenServer 5.6), create a HVM VM and control it via a VNC = shell.

Development thus far has been carried out by = Jorgen Evens, frontend lead and Wannes De Smet, project lead and backend = developer. Of course, we now would like to welcome you in becoming a = tester and/or contributor!
You can find more information at = xen-master.orginstall and configure = XenMaster. If you'd like to help and have experience in = developing Java and/or Javascript, load the source in your favorite IDE = and have at it!

If you have any questions at all, = we'll be happy to answer them here or through GitHub.

Wannes De Smet
XenMaster = = --Apple-Mail=_FB3F3A77-CC5D-44D0-BAE8-13045D16074C-- --===============4516901266380225288== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ xen-api mailing list xen-api@lists.xensource.com http://lists.xensource.com/mailman/listinfo/xen-api --===============4516901266380225288==-- From xen-api-bounces@lists.xensource.com Sat Feb 11 19:15:21 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sat, 11 Feb 2012 19:15:21 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1RwIPb-0003wN-7R; Sat, 11 Feb 2012 19:15:07 +0000 Received: from mail216.messagelabs.com ([85.158.143.99]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1RwIPZ-0003wD-6t; Sat, 11 Feb 2012 19:15:05 +0000 X-Env-Sender: wannes321@gmail.com X-Msg-Ref: server-14.tower-216.messagelabs.com!1328987698!13858192!1 X-Originating-IP: [74.125.82.43] X-SpamReason: No, hits=0.3 required=7.0 tests=HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Version: 6.5.5; banners=-,-,- X-VirusChecked: Checked Received: (qmail 12545 invoked from network); 11 Feb 2012 19:14:58 -0000 Received: from mail-ww0-f43.google.com (HELO mail-ww0-f43.google.com) (74.125.82.43) by server-14.tower-216.messagelabs.com with RC4-SHA encrypted SMTP; 11 Feb 2012 19:14:58 -0000 Received: by wgbdr13 with SMTP id dr13so3358277wgb.24 for ; Sat, 11 Feb 2012 11:14:58 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=from:content-type:subject:date:message-id:to:mime-version:x-mailer; bh=pwvG7oGhOKJWNfDVnoXBo59h8Du1OiRoTF07XORDyag=; b=aVO62Mz3LHPpS0KIzXU8hvEoSN/7qikZF/44mKfY3fWlFqHL8B9yRW+MKw+K9EXy6G 5810p3tKwRfroptEquoTJ97HiyXhHUSvgHjwgIGOmvx9hHWGGylNwaERhRVbkhw7S5bX DoARP2UQdtVR+rRs0GMBpuWApm/92gFcojLHY= Received: by 10.180.78.130 with SMTP id b2mr10011335wix.1.1328987697233; Sat, 11 Feb 2012 11:14:57 -0800 (PST) Received: from [172.16.223.52] (151.20-241-81.adsl-dyn.isp.belgacom.be. [81.241.20.151]) by mx.google.com with ESMTPS id hb10sm29961652wib.10.2012.02.11.11.14.54 (version=TLSv1/SSLv3 cipher=OTHER); Sat, 11 Feb 2012 11:14:56 -0800 (PST) From: Wannes De Smet Date: Sat, 11 Feb 2012 20:14:52 +0100 Message-Id: To: xen-api@lists.xensource.com, xen-users@lists.xensource.com Mime-Version: 1.0 (Apple Message framework v1257) X-Mailer: Apple Mail (2.1257) Subject: [Xen-API] Announcing XenMaster X-BeenThere: xen-api@lists.xensource.com X-Mailman-Version: 2.1.13 Precedence: list List-Id: Discussion of API issues surrounding Xen List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============4516901266380225288==" Sender: xen-api-bounces@lists.xensource.com Errors-To: xen-api-bounces@lists.xensource.com --===============4516901266380225288== Content-Type: multipart/alternative; boundary="Apple-Mail=_FB3F3A77-CC5D-44D0-BAE8-13045D16074C" --Apple-Mail=_FB3F3A77-CC5D-44D0-BAE8-13045D16074C Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii We're happy to announce XenMaster, which has the ambitious goal to = become the de facto frontend for Xen with XCP. We've had the opportunity to present our project to some of the Xen/XCP = developers and now it's time to announce the project to a larger public. XenMaster, in short, is a HTML5 frontend coupled to a Java backend = delivering a rich UI for Xen, targeted at end users. At the moment, one is able to successfully add NFS ISO repositories and = iSCSI/NFS storage repositories (iSCSI currently only works on XenServer = 5.6), create a HVM VM and control it via a VNC shell.=20 Development thus far has been carried out by Jorgen Evens, frontend lead = and Wannes De Smet, project lead and backend developer. Of course, we = now would like to welcome you in becoming a tester and/or contributor!=20= You can find more information at xen-master.org, to install and = configure XenMaster. If you'd like to help and have experience in = developing Java and/or Javascript, load the source in your favorite IDE = and have at it! If you have any questions at all, we'll be happy to answer them here or = through GitHub. We hope to welcome you in using XenMaster! Jorgen Evens Wannes De Smet XenMaster=20= --Apple-Mail=_FB3F3A77-CC5D-44D0-BAE8-13045D16074C Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=us-ascii We're happy to announce XenMaster, which has = the ambitious goalto become the de facto frontend for Xen with = XCP.

We've had the opportunity to present our = project to some of the Xen/XCP developers and now it's time to announce = the project to a larger public.
XenMaster, in short, is a HTML5 = frontend coupled to a Java backend delivering a rich UI for Xen, = targeted at end users.
At the moment, one is able to successfully add = NFS ISO repositories and iSCSI/NFS storage repositories (iSCSI currently = only works on XenServer 5.6), create a HVM VM and control it via a VNC = shell.

Development thus far has been carried out by = Jorgen Evens, frontend lead and Wannes De Smet, project lead and backend = developer. Of course, we now would like to welcome you in becoming a = tester and/or contributor!
You can find more information at = xen-master.orginstall and configure = XenMaster. If you'd like to help and have experience in = developing Java and/or Javascript, load the source in your favorite IDE = and have at it!

If you have any questions at all, = we'll be happy to answer them here or through GitHub.

Wannes De Smet
XenMaster = = --Apple-Mail=_FB3F3A77-CC5D-44D0-BAE8-13045D16074C-- --===============4516901266380225288== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ xen-api mailing list xen-api@lists.xensource.com http://lists.xensource.com/mailman/listinfo/xen-api --===============4516901266380225288==-- From xen-api-bounces@lists.xensource.com Sun Feb 12 12:37:07 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sun, 12 Feb 2012 12:37: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 1RwYfp-0004Nr-D4; Sun, 12 Feb 2012 12:36:57 +0000 Received: from mail174.messagelabs.com ([85.158.138.51]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1RwYfn-0004Ni-Ul; Sun, 12 Feb 2012 12:36:56 +0000 X-Env-Sender: brainy@gmail.com X-Msg-Ref: server-7.tower-174.messagelabs.com!1329050207!8804050!1 X-Originating-IP: [209.85.220.171] X-SpamReason: No, hits=0.9 required=7.0 tests=HTML_60_70,HTML_MESSAGE, MAILTO_TO_SPAM_ADDR,ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Version: 6.5.5; banners=-,-,- X-VirusChecked: Checked Received: (qmail 32674 invoked from network); 12 Feb 2012 12:36:48 -0000 Received: from mail-vx0-f171.google.com (HELO mail-vx0-f171.google.com) (209.85.220.171) by server-7.tower-174.messagelabs.com with RC4-SHA encrypted SMTP; 12 Feb 2012 12:36:48 -0000 Received: by vcbfo11 with SMTP id fo11so9882850vcb.30 for ; Sun, 12 Feb 2012 04:36:47 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=qEQ+7GGC3Tb89GYFauWpkTmuVjR97vFbMWBAfl18n/Q=; b=uii/MEfs0vywfP6z6EpwxVIaosz39wa+h+Je7kL/91y1l6Oz6NaB2o0iuRh9Pd9QSj 83ziU9/DGUw8wyppO136j11Jhdr1riGiD9ZJ14zlmpHha7Faq+WeMbEMgr45jOj16VkH xogDCod6WFiIGHFM7TEglHM75SvQ9VambKQnw= MIME-Version: 1.0 Received: by 10.52.29.17 with SMTP id f17mr5588790vdh.126.1329050206861; Sun, 12 Feb 2012 04:36:46 -0800 (PST) Received: by 10.220.213.201 with HTTP; Sun, 12 Feb 2012 04:36:46 -0800 (PST) In-Reply-To: References: Date: Sun, 12 Feb 2012 12:36:46 +0000 X-Google-Sender-Auth: 5zjhoxKJLVTaO3iG8Hc5DDIzyV8 Message-ID: From: "msgbox450@gmail.com" To: Wannes De Smet Cc: xen-users@lists.xensource.com, xen-api@lists.xensource.com Subject: Re: [Xen-API] Announcing XenMaster X-BeenThere: xen-api@lists.xensource.com X-Mailman-Version: 2.1.13 Precedence: list List-Id: Discussion of API issues surrounding Xen List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============0595927266463976029==" Sender: xen-api-bounces@lists.xensource.com Errors-To: xen-api-bounces@lists.xensource.com --===============0595927266463976029== Content-Type: multipart/alternative; boundary=20cf307c9eba77fb6404b8c39dd5 --20cf307c9eba77fb6404b8c39dd5 Content-Type: text/plain; charset=ISO-8859-1 This looks nice although I am not really sure I understand the angle you're coming from here... You're announcing a GUI, but the site is just a wiki with text and a bit of bashing vmware and windows but no screenshots of nice GUI designs or explanations of how yours will be better... In my view, XAPI already has a decent Windows GUI in the form of XenCenter, the bit we're missing is a really good cross-platform and fully open gui base. Java isn't a great choice for that due to the anti-java feelings around the community and GPL is also not a great choice given its viral nature. You seem to have a misunderstanding of the GPL in your wiki too when you say "the GPLv3 requires that everyone who improves our project, makes his work available publicly". It doesn't - not if people just use it in house. People can make their own improvements all they like without releasing it. What the GPL actually means for anyone who wants to make a rebranded release of it for their clients or customers though, is that they will have to maintain a full archive of all the source going back all the versions, including all their little service-specific tweaks and then make it readily available to whoever wants it on request. In my view that just adds a lot of extra work and security considerations to any project that wants to use it. It also means no-one can add anything clever with it that gives them a competitive edge without releasing the source, so in that case they'll probably choose to build a GUI from scratch rather than contribute anything. If we want a free, uncustomised proprietary windows GUI like VSphere Client then XenCenter does a great job. If we want a fully open, cross platform GUI that we can rebrand and customised for our own service offerings then we should be looking at something AJAX based with a BSD/MIT style license. Just my 10 cents ;) On 11 February 2012 19:14, Wannes De Smet wrote: > *We're happy to announce XenMaster, which has the ambitious goal to > become the de facto frontend for Xen with XCP. > > We've had the opportunity to present our project to some of the Xen/XCP > developers and now it's time to announce the project to a larger public. > XenMaster, in short, is a HTML5 frontend coupled to a Java backend > delivering a rich UI for Xen, targeted at end users. > At the moment, one is able to successfully add NFS ISO repositories and > iSCSI/NFS storage repositories (iSCSI currently only works on XenServer > 5.6), create a HVM VM and control it via a VNC shell. > > Development thus far has been carried out by Jorgen Evens, frontend lead > and Wannes De Smet, project lead and backend developer. Of course, we now > would like to welcome you in becoming a tester and/or contributor! > You can find more information at xen-master.org, to install and configure > XenMaster . If you'd like to > help and have experience in developing Java and/or Javascript, load the > source in your favorite IDE and have at it! > > If you have any questions at all, we'll be happy to answer them here or > through GitHub. > > We hope to welcome you in using XenMaster! > Jorgen Evens > Wannes De Smet > XenMaster * > > _______________________________________________ > xen-api mailing list > xen-api@lists.xensource.com > http://lists.xensource.com/mailman/listinfo/xen-api > > --20cf307c9eba77fb6404b8c39dd5 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable This looks nice although I am not really sure I understand the angle you= 9;re coming from here...

You're announcing a GUI, bu= t the site is just a wiki with text and a bit of bashing vmware and windows= but no screenshots of nice GUI designs or explanations of how yours will b= e better...=A0

In my view, XAPI already has a decent Windows GUI in the form of XenCe= nter, the bit we're missing is a really good cross-platform and fully o= pen gui base. Java isn't a great choice for that due to the anti-java f= eelings around the community and GPL is also not a great choice given its v= iral nature.

You seem to have a misunderstanding of the GPL in your = wiki too when you say "the GPLv3 require= s that everyone who improves our project, makes his work available publicly= ". =A0It doesn't - not if people just use it in house. People can = make their own improvements all they like without releasing it.

What the GPL actually means for anyone w= ho wants to make a rebranded release of it for their clients or customers t= hough, is that they will have to maintain a full archive of all the source = going back all the versions, including all their little service-specific tw= eaks and then make it readily available to whoever wants it on request.=A0<= /span>

In my view that just adds a lot of extra= work and security considerations to any project that wants to use it. It a= lso means no-one can add anything clever with it that gives them a competit= ive edge without releasing the source, so in that case they'll probably= choose to build a GUI from scratch rather than contribute anything.=

If we want a free, uncustomised=A0proprietary windows GUI l= ike VSphere Client then XenCenter does a great job. If we want a fully open= , cross platform GUI that we can rebrand and customised for our own service= offerings then we should be looking at something AJAX based with a BSD/MIT= style license.=A0

= Just my 10 cents ;)<= /div>

On 11 February 2012 19:14, Wannes De Sm= et <wannes321@g= mail.com> wrote:

<= font face=3D"Arial" style=3D"font-size:15px">We're ha= ppy to announce XenMaster, which has the ambitious goal to become the de facto frontend for Xen with XCP.

We've had the opportunit= y to present our project to some of the Xen/XCP developers and now it's= time to announce the project to a larger public.
XenMaster, in short, is a HTML5 frontend coupled to a Jav= a backend delivering a rich UI for Xen, targeted at end users.
At the moment, one is able to successfully add NFS ISO re= positories and iSCSI/NFS storage repositories (iSCSI currently only works o= n XenServer 5.6), create a HVM VM and control it via a VNC shell.
Development thus far has bee= n carried out by Jorgen Evens, frontend lead and Wannes De Smet, project le= ad and backend developer. Of course, we now would like to welcome you in be= coming a tester and/or contributor!
You can find more information at xen-master.org, to install and configu= re XenMaster. If you'd like to help and ha= ve experience in developing Java and/or Javascript, load the source in your= favorite IDE and have at it!

If you have any questions at= all, we'll be happy to answer them here or through GitHub.

We hope to welcome you in us= ing XenMaster!
Jorgen Evens
Wannes De Smet
XenMaster

_______________________________________________
xen-api mailing list
xen-api@lists.xensource.com<= /a>
http://lists.xensource.com/mailman/listinfo/xen-api

--20cf307c9eba77fb6404b8c39dd5-- --===============0595927266463976029== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ xen-api mailing list xen-api@lists.xensource.com http://lists.xensource.com/mailman/listinfo/xen-api --===============0595927266463976029==-- From xen-api-bounces@lists.xensource.com Sun Feb 12 12:37:07 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sun, 12 Feb 2012 12:37: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 1RwYfp-0004Nr-D4; Sun, 12 Feb 2012 12:36:57 +0000 Received: from mail174.messagelabs.com ([85.158.138.51]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1RwYfn-0004Ni-Ul; Sun, 12 Feb 2012 12:36:56 +0000 X-Env-Sender: brainy@gmail.com X-Msg-Ref: server-7.tower-174.messagelabs.com!1329050207!8804050!1 X-Originating-IP: [209.85.220.171] X-SpamReason: No, hits=0.9 required=7.0 tests=HTML_60_70,HTML_MESSAGE, MAILTO_TO_SPAM_ADDR,ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Version: 6.5.5; banners=-,-,- X-VirusChecked: Checked Received: (qmail 32674 invoked from network); 12 Feb 2012 12:36:48 -0000 Received: from mail-vx0-f171.google.com (HELO mail-vx0-f171.google.com) (209.85.220.171) by server-7.tower-174.messagelabs.com with RC4-SHA encrypted SMTP; 12 Feb 2012 12:36:48 -0000 Received: by vcbfo11 with SMTP id fo11so9882850vcb.30 for ; Sun, 12 Feb 2012 04:36:47 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=qEQ+7GGC3Tb89GYFauWpkTmuVjR97vFbMWBAfl18n/Q=; b=uii/MEfs0vywfP6z6EpwxVIaosz39wa+h+Je7kL/91y1l6Oz6NaB2o0iuRh9Pd9QSj 83ziU9/DGUw8wyppO136j11Jhdr1riGiD9ZJ14zlmpHha7Faq+WeMbEMgr45jOj16VkH xogDCod6WFiIGHFM7TEglHM75SvQ9VambKQnw= MIME-Version: 1.0 Received: by 10.52.29.17 with SMTP id f17mr5588790vdh.126.1329050206861; Sun, 12 Feb 2012 04:36:46 -0800 (PST) Received: by 10.220.213.201 with HTTP; Sun, 12 Feb 2012 04:36:46 -0800 (PST) In-Reply-To: References: Date: Sun, 12 Feb 2012 12:36:46 +0000 X-Google-Sender-Auth: 5zjhoxKJLVTaO3iG8Hc5DDIzyV8 Message-ID: From: "msgbox450@gmail.com" To: Wannes De Smet Cc: xen-users@lists.xensource.com, xen-api@lists.xensource.com Subject: Re: [Xen-API] Announcing XenMaster X-BeenThere: xen-api@lists.xensource.com X-Mailman-Version: 2.1.13 Precedence: list List-Id: Discussion of API issues surrounding Xen List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============0595927266463976029==" Sender: xen-api-bounces@lists.xensource.com Errors-To: xen-api-bounces@lists.xensource.com --===============0595927266463976029== Content-Type: multipart/alternative; boundary=20cf307c9eba77fb6404b8c39dd5 --20cf307c9eba77fb6404b8c39dd5 Content-Type: text/plain; charset=ISO-8859-1 This looks nice although I am not really sure I understand the angle you're coming from here... You're announcing a GUI, but the site is just a wiki with text and a bit of bashing vmware and windows but no screenshots of nice GUI designs or explanations of how yours will be better... In my view, XAPI already has a decent Windows GUI in the form of XenCenter, the bit we're missing is a really good cross-platform and fully open gui base. Java isn't a great choice for that due to the anti-java feelings around the community and GPL is also not a great choice given its viral nature. You seem to have a misunderstanding of the GPL in your wiki too when you say "the GPLv3 requires that everyone who improves our project, makes his work available publicly". It doesn't - not if people just use it in house. People can make their own improvements all they like without releasing it. What the GPL actually means for anyone who wants to make a rebranded release of it for their clients or customers though, is that they will have to maintain a full archive of all the source going back all the versions, including all their little service-specific tweaks and then make it readily available to whoever wants it on request. In my view that just adds a lot of extra work and security considerations to any project that wants to use it. It also means no-one can add anything clever with it that gives them a competitive edge without releasing the source, so in that case they'll probably choose to build a GUI from scratch rather than contribute anything. If we want a free, uncustomised proprietary windows GUI like VSphere Client then XenCenter does a great job. If we want a fully open, cross platform GUI that we can rebrand and customised for our own service offerings then we should be looking at something AJAX based with a BSD/MIT style license. Just my 10 cents ;) On 11 February 2012 19:14, Wannes De Smet wrote: > *We're happy to announce XenMaster, which has the ambitious goal to > become the de facto frontend for Xen with XCP. > > We've had the opportunity to present our project to some of the Xen/XCP > developers and now it's time to announce the project to a larger public. > XenMaster, in short, is a HTML5 frontend coupled to a Java backend > delivering a rich UI for Xen, targeted at end users. > At the moment, one is able to successfully add NFS ISO repositories and > iSCSI/NFS storage repositories (iSCSI currently only works on XenServer > 5.6), create a HVM VM and control it via a VNC shell. > > Development thus far has been carried out by Jorgen Evens, frontend lead > and Wannes De Smet, project lead and backend developer. Of course, we now > would like to welcome you in becoming a tester and/or contributor! > You can find more information at xen-master.org, to install and configure > XenMaster . If you'd like to > help and have experience in developing Java and/or Javascript, load the > source in your favorite IDE and have at it! > > If you have any questions at all, we'll be happy to answer them here or > through GitHub. > > We hope to welcome you in using XenMaster! > Jorgen Evens > Wannes De Smet > XenMaster * > > _______________________________________________ > xen-api mailing list > xen-api@lists.xensource.com > http://lists.xensource.com/mailman/listinfo/xen-api > > --20cf307c9eba77fb6404b8c39dd5 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable This looks nice although I am not really sure I understand the angle you= 9;re coming from here...

You're announcing a GUI, bu= t the site is just a wiki with text and a bit of bashing vmware and windows= but no screenshots of nice GUI designs or explanations of how yours will b= e better...=A0

= Just my 10 cents ;)<= /div>

On 11 February 2012 19:14, Wannes De Sm= et <wannes321@g= mail.com> wrote:

<= font face=3D"Arial" style=3D"font-size:15px">We're ha= ppy to announce XenMaster, which has the ambitious goal to become the de facto frontend for Xen with XCP.

We've had the opportunit= y to present our project to some of the Xen/XCP developers and now it's= time to announce the project to a larger public.
XenMaster, in short, is a HTML5 frontend coupled to a Jav= a backend delivering a rich UI for Xen, targeted at end users.
At the moment, one is able to successfully add NFS ISO re= positories and iSCSI/NFS storage repositories (iSCSI currently only works o= n XenServer 5.6), create a HVM VM and control it via a VNC shell.
Development thus far has bee= n carried out by Jorgen Evens, frontend lead and Wannes De Smet, project le= ad and backend developer. Of course, we now would like to welcome you in be= coming a tester and/or contributor!
You can find more information at xen-master.org, to install and configu= re XenMaster. If you'd like to help and ha= ve experience in developing Java and/or Javascript, load the source in your= favorite IDE and have at it!

If you have any questions at= all, we'll be happy to answer them here or through GitHub.

We hope to welcome you in us= ing XenMaster!
Jorgen Evens
Wannes De Smet
XenMaster

_______________________________________________
xen-api mailing list
xen-api@lists.xensource.com<= /a>
http://lists.xensource.com/mailman/listinfo/xen-api

--20cf307c9eba77fb6404b8c39dd5-- --===============0595927266463976029== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ xen-api mailing list xen-api@lists.xensource.com http://lists.xensource.com/mailman/listinfo/xen-api --===============0595927266463976029==-- From xen-api-bounces@lists.xensource.com Sun Feb 12 13:34:36 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sun, 12 Feb 2012 13:34: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 1RwZZT-0005Ze-0X; Sun, 12 Feb 2012 13:34:27 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1RwZZR-0005ZZ-Dw for xen-api@lists.xensource.com; Sun, 12 Feb 2012 13:34:25 +0000 Received: from [85.158.139.83:12276] by server-9.bemta-5.messagelabs.com id 8C/52-23757-0EFB73F4; Sun, 12 Feb 2012 13:34:24 +0000 X-Env-Sender: wannes321@gmail.com X-Msg-Ref: server-7.tower-182.messagelabs.com!1329053662!14646620!1 X-Originating-IP: [209.85.212.171] X-SpamReason: No, hits=0.7 required=7.0 tests=HTML_50_60,HTML_MESSAGE, MAILTO_TO_SPAM_ADDR,ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Version: 6.5.5; banners=-,-,- X-VirusChecked: Checked Received: (qmail 12106 invoked from network); 12 Feb 2012 13:34:23 -0000 Received: from mail-wi0-f171.google.com (HELO mail-wi0-f171.google.com) (209.85.212.171) by server-7.tower-182.messagelabs.com with RC4-SHA encrypted SMTP; 12 Feb 2012 13:34:23 -0000 Received: by wibhm2 with SMTP id hm2so12659535wib.30 for ; Sun, 12 Feb 2012 05:34:22 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=subject:mime-version:content-type:from:in-reply-to:date:cc :message-id:references:to:x-mailer; bh=mvzWiVwrQM1QG71HmiHKGSxAcZNgp0W4PilXII21c8I=; b=cu2cAAVUIBaJQ6JyGAukhFHnOUQ/qKvZt8M78KH7gn7xRu1Dx/frePf1A234qwtAgz tUpaHlaU7eMI6bE9gGf1DcTSsqkuFVx3pn3kGRABFwEUHA63EABHFh1II9cU1YeFe103 baD42TJhV47+dR4sPYRwwnIoDVeKkK+dNXxZ0= Received: by 10.180.95.105 with SMTP id dj9mr18945522wib.18.1329053662294; Sun, 12 Feb 2012 05:34:22 -0800 (PST) Received: from banana.w-gr.net (202.49-241-81.adsl-dyn.isp.belgacom.be. [81.241.49.202]) by mx.google.com with ESMTPS id dw7sm15227998wib.4.2012.02.12.05.34.20 (version=TLSv1/SSLv3 cipher=OTHER); Sun, 12 Feb 2012 05:34:21 -0800 (PST) Mime-Version: 1.0 (Apple Message framework v1257) From: Wannes De Smet In-Reply-To: Date: Sun, 12 Feb 2012 14:34:18 +0100 Message-Id: References: To: "msgbox450@gmail.com" X-Mailer: Apple Mail (2.1257) Cc: xen-api@lists.xensource.com Subject: Re: [Xen-API] Announcing XenMaster X-BeenThere: xen-api@lists.xensource.com X-Mailman-Version: 2.1.13 Precedence: list List-Id: Discussion of API issues surrounding Xen List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============8933912776584421086==" Sender: xen-api-bounces@lists.xensource.com Errors-To: xen-api-bounces@lists.xensource.com --===============8933912776584421086== Content-Type: multipart/alternative; boundary="Apple-Mail=_B0AD4611-5664-4B01-BE1B-C65B10464BF9" --Apple-Mail=_B0AD4611-5664-4B01-BE1B-C65B10464BF9 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=windows-1252 On 12 Feb 2012, at 13:36, msgbox450@gmail.com wrote: > This looks nice although I am not really sure I understand the angle = you're coming from here... >=20 > You're announcing a GUI, but the site is just a wiki with text and a = bit of bashing vmware and windows but no screenshots of nice GUI designs = or explanations of how yours will be better=85=20 I should've noted that this was merely an announcement to let everyone = know we're alive and to give it a shot, we're not even close to a 1.0 = release. However your point is valid and we've added it on our TODO = list. > In my view, XAPI already has a decent Windows GUI in the form of = XenCenter, the bit we're missing is a really good cross-platform and = fully open gui base. Java isn't a great choice for that due to the = anti-java feelings around the community and GPL is also not a great = choice given its viral nature. >=20 > You seem to have a misunderstanding of the GPL in your wiki too when = you say "the GPLv3 requires that everyone who improves our project, = makes his work available publicly". It doesn't - not if people just use = it in house. People can make their own improvements all they like = without releasing it. > What the GPL actually means for anyone who wants to make a rebranded = release of it for their clients or customers though, is that they will = have to maintain a full archive of all the source going back all the = versions, including all their little service-specific tweaks and then = make it readily available to whoever wants it on request.=20 Thanks for pointing that out. > In my view that just adds a lot of extra work and security = considerations to any project that wants to use it. It also means no-one = can add anything clever with it that gives them a competitive edge = without releasing the source, so in that case they'll probably choose to = build a GUI from scratch rather than contribute anything. Here's the thing: we don't want people to not release the source. This = might make sense from a money perspective, but we're true believers in = the open source way. You can be competitive as a service provider on = many other levels; after all, we're just one piece of the machine. Our = main ambition is to make this a single implementation that is the best = anyone can get, instead of some scattered implementations only to give a = competitive edge. > If we want a free, uncustomised proprietary windows GUI like VSphere = Client then XenCenter does a great job. If we want a fully open, cross = platform GUI that we can rebrand and customised for our own service = offerings then we should be looking at something AJAX based with a = BSD/MIT style license.=20 >=20 The rebranding part sounds rather odd to me: you could stick another = logo on top, sure, but we want to know about people's customizations. At = this moment we're happy we can boot an HVM domain but in the long term = we'd like to see this grow to being the best (FOSS) management tool for = XCP.=20 To achieve that goal we need every contribution we can get (especially = from those running this in production). This way the GPL makes a bit = more sense, as you said people need to maintain their modifications on = file, so they might just as well be good open source citizens and = contribute them. > Just my 10 cents ;) Appreciated, W PS: I didn't CC xen-users, I don't want to crosspost too much. >=20 > On 11 February 2012 19:14, Wannes De Smet wrote: > We're happy to announce XenMaster, which has the ambitious goal to = become the de facto frontend for Xen with XCP. >=20 > We've had the opportunity to present our project to some of the = Xen/XCP developers and now it's time to announce the project to a larger = public. > XenMaster, in short, is a HTML5 frontend coupled to a Java backend = delivering a rich UI for Xen, targeted at end users. > At the moment, one is able to successfully add NFS ISO repositories = and iSCSI/NFS storage repositories (iSCSI currently only works on = XenServer 5.6), create a HVM VM and control it via a VNC shell.=20 >=20 > Development thus far has been carried out by Jorgen Evens, frontend = lead and Wannes De Smet, project lead and backend developer. Of course, = we now would like to welcome you in becoming a tester and/or = contributor!=20 > You can find more information at xen-master.org, to install and = configure XenMaster. If you'd like to help and have experience in = developing Java and/or Javascript, load the source in your favorite IDE = and have at it! >=20 > If you have any questions at all, we'll be happy to answer them here = or through GitHub. >=20 > We hope to welcome you in using XenMaster! > Jorgen Evens > Wannes De Smet > XenMaster=20 >=20 > _______________________________________________ > xen-api mailing list > xen-api@lists.xensource.com > http://lists.xensource.com/mailman/listinfo/xen-api >=20 >=20 --Apple-Mail=_B0AD4611-5664-4B01-BE1B-C65B10464BF9 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=windows-1252 msgbox450@gmail.com = wrote:

This looks nice although I am not really sure I understand = the angle you're coming from here...

You're = announcing a GUI, but the site is just a wiki with text and a bit of = bashing vmware and windows but no screenshots of nice GUI designs or = explanations of how yours will be = better=85

I should've noted = that this was merely an announcement to let everyone know we're alive = and to give it a shot, we're not even close to a 1.0 release. However = your point is valid and we've added it on our TODO = list.

In my view, XAPI already has a decent Windows GUI in the form of = XenCenter, the bit we're missing is a really good cross-platform and = fully open gui base. Java isn't a great choice for that due to the = anti-java feelings around the community and GPL is also not a great = choice given its viral nature.

You seem to have a misunderstanding of the GPL in = your wiki too when you say "the GPLv3 requires that everyone who improves = our project, makes his work available publicly". It doesn't - not = if people just use it in house. People can make their own improvements = all they like without releasing it.

What the GPL actually means for anyone who = wants to make a rebranded release of it for their clients or customers = though, is that they will have to maintain a full archive of all the = source going back all the versions, including all their little = service-specific tweaks and then make it readily available to whoever = wants it on = request.

Thanks for = pointing that out.

In my view that just adds a lot of extra work = and security considerations to any project that wants to use it. It also = means no-one can add anything clever with it that gives them a = competitive edge without releasing the source, so in that case they'll = probably choose to build a GUI from scratch rather than contribute = anything.

Here's the thing: = we don't want people to not release the source. This might make sense = from a money perspective, but we're true believers in the open source = way. You can be competitive as a service provider on many other levels; = after all, we're just one piece of the machine. Our main ambition is to = make this a single implementation that is the best anyone can get, = instead of some scattered implementations only to give a competitive = edge.

If we want a free, = uncustomised proprietary windows GUI like VSphere Client then = XenCenter does a great job. If we want a fully open, cross platform GUI = that we can rebrand and customised for our own service offerings then we = should be looking at something AJAX based with a BSD/MIT style = license.

The rebranding part sounds rather odd to me: you could stick another = logo on top, sure, but we want to know about people's customizations. At = this moment we're happy we can boot an HVM domain but in the long term = we'd like to see this grow to being the best (FOSS) management tool for = XCP.

To achieve that goal we need every contribution we = can get (especially from those running this in production). This way the = GPL makes a bit more sense, as you said people need to maintain their = modifications on file, so they might just as well be good open source = citizens and contribute them.

Just my 10 cents = ;)

Appreciated,=

PS: I didn't CC xen-users, I don't want = to crosspost too much.

On 11 February 2012 19:14, Wannes De = Smet <wannes321@gmail.com> = wrote:

We're happy to announce XenMaster, which has the ambitious = goal = to become the de facto frontend for Xen with = XCP.

We've had the opportunity to present our project to some = of the Xen/XCP developers and now it's time to announce the project to a = larger public.
XenMaster, in short, is a HTML5 frontend coupled to a Java = backend delivering a rich UI for Xen, targeted at end users.
At the moment, one is able to successfully add NFS ISO = repositories and iSCSI/NFS storage repositories (iSCSI currently only = works on XenServer 5.6), create a HVM VM and control it via a VNC shell. =

Development thus far has been carried out by Jorgen Evens, = frontend lead and Wannes De Smet, project lead and backend developer. Of = course, we now would like to welcome you in becoming a tester and/or = contributor!
You can find more information at xen-master.org, to install and configure = XenMaster. If you'd like to help and have experience in developing = Java and/or Javascript, load the source in your favorite IDE and have at = it!

If you have any questions at all, we'll be happy to answer = them here or through GitHub.

We hope to welcome you in using XenMaster!
Jorgen Evens
Wannes De Smet
XenMaster

_______________________________________________
xen-api mailing list
xen-api@lists.xensource.com
http://lists.xensource.com/mailman/listinfo/xen-api<= br>

= --Apple-Mail=_B0AD4611-5664-4B01-BE1B-C65B10464BF9-- --===============8933912776584421086== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ xen-api mailing list xen-api@lists.xensource.com http://lists.xensource.com/mailman/listinfo/xen-api --===============8933912776584421086==-- From xen-api-bounces@lists.xensource.com Sun Feb 12 13:34:36 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sun, 12 Feb 2012 13:34: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 1RwZZT-0005Ze-0X; Sun, 12 Feb 2012 13:34:27 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1RwZZR-0005ZZ-Dw for xen-api@lists.xensource.com; Sun, 12 Feb 2012 13:34:25 +0000 Received: from [85.158.139.83:12276] by server-9.bemta-5.messagelabs.com id 8C/52-23757-0EFB73F4; Sun, 12 Feb 2012 13:34:24 +0000 X-Env-Sender: wannes321@gmail.com X-Msg-Ref: server-7.tower-182.messagelabs.com!1329053662!14646620!1 X-Originating-IP: [209.85.212.171] X-SpamReason: No, hits=0.7 required=7.0 tests=HTML_50_60,HTML_MESSAGE, MAILTO_TO_SPAM_ADDR,ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Version: 6.5.5; banners=-,-,- X-VirusChecked: Checked Received: (qmail 12106 invoked from network); 12 Feb 2012 13:34:23 -0000 Received: from mail-wi0-f171.google.com (HELO mail-wi0-f171.google.com) (209.85.212.171) by server-7.tower-182.messagelabs.com with RC4-SHA encrypted SMTP; 12 Feb 2012 13:34:23 -0000 Received: by wibhm2 with SMTP id hm2so12659535wib.30 for ; Sun, 12 Feb 2012 05:34:22 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=subject:mime-version:content-type:from:in-reply-to:date:cc :message-id:references:to:x-mailer; bh=mvzWiVwrQM1QG71HmiHKGSxAcZNgp0W4PilXII21c8I=; b=cu2cAAVUIBaJQ6JyGAukhFHnOUQ/qKvZt8M78KH7gn7xRu1Dx/frePf1A234qwtAgz tUpaHlaU7eMI6bE9gGf1DcTSsqkuFVx3pn3kGRABFwEUHA63EABHFh1II9cU1YeFe103 baD42TJhV47+dR4sPYRwwnIoDVeKkK+dNXxZ0= Received: by 10.180.95.105 with SMTP id dj9mr18945522wib.18.1329053662294; Sun, 12 Feb 2012 05:34:22 -0800 (PST) Received: from banana.w-gr.net (202.49-241-81.adsl-dyn.isp.belgacom.be. [81.241.49.202]) by mx.google.com with ESMTPS id dw7sm15227998wib.4.2012.02.12.05.34.20 (version=TLSv1/SSLv3 cipher=OTHER); Sun, 12 Feb 2012 05:34:21 -0800 (PST) Mime-Version: 1.0 (Apple Message framework v1257) From: Wannes De Smet In-Reply-To: Date: Sun, 12 Feb 2012 14:34:18 +0100 Message-Id: References: To: "msgbox450@gmail.com" X-Mailer: Apple Mail (2.1257) Cc: xen-api@lists.xensource.com Subject: Re: [Xen-API] Announcing XenMaster X-BeenThere: xen-api@lists.xensource.com X-Mailman-Version: 2.1.13 Precedence: list List-Id: Discussion of API issues surrounding Xen List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============8933912776584421086==" Sender: xen-api-bounces@lists.xensource.com Errors-To: xen-api-bounces@lists.xensource.com --===============8933912776584421086== Content-Type: multipart/alternative; boundary="Apple-Mail=_B0AD4611-5664-4B01-BE1B-C65B10464BF9" --Apple-Mail=_B0AD4611-5664-4B01-BE1B-C65B10464BF9 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=windows-1252 On 12 Feb 2012, at 13:36, msgbox450@gmail.com wrote: > This looks nice although I am not really sure I understand the angle = you're coming from here... >=20 > You're announcing a GUI, but the site is just a wiki with text and a = bit of bashing vmware and windows but no screenshots of nice GUI designs = or explanations of how yours will be better=85=20 I should've noted that this was merely an announcement to let everyone = know we're alive and to give it a shot, we're not even close to a 1.0 = release. However your point is valid and we've added it on our TODO = list. > In my view, XAPI already has a decent Windows GUI in the form of = XenCenter, the bit we're missing is a really good cross-platform and = fully open gui base. Java isn't a great choice for that due to the = anti-java feelings around the community and GPL is also not a great = choice given its viral nature. >=20 > You seem to have a misunderstanding of the GPL in your wiki too when = you say "the GPLv3 requires that everyone who improves our project, = makes his work available publicly". It doesn't - not if people just use = it in house. People can make their own improvements all they like = without releasing it. > What the GPL actually means for anyone who wants to make a rebranded = release of it for their clients or customers though, is that they will = have to maintain a full archive of all the source going back all the = versions, including all their little service-specific tweaks and then = make it readily available to whoever wants it on request.=20 Thanks for pointing that out. > In my view that just adds a lot of extra work and security = considerations to any project that wants to use it. It also means no-one = can add anything clever with it that gives them a competitive edge = without releasing the source, so in that case they'll probably choose to = build a GUI from scratch rather than contribute anything. Here's the thing: we don't want people to not release the source. This = might make sense from a money perspective, but we're true believers in = the open source way. You can be competitive as a service provider on = many other levels; after all, we're just one piece of the machine. Our = main ambition is to make this a single implementation that is the best = anyone can get, instead of some scattered implementations only to give a = competitive edge. > If we want a free, uncustomised proprietary windows GUI like VSphere = Client then XenCenter does a great job. If we want a fully open, cross = platform GUI that we can rebrand and customised for our own service = offerings then we should be looking at something AJAX based with a = BSD/MIT style license.=20 >=20 The rebranding part sounds rather odd to me: you could stick another = logo on top, sure, but we want to know about people's customizations. At = this moment we're happy we can boot an HVM domain but in the long term = we'd like to see this grow to being the best (FOSS) management tool for = XCP.=20 To achieve that goal we need every contribution we can get (especially = from those running this in production). This way the GPL makes a bit = more sense, as you said people need to maintain their modifications on = file, so they might just as well be good open source citizens and = contribute them. > Just my 10 cents ;) Appreciated, W PS: I didn't CC xen-users, I don't want to crosspost too much. >=20 > On 11 February 2012 19:14, Wannes De Smet wrote: > We're happy to announce XenMaster, which has the ambitious goal to = become the de facto frontend for Xen with XCP. >=20 > We've had the opportunity to present our project to some of the = Xen/XCP developers and now it's time to announce the project to a larger = public. > XenMaster, in short, is a HTML5 frontend coupled to a Java backend = delivering a rich UI for Xen, targeted at end users. > At the moment, one is able to successfully add NFS ISO repositories = and iSCSI/NFS storage repositories (iSCSI currently only works on = XenServer 5.6), create a HVM VM and control it via a VNC shell.=20 >=20 > Development thus far has been carried out by Jorgen Evens, frontend = lead and Wannes De Smet, project lead and backend developer. Of course, = we now would like to welcome you in becoming a tester and/or = contributor!=20 > You can find more information at xen-master.org, to install and = configure XenMaster. If you'd like to help and have experience in = developing Java and/or Javascript, load the source in your favorite IDE = and have at it! >=20 > If you have any questions at all, we'll be happy to answer them here = or through GitHub. >=20 > We hope to welcome you in using XenMaster! > Jorgen Evens > Wannes De Smet > XenMaster=20 >=20 > _______________________________________________ > xen-api mailing list > xen-api@lists.xensource.com > http://lists.xensource.com/mailman/listinfo/xen-api >=20 >=20 --Apple-Mail=_B0AD4611-5664-4B01-BE1B-C65B10464BF9 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=windows-1252 msgbox450@gmail.com = wrote:

This looks nice although I am not really sure I understand = the angle you're coming from here...

You're = announcing a GUI, but the site is just a wiki with text and a bit of = bashing vmware and windows but no screenshots of nice GUI designs or = explanations of how yours will be = better=85

In my view, XAPI already has a decent Windows GUI in the form of = XenCenter, the bit we're missing is a really good cross-platform and = fully open gui base. Java isn't a great choice for that due to the = anti-java feelings around the community and GPL is also not a great = choice given its viral nature.

You seem to have a misunderstanding of the GPL in = your wiki too when you say "the GPLv3 requires that everyone who improves = our project, makes his work available publicly". It doesn't - not = if people just use it in house. People can make their own improvements = all they like without releasing it.

What the GPL actually means for anyone who = wants to make a rebranded release of it for their clients or customers = though, is that they will have to maintain a full archive of all the = source going back all the versions, including all their little = service-specific tweaks and then make it readily available to whoever = wants it on = request.

Thanks for = pointing that out.

In my view that just adds a lot of extra work = and security considerations to any project that wants to use it. It also = means no-one can add anything clever with it that gives them a = competitive edge without releasing the source, so in that case they'll = probably choose to build a GUI from scratch rather than contribute = anything.

If we want a free, = uncustomised proprietary windows GUI like VSphere Client then = XenCenter does a great job. If we want a fully open, cross platform GUI = that we can rebrand and customised for our own service offerings then we = should be looking at something AJAX based with a BSD/MIT style = license.

Just my 10 cents = ;)

Appreciated,=

PS: I didn't CC xen-users, I don't want = to crosspost too much.

On 11 February 2012 19:14, Wannes De = Smet <wannes321@gmail.com> = wrote:

We're happy to announce XenMaster, which has the ambitious = goal = to become the de facto frontend for Xen with = XCP.

We've had the opportunity to present our project to some = of the Xen/XCP developers and now it's time to announce the project to a = larger public.
XenMaster, in short, is a HTML5 frontend coupled to a Java = backend delivering a rich UI for Xen, targeted at end users.
At the moment, one is able to successfully add NFS ISO = repositories and iSCSI/NFS storage repositories (iSCSI currently only = works on XenServer 5.6), create a HVM VM and control it via a VNC shell. =

Development thus far has been carried out by Jorgen Evens, = frontend lead and Wannes De Smet, project lead and backend developer. Of = course, we now would like to welcome you in becoming a tester and/or = contributor!
You can find more information at xen-master.org, to install and configure = XenMaster. If you'd like to help and have experience in developing = Java and/or Javascript, load the source in your favorite IDE and have at = it!

If you have any questions at all, we'll be happy to answer = them here or through GitHub.

We hope to welcome you in using XenMaster!
Jorgen Evens
Wannes De Smet
XenMaster

_______________________________________________
xen-api mailing list
xen-api@lists.xensource.com
http://lists.xensource.com/mailman/listinfo/xen-api<= br>

If it's going to be just another out-of-the-box vSp= here client clone then there's XenCenter and OpenXenManager already...<= /div>

On 1= 2 February 2012 13:34, Wannes De Smet <wannes321@gmail.com> wrote:

On 12 Feb 2012, at 13:36, msgbox450@gmail.com wrote:

This looks nice altho= ugh I am not really sure I understand the angle you're coming from here= ...

You're announcing a GUI, but the site is j= ust a wiki with text and a bit of bashing vmware and windows but no screens= hots of nice GUI designs or explanations of how yours will be better=85=A0<= /div>

I should've noted that this was merely= an announcement to let everyone know we're alive and to give it a shot= , we're not even close to a 1.0 release. However your point is valid an= d we've added it on our TODO list.

In my view, XAPI already has a decent Windows GUI in the form of XenCe= nter, the bit we're missing is a really good cross-platform and fully o= pen gui base. Java isn't a great choice for that due to the anti-java f= eelings around the community and GPL is also not a great choice given its v= iral nature.

You seem to have a misunderstanding of the GPL in your = wiki too when you say "the GPLv3 requires that everyone who improves our p= roject, makes his work available publicly". =A0It doesn't - not if= people just use it in house. People can make their own improvements all th= ey like without releasing it.

What the GPL actually means for anyone who wants to make a rebranded relea= se of it for their clients or customers though, is that they will have to m= aintain a full archive of all the source going back all the versions, inclu= ding all their little service-specific tweaks and then make it readily avai= lable to whoever wants it on request.=A0

Thanks for pointing that out.
<= div class=3D"im">

In my view that just adds a lot of extra work and security considerations = to any project that wants to use it. It also means no-one can add anything = clever with it that gives them a competitive edge without releasing the sou= rce, so in that case they'll probably choose to build a GUI from scratc= h rather than contribute anything.

Here's the thing: we don't w= ant people to not release the source. This might make sense from a money pe= rspective, but we're true believers in the open source way. You can be = competitive as a service provider on many other levels; after all, we'r= e just one piece of the machine. Our main ambition is to make this a single= implementation that is the best anyone can get, instead of some scattered = implementations only to give a competitive edge.

If we want a fr= ee, uncustomised=A0proprietary windows GUI like VSphere Client then XenCent= er does a great job. If we want a fully open, cross platform GUI that we ca= n rebrand and customised for our own service offerings then we should be lo= oking at something AJAX based with a BSD/MIT style license.=A0

The rebranding part= sounds rather odd to me: you could stick another logo on top, sure, but we= want to know about people's customizations. At this moment we're h= appy we can boot an HVM domain but in the long term we'd like to see th= is grow to being the best (FOSS) management tool for XCP.=A0

To achieve that goal we need every contribution we can get (especially= from those running this in production). This way the GPL makes a bit more = sense, as you said people need to maintain their modifications on file, so = they might just as well be good open source citizens and contribute them.

Just my 10 cents ;)=

Appreciated,
W

PS: I didn't CC xen-users, I don't want to cr= osspost too much.

On 11 February 2012 19:14, Wannes De Sm= et <wannes321@gmail.com> wrote:

<= font face=3D"Arial" style=3D"font-size:15px">We're ha= ppy to announce XenMaster, which has the ambitious goal to become the de facto frontend for Xen with XCP.

We've had the opportunit= y to present our project to some of the Xen/XCP developers and now it's= time to announce the project to a larger public.
XenMaster, in short, is a HTML5 frontend coupled to a Jav= a backend delivering a rich UI for Xen, targeted at end users.
At the moment, one is able to successfully add NFS ISO re= positories and iSCSI/NFS storage repositories (iSCSI currently only works o= n XenServer 5.6), create a HVM VM and control it via a VNC shell.
Development thus far has bee= n carried out by Jorgen Evens, frontend lead and Wannes De Smet, project le= ad and backend developer. Of course, we now would like to welcome you in be= coming a tester and/or contributor!
You can find more information at xen-master.org, to install and configu= re XenMaster. If you'd like to help and ha= ve experience in developing Java and/or Javascript, load the source in your= favorite IDE and have at it!

If you have any questions at= all, we'll be happy to answer them here or through GitHub.

We hope to welcome you in us= ing XenMaster!
Jorgen Evens
Wannes De Smet
XenMaster

_______________________________________________
xen-api mailing list
xen-api@li= sts.xensource.com
http://lists.xensource.com/mailman/listinfo/xen-api

Date: Sun, 12 Feb 2012 21:26:23 +0000 X-Google-Sender-Auth: 4J96q0svyzeFcvhtWcZOZAILiCc Message-ID: From: "msgbox450@gmail.com" To: Wannes De Smet Cc: xen-api@lists.xensource.com Subject: Re: [Xen-API] Announcing XenMaster X-BeenThere: xen-api@lists.xensource.com X-Mailman-Version: 2.1.13 Precedence: list List-Id: Discussion of API issues surrounding Xen List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============0592655977511420842==" Sender: xen-api-bounces@lists.xensource.com Errors-To: xen-api-bounces@lists.xensource.com --===============0592655977511420842== Content-Type: multipart/alternative; boundary=14dae9cdc3fb7f59a404b8cb03b5 --14dae9cdc3fb7f59a404b8cb03b5 Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable You are right that free and open is good. But that's exactly why I don't think GPL is the right choice in this case. Look at Apache for example... just because the Apache license doesn't contain the GPL "viral" clause and other restrictions doesn't mean people don't release their modules for free. The point is, that if they need to keep certain bits closed for security reasons, or they write some extra functionality based upon it that they want to try to sell, they are free to do so. No-one's going to suddenly close the source of the main project and if anyone does make some commercial closed source addons then good luck to them, all it means is that they're got paying customers who will now expect things to work, and if there are any bugs in the core they'll have to fix them and its in their best interests to submit them to the core project anyway rather than maintain diffs and having to switch their solution for someone elses later... Give people full freedom and they'll often choose to contribute. Prescribe to them what they can and cannot do with their own work, and they'll often choose a different base for their projects (such as libvirt in this case). What XAPI is lacking right now is a really nice, clean, free and open GUI framework that people can chop and change to their needs, whether they want a simple web access for starting VMs on their home server or want to incorporate it into their commercial cloud platform offerings with their custom metering and billing. There are loads of commercial cloud platforms and VM management solutions out there, but there's no real standard, because no-one has made a non-proprietary, non-GPL, truly open base system that can be moulded to suit the needs of each geek's particular hardware setup and user base. That's the niche I think. If it's going to be just another out-of-the-box vSphere client clone then there's XenCenter and OpenXenManager already... On 12 February 2012 13:34, Wannes De Smet wrote: > On 12 Feb 2012, at 13:36, msgbox450@gmail.com wrote: > > This looks nice although I am not really sure I understand the angle > you're coming from here... > > You're announcing a GUI, but the site is just a wiki with text and a bit > of bashing vmware and windows but no screenshots of nice GUI designs or > explanations of how yours will be better=85 > > > I should've noted that this was merely an announcement to let everyone > know we're alive and to give it a shot, we're not even close to a 1.0 > release. However your point is valid and we've added it on our TODO list. > > In my view, XAPI already has a decent Windows GUI in the form of > XenCenter, the bit we're missing is a really good cross-platform and full= y > open gui base. Java isn't a great choice for that due to the anti-java > feelings around the community and GPL is also not a great choice given it= s > viral nature. > > > You seem to have a misunderstanding of the GPL in your wiki too when you > say "the GPLv3 requires that everyone who improves our project, makes his > work available publicly". It doesn't - not if people just use it in hous= e. > People can make their own improvements all they like without releasing it= . > > What the GPL actually means for anyone who wants to make a rebranded > release of it for their clients or customers though, is that they will ha= ve > to maintain a full archive of all the source going back all the versions, > including all their little service-specific tweaks and then make it readi= ly > available to whoever wants it on request. > > > Thanks for pointing that out. > > In my view that just adds a lot of extra work and security considerations > to any project that wants to use it. It also means no-one can add anythin= g > clever with it that gives them a competitive edge without releasing the > source, so in that case they'll probably choose to build a GUI from scrat= ch > rather than contribute anything. > > > Here's the thing: we don't want people to not release the source. This > might make sense from a money perspective, but we're true believers in th= e > open source way. You can be competitive as a service provider on many oth= er > levels; after all, we're just one piece of the machine. Our main ambition > is to make this a single implementation that is the best anyone can get, > instead of some scattered implementations only to give a competitive edge= . > > If we want a free, uncustomised proprietary windows GUI like VSphere > Client then XenCenter does a great job. If we want a fully open, cross > platform GUI that we can rebrand and customised for our own service > offerings then we should be looking at something AJAX based with a BSD/MI= T > style license. > > The rebranding part sounds rather odd to me: you could stick another logo > on top, sure, but we want to know about people's customizations. At this > moment we're happy we can boot an HVM domain but in the long term we'd li= ke > to see this grow to being the best (FOSS) management tool for XCP. > To achieve that goal we need every contribution we can get (especially > from those running this in production). This way the GPL makes a bit more > sense, as you said people need to maintain their modifications on file, s= o > they might just as well be good open source citizens and contribute them. > > Just my 10 cents ;) > > > Appreciated, > W > > PS: I didn't CC xen-users, I don't want to crosspost too much. > > > On 11 February 2012 19:14, Wannes De Smet wrote: > >> *We're happy to announce XenMaster, which has the ambitious goal to >> become the de facto frontend for Xen with XCP. >> >> We've had the opportunity to present our project to some of the Xen/XCP >> developers and now it's time to announce the project to a larger public. >> XenMaster, in short, is a HTML5 frontend coupled to a Java backend >> delivering a rich UI for Xen, targeted at end users. >> At the moment, one is able to successfully add NFS ISO repositories and >> iSCSI/NFS storage repositories (iSCSI currently only works on XenServer >> 5.6), create a HVM VM and control it via a VNC shell. >> >> Development thus far has been carried out by Jorgen Evens, frontend lead >> and Wannes De Smet, project lead and backend developer. Of course, we no= w >> would like to welcome you in becoming a tester and/or contributor! >> You can find more information at xen-master.org, to install and >> configure XenMaster . If >> you'd like to help and have experience in developing Java and/or >> Javascript, load the source in your favorite IDE and have at it! >> >> If you have any questions at all, we'll be happy to answer them here or >> through GitHub. >> >> We hope to welcome you in using XenMaster! >> Jorgen Evens >> Wannes De Smet >> XenMaster * >> >> _______________________________________________ >> xen-api mailing list >> xen-api@lists.xensource.com >> http://lists.xensource.com/mailman/listinfo/xen-api >> >> > > --14dae9cdc3fb7f59a404b8cb03b5 Content-Type: text/html; charset=windows-1252 Content-Transfer-Encoding: quoted-printable You are right that free and open is good. But that's exactly why I don&= #39;t think GPL is the right choice in this case.

Look at Apache for ex= ample... just because the Apache license doesn't contain the GPL "= viral" clause and other restrictions doesn't mean people don't= release their modules for free. The point is, that if they need to keep ce= rtain bits closed for security reasons, or they write some extra functional= ity based upon it that they want to try to sell, they are free to do so. No= -one's going to suddenly close the source of the main project and if an= yone does make some commercial closed source addons then good luck to them,= all it means is that they're got paying customers who will now expect = things to work, and if there are any bugs in the core they'll have to f= ix them and its in their best interests to submit them to the core project = anyway rather than maintain diffs and having to switch their solution for s= omeone elses later...=A0

Give people full freedom and they'll often choose to contribute. P= rescribe to them what they can and cannot do with their own work, and they&= #39;ll often choose a different base for their projects (such as libvirt in= this case).

What XAPI is lacking right now is a really nice, clean,= free and open GUI framework that people can chop and change to their needs= , whether they want a simple web access for starting VMs on their home serv= er or want to incorporate it into their commercial cloud platform offerings= with their custom metering and billing.=A0

There are loads of commercial cloud platforms and VM management soluti= ons out there, but there's no real standard, because no-one has made a = non-proprietary, non-GPL, truly open base system that can be moulded to sui= t the needs of each geek's particular hardware setup and user base.=A0T= hat's the niche I think.

If it's going to be just another out-of-the-box vSp= here client clone then there's XenCenter and OpenXenManager already...<= /div>

On 1= 2 February 2012 13:34, Wannes De Smet <wannes321@gmail.com> wrote:

On 12 Feb 2012, at 13:36, msgbox450@gmail.com wrote:

This looks nice altho= ugh I am not really sure I understand the angle you're coming from here= ...

You're announcing a GUI, but the site is j= ust a wiki with text and a bit of bashing vmware and windows but no screens= hots of nice GUI designs or explanations of how yours will be better=85=A0<= /div>

I should've noted that this was merely= an announcement to let everyone know we're alive and to give it a shot= , we're not even close to a 1.0 release. However your point is valid an= d we've added it on our TODO list.

In my view, XAPI already has a decent Windows GUI in the form of XenCe= nter, the bit we're missing is a really good cross-platform and fully o= pen gui base. Java isn't a great choice for that due to the anti-java f= eelings around the community and GPL is also not a great choice given its v= iral nature.

You seem to have a misunderstanding of the GPL in your = wiki too when you say "the GPLv3 requires that everyone who improves our p= roject, makes his work available publicly". =A0It doesn't - not if= people just use it in house. People can make their own improvements all th= ey like without releasing it.

What the GPL actually means for anyone who wants to make a rebranded relea= se of it for their clients or customers though, is that they will have to m= aintain a full archive of all the source going back all the versions, inclu= ding all their little service-specific tweaks and then make it readily avai= lable to whoever wants it on request.=A0

Thanks for pointing that out.
<= div class=3D"im">

In my view that just adds a lot of extra work and security considerations = to any project that wants to use it. It also means no-one can add anything = clever with it that gives them a competitive edge without releasing the sou= rce, so in that case they'll probably choose to build a GUI from scratc= h rather than contribute anything.

Here's the thing: we don't w= ant people to not release the source. This might make sense from a money pe= rspective, but we're true believers in the open source way. You can be = competitive as a service provider on many other levels; after all, we'r= e just one piece of the machine. Our main ambition is to make this a single= implementation that is the best anyone can get, instead of some scattered = implementations only to give a competitive edge.

If we want a fr= ee, uncustomised=A0proprietary windows GUI like VSphere Client then XenCent= er does a great job. If we want a fully open, cross platform GUI that we ca= n rebrand and customised for our own service offerings then we should be lo= oking at something AJAX based with a BSD/MIT style license.=A0

The rebranding part= sounds rather odd to me: you could stick another logo on top, sure, but we= want to know about people's customizations. At this moment we're h= appy we can boot an HVM domain but in the long term we'd like to see th= is grow to being the best (FOSS) management tool for XCP.=A0

To achieve that goal we need every contribution we can get (especially= from those running this in production). This way the GPL makes a bit more = sense, as you said people need to maintain their modifications on file, so = they might just as well be good open source citizens and contribute them.

Just my 10 cents ;)=

Appreciated,
W

PS: I didn't CC xen-users, I don't want to cr= osspost too much.

On 11 February 2012 19:14, Wannes De Sm= et <wannes321@gmail.com> wrote:

<= font face=3D"Arial" style=3D"font-size:15px">We're ha= ppy to announce XenMaster, which has the ambitious goal to become the de facto frontend for Xen with XCP.

We've had the opportunit= y to present our project to some of the Xen/XCP developers and now it's= time to announce the project to a larger public.
XenMaster, in short, is a HTML5 frontend coupled to a Jav= a backend delivering a rich UI for Xen, targeted at end users.
At the moment, one is able to successfully add NFS ISO re= positories and iSCSI/NFS storage repositories (iSCSI currently only works o= n XenServer 5.6), create a HVM VM and control it via a VNC shell.
Development thus far has bee= n carried out by Jorgen Evens, frontend lead and Wannes De Smet, project le= ad and backend developer. Of course, we now would like to welcome you in be= coming a tester and/or contributor!
You can find more information at xen-master.org, to install and configu= re XenMaster. If you'd like to help and ha= ve experience in developing Java and/or Javascript, load the source in your= favorite IDE and have at it!

If you have any questions at= all, we'll be happy to answer them here or through GitHub.

We hope to welcome you in us= ing XenMaster!
Jorgen Evens
Wannes De Smet
XenMaster

_______________________________________________
xen-api mailing list
xen-api@li= sts.xensource.com
http://lists.xensource.com/mailman/listinfo/xen-api

--14dae9cdc3fb7f59a404b8cb03b5-- --===============0592655977511420842== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ xen-api mailing list xen-api@lists.xensource.com http://lists.xensource.com/mailman/listinfo/xen-api --===============0592655977511420842==-- From xen-api-bounces@lists.xensource.com Mon Feb 13 12:42:30 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 13 Feb 2012 12:42:30 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1RwvEc-0003gi-P1; Mon, 13 Feb 2012 12:42:22 +0000 Received: from mail174.messagelabs.com ([85.158.138.51]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1RwvEb-0003gZ-CK; Mon, 13 Feb 2012 12:42:21 +0000 X-Env-Sender: sdamron@gmail.com X-Msg-Ref: server-13.tower-174.messagelabs.com!1329136933!7992690!1 X-Originating-IP: [209.85.220.171] X-SpamReason: No, hits=0.6 required=7.0 tests=MAILTO_TO_SPAM_ADDR, ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Version: 6.5.5; banners=-,-,- X-VirusChecked: Checked Received: (qmail 29738 invoked from network); 13 Feb 2012 12:42:14 -0000 Received: from mail-vx0-f171.google.com (HELO mail-vx0-f171.google.com) (209.85.220.171) by server-13.tower-174.messagelabs.com with RC4-SHA encrypted SMTP; 13 Feb 2012 12:42:14 -0000 Received: by vcbfo11 with SMTP id fo11so11372825vcb.30 for ; Mon, 13 Feb 2012 04:42:13 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=wUuT/iGmh/tZ0NibPw+erqiU2ZpRLmoWeMEoBgkCXf8=; b=eGn/057YtGDoK59kEcJlQIwkw0O8tdRmhQHDw0fvEw7yJ77qTg4ygtcn8HJYO4euzN xDepTb4FwH99cFCqZsfc5p+jfHe4WKiKBAMYIJ/9xnYePLoJ3PSPkMRX6QpVD7rsmJRw 6F1ZsrCh/rp4UEUFikb1WZPutRdKbxDreIvi4= Received: by 10.220.147.131 with SMTP id l3mr8187774vcv.34.1329136932712; Mon, 13 Feb 2012 04:42:12 -0800 (PST) MIME-Version: 1.0 Received: by 10.52.34.172 with HTTP; Mon, 13 Feb 2012 04:41:52 -0800 (PST) In-Reply-To: <0C8A6062-597B-4914-B150-0FF8917D81C8@gmail.com> References: <0C8A6062-597B-4914-B150-0FF8917D81C8@gmail.com> From: Scott Damron Date: Mon, 13 Feb 2012 06:41:52 -0600 Message-ID: To: Wannes De Smet Cc: xen-users@lists.xensource.com, xen-api@lists.xensource.com Subject: Re: [Xen-API] [Xen-users] Announcing XenMaster X-BeenThere: xen-api@lists.xensource.com X-Mailman-Version: 2.1.13 Precedence: list List-Id: Discussion of API issues surrounding Xen List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-api-bounces@lists.xensource.com Errors-To: xen-api-bounces@lists.xensource.com Instead of harshing on your for using Java, I am going to say - Nicely done! I use either Linux or Mac OS X workstations, and have to run a VM of Windows if I want to use a GUI to manage my Xen boxes. I actually prefer to do the management via a GUI because I don't have a lot of time to waste on trying to remember all of the commands to do stuff. Thank you for the hard work, I will certainly be giving it a try. Regards, Scott On Sat, Feb 11, 2012 at 1:00 PM, Wannes De Smet wrote: > We're happy to announce XenMaster, which has the ambitious goal to become > the de facto frontend for Xen with XCP. > > We've had the opportunity to present our project to some of the Xen/XCP > developers and now it's time to announce the project to a larger public. > XenMaster, in short, is a HTML5 frontend coupled to a Java backend > delivering a rich UI for Xen, targeted at end users. > At the moment, one is able to successfully add NFS ISO repositories and > iSCSI/NFS storage repositories (iSCSI currently only works on XenServer > 5.6), create a HVM VM and control it via a VNC shell. > > Development thus far has been carried out by Jorgen Evens, frontend lead and > Wannes De Smet, project lead and backend developer. Of course, we now would > like to welcome you in becoming a tester and/or contributor! > You can find more information at xen-master.org, to install and configure > XenMaster. If you'd like to help and have experience in developing Java > and/or Javascript, load the source in your favorite IDE and have at it! > > If you have any questions at all, we'll be happy to answer them here or > through GitHub. > > We hope to welcome you in using XenMaster! > Jorgen Evens > Wannes De Smet > XenMaster > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users _______________________________________________ xen-api mailing list xen-api@lists.xensource.com http://lists.xensource.com/mailman/listinfo/xen-api From xen-api-bounces@lists.xensource.com Mon Feb 13 12:42:30 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 13 Feb 2012 12:42:30 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1RwvEc-0003gi-P1; Mon, 13 Feb 2012 12:42:22 +0000 Received: from mail174.messagelabs.com ([85.158.138.51]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1RwvEb-0003gZ-CK; Mon, 13 Feb 2012 12:42:21 +0000 X-Env-Sender: sdamron@gmail.com X-Msg-Ref: server-13.tower-174.messagelabs.com!1329136933!7992690!1 X-Originating-IP: [209.85.220.171] X-SpamReason: No, hits=0.6 required=7.0 tests=MAILTO_TO_SPAM_ADDR, ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Version: 6.5.5; banners=-,-,- X-VirusChecked: Checked Received: (qmail 29738 invoked from network); 13 Feb 2012 12:42:14 -0000 Received: from mail-vx0-f171.google.com (HELO mail-vx0-f171.google.com) (209.85.220.171) by server-13.tower-174.messagelabs.com with RC4-SHA encrypted SMTP; 13 Feb 2012 12:42:14 -0000 Received: by vcbfo11 with SMTP id fo11so11372825vcb.30 for ; Mon, 13 Feb 2012 04:42:13 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=wUuT/iGmh/tZ0NibPw+erqiU2ZpRLmoWeMEoBgkCXf8=; b=eGn/057YtGDoK59kEcJlQIwkw0O8tdRmhQHDw0fvEw7yJ77qTg4ygtcn8HJYO4euzN xDepTb4FwH99cFCqZsfc5p+jfHe4WKiKBAMYIJ/9xnYePLoJ3PSPkMRX6QpVD7rsmJRw 6F1ZsrCh/rp4UEUFikb1WZPutRdKbxDreIvi4= Received: by 10.220.147.131 with SMTP id l3mr8187774vcv.34.1329136932712; Mon, 13 Feb 2012 04:42:12 -0800 (PST) MIME-Version: 1.0 Received: by 10.52.34.172 with HTTP; Mon, 13 Feb 2012 04:41:52 -0800 (PST) In-Reply-To: <0C8A6062-597B-4914-B150-0FF8917D81C8@gmail.com> References: <0C8A6062-597B-4914-B150-0FF8917D81C8@gmail.com> From: Scott Damron Date: Mon, 13 Feb 2012 06:41:52 -0600 Message-ID: To: Wannes De Smet Cc: xen-users@lists.xensource.com, xen-api@lists.xensource.com Subject: Re: [Xen-API] [Xen-users] Announcing XenMaster X-BeenThere: xen-api@lists.xensource.com X-Mailman-Version: 2.1.13 Precedence: list List-Id: Discussion of API issues surrounding Xen List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-api-bounces@lists.xensource.com Errors-To: xen-api-bounces@lists.xensource.com Instead of harshing on your for using Java, I am going to say - Nicely done! I use either Linux or Mac OS X workstations, and have to run a VM of Windows if I want to use a GUI to manage my Xen boxes. I actually prefer to do the management via a GUI because I don't have a lot of time to waste on trying to remember all of the commands to do stuff. Thank you for the hard work, I will certainly be giving it a try. Regards, Scott On Sat, Feb 11, 2012 at 1:00 PM, Wannes De Smet wrote: > We're happy to announce XenMaster, which has the ambitious goal to become > the de facto frontend for Xen with XCP. > > We've had the opportunity to present our project to some of the Xen/XCP > developers and now it's time to announce the project to a larger public. > XenMaster, in short, is a HTML5 frontend coupled to a Java backend > delivering a rich UI for Xen, targeted at end users. > At the moment, one is able to successfully add NFS ISO repositories and > iSCSI/NFS storage repositories (iSCSI currently only works on XenServer > 5.6), create a HVM VM and control it via a VNC shell. > > Development thus far has been carried out by Jorgen Evens, frontend lead and > Wannes De Smet, project lead and backend developer. Of course, we now would > like to welcome you in becoming a tester and/or contributor! > You can find more information at xen-master.org, to install and configure > XenMaster. If you'd like to help and have experience in developing Java > and/or Javascript, load the source in your favorite IDE and have at it! > > If you have any questions at all, we'll be happy to answer them here or > through GitHub. > > We hope to welcome you in using XenMaster! > Jorgen Evens > Wannes De Smet > XenMaster > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users _______________________________________________ xen-api mailing list xen-api@lists.xensource.com http://lists.xensource.com/mailman/listinfo/xen-api From xen-api-bounces@lists.xensource.com Mon Feb 13 13:21:38 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 13 Feb 2012 13:21:38 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1RwvqX-0007GB-3f; Mon, 13 Feb 2012 13:21:33 +0000 Received: from mail27.messagelabs.com ([193.109.254.147]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1RwvqV-0007FO-2G; Mon, 13 Feb 2012 13:21:31 +0000 X-Env-Sender: sdamron@gmail.com X-Msg-Ref: server-4.tower-27.messagelabs.com!1329139244!59895787!1 X-Originating-IP: [209.85.212.43] X-SpamReason: No, hits=0.6 required=7.0 tests=MAILTO_TO_SPAM_ADDR, ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Version: 6.5.5; banners=-,-,- X-VirusChecked: Checked Received: (qmail 2202 invoked from network); 13 Feb 2012 13:20:45 -0000 Received: from mail-vw0-f43.google.com (HELO mail-vw0-f43.google.com) (209.85.212.43) by server-4.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 13 Feb 2012 13:20:45 -0000 Received: by vbbfq11 with SMTP id fq11so11509879vbb.30 for ; Mon, 13 Feb 2012 05:21:28 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type:content-transfer-encoding; bh=OQr1kO+SF5210lq9U5ctk4D7tqlp3zntVhcVodt55hs=; b=L8pT/DoCfpYcxR3L/4VFj6UUQZyrN608XxFQc22KX8itHzz4p8EWWzw+HEqqwg/MIA sZ28jMg4U7qkRCzv8ik/tZHzrcXTNneguh78YndzbFYlM4sRT7KaXkyx7GWbYG2kvD/P UHLf2gc8UGpRSNOTt3l/ju1nAqCCHef2jqGQ8= Received: by 10.220.224.136 with SMTP id io8mr8311020vcb.4.1329139288250; Mon, 13 Feb 2012 05:21:28 -0800 (PST) MIME-Version: 1.0 Received: by 10.52.34.172 with HTTP; Mon, 13 Feb 2012 05:21:08 -0800 (PST) In-Reply-To: References: <0C8A6062-597B-4914-B150-0FF8917D81C8@gmail.com> From: Scott Damron Date: Mon, 13 Feb 2012 07:21:08 -0600 Message-ID: To: Ciprian Pantea Cc: xen-users@lists.xensource.com, xen-api@lists.xensource.com Subject: Re: [Xen-API] [Xen-users] Announcing XenMaster X-BeenThere: xen-api@lists.xensource.com X-Mailman-Version: 2.1.13 Precedence: list List-Id: Discussion of API issues surrounding Xen List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Sender: xen-api-bounces@lists.xensource.com Errors-To: xen-api-bounces@lists.xensource.com Screen shots are included on the Wiki... On Mon, Feb 13, 2012 at 7:19 AM, Ciprian Pantea wrote: > I'd love to give it a try too but screenshots would have been better :) > I'm not clear though on the list of features and I don't find any on your > site either. > > > Good job! > PS: try to get rid of java in the future > > > On Mon, Feb 13, 2012 at 14:41, Scott Damron wrote: >> >> Instead of harshing on your for using Java, I am going to say - Nicely >> done! =A0I use either Linux or Mac OS X workstations, and have to run a >> VM of Windows if I want to use a GUI to manage my Xen boxes. =A0I >> actually prefer to do the management via a GUI because I don't have a >> lot of time to waste on trying to remember all of the commands to do >> stuff. =A0Thank you for the hard work, I will certainly be giving it a >> try. >> >> Regards, >> >> Scott >> >> On Sat, Feb 11, 2012 at 1:00 PM, Wannes De Smet >> wrote: >> > We're happy to announce XenMaster, which has the ambitious goal to >> > become >> > the de facto frontend for Xen with XCP. >> > >> > We've had the opportunity to present our project to some of the Xen/XCP >> > developers and now it's time to announce the project to a larger publi= c. >> > XenMaster, in short, is a HTML5 frontend coupled to a Java backend >> > delivering a rich UI for Xen, targeted at end users. >> > At the moment, one is able to successfully add NFS ISO repositories and >> > iSCSI/NFS storage repositories (iSCSI currently only works on XenServer >> > 5.6), create a HVM VM and control it via a VNC shell. >> > >> > Development thus far has been carried out by Jorgen Evens, frontend le= ad >> > and >> > Wannes De Smet, project lead and backend developer. Of course, we now >> > would >> > like to welcome you in becoming a tester and/or contributor! >> > You can find more information at xen-master.org, to install and >> > configure >> > XenMaster. If you'd like to help and have experience in developing Java >> > and/or Javascript, load the source in your favorite IDE and have at it! >> > >> > If you have any questions at all, we'll be happy to answer them here or >> > through GitHub. >> > >> > We hope to welcome you in using XenMaster! >> > Jorgen Evens >> > Wannes De Smet >> > XenMaster >> > >> > _______________________________________________ >> > Xen-users mailing list >> > Xen-users@lists.xensource.com >> > http://lists.xensource.com/xen-users >> >> _______________________________________________ >> Xen-users mailing list >> Xen-users@lists.xensource.com >> http://lists.xensource.com/xen-users > > _______________________________________________ xen-api mailing list xen-api@lists.xensource.com http://lists.xensource.com/mailman/listinfo/xen-api From xen-api-bounces@lists.xensource.com Mon Feb 13 13:21:38 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 13 Feb 2012 13:21:38 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1RwvqX-0007GB-3f; Mon, 13 Feb 2012 13:21:33 +0000 Received: from mail27.messagelabs.com ([193.109.254.147]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1RwvqV-0007FO-2G; Mon, 13 Feb 2012 13:21:31 +0000 X-Env-Sender: sdamron@gmail.com X-Msg-Ref: server-4.tower-27.messagelabs.com!1329139244!59895787!1 X-Originating-IP: [209.85.212.43] X-SpamReason: No, hits=0.6 required=7.0 tests=MAILTO_TO_SPAM_ADDR, ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Version: 6.5.5; banners=-,-,- X-VirusChecked: Checked Received: (qmail 2202 invoked from network); 13 Feb 2012 13:20:45 -0000 Received: from mail-vw0-f43.google.com (HELO mail-vw0-f43.google.com) (209.85.212.43) by server-4.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 13 Feb 2012 13:20:45 -0000 Received: by vbbfq11 with SMTP id fq11so11509879vbb.30 for ; Mon, 13 Feb 2012 05:21:28 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type:content-transfer-encoding; bh=OQr1kO+SF5210lq9U5ctk4D7tqlp3zntVhcVodt55hs=; b=L8pT/DoCfpYcxR3L/4VFj6UUQZyrN608XxFQc22KX8itHzz4p8EWWzw+HEqqwg/MIA sZ28jMg4U7qkRCzv8ik/tZHzrcXTNneguh78YndzbFYlM4sRT7KaXkyx7GWbYG2kvD/P UHLf2gc8UGpRSNOTt3l/ju1nAqCCHef2jqGQ8= Received: by 10.220.224.136 with SMTP id io8mr8311020vcb.4.1329139288250; Mon, 13 Feb 2012 05:21:28 -0800 (PST) MIME-Version: 1.0 Received: by 10.52.34.172 with HTTP; Mon, 13 Feb 2012 05:21:08 -0800 (PST) In-Reply-To: References: <0C8A6062-597B-4914-B150-0FF8917D81C8@gmail.com> From: Scott Damron Date: Mon, 13 Feb 2012 07:21:08 -0600 Message-ID: To: Ciprian Pantea Cc: xen-users@lists.xensource.com, xen-api@lists.xensource.com Subject: Re: [Xen-API] [Xen-users] Announcing XenMaster X-BeenThere: xen-api@lists.xensource.com X-Mailman-Version: 2.1.13 Precedence: list List-Id: Discussion of API issues surrounding Xen List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Sender: xen-api-bounces@lists.xensource.com Errors-To: xen-api-bounces@lists.xensource.com Screen shots are included on the Wiki... On Mon, Feb 13, 2012 at 7:19 AM, Ciprian Pantea wrote: > I'd love to give it a try too but screenshots would have been better :) > I'm not clear though on the list of features and I don't find any on your > site either. > > > Good job! > PS: try to get rid of java in the future > > > On Mon, Feb 13, 2012 at 14:41, Scott Damron wrote: >> >> Instead of harshing on your for using Java, I am going to say - Nicely >> done! =A0I use either Linux or Mac OS X workstations, and have to run a >> VM of Windows if I want to use a GUI to manage my Xen boxes. =A0I >> actually prefer to do the management via a GUI because I don't have a >> lot of time to waste on trying to remember all of the commands to do >> stuff. =A0Thank you for the hard work, I will certainly be giving it a >> try. >> >> Regards, >> >> Scott >> >> On Sat, Feb 11, 2012 at 1:00 PM, Wannes De Smet >> wrote: >> > We're happy to announce XenMaster, which has the ambitious goal to >> > become >> > the de facto frontend for Xen with XCP. >> > >> > We've had the opportunity to present our project to some of the Xen/XCP >> > developers and now it's time to announce the project to a larger publi= c. >> > XenMaster, in short, is a HTML5 frontend coupled to a Java backend >> > delivering a rich UI for Xen, targeted at end users. >> > At the moment, one is able to successfully add NFS ISO repositories and >> > iSCSI/NFS storage repositories (iSCSI currently only works on XenServer >> > 5.6), create a HVM VM and control it via a VNC shell. >> > >> > Development thus far has been carried out by Jorgen Evens, frontend le= ad >> > and >> > Wannes De Smet, project lead and backend developer. Of course, we now >> > would >> > like to welcome you in becoming a tester and/or contributor! >> > You can find more information at xen-master.org, to install and >> > configure >> > XenMaster. If you'd like to help and have experience in developing Java >> > and/or Javascript, load the source in your favorite IDE and have at it! >> > >> > If you have any questions at all, we'll be happy to answer them here or >> > through GitHub. >> > >> > We hope to welcome you in using XenMaster! >> > Jorgen Evens >> > Wannes De Smet >> > XenMaster >> > >> > _______________________________________________ >> > Xen-users mailing list >> > Xen-users@lists.xensource.com >> > http://lists.xensource.com/xen-users >> >> _______________________________________________ >> Xen-users mailing list >> Xen-users@lists.xensource.com >> http://lists.xensource.com/xen-users > > _______________________________________________ xen-api mailing list xen-api@lists.xensource.com http://lists.xensource.com/mailman/listinfo/xen-api From xen-api-bounces@lists.xensource.com Mon Feb 13 18:00:01 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 13 Feb 2012 18:00: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 1Rx0Bt-0003EX-Ca; Mon, 13 Feb 2012 17:59:53 +0000 Received: from mail216.messagelabs.com ([85.158.143.99]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Rx0Br-0003EI-9a for xen-api@lists.xensource.com; Mon, 13 Feb 2012 17:59:51 +0000 X-Env-Sender: jorgen.evens@gmail.com X-Msg-Ref: server-14.tower-216.messagelabs.com!1329155984!14087713!1 X-Originating-IP: [209.85.213.171] X-SpamReason: No, hits=1.2 required=7.0 tests=HTML_20_30,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Version: 6.5.5; banners=-,-,- X-VirusChecked: Checked Received: (qmail 10835 invoked from network); 13 Feb 2012 17:59:45 -0000 Received: from mail-yx0-f171.google.com (HELO mail-yx0-f171.google.com) (209.85.213.171) by server-14.tower-216.messagelabs.com with RC4-SHA encrypted SMTP; 13 Feb 2012 17:59:45 -0000 Received: by yenm7 with SMTP id m7so83433524yen.30 for ; Mon, 13 Feb 2012 09:59:43 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; bh=ymrZoBeiW5qRJof0gqonVCrvMXQYhKU0ydb9stUXdT4=; b=ijFx/eNIrtTppKJkQpB5T26Ox5Lsh9ngkaIDZDBNFn4sU64zu19ymA4vS1wvQKYHen 3Vn/BDpXeyZ8kTLTDDsGma3E7fGahKPT3P9AN170GAsrTQpIZiSfL7OrWV4QzPKqDSAR ybzF61Ognu4qM3BoaoqnYpq1JjmsQpTxjt5h8= MIME-Version: 1.0 Received: by 10.50.156.196 with SMTP id wg4mr28844821igb.13.1329155983714; Mon, 13 Feb 2012 09:59:43 -0800 (PST) Received: by 10.231.173.80 with HTTP; Mon, 13 Feb 2012 09:59:43 -0800 (PST) Date: Mon, 13 Feb 2012 18:59:43 +0100 Message-ID: From: Jorgen Evens To: xen-api@lists.xensource.com Subject: [Xen-API] Requesting multiple consoles through XAPI X-BeenThere: xen-api@lists.xensource.com X-Mailman-Version: 2.1.13 Precedence: list List-Id: Discussion of API issues surrounding Xen List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============0583924597095208223==" Sender: xen-api-bounces@lists.xensource.com Errors-To: xen-api-bounces@lists.xensource.com --===============0583924597095208223== Content-Type: multipart/alternative; boundary=e89a8f3baf0142a8c204b8dc3ee9 --e89a8f3baf0142a8c204b8dc3ee9 Content-Type: text/plain; charset=ISO-8859-1 Hello, We would like to be able to connect to a virtual machine console through XAPI from multiple computers at once. Currently when a connection is already open and we try to open another one on a different computer we only get the HTTP/1.1 200 OK headers from XAPI, but no VNC data is received. The second connections stays open until we close it manually. We are trying to do this on Kronos. Met vriendelijke groeten, -- Jorgen Evens --e89a8f3baf0142a8c204b8dc3ee9 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable

Hello,

We would like to be able to conne= ct to a virtual machine console through XAPI from multiple computers at onc= e.

Currently when a connection is already open and we try to open= another one on a different computer we only get the=A0HTTP/1.1 200 OK head= ers from XAPI, but no VNC data is received.

The second connections stays open until we close it manually.

We are trying to do this on Kronos.

Met vriendelijke groeten,

Jorgen Evens

--e89a8f3baf0142a8c204b8dc3ee9-- --===============0583924597095208223== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ xen-api mailing list xen-api@lists.xensource.com http://lists.xensource.com/mailman/listinfo/xen-api --===============0583924597095208223==-- From xen-api-bounces@lists.xensource.com Mon Feb 13 18:00:01 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 13 Feb 2012 18:00: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 1Rx0Bt-0003EX-Ca; Mon, 13 Feb 2012 17:59:53 +0000 Received: from mail216.messagelabs.com ([85.158.143.99]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Rx0Br-0003EI-9a for xen-api@lists.xensource.com; Mon, 13 Feb 2012 17:59:51 +0000 X-Env-Sender: jorgen.evens@gmail.com X-Msg-Ref: server-14.tower-216.messagelabs.com!1329155984!14087713!1 X-Originating-IP: [209.85.213.171] X-SpamReason: No, hits=1.2 required=7.0 tests=HTML_20_30,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Version: 6.5.5; banners=-,-,- X-VirusChecked: Checked Received: (qmail 10835 invoked from network); 13 Feb 2012 17:59:45 -0000 Received: from mail-yx0-f171.google.com (HELO mail-yx0-f171.google.com) (209.85.213.171) by server-14.tower-216.messagelabs.com with RC4-SHA encrypted SMTP; 13 Feb 2012 17:59:45 -0000 Received: by yenm7 with SMTP id m7so83433524yen.30 for ; Mon, 13 Feb 2012 09:59:43 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; bh=ymrZoBeiW5qRJof0gqonVCrvMXQYhKU0ydb9stUXdT4=; b=ijFx/eNIrtTppKJkQpB5T26Ox5Lsh9ngkaIDZDBNFn4sU64zu19ymA4vS1wvQKYHen 3Vn/BDpXeyZ8kTLTDDsGma3E7fGahKPT3P9AN170GAsrTQpIZiSfL7OrWV4QzPKqDSAR ybzF61Ognu4qM3BoaoqnYpq1JjmsQpTxjt5h8= MIME-Version: 1.0 Received: by 10.50.156.196 with SMTP id wg4mr28844821igb.13.1329155983714; Mon, 13 Feb 2012 09:59:43 -0800 (PST) Received: by 10.231.173.80 with HTTP; Mon, 13 Feb 2012 09:59:43 -0800 (PST) Date: Mon, 13 Feb 2012 18:59:43 +0100 Message-ID: From: Jorgen Evens To: xen-api@lists.xensource.com Subject: [Xen-API] Requesting multiple consoles through XAPI X-BeenThere: xen-api@lists.xensource.com X-Mailman-Version: 2.1.13 Precedence: list List-Id: Discussion of API issues surrounding Xen List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============0583924597095208223==" Sender: xen-api-bounces@lists.xensource.com Errors-To: xen-api-bounces@lists.xensource.com --===============0583924597095208223== Content-Type: multipart/alternative; boundary=e89a8f3baf0142a8c204b8dc3ee9 --e89a8f3baf0142a8c204b8dc3ee9 Content-Type: text/plain; charset=ISO-8859-1 Hello, We would like to be able to connect to a virtual machine console through XAPI from multiple computers at once. Currently when a connection is already open and we try to open another one on a different computer we only get the HTTP/1.1 200 OK headers from XAPI, but no VNC data is received. The second connections stays open until we close it manually. We are trying to do this on Kronos. Met vriendelijke groeten, -- Jorgen Evens --e89a8f3baf0142a8c204b8dc3ee9 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable