Difference between revisions of "Installing LinuxMCE on Virtual Machine via KVM"

From LinuxMCE
Jump to: navigation, search
Line 62: Line 62:
 
Step 3) Add some management tools:
 
Step 3) Add some management tools:
  
 +
I use webmin to give my server a fixed ip address and perform other administrative tasks.
 +
 +
aptitude -y install perl libnet-ssleay-perl openssl libauthen-pam-perl libpam-runtime libio-pty-perl libmd5-perl apt-show-versions libapt-pkg-perl
 +
 +
You'll will get an error: Couldn't find any package whose name or description matched "libmd5-perl"
 +
 
  wget http://ftp.debian.org/pool/main/libm/libmd5-perl/libmd5-perl_2.03-1_all.deb
 
  wget http://ftp.debian.org/pool/main/libm/libmd5-perl/libmd5-perl_2.03-1_all.deb
  d
+
  dpkg -i libmd5-perl_2.03-1_all.deb
  
sudo wget http://prdownloads.sourceforge.net/webadmin/webmin_1.480_all.deb
+
I use MidNight Commander for file stuff
sudo apt-get install libnet-ssleay-perl libauthen-pam-perl libio-pty-perl libmd5-perl
+
   
  sudo dpkg -i webmin_1.480_all.deb
+
  apt-get install mc
  sudo apt-get install mc
+
  
I use webmin to give my server a fixed ip address and perform other administrative tasks.
+
Step 4) Changing kernel parameters.
MC (Midnight Commander) is a nice tool to move files around the server.
+
  
Step 4) Download the latest kernel from The Linux Kernel Archives [http://www.kernel.org/] and unpack it into /usr/bin.
+
Because Lucid Lynx does not support IOMMU out of the box we have to rebuild the kernel (see [http://linuxtweaking.blogspot.com/2010/05/how-to-compile-kernel-on-ubuntu-1004.html Rebuilding Lucid Kernel]
  
wget http://www.kernel.org/pub/linux/kernel/v2.6/linux-2.6.33.tar.bz2
+
Install the required tools and packages.
sudo tar -jxvf linux-2.6.33.tar.bz2 -C /usr/bin
+
  
Step 5) Install dependencies for make menuconfig.
+
Open a terminal and type the following,
  
  sudo apt-get install gcc ncurses* kernel-package fakeroot
+
  apt-get install fakeroot kernel-wedge build-essential makedumpfile kernel-package libncurses5 libncurses5-dev
  
Step 6) Configure the new kernel.
+
Then run the following command,
  
  cd /usr/bin/linux-2.6.33
+
  apt-get build-dep --no-install-recommends linux-image-$(uname -r)
sudo make menuconfig
+
  
  * set "Bus options (PCI etc.)" -> "Support for DMA Remapping Devices" to "*"
+
And finally type,
  * set "Bus options (PCI etc.)" -> "Enable DMA Remapping Devices" to "*"
+
  * set "Bus options (PCI etc.)" -> "PCI Stub driver" to "*"
+
  This line broke my setup so I took it out * optional setting: set "Bus options (PCI etc.)" -> "Support for Interrupt Remapping" to "*"
+
  
 +
mkdir ~/src
 +
cd ~/src
 +
apt-get source linux-image-$(uname -r)
 +
cd linux-2.6.32
  
 +
At the time of writing 2.6.32 was the current kernel source, it should remain at this version throughout the life of Ubuntu 10.04
  
Step 7) Build the new kernel.
+
It is a good idea to start with the same .config as the currently running kernel, so type the following,
  
For Karmic Koala and kernels > 2.6.32 we have to patch 2 files otherwise the build of the new kernel will fail. The kernel filesystem hierarchy has changed to separate generated header files from repository header files. So patch the files as explained in [http://ubuntuforums.org/showthread.php?p=8922730 The UTS Release version error Kernel Compile]
+
cp -vi /boot/config-`uname -r` .config
Download the patch and put it in /usr/share.
+
  
Patch the file with:
+
Now we are ready to customize the build and kernel options.
  
  patch -p0 < kernel-package-11.015-2.6.33.patch
+
  make menuconfig
  
Now build the new kernel:
+
  * set "Bus options (PCI etc.)" -> "Support for DMA Remapping Devices" to "*"
 +
  * set "Bus options (PCI etc.)" -> "Enable DMA Remapping Devices" to "*"
 +
  * set "Bus options (PCI etc.)" -> "PCI Stub driver" to "*"
 +
  This line broke my setup so I took it out * optional setting: set "Bus options (PCI etc.)" -> "Support for Interrupt Remapping" to "*"
  
sudo make-kpkg clean
+
Once you have finished, save and exit. It is now time to compile. However to speed up the build if you have a dual core processor type,
sudo fakeroot make-kpkg --initrd --append-to-version=-custom kernel_image kernel_headers
+
  
You can grab a coffee, make a hot meal, have a sleep ;-)
+
export CONCURRENCY_LEVEL=3
  
 +
