It does not currently appear to be possible to attach/detach a filesystem
with kvm through the C API or virsh. Looking at
src/qemu/qemu_driver.c:qemuDomain{Attach,Detach,Update}Config,
VIR_DOMAIN_DEVICE_FS is not a case within the switch statement for
dev-type.
Is support for this planned for the
On Fri, Mar 16, 2012 at 7:35 AM, Eric Blake ebl...@redhat.com wrote:
On 03/15/2012 08:26 PM, Jesse Cook wrote:
v0.9.10 client did not want to play nicely with the v0.9.10 server via
qemu+ssh. I got frustrated and just tried running the test from a
client running an older version of libvirt
On Thu, Mar 15, 2012 at 3:42 AM, Osier Yang jy...@redhat.com wrote:
On 03/15/2012 09:42 AM, Jesse J. Cook wrote:
256 (8 bits) is insufficient for large scale deployments. 65536 (16 bits)
is a
more appropriate limit and should be sufficient. You are more likely to
run
into other system
On Thu, Mar 15, 2012 at 5:14 AM, Daniel P. Berrange berra...@redhat.com wrote:
On Wed, Mar 14, 2012 at 08:42:35PM -0500, Jesse J. Cook wrote:
256 (8 bits) is insufficient for large scale deployments. 65536 (16
bits) is a
more appropriate limit and should be sufficient. You are more likely
Just to clarify, you would like to see:
v0.9.10 pre-patch client talk to v0.9.10 patch server
v0.9.10 patch client talk to v0.9.10 pre-patch server
Would the test code I used in my cover letter be sufficient? If so, I
could probably test this fairly easily and quickly today.
On Thu, Mar 15,
On Thu, Mar 15, 2012 at 11:47 AM, Eric Blake ebl...@redhat.com wrote:
On 03/15/2012 08:31 AM, Eric Blake wrote:
It may also be worth considering the addition of _just_ a new ranged RPC
call, but no new public API, by making the public API smart enough to
automatically call the ranged RPC
On Thu, Mar 15, 2012 at 1:10 PM, Eric Blake ebl...@redhat.com wrote:
On 03/15/2012 11:48 AM, Daniel P. Berrange wrote:
Using the sequence of RPC calls to iterate over this is only
addressing that second part of memory usage. So I'm not really
feeling that's a huge win, given the complexity it
On Thu, Mar 15, 2012 at 9:43 AM, Eric Blake ebl...@redhat.com wrote:
On 03/15/2012 05:51 AM, Daniel P. Berrange wrote:
On Thu, Mar 15, 2012 at 06:22:38AM -0500, Jesse Cook wrote:
Just to clarify, you would like to see:
I have not actually tried this, but based on my understanding of the RPC
This patch enables the relative backing file path support provided by
qemu-img create.
If a relative path is specified for the backing file, it is converted
to an absolute path using the storage pool path. The absolute path is
used to verify that the backing file exists. If the backing file
This patch enables the relative backing file path support provided by
qemu-img create.
If the storage pool is not found with the specified path, check if the
file exists relative to the pool where the new image will be created by
prepending the storage pool path.
---
10 matches
Mail list logo
