Difference between revisions of "Vnx-rootfsubuntu"

From VNX
Jump to: navigation, search
(Configuration)
(Configuration)
 
(45 intermediate revisions by the same user not shown)
Line 1: Line 1:
{{Title|How to create a Ubuntu root-file-system for VNX}}
+
{{Title|How to create a KVM Ubuntu root filesystem for VNX}}
  
 
== Basic installation ==
 
== Basic installation ==
  
Follow this procedure to create a Ubuntu based root-file-system for VNX. The procedure has been tested with Ubuntu 9.10 and 10.04.
+
Follow this procedure to create a KVM Ubuntu based root filesystem for VNX. The procedure has been tested with Ubuntu 9.10, 10.04, 10.10, 11.04, 12.04, 13.04, 13.10, 14.04, 14.10, 15.04, 15.10 and 16.04.
 
<ul>
 
<ul>
 
<li>Create the filesystem disk image:</li>
 
<li>Create the filesystem disk image:</li>
  qemu-img create -f qcow2 root_fs_ubuntu-base.qcow2 5GB
+
  qemu-img create -f qcow2 vnx_rootfs_kvm_ubuntu.qcow2 20G
 
<li>Get Ubuntu installation CD. For example:</li>
 
<li>Get Ubuntu installation CD. For example:</li>
  wget ftp://ftp.rediris.es/mirror/ubuntu-releases/10.04.1/ubuntu-10.04.1-server-i386.iso
+
  wget ftp://ftp.rediris.es/mirror/ubuntu-releases/16.04/ubuntu-16.04-server-i386.iso
  cp ubuntu-10.04.1-server-i386.iso /almacen/iso
+
  cp ubuntu-16.04-server-i386.iso /almacen/iso
<li>Create a libvirt XML definition (root_fs_ubuntu.xml) containing the virtual machine description:</li>
+
Note: use 'server' or 'desktop' CD versions depending on the system you want to create.
<pre>
+
<li>Create the virtual machine with:</li>
<domain type='kvm'>
+
vnx --create-rootfs vnx_rootfs_kvm_ubuntu.qcow2 --install-media /almacen/iso/ubuntu-16.04-server-i386.iso --mem 512M
  <name>Ubuntu</name>
+
Note: add '''"--arch x86_64"''' option for 64 bits virtual machines
  <memory>524288</memory>
+
<li>Follow Ubuntu installation menus to install a basic system with ssh server.</li>
  <vcpu>1</vcpu>
+
<li>Configure a serial console on ttyS0 (skip this step for 15.04 or later releases):</li>
  <os>
+
cd /etc/init
    <type arch="i686">hvm</type>
+
cp tty1.conf ttyS0.conf
    <boot dev='hd'/>
+
sed -i -e 's/tty1/ttyS0/' ttyS0.conf
    <boot dev='cdrom'/>
+
<li>Activate startup traces on serial console by editting /etc/default/grub file and setting the GRUB_CMDLINE_LINUX_DEFAULT variable to "console=ttyS0". Also change the boot menu timeout to 0 (sometimes virtual machines get stopped on the boot menu when starting on high loaded systems):</li>
  </os>
+
GRUB_CMDLINE_LINUX_DEFAULT="console=ttyS0"
  <features>
+
GRUB_TIMEOUT=0
    <pae/>
+
GRUB_RECORDFAIL_TIMEOUT=1
    <acpi/>
+
<li>Only for Ubuntu 15.10 or later releases:</li>
    <apic/>
+
GRUB_CMDLINE_LINUX="net.ifnames=0 biosdevname=0"
  </features>
+
<li>Make grub process the previous changes:</li>
  <clock sync="localtime"/>
+
  update-grub
  <devices>
+
<li>Add a timeout to systemd-networkd-wait-online service to avoid long waits at startup. Edit /lib/systemd/system/systemd-networkd-wait-online.service and change the following line:</li>
    <emulator>/usr/bin/kvm</emulator>
