On 4/18/24 11:16, Alexander Zeidler wrote: > to get a first clue for debugging passthrough and similar issues, when > no dmesg output has been provided yet. > > Signed-off-by: Alexander Zeidler <a.zeid...@proxmox.com> > --- > v2: > * move away from dmesg base > * only print kernel command line (boot times can be added by another patch) > > v1: https://lists.proxmox.com/pipermail/pve-devel/2024-March/062342.html > > > PVE/Report.pm | 1 + > 1 file changed, 1 insertion(+) > > diff --git a/PVE/Report.pm b/PVE/Report.pm > index 53ffdcbb..a8c1cab9 100644 > --- a/PVE/Report.pm > +++ b/PVE/Report.pm > @@ -31,6 +31,7 @@ my $init_report_cmds = sub { > cmds => [ > 'hostname', > 'date -R', > + 'cat /proc/cmdline', > 'pveversion --verbose', > 'cat /etc/hosts', > 'pvesubscription get', Tested the whole patch series. Looks good so far, especially the cmdline and APT information is nice to have.
With the added APT information between subscription info, lscpu and /cluster/resources, would it maybe make sense to move `pvesubscription get` and `pvesh get /cluster/resources` next to each other, and `lscpu` to the hardware section where we have all the `dmidecode` output, and `lspci`? Except for the `dmidecode -t16,17` command needing a space for consistency, I'm fine with any of the additions. So consider the whole series: Reviewed-by: Mira Limbeck <m.limb...@proxmox.com> Tested-by: Mira Limbeck <m.limb...@proxmox.com> _______________________________________________ pve-devel mailing list pve-devel@lists.proxmox.com https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
