Welp. Yeah now I see it, it was in the test case I linked. Thanks.
Vmware doesn't seem to need this. Seems like it assigns a WWN of
0x5000c293944837df to my disk (not in the vm config files as far as i
can see, seems to persist across reboots)
[2.305111] ioc0: LSISAS1068 B0: Capabilities={Ini
** Attachment added: "The test script from the bug description"
https://bugs.launchpad.net/qemu/+bug/1603693/+attachment/4702121/+files/test-mptsas1068.sh
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/
Public bug reported:
When using the mptsas1068 scsi controller, linux detects the controller
itself but not the drives attached to it. Freebsd works. Using a
different controller with linux works. VMware with linux works.
qemu 2.6.50 (v2.6.0-1925-g6b92bbf)
seabios rel-1.9.0-139-gae3f78f (master b
We're affected by this bug, too. Trying to find a workaround, last
friday we changed VGA model to cirrus, and the machine is working
properly without new entries in log.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.lau
