Turned out that security_model=mapped can't cope with symlinks in the
host file system.
Instead, security_model=passthrough works as expected. OTOH, I'll have
to check, whether this mode already provides a safe chroot, or guest can
escape and damage the host system.
The wiki page needs some more
On Tue, Aug 07, 2018 at 05:12:07PM +0800, guangrong.x...@gmail.com wrote:
> From: Xiao Guangrong
>
> ram_find_and_save_block() can return negative if any error hanppens,
> however, it is completely ignored in current code
Could you hint me where we'll return an error?
(Anyway I agree that the
Can you simply put a
echo $solaris
right before the "if test "$darwin" != "yes" -a "$mingw32" != "yes" -a
"$solaris" != yes -a" line in the configure script, and then run
configure again? You then should see the contents of the $solaris
variable.
And what do you get if you run
On Tue, Aug 07, 2018 at 05:12:06PM +0800, guangrong.x...@gmail.com wrote:
> From: Xiao Guangrong
>
> flush_compressed_data() needs to wait all compression threads to
> finish their work, after that all threads are free until the
> migration feeds new request to them, reducing its call can
On Tue, Aug 07, 2018 at 05:12:04PM +0800, guangrong.x...@gmail.com wrote:
> From: Xiao Guangrong
>
> Detecting zero page is not a light work, moving it to the thread to
> speed the main thread up, btw, handling ram_release_pages() for the
> zero page is moved to the thread as well
>
>
[Expired for QEMU because there has been no activity for 60 days.]
** Changed in: qemu
Status: Incomplete => Expired
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1463172
Title:
[Expired for QEMU because there has been no activity for 60 days.]
** Changed in: qemu
Status: Incomplete => Expired
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1463812
Title:
[Expired for qemu (Ubuntu) because there has been no activity for 60
days.]
** Changed in: qemu (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1463172
On Tue, Aug 07, 2018 at 12:33:30AM -0400, John Snow wrote:
> Most jobs do the same thing when they leave their running loop:
> - Store the return code in a structure
> - wait to receive this structure in the main thread
> - signal job completion via job_completed
>
> More seriously, when we
On Tue, Aug 07, 2018 at 08:29:54AM -0500, Eric Blake wrote:
> On 08/07/2018 04:12 AM, guangrong.x...@gmail.com wrote:
> > From: Xiao Guangrong
> >
> > Instead of putting the main thread to sleep state to wait for
> > free compression thread, we can directly post it out as normal
> > page that
On Tue, Aug 07, 2018 at 12:33:34AM -0400, John Snow wrote:
> Change the manual deferment to stream_complete into the implicit
> callback to job_exit.
>
> Signed-off-by: John Snow
Reviewed-by: Jeff Cody
> ---
> block/stream.c | 23 ---
> 1 file changed, 8 insertions(+), 15
On Tue, Aug 07, 2018 at 12:33:33AM -0400, John Snow wrote:
> Change the manual deferment to mirror_exit into the implicit
> callback to job_exit and the mirror_exit callback.
>
> Signed-off-by: John Snow
Reviewed-by: Jeff Cody
> ---
> block/mirror.c | 27 +++
> 1 file
On Wed, Aug 08, 2018 at 12:58:32AM +0300, Michael S. Tsirkin wrote:
> At least with VTD, it seems entirely possible to change e.g. a PMD
> atomically to point to a different set of PTEs, then flush.
> That will allow removing memory at high granularity for
> an arbitrary device without mdev or
On Tue, Aug 07, 2018 at 12:33:32AM -0400, John Snow wrote:
> Change the manual deferment to commit_complete into the implicit
> callback to job_exit.
>
> Signed-off-by: John Snow
> ---
> block/commit.c | 19 +--
> 1 file changed, 5 insertions(+), 14 deletions(-)
>
> diff --git
On Tue, Aug 07, 2018 at 01:31:24PM -0600, Alex Williamson wrote:
> We use a VFIOContainer to associate an AddressSpace to one or more
> VFIOGroups. The VFIOContainer represents the DMA context for that
> AdressSpace for those VFIOGroups and is synchronized to changes in
> that AddressSpace via a
Hello,
On behalf of the QEMU Team, I'd like to announce the availability of the
fifth release candidate for the QEMU 3.0 release. This release is meant
for testing purposes and should not be used in a production environment.
http://download.qemu-project.org/qemu-3.0.0-rc4.tar.xz
On Tue, Aug 07, 2018 at 10:35:05AM -0600, Alex Williamson wrote:
> On Tue, 7 Aug 2018 21:10:21 +0800
> Peter Xu wrote:
>
> > On Mon, Jul 30, 2018 at 05:14:21PM -0600, Alex Williamson wrote:
> > > We use a VFIOContainer to associate an AddressSpace to one or more
> > > VFIOGroups. The
On 08/07/2018 05:53 PM, Dr. David Alan Gilbert wrote:
* Wei Wang (wei.w.w...@intel.com) wrote:
On 08/07/2018 03:39 PM, Peter Xu wrote:
On Tue, Jul 31, 2018 at 06:01:18PM +0800, Wei Wang wrote:
When "nbits = 0", which means no bits to mask, this macro is expected to
return 0, instead of
On 08/07/2018 08:17 PM, Peter Xu wrote:
On Tue, Aug 07, 2018 at 04:21:15PM +0800, Wei Wang wrote:
On 08/07/2018 03:39 PM, Peter Xu wrote:
On Tue, Jul 31, 2018 at 06:01:18PM +0800, Wei Wang wrote:
When "nbits = 0", which means no bits to mask, this macro is expected to
return 0, instead of
On Tue, Aug 07, 2018 at 02:08:26PM -0600, Alex Williamson wrote:
> On Tue, 7 Aug 2018 22:44:11 +0300
> "Michael S. Tsirkin" wrote:
>
> > On Tue, Aug 07, 2018 at 01:31:22PM -0600, Alex Williamson wrote:
> > > A simple true/false internal state does not allow multiple users. Fix
> > > this within
On Tue, Aug 07, 2018 at 04:40:33PM -0600, Alex Williamson wrote:
> Maybe some of these will evolve over time, SVA efforts are working on
> some of these interfaces, but apparently device assignment users have
> been getting along just fine without ballooning for many years.
But not any more I
OK, finally got some time to try it out, I'm using
c42634d8e3428cfa60672c3ba89cabefc720cde9 from rr-180725.
Replay works well as far as I can tell, so I moved to the reverse debugging:
/home/ciro/bak/git/linux-kernel-module-cheat/out/x86_
Hi
On Wed, Aug 8, 2018 at 12:18 AM, Peter Wu wrote:
> Fixes repeated memory leaks of 18 bytes when using VNC:
>
> Direct leak of 831024 byte(s) in 46168 object(s) allocated from:
> ...
> #4 0x7f6d2f919bdd in g_strdup_vprintf glib/gstrfuncs.c:514
> #5 0x56085cdcf660 in
Ping
On 06/29/2018 06:47 PM, Tony Krowiak wrote:
From: Tony Krowiak
This patch series is the QEMU counterpart to the KVM/kernel support for
guest dedicated crypto adapters. The KVM/kernel model is built on the
VFIO mediated device framework and provides the infrastructure for
granting
On Wed, 8 Aug 2018 00:58:32 +0300
"Michael S. Tsirkin" wrote:
> On Tue, Aug 07, 2018 at 01:53:03PM -0600, Alex Williamson wrote:
> > On Tue, 7 Aug 2018 22:44:56 +0300
> > "Michael S. Tsirkin" wrote:
> >
> > > On Tue, Aug 07, 2018 at 01:31:21PM -0600, Alex Williamson wrote:
> > > > v3:
> >
** Changed in: qemu
Status: New => 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/1785734
Title:
movdqu partial write at page boundary
Status in QEMU:
Confirmed
Bug
Fixes repeated memory leaks of 18 bytes when using VNC:
Direct leak of 831024 byte(s) in 46168 object(s) allocated from:
...
#4 0x7f6d2f919bdd in g_strdup_vprintf glib/gstrfuncs.c:514
#5 0x56085cdcf660 in buffer_init util/buffer.c:59
#6 0x56085ca6a7ec in
On Tue, Aug 07, 2018 at 01:53:03PM -0600, Alex Williamson wrote:
> On Tue, 7 Aug 2018 22:44:56 +0300
> "Michael S. Tsirkin" wrote:
>
> > On Tue, Aug 07, 2018 at 01:31:21PM -0600, Alex Williamson wrote:
> > > v3:
> > > - Drop "nested" term in commit log (David)
> > > - Adopt suggested wording
Public bug reported:
Version: 2.9.1
The primary symptom is resolving symlink fails w/ error "too many levels
of symbolic links".
My analysis showed that local_readlink() uses local_open_nofollow() to
open the file and then tries to read it. local_open_nofollow() then
tries to open the file w/
This is a part of a class of related problems for qemu linux-user, in
that any non-atomic store is not validated before initiating a partial
write.
For instance, qemu-x86_64, built for arm32, would show this same partial
store problem for any 64-bit write crossing a page boundary because we
are
On 08/07/2018 03:21 PM, Leonid Bloch wrote:
The default cache-clean-interval is set to 30 seconds, in order to lower
the overhead of the qcow2 caches.
Signed-off-by: Leonid Bloch
---
+++ b/qapi/block-core.json
@@ -2830,7 +2830,8 @@
#
# @cache-clean-interval: clean unused entries in the
The caches are now recalculated upon image resizing. This is done
because the new default behavior of assigning a sufficient L2 cache to
cover the entire image implies that the cache will still be sufficient
after an image resizing.
Signed-off-by: Leonid Bloch
---
block/qcow2.c | 8
1
Sufficient L2 cache can noticeably improve the performance when using
large images with frequent I/O. The memory overhead is not significant
in most cases, as the cache size is only 1 MB for each 8 GB of virtual
image size (with the default cluster size of 64 KB). For cases with very
large images
The default cache-clean-interval is set to 30 seconds, in order to lower
the overhead of the qcow2 caches.
Signed-off-by: Leonid Bloch
---
block/qcow2.c| 2 +-
block/qcow2.h| 1 +
docs/qcow2-cache.txt | 3 +--
qapi/block-core.json | 3 ++-
qemu-options.hx | 2 +-
5 files
Signed-off-by: Leonid Bloch
---
docs/qcow2-cache.txt | 3 +++
qemu-options.hx | 9 ++---
2 files changed, 9 insertions(+), 3 deletions(-)
diff --git a/docs/qcow2-cache.txt b/docs/qcow2-cache.txt
index 8a09a5cc5f..5bf2a8ad29 100644
--- a/docs/qcow2-cache.txt
+++ b/docs/qcow2-cache.txt
Signed-off-by: Leonid Bloch
---
block/qcow2.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/block/qcow2.c b/block/qcow2.c
index 453a6377ac..a54e20402b 100644
--- a/block/qcow2.c
+++ b/block/qcow2.c
@@ -1321,7 +1321,7 @@ static int coroutine_fn
This series makes the qcow2 L2 cache cover the entire image by default.
The importance of this change is in noticeable performance improvement,
especially with heavy random I/O. The memory overhead is not big in most
cases, as only 1 MB of cache for every 8 GB of image size is used.
For cases with
On Tue, 7 Aug 2018 22:44:11 +0300
"Michael S. Tsirkin" wrote:
> On Tue, Aug 07, 2018 at 01:31:22PM -0600, Alex Williamson wrote:
> > A simple true/false internal state does not allow multiple users. Fix
> > this within the existing interface by converting to a counter, so long
> > as the
On 08/06/2018 05:04 PM, Eric Blake wrote:
On 06/18/2018 11:44 AM, Kevin Wolf wrote:
From: Greg Kurz
Removing a drive with drive_del while it is being used to run an I/O
intensive workload can cause QEMU to crash.
...
Test 83 sets up a client that intentionally disconnects at critical
On Tue, 7 Aug 2018 22:44:56 +0300
"Michael S. Tsirkin" wrote:
> On Tue, Aug 07, 2018 at 01:31:21PM -0600, Alex Williamson wrote:
> > v3:
> > - Drop "nested" term in commit log (David)
> > - Adopt suggested wording in ccw code (Cornelia)
> > - Explain balloon inhibitor usage in vfio common
On Tue, Aug 07, 2018 at 08:27:30PM +0100, Mark Cave-Ayland wrote:
> On 06/08/18 21:11, Eduardo Habkost wrote:
> > On Sun, Aug 05, 2018 at 12:28:50PM +0100, Mark Cave-Ayland wrote:
> > > For the older machines (such as Mac and SPARC) the DT nodes representing
> > > bootdevices for disk nodes are
On Tue, Aug 07, 2018 at 01:31:21PM -0600, Alex Williamson wrote:
> v3:
> - Drop "nested" term in commit log (David)
> - Adopt suggested wording in ccw code (Cornelia)
> - Explain balloon inhibitor usage in vfio common (Peter)
> - Fix to call inhibitor prior to re-using existing containers
>
On Tue, Aug 07, 2018 at 01:31:22PM -0600, Alex Williamson wrote:
> A simple true/false internal state does not allow multiple users. Fix
> this within the existing interface by converting to a counter, so long
> as the counter is elevated, ballooning is inhibited.
>
> Reviewed-by: David
On 08/07/2018 05:34 AM, Aleksandar Markovic wrote:
> We are introducing a new MIPS platform - called nanoMIPS - to the QEMU.
>
> Besides providing new functionality, we would like to integrate into QEMU
> some basic testing capabilities for that new platform. Something like this:
>
> Enable user
A simple true/false internal state does not allow multiple users. Fix
this within the existing interface by converting to a counter, so long
as the counter is elevated, ballooning is inhibited.
Reviewed-by: David Hildenbrand
Reviewed-by: Peter Xu
Reviewed-by: Cornelia Huck
Signed-off-by: Alex
If a vfio assigned device makes use of a physical IOMMU, then memory
ballooning is necessarily inhibited due to the page pinning, lack of
page level granularity at the IOMMU, and sufficient notifiers to both
remove the page on balloon inflation and add it back on deflation.
However, not all
We use a VFIOContainer to associate an AddressSpace to one or more
VFIOGroups. The VFIOContainer represents the DMA context for that
AdressSpace for those VFIOGroups and is synchronized to changes in
that AddressSpace via a MemoryListener. For IOMMU backed devices,
maintaining the DMA context
v3:
- Drop "nested" term in commit log (David)
- Adopt suggested wording in ccw code (Cornelia)
- Explain balloon inhibitor usage in vfio common (Peter)
- Fix to call inhibitor prior to re-using existing containers
to avoid gap that pinning may have occurred in set container
ioctl (self)
Remove KVM specific tests in balloon_page(), instead marking
ballooning as inhibited without KVM_CAP_SYNC_MMU support.
Reviewed-by: David Hildenbrand
Reviewed-by: Peter Xu
Reviewed-by: Cornelia Huck
Signed-off-by: Alex Williamson
---
accel/kvm/kvm-all.c| 4
On 06/08/18 21:11, Eduardo Habkost wrote:
On Sun, Aug 05, 2018 at 12:28:50PM +0100, Mark Cave-Ayland wrote:
For the older machines (such as Mac and SPARC) the DT nodes representing
bootdevices for disk nodes are irregular for mainly historical reasons, and
should be handled on an individual
* Zhang Chen (zhangc...@gmail.com) wrote:
> On Sat, Jul 28, 2018 at 2:51 AM, Dr. David Alan Gilbert > wrote:
>
> > * Zhang Chen (zhangc...@gmail.com) wrote:
> > > We record the address of the dirty pages that received,
> > > it will help flushing pages that cached into SVM.
> > >
> > > Here, it
Gerd Hoffmann writes:
> On Fri, Jul 20, 2018 at 05:40:18PM -0400, Bandan Das wrote:
>> For large buffers, write may not copy the full buffer. For example,
>> on Linux, write imposes a limit of 0x7000. Note that this does
>> not fix >4G transfers but ~>2G files will transfer successfully.
>
>
On 08/07/2018 10:52 AM, Eric Blake wrote:
> On 08/06/2018 11:33 PM, John Snow wrote:
>> Signed-off-by: John Snow
>> ---
>> blockdev.c | 8
>> qapi/block-core.json | 3 ++-
>> 2 files changed, 10 insertions(+), 1 deletion(-)
>>
>
>> +++ b/qapi/block-core.json
>> @@
* Zhang Chen (zhangc...@gmail.com) wrote:
> We should not load PVM's state directly into SVM, because there maybe some
> errors happen when SVM is receving data, which will break SVM.
>
> We need to ensure receving all data before load the state into SVM. We use
> an extra memory to cache these
Has this issue ever been fixed? If not, is there still interest in
fixing it? Or could we close this ticket nowadays?
** 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.
Start several async requests instead of read chunk by chunk.
Iotest 026 output is changed, as because of async io error path has
changed.
Signed-off-by: Vladimir Sementsov-Ogievskiy
---
block/qcow2.c | 47 ++
tests/qemu-iotests/026.out
Hi all!
Here is an asynchronous scheme for handling fragmented qcow2
reads and writes. Both qcow2 read and write functions loops through
sequential portions of data. The series aim it to parallelize these
loops iterations.
It improves performance for fragmented qcow2 images, I've tested it
as
Start several async requests instead of read chunk by chunk.
Signed-off-by: Vladimir Sementsov-Ogievskiy
---
block/qcow2.c | 208 --
1 file changed, 204 insertions(+), 4 deletions(-)
diff --git a/block/qcow2.c b/block/qcow2.c
index
Memory allocation may become less efficient for encrypted case. It's a
payment for further asynchronous scheme.
Signed-off-by: Vladimir Sementsov-Ogievskiy
---
block/qcow2.c | 114 --
1 file changed, 64 insertions(+), 50 deletions(-)
diff
Split out block which will be reused in async scheme.
Signed-off-by: Vladimir Sementsov-Ogievskiy
---
block/qcow2.c | 138 --
1 file changed, 86 insertions(+), 52 deletions(-)
diff --git a/block/qcow2.c b/block/qcow2.c
index
We don't need locking for encryption code.
Signed-off-by: Vladimir Sementsov-Ogievskiy
---
block/qcow2.c | 20
1 file changed, 12 insertions(+), 8 deletions(-)
diff --git a/block/qcow2.c b/block/qcow2.c
index 41def07c67..65e3ca00e2 100644
--- a/block/qcow2.c
+++
From: "Denis V. Lunev"
We are not working with a shared state data in the decruption code and
thus this operation is safe. On the other hand this significantly
reduces the scope of the lock.
Signed-off-by: Denis V. Lunev
---
block/qcow2.c | 14 --
1 file changed, 8 insertions(+),
Move local variables related to individual loop iteration into while
block.
Signed-off-by: Vladimir Sementsov-Ogievskiy
---
block/qcow2.c | 9 -
1 file changed, 4 insertions(+), 5 deletions(-)
diff --git a/block/qcow2.c b/block/qcow2.c
index 4d669432d1..88b3fb8080 100644
---
Hi Geert,
On 08/07/2018 05:32 PM, Geert Uytterhoeven wrote:
> Hi Eric,
>
> On Tue, Aug 7, 2018 at 4:19 PM Auger Eric wrote:
>> On 07/25/2018 04:34 PM, Geert Uytterhoeven wrote:
>>> Add a fallback for instantiating generic devices without a type-specific
>>> or compatible-specific instantation
On Tue, 7 Aug 2018 21:10:21 +0800
Peter Xu wrote:
> On Mon, Jul 30, 2018 at 05:14:21PM -0600, Alex Williamson wrote:
> > We use a VFIOContainer to associate an AddressSpace to one or more
> > VFIOGroups. The VFIOContainer represents the DMA context for that
> > AdressSpace for those VFIOGroups
On 08/07/18 14:19, Laszlo Ersek wrote:
> On 08/07/18 09:04, Jing Liu wrote:
>> Add hint to firmware (e.g. SeaBIOS) to reserve addtional
>> IO/MEM/PREF spaces for legacy pci-pci bridge, to enable
>> some pci devices hotplugging whose IO/MEM/PREF spaces
>> requests are larger than the ones in
On 7 August 2018 at 16:47, Markus Armbruster wrote:
> Peter Maydell writes:
>
>> On 7 August 2018 at 14:09, Daniel P. Berrangé wrote:
>>> On Tue, Aug 07, 2018 at 03:07:07PM +0200, Thomas Huth wrote:
But 864036e251f54c9 was never part of an official QEMU release, was it?
Or did it go
Ah, I see:
"in a future QEMU release we may drop support for those hosts unless
somebody volunteers to help us with maintaining them (and can provide
build/CI machines)."
OK, so I happily volunteer an account on my machine to help maintain
this.
"What's the content of the $solaris variable at
"The libgcrypt-config command should be in $PATH"
I'm sorry - I don't understand. Isn't $PATH a list of directories? I
need to put a command in there? I'm clearly missing something here.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to
Peter Maydell writes:
> On 7 August 2018 at 14:09, Daniel P. Berrangé wrote:
>> On Tue, Aug 07, 2018 at 03:07:07PM +0200, Thomas Huth wrote:
>>> But 864036e251f54c9 was never part of an official QEMU release, was it?
>>> Or did it go into a stable release already? If not, I think you simply
>>>
Hi Eric,
On Tue, Aug 7, 2018 at 4:19 PM Auger Eric wrote:
> On 07/25/2018 04:34 PM, Geert Uytterhoeven wrote:
> > Add a fallback for instantiating generic devices without a type-specific
> > or compatible-specific instantation method. This will be used when no
> > other match is found.
> >
> >
Hi
On Fri, Aug 3, 2018 at 7:36 PM, Marc-André Lureau
wrote:
> Most chardev backend handle write() as discarded data if underlying
> system is disconnected. For unknown historical reasons, the Spice
> backend has "reliable" write. It will wait until the client end is
> reconnected to accept
I think I'd start by seeing if it fails in both or if they're different.
If they're different then you'd follow the series of exceptions that they each
get
and see where they diverge.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
On Thu 28 Jun 2018 02:07:20 AM CEST, Max Reitz wrote:
> Signed-off-by: Max Reitz
Reviewed-by: Alberto Garcia
Berto
On 7 August 2018 at 16:05, Juan Quintela wrote:
> Peter Maydell wrote:
>> So it's better to use a needed-always subsection, which will give
>> the desired behaviour:
>> * new QEMU -> new QEMU: state is always migrated
>> * old QEMU -> new QEMU: migration doesn't fail, and guest
>>will work
* Peter Maydell (peter.mayd...@linaro.org) wrote:
> On 7 August 2018 at 16:05, Juan Quintela wrote:
> > Peter Maydell wrote:
> >> So it's better to use a needed-always subsection, which will give
> >> the desired behaviour:
> >> * new QEMU -> new QEMU: state is always migrated
> >> * old QEMU
* Peter Maydell (peter.mayd...@linaro.org) wrote:
> On 7 August 2018 at 15:57, Dr. David Alan Gilbert wrote:
> > * Gerd Hoffmann (kra...@redhat.com) wrote:
> >> On Fri, Jul 20, 2018 at 10:19:48AM +0200, remy.n...@blade-group.com wrote:
> >> > From: "Remy Noel"
> >> >
> >> > When removing a
On Thu 28 Jun 2018 02:07:28 AM CEST, Max Reitz wrote:
> This function may be implemented by block drivers to derive a directory
> name from a BDS. Concatenating this g_free()-able string with a relative
> filename must result in a valid (not necessarily existing) filename, so
> this is a function
On Thu 28 Jun 2018 02:07:27 AM CEST, Max Reitz wrote:
> bdrv_find_backing_image() should use bdrv_get_full_backing_filename() or
> bdrv_make_absolute_filename() instead of trying to do what those
> functions do by itself.
>
> path_combine_deprecated() can now be dropped, so let's do that.
>
>
On 7 August 2018 at 14:41, Gerd Hoffmann wrote:
> On Tue, Aug 07, 2018 at 03:02:49PM +0200, Marc-André Lureau wrote:
>> Hi
>>
>> On Tue, Aug 7, 2018 at 2:55 PM, Gerd Hoffmann wrote:
>> > On Fri, Aug 03, 2018 at 05:32:35PM +0200, Marc-André Lureau wrote:
>> >> With vga=775 on the Linux command
On Thu 28 Jun 2018 02:07:26 AM CEST, Max Reitz wrote:
> This is a general function for making a filename that is relative to a
> certain BDS absolute.
>
> It calls bdrv_get_full_backing_filename_from_filename() for now, but
> that will be changed in a follow-up patch.
>
> Signed-off-by: Max Reitz
On 7 August 2018 at 15:57, Dr. David Alan Gilbert wrote:
> * Gerd Hoffmann (kra...@redhat.com) wrote:
>> On Fri, Jul 20, 2018 at 10:19:48AM +0200, remy.n...@blade-group.com wrote:
>> > From: "Remy Noel"
>> >
>> > When removing a secondary-vga device and then adding it back (or adding
>> > an
Hi Geert,
On 08/07/2018 05:00 PM, Geert Uytterhoeven wrote:
> Hi Eric,
>
> On Tue, Aug 7, 2018 at 4:18 PM Auger Eric wrote:
>> On 07/25/2018 04:34 PM, Geert Uytterhoeven wrote:
>>> From: Auger Eric
>>>
>>> Up to now the vfio-platform device has been abstract and could not be
>>> instantiated.
On Thu 28 Jun 2018 02:07:25 AM CEST, Max Reitz wrote:
> Make bdrv_get_full_backing_filename() return an allocated string instead
> of placing the result in a caller-provided buffer.
>
> Signed-off-by: Max Reitz
Reviewed-by: Alberto Garcia
Berto
Peter Maydell wrote:
> On 7 August 2018 at 15:49, Juan Quintela wrote:
>> But what I wonder is _why_ we want subsections that are always there.
>> We have:
>>
>> - normal sections
>> int32_t foo
>> int64_t bad;
>>
>> - subsections (always optional)
>> if needed(whatever)
>> int16_t
On Thu 28 Jun 2018 02:07:24 AM CEST, Max Reitz wrote:
> Make bdrv_get_full_backing_filename_from_filename() return an allocated
> string instead of placing the result in a caller-provided buffer.
>
> Signed-off-by: Max Reitz
Reviewed-by: Alberto Garcia
Berto
Hi Eric,
On Tue, Aug 7, 2018 at 4:18 PM Auger Eric wrote:
> On 07/25/2018 04:34 PM, Geert Uytterhoeven wrote:
> > From: Auger Eric
> >
> > Up to now the vfio-platform device has been abstract and could not be
> > instantiated. The integration of a new vfio platform device required
> > creating
On 7 August 2018 at 15:49, Juan Quintela wrote:
> But what I wonder is _why_ we want subsections that are always there.
> We have:
>
> - normal sections
> int32_t foo
> int64_t bad;
>
> - subsections (always optional)
> if needed(whatever)
> int16_t foo2
> int32_t bar2
>
> So
* Gerd Hoffmann (kra...@redhat.com) wrote:
> On Fri, Jul 20, 2018 at 10:19:48AM +0200, remy.n...@blade-group.com wrote:
> > From: "Remy Noel"
> >
> > When removing a secondary-vga device and then adding it back (or adding
> > an other one), qemu aborts with:
> > "RAMBlock
On 08/06/2018 11:33 PM, John Snow wrote:
Signed-off-by: John Snow
---
blockdev.c | 8
qapi/block-core.json | 3 ++-
2 files changed, 10 insertions(+), 1 deletion(-)
+++ b/qapi/block-core.json
@@ -1518,7 +1518,8 @@
{ 'command': 'block-commit',
'data': {
Glad to see such a quick fix, and ASAN looks like a great tool :)
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1785670
Title:
Guest(ubuntu 18.04) crashes when trying uploading file
Status in
Peter Maydell wrote:
> On 7 August 2018 at 15:40, Juan Quintela wrote:
>> But having 3 subsections with the same needed function ... we could have
>> a single subsection.
>
> I wanted to keep the change small here since we're very
> late in the release cycle, so I kept it to a change
> that
On Thu 28 Jun 2018 02:07:21 AM CEST, Max Reitz wrote:
> This function queries a node; since we cannot do that right now, it
> executes query-named-block-nodes and returns the matching node's object.
>
> Signed-off-by: Max Reitz
> ---
> tests/qemu-iotests/iotests.py | 7 +++
> 1 file changed,
Peter Maydell wrote:
> On 7 August 2018 at 15:32, Juan Quintela wrote:
>> Peter Maydell wrote:
>>> On 7 August 2018 at 14:17, Juan Quintela wrote:
>>> Also, what prompted me to write this patch was that for 3.0
>>> I had to fix several bugs where subsections had been written
>>> with no needed
On 7 August 2018 at 15:40, Juan Quintela wrote:
> But having 3 subsections with the same needed function ... we could have
> a single subsection.
I wanted to keep the change small here since we're very
late in the release cycle, so I kept it to a change
that restores the intent of the code, ie
On 07/08/2018 16:30, Gerd Hoffmann wrote:
>>>
>>>-display spice,client=yes
>> There is no -display spice, atm.
>>
>> However there is a -display vnc.
> That should not be there. Now that we have a deprecation process
> I should probably actually deprecate it in favor of -vnc.
>
>> It's a bit
Peter Maydell wrote:
> Contrary to the the impression given in docs/devel/migration.rst,
> the migration code does not run the pre_load hook for a
> subsection unless the subsection appears on the wire, and so
> this is not a place where you can set the default value for
> state for the
Peter Maydell wrote:
> Currently the migration code incorrectly treats a subsection with
> no .needed function pointer as if it was the subsection list
> terminator -- it is ignored and so is everything after it.
> Work around this by giving various M profile vmstate structs
> a 'needed' function
On 7 August 2018 at 15:32, Juan Quintela wrote:
> Peter Maydell wrote:
>> On 7 August 2018 at 14:17, Juan Quintela wrote:
>> Also, what prompted me to write this patch was that for 3.0
>> I had to fix several bugs where subsections had been written
>> with no needed function and the migration
Peter Maydell wrote:
> Commit 6692aac411199064 accidentally introduced a second initialization
> of the .subsections field of vmstate_gicv3_cpu, instead of adding
> the new subsection to the existing list. The effect of this was
> probably that migration of GICv3 with virtualization enabled was
>
1 - 100 of 216 matches
Mail list logo
