Arch Linux User Repository

I have never used libvirt, and I do not have a hardware-virtual processor (nor any need for one), so anything I can do will be limited to pv. I have just downloaded v1.0.0 and made an initial attempt to build it. I am also checking out the abs build. However, even if it builds, it may not have all features. http://wiki.xen.org/wiki/Fedora_Host_Installation "Starting from Xen 4.2, the default toolstack is libxl. libvirt has a libxl driver, but it (at the time of writing) still lacks many important features... ...There is an on-going effort to fill the gap and render the libvirt libxl driver feature complete and fully functional, although it is yet unclear when that will happen (in particular, whether or not it will make it in time for Fedora 18." On the other hand, the tarball that I downloaded (stable libvirt 1.0.0) has News November 2 2012 at least mentions xen 4.2. So there may be hope. http://libvirt.org/news.html "various improvement and fixes when using QMP QEmu interface Support for Xen 4.2 (Jim Fehlig)" If I have anything more useful to say, I shall put it on some libvirt page and leave a comment here.

@ paleo9: thanks, running # xenstore-write "/local/domain/0/name" "Domain-0" manually changed the (null) value. Is there any way to get libvirt for xen to build without error?

Writing something to add the name into xenstore (amongst other things, such as using xl to update my assignable pci devices) is on my todo list; right now I just kick off script on bootup, but that won't work for me once I start using xendomains to auto-start. @fernando_ccs17, my desktop has both an ATI and a Nvidia graphics card in it, and I spend a few hours trying to get the official Nvidia drivers working, only to have to give up for now. The problem is that Nvidia have already stated that they will only support the Quadro series when it comes to virtualization, so i'm waiting for nouveau support to improve. The ATI card, which is passed through to a Windows domU, works much better (although still with quirks at times)

Re "Domain-0" and (null), the relevant lines in xencommons are: echo Setting domain 0 name... xenstore-write "/local/domain/0/name" "Domain-0" My thoughts: It appears to be using "xenstore-write" to place an entry "Domain-0" into the 'name' field of its database. There is only one dom0, so there should not be a "/local/domain/1/name" or "Domain-1" etc. It is unlikely that there will be anything to be gained by checking the value of "/local/domain/0/name/", so unless errors happen it was not a high priority for getting the service file to work.

Nothing to worry about. In the old xencommons script, which has been replaced by systemd service files, there was a line which gave the name Domain-0. Can't remember off hand, maybe printed a line into the pid file? Anyway, this line wasn't included in the service file. It's not used by anything, just a label for human eyes.

any idea why am I having (null) instead of Domain-0?

@paleo9 Removed the file from the package.

Hmm... So it works only with nouveau. I Need 3D support for my 9800GT. You know...

Just for info: My card is nvidia, I have no problems with the nouveau driver.