http://wiki.linuxmce.org/api.php?action=feedcontributions&feedformat=atom&user=DeepbLinuxMCE - User contributions [en]2026-05-11T05:33:20ZUser contributionsMediaWiki 1.44.0http://wiki.linuxmce.org/index.php?title=User:Deepb&diff=34477User:Deepb2013-09-14T06:29:11Z<p>Deepb: </p>
<hr />
<div>=Installation of LinuxMCE in a KVM Virtual Machine=<br />
On this page I will describe the installation process of LinuxMCE in a KVM virtual machine. As a host system I use proxmox, a very user friendly and easy to use bare metal hypervisor. <br />
<br />
==Download Required Software==<br />
<br />
Download Proxmox the latest version of proxmox: [http://www.proxmox.com/downloads/category/iso-images-pve]<br />
:At the moment of this writing the current version is Proxmox VE 3.1<br />
Download LinuxMCE [http://www.linuxmce.org/download.html]<br />
:At the moment of this writing the current version is LinuxMCE 1004 final<br />
<br />
Adittionally if you are on Windows and want to use a usb-stick: (you do not need any addidional program on Linux)<br />
:Suse Studio Image Writer [ftp://ftp.berlios.de/pub/kiwi/ImageWriter.exe] to write the image to a usb-stick. UnetBootin and Rufus do not work. <br />
<br />
==Copying Image to USB-Stick==<br />
If you want to use a CD simply burn the iso to a cd.<br />
===On Linux===<br />
Please make sure that /dev/XYZ is the right device, as this delets all content. Please also note that this is the device WITHOUT the number for the partition. SO for example /dev/sdc AND NOT /dev/sdc1 pve-cd.iso is the current proxmox iso that you downloaded. <br />
dd if=pve-cd.iso of=/dev/XYZ bs=1M<br />
===On Windows===<br />
First delete the partition of the usb-stick, else Suse Studio Image Writer might fail with a access failed error.<br />
Then rename the Proxmox iso that you downloaded from .iso to .raw. <br />
Run Suse Studio Image Writer, selct the drive and the image.<br />
<br />
==Base Installation of Proxmox==<br />
The graphical installation guide is straightforward and easy to understand.<br />
Please note though that the installer <span style="background:#ff0000">DELETS ALL PARTITIONS ON THE SELECTED DRIVE!</span> So all data on that drive is lost! You might want to unhook all harddrives that have unsaved data on it just to make sure you do not pick the wrong one by accident. <br />
<br />
==Reboot and Settings==<br />
After the base installation reboot the system, and check if you put in the right ip data in the installation process. <br />
NOTE: if you have multiple newtork cards make sure you plug the cable into the right one, if you do not have network connection try the other one.<br />
===Networking===<br />
Networking should work out of the box, if it does you can ignore this chapter and continue with [[Update]]. <br />
Else: check if there is internet connectivity by pinging something.<br />
ping google.com<br />
If you want to change the network settings <br />
nano /etc/network/interfaces<br />
if you want to use dhcp for the public interface this should look like:<br />
auto lo<br />
iface lo inet loopback<br />
auto vmbr0<br />
iface vmbr0 inet dhcp<br />
If you want to use static it should look something like that:<br />
auto lo<br />
iface lo inet loopback<br />
auto vmbr0<br />
iface vmbr0 inet static<br />
address 192.168.0.13<br />
netmask 255.255.255.0<br />
gateway 192.168.0.1<br />
bridge_ports eth0<br />
bridge_stp off<br />
bridge_fd 0<br />
if you did change some network setting run <br />
/etc/init.d/networking restart<br />
===Update===<br />
run<br />
aptitude update && aptitude full-upgrade<br />
If you get the message <br />
E: Some index files failed to download. They have been ignored, or old ones used instead.<br />
you can ignore it, or if rather not you can edit<br />
nano /etc/apt/sources.list.d/pve-enterprise.list<br />
and comment out the enterpries repository by placing a "#" in front of it. <br />
#deb https://enterprise.proxmox.com/debian wheezy pve-enterprise<br />
<br />
==Software Raid==<br />
If you do not want to use softwar raid you can continue with the next chapter.<br />
<span style="background:#ff0000">WARNING: Software raid is not supported by proxmox!</span><br />
But of course it works nevertheless, but as usual do it on your own risk.<br />
This part of the guide is based in a German guide found here[http://dominicpratt.de/proxmox-ve-3-0-software-raid/]<br />
First install the required package:<br />
apt-get update; apt-get install mdadm screen<br />
If there are any prompts on installing mdadm just ignore or press yes.<br />
<br />
If you have not done so yet shutdown and plugin the second (identical) drive.<br />
In this guide the harddrive that proxmox was installed on is /dev/sda, while the second to use in the raid is /dev/sdb. If you have different drive letter, please change them accordingly.<br />
Prepare and create raid:<br />
sfdisk -d /dev/sda | sfdisk -f /dev/sdb<br />
sfdisk -c /dev/sdb 1 fd<br />
sfdisk -c /dev/sdb 2 fd<br />
mdadm --create -l1 -n2 /dev/md0 missing /dev/sdb1<br />
mdadm --create -l1 -n2 /dev/md1 missing /dev/sdb2<br />
copy /boot to the new raid md. (Note: md with raid means "multiple device" and has nothing to do with media director)<br />
mkfs.ext3 /dev/md0<br />
mkdir /mnt/md0<br />
mount /dev/md0 /mnt/md0<br />
cp -ax /boot/* /mnt/md0<br />
Then edit the fstab<br />
nano /etc/fstab<br />
and find the line for boot that says <br />
UUID=xxxxxxxxx /boot ext3 defaults 0 1<br />
and change it to <br />
/dev/md0 /boot ext3 defaults 0 1<br />
then reboot and check with<br />
mount | grep boot<br />
that /dev/md0 is mounted on /boot.<br />
if that worked we tell grub that we want to boot from the raid:<br />
echo ‘GRUB_DISABLE_LINUX_UUID=true’ >> /etc/default/grub <br />
echo ‘GRUB_PRELOAD_MODULES=”raid dmraid”‘ >> /etc/default/grub <br />
echo raid1 >> /etc/modules <br />
echo raid1 >> /etc/initramfs-tools/modules <br />
grub-install /dev/sda --recheck<br />
grub-install /dev/sda<br />
grub-install /dev/sdb --recheck<br />
grub-install /dev/sdb<br />
update-grub<br />
update-initramfs -u<br />
Then we add sda1 to the raid (note: this might take some time, so make a coffee... or do it over the night. It might take >3 hours on 1TB). You should probably use screen.<br />
screen<br />
sfdisk -c /dev/sda 1 fd<br />
mdadm –add /dev/md0 /dev/sda1<br />
and move the root lvm onto the raid too<br />
pvcreate /dev/md1<br />
vgextend pve /dev/md1<br />
pvmove /dev/sda2 /dev/md1<br />
vgreduce pve /dev/sda2<br />
pvremove /dev/sda2<br />
sfdisk –change-id /dev/sda 2 fd<br />
mdadm –add /dev/md1 /dev/sda2<br />
with<br />
cat /proc/mdstat <br />
you can see how far the building of the new raid is, and only if it is finnished reboot.<br />
==Checking Network again==<br />
If you do not see the two network adapters (vmbr0 and vmbr1) in<br />
ifconfig<br />
you need to change edit interfaces again.<br />
nano /etc/network/interfaces<br />
mine looks like that:<br />
auto lo<br />
iface lo inet loopback<br />
auto vmbr0<br />
iface vmbr0 inet static<br />
address 192.168.0.13<br />
netmask 255.255.255.0<br />
gateway 192.168.0.1<br />
bridge_ports eth0<br />
bridge_stp off<br />
bridge_fd 0<br />
auto vmbr1<br />
iface vmbr1 inet static<br />
address 10.0.0.1<br />
netmask 255.255.255.0<br />
bridge_ports eth1<br />
bridge_stp off<br />
bridge_fd 0<br />
<br />
==Installing LinuxMCE==<br />
open a browser (on any pc in the network, not on the server) and navigate to https://server-ipadress:8006. Substitute server-ipadress for the ipadress of the proxmox-server. this is usually something like https://192.168.0.5:8006<br />
<br />
In the left column open datacenter, then your server (the servername), then local (storage) and click in the upper middle of the page on upload. Select the linuxmce iso and upload it. There are also other possibilities, including copying from a NAS, but for further information see the proxmox wiki [http://pve.proxmox.com/wiki/Main_Page].<br />
<br />
When the upload is done click on the very upper right "create VM" to create a VM.<br />
You only have one node, the VM ID you can put wathever you want, the same for the Name. Ignore the REsource Pool. <br />
Click on Next<br />
<br />
Choose Linux 3.x/2.6 Kernal (l26) and click on Next.<br />
<br />
Then choose the iso image you just uploaded and click on Next<br />
<br />
Note: Everything from here on you can change later.<br />
<br />
Change Bus/Device from IDE to virtio (better performance)<br />
Put in the Disk Size you want, and leave everything else. Click on Next.<br />
<br />
Choose the CPU Cores, and click Next.<br />
<br />
Choose Memory size an click Next.<br />
<br />
Change Network model to virtio (better performance) and klick next.<br />
<br />
Click Finnish to create VM.<br />
Congratulations, now you have succesfully created the first VM.<br />
<br />
But not all work is done, the VM still has only one network interface.<br />
<br />
Now select the new VM on the left, then click on Hardware and select add->network device<br />
Select the Second Bridge, and again Model: Virtio and click add.<br />
<br />
Congratulations, now you have everything you need. Click on Start to start the VM, and on Console to get the screen of the VM.<br />
Please note that the Console is quite picky about the java version, if it does not work try another one.</div>Deepbhttp://wiki.linuxmce.org/index.php?title=User:Deepb&diff=34475User:Deepb2013-09-12T16:51:27Z<p>Deepb: </p>
<hr />
<div>=Installation of LinuxMCE in a KVM Virtual Machine=<br />
On this page I will describe the installation process of LinuxMCE in a KVM virtual machine. As a host system I use proxmox, a very user friendly and easy to use bare metal hypervisor. <br />
<br />
==Download Required Software==<br />
<br />
Download Proxmox the latest version of proxmox: [http://www.proxmox.com/downloads/category/iso-images-pve]<br />
:At the moment of this writing the current version is Proxmox VE 3.1<br />
Download LinuxMCE [http://www.linuxmce.org/download.html]<br />
:At the moment of this writing the current version is LinuxMCE 1004 final<br />
<br />
Adittionally if you are on Windows and want to use a usb-stick: (you do not need any addidional program on Linux)<br />
:Suse Studio Image Writer [ftp://ftp.berlios.de/pub/kiwi/ImageWriter.exe] to write the image to a usb-stick. UnetBootin and Rufus do not work. <br />
<br />
==Copying Image to USB-Stick==<br />
If you want to use a CD simply burn the iso to a cd.<br />
===On Linux===<br />
Please make sure that /dev/XYZ is the right device, as this delets all content. Please also note that this is the device WITHOUT the number for the partition. SO for example /dev/sdc AND NOT /dev/sdc1 pve-cd.iso is the current proxmox iso that you downloaded. <br />
dd if=pve-cd.iso of=/dev/XYZ bs=1M<br />
===On Windows===<br />
First delete the partition of the usb-stick, else Suse Studio Image Writer might fail with a access failed error.<br />
Then rename the Proxmox iso that you downloaded from .iso to .raw. <br />
Run Suse Studio Image Writer, selct the drive and the image.<br />
<br />
==Base Installation of Proxmox==<br />
The graphical installation guide is straightforward and easy to understand.<br />
Please note though that the installer <span style="background:#ff0000">DELETS ALL PARTITIONS ON THE SELECTED DRIVE!</span> So all data on that drive is lost! You might want to unhook all harddrives that have unsaved data on it just to make sure you do not pick the wrong one by accident. <br />
<br />
==Reboot and Settings==<br />
After the base installation reboot the system, and check if you put in the right ip data in the installation process. <br />
NOTE: if you have multiple newtork cards make sure you plug the cable into the right one, if you do not have network connection try the other one.<br />
===Networking===<br />
Networking should work out of the box, if it does you can ignore this chapter and continue with [[Update]]. <br />
Else: check if there is internet connectivity by pinging something.<br />
ping google.com<br />
If you want to change the network settings <br />
nano /etc/network/interfaces<br />
if you want to use dhcp for the public interface this should look like:<br />
auto lo<br />
iface lo inet loopback<br />
auto vmbr0<br />
iface vmbr0 inet dhcp<br />
If you want to use static it should look something like that:<br />
auto lo<br />
iface lo inet loopback<br />
auto vmbr0<br />
iface vmbr0 inet static<br />
address 192.168.0.13<br />
netmask 255.255.255.0<br />
gateway 192.168.0.1<br />
bridge_ports eth0<br />
bridge_stp off<br />
bridge_fd 0<br />
if you did change some network setting run <br />
/etc/init.d/networking restart<br />
===Update===<br />
run<br />
aptitude update && aptitude full-upgrade<br />
If you get the message <br />
E: Some index files failed to download. They have been ignored, or old ones used instead.<br />
you can ignore it, or if rather not you can edit<br />
nano /etc/apt/sources.list.d/pve-enterprise.list<br />
and comment out the enterpries repository by placing a "#" in front of it. <br />
#deb https://enterprise.proxmox.com/debian wheezy pve-enterprise<br />
<br />
==Software Raid==<br />
If you do not want to use softwar raid you can continue with the next chapter.<br />
<span style="background:#ff0000">WARNING: Software raid is not supported by proxmox!</span><br />
But of course it works nevertheless, but as usual do it on your own risk.<br />
This part of the guide is based in a German guide found here[http://dominicpratt.de/proxmox-ve-3-0-software-raid/]<br />
First install the required package:<br />
apt-get update; apt-get install mdadm screen<br />
If there are any prompts on installing mdadm just ignore or press yes.<br />
<br />
If you have not done so yet shutdown and plugin the second (identical) drive.<br />
In this guide the harddrive that proxmox was installed on is /dev/sda, while the second to use in the raid is /dev/sdb. If you have different drive letter, please change them accordingly.<br />
Prepare and create raid:<br />
sfdisk -d /dev/sda | sfdisk -f /dev/sdb<br />
sfdisk -c /dev/sdb 1 fd<br />
sfdisk -c /dev/sdb 2 fd<br />
mdadm --create -l1 -n2 /dev/md0 missing /dev/sdb1<br />
mdadm --create -l1 -n2 /dev/md1 missing /dev/sdb2<br />
copy /boot to the new raid md. (Note: md with raid means "multiple device" and has nothing to do with media director)<br />
mkfs.ext3 /dev/md0<br />
mkdir /mnt/md0<br />
mount /dev/md0 /mnt/md0<br />
cp -ax /boot/* /mnt/md0<br />
Then edit the fstab<br />
nano /etc/fstab<br />
and find the line for boot that says <br />
UUID=xxxxxxxxx /boot ext3 defaults 0 1<br />
and change it to <br />
/dev/md0 /boot ext3 defaults 0 1<br />
then reboot and check with<br />
mount | grep boot<br />
that /dev/md0 is mounted on /boot.<br />
if that worked we tell grub that we want to boot from the raid:<br />
echo ‘GRUB_DISABLE_LINUX_UUID=true’ >> /etc/default/grub <br />
echo ‘GRUB_PRELOAD_MODULES=”raid dmraid”‘ >> /etc/default/grub <br />
echo raid1 >> /etc/modules <br />
echo raid1 >> /etc/initramfs-tools/modules <br />
grub-install /dev/sda --recheck<br />
grub-install /dev/sda<br />
grub-install /dev/sdb --recheck<br />
grub-install /dev/sdb<br />
update-grub<br />
update-initramfs -u<br />
Then we add sda1 to the raid (note: this might take some time, so make a coffee... or do it over the night. It might take >3 hours on 1TB). You should probably use screen.<br />
screen<br />
sfdisk -c /dev/sda 1 fd<br />
mdadm –add /dev/md0 /dev/sda1<br />
and move the root lvm onto the raid too<br />
pvcreate /dev/md1<br />
vgextend pve /dev/md1<br />
pvmove /dev/sda2 /dev/md1<br />
vgreduce pve /dev/sda2<br />
pvremove /dev/sda2<br />
sfdisk –change-id /dev/sda 2 fd<br />
mdadm –add /dev/md1 /dev/sda2<br />
with<br />
cat /proc/mdstat <br />
you can see how far the building of the new raid is, and only if it is finnished reboot.<br />
===Checking Network again===<br />
If you do not see the two network adapters (vmbr0 and vmbr1) in<br />
ifconfig<br />
you need to change edit interfaces again.<br />
nano /etc/network/interfaces<br />
mine looks like that:<br />
auto lo<br />
iface lo inet loopback<br />
auto vmbr0<br />
iface vmbr0 inet static<br />
address 192.168.0.13<br />
netmask 255.255.255.0<br />
gateway 192.168.0.1<br />
bridge_ports eth0<br />
bridge_stp off<br />
bridge_fd 0<br />
auto vmbr1<br />
iface vmbr1 inet static<br />
address 10.0.0.1<br />
netmask 255.255.255.0<br />
bridge_ports eth1<br />
bridge_stp off<br />
bridge_fd 0<br />
<br />
==Installing LinuxMCE==<br />
open a browser (on any pc in the network, not on the server) and navigate to https://server-ipadress:8006. Substitute server-ipadress for the ipadress of the proxmox-server. this is usually something like https://192.168.0.5:8006<br />
<br />
In the left column open datacenter, then your server (the servername), then local (storage) and click in the upper middle of the page on upload. Select the linuxmce iso and upload it. There are also other possibilities, including copying from a NAS, but for further information see the proxmox wiki [http://pve.proxmox.com/wiki/Main_Page].<br />
<br />
When the upload is done click on the very upper right "create VM" to create a VM.<br />
You only have one node, the VM ID you can put wathever you want, the same for the Name. Ignore the REsource Pool. <br />
Click on Next<br />
<br />
Choose Linux 3.x/2.6 Kernal (l26) and click on Next.<br />
<br />
Then choose the iso image you just uploaded and click on Next<br />
<br />
Note: Everything from here on you can change later.<br />
<br />
Change Bus/Device from IDE to virtio (better performance)<br />
Put in the Disk Size you want, and leave everything else. Click on Next.<br />
<br />
Choose the CPU Cores, and click Next.<br />
<br />
Choose Memory size an click Next.<br />
<br />
Change Network model to virtio (better performance) and klick next.<br />
<br />
Click Finnish to create VM.<br />
Congratulations, now you have succesfully created the first VM.<br />
<br />
But not all work is done, the VM still has only one network interface.<br />
<br />
Now select the new VM on the left, then click on Hardware and select add->network device<br />
Select the Second Bridge, and again Model: Virtio and click add.<br />
<br />
Congratulations, now you have everything you need. Click on Start to start the VM, and on Console to get the screen of the VM.<br />
Please note that the Console is quite picky about the java version, if it does not work try another one.</div>Deepbhttp://wiki.linuxmce.org/index.php?title=User:Deepb&diff=34474User:Deepb2013-09-12T16:40:38Z<p>Deepb: </p>
<hr />
<div>=Installation of LinuxMCE in a KVM Virtual Machine=<br />
On this page I will describe the installation process of LinuxMCE in a KVM virtual machine. As a host system I use proxmox, a very user friendly and easy to use bare metal hypervisor. <br />
<br />
==Download Required Software==<br />
<br />
Download Proxmox the latest version of proxmox: [http://www.proxmox.com/downloads/category/iso-images-pve]<br />
:At the moment of this writing the current version is Proxmox VE 3.1<br />
Download LinuxMCE [http://www.linuxmce.org/download.html]<br />
:At the moment of this writing the current version is LinuxMCE 1004 final<br />
<br />
Adittionally if you are on Windows and want to use a usb-stick: (you do not need any addidional program on Linux)<br />
:Suse Studio Image Writer [ftp://ftp.berlios.de/pub/kiwi/ImageWriter.exe] to write the image to a usb-stick. UnetBootin and Rufus do not work. <br />
<br />
==Copying Image to USB-Stick==<br />
If you want to use a CD simply burn the iso to a cd.<br />
===On Linux===<br />
Please make sure that /dev/XYZ is the right device, as this delets all content. Please also note that this is the device WITHOUT the number for the partition. SO for example /dev/sdc AND NOT /dev/sdc1 pve-cd.iso is the current proxmox iso that you downloaded. <br />
dd if=pve-cd.iso of=/dev/XYZ bs=1M<br />
===On Windows===<br />
First delete the partition of the usb-stick, else Suse Studio Image Writer might fail with a access failed error.<br />
Then rename the Proxmox iso that you downloaded from .iso to .raw. <br />
Run Suse Studio Image Writer, selct the drive and the image.<br />
<br />
==Base Installation of Proxmox==<br />
The graphical installation guide is straightforward and easy to understand.<br />
Please note though that the installer <span style="background:#ff0000">DELETS ALL PARTITIONS ON THE SELECTED DRIVE!</span> So all data on that drive is lost! You might want to unhook all harddrives that have unsaved data on it just to make sure you do not pick the wrong one by accident. <br />
<br />
==Reboot and Settings==<br />
After the base installation reboot the system, and check if you put in the right ip data in the installation process. <br />
NOTE: if you have multiple newtork cards make sure you plug the cable into the right one, if you do not have network connection try the other one.<br />
===Networking===<br />
Networking should work out of the box, if it does you can ignore this chapter and continue with [[Update]]. <br />
Else: check if there is internet connectivity by pinging something.<br />
ping google.com<br />
If you want to change the network settings <br />
nano /etc/network/interfaces<br />
if you want to use dhcp for the public interface this should look like:<br />
auto lo<br />
iface lo inet loopback<br />
auto vmbr0<br />
iface vmbr0 inet dhcp<br />
If you want to use static it should look something like that:<br />
auto lo<br />
iface lo inet loopback<br />
auto vmbr0<br />
iface vmbr0 inet static<br />
address 192.168.0.13<br />
netmask 255.255.255.0<br />
gateway 192.168.0.1<br />
bridge_ports eth0<br />
bridge_stp off<br />
bridge_fd 0<br />
if you did change some network setting run <br />
/etc/init.d/networking restart<br />
===Update===<br />
run<br />
aptitude update && aptitude full-upgrade<br />
If you get the message <br />
E: Some index files failed to download. They have been ignored, or old ones used instead.<br />
you can ignore it, or if rather not you can edit<br />
nano /etc/apt/sources.list.d/pve-enterprise.list<br />
and comment out the enterpries repository by placing a "#" in front of it. <br />
#deb https://enterprise.proxmox.com/debian wheezy pve-enterprise<br />
<br />
==Software Raid==<br />
If you do not want to use softwar raid you can continue with the next chapter.<br />
<span style="background:#ff0000">WARNING: Software raid is not supported by proxmox!</span><br />
But of course it works nevertheless, but as usual do it on your own risk.<br />
This part of the guide is based in a German guide found here[http://dominicpratt.de/proxmox-ve-3-0-software-raid/]<br />
First install the required package:<br />
apt-get update; apt-get install mdadm screen<br />
If there are any prompts on installing mdadm just ignore or press yes.<br />
<br />
If you have not done so yet shutdown and plugin the second (identical) drive.<br />
In this guide the harddrive that proxmox was installed on is /dev/sda, while the second to use in the raid is /dev/sdb. If you have different drive letter, please change them accordingly.<br />
Prepare and create raid:<br />
sfdisk -d /dev/sda | sfdisk -f /dev/sdb<br />
sfdisk -c /dev/sdb 1 fd<br />
sfdisk -c /dev/sdb 2 fd<br />
mdadm --create -l1 -n2 /dev/md0 missing /dev/sdb1<br />
mdadm --create -l1 -n2 /dev/md1 missing /dev/sdb2<br />
copy /boot to the new raid md. (Note: md with raid means "multiple device" and has nothing to do with media director)<br />
mkfs.ext3 /dev/md0<br />
mkdir /mnt/md0<br />
mount /dev/md0 /mnt/md0<br />
cp -ax /boot/* /mnt/md0<br />
Then edit the fstab<br />
nano /etc/fstab<br />
and find the line for boot that says <br />
UUID=xxxxxxxxx /boot ext3 defaults 0 1<br />
and change it to <br />
/dev/md0 /boot ext3 defaults 0 1<br />
then reboot and check with<br />
mount | grep boot<br />
that /dev/md0 is mounted on /boot.<br />
if that worked we tell grub that we want to boot from the raid:<br />
echo ‘GRUB_DISABLE_LINUX_UUID=true’ >> /etc/default/grub <br />
echo ‘GRUB_PRELOAD_MODULES=”raid dmraid”‘ >> /etc/default/grub <br />
echo raid1 >> /etc/modules <br />
echo raid1 >> /etc/initramfs-tools/modules <br />
grub-install /dev/sda --recheck<br />
grub-install /dev/sda<br />
grub-install /dev/sdb --recheck<br />
grub-install /dev/sdb<br />
update-grub<br />
update-initramfs -u<br />
Then we add sda1 to the raid (note: this might take some time, so make a coffee... or do it over the night. It might take >3 hours on 1TB). You should probably use screen.<br />
screen<br />
sfdisk -c /dev/sda 1 fd<br />
mdadm –add /dev/md0 /dev/sda1<br />
and move the root lvm onto the raid too<br />
pvcreate /dev/md1<br />
vgextend pve /dev/md1<br />
pvmove /dev/sda2 /dev/md1<br />
vgreduce pve /dev/sda2<br />
pvremove /dev/sda2<br />
sfdisk –change-id /dev/sda 2 fd<br />
mdadm –add /dev/md1 /dev/sda2<br />
with<br />
cat /proc/mdstat <br />
you can see how far the building of the new raid is, and only if it is finnished reboot.<br />
===Checking Network again===<br />
If you do not see the two network adapters (vmbr0 and vmbr1) in<br />
ifconfig<br />
you need to change edit interfaces again.<br />
nano /etc/network/interfaces<br />
mine looks like that:<br />
auto lo<br />
iface lo inet loopback<br />
auto vmbr0<br />
iface vmbr0 inet static<br />
address 192.168.0.13<br />
netmask 255.255.255.0<br />
gateway 192.168.0.1<br />
bridge_ports eth0<br />
bridge_stp off<br />
bridge_fd 0<br />
auto vmbr1<br />
iface vmbr1 inet static<br />
address 10.0.0.1<br />
netmask 255.255.255.0<br />
bridge_ports eth1<br />
bridge_stp off<br />
bridge_fd 0<br />
<br />
==Installing LinuxMCE==<br />
open a browser (on any pc in the network, not on the server) and navigate to https://server-ipadress:8006. Substitute server-ipadress for the ipadress of the proxmox-server. this is usually something like https://192.168.0.5:8006<br />
<br />
In the left column open datacenter, then your server (the servername), then local (storage) and click in the upper middle of the page on upload. Select the linuxmce iso and upload it. There are also other possibilities, including copying from a NAS, but for further information see the proxmox wiki [http://pve.proxmox.com/wiki/Main_Page].<br />
<br />
When the upload is done click on the very upper right "create VM" to create a VM.<br />
You only have one node, the VM ID you can put wathever you want, the same for the Name. Ignore the REsource Pool. <br />
Click on Next<br />
Choose Linux 3.x/2.6 Kernal (l26) and click on Next.<br />
Then choose the iso image you just uploaded and click on Next<br />
Note: Everything from here on you can change later.<br />
Change Bus/Device from IDE to virtio (better performance)<br />
Put in the Disk Size you want, and leave everything else.<br />
Choose the CPU Cores, and click Next.<br />
Choose Memory size an click Next.<br />
Change Network model to virtio (better performance) and klick next.<br />
Click Finnish to create VM.<br />
Congratulations, now you have succesfully created the first VM.</div>Deepbhttp://wiki.linuxmce.org/index.php?title=User:Deepb&diff=34473User:Deepb2013-09-12T16:36:12Z<p>Deepb: </p>
<hr />
<div>=Installation of LinuxMCE in a KVM Virtual Machine=<br />
On this page I will describe the installation process of LinuxMCE in a KVM virtual machine. As a host system I use proxmox, a very user friendly and easy to use bare metal hypervisor. <br />
<br />
==Download Required Software==<br />
<br />
Download Proxmox the latest version of proxmox: [http://www.proxmox.com/downloads/category/iso-images-pve]<br />
:At the moment of this writing the current version is Proxmox VE 3.1<br />
Download LinuxMCE [http://www.linuxmce.org/download.html]<br />
:At the moment of this writing the current version is LinuxMCE 1004 final<br />
<br />
Adittionally if you are on Windows and want to use a usb-stick: (you do not need any addidional program on Linux)<br />
:Suse Studio Image Writer [ftp://ftp.berlios.de/pub/kiwi/ImageWriter.exe] to write the image to a usb-stick. UnetBootin and Rufus do not work. <br />
<br />
==Copying Image to USB-Stick==<br />
If you want to use a CD simply burn the iso to a cd.<br />
===On Linux===<br />
Please make sure that /dev/XYZ is the right device, as this delets all content. Please also note that this is the device WITHOUT the number for the partition. SO for example /dev/sdc AND NOT /dev/sdc1 pve-cd.iso is the current proxmox iso that you downloaded. <br />
dd if=pve-cd.iso of=/dev/XYZ bs=1M<br />
===On Windows===<br />
First delete the partition of the usb-stick, else Suse Studio Image Writer might fail with a access failed error.<br />
Then rename the Proxmox iso that you downloaded from .iso to .raw. <br />
Run Suse Studio Image Writer, selct the drive and the image.<br />
<br />
==Base Installation of Proxmox==<br />
The graphical installation guide is straightforward and easy to understand.<br />
Please note though that the installer <span style="background:#ff0000">DELETS ALL PARTITIONS ON THE SELECTED DRIVE!</span> So all data on that drive is lost! You might want to unhook all harddrives that have unsaved data on it just to make sure you do not pick the wrong one by accident. <br />
<br />
==Reboot and Settings==<br />
After the base installation reboot the system, and check if you put in the right ip data in the installation process. <br />
NOTE: if you have multiple newtork cards make sure you plug the cable into the right one, if you do not have network connection try the other one.<br />
===Networking===<br />
Networking should work out of the box, if it does you can ignore this chapter and continue with [[Update]]. <br />
Else: check if there is internet connectivity by pinging something.<br />
ping google.com<br />
If you want to change the network settings <br />
nano /etc/network/interfaces<br />
if you want to use dhcp for the public interface this should look like:<br />
auto lo<br />
iface lo inet loopback<br />
auto vmbr0<br />
iface vmbr0 inet dhcp<br />
If you want to use static it should look something like that:<br />
auto lo<br />
iface lo inet loopback<br />
auto vmbr0<br />
iface vmbr0 inet static<br />
address 192.168.0.13<br />
netmask 255.255.255.0<br />
gateway 192.168.0.1<br />
bridge_ports eth0<br />
bridge_stp off<br />
bridge_fd 0<br />
if you did change some network setting run <br />
/etc/init.d/networking restart<br />
===Update===<br />
run<br />
aptitude update && aptitude full-upgrade<br />
If you get the message <br />
E: Some index files failed to download. They have been ignored, or old ones used instead.<br />
you can ignore it, or if rather not you can edit<br />
nano /etc/apt/sources.list.d/pve-enterprise.list<br />
and comment out the enterpries repository by placing a "#" in front of it. <br />
#deb https://enterprise.proxmox.com/debian wheezy pve-enterprise<br />
<br />
==Software Raid==<br />
If you do not want to use softwar raid you can continue with the next chapter.<br />
<span style="background:#ff0000">WARNING: Software raid is not supported by proxmox!</span><br />
But of course it works nevertheless, but as usual do it on your own risk.<br />
This part of the guide is based in a German guide found here[http://dominicpratt.de/proxmox-ve-3-0-software-raid/]<br />
First install the required package:<br />
apt-get update; apt-get install mdadm screen<br />
If there are any prompts on installing mdadm just ignore or press yes.<br />
<br />
If you have not done so yet shutdown and plugin the second (identical) drive.<br />
In this guide the harddrive that proxmox was installed on is /dev/sda, while the second to use in the raid is /dev/sdb. If you have different drive letter, please change them accordingly.<br />
Prepare and create raid:<br />
sfdisk -d /dev/sda | sfdisk -f /dev/sdb<br />
sfdisk -c /dev/sdb 1 fd<br />
sfdisk -c /dev/sdb 2 fd<br />
mdadm --create -l1 -n2 /dev/md0 missing /dev/sdb1<br />
mdadm --create -l1 -n2 /dev/md1 missing /dev/sdb2<br />
copy /boot to the new raid md. (Note: md with raid means "multiple device" and has nothing to do with media director)<br />
mkfs.ext3 /dev/md0<br />
mkdir /mnt/md0<br />
mount /dev/md0 /mnt/md0<br />
cp -ax /boot/* /mnt/md0<br />
Then edit the fstab<br />
nano /etc/fstab<br />
and find the line for boot that says <br />
UUID=xxxxxxxxx /boot ext3 defaults 0 1<br />
and change it to <br />
/dev/md0 /boot ext3 defaults 0 1<br />
then reboot and check with<br />
mount | grep boot<br />
that /dev/md0 is mounted on /boot.<br />
if that worked we tell grub that we want to boot from the raid:<br />
echo ‘GRUB_DISABLE_LINUX_UUID=true’ >> /etc/default/grub <br />
echo ‘GRUB_PRELOAD_MODULES=”raid dmraid”‘ >> /etc/default/grub <br />
echo raid1 >> /etc/modules <br />
echo raid1 >> /etc/initramfs-tools/modules <br />
grub-install /dev/sda --recheck<br />
grub-install /dev/sda<br />
grub-install /dev/sdb --recheck<br />
grub-install /dev/sdb<br />
update-grub<br />
update-initramfs -u<br />
Then we add sda1 to the raid (note: this might take some time, so make a coffee... or do it over the night. It might take >3 hours on 1TB). You should probably use screen.<br />
screen<br />
sfdisk -c /dev/sda 1 fd<br />
mdadm –add /dev/md0 /dev/sda1<br />
and move the root lvm onto the raid too<br />
pvcreate /dev/md1<br />
vgextend pve /dev/md1<br />
pvmove /dev/sda2 /dev/md1<br />
vgreduce pve /dev/sda2<br />
pvremove /dev/sda2<br />
sfdisk –change-id /dev/sda 2 fd<br />
mdadm –add /dev/md1 /dev/sda2<br />
with<br />
cat /proc/mdstat <br />
you can see how far the building of the new raid is, and only if it is finnished reboot.<br />
===Checking Network again===<br />
If you do not see the two network adapters (vmbr0 and vmbr1) in<br />
ifconfig<br />
you need to change edit interfaces again.<br />
nano /etc/network/interfaces<br />
mine looks like that:<br />
auto lo<br />
iface lo inet loopback<br />
auto vmbr0<br />
iface vmbr0 inet static<br />
address 192.168.0.13<br />
netmask 255.255.255.0<br />
gateway 192.168.0.1<br />
bridge_ports eth0<br />
bridge_stp off<br />
bridge_fd 0<br />
auto vmbr1<br />
iface vmbr1 inet static<br />
address 10.0.0.1<br />
netmask 255.255.255.0<br />
bridge_ports eth1<br />
bridge_stp off<br />
bridge_fd 0<br />
<br />
==Installing LinuxMCE==<br />
open a browser (on any pc in the network, not on the server) and navigate to https://server-ipadress:8006. Substitute server-ipadress for the ipadress of the proxmox-server. this is usually something like https://192.168.0.5:8006<br />
<br />
In the left column open datacenter, then your server (the servername), then local (storage) and click in the upper middle of the page on upload. Select the linuxmce iso and upload it. There are also other possibilities, including copying from a NAS, but for further information see the proxmox wiki [http://pve.proxmox.com/wiki/Main_Page].<br />
<br />
When the upload is done click on the very upper right "create VM" to create a VM.</div>Deepbhttp://wiki.linuxmce.org/index.php?title=User:Deepb&diff=34472User:Deepb2013-09-12T15:46:17Z<p>Deepb: </p>
<hr />
<div>=Installation of LinuxMCE in a KVM Virtual Machine=<br />
On this page I will describe the installation process of LinuxMCE in a KVM virtual machine. As a host system I use proxmox, a very user friendly and easy to use bare metal hypervisor. <br />
<br />
==Download Required Software==<br />
<br />
Download Proxmox the latest version of proxmox: [http://www.proxmox.com/downloads/category/iso-images-pve]<br />
:At the moment of this writing the current version is Proxmox VE 3.1<br />
Download LinuxMCE [http://www.linuxmce.org/download.html]<br />
:At the moment of this writing the current version is LinuxMCE 1004 final<br />
<br />
Adittionally if you are on Windows and want to use a usb-stick: (you do not need any addidional program on Linux)<br />
:Suse Studio Image Writer [ftp://ftp.berlios.de/pub/kiwi/ImageWriter.exe] to write the image to a usb-stick. UnetBootin and Rufus do not work. <br />
<br />
==Copying Image to USB-Stick==<br />
If you want to use a CD simply burn the iso to a cd.<br />
===On Linux===<br />
Please make sure that /dev/XYZ is the right device, as this delets all content. Please also note that this is the device WITHOUT the number for the partition. SO for example /dev/sdc AND NOT /dev/sdc1 pve-cd.iso is the current proxmox iso that you downloaded. <br />
dd if=pve-cd.iso of=/dev/XYZ bs=1M<br />
===On Windows===<br />
First delete the partition of the usb-stick, else Suse Studio Image Writer might fail with a access failed error.<br />
Then rename the Proxmox iso that you downloaded from .iso to .raw. <br />
Run Suse Studio Image Writer, selct the drive and the image.<br />
<br />
==Base Installation of Proxmox==<br />
The graphical installation guide is straightforward and easy to understand.<br />
Please note though that the installer <span style="background:#ff0000">DELETS ALL PARTITIONS ON THE SELECTED DRIVE!</span> So all data on that drive is lost! You might want to unhook all harddrives that have unsaved data on it just to make sure you do not pick the wrong one by accident. <br />
<br />
==Reboot and Settings==<br />
After the base installation reboot the system, and check if you put in the right ip data in the installation process. <br />
NOTE: if you have multiple newtork cards make sure you plug the cable into the right one, if you do not have network connection try the other one.<br />
===Networking===<br />
Networking should work out of the box, if it does you can ignore this chapter and continue with [[Update]]. <br />
Else: check if there is internet connectivity by pinging something.<br />
ping google.com<br />
If you want to change the network settings <br />
nano /etc/network/interfaces<br />
if you want to use dhcp for the public interface this should look like:<br />
auto lo<br />
iface lo inet loopback<br />
auto vmbr0<br />
iface vmbr0 inet dhcp<br />
If you want to use static it should look something like that:<br />
auto lo<br />
iface lo inet loopback<br />
auto vmbr0<br />
iface vmbr0 inet static<br />
address 192.168.0.13<br />
netmask 255.255.255.0<br />
gateway 192.168.0.1<br />
bridge_ports eth0<br />
bridge_stp off<br />
bridge_fd 0<br />
if you did change some network setting run <br />
/etc/init.d/networking restart<br />
===Update===<br />
run<br />
aptitude update && aptitude full-upgrade<br />
If you get the message <br />
E: Some index files failed to download. They have been ignored, or old ones used instead.<br />
you can ignore it, or if rather not you can edit<br />
nano /etc/apt/sources.list.d/pve-enterprise.list<br />
and comment out the enterpries repository by placing a "#" in front of it. <br />
#deb https://enterprise.proxmox.com/debian wheezy pve-enterprise<br />
<br />
==Software Raid==<br />
If you do not want to use softwar raid you can continue with the next chapter.<br />
<span style="background:#ff0000">WARNING: Software raid is not supported by proxmox!</span><br />
But of course it works nevertheless, but as usual do it on your own risk.<br />
This part of the guide is based in a German guide found here[http://dominicpratt.de/proxmox-ve-3-0-software-raid/]<br />
First install the required package:<br />
apt-get update; apt-get install mdadm screen<br />
If there are any prompts on installing mdadm just ignore or press yes.<br />
<br />
If you have not done so yet shutdown and plugin the second (identical) drive.<br />
In this guide the harddrive that proxmox was installed on is /dev/sda, while the second to use in the raid is /dev/sdb. If you have different drive letter, please change them accordingly.<br />
Prepare and create raid:<br />
sfdisk -d /dev/sda | sfdisk -f /dev/sdb<br />
sfdisk -c /dev/sdb 1 fd<br />
sfdisk -c /dev/sdb 2 fd<br />
mdadm --create -l1 -n2 /dev/md0 missing /dev/sdb1<br />
mdadm --create -l1 -n2 /dev/md1 missing /dev/sdb2<br />
copy /boot to the new raid md. (Note: md with raid means "multiple device" and has nothing to do with media director)<br />
mkfs.ext3 /dev/md0<br />
mkdir /mnt/md0<br />
mount /dev/md0 /mnt/md0<br />
cp -ax /boot/* /mnt/md0<br />
Then edit the fstab<br />
nano /etc/fstab<br />
and find the line for boot that says <br />
UUID=xxxxxxxxx /boot ext3 defaults 0 1<br />
and change it to <br />
/dev/md0 /boot ext3 defaults 0 1<br />
then reboot and check with<br />
mount | grep boot<br />
that /dev/md0 is mounted on /boot.<br />
if that worked we tell grub that we want to boot from the raid:<br />
echo ‘GRUB_DISABLE_LINUX_UUID=true’ >> /etc/default/grub <br />
echo ‘GRUB_PRELOAD_MODULES=”raid dmraid”‘ >> /etc/default/grub <br />
echo raid1 >> /etc/modules <br />
echo raid1 >> /etc/initramfs-tools/modules <br />
grub-install /dev/sda --recheck<br />
grub-install /dev/sda<br />
grub-install /dev/sdb --recheck<br />
grub-install /dev/sdb<br />
update-grub<br />
update-initramfs -u<br />
Then we add sda1 to the raid (note: this might take some time, so make a coffee... or do it over the night. It might take >3 hours on 1TB). You should probably use screen.<br />
screen<br />
sfdisk -c /dev/sda 1 fd<br />
mdadm –add /dev/md0 /dev/sda1<br />
and move the root lvm onto the raid too<br />
pvcreate /dev/md1<br />
vgextend pve /dev/md1<br />
pvmove /dev/sda2 /dev/md1<br />
vgreduce pve /dev/sda2<br />
pvremove /dev/sda2<br />
sfdisk –change-id /dev/sda 2 fd<br />
mdadm –add /dev/md1 /dev/sda2<br />
with<br />
cat /proc/mdstat <br />
you can see how far the building of the new raid is, and only if it is finnished reboot.<br />
==Installing LinuxMCE==<br />
open a browser (on any pc in the network, not on the server) and navigate to https://server-ipadress:8006. Substitute server-ipadress for the ipadress of the proxmox-server. this is usually something like https://192.168.0.5:8006<br />
<br />
In the left column open datacenter, then your server (the servername), then local (storage) and click in the upper middle of the page on upload. Select the linuxmce iso and upload it. There are also other possibilities, including copying from a NAS, but for further information see the proxmox wiki [http://pve.proxmox.com/wiki/Main_Page].<br />
<br />
When the upload is done click on the very upper right "create VM" to create a VM.</div>Deepbhttp://wiki.linuxmce.org/index.php?title=User:Deepb&diff=34471User:Deepb2013-09-12T15:44:27Z<p>Deepb: </p>
<hr />
<div>=Installation of LinuxMCE in a KVM Virtual Machine=<br />
On this page I will describe the installation process of LinuxMCE in a KVM virtual machine. As a host system I use proxmox, a very user friendly and easy to use bare metal hypervisor. <br />
<br />
==Download Required Software==<br />
<br />
Download Proxmox the latest version of proxmox: [http://www.proxmox.com/downloads/category/iso-images-pve]<br />
:At the moment of this writing the current version is Proxmox VE 3.1<br />
Download LinuxMCE [http://www.linuxmce.org/download.html]<br />
:At the moment of this writing the current version is LinuxMCE 1004 final<br />
<br />
Adittionally if you are on Windows and want to use a usb-stick: (you do not need any addidional program on Linux)<br />
:Suse Studio Image Writer [ftp://ftp.berlios.de/pub/kiwi/ImageWriter.exe] to write the image to a usb-stick. UnetBootin and Rufus do not work. <br />
<br />
==Copying Image to USB-Stick==<br />
If you want to use a CD simply burn the iso to a cd.<br />
===On Linux===<br />
Please make sure that /dev/XYZ is the right device, as this delets all content. Please also note that this is the device WITHOUT the number for the partition. SO for example /dev/sdc AND NOT /dev/sdc1 pve-cd.iso is the current proxmox iso that you downloaded. <br />
dd if=pve-cd.iso of=/dev/XYZ bs=1M<br />
===On Windows===<br />
First delete the partition of the usb-stick, else Suse Studio Image Writer might fail with a access failed error.<br />
Then rename the Proxmox iso that you downloaded from .iso to .raw. <br />
Run Suse Studio Image Writer, selct the drive and the image.<br />
<br />
==Base Installation of Proxmox==<br />
The graphical installation guide is straightforward and easy to understand.<br />
Please note though that the installer <span style="background:#ff0000">DELETS ALL PARTITIONS ON THE SELECTED DRIVE!</span> So all data on that drive is lost! You might want to unhook all harddrives that have unsaved data on it just to make sure you do not pick the wrong one by accident. <br />
<br />
==Reboot and Settings==<br />
After the base installation reboot the system, and check if you put in the right ip data in the installation process. <br />
NOTE: if you have multiple newtork cards make sure you plug the cable into the right one, if you do not have network connection try the other one.<br />
===Networking===<br />
Networking should work out of the box, if it does you can ignore this chapter and continue with [[Update]]. <br />
Else: check if there is internet connectivity by pinging something.<br />
ping google.com<br />
If you want to change the network settings <br />
nano /etc/network/interfaces<br />
if you want to use dhcp for the public interface this should look like:<br />
auto lo<br />
iface lo inet loopback<br />
auto vmbr0<br />
iface vmbr0 inet dhcp<br />
If you want to use static it should look something like that:<br />
auto lo<br />
iface lo inet loopback<br />
auto vmbr0<br />
iface vmbr0 inet static<br />
address 192.168.0.13<br />
netmask 255.255.255.0<br />
gateway 192.168.0.1<br />
bridge_ports eth0<br />
bridge_stp off<br />
bridge_fd 0<br />
if you did change some network setting run <br />
/etc/init.d/networking restart<br />
===Update===<br />
run<br />
aptitude update && aptitude full-upgrade<br />
If you get the message <br />
E: Some index files failed to download. They have been ignored, or old ones used instead.<br />
you can ignore it, or if rather not you can edit<br />
nano /etc/apt/sources.list.d/pve-enterprise.list<br />
and comment out the enterpries repository by placing a "#" in front of it. <br />
#deb https://enterprise.proxmox.com/debian wheezy pve-enterprise<br />
<br />
==Software Raid==<br />
If you do not want to use softwar raid you can continue with the next chapter.<br />
<span style="background:#ff0000">WARNING: Software raid is not supported by proxmox!</span><br />
But of course it works nevertheless, but as usual do it on your own risk.<br />
This part of the guide is based in a German guide found here[http://dominicpratt.de/proxmox-ve-3-0-software-raid/]<br />
First install the required package:<br />
apt-get update; apt-get install mdadm screen<br />
If there are any prompts on installing mdadm just ignore or press yes.<br />
<br />
If you have not done so yet shutdown and plugin the second (identical) drive.<br />
In this guide the harddrive that proxmox was installed on is /dev/sda, while the second to use in the raid is /dev/sdb. If you have different drive letter, please change them accordingly.<br />
Prepare and create raid:<br />
sfdisk -d /dev/sda | sfdisk -f /dev/sdb<br />
sfdisk -c /dev/sdb 1 fd<br />
sfdisk -c /dev/sdb 2 fd<br />
mdadm --create -l1 -n2 /dev/md0 missing /dev/sdb1<br />
mdadm --create -l1 -n2 /dev/md1 missing /dev/sdb2<br />
copy /boot to the new raid md. (Note: md with raid means "multiple device" and has nothing to do with media director)<br />
mkfs.ext3 /dev/md0<br />
mkdir /mnt/md0<br />
mount /dev/md0 /mnt/md0<br />
cp -ax /boot/* /mnt/md0<br />
Then edit the fstab<br />
nano /etc/fstab<br />
and find the line for boot that says <br />
UUID=xxxxxxxxx /boot ext3 defaults 0 1<br />
and change it to <br />
/dev/md0 /boot ext3 defaults 0 1<br />
then reboot and check with<br />
mount | grep boot<br />
that /dev/md0 is mounted on /boot.<br />
if that worked we tell grub that we want to boot from the raid:<br />
echo ‘GRUB_DISABLE_LINUX_UUID=true’ >> /etc/default/grub <br />
echo ‘GRUB_PRELOAD_MODULES=”raid dmraid”‘ >> /etc/default/grub <br />
echo raid1 >> /etc/modules <br />
echo raid1 >> /etc/initramfs-tools/modules <br />
grub-install /dev/sda --recheck<br />
grub-install /dev/sda<br />
grub-install /dev/sdb --recheck<br />
grub-install /dev/sdb<br />
update-grub<br />
update-initramfs -u<br />
Then we add sda1 to the raid (note: this might take some time, so make a coffee... or do it over the night. It might take >3 hours on 1TB). You should probably use screen.<br />
screen<br />
sfdisk -c /dev/sda 1 fd<br />
mdadm –add /dev/md0 /dev/sda1<br />
and move the root lvm onto the raid too<br />
pvcreate /dev/md1<br />
vgextend pve /dev/md1<br />
pvmove /dev/sda2 /dev/md1<br />
vgreduce pve /dev/sda2<br />
pvremove /dev/sda2<br />
sfdisk –change-id /dev/sda 2 fd<br />
mdadm –add /dev/md1 /dev/sda2<br />
with<br />
cat /proc/mdstat <br />
you can see how far the building of the new raid is, and only if it is finnished reboot.<br />
==Installing LinuxMCE==<br />
open a browser (on any pc in the network, not on the server) and navigate to https://server-ipadress:8006. Substitute server-ipadress for the ipadress of the proxmox-server. this is usually something like https://192.168.0.5:8006<br />
In the left column open datacenter, then your server (the servername), then local (storage) and click in the upper middle of the page on upload. Select the linuxmce iso and upload it. There are also other possibilities, including copying from a NAS, but for further information see the proxmox wiki [http://pve.proxmox.com/wiki/Main_Page].</div>Deepbhttp://wiki.linuxmce.org/index.php?title=User:Deepb&diff=34470User:Deepb2013-09-12T15:39:57Z<p>Deepb: </p>
<hr />
<div>=Installation of LinuxMCE in a KVM Virtual Machine=<br />
On this page I will describe the installation process of LinuxMCE in a KVM virtual machine. As a host system I use proxmox, a very user friendly and easy to use bare metal hypervisor. <br />
<br />
==Download Required Software==<br />
<br />
Download Proxmox the latest version of proxmox: [http://www.proxmox.com/downloads/category/iso-images-pve]<br />
:At the moment of this writing the current version is Proxmox VE 3.1<br />
Download LinuxMCE [http://www.linuxmce.org/download.html]<br />
:At the moment of this writing the current version is LinuxMCE 1004 final<br />
<br />
Adittionally if you are on Windows and want to use a usb-stick: (you do not need any addidional program on Linux)<br />
:Suse Studio Image Writer [ftp://ftp.berlios.de/pub/kiwi/ImageWriter.exe] to write the image to a usb-stick. UnetBootin and Rufus do not work. <br />
<br />
==Copying Image to USB-Stick==<br />
If you want to use a CD simply burn the iso to a cd.<br />
===On Linux===<br />
Please make sure that /dev/XYZ is the right device, as this delets all content. Please also note that this is the device WITHOUT the number for the partition. SO for example /dev/sdc AND NOT /dev/sdc1 pve-cd.iso is the current proxmox iso that you downloaded. <br />
dd if=pve-cd.iso of=/dev/XYZ bs=1M<br />
===On Windows===<br />
First delete the partition of the usb-stick, else Suse Studio Image Writer might fail with a access failed error.<br />
Then rename the Proxmox iso that you downloaded from .iso to .raw. <br />
Run Suse Studio Image Writer, selct the drive and the image.<br />
<br />
==Base Installation of Proxmox==<br />
The graphical installation guide is straightforward and easy to understand.<br />
Please note though that the installer <span style="background:#ff0000">DELETS ALL PARTITIONS ON THE SELECTED DRIVE!</span> So all data on that drive is lost! You might want to unhook all harddrives that have unsaved data on it just to make sure you do not pick the wrong one by accident. <br />
<br />
==Reboot and Settings==<br />
After the base installation reboot the system, and check if you put in the right ip data in the installation process. <br />
NOTE: if you have multiple newtork cards make sure you plug the cable into the right one, if you do not have network connection try the other one.<br />
===Networking===<br />
Networking should work out of the box, if it does you can ignore this chapter and continue with [[Update]]. <br />
Else: check if there is internet connectivity by pinging something.<br />
ping google.com<br />
If you want to change the network settings <br />
nano /etc/network/interfaces<br />
if you want to use dhcp for the public interface this should look like:<br />
auto lo<br />
iface lo inet loopback<br />
auto vmbr0<br />
iface vmbr0 inet dhcp<br />
If you want to use static it should look something like that:<br />
auto lo<br />
iface lo inet loopback<br />
auto vmbr0<br />
iface vmbr0 inet static<br />
address 192.168.0.13<br />
netmask 255.255.255.0<br />
gateway 192.168.0.1<br />
bridge_ports eth0<br />
bridge_stp off<br />
bridge_fd 0<br />
if you did change some network setting run <br />
/etc/init.d/networking restart<br />
===Update===<br />
run<br />
aptitude update && aptitude full-upgrade<br />
If you get the message <br />
E: Some index files failed to download. They have been ignored, or old ones used instead.<br />
you can ignore it, or if rather not you can edit<br />
nano /etc/apt/sources.list.d/pve-enterprise.list<br />
and comment out the enterpries repository by placing a "#" in front of it. <br />
#deb https://enterprise.proxmox.com/debian wheezy pve-enterprise<br />
<br />
==Software Raid==<br />
If you do not want to use softwar raid you can continue with the next chapter.<br />
<span style="background:#ff0000">WARNING: Software raid is not supported by proxmox!</span><br />
But of course it works nevertheless, but as usual do it on your own risk.<br />
This part of the guide is based in a German guide found here[http://dominicpratt.de/proxmox-ve-3-0-software-raid/]<br />
First install the required package:<br />
apt-get update; apt-get install mdadm screen<br />
If there are any prompts on installing mdadm just ignore or press yes.<br />
<br />
If you have not done so yet shutdown and plugin the second (identical) drive.<br />
In this guide the harddrive that proxmox was installed on is /dev/sda, while the second to use in the raid is /dev/sdb. If you have different drive letter, please change them accordingly.<br />
Prepare and create raid:<br />
sfdisk -d /dev/sda | sfdisk -f /dev/sdb<br />
sfdisk -c /dev/sdb 1 fd<br />
sfdisk -c /dev/sdb 2 fd<br />
mdadm --create -l1 -n2 /dev/md0 missing /dev/sdb1<br />
mdadm --create -l1 -n2 /dev/md1 missing /dev/sdb2<br />
copy /boot to the new raid md. (Note: md with raid means "multiple device" and has nothing to do with media director)<br />
mkfs.ext3 /dev/md0<br />
mkdir /mnt/md0<br />
mount /dev/md0 /mnt/md0<br />
cp -ax /boot/* /mnt/md0<br />
Then edit the fstab<br />
nano /etc/fstab<br />
and find the line for boot that says <br />
UUID=xxxxxxxxx /boot ext3 defaults 0 1<br />
and change it to <br />
/dev/md0 /boot ext3 defaults 0 1<br />
then reboot and check with<br />
mount | grep boot<br />
that /dev/md0 is mounted on /boot.<br />
if that worked we tell grub that we want to boot from the raid:<br />
echo ‘GRUB_DISABLE_LINUX_UUID=true’ >> /etc/default/grub <br />
echo ‘GRUB_PRELOAD_MODULES=”raid dmraid”‘ >> /etc/default/grub <br />
echo raid1 >> /etc/modules <br />
echo raid1 >> /etc/initramfs-tools/modules <br />
grub-install /dev/sda --recheck<br />
grub-install /dev/sda<br />
grub-install /dev/sdb --recheck<br />
grub-install /dev/sdb<br />
update-grub<br />
update-initramfs -u<br />
Then we add sda1 to the raid (note: this might take some time, so make a coffee... or do it over the night. It might take >3 hours on 1TB). YOu should probably use screen.<br />
screen<br />
sfdisk -c /dev/sda 1 fd<br />
mdadm –add /dev/md0 /dev/sda1<br />
and move the root lvm onto the raid too<br />
pvcreate /dev/md1<br />
vgextend pve /dev/md1<br />
pvmove /dev/sda2 /dev/md1<br />
vgreduce pve /dev/sda2<br />
pvremove /dev/sda2<br />
sfdisk –change-id /dev/sda 2 fd<br />
mdadm –add /dev/md1 /dev/sda2<br />
with<br />
cat /proc/mdstat <br />
you can see how far the building of the new raid is, and only if it is finnished reboot.</div>Deepbhttp://wiki.linuxmce.org/index.php?title=User:Deepb&diff=34469User:Deepb2013-09-12T15:38:25Z<p>Deepb: </p>
<hr />
<div>=Installation of LinuxMCE in a KVM Virtual Machine=<br />
On this page I will describe the installation process of LinuxMCE in a KVM virtual machine. As a host system I use proxmox, a very user friendly and easy to use bare metal hypervisor. <br />
<br />
==Download Required Software==<br />
<br />
Download Proxmox the latest version of proxmox: [http://www.proxmox.com/downloads/category/iso-images-pve]<br />
:At the moment of this writing the current version is Proxmox VE 3.1<br />
Download LinuxMCE [http://www.linuxmce.org/download.html]<br />
:At the moment of this writing the current version is LinuxMCE 1004 final<br />
<br />
Adittionally if you are on Windows and want to use a usb-stick: (you do not need any addidional program on Linux)<br />
:Suse Studio Image Writer [ftp://ftp.berlios.de/pub/kiwi/ImageWriter.exe] to write the image to a usb-stick. UnetBootin and Rufus do not work. <br />
<br />
==Copying Image to USB-Stick==<br />
If you want to use a CD simply burn the iso to a cd.<br />
===On Linux===<br />
Please make sure that /dev/XYZ is the right device, as this delets all content. Please also note that this is the device WITHOUT the number for the partition. SO for example /dev/sdc AND NOT /dev/sdc1 pve-cd.iso is the current proxmox iso that you downloaded. <br />
dd if=pve-cd.iso of=/dev/XYZ bs=1M<br />
===On Windows===<br />
First delete the partition of the usb-stick, else Suse Studio Image Writer might fail with a access failed error.<br />
Then rename the Proxmox iso that you downloaded from .iso to .raw. <br />
Run Suse Studio Image Writer, selct the drive and the image.<br />
<br />
==Base Installation of Proxmox==<br />
The graphical installation guide is straightforward and easy to understand.<br />
Please note though that the installer <span style="background:#ff0000">DELETS ALL PARTITIONS ON THE SELECTED DRIVE!</span> So all data on that drive is lost! You might want to unhook all harddrives that have unsaved data on it just to make sure you do not pick the wrong one by accident. <br />
<br />
==Reboot and Settings==<br />
After the base installation reboot the system, and check if you put in the right ip data in the installation process. <br />
NOTE: if you have multiple newtork cards make sure you plug the cable into the right one, if you do not have network connection try the other one.<br />
===Networking===<br />
Networking should work out of the box, if it does you can ignore this chapter and continue with [[Update]]. <br />
Else: check if there is internet connectivity by pinging something.<br />
ping google.com<br />
If you want to change the network settings <br />
nano /etc/network/interfaces<br />
if you want to use dhcp for the public interface this should look like:<br />
auto lo<br />
iface lo inet loopback<br />
auto vmbr0<br />
iface vmbr0 inet dhcp<br />
If you want to use static it should look something like that:<br />
auto lo<br />
iface lo inet loopback<br />
auto vmbr0<br />
iface vmbr0 inet static<br />
address 192.168.0.13<br />
netmask 255.255.255.0<br />
gateway 192.168.0.1<br />
bridge_ports eth0<br />
bridge_stp off<br />
bridge_fd 0<br />
if you did change some network setting run <br />
/etc/init.d/networking restart<br />
===Update===<br />
run<br />
aptitude update && aptitude full-upgrade<br />
If you get the message <br />
E: Some index files failed to download. They have been ignored, or old ones used instead.<br />
you can ignore it, or if rather not you can edit<br />
nano /etc/apt/sources.list.d/pve-enterprise.list<br />
and comment out the enterpries repository by placing a "#" in front of it. <br />
#deb https://enterprise.proxmox.com/debian wheezy pve-enterprise<br />
<br />
==Software Raid==<br />
If you do not want to use softwar raid you can continue with the next chapter.<br />
<span style="background:#ff0000">WARNING: Software raid is not supported by proxmox!</span><br />
But of course it works nevertheless, but as usual do it on your own risk.<br />
This part of the guide is based in a German guide found here[http://dominicpratt.de/proxmox-ve-3-0-software-raid/]<br />
First install the required package:<br />
apt-get update; apt-get install mdadm screen<br />
If there are any prompts on installing mdadm just ignore or press yes.<br />
===Prepare Raid===<br />
If you have not done so yet shutdown and plugin the second (identical) drive.<br />
In this guide the harddrive that proxmox was installed on is /dev/sda, while the second to use in the raid is /dev/sdb. If you have different drive letter, please change them accordingly.<br />
Prepare and create raid:<br />
sfdisk -d /dev/sda | sfdisk -f /dev/sdb<br />
sfdisk -c /dev/sdb 1 fd<br />
sfdisk -c /dev/sdb 2 fd<br />
mdadm --create -l1 -n2 /dev/md0 missing /dev/sdb1<br />
mdadm --create -l1 -n2 /dev/md1 missing /dev/sdb2<br />
copy /boot to the new raid md. (Note: md with raid means "multiple device" and has nothing to do with media director)<br />
mkfs.ext3 /dev/md0<br />
mkdir /mnt/md0<br />
mount /dev/md0 /mnt/md0<br />
cp -ax /boot/* /mnt/md0<br />
Then edit the fstab<br />
nano /etc/fstab<br />
and find the line for boot that says <br />
UUID=xxxxxxxxx /boot ext3 defaults 0 1<br />
and change it to <br />
/dev/md0 /boot ext3 defaults 0 1<br />
then reboot and check with<br />
mount | grep boot<br />
that /dev/md0 is mounted on /boot.<br />
if that worked we tell grub that we want to boot from the raid:<br />
echo ‘GRUB_DISABLE_LINUX_UUID=true’ >> /etc/default/grub <br />
echo ‘GRUB_PRELOAD_MODULES=”raid dmraid”‘ >> /etc/default/grub <br />
echo raid1 >> /etc/modules <br />
echo raid1 >> /etc/initramfs-tools/modules <br />
grub-install /dev/sda --recheck<br />
grub-install /dev/sda<br />
grub-install /dev/sdb --recheck<br />
grub-install /dev/sdb<br />
update-grub<br />
update-initramfs -u<br />
Then we add sda1 to the raid (note: this might take some time, so make a coffee... or do it over the night. It might take >3 hours on 1TB). YOu should probably use screen.<br />
screen<br />
sfdisk -c /dev/sda 1 fd<br />
mdadm –add /dev/md0 /dev/sda1<br />
and move the root lvm onto the raid too<br />
pvcreate /dev/md1<br />
vgextend pve /dev/md1<br />
pvmove /dev/sda2 /dev/md1<br />
vgreduce pve /dev/sda2<br />
pvremove /dev/sda2<br />
sfdisk –change-id /dev/sda 2 fd<br />
mdadm –add /dev/md1 /dev/sda2</div>Deepbhttp://wiki.linuxmce.org/index.php?title=User:Deepb&diff=34468User:Deepb2013-09-12T15:30:20Z<p>Deepb: </p>
<hr />
<div>=Installation of LinuxMCE in a KVM Virtual Machine=<br />
On this page I will describe the installation process of LinuxMCE in a KVM virtual machine. As a host system I use proxmox, a very user friendly and easy to use bare metal hypervisor. <br />
<br />
==Download Required Software==<br />
<br />
Download Proxmox the latest version of proxmox: [http://www.proxmox.com/downloads/category/iso-images-pve]<br />
:At the moment of this writing the current version is Proxmox VE 3.1<br />
Download LinuxMCE [http://www.linuxmce.org/download.html]<br />
:At the moment of this writing the current version is LinuxMCE 1004 final<br />
<br />
Adittionally if you are on Windows and want to use a usb-stick: (you do not need any addidional program on Linux)<br />
:Suse Studio Image Writer [ftp://ftp.berlios.de/pub/kiwi/ImageWriter.exe] to write the image to a usb-stick. UnetBootin and Rufus do not work. <br />
<br />
==Copying Image to USB-Stick==<br />
If you want to use a CD simply burn the iso to a cd.<br />
===On Linux===<br />
Please make sure that /dev/XYZ is the right device, as this delets all content. Please also note that this is the device WITHOUT the number for the partition. SO for example /dev/sdc AND NOT /dev/sdc1 pve-cd.iso is the current proxmox iso that you downloaded. <br />
dd if=pve-cd.iso of=/dev/XYZ bs=1M<br />
===On Windows===<br />
First delete the partition of the usb-stick, else Suse Studio Image Writer might fail with a access failed error.<br />
Then rename the Proxmox iso that you downloaded from .iso to .raw. <br />
Run Suse Studio Image Writer, selct the drive and the image.<br />
<br />
==Base Installation of Proxmox==<br />
The graphical installation guide is straightforward and easy to understand.<br />
Please note though that the installer <span style="background:#ff0000">DELETS ALL PARTITIONS ON THE SELECTED DRIVE!</span> So all data on that drive is lost! You might want to unhook all harddrives that have unsaved data on it just to make sure you do not pick the wrong one by accident. <br />
<br />
==Reboot and Settings==<br />
After the base installation reboot the system, and check if you put in the right ip data in the installation process. <br />
NOTE: if you have multiple newtork cards make sure you plug the cable into the right one, if you do not have network connection try the other one.<br />
===Networking===<br />
Networking should work out of the box, if it does you can ignore this chapter and continue with [[Update]]. <br />
Else: check if there is internet connectivity by pinging something.<br />
ping google.com<br />
If you want to change the network settings <br />
nano /etc/network/interfaces<br />
if you want to use dhcp for the public interface this should look like:<br />
auto lo<br />
iface lo inet loopback<br />
auto vmbr0<br />
iface vmbr0 inet dhcp<br />
If you want to use static it should look something like that:<br />
auto lo<br />
iface lo inet loopback<br />
auto vmbr0<br />
iface vmbr0 inet static<br />
address 192.168.0.13<br />
netmask 255.255.255.0<br />
gateway 192.168.0.1<br />
bridge_ports eth0<br />
bridge_stp off<br />
bridge_fd 0<br />
if you did change some network setting run <br />
/etc/init.d/networking restart<br />
===Update===<br />
run<br />
aptitude update && aptitude full-upgrade<br />
If you get the message <br />
E: Some index files failed to download. They have been ignored, or old ones used instead.<br />
you can ignore it, or if rather not you can edit<br />
nano /etc/apt/sources.list.d/pve-enterprise.list<br />
and comment out the enterpries repository by placing a "#" in front of it. <br />
#deb https://enterprise.proxmox.com/debian wheezy pve-enterprise<br />
<br />
==Software Raid==<br />
If you do not want to use softwar raid you can continue with the next chapter.<br />
<span style="background:#ff0000">WARNING: Software raid is not supported by proxmox!</span><br />
But of course it works nevertheless, but as usual do it on your own risk.<br />
This part of the guide is based in a German guide found here[http://dominicpratt.de/proxmox-ve-3-0-software-raid/]<br />
First install the required package:<br />
apt-get update; apt-get install mdadm<br />
If there are any prompts on installing mdadm just ignore or press yes.<br />
===Prepare Raid===<br />
If you have not done so yet shutdown and plugin the second (identical) drive.<br />
In this guide the harddrive that proxmox was installed on is /dev/sda, while the second to use in the raid is /dev/sdb. If you have different drive letter, please change them accordingly.<br />
Prepare and create raid:<br />
sfdisk -d /dev/sda | sfdisk -f /dev/sdb<br />
sfdisk -c /dev/sdb 1 fd<br />
sfdisk -c /dev/sdb 2 fd<br />
mdadm --create -l1 -n2 /dev/md0 missing /dev/sdb1<br />
mdadm --create -l1 -n2 /dev/md1 missing /dev/sdb2<br />
copy /boot to the new raid md. (Note: md with raid means "multiple device" and has nothing to do with media director)<br />
mkfs.ext3 /dev/md0<br />
mkdir /mnt/md0<br />
mount /dev/md0 /mnt/md0<br />
cp -ax /boot/* /mnt/md0<br />
Then edit the fstab<br />
nano /etc/fstab<br />
and find the line for boot that says <br />
UUID=xxxxxxxxx /boot ext3 defaults 0 1<br />
and change it to <br />
/dev/md0 /boot ext3 defaults 0 1</div>Deepbhttp://wiki.linuxmce.org/index.php?title=User:Deepb&diff=34467User:Deepb2013-09-12T15:25:20Z<p>Deepb: </p>
<hr />
<div>=Installation of LinuxMCE in a KVM Virtual Machine=<br />
On this page I will describe the installation process of LinuxMCE in a KVM virtual machine. As a host system I use proxmox, a very user friendly and easy to use bare metal hypervisor. <br />
<br />
==Download Required Software==<br />
<br />
Download Proxmox the latest version of proxmox: [http://www.proxmox.com/downloads/category/iso-images-pve]<br />
:At the moment of this writing the current version is Proxmox VE 3.1<br />
Download LinuxMCE [http://www.linuxmce.org/download.html]<br />
:At the moment of this writing the current version is LinuxMCE 1004 final<br />
<br />
Adittionally if you are on Windows and want to use a usb-stick: (you do not need any addidional program on Linux)<br />
:Suse Studio Image Writer [ftp://ftp.berlios.de/pub/kiwi/ImageWriter.exe] to write the image to a usb-stick. UnetBootin and Rufus do not work. <br />
<br />
==Copying Image to USB-Stick==<br />
If you want to use a CD simply burn the iso to a cd.<br />
===On Linux===<br />
Please make sure that /dev/XYZ is the right device, as this delets all content. Please also note that this is the device WITHOUT the number for the partition. SO for example /dev/sdc AND NOT /dev/sdc1 pve-cd.iso is the current proxmox iso that you downloaded. <br />
dd if=pve-cd.iso of=/dev/XYZ bs=1M<br />
===On Windows===<br />
First delete the partition of the usb-stick, else Suse Studio Image Writer might fail with a access failed error.<br />
Then rename the Proxmox iso that you downloaded from .iso to .raw. <br />
Run Suse Studio Image Writer, selct the drive and the image.<br />
<br />
==Base Installation of Proxmox==<br />
The graphical installation guide is straightforward and easy to understand.<br />
Please note though that the installer <span style="background:#ff0000">DELETS ALL PARTITIONS ON THE SELECTED DRIVE!</span> So all data on that drive is lost! You might want to unhook all harddrives that have unsaved data on it just to make sure you do not pick the wrong one by accident. <br />
<br />
==Reboot and Settings==<br />
After the base installation reboot the system, and check if you put in the right ip data in the installation process. <br />
NOTE: if you have multiple newtork cards make sure you plug the cable into the right one, if you do not have network connection try the other one.<br />
===Networking===<br />
Networking should work out of the box, if it does you can ignore this chapter and continue with [[Update]]. <br />
Else: check if there is internet connectivity by pinging something.<br />
ping google.com<br />
If you want to change the network settings <br />
nano /etc/network/interfaces<br />
if you want to use dhcp for the public interface this should look like:<br />
auto lo<br />
iface lo inet loopback<br />
auto vmbr0<br />
iface vmbr0 inet dhcp<br />
If you want to use static it should look something like that:<br />
auto lo<br />
iface lo inet loopback<br />
auto vmbr0<br />
iface vmbr0 inet static<br />
address 192.168.0.13<br />
netmask 255.255.255.0<br />
gateway 192.168.0.1<br />
bridge_ports eth0<br />
bridge_stp off<br />
bridge_fd 0<br />
if you did change some network setting run <br />
/etc/init.d/networking restart<br />
===Update===<br />
run<br />
aptitude update && aptitude full-upgrade<br />
If you get the message <br />
E: Some index files failed to download. They have been ignored, or old ones used instead.<br />
you can ignore it, or if rather not you can edit<br />
nano /etc/apt/sources.list.d/pve-enterprise.list<br />
and comment out the enterpries repository by placing a "#" in front of it. <br />
#deb https://enterprise.proxmox.com/debian wheezy pve-enterprise<br />
<br />
==Software Raid==<br />
If you do not want to use softwar raid you can continue with the next chapter.<br />
<span style="background:#ff0000">WARNING: Software raid is not supported by proxmox!</span><br />
But of course it works nevertheless, but as usual do it on your own risk.<br />
This part of the guide is based in a German guide found here[http://dominicpratt.de/proxmox-ve-3-0-software-raid/]<br />
First install the required package:<br />
apt-get update; apt-get install mdadm<br />
If there are any prompts on installing mdadm just ignore or press yes.<br />
===Prepare Raid===<br />
If you have not done so yet shutdown and plugin the second (identical) drive.<br />
In this guide the harddrive that proxmox was installed on is /dev/sda, while the second to use in the raid is /dev/sdb. If you have different drive letter, please change them accordingly.<br />
Prepare and create raid:<br />
sfdisk -d /dev/sda | sfdisk -f /dev/sdb<br />
sfdisk -c /dev/sdb 1 fd<br />
sfdisk -c /dev/sdb 2 fd<br />
mdadm --create -1 1 -n 2 /dev/md0 missing /dev/sdb1<br />
mdadm --create -1 1 n 2 /dev/md1 missing /dev/sdb2</div>Deepbhttp://wiki.linuxmce.org/index.php?title=User:Deepb&diff=34466User:Deepb2013-09-12T15:19:35Z<p>Deepb: </p>
<hr />
<div>=Installation of LinuxMCE in a KVM Virtual Machine=<br />
On this page I will describe the installation process of LinuxMCE in a KVM virtual machine. As a host system I use proxmox, a very user friendly and easy to use bare metal hypervisor. <br />
<br />
==Download Required Software==<br />
<br />
Download Proxmox the latest version of proxmox: [http://www.proxmox.com/downloads/category/iso-images-pve]<br />
:At the moment of this writing the current version is Proxmox VE 3.1<br />
Download LinuxMCE [http://www.linuxmce.org/download.html]<br />
:At the moment of this writing the current version is LinuxMCE 1004 final<br />
<br />
Adittionally if you are on Windows and want to use a usb-stick: (you do not need any addidional program on Linux)<br />
:Suse Studio Image Writer [ftp://ftp.berlios.de/pub/kiwi/ImageWriter.exe] to write the image to a usb-stick. UnetBootin and Rufus do not work. <br />
<br />
==Copying Image to USB-Stick==<br />
If you want to use a CD simply burn the iso to a cd.<br />
===On Linux===<br />
Please make sure that /dev/XYZ is the right device, as this delets all content. Please also note that this is the device WITHOUT the number for the partition. SO for example /dev/sdc AND NOT /dev/sdc1 pve-cd.iso is the current proxmox iso that you downloaded. <br />
dd if=pve-cd.iso of=/dev/XYZ bs=1M<br />
===On Windows===<br />
First delete the partition of the usb-stick, else Suse Studio Image Writer might fail with a access failed error.<br />
Then rename the Proxmox iso that you downloaded from .iso to .raw. <br />
Run Suse Studio Image Writer, selct the drive and the image.<br />
<br />
==Base Installation of Proxmox==<br />
The graphical installation guide is straightforward and easy to understand.<br />
Please note though that the installer <span style="background:#ff0000">DELETS ALL PARTITIONS ON THE SELECTED DRIVE!</span> So all data on that drive is lost! You might want to unhook all harddrives that have unsaved data on it just to make sure you do not pick the wrong one by accident. <br />
<br />
==Reboot and Settings==<br />
After the base installation reboot the system, and check if you put in the right ip data in the installation process. <br />
NOTE: if you have multiple newtork cards make sure you plug the cable into the right one, if you do not have network connection try the other one.<br />
===Networking===<br />
Networking should work out of the box, if it does you can ignore this chapter and continue with [[Update]]. <br />
Else: check if there is internet connectivity by pinging something.<br />
ping google.com<br />
If you want to change the network settings <br />
nano /etc/network/interfaces<br />
if you want to use dhcp for the public interface this should look like:<br />
auto lo<br />
iface lo inet loopback<br />
auto vmbr0<br />
iface vmbr0 inet dhcp<br />
If you want to use static it should look something like that:<br />
auto lo<br />
iface lo inet loopback<br />
auto vmbr0<br />
iface vmbr0 inet static<br />
address 192.168.0.13<br />
netmask 255.255.255.0<br />
gateway 192.168.0.1<br />
bridge_ports eth0<br />
bridge_stp off<br />
bridge_fd 0<br />
if you did change some network setting run <br />
/etc/init.d/networking restart<br />
===Update===<br />
run<br />
aptitude update && aptitude full-upgrade<br />
If you get the message <br />
E: Some index files failed to download. They have been ignored, or old ones used instead.<br />
you can ignore it, or if rather not you can edit<br />
nano /etc/apt/sources.list.d/pve-enterprise.list<br />
and comment out the enterpries repository by placing a "#" in front of it. <br />
#deb https://enterprise.proxmox.com/debian wheezy pve-enterprise</div>Deepbhttp://wiki.linuxmce.org/index.php?title=User:Deepb&diff=34465User:Deepb2013-09-12T15:10:34Z<p>Deepb: </p>
<hr />
<div>=Installation of LinuxMCE in a KVM Virtual Machine=<br />
On this page I will describe the installation process of LinuxMCE in a KVM virtual machine. As a host system I use proxmox, a very user friendly and easy to use bare metal hypervisor. <br />
<br />
==Download Required Software==<br />
<br />
Download Proxmox the latest version of proxmox: [http://www.proxmox.com/downloads/category/iso-images-pve]<br />
:At the moment of this writing the current version is Proxmox VE 3.1<br />
Download LinuxMCE [http://www.linuxmce.org/download.html]<br />
:At the moment of this writing the current version is LinuxMCE 1004 final<br />
<br />
Adittionally if you are on Windows and want to use a usb-stick: (you do not need any addidional program on Linux)<br />
:Suse Studio Image Writer [ftp://ftp.berlios.de/pub/kiwi/ImageWriter.exe] to write the image to a usb-stick. UnetBootin and Rufus do not work. <br />
<br />
==Copying Image to USB-Stick==<br />
If you want to use a CD simply burn the iso to a cd.<br />
===On Linux===<br />
Please make sure that /dev/XYZ is the right device, as this delets all content. Please also note that this is the device WITHOUT the number for the partition. SO for example /dev/sdc AND NOT /dev/sdc1 pve-cd.iso is the current proxmox iso that you downloaded. <br />
dd if=pve-cd.iso of=/dev/XYZ bs=1M<br />
===On Windows===<br />
First delete the partition of the usb-stick, else Suse Studio Image Writer might fail with a access failed error.<br />
Then rename the Proxmox iso that you downloaded from .iso to .raw. <br />
Run Suse Studio Image Writer, selct the drive and the image.<br />
<br />
==Base Installation of Proxmox==<br />
The graphical installation guide is straightforward and easy to understand.<br />
Please note though that the installer <span style="background:#ff0000">DELETS ALL PARTITIONS ON THE SELECTED DRIVE!</span> So all data on that drive is lost! You might want to unhook all harddrives that have unsaved data on it just to make sure you do not pick the wrong one by accident. <br />
<br />
==Reboot and Settings==<br />
After the base installation reboot the system, and check if you put in the right ip data in the installation process. <br />
NOTE: if you have multiple newtork cards make sure you plug the cable into the right one, if you do not have network connection try the other one.<br />
===Networking===<br />
Networking should work out of the box, if it does you can ignore this chapter and continue with [[Update]]. <br />
Else: check if there is internet connectivity by pinging something.<br />
ping google.com<br />
If you want to change the network settings <br />
nano /etc/network/interfaces<br />
if you want to use dhcp for the public interface this should look like:<br />
auto lo<br />
iface lo inet loopback<br />
auto vmbr0<br />
iface vmbr0 inet dhcp<br />
If you want to use static it should look something like that:<br />
auto lo<br />
iface lo inet loopback<br />
auto vmbr0<br />
iface vmbr0 inet static<br />
address 192.168.0.13<br />
netmask 255.255.255.0<br />
gateway 192.168.0.1<br />
bridge_ports eth0<br />
bridge_stp off<br />
bridge_fd 0<br />
if you did change some network setting run <br />
/etc/init.d/networking restart<br />
===Update===<br />
run<br />
aptitude update && aptitude full-upgrade<br />
If you get the message <br />
E: Some index files failed to download. They have been ignored, or old ones used instead.<br />
you can ignore it, or if rather not you can edit<br />
nano /etc/apt/sources.list.d/pve-enterprise.list</div>Deepbhttp://wiki.linuxmce.org/index.php?title=User:Deepb&diff=34464User:Deepb2013-09-12T14:59:41Z<p>Deepb: </p>
<hr />
<div>=Installation of LinuxMCE in a KVM Virtual Machine=<br />
On this page I will describe the installation process of LinuxMCE in a KVM virtual machine. As a host system I use proxmox, a very user friendly and easy to use bare metal hypervisor. <br />
<br />
==Download Required Software==<br />
<br />
Download Proxmox the latest version of proxmox: [http://www.proxmox.com/downloads/category/iso-images-pve]<br />
:At the moment of this writing the current version is Proxmox VE 3.1<br />
Download LinuxMCE [http://www.linuxmce.org/download.html]<br />
:At the moment of this writing the current version is LinuxMCE 1004 final<br />
<br />
Adittionally if you are on Windows and want to use a usb-stick: (you do not need any addidional program on Linux)<br />
:Suse Studio Image Writer [ftp://ftp.berlios.de/pub/kiwi/ImageWriter.exe] to write the image to a usb-stick. UnetBootin and Rufus do not work. <br />
<br />
==Copying Image to USB-Stick==<br />
If you want to use a CD simply burn the iso to a cd.<br />
===On Linux===<br />
Please make sure that /dev/XYZ is the right device, as this delets all content. Please also note that this is the device WITHOUT the number for the partition. SO for example /dev/sdc AND NOT /dev/sdc1 pve-cd.iso is the current proxmox iso that you downloaded. <br />
dd if=pve-cd.iso of=/dev/XYZ bs=1M<br />
===On Windows===<br />
First delete the partition of the usb-stick, else Suse Studio Image Writer might fail with a access failed error.<br />
Then rename the Proxmox iso that you downloaded from .iso to .raw. <br />
Run Suse Studio Image Writer, selct the drive and the image.<br />
<br />
==Base Installation of Proxmox==<br />
The graphical installation guide is straightforward and easy to understand.<br />
Please note though that the installer <span style="background:#ff0000">DELETS ALL PARTITIONS ON THE SELECTED DRIVE!</span> So all data on that drive is lost! You might want to unhook all harddrives that have unsaved data on it just to make sure you do not pick the wrong one by accident. <br />
<br />
==Reboot and Settings==<br />
After the base installation reboot the system, and check if you put in the right ip data in the installation process. <br />
NOTE: if you have multiple newtork cards make sure you plug the cable into the right one, if you do not have network connection try the other one.<br />
===Networking===<br />
Networking should work out of the box, if it does you can ignore this chapter and continue with [[Update]]. <br />
Else: check if there is internet connectivity by pinging something.<br />
ping google.com<br />
If you want to change the network settings <br />
nano /etc/network/interfaces<br />
if you want to use dhcp for the public interface this should look like:<br />
auto lo<br />
iface lo inet loopback<br />
auto vmbr0<br />
iface vmbr0 inet dhcp<br />
If you want to use static it should look something like that:<br />
auto lo<br />
iface lo inet loopback<br />
auto vmbr0<br />
iface vmbr0 inet static<br />
address 192.168.0.13<br />
netmask 255.255.255.0<br />
gateway 192.168.0.1<br />
bridge_ports eth0<br />
bridge_stp off<br />
bridge_fd 0<br />
if you did change some network setting run <br />
/etc/init.d/networking restart<br />
===Update===<br />
run<br />
aptitude update && aptitude full-upgrade</div>Deepbhttp://wiki.linuxmce.org/index.php?title=User:Deepb&diff=34463User:Deepb2013-09-12T14:59:12Z<p>Deepb: </p>
<hr />
<div>=Installation of LinuxMCE in a KVM Virtual Machine=<br />
On this page I will describe the installation process of LinuxMCE in a KVM virtual machine. As a host system I use proxmox, a very user friendly and easy to use bare metal hypervisor. <br />
<br />
==Download Required Software==<br />
<br />
Download Proxmox the latest version of proxmox: [http://www.proxmox.com/downloads/category/iso-images-pve]<br />
:At the moment of this writing the current version is Proxmox VE 3.1<br />
Download LinuxMCE [http://www.linuxmce.org/download.html]<br />
:At the moment of this writing the current version is LinuxMCE 1004 final<br />
<br />
Adittionally if you are on Windows and want to use a usb-stick: (you do not need any addidional program on Linux)<br />
:Suse Studio Image Writer [ftp://ftp.berlios.de/pub/kiwi/ImageWriter.exe] to write the image to a usb-stick. UnetBootin and Rufus do not work. <br />
<br />
==Copying Image to USB-Stick==<br />
If you want to use a CD simply burn the iso to a cd.<br />
===On Linux===<br />
Please make sure that /dev/XYZ is the right device, as this delets all content. Please also note that this is the device WITHOUT the number for the partition. SO for example /dev/sdc AND NOT /dev/sdc1 pve-cd.iso is the current proxmox iso that you downloaded. <br />
dd if=pve-cd.iso of=/dev/XYZ bs=1M<br />
===On Windows===<br />
First delete the partition of the usb-stick, else Suse Studio Image Writer might fail with a access failed error.<br />
Then rename the Proxmox iso that you downloaded from .iso to .raw. <br />
Run Suse Studio Image Writer, selct the drive and the image.<br />
<br />
==Base Installation of Proxmox==<br />
The graphical installation guide is straightforward and easy to understand.<br />
Please note though that the installer <span style="background:#ff0000">DELETS ALL PARTITIONS ON THE SELECTED DRIVE!</span> So all data on that drive is lost! You might want to unhook all harddrives that have unsaved data on it just to make sure you do not pick the wrong one by accident. <br />
<br />
==Reboot and Settings==<br />
After the base installation reboot the system, and check if you put in the right ip data in the installation process. <br />
NOTE: if you have multiple newtork cards make sure you plug the cable into the right one, if you do not have network connection try the other one.<br />
===Networking===<br />
Networking should work out of the box, if it does you can ignore this chapter. <br />
Else: check if there is internet connectivity by pinging something.<br />
ping google.com<br />
If you want to change the network settings <br />
nano /etc/network/interfaces<br />
if you want to use dhcp for the public interface this should look like:<br />
auto lo<br />
iface lo inet loopback<br />
auto vmbr0<br />
iface vmbr0 inet dhcp<br />
If you want to use static it should look something like that:<br />
auto lo<br />
iface lo inet loopback<br />
auto vmbr0<br />
iface vmbr0 inet static<br />
address 192.168.0.13<br />
netmask 255.255.255.0<br />
gateway 192.168.0.1<br />
bridge_ports eth0<br />
bridge_stp off<br />
bridge_fd 0<br />
if you did change some network setting run <br />
/etc/init.d/networking restart<br />
===Update===<br />
run<br />
aptitude update && aptitude full-upgrade</div>Deepbhttp://wiki.linuxmce.org/index.php?title=User:Deepb&diff=34462User:Deepb2013-09-12T14:58:37Z<p>Deepb: </p>
<hr />
<div>=Installation of LinuxMCE in a KVM Virtual Machine=<br />
On this page I will describe the installation process of LinuxMCE in a KVM virtual machine. As a host system I use proxmox, a very user friendly and easy to use bare metal hypervisor. <br />
<br />
==Download Required Software==<br />
<br />
Download Proxmox the latest version of proxmox: [http://www.proxmox.com/downloads/category/iso-images-pve]<br />
:At the moment of this writing the current version is Proxmox VE 3.1<br />
Download LinuxMCE [http://www.linuxmce.org/download.html]<br />
:At the moment of this writing the current version is LinuxMCE 1004 final<br />
<br />
Adittionally if you are on Windows and want to use a usb-stick: (you do not need any addidional program on Linux)<br />
:Suse Studio Image Writer [ftp://ftp.berlios.de/pub/kiwi/ImageWriter.exe] to write the image to a usb-stick. UnetBootin and Rufus do not work. <br />
<br />
==Copying Image to USB-Stick==<br />
If you want to use a CD simply burn the iso to a cd.<br />
===On Linux===<br />
Please make sure that /dev/XYZ is the right device, as this delets all content. Please also note that this is the device WITHOUT the number for the partition. SO for example /dev/sdc AND NOT /dev/sdc1 pve-cd.iso is the current proxmox iso that you downloaded. <br />
dd if=pve-cd.iso of=/dev/XYZ bs=1M<br />
===On Windows===<br />
First delete the partition of the usb-stick, else Suse Studio Image Writer might fail with a access failed error.<br />
Then rename the Proxmox iso that you downloaded from .iso to .raw. <br />
Run Suse Studio Image Writer, selct the drive and the image.<br />
<br />
==Base Installation of Proxmox==<br />
The graphical installation guide is straightforward and easy to understand.<br />
Please note though that the installer <span style="background:#ff0000">DELETS ALL PARTITIONS ON THE SELECTED DRIVE!</span> So all data on that drive is lost! You might want to unhook all harddrives that have unsaved data on it just to make sure you do not pick the wrong one by accident. <br />
<br />
==Reboot and Settings==<br />
After the base installation reboot the system, and check if you put in the right ip data in the installation process. <br />
NOTE: if you have multiple newtork cards make sure you plug the cable into the right one, if you do not have network connection try the other one.<br />
===Networking===<br />
Networking should work out of the box, if it does you can ignore this chapter. <br />
Else: check if there is internet connectivity by pinging something.<br />
ping google.com<br />
If you want to change the network settings <br />
nano /etc/network/interfaces<br />
if you want to use dhcp for the public interface this should look like:<br />
auto lo<br />
iface lo inet loopback<br />
auto vmbr0<br />
iface vmbr0 inet dhcp<br />
If you want to use static it should look something like that:<br />
auto lo<br />
iface lo inet loopback<br />
auto vmbr0<br />
iface vmbr0 inet static<br />
address 192.168.0.13<br />
netmask 255.255.255.0<br />
gateway 192.168.0.1<br />
bridge_ports eth0<br />
bridge_stp off<br />
bridge_fd 0<br />
if you did change some network setting run <br />
/etc/init.d/networking restart</div>Deepbhttp://wiki.linuxmce.org/index.php?title=User:Deepb&diff=34461User:Deepb2013-09-12T14:58:01Z<p>Deepb: </p>
<hr />
<div>=Installation of LinuxMCE in a KVM Virtual Machine=<br />
On this page I will describe the installation process of LinuxMCE in a KVM virtual machine. As a host system I use proxmox, a very user friendly and easy to use bare metal hypervisor. <br />
<br />
==Download Required Software==<br />
<br />
Download Proxmox the latest version of proxmox: [http://www.proxmox.com/downloads/category/iso-images-pve]<br />
:At the moment of this writing the current version is Proxmox VE 3.1<br />
Download LinuxMCE [http://www.linuxmce.org/download.html]<br />
:At the moment of this writing the current version is LinuxMCE 1004 final<br />
<br />
Adittionally if you are on Windows and want to use a usb-stick: (you do not need any addidional program on Linux)<br />
:Suse Studio Image Writer [ftp://ftp.berlios.de/pub/kiwi/ImageWriter.exe] to write the image to a usb-stick. UnetBootin and Rufus do not work. <br />
<br />
==Copying Image to USB-Stick==<br />
If you want to use a CD simply burn the iso to a cd.<br />
===On Linux===<br />
Please make sure that /dev/XYZ is the right device, as this delets all content. Please also note that this is the device WITHOUT the number for the partition. SO for example /dev/sdc AND NOT /dev/sdc1 pve-cd.iso is the current proxmox iso that you downloaded. <br />
dd if=pve-cd.iso of=/dev/XYZ bs=1M<br />
===On Windows===<br />
First delete the partition of the usb-stick, else Suse Studio Image Writer might fail with a access failed error.<br />
Then rename the Proxmox iso that you downloaded from .iso to .raw. <br />
Run Suse Studio Image Writer, selct the drive and the image.<br />
<br />
==Base Installation of Proxmox==<br />
The graphical installation guide is straightforward and easy to understand.<br />
Please note though that the installer <span style="background:#ff0000">DELETS ALL PARTITIONS ON THE SELECTED DRIVE!</span> So all data on that drive is lost! You might want to unhook all harddrives that have unsaved data on it just to make sure you do not pick the wrong one by accident. <br />
<br />
==Reboot and Settings==<br />
After the base installation reboot the system, and check if you put in the right ip data in the installation process. <br />
NOTE: if you have multiple newtork cards make sure you plug the cable into the right one, if you do not have network connection try the other one.<br />
===Networking===<br />
Networking should work out of the box, if it does you can ignore this chapter. <br />
Else: check if there is internet connectivity by pinging something.<br />
ping google.com<br />
If you want to change the network settings <br />
nano /etc/network/interfaces<br />
if you want to use dhcp for the public interface this should look like:<br />
auto lo<br />
iface lo inet loopback<br />
auto vmbr0<br />
iface vmbr0 inet dhcp<br />
If you want to use static it should look something like that:<br />
auto lo<br />
iface lo inet loopback<br />
auto vmbr0<br />
iface vmbr0 inet static<br />
address 192.168.0.13<br />
netmask 255.255.255.0<br />
gateway 192.168.0.1<br />
bridge_ports eth0<br />
bridge_stp off<br />
bridge_fd 0</div>Deepbhttp://wiki.linuxmce.org/index.php?title=User:Deepb&diff=34460User:Deepb2013-09-12T14:57:21Z<p>Deepb: </p>
<hr />
<div>=Installation of LinuxMCE in a KVM Virtual Machine=<br />
On this page I will describe the installation process of LinuxMCE in a KVM virtual machine. As a host system I use proxmox, a very user friendly and easy to use bare metal hypervisor. <br />
<br />
==Download Required Software==<br />
<br />
Download Proxmox the latest version of proxmox: [http://www.proxmox.com/downloads/category/iso-images-pve]<br />
:At the moment of this writing the current version is Proxmox VE 3.1<br />
Download LinuxMCE [http://www.linuxmce.org/download.html]<br />
:At the moment of this writing the current version is LinuxMCE 1004 final<br />
<br />
Adittionally if you are on Windows and want to use a usb-stick: (you do not need any addidional program on Linux)<br />
:Suse Studio Image Writer [ftp://ftp.berlios.de/pub/kiwi/ImageWriter.exe] to write the image to a usb-stick. UnetBootin and Rufus do not work. <br />
<br />
==Copying Image to USB-Stick==<br />
If you want to use a CD simply burn the iso to a cd.<br />
===On Linux===<br />
Please make sure that /dev/XYZ is the right device, as this delets all content. Please also note that this is the device WITHOUT the number for the partition. SO for example /dev/sdc AND NOT /dev/sdc1 pve-cd.iso is the current proxmox iso that you downloaded. <br />
dd if=pve-cd.iso of=/dev/XYZ bs=1M<br />
===On Windows===<br />
First delete the partition of the usb-stick, else Suse Studio Image Writer might fail with a access failed error.<br />
Then rename the Proxmox iso that you downloaded from .iso to .raw. <br />
Run Suse Studio Image Writer, selct the drive and the image.<br />
<br />
==Base Installation of Proxmox==<br />
The graphical installation guide is straightforward and easy to understand.<br />
Please note though that the installer <span style="background:#ff0000">DELETS ALL PARTITIONS ON THE SELECTED DRIVE!</span> So all data on that drive is lost! You might want to unhook all harddrives that have unsaved data on it just to make sure you do not pick the wrong one by accident. <br />
<br />
==Reboot and Settings==<br />
After the base installation reboot the system, and check if you put in the right ip data in the installation process. <br />
NOTE: if you have multiple newtork cards make sure you plug the cable into the right one, if you do not have network connection try the other one.<br />
===Networking===<br />
Networking should work out of the box, if it does you can ignore this chapter. <br />
Else: check if there is internet connectivity by pinging something.<br />
ping google.com<br />
If you want to change the network settings <br />
nano /etc/network/interfaces<br />
if you want to use dhcp for the public interface this should look like:<br />
auto lo<br />
iface lo inet loopback<br />
auto vmbr0<br />
iface vmbr0 inet dhcp<br />
If you want to use static it should look something like that:<br />
auto lo<br />
iface lo inet loopback<br />
auto vmbr0<br />
iface vmbr0 inet static<br />
:address 192.168.0.13<br />
:netmask 255.255.255.0<br />
:gateway 192.168.0.1<br />
:bridge_ports eth0<br />
:bridge_stp off<br />
:bridge_fd 0</div>Deepbhttp://wiki.linuxmce.org/index.php?title=User:Deepb&diff=34459User:Deepb2013-09-12T14:57:00Z<p>Deepb: </p>
<hr />
<div>=Installation of LinuxMCE in a KVM Virtual Machine=<br />
On this page I will describe the installation process of LinuxMCE in a KVM virtual machine. As a host system I use proxmox, a very user friendly and easy to use bare metal hypervisor. <br />
<br />
==Download Required Software==<br />
<br />
Download Proxmox the latest version of proxmox: [http://www.proxmox.com/downloads/category/iso-images-pve]<br />
:At the moment of this writing the current version is Proxmox VE 3.1<br />
Download LinuxMCE [http://www.linuxmce.org/download.html]<br />
:At the moment of this writing the current version is LinuxMCE 1004 final<br />
<br />
Adittionally if you are on Windows and want to use a usb-stick: (you do not need any addidional program on Linux)<br />
:Suse Studio Image Writer [ftp://ftp.berlios.de/pub/kiwi/ImageWriter.exe] to write the image to a usb-stick. UnetBootin and Rufus do not work. <br />
<br />
==Copying Image to USB-Stick==<br />
If you want to use a CD simply burn the iso to a cd.<br />
===On Linux===<br />
Please make sure that /dev/XYZ is the right device, as this delets all content. Please also note that this is the device WITHOUT the number for the partition. SO for example /dev/sdc AND NOT /dev/sdc1 pve-cd.iso is the current proxmox iso that you downloaded. <br />
dd if=pve-cd.iso of=/dev/XYZ bs=1M<br />
===On Windows===<br />
First delete the partition of the usb-stick, else Suse Studio Image Writer might fail with a access failed error.<br />
Then rename the Proxmox iso that you downloaded from .iso to .raw. <br />
Run Suse Studio Image Writer, selct the drive and the image.<br />
<br />
==Base Installation of Proxmox==<br />
The graphical installation guide is straightforward and easy to understand.<br />
Please note though that the installer <span style="background:#ff0000">DELETS ALL PARTITIONS ON THE SELECTED DRIVE!</span> So all data on that drive is lost! You might want to unhook all harddrives that have unsaved data on it just to make sure you do not pick the wrong one by accident. <br />
<br />
==Reboot and Settings==<br />
After the base installation reboot the system, and check if you put in the right ip data in the installation process. <br />
NOTE: if you have multiple newtork cards make sure you plug the cable into the right one, if you do not have network connection try the other one.<br />
===Networking===<br />
Networking should work out of the box, if it does you can ignore this chapter. Else:<br />
check if there is internet connectivity by pinging something.<br />
ping google.com<br />
If you want to change the network settings <br />
nano /etc/network/interfaces<br />
if you want to use dhcp for the public interface this should look like:<br />
auto lo<br />
iface lo inet loopback<br />
auto vmbr0<br />
iface vmbr0 inet dhcp<br />
If you want to use static it should look something like that:<br />
auto lo<br />
iface lo inet loopback<br />
auto vmbr0<br />
iface vmbr0 inet static<br />
:address 192.168.0.13<br />
:netmask 255.255.255.0<br />
:gateway 192.168.0.1<br />
:bridge_ports eth0<br />
:bridge_stp off<br />
:bridge_fd 0</div>Deepbhttp://wiki.linuxmce.org/index.php?title=User:Deepb&diff=34458User:Deepb2013-09-12T14:56:15Z<p>Deepb: </p>
<hr />
<div>=Installation of LinuxMCE in a KVM Virtual Machine=<br />
On this page I will describe the installation process of LinuxMCE in a KVM virtual machine. As a host system I use proxmox, a very user friendly and easy to use bare metal hypervisor. <br />
<br />
==Download Required Software==<br />
<br />
Download Proxmox the latest version of proxmox: [http://www.proxmox.com/downloads/category/iso-images-pve]<br />
:At the moment of this writing the current version is Proxmox VE 3.1<br />
Download LinuxMCE [http://www.linuxmce.org/download.html]<br />
:At the moment of this writing the current version is LinuxMCE 1004 final<br />
<br />
Adittionally if you are on Windows and want to use a usb-stick: (you do not need any addidional program on Linux)<br />
:Suse Studio Image Writer [ftp://ftp.berlios.de/pub/kiwi/ImageWriter.exe] to write the image to a usb-stick. UnetBootin and Rufus do not work. <br />
<br />
==Copying Image to USB-Stick==<br />
If you want to use a CD simply burn the iso to a cd.<br />
===On Linux===<br />
Please make sure that /dev/XYZ is the right device, as this delets all content. Please also note that this is the device WITHOUT the number for the partition. SO for example /dev/sdc AND NOT /dev/sdc1 pve-cd.iso is the current proxmox iso that you downloaded. <br />
dd if=pve-cd.iso of=/dev/XYZ bs=1M<br />
===On Windows===<br />
First delete the partition of the usb-stick, else Suse Studio Image Writer might fail with a access failed error.<br />
Then rename the Proxmox iso that you downloaded from .iso to .raw. <br />
Run Suse Studio Image Writer, selct the drive and the image.<br />
<br />
==Base Installation of Proxmox==<br />
The graphical installation guide is straightforward and easy to understand.<br />
Please note though that the installer <span style="background:#ff0000">DELETS ALL PARTITIONS ON THE SELECTED DRIVE!</span> So all data on that drive is lost! You might want to unhook all harddrives that have unsaved data on it just to make sure you do not pick the wrong one by accident. <br />
<br />
==Reboot and Settings==<br />
After the base installation reboot the system, and check if you put in the right ip data in the installation process. <br />
NOTE: if you have multiple newtork cards make sure you plug the cable into the right one, if you do not have network connection try the other one.<br />
check if there is internet connectivity by pinging something.<br />
ping google.com<br />
If you want to change the network settings <br />
nano /etc/network/interfaces<br />
if you want to use dhcp for the public interface this should look like:<br />
auto lo<br />
iface lo inet loopback<br />
auto vmbr0<br />
iface vmbr0 inet dhcp<br />
If you want to use static it should look something like that:<br />
auto lo<br />
iface lo inet loopback<br />
auto vmbr0<br />
iface vmbr0 inet static<br />
:address 192.168.0.13<br />
:netmask 255.255.255.0<br />
:gateway 192.168.0.1<br />
:bridge_ports eth0<br />
:bridge_stp off<br />
:bridge_fd 0</div>Deepbhttp://wiki.linuxmce.org/index.php?title=User:Deepb&diff=34457User:Deepb2013-09-12T14:55:55Z<p>Deepb: </p>
<hr />
<div>=Installation of LinuxMCE in a KVM Virtual Machine=<br />
On this page I will describe the installation process of LinuxMCE in a KVM virtual machine. As a host system I use proxmox, a very user friendly and easy to use bare metal hypervisor. <br />
<br />
==Download Required Software==<br />
<br />
Download Proxmox the latest version of proxmox: [http://www.proxmox.com/downloads/category/iso-images-pve]<br />
:At the moment of this writing the current version is Proxmox VE 3.1<br />
Download LinuxMCE [http://www.linuxmce.org/download.html]<br />
:At the moment of this writing the current version is LinuxMCE 1004 final<br />
<br />
Adittionally if you are on Windows and want to use a usb-stick: (you do not need any addidional program on Linux)<br />
:Suse Studio Image Writer [ftp://ftp.berlios.de/pub/kiwi/ImageWriter.exe] to write the image to a usb-stick. UnetBootin and Rufus do not work. <br />
<br />
==Copying Image to USB-Stick==<br />
If you want to use a CD simply burn the iso to a cd.<br />
===On Linux===<br />
Please make sure that /dev/XYZ is the right device, as this delets all content. Please also note that this is the device WITHOUT the number for the partition. SO for example /dev/sdc AND NOT /dev/sdc1 pve-cd.iso is the current proxmox iso that you downloaded. <br />
dd if=pve-cd.iso of=/dev/XYZ bs=1M<br />
===On Windows===<br />
First delete the partition of the usb-stick, else Suse Studio Image Writer might fail with a access failed error.<br />
Then rename the Proxmox iso that you downloaded from .iso to .raw. <br />
Run Suse Studio Image Writer, selct the drive and the image.<br />
<br />
==Base Installation of Proxmox==<br />
The graphical installation guide is straightforward and easy to understand.<br />
Please note though that the installer <span style="background:#ff0000">DELETS ALL PARTITIONS ON THE SELECTED DRIVE!</span> So all data on that drive is lost! You might want to unhook all harddrives that have unsaved data on it just to make sure you do not pick the wrong one by accident. <br />
<br />
==Reboot and Settings==<br />
After the base installation reboot the system, and check if you put in the right ip data in the installation process. <br />
NOTE: if you have multiple newtork cards make sure you plug the cable into the right one, if you do not have network connection try the other one.<br />
check if there is internet connectivity by pinging something.<br />
ping google.com<br />
If you want to change the network settings <br />
nano /etc/network/interfaces<br />
if you want to use dhcp for the public interface this should look like:<br />
auto lo<br />
iface lo inet loopback<br />
<br />
auto vmbr0<br />
iface vmbr0 inet dhcp<br />
If you want to use static it should look something like that:<br />
auto lo<br />
iface lo inet loopback<br />
<br />
auto vmbr0<br />
iface vmbr0 inet static<br />
:address 192.168.0.13<br />
:netmask 255.255.255.0<br />
:gateway 192.168.0.1<br />
:bridge_ports eth0<br />
:bridge_stp off<br />
:bridge_fd 0</div>Deepbhttp://wiki.linuxmce.org/index.php?title=User:Deepb&diff=34456User:Deepb2013-09-12T14:37:24Z<p>Deepb: </p>
<hr />
<div>=Installation of LinuxMCE in a KVM Virtual Machine=<br />
On this page I will describe the installation process of LinuxMCE in a KVM virtual machine. As a host system I use proxmox, a very user friendly and easy to use bare metal hypervisor. <br />
<br />
==Download Required Software==<br />
<br />
Download Proxmox the latest version of proxmox: [http://www.proxmox.com/downloads/category/iso-images-pve]<br />
:At the moment of this writing the current version is Proxmox VE 3.1<br />
Download LinuxMCE [http://www.linuxmce.org/download.html]<br />
:At the moment of this writing the current version is LinuxMCE 1004 final<br />
<br />
Adittionally if you are on Windows and want to use a usb-stick: (you do not need any addidional program on Linux)<br />
:Suse Studio Image Writer [ftp://ftp.berlios.de/pub/kiwi/ImageWriter.exe] to write the image to a usb-stick. UnetBootin and Rufus do not work. <br />
<br />
==Copying Image to USB-Stick==<br />
If you want to use a CD simply burn the iso to a cd.<br />
===On Linux===<br />
Please make sure that /dev/XYZ is the right device, as this delets all content. Please also note that this is the device WITHOUT the number for the partition. SO for example /dev/sdc AND NOT /dev/sdc1<br />
dd if=pve-cd.iso of=/dev/XYZ bs=1M<br />
===On Windows===</div>Deepbhttp://wiki.linuxmce.org/index.php?title=User:Deepb&diff=34455User:Deepb2013-09-12T14:33:25Z<p>Deepb: </p>
<hr />
<div>=Installation of LinuxMCE in a KVM Virtual Machine=<br />
On this page I will describe the installation process of LinuxMCE in a KVM virtual machine. As a host system I use proxmox, a very user friendly and easy to use bare metal hypervisor. <br />
<br />
==Download Required Software==<br />
<br />
Download Proxmox the latest version of proxmox: [http://www.proxmox.com/downloads/category/iso-images-pve]<br />
:At the moment of this writing the current version is Proxmox VE 3.1<br />
Download LinuxMCE [http://www.linuxmce.org/download.html]<br />
:At the moment of this writing the current version is LinuxMCE 1004 final<br />
<br />
If you are on Windows and want to use a usb-stick:<br />
:Suse Studio Image Writer [ftp://ftp.berlios.de/pub/kiwi/ImageWriter.exe] to write the image to a usb-stick. UnetBootin and Rufus do not work. <br />
<br />
If you are on Linuxand want to use a usb-stick:<br />
:nothing</div>Deepbhttp://wiki.linuxmce.org/index.php?title=User:Deepb&diff=34454User:Deepb2013-09-12T14:29:53Z<p>Deepb: Created page with "=Installation of LinuxMCE in a KVM Virtual Machine= On this page I will describe the installation process of LinuxMCE in a KVM virtual machine. As a host system I use proxmox, a ..."</p>
<hr />
<div>=Installation of LinuxMCE in a KVM Virtual Machine=<br />
On this page I will describe the installation process of LinuxMCE in a KVM virtual machine. As a host system I use proxmox, a very user friendly and easy to use bare metal hypervisor. <br />
<br />
==Download Required Software==<br />
<br />
Download Proxmox the latest version of proxmox: [http://www.proxmox.com/downloads/category/iso-images-pve]<br />
:At the moment of this writing the current version is Proxmox VE 3.1, which is found here [http://www.proxmox.com/downloads?task=callelement&format=raw&item_id=68&element=f85c494b-2b32-4109-b8c1-083cca2b7db6&method=download&args[0]=669a8fa5be918ec211fc0cbb0f8d50e3]</div>Deepbhttp://wiki.linuxmce.org/index.php?title=SMB_/_Samba_NAS_Configurations&diff=34423SMB / Samba NAS Configurations2013-09-04T09:21:25Z<p>Deepb: </p>
<hr />
<div>[[Category: Tutorials]]<br />
<br />
[[How to setup Samba with two workgroups?]]<br />
[[How to setup Samba to follow symbolic links?]]<br />
<br />
Problem: we have shares for each users. if I want to access it from Windows, I have to enter password. if I don't this on first access, windows won't ask my anymore to enter password and just denies access. How can I force windows, to reenter password for share ???<br />
<br />
If your samba password doesn't work then run this on core to update your samba password:<br />
sudo smbpasswd pluto_USER<br />
where USER is your username. For instance to change john's password run sudo smbpasswd pluto_john<br />
NOTE: if you set your Samba password like that it will be forgotten on reboot. Set the password in the webadmin. [[User:Deepb|Deepb]] 11:21, 4 September 2013 (CEST)<br />
<br />
== Adding fileserver on the external network ==<br />
The external network does not get scanned for Samba servers. You can easily add a new server by going into the web admin<br />
* Click Show Device Tree<br />
* Click CORE<br />
* On the right hand side, click Create Child Device<br />
* Click Pick Device Template<br />
* In the popup select Manufacturer->Generic and Device Category->File Server from the drop down menus; you can also enter device template ID 1837 in the "Do you know the ID of the device template?" field<br />
* Now, it is important to fill out just the IP field (otherwise the DHCP configuration gets screwed)<br />
* The username and password are only needed if the file server requires them.<br />
* There is currently a bug in the webadmin which causes this file server to not be scanned for shares.<br />
=== Scanning For Shares ===<br />
The good thing about LinuxMCE is, that LinuxMCE routinely scans the internal network for servers, and if found, scans those servers for shares to be mounted and spidered for media. To initiate the scan for shares manually (because of a manually added server) do the following<br />
* Open a terminal<br />
* Execute<br />
/usr/pluto/bin/Configure_1837.sh -d <device-id> -i '<ip-address>' -m '<mac-address>'<br />
<br />
This will execute the scan for new shares. The shares will be presented to you on any orbiter.</div>Deepb