Hi All;
I have receive quite a lot of very valuable assistance in this mailing
list and I thought of giving something back.
I have setup the Nevada build 77 running on xVM Hypervisor. It works.
# uname -a
SunOS solaris-devx 5.11 snv_77 i86pc i386 i86xpv
The H/W is an Intel Core2 Quad CP (2.4 Ghz) with 4 Gbyte RAM and 4 x 320
Mbyte eSATA hard disks. The motherboard is a Gigabyte DS3 with Intel VT
support turned on.
# xm info
host : solaris-devx
release : 5.11
version : snv_77
machine : i86pc
nr_cpus : 4
nr_nodes : 1
sockets_per_node : 1
cores_per_socket : 4
threads_per_core : 1
cpu_mhz : 2400
hw_caps :
bfebfbff:20100800:00000000:00000140:0000e3bd:00000000:00000001
total_memory : 4094
free_memory : 784
xen_major : 3
xen_minor : 0
xen_extra : .4-1-xvm
xen_caps : xen-3.0-x86_64 hvm-3.0-x86_32 hvm-3.0-x86_32p
hvm-3.0-x86_64
xen_pagesize : 4096
platform_params : virt_start=0xffff800000000000
xen_changeset : Mon Oct 29 23:19:32 2007 -0700 13226:b0c4d9d28fee
cc_compiler : gcc version 3.4.3 (csl-sol210-3_4-20050802)
cc_compile_by : xen-discuss
cc_compile_domain : opensolaris.org
cc_compile_date : Mon Oct 29 23:20:11 PDT 2007
xend_config_format : 3
# prtdiag
System Configuration: Gigabyte Technology Co., Ltd. P35-DS3
BIOS Configuration: Award Software International, Inc. F5 08/13/2007
==== Processor Sockets ====================================
Version Location Tag
-------------------------------- --------------------------
Intel(R) Core(TM)2 Quad CP Socket 775
==== Memory Device Sockets ================================
Type Status Set Device Locator Bank Locator
------- ------ --- ------------------- --------------------
unknown in use 0 A0 Bank0/1
unknown in use 0 A1 Bank2/3
unknown in use 0 A2 Bank4/5
unknown in use 0 A3 Bank6/7
==== On-Board Devices =====================================
==== Upgradeable Slots ====================================
ID Status Type Description
--- --------- ---------------- ----------------------------
0 available PCI PCI
1 available PCI PCI
2 available PCI PCI
0 available PCI PCI
I've tried Windoze and very much thanks to Moinak Ghosh and friends I
have now gotten Windoze running as a DomU.
Thanks to John Levon for his pointer to use "xm new" instead of "xm create"
From John's email, I gather that the xm create / xm new sub commands
would be deprecated soon and that the recommended method for creation a
DomU would be to use virt-install.
But virt-install did not allow me to further customize the DomU
configuration so I went back to the Python script. For anybody who is
interested, the script is shown below..
# cat winxp2.py
kernel = "/usr/lib/xen/boot/hvmloader"
builder='hvm'
name = "winxp1"
vcpus = 1
memory = 1056
shadow_memory = 8
kernel = '/usr/lib/xen/boot/hvmloader'
builder = 'hvm'
vif = [ 'mac=00:16:3e:1b:f1:92,type=ioemu' ]
disk = ['file:/export/home/hvm1/windoze-raw,hdc,w',
'file:/export/home/admin/iso-images/xp2/e-xp2ja2k7.iso,hda:cdrom,r']
sdl = 0
vnc = 5900
vncconsole = 1
vnclisten="0.0.0.0"
boot = 'd'
on_shutdown = "destroy"
on_reboot = "restart"
on_crash = "restart"
device_model = '/usr/lib/xen/bin/qemu-dm'
usb=1
usbdevice='tablet'
serial='null'
soundhw='sb16'
XML dump...
# virsh dumpxml winxp1
<domain type='xen' id='9'>
<name>winxp1</name>
<uuid>90f32adda19bfcc29e350ceb32fff057</uuid>
<os>
<type>hvm</type>
<loader>/usr/lib/xen/boot/hvmloader</loader>
<boot dev='cdrom'/>
</os>
<memory>1097728</memory>
<currentMemory>1081344</currentMemory>
<vcpu>1</vcpu>
<on_poweroff>destroy</on_poweroff>
<on_reboot>restart</on_reboot>
<on_crash>restart</on_crash>
<features>
<acpi/>
<apic/>
<pae/>
</features>
<devices>
<emulator>/usr/lib/xen/bin/qemu-dm</emulator>
<interface type='ethernet'>
<mac address='00:16:3e:1b:f1:92'/>
</interface>
<disk type='file' device='disk'>
<driver name='file'/>
<source file='/export/home/hvm1/windoze-raw'/>
<target dev='hdc'/>
</disk>
<disk type='file' device='cdrom'>
<driver name='file'/>
<source file='/export/home/admin/iso-images/xp2/e-xp2ja2k7.iso'/>
<target dev='hda'/>
<readonly/>
</disk>
</devices>
</domain>
I was wondering whether we could have the <> tag syntax?? The XML DTD
perhaps?
I've also tested the follow OS but they didn't quite work out....nothing
on vncviewer, just a blank screen.
Fedora8
CentOS
CentOS actually gave me the initial linux boot up screen. However, after
typing "linux text" for the installation, vmlinuz loaded and...the DomU
then rebooted and went back to the original screen once more.
The following virt-install syntax was used..
#virt-install --name=fedora8 --ram 768 --cdrom
//export/home/admin/iso-images/Fedora8/Fedora-8-i386-DVD.iso
--os-type=linux --os-variant=fedora6 --file
/dev/zvol/dsk/datahome/fedora8 --vnc
Attempt to create with the -nographics option also failed with the
following error...
#virt-install --name=fedora8 --ram 768 --cdrom
//export/home/admin/iso-images/Fedora8/Fedora-8-i386-DVD.iso
--os-type=linux --os-variant=fedora6 --file
/dev/zvol/dsk/datahome/fedora8 --nographics
Would you like a fully virtualized guest (yes or no)? This will allow
you to run unmodified operating systems. yes
Starting install...
Creating domain... 0 B
00:06
Domain installation still in progress. You can reconnect
to the console to complete the installation process.
**** Attempt to console in failed as follows *********
# xm console fedora8
/usr/lib/xen/bin/xenconsole: Could not read tty from store: No such file
or directory
**** new Fedora DomU reflected in xm list ****************
# xm list
Name ID Mem VCPUs State
Time(s)
Domain-0 0 2165 4 r----- 14503.7
fedora8 15 768 1 ------ 0.0
winxp1 9 1064 1 -b---- 8139.2
**** so I destroyed and delete the new Domu ************
# xm destroy fedora8
# xm delete fedora8
I'm going to create a DomU for Solaris 10 Update 4 (8/07) soon. I will
report to this list the outcome if people are interested.
But Windoze works just fine. Irony huh?
Warmest Regards
Steven Sim
Fujitsu Asia Pte. Ltd.
_____________________________________________________
This e-mail is confidential and may also be privileged. If you are not the
intended recipient, please notify us immediately. You should not copy or use it
for any purpose, nor disclose its contents to any other person.
Opinions, conclusions and other information in this message that do not relate
to the official business of my firm shall be understood as neither given nor
endorsed by it.
_______________________________________________
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org
