Feature #10680
closed
qemu task relies on virtio-9p, which is not available in centos/rhel
Added by Josh Durgin over 9 years ago.
Updated about 9 years ago.
Description
From the teuthology log:
2015-01-27T18:50:16.413 INFO:tasks.qemu.client.0.magna091.stderr:qemu-kvm: -device virtio-9p-pci,fsdev=log,mount_tag=test_log: 'virtio-9p-pci' is not a valid device model name
2015-01-27T18:50:16.686 INFO:tasks.qemu.client.0.magna091.stderr:daemon-helper: command failed with exit status 1
We'll need to use another mechanism (at least on centos/rhel) to let the guest report success/failure of a test running inside of it. If we used nfs it would be able to continue outputing the test results on the fly as well, so hangs and progress could be checked more easily. Other mechanisms might be simpler to set up though.
- Tracker changed from Bug to Feature
- Status changed from New to Need More Info
- Assignee set to Josh Durgin
Changing to a feature so we can plan for it as such.
We'll also want some more specific requirements. Is NFS definitely what we should use? If not, what else should we look at? Do we need to support both?
- Status changed from Need More Info to New
- Assignee deleted (
Josh Durgin)
The main other option would be samba. Whichever is easier to configure in the host and via cloudinit (where the tests run) in the guest is fine. The two things I'm interested in are:
1) ability to access the test log on the host, as it's being written by the guest (so if the guest hangs or crashes we have some clue as to what happened, and can see progress in general)
2) a way for the guest to report test success/failure to teuthology - this is currently done by touching a 'success' file on the shared fs at the end of the test, which the qemu task checks for
There's no need to keep virtio-9p around. Using the same mechanism on each platform would simplify things a bit.
- Target version set to sprint24
- Assignee set to Andrew Schoen
- Status changed from New to Resolved
Also available in: Atom
PDF