Since I have a problem with another physical interface (link is down), I thought
I''d try to assign a logical interface to a Solaris PV guesst domain and
assign an IP.
''nge0:1:''
bash-3.2# ifconfig -a
lo0: flags=2001000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4,VIRTUAL> mtu 8232
index 1
inet 127.0.0.1 netmask ff000000
nge0: flags=201000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4,CoS> mtu 1500
index 2
inet 10.5.62.54 netmask fffff800 broadcast 10.5.63.255
ether 0:14:4f:2:12:34
nge0:1: flags=201000842<BROADCAST,RUNNING,MULTICAST,IPv4,CoS> mtu 1500
index 2
inet 10.5.63.98 netmask ff000000 broadcast 10.255.255.255
How can it be done? I did attempt but failed.
bash-3.2# uname -a
SunOS va64-x4200g-sca11 5.11 snv_80 i86pc i386 i86xpv
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''
#vif = [ ''ip=10.5.63.98'', ''bridge=nge0:1'' ]
bash-3.2#
bash-3.2# svccfg -s xvm/xend listprop | grep default
config/default-nic astring nge0:1
bash-3.2#
May be we can''t give logical interface to default-nic but I
couldn''t get it to work when I specified as ''bridge''
as well.
Thanks,
/Saurabh
This message posted from opensolaris.org
Saurabh Mishra wrote:> Since I have a problem with another physical interface (link is down), I thought I''d try to assign a logical interface to a Solaris PV guesst domain and assign an IP. > > ''nge0:1:''Logical interfaces cannot be used in this way. The VNIC implementation, which is the thing that opens the NIC you specify, expects to directly use a GLDv3 NIC. Logical interfaces are an IP layer concept. Can you explain the problem you see with a link that is down? dme.
Thanks. So how do we create a VNIC which can be used by guest domains?
Considering that my laptop has only one NIC, I would want to create a VNIC so
that guest operating system can share the same physical interface.
This is what I tried on a test lab machine which has more than one NIC.
bash-3.2# uname -a
SunOS va64-x4200g-sca11 5.11 snv_80 i86pc i386 i86xpv
bash-3.2# dladm show-dev
nge0 link: up speed: 1000Mb duplex: full
nge1 link: down speed: 0Mb duplex: unknown
e1000g0 link: down speed: 0Mb duplex: half
e1000g1 link: unknown speed: 0Mb duplex: half
vnic0 link: unknown speed: 0Mb duplex: unknown
bash-3.2# ifconfig nge1 plumb
bash-3.2# ifconfig nge1 up
bash-3.2# ifconfig -a
lo0: flags=2001000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4,VIRTUAL> mtu 8232
index 1
inet 127.0.0.1 netmask ff000000
nge0: flags=201000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4,CoS> mtu 1500
index 2
inet 10.5.62.54 netmask fffff800 broadcast 10.5.63.255
ether 0:14:4f:2:12:34
nge1: flags=201000803<UP,BROADCAST,MULTICAST,IPv4,CoS> mtu 1500 index 6
inet 0.0.0.0 netmask ff000000
ether 0:14:4f:2:12:35
lo0: flags=2002000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv6,VIRTUAL> mtu 8252
index 1
inet6 ::1/128
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''
vif = [ ''mac=0:14:4f:2:12:35'',
''ip=10.5.63.98'', ''bridge=nge1'' ]
bash-3.2# svccfg -s xvm/xend listprop | grep default
bash-3.2# xm create -c snv.1.boot.py
Using config file "./snv.1.boot.py".
Error:
bash-3.2#
Running Dtrace on VNIC routines :-
bash-3.2# dtrace -n vnic_dev_create:entry''{printf("%s",
stringof(args[1]))}'' -n
vnic_mac_open:return''{trace(arg1)}''
dtrace: description ''vnic_dev_create:entry'' matched 1 probe
dtrace: description ''vnic_mac_open:return'' matched 1 probe
Dec 18 09:41:17 va64-x4200g-sca11 syseventconfd[733]: process 7812 exited with
status 1
Dec 18 09:41:17 va64-x4200g-sca11 syseventconfd[733]: process 7820 exited with
status 1
CPU ID FUNCTION:NAME
3 2527 vnic_dev_create:entry nge1
3 2418 vnic_mac_open:return 0
Dec 18 09:41:27 va64-x4200g-sca11 syseventconfd[733]: process 7834 exited with
status 1
Dec 18 09:41:27 va64-x4200g-sca11 syseventconfd[733]: process 7835 exited with
status 1
As you can see, we were able to open the mac but perhaps failed with EPERM (1
errno).
Could that because nge1 has ''link down'' status (as shown by
dladm(1m))?
Thanks,
/Saurabh
This message posted from opensolaris.org
Saurabh Mishra wrote:> Thanks. So how do we create a VNIC which can be used by guest domains? Considering that my laptop has only one NIC, I would want to create a VNIC so that guest operating system can share the same physical interface.Both dom0 and the guest can share access to a single NIC. dom0 plumbs the NIC as usual - you shouldn''t need to change anything. The guest domain will have a VNIC created over that NIC by the domain creation tools. Does this not work? dme.
This is what I did as you suggested. I don''t see any interface for
guest domain.
bash-3.2# xm create -c snv.1.boot.py
Using config file "./snv.1.boot.py".
Started domain solaris-pv
v3.0.4-1-xvm chgset ''Tue Dec 04 09:56:10 2007 +0000
13231:406e2a7faf20''
SunOS Release 5.11 Version snv_79 64-bit
Copyright 1983-2007 Sun Microsystems, Inc. All rights reserved.
Use is subject to license terms.
Hostname: saurabh-snv
/dev/rdsk/c0d0s7 is clean
Reading ZFS config: done.
Dec 18 10:08:43 saurabh-snv sendmail[473]: My unqualified host name (localhost)
unknown; sleeping for retry
Dec 18 10:08:43 saurabh-snv sendmail[472]: My unqualified host name (localhost)
unknown; sleeping for retry
saurabh-snv console login: root
Password:
Last login: Mon Dec 17 14:44:21 on console
Dec 18 10:08:47 saurabh-snv login: ROOT LOGIN /dev/console
Sun Microsystems Inc. SunOS 5.11 snv_79 January 2008
# bash
bash-3.2# pwd
/
bash-3.2# uname -a
SunOS saurabh-snv 5.11 snv_79 i86pc i386 i86xpv
bash-3.2# dladm show-link
bash-3.2# dladm show-dev
bash-3.2# ifconfig -a
lo0: flags=2001000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4,VIRTUAL> mtu 8232
index 1
inet 127.0.0.1 netmask ff000000
lo0: flags=2002000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv6,VIRTUAL> mtu 8252
index 1
inet6 ::1/128
bash-3.2#
On side note, I have IP from a different subnet than where the machine is. Dom0
is in 62 subnet and the spare IP I have is from 63 subnet. Would changing
/etc/netmask of guest domain to 255.255.240.0 help route the packets?
/Saurabh
This message posted from opensolaris.org
Saurabh Mishra wrote:> This is what I did as you suggested. I don''t see any interface for guest domain. > > bash-3.2# xm create -c snv.1.boot.pyCan you show us the contents of snv.1.boot.py?> On side note, I have IP from a different subnet than where the machine is. Dom0 is in 62 subnet and the spare IP I have is from 63 subnet. Would changing /etc/netmask of guest domain to 255.255.240.0 help route the packets?That won''t work. Your NIC is connected to a particular network - you can''t just decide to start using addresses from a different network. dme.
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'' ] bash-3.2# /Saurabh /Saurabh This message posted from opensolaris.org
Michael Schuster
2007-Dec-18 21:14 UTC
Re: Logical interface for a Solaris PV guest domain
Saurabh Mishra wrote:> 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'' ]you need vif = [ '''' ] Michael -- Michael Schuster Recursion, n.: see ''Recursion''
It still didn''t work for me.
bash-3.2# xm create -c snv.1.boot.py
Using config file "./snv.1.boot.py".
Error:
bash-3.2# uname -a
SunOS va64-x4200g-sca11 5.11 snv_80 i86pc i386 i86xpv
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#
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
open64("/dev/xen/privcmd", O_RDWR) = 3
fcntl(3, F_GETFD, 0x00000053) = 0
fcntl(3, F_SETFD, 0x00000001) = 0
ioctl(3,
((''p''<<24)|(''r''<<16)|(''v''<<8)|0),
0x08046F7C) Err#79 EOVERFLOW
close(3) = 0
open64("/dev/xen/privcmd", O_RDWR) = 3
fcntl(3, F_GETFD, 0xFEF45449) = 0
fcntl(3, F_SETFD, 0x00000001) = 0
ioctl(3,
((''p''<<24)|(''r''<<16)|(''v''<<8)|0),
0x08046E6C) Err#79 EOVERFLOW
close(3) = 0
/Saurabh
This message posted from opensolaris.org
I''m trying to understand what works and what doesn''t. On Tue, Dec 18, 2007 at 01:07:42PM -0800, Saurabh Mishra wrote:> 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'' ] > bash-3.2#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.
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) = 0What 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.
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
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 is 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#
The same procedure works for s10u5 HVM domain (i.e when giving nge1). I can
plumb the interface and assign IP to s10u5 domain.
Thanks,
/Saurabh
This message posted from opensolaris.org
On Thu, Jan 03, 2008 at 05:54:16PM -0800, Saurabh Mishra wrote:> 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 is 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'' ]Whilst it''s commented out, this line is actually wrong. It says to assign three network interfaces to the guest. You want something more like: vif = [ ''mac=0:14:4f:2:12:35,ip=10.5.63.98,bridge=nge1'' ]> vif = [ '''' ] > bash-3.2# > > The same procedure works for s10u5 HVM domain (i.e when giving > nge1). I can plumb the interface and assign IP to s10u5 domain.After trying with the PV domain and "vif = ['''']", please put the contents of the logfiles in /var/log/xen somewhere that I can look at them. dme.
Here''s the log from /var/log/xen/xend.log when xm create was tried at
13.00 hours
bash-3.2# xm create -c snv.1.boot.py
Using config file "./snv.1.boot.py".
Error:
bash-3.2# date
Mon Jan 7 13:31:07 PST 2008
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''
##vif = [ ''mac=0:14:4f:2:12:35, ip=10.5.63.98, bridge=nge1'' ]
vif = [ '''' ]
[2008-01-07 10:35:20 xend 294] DEBUG (DevController:557) destroyCallback
/local/domain/2/device/vif/0 is destroyed
[2008-01-07 13:30:55 xend.XendDomainInfo 294] DEBUG (XendDomainInfo:94)
XendDomainInfo.create([''vm'', [''name'',
''solaris-pv''], [''memory'',
''1024''], [''on_poweroff'',
''destroy''], [''on_reboot'',
''restart''], [''on_crash'',
''preserve''], [''vcpus'', 4],
[''on_xend_start'', ''ignore''],
[''on_xend_stop'', ''shutdown''],
[''image'', [''linux'']],
[''device'', [''vbd'',
[''uname'', ''phy:/dev/zvol/dsk/snv-pool/vol''],
[''dev'', ''0''], [''mode'',
''w'']]], [''device'',
[''vif'']]])
[2008-01-07 13:30:55 xend.XendConfig 294] WARNING (XendConfig:612) Unconverted
key: cpus
[2008-01-07 13:30:55 xend.XendDomainInfo 294] DEBUG (XendDomainInfo:1320)
XendDomainInfo.constructDomain
[2008-01-07 13:30:55 xend.XendDomainInfo 294] DEBUG (XendDomainInfo:1366)
XendDomainInfo.initDomain: 3 256
[2008-01-07 13:30:55 xend 875] DEBUG (XendBootloader:70) Launching bootloader as
[''/usr/lib/xen/bin/pygrub'', ''-q'',
''--output=/var/run/xend/boot/xenbl.10158'',
''/dev/zvol/dsk/snv-pool/vol''].
[2008-01-07 13:30:55 xend 294] DEBUG (balloon:116) Balloon: 1049412 KiB free;
need 1048576; done.
[2008-01-07 13:30:55 xend 294] INFO (image:129) buildDomain os=linux dom=3
vcpus=4
[2008-01-07 13:30:55 xend 294] DEBUG (image:198) domid = 3
[2008-01-07 13:30:55 xend 294] DEBUG (image:199) memsize = 1024
[2008-01-07 13:30:55 xend 294] DEBUG (image:200) image =
/var/run/xend/boot/boot_kernel.GTtMsg
[2008-01-07 13:30:55 xend 294] DEBUG (image:201) store_evtchn = 1
[2008-01-07 13:30:55 xend 294] DEBUG (image:202) console_evtchn = 2
[2008-01-07 13:30:55 xend 294] DEBUG (image:203) cmdline =
/platform/i86xpv/kernel/amd64/unix
[2008-01-07 13:30:55 xend 294] DEBUG (image:204) ramdisk =
/var/run/xend/boot/boot_ramdisk.MtfIkM
[2008-01-07 13:30:55 xend 294] DEBUG (image:205) vcpus = 4
[2008-01-07 13:30:55 xend 294] DEBUG (image:206) features [2008-01-07
13:30:56 xend.XendDomainInfo 294] INFO (XendDomainInfo:1230) createDevice: vbd :
{''uname'': ''phy:/dev/zvol/dsk/snv-pool/vol'',
''driver'': ''paravirtualised'',
''mode'': ''w'', ''dev'':
''0'', ''uuid'':
''273bf24d-31bd-9d2e-39b7-d0dfd0b481ce''}
[2008-01-07 13:30:56 xend 294] DEBUG (DevController:116) DevController: writing
{''backend-id'': ''0'',
''virtual-device'': ''0'',
''device-type'': ''disk'',
''state'': ''1'', ''backend'':
''/local/domain/0/backend/vbd/3/0''} to
/local/domain/3/device/vbd/0.
[2008-01-07 13:30:56 xend 294] DEBUG (DevController:118) DevController: writing
{''domain'': ''solaris-pv'',
''frontend'': ''/local/domain/3/device/vbd/0'',
''uuid'':
''273bf24d-31bd-9d2e-39b7-d0dfd0b481ce'',
''dev'': ''0'', ''state'':
''1'', ''params'':
''/dev/zvol/dsk/snv-pool/vol'', ''mode'':
''w'', ''online'': ''1'',
''frontend-id'': ''3'',
''type'': ''phy''} to
/local/domain/0/backend/vbd/3/0.
[2008-01-07 13:30:56 xend.XendDomainInfo 294] INFO (XendDomainInfo:1230)
createDevice: vif : {''mac'':
''00:16:3e:65:3c:05'', ''uuid'':
''5e2e0503-8436-56f7-bf23-2324aa1e0dcb''}
[2008-01-07 13:30:56 xend 294] DEBUG (DevController:116) DevController: writing
{''backend-id'': ''0'', ''mac'':
''00:16:3e:65:3c:05'', ''handle'':
''0'', ''state'': ''1'',
''backend'':
''/local/domain/0/backend/vif/3/0''} to
/local/domain/3/device/vif/0.
[2008-01-07 13:30:56 xend 294] DEBUG (DevController:118) DevController: writing
{''domain'': ''solaris-pv'',
''handle'': ''0'', ''uuid'':
''5e2e0503-8436-56f7-bf23-2324aa1e0dcb'',
''script'': ''/usr/lib/xen/scripts/vif-vnic'',
''state'': ''1'', ''frontend'':
''/local/domain/3/device/vif/0'', ''mac'':
''00:16:3e:65:3c:05'', ''online'':
''1'', ''frontend-id'': ''3'',
''type'': ''SUNW_mac''} to
/local/domain/0/backend/vif/3/0.
[2008-01-07 13:30:56 xend.XendDomainInfo 294] DEBUG (XendDomainInfo:1750)
Storing VM details: {''on_xend_stop'':
''shutdown'', ''shadow_memory'':
''0'', ''uuid'':
''17115dd6-a1cb-2023-33ee-099f78fbdd26'',
''name'': ''solaris-pv'',
''on_reboot'': ''restart'',
''start_time'': ''1199741456.05'',
''on_poweroff'': ''destroy'',
''on_xend_start'': ''ignore'',
''on_crash'': ''preserve'',
''xend/restart_count'': ''0'',
''vcpus'': ''4'',
''vcpu_avail'': ''15'',
''memory'': ''1024'', ''image'':
''(linux (kernel ))'', ''maxmem'':
''1024''}
[2008-01-07 13:30:56 xend.XendDomainInfo 294] DEBUG (XendDomainInfo:757) Storing
domain details: {''console/ring-ref'':
''2023074'', ''console/port'':
''2'', ''cpu/3/availability'':
''online'', ''name'':
''solaris-pv'', ''console/limit'':
''1048576'', ''cpu/2/availability'':
''online'', ''vm'':
''/vm/17115dd6-a1cb-2023-33ee-099f78fbdd26'',
''domid'': ''3'',
''cpu/0/availability'': ''online'',
''memory/target'': ''1048576'',
''store/ring-ref'': ''2023075'',
''cpu/1/availability'': ''online'',
''store/port'': ''1''}
[2008-01-07 13:30:56 xend 294] DEBUG (XendDomain:431) Adding Domain: 3
[2008-01-07 13:30:56 xend.XendDomainInfo 294] DEBUG (XendDomainInfo:824)
XendDomainInfo.handleShutdownWatch
[2008-01-07 13:30:56 xend 294] DEBUG (DevController:149) Waiting for devices
vif.
[2008-01-07 13:30:56 xend 294] DEBUG (DevController:154) Waiting for 0.
[2008-01-07 13:30:56 xend 294] DEBUG (DevController:561) hotplugStatusCallback
/local/domain/0/backend/vif/3/0/hotplug-status.
[2008-01-07 13:30:56 xend 294] DEBUG (DevController:575) hotplugStatusCallback
2.
[2008-01-07 13:30:56 xend 294] DEBUG (DevController:549) destroyCallback
/local/domain/3/device/vif/0.
[2008-01-07 13:31:06 xend 294] ERROR (xmlrpclib2:218)
Traceback (most recent call last):
File "/usr/lib/python2.4/site-packages/xen/util/xmlrpclib2.py", line
197, in _marshaled_dispatch
File "/usr/lib/python2.4/SimpleXMLRPCServer.py", line 406, in
_dispatch
return func(*params)
File "<string>", line 1, in <lambda>
File
"/usr/lib/python2.4/site-packages/xen/xend/server/XMLRPCServer.py",
line 52, in dispatch
File "/usr/lib/python2.4/site-packages/xen/xend/XendDomainInfo.py",
line 518, in waitForDevices
File
"/usr/lib/python2.4/site-packages/xen/xend/server/DevController.py",
line 150, in waitForDevices
File
"/usr/lib/python2.4/site-packages/xen/xend/server/DevController.py",
line 165, in waitForDevice
File
"/usr/lib/python2.4/site-packages/xen/xend/server/DevController.py",
line 237, in destroyDevice
EnvironmentError
[2008-01-07 13:31:06 xend.XendDomainInfo 294] DEBUG (XendDomainInfo:1519)
XendDomainInfo.destroy: domid=3
[2008-01-07 13:31:06 xend.XendDomainInfo 294] DEBUG (XendDomainInfo:1527)
XendDomainInfo.destroyDomain(3)
[2008-01-07 13:31:06 xend 294] DEBUG (DevController:549) destroyCallback
/local/domain/3/device/vif/0.
[2008-01-07 13:31:06 xend 294] DEBUG (DevController:557) destroyCallback
/local/domain/3/device/vif/0 is destroyed
bash-3.2#
/Saurabh
This message posted from opensolaris.org