Yes,on Ubuntu 9.10 Server , Xen 3.4.3-rc1 Dom0 (2.6.31.6 pvops) , i cannot

#  virsh create osol131.install 

***************
osol131.install
****************
<domain type='xen' id='1'>
<name>OS131</name>
<memory>2097152</memory>
<currentMemory>2097152</currentMemory>
<vcpu>2</vcpu>
<bootloader>/usr/bin/pygrub</bootloader>
<bootloader_args>--kernel=/platform/i86xpv/kernel/amd64/unix 
--ramdisk=/platform/i86pc/amd64/boot_archive</bootloader_args>
<clock offset='utc'/>
<on_poweroff>destroy</on_poweroff>
<on_reboot>restart</on_reboot>
<on_crash>restart</on_crash>
<devices>
<disk type='file' device='cdrom'>
<driver name='file'/>
<source file='/root/osol131.iso'/>
<target dev='xvdc' bus='xen'/>
<readonly/>
</disk>
<disk type='block' device='disk'>
<driver name='phy'/>
<source dev='/dev/sdb7'/>
<target dev='xvda' bus='xen'/>
</disk>
<interface type='bridge'>
<mac address='00:16:3e:2a:0b:28'/>
<source bridge='eth0'/>
<script path='/etc/xen/scripts/vif-bridge'/>
<target dev='vif1.0'/>
</interface>
<console type='pty' tty='/dev/pts/1'>
<source path='/dev/pts/1'/>
<target port='0'/>
</console>
</devices>
</domain>

Pygrub doesn't return any data.
However , same profile starts install OSOL131 DomU via "virsh create" at Xen 
3.4.2 Dom0 (same pvops kernel) on top of Fedora 12 .


--- On Sat, 1/23/10, Michael Böhm <[email protected]> wrote:

From: Michael Böhm <[email protected]>
Subject: [xen-discuss] OpenSolaris DomU installation problem
To: [email protected]
Date: Saturday, January 23, 2010, 1:53 PM

Hi,

I try to install OpenSolaris DomU. Xen Version is 3.4.3-rc1, Dom0 is Ubuntu 
9.10 64bit server with linux kernel 2.6.31.6 from 
git://git.kernel.org/pub/scm/linux/kernel/git/jeremy/xen.git .

Hardware is Intel S5520HC server mainboard (vt-d) with latest firmware and dual 
Intel Xeon E5520. System has 8 physical / 16 logical cores and 12GB ram.

My setup works, I have running linux(pv and hvm), freebsd(hvm) and windows(hvm) 
virtual machines.

But I have absolutely no success in installing OpenSolaris virtual machine. 
Native install works but that does not help me because I need a linux Dom0, 
have special hardware with no driver support for OpenSolaris.

*1* OpenSolaris 0906 hvm:

r...@vmhost:/etc/xen# xm create osol-0906-64-hvm.cfg
Using config file "./osol-0906-64-hvm.cfg".
Started domain osol-0906-64-hvm (id=2)
r...@vmhost:/etc/xen# xm list
Name                                        ID   Mem VCPUs      State   Time(s)
Domain-0                                     0  1020    16     r-----    159.1
osol-0906-64-hvm                             2  2048     1     -b----     17.7

System boots to grub, then
SunOS Release 5.11 Version snv_111b 64-bit
Copyright 1983-2009 Sun Microsystems, Inc.  All rights reserved.
Use is subject to license terms.
Hostname: opensolaris
Remounting root read/write
Probing for device nodes...

Here system freezes, no cpu consumption, no errors messages.

*2* OpenSolaris 0906 pv:

r...@vmhost:/etc/xen# xm create -c osol-0906-64-pv.cfg
Using config file "./osol-0906-64-pv.cfg".
Started domain osol-0906-64-pv (id=3)
                                     v3.4.3-rc1 chgset 'Wed Jan 13 08:37:09 
2010 +0000 19871:eafb9f876dd2'
SunOS Release 5.11 Version snv_111b 64-bit
Copyright 1983-2009 Sun Microsystems, Inc.  All rights reserved.
Use is subject to license terms.
Hostname: opensolaris
Remounting root read/write
Probing for device nodes ...
Preparing live image for use

And again, system freeze, no cpu used, no messages. Nothing.

r...@vmhost:/home/xen# xm list
Name                                        ID   Mem VCPUs      State   Time(s)
Domain-0                                     0  1020    16     r-----    220.1
osol-0906-64-pv                              3  2048     1     -b----      9.5

Think I need help. HELP! :)

Also tried osol-0811 and osol-dev-130 without success.

Regards
Michael
-- 
This message posted from opensolaris.org
_______________________________________________
xen-discuss mailing list
[email protected]



      
_______________________________________________
xen-discuss mailing list
[email protected]

Reply via email to