Changes between Version 6 and Version 7 of Paravmssh
- Timestamp:
- May 21, 2009, 1:14:32 PM (16 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Paravmssh
v6 v7 1 XVM supports running paravirtualized guests. Paravirtualized guests are not virtual machines in the traditional sense; instead of running on emulated hardware, they are aware that they are running inside a VM system and can talk directly to the host. The result is that paravirtualized guests are significantly faster than fully virtualized guests ("HVMs"). To create a new ParaVM, first enter a name and description, then click the "Autoinstall" radio button and select one of the available operating systems from the menu. Finally, click "Create it!" 1 XVM supports running paravirtualized guests. Paravirtualized guests are not virtual machines in the traditional sense; instead of running on emulated hardware, they are aware that they are running inside a VM system and can talk directly to the host. The result is that paravirtualized guests are significantly faster than fully virtualized guests ("HVMs"). 2 3 = Creating a ParaVM = 4 5 To create a new ParaVM, first enter a name and description, then click the "Autoinstall" radio button and select one of the available operating systems from the menu. Finally, click "Create it!" 2 6 3 7 (Note that the default RAM quota is 512MiB, so if you already have two running VMs, you'll need to shut one of them down to create a new machine.) … … 5 9 After creating the VM, you should wait about 5-6 minutes for the install to complete. During this time, the VM will show as "on" in the web interface. Do not power it off; the operating system is being installed. If you want to watch the progress, you can follow the next set of instructions to see the install's debugging output. 6 10 7 After about 5 minutes, the installation will be done. You can then press the power button in the web interface to turn the VM on. You can access the machine's console from an Athena machine or from any machine that has Kerberos tickets. Assuming you have called your machine "myparavm", you can connect to it with 11 After about 5 minutes, the installation will be done. You can then press the power button in the web interface to turn the VM on. 12 13 = Accessing the Console = 14 15 You can access the machine's console from an Athena machine or from any machine that has Kerberos tickets. Assuming you have called your machine "myparavm", you can connect to it with 8 16 {{{ 9 17 athena% ssh myparavm@xvm-console.mit.edu … … 13 21 14 22 }}} 15 Hit enter to be given a login prompt. Type "root", and if asked for a password, just hit enter. At this point the machine will only allow logins as root and only allow logins from the console. Normally, we don't want to login as root, so we need to add a user: 23 Hit enter to be given a login prompt. Type "root", and if asked for a password, just hit enter. At this point the machine will only allow logins as root and only allow logins from the console. (So don't worry, other people can't access your machine.) 24 25 = Adding a User = 26 Normally, we don't want to login as root, so we'll add a user: 16 27 {{{ 17 28 root@myParaVM:~# adduser username 18 29 }}} 19 where username is preferably your athena identity. This will prompt you for a password and then for some personal information30 where {{{username}}} is preferably your Athena identity. This will prompt you for a password and then for some personal information 20 31 that does not matter for our purposes. 21 32 22 In order to install software, we next need to add ourselves to the sudoers file. If you chose an Ubuntu installation, you can do this by adding your user to the admin group, as follows: 33 == Making the new user an administrator == 34 You'll probably want to be able to install software and do other administration tasks without connecting to the console all the time. Here's how to make your new user a {{{sudo}}}er. 35 36 === Ubuntu === 37 38 If you chose an Ubuntu installation, you can do this by adding your user to the admin group, as follows: 23 39 {{{ 24 40 root@myParaVM~# adduser <username> admin 25 41 }}} 26 42 27 If you chose Debian, you'll need to add yourself to /etc/sudoers: 43 Note: Until ticket #118 is fixed, this won't actually work. Run the following lines first: 44 {{{ 45 addgroup --gid 114 admin 46 cat >> /etc/sudoers <<EOF 47 # Members of the admin group may gain root privileges 48 %admin ALL=(ALL) ALL 49 EOF 50 }}} 51 52 === Debian === 53 If you chose Debian, you'll need to add yourself to {{{/etc/sudoers}}}: 28 54 {{{ 29 55 root@myParaVM~# visudo … … 42 68 }}} 43 69 44 Now just open up another local terminal and try to ssh into your VM: 70 = Connecting = 71 Now, from another terminal on your local machine, you can try to ssh into your VM: 45 72 {{{ 46 73 athena% ssh username@myParaVM.xvm.mit.edu … … 48 75 and check that you can sudo: 49 76 {{{ 50 username@myParaVM~$ sudo -l77 username@myParaVM~$ sudo aptitude update 51 78 }}}
