[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Qemu-devel] [Bug 1671173] [NEW] OS started to crash with a message: "Tr
From: |
Konstantin Tcholokachvili |
Subject: |
[Qemu-devel] [Bug 1671173] [NEW] OS started to crash with a message: "Trying to execute code outside RAM or ROM" |
Date: |
Wed, 08 Mar 2017 17:23:25 -0000 |
Public bug reported:
There is a project (https://github.com/narke/colorForth ) wich always
worked with qemu up to version 2.5.1.1 but doesn't works from version
2.6 onwards. It continues to work with bochs.
Downlaod: git clone https://github.com/narke/colorForth.git
Build: make
Test: qemu-system-i386 -drive format=raw,file=cf2012.img,index=0,if=floppy
System information: Ubuntu LTS 16.04 x86-64
Affected qemu versions: 2.6 to present (2.8)
I got the message:
WARNING: Image format was not specified for 'cf2012.img' and probing guessed
raw.
Automatically detecting the format is dangerous for raw images, write
operations on block 0 will be restricted.
Specify the 'raw' format explicitly to remove the restrictions.
qemu-system-i386: Trying to execute code outside RAM or ROM at 0x8998c426
This usually means one of the following happened:
(1) You told QEMU to execute a kernel for the wrong machine type, and it
crashed on startup (eg trying to run a raspberry pi kernel on a versatilepb
QEMU machine)
(2) You didn't give QEMU a kernel or BIOS filename at all, and QEMU executed a
ROM full of no-op instructions until it fell off the end
(3) Your guest kernel has a bug and crashed by jumping off into nowhere
This is almost always one of the first two, so check your command line and that
you are using the right type of kernel for this machine.
If you think option (3) is likely then you can try debugging your guest with
the -d debug options; in particular -d guest_errors will cause the log to
include a dump of the guest register state at this point.
Execution cannot continue; stopping here.
Thank you in advance.
** Affects: qemu
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1671173
Title:
OS started to crash with a message: "Trying to execute code outside
RAM or ROM"
Status in QEMU:
New
Bug description:
There is a project (https://github.com/narke/colorForth ) wich always
worked with qemu up to version 2.5.1.1 but doesn't works from version
2.6 onwards. It continues to work with bochs.
Downlaod: git clone https://github.com/narke/colorForth.git
Build: make
Test: qemu-system-i386 -drive format=raw,file=cf2012.img,index=0,if=floppy
System information: Ubuntu LTS 16.04 x86-64
Affected qemu versions: 2.6 to present (2.8)
I got the message:
WARNING: Image format was not specified for 'cf2012.img' and probing guessed
raw.
Automatically detecting the format is dangerous for raw images,
write operations on block 0 will be restricted.
Specify the 'raw' format explicitly to remove the restrictions.
qemu-system-i386: Trying to execute code outside RAM or ROM at 0x8998c426
This usually means one of the following happened:
(1) You told QEMU to execute a kernel for the wrong machine type, and it
crashed on startup (eg trying to run a raspberry pi kernel on a versatilepb
QEMU machine)
(2) You didn't give QEMU a kernel or BIOS filename at all, and QEMU executed
a ROM full of no-op instructions until it fell off the end
(3) Your guest kernel has a bug and crashed by jumping off into nowhere
This is almost always one of the first two, so check your command line and
that you are using the right type of kernel for this machine.
If you think option (3) is likely then you can try debugging your guest with
the -d debug options; in particular -d guest_errors will cause the log to
include a dump of the guest register state at this point.
Execution cannot continue; stopping here.
Thank you in advance.
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1671173/+subscriptions
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- [Qemu-devel] [Bug 1671173] [NEW] OS started to crash with a message: "Trying to execute code outside RAM or ROM",
Konstantin Tcholokachvili <=