Search results

* Fixed block load instructions regression happened in 1.0 release. * Fixed BCD mask in m48t59 emulation, so that Solaris 2.5.1 doesn't hang on sun4m emulation when day of month >21.

* Support for more than 1 TiB of guest memory.

* The 'mem' parameter of the '-numa' option is not supported for 5.1 and newer machine types, use the 'memdev' parameter instead. Though for com * The ''spike_v1.9.1'' and ''spike_v1.10'' machines have been removed

* Fix for booting sun4m machines with more than 1 CPU ...l crash when handling 'Twalk'] requests; thus bug was introduced in QEMU 6.1.0.

...n do this with the "hubport" backend, e.g. by using <tt>-nic hubport,hubid=1</tt>.

...ICv3 now correctly reports GICD_TYPER.SecurityExtn as 0 if GICD_CTLR.DS is 1. * pseries now defaults to XIVE interrupt controller if using pseries-4.1 machine version, POWER9 cpu and a guest OS which supports it

* Support for ARMv8.1 LSE atomics EXECUTABLE=./aarch64-linux-user/qemu-aarch64 V=1

...a way to send BIOS output to the serial console, has been removed; SeaBIOS 1.11.0 and newer supports this feature natively when QEMU is started with the * OpenSBI has been updated to version 1.2, see [https://github.com/riscv-software-src/opensbi/releases/tag/v1.2 rel

...on windows hosts), evaluate options and implement it. Possible options: (1) create small posix/win32 abstraction layer for file+directory access, or (

Starting in the 1.0 release, we freed up the ''qemu'' executable name in order to allow a scr * [http://www.linux-kvm.org/wiki/images/1/12/KvmForum2007$KVM-IA64_forum_083107.pdf Talk on IA64 KVM]

** ARMv8.1-VHE ** ARMv8.1-VMID16

* The actual bitmap (1 TB disk @ 64 KB granularity = 2 MB bitmap)

* The old machine types pc-i440fx-1.4 to pc-i440fx-1.7 have been removed; use a newer machine type instead ** MacOS 7.1 - 8.1, with or without virtual memory enabled

- Fix SIGFPE for vnc display of width/height = 1 (Chris Webb) === Version 0.12.1 ===

...has been removed. It was only a "dummy" option without meaning since QEMU 1.7, so there is no replacement. ...e range of "reboot-timeout" parameter has been adjusted from 0 to 0xffff. -1 will not valid for it.