As soon as virtio-pci.c gets compiled and used on S390 the internal qdev magic
gets confused and tries to give us PCI devices instead of S390 virtio devices.
Since we don't have PCI on S390, we can safely not compile virtio-pci at all.
In order to do this I added a new config option "CONFIG_VIRTI
On 3/24/10, Alexander Graf wrote:
> Blue Swirl wrote:
> > On 3/24/10, Alexander Graf wrote:
> >
> >> As soon as virtio-pci.c gets compiled and used on S390 the internal qdev
> magic
> >> gets confused and tries to give us PCI devices instead of S390 virtio
> devices.
> >>
> >> Since we
Blue Swirl wrote:
> On 3/24/10, Alexander Graf wrote:
>
>> As soon as virtio-pci.c gets compiled and used on S390 the internal qdev
>> magic
>> gets confused and tries to give us PCI devices instead of S390 virtio
>> devices.
>>
>> Since we don't have PCI on S390, we can safely not compile
On 3/24/10, Alexander Graf wrote:
> As soon as virtio-pci.c gets compiled and used on S390 the internal qdev magic
> gets confused and tries to give us PCI devices instead of S390 virtio
> devices.
>
> Since we don't have PCI on S390, we can safely not compile virtio-pci at all.
>
> In order t
As soon as virtio-pci.c gets compiled and used on S390 the internal qdev magic
gets confused and tries to give us PCI devices instead of S390 virtio devices.
Since we don't have PCI on S390, we can safely not compile virtio-pci at all.
In order to do this I added a new config option "CONFIG_PCI"
