How do you setup Solaris to run on a linux dom0? Is there a Solaris
builder function?
I copied the files (boot_archive mydomU.py root.file unix)
from Solaris to my linux domU and gave xm create a whirl to see what
would happen.
xend-debug.log says:
ERROR: Initial guest OS requires too much space
(1748MB is greater than 400MB limit)
(0 = Success)
ERROR: Error constructing guest OS
xm crate itself said:
# xm create -f mydomU.py
Using config file "mydomU.py".
Error: (9, ''Bad file descriptor'')
The xend.log recorded all this:
[2006-08-21 12:51:30 xend.XendDomainInfo] DEBUG (XendDomainInfo:178) XendDomainI
nfo.create([''vm'', [''name'',
''mydomU''], [''memory'',
''400''], [''on_reboot'',
''restart''
], [''on_crash'', ''destroy''],
[''vcpus'', 1], [''image'',
[''linux'', [''kernel'', ''/vol/l
ocal/solaris/unix''], [''ramdisk'',
''/vol/local/solaris/boot_archive''], [''root'',
''/
dev/dsk/c0d0s0''], [''args'',
''/platform/i86xen/kernel/unix'']]],
[''device'', [''vbd'',
[''uname'',
''file:/vol/local/solaris/root.file''],
[''dev'', ''0''], [''mode'',
''w'']]],
[''device'', [''vif'',
[''bridge'', ''xenbr0''],
[''mac'', ''aa:00:ac:10:0c:09'']]]])
[2006-08-21 12:51:30 xend.XendDomainInfo] DEBUG (XendDomainInfo:284) parseConfig
: config is [''vm'', [''name'',
''mydomU''], [''memory'',
''400''], [''on_reboot'', ''restart
''], [''on_crash'', ''destroy''],
[''vcpus'', 1], [''image'',
[''linux'', [''kernel'', ''/vol/
local/solaris/unix''], [''ramdisk'',
''/vol/local/solaris/boot_archive''], [''root'',
''
/dev/dsk/c0d0s0''], [''args'',
''/platform/i86xen/kernel/unix'']]],
[''device'', [''vbd''
, [''uname'',
''file:/vol/local/solaris/root.file''],
[''dev'', ''0''], [''mode'',
''w'']]],
[''device'', [''vif'',
[''bridge'', ''xenbr0''],
[''mac'', ''aa:00:ac:10:0c:09'']]]]
[2006-08-21 12:51:30 xend.XendDomainInfo] DEBUG (XendDomainInfo:380) parseConfig
: result is {''ssidref'': None, ''uuid'': None,
''on_crash'': ''destroy'',
''on_reboot'':
''restart'', ''image'':
[''linux'', [''kernel'',
''/vol/local/solaris/unix''], [''ramdisk'',
''/vol/local/solaris/boot_archive''],
[''root'', ''/dev/dsk/c0d0s0''],
[''args'', ''/pla
tform/i86xen/kernel/unix'']], ''on_poweroff'': None,
''cpus'': None, ''name'':
''mydomU''
, ''backend'': [], ''vcpus'': 1,
''cpu_weight'': None, ''vcpu_avail'': None,
''memory'': 4
00, ''device'': [(''vbd'',
[''vbd'', [''uname'',
''file:/vol/local/solaris/root.file''], [
''dev'', ''0''], [''mode'',
''w'']]), (''vif'', [''vif'',
[''bridge'', ''xenbr0''],
[''mac'', ''aa:
00:ac:10:0c:09'']])], ''bootloader'': None,
''cpu'': None, ''maxmem'': None}
[2006-08-21 12:51:30 xend.XendDomainInfo] DEBUG (XendDomainInfo:1164) XendDomain
Info.construct: None 0
[2006-08-21 12:51:30 xend.XendDomainInfo] DEBUG (XendDomainInfo:1198) XendDomain
Info.initDomain: 3 1.0 maxmem 400 memory 400
[2006-08-21 12:51:30 xend] DEBUG (balloon:128) Balloon: free 1971; need 401; don
e.
[2006-08-21 12:51:30 xend] INFO (image:135) buildDomain os=linux dom=3 vcpus=1
[2006-08-21 12:51:30 xend] DEBUG (image:173) dom = 3
[2006-08-21 12:51:30 xend] DEBUG (image:174) image = /vol/local/solaris
/unix
[2006-08-21 12:51:30 xend] DEBUG (image:175) store_evtchn = 1
[2006-08-21 12:51:30 xend] DEBUG (image:176) console_evtchn = 2
[2006-08-21 12:51:30 xend] DEBUG (image:177) cmdline = root=/dev/dsk/c0d
0s0 /platform/i86xen/kernel/unix
[2006-08-21 12:51:30 xend] DEBUG (image:178) ramdisk = /vol/local/solaris
/boot_archive
[2006-08-21 12:51:30 xend] DEBUG (image:179) vcpus = 1
[2006-08-21 12:51:30 xend] DEBUG (image:180) features =
[2006-08-21 12:51:30 xend.XendDomainInfo] ERROR (XendDomainInfo:190) Domain cons
truction failed
Traceback (most recent call last):
File "/usr/lib/python2.3/xen/xend/XendDomainInfo.py", line 183, in
create
vm.initDomain()
File "/usr/lib/python2.3/xen/xend/XendDomainInfo.py", line 1227, in
initDomain
channel_details = self.image.createImage()
File "/usr/lib/python2.3/xen/xend/image.py", line 118, in
createImage
return self.createDomain()
File "/usr/lib/python2.3/xen/xend/image.py", line 137, in
createDomain
result = self.buildDomain()
File "/usr/lib/python2.3/xen/xend/image.py", line 188, in
buildDomain
features = self.features)
error: (9, ''Bad file descriptor'')
[2006-08-21 12:51:30 xend.XendDomainInfo] DEBUG (XendDomainInfo:1329) XendDomain
Info.destroy: domid=3
[2006-08-21 12:51:30 xend.XendDomainInfo] DEBUG (XendDomainInfo:1337) XendDomain
Info.destroyDomain(3)
[2006-08-21 12:51:30 xend] ERROR (xmlrpclib2:124) (9, ''Bad file
descriptor'')
Traceback (most recent call last):
File "/usr/lib/python2.3/xen/util/xmlrpclib2.py", line 103, in
_marshaled_disp
atch
response = self._dispatch(method, params)
File "/usr/lib/python2.3/SimpleXMLRPCServer.py", line 407, in
_dispatch
return func(*params)
File "/usr/lib/python2.3/xen/xend/server/XMLRPCServer.py", line 63,
in domain_
create
info = XendDomain.instance().domain_create(config)
File "/usr/lib/python2.3/xen/xend/XendDomain.py", line 227, in
domain_create
dominfo = XendDomainInfo.create(config)
File "/usr/lib/python2.3/xen/xend/XendDomainInfo.py", line 183, in
create
vm.initDomain()
File "/usr/lib/python2.3/xen/xend/XendDomainInfo.py", line 1227, in
initDomain
channel_details = self.image.createImage()
File "/usr/lib/python2.3/xen/xend/image.py", line 118, in
createImage
return self.createDomain()
File "/usr/lib/python2.3/xen/xend/image.py", line 137, in
createDomain
result = self.buildDomain()
File "/usr/lib/python2.3/xen/xend/image.py", line 188, in
buildDomain
features = self.features)
error: (9, ''Bad file descriptor'')
xm info from linux dom0 says:
# xm info
host : sur84-xen
release : 2.6.16.13-xen0
version : #2 Thu Jul 6 12:57:36 EDT 2006
machine : i686
nr_cpus : 4
nr_nodes : 1
sockets_per_node : 2
cores_per_socket : 1
threads_per_core : 2
cpu_mhz : 2790
hw_caps : bfebfbff:00000000:00000000:00000080:00004400
total_memory : 2048
free_memory : 1971
xen_major : 3
xen_minor : 0
xen_extra : .2-3
xen_caps : xen-3.0-x86_32
platform_params : virt_start=0xfc000000
xen_changeset : Thu Jun 29 05:51:49 2006
9762:1e225598ce827a8d810ad57e82547ad6e
cc_compiler : gcc version 3.3.5 (Debian 1:3.3.5-13)
cc_compile_by : becker
cc_compile_domain :
cc_compile_date : Fri Jun 30 15:36:33 EDT 2006
David Becker wrote:> How do you setup Solaris to run on a linux dom0? Is there a Solaris > builder function? > > I copied the files (boot_archive mydomU.py root.file unix) > from Solaris to my linux domU and gave xm create a whirl to see what > would happen.I''m assuming these were setup from vbdcfg? Did you run this domU on a solaris dom0 without any problems? i.e. http://www.opensolaris.org/os/community/xen/How-To-07-2006/Solaris-domU/> xend-debug.log says: > ERROR: Initial guest OS requires too much space > (1748MB is greater than 400MB limit) > (0 = Success) > ERROR: Error constructing guest OS > > xm crate itself said: > # xm create -f mydomU.py > Using config file "mydomU.py". > Error: (9, ''Bad file descriptor'')Could you double check that these are valid.. Does the size of each file make sense? i.e. how big are the unix and boot_archive files? # ls -l /vol/local/solaris/unix # ls -l /vol/local/solaris/boot_archive # ls -l /vol/local/solaris/root.file The xend-debug.log is coming from setup_guest() in libxc. it basically saying the the memory required by the kernel (unix), the ramdisk (boot_archive), and some minor overhead pages are more than the memory you allocated for the domU. Off the top of my head, the only reason I could see that is if one of those files was wrong? MRJ> The xend.log recorded all this: > > [2006-08-21 12:51:30 xend.XendDomainInfo] DEBUG (XendDomainInfo:178) XendDomainI > nfo.create([''vm'', [''name'', ''mydomU''], [''memory'', ''400''], [''on_reboot'', ''restart'' > ], [''on_crash'', ''destroy''], [''vcpus'', 1], [''image'', [''linux'', [''kernel'', ''/vol/l > ocal/solaris/unix''], [''ramdisk'', ''/vol/local/solaris/boot_archive''], [''root'', ''/ > dev/dsk/c0d0s0''], [''args'', ''/platform/i86xen/kernel/unix'']]], [''device'', [''vbd'', > [''uname'', ''file:/vol/local/solaris/root.file''], [''dev'', ''0''], [''mode'', ''w'']]], > [''device'', [''vif'', [''bridge'', ''xenbr0''], [''mac'', ''aa:00:ac:10:0c:09'']]]]) > [2006-08-21 12:51:30 xend.XendDomainInfo] DEBUG (XendDomainInfo:284) parseConfig > : config is [''vm'', [''name'', ''mydomU''], [''memory'', ''400''], [''on_reboot'', ''restart > ''], [''on_crash'', ''destroy''], [''vcpus'', 1], [''image'', [''linux'', [''kernel'', ''/vol/ > local/solaris/unix''], [''ramdisk'', ''/vol/local/solaris/boot_archive''], [''root'', '' > /dev/dsk/c0d0s0''], [''args'', ''/platform/i86xen/kernel/unix'']]], [''device'', [''vbd'' > , [''uname'', ''file:/vol/local/solaris/root.file''], [''dev'', ''0''], [''mode'', ''w'']]], > [''device'', [''vif'', [''bridge'', ''xenbr0''], [''mac'', ''aa:00:ac:10:0c:09'']]]] > [2006-08-21 12:51:30 xend.XendDomainInfo] DEBUG (XendDomainInfo:380) parseConfig > : result is {''ssidref'': None, ''uuid'': None, ''on_crash'': ''destroy'', ''on_reboot'': > ''restart'', ''image'': [''linux'', [''kernel'', ''/vol/local/solaris/unix''], [''ramdisk'', > ''/vol/local/solaris/boot_archive''], [''root'', ''/dev/dsk/c0d0s0''], [''args'', ''/pla > tform/i86xen/kernel/unix'']], ''on_poweroff'': None, ''cpus'': None, ''name'': ''mydomU'' > , ''backend'': [], ''vcpus'': 1, ''cpu_weight'': None, ''vcpu_avail'': None, ''memory'': 4 > 00, ''device'': [(''vbd'', [''vbd'', [''uname'', ''file:/vol/local/solaris/root.file''], [ > ''dev'', ''0''], [''mode'', ''w'']]), (''vif'', [''vif'', [''bridge'', ''xenbr0''], [''mac'', ''aa: > 00:ac:10:0c:09'']])], ''bootloader'': None, ''cpu'': None, ''maxmem'': None} > [2006-08-21 12:51:30 xend.XendDomainInfo] DEBUG (XendDomainInfo:1164) XendDomain > Info.construct: None 0 > [2006-08-21 12:51:30 xend.XendDomainInfo] DEBUG (XendDomainInfo:1198) XendDomain > Info.initDomain: 3 1.0 maxmem 400 memory 400 > [2006-08-21 12:51:30 xend] DEBUG (balloon:128) Balloon: free 1971; need 401; don > e. > [2006-08-21 12:51:30 xend] INFO (image:135) buildDomain os=linux dom=3 vcpus=1 > [2006-08-21 12:51:30 xend] DEBUG (image:173) dom = 3 > [2006-08-21 12:51:30 xend] DEBUG (image:174) image = /vol/local/solaris > /unix > [2006-08-21 12:51:30 xend] DEBUG (image:175) store_evtchn = 1 > [2006-08-21 12:51:30 xend] DEBUG (image:176) console_evtchn = 2 > [2006-08-21 12:51:30 xend] DEBUG (image:177) cmdline = root=/dev/dsk/c0d > 0s0 /platform/i86xen/kernel/unix > [2006-08-21 12:51:30 xend] DEBUG (image:178) ramdisk = /vol/local/solaris > /boot_archive > [2006-08-21 12:51:30 xend] DEBUG (image:179) vcpus = 1 > [2006-08-21 12:51:30 xend] DEBUG (image:180) features = > [2006-08-21 12:51:30 xend.XendDomainInfo] ERROR (XendDomainInfo:190) Domain cons > truction failed > Traceback (most recent call last): > File "/usr/lib/python2.3/xen/xend/XendDomainInfo.py", line 183, in create > vm.initDomain() > File "/usr/lib/python2.3/xen/xend/XendDomainInfo.py", line 1227, in initDomain > channel_details = self.image.createImage() > File "/usr/lib/python2.3/xen/xend/image.py", line 118, in createImage > return self.createDomain() > File "/usr/lib/python2.3/xen/xend/image.py", line 137, in createDomain > result = self.buildDomain() > File "/usr/lib/python2.3/xen/xend/image.py", line 188, in buildDomain > features = self.features) > error: (9, ''Bad file descriptor'') > [2006-08-21 12:51:30 xend.XendDomainInfo] DEBUG (XendDomainInfo:1329) XendDomain > Info.destroy: domid=3 > [2006-08-21 12:51:30 xend.XendDomainInfo] DEBUG (XendDomainInfo:1337) XendDomain > Info.destroyDomain(3) > [2006-08-21 12:51:30 xend] ERROR (xmlrpclib2:124) (9, ''Bad file descriptor'') > Traceback (most recent call last): > File "/usr/lib/python2.3/xen/util/xmlrpclib2.py", line 103, in _marshaled_disp > atch > response = self._dispatch(method, params) > File "/usr/lib/python2.3/SimpleXMLRPCServer.py", line 407, in _dispatch > return func(*params) > File "/usr/lib/python2.3/xen/xend/server/XMLRPCServer.py", line 63, in domain_ > create > info = XendDomain.instance().domain_create(config) > File "/usr/lib/python2.3/xen/xend/XendDomain.py", line 227, in domain_create > dominfo = XendDomainInfo.create(config) > File "/usr/lib/python2.3/xen/xend/XendDomainInfo.py", line 183, in create > vm.initDomain() > File "/usr/lib/python2.3/xen/xend/XendDomainInfo.py", line 1227, in initDomain > channel_details = self.image.createImage() > File "/usr/lib/python2.3/xen/xend/image.py", line 118, in createImage > return self.createDomain() > File "/usr/lib/python2.3/xen/xend/image.py", line 137, in createDomain > result = self.buildDomain() > File "/usr/lib/python2.3/xen/xend/image.py", line 188, in buildDomain > features = self.features) > error: (9, ''Bad file descriptor'') > > > > xm info from linux dom0 says: > # xm info > host : sur84-xen > release : 2.6.16.13-xen0 > version : #2 Thu Jul 6 12:57:36 EDT 2006 > machine : i686 > nr_cpus : 4 > nr_nodes : 1 > sockets_per_node : 2 > cores_per_socket : 1 > threads_per_core : 2 > cpu_mhz : 2790 > hw_caps : bfebfbff:00000000:00000000:00000080:00004400 > total_memory : 2048 > free_memory : 1971 > xen_major : 3 > xen_minor : 0 > xen_extra : .2-3 > xen_caps : xen-3.0-x86_32 > platform_params : virt_start=0xfc000000 > xen_changeset : Thu Jun 29 05:51:49 2006 9762:1e225598ce827a8d810ad57e82547ad6e > cc_compiler : gcc version 3.3.5 (Debian 1:3.3.5-13) > cc_compile_by : becker > cc_compile_domain : > cc_compile_date : Fri Jun 30 15:36:33 EDT 2006 > > _______________________________________________ > xen-discuss mailing list > xen-discuss@opensolaris.org
" I''m assuming these were setup from vbdcfg? Did you
" run this domU on a solaris dom0 without any problems?
Yes I created the files using the vbdcfg instructions from the domU
instruction page. But, no, I do not have a Solaris dom0 handy to test
the results.
" Could you double check that these are valid.. Does
" the size of each file make sense? i.e. how big
" are the unix and boot_archive files?
Here are the sizes. They seem reasonable to my eye
# ls -l
total 6796780
-rw-r--r-- 1 root root 23756800 Aug 18 16:44 boot_archive
-rw-r--r-- 1 root root 337 Aug 21 13:18 mydomU.py
-rw-r--r-- 1 root root 6928037888 Aug 18 16:44 root.file
-rwxr-xr-x 1 root root 1288396 Aug 18 16:44 unix
" Off the top of my head, the only reason I could see that is if
" one of those files was wrong?
xend would be using the Linux builder function presumably. Is that ok
or is there a solaris builder?
David Becker wrote:> " I''m assuming these were setup from vbdcfg? Did you > " run this domU on a solaris dom0 without any problems? > > Yes I created the files using the vbdcfg instructions from the domU > instruction page. But, no, I do not have a Solaris dom0 handy to test > the results. > > > " Could you double check that these are valid.. Does > " the size of each file make sense? i.e. how big > " are the unix and boot_archive files? > > Here are the sizes. They seem reasonable to my eye > # ls -l > total 6796780 > -rw-r--r-- 1 root root 23756800 Aug 18 16:44 boot_archive > -rw-r--r-- 1 root root 337 Aug 21 13:18 mydomU.py > -rw-r--r-- 1 root root 6928037888 Aug 18 16:44 root.file > -rwxr-xr-x 1 root root 1288396 Aug 18 16:44 unixYeah, those look to be in the right range.> " Off the top of my head, the only reason I could see that is if > " one of those files was wrong? > > xend would be using the Linux builder function presumably. Is that ok > or is there a solaris builder?We use the linux builder code. I don''t think we modified that at all for solaris domUs. There are some minor changes for solaris dom0. We do specify the disk differently by passing the disk number in after the disk file.. e.g. usually we specify disk 0, but if you wanted to use disk 5, it would be: disk = [''file:/export/xc/xvm/disks/solaris-b44.img,5,w''] root = "/dev/dsk/c0d5s0" vs linux using sda1, etc. That shouldn''t be a problem? But maybe it is with the xen code drop you have? Do you know what you have for Xen. It looked like maybe it was 3.0.2-3 from your previous e-mail? Are you running unstable or a release? We''ll do a quick test to make sure it still works on our side (right now, most of our linux dom0 testing is with diskless solaris domU clients). We should have an updated release out soon and hopefully it will include a ready-to-run Solaris domU disk image. If we can''t reproduce the problem on our end, maybe that will help us narrow it down.. MRJ
Mark Johnson wrote:> We''ll do a quick test to make sure it still works on our side > (right now, most of our linux dom0 testing is with diskless > solaris domU clients). > > We should have an updated release out soon and hopefully it > will include a ready-to-run Solaris domU disk image. If we can''t > reproduce the problem on our end, maybe that will help us > narrow it down..I just tested these solaris domU bits on a centos 4.2 dom0 running the stock 3.0.2-2 xen source bits. Booted up fine. So it''s either something different with the xen bits you have or with the solaris domU bits that you have. MRJ
" So it''s either something different with the xen bits
" you have or with the solaris domU bits that you have.
It was the the domU bits. Recreating boot_archive resulted in a larger
file that worked fine. The new size:
-rw-r--r-- 1 root root 33145701 Aug 22 09:10 boot_archive
That file was recreated with
solaris# touch /platform/i86xen/kernel/unix
solaris# bootadm update-archive
With the new boot_archive, the solaris domU solaris kernel boots up.
Next hurdle is the root device. The linux xend throws an exception
trying to create a vbd disk named 0.
[2006-08-22 09:13:08 xend] DEBUG (blkif:24) exception looking up device
number for 0: [Errno 2] No such file or directory: ''/dev/0''
The disk spec was
disk = [''file:/vol/local/solaris/root.file,0,w'']
If I change the disk specification to
disk = [''file:/vol/local/solaris/root.file,sda,w'']
the exception goes away, but domU solaris gives the same panic message
for both disk specs:
linuxdom0# xm create -c mydomU.py
Using config file "mydomU.py".
Started domain mydomU
SunOS Release 5.11 Version matrix-build-2006-07-14 32-bit
Copyright 1983-2006 Sun Microsystems, Inc. All rights reserved.
Use is subject to license terms.
DEBUG enabled
WARNING: Found xen v3.0.2-3 but need xen v3.0.2-sun
WARNING: The kernel may not function correctly
panic[cpu0]/thread=fb828380: cannot mount root path
/pci@0,0/pci1022,7450@2/pci1000,3060@3/sd@0,0:a
fb83f77c genunix:rootconf+fa (0, 1, fb827b10, 0, )
fb83f7a0 genunix:vfs_mountroot+54 (fb400010, fb83d638,)
fb83f7c0 genunix:main+e4 ()
skipping system dump - no dump device configured
rebooting...
When renaming the vbd disk to sda instead of 0, booting domU results in the
same panic message:
panic[cpu0]/thread=fb828380: cannot mount root path
/pci@0,0/pci1022,7450@2/pci1000,3060@3/sd@0,0:a
fb83f77c genunix:rootconf+fa (0, 1, fb827b10, 0, )
fb83f7a0 genunix:vfs_mountroot+54 (fb400010, fb83d638,)
fb83f7c0 genunix:main+e4 ()
skipping system dump - no dump device configured
# cat mydomU.py
name = "mydomU"
memory = "400"
kernel = "/vol/local/solaris/unix"
extra = "/platform/i86xen/kernel/unix"
ramdisk = "/vol/local/solaris/boot_archive"
on_shutdown = "destroy"
on_reboot = "restart"
on_crash = "destroy"
root = "/dev/dsk/c0d0s0"
# disk = [''file:/vol/local/solaris/root.file,0,w'']
disk = [''file:/vol/local/solaris/root.file,sda,w'']
vif = [''mac=aa:00:ac:10:0c:09, bridge=xenbr0'']
David Becker wrote:> " So it''s either something different with the xen bits > " you have or with the solaris domU bits that you have. > > It was the the domU bits. Recreating boot_archive resulted in a larger > file that worked fine. The new size: > -rw-r--r-- 1 root root 33145701 Aug 22 09:10 boot_archive > That file was recreated with > solaris# touch /platform/i86xen/kernel/unix > solaris# bootadm update-archive > With the new boot_archive, the solaris domU solaris kernel boots up.Great.> > Next hurdle is the root device. The linux xend throws an exception > trying to create a vbd disk named 0. > [2006-08-22 09:13:08 xend] DEBUG (blkif:24) exception looking up device > number for 0: [Errno 2] No such file or directory: ''/dev/0'' > The disk spec was > disk = [''file:/vol/local/solaris/root.file,0,w'']Yep, it does for us too, but keeps on going.. It''s something that needs to be cleaned up. [2006-08-18 13:52:44 xend] DEBUG (blkif:24) exception looking up device number f or 0: [Errno 2] No such file or directory: ''/dev/0'' [2006-08-18 13:52:44 xend] DEBUG (DevController:103) DevController: writing {''vi rtual-device'': ''0'', ''backend-id'': ''0'', ''state'': ''1'', ''backend'': ''/local/domain/0 /backend/vbd/4/0''} to /local/domain/4/device/vbd/0. ... What are you seeing when you do a xm create with it set to 0?> > If I change the disk specification to > disk = [''file:/vol/local/solaris/root.file,sda,w''] > the exception goes away, but domU solaris gives the same panic message > for both disk specs: > linuxdom0# xm create -c mydomU.py > Using config file "mydomU.py". > Started domain mydomU > SunOS Release 5.11 Version matrix-build-2006-07-14 32-bit > Copyright 1983-2006 Sun Microsystems, Inc. All rights reserved. > Use is subject to license terms. > DEBUG enabled > WARNING: Found xen v3.0.2-3 but need xen v3.0.2-sun > WARNING: The kernel may not function correctly > > panic[cpu0]/thread=fb828380: cannot mount root path > /pci@0,0/pci1022,7450@2/pci1000,3060@3/sd@0,0:a > > fb83f77c genunix:rootconf+fa (0, 1, fb827b10, 0, ) > fb83f7a0 genunix:vfs_mountroot+54 (fb400010, fb83d638,) > fb83f7c0 genunix:main+e4 () > > skipping system dump - no dump device configured > rebooting... > > When renaming the vbd disk to sda instead of 0, booting domU results in the > same panic message: > panic[cpu0]/thread=fb828380: cannot mount root path > /pci@0,0/pci1022,7450@2/pci1000,3060@3/sd@0,0:a > > fb83f77c genunix:rootconf+fa (0, 1, fb827b10, 0, ) > fb83f7a0 genunix:vfs_mountroot+54 (fb400010, fb83d638,) > fb83f7c0 genunix:main+e4 () > > skipping system dump - no dump device configured > > > > # cat mydomU.py > name = "mydomU" > memory = "400" > kernel = "/vol/local/solaris/unix" > extra = "/platform/i86xen/kernel/unix" > ramdisk = "/vol/local/solaris/boot_archive" > on_shutdown = "destroy" > on_reboot = "restart" > on_crash = "destroy" > root = "/dev/dsk/c0d0s0" > # disk = [''file:/vol/local/solaris/root.file,0,w''] > disk = [''file:/vol/local/solaris/root.file,sda,w''] > vif = [''mac=aa:00:ac:10:0c:09, bridge=xenbr0'']yep, definitely can''t do that. The number after the disk file specifies the disk # for us. The root disk has to be /dev/dsk/c0d#s0 for most cases. If your really advanced, you can change the controller and slice number easy enough.. But that''s not going to help you here. Currently, the xen code is linux specific here (we need to clean it up and get it back), but it still works for us even with the exception. Are you sure the exception is the problem? MRJ
Thanks! That did the trick. The Solaris domU can now be created and boot from my debian linux dom0. On Tue, Aug 22, 2006 at 11:22:35AM -0400, Mark Johnson wrote: " > " >" [0]> moddebug?W 0x80000000 " > " >panic[cpu0]/thread=fb828380: cannot mount root path " >/pci@0,0/pci1022,7450@2/pci1000,3060@3/sd@0,0:a " > " >fb83f77c genunix:rootconf+fa (0, 1, fb827b10, 0, ) " >fb83f7a0 genunix:vfs_mountroot+54 (fb400010, fb83d638,) " >fb83f7c0 genunix:main+e4 () " > " >panic: entering debugger (no dump device, continue to reboot) " >Loaded modules: [ ufs xen_psm specfs ] " >kmdb: target stopped at: " >kmdb_enter+0xa: pushl %eax " >[0]> " " It''s trying boot from the disk on the system you build the " boot_archive on :-) No such controller on the domU. " /pci@0,0/pci1022,7450@2/pci1000,3060@3/sd@0,0:a " " You need to mount the disk image on your solaris system " and use the boot archive from there.. " " # lofiadm -a <path>/root.file " " assuming this gets /dev/lofi/1 " " # mount /dev/lofi/1 /mnt " " then cd to /mnt/platform/i86xen/kernel, " do a ls and make sure things looks ok " Build you archive again, this time using " the disk image settings. " " # cd / " # touch /mnt/platform/i86xen/kernel/unix " # bootadm update-archive -R /mnt " # scp /mnt/platform/i86pc/boot_archive <path> " # umount /mnt " # lofiadm -d /dev/lofi/1 " " If your disk image is OK, this will solve the vfs_mountroot() " problem. " " " " MRJ