While QEMU does indeed works for x86 Windows, current QEMU's m68k architecture
does not included that specific Motorola chip.
El 23/05/2010, a las 05:28, hadi motamedi escribió:
> Dear All
> Do you have qemu emulator for Motorola 68360 emulation on x86 Windows
> platform?
> Thank you in advance
> >>While QEMU does indeed works for x86 Windows, current QEMU's m68k
architecture does not included that specific Motorola chip.
Thank you for your reply. Can you please let me know which Motorola chips
are being currently supported?
On 05/21/2010 12:10 PM, Paolo Bonzini wrote:
diff --git a/roms/seabios b/roms/seabios
index 7d09d0e..8f469b9 16
--- a/roms/seabios
+++ b/roms/seabios
@@ -1 +1 @@
-Subproject commit 7d09d0e3ba11310e973d4302c7fcc3fc2184e04c
+Subproject commit 8f469b9676127ba6bb52609d89ec774e61db0ee1
This was
Blue Swirl wrote:
> On Sat, May 22, 2010 at 8:18 AM, Jan Kiszka wrote:
>> From: Jan Kiszka
>>
>> Will be used by QBuffer.
>>
>> Signed-off-by: Jan Kiszka
>> ---
>> Makefile.objs |2 +-
>> base64.c | 202
>> +
>> base64.h |
Blue Swirl wrote:
> On Sat, May 22, 2010 at 8:17 AM, Jan Kiszka wrote:
>> Here is version 2 of the device_show patch series. It currently has some
>> dependencies on recently posted doc changes / enhancements, namely:
>> - http://thread.gmane.org/gmane.comp.emulators.qemu/70673
>> ([PATCH v3 0/
Avi Kivity wrote:
> On 05/22/2010 11:18 AM, Jan Kiszka wrote:
>> From: Jan Kiszka
>>
>> This introduces device_show, a monitor command that saves the vmstate of
>> a qdev device and visualizes it. QMP is also supported. Buffers are cut
>> after 16 byte by default, but the full content can be reques
On Thu, May 20, 2010 at 11:02 PM, Yehuda Sadeh Weinraub
wrote:
> On Thu, May 20, 2010 at 1:31 PM, Blue Swirl wrote:
>> On Wed, May 19, 2010 at 7:22 PM, Christian Brunner wrote:
>>> The attached patch is a block driver for the distributed file system
>>> Ceph (http://ceph.newdream.net/). This dri
From: Jan Kiszka
Unless we are running in full-screen mode, QEMU's SDL window should not
disable the host's screensaver. The user can still change this behaviour
by setting the environment variable SDL_VIDEO_ALLOW_SCREENSAVER as
desired.
Signed-off-by: Jan Kiszka
---
Cool, thanks for digging o
On 05/23/2010 10:57 AM, Jan Kiszka wrote:
Avi Kivity wrote:
On 05/22/2010 11:18 AM, Jan Kiszka wrote:
From: Jan Kiszka
This introduces device_show, a monitor command that saves the vmstate of
a qdev device and visualizes it. QMP is also supported. Buffers are cut
after 16 byte by def
On 05/23/2010 10:55 AM, Jan Kiszka wrote:
+/*
+ * Convert string 'src' of length 'srclen' from base64 to binary form,
+ * saving the result in 'dest'. The size of the destination buffer must be at
+ * least srclen * 3 / 4.
+ *
+ * Returns 0 on success, -1 on conversion error.
+ */
+int base64_dec
Am 18.05.2010 um 15:51 schrieb Alexander Graf:
> Peter Lieven wrote:
>> Alexander Graf wrote:
>>> Peter Lieven wrote:
>>>
we are running on intel xeons here:
>>>
>>> That might be the reason. Does it break when passing -no-kvm?
>>>
>>>
processor: 0
vendor_id: Genu
Hi,
after live migrating ubuntu 9.10 server (2.6.31-14-server) and suse linux 10.1
(2.6.16.13-4-smp)
it happens sometimes that the guest runs into irq problems. i mention these 2
guest oss
since i have seen the error there. there are likely others around with the same
problem.
on the host i ru
Avi Kivity wrote:
> On 05/23/2010 10:57 AM, Jan Kiszka wrote:
>> Avi Kivity wrote:
>>
>>> On 05/22/2010 11:18 AM, Jan Kiszka wrote:
>>>
From: Jan Kiszka
This introduces device_show, a monitor command that saves the
vmstate of
a qdev device and visualizes it. QMP is
Avi Kivity wrote:
> On 05/23/2010 10:55 AM, Jan Kiszka wrote:
+/*
+ * Convert string 'src' of length 'srclen' from base64 to binary form,
+ * saving the result in 'dest'. The size of the destination buffer
must be at
+ * least srclen * 3 / 4.
+ *
+ * Returns 0 on
Public bug reported:
After live migrating ubuntu 9.10 server (2.6.31-14-server) and suse linux 10.1
(2.6.16.13-4-smp)
it happens sometimes that the guest runs into irq problems. i mention these 2
guest oss
since i have seen the error there. there are likely others around with the same
problem.
Am 19.05.2010 um 10:18 schrieb Peter Lieven:
> Kevin Wolf wrote:
>> Am 19.05.2010 09:29, schrieb Christoph Hellwig:
>>
>>> On Tue, May 18, 2010 at 03:22:36PM +0200, Kevin Wolf wrote:
>>>
I think it's stuck here in an endless loop:
while (laiocb->ret == -EINPROGRESS)
23.05.2010 13:55, Peter Lieven wrote:
Hi,
after live migrating ubuntu 9.10 server (2.6.31-14-server) and suse linux 10.1
(2.6.16.13-4-smp)
it happens sometimes that the guest runs into irq problems. i mention these 2
guest oss
since i have seen the error there. there are likely others around w
Public bug reported:
I recently had a 0.12.4 qemu-kvm with a debian lenny guest which
occasionally paused.
There was no memory exhaustion as suggested earlier.
qemu-kvm send the following output::
VM internal error. Suberror: 1
rax 0100 rbx 880017585bc0 rcx 7f84c6d5b000 rdx
On 05/23/2010 01:03 PM, Jan Kiszka wrote:
Can your elaborate what precisely is ambiguous?
Can't the user choose the unique ID so that it aliases an unrelated
qtree path?
True. I'll swap the search order and document this. Qtree paths should
always rule.
Well, I guess the u
Am 23.05.2010 um 12:38 schrieb Michael Tokarev:
> 23.05.2010 13:55, Peter Lieven wrote:
>> Hi,
>>
>> after live migrating ubuntu 9.10 server (2.6.31-14-server) and suse linux
>> 10.1 (2.6.16.13-4-smp)
>> it happens sometimes that the guest runs into irq problems. i mention these
>> 2 guest oss
Public bug reported:
i would like to debug a problem that I encountered some time ago with opensuse
11.2 and also
with Ubuntu (karmic/lucid).
If I run an opensuse guest 64-bit and do not touch the clocksource settings the
guest almost
everytime hangs after live migration at:
(gdb) thread apply
And here is v3. Dependencies remained, the changes are:
- disabled device_show for QMP use (due to protocol instability)
- reordered device tree path search: user-assigned ID comes last now
- added vmstate version-id to device_show output
- base64 cleanups according to review comments
- fixed
From: Jan Kiszka
As long as we allow /dev.1 as shortcut for /dev1/bus1, we also have to
make sure that /dev1/dev2 works for /dev1/bus1/dev2/bus2 - as long as
there is only one child bus per device.
Signed-off-by: Jan Kiszka
---
docs/qdev-device-use.txt |4
hw/qdev.c|
From: Jan Kiszka
Ported commands that are marked 'user_only' will not be considered for
QMP monitor sessions. This allows to implement new commands that do not
(yet) provide a sufficiently stable interface for QMP use (e.g.
device_show).
Signed-off-by: Jan Kiszka
---
monitor.c | 13 +
From: Jan Kiszka
Allow to specify the device to be removed via device_del not only by ID
but also by its full or abbreviated qtree path. For this purpose,
qdev_find is introduced which combines walking the qtree with searching
for device IDs if required.
Signed-off-by: Jan Kiszka
---
hw/qdev.c
From: Jan Kiszka
This reserves JSON objects that contain the key '__class__' for QMP-specific
complex objects. First user will be the buffer class.
Signed-off-by: Jan Kiszka
---
QMP/qmp-spec.txt | 16 +---
1 files changed, 13 insertions(+), 3 deletions(-)
diff --git a/QMP/qmp-sp
From: Jan Kiszka
Extend qbus_find_dev to allow addressing of devices without an unique id
via an optional per-bus instance number. The new formats are
'driver.instance' and 'alias.instance'.
Signed-off-by: Jan Kiszka
---
docs/qdev-device-use.txt | 14 +-
hw/qdev.c
From: Jan Kiszka
Cosmetic change to align the instance number assignment with bus
ordering. The current ordering due to QLIST_INSERT_HEAD is a bit
annoying when you dump the qtree or address devices via
'driver.instance'.
Signed-off-by: Jan Kiszka
---
hw/acpi_piix4.c |2 +-
hw/i2c.c
From: Jan Kiszka
As the user may specify ambiguous device IDs, let's search for their
official names first before considering the user-supplied identifiers.
Signed-off-by: Jan Kiszka
---
docs/qdev-device-use.txt |4 +++-
hw/qdev.c| 18 +-
2 files changed,
From: Jan Kiszka
Simplifies the usage.
Signed-off-by: Jan Kiszka
---
hw/qdev.c | 22 ++
1 files changed, 10 insertions(+), 12 deletions(-)
diff --git a/hw/qdev.c b/hw/qdev.c
index df945ed..e07ec98 100644
--- a/hw/qdev.c
+++ b/hw/qdev.c
@@ -492,6 +492,9 @@ static void qbu
From: Jan Kiszka
This demonstrates the conversion of QMP buffer objects and does some
minimalistic pretty-printing.
Signed-off-by: Jan Kiszka
---
QMP/qmp.py | 25 +++--
1 files changed, 23 insertions(+), 2 deletions(-)
diff --git a/QMP/qmp.py b/QMP/qmp.py
index 4062f84..
From: Jan Kiszka
Implement monitor command line completion for device tree paths. The
first user is device_del.
Signed-off-by: Jan Kiszka
---
hw/qdev.c | 50 ++--
hw/qdev.h |2 +
monitor.c | 85 ++
From: Jan Kiszka
Will be used by QBuffer.
Signed-off-by: Jan Kiszka
---
Makefile.objs |2 +-
base64.c | 202 +
base64.h | 19 ++
3 files changed, 222 insertions(+), 1 deletions(-)
create mode 100644 base64.c
create
From: Jan Kiszka
As sending "qmp_capabilities" on session start became mandatory, both
python examples were broken.
Signed-off-by: Jan Kiszka
---
QMP/qmp-shell |1 +
QMP/vm-info |1 +
2 files changed, 2 insertions(+), 0 deletions(-)
diff --git a/QMP/qmp-shell b/QMP/qmp-shell
index f
From: Jan Kiszka
This simply forwards the result of the internal vsnprintf to the callers
of monitor_printf and monitor_vprintf. When invoked over a QMP session
or in absence of an active monitor, -1 is returned.
Signed-off-by: Jan Kiszka
---
monitor.c | 23 +++
monitor
From: Jan Kiszka
Remove the arbitrary limitation of 1024 characters per return string and
read complete lines instead. Required for device_show.
Signed-off-by: Jan Kiszka
---
QMP/qmp.py |6 +-
1 files changed, 5 insertions(+), 1 deletions(-)
diff --git a/QMP/qmp.py b/QMP/qmp.py
index
From: Jan Kiszka
This introduces device_show, a monitor command that saves the vmstate of
a qdev device and visualizes it. Buffers are cut after 16 byte by
default, but the full content can be requested via '-f'. To pretty-print
sub-arrays, vmstate is extended to store the start index name. A new
From: Jan Kiszka
Signed-off-by: Jan Kiszka
---
Makefile |2 ++
1 files changed, 2 insertions(+), 0 deletions(-)
diff --git a/Makefile b/Makefile
index 3a8a311..1514433 100644
--- a/Makefile
+++ b/Makefile
@@ -144,6 +144,8 @@ qemu-io$(EXESUF): qemu-io.o cmd.o qemu-tool.o qemu-error.o
$(blo
On 05/20/2010 01:28 AM, Jan Kiszka wrote:
From: Jan Kiszka
Guest debugging under KVM is currently broken once io-threads are
enabled. Easily fixable by switching the fake on_vcpu to the real
run_on_cpu implementation.
Applied uq/master, thanks.
--
error compiling committee.c: too many arg
From: Jan Kiszka
This introduces a buffer object for use with QMP. As a buffer is not
natively encodable in JSON, we encode it as a base64 string and
encapsulate the result in the new QMP object class "buffer".
The first use case for this is pushing the content of buffers that are
part of a devi
On 05/21/2010 12:29 AM, Anthony Liguori wrote:
I'd be more interested in enabling people to build these types of
storage systems without touching qemu.
Both sheepdog and ceph ultimately transmit I/O over a socket to a
central daemon, right?
That incurs an extra copy.
So could we not stan
Le dimanche 23 mai 2010 à 08:47 +0100, hadi motamedi a écrit :
>
>
>
>
> >>While QEMU does indeed works for x86 Windows, current QEMU's m68k
> architecture does not included that specific Motorola chip.
> Thank you for your reply. Can you please let me know which Motorola
> chip
Rearrange code so that in the end, mc146818 can be compiled once.
The other patches should be safe, but I'm not so sure about coalesced
irq handling changes in 3/4.
Also, is the periodic timer optimization (removed in 1/4) very important?
Blue Swirl (4):
mc146818: move hpet handling to pc.c
Move hpet_in_legacy_mode check from mc146818.c to pc.c. Remove
the optimization where the periodic timer is disabled if
hpet is in legacy mode.
Signed-off-by: Blue Swirl
---
hw/mc146818rtc.c | 37 +++--
hw/mc146818rtc.h |2 ++
hw/pc.c | 32 +++
Signed-off-by: Blue Swirl
---
hw/hpet.c | 68 +--
hw/hpet_emul.h |4 +-
hw/pc.c|8 --
hw/pc.h|3 +-
hw/pc_piix.c |3 +-
5 files changed, 47 insertions(+), 39 deletions(-)
diff --git a/hw/hpet.c b/hw/
A side effect is that coalesced irq handling is extended to seconds
alarm and irq reinjection.
Signed-off-by: Blue Swirl
---
hw/mc146818rtc.c | 20 ++--
hw/mc146818rtc.h |1 +
hw/pc.c |6 ++
hw/pc.h |1 +
4 files changed, 18 insertions(+), 10 d
8 compilations less for the full build.
Signed-off-by: Blue Swirl
---
Makefile.objs|1 +
Makefile.target |7 +++
default-configs/i386-softmmu.mak |1 +
default-configs/mips-softmmu.mak |1 +
default-configs/mips64-softmmu.m
qemu-system-m68k -cpu ?
El 23/05/2010, a las 08:47, hadi motamedi escribió:
>
>
>
> >>While QEMU does indeed works for x86 Windows, current QEMU's m68k
> >>architecture does not included that specific Motorola chip.
> Thank you for your reply. Can you please let me know which Motorola chips a
On Thu, May 20, 2010 at 02:38:16PM +0930, Rusty Russell wrote:
> On Thu, 20 May 2010 02:31:50 pm Rusty Russell wrote:
> > On Wed, 19 May 2010 05:36:42 pm Avi Kivity wrote:
> > > > Note that this is a exclusive->shared->exclusive bounce only, too.
> > > >
> > >
> > > A bounce is a bounce.
> >
Blue Swirl wrote:
> Move hpet_in_legacy_mode check from mc146818.c to pc.c. Remove
> the optimization where the periodic timer is disabled if
> hpet is in legacy mode.
>
> Signed-off-by: Blue Swirl
> ---
> hw/mc146818rtc.c | 37 +++--
> hw/mc146818rtc.h |2 +
On 05/23/2010 06:31 PM, Michael S. Tsirkin wrote:
On Thu, May 20, 2010 at 02:38:16PM +0930, Rusty Russell wrote:
On Thu, 20 May 2010 02:31:50 pm Rusty Russell wrote:
On Wed, 19 May 2010 05:36:42 pm Avi Kivity wrote:
Note that this is a exclusive->shared->exclusive bounce only
Blue Swirl wrote:
> Signed-off-by: Blue Swirl
> ---
> hw/hpet.c | 68 +--
> hw/hpet_emul.h |4 +-
> hw/pc.c|8 --
> hw/pc.h|3 +-
> hw/pc_piix.c |3 +-
> 5 files changed, 47 insertions(+), 39 deletion
Stefan Hajnoczi wrote:
> The following patches against qemu.git allow static trace events to be
> declared
> in QEMU. Trace events use a lightweight syntax and are independent of the
> backend tracing system (e.g. LTTng UST).
>
> Supported backends are:
> * my trivial tracer ("simple")
> * LTT
Stefan Hajnoczi wrote:
> This patch adds LTTng Userspace Tracer (UST) backend support. The UST
> system requires no kernel support but libust and liburcu must be
> installed.
>
> $ ./configure --trace-backend ust
> $ make
>
> Start the UST daemon:
> $ ustd &
>
> List available tracepoints and e
On Sun, May 23, 2010 at 06:41:33PM +0300, Avi Kivity wrote:
> On 05/23/2010 06:31 PM, Michael S. Tsirkin wrote:
>> On Thu, May 20, 2010 at 02:38:16PM +0930, Rusty Russell wrote:
>>
>>> On Thu, 20 May 2010 02:31:50 pm Rusty Russell wrote:
>>>
On Wed, 19 May 2010 05:36:42 pm Avi Kivity
On Thu, May 20, 2010 at 02:38:16PM +0930, Rusty Russell wrote:
> On Thu, 20 May 2010 02:31:50 pm Rusty Russell wrote:
> > On Wed, 19 May 2010 05:36:42 pm Avi Kivity wrote:
> > > > Note that this is a exclusive->shared->exclusive bounce only, too.
> > > >
> > >
> > > A bounce is a bounce.
> >
On Sun, May 23, 2010 at 3:40 PM, Jan Kiszka wrote:
> Blue Swirl wrote:
>> Move hpet_in_legacy_mode check from mc146818.c to pc.c. Remove
>> the optimization where the periodic timer is disabled if
>> hpet is in legacy mode.
>>
>> Signed-off-by: Blue Swirl
>> ---
>> hw/mc146818rtc.c | 37 ++
On 05/23/2010 06:51 PM, Michael S. Tsirkin wrote:
So locked version seems to be faster than unlocked,
and share/unshare not to matter?
May be due to the processor using the LOCK operation as a hint to
reserve the cacheline for a bit.
Maybe we should use atomics on index then?
On Sun, May 23, 2010 at 3:40 PM, Jan Kiszka wrote:
> Blue Swirl wrote:
>> Signed-off-by: Blue Swirl
>> ---
>> hw/hpet.c | 68
>> +--
>> hw/hpet_emul.h | 4 +-
>> hw/pc.c | 8 --
>> hw/pc.h | 3 +-
>> hw/pc_pii
On Sun, May 23, 2010 at 07:03:10PM +0300, Avi Kivity wrote:
> On 05/23/2010 06:51 PM, Michael S. Tsirkin wrote:
>>>
So locked version seems to be faster than unlocked,
and share/unshare not to matter?
>>> May be due to the processor using the LOCK operation as a hint to
On Sun, May 23, 2010 at 07:03:10PM +0300, Avi Kivity wrote:
> On 05/23/2010 06:51 PM, Michael S. Tsirkin wrote:
>>>
So locked version seems to be faster than unlocked,
and share/unshare not to matter?
>>> May be due to the processor using the LOCK operation as a hint to
Hi,
The overall plan is to add a new flag, IO_MEM_BSWAP, which triggers
byte swapping inside CPU load/store functions. Convert all PCI devices
to register their memory areas via the PCI host. Then the big endian
PCI hosts enable IO_MEM_BSWAP for all registered regions,
simultaneously all PCI devic
Convert also APB to use the registration so that
we can remove mem_base.
Signed-off-by: Blue Swirl
---
hw/apb_pci.c | 23 -
hw/pci.c | 64 ++---
hw/pci.h |9 +++-
3 files changed, 68 insertions(+), 28 del
BROKEN
Signed-off-by: Blue Swirl
---
cpu-common.h |3 +-
softmmu_template.h | 69 ++--
2 files changed, 63 insertions(+), 9 deletions(-)
diff --git a/cpu-common.h b/cpu-common.h
index b24cecc..f96cea0 100644
--- a/cpu-common.h
+++ b/cp
Signed-off-by: Blue Swirl
---
hw/cirrus_vga.c | 12 ++--
hw/e1000.c|2 +-
hw/eepro100.c |2 +-
hw/isa.h |1 +
hw/isa_mmio.c | 18 --
hw/lsi53c895a.c |4 ++--
hw/macio.c| 24
hw/msix.c
Signed-off-by: Blue Swirl
---
hw/apb_pci.c |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/hw/apb_pci.c b/hw/apb_pci.c
index fb23397..cfa198c 100644
--- a/hw/apb_pci.c
+++ b/hw/apb_pci.c
@@ -323,7 +323,7 @@ static void apb_register_mem(void *opaque,
pcibus_t addr, pcibus
From: Laurent Vivier
As it is done for qemu-system with "-cpu ?", when cpu_list_id() is missing
for a target, call cpu_list() instead.
Signed-off-by: Laurent Vivier
---
linux-user/main.c |2 ++
1 files changed, 2 insertions(+), 0 deletions(-)
diff --git a/linux-user/main.c b/linux-user/ma
On Sun, May 23, 2010 at 12:59 AM, Blue Swirl wrote:
> On Thu, May 20, 2010 at 11:02 PM, Yehuda Sadeh Weinraub
> wrote:
>> On Thu, May 20, 2010 at 1:31 PM, Blue Swirl wrote:
>>> On Wed, May 19, 2010 at 7:22 PM, Christian Brunner wrote:
The attached patch is a block driver for the distribute
On Wed, May 19, 2010 at 07:31:29PM -, Anthony Liguori wrote:
> ** Changed in: qemu
>Status: New => Confirmed
>
> --
> Windows 98 doesn't detect mouse on qemu and SeaBIOS.
> https://bugs.launchpad.net/bugs/521994
> You received this bug notification because you are a member of qemu-
>
Non-migrated memory is useful for devices that do not want to take memory
region data with them on migration.
As suggested by Avi, an alternative approach could add a "flags" parameter to
cpu_register_physical_memory() rather than explicityly call
cpu_mark_pages_no_migrate(). However, having a se
The phys_ram_dirty array consists of 8-bit values for storing 3 dirty bits.
Change to more generic phys_ram_flags and use lower 4-bits for dirty status and
leave upper 4 for other uses of marking memory pages.
One potential use for upper bits is to mark certain device pages to not be
migrated.
So
At Fri, 21 May 2010 13:40:31 +0200,
Kevin Wolf wrote:
>
> Am 20.05.2010 07:36, schrieb MORITA Kazutaka:
> > This patch enables protocol drivers to use their create options which
> > are not supported by the format. For example, protcol drivers can use
> > a backing_file option with raw format.
>
At Fri, 21 May 2010 18:57:36 +0200,
Kevin Wolf wrote:
>
> Am 20.05.2010 07:36, schrieb MORITA Kazutaka:
> > +
> > +/*
> > + * Append an option list (list) to an option list (dest).
> > + *
> > + * If dest is NULL, a new copy of list is created.
> > + *
> > + * Returns a pointer to the first elemen
On 05/23/2010 07:30 PM, Michael S. Tsirkin wrote:
Maybe we should use atomics on index then?
This should only be helpful if you access the cacheline several times in
a row. That's not the case in virtio (or here).
So why does it help?
We actually do access the cachel
74 matches
Mail list logo
