{"id":9822,"date":"2012-06-29T18:27:56","date_gmt":"2012-06-29T16:27:56","guid":{"rendered":"http:\/\/www.borncity.com\/blog\/?p=9822"},"modified":"2024-01-05T17:27:53","modified_gmt":"2024-01-05T16:27:53","slug":"windows-8-using-hyper-v-on-non-slat-cpus","status":"publish","type":"post","link":"https:\/\/borncity.com\/blog\/2012\/06\/29\/windows-8-using-hyper-v-on-non-slat-cpus\/","title":{"rendered":"Windows 8: Using Hyper-V on non SLAT CPUs?"},"content":{"rendered":"<p><img loading=\"lazy\" decoding=\"async\" style=\"margin: 0px 10px 0px 0px; display: inline;\" src=\"http:\/\/web.archive.org\/web\/20150913035047\/http:\/\/img855.imageshack.us\/img855\/6201\/winla.jpg\" alt=\"\" width=\"58\" height=\"58\" align=\"left\" \/>[<a href=\"https:\/\/borncity.com\/blog\/2012\/06\/29\/windows-8-luft-hyper-v-auf-nicht-slat-fhigen-cpus\/\">German edition<\/a>] Windows 8 Pro and Enterprise are shipped with Hyper-V 3.0 in 64 Bit versions. But a CPU with SLAT support is mandatory (see my German article [<a href=\"https:\/\/borncity.com\/blog\/2011\/09\/08\/windows-8-hyper-v-braucht-slat-fhige-cpus\/comment-page-1\/#comment-6371\">2<\/a>]). Otherwise, only the Client (Hyper-V-Manager) is useable, whilst the Hypervisor (Hyper-V-Platform) will be blocked. Recently there was a rumor [<a href=\"https:\/\/web.archive.org\/web\/20120603051715\/http:\/\/social.technet.microsoft.com\/Forums\/en\/w8itprovirt\/thread\/0c569506-3232-4a9d-ae72-67b642dc7951\" target=\"_blank\" rel=\"noopener noreferrer\">3,<\/a> <a href=\"https:\/\/web.archive.org\/web\/20151209154549\/http:\/\/blogs.msdn.com\/b\/virtual_pc_guy\/archive\/2012\/06\/01\/hyper-v-on-windows-server-2012-rc-information.aspx\" target=\"_blank\" rel=\"noopener noreferrer\">4<\/a>], that Hyper-V-Platform will be useable in Windows 8 on non SLAT CPUs. Well, I have tested it.<\/p>\n<p><!--more--><\/p>\n<h3>Some theory and a rumor<\/h3>\n<p><img loading=\"lazy\" decoding=\"async\" src=\"https:\/\/ssl-vg03.met.vgwort.de\/na\/7ac8d642de014f28858ff7e524d2e871\" alt=\"\" width=\"1\" height=\"1\" \/>Hyper V 3.0 shipped with Windows 8 consists of Hyper-V-Manager and Hyper-V-Platform. Hyper-V-Manager will run as a front end also on 32 bit environment and doesn't require SLAT support. The Hypervisor, called Hyper-V-Platform, is restricted to 64 Bit Windows 8 versions and requires a CPU supporting virtualization support (Intel VT-X, AMD-V) and also Second Level Address Support (SLAT) \u2013 see also my Article [<a href=\"https:\/\/borncity.com\/blog\/2011\/09\/08\/windows-8-hyper-v-braucht-slat-fhige-cpus\/comment-page-1\/#comment-6371\">1<\/a>].<\/p>\n<p>In [<a href=\"https:\/\/web.archive.org\/web\/20120603051715\/http:\/\/social.technet.microsoft.com\/Forums\/en\/w8itprovirt\/thread\/0c569506-3232-4a9d-ae72-67b642dc7951\" target=\"_blank\" rel=\"noopener noreferrer\">3,<\/a> <a href=\"https:\/\/web.archive.org\/web\/20151209154549\/http:\/\/blogs.msdn.com\/b\/virtual_pc_guy\/archive\/2012\/06\/01\/hyper-v-on-windows-server-2012-rc-information.aspx\" target=\"_blank\" rel=\"noopener noreferrer\">4<\/a>] some people mentioned, that only the GUI of Windows Features will check a CPU's Hyper-V support. If that isn't available, activation of Hyper-V-Platform will be blocked (grayed out). But there should be a way, to add this feature using DISM \u2013 and afterward Hyper-V-Platform should be useable\u2026<\/p>\n<h3>Test it! Here we go \u2013 Part 1<\/h3>\n<p>After Andr\u00e9 from WinVistaSide.de left a comment about this topic, I decided to try a proof of concept. I was eager, to see, how Hyper-V will work, because I haven't a computer with a SLAT supported CPU anymore. A Dell Inspiron One 2330 with Intel iCore i7-CPU, I've had for test purposes, was send back to Dell a while ago. Currently I'm using a system with Intel Q8300 Quad Core CPU, that supports Intel VT-X.<\/p>\n<p>Because this machine runs with Windows 7, I created a 64 Bit Windows To Go from Windows 8 Release Preview [<a href=\"https:\/\/borncity.com\/blog\/2012\/06\/02\/creating-windows-to-go-from-windows-8-release-preview\/\">1<\/a>]. Then I booted Windows To Go, went to Windows 8 Desktop and entered the administrative command prompt (via hover \"Start\" button). Then I activated all Hyper-V features using the following command:<\/p>\n<p><em>DISM \/online \/Enable-Feature:Microsoft-Hyper-V-All<\/em><\/p>\n<p>DISM confirmed the successful execution of that command and asked for a reboot. The system started to reconfigure and booted twice. But during 2nd boot, the screen went black. Then I booted the system again, but this time with a distinct Windows 8 installation, went to an administrative command prompt and used the following command to deactivate Hyper-V.<\/p>\n<p><em>DISM \/Image:R:\\ \/Disable-Feature \/FeatureName:Microsoft-Hyper-V-All<\/em><\/p>\n<p>After reboot, Windows 8 worked again. I tried that twice, always ending with a black screen. Once I tried to boot with F8 in secure mode. I was able to see the secure desktop and in Windows features I could see, that Hyper-V-Platform was activated. And I was able to invoke Hyper-V-Manager and configure a VM with a preinstalled Windows Server 2008. But I wasn't able to run this VM \u2013 I got a notification, that this wasn't supported in secure mode.<\/p>\n<p><a href=\"https:\/\/web.archive.org\/web\/20191210151252\/http:\/\/b85.imgup.net\/Abges0151d4.jpg\" target=\"_blank\" rel=\"noopener noreferrer\"><img loading=\"lazy\" decoding=\"async\" src=\"https:\/\/web.archive.org\/web\/20191210151252\/http:\/\/b85.imgup.net\/Abges0151d4.jpg\" alt=\"\" width=\"573\" height=\"430\" \/><\/a><\/p>\n<h3><strong>A 2nd test with a native Windows 8 RP (64 Bit) install<\/strong><\/h3>\n<p>Then I installed Windows 8 RP (32-Bit-Pro-Version) on that machine. As estimated, I wasn't able to activate Hyper-V-Platform in <em>Activate or deactivate Windows features <\/em>(see sceenshot of my German dialog box), because the option was grayed out.<\/p>\n<p><img loading=\"lazy\" decoding=\"async\" src=\"https:\/\/borncity.com\/blog\/wp-content\/uploads\/2012\/06\/Features01.jpg\" alt=\"Gesperrter Hyper-V-Plattform-Eintrag\" width=\"412\" height=\"362\" \/><\/p>\n<p>Then I invoked an administrative command prompt from Windows desktop and entered DISM-command shown below:<\/p>\n<p><img loading=\"lazy\" decoding=\"async\" src=\"https:\/\/borncity.com\/blog\/wp-content\/uploads\/2012\/06\/Dos01.jpg\" alt=\"Eingabeaufforderung\" width=\"552\" height=\"280\" \/><\/p>\n<p>The command was successfully processed and the system rebooted. After two boots, Windows 8 was able to launch and I controlled feature settings (which was set as shown below).<\/p>\n<p><img loading=\"lazy\" decoding=\"async\" src=\"https:\/\/borncity.com\/blog\/wp-content\/uploads\/2012\/06\/Features021.jpg\" alt=\"Windows-Features mit Hyper-V\" width=\"402\" height=\"353\" \/><\/p>\n<p>Then I invoked Hyper-V-Manager via Start screen \u2013 and suddenly I was able, to configure a virtual machine.<\/p>\n<p><a href=\"https:\/\/borncity.com\/blog\/wp-content\/uploads\/2012\/06\/Hyper-V-01.jpg\" target=\"_blank\" rel=\"noopener noreferrer\"><img loading=\"lazy\" decoding=\"async\" src=\"https:\/\/borncity.com\/blog\/wp-content\/uploads\/2012\/06\/Hyper-V-01.jpg\" alt=\"Hyper-V-Manager\" width=\"569\" height=\"384\" \/><\/a><\/p>\n<p>And after clicking the <em>connect<\/em> button, I could see the following window.<\/p>\n<p><a href=\"https:\/\/borncity.com\/blog\/wp-content\/uploads\/2012\/06\/Hyper-V-02.jpg\"><img decoding=\"async\" src=\"https:\/\/borncity.com\/blog\/wp-content\/uploads\/2012\/06\/Hyper-V-02.jpg\" alt=\"Hyper-V-Gastbetriebssystem-Fenster\" width=\"590\" \/><\/a><\/p>\n<p>But I wasn't able to run the VM using the <em>run <\/em>button because of an error dialog, informing me, that the CPU doesn't support virtualization (Intel Q8300 supports VT-X, but no SLAT).<\/p>\n<p><a href=\"https:\/\/borncity.com\/blog\/wp-content\/uploads\/2012\/06\/Hyper-V-03.jpg\" target=\"_blank\" rel=\"noopener noreferrer\"><img decoding=\"async\" src=\"https:\/\/borncity.com\/blog\/wp-content\/uploads\/2012\/06\/Hyper-V-03.jpg\" alt=\"Fehler beim Hyper-V-Start\" width=\"590\" \/><\/a><\/p>\n<p>I tried to inspect Hyper-V services. But all Hyper-V services stalled (obviously due to lack of SLAT support).<\/p>\n<h3>Will the right BCD entry helps?<\/h3>\n<p>Andr\u00e9 from WinVistaSide.de suggested to enter the following command in administrative command prompt (see <a href=\"https:\/\/web.archive.org\/web\/20150226125944\/http:\/\/support.microsoft.com\/kb\/954356\" target=\"_blank\" rel=\"noopener noreferrer\">also<\/a>).<\/p>\n<p>bcdedit \/set {current} hypervisorlaunchtype auto<\/p>\n<p>After rebooting my system I tried Hyper-V-Manager again. My attempt, to invoke a VM vie Hyper-V platform resulted in the same error message. I came to the conclusion, that the rumor in the net about running Hyper-V on non SLAT CPUs was never tested with Windows 8 Release Preview.<\/p>\n<h3>But there is a positive result at least!<\/h3>\n<p>After adding a Hyper-V role to my Windows 8 client, I wasn't able to run the hypervisor. But I was at least I was able to configure VMs in Hyper-V-Manager (because a Hyper-V-Server was already detected and shown). Maybe I will use Windows Server 2008 R2 or 2012 (which didn't <a href=\"http:\/\/web.archive.org\/web\/20161126182404\/http:\/\/www.aidanfinn.com\/?p=12679\" target=\"_blank\" rel=\"noopener noreferrer\">require SLAT support for Hyper-V<\/a>) to run a VM \u2013 and use a Windows 8 client to connect to this server.<\/p>\n<p><strong>Links:<\/strong><br \/>\n1: <a href=\"https:\/\/borncity.com\/blog\/2012\/06\/02\/creating-windows-to-go-from-windows-8-release-preview\/\">Windows To Go with Windows 8 Release Preview<\/a><br \/>\n2: <a href=\"https:\/\/borncity.com\/blog\/2011\/09\/08\/windows-8-hyper-v-braucht-slat-fhige-cpus\/comment-page-1\/#comment-6371\">Windows 8: Hyper-V braucht SLAT f\u00e4hige CPUs<\/a><br \/>\n3: <a href=\"https:\/\/web.archive.org\/web\/20120603051715\/http:\/\/social.technet.microsoft.com\/Forums\/en\/w8itprovirt\/thread\/0c569506-3232-4a9d-ae72-67b642dc7951\" target=\"_blank\" rel=\"noopener noreferrer\">Technet-Diskussion: Hyper-V ohne SLAT<\/a><br \/>\n4: <a href=\"https:\/\/web.archive.org\/web\/20151209154549\/http:\/\/blogs.msdn.com\/b\/virtual_pc_guy\/archive\/2012\/06\/01\/hyper-v-on-windows-server-2012-rc-information.aspx\" target=\"_blank\" rel=\"noopener noreferrer\">Artikel zu Hyper-V auf Windows Server 2012<\/a><br \/>\n5: <a href=\"http:\/\/www.windowspro.de\/tipp\/hyper-v-voruebergehend-abschalten-und-wieder-aktivieren\" target=\"_blank\" rel=\"noopener noreferrer\">Hyper-V vor\u00fcbergehend abschalten<\/a><br \/>\n6: <a href=\"https:\/\/web.archive.org\/web\/20150506054759\/http:\/\/blogs.technet.com:80\/b\/keithcombs\/archive\/2009\/12\/08\/hypervisorlaunchtype-not-set-after-bcd-changes-here-is-the-fix.aspx\" target=\"_blank\" rel=\"noopener noreferrer\">Technet-Article about Hyper-V<\/a><\/p>\n<p><strong>Similar Artikle (German):<br \/>\n<\/strong>i: <a href=\"https:\/\/borncity.com\/blog\/2012\/04\/14\/windows-8-hyper-v-im-test-teil-i\/\">Windows 8: Hyper-V im Test<\/a> \u2013 Teil I (Hyper-V einrichten)<br \/>\nii: <a href=\"https:\/\/borncity.com\/blog\/2012\/04\/15\/windows-8-hyper-v-im-test-teil-ii\/\">Windows 8: Hyper-V im Test<\/a> \u2013 Teil II (Host vorbereiten)<br \/>\niii: <a href=\"https:\/\/borncity.com\/blog\/2012\/04\/16\/windows-8-hyper-v-im-test-teil-iii\/\">Windows 8: Hyper-V im Test<\/a> \u2013 Teil III (VMs aufsetzen)<br \/>\niv: <a href=\"https:\/\/borncity.com\/blog\/2012\/04\/17\/windows-8-hyper-v-im-test-teil-iv\/\">Windows 8: Hyper-V im Test<\/a> \u2013 Teil IV (VMs einsetzen)<\/p>\n","protected":false},"excerpt":{"rendered":"<p>[German edition] Windows 8 Pro and Enterprise are shipped with Hyper-V 3.0 in 64 Bit versions. But a CPU with SLAT support is mandatory (see my German article [2]). Otherwise, only the Client (Hyper-V-Manager) is useable, whilst the Hypervisor (Hyper-V-Platform) &hellip; <a href=\"https:\/\/borncity.com\/blog\/2012\/06\/29\/windows-8-using-hyper-v-on-non-slat-cpus\/\">Weiterlesen <span class=\"meta-nav\">&rarr;<\/span><\/a><\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[14],"tags":[2242,1169,1471,4336],"class_list":["post-9822","post","type-post","status-publish","format-standard","hentry","category-virtualisierung","tag-dism","tag-hyper-v","tag-slat","tag-windows-8-beta"],"_links":{"self":[{"href":"https:\/\/borncity.com\/blog\/wp-json\/wp\/v2\/posts\/9822","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/borncity.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/borncity.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/borncity.com\/blog\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/borncity.com\/blog\/wp-json\/wp\/v2\/comments?post=9822"}],"version-history":[{"count":0,"href":"https:\/\/borncity.com\/blog\/wp-json\/wp\/v2\/posts\/9822\/revisions"}],"wp:attachment":[{"href":"https:\/\/borncity.com\/blog\/wp-json\/wp\/v2\/media?parent=9822"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/borncity.com\/blog\/wp-json\/wp\/v2\/categories?post=9822"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/borncity.com\/blog\/wp-json\/wp\/v2\/tags?post=9822"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}