Just thought I''d give the people on the list who maybe interested a
pointer as to how I managed to install an opensolaris domU (latest
drop) under a Linux dom0 (Ubuntu Feisty to be exact)...
The instructions in the community documentation here doesn''t include a
kernel or a ramdisk specification, so my Linux dom0''s tools
didn''t
care for it. To get around this, I loop mounted the DVD image, and
took:
cp /media/cdrom/boot/platform/i86xpv/kernel/unix
/etc/xen/kernel/OpenSolaris-07-07.kernel
cp /media/cdrom/boot/x86.miniroot /etc/xen/kernel/OpenSolaris-07-07.miniroot
Then used the following xen python config (as /etc/xen/configs/opensol.cfg)
name = "opensol"
memory = "300"
kernel = ''/etc/xen/kernel/OpenSol-07-07.kernel''
ramdisk = "/etc/xen/kernel/OpenSol-07-07.miniroot"
extra = ''/platform/i86xpv/kernel/unix - nowin -B
install_media=cdrom''
on_shutdown = "destroy"
on_reboot = "destroy"
on_crash = "destroy"
disk =
[''file:/opt/iso/OS/OpenSolaris/66-0624-nd.iso,6:cdrom,r'',
''phy:optData/xen-opensol-c0t0d0,0,w'']
vif = [''bridge=xenbr0'']
This seems to have worked (so far, it''s busily installing packages
right now). I expect to have the same kind of issues with the
boot_archive not getting propagated back to the dom0, causing it not
to be read as the ramdisk, but I''ll manage to get around that.
It would be beneficial if the kernels (both for x86 and amd64) and the
initial ramdisk image could be extracted from the ISO and put onto the
Sun Downloads page with the ISO image chunks. This would definitely
help any who choose to attempt to run an OpenSolaris domU under a
Linux (or maybe even NetBSD) dom0.
Thanks for the good work, and for the useful support on IRC.
Note: I''m not yet sure if my networking will work, or if I need to
twiddle that. That vif setting works for all my Linux domUs so I used
it as a starting place. I think it worked with the b44 drop too.
On Sun, 2007-07-22 at 15:39 -0400, Gavin Hurlbut wrote:> vif = [''bridge=xenbr0''] > ... > Note: I''m not yet sure if my networking will work, or if I need to > twiddle that. That vif setting works for all my Linux domUs so I used > it as a starting place. I think it worked with the b44 drop too.It should work just fine. dme.
Well, with David''s help (on IRC), I added to /etc/system: set xnf:xnf_cksum_offload = 0 then did bootadm update-archive, rebooted, and all seems to work. It turns out that the checksum offloading didn''t work well on my setup, chance why... I suspect that the sis900 ethernet driver being used on the Linux dom0 side doesn''t support checksum offloading all that well. The symptoms were: I could see traffic coming from the OpenSolaris domU into the bridge on the dom0 with no checksums, and then the traffic leaving the bridge on the dom0 with bad checksums. This, of course, should not happen. With the workaround above, the traffic from the domU has correct checksums in it (rather than expecting hardware elsewhere to insert it) and all is well... At the cost of CPU time, but as a workaround, that''s acceptable to me. If I can be of any help to try to track down the actual problem, let me know. Gavin (Beirdo on IRC) On 7/23/07, David Edmondson <dme@sun.com> wrote:> On Sun, 2007-07-22 at 15:39 -0400, Gavin Hurlbut wrote: > > vif = [''bridge=xenbr0''] > > ... > > Note: I''m not yet sure if my networking will work, or if I need to > > twiddle that. That vif setting works for all my Linux domUs so I used > > it as a starting place. I think it worked with the b44 drop too. > > It should work just fine. > > dme. > > >
Gavin,>>Well, with David''s help (on IRC), I added to /etc/system: >> >>set xnf:xnf_cksum_offload = 0 >> >>then did bootadm update-archive, rebooted, and all seems to work.Good hint. But there''s one important step missing : After the "bootadm update-archive" is finished copy the new boot_archive to the Dom0. At least in my configuration I had to do this (Solaris 10 DomU under Ubuntu Feisty Dom0). And my config file to boot the installed Solaris 10 DomU is: name = "solaris_10_July_07" memory = "368" vcpus = "1" disk = [ ''file:/data/cdtemp/sol10_xen.iso,6:cdrom,r'',''file:/test/Solaris10_xen0707.raw,0,w'' ] vif = [ '''' ] on_shutdown = ''destroy'' on_reboot = ''restart'' on_crash = ''destroy'' kernel = "/test/Solaris10_xen0707.kernel" ramdisk = "/test/boot_archive" rootdisk = "/dev/dsk/c0d0s0" extra = ''/platform/i86xpv/kernel/unix -B bootpath=/xpvd/xdf@0:a'' I think the -B parameter is not necessary with the updated boot_archive but I did not test this ... @David: I suggest there should be a short cookbook for using a Solaris DomU under a Linux Dom0 Without it it''s a little difficult for someone not knowing Solaris to create a DomU for running under a Linux Dom0. regards Bernd This message posted from opensolaris.org
Gavin,>>Well, with David''s help (on IRC), I added to /etc/system: >> >>set xnf:xnf_cksum_offload = 0 >> >>then did bootadm update-archive, rebooted, and all seems to work.Good hint. But there''s one important step missing : After the "bootadm update-archive" is finished copy the new boot_archive to the Dom0. At least in my configuration I had to do this (Solaris 10 DomU under Ubuntu Feisty Dom0). And my config file to boot the installed Solaris 10 DomU is: name = "solaris_10_July_07" memory = "368" vcpus = "1" disk = [ ''file:/data/cdtemp/sol10_xen.iso,6:cdrom,r'',''file:/test/Solaris10_xen0707.raw,0,w'' ] vif = [ '''' ] on_shutdown = ''destroy'' on_reboot = ''restart'' on_crash = ''destroy'' kernel = "/test/Solaris10_xen0707.kernel" ramdisk = "/test/boot_archive" rootdisk = "/dev/dsk/c0d0s0" extra = ''/platform/i86xpv/kernel/unix -B bootpath=/xpvd/xdf@0:a'' I think the -B parameter is not necessary with the updated boot_archive but I did not test this ... @David: I suggest there should be a short cookbook for using a Solaris DomU under a Linux Dom0 Without it it''s a little difficult for someone not knowing Solaris to create a DomU for running under a Linux Dom0. regards Bernd This message posted from opensolaris.org