xen discuss - Jan 2008 - Solaris 10 DomU on Centos5.1 xen 3.0.3 - Multiple OS instances were found.

Hi Dear!
I''ve a painful problem here...
In some weeks I''m trying to install solaris 10 on my CentOS5.1 system.
Using the howto I can install OS10 without any particular problem.

But then when I reboot I get the folloe result:
[i][root@localhost xen]# xm create OS11-amd64-2 -c
Using config file "./OS11-amd64-2".
Started domain OS11-amd64
v3.1.0-53.1.4.el5.c chgset ''unavailable''
SunOS Release 5.11 Version snv_78 64-bit
Copyright 1983-2007 Sun Microsystems, Inc.  All rights reserved.
Use is subject to license terms.
Configuring /dev
NOTICE: xdf@sda: failed to read feature-barrier
Searching for installed OS instances...

Multiple OS instances were found. To check and mount one of them
read-write under /a, select it from the following list. To not mount
any, select ''q''.

  1  /dev/dsk/c0d-25308608s0     Solaris Express Community Edition snv_78 X86
  2  /dev/dsk/c0d134511472s0     Solaris Express Community Edition snv_78 X86

Please select a device to be mounted (q for none) [?,??,q]: 
[/i]

At this moment I try to update the book archive with:
[i]bootadm update-archive -f -R /a
[/i]

But nothing!!! I can''t boot in my solaris 10...
Somebody can help me!!!
Thanks 
Alessandro
 
 
This message posted from opensolaris.org

> Hi Dear!
> I''ve a painful problem here...
> In some weeks I''m trying to install solaris 10 on my
> CentOS5.1 system.
> Using the howto I can install OS10 without any
> particular problem.
> 
> But then when I reboot I get the folloe result:
> [i][root@localhost xen]# xm create OS11-amd64-2 -c
> Using config file "./OS11-amd64-2".
> Started domain OS11-amd64
> v3.1.0-53.1.4.el5 chgset ''unavailable''
This is version of Xen running at CentOS 5.1:-
3.1.0-53.1.4.el5 (it''s not 3.0.3)
Kernel  is already patched.
> SunOS Release 5.11 Version snv_78 64-bit
Looks like you try to create SNV78 DomU (it''s not Solaris 10)
> Copyright 1983-2007 Sun Microsystems, Inc.  All
> rights reserved.
> Use is subject to license terms.
> Configuring /dev
> NOTICE: xdf@sda: failed to read feature-barrier
> Searching for installed OS instances...
> 
> Multiple OS instances were found. To check and mount
> one of them
> read-write under /a, select it from the following
> list. To not mount
> any, select ''q''.
> 
> 1  /dev/dsk/c0d-25308608s0     Solaris Express
>  Community Edition snv_78 X86
> 2  /dev/dsk/c0d134511472s0     Solaris Express
>  Community Edition snv_78 X86
> 
> Please select a device to be mounted (q for none)
> [?,??,q]: 
> [/i]
> 
> At this moment I try to update the book archive
> with:
> [i]bootadm update-archive -f -R /a
> [/i]
> 
I can suggest to try workaround working for
Xen v3.1.0-53.el5 running at CentOS 5.1 ( not patched )

*************************************************************************
Root cause of issue error in blkif.py . If still there fix anyway.
*************************************************************************
# cd /usr/lib64/python2.4/site-packages/xen/xend/server
# vi blkif.py and made this change:

devid = blkif.blkdev_name_to_number(dev)
-if not devid:
+if devid is None:
raise VmError(''Unable to find number for device (%s)'' %
(dev))finally:

# /etc/init.d/xend restart

Create SNV78 DomU with usual profile 
Select DHCP during install.
Complete it.Change profile for runtime
and start up DomU again.
Modify /etc/system as usual for build < 81
Run:-
# bootadm update-archive
Copy (scp) boot_archive to Dom0
Make final changes to profile:-
ramdisk = "/usr/lib/xen-solaris/boot_archive"
*******************************************************************
If you need step by step instructions , view  blog entry:-
*******************************************************************

http://bderzhavets.blogspot.com/2008/01/install-opensolaris-snv78-domu-at.html 
> But nothing!!! I can''t boot in my solaris 10...
> Somebody can help me!!!
> Thanks 
> Alessandro
 
 
This message posted from opensolaris.org

