search for: l302

...n Battery Charge/Runtime reaches 0. > Is this correct? Or should there be an earlier transition and shutdown triggered by OB LB? The driver should recognize one of several standard shutdown notifications: https://github.com/networkupstools/nut/blob/v2.7.2-signed/drivers/openups-hid.c#L300-L302 However, I don't know which of these is actually implemented in the firmware. If you can afford some downtime, you can capture a log as the battery discharges - let us know if you want to try that. To synthesize the OB+LB state, you can use the "ignorelb" flag with override.battery....

...0. > > Is this correct? Or should there be an earlier transition and shutdown > triggered by OB LB? > > The driver should recognize one of several standard shutdown notifications: > > https://github.com/networkupstools/nut/blob/v2.7. > 2-signed/drivers/openups-hid.c#L300-L302 > > However, I don't know which of these is actually implemented in the > firmware. If you can afford some downtime, you can capture a log as the > battery discharges - let us know if you want to try that. > > To synthesize the OB+LB state, you can use the "ignorelb"...

Hi Michael On Tue Nov 10, 2020 at 1:29 AM GMT, Michael Kruse wrote: > Am Mo., 2. Nov. 2020 um 14:01 Uhr schrieb David Blaikie > <dblaikie at gmail.com>: > > Hmm, not sure why the whole file was added only when MSVC support was added - if it is a "static library object file selection" issue. Wouldn't that have turned up on other platforms before that moment? >

Hi Charles, Tim, Ah, thanks for bit about the dependencies. Would have thought them to be version specific. Tried with the client and server debs but it seems too many dependency differences between wheezy and jessie. I also tried upgrading from wheezy to jessie wholesale to see if that worked and it did solve nut but in the process broke something else that's more critical so I'll give

...83b1#file-libvirtd-log-L226-L253 > [3] > https://gist.github.com/filmaj/207ab3c09f5b881d83b1#file-libvirtd-log-L257-L266 > [4] > https://gist.github.com/filmaj/207ab3c09f5b881d83b1#file-libvirtd-log-L296 > [5] > https://gist.github.com/filmaj/207ab3c09f5b881d83b1#file-libvirtd-log-L302 > [6] > https://gist.github.com/filmaj/207ab3c09f5b881d83b1#file-libvirtd-log-L685 > [7] > https://gist.github.com/filmaj/207ab3c09f5b881d83b1#file-libvirtd-log-L752-L799 > [8] > https://gist.github.com/filmaj/207ab3c09f5b881d83b1#file-libvirtd-log-L1075 > [9] > https://gist...

...ub.com/filmaj/207ab3c09f5b881d83b1#file-libvirtd-log-L226-L253 [3] https://gist.github.com/filmaj/207ab3c09f5b881d83b1#file-libvirtd-log-L257-L266 [4] https://gist.github.com/filmaj/207ab3c09f5b881d83b1#file-libvirtd-log-L296 [5] https://gist.github.com/filmaj/207ab3c09f5b881d83b1#file-libvirtd-log-L302 [6] https://gist.github.com/filmaj/207ab3c09f5b881d83b1#file-libvirtd-log-L685 [7] https://gist.github.com/filmaj/207ab3c09f5b881d83b1#file-libvirtd-log-L752-L799 [8] https://gist.github.com/filmaj/207ab3c09f5b881d83b1#file-libvirtd-log-L1075 [9] https://gist.github.com/filmaj/207ab3c09f5b881d83b1#...

Further followups! We are correlating DEBUG-level output from libvirt with the libvirt 1.2.2 code to try to figure out what libvirt is doing under the hood. Even though we have the log level set to 1 (info) in our libvirtd.conf, we are not seeing the VIR_DEBUG() [1] statements being printed out. There are tons of other presumably-debug lines of output showing up in our log. We are sort of

On Thu, Mar 09, 2023 at 03:47:10PM +0200, Andrey Drobyshev wrote: > On 3/8/23 22:52, Richard W.M. Jones wrote: > > On Wed, Mar 08, 2023 at 08:05:35PM +0200, Andrey Drobyshev wrote: > >> During conversion we copy the necessary drivers to the directory > >> "%systemroot%\Drivers\Virtio", adding it to the DevicePath registry > >> value. As documented in