Hi Alon! On Sun, Jun 26, 2011 at 4:55 PM, Alon Levy <alevy@xxxxxxxxxx> wrote: > Hi, > > These patches refactor the kvm_installer and add two repositories, spice-protocol > and spice. > > I'm not sure what the best way is to achieve the next points I need to do: > > 1. Installing pre built qxl drivers into images. I'd assume there is already support for > installing virtio? is the unattended install for windows used for that? Yes, there is. I need to do some documentation on how to enable the virtio drivers install. I haven't so far because it involves some setup that we can't easily automate. Will fix this. For more details, we work from the assumption there is a virtio drivers cd with the virtio drivers, then: 1) For Win XP, 2003: We put viostor and netKVM drivers on the unattended floppy and inform on the unattended install file where to find those drivers. 2) For Win 2008 and later: We just point on the unattended install file the paths on the virtio cd where the drivers are. In both cases, we do it in a way that the windows installer knows where to find and install the drivers. > 2. Running a spice client. Is there already support for running some long lived > process while a vm is running, and controlling it? Yes, aexpect is precisely this mechanism. The qemu instances are run on an aexpect subprocess, that outlives tests and can be controlled and checked for output. We also use this for controlling tcpdump instances and other userspace programs. > > I would possibly like to also build qxl drivers - it is doable from linux using > wine and ddk, and possibly with mingw (the former I already use). Is something > similar being done for virtio drivers? Well, no, but I'll be happy to help adding this support. rss.exe and finish.exe are already generated using mingw, however, we ship binary versions of it on the autotest tree because they are small and save yet-another-complicated-setup for users. -- Lucas -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