I am not sure workaround will work for Xen 3.1.0-53.1.4.el5.
What I am sure about :- 
This is a Linux Bug.
Working on CentOS 5.1 you are your own. There is nobody you can escalate
the issue to.View also :-
http://forum.lxlabs.com/pdf.php?th=3273&.
 
 
This message posted from opensolaris.org

Boris Derzhavets wrote:
> I am not sure workaround will work for Xen 3.1.0-53.1.4.el5.
> What I am sure about :- 
> This is a Linux Bug.
> Working on CentOS 5.1 you are your own. There is nobody you can escalate
> the issue to.View also :-
> http://forum.lxlabs.com/pdf.php?th=3273&.
>  
>  
> This message posted from opensolaris.org
> _______________________________________________
> xen-discuss mailing list
> xen-discuss@opensolaris.org
>   
Wow, how helpful that discussion is ;-)
I tried it myself, same result, and it is a Linux-specific bug, you''d
need to patch your own build of the release kernel for CentOS 5.1. 
Workaround doesn''t work from my limited testing.

James

Workaround mentioned above does work with
kernel-xen-2.6.18-53.1.4.el5.x86_64.rpm:-
# rpm -ivh kernel-xen-2.6.18-53.1.4.el5.x86_64.rpm \
  kernel-xen-devel-2.6.18-53.1.4.el5.x86_64.rpm
Modify grub.conf as follows:-
title CentOS (2.6.18-53.1.4.el5xen)
root (hd0,4)
kernel /xen.gz-2.6.18-53.1.4.el5
module /vmlinuz-2.6.18-53.1.4.el5xen ro root=/dev/VolGroup02/LogVol01 rhgb quiet
module /initrd-2.6.18-53.1.4.el5xen.img
Reboot into new kernel and successfully reproduced SNV78 DomU install.
I will check "yum update" at my earliest convinience.
Snapshots will be attached shortly
 
 
This message posted from opensolaris.org

It also possible to deactivate virbr0 :-
# chkconfig  libvirtd off
# reboot
Now it becomes possible to create SNV DomUs with static IP addresses
working win xen-bridge (xenbr0) in good old style (view Tardis Wiki,
for example).
 
 
This message posted from opensolaris.org

Boris Derzhavets wrote:
> Workaround mentioned above does work with
kernel-xen-2.6.18-53.1.4.el5.x86_64.rpm:-
> # rpm -ivh kernel-xen-2.6.18-53.1.4.el5.x86_64.rpm \
>   kernel-xen-devel-2.6.18-53.1.4.el5.x86_64.rpm
> Modify grub.conf as follows:-
> title CentOS (2.6.18-53.1.4.el5xen)
> root (hd0,4)
> kernel /xen.gz-2.6.18-53.1.4.el5
> module /vmlinuz-2.6.18-53.1.4.el5xen ro root=/dev/VolGroup02/LogVol01 rhgb
quiet
> module /initrd-2.6.18-53.1.4.el5xen.img
> Reboot into new kernel and successfully reproduced SNV78 DomU install.
> I will check "yum update" at my earliest convinience.
> Snapshots will be attached shortly
>  
>  
> This message posted from opensolaris.org
> _______________________________________________
> xen-discuss mailing list
> xen-discuss@opensolaris.org
>   
Thanks Boris, I''ll try it as soon as I can :-).

James

