Reason is to be identical to the upstream KVM CI. Some Tempest
tests rely on vdX virtio-blk device naming. Others simply create
their own with a brand new image. Also, the scsi support on the
CirrOS image is limited, tests booting from volume fail.
Change-Id: I389147a58042aa6098a695e6dd32f3e697fbbbab
... | ... |
@@ -364,7 +364,7 @@ function upload_image { |
364 | 364 |
esac |
365 | 365 |
|
366 | 366 |
if is_arch "ppc64le" || is_arch "ppc64" || is_arch "ppc"; then |
367 |
- img_property="--property hw_disk_bus=scsi --property hw_scsi_model=virtio-scsi --property hw_cdrom_bus=scsi --property os_command_line=console=hvc0" |
|
367 |
+ img_property="--property hw_cdrom_bus=scsi --property os_command_line=console=hvc0" |
|
368 | 368 |
fi |
369 | 369 |
|
370 | 370 |
if is_arch "aarch64"; then |