Re: [rdo-users] [rdo][ussuri][TripleO][nova][kvm] libvirt.libvirtError: internal error: process exited while connecting to monitor

yes, will check and add it later, once back home. On Wed, 24 Jun 2020, 21:02 Arkady Shtempler, <ashtempl(a)redhat.com&gt; wrote: > Hi Ruslanas! > > Is it possible to get all logs under /var/log/containers somehow? > > Thanks! > > On Wed, Jun 24, 2020 at 2:18 AM Ruslanas Gžibovskis <ruslanas(a)lpic.lt&gt; > wrote: > >> Hi Alfredo, >> >> Compute nodes are baremetal or virtualized?, I've seen similar bug >>>> reports when using nested virtualization in other OSes. >>>> >>> baremetal. Dell R630 if to be VERY precise. >> >> >> >>>> When using podman, the recommended way to restart containers is using >>> systemd: >>> >>> >>> https://docs.openstack.org/project-deploy-guide/tripleo-docs/latest/deplo... >>> >> >> Thank you, I will try. I also modified a file, and it looked like it >> relaunched podman container once config was changed. Either way, if I >> understand Linux config correctly, the default value for user and group is >> root, if commented out: >> #user = "root" >> #group = "root" >> >> also in some logs, I saw, that it detected, that it is not AMD CPU :) >> and it is really not AMD CPU. >> >> >> Just for fun, it might be important, here is how my node info looks. >> ComputeS01Parameters: >> NovaReservedHostMemory: 16384 >> KernelArgs: "crashkernel=no rhgb" >> ComputeS01ExtraConfig: >> nova::cpu_allocation_ratio: 4.0 >> nova::compute::libvirt::rx_queue_size: 1024 >> nova::compute::libvirt::tx_queue_size: 1024 >> nova::compute::resume_guests_state_on_host_boot: true >> _______________________________________________ >> users mailing list >> users(a)lists.rdoproject.org >> http://lists.rdoproject.org/mailman/listinfo/users >> >> To unsubscribe: users-unsubscribe(a)lists.rdoproject.org >> >