Differences between revisions 6 and 7
Revision 6 as of 2008-07-14 21:54:05
Size: 10516
Editor: FranklinPiat
Comment: workaround for NM network detection.
Revision 7 as of 2009-03-16 03:32:51
Size: 10685
Editor: anonymous
Comment: converted to 1.6 markup
Deletions are marked like this. Additions are marked like this.
Line 9: Line 9:
 /!\ Microsoft Virtual PC is a {{{non-free}}} (proprietary) software. It isn't supported by Debian. It's probably wiser to use a free [:SystemVirtualization:Virtualization] tool.  /!\ Microsoft Virtual PC is a {{{non-free}}} (proprietary) software. It isn't supported by Debian. It's probably wiser to use a free [[SystemVirtualization|Virtualization]] tool.
Line 14: Line 14:
||||<tablestyle="margin-left:3em;width:90%">'''Core Components'''||<|10 style="text-align:right;border-style:none;vertical-align:top;"> [[ImageLink(photo.png,http://wiki.debian.org/WindowsServerHyperV#screenshot,width=267,height=230,alt=Screenshot)]] || ||||<tablestyle="margin-left:3em;width:90%">'''Core Components'''||<|10 style="text-align:right;border-style:none;vertical-align:top;"> [[http://wiki.debian.org/WindowsServerHyperV#screenshot|{{attachment:photo.png|Screenshot|width=267, height=230}}]] ||
Line 25: Line 25:
~-Legend :[[BR]] {OK} = OK ; {X} Unsupported(No Driver) ; /!\ = Error (Couldn't get it working); [?] Unknown, Not Test ; [-] Not-applicable [[BR]] {i} = Configuration Required; X-( = Only works with a proprietary driver-~ ~-Legend :<<BR>> {OK} = OK ; {X} Unsupported(No Driver) ; /!\ = Error (Couldn't get it working); [?] Unknown, Not Test ; [-] Not-applicable <<BR>> {i} = Configuration Required; X-( = Only works with a proprietary driver-~
Line 37: Line 37:
 * There is a [#step-by-step-installation step by step guide] on how to declare the VM in Hyper-V.  * There is a [[#step-by-step-installation|step by step guide]] on how to declare the VM in Hyper-V.
Line 40: Line 40:
[[Anchor(kernel-param)]] <<Anchor(kernel-param)>>
Line 48: Line 48:
The device (or driver) has no link detection. So DebPkg:network-manager will show an unplugged device (see bug Bug:490816 and gnome's [http://bugzilla.gnome.org/show_bug.cgi?id=542916 542916]).
  inline:InstallingDebianOn/VMs/MicrosoftVirtualPc2007/etch/networkmanager-bug.png
The device (or driver) has no link detection. So DebPkg:network-manager will show an unplugged device (see bug Bug:490816 and gnome's [[http://bugzilla.gnome.org/show_bug.cgi?id=542916|542916]]).
  {{attachment:InstallingDebianOn/VMs/MicrosoftVirtualPc2007/etch/networkmanager-bug.png}}
Line 52: Line 52:
 1. Left click on the nm-applet then click on "Wired Network" (each time you reboot) [[BR]] ''or''  1. Left click on the nm-applet then click on "Wired Network" (each time you reboot) <<BR>> ''or''
Line 65: Line 65:
 inline:no-mouse.gif  {{attachment:no-mouse.gif}}
Line 68: Line 68:
The Xorg server uses vesa driver (since Microsoft has developed a weird proprietary device [#pci-1414-5353 PCI:1414:5353]). The Xorg server uses vesa driver (since Microsoft has developed a weird proprietary device [[#pci-1414-5353|PCI:1414:5353]]).
Line 73: Line 73:
 * Under Lenny, the Emulated screen always pretend to be 1600x1200... which is anoying if you have a smaller screen (you can force it in attachment:xorg-lenny.conf.txt )  * Under Lenny, the Emulated screen always pretend to be 1600x1200... which is anoying if you have a smaller screen (you can force it in [[attachment:xorg-lenny.conf.txt]] )
Line 81: Line 81:
[[Anchor(step-by-step-installation)]] <<Anchor(step-by-step-installation)>>
Line 85: Line 85:
Pick the Installation that best fits you needs, from [http://www.debian.org/CD/]. I've picked the NetInst CD (at the time of writing, [http://cdimage.debian.org/debian-cd/4.0_r3/i386/iso-cd/debian-40r3-i386-netinst.iso debian-40r3-i386-netinst.iso]). Pick the Installation that best fits you needs, from [[http://www.debian.org/CD/]]. I've picked the NetInst CD (at the time of writing, [[http://cdimage.debian.org/debian-cd/4.0_r3/i386/iso-cd/debian-40r3-i386-netinst.iso|debian-40r3-i386-netinst.iso]]).
Line 88: Line 88:
. {i} If you haven't installed Hyper-V, check [#install-hyperv Installing Hyper-V] below. . {i} If you haven't installed Hyper-V, check [[#install-hyperv|Installing Hyper-V]] below.
Line 91: Line 91:
 * The first time you run Hyper-V, you need to accept their specific attachment:EULA.txt:
 inline:EULA.gif

 inline:Hyper-V_Console.gif
 * The first time you run Hyper-V, you need to accept their specific [[attachment:EULA.txt]]:
 {{attachment:EULA.gif}}

 {{attachment:Hyper-V_Console.gif}}
Line 97: Line 97:
 inline:wizard_1.gif  {{attachment:wizard_1.gif}}
Line 99: Line 99:
 inline:wizard2_name.gif  {{attachment:wizard2_name.gif}}
Line 101: Line 101:
 inline:wizard3_ram.gif  {{attachment:wizard3_ram.gif}}
Line 103: Line 103:
 inline:wizard4_net.gif  {{attachment:wizard4_net.gif}}
Line 105: Line 105:
 inline:wizard5_hd.gif  {{attachment:wizard5_hd.gif}}
Line 107: Line 107:
 inline:wizard6a_install_from_iso.gif  {{attachment:wizard6a_install_from_iso.gif}}
Line 109: Line 109:
 inline:wizard7a_summary.gif  {{attachment:wizard7a_summary.gif}}
Line 120: Line 120:
 inline:virtual-network_1-add.gif  {{attachment:virtual-network_1-add.gif}}
Line 122: Line 122:
 inline:virtual-network_2-property.gif  {{attachment:virtual-network_2-property.gif}}
Line 130: Line 130:
 inline:property_add-legacy-nework_1.gif  {{attachment:property_add-legacy-nework_1.gif}}
Line 132: Line 132:
 inline:property_add-legacy-nework_2-bind.gif  {{attachment:property_add-legacy-nework_2-bind.gif}}
Line 136: Line 136:
[[Anchor(install-hyperv)]] <<Anchor(install-hyperv)>>
Line 141: Line 141:
 * Step-by-Step Guide to Getting Started with Hyper-V [[BR]] ~-[http://go.microsoft.com/fwlink/?LinkId=105293]-~
 * How to Install Windows Server 2008 Hyper-V [[BR]] ~-[http://www.microsoft.com/windowsserver2008/en/us/hyperv-install.aspx]-~

Microsoft has already provided an update. Apparently, you must install it to have a supported Hyper-V installation ([http://www.microsoft.com/downloads/details.aspx?FamilyID=F3AB3D4B-63C8-4424-A738-BADED34D24ED&displaylang=en Update for Windows Server 2008 x64 Edition (KB950050)])

''Note that for some odd reasons, Microsoft doesn't provides a version of Hyper-V under 32bit platform (even though it [http://www.microsoft.com/windowsserver2008/en/us/scalability-ent.aspx can use 64Gb of RAM]).''
 * Step-by-Step Guide to Getting Started with Hyper-V <<BR>> ~-[[http://go.microsoft.com/fwlink/?LinkId=105293]]-~
 * How to Install Windows Server 2008 Hyper-V <<BR>> ~-[[http://www.microsoft.com/windowsserver2008/en/us/hyperv-install.aspx]]-~

Microsoft has already provided an update. Apparently, you must install it to have a supported Hyper-V installation ([[http://www.microsoft.com/downloads/details.aspx?FamilyID=F3AB3D4B-63C8-4424-A738-BADED34D24ED&displaylang=en|Update for Windows Server 2008 x64 Edition (KB950050)]])

''Note that for some odd reasons, Microsoft doesn't provides a version of Hyper-V under 32bit platform (even though it [[http://www.microsoft.com/windowsserver2008/en/us/scalability-ent.aspx|can use 64Gb of RAM]]).''
Line 149: Line 149:
[[Anchor(screenshot)]]
 inline:logon-screen.png
<<Anchor(screenshot)>>
 {{attachment:logon-screen.png}}
Line 166: Line 166:
[[Anchor(pci-1414-5353)]] <<Anchor(pci-1414-5353)>>
Line 180: Line 180:
You can also have a look at attachment:Xorg-lenny.log.txt . You can also have a look at [[attachment:Xorg-lenny.log.txt]] .
Line 186: Line 186:
 * attachment:debian-etch-hyperv6.dmidecode.txt  * [[attachment:debian-etch-hyperv6.dmidecode.txt]]
Line 191: Line 191:
  * Commercial Product page [[BR]] ~-[http://www.microsoft.com/windowsserver2008/en/us/virtualization-consolidation.aspx]-~
  * Technet Page [[BR]] ~-[http://go.microsoft.com/fwlink/?LinkId=48557]-~
 * ["InstallingDebianOn/VMs/MicrosoftVirtualPc2007/etch"]
 * [wiki:DebPkg:qemu Qemu]'s qemu-img can convert [http://www.microsoft.com/technet/virtualserver/downloads/vhdspec.mspx vhd] images.
  * Commercial Product page <<BR>> ~-[[http://www.microsoft.com/windowsserver2008/en/us/virtualization-consolidation.aspx]]-~
  * Technet Page <<BR>> ~-[[http://go.microsoft.com/fwlink/?LinkId=48557]]-~
 * [[InstallingDebianOn/VMs/MicrosoftVirtualPc2007/etch]]
 * [[DebPkg:qemu|Qemu]]'s qemu-img can convert [[http://www.microsoft.com/technet/virtualserver/downloads/vhdspec.mspx|vhd]] images.

Running Debian in Windows Server's Hyper-V

This page explain how to use Debian under Microsoft Hyper-V (Windows Server 2008).

  • /!\ Microsoft Virtual PC is a non-free (proprietary) software. It isn't supported by Debian. It's probably wiser to use a free Virtualization tool.

Overall Status

Core Components

Screenshot

Boot Standard Kernel:

{OK}

LAN network card:

{OK}

Detect CD/DVD:

{OK}

Detect hard drives:

{OK}

Extra Features

Xorg

{OK}

- OpenGL

[?]

- Resize-and-Rotate(randr)

/!\

Sound

[-]

Mouse

{OK}

Legend :
{OK} = OK ; {X} Unsupported(No Driver) ; /!\ = Error (Couldn't get it working); [?] Unknown, Not Test ; [-] Not-applicable
{i} = Configuration Required; X-( = Only works with a proprietary driver

Important Note

  • Passing vga=XXX may cause some problem when you switch from X11 to console.
  • The display is drawn very slowly during the installation (under Lenny, for newt only, not for installgui). But the installation process itself isn't longer

Configuration

  • There is a step by step guide on how to declare the VM in Hyper-V.

  • Here are the configuration / compatibility notes on how to install Debian.

Kernel Parameters

  • None required, currently

Networking

The emulated device is a "Digital Equipment Corporation DECchip 21140 [FasterNet]" PCI id:1011:0009.

The device (or driver) has no link detection. So network-manager will show an unplugged device (see bug 490816 and gnome's 542916).

  • InstallingDebianOn/VMs/MicrosoftVirtualPc2007/etch/networkmanager-bug.png

Workarounds : either

  1. Left click on the nm-applet then click on "Wired Network" (each time you reboot)
    or

  2. Create a the file /etc/default/NetworkManager to prevent NetworkManager from disabling the interface :

    #Exit to prevent NetworkManager from running
    exit

Mouse

The mouse is working well. (the scroll button doesn't).

However, you can't use use the mouse inside your machine if you connect to the server using RDP, unless you install the Integration services... Which can't be downloaded for free, you need to pay for extra support. (The error message says "Mouse not captured in Remote Desktop session"). It looks like :

  1. Microsoft only wants you to used blessed guest operating systems (like Windows and Suse)
  2. Microsoft wants you to use their Hyper-V Management console (only available under Windows !)

    no-mouse.gif

Display Adapter / Video

The Xorg server uses vesa driver (since Microsoft has developed a weird proprietary device PCI:1414:5353).

It works quite well under both Etch and Lenny (Xorg 7.3). However:

  • Using xrandr causes the Xserver to restart.
  • vga= works, but you can't switch between X11 and the console (it causes the system to crash).
  • Under Lenny, the Emulated screen always pretend to be 1600x1200... which is anoying if you have a smaller screen (you can force it in xorg-lenny.conf.txt )

Audio

Hyper-V doesn't seems to provide audio emulation, at all.

Power Management

  • (not covered... use Hyper-V's suspend feature.)

Step by Step Installation

Download Debian ISO image

Pick the Installation that best fits you needs, from http://www.debian.org/CD/. I've picked the NetInst CD (at the time of writing, debian-40r3-i386-netinst.iso).

Create the VM

. {i} If you haven't installed Hyper-V, check Installing Hyper-V below.

  • Launch "Microsoft Virtual PC" in Start Menu > Administrative Tools > Hyper-V Manager.

  • The first time you run Hyper-V, you need to accept their specific EULA.txt: EULA.gif

    Hyper-V_Console.gif

  • Select the your server (on the left pane)
  • Go to Menu > Action > New > Virtual Machine. wizard_1.gif

  • Choose a name for your Virual Machine

    wizard2_name.gif

  • Select the amount or RAM for the Vritual Machine (128Mb is enough for text only. 512Mb is recommended for GUI/Desktop).

    wizard3_ram.gif

  • Select the Network you have created during Hyper-V initial configuration (If the drop down menu is empty, clse the wizard, and go to Menu > Action > Virtual Network Manager). wizard4_net.gif

  • Select a name and location for the disk image. You can change the maximum disk space allocated, but it isn't important since the space is allocated as needed. (Don't go below 6Gb unless you know exaclty what your are doing, not to shoot a bullet in your own foot).

    wizard5_hd.gif

  • You can select the installation media for your VM

    wizard6a_install_from_iso.gif

  • Review the summary, and click ok (or back ;).

    wizard7a_summary.gif

Configure Networking

Enabling networking requires two steps:

  1. Add a virtual switch
  2. Add a (so called) Legacy Network Adapter (The other one, named Network Adapter requires to install Microsoft's Integration services).

Add Virtual Network

If you don't have one yet, you have to add a virtual network (a kind of virtual switch).

  • In "Hyper-V Manager", go to menu Action > Virtual Network Manager.

  • Select "External" network, then click on "Add".

    virtual-network_1-add.gif

  • Give it a name, like My Virtual Network. Then select the pyhsical network interface that it should be connected to (i.e bridged). virtual-network_2-property.gif

Add a Network Adapter

The installation wizard don't offer to a a network installation, so you have to add it manually (!) :

  • Select your on Virtual machine in "Hyper-V Manager", then select Settings.
  • On the left panel, select "Add Hardware"
  • Select Legacy Network Adapter. property_add-legacy-nework_1.gif

  • Then select the virtual network (i.e switch) to which the adapter should be connected. property_add-legacy-nework_2-bind.gif

That's it.

Installing Hyper-V

If you are reading this page, you probably already have Hyper-V installed ! for the other, you should follow Microsoft's instructions :

Microsoft has already provided an update. Apparently, you must install it to have a supported Hyper-V installation (Update for Windows Server 2008 x64 Edition (KB950050))

Note that for some odd reasons, Microsoft doesn't provides a version of Hyper-V under 32bit platform (even though it can use 64Gb of RAM).

That's It !

  • logon-screen.png


System Summary

lspci

$lspci -nn
00:00.0 Host bridge [0600]: Intel Corporation 440BX/ZX/DX - 82443BX/ZX/DX Host bridge (AGP disabled) [8086:7192] (rev 03)
00:07.0 ISA bridge [0601]: Intel Corporation 82371AB/EB/MB PIIX4 ISA [8086:7110] (rev 01)
00:07.1 IDE interface [0101]: Intel Corporation 82371AB/EB/MB PIIX4 IDE [8086:7111] (rev 01)
00:07.3 Bridge [0680]: Intel Corporation 82371AB/EB/MB PIIX4 ACPI [8086:7113] (rev 02)
00:08.0 VGA compatible controller [0300]: Microsoft Corporation Unknown device [1414:5353]
00:0a.0 Ethernet controller [0200]: Digital Equipment Corporation DECchip 21140 [FasterNet] [1011:0009] (rev 20)

PCI 1414:5353 VGA device

Here's are two quotes from Microsoft Integration Service's s3cap.inf regarding the device 1414:5353 :

  • This is the INF file for installing the Hyper-V VGA Cap driver

  • Microsoft Emulated S3 Device Cap.

and a compulsory lspci -d 1414:5353 -vvv output :

00:08.0 VGA compatible controller: Microsoft Corporation Unknown device 5353 (prog-if 00 [VGA])
        Control: I/O+ Mem+ BusMaster+ SpecCycle+ MemWINV+ VGASnoop- ParErr- Stepping- SERR+ FastB2B-
        Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-
        Latency: 0
        Region 0: Memory at f8000000 (32-bit, non-prefetchable) [size=64M]

You can also have a look at Xorg-lenny.log.txt .

lsusb

None

Attachements

Credits


keywords: Viridian