similar to: Help ! libvirt

Attaching win11.xml Please note that this used to work fine. It is failing now on libvirt- 9.7.0-1 On Thu, Sep 21, 2023 at 9:13?AM Peter Krempa <pkrempa at redhat.com> wrote: > On Thu, Sep 21, 2023 at 09:05:43 +0100, Bhasker C V wrote: > > Adding libvirt mailing list > > apologies for cross-posting > > libvirt version: 9.7.0-1 > > > > On Thu, Sep 21, 2023

On Thu, Sep 21, 2023 at 09:05:43 +0100, Bhasker C V wrote: > Adding libvirt mailing list > apologies for cross-posting > libvirt version: 9.7.0-1 > > On Thu, Sep 21, 2023 at 8:39?AM john doe <johndoe65534 at mail.com> wrote: > > > On 9/21/23 09:32, Bhasker C V wrote: > > > I am getting an error with libivrt when I create a VM > > > > > >

On Thu, Sep 21, 2023 at 10:50:07 +0100, Bhasker C V wrote: > Attaching win11.xml > Please note that this used to work fine. It is failing now on libvirt- > 9.7.0-1 > > On Thu, Sep 21, 2023 at 9:13?AM Peter Krempa <pkrempa at redhat.com> wrote: > > > On Thu, Sep 21, 2023 at 09:05:43 +0100, Bhasker C V wrote: > > > Adding libvirt mailing list > > >

Hi, I have tried that too and that did not help either (i.e adding the format type=gpt) The output you requested ``` $ sudo qemu-img info --backing-chain /var/virt/WINDOWS/WIN11 image: /var/virt/WINDOWS/WIN11 file format: qcow2 virtual size: 60 GiB (64424509440 bytes) disk size: 55.1 GiB cluster_size: 65536 backing file: WIN11-BASE (actual path: /var/virt/WINDOWS/WIN11-BASE) backing file

I finally fixed it. The issue seems to be with the tpm-tis/cpu backend (wonder why it shows up with a different error) For the sake of community, I am attaching the new xml file so that you can do forensics on what changed (I prettymuch did a virt-install --import --print-xml to redo the config keeping everything intact) I found another issue If I switch the suspend-to-disk

On Thu, Sep 21, 2023 at 09:05:43AM +0100, Bhasker C V wrote: > Adding libvirt mailing list > apologies for cross-posting > libvirt version: 9.7.0-1 > > On Thu, Sep 21, 2023 at 8:39?AM john doe <johndoe65534 at mail.com> wrote: > > > On 9/21/23 09:32, Bhasker C V wrote: > > > I am getting an error with libivrt when I create a VM > > > > > >

Le Thu, 3 Oct 2024 21:35:04 +0100 Rowland Penny via samba <samba at lists.samba.org> ?crivait: > > Yes, I mean Windows 11 or WIndows Server 2022 machines that are > > registered into the AD. A Win11 PC which isn't AD-connected (but in > > the same IP network) can connect just fine using the server IP > > address and credentials from one of the domain user

On Thu, Jul 13, 2023 at 11:47?AM Bo Kersey <bo at vircio.com> wrote: > The patch on Windows Server 2012 R2 that does the same thing as kb5028166 > is KB5028228 > > > ------------------------------ > > *From: *"Philippe LeCavalier" <support at plecavalier.com> > *To: *"Bo Kersey" <bo at vircio.com> > *Cc: *"samba" <samba

On Thu, 3 Oct 2024 22:04:11 +0200 Emmanuel Florac <eflorac at intellique.com> wrote: > Le Thu, 3 Oct 2024 16:20:38 +0100 > Rowland Penny via samba <samba at lists.samba.org> ?crivait: > > > > > > > "smbclient" on Linux connects to the share just fine using domain > > > user credentials. Only domain members can't... > > >

Hi fellow Members!I'm Systems administrator at a school using SAMBA 4 as AD DC. As you know, WIN11 is at the doorstep and my "old" Samba4 Server (4.9) doesn't serve Windows Servers (Server 2019) very well, e.g. the latest issue is that the domain administrator cannot access the GPO's or other informations from the Samba-LDAP (authentication failure ?). I think that it has

On 21/04/2023 15:11, E Kogler via samba wrote: > Hi fellow Members!I'm Systems administrator at a school using SAMBA 4 as AD DC. > As you know, WIN11 is at the doorstep and my "old" Samba4 Server (4.9) doesn't serve Windows Servers (Server 2019) very well, > e.g. the latest issue is that the domain administrator cannot access the GPO's or other informations from the

On Thursday, September 26th, 2024 at 07:17, Marco Gaiarin via samba <samba at lists.samba.org> wrote: > Mandi! June Chong | TechnologyWise via samba > In chel di` si favelave... > > > Would someone be able to advise us on how to handle 'Folder Redirection' > > for users that work remotely? > > > I'm currently using roaming profiles, with quota,

