On 1/8/25 07:01, BALATON Zoltan wrote:
On Tue, 7 Jan 2025, Rob Landley wrote:
What's the alternative to -hda you suggest for that?
Can I do "./run-qemu.sh -drive file=blah.img" without the rest?
Perhaps specify all the details in the script and then optionally add
an extra
On 1/8/25 10:26, Geert Uytterhoeven wrote:
Hi Rob,
On Wed, Jan 8, 2025 at 5:23 PM Rob Landley wrote:
On 1/8/25 02:24, Geert Uytterhoeven wrote:
On Tue, Jan 7, 2025 at 11:53 PM Rob Landley wrote:
Microblaze has no /dev/?da (as in there's no device I could attach it to
even with the
On 1/8/25 08:59, Alex Bennée wrote:
Rob Landley writes:
On 1/7/25 12:05, Alex Bennée wrote:
Stafford Horne writes:
I have not used -hda before, do you have it working with other targets?
According to the qemu docs in qemu-options.hx. I see:
Use file as hard disk 0, 1, 2 or 3 image
On 1/8/25 02:24, Geert Uytterhoeven wrote:
Hi Rob,
On Tue, Jan 7, 2025 at 11:53 PM Rob Landley wrote:
Microblaze has no /dev/?da (as in there's no device I could attach it to
even with the long option, I'd have to use NBD), sh4eb has -hda is
working but it's having some endiann
On 1/7/25 12:05, Alex Bennée wrote:
Stafford Horne writes:
I have not used -hda before, do you have it working with other targets?
According to the qemu docs in qemu-options.hx. I see:
Use file as hard disk 0, 1, 2 or 3 image on the default bus of the
emulated machine (this is for e
On 1/7/25 11:31, Stafford Horne wrote:
On Tue, Jan 07, 2025 at 05:56:52AM -0600, Rob Landley wrote:
On 12/31/24 19:19, Rob Landley wrote:
On 12/23/24 07:05, Stafford Horne wrote:
The kernel config looks like it should have virt block device
support, but
...
-device virtio-blk-device
On 12/31/24 19:19, Rob Landley wrote:
On 12/23/24 07:05, Stafford Horne wrote:
The kernel config looks like it should have virt block device
support, but
...
-device virtio-blk-device,drive=d0 -drive
file=${DISK},id=d0,if=none,format=qcow2
-drive file=file.img,format=raw,id=hd0 -device
On 12/23/24 07:05, Stafford Horne wrote:
The kernel config looks like it should have virt block device support, but
nether -hda README nor "-drive file=README,format=raw,id=hd0 -device
virtio-blk-device,drive=hd0" seem to be wiring it up in qemu where the
kernel can find it?
The default virt_de
On 11/24/24 00:50, Stafford Horne wrote:
Speaking of which, is there a way to get or1k to exit the emulator? I told
the kernel to reboot but it says "reboot failed, system halted" and hangs
instead of exiting qemu. (My testroot runs qemu under "timeout -i 10" to
kill it after 10 seconds of inacti
On 11/23/24 02:28, Stafford Horne wrote:
Just a guess, but given the alignment change, I suspect it's barfing on the
statically linked initramfs? That seems the most likely step to go off the
rails given the failing patch is a symbol alignment change in the flattened
device tree plumbing, and I t
On 11/22/24 10:35, Stafford Horne wrote:
I just regression tested linux-6.12 against qemu-9.2.0-rc1 and I'm still
getting no output from or1k, with the current image or the old or1k release
image that worked under old qemu versions.
I tried applying your serial patch to current qemu, and it made
On 9/16/24 02:21, Stafford Horne wrote:
On Wed, Sep 11, 2024 at 12:42:58AM -0500, Rob Landley wrote:
Grab this tarball, extract it, and ./run-qemu.sh. It's a simple
linux+initramfs image that boots to a shell prompt.
https://landley.net/bin/mkroot/latest/or1k.tgz
QEMU 7.0.0 ran that
On 11/14/24 17:33, Paolo Bonzini wrote:
On 11/15/24 00:10, Rob Landley wrote:
Seems a _bit_ awkward to do that (and potentially fail on a random new
dependency) just to delete it all again?
That's just how Make works.
Linux and busybox and so on use make, and I've never seen &
Apparently because:
../meson.build:1:0: ERROR: Meson version is 0.59.3 but project requires
>=1.5.0
A full log can be found at
/home/landley/qemu/qemu/build/meson-logs/meson-log.txt
/home/landley/qemu/qemu/build/pyvenv/bin/meson setup --reconfigure
/home/landley/qemu/qemu
WARNING: Regeneratin
On 10/24/24 03:27, Thomas Huth wrote:
Now that we are aware of binaries that are available for sh4eb,
we should make sure that there are no regressions with this
target and test it regularly in our CI.
Any progress on restoring this? Didn't see it in "git pull" just now...
+class R2dEBTest(Li
was wrong.
Signed-off-by: Thomas Huth
Signed-off-by: Rob Landley
Rob
On 10/24/24 00:44, Thomas Huth wrote:
On 24/10/2024 02.11, Rob Landley wrote:
I use it, and ship system images for it:
https://landley.net/bin/mkroot/latest/sh4eb.tgz
Oh, that's interesting, I've been told that the r2d machine does not
work in big endian mode:
https://lore.
On 10/23/24 19:11, Rob Landley wrote:
There was a big-endian issue breaking r2d last year, but it also broke
big endian mips and some other targets too, and it got fixed. The binary
I built a few months ago was working fine for me with vanilla qemu git
source? (I don't _think_ I had
I use it, and ship system images for it:
https://landley.net/bin/mkroot/latest/sh4eb.tgz
And here's me recentish-ly debugging an issue via it:
https://landley.net/notes-2024.html#24-05-2024
(Compile/test cycles are WAY easier there than copying files onto an sd
card to test on actual hardw
Grab this tarball, extract it, and ./run-qemu.sh. It's a simple
linux+initramfs image that boots to a shell prompt.
https://landley.net/bin/mkroot/latest/or1k.tgz
QEMU 7.0.0 ran that linux-or1k image, but newer qemu does not. I besected the
issue to qemu commit 0a923be2f642, and it's still brok
On 3/29/23 12:23, Philippe Mathieu-Daudé wrote:
> On 29/3/23 18:48, Rob Landley wrote:
>>>> Works fine for me. Somebody said it was the wrong fix but I don't remember
>>>> why...
>>>
>>> This is a correct /partial/ fix. With this patch, Malta
On 3/29/23 11:07, Philippe Mathieu-Daudé wrote:
> On 29/3/23 18:09, Rob Landley wrote:
>> On 3/28/23 12:02, Philippe Mathieu-Daudé wrote:
>>> On 20/3/23 17:58, Nathan Chancellor wrote:
>>>> On Wed, Mar 08, 2023 at 12:33:38AM +0100, Philippe Mathieu-Daudé wrote:
On 3/29/23 03:55, Thomas Huth wrote:
> On 28/03/2023 19.02, Philippe Mathieu-Daudé wrote:
>> On 20/3/23 17:58, Nathan Chancellor wrote:
>>> On Wed, Mar 08, 2023 at 12:33:38AM +0100, Philippe Mathieu-Daudé wrote:
On 23/2/23 17:19, Jiaxun Yang wrote:
> 145e2198d749 ("hw/mips/gt64xxx_pci:
On 3/28/23 12:02, Philippe Mathieu-Daudé wrote:
> On 20/3/23 17:58, Nathan Chancellor wrote:
>> On Wed, Mar 08, 2023 at 12:33:38AM +0100, Philippe Mathieu-Daudé wrote:
>>> On 23/2/23 17:19, Jiaxun Yang wrote:
145e2198d749 ("hw/mips/gt64xxx_pci: Endian-swap using PCI_HOST_BRIDGE
MemoryRegi
On 1/21/23 07:14, Peter Maydell wrote:
> On Sat, 21 Jan 2023 at 10:45, Rob Landley wrote:
>>
>> wget https://landley.net/toybox/downloads/binaries/mkroot/0.8.9/mips.tgz
>> extract
>> and ./run-qemu.sh in there. Before this commit it goes:
>
> Hi; does this pa
wget https://landley.net/toybox/downloads/binaries/mkroot/0.8.9/mips.tgz extract
and ./run-qemu.sh in there. Before this commit it goes:
loop: module loaded
ata_piix :00:0a.1: enabling device ( -> 0001)
scsi host0: ata_piix
scsi host1: ata_piix
ata1: PATA max UDMA/33 cmd 0x1f0 ctl 0x3f6 bm
On 4/29/22 16:43, Fabiano Rosas wrote:
> Rob Landley writes:
>> Then paste something longer than 16 characters at the eventual command prompt
>> once the kernel finishes booting.
>
> I suspect this is due to how the tty driver (n_tty.c) interacts with
> the console
On 4/28/22 00:41, Rob Landley wrote:
> On 4/27/22 10:27, Thomas Huth wrote:
>> On 26/04/2022 12.26, Rob Landley wrote:
>>> When I cut and paste 80-ish characters of text into the Linux serial
>>> console, it
>>> reads 16 characters and stops. W
On 4/27/22 10:27, Thomas Huth wrote:
> On 26/04/2022 12.26, Rob Landley wrote:
>> When I cut and paste 80-ish characters of text into the Linux serial
>> console, it
>> reads 16 characters and stops. When I hit space, it reads another 16
>> characters,
>> an
When I cut and paste 80-ish characters of text into the Linux serial console, it
reads 16 characters and stops. When I hit space, it reads another 16 characters,
and if I keep at it will eventually catch up without losing data. If I type,
every character shows up immediately.
(On other qemu target
On 7/26/21 8:59 AM, Taylor Simpson wrote:
> We're working on system mode support for Hexagon, and we plan to upstream it
> when it is ready.
>
> Thanks,
> Taylor
Any progress on this? (Is there a way for outsiders to track the status?)
Thanks,
Rob
On 7/29/21 8:52 AM, Peter Maydell wrote:
> On Thu, 29 Jul 2021 at 02:01, Richard Henderson
> wrote:
>>
>> Cc: Yoshinori Sato
>> Signed-off-by: Richard Henderson
>> ---
>> linux-user/sh4/cpu_loop.c | 8
>> target/sh4/cpu.c | 2 +-
>> target/sh4/op_helper.c| 3 ---
>> 3 f
On 7/26/21 8:59 AM, Taylor Simpson wrote:
>> Anyway, I still hope somebody else has already done most of this in a git
>> tree somewhere. :)
>
> We're working on system mode support for Hexagon, and we plan to upstream it
> when it is ready.
Yay! Thanks.
While you're at it, why is llvm's cmake c
On 7/26/21 2:57 AM, Rob Landley wrote:
> Anyway... it doesn't look like qemu-system-hexagon (softmmu) its currently in
> vanilla qemu? Is there a public fork that has this somewhere?
I did a little wild flailing to get ./configure to give me a qemu-system-hexagon
option (patch att
On 7/19/21 11:19 AM, Sid Manning wrote:>> -Original Message-
>> From: Brian Cain
>> Sent: Monday, July 19, 2021 8:40 AM
>> To: Rob Landley ; Taylor Simpson
>> ; qemu-devel@nongnu.org; Sid Manning
>>
>> Cc: a...@rev.ng; peter.mayd...@linaro
On 7/12/21 8:42 AM, Brian Cain wrote:
> If you don't mind binaries, there are x86_64 linux binary toolchains with lld
> on releases.llvm.org
I've never managed to run those binaries, because they're dynamically linked
against some specific distro I'm not using:
$ bin/clang --help
/lib/ld-linu
On 7/5/21 6:34 PM, Taylor Simpson wrote:
> Signed-off-by: Taylor Simpson
> ---
> target/hexagon/README | 83
> ++-
> 1 file changed, 82 insertions(+), 1 deletion(-)
I'm poking at the hexagon toolchain build script you checked into the test
directo
On 8/30/20 3:47 PM, Taylor Simpson wrote:
> Richard,
>
> Thank you so much for the feedback. I really appreciate it.
>
> I'll get to work addressing the issues. Since some of the items will take
> longer than others, please advise whether it's preferred to send intermediate
> updates or wait
On 11/2/18 6:25 AM, Laurent Vivier wrote:
>> If that does not work, I'm also fine if we simply deprecate the simcalls
>> (if possible).
>
> I have a patch to deprecate the interface. I will send it once the
> release will be done.
Did I ever point out that I got m68k running under your q800 emula
9600 bps, which is fine for any interative console.
>>
>> Reported-by: Rob Landley
>> Signed-off-by: Geert Uytterhoeven
>
> Works for me, kernel 4.18-rc7 for rts7751r2dplus.
Works for me too.
Tested-by: Rob Landley
Rob
On 04/02/2018 02:05 PM, Laurent Vivier wrote:
> Le 02/04/2018 à 20:13, Rob Landley a écrit :
>>> The branch to use is q800-dev
...
>> It booted Linux to a shell prompt, I could wget a file from the internet, and
>> /home had the 2 gigabyte ext3 mount from the virtual blo
On 03/30/2018 12:00 PM, Laurent Vivier wrote:
> Le 30/03/2018 à 18:54, Rob Landley a écrit :
>> On 03/20/2018 04:08 AM, Laurent Vivier wrote:> This series of patches is
>> needed
>> to fix a problem
>>> in the m68k translator that can crash QEMU when t
On 03/20/2018 04:08 AM, Laurent Vivier wrote:> This series of patches is needed
to fix a problem
> in the m68k translator that can crash QEMU when translation
> cache has too many instructions:
>
> qemu-m68k: tcg/tcg.c:883: tcg_temp_alloc: Assertion `n < 512' failed.
> qemu: uncaught target si
On 01/18/2018 01:38 PM, Laurent Vivier wrote:
> Only add MC68040 MMU page table processing and related
> registers (Special Status Word, Translation Control Register,
> User Root Pointer and Supervisor Root Pointer).
>
> Transparent Translation Registers, DFC/SFC and pflush/ptest
> will be added l
On 05/18/2017 06:01 PM, Aurelien Jarno wrote:
> On 2017-05-18 17:37, Rob Landley wrote:
>> On 05/18/2017 02:00 PM, Aurelien Jarno wrote:
>>> On 2017-05-18 11:08, Rob Landley wrote:
>>>> Serial input hangs after the first character in the 4.11 kernel:
>>>>
On 05/30/2017 07:17 AM, Peter Maydell wrote:
> On 8 May 2017 at 06:08, Rob Landley wrote:
>> As far as I can tell "qemu-system-arm -M vexpress-a9" only implements sd
>> card, not any conventional hard drive, and it uses an sdcard block size
>> of 262144 bytes
On 05/29/2017 05:14 AM, Richard W.M. Jones wrote:
> I see in the disassembly use of cmovne (new in Pentium Pro) and
> bswap (new in 486).
> [http://cse.unl.edu/~goddard/Courses/CSCE351/IntelArchitecture/InstructionSetSummary.pdf]
>
> The cmovne instruction is generated by the compiler (GCC in my c
You can't boot a kernel under -cpu 486 since that commit (hangs
producing no output) because it added a bios image that won't run on
anything short of pentium II.
You can try the run-emulator.sh script in
http://landley.net/aboriginal/downloads/binaries/system-image-i486.tar.gz
before and after th
On 05/18/2017 06:00 PM, Aurelien Jarno wrote:
>> Exiting the linux instance says "reboot: Restarting system\nUnauthorized
>> access" and then hangs eating 100% cpu, but maybe I can fix that with
>> kernel configuration changes.
>
> I guess you mean rebooting the linux instance. This is because you
On 05/18/2017 02:00 PM, Aurelien Jarno wrote:
> On 2017-05-18 11:08, Rob Landley wrote:
>> Serial input hangs after the first character in the 4.11 kernel:
>>
>> http://www.spinics.net/lists/linux-sh/msg51183.html
>>
>> Because they enabled support for
On 05/18/2017 02:57 PM, Paolo Bonzini wrote:
>
>
> On 18/05/2017 18:08, Rob Landley wrote:
>> Serial input hangs after the first character in the 4.11 kernel:
>>
>> http://www.spinics.net/lists/linux-sh/msg51183.html
>>
>> Because they enabled suppo
Serial input hangs after the first character in the 4.11 kernel:
http://www.spinics.net/lists/linux-sh/msg51183.html
Because they enabled support for a buffer size thing QEMU doesn't
emulate right:
http://www.spinics.net/lists/linux-sh/msg51189.html
Rob
When I feed a second -append to qemu-system-i386 they don't get
concatenated, the second replaces the first. Why is it called "append" then?
Rob
As far as I can tell "qemu-system-arm -M vexpress-a9" only implements sd
card, not any conventional hard drive, and it uses an sdcard block size
of 262144 bytes rounded down. This means when I create a squashfs image
and feed it in through the sd card, it truncates it.
Wouldn't -sd rounding _up_ b
On Mon, Apr 13, 2015 at 6:29 AM, vt wrote:
> Hi, guys
>
> I saw the architecture code about mips in the qemu and kvm modules, so it is
> no doubt that mips cpu can be supported.
It looks like the 32 bit one should work fine. I haven't played with
64 bit yet but there's some support for it in the
On 09/01/14 03:07, Paolo Bonzini wrote:
> Il 01/09/2014 07:05, Rob Landley ha scritto:
>> If you grab http://landley.net/aboriginal/bin/qemu-system-sh4.tar.bz2
>> extract it and ./run-emulator.sh (which is a fairly straightforward
>> qemu-system-sh4 invocation on the incl
On 09/01/14 00:05, Rob Landley wrote:
> If you grab http://landley.net/aboriginal/bin/qemu-system-sh4.tar.bz2
> extract it and ./run-emulator.sh (which is a fairly straightforward
> qemu-system-sh4 invocation on the included kernel image and squashfs
> root filesystem), older qemu ve
If you grab http://landley.net/aboriginal/bin/qemu-system-sh4.tar.bz2
extract it and ./run-emulator.sh (which is a fairly straightforward
qemu-system-sh4 invocation on the included kernel image and squashfs
root filesystem), older qemu versions would run it just fine, and ctrl-C
would pass through
On 11/12/2013 08:30:39 AM, Peter Maydell wrote:
On 12 November 2013 14:27, Xin Tong wrote:
> Hi
>
> I would like to know where i get can 32bit ARM image
For which board?
> with appropriate network driver.
Appropriate for what?
http://people.debian.org/~aurel32/qemu/armel/
has a simple versat
On 10/01/2013 12:19:51 PM, Richard Henderson wrote:
On 09/25/2013 12:27 PM, Richard Henderson wrote:
> Signed-off-by: Richard Henderson
> ---
>
> Since the GCC compile farm took their hppa machine off-line, I have
no way
> to test this port anymore. Worse, I can't find any distributions
tha
On 09/30/2013 12:25:45 PM, Min LI wrote:
Dear all,
I am very interested in QEMU and trying to figure out the boot
process of guest VM. According to my understanding about QEMU code,
bochs BIOS is loaded into memory by pc_system_firmware_init(…).
However, I notice QEMU handles hardwar
On 10/02/2013 06:40:18 PM, Laurent Vivier wrote:
Le 02/10/2013 20:42, Rob Landley a écrit :
Laurent Vivier has an m68k gitorious branch to add the q800 target,
which
I've occasionally tested and would really really like to see
finished and
merged.
Alas, last time I tested it the s
On 10/02/2013 12:09:58 PM, Anthony Liguori wrote:
All of Paul's emails are bouncing and he hasn't been active for
some time.
...
M68K
-M: Paul Brook
-S: Odd Fixes
+S: Orphan
F: target-m68k/
F: hw/m68k/
Laurent Vivier has an m68k gitorious branch to add the q800 target,
which I've occasi
On 09/11/2013 07:54:32 AM, Claudio Fontana wrote:
This is the aarch64 libvixl support patchset in the current state.
It provides (limited) support for disassembly output on aarch64.
Only host disassembly is enabled, since target for aarch64 is not in
yet.
An external objdump solution as exem
On 09/02/2013 11:07:03 AM, Aurelien Jarno wrote:
On Fri, Aug 23, 2013 at 12:47:43PM -0700, Richard Henderson wrote:
> I've been thinking for a while about how to reliably test TCG
backends, and
> maybe how to do regression testing on them. Having to begin the
test from a
> guest binary, espe
On 08/18/2013 08:57:08 AM, Herbei Dacian wrote:
good to know.
I was working back in 2005-2006 with a company that had a 4MB kernel.
At that time I was too inexperienced to work at that level but I
thought now I could reproduce their work with some help.
Anyhow for the moment I'll go for 256 MB
On 08/16/2013 11:17:06 AM, Herbei Dacian wrote:
my system should run in far less memory. something like 2-4MB.
but first I need to have a system running so that I can monitor with
qemu the addresses accessed for read execute and write by the code
run by the emulator.
if I reach that is a rea
On 08/15/2013 09:18:48 AM, Herbei Dacian wrote:
but you said that "qemu-system-arm" is not maintained and it doesn't
work.
Who said that?
git log --pretty=format:"%h %ci %s" hw/arm
be2f78b 2013-08-05 11:46:58 -0500 pxa2xx: Avoid
object_get_link_property() asser
cfc6b24 2013-07-29 21:06:2
On 08/15/2013 09:01:19 AM, Herbei Dacian wrote:
yes but which binary do I use to call to run an emulated arm image?
is there an actual binary that can emulate an existing arm board,
anyboard?
qemu?
if not which is the emulator that works with arm?
If not where is the project that I can tweak
On 08/15/2013 06:53:30 AM, Andreas Färber wrote:
Hi,
Am 15.08.2013 10:57, schrieb Herbei Dacian:
>
> please, can anyone recommend me a distribution that offers a
barebone
> linux kernel.
> minimum that I need on that image are:
> _ the kernel
> _ the compiler and development infrastructure to
On 08/12/2013 11:45:49 AM, Russell King - ARM Linux wrote:
On Mon, Aug 12, 2013 at 05:24:50PM +0100, Peter Maydell wrote:
> On 12 August 2013 01:40, Guenter Roeck wrote:
> > On 08/11/2013 03:04 PM, Russell King - ARM Linux wrote:
> >> It could be that it's qemu's PCI routing is wrong - it's not
On 07/31/2013 12:19:03 AM, Stefan Weil wrote:
Am 31.07.2013 03:50, schrieb Erik de Castro Lopo:
> Hi all,
>
> I have a patch I would like to submit and I am currently running it
past
> my employer's legal department. The legal department has identified
10
> different licenses in the Qemu code
On 07/23/2013 12:16:53 AM, Renich Bon Ciric wrote:
Hello,
I am new to this...
I'm trying to run some rom file I got from a client. It's a sc2005
processor; supposedly compatible with 4k.
Anyway, I do this:
qemu-system-mips -M mips -pflash 301-3100\ -\ user\ specified\ -\
Full.bin -serial stdi
On 07/10/2013 08:49:35 AM, Richard Henderson wrote:
On 07/09/2013 10:43 AM, Rob Landley wrote:
> Do you have a kernel .config that boots on this board? I'd really
like to try
> this out myself...
I haven't worked on this in quite some time. But I've located two
bra
Prebulit binaries of all of the above are at:
http://landley.net/aboriginal/bin
The "system-image" tarballs are bootable system images, tested under
qemu 1.5.1, which provide a shell prompt on qemu's stdin/stdout and a
native compiler capable of building Linux From Scratch inside the
emu
On 07/08/2013 08:01:08 PM, Richard Henderson wrote:
The recent changes for ioport memory regions is a blessing and a
curse for the simplified alpha machine model we have.
On the one hand, we can eliminate two hacks present in the tsunami
system chip emulation. We also now get machine checks whe
On 06/29/2013 06:03:26 AM, Peter Maydell wrote:
On 28 June 2013 08:01, Rob Landley wrote:
> Now that the next kernel's about to come out, I'm trying to get my
arm
> versatile image to work under qemu 1.5.0. The old kernel doesn't
work, and
> the current vanilla k
On 06/29/2013 03:29:08 PM, Olivier Danet wrote:
How embarrassing...
- QEMU 1.5.1 can boot Debian Etch (kernel 2.6.18), RedHat 4.2 (kernel
2.0.30), NetBSD 6.1 and OpenBSD 5.3.
- Your image (Linux 3.8) can be started with a TurboSparc CPU :
qemu -cpu "Fujitsu MB86907".
Yay! That fixes it. Th
On 07/04/2013 04:52:45 PM, Olivier Danet wrote:
On 29/06/2013 22:29, Olivier Danet wrote:
On 28/06/2013 23:44, Mark Cave-Ayland wrote:
On 28/06/13 03:08, Rob Landley wrote:
Commit 467b34689d27 upgraded the openbios image, and ever since my
linux
system images hang about the time they try to
On 04/08/2013 03:16:18 PM, Peter Maydell wrote:
On 8 April 2013 18:37, Rob Landley wrote:
> On 04/06/2013 10:44:25 AM, Peter Maydell wrote:
>>
>> This patch series fixes a number of serious bugs in our emulation
of
>> the PCI controller found on VersatilePB and the ea
I have images that boot under qemu-system-sh4 at:
http://landley.net/aboriginal/bin/system-image-sh4.tar.bz2
But in order to get them to work with current kernels, I have to apply
the attached sh4.patch to qemu.
What I did with earlier kernels was apply the attached
linux-fixsh4-2.patch
Commit 467b34689d27 upgraded the openbios image, and ever since my
linux system images hang about the time they try to initialize
interrupts.
http://landley.net/aboriginal/bin/system-image-sparc.tar.bz2
Extract that and "./run-emulator.sh" in the tarball. Using qemu 1.2.0
for example works
I intermittently get this from current kernels running under currentish
qemu-git. Look familiar to anybody?
reboot: machine restart
general protection fault: fff2 [#1]
CPU: 0 PID: 44 Comm: oneit Not tainted 3.10.0-rc7+ #3
Hardware name: Bochs Bochs, BIOS Bochs 01/01/2011
task: 8800068fd500
On 05/19/2013 03:09:14 PM, Mark Burton wrote:
Spot on Peter,
The (simplistic) plan is simply to take a snapshot at regular
intervals,
when you want to step backwards, you return to a snapshot, and then
re-run
forwards to 'just before you started'.
You'd have to snapshot all of memory becau
On 05/17/2013 12:23:51 PM, KONRAD Frédéric wrote:
On 09/05/2013 19:54, Blue Swirl wrote:
On Tue, May 7, 2013 at 6:27 PM, KONRAD Frédéric
wrote:
Hi,
We are trying to find a way to do reverse execution happen with
QEMU.
...
For now we tried some other things which are not working very well,
On 05/08/2013 04:45:45 AM, Torbjorn Granlund wrote:
Paolo Bonzini writes:
I guess that's the register windows. There's only so much you can
do to
optimize them, and heavily recursive workloads (like Perl, or the
RTL
half of GCC) pay a hefty price.
Two qemu targets stand out for slo
On 04/30/2013 04:31:29 PM, Artyom Tarasenko wrote:
On Mon, Apr 29, 2013 at 7:43 AM, Rob Landley wrote:
> On 04/27/2013 03:00:06 PM, Artyom Tarasenko wrote:
>>
>> > For a lot of the 64-bit targets, actual 64 bit userspace support
is
>> > strangely lacking. For ppc64
On 04/30/2013 01:36:39 PM, Anthony Liguori wrote:
The current release schedule has hard freeze happening tomorrow.
There
are a few things still outstanding including cpu hotplug and updating
SeaBIOS. We still need to resolve how to handle the softfloat code
too. I am particularly intereste
This issue here:
http://lists.nongnu.org/archive/html/qemu-devel/2012-07/msg03870.html
Still hits the 3.8 kernel by the way:
wget http://landley.net/aboriginal/bin/system-image-sh4.tar.bz2
tar xvjf system-image-sh4.tar.bz2
cd system-image-sh4
./run-emulator.sh
Still tracking down a d
On 04/27/2013 03:00:06 PM, Artyom Tarasenko wrote:
> For a lot of the 64-bit targets, actual 64 bit userspace support is
> strangely lacking. For ppc64 they say to use ppc32, and I've been
told that
> about sparc64 as well. I don't know if this is an optimization or a
> requirement. I have a 3
On 04/19/2013 05:27:55 AM, Mark Cave-Ayland wrote:
On 22/03/13 05:19, Rob Landley wrote:
If I do this:
qemu-system-sparc -nographic -no-reboot -kernel image -hda hda.sqf
-append 'root=/dev/sda rw init=/sbin/init.sh panic=1
PATH=/usr/distcc:/bin:/sbin console=ttyS0 HOST=sparc C
On 04/20/2013 05:36:46 AM, Blue Swirl wrote:
> I plan to add a sparc64 target built from source to Aboriginal
Linux.
>
> For a lot of the 64-bit targets, actual 64 bit userspace support is
> strangely lacking. For ppc64 they say to use ppc32, and I've been
told that
> about sparc64 as well.
On 04/14/2013 04:38:23 AM, Artyom Tarasenko wrote:
On Sat, Apr 13, 2013 at 7:03 PM, Rob Landley wrote:
> On 03/26/2013 02:34:50 AM, Artyom Tarasenko wrote:
>>
>> On Tue, Mar 26, 2013 at 1:52 AM, Rob Landley
wrote:
>> > Can the virtio things (serial, network, b
On 04/14/2013 02:49:53 PM, Artyom Tarasenko wrote:
On Sun, Apr 14, 2013 at 11:59 AM, Mark Cave-Ayland
wrote:
> On 14/04/13 10:38, Artyom Tarasenko wrote:
>
>>> Do you have an example kernel .config and qemu command line
showing how
>>> to
>>> use virtio for those? (Or a working sparc64 image
On 03/26/2013 02:34:50 AM, Artyom Tarasenko wrote:
On Tue, Mar 26, 2013 at 1:52 AM, Rob Landley wrote:
> Can the virtio things (serial, network, block, virtfs) be used on
arbitrary
> targets yet? I.E. Can I use a virtio network device on arm, mips,
powerpc,
> sparc...
Yes. More
On 04/06/2013 10:44:25 AM, Peter Maydell wrote:
This patch series fixes a number of serious bugs in our emulation of
the PCI controller found on VersatilePB and the early Realview boards:
* our interrupt mapping was totally wrong
Yes. Yes it was. However, what you were doing matched the kernel
On 04/04/2013 04:57:32 AM, Artyom Tarasenko wrote:
On Thu, Apr 4, 2013 at 11:50 AM, Alexander Graf wrote:
>
> On 04.04.2013, at 11:46, Artyom Tarasenko wrote:
>
>> On Thu, Apr 4, 2013 at 10:37 AM, Fabien Chouteau
wrote:
>>>
>>> On 04/03/2013 06:59 PM, Alexander Graf wrote:
On 03.04
On 03/28/2013 03:12:11 PM, H. Peter Anvin wrote:
On 03/28/2013 12:15 PM, Aurelien Jarno wrote:
>
> This really looks like Linux kernel specific. I haven't been able to
> test on a real machine, but the documentation I have found suggest
that
> without and x87 FPU, the FPU instructions are simpl
On 03/25/2013 08:24:44 PM, Richard Henderson wrote:
On 2013-03-25 17:52, Rob Landley wrote:
Can the virtio things (serial, network, block, virtfs) be used on
arbitrary
targets yet? I.E. Can I use a virtio network device on arm, mips,
powerpc,
sparc... (And can the virtio serial console hook
On 03/25/2013 08:17:44 AM, Juan Quintela wrote:
Hi
Please send in any agenda topics you are interested in.
Later, Juan.
If Google summer of code is still open:
http://qemu-project.org/Google_Summer_of_Code_2013
Last I checked, the older targets haven't had a lot of love. QEMU still
doe
1 - 100 of 382 matches
Mail list logo
