search for: not_implemented

-- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones virt-top is 'top' for virtual machines. Tiny program with many powerful monitoring features, net stats, disk stats, logging, etc. http://et.redhat.com/~rjones/virt-top -------------- next part -------------- >From 2b26c7f721fc8ed2e6f64963289981ac286c02aa Mon Sep 17 00:00:00 2001 From: Richard W.M. Jones

This adds most of the hivex APIs directly to the libguestfs API, so that you can read and write Windows Registry hive files from libguestfs without needing to download and upload hive files from the guest. This is analogous to how Augeas APIs are exposed already (guestfs_aug_*) Also, inspection is now done using the new APIs, which fixes the following bug:

From: "Richard W.M. Jones" <rjones at redhat.com> This commit models libvirt authentication events through the API, adding one new event (GUESTFS_EVENT_LIBVIRT_AUTH) and several new APIs: guestfs_set_libvirt_supported_credentials guestfs_get_libvirt_requested_credentials guestfs_get_libvirt_requested_credential_prompt guestfs_get_libvirt_requested_credential_challenge

If libmagic isn't installed then the guestfs_file_architecture API doesn't work. This means that inspection will always return <arch>unknown</arch> for every guest. This subtly breaks a few features. In particular it was reported that the virt-builder/virt-customize --install option did not work because the "unknown" architecture of the guest was not compatible

Hello Community, im joining several macintosh workstations to my samba AD. First of all, it works pretty well and im able to authenticate/login my AD user on a mac. Server: Ubuntu 16.04 SAMBA: 4.7.7 First: Everytime when a mac starts up, some log entries are shown in log.samba. Looks like (Its not a flood, about 4 messages for each client): [2018/04/19 14:35:04.645001, 0]

...in Street, Fifth Floor, - * Boston, MA 02110-1301 USA - */ - -#ifdef HAVE_CONFIG_H -#include "config.h" -#endif - -#include "swfdec_js.h" -#include "swfdec_debug.h" -#include "swfdec_movie.h" -#include "swfdec_player_internal.h" - -static JSBool -not_implemented (JSContext *cx, JSObject *obj, uintN argc, jsval *argv, jsval *rval) -{ - SWFDEC_WARNING ("FIXME: implement this sound function"); - return JS_TRUE; -} - -static JSFunctionSpec sound_methods[] = { - { "attachSound", not_implemented, 1, 0, 0 }, - { "getPan",...

...mmand) to do its work. When working on RuntimeDyldELF, I encountered some cases of Elf information I need which wasn't exposed through the ObjectFile interface. Adding additional getters to that interface requires to implement them in COFF and MachO object files as well (perhaps returning "not_implemented" error codes). So, I'm wondering whether the right approach here is to keep everything behind the ObjectFile interface, or just expose some ELF specific structures via a header file and use those? After all, this is in code that is specifically meant to handle ELF files, so it makes some...

...: >         case DNS_QTYPE_SRV: >         case DNS_QTYPE_TXT: >                 break; >         default: >                 DEBUG(0, ("Can't handle updates of type %u yet\n", >                           update->rr_type)); >                 return DNS_ERR(NOT_IMPLEMENTED); >         } > > Google searching DNS type 255 (RFC 1035) states it's "A > request for all > records". You could run a trace and see what application is > requesting > this record type. > > As far as the cpu usage. I do not know. > > -- >...

...ing, 1 is failing. Both use the Isolinux bootloader, also used on many Linux distribution cdroms / DVDs. However the working one has version 2.xx, failing one has version 3.05 Boot from cdrom, then select option 1, and you should see the following: VMware Workstation unrecoverable error: (vcpu-0) NOT_IMPLEMENTED C:/ob/bora-11888/bora/devices/misc/flashram.c:502 A log file is available in "C:\Documents and Settings\me\Mijn documenten\My Virtual Machines\MS-DOS 12\vmware.log". A core file is available in "C:\Documents and Settings\Bernd\Application Data\VMware\vmware-vmx-9704.dmp". Please...

From: "Richard W.M. Jones" <rjones at redhat.com> Previously there was no programmatic way to tell if inspection APIs were unavailable because they are not compiled in (because hivex isn't around). This contrasts with daemon APIs where the availability is covered by the guestfs_available API. Change the inspection APIs so that when they are not available, the last errno is

Hello! I’m seeing the following log entries in /var/log/syslog on my FSMO (Ubuntu 14.04.3 LTS / Samba 4.3.4): Feb 19 09:56:48 dc00 samba[4552]: [2016/02/19 09:56:48.527183, 0] ../source4/dns_server/dns_update.c:426(handle_one_update) Feb 19 09:56:48 dc00 samba[4552]: Can't handle updates of type 255 yet Feb 19 09:56:48 dc00 samba[4552]: [2016/02/19 09:56:48.860255, 0]

..._SRV: >> case DNS_QTYPE_TXT: >> break; >> default: >> DEBUG(0, ("Can't handle updates of type %u yet\n", >> update->rr_type)); >> return DNS_ERR(NOT_IMPLEMENTED); >> } >> >> Google searching DNS type 255 (RFC 1035) states it's "A >> request for all >> records". You could run a trace and see what application is >> requesting >> this record type. >> >> As far as the cpu usage. I do...

A disk of type 'volume' is stored as <source pool='pool_name' volume='volume_name'/> and its real location is inside the 'volume_name', as 'pool_name': in this case, query libvirt for the actual path of the specified volume in the specified pool. Adjust the code so that: - for_each_disk gets the virConnectPtr, needed to do operations with libvirt

This preliminary patch series adds a libvirt backend to libguestfs. It's for review only because although it launches the guest OK, there are some missing features that need to be implemented. The meat of the patch is in part 4/4. To save you the trouble of interpreting libxml2 fragments, an example of the generated XML and the corresponding qemu command line are attached below. Note the

This is, I guess, version 3 of this patch series which adds disk labels and hotplugging (only hot-add implemented so far). The good news is .. it works! Rich.

https://bugzilla.redhat.com/show_bug.cgi?id=912499 (especially comments 7 & 10) This patch set is the final fix so that we can access disks in use by other guests when SELinux and sVirt are enabled. Previously such disks were inaccessible because sVirt labels the disks with a random SELinux label to prevent other instances of qemu from being able to read them. So naturally the libguestfs

A disk of type 'volume' is stored as <source pool='pool_name' volume='volume_name'/> and its real location is inside the 'volume_name', as 'pool_name': in this case, query libvirt for the actual path of the specified volume in the specified pool. Adjust the code so that: - for_each_disk gets the virConnectPtr, needed to do operations with libvirt

This rounds off hotplugging support by allowing you to add and remove drives at any stage (before and after launch). Rich.

Move the checks for empty xmlXPathObjectPtr, and for extracting the result string out of it, to a new helper functions. This is just code motion, there should be no behaviour changes. --- src/libvirt-domain.c | 122 +++++++++++++++++++++------------------------------ 1 file changed, 50 insertions(+), 72 deletions(-) diff --git a/src/libvirt-domain.c b/src/libvirt-domain.c index 4d4142d..baab307

From: Nikolay Ivanets <stenavin@gmail.com> Nowadays there are hard drives and operating systems which support "4K native" sector size. In this mode physical and logical block size exposed to the operating system is equal to 4096 bytes. GPT partition table (as a known example) being created in this mode will place GPT header at LBA1 which is 4096 bytes. libguetfs is unable to