Planning/0.14/Testing: Difference between revisions

From QEMU
Line 9: Line 9:
* http://wiki.qemu.org/Manual
* http://wiki.qemu.org/Manual
* qemu --help
* qemu --help
* qemu -cpu ?, cpu -M ? ...
* qemu -cpu ?, qemu -M ?, qemu-system-x86_64 -M ?, ...
* man qemu
* man qemu
* qemu -monitor stdio ... (qemu) help
* qemu -monitor stdio ... (qemu) help
Line 16: Line 16:
* qemu-nbd --help
* qemu-nbd --help
* qemu-doc.html
* qemu-doc.html
* Please see https://bugs.launchpad.net/qemu/+bug/498107


==Hosts==
==Hosts==

Revision as of 06:18, 3 February 2011

QEMU 0.14 Release Testing

Add yourself to volunteer for QEMU 0.14 release testing.

Choose areas that you care about and are willing to test release candidates against. Please try to test each release candidate and raise any regressions on the mailing list.

Documentation

Compare all of these

Hosts

  • Linux x86 (32 bit)
  • Linux x86 (64 bit)
    • Linux x86 on AMD-CPUs (QEMU 0.13. has a lot of bugs here)
  • Win32
  • BSD, MacOS, SunOS, others

Targets

ARM, x86, s390, etc go here.

mips, mipsel

  • Debian guest on emulated MIPS Malta (little/big endian, 32/64 bit) (sweil)

x86 KVM

  • kvm-autotest run (aliguori?):
    • install Fedora guest
    • install Windows

Subsystems

Feature areas go here.

Block

  • Full qemu-io test suite (kwolf)
  • blkverify install and boot of RHEL6 and Windows 2003 Server for QED and qcow2 (stefanha)
  • qemu-img create manual testing (stefanha)
    • Want to add automated tests to qemu-img in the future!
  • qemu-nbd access to a QED image (stefanha)

Tracing

  • Check cpu_in/cpu_out trace event works for simple, dtrace, and ust backends (stefanha)

Character devices

  • Test unix/tcp socket chardev with isa/virtio serial backends (mdroth)

Networking

Monitor (HMP/QMP)

  • QMP: quit, change, block_passwd, query-version, screendump, stop, cont, system_reset, system_powerdown (anthony)

USB

Audio

Graphics

Migration

- live migration, block live migration, and hopefully Kemari with some stress to cpu, memory and disk. (yoshi)