3 comments

Add a comment…

Sign in

prestine

Your email address

Check!

invalid email

(thinking…)

Reset

or sign in with

• 
• 

UserVoice password

Forgot password?

Create a password

Your name

I agree to the terms of service

Signed in as (Sign out)

Close

Close

Post comment Submitting...

• Florian Heigl commented  ·  January 18, 2013 8:14 a.m.  ·  Delete

  George: I think Pasi had it down right.
  The mess is as broad and vague as his post suggests.
  In every release of Xen, every version of Libvirt, in every Distro, the users have no way of telling if a given feature will work.

  On first glance, that would be only fixable with unlimited ressources.
  On the other hand, maybe something more hands-on might work:

  i.e. define a number of goals like "it should be possible to add a xen host to virt-manager" or "virsh list should just work" on every current (bug reports for those) or new release of Debian, Ubuntu, Fedora. (just an example, but I'd suggest starting with the basics. If they would just work (they don't, imo) then the whole things like "ballooning, io limiting, hot migrations, ..." come from the list.

  Then it's something that can be planned / reviewed and also done by us users on the xen testing days.
  What you devs could do is get in closer loop with the libvirt devs and get tested documentation on their site.

  Pasi, am I missing the point?

• Florian Heigl commented  ·  September 19, 2012 4:30 p.m.  ·  Delete

  I think I remember that the Xen driver was also sometimes missing in the libvirt base install. This is a lobbyism issue, too.

• George Dunlap commented  ·  August 22, 2012 9:34 a.m.  ·  Delete

  Hey Pasi -- thanks for posting this. But this is both to vague and too broad to be actually useful. Of all the functionality of Xen which is missing from libvirt, which is causing the most pain to users? That's what we need to know.