Hi dear,
> > SunOS Release 5.11 Version snv_78 64-bit
> 
> Looks like you try to create SNV78 DomU (it''s not
> Solaris 10)
Yes sorry it is SNV78.
> 
> > Copyright 1983-2007 Sun Microsystems, Inc.  All
> > rights reserved.
> > Use is subject to license terms.
> > Configuring /dev
> > NOTICE: xdf@sda: failed to read feature-barrier
> > Searching for installed OS instances...
> > 
> > Multiple OS instances were found. To check and
> mount
> > one of them
> > read-write under /a, select it from the following
> > list. To not mount
> > any, select ''q''.
> > 
> > 1  /dev/dsk/c0d-25308608s0     Solaris Express
> >  Community Edition snv_78 X86
> > 2  /dev/dsk/c0d134511472s0     Solaris Express
> >  Community Edition snv_78 X86
> > 
> > Please select a device to be mounted (q for none)
> > [?,??,q]: 
> > [/i]
> > 
> > At this moment I try to update the book archive
> > with:
> > [i]bootadm update-archive -f -R /a
> > [/i]
> > 
> I can suggest to try workaround working for
> Xen v3.1.0-53.el5 running at CentOS 5.1 ( not patched
> )
> 
> ******************************************************
> *******************
> Root cause of issue error in blkif.py . If still
> there fix anyway.
> ******************************************************
> *******************
> # cd
> /usr/lib64/python2.4/site-packages/xen/xend/server
> # vi blkif.py and made this change:
> 
> devid = blkif.blkdev_name_to_number(dev)
> -if not devid:
> +if devid is None:
> raise VmError(''Unable to find number for device (%s)''
> % (dev))finally:
> 
> # /etc/init.d/xend restart
> 
> Create SNV78 DomU with usual profile 
> Select DHCP during install.
> Complete it.Change profile for runtime
> and start up DomU again.
> Modify /etc/system as usual for build < 81
> Run:-
> # bootadm update-archive
> Copy (scp) boot_archive to Dom0
> Make final changes to profile:-
> ramdisk = "/usr/lib/xen-solaris/boot_archive"
> ******************************************************
> *************
> If you need step by step instructions , view  blog
> entry:-
> ******************************************************
> *************
> 
> http://bderzhavets.blogspot.com/2008/01/install-openso
> laris-snv78-domu-at.html 
> 
> > But nothing!!! I can''t boot in my solaris 10...
> > Somebody can help me!!!
> > Thanks 
> > Alessandro
I have patched like you suggest but I have the same problem...
 
 
This message posted from opensolaris.org

> Workaround mentioned above does work with
> kernel-xen-2.6.18-53.1.4.el5.x86_64.rpm:-
> # rpm -ivh kernel-xen-2.6.18-53.1.4.el5.x86_64.rpm \
>   kernel-xen-devel-2.6.18-53.1.4.el5.x86_64.rpm
Ocky I''m using centos plus kernel version.
I''ll try to use the default...

ThankS
Zioale
 
 
This message posted from opensolaris.org

Alessandro <zioalex@gmail.com> wrote:
> But then when I reboot I get the folloe result:
> [root@localhost xen]# xm create OS11-amd64-2 -c
> Using config file "./OS11-amd64-2".
> Started domain OS11-amd64
> v3.1.0-53.1.4.el5.c chgset ''unavailable''
> SunOS Release 5.11 Version snv_78 64-bit
> Copyright 1983-2007 Sun Microsystems, Inc.  All rights reserved.
> Use is subject to license terms.
> Configuring /dev
> NOTICE: xdf@sda: failed to read feature-barrier
Where does that "sda" substring from the above notice message come
from?
Can you show us your OS11-amd64-2 config file for the solaris domU?

Did you perhaps use something like

   disk = [ ''phy:/dev/sda,sda,w'' ]

??

That wouldn''t be OK for a Solaris domU - you need
''phy:/dev/sda,0,w''
 
 
This message posted from opensolaris.org

During SNV DomU the very first startup expected output should be :-
NOTICE: xdf@0: failed to read feature-barrier
NOTICE: xdf@6: failed to read feature-barrier
Otherwise SNV78 DomU profile is incorrect
I would ask you to submit  the source of blkif.py file after you edit it
and SNV78 domU profile as was asked by jkeil .
P.S.
Make sure xend has been restarted after fixing code in blkif.py.
 
 
This message posted from opensolaris.org

> That wouldn''t be OK for a Solaris domU - you need
> ''phy:/dev/sda,0,w''
[b]Hi Dear,
thanks to everybody.[/b]

Finally My OS-SNV78 is UO&RUNNING . I''ve found some problem:
1) the /usr/lib/python2.4/site-packages/xen/xend/server/blkif.py patch
2) the domU sda device is wrong ; in Solaris use a number corresponding to the
solaris LUN
3) after the first  reboot the system doesn''t come up . I''ve
to configure manually the network to copy the updated boot_archive via nfs to
the domU

I like to attach the procedure used but the system said me that I
can''t!!!

Thanks Again to everybody

Zioalex
 
 
This message posted from opensolaris.org

