El domingo 08 de junio del 2008 a las 08:23:28, Boris Derzhavets escribió:
> Daniel, Hi Boris. > You are right. However, install procedure was done by myself at Xen > 3.2.1 Ubuntu 8.04, CentOS 5.1 Dom0 ( thanks to Jurgen Keil and Mark > Jonson) :- http://lxer.com/module/newswire/view/103407/index.html > http://lxer.com/module/newswire/view/103407/index.html and at Xen 3.1 > F8 Dom0 with no problems (no kernel patch needed) I try installing xen-utils-3.2-1 and xen-hypervisor-3.2-1-i386 packages from backports repositories. These have Xen 3.2.0-3 version, according to I can see. This is domU's config file: sirius:/etc/xen# cat febo.cfg.200806 name = 'febo' memory = '256' vif = [ 'mac=00:16:3e:1b:04:c9, ip=10.1.0.70' ] # Install disk = [ 'file:/root/os200805.iso,6:cdrom,r', 'phy:vm1/febo,0,w' ] kernel = '/etc/xen/os1/unix' ramdisk = '/etc/xen/os1/x86.microroot' extra = '/platform/i86xpv/kernel/unix -B console=ttya,livemode=text' on_shutdown = 'destroy' on_reboot = 'destroy' on_crash = 'destroy' Booting I got a panic message: sirius:/etc/xen# xm create -c febo.cfg.200806 Using config file "./febo.cfg.200806". v3.2-1 chgset 'unavailable' Started domain febo SunOS Release 5.11 Version snv_86 32-bit Copyright 1983-2008 Sun Microsystems, Inc. All rights reserved. Use is subject to license terms. panic[cpu0]/thread=f5028f60sirius:/etc/xen# In [1] I noticed the following difference in the configuration file: extra = "/platform/i86xpv/kernel/unix -kd - nowin -B install_media=cdrom" Introducing 'gnttab_init+0xce/W 403' during the Solaris bootstrapping, I got this stack trace: sirius:/etc/xen# xm create -c febo.cfg.200806 Using config file "./febo.cfg.200806". Started domain febo Loading kmdb... Welcome to kmdb Loaded modules: [ unix krtld genunix ] [0]> gnttab_init+0xce/W 403 gnttab_init+0xce: 0x6ac472 = 0x403 [0]> :c v3.2-1 chgset 'unavailable' SunOS Release 5.11 Version snv_86 32-bit Copyright 1983-2008 Sun Microsystems, Inc. All rights reserved. Use is subject to license terms. panic[cpu0]/thread=f5028f60: BAD TRAP: type=e (#pf Page fault) rp=f5053654 addr=d4800570 #pf Page fault Bad kernel fault at addr=0xd4800570 pid=0, pc=0xf4c70916, sp=0x0, eflags=0x10002 cr0: 80050033<pg,wp,ne,et,mp,pe> cr4: 660<xmme,fxsr,mce,pae> cr2: d4800570 gs: f4c101b1 fs: 1bd10000 es: 80000161 ds: d4800161 edi: 1bc673 esi: d4800570 ebp: f5053700 esp: f505368c ebx: 1bc673 edx: 0 ecx: 80000000 eax: 0 trp: e err: 3 eip: f4c70916 cs: 159 efl: 10002 usp: 0 ss: 0 f50535ac unix:die+ed (e, f5053654, d48005) f5053640 unix:trap+12b9 (f5053654, d4800570,) f5053654 unix:_cmntrap+aa (f4c101b1, 1bd10000,) f5053700 unix:atomic_cas_64+16 (d4611ea0, ae, 1bc67) f505375c unix:hati_pte_map+143 (d4611ea0, ae, 0, 1b) f50537a0 unix:hati_load_common+12f (d4460f68, d52ae000,) f5053804 unix:hat_devload+10b (d4460f68, d52ae000,) f5053858 unix:gnttab_init+bb (f4c4feae, 3, f50538) f5053868 unix:startup_modules+fb (f5053880, f4d3d812,) f5053870 unix:startup+35 (f4c00010, f504f688,) f5053880 genunix:main+1e () panic: entering debugger (no dump device, continue to reboot) Loaded modules: [ specfs ] kmdb: target stopped at: kmdb_enter+0xa: pushl %eax [0]> Would I have to download the kernel packages mentioned in [1]? Regards, Daniel [1] http://lxer.com/module/newswire/view/103407/index.html -- Daniel Bareiro - System Administrator Fingerprint: BFB3 08D6 B4D1 31B2 72B9 29CE 6696 BF1B 14E6 1D37 Powered by Debian GNU/Linux Lenny - Linux user #188.598
signature.asc
Description: Digital signature
_______________________________________________ xen-discuss mailing list xen-discuss@opensolaris.org
