| Summary: | Virt-manager does not start xen machines | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | ojpp99 <ojpp99> |
| Component: | kernel | Assignee: | Kernel Maintainer List <kernel-maint> |
| Status: | CLOSED ERRATA | QA Contact: | |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 16 | CC: | crobinso, gansalmon, itamar, jonathan, kernel-maint, ketuzsezr, madhu.chinakonda, xen-maint |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | kernel-3.1.0-0.rc10.git0.1.fc16 | Doc Type: | Bug Fix |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2011-10-20 04:02:26 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
Hmm, that looks like it could be related to CONFIG_XEN_BALLOON_MEMORY_HOTPLUG=y That was it. I built a kernel with CONFIG_XEN_BALLOON_MEMORY_HOTPLUG not set and was able to create guests. Dave, would it be possible to modify the .config file to disable the above mention config option? Summary of bug: When a guest is launched, xend tries to balloon dom0 (the initial Linux guest) down to an Ok size to contain the guest. Sadly, xend does not support memory hotplugging and tries to use the old balloon SysFS calls - and since they are not present it bails out. We need to fix the xend (and xl) to handle the memory hotplug - but that is not going to happen in F16 release. So as a workaround, lets disable the Xen memory hotplug until the tools are ready. You're essentially the expert, so I don't think we'll have any problems disabling the option in the config. I do have 2 questions though: 1) Is this going to impact non virt-manager environments, such as EC2 or others? (I would guess no, but I hate guessing.) 2) Do you want to either open a bug against xen to track the fixups needed for the tools, or leave this bug against xen and just change the kernel config? I've disabled the kernel config option in f16/rawhide now. Should be in the next kernel builds. I guess we'll go ahead and track the kernel change with this bug. You might want to open one for xen to track the changes needed. Josh, Thanks for disabling the kernel option. I will track the xen changes on another bug/xen-devel mailing list. kernel-3.1.0-0.rc10.git0.1.fc16 has been submitted as an update for Fedora 16. https://admin.fedoraproject.org/updates/kernel-3.1.0-0.rc10.git0.1.fc16 Package kernel-3.1.0-0.rc10.git0.1.fc16: * should fix your issue, * was pushed to the Fedora 16 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing kernel-3.1.0-0.rc10.git0.1.fc16' as soon as you are able to, then reboot. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2011-14609 then log in and leave karma (feedback). kernel-3.1.0-0.rc10.git0.1.fc16 has been pushed to the Fedora 16 stable repository. If problems still persist, please make note of it in this bug report. |
Description of problem: Virt-manager can't start machines if kernel version = 3.1, it works with 3.0 kernels. The messages are : Erreur lors du démarrage du domaine: POST operation failed: xend_post: error from xen daemon: (xend.err 'Failed to query current memory allocation of dom0.') Traceback (most recent call last): File "/usr/share/virt-manager/virtManager/asyncjob.py", line 44, in cb_wrapper callback(asyncjob, *args, **kwargs) File "/usr/share/virt-manager/virtManager/asyncjob.py", line 65, in tmpcb callback(*args, **kwargs) File "/usr/share/virt-manager/virtManager/domain.py", line 1050, in startup self._backend.create() File "/usr/lib/python2.7/dist-packages/libvirt.py", line 510, in create if ret == -1: raise libvirtError ('virDomainCreate() failed', dom=self) libvirtError: POST operation failed: xend_post: error from xen daemon: (xend.err 'Failed to query current memory allocation of dom0.') Virt-managet : 0.9.0 How reproducible: Yes, every time I try I get the message Steps to Reproduce: 1) Use a 3.1 kernel as DOM0 2) Launch a VM 3) That's it Actual results: The given message Expected results: A running machine ! Additional info: That bug is specific to 3.1 kernels, all is OK with 3.0 Xen version : 4.1.1 Regards