(the type was that the same Dom0 block device is used twice in the
first
example)
Which was working great until I did a 'mkswap /dev/hda2' inside the
domain, which really fscked things up :(
Given that there is almost no way you would ever want to publish the
same block device to the same virtual domain more than once, would
there
be any value in flagging that as an error when you try and start the
domain?
I'm surprised that the existing block device safety checks don't pick up
on this, but I guess they're run before the guest is started rather than
before each virtual disk is attached.
I certainly think there's a strong argument for protecting the user from
this kind of error, at least unless they've specified 'w!' and hence
indicated they want sharing.
Anyone care to knock up a patch?
Best,
Ian
9 messages in com.xensource.lists.xen-develRE: [Xen-devel] feature request - pre...