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 <[email protected]>wrote: > Hi, > > > > 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: > > http://www.xen.org/files/XenCloud/Software/20719c/xapi-no-expiry > > > > 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) > > > > Thanks, > > Dave > > > > > > *From:* Dave Scott > *Sent:* 24 December 2009 17:10 > *To:* Stephen Spector; 'Vern Burke'; [email protected]; > [email protected] > *Subject:* RE: [Xen-users] Xen Cloud Platform disaster > > > > Hi, > > > > 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: > > > > http://www.xen.org/files/XenCloud/Software/20719c/xapi-no-expiry > > > > 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, > > Dave > > > > *From:* [email protected] [mailto: > [email protected]] *On Behalf Of *Stephen Spector > *Sent:* 24 December 2009 14:24 > *To:* 'Vern Burke'; [email protected]; > [email protected] > *Subject:* [Xen-API] RE: [Xen-users] Xen Cloud Platform disaster > > > > Vern: > > > > 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:* [email protected] [mailto: > [email protected]] *On Behalf Of *Vern Burke > *Sent:* Thursday, December 24, 2009 5:05 AM > *To:* [email protected] > *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? > > Vern > > > > _______________________________________________ > xen-api mailing list > [email protected] > http://lists.xensource.com/mailman/listinfo/xen-api > > -- Marco Sinhoreli
_______________________________________________ xen-api mailing list [email protected] http://lists.xensource.com/mailman/listinfo/xen-api
