Xen users - Sep 2009 - OpenSolaris domU on RedHat Linux dom0

Hi,

I''m trying to create OpenSolaris (2008.11) domU on RedHat Linux dom0.
I''m using a file backed VBD. I used the iso image to first launch and
install OpenSolaris into the file VBD. Once that process is complete,
I''m trying to run it using the config file below:

name    = ''opensolaris''
vcpus   = 1
memory  = "512"
vif     = [''bridge=br0'']
ip = "10.226.33.98"
netmask = "255.255.255.0"
gateway = "10.226.33.1"
disk    [
''file:/Application/xen/images/opensolaris_2008_11.disk,0,w'' ]
kernel  = ''/boot/osol/kernel.opensolaris''
ramdisk = ''/boot/osol/ramdisk.opensolaris''
extra   = ''/platform/i86xpv/kernel/unix -B
zfs-bootfs=rpool/54,bootpath=/xpvd/xdf@0:a''
on_shutdown = ''destroy''
on_reboot = ''destroy''
on_crash = ''destroy''

When I do that, I get an error message like this.

Unable to find number for device (0)

Can someone please help me debug this problem?

Thanks,
Viswanath




This e-mail and any files transmitted with it are for the sole use of 
the intended recipient(s) and may contain confidential and privileged 
information.
If you are not the intended recipient, please contact the sender by 
reply e-mail and destroy all copies of the original message.
Any unauthorized review, use, disclosure, dissemination, forwarding, 
printing or copying of this email or any action taken in reliance on this 
e-mail is strictly prohibited and may be unlawful.

  

_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

Btwy, ''brctl show'' is it matching to your  vif ?


- regards
   Pallab




-----Original Message-----
From: xen-users-bounces@lists.xensource.com
[mailto:xen-users-bounces@lists.xensource.com] On Behalf Of Viswanath
Durbha
Sent: Wednesday, September 09, 2009 4:51 PM
To: xen-users
Subject: [Xen-users] OpenSolaris domU on RedHat Linux dom0

Hi,

I''m trying to create OpenSolaris (2008.11) domU on RedHat Linux dom0.
I''m
using a file backed VBD. I used the iso image to first launch and install
OpenSolaris into the file VBD. Once that process is complete, I''m
trying
to run it using the config file below:

name    = ''opensolaris''
vcpus   = 1
memory  = "512"
vif     = [''bridge=br0'']
ip = "10.226.33.98"
netmask = "255.255.255.0"
gateway = "10.226.33.1"
disk    = [
''file:/Application/xen/images/opensolaris_2008_11.disk,0,w'' ]
kernel  = ''/boot/osol/kernel.opensolaris''
ramdisk = ''/boot/osol/ramdisk.opensolaris''
extra   = ''/platform/i86xpv/kernel/unix -B
zfs-bootfs=rpool/54,bootpath=/xpvd/xdf@0:a''
on_shutdown = ''destroy''
on_reboot = ''destroy''
on_crash = ''destroy''

When I do that, I get an error message like this.

Unable to find number for device (0)

Can someone please help me debug this problem?

Thanks,
Viswanath


This e-mail and any files transmitted with it are for the sole use of
the intended recipient(s) and may contain confidential and privileged
information.
If you are not the intended recipient, please contact the sender by
reply e-mail and destroy all copies of the original message.
Any unauthorized review, use, disclosure, dissemination, forwarding,
printing or copying of this email or any action taken in reliance on this
e-mail is strictly prohibited and may be unlawful.




No virus found in this incoming message.
Checked by AVG - www.avg.com
Version: 8.5.409 / Virus Database: 270.13.86/2355 - Release Date: 09/08/09
20:45:00

_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

Yes. ''brctl show'' matches with vif. This error seems to be
related to
the deviceid ''0'' that I''m using for my disk. The
xend.log file shows the
following details about the error.

[2009-09-09 15:12:41 xend 3718] DEBUG (blkif:24) exception looking up
device number for 0: [Errno 2] No such file or directory:
''/dev/0''
[2009-09-09 15:12:41 xend.XendDomainInfo 3718] ERROR
(XendDomainInfo:212) Domain construction failed
Traceback (most recent call last):
  File "/usr/lib/python2.4/site-packages/xen/xend/XendDomainInfo.py",