+
  ExecStart=/lib/systemd/systemd-networkd-wait-online --timeout 20
    <disk type='file' device='disk'>
+
<li>Finally, delete the net udev rules file and halt the system:</li>
      <source file='/usr/share/vnx/filesystems/root_fs_ubuntu-base.qcow2'/>
+
rm /etc/udev/rules.d/70-persistent-net.rules
      <target dev='hda'/>
+
halt -p
      <driver name="qemu" type="qcow2"/>
 
    </disk>
 
    <disk type='file' device='cdrom'>
 
      <source file='/almacen/iso/ubuntu-10.04.1-server-i386.iso'/>
 
      <target dev='hdb'/>
 
    </disk>
 
    <interface type='network'>
 
      <source network='default'/>
 
    </interface>
 
    <graphics type='vnc'/>
 
  </devices>
 
</domain>
 
</pre>
 
Note: change "source file=" lines to whatever fits your case (use full paths).
 
 
 
<li>Start the virtual machine with:</li>
 
  virsh create root_fs_ubuntu.xml
 
<li>Access virtual machine console with:</li>
 
  virt-viewer Ubuntu
 
Note: alternative you can start the machine and open the console at the same time with the command:
 
/usr/share/vnx/bin/vnx_modify_rootfs root_fs_ubuntu.xml
 
<li>Follow Ubuntu installation menus to install a basic system with ssh server. Once the installation is finished, stop the machine and edit root_fs_ubuntu.xml file and comment the following line in cdrom disk specification:</li>
 
<pre>
 
  <!--source file='/almacen/iso/ubuntu-10.04-server-i386.iso'/-->
 
</pre>
 
 
</ul>
 
</ul>
  
Line 62: Line 37:
  
 
<ul>
 
<ul>
<li>Start the virtual machine again and finish the installation:</li>
+
<li>Restart the system with the following command:</li>
<ul>
+
vnx --modify-rootfs vnx_rootfs_kvm_ubuntu.qcow2 --update-aced --mem 512M
<li>Access the console and sudo root: </li>
+
Note: add '''"--arch x86_64"''' option for 64 bits virtual machines
 +
Note: ignore the errors "timeout waiting for response on VM socket". 768M are needed if you are installing a root filesystem with desktop interface
 +
<li>Access the system through the text console to easy the copy-paste of commands:</li>
 +
virsh console vnx_rootfs_kvm_ubuntu.qcow2
 +
<li>Access the console and sudo root:</li>
 
  sudo su
 
  sudo su
 
<li>Update the system</li>
 
<li>Update the system</li>
Line 70: Line 49:
 
  apt-get dist-upgrade
 
  apt-get dist-upgrade
 
<li>Install XML::DOM perl package and ACPI daemon:</li>
 
<li>Install XML::DOM perl package and ACPI daemon:</li>
  apt-get install libxml-dom-perl acpid
+
  apt-get install libxml-libxml-perl libnetaddr-ip-perl acpid
<li>Only for Ubuntu 10.04:</li>
+
<li>For 17.10 or newer install ifupdown</li>
 +
apt-get install ifupdown
 +
<!--li>Only for Ubuntu 10.04:</li>
 
<ul>
 
<ul>
 
<li>create /media/cdrom* directories:</li>
 
<li>create /media/cdrom* directories:</li>
Line 81: Line 62:
 
  /dev/scd0  /media/cdrom0    udf,iso9660  user,noauto,exec,utf8  0  0
 
  /dev/scd0  /media/cdrom0    udf,iso9660  user,noauto,exec,utf8  0  0
 
  /dev/scd1  /media/cdrom1    udf,iso9660  user,noauto,exec,utf8  0  0
 
  /dev/scd1  /media/cdrom1    udf,iso9660  user,noauto,exec,utf8  0  0
