Hi Stefan,
Thanks for your reply.
On Thu, Aug 15, 2019 at 7:07 AM Stefan Hajnoczi wrote:
>
> On Wed, Aug 14, 2019 at 10:54:34AM -0700, William Tu wrote:
> > Hi,
> >
> > I'm using libvhost-user.a to write a vhost backend, in order to receive and
> > send packets from/to VMs from OVS. I started by
On Wed, Aug 14, 2019 at 10:54:34AM -0700, William Tu wrote:
> Hi,
>
> I'm using libvhost-user.a to write a vhost backend, in order to receive and
> send packets from/to VMs from OVS. I started by reading the
> vhost-user-bridge.c.
> I can now pass the initialization stage, seeing .queue_set_start
Hi,
I'm using libvhost-user.a to write a vhost backend, in order to receive and
send packets from/to VMs from OVS. I started by reading the vhost-user-bridge.c.
I can now pass the initialization stage, seeing .queue_set_started get invoked.
However, I am stuck at receiving the packet from VM.
So
>
>
>
> >
> > I already spent 2h on this today, I have to continue other tasks
> > meanwhile, I might continue later.
>
> I spent 1 more hour installing the CodeScape MIPS SDK,...
Philippe, thank you so much for your 3 hours!
Regards,
Aleksandar
Hi Aleksandar,
On 7/18/19 8:20 AM, Philippe Mathieu-Daudé wrote:
> On 7/16/19 8:20 PM, Philippe Mathieu-Daudé wrote:
>> Hi Aleksandar,
>>
>> On 7/16/19 7:09 PM, Aleksandar Markovic wrote:
>>> On Tue, Jul 16, 2019 at 1:54 PM Thomas Huth wrote:
On 16/07/2019 13.17, Aleksandar Markovic wro
sainath grandhi writes:
> Hello
> I am working with qemu tracing support and combined with tcg.
> I read that if tcg property is used for trace-event, it generates a
> trace-event once during translation and another trace-event after the
> execution.
>
> I made the following change in target/i3
Hello
I am working with qemu tracing support and combined with tcg.
I read that if tcg property is used for trace-event, it generates a
trace-event once during translation and another trace-event after the
execution.
I made the following change in target/i386/translate.c
-static inline void gen_o
On 7/16/19 8:20 PM, Philippe Mathieu-Daudé wrote:
> Hi Aleksandar,
>
> On 7/16/19 7:09 PM, Aleksandar Markovic wrote:
>> On Tue, Jul 16, 2019 at 1:54 PM Thomas Huth wrote:
>>>
>>> On 16/07/2019 13.17, Aleksandar Markovic wrote:
Hello, Gerd, Daniel, and others involved.
I have multi
On 7/17/19 2:20 PM, Aleksandar Markovic wrote:
> But, does "configure" list somewhere unmet soft dependencies? (the
> question is general, not looking at SDL only) Is there any other way for
> an end user to have info on unmet dependencies (whether soft or hard),
> other than see QEMU is not build
On Wed, Jul 17, 2019 at 8:57 PM Eric Blake wrote:
>
> On 7/17/19 1:34 PM, Aleksandar Markovic wrote:
>
> >
> > Daniel, that is fine, I don't question that, I basically wanted to start a
> > talk
> > between us to clarify some things. Related to our situation in the field,
> > I have a sub-questio
On 7/17/19 1:34 PM, Aleksandar Markovic wrote:
>
> Daniel, that is fine, I don't question that, I basically wanted to start a
> talk
> between us to clarify some things. Related to our situation in the field,
> I have a sub-question to you:
>
> Let's say there is a build system with SDL 1.2, an
On Tue, Jul 16, 2019 at 7:44 PM Daniel P. Berrangé wrote:
>
> On Tue, Jul 16, 2019 at 07:09:37PM +0200, Aleksandar Markovic wrote:
> > On Tue, Jul 16, 2019 at 1:54 PM Thomas Huth wrote:
> > >
> > > On 16/07/2019 13.17, Aleksandar Markovic wrote:
> > > > Hello, Gerd, Daniel, and others involved.
>
On Tue, 16 Jul 2019 at 18:48, Aleksandar Markovic
wrote:
> "For distributions with frequent, short-lifetime releases, the project will
> aim to support all versions that are not end of life by their respective
> vendors. For the purposes of identifying supported software versions,
> the project wi
Hi Aleksandar,
On 7/16/19 7:09 PM, Aleksandar Markovic wrote:
> On Tue, Jul 16, 2019 at 1:54 PM Thomas Huth wrote:
>>
>> On 16/07/2019 13.17, Aleksandar Markovic wrote:
>>> Hello, Gerd, Daniel, and others involved.
>>>
>>> I have multiple reports from end users that say that transition from
>>> S
On Tue, Jul 16, 2019 at 08:06:24PM +0200, Aleksandar Markovic wrote:
> > > It appears that Ubuntu 16.04 came originally with SDL 1.2, and
> > > SDL 2.0 was made available later on.
> >
> > That is not the case. Ubuntu has shipped both SDL 1.2 and 2.0
> > concurrently as options, even in the previou
> > It appears that Ubuntu 16.04 came originally with SDL 1.2, and
> > SDL 2.0 was made available later on.
>
> That is not the case. Ubuntu has shipped both SDL 1.2 and 2.0
> concurrently as options, even in the previous 14.04 LTS, and
> probably before that too.
>
Thank you for finding this out.
On Tue, Jul 16, 2019 at 1:41 PM Peter Maydell wrote:
>
> On Tue, 16 Jul 2019 at 12:17, Aleksandar Markovic
> wrote:
> >
> > Hello, Gerd, Daniel, and others involved.
> >
> > I have multiple reports from end users that say that transition from
> > SDL 1.2 to SDL 2.0 was difficult, or even impossib
On Tue, Jul 16, 2019 at 07:09:37PM +0200, Aleksandar Markovic wrote:
> On Tue, Jul 16, 2019 at 1:54 PM Thomas Huth wrote:
> >
> > On 16/07/2019 13.17, Aleksandar Markovic wrote:
> > > Hello, Gerd, Daniel, and others involved.
> > >
> > > I have multiple reports from end users that say that transit
On Tue, Jul 16, 2019 at 1:54 PM Thomas Huth wrote:
>
> On 16/07/2019 13.17, Aleksandar Markovic wrote:
> > Hello, Gerd, Daniel, and others involved.
> >
> > I have multiple reports from end users that say that transition from
> > SDL 1.2 to SDL 2.0 was difficult, or even impossible for their hosts
On 16/07/2019 13.17, Aleksandar Markovic wrote:
> Hello, Gerd, Daniel, and others involved.
>
> I have multiple reports from end users that say that transition from
> SDL 1.2 to SDL 2.0 was difficult, or even impossible for their hosts.
> In that light, they don't appreciate removing SDL 1.2 suppo
On Tue, Jul 16, 2019 at 01:17:01PM +0200, Aleksandar Markovic wrote:
> Hello, Gerd, Daniel, and others involved.
>
> I have multiple reports from end users that say that transition from
> SDL 1.2 to SDL 2.0 was difficult, or even impossible for their hosts.
> In that light, they don't appreciate r
On Tue, 16 Jul 2019 at 12:17, Aleksandar Markovic
wrote:
>
> Hello, Gerd, Daniel, and others involved.
>
> I have multiple reports from end users that say that transition from
> SDL 1.2 to SDL 2.0 was difficult, or even impossible for their hosts.
> In that light, they don't appreciate removing SD
Hello, Gerd, Daniel, and others involved.
I have multiple reports from end users that say that transition from
SDL 1.2 to SDL 2.0 was difficult, or even impossible for their hosts.
In that light, they don't appreciate removing SDL 1.2 support from
QEMU. The most notable example is Ubutnu 16.04, wh
Am 01.07.2019 um 18:42 hat Yury Kotov geschrieben:
> Hi,
>
> I just want to clarify the purpose of bdrv_co_invalidate_cache callback.
> IIUC on of the purposes of this callback is to "activate" BDRV (opposite of
> the
> bdrv_inactivate callback) on migration end, right?
>
> E.g, if we have a cus
Hi,
I just want to clarify the purpose of bdrv_co_invalidate_cache callback.
IIUC on of the purposes of this callback is to "activate" BDRV (opposite of the
bdrv_inactivate callback) on migration end, right?
E.g, if we have a custom BDRV which is backed by some network block storage with
exclusiv
On 2019/6/10 下午11:55, Michael S. Tsirkin wrote:
On Tue, Jun 04, 2019 at 03:10:43PM +0800, Like Xu wrote:
Hi Michael，
At https://www.linux-kvm.org/page/NetworkingTodo, there is an entry for
network latency saying:
---
reduce networking latency:
allow handling short packets from softirq or V
On 2019/6/10 下午11:55, Michael S. Tsirkin wrote:
On Tue, Jun 04, 2019 at 03:10:43PM +0800, Like Xu wrote:
Hi Michael，
At https://www.linux-kvm.org/page/NetworkingTodo, there is an entry for
network latency saying:
---
reduce networking latency:
allow handling short packets from softirq or V
On Tue, Jun 04, 2019 at 03:10:43PM +0800, Like Xu wrote:
> Hi Michael，
>
> At https://www.linux-kvm.org/page/NetworkingTodo, there is an entry for
> network latency saying:
>
> ---
> reduce networking latency:
> allow handling short packets from softirq or VCPU context
> Plan:
>We are going
Hi Michael，
At https://www.linux-kvm.org/page/NetworkingTodo, there is an entry for
network latency saying:
---
reduce networking latency:
allow handling short packets from softirq or VCPU context
Plan:
We are going through the scheduler 3 times
(could be up to 5 if softirqd is involve
We find only one VM aborted among at least 20 VMs with the same configuration.
And this problem does not reproduce yet... (Be aware of reproduce is importance
to figure out the problem, we already tried to add more VMs to reproduce, but
no results yet.)
The qemu cmdline is as follows:
/usr/bin/q
On Sat, 25 May 2019 03:35:20 +
"liujunjie (A)" wrote:
> Hi, I have met a problem:
>
> The QEMU version is 2.8.1, the virtual machine is configured with 1G huge
> pages, two NUMA nodes and four pass-through NVME SSDs.
>
> After we started the VM, in addition to some QMP queries nothing more
Hi, I have met a problem:
The QEMU version is 2.8.1, the virtual machine is configured with 1G huge
pages, two NUMA nodes and four pass-through NVME SSDs.
After we started the VM, in addition to some QMP queries nothing more has been
done, the QEMU aborted after some months later.
After that, t
Alex Williamson 于2019年5月15日周三 下午10:54写道：
> On Wed, 15 May 2019 17:27:52 +0300
> Maxim Levitsky wrote:
>
> > Hi!
> >
> > Let me add my 0.2 cents to this discussion by sharing my summary of INTx
> emulation in VFIO:
> >
> > COMMON:
> > * real interrupt is signaled in the kernel
> > * vfio-pci kern
On Wed, 15 May 2019 17:27:52 +0300
Maxim Levitsky wrote:
> Hi!
>
> Let me add my 0.2 cents to this discussion by sharing my summary of INTx
> emulation in VFIO:
>
> COMMON:
> * real interrupt is signaled in the kernel
> * vfio-pci kernel interrupt hanlder (vfio_intx_handler), masks the INTx fl
Hi!
Let me add my 0.2 cents to this discussion by sharing my summary of INTx
emulation in VFIO:
COMMON:
* real interrupt is signaled in the kernel
* vfio-pci kernel interrupt hanlder (vfio_intx_handler), masks the INTx flag
* vfio-pci kernel interrupt handler triggers an eventfd, if the interrup
On Wed, 15 May 2019 18:22:54 +0800
Li Qiang wrote:
> Auger Eric 于2019年5月15日周三 下午6:16写道：
>
> > Hi,
> >
> > On 5/15/19 12:01 PM, Li Qiang wrote:
> > > Hello Paolo, Alex and all,
> > >
> > > In vfio_intx_enable_kvm(qemu) I see we associate a resamplefd with the
> > > umask function(vfio_pci_intx
Auger Eric 于2019年5月15日周三 下午6:16写道：
> Hi,
>
> On 5/15/19 12:01 PM, Li Qiang wrote:
> > Hello Paolo, Alex and all,
> >
> > In vfio_intx_enable_kvm(qemu) I see we associate a resamplefd with the
> > umask function(vfio_pci_intx_unmask_handler in linux).
> >
> > irq_set = g_malloc0(argsz);
> >
Hi,
On 5/15/19 12:01 PM, Li Qiang wrote:
> Hello Paolo, Alex and all,
>
> In vfio_intx_enable_kvm(qemu) I see we associate a resamplefd with the
> umask function(vfio_pci_intx_unmask_handler in linux).
>
> irq_set = g_malloc0(argsz);
> irq_set->argsz = argsz;
> irq_set->flags = VFIO_
Hello Paolo, Alex and all,
In vfio_intx_enable_kvm(qemu) I see we associate a resamplefd with the
umask function(vfio_pci_intx_unmask_handler in linux).
irq_set = g_malloc0(argsz);
irq_set->argsz = argsz;
irq_set->flags = VFIO_IRQ_SET_DATA_EVENTFD | VFIO_IRQ_SET_ACTION_UNMASK;
irq
emu-devel@nongnu.org; Linuxarm
> >> ; linux-mm ;
> >> qemu-...@nongnu.org; Jonathan Cameron
> >> ; Robin Murphy ;
> >> linux-arm-ker...@lists.infradead.org
> >> Subject: Re: [Qemu-devel] [Question] Memory hotplug clarification for Qemu
> >> A
t;
>> Cc: peter.mayd...@linaro.org; xuwei (O) ; Anshuman
>> Khandual ; Catalin Marinas
>> ; ard.biesheu...@linaro.org;
>> will.dea...@arm.com; qemu-devel@nongnu.org; Linuxarm
>> ; linux-mm ;
>> qemu-...@nongnu.org; Jonathan Cameron
>> ; Robin Murphy ;
&g
; ard.biesheu...@linaro.org;
> will.dea...@arm.com; qemu-devel@nongnu.org; Linuxarm
> ; linux-mm ;
> qemu-...@nongnu.org; Jonathan Cameron
> ; Robin Murphy ;
> linux-arm-ker...@lists.infradead.org
> Subject: Re: [Qemu-devel] [Question] Memory hotplug clarification for Qemu
> AR
Hi Shameer,
On 5/10/19 10:34 AM, Shameerali Kolothum Thodi wrote:
>
>
>> -Original Message-
>> From: Laszlo Ersek [mailto:ler...@redhat.com]
>> Sent: 09 May 2019 22:48
>> To: Igor Mammedov
>> Cc: Robin Murphy ; Shameerali Kolothum Thodi
>> ; will.dea...@arm.com; Catalin
>> Marinas ; Ans
> -Original Message-
> From: Laszlo Ersek [mailto:ler...@redhat.com]
> Sent: 09 May 2019 22:48
> To: Igor Mammedov
> Cc: Robin Murphy ; Shameerali Kolothum Thodi
> ; will.dea...@arm.com; Catalin
> Marinas ; Anshuman Khandual
> ; linux-arm-ker...@lists.infradead.org;
> linux-mm ; qemu-dev
On 05/09/19 18:35, Igor Mammedov wrote:
> On Wed, 8 May 2019 22:26:12 +0200
> Laszlo Ersek wrote:
>
>> On 05/08/19 14:50, Robin Murphy wrote:
>>> Hi Shameer,
>>>
>>> On 08/05/2019 11:15, Shameerali Kolothum Thodi wrote:
Hi,
This series here[0] attempts to add support for PCDIMM in
On Wed, 8 May 2019 22:26:12 +0200
Laszlo Ersek wrote:
> On 05/08/19 14:50, Robin Murphy wrote:
> > Hi Shameer,
> >
> > On 08/05/2019 11:15, Shameerali Kolothum Thodi wrote:
> >> Hi,
> >>
> >> This series here[0] attempts to add support for PCDIMM in QEMU for
> >> ARM/Virt platform and has stumbl
On Thu, May 09, 2019 at 02:45:25PM +0100, Stefan Hajnoczi wrote:
> On Tue, May 07, 2019 at 11:29:03AM +0900, S KH wrote:
> > This is a question I have encountered while using QEMU.
> >
> > I want to compile the source directly rather than through apt or yum and
> > install QEMU and input the outpu
On Tue, May 07, 2019 at 11:29:03AM +0900, S KH wrote:
> This is a question I have encountered while using QEMU.
>
> I want to compile the source directly rather than through apt or yum and
> install QEMU and input the output statement to the source to check the
> output value.
>
> When I compiled
On 05/08/19 14:50, Robin Murphy wrote:
> Hi Shameer,
>
> On 08/05/2019 11:15, Shameerali Kolothum Thodi wrote:
>> Hi,
>>
>> This series here[0] attempts to add support for PCDIMM in QEMU for
>> ARM/Virt platform and has stumbled upon an issue as it is not clear(at
>> least
>> from Qemu/EDK2 point
On 05/08/19 12:15, Shameerali Kolothum Thodi wrote:
> Hi,
>
> This series here[0] attempts to add support for PCDIMM in QEMU for
> ARM/Virt platform and has stumbled upon an issue as it is not clear(at least
> from Qemu/EDK2 point of view) how in physical world the hotpluggable
> memory is handled
Hi Shameer,
On 08/05/2019 11:15, Shameerali Kolothum Thodi wrote:
Hi,
This series here[0] attempts to add support for PCDIMM in QEMU for
ARM/Virt platform and has stumbled upon an issue as it is not clear(at least
from Qemu/EDK2 point of view) how in physical world the hotpluggable
memory is ha
Hi,
This series here[0] attempts to add support for PCDIMM in QEMU for
ARM/Virt platform and has stumbled upon an issue as it is not clear(at least
from Qemu/EDK2 point of view) how in physical world the hotpluggable
memory is handled by kernel.
The proposed implementation in Qemu, builds the SRA
Re-adding qemu-devel - please don't take mailing list threads private.
On Wed, May 08, 2019 at 07:07:01PM +0900, S KH wrote:
> Hello.
>
> Thanks to help, I can see the results of the output in the log file. Thank
> you very much for your help. I am currently working with the QEMU source as
> well
On Wed, May 08, 2019 at 10:51:00AM +0900, S KH wrote:
> Hello.
>
> I'am student studying QEMU hypervisor and SPICE.
>
> In order to find out the calling order of functions in QEMU source, I input
> and compiled 'printf ("% s \ n", __ func__) "into source.
If using printf() output is buffered so
Hello.
I'am student studying QEMU hypervisor and SPICE.
In order to find out the calling order of functions in QEMU source, I input
and compiled 'printf ("% s \ n", __ func__) "into source.
And when I run the VM and open 'domain_name.log' in '/ var / log / libvirt
/ qemu', I see that no output f
This is a question I have encountered while using QEMU.
I want to compile the source directly rather than through apt or yum and
install QEMU and input the output statement to the source to check the
output value.
When I compiled QEMU using dpkg-buildpackage in Ubuntu, I verified that
when QEMU's
On Tue, Apr 23, 2019 at 11:12:40AM +0800, Jie Wang wrote:
> Does qemu-pr-helper have its own log files？
When QEMU launches it, i think it just inherits stdout/err from
QEMU itself, so errors appear mixed into QEMU's stdout output.
When libvirt launches it, there stdout is connected to /dev/null
Does qemu-pr-helper have its own log files？
Hi Eric and Michael,
Appreciate your sharing of this information. But sorry I'm still a little
confused due to my poor English...
On 2019/4/11 20:19, Auger Eric wrote:
Hi Heyi,
On 4/11/19 1:30 PM, Heyi Guo wrote:
Hi Eric,
Could you help to confirm?
Practically I have not tried anything el
Hi Heyi,
On 4/11/19 1:30 PM, Heyi Guo wrote:
> Hi Eric,
>
> Could you help to confirm?
Practically I have not tried anything else than hot-plugging the
downstream port downstream to the upstream port. This looks not
supported as documented.
Michael answered that up to him, the downstream port c
Hi Eric,
Could you help to confirm?
Thanks,
Heyi
On 2019/4/7 9:59, Heyi Guo wrote:
Hi Eric,
My real interesting is about the hotplug of PCIe switch, which means we don't
need to provide lots of PCIe root ports or PCIe down stream ports at the
beginning, but we can extend the capacity by h
Hi Eric,
My real interesting is about the hotplug of PCIe switch, which means we don't
need to provide lots of PCIe root ports or PCIe down stream ports at the
beginning, but we can extend the capacity by hot adding PCIe switches which can
provide more hot-pluggable slots for endpoint devices.
Hello, folks.
There is some optimization activity in MIPS target, and we have some simple
micro-benchmarks for measuring speed of emulation of a single target
instruction, but I am not particulary happy with them. They are just a
single instruction assembly within a “for“ loop. I tried some other
Hi Heyi,
On 4/3/19 8:50 PM, Michael S. Tsirkin wrote:
> On Wed, Apr 03, 2019 at 03:32:09PM +0800, Heyi Guo wrote:
>> Hi folks,
>>
>> In physical world, a PCIe switch including one upstream port and several
>> downstream ports is a single physical device, however we treat each port as
>> a device
On Wed, Apr 03, 2019 at 03:32:09PM +0800, Heyi Guo wrote:
> Hi folks,
>
> In physical world, a PCIe switch including one upstream port and several
> downstream ports is a single physical device, however we treat each port as a
> device in qemu world. In qemu docs/pcie.txt, we have below statemen
Hi folks,
In physical world, a PCIe switch including one upstream port and several
downstream ports is a single physical device, however we treat each port as a
device in qemu world. In qemu docs/pcie.txt, we have below statements:
Line 230: Be aware that PCI Express Downstream Ports can't be
Appears that this was already done in 2018 October:
https://lists.gnu.org/archive/html/qemu-devel/2018-10/msg05734.html
Disregard this thread, I should have searched better.
On Wed, Mar 27, 2019 at 4:02 PM Hikmat Jafarli wrote:
> So I'm trying to add IPv6 support to hostfwd, as requested in
> ht
So I'm trying to add IPv6 support to hostfwd, as requested in
https://bugs.launchpad.net/qemu/+bug/1724590
I'm not entirely sure what would be the right parameter format in case of
IPv6 support.
Current IPv4-only format is
"hostfwd=[tcp|udp]:[hostaddr]:hostport-[guestaddr]:guestport", example
usa
Thanks a lot!
пт, 22 мар. 2019 г. в 16:15, Greg Kurz :
> On Fri, 22 Mar 2019 11:57:04 +0200
> "П, Алексей" wrote:
>
> > Hi there. Cannot find any info and examples about "proxy" and "handle"
> > types of fsdriver of virtfs. Can anyone advise me description of?
> > Witrh regards/
>
> Hi,
>
> The
On Fri, 22 Mar 2019 11:57:04 +0200
"П, Алексей" wrote:
> Hi there. Cannot find any info and examples about "proxy" and "handle"
> types of fsdriver of virtfs. Can anyone advise me description of?
> Witrh regards/
Hi,
The "handle" backend was deprecated in QEMU 2.12, for various reasons...
requi
Hi there. Cannot find any info and examples about "proxy" and "handle"
types of fsdriver of virtfs. Can anyone advise me description of?
Witrh regards/
On Tue, Mar 19, 2019 at 09:51:17AM +, Lilijun (Jerry, Cloud Networking)
wrote:
> After more detail test, I found two results:
> 1) This route entry's lost can be reproduced on both virtio-net and
> pass-through physical devices.
> 2) The link down event is handled by a service named NetworkM
mail.com]
> Sent: Wednesday, March 13, 2019 10:55 PM
> To: Lilijun (Jerry, Cloud Networking)
> Cc: qemu-devel@nongnu.org; wangxin (U)
> ; wangyunjian
>
> Subject: Re: [Qemu-devel] Question about VM inner route entry's lost when
> vhost-user reconnect
>
> On Tue, Mar 12,
; Cc: qemu-devel@nongnu.org; wangxin (U)
> > ; wangyunjian
> >
> > Subject: Re: [Qemu-devel] Question about VM inner route entry's lost when
> > vhost-user reconnect
> >
> > On Fri, Mar 08, 2019 at 02:31:12AM +, Lilijun (Jerry, Cloud Networking)
>
> -Original Message-
> From: Stefan Hajnoczi [mailto:stefa...@gmail.com]
> Sent: Monday, March 11, 2019 5:47 PM
> To: Lilijun (Jerry, Cloud Networking)
> Cc: qemu-devel@nongnu.org; wangxin (U)
> ; wangyunjian
>
> Subject: Re: [Qemu-devel] Question about VM
On Fri, Mar 08, 2019 at 02:31:12AM +, Lilijun (Jerry, Cloud Networking)
wrote:
> This problem is related with backend vhost-user socket abnormal cases, we
> shouldn't ask customers to configure it manually for backend's issues or
> depends on guest OS's network configuration.
In Step 1 you
to:stefa...@gmail.com]
> Sent: Wednesday, March 06, 2019 6:07 PM
> To: Lilijun (Jerry, Cloud Networking)
> Cc: qemu-devel@nongnu.org; wangxin (U)
> ; wangyunjian
>
> Subject: Re: [Qemu-devel] Question about VM inner route entry's lost when
> vhost-user reconnect
>
&
On Fri, Mar 08, 2019 at 01:53:28AM +, Lilijun (Jerry, Cloud Networking)
wrote:
> > -Original Message-
> > From: Michael S. Tsirkin [mailto:m...@redhat.com]
> >
> > On Wed, Mar 06, 2019 at 07:36:44AM +, Lilijun (Jerry, Cloud Networking)
> > wrote:
> > > Thanks a lot for your advice
> -Original Message-
> From: Michael S. Tsirkin [mailto:m...@redhat.com]
>
> On Wed, Mar 06, 2019 at 07:36:44AM +, Lilijun (Jerry, Cloud Networking)
> wrote:
> > Thanks a lot for your advice.
> >
> > Maybe there are two methods to add this option:
> > 1) Firstly, add a vhost-user proto
On Thu, 7 Mar 2019, BALATON Zoltan wrote:
I still have the unfinished version using the callbacks which might work with
force_shadow like for cirrus but I'd need to finish and clean that up. Now
that we have both implemented probably will allow switching between them but
may not be able to do i
On Thu, 7 Mar 2019, Gerd Hoffmann wrote:
On Wed, Mar 06, 2019 at 02:50:36PM +0100, BALATON Zoltan wrote:
On Wed, 6 Mar 2019, Gerd Hoffmann wrote:
On Wed, Mar 06, 2019 at 12:48:59AM +0100, BALATON Zoltan wrote:
On Tue, 5 Mar 2019, Gerd Hoffmann wrote:
Use dpy_cursor_define().
I've done that
On Wed, Mar 06, 2019 at 02:50:36PM +0100, BALATON Zoltan wrote:
> On Wed, 6 Mar 2019, Gerd Hoffmann wrote:
> > On Wed, Mar 06, 2019 at 12:48:59AM +0100, BALATON Zoltan wrote:
> > > On Tue, 5 Mar 2019, Gerd Hoffmann wrote:
> > > > Use dpy_cursor_define().
> > >
> > > I've done that but it's not wor
On Wed, Mar 06, 2019 at 07:36:44AM +, Lilijun (Jerry, Cloud Networking)
wrote:
> Thanks a lot for your advice.
>
> Maybe there are two methods to add this option:
> 1) Firstly, add a vhost-user protocol feature to tell Qemu if hide the
> disconnects from the guest. Here we just need the bac
On Wed, 6 Mar 2019, Gerd Hoffmann wrote:
On Wed, Mar 06, 2019 at 12:48:59AM +0100, BALATON Zoltan wrote:
On Tue, 5 Mar 2019, Gerd Hoffmann wrote:
Use dpy_cursor_define().
I've done that but it's not working very well. The mouse pointer is quite
jumpy with this and there are some problems upda
On Mon, Mar 04, 2019 at 08:26:23AM +, Lilijun (Jerry, Cloud Networking)
wrote:
> I am running my VM using vhost-user NIC with OVS-DPDK. The steps of my
> question is shown as follows:
> 1) In the VM, I add one route entry manually on the vNIC eth0 using the
> linux tool route.
>
Thanks a lot for your advice.
Maybe there are two methods to add this option:
1) Firstly, add a vhost-user protocol feature to tell Qemu if hide the
disconnects from the guest. Here we just need the backend such as dpdk
vhostuser to support this option and the feature.
2) Secondly, add a VM XML
On Wed, Mar 06, 2019 at 12:48:59AM +0100, BALATON Zoltan wrote:
> On Tue, 5 Mar 2019, Gerd Hoffmann wrote:
> > On Mon, Mar 04, 2019 at 03:58:00PM +0100, BALATON Zoltan wrote:
> > > Hello,
> > >
> > > I'm trying to implement hardware cursor for ati-vga before submitting the
> > > last version of it
On Tue, 5 Mar 2019, Gerd Hoffmann wrote:
On Mon, Mar 04, 2019 at 03:58:00PM +0100, BALATON Zoltan wrote:
Hello,
I'm trying to implement hardware cursor for ati-vga before submitting the
last version of it before the freeze.
Use dpy_cursor_define().
I've done that but it's not working very w
On Mon, Mar 04, 2019 at 03:58:00PM +0100, BALATON Zoltan wrote:
> Hello,
>
> I'm trying to implement hardware cursor for ati-vga before submitting the
> last version of it before the freeze.
Use dpy_cursor_define().
cheers,
Gerd
On Mon, Mar 04, 2019 at 11:46:32AM +, Lilijun (Jerry, Cloud Networking)
wrote:
> Hi all,
>
> I am running my VM using vhost-user NIC with OVS-DPDK. The steps of my
> question is shown as follows:
> 1) In the VM, I add one route entry manually on the vNIC eth0 using
> "route add
Hello,
I'm trying to implement hardware cursor for ati-vga before submitting the
last version of it before the freeze. (This was found to be used at least
by MorphOS and Mac OS X.) I've found that vga has facilities for this
already (used by cirrus) with the cursor_invalidate() and
cursor_dra
Hi all,
I am running my VM using vhost-user NIC with OVS-DPDK. The steps of my
question is shown as follows:
1) In the VM, I add one route entry manually on the vNIC eth0 using "route
add default gw 192.168.1.2".
2) If openvswitch service was restarted, or the process ovs-vswit
Hi all,
I am running my VM using vhost-user NIC with OVS-DPDK. The steps of my
question is shown as follows:
1) In the VM, I add one route entry manually on the vNIC eth0 using the
linux tool route.
2) When restarting openvswitch service for the crash of the ovs-vswitchd,
qem
On 2/26/19 5:51 AM, Zhan Adlun wrote:
> Dear Sir:
> Sorry to bother you. I use dirty bitmap to do backup in KVM. I could
> get output from the terminal when I use the command ' virsh
> qemu-monitor-event DOMAIN --timestamp --loop', but when using ' virsh
> qemu-monitor-event DOMAIN --times
On 2/26/19 6:51 AM, Zhan Adlun wrote:
> Dear Sir:
> Sorry to bother you. I use dirty bitmap to do backup in KVM. I could
> get output from the terminal when I use the command ' virsh
> qemu-monitor-event DOMAIN --timestamp --loop', but when using ' virsh
> qemu-monitor-event DOMAIN --ti
Dear Sir:
Sorry to bother you. I use dirty bitmap to do backup in KVM. I could get
output from the terminal when I use the command ' virsh qemu-monitor-event
DOMAIN --timestamp --loop', but when using ' virsh qemu-monitor-event DOMAIN
--timestamp --loop > /file ' to redirect the output to
Fam Zheng 于2018年12月20日周四 上午9:26写道：
>
>
> > On Dec 20, 2018, at 06:58, Li Qiang wrote:
> >
> > Hello Paolo
> >
> > Thanks for your kind reply.
> >
> > Yes, aio_poll and aio_ctx_dispatch mostly run in different threads,
> though
> > Sometimes they can run in a thread nested from Fam’s slides:
> >
> On Dec 20, 2018, at 06:58, Li Qiang wrote:
>
> Hello Paolo
>
> Thanks for your kind reply.
>
> Yes, aio_poll and aio_ctx_dispatch mostly run in different threads, though
> Sometimes they can run in a thread nested from Fam’s slides:
> →http://events17.linuxfoundation.org/sites/events/files
On 19/12/18 11:05, Li Qiang wrote:
> Sent it to qemu-devel.
>
> Li Qiang mailto:liq...@gmail.com>> 于2018年12月19日周
> 三 下午6:04写道：
>
> Hello Paolo, Stefan, Fam and all,
>
> Here I have a question about 'aio_poll'.
> IIUC the 'aio_poll' is (mostly) used for synchronous IO
> as I see a
Sent it to qemu-devel.
Li Qiang 于2018年12月19日周三 下午6:04写道：
> Hello Paolo, Stefan, Fam and all,
>
> Here I have a question about 'aio_poll'.
> IIUC the 'aio_poll' is (mostly) used for synchronous IO
> as I see a lot of code like this:
> while(condition)
> aio_poll();
>
> However it seems the 'aio_
1 - 100 of 1093 matches
Mail list logo
