On 24 March 2014 19:49, Joel Fernandes wrote:
> Now, I start gdb with -s -S options to halt on startup, and step
> through, each time I'm dumping the register set:
> ..
> Reading symbols from /home/joel/data/repo/linux-omap1/vmlinux...done.
> (gdb) info registers
> r0 0x0 0
> r1
On 26 May 2014 07:15, Mallikarjun Goudar wrote:
> Hi,
> I built an "'hello world" application using aarch64-none-elf-gcc (linaro gcc
> tools). And I tried to run generated elf using following command:
>
> qemu-system-aarch64 -M virt -cpu cortex-a57 -nographic -serial null
> -monitor null -semihos
On 28 May 2014 09:58, Radu Velea wrote:
> I've been using QEMU in user mode to run an executable with debug mode and
> I've noticed that the number of assembly instructions differs from one
> runtime to another, even for a trivial "hello world". Is there an
> explanation for this?
>
> qemu-aarch64
On 4 June 2014 17:32, Waldemar Brodkorb wrote:
> I am trying qemu-system-i386 -alt-grab and -ctrl-grab
> on MacOS X Maverick, but both are ignored in Qemu 2.0.0.
>
> On Linux I at least get:
> -alt-grab and -ctrl-grab are only valid for SDL, ignoring option
>
> So I need to recompile qemu with SDL
On 11 June 2014 00:50, Steere, Andy wrote:
> Curious I wrote a simple script to start all the qemu-system-*.exe files in
> the distribution without any arguments. The results were mixed. Some of the
> qemu exes start a qemu window. Others write to the event log and the last
> group does not write
On 10 June 2014 16:25, Matwey V. Kornilov wrote:
> Only this instructions are executed:
>
> >│0x6000 <_start> movr0, #0
> │
>│0x6004 <_start+4> ldrr1, [pc, #6397080]
> ; 0x6010
On 13 June 2014 09:50, Matwey V. Kornilov wrote:
> I am stuck here. I've put u-boot binary on the 0 of flash.bin (which
> is 67108864 bytes long), and run following
>
> qemu-system-arm -M vexpress-a9 -pflash pflash.bin -S -s
>
> I have no warnings, but when I attach with gdb I either don't see m
On 13 June 2014 18:10, Steere, Andy wrote:
> Thanks for the clarifying. I now understand that not passing arguments would
> get different behavior so I will ask a simpler form of my question.
>
> Running "qemu-system-mipsel --help" on Ubuntu 14.0 gives a help message.
>
> Should Windows "qemu-sys
On 17 June 2014 22:07, Steere, Andy wrote:
> On to the real problem - running qemu mipsel with a Debian release on a
> Windows 7, 64bit machine.
>
> 1. Installed the Windows 64 bit Qemu from here: http://qemu.weilnetz.de/w64/
>
> 2. Use the vmlinux and qcow from here:
> http://people.debian.org/
On 23 June 2014 01:28, Davor Herga wrote:
> Hello!
>
> Following some guidelines for using the qemu, I tried to use
> qemu-system-mipsel
> for the brcm47xx using openwrt-brcm47xx-generic-vmlinux-initramfs.elf, build
> by openwrt buildroot tools.
>
> Using the command -
>
> qemu-system-mipsel -kern
On 25 June 2014 13:01, Programmingkid wrote:
> On Jun 24, 2014, at 12:00 PM, qemu-discuss-requ...@nongnu.org wrote:
> I use -soun???dhw ac97,hda but it still print "??audio: Could
> not init `oss' audio driver"? , and sound hw in the guest os(win7).
This message comes from the audi
On 29 June 2014 05:08, Programmingkid wrote:
> On Jun 28, 2014, at 7:04 PM, Peter Maydell wrote:
>> Our default of OSS made sense at the time, but since I think
>> most modern Linux distros have moved away from it it
>> might be worth reconsidering that choice. (The trouble i
On 30 June 2014 13:01, Rekha Herur wrote:
> We are using Fast-model (FastModelsPortfolio_9.0) to simulate ARM cortexA15.
> We are building qemu 1.7 for arm but getting these errors ,
>
> CCtests/qemu-iotests/socket_scm_helper.o
> LINK tests/qemu-iotests/socket_scm_helper
> /usr/lib/gcc/ar
On 1 July 2014 06:58, Rekha Herur wrote:
> Hi Peter,
> Thanks for the reply ..Here is the configure i used
>
> srv/nfsroot/root/qemu-1.7.1# ./configure
> --cross-prefix=arm-linux-gnueabihf- --target-list=arm-softmmu
> --audio-drv-list="" --disable-libusb --disable-gtk --enable-fdt --en
On 1 July 2014 09:01, Magyar Péter wrote:
> I also wanted to cross compile for win32 under linux and ran into several
> issues, like it complained about zlib first, then lgthread and glib. Since i
> am not an expert of building apps under linux, not to mention cross
> compiling, finally i chosed t
On 7 August 2014 21:45, Raghunath Lolur
wrote:
> I am using qemu-system emulator (qemu-system-aarch64) and gdb
> (aarch64-linux-gnu-gdb) to debug a c program, both running on the same
> system, i686-pc-linux-gnu on Ubuntu 12.04 LTS. However, with the gdb,
> if I set a breakpoint and issue 'continu
On 18 August 2014 07:09, Tony Su wrote:
> Unless someone says differently,
> I believe that doesn't change the likely fact that the main KVM is
> different than what you are doing and would perform much better.
No, Julio is correct. The KVM functionality was all merged
into upstream QEMU, and th
On 18 August 2014 15:32, Dale R. Worley wrote:
> The "per each function call" metric is tricky, because you'd need to
> define what a "function call" is.
In particular, on some guest CPU architectures it's genuinely
not possible to reliably distinguish function call return from a
computed branch.
On 3 September 2014 12:05, 孙贝磊 wrote:
> How can Linux read the information from Qemu, for example, the cache miss
> rate.
QEMU doesn't emulate caches and so we don't track
statistics like cache miss rates at all.
-- PMM
On 5 September 2014 04:52, wrote:
> Since, for RPi, 'armv6l' is the correct arch, where in the qemu config/setup
> -- either on host or in CHROOT -- can the default arch be set so that 'just'
>
> chroot /opt/raspbian-chroot bash -c "uname -rm"
>
> correctly returns
>
> 3.16.1-7.g
On 15 September 2014 12:07, Paul Gydos wrote:
> Again I have my reasons, I'm hoping not to be convinced away from QEMU but
> I'm hoping someone might help me get started with Natively Compiling QEMU
> in W32. So now that I'm clear that I'm staying with QEMU for now. Who is up
> to the bizzaro chal
On 18 September 2014 10:13, Tony Lapointe wrote:
> Hi List,
>
> I am using qemu on gentoo, trying to boot arm based images but, i am
> facing some issues.
>
> With qemu-system-arm, i am unable to boot with a kernel that i have
> compiled myself (with crossdev) but the same kernel boot just fine on
On 18 September 2014 12:14, Dave Flogeras wrote:
> I have used aboriginal linux (http://landley.net/aboriginal/) 1.2.8 to
> create a musl based root filesystem with the following command:
>
> MUSL=1 ./build.sh armv6l
>
> After this I set up binfmt to call a qemu-arm (which I have build
> staticall
On 18 September 2014 14:09, Max Gorley wrote:
> Here is the full output (starting with shell):
>
> root@MAX-HP:~/qemu-pi/qemu# make
> CCui/gtk.o
> ui/gtk.c: In function ‘gd_vc_vte_init’:
> ui/gtk.c:1460:7: error: ‘VirtualConsole’ has no member named ‘vte’
> vc->vte.chr = chr;
>^
On 19 September 2014 00:32, Mauro Molinari wrote:
> qemu: uncaught target signal 11 (Segmentation fault) - core dumped
> Segmentation fault
>
> followed by other error messages saying that the child process (the build
> one) failed.
This doesn't inherently come from QEMU -- if the guest process
w
On 19 September 2014 05:11, Dave Flogeras wrote:
> Similar to yesterday, in my qemu chroot
> (armv6j-hardfloat-linux-musleabi) I am seeing un-supported syscalls
> related to get/set/list xattr. However, unlike yesterday, I looked
> into the linux-user/arm/syscall_nr.h and those syscalls (226 thro
On 22 September 2014 00:10, Mauro Molinari wrote:
> I see... so, the "qemu:" prefix doesn't mean the error comes from QEMU...
> It's just strange that a standard Debian package does not build.
Not everything will run under QEMU, our emulation has weak
spots. The most common one is where the progr
On 22 September 2014 07:08, Ronen Meir wrote:
> Is there a scheduled release update to support ARM v8 architecture?
Er, it's already supported. linux-user mode works from 2.0,
and system emulation from 2.1.
-- PMM
On 23 September 2014 14:42, Paul Gydos wrote:
> your email goes out fine - it takes a half hour for the
> server to update
Occasionally if the list server is having a bad day it
can lag by hours, but mostly it's just a few minutes.
If you're wondering if a mail you sent has gone out then
it's bet
On 26 September 2014 09:58, Mauro Molinari wrote:
> Il 22/09/2014 12:50, Peter Maydell ha scritto:
>> Not everything will run under QEMU, our emulation has weak spots. The most
>> common one is where the program you're running uses multiple threads -- this
>> isn'
On 29 September 2014 12:37, Chan Kim wrote:
> So whatever 32bit value I write, it should be seen as such
> at the device's qemu write function. Isn't this the normal
> behavior? (If I write 0x12345678, it is seen 0x12345678 not
> 0x78563412).
This depends on what the MemoryRegionOps struct for
th
On 30 September 2014 16:18, Brad Smith wrote:
> Anyway, I can now boot the Debian installer. But I'm still having problems
> when I try to boot the Cubuietruck version of lubuntu. Specifically, it
> fails with a "qemu: fatal: Trying to execute code outside RAM or ROM at ..."
> error.
This error m
On 6 October 2014 03:38, Paul Gydos wrote:
> I have hit a snag with -kernel and -initrd arguments which cause QEMU to
> not launch no matter how they are phrased - is Direct Linux Booting not
> supported on this particular Debian Cross Compiled QEMU for Windows?
> But even with community help
On 6 October 2014 19:13, Jeshwanth Kumar N K wrote:
> I am working on an Cortex-m4 chip from Atmel, was searching whether Qemu
> supports for that architecture.
>
> My question is, Qemu supported for Cortex-m3 and M4 architecture ? If not,
> is there any development is going on in these processors
On 9 October 2014 01:35, ta0590897 wrote:
> Under Lubuntu 14.04, here's the cmdline:
> ./configure --target-list=i386-softmmu --cross-prefix=i686-w64-mingw32-
> --static --disable-sdl --enable-gtk --disable-kvm --disable-curl
> --disable-vnc --disable-fdt --disable-rdma
>
> ERROR: zlib check faile
On 14 October 2014 09:57, Yash Nandkeolyar wrote:
> Hi,
>
> We are trying to migrate an AArch64 VM using Qemu version 2.1(latest). I
> tried with Live and Offline migration. However, same error is observed in
> both cases:
>
> qemu-system-aarch64: Unknown migration flags: 0
>
> qemu: warning: erro
On 16 October 2014 21:31, Pranith Kumar wrote:
> I am trying to gather some instruction execution statistics of a
> multi-threaded program by adding some counters in TCG.
>
> I've learnt that multi-threaded execution is not supported in user
> mode and in system mode with TCG. Is KVM the only mode
On 18 October 2014 05:12, Sandeep Joshi wrote:
> I'd like to write a QEMU block driver which forwards IO requests to a
> custom-built storage cluster.
>
> I have seen Jeff Cody's presentation and also browsed the source code for
> sheepdog, nbd and gluster in the "block" directory and had a few qu
On 23 October 2014 02:47, Urmish Ajit Thakker wrote:
> Hi,
>
> I am trying to chroot into an arm system from a x86 host. However, I keep
> getting the following error
>
> chroot: failed to run command `/bin/bash': Exec format error.
>
> I think I have already installed the required files and I am
On 23 October 2014 18:28, Urmish Ajit Thakker wrote:
> 3) usr/bin/qemu-arm-static bin/ls
> E - Error while loading bin/ls: No such file or directory
>
> Note : bin/ls exists
>
> 4) sudo chroot . /usr/bin/qemu-arm-static /bin/ls
> R - /bin/ls: Invalid ELF image for this architecture
>
> 5) sudo chr
On 23 October 2014 22:51, Urmish Ajit Thakker wrote:
> Some more info -
>
> I am running an Ubuntu 12.04 machine.
>
> Disk Image is for armv8 architecture. (64 bit).
Ah, I had wondered. qemu-arm-static is for 32 bit ARM.
For 64 bit you want qemu-aarch64-static...
> So my ls -l bin/ls gives me th
On 24 October 2014 23:38, Urmish Ajit Thakker wrote:
> ...and if you run 'file' on that...?
>
> This is the file result in/busybox.nosuid: ELF 64-bit LSB executable,
> version 1 (SYSV), dynamically linked (uses shared libs), for GNU/Linux
> 3.7.0, BuildID[sha1]=0x449d66054f43dcae8f28ccd92e17
On 31 October 2014 14:46, Kai Liu wrote:
> Hi,
> I downloaded the qemu binary file and installed on my win7 64-bit machine. I
> can run qemu-system-i386.exe to load my own disk image. It seems to be
> working. One strange thing is that the console window (cmd) does not give me
> any output or erro
On 9 November 2014 15:37, Ronen Meir wrote:
> I'm using Qemu with ARM as target OS.
>
> As far as I understand QEMU executes full translation blocks (TB). I would
> like to isolate and debug a specific instruction within a translation block.
That depends on what you mean by "debug". The simples
On 10 November 2014 14:56, James Kelly wrote:
> I've used buildroot to compile a firmware targeting the LPC EA3250 board,
> I'm trying to get this to run using qemu so that I can test changes to the
> firmware on my machine.
Firmware typically requires that it runs on the actual
hardware in quest
On 11 November 2014 17:28, Dave Flogeras wrote:
> I have a qemu-arm chroot, inside of which I am trying to build
> chromium (probably stupid). At the linking phase, it falls over,
> running out of memory. I am just wondering what the memory limit
> inside of a 32bit arm chroot is (or is that a lo
On 14 November 2014 20:01, Assaf Gordon wrote:
> A newbie question about using QEMU on Mac OS-X host:
> What is the support of hardware acceleration when using an x86_64
> Mac OS X host with X86_64 guest ?
At least in mainline, there is none.
> I assume KVM is not supported.
> Is TCG relevant (o
On 21 November 2014 09:47, harsh jain wrote:
> Hi,
>
> Can we use the -vnc option to launch ARM64 VM to access console.
The only currently supported 64-bit ARM board is "virt", which
has no display (graphics) device at all, so -vnc is not going
to be any use. You want to use QEMU's options for di
On 22 November 2014 at 09:39, harsh jain wrote:
> Thanks Peter for quick reply.
> The VM is redirecting the serial port output to text file in Host
> machine. Find below the libvirt.xml file content.
>
>
>path='/etc/nova/instances/784ec496-bab6-4349-91f0-42effad0afa6/console.log'/>
>
On 26 November 2014 at 07:42, edonli wrote:
> Hello everyone,
>
> I have happened to an error when running 'qemu-system-aarch64' of version
> qemu-2.2.0-rc3.
> The error is "*** stack smashing detected".
> The start command is "qemu-system-aarch64 -m 1024 -cpu cortex-a57 -nographic
> -machine virt
On 26 November 2014 at 11:55, Peter Maydell wrote:
> On 26 November 2014 at 07:42, edonli wrote:
>> Hello everyone,
>>
>> I have happened to an error when running 'qemu-system-aarch64' of version
>> qemu-2.2.0-rc3.
>> The error is "*** stack s
On 26 November 2014 at 12:19, edonli wrote:
>
> Thanks for your reply.
> The environment I use:
> * Linux 2.6.18 CentOS
> *GNU gcc version 4.1.2
> *There is no configure flag to build QEMU, I just execute './configure
> --prefix=/home/myname/qemu' .(There was no flags to build qemu-0.15
>
On 27 November 2014 at 02:47, wrote:
>Many instructions can output only one return value by cpu_T[0] parameter,
> and input parameter is cpu_T[0], there is no other parameter to use for
> output more return value. How can I do it?
>
>For example:
>
> Common instruction: ADD, the out
On 27 November 2014 at 12:24, edonli wrote:
>
> I have rebuilt qemu-2.2.0-rc3 with "--enable-debug".
> Luckily，there is no running 'error'.
> Unfortunately， there is no any response since started. Using command 'top',
> the process is running normally without any output.
> How can this things hap
On 28 November 2014 at 02:27, wrote:
> Hi，Peter
> Many thanks for you to reply, I am confused here in many days. Thanks you
> very much.
> Another problem, my instruction “Getsec” want to output 3 return value to
> eax/ebx/ecx and only one input parameter eax.
> But the return value eax
On 28 November 2014 at 03:32, edonli wrote:
> Can you tell me what`s your compile environment, and what img or kernel you
> used to build your QEMU.
I currently build QEMU primarily on x86-64 Ubuntu 14.04 ("trusty"),
with the stock gcc for that distro, which is 4.8.2-19ubuntu1. The
host kernel is
On 29 November 2014 at 11:31, Jones Smith wrote:
> I am using QEMU from MacOSX, and I would like to emulate an arm system
> directly from my SD card (which I can do from Arch Linux).
>
> Actually, I can emulate the image of my SD card successfully (i.e. the *.img
> file that I flashed on the SD ca
On 1 December 2014 at 02:53, wrote:
> Hi, Peter
>1) cpu_T[2] and cpu_T[3] have been built by me as same as cpu_[0] &1.
Don't do that. Use local temporaries as I have been suggesting.
>2) tcg_gen_getsec_tl(R_EAX, R_EBX, R_ECX, cpu_T[1]); I tried
> it before, but the result is not my expe
On 1 December 2014 at 10:25, wrote:
> Firstly, I tell you about my instruction -- Getsec (opcode is 0f 37), it
> is about the x86 arch safer mode . I want to emulate it by QEMU.
> Then, the function of Getsec is so complicated. There are
> many jmp or je/z opcode in this function. Accord
On 4 December 2014 at 09:01, wrote:
> Hi, Experts
>
>I implement special function by helper function just used on x86 host. I
> can get the value of common registers (eg: eax,ebx), and this value of eax
> means the physical memory address. But when I access the content of this
> physical memo
On 10 December 2014 at 07:58, wrote:
> 4) Execute the binary
>
> ((int (*)(void))(env->eip))();
This makes no sense. You're taking a guest virtual address
(EIP value) and treating it as a host function pointer.
This is obviously going to crash.
-- PMM
On 12 December 2014 at 03:52, wrote:
> Hi, Peter and all
>I am still confused on that problem, I delete the code "((int
> (*)(void))(env->eip))();" and just change env->eip to my image entrypoint, In
> the end the qemu is crash with useful information. After executing my helper
> function,
On 17 December 2014 at 17:23, Jakob Bohm wrote:
> On 17/12/2014 14:36, Kevin Grandemange wrote:
>>
>> I am trying to boot my own "kernel" with qemu-microblaze but I can't get
>> it running.
>> I tried the following cmdline:
>>
>> qemu-system-microblaze img.elf
>> qemu-system-microblaze -M petalogi
On 21 December 2014 at 16:29, sacarde wrote:
> if I run:
> qemu-system-x86_64 -cdrom /home/sacarde/dati-estranei/q2/neon5-latest.iso
> -enable-kvm -k
> en-us -net nic -net tap,vlan=0,ifname=tap0 -boot d
>
> I have error: http://digilander.libero.it/sacarde/np/manjaro1.jpg
For both of these comma
On 25 December 2014 at 11:04, jiang wrote:
> Hello all:
> I try to run uboot(from some router(cpu:QCA9533 24Kc)) with
> qemu-system-mips,but there are some problems.
It seems unlikely that a boot loader intended for a specific
bit of router hardware will run on any of the board models
we supp
On 30 December 2014 at 21:26, Rishi Ranjan wrote:
> I was able to get this working. Xen headers were not getting included
> correctly. But now I am getting following error:
>
> qemu: hardware error: map shared IO page returned error 3
> handle=0x7f9af6a7e7a
>
> I don't see any documentation on use
On 30 December 2014 at 23:27, Rishi Ranjan wrote:
> Hi Peter,
> The reason I asked this question here is that the errors I am
> getting is from the Qemu code which tries to use the guest Dom. The error is
> not coming from Xen as such. May be I can send the mail to qemu-devel list.
B
On 8 January 2015 at 05:32, Pratyush Anand wrote:
> Have anyone tried to test single step exception with ARM64 on Qemu?
> My Qemu version is:
>
> QEMU emulator version 2.1.2, Copyright (c) 2003-2008 Fabrice Bellard
AArch64 single step emulation was only added in QEMU 2.2...
-- PMM
On 9 January 2015 at 21:23, Evan Driscoll wrote:
> I am running an ARM program in single-process mode with '-d exec', and
> either the resulting traces are incomplete, I don't understand them, or
> something else is going on. Tried with QEMU 2.2.0; more detailed info about
> how things are built &
On 12 January 2015 at 00:44, Peter Fillmore wrote:
> heres the code which creates the memory (contained in a custom driver):
>
>> memory_region_init_ram(&s->iomem, OBJECT(dev), "arm-lpc213x-iap", 0x1000,
>> NULL);
>> sysbus_init_mmio(sd, &s->iomem);
>> char *memptr = memory_region_get_ram_ptr(&s-
On 12 January 2015 at 23:18, Peter Fillmore wrote:
> The setup code is :
> MemoryRegion *sysmem = get_system_memory();
> MemoryRegion *iap = g_new(MemoryRegion, 1);
> //create pointer for region
> memory_region_init_ram(iap, NULL, "vivot
On 14 January 2015 at 01:47, Evan Driscoll wrote:
> I have another question vaguely related to my previous one. To recall, I'm
> running QEMU in single-process mode on an ARM program, passing -d
> exec,in_asm and trying to reconstruct the program's execution trace.
>
> Unfortunately, I don't have
On 14 January 2015 at 07:28, ravali pullela wrote:
> I would like to know if kvm maintains a cache of the mappings from guest
> virtual address to host physical address or any related mappings? Does
> flushing the host tlb entries do a flush of these mappings as well. Please
> kindly let me know o
On 16 January 2015 at 11:54, lux-integ wrote:
> Dear qemuers,
>
> I am new to this list. I am trying to compile qemu-2.2.0 statically
> My System has these:
> GCC-4.8.1, linux-3.10.61. I configure qemu-2.2.0 with the following
> switches:-
The static build is only really supported for use with
On 20 January 2015 at 12:10, Chan Kim wrote:
> when I run 'make', I get
> $make
> ...(many lines from make)...
> lt LINK vscclient
> /usr/bin/ld: -f may not be used without -shared
> collect2: ld returned 1 exit status
> make: *** [vscclient] Error 1
> $
>
> If I remove --disable-pie, I don't see
On 26 January 2015 at 17:26, Javier Picorel wrote:
> Dear all,
>
> We are trying to make QEMU deterministic for
> architectural simulation. In the absence of I/O,
> let’s say only user code or exceptions, is there
> any source of indeterminism (e.g., non deterministic
> compiler optimizations, TB
On 28 January 2015 at 02:51, Dale R. Worley wrote:
> Javier Picorel writes:
>> We are trying to make QEMU deterministic for
>> architectural simulation. In the absence of I/O,
>> let's say only user code or exceptions, is there
>> any source of indeterminism (e.g., non deterministic
>> compiler o
On 28 January 2015 at 16:02, Stefan wrote:
> I'd like to emulate an armhf platform with at least 2, better 4
> or more GB RAM, allthough didn't find one supported by qemu.
> (most was vexpress-a9 with up to 1 GB)
vexpress-a15 allows up to 30GB (assuming a 64-bit host system;
32-bit hosts are alwa
On 29 January 2015 at 12:36, eth0 wrote:
> I'm trying to run a ARM32 binary within qemu but I get seg fault:
>
> root@debian:~/squashfs-root# chroot . ./qemu-arm bin/xxx
> qemu: Unsupported syscall: 983040
> qemu: Unsupported syscall: 983040
> qemu: uncaught target signal 11 (Segmentation fault) -
On 3 February 2015 at 17:05, Attila Csosz wrote:
> GCC command line
> arm-none-eabi-gcc -o main.elf main.c -g -mcpu=cortex-m3 -mthumb
> --specs=rdimon.specs -lc -lrdimon
You're building for the Cortex-M3...
> Starting QEMU
> qemu-system-arm -machine versatilepb -nographic -monitor null -serial n
On 3 February 2015 at 17:37, Attila Csosz wrote:
> Tried with the new board but the result almost the same. The programs stays
> at 0x after Ctrl+C
Well, is your program targeting that board? Does it (for instance)
link at an address corresponding to flash or RAM on those
boards? Does it have
On 4 February 2015 at 14:13, wrote:
> We are currently trying to launch an Ubuntu guest OS (with
> virtualization/kvm) on a Cortex-A15/Exynos 5250 Arndale board with the
> following qemu command line :
>
> qemu-system-arm \
> -enable-kvm \
> -m 512 -M vexpress-a15 -cpu cortex-a15 -smp 2 \
> -d
On 5 February 2015 at 09:51, Eric Valette wrote:
> This is a pity :
>
> KVM -> Cortex A15 (ok or A17 or A57) -> Host A15 -> Guest A15 -> NO USB
Right, but USB devices aren't a very common use case for servers,
which is what KVM has been primarily targeting.
> And seen in the doc the way you shou
On 5 February 2015 at 10:32, Eric Valette wrote:
> Virtualization on Intel/AMD world is also used to emulate different OS
> (windows on linux, android x86, ...) and there you need performance that you
> can only achieve using KVM...
But you still don't need USB particularly.
> I would like to em
On 5 February 2015 at 10:44, Eric Valette wrote:
> On 05/02/2015 11:39, Peter Maydell wrote:
>> For Android emulation you'll need 3D acceleration to get good
>> performance anyway, which upstream QEMU doesn't have.
> Granted.
You might want to investigate the new up
On 5 February 2015 at 16:11, wrote:
> I just found out that mouse and keyboard are working correctly
> BUT the issue is that QEMU graphical window is badly refreshed...
> It's also linked to my other message about the graphical issue.
Can you confirm which host OS and which of QEMU's UI frontend
On 5 February 2015 at 16:26, wrote:
> On 5 February 2015 at 16:11, wrote:
>> I just found out that mouse and keyboard are working correctly
>> BUT the issue is that QEMU graphical window is badly refreshed...
>> It's also linked to my other message about the graphical issue.
>
> Can you confirm
On 6 February 2015 at 13:44, wrote:
> I just tested with current qemu version (version 2.2.50 after a
> "git clone git://git.qemu-project.org/qemu.git") and I still
> have the same issue... Can I test something to find out where
> does this issue comes from ? Can I use another frontend ?
If you
On 4 March 2015 at 20:16, Srinath M wrote:
> I am new to qemu and want to run a program meant for arm-cortex-m3 on an
> i386.
>
> So i ran the following command
>
> ./qemu-system-arm -cpu cortex-m3 -S -s -singlestep -nographic -m 513 -kernel
> hello.elf
>
> I get the following output
> No machine
On 4 March 2015 at 23:32, Srinath M wrote:
> The binary is for a very custom board.
> http://autoquad.org/
> I have replaced the sensor reading tasks with an onboard simulation that
> feeds 'virtual sensor values' to the STM32F4. This way the executable is now
> entirely self contained and doesn't
On 7 March 2015 at 00:54, Jakob Bohm wrote:
> Life would be so much easier if the Arm "machines" supported
> by the Linux kernel, qemu etc. were more like the PC
> architectures:
Well, perhaps, but the ARM ecosystem is not like x86.
In x86 everything in the world is basically identical
(it's a PC
On 25 March 2015 at 18:51, anand.k wrote:
> I am trying QEMU for the first time. I am trying to emulate a ARM machine
> using qemu-system-arm.
>
> But when I executed this command,
> $ qemu-system-arm -M versatilepb -kernel zImage.integrator -initrd
> arm_root.img -serial "/dev/ttyS0" -display sdl
On 25 March 2015 at 11:08, Marcin Krzemiński wrote:
> I want to start u-boot ( or any other bear metal program ) from flash in
> versatilepb board. I am usung a command:
>
> qemu-system-arm -M versatilepb -m 128M -serial stdio -pflash flash.bin
> -display none -monitor null
>
> No mateher what is
On 26 March 2015 at 19:01, Patrick wrote:
> Like bochs [3], QEMU emulates an x86 CPU.
This is true but somewhat incomplete -- we also emulate
many other guest CPU types including ARM, MIPS and PPC.
> The whole translation task thus consists of two parts: blocks of target code
> (TBs) being rewri
On 26 March 2015 at 20:44, Patrick wrote:
> Thank you for the response. This makes sense, but I am not seeing how the
> "cpu" or "machine" command-line arguments fit into the "flow." It appears
> that the "cpu" flag is changing the x86 microarchitecture that is being
> emulated. If the x86 code is
On 26 March 2015 at 21:24, Patrick wrote:
> "That affects the fine detail of exactly how we translate the guest code..."
>
> I see that the list of x86 cpus includes Nehalem, Westmere, Penryn, and many
> others. I was somewhat interested in what QEMU is doing differently when
> emulating, for exam
On 30 March 2015 at 08:24, benoit ROUSSELLE wrote:
> Dear All,
>
> i am running a debian8 amd64 machine and i would like to emulate an:
> armhf machine with kernel > 3.8 (docker testing)
>
> following this: https://gist.github.com/bdsatish/7476239
> i succeed to have a debian7 (3.2 kernel) working
On 1 April 2015 at 01:21, Michele Denber wrote:
> Could someone please help tell me what's going wrong here? Thiis is
> qemu-2.3.0-rc1on Solaris 10 Sparc 64.
I suspect what you may be running into is "nobody
tests QEMU on Solaris". Hopefully the bugs are minor...
> In particular I don't get the
On 22 April 2015 at 17:15, nibon7 wrote:
> Hi,
>
> Is it possible to accelerate 32bit VMs(armv7) with kvm on aarch64?
With QEMU 2.3 you should be able to run a 32-bit VM
on AArch64. Note that it will be ARMv8 32-bit, not ARMv7,
but the guest is unlikely to really care.
https://wiki.linaro.org/Co
On 6 May 2015 at 09:48, Nakul Vyas wrote:
> Hi everyone,
>
> I tried using a qemu-system-m68k (on raspbian) with test kernel of uCLinux
> but it hangs (I am attaching the screenshot of that ).
The first question is: does this work on an x86 Linux host?
That will rule out problems because you're r
1 - 100 of 815 matches
Mail list logo