> > That wouldn''t be OK for a Solaris domU - you need
> > ''phy:/dev/sda,0,w''
> 
> [b]Hi Dear,
> thanks to everybody.[/b]
> 
> Finally My OS-SNV78 is UO&RUNNING . I''ve found some
> problem:
> 1) the
> /usr/lib/python2.4/site-packages/xen/xend/server/blkif
> .py patch
> 2) the domU sda device is wrong ; in Solaris use a
> number corresponding to the solaris LUN
> 3) after the first  reboot the system doesn''t come up
> . I''ve to configure manually the network to copy the
> updated boot_archive via nfs to the domU
Make sure service "dnsmask" is running . It''s DHCP server for
CentOS 5.1 DomUs
You should be able specify DHCP for xnf0 during first install.
When done:-
1.Modify disk entry like:-
disk=[''phy:/dev/sdaX,0,w'']
2. Add:-
root="/dev/dsk/c0d0s0"
Be patient during next startup SNV DomU will send DHCP request to
"dnsmask"
service. You should be able to get a login prompt.
Login as root:-
1.Modify /etc/system as usual.
2.bootadm update-archive
3.Copy (scp) boot_archive to CentOS 5.1 Dom0.
4.Shutdown
Modify ramdisk entry pointing to full path of boot_archive at Dom0
1. Startup SNV 78 DomU
> 
> I like to attach the procedure used but the system
> said me that I can''t!!!
> 
> Thanks Again to everybody
> 
> Zioalex
 
 
This message posted from opensolaris.org

> > updated boot_archive via nfs to the domU
> 
> Make sure service "dnsmask" is running . It''s DHCP
> server for  CentOS 5.1 DomUs
> You should be able specify DHCP for xnf0 during first
> install.
> When done:-
> 1.Modify disk entry like:-
> disk=[''phy:/dev/sdaX,0,w'']
> 2. Add:-
> root="/dev/dsk/c0d0s0"
> Be patient during next startup SNV DomU will send
> DHCP request to "dnsmask"
> service. You should be able to get a login prompt.
> Login as root:-
> 1.Modify /etc/system as usual.
> 2.bootadm update-archive
> 3.Copy (scp) boot_archive to CentOS 5.1 Dom0.
> 4.Shutdown
> Modify ramdisk entry pointing to full path of
> boot_archive at Dom0
> 1. Startup SNV 78 DomU
> *****************
> Fair enough ?
> *****************
> http://bderzhavets.blogspot.com/2008/01/internet-worki
> ng-on-snv78-domu-at.html
> > 
> > I like to attach the procedure used but the system
> > said me that I can''t!!!
> > 
> > Thanks Again to everybody
> > 
> > Zioalex
Dear dbaxps,
this procedure doesn''t work for me.
I''ve done some trick to copy the updated boot_archive in domU.
The detail here:
http://mpd.homeip.net/?p=210
 
 
This message posted from opensolaris.org

