so},id=cdrom,if=none,media=cdrom" \
I've also discovered that the installer is just to slow to bear without KVM
:-)
On Mon, Jan 14, 2019 at 4:41 PM Peter Maydell
wrote:
> On Mon, 14 Jan 2019 at 16:15, Ciro Santilli
> wrote:
> > I just wonder, is it really possible that a
On Mon, Jan 14, 2019 at 5:11 PM Dennis Clarke wrote:
> On 1/14/19 11:41 AM, Peter Maydell wrote:
> > On Mon, 14 Jan 2019 at 16:15, Ciro Santilli
> wrote:
> >> I just wonder, is it really possible that a system misconfiguration
> >> prevented the ISO from being re
On Mon, Jan 14, 2019 at 10:46 AM Peter Maydell
wrote:
> On Mon, 14 Jan 2019 at 10:18, Ciro Santilli
> wrote:
> >
> >
> https://askubuntu.com/questions/797599/how-to-run-ubuntu-16-04-arm-in-qemu
> >
> > I wanted to test out the ISO from:
> https://www.ubuntu
https://askubuntu.com/questions/797599/how-to-run-ubuntu-16-04-arm-in-qemu
I wanted to test out the ISO from:
https://www.ubuntu.com/download/server/arm on QEMU, but haven't managed to
run it, has anyone ever done that?
I've tried the setup below from Ubuntu 18.04, and GRUB does start, then the
i
https://superuser.com/questions/1376944/can-qemu-boot-linux-from-vmlinux-instead-of-bzimage
I've been using QEMU 3.0.0 happily with -kernel bzImage from Linux v4.19.
However, now I have another simulator (gem5) that boots from vmlinux,
it would be convenient if I could boot both from the exact sa
https://superuser.com/questions/1373226/how-to-redirect-qemu-serial-output-to-both-a-file-and-the-terminal-or-a-port
I would like to be able to both interact with the system via the
command line, but also get the output to a file at the same time.
If I do:
qemu-sysem-x86_64 -serial stdio |&
https://unix.stackexchange.com/questions/479085/can-qemu-m-virt-on-arm-aarch64-have-multiple-serial-ttys-like-such-as-pl011-t
I was playing around with TTYs, and for `qemu-system-x86_64 -M pc`,
whenever I pass the `-serial` option it crates a new TTY and I can
attach a serial like `ttyS0` and `tty
I think they are not supported since I found no reference in the GDB
XMLs: https://github.com/qemu/qemu/tree/v3.0.0/gdb-xml is that
correct?
Is there any major blocker, or anyone already working on it?
I'm slightly tempted, would be a big boost for SVE usability.
On Sat, Aug 11, 2018 at 8:17 AM, Auger Eric wrote:
> Hi Ciro, Nerijus,
>
> On 08/11/2018 01:43 AM, Ciro Santilli wrote:
> > Bisected to 17ec075a651a3f9613429c2d97018fce459ed943 hw/arm/virt: Use
> > 256MB ECAM region by default
> >
> > @Eric: do you know
eri...@users.sourceforge.net> wrote:
> On Thu, 9 Aug 2018 22:59:27 +0100 Ciro Santilli
> wrote:
>
> > Analogous commands work for x86_64 and aarch64
> >
> > All worked on v2.12.0 with the same images.
>
> > Kernel boot error message:
> > VFS: Cannot open root device
Analogous commands work for x86_64 and aarch64
All worked on v2.12.0 with the same images.
Do I have to use a new config option for the virtio support or is it a bug?
Ubuntu 18.04 host, default build:
./configure --target-list=x86_64-softmmu,arm-softmmu,aarch64-softmmu
then try to ru
OK, I rediscovered: https://bugs.launchpad.net/qemu/+bug/1528239
On Fri, Jul 13, 2018 at 10:32 AM, Ciro Santilli
wrote:
> https://stackoverflow.com/questions/51310756/how-to-gdb-
> step-debug-a-dynamically-linked-executable-in-qemu-user-mode
>
> For example for ARM, if I compile sta
https://stackoverflow.com/questions/51310756/how-to-gdb-step-debug-a-dynamically-linked-executable-in-qemu-user-mode
For example for ARM, if I compile statically, all works fine:
sudo apt-get install gdb-multiarch gcc-arm-linux-gnueabihf qemu-user
printf '
#include
#include
On Thu, May 24, 2018 at 10:08 AM, Peter Maydell
wrote:
> On 23 May 2018 at 20:28, Ciro Santilli wrote:
>> On Mon, May 21, 2018 at 9:32 AM, Peter Maydell
>> wrote:
>>> On 21 May 2018 at 00:26, Ciro Santilli wrote:
>>>> Do you know which options I m
On Mon, May 21, 2018 at 9:32 AM, Peter Maydell wrote:
> On 21 May 2018 at 00:26, Ciro Santilli wrote:
>> Do you know which options I might need to add to my QEMU -M virt
>> command to make it open a graphic window (and hopefully show the
>> CONFIG_LOGO penguin)?
>
On Sun, May 20, 2018 at 2:06 PM, Peter Maydell wrote:
> On 20 May 2018 at 11:19, Ciro Santilli wrote:
>> Is there a fundamental technical reason, or just was not worth the trouble?
>>
>> The wiki says https://wiki.qemu.org/Documentation/Platforms/ARM
>>
>>> T
Is there a fundamental technical reason, or just was not worth the trouble?
The wiki says https://wiki.qemu.org/Documentation/Platforms/ARM
> The only thing it [virt] doesn't have is graphics
and the graphic window indeed does not show on -M virt.
The dream of arm laptops lives.
On Wed, Apr 11, 2018 at 2:11 PM, Peter Maydell wrote:
> On 11 April 2018 at 13:33, Ciro Santilli wrote:
>> There is now just one minor quirk which I can live with: for arm and
>> aarch64, if I hit Ctrl + C while the kernel is booting and spitting
>> out dmesg messages, then
On Tue, Apr 10, 2018 at 9:54 PM, Thomas Huth wrote:
> On 10.04.2018 16:06, Ciro Santilli wrote:
>> On Tue, Apr 10, 2018 at 6:27 AM, Thomas Huth wrote:
>>> On 10.04.2018 02:10, Ciro Santilli wrote:
>>>> On Mon, Apr 9, 2018 at 1:33 PM, Thomas Huth wrote:
>>&g
I've managed to prevent the trace generation with:
-T "pr_manager_run,file=/dev/null"
I add a valid event "pr_manager_run" to prevent the warning, and
redirect to /dev/null
Maybe someone will have a more elegant solution.
On Tue, Apr 10, 2018 at 10:46 PM, Ciro Sant
generates a trace file trace-. Trace options can be
controlled with:
./qemu-img -T ... convert ...
On Tue, Apr 10, 2018 at 10:26 PM, Ciro Santilli wrote:
> I noticed that qemu-img was producing some trace files when I compiled
> with --enable-trace-backends=simple.
>
> What is
I noticed that qemu-img was producing some trace files when I compiled
with --enable-trace-backends=simple.
What is the point of tracing qemu-img?
I thought trace events were supposed to represent execution related
things, like "an instruction got executed" and so on.
I also noticed that qemu-im
On Tue, Apr 10, 2018 at 6:27 AM, Thomas Huth wrote:
> On 10.04.2018 02:10, Ciro Santilli wrote:
>> On Mon, Apr 9, 2018 at 1:33 PM, Thomas Huth wrote:
>>> On 08.04.2018 12:39, Ciro Santilli wrote:
> [...]
>>>> Is there a way to both keep my `Ctrl-C` and `-monit
On Mon, Apr 9, 2018 at 1:33 PM, Thomas Huth wrote:
> On 08.04.2018 12:39, Ciro Santilli wrote:
>> https://stackoverflow.com/questions/49716931/how-to-run-qemu-with-nographic-and-monitor-but-still-be-able-to-send-ctrlc-to
>>
>> I have just found out that if you run QEMU wit
https://stackoverflow.com/questions/49716931/how-to-run-qemu-with-nographic-and-monitor-but-still-be-able-to-send-ctrlc-to
I have just found out that if you run QEMU with `-monitor
telnet::45454,server,nowait -nographic`, then Ctrl-C kills the QEMU VM
instead of generating SIGINT on the guest:
htt
25 matches
Mail list logo
