since there are a lot of people that is using QEMU. Can anyone has tried version 8.1 with e500v2 and PPC Linux? Is there a way to use ide bus? Because it seems it doesn't have any ide or scsi bus available. Any hint?
You can add a device to do this, and you can get the full list of valid devices using the following line.
./qemu-system-ppc -device help
Here is the list of valid storage devices
Storage devices:
name "am53c974", bus PCI, desc "AMD Am53c974 PCscsi-PCI SCSI adapter"
name "dc390", bus PCI, desc "Tekram DC-390 SCSI adapter"
name "floppy", bus floppy-bus, desc "virtual floppy drive"
name "ich9-ahci", bus PCI, alias "ahci"
name "ide-cd", bus IDE, desc "virtual IDE CD-ROM"
name "ide-cf", bus IDE, desc "virtual CompactFlash card"
name "ide-hd", bus IDE, desc "virtual IDE disk"
name "isa-fdc", bus ISA, desc "virtual floppy controller"
name "isa-ide", bus ISA
name "lsi53c810", bus PCI
name "lsi53c895a", bus PCI, alias "lsi"
name "megasas", bus PCI, desc "LSI MegaRAID SAS 1078"
name "megasas-gen2", bus PCI, desc "LSI MegaRAID SAS 2108"
name "mptsas1068", bus PCI, desc "LSI SAS 1068"
name "nvme", bus PCI, desc "Non-Volatile Memory Express"
name "nvme-ns", bus nvme-bus, desc "Virtual NVMe namespace"
name "nvme-subsys", desc "Virtual NVMe subsystem"
name "pvscsi", bus PCI
name "scsi-cd", bus SCSI, desc "virtual SCSI CD-ROM"
name "scsi-hd", bus SCSI, desc "virtual SCSI disk"
name "sd-card", bus sd-bus
name "sdhci-pci", bus PCI
name "sii3112", bus PCI, desc "SiI3112A SATA controller"
name "usb-bot", bus usb-bus
name "usb-storage", bus usb-bus
name "usb-uas", bus usb-bus
name "virtio-blk-device", bus virtio-bus
name "virtio-blk-pci", bus PCI, alias "virtio-blk"
name "virtio-blk-pci-non-transitional", bus PCI
name "virtio-blk-pci-transitional", bus PCI
name "virtio-scsi-device", bus virtio-bus
name "virtio-scsi-pci", bus PCI, alias "virtio-scsi"
name "virtio-scsi-pci-non-transitional", bus PCI
name "virtio-scsi-pci-transitional", bus PCI
For scsi you could add a new device of 'virtio-scsi-pci', and then add a scsi-hd image and attach it to scsi.0
Our X5000 Linux kernels work in virtual e5500 QEMU machines and we have successfully tested NVMe, SCSI, VirtIO and IDE drives. Maybe you can find some information in the following thread:
It seems you are running it on Linux (PPC) and not on Windows (or lunux x86) for example. However where I can find all I need? I mean uboot and the kernel? Thank you
But it doesn't work. U-boot starts but no ide/scsi devices are found and so the autoboot fail
It has nothing to do with Linux PPC, but exactly the same thing happens when I try to use SCSI devices under Pegasos 2 emulation. AmigaOs4.1 shows me the boot logo, but does not boot.
Also under AmigaOs4.1 no SCSI devices are shown that I have mounted. I'm not sure, but maybe the Qemu line still needs to be assigned a suitable SCSI driver supported by AmigaOs4.1 or in your case Linux PPC.
I think it was already mentioned that AmigaOs4.1 is not able to boot from SCSI disks, but at least with AmigaOs4.1 I should have access to SCSI devices then, right?
@Maijestro If AmigaOS does not have a driver for virtio-scsi then how could it see disks attached to that? The AmigaOne firmware printed scsi not found with a vendor/device id of an LSI scsi contoller but QEMU emulates a somewhat newer version of that so probably it won't work unless one of the emulated scsi controllers in QEMU matches a driver in AmigaOS.
For guests that have virtio drivers maybe using virtio-blk is better as it has less legacy stuff, only pure virtio which should be the fastest and simplest. For AmigaOS that's the same as for virtio-gpu and virtio-net: drivers need to be written.
@balaton AmigaOS 4.x only has a driver for lsi53c8xx SCSI. (There are more SCSI drivers, for example for the onboard A4000T, CyberStormPPC, etc. SCSI controllers, but lsi53c8xx is the only PCI one.)
Storage devices: name "am53c974", bus PCI, desc "AMD Am53c974 PCscsi-PCI SCSI adapter" name "dc390", bus PCI, desc "Tekram DC-390 SCSI adapter" name "lsi53c810", bus PCI name "lsi53c895a", bus PCI, alias "lsi"
I think the AmigaOne ROM listed 1000:000f PCI ID but I did not find that in QEMU, it has
@balaton From the documentation of the AmigaOS 4.x driver: Quote:
- To use the driver, just drop an LSI/NCR/SYM53Cxxx SCSI board into any PCI slot, connect it to SCSI drives, make sure the termination chain is set properly, and add the driver to your kicklayout.
Quote:
I - Configuring lsi53c8xx through UBOOT envvars ================================================
Currently lsi53c8xx is configurable through the following UBOOT envvars :
- scsi_pci_override
Legal values are : set to the PCI product ID if your board does not show a product id of 000F. For example, my LSI53C895 board has a product id of 000C thus I used that feature.
Note : Uboot's internal SCSI code uses the same mechanism and the same envvar (this is why I chose that name : if you have properly set it for UBoot then it works for the OS4 driver).
Default if unset : 000F.
SAS SCSI hardware is not supported by the driver, but PCI_DEVICE_ID_LSI_53C895A 0x0012, and maybe even PCI_DEVICE_ID_LSI_53C810 0x0001, should work.
u-boot is supplied with qemu. QEMU_PREFIX:shared/qemu/u-boot.e500
What distribution and I understand you want to run ppc with Windows x86, yes?
I just checked what @xeno74 wrote on the console. as far as I can see he is running ppc on ppc -- qemu-system-ppc -nographic -machine ppce500 -bios ../share/qemu/u-boot.e500 -cpu e500v2 -M mpc8544ds
@smarkusg You have two machine options in that command line (-M is synonym for -machine). I wonder why it did not give an error but one of those should be enough.
You have two machine options in that command line (-M is synonym for -machine). I wonder why it did not give an error but one of those should be enough.
Yes I saw this. But this isn't the problem. The problem is that with shipped uboot e500 version I can't manage to add any drive. In any way.
@afxgroup I can't help woth that but there should be examples on line on how to use the e500 machine so you should be able to search and find onw. Of course you'd need to emulate something that the guest has drivers for so it amy depend on the guest you're trying to run.
Also the sources fot the included U-boot-e500 firmware is in qemu/roms/u-boot so you may check what config it uses to find out what it shoulc support. If the dir is empty look at git submodule and to build it see qemu/roms/Makefile:
The only devices that seems usable are virtio-blk. And reading the second link you gave me there is also an example. But there is no way to make it work..
To the topic ubuntu-14.04.5-server-powerpc.iso There is supposedly a kernel under the e500 ..probably "e500mc" I got as far as it will help you. I have no idea if the kernel is the right one or if something should show up ..but it tries to boot up
Ok. That's fine. But except for the Linux iso. I don't have the kernel, initrd and so on. Do I have to compile it? Or it is possible to download them somewhere?