Unrelated issue with ltsp-vmclient - breaks kvm windows machines

Dan Young dyoung at mesd.k12.or.us
Wed Mar 26 14:14:26 UTC 2008


On Tue, Mar 25, 2008 at 5:46 PM, Warren Togami <wtogami at redhat.com> wrote:
> Dan Young wrote:
>  > I saw this on moving to rawhide. The NIC (as e1000) works fine for me
>  > in Windows when I install this Intel driver:
>  > http://tinyurl.com/336qts
>  >
>  > Video is still borked, however. The PCI ID in Windows indicates it's a
>  > VMWare SVGA II, but a driver scraped out of the VMWare Tools package
>  > did not work.
>  >
>  > $ rpm -q --changelog kvm | grep 'Mon Mar 03 2008' -A1
>  > * Mon Mar 03 2008 Jeremy Katz <katzj at redhat.com> - 62-3
>  > - Default to vmwaresvga now that it's been fixed to work
>  >
>
>  I am sorry the newer kvm causes these difficulties, but that is the cost
>  of progress.  We need fixes in libvirt and kvm for these issues because
>  rawhide isn't going back.

Understood. No apologies necessary.

>  I highly recommend filing a bug against libvirt because it really should
>  allow choosing the different network interface and video devices.
>  As far as the Windows VMWare driver not working, this is unfortunate
>  because we have no control over that driver.  Also VMWare is not likely
>  to help kvm because kvm is a threat to VMWare's future business.  I
>  might file a bug against kvm, maybe there is something they can do to
>  make their emulated video work with the VMWare Windows driver.

I understand that making free software work well there is the
project's priority. Yeah, were mostly included as Google fodder,
should anyone else attempt to be "clever".

-- 
Dan Young <dyoung at mesd.k12.or.us>
Multnomah ESD - Technology Services
503-257-1562




More information about the K12Linux-devel-list mailing list