On 9 January 2018 at 20:41, Steven Seeger
wrote:
> I am working with a custom model powerpc board (750-based) and I am having an
> issue with icount (any shift value).
>
> First, upon the first execution of the rfi instruction, I get:
>
> qemu: fatal: Raised
On 21 December 2017 at 16:36, Thomas Schmiedl wrote:
> I try to emulate this Intel 64-bit app
> https://drive.google.com/open?id=0B-F25LE4in_xYjMwME1BODRpdFU (from
> http://xupnpd.org/) on 32-bit Intel hardware (Ubuntu 16.04.1 LTS) using
> qemu-x86_64 from git, version
On 17 December 2017 at 05:57, Adam Baxter wrote:
> Hi,
> I realise this isn't strictly a qemu issue but I can't find any reference
> to this kernel panic happening on real hardware (I can't currently get
> serial out working on my Pi, so I can't test there)
>
> When running
On 28 November 2017 at 02:21, Aimee Ukasick wrote:
> Hi. Newbie here. I am trying to access an Ubuntu image running in
> qemu-system-aarch64.
> aimeeu@aimeeu-7520:~/dev/QEMU-arm64$ cloud-localds my-seed.img my-user-data
> aimeeu@aimeeu-7520:~/dev/QEMU-arm64$
On 24 November 2017 at 07:21, jiang00gle wrote:
> The Qemu is really a good project and the android emulator is
> based on the Qemu. But the version of Qemu in android 4.0 is 0.10
> which has no Tci module.
>
> So, is there any mature solution to add the tci module in
On 23 November 2017 at 21:00, Alex Kashchenko wrote:
> Hi,
>
> I am trying to build qemu-s390x-user static binary to run a hello-world
> program cross-compiled with gcc-s390x-linux-gnu on linux_x86_64.
>
> I am building qemu with:
>
> ./configure --static --disable-werror
On 20 November 2017 at 05:30, 李阳 wrote:
> Since I want to trace the instruction statistics( instruction type and
> number) about specified process running on the simulated operating system,
> I can do the analysis of instruction type via the *struct TCGOpcode* in
> qemu
On 17 November 2017 at 13:52, Kurt Jordon
wrote:
> Does someone know how to use the machine type "raspi2" (qemu option "-M
> raspi2") to emulate Raspberry Pi 1?
>
> I tried
>
> qemu-system-arm -M raspi2 -append "root=/dev/mmcblk0p2 rootfstype=ext4
> rootwait"
On 7 November 2017 at 15:05, Taylor Holberton
wrote:
> Yesterday I wrote a simple boot sector that goes into an infinite loop. I
> produced a flat binary, with the text section starting at 0x00.
>
> The binary appeared to work when running this:
>
> qemu-system-aarch64
On 2 November 2017 at 13:44, poxyran wrote:
> I mean, the right question would be "how can I add the /dev/ttysomthing
> or /dev/ttyAMA0 to the QEMU guest image?"
If it has devices in /dev/ as static things in the filesystem,
the answer is mknod. If it doesn't then you're
On 1 November 2017 at 18:31, poxyran <poxyran...@gmail.com> wrote:
>
>
> On 11/1/2017 1:07 PM, Peter Maydell wrote:
>> On 1 November 2017 at 13:34, poxyran <poxyran...@gmail.com> wrote:
>>> Hi all!,
>>>
>>> I'm trying to emulate a firmware fr
On 1 November 2017 at 02:35, 李阳 wrote:
> Recently, I want to use QEMU to trace the instruction features of the
> specified binary.
>
> My host: X86
> Guest: ARMv8,
>
> I run the benchmark on the AArch64 Operating System in QEMU and I want to
> collect the instruction data
On 23 October 2017 at 07:52, Dennis Luehring wrote:
> using git version 2.14.1 under ubuntu 17.10
>
> howto from https://www.qemu.org/download/#source
>
> 1. git clone git://git.qemu.org/qemu.git
> 2. cd qemu
> 3. git submodule init
> 4. git submodule update --recursive
>
> 1.
On 14 October 2017 at 17:38, Philippe Mathieu-Daudé wrote:
>>> Hello, is it possible to run (or rebuild modifying build flags) QEMU
>>> without support for X11 window system integration?
>>
>> ./configure --disable-gtk --disable-sdl --disable-opengl
>
> Is there some interest in
On 13 October 2017 at 08:00, Gerd Hoffmann wrote:
> On Thu, 2017-10-12 at 16:25 -0400, hanji unit wrote:
>> Hello, is it possible to run (or rebuild modifying build flags) QEMU
>> without support for X11 window system integration?
>
> ./configure --disable-gtk --disable-sdl
On 6 October 2017 at 16:25, Hui Yie Teh wrote:
> Hi,
>
> I'm wondering what the default RAM size for the board LM3S6965evb is?
>
> I am trying to increase the size of the RAM using:
>
> *qemu-system-arm -no-reboot -nographic -M lm3s6965evb -m 512M -kernel
>
On 4 October 2017 at 00:20, Will Senn wrote:
> I thought maybe it was
> environmental, but I got the same errors on Linux Mint 18 with qemu 1.7,
> 2.0, and 2.14 as well as on FreeBSD with qemu 2.8.1, so I'm asking for help.
There is no QEMU 2.14 -- 2.10 is the most recent
On 4 October 2017 at 05:42, Dennis Luehring wrote:
> try Artyom Tarasenko's blog
> http://tyom.blogspot.de/2009/12/solaris-under-qemu-how-to.html
That's now 8 years old and very likely to be no longer accurate
about the current situation...
thanks
-- PMM
On 3 October 2017 at 11:50, Marco Aurélio Lopes Barbosa
wrote:
> if (ioctl(fd, RNDGETENTCNT, ) == -1)
> When I run this program with qemu-x86_64-static I got the error
>
> Unsupported ioctl: cmd=0x80045200
> ioctl failed
> I've patched qemu to forward the
On 15 September 2017 at 21:41, William Mahoney wrote:
> 3) Can of worms. The 5282 allows you to move the base address
> of the control registers, the start address of the SRAM, all
> sorts of things. The control registers are all offset from a
> default address when the
On 8 September 2017 at 21:32, William Mahoney wrote:
> "digic_load_rom()" knows the filename via an extern “bios_name” which is at
> “include/sysemu/sysemu.h” but really lives in “vl.c”. It is set based on
> “machine_ops” that comes from “qemu_get_machine_opts()” which in
On 8 September 2017 at 11:14, massimiliano cialdi
wrote:
> I believe that this goes beyond my skills. However, where could I start
> from? Can I copy/paste something from somewhere?
I'm afraid it's more complicated than copy-and-pasting.
Most of the floating
On 8 September 2017 at 10:26, massimiliano cialdi
wrote:
> is it planned to add FPU extension for M4 profile?
Not currently. I'd be happy to review the code if somebody else
wrote it, but I'm not aware of anybody with plans to write it
right now.
thanks
-- PMM
On 8 September 2017 at 09:43, massimiliano cialdi
wrote:
> M4F has FPU option implemented.
>
> I use floating point instuctions, so FPU has to be emulated by qemu. Surfing
> in qemu source code it seems to me that the FPU extensions are not
> implemented for
On 1 September 2017 at 18:33, Arnabjyoti Kalita
wrote:
> 1. I start QEMU with *-enable-kvm* option. I then run a workload(a program
> from Spec2006) on QEMU.
> 2. Immediately after I start running the workload, I open the QEMU monitor
> and using "SAVEVM" command I save
On 31 August 2017 at 11:34, Mahmood via Qemu-devel
wrote:
> Hello again,
> For the command
>
> mount -t 9p -o trans=virtio Downloads /media/Downloads
>
> inside the Centos-7 guest, I get this error
>
> mount: unknown filesystem type '9p'
>
> Any thought?
That's an
On 30 August 2017 at 12:38, Mahmood wrote:
> Hello again,I installed 2.5.0 quickly and it was pretty straight forward!
>
> Here is the error message I get regarding the 'virtio-9p-pci'
> 'virtio-9p-pci' is not a valid device model name
Are you building your own QEMU binary
On 28 August 2017 at 18:28, Thomas Huth wrote:
> On 28.08.2017 13:56, Mahmood wrote:
>> Hi,I have installed a Centos 7 minimal installation with the following
>> command
>> qemu-system-x86_64 -m 4000 -smp 2 -hda centos7ser.img -boot c -usbdevice
>> tablet -enable-kvm -device
On 14 August 2017 at 07:26, Sam wrote:
> Hi all,
>
> I add some log like this in QEMU_SRC/hw/i386/pc.c
>
> +++ b/hw/i386/pc.c
>>
>> @@ -1364,6 +1364,13 @@ void pc_memory_init(PCMachineState *pcms,
>>
>>
>>> linux_boot = (machine->kernel_filename != NULL);
>>
>>
>>> +
On 23 July 2017 at 18:22, tukozaki wrote:
> I tried launching the Qemu vm without kvm:
>
> $ qemu-system-i386 -cpu pentium3,check
>
> was slow as it should, but the same applications requiring sse2 still
> did run (with some patience).
>
> So I can't
On 11 July 2017 at 00:15, Nguyen, Theresa X wrote:
> Dear Sir/Madame,
>
> I have an opportunity to download the Quick Emulator (QEMU)
> V2.9.0.
>
> There is one file located at:
>
>
>
On 12 June 2017 at 16:58, Vincent wrote:
> Hi !
> I'm trying to test a bare metal aarch64 OS using qemu 'virt' machine.
> So far I'm only running the EL3 part of the OS.
> I am using the following command line to start qemu:
>
> qemu-system-aarch64 -machine virt,secure=on
On 14 April 2017 at 08:31, Zhangwen (Esan) wrote:
> Hi,
> When I run a binary with qemu-2.7.1, I found it report a error:
> Program received signal SIGILL, Illegal instruction.
> Then I gdb it, the scene is as follows:
> (gdb) si
>
> Program received signal
On 14 March 2017 at 17:47, Wu, Michael Y [US] (MS) wrote:
> I am trying to compile qemu 2.8 on solaris 10 (ultrasparc).
>
>
>
> The most success I’ve had with compiling is using the configure command
> below:
>
> ../qemu/configure --cc=/usr/local/gcc-4.2.1/gcc/bin/gcc
>
On 1 March 2017 at 17:36, Brett Neumeier wrote:
> Hi,
>
> I'm trying to test out an x32-ABI userspace. When I boot the actual computer
> using the target filesystem as the rootfs, it works fine; when I boot it
> using qemu-system-x86_64 (version 2.8.0), I get a kernel panic
On 28 February 2017 at 22:13, Zach Riggle wrote:
> Is there any mechanism that can be used to read TTBR0 from the QEMU Monitor,
> or from the GDB Stub?
Not at the moment, no.
thanks
-- PMM
On 20 February 2017 at 23:21, Herb Peyerl wrote:
> Thanks for the explanation. I was away for the weekend so I’m back digging
> into this now. I think I understand better now.
>
> Based on your explanation, this seems to do something though I’m not quite
> sure if it’s the
On 17 February 2017 at 16:49, Herb Peyerl <hpey...@beer.org> wrote:
>> On Feb 17, 2017, at 9:36 AM, Peter Maydell <peter.mayd...@linaro.org> wrote:
>>>> qemu-system-aarch64: Option ‘-device myfoo’ cannot be handled by this
>>>> machine
>>
>>
On 5 February 2017 at 14:27, Hrishikesh Murukkathampoondi
wrote:
> * a flash device at 0x0
> * RAM starting at 0x4000
You can also get away with hardcoding the UART being at
0x0900 (since UEFI hardcodes that too).
> He mentioned that all other values like -machine
On 7 February 2017 at 15:26, Thomas Huth wrote:
> On 07.02.2017 11:06, James Hanley wrote:
>> Why the new domain?
>
> It's not new, it's the official domain of the QEMU project.
Yes, we've always had both domains in parallel. The recent
change is that qemu.org now redirects to
On 6 February 2017 at 17:27, Vincenzo Romano
wrote:
> I am using qemu-2.8.0 on a Ubuntu server 16.04.1 (x86_64).
> For a VM I am already using "-device virtio-net-pci" for its ethernets.
>
> I was willing to test also "-device virtio-net-device" but I get the error:
>
On 6 February 2017 at 11:45, Hrishikesh Murukkathampoondi
wrote:
> dtc gives me this error when trying to convert the blob to dts.
>
> Zeppelin:arm hrishi$ dtc/dtc virt.dtb -I dtb -o virt.dts -I dts
> Error: virt.dtb:1.1-2 syntax error
> FATAL ERROR: Unable to parse input tree
On 12 January 2017 at 05:50, 韩雨哲 wrote:
> Thanks for your reply!
> I have found that qemu uses tcg to translate target code.
> Now my problem is that I only want to fuzz test the syscalls to cover logic
> and process in the driver code, but I don't care what the device returns
On 11 January 2017 at 12:55, 韩雨哲 wrote:
> Hi,all:
> I am trying to test the device driver and related syscalls in arm64
> qemu.There are some problems:
>
> 1.The kernel cannot run when I set "machine" to "virt" and load my own dtb
> file.
Why do you want to do that? Generally
On 7 January 2017 at 08:29, Kevin Wilson wrote:
> Hi,
>
> I try to build qemu on x86_64 platform from source with qemu-2.2.0
> from the official website, http://wiki.qemu.org/download/
> I ran "./configure" and make.
Why are you trying to build such an old version? The
current
On 22 December 2016 at 14:01, r0ller wrote:
> As mentioned in the subject, I'm trying to get qemu-i386 (from qemu-2.7.0)
> user space emulation working on an amd64 NetBSD (7.0). Unfortunately, even
> giving a try to a 32bit binary printing "hello world" gives a segfault.
>
On 7 December 2016 at 20:31, James Hanley wrote:
> Seems like I spoke too soon. Removed the DTB option and started down the
> road of building up our board as a test and connect gdb to the target with
> the --gdb option.
> Using host libthread_db library
On 5 December 2016 at 17:31, James Hanley wrote:
> It seems after upgrading to tip that it exits gracefully with
> qemu-system-arm: qemu_fdt_getprop: Couldn't get //#address-cells:
> FDT_ERR_NOTFOUND
That suggests that your device tree is malformed (the root node
is missing
On 4 November 2016 at 16:44, Brooke Wallace wrote:
> Sure, any update or link to your blog on bringing up the "virt" image your
> talking about?
I sent the link out last night, but here it is again in case
that mail didn't get through to you:
On 4 November 2016 at 05:09, Tu Do 2 wrote:
> Hi list,
>
> I'm doing some LAPIC programing.
>
> According to Intel's document, FEE0 H to FEE0 03F0H is the range of
> local APIC. However, examining it from QEMU console, I can only find the
> value 0 there:
>
> (qemu)
On 3 November 2016 at 23:59, Brooke Wallace wrote:
> Pretty sure I have the correct cross compile tool chain,
> and its a simple main program to just return a value -
> no libs required - well thats not entirely true - it
> has all that std c/gnu garbage.
>
> Still, I did
On 3 November 2016 at 22:48, Brooke Wallace wrote:
> Thanks again Peter,
>
> Is there anyway to mount an -initrd image to the host?
You can't directly mount it, because it's not a filesystem.
But there are tools for manipulating initrd images:
something like
On 3 November 2016 at 19:42, Peter Maydell <peter.mayd...@linaro.org> wrote:
> On 3 November 2016 at 18:56, Brooke Wallace <bwall...@ramlabs.com> wrote:
>> Thanks for the sympathy Peter. Unfortunately the lack of documentation
>> and reasonable introductory guide i
On 3 November 2016 at 18:56, Brooke Wallace wrote:
> Thanks for the sympathy Peter. Unfortunately the lack of documentation
> and reasonable introductory guide is making this a non-starter for us.
Yeah, I was surprised there wasn't a decent guide to getting
the 'virt' board
On 2 November 2016 at 20:03, Brooke Wallace wrote:
> I'm new to QEMU and was able to pull the latest stable version and build it.
> I downloaded a simple test arm image that I found in one of the docs -
> arm-test-0.2.tar.gz and was able to run that w/o any problems.
On 26 October 2016 at 18:44, Utku Gültopu wrote:
> I would like to copy the article I have written in wikibooks [1] to
> main QEMU wiki. Could someone help me with account creation please?
>
> Regards
>
> [1]
>
On 7 October 2016 at 09:49, Jerry Stuckle wrote:
> This works fine, except the ethernet port (eth0) gets an ip address of
> 10.0.2.15 instead of one from our intranet and can't access anything on
> the intranet or the internet. (The interface is defined in Debian for
>
On 1 October 2016 at 01:06, Amogh Mannekote wrote:
> I'm trying to run Pint OS on QEMU, and the qemu command gets executed from a
> Perl file. At this point., it refuses to take ANY command line options
> whatsoever by displaying the error:
> qemu: unknown option ''
>
> The
On 26 September 2016 at 08:59, Максим Скопич wrote:
> Dear all,
>
> I run qemu with trust zone emulation. 64 bit Linux is run in Normal world
> (NWD) EL1 and some proprietary code are run in EL3 and Secure World (SWD)
> EL1. Also i have such configuration for interrupts: 1)
On 8 September 2016 at 10:29, Dennis Luehring wrote:
> small tests show that this seem not to be a kernel or gcc bug (same problem
> with linux 4.5,4.6.4,4,7, gcc 5.2,5.3,6.1)
That doesn't show that it's not a kernel bug -- it just shows
that if it is a kernel bug it's been
On 26 August 2016 at 10:02, wrote:
> Hi
> I'm trying to run a simple hello world with
> qemu-system-tricore -machine tricore_testboard -cpu tc27x -nographic -kernel
> Test.elf
> The program is compiled with tricore-gcc (HighTec) for ROM target. The
> adress range for the code is
On 24 August 2016 at 07:10, Soramichi AKIYAMA wrote:
> I am currently using the user-mode (not system-mode) of QEMU
> for performance analysis of multi-threaded programs.
>
> Although there are several discussions about SMP for the system-mode,
> I cannot find a thorough
On 16 August 2016 at 18:41, Nerijus Baliūnas
<neri...@users.sourceforge.net> wrote:
> 2016-08-16 20:26, Peter Maydell rašė:
>>>
>>> Yes, it still hangs:
>>>
>>> # gdb /usr/bin/qemu-system-alpha
>>> (gdb) r -S -no-user-config -nodefaults
On 16 August 2016 at 17:50, Nerijus Baliūnas
wrote:
> I tried to debug with gdb:
>
> # gdb /usr/bin/qemu-system-alpha
> Reading symbols from /usr/bin/qemu-system-alpha...Reading symbols from
> /usr/lib/debug/usr/bin/qemu-system-alpha.debug...done.
> done.
> (gdb) r
On 5 August 2016 at 19:50, Nutaro, James J. wrote:
> I've found a handful of posts mentioning this problem,
> but no solutions yet. The command line that I'm trying to run with is
>
> qemu-system-i386 --enable-kvm disk.img
>
> If I remove the --enable-kvm it runs fine.
(CCing qemu-devel, which is more likely to get developer attention)
On 18 July 2016 at 15:45, Maxim Ostapenko wrote:
> 1) AddressSanitizer mmaps quite large regions of memory for redzones and
> shadow gap. In particular, for 39-bit AS it mmapes:
>
> || `[0x14,
On 16 July 2016 at 23:38, Federico Vaga wrote:
> I'm super new to qemu and I would like to understand more about the hardware
> components emulation. I surfed for some hours on the internet but I cannot
> find much help.
> By looking at the source code in the 'hw'
On 4 July 2016 at 15:04, wrote:
> I am using QEMU 2.5.0 with a 4 core set up and was expecting that the load
> of the system would be minimal, as none of the 4 core cpus are really doing
> anything. Each is awating a core specific timer interrupt, writes a few
> characters
On 7 June 2016 at 15:47, Jérôme Forissier wrote:
> Hi,
>
> I just noticed this error [1] (QEMU master branch):
>
> ../qemu/arm-softmmu/qemu-system-arm -nographic -monitor none -machine
> virt -machine secure=on -cpu cortex-a15 -m 1057 -serial stdio -serial
>
On 13 May 2016 at 17:24, Jerome Ibanes wrote:
> I'm running qemu-arm version 2.1.2 (Debian 1:2.1+dfsg-12+deb8u6); and
> trying to start the Wolfram Engine (retrieved from raspbian); and get
> the following:
2.1.2 is now a pretty old release, so the first thing to do is
try a
On 22 April 2016 at 15:27, Ashkan Taslimi wrote:
> When I am running the tests on qemu there is a lot of delay at this stage:
>
> adt-run [16:15:06]: test command2: preparing
> qemu: terminating on signal 15 from pid 20216
I'm not sure what adt-run is, but it's not part
On 18 April 2016 at 20:17, Ran Shalit wrote:
> I probably have some misunderstanding with running qemu.
> I see in the following link:
> http://www.osadl.org/Use-BuildRoot-to-create-a-Linux-image-fo.buildroot-qemu.0.html
> that qemu should be run as following:
>
>
On 3 April 2016 at 17:16, Predrag Ivanovic wrote:
> Hi.
>
> I tried to build qemu-2.6.0-rc0 from http://wiki.qemu-project.org/download
> tarball and the
> one I generated from git master (HEAD is
> de1d099a448beb2ec39af4bd9ce4dd6452a18cb5)
> using
> --
> scripts/make-release
On 27 March 2016 at 11:03, Pat wrote:
> Hello,
>
> This is a repost from UNIX StackExchange, I figured many people here
> probably don't follow qemu questions there..
>
> I am running Qemu under a host with two bridge interfaces and would simply
> like to bridge them to guest
On 15 March 2016 at 20:38, Jim Jones wrote:
> is QEMU capable of emulating an OMAP5 SoC?
No, it isn't; sorry.
thanks
-- PMM
On 12 March 2016 at 10:06, bilsch wrote:
> BIOS is SeaBIOS (version 1.7.4-20150827-223240-lgw01-56)
> any more than that I don't know. I don't know how to make QEMU tell me
> anything more. If it does INT 13 extensions then it should do int13/ah=48.
> But it's not doing
On 1 March 2016 at 13:00, Jakob Bohm wrote:
> As an alternative, could it be useful to look beyond the current
> glibc code and see if there is a way for qemu-user to provide the
> full set of Linux syscall provided facilities (including signals
> and calls), without
On 15 February 2016 at 10:04, Yehuda Yitschak wrote:
> From what I can gather it looks like QEMU is not generating a screen for the
> guest to work with. I understood that QEMU uses SDL to start a screen for
> the guest but I suspect that doesn’t happen for some reason. Also
On 11 February 2016 at 05:11, Ren Kimura wrote:
> I have a question about activation of kvm.
>
> Is there any way to enable/disable kvm at qemu runtime?
Yes, the command line is -enable-kvm. (We default to not using KVM.)
> It should be useful for sandbox tools like DECAF
On 28 January 2016 at 16:35, Nathan Sowatskey wrote:
> What I would like is to have a DHCP assigned address for the VM so that I can
> reach it from the host. I have tried the startup options below:
>
> /usr/local/bin/qemu-system-x86_64 -kernel images/bzImage-qemux86-64.bin
On 14 January 2016 at 13:50, Franz-Josef Haider
wrote:
> This would be a unstripped version of the qemu-i386 binary:
> https://www.dropbox.com/s/s9f8pcn5co34khn/qemu-i386?dl=0, although i think
> it is not worth trying to pursue this any further, because i
On 4 January 2016 at 13:24, Jakob Bohm wrote:
> For your information, the x86 memory model only requires
> barriers in the following cases (this is somewhat
> implemented on modern machines with multiple actual x86
> CPU sockets, as opposed to multicore chips, it may also
On 3 January 2016 at 20:57, David Durham wrote:
> Any suggestions or comments on how to do this are very welcome
> ... I built qemu with --target-list i386-softmmu and when I run
> qemu, top only shows one qemu-system-i386 using 100% of one core
This is expected. Our current
On 22 December 2015 at 20:22, Ilya Katsnelson wrote:
> Thanks, Peter.
> My final HW platform is an ALTERA's Arria10 FPGA which has 2
> ARM cores. So it would be useful to simulate them correctly.
> But I'll take one core if that's the only thing available.
> However, QEMU
On 21 December 2015 at 18:40, Ilya Katsnelson wrote:
> Does anyone have experience running ARM Dual-core (in particular) Cortexa9
> simulation? Can you share the exact parameters that should be used?
Why do you want to run dual-core? At the moment it will just
give worse
On 18 December 2015 at 19:03, Franz-Josef Haider
wrote:
> Hi, i don't know why it locked up previously with a fresh clone it does not
> lock up anymore, but it still crashes with current master.
Hmm. Unfortunately since I haven't been able to reproduce
any
On 5 December 2015 at 16:04, Wink Saville wrote:
> Thanks Peter, is there any documentation for any configuration?
No. In theory it should look like the hardware; in practice
some devices are missing (usually the missing ones fall into
two categories: (a) "Linux doesn't care
On 24 November 2015 at 10:19, Franz-Josef Haider
<franz-josef.hai...@student.uibk.ac.at> wrote:
> On 11/24/2015 10:08 AM, Peter Maydell wrote:
>> OK, that's definitely not the problem I thought it might have been.
>> Can you run maple under qemu, adding
>>-D qemu.lo
On 26 November 2015 at 17:33, Abhinav Sharma wrote:
> Hi,
> What does Qemu do when invoked using "-cpu host" option that sets target CPU
> same as the host CPU?
>
> Is it that when this option is used Qemu performs no binary translation?
> Because the target CPU is same as
On 24 November 2015 at 07:28, Franz-Josef Haider
<franz-josef.hai...@student.uibk.ac.at> wrote:
> On 11/23/2015 10:51 PM, Peter Maydell wrote:
> (gdb) run cmaple
> Starting program: /usr/bin/qemu-i386 cmaple
>
> Program received signal SIGSEGV, Segmentation fault.
> 0x
On 23 November 2015 at 17:50, Franz-Josef Haider
wrote:
> But this is a backtrace from directly launching cmaple.
> # qemu configure line: ./configure --prefix=/usr --static
> --target-list=i386-linux-user
>
>
On 18 November 2015 at 13:44, Fernando Endo wrote:
> I have a question regarding qemu-system-aarch64 running in a x86 host. I'd
> like to boot an aarch64 Linux kernel (guest) that emulates the kvm support.
> qemu succesfully boots Ubuntu, but I see the following kernel
On 5 November 2015 at 21:25, Jerry Stuckle wrote:
> I'm having trouble trying to emulate an Olimex A10-OlinuXino-Lime
> (https://www.olimex.com/Products/OLinuXino/A10/A10-OLinuXino-LIME/open-source-hardware).
QEMU doesn't have a model of this hardware.
> To do so, I
On 21 October 2015 at 14:41, Bilal Arif wrote:
> mr@mr:~/qemu-2.4.0.1$ ./configure
>
> ERROR: "cc" either does not exist or does not work
This is trying to tell you that you need to install
some development tools; in this case, the C compiler.
It's a problem with the
On 19 October 2015 at 20:30, Wink Saville wrote:
> I would like to use qemu in a test environment where I give a "kernel" image
> to qmeu have it execute it and then when complete have qemu exit. Currently
> when
> executing:
>
> $ qemu-system-arm -M versatilepb -m 128M
On 13 October 2015 at 13:00, Muhammad Asif wrote:
> Hi Geeks,
>
> We intend to use KVM with libvmi for VM introspection. libvmi provide a
> patch to get this functionality with KVM.
> I downloaded qemu-kvm-0.14.0/ and patch it respectively and them try to
> compile as
(looping in qemu-devel and Paolo)
On 2 October 2015 at 17:54, Sair, Umair wrote:
> I am working with qemu-2.4.0. I built it using mingw on Windows. I am having
> a problem while connecting it to gdb. I figured out that qemu gdb server is
> running on IPv6 whereas gdb tries
On 2 October 2015 at 19:20, Sair, Umair wrote:
> If I am understanding correct, you are saying that we should set
> addr->has_ipv6 and addr->has_ipv4 to true in any case, then in my opinion we
> should simply ignore the value of addr->has_ipv* while evaluating the value
On 25 September 2015 at 12:48, Willard Dennis wrote:
> Hi all,
>
> Using the CentOS 7 package of QEMU 2.0.0 ( package name =
> qemu-system-x86-2.0.0-1.el7.5.x86_64 ) and it's generally working fine.
> However, when I tried to use it with GNS3 (networking device emulation
On 22 September 2015 at 08:30, Maciej Bielski wrote:
> Hi,
>
> I am using qemu-system-arm for ARM emulation. I have found that an
> interrupt may be sent by qemu_set_irq(), with all device configuration
> done inside fdt. But then, the only result is that a cpu flag is set:
>
501 - 600 of 680 matches
Mail list logo