1 | Installing a test scripts server on XVM |
---|
2 | ======================================= |
---|
3 | |
---|
4 | It's useful to have a less secure scripts server for testing |
---|
5 | purposes. Here's what you have to do: |
---|
6 | |
---|
7 | 1. Creating the VM |
---|
8 | ------------------ |
---|
9 | |
---|
10 | To authenticate to xvm.mit.edu with root tickets, you need |
---|
11 | a browser that suppors SPNEGO; Firefox is one such browser and |
---|
12 | the following instructions will assume it. Browse to about:config |
---|
13 | and modify the key 'network.negotiate-auth.trusted-uris' to be |
---|
14 | |
---|
15 | https://xvm.mit.edu:442/* |
---|
16 | |
---|
17 | Then, with active root tickets on your system, navigate to |
---|
18 | |
---|
19 | https://xvm.mit.edu:442/ |
---|
20 | |
---|
21 | You should be logged in as root, and if you are on scripts-root |
---|
22 | you should be able to assign ownership to scripts. |
---|
23 | |
---|
24 | [XXX: there should be a way to do this with remctl too] |
---|
25 | |
---|
26 | 2. Configure |
---|
27 | ------------ |
---|
28 | |
---|
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. |
---|
32 | |
---|
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.) Since you're doing an install CD, it's going to be an HVM. |
---|
38 | |
---|
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: |
---|
43 | |
---|
44 | athrun xvm invirt-vnc-client -a $AUTHTOKEN |
---|
45 | vncviewer localhost |
---|
46 | |
---|
47 | where AUTHTOKEN is the contents of the AUTHTOKEN param on the console page |
---|
48 | (which would have had the Java applet.) |
---|
49 | |
---|
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: |
---|
53 | |
---|
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-test-passwd which we tend to use. |
---|
64 | |
---|
65 | We don't know how to convert to ParaVM yet, because latest Fedora |
---|
66 | uses Grub2 but XVM's bootloader doesn't understand how to read it |
---|
67 | (see also the Scripts patches we manually applied to our hosts.) |
---|
68 | |
---|
69 | 3. Debugging |
---|
70 | ------------ |
---|
71 | |
---|
72 | Get dropped into dracut:#/ ? Check for 'Warn' in dmesg (dmesg | grep Warn) |
---|
73 | and fix any problems that are stopping Dracut from proceeding. |
---|