On Tue, Oct 28, 2008 at 3:26 AM, Ryan Scott <[EMAIL PROTECTED]> 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: >> [EMAIL PROTECTED]: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. > > -Ryan
Sorry, 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: >> [EMAIL PROTECTED]: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. >> >> [EMAIL PROTECTED]:~]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 >> [EMAIL PROTECTED]:~]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 <[EMAIL PROTECTED]> 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 >> [email protected] > > _______________________________________________ xen-discuss mailing list [email protected]
