On 20/04/2015 22:34, Michael S. Tsirkin wrote:
On Mon, Apr 20, 2015 at 09:10:02PM +0200, Paolo Bonzini wrote:
On 20/04/2015 19:36, Michael S. Tsirkin wrote:
At the implementation level, there's one big issue you seem to have
missed: DMA to invalid memory addresses causes a crash in memory
On Tue, Apr 21, 2015 at 01:50:33PM +0800, Fam Zheng wrote:
On Tue, 04/21 07:22, Michael S. Tsirkin wrote:
On Tue, Apr 21, 2015 at 10:37:00AM +0800, Fam Zheng wrote:
On Mon, 04/20 19:36, Michael S. Tsirkin wrote:
On Fri, Apr 17, 2015 at 03:59:15PM +0800, Fam Zheng wrote:
Currently,
On Mon, 04/20 17:13, Cornelia Huck wrote:
On Fri, 17 Apr 2015 15:59:15 +0800
Fam Zheng f...@redhat.com wrote:
Currently, virtio code chooses to kill QEMU if the guest passes any invalid
data with vring. That has drawbacks such as losing unsaved data (e.g. when
guest user is writing a
On Tue, 04/21 11:08, Cornelia Huck wrote:
On Tue, 21 Apr 2015 16:38:31 +0800
Fam Zheng f...@redhat.com wrote:
On Tue, 04/21 10:04, Cornelia Huck wrote:
On Tue, 21 Apr 2015 15:44:02 +0800
Fam Zheng f...@redhat.com wrote:
On Mon, 04/20 17:13, Cornelia Huck wrote:
On Fri, 17
On Tue, Apr 21, 2015 at 08:52:36AM +0200, Paolo Bonzini wrote:
On 20/04/2015 22:34, Michael S. Tsirkin wrote:
On Mon, Apr 20, 2015 at 09:10:02PM +0200, Paolo Bonzini wrote:
On 20/04/2015 19:36, Michael S. Tsirkin wrote:
At the implementation level, there's one big issue you seem to
On Tue, 04/21 10:04, Cornelia Huck wrote:
On Tue, 21 Apr 2015 15:44:02 +0800
Fam Zheng f...@redhat.com wrote:
On Mon, 04/20 17:13, Cornelia Huck wrote:
On Fri, 17 Apr 2015 15:59:15 +0800
Fam Zheng f...@redhat.com wrote:
Currently, virtio code chooses to kill QEMU if the guest
On Tue, 21 Apr 2015 16:38:31 +0800
Fam Zheng f...@redhat.com wrote:
On Tue, 04/21 10:04, Cornelia Huck wrote:
On Tue, 21 Apr 2015 15:44:02 +0800
Fam Zheng f...@redhat.com wrote:
On Mon, 04/20 17:13, Cornelia Huck wrote:
On Fri, 17 Apr 2015 15:59:15 +0800
Fam Zheng
On Tue, 21 Apr 2015 15:44:02 +0800
Fam Zheng f...@redhat.com wrote:
On Mon, 04/20 17:13, Cornelia Huck wrote:
On Fri, 17 Apr 2015 15:59:15 +0800
Fam Zheng f...@redhat.com wrote:
Currently, virtio code chooses to kill QEMU if the guest passes any
invalid
data with vring. That has
On Tue, Apr 21, 2015 at 05:16:53PM +0800, Fam Zheng wrote:
On Tue, 04/21 11:08, Cornelia Huck wrote:
On Tue, 21 Apr 2015 16:38:31 +0800
Fam Zheng f...@redhat.com wrote:
On Tue, 04/21 10:04, Cornelia Huck wrote:
On Tue, 21 Apr 2015 15:44:02 +0800
Fam Zheng f...@redhat.com wrote:
On Tue, 21 Apr 2015 17:16:53 +0800
Fam Zheng f...@redhat.com wrote:
On Tue, 04/21 11:08, Cornelia Huck wrote:
My concern is mainly about legacy setups that aren't used interactively.
How about pausing guest and generating an QMP event?
That sounds good as well.
On Mon, Apr 20, 2015 at 09:10:02PM +0200, Paolo Bonzini wrote:
On 20/04/2015 19:36, Michael S. Tsirkin wrote:
At the implementation level, there's one big issue you seem to have
missed: DMA to invalid memory addresses causes a crash in memory core.
I'm not sure whether it makes sense to
On Mon, 04/20 22:34, Michael S. Tsirkin wrote:
On Mon, Apr 20, 2015 at 09:10:02PM +0200, Paolo Bonzini wrote:
On 20/04/2015 19:36, Michael S. Tsirkin wrote:
At the implementation level, there's one big issue you seem to have
missed: DMA to invalid memory addresses causes a crash in
On Tue, 04/21 07:22, Michael S. Tsirkin wrote:
On Tue, Apr 21, 2015 at 10:37:00AM +0800, Fam Zheng wrote:
On Mon, 04/20 19:36, Michael S. Tsirkin wrote:
On Fri, Apr 17, 2015 at 03:59:15PM +0800, Fam Zheng wrote:
Currently, virtio code chooses to kill QEMU if the guest passes any
On Tue, Apr 21, 2015 at 10:37:00AM +0800, Fam Zheng wrote:
On Mon, 04/20 19:36, Michael S. Tsirkin wrote:
On Fri, Apr 17, 2015 at 03:59:15PM +0800, Fam Zheng wrote:
Currently, virtio code chooses to kill QEMU if the guest passes any
invalid
data with vring.
That has drawbacks such
On Mon, 04/20 19:36, Michael S. Tsirkin wrote:
On Fri, Apr 17, 2015 at 03:59:15PM +0800, Fam Zheng wrote:
Currently, virtio code chooses to kill QEMU if the guest passes any invalid
data with vring.
That has drawbacks such as losing unsaved data (e.g. when
guest user is writing a very
On Fri, 17 Apr 2015 15:59:15 +0800
Fam Zheng f...@redhat.com wrote:
Currently, virtio code chooses to kill QEMU if the guest passes any invalid
data with vring. That has drawbacks such as losing unsaved data (e.g. when
guest user is writing a very long email), or possible denial of service in
On Fri, Apr 17, 2015 at 03:59:15PM +0800, Fam Zheng wrote:
Currently, virtio code chooses to kill QEMU if the guest passes any invalid
data with vring.
That has drawbacks such as losing unsaved data (e.g. when
guest user is writing a very long email), or possible denial of service in
a nested
On 20/04/2015 19:36, Michael S. Tsirkin wrote:
At the implementation level, there's one big issue you seem to have
missed: DMA to invalid memory addresses causes a crash in memory core.
I'm not sure whether it makes sense to recover from virtio core bugs
when we can't recover from device
Currently, virtio code chooses to kill QEMU if the guest passes any invalid
data with vring. That has drawbacks such as losing unsaved data (e.g. when
guest user is writing a very long email), or possible denial of service in
a nested vm use case where virtio device is passed through.
virtio-1
19 matches
Mail list logo
