Þ•”¿  6 )@ j Í€ ,N <{ ¸ ?Ð5-Lc°Ô¸Î \fndƒeè!Np ƒ¤»Ë Þ êØõÎà æô!4V]§e !&;Ld} Œ ™§ ¶ Ã Ñ ß êø  "/ C PZNn9½÷ ‘·¨`qÉvH@! ‰"¤—"v<#S³#$¤$T¼$ & &Î+&ú&$'9'0Y':Š';Å' ( (< ( ]( g( u( €(Š(¡(½(À(IÝ(™')øÁ)ú+Ž~- .*.È.Ñ.×.î. / / "/@//p/-y/§/0Å/¹ö/°2·2V¿2/3jF3*±3Ü4ñ4%5175}i5Kç536;6=X6 –6 6øÀ6B¹7ü78.8F8 e8o8‘~80:*A:l:Ú‚:];1};á¯;0‘=íÂ=°>9É?@ @ƒ›A C)C 0Cf=Ci¤C!D 0D=DSD cDqD …D“D©šDDEWE ^EkE‚E™E¶E½E“ÄE XFeFlFƒF›F®F ÄF ÒF ÜF éF ÷F G G G %G2G HGÉUG I,I BIOIVIHmI0¶I çI ôIvJ wJK)Kz0K;«L çM‰õMuNSõNIO‰[O5åO Q(QÍ>Q RR5R%KR@qR0²R ãRðR4S XÆXÜX ãXíXY Y -Y ;Y.HYwY%~Y¤Y »YbÜY?\F\7M\%…\F«\ò\ ö]^"!^-D^rr^Då^*_1_*D_ o_y_ô_@…`Æ`Ü`ï`ÿ` a aaLf@[0s>&z€ZR‚6=(2#Jp‹vUN|Xb†:,` „Mt~ ŒS+uIToqk{ ]-…h/glB ?K_CˆVyG14c}Fir.$m8QOj\%xd‰Ž*nYƒ;3PA^HeE'ŠWD"7<w‡! 59 )1. Copy this configuration script to a safe directory.2. Make the script executable and run it.3. Delete the script.A comma-separated list of hostnames or domains or ip addresses to ignore proxy settings for. Optionally this may be set to * to bypass proxy settings for all hostnames domains or ip addresses.A plugin to make virt-who configuration easyAccount name by which virt-who is to connect to Nutanix AHV.Account name by which virt-who is to connect to the hypervisor, in the format domain_name\account_name. Note that only a single backslash separates the values for domain_name and account_name. If you are using a domain account, and the global configuration file /etc/virt-who.conf, then two backslashes are required. For further details, see Red Hat Knowledgebase solution How to use a windows domain account with virt-who for more information.Account name by which virt-who is to connect to the hypervisor.Account name by which virt-who is to connect to the hypervisor. By default this is Administrator. To use an alternate account, create a user account and assign that account to the following groups (Windows 2012 Server): Hyper-V Administrators and Remote Management Users.Account name by which virt-who is to connect to the hypervisor. Virt-who does not support password based authentication, you must manually setup SSH key, see Red Hat Knowledgebase solution How to configure virt-who for a KVM host for more information.Account password by which virt-who is to connect to the hypervisor instance.ActionsApplicable only for esx provider type. Hosts which parent (usually ComputeResource) name is specified in comma-separated list in this option will NOT be reported. Wildcards and regular expressions are supported, multiple records must be separated by comma. Put the value into the double-quotes if it contains special characters like comma. All new line characters will be removed in resulting configuration file, white spaces are removed from beginning and end.Applicable only for esx provider type. Only hosts which parent (usually ComputeResource) name is specified in comma-separated list in this option will be reported. Wildcards and regular expressions are supported, multiple records must be separated by comma. Put the value into the double-quotes if it contains special characters like comma. All new line characters will be removed in resulting configuration file, white spaces are removed from beginning and end.BlacklistConfigsConfiguration StatusConfiguration file containing details about how to connect to the cluster and authentication detailsConfiguration file containing details about how to connect to the cluster and authentication details.Configuration interval in minutesConfiguration nameConfiguration numeric identifierConfiguration script: Config|IntervalConfig|Last ReportConfig|NameConnectionContainer-native virtualization’s fully qualified host name or IP address. In order to connect to the cluster it is required to provide path to kubeconfig which contains connection details and authentication token.Copy to clipboardCountCreate ConfigCreate a virt-who configurationDelete a virt-who configurationDelete virt-who configuration %s?DeployDetailsDifferent debug value can't be set per hypervisor, therefore it will affect all other deployed configurations on the host on which this configuration will be deployed.Download the scriptEditEdit Virt-who ConfigEnable AHV debugEnable debugging outputEnable debugging output?Every 12 hoursEvery 2 daysEvery 2 hoursEvery 24 hoursEvery 3 daysEvery 4 hoursEvery 8 hoursEvery hourExclude HostsExclude host parentsExclude hostsExclude hosts which cluster ID is specified in comma-separated list in this option will NOT be reported. PowerCLI command to find the domain names in VMware Get-Cluster “ClusterName†| Select ID. Wildcards and regular expressions are supported, multiple records must be separated by comma. Put the value into the double-quotes if it contains special characters like comma. All new line characters will be removed in resulting configuration file, white spaces are removed from beginning and end.Filter HostsFilter host parentsFilter hostsFilteringForeman server FQDNForeman server’s fully-qualified host name, for example: foreman.example.comFully qualified host name or IP address of the hypervisorGeneral informationHTTP ProxyHTTP proxy that should be used for communication between the server on which virt-who is running and the hypervisors and virtualization managers.HTTP proxy that should be used for communication between the server on which virt-who is running and the hypervisors and virtualization managers. Leave this blank if no proxy is used.Hammer command: HelpHosts which uuid (or hostname or hwuuid, based on hypervisor_id) is specified in comma-separated list in this option will NOT be reported. Wildcards and regular expressions are supported, multiple records must be separated by comma. Put the value into the double-quotes if it contains special characters like comma. All new line characters will be removed in resulting configuration file, white spaces are removed from beginning and end.How often to check connected hypervisors for changes? Also affects how often a mapping is reported. The recommended value for most environments is every two hours. Different interval can't be set per hypervisor, therefore it will affect all other deployed configurations on the host on which this configuration will be deployed.Hypervisor IDHypervisor blacklist, applicable only when filtering mode is set to 2. Wildcards and regular expressions are supported, multiple records must be separated by comma.Hypervisor filtering mode, %{unlimited} means no filtering, %{whitelist} means whitelist, %{blacklist} means blacklistHypervisor password, required for all hypervisor types except for libvirt/kubevirt.Hypervisor typeHypervisor whitelist, applicable only when filtering mode is set to 1. Wildcards and regular expressions are supported, multiple records must be separated by comma.If you run a hybrid environment, with virtual machines running Red Hat Enterprise Linux and other operating systems, you may want to limit the scope of virt-who’s access to hosts. For example, if some hypervisors host only Microsoft Windows Server instances, there is no benefit in having those hypervisors reported by the virt-who agent.Ignore ProxyIgnore proxyIgnore proxy. A comma-separated list of hostnames or domains or ip addresses to ignore proxy settings for. Optionally this may be set to * to bypass proxy settings for all hostnames domains or ip addresses.Interval was not providedLatest Configurations Without ChangeList of virt-who configurationsList of virt-who configurations per organizationMicrosoft Hyper-V fully qualified host name or IP address.Name of this configuration, e.g. the name of the hypervisorNew ConfigNew Virt-who ConfigNewer version of virt-who is required, minimum version is %sNo ChangeNo Report YetNo ReportsNo changeNo configuration foundNutanix AHV’s IP address.OKOn the target virt-who host:On this page you can define virt-who configurations for your hypervisors.One virt-who configuration represents one config file in /etc/virt-who.d directory and maps to single hypervisor, organization and lifecycle environment.Only hosts which cluster ID is specified in comma-separated list in this option will be reported. PowerCLI command to find the domain names in VMware Get-Cluster “ClusterName†| Select ID. Wildcards and regular expressions are supported, multiple records must be separated by comma. Put the value into the double-quotes if it contains special characters like comma. All new line characters will be removed in resulting configuration file, white spaces are removed from beginning and end.Only hosts which uuid (or hostname or hwuuid, based on hypervisor_id) is specified in comma-separated list in this option will be reported. Wildcards and regular expressions are supported, multiple records must be separated by comma. Put the value into the double-quotes if it contains special characters like comma. All new line characters will be removed in resulting configuration file, white spaces are removed from beginning and end.Option Enable debugging output is required to enable AHV internal debug. It provides extra AHV debug information when both options are enabledOption Enable debugging output is required to enable AHV internal debug. It provides extra AHV debug information when both options are enabled Organization of the virt-who configurationOverviewOwnerOwner was not providedPath to kubeconfig filePrism CentralPrism ElementPrism FlavorRenders a deploy script for the specified virt-who configurationScheduleSelect the Prism flavor you are connecting toShow a virt-who configurationSpecifies how the hypervisor will be identified.Specifies that hypervisors will be identified by their hostname, uuid or hwuuid. Note that some virtualization backends don't have all of them implemented. Default is hostname, which provides more meaningful hypervisor names, but can cause duplicated hypervisor registrations if the host is renamed. To avoid that, you can use uuid instead. hwuuid is applicable to esx only. This property is meant to be set up before the initial run of virt-who. Changing it later will result in duplicated entries in the subscription manager.StatusSuccessThe configuration was not deployed yet or the virt-who was unable to report the statusThe virt-who report arrived within the intervalThe virt-who report has not arrived within the interval, which indicates there was no change on hypervisorTo define a new configuration, click the New Config button and fill in the form. After you provide all required information a virt-who configuration script will be generated. You could either install it manually by copying the script or deploy it on a selected target host through Remote Execution.Total ConfigurationsUnable to create sysconfig fileUnable to create virt-who config fileUnable to enable virt-who service using systemctlUnable to install virt-who package, make sure the host is properly subscribed and has access to katello-host-tools repositoryUnable to start virt-who service, please see virt-who logs for more detailsUnknownUnknown configuration statusUnknown configuration status, caused by unexpected conditionsUnlimitedUpdate a virt-who configurationUse either hammer command or the script below to deploy this configuration. Both require root privileges. Run one of them on the target host which has access to katello-host-tools repository and will run virt-who reporting, preferably Foreman host:VMware vCenter server’s fully qualified host name or IP address.Virt-who Configs StatusVirt-who Configuration %sVirt-who ConfigurationsVirt-who Configurations StatusWhitelistevery %s hoursProject-Id-Version: foreman_virt_who_configure 0.5.17 Report-Msgid-Bugs-To: PO-Revision-Date: 2017-05-03 11:59+0000 Last-Translator: Amit Upadhye , 2023 Language-Team: Chinese (China) (https://app.transifex.com/foreman/teams/114/zh_CN/) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Language: zh_CN Plural-Forms: nplurals=1; plural=0; 1. 将这个é…置脚本å¤åˆ¶åˆ°å®‰å…¨ç›®å½•ã€‚2. 使脚本å¯æ‰§è¡Œï¼Œå¹¶è¿è¡Œè„šæœ¬ã€‚3. 删除该脚本。忽略代ç†æœåŠ¡å™¨ã€‚忽略代ç†æœåŠ¡å™¨è®¾ç½®çš„主机åã€åŸŸæˆ– ip 地å€é€—å·åˆ†éš”列表。å¯é€‰æ‹©æ€§åœ°è®¾ç½®ä¸º *,以便为所有主机åã€åŸŸæˆ– ip 地å€è·³è¿‡ä»£ç†æœåŠ¡å™¨è®¾ç½®ã€‚简化 virt-who é…置的æ’件virt-who 连接到 Nutanix AHV çš„å¸æˆ·å称。virt-who 用于连接 hypervisor çš„å¸æˆ·å,格å¼ä¸º domain_name\account_name。注æ„åªä½¿ç”¨å•æ–œçº¿æ¥åˆ†ç¦» domain_name å’Œ account_name 的值。如果您使用域å¸æˆ·ï¼Œä»¥åŠå…¨å±€é…置文件 /etc/virt-who.conf,则需è¦ä½¿ç”¨ åŒæ–œçº¿ã€‚有关进一步详情,请å‚è§çº¢å¸½çŸ¥è¯†åº“解决方案 如何将 windows 域åå¸æˆ·ç”¨äºŽ 在 virt-who 了解更多信æ¯ã€‚virt-who 用于连接 hypervisor çš„å¸æˆ·å。virt-who 连接 hypervisor 所用的å¸æˆ·å。默认为 Administrator。è¦ä½¿ç”¨æ›¿æ¢å¸æˆ·ï¼Œè¯·åˆ›å»ºç”¨æˆ·å¸æˆ·å¹¶å°†è¯¥å¸æˆ·åˆ†é…给以下组(Windows 2012 æœåŠ¡å™¨ï¼‰ï¼šHyper-V 管ç†å‘˜å’Œè¿œç¨‹ç®¡ç†ç”¨æˆ·ã€‚virt-who 连接 hypervisor 所用的å¸æˆ·å。Virt-who ä¸æ”¯æŒåŸºäºŽå¯†ç çš„验è¯ï¼Œæ‚¨å¿…须手动设置 SSH 密钥,有关更多信æ¯ï¼Œè¯·å‚è§ çº¢å¸½çŸ¥è¯†åº“è§£å†³æ–¹æ¡ˆ 如何为 KVM 主机é…ç½® virt-who。virt-who 用于连接 hypervisor 实例的å¸æˆ·å¯†ç ã€‚æ“作仅适用于 esx æ供程åºç±»åž‹ã€‚在此选项中以逗å·åˆ†éš”的列表指定了父资æºï¼ˆé€šå¸¸æ˜¯ ComputeResource)å称的主机ä¸ä¼šè¢«æŠ¥å‘Šã€‚支æŒé€šé…符和正则表达å¼ï¼Œå¤šä¸ªè®°å½•å¿…须用逗å·åˆ†éš”。如果该值包å«é€—å·ç­‰ç‰¹æ®Šå­—符,则将其放在åŒå¼•å·ä¸­ã€‚所有新行字符将在生æˆçš„é…置文件中删除,空格从开头和结尾删除。仅适用于 esx æ供程åºç±»åž‹ã€‚仅报告在此选项中以逗å·åˆ†éš”的列表指定了父资æºï¼ˆé€šå¸¸æ˜¯ ComputeResource)å称的主机。支æŒé€šé…符和正则表达å¼ï¼Œå¤šä¸ªè®°å½•å¿…须用逗å·åˆ†éš”。如果该值包å«é€—å·ç­‰ç‰¹æ®Šå­—符,则将其放在åŒå¼•å·ä¸­ã€‚所有新行字符将在生æˆçš„é…置文件中删除,空格从开头和结尾删除。黑åå•é…ç½®é…置状æ€é…置文件,其中包å«æœ‰å…³å¦‚何连接到集群的详细信æ¯ä»¥åŠèº«ä»½éªŒè¯çš„详细信æ¯é…置文件,其中包å«æœ‰å…³å¦‚何连接到集群的详细信æ¯ä»¥åŠèº«ä»½éªŒè¯çš„详细信æ¯ã€‚以分钟为å•ä½çš„é…置间隔é…ç½®å称é…置数字识别符é…置脚本:é…ç½®|é—´éš”é…ç½®|最新报告é…ç½®|å称连接容器原生虚拟化的标准主机å或 IP 地å€ã€‚为了连接到集群,需è¦æä¾› kubeconfig 的路径,其中包å«è¿žæŽ¥è¯¦ç»†ä¿¡æ¯å’Œèº«ä»½éªŒè¯ä»¤ç‰Œã€‚å¤åˆ¶åˆ°å‰ªè´´æ¿è®¡æ•°åˆ›å»ºé…置创建 virt-who é…置删除 virt-who é…置删除 virt-who é…ç½® %s?部署详情ä¸èƒ½ä¸ºæ¯ä¸ªç®¡ç†ç¨‹åºè®¾ç½®ä¸åŒçš„调试值,因此它将影å“将在其上部署此é…置的主机上的所有其他已部署的é…置。下载脚本编辑编辑 Virt-who é…ç½®å¯ç”¨ AHV 故障排除å¯ç”¨è°ƒè¯•è¾“出å¯ç”¨è°ƒè¯•è¾“å‡ºï¼Ÿæ¯ 12 å°æ—¶æ¯ 2 å¤©æ¯ 2 å°æ—¶æ¯ 24 å°æ—¶æ¯ 3 å¤©æ¯ 4 å°æ—¶æ¯ 8 å°æ—¶æ¯å°æ—¶æŽ’除主机排除主机父系统排除主机排除集群 ID 在这个选项中列出(以逗å·åˆ†éš”的列表)的主机,ä¸ä¼šæŠ¥å‘Šè¿™äº›ä¸»æœºã€‚PowerCLI 命令在 VMware Get-Cluster "ClusterName" | Select ID 中找到域å。支æŒé€šé…符和正则表达å¼ï¼Œä»¥é€—å·åˆ†å¼€å¤šä¸ªè®°å½•ã€‚如果包å«ç‰¹æ®Šå­—符(如逗å·ï¼‰ï¼Œåˆ™éœ€è¦å°†å€¼åŒ…括在括å·ä¸­ã€‚在结果é…置文件中,所有新行都将被删除,开头和结尾的空字符也会被删除。过滤主机过滤主机父系统过滤主机过滤Foreman æœåŠ¡å™¨ FQDNForeman æœåŠ¡å™¨çš„完全é™å®šä¸»æœºå,例如:foreman.example.comHypervisor 的完全é™å®šä¸»æœºå或 IP 地å€é€šç”¨ä¿¡æ¯HTTP 代ç†åº”当用于 virt-who è¿è¡Œæ‰€åœ¨æœåŠ¡å™¨å’Œ hypervisor åŠè™šæ‹ŸåŒ–管ç†å™¨ä¹‹é—´é€šä¿¡çš„ HTTP 代ç†æœåŠ¡å™¨ã€‚应当用于 virt-who è¿è¡Œæ‰€åœ¨æœåŠ¡å™¨å’Œ hypervisor åŠè™šæ‹Ÿç®¡ç†å™¨ä¹‹é—´é€šä¿¡çš„ HTTP 代ç†æœåŠ¡å™¨ã€‚如果未使用代ç†æœåŠ¡å™¨ï¼Œåˆ™ç•™ç©ºã€‚Hammer 命令:帮助ä¸æŠ¥å‘Šåœ¨æ­¤é€‰é¡¹ä¸­ä»¥é€—å·åˆ†éš”的列表指定了uuid(或主机å或 hwuuid,基于 hypervisor_id)的主机。支æŒé€šé…符和正则表达å¼ï¼Œå¤šä¸ªè®°å½•å¿…须用逗å·åˆ†éš”。如果该值包å«é€—å·ç­‰ç‰¹æ®Šå­—符,则将其放在åŒå¼•å·ä¸­ã€‚所有新行字符将在生æˆçš„é…置文件中删除,空格从开头和结尾删除。检查连接的虚拟机管ç†ç¨‹åºæ˜¯å¦æœ‰æ›´æ”¹çš„频率?åŒæ—¶è¿˜å½±å“报告映射的频率。对于大多数环境,建议值为æ¯ä¸¤ä¸ªå°æ—¶ä¸€æ¬¡ã€‚ä¸èƒ½ä¸ºæ¯ä¸ªè™šæ‹Ÿæœºç®¡ç†ç¨‹åºè®¾ç½®ä¸åŒçš„间隔,因此它将影å“将在其上部署此é…置的主机上的所有其他已部署的é…置。Hypervisor IDHypervisor 黑åå•ï¼Œä»…在过滤模å¼è®¾ç½®ä¸º 2 时适用。支æŒé€šé…符和正则表达å¼ï¼Œå¿…须用逗å·åˆ†éš”多项记录。Hypervisor è¿‡æ»¤æ¨¡å¼ %{unlimited} 表示没有过滤,%{whitelist} 表示白åå•ï¼Œ%{blacklist} 代表黑åå•Hypervisor 密ç ï¼Œé™¤ libvirt/kubevirt 以外的所有 hypervisor 类型都需è¦Hypervisor 类型Hypervisor 白åå•ï¼Œä»…在过滤模å¼è®¾ç½®ä¸º 1 时适用。支æŒé€šé…符和正则表达å¼ï¼Œå¿…须用逗å·åˆ†éš”多项记录。如果您è¿è¡Œæ··åˆçŽ¯å¢ƒï¼Œä¸”虚拟机è¿è¡Œ Red Hat Enterprise Linux 和其他æ“作系统,您å¯èƒ½æƒ³è¦é™åˆ¶ virt-who 对主机的访问æƒé™èŒƒå›´ã€‚例如,如果æŸäº› hypervisor åªæ‰˜ç®¡ Microsoft Windows Server 实例,那么让 virt-who agent 报告这些 hypervisor 没有任何æ„义。忽略代ç†å¿½ç•¥ä»£ç†æœåŠ¡å™¨å¿½ç•¥ä»£ç†æœåŠ¡å™¨ã€‚忽略代ç†æœåŠ¡å™¨è®¾ç½®çš„主机åã€åŸŸæˆ– ip 地å€é€—å·åˆ†éš”列表。å¯é€‰æ‹©æ€§åœ°è®¾ç½®ä¸º *,以便为所有主机åã€åŸŸæˆ– ip 地å€è·³è¿‡ä»£ç†æœåŠ¡å™¨è®¾ç½®ã€‚未æ供间隔无更改的最新é…ç½®virt-who é…置列表æ¯ä¸ªæœºæž„çš„ virt-who é…置列表Microsoft Hyper-V fully 的完全é™å®šä¸»æœºå或 IP 地å€ã€‚æ­¤é…置的å称,例如 hypervisor çš„å称新建é…置新建 Virt-who é…置需è¦æ›´é«˜çš„ virt-who 版本,最低版本为 %s無變更尚没有报告没有报告ä¸æ›´æ”¹æ‰¾ä¸åˆ°é…ç½®Nutanix AHV çš„ IP 地å€ã€‚好在目标 virt-who 主机上:在本页é¢ï¼Œæ‚¨å¯ä»¥ä¸ºæ‚¨çš„ hypervisor 定义 virt-who é…置。一个 virt-who é…置代表 /etc/virt-who.d 目录中的一个é…置文件,映射至å•ä¸ª hypervisorã€æœºæž„和生命周期环境。åªæœ‰é›†ç¾¤ ID 在这个选项中列出(以逗å·åˆ†éš”的列表)的主机æ‰ä¼šæŠ¥å‘Šã€‚PowerCLI 命令在 VMware Get-Cluster "ClusterName" | Select ID 中找到域å。支æŒé€šé…符和正则表达å¼ï¼Œä»¥é€—å·åˆ†å¼€å¤šä¸ªè®°å½•ã€‚如果包å«ç‰¹æ®Šå­—符(如逗å·ï¼‰ï¼Œåˆ™éœ€è¦å°†å€¼åŒ…括在括å·ä¸­ã€‚在结果é…置文件中,所有新行都将被删除,开头和结尾的空字符也会被删除。仅报告在此选项中以逗å·åˆ†éš”的列表指定了uuid(或主机å或 hwuuid,基于 hypervisor_id)的主机。支æŒé€šé…符和正则表达å¼ï¼Œå¤šä¸ªè®°å½•å¿…须用逗å·åˆ†éš”。如果该值包å«é€—å·ç­‰ç‰¹æ®Šå­—符,则将其放在åŒå¼•å·ä¸­ã€‚所有新行字符将在生æˆçš„é…置文件中删除,空格从开头和结尾删除。å¯ç”¨ AHV å†…éƒ¨æ•…éšœæŽ’é™¤éœ€è¦ Option Enable debugging output。它会在两个选项都å¯ç”¨æ—¶æä¾›é¢å¤–çš„ AHV 调试信æ¯å¯ç”¨ AHV å†…éƒ¨æ•…éšœæŽ’é™¤éœ€è¦ Option Enable debugging output。它会在两个选项都å¯ç”¨æ—¶æä¾›é¢å¤–çš„ AHV è°ƒè¯•ä¿¡æ¯ virt-who é…置机构概况所有者未æ供所有者到 kubeconfig 文件的路径Prism CentralPrism ElementPrism Flavor为指定的 virt-who é…ç½®æ供部署脚本调度选择您è¦è¿žæŽ¥åˆ°çš„ Prism 类别显示 virt-who é…置指定如何识别 hypervisor。指定 hypervisor 由其 hostnameã€uuid 或 hwuuid 标识。 注æ„æŸäº›è™šæ‹ŸåŒ–åŽç«¯å¹¶æœªå®Œå…¨å®žæ–½ã€‚ 默认为 hostname,它æ供更具æ„义的 hypervisor å称,但如果主机é‡å‘½å,则å¯èƒ½é€ æˆé‡å¤çš„ hypervisor 注册。为了é¿å…è¿™ç§æƒ…况,å¯ä½¿ç”¨ uuid 代替。hwuuid 仅适用于 esx。 此特性应在首次è¿è¡Œ virt-who 之å‰è®¾ç½®ã€‚之åŽæ›´æ”¹å°†å¯¼è‡´è®¢é˜…管ç†å™¨ä¸­å‡ºçŽ°é‡å¤æ¡ç›®ã€‚状æ€æˆåŠŸå°šæœªéƒ¨ç½²é…置,或者 virt-who 无法报告状æ€åœ¨é—´éš”期间收到 virt-who 报告未在间隔期间收到 virt-who 报告,表示 hypervisor 无更改如è¦å®šä¹‰æ–°é…置,请点击 New Config 按钮,填写表格。当您æ供所有所需信æ¯ä¹‹åŽï¼Œä¼šç”Ÿæˆ virt-who é…置脚本。您å¯ä»¥é€šè¿‡å¤åˆ¶è„šæœ¬è¿›è¡Œæ‰‹åŠ¨å®‰è£…,也å¯ä»¥é€šè¿‡ Remote Execution 在选定的目标主机上部署。全部é…置无法创建 sysconfig 文件无法创建 virt-who é…置文件无法使用 systemctl å¯ç”¨ virt-who æœåŠ¡æ— æ³•å®‰è£… virt-who 软件包,确ä¿å·²æ­£ç¡®è®¢é˜…主机,且具备访问 katello-host-tools 的访问æƒé™æ— æ³•å¼€å§‹ virt-who æœåŠ¡ï¼Œè¯·æŸ¥çœ‹ virt-who 日志了解详情未知未知é…置状æ€æœªçŸ¥é…置状æ€ï¼Œç”±æ„外情况造æˆæ— é™åˆ¶æ›´æ–° virt-who é…置使用 hammer 命令或下é¢çš„脚本æ¥éƒ¨ç½²æ­¤é…ç½®ã€‚ä¸¤è€…éƒ½éœ€è¦ root 特æƒã€‚在有æƒè®¿é—® Red Hat Satellite Tools 仓库的一个目标主机上è¿è¡Œå…¶ä¸­ä¸€ä¸ªï¼Œå¹¶è¿è¡Œ virt-who 报告,最好在 Foreman 主机上è¿è¡Œï¼šVMware vCenter æœåŠ¡å™¨çš„完全é™å®šä¸»æœºå或 IP 地å€ã€‚Virt-who é…置状æ€Virt-who é…ç½® %sVirt-who é…ç½®Virt-who é…置状æ€ç™½åå•æ¯ %s å°æ—¶