Per Alex ( http://mpd.homeip.net/?p=210)  install profile for SNV78 DomU at
CentOS 5.1 :-
name = "OS11-amd64-final"
memory = 1024
vcpus = "1"
vif = [ "" ]
#dhcp="dhcp"
kernel = "/app/XenVm/os11-snv78-full/dvd.unix.64"
## PRE INSTALL
disk = [ 'file://app/XenVm/dvd/sol-nv-b78-x86-dvd.iso,6:cdrom,r', 
"file:/app/XenVm/os11-snv78-full/svn78.root.disk,sda,w" ]
extra = "/platform/i86xpv/kernel/amd64/unix - nowin -B
install_media=cdrom"
ramdisk = "/app/XenVm/os11-snv78-full/dvd.x86.miniroot"
## POST INSTALL
#disk = [ "file:/app/XenVm/os11-snv78-full/svn78.root.disk,0,w" ]
#extra = '/platform/i86xpv/kernel/amd64/unix'
#ramdisk = "/app/XenVm/os11-snv78-full/boot_archive.amd64"
rootdisk = '/dev/dsk/c0d0s0'
*******************************************
I see two strange entries in profile:-
*******************************************
disk = [ 'file://app/XenVm/dvd/sol-nv-b78-x86-dvd.iso,6:cdrom,r', 
"file:/app/XenVm/os11-snv78-full/svn78.root.disk,sda,w" ]
rootdisk = '/dev/dsk/c0d0s0'

I would try remove “rootdisk” at all (add it latter  for runtime) and modify
“disk”:-
disk = [ 'file://app/XenVm/dvd/sol-nv-b78-x86-dvd.iso,6:cdrom,r', 
"file:/app/XenVm/os11-snv78-full/svn78.root.disk,0w" ]
Then see what happens ?
 
 
This message posted from opensolaris.org
_______________________________________________
xen-discuss mailing list
xen-discuss@opensolaris.org

Snapshots of configs suggested by zioalex attached.
 
 
This message posted from opensolaris.org

It seems to me a kind of fun. Now Alex silently changed his install profile:-
*******************************************************************************************
name = "OS11-amd64-final"
memory = 1024
vcpus = "1"
vif = [ "" ]
#dhcp="dhcp"
kernel = "/app/XenVm/os11-snv78-full/dvd.unix.64"
## PRE INSTALL
disk = [
''file://app/XenVm/dvd/sol-nv-b78-x86-dvd.iso,6:cdrom,r'', 
"file:/app/XenVm/os11-snv78-full/svn78.root.disk,0,w" ]
extra = "/platform/i86xpv/kernel/amd64/unix - nowin -B
install_media=cdrom"
ramdisk = "/app/XenVm/os11-snv78-full/dvd.x86.miniroot"
## POST INSTALL
#disk = [ "file:/app/XenVm/os11-snv78-full/svn78.root.disk,0,w" ]
#extra = ''/platform/i86xpv/kernel/amd64/unix''
#ramdisk = "/app/XenVm/os11-snv78-full/boot_archive.amd64"
rootdisk = ''/dev/dsk/c0d0s0''
*********************************************************************************************
But still follows his special way due to entry:-
 rootdisk = ''/dev/dsk/c0d0s0''
Please, do one more step and remove :-)
rootdisk = ''/dev/dsk/c0d0s0''
from installation profile. I strongly believe the rest of Alex''s blog
will change as well. No more tricks will be needed. If I am wrong
about that, please, respond.
Regards.
Boris.
 
 
This message posted from opensolaris.org

I''m having problems following the howto''s for Solaris on
CentOS 5.1/Xen.  Here is my setup:

CentOS 5.0 installed from CD''s, plus patched to 5.1 from yum

# uname -r
2.6.18-53.1.4.el5xen

# cat /etc/redhat-release
CentOS release 5 (Final) 

# ls -al /usr/lib/xen-solaris/
-rwxrwxrwx  1 root root 2718433280 Jan 17 17:32 sol-10-u4-ga-x86-dvd.iso
-rwxrwxrwx  1 root root 3674931200 Jan 18 11:21 sol-nv-b78-x86-dvd.iso
-rwxrwxrwx  1 root root    1352660 Jan 18 11:23 unix-78
-rwxrwxrwx  1 root root   61181057 Jan 18 11:22 x86.miniroot

# ls -al /xen/
-rw-r--r--  1 root root 10240000000 Jan 17 17:43 solaris.img

