Differences between revisions 3 and 4
Revision 3 as of 2008-07-13 11:50:18
Size: 8586
Editor: FranklinPiat
Comment: progessing...
Revision 4 as of 2008-07-13 17:34:47
Size: 10143
Editor: FranklinPiat
Comment: testing... testing ;)
Deletions are marked like this. Additions are marked like this.
Line 4: Line 4:
This page explain how to use Debian under Microsoft Hyper-V (Windows Server 2008).
 
## [[TableOfContents(2)]]
Line 9: Line 6:

This page explain how to use Debian under Microsoft Hyper-V (Windows Server 2008).
Line 30: Line 29:
 ''None, currently''  * 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}}}).
Line 36: Line 37:
Passing vga=XXX may cause some problem when you switch from X11 to console.
Line 38: Line 38:
 ''None required, currently''
Line 47: Line 48:

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 operating systems (like Windows and Suse)
 2. Microsoft wants you to use their Hyper-V Management console (only available under Windows !)
 inline:no-mouse.gif

==== Display Adapter / Video ====
The Xorg server uses vesa driver (since Microsoft has developed a weird proprietary device [#pci-1414-5353 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 attachment:xorg-lenny.conf.txt )
Line 87: Line 101:
 2. Add a (so called) ''Legacy Network Adapter'' (The other one, named ''Network Adapter'' being some Microsoft shit that requires to install Microsoft's ''Integration services'').  2. Add a (so called) ''Legacy Network Adapter'' (The other one, named ''Network Adapter'' requires to install Microsoft's ''Integration services'').
Line 136: Line 150:
}}}
Line 137: Line 152:
$lspci -s 00:08.0 -vvv [[Anchor(pci-1414-5353)]]
=== 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 :
{{{
Line 144: Line 166:
You can also have a look at attachment:Xorg-lenny.log.txt .
Line 165: Line 189:
keywords: Viridian

Running Debian in Windows Server's Hyper-V

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

Overall Status

Core Components

?ImageLink(photo.png,http://wiki.debian.org/WindowsServerHyperV#screenshot,width=267,height=230,alt=Screenshot)

Boot Standard Kernel:

{OK}

LAN network card:

{OK}

Detect CD/DVD:

{OK}

Detect hard drives:

{OK}

Extra Features

Xorg

{i}

- OpenGL

[?]

- Resize-and-Rotate(randr)

{OK}

Sound

n.a

Mouse

{OK}

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

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).

Configuration

?Anchor(kernel-param)

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. Even though it's working ! (known upstream by Gnome as bug [http://bugzilla.gnome.org/show_bug.cgi?id=418745 #418745]). ?BR If you lose Network connection then left click on the nm-applet then click on "Wired Network" :

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

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 operating systems (like Windows and Suse)
  2. Microsoft wants you to use their Hyper-V Management console (only available under Windows !) inline:no-mouse.gif

Display Adapter / Video

The Xorg server uses vesa driver (since Microsoft has developed a weird proprietary device [#pci-1414-5353 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 attachment: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.)

?Anchor(step-by-step-installation)

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, [http://cdimage.debian.org/debian-cd/4.0_r3/i386/iso-cd/debian-40r3-i386-netinst.iso debian-40r3-i386-netinst.iso]).

Create the VM

. {i} If you haven't installed Hyper-V, check [#install-hyperv 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 attachment:EULA.txt: inline:EULA.gif inline:Hyper-V_Console.gif
  • Select the your server (on the left pane)
  • Go to Menu > Action > New > Virtual Machine. inline:wizard_1.gif

  • Choose a name for your Virual Machine inline:wizard2_name.gif
  • Select the amount or RAM for the Vritual Machine (128Mb is enough for text only. 512Mb is recommended for GUI/Desktop). inline: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). inline: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). inline:wizard5_hd.gif
  • You can select the installation media for your VM inline:wizard6a_install_from_iso.gif
  • Review the summary, and click ok (or back ;). inline: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". inline: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). inline: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. inline:property_add-legacy-nework_1.gif

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

inline:foo That's it.

?Anchor(install-hyperv)

Installing Hyper-V

If you are reading this page, you probably already have Hyper-V installed ! for the other, you should follow Microsoft's instruction : See also Microsoft's Step-by-Step Guide to Getting Started with Hyper-V ?BR [http://technet2.microsoft.com/WindowsServer2008/en/library/c513e254-adf1-400e-8fcb-c1aec8a029311033.mspx#BKMK_step3]-~

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]).

That's It !

?Anchor(screenshot)

  • inline: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)

?Anchor(pci-1414-5353)

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 attachment:Xorg-lenny.log.txt .

lsusb

None

Attachements

  • attachment:debian-etch-hyperv6.dmidecode.txt

Credits


keywords: Viridian