Hi!
I've Nevada build 77 running on xVM Hypervisor with Nevada as Dom0.
# 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 : 1
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
With valued assistance from Moinak Ghosh, I manage to create a properly
running Windows DomU.
# virsh dumpxml winxp1
<domain type='xen' id='8'>
<name>winxp1</name>
<uuid>a3011e029cde5c88bb74c6a160dd727e</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>
# xm list
Name ID Mem VCPUs State
Time(s)
Domain-0 0 2948 4 r----- 2694.8
winxp1 8 1064 1 -b---- 484.3
I eventually shutdown my computer and when I re-started it hours later,
xm list showed no winxp1 DomU!
!!!!!!
Is this normal??
I then re-created the DomU from scratch. And then I noticed something
else...
Everytime I "shutdown" my Windows DomU I noticed the relevant entry
disappears from xm list!!!!!
I can get back the previous state by doing
#xm create -c -f /export/home/admin/iso-images/xp2/winxp2.py
But is this the correct way?
Should it be
#xm start winxp1
Something is wrong here..
I had thought it would be like Solaris Zones....the zone is reflected
even when shutdown using zoneadm...
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
