Eric Blake writes:
> On 03/24/2017 09:10 AM, Jeff Cody wrote:
>> On Fri, Mar 24, 2017 at 08:49:20AM -0500, Eric Blake wrote:
>>> On 03/24/2017 07:42 AM, Jeff Cody wrote:
>>>
Agree. My preference is to leave it as an array of methods, so long as
that
is tenable
On 26/03/17 20:54, Stefan Weil wrote:
> Am 26.03.2017 um 14:57 schrieb Peter Maydell:
>> On 26 March 2017 at 11:30, Mark Cave-Ayland
>> wrote:
>>> In order to do some testing on a Windows box, I've spent a bit of time
>>> this weekend setting up a mingw-w64 build
On 24/03/17 20:34, Paul Durrant wrote:
>> -Original Message-
>> From: Qemu-devel [mailto:qemu-devel-
>> bounces+paul.durrant=citrix@nongnu.org] On Behalf Of Paul Durrant
>> Sent: 24 March 2017 19:18
>> To: 'Stefano Stabellini' ; Juergen Gross
>>
Reviewed-by: Pavel Dovgalyuk
> -Original Message-
> From: Alex Bennée [mailto:alex.ben...@linaro.org]
> Sent: Friday, March 24, 2017 6:26 PM
> To: pavel.dovga...@ispras.ru
> Cc: qemu-devel@nongnu.org; Alex Bennée
> Subject: [PATCH-for-2.9] replay/replay.c: bump
> From: Alex Bennée [mailto:alex.ben...@linaro.org]
> > From: Pavel Dovgalyuk
> >
> > This patch adds recording and replaying audio data. Is saves synchronization
> > information for audio out and inputs from the microphone.
> >
> > v2: removed unneeded whitespace change
This enables in-kernel handling of H_PUT_TCE_INDIRECT and
H_STUFF_TCE hypercalls. The host kernel support is there since v4.6,
in particular d3695aa4f452
("KVM: PPC: Add support for multiple-TCE hcalls").
H_PUT_TCE is already accelerated and does not need any special enablement.
Signed-off-by:
On Thu, Mar 23, 2017 at 09:44:56PM +0100, Juan Quintela wrote:
> We create a struct where to put all the ram state
>
> Start with the following fields:
>
> last_seen_block, last_sent_block, last_offset, last_version and
> ram_bulk_stage are globals that are really related together.
>
>
The recent introduction of a bus master container added
memory_region_add_subregion() into the PCI device registering path but
missed memory_region_del_subregion() in the unregistering path leaving
a reference to the root memory region of the new container.
This adds missing
On Wed, Mar 22, 2017 at 5:03 PM, ashish mittal wrote:
> On Mon, Mar 20, 2017 at 5:55 AM, Daniel P. Berrange
> wrote:
>> On Fri, Mar 17, 2017 at 06:44:56PM -0700, ashish mittal wrote:
>>> On Thu, Mar 16, 2017 at 5:29 PM, ashish mittal
raw_open() expects the caller always passing in the right actual
@options parameter. But when trying to applying snapshot on a RBD
image, bdrv_snapshot_goto() calls raw_open() (by calling the
bdrv_open callback on the BlockDriver) with a NULL @options, and
that will result in a Segmentation fault.
Trying to restore rbd image on ceph cluster from snapshot with
qemu-img could trigger a calling to raw_open with a NULL @options,
and that will lead to a failure of the snapshot applying.
[root@s8345007 ~]# gdb --args qemu-img snapshot -a snap1 rbd:test_pool/dj_image
... ...
Program received
These changes use a vxhs test server that is a part of the following
repository:
https://github.com/VeritasHyperScale/libqnio.git
Signed-off-by: Ashish Mittal
---
v10 changelog:
(1) Redirect o/p of "$QEMU_VXHS -d $TEST_DIR" to /dev/null
v9 changelog:
(1) Dropped
Source code for the qnio library that this code loads can be downloaded from:
https://github.com/VeritasHyperScale/libqnio.git
Sample command line using JSON syntax:
./x86_64-softmmu/qemu-system-x86_64 -name instance-0008 -S -vnc 0.0.0.0:0
-k en-us -vga cirrus -device
Hi,
It seems that there is no difference from your previous version.
You don't have to re-send it if there are no changes.
This patch has been reviewed, so you can just wait until maintainers process it
:)
Thanks.
On 2017/3/27 9:58, Guang Wang wrote:
From: Wang guang
From: Wang guang
The channel socket was initialized manually,
but forgot to set QIO_CHANNEL_FEATURE_SHUTDOWN.
Thus, the colo_process_incoming_thread would hang at recvmsg.
This patch just call qio_channel_socket_new to get channel,
Which set QIO_CHANNEL_FEATURE_SHUTDOWN
On Wed, Mar 22, 2017 at 02:32:26PM +0100, Igor Mammedov wrote:
> Signed-off-by: Igor Mammedov
Reviewed-by: David Gibson
> ---
> tests/Makefile.include | 5 +++
> tests/numa-test.c | 106
>
Am 26.03.2017 um 14:57 schrieb Peter Maydell:
On 26 March 2017 at 11:30, Mark Cave-Ayland
wrote:
In order to do some testing on a Windows box, I've spent a bit of time
this weekend setting up a mingw-w64 build environment on Windows 10
using
Do not hardcode the RA size at all, use a pl_size variable which
accounts the accumulated size, and fill rip->ip_pl at the end.
This will allow to make some blocks optional.
Signed-off-by: Samuel Thibault
---
slirp/ip6_icmp.c | 24 +---
1 file
Hello,
These two patches fix sending the IPv6 RDNSS announce only when
it can actually work, fixing the bug reported by Cole Robinson
. Could somebody review them before I can send
a pull update?
Samuel Thibault (2):
slirp: Make RA build more flexible
slirp: Send RDNSS
Previously we would always send an RDNSS option in the RA, making the guest
try to resolve DNS through IPv6, even if the host does not actually have
and IPv6 DNS server available.
This makes the RDNSS option enabled only when an IPv6 DNS server is
available.
Signed-off-by: Samuel Thibault
Hello,
Cole Robinson, on ven. 24 mars 2017 21:17:43 -0400, wrote:
> I bisected to this commit:
>
> slirp: Add RDNSS advertisement
Mmm, I see. Could you try the attached patch to confirm that it fixes
the issue for you too?
Samuel
diff --git a/slirp/ip6_icmp.c b/slirp/ip6_icmp.c
index
On Windows 98 SE:
* SB16: System hangs as described in this bug report
* ES1370: Causes system freeze with back screen at boot time
* AC97 (as suggested here:
https://smcv.pseudorandom.co.uk/2015/discworldnoir/): BSODs during the
installation
* GUS: Device is not even detected
Conclusion:
Addendum: Since this report is from 2014, I should mention that I am
currently on 16.04.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1295587
Title:
Temporal freeze and slowdown while using
On Fri, Mar 24, 2017 at 12:44:06PM +0100, Juan Quintela wrote:
> Peter Xu wrote:
> > Hi, Juan,
> >
> > Got several nitpicks below... (along with some questions)
> >
> > On Thu, Mar 23, 2017 at 09:44:54PM +0100, Juan Quintela wrote:
> >
> > [...]
> >
> >> static void
On 26 March 2017 at 11:30, Mark Cave-Ayland
wrote:
> In order to do some testing on a Windows box, I've spent a bit of time
> this weekend setting up a mingw-w64 build environment on Windows 10
> using http://wiki.qemu-project.org/Hosts/W32 as a guideline.
I think
Hi all,
In order to do some testing on a Windows box, I've spent a bit of time
this weekend setting up a mingw-w64 build environment on Windows 10
using http://wiki.qemu-project.org/Hosts/W32 as a guideline.
After a few false starts, I was able to get the basic environment
working but so far
Could you provide the command you've used?
I tried `CC=gcc-4.8 ./configure --enable-stack-protector && make` in Ubuntu
14.04 and qemu v2.8.0. It didn't set `-fstack-protector-strong` flag, only
`-fstack-protector-all`.
--
You received this bug notification because you are a member of qemu-
Attempting to compile qemu-ga statically as follows for Windows causes
the following error:
Compilation:
./configure --disable-docs --target-list=x86_64-softmmu \
--cross-prefix=x86_64-w64-mingw32- --static \
--enable-guest-agent-msi --with-vss-sdk=/path/to/VSSSDK72
make -j8
The evdev devices in input-linux.c are read in blocks of one whole
event. If there are not enough bytes available, they are discarded,
instead of being kept for the next read operation. This results in
lost events, of even non-working devices.
This patch keeps track of the number of bytes to be
On Thu, Mar 23, 2017 at 9:21 PM, Stefan Hajnoczi wrote:
> On Thu, Mar 23, 2017 at 11:22:11AM +0200, Sameeh Jubran wrote:
> > Attempting to compile qemu-ga statically as follows for Windows causes
> > the following error:
> >
> > Compilation:
> > ./configure --disable-docs
On Sat, 2017-03-25 at 21:15 +, Peter Maydell wrote:
> On 25 March 2017 at 20:49, Knut Omang wrote:
> >
> > Can we please keep the Sparc support in for a while still?
>
> Yes, John Paul Adrian Glaubitz and the Debian Project have
> kindly provided me with access to a
31 matches
Mail list logo