1. 22 10月, 2012 2 次提交
    • L
      virtio_console: FIX loopback test result when background thread fails · ebb2e47c
      Lukáš Doktor 提交于
      Make the loopback test fail when the background loopback thread
      fails.
      Signed-off-by: NLukáš Doktor <ldoktor@redhat.com>
      ebb2e47c
    • L
      virtio_console: Modify virtio_console to suit Windows testing · 5a059ebc
      Lukáš Doktor 提交于
      This patch changes the GuestWorker to run on windows and adjusts
      virtio_console test also to support windows testing.
      
      Currently supported tests are:
      * open
      * multiopen
      * close
      * max_serials_and_conosles (windows won't initialize consoles. I need
                 to check it with the developer if this is a bug or feature)
      * rw_host_offline (fails, need to check with developer the expected
                         results)
      * basic_loopback (fails, data are corrupted)
      * loopback (fails, data are corrupted)
      * migrate (fails, data are corrupted)
      * hotplug (fails, windows won't initialize consoles properly)
      * shutdown
      
      Beware on my laptop in 50% the ports were not initialized properly,
      VM reboot usually helped (not always). You might use "Winobj" program
      to list \\Device\vport* ports or \\.\$port_name devices/symlinks.
      
      I checked the data corruption and it happends (winXP->Fedora18)
      pretty regularly even with Amit's C++ testing script.
      Signed-off-by: NLukáš Doktor <ldoktor@redhat.com>
      5a059ebc
  2. 19 9月, 2012 1 次提交
  3. 07 9月, 2012 2 次提交