The general rule is 1 + the number of processor cores.
  
Step 8) Install The New Kernel
+
Step 5) Build the new kernel.
  
Backup the "old" menu.lst
+
make-kpkg clean
 +
fakeroot make-kpkg --initrd --append-to-version=-iommu kernel-image kernel-headers
  
cp /boot/grub/menu.lst /boot/grub/menu.lst.bu
+
You can grab a coffee, make a hot meal, have a sleep ;-)
 +
 
 +
Step 6) Install The New Kernel
  
 
After the successful kernel build, you can find two .deb packages in the /usr/src directory.
 
After the successful kernel build, you can find two .deb packages in the /usr/src directory.
Line 126: Line 135:
  
  
Step 9) Check that menu.list has been updated with your new kernel
+
Step 7) Booting with the new kernel
 
+
+
cat /boot/grub/menu.lst
+
 
+
Step 10)
+
 
+
Using vim /boot/grub/menu.lst add the kernel options as shown below
+
 
+
title          Ubuntu 9.10, kernel 2.6.33-custom
+
uuid            3f26dc3f-a288-4457-8ce2-c8adecc
+
kernel          /boot/vmlinuz-2.6.33-custom root=UUID=3f26dc3f-a288-4457-8ce2-c8adecc ro quiet splash '''iommu=on,igfx_off,pass-through'''                                                                                       
+
initrd          /boot/initrd.img-2.6.33-custom                                                                 
+
quiet
+
 
+
After saving the file reboot the system;
+
  
 +
update-grub
 
  sudo reboot
 
  sudo reboot
  
Step 11) Deinstall networkmanager
+
Step 8) Deinstall networkmanager
  
 
  aptitude remove network-manager
 
  aptitude remove network-manager
  
Step 12) Setup your network, change /etc/network/interfaces to look like this
+
Step 9) Setup your network, change /etc/network/interfaces to look like this
  
 
  # This file describes the network interfaces available on your system
 
  # This file describes the network interfaces available on your system
Line 180: Line 175:
  
  
Step 13) Install Linuxmce
+
Step 10) Install Linuxmce
  
 
Using virt-manager you can now install LinuxMCE. As we are all experts on that I will only give away my xml config file (should be enough ;-))
 
Using virt-manager you can now install LinuxMCE. As we are all experts on that I will only give away my xml config file (should be enough ;-))
Line 263: Line 258:
 
  </domain>
 
  </domain>
  
Step 14) Enjoying building a test enviroment, inline upgrade etc.
+
Step 11) Enjoying building a test enviroment, inline upgrade etc.
  
Step 15) I chose to put my media on the host via a Samba share which will be detected as a NAS. This will simplify things when performing upgrades and test. Because I am using LVM also expansion is easy ;-)
+
Step 12) I chose to put my media on the host via a Samba share which will be detected as a NAS. This will simplify things when performing upgrades and test. Because I am using LVM also expansion is easy ;-)
  
  

Revision as of 13:11, 29 August 2010


KVM: To baldly go where (almost) no man has gone before

In this overview I will try to follow the installation path to get LCME 8.10 into a virtual machine which uses PCI(-E) devices from the host. Normally the option to install on a dedicated computer is the best, but as I want to host several systems, including LCME, websites etc and the ease of testing out new stuff combined with the fact that I want to keep it as green as possible lead me to the conclusion that virtualization was the way to go. Over the last 2 years I've been building systems that have failed in doing what I wanted (XEN and KVM based), but with the latest state of soft- and hardware I'll hope I'll have a better chance. The below is my queste for the wanted setup up, step by step.

Virtualization the way I want to do it can only be done with specific hardware/firmware which uses VT-d, a virtualization PCI Passthrough technique embedded in the bios.

So I will state my machine details first:

  • Motherboard: ASUS P5E VM DO with bios 10.1
  • CPU: Q6600
  • 6 Gb DDR-2 Memory
  • 1 onboard GbE Nic
  • 1 PCI-E GbE Nic
  • 1 Hauppauge PVR-150
  • 1 Hauppauge PVR-500