</ul>
+
</ul-->
<li>Configure a serial console on ttyS0:</li>
 
cd /etc/init
 
cp tty1.conf ttyS0.conf
 
sed -i -e 's/tty1/ttyS0/' ttyS0.conf
 
<li>Activate startup traces on serial console by editting /boot/grub/grub.cfg file and adding "console=ttyS0" to the linux line. For example:</li>
 
linux  /boot/vmlinuz-2.6.35-25-generic-pae root=UUID=eb1a0afb-48b2-4e42-ba6d-22bfae1055f3 ro  quiet console=ttyS0
 
 
<li>Install VNX autoconfiguration daemon:</li>
 
<li>Install VNX autoconfiguration daemon:</li>
<ul>
+
  mount /dev/sdb /mnt/
<li>From the host execute:</li>
+
perl /mnt/vnxaced-lf/install_vnxaced
  /usr/share/vnx/bin/vnx_update_aced Ubuntu /usr/share/vnx/aced/vnx-aced-lf-0.1b.tgz
+
Change 'sdb' by 'vdb' in case virtio drivers are being used.
<li>From the virtual machine console:</li>
+
<li>Edit /etc/network/interfaces file and comment all lines related to eth0, eth1, etc interfaces. Leave only the loopback (lo) interface.</li>
mount /media/cdrom
 
/media/cdrom/install_vnxdaemon
 
</ul>
 
 
<li>Optional: install graphical user interface.</li>
 
<li>Optional: install graphical user interface.</li>
 
<ul>
 
<ul>
 
<li>Minimal:</li>
 
<li>Minimal:</li>
 +
# recommended option
 +
sudo apt-get install lubuntu-desktop
 +
 +
# old recipe not tested in later versions
 
  sudo apt-get install xorg gnome-core gksu gdm gnome-system-tools gnome-nettool firefox-gnome-support
 
  sudo apt-get install xorg gnome-core gksu gdm gnome-system-tools gnome-nettool firefox-gnome-support
 
<li>Complete:</li>
 
<li>Complete:</li>
 
  sudo apt-get install ubuntu-desktop
 
  sudo apt-get install ubuntu-desktop
 +
Note: to avoid nautilus being launched any time you remotely execute a command on the virtual machine using VNX (which interferes with the normal execution of commands), you should disable the start of programs when media insertion takes place. Go to "System settings->System->Details->Removable Media" and deselect the checkbox "Never prompt or start programs on media insertion".
 +
<!--
 +
nautilus automount feature. Just execute gconf-editor and create a variable "/apps/nautilus/preferences/media_automount" and set it to 0.
 +
This does not seem to work:
 +
gconftool-2 --direct --config-source xml:readwrite:/etc/gconf/gconf.xml.mandatory --type bool --set "/apps/nautilus/preferences/media_automount" "false"
 +
gconftool-2 --direct --config-source xml:readwrite:/etc/gconf/gconf.xml.mandatory --type bool --set "/apps/nautilus/preferences/media_automount_open" "false"
 +
-->
 
</ul>
 
</ul>
 
<li>Optional: install other services:</li>
 
<li>Optional: install other services:</li>
Line 108: Line 91:
 
  sudo apt-get install apache2
 
  sudo apt-get install apache2
 
  update-rc.d -f apache2 remove  # to avoid automatic start
 
  update-rc.d -f apache2 remove  # to avoid automatic start
<li>Other network tools</li>
+
<li>Other tools</li>
 
  sudo apt-get install traceroute
 
  sudo apt-get install traceroute
 +
sudo apt-get install xterm  # needed to have the 'resize' tool to resize consoles
 
</ul>
 
</ul>
  
<li>Edit the "message of the day" file (/etc/motd) and add the following message:</li>
+
<li>Create a file /etc/vnx_rootfs_version to store version number and informacion about modification:</li>
 
<pre>
 
<pre>
  ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
VER=v0.25
  ~~~~~                  WARNING!                  ~~~~~
