Bug 1218814

Summary: ksm.service - ksmctl path
Product: [Fedora] Fedora Reporter: poma <pomidorabelisima>
Component: qemuAssignee: Fedora Virtualization Maintainers <virt-maint>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 22CC: amit.shah, berrange, cfergeau, crobinso, dwmw2, itamar, pbonzini, rjones, scottt.tw, virt-maint
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: qemu-2.3.0-3.fc22 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-05-11 19:02:06 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
Fix Exec/Start/Stop path none

Description poma 2015-05-06 00:01:50 UTC
Created attachment 1022350 [details]
Fix Exec/Start/Stop path

I hope this will not wait 4 months. :)

Comment 1 poma 2015-05-06 00:02:46 UTC
Also for Fedora 22.

Comment 2 Cole Robinson 2015-05-06 16:50:44 UTC
Hmm sorry about that, will push your patch shortly

Comment 3 Fedora Update System 2015-05-06 23:16:23 UTC
qemu-2.3.0-3.fc22 has been submitted as an update for Fedora 22.
https://admin.fedoraproject.org/updates/qemu-2.3.0-3.fc22

Comment 4 Fedora Update System 2015-05-10 23:48:23 UTC
Package qemu-2.3.0-3.fc22:
* should fix your issue,
* was pushed to the Fedora 22 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing qemu-2.3.0-3.fc22'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2015-7809/qemu-2.3.0-3.fc22
then log in and leave karma (feedback).

Comment 5 Fedora Update System 2015-05-11 19:02:06 UTC
qemu-2.3.0-3.fc22 has been pushed to the Fedora 22 stable repository.  If problems still persist, please make note of it in this bug report.