> Peter Maydell hat am 18. März 2017 um 23:22
> geschrieben:
>
> This is expected, because you're creating two devices.
> Device 1 is the one that's created by calling
> mydevice_init() here in the board code.
> Device 2 is created because you say "-device mydevice"
> on the command line.
I see
On 18 March 2017 at 21:15, Marc Bommert wrote:
> I ran into some behaviour I don't understand and which may be a qemu problem
> but which may also be my fault, since I haven't investigated much on QOM so
> far.
> I am currently writing a NIC sysbus device based on the structure of
> hw/net/smc9
Hello development,
I ran into some behaviour I don't understand and which may be a qemu problem
but which may also be my fault, since I haven't investigated much on QOM so far.
I am currently writing a NIC sysbus device based on the structure of
hw/net/smc91c111.c
qemu is invoked as:
$ qemu-
Hello,
I'm not sure I'm on the right list to post, sorry about that, but I
tried on IRC and got no answer.
I'm working on a low level piece of system, which has to change PSR
values on ARM.
I use qemu-system-arm v 2.0.0, with the command : qemu-system-arm
-nographic -s -S -m 1024 -M vexpress-a9
Do you think your problems are related to either of the following Ubuntu
bugs?
https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/144368
https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/154960
Joe
On 10/22/07, Christian Fontana <[EMAIL PROTECTED]> wrote:
>
> Hello.
>
> I'm using QEMU to expi
Hello.
I'm using QEMU to expirement configuration, sw,... so I've create some images
with different linux distros.
Yesterday I've upgraded my Kubuntu from 7.04 to 7.10 and so also qemu was
upgraded from 0.8.2 to 0.9.0. What I discovered is that some VM I've created
(in particular suse) now are
