Difference between pages "ClamAV" and "Compiling Xen"

From Wikislax
(Difference between pages)
Jump to: navigation, search
(Testing ClamAV)
 
(Compiling acpica)
 
Line 1: Line 1:
 
{{RightTOC}}
 
{{RightTOC}}
  
== What is ClamAV ? ==
+
== What is Xen ? ==
  
[http://www.clamav.net Clamav] is an Open Source antivirus.
+
[http://wiki.xen.org/wiki/Xen_Overview Xen] is an hypervisor, a thin software layer executing multiple virtual machines, each running its own operating system. Xen is normally used as a server virtualization platform, running on headless servers without graphical console and controlled through the network. However it is also possible to run Xen on graphical desktops, and with proper hardware virtualization, to dedicate the primary graphics card (and keyboard / mouse) to a virtual machine, making it possible to have high performance full 3D and video acceleration in a virtual machine (see [http://wiki.xen.org/wiki/Xen_VGA_Passthrough Xen VGA Passthru]). Xen is otherwise free and open source.
  
== Installing ClamAV ==
+
== A few quirks ==
  
Get the tarball from the [http://www.clamav.net/lang/en/download/sources/ download page]. Install in the standard way, create a user for running the software (e.g. '''milter''', as a single user has to be used by both '''Clamav''' and '''MIMEDefang''').
+
The '''dev86-0.16.21-x86_64-1.txz''' package included with Slackware 14.2 does not afford compiling '''xen-4.9.0''' properly, and must be replaced by '''[{{SERVER}}/wikislax/download/dev86-0.16.17-x86_64-2.txz dev86-0.16.17-x86_64-2.txz]''', that can be found on the Slackware 13.37, 14.0, or 14.1 distribution disks, in directory '''slackware64/d'''. Trying to compile dev86 [http://v3.sk/~lkundrak/dev86/ from source] is not an alternative : dev86 source versions 0.16.18 to 0.16.21 have the same issue compiling xen-4.9.0, and older 0.16.17 does not compile on Slackware 14.2.
  
  # tar -C /usr/local -xvf clamav-x.y.tar.gz
+
# removepkg /var/log/packages/dev86-0.16.21-x86_64-1.txz
  # cd /usr/local/
+
# installpkg dev86-0.16.17-x86_64-2.txz
  # chown -R root:root clamav-x.y.z
+
 
  # cd clamav-x.y
+
Also, the '''grub-2.00''' included with Slackware 14.2 does not afford booting xen. However, getting the latest version '''grub-2.02''' from source does work.
  # ./configure --help | less
+
 
  # ./configure --libdir=/usr/local/lib64 --mandir=/usr/local/man \
+
== Hardware requirements ==
  --sysconfdir=/etc --with-user=milter --with-group=milter
+
 
 +
Xen runs on Intel X86 hardware and requires a processor and motherboard supporting VT-x and optionally VT-d for hardware virtualization. See this [http://www.intel.com/support/motherboards/desktop/sb/cs-030922.htm page] for a list of Intel compatible motherboards and chipsets and this [http://ark.intel.com/ page] for a list of compatible processors. Our system running Xen successfully at the time of this writing (and since June 2012) is based on a DZ77GA70K Intel motherboard, an Intel® Core™ i7-3770 Processor (the overclockable i7-3770 "K" model does not afford virtualization), 32 Gb of PC12800 memory and an MSI GeForce G210 graphics board.
 +
 
 +
== Documentation difficulties ==
 +
 
 +
Although the software itself works well and is pretty straighforward, good quality Internet information is missing. The volume of information on the Xen wiki is plethoric, but mostly irrelevant as pertaining to old versions of everything. Building the big picture requires interpretation of tiny bits in forum messages, a pretty painful process, although I have to recognize that it worked for me in the end. An alternative is to use one of these old-style information repositories named "books". Yes it is pretty old-fashionned ;) but actually there are good ones on the topic. Here is [http://www.amazon.co.uk/The-Book-Xen-Practical-Administrator/dp/1593271867/ref=sr_1_1?s=books&ie=UTF8&qid=1341037874&sr=1-1 the most recent I found], it is a good value but of course you can find more on [http://www.amazon.co.uk/s/ref=nb_sb_noss_2?url=search-alias%3Dstripbooks&field-keywords=xen&x=0&y=0 amazon(.co.uk)].
 +
 
 +
== Software constraints ==
 +
 
 +
To make a long story short, at the time of this writing (and since June 2012) working with nVidia graphic boards on Xen and X11 requires the "nouveau" driver. Other drivers like nv or the nVidia proprietary driver do not support Xen and switch off the screen when launched or do not display properly. "Nouveau" requires a fairly recent version of X11. Slackware 13.37 or newer is required. "Nouveau" is available in kernel 3.4.2 upstream and was previously included as a staging driver. Xen dom0 support was included in kernel 3.0. To benefit from both Xen and "Nouveau", the best is to use kernel 3.4.2 upstream.
 +
 
 +
== Installing acpica ==
 +
 
 +
Xen requires acpica. [https://www.acpica.org/downloads Download] then install as below :
 +
 
 +
  # tar -C /usr/local -xvf acpica-unix-yyyymmdd.tar.gz
 +
  # cd /usr/local
 +
  # chown -R root:root acpica-unix-yyyymmdd
 +
  # cd acpica-unix-yyyymmdd
 +
# make
 +
  # make install
 +
 
 +
== Compiling yajl ==
 +
 
 +
Xen requires yajl. [http://lloyd.github.io/yajl/ Download] then install as below. <u>Note</u> : there is no option to specify the target library directory so the files need to be moved manually.
 +
 
 +
  # tar -C /usr/local -xvf lloyd-yajl-x.y.z.66cb08c.tar.gz
 +
# cd /usr/local
 +
  # chown -R root:root lloyd-yajl-66cb08c
 +
# cd lloyd-yajl-66cb08c
 +
# ./configure
 
  # make
 
  # make
 
  # make install
 
  # make install
  # make clean
+
  # cd ../lib
 +
# mv libyajl* ../lib64
 
  # ldconfig
 
  # ldconfig
  # groupadd milter
+
  # cd ..
  # useradd -g milter -s /bin/false milter
+
  # rm -r lloyd-yajl-66cb08c
# cd /var/log
 
# mkdir -m 700 milter
 
# chown milter:milter milter
 
# cd /var/run
 
# mkdir -m 700 milter
 
# chown milter:milter milter
 
# cd /usr/local/share
 
# mkdir clamav
 
# chown milter:milter clamav
 
  
== Configuring ClamAV ==
+
== Updating go ==
  
Review the configuration files in '''/etc/clamd.conf''' and '''/etc/freshclam.conf'''. Comment out the '''Example''' line and set the other parameters as below. The User milter line tells the software to execute as user milter :
+
Xen 4.19.1 requires the go language. Go is included as part of gcc but does not work "as is" and must be replaced by the version from the go web site. [https://go.dev/dl/ Download] then install as below.
  
  # cd /etc
+
  # ls /var/log/packages | grep gcc-go
  # cp clamd.conf.sample clamd.conf
+
  gcc-go-11.2.0-x86_64-2
  # vi clamd.conf
+
  # removepkg gcc-go-11.2.0-x86_64-2
 
  . . .
 
  . . .
  #Example
+
  # tar -C /usr/local -xvf go1.23.5.linux-amd64.tar.gz
LogFile /var/log/milter/clamd.log
+
 
  PidFile /var/run/milter/clamd.pid
+
Then add the '''/usr/local/go/bin''' to '''$PATH''' in /etc/profile. Make sure it works :
LocalSocket /var/spool/MIMEDefang/clamd.sock
+
 
TCPAddr 127.0.0.1
+
# go version
User milter
+
go version go1.23.5 linux/amd64
  DetectBrokenExecutables yes
+
  #
  <esc>
+
 
  :x
+
== Compiling Xen ==
  # cp freshclam.conf.sample freshclam.conf
+
 
  # vi freshclam.conf
+
[http://xen.org/products/xen_source.html Download Xen] from the official [http://www.xen.org xen.org] site. <u>Note</u> : File stubs-32.h is missing in the compiler includes so we add a link to the existing stubs-64.h. Also, some Xen Python scripts are installed in /usr/local/lib64/python-2.7/site-packages which python cannot find so we add links from the standard library as well.
  . . .
+
 
  #Example
+
  # cd /usr/include/gnu
  DatabaseDirectory /usr/local/share/clamav
+
  # ln -s stubs-64.h stubs-32.h
  UpdateLogFile /var/log/milter/freshclam.log
+
  # cd
  LogFileMaxSize 2M
+
  # tar -C /usr/local -xvf xen-x.y.z.tar.gz
  LogTime yes
+
  # cd /usr/local
  PidFile /var/run/milter/freshclam.pid
+
  # chown -R root:root xen-x.y.z
  DatabaseOwner milter
+
  # cd xen-x.y.z
DatabaseMirror db.FR.clamav.net
+
  # ./configure --libdir=/usr/local/lib64 --with-initddir=/etc/rc.d
NotifyClamd /etc/clamd.conf
+
  # make world
<esc>
+
  # make install
:x
+
  # make clean
 +
  # cd ../lib64/python2.7/site-packages
 +
# ln -s xen /usr/lib64/python2.7/site-packages
 +
  # ln -s xen-3.0-py2.7.egg-info /usr/lib64/python2.7/site-packages
  
== Running ClamAV ==
+
== Adjusting rc.local* ==
  
clamd and freshclam run as daemons so must be launched at startup and stopped at shutdown. Update '''/etc/rc.d/rc.local''' and '''/etc/rc.d/rc.local_shutdown''' accordingly :
+
Xen needs a couple of daemons to run to ensure VM management. Add these lines to rc.local and rc.local_shutdown :
  
  # vi /etc/rc.d/rc.local
+
  PATH=/usr/local/sbin:/usr/local/bin:$PATH
. . .
+
  export PATH
# start clamd
 
if [ -x /usr/local/sbin/clamd ]; then
 
        echo "Starting clamd daemon: /usr/local/sbin/clamd"
 
        /usr/local/sbin/clamd
 
  fi
 
 
   
 
   
  # start freshclam
+
  # start xencommons
  if [ -x /usr/local/bin/freshclam ]; then
+
  if [ -x /etc/rc.d/xencommons ]; then
        echo "Starting freshclam daemon: /usr/local/bin/freshclam -d"
+
    /etc/rc.d/xencommons start
        /usr/local/bin/freshclam -d
 
fi
 
<esc>
 
:x
 
# vi /etc/rc.d/rc.local_shutdown
 
. . .
 
# stop freshclam
 
if [ -r /var/run/milter/freshclam.pid ]; then
 
        echo "Stopping freshclam: kill -INT `cat /var/run/milter/freshclam.pid`"
 
        kill -INT `cat /var/run/milter/freshclam.pid`
 
 
  fi
 
  fi
 
   
 
   
  # stop clamd
+
  # stop xencommons
  if [ -r /var/run/milter/clamd.pid ]; then
+
  if [ -x /etc/rc.d/xencommons ]; then
        echo "Stopping clamd: kill -INT `cat /var/run/milter/clamd.pid`"
+
    /etc/rc.d/xencommons stop
        kill -INT `cat /var/run/milter/clamd.pid`
 
 
  fi
 
  fi
<esc>
 
:x
 
  
At this stage freshclam can be launched manually to initialize the virus database however clamd will fail as it requires a socket created by MIMEDefang when starting up. So we will delay clamd execution until MIMEDefang Sendmail with Milter are ready for use.
+
== Compiling a dom0 Kernel ==
  
== Testing ClamAV ==
+
Domain-0 (dom0 for short) is a special guest (virtual machine) that the Xen hypervisor always loads on host startup. Dom0 is used to control and manage the Xen hypervisor, and provides virtual disks and networks for other unprivileged guests (=domUs). Dom0 support was introduced in Linux kernel 3.0. The kernel generated must include the .config file domU and [http://wiki.xen.org/wiki/Mainline_Linux_Kernel_Configs#Configuring_the_kernel dom0 options]. Here is a minimal example of such a [{{SERVER}}/wikislax/download/config-dom0 .config dom0] file. Feel free to use it as a base, replacing device drivers as required. The rest of the kernel compilation is nominal :
  
Don't run '''rc.local''' now. Download the ClamAV database first:
+
# tar -C /usr/src -xvf linux-4.4.88.tar.bz2
 
+
# cd /usr/local
  # freshclam
+
# rm linux
 
+
# ln -s linux-4.4.88 linux
eicar.com is a test signature for ClamAV. Make sure it works for you.
+
# cd linux
 +
# make menuconfig
 +
  # make
 +
# make modules_install
 +
# cp arch/x86_64/boot/bzImage /boot/vmlinuz-4.4.88-dom0
 +
# cp System.map /boot/System.map-4.4.88-dom0
 +
# cp .config /boot/config-4.4.88-dom0
  
# '''clamscan -r -l scan.txt ./'''[{{SERVER}}/wikislax/download/eicar.com eicar.com]
+
We're now all set up, Xen is ready to be booted by grub2 !
./eicar.com: Eicar-Test-Signature FOUND
 
 
----------- SCAN SUMMARY -----------
 
Known viruses: 4890369
 
Engine version: 0.99.2
 
Scanned directories: 0
 
Scanned files: 1
 
Infected files: 1
 
Data scanned: 0.00 MB
 
Data read: 0.00 MB (ratio 0.00:1)
 
Time: 6.302 sec (0 m 6 s)
 
  
 
<br/>
 
<br/>
  
{{pFoot|[[SpamAssassin]]|[[Main Page]]|[[Milter]]}}
+
{{ pFoot |[[Compiling from Source]]|[[Main Page]]|[[Using Grub2]]}}

Revision as of 14:52, 4 February 2025

What is Xen ?

Xen is an hypervisor, a thin software layer executing multiple virtual machines, each running its own operating system. Xen is normally used as a server virtualization platform, running on headless servers without graphical console and controlled through the network. However it is also possible to run Xen on graphical desktops, and with proper hardware virtualization, to dedicate the primary graphics card (and keyboard / mouse) to a virtual machine, making it possible to have high performance full 3D and video acceleration in a virtual machine (see Xen VGA Passthru). Xen is otherwise free and open source.

A few quirks

The dev86-0.16.21-x86_64-1.txz package included with Slackware 14.2 does not afford compiling xen-4.9.0 properly, and must be replaced by dev86-0.16.17-x86_64-2.txz, that can be found on the Slackware 13.37, 14.0, or 14.1 distribution disks, in directory slackware64/d. Trying to compile dev86 from source is not an alternative : dev86 source versions 0.16.18 to 0.16.21 have the same issue compiling xen-4.9.0, and older 0.16.17 does not compile on Slackware 14.2.

# removepkg /var/log/packages/dev86-0.16.21-x86_64-1.txz
# installpkg dev86-0.16.17-x86_64-2.txz

Also, the grub-2.00 included with Slackware 14.2 does not afford booting xen. However, getting the latest version grub-2.02 from source does work.

Hardware requirements

Xen runs on Intel X86 hardware and requires a processor and motherboard supporting VT-x and optionally VT-d for hardware virtualization. See this page for a list of Intel compatible motherboards and chipsets and this page for a list of compatible processors. Our system running Xen successfully at the time of this writing (and since June 2012) is based on a DZ77GA70K Intel motherboard, an Intel® Core™ i7-3770 Processor (the overclockable i7-3770 "K" model does not afford virtualization), 32 Gb of PC12800 memory and an MSI GeForce G210 graphics board.

Documentation difficulties

Although the software itself works well and is pretty straighforward, good quality Internet information is missing. The volume of information on the Xen wiki is plethoric, but mostly irrelevant as pertaining to old versions of everything. Building the big picture requires interpretation of tiny bits in forum messages, a pretty painful process, although I have to recognize that it worked for me in the end. An alternative is to use one of these old-style information repositories named "books". Yes it is pretty old-fashionned ;) but actually there are good ones on the topic. Here is the most recent I found, it is a good value but of course you can find more on amazon(.co.uk).

Software constraints

To make a long story short, at the time of this writing (and since June 2012) working with nVidia graphic boards on Xen and X11 requires the "nouveau" driver. Other drivers like nv or the nVidia proprietary driver do not support Xen and switch off the screen when launched or do not display properly. "Nouveau" requires a fairly recent version of X11. Slackware 13.37 or newer is required. "Nouveau" is available in kernel 3.4.2 upstream and was previously included as a staging driver. Xen dom0 support was included in kernel 3.0. To benefit from both Xen and "Nouveau", the best is to use kernel 3.4.2 upstream.

Installing acpica

Xen requires acpica. Download then install as below :

# tar -C /usr/local -xvf acpica-unix-yyyymmdd.tar.gz
# cd /usr/local
# chown -R root:root acpica-unix-yyyymmdd
# cd acpica-unix-yyyymmdd
# make
# make install

Compiling yajl

Xen requires yajl. Download then install as below. Note : there is no option to specify the target library directory so the files need to be moved manually.

# tar -C /usr/local -xvf lloyd-yajl-x.y.z.66cb08c.tar.gz
# cd /usr/local
# chown -R root:root lloyd-yajl-66cb08c
# cd lloyd-yajl-66cb08c
# ./configure
# make
# make install
# cd ../lib
# mv libyajl* ../lib64
# ldconfig
# cd ..
# rm -r lloyd-yajl-66cb08c

Updating go

Xen 4.19.1 requires the go language. Go is included as part of gcc but does not work "as is" and must be replaced by the version from the go web site. Download then install as below.

# ls /var/log/packages | grep gcc-go
gcc-go-11.2.0-x86_64-2
# removepkg gcc-go-11.2.0-x86_64-2
. . .
# tar -C /usr/local -xvf go1.23.5.linux-amd64.tar.gz

Then add the /usr/local/go/bin to $PATH in /etc/profile. Make sure it works :

# go version
go version go1.23.5 linux/amd64
#

Compiling Xen

Download Xen from the official xen.org site. Note : File stubs-32.h is missing in the compiler includes so we add a link to the existing stubs-64.h. Also, some Xen Python scripts are installed in /usr/local/lib64/python-2.7/site-packages which python cannot find so we add links from the standard library as well.

# cd /usr/include/gnu
# ln -s stubs-64.h stubs-32.h
# cd
# tar -C /usr/local -xvf xen-x.y.z.tar.gz
# cd /usr/local
# chown -R root:root xen-x.y.z
# cd xen-x.y.z
# ./configure --libdir=/usr/local/lib64 --with-initddir=/etc/rc.d
# make world
# make install
# make clean
# cd ../lib64/python2.7/site-packages
# ln -s xen /usr/lib64/python2.7/site-packages
# ln -s xen-3.0-py2.7.egg-info /usr/lib64/python2.7/site-packages

Adjusting rc.local*

Xen needs a couple of daemons to run to ensure VM management. Add these lines to rc.local and rc.local_shutdown :

PATH=/usr/local/sbin:/usr/local/bin:$PATH
export PATH

# start xencommons
if [ -x /etc/rc.d/xencommons ]; then
    /etc/rc.d/xencommons start
fi

# stop xencommons
if [ -x /etc/rc.d/xencommons ]; then
    /etc/rc.d/xencommons stop
fi

Compiling a dom0 Kernel

Domain-0 (dom0 for short) is a special guest (virtual machine) that the Xen hypervisor always loads on host startup. Dom0 is used to control and manage the Xen hypervisor, and provides virtual disks and networks for other unprivileged guests (=domUs). Dom0 support was introduced in Linux kernel 3.0. The kernel generated must include the .config file domU and dom0 options. Here is a minimal example of such a .config dom0 file. Feel free to use it as a base, replacing device drivers as required. The rest of the kernel compilation is nominal :

# tar -C /usr/src -xvf linux-4.4.88.tar.bz2
# cd /usr/local
# rm linux
# ln -s linux-4.4.88 linux
# cd linux
# make menuconfig
# make
# make modules_install
# cp arch/x86_64/boot/bzImage /boot/vmlinuz-4.4.88-dom0
# cp System.map /boot/System.map-4.4.88-dom0
# cp .config /boot/config-4.4.88-dom0

We're now all set up, Xen is ready to be booted by grub2 !


Compiling from Source Main Page Using Grub2