{"id":7431,"date":"2016-04-12T10:01:23","date_gmt":"2016-04-12T08:01:23","guid":{"rendered":"https:\/\/www.dbi-services.com\/blog\/vm-linux-device-not-found-network-unreachable\/"},"modified":"2023-01-03T13:59:32","modified_gmt":"2023-01-03T12:59:32","slug":"vm-linux-device-not-found-network-unreachable","status":"publish","type":"post","link":"https:\/\/www.dbi-services.com\/blog\/vm-linux-device-not-found-network-unreachable\/","title":{"rendered":"VM Linux &#8211; Device not found :  Network unreachable"},"content":{"rendered":"<p>Recently I exported an Oracle Virtual Box VM as an &#8220;.ova&#8221; file. When the file was imported again I faced issues with the network devices inside the VM. This post is about what I experienced and how I resolved it.<\/p>\n<p>In my example I have two networks devices configured for the VM in the Virtual Box:<br \/>\n<a href=\"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2022\/04\/OVA.png\"><img loading=\"lazy\" decoding=\"async\" class=\" size-medium wp-image-7701 aligncenter\" src=\"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2022\/04\/OVA.png\" alt=\"Importation OVA\" width=\"300\" height=\"203\"><\/a><\/p>\n<p>When I logged in I found that eth0 and eth1 are not available:<br \/>\n<code><br \/>\n[root@MYSQL ~]# ifconfig<br \/>\nlo Link encap:Local Loopback<br \/>\ninet addr:127.0.0.1 Mask:255.0.0.0<br \/>\ninet6 addr: ::1\/128 Scope:Host<br \/>\nUP LOOPBACK RUNNING MTU:65536 Metric:1<br \/>\nRX packets:16 errors:0 dropped:0 overruns:0 frame:0<br \/>\nTX packets:16 errors:0 dropped:0 overruns:0 carrier:0<br \/>\ncollisions:0 txqueuelen:0<br \/>\nRX bytes:960 (960.0 b) TX bytes:960 (960.0 b)<br \/>\n[root@MYSQL ~]#<br \/>\n<\/code><\/p>\n<p>The issue is with the udev rules for the network devices. You can check these in &#8220;\/etc\/udev\/rules.d&#8221;. Usually the file which defines the rules for the network devices is named &#8220;70-persistent-net.rules&#8221;:<br \/>\n<code><br \/>\n[root@MYSQL ~]# cd \/etc\/udev\/rules.d\/<br \/>\n[root@MYSQL rules.d]# ll<br \/>\ntotal 44<br \/>\n-rw-r--r--. 1 root root 1652 Nov 12 2010 60-fprint-autosuspend.rules<br \/>\n-rw-r--r--. 1 root root 1060 Nov 11 2010 60-pcmcia.rules<br \/>\n-rw-r--r--. 1 root root 316 Oct 15 2014 60-raw.rules<br \/>\n-rw-r--r--. 1 root root 134 Aug 18 2015 60-vboxadd.rules<br \/>\n-rw-r--r--. 1 root root 530 Apr 29 2015 70-persistent-cd.rules<br \/>\n<strong>-rw-r--r--. 1 root root 1245 Mar 19 19:23 70-persistent-net.rules<\/strong><br \/>\n-rw-r--r--. 1 root root 320 Jan 12 2015 90-alsa.rules<br \/>\n-rw-r--r--. 1 root root 83 Oct 15 2014 90-hal.rules<br \/>\n-rw-r--r--. 1 root root 2486 Nov 11 2010 97-bluetooth-serial.rules<br \/>\n-rw-r--r--. 1 root root 308 Apr 15 2015 98-kexec.rules<br \/>\n-rw-r--r--. 1 root root 54 Dec 8 2011 99-fuse.rules<br \/>\n<\/code><\/p>\n<p>To resolve this check the MAC address for the VM in VirtualBox and adapt the file with the same values that VirtualBox shows for the network device:<br \/>\n<a href=\"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2022\/04\/MAC-Address.png\"><img loading=\"lazy\" decoding=\"async\" class=\" size-medium wp-image-7704 alignleft\" src=\"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2022\/04\/MAC-Address.png\" alt=\"MAC Address\" width=\"300\" height=\"157\"> <\/a><a href=\"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2022\/04\/MAC-Address-v2.png\"><img loading=\"lazy\" decoding=\"async\" class=\"alignnone size-medium wp-image-7705\" src=\"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2022\/04\/MAC-Address-v2.png\" alt=\"MAC Address v2\" width=\"300\" height=\"157\"><\/a><\/p>\n<p>Why? When you clone a VM that causes VirtualBox to generate a new MAC address for the network device. The new device is auto detected when VM boots and added as a new device in &#8220;\/etc\/udev\/rules.d\/70-persistent-net.rules&#8221;:<br \/>\n<code><br \/>\n[root@MYSQL rules.d]# vi 70-persistent-net.rules<br \/>\nThis file was automatically generated by the \/lib\/udev\/write_net_rules<br \/>\n# program, run by the persistent-net-generator.rules rules file.<br \/>\n#<br \/>\n# You can modify it, as long as you keep each rule on a single<br \/>\n# line, and change only the value of the NAME= key.<br \/>\n#<br \/>\n# PCI device 0x8086:0x100e (e1000)<br \/>\nSUBSYSTEM==\"net\", ACTION==\"add\", DRIVERS==\"?*\", ATTR{address}==\"08:00:27:4a:32:87\", ATTR{type}==\"1\", KERNEL==\"eth*\", NAME=\"eth0\"<br \/>\n..<br \/>\n# PCI device 0x8086:0x100e (e1000)<br \/>\nSUBSYSTEM==\"net\", ACTION==\"add\", DRIVERS==\"?*\", ATTR{address}==\"08:00:27:87:cc:59\", ATTR{type}==\"1\", KERNEL==\"eth*\", NAME=\"eth1\"<br \/>\n..<br \/>\n# PCI device 0x8086:0x100e (e1000)<br \/>\nSUBSYSTEM==\"net\", ACTION==\"add\", DRIVERS==\"?*\", ATTR{address}==\"08:00:27:05:19:40\", ATTR{type}==\"1\", KERNEL==\"eth*\", NAME=\"eth3\"<br \/>\n..<br \/>\n# PCI device 0x8086:0x100e (e1000)<br \/>\nSUBSYSTEM==\"net\", ACTION==\"add\", DRIVERS==\"?*\", ATTR{address}==\"08:00:27:ba:d7:60\", ATTR{type}==\"1\", KERNEL==\"eth*\", NAME=\"eth2\"<br \/>\n..<br \/>\n# PCI device 0x8086:0x100e (e1000)<br \/>\n<strong>SUBSYSTEM==\"net\", ACTION==\"add\", DRIVERS==\"?*\", ATTR{address}==\"08:00:27:54:57:a8\", ATTR{type}==\"1\", KERNEL==\"eth*\", NAME=\"eth4\"<br \/>\n..<br \/>\n# PCI device 0x8086:0x100e (e1000)<br \/>\nSUBSYSTEM==\"net\", ACTION==\"add\", DRIVERS==\"?*\", ATTR{address}==\"08:00:27:09:6c:96\", ATTR{type}==\"1\", KERNEL==\"eth*\", NAME=\"eth5\"<\/strong><br \/>\n<\/code><\/p>\n<p>Edit the file &#8220;70-persistent-net.rules&#8221; and adapt your network configuration for eth0 and eth1.<br \/>\n<code><br \/>\n# This file was automatically generated by the \/lib\/udev\/write_net_rules<br \/>\n# program, run by the persistent-net-generator.rules rules file.<br \/>\n#<br \/>\n# You can modify it, as long as you keep each rule on a single<br \/>\n# line, and change only the value of the NAME= key.<br \/>\n#<br \/>\n# PCI device 0x8086:0x100e (e1000)<br \/>\n#SUBSYSTEM==\"net\", ACTION==\"add\", DRIVERS==\"?*\", ATTR{address}==\"08:00:27:4a:32:87\", ATTR{type}==\"1\", KERNEL==\"eth*\", NAME=\"eth0\"<br \/>\n..<br \/>\n# PCI device 0x8086:0x100e (e1000)<br \/>\n#SUBSYSTEM==\"net\", ACTION==\"add\", DRIVERS==\"?*\", ATTR{address}==\"08:00:27:87:cc:59\", ATTR{type}==\"1\", KERNEL==\"eth*\", NAME=\"eth1\"<br \/>\n..<br \/>\n# PCI device 0x8086:0x100e (e1000)<br \/>\n#SUBSYSTEM==\"net\", ACTION==\"add\", DRIVERS==\"?*\", ATTR{address}==\"08:00:27:05:19:40\", ATTR{type}==\"1\", KERNEL==\"eth*\", NAME=\"eth3\"<br \/>\n..<br \/>\n# PCI device 0x8086:0x100e (e1000)<br \/>\n#SUBSYSTEM==\"net\", ACTION==\"add\", DRIVERS==\"?*\", ATTR{address}==\"08:00:27:ba:d7:60\", ATTR{type}==\"1\", KERNEL==\"eth*\", NAME=\"eth2\"<br \/>\n..<br \/>\n<strong># PCI device 0x8086:0x100e (e1000)<br \/>\nSUBSYSTEM==\"net\", ACTION==\"add\", DRIVERS==\"?*\", ATTR{address}==\"08:00:27:54:57:a8\", ATTR{type}==\"1\", KERNEL==\"eth*\", NAME=\"eth1\"<br \/>\n..<br \/>\n# PCI device 0x8086:0x100e (e1000)<br \/>\nSUBSYSTEM==\"net\", ACTION==\"add\", DRIVERS==\"?*\", ATTR{address}==\"08:00:27:09:6c:96\", ATTR{type}==\"1\", KERNEL==\"eth*\", NAME=\"eth0\"<\/strong><br \/>\n<\/code><\/p>\n<p>Execute the following command: &#8220;udevadm trigger &#8211;type=devices &#8211;action=add&#8221; without reboot and restart the network service :<br \/>\n<code><br \/>\n[root@MYSQL network-scripts]# <strong>udevadm trigger --type=devices --action=add<\/strong><br \/>\n[root@MYSQL network-scripts]# service network restart<br \/>\nShutting down interface eth0:                              [  OK  ]<br \/>\nShutting down interface eth1:                              [  OK  ]<br \/>\nShutting down loopback interface:                          [  OK  ]<br \/>\nBringing up loopback interface:                            [  OK  ]<br \/>\nBringing up interface eth0:<br \/>\nDetermining IP information for eth0... done.<br \/>\n[  OK  ]<br \/>\nBringing up interface eth1:  Determining if ip address 192.168.56.11 is already in use for device eth1...<br \/>\n[  OK  ]<br \/>\n[root@MYSQL network-scripts]#<br \/>\n<\/code><\/p>\n<p>After this change the network devices in the Virtual Machine are up and running again:<br \/>\n<code><br \/>\n[root@MYSQL ~]# ifconfig<br \/>\neth0 Link encap:Ethernet HWaddr 08:00:27:09:6C:96<br \/>\ninet addr:10.0.0.11 Bcast:10.0.0.255 Mask:255.255.255.0<br \/>\ninet6 addr: fe80::a00:27ff:fe09:6c96\/64 Scope:Link<br \/>\nUP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1<br \/>\nRX packets:2 errors:0 dropped:0 overruns:0 frame:0<br \/>\nTX packets:11 errors:0 dropped:0 overruns:0 carrier:0<br \/>\ncollisions:0 txqueuelen:1000<br \/>\nRX bytes:1180 (1.1 KiB) TX bytes:1346 (1.3 KiB)<br \/>\n..<br \/>\neth1 Link encap:Ethernet HWaddr 08:00:27:54:57:A8<br \/>\ninet addr:192.168.56.11 Bcast:192.168.56.255 Mask:255.255.255.0<br \/>\ninet6 addr: fe80::a00:27ff:fe54:57a8\/64 Scope:Link<br \/>\nUP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1<br \/>\nRX packets:8 errors:0 dropped:0 overruns:0 frame:0<br \/>\nTX packets:11 errors:0 dropped:0 overruns:0 carrier:0<br \/>\ncollisions:0 txqueuelen:1000<br \/>\nRX bytes:506 (506.0 b) TX bytes:726 (726.0 b)<br \/>\n..<br \/>\nlo Link encap:Local Loopback<br \/>\ninet addr:127.0.0.1 Mask:255.0.0.0<br \/>\ninet6 addr: ::1\/128 Scope:Host<br \/>\nUP LOOPBACK RUNNING MTU:65536 Metric:1<br \/>\nRX packets:40 errors:0 dropped:0 overruns:0 frame:0<br \/>\nTX packets:40 errors:0 dropped:0 overruns:0 carrier:0<br \/>\ncollisions:0 txqueuelen:0<br \/>\nRX bytes:3004 (2.9 KiB) TX bytes:3004 (2.9 KiB)<br \/>\n[root@MYSQL ~]#<br \/>\n<\/code><\/p>\n","protected":false},"excerpt":{"rendered":"<p>Recently I exported an Oracle Virtual Box VM as an &#8220;.ova&#8221; file. When the file was imported again I faced issues with the network devices inside the VM. This post is about what I experienced and how I resolved it. In my example I have two networks devices configured for the VM in the Virtual [&hellip;]<\/p>\n","protected":false},"author":109,"featured_media":7435,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[229,42],"tags":[46,317],"type_dbi":[],"class_list":["post-7431","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-database-administration-monitoring","category-operating-systems","tag-linux-unix","tag-network"],"acf":[],"yoast_head":"<!-- This site is optimized with the Yoast SEO Premium plugin v27.2 (Yoast SEO v27.2) - https:\/\/yoast.com\/product\/yoast-seo-premium-wordpress\/ -->\n<title>VM Linux - Device not found : Network unreachable - dbi Blog<\/title>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/www.dbi-services.com\/blog\/vm-linux-device-not-found-network-unreachable\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"VM Linux - Device not found : Network unreachable\" \/>\n<meta property=\"og:description\" content=\"Recently I exported an Oracle Virtual Box VM as an &#8220;.ova&#8221; file. When the file was imported again I faced issues with the network devices inside the VM. This post is about what I experienced and how I resolved it. In my example I have two networks devices configured for the VM in the Virtual [&hellip;]\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.dbi-services.com\/blog\/vm-linux-device-not-found-network-unreachable\/\" \/>\n<meta property=\"og:site_name\" content=\"dbi Blog\" \/>\n<meta property=\"article:published_time\" content=\"2016-04-12T08:01:23+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2023-01-03T12:59:32+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2022\/04\/OVA-1.png\" \/>\n\t<meta property=\"og:image:width\" content=\"508\" \/>\n\t<meta property=\"og:image:height\" content=\"343\" \/>\n\t<meta property=\"og:image:type\" content=\"image\/png\" \/>\n<meta name=\"author\" content=\"DevOps\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"DevOps\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"5 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/vm-linux-device-not-found-network-unreachable\/#article\",\"isPartOf\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/vm-linux-device-not-found-network-unreachable\/\"},\"author\":{\"name\":\"DevOps\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/4cd1b5f8a3de93f05a16ab8d7d2b7735\"},\"headline\":\"VM Linux &#8211; Device not found : Network unreachable\",\"datePublished\":\"2016-04-12T08:01:23+00:00\",\"dateModified\":\"2023-01-03T12:59:32+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/vm-linux-device-not-found-network-unreachable\/\"},\"wordCount\":226,\"commentCount\":0,\"image\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/vm-linux-device-not-found-network-unreachable\/#primaryimage\"},\"thumbnailUrl\":\"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2022\/04\/OVA-1.png\",\"keywords\":[\"Linux\/UNIX\",\"Network\"],\"articleSection\":[\"Database Administration &amp; Monitoring\",\"Operating systems\"],\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\/\/www.dbi-services.com\/blog\/vm-linux-device-not-found-network-unreachable\/#respond\"]}]},{\"@type\":\"WebPage\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/vm-linux-device-not-found-network-unreachable\/\",\"url\":\"https:\/\/www.dbi-services.com\/blog\/vm-linux-device-not-found-network-unreachable\/\",\"name\":\"VM Linux - Device not found : Network unreachable - dbi Blog\",\"isPartOf\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/vm-linux-device-not-found-network-unreachable\/#primaryimage\"},\"image\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/vm-linux-device-not-found-network-unreachable\/#primaryimage\"},\"thumbnailUrl\":\"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2022\/04\/OVA-1.png\",\"datePublished\":\"2016-04-12T08:01:23+00:00\",\"dateModified\":\"2023-01-03T12:59:32+00:00\",\"author\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/4cd1b5f8a3de93f05a16ab8d7d2b7735\"},\"breadcrumb\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/vm-linux-device-not-found-network-unreachable\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/www.dbi-services.com\/blog\/vm-linux-device-not-found-network-unreachable\/\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/vm-linux-device-not-found-network-unreachable\/#primaryimage\",\"url\":\"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2022\/04\/OVA-1.png\",\"contentUrl\":\"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2022\/04\/OVA-1.png\",\"width\":508,\"height\":343},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/vm-linux-device-not-found-network-unreachable\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Accueil\",\"item\":\"https:\/\/www.dbi-services.com\/blog\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"VM Linux &#8211; Device not found : Network unreachable\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#website\",\"url\":\"https:\/\/www.dbi-services.com\/blog\/\",\"name\":\"dbi Blog\",\"description\":\"\",\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/www.dbi-services.com\/blog\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en-US\"},{\"@type\":\"Person\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/4cd1b5f8a3de93f05a16ab8d7d2b7735\",\"name\":\"DevOps\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/secure.gravatar.com\/avatar\/cdd2dd7441774355062c0f0f68612296b059cd1e2ff6c7af0b15dba0ed64a85f?s=96&d=mm&r=g\",\"url\":\"https:\/\/secure.gravatar.com\/avatar\/cdd2dd7441774355062c0f0f68612296b059cd1e2ff6c7af0b15dba0ed64a85f?s=96&d=mm&r=g\",\"contentUrl\":\"https:\/\/secure.gravatar.com\/avatar\/cdd2dd7441774355062c0f0f68612296b059cd1e2ff6c7af0b15dba0ed64a85f?s=96&d=mm&r=g\",\"caption\":\"DevOps\"},\"url\":\"https:\/\/www.dbi-services.com\/blog\/author\/devops\/\"}]}<\/script>\n<!-- \/ Yoast SEO Premium plugin. -->","yoast_head_json":{"title":"VM Linux - Device not found : Network unreachable - dbi Blog","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/www.dbi-services.com\/blog\/vm-linux-device-not-found-network-unreachable\/","og_locale":"en_US","og_type":"article","og_title":"VM Linux - Device not found : Network unreachable","og_description":"Recently I exported an Oracle Virtual Box VM as an &#8220;.ova&#8221; file. When the file was imported again I faced issues with the network devices inside the VM. This post is about what I experienced and how I resolved it. In my example I have two networks devices configured for the VM in the Virtual [&hellip;]","og_url":"https:\/\/www.dbi-services.com\/blog\/vm-linux-device-not-found-network-unreachable\/","og_site_name":"dbi Blog","article_published_time":"2016-04-12T08:01:23+00:00","article_modified_time":"2023-01-03T12:59:32+00:00","og_image":[{"width":508,"height":343,"url":"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2022\/04\/OVA-1.png","type":"image\/png"}],"author":"DevOps","twitter_card":"summary_large_image","twitter_misc":{"Written by":"DevOps","Est. reading time":"5 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/www.dbi-services.com\/blog\/vm-linux-device-not-found-network-unreachable\/#article","isPartOf":{"@id":"https:\/\/www.dbi-services.com\/blog\/vm-linux-device-not-found-network-unreachable\/"},"author":{"name":"DevOps","@id":"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/4cd1b5f8a3de93f05a16ab8d7d2b7735"},"headline":"VM Linux &#8211; Device not found : Network unreachable","datePublished":"2016-04-12T08:01:23+00:00","dateModified":"2023-01-03T12:59:32+00:00","mainEntityOfPage":{"@id":"https:\/\/www.dbi-services.com\/blog\/vm-linux-device-not-found-network-unreachable\/"},"wordCount":226,"commentCount":0,"image":{"@id":"https:\/\/www.dbi-services.com\/blog\/vm-linux-device-not-found-network-unreachable\/#primaryimage"},"thumbnailUrl":"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2022\/04\/OVA-1.png","keywords":["Linux\/UNIX","Network"],"articleSection":["Database Administration &amp; Monitoring","Operating systems"],"inLanguage":"en-US","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/www.dbi-services.com\/blog\/vm-linux-device-not-found-network-unreachable\/#respond"]}]},{"@type":"WebPage","@id":"https:\/\/www.dbi-services.com\/blog\/vm-linux-device-not-found-network-unreachable\/","url":"https:\/\/www.dbi-services.com\/blog\/vm-linux-device-not-found-network-unreachable\/","name":"VM Linux - Device not found : Network unreachable - dbi Blog","isPartOf":{"@id":"https:\/\/www.dbi-services.com\/blog\/#website"},"primaryImageOfPage":{"@id":"https:\/\/www.dbi-services.com\/blog\/vm-linux-device-not-found-network-unreachable\/#primaryimage"},"image":{"@id":"https:\/\/www.dbi-services.com\/blog\/vm-linux-device-not-found-network-unreachable\/#primaryimage"},"thumbnailUrl":"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2022\/04\/OVA-1.png","datePublished":"2016-04-12T08:01:23+00:00","dateModified":"2023-01-03T12:59:32+00:00","author":{"@id":"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/4cd1b5f8a3de93f05a16ab8d7d2b7735"},"breadcrumb":{"@id":"https:\/\/www.dbi-services.com\/blog\/vm-linux-device-not-found-network-unreachable\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.dbi-services.com\/blog\/vm-linux-device-not-found-network-unreachable\/"]}]},{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/www.dbi-services.com\/blog\/vm-linux-device-not-found-network-unreachable\/#primaryimage","url":"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2022\/04\/OVA-1.png","contentUrl":"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2022\/04\/OVA-1.png","width":508,"height":343},{"@type":"BreadcrumbList","@id":"https:\/\/www.dbi-services.com\/blog\/vm-linux-device-not-found-network-unreachable\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Accueil","item":"https:\/\/www.dbi-services.com\/blog\/"},{"@type":"ListItem","position":2,"name":"VM Linux &#8211; Device not found : Network unreachable"}]},{"@type":"WebSite","@id":"https:\/\/www.dbi-services.com\/blog\/#website","url":"https:\/\/www.dbi-services.com\/blog\/","name":"dbi Blog","description":"","potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/www.dbi-services.com\/blog\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-US"},{"@type":"Person","@id":"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/4cd1b5f8a3de93f05a16ab8d7d2b7735","name":"DevOps","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/secure.gravatar.com\/avatar\/cdd2dd7441774355062c0f0f68612296b059cd1e2ff6c7af0b15dba0ed64a85f?s=96&d=mm&r=g","url":"https:\/\/secure.gravatar.com\/avatar\/cdd2dd7441774355062c0f0f68612296b059cd1e2ff6c7af0b15dba0ed64a85f?s=96&d=mm&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/cdd2dd7441774355062c0f0f68612296b059cd1e2ff6c7af0b15dba0ed64a85f?s=96&d=mm&r=g","caption":"DevOps"},"url":"https:\/\/www.dbi-services.com\/blog\/author\/devops\/"}]}},"_links":{"self":[{"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts\/7431","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/users\/109"}],"replies":[{"embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/comments?post=7431"}],"version-history":[{"count":1,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts\/7431\/revisions"}],"predecessor-version":[{"id":21365,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts\/7431\/revisions\/21365"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/media\/7435"}],"wp:attachment":[{"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/media?parent=7431"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/categories?post=7431"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/tags?post=7431"},{"taxonomy":"type","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/type_dbi?post=7431"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}