The Buildbot has detected a new failure on builder s390-next_x86_64_debian_5_0
while building qemu.
Full details are available at:
http://buildbot.b1-systems.de/qemu/builders/s390-next_x86_64_debian_5_0/builds/38
Buildbot URL: http://buildbot.b1-systems.de/qemu/
Buildslave for this Build: yuzu
The Buildbot has detected a new failure on builder s390-next_i386_debian_5_0
while building qemu.
Full details are available at:
http://buildbot.b1-systems.de/qemu/builders/s390-next_i386_debian_5_0/builds/38
Buildbot URL: http://buildbot.b1-systems.de/qemu/
Buildslave for this Build: yuzuki
B
On 07/12/2011 03:37 PM, Kevin Wolf wrote:
Am 11.07.2011 15:02, schrieb Hannes Reinecke:
Hi all,
these are some fixes I found during debugging my megasas HBA emulation.
This time I've sent them as a separate patchset for inclusion.
All of them have been acked, so please apply.
Hannes Reinecke (
Ping? Anyone know this area of code? Can we just remove
one monitor_resume() call from migrate_fd_put_buffer() ?
09.07.2011 15:07, Michael Tokarev wrote:
> After some debugging I found a programming error in
> error handling in migration, but I'm not sure how to
> fix it.
>
> When migration sta
Am 19.07.2011 04:39, schrieb Isaku Yamahata:
Thank you for addressing this. Similar patches were proposed and
weren't merged unfortunately.
The reason why the qdev_register_reset() in vl.c is to keep the reset order.
The reset for main_system_bus shouldn't registered by qbus_create_inplace().
Bu
The Buildbot has detected a new failure on builder xen_x86_64_debian_5_0 while
building qemu.
Full details are available at:
http://buildbot.b1-systems.de/qemu/builders/xen_x86_64_debian_5_0/builds/38
Buildbot URL: http://buildbot.b1-systems.de/qemu/
Buildslave for this Build: yuzuki
Build Rea
The Buildbot has detected a new failure on builder xen_i386_debian_5_0 while
building qemu.
Full details are available at:
http://buildbot.b1-systems.de/qemu/builders/xen_i386_debian_5_0/builds/38
Buildbot URL: http://buildbot.b1-systems.de/qemu/
Buildslave for this Build: yuzuki
Build Reason:
On Mon, Jul 18, 2011 at 2:22 PM, Juergen Lock wrote:
> Hi!
>
> I'm the FreeBSD qemu port maintainer and don't have a sparc64 box
> myself, but Jashank Jeremy (Cc'd) now was so kind to test qemu 0.14.1
> on a FreeBSD/sparc64 box booting a FreeBSD 8/i386 install iso using
> i386-softmmu
What's th
On Mon, 2011-07-18 at 11:03 +0100, Ian Campbell wrote:
> On Mon, 2011-07-18 at 10:51 +0100, Wei Liu wrote:
> > Bug resend.
> >
> > This bug was reported about one month ago. QEMU fails to start with
> > Xen unstable. I found that it has not been fix with latest Xen
> > unstable. BIOS is Seabios (w
Thank you for addressing this. Similar patches were proposed and
weren't merged unfortunately.
The reason why the qdev_register_reset() in vl.c is to keep the reset order.
The reset for main_system_bus shouldn't registered by qbus_create_inplace().
But the check, bus != main_system_bus, doesn't wo
Hi,
Resent [09/12] and [10/12].
On Mon, Jul 18, 2011 at 10:52 PM, Kevin Wolf wrote:
> Am 12.07.2011 13:56, schrieb Fam Zheng:
>> Changes from v8:
>> 09/12: remove duplicated sscanf
>> 10/12: change option name to 'subformat', change commit message typo,
>> factor common parts
Add create option 'format', with enums:
monolithicSparse
monolithicFlat
twoGbMaxExtentSparse
twoGbMaxExtentFlat
Each creates a subformat image file. The default is monolithicSparse.
Signed-off-by: Fam Zheng
---
block/vmdk.c | 503 +++--
The Buildbot has detected a new failure on builder block_i386_debian_5_0 while
building qemu.
Full details are available at:
http://buildbot.b1-systems.de/qemu/builders/block_i386_debian_5_0/builds/38
Buildbot URL: http://buildbot.b1-systems.de/qemu/
Buildslave for this Build: yuzuki
Build Rea
The Buildbot has detected a new failure on builder block_x86_64_debian_5_0
while building qemu.
Full details are available at:
http://buildbot.b1-systems.de/qemu/builders/block_x86_64_debian_5_0/builds/38
Buildbot URL: http://buildbot.b1-systems.de/qemu/
Buildslave for this Build: yuzuki
Build
Parse vmdk decriptor file and open mono flat image.
Read/write the flat extent.
Signed-off-by: Fam Zheng
---
block/vmdk.c | 171 +-
1 files changed, 158 insertions(+), 13 deletions(-)
diff --git a/block/vmdk.c b/block/vmdk.c
index f637d98
Signed-off-by: Hervé Poussineau
---
hw/ds1225y.c | 99 +--
hw/mips.h |3 --
hw/mips_jazz.c | 11 +-
3 files changed, 82 insertions(+), 31 deletions(-)
diff --git a/hw/ds1225y.c b/hw/ds1225y.c
index 5105b9b..87412e2 100644
---
Signed-off-by: Hervé Poussineau
---
hw/ds1225y.c | 42 +-
hw/mips.h|1 -
2 files changed, 1 insertions(+), 42 deletions(-)
diff --git a/hw/ds1225y.c b/hw/ds1225y.c
index b1c5232..1fd7010 100644
--- a/hw/ds1225y.c
+++ b/hw/ds1225y.c
@@ -33,7 +33,6
Signed-off-by: Hervé Poussineau
---
hw/ds1225y.c | 16 +---
trace-events |4
2 files changed, 9 insertions(+), 11 deletions(-)
diff --git a/hw/ds1225y.c b/hw/ds1225y.c
index 1fd7010..5105b9b 100644
--- a/hw/ds1225y.c
+++ b/hw/ds1225y.c
@@ -24,9 +24,7 @@
#include "hw.h"
This patchset qdev-ifies the ds1225y device, used in MIPS Jazz emulation.
Changes since v2:
- replace "nvram" by "ds1225y" for qdev device name
(no change in patches 1 and 2)
Changes since v1:
- rebased
- split into multiple patches as per Markus advice
Hervé Poussineau (3):
ds1225y: Remove pr
qbus_reset_all_fn was registered twice, so a lot of device reset
functions were also called twice when QEMU started.
It is sufficient to call sysbus_get_default() which will
register qbus_reset_all_fn.
Signed-off-by: Stefan Weil
---
vl.c |2 +-
1 files changed, 1 insertions(+), 1 deletions(
On Mon, Jul 18, 2011 at 15:46, Anthony PERARD wrote:
> On Mon, Jul 18, 2011 at 13:30, Alexander Graf wrote:
>>
>> On 15.07.2011, at 16:32, Anthony Perard wrote:
>>
>>> In Xen case, memory can be bigger than the host memory. that mean a
>>> 32bits host (and QEMU) should be able to handle a RAM add
On 07/18/2011 02:11 PM, Juan Quintela wrote:
Hi
Please send in any agenda items you are interested in covering.
From last week:
- Device passthrough on non-PCI (take 2) (agraf)
- 0.15 Release Schedule
- Unified object model (QEMU Object Model)
Regards,
Anthony Liguori
Later, Juan.
Hi
Please send in any agenda items you are interested in covering.
>From last week:
- Device passthrough on non-PCI (take 2) (agraf)
Later, Juan.
Hi!
I'm the FreeBSD qemu port maintainer and don't have a sparc64 box
myself, but Jashank Jeremy (Cc'd) now was so kind to test qemu 0.14.1
on a FreeBSD/sparc64 box booting a FreeBSD 8/i386 install iso using
i386-softmmu and we found two things:
1. The hang people have been reporting seems to be
Hello gentlemans,
I'm back to this issue, hopefully I'm not bothering too much :(
To summarize first:
we're experiencing problems with 2.6.32.x KVM guests crashing when running
tcpdump. The problem has been fixed since then, in newer kernels, but
I'd like to find the fix and get it to 2.6.32.x st
Hi Andreas.
I posted a reply to the bug database. Regarding my 'bios' - it is really
nothing.
I need it to boot RTEMS. It just mocks up a minimal residual and jumps to
the kernel load address.
You can take a look at
http://www.rtems.org/viewvc/rtems/c/src/lib/libbsp/powerpc/shared/bootloader/
T
From: Stefano Stabellini
The unplug protocol is necessary to support PV drivers in the guest: the
drivers expect to be able to "unplug" emulated disks and nics before
initializing the Xen PV interfaces.
It is responsibility of the guest to make sure that the unplug is done
before the emulated dev
Public bug reported:
The 7540 family of PPCs' MMU can update TLBs using hardware search (like
a 604 or 7400) but also using a software algorithm. The mechanism used
is defined by HID0[STEN].
By default (CPU reset) HID0 is set to 0x8000 (BTW; another small bug, qemu
doesn't set the hardwired
Google for MPC7450UM.pdf and MPC7410UM.pdf. These two documents cover
the
7441, 7445, 7451, 7455, 7457, 7447, 7448 and the 7410 and 7400 CPUs,
respectively.
For all these, Alex' description applies. However, (and I made a mistake in my
original post),
the setting affected is
env->hreset_excp_pr
On Fri, 15 Jul 2011, Anthony PERARD wrote:
> A Xen guest memory is allocated by libxc. But this memory is not
> allocated continuously, instead, it leaves the VGA IO memory space not
> allocated, same for the MMIO space (at HVM_BELOW_4G_MMIO_START of size
> HVM_BELOW_4G_MMIO_LENGTH).
I realized no
On Mon, 18 Jul 2011, Wei Liu wrote:
> Bug resend.
>
> This bug was reported about one month ago. QEMU fails to start with
> Xen unstable. I found that it has not been fix with latest Xen
> unstable. BIOS is Seabios (with Xen patch).
>
> Xen-unstable a2457fc25c83872a5646c93f1e31958a2f5951e9
>
On Mon, 18 Jul 2011, Alexander Graf wrote:
> On 15.07.2011, at 12:52, Kevin Wolf wrote:
>
> > Am 15.07.2011 12:34, schrieb Stefano Stabellini:
> >> On Fri, 1 Jul 2011, Stefano Stabellini wrote:
> >>> On Fri, 1 Jul 2011, Kevin Wolf wrote:
> Am 30.06.2011 16:16, schrieb Stefano Stabellini:
> >>
On Sun, 17 Jul 2011, Alexander Graf wrote:
> While applying some of the outstanding patches from the masses of Xen patches
> on the mailing list, I stumbled over a few things and wrote up patches to fix
> them.
>
> Functionally, nothing should change with these applied, but I want to give
> people
Map guest memory and pass on a direct pointer instead of copying
the bits to a indirect buffer. EHCI transfer descriptors can
reference multiple (physical guest) pages so we'll actually start
seeing usb packets wich carry iovec with more than one element.
Signed-off-by: Gerd Hoffmann
---
hw/usb
Map guest memory and pass on a direct pointer instead of copying
the bits to a indirect buffer.
Signed-off-by: Gerd Hoffmann
---
hw/usb-uhci.c | 15 +++
1 files changed, 7 insertions(+), 8 deletions(-)
diff --git a/hw/usb-uhci.c b/hw/usb-uhci.c
index 20b829b..824e3a5 100644
--- a/
Add full iovec support to usb-storage.
Signed-off-by: Gerd Hoffmann
---
hw/usb-msd.c | 107 ++---
1 files changed, 49 insertions(+), 58 deletions(-)
diff --git a/hw/usb-msd.c b/hw/usb-msd.c
index 64fb9f8..91c4552 100644
--- a/hw/usb-msd.c
+++
Zap data pointer from USBPacket, add a QEMUIOVector instead.
Add a bunch of helper functions to manage USBPacket data.
Switch over users to the new interface.
Note that USBPacket->len was used for two purposes: First to
pass in the buffer size and second to return the number of
transfered bytes o
Add full support for iovecs to usb-host. The code can split large
transfers into smaller ones already, we are using this to also split
requests at iovec borders.
Signed-off-by: Gerd Hoffmann
---
usb-linux.c | 27 ++-
1 files changed, 18 insertions(+), 9 deletions(-)
d
Add full support for iovecs to usb-serial.
Signed-off-by: Gerd Hoffmann
---
hw/usb-serial.c | 27 ---
1 files changed, 16 insertions(+), 11 deletions(-)
diff --git a/hw/usb-serial.c b/hw/usb-serial.c
index 4a00211..1133e8d 100644
--- a/hw/usb-serial.c
+++ b/hw/usb-seri
Move the QEMUSGList typedef to qemu-common so it can easily be used.
The actual struct definition stays in dma.h.
Signed-off-by: Gerd Hoffmann
---
dma.h |4 ++--
qemu-common.h |1 +
2 files changed, 3 insertions(+), 2 deletions(-)
diff --git a/dma.h b/dma.h
index 3d8324b..a6db5b
Fill the spefified area with zeros.
Signed-off-by: Gerd Hoffmann
---
iov.c | 23 +++
iov.h |2 ++
2 files changed, 25 insertions(+), 0 deletions(-)
diff --git a/iov.c b/iov.c
index 60553c7..e7385c4 100644
--- a/iov.c
+++ b/iov.c
@@ -62,6 +62,29 @@ size_t iov_to_buf(con
Useful for debugging purposes.
Signed-off-by: Gerd Hoffmann
---
iov.c | 31 +++
iov.h |2 ++
2 files changed, 33 insertions(+), 0 deletions(-)
diff --git a/iov.c b/iov.c
index 1e02791..60553c7 100644
--- a/iov.c
+++ b/iov.c
@@ -73,3 +73,34 @@ size_t iov_size(co
Hi,
This patch series introduces iovecs to the USB subsystem, usb packet
payload is passed around as iovec instead of a linear buffer. This
allows the host controllers to use scatter lists and to pass on data
buffers directly, so we can avoid an extra copy.
please review,
Gerd
Gerd Hoffmann
On Mon, Jul 18, 2011 at 12:14, Stefano Stabellini
wrote:
> On Fri, 15 Jul 2011, Anthony PERARD wrote:
>> On Fri, Jul 15, 2011 at 18:05, Stefano Stabellini
>> wrote:
>> > Shouldn't we avoid registering any memory for the whole video ram area?
>> > I mean:
>> >
>> > 0xa - 0x10
>>
>> No, bec
Am 12.07.2011 13:56, schrieb Fam Zheng:
> Changes from v8:
> 09/12: remove duplicated sscanf
> 10/12: change option name to 'subformat', change commit message typo,
> factor common parts of creating, and other small improvements
>
> Fam Zheng (12):
> VMDK: introduce VmdkExte
On Mon, Jul 18, 2011 at 13:30, Alexander Graf wrote:
>
> On 15.07.2011, at 16:32, Anthony Perard wrote:
>
>> In Xen case, memory can be bigger than the host memory. that mean a
>> 32bits host (and QEMU) should be able to handle a RAM address of 64bits.
>>
>> Signed-off-by: Anthony PERARD
>> ---
>
On 07/18/11 09:13, Hans de Goede wrote:
This patch adds support for a usb-redir device, which takes a chardev
as a communication channel to an actual usbdevice using the usbredir protocol.
Compiling the usb-redir device requires usbredir-0.3 to be installed for
the usbredir protocol parser, usbr
On Fri, Jul 15, 2011 at 3:58 PM, Jes Sorensen wrote:
> I have been updating the live snapshot wiki for qemu to try and cover
> the commands we will want for async snapshot handling too.
>
> http://wiki.qemu.org/Features/Snapshots
Regarding fd passing, do we even support SELinux today with backing
On Sun, Jul 17, 2011 at 06:39, Alexander Graf wrote:
> When using xen_enabled() we're currently only checking if xen is enabled
> at all during the build. But what if you want to build multiple targets
> out of which only one can potentially run xen code?
>
> That means that for generic code we'll
On Sat, Jul 2, 2011 at 18:35, Andreas Färber wrote:
> Am 30.06.2011 um 23:35 schrieb Anthony PERARD:
>
>> This patch introduces the two IOPorts on e1000, IOADDR and IODATA. The
>> IOADDR is used to specify which register we want to access when we read
>> or write on IODATA.
>>
>> This patch fixes
During the transition to get rid of CONFIG_XEN_MAPCACHE we lost the mapcache
stubs along the way. Nobody realized it because the commands were guarded by
if (xen_enabled()) clauses that made gcc optimize out the respective calls.
This patch adds the stubs again - this time in the generic xen-stubs
On Sat, Jul 16, 2011 at 11:08 AM, Blue Swirl wrote:
> On Mon, Jun 27, 2011 at 12:21 PM, Stefan Hajnoczi wrote:
>> Here is the latest version of the coroutine series with Mac OS X fixes from
>> Andreas Färber .
>>
>> QEMU is event-driven and suffers when blocking operations are performed
>> becau
We were still exporting CONFIG_XEN_MAPCACHE, even though it's completely
unused by now. Remove it.
Signed-off-by: Alexander Graf
---
configure |3 ---
1 files changed, 0 insertions(+), 3 deletions(-)
diff --git a/configure b/configure
index e57efb1..f537130 100755
--- a/configure
+++ b/conf
When using xen_enabled() we're currently only checking if xen is enabled
at all during the build. But what if you want to build multiple targets
out of which only one can potentially run xen code?
That means that for generic code we'll still have to fall back to the
variable and potentially slow t
While applying some of the outstanding patches from the masses of Xen patches
on the mailing list, I stumbled over a few things and wrote up patches to fix
them.
Functionally, nothing should change with these applied, but I want to give
people the chance to review them before pushing them :).
Ale
On 15.07.2011, at 16:32, Anthony Perard wrote:
> In Xen case, memory can be bigger than the host memory. that mean a
> 32bits host (and QEMU) should be able to handle a RAM address of 64bits.
>
> Signed-off-by: Anthony PERARD
> ---
> cpu-common.h |8
> exec.c |9 +
On 15.07.2011, at 16:32, Anthony Perard wrote:
> Use the "host" CONFIG_ define instead of the "target" one.
>
> Signed-off-by: Anthony PERARD
> ---
> hw/xen.h |2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
>
> diff --git a/hw/xen.h b/hw/xen.h
> index e432705..43b95d6 100644
> ---
On 15.07.2011, at 19:05, Stefano Stabellini wrote:
> On Fri, 15 Jul 2011, Anthony PERARD wrote:
>> Hi all,
>>
>> Xen is not limited by the QEMU's virtual address space for the allocation of
>> the guest RAM. So even with a QEMU 32bits, a Xen guest can have more than 4
>> GB
>> of RAM.
>>
>> Wi
On Sun, Jul 17, 2011 at 9:48 AM, Blue Swirl wrote:
> 789f88d0b21fedfd4251d56bb7a9fbfbda7a4ac7 only fixed #else,
> fix also #if.
>
> Signed-off-by: Blue Swirl
> ---
> scripts/checkpatch.pl | 1 +
> 1 files changed, 1 insertions(+), 0 deletions(-)
>
> diff --git a/scripts/checkpatch.pl b/script
On 15.07.2011, at 12:52, Kevin Wolf wrote:
> Am 15.07.2011 12:34, schrieb Stefano Stabellini:
>> On Fri, 1 Jul 2011, Stefano Stabellini wrote:
>>> On Fri, 1 Jul 2011, Kevin Wolf wrote:
Am 30.06.2011 16:16, schrieb Stefano Stabellini:
> On Thu, 30 Jun 2011, Kevin Wolf wrote:
>>> +stat
2011/7/17 Stéphanie Ouillon :
> I have been facing a problem for 3-4 days with my virtio network device
> driver in qemu: when I load the driver, I get the following error:
> kvm: virtio: trying to map MMIO memory
[...]
> Would anybody have a clue about what kind of bug would provoke this error in
On Fri, 15 Jul 2011, Anthony PERARD wrote:
> On Fri, Jul 15, 2011 at 18:05, Stefano Stabellini
> wrote:
> > Shouldn't we avoid registering any memory for the whole video ram area?
> > I mean:
> >
> > 0xa - 0x10
>
> No, because SeaBIOS load the Options ROM (VGA Bios, PXE) to the area
> bet
The code which prints the debug usage message on '-d ?' for *-user
has to come before the check for "not enough arguments", so that
"qemu-foo -d ?" prints the list of possible debug log items rather than
the generic usage message. (This was inadvertently broken in commit
c235d73.)
Signed-off-by: P
On 18.07.2011, at 12:28, riku voipio wrote:
> On 07/18/2011 01:18 PM, Alexander Graf wrote:
>>> The ia64 sys/ucontext.h defines macros 'uc_link', 'uc_sigmask' and
>>> 'uc_stack'. Rename the s390 target_ucontext struct members to tuc_*,
>>> bringing them into line with the other targets and fixing
On 07/18/2011 01:18 PM, Alexander Graf wrote:
The ia64 sys/ucontext.h defines macros 'uc_link', 'uc_sigmask' and
'uc_stack'. Rename the s390 target_ucontext struct members to tuc_*,
bringing them into line with the other targets and fixing a compile
failure on ia64 hosts caused by this clash.
On 12.07.2011, at 22:27, Peter Maydell wrote:
> The ia64 sys/ucontext.h defines macros 'uc_link', 'uc_sigmask' and
> 'uc_stack'. Rename the s390 target_ucontext struct members to tuc_*,
> bringing them into line with the other targets and fixing a compile
> failure on ia64 hosts caused by this cl
Here's some reproduction code you can use to see the difference between
glibc and raw system calls:
https://gist.github.com/1084042
If you're wondering about Linux and non-glibc distributions using qemu,
Alpine is one particular answer to that question (so the affected Linux
distributions is non-
On Mon, 2011-07-18 at 10:51 +0100, Wei Liu wrote:
> Bug resend.
>
> This bug was reported about one month ago. QEMU fails to start with
> Xen unstable. I found that it has not been fix with latest Xen
> unstable. BIOS is Seabios (with Xen patch).
Please use current mainline seabios.git -- it does
Bug resend.
This bug was reported about one month ago. QEMU fails to start with
Xen unstable. I found that it has not been fix with latest Xen
unstable. BIOS is Seabios (with Xen patch).
Xen-unstable a2457fc25c83872a5646c93f1e31958a2f5951e9
libxl: add LIBXL_MAC_{FMT,FMTLEN,BYTES}
Modelle
p.s.
For people wishing to give this a try, usbredir-0.3 needs a
libusb-1.0.9 git snapshot (a 1.0.9 release is longer
overdue).
In the mean time grab the usbredir branch from my libusb repo
and use that:
http://cgit.freedesktop.org/~jwrdegoede/libusb/log/?h=usbredir
Regards,
Hans
Am 18.07.2011 09:25, schrieb Frediano Ziglio:
> Hi,
> I noted that there are two cluster_data member in block/qcow.c, one
> in BDRVQcowState, the other in QCowAIOCB. The last one is used in
> qcow_aio_write_cb to hold buffer for encrypt the cluster before write
> but I cannot find any related qem
The monitor command for hotplugging is in i386 specific code. This is just
plain wrong, as S390 just learned how to do hotplugging too and needs to
get drives for that.
So let's add a generic copy to generic code that handles drive_add in a
way that doesn't have pci dependencies. All pci specific
Hey guys,
this patch set adds support for hotplug add on S390. Apparently it's the first
non-x86 platform receiving so much love in Qemu, so I've stumbled over some
very basic #if defined(TARGET_I386) cases that just shouldn't be there.
It's trying to make things as generic as possible. I've talk
I just submitted a few patches that enable the s390 virtio bus to receive
a hotplug add event. This patch implements the qemu side of it, so that new
hotplug events can be submitted to the guest.
Signed-off-by: Alexander Graf
---
v1 -> v2:
- make s390 virtio hoplug code emulate-capable
---
On Tue, Jul 12, 2011 at 07:56:27PM +0800, Fam Zheng wrote:
> Changes from v8:
> 09/12: remove duplicated sscanf
> 10/12: change option name to 'subformat', change commit message typo,
> factor common parts of creating, and other small improvements
>
> Fam Zheng (12):
> VMDK:
All architectures can now use drive_add on the monitor. This of course
does not mean that there is hotplug support for the specific platform,
so in order to actually make use of the new drives you still need to
have a hotplug capable device.
Signed-off-by: Alexander Graf
---
hmp-commands.hx |
All guest targets could potentially implement hotplugging. With the next
patches in this set I will also reflect this in the monitor interface.
So let's always compile it in. It shouldn't hurt.
Signed-off-by: Alexander Graf
---
Makefile.target |5 -
1 files changed, 4 insertions(+), 1 d
On 14.07.2011, at 14:13, Kevin Wolf wrote:
> Am 12.07.2011 09:21, schrieb Alexander Graf:
>> The monitor command for hotplugging is in i386 specific code. This is just
>> plain wrong, as S390 just learned how to do hotplugging too and needs to
>> get drives for that.
>>
>> So let's add a generic
On 15.07.2011, at 21:38, Stefan Weil wrote:
> tcg_gen_exit_tb takes a parameter of type tcg_target_long,
> so the type casts of pointer to long should be replaced by
> type casts of pointer to tcg_target_long.
>
> These changes are needed for build environments where
> sizeof(long) != sizeof(voi
The following changes since commit 89b9ba661bd2d6155308f895ec075d813f0e129b:
Fix signal handling of SIG_IPI when io-thread is enabled (2011-07-16 19:43:00
+)
are available in the git repository at:
git://git.linaro.org/people/rikuvoipio/qemu.git linux-user-for-upstream
Cédric VINCENT (4
On 18.07.2011, at 00:34, Andreas Färber wrote:
> Hi,
>
> Am 16.07.2011 um 23:49 schrieb till:
>
>> I have a proprietary ROM implementing system calls that are executed via
>> the 'SC' instruction.
>>
>> I use qemu-0.14.1,
>>
>> qemu-system-ppc -M prep -cpu $CPU -bios my_bios -kernel my_kernel
On 16.07.2011, at 18:26, Blue Swirl wrote:
> On Sat, Jul 16, 2011 at 10:53 AM, Alexander Graf wrote:
>>
>> On 14.07.2011, at 17:22, Bernhard M. Wiedemann wrote:
>>
>>> Hi,
>>>
>>> I tried nested VMX on Xeon E5630 and it worked really well with the Kernel
>>> from avi's git and 0.14.0
>>> (wi
Hi,
I noted that there are two cluster_data member in block/qcow.c, one
in BDRVQcowState, the other in QCowAIOCB. The last one is used in
qcow_aio_write_cb to hold buffer for encrypt the cluster before write
but I cannot find any related qemu_free while I can find many place
where BDRVQcowState::
Hi,
Note that using this with devices where a lot of data is send to the device
(ie a usb stick and writing to it a lot) may lead to increased latencies, due
to the long missing flowcontrol support in chardev in one direction.
For those interested, my personal tree contains Amit's flowcontrol pa
This patch adds support for a usb-redir device, which takes a chardev
as a communication channel to an actual usbdevice using the usbredir protocol.
Compiling the usb-redir device requires usbredir-0.3 to be installed for
the usbredir protocol parser, usbredir-0.3 also contains a server for
redire
Juan Quintela writes:
[...]
> I have think a little bit about hotplug & migration, and haven't arraive
> to a nice solution.
>
> - Disabling hotplug/unplug during migration: easy to do. But it is not
> exactly user friendly (we are here).
>
> - Allowing hotplug during migration. Solutions:
>
86 matches
Mail list logo