line 205, in create
    vm.initDomain()
  File "/usr/lib/python2.4/site-packages/xen/xend/XendDomainInfo.py",
line 1463, in initDomain
    self.createDevices()
  File "/usr/lib/python2.4/site-packages/xen/xend/XendDomainInfo.py",
line 1679, in createDevices
    self.createDevice(n, c)
  File "/usr/lib/python2.4/site-packages/xen/xend/XendDomainInfo.py",
line 1154, in createDevice
    return self.getDeviceController(deviceClass).createDevice(devconfig)
  File
"/usr/lib/python2.4/site-packages/xen/xend/server/DevController.py",
line 80, in createDevice
    (devid, back, front) = self.getDeviceDetails(config)
  File "/usr/lib/python2.4/site-packages/xen/xend/server/blkif.py",
line
85, in getDeviceDetails
    raise VmError(''Unable to find number for device (%s)'' %
(dev))
VmError: Unable to find number for device (0)
[2009-09-09 15:12:41 xend.XendDomainInfo 3718] DEBUG
(XendDomainInfo:1557) XendDomainInfo.destroy: domid=95
[2009-09-09 15:12:41 xend.XendDomainInfo 3718] DEBUG
(XendDomainInfo:1566) XendDomainInfo.destroyDomain(95)

Thanks,
Viswanath

On Wed, 2009-09-09 at 06:24 -0500, Pallab Chakrabarty wrote:
> Btwy, ''brctl show'' is it matching to your  vif ?
> 
> 
> - regards
>    Pallab
> 
> 
> 
> 
> -----Original Message-----
> From: xen-users-bounces@lists.xensource.com
> [mailto:xen-users-bounces@lists.xensource.com] On Behalf Of Viswanath
> Durbha
> Sent: Wednesday, September 09, 2009 4:51 PM
> To: xen-users
> Subject: [Xen-users] OpenSolaris domU on RedHat Linux dom0
> 
> Hi,
> 
> I''m trying to create OpenSolaris (2008.11) domU on RedHat Linux
dom0. I''m
> using a file backed VBD. I used the iso image to first launch and install
> OpenSolaris into the file VBD. Once that process is complete, I''m
trying
> to run it using the config file below:
> 
> name    = ''opensolaris''
> vcpus   = 1
> memory  = "512"
> vif     = [''bridge=br0'']
> ip = "10.226.33.98"
> netmask = "255.255.255.0"
> gateway = "10.226.33.1"
> disk    = [
''file:/Application/xen/images/opensolaris_2008_11.disk,0,w'' ]
> kernel  = ''/boot/osol/kernel.opensolaris''
> ramdisk = ''/boot/osol/ramdisk.opensolaris''
> extra   = ''/platform/i86xpv/kernel/unix -B
> zfs-bootfs=rpool/54,bootpath=/xpvd/xdf@0:a''
> on_shutdown = ''destroy''
> on_reboot = ''destroy''
> on_crash = ''destroy''
> 
> When I do that, I get an error message like this.
> 
> Unable to find number for device (0)
> 
> Can someone please help me debug this problem?
> 
> Thanks,
> Viswanath
> 
> 
> This e-mail and any files transmitted with it are for the sole use of
> the intended recipient(s) and may contain confidential and privileged
> information.
> If you are not the intended recipient, please contact the sender by
> reply e-mail and destroy all copies of the original message.
> Any unauthorized review, use, disclosure, dissemination, forwarding,
> printing or copying of this email or any action taken in reliance on this
> e-mail is strictly prohibited and may be unlawful.
> 
> 
> 
> 
> No virus found in this incoming message.
> Checked by AVG - www.avg.com
> Version: 8.5.409 / Virus Database: 270.13.86/2355 - Release Date: 09/08/09
> 20:45:00



