search for: head2

...-- a/docs/virt-v2v-input-vmware.pod +++ b/docs/virt-v2v-input-vmware.pod @@ -107,18 +107,6 @@ If you find a folder of files called F<I<guest>.vmx>, F<I<guest>.vmxf>, F<I<guest>.nvram> and one or more F<.vmdk> disk images, then you can use this method. -=head2 VMX: Remove VMware tools from Windows guests - -For Windows guests, you should remove VMware tools before conversion. -Although this is not strictly necessary, and the guest will still be -able to run, if you don't do this then the converted guest will -complain on every boot. The tools cannot...

Previously posted: https://www.redhat.com/archives/libguestfs/2018-November/msg00000.html https://www.redhat.com/archives/libguestfs/2018-November/msg00001.html This completes the split and rewrite of the virt-v2v manual to make it much simpler to understand and digest. Rich.

This patch is incomplete, but early feedback would be welcome. Rich.

...++++++++++++++++++++++++------ 2 files changed, 98 insertions(+), 17 deletions(-) diff --git a/docs/nbdkit-filter.pod b/docs/nbdkit-filter.pod index bf01db14..f15bdd96 100644 --- a/docs/nbdkit-filter.pod +++ b/docs/nbdkit-filter.pod @@ -339,12 +339,18 @@ an error message and return C<-1>. =head2 C<.list_exports> int (*list_exports) (nbdkit_next_list_exports *next, void *nxdata, - int readonly, int default_only, + int readonly, int is_tls, struct nbdkit_exports *exports); This intercepts the plugin C<.list_export...

...at callback it doesn't call the C<next> function then the corresponding method in the plugin will never be called. =head1 CALLBACKS C<struct nbdkit_filter> has some static fields describing the filter and optional callback functions which can be used to intercept plugin methods. =head2 C<.name> const char *name; This field (a string) is required, and B<must> contain only ASCII alphanumeric characters and be unique amongst all filters. =head2 C<.version> const char *version; Filters may optionally set a version string which is displayed in help and debuggi...

...in code). > --- > docs/nbdkit-plugin.pod | 47 +++++++++++++++-- > include/nbdkit-common.h | 3 ++ > server/nbdkit.syms | 3 ++ > server/public.c | 108 ++++++++++++++++++++++++++++++++++++++++ > 4 files changed, 156 insertions(+), 5 deletions(-) > > +=head2 C<nbdkit_peer_pid> > + > +(nbdkit E<ge> 1.24) > + > + int nbdkit_peer_pid (void); > + > +Return the peer process ID. This is only available when the client > +connected over a Unix domain socket, and only works for Linux. > + > +On success this returns the pe...

...rlier alias in a long transaction), or do we want to put in hedge wording that (in the future) a request might be split into smaller regions that get operated on in parallel (thereby making the end contents indeterminate when writing to two aliases of the same byte in one transaction)? > +=head2 C<start-end> > + > + start-end offset > + > +means that the source region starting at byte C<start> through to byte > +C<end> (inclusive) is mapped to C<offset> through to > +C<offset+(end-start)> in the output. > + > +For example: > + &g...

...for the guest domain virt-v2v uses a libvirt domain description to determine the current @@ -545,19 +536,18 @@ This will require a reboot if the host running Xen is the same host that will run KVM. This is because libvirt needs to connect to a running xen hypervisor to obtain its metadata. -=head2 ESX guests +=head2 Converting to run on libvirt/KVM =head3 Create a local storage pool for transferred storage -virt-v2v copies the guest storage to the local machine during import from an ESX -server. It creates new storage in a locally defined libvirt pool. This pool can -be defined using an...