+
OS=Ubuntu 16.04 32 bits
  ~~~~~      VNX Autoconfiguration in progress...   ~~~~~
+
DESC=Basic Ubuntu 16.04 root filesystem without GUI
  ~~~~~    Wait until the virtual machine reboots    ~~~~~
 
  ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
 
</pre>
 
</pre>
  
<li>Create a file /etc/vnx_root_fs_version to store version number and informacion about modification:</li>
+
<li>Zero the image empty space to allow reducing the size of the image:</li>
<pre>
+
dd if=/dev/zero of=/mytempfile
VER=v0.21
+
rm -f /mytempfile
OS=Ubuntu 10.10
 
DESC=basic Ubuntu 10.10 root-file-system without GUI
 
</pre>
 
  
<li>Create a script named /usr/local/bin/vnx_halt:</li>
+
<li>Stop the machine with vnx_halt:</li>
<pre>
+
sudo vnx_halt
#!/bin/bash
 
# Clean apt cache
 
apt-get clean
 
apt-get -y autoremove
 
# Delete /etc/resolv.conf
 
rm -f /etc/resolv.conf
 
# Clean command history
 
rm -f /root/.bash_history
 
# Delete udev net rules files:
 
rm -f /etc/udev/rules.d/70-persistent-net.rules
 
while true; do
 
    # Ask for a message to save in /etc/vnx_root_fs_version file
 
    echo    "** Save a log message in /etc/vnx_root_fs_version file "
 
    echo -n "** describing the modifications done? "
 
    read -n 1 -p "[y/n] " answer
 
    echo ""
 
    case $answer in
 
        [Yy]* )
 
                echo "** Log message (1 line maximum):"
 
                read logmsg
 
                DATE=`date`
 
                echo "MODDATE=$DATE" >> /etc/vnx_root_fs_version
 
                echo "MODDESC=$logmsg" >> /etc/vnx_root_fs_version
 
                break;;
 
        [Nn]* ) break;;
 
        * )    echo "** Error: please answer 'y' or 'n'.";;
 
    esac
 
done
 
# Halt the system
 
halt
 
</pre>
 
  
<li>Give the script execution permissions:</li>
+
<li>Reduce the size of the image:</li>
  chmod +x /usr/local/bin/vnx_halt
+
  mv vnx_rootfs_kvm_ubuntu.qcow2 vnx_rootfs_kvm_ubuntu.qcow2.bak
 +
qemu-img convert -O qcow2 vnx_rootfs_kvm_ubuntu.qcow2.bak vnx_rootfs_kvm_ubuntu.qcow2
  
<li>Stop the machine with that script:</li>
 
vnx_halt
 
</ul>
 
 
</ul>
 
</ul>
  
If everything went well, your root filesystem will be ready to be used with VNX. You can make a simple test using the simple_ubuntu.xml scenario distributed with VNX.  
+
If everything went well, your root filesystem will be ready to be used with VNX. You can make a simple test using the simple_ubuntu.xml scenario distributed with VNX.
  
=== Installing additional software ===
+
== Installing additional software ==
  
To install additional software or modify your root file system, you just have to start it as described above and make the operations required on the filesystem.
+
To install additional software or to modify your root file system, you just have to:
 
<ul>
 
<ul>
<li>Start the virtual machine (directly using virsh or the vnx_modify_rootfs utility):</li>
+
<li>Start a virtual machine from it:</li>
  /usr/share/vnx/bin/vnx_modify_rootfs root_fs_ubuntu.xml
+
vnx --modify-rootfs vnx_rootfs_kvm_ubuntu.qcow2
<li>Install the software:</li>
+
<li>Check network connectivity. Maybe you have to activate the network interface by hand:</li>
  apt-get install ...
+
  dhclient eth0
<li>Stop the machine with:</li>
+
Note: use "ip link show" to know which network interface to use.
 +
