similar to: question about upgrade qemu and libvirtd

On Feb 14, 2019, at 18:23, rong zhao <zhaorbox at gmail.com> wrote: > > Hi Team, > I am not sure if I should put my question here, I have googled long > time, no explicit information found. > > Background: > We need to support KVM encryption and decided to use LUKS. > > Refer to:https://libvirt.org/formatsecret.html#VolumeUsageType > >

A few days ago I demoted my first DC (a v4.2.14, I think) and thought the demote had gone well. Now, when I run "samba-tool dnsupdate --verbose" I can see references to the first DC that remain. Unfortunately, that DC no longer exists so I simply cannot demote it again. Following the instructions on the "Demote a Samba AD DC" page "Verifying The Demotion" section, I

I am seeing domain and forest levels for 2012R2 mentioned in the wiki pages. Has anyone in a production environment "raised" their domain and forest levels to 2012R2 yet? Am I correct that this would only apply to v4.5.0 or higher? -- _______________________________ Bob Wooden of Donelson Trophy

Rowland, I have seen you state this before that "server services" line within a smb.conf file is not necessary on a DC. I have to ask, and it may have been asked before but, I recently install from source the v4.5.0 and during provisioning samba created that "line" within the smb.conf file. I understand what and why your saying this but, if the line is not needed then why

On 2016-11-05 07:46, Mike Lykov via samba wrote: > 05.11.2016 16:09, Bob of Donelson Trophy via samba пишет: > >> Once again, reading here and there and I am confused. >> >> I thought the W clients (both W7 and W10) reverse dns PTR records where >> added by the ADDC automatically. >> >> This mornings testing (nslookup of client IP addresses) is not

On Sat, 22 Apr 2017 08:47:53 -0500 Bob of Donelson Trophy via samba <samba at lists.samba.org> wrote: > On 2017-04-22 07:36, Bob of Donelson Trophy via samba wrote: > > > I have updated from Samba 4.5.0 to 4.6.2 on my second DC and all > > appears good, so far. > > > > On the "https://wiki.samba.org/index.php/Updating_Samba" [1 [1]] > > page

Hello developers, Your release notes from libvirt(https://libvirt.org/news.html) are really helpful to our users and QAs. How about giving commit ID of each item in release notes, so that our user can gather more info from release notes. For example,in v4.5.0 release note, add commit ID on each item: capabilities: Provide info about host IOMMU support Capabilities XML now provide information about

On 11/3/2016 12:07 PM, Marc Muehlfeld via samba wrote: > Hi Bob, > > Am 03.11.2016 um 16:43 schrieb Bob of Donelson Trophy via samba: >> I have seen you state this before that "server services" line within a >> smb.conf file is not necessary on a DC. >> >> I have to ask, and it may have been asked before but, I recently install >> from source the

On 2016-11-05 08:21, Rowland Penny via samba wrote: > On Sat, 05 Nov 2016 08:07:18 -0500 > Bob of Donelson Trophy via samba <samba at lists.samba.org> wrote: > > On 2016-11-05 07:46, Mike Lykov via samba wrote: > > 05.11.2016 16:09, Bob of Donelson Trophy via samba пишет: > > Once again, reading here and there and I am confused. > > I thought the W clients

On Fri, 04 Nov 2016 06:56:32 +1300 Andrew Bartlett via samba <samba at lists.samba.org> wrote: > On Thu, 2016-11-03 at 13:17 -0400, lingpanda101 via samba wrote: > > On 11/3/2016 12:07 PM, Marc Muehlfeld via samba wrote: > > > > > > Hi Bob, > > > > > > Am 03.11.2016 um 16:43 schrieb Bob of Donelson Trophy via samba: > > > > >

Hi! I'm new to libvirt and face problems connecting to an iSCSI target. What I intend to do is to connect libvirt (I tried virt-manager and virsh) to an iSCSI target and then boot from the LUNs which contain the VMs. I followed the documentation¹ but got stuck at section 12.1.5.4.3. 1) virsh pool-define-as \ --name foo \ --type iscsi

On Thu, 3 Nov 2016 14:15:57 -0400 lingpanda101 via samba <samba at lists.samba.org> wrote: > On 11/3/2016 2:03 PM, Rowland Penny via samba wrote: > > On Fri, 04 Nov 2016 06:56:32 +1300 > > Andrew Bartlett via samba <samba at lists.samba.org> wrote: > > > >> On Thu, 2016-11-03 at 13:17 -0400, lingpanda101 via samba wrote: > >>> On 11/3/2016

Once again, reading here and there and I am confused. I thought the W clients (both W7 and W10) reverse dns PTR records where added by the ADDC automatically. This mornings testing (nslookup of client IP addresses) is not finding clients via their IP addresses. (Forward lookups via hostname work fine.) Do we (users of samba4) need to add each W client to our dns servers? (Grated this would

Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=2168506 This small set covers the new /dev/mapper/VG-LV "--key" ID format in the libguestfs LUKS-on-LVM inspection test. Thanks, Laszlo Laszlo Ersek (3): update common submodule LUKS-on-LVM inspection test: rename VGs and LVs LUKS-on-LVM inspection test: test /dev/mapper/VG-LV translation common

This combined patch series enables to decrypt LUKS devices on inspection by allowing the UUID of the LUKS device with the --key syntax. I opted for reusing the option instead of adding another one, as I think that device names and UUIDs are different enough that can be properly distinguished. A test for this (patch #4) can be applied only when the patches for common are applied, and the

Requires this series: https://www.redhat.com/archives/libguestfs/2019-November/msg00036.html

Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=2168506 This small set covers the new /dev/mapper/VG-LV "--key" ID format in the LUKS-on-LVM virt-inspector test. Thanks, Laszlo Laszlo Ersek (3): update common submodule inspector: rename VGs and LVs in LUKS-on-LVM test inspector: test /dev/mapper/VG-LV translation in LUKS-on-LVM test common

I'm sorry, but grep -i crypt /var/log/anaconda/anaconda.program.log returns nothing. But I have got an entry in /etc/crypttab. I only found this with grep -i luks /var/log/anaconda/anaconda.*: /var/log/anaconda/anaconda.storage.log:20:47:55,959 DEBUG blivet: LUKS.__init__: /var/log/anaconda/anaconda.storage.log:20:49:25,009 DEBUG storage.ui: LUKS.__init__:

The following patch attempts to implement sparsification of LUKS-encrypted partitions. It uses lsblk to pair the underlying LUKS block device with its mapped name. Also, --allow-discards was added by default to luks_open(). There are several potential issues that I can think of: 1) If and entire device is encrypted (not just one of more partitions), the lsblk trick might not work. 2) The

These commits, along with the associated changes to common: https://www.redhat.com/archives/libguestfs/2020-March/msg00286.html support the transparent decryption and inspection of Windows guests encrypted with BitLocker encryption. To do the BitLocker decryption requires cryptsetup 2.3.0 (although cryptsetup 2.3 is not required for existing LUKS use). It also requires a new-ish Linux kernel, I