From: Brendan S. <Brendan@BrendanSimon.com> - 2007-04-24 00:16:50
|
Thanks for the help George. This sounds like the best solution currently available for X/VNC with laptops :) Is there a wiki/faq entry on how to setup this scenario? The virtual video device sounds very interesting and would bring coLinux up to par with K/QEMU with respect to GUI performance. I've seen a colleague use QEMU and it looked great with the X display. AFAICT, K/QEMU does not require a special kernel where as coLinux requires a special coLinux built kernel, so I presume coLinux is slightly faster than K/QEMU otherwise there would be no point, right ???? Cheers, Brendan. George P Boutwell wrote: > Brendan Simon wrote: > > There are some scenarios, such as VNC and X usage where the throughput > of SLiRP and coLinux's Networking in general just aren't up to it. This > is a known issue and believe it or not this has been improving. The > speed of coLinux networking in 0.7.1 is way, way, way better than it was > in 0.6.x > > coLinux project is attacking the network performance issue as best we > can, with the tools and resources that we have. As someone else pointed > out there have been some really good discussions in the past about > changes/tweaks, etc to default networking settings that done > carefully/correctly can drastically improve the performance (see the > archives for details) > > In addition to that we are addressing the VNC/X issue by working on an > experimental (at this time) virtual video device driver that would (in > theory) allow QEMU & VMWare like video for coLinux and which would > provide better performance than the current solutions which all involve > using the network to get video. > > Having said this, the easiest & fastest mechanism that we (several > core developers & core community members) have found to work for both > Internet & network-based X/VNC display is to use eth0=SliRP for Internet > and eth1=tap for X/VNC. That is to say that SLiRP is used to allow an > virtually 0 configuration internet connection, even when switching > interfaces, moving around as is common with laptops. While having a > static configuration with the TAP device for X/VNC. > |