Permalink
Browse files

updating doc to reflect most of the comments from Dan Yocum

we still need to add console access for KVM
  • Loading branch information...
1 parent fb4fc6a commit 90a95e3befe457e5598687176ce7e415a71d512f @buzztroll buzztroll committed Jun 22, 2011
Showing with 27 additions and 7 deletions.
  1. +27 −7 docs/src/admin/z2c/vmm-setup.html
@@ -247,15 +247,15 @@
First, make the nimbus user a member of the root group:
</p>
<div class="panel"><pre>
-root # usermod -a -G root nimbus
+root # usermod -a -G libvirtd nimbus
</pre></div>
<p>
Make the libvirt domain socket available for reading and writing by the root group by enabling the following configurations in <tt class="literal">/etc/libvirt/libvirtd.conf</tt>
</p>
<div class="panel"><pre>
-unix_sock_group = "root"
+unix_sock_group = "libvirtd"
unix_sock_ro_perms = "0770"
unix_sock_rw_perms = "0770"
unix_sock_dir = "/var/run/libvirt"
@@ -298,7 +298,7 @@
<div class="panel"><pre>
root # wget http://www.nimbusproject.org/downloads/nimbus-controls-2.8.tar.gz
root # tar xfz nimbus-controls-2.8.tar.gz
-root # mv nimbus-controls-2.8/workspace-control/ /opt/nimbus
+root # mv nimbus-controls-2.8/workspace-control/* /opt/nimbus
</pre></div>
<p>
@@ -365,6 +365,9 @@
nimbus $ cp /boot/vmlinuz-2.6.16.29-xen $KERNELDIR/default
nimbus $ cp /boot/initrd-2.6.16.29-xen $KERNELDIR/default-initrd
</pre></div>
+<div class="note">
+The files under /boot may only be readable by root so you may need to become root to access them.
+</div>
<p>
Now you have created a kernel called <tt class="literal">default</tt> that workspace-control will launch paravirtualized VMs with. The default kernel and initrd to use for VMs is controlled by the <tt class="literal">authz_kernels</tt> configuration in <tt class="literal">/opt/nimbus/etc/workspace-control/kernels.conf</tt> (by default the authorized kernel is "default").
@@ -572,7 +575,9 @@
</p>
<p>
- The <tt class="literal">--mountpoint</tt> value will be <tt class="literal">sda1</tt> for the nimbus-z2c image.
+ The <tt class="literal">--mountpoint</tt> value will be <tt class="literal">sda1</tt> if you are using xen and
+<tt class="literal">hda</tt> if you are using kvm
+ for the nimbus-z2c image.
</p>
<p>
@@ -583,10 +588,14 @@
Run the following:
</p>
-<div class="panel"><pre>
+<div class="xenpanel"><pre>
nimbus $ ./sbin/libvirt-xml.sh --image /tmp/nimbus-z2c --netsample \
/tmp/control.netsample.txt --memory 256 --mountpoint sda1
</pre></div>
+<div class="kvmpanel"><pre>
+nimbus $ ./sbin/libvirt-xml.sh --image /tmp/nimbus-z2c --netsample \
+/tmp/control.netsample.txt --memory 256 --mountpoint hda
+</pre></div>
<p>
On stdout, you will see an XML document printed.
@@ -623,10 +632,14 @@
<p>
Once you have the XML getting printed, capture it to a file:
</p>
-<div class="panel"><pre>
+<div class="xenpanel"><pre>
nimbus $ ./sbin/libvirt-xml.sh --image /tmp/nimbus-z2c --netsample \
/tmp/control.netsample.txt --memory 256 --mountpoint sda1 > /tmp/z2c.xml
</pre></div>
+<div class="kvmpanel"><pre>
+nimbus $ ./sbin/libvirt-xml.sh --image /tmp/nimbus-z2c --netsample \
+/tmp/control.netsample.txt --memory 256 --mountpoint hda > /tmp/z2c.xml
+</pre></div>
<div class="note">
<p class="note-title">Remember to keep destroying the control-test</p>
@@ -738,13 +751,20 @@
Gather the same arguments you used for <tt class="literal">./sbin/libvirt-xml.sh</tt>
</p>
-<div class="panel"><pre>
+<div class="xenpanel"><pre>
$ ./sbin/control-test.sh --image /tmp/nimbus-z2c --netsample \
/tmp/control.netsample.txt --memory 256 --mountpoint sda1
$ echo $?
0
</pre></div>
+<div class="kvmpanel"><pre>
+$ ./sbin/control-test.sh --image /tmp/nimbus-z2c --netsample \
+/tmp/control.netsample.txt --memory 256 --mountpoint hda
+
+$ echo $?
+0
+</pre></div>
<p>

0 comments on commit 90a95e3

Please sign in to comment.