Re: how do the iotests pick a machine model to run on ?

2024-03-25 Thread Thomas Huth
On 19/01/2024 17.18, Peter Maydell wrote: On Fri, 19 Jan 2024 at 15:26, Peter Maydell wrote: (Also, we should probably put an entry for sh4 in machine_map, because the default board type (shix) is about to be deprecated, and the r2d board type is thus a better choice.) The good news is if we

Re: how do the iotests pick a machine model to run on ?

2024-01-19 Thread Peter Maydell
On Fri, 19 Jan 2024 at 15:26, Peter Maydell wrote: > (Also, we should probably put an entry for sh4 in machine_map, > because the default board type (shix) is about to be deprecated, > and the r2d board type is thus a better choice.) The good news is if we add r2d to the machine_map, then only 3

Re: how do the iotests pick a machine model to run on ?

2024-01-19 Thread Peter Maydell
On Fri, 19 Jan 2024 at 14:07, Kevin Wolf wrote: > > Am 19.01.2024 um 13:55 hat Peter Maydell geschrieben: > > How are the iotests supposed to select a machine model to run > > on, and how are they intended to mark themselves as requiring > > particular facilities, like PCI? Presumably some of the

Re: how do the iotests pick a machine model to run on ?

2024-01-19 Thread Kevin Wolf
Am 19.01.2024 um 13:55 hat Peter Maydell geschrieben: > If you build QEMU with support for the sh4 target only > (configure --target-list=sh4-softmmu) then 'make check' fails > in the iotests, because some iotests, including for instance 040, > try to create a machine with a virtio-scsi device, but

how do the iotests pick a machine model to run on ?

2024-01-19 Thread Peter Maydell
If you build QEMU with support for the sh4 target only (configure --target-list=sh4-softmmu) then 'make check' fails in the iotests, because some iotests, including for instance 040, try to create a machine with a virtio-scsi device, but they don't do anything to ensure that the machine they create