Difference between revisions of "Vnx-modify-rootfs"
Line 15: | Line 15: | ||
</ul> | </ul> | ||
<li>Once the virtual machine is started and you have access to the console, you can make the modifications desired, for example, updating the VNXACE daemon following the step described below.</li> | <li>Once the virtual machine is started and you have access to the console, you can make the modifications desired, for example, updating the VNXACE daemon following the step described below.</li> | ||
− | + | <li>Finally halt the virtual machine using the '''vnx_halt''' command. This will clean some log and history files, clean the apt cache and optionally leave a text message in /etc/vnx_rootfs_version describing the modifications done. | |
− | |||
− | |||
</ul> | </ul> | ||
Line 44: | Line 42: | ||
mount /media/cdrom | mount /media/cdrom | ||
<li>Execute the install script:</li> | <li>Execute the install script:</li> | ||
− | perl /media/cdrom/ | + | perl /media/cdrom/install_vnxaced |
+ | </ul> | ||
+ | === Windows === | ||
− | + | To be completed | |
− | |||
− | |||
+ | === Olive === | ||
+ | To be completed | ||
+ | <!-- | ||
<li> '''rootfs_XXX.xml''', which are libvirt specifications to start virtual machines with Internet connection (through a NAT) using the different VNX root file-systems. They are included to easily allow modifying root filesystems (for example, to install new software packages).</li> | <li> '''rootfs_XXX.xml''', which are libvirt specifications to start virtual machines with Internet connection (through a NAT) using the different VNX root file-systems. They are included to easily allow modifying root filesystems (for example, to install new software packages).</li> | ||
− | + | --> | |
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− |
Revision as of 23:28, 7 May 2012
Updating or modifying a VNX root filesystem
In order to update or modify a VNX root filesystem (rootfs from now on), you have to:
- Using the vnx_modify_rootfs tool (recommended):
vnx_modify_rootfs <rootfs_name>
being <rootfs_name> the rootfs filename.
virsh create rootfs_XXX.xml
and manually opening the console using:
virt-viewer <vmname>
being <vmname> the name assigned by libvirt to the virtual machine (you can get it with "virsh list" command or just looking for the <name> tag in root_fs_XXX.xml file).
Updating VNXACE daemon
If you have a rootfs with the autoconfiguration and command execution daemon (ACE) already installed, you can use the autoupdate functionality to update the daemon to a newer version. Just follow this procedure:
Linux and FreeBSD
- Once the virtual machine is running, execute the update utility:
/usr/share/vnx/bin/vnx_update_aced <vmname> /usr/share/vnx/aced/<vnxaced_file_name>
being <vmname> the name assigned by libvirt to the virtual machine, and <vnxaced_file_name> the filename of the latest VNXACE version (just have a look at /usr/share/vnx/aced directory take the highest version number). For example:
# virsh list Id Nombre Estado
10 vnx_rootfs_kvm_ubuntu-12.04-v023.qcow2 running # /usr/share/vnx/bin/vnx_update_aced vnx_rootfs_kvm_ubuntu-12.04-v023.qcow2 /usr/share/vnx/aced/vnx-aced-lf-2.0b.1882.tgz
In case the VNXACE daemon is not automatilly updated, you can do it manually. From inside the VM:
- Mount the cdrom with:
mount /media/cdrom
perl /media/cdrom/install_vnxaced
Windows
To be completed
Olive
To be completed