The Buildbot has detected a new failure on builder default_openbsd_4.9 while
building qemu.
Full details are available at:
http://buildbot.b1-systems.de/qemu/builders/default_openbsd_4.9/builds/167
Buildbot URL: http://buildbot.b1-systems.de/qemu/
Buildslave for this Build: kraxel_openbsd49
The Buildbot has detected a new failure on builder default_openbsd_current
while building qemu.
Full details are available at:
http://buildbot.b1-systems.de/qemu/builders/default_openbsd_current/builds/167
Buildbot URL: http://buildbot.b1-systems.de/qemu/
Buildslave for this Build:
The Buildbot has detected a new failure on builder default_x86_64_rhel61 while
building qemu.
Full details are available at:
http://buildbot.b1-systems.de/qemu/builders/default_x86_64_rhel61/builds/167
Buildbot URL: http://buildbot.b1-systems.de/qemu/
Buildslave for this Build: kraxel_rhel61
This was missed due to the fact that it's in the top level and it uses
'struct DeviceInfo' instead of 'DeviceInfo' for some strange reason.
I'm not able to test this as I don't have libusbredir installed.
Signed-off-by: Anthony Liguori aligu...@us.ibm.com
---
usb-redir.c | 24
The Buildbot has detected a new failure on builder default_mingw32 while
building qemu.
Full details are available at:
http://buildbot.b1-systems.de/qemu/builders/default_mingw32/builds/167
Buildbot URL: http://buildbot.b1-systems.de/qemu/
Buildslave for this Build: kraxel_rhel61
Build
On 02/03/2012 06:11 PM, q...@buildbot.b1-systems.de wrote:
The Buildbot has detected a new failure on builder default_mingw32 while
building qemu.
Full details are available at:
http://buildbot.b1-systems.de/qemu/builders/default_mingw32/builds/167
Buildbot URL:
Untested but simple enough.
Signed-off-by: Anthony Liguori aligu...@us.ibm.com
---
usb-bsd.c | 11 ++-
1 files changed, 6 insertions(+), 5 deletions(-)
diff --git a/usb-bsd.c b/usb-bsd.c
index 2c6afc8..43fd1a1 100644
--- a/usb-bsd.c
+++ b/usb-bsd.c
@@ -410,15 +410,16 @@ static void
On 02/03/2012 03:14 PM, Anthony Liguori wrote:
Nope, the legacy property still keeps the dd.f format. This is only
for QOM (and
internal use by qdev).
Ah, I forgot we duplicate the properties here.
Since there is now a programmatic mapping between legacy properties
types and non-legacy
On 02/03/2012 03:27 PM, Anthony Liguori wrote:
On 02/02/2012 10:45 AM, Paolo Bonzini wrote:
The reference that is returned by qdev_device_add is never given
back, so that device_del does not cause the refcount to go to zero
(and thus does nothing).
Signed-off-by: Paolo
On 02/04/2012 01:21 AM, Paolo Bonzini wrote:
I'm not sure... we would trade removal of an ugly concept (the legacy
properties) with addition of a layering violation (poking into the
DeviceState subclasses).
The main problem here is that you said no to a hierarchy of property
classes. This is
Hope to get comments from live migration developers,
Anthony Liguori anth...@codemonkey.ws wrote:
Guest memory management
---
Instead of managing each memory slot individually, a single API will be
provided that replaces the entire guest physical memory map
On 3 February 2012 20:58, Mark Langsdorf mark.langsd...@calxeda.com wrote:
Signed-off-by: Mark Langsdorf mark.langsd...@calxeda.com
---
MAINTAINERS | 5 +
1 files changed, 5 insertions(+), 0 deletions(-)
diff --git a/MAINTAINERS b/MAINTAINERS
index 173e893..bdc254f 100644
---
On 02/03/2012 06:43 PM, Paolo Bonzini wrote:
On 02/04/2012 01:21 AM, Paolo Bonzini wrote:
I'm not sure... we would trade removal of an ugly concept (the legacy
properties) with addition of a layering violation (poking into the
DeviceState subclasses).
The main problem here is that you said no
On 02/03/2012 06:27 PM, Paolo Bonzini wrote:
On 02/03/2012 03:27 PM, Anthony Liguori wrote:
On 02/02/2012 10:45 AM, Paolo Bonzini wrote:
The reference that is returned by qdev_device_add is never given
back, so that device_del does not cause the refcount to go to zero
(and thus does nothing).
Vadim,
We tested the free build driver on 32-bit Windows 7 and the symptom was the
same. In other words, the latest driver source from
https://github.com/YanVugenfirer/ is buggy and it was not workable at all.
-Original Message-
From: Charles.Tsai-蔡清海-研究發展部
Sent: Friday, February
On 02/04/2012 04:00 AM, Anthony Liguori wrote:
Yeah, I was just thinking out loud. My plan is to pull your series into
my qom-rebase branch.
The last few commits on
https://github.com/aliguori/qemu/tree/qom-rebase.12 have a variant
visitor and accessors that use it.
Ok, I'll cherry-pick
On 02/04/2012 04:03 AM, Anthony Liguori wrote:
There's no object_ref() in qdev_device_add(). The 2 references come
from adding a child link to /peripheral and via object_new().
Sure, but there's when the object_new() reference becomes unreachable.
At this point, if it weren't for /peripheral
On 02/04/2012 07:42 AM, Paolo Bonzini wrote:
Ok, I'll cherry-pick from there and send out an updated patch series
later today.
... that won't work unfortunately. Enums are broken (not your fault
really, I sent this before losttickpolicy went in); I really dislike
having a single object that
101 - 118 of 118 matches
Mail list logo
