Re: [Qemu-devel] RFH: difference in read-only mapped bios.bin - memory corruption?

* Philipp Hahn (h...@univention.de) wrote: > Hello, > > Am 15.08.2017 um 13:25 schrieb Laszlo Ersek: > > On 08/14/17 20:39, Dr. David Alan Gilbert wrote: > >> * Philipp Hahn (h...@univention.de) wrote: > >>> I'm currently investigating a problem, were a Linux VM does not reboot > >>> and gets stuc

Re: [Qemu-devel] RFH: difference in read-only mapped bios.bin - memory corruption?

Hello, Am 15.08.2017 um 13:25 schrieb Laszlo Ersek: > On 08/14/17 20:39, Dr. David Alan Gilbert wrote: >> * Philipp Hahn (h...@univention.de) wrote: >>> I'm currently investigating a problem, were a Linux VM does not reboot >>> and gets stuck in the SeaBIOS reboot code: >>> >>> I'm using SeaBIOS-1

Re: [Qemu-devel] RFH: difference in read-only mapped bios.bin - memory corruption?

On 08/14/17 20:39, Dr. David Alan Gilbert wrote: > * Philipp Hahn (h...@univention.de) wrote: >> Hello, >> >> I'm currently investigating a problem, were a Linux VM does not reboot >> and gets stuck in the SeaBIOS reboot code: >> >> I'm using SeaBIOS-1.7 from Debian with a more modern qemu-2.8 >> >

Re: [Qemu-devel] RFH: difference in read-only mapped bios.bin - memory corruption?

* Philipp Hahn (h...@univention.de) wrote: > Hello, > > I'm currently investigating a problem, were a Linux VM does not reboot > and gets stuck in the SeaBIOS reboot code: > > I'm using SeaBIOS-1.7 from Debian with a more modern qemu-2.8 > > > virsh # qemu-monitor-command --hmp ucs41-414 info ro

[Qemu-devel] RFH: difference in read-only mapped bios.bin - memory corruption?

Hello, I'm currently investigating a problem, were a Linux VM does not reboot and gets stuck in the SeaBIOS reboot code: I'm using SeaBIOS-1.7 from Debian with a more modern qemu-2.8 > virsh # qemu-monitor-command --hmp ucs41-414 info roms > fw=genroms/kvmvapic.bin size=0x002400 name="kvmvapic.b