add categories, add todo
better suggestion for where to rename the page
|Deletions are marked like this.||Additions are marked like this.|
|Line 209:||Line 209:|
|'''TODO:''' rename to [[DebianOn/WindowsServerHyperV]]||'''TODO:''' rename to [[InstallingDebianOn/Microsoft/WindowsServerHyperV]]|
Running Debian in Windows Server's Hyper-V
This page explain how to use Debian under Microsoft Hyper-V (Windows Server 2008/R2).
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.
Boot Standard Kernel:
LAN network card:
Detect hard drives:
= OK ; Unsupported(No Driver) ; = Error (Couldn't get it working); [?] Unknown, Not Test ; [-] Not-applicable
= Configuration Required; = Only works with a proprietary driver
- 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
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.
None required, currently
The emulated device is a "Digital Equipment Corporation DECchip 21140 [FasterNet]" PCI id:1011:0009.
Workarounds : either
Left click on the nm-applet then click on "Wired Network" (each time you reboot)
Create a the file /etc/default/NetworkManager to prevent NetworkManager from disabling the interface :
#Exit to prevent NetworkManager from running exit
Solution: Build and install the "Linux Integration Services" drivers, freely available from Microsoft. The result will be that a non-legacy network adapter can be added from the Hyper-V Manager, vastly improving speed & functionality. However, this procedure is non-trivial because:
- Microsoft only supports certain guest operating systems (like Windows, Suse and flavors of Red Hat)
- Microsoft has alternated between providing and not providing non-official support for the Linux IC drivers. The drivers were bundled with kernel version 2.6.32, but are slated for removal by 2.6.35.
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. (The error message says "Mouse not captured in Remote Desktop session"). This has to do with the Debian install not being aware that it is dealing with an "enlightened" virtualized mouse. In order to get this "enlightened" mouse, you will need to build and install the "inputvsc" driver from the Citrix Satori Project. However, the inputvsc driver requires the "Linux Integration Services" drivers, see discussion above, to be built and installed.
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 )
Hyper-V doesn't seems to provide audio emulation, at all.
- (not covered... use Hyper-V's suspend feature.)
Step by Step Installation
Download Debian ISO image
Create the VM
. 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:
- Select the your server (on the left pane)
Go to Menu > Action > New > Virtual Machine.
- Choose a name for your Virual Machine
- Select the amount or RAM for the Vritual Machine (128Mb is enough for text only. 512Mb is recommended for GUI/Desktop).
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).
- 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).
- You can select the installation media for your VM
- Review the summary, and click ok (or back ;).
Enabling networking requires two steps:
- Add a virtual switch
Add a (so called) Legacy Network Adapter (The other one, named Network Adapter requires installation of Microsoft's free 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".
Give it a name, like My Virtual Network. Then select the pyhsical network interface that it should be connected to (i.e bridged).
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.
Then select the virtual network (i.e switch) to which the adapter should be connected.
If you are reading this page, you probably already have Hyper-V installed ! for the other, you should follow Microsoft's instructions :
Step-by-Step Guide to Getting Started with Hyper-V
How to Install Windows Server 2008 Hyper-V
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 !
$lspci -nn 00:00.0 Host bridge : Intel Corporation 440BX/ZX/DX - 82443BX/ZX/DX Host bridge (AGP disabled) [8086:7192] (rev 03) 00:07.0 ISA bridge : Intel Corporation 82371AB/EB/MB PIIX4 ISA [8086:7110] (rev 01) 00:07.1 IDE interface : Intel Corporation 82371AB/EB/MB PIIX4 IDE [8086:7111] (rev 01) 00:07.3 Bridge : Intel Corporation 82371AB/EB/MB PIIX4 ACPI [8086:7113] (rev 02) 00:08.0 VGA compatible controller : Microsoft Corporation Unknown device [1414:5353] 00:0a.0 Ethernet controller : 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 .
- Microsoft Hyper-V front pages
Commercial Product page
Installing Debian Lenny on Microsoft VirtualPC 2007
TODO: rename to ?InstallingDebianOn/Microsoft/WindowsServerHyperV