On Sun, Mar 11, 2018 at 5:33 AM, Eric Blake wrote:
> On 03/10/2018 03:22 PM, Zhang Chen wrote:
>
>> Libvirt or other high level sofware can use this command query colo
>> status.
>>
>
> s/sofware/software/
>
> You can test this command like that:
>> {'execute':'query-colo-status'}
>>
>> Signed-
From: zhanghailiang
Notify all net filters about the checkpoint and failover event.
Signed-off-by: zhanghailiang
---
migration/colo.c | 12
1 file changed, 12 insertions(+)
diff --git a/migration/colo.c b/migration/colo.c
index f3d588e..1a59baa 100644
--- a/migration/colo.c
+++ b
From: zhanghailiang
COLO thread may sleep at qemu_sem_wait(&s->colo_checkpoint_sem),
while failover works begin, It's better to wakeup it to quick
the process.
Signed-off-by: zhanghailiang
---
migration/colo.c | 8
1 file changed, 8 insertions(+)
diff --git a/migration/colo.c b/migra
** Description changed:
I use Arch Linux x86_64
- both qemu 2.11.1 and Zhang
Chen's(https://github.com/zhangckid/qemu/commits/colo-with-virtio-net-internal-jul10)
+ Zhang
Chen's(https://github.com/zhangckid/qemu/commits/colo-with-virtio-net-internal-jul10)
Following document 'COLO-FT.txt',
** Summary changed:
- colo: secondary vm crash when execute x-colo-lost-heartbeat
+ colo: vm crash with segmentation fault
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1754542
Title:
colo: vm c
Hi Mark,
On 03/10/2018 10:40 AM, Mark Cave-Ayland wrote:
> On 10/03/18 03:02, Michael Clark wrote:
>
>> On Sat, Mar 10, 2018 at 1:39 AM, Philippe Mathieu-Daudé
>> wrote:
>>
[...]
> Another general note: for each of the main QEMU platforms supported
> there is a home page on the official wiki, so
On 03/10/2018 10:25 PM, Philippe Mathieu-Daudé wrote:
> On 03/09/2018 10:01 PM, Michael Clark wrote:
>> Logic bug caused the string size calculation for the RISC-V
>> format ISA string to be small. This fix allows slack for rv128.
>>
>> Cc: Palmer Dabbelt
>> Cc: Peter Maydell
>> Cc: Eric Blake
>
On 11 March 2018 at 06:58, Eva Chen wrote:
> Hello,
>
> I am working on compiling QEMU 2.10.2 to a static library.
>
> Everything works fine in compiling QEMU to an execution
> file(qemu-system-aarch64), but after I link all .o and .a file to create a
> QEMU library and write a c file to call qemu
Hi Michael, Paolo.
Now than all other PCI QOM'ification patches got applied, can you take
this patch for 2.12?
Thanks,
Phil.
On 12/17/2017 09:49 PM, Philippe Mathieu-Daudé wrote:
> All PCI devices are now QOM'ified.
>
> Signed-off-by: Philippe Mathieu-Daudé
> ---
> include/hw/pci/pci.h | 1
From: Aishwarya Kadlag
Remove support for DEPTH != 32 values from hw/display/*_template.h
files and other files that include them. Only DEPTH == 32 case is
supported.
Signed-off-by: Aishwarya Kadlag
---
hw/display/sw501_1.c | 36
hw/display/
Hi
On Fri, Mar 9, 2018 at 6:03 PM, Wei Huang wrote:
> For guest kernel that supports KASLR, the load address can change every
> time when guest VM runs. To find the physical base address correctly,
> current QEMU dump searches VMCOREINFO for the string "NUMBER(phys_base)=".
> However this string
Signed-off-by: Nia Alarie
---
hw/9pfs/9p.c | 12 ++--
1 file changed, 10 insertions(+), 2 deletions(-)
diff --git a/hw/9pfs/9p.c b/hw/9pfs/9p.c
index 48fa48e720..64f3bb976c 100644
--- a/hw/9pfs/9p.c
+++ b/hw/9pfs/9p.c
@@ -15,6 +15,7 @@
#include
#include "hw/virtio/virtio.h"
#include
On Thu, 8 Mar 2018, Igor Druzhinin wrote:
> This should help to avoid problems with accessing the device after
> migration/resume without PV drivers. Older systems will acquire
> the new record when migrated which should not change their state for
> worse.
Could you please explain what problems th
On Fri, 9 Mar 2018, Eduardo Habkost wrote:
> On Fri, Mar 09, 2018 at 12:07:21PM +, Ian Jackson wrote:
> > Ian Jackson writes ("Re: [PATCH 03/11] xen: defer call to xen_restrict
> > until just before os_setup_post"):
> > > Eduardo Habkost writes ("Re: [PATCH 03/11] xen: defer call to
> > > xen
On Sun, Mar 11, 2018 at 04:46:52PM +0100, Philippe Mathieu-Daudé wrote:
> Hi Michael, Paolo.
>
> Now than all other PCI QOM'ification patches got applied, can you take
> this patch for 2.12?
>
> Thanks,
>
> Phil.
>
> On 12/17/2017 09:49 PM, Philippe Mathieu-Daudé wrote:
> > All PCI devices are
On Mon, Mar 12, 2018 at 02:03:17AM +0200, Michael S. Tsirkin wrote:
> On Sun, Mar 11, 2018 at 04:46:52PM +0100, Philippe Mathieu-Daudé wrote:
> > Hi Michael, Paolo.
> >
> > Now than all other PCI QOM'ification patches got applied, can you take
> > this patch for 2.12?
> >
> > Thanks,
> >
> > Phi
** Description changed:
I use Arch Linux x86_64
- Zhang
Chen's(https://github.com/zhangckid/qemu/commits/colo-with-virtio-net-internal-jul10)
+ Zhang Chen's(https://github.com/zhangckid/qemu/tree/qemu-colo-18mar10)
Following document 'COLO-FT.txt',
I test colo feature on my hosts
I run
** Description changed:
I use Arch Linux x86_64
Zhang Chen's(https://github.com/zhangckid/qemu/tree/qemu-colo-18mar10)
Following document 'COLO-FT.txt',
I test colo feature on my hosts
I run this command
Primary:
- sudo qemu-system-x86_64 -boot c -enable-kvm -m 2048 -smp 2 -qmp s
The issue has been fixed: http://lists.nongnu.org/archive/html/qemu-
devel/2018-03/msg02174.html
** Changed in: qemu
Status: New => Fix Committed
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs
I tried the above patches on a TR 1900X and they do not help to enable
SMT. I still receive the warning.
Also, with the patches applied, the CPU now identifies as EPYC in the
guest.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
htt
On Fri, Mar 09, 2018 at 11:13:23AM -0600, Eric Blake wrote:
> On 03/09/2018 02:59 AM, Peter Xu wrote:
> > Update both the developer and spec for the new QMP OOB (Out-Of-Band)
> > command.
> >
> > Signed-off-by: Peter Xu
> > ---
> > docs/devel/qapi-code-gen.txt | 65
> >
On Sat, Mar 10, 2018 at 08:27:22PM -0600, Eric Blake wrote:
[...]
> I'm a bit disappointed that tests/qapi-schema/qapi-schema-test.json doesn't
> have any "allow-oob":true commands at any point in the series. I consider
> that to be a bug, so it can be fixed by followup patch even after soft
> fr
On Sat, Mar 10, 2018 at 08:45:46PM -0600, Eric Blake wrote:
> On 03/09/2018 03:00 AM, Peter Xu wrote:
> > OOB introduced DROP event for flow control. This should not affect old
> > QMP clients. Add a command batching check to make sure of it.
> >
> > Reviewed-by: Stefan Hajnoczi
> > Signed-off-
On Sat, Mar 10, 2018 at 08:49:42PM -0600, Eric Blake wrote:
> On 03/09/2018 03:00 AM, Peter Xu wrote:
> > Test the new OOB capability. Here we used the new "x-oob-test" command.
> > Firstly, we send a lock=true and oob=false command to hang the main
>
> s/Firstly/First/
>
> > thread. Then send
On Sat, Mar 10, 2018 at 08:59:38PM -0600, Eric Blake wrote:
> On 03/09/2018 02:59 AM, Peter Xu wrote:
> > Based-on: <20180306053320.15401-1-pet...@redhat.com>
> >
> > The series is based on the following series:
> >
> >[PATCH v2 0/9] chardev: qio related non-default context support
> >(ac
[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/1173490
Title:
virtio net
[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/1129957
Title:
Performance
[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/1122492
Title:
qemu and gr
[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/1055090
Title:
esp error:
[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/1086745
Title:
serial port
[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/1175089
Title:
Crash why d
[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/1090726
Title:
qemu does n
On Fri, Mar 09, 2018 at 10:59:03AM -0600, Eric Blake wrote:
> On 03/09/2018 10:54 AM, Eric Blake wrote:
> > On 03/09/2018 03:15 AM, Peter Xu wrote:
> > > Based-on: <20180309090006.10018-1-pet...@redhat.com>
> > >
> > > This series is based on the series:
> > >
> > > [PATCH v8 00/23] QMP: out-o
It works in my side after specify the full path to swtpm tpmemu.sock in qemu
command options. Thanks!
Steven Shi
Intel\SSG\STO\UEFI Firmware
Tel: +86 021-61166522
iNet: 821-6522
> -Original Message-
> From: Stefan Berger [mailto:stef...@linux.vnet.ibm.com]
> Sent: Friday, March 9, 2018
On 28.02.2018 10:32, Paolo Bonzini wrote:
> Allow distributions to disable the Intel and/or AMD IOMMU devices.
>
> Signed-off-by: Paolo Bonzini
> ---
> default-configs/i386-softmmu.mak | 2 ++
> default-configs/x86_64-softmmu.mak | 2 ++
> hw/i386/Makefile.objs | 5 +++--
> 3 file
On 11.03.2018 17:40, Aishwarya Kadlag wrote:
> From: Aishwarya Kadlag
>
> Remove support for DEPTH != 32 values from hw/display/*_template.h
> files and other files that include them. Only DEPTH == 32 case is
> supported.
>
> Signed-off-by: Aishwarya Kadlag
> ---
> hw/display/sw501_1.c
Hi all,
it's great that we have https://wiki.qemu.org/BiteSizedTasks - but
apparently some tasks are apparently described a little bit too
scarcely. Many newcomers seem to have problems understanding the tasks
that are mentioned here. To improve the experience of people willing to
contribute to Q
Looks like the mailing list <-> launchpad bridge again ignored mails to the
corresponding mailing list thread. It's not a real bug, see here for details:
https://lists.gnu.org/archive/html/qemu-devel/2018-03/msg01142.html
I'll try to remember to clean this up the next time we update the s390-ccw b
38 matches
Mail list logo
