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

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


  • To: "John Byrne" <john.l.byrne@xxxxxx>
  • From: "Tian, Kevin" <kevin.tian@xxxxxxxxx>
  • Date: Thu, 1 Sep 2005 10:40:24 +0800
  • Cc: xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
  • Delivery-date: Thu, 01 Sep 2005 02:38:34 +0000
  • List-id: Discussion of the ia64 port of Xen <xen-ia64-devel.lists.xensource.com>
  • Thread-index: AcWum2Y6JSkhxbviRTqxHyIn1ePpEAAApCPA
  • Thread-topic: [Xen-ia64-devel] Community effort neededtocatch upwithxen-unstable

>From: John Byrne [mailto:john.l.byrne@xxxxxx]
>>
>> You can "make XEN_NO_IOEMU=y". So this change is not required.
>
>Yeah, but I have to remember to do it.

VTI unmodified domain will required device model, and use __ia64__ here
actually affect the former. Later when we bring qemu back to compile,
there's then no need for this option. So please just take a bit extra
effort to assign the option in cmdline, or you can simply modify it
locally but not send out as a patch. ;-)

>
>Here are my patches. I spoke too soon about being done. I think the
>console driver has a problem in it. My system rebooted when I got to
the
>console login. I'm only online for about 1/2 hour more. Let me know if
>you have the same problem or find a fix.
>
>John
>

I'm trying now...

Thanks,
Kevin

_______________________________________________
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®.