If the file is readonly its not expected to grow so
save the blocking call to nfs_fstat_async and use
the value saved at connection time. Also important
the monitor (and thus the main loop) will not hang
if block device info is queried and the NFS share
is unresponsive.
Signed-off-by: Peter
If an image is opened with driver-specific options then attempting to
use snapshot_blkdev will fail with Driver specified twice.
The reason is that bs-filename is replaced with a full JSON object by
bdrv_refresh_filename() when such options are present:
-drive
On 24.08.2015 10:06, Peter Lieven wrote:
If the file is readonly its not expected to grow so
save the blocking call to nfs_fstat_async and use
the value saved at connection time. Also important
the monitor (and thus the main loop) will not hang
if block device info is queried and the NFS
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 24.08.2015 15:05, Alberto Garcia wrote:
If an image is opened with driver-specific options then attempting
to use snapshot_blkdev will fail with Driver specified twice.
The reason is that bs-filename is replaced with a full JSON object
by
Am 24.08.2015 um 20:39 schrieb Max Reitz:
On 24.08.2015 10:06, Peter Lieven wrote:
If the file is readonly its not expected to grow so
save the blocking call to nfs_fstat_async and use
the value saved at connection time. Also important
the monitor (and thus the main loop) will not hang
if
On 04.08.2015 14:14, Alberto Garcia wrote:
v7:
- Rebase against the current master.
- Update version number in the 'since' field of the
'cache-clean-interval' option.
v6: https://lists.gnu.org/archive/html/qemu-devel/2015-06/msg01929.html
- Update documentation to clarify what unused
On 24.08.2015 21:34, Peter Lieven wrote:
Am 24.08.2015 um 20:39 schrieb Max Reitz:
On 24.08.2015 10:06, Peter Lieven wrote:
If the file is readonly its not expected to grow so
save the blocking call to nfs_fstat_async and use
the value saved at connection time. Also important
the monitor
On 07/13/2015 06:18 AM, Kevin Wolf wrote:
Am 11.07.2015 um 03:05 hat John Snow geschrieben:
We're supposed to abort on transfers like this, unless we fill
Word 125 of our IDENTIFY data with a default transfer size, which
we don't currently do.
This is an ATA error, not a SCSI/ATAPI one.
