On Thu, 25 Apr 2024 at 09:55, lacsaP Patatetom wrote:
>
> hi,
>
> when using `qemu-img create`, why do I have to specify the format of the base
> image ?
> can't `qemu-img` detect it itself ?
Image format detection isn't 100% reliable. Notably, a 'raw'
format image could in theory look like any
On Fri, 29 Mar 2024 at 12:47, Raphaël Poggi wrote:
>
> Hi,
>
> I am currently working on adding support of a custom ASIC based on
> ARMv7-M (Cortex-M3).
>
> I have a RAM region defined as followed:
>
> base address = 0x0021E000
> size = 0x1FFC
>
> For some reason, during memcpy performed on guest
On Thu, 21 Mar 2024 at 08:16, Sanjeev Kumar wrote:
>
> Hi,
> our kernel is build with aarch64le. it is 64 bit ARM architecture.
Such a kernel cannot possibly boot on the vexpress-a15 machine
that you say you are using. So something doesn't seem right...
> when i am trying to use virt as
On Wed, 20 Mar 2024 at 13:06, Sanjeev Kumar wrote:
>
> Hi Peter,
> Thanks for your detailed review.
> ifs.bin is our custom build and the linux kernel is booting fine with this
> file.
If it is, then it must be a 32-bit kernel. So trying to run it
on the cortex-a57 will not work at all, because
On Wed, 20 Mar 2024 at 06:40, Sanjeev Kumar wrote:
>
> Hi,
> Sorry for incomplete command.
> here is the complete command line.
>
> qemu-system-aarch64 -machine vexpress-a15 -cpu cortex-a57 -smp 4 -m 10G
> -kernel ifs.bin -drive file=disk-qemu.vmdk,if=none,id=drv0 -device
>
On Tue, 19 Mar 2024 at 09:41, Sanjeev Kumar wrote:
>
> Hi,
> I am starting QEMU as below.
> qemu-system-aarch64 [] -device ivshmem-plain,memdev=hostmem -object
> memory-backend-file,size=1M,share=on,mem-path=/dev/shm/ivshmem,id=hostmem
Please give us the *full* command line, not the
On Thu, 7 Mar 2024 at 01:03, yb liu wrote:
>
> Thanks a lot for you respond me soon!
> The exact instruction is mrc, and the exception happended in early boot
> process. I have no idea to how to debug this error because it happended in
> code_gen_prologue.
That's a system register access. If
On Wed, 6 Mar 2024 at 14:33, yb liu wrote:
>
>
> Dear QEMU developers
>
> I hope this email finds you well. We are currently facing an issue related to
> QEMU and the Cortex-A55 architecture. Specifically, we have compiled a
> firmware for Cortex-A55 and would like it to run smoothly on QEMU
On Tue, 5 Mar 2024 at 18:31, Vadim Idelchuk via wrote:
> The additional information about my build:
Thanks for that. Yeah, you're missing only this machine type.
I had a poke around in the config files, and I think this is because
the machine has a dependency on pixman, so if configure doesn't
On Mon, 4 Mar 2024 at 11:20, Vadim Idelchuk via wrote:
> For building the products I run the following:
>
> ./configure
>
> make
>
>
>
> I tried these sequence number of times with the same result - machine type
> xlnx-zcu102 is absent in the list of supported machines
What is the exact command
On Sun, 3 Mar 2024 at 11:01, Vadim Idelchuk wrote:
> I built the latest version of QEMU - v8.2.0-1528-g5767815218.
> But the machine xlnx-zcu102 is absent in the list of supported machines.
> Is it need any additional definitions for building?
It should build by default if you build the aarch64
On Mon, 26 Feb 2024 at 10:59, ankita suman wrote:
> I am trying to emulate multi core processor (dual core for now) on QEMU. The
> processor I am targeting is cortex m7. I tried by running multiple instances
> of QEMU to emulate multi cores, and use shared memory for communication, but
> since
On Sat, 24 Feb 2024 at 22:02, Serdar Bahar wrote:
> I'm trying to enable Spice in my virtual machine. In order to do that, I've
> found that I should append my booting command line with an option like this :
> "-spice port=3001...". However, when I try this, I get the error:
>
On Tue, 20 Feb 2024 at 21:26, Michael N. Moran wrote:
> I really wanted a way to specify associations between front-end
> (serial?) and back-end (chardev?) without the need for the
> sequential assignment of front-ends, and the need to skip
> unused front-ends by using the likes of -serial null.
On Mon, 19 Feb 2024 at 20:57, Michael N. Moran wrote:
>
> I'm working on Linux with `qemu-system-arm -machine olimex-stm32-h405`, which
> uses an `stm32f405-soc` that implements 8 USARTs(UARTs).
>
> I currently use two "-serial telnet" options which assigns the first two
> USART ports
On Fri, 9 Feb 2024 at 16:53, Christopher Davies
wrote:
> I've been down a bit of a rabbit hole trying to get the Linux AMBA-CLCD
> driver for versatilepb target's graphics to work with modern Linux kernels.
> After a good deal of reading of both the Linux kernel code and the qemu code,
> I
On Wed, 31 Jan 2024 at 12:12, Minjun Hong wrote:
>
> Hello.
>
> I'm trying to execute AARCH64 Linux kernel on the QEMU.
>
> But,there was an error and the error log is:
>>
>> rom: requested regions overlap (rom bootloader. free=0x422c0a00,
>> addr=0x4000)
>>
On Tue, 9 Jan 2024 at 16:12, Stephen Bates via wrote:
>
> Hi
>
> I am exploring the rather awesome TCG Plugin feature of QEMU
> (https://www.qemu.org/docs/master/devel/tcg-plugins.html#). The latest
> documentation for this feature states:
>
> "This is a new feature for QEMU and it does allow
On Mon, 18 Dec 2023 at 23:56, Dave Blanchard wrote:
>
> > Hmm. Well, we do put the terminal into raw mode (so that we
> > get stuff like ^C), but that is supposed to be reset when
> > QEMU exits.
>
> Can you please direct me to where in the source code this happens?
It happens in different
On Mon, 18 Dec 2023 at 13:36, Dave Blanchard wrote:
>
>
> > If you're directing a guest's terminal to the console then things
> > like line wrapping are entirely up to the guest -- QEMU is
> > providing the equivalent of a piece of hardware like a serial
> > terminal, and how the guest chooses to
On Sun, 17 Dec 2023 at 22:49, Dave Blanchard wrote:
>
> One particularly annoying trait of Qemu is how it nukes my terminal settings.
> This is especially infuriating when booting Linux where the VM console is
> redirected to the serial port, which is then displayed on the host console.
>
On Mon, 11 Dec 2023 at 11:52, Shunsuke Mie wrote:
> The steps taken are as follows:
>
> 1. build qemu v6.2.0-rc2
Is that a typo for "v8.2.0-rc2", or are you really building
from a two year old release candidate ?
thanks
-- PMM
On Wed, 29 Nov 2023 at 15:08, 泰宇周 wrote:
>
> I tried to use febootstrap to make a roofs image for qemu-kvm.
> It reported that
>
> [1.766919] Kernel panic - not syncing: VFS: Unable to mount root fs
> on unknown-block(0,0)
When the kernel tells you it can't mount the root filesystem,
On Wed, 8 Nov 2023 at 01:40, 陈朱叠(澜赆) wrote:
>
> Dear QEMU folks,
> We have modeled our system using qemu, which includes multiple cortex-m
> cores and multiple neoverse n1 cores, all running in TCG mode. Based on this,
> we want to use KVM technology to accelerate the performance of the
On Tue, 31 Oct 2023 at 06:51, Jiatong Shen wrote:
>
> Hello community experts,
>
> I am using a 4.2.0 versioned qemu and passthrough an A40 (48G GPU memory).
> When I start the virtual machine with following option "-m
> size=4096M,slots=2,maxmem=1T ", the virtual machine could boot but the
On Sun, 24 Sept 2023 at 23:05, Igor Ordecha wrote:
> I'm trying to emulate a USB thumb drive from a .img file. My current
> arguments for that look like this:
>
> -drive file=/path/to/file.img,if=none,id=drive-usb0,format=raw -device
> nec-usb-xhci,id=xhci -device
>
On Sun, 10 Sept 2023 at 20:52, Narcis Garcia wrote:
>
> I do with this command:
>
> sudo apt --autoremove remove qemu qemu-system qemu-utils
>
> ...but probably your operating system provides a graphical package
> manager that helps to do it with a single click.
Yes, if you installed QEMU via
On Thu, 17 Aug 2023 at 09:05, Swedha R wrote:
>
> Hi,
> In the qemu website , under the section ARM system emulator, they mentioned
> like,
>
> Secure-World-only devices if the CPU has TrustZone:
>
> A second PL011 UART
> A second PL061 GPIO controller, with GPIO lines for triggering a system
On Fri, 11 Aug 2023 at 18:52, Mario Marietto wrote:
>
> ok. I could extract the kernel files (so,between the qemu parameters I should
> put : initrd and vmlinuz,right ? How ?
>
> -enable-kvm -serial stdio -kernel vmlinux -what here initrd \
>
> from the ubuntu 22.10 img,but I'm sure that it does
On Fri, 11 Aug 2023 at 18:27, Mario Marietto wrote:
>
> ok. I've been lucky. Qemu compiled successfully. Now I'm going to execute
> this command :
>
> qemu-system-arm \
> -enable-kvm -serial stdio -kernel zImage \
> -m 512 -M vexpress-a15 -cpu cortex-a15 \
> -drive
>
On Fri, 11 Aug 2023 at 17:05, Mario Marietto wrote:
>
> I made some progress,but unfortunately I've got an error :
>
> root@devuan:~/Desktop/qemu-v5.1.0# ./configure --target-list=arm-softmmu
> --enable-opengl --enable-gtk --enable-kvm --enable-guest-agent --enable-spice
> --audio-drv-list="oss
On Fri, 11 Aug 2023 at 14:44, Валентин via wrote:
>
> > I've thought to compile it directly on the devuan 4 installed on the ARM
> > chromebook.
>
> If you have native Arm toolchain, it's even simpler then – just try to
> "./configure" and "make".
Specify a --target-list= option to configure
On Fri, 11 Aug 2023 at 13:30, Mario Marietto wrote:
>
> ok. Can you share the github address ? I found the source code for x86-x64
> but not for armhf.
There is not, and has never been, a separate git tree for
different guest architectures. It is all in the one
git tree at
On Fri, 11 Aug 2023 at 12:19, Mario Marietto wrote:
> Anyway,can you tell me where is the branch 5.1 for the qemu source code for
> armhf ?
You want the "v5.1.0" git tag.
-- PMM
On Fri, 11 Aug 2023 at 11:34, Mario Marietto wrote:
>
> ok. I will recompile a qemu version lower than 5.2. I've asked all around and
> someone says that I should use 5.1,someone else 4.9. Which version should I
> use ? And,please can you point me to a good tutorial that can teach me the
>
On Thu, 10 Aug 2023 at 18:28, Mario Marietto wrote:
>
> ---> You can't use KVM with the vexpress-a15 board. The only Arm guest
> machine that will work with KVM is the "virt" board.
>
> point 1)
>
> On the virtual open systems website they used the vexpress-a15 board. You can
> read by yourself
On Thu, 10 Aug 2023 at 17:52, Mario Marietto wrote:
> I conducted some further experiments :
>
> In this example I've used qemu 5.2.0 installed by default by the devuan 4 :
>
>
> qemu-system-arm \
> -enable-kvm -serial stdio -kernel zImage \
> -m 512 -M vexpress-a15 -cpu cortex-a15 \
>
On Sat, 5 Aug 2023 at 15:00, Lakshmana Reddy wrote:
> I am working on an ubuntu machine and using the qemu platform for emulating
> an x86 architecture .And i am having some doubts related to this work which
> are mentioned as follows
>
> Can I emulate gpio driver pins inside the virtual
On Fri, 4 Aug 2023 at 11:02, Swedha R wrote:
>
> Hi ,
> Is qemu will support virtual GPIO drivers. How to work on GPIO in qemu?
Broadly speaking, you seem to be trying to do something
that QEMU is not set up to do. QEMU's support for GPIO
controllers and GPIO lines is almost entirely there
so we
On Fri, 4 Aug 2023 at 10:25, Swedha R wrote:
>
> Hi team,
> I have arm64 up and running in Qemu, And I built kernel image, rootfs
> everything via buildroot open source I cloned from git.
> And I customized via make - menuconfig like enabling gpio support, libgpiod
> module and in device
On Thu, 3 Aug 2023 at 14:31, Swedha R wrote:
>
> Hi team,
> I have arm64 up and running in Qemu, And I built kernel image, rootfs
> everything via buildroot open source I cloned from git.
> And I customized via make - menuconfig like enabling gpio support, libgpiod
> module and in device
On Sun, 30 Jul 2023 at 21:32, Swedha R wrote:
>
> Hi ,
> when I run this following command , I am facing this problem for all machine
> types rather that virt.
>
> qemu-system-riscv64 -M sifive_u -bios fw_jump.elf -kernel Image -append
> "rootwait root=/dev/vda ro" -drive
On Tue, 25 Jul 2023 at 12:50, Mark Wood-Patrick wrote:
>
> I am trying to debug a driver issue where the driver is running on the guest
> os running under QEMU 7.1.0 using gdb running on the host & connecting to the
> guest. When I try to attach I get a message "qemu-system-x86_64:
On Tue, 11 Jul 2023 at 15:18, Weller, Nitzan wrote:
>
> Hello,
>
> We are trying to run Qemu with E1000 as the NIC.
> The Qemu we use is compiled statically using a Docker, based on
> https://github.com/ziglang/qemu-static.
> When we boot a VM it causes a Segfault that crashes the VM during the
On Mon, 10 Jul 2023 at 09:12, Jiatong Shen wrote:
>
> Hello community experts,
>
> I am trying to learn some arm64 basics using qemu. I would like to
> retrieve a register value
> through hmp command info register. The output is
>
> virsh # qemu-monitor-command --hmp
On Tue, 6 Jun 2023 at 02:07, Ahmed Elsaka wrote:
> i am trying to run QNX ifs.bin for raspberry pi on qmeu but it is not working
> :
>
> what i actually did :
>
> installed qemu-system-aarch64
> downloaded ifs-rpi4.bin file from qnx sw center 3- using the follwoing
> command to run this
On Wed, 31 May 2023 at 18:48, Tanmay Das wrote:
>
> Hi,
>
> Hope all is well with you!
>
> I am trying to use qemu-arm to run a binary and trying to pass a command line
> argument to the main method like below
>
> qemu-arm -cpu cortex-m3 path-to-the-binary
This is the correct syntax. It works
On Wed, 17 May 2023 at 15:36, Jiatong Shen wrote:
>
> Thank you very much for the clarification. Although cpu type cannot be
> changed, another
> registers like aa64isar0, aa64isar1 could be changed through KVM_SET_ONE_REG
> interface,
> and then could potentially hide some cpu features from
On Wed, 17 May 2023 at 14:06, Peter Maydell wrote:
>
> On Wed, 17 May 2023 at 03:23, Jiatong Shen wrote:
> >
> > Hello community Experts!
> >
> > I am doing some experiments with arm64 host machine. The host machine
> > is kunpeng 920 52
On Wed, 17 May 2023 at 03:23, Jiatong Shen wrote:
>
> Hello community Experts!
>
> I am doing some experiments with arm64 host machine. The host machine is
> kunpeng 920 5251k. I try to boot a virtual machine with the following command:
>
> qemu-system-aarch64 -cpu cortex-a53 -enable-kvm
On Mon, 8 May 2023 at 14:18, Zongyuan Li wrote:
>
> I’v noticed that there used to be a patch series working on it:
>
> https://patchew.org/QEMU/20200613213629.21984-1-salil.me...@huawei.com/
>
> It seems to be working, any reason on why it is not merged? Is there any
> difficulty
> to implement
On Thu, 27 Apr 2023 at 10:29, Chan Kim wrote:
> I thought I would try to analyze u-boot's PCIe enumeration using qemu.
> I used qemu-6.2 (old now) and built it for arm-softmmu. And I built
> u-boot-v2022.07 using qemu_arm_defconfig and built linux-5.15.68 using
> integrator_defconfig(just because
On Wed, 19 Apr 2023 at 17:33, Wilm Boerhout wrote:
>
> Is there a Qemu/KVM live CD or such with the minimum 64-bit Debian set to
> support it?
The Debian official live CD image will probably do fine:
https://www.debian.org/CD/live/
I don't know if QEMU is installed in it by default but if it
On Wed, 19 Apr 2023 at 17:27, Wilm Boerhout wrote:
> (Bangs forehead to wall). I have been working too long
> with Raspberry Pi's with 64 bit Debian. I never noticed
> that the laptop runs a 32-bit version of Debian now.
Yeah, if your *host* is running a 32-bit kernel I would
definitely suggest
On Wed, 19 Apr 2023 at 17:14, Wilm Boerhout wrote:
> Thank you Narcis for your attention. Pc.ram is in the error message. And the
> difference between GB and GiB is not the issue.
>
> I tried binging memory down from 12 GB, and only when it was 1 GB, it would
> start the VM. Is there a
On Mon, 17 Apr 2023 at 18:04, Johannes Scheyerle wrote:
> > Am 17.04.2023 um 19:03 schrieb Peter Maydell :
> >
> > On Mon, 17 Apr 2023 at 17:55, Johannes Scheyerle
> > wrote:
> >>
> >> Hey PMM,
> >>
> >> thanks for the replay.
On Mon, 17 Apr 2023 at 15:53, Johannes Scheyerle wrote:
>
> Hey guys,
>
> I'm using an Macbook Air M1 and looking for a possibility to use Windows on
> this computer. The most important thing is, that OpenGL 4 or higher
> supported. Can your System do this?
Bear in mind that on an M1 Windows
On Fri, 7 Apr 2023 at 17:05, Huang Canming wrote:
>
> Sorry for the wrong cmd. It'a typo after I edit the sample command.
> my command is: ./qemu-system-arm -M mymachine -smp cpus=2 -kernel test1.elf
> -bios test2.elf -serial stdio -serial tcp::5678,server=on,wait=off
> which use 'kernel' and
On Fri, 7 Apr 2023 at 11:41, Huang Canming wrote:
>
> hi, members.
>
> I'm trying to model a custom machine which has 2 cpus. Each cpu has its own
> ram/rom.
>
> for now, I have create a different MemoryRegion for the 2 cpu.
>
> I want that the 2 cpu could run differnt firmware, so I use
>
>
On Thu, 30 Mar 2023 at 12:51, Fenix GDH wrote:
> I am working on emulating some soho router firmwares, but most of them use
> SoCs not supported by qemu. I found the Firmguide, where the authors
> implemented some specific devices on QEMU 4.0.0 in order to emulate linux
> kernel. I'm trying to
On Thu, 23 Mar 2023 at 19:57, Pedro Miguel Veiga de Almeida e Silva
wrote:
>
> Hello,
>
> I am trying to cross compile the source code to deploy it in a xilinx ZCU106.
> But every time I execute the ./configure --target-list=aarch64-softmmu
> --enable-kvm and then make.
>
> But the file that
On Thu, 23 Mar 2023 at 06:59, Zheng Jian wrote:
>
> Dear Qemu technical experts:
>
> My question is whether QEMU also needs to support specific CPU models
> when KVM is turned on? Here is the description of the problem I encountered.
No, there's nothing particularly you need to enable in QEMU.
On Sat, 18 Mar 2023 at 23:54, 沈梦姣 wrote:
>
>
> Thanks Peter
>
> > 在 2023年3月19日，上午2:52，Peter Maydell 写道：
> >
> > On Fri, 17 Mar 2023 at 21:01, 沈梦姣 wrote:
> >> TCG knows what registers may be clobbered by a call into
> >> host C code (th
On Fri, 17 Mar 2023 at 21:01, 沈梦姣 wrote:
> TCG knows what registers may be clobbered by a call into
> host C code (this is set up in the tcg_target_call_clobber_regs
> regset by code in tcg_target_init()), so the register allocator
> will either avoid using those registers
>
> Look at
On Fri, 17 Mar 2023 at 15:17, 沈梦姣 wrote:
>
> Hi,
> When generating host code, sometimes it has to jmp to qemu common
> code(e.g. memory management code to get host virtual address), but
> it seems before the jmp the caller saved registers haven’t been
> pushed to stack, qemu common code is
On Tue, 14 Mar 2023 at 11:36, Alyosha Shevandin
wrote:
>
> Peter Maydell,
> can I assume that It would be possible if there was the full emulation of the
> Lenovo hardware, including the all firmware blobs and Intell ME?
As a theoretical question, maybe. But that's never going t
On Sun, 12 Mar 2023 at 16:25, Ahlani Poacher wrote:
>
> Hello, sorry to bother you, I'm a qemu beginner. I want to use QEMU
> to emulate Lenovo's UEFI firmware, but so far I have only found a
> tutorial for QEMU to run EDK2 to implement UEFI. I would like to
> ask how to convert the UEFI
On Thu, 9 Mar 2023 at 15:28, Alyosha Shevandin wrote:
>
> Hi,
> I'm trying ti start virt emulation and fails with the follow error:
> qemu-system-aarch64: device requires 67108864 bytes, block backend provides
> 1112576 bytes
>
> What exactly does it mean and what could be done to prevent it?
>
On Fri, 3 Mar 2023 at 07:27, Robert Henry wrote:
>
> I cannot figure out how to make QEMU TCG emulate aarch64 Graviton G3. I'm
> working against master/head of the QEMU source.
>
> I come up with feature names by consulting
> https://marcin.juszkiewicz.com.pl/download/tables/arm-socs.html
On Mon, 27 Feb 2023 at 17:28, Alyosha Shevandin
wrote:
>
> I'm building the custom SoC emulation that is based on the Cortext-a55.
>
> During the runtime $pc register contains 0 instead the address that is
> provided in means of arm_boot_info.loader_start :
> Then the quemu is started:
>
>
On Tue, 14 Feb 2023 at 11:54, Alyosha Shevandin
wrote:
>
> Thank you for your answer. I belive that 'owner' parameter is initialized: 1)
> without --bios parameter the code does not crash; 2) I check the the owner
> parameter before;
> Here is the fragment of my code:
>
> static void
On Tue, 14 Feb 2023 at 10:40, Alyosha Shevandin
wrote:
>
> I wonder if there is any other way to build emulation for the custom SoC
> except using QEMU C API? I mean, the C API the one, that is used in a lot of
> examples under /hw folder. The other way – the high level abstractions –
> based:
On Tue, 14 Feb 2023 at 11:03, Alyosha Shevandin
wrote:
>
>
> I would appreciate any clue about the crash.
>
> When I start my custom SoC emulation and the –bios command line parameter us
> presented, the QEMU processes crashes before the custom code even tries to
> load the firmware. It crashes
On Mon, 30 Jan 2023 at 06:53, Jiatong Shen wrote:
>
> Hello community experts,
>
>I am facing an issue to migrate a virtual machine from qemu 2.11 to qemu
> 4.2 node. The command using on src node is
>
> qemu-system-aarch64 -M virt -vnc :2 -rtc base=utc,driftfix=slew -smp 2 -m
> 4096 -cpu
On Mon, 23 Jan 2023 at 20:08, Thomas Huth wrote:
>
> On 23/01/2023 19.07, Matwey V. Kornilov wrote:
> > пн, 23 янв. 2023 г. в 21:02, Peter Maydell :
> >>
> >> On Mon, 23 Jan 2023 at 17:36, Matwey V. Kornilov
> >> wrote:
> >>> I am
On Mon, 23 Jan 2023 at 18:07, Matwey V. Kornilov
wrote:
>
> пн, 23 янв. 2023 г. в 21:02, Peter Maydell :
> >
> > On Mon, 23 Jan 2023 at 17:36, Matwey V. Kornilov
> > wrote:
> > > I am playing with qemu-system-avr currently.
> > > I see tha
On Mon, 23 Jan 2023 at 17:36, Matwey V. Kornilov
wrote:
> I am playing with qemu-system-avr currently.
> I see that there is an "empty machine" called "none" in
>
> qemu-system-avr -M help
>
> list.
>
> Is it a real thing? I am failed to run any code with "none" machine.
It is mostly for
On Thu, 5 Jan 2023 at 22:47, Eskowitz, Michael
wrote:
> I hope this is a simple question. I have been unable to find
> documentation related to interrupt behavior on the UART of the
> mps2_an521. Application note AN521 does not go into great depth
> in this area and I am hoping that someone can
On Tue, 20 Dec 2022 at 07:26, Paul Menzel wrote:
>
> Dear mailing list administrators.
>
>
> Am 19.12.22 um 21:59 schrieb Helge Konetzka:
>
> […]
>
> > I already wrote an answer on qemu-devel list
> > (https://lists.gnu.org/archive/html/qemu-devel/2022-12/msg02445.html).
>
> That message did not
On Mon, 19 Dec 2022 at 16:20, wrote:> I
noticed that many questions in the qemu-discus maling list are not
answered here? Doesn't anyone use qemu on Windows and doesn't know the
command how to start qemu-system-x86_64.exe with sound support? Where
are the developers of Qemu? it would be very nice
On Wed, 23 Nov 2022 at 06:12, Jiatong Shen wrote:
>I am trying to investigate bug fixes and new features for qemu from 4.2. I
> noticed qemu's commits are reviewed through email, but right now the only way
> that I found to connect commits to a particular email is through googling. So
> my
On Fri, 28 Oct 2022 at 07:57, Antonio Apostoliu
wrote:
>
> Hello
>
>I use Qemu 6.2.0 on Windows 10.
> I launch qemu with this script:
> ..\qemu\qemu-system-x86_64.exe -m 512 -smp 1 -hda images/d.qcow2 ^
> -nic user,tftp=trf,hostfwd=tcp:127.0.0.1:-:22
>
>
> Before run script I
On Wed, 5 Oct 2022 at 23:53, wrote:
>
> There are no issues with "offline" snapshots with qemu-img with the
> guest powered off.
>
> However, with "online" snapshots through QEMU monitor I get this:
>
> Error: Device 'pflash1' is writable but does not support snapshots
>
> Indeed, it's trying to
On Mon, 3 Oct 2022 at 11:25, Alex Bennée wrote:
>
>
> Peter Maydell writes:
>
> > On Mon, 3 Oct 2022 at 10:09, Alex Bennée wrote:
> >>
> >>
> >> Thomas Huth writes:
> >>
> >> > On 29/09/2022 04.32, Jason Wang wrote:
> >>
On Mon, 3 Oct 2022 at 10:09, Alex Bennée wrote:
>
>
> Thomas Huth writes:
>
> > On 29/09/2022 04.32, Jason Wang wrote:
> >> On Thu, Sep 29, 2022 at 1:06 AM Philippe Mathieu-Daudé
> >> wrote:
> >>> Jason, Marc-André, could we improve the buildsys check or display
> >>> a more helpful
On Sun, 2 Oct 2022 at 04:41, Tavis Ormandy wrote:
> Hello, I'm trying to use qemu-i386 on aarch64 to run an old binary and
> running into a crash.
>
> I've minimized it down to %esp getting corrupted after return from a
> signal handler return, but this seems so trivial that I must be doing
>
On Wed, 28 Sept 2022 at 18:27, Victor Martins wrote:
> Peter Maydell escreveu no dia terça, 27/09/2022
> à(s) 16:52:
>>
>> > Any way, I have no problem use the -machine virt. My problem is know
>> > how I can map my RISC-V SoC in the FPGA (like have control o
On Tue, 27 Sept 2022 at 16:34, Victor Martins wrote:
> Peter Maydell escreveu no dia terça, 27/09/2022
> à(s) 10:27:
>>
>> What are you trying to achieve by removing the "-machine virt"
>> option?
> Thanks Peter, you gave me a great first lesson.
>
On Mon, 26 Sept 2022 at 20:39, Victor Martins wrote:
> And after I try use the dtb file and remove the virt board like this:
>
> $ qemu-system-riscv64 \
> -nographic \
> -dtb ./riscv64-virt.dtb \
> -kernel linux-5.19.1/arch/riscv/boot/Image \
> -append "root=/dev/vda ro
On Sat, 3 Sept 2022 at 02:30, Little Tree wrote:
>
> Hi,
>
> I have built a simple hello world program for aarch64 like this
>
> $aarch64-none-elf-gcc -c -march=armv8-a -g hello.c hello.o
> $aarch64-none-elf-gcc -specs=aem-ve.specs -Wl,-Map=linkmap.txt hello.o -o
> hello.axf
>
> Then I tried to
On Fri, 12 Aug 2022 at 15:41, Denis Krienbühl wrote:
>
> I’m not much further with my segfault, though I now know that the number of
> detaches likely does not matter and it seems to occur during the attach, not
> the detach part of the code.
>
> I adapted my change to be a bit more sane - I
On Tue, 9 Aug 2022 at 17:26, Denis Krienbühl wrote:
> On 9 Aug 2022, at 18:15, Peter Maydell wrote:
>> My wild guess is that there's a race condition somewhere such
>> that when you're doing this huge amount of detaches, very rarely
>> a disk is detached and deleted but
On Tue, 9 Aug 2022 at 16:37, Denis Krienbühl wrote:
> We are running a Ceph 15.2.16 cluster at work, connect VMs to it using
> librbd1 14.2.22, running on the QEMU 4.2 release by Ubuntu’s Cloud Archive
> (4.2-3ubuntu6.23~cloud0).
>
> A few of our VMs randomly trigger a segfault in
On Thu, 4 Aug 2022 at 13:51, Chan Kim wrote:
> Yes, you are right. I tried again with that -dtb option like this.
>
> qemu-system-aarch64 -machine
> ab21q,gic-version=max,secure=on,virtualization=true -cpu max -kernel
> u-boot-spl -m 8M -nographic -device loader,file=Image,addr=0x8020 -dtb
On Wed, 27 Jul 2022 at 18:45, Jayakrishna Vadayath
wrote:
> Yes I did profile it afterwards and found that the majority of time is being
> spent on loading the RAM.
> I'm running QEMU with "-m 1G" and I do see that there's close to 1 gigabyte
> of memory being loaded from the snapshot.
>
> In
On Tue, 26 Jul 2022 at 23:11, Jayakrishna Vadayath
wrote:
> I'm very new to QEMU and I'm still trying to figure my way out through the
> source code.
> Currently I'm using the QEMU snapshot restore mechanism and I've noticed that
> it usually takes close to 200 milliseconds to restore a small
On Thu, 21 Jul 2022 at 03:46, Jakob Bohm wrote:
> It would be a lot more helpful if your error message was explicit about
> which items were conflicting rather than demanding the full configuration
> from people affected. And don't fall for the temptation of printing out a
> list of potential
On Wed, 20 Jul 2022 at 13:14, Chan Kim wrote:
>
> Hi, Peter Maydell,
>
> Thank you for the advice.
> So I uncommented the stdio_in_use guard, and used this option
> (because the second uart will be used)
>
> -chardev null,mux=off,id=char0 -serial chardev:char0 -chardev
On Wed, 20 Jul 2022 at 11:27, Chan Kim wrote:
>
> Hello qemu experts,
>
> In my virtual machine I have two uart and I want to use the input/output in
> my host machine.
> For that I commented out these lines in qemu_chr_open_stdio function in
> chardev/char-stdio.c. (qemu-6.2.0)
>
> /*
> if
On Thu, 14 Jul 2022 at 20:43, James Miller wrote:
> I would think the -nographic switch would be the one to get me
> command-line access to the guest OS, since the man page says "Normally, if
> QEMU is compiled with graphical window support, it displays output such as
> guest graphics, guest
1 - 100 of 680 matches
Mail list logo
