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 <[EMAIL PROTECTED]> 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
>
>
_______________________________________________
xen-discuss mailing list
[email protected]
