I was wondering about the progress towards dom0 support in F15. The
feature page [1] hasn't been updated for a while, so I'm not clear on
how close the feature is to completion.
Specifically, I am looking to find out what kind of testing has been
done or is being done for this new feature. As far
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-k
On Fri, 7 Oct 2011 14:11:04 +0100 (BST)
M A Young 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 bugzi
On Sun, 16 Oct 2011 14:30:22 +0300
Pasi Kärkkäinen 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 -
On Fri, 14 Oct 2011 21:04:17 +0300
Marko Ristola 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 r
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 update
On Mon, 24 Oct 2011 20:56:47 +0100 (BST)
M A Young 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 triggeri
