I''m attempting to run a domU, paravirtualized Solaris instance on
SLES10SP1.  When I boot, I get this:
--Begin Console Output--
SunOS Release 5.11 Version xen-nv66-2007-06-24 32-bit
Copyright 1983-2007 Sun Microsystems, Inc.  All rights reserved.
Use is subject to license terms.
WARNING: Found xen v3.0.4_13138-0.40 but need xen v3.0.4-1-sun
WARNING: The kernel may not function correctly
Configuring /dev
Solaris Interactive Text (Console session)
|
panic[cpu0]/thread=d4f9de00: BAD TRAP: type=0 (#de Divide error) rp=d4fd3b50
addr=0
fstyp: #de Divide error
pid=92, pc=0xf4c00eea, sp=0xd4fd3c04, eflags=0x10246
cr0: 8005003b<pg,wp,ne,et,ts,mp,pe> cr4: 640<xmme,fxsr,mce>
cr2: d32c6d34
         gs:      1b1  fs: f4c10000  es:      161  ds: f5020161
        edi:       48 esi:        0 ebp: d4fd3c40 esp: d4fd3b88
        ebx:        0 edx:        0 ecx:        0 eax:        0
        trp:        0 err:        0 eip: f4c00eea  cs:      159
        efl:    10246 usp: d4fd3c04  ss: d4fd3bd8
d4fd3a9c unix:die+ed (0, d4fd3b50, 0, 0)
d4fd3b3c unix:trap+10ae (d4fd3b50, 0, 0)
d4fd3b50 unix:cmntrap+aa (1b1, f4c10000, 161,)
d4fd3c40 unix:UDiv+2a (d5574580, 0)
d4fd3c8c cmlb:cmlb_validate_geometry+2cb (d5574580, 0, 0, 0)
d4fd3cb0 cmlb:cmlb_partinfo+4a (d5574580, 10, d4fd3)
d4fd3d0c xdf:xdf_prop_op+88 (3040050, d48e24d0, )
d4fd3d30 genunix:cdev_prop_op+36 (3040050, d48e24d0, )
d4fd3d84 specfs:spec_size+fb (d4fa0dd0)
d4fd3dd0 specfs:spec_open+468 (d4fd3ef0, 2001, db7)
d4fd3e0c genunix:fop_open+8c (d4fd3ef0, 2001, db7)
d4fd3efc genunix:vn_openat+449 (8047ec8, 0, 2001, e)
d4fd3f68 genunix:copen+288 (ffd19553, 8047ec8, )
d4fd3f84 genunix:open64+20 (8047ec8, 0, 8047e50)
syncing file systems... done
skipping system dump - no dump device configured
rebooting...
--End Console Output--
I know, I know - there''s the warning there about having the wrong
version of Xen, but I was hoping maybe someone had some workaround or success
story getting this type of setup going.
Thanks - Nick
 
 
This message posted from opensolaris.org
Nick wrote:> I''m attempting to run a domU, paravirtualized Solaris> instance on SLES10SP1. When I boot, I get this: This should work fine in theory.. How did you create the disk? Are you using a file backed disk? e.g. # dd if=/dev/zero of=disk.img bs=1024k seek=8k count=1 The disk line should look like... disk = [''file:/export/guests/solaris/disk.img,0,w''] or if your installing off of the iso, disk = [''file:/export/guests/install/solaris/66-0624-nd.iso,6:cdrom,r'', ''file:/export/guests/install/solaris/disk.img,0,w''] MRJ> --Begin Console Output-- > SunOS Release 5.11 Version xen-nv66-2007-06-24 32-bit > Copyright 1983-2007 Sun Microsystems, Inc. All rights reserved. > Use is subject to license terms. > WARNING: Found xen v3.0.4_13138-0.40 but need xen v3.0.4-1-sun > WARNING: The kernel may not function correctly > Configuring /dev > Solaris Interactive Text (Console session) > | > panic[cpu0]/thread=d4f9de00: BAD TRAP: type=0 (#de Divide error) rp=d4fd3b50 addr=0 > > fstyp: #de Divide error > pid=92, pc=0xf4c00eea, sp=0xd4fd3c04, eflags=0x10246 > cr0: 8005003b<pg,wp,ne,et,ts,mp,pe> cr4: 640<xmme,fxsr,mce> > cr2: d32c6d34 > gs: 1b1 fs: f4c10000 es: 161 ds: f5020161 > edi: 48 esi: 0 ebp: d4fd3c40 esp: d4fd3b88 > ebx: 0 edx: 0 ecx: 0 eax: 0 > trp: 0 err: 0 eip: f4c00eea cs: 159 > efl: 10246 usp: d4fd3c04 ss: d4fd3bd8 > > d4fd3a9c unix:die+ed (0, d4fd3b50, 0, 0) > d4fd3b3c unix:trap+10ae (d4fd3b50, 0, 0) > d4fd3b50 unix:cmntrap+aa (1b1, f4c10000, 161,) > d4fd3c40 unix:UDiv+2a (d5574580, 0) > d4fd3c8c cmlb:cmlb_validate_geometry+2cb (d5574580, 0, 0, 0) > d4fd3cb0 cmlb:cmlb_partinfo+4a (d5574580, 10, d4fd3) > d4fd3d0c xdf:xdf_prop_op+88 (3040050, d48e24d0, ) > d4fd3d30 genunix:cdev_prop_op+36 (3040050, d48e24d0, ) > d4fd3d84 specfs:spec_size+fb (d4fa0dd0) > d4fd3dd0 specfs:spec_open+468 (d4fd3ef0, 2001, db7) > d4fd3e0c genunix:fop_open+8c (d4fd3ef0, 2001, db7) > d4fd3efc genunix:vn_openat+449 (8047ec8, 0, 2001, e) > d4fd3f68 genunix:copen+288 (ffd19553, 8047ec8, ) > d4fd3f84 genunix:open64+20 (8047ec8, 0, 8047e50) > > syncing file systems... done > skipping system dump - no dump device configured > rebooting... > --End Console Output-- > > I know, I know - there''s the warning there about having the wrong version of Xen, but I was hoping maybe someone had some workaround or success story getting this type of setup going. > > Thanks - Nick > > > This message posted from opensolaris.org > _______________________________________________ > xen-discuss mailing list > xen-discuss@opensolaris.org-- Mark Johnson <mark.johnson@sun.com> Sun Microsystems, Inc. (781) 442-0869
I''m using an ISO image for install and a file-backed disk (COW/SPARSE) for the hard drive. I created the disk image with the qcow-create program: qcow-create 8192 /var/lib/xen/images/Turing/disk0 The ISO file I downloaded from OpenSolaris.org. Here''s the configuration file for the domU instance: name = ''Turing'' memory = ''256'' disk = [ ''file:/root/66-0624-nd.iso,6:cdrom,r'', ''file:/var/lib/xen/images/Turing/disk0,0,w'' ] vif = [ '''' ] kernel = ''/var/lib/xen/images/Turing/unix'' ramdisk = ''/var/lib/xen/images/Turing/x86.miniroot'' This message posted from opensolaris.org
Nick wrote:> I''m using an ISO image for install and a> file-backed disk (COW/SPARSE) for the hard drive. > I created the disk image with the qcow-create program:> qcow-create 8192 /var/lib/xen/images/Turing/disk0 > > The ISO file I downloaded from OpenSolaris.org. Here''s the configuration file for the domU instance: > > name = ''Turing'' > memory = ''256'' > disk = [ ''file:/root/66-0624-nd.iso,6:cdrom,r'', ''file:/var/lib/xen/images/Turing/disk0,0,w'' ] > vif = [ '''' ] > kernel = ''/var/lib/xen/images/Turing/unix'' > ramdisk = ''/var/lib/xen/images/Turing/x86.miniroot''Can you try two different things... Can you knock the memory up to 1G for the install. You can move it back down to 256M after the install has completed. Also, can you try to create a straight file back disk with dd. I would expect that if you were doing a COW/SPARCE, you would be using blktap? Since this is a PV domain, qcow-create is probably making a disk image that Solaris doesn''t like.. MRJ -- Mark Johnson <mark.johnson@sun.com> Sun Microsystems, Inc. (781) 442-0869