s-intac.patch):' Patch #3010 (xsa179-qemut-unstable-0005-vga-make-sure-vga-register-setup-for-vbe-stays-intac.patch): + /bin/cat /builddir/build/SOURCES/xsa179-qemut-unstable-0005-vga-make-sure-vga-register-setup-for-vbe-stays-intac.patch + /usr/bin/patch -p1 --fuzz=2 patching file hw/vga.c Patch #3011 (xsa180-qemut.patch): + echo 'Patch #3011 (xsa180-qemut.patch):' + /bin/cat /builddir/build/SOURCES/xsa180-qemut.patch + /usr/bin/patch -p1 --fuzz=2 patching file vl.c Hunk #1 succeeded at 3753 (offset 1 line). Hunk #2 succeeded at 3808 (offset 1 line). + popd ~/build/BUILD/xen-4.4.4 Patch #4000 (xen-44-tools-xendomains-create-lockfile-uncond.patch): + echo 'Patch #4000 (xen-44-tools-xendomains-create-lockfile-uncond.patch):' + /bin/cat /builddir/build/SOURCES/xen-44-tools-xendomains-create-lockfile-uncond.patch + /usr/bin/patch -p1 --fuzz=2 can't find file to patch at input line 45 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -------------------------- |From 1c7fa3dc039487d18ad0c6fb6b773c831dca5e5d Mon Sep 17 00:00:00 2001 |From: George Dunlap |Date: Wed, 11 May 2016 12:14:45 +0100 |Subject: [PATCH] tools/xendomains: Create lockfile on start unconditionally | |At the moment, the xendomains init script will only create a lockfile |if when started, it actually does something -- either tries to restore |a previously saved domain as a result of XENDOMAINS_RESTORE, or tries |to create a domain as a result of XENDOMAINS_AUTO. | |RedHat-based SYSV init systems try to only call "${SERVICE} shutdown" |on systems which actually have an actively running component; and they |use the existence of /var/lock/subsys/${SERVICE} to determine which |systems are running. | |This means that at the moment, on RedHat-based SYSV systems (such as |CentOS 6), if you enable xendomains, and have XENDOMAINS_RESTORE set |to "true", but don't happen to start a VM, then your running VMs will |not be suspended on shutdown. | |Since the lockfile doesn't really have any other effect than to |prevent duplicate starting, just create it unconditionally every time |we start the xendomains script. | |The other option would have been to touch the lockfile if |XENDOMAINS_RESTORE was true regardless of whether there were any |domains to be restored. But this would mean that if you started with |the xendomains script active but XENDOMAINS_RESTORE set to "false", |and then changed it to "true", then xendomains would still not run the |next time you shut down. This seems to me to violate the principle of |least surprise. | |Signed-off-by: George Dunlap |Acked-by: Wei Liu |Acked-by: Olaf Hering |Release-acked-by: Wei Liu |--- | tools/hotplug/Linux/xendomains.in | 6 +++--- | 1 file changed, 3 insertions(+), 3 deletions(-) | |diff --git a/tools/hotplug/Linux/xendomains.in b/tools/hotplug/Linux/xendomains.in |index 727cd42..334d244 100644 |--- a/tools/hotplug/Linux/xendomains.in |+++ b/tools/hotplug/Linux/xendomains.in -------------------------- File to patch: Skip this patch? [y] Skipping patch. 2 out of 2 hunks ignored RPM build errors: error: Bad exit status from /var/tmp/rpm-tmp.zmC6bN (%prep) Bad exit status from /var/tmp/rpm-tmp.zmC6bN (%prep) Child return code was: 1 EXCEPTION: Command failed. See logs for output. # bash --login -c /usr/bin/rpmbuild -bb --target x86_64 --nodeps /builddir/build/SPECS/xen.spec Traceback (most recent call last): File "/usr/lib/python2.6/site-packages/mockbuild/trace_decorator.py", line 88, in trace result = func(*args, **kw) File "/usr/lib/python2.6/site-packages/mockbuild/util.py", line 547, in do raise exception.Error("Command failed. See logs for output.\n # %s" % (command,), child.returncode) Error: Command failed. See logs for output. # bash --login -c /usr/bin/rpmbuild -bb --target x86_64 --nodeps /builddir/build/SPECS/xen.spec LEAVE do --> EXCEPTION RAISED