Alex Williamson wrote:
On Fri, 2006-12-01 at 15:13 +0100, [EMAIL PROTECTED] wrote:
Original files copied from Linux, requires for initial SN2 and machine
vector support.
Hi Jes,
I'm having trouble figuring out which Linux version each of these
came from. I think it's important that
Hi Tristan:
I add eepro100 in my QEMU device model. It can work under linux. But
windows2003 still cannot recognize it. Which version of win2k3 you used? Mine
is SP1, I'm not sure this version include eepro100's driver. Meanwhile, I
google the driver but still not found appropriate copy
Hi,
I had a closer look to my problem described on
http://lists.xensource.com/archives/html/xen-ia64-devel/2006-12/msg00120.html.
Now I can reproduce the panic in Xen with a dom0-user program.
The instructions
movl r16=0xff;;
mov ar.rsc=r16
lead to a general exception with function code 0x30
Hi, Markus
I am checking VFB with SMP
with xen-ia64-unstable cset 12886.
But It seems strange behavior.
(call trace appeared from DomU xm console output)
Did you test it on SMP DomU?
Of course UP DomU seems fine at this moment.
Thanks
Atsushi SAKAI
Hi Akio,
I think your suggestion is almost right.
But should the folloing IA64_ISR_CODE_LFETCH be checked?
(because Privilege Register Fault may be occurred on guest.)
ia64_fault()
393 if ((isr IA64_ISR_NA)
394 ((isr IA64_ISR_CODE_MASK) == IA64_ISR_CODE_LFETCH)) {
Xen/IA64 Healthiness Report
Several issues:
1. VTI Linux domain boot slowly, if enabled 'serial=pty'.
2. Even without serial='pty', the VTI domain boots very slowly. (UPVTI
needs 150s and VTI_Win2k3svr needs 8 minutes or so)
3. SMPVTI_LTP performed slowly.
Except
Hi, Dietmar
Hi Akio,
I think your suggestion is almost right.
But should the folloing IA64_ISR_CODE_LFETCH be checked?
(because Privilege Register Fault may be occurred on guest.)
ia64_fault()
393 if ((isr IA64_ISR_NA)
394 ((isr IA64_ISR_CODE_MASK) ==
