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 https://access.redhat.com/solutions/24
On 3 November 2016 at 19:42, Peter Maydell wrote:
> 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 sur
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 working; I've spent th
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.
Firstly, sorry that this has
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]
> https://en.wikibooks.org/wiki/QEMU/QEMU_Hello_World:_Installing_QEMU_and_getting_it_up
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
> DHCP on eth0).
In what way
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 list of options I'm try
On 27 September 2016 at 02:59, Максим Скопич wrote:
> Good day,
> I am using qemu from head of
> https://git.linaro.org/virtualization/qemu-tz.git, armv8tz branch.
Don't do that, that code is an out of date development branch.
Use QEMU mainline 2.7.0 or better.
> Unfortunately I haven't snippet
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) FIQ is assigned for
> S
On 8 September 2016 at 13:32, Donald R Laster Jr wrote:
> Stephen,
>
> When building the various software packages use the following configuration
> --prefix like this:
>
> --prefix=/opt/qemu/qemu-${VARIANT}
If you're just doing local testing (where running QEMU
from the command line is
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 around since at least
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 0x8000.
> Unf
On 25 August 2016 at 18:33, Parfait Tokponnon
wrote:
> Hello
>
> I read from here that vmx capability support on quemu must be explicitely
> enable by providing +vmx option to the command but the probllem is that it
> does not seem to work. In my system, VMX feature is still undetected.
>
> Comman
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 documentation about SMP fo
On 16 August 2016 at 19:45, Nerijus Baliūnas
wrote:
> 2016-08-16 21:21, Nerijus Baliūnas rašė:
>>
>> I've tried gdb without daemonize on a working PC and got the same
>> backtrace. So it seems it is daemonize code which has a problem.
>
>
> Debugging the child revealed the problem:
> #11 0x7f
On 16 August 2016 at 18:41, Nerijus Baliūnas
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 -nographic -M none -qmp
>>> un
On 16 August 2016 at 18:13, Nerijus Baliūnas
wrote:
> 2016-08-16 19:58, Peter Maydell rašė:
>>
>> This is the outer process waiting for the child process to tell
>> it it's got started in os_daemonize().
>>
>> Does QEMU still hang if you don't pass it -d
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 -S -no-user-config -nodefaults -
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. Otherwise,
> I get a blank s
On 19 July 2016 at 10:22, Maxim Ostapenko wrote:
> On 18/07/16 18:51, Peter Maydell wrote:
>> Well, we do need to do some things:
>> * we're populating the PageDesc data structure which we later use
>> to cache generated code
>> * if we're marking
(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, 0x1f]` || HighShadow
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' directory of the qemu git reposit
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 to the QEMU screen, and
On 8 June 2016 at 07:23, Jérôme Forissier wrote:
>
>
> On 06/08/2016 04:30 AM, xiaoqiang zhao wrote:
>> commit f0d1d2c115dffc1fbaf954d0b449db05c5eb79b1
>> ("hw/char: QOM'ify pl011 model") break qemu-system-arm virt machine
>> if option '-machine secure=on' is provided.
>>
>> The function create_ua
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
> file:serial1.log -bios
> /home/travis/o
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 newer QEMU, like 2.6
On 2 May 2016 at 11:50, Anand Umarji wrote:
> Thanks Peter for the info. To open a file with semihosting what is the
> option. Can you provide me an example it will be helpful.
(Assuming ARM semihosting) the guest passes a filename to the
semihosting open syscall, or it passes ":tt" as a magic st
On 2 May 2016 at 05:39, Anand Umarji wrote:
> I am trying to use semihosting option to capture the output logs
> into a log file.
> But i am not able to find the option to provide a log file for
> capturing .
There isn't one. The semihosting ABI allows the guest to either
(a) open a file (it choo
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 of QEMU's test framework.
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:
>
> KERNEL="bzImage"
> DISK="rootfs.i
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 /~/repos/qemu/qemu 2
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 NICs. All of this wor
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 that.
SeaBIOS source cod
On 4 March 2016 at 05:14, Jakob Bohm wrote:
> There are lots of possibilities once you don't treat glibc as a
> black box,
If you don't treat glibc as a black box then you become
very vulnerable to being broken when details of its
implementation change. (Also it means you may no longer
work with
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 having to reserve some for its
On 1 March 2016 at 09:38, Hunter Laux wrote:
> I was having trouble running golang on linux-user with an aarch64 target.
>
> It turns out that snappy is written in Go. When I tried the xenial aarch64
> preinstall image in qemu, Snappy was broken.
>
> For some reason, it calls sigaction on all the
On 15 February 2016 at 15:07, Alexander Spyridakis
wrote:
> For that model you need a kernel with the HDLCD driver (PL111)
The HDLCD and PL111 are two totally different framebuffer devices.
HDLCD supports HD resolution, as the name suggests; PL111 is the
older and simpler device. (There's no QEMU
On 15 February 2016 at 11:10, Yehuda Yitschak wrote:
> That makes sense however I need graphics for demo purposes.
> How can I overcome this limitation ? should I re-build QEMU with
> a different configuration, or is this limitation built-in in the
> QEMU code ?
In theory you can add an emulated
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 the fact
> that the Qe
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 or TEMU,
> because some
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 -usb
> -netdev user,i
On 22 January 2016 at 07:00, Daniele Colombo wrote:
> Hi all,
> Is Cortex-A5 cpu supported by qemu ? I'm looking for an emulator of SAMA5D3
> SoC.
We don't emulate the Cortex-A5, but more importantly for you
we don't emulate the SAMA5D3 SoC. Implementing the SoC and its
peripherals is much more w
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 have updated
> GCC in my build chroot (sc
On 10 January 2016 at 13:07, Meng Xu wrote:
> Hi All,
>
> I am using the ivshmem device to create shared memory between an x86_64 host
> and aarch64 guest.
> The guest has ubuntu server 14.04 installed with kernel version 3.13.0. I
> wrote a kernel driver to
> drive the ivshmem device (as a pci
On 6 January 2016 at 04:55, Ilya Katsnelson wrote:
> I'm trying to test my ARM build on QEMU from Yocto script.
>
> The command line is this:
>
>
> runqemu qemuarm qemuparams="-D /tmp/a.log -smp cpus=1 -nographic -serial
> mon:stdio -append 'console=ttyS0'"
> ./tmp/deploy/images/vcm4-qemu/zImage-v
On 5 January 2016 at 23:10, Jakob Bohm wrote:
> On 05/01/2016 18:35, Peter Maydell wrote:
>> (It would also be possible
>> to use the v8 ARM load-acquire and store-release instructions
>> rather than full on barriers, but on v7 I think barriers are
>> the only answe
On 4 January 2016 at 22:00, Jakob Bohm wrote:
> On 04/01/2016 22:29, Peter Maydell wrote:
>>
>> On 4 January 2016 at 13:24, Jakob Bohm wrote:
>> https://en.wikipedia.org/wiki/Memory_ordering#In_symmetric_multiprocessing_.28SMP.29_microprocessor_systems
>> lists several
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
> be observed when using
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 emulation is single t
On 24 December 2015 at 01:00, Programmingkid wrote:
> I'm having problems with the pci_dma_read() function. When using
> a Mac OS X guest, the data that this function returns is all zeros.
> After doing a lot of instruction tracing, I tracked the problem to a
> function called phys_page_find(). It
On 22 December 2015 at 21:37, Franz-Josef Haider
wrote:
> https://www.dropbox.com/s/vh2efuulpk89s23/sarge.tar.gz?dl=0
>
> This is a sarge installation. Executing apt-get update triggers the crash
> for me. I understand that the commit i referenced earlier is probably not
> the root cause, but i ve
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 has multicore parameters.
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 performance than running
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 of these crashes or lockups I'm getting
On 18 December 2015 at 14:43, Dale R. Worley wrote:
> There probably is an error in the qemu-options.texi file, as indicated
> by the error messages.
>
> Unfortunately, the makefile that controls "make" is preventing the
> commands from showing, so you don't see the exact command that is
> finding
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 about this" and
(b) "
On 4 December 2015 at 19:32, Wink Saville wrote:
> How can I determine what is actually implemented for a particular "machine"
> such as VersatilePB for qemu-system-arm. The actual VersatilePB uses an
> ARM926EJ-S cpu, but what happens to the peripherals and memory map when I
> change the cpu to A
On 27 November 2015 at 14:31, Peter Maydell wrote:
> On 24 November 2015 at 10:19, Franz-Josef Haider
> 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
On 24 November 2015 at 10:19, Franz-Josef Haider
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.log -d in_asm,out_asm,op,exec,int,cpu,gu
On 26 November 2015 at 17:46, Abhinav Sharma wrote:
> Sorry, I should have mentioned this earlier.
> I'm running it on x86_64 architecture, and I'm using -enable-kvm .
> So in this case, does Qemu binary translate even when "-cpu host" is used?
-cpu host doesn't affect the choice of whether we do
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 host CPU, code compiled
On 23 November 2015 at 21:20, Jerry Stuckle wrote:
> Peter,
> On 11/5/2015 5:31 PM, Peter Maydell wrote:
>> 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/P
On 24 November 2015 at 07:28, Franz-Josef Haider
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.
> 0x600104c0 in ?? ()
> (gdb) info thre
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
>
> [1|user@Nokia-N900|~/MyDocs/maple13_i386/bin.IBM_INTEL_LINUX]LD_LIBRARY_PATH=/home/user/
On 18 November 2015 at 16:33, Franz-Josef Haider
wrote:
> sure, apt-get:
>
> root@Nokia-N900:/# gdb apt-get qemu_apt-get_20151118-120024_16081.core
> GNU gdb 6.3-debian
> Copyright 2004 Free Software Foundation, Inc.
> GDB is free software, covered by the GNU General Public License, and you are
>
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 message:
> [2.710572] k
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 downloaded the Ubuntu trusty
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 machine you're running the
c
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 -nographic -kernel test.b
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 following link.
> https://git
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
> of ipv4 and ipv6 varia
(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 to connect on IPv4. Thi
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
> package) with a certain
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:
>
> cpu->tcg_exit_req =
On 17 September 2015 at 21:48, Scott Dattalo wrote:
> You're correct: the version in /usr/bin was taking precedence over the one
> in /usr/local/bin. I should've caught that... The nochain option is indeed
> enabled with the patch.
>
> Unfortunately, I must be missing something else. Here's how I
On 17 September 2015 at 19:50, Scott Dattalo wrote:
>
>
> On 9/17/2015 1:37 AM, Peter Maydell wrote:
>>
>>
>> Patch on list now, from Richard Henderson:
>> http://patchwork.ozlabs.org/patch/518643/
> Thanks Peter. How do you enable the 'nochain' f
On 15 September 2015 at 20:30, Peter Maydell wrote:
> The optimisation that is tripping you up is that we chain TBs together,
> which means we will run a long chain of TBs and only print the 'exec'
> trace for the first one. (The exec tracing in current git master
> will
On 16 September 2015 at 04:30, Dale R. Worley wrote:
> Peter Maydell writes:
>>> I have an ISO fromat via dd from an old scsi unix:
>>> //
>>> dd if=/dev/hdc of=./all_files.iso
>>> I think it's sysv unix. How can I detedct it
On 15 September 2015 at 21:51, Scott Dattalo wrote:
>
>
> On 9/15/2015 12:30 PM, Peter Maydell wrote:
>>
>> On 15 September 2015 at 19:38, Scott Dattalo
>> wrote:
>>>
>>> Question: how can you tell QEmu to create an instruction trace?
>>
&
On 15 September 2015 at 19:38, Scott Dattalo wrote:
> The answer provided doesn't work (at least with the latest QEmu in git).
> Specifically, it appears that once a TB has been cached there is no way to
> trace instruction execution. Similar to Manu, I invoke QEmu with '-D
> trace.log -d in_asm,c
On 15 September 2015 at 12:47, Mohsen Pahlevanzadeh
wrote:
> Dear All,
>
> I have an ISO fromat via dd from an old scsi unix:
> //
> dd if=/dev/hdc of=./all_files.iso
> //
> I have the following information from my iso:
>
On 14 September 2015 at 15:44, Jakob Bohm wrote:
> On 14/09/2015 11:33, Peter Maydell wrote:
>> Rather than reinventing the wheel I suggest looking at how QEMU
>> already supports file-backed ROMs for other platforms...
>
> Note that this is about *writable* persistent memo
On 14 September 2015 at 00:25, Programmingkid wrote:
>
> On Sep 13, 2015, at 7:20 PM, Bodo Eggert wrote:
>
>> On Sun, 13 Sep 2015, Programmingkid wrote:
>>> On Sep 13, 2015, at 5:50 PM, Bodo Eggert wrote:
On Sun, 13 Sep 2015, Mark Cave-Ayland wrote:
> On 11/09/15 19:01, Programmingkid wro
On 9 September 2015 at 07:59, Zheng, Di wrote:
> Compile qemu.git failed on RHEL6 while succeed on RHEL7.
> GEN x86_64-softmmu/config-devices.mak
>
> GEN config-all-devices.mak
>
> Traceback (most recent call last):
>
> File "/root/cathy/qemu.git/scripts/qapi-visit.py", line 467, in
>
>
On 23 August 2015 at 01:09, Ken Moffat wrote:
> Is this the right place to ask about what seems to be a fairly
> catastrophic bug (host machine running recent x86_64 linux and
> 4.2-rc kernels locks up with 2.4.0 when qemu is running but
> seems fine with 2.3.0) or do I need to subscribe to a diff
On 21 August 2015 at 23:22, Programmingkid wrote:
> Do you think there is any hope for hypervisor support in Mac OS X
> for QEMU?
It's not impossible. But it would require somebody who:
* cares about it working
* is technically capable of implementing it
* is willing to stay around the project
On 19 August 2015 at 20:40, Programmingkid wrote:
>
> On Aug 19, 2015, at 3:25 PM, Peter Maydell wrote:
>
>> On 18 August 2015 at 14:12, Programmingkid wrote:
>>> Do you think this should be a Google Summer of Code project?
>>
>> I guess it's probably a s
On 18 August 2015 at 14:12, Programmingkid wrote:
> Do you think this should be a Google Summer of Code project?
I guess it's probably a size that would work for a GSoC
project with a suitably capable and enthusiastic student.
Are you asking because you would want to do it as a GSoC
project your
On 18 August 2015 at 01:51, Programmingkid wrote:
> If we did use Mac OS 10.10's hypervisor, I'm thinking that would
> mean everyone using Mac OS 10.9 and below would not be able to
> use it. Does implementing one ourselves that could work on
> Mac OS 10.5 and up sound possible?
Nope. That would
On 17 August 2015 at 06:17, Programmingkid wrote:
> Do you think it is possible to one day be able to run QEMU in
> KVM mode on a Mac OS X host? Would this task require a dedicated
> Google Summer of Code student or two to implement?
As of OSX Yosemite it looks like Apple have finally provided a
On 27 July 2015 at 01:10, Devendra Agarwal wrote:
> Do arm cpu emulator and arm dynamic translator work together?
The ARM CPU emulation *is* by dynamic translation. That's how it works...
> I do not have very good understanding but I am assuming that an arm cpu
> emulator should be able to execu
On 24 July 2015 at 16:54, Maciej Bielski wrote:
> Ok, I have found a solution. The process spawned was using SIGUSR1 to
> signal something to the parent process (device internals). It seems that
> QEMU uses SIGUSR1 internally because when I have switched to SIGUSR2 it
> works as expected.
Yes, we
On 21 July 2015 at 20:30, Jiaqi Liu wrote:
> I used the following command to execute some AArch64 instructions contained
> in test.bin:
> qemu-system-aarch64 -cpu cortex-a57 -M virt -m 128M -nographic -s -S -kernel
> test.bin
>
> But QEMU hanged up while executing floating point instructions.
>
>
On 20 July 2015 at 21:35, Jeremy Hansen wrote:
> New to Qemu and just trying to use the linux-0.2.img test image running on
> native sparc hardware:
>
> root@sparc1:/usr/local/src/qemu# /usr/local/bin/qemu-system-x86_64
> linux-0.2.img
> WARNING: Image format was not specified for 'linux-0.2.img
On 10 July 2015 at 21:57, Binh Pham wrote:
> Hi folks,
> I am working on a task that requires replicating the page table walk process
> in QEMU to a timing model, which is plugged in QEMU. In order to do so, I
> want to back guest RAM by a file on my host system, so that I can perform
> the walk o
On 4 July 2015 at 08:36, Morten W. Petersen wrote:
> I was wondering if it is possible to see what's going on, on machine code
> level using QEMU.
>
> For example, would it be possible to call some function or interrupt when
> running Linux inside QEMU X86 emulation mode and be able to peek throug
On 30 June 2015 at 17:05, web wrote:
> I am finding a way to connecting QEMU to a timing model of my CPU.
> All I need is find out a way to catch all instruction trace and the result
> of each instruction, and send them to a FIFO which connects to my timing
> model.
>
> Could anyone tell me where
On 18 June 2015 at 12:20, Venkateswara Rao Dokku wrote:
> error: Failed to create domain from NSVPX-KVM.xml
> error: internal error Process exited while reading console log output:
> libvir: error : cannot execute binary
> /root/ovdk/qemu/x86_64-softmmu/qemu-system-x86_64: Permission denied
This
On 5 June 2015 at 17:38, Igor R wrote:
> This particular set is quite recent, but IUUC, this is a continuation
> of a long series, which begins several months ago:
> http://lists.nongnu.org/archive/html/qemu-devel/2014-12/msg00805.html
> Is it all still not applied?
Correct -- it's a big feature
601 - 700 of 807 matches
Mail list logo
