{"id":9420,"date":"2025-04-10T08:44:04","date_gmt":"2025-04-10T08:44:04","guid":{"rendered":"https:\/\/www.gpu4host.com\/knowledge-base\/?p=9420"},"modified":"2025-04-10T09:36:11","modified_gmt":"2025-04-10T09:36:11","slug":"openstack-nova","status":"publish","type":"post","link":"https:\/\/www.gpu4host.com\/knowledge-base\/openstack-nova\/","title":{"rendered":"OpenStack Nova"},"content":{"rendered":"<div class='epvc-post-count'><span class='epvc-eye'><\/span>  <span class=\"epvc-count\"> 1,012<\/span><span class='epvc-label'> Views<\/span><\/div>\n<h2 class=\"wp-block-heading\"><strong>PCI Alias Is Not Defined: OpenStack Nova Troubleshooting<\/strong><\/h2>\n\n\n\n<p>In the case of OpenStack Nova, PCI passthrough helps all instances to use various hardware devices such as GPUs directly. This feature is critical at the time of utilizing <a href=\"https:\/\/www.gpu4host.com\/\">GPU servers<\/a>, mainly in the case of artificial intelligence and machine learning environments or virtual desktop infrastructures. Moreover, a general configuration error occurs at the time Nova fails to launch instances just because of a missing or undefined PCI alias. This guide covers what causes the &#8220;PCI alias is not defined&#8221; issue and how to troubleshoot it.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><strong>A Few Error Message Example<\/strong><\/h2>\n\n\n\n<p>At the time of attempting to boot any instance along with GPU passthrough allowed, you may easily encounter an issue like:<\/p>\n\n\n\n<p class=\"has-vivid-green-cyan-color has-text-color has-link-color wp-elements-f7e4a02fad79d299ec2c27f31901439f\">ERROR (BadRequest): Invalid input for field\/attribute pci_alias. Value: &#8216;gpu&#8217;. Alias &#8216;gpu&#8217; is not defined in the configuration file.<\/p>\n\n\n\n<p class=\"has-black-color has-text-color has-link-color wp-elements-6e760dd50f9310801121ebbc56beeac4\">This shows that the requested alias (in this case, gpu) does not easily map to any specified PCI device as described in the OpenStack Nova setup.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><strong>Root Cause<\/strong><\/h2>\n\n\n\n<p>The issue takes place just because the alias utilized in the flavor or image metadata is not known. Nova utilizes pci_alias entries described in the nova.conf file to map logical alias names (such as gpu) to physical PCI devices.<\/p>\n\n\n\n<p>This error is common at the time of setting up GPU hosting with a <a href=\"https:\/\/www.infinitivehost.com\/gpu-dedicated-server\" target=\"_blank\" rel=\"noopener\">GPU dedicated server<\/a>, as physical GPU assets must be clearly described in the OpenStack Nova configuration.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><strong>Prerequisites<\/strong><\/h2>\n\n\n\n<p>Before resolving, make sure:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>You have full root or admin access to your compute nodes and OpenStack Nova controller.<\/li>\n\n\n\n<li>PCI passthrough is allowed in your environment.<\/li>\n\n\n\n<li>You have installed <a href=\"https:\/\/www.gpu4host.com\/\">GPU server<\/a> and detected them at the hardware level (for example, NVIDIA A40 &amp; NVIDIA A100).<\/li>\n\n\n\n<li>Nova-api and nova-compute services are constantly running.<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\"><strong>Step-by-Step Troubleshooting Guide<\/strong><\/h2>\n\n\n\n<figure class=\"wp-block-image size-full\"><img fetchpriority=\"high\" decoding=\"async\" width=\"768\" height=\"288\" src=\"https:\/\/www.gpu4host.com\/knowledge-base\/wp-content\/uploads\/2025\/04\/Step-by-Step-Troubleshooting-Guide.webp\" alt=\"OpenStack Nova \" class=\"wp-image-9421\" srcset=\"https:\/\/www.gpu4host.com\/knowledge-base\/wp-content\/uploads\/2025\/04\/Step-by-Step-Troubleshooting-Guide.webp 768w, https:\/\/www.gpu4host.com\/knowledge-base\/wp-content\/uploads\/2025\/04\/Step-by-Step-Troubleshooting-Guide-300x113.webp 300w\" sizes=\"(max-width: 768px) 100vw, 768px\" \/><\/figure>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>1. Check GPU Presence on Compute Node<\/strong><\/h3>\n\n\n\n<p>Make sure that the GPU device is completely visible on the host.<\/p>\n\n\n\n<p class=\"has-vivid-green-cyan-color has-text-color has-link-color wp-elements-1419f8ce6c72a69c03190f5c3f0334d8\">lspci | grep -i nvidia<\/p>\n\n\n\n<p>Predicted result (example):<\/p>\n\n\n\n<p class=\"has-vivid-green-cyan-color has-text-color has-link-color wp-elements-857a144823a9da3875bfdd1b99975486\">65:00.0 3D controller: NVIDIA Corporation A100 PCIe 80GB<\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>2. Check Present PCI Alias Configuration<\/strong><\/h3>\n\n\n\n<p>Check your nova.conf file, generally located at \/etc\/nova\/nova.conf.<\/p>\n\n\n\n<p>Look under the [pci] section:<\/p>\n\n\n\n<p class=\"has-vivid-green-cyan-color has-text-color has-link-color wp-elements-d2c7974324c92cbebf9b2f6e7aa878b7\">[pci]<\/p>\n\n\n\n<p class=\"has-vivid-green-cyan-color has-text-color has-link-color wp-elements-b9bf63898c69859050e6fada2e4b7608\">alias = {<\/p>\n\n\n\n<p class=\"has-vivid-green-cyan-color has-text-color has-link-color wp-elements-4076a5effe5050ce92f9ddbba4e0df79\">&nbsp;&nbsp;&nbsp;&nbsp;&#8220;name&#8221;: &#8220;gpu&#8221;,<\/p>\n\n\n\n<p class=\"has-vivid-green-cyan-color has-text-color has-link-color wp-elements-3cd25684c7c8ee5f2b89f4a5498ced59\">&nbsp;&nbsp;&nbsp;&nbsp;&#8220;product_id&#8221;: &#8220;20B0&#8221;,<\/p>\n\n\n\n<p class=\"has-vivid-green-cyan-color has-text-color has-link-color wp-elements-0d578f14253764553de01e9d556d22bb\">&nbsp;&nbsp;&nbsp;&nbsp;&#8220;vendor_id&#8221;: &#8220;10DE&#8221;,<\/p>\n\n\n\n<p class=\"has-vivid-green-cyan-color has-text-color has-link-color wp-elements-ca6513d94fa9aa7ed90ce15d3ab28ba0\">&nbsp;&nbsp;&nbsp;&nbsp;&#8220;device_type&#8221;: &#8220;type-PCI&#8221;<\/p>\n\n\n\n<p class=\"has-vivid-green-cyan-color has-text-color has-link-color wp-elements-59c01ae665f4cd9b3c32403199577e7e\">}<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>vendor_id: Mainly 10DE for NVIDIA.<\/li>\n\n\n\n<li>product_id: Matches the GPU model (utilize lspci -nn to verify).<\/li>\n\n\n\n<li>name: Alias that will be specified in the metadata or flavor.<\/li>\n<\/ul>\n\n\n\n<p>If no alias is described properly, then this is the main reason for the error.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>3. Describe PCI Alias in nova.conf<\/strong><\/h3>\n\n\n\n<p>Simply update or add the PCI alias entry in the [pci] section. The instance for <a href=\"https:\/\/www.gpu4host.com\/nvidia-a100-rental\">NVIDIA A100<\/a> is:<\/p>\n\n\n\n<p class=\"has-vivid-green-cyan-color has-text-color has-link-color wp-elements-d2c7974324c92cbebf9b2f6e7aa878b7\">[pci]<\/p>\n\n\n\n<p class=\"has-vivid-green-cyan-color has-text-color has-link-color wp-elements-b9bf63898c69859050e6fada2e4b7608\">alias = {<\/p>\n\n\n\n<p class=\"has-vivid-green-cyan-color has-text-color has-link-color wp-elements-4076a5effe5050ce92f9ddbba4e0df79\">&nbsp;&nbsp;&nbsp;&nbsp;&#8220;name&#8221;: &#8220;gpu&#8221;,<\/p>\n\n\n\n<p class=\"has-vivid-green-cyan-color has-text-color has-link-color wp-elements-0d578f14253764553de01e9d556d22bb\">&nbsp;&nbsp;&nbsp;&nbsp;&#8220;vendor_id&#8221;: &#8220;10DE&#8221;,<\/p>\n\n\n\n<p class=\"has-vivid-green-cyan-color has-text-color has-link-color wp-elements-3cd25684c7c8ee5f2b89f4a5498ced59\">&nbsp;&nbsp;&nbsp;&nbsp;&#8220;product_id&#8221;: &#8220;20B0&#8221;,<\/p>\n\n\n\n<p class=\"has-vivid-green-cyan-color has-text-color has-link-color wp-elements-ca6513d94fa9aa7ed90ce15d3ab28ba0\">&nbsp;&nbsp;&nbsp;&nbsp;&#8220;device_type&#8221;: &#8220;type-PCI&#8221;<\/p>\n\n\n\n<p class=\"has-vivid-green-cyan-color has-text-color has-link-color wp-elements-59c01ae665f4cd9b3c32403199577e7e\">}<\/p>\n\n\n\n<p>For numerous GPUs with diverse product IDs (e.g., <a href=\"https:\/\/www.gpu4host.com\/nvidia-a40-hosting\">NVIDIA A40<\/a> and NVIDIA A100), describe many aliases:<\/p>\n\n\n\n<p class=\"has-vivid-green-cyan-color has-text-color has-link-color wp-elements-b9bf63898c69859050e6fada2e4b7608\">alias = {<\/p>\n\n\n\n<p class=\"has-vivid-green-cyan-color has-text-color has-link-color wp-elements-e1e8cc1d52fe823d7f5648d1769fc932\">&nbsp;&nbsp;&nbsp;&nbsp;&#8220;name&#8221;: &#8220;gpu_a100&#8221;,<\/p>\n\n\n\n<p class=\"has-vivid-green-cyan-color has-text-color has-link-color wp-elements-0d578f14253764553de01e9d556d22bb\">&nbsp;&nbsp;&nbsp;&nbsp;&#8220;vendor_id&#8221;: &#8220;10DE&#8221;,<\/p>\n\n\n\n<p class=\"has-vivid-green-cyan-color has-text-color has-link-color wp-elements-3cd25684c7c8ee5f2b89f4a5498ced59\">&nbsp;&nbsp;&nbsp;&nbsp;&#8220;product_id&#8221;: &#8220;20B0&#8221;,<\/p>\n\n\n\n<p class=\"has-vivid-green-cyan-color has-text-color has-link-color wp-elements-ca6513d94fa9aa7ed90ce15d3ab28ba0\">&nbsp;&nbsp;&nbsp;&nbsp;&#8220;device_type&#8221;: &#8220;type-PCI&#8221;<\/p>\n\n\n\n<p class=\"has-vivid-green-cyan-color has-text-color has-link-color wp-elements-59c01ae665f4cd9b3c32403199577e7e\">}<\/p>\n\n\n\n<p class=\"has-vivid-green-cyan-color has-text-color has-link-color wp-elements-b9bf63898c69859050e6fada2e4b7608\">alias = {<\/p>\n\n\n\n<p class=\"has-vivid-green-cyan-color has-text-color has-link-color wp-elements-3f0c57e637b1ce1a2c216e8c336052e9\">&nbsp;&nbsp;&nbsp;&nbsp;&#8220;name&#8221;: &#8220;gpu_a40&#8221;,<\/p>\n\n\n\n<p class=\"has-vivid-green-cyan-color has-text-color has-link-color wp-elements-0d578f14253764553de01e9d556d22bb\">&nbsp;&nbsp;&nbsp;&nbsp;&#8220;vendor_id&#8221;: &#8220;10DE&#8221;,<\/p>\n\n\n\n<p class=\"has-vivid-green-cyan-color has-text-color has-link-color wp-elements-462b0779604f605811441e5ac582b6ed\">&nbsp;&nbsp;&nbsp;&nbsp;&#8220;product_id&#8221;: &#8220;2235&#8221;,<\/p>\n\n\n\n<p class=\"has-vivid-green-cyan-color has-text-color has-link-color wp-elements-ca6513d94fa9aa7ed90ce15d3ab28ba0\">&nbsp;&nbsp;&nbsp;&nbsp;&#8220;device_type&#8221;: &#8220;type-PCI&#8221;<\/p>\n\n\n\n<p class=\"has-vivid-green-cyan-color has-text-color has-link-color wp-elements-59c01ae665f4cd9b3c32403199577e7e\">}<\/p>\n\n\n\n<p>You can easily define multiple alias entries by reiterating the alias = line.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>4. Restart Nova Services<\/strong><\/h3>\n\n\n\n<p>After simply updating nova.conf, just restart the appropriate services:<\/p>\n\n\n\n<p class=\"has-vivid-green-cyan-color has-text-color has-link-color wp-elements-4a9d45dffacbf81a62d0d8150331018f\">sudo systemctl restart nova-compute<\/p>\n\n\n\n<p class=\"has-vivid-green-cyan-color has-text-color has-link-color wp-elements-1ff1fc828c39cfe6dc29cab4f1f91a66\">sudo systemctl restart nova-api<\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>5. Create or Update Flavor with Additional Specs<\/strong><\/h3>\n\n\n\n<p>Once the alias is properly described, modify or create a flavor to utilize it.<\/p>\n\n\n\n<p>Example (for NVIDIA A100 GPU):<\/p>\n\n\n\n<p class=\"has-vivid-green-cyan-color has-text-color has-link-color wp-elements-63c5b21786032bec95384bc1114edd42\">openstack flavor set m1.gpu &#8211;property &#8220;pci_passthrough:alias&#8221;=&#8221;gpu_a100:1&#8221;<\/p>\n\n\n\n<p>This describes Nova to allocate 1 GPU that simply matches the alias gpu_a100 to instances launched with this flavor.<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>You can also utilize metadata on all images, but utilizing flavors is generally more compatible for GPU hosting environments.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>6. Test Instance Boot<\/strong><\/h3>\n\n\n\n<p>Try launching an instance utilizing the flavor related to the GPU alias:<\/p>\n\n\n\n<p class=\"has-vivid-green-cyan-color has-text-color has-link-color wp-elements-d61f4532e3f85dd035ba680d847ac433\">openstack server create \\<\/p>\n\n\n\n<p class=\"has-vivid-green-cyan-color has-text-color has-link-color wp-elements-42a51e5f08a4f6949ce7a622c0b718cb\">&nbsp;&nbsp;&#8211;flavor m1.gpu \\<\/p>\n\n\n\n<p class=\"has-vivid-green-cyan-color has-text-color has-link-color wp-elements-07bb8506ade0dacdd5c647137d412531\">&nbsp;&nbsp;&#8211;image ubuntu-22.04 \\<\/p>\n\n\n\n<p class=\"has-vivid-green-cyan-color has-text-color has-link-color wp-elements-78b975b9812e4aee4dfc4a94c58937bd\">&nbsp;&nbsp;&#8211;network private-net \\<\/p>\n\n\n\n<p class=\"has-vivid-green-cyan-color has-text-color has-link-color wp-elements-1a6d057725866257f4395bf0dd9c72b8\">&nbsp;&nbsp;&#8211;security-group default \\<\/p>\n\n\n\n<p class=\"has-vivid-green-cyan-color has-text-color has-link-color wp-elements-fea1c7dd9ef5d3e02ebff3c0c83e3610\">&nbsp;&nbsp;&#8211;key-name mykey \\<\/p>\n\n\n\n<p class=\"has-vivid-green-cyan-color has-text-color has-link-color wp-elements-afe01d5348b09768d1df8164c336efb0\">&nbsp;&nbsp;gpu-instance<\/p>\n\n\n\n<p>If configured properly, the instance will be effortlessly scheduled on a compute node with an easily available GPU coordinating with the alias.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><strong>More Tips<\/strong><\/h2>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>Verify Accessible PCI Devices With the Help of Placement<\/strong><\/h3>\n\n\n\n<p>Utilize the Placement API to examine resource availability:<\/p>\n\n\n\n<p class=\"has-vivid-green-cyan-color has-text-color has-link-color wp-elements-709a6779d9ecde18644e85cb5f1f3464\">openstack resource provider list &#8211;os-placement-api-version 1.2<\/p>\n\n\n\n<p>This helps guarantee the appropriate compute nodes are reporting their GPU server proficiencies to the OpenStack Nova controller.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>Log File Troubleshooting<\/strong><\/h3>\n\n\n\n<p>Check all logs if any issues continue:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li class=\"has-vivid-green-cyan-color has-text-color has-link-color wp-elements-cc1c06d963ae3b3f7fc636367329d9db\">\/var\/log\/nova\/nova-compute.log<\/li>\n\n\n\n<li class=\"has-vivid-green-cyan-color has-text-color has-link-color wp-elements-59b26d611903df5b904327273750838f\">\/var\/log\/nova\/nova-api.log<\/li>\n<\/ul>\n\n\n\n<p>Opt for messages associated with PCI passthrough, scheduling failures, or device claiming.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><strong>Real-World Use Case Situations<\/strong><\/h2>\n\n\n\n<figure class=\"wp-block-image size-full\"><img decoding=\"async\" width=\"768\" height=\"288\" src=\"https:\/\/www.gpu4host.com\/knowledge-base\/wp-content\/uploads\/2025\/04\/Real-World-Use-Case-Situations.webp\" alt=\"OpenStack Nova \" class=\"wp-image-9422\" srcset=\"https:\/\/www.gpu4host.com\/knowledge-base\/wp-content\/uploads\/2025\/04\/Real-World-Use-Case-Situations.webp 768w, https:\/\/www.gpu4host.com\/knowledge-base\/wp-content\/uploads\/2025\/04\/Real-World-Use-Case-Situations-300x113.webp 300w\" sizes=\"(max-width: 768px) 100vw, 768px\" \/><\/figure>\n\n\n\n<ol class=\"wp-block-list\">\n<li><strong>AI and ML-Based Tasks<\/strong>: Organizations utilizing a <a href=\"https:\/\/www.infinitivehost.com\/gpu-dedicated-server\" target=\"_blank\" rel=\"noopener\">GPU dedicated server<\/a>, especially for AI model training (such as TensorFlow and PyTorch), depend on the right PCI passthrough for model boost.<\/li>\n\n\n\n<li><strong>AI Image Generator Deployment<\/strong>: Tools such as AI image generators get a good advantage from running on virtual machines along with direct GPU usage.<\/li>\n\n\n\n<li><strong>GPU Hosting Platforms<\/strong>: Both private and public cloud service providers providing GPU hosting must describe PCI aliases for client access to GPUs such as the NVIDIA A40 and NVIDIA A100.<\/li>\n<\/ol>\n\n\n\n<h2 class=\"wp-block-heading\"><strong>General Mistakes to Avoid<\/strong><\/h2>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Incorrect product ID<\/strong>: Always verify product IDs utilizing lspci -nn instead of guessing.<\/li>\n\n\n\n<li><strong>Syntax issues in <\/strong><strong>nova.conf<\/strong>: Inappropriate JSON format can quietly fail.<\/li>\n\n\n\n<li><strong>Service not restarted<\/strong>: Modifications won&#8217;t be implemented unless OpenStack Nova services are restarted properly.<\/li>\n\n\n\n<li><strong>Flavor mismatch<\/strong>: The alias in the case of flavor must precisely match the one that is present in nova.conf.<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\"><strong>Quick Setup Guide<\/strong><\/h2>\n\n\n\n<figure class=\"wp-block-table\"><table class=\"has-fixed-layout\"><tbody><tr><td><strong>Task<\/strong><\/td><td><strong>Command File<\/strong><\/td><\/tr><tr><td>Verify GPU hardware<\/td><td>`lspci<\/td><\/tr><tr><td>Edit PCI alias<\/td><td>\/etc\/nova\/nova.conf<\/td><\/tr><tr><td>Restart services<\/td><td>systemctl restart nova-*<\/td><\/tr><tr><td>Create flavor<\/td><td>openstack flavor set &#8230;<\/td><\/tr><tr><td>Launch instance<\/td><td>openstack server create &#8230;<\/td><\/tr><tr><td>View logs<\/td><td>\/var\/log\/nova\/<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<h2 class=\"wp-block-heading\"><strong>Conclusion<\/strong><\/h2>\n\n\n\n<p>Describing PCI aliases appropriately in the case of OpenStack Nova is necessary when allowing GPU passthrough, especially for virtual machines, mainly in all those environments that are powered by a GPU dedicated server or a<a href=\"https:\/\/www.gpu4host.com\/\"> GPU server<\/a>. The \u201cPCI alias is not defined\u201d issue specifically arises from missing or misconfigured alias entries in the case of the nova.conf file. By properly identifying GPU devices (such as NVIDIA A40 or NVIDIA A100), configuring the appropriate alias configuration, and relating all of them with flavors, admins can guarantee quick deployment of GPU-backed instances.<\/p>\n\n\n\n<p>For long-term growth, always keep your configuration files well-documented, enable hardware mappings along with lspci, and automate testing after some changes to Nova settings.<\/p>\n\n\n\n<p><\/p>\n","protected":false},"excerpt":{"rendered":"<p>1,012 Views PCI Alias Is Not Defined: OpenStack Nova Troubleshooting In the case of OpenStack Nova, PCI passthrough helps all instances to use various hardware devices such as GPUs directly. This feature is critical at the time of utilizing GPU servers, mainly in the case of artificial intelligence and machine learning environments or virtual desktop [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":9423,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"inline_featured_image":false,"footnotes":""},"categories":[1],"tags":[],"class_list":["post-9420","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-web-hosting"],"_links":{"self":[{"href":"https:\/\/www.gpu4host.com\/knowledge-base\/wp-json\/wp\/v2\/posts\/9420","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.gpu4host.com\/knowledge-base\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.gpu4host.com\/knowledge-base\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.gpu4host.com\/knowledge-base\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.gpu4host.com\/knowledge-base\/wp-json\/wp\/v2\/comments?post=9420"}],"version-history":[{"count":1,"href":"https:\/\/www.gpu4host.com\/knowledge-base\/wp-json\/wp\/v2\/posts\/9420\/revisions"}],"predecessor-version":[{"id":9424,"href":"https:\/\/www.gpu4host.com\/knowledge-base\/wp-json\/wp\/v2\/posts\/9420\/revisions\/9424"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.gpu4host.com\/knowledge-base\/wp-json\/wp\/v2\/media\/9423"}],"wp:attachment":[{"href":"https:\/\/www.gpu4host.com\/knowledge-base\/wp-json\/wp\/v2\/media?parent=9420"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.gpu4host.com\/knowledge-base\/wp-json\/wp\/v2\/categories?post=9420"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.gpu4host.com\/knowledge-base\/wp-json\/wp\/v2\/tags?post=9420"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}