Here's the output :-
bash-3.2# pkginfo -l SUNWxvmhvm
PKGINST: SUNWxvmhvm
NAME: Hypervisor HVM
CATEGORY: system
ARCH: i386
VERSION: 11.11,REV=2007.09.18.17.34
BASEDIR: /
VENDOR: Sun Microsystems, Inc.
DESC: Hypervisor HVM support
PSTAMP: elpaso20071210232555
INSTDATE: Dec 11 2007 20:17
HOTLINE: Please contact your local service provider
STATUS: completely installed
FILES: 50 installed pathnames
7 shared pathnames
1 linked files
11 directories
3 executables
6562 blocks used (approx)
bash-3.2# xm info
host : va64-x4200g-sca11
release : 5.11
version : snv_80
machine : i86pc
nr_cpus : 4
nr_nodes : 1
sockets_per_node : 2
cores_per_socket : 2
threads_per_core : 1
cpu_mhz : 2393
hw_caps :
178bfbff:ebd3fbff:00000000:00000010:00002001:00000000:0000001f
total_memory : 8191
free_memory : 4153
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 : Tue Dec 04 09:56:10 2007 +0000 13231:406e2a7faf20
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 Dec 10 23:12:59 PST 2007
xend_config_format : 3
bash-3.2# isainfo -v
64-bit amd64 applications
ahf cx16 sse3 sse2 sse fxsr amd_3dnowx amd_3dnow amd_mmx mmx
cmov cx8
tsc fpu
32-bit i386 applications
ahf cx16 sse3 sse2 sse fxsr amd_3dnowx amd_3dnow amd_mmx mmx
cmov cx8
tsc fpu
bash-3.2#
All I did was 'xm create <.py file>'.
> I understood you to say that using this configuration file you can
> boot the guest domain and that it has no network interface. Is that
> right? It's what we would expect - you don't ask for a network device
> to be present (as Michael indicated earlier).
>
> When you add:
> vif = ['']
> you showed some output which indicated that the domain didn't even
> start. Is that right?
>
> dme.
When I add 'vif = [''] in the .pf file, xm create failed and I couldn't
even boot the domain.
If I don't give 'vif = ['']' in .py file, then domain boots but does not
see VNIC interface via dladm.
bash-3.2# xm create -c snv.1.boot.py
Using config file "./snv.1.boot.py".
Error:
bash-3.2#
As you can see, there are no error message being communicated back to user.
bash-3.2# cat snv.1.boot.py
name = 'solaris-pv'
memory = '1024'
vcpus = 4
disk = [ 'phy:/dev/zvol/dsk/snv-pool/vol,0,w' ]
on_poweroff = 'destroy'
on_reboot = 'restart'
on_crash = 'preserve'
# Commenting it out
#vif = [ 'mac=0:14:4f:2:12:35', 'ip=10.5.63.98', 'bridge=nge1' ]
vif = [ '' ]
bash-3.2#
Thanks,
/Saurabh
David Edmondson wrote:
> On Tue, Dec 18, 2007 at 01:27:51PM -0800, Saurabh Mishra wrote:
>> open64("/dev/xen/privcmd", O_RDWR) = 3
>> fcntl(3, F_GETFD, 0x08046FBC) = 0
>> fcntl(3, F_SETFD, 0x00000001) = 0
>> ioctl(3, (('p'<<24)|('r'<<16)|('v'<<8)|0), 0x08046F7C) Err#79 EOVERFLOW
>> close(3) = 0
>
> What software are you running on this system?
>
> The privcmd driver returns EOVERFLOW for ioctl() calls if the data
> model of the calling application differs from that of the kernel
> (i.e. 32 bit application on 64 bit kernel). The user-level hypervisor
> control tools need to match the kernel.
>
> dme.
--
/Saurabh
http://blogs.sun.com/saurabh_mishra
_______________________________________________
xen-discuss mailing list
[email protected]
