This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


Re: [Xen-API] RE: [Xen-users] Xen Cloud Platform disaster

To: Dave Scott <Dave.Scott@xxxxxxxxxxxxx>
Subject: Re: [Xen-API] RE: [Xen-users] Xen Cloud Platform disaster
From: Marco Sinhoreli <msinhore@xxxxxxxxx>
Date: Tue, 5 Jan 2010 11:06:49 -0200
Cc: Vern Burke <vburke0715@xxxxxxxxx>, "xen-api@xxxxxxxxxxxxxxxxxxx" <xen-api@xxxxxxxxxxxxxxxxxxx>, Stephen Spector <stephen.spector@xxxxxxxxxx>, "xen-users@xxxxxxxxxxxxxxxxxxx" <xen-users@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Tue, 05 Jan 2010 05:07:36 -0800
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type; bh=VJUdGU66SZEisAxnzeRj9tUXGSiXm5X+0+5SFTyPrR4=; b=iqUjhma/8AQEiyhUfhoQxqVPp+dtGUZQZ4NfqgxOQ9ZLfJAp8UoSbVLsC6GEkt+f1x pr0HDaE6aMb3qUOei065dNMETKd8DW2L9A6yC8yFdwVH0QdMzTq56sdS5fkm9WWJrISp TFhcetuJd/u249X32SMp2PMmvUjmn3gdczxek=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=NlUMXGRIcACB56v/SLy8iJFYdJcOefMC31EoKKr72YGyr7nAJ3Owk2rLg6WyhFvJQH uwj63nTNIieq6Q04gR9Z03e/tszjxiJVCVoA2bpE7Y7vfL+R+gdnvZz0DtwpSbxVBI2P Yr+1unvnTvwEXl9LU14GA6maCAErESDWyxG78=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <81A73678E76EA642801C8F2E4823AD2143B8C19421@xxxxxxxxxxxxxxxxxxxxxxxxx>
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
References: <597560.33302.qm@xxxxxxxxxxxxxxxxxxxxxxxxxxx> <652FFB2C8F91E3428799B1FFF8B490C9724AD4F4F4@xxxxxxxxxxxxxxxxxxxxxxxxx> <81A73678E76EA642801C8F2E4823AD2143B8C1941D@xxxxxxxxxxxxxxxxxxxxxxxxx> <81A73678E76EA642801C8F2E4823AD2143B8C19421@xxxxxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
Hi Dave,

Thanks for your fix. When (exact date) the .isos will be available? Are you thinking in end of January or before? I am starting my infrastructure virtualized with XCP exactly this week. I worked in middleware software for integrate the XCP using XAPI, Switches, Balancers and monitoring using an API develloped internally. If you can let me know about the it I'll be glad.  

Thanks in advance,

On Tue, Dec 29, 2009 at 9:36 AM, Dave Scott <Dave.Scott@xxxxxxxxxxxxx> wrote:



I’ve updated the patched xapi binary to fix an issue where migration/suspend/resume would fail with a spurious ‘PV drivers out of date’ error. The link is still the same:

The md5 of the new file is 3895f81600cf1c84519d76ac6fbaa5ff.


Again the procedure to install it is:

1.       service xapi stop

2.       copy the file to /opt/xensource/bin/xapi

3.       chmod +x /opt/xensource/bin/xapi

4.       service xapi start

This should be done on all hosts.


I still aim to update the XCP .isos in January to include these fixes (and lots more)






From: Dave Scott
Sent: 24 December 2009 17:10
To: Stephen Spector; 'Vern Burke'; xen-users@xxxxxxxxxxxxxxxxxxx; xen-api@xxxxxxxxxxxxxxxxxxx
Subject: RE: [Xen-users] Xen Cloud Platform disaster




I investigated and discovered that I removed most but not all of the licensing code L The ‘feature restrictions’ were disabled but the license expiry check was still present. I’ve pushed a patch to xen-api.hg to fix this.


I’ve compiled a custom xapi binary which is: build 20719 (the one on the website) plus this specific patch. The binary is here:




if you copy that to /opt/xensource/bin/xapi, make sure you ‘chmod +x’ it, and the restart xapi it should work. The binary needs to be changed on all hosts.


I installed a 20719c build, installed a VM, pushed my clock forward, reproduced the failure, installed the new xapi and verified the VM could be started.


I’ll aim to update the XCP binaries on the website in January to include this fix.


Sorry about that,



From: xen-api-bounces@xxxxxxxxxxxxxxxxxxx [mailto:xen-api-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of Stephen Spector
Sent: 24 December 2009 14:24
To: 'Vern Burke'; xen-users@xxxxxxxxxxxxxxxxxxx; xen-api@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-API] RE: [Xen-users] Xen Cloud Platform disaster




The licensing components from XCP should have been removed and this not occur. I have added the xen-api list to this email so the developers can be aware of the situation and offer their guidance. Thanks.


Stephen Spector


From: xen-users-bounces@xxxxxxxxxxxxxxxxxxx [mailto:xen-users-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of Vern Burke
Sent: Thursday, December 24, 2009 5:05 AM
To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-users] Xen Cloud Platform disaster


Well, I made the mistake of shutting down my XCP cloud tonight not knowing that XCP licenses expire every 30 days and expired licenses prevent any VMs from being started (and not having any procedure listed anywhere to get a new license). So I reinstall XCP on one machine, get a new 30 day license generated, import the pool data base so the VMs are back and discover it sets the damn license back to the expired date!

So now I'm down totally. I can't start anything, I can't restore anything, I can't regenerate a new license for any of the machines without abandoning everything. Is there ANY way to get a new license on these without starting over from ground zero?



xen-api mailing list

Marco Sinhoreli
Xen-users mailing list
<Prev in Thread] Current Thread [Next in Thread>