...ently. It not recycling would be unexpected based on the behavior of many R functions but would preserve the current behavior while granting more fine-grained control to users that feel they need it. A rapidly thrown-together prototype of such a method for the head of a matrix case is as follows: head2 = function(x, n = 6L, ...) { indvecs = lapply(seq_along(dim(x)), function(i) { if(length(n) >= i) { ni = n[i] } else { ni = dim(x)[i] } if(ni < 0L) ni = max(nrow(x) + ni, 0L) else ni = min(ni, dim(x)[...

...re is an error, C<.can_trim> should call C<nbdkit_error> with an error message and return C<-1>. This callback is not required. If omitted, then we return true iff a -C<.trim> callback has been defined. +C<.trim> or C<.trim_fua> callback has been defined. + +=head2 C<.can_fua> + + int can_fua (void *handle); + +This is called during the option negotiation phase to find out if the +plugin supports the Forced Unit Access (FUA) flag on write and trim +requests. + +If there is an error, C<.can_fua> should call C<nbdkit_error> with an +error mess...

...into smaller regions > that get operated on in parallel (thereby making the end contents > indeterminate when writing to two aliases of the same byte in one > transaction)? I think I'd rather leave it unspecified. I'll add some caveat text to the documentation. > > >+=head2 C<start-end> > >+ > >+ start-end offset > >+ > >+means that the source region starting at byte C<start> through to byte > >+C<end> (inclusive) is mapped to C<offset> through to > >+C<offset+(end-start)> in the output. > >+...

...ould preserve the current behavior >> while granting more fine-grained control to users that >> feel they need it. >> >> A rapidly thrown-together prototype of such a method for >> the head of a matrix case is as follows: >> >> head2 = function(x, n = 6L, ...) { indvecs = >> lapply(seq_along(dim(x)), function(i) { if(length(n) >= >> i) { ni = n[i] } else { ni = dim(x)[i] } if(ni < 0L) ni = >> max(nrow(x) + ni, 0L) else ni = min(ni, dim(x)[i]) >> seq_len(ni) }) lstargs = c(list(x),in...

...k it +doesn't call the C<next> function then the corresponding method in the +plugin will never be called. + +=head1 CALLBACKS + +C<struct nbdkit_filter> has some static fields describing the filter +and optional callback functions which can be used to intercept plugin +methods. + +=head2 C<.name> + + const char *name; + +This field (a string) is required, and B<must> contain only ASCII +alphanumeric characters and be unique amongst all filters. + +=head2 C<.version> + + const char *version; + +Filters may optionally set a version string which is displayed in help...

...(* Append the key. *) diff --git a/src/guestfs.pod b/src/guestfs.pod index 75afa9d..366d6f5 100644 --- a/src/guestfs.pod +++ b/src/guestfs.pod @@ -2244,6 +2244,23 @@ allowed a malformed filesystem to take over the appliance. If you use sVirt to confine qemu, that would thwart some attacks. +=head2 Permissions of F<.ssh> and F<.ssh/authorized_keys> + +L<https://bugzilla.redhat.com/1260778> + +The tools L<virt-customize(1)>, L<virt-sysprep(1)> and +L<virt-builder(1)> have an I<--ssh-inject> option for injecting an SSH +key into virtual machine disk ima...

...6c 100644 --- a/plugins/python/nbdkit-python-plugin.pod +++ b/plugins/python/nbdkit-python-plugin.pod @@ -46,14 +46,15 @@ may want to include documentation and globals (eg. for storing global state). Any other top level statements are run when the script is loaded, just like ordinary Python. -=head2 Python 2 and Python 3 +=head2 Python versions -The Python plugin has to be compiled for either Python 2 or Python 3 -when building nbdkit. You can set the C<PYTHON> environment variable -to the desired interpreter, otherwise nbdkit will use the interpreter -called C<python> on the cu...

...k it +doesn't call the C<next> function then the corresponding method in the +plugin will never be called. + +=head1 CALLBACKS + +C<struct nbdkit_filter> has some static fields describing the filter +and optional callback functions which can be used to intercept plugin +methods. + +=head2 C<.name> + + const char *name; + +This field (a string) is required, and B<must> contain only ASCII +alphanumeric characters and be unique amongst all filters. + +=head2 C<.version> + + const char *version; + +Filters may optionally set a version string which is displayed in help...

...+ server/plugins.c | 72 +++++++++++++++++++++++++++++++++- 8 files changed, 275 insertions(+), 5 deletions(-) diff --git a/docs/nbdkit-filter.pod b/docs/nbdkit-filter.pod index dc9a262..ada49dd 100644 --- a/docs/nbdkit-filter.pod +++ b/docs/nbdkit-filter.pod @@ -350,6 +350,8 @@ calls. =head2 C<.can_zero> +=head2 C<.can_extents> + =head2 C<.can_fua> =head2 C<.can_multi_conn> @@ -365,6 +367,8 @@ calls. void *handle); int (*can_zero) (struct nbdkit_next_ops *next_ops, void *nxdata, void *handle); + int (*can_extents) (s...

This patch series lifts the previous restriction that virt-v2v would refuse to convert a guest to Glance that had more than one disk. The first patch is just better documentation for the Glance output mode. The second patch contains the change (best viewed with 'git diff -w' since it is mostly a whitespace change). virt-v2v -o glance will now create multiple disks called: - guestname

v2 was here: https://www.redhat.com/archives/libguestfs/2020-April/msg00075.html In v3: - Add [VAR=VALUE ...] to manual. - Various minor improvements to the manual. - Work (at least, in theory - not tested) with block devices or symlinks. I didn't document this because it's hard to ensure these files or block devices would be cleaned up, so here be dragons. - Remove O_NOCTTY. -

...error, C<.can_write> should call C<nbdkit_error> with an error message and return C<-1>. -This callback is not required. If omitted, then we return true iff a +This callback is not required. If omitted, then we return true if a C<.pwrite> callback has been defined. =head2 C<.can_flush> @@ -361,7 +361,7 @@ handle supports the flush-to-disk operation. If there is an error, C<.can_flush> should call C<nbdkit_error> with an error message and return C<-1>. -This callback is not required. If omitted, then we return true iff a +This callback is...