[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: [Xen-ia64-devel] Community effort neededtocatch upwithxen-unstable


  • To: "Byrne, John (HP Labs)" <john.l.byrne@xxxxxx>, "Tian, Kevin" <kevin.tian@xxxxxxxxx>
  • From: "Magenheimer, Dan (HP Labs Fort Collins)" <dan.magenheimer@xxxxxx>
  • Date: Thu, 1 Sep 2005 14:11:33 -0700
  • Cc: xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
  • Delivery-date: Thu, 01 Sep 2005 21:09:44 +0000
  • List-id: Discussion of the ia64 port of Xen <xen-ia64-devel.lists.xensource.com>
  • Thread-index: AcWvMTOFrA1NTBYWSFqi8GJ1sqb6yAACBR0w
  • Thread-topic: [Xen-ia64-devel] Community effort neededtocatch upwithxen-unstable

I haven't yet merged in the changes that you and Kevin
have been posting so I'm sure tip wouldn't work.  Now
that I've gotten through all the maintenance work,
I will apply the patch to xen... even if it is incomplete,
it won't be any worse than what is there now.

Re crashing at login prompt... are you using a real
disk/partition for domU?  When I last tried this, I
trashed both dom0 and domU disks... it may be the
case that there is some "crosstalk" such that two
domains are (under some circumstances) writing to
the same disk(s).  Just a possibility...

Dan

> -----Original Message-----
> From: xen-ia64-devel-bounces@xxxxxxxxxxxxxxxxxxx 
> [mailto:xen-ia64-devel-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf 
> Of Byrne, John (HP Labs)
> Sent: Thursday, September 01, 2005 2:10 PM
> To: Tian, Kevin
> Cc: xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
> Subject: Re: [Xen-ia64-devel] Community effort neededtocatch 
> upwithxen-unstable
> 
> Tian, Kevin wrote:
> > Hi, John,
> >     It works on my side now, with attached set of patches which also
> > include your's modifications. As a note to some further cleanup upon
> > yours, I kept all get_vm_area/vfree lines though ia64 
> doesn't need them.
> > But this can reduce #ifdefs and at least no harm to ia64. 
> Then I also
> > removed the #ifdef for "addr == 0" check in grant_table.c 
> due to same
> > reason. The tools patch contains some changes to common side, but I
> > think that's necessary for current ia64 model. See whether 
> it works for
> > you then.
> > 
> > Thanks,
> > Kevin
> > 
> > 
> 
> I'm still having problems when it gets to the login prompt, 
> but they're 
> different. I'll look into it. I'm fine with getting rid of 
> the #ifdefs. 
> (Assuming I'm not about to find some reason for them.) Because I had 
> mercurial problems, I first tried things with Dan's 2.6.13 merge and 
> trying to start a guest didn't work at all. I don't know what the 
> problem is.
> 
> 
> 000000, addr=f000ff54f0000000, spinning...
> (XEN) $$$$$ PANIC in domain 0 (k6=f0000000040a8000): *** 
> xen_handle_domain_access: exception table lookup failed, 
> iip=f000ff54f0000000, addr=f000ff54f0000000, spinning...
> (XEN) *** ADD REGISTER DUMP HERE FOR DEBUGGING
> (XEN) BUG at domain.c:311
> (XEN) priv_emulate: priv_handle_op fails, isr=0000000000000000
> (XEN) $$$$$ PANIC in domain 0 (k6=f0000000040a8000): psr.ic off, 
> delivering 
> fault=5300,ipsr=0000121208026010,iip=a00000010000bd00,ifa=f000
> 0000040afcb0,isr=00000a0c00000004,PSCB.iip*** 
> ADD REGISTER DUMP HERE FOR DEBUGGING
> (XEN) BUG at domain.c:311
> (XEN) priv_emulate: priv_handle_op fails, isr=0000000000000000
> (XEN) $$$$$ PANIC in domain 0 (k6=f0000000040a8000): psr.ic off, 
> delivering 
> fault=5400,ipsr=0000101008026018,iip=f00000000400edf0,ifa=f300
> 000000000000,isr=0000000000000000,PSCB.iip*** 
> ADD REGISTER DUMP HERE FOR DEBUGGING
> (XEN) BUG at domain.c:311
> (XEN) priv_emulate: priv_handle_op fails, isr=00000000000000
> ...
> 
> 
> John
> 
> _______________________________________________
> Xen-ia64-devel mailing list
> Xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-ia64-devel
> 

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


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.