On 10/28/2011 07:21 PM, Kevin Wolf wrote:
-if (!force !bdrv_dev_is_tray_open(bs)
- bdrv_dev_is_medium_locked(bs)) {
-qerror_report(QERR_DEVICE_LOCKED, bdrv_get_device_name(bs));
+if (bdrv_dev_is_medium_locked(bs) !bdrv_dev_is_tray_open(bs)) {
+
Undefine ABS to avoid a clash with the macro that glib.h
helpfully defines for us (and a resulting build failure
on ia64 hosts).
Signed-off-by: Peter Maydell peter.mayd...@linaro.org
---
Bit of a namespace grab by glib.h if you ask me. Undefining
ABS seems the most straightforward fix.
Thank you for subscribing. You have now unsubscribed and no more messages will
be sent.
Hi list,
During the GSoC mentor summit I held a small summit to find out what users of
QEMU think could be improved and how they perceive QEMU.
The main point brought up was that people felt ignored when sending patches.
From my experience, this usually happens when patches hit a maintainer
Hi list,
During the GSoC mentor summit there was a pretty interesting session on how to
get students to stick with your project even after GSoC has ended. So far we
haven't really been exactly successful in that respect :). I'll just post my
notes below:
- send successful students to
On 13.10.2011, at 17:24, Alexander Graf wrote:
When running QEMU without -cpu parameter, the user usually wants a sane
default. So far, we're using the qemu64/qemu32 CPU type, which basically
means the maximum TCG can emulate.
That's a really good default when using TCG, but when running
On 30.09.2011, at 19:46, Alexander Graf wrote:
When using qemu's linux-user binaries through binfmt, argv[0] gets lost
along the execution because qemu only gets passed in the full file name
to the executable while argv[0] can be something completely different.
This breaks in some subtile
Hi,
As guests become NUMA aware, it becomes important for the guests to
have correct NUMA policies when they run on NUMA aware hosts.
Currently limited support for NUMA binding is available via libvirt
where it is possible to apply a NUMA policy to the guest as a whole.
However multinode guests
On 29.10.2011, at 20:45, Bharata B Rao wrote:
Hi,
As guests become NUMA aware, it becomes important for the guests to
have correct NUMA policies when they run on NUMA aware hosts.
Currently limited support for NUMA binding is available via libvirt
where it is possible to apply a NUMA
