On Mon, 11/27 15:43, Roman Kagan wrote:
> It's going to be useful, in particular, in VMBus code massively using
> uuids aka GUIDs.
>
> Signed-off-by: Roman Kagan
> ---
> v1 -> v2:
> - drop dedicated testcase (for it was of no value) and incorporate
>is_null and is_equal assertions into uuid_
Also on the qemu side this is "works as intended" and workarounds are
documented in this bug.
So we should set that bug status as well - looking back given it was mostly a
discussion I guess "opinion" is the best close status in this case.
** Changed in: qemu (Ubuntu)
Status: Won't Fix =>
Umm, the latter is the official way to go, but only in latter libvirt versions.
https://libvirt.org/git/?p=libvirt.git;a=commit;h=28907b0043fbf71085a798372ab9c816ba043b93
I'm adding a libvirt bug task for the bionic merge to pick that up
"explicitly"
** Changed in: qemu (Ubuntu)
Status: Ne
Note: Depending on the case you might also get lucky with "shareable"
and/or "readonly" disk attributes.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1716028
Title:
qemu 2.10 locks images with no
28.11.2017 10:14, Vladimir Sementsov-Ogievskiy wrote:
The test creates two vms (vm_a, vm_b), create dirty bitmap in
the first one, do several writes to corresponding device and
then migrate vm_a to vm_b with dirty bitmaps.
For now, only migration through shared storage for persistent
bitmaps is
Add version of qcow2_reopen_bitmaps_rw, which do the same work but
also return a hint about was header updated or not. This will be
used in the following fix for bitmaps reloading after migration.
Signed-off-by: Vladimir Sementsov-Ogievskiy
---
block/qcow2.h| 2 ++
block/qcow2-bitmap.c
The test creates two vms (vm_a, vm_b), create dirty bitmap in
the first one, do several writes to corresponding device and
then migrate vm_a to vm_b with dirty bitmaps.
For now, only migration through shared storage for persistent
bitmaps is available, so it is tested here. Only offline variant
is
- add comment
- allow int timeout and disallow bool (which has special
meaning for pull_event())
- remove unreachable 'return None'
Signed-off-by: Vladimir Sementsov-Ogievskiy
---
scripts/qemu.py | 10 +++---
1 file changed, 7 insertions(+), 3 deletions(-)
diff --git a/scripts/qemu.py b/s
Consider migration with shared storage. Persistent bitmaps are stored
on bdrv_inactivate. Then, on destination
process_incoming_migration_bh() calls bdrv_invalidate_cache_all() which
leads to qcow2_load_autoloading_dirty_bitmaps() which fails if bitmaps
are already loaded on destination start. In t
Hi all.
This fix may be considered as a material for 2.11, or may be postponed
to 2.12, on your choice.
The core patch is 02.
Vladimir Sementsov-Ogievskiy (4):
qcow2-bitmap: add qcow2_reopen_bitmaps_rw_hint()
qcow2: handle reopening bitmaps on bdrv_invalidate_cache
scripts/qemu.py: tiny en
在 2017/11/28 上午12:02, Cornelia Huck 写道:
On Mon, 27 Nov 2017 16:53:04 +0100
Pierre Morel wrote:
On 27/11/2017 16:30, Cornelia Huck wrote:
On Mon, 27 Nov 2017 16:24:08 +0100
Pierre Morel wrote:
On 27/11/2017 15:34, Cornelia Huck wrote:
On Mon, 27 Nov 2017 12:02:55 +0100
Cornelia Huck
在 2017/11/27 下午7:13, Thomas Huth 写道:
On 27.11.2017 11:09, Yi Min Zhao wrote:
在 2017/11/27 下午2:59, Thomas Huth 写道:
On 25.11.2017 14:49, Pierre Morel wrote:
On 24/11/2017 07:19, Yi Min Zhao wrote:
在 2017/11/23 下午8:18, Thomas Huth 写道:
On 23.11.2017 13:07, Yi Min Zhao wrote:
在 2017/11/23 下午6
On Tue, 11/28 12:46, linzhecheng wrote:
> If we create a thread with QEMU_THREAD_DETACHED mode, QEMU may get a segfault
> in a low probability.
>
> The backtrace is:
> #0 0x7f46c60291d7 in __GI_raise (sig=sig@entry=6) at
> ../nptl/sysdeps/unix/sysv/linux/raise.c:56
> #1 0x7f46c602a8c8
Signed-off-by: Yoni Bettan
---
hw/pci/pci.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/hw/pci/pci.c b/hw/pci/pci.c
index 02f6f2f37a..d2bf749251 100644
--- a/hw/pci/pci.c
+++ b/hw/pci/pci.c
@@ -2014,7 +2014,7 @@ static void pci_qdev_realize(DeviceState *qdev, Error
**errp
* according to Eduardo Habkost's commit
fd3b02c8896d597dd8b9e053dec579cf0386aee1
* since all PCIEs now implement INTERFACE_PCIE_DEVICE we
don't need this field anymore
Signed-off-by: Yoni Bettan
---
hw/block/nvme.c| 1 -
hw/net/e1000e.c
On Tue, Nov 28, 2017 at 12:29:09AM +0100, Kevin Wolf wrote:
> Am 23.11.2017 um 18:57 hat Fam Zheng geschrieben:
> > Jeff's block job patch made the latent drain bug visible, and I find this
> > patch, which by itself also makes some sense, can hide it again. :) With it
> > applied we are at least b
On Mon, Nov 27, 2017 at 11:12:43PM -0200, Eduardo Habkost wrote:
> On Mon, Nov 27, 2017 at 12:52:09PM +1100, David Gibson wrote:
> > On Sat, Nov 25, 2017 at 01:16:07PM -0200, Eduardo Habkost wrote:
> > > platform_bus_create_devtree() already rejects all dynamic sysbus
> > > devices except TYPE_ETSE
If we create a thread with QEMU_THREAD_DETACHED mode, QEMU may get a segfault
in a low probability.
The backtrace is:
#0 0x7f46c60291d7 in __GI_raise (sig=sig@entry=6) at
../nptl/sysdeps/unix/sysv/linux/raise.c:56
#1 0x7f46c602a8c8 in __GI_abort () at abort.c:90
#2 0x008543c9
Guest state should not be touched if VM is stopped, unfortunately we
didn't check running state and tried to drain tx queue unconditionally
in virtio_net_set_status(). A crash was then noticed as a migration
destination when user type quit after virtqueue state is loaded but
before region cache is
The following changes since commit 5e19aed59ab48ca3c7f1e2da203eed27b91bef2d:
Merge remote-tracking branch 'remotes/dgibson/tags/ppc-for-2.11-20171127'
into staging (2017-11-27 11:16:20 +)
are available in the git repository at:
https://github.com/jasowang/qemu.git tags/net-pu
On Tue, 11/28 09:50, linzhecheng wrote:
> If we create a thread with QEMU_THREAD_DETACHED mode, QEMU may get a segfault
> in a low probability.
>
> The backtrace is:
> arg=arg@entry=0x3f5cf70, mode=mode@entry=1) at
> util/qemu_thread_posix.c:512
> at io/task.c:141
> destroy=destroy@e
If we create a thread with QEMU_THREAD_DETACHED mode, QEMU may get a segfault
in a low probability.
The backtrace is:
#0 0x7f46c60291d7 in __GI_raise (sig=sig@entry=6) at
../nptl/sysdeps/unix/sysv/linux/raise.c:56
#1 0x7f46c602a8c8 in __GI_abort () at abort.c:90
#2 0x008543c9
On Mon, 11/27 13:02, Peter Maydell wrote:
> On 26 November 2017 at 22:13, Brad Smith wrote:
> > Fix the curses probe with older ncurses (.e.g. 5.7, as used by OpenBSD).
> >
> > ncurses 5.7 requires _XOPEN_SOURCE_EXTENDED to be defined for WACS_*
> > constants.
>
> ncurses 5.7 was released in 200
On Fri, 11/24 17:39, Kevin Wolf wrote:
> Maybe the backtraces would help me understand the problem if they were
> actually there. :-)
Ouch, looks like git-tag(1) doesn't like to store # lines in the message.
Unfortunately I rebooted the laptop and didn't save the vim buffer, thinking it
is already
Interrupt conditions occurring while masked are not being
signaled when later unmasked.
The fix is to raise/lower IRQs when IMASK is changed.
To avoid problems like this in future, consolidate
IRQ pin update logic in one function.
Also fix probable typo "IEVENT_TXF | IEVENT_TXF",
and update IRQ p
On Fri, 11/24 16:24, Kevin Wolf wrote:
> > @@ -693,6 +693,10 @@ This is the protocol-level block driver for accessing
> > regular files.
> > The path to the image file in the local filesystem
> > @item aio
> > Specifies the AIO backend (threads/native, default: threads)
> > +@item locking
> > +
* Cornelia Huck [2017-11-27 13:58:16 +0100]:
> On Mon, 27 Nov 2017 10:20:56 +0800
> Dong Jia Shi wrote:
>
> > * Halil Pasic [2017-11-24 17:39:04 +0100]:
> >
> > >
> > >
> > > On 11/24/2017 05:15 PM, Cornelia Huck wrote:
> > > >>> In theory this should work.
> > > >>>
> > > >>> In reality
* Cornelia Huck [2017-11-27 17:56:07 +0100]:
> On Mon, 27 Nov 2017 16:09:09 +0100
> Boris Fiuczynski wrote:
>
> > On 11/27/2017 03:13 PM, Halil Pasic wrote:
> > >
> > >
> > > On 11/27/2017 02:19 PM, Cornelia Huck wrote:
> > >> On Mon, 27 Nov 2017 14:11:57 +0100
> > >> Halil Pasic wrote:
>
If we create a thread with QEMU_THREAD_DETACHED mode, QEMU may get a segfault
in a low probability.
The backtrace is:
arg=arg@entry=0x3f5cf70, mode=mode@entry=1) at util/qemu_thread_posix.c:512
at io/task.c:141
destroy=destroy@entry=0x0) at io/channel_socket.c:194
The root cause of t
Nope, looks good here. As a note to other commenters, this won't work
unless you are using a kernel compiled with the 4k page size -- default
for PPC64 is 64k.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.ne
On Mon, Nov 27, 2017 at 10:44:34AM +0200, Marcel Apfelbaum wrote:
> On 25/11/2017 17:16, Eduardo Habkost wrote:
> > The only user-creatable sysbus devices in qemu-system-x86_64 are
> > amd-iommu, intel-iommu, and xen-backend. xen-backend is handled
> > by xen_set_dynamic_sysbus(), so we only need
Public bug reported:
qemu-x86_66 GIT HEAD fails on a userspace application that requires
memfd_create with:
"qemu: Unsupported syscall: 319".
memfd_create support needs to be implemented in QEMU.
** Affects: qemu
Importance: Undecided
Status: New
--
You received this bug notific
On Mon, Nov 27, 2017 at 12:52:09PM +1100, David Gibson wrote:
> On Sat, Nov 25, 2017 at 01:16:07PM -0200, Eduardo Habkost wrote:
> > platform_bus_create_devtree() already rejects all dynamic sysbus
> > devices except TYPE_ETSEC_COMMON, so register it as the only
> > allowed dynamic sysbus device fo
On Sat, Nov 25, 2017 at 07:31:19PM +0100, Greg Kurz wrote:
> On Sat, 25 Nov 2017 13:16:07 -0200
> Eduardo Habkost wrote:
>
> > platform_bus_create_devtree() already rejects all dynamic sysbus
> > devices except TYPE_ETSEC_COMMON, so register it as the only
> > allowed dynamic sysbus device for th
On Mon, Nov 27, 2017 at 12:35:15PM +0800, Haozhong Zhang wrote:
> When mmap(2) the backend files, QEMU uses the host page size
> (getpagesize(2)) by default as the alignment of mapping address.
> However, some backends may require alignments different than the page
> size. For example, mmap a devic
** Changed in: qemu
Status: Incomplete => 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/1401798
Title:
Qemu 2.2.0 savevm crash.
Status in QEMU:
Fix Released
Bug description:
On 11/27/2017 06:29 PM, Kevin Wolf wrote:
> Am 23.11.2017 um 18:57 hat Fam Zheng geschrieben:
>> Jeff's block job patch made the latent drain bug visible, and I find this
>> patch, which by itself also makes some sense, can hide it again. :) With it
>> applied we are at least back to the ground w
On 11/27/17 07:02, Peter Maydell wrote:
On 26 November 2017 at 22:13, Brad Smith wrote:
Fix the curses probe with older ncurses (.e.g. 5.7, as used by OpenBSD).
ncurses 5.7 requires _XOPEN_SOURCE_EXTENDED to be defined for WACS_* constants.
ncurses 5.7 was released in 2008 and is now 9 years
Am 23.11.2017 um 18:57 hat Fam Zheng geschrieben:
> Jeff's block job patch made the latent drain bug visible, and I find this
> patch, which by itself also makes some sense, can hide it again. :) With it
> applied we are at least back to the ground where patchew's iotests (make
> docker-test-block@
On 27 November 2017 at 04:52, Philippe Mathieu-Daudé
wrote:
> Hi Francisco,
>
> On 11/26/2017 08:16 PM, Francisco Iglesias wrote:
> > Make tx/rx_data_bytes more generic so they can be reused (when adding
> > support for the Zynqmp Generic QSPI).
> >
> > Signed-off-by: Francisco Iglesias
> > Revi
On 11/23/2017 11:31 AM, Peter Maydell wrote:
> As usual, during this year's KVM Forum we also held the
> QEMU Summit, which is where the more active subsystem
> maintainers meet up for a discussion of various maintenance
> and other project issues. As usual, none of this is set-in-stone
> decisio
On 2017-11-27 17:00, Peter Lieven wrote:
> DIV_ROUND_UP(st.st_size, BDRV_SECTOR_SIZE) was overflowing ret (int) if
> st.st_size is greater than 1TB.
>
> Cc: qemu-sta...@nongnu.org
> Signed-off-by: Peter Lieven
> ---
> block/nfs.c | 7 +++
> 1 file changed, 3 insertions(+), 4 deletions(-)
Th
Surprisingly the GCC compiler transformed my 32 bits access into 4 x 8
bits access in my application code.
So this is not a Qemu issue but I need to find why the compiler is not
generating the code I was expecting.
Sorry for the noise.
JC
Le 27/11/2017 à 21:16, Jean-Christophe DUBOIS a écri
When the boot menu options are present and the guest's
disk has been configured by the zipl tool, then the user
will be presented with an interactive boot menu with
labeled entries. An example of what the menu might look
like:
zIPL v1.37.1-build-20170714 interactive boot menu.
0. default
Set boot menu options for an s390 guest and store them in
the iplb. These options are set via the QEMU command line
option:
-boot menu=on|off[,splash-time=X]
or via the libvirt domain xml:
Where X represents some positive integer representing
milliseconds.
Signed-off-by: C
These patches implement a boot menu for ECKD DASD and SCSI guests on s390x.
The menu will only appear if the disk has been configured for IPL with the
zIPL tool and with the following QEMU command line options:
-boot menu=on[,splash-time=X] and/or -machine loadparm='prompt'
or via the follo
Interactive boot menu for scsi. This follows the same procedure
as the interactive menu for eckd dasd. An example follows:
s390x Enumerated Boot Menu.
3 entries detected. Select from index 0 to 2.
Please choose:
Signed-off-by: Collin L. Walling
---
pc-bios/s390-ccw/bootmap.c | 9
Moved:
memcmp from bootmap.h to libc.h (renamed from _memcmp)
strlen from sclp.c to libc.h (renamed from _strlen)
Added C standard functions:
isdigit
atoi
Added non-C standard function:
itostr
Signed-off-by: Collin L. Walling
Acked-by: Christian Borntraeger
Reviewed-by: fran...@linux
ECKD DASDs have different IPL structures for CDL and LDL
formats. The current Ipl1 and Ipl2 structs follow the CDL
format, so we prepend "EckdCdl" to them. A new struct,
EckdLdlIpl1 is introduced and contains boot info for LDL.
Also introduce structs for IPL stages 1 and 1b and for
disk geometry.
On 11/27/2017 11:49 AM, Mike Frysinger wrote:
> Signed-off-by: Mike Frysinger
> ---
> scripts/git-submodule.sh | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/scripts/git-submodule.sh b/scripts/git-submodule.sh
> index 030617b4ac0c..bc7224a27fe3 100755
> --- a/scripts/gi
Hello Mark,
Did you get any second opinion on this?
Also do you need me to resend the patch with the SPARC keyword in the
patch subject line?
Regards
JC
Le 23/11/2017 à 20:49, Mark Cave-Ayland a écrit :
On 22/11/17 06:32, Jean-Christophe Dubois wrote:
This code is preventing the MMU debu
Hi,
I am using Qemu to emulate a Leon3 based board.
In the software I am running on top of Qemu, I am mapping devices to a
virtual address using MMU table.
Now I am experimenting some issues when I am trying to access some
device (here the UART port at 0x8100) through the MMU mapping (wi
On 11/27/2017 01:58 PM, no-re...@patchew.org wrote:
Hi,
This series failed build test on s390x host. Please find the details below.
Type: series
Subject: [Qemu-devel] [PATCH v1 0/4] Interactive Boot Menu for DASD and SCSI
Guests on s390x
Message-id: 1511808659-8846-1-git-send-email-wall...@lin
On 11/27/2017 12:49 PM, Mike Frysinger wrote:
> Signed-off-by: Mike Frysinger
> ---
> scripts/git-submodule.sh | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/scripts/git-submodule.sh b/scripts/git-submodule.sh
> index 030617b4ac0c..bc7224a27fe3 100755
> --- a/scripts/
> From: Peter Maydell [mailto:peter.mayd...@linaro.org]
> Sent: Saturday, 25 November 2017 10:05
> On 25 November 2017 at 16:43, bzt bzt wrote:
> > Dear Andrew,
> >
> > A month passed, and the maintainers didn't gave a damn about raspi3
> support
> > in qemu. Any ideas?
>
> Sorry this patch fell
On 11/27/2017 01:12 AM, David Gibson wrote:
> On Sun, Nov 26, 2017 at 03:59:01PM -0600, Michael Davidsaver wrote:
>> Signed-off-by: Michael Davidsaver
>> ---
>> hw/i2c/Makefile.objs | 1 +
>> hw/i2c/mpc8540_i2c.c | 307
>> +++
>> hw/i2c/trace-eve
Hi,
This series failed build test on s390x host. Please find the details below.
Type: series
Subject: [Qemu-devel] [PATCH v1 0/4] Interactive Boot Menu for DASD and SCSI
Guests on s390x
Message-id: 1511808659-8846-1-git-send-email-wall...@linux.vnet.ibm.com
=== TEST SCRIPT BEGIN ===
#!/bin/bash
Hi,
This series seems to have some coding style problems. See output below for
more information:
Subject: [Qemu-devel] [PATCH v1 0/4] Interactive Boot Menu for DASD and SCSI
Guests on s390x
Type: series
Message-id: 1511808659-8846-1-git-send-email-wall...@linux.vnet.ibm.com
=== TEST SCRIPT BEGI
When the boot menu options are present and the guest's
disk has been configured by the zipl tool, then the user
will be presented with an interactive boot menu with
labeled entries. An example of what the menu might look
like:
zIPL v1.37.1-build-20170714 interactive boot menu.
0. default
Interactive boot menu for scsi. This follows the same procedure
as the interactive menu for eckd dasd. An example follows:
s390x Enumerated Boot Menu.
3 entries detected. Select from index 0 to 2.
Please choose:
Signed-off-by: Collin L. Walling
---
pc-bios/s390-ccw/bootmap.c | 9
ECKD DASDs have different IPL structures for CDL and LDL
formats. The current Ipl1 and Ipl2 structs follow the CDL
format, so we prepend "EckdCdl" to them. A new struct,
EckdLdlIpl1 is introduced and contains boot info for LDL.
Also introduce structs for IPL stages 1 and 1b and for
disk geometry.
Set boot menu options for an s390 guest and store them in
the iplb. These options are set via the QEMU command line
option:
-boot menu=on|off[,splash-time=X]
or via the libvirt domain xml:
Where X represents some positive integer representing
milliseconds.
Signed-off-by: C
These patches implement a boot menu for ECKD DASD and SCSI guests on s390x.
The menu will only appear if the disk has been configured for IPL with the
zIPL tool and with the following QEMU command line options:
-boot menu=on[,splash-time=X] and/or -machine loadparm='prompt'
or via the follo
> On Nov 23, 2017, at 9:29 AM, Kevin Wolf wrote:
>
> Am 23.11.2017 um 18:05 hat Deepa Srinivasan geschrieben:
>> blk_aio_prwv() now takes a void pointer and the coroutine functions
>> have been modified to cast it into QEMUIOVector if needed. It does not
>> use an union in BlkRwCo since this lea
+-- On Mon, 27 Nov 2017, Cornelia Huck wrote --+
|The check for align is not really needed, as virtio-1 disallows setting align
|anyway.
disallows...?
| Checking for !desc is wrong (why shouldn't a driver be able to unset a
| descriptor table?)
+-- On Mon, 27 Nov 2017, Stefan Hajnoczi wrote --
Signed-off-by: Mike Frysinger
---
scripts/git-submodule.sh | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/scripts/git-submodule.sh b/scripts/git-submodule.sh
index 030617b4ac0c..bc7224a27fe3 100755
--- a/scripts/git-submodule.sh
+++ b/scripts/git-submodule.sh
@@ -24,7 +24,7 @
On 11/27/2017 05:56 PM, Cornelia Huck wrote:
> On Mon, 27 Nov 2017 16:09:09 +0100
> Boris Fiuczynski wrote:
>
>> On 11/27/2017 03:13 PM, Halil Pasic wrote:
>>>
>>>
>>> On 11/27/2017 02:19 PM, Cornelia Huck wrote:
On Mon, 27 Nov 2017 14:11:57 +0100
Halil Pasic wrote:
> On
"Tan, Jianfeng" writes:
> On 11/27/2017 10:27 PM, Yuanhan Liu wrote:
>> On Fri, Nov 24, 2017 at 05:59:09PM +0800, Chen Hailin wrote:
>>> Hi Aaron Conole && Jianfeng,
>>>
>>> The stp could not work in ovs-dpdk vhostuser.
>>> Because the attached vhost device doesn't have MAC address.
>>>
>>> Now w
On Mon, 27 Nov 2017 16:09:09 +0100
Boris Fiuczynski wrote:
> On 11/27/2017 03:13 PM, Halil Pasic wrote:
> >
> >
> > On 11/27/2017 02:19 PM, Cornelia Huck wrote:
> >> On Mon, 27 Nov 2017 14:11:57 +0100
> >> Halil Pasic wrote:
> >>
> >>> On 11/27/2017 01:56 PM, Cornelia Huck wrote:
>
On 11/27/2017 12:50 PM, Peter Maydell wrote:
> On 27 November 2017 at 11:47, Russell King - ARM Linux
> wrote:
>> On Mon, Nov 27, 2017 at 11:16:06AM +0100, Cédric Le Goater wrote:
>>> Additional QEMU logging gives us :
>>>
>>> Ignoring attempt to switch CPSR_A flag from non-secure world with SCR
On Mon, Nov 27, 2017 at 2:05 PM, Roman Kagan wrote:
> UUIDs (GUIDs) are widely used in VMBus-related stuff, so a dedicated
> property type becomes helpful.
>
> The property accepts a string-formatted UUID or a special keyword "auto"
> meaning a randomly generated UUID; the latter is also the defau
On Mon, Nov 27, 2017 at 2:05 PM, Roman Kagan wrote:
> Switch vmgenid device to use the UUID property type introduced in the
> previous patch for its 'guid' property.
>
> One semantic change it introduces is that post-realize modification of
> 'guid' via HMP or QMP will now be rejected with an erro
On 27/11/2017 17:02, Cornelia Huck wrote:
On Mon, 27 Nov 2017 16:53:04 +0100
Pierre Morel wrote:
On 27/11/2017 16:30, Cornelia Huck wrote:
On Mon, 27 Nov 2017 16:24:08 +0100
Pierre Morel wrote:
On 27/11/2017 15:34, Cornelia Huck wrote:
On Mon, 27 Nov 2017 12:02:55 +0100
Cornelia Huck
It looks like you dropped Marc-André and my Reviewed-by lines. Please put them
back.
> On Nov 27, 2017, at 5:05 AM, Roman Kagan wrote:
>
> Switch vmgenid device to use the UUID property type introduced in the
> previous patch for its 'guid' property.
>
> One semantic change it introduces is t
On 11/28/2017 12:14 AM, Aaron Conole wrote:
Yuanhan Liu writes:
On Fri, Nov 24, 2017 at 05:59:09PM +0800, Chen Hailin wrote:
Hi Aaron Conole && Jianfeng,
The stp could not work in ovs-dpdk vhostuser.
Because the attached vhost device doesn't have MAC address.
Now we have two ways to solve
On 27/11/2017 14:10, John Paul Adrian Glaubitz wrote:
> On 11/27/2017 05:07 PM, Adhemerval Zanella wrote:> However I am not very
> compelled to change internal posix_spawn
>> on GLIBC on Linux mainly because it uses a slight less resources
>> than the generic POSIX one (check e83be730910c) and i
Yuanhan Liu writes:
> On Fri, Nov 24, 2017 at 05:59:09PM +0800, Chen Hailin wrote:
>> Hi Aaron Conole && Jianfeng,
>>
>> The stp could not work in ovs-dpdk vhostuser.
>> Because the attached vhost device doesn't have MAC address.
>>
>> Now we have two ways to solve this problem.
>> 1. The vhost
* according to Eduardo Habkost's commit
fd3b02c8896d597dd8b9e053dec579cf0386aee1
* since all PCIEs now implement INTERFACE_PCIE_DEVICE we
don't need this field anymore
Signed-off-by: Yoni Bettan
---
hw/block/nvme.c| 1 -
hw/net/e1000e.c
On 11/27/2017 05:07 PM, Adhemerval Zanella wrote:> However I am not very
compelled to change internal posix_spawn
on GLIBC on Linux mainly because it uses a slight less resources
than the generic POSIX one (check e83be730910c) and it works
on Linux kernel as expected.
But it breaks QEMU and Mi
Just as a note, I've been watching these series with great interest.
Once the changes settle down / are mergeable we will be looking to
implement vector <--> vector support between a couple of other
architectures.
Thanks for working on this!
On 11/21/2017 03:25 PM, Richard Henderson wrote:
> Quit
On 27/11/2017 13:24, Peter Maydell wrote:
> On 27 November 2017 at 12:57, Adhemerval Zanella
> wrote:
>> We found out this potential bogus assert on 2.27 development [1] which
>> resulted in two fixes [2][3].
>>
>> It should not be an issue for generic posix_spawn usage where there is
>> no expe
On Mon, 27 Nov 2017 16:53:04 +0100
Pierre Morel wrote:
> On 27/11/2017 16:30, Cornelia Huck wrote:
> > On Mon, 27 Nov 2017 16:24:08 +0100
> > Pierre Morel wrote:
> >
> >> On 27/11/2017 15:34, Cornelia Huck wrote:
> >>> On Mon, 27 Nov 2017 12:02:55 +0100
> >>> Cornelia Huck wrote:
> >>>
DIV_ROUND_UP(st.st_size, BDRV_SECTOR_SIZE) was overflowing ret (int) if
st.st_size is greater than 1TB.
Cc: qemu-sta...@nongnu.org
Signed-off-by: Peter Lieven
---
block/nfs.c | 7 +++
1 file changed, 3 insertions(+), 4 deletions(-)
diff --git a/block/nfs.c b/block/nfs.c
index 337fcd9..effc8
On 27/11/2017 16:30, Cornelia Huck wrote:
On Mon, 27 Nov 2017 16:24:08 +0100
Pierre Morel wrote:
On 27/11/2017 15:34, Cornelia Huck wrote:
On Mon, 27 Nov 2017 12:02:55 +0100
Cornelia Huck wrote:
On Mon, 27 Nov 2017 07:59:36 +0100
Thomas Huth wrote:
On 25.11.2017 14:49, Pierre Morel
On 11/27/2017 10:27 PM, Yuanhan Liu wrote:
On Fri, Nov 24, 2017 at 05:59:09PM +0800, Chen Hailin wrote:
Hi Aaron Conole && Jianfeng,
The stp could not work in ovs-dpdk vhostuser.
Because the attached vhost device doesn't have MAC address.
Now we have two ways to solve this problem.
1. The vh
On Mon, 27 Nov 2017 16:24:08 +0100
Pierre Morel wrote:
> On 27/11/2017 15:34, Cornelia Huck wrote:
> > On Mon, 27 Nov 2017 12:02:55 +0100
> > Cornelia Huck wrote:
> >
> >> On Mon, 27 Nov 2017 07:59:36 +0100
> >> Thomas Huth wrote:
> >>
> >>> On 25.11.2017 14:49, Pierre Morel wrote:
> >>>
On 27/11/2017 15:34, Cornelia Huck wrote:
On Mon, 27 Nov 2017 12:02:55 +0100
Cornelia Huck wrote:
On Mon, 27 Nov 2017 07:59:36 +0100
Thomas Huth wrote:
On 25.11.2017 14:49, Pierre Morel wrote:
On 24/11/2017 07:19, Yi Min Zhao wrote:
在 2017/11/23 下午8:18, Thomas Huth 写道:
On 23.11.2017 13
On 27 November 2017 at 12:57, Adhemerval Zanella
wrote:
> We found out this potential bogus assert on 2.27 development [1] which
> resulted in two fixes [2][3].
>
> It should not be an issue for generic posix_spawn usage where there is
> no expectation system/user/program kills random pids (since
Hi,
This series failed build test on ppc host. Please find the details below.
Subject: [Qemu-devel] [PATCH] thread: move detach_thread from creating thread
to created thread
Type: series
Message-id: 20171127145936.15676-1-linzhech...@huawei.com
=== TEST SCRIPT BEGIN ===
#!/bin/bash
# Testing sc
On 27/11/2017 16:08, Daniel P. Berrange wrote:
> We should just do
>
> if (mode == QEMU_THREAD_DETACHED) {
> pthread_attr_setdetachstate(&attr, PTHREAD_CREATE_DETACHED);
> }
>
This is true, but Zhecheng's patch (when fixed---see patchew's report)
would also fix a similar race on
On 27/11/2017 16:06, Peter Maydell wrote:
> On 27 November 2017 at 15:53, Paolo Bonzini wrote:
>> On 27/11/2017 15:47, Peter Maydell wrote:
>>> I have a patch from rth based on an idea he and I came up with:
>>> we add a field to the PageDesc struct to store the thread id of
>>> the thread that la
On 11/27/2017 03:13 PM, Halil Pasic wrote:
On 11/27/2017 02:19 PM, Cornelia Huck wrote:
On Mon, 27 Nov 2017 14:11:57 +0100
Halil Pasic wrote:
On 11/27/2017 01:56 PM, Cornelia Huck wrote:
On Fri, 24 Nov 2017 17:39:04 +0100
Halil Pasic wrote:
On 11/24/2017 05:15 PM, Cornelia Huck wrote
On Mon, Nov 27, 2017 at 10:59:36PM +0800, linzhecheng wrote:
> If we create a thread with QEMU_THREAD_DETACHED mode, QEMU may get a segfault
> in a low probability.
>
> The backtrace is:
> #0 0x7f46c60291d7 in __GI_raise (sig=sig@entry=6) at
> ../nptl/sysdeps/unix/sysv/linux/raise.c:56
> #1
On 27 November 2017 at 15:53, Paolo Bonzini wrote:
> On 27/11/2017 15:47, Peter Maydell wrote:
>> I have a patch from rth based on an idea he and I came up with:
>> we add a field to the PageDesc struct to store the thread id of
>> the thread that last touches the flags. If you come into the
>> se
Hi,
This series failed build test on s390x host. Please find the details below.
Type: series
Subject: [Qemu-devel] [PATCH] thread: move detach_thread from creating thread
to created thread
Message-id: 20171127145936.15676-1-linzhech...@huawei.com
=== TEST SCRIPT BEGIN ===
#!/bin/bash
# Testing
On 2017-11-23 08:24, Fam Zheng wrote:
> On Thu, 11/23 03:08, Max Reitz wrote:
>> (I hate to write Python tests because the boilerplate seems so large and
>> the debugging is so hard. But there is test 194 which shows that it is
>> possible to write simple bash-like tests as well--and that is how
If we create a thread with QEMU_THREAD_DETACHED mode, QEMU may get a segfault
in a low probability.
The backtrace is:
#0 0x7f46c60291d7 in __GI_raise (sig=sig@entry=6) at
../nptl/sysdeps/unix/sysv/linux/raise.c:56
#1 0x7f46c602a8c8 in __GI_abort () at abort.c:90
#2 0x008543c9
Hello!
I tagged libtpms with TPM 1.2 and TPM 2 support with tag/v0.6.0-dev1 and
swtpm with TPM 1.2 and TPM 2 support with tag/v0.1.0-dev2. The git repos
of the respective projects are here:
libtpms: https://github.com/stefanberger/libtpms
swtpm: https://github.com/stefanberger/swtpm
Note:
On 26/11/2017 18:35, John Paul Adrian Glaubitz wrote:
> On 11/26/2017 09:28 PM, John Paul Adrian Glaubitz wrote:
>> I'm not sure yet what the actual problem is but I thought it should be
>> necessary
>> to point you at the problem.
>
> Ok, there is already a QEMU bug report for this [1].
>
> Adr
On 27/11/2017 15:47, Peter Maydell wrote:
> On 27 November 2017 at 15:38, Paolo Bonzini wrote:
>> On 24/11/2017 18:18, Peter Maydell wrote:
>>> * threads A & B both try to do a write to a page with code in it at
>>>the same time (ie which we've made non-writeable, so SEGV)
>>> * they race in
1 - 100 of 171 matches
Mail list logo