<li>Do the modifications you want.</li>
 +
<li>Finally, halt the system using:</li>
 
  vnx_halt
 
  vnx_halt
 
</ul>
 
</ul>
  
=== Updating ACE daemon ===
+
==== Examples ====
 +
 
 +
<ul>
 +
<li>dhcp server and relay:</li>
 +
<ul>
 +
<li>Install dhcp3 packages:</li>
 +
apt-get install dhcp3-server dhcp3-relay
 +
<li>Disable autostart (optional):</li>
 +
update-rc.d -f isc-dhcp-server remove
 +
update-rc.d -f isc-dhcp-relay remove
 +
</ul>
  
If you have a root filesystem with the autoconfiguration and command execution daemon (ACE) already installed, you can use the autoupdate functionallity to update the daemon to a newer version. Just follow this procedure:
 
  
<ul>
 
<li>Edit the xml described above and comment the line defining the Ubuntu iso file for the cdrom:</li>
 
  <!--source file='/almacen/iso/ubuntu-10.04-server-i386.iso'/-->
 
<li>Start the virtual machine (directly using virsh or the vnx_modify_rootfs utility):</li>
 
  /usr/share/vnx/bin/vnx_modify_rootfs root_fs_ubuntu.xml
 
<li>Execute the update utility:</li>
 
/usr/share/vnx/bin/vnx_update_aced Ubuntu /usr/share/vnx/aced/vnx-aced-lf-0.1b.tgz
 
<li>Once the ace daemon is updated the virtual machine will be rebooted automatically.</li>
 
 
</ul>
 
</ul>
  
=== Known problems ===
+
== Updating VNXACED ==
 +
 
 +
You can automatically update the VNXACE daemon with the following command:
 +
vnx --modify-rootfs vnx_rootfs_kvm_ubuntu.qcow2 --update-aced -y
 +
If VNXACE daemon is not updated automatically, you can do it manually by accessing the virtual machine console and type:
 +
mount /dev/sdb /mnt/
 +
perl /mnt/vnxaced-lf/install_vnxaced
 +
 
 +
== Known problems ==
  
 
<ul>
 
<ul>
 +
<li>Sometimes after restarting, the virtual machines stop at showing the grub menu and do not start until you manually choose one option. To avoid it, just follow the instructions here: http://www.linuxquestions.org/questions/linux-server-73/how-to-disable-grub-2-menu-even-after-server-crash-796562/. Beware that the changes you make to grub.cfg file are lost after executing "update-grub" command.
 +
</li>
 +
<li>In Ubuntu 12.04 Desktop, graphical commands execution does not work. Command execution fails with "ERROR: no user logged on display :0.0" (see /var/log/vnxaced.log). If you just open a "terminal" window, commands work correctly (does not work if you open other applications; only when you start a terminal...).</li>
 
<li>Each time a cdrom is mounted (for example, whenever a command is executed on the virtual machine) the following error appears in the console:</li>
 
<li>Each time a cdrom is mounted (for example, whenever a command is executed on the virtual machine) the following error appears in the console:</li>
 
<pre>
 
<pre>

Latest revision as of 03:33, 11 February 2018

How to create a KVM Ubuntu root filesystem for VNX

Basic installation

