Hi folks,
I''ve built a domain 0 for the xVM built for the developing code
(downloaded two weeks ago, not sure if it is the latest code). xVM
hypervisor and domain 0 work well. However, when I tried to start a PV
domain with "virsh start" command. The command failed with the
following information.
This is what I''ve typed:
***************************************************
# virsh
Using new hypervisor call: 30003
Welcome to virsh, the virtualization interactive terminal.
Type: ''help'' for help with commands
''quit'' to quit
virsh # start pv_snv_100
libvir: Xen Daemon error : POST operation failed: (xend.err "Boot
loader didn''t return any data!")
error: Failed to start domain pv_snv_100
***************************************************
This is what I got from /var/adm/message during above operation:
***************************************************
[allen@blu-wbg:~]tail -f /var/adm/messages
Oct 24 12:36:03 blu-wbg privcmd: [ID 388104 kern.notice] unrecognized
HYPERVISOR_platform_op 38
Oct 24 12:36:14 blu-wbg xpvd: [ID 395608 kern.info] balloon@0, balloon0
Oct 24 12:36:14 blu-wbg genunix: [ID 936769 kern.info] balloon0 is
/xpvd/balloon@0
***************************************************
The first line displayed when "virsh" executed. And the next two lines
were during "start pv_snv_100". pv_snv_100 is a domain name for a PV
guest. It was installed before upgrading to the latest xVM binaries.
virsh-install can''t install a guest after upgrading.
***************************************************
[allen@blu-wbg:~]sudo virt-install
libvirt_virConnectPtrWrap: node = 83ed000
libvirt_xmlcharPtrWrap: str = Xen
libvirt_xmlcharPtrWrap: str = Xen
libvirt_virConnectPtrWrap: node = 8117948
libvirt_xmlcharPtrWrap: str = <capabilities>
<host>
<cpu>
<arch>i86pc</arch>
<features>
<vmx/>
<pae/>
</features>
</cpu>
<migration_features>
<live/>
<uri_transports>
<uri_transport>xenmigr</uri_transport>
</uri_transports>
</migration_features>
</host>
</capabilities>
libvirt_intWrap: val = 0
Would you like a fully virtualized guest (yes or no)? This will allow
you to run unmodified operating systems. yes
libvirt_virConnectPtrWrap: node = 8117948
libvirt_xmlcharPtrWrap: str = <capabilities>
<host>
<cpu>
<arch>i86pc</arch>
<features>
<vmx/>
<pae/>
</features>
</cpu>
<migration_features>
<live/>
<uri_transports>
<uri_transport>xenmigr</uri_transport>
</uri_transports>
</migration_features>
</host>
</capabilities>
libvirt_intWrap: val = 0
What is the name of your virtual machine? hvm_snv_100
How much RAM should be allocated (in megabytes)? 1024
What would you like to use as the disk (path)? /dev/dsk/c1d0s0
libvirt_intWrap: val = 0
libvirt_virDomainPtrWrap: node = 83dd7c0
libvirt_xmlcharPtrWrap: str = pv_snv_100
libvirt_virDomainPtrWrap: node = 8319398
libvirt_xmlcharPtrWrap: str = <domain type=''xen''
id=''0''>
<name>Domain-0</name>
<uuid>00000000-0000-0000-0000-000000000000</uuid>
<bootloader/>
<memory>1880064</memory>
<vcpu>2</vcpu>
<on_poweroff>destroy</on_poweroff>
<on_reboot>restart</on_reboot>
<on_crash>restart</on_crash>
<devices>
</devices>
</domain>
libvirt_xmlcharPtrWrap: str = <domain type=''xen''
id=''-1''>
<name>pv_snv_100</name>
<uuid>7bebdae1-9709-dafb-8b39-b9004cb5a2ce</uuid>
<bootloader>/usr/lib/xen/bin/pygrub</bootloader>
<os>
<type>linux</type>
</os>
<memory>1048576</memory>
<vcpu>1</vcpu>
<on_poweroff>destroy</on_poweroff>
<on_reboot>restart</on_reboot>
<on_crash>restart</on_crash>
<devices>
<interface type=''ethernet''>
<target dev=''vif-1.0''/>
<mac address=''00:16:3e:0a:13:e0''/>
<script path=''vif-vnic''/>
</interface>
<disk type=''block'' device=''disk''>
<driver name=''phy''/>
<source dev=''/dev/dsk/c1d0s0''/>
<target dev=''xvda''/>
</disk>
</devices>
</domain>
libvirt_intWrap: val = 0
libvirt_intWrap: val = 0
Disk /dev/dsk/c1d0s0 is already in use by another guest! Do you
really want to use the disk (yes or no)? yes
Would you like to enable graphics support? (yes or no) yes
What would you like to use for the virtual CD image?
/export/home/allen/Download/sol-11-x86-snv-100.iso
Starting install...
libvir: Xen Daemon error : GET operation failed:
libvirt_virDomainPtrWrap: node = 0
libvirt_xmlcharPtrWrap: str = GET operation failed:
libvirt_xmlcharPtrWrap: str = GET operation failed: %s
libvirt_xmlcharPtrWrap: str libvir: Xen Daemon error : GET operation failed:
libvirt_virDomainPtrWrap: node = 0
libvirt_xmlcharPtrWrap: str = GET operation failed:
libvirt_xmlcharPtrWrap: str = GET operation failed: %s
libvirt_xmlcharPtrWrap: str libvirt_intWrap: val = 0
libvirt_virDomainPtrWrap: node = 8319398
libvirt_xmlcharPtrWrap: str = pv_snv_100
libvirt_virDomainPtrWrap: node = 83657f0
libvirt_xmlcharPtrWrap: str = <domain type=''xen''
id=''0''>
<name>Domain-0</name>
<uuid>00000000-0000-0000-0000-000000000000</uuid>
<bootloader/>
<memory>1880064</memory>
<vcpu>2</vcpu>
<on_poweroff>destroy</on_poweroff>
<on_reboot>restart</on_reboot>
<on_crash>restart</on_crash>
<devices>
</devices>
</domain>
libvirt_intWrap: val = 0
libvirt_intWrap: val = 0
libvir: Xen Daemon error : POST operation failed: (xend.err ''Error
creating domain: HVM guest support is unavailable: is VT/AMD-V
supported by your CPU and enabled in your BIOS?'')
libvirt_virDomainPtrWrap: node = 0
libvirt_xmlcharPtrWrap: str = POST operation failed: (xend.err ''Error
creating domain: HVM guest support is unavailable: is VT/AMD-V
supported by your CPU and enabled in your BIOS?'')
libvirt_xmlcharPtrWrap: str = POST operation failed: %s
libvirt_xmlcharPtrWrap: str = (xend.err ''Error creating domain: HVM
guest support is unavailable: is VT/AMD-V supported by your CPU and
enabled in your BIOS?'')
Traceback (most recent call last):
File "/usr/bin/virt-install", line 657, in ?
main()
File "/usr/bin/virt-install", line 606, in main
dom = guest.start_install(conscb,progresscb)
File
"/export/home/allen/Download/xvm-gate///proto/install/usr/lib/python2.4/site-packages/virtinst/Guest.py",
line 638, in start_install
File
"/export/home/allen/Download/xvm-gate///proto/install/usr/lib/python2.4/site-packages/virtinst/Guest.py",
line 655, in _do_install
File "/usr/lib/python2.4/vendor-packages/libvirt.py", line 585, in
createLinux
if ret is None:raise libvirtError(''virDomainCreateLinux()
failed'',
conn=self)
libvirt.libvirtError: virDomainCreateLinux() failed POST operation
failed: (xend.err ''Error creating domain: HVM guest support is
unavailable: is VT/AMD-V supported by your CPU and enabled in your
BIOS?'')
libvirt_intWrap: val = 0
***************************************************
I am very appreciated for your suggestions and tips.
Thanks,
-Baolu
More information.
I disabled the Intel vt-d in BIOS setup and tried to install another
snv_100 PV guest. The installation failed with domain 0 panic''ing and
rebooting.
Below is the domain 0 panic information:
Oct 24 13:17:02 blu-wbg privcmd: unrecognized HYPERVISOR_platform_op 38
Oct 24 13:23:49 blu-wbg last message repeated 2 times
Oct 24 13:25:38 blu-wbg syseventconfd[101290]: process 101301 exited
with status 1
panic[cpu1]/thread=ffffff013572e8c0: xen_xlate_errcode: unknown error -11
ffffff0004e72c10 unix:xen_xlate_errcode+ea ()
ffffff0004e72c80 privcmd:do_privcmd_hypercall+1cc ()
ffffff0004e72cf0 privcmd:privcmd_ioctl+79 ()
ffffff0004e72d30 genunix:cdev_ioctl+4b ()
ffffff0004e72d70 specfs:spec_ioctl+89 ()
ffffff0004e72df0 genunix:fop_ioctl+81 ()
ffffff0004e72ef0 genunix:ioctl+191 ()
ffffff0004e72f00 unix:brand_sys_syscall+408 ()
syncing file systems... 6 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1
done (not all i/o completed)
dumping to /dev/dsk/c0d0s1, offset 429391872, content: kernel
100% done: 158623 pages dumped, compression ratio 3.95, dump succeeded
rebooting...
Below is virt-install input/output:
[allen@blu-wbg:~]sudo virt-install
libvirt_virConnectPtrWrap: node = 83ed000
libvirt_xmlcharPtrWrap: str = Xen
libvirt_xmlcharPtrWrap: str = Xen
libvirt_virConnectPtrWrap: node = 8117948
libvirt_xmlcharPtrWrap: str = <capabilities>
<host>
<cpu>
<arch>i86pc</arch>
<features>
<vmx/>
<pae/>
</features>
</cpu>
<migration_features>
<live/>
<uri_transports>
<uri_transport>xenmigr</uri_transport>
</uri_transports>
</migration_features>
</host>
</capabilities>
libvirt_intWrap: val = 0
Would you like a fully virtualized guest (yes or no)? This will allow
you to run unmodified operating systems. no
What is the name of your virtual machine? pv_snv_100_1
How much RAM should be allocated (in megabytes)? 1024
What would you like to use as the disk (path)? /dev/dsk/c1d0s0
libvirt_intWrap: val = 0
libvirt_virDomainPtrWrap: node = 83dd7c0
libvirt_xmlcharPtrWrap: str = pv_snv_100
libvirt_virDomainPtrWrap: node = 8319398
libvirt_xmlcharPtrWrap: str = <domain type=''xen''
id=''0''>
<name>Domain-0</name>
<uuid>00000000-0000-0000-0000-000000000000</uuid>
<bootloader/>
<memory>1885184</memory>
<vcpu>2</vcpu>
<on_poweroff>destroy</on_poweroff>
<on_reboot>restart</on_reboot>
<on_crash>restart</on_crash>
<devices>
</devices>
</domain>
libvirt_xmlcharPtrWrap: str = <domain type=''xen''
id=''-1''>
<name>pv_snv_100</name>
<uuid>7bebdae1-9709-dafb-8b39-b9004cb5a2ce</uuid>
<bootloader>/usr/lib/xen/bin/pygrub</bootloader>
<os>
<type>linux</type>
</os>
<memory>1048576</memory>
<vcpu>1</vcpu>
<on_poweroff>destroy</on_poweroff>
<on_reboot>restart</on_reboot>
<on_crash>restart</on_crash>
<devices>
<interface type=''ethernet''>
<target dev=''vif-1.0''/>
<mac address=''00:16:3e:0a:13:e0''/>
<script path=''vif-vnic''/>
</interface>
<disk type=''block'' device=''disk''>
<driver name=''phy''/>
<source dev=''/dev/dsk/c1d0s0''/>
<target dev=''xvda''/>
</disk>
</devices>
</domain>
libvirt_intWrap: val = 0
libvirt_intWrap: val = 0
Disk /dev/dsk/c1d0s0 is already in use by another guest! Do you
really want to use the disk (yes or no)? yes
Would you like to enable graphics support? (yes or no) no
What is the install location?
/export/home/allen/Download/sol-11-x86-snv-100.iso
Starting install...
libvir: Xen Daemon error : GET operation failed:
libvirt_virDomainPtrWrap: node = 0
libvirt_xmlcharPtrWrap: str = GET operation failed:
libvirt_xmlcharPtrWrap: str = GET operation failed: %s
libvirt_xmlcharPtrWrap: str libvir: Xen Daemon error : GET operation failed:
libvirt_virDomainPtrWrap: node = 0
libvirt_xmlcharPtrWrap: str = GET operation failed:
libvirt_xmlcharPtrWrap: str = GET operation failed: %s
libvirt_xmlcharPtrWrap: str libvirt_intWrap: val = 0
libvirt_virDomainPtrWrap: node = 8319398
libvirt_xmlcharPtrWrap: str = pv_snv_100
libvirt_virDomainPtrWrap: node = 83657f0
libvirt_xmlcharPtrWrap: str = <domain type=''xen''
id=''0''>
<name>Domain-0</name>
<uuid>00000000-0000-0000-0000-000000000000</uuid>
<bootloader/>
<memory>1885184</memory>
<vcpu>2</vcpu>
<on_poweroff>destroy</on_poweroff>
<on_reboot>restart</on_reboot>
<on_crash>restart</on_crash>
<devices>
</devices>
</domain>
libvirt_intWrap: val = 0
libvirt_intWrap: val = 0
On Fri, Oct 24, 2008 at 1:10 PM, Lu Baolu <allen.virt@gmail.com>
wrote:> Hi folks,
>
> I''ve built a domain 0 for the xVM built for the developing code
> (downloaded two weeks ago, not sure if it is the latest code). xVM
> hypervisor and domain 0 work well. However, when I tried to start a PV
> domain with "virsh start" command. The command failed with the
> following information.
>
> This is what I''ve typed:
> ***************************************************
> # virsh
> Using new hypervisor call: 30003
> Welcome to virsh, the virtualization interactive terminal.
>
> Type: ''help'' for help with commands
> ''quit'' to quit
>
> virsh # start pv_snv_100
> libvir: Xen Daemon error : POST operation failed: (xend.err "Boot
> loader didn''t return any data!")
> error: Failed to start domain pv_snv_100
> ***************************************************
>
> This is what I got from /var/adm/message during above operation:
> ***************************************************
> [allen@blu-wbg:~]tail -f /var/adm/messages
> Oct 24 12:36:03 blu-wbg privcmd: [ID 388104 kern.notice] unrecognized
> HYPERVISOR_platform_op 38
> Oct 24 12:36:14 blu-wbg xpvd: [ID 395608 kern.info] balloon@0, balloon0
> Oct 24 12:36:14 blu-wbg genunix: [ID 936769 kern.info] balloon0 is
> /xpvd/balloon@0
> ***************************************************
>
> The first line displayed when "virsh" executed. And the next two
lines
> were during "start pv_snv_100". pv_snv_100 is a domain name for a
PV
> guest. It was installed before upgrading to the latest xVM binaries.
> virsh-install can''t install a guest after upgrading.
>
> ***************************************************
> [allen@blu-wbg:~]sudo virt-install
> libvirt_virConnectPtrWrap: node = 83ed000
> libvirt_xmlcharPtrWrap: str = Xen
> libvirt_xmlcharPtrWrap: str = Xen
> libvirt_virConnectPtrWrap: node = 8117948
> libvirt_xmlcharPtrWrap: str = <capabilities>
> <host>
> <cpu>
> <arch>i86pc</arch>
> <features>
> <vmx/>
> <pae/>
> </features>
> </cpu>
> <migration_features>
> <live/>
> <uri_transports>
> <uri_transport>xenmigr</uri_transport>
> </uri_transports>
> </migration_features>
> </host>
> </capabilities>
>
> libvirt_intWrap: val = 0
> Would you like a fully virtualized guest (yes or no)? This will allow
> you to run unmodified operating systems. yes
> libvirt_virConnectPtrWrap: node = 8117948
> libvirt_xmlcharPtrWrap: str = <capabilities>
> <host>
> <cpu>
> <arch>i86pc</arch>
> <features>
> <vmx/>
> <pae/>
> </features>
> </cpu>
> <migration_features>
> <live/>
> <uri_transports>
> <uri_transport>xenmigr</uri_transport>
> </uri_transports>
> </migration_features>
> </host>
> </capabilities>
>
> libvirt_intWrap: val = 0
> What is the name of your virtual machine? hvm_snv_100
> How much RAM should be allocated (in megabytes)? 1024
> What would you like to use as the disk (path)? /dev/dsk/c1d0s0
> libvirt_intWrap: val = 0
> libvirt_virDomainPtrWrap: node = 83dd7c0
> libvirt_xmlcharPtrWrap: str = pv_snv_100
> libvirt_virDomainPtrWrap: node = 8319398
> libvirt_xmlcharPtrWrap: str = <domain type=''xen''
id=''0''>
> <name>Domain-0</name>
> <uuid>00000000-0000-0000-0000-000000000000</uuid>
> <bootloader/>
> <memory>1880064</memory>
> <vcpu>2</vcpu>
> <on_poweroff>destroy</on_poweroff>
> <on_reboot>restart</on_reboot>
> <on_crash>restart</on_crash>
> <devices>
> </devices>
> </domain>
>
> libvirt_xmlcharPtrWrap: str = <domain type=''xen''
id=''-1''>
> <name>pv_snv_100</name>
> <uuid>7bebdae1-9709-dafb-8b39-b9004cb5a2ce</uuid>
> <bootloader>/usr/lib/xen/bin/pygrub</bootloader>
> <os>
> <type>linux</type>
> </os>
> <memory>1048576</memory>
> <vcpu>1</vcpu>
> <on_poweroff>destroy</on_poweroff>
> <on_reboot>restart</on_reboot>
> <on_crash>restart</on_crash>
> <devices>
> <interface type=''ethernet''>
> <target dev=''vif-1.0''/>
> <mac address=''00:16:3e:0a:13:e0''/>
> <script path=''vif-vnic''/>
> </interface>
> <disk type=''block''
device=''disk''>
> <driver name=''phy''/>
> <source dev=''/dev/dsk/c1d0s0''/>
> <target dev=''xvda''/>
> </disk>
> </devices>
> </domain>
>
> libvirt_intWrap: val = 0
> libvirt_intWrap: val = 0
> Disk /dev/dsk/c1d0s0 is already in use by another guest! Do you
> really want to use the disk (yes or no)? yes
> Would you like to enable graphics support? (yes or no) yes
> What would you like to use for the virtual CD image?
> /export/home/allen/Download/sol-11-x86-snv-100.iso
>
>
> Starting install...
> libvir: Xen Daemon error : GET operation failed:
> libvirt_virDomainPtrWrap: node = 0
> libvirt_xmlcharPtrWrap: str = GET operation failed:
> libvirt_xmlcharPtrWrap: str = GET operation failed: %s
> libvirt_xmlcharPtrWrap: str > libvir: Xen Daemon error : GET operation
failed:
> libvirt_virDomainPtrWrap: node = 0
> libvirt_xmlcharPtrWrap: str = GET operation failed:
> libvirt_xmlcharPtrWrap: str = GET operation failed: %s
> libvirt_xmlcharPtrWrap: str > libvirt_intWrap: val = 0
> libvirt_virDomainPtrWrap: node = 8319398
> libvirt_xmlcharPtrWrap: str = pv_snv_100
> libvirt_virDomainPtrWrap: node = 83657f0
> libvirt_xmlcharPtrWrap: str = <domain type=''xen''
id=''0''>
> <name>Domain-0</name>
> <uuid>00000000-0000-0000-0000-000000000000</uuid>
> <bootloader/>
> <memory>1880064</memory>
> <vcpu>2</vcpu>
> <on_poweroff>destroy</on_poweroff>
> <on_reboot>restart</on_reboot>
> <on_crash>restart</on_crash>
> <devices>
> </devices>
> </domain>
>
> libvirt_intWrap: val = 0
> libvirt_intWrap: val = 0
> libvir: Xen Daemon error : POST operation failed: (xend.err ''Error
> creating domain: HVM guest support is unavailable: is VT/AMD-V
> supported by your CPU and enabled in your BIOS?'')
> libvirt_virDomainPtrWrap: node = 0
> libvirt_xmlcharPtrWrap: str = POST operation failed: (xend.err
''Error
> creating domain: HVM guest support is unavailable: is VT/AMD-V
> supported by your CPU and enabled in your BIOS?'')
> libvirt_xmlcharPtrWrap: str = POST operation failed: %s
> libvirt_xmlcharPtrWrap: str = (xend.err ''Error creating domain:
HVM
> guest support is unavailable: is VT/AMD-V supported by your CPU and
> enabled in your BIOS?'')
> Traceback (most recent call last):
> File "/usr/bin/virt-install", line 657, in ?
> main()
> File "/usr/bin/virt-install", line 606, in main
> dom = guest.start_install(conscb,progresscb)
> File
"/export/home/allen/Download/xvm-gate///proto/install/usr/lib/python2.4/site-packages/virtinst/Guest.py",
> line 638, in start_install
> File
"/export/home/allen/Download/xvm-gate///proto/install/usr/lib/python2.4/site-packages/virtinst/Guest.py",
> line 655, in _do_install
> File "/usr/lib/python2.4/vendor-packages/libvirt.py", line 585,
in createLinux
> if ret is None:raise libvirtError(''virDomainCreateLinux()
failed'',
> conn=self)
> libvirt.libvirtError: virDomainCreateLinux() failed POST operation
> failed: (xend.err ''Error creating domain: HVM guest support is
> unavailable: is VT/AMD-V supported by your CPU and enabled in your
> BIOS?'')
> libvirt_intWrap: val = 0
> ***************************************************
>
> I am very appreciated for your suggestions and tips.
>
> Thanks,
> -Baolu
>
On Fri, Oct 24, 2008 at 01:10:12PM +0800, Lu Baolu wrote:> I''ve built a domain 0 for the xVM built for the developing code > (downloaded two weeks ago, not sure if it is the latest code). xVM > hypervisor and domain 0 work well. However, when I tried to start a PV > domain with "virsh start" command. The command failed with the > following information.Sorry, I thought you were aware of this: you can''t just switch out new version of the hypervisor. It requires (significant) work both in the Solaris kernel for dom0 and in xen tools themselves to move to a new version of xen. As an indication, it took around 3 months from the point work started to move from 3.0.4 to 3.1.4 without any regressions. regards john
Hi John, Thanks for the quick response and information. I took the following steps to switch the new version xVM: # svcadm disable xvm/domains xvm/console xvm/xend xvm/store #pkgrm SUNWvirtinst SUNWurlgrabber SUNWlibvirt SUNWxvmh \ SUNWxvmhvm SUNWxvmu SUNWxvmr SUNWxvmdomu SUNWxvmdomr (9 packages removed) #pkgadd -d packages-nondebug SUNWxvmdomr SUNWxvmdomu \ SUNWxvmr SUNWxvmu SUNWxvmhvm \ SUNWxvmh SUNWlibvirt SUNWurlgrabber SUNWvirtinst (9 packages installed) # svcadm enable xvm/store xvm/xend xvm/console xvm/domains # reboot Are above steps correct? Also, could you please address the below questions? 1. The packages build from developping xvm and xVM for snv_100 are differet. 9 packages are generated by the developping xvm: [allen@blu-wbg:packages-nondebug]ls SUNWlibvirt SUNWvirtinst SUNWxvmdomu SUNWxvmhvm SUNWxvmu SUNWurlgrabber SUNWxvmdomr SUNWxvmh SUNWxvmr While, 11 packages are generated by xvm for snv_100: [allen@blu-wbg:packages-nondebug]ls SUNWlibvirt SUNWurlgrabber SUNWvirtinst SUNWxvmdomu SUNWxvmhvm SUNWxvmu SUNWlibvirtr SUNWvdisk SUNWxvmdomr SUNWxvmh SUNWxvmr If I only replace the 9 packages generated by developping xvm and leave others untouching, do this impact? 2. When domain 0 kernel boots on the new xvm, there is a WARN messages: Oct 24 14:09:21 blu-wbg privcmd: [ID 388104 kern.notice] unrecognized HYPERVISOR_platform_op 38 However, I can''t find any platform hypercall interface with command #38 defined in the xen public header files. Is this a misbehavioring hypercall request or I didn''t get the latest xen header? 3. I have domain 0 working on the new xVM and all xvm services running now. [allen@blu-wbg:~]svcs | grep xvm online 14:08:59 svc:/system/xvm/ipagent:default online 14:09:07 svc:/system/xvm/store:default online 14:09:17 svc:/system/xvm/xend:default online 14:09:18 svc:/system/xvm/console:default online 14:09:21 svc:/system/xvm/virtd:default online 14:09:22 svc:/system/xvm/domains:default [allen@blu-wbg:~]uname -a SunOS blu-wbg 5.11 dom0-101 i86pc i386 i86xpv But I can''t create and run another domain. Does this mean 1). xen tools in the xvm source tree are not ready yet, I need to port them into the new domain 0. or 2). the domain 0 is not ready, some hypercall interfaces are not supported. I need to add them into domain 0? Thanks for your help. -Baolu On Sat, Oct 25, 2008 at 3:26 AM, John Levon <john.levon@sun.com> wrote:> On Fri, Oct 24, 2008 at 01:10:12PM +0800, Lu Baolu wrote: > >> I''ve built a domain 0 for the xVM built for the developing code >> (downloaded two weeks ago, not sure if it is the latest code). xVM >> hypervisor and domain 0 work well. However, when I tried to start a PV >> domain with "virsh start" command. The command failed with the >> following information. > > Sorry, I thought you were aware of this: you can''t just switch out new > version of the hypervisor. It requires (significant) work both in the > Solaris kernel for dom0 and in xen tools themselves to move to a new > version of xen. As an indication, it took around 3 months from the point > work started to move from 3.0.4 to 3.1.4 without any regressions. > > regards > john >
Lu Baolu wrote:> Hi John, > > Thanks for the quick response and information. I took the following > steps to switch the new version xVM: > > # svcadm disable xvm/domains xvm/console xvm/xend xvm/store > > #pkgrm SUNWvirtinst SUNWurlgrabber SUNWlibvirt SUNWxvmh \ > SUNWxvmhvm SUNWxvmu SUNWxvmr SUNWxvmdomu SUNWxvmdomr > (9 packages removed) > > #pkgadd -d packages-nondebug SUNWxvmdomr SUNWxvmdomu \ > SUNWxvmr SUNWxvmu SUNWxvmhvm \ > SUNWxvmh SUNWlibvirt SUNWurlgrabber SUNWvirtinst > (9 packages installed) > > # svcadm enable xvm/store xvm/xend xvm/console xvm/domains > # reboot > > Are above steps correct? Also, could you please address the below questions? > > 1. The packages build from developping xvm and xVM for snv_100 are differet. > 9 packages are generated by the developping xvm: > [allen@blu-wbg:packages-nondebug]ls > SUNWlibvirt SUNWvirtinst SUNWxvmdomu SUNWxvmhvm SUNWxvmu > SUNWurlgrabber SUNWxvmdomr SUNWxvmh SUNWxvmrI must have missed something... what exactly are you installing, and where did this list of packages come from? It is missing SUNWlibvirtr, which was introduced in snv_92. SUNWvdisk was introduced in snv_100. If you''re trying to mix old xvm packages and a new dom0 (or vice-versa), I''m not surprised things don''t work. -Ryan> > While, 11 packages are generated by xvm for snv_100: > [allen@blu-wbg:packages-nondebug]ls > SUNWlibvirt SUNWurlgrabber SUNWvirtinst SUNWxvmdomu SUNWxvmhvm SUNWxvmu > SUNWlibvirtr SUNWvdisk SUNWxvmdomr SUNWxvmh SUNWxvmr > > If I only replace the 9 packages generated by developping xvm and > leave others untouching, do this impact? > > 2. When domain 0 kernel boots on the new xvm, there is a WARN messages: > > Oct 24 14:09:21 blu-wbg privcmd: [ID 388104 kern.notice] unrecognized > HYPERVISOR_platform_op 38 > > However, I can''t find any platform hypercall interface with command > #38 defined in the xen public header files. Is this a misbehavioring > hypercall request or I didn''t get the latest xen header? > > 3. I have domain 0 working on the new xVM and all xvm services running now. > > [allen@blu-wbg:~]svcs | grep xvm > online 14:08:59 svc:/system/xvm/ipagent:default > online 14:09:07 svc:/system/xvm/store:default > online 14:09:17 svc:/system/xvm/xend:default > online 14:09:18 svc:/system/xvm/console:default > online 14:09:21 svc:/system/xvm/virtd:default > online 14:09:22 svc:/system/xvm/domains:default > [allen@blu-wbg:~]uname -a > SunOS blu-wbg 5.11 dom0-101 i86pc i386 i86xpv > > But I can''t create and run another domain. Does this mean > > 1). xen tools in the xvm source tree are not ready yet, I need to port > them into the new domain 0. > > or > > 2). the domain 0 is not ready, some hypercall interfaces are not > supported. I need to add them into domain 0? > > Thanks for your help. > -Baolu > > > On Sat, Oct 25, 2008 at 3:26 AM, John Levon <john.levon@sun.com> wrote: >> On Fri, Oct 24, 2008 at 01:10:12PM +0800, Lu Baolu wrote: >> >>> I''ve built a domain 0 for the xVM built for the developing code >>> (downloaded two weeks ago, not sure if it is the latest code). xVM >>> hypervisor and domain 0 work well. However, when I tried to start a PV >>> domain with "virsh start" command. The command failed with the >>> following information. >> Sorry, I thought you were aware of this: you can''t just switch out new >> version of the hypervisor. It requires (significant) work both in the >> Solaris kernel for dom0 and in xen tools themselves to move to a new >> version of xen. As an indication, it took around 3 months from the point >> work started to move from 3.0.4 to 3.1.4 without any regressions. >> >> regards >> john >> > _______________________________________________ > xen-discuss mailing list > xen-discuss@opensolaris.org
On Tue, Oct 28, 2008 at 3:26 AM, Ryan Scott <Ryan.Scott@sun.com> wrote:> Lu Baolu wrote: >> >> Hi John, >> >> Thanks for the quick response and information. I took the following >> steps to switch the new version xVM: >> >> # svcadm disable xvm/domains xvm/console xvm/xend xvm/store >> >> #pkgrm SUNWvirtinst SUNWurlgrabber SUNWlibvirt SUNWxvmh \ >> SUNWxvmhvm SUNWxvmu SUNWxvmr SUNWxvmdomu SUNWxvmdomr >> (9 packages removed) >> >> #pkgadd -d packages-nondebug SUNWxvmdomr SUNWxvmdomu \ >> SUNWxvmr SUNWxvmu SUNWxvmhvm \ >> SUNWxvmh SUNWlibvirt SUNWurlgrabber SUNWvirtinst >> (9 packages installed) >> >> # svcadm enable xvm/store xvm/xend xvm/console xvm/domains >> # reboot >> >> Are above steps correct? Also, could you please address the below >> questions? >> >> 1. The packages build from developping xvm and xVM for snv_100 are >> differet. >> 9 packages are generated by the developping xvm: >> [allen@blu-wbg:packages-nondebug]ls >> SUNWlibvirt SUNWvirtinst SUNWxvmdomu SUNWxvmhvm SUNWxvmu >> SUNWurlgrabber SUNWxvmdomr SUNWxvmh SUNWxvmr > > I must have missed something... what exactly are you installing, and where > did this list of packages come from? It is missing SUNWlibvirtr, which was > introduced in snv_92. SUNWvdisk was introduced in snv_100. > > If you''re trying to mix old xvm packages and a new dom0 (or vice-versa), I''m > not surprised things don''t work. > > -RyanSorry, I didn''t explain well what I am trying to do. I am trying to work out an OpenSolaris domain 0 for the developing xVM. The steps I followed to get the latest source tree and build the packages were posted at below link: http://mail.opensolaris.org/pipermail/xen-discuss/2008-May/003278.html The only difference is that I used xen-unstable changeset #17748. This changeset was said to be the latest xen base. The mistake I''ve made is that I didn''t use the latest xvm-src.tar.bz2 (I am using snv_89, the latest is snv_101). That definitely will miss the two packages you mentioned. I will turn to use xvm-src for snv_100. Thanks for the help. -Baolu> >> >> While, 11 packages are generated by xvm for snv_100: >> [allen@blu-wbg:packages-nondebug]ls >> SUNWlibvirt SUNWurlgrabber SUNWvirtinst SUNWxvmdomu SUNWxvmhvm >> SUNWxvmu >> SUNWlibvirtr SUNWvdisk SUNWxvmdomr SUNWxvmh SUNWxvmr >> >> If I only replace the 9 packages generated by developping xvm and >> leave others untouching, do this impact? >> >> 2. When domain 0 kernel boots on the new xvm, there is a WARN messages: >> >> Oct 24 14:09:21 blu-wbg privcmd: [ID 388104 kern.notice] unrecognized >> HYPERVISOR_platform_op 38 >> >> However, I can''t find any platform hypercall interface with command >> #38 defined in the xen public header files. Is this a misbehavioring >> hypercall request or I didn''t get the latest xen header? >> >> 3. I have domain 0 working on the new xVM and all xvm services running >> now. >> >> [allen@blu-wbg:~]svcs | grep xvm >> online 14:08:59 svc:/system/xvm/ipagent:default >> online 14:09:07 svc:/system/xvm/store:default >> online 14:09:17 svc:/system/xvm/xend:default >> online 14:09:18 svc:/system/xvm/console:default >> online 14:09:21 svc:/system/xvm/virtd:default >> online 14:09:22 svc:/system/xvm/domains:default >> [allen@blu-wbg:~]uname -a >> SunOS blu-wbg 5.11 dom0-101 i86pc i386 i86xpv >> >> But I can''t create and run another domain. Does this mean >> >> 1). xen tools in the xvm source tree are not ready yet, I need to port >> them into the new domain 0. >> >> or >> >> 2). the domain 0 is not ready, some hypercall interfaces are not >> supported. I need to add them into domain 0? >> >> Thanks for your help. >> -Baolu >> >> >> On Sat, Oct 25, 2008 at 3:26 AM, John Levon <john.levon@sun.com> wrote: >>> >>> On Fri, Oct 24, 2008 at 01:10:12PM +0800, Lu Baolu wrote: >>> >>>> I''ve built a domain 0 for the xVM built for the developing code >>>> (downloaded two weeks ago, not sure if it is the latest code). xVM >>>> hypervisor and domain 0 work well. However, when I tried to start a PV >>>> domain with "virsh start" command. The command failed with the >>>> following information. >>> >>> Sorry, I thought you were aware of this: you can''t just switch out new >>> version of the hypervisor. It requires (significant) work both in the >>> Solaris kernel for dom0 and in xen tools themselves to move to a new >>> version of xen. As an indication, it took around 3 months from the point >>> work started to move from 3.0.4 to 3.1.4 without any regressions. >>> >>> regards >>> john >>> >> _______________________________________________ >> xen-discuss mailing list >> xen-discuss@opensolaris.org > >