Difference between revisions of "BCCD:Automated liberation"
Jump to navigation
Jump to search
(explain how to use qemu with socket connect/listen) |
|||
| (3 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
| + | [[BCCD:Automated_liberation:Generalization|Generalization]] Work towards giving the liberation process a more general approach | ||
| + | |||
''Do all these commands from /p0/bccd on acl13 (or the equivalent).'' | ''Do all these commands from /p0/bccd on acl13 (or the equivalent).'' | ||
| + | |||
| + | * Make a fresh work environment /p0/bccd from a BCCD ISO: | ||
| + | <tt>./gen_staging.sh</tt> | ||
* Make a new boot ISO (bccdserver.iso): | * Make a new boot ISO (bccdserver.iso): | ||
| Line 9: | Line 14: | ||
* Look inside the qemu ISO (mount to /mnt/bccd): | * Look inside the qemu ISO (mount to /mnt/bccd): | ||
<tt>./lomount lib.img 2 /mnt/bccd</tt> | <tt>./lomount lib.img 2 /mnt/bccd</tt> | ||
| + | |||
| + | * Liberate to the hard drive after booting BCCD: | ||
| + | <tt>/bin/liberate</tt> | ||
| + | |||
| + | * Make a server after liberation: | ||
| + | <tt>/bin/prepareserver</tt> | ||
| + | |||
| + | * Boot a QEMU image with networking support between VMs (make sure MACs are unique!): | ||
| + | **<tt>qemu -hda lib.img -cdrom bccdserver.iso -net nic,macaddr=52:54:00:12:34:56 -net socket,mcast=230.0.0.1:1234 -boot d</tt> | ||
| + | |||
| + | Another way to accomplish the same thing, though perhaps not as efficient: | ||
| + | ** 1. Start the server: | ||
| + | <tt>qemu -hda hdas.img -net nic,macaddr=52:54:00:12:34:50 -net socket,listen=:1234</tt> | ||
| + | ** 2. Start some clients: | ||
| + | <tt>qemu -cdrom eb-5.4.1-ns8390.iso -net nic,macaddr=52:54:00:12:34:51 -net socket,connect=acl13:1234</tt> | ||
| + | <tt>qemu -cdrom eb-5.4.1-ns8390.iso -net nic,macaddr=52:54:00:12:34:52 -net socket,connect=acl13.cs.earlham.edu:1234</tt> | ||
| + | <tt>qemu -cdrom eb-5.4.1-ns8390.iso -net nic,macaddr=52:54:00:12:34:59 -net socket,connect=159.28.230.23:1234</tt> | ||
| + | |||
| + | WARNING: Not sure why, but running this networked version of Qemu is /very/ slow. If you have real hardware, consider using it instead. | ||
Latest revision as of 02:19, 12 April 2006
Generalization Work towards giving the liberation process a more general approach
Do all these commands from /p0/bccd on acl13 (or the equivalent).
- Make a fresh work environment /p0/bccd from a BCCD ISO:
./gen_staging.sh
- Make a new boot ISO (bccdserver.iso):
./mksingularity.sh singularity staging
- Boot that ISO for liberation:
qemu -hda lib.img -cdrom bccdserver.iso -boot d
- Look inside the qemu ISO (mount to /mnt/bccd):
./lomount lib.img 2 /mnt/bccd
- Liberate to the hard drive after booting BCCD:
/bin/liberate
- Make a server after liberation:
/bin/prepareserver
- Boot a QEMU image with networking support between VMs (make sure MACs are unique!):
- qemu -hda lib.img -cdrom bccdserver.iso -net nic,macaddr=52:54:00:12:34:56 -net socket,mcast=230.0.0.1:1234 -boot d
Another way to accomplish the same thing, though perhaps not as efficient:
- 1. Start the server:
qemu -hda hdas.img -net nic,macaddr=52:54:00:12:34:50 -net socket,listen=:1234
- 2. Start some clients:
qemu -cdrom eb-5.4.1-ns8390.iso -net nic,macaddr=52:54:00:12:34:51 -net socket,connect=acl13:1234 qemu -cdrom eb-5.4.1-ns8390.iso -net nic,macaddr=52:54:00:12:34:52 -net socket,connect=acl13.cs.earlham.edu:1234 qemu -cdrom eb-5.4.1-ns8390.iso -net nic,macaddr=52:54:00:12:34:59 -net socket,connect=159.28.230.23:1234
WARNING: Not sure why, but running this networked version of Qemu is /very/ slow. If you have real hardware, consider using it instead.