Follow this procedure to create a KVM Ubuntu based root filesystem for VNX. The procedure has been tested with Ubuntu 9.10, 10.04, 10.10, 11.04, 12.04, 13.04, 13.10, 14.04, 14.10, 15.04, 15.10 and 16.04.

  • Create the filesystem disk image:
  • qemu-img create -f qcow2 vnx_rootfs_kvm_ubuntu.qcow2 20G
    
  • Get Ubuntu installation CD. For example:
  • wget ftp://ftp.rediris.es/mirror/ubuntu-releases/16.04/ubuntu-16.04-server-i386.iso
    cp ubuntu-16.04-server-i386.iso /almacen/iso
    

    Note: use 'server' or 'desktop' CD versions depending on the system you want to create.

  • Create the virtual machine with:
  • vnx --create-rootfs vnx_rootfs_kvm_ubuntu.qcow2 --install-media /almacen/iso/ubuntu-16.04-server-i386.iso --mem 512M
    

    Note: add "--arch x86_64" option for 64 bits virtual machines

  • Follow Ubuntu installation menus to install a basic system with ssh server.
  • Configure a serial console on ttyS0 (skip this step for 15.04 or later releases):
  • cd /etc/init
    cp tty1.conf ttyS0.conf
    sed -i -e 's/tty1/ttyS0/' ttyS0.conf
    
  • Activate startup traces on serial console by editting /etc/default/grub file and setting the GRUB_CMDLINE_LINUX_DEFAULT variable to "console=ttyS0". Also change the boot menu timeout to 0 (sometimes virtual machines get stopped on the boot menu when starting on high loaded systems):
  • GRUB_CMDLINE_LINUX_DEFAULT="console=ttyS0"
    GRUB_TIMEOUT=0
    GRUB_RECORDFAIL_TIMEOUT=1
    
  • Only for Ubuntu 15.10 or later releases:
  • GRUB_CMDLINE_LINUX="net.ifnames=0 biosdevname=0"
    
  • Make grub process the previous changes:
  • update-grub
    
  • Add a timeout to systemd-networkd-wait-online service to avoid long waits at startup. Edit /lib/systemd/system/systemd-networkd-wait-online.service and change the following line:
  • ExecStart=/lib/systemd/systemd-networkd-wait-online --timeout 20
    
  • Finally, delete the net udev rules file and halt the system:
  • rm /etc/udev/rules.d/70-persistent-net.rules
    halt -p
    

Configuration

  • Restart the system with the following command:
  • vnx --modify-rootfs vnx_rootfs_kvm_ubuntu.qcow2 --update-aced --mem 512M
    

    Note: add "--arch x86_64" option for 64 bits virtual machines Note: ignore the errors "timeout waiting for response on VM socket". 768M are needed if you are installing a root filesystem with desktop interface

  • Access the system through the text console to easy the copy-paste of commands:
  • virsh console vnx_rootfs_kvm_ubuntu.qcow2
    
  • Access the console and sudo root:
  • sudo su
    
  • Update the system
  • apt-get update
    apt-get dist-upgrade
    
  • Install XML::DOM perl package and ACPI daemon:
  • apt-get install libxml-libxml-perl libnetaddr-ip-perl acpid
    
  • For 17.10 or newer install ifupdown
  • apt-get install ifupdown
    
  • Install VNX autoconfiguration daemon:
  • mount /dev/sdb /mnt/
    perl /mnt/vnxaced-lf/install_vnxaced
    

    Change 'sdb' by 'vdb' in case virtio drivers are being used.

  • Edit /etc/network/interfaces file and comment all lines related to eth0, eth1, etc interfaces. Leave only the loopback (lo) interface.
  • Optional: install graphical user interface.
    • Minimal:
    • # recommended option
      sudo apt-get install lubuntu-desktop
      
      # old recipe not tested in later versions
      sudo apt-get install xorg gnome-core gksu gdm gnome-system-tools gnome-nettool firefox-gnome-support
      
    • Complete:
    • sudo apt-get install ubuntu-desktop
      

      Note: to avoid nautilus being launched any time you remotely execute a command on the virtual machine using VNX (which interferes with the normal execution of commands), you should disable the start of programs when media insertion takes place. Go to "System settings->System->Details->Removable Media" and deselect the checkbox "Never prompt or start programs on media insertion".

  • Optional: install other services:
    • Apache server:
    • sudo apt-get install apache2
      update-rc.d -f apache2 remove   # to avoid automatic start
      
    • Other tools
    • sudo apt-get install traceroute
      sudo apt-get install xterm   # needed to have the 'resize' tool to resize consoles 
      
  • Create a file /etc/vnx_rootfs_version to store version number and informacion about modification:
  • VER=v0.25
    OS=Ubuntu 16.04 32 bits
    DESC=Basic Ubuntu 16.04 root filesystem without GUI
    
  • Zero the image empty space to allow reducing the size of the image:
  • dd if=/dev/zero of=/mytempfile
    rm -f /mytempfile
    
  • Stop the machine with vnx_halt:
  • sudo vnx_halt
    
  • Reduce the size of the image:
  • mv vnx_rootfs_kvm_ubuntu.qcow2 vnx_rootfs_kvm_ubuntu.qcow2.bak
    qemu-img convert -O qcow2 vnx_rootfs_kvm_ubuntu.qcow2.bak vnx_rootfs_kvm_ubuntu.qcow2
    

