search for: xsconstants

...* mv /lib/tls /lib/tls.disabled ** ** Offending process: xend (pid=1045) ** *************************************************************** *************************************************************** Continuing... /usr/lib/python/xen/util/xsconstants.py:110: FutureWarning: hex/oct constants > sys.maxint will return positive values in Python 2.4 and up INVALID_SSIDREF = 0xFFFFFFFF etc/xen/scripts/xen-network-common.sh sh: =~: unknown operand sh: =~: unknown operand *ifdown: interface eth0 not configured* ip: SIOCSIFNAME: Device or resource...

- The patch does away with the autogenerated xsm.py file and introduces a config parameter in xend-config.sxp to determine the security module. The parameter is (xsm_module_name {acm, dummy, flask}). The default setting/option is dummy. .hgignore is also updated to stop ignoring xsm.py on commits. - The patch has created an xsconstant for XS_POLICY_FLASK and updated the toolchain to check the

...xen-3.2-1/bin/../lib/python/xen/util/xsm/dummy/xen.py", O_RDONLY) = -1 ENOENT (No such file or directory) open("/usr/lib/xen-3.2-1/bin/../lib/python/xen/util/xsm/dummy/xen.pyc", O_RDONLY) = -1 ENOENT (No such file or directory) stat("/usr/lib/xen-3.2-1/bin/../lib/python/xen/util/xsconstants", 0x7ffffffec7e0) = -1 ENOENT (No such file or directory) open("/usr/lib/xen-3.2-1/bin/../lib/python/xen/util/xsconstants.so", O_RDONLY) = -1 ENOENT (No such file or directory) open("/usr/lib/xen-3.2-1/bin/../lib/python/xen/util/xsconstantsmodule.so", O_RDONLY) = -1 ENOENT...

The following series of 10 patches is a merge of the xenfb and xenconsoled functionality into the qemu-dm code. The general approach taken is to have qemu-dm provide two machine types - one for xen paravirt, the other for fullyvirt. For compatability the later is the default. The goals overall are to kill LibVNCServer, remove alot of code duplication and/or parallel impls of the same concepts, and