On Fri, 8 Jul 2022 at 15:06, Fernando T. Reagan
wrote:
> I have a custom amd64 Docker image that is based on CentOS 7 and has a UNIX
> application installed in it.
> The amd64 Docker image and the application inside work without problems on an
> amd64 computer.
>
> However, when starting this
On Thu, 7 Jul 2022 at 20:54, Gregg Allison
wrote:
> We are considering the Gaisler GR712RC (2 core LEON3) and GR740 (4 core
> LEON4) SoCs for a new deep space mission.
>
> Does QEMU support these two multicore configurations at present? Is there
> an effort planned to provide multicore LEONx
On Mon, 27 Jun 2022 at 15:11, Patrice Blin wrote:
> If I compare the logs (real/emulated), I'm missing,
> - CPU features: detected: ARM errata 1165522, 1319367, or 1530923
>
> I'm guessing qemu doesn't implement erratas
These are usually printed based on the specific CPU model and
On Mon, 13 Jun 2022 at 16:18, Patrice Blin wrote:
>
> Hi,
>
> As of version 7.0.50 (v7.0.0-1647-g028f2361d0), cortex-a55 is not part of the
> available CPUs.
> I would like to know if support is on the horizon or should I rely on -cpu
> max ?
>
> While googling, I found this question was asked
On Mon, 30 May 2022 at 13:56, Thomas Huth wrote:
>
> On 26/05/2022 12.01, Narcis Garcia wrote:
> > Is it possible to specify an explicit DNS IP for a VM in user mode
> > networking?
> >
> > For example, host uses 1.2.3.4 as nameserver at /etc/resolv.conf
> > And I want a user mode VM makes
On Thu, 26 May 2022 at 11:37, Jiatong Shen wrote:
>
> Hi,
>
>I've tried to use qemu 7.0 and indeed "qemu-system-aarch64 -cpu host
> -enable-kvm -machine virt -m size=4G,maxmem=512G" works this time! I also
> tried qemu 6.2 but it doesn't work.
> we have some environments which unfortunately
On Thu, 26 May 2022 at 07:45, Jiatong Shen wrote:
>I am trying to run qemu-system-aarch64 on a Kylin based machine, the host
> kernel version is 4.19. qemu is versioned 4.2.1. The command I am running is
> "qemu-system-aarch64 -cpu host -enable-kvm -machine virt -m
> size=4G,maxmem=512G".
On Wed, 18 May 2022 at 10:14, Jiatong Shen wrote:
>
> Hello community,
>
> I am trying to get qemu uniting test coverage report. I find this
> https://www.qemu.org/docs/master/devel/testing.html#gcc-gcov-support link
> might be relevant. but when I execute make coverage-html.
>
> it
On Wed, 20 Apr 2022 at 11:04, asif siddiqui wrote:
>
> Hello Peter,
>
> Is there any expected date for QEMU 7.1 release.
QEMU releases are calendar-based: we have three a year:
x.0 is in April (7.0 just came out)
x.1 is in August
x.2 is in December
thanks
-- PMM
On Mon, 11 Apr 2022 at 15:49, Greg KH wrote:
>
> On Mon, Apr 11, 2022 at 03:32:23PM +0100, Peter Maydell wrote:
> > On Mon, 11 Apr 2022 at 15:22, Chan Kim wrote:
> > >
> > >
> > > > > > What bus type is your driver written for?
> > > >
On Mon, 11 Apr 2022 at 15:22, Chan Kim wrote:
>
>
> > > > What bus type is your driver written for?
> > > >
> > > That sounds very logical. In my case I added it to system bus.
> >
> > What exactly do you mean by "system bus"?
> >
> I meant 'sysbus' in qemu code that I showed in the qemu code.
>
On Mon, 11 Apr 2022 at 11:05, Avi Kivity wrote:
>
>
> On 11/04/2022 12.25, Peter Maydell wrote:
> > On Sun, 10 Apr 2022 at 21:03, Avi Kivity wrote:
> >> I'm using qemu to cross-build container images with docker. It works
> >> well, but aarch64 emulation is sl
On Sun, 10 Apr 2022 at 21:03, Avi Kivity wrote:
> I'm using qemu to cross-build container images with docker. It works
> well, but aarch64 emulation is slow, due to pointer authentication.
>
>
> The documentation refers to a pauth-impdef cpu feature to speed it up,
> but I could not find an
On Mon, 4 Apr 2022 at 14:29, Chan Kim wrote:
>
> Hello all,
>
> I have assigned my device's irq at SPI 176 (= INTID 208 ).
> And I found in the qemu's gicv3_cpuif_update function below, the
> icc_hppi_can_preempt(cs) returns false because cs->hppi.prio == 0xff.
> I understand this means the
On Fri, 1 Apr 2022 at 10:27, Chan Kim wrote:
> static void create_ab21q_axpu_device(const Ab21qMachineState *vms,
> MemoryRegion *mem)
> {
> char *nodename;
> hwaddr base = vms->memmap[AB21Q_AXPU].base;
> hwaddr size = vms->memmap[AB21Q_AXPU].size;
> int
On Tue, 22 Mar 2022 at 14:21, Zongyuan Li wrote:
>
> I recently read the following code in hw/openrisc/openrisc_sim.c:
>
> > if (num_cpus > 1) {
> >DeviceState *splitter = qdev_new(TYPE_SPLIT_IRQ);
> >qdev_prop_set_uint32(splitter, "num-lines", num_cpus);
> >
On Tue, 22 Mar 2022 at 06:42, Chan Kim wrote:
>
> Hi,
>
> It may not be important but I'm trying to make the linux boot log the same
> for qemu direct kernel loading and loading by u-boot.
> In armv8 the cntfrq_el0 register is supposed to be written with the system
> counter frequency. The armv8
On Thu, 17 Mar 2022 at 10:19, Johannes Zirngibl wrote:
> At first i have to say that i found a Step by Step Guide following this link.
> https://linuxconfig.org/how-to-run-the-raspberry-pi-os-in-a-virtual-machine-with-qemu-and-kvm
> STEP 7 Build the VM and Emulate Raspi3
>
>
> $ sudo
On Tue, 15 Mar 2022 at 07:36, Johannes Zirngibl wrote:
> 2.) sudo qemu-system-aarch64 -machine raspi3b -drive
> file=kube-worker-1.img,format=raw -drive-
> if=none,id=stick,file=/home/john/Downloads/2022-01-28-raspios-bullseye-armhf/2022-01-28-raspios-bullseye-armhf.img,format=raw
> -device
On Mon, 14 Mar 2022 at 09:06, Chan Kim wrote:
> After this, I tried to read the memory at 0x8020 to see if this kernel
> Image is there but could not find it.
>
> I used this method to see memory at 0x8020 :
>
> during the machab21q_init function,
>
> Ram_ptr =
On Fri, 25 Feb 2022 at 02:53, Chan Kim wrote:
> Hi, Could anyone explain to me what ‘secure=on’ option means?
>
> Doesn’t it mean the virtual hardware machine has security features
> implemented? (that’s what I understand)
$ qemu-system-aarch64 -M virt,help | grep 'secure'
secure= -
On Thu, 24 Feb 2022 at 21:57, Frederick Virchanza Gotham
wrote:
>
> I want to test a program of mine on all kinds of computer. I've been
> able to build my program for 32-Bit ARM Big Endian and then run it in
> Qemu-user on a 64-Bit x86 Little Endian desktop computer.
>
> Do any of the targets of
On Thu, 24 Feb 2022 at 10:53, Ben Dooks wrote:
> I have been trying to get qom-get/qom-set scripts working to make an
> virtual GPIO device on qemu-system-x86_64. I have a working TMP105
> and I can see the MAX7310 being instantiated with the relevant Linux
> devices showing up (i2c, gpio).
>
> I
On Thu, 17 Feb 2022 at 14:27, Glenn Michael Petrie via
wrote:
>
> I have a problem compiling this version of QEMU which I didn't have people. I
> am compiling it using the git repository and am in the process of "make"ing
> it. I got up to [2072/9676] then I get a "Segmentation Fault", as shown
On Thu, 17 Feb 2022 at 08:49, Chan Kim wrote:
> I found by setting -cpu max, this ID_AA64MMFR1 register value is read
> correctly.
The value is correct in both cases. The Cortex-A72 does not implement
the VHE architecture feature (it is mandatory from Armv8.1, but the
A72 is an Armv8.0 core).
On Sun, 13 Feb 2022 at 18:24, Frederick Virchanza Gotham
wrote:
> I have written a program called 'Dynamo', and I have built it as a 32-Bit Big
> Endian ARM executable binary. (The architecture codename for 32-Bit Big
> Endian ARM is "armeb").
>
> When I run this 'armeb' binary on my x86_64
On Wed, 9 Feb 2022 at 02:27, Jiatong Shen wrote:
>
> Hello community,
>
>I am trying to find new changelogs for each release. I find there is a
> site (https://wiki.qemu.org/ChangeLog/6.1) for it, but looks like it does not
> contain every changes. for example,
>
On Sat, 29 Jan 2022 at 02:44, Chan Kim wrote:
>
> Oh, I found it was -gdb tcp::1235. (I had tried only -gdb tcp:1235)
>
> I think the manual should better have this information there.
The syntax for that is given as one of the examples in the
-gdb option description in the "Invocation" section
On Wed, 19 Jan 2022 at 18:50, Schultschik, Sven
wrote:
>
> Actually I try to emulate a real eMMC. I thought an sdcard would be
> sufficient, but I'm not sure.
>
> eMMC (Embedded Multi Media Card) has a feature called RPMB (Replay Protected
> Memory Block).
>
> Now if I think more about it I
On Wed, 19 Jan 2022 at 14:44, Godmar Back wrote:
> after upgrading to 6.2.0, I observed that code such as MIT's xv6 (see
> [1]) is no longer able to detect multiple CPUs. Their code works in
> 6.1.1, however.
Hi; this isn't a great place for reporting QEMU bugs, because
it's more of a
On Tue, 18 Jan 2022 at 18:13, Schultschik, Sven
wrote:
> I try to add an eMMC to a qemu aarch64 virt machine. This for I try to use
> the type if=sd but it fails and I don’t find any hint, how to do it properly.
This is because the virt board doesn't have an SD controller.
> So I search now a
On Thu, 13 Jan 2022 at 15:03, Wenqing Xu wrote:
> I have met a problem with QEMU’s virtio-serial device while using it to
> invoke bash process inside VM from host. But we’ve met a problem that if the
> host process is closed unexpectedly, following calls then will fail and stuck.
>
> Some
On Tue, 11 Jan 2022 at 17:06, zadig wrote:
>
> > Because qemu-user is specifically emulating a Linux kernel.
> > We don't want to provide a million tweakable command line options,
> > it gets unmaintainable very quickly. We just want to provide the
> > process with the environment that the Linux
On Tue, 11 Jan 2022 at 16:33, zadig wrote:
>
> Thanks for your celerity.
>
> > The architecture specifies that the number of bits used for the
> > signature depends on various properties of the CPU and of
> > the configuration that the host OS has put it into.
> Yes, this is why I checked for the
On Tue, 11 Jan 2022 at 15:28, zadig wrote:
>
> Hello,
>
> I am running some dummy aarch64 ELF I have built using clang with
> -mbranch-protection=pac-ret+leaf+b-key.
>
> qemu successfully emulates the code, however the pointer authentication
> signature seems weird to me: only one byte is used
On Tue, 21 Dec 2021 at 16:23, abhijeet inamdar
wrote:
> How did we decide the NUM_IRQ_LINES 64 for stellaris?
Either:
(a) we looked at the documentation for the hardware, which told us
that this SoC is built with its Cortex-M core configured with
that many interrupt lines
Or:
(b) this is for
On Thu, 16 Dec 2021 at 20:07, abhijeet inamdar
wrote:
>
> If I won't make that change it gives me immediate error as follows:
>
> Taking exception 18 [v7M INVSTATE UsageFault]
> ...BusFault with BFSR.STKERR
> ...taking pending nonsecure exception 3
> qemu: fatal: Lockup: can't take terminal
On Thu, 16 Dec 2021 at 17:44, Philippe Mathieu-Daudé wrote:
>
> Cc'ing qemu-arm developers.
>
> On 12/16/21 18:31, abhijeet inamdar wrote:
> > Hi,
> >
> > I was running my .elf file on my custom machine(CM3) and was hit with
> > this error when debugging and had the required -d flags and single
On Tue, 14 Dec 2021 at 09:52, Marc Zyngier wrote:
> You are still missing the point of how QEMU works:
>
> - QEMU creates a dummy VM with a single vcpu. This can happen on *any*
> CPU.
> - It snapshots the sysregs for this vcpu, and keep them for later
> - It then destroy this VM
> - QEMU then
KVM on big.little setups is a kernel-level question really; I've
cc'd the kvmarm list.
On Mon, 13 Dec 2021 at 15:02, Qu Wenruo wrote:
>
>
>
> On 2021/12/13 21:17, Michal Prívozník wrote:
> > On 12/11/21 02:58, Qu Wenruo wrote:
> >> Hi,
> >>
> >> Recently I got my libvirt setup on both RK3399
On Fri, 10 Dec 2021 at 15:44, abhijeet inamdar
wrote:
>
> Hi,
>
> In the Qemu monitor:
>
> (qemu) info qom-tree
> /machine (vcpu-machine)
> /peripheral (container)
> /peripheral-anon (container)
> /unattached (container)
> /sysbus (System)
> What does this "Unattached" mean here?
On Wed, 8 Dec 2021 at 10:45, abhijeet inamdar
wrote:
>
> Hi,
>
> Are these lines to be changed accordingly for my compatible
> https://github.com/qemu/qemu/blob/stable-4.2/target/arm/helper.c#L9842-#L9852
> or is it fixed?
Those lines aren't board-specific, they are an
architectural
On Tue, 7 Dec 2021 at 09:23, abhijeet inamdar
wrote:
>
> And we have two memory map one at the boot time and other is the normal
> memory map. There is slight chance in the size/addresses. My doubt is which
> do mapping do we usually follow?
The rule of thumb is: model what the real hardware
On Mon, 6 Dec 2021 at 13:30, abhijeet inamdar
wrote:
>
> How to find out where actually the hardware is expecting the initial VTOR?
This should be documented in its technical reference
manual/specification.
-- PMM
On Sun, 5 Dec 2021 at 17:16, abhijeet inamdar
wrote:
>
> So the solution would be placing the vector correctly and mapping to the
> right address for Flash/RAM...?
Yes, you need to make sure your model:
* puts RAM and flash where the hardware does
* configures the CPU object to set the
On Sat, 4 Dec 2021 at 23:06, abhijeet inamdar
wrote:
> I'm getting this error. There is no hit for this in google as most are on
> Hardfault. The error is :
>
> "Taking exception 18 [v7M INVSTATE UsageFault]
> ...BusFault with BFSR.STKERR
> ...taking pending nonsecure exception 3
> qemu: fatal:
On Wed, 1 Dec 2021 at 19:28, Leek, Jim wrote:
> So, why doesn't QEMU support external checkpoints? (ie an option
> where checkpoints each get written to a new file.)
If you really want to save to an external file I think you
can do this by treating it as a migration (which is the same
On Wed, 1 Dec 2021 at 14:14, Динар Талибуллин wrote:
>
> Hello. Is it possible to save qemu state if image is in *. elf format?
> I tried to do it in qemu monitor, but it require qcow2 format
You need QEMU to know about one disk which is in qcow2 format,
so it can save the state there, but that
On Tue, 30 Nov 2021 at 22:53, abhijeet inamdar
wrote:
> What difference does it make to define:
>
> DeviceState *nvic;
>
> nvic = qdev_create(NULL, TYPE_ARMV7M);
This creates a new device in freshly allocated memory,
both initializing and realizing it, and returns a pointer
to that newly created
On Fri, 19 Nov 2021 at 20:56, Garrick Toubassi wrote:
> But the question remains as to whether the behavior is expected that if you
> have pages which are executable and also written to, the writes will be
> persistently slow? Or is that a possible (fringe) bug?
I think that is just always
On Mon, 8 Nov 2021 at 18:05, David Fernandez wrote:
> I couldn't get the stock qemu-system-x86_04 to boot correctly, as it was
> an old version 2.11.1, I decided to recompile from sources to see if
> that would fix the problem, but the problem still persists, using both
> top of master and
On Mon, 8 Nov 2021 at 18:05, David Fernandez wrote:
>
> ../configure \
>--enable-lto \
Does disabling LTO make a difference? That's about the only
thing in the configure options that stands out as maybe
making a difference.
-- PMM
On Thu, 11 Nov 2021 at 12:45, David Fernandez wrote:
> On 11/11/2021 11:23, Peter Maydell wrote:
> > The problem is that the
> > udev machinery that creates nodes in /dev is being too slow
> > (or possibly is failing for some other reason, but given all the
> >
On Wed, 10 Nov 2021 at 18:56, David Fernandez wrote:
>
> As I have not hear anything yet, I thought I would summarize the current
> status
> for this problem. Please, let me know if any other tests or information are
> needed.
>
> I am running qemu-system-x86_64 v5.2.0 (also tried v6.1.0 and top
On Tue, 9 Nov 2021 at 15:00, Arnabjyoti Kalita
wrote:
>
> Thank you very much, Peter. I have got the gist of the code flow.
> Based on your explanation, I have a couple of questions to ask -
>
> - In cpu_restore_state(), can it happen that the host PC is incorrect
> and thereby, the resultant
On Tue, 9 Nov 2021 at 05:44, Arnabjyoti Kalita
wrote:
> I am trying to understand how page faults happen when a guest is
> executing in TCG mode. Specifically, how does TCG determine at which
> instruction pointer did page fault happen? Which functions in the TCG
> code flow get called when it
On Mon, 8 Nov 2021 at 20:22, David Fernandez wrote:
>
> Hi Peter,
>
> Answers in line.
>
> On 08/11/2021 19:59, Peter Maydell wrote:
> > On Mon, 8 Nov 2021 at 18:05, David Fernandez
> > wrote:
> >> I am running qemu-system-x86_64 on aarch64 running U
On Mon, 8 Nov 2021 at 18:05, David Fernandez wrote:
> I am running qemu-system-x86_64 on aarch64 running Ubuntu 18.04 as both
> guest and host.
>
> I couldn't get the stock qemu-system-x86_04 to boot correctly, as it was
> an old version 2.11.1, I decided to recompile from sources to see if
>
On Wed, 3 Nov 2021 at 14:04, abhijeet inamdar
wrote:
> In a machine definition can there be a two different "cpu-type"
> ( say ARM M or A or R)that can be emulated ? (if it make sense)
Currently a machine can have multiple CPUs as long as
they are from the same guest architecture. So you can
On Tue, 2 Nov 2021 at 14:39, abhijeet inamdar
wrote:
>
> Can you elaborate the Testing point (3) as I have never done any unit test so.
Look at some of the existing tests like the one I suggest,
write tests that do that kind of thing. "Unit test" here
just means "this is a test case that tests
On Tue, 2 Nov 2021 at 13:15, abhijeet inamdar
wrote:
>
> Hi,
>
> I have a hardware which I want to emulate on QEMU based on arm Cortex M3. I
> tried to follow the examples like mps2 or stellaris.
>
> I'm finding it really hard to figure out how can I test the
> devices/peripherals I add to the
On Fri, 29 Oct 2021 at 04:44, Виртуалины MER user MER
wrote:
>
> when will the android qemu emulator version be added on the qemu.org website
Never, because the Android emulator is something written and provided
by Google. It's not something that the upstream QEMU developers have
anything to do
On Thu, 30 Sept 2021 at 12:34, abhijeet inamdar
wrote:
> Actually the ELF generates the .bin file which is being used to run on the
> target (hardware). It's address starts from zero when I see the starting
> frames of it. As follows:
>
> IN:
> 0x0002: c0de stm r0!, {r1, r2, r3,
On Thu, 30 Sept 2021 at 07:17, abhijeet inamdar
wrote:
>
> But this very ELF file runs on the target(real hardware) perfectly. So how
> different should it be to emulate?
Real hardware doesn't have a magic ELF file loader. The
details of what a debug environment or whatever mechanism
you're
On Wed, 29 Sept 2021 at 16:24, abhijeet inamdar
wrote:
>
> I tried to add -d in_asm,out_asm,guest_errors it gives out as follows:
'int,exec,cpu' are probably also helpful.
> [New Thread 0x7fffe700 (LWP 44283)]
>
> IN:
> 0x: andeqr0, r0, r0
We started
On Sat, 18 Sept 2021 at 09:12, Ali Vatankhah wrote:
> then to check what instructions are executing I run this command:
>
> qemu-system-ppc64 -nographic -M ppce500 -cpu e5500 -kernel uImage -singlestep
> -d in_asm -D target_asm.log
>
> Obviously this results in a Kernel panic, but the point is
On Thu, 16 Sept 2021 at 20:13, abhijeet inamdar
wrote:
>
> Is there any way/s to check where actually is it failing or point which file?
Use the usual debugging facilities -- gdbstub or -d debug logging.
-- PMM
On Thu, 16 Sept 2021 at 19:46, Peter Maydell wrote:
>
> On Thu, 16 Sept 2021 at 17:52, abhijeet inamdar
> wrote:
> > How do I fix it ? it's for cortex-m3 and the below is the gdb trace when I
> > load ELF.
> >
> > qemu: fatal: Lockup: can't escalate 3
On Thu, 16 Sept 2021 at 17:52, abhijeet inamdar
wrote:
> How do I fix it ? it's for cortex-m3 and the below is the gdb trace when I
> load ELF.
>
> qemu: fatal: Lockup: can't escalate 3 to HardFault (current priority -1)
>
> R00= R01= R02= R03=
> R04=
On Wed, 15 Sept 2021 at 12:13, abhijeet inamdar
wrote:
>
> Now there are some many UART implemented in the hw/char. What should we look
> for or how do you choose which one to use? or implement similar kind.
You implement what the hardware you are modelling has, obviously.
This is why we have
On Wed, 15 Sept 2021 at 08:23, abhijeet inamdar
wrote:
>
> Hi,
>
> As my custom machine is based on cortex-m3 I checked the stellaris.c
> https://github.com/qemu/qemu/blob/stable-4.2/hw/arm/stellaris.c#1384,1390.
> Does only this part define the UART peripheral for this machine? Can you
>
On Tue, 14 Sept 2021 at 13:51, abhijeet inamdar
wrote:
>
> Is there any example for UART being added to the machine in 4.2.0?
Lots of machines have UARTs. Look at almost any Arm board.
-- PMM
On Tue, 14 Sept 2021 at 11:21, abhijeet inamdar
wrote:
>
> My question is that can we see the list of devices for say any particular
> machine.
> EX: if we do -m help.
> we do get the list of machines right so is their anything similar for the
> devices to check for a particular machine.
"-M
On Tue, 14 Sept 2021 at 10:58, abhijeet inamdar
wrote:
> Is there anything in qemu to check for a machine which all
> devices are added or working? Can we do that!?
I dunno what you're asking for; could you elaborate ?
In general each machine has a different set of devices that
it has, because
On Tue, 14 Sept 2021 at 09:52, abhijeet inamdar
wrote:
> I was trying to emulate a machine in qemu-4.2.0 but was getting an error
> message:
>
> Unexpected error in qemu_chr_fe_init() at
> /home/qemu-4.2.0/chardev/char-fe.c:220:
> qemu-system-arm: Device 'serial0' is in use
>
> I tried to apply
On Thu, 9 Sept 2021 at 20:24, Eric Blake wrote:
> There may be other less-risky ways for easily transferring files
> between host and guest; I know in the past I have seen both p9 and MTP
> file systems mentioned as approaches, although I do not have
> experience with setting those up myself to
On Wed, 8 Sept 2021 at 01:29, Hinko Kocevar wrote:
> I would like to be able to see target CPU state for every instruction that
> gets emulated.
>
> Looking at the qemu code and experimenting with the options I can get only
> pre/post tb CPU state printed; I would like to see also the state for
On Sun, 5 Sept 2021 at 20:53, David Faller wrote:
> I have a little question about aarch64 virtualization on x86_host.
>
> At home I build up a virtual machine running aarch64 debian.
> My system setup is an AMD Ryzen 5900x.
> On this System aarch64 emulation runs really smooth and fine without
On Sun, 5 Sept 2021 at 16:01, Mike Ladouceur wrote:
>
> # This runs fine
> ./configure --enable-kvm --enable-system --enable-spice --enable-opengl
> --enable-virglrenderer --enable-libusb --target-list=aarch64-softmmu
>
> # Make runs. with no errors
>
> # No egl-headless here
> $
On Sat, 4 Sept 2021 at 21:02, Mike Ladouceur wrote:
>
> Hi, for some reason I can't seem to compile qemu-system-aarch64 with
> egl-headless capability on Ubuntu on a Raspberry Pi 4. I have all the
> dependencies and configure passes without any errors as well as make. I'm
> using the git repo.
On Tue, 31 Aug 2021 at 13:37, wrote:
> The peripheral model just passes the ioctl requests from the driver to the
> simulator shared library. This application runs ok in baremetal case, but
> when running as a ubuntu application, the output has many errors.(15%~30%,
> error occurs in 8 word
On Tue, 31 Aug 2021 at 05:48, Arnabjyoti Kalita
wrote:
>
> Dear Peter,
>
> I had a few additional questions with regards to dma_memory_map(). So,
> let's say I record the buffer that has been written/read from the
> disk.
>
> iov[num_sg].iov_base = dma_memory_map(vdev->dma_as, pa, , s_write ?
>
On Mon, 30 Aug 2021 at 18:18, Albert Brooks wrote:
>
> Hello QEMU,
>
> I saw that QEMU was a contributor to Godel.Run.
I guess you're referring to their web page, which says:
"Driven by the following open source projects, thanks to their
contributors. QT6 | noVNC | CodiMD | QEMU"
?
That just
On Mon, 30 Aug 2021 at 03:30, Arnabjyoti Kalita
wrote:
>
> > That's normal, yes, but you can't guarantee it. The guest can
> > choose to program it to any physical memory it likes.
>
> Is it ? If this is indeterministic, my approach will obviously not
> work.
It's deterministic to the extent
On Sun, 29 Aug 2021 at 04:48, Arnabjyoti Kalita
wrote:
>
> Thank you for the detailed explanation, Peter. It makes a lot of things clear
> now.
>
> I see that the virtio block device is accessing guest physical memory that is
> not backed by a device.
That's normal, yes, but you can't
On Sat, 28 Aug 2021 at 16:56, Marcel Prisi via wrote:
>
> Hi all,
>
> I am trying to "virtualize" an older C3000 application to a qemu based setup.
> It runs on HP-UX 10.20.
This is the third time in three days that you've posted the same email.
The first copy got through fine, you don't need
On Sat, 28 Aug 2021 at 13:03, Arnabjyoti Kalita
wrote:
> I am trying to understand how a virtio-block device updates "used" buffers in
> the virtqueue. I intend to 'mimic' this process without the actual disk event
> happening, by storing the used buffers and then re-using them later. I can
>
On Fri, 27 Aug 2021 at 19:49, Frans de Boer wrote:
> Following your pointers, I noticed that it was all about missing static
> libraries/header files. The error messages where not helpful at all.
> config.log provided some pointers.
Yeah. We tend to assume "the compiler works" a bit more than
On Fri, 27 Aug 2021 at 10:34, Frans de Boer wrote:
> I try to build qemu-aarch64-static, but all I get are errors;
> 6.1.0"big/little test failed"
>
> 6.0.0 "ERROR: sizeof(size_t) doesn't match GLIB_SIZEOF_SIZE_T.
> You probably need to set PKG_CONFIG_LIBDIR
> to point to the
On Sun, 22 Aug 2021 at 16:07, Mahesh Kurapati
wrote:
> I get below error when I try to build the QEMU on my unbuntu16.04 VM. I
> tried to upgrade the glib tool, but it says it is already at the latest
> version 2.48. How do I (force) update to the needed versions? Any ideas?
You should
On Thu, 19 Aug 2021 at 06:54, asif siddiqui wrote:
>
> Hello All,
>
> We are using xlnx-zcu102 machine and following command to boot the QNX OS as
> guest on top of QEMU with WIndows as HOST OS.
>
> QEMU Command to boot QNX Image-
> qemu-system-aarch64 -M xlnx-zcu102 -m 8G -serial mon:stdio
On Mon, 16 Aug 2021 at 15:14, lejeczek wrote:
> On 16/08/2021 10:02, Peter Maydell wrote:
> > Please don't make me try to reconstruct what you ran. Run
> > the command, and cut-and-paste the command line and the
> > output from your terminal into an email.
> reconstr
On Sun, 15 Aug 2021 at 17:26, lejeczek wrote:
> On 15/08/2021 13:17, Peter Maydell wrote:
> > How about you say what command line(s) you tried that gave that
> > error message ?
> Almost identical to the original, only take out 'options'
> out and put in front of '-b' (or a
On Sun, 15 Aug 2021 at 13:07, lejeczek wrote:
>
>
>
> On 14/08/2021 11:19, Peter Maydell wrote:
> > On Sat, 14 Aug 2021 at 08:24, lejeczek wrote:
> >> -> $ qemu-img create -f qcow2 -b -o
> >> encrypt.key-secret=3fd57349-3671-4cf2-ab00-f13b8ba00a4d
> >
On Sat, 14 Aug 2021 at 08:24, lejeczek wrote:
> -> $ qemu-img create -f qcow2 -b -o
> encrypt.key-secret=3fd57349-3671-4cf2-ab00-f13b8ba00a4d
> /00.GLUSTER-mnt/VMs3/enc.locallan.qcow2 -F qcow2
> ./enc.locallan.qcow2.bkp
> qemu-img: Invalid image size specified. You may use k, M, G,
> T, P or E
On Wed, 11 Aug 2021 at 19:42, Frans de Boer wrote:
> Your proposal (copying qemu-aarch64 to the target directory) is just the
> thing I wanted to avoid. However, Philippe has offered the right
> solution. I missed the -L flag because that was what I needed and -
> albeit not very well - looked
On Wed, 11 Aug 2021 at 03:52, wrote:
> I thought I’d better setup TAP networking for qemu to solve my problem.
>
> I’ve used qemu with TAP networking several years ago and can find some
> information on the internet but wish there were a kind information on the
> official qemu document site.
>
On Fri, 6 Aug 2021 at 10:16, wrote:
>
> Sorry, I soon found when I run the application on the OS, the breakpoint work
> in the debugger and the debugger command and source window comes back.
>
> I need to occasionally type ctrl-l to see the source code clearly.
You can also use any of the
On Wed, 4 Aug 2021 at 10:28, Sukreet pal wrote:
>
> I can share the .config file. Is there a guide available which I can use to
> add a new machine in upstream QEMU ?
>
> The configuration file is attached with this email.
That's a Linux kernel configuration file. It does not contain
anywhere
On Wed, 4 Aug 2021 at 08:58, Sukreet pal wrote:
>
> Hi developers,
>
> I am new to qemu system emulation. I currently have a configuration file from
> a control unit which uses Infineon Tricore SAK-TC234LX 32F200 AB with ARM v7
> processor.
>
> I am able to build the zImage with the config file
101 - 200 of 680 matches
Mail list logo