If everything went well, your root filesystem will be ready to be used with VNX. You can make a simple test using the simple_ubuntu.xml scenario distributed with VNX.

Installing additional software

To install additional software or to modify your root file system, you just have to:

  • Start a virtual machine from it:
  • vnx --modify-rootfs vnx_rootfs_kvm_ubuntu.qcow2
    
  • Check network connectivity. Maybe you have to activate the network interface by hand:
  • dhclient eth0
    

    Note: use "ip link show" to know which network interface to use.

  • Do the modifications you want.
  • Finally, halt the system using:
  • vnx_halt
    

Examples

  • dhcp server and relay:
    • Install dhcp3 packages:
    • apt-get install dhcp3-server dhcp3-relay
      
    • Disable autostart (optional):
    • update-rc.d -f isc-dhcp-server remove
      update-rc.d -f isc-dhcp-relay remove
      


Updating VNXACED

You can automatically update the VNXACE daemon with the following command:

vnx --modify-rootfs vnx_rootfs_kvm_ubuntu.qcow2 --update-aced -y

If VNXACE daemon is not updated automatically, you can do it manually by accessing the virtual machine console and type:

mount /dev/sdb /mnt/
perl /mnt/vnxaced-lf/install_vnxaced

Known problems

  • Sometimes after restarting, the virtual machines stop at showing the grub menu and do not start until you manually choose one option. To avoid it, just follow the instructions here: http://www.linuxquestions.org/questions/linux-server-73/how-to-disable-grub-2-menu-even-after-server-crash-796562/. Beware that the changes you make to grub.cfg file are lost after executing "update-grub" command.
  • In Ubuntu 12.04 Desktop, graphical commands execution does not work. Command execution fails with "ERROR: no user logged on display :0.0" (see /var/log/vnxaced.log). If you just open a "terminal" window, commands work correctly (does not work if you open other applications; only when you start a terminal...).
  • Each time a cdrom is mounted (for example, whenever a command is executed on the virtual machine) the following error appears in the console:
  • Jul 27 22:33:31 vnx kernel: [ 4384.875886] ata1.01: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6
    Jul 27 22:33:31 vnx kernel: [ 4385.291374] ata1.01: BMDMA stat 0x5
    Jul 27 22:33:31 vnx kernel: [ 4385.493411] sr 0:0:1:0: [sr0] CDB: Read(10): 28 00 00 00 00 18 00 00 01 00
    Jul 27 22:33:31 vnx kernel: [ 4385.493460] ata1.01: cmd a0/01:00:00:00:08/00:00:00:00:00/b0 tag 0 dma 2048 in
    Jul 27 22:33:31 vnx kernel: [ 4385.493461]          res 01/60:00:00:00:08/00:00:00:00:00/b0 Emask 0x3 (HSM violation)
    Jul 27 22:33:31 vnx kernel: [ 4386.263553] ata1.01: status: { ERR }
    

    Despite of the error trace, the commands are executed correctly. This error does not appear on Ubuntu 9.10 filesystems.