virtualization script sends wrong parameters to qemu-system-x86_64 (space before hostfwd)
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Checkbox |
Fix Released
|
Critical
|
Daniel Manrique |
Bug Description
Narinder was testing a server at HP and the KVM test is failing with a strange ioctl message in the results:
Here is the log:
Executing KVM Test
DEBUG:root:Starting KVM Test
DEBUG:root:Creating cloud user-data
DEBUG:root:Creating cloud meta-data
I: -input-charset not specified, using utf-8 (detected in locale settings)
Total translation table size: 0
Total rockridge attributes bytes: 331
Total directory bytes: 0
Path table size(bytes): 10
Max brk space used 0
183 extents written (0 MB)
DEBUG:root:
DEBUG:root:
DEBUG:root:Using params:
reset: standard error: Inappropriate ioctl for device
KVM instance failed to boot
Related branches
- Daniel Manrique (community): Approve
- Jeff Lane : Approve
-
Diff: 25 lines (+3/-1)2 files modifiedcheckbox-old/debian/changelog (+2/-0)
checkbox-old/scripts/virtualization (+1/-1)
Changed in checkbox: | |
milestone: | none → 2013-nov-22 |
Changed in checkbox: | |
status: | In Progress → Fix Committed |
Changed in checkbox: | |
status: | Fix Committed → Fix Released |
Hey, the ioctl message can be safely ignored. It's just qemu-system-x86_64 trying to send a reset/clear ioctl to the terminal, without realizing there's no terminal (we're piping stdout to a file to get the log). It's not the cause for the failure.
Actually, look at the command:
DEBUG:root:Using params: qemu-system- x86_64 -machine accel=kvm:tcg -m 256 -net nic -net user,net= 10.0.0. 0/8,host= 10.0.0. 1, hostfwd= tcp::2222- :22-drive file=/home/ ubuntu/ precise- server- cloudimg- i386-disk1. img,if= virtio -drive file=seed. iso,if= virtio -display none -nographic
See the space right before "hostfwd", that's what's causing the failure. This bug was introduced in checkbox rev 2402 but fixed in rev 2413 about 6 weeks ago.
How is Narinder installing checkbox? could we ask him to update to a newer version and try again?
I'd say this bug is Fix Released but let's wait until we know more from Narinder, setting to Incomplete in the meanwhile.