xen 4.0 testing - not check if disk is already in use by other domU on start

xen 4.0 testing - not check if disk is already in use by other domU on start

[Fantu]

I have xen 4.0-testing changeset: 21484 on testing system, if i start 2 domU
with different name but some file disk (with tap2:aio) start also the second
domU and disk have heavy problem, check of "if in use disk" missed? domU
start with xm create (i not try xl)

--
View this message in context: http://xen.1045712.n5.nabble.com/xen-4-0-testing-not-check-if-disk-is-already-in-use-by-other-domU-on-start-tp4409805p4409805.html
Sent from the Xen - Dev mailing list archive at Nabble.com.

Re: xen 4.0 testing - not check if disk is already in use by other domU on start

[Konrad Rzeszutek Wilk]

On Thu, May 19, 2011 at 07:07:50AM -0700, Fantu wrote:
> I have xen 4.0-testing changeset: 21484 on testing system, if i start 2 domU
> with different name but some file disk (with tap2:aio) start also the second
> domU and disk have heavy problem, check of "if in use disk" missed? domU
> start with xm create (i not try xl)

What if you have a cluster filesystem on both disks and it is OK
to share the disk?

Re: xen 4.0 testing - not check if disk is already in use by other domU on start

[Fantu]

Maybe i have posted the question in the wrong way.
For example i have

squeeze1.cfg
------------
name = "squeeze1"
...
disk  = ['tap2:aio:/mnt/vm/disks/squeeze1.disk1.xm,xvda1,w',
'tap2:aio:/mnt/vm/disks/squeeze1.disk2.xm,xvda2,w']
------------


squeeze2.cfg
------------
name = "squeeze2"
...
disk  = ['tap2:aio:/mnt/vm/disks/squeeze1.disk1.xm,xvda1,w',
'tap2:aio:/mnt/vm/disks/squeeze1.disk2.xm,xvda2,w']
------------

in squeeze2.cfg i forgot to change disk name from squeeze1 to squeeze2, and
then started the 2 domUs:
xm create squeeze1.cfg
xm create squeeze2.cfg

domU squeeze2 starts even if squeeze1 domU was already active and running on
the same disk file, logically i think that is wrong that there is no check,
maybe I'm wrong?

--
View this message in context: http://xen.1045712.n5.nabble.com/xen-4-0-testing-not-check-if-disk-is-already-in-use-by-other-domU-on-start-tp4409805p4411978.html
Sent from the Xen - Dev mailing list archive at Nabble.com.

Re: Re: xen 4.0 testing - not check if disk is already in use by other domU on start

[Konrad Rzeszutek Wilk]

On Fri, May 20, 2011 at 12:46:13AM -0700, Fantu wrote:
> Maybe i have posted the question in the wrong way.
> For example i have
> 
> squeeze1.cfg
> ------------
> name = "squeeze1"
> ...
> disk  = ['tap2:aio:/mnt/vm/disks/squeeze1.disk1.xm,xvda1,w',
> 'tap2:aio:/mnt/vm/disks/squeeze1.disk2.xm,xvda2,w']
> ------------
> 
> 
> squeeze2.cfg
> ------------
> name = "squeeze2"
> ...
> disk  = ['tap2:aio:/mnt/vm/disks/squeeze1.disk1.xm,xvda1,w',
> 'tap2:aio:/mnt/vm/disks/squeeze1.disk2.xm,xvda2,w']
> ------------
> 
> in squeeze2.cfg i forgot to change disk name from squeeze1 to squeeze2, and
> then started the 2 domUs:
> xm create squeeze1.cfg
> xm create squeeze2.cfg
> 
> domU squeeze2 starts even if squeeze1 domU was already active and running on
> the same disk file, logically i think that is wrong that there is no check,
> maybe I'm wrong?

Think of clusters of guests - where they share the same disk.