search for: msg00086

...definition will not be present. > > > > Just because it may not be obvious that the thread forked (probably > email client for original poster)... Anyway, see what ended up being a > longer explanation here: > > https://www.redhat.com/archives/libvirt-users/2018-February/msg00086.html > > Where the short story is I don't think you need to hotplug a secret > object as that should already be there. One cannot hotplug a cdrom, so > the definition and the secret used must already exist. It's a strange No, no, no. That is plain wrong. The secret object is p...

On Tue, Feb 27, 2018 at 09:53:00 +0100, Michal Privoznik wrote: > On 02/27/2018 03:06 AM, Star Guo wrote: > > Hello Everyone, > > > > > > > > My pc run in CentOS 7.4 and install libvirt-4.0.0 + Qemu-kvm 2.9.0 + Ceph > > 10.2.10 ALL-in-One. > > > > > > > > I use python-sdk with libvirt and run [self.domain.updateDeviceFlags(xml,

We're exploring the use of "plus addressing" in our MTA (Exim), which delivers "user+topic at domain.com" to a user's "topic" folder. However, the case-sensitive nature of our ext3 filesystem means that a message destined to "topic" won't deliver to a user's "Topic" folder. For example, if a user creates a "Topic"

Has anyone recently started seeing LibClamAV Warning: Cannot prepare for JIT, because it has already been converted to interpreter ? I can't find anything googling for that. mark

...t; referenced by the storage source definition will not be present. > Just because it may not be obvious that the thread forked (probably email client for original poster)... Anyway, see what ended up being a longer explanation here: https://www.redhat.com/archives/libvirt-users/2018-February/msg00086.html Where the short story is I don't think you need to hotplug a secret object as that should already be there. One cannot hotplug a cdrom, so the definition and the secret used must already exist. It's a strange code path and while looking I didn't find a mechanism that would allow a...

Hi All, Will some one explain how is this tls libvirt server is implemented. For my testing purpose I need to implement the similar TLS server in Java or Python and this server is capable to receive all libvirt calls like getCapabilities, hostname etc and return response as I'm configured. Basically I need to simulate the libvirt TLS server. I tried creating many TLS server but none of the my

...present. >>> >> >> Just because it may not be obvious that the thread forked (probably >> email client for original poster)... Anyway, see what ended up being a >> longer explanation here: >> >> https://www.redhat.com/archives/libvirt-users/2018-February/msg00086.html >> >> Where the short story is I don't think you need to hotplug a secret >> object as that should already be there. One cannot hotplug a cdrom, so >> the definition and the secret used must already exist. It's a strange > > No, no, no. That is plain wron...

Regardless of the filesystem (i''ve used reiserfs, xfs, ext3), whenever I mount a fresh DRBD partition I get some nasty kernel messages. This is under Debian Sarge, Xen kernel 2.6.11.12-xen0 (dom0) using DRBD v0.7.11 (pulled from Debian "testing"). This is what I did to create the partition. On both nodes I created a new LVM storage device and started DRBD: # lvcreate

Hi all! I am having troubles with booting Xen with grub2 in UEFI mode. Does Xen support this configuration? Are there any specific settings? _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users

Hi all, I''m trying to get a pci card working on a guest os (ast01) on dum0 I hided the pci card w/: # modprobe pciback hide=''(0b:08.0)'' then added this line to the guest os config file (/etc/xen/ast01) pci = [ "0000:08:0e.0" ] Whenever I try to start it fails w/: # xm create ast01 Using config file "/etc/xen/ast01". Error: function takes exactly 4

Patch 1 was previously posted here: https://www.redhat.com/archives/libguestfs/2020-June/msg00086.html to handle this bug: https://bugzilla.redhat.com/show_bug.cgi?id=1848862 I was able to observe this bug and for me at least disabling readahead seems to cure it. Patches 2 and 3 are simplifications, removing a now-undocumented feature of virt-v2v-copy-to-local and thus simplifying greatly the...