[Fedora-xen] Grubby Issues with F16 Dom0
Just as a heads up, there seem to be a couple of issues with grubby and
the grub.cfg submenus used for Xen right now. My system still boots
after triggering any of these but it's usually not running Xen and not
always running the kernel I want it to be running.
Kernel submenu entries aren't updated w/ kernel updates:
- https://bugzilla.redhat.com/show_bug.cgi?id=748551
This can be worked around by regenerating grub.cfg @ every kernel
update ('grub2-mkconfig -o /boot/grub2/grub.cfg')
There are a couple other grubby issues that I haven't hit naturally yet
(not difficult to provoke, though). Both can be worked around by
regenerating grub.cfg after making kernel changes but before rebooting.
- Extra entries are being removed from grub.cfg @ kernel pkg removal
* https://bugzilla.redhat.com/show_bug.cgi?id=744717
* I haven't personally seen this during kernel removal @ upgrade time
but it's something to watch out for if you are removing kernels
- Whitespace is removed from grub default once grub.cfg is processed
by grubby.
* https://bugzilla.redhat.com/show_bug.cgi?id=742720
* 748551 also stomps on the default in grub.cfg, so I haven't seen
this yet but it could show up.
signature.asc
Description: PGP signature
--
xen mailing list
xen@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/xen
Re: [Fedora-xen] Grubby Issues with F16 Dom0
On Mon, 24 Oct 2011 20:56:47 +0100 (BST) M A Young m.a.yo...@durham.ac.uk wrote: On Mon, 24 Oct 2011, Tim Flink wrote: Just as a heads up, there seem to be a couple of issues with grubby and the grub.cfg submenus used for Xen right now. My system still boots after triggering any of these but it's usually not running Xen and not always running the kernel I want it to be running. I have seen what I suspect is another one though I haven't investigated fully yet to confirm it. I think that if you delete a kernel with a xen entry it can remove a submenu opening clause but not the corresponding closing } which is bad if you have the xen hypervisor installed in a guest as it upsets pygrub. Yeah, that's 744717. The bug isn't incredibly clear and I didn't do a very good job of summarizing it. If you look at the before and after grub.cfg files, you can see it though. How often would that happen in a guest? I don't think that I have submenu entries in any of my DomUs. Tim signature.asc Description: PGP signature -- xen mailing list xen@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/xen
Re: [Fedora-xen] F16 Xen dom0 SElinux problems with LVM volumes for domUs
On Sun, 16 Oct 2011 14:30:22 +0300 Pasi Kärkkäinen pa...@iki.fi wrote: Hello, I need to do setenforce 0 before I'm able to install Xen VMs with LVM volumes as disk backends.. Should I file a bugzilla entry about this? I wonder if you're hitting the same thing that I filed last week: - 745996 - AVC denials preventing start of Xen domain [1] I'm generating my DomUs outside of Xen, so I don't see it at install time but I'm wondering if they might be related. Are the AVC denials the same as the ones I listed there? Tim [1] https://bugzilla.redhat.com/show_bug.cgi?id=745996 signature.asc Description: PGP signature -- xen mailing list xen@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/xen
Re: [Fedora-xen] virt-manager destroying the guest leaves a ghost in xend.
On Fri, 14 Oct 2011 21:04:17 +0300 Marko Ristola marko.rist...@kolumbus.fi wrote: Hi Konrad. I can easilly repeat a following situation: 1. Start up a guest on Virt-Manager. The quest is created via virt-manager, Fedora 14, as a network install. 2. Shut it down via Virt-Manager's menus. 3. Wait until Xen reports on xend.log: Domain has shutdown: name=fedora14 id=2 reason=poweroff On virt-manager, guest's status remains Running. If I try any operations for the guest, I get a Python exception, something like you found, but related to the operation. 4. Disconnect from localhost(xen) on Virt-Manager. 5. Connect into localhost(xen) on Virt-Manager. 6. Now the guest status of fedora14 is Shutoff. 7. Now we can go back to phase 1 and start again. So the bug is (on high level) something like: Xen turns off the guest, but virt-manager won't get notified, or won't detect, about the state change of Xen quest: Running - Shutoff. So my hypothesis on your problem is, that Xen already turned guest's power off, and virt-manager didn't notice it. So virt-manager asks Xen to do commands which aren't supported for turned off quest. Regards, Marko Ristola I really need to be better about communicating the xen related bugs that I'm filing. Konrad's initial question sounded slightly different but I never got around to testing with the method that he listed. Part of this sounds like a virt-manager bug that I filed last week: * 746007 - Status of Xen guests is not updated in virt-manager [1] Interesting note: - In this case, status is correct for 'virsh list --all' and 'xm list' even though virt-manager isn't showing DomU status correctly Tim [1] https://bugzilla.redhat.com/show_bug.cgi?id=746007 signature.asc Description: PGP signature -- xen mailing list xen@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/xen
[Fedora-xen] High Volume of Syslog Messages on Fedora 16 Dom0
I just upgraded an older Opteron machine that I've been using as Xen Dom0 from RHEL5 to Fedora 16. When I boot with Xen, my syslog is full of messages (several per second) like the following: kernel: [1.226209] powernow-k8: fid trans failed, fid 0x2, curr 0x0 kernel: [1.226271] powernow-k8: transition frequency failed Things seem to be working (I can use xm list) but I would rather not have my system log be quite that noisy. Unfortunately, I'm quite sure where to go from here to debug and fix the issue; any suggestions? Tim Fedora 16 3.1.0-0.rc8.git0.1.fc16.x86_64 xen-4.1.1-6 2x Dual Core AMD Opteron(tm) Processor 865 HE signature.asc Description: PGP signature -- xen mailing list xen@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/xen
Re: [Fedora-xen] High Volume of Syslog Messages on Fedora 16 Dom0
On Fri, 7 Oct 2011 14:11:04 +0100 (BST) M A Young m.a.yo...@durham.ac.uk wrote: On Fri, 7 Oct 2011, Tim Flink wrote: There is a bug on this issue at https://bugzilla.redhat.com/show_bug.cgi?id=739159 Thanks for the pointer. For some reason, I didn't find that when I searched through bugzilla earlier. The kernel maintainers claim that isn't a kernel bug and that it's a Xen issue. I have filed the bug upstream as: http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1789 Thanks, Tim signature.asc Description: PGP signature -- xen mailing list xen@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/xen
