Re: Issues with DomU consoles and xenconsoled

From: Stephen Walker-Weinshenker <freebsd-xen_at_sww1235.net>
Date: Sat, 03 May 2025 01:12:42 UTC
Hello Roger:

Thanks for the response.

Running xenconsoled in the foreground with the -iv option did successfully launch, but it took over my command line, so not sure how much that would be useful.

When rebooting after uncommenting XENCONSOLED_TRACE="all", the xenconsoled process did not start at all. It is not visible in htop. I did not see any error messages, as it was running in the background.

The service starts up again at next boot when I comment the line back out.

Thanks again



On Wed, Apr 30, 2025, at 02:22, Roger Pau Monné wrote:
> On Tue, Apr 29, 2025 at 08:30:46PM -0600, Stephen Walker-Weinshenker wrote:
> > Running 14.2-RELEASE.
> > 
> > Having issues with xenconsoled not properly starting/restarting with the options I want.
> 
> Hello,
> 
> > During some troubleshooting of a pvh guest, I attempted to relaunch xenconsoled with the following command as root: `xenconsoled --log=guest --log-dir=/var/log/xen/guest/ --timestamp=guest` but the command line reported in htop did not change.
> > 
> > If I killed the xencommons process and attempted to restart it using the same commandline, it would not start.
> 
> What error would you get?  Can you try to start the process with `-iv`,
> as that will prevent it from going into the background.
> 
> > I also attempted to enable the trace functionality of xenconsoled by uncommenting the lines in `/usr/local/etc/rc.d/xencommons` and rebooting, but the process silently failed to start with those lines uncommented.
> 
> Hm, I've attempted to uncomment the TRACE option, so it looks like:
> 
> XENCONSOLED_TRACE="all"
> 
> And that seems to work for me.
> 
> I've noticed the XENCONSOLED_PIDFILE option seem to be completely
> ignored when launching the process.
> 
> > Is there a different/better way to specify these options for xenconsoled? Seems to not like the way I am going about this.
> 
> I've attempted to use:
> 
> # xenconsoled -vi --log="all"
> 
> And it seems to work fine for me, can you describe exactly which
> options are you trying to use?
> 
> Regards, Roger.
>