# cat /etc/xen/solaris
name = ''solaris''
memory = ''1024''
disk = [
''file:/xen/solaris.img,0,w'',''file:/usr/lib/xen-solaris/sol-nv-b78-x86-dvd.iso,6:cdrom,r''
]
vif = [ '''' ]
on_shutdown = ''destroy''
on_reboot = ''destroy''
on_crash = ''destroy''
kernel = ''/usr/lib/xen-solaris/unix-78''
ramdisk = ''/usr/lib/xen-solaris/x86.miniroot''
extra = ''/platform/i86xpv/kernel/unix - nowin -B
install_media=cdrom''

I''ve made the change to
/usr/lib/python2.4/site-packages/xen/xend/server/blkif.py and restarted xend

When I try to create the VM I get the following:
# xm create /etc/xen/solaris -c
Using config file "/etc/xen/solaris".
Error: Device 6 (vbd) could not be connected. losetup -r /dev/loop1
/usr/lib/xen-solaris/sol-nv-b78-x86-dvd.iso failed

# cat /var/log/xen/xen-hotplug.log 
Nothing to flush.
/usr/lib/xen-solaris/sol-nv-b78-x86-dvd.iso: Permission denied
xenstore-read: couldn''t read path backend/vbd/5/6/node

Any help would be appreciated as nobody else seems to have the same problems
with CentOS 5
 
 
This message posted from opensolaris.org

Paul Abel wrote:
> I''m having problems following the howto''s for Solaris on
CentOS 5.1/Xen.  Here is my setup:
> 
> CentOS 5.0 installed from CD''s, plus patched to 5.1 from yum

corrupted iso??  Can you:
  # mount -o loop /usr/lib/xen-solaris/sol-nv-b78-x86-dvd.iso /mnt


 > disk = [
''file:/xen/solaris.img,0,w'',''file:/usr/lib/xen-solaris/sol-nv-b78-x86-dvd.iso,6:cdrom,r''
]


Usually, you want to put the disk your going to boot
off of first on the disk line.  It shouldn''t matter
in your case since you copied out the kernel and
ramdisk. You can have left them in the iso and just
referred to them.

disk = [
''file:/usr/lib/xen-solaris/sol-nv-b78-x86-dvd.iso,6:cdrom,r'',
''file:/xen/solaris.img,0,w'' ]



MRJ




> # uname -r
> 2.6.18-53.1.4.el5xen
> 
> # cat /etc/redhat-release
> CentOS release 5 (Final) 
> 
> # ls -al /usr/lib/xen-solaris/
> -rwxrwxrwx  1 root root 2718433280 Jan 17 17:32 sol-10-u4-ga-x86-dvd.iso
> -rwxrwxrwx  1 root root 3674931200 Jan 18 11:21 sol-nv-b78-x86-dvd.iso
> -rwxrwxrwx  1 root root    1352660 Jan 18 11:23 unix-78
> -rwxrwxrwx  1 root root   61181057 Jan 18 11:22 x86.miniroot
> 
> # ls -al /xen/
> -rw-r--r--  1 root root 10240000000 Jan 17 17:43 solaris.img
> 
> # cat /etc/xen/solaris
> name = ''solaris''
> memory = ''1024''
> disk = [
''file:/xen/solaris.img,0,w'',''file:/usr/lib/xen-solaris/sol-nv-b78-x86-dvd.iso,6:cdrom,r''
]
> vif = [ '''' ]
> on_shutdown = ''destroy''
> on_reboot = ''destroy''
> on_crash = ''destroy''
> kernel = ''/usr/lib/xen-solaris/unix-78''
> ramdisk = ''/usr/lib/xen-solaris/x86.miniroot''
> extra = ''/platform/i86xpv/kernel/unix - nowin -B
install_media=cdrom''
> 
> I''ve made the change to
/usr/lib/python2.4/site-packages/xen/xend/server/blkif.py and restarted xend
> 
> When I try to create the VM I get the following:
> # xm create /etc/xen/solaris -c
> Using config file "/etc/xen/solaris".
> Error: Device 6 (vbd) could not be connected. losetup -r /dev/loop1
/usr/lib/xen-solaris/sol-nv-b78-x86-dvd.iso failed
> 
> # cat /var/log/xen/xen-hotplug.log 
> Nothing to flush.
> /usr/lib/xen-solaris/sol-nv-b78-x86-dvd.iso: Permission denied
> xenstore-read: couldn''t read path backend/vbd/5/6/node
> 
> Any help would be appreciated as nobody else seems to have the same
problems with CentOS 5
>  
>  
> This message posted from opensolaris.org
> _______________________________________________
> xen-discuss mailing list
> xen-discuss@opensolaris.org

Boris,
I don''t want to fool you and nobody else.
I''ve sent a message in this forum saying that it was just a typewrite
problem...But sure there weren''t a problem and the message
doesn''t arrive.

But you think I just correct my errors...in a malicious manner...!!! Please
consider what you say!!!

> It seems to me a kind of fun. Now Alex silently
> changed his install profile:-
**********************************************************
***********************************
But still follows his special way due to entry:-
rootdisk = ''/dev/dsk/c0d0s0''
Please, do one more step and remove :-)
rootdisk = ''/dev/dsk/c0d0s0''
> from installation profile. I strongly believe the
> rest of Alex''s blog
> will change as well. No more tricks will be needed.
> If I am wrong
> about that, please, respond.
> Regards.
> Boris.
For the rootdisk options I''m sure that with it I can configure and run
my DomU Solaris.

Now I don''t  need any deep analysis to know if without its all work.

Alex
 
 
This message posted from opensolaris.org

