similar to: HELP!! - ActiveRecord derivates in AWS :expects method

Hi, I have a strange problem while using WebService API which expects an ActiveRecord derivate. This is the code of the API ... ------ class HarvesterApi < ActionWebService::API::Base api_method :send_measurand, :expects => [{:measurand => Measurand}, {:eaiSystemName => :string}] end ------ ... and this of my Model ------ class Measurand < ActiveRecord::Base

Does genid exist in oVirt ? If yes, is it already preserved or should it be a new patch ? On Thu, Jul 5, 2018 at 3:44 PM Richard W.M. Jones <rjones@redhat.com> wrote: > virt-v2v moves guests, it doesn't clone them. Therefore we should try > to preserve the VM Generation ID (genid) as much as possible. > > This has the ability to read the genid from VMware VMX files and

virt-v2v moves guests, it doesn't clone them. Therefore we should try to preserve the VM Generation ID (genid) as much as possible. This has the ability to read the genid from VMware VMX files and libvirt XML (but note RHBZ#1598348). It can also write the genid to libvirt (‘-o libvirt’, ‘-o local’) and QEMU (‘-o qemu’). We are missing support currently for all OVF-based formats (hence ‘-i

These patch update Windows generation ID support on ACPI. First patch mainly update to new specifications while second one introduce again the device in ACPI table. Frediano Ziglio (2): genid: Update Windows generation ID genid: Introduce again Windows generation ID device docs/misc/xenstore-paths.markdown | 6 ++++ tools/firmware/hvmloader/acpi/build.c | 49

On 5 Jul 2018, at 16:15, Richard W.M. Jones <rjones@redhat.com> wrote: On Thu, Jul 05, 2018 at 03:57:43PM +0200, Fabien Dupont wrote: Does genid exist in oVirt ? If yes, is it already preserved or should it be a new patch ? This patch does not preserve it for any RHV output mode: We are missing support currently for all OVF-based formats (hence ‘-i ova’, and all oVirt/RHV output

On Fri, Nov 23, 2018 at 12:39:44PM +0100, Martin Kletzander wrote: > There's a standardized libosinfo namespace for libvirt domain metadata. For now > it supports the id of the OS only. However that is still a very helpful feature > that is already supported in gnome-boxes and virt-manager (at least). > > The discussion happened here: > >

There's a standardized libosinfo namespace for libvirt domain metadata. For now it supports the id of the OS only. However that is still a very helpful feature that is already supported in gnome-boxes and virt-manager (at least). The discussion happened here: https://www.redhat.com/archives/libosinfo/2018-September/msg00003.html So let's add the support to local and libvirt outputs.

There's a standardized libosinfo namespace for libvirt domain metadata. For now it supports the id of the OS only. However that is still a very helpful feature that is already supported in gnome-boxes and virt-manager (at least). The discussion happened here: https://www.redhat.com/archives/libosinfo/2018-September/msg00003.html So let's add the support to local and libvirt outputs.

Hi, after one month with gmirror and gjournal running on a 7.0-RELEASE #p2 amd64 (built from latest CVS source), the box hung a couple of times when on high disk load. Finally, while building some port it won't boot for no reason obvious to me. This is what I get with kernel.geom.mirror.debug=2: ata2-master: pio=PIO4 wdma=WDMA2 udma=UDMA133 cable=40 wire ad4: 476940MB <SAMSUNG HD501LJ

Hi! The Netfilter project proudly presents: libnftnl 1.1.3 libnftnl is a userspace library providing a low-level netlink programming interface (API) to the in-kernel nf_tables subsystem. The library libnftnl has been previously known as libnftables. This library is currently used by nftables. See ChangeLog that comes attached to this email for more details. You can download it from:

Add a new output mode to virt-v2v: similar to -o local, the written metadata is a JSON file with the majority of the data that virt-v2v knowns about (or collects) during the conversion. This is meant to be used only when no existing output mode is usable, and a guest needs to be converted to run on KVM anyway. The user of this mode is supposed to use all the data in the JSON, as they contain

Add a new output mode to virt-v2v: similar to -o local, the written metadata is a JSON file with the majority of the data that virt-v2v knowns about (or collects) during the conversion. This is meant to be used only when no existing output mode is usable, and a guest needs to be converted to run on KVM anyway. The user of this mode is supposed to use all the data in the JSON, as they contain

I have a FreeBSD 6.2-based server running a 1.2TB graid3 volume, which consists of 5x 320gb SATA hard drives. I've been getting errors in /var/log/messages from the graid3 volume, which I suspect means an underlying fault with one of the disks, but is there any way to decipher which one of these drives is throwing errors? I've checked smartctl -a /dev/adXX but nothing shows up there..

Hi there, Taking my first steps in Prototype and reading this very helpful book by Christophe Porteneuve. There''s an interesting tutorial (Chpt. 7) on making a tree to organize staff members. The problem is that I can''t make it working in IE. In Firefox it works just great. Did anybody fiddle with it? Maybe somebody has already figured it out. IE says

Hello, For those who run tinc on Debian or Debian-based distributions like Ubuntu and Knoppix, be advised that the following security issue affects tinc as well: http://www.debian.org/security/2008/dsa-1571 In short, if you generated public/private keypairs for tinc between 2006 and May 7th of 2008 on a machine running Debian or a derivative, they may have been generated without a properly

Hello, For those who run tinc on Debian or Debian-based distributions like Ubuntu and Knoppix, be advised that the following security issue affects tinc as well: http://www.debian.org/security/2008/dsa-1571 In short, if you generated public/private keypairs for tinc between 2006 and May 7th of 2008 on a machine running Debian or a derivative, they may have been generated without a properly

QEMU for x86 supports two machine types, "pc" (emulating the ancient Intel i440FX chipset originally used by the Pentium Pro), and "q35" (https://wiki.qemu.org/Features/Q35). Currently virt-v2v does not set any machine type, so libvirt or the target hypervisor will choose some default, probably i440fx. The latest advice from the QEMU and libvirt communities is not to rely on

Hello list, Last night one disk of my desktop machine dead causing a hard lock of the computer. It was a component of a mirror volume so it wasn't as serious as it initially looked. Unfortunately, the metadata structure of my data partition (a geom raid3 array with tree components ) seems to be corrupted by this hard lock, the following message is scrolled constantly on the screen:

I'm pleased to announce libguestfs 1.40, a library and a set of tools for accessing and modifying virtual machine disk images. This release represents about a year of work by many contributors. I'd like to call out in particular substantial contributions from: Pino Toscano, Tomáš Golembiovský, Nir Soffer and Nikolay Ivanets. See the release notes below for full details. You can get

A colleague found some VMX files which omit the deviceType field. This allows -i vmx mode to parse them. Rich.