On Sun, 7 Jul 2024 00:55:20 +0100 Jonathan Hunter via samba <samba at lists.samba.org> wrote: > Hi, > > I recently noticed that two separate Windows 11 machines joined to my > domain are not letting me log in to them as a domain user. In the > Windows Security event log I can see 'Audit Failure' - 'An account > failed to log on'. Details shown are:

Mandi! June Chong | TechnologyWise via samba In chel di` si favelave... > Would someone be able to advise us on how to handle 'Folder Redirection' > for users that work remotely? I'm currently using roaming profiles, with quota, and with a careful exclusions from profiles by folder redirection and 'HKCU\SOFTWARE\Microsoft\Windows

Hello, I'm trying to connect a Debian 11.x server (running Samba 4.13.13, old version...) to an AD which is controlled by a Windows Server 2022 (21H2) controller. The server joined the domain fine, it's listed among the domain members normally, and user authentication works ("id <some domain user>" works), however I can connect to the server just fine in two cases : *

Hi, I have this setup kernel: x86_64 version 4.2.0 operating system (rootfs binutils etc.,) : i386 (ELF-32-bit) qemu-system : version 2.4.0 qemu-system-x86_64 (i386 binary) libvirt: 1.2.19 (i386 ) When I run the qemu-system-x86_64 binary with --enable-kvm, the guest machine is working properly as hvm. So QEMU can run x86_64 OS as hvm when I install using virt-install virt-install --name

Op 20-01-2025 om 11:52 schreef Rowland Penny via samba: > On Sun, 19 Jan 2025 17:51:54 +0100 > Peter Milesson via samba <samba at lists.samba.org> wrote: > >> >> >> On 19.01.2025 17:30, Sonic via samba wrote: >>> When I first did a Samba upgrade to 4.19.3 on Debian Bookworm back >>> in December of 2023 Chrony was working just fine for a natural

Hi everyone, I'm posting here because I'm facing a kerberos authentication problem after the 2:4.13.17~dfsg-0ubuntu1.20.04.4 samba upgrade. The clients, win10, win11, win2016 cannot login to AD anymore. On server logs the authentication succeeded but in the Event Viewer on the client I have this error: Security-Kerberos The Kerberos client received a KRB_AP_ERR_MODIFIED error from the

Source: xen Severity: normal User: debian-lts at lists.debian.org Usertags: upstream-trixie X-Debbugs-Cc: debian-lts at lists.debian.org Dear xen maintainers, Testing (trixie) currently ships xen 4.17, which, according to the upstream support matrix [x], will get security support until 2025-12-12. The latest upstream release (4.19) will get security support until 2027-07-29. I believe it would

On Sun, 19 Jan 2025 17:51:54 +0100 Peter Milesson via samba <samba at lists.samba.org> wrote: > > > > On 19.01.2025 17:30, Sonic via samba wrote: > > When I first did a Samba upgrade to 4.19.3 on Debian Bookworm back > > in December of 2023 Chrony was working just fine for a natural > > domain time sync to the DC - no special config or GPO necessary. So >