On Sat, 5 Mar 2016 05:51:21 +0100 thibaut noah <thibaut.noah@xxxxxxxxx> wrote: > 2016-03-05 4:13 GMT+01:00 stan <stanl-fedorauser@xxxxxxxxxxx>: > > All the installed packages are coming from virt-preview actually : > ipxe-roms-qemu.noarch > libvirt-daemon-driver-qemu > qemu-common > qemu-guest-agent > qemu-img > qemu-kvm > qemu-systen-x86 OK, that's great! Because it means that you can replace them with the latest fedora packages without a problem. > The guys from redhat made some patches for qemu that are not currently > upstream, allow qemu user to transfer mouse and keyboard betweem host > and guest by pressing both ctrl keys. So it shouldn't be a problem to use the fedora packages directly. And they would have the patches already. > I build a custom kernel already (same reason, i needed a patch not > available upstream) so i understand the basics of creating a rpm > package. The problem i have on hand is like you stated above qemu > package itself is not installed and that seems to be the package i'm > suppose to patch. What i don't get is how the system is suppose to > use something it didn't use before and what my system is actually > using since qemu is not there (i checked the packages list from the > repo, i have everything except qemu), does qemu-kvm include all qemu > functions or does libvirt not need qemu at all as long as you don't > use qemu command lines inside your libvirt domain xml ? that would > explain things. I wonder if the qemu at virt-preview is a master package, that only installs other packages. I'm not a packager, but I think there are packages that are sort of like virtual functions. > That was only step one of what i needed actually but like i said > above, thought step 2 would go down easy. > Long story short 2.5 is needed to apply the patches and since i > misunderstood version number i thought i had 2.2.5, that's why i > wanted to update before. > After patching i would just add the patch commands with something > like this : > http://blog.vmsplice.net/2011/04/how-to-pass-qemu-command-line-options.html So, because you already have 2.5.0, you don't actually need to update in order to patch? I think at this point you've exhausted me as a resource, and need someone more knowledgeable. Because, what I would do would be to download the fedora packages to the local machine (they're at 2.5.0-8), and install them using the dnf -C upgrade command. That way, you get the patches without any need to mess around with source packages. It might mess up the virt-preview repo if you need it in future. But if your system is running without the qemu package from virt-preview, you don't need it, and can get back in sync with fedora. As a precaution, you could get the binary packages for the qemu stuff you have installed from virt-preview. And if you have to downgrade because the fedora packages don't work, you could just do a dnf -C downgrade with those packages. But it is possible I don't really understand your issue, and that might be the wrong thing to do. -- users mailing list users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
