Hi Axel,<div><br></div><div>Thank you for the response. Some more questions inline. </div><div><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div><br>
</div>The 4.3 .deb for the PPA is still missing. I may release have to<br>
release a 4.3.1 which fixes some testsuite issues, this time with 32<br>
bit architectures. And since Ubuntu builds their .debs for the PPAs on<br>
32 bit...<br>
<br>
The 4.3 .deb is also available from<br>
<a href="http://xen-tools.org/software/xen-tools/releases.html" target="_blank">http://xen-tools.org/software/xen-tools/releases.html</a> so anyone who<br>
needs to install Precise DomUs should consider using that one. I'll<br>
(try to :-) update the PPA as soon as I got the next release out.<br>
<div><br></div></blockquote><div><br></div><div>I am using Precise Pangolin - Ubuntu 12.04 (64bit) as the dom0. Will the PPA eventually have precise (12.04) packages too? I tried to follow the instructions on your Launchpad/ppa website, <a href="https://launchpad.net/~xtaran/+archive/xen-tools" target="_blank">https://launchpad.net/~xtaran/+archive/xen-tools</a> and add the repo "<strong style="line-height:18px;text-align:left;color:rgb(51,51,51);font-size:12px;font-family:Ubuntu,'Bitstream Vera Sans','DejaVu Sans',Tahoma,sans-serif">ppa:xtaran/xen-tools"</strong>. However when I do an "apt-get update" to get the updates it throws an error. That is probably because there are no 12.04 packages yet? Also, it seems like the xen-tools package builds failed? </div>
<div><br></div><div>Could I just get the source or the .deb from the xen-tools website and install it? It will clobber the current Ubuntu installed version of xen-tools (4.2.1) and not sure if that has any issues later... </div>
<div><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">I must admit, I always did this manually before, either with dd or<br>
lvcreate -s for the image and cp for the config file. But I do see<br>
that you may want to have the whole machinery running which modifies<br>
the installation.<br>
<div></div></blockquote><div><br></div><div>This is not a problem. I can also dd testvm2/disk.img (although dd will expand the sparse disk image which is not ideal) to create a new VM testvm3 for example. But as you mention, I would still need to modify all the files that make the two distinct. These include, /etc/hosts, /etc/hostname, /etc/network/interfaces, and I am sure what other files also need to be installed/edited. The OpenSSH generated keys for example also need to be changed? I was hoping that the "copy" or the "tar" methods of install could take of these things... </div>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div> </div></blockquote><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div>
> For example, I have a VM image created (testvm2) that has a disk image<br>
> (file backed: disk.img) and a swap file (file backed: swap.img) using<br>
> xen-create-image. This image uses pygrub and also runs Ubuntu 12.04 (32<br>
> bit) in the domU. I have customized it in various ways and next I want to<br>
> create a clone of this VM image quickly, lets say "testvm3" and make<br>
> whatever changes I need to it so that the two images are distinct and can<br>
> both run *simultaneously*. It seems like I should be able to do the<br>
> following:<br>
><br>
> 1. I tarred up the disk.img file and named it:<br>
> /home/xen/testvm2-disk.img.tar<br>
<br>
</div>That doesn't work. The tar file xen-tools expects should contain the<br>
contents of an installed system (i.e. files like /bin/ls, /bin/cp,<br>
etc.), not an block device image as file.<br>
<div><br></div></blockquote><div>So, is the following the right way to do it then? I should probably remove the /proc/ and /sys/ directories from the tar in Step (b) below? </div><div> </div><div>(a) mount /home/xen/domains/testvm2/disk.img /mnt/baseimage -i loop </div>
<div>(b) tar cvf /mnt/baseimage.tar /mnt/baseimage </div><div>(c) xen-create-image --hostname=testvm3 --size=2G --swap=128M --ip=10.16.17.67 --netmask=255.255.255.0 --gateway=10.16.17.1 --force --bridge=eth0-br --dir=/home/xen --memory=64M --install-method=tar --install-source=/mnt/baseimage.tar
</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div>
> 2. xen-create-image --hostname=testvm3 --size=2G --swap=128M<br>
> --ip=10.16.17.67 --netmask=255.255.255.0<br>
> --gateway=10.16.17.1 --force --bridge=eth0-br --dir=/home/xen --memory=64M<br>
> --install-method=tar --install-source=/home/xen/testvm2-disk.img.tar<br>
><br>
> That does not seem to work and fails with the following error. Any thoughts<br>
> on how to fix this will be appreciated.<br>
<br>
</div>You are not the first one asking for or expecting such a feature, see<br>
<a href="http://bugs.debian.org/377984" target="_blank">http://bugs.debian.org/377984</a> (I think installing from an image and<br>
duplicating a DomU is quite similar.)<br>
<br></blockquote><div>Yes, I think the feature would be useful! </div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
I will think about I can best implement such a feature, but I can't<br>
promise anything. I'm open for suggestions (and patches :-) though!<br>
<br>
Kind regards, Axel<br>
<span><font color="#888888">--<br>
/~\ Plain Text Ribbon Campaign | Axel Beckert<br>
\ / Say No to HTML in E-Mail and News | <a href="mailto:abe@deuxchevaux.org" target="_blank">abe@deuxchevaux.org</a> (Mail)<br>
X See <a href="http://www.asciiribbon.org/" target="_blank">http://www.asciiribbon.org/</a> | <a href="mailto:abe@noone.org" target="_blank">abe@noone.org</a> (Mail+Jabber)<br>
/ \ I love long mails: <a href="http://email.is-not-s.ms/" target="_blank">http://email.is-not-s.ms/</a> | <a href="http://noone.org/abe/" target="_blank">http://noone.org/abe/</a> (Web)<br>
_______________________________________________<br>
xen-tools-discuss mailing list<br>
<a href="mailto:xen-tools-discuss@xen-tools.org" target="_blank">xen-tools-discuss@xen-tools.org</a><br>
<a href="https://xen-tools.org/mailman/listinfo/xen-tools-discuss" target="_blank">https://xen-tools.org/mailman/listinfo/xen-tools-discuss</a></font></span></blockquote></div>
</div>