I am now successfully runninf 4 UML instances in a virtual network with COW files. It is a very good feature as my original filesystem remains intact and only COW files are written into. And still I can access all data on my original root_fs without wasting any disk space (that would have required
On Tuesday 30 May 2006 20:07, Brock, Anthony - NET wrote:
> You need to create a separate COW file (probably based of the same
> original image) for each instance. Your customizations will then be
> written to the COW file while preserving the base image intact. This
> will also bypass the file loc
> -Original Message-
> On Tuesday 30 May 2006 20:07, Brock, Anthony - NET wrote:
> > You need to create a separate COW file (probably based of the same
> > original image) for each instance. Your customizations will then be
> > written to the COW file while preserving the base image intact.
, 2006 10:57 AMTo: Brock, Anthony - NETCc:
user-mode-linux-user@lists.sourceforge.netSubject: Re: [uml-user] Problems in sharing filesystems between Virtual Machines
But I am facing another problem. I have created the COW file and UML boots properly. But now when I boot another UML instance from t
[mailto:[EMAIL PROTECTED] Sent: Tuesday, May 30, 2006
10:57 AMTo: Brock, Anthony - NETCc:
user-mode-linux-user@lists.sourceforge.netSubject: Re: [uml-user]
Problems in sharing filesystems between Virtual Machines
But I am facing another problem. I have created the COW file and UML
But I am facing another problem. I have created the COW file and UML boots properly. But now when I boot another UML instance from the COW file I get the followimg error: It shows file is already locked by pid ...
#include <[EMAIL PROTECTED] um32-2.6.15-release-mod]$ ls -al
total 622708
drwxr-
Hi,
I am now able to create a COW filesystem through uml_mkcow utility and then booting the UML with ubd0=root_fs.cow successfully.
Thanks,
Pranjal
On 5/30/06, Brock, Anthony - NET <[EMAIL PROTECTED]> wrote:
Do you have write permissions to the current working directory? I don't k
Do you have write permissions to the current working
directory? I don't know what err=113 means, but the guest instance needs
permissions to create the file on the local file system.
Tony
From:
[EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
Pranjal Kumar DuttaSent