Arch Linux User Repository

I have a Windows 7 domU with an ATI 6770 passed through as a secondary adaptor, along with a USB 2.0 root hub and USB 3.0 root hub. Its been working well, except that I can't install the PV drivers without the ATI driver appearing to cause a blue screen on bootup. Still runs well without them. This is on a ASUS Sabertooth 990FX motherboard with an AMD Phenom II x4 965 processor and a total of 12Gb on board (6Gb assigned to the Windows domU)

Just tried the new package and things seem to go much smoother. I had to create the folder /var/lib/xen/ by hand in order to create a HVM though. Based on the processor usage pattern after I start the HVM Windows 7 is starting, but I'm not getting any display through the video adapter I pass through to the HVM. I never got the dedicated graphics passthrough capability working on 4.1, the graphics was just passed through as a PCI device. Not sure what's going on with the PCI passthrough but I'll keep fiddling with my setup. Anyone here using this for PCI or GFX passthrough yet?

Sorry to insist, but in some supported configurations /run/xen *is* needed: http://pastebin.com/QaqS2Krt kantras' tmpfiles.d solution would appear to be the way to go and should be included.

fixed.

Just tried the modified xenstored.service, doesn't like it. This is the one: tested, works ExecStart=/usr/sbin/xenstored --pid-file /var/run/xenstored.pid $XENSTORED_ARGS ExecStartPost=/usr/bin/xenstore-write "/local/domain/0/name" "Domain-0" Result: Name ID Mem VCPUs State Time(s) Domain-0 0 1024 2 r----- 24.9

Removed archinit.patch and added xenstore-write cmd to xenstored service file.

Package built with archinit.patch - fail Package built without archinit.patch - successfully created, logged into and shut down a pv of Debian wheezy. created: /run/xenstored /run/xenstored.pid /var/run/xenstored /var/run/xenstored.pid not created (not needed), /run/xen /var/run/xen Using journalctl on the failed build showed xendomains failed at three points, each of which were lines added to xendomains by archinit.patch. The patch adds to xendomains function calls from rc.d/functions, which no longer exists. Previously no effect, but now causes xendomains.service to fail. Also all to do with xend. Conclusion: previously the patch was useless, now it is a liability.

Actually, I have a file for creating the /run/xen directory as well, on http://www.kantras.info/xen, called tmpfiles.d.xen.conf. In the test PKGBUILD file I was using, I copied it to /usr/lib/tmpfiles.d/xen.conf

/var/run/xen is being created on my system, but it is built from the official tarball, with the service files as existed in the 4.2.0-3 arch release. i.e archinit.patch was not used, but otherwise the same as 4.2.0-3. I 'll take a look tomorrow and do a full aur install of the current version.