On Wed, Sep 12, 2007 at 03:40:49AM +0100, John Levon wrote:
On Wed, Sep 12, 2007 at 03:08:32AM +0100, Daniel P. Berrange wrote:
> We definitely need to support 32-bit tools on 64-bit HV
Thanks. Mark Johnson pointed out that we get away with a 32-bit
virt-install right now simply because the hypercall libvirt backend
fails, and falls back to calling into xend. In general this works well,
but seems to have at least one issue that means we might need to create
a 64-bit virt-{install,manager} ...
That's odd - to be able to run a 32-bit userspace on 64-bit HV you must
be running a Xen 3.1 release or later. If using that, then libvirt should
have automatically detected the hypervisor ABI which is 32/64 invariant.
ie it ought to be working ! Your problem could be a compatability issue
between the Solaris & Linux Xen ABIs which we're getting wrong.
You really want to be letting libvirt use the HV because for calls such
as listing guests, getting domain stats we get x100 to x1000 lower overheads
from talking to the HV instead of XenD. Talking to XenD you'll quickly see
XenD and XenStoreD start to take up considerable CPU time in Dom0 with even
a few guests being monitored by virt-manager.
Dan.
--
|=- Red Hat, Engineering, Emerging Technologies, Boston. +1 978 392 2496 -=|
|=- Perl modules:
http://search.cpan.org/~danberr/ -=|
|=- Projects:
http://freshmeat.net/~danielpb/ -=|
|=- GnuPG: 7D3B9505 F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 -=|