Project Presentation
Here is our Project Presentation on Huge-Page Support in Xen Virtualization.
Ottawa Linux Symposium (OLS) Papers for 2011:
Here is links of Ottawa Linux Symposium 2011 where our paper was selected.
Now its on www.kernerl.org, here is the link.
Shell script to see if service is stopped
#!/bin/sh
running=1
while [ $running -eq 1 ]
do
sleep 1
running=`ps ax | grep $service_name | grep -v grep | wc -l`
done
echo "$service_name stopped successfully"
Reading a file, word by word
#!/bin/sh
ln=1
#Reading from config file
while [ ! -z "$ln" ]
do
read ln
word1=`echo $ln | awk '{print $1}'`
word2=`echo $ln | awk '{print $2}'`
word3=`echo $ln | awk '{print $3}'`
echo "word1 = $word1 ,word2 = $word2, word3 = $word3"
done < ./config
Checking if VM is booted
Pre- condition : Assign static ip to VM.
virsh start Fedora13
until ping -c 1 -W 1 192.168.122.11
do
sleep 1
done
sleep 3
echo "Started"
Password less ssh
#!/bin/sh
#$1: User
#$2: IP
## Should run as root user
ssh-keygen -t rsa
ssh $1@$2 mkdir -p .ssh
cat /root/.ssh/id_rsa.pub | $1@$2 ‘cat >> .ssh/authorized_keys’
ssh-keygen -t rsa: This will generate public and private rsa key pair for security. This should be called only once. Press “Enter” for every step.
ssh : remote login. This will prompt for password.
last step “cat …” : Send public key to remote host.
Guidelines to submit patch in xen-devel…
Please try to follow the guidelines below. This will make things
easier on the maintainers. Not all of these guidelines matter for every
trivial patch so apply some common sense.
1. Always _test_ your changes, however small, on at least 4 or
5 people, preferably many more.
2. Make sure your changes compile correctly in multiple
configurations. For example, both 32- and 64-bit x86.
3. Make a patch available to the relevant maintainer in the list. Use
‘diff -u’ to make the patch easy to merge. Be prepared to get your
changes sent back with seemingly silly requests about formatting
and variable names. These aren’t as silly as they seem. One
job the maintainersdo is to keep things looking the same.
PLEASE try to include any credit lines you want added with the
patch. It avoids people being missed off by mistake and makes
it easier to know who wants adding and who doesn’t.
PLEASE document known bugs. If it doesn’t work for everything
or does something very odd once a month document it.
PLEASE remember that submissions must be made under the terms
of the “Developer’s Certificate of Origin” (DCO) and should include
a Signed-off-by: line.
4. Make sure you have the right to send any changes you make. If you
do changes at work you may find your employer owns the patch
not you.
5. Happy hacking.
check wiki.xensource.com for more information.
