On Thu, Jun 03, 2010 at 06:53:54AM -0400, Amos Benari wrote:
After applying the patch windows guest came up with no error in the event log.
+[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\Parport] +"Start"=dword:00000004
Disabling the parallel port? I would say this is a separate and unrelated bug in virt-v2v: either virt-v2v should enable the parallel port under KVM in the same way as it is configured in VMWare (if that's possible) or it should separately disable it. The rest of the patch looks fine, but I'm leery of including the change to the parallel port driver. If we don't disable the parport driver what are the consequences? Simply an error in a log file and an unusable parport? Or is there a more user-visible change? Rich. PS. Your mailer sets the content-type of attachments to application/octet-stream which makes it hard to reply to your patches inline. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones New in Fedora 11: Fedora Windows cross-compiler. Compile Windows programs, test, and build Windows installers. Over 70 libraries supprt'd http://fedoraproject.org/wiki/MinGW http://www.annexia.org/fedora_mingw