$ ssh-keygen -t rsa -b 1024 -f filename- ssh to the bluecoat proxy
> en
# configure terminal
#(config) ssh-console
#(config ssh-console) inline client-key admin ...
< paste the key after those three dots >
..../arun
$ ssh-keygen -t rsa -b 1024 -f filename
> en
# configure terminal
#(config) ssh-console
#(config ssh-console) inline client-key admin ...
< paste the key after those three dots >
...$ sudo lvdisplay
# qemu-img convert -O qcow2 /dev/mapper/lv_name <destination_file>.qcow2
# qemu-img convert -O qcow2 /dev/mapper/disk1 disk1.qcow2

# ./fastboot-mac devices
HT845Gxxxxx fastboot
# ./fastboot-mac flash recovery recovery-RA-dream-v1.7.0.img
sending 'recovery' (4594 KB)... OKAY
writing 'recovery'... OKAY
# ./fastboot-mac reboot





$ ./adb install ~/sam2.apk
1686 KB/s (506724 bytes in 0.293s)
pkg: /data/local/tmp/sam2.apk
Success
ssh -X user@host
# echo $DISPLAY
localhost:10.0
IPV6INIT=yes
IPV6ADDR=xxxx.xx::10
IPV6_DEFAULTGW=xxxx.xx::1
IPV6_AUTOCONF=no
IPV6INIT=yes
IPV6ADDR=xxxx.xx::11
IPV6_DEFAULTGW=xxxx.xx::1
IPV6_AUTOCONF=no
-A FORWARD -m physdev --physdev-is-bridged -j ACCEPT.
You can use the host-only-adapter networking, if you require the virtual machine to be accessible only from the host machine. In this case your virtual machine will not have access to anywhere outside the host. Read more about virtual box networking at http://www.virtualbox.org/manual/ch06.html
On the other hand NAT enabled interface can communicate with clients outside the host, but the host cannot access the services on the virtual machine directly. We need to enabled port forwarding with NAT interface to achieve this.
$ VBoxManage modifyvm "VM Name" --natpf1 "openssh,tcp,127.0.0.1,2222,,22"$ VBoxManage modifyvm "VM Name" --natpf1 "openssh,tcp,127.0.0.1,2222,10.0.2.20,22" $ ssh localhost -p 2222VBoxManage modifyvm "VM Name" --natpf1 "proxy,tcp,127.0.0.1,8080,10.0.2.20,8080"< Forwarding name="openssh" proto="1" hostip="127.0.0.1" hostport="2222" guestip=10.0.2.20 guestport="2222"/>VBoxManage setextradata "VM Name" "VBoxInternal/Devices/pcnet/0/LUN#0/Config/guestssh/Protocol" TCPVBoxManage setextradata "VM Name" "VBoxInternal/Devices/pcnet/0/LUN#0/Config/guestssh/GuestPort" 22VBoxManage setextradata "VM Name" "VBoxInternal/Devices/pcnet/0/LUN#0/Config/guestssh/HostPort" 2222
It took a while to get the KVM image working with Sun virtual box.
The advantages of a virtual box image is, you can run it on any platform (linux, mac or windows), works without virtualization enabled processor and will work on a 32bit machine
Here are the steps to create an image that works with virtual box:
$ qemu-img convert kvm-os.img -O raw kvm-os-raw.img$ VBoxManage convertfromrow --format VDI kvm-os-raw.img vbox.vdiConverting from raw image file="kvm-os-raw.img" to file="vbox.vdi"...
Creating dynamic image with size ....
$ VBoxManage modifyvdi /home/user/vbox.vdi compact0%...10%...20%...30%...40%...50%...60%...70%
Here the path to vdi image must be absolute.
Now you can create a new virtual machine from virtual box console/command line, with the vdi image as storage.
Boot the machine and hope for the best :)
But it wasn't easy for me even after this beautiful vdi image, boot hangs with a kernel panic, file system not found.
> linux rescue # chroot /mnt/sysimage # cp /boot/initrd-2.6.xxx.img initrd-2.6-old# mkinitrd -v /boot/initrd-new.img kernel-version # cat /boot/grub/menu.lst-A FORWARD -m physdev --physdev-is-bridged -j ACCEPTtcpdump -i br0 port bootps -vvv -s 1500$ easy_install ZODB3==VERSION
$ easy_install ZODB3==3.8.3
$python
>>> import ZODB