We should never be running in multi-threaded mode with icount enabled.
There is no point calling handle_icount_deadline here so remove it and
assert !use_icount.
Signed-off-by: Alex Bennée
Reviewed-by: Richard Henderson
---
cpus.c | 4 ++--
1 file
On 7 April 2017 at 14:47, Kevin Wolf wrote:
> The following changes since commit 5fe2339e6b09da7d6f48b9bef0f1a7360392b489:
>
> Merge remote-tracking branch
> 'remotes/awilliam/tags/vfio-updates-20170406.0' into staging (2017-04-07
> 10:29:56 +0100)
>
> are available in the
Am 07.04.2017 um 08:54 hat Fam Zheng geschrieben:
> Coroutine in block layer should always be waken up in bs->aio_context
> rather than the "current" context where it is entered. They differ when
> the main loop is doing QMP tasks.
>
> Race conditions happen without this patch, because the wrong
* Eric Blake (ebl...@redhat.com) wrote:
> On 04/07/2017 09:56 AM, Dr. David Alan Gilbert wrote:
>
> >
> >> The cleanup is useful, and resolves one of the build issues I pointed
> >> out earlier on Rawhide (looks like it is now Fedora 26 in addition to
> >> Rawhide that have new-enough gcc). In
Hi
On Fri, Apr 7, 2017 at 4:41 PM Daniel P. Berrange
> > +.name = "data-path",
> > +.type = QEMU_OPT_STRING,
> > +.help = "Socket path to use for data exhange",
> > +},
> > +{
> > +.name = "ctrl-path",
> > +.type = QEMU_OPT_STRING,
> > +
This is now fixed in QEMU 2.9-rc
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1678466
Title:
using x-vga=on with vfio-pci leads to segfault
Status in QEMU:
New
Bug description:
bug occures
On 04/07/2017 09:56 AM, Dr. David Alan Gilbert wrote:
>
>> The cleanup is useful, and resolves one of the build issues I pointed
>> out earlier on Rawhide (looks like it is now Fedora 26 in addition to
>> Rawhide that have new-enough gcc). In that thread, we argued that it's
>> not going to be
If you get one boot where GPU assignment works with a mobile GeForce,
you're doing better than most.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1680679
Title:
qemu cannot run twice
Status in
* Eric Blake (ebl...@redhat.com) wrote:
> On 04/07/2017 09:32 AM, Dr. David Alan Gilbert (git) wrote:
> > From: "Dr. David Alan Gilbert"
> >
> > gcc 7 (on fedora 26) objects to many of the snprintf's
> > in the smb path and command creation because it can't
> > figure out
On Fri 07 Apr 2017 02:41:21 PM CEST, Kevin Wolf wrote:
>> 6356 5548 4740 3932 3124 2316 15 8 7 0
>>
>> **<> <---><-->*
Sorry, but I have moved to ESXI more than 4 years ago.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1014681
Title:
BSOD with newer host kernels (x64) and W2k8S guest (x64)
Status in QEMU:
On 04/07/2017 09:32 AM, Dr. David Alan Gilbert (git) wrote:
> From: "Dr. David Alan Gilbert"
>
> gcc 7 (on fedora 26) objects to many of the snprintf's
> in the smb path and command creation because it can't
> figure out that the smb_dir (i.e. the /tmp dir for the
On Thu, Apr 06, 2017 at 02:08:47PM -0500, Eric Blake wrote:
> When a block device that is part of a throttle group is hot-unplugged,
> we forgot to remove it from the throttle group. This leaves stale
> memory around, and causes an easily reproducible crash:
>
> $
** Changed in: qemu
Status: Fix Released => Confirmed
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1635339
Title:
qxl_pre_save assertion failure on vm "save"
Status in QEMU:
Confirmed
On Fri, Apr 07, 2017 at 02:58:46PM +0800, weiqi wrote:
> From: Wei Qi
>
> It is unnecessary to assign 'hdev->nvqs' to 'i', because 'hdev->nvqs' unused
> after assignment, so remove it.
>
> Signed-off-by: Wei Qi
> ---
> hw/virtio/vhost.c | 1 -
> 1 file
On 07.04.2017 03:37, Eric Blake wrote:
> As mentioned in commit 0c1bd46, we ignored requests to
> discard the trailing cluster of an unaligned image. While
> discard is an advisory operation from the guest standpoint,
> (and we are therefore free to ignore any request), our
> qcow2 implementation
Our current ACPI table generation code limits the placement of ACPI
tables to 32-bit addressable memory, in order to be able to emit the
root pointer (RSDP) and root table (RSDT) using table types from the
ACPI 1.0 days.
Since ARM was not supported by ACPI before version 5.0, it makes sense
to
On Fri, Apr 07, 2017 at 05:30:31PM +0300, Amarnath Valluri wrote:
> This change introduces a new TPM backend driver that can communicate with
> swtpm(software TPM emulator) using unix domain socket interface.
>
> Swtpm uses two unix sockets, one for plain TPM commands and responses, and one
> for
Hi,
Fedora 26 has gcc 7.0.1 which has the normal compliment
of new fussy warnings; so far I've posted :
tests/check-qdict: Fix missing brackets
slirp/smb: Replace constant strings by glib string
that fix one actual mistake and work around something it's being
fussy over.
But I've also got a
From: "Dr. David Alan Gilbert"
gcc 7 (on fedora 26) objects to many of the snprintf's
in the smb path and command creation because it can't
figure out that the smb_dir (i.e. the /tmp dir for the configuration)
is known to be short.
Replace all these fixed length buffers by
On Thu, Apr 06, 2017 at 06:53:09PM +0800, Haozhong Zhang wrote:
> On 04/06/17 11:13 +0100, Stefan Hajnoczi wrote:
> > On Fri, Mar 31, 2017 at 04:41:47PM +0800, Haozhong Zhang wrote:
> > >
> > > Add an boolean option 'flush-hint' to device 'nvdimm'. If it's on, a
> > > flush hint address structure
Public bug reported:
After using qemu with gpu passthrough and then shutting down windows 7 properly
I cannot boot windows 7 a second time.
Only a full reboot of linux fixes this issue.
Qemu appears to corrupt something in linux when exiting.
I get no error messages but windows 7 never finishes
Signed-off-by: Amarnath Valluri
---
hw/tpm/tpm_passthrough.c | 64
hw/tpm/tpm_util.c| 25 +++
hw/tpm/tpm_util.h| 4 +++
3 files changed, 34 insertions(+), 59 deletions(-)
diff --git
On Thu, Apr 06, 2017 at 06:31:17PM +0800, Haozhong Zhang wrote:
> On 04/06/17 10:43 +0100, Stefan Hajnoczi wrote:
> > On Fri, Mar 31, 2017 at 04:41:43PM +0800, Haozhong Zhang wrote:
> > We should think about the optimal way of implementing Flush Hint
> > Addresses in QEMU. But if there is no
TPM configuration options are backend implementation details and shall not be
part of base TPMBackend object, and these shall not be accessed directly outside
of the class, hence added a new interface method, get_tpm_options() to
TPMDriverOps., which shall be implemented by the derived classes to
On Thu, Apr 06, 2017 at 07:32:01AM -0700, Dan Williams wrote:
> On Thu, Apr 6, 2017 at 2:43 AM, Stefan Hajnoczi wrote:
> > On Fri, Mar 31, 2017 at 04:41:43PM +0800, Haozhong Zhang wrote:
> * I don't think we can just skip implementing support for this flush.
> Yes it's
you could pass sockets via QMP a while ago, but listening to unix socket
has been added there:
commit fe4831b1e7e7007ae15ae0470a06898660ab3877
Author: Marc-André Lureau
Date: Tue Jan 13 17:57:51 2015 +0100
spice: add unix address support
Teach qemu to
damn launchpad, wrong bug and I can't change it back. Please someone
move it back to New/Confirmed
** Changed in: qemu
Status: New => Fix Released
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
As TPMBackend is a Qemu Object, we can use object_unref() inplace of
tpm_backend_destroy() to free the backend object, hence removed destroy() from
TPMDriverOps interface.
Signed-off-by: Amarnath Valluri
---
backends/tpm.c | 11 ---
Provide base implementation of realloc_buffer(), so that backend implementations
can resue.
Signed-off-by: Amarnath Valluri
---
backends/tpm.c | 9 -
hw/tpm/tpm_passthrough.c | 12
2 files changed, 8 insertions(+), 13 deletions(-)
This change introduces a new TPM backend driver that can communicate with
swtpm(software TPM emulator) using unix domain socket interface.
Swtpm uses two unix sockets, one for plain TPM commands and responses, and one
for out-of-band control messages.
The swtpm and associated tools can be found
Move thread handling inside TPMBackend, this way backend implementations need
not to maintain their own thread life cycle, instead they needs to implement
'handle_request()' class method that always been called from a thread.
This change made tpm_backend_int.h kind of useless, hence removed it.
This allows backend implementations left optional interface methods.
For mandatory methods assertion checks added.
Signed-off-by: Amarnath Valluri
---
backends/tpm.c | 28 +---
hw/tpm/tpm_passthrough.c | 16
2 files
Initialize and free TPMBackend data members in it's own instance_init() and
instance_finalize methods.
Took the opportunity to fix object cleanup in tpm_backend_{create,destroy}
methods
Signed-off-by: Amarnath Valluri
---
backends/tpm.c | 8 ++--
TPMDriverOps inside TPMBackend is not required, as it is supposed to be a class
member. The only possible reason for keeping in TPMBackend was, to get the
backend type in tpm.c where dedicated backend api, tpm_backend_get_type() is
present.
Signed-off-by: Amarnath Valluri
Briefly, Theses set of patches introduces:
- new TPM backend driver to support software TPM emulators(swtpm(1)).
- and few supported fixes/enhancements/cleanup to existing tpm backend code.
The similar idea was initiated earliar(2) by Stefan Berger(CCed) with slightly
different approach,
Looks like tribblix is an OpenSolaris variant from the above output (I
normally tend to test with Milax but it's good to have another reference
around).
I spent a lot of time during the 2.8 cycle fixing up the context switch
code in OpenBIOS which gets OpenSolaris most of the way. AFAICT the 2
On 06.04.2017 21:08, Eric Blake wrote:
> When a block device that is part of a throttle group is hot-unplugged,
> we forgot to remove it from the throttle group. This leaves stale
> memory around, and causes an easily reproducible crash:
>
> $ ./x86_64-softmmu/qemu-system-x86_64 -nodefaults
On 04/07/2017 08:47 AM, Kevin Wolf wrote:
> The assertion is currently failing. We can't require callers to have
> write permissions when all they are doing is a read, so comment it out.
> Add a FIXME comment in the code so that the check is re-enabled when
> copy on read is refactored into its
Looks like these counters have been implemented here:
http://git.qemu-project.org/?p=qemu.git;a=commitdiff;h=3b27430177498a1728b6
** Changed in: qemu
Status: New => Fix Released
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
On Fri, Apr 07, 2017 at 02:58:25PM +0800, weiqi wrote:
> From: Wei Qi
>
> This patchset cleanups some unused/unnecessary variables assignment.
Pls remember to repost after 2.9 is out.
> Wei Qi (3):
> vhost: simple clean up
> vnc: simple clean up
> esp-pci: simple
On 04/07/2017 01:54 AM, Fam Zheng wrote:
> Coroutine in block layer should always be waken up in bs->aio_context
s/waken up/awakened/
> rather than the "current" context where it is entered. They differ when
> the main loop is doing QMP tasks.
>
> Race conditions happen without this patch,
Triaging old bug tickets ... can you still reproduce this issue with the
latest version of QEMU (version 2.9)?
** Changed in: qemu
Status: New => Incomplete
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
** No longer affects: qemu
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1077806
Title:
Integrate Virtualbox/Qemu Guest booting as a desktop environment
listing (request)
Status in Light
Triaging old bug tickets ... can you still reproduce this issue with the
latest version of QEMU (version 2.9)?
** Changed in: qemu
Status: New => Incomplete
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
Triaging old bug tickets ... can you still reproduce this issue with the
latest version of QEMU (version 2.9)?
** Changed in: qemu
Status: New => Incomplete
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
Triaging old bug tickets ... can you still reproduce this issue with the
latest version of QEMU (version 2.9)?
** Changed in: qemu
Status: New => Incomplete
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
Triaging old bug tickets ... can you still reproduce this issue with the
latest version of QEMU (version 2.9)?
** Changed in: qemu
Status: New => Incomplete
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
On 04/07/2017 06:18 AM, Cornelia Huck wrote:
> From: Jing Liu
>
> This introduces basic support for TN3270, which needs to negotiate
> three Telnet options during handshake:
> - End of Record
> - Binary Transmission
> - Terminal-Type
>
> As a basic
On 07.04.2017 15:53, Eric Blake wrote:
> On 04/07/2017 05:32 AM, Kevin Wolf wrote:
>> The assertion is currently failing. We can't require callers to have
>> write permissions when all they are doing is a read, so comment it out.
>> Add a FIXME comment in the code so that the check is re-enabled
Triaging old bug tickets ... can you still reproduce this issue with the
latest version of QEMU (version 2.9)?
** Changed in: qemu
Status: New => Incomplete
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
The assertion is currently failing. We can't require callers to have
write permissions when all they are doing is a read, so comment it out.
Add a FIXME comment in the code so that the check is re-enabled when
copy on read is refactored into its own filter driver.
Reported-by: Richard W.M. Jones
According to the Debian bug tracker, this has been fixed with this upstream
commit:
http://git.qemu.org/?p=qemu.git;a=commit;h=ab51b1d568e02c80b1abf9016bda3a86dc1db389
... so let's close this now.
** Changed in: qemu
Status: Confirmed => Fix Released
--
You received this bug
On 30.03.2017 04:16, Eric Blake wrote:
> On 03/29/2017 09:01 PM, Ed Swierk via Qemu-devel wrote:
>> Parts of qemu's block code have changed a lot in recent months but are
>> not well exercised by current tests.
>>
>> Subtle bugs have crept in causing assertion failures, hangs and other
>> crashes
From: Fam Zheng
Suggested-by: Kevin Wolf
Signed-off-by: Fam Zheng
Signed-off-by: Kevin Wolf
---
block.c | 4
1 file changed, 4 insertions(+)
diff --git a/block.c b/block.c
index 927ba89..b8a3011 100644
--- a/block.c
Like in the mirror filter driver, we also need to set the image size for
the commit filter driver. This is less likely to be a problem in
practice than for the mirror because we're not at the active layer here,
but attaching new parents to a node in the middle of the chain is
possible, so the size
On 04/07/2017 05:32 AM, Kevin Wolf wrote:
> The assertion is currently failing. We can't require callers to have
> write permissions when all they are doing is a read, so comment it out.
> Add a FIXME comment in the code so that the check is re-enabled when
> copy on read is refactored into its
From: Fam Zheng
It should be moved to the same context as source, before inserting to the
graph.
Reviewed-by: Eric Blake
Reviewed-by: Kevin Wolf
Signed-off-by: Fam Zheng
Signed-off-by: Kevin Wolf
---
Usually guest devices don't like other writers to the same image, so
they use blk_set_perm() to prevent this from happening. In the migration
phase before the VM is actually running, though, they don't have a
problem with writes to the image. On the other hand, storage migration
needs to be able
On 04/07/2017 03:38 AM, Sahid Orentino Ferdjaoui wrote:
> On Fri, Apr 07, 2017 at 02:58:46PM +0800, weiqi wrote:
>> From: Wei Qi
>>
>> It is unnecessary to assign 'hdev->nvqs' to 'i', because 'hdev->nvqs' unused
>> after assignment, so remove it.
>
> nit: The line should not
From: Max Reitz
Signed-off-by: Max Reitz
Reviewed-by: John Snow
Reviewed-by: Eric Blake
Signed-off-by: Kevin Wolf
---
tests/qemu-iotests/041| 46 +++
The following changes since commit 5fe2339e6b09da7d6f48b9bef0f1a7360392b489:
Merge remote-tracking branch 'remotes/awilliam/tags/vfio-updates-20170406.0'
into staging (2017-04-07 10:29:56 +0100)
are available in the git repository at:
git://repo.or.cz/qemu/kevin.git tags/for-upstream
for
From: Fam Zheng
bdrv_replace_child_noperm tries to hand over the quiesce_counter state
from old bs to the new one, but if they are not on the same aio context
this causes unbalance.
Fix this by setting the correct aio context before calling
bdrv_append().
Reported-by: Ed
** Changed in: qemu
Importance: Undecided => Wishlist
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1022023
Title:
vga/std lacks few wide screen modes.
Status in QEMU:
New
Bug description:
Crash reproduced immediately after setting up a win10 VM with qxl driver
10.0.0.15000.
Gerd, are you looking into fixing it? Is it acceptable to crash qemu if
the driver is faulty?
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
From: Max Reitz
If @bs does not have any parents, the only reference to @mirror_top_bs
will be held by the BlockJob object after the bdrv_unref() following
block_job_create(). However, if block_job_create() fails, this reference
will not exist and @mirror_top_bs will have been
The filter driver that is inserted by the commit job needs to use the
same AioContext as its parent and child nodes.
Signed-off-by: Kevin Wolf
Reviewed-by: Eric Blake
Reviewed-by: Fam Zheng
---
block/commit.c | 2 ++
1 file changed, 2
From: Jeff Cody
The documentation and help for qemu-img claims that 'qemu-img create'
will take the '--image-opts' argument. This is not true, so this
patch removes those claims.
Signed-off-by: Jeff Cody
Reviewed-by: Eric Blake
On 04/07/2017 04:35 AM, Daniel P. Berrange wrote:
> On Thu, Apr 06, 2017 at 04:09:17PM -0500, Eric Blake wrote:
>> qemu_kill_report() is already able to tell whether a shutdown
>> was triggered by guest action (no output) or by a host signal
>> (a message about termination is printed via
Which version of QEMU have you been using here? Can you still reproduce
this with the latest version of QEMU (version 2.9)?
** Changed in: qemu
Status: New => Incomplete
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
On Thu, Apr 06, 2017 at 06:46:49PM +0800, Haozhong Zhang wrote:
> On 04/06/17 11:24 +0100, Stefan Hajnoczi wrote:
> > On Fri, Mar 31, 2017 at 04:41:44PM +0800, Haozhong Zhang wrote:
> > > If option 'reserved-size=RSVD' is present, QEMU will reserve an
> > > address range of size 'RSVD' after the
** Changed in: qemu
Importance: Undecided => Wishlist
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1020484
Title:
RFE: Support spice via unix domain socket
Status in QEMU:
New
Bug
Triaging old bug tickets ... can you still reproduce this issue with the
latest version of QEMU (version 2.9)?
** Changed in: qemu
Status: New => Incomplete
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
Marking this bug as fixed, according to comment #4 and #5
** Changed in: qemu
Status: New => Fix Released
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1013888
Title:
windows xp sp3 setup
Hi,
I've attached the files with logs you requested. Could you comment them
somehow?
x86info says that IA32_PERF is not enabled:
Performance MSRs:
MSR_IA32_PERF_STATUS: 0x0
MSR_IA32_MISC_ENABLE: 0x0 [Enabled: ]
--
You received this bug notification because you are a member of qemu-
Closing according to comment #3
** Changed in: qemu
Status: New => Fix Released
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1013714
Title:
Data corruption after block migration (LV->LV)
I put my money on that one:
https://cgit.freedesktop.org/spice/win32/qxl-wddm-
dod/commit/?id=f6e099db39e7d0787f294d5fd0dce328b5210faa
commit f6e099db39e7d0787f294d5fd0dce328b5210faa
Author: Sameeh Jubran
Date: Sun Sep 11 16:05:24 2016 +0300
Use the second bar (VRAM)
On Fri, Apr 07, 2017 at 02:54:14PM +0800, Fam Zheng wrote:
> Previously, before test_block_job_start returns, the job can already
> complete, as a result, the transactional state of other jobs added to
> the same txn later cannot be handled correctly.
>
> Move the block_job_start() calls to
On Fri, Apr 07, 2017 at 02:54:13PM +0800, Fam Zheng wrote:
> Coroutine in block layer should always be waken up in bs->aio_context
> rather than the "current" context where it is entered. They differ when
> the main loop is doing QMP tasks.
>
> Race conditions happen without this patch, because
On Fri, Apr 07, 2017 at 02:54:11PM +0800, Fam Zheng wrote:
> It should be moved to the same context as source, before inserting to the
> graph.
>
> Reviewed-by: Eric Blake
> Reviewed-by: Kevin Wolf
> Signed-off-by: Fam Zheng
> ---
>
On Fri, Apr 07, 2017 at 02:54:10PM +0800, Fam Zheng wrote:
> Suggested-by: Kevin Wolf
> Signed-off-by: Fam Zheng
> ---
> block.c | 4
> 1 file changed, 4 insertions(+)
Reviewed-by: Stefan Hajnoczi
signature.asc
Description: PGP
On Fri, Apr 07, 2017 at 02:54:09PM +0800, Fam Zheng wrote:
> bdrv_replace_child_noperm tries to hand over the quiesce_counter state
> from old bs to the new one, but if they are not on the same aio context
> this causes unbalance.
>
> Fix this by setting the correct aio context before calling
>
Paolo Bonzini writes:
> - Original Message -
>> From: "Alex Bennée"
>> To: "Paolo Bonzini"
>> Cc: dovga...@ispras.ru, r...@twiddle.net, "peter maydell"
>> , qemu-devel@nongnu.org,
>>
On Apr 7, 2017, at 3:08 AM, Jiahuan Zhang wrote:
On 7 April 2017 at 08:26, Jiahuan Zhang
wrote:
On 6 April 2017 at 19:58, G 3 wrote:
On Apr 6, 2017, at 12:00 PM, qemu-devel-requ...@nongnu.org wrote:
Dear QEMU developers,
I need
Am 07.04.2017 um 14:20 hat Stefan Hajnoczi geschrieben:
> On Thu, Apr 06, 2017 at 06:01:48PM +0300, Alberto Garcia wrote:
> > Here are the results (subcluster size in brackets):
> >
> > |-++-+---|
> > | cluster size |
On Fri, Apr 07, 2017 at 02:54:12PM +0800, Fam Zheng wrote:
> @@ -4413,6 +4416,10 @@ void bdrv_set_aio_context(BlockDriverState *bs,
> AioContext *new_context)
> aio_context_acquire(new_context);
> bdrv_attach_aio_context(bs, new_context);
> aio_context_release(new_context);
> +
Am 07.04.2017 um 08:54 hat Fam Zheng geschrieben:
> v2: - Drop patch 4 in v1. A second thought made me feel neither it nor Kevin's
> suggestion to move the BH process to bdrv_drain_recurse/BDRV_POLL_WHILE
> is a complete fix. So leave it for a separate patch.
> - Add rev-by to
Am 06.04.2017 um 18:40 hat Eric Blake geschrieben:
> On 04/06/2017 10:01 AM, Alberto Garcia wrote:
> > I thought of three alternatives for storing the subcluster bitmaps. I
> > haven't made my mind completely about which one is the best one, so
> > I'd like to present all three for discussion.
On Fri 07 Apr 2017 02:20:21 PM CEST, Stefan Hajnoczi wrote:
>> Here are the results when writing to an empty 40GB qcow2 image with no
>> backing file. The numbers are of course different but as you can see
>> the patterns are similar:
>>
>>
On Thu, Apr 06, 2017 at 06:01:48PM +0300, Alberto Garcia wrote:
> Here are the results (subcluster size in brackets):
>
> |-++-+---|
> | cluster size | subclusters=on | subclusters=off | Max L2 cache size |
>
- Original Message -
> From: "Alex Bennée"
> To: "Paolo Bonzini"
> Cc: dovga...@ispras.ru, r...@twiddle.net, "peter maydell"
> , qemu-devel@nongnu.org,
> mt...@greensocs.com, "fred konrad"
Paolo Bonzini writes:
> On 05/04/2017 15:25, Alex Bennée wrote:
>> This ensures each time the vCPU thread reads the icount we update the
>> master timer_state.qemu_icount field. This way as long as updates are
>> in BQL protected sections (which they should be) the
On Fri, Apr 07, 2017 at 09:30:33AM +0800, 858585 jemmy wrote:
> On Thu, Apr 6, 2017 at 10:02 PM, Stefan Hajnoczi wrote:
> > On Wed, Apr 05, 2017 at 05:27:58PM +0800, jemmy858...@gmail.com wrote:
> >
> > A proper solution is to refactor the synchronous code to make it
> >
Do not do extra call to _get_block_status()
Signed-off-by: Vladimir Sementsov-Ogievskiy
---
Also, I'm not sure about last line:
s->status = s->target_has_backing ? BLK_BACKING_FILE : BLK_DATA;
(which is equal to old code)
may be, it should be
s->status =
On Fri, Apr 07, 2017 at 09:30:33AM +0800, 858585 jemmy wrote:
> On Thu, Apr 6, 2017 at 10:02 PM, Stefan Hajnoczi wrote:
> > On Wed, Apr 05, 2017 at 05:27:58PM +0800, jemmy858...@gmail.com wrote:
> >> From: Lidong Chen
> >>
> >> when migration with
> From: mttcg-requ...@listserver.greensocs.com
> [mailto:mttcg-requ...@listserver.greensocs.com]
> On 04/04/2017 07:37, Pavel Dovgalyuk wrote:
> >> -icount -= (cpu->icount_decr.u16.low + cpu->icount_extra);
> >> +/* Take into account what has run */
> >> +icount +=
From: Jing Liu
To ensure that we do not keep any 3270 sockets where the client is not
connected anymore, we send a packet with the timing mark option after
ten minutes of client inactivity. If the client does not answer it,
then the socket will be closed
From: Jing Liu
This introduces a chr_event handler to handle the 3270 connection
and disconnection events.
Signed-off-by: Jing Liu
Reviewed-by: QingFeng Hao
Reviewed-by: Dong Jia Shi
From: Jing Liu
Mark 3270 as non-migratable for the experimental stage. Enable
the 3270 device so that we can use x3270 client to operate the guest.
Run qemu with the arguments:
-chardev socket,id=char3270_0,host=0.0.0.0,port=23,nowait,server,tn3270 \
-device
From: Jing Liu
This introduces the input and output handlers for 3270 device, setting
up the data tunnel among guest kernel, qemu and the 3270 client.
After the client connected and TN3270 handshake done, signal the not-ready
to ready status by an unsolicited
101 - 200 of 293 matches
Mail list logo