This e-mail and any files transmitted with it are for the sole use of 
the intended recipient(s) and may contain confidential and privileged 
information.
If you are not the intended recipient, please contact the sender by 
reply e-mail and destroy all copies of the original message.
Any unauthorized review, use, disclosure, dissemination, forwarding, 
printing or copying of this email or any action taken in reliance on this 
e-mail is strictly prohibited and may be unlawful.

  

_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

On Wed, Sep 9, 2009 at 6:35 PM, Viswanath Durbha <
Durbha.Viswanath@cognizant.com> wrote:
>  Yes. ''brctl show'' matches with vif. This error seems to
be related to the
> deviceid ''0'' that I''m using for my disk. The
xend.log file shows the
> following details about the error.
>
> packages/xen/xend/server/blkif.py", line 85, in getDeviceDetails
>     raise VmError(''Unable to find number for device (%s)''
% (dev))
> VmError: Unable to find number for device (0)
>

As I recall you should edit blkif.py to get it to understand "0" as a
valid
device if using Redhat''s version of Xen.

An easier method is to use newer Xen version from http://www.gitco.de/repo/

-- 
Fajar


_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

On Wed, Sep 09, 2009 at 04:50:33PM +0530, Viswanath Durbha wrote:
> [
''file:/Application/xen/images/opensolaris_2008_11.disk,0,w'' ]
Use ''xvda'' not ''0''

regards
john

_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

>When I do that, I get an error message like this.
>
>Unable to find number for device (0)
>
>Can someone please help me debug this problem?
>
>Thanks,
>Viswanath 
Without posting a long email, please check this entry on my blog for my
instructions on setting up an opensolaris DomU on a CentOS 5.2 Dom0. If you have
any questions about my instructions, feel free to email me.

http://www.taiter.com/blog/2009/02/opensolaris-200811-paravirtual.html#more

Best,
Tait



_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

> 
> Without posting a long email, please check this entry on my blog for my 
> instructions on setting up an opensolaris DomU on a CentOS 5.2 Dom0. If you
have
> any questions about my instructions, feel free to email me.
> 
> http://www.taiter.com/blog/2009/02/opensolaris-200811-paravirtual.html#more
> 
> Best,
> Tait
I just used this to get a DomU going two minutes ago, so thanks for that. I
started off on another description, but that had me copying some file called
boot_archive  from /a/platform..... /a was empty and I couldn''t figure
out how to mount the installed disk, if that was what I was supposed to do.

I then came across your blog which allowed me to finish it off. I don''t
know whether it was right not to use boot_archive or what you are missing out by
not using it.



      

_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

> >
> > Without posting a long email, please check this entry on my blog for
my
> > instructions on setting up an opensolaris DomU on a CentOS 5.2 Dom0.
If
> you have
> > any questions about my instructions, feel free to email me.
> >
> > http://www.taiter.com/blog/2009/02/opensolaris-200811-
> paravirtual.html#more
> >
> > Best,
> > Tait
> 
> I just used this to get a DomU going two minutes ago, so thanks for that. I
> started off on another description, but that had me copying some file
called
> boot_archive  from /a/platform..... /a was empty and I couldn't figure
out
> how to mount the installed disk, if that was what I was supposed to do.
> 
> I then came across your blog which allowed me to finish it off. I don't
know
> whether it was right not to use boot_archive or what you are missing out by
> not using it.
Yeah, that part had me pretty confused as well. Glad to hear I could be of some
help, I haven't done any stress testing on an Opensolaris domU yet so I am
not sure how stable it is to run under xen.

Tait

_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

