search for: 38ced0208491

Displaying 12 results from an estimated 12 matches for "38ced0208491".

vhost changes (batched) in linux-next after 12/13 trigger random crashes in KVM guests after reboot
2020 Feb 06
2
vhost changes (batched) in linux-next after 12/13 trigger random crashes in KVM guests after reboot
On Thu, Feb 06, 2020 at 04:12:21PM +0100, Christian Borntraeger wrote: > > > On 06.02.20 15:22, eperezma at redhat.com wrote: > > Hi Christian. > > > > Could you try this patch on top of ("38ced0208491 vhost: use batched version by default")? > > > > It will not solve your first random crash but it should help with the lost of network connectivity. > > > > Please let me know how does it goes. > > > 38ced0208491 + this seem to be ok. > > Not sure if...
vhost changes (batched) in linux-next after 12/13 trigger random crashes in KVM guests after reboot
2020 Feb 06
2
vhost changes (batched) in linux-next after 12/13 trigger random crashes in KVM guests after reboot
On Thu, Feb 06, 2020 at 04:12:21PM +0100, Christian Borntraeger wrote: > > > On 06.02.20 15:22, eperezma at redhat.com wrote: > > Hi Christian. > > > > Could you try this patch on top of ("38ced0208491 vhost: use batched version by default")? > > > > It will not solve your first random crash but it should help with the lost of network connectivity. > > > > Please let me know how does it goes. > > > 38ced0208491 + this seem to be ok. > > Not sure if...
vhost changes (batched) in linux-next after 12/13 trigger random crashes in KVM guests after reboot
2020 Feb 07
1
vhost changes (batched) in linux-next after 12/13 trigger random crashes in KVM guests after reboot
...04:12:21PM +0100, Christian Borntraeger wrote: > >>>> > >>>> > >>>> On 06.02.20 15:22, eperezma at redhat.com wrote: > >>>>> Hi Christian. > >>>>> > >>>>> Could you try this patch on top of ("38ced0208491 vhost: use batched version by default")? > >>>>> > >>>>> It will not solve your first random crash but it should help with the lost of network connectivity. > >>>>> > >>>>> Please let me know how does it goes. > >&...
vhost changes (batched) in linux-next after 12/13 trigger random crashes in KVM guests after reboot
2020 Jan 07
6
vhost changes (batched) in linux-next after 12/13 trigger random crashes in KVM guests after reboot
On 07.01.20 10:39, Michael S. Tsirkin wrote: > On Tue, Jan 07, 2020 at 09:59:16AM +0100, Christian Borntraeger wrote: >> >> >> On 06.01.20 11:50, Michael S. Tsirkin wrote: >>> On Wed, Dec 18, 2019 at 04:59:02PM +0100, Christian Borntraeger wrote: >>>> On 18.12.19 16:10, Michael S. Tsirkin wrote: >>>>> On Wed, Dec 18, 2019 at 03:43:43PM
vhost changes (batched) in linux-next after 12/13 trigger random crashes in KVM guests after reboot
2020 Jan 07
6
vhost changes (batched) in linux-next after 12/13 trigger random crashes in KVM guests after reboot
On 07.01.20 10:39, Michael S. Tsirkin wrote: > On Tue, Jan 07, 2020 at 09:59:16AM +0100, Christian Borntraeger wrote: >> >> >> On 06.01.20 11:50, Michael S. Tsirkin wrote: >>> On Wed, Dec 18, 2019 at 04:59:02PM +0100, Christian Borntraeger wrote: >>>> On 18.12.19 16:10, Michael S. Tsirkin wrote: >>>>> On Wed, Dec 18, 2019 at 03:43:43PM
vhost changes (batched) in linux-next after 12/13 trigger random crashes in KVM guests after reboot
2020 Feb 06
0
vhost changes (batched) in linux-next after 12/13 trigger random crashes in KVM guests after reboot
On 06.02.20 15:22, eperezma at redhat.com wrote: > Hi Christian. > > Could you try this patch on top of ("38ced0208491 vhost: use batched version by default")? > > It will not solve your first random crash but it should help with the lost of network connectivity. > > Please let me know how does it goes. 38ced0208491 + this seem to be ok. Not sure if you can make out anything of this (and the p...
vhost changes (batched) in linux-next after 12/13 trigger random crashes in KVM guests after reboot
2020 Feb 07
0
vhost changes (batched) in linux-next after 12/13 trigger random crashes in KVM guests after reboot
...elia. On 06.02.20 23:17, Michael S. Tsirkin wrote: > On Thu, Feb 06, 2020 at 04:12:21PM +0100, Christian Borntraeger wrote: >> >> >> On 06.02.20 15:22, eperezma at redhat.com wrote: >>> Hi Christian. >>> >>> Could you try this patch on top of ("38ced0208491 vhost: use batched version by default")? >>> >>> It will not solve your first random crash but it should help with the lost of network connectivity. >>> >>> Please let me know how does it goes. >> >> >> 38ced0208491 + this seem to be ok. &g...
vhost changes (batched) in linux-next after 12/13 trigger random crashes in KVM guests after reboot
2020 Feb 07
0
vhost changes (batched) in linux-next after 12/13 trigger random crashes in KVM guests after reboot
...;>> On Thu, Feb 06, 2020 at 04:12:21PM +0100, Christian Borntraeger wrote: >>>> >>>> >>>> On 06.02.20 15:22, eperezma at redhat.com wrote: >>>>> Hi Christian. >>>>> >>>>> Could you try this patch on top of ("38ced0208491 vhost: use batched version by default")? >>>>> >>>>> It will not solve your first random crash but it should help with the lost of network connectivity. >>>>> >>>>> Please let me know how does it goes. >>>> >>>&gt...
vhost changes (batched) in linux-next after 12/13 trigger random crashes in KVM guests after reboot
2020 Feb 10
0
vhost changes (batched) in linux-next after 12/13 trigger random crashes in KVM guests after reboot
...t;>>> > >>>> > >>>> On 06.02.20 15:22, eperezma at redhat.com <mailto:eperezma at redhat.com> wrote: > >>>>> Hi Christian. > >>>>> > >>>>> Could you try this patch on top of ("38ced0208491 vhost: use batched version by default")? > >>>>> > >>>>> It will not solve your first random crash but it should help with the lost of network connectivity. > >>>>> > >>>>> Please let me know how does it go...
vhost changes (batched) in linux-next after 12/13 trigger random crashes in KVM guests after reboot
2020 Feb 06
0
vhost changes (batched) in linux-next after 12/13 trigger random crashes in KVM guests after reboot
On Thu, Feb 06, 2020 at 03:22:39PM +0100, eperezma at redhat.com wrote: > Hi Christian. > > Could you try this patch on top of ("38ced0208491 vhost: use batched version by default")? > > It will not solve your first random crash but it should help with the lost of network connectivity. > > Please let me know how does it goes. > > Thanks! > > >From 99f0f543f3939dbe803988c9153a95616ccccacd Mon Sep 17 00:...
vhost changes (batched) in linux-next after 12/13 trigger random crashes in KVM guests after reboot
2020 Feb 07
16
vhost changes (batched) in linux-next after 12/13 trigger random crashes in KVM guests after reboot
...S. Tsirkin wrote: > > On Thu, Feb 06, 2020 at 04:12:21PM +0100, Christian Borntraeger wrote: > >> > >> > >> On 06.02.20 15:22, eperezma at redhat.com wrote: > >>> Hi Christian. > >>> > >>> Could you try this patch on top of ("38ced0208491 vhost: use batched version by default")? > >>> > >>> It will not solve your first random crash but it should help with the lost of network connectivity. > >>> > >>> Please let me know how does it goes. > >> > >> > >> 38...
vhost changes (batched) in linux-next after 12/13 trigger random crashes in KVM guests after reboot
2020 Feb 07
16
vhost changes (batched) in linux-next after 12/13 trigger random crashes in KVM guests after reboot
...S. Tsirkin wrote: > > On Thu, Feb 06, 2020 at 04:12:21PM +0100, Christian Borntraeger wrote: > >> > >> > >> On 06.02.20 15:22, eperezma at redhat.com wrote: > >>> Hi Christian. > >>> > >>> Could you try this patch on top of ("38ced0208491 vhost: use batched version by default")? > >>> > >>> It will not solve your first random crash but it should help with the lost of network connectivity. > >>> > >>> Please let me know how does it goes. > >> > >> > >> 38...