root@obelix:~# lspci
00:00.0 Host bridge: Intel Corporation 82Q35 Express DRAM Controller (rev 02)
00:02.0 VGA compatible controller: Intel Corporation 82Q35 Express Integrated Graphics Controller (rev 02)
00:03.0 Communication controller: Intel Corporation 82Q35 Express MEI Controller (rev 02)
00:03.2 IDE interface: Intel Corporation 82Q35 Express PT IDER Controller (rev 02)
00:03.3 Serial controller: Intel Corporation 82Q35 Express Serial KT Controller (rev 02)
00:19.0 Ethernet controller: Intel Corporation 82566DM-2 Gigabit Network Connection (rev 02)
00:1a.0 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #4 (rev 02)
00:1a.1 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #5 (rev 02)
00:1a.2 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #6 (rev 02)
00:1a.7 USB Controller: Intel Corporation 82801I (ICH9 Family) USB2 EHCI Controller #2 (rev 02)
00:1b.0 Audio device: Intel Corporation 82801I (ICH9 Family) HD Audio Controller (rev 02)
00:1c.0 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 1 (rev 02)
00:1d.0 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #1 (rev 02)
00:1d.1 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #2 (rev 02)
00:1d.2 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #3 (rev 02)
00:1d.7 USB Controller: Intel Corporation 82801I (ICH9 Family) USB2 EHCI Controller #1 (rev 02)
00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev 92)
00:1f.0 ISA bridge: Intel Corporation 82801IO (ICH9DO) LPC Interface Controller (rev 02)
00:1f.2 IDE interface: Intel Corporation 82801IR/IO/IH (ICH9R/DO/DH) 4 port SATA IDE Controller (rev 02)
00:1f.3 SMBus: Intel Corporation 82801I (ICH9 Family) SMBus Controller (rev 02)
00:1f.5 IDE interface: Intel Corporation 82801I (ICH9 Family) 2 port SATA IDE Controller (rev 02)
00:1f.6 Signal processing controller: Intel Corporation 82801I (ICH9 Family) Thermal Subsystem (rev 02)
01:00.0 Ethernet controller: Intel Corporation 82572EI Gigabit Ethernet Controller (Copper) (rev 06)
02:00.0 Multimedia video controller: Internext Compression Inc iTVC16 (CX23416) MPEG-2 Encoder (rev 01)
02:01.0 PCI bridge: Hint Corp HB6 Universal PCI-PCI bridge (non-transparent mode) (rev 11)
03:08.0 Multimedia video controller: Internext Compression Inc iTVC16 (CX23416) MPEG-2 Encoder (rev 01)
03:09.0 Multimedia video controller: Internext Compression Inc iTVC16 (CX23416) MPEG-2 Encoder (rev 01)
root@obelix:~#

Step 1) Install Ubuntu 10.04 server AMD 64 (should be easy enough if you are able to get LMCE up and running :-) )


Step 2) Make the system current:

 sudo apt-get update
 sudo apt-get upgrade


Step 3) Add some management tools:

I use webmin to give my server a fixed ip address and perform other administrative tasks.

aptitude -y install perl libnet-ssleay-perl openssl libauthen-pam-perl libpam-runtime libio-pty-perl libmd5-perl apt-show-versions libapt-pkg-perl

You'll will get an error: Couldn't find any package whose name or description matched "libmd5-perl"

wget http://ftp.debian.org/pool/main/libm/libmd5-perl/libmd5-perl_2.03-1_all.deb
dpkg -i libmd5-perl_2.03-1_all.deb

I use MidNight Commander for file stuff

apt-get install mc

Step 4) Changing kernel parameters.

