Re: Strange problem with chroot

Robert McBroom via users <users@xxxxxxxxxxxxxxxxxxxxxxx> · Mon, 16 Jun 2025 08:10:36 -0400



    On 6/14/25 6:01 AM, Barry Scott wrote:

    
          On 14 Jun 2025, at 04:35, Robert McBroom via users
            <users@xxxxxxxxxxxxxxxxxxxxxxx> wrote:
          

              CentOs 9.4 installation is going into kernel panic.
                Trying to get access to the system from a running Fedora
                41 installation. 

                  
              ~]#
                    mount /dev/sdb2 /mnt/sysimage 

                  ~]# for
                    dir in /dev /proc /sys;do mount --bind $dir
                    /mnt/sysimage/$dir;done

                   
                ~]# chroot
                    /mnt/sysimage

                   Fatal
                    glibc error: CPU does not support x86-64-v2

                
        Run this to find out what your hardware supports:
      

         ld.so --help
      

      Does it list x86-62-v2 as supported?
      

    From the Fedora 41 installation

    ~]# ld.so --help
      

      Usage: ld.so
        [OPTION]... EXECUTABLE-FILE [ARGS-FOR-PROGRAM...]
      

      You have
        invoked 'ld.so', the program interpreter for dynamically-linked
      

      ELF
        programs.  Usually, the program interpreter is invoked
        automatically
      

      when a
        dynamically-linked executable is started.
      

      You may
        invoke the program interpreter program directly from the command
      

      line to load
        and run an ELF executable file; this is like executing that
      

      file itself,
        but always uses the program interpreter you invoked,
      

      instead of
        the program interpreter specified in the executable file you
      

      run.
         Invoking the program interpreter directly provides access to
      

      additional
        diagnostics, and changing the dynamic linker behavior without
      

      setting
        environment variables (which would be inherited by
        subprocesses).
      

        --list
                       list all dependencies and how they are resolved
      

        --verify
                     verify that given object really is a dynamically
        linked
      

                               object we can handle
      

         --inhibit-cache       Do not use /etc/ld.so.cache
      

         --library-path PATH   use given PATH instead of content of the
        environment
      

                               variable LD_LIBRARY_PATH
      

         --glibc-hwcaps-prepend LIST
      

                               search glibc-hwcaps subdirectories in
        LIST
      

         --glibc-hwcaps-mask LIST
      

                               only search built-in subdirectories if in
        LIST
      

         --inhibit-rpath LIST  ignore RUNPATH and RPATH information in
        object names
      

                               in LIST
      

        --audit
        LIST          use objects named in LIST as auditors
      

        --preload
        LIST        preload objects named in LIST
      

        --argv0
        STRING        set argv[0] to STRING before running
      

         --list-tunables       list all tunables with minimum and
        maximum values
      

         --list-diagnostics    list diagnostics information
      

        --help
                       display this help and exit
      

        --version
                    output version information and exit
      

      This program
        interpreter self-identifies as: /lib64/ld-linux-x86-64.so.2
      

      Shared
        library search path:
      

        (libraries
        located via /etc/ld.so.cache)
      

        /lib64
        (system search path)
      

        /usr/lib64
        (system search path)
      

      Subdirectories
        of glibc-hwcaps directories, in priority order:
      

        x86-64-v4
      

        x86-64-v3
      

        x86-64-v2

      
      When you run chroot it will run /bin/bash from the chroot.
      I recall that RHEL compiles for a higher spec CPU than Fedora
        does.
      

      Try this to run the ld.so inside the chroot and see
        what the chroot thinks.
      

        chroot /mnt/sysimage ld.so --help
      

      Does it say x86-64-v2 is supported?
    
    Then
     ~]# chroot
          /mnt/sysimage ld.so --help
        

        Fatal
          glibc error: CPU does not support x86-64-v2

        
              I've used this
                  process a number of time between installations, What
                  is failing now?

                
        I suspect the hardware you are doing the chroot on is too old if
        ld.so says
        x86-64-v2 is not supported.
      

      Barry
      

-- 
_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue