Jacob Ritorto wrote:
Oh, nice, thanks -- I had no idea this was possible. So is it going to be hvm
or
> pv?
You would start off with hvm... If it uses a nevada kernel, it should be
possible to convert it to a PV guest. I need to do a quick writeup
on how you do that one of these days...
Once 3.3 is putback, you should be able to use a e1000 NIC on a
xen HVM guest too (although I'm not sure how much this has
been tested).
I suppose I can vdiskadm this comms suite image to a zvol and point the
> Xen config file to it just like I did for the NetWare stuff (I'm stuck with
> using xm new and that ilk -- haven't even tried virt-install et al because
> NetWare requires a kernel parameter).
If you have xvm 3.3 or 3.4 development bits, yes, you can use
translate. Takes a while of course :-)
vdiskadm translate -I disk.vdi -x raw -d /dev/zvol/dsk/pool1/t1
-bash-3.2# vdiskadm help translate
translate - translate virtual disk data to a different type
USAGE:
vdiskadm translate [-i type[:opt]] -I input_file -x type[:opt] -d output_file
TYPES AND OPTIONS SUPPORTED
vmdk:sparse
vmdk:fixed
vdi:sparse
vdi:fixed
vhd:sparse
vhd:fixed
raw
EXAMPLE:
vdiskadm translate -I app.vmdk -x raw -d /dev/zvol/dsk/pool1/t1
-bash-3.2#
As to the whereabouts of the comms suite image, I actually just googled comms
suite and it found http://www.sun.com/software/communications_suite/get.jsp ,
which took me to the demo image download (unzip and concatenate to get your
vdi):
http://mediacast.sun.com/users/AnthonyWaldron/media/vbox_vm_part_1_of_5
http://mediacast.sun.com/users/AnthonyWaldron/media/vbox_vm_part_2_of_5
http://mediacast.sun.com/users/AnthonyWaldron/media/vbox_vm_part_3_of_5
http://mediacast.sun.com/users/AnthonyWaldron/media/vbox_vm_part_4_of_5
http://mediacast.sun.com/users/AnthonyWaldron/media/vbox_vm_part_5_of_5
Thanks.
MRJ
_______________________________________________
xen-discuss mailing list
[email protected]