Because Lucid Lynx does not support IOMMU out of the box we have to rebuild the kernel (see Rebuilding Lucid Kernel

Install the required tools and packages.

Open a terminal and type the following,

apt-get install fakeroot kernel-wedge build-essential makedumpfile kernel-package libncurses5 libncurses5-dev

Then run the following command,

apt-get build-dep --no-install-recommends linux-image-$(uname -r)

And finally type,

mkdir ~/src
cd ~/src
apt-get source linux-image-$(uname -r)
cd linux-2.6.32

At the time of writing 2.6.32 was the current kernel source, it should remain at this version throughout the life of Ubuntu 10.04

It is a good idea to start with the same .config as the currently running kernel, so type the following,

cp -vi /boot/config-`uname -r` .config

Now we are ready to customize the build and kernel options.

make menuconfig
  * set "Bus options (PCI etc.)" -> "Support for DMA Remapping Devices" to "*"
  * set "Bus options (PCI etc.)" -> "Enable DMA Remapping Devices" to "*"
  * set "Bus options (PCI etc.)" -> "PCI Stub driver" to "*"
  This line broke my setup so I took it out * optional setting: set "Bus options (PCI etc.)" -> "Support for Interrupt Remapping" to "*"

Once you have finished, save and exit. It is now time to compile. However to speed up the build if you have a dual core processor type,

export CONCURRENCY_LEVEL=3

The general rule is 1 + the number of processor cores.

Step 5) Build the new kernel.

make-kpkg clean
fakeroot make-kpkg --initrd --append-to-version=-iommu kernel-image kernel-headers

You can grab a coffee, make a hot meal, have a sleep ;-)

Step 6) Install The New Kernel

After the successful kernel build, you can find two .deb packages in the /usr/src directory.

cd .. 
ls -l linux*

Install them:

sudo dpkg -i linux-image-2.6.33-custom_2.6.33-custom-10.00.Custom_amd64.deb
sudo dpkg -i linux-headers-2.6.33-custom_2.6.33-custom-10.00.Custom_amd64.deb


Step 7) Booting with the new kernel

update-grub
sudo reboot

Step 8) Deinstall networkmanager

aptitude remove network-manager

Step 9) Setup your network, change /etc/network/interfaces to look like this

# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).
# The loopback network interface
auto lo
iface lo inet loopback
# The first bridge interface
auto bridge_ext
iface bridge_ext inet static
address 0.0.0.0 #no external access without going through DCERouter first
netmask 255.255.255.0
broadcast 10.0.0.255 
gateway 10.0.0.138
bridge_ports eth0
bridge_stp off
bridge_maxwait 5
# The second bridge interface
auto bridge_int
iface bridge_int inet static
address 192.168.80.240
netmask 255.255.255.0
broadcast 192.168.80.255
gateway 192.168.80.1
bridge_ports eth1
bridge_stp off
bridge_maxwait 5

With the above the host will use dcerouter as its way into the internet and thus the protection offered by the firewall. The host has no direct access to the 10.0.0.0 network.


Step 10) Install Linuxmce

Using virt-manager you can now install LinuxMCE. As we are all experts on that I will only give away my xml config file (should be enough ;-))

<domain type='kvm'>
 <name>DCERouter</name>
 <uuid>xxxxxxx-xxxx-xxxx-xxxx-xxxxxxxx</uuid>
 <memory>2097152</memory>
 <currentMemory>2097152</currentMemory>
 <vcpu>2</vcpu>
 <os>
   <type arch='x86_64' machine='pc-0.11'>hvm</type>
   <boot dev='hd'/>
 </os>
 <features>
   <acpi/>
   <apic/>
   <pae/>
 </features>
 <clock offset='utc'/>
 <on_poweroff>destroy</on_poweroff>
 <on_reboot>restart</on_reboot>
 <on_crash>restart</on_crash>
 <devices>
   <emulator>/usr/bin/kvm</emulator>
   <disk type='block' device='disk'>
     <source dev='/dev/sdc'/>
     <target dev='hda' bus='ide'/>
   </disk>
   <disk type='file' device='cdrom'>
     <target dev='hdc' bus='ide'/>
     <readonly/>
   </disk>
   <interface type='bridge'>
     <mac address='xx:xx:xx:xx:xx:xx'/>
     <source bridge='bridge_ext'/>
   </interface>
   <interface type='bridge'>
     <mac address='xx:xx:xx:xx:xx:xx'/>
     <source bridge='bridge_int'/>
     <model type='virtio'/>
   </interface>
   <serial type='pty'>
     <target port='0'/>
   </serial>
   <console type='pty'>
     <target port='0'/>
   </console>
   <input type='tablet' bus='usb'/>
   <input type='mouse' bus='ps2'/>
   <graphics type='vnc' port='-1' autoport='yes' keymap='en-us'/>
   <video>
     <model type='cirrus' vram='9216' heads='1'/>
   </video>
   <hostdev mode='subsystem' type='pci' managed='yes'>
     <source>
       <address domain='0x0000' bus='0x02' slot='0x00' function='0x0'/>
     </source>
   </hostdev>
   <hostdev mode='subsystem' type='pci' managed='yes'>
     <source>
       <address domain='0x0000' bus='0x03' slot='0x08' function='0x0'/>
     </source>
   </hostdev>
   <hostdev mode='subsystem' type='pci' managed='yes'>
     <source>
       <address domain='0x0000' bus='0x03' slot='0x09' function='0x0'/>
     </source>
   </hostdev>
   <hostdev mode='subsystem' type='usb' managed='yes'>
     <source>
       <vendor id='0x0403'/>
       <product id='0xf2d0'/>
     </source>
   </hostdev>
   <hostdev mode='subsystem' type='pci' managed='yes'>
     <source>
       <address domain='0x0000' bus='0x00' slot='0x1b' function='0x0'/>
     </source>
   </hostdev>
 </devices>
