Hi, On 2015-11-02 00:24, Kevin Kwan (Personal) wrote:
I actually do run into fatal errors if I run this on my Debian x64 machine, but I think it's possible issues with the S390X TCG in the older builds of QEMU - actually have both the Windows and Linux version running side-by-side- the Windows version does get me further...although I do suspect other issues down the line.
qemu master actually segfaults[1] if you try to use s390x. [2] hopefully fixes that (untested).
How did you deactivate the s390 postinst on the installer shell?
You can go back to the menu, go down and "Execute a shell". Then edit /var/lib/dpkg/info/s390-dasd.postinst with nano and add an "exit 0" after the shebang.
I did push a fix to s390-dasd[3] yesterday night. If you use the unstable udebs, you should get it. Otherwise in five days. With that it will simply exit if there's no DASD channel found on the bus. I think that we could stuff that into stable as well.
The interesting side-bit is that I tried to define the machine as avirtio-ccw machine using the following command, and then define the disk andnetworking as channel devices: qemu-system-s390x.exe -machine type=s390-ccw-virtio-2.5 -m 512 -kernel kernel.debian9 -initrd initrd.debian9 -hda linux.dsk -devicevirtio-net-ccw,netdev=net0 -netdev user,id=net0 -k en-us -redir tcp:9022::22I was able to define it, but Debian cannot initialize it on boot (virtio_ccw0.0.0000: Failed to set online: -5), so that's a bit of a dead end.
Yeah, I had the same issue back in August. With current qemu and current kernel (4.1 worked, but also 4.2) it worked for me.
Kind regards Philipp Kern[1] http://lists.nongnu.org/archive/html/qemu-devel/2015-11/msg00007.html [2] http://lists.nongnu.org/archive/html/qemu-devel/2015-11/msg00025.html [3] https://packages.qa.debian.org/s/s390-dasd/news/20151101T222109Z.html