Fajar A. Nugraha wrote:
> On Thu, Feb 5, 2009 at 7:24 PM, Mark Johnson <[email protected]> wrote:
>>> I agree with you on some of them. Still, I wished we've reached the
>>> point where moving domUs between Linux <-> Opensolaris dom0 is a
>>> simple matter matter of copying data and config files.
>> You can do that today.. What problems do you have
>> moving a guest between a linux dom0 and a solaris
>> dom0?
>
> Most of them can be modified to work correctly, like :
> - clock issue (Linux use UTC on hwclock by default, while solaris uses
> local time. Can be fixed).
Yeah. Either of these can be changed...
For Solaris,
man rtc
which will change /etc/rtc_config
> - I can't use vncunused=0 (then again I have problem using this on
> Xen-3.3.1/Linux)
Oh, what happens? (We have a bunch of qemu unstable
patches backported in our 3.1.4 which probably
explains why it behaves the same as what you see in 3.3.1)
> - different bootloader location. /usr/bin/pygrub vs
> /usr/lib/xen/bin/pygrub (again, simple workaround)
Yeah, this is a problem.. Hardcoding the path in
the domain config is broken... It should really
just be pygrub, etc. But I don't expect anyone
to fix this anytime soon on Solaris or Linux.
It should be a pretty easy fix if anyone wants to
contribute it though.
> - serial='pty' does not work on HVM guest on opensolaris
This was fixed somewhat recently... On solaris, it's:
(serial pty)
>> Migration "should" work too, but we don't test it.
>
> That would be hard, since migration requires :
> - same network setup (how can we set the same bridge setup on Linux
> and opensolaris?)
On solaris, you can rename the NICs to match the
bridges on the linux side.. This also requires a
somewhat new version of OpenSolaris.
i.e.
dladm rename-link
We have a bunch of new NIC stuff coming
in relatively soon. Rate limiting, vlan,
support..
NATs should work now too, but as of today it requires
manual setup on dom0. I haven't played with it to
see how/if it works yet.
> - same disk setup (using /dev/sda or /dev/disk/by-id obviously won't
> work on solaris, even when it's iscsi-imported disk).
This is where the real problem is... When I did
a migration between Solaris and Fedora (a while ago)
I used file:/.../. So it does work... But you wouldn't
use file:/ in a real setup for performance reasons.
We've diverged quite a bit here unfortunately. XenSource
did a closed source fork in this area and the current
stuff upstream wasn't close to what we needed.
so we have file:/... and phy:/.... But for tap, we
have a different implementation which is tap:vdisk:
and supports vmdk, vdi (virtual box disk), and soon
vhd. It also supports snapshots, rollbacks, clones, etc
for each (man vdiskadm). It's all opensource, but
unlikely to be adopted upstream.
coming soon we will also have (format subject to change)
phy:iscsi:alias/<iscsi-alias>
phy:iscsi:static/<server IP>/<lun>/<target id>
phy:iscsi:discover/<lun>/<alias or target id>
e.g.
disk = ['phy:iscsi:alias/serv01-iscsi/winxp05-disk0,0,w']
disk =
['phy:iscsi:static/192.168.0.70/0/iqn.1986-03.com.sun:02:17f34578-00a9-ef69-f3e9-b8a2896a4915,0,w']
and something like...
phy:san:guid/<lun>/<guid>/
I'm not sure what linux dmo0s have in these areas these days?
> - same Xen version (is this required?)
They would have to be close.. i.e. both 3.3.x..
MRJ
_______________________________________________
xen-discuss mailing list
[email protected]