</domain>

Step 11) Enjoying building a test enviroment, inline upgrade etc.

Step 12) I chose to put my media on the host via a Samba share which will be detected as a NAS. This will simplify things when performing upgrades and test. Because I am using LVM also expansion is easy ;-)


Lmce kvm.png


Hints/Known Issues/Working Hardware


AMD/ATI Hardware
- NVidia Chipset 3600 with Opteron Socket F has full KVM support and works fine with LMCE 8.10.
- ATI-driver 9.8 supports kernel 2.6.30

Keyboard Layout
- As you can't choose the keyboard-layout in virtual-manager, simply change the keymap in the xml-file e.g. from "en-us" to "de".

Networking
- Step 11) is not needed if the physical network devices are configured as 'auto ethx \ iface ethx inet manual'
- The virtual LMCE runs fine with only one NIC provided to it. The setup automatically configures a sub-NIC which works well. I would suggest to have the host provide the internet-access, so vLMCE can't mess it up at the installation.

PCI-Passthrough at KVM
- PCI-Passthrough only works if the full PCI-device is transferred to the virtual machine. So if the PCI-Slot has sub-functions (e.g. Firewire) all of the 'functions' have to be adressed to the virtual machine with the <hostdev> section of Step 12). To look up your PCI-device-tree, use 'lspci -t'.

(Tyan S2915-E)
[0000:00]-+-00.0
          +-01.0
          +-01.1
          +-02.0
          +-02.1
          +-04.0
          +-05.0
          +-05.1
          +-06.0-[0000:01]----04.0                                           (<- PCI-Slot = DVB-card)
                            \-04.1                                           (<- Firewire, either disable in Bios or ->KVM)
          +-06.1
          +-08.0
          +-09.0
          +-0d.0-[0000:02-04]--+-00.0-[0000:03]----04.0
          |                    \-00.1-[0000:04]--
          +-0f.0-[0000:05]--+-00.0
          |                 \-00.1
          +-18.0
          +-18.1
          +-18.2
          +-18.3
          \-18.4

- PCIe-devices do not have this restriction.

- Please note that each change in the .xml-files is activated only after rebooting the libvirtd. You can do this manually by killing and restarting the process "libvirtd" or by a host reboot.

Problems with PVR-150 not responding

During usage it turned out that sometimes recordings failed having a total size of 0 B. Live TV has not worked stable at all. Checking the mythbackend logs shows that /dev/video0 was not responding as expected. Furthermore I detected DMA errors in the log of the host.

I am now testing the commandline option iommu=on,igfx_off,pass-through, where pass-through should be able to iron out the DMA errors.

Because the behaviour was not stable I also installed the mercurial ivtv drivers (within the VM ofcourse!!!!):

sudo apt-get install mercurial
cd /usr/src
sudo hg clone http://linuxtv.org/hg/v4l-dvb
cd v4l-dvb
sudo make
sudo make install
sudo make unload
sudo make load

You will have to rebuild after a kernel change.

Clicking sound on Audio device: Intel Corporation 82801I (ICH9 Family) HD Audio Controller (rev 02)

When passing-through my audio card I noticed hick ups in the MP3's and a message in kern.log;

hda-intel: IRQ timing workaround is activated for card #0. Suggest a bigger bdl_pos_adj.

edit alsa-base.conf;

vim /etc/modprobe.dalsa-base.conf

add the following line at the bottom;

options snd-hda-intel model=3stack-dig
options snd-hda-intel enable_msi=1
options snd-hda-intel single_cmd=1

and reboot (reload alsa does not seem to have the full effect)

Tip from Bugs Launchpad