From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: "W. Michael Petullo" <mike@flyn.org>
Cc: xen-devel@lists.xensource.com, m.a.young@durham.ac.uk
Subject: Re: Fedora Core 16 + Xen
Date: Mon, 29 Aug 2011 16:57:03 -0400 [thread overview]
Message-ID: <20110829205703.GA18697@dumpdata.com> (raw)
In-Reply-To: <20110829201554.GA18533@imp.local>
On Mon, Aug 29, 2011 at 03:15:54PM -0500, W. Michael Petullo wrote:
> > I was quite excited to see that with Fedora Core 16 I can just do:
> >
> > 'yum install xen' and the hypervisor is installed.
> >
> > Sadly the grub is not updated so nothing gets loaded. Should I report
> > bugs against this on bugzilla.redhat.com or just send them to your personally?
> >
> > libvirt seems to have forgotten about Xen too.. but that is a different issue.
> >
> > I played with running HVM and PV guests using 'xl' and they worked right
> > out of box. Neat!!
>
> See also in Red Hat Bugzilla:
>
> grub2 --class xen: initramfs missing, booting under XEN fails (found on Fedora 16)
> https://bugzilla.redhat.com/show_bug.cgi?id=728775
>
> Patch to allow mbkernel and mbargs to be read from /etc/sysconfig/kernel
> https://bugzilla.redhat.com/show_bug.cgi?id=658387
>
> Grubby does not handle "template" that uses module key
> https://bugzilla.redhat.com/show_bug.cgi?id=668063
>
> and:
>
> The Xen feature proposal for Fedora 16
> http://fedoraproject.org/wiki/Features/XenPvopsDom0
Oh, ok, so what is the next step to talk to the developers on those
bugs?
next prev parent reply other threads:[~2011-08-29 20:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-29 19:00 Fedora Core 16 + Xen Konrad Rzeszutek Wilk
2011-08-29 20:15 ` W. Michael Petullo
2011-08-29 20:57 ` Konrad Rzeszutek Wilk [this message]
2011-09-14 5:15 ` Andy Burns
2011-09-15 8:17 ` Konrad Rzeszutek Wilk
2011-09-22 2:15 ` Andy Burns
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20110829205703.GA18697@dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=m.a.young@durham.ac.uk \
--cc=mike@flyn.org \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.