Hi folks, I am trying to build a functional xVM (hypervisor + tools + utilities) from the source tree under hg.opensolaris.org/hg/xen-gate/. I followed the instructions posted below to build xen-unstable.hg source. http://mail.opensolaris.org/pipermail/xen-discuss/2008-May/003278.html sunos.hg and xen.hg are updated according to the instruction while other hg gates remain the same as those in xvm snv_101. After I replaced the xVM packages with the new ones. libvirt seems not to work. [allen@blu-wbg:~]sudo virsh libvir: Remote error : remoteDispatchClientRequest: internal error: library function returned error but did not set virterror error: failed to connect to the hypervisor [allen@blu-wbg:~]svcs | grep xvm online 16:25:17 svc:/system/xvm/ipagent:default online 16:25:27 svc:/system/xvm/store:default online 16:25:33 svc:/system/xvm/xend:default online 16:25:33 svc:/system/xvm/console:default online 16:25:35 svc:/system/xvm/virtd:default online 16:25:38 svc:/system/xvm/domains:default Is it a must to use all the latest gates to build a functional xvm hypervisor/tools/utilities? If so, how can a developer to get the latest gate from outside of SUN? Does SUN has a consolidated xVM for xen 3.3 functionalities? Thanks, -Baolu
On Thu, Oct 30, 2008 at 04:37:56PM +0800, Lu Baolu wrote:> I am trying to build a functional xVM (hypervisor + tools + utilities) > from the source tree under hg.opensolaris.org/hg/xen-gate/. I followed > the instructions posted below to build xen-unstable.hg source. > > http://mail.opensolaris.org/pipermail/xen-discuss/2008-May/003278.html > > sunos.hg and xen.hg are updated according to the instruction while > other hg gates remain the same as those in xvm snv_101. After I > replaced the xVM packages with the new ones. libvirt seems not to > work.Allen, can you describe exactly what you have done to get this far? The instructions you cite are specifically for a build 89 based environment. That was later updated to build 94. No-one has done any work with those bits and build 101 - there''s no reason to expect that it would work.
> > Allen, can you describe exactly what you have done to get this far? >OK! 1. Setting up all the environment parameters according to the instruction 2. Grab/setup the b101 xvm sources mkdir xvm-gate cd xvm-gate wget http://dlc.sun.com/osol/on/downloads/b101/xvm-src.tar.bz2 bzcat xvm-src.tar.bz2 | tar xf - 3. Clone the sunos.hg bits mv sunos.hg sunos.hg.101 hg clone ssh://anon@hg.opensolaris.org/hg/xen-gate/sunos-unstable sunos.hg 4. modify check_pkgs.ksh to let build continue if some files were not packaged vi sunos.hg/src/pkgdefs/check_pkgs.ksh #comment the "ret=1" line 5. Get the xen-unstable changeset 17748 mv xen.hg xen.hg.101 hg clone -r 17748 http://xenbits.xensource.com/xen-unstable.hg xen.hg 6. get xen-unstable patches cd xen.hg hg qinit -c echo "[paths]" > .hg/patches/.hg/hgrc echo "default ssh://anon@hg.opensolaris.org/hg/xen-gate/devel-unstable-patches" >> .hg/patches/.hg/hgrc cd .hg/patches/ hg pull -uv 7. push the patch stack cd ../../ hg qpush -a 8. modify a gcc option to let the build continue if there is a warning in libxc vi xen.hg/tools/libxc/Makefile #remove "-Werror" gcc option 9. build all sunos.hg/bin/build-all full # 11 packages are generated under packages-(non)debug directories 10. replace the installed packages with the built result # svcadm disable xvm/domains xvm/console xvm/xend xvm/store # pkgrm SUNWvirtinst SUNWurlgrabber SUNWlibvirt SUNWlibvirtr SUNWxvmh \ SUNWxvmhvm SUNWxvmu SUNWxvmr SUNWxvmdomu SUNWxvmdomr SUNWvdisk # pkgadd -d packages-nondebug SUNWxvmdomr SUNWxvmdomu SUNWxvmr SUNWxvmu SUNWxvmhvm \ SUNWxvmh SUNWlibvirt SUNWlibvirtr SUNWurlgrabber SUNWvirtinst SUNWvdisk # svcadm enable xvm/store xvm/xend xvm/console xvm/domains # reboot Thanks, -Baolu
On Fri, Oct 31, 2008 at 10:28:22AM +0800, Lu Baolu wrote:> > > > Allen, can you describe exactly what you have done to get this far? > > > > OK! > > 1. Setting up all the environment parameters according to the instruction > > 2. Grab/setup the b101 xvm sources > mkdir xvm-gate > cd xvm-gate > wget http://dlc.sun.com/osol/on/downloads/b101/xvm-src.tar.bz2 > bzcat xvm-src.tar.bz2 | tar xf - > > 3. Clone the sunos.hg bits > mv sunos.hg sunos.hg.101 > hg clone ssh://anon@hg.opensolaris.org/hg/xen-gate/sunos-unstable sunos.hgYou can''t use build 101. You have to base on build 89 of the xvm bits and the (build 94 derived) associated onnv bits.
On Fri, Oct 31, 2008 at 3:59 PM, David Edmondson <dme@sun.com> wrote:> On Fri, Oct 31, 2008 at 10:28:22AM +0800, Lu Baolu wrote: >> > >> > Allen, can you describe exactly what you have done to get this far? >> > >> >> OK! >> >> 1. Setting up all the environment parameters according to the instruction >> >> 2. Grab/setup the b101 xvm sources >> mkdir xvm-gate >> cd xvm-gate >> wget http://dlc.sun.com/osol/on/downloads/b101/xvm-src.tar.bz2 >> bzcat xvm-src.tar.bz2 | tar xf - >> >> 3. Clone the sunos.hg bits >> mv sunos.hg sunos.hg.101 >> hg clone ssh://anon@hg.opensolaris.org/hg/xen-gate/sunos-unstable sunos.hg > > You can''t use build 101. You have to base on build 89 of the xvm bits and > the (build 94 derived) associated onnv bits.Thanks for the information. For onnv, do you mean build 94 or 89?
On Fri, Oct 31, 2008 at 04:13:15PM +0800, Lu Baolu wrote:> For onnv, do you mean build 94 or 89?Start with build 89. The onnv gate that Mark describes in his instructions started out as based on build 89. It was later updated to build 94, but it''s still easier to start with 89.
On Fri, Oct 31, 2008 at 4:52 PM, David Edmondson <dme@sun.com> wrote:> On Fri, Oct 31, 2008 at 04:13:15PM +0800, Lu Baolu wrote: >> For onnv, do you mean build 94 or 89? > > Start with build 89. The onnv gate that Mark describes in his > instructions started out as based on build 89. It was later updated to > build 94, but it''s still easier to start with 89. >Hi David, I changed the steps to build the vt-d supported xvm and onnv bits according to the discussion with you. Would you please help me to review it and tell whether it works? Grub and build xvm packages =======================1. Setting up all the environment parameters according to the Mark''s instruction 2. Grab/setup the b101 xvm sources mkdir xvm-gate cd xvm-gate wget http://dlc.sun.com/osol/on/downloads/b89/xvm-src.tar.bz2 bzcat xvm-src.tar.bz2 | tar xf - 3. Clone the sunos.hg bits mv sunos.hg sunos.hg.89 hg clone ssh://anon@hg.opensolaris.org/hg/xen-gate/sunos-unstable sunos.hg 4. Get the xen-unstable changeset 17748 [Note: Since the latest xvm source was sync''ed up to xen-unstable changeset 17748, the changeset # is different from Mark''s original instruction.] mv xen.hg xen.hg.89 hg clone -r 17748 http://xenbits.xensource.com/xen-unstable.hg xen.hg 5. get xen-unstable patches cd xen.hg hg qinit -c echo "[paths]" > .hg/patches/.hg/hgrc echo "default ssh://anon@hg.opensolaris.org/hg/xen-gate/devel-unstable-patches" >> .hg/patches/.hg/hgrc cd .hg/patches/ hg pull -uv 6. push the patch stack cd ../../ hg qpush -a 7. build xvm packages sunos.hg/bin/build-all full Grub and build onnv bits ==================hg clone ssh://anon@hg.opensolaris.org/hg/xen-gate/matrix-unstable hg clone ./matrix-unstable matrix-unstable-build cd matrix-unstable-build [Note: since the onnv bits are updated to onnv_94, so the b94 close-bin is grubed instead of b89 in original instruction.] wget http://dlc.sun.com/osol/on/downloads/b94/on-closed-bins.i386.tar.bz2 wget http://dlc.sun.com/osol/on/downloads/b94/on-closed-bins-nd.i386.tar.bz2 bzcat on-closed-bins.i386.tar.bz2 | tar xf - bzcat on-closed-bins-nd.i386.tar.bz2 | tar xf - setup env script and run nightly Update xvm packages and onnv bits =========================== [Question: is there any dependence between the xvm packages installation and onnv bits BFU? In another word, is there a must that who will be updated first?] 1. install xvm packages # svcadm disable xvm/domains xvm/console xvm/xend xvm/store # pkgrm SUNWvirtinst SUNWurlgrabber SUNWlibvirt SUNWxvmh \ SUNWxvmhvm SUNWxvmu SUNWxvmr SUNWxvmdomu SUNWxvmdomr # pkgadd -d packages-nondebug SUNWxvmdomr SUNWxvmdomu SUNWxvmr SUNWxvmu SUNWxvmhvm \ SUNWxvmh SUNWlibvirt SUNWurlgrabber SUNWvirtinst # svcadm enable xvm/store xvm/xend xvm/console xvm/domains # reboot 2. BFU the onnv bits That''s all. Thanks, -Baolu
On Fri, Oct 31, 2008 at 11:20:53PM +0800, Lu Baolu wrote:> I changed the steps to build the vt-d supported xvm and onnv bits > according to the discussion with you. Would you please help me to > review it and tell whether it works?This set of instructions look good, though you say:> 2. Grab/setup the b101 xvm sources > mkdir xvm-gate > cd xvm-gate > wget http://dlc.sun.com/osol/on/downloads/b89/xvm-src.tar.bz2 > bzcat xvm-src.tar.bz2 | tar xf -Obviously you are getting b89 xVM sources rather than b101.
Lu Baolu wrote:> On Fri, Oct 31, 2008 at 4:52 PM, David Edmondson <dme@sun.com> wrote: >> On Fri, Oct 31, 2008 at 04:13:15PM +0800, Lu Baolu wrote: >>> For onnv, do you mean build 94 or 89? >> Start with build 89. The onnv gate that Mark describes in his >> instructions started out as based on build 89. It was later updated to >> build 94, but it''s still easier to start with 89. >> > > Hi David, > > I changed the steps to build the vt-d supported xvm and onnv bits > according to the discussion with you. Would you please help me to > review it and tell whether it works? > > Grub and build xvm packages > =======================> 1. Setting up all the environment parameters according to the Mark''s instruction > > 2. Grab/setup the b101 xvm sources > mkdir xvm-gate > cd xvm-gate > wget http://dlc.sun.com/osol/on/downloads/b89/xvm-src.tar.bz2 > bzcat xvm-src.tar.bz2 | tar xf - > > 3. Clone the sunos.hg bits > mv sunos.hg sunos.hg.89 > hg clone ssh://anon@hg.opensolaris.org/hg/xen-gate/sunos-unstable sunos.hgYou probably want to have the b89 sunos.hg bits and hg pull -uv <path-to-b101-xvm-source>/sunos.hg to pull in the 101 bits.. There will be a fair amount of merging to get that to work. MRJ> 4. Get the xen-unstable changeset 17748 > [Note: Since the latest xvm source was sync''ed up to xen-unstable > changeset 17748, the changeset # is different from Mark''s original > instruction.] > mv xen.hg xen.hg.89 > hg clone -r 17748 http://xenbits.xensource.com/xen-unstable.hg xen.hg > > 5. get xen-unstable patches > cd xen.hg > hg qinit -c > echo "[paths]" > .hg/patches/.hg/hgrc > echo "default > ssh://anon@hg.opensolaris.org/hg/xen-gate/devel-unstable-patches" >> > .hg/patches/.hg/hgrc > cd .hg/patches/ > hg pull -uv > > 6. push the patch stack > cd ../../ > hg qpush -a > > 7. build xvm packages > sunos.hg/bin/build-all full > > Grub and build onnv bits > ==================> hg clone ssh://anon@hg.opensolaris.org/hg/xen-gate/matrix-unstable > hg clone ./matrix-unstable matrix-unstable-build > cd matrix-unstable-build > > [Note: since the onnv bits are updated to onnv_94, so the b94 > close-bin is grubed instead of b89 in original instruction.] > > wget http://dlc.sun.com/osol/on/downloads/b94/on-closed-bins.i386.tar.bz2 > wget http://dlc.sun.com/osol/on/downloads/b94/on-closed-bins-nd.i386.tar.bz2 > bzcat on-closed-bins.i386.tar.bz2 | tar xf - > bzcat on-closed-bins-nd.i386.tar.bz2 | tar xf - > setup env script and run nightly > > Update xvm packages and onnv bits > ===========================> > [Question: is there any dependence between the xvm packages > installation and onnv bits BFU? In another word, is there a must that > who will be updated first?] > > 1. install xvm packages > # svcadm disable xvm/domains xvm/console xvm/xend xvm/store > # pkgrm SUNWvirtinst SUNWurlgrabber SUNWlibvirt SUNWxvmh \ > SUNWxvmhvm SUNWxvmu SUNWxvmr SUNWxvmdomu SUNWxvmdomr > # pkgadd -d packages-nondebug SUNWxvmdomr SUNWxvmdomu SUNWxvmr > SUNWxvmu SUNWxvmhvm \ > SUNWxvmh SUNWlibvirt SUNWurlgrabber SUNWvirtinst > # svcadm enable xvm/store xvm/xend xvm/console xvm/domains > # reboot > > 2. BFU the onnv bits > > That''s all. > Thanks, > -Baolu > _______________________________________________ > xen-discuss mailing list > xen-discuss@opensolaris.org
On Fri, Oct 31, 2008 at 12:37:21PM -0400, Mark Johnson wrote:> > > Lu Baolu wrote: >> On Fri, Oct 31, 2008 at 4:52 PM, David Edmondson <dme@sun.com> wrote: >>> On Fri, Oct 31, 2008 at 04:13:15PM +0800, Lu Baolu wrote: >>>> For onnv, do you mean build 94 or 89? >>> Start with build 89. The onnv gate that Mark describes in his >>> instructions started out as based on build 89. It was later updated to >>> build 94, but it''s still easier to start with 89. >>> >> >> Hi David, >> >> I changed the steps to build the vt-d supported xvm and onnv bits >> according to the discussion with you. Would you please help me to >> review it and tell whether it works? >> >> Grub and build xvm packages >> =======================>> 1. Setting up all the environment parameters according to the Mark''s instruction >> >> 2. Grab/setup the b101 xvm sources >> mkdir xvm-gate >> cd xvm-gate >> wget http://dlc.sun.com/osol/on/downloads/b89/xvm-src.tar.bz2 >> bzcat xvm-src.tar.bz2 | tar xf - >> >> 3. Clone the sunos.hg bits >> mv sunos.hg sunos.hg.89 >> hg clone ssh://anon@hg.opensolaris.org/hg/xen-gate/sunos-unstable sunos.hg > > You probably want to have the b89 sunos.hg bits > and > hg pull -uv <path-to-b101-xvm-source>/sunos.hg > > to pull in the 101 bits.. There will be a fair amount of merging > to get that to work.Why would we want the 101 bits? The bits that he gets from the b89 based stuff should be self-consistent (which is all that matters right now).
David Edmondson wrote:> On Fri, Oct 31, 2008 at 12:37:21PM -0400, Mark Johnson wrote: >> >> Lu Baolu wrote: >>> On Fri, Oct 31, 2008 at 4:52 PM, David Edmondson <dme@sun.com> wrote: >>>> On Fri, Oct 31, 2008 at 04:13:15PM +0800, Lu Baolu wrote: >>>>> For onnv, do you mean build 94 or 89? >>>> Start with build 89. The onnv gate that Mark describes in his >>>> instructions started out as based on build 89. It was later updated to >>>> build 94, but it''s still easier to start with 89. >>>> >>> Hi David, >>> >>> I changed the steps to build the vt-d supported xvm and onnv bits >>> according to the discussion with you. Would you please help me to >>> review it and tell whether it works? >>> >>> Grub and build xvm packages >>> =======================>>> 1. Setting up all the environment parameters according to the Mark''s instruction >>> >>> 2. Grab/setup the b101 xvm sources >>> mkdir xvm-gate >>> cd xvm-gate >>> wget http://dlc.sun.com/osol/on/downloads/b89/xvm-src.tar.bz2 >>> bzcat xvm-src.tar.bz2 | tar xf - >>> >>> 3. Clone the sunos.hg bits >>> mv sunos.hg sunos.hg.89 >>> hg clone ssh://anon@hg.opensolaris.org/hg/xen-gate/sunos-unstable sunos.hg >> You probably want to have the b89 sunos.hg bits >> and >> hg pull -uv <path-to-b101-xvm-source>/sunos.hg >> >> to pull in the 101 bits.. There will be a fair amount of merging >> to get that to work. > > Why would we want the 101 bits? The bits that he gets from the b89 > based stuff should be self-consistent (which is all that matters right > now).I was just saying if he was trying to merge up to b101 (e.g. >>> 2. Grab/setup the b101 xvm sources), he would have to merge sunos.hg vs just using the 101 bits.. I guess I''m not clear on what the final goal is here? MRJ
On Fri, Oct 31, 2008 at 02:28:10PM -0400, Mark Johnson wrote:>> Why would we want the 101 bits? The bits that he gets from the b89 >> based stuff should be self-consistent (which is all that matters right >> now). > > I was just saying if he was trying to merge up to b101 (e.g. >>> > 2. Grab/setup the b101 xvm sources), he would have to merge sunos.hg > vs just using the 101 bits..I understand, sorry for being slow.> I guess I''m not clear on what the final goal is here?Get something which supports VT-d working.
>> >> Why would we want the 101 bits? The bits that he gets from the b89 >> based stuff should be self-consistent (which is all that matters right >> now). > > I was just saying if he was trying to merge up to b101 > (e.g. >>> 2. Grab/setup the b101 xvm sources), he would have > to merge sunos.hg vs just using the 101 bits..Hi Mark, That''s a typo. I will work everything on b89, not willing to merge up to b101. The final goal here is to get xVM bits that support vt-d. So, if I use b89, following the instruction set here should be ok, right? Thanks, -Allen> > I guess I''m not clear on what the final goal is here? > > > > MRJ > > > _______________________________________________ > xen-discuss mailing list > xen-discuss@opensolaris.org >
Lu Baolu wrote:>>> Why would we want the 101 bits? The bits that he gets from the b89 >>> based stuff should be self-consistent (which is all that matters right >>> now). >> I was just saying if he was trying to merge up to b101 >> (e.g. >>> 2. Grab/setup the b101 xvm sources), he would have >> to merge sunos.hg vs just using the 101 bits.. > > Hi Mark, > > That''s a typo. I will work everything on b89, not willing to merge up to b101. > > The final goal here is to get xVM bits that support vt-d. > > So, if I use b89, following the instruction set here should be ok, right?Yes. I just ran through them and it worked fine. I did run into one thing recently however. You need to build the xvm source on an older snv machine so they match the dom0 machine (I built mine on b93). I ran into problems when I build them on a b100a machine then tried to start xend on my unstable based dom0 (which is b94 based). (there was a htonll symbol problem with the xen libraries if you looked at the xend SMF log). MRJ
Hi Mark and David,
I ran through the steps this morning. Everything went well, however
the final system (xvm + domain 0) failed to create a PV guest. Below
is what happened when I try to run a PV guest:
Install an os200805 PV guest with xm tool:
==================================
# cat os200805.py
name = "os200805"
vcpus = 1
memory = "1024"
bootloader = "/usr/lib/xen/bin/pygrub"
kernel = "/platform/i86xpv/kernel/amd64/unix"
ramdisk = "/boot/x86.microroot"
extra = "/platform/i86xpv/kernel/amd64/unix -B
console=ttya,livemode=text"
disk =
[''file:/export/home/allen/Virtualization/ISO/os200805.iso,6:cdrom,r'',
''file:/export/home/allen/Virtualization/Vdisk/os200805.img,0,w'']
vif = ['''']
on_shutdown = "destroy"
on_reboot = "destroy"
on_crash = "preserve"
# xm create -c os200805.py
Using config file "./os200805.py".
Started domain os200805
WARNING: Cannot extract revision on this
hypervisor version: v-unstable-xvm, unexpected version format
v3.3-unstable-xvm chgset ''Sat Nov 01 22:43:09 2008 +0800
17779:ba68f09d5640''
SunOS Release 5.11 Version snv_86 64-bit
Copyright 1983-2008 Sun Microsystems, Inc. All rights reserved.
Use is subject to license terms.
panic[cpu0]/thread=fffffffffbc3cbe0: BAD TRAP: type=e (#pf Page fault)
rp=fffffffffbc6ea00 addr=fffffe000c1a6d80
#pf Page fault
Bad kernel fault at addr=0xfffffe000c1a6d80
pid=0, pc=0xfffffffffb885da3, sp=0xfffffffffbc6eaf8, eflags=0x10046
cr0: 80050033<pg,wp,ne,et,mp,pe> cr4: 2620<vmxe,xmme,fxsr,pae>
cr2: fffffe000c1a6d80
rdi: fffffe000c1a6d80 rsi: 0 rdx: 800000007c7f8673
rcx: 3 r8: 0 r9: ffffff00c5fb0000
rax: 0 rbx: 800000007c7f8673 rbp: fffffffffbc6eb90
r10: 0 r11: ffffffffc0000000 r12: 0
r13: 1 r14: fffffe000c1a6d80 r15: 800000007c7f8673
fsb: 200000000 gsb: fffffffffbc3e030 ds: 0
es: 0 fs: 0 gs: 0
trp: e err: 3 rip: fffffffffb885da3
cs: e030 rfl: 10046 rsp: fffffffffbc6eaf8
ss: e02b
fffffffffbc6e8e0 unix:die+ea ()
fffffffffbc6e9f0 unix:trap+13cf ()
fffffffffbc6ea00 unix:_cmntrap+12f ()
fffffffffbc6eb90 unix:atomic_cas_64+3 ()
fffffffffbc6ec30 unix:hati_pte_map+153 ()
fffffffffbc6ecb0 unix:hati_load_common+15a ()
fffffffffbc6ed70 unix:hat_devload+13c ()
fffffffffbc6edc0 unix:gnttab_init+dd ()
fffffffffbc6edd0 unix:startup_modules+f9 ()
fffffffffbc6ede0 unix:startup+3f ()
fffffffffbc6ee10 genunix:main+27 ()
fffffffffbc6ee20 unix:_locore_start+80 ()
skipping system dump - no dump device configured
rebooting...
Install a snv_94 PV guest with virt-install tool:
====================================
# virt-install
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_94
How much RAM should be allocated (in megabytes)? 1024
What would you like to use as the disk (path)?
/export/home/allen/Virtualization/ISO/sol-11-x86-snv-94.iso
Arithmetic Exception - core dumped
What''s probably missed in my steps?
Thanks,
Allen
On Sun, Nov 2, 2008 at 11:19 PM, Mark Johnson <Mark.Johnson@sun.com>
wrote:>
>
> Lu Baolu wrote:
>>>>
>>>> Why would we want the 101 bits? The bits that he gets from the
b89
>>>> based stuff should be self-consistent (which is all that
matters right
>>>> now).
>>>
>>> I was just saying if he was trying to merge up to b101
>>> (e.g. >>> 2. Grab/setup the b101 xvm sources), he would
have
>>> to merge sunos.hg vs just using the 101 bits..
>>
>> Hi Mark,
>>
>> That''s a typo. I will work everything on b89, not willing to
merge up to
>> b101.
>>
>> The final goal here is to get xVM bits that support vt-d.
>>
>> So, if I use b89, following the instruction set here should be ok,
right?
>
> Yes. I just ran through them and it worked fine.
>
> I did run into one thing recently however. You need to
> build the xvm source on an older snv machine so they
> match the dom0 machine (I built mine on b93). I ran
> into problems when I build them on a b100a machine
> then tried to start xend on my unstable based dom0
> (which is b94 based). (there was a htonll symbol
> problem with the xen libraries if you looked at
> the xend SMF log).
>
>
>
>
>
> MRJ
>
>
On Mon, Nov 3, 2008 at 1:25 PM, Lu Baolu <allen.virt@gmail.com> wrote:> Hi Mark and David, > > I ran through the steps this morning. Everything went well, however > the final system (xvm + domain 0) failed to create a PV guest. Below > is what happened when I try to run a PV guest: > > Install an os200805 PV guest with xm tool: > ==================================> > # cat os200805.py > name = "os200805" > vcpus = 1 > memory = "1024" > bootloader = "/usr/lib/xen/bin/pygrub" > kernel = "/platform/i86xpv/kernel/amd64/unix" > ramdisk = "/boot/x86.microroot" > extra = "/platform/i86xpv/kernel/amd64/unix -B console=ttya,livemode=text" > disk = [''file:/export/home/allen/Virtualization/ISO/os200805.iso,6:cdrom,r'', > ''file:/export/home/allen/Virtualization/Vdisk/os200805.img,0,w''] > vif = [''''] > on_shutdown = "destroy" > on_reboot = "destroy" > on_crash = "preserve" > > # xm create -c os200805.py > Using config file "./os200805.py". > Started domain os200805 > WARNING: Cannot extract revision on this > hypervisor version: v-unstable-xvm, unexpected version format > v3.3-unstable-xvm chgset ''Sat Nov 01 22:43:09 2008 +0800 17779:ba68f09d5640'' > SunOS Release 5.11 Version snv_86 64-bit > Copyright 1983-2008 Sun Microsystems, Inc. All rights reserved. > Use is subject to license terms. > > panic[cpu0]/thread=fffffffffbc3cbe0: BAD TRAP: type=e (#pf Page fault) > rp=fffffffffbc6ea00 addr=fffffe000c1a6d80 > > #pf Page fault > Bad kernel fault at addr=0xfffffe000c1a6d80 > pid=0, pc=0xfffffffffb885da3, sp=0xfffffffffbc6eaf8, eflags=0x10046 > cr0: 80050033<pg,wp,ne,et,mp,pe> cr4: 2620<vmxe,xmme,fxsr,pae> > cr2: fffffe000c1a6d80 > rdi: fffffe000c1a6d80 rsi: 0 rdx: 800000007c7f8673 > rcx: 3 r8: 0 r9: ffffff00c5fb0000 > rax: 0 rbx: 800000007c7f8673 rbp: fffffffffbc6eb90 > r10: 0 r11: ffffffffc0000000 r12: 0 > r13: 1 r14: fffffe000c1a6d80 r15: 800000007c7f8673 > fsb: 200000000 gsb: fffffffffbc3e030 ds: 0 > es: 0 fs: 0 gs: 0 > trp: e err: 3 rip: fffffffffb885da3 > cs: e030 rfl: 10046 rsp: fffffffffbc6eaf8 > ss: e02b > > fffffffffbc6e8e0 unix:die+ea () > fffffffffbc6e9f0 unix:trap+13cf () > fffffffffbc6ea00 unix:_cmntrap+12f () > fffffffffbc6eb90 unix:atomic_cas_64+3 () > fffffffffbc6ec30 unix:hati_pte_map+153 () > fffffffffbc6ecb0 unix:hati_load_common+15a () > fffffffffbc6ed70 unix:hat_devload+13c () > fffffffffbc6edc0 unix:gnttab_init+dd () > fffffffffbc6edd0 unix:startup_modules+f9 () > fffffffffbc6ede0 unix:startup+3f () > fffffffffbc6ee10 genunix:main+27 () > fffffffffbc6ee20 unix:_locore_start+80 () > > skipping system dump - no dump device configured > rebooting... > > > > Install a snv_94 PV guest with virt-install tool: > ====================================> > # virt-install > 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_94 > How much RAM should be allocated (in megabytes)? 1024 > What would you like to use as the disk (path)? > /export/home/allen/Virtualization/ISO/sol-11-x86-snv-94.iso > Arithmetic Exception - core dumped > >An incorrect input of the disk path was found. I changed to input a valid disk path (this path is non-exist, let the tool to create for me). Virt-install still exited with same error message: virt-install 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_94 How much RAM should be allocated (in megabytes)? 1024 What would you like to use as the disk (path)? /export/home/allen/Virtualization/Vdisk/pv_snv_94.img How large would you like the disk (/export/home/allen/Virtualization/Vdisk/pv_snv_94.img) to be (in gigabytes)? 24 Arithmetic Exception (core dumped)
On Mon, Nov 03, 2008 at 01:25:27PM +0800, Lu Baolu wrote:> Hi Mark and David, > > I ran through the steps this morning. Everything went well, however > the final system (xvm + domain 0) failed to create a PV guest. Below > is what happened when I try to run a PV guest: > > Install an os200805 PV guest with xm tool: > ==================================> fffffffffbc6e8e0 unix:die+ea () > fffffffffbc6e9f0 unix:trap+13cf () > fffffffffbc6ea00 unix:_cmntrap+12f () > fffffffffbc6eb90 unix:atomic_cas_64+3 () > fffffffffbc6ec30 unix:hati_pte_map+153 () > fffffffffbc6ecb0 unix:hati_load_common+15a () > fffffffffbc6ed70 unix:hat_devload+13c () > fffffffffbc6edc0 unix:gnttab_init+dd () > fffffffffbc6edd0 unix:startup_modules+f9 () > fffffffffbc6ede0 unix:startup+3f () > fffffffffbc6ee10 genunix:main+27 () > fffffffffbc6ee20 unix:_locore_start+80 () > > skipping system dump - no dump device configured > rebooting...This looks like http://bugs.opensolaris.org/view_bug.do?bug_id=6650717 Fixed in snv_87, but 2008.05 is based on snv_86. That would appear to rule out installing 2008.05 as a PV guest.> Install a snv_94 PV guest with virt-install tool: > ====================================> > # virt-install > 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_94 > How much RAM should be allocated (in megabytes)? 1024 > What would you like to use as the disk (path)? > /export/home/allen/Virtualization/ISO/sol-11-x86-snv-94.iso > Arithmetic Exception - core dumpedThis question is asking about the disk image rather than the install image. Given that you also tried specifying a disk there (discussed on MSN) and got the same failure, I''m puzzled. What size did you specify for the disk in the second attempt?
Lu Baolu wrote:> On Mon, Nov 3, 2008 at 1:25 PM, Lu Baolu <allen.virt@gmail.com> wrote: >> Hi Mark and David, >> Install a snv_94 PV guest with virt-install tool: >> ====================================>> >> # virt-install >> 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_94 >> How much RAM should be allocated (in megabytes)? 1024 >> What would you like to use as the disk (path)? >> /export/home/allen/Virtualization/ISO/sol-11-x86-snv-94.iso >> Arithmetic Exception - core dumped >> >> > > An incorrect input of the disk path was found. > > I changed to input a valid disk path (this path is non-exist, let the > tool to create for me). Virt-install still exited with same error > message:You''ll need to stick with xm at the moment. We havn''t update libvirt yet.. We need to update to the most recent bits so that they work with the updated hypercalls in Xen. MRJ> virt-install > 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_94 > How much RAM should be allocated (in megabytes)? 1024 > What would you like to use as the disk (path)? > /export/home/allen/Virtualization/Vdisk/pv_snv_94.img > How large would you like the disk > (/export/home/allen/Virtualization/Vdisk/pv_snv_94.img) to be (in > gigabytes)? 24 > Arithmetic Exception (core dumped)
> > You'll need to stick with xm at the moment. We havn't > update libvirt yet.. We need to update to the most recent > bits so that they work with the updated hypercalls in Xen. > >Hi Mark, Thanks for the information. Thinking creation os200805 failure is a known issue, I tried to create a snv_89 PV guest with xm. The result is still failure. [allen@blu-nhm:Virtualization]sudo xm create pv_snv_89.py Using config file "./pv_snv_89.py". pyGRUB version 0.6 ┌────────────────────────────────────────────────────────────────────────┐ │ Solaris Express Developer Edition │ │ Solaris Express │ │ Solaris Express Serial Console ttya │ │ Solaris Express Serial Console ttyb (for lx50, v60x and v65x) │ │ │ │ │ │ │ │ │ └────────────────────────────────────────────────────────────────────────┘ Use the ^ and v keys to select which entry is highlighted. Press enter to boot the selected OS. 'e' to edit the commands before booting, 'a' to modify the kernel arguments before booting, or 'c' for a command line. Will boot selected entry in 58 seconds [enter for selection] [allen@blu-nhm:Virtualization]Error: (2, 'Invalid kernel', 'elf_xen_note_check: ERROR: Will only load images built for the generic loader or Linux images') I googled and got some results. Seems this is a known issue. But I didn't get any fix or workaround. Is there any way that I can install a snv pv guest? Thanks, Allen _______________________________________________ xen-discuss mailing list xen-discuss@opensolaris.org