search for: _legacy

...020/02/13 01:18:42.759997, 5] ../../source3/passdb/passdb.c:2396(get_trust_pw_clear2) get_trust_pw_clear2: could not fetch clear text trust account password for domain OFFICE [2020/02/13 01:18:42.760013, 5] ../../source3/passdb/machine_account_secrets.c:343(secrets_fetch_trust_account_password _legacy) secrets_fetch failed! [2020/02/13 01:18:42.760024, 5] ../../source3/passdb/passdb.c:2475(get_trust_pw_hash2) get_trust_pw_hash: could not fetch trust account password for domain OFFICE [2020/02/13 01:18:42.760896, 3] ../../lib/ldb-samba/ldb_wrap.c:332(ldb_wrap_connect) ldb_wrap open of sec...

...detecting old kernels will just use 64, > > this means we do want a flag to get the old way. > > > > OTOH if you won't think it's useful, let me know. > this header will be synced into QEMU's tree so that we could use this define there, > isn't it? IMHO then _LEGACY is more exact description of macro. > > As for 0 return value, -1 is just fine for detecting old kernels (i.e. try and see if it works), so 0 looks unnecessary but it doesn't in any way hurt either. > For me limit or -1 is enough to try fix userspace. OK. Do you want to try now befor...

...detecting old kernels will just use 64, > > this means we do want a flag to get the old way. > > > > OTOH if you won't think it's useful, let me know. > this header will be synced into QEMU's tree so that we could use this define there, > isn't it? IMHO then _LEGACY is more exact description of macro. > > As for 0 return value, -1 is just fine for detecting old kernels (i.e. try and see if it works), so 0 looks unnecessary but it doesn't in any way hurt either. > For me limit or -1 is enough to try fix userspace. OK. Do you want to try now befor...

...JS ERROR: > Exception in callback for signal: reset: Gio.DBusError: > GDBus.Error:org.freedesktop.DBus.Error.AccessDenied: No session available > LoginDialog<._resetGreeterProxy at resource:///org/gnome/shell/gdm/loginDialog.js:837:29 > wrapper at resource:///org/gnome/gjs/modules/_legacy.js:82:22... Did the upgrade break something? Possibly. Any and all hints/ideas/etc. greatly welcomed. PEV -- Paul E Virgo Sr. System Administrator Code 610.2 SESDA III - DAAC/DISC Goddard Space Flight Ctr/NASA Greenbelt, MD Greenbelt, MD 20771 (301) 614-5751

"Michael S. Tsirkin" <mst at redhat.com> writes: > virtio 1.0 config space is in LE format for all > devices, use modern wrappers when accessed through > the 1.0 BAR. Hmm, I'm not so sure about these patches. It's easy to miss the existence of the _modern variants, and they're 90% the same as the legacy variants. But as long as it's fixed... Thanks,

"Michael S. Tsirkin" <mst at redhat.com> writes: > virtio 1.0 config space is in LE format for all > devices, use modern wrappers when accessed through > the 1.0 BAR. Hmm, I'm not so sure about these patches. It's easy to miss the existence of the _modern variants, and they're 90% the same as the legacy variants. But as long as it's fixed... Thanks,

On Wed, Jun 24, 2015 at 04:07:27PM +0200, Igor Mammedov wrote: > On Wed, 24 Jun 2015 15:49:27 +0200 > "Michael S. Tsirkin" <mst at redhat.com> wrote: > > > Userspace currently simply tries to give vhost as many regions > > as it happens to have, but you only have the mem table > > when you have initialized a large part of VM, so graceful > >

On Wed, Jun 24, 2015 at 04:07:27PM +0200, Igor Mammedov wrote: > On Wed, 24 Jun 2015 15:49:27 +0200 > "Michael S. Tsirkin" <mst at redhat.com> wrote: > > > Userspace currently simply tries to give vhost as many regions > > as it happens to have, but you only have the mem table > > when you have initialized a large part of VM, so graceful > >

...ption was that userspace detecting old kernels will just use 64, > this means we do want a flag to get the old way. > > OTOH if you won't think it's useful, let me know. this header will be synced into QEMU's tree so that we could use this define there, isn't it? IMHO then _LEGACY is more exact description of macro. As for 0 return value, -1 is just fine for detecting old kernels (i.e. try and see if it works), so 0 looks unnecessary but it doesn't in any way hurt either. For me limit or -1 is enough to try fix userspace. > > > > + > > > /* VHOST...

...020/02/14 16:59:37.564842, 5] ../../source3/passdb/passdb.c:2396(get_trust_pw_clear2) get_trust_pw_clear2: could not fetch clear text trust account password for domain OFFICE [2020/02/14 16:59:37.564857, 5] ../../source3/passdb/machine_account_secrets.c:343(secrets_fetch_trust_account_password _legacy) secrets_fetch failed! [2020/02/14 16:59:37.564866, 5] ../../source3/passdb/passdb.c:2475(get_trust_pw_hash2) get_trust_pw_hash: could not fetch trust account password for domain OFFICE [2020/02/14 16:59:37.566881, 3] ../../lib/ldb-samba/ldb_wrap.c:332(ldb_wrap_connect) ldb_wrap open of sec...