Am 09.01.2014 um 17:08 hat Peter Lieven geschrieben:
Am 09.01.2014 15:13, schrieb Kevin Wolf:
Am 26.12.2013 um 13:48 hat Peter Lieven geschrieben:
v4-v5:
- disussed with Ronnie and decided to move URL + Paramter parsing to
LibNFS.
This allows for URL parameter processing directly
On 10.01.2014 12:40, Kevin Wolf wrote:
Am 09.01.2014 um 17:08 hat Peter Lieven geschrieben:
Am 09.01.2014 15:13, schrieb Kevin Wolf:
Am 26.12.2013 um 13:48 hat Peter Lieven geschrieben:
v4-v5:
- disussed with Ronnie and decided to move URL + Paramter parsing to LibNFS.
This allows for
Il 10/01/2014 13:12, Peter Lieven ha scritto:
Then I shall convert everything to a qapi schema whereby the current
design of libnfs is designed to work with plain URLs.
No, no one is asking you to do this. URLs are fine, but I agree with
Kevin that parsing them in QEMU is better.
Also because
On Fri, Jan 10, 2014 at 4:30 AM, Paolo Bonzini pbonz...@redhat.com wrote:
Il 10/01/2014 13:12, Peter Lieven ha scritto:
Then I shall convert everything to a qapi schema whereby the current
design of libnfs is designed to work with plain URLs.
No, no one is asking you to do this. URLs are
On 10.01.2014 15:49, ronnie sahlberg wrote:
On Fri, Jan 10, 2014 at 4:30 AM, Paolo Bonzini pbonz...@redhat.com wrote:
Il 10/01/2014 13:12, Peter Lieven ha scritto:
Then I shall convert everything to a qapi schema whereby the current
design of libnfs is designed to work with plain URLs.
No, no
Am 10.01.2014 um 16:05 hat Peter Lieven geschrieben:
On 10.01.2014 15:49, ronnie sahlberg wrote:
On Fri, Jan 10, 2014 at 4:30 AM, Paolo Bonzini pbonz...@redhat.com wrote:
Il 10/01/2014 13:12, Peter Lieven ha scritto:
Then I shall convert everything to a qapi schema whereby the current
design
Am 10.01.2014 16:46, schrieb Kevin Wolf:
Am 10.01.2014 um 16:05 hat Peter Lieven geschrieben:
On 10.01.2014 15:49, ronnie sahlberg wrote:
On Fri, Jan 10, 2014 at 4:30 AM, Paolo Bonzini pbonz...@redhat.com wrote:
Il 10/01/2014 13:12, Peter Lieven ha scritto:
Then I shall convert everything to
On Fri, Jan 10, 2014 at 8:10 AM, Peter Lieven p...@kamp.de wrote:
Ronnie, can you also give a short advise on Kevin's question about short
reads.
I think they can happen if we read beyond past EOF or not?
Short reads should normally not happen in libnfs itself since servers
are often
Il 10/01/2014 18:16, ronnie sahlberg ha scritto:
There is a common exception though, for the case where you read past
the end of file.
So short reads should normally not happen. Unless QEMU or the guest
sends a request to libnfs to read past the end of the file.
Yes, this can happen in QEMU
Von meinem iPad gesendet
Am 10.01.2014 um 19:05 schrieb Paolo Bonzini pbonz...@redhat.com:
Il 10/01/2014 18:16, ronnie sahlberg ha scritto:
There is a common exception though, for the case where you read past
the end of file.
So short reads should normally not happen. Unless QEMU or the
Il 10/01/2014 19:07, Peter Lieven ha scritto:
Von meinem iPad gesendet
Am 10.01.2014 um 19:05 schrieb Paolo Bonzini pbonz...@redhat.com:
Il 10/01/2014 18:16, ronnie sahlberg ha scritto:
There is a common exception though, for the case where you read past
the end of file.
So short
Am 10.01.2014 19:24, schrieb Paolo Bonzini:
Il 10/01/2014 19:07, Peter Lieven ha scritto:
Von meinem iPad gesendet
Am 10.01.2014 um 19:05 schrieb Paolo Bonzini pbonz...@redhat.com:
Il 10/01/2014 18:16, ronnie sahlberg ha scritto:
There is a common exception though, for the case where you
Am 26.12.2013 um 13:48 hat Peter Lieven geschrieben:
This patch adds native support for accessing images on NFS shares without
the requirement to actually mount the entire NFS share on the host.
NFS Images can simply be specified by an url of the form:
nfs://host/export/filename
For
Am 09.01.2014 15:13, schrieb Kevin Wolf:
Am 26.12.2013 um 13:48 hat Peter Lieven geschrieben:
This patch adds native support for accessing images on NFS shares without
the requirement to actually mount the entire NFS share on the host.
NFS Images can simply be specified by an url of the form:
On Fri, Jan 03, 2014 at 12:28:31PM +0100, Peter Lieven wrote:
On 03.01.2014 11:37, Stefan Hajnoczi wrote:
Looks good. In order to merge this new block driver qemu-iotests
support for nfs is required. That way the block driver can be exercised
and checked for regressions (I guess you
On 06.01.2014 02:18, Stefan Hajnoczi wrote:
On Fri, Jan 03, 2014 at 12:28:31PM +0100, Peter Lieven wrote:
On 03.01.2014 11:37, Stefan Hajnoczi wrote:
Looks good. In order to merge this new block driver qemu-iotests
support for nfs is required. That way the block driver can be exercised
and
Looks good. In order to merge this new block driver qemu-iotests
support for nfs is required. That way the block driver can be exercised
and checked for regressions (I guess you performed manual testing
during development).
Please see tests/qemu-iotests/common for examples of
On 03.01.2014 11:37, Stefan Hajnoczi wrote:
Looks good. In order to merge this new block driver qemu-iotests
support for nfs is required. That way the block driver can be exercised
and checked for regressions (I guess you performed manual testing
during development).
Please see
On 03.01.2014 11:37, Stefan Hajnoczi wrote:
Looks good. In order to merge this new block driver qemu-iotests
support for nfs is required. That way the block driver can be exercised
and checked for regressions (I guess you performed manual testing
during development).
Please see
On 03.01.2014 11:37, Stefan Hajnoczi wrote:
Looks good. In order to merge this new block driver qemu-iotests
support for nfs is required. That way the block driver can be exercised
and checked for regressions (I guess you performed manual testing
during development).
Please see
This patch adds native support for accessing images on NFS shares without
the requirement to actually mount the entire NFS share on the host.
NFS Images can simply be specified by an url of the form:
nfs://host/export/filename
For example:
qemu-img create -f qcow2
21 matches
Mail list logo
