Captain Jack
星期一 四月 23, 2007
Started to work with Xen
1. Currently there is a bug so I can't specify a vif for domu now.2. User can have multiple console in the same time by xm console, I'm not sure if this is intended.
3. Found a bug if there is no entry in /etc/name_to_major for 'vdb' then the dom0 will panic after a while from 'xm create -c .....'. Max is fixing it.
4. After the first installation, domU used to reboot and then the installation starts over. This is harmless anyway but annoying.
5. Hit 6300863 while domU starting up.
--------------------------- root@dmgdom0xen:/$ xm console 11 SunOS Release 5.11 Version matrix-build-2007-04-19 64-bit Copyright 1983-2007 Sun Microsystems, Inc. All rights reserved. Use is subject to license terms. Hostname: dmgdomu0xen /dev/rdsk/c0d0s6 is clean /dev/rdsk/c0d0s3 is clean /dev/rdsk/c0d0s4 is clean t_optmgmt: System error: Cannot assign requested address Starting Solaris Install Launcher in Command Line Mode. Apr 23 01:43:49 dmgdomu0xen sendmail[486]: My unqualified host name (localhost) unknown; sleeping for retry Apr 23 01:43:49 dmgdomu0xen sendmail[485]: My unqualified host name (localhost) unknown; sleeping for retry Exiting launcher. File find_device.out does not exist. The Solaris Install Launcher has terminated unexpectedly. Press the Return key and a system reboot will take place on your machine.Apr 23 01:44:49 dmgdomu0xen sendmail[486]: unable to qualify my own domain name (localhost) -- using short name Apr 23 01:44:49 dmgdomu0xen sendmail[485]: unable to qualify my own domain name (localhost) -- using short name ----------------------------------
Seems this is an unsolved issue and a workaround is add -text to grub. However, how to specify kernel arguments for domU? hm...
Posted at 12:20上午 四月 23, 2007 by jackmeng in Tech@Sun | 评论[2]
Subscribe!
you say that "4. After the first installation, domU used to reboot and then the installation starts over. This is harmless anyway but annoying. ", how did you over come this? i get it every time i reboot the domU and its getting more than annoying right now.
i'm creating a .img file for the domU to boot within and it installs (slowly), does my create.py need to be called with additional params? would it be possible to see your running config?
Also, have you tried jumpstart installs with them yet?
probably dumb questions, but any help would be greatly appreciated....
thanks
Martin
发表于 Martin Baxter 在 2007年04月30日, 07:31 上午 GMT-08:00 #
I used 'xm destroy' to destroy the domU which doing installation. And then scecify another profile to start the GuestOS which was just installed. However, I haven't tried jumpstart yet...
Profile for installation:
-----------
name = "solaris-install"
memory = "2048"
disk = [ 'file:/xen/iso/63-0426-nd.iso,6:cdrom,r', 'phy:/dev/dsk/c1t0d0s5,0,w' ]
#sxc16's MAC
vif = [ 'mac=00:14:4f:47:da:7a' ]
-----------
Profile for the GuestOS:
-----------
name = "dom0"
memory = "1024"
vcpus = 2
root = "/dev/dsk/c0d0s0"
disk = [ 'phy:/dev/dsk/c1t0d0s5,0,w' ]
#dom0's MAC
vif = [ 'mac=00:14:4f:47:da:7a' ]
-----------
发表于 Jack 在 2007年08月06日, 07:17 下午 GMT-08:00 #