Using the self-serve net installer: Difference between revisions

From BitFolk
Jump to navigation Jump to search
(→‎OS-specific notes: Ubuntu Lucid)
(New disk layout simplifies things somewhat. CentOS also added)
Line 1: Line 1:
For some guest operating systems it is possible for customers to launch a
For some guest operating systems it is possible for customers to launch a
'''self-service network installer''' from the [[Xen Shell]].
'''self-service network installer''' from the [[Xen Shell]].
{{warning|This feature is still in development and currently only works for Debian lenny and Debian squeeze. Additionally if you don't see the '''install''' menu item in your Xen Shell then it is not available to you yet.}}


==Default image installs ''vs.'' network installer==
==Default image installs ''vs.'' network installer==
Line 28: Line 24:
:If you don't know the password then you'll need to do a reset or contact BitFolk Support.
:If you don't know the password then you'll need to do a reset or contact BitFolk Support.
* '''Be running a new enough version of Xen Shell.'''
* '''Be running a new enough version of Xen Shell.'''
:Xen Shell stays running if you disconnect from it, so it's possible that you're still running an old version. You need to be running version '''v1.48bitfolk5''' or later.
:Xen Shell stays running if you disconnect from it, so it's possible that you're still running an old version. You need to be running version '''v1.48bitfolk8''' or later.
:You can see the version of a running Xen Shell instance by using the '''help''' command. If yours is too old just '''exit''' from every screen until you're disconnected, and then reconnect.
:You can see the version of a running Xen Shell instance by using the '''help''' command. If yours is too old just '''exit''' from every screen until you're disconnected, and then reconnect.
* '''Have a modern enough VPS configuration.'''
* '''Have a modern enough VPS configuration.'''
:If you don't see the '''install''' option in the '''help''' menu then your VPS configuration is too old.
:You may be warned that your VPS's disk layout is non-standard. In that case you'll need to use the '''reset''' command of the '''disks''' sub-menu to standardise it.
:BitFolk has gone through several different styles of VPS configuration because Linux is quite flexible and there's more than one way to do it. It was only later discovered that some styles are better for some things, like resizing disks, or tricking distributions' boot loader scripts into playing nice.
:Unfortunately some of the older configurations are just impossible to make work with some netboot installers and there's no way to reconfigure your VPS without coordinating with you. Your VPS still works fine as it is, but if you'd like to use one of the netboot installer then please contact BitFolk support find out what you need to do to get your VPS configuration updated.
* '''Be prepared to nuke your existing VPS and any data stored on it.'''
* '''Be prepared to nuke your existing VPS and any data stored on it.'''
:Generally the first thing the network installers do is format your VPS's block device(s), so don't try to do this unless you have backups or don't care about your data. It ''might'' be possible depending on the installer to preserve the contents of some block devices, but please don't rely on this.
:Generally the first thing the network installers do is format your VPS's block device(s), so don't try to do this unless you have backups or don't care about your data. It ''might'' be possible depending on the installer to preserve the contents of some block devices, but please don't rely on this.
Line 59: Line 53:


The network installer should then boot and you'll follow the usual procedure for installing your chosen operating system.
The network installer should then boot and you'll follow the usual procedure for installing your chosen operating system.
==General issues to be aware of==
===Partitioning===
You must place your root filesystem on the first partition of the first disk (i.e. '''xvda1'''), it must be '''ext3''' filesystem and '''/boot''' must be contained within it. If you don't do this then your VPS almost certainly will not boot.
For later ease of resizing it is recommended that you restrict yourself to one partition per disk. The typical BitFolk VPS has two disks, '''xvda''' and '''xvdb''' each of which has a single partition spanning the whole disk ('''xvda1''' and '''xvdb1''' respectively). If you require more partitions then you can add them via the '''disks''' sub-menu of the Xen Shell prior to install. This will give you extra disks, e.g. '''xvdc''', '''xvdd''' and so on. You can split your disk allocation up into as many disk devices as you like.
If you ''don't'' do this and instead put multiple partitions on a disk it will still work fine, but if you should ever come to want a disk resized it makes the process more difficult.
Apart from the restriction of having to have your root filesystem as '''ext3''' on '''xvda1''', you can use your distribution's installer to add extra partitions of any filesystem type that your distribution normally supports, and lay out your filesystems as you please.


==OS-specific notes==
==OS-specific notes==
Line 71: Line 75:


====Disk partitioning====
====Disk partitioning====
On a normal machine you would usually have a block device such as '''/dev/sda''' representing an entire hard disk, and you would then partition this into one or more partitions like '''/dev/sda1''', '''/dev/sda2''', etc. On a BitFolk VPS you have '''/dev/xvda''' (and perhaps additional block devices if you have requested that), but later resizing of these block devices is made much easier if you place a filesystem directly on the block device without a partition table.
The first partman dialog you'll be shown looks like this:
 
Additionally, the first block device ('''/dev/xvda''') must contain your root filesystem and '''/boot''' and must be of type '''ext3'''.
 
Unfortunately the partman partitioning tool doesn't like putting filesystems directly onto block devices. The first partman dialog you'll be shown looks like this:


<pre>
<pre>
Line 100: Line 100:
</pre>
</pre>


The rest of this section covers the usual case where BitFolk has given you a single block device upon which you intend to put your root filesystem. If instead you have additional block devices and want to do something more advanced then the procedure is [[Using the self-serve net installer/Advanced partitioning|slightly more complicated]].
You're advised to select '''Manual''' so that you can ensure that your root filesystem goes on '''xvda1''' and your swap goes on '''xvdb1''' as per the notes above.
 
You'll need to select '''Manual'''. Then you'll see something like:
 
<pre>
  ┌────────────────┤ [!!] Partition disks ├─────────────────────────┐
  │                                                                        │
  │ This is an overview of your currently configured partitions and mount  │
  │ points. Select a partition to modify its settings (file system, mount  │
  │ point, etc.), a free space to create partitions, or a device to        │
  │ initialize its partition table.                                        │
  │                                                                        │
  │      Guided partitioning                                              │
  │      Help on partitioning                                              │
  │                                                                        │
  │      Virtual disk 1 (xvda) - 10.7 GB Xen Virtual Block Device          │
  │      >    #1    10.7 GB      ext3                                    │
  │                                                                        │
  │      Undo changes to partitions                                        │
  │      Finish partitioning and write changes to disk                    │
  │                                                                        │
  │    <Go Back>                                                          │
  │                                                                        │
  └─────────────────────────────────────────────────────────────┘
</pre>
 
You are advised to move to the line for the single existing filesystem:
 
<pre>
  │      >    #1    10.7 GB      ext3                                    │
</pre>
 
select it, then:
 
* Use as: Ext3 journaling file system
* Format the partition:  yes, format it
* Mount point:          /


"'''relatime'''" is a good idea as a mount option, and using a filesystem label is also smart.
"'''relatime'''" is a good idea as a mount option, and using a filesystem label is also smart.
It is recommended [http://bitfolk.com/customer_information.html#toc_3_Why_is_my_swap_a_swap_file__not_a_swap_device_ not to add a swap partition]. The installer later creates a swap file for you.
If you decide ''not'' to follow this advice and start adding partitions then it should still work, but if you later request your block device be resized it will require longer downtime, and your VPS would be booting in a way that is different to all other BitFolk VPSes, so it is not recommended. If you want extra disk devices then just contact support; this will not be a problem.


Once you've selected '''Finish partitioning and write changes to disk''' the installation will proceed as normal. If you don't select any additional software it should only take a few minutes.
Once you've selected '''Finish partitioning and write changes to disk''' the installation will proceed as normal. If you don't select any additional software it should only take a few minutes.
Line 196: Line 156:
* '''/etc/resolv.conf''' will only have one of the two BitFolk [http://bitfolk.com/customer_information.html#toc_2_DNS DNS resolvers].
* '''/etc/resolv.conf''' will only have one of the two BitFolk [http://bitfolk.com/customer_information.html#toc_2_DNS DNS resolvers].
* Your '''/etc/fstab''' will be mounting things by device name, but it's recommended to [[Mounting filesystems by UUID or label|change that to UUID or label]]. Future changes to the Linux kernel are more likely to rename virtual block devices than devices for regular SATA disks, so it's wise to make sure that things mount properly even if this should happen.
* Your '''/etc/fstab''' will be mounting things by device name, but it's recommended to [[Mounting filesystems by UUID or label|change that to UUID or label]]. Future changes to the Linux kernel are more likely to rename virtual block devices than devices for regular SATA disks, so it's wise to make sure that things mount properly even if this should happen.
* Your filesystems will be set to periodically '''fsck'''. Default BitFolk VPS installs have this [http://bitfolk.com/customer_information.html#toc_3_Why_has_time_based_filesystem_check__fsck__been_disabled_ disabled for performance reasons], and you might like to [http://bitfolk.com/customer_information.html#toc_3_Why_has_time_based_filesystem_check__fsck__been_disabled_ do that too].
* If your VPS has multiple IPv4 addresses then only the first one will have been configured by the installer.
* If your VPS has multiple IPv4 addresses then only the first one will have been configured by the installer.
* The installer won't have set up IPv6 at all.
* The installer won't have set up IPv6 at all.
Line 213: Line 172:


There seemed to be a large pause (as much as 4 minutes) with no visible progress in between setting hostname/domain and installing the base system, but the install did eventually proceed by itself.
There seemed to be a large pause (as much as 4 minutes) with no visible progress in between setting hostname/domain and installing the base system, but the install did eventually proceed by itself.
===CentOS===
So far supported:
* CentOS 5.x
====Partitioning====
Soon after the install starts you'll see something like this:
<syntaxhighlight>
Welcome to CentOS                                                             
  +-------------------------+ Partitioning Type +-------------------------+   
  |                                                                      |   
  |    Installation requires partitioning of your hard drive.  The        |   
  |    default layout is reasonable for most users.  You can either      |   
  |    choose to use this or create your own.                            |   
  |                                                                      |   
  | Remove all partitions on selected drives and create default layout.  |   
  | Remove linux partitions on selected drives and create default layout. |   
  | Use free space on selected drives and create default layout.          |   
  | Create custom layout.                                                |   
  |                                                                      |   
  |      Which drive(s) do you want to use for this installation?        |   
  |          [*]  xvda    10237 MB (Xen Virtual Block Device) ^          |   
  |          [*]  xvdb      251 MB (Xen Virtual Block Device) #          |   
  |                                                                      |   
  |                          +----+  +------+                            |   
  |                          | OK |  | Back |                            |   
  |                          +----+  +------+                            |   
  |                                                                      |   
  |                                                                      |   
  +-----------------------------------------------------------------------+   
                                                                               
<Space>,<+>,<-> selection  |  <F2> Add drive  |  <F12> next screen     
</syntaxhighlight>
You are advised to:
* move the cursor to the "Create custom layout." line
* hit tab to move drive selection, where you can toggle the drives with the space key
* when done there, tab again to the "OK" button and press return to continue.
You will then see something like:
<syntaxhighlight>
Welcome to CentOS                                                             
                                                                               
+------------------------------+ Partitioning +------------------------------+
|                                                                            |
|        Device          Start    End    Size      Type    Mount Point    |
| /dev/xvda                                                                ^ |
|  Free space                1    1306  10240M  Free space              # |
| /dev/xvdb                                                                : |
|  Free space                1      33    256M  Free space              : |
| /dev/xvdc                                                                : |
|  Free space                1    621    4864M  Free space              : |
|                                                                          : |
|                                                                          : |
|                                                                          : |
|                                                                          v |
|                                                                            |
|      +-----+  +------+  +--------+  +------+  +----+  +------+        |
|      | New |  | Edit |  | Delete |  | RAID |  | OK |  | Back |        |
|      +-----+  +------+  +--------+  +------+  +----+  +------+        |
|                                                                            |
|                                                                            |
+----------------------------------------------------------------------------+
                                                                               
    F1-Help    F2-New      F3-Edit  F4-Delete    F5-Reset    F12-OK         
</syntaxhighlight>
You just need to remember the above advice to put root as type '''ext3''' on '''xvda1''' and swap as '''xvdb1'''.
The install will now proceed normally and should be finished in a couple of minutes.
====Finishing the install====
Once the install has completed you'll see something like:
<syntaxhighlight>
sending termination signals...done                                           
sending kill signals...done
disabling swap...
        /tmp/xvdb1
unmounting filesystems...
        /mnt/runtime done
        disabling /dev/loop0
        /proc done
        /dev/pts done
        /sys done
        /tmp/ramfs done
        /selinux done
        /mnt/sysimage/sys done
        /mnt/sysimage/proc done
        /mnt/sysimage/selinux done
        /mnt/sysimage/dev done
        /mnt/sysimage done
rebooting system
Restarting system.
xen-shell>
</syntaxhighlight>
You should now be able to '''boot''' into the new CentOS install.
====Things you might like to change after install====
* You may want to configure '''yum''' to take advantage of BitFolk's [http://bitfolk.com/customer_information.html#toc_2_Centos_5_mirror CentOS 5 mirror]
* You either won't have an NTP server installed or else it won't be configured to talk to BitFolk's [http://bitfolk.com/customer_information.html#toc_2_NTP NTP servers]
* '''/etc/resolv.conf''' will only have one of the two BitFolk [http://bitfolk.com/customer_information.html#toc_2_DNS DNS resolvers].
* If your VPS has multiple IPv4 addresses then only the first one will have been configured by the installer.
* The installer won't have set up IPv6 at all.
* A default firewall configuration has been loaded; this will likely need to be modified if you're going to run any public network services.

Revision as of 12:48, 30 December 2010

For some guest operating systems it is possible for customers to launch a self-service network installer from the Xen Shell.

Default image installs vs. network installer

Most BitFolk customers have their VPS initially provisioned by BitFolk support via an image file. This results in a minimal install fully-customised for the BitFolk environment, but with very little flexibility.

Some customers prefer to run through their chosen operating system's familiar network installer in order to carry out a custom install to their specification. This can also be useful to reinstall your VPS without requiring assistance from BitFolk support.

Not all operating systems that BitFolk supports are available as self-service network installs. It requires that the operating system has a Xen-compatible network installer, and that this has been tested by BitFolk.

Prerequisites

In order to initiate a network install you must:

  • Have access to your Xen Shell.
If you don't know the password then you'll need to do a reset or contact BitFolk Support.
  • Be running a new enough version of Xen Shell.
Xen Shell stays running if you disconnect from it, so it's possible that you're still running an old version. You need to be running version v1.48bitfolk8 or later.
You can see the version of a running Xen Shell instance by using the help command. If yours is too old just exit from every screen until you're disconnected, and then reconnect.
  • Have a modern enough VPS configuration.
You may be warned that your VPS's disk layout is non-standard. In that case you'll need to use the reset command of the disks sub-menu to standardise it.
  • Be prepared to nuke your existing VPS and any data stored on it.
Generally the first thing the network installers do is format your VPS's block device(s), so don't try to do this unless you have backups or don't care about your data. It might be possible depending on the installer to preserve the contents of some block devices, but please don't rely on this.

Initiating a network install

Use the install command. It's as simple as: 

xen-shell v1.48bitfolk2 - type 'help' for help.
xen-shell> install debian_lenny
About to overwrite your VPS with the debian_lenny network installer - this will result in a loss of all data, without further confirmation!
Are you sure? Please type "Yes" to confirm, or anything else to abort.
INSTALL?> yes
Booting debian_lenny net installer for: debtest1
Using config file "/etc/xen/debtest1.conf".
Install Mirror: http://ftp.uk.debian.org/debian
Install Suite: lenny
Installer: http://ftp.uk.debian.org/debian/dists/lenny/main/installer-i386/current/images

WARNING: Installer kernel and ramdisk are not authenticated.

Fetching http://ftp.uk.debian.org/debian/dists/lenny/main/installer-i386/current/images/netboot/xen/vmlinuz
Fetching http://ftp.uk.debian.org/debian/dists/lenny/main/installer-i386/current/images/netboot/xen/initrd.gz

The network installer should then boot and you'll follow the usual procedure for installing your chosen operating system.

General issues to be aware of

Partitioning

You must place your root filesystem on the first partition of the first disk (i.e. xvda1), it must be ext3 filesystem and /boot must be contained within it. If you don't do this then your VPS almost certainly will not boot.

For later ease of resizing it is recommended that you restrict yourself to one partition per disk. The typical BitFolk VPS has two disks, xvda and xvdb each of which has a single partition spanning the whole disk (xvda1 and xvdb1 respectively). If you require more partitions then you can add them via the disks sub-menu of the Xen Shell prior to install. This will give you extra disks, e.g. xvdc, xvdd and so on. You can split your disk allocation up into as many disk devices as you like.

If you don't do this and instead put multiple partitions on a disk it will still work fine, but if you should ever come to want a disk resized it makes the process more difficult.

Apart from the restriction of having to have your root filesystem as ext3 on xvda1, you can use your distribution's installer to add extra partitions of any filesystem type that your distribution normally supports, and lay out your filesystems as you please.

OS-specific notes

Debian

So far supported:

  • lenny (5.x)
  • squeeze (6.x)

The installation process is pretty much identical to a normal Debian net install, with the following quirks.

Disk partitioning

The first partman dialog you'll be shown looks like this: 

  ┌────────────────────────┤ [!!] Partition disks ├─────────────────┐
  │                                                                         │ 
  │ The installer can guide you through partitioning a disk (using          │ 
  │ different standard schemes) or, if you prefer, you can do it            │ 
  │ manually. With guided partitioning you will still have a chance later   │ 
  │ to review and customise the results.                                    │ 
  │                                                                         │ 
  │ If you choose guided partitioning for an entire disk, you will next     │ 
  │ be asked which disk should be used.                                     │ 
  │                                                                         │ 
  │ Partitioning method:                                                    │ 
  │                                                                         │ 
  │          Guided - use entire disk                                       │ 
  │          Guided - use entire disk and set up LVM                        │ 
  │          Guided - use entire disk and set up encrypted LVM              │ 
  │          Manual                                                         │ 
  │                                                                         │ 
  │     <Go Back>                                                           │ 
  │                                                                         │ 
  └─────────────────────────────────────────────────────────────┘

You're advised to select Manual so that you can ensure that your root filesystem goes on xvda1 and your swap goes on xvdb1 as per the notes above.

"relatime" is a good idea as a mount option, and using a filesystem label is also smart.

Once you've selected Finish partitioning and write changes to disk the installation will proceed as normal. If you don't select any additional software it should only take a few minutes.

Finishing the install

At the end you'll see: 

   ┌────────────┤ [!!] Finish the installation ├────────────────────┐
  ┌│                         Installation complete                         │ 
  ││ Installation is complete, so it is time to boot into your new system. │  
  ││ Make sure to remove the installation media (CD-ROM, floppies), so     │  
  ││ that you boot into the new system rather than restarting the          │  
  ││ installation.                                                         │  
  ││                                                                       │  
  └│     <Go Back>                                          <Continue>     │  
   │                                                                       │  
   └───────────────────────────────────────────────────────────┘

Normally at this point you'd select <Continue> and your machine would reboot into your new install. Under Xen though, a reboot does not fully destroy the virtual machine. If the installer did do a reboot here, all that would happen is that Xen would restart the installer again. For that reason the installer has been set to halt here. You'll be dropped back to the Xen Shell prompt, and issuing a boot command will boot up your new VPS: 

The system is going down NOW!ystem...                                       │ 
Sending SIGTERM to all processes                                            │ 
Sending SIGKILL to all processes─────────────────────────────────────┘ 
Requesting system halt                                                        
                      [ 4298.952440] md: stopping all md devices.
[ 4299.944797] xenbus_dev_shutdown: device/console/0: Initialising != Connected, skipping
[ 4300.295265] System halted.
xen-shell> boot
Booting instance: debtest1

    pyGRUB  version 0.6
 lqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqk
 x Debian GNU/Linux, kernel 2.6.26-2-xen-686                              x
 x Debian GNU/Linux, kernel 2.6.26-2-xen-686 (single-user mode)           x

Started domain debtest1
                       [    0.000000] Initializing cgroup subsys cpuset
[    0.000000] Initializing cgroup subsys cpu
[    0.000000] Linux version 2.6.26-2-xen-686 (Debian 2.6.26-26lenny1) (dannf@debian.org) (gcc version 4.1.3 20080704 (prerelease) (Debian 4.1.2-25)) #1 SMP Thu Nov 25 02:32:31 UTC 2010
.
.
.

Things you might like to change after install

By this point you've just completed a fresh install of Debian and it should be working fine, but you won't have some of the nice features of a typical BitFolk VPS image configured. Things you may wish to look into:

  • Probably not all of your entries in /etc/apt/sources.lst are taking advantage of the apt-cacher.
  • You either won't have an NTP server installed or else it won't be configured to talk to the NTP servers.
  • /etc/resolv.conf will only have one of the two BitFolk DNS resolvers.
  • Your /etc/fstab will be mounting things by device name, but it's recommended to change that to UUID or label. Future changes to the Linux kernel are more likely to rename virtual block devices than devices for regular SATA disks, so it's wise to make sure that things mount properly even if this should happen.
  • If your VPS has multiple IPv4 addresses then only the first one will have been configured by the installer.
  • The installer won't have set up IPv6 at all.

Breaking out of the installer

If you do something wrong then you can generally fix it by going back to the installer's main menu. You get there by selecting Go back when given that option in a dialog. From the main menu of the installer you can retrace your steps. You can also start a shell if you need to poke around.

You can of course always create a new Xen Shell window, shutdown or destroy your running installer VPS and just start over again.

Ubuntu

So far supported:

  • Lucid (10.04 LTS)

The process is largely identical to Debian.

There seemed to be a large pause (as much as 4 minutes) with no visible progress in between setting hostname/domain and installing the base system, but the install did eventually proceed by itself.

CentOS

So far supported:

  • CentOS 5.x

Partitioning

Soon after the install starts you'll see something like this: 

Welcome to CentOS                                                               
   +-------------------------+ Partitioning Type +-------------------------+    
   |                                                                       |    
   |    Installation requires partitioning of your hard drive.  The        |    
   |    default layout is reasonable for most users.  You can either       |    
   |    choose to use this or create your own.                             |    
   |                                                                       |    
   | Remove all partitions on selected drives and create default layout.   |    
   | Remove linux partitions on selected drives and create default layout. |    
   | Use free space on selected drives and create default layout.          |    
   | Create custom layout.                                                 |    
   |                                                                       |    
   |       Which drive(s) do you want to use for this installation?        |    
   |          [*]   xvda    10237 MB (Xen Virtual Block Device) ^          |    
   |          [*]   xvdb      251 MB (Xen Virtual Block Device) #          |    
   |                                                                       |    
   |                          +----+   +------+                            |    
   |                          | OK |   | Back |                            |    
   |                          +----+   +------+                            |    
   |                                                                       |    
   |                                                                       |    
   +-----------------------------------------------------------------------+    
                                                                                
<Space>,<+>,<-> selection   |   <F2> Add drive   |   <F12> next screen

You are advised to:

  • move the cursor to the "Create custom layout." line
  • hit tab to move drive selection, where you can toggle the drives with the space key
  • when done there, tab again to the "OK" button and press return to continue.

You will then see something like: 

Welcome to CentOS                                                               
                                                                                
 +------------------------------+ Partitioning +------------------------------+ 
 |                                                                            | 
 |        Device          Start    End     Size       Type     Mount Point    | 
 | /dev/xvda                                                                ^ | 
 |   Free space                1    1306   10240M  Free space               # | 
 | /dev/xvdb                                                                : | 
 |   Free space                1      33     256M  Free space               : | 
 | /dev/xvdc                                                                : | 
 |   Free space                1     621    4864M  Free space               : | 
 |                                                                          : | 
 |                                                                          : | 
 |                                                                          : | 
 |                                                                          v | 
 |                                                                            | 
 |      +-----+   +------+   +--------+   +------+   +----+   +------+        | 
 |      | New |   | Edit |   | Delete |   | RAID |   | OK |   | Back |        | 
 |      +-----+   +------+   +--------+   +------+   +----+   +------+        | 
 |                                                                            | 
 |                                                                            | 
 +----------------------------------------------------------------------------+ 
                                                                                
    F1-Help     F2-New      F3-Edit   F4-Delete    F5-Reset    F12-OK

You just need to remember the above advice to put root as type ext3 on xvda1 and swap as xvdb1.

The install will now proceed normally and should be finished in a couple of minutes.

Finishing the install

Once the install has completed you'll see something like: 

sending termination signals...done                                             
sending kill signals...done
disabling swap...
        /tmp/xvdb1
unmounting filesystems...
        /mnt/runtime done
        disabling /dev/loop0
        /proc done
        /dev/pts done
        /sys done
        /tmp/ramfs done
        /selinux done
        /mnt/sysimage/sys done
        /mnt/sysimage/proc done
        /mnt/sysimage/selinux done
        /mnt/sysimage/dev done
        /mnt/sysimage done
rebooting system
Restarting system.
xen-shell>

You should now be able to boot into the new CentOS install.

Things you might like to change after install

  • You may want to configure yum to take advantage of BitFolk's CentOS 5 mirror
  • You either won't have an NTP server installed or else it won't be configured to talk to BitFolk's NTP servers
  • /etc/resolv.conf will only have one of the two BitFolk DNS resolvers.
  • If your VPS has multiple IPv4 addresses then only the first one will have been configured by the installer.
  • The installer won't have set up IPv6 at all.
  • A default firewall configuration has been loaded; this will likely need to be modified if you're going to run any public network services.
Retrieved from "https://tools.bitfolk.com/w/index.php?title=Using_the_self-serve_net_installer&oldid=116"