qemu-kvm changes coming...

[Bryce Harrington]

On Mon, Aug 24, 2009 at 06:12:16PM +0200, Stefan Potyra wrote:
> Hi,
> 
> Am Monday 24 August 2009 18:03:49 schrieb Dustin Kirkland:
> > On Fri, Aug 21, 2009 at 5:33 PM, Stefan
> >
> > Potyra<stefan.potyra at informatik.uni-erlangen.de> wrote:
> > > That's great news! Awesome!
> > >
> > > Side note: Will we still need to carry Xorg hacks? (if so, how does qemu
> > > vs. kvm accelerated qemu make use of these... iirc these were based on
> > > cpuid of the VM which used to be different between qemu and kvm. Or is
> > > this no longer true?)
> >
> > What Xorg hacks are you talking about?  These are qemu-hacks-in-Xorg,
> > or Xorg-hacks-in-qemu?
> 
> The dexconf specific hacks to detect a running kvm instance and create a 
> different xorg.conf if found, referenced in bug 237164 [1].
> 
> The logic used to be to base the check on a cpuid pattern [2], which differed 
> between qemu and kvm.

I would like to drop all of this dexconf logic at this point.

Today I have added code to the xserver which should automatically detect
and select the correct driver for qemu and vbox cases.  I've also added a
patch to the cirrus driver which should configure 1024x768 on the kvm
case.

Thus, I believe all cases currently covered by dexconf hacks now should
be automatically handled when no xorg.conf is present.

Next step, I would like it if people could please confirm that kvm
(cirrus), qemu (non-cirrus), and vbox all work equally well with no
xorg.conf as when the dexconf-produced xorg.conf is present.  If this is
the case, then I can proceed with dumping the dexconf hacks.

Bryce