Changeset 2315 for trunk/server
- Timestamp:
- Sep 5, 2012, 12:11:51 AM (12 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
trunk/server/doc/install-xvm
r1693 r2315 24 24 [XXX: there should be a way to do this with remctl too] 25 25 26 2. Spin up27 ---------- 26 2. Configure 27 ------------ 28 28 29 These instructions are mostly the same as the latter part of 30 install-fedora, with the following changes: 29 Lest you be tempted to skimp on RAM: you must have more than 700MBish 30 to install Fedora; 1024MB is a good amount is a good amount to give to 31 the server. Disk space on order of 40G is probably good enough. 31 32 32 VNC 33 --- 33 While it is best to use the install CD from the most recent version 34 of Fedora, any kernel which supports Kickstarting can be used. A good 35 bet is to use the Netboot CD from the latest version of Fedora that 36 XVM has (since XVM is sort of bad about keeping their boot CDs up to 37 date.) 34 38 35 You will not need to sketchily forward VNC, because XVM has a built 36 in VNC console. 39 You will need VNC access to perform the installation process. If you have 40 Java, just go to the Console page for the VM; if you do not, you can use 41 the following set of incants to setup a local VNC server which can talk 42 to the console: 37 43 38 Password 39 -------- 44 athrun xvm invirt-vnc-client -a $AUTHTOKEN 45 vncviewer localhost 40 46 41 Do NOT use the scripts-root password. Pick something else. 47 where AUTHTOKEN is the contents of the AUTHTOKEN param on the console page 48 (which would have had the Java applet.) 42 49 43 Disks 44 ----- 50 On the bootloader screen (usually it gives you a bunch of options 51 such as "Install" or "Advanced"), press TAB and edit the kernel boot 52 line to append the text: 45 53 46 The standard Scripts setup has separate LVM partitions for root and 47 swap, as well as a non-LVM partition for boot. You will not have this 48 for XVM, so the Fedora defaults mostly work. Don't use ext4 though. 54 ks=http://ezyang.scripts.mit.edu/kickstart/scripts.php?type=xvm&release=$RELEASE_NO&hostname=scripts-f$RELEASE_NO-test.xvm.mit.edu 55 56 with $RELEASE_NO interpolated properly. You should keep around any initrd 57 lines since the kernel image still needs to know how to boot up. 58 59 XXX the kickstart file needs to live in a less sketchy place 60 61 The install process will ask you for a password. Do NOT use the 62 scripts-root password. We have a password in 63 /mit/scripts/Private/scripts-f9-test-passwd which we tend to use.
Note: See TracChangeset
for help on using the changeset viewer.