Virtual SME Server

The problem is that your IP is NOT on the same network range as your gateway so we have to fool the system.

config delprop sysconfig SystemID
config setprop sysconfig InstallEpoch `date +%s`
rm -f /etc/udev/rules.d/70-persistent-net.rules

config setprop ntpd SupportLargeDrift enabled
expand-template /etc/ntp.conf

service ntpd restart

[root@sme8 ~]# grep CONFIG_HZ /boot/config-`uname -r`
# CONFIG_HZ_100 is not set
# CONFIG_HZ_250 is not set
CONFIG_HZ_1000=y
CONFIG_HZ=1000

kernel /vmlinuz-2.6.18-348.6.1.el5 ro root=/dev/main/root 

kernel /vmlinuz-2.6.18-348.6.1.el5 ro root=/dev/main/root divider=10 clocksource=acpi_pm

yum install iotop

cat /proc/cpuinfo

db configuration set ExternalIP 200.30.30.1
db configuration set ExternalNetmask 255.255.255.255
db configuration set GatewayIP 62.20.20.1
/etc/e-smith/events/actions/initialize-default-databases

mkdir -p /etc/e-smith/templates-custom/etc/sysconfig/network/
echo '# GATEWAYDEV disabled for dedibox network' > /etc/e-smith/templates-custom/etc/sysconfig/network/40GATEWAYDEV
echo '# GATEWAY disabled for dedibox network' > /etc/e-smith/templates-custom/etc/sysconfig/network/50GATEWAY
expand-template /etc/sysconfig/network
mkdir -p /etc/e-smith/templates-custom/etc/sysconfig/network-scripts/route-ethX
cat <<'EOF' > /etc/e-smith/templates-custom/etc/sysconfig/network-scripts/route-ethX/20gateway
{
   die "Need to pass THIS_DEVICE in MORE_DATA\n" unless (defined $THIS_DEVICE);

   my $device = $ExternalInterface{Name};
   unless ($device)
   {   
       warn("Can't determine device name for external network");
       return "# template expansion error - Can't determine device name for external network";
   }

   return "# Gateway only applies on external interface"
       unless ($ExternalInterface{Name} eq $THIS_DEVICE);

   my $gw = $ExternalInterface{'Gateway'};

   $OUT .= "$gw dev $THIS_DEVICE\n";
   $OUT .= "default via $gw dev $THIS_DEVICE";
}
EOF

expand-template /etc/sysconfig/network-scripts/ifcfg-$(db configuration getprop ExternalInterface Name) 
expand-template /etc/sysconfig/network-scripts/route-$(db configuration getprop ExternalInterface Name)

signal-event post-upgrade;signal-event reboot

EthernetDriver1=virtio_net
EthernetDriver2=virtio_net
ExternalDHCP=off
ExternalIP=200.30.30.1
ExternalInterface=interface
   Broadcast=(whatever)
   Configuration=static
   Driver=virtio_net
   Gateway=62.20.20.1 #gateway for your main IP address
   HWAddress=10:10:00:00:20:20 #MAC that you set for 2nd IP address
   IPAddress=200.30.30.1 #your 2nd IP address 
   Name=eth1
   Netmask=255.255.255.255
   Network=200.30.30.1 #your 2nd IP address
ExternalNetmask=255.255.255.255
GatewayIP=62.20.20.1 #gateway for your main IP address

InternalInterface=interface
   Broadcast=192.168.98.255
   Configuration=static
   Driver=virtio_net
   HWAddress=fe:aa:16:19:e8:bf #MAC for 'virtual' adaptor
   IPAddress=192.168.98.1
   NICBondingOptions=miimon=200 mode=active-backup
   Name=eth0
   Netmask=255.255.255.0
   Network=192.168.98.0
LocalIP=192.168.98.1
LocalNetmask=255.255.255.0

Apr 30 13:37:29 sme9 kernel: ata2.00: exception Emask 0x0 SAct 0x7fffffff SErr 0x0 action 0x6 frozen
Apr 30 13:37:29 sme9 kernel: ata2.00: failed command: WRITE FPDMA QUEUED
Apr 30 13:37:29 sme9 kernel: ata2.00: cmd 61/08:00:08:7d:77/00:00:03:00:00/40 tag 0 ncq 4096 out
Apr 30 13:37:29 sme9 kernel:         res 40/00:01:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)

ssh -c blowfish -X -C root@YourServerIP

cd /storage/local/iso/
wget http://mirror.smeserver.eu/smeserver/releases/8.1/iso/x86_64/smeserver-8.1-x86_64.iso

qemu-img create -f qcow2 -o preallocation=metadata /storage/local/images/smeserver8vm.qcow2 10G

screen
virt-install --connect qemu:///system \
--name smeserver8vm --ram 1024 --vcpus 1 \
--disk path=/storage/local/images/smeserver8vm.qcow2,format=qcow2,bus=virtio,cache=none \
--network=bridge:vmbr0,model=virtio --vnc --os-type=linux --os-variant=rhel5 \
--cdrom /storage/local/iso/smeserver-8.1-x86_64.iso --accelerate --noautoconsole --keymap=fr

[CTRL+A+D]

virt-manager

Virtual SME Server

Contents

SME Server as a virtualized Guest server

Considerations

'Hardware' configuration of a Virtual SME Sever

CPU

Memory options

Disk options

Network options

Cloning a virtual SME Server

Installation options of a Virtual SME Server

Kernel options

SME Server configuration settings

NTPD

Clock/frequency

Tools/utilities

iotop

cpu info

Proxmox

SME v8 and v9 on Proxmox at Online.net

Online.net configuration

Proxmox configuration

SME Configuration

Xen

QEMU/KVM

Virtualbox

High I/O causing filesystem corruption

OpenNode

SME Server as a Host server

Phpvirtualbox

VMware

Navigation menu

Search

	Note:
	WIP. Place holder page for all things related to using SME Server as a virtualized server. Please add any info you feel is useful and someone from the doc team will format it nicely, so please go ahead!

	Skill level: Developer
	Thorough understanding of SME Server, configuration and virualization is required. Do not deploy in a production environment unless you are very confident you have the skills to manage and troubleshoot and find root causes of possible issues.

	Note:
	We need to come up with a template fragment for grub.conf to make kernel options survive events.

	Warning:
	You need a second IP (failover) address. Assign it to your server and make sure you set the MAC for this IP before you do anything else - failure to do so may block your network !! The problem is that your IP is NOT on the same network range as your gateway so we have to fool the system.

	Note:
	Make sure you set your default keyboard - it makes life much easier!!

	Warning:
	The procedures listed here are outside normal SME operation. They are not guaranteed to work. Make sure you fully understand what you are going before proceeding