On Wed, Sep 9, 2009 at 8:22 PM, Tait
Clarridge<Tait.Clarridge@lavalife.com> wrote:
> Without posting a long email, please check this entry on my blog for my
instructions on setting up an opensolaris DomU on a CentOS 5.2 Dom0. If you have
any questions about my instructions, feel free to email me.
>
> http://www.taiter.com/blog/2009/02/opensolaris-200811-paravirtual.html#more
So after comparing your blog and John Levon''s
(http://blogs.sun.com/levon/entry/opensolaris_2009_06_guest_domain),
and trying it for opensolaris snv_122 from genunix.org, here''s what I
come up with :

- you can use "xvda" instead of "0" for domU disk (in fact,
xvda is
currently recommended)
- if you use 64bit kernel, location of x86.microroot has moved to
/boot/amd64/x86.microroot
- no need for "-B console=ttya,livemode=text" anymore
- the live CD can''t use virtual frame buffer, but by default it
creates a vnc server whose parameter (ip, port, password) can be
lookup from xenstore. So it''s an alternative to starting vncserver
manually

Some additional note, if you use updated Xen 3.4.1 and virt-install
0.6.4 from Gitco, virt-install works for opensolaris installation :D

-- 
Fajar

_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

Hi,

I finally have my OpenSolaris domU up and running by using
''xvda''
instead of ''0''. But I want to emphasize here that
''xvda'' has to be used
while installing from iso as well as when running it after installation.
Using ''0'' while installing and ''xvda'' after
install did not work for me.

I have couple of more questions.

1. How do we use the domU disk image of OpenSolaris and provision many
domU''s using LVM partitions? In other words, can we clone it to create
many copies?
2. Is it possible to assign static ip address to domU from the
configuration file itself with parameters like ip=x.x.x.x and
netmask=x.x.x.x etc?

Thanks,
Viswanath

On Thu, 2009-09-10 at 12:06 +0700, Fajar A. Nugraha wrote:
> On Wed, Sep 9, 2009 at 8:22 PM, Tait
> Clarridge<Tait.Clarridge@lavalife.com> wrote:
> > Without posting a long email, please check this entry on my blog for
my instructions on setting up an opensolaris DomU on a CentOS 5.2 Dom0. If you
have any questions about my instructions, feel free to email me.
> >
> >
http://www.taiter.com/blog/2009/02/opensolaris-200811-paravirtual.html#more
> 
> So after comparing your blog and John Levon''s
> (http://blogs.sun.com/levon/entry/opensolaris_2009_06_guest_domain),
> and trying it for opensolaris snv_122 from genunix.org, here''s
what I
> come up with :
> 
> - you can use "xvda" instead of "0" for domU disk (in
fact, xvda is
> currently recommended)
> - if you use 64bit kernel, location of x86.microroot has moved to
> /boot/amd64/x86.microroot
> - no need for "-B console=ttya,livemode=text" anymore
> - the live CD can''t use virtual frame buffer, but by default it
> creates a vnc server whose parameter (ip, port, password) can be
> lookup from xenstore. So it''s an alternative to starting vncserver
> manually
> 
> Some additional note, if you use updated Xen 3.4.1 and virt-install
> 0.6.4 from Gitco, virt-install works for opensolaris installation :D
> 



This e-mail and any files transmitted with it are for the sole use of 
the intended recipient(s) and may contain confidential and privileged 
information.
If you are not the intended recipient, please contact the sender by 
reply e-mail and destroy all copies of the original message.
Any unauthorized review, use, disclosure, dissemination, forwarding, 
printing or copying of this email or any action taken in reliance on this 
e-mail is strictly prohibited and may be unlawful.

  

_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

On Thu, Sep 10, 2009 at 12:43 PM, Viswanath
Durbha<Durbha.Viswanath@cognizant.com> wrote:
> Hi,
>
> I finally have my OpenSolaris domU up and running by using
''xvda'' instead of
> ''0''. But I want to emphasize here that
''xvda'' has to be used while
> installing from iso as well as when running it after installation. Using
''0''
> while installing and ''xvda'' after install did not work
for me.
>
> I have couple of more questions.
>
> 1. How do we use the domU disk image of OpenSolaris and provision many
> domU''s using LVM partitions? In other words, can we clone it to
create many
> copies?
Yes, a simple "dd" will do.
> 2. Is it possible to assign static ip address to domU from the
configuration
> file itself with parameters like ip=x.x.x.x and netmask=x.x.x.x etc?
I don''t think so. It requires kernel-level IP configuration support
(which AFAIK is not compiled-in even on some linux distros).
And even then, on the default setup there''s nothing preventing domU
from changing it''s own IP address. Better use dhcp.

You should ask on opensolaris list to be sure.

-- 
Fajar

_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users