On Mon, Aug 18, 2025 at 10:53:09AM -0500, Praveen Paladugu wrote:
> Daniel,
>
> The log files are actually created under /var/log/libvirt/ch/
> sub-directory. Seems like
> I made a typo in my previous email.
>
> /var/log/libvirt/ch/ch_.log is the logfile name.
Ok, adding the 'ch_' prefix to the
Daniel,
The log files are actually created under /var/log/libvirt/ch/
sub-directory. Seems like
I made a typo in my previous email.
/var/log/libvirt/ch/ch_.log is the logfile name.
Praveen
On Mon, Aug 18, 2025 at 10:02 AM Daniel P. Berrangé
wrote:
> On Mon, Aug 18, 2025 at 09:58:32AM -0500
Hey Michal,
Thanks for the follow up. I noticed the new patchset. The new patchset
builds on top of the one I sent.
My patchset enables support for capturing logs from ch domains to
the standard libvirt path at /var/log/libvirt/ch_.log.
The new patchset enables verbosity knobs on top of my patchs
On Mon, Aug 18, 2025 at 09:58:32AM -0500, Praveen Paladugu wrote:
> Hey Michal,
>
> Thanks for the follow up. I noticed the new patchset. The new patchset
> builds on top of the one I sent.
>
> My patchset enables support for capturing logs from ch domains to
> the standard libvirt path at /var/l
On 12/19/24 18:07, Praveen K Paladugu wrote:
> LogContext management is now moved from Qemu driver to hypervisor. After
> migrating Qemu to use domain_logcontext, I extended ch driver to use also use
> domain_logcontext to capture early boot failures within domain specific log
> files.
>
> Changes
LogContext management is now moved from Qemu driver to hypervisor. After
migrating Qemu to use domain_logcontext, I extended ch driver to use also use
domain_logcontext to capture early boot failures within domain specific log
files.
Changes in V2:
* refactored the patches to ensure all of them bu
