Re: [Qemu-devel] [PATCH v2] blockdev: reset werror/rerror on drive_del

2013-06-05 Thread Stefan Hajnoczi
On Wed, Jun 05, 2013 at 10:33:14AM +0200, Stefan Hajnoczi wrote: > Paolo Bonzini suggested the following test case: > > 1. Launch a guest and wait at the GRUB boot menu: > > qemu-system-x86_64 -enable-kvm -m 1024 \ >-drive if=none,cache=none,file=test.img,id=foo,werror=stop,rerror=stop >

Re: [Qemu-devel] [PATCH v2] blockdev: reset werror/rerror on drive_del

2013-06-05 Thread Stefan Hajnoczi
On Wed, Jun 05, 2013 at 11:00:32AM +0200, Kevin Wolf wrote: > Am 05.06.2013 um 10:33 hat Stefan Hajnoczi geschrieben: > > Paolo Bonzini suggested the following test case: > > > > 1. Launch a guest and wait at the GRUB boot menu: > > > > qemu-system-x86_64 -enable-kvm -m 1024 \ > >-drive if

Re: [Qemu-devel] [PATCH v2] blockdev: reset werror/rerror on drive_del

2013-06-05 Thread Kevin Wolf
Am 05.06.2013 um 10:33 hat Stefan Hajnoczi geschrieben: > Paolo Bonzini suggested the following test case: > > 1. Launch a guest and wait at the GRUB boot menu: > > qemu-system-x86_64 -enable-kvm -m 1024 \ >-drive if=none,cache=none,file=test.img,id=foo,werror=stop,rerror=stop >-device

[Qemu-devel] [PATCH v2] blockdev: reset werror/rerror on drive_del

2013-06-05 Thread Stefan Hajnoczi
Paolo Bonzini suggested the following test case: 1. Launch a guest and wait at the GRUB boot menu: qemu-system-x86_64 -enable-kvm -m 1024 \ -drive if=none,cache=none,file=test.img,id=foo,werror=stop,rerror=stop -device virtio-blk-pci,drive=foo,id=virtio0,addr=4 2. Hot unplug the device: