- Update to Xen 4.4.0 RC1 c/s 28233

- Drop 32bit support from spec file
- Dropped 520d417d-xen-Add-stdbool.h-workaround-for-BSD.patch

OBS-URL: https://build.opensuse.org/package/show/Virtualization/xen?expand=0&rev=282

xend-config.patch

@@ -0,0 +1,54 @@
+Index: xen-4.2.0-testing/tools/hotplug/Linux/init.d/sysconfig.xendomains
+===================================================================
+--- xen-4.2.0-testing.orig/tools/hotplug/Linux/init.d/sysconfig.xendomains
++++ xen-4.2.0-testing/tools/hotplug/Linux/init.d/sysconfig.xendomains
+@@ -98,7 +98,6 @@ XENDOMAINS_RESTORE=true
+ # Note that the script tries to be clever if both RESTORE and AUTO are 
+ # set: It will first restore saved domains and then only start domains
+ # in AUTO which are not running yet. 
+-# Note that the name matching is somewhat fuzzy.
+ #
+ XENDOMAINS_AUTO=/etc/xen/auto
+ 
+Index: xen-4.2.0-testing/tools/examples/xend-config.sxp
+===================================================================
+--- xen-4.2.0-testing.orig/tools/examples/xend-config.sxp
++++ xen-4.2.0-testing/tools/examples/xend-config.sxp
+@@ -58,11 +58,12 @@
+ 
+ 
+ #(xend-http-server no)
+-#(xend-unix-server no)
++(xend-unix-server yes)
+ #(xend-tcp-xmlrpc-server no)
+ #(xend-unix-xmlrpc-server yes)
++# Only enable xend-relocation-server on trusted networks as it lacks
++# encryption and authentication.
+ #(xend-relocation-server no)
+-(xend-relocation-server yes)
+ #(xend-relocation-ssl-server no)
+ #(xend-udev-event-server no)
+ 
+@@ -170,7 +171,12 @@
+ # two fake interfaces per guest domain.  To do things like this, write
+ # yourself a wrapper script, and call network-bridge from it, as appropriate.
+ #
+-(network-script network-bridge)
++# SuSE users note:
++# On openSUSE >= 11.1 and SLES >= 11, networks should be configured using
++# native platform tool - YaST.  vif-bridge and qemu-ifup can be used to
++# connect vifs to the YaST-managed networks.
++#(network-script network-bridge)
++(network-script )
+ 
+ # The script used to control virtual interfaces.  This can be overridden on a
+ # per-vif basis when creating a domain or a configuring a new vif.  The
+@@ -203,7 +209,7 @@
+ # dom0-min-mem is the lowest permissible memory level (in MB) for dom0.
+ # This is a minimum both for auto-ballooning (as enabled by
+ # enable-dom0-ballooning below) and for xm mem-set when applied to dom0.
+-(dom0-min-mem 196)
++(dom0-min-mem 512)
+ 
+ # Whether to enable auto-ballooning of dom0 to allow domUs to be created.
+ # If enable-dom0-ballooning = no, dom0 will never balloon out.