Il 09/07/2012 09:11, Wayne Xia ha scritto:
> Paolo, what do you think write a short section in document for it, but
> make no change to code?
That's okay, but perhaps for 1.2 we can fix the probing. I'll apply the
patch to nbd-next and not submit it until it's clear that 1.2 will still
have the
Paolo, what do you think write a short section in document for it, but
make no change to code?
于 2012-7-5 16:34, Paolo Bonzini 写道:
Il 05/07/2012 10:13, Michael Tokarev ha scritto:
Hi Paolo, should I make a patch to make persistent the default for
qemu-nbd?
Yes, why not. However, as mention
于 2012-7-5 16:34, Paolo Bonzini 写道:
Il 05/07/2012 10:13, Michael Tokarev ha scritto:
Hi Paolo, should I make a patch to make persistent the default for
qemu-nbd?
Yes, why not. However, as mentioned above client mode should still be
non-persistent.
I don't think this makes sense or is good: n
Il 05/07/2012 10:13, Michael Tokarev ha scritto:
>>> >> Hi Paolo, should I make a patch to make persistent the default for
>>> >> qemu-nbd?
>> >
>> > Yes, why not. However, as mentioned above client mode should still be
>> > non-persistent.
> I don't think this makes sense or is good: now we'll n
On 05.07.2012 10:42, Paolo Bonzini wrote:
> Il 05/07/2012 05:29, Wayne Xia ha scritto:
[]
>> Hi Paolo, should I make a patch to make persistent the default for
>> qemu-nbd?
>
> Yes, why not. However, as mentioned above client mode should still be
> non-persistent.
I don't think this makes sense
Il 05/07/2012 05:29, Wayne Xia ha scritto:
>>
>>> +
>>> + Note: When qemu-nbd was used to export a disk that would be used
>>> by QEMU
>>> +block device, -t or --persistent must be set for that QEMU nbd
>>> client would try
>>> +connect more than one time. For eg:
>>> + qemu-nbd ./simple.img -p 1
于 2012-7-3 19:55, Paolo Bonzini 写道:
Il 03/07/2012 13:05, xiaw...@linux.vnet.ibm.com ha scritto:
+
+ Note: When qemu-nbd was used to export a disk that would be used by QEMU
+block device, -t or --persistent must be set for that QEMU nbd client would try
+connect more than one time. For eg:
+ q
Am 03.07.2012 21:45, schrieb Michael Tokarev:
> On 03.07.2012 15:05, xiaw...@linux.vnet.ibm.com wrote:
>> From: Wenchao Xia
>>
>> Qemu system emulator reports only fails that make people confused
>> about why, when it is invoked with nbd block device tring to connect
>> qemu-nbd server. In fact
Il 04/07/2012 04:14, Wayne Xia ha scritto:
>
>> of the internal structure inside - be it raw, or qcow, or anything else.
>> So, if you specify the format of the device explicitly, by using
>> format=raw, only single connection will be made.
> thanks, that helped me. A bit more question: is there
于 2012-7-4 0:18, 陳韋任 (Wei-Ren Chen) 写道:
+
+ Note: When qemu-nbd was used to export a disk that would be used by QEMU
+block device, -t or --persistent must be set for that QEMU nbd client would try
+connect more than one time. For eg:
^^
Not a native engli
于 2012-7-3 19:55, Paolo Bonzini 写道:
Il 03/07/2012 13:05, xiaw...@linux.vnet.ibm.com ha scritto:
+
+ Note: When qemu-nbd was used to export a disk that would be used by QEMU
+block device, -t or --persistent must be set for that QEMU nbd client would try
+connect more than one time. For eg:
+ q
On 03.07.2012 15:05, xiaw...@linux.vnet.ibm.com wrote:
From: Wenchao Xia
Qemu system emulator reports only fails that make people confused
about why, when it is invoked with nbd block device tring to connect
qemu-nbd server. In fact qemu will try connect server for several
times but server on
On 03.07.2012 15:05, xiaw...@linux.vnet.ibm.com wrote:
> From: Wenchao Xia
>
> Qemu system emulator reports only fails that make people confused
> about why, when it is invoked with nbd block device tring to connect
> qemu-nbd server. In fact qemu will try connect server for several
> times but
> +
> + Note: When qemu-nbd was used to export a disk that would be used by QEMU
> +block device, -t or --persistent must be set for that QEMU nbd client would
> try
> +connect more than one time. For eg:
^^
Not a native english speaker, but I never see such u
From: Wenchao Xia
Qemu system emulator reports only fails that make people confused
about why, when it is invoked with nbd block device tring to connect
qemu-nbd server. In fact qemu will try connect server for several
times but server only accept one connect by default.
I paid some times to
Il 03/07/2012 13:05, xiaw...@linux.vnet.ibm.com ha scritto:
> +
> + Note: When qemu-nbd was used to export a disk that would be used by QEMU
> +block device, -t or --persistent must be set for that QEMU nbd client would
> try
> +connect more than one time. For eg:
> + qemu-nbd ./simple.img -p 10
16 matches
Mail list logo
