[LAD] Gone virtually Meego 1.1 in Fedora -- lots of questions....

Niels Mayer nielsmayer at gmail.com
Mon Oct 25 06:16:11 UTC 2010

On Sun, Oct 24, 2010 at 2:03 PM, Paul Davis <paul at linuxaudiosystems.com> wrote:
> the mainstream kernel has merged *parts* of the RT patch. it does not
> have all of it, and the last time i heard gleixner talk about it (last
> fall, in portland, OR at the linux plumbers conf) he felt that it
> unlikely that it would ever all be merged.

Paul -- thanks for the clarifications. Hopefully somebody from the
Meego community will be able to respond further to the specific RT
capabilities (or lack thereof) in Meego 1.1.

> configuring your system for RT usage has ABSOLUTELY ZERO to do with
> the presence or absence of the RT patch. RT scheduling, mlock and
> other features used by RT applications are all available and usable on
> all modern linux kernels. the RT patch just makes them work better, on
> some machines, some of the time.

True -- I use them currently with a stock fedora kernel (which is
where I run my KVMs out of). This functions adequately for most
low-channel purposes using tools like jack, ardour and qtractor -- as
long as I'm not running certain other applications concurrently (such
as a web browser doing heavy javascript processing, like browsing

However, "rtirq" is one such configuration change which does have
something to do with the presence of the RT patch, and appears to be
in inequality with "absolutely zero." especially the all-capitalized
variety. :-)


Regarding virtualization and multimedia devices access, Fedora 14
claims "Easier virtualization for end users. From the creators of KVM
comes Spice (Simple Protocol for Independent Computing Environments).
This framework allows end-users to enjoy the features they enjoy, such
as accelerated 2D graphics, encryption, and audio playing and
recording, all while working in a virtualized environment" ...

///// ///// ///// ///// /////
The other big news is Spice, the Simple Protocol for Independent
Computing Environments. Spice is part of Red Hat's Qumranet
acquisition[2], which also brought the now standard KVM virtualization
to both RHEL and Fedora.
The goal of the Spice project is to improve remote access to QEMU
virtual machines. For those running Windows clients in a virtual
machine Spice includes a few Windows helpers right out of the box
including a video driver, an agent for performing operations inside
the guest system and virtio serial drivers for talking to the agent.
Although Spice has been available in the Yum repos since Fedora 12,
the new tools make getting Spice up and running much easier and should
be good news for those with multiple virtual machines to manage.
The cloud gets an update, too.
Fedora 14 will mark the first time that Fedora will concurrently
release all its usual spins and a new Amazon EC2 image. That's great
news for those using Amazon's cloud hosting to run Fedora machines."
↑ http://lists.fedoraproject.org/pipermail/marketing/2010-September/013438.htmlhttp://www.redhat.com/about/news/prarchive/2009/spice-os.htmlhttp://www.channelregister.co.uk/2010/09/29/fedora_14_beta_review/
///// ///// ///// ///// /////

-- Niels

PS:  Potentially answering some of my previous questions:
app-emulation/qemu-kvm-spice:esd ... (which are not in F12... yet
another reason to upgrade to F14 around the end of November...).

More information about the Linux-audio-dev mailing list