> # cat /etc/xen/solaris
> name = ''solaris''
> memory = ''1024''
> disk = [
>
''file:/xen/solaris.img,0,w'',''file:/usr/lib/xen-solaris
> /sol-nv-b78-x86-dvd.iso,6:cdrom,r'' ]
> vif = [ '''' ]
> on_shutdown = ''destroy''
> on_reboot = ''destroy''
> on_crash = ''destroy''
> kernel = ''/usr/lib/xen-solaris/unix-78''
> ramdisk = ''/usr/lib/xen-solaris/x86.miniroot''
> extra = ''/platform/i86xpv/kernel/unix - nowin -B
> install_media=cdrom''
>
First try to exchange the disk order; put before the dvd image and then the
disk.
disk = [
''file:/usr/lib/xen-solaris/sol-nv-b78-x86-dvd.iso,6:cdrom,r'',file:/xen/solaris.img,0,w''
]
> I''ve made the change to
> /usr/lib/python2.4/site-packages/xen/xend/server/blkif
> .py and restarted xend
> 
> When I try to create the VM I get the following:
> # xm create /etc/xen/solaris -c
> Using config file "/etc/xen/solaris".
> Error: Device 6 (vbd) could not be connected. losetup
> -r /dev/loop1
> /usr/lib/xen-solaris/sol-nv-b78-x86-dvd.iso failed
> 
Have you the loop module loaded or built in the kernel?
> # cat /var/log/xen/xen-hotplug.log 
> Nothing to flush.
> /usr/lib/xen-solaris/sol-nv-b78-x86-dvd.iso:
> Permission denied
This is very strange after your permission listing!!!
> xenstore-read: couldn''t read path
> backend/vbd/5/6/node
> 
> Any help would be appreciated as nobody else seems to
> have the same problems with CentOS 5
 
 
This message posted from opensolaris.org

> Boris,
> I don''t want to fool you and nobody else.
> I''ve sent a message in this forum saying that it was
> just a typewrite problem...But sure there weren''t a
> problem and the message doesn''t arrive.
> 
> But you think I just correct my errors...in a
> malicious manner...!!! Please consider what you
> say!!!
> 
> 
> > It seems to me a kind of fun. Now Alex silently
> > changed his install profile:-
> ******************************************************
> **** ***********************************
> But still follows his special way due to entry:-
> rootdisk = ''/dev/dsk/c0d0s0''
> Please, do one more step and remove :-)
> rootdisk = ''/dev/dsk/c0d0s0''
> > from installation profile. I strongly believe the
> > rest of Alex''s blog
> > will change as well. No more tricks will be
> needed.
> > If I am wrong
> > about that, please, respond.
> > Regards.
> > Boris.
> For the rootdisk options I''m sure that with it I can
> configure and run my DomU Solaris.
> 
> Now I don''t  need any deep analysis to know if
> without its all work.
Analysis is done and it works:-
1.http://wiki.tardis.ed.ac.uk/index.php/OpenSolaris_Xen_domU
2.http://lxer.com/module/newswire/view/93016/index.html
3.http://librenix.com/?inode=11539
4.http://librenix.com/?inode=11594
Thanks.
Boris
> 
> Alex
 
 
This message posted from opensolaris.org

Thanks for the responses.  I''ve managed to sort out the problem, there
was a typing mistake in my config file.  I had a space after the disk number in
the cdrom section.
 
 
This message posted from opensolaris.org

> Wow, how helpful that discussion is ;-)
> I tried it myself, same result, and it is a
> Linux-specific bug, you''d
> need to patch your own build of the release kernel
> for CentOS 5.1. 
> Workaround doesn''t work from my limited testing.
Hi James,
I just comleted "yum update" on CentOS 5.1 box:-
[root@ServerRHL51 xen-solaris]# uname -a
Linux ServerRHL51 2.6.18-53.1.13.el5xen #1 SMP Tue Feb 12 13:33:07 
EST 2008 x86_64 x86_64 x86_64 GNU/Linux
Applied mentioned above workaround and proceeded with standard SNV81 DomU
installation with no problems.If something will go wrong, i''ll let you
know ASAP :-)
Regards.
-b
> 
> James
> _______________________________________________
> xen-discuss mailing list
> xen-discuss@opensolaris.org
 
 
This message posted from opensolaris.org