Xen dom0 / Fedora 16 Schedule Reminders - Feature Submission and Feature Freeze
by Pasi Kärkkäinen
Hello,
Is someone currently working on Xen dom0 support for Fedora 16 ?
Upstream Linux kernel supports Xen dom0 now, so we should definitely
get dom0 support back to Fedora for F16.
http://fedoraproject.org/wiki/Features/XenPvopsDom0
https://bugzilla.redhat.com/show_bug.cgi?id=658387
https://bugzilla.redhat.com/show_bug.cgi?id=668063
Feature submission deadline for F16 is today..
-- Pasi
In-Reply-To: <4E1B5992.5030403(a)redhat.com>
On Mon, Jul 11, 2011 at 01:14:10PM -0700, Robyn Bergeron wrote:
> A few friendly reminders:
>
> * The Feature Submission deadline for Fedora 16 is *tomorrow*, July 12.
> The current process for submitting a feature for Fedora 16 can be seen
> here: http://fedoraproject.org/wiki/Features/Policy
>
> * Feature Freeze comes quickly after the Feature Submission deadline, on
> July 26. Please note that at this point, Features should be
> *substantially complete and in a testable state.* For more information
> on the Feature Freeze policy, please read:
> http://fedoraproject.org/wiki/ReleaseEngineering/FeatureFreezePolicy
>
> And finally.... for those of you interested in seeing how the Feature
> List is shaping up for Fedora 16, it is up to date with the latest and
> greatest approvals from today's FESCo meeting.
>
> http://fedoraproject.org/wiki/FeatureList
>
> This is where I'm going to put on my Gentle Reminder Hat, and give
> everyone a chance to go into their individual feature pages and update
> their percentage complete, and update their "Last Updated" date, which I
> will apply to the main FeatureList page. Your efforts here are
> appreciated, and help a number of groups understand how close you are to
> completion, or conversely, if you are at risk of not making deadlines.
>
> If percentages don't start getting updated, and "last-updated" dates
> aren't getting touched, I'll be reaching out to folks individually, but
> I would prefer to see that people take the initiative and keep those
> things up. Otherwise I have to get out the not-so-Gentle-Reminder-Hat,
> and frankly, I don't look very good in that one.
>
> Communication is the key here. If you believe you are *at risk* of not
> making the Feature Freeze, please update your feature page accordingly.
>
> The rest of the schedule, as always, can be seen here:
> https://fedoraproject.org/wiki/Releases/16/Schedule
>
> Thanks!
>
> -Robyn
> _______________________________________________
> devel-announce mailing list
> devel-announce(a)lists.fedoraproject.org
> https://admin.fedoraproject.org/mailman/listinfo/devel-announce
> --
> devel mailing list
> devel(a)lists.fedoraproject.org
> https://admin.fedoraproject.org/mailman/listinfo/devel
12 years, 9 months
Re: [Fedora-xen] [Xen-devel] Xen4.1.0 and Fedora15 Block device bug?
by Travis
On Sat, Jul 2, 2011 at 2:02 AM, Ian Campbell <Ian.Campbell(a)citrix.com>wrote:
> On Sat, 2011-07-02 at 05:15 +0100, Fajar A. Nugraha wrote:
> >
> > Second part, F15's boot/config-2.6.38.6-26.rc1.fc15.x86_64 has these
> > entries:
> > CONFIG_XEN_PLATFORM_PCI=m
> > CONFIG_XEN_BLKDEV_FRONTEND=m
> >
> > So if you could add xen-platform-pci.ko and xen-blkfront.ko to the
> > install initrd, you should be able to use PV drivers directly. Not
> > sure what's the easiest way to do it though (maybe unpack initrd, add
> > some files, and repack it).
>
> Has somebody reported this as a bug against F15? Either the initrd tool
> (drakut?) should understand when xen-platform-pci is needed or it should
> be =y. It's a very small amount of code so building it in is not
> unreasonable.
>
> Ian.
>
> I'm filing one now.
--
"Eating and sleeping are the only activities that should be allowed
to interrupt a man's enjoyment of his cigar." - Mark Twain
12 years, 9 months
creating a private network of virtual machines
by Gergely Buday
Hi there,
I would like to create a network of virtual machines, divided into
private subnets so that one can exercise network configuration,
routing etc. on them.
Is Xen the right solution for me? I do not want to run heavy software
on the machines, only the networking.
And, is there any open source software that helps creating such
network topologies?
Thanks
- Gergely
12 years, 9 months
Re: [Fedora-xen] [Xen-devel] Xen4.1.0 and Fedora15 Block device bug?
by Travis
On Sat, Jul 2, 2011 at 12:15 AM, Fajar A. Nugraha <list(a)fajar.net> wrote:
> On Sat, Jul 2, 2011 at 10:50 AM, Travis <corasian(a)gmail.com> wrote:
> > I'm using HVM, and I've attached screenshots from the requested output
> > (+lspci). No other OS is giving me this problem, and
> i'm consistently able
> > to reproduce it. What's your take?
>
> So no block device detected, and no xen-related module loaded. That's
> weird.
>
> Two parts of this problem.
>
> The first part is why would the emulated block device be missing. It
> should still be there if PV drivers was not loaded.
> Are you using the same dom0 (xen and dom0 kernel) and domU config file
> for both the working F14 and F15? If yes, try:
> - "xen_emul_unplug=never" on kernel command line. See
> http://www.kernel.org/doc/Documentation/kernel-parameters.txt
> - make sure you use "hda" on domU config file
>
> Awesome, the "xen_emul_unplug=never" arg fixed it. I tossed it in and it
booted up and installed just fine. Thanks!!! And the doc you linked
is definitely going in my sysadmin toolbox. Sweet!
> Second part, F15's boot/config-2.6.38.6-26.rc1.fc15.x86_64 has these
> entries:
> CONFIG_XEN_PLATFORM_PCI=m
> CONFIG_XEN_BLKDEV_FRONTEND=m
>
> So if you could add xen-platform-pci.ko and xen-blkfront.ko to the
> install initrd, you should be able to use PV drivers directly. Not
> sure what's the easiest way to do it though (maybe unpack initrd, add
> some files, and repack it).
>
I had tried the fed15 rawhide version from fedora's virtualization-xendomu
test day (april) last night, and it includes the support (it reads the v
disk as a xen device, even) so hopefully it will be polished up (it was
quite a bit rough looking still) and pushed out in the next release/update.
>
> --
> Fajar
>
12 years, 9 months
Xen4.1.0 and Fedora15 Block device bug?
by Travis
Hi guys,
I'm an administrator for a small cluster running ganeti2.3.1/xen4.1.0/drbd83
on centos5.6, with predominantly fedora14 instances. We've been running the
fedora 14 images pretty well, not many issues. However, I've noticed that in
an attempt to install fedora 15, the virtualized block devices are
unrecognized by anaconda. has anyone else seen this or is this a known
issue?
-Corasian
12 years, 9 months
