CA-127183: qemu-dm does not accept this flag anymore. Passing the
'-priv' flag to the qemu-dm causes it to exit and VM creation fails.

Signed-off-by: Akshay <akshay.ramani@citrix.com>
s/Stringext/Xstringext/g

Signed-off-by: Jon Ludlam <jonathan.ludlam@citrix.com>
Add vm pre-resume hook.

No hooks are currently triggered on resume - including resume after
a live migrate, which is the only possible time a hook could trigger
on a new VM on the target host.
Merge pull request #63 from jonludlam/great_stringext_rename

s/Stringext/Xstringext/g
arm: shadow_allocation_set is not supported; log failure and continue

Signed-off-by: David Scott <dave.scott@citrix.com>
Remove Re_str usage

It's not threadsafe

Signed-off-by: Jon Ludlam <jonathan.ludlam@citrix.com>
CA-136054: Make path to vgpu configurable

vgpu is currently a non-essential resource as it's not yet installed in
trunk. We may or may not want to change this in the future.

Signed-off-by: John Else <john.else@citrix.com>
Merge pull request #71 from jonludlam/re_str_removal

Remove Re_str usage
Merge pull request #62 from BobBall/resume_hook

Add vm pre-resume hook.
CA-135934: remove the KiB suffix from an error message using bytes

Signed-off-by: David Scott <dave.scott@citrix.com>
Merge pull request #72 from djs55/CA-135934

CA-135934: remove the KiB suffix from an error message using bytes
Merge pull request #70 from johnelse/ca-136054

CA-136054: Make path to vgpu configurable
CA-116551: Remove the extra log files created by xenguest.
Signed-off-by: Akshay <akshay.ramani@citrix.com>
Merge pull request #73 from akshayramani/CA-116551

CA-116551: Prevent xenguest from creating extra log files.
Merge pull request #61 from akshayramani/CA-127183

CA-127183: qemu-dm does not accept the '-priv' flag anymore
Merge pull request #66 from djs55/arm/shadow-allocation-set

arm: shadow_allocation_set is not supported; log failure and continue
0.9.37 release

Signed-off-by: Jon Ludlam <jonathan.ludlam@citrix.com>
Merge pull request #75 from jonludlam/0.9.37-release

0.9.37 release
CA-134972: fix a tight loop getting xenops updates

Each barrier injected among the xenops events now holds a snapshot of
the event id counter as well as the set of events. The get function uses
this to select only the barriers newer than the "from" parameter, and
returns it as the "id of latest thing found" if it is newer than all the
events. If there are no barriers or events to return then the function
waits: this behaviour is unchanged, but now there will be no barriers to
return if there are barriers but they are all too old to be of interest
to the caller.

This means a client no longer keeps calling repeatedly with the same
"from" and getting back the same result (one or more barriers, no events
and the same next-id as the "from" param).

Because each barrier has an extra int associated with it, the formats
for RPC and Dump have changed in a backwards-incompatible way.

This is based on commit b68d6003 in the xs64bit-ring3 branch of the
xen-api repository.

Signed-off-by: Thomas Sanders <thomas.sanders@citrix.com>
Merge pull request #76 from thomassa/tr3-xenopsd-tightloop-CA-134972

CA-134972: fix a tight loop getting xenops updates