dracut in Fedora 20 doesn't know about *-pci modules (which were split
of *-hcd). So add them manually, in all flavors (ehci, ohci, xhci).
FixesQubesOS/qubes-issues#1517
(cherry picked from commit f66be6c943)
This allows to clear the flag when for some reason it wasn't cleared
immediately after installing updates.
FixesQubesOS/qubes-issues#1511
(cherry picked from commit 6921400a7a)
Unfortunate side effect (to be solved at Qubes Manager side): it will
block Qubes Manager until all updates are installed (not only updater
launched).
FixesQubesOS/qubes-issues#1511
(cherry picked from commit cb6a52a652)
Otherwise if the child process isn't reading its stdin at that time, it
would deadlock the whole qrexec connection (for example preventing
reading the data from the child, which may be a cause of that deadlock).
QubesOS/qubes-issues#1347
(cherry picked from commit 0c288aa355)
Do not reimplement manual VM state checking in qrexec-policy.
`qubes.xml` is loaded anyway, so just use QubesVM object to check if
domain is running.
FixesQubesOS/qubes-issues#1283
(cherry picked from commit 63e74a01d3)
The specification doesn't cover how to boot Xen (or any other multiboot
binary), but the sole presence of such directory changes dracut default
path. So get rid of that directory.
Main qubes-core-dom0 should not be installed as part of installer image,
but os-prober dependency pulls that in. So move it into
qubes-core-dom0-kernel-install subpackage. After all this is where grub
config regeneration code is placed, so it is more logical place.
Split kernel-install hook into separate package, as only this part is
needed by the installer. This will prevent installing all the Qubes/Xen
staff in the installer, especially udev scripts and xenstored, which
doesn't play well with anaconda.
Since we now allow using Fedora kernel, add a script to generate proper
bootloader configuration then. Standard Fedora mechanism relies on
Boot Loader Specification support in grub2, which sadly does not support
Xen, so it is useless in Qubes.
Make sure that all the data from local process is sent (including final
EOF), before handling its exit code - which would include terminating
qrexec-client process.
In such case, we can't set module parameters in initramfs. But we can
bind the driver to appropriate devices manually - which is also doable
in case of module.
Apparently when package is signed with DSA key, rpm -K output is totally
different. This is the case for bumblebee package on rpmfusion.
Fixesqubesos/qubes-issues#988
