RE: [Xen-users] OpenSolaris 10 on x86_32 Xen-VTx

["Puthiyaparambil, Aravindh" <aravindh.puthiyaparambil@xxxxxxxxxx>]

Nope, I am not able to get a stack trace when qemu-dies. I tried the
CTRL-F2 and CTRL-3 in the SDL windows but that produces no results.
Looks like I will have to start adding prinks in image.py to begin with.

Thanks,
Aravindh

> -----Original Message-----
> From: Andrew D. Ball [mailto:aball@xxxxxxxxxx]
> Sent: Friday, January 27, 2006 2:18 PM
> To: Puthiyaparambil, Aravindh
> Subject: RE: [Xen-users] OpenSolaris 10 on x86_32 Xen-VTx
> 
> Hrm -- that's a good reason for the patch to not make it in.  Are you
> able to get a stack trace if you don't set a breakpoint and qemu-dm
dies
> as usual?
> 
> I think there may be some logging capability taken directly from QEMU
as
> well -- try pressing CTRL-F2 and CTRL-3 in the SDL window that pops
up.
> Debugging the device model has never been simple for me. I was hoping
> that I could just use gdb with it, but if that's not really feasible
due
> to timing issues, we'll have to think of something else.
> 
> I'm assuming that the qemu-dm processes die for some reason like a
> segmentation fault, but with them being launched by xend it's harder
to
> find that out, since 'ulimit -c unlimited" has never make them dump
core
> that I have been able to find.
> 
> I really just want a core dump :-)
> 
> There's always the old well-placed printf method or regular qemu logs
> that you ask qemu-dm to produce with arguments [provided that code is
> still there].  The last time I checked it wasn't incredibly easy to
pass
> new arguments to qemu-dm -- I think I needed to modify
> tools/python/xen/xend/image.py in the 'createDeviceModel' function.
> 
> Good luck!
> Andrew
> 
> On Thu, 2006-01-26 at 18:10 -0500, Puthiyaparambil, Aravindh wrote:
> > I am able to do only "one" thing after ddd starts up. If I say "run"
> > without any breakpoint then qemu executes and the Solaris install
hangs
> > as always. If I set a breakpoint, then the code stops there. In both
the
> > cases ddd/gdb is not responsive to any commands :-(
> >
> > Thanks,
> > Aravindh
> >
> > > -----Original Message-----
> > > From: Andrew D. Ball [mailto:aball@xxxxxxxxxx]
> > > Sent: Thursday, January 26, 2006 5:33 PM
> > > To: Puthiyaparambil, Aravindh
> > > Subject: RE: [Xen-users] OpenSolaris 10 on x86_32 Xen-VTx
> > >
> > > You're probably not doing anything wrong.  Can you continue
execution
> > > here?  What I really wanted when working on the patch was to be
able
> > to
> > > get a stack trace from a dead qemu-dm process.  I kept seeing
defunct
> > > qemu-dm processes and 'ulimit -c' wasn't working to get core dumps
> > from
> > > them.
> > >
> > > I think ddd is much like command-line gdb, or at least can be if
> > that's
> > > what you're familiar with.  It's got some buttons for common
> > > functionality and displays the source code, but it still
communicates
> > > with gcc at the bottom.
> > >
> > > Good luck!
> > > Andrew
> > >
> > > On Thu, 2006-01-26 at 16:12 -0500, Puthiyaparambil, Aravindh
wrote:
> > > > Andrew,
> > > >
> > > > I followed your instructions in the patch and now when I bring
up
> > the
> > > > DomVT, ddd fires. I am able to set breakpoints and the program
> > execution
> > > > stops at the first one. But I am not able to do much beyond as
ddd
> > > > reports "waiting until GDB is ready". Am I doing anything wrong
> > here?
> > > >
> > > > Thanks,
> > > > Aravindh
> > > >
> > > > > -----Original Message-----
> > > > > From: Andrew D. Ball [mailto:aball@xxxxxxxxxx]
> > > > > Sent: Wednesday, January 25, 2006 12:14 PM
> > > > > To: Puthiyaparambil, Aravindh
> > > > > Subject: RE: [Xen-users] OpenSolaris 10 on x86_32 Xen-VTx
> > > > >
> > > > > That means that the device model has died on you.  There's
only
> > one
> > > > > device model at the moment -- it's mostly code taken from the
qemu
> > > > > hypervisor to emulate whatever hardware is needed for full
> > > > > virtualization.
> > > > >
> > > > > You may want to try getting and building this tree of Xen
> > > > >
> > > > > http://xenbits.xensource.com/ext/xen-unstable-hvm.hg
> > > > >
> > > > > I have seen much more stability with the device model with
this
> > one.
> > > > > You will need to use 'hvm' instead of 'vmx' for configurations
> > here,
> > > > but
> > > > > I don't know of any other differences in the interface.
> > > > >
> > > > > I put out a patch some time ago to try to help debug the
device
> > model,
> > > > > if you'd like to try to find out where and why it's crashing:
> > > > >
> > > > >
> > > >
> >
http://lists.xensource.com/archives/html/xen-devel/2006-01/msg00103.html
> > > > >
> > > > > Good luck!
> > > > > Andrew
> > > > > --
> > > > > Andrew D. Ball
> > > > > aball@xxxxxxxxxx
> > > > >
> > > > > "Festina Lente" $\approx$ "Make hast slowly"
> > > > >   -- Caesar Augustus
> > > > >
> > > > >
> > > > > On Wed, 2006-01-25 at 11:32 -0500, Puthiyaparambil, Aravindh
> > wrote:
> > > > > > Andrew,
> > > > > >
> > > > > > Yes, I see defunct qemu-dm processes. But I am not sure what
it
> > > > means.
> > > > > > Will OS10 require a separate device model?
> > > > > >
> > > > > > Thanks,
> > > > > > Aravindh
> > > > > >
> > > > > > root     15753  0.0  0.0      0     0 ?        Z    Jan24
0:04
> > > > > > [qemu-dm] <defunct>
> > > > > > root     16334  0.0  0.0      0     0 ?        Z    Jan24
0:06
> > > > > > [qemu-dm] <defunct>
> > > > > > root     16917  0.0  0.0      0     0 ?        Z    Jan24
0:01
> > > > > > [qemu-dm] <defunct>
> > > > > > root     17022  0.0  0.0      0     0 ?        Z    Jan24
0:01
> > > > > > [qemu-dm] <defunct>
> > > > > > root     17156  0.0  0.0      0     0 ?        Z    Jan24
0:17
> > > > > > [qemu-dm] <defunct>
> > > > > > root     18893  0.0  0.0      0     0 ?        Z    Jan24
0:00
> > > > > > [qemu-dm] <defunct>
> > > > > > root     18943  0.0  0.0      0     0 ?        Z    Jan24
0:01
> > > > > > [qemu-dm] <defunct>
> > > > > > root     19400  0.0  0.0      0     0 ?        Z    Jan24
0:01
> > > > > > [qemu-dm] <defunct>
> > > > > > root     19541  0.0  0.0      0     0 ?        Z    Jan24
0:01
> > > > > > [qemu-dm] <defunct>
> > > > > > root     27794  1.3  1.0  31604  5576 ?        S    12:36
0:01
> > > > > > /usr/lib/xen/bin/qemu-dm -d 18 -p 3 -m 512 -cdrom /dev/hdd
-boot
> > d
> > > > > > -nic-ne2000 -vcpus 1 -domain-name OpenSolaris10 -hda
> > > > > > /root/xen/vm/vmxsol.img -nics 0
> > > > > > root     27806  0.0  1.0  31604  5576 ?        S    12:36
0:00
> > > > > > /usr/lib/xen/bin/qemu-dm -d 18 -p 3 -m 512 -cdrom /dev/hdd
-boot
> > d
> > > > > > -nic-ne2000 -vcpus 1 -domain-name OpenSolaris10 -hda
> > > > > > /root/xen/vm/vmxsol.img -nics 0
> > > > > > root     27807  0.0  1.0  31604  5576 ?        S    12:36
0:00
> > > > > > /usr/lib/xen/bin/qemu-dm -d 18 -p 3 -m 512 -cdrom /dev/hdd
-boot
> > d
> > > > > > -nic-ne2000 -vcpus 1 -domain-name OpenSolaris10 -hda
> > > > > > /root/xen/vm/vmxsol.img -nics 0
> > > > > >
> > > > > > > -----Original Message-----
> > > > > > > From: Andrew D. Ball [mailto:aball@xxxxxxxxxx]
> > > > > > > Sent: Wednesday, January 25, 2006 9:36 AM
> > > > > > > To: Puthiyaparambil, Aravindh
> > > > > > > Subject: Re: [Xen-users] OpenSolaris 10 on x86_32 Xen-VTx
> > > > > > >
> > > > > > > Do you see any defunct processes if you do
> > > > > > >
> > > > > > > ps aux | grep qemu-dm
> > > > > > >
> > > > > > > ?
> > > > > > >
> > > > > > > Good luck.
> > > > > > > Andrew
> > > > > > > --
> > > > > > > Andrew D. Ball
> > > > > > > aball@xxxxxxxxxx
> > > > > > >
> > > > > > > "Festina Lente" $\approx$ "Make hast slowly"
> > > > > > >   -- Caesar Augustus
> > > > > > >
> > > > > > > On Tue, 2006-01-24 at 17:48 -0500, Puthiyaparambil,
Aravindh
> > > > wrote:
> > > > > > > > I am trying to install x86_32 OpenSolaris 10 in a VT
domain
> > on
> > > > > > x86_32
> > > > > > > > Xen (changeset 8634). The domain boots off the install
CD
> > and I
> > > > see
> > > > > > the
> > > > > > > > grub menu where I choose "Solaris". I then see the
"Booting
> > > > Solaris"
> > > > > > and
> > > > > > > > the loading kernel and modules lines but after that the
Qemu
> > > > window
> > > > > > goes
> > > > > > > > blank. I have listed my config file below. Any idea how
to
> > get
> > > > > > around
> > > > > > > > this issue?
> > > > > > > >
> > > > > > > > Thanks,
> > > > > > > > Aravindh
> > > > > > > >
> > > > > > > >
> > > > > > > > OpesnSolaris10 DomVT Config file
> > > > > > > > --------------------------------
> > > > > > > > import os, re
> > > > > > > > arch = os.uname()[4]
> > > > > > > > if re.search('64', arch):
> > > > > > > >     arch_libdir = 'lib64'
> > > > > > > > else:
> > > > > > > >     arch_libdir = 'lib'
> > > > > > > >
> > > > > > > > kernel = "/usr/lib/xen/boot/vmxloader"
> > > > > > > > builder='vmx'
> > > > > > > > memory = 512
> > > > > > > > name = "OpenSolaris10"
> > > > > > > > vif = [ 'type=ioemu, bridge=xenbr0' ]
> > > > > > > > disk = [ 'file:/root/xen/vm/vmxsol.img,ioemu:hda,w' ]
> > > > > > > > device_model = '/usr/' + arch_libdir +
'/xen/bin/qemu-dm'
> > > > > > > > cdrom = '/dev/hdd'
> > > > > > > > boot = 'd'
> > > > > > > > sdl=1
> > > > > > > > vnc=0
> > > > > > > > vncviewer=0
> > > > > > > > ne2000=0
> > > > > > > >
> > > > > > > > _______________________________________________
> > > > > > > > Xen-users mailing list
> > > > > > > > Xen-users@xxxxxxxxxxxxxxxxxxx
> > > > > > > > http://lists.xensource.com/xen-users
> > > > > > > >
> > > > > > >
> > > > > >
> > > > > >
> > > > >
> > > >
> > > >
> >
> >


_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users