[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [Xen-users] 2 instances of a DomU on the same LV
On Mon, Mar 22, 2010 at 11:20 PM, Guy Roussin <guy.roussin@xxxxxxxxxxxxxxxx> wrote: > Hi, > > I'm a xen newbie and i try to configure xen (lenny), > > - Dom0 Boot On San (lenny 5.0.3 amd64) > - DomU LV on clvm (openais) > > LM08q:/var/vm/scripts# xm list > Name ID Mem VCPUs State > Time(s) > Domain-0 0 1024 8 r----- > 665.0 > xen-dmz-vm02 256 1 > 0.0 > xen-int-vm01 1 256 1 -b---- > 7.4 > xen-wif-vm03 256 1 > 0.0 > > LM09q:/etc/xen# xm list > Name ID Mem VCPUs State > Time(s) > Domain-0 0 1024 8 r----- > 1310.3 > xen-dmz-vm02 1 256 1 -b---- > 283.3 > xen-int-vm01 256 1 > 0.0 > xen-wif-vm03 3 256 1 -b---- > 2.0 > > if i try to 'xm create xen-int-vm01.cfg' on LM09q i get this error : > xm create xen-int-vm01.cfg > Using config file "./xen-int-vm01.cfg". > Error: VM name 'xen-int-vm01' already exists > > This is a good behavior i think. > > But, with virt-manager i can start xen-int-vm01 on LM09q > so thereis 2 instances of the DomU sharing the same LV !!! You misunderstood the commands. First the basics: xen does a basic sanity check to prevent more than a domU uses the same block device/file when it's set as writable, unless user specifically overides it. The check is only on the same dom0. Nothing is done to prevent the same device used on another dom0. You need some other kind of external mechanism to prevent that. Your original "xm create" command failed because the domU is already defined, but not started. You can start it with "xm start", which would produce the same result as starting it from virt-manager. -- Fajar _______________________________________________ Xen-users mailing list Xen-users@xxxxxxxxxxxxxxxxxxx http://lists.xensource.com/xen-users
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |