Yep, I've playing with XCP 1.6 before accepting it to product.
Found two clear bugs:
1. Bad setup-vif-rules - already send a pull request:
https://github.com/xen-org/xen-api/pull/953
2. Bug with strange maxmem_kb leak on loop migration.
The second is very easy to test: create vm with dynamc=static=512Mib and
do 1000 migration:
xe vm-migrate vm=test host=`hostname`
After every migration maxmem_kb in xc.domain_getinfo() raised a little.
1000 migration was enough to get it >800MiB (with static-max=512MiB).
I'll resend this to issue tracker on github. Thank you for advice.
On 22.12.2012 23:41, Dave Scott wrote:
Hi,
You've provoked me to respond :-) but it is a good question so thanks for
asking it.
Is it worth experimenting with the github issue tracker to see what it's like? If we
decide to use some other system later we can probably export the github data via their
API and move across. I worry that, if we wait to find the ideal system, we could be
waiting a very long time (as that (originally French?) saying goes, "the perfect is
the enemy of the good")
The migration bug you mention-- is that still happening on XCP 1.6? It sounds
familiar.
Thanks,
_______________________________________________
Xen-api mailing list
[email protected]
http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api
