> Folks: > I am unable to get my opensolaris sn-b85 domU to > start up in an > opensolaris sn-b85 dom0. I am booted to xvm. Other > systems, such as > Fedora 8, WinXP Pro, W2k3 server, W2k8 server and > Windows Vista startup > normally. > > I have used the following to build the domU: > > # mkfile -n 25g /solhvm/solhvm.img > # ls -l /solhvm > total 269 > -rw------T 1 root root 26843545600 Jul 7 > 10:37 solhvm.img > # # virt-install > Would you like a fully virtualized guest (yes or no)? > This will allow > ou to run unmodified operating systems. yes > What is the name of your virtual machine? solhvm > How much RAM should be allocated (in megabytes)? 1024 > What would you like to use as the disk (path)? > /solhvm/solhvm.img > Would you like to enable graphics support? (yes or > no) yes > What would you like to use for the virtual CD image? > /isos/solb85.iso > > > Starting install... > libvir: Xen Daemon error : GET operation failed: > libvir: Xen Daemon error : GET operation failed: > Creating domain... > 0 B > lt Mar 3 2008 20:21:29 > Copyright (C) 2002-2005 RealVNC Ltd. > See http://www.realvnc.com for information on VNC. > > Mon Jul 7 10:42:19 2008 > CConn: connected to host 127.0.0.1 port 5900 > CConnection: Server supports RFB protocol version 3.3 > CConnection: Using RFB protocol version 3.3 > Mon Jul 7 10:42:25 2008 > TXImage: Using default colormap and visual, > TrueColor, depth 24. > CConn: Using pixel format depth 6 (8bpp) rgb222 > CConn: Using ZRLE encoding > Mon Jul 7 10:42:26 2008 > CConn: Throughput 20000 kbit/s - changing to > hextile encoding > CConn: Throughput 20000 kbit/s - changing to > full colour > CConn: Using pixel format depth 24 (32bpp) > little-endian rgb888 > CConn: Using hextile encoding > > .... > > Everything progresses as expected during the install > and the install > completes normally. After installation, I am using > the following syntax *********************************************** After install completed run :- # xm list It should report "solhvm" on the list. Then try :- # xm start solhvm When returned to command prompt issue:- # vncviewer localhost:0 I would wonder how it works ? ***********************************************
> from a python file to start up the domU: > > # cat solhvm.py > name = "solhvm" > vcpus = 1 > memory = "768" > root = "/dev/dsk/c0d0s0" > disk = ['file:/solhvm/solhvm.img,0,w'] > vif = [ '' ] > on_shutdown = 'destroy' > on_reboot = 'restart' > on_crash = 'destroy' > > # xm new -f solhvm.py > Using config file "./solhvm.py". > # virsh start solhvm > Domain solhvm started > > # virsh console solhvm > v3.1.2-xvm chgset 'Mon Mar 03 23:05:33 2008 -0800 > 15630:a1a16c966b70' > SunOS Release 5.11 Version snv_85 64-bit > Copyright 1983-2008 Sun Microsystems, Inc. All > rights reserved. > Use is subject to license terms. > Failed to plumb IPv4 interface(s): rtls0 > The / file system (/dev/rdsk/c0d0s0) is being > checked. > > WARNING - Unable to repair the / filesystem. Run fsck > manually (fsck -F ufs /dev/rdsk/c0d0s0). > > Jul 7 13:45:15 svc.startd[7]: > svc:/system/filesystem/usr:default: > Method "/lib/svc/method/fs-usr" failed with exit > status 95. > Jul 7 13:45:15 svc.startd[7]: > system/filesystem/usr:default failed > fatally: transitioned to maintenance (see 'svcs -xv' > for details) > Requesting System Maintenance Mode > (See /lib/svc/share/README for more information.) > Console login service(s) cannot run > > Root password for system maintenance (control-d to > bypass): Jul 7 > 13:45:15 svc.startd[7]: > svc:/network/physical:default: Method > "/lib/svc/method/net-physical" failed with exit > status 96. > Jul 7 13:45:15 svc.startd[7]: > network/physical:default misconfigured: > transitioned to maintenance (see 'svcs -xv' for > details) > Hostname: solhvm > single-user privilege assigned to /dev/console. > Entering System Maintenance Mode > > Jul 7 13:46:26 su: 'su root' succeeded for LOGIN on > /dev/console > Sun Microsystems Inc. SunOS 5.11 snv_85 > January 2008 > format > earching for disks...done > No disks found! > > # > > .... > > Could someone give me a hint as to why the boot > loader can't find the disk? > > Thanks > Don > _______________________________________________ > xen-discuss mailing list > [email protected] This message posted from opensolaris.org _______________________________________________ xen-discuss mailing list [email protected]
