2016-03-05 4:13 GMT+01:00 stan <[email protected]>: > > dnf list installed | grep -i qemu > > Over to the right it will tell you the repository the installed package > came from. I suspect you will find that it will be fedora or updates, > and not virt-preview. > > 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
> > Why do you want to patch anything? If there are updates in the fedora > repositiories, why not just update your system using them? IIRC, the > results from your system showed that the fedora update packages were > 2.5.0 as well. > > Is there some customization that you are adding to the standard > source? 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. > Patch it with what? You haven't mentioned any patches before, that I > recall. > One of those : https://www.kraxel.org/cgit/qemu/patch/?id=0d60ce8e719b5c49ba69c42080f7724fc7de5c1f I didn't, because i thought after the update it will be easy, i was obviously wrong. No, rpmbuild builds a binary RPM package from a src.rpm that can then be > installed with dnf. The advantage of doing this is that the packaging > system is aware of the new package. I see, creating the rpm then install with dnf, thanks. > > And this is how to build a custom kernel. Parts of that will also help > you understand what you have to do with rpmbuild in order to build the > binary RPMs you want to install. > http://fedoraproject.org/wiki/Building_a_custom_kernel 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 thought it was clear from our previous exchange that all you needed to > do was run dnf upgrade to update the qemu packages already installed on > your system. At least that is what I took away. 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
-- users mailing list [email protected] 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
