WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 		  
Home Products Support Community News
 
   
 

xen-devel

[Top] [All Lists]
<prev [Date] next>
[Advanced]
 <prev [Thread] next>

Re: [Xen-devel] Latest pvops hangs on boot

from [Jeremy Fitzhardinge] [Permanent Link][Original]
To: "Williams, Mitch A" <mitch.a.williams@xxxxxxxxx>
Subject: Re: [Xen-devel] Latest pvops hangs on boot
From: Jeremy Fitzhardinge <jeremy@xxxxxxxx>
Date: Wed, 11 Nov 2009 13:54:23 -0800
Cc: "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>, Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx>
Delivery-date: Wed, 11 Nov 2009 13:56:27 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <EA929A9653AAE14F841771FB1DE5A1365FA65FF9FE@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <EA929A9653AAE14F841771FB1DE5A1365FA65FF9FE@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.4pre) Gecko/20091014 Fedora/3.0-2.8.b4.fc11 Lightning/1.0pre Thunderbird/3.0b4 
On 11/11/09 13:16, Williams, Mitch A wrote:
> Looking for a little advice here.  I've compiled the latest xen-unstable tree 
> along with the latest pvops kernel from Jeremy's git tree.
>
> Xen boots and loads the Linux kernel but then the system spews a bunch of 
> errors and hangs.  I've set up my serial cable to capture the log, which is 
> appended to this email.
>
> This is a SuperMicro Nehalem box, nothing funny hardware-wise. The kernel 
> boots fine on bare metal.
>
> My current .config is attached. I've been tweaking config options for three 
> days and haven't had any luck. Any ideas?
>   

Those all look like reasonable messages for a successful boot, but only
from the Xen side; there should be corresponding dom0 kernel console
messages somewhere.  The machine could be up and running; have you tried
pinging it?

Ah, I see Konrad has also replied; try those kernel parameters to get
the console output working.  (Note the console has changed from xvc0 to
hvc0, if you're using an installation from an older kernel.)

    J
> Thanks,
> Mitch
>
> Boot log follows:
>
> (XEN) io_apic.c:2251:
> (XEN) ioapic_guest_write: apic=0, pin=0, irq=0
> (XEN) ioapic_guest_write: new_entry=00010900
> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ!
> (XEN) io_apic.c:2251:
> (XEN) ioapic_guest_write: apic=0, pin=2, irq=0
> (XEN) ioapic_guest_write: new_entry=00010900
> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ!
> (XEN) irq.c:1426: dom0: pirq 0 or irq 3 already mapped
> (XEN) io_apic.c:2251:
> (XEN) ioapic_guest_write: apic=0, pin=4, irq=4
> (XEN) ioapic_guest_write: new_entry=00010900
> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ!
> (XEN) irq.c:1426: dom0: pirq 0 or irq 5 already mapped
> (XEN) irq.c:1426: dom0: pirq 0 or irq 6 already mapped
> (XEN) irq.c:1426: dom0: pirq 0 or irq 7 already mapped
> (XEN) irq.c:1426: dom0: pirq 0 or irq 8 already mapped
> (XEN) irq.c:1426: dom0: pirq 0 or irq 9 already mapped
> (XEN) irq.c:1426: dom0: pirq 0 or irq 10 already mapped
> (XEN) irq.c:1426: dom0: pirq 0 or irq 11 already mapped
> (XEN) irq.c:1426: dom0: pirq 0 or irq 12 already mapped
> (XEN) irq.c:1426: dom0: pirq 0 or irq 13 already mapped
> (XEN) irq.c:1426: dom0: pirq 0 or irq 14 already mapped
> (XEN) irq.c:1426: dom0: pirq 0 or irq 15 already mapped
> (XEN) allocated vector for irq:16
> (XEN) irq.c:1426: dom0: pirq 0 or irq 16 already mapped
> (XEN) allocated vector for irq:17
> (XEN) irq.c:1426: dom0: pirq 0 or irq 17 already mapped
> (XEN) allocated vector for irq:18
> (XEN) irq.c:1426: dom0: pirq 0 or irq 18 already mapped
> (XEN) allocated vector for irq:19
> (XEN) irq.c:1426: dom0: pirq 0 or irq 19 already mapped
> (XEN) allocated vector for irq:20
> (XEN) irq.c:1426: dom0: pirq 0 or irq 20 already mapped
> (XEN) allocated vector for irq:21
> (XEN) irq.c:1426: dom0: pirq 0 or irq 21 already mapped
> (XEN) allocated vector for irq:22
> (XEN) irq.c:1426: dom0: pirq 0 or irq 22 already mapped
> (XEN) allocated vector for irq:23
> (XEN) irq.c:1426: dom0: pirq 0 or irq 23 already mapped
> (XEN) allocated vector for irq:24
> (XEN) irq.c:1426: dom0: pirq 0 or irq 24 already mapped
> (XEN) allocated vector for irq:25
> (XEN) irq.c:1426: dom0: pirq 0 or irq 25 already mapped
> (XEN) allocated vector for irq:26
> (XEN) irq.c:1426: dom0: pirq 0 or irq 26 already mapped
> (XEN) allocated vector for irq:27
> (XEN) irq.c:1426: dom0: pirq 0 or irq 27 already mapped
> (XEN) allocated vector for irq:28
> (XEN) irq.c:1426: dom0: pirq 0 or irq 28 already mapped
> (XEN) allocated vector for irq:29
> (XEN) irq.c:1426: dom0: pirq 0 or irq 29 already mapped
> (XEN) allocated vector for irq:30
> (XEN) irq.c:1426: dom0: pirq 0 or irq 30 already mapped
> (XEN) allocated vector for irq:31
> (XEN) irq.c:1426: dom0: pirq 0 or irq 31 already mapped
> (XEN) allocated vector for irq:32
> (XEN) irq.c:1426: dom0: pirq 0 or irq 32 already mapped
> (XEN) allocated vector for irq:33
> (XEN) irq.c:1426: dom0: pirq 0 or irq 33 already mapped
> (XEN) allocated vector for irq:34
> (XEN) irq.c:1426: dom0: pirq 0 or irq 34 already mapped
> (XEN) allocated vector for irq:35
> (XEN) irq.c:1426: dom0: pirq 0 or irq 35 already mapped
> (XEN) allocated vector for irq:36
> (XEN) irq.c:1426: dom0: pirq 0 or irq 36 already mapped
> (XEN) allocated vector for irq:37
> (XEN) irq.c:1426: dom0: pirq 0 or irq 37 already mapped
> (XEN) allocated vector for irq:38
> (XEN) irq.c:1426: dom0: pirq 0 or irq 38 already mapped
> (XEN) allocated vector for irq:39
> (XEN) irq.c:1426: dom0: pirq 0 or irq 39 already mapped
> (XEN) allocated vector for irq:40
> (XEN) irq.c:1426: dom0: pirq 0 or irq 40 already mapped
> (XEN) allocated vector for irq:41
> (XEN) irq.c:1426: dom0: pirq 0 or irq 41 already mapped
> (XEN) allocated vector for irq:42
> (XEN) irq.c:1426: dom0: pirq 0 or irq 42 already mapped
> (XEN) allocated vector for irq:43
> (XEN) irq.c:1426: dom0: pirq 0 or irq 43 already mapped
> (XEN) allocated vector for irq:44
> (XEN) irq.c:1426: dom0: pirq 0 or irq 44 already mapped
> (XEN) allocated vector for irq:45
> (XEN) irq.c:1426: dom0: pirq 0 or irq 45 already mapped
> (XEN) allocated vector for irq:46
> (XEN) irq.c:1426: dom0: pirq 0 or irq 46 already mapped
> (XEN) allocated vector for irq:47
> (XEN) irq.c:1426: dom0: pirq 0 or irq 47 already mapped
> (XEN) allocated vector for irq:48
> (XEN) irq.c:1426: dom0: pirq 0 or irq 48 already mapped
> (XEN) allocated vector for irq:49
> (XEN) irq.c:1426: dom0: pirq 0 or irq 49 already mapped
> (XEN) allocated vector for irq:50
> (XEN) irq.c:1426: dom0: pirq 0 or irq 50 already mapped
> (XEN) allocated vector for irq:51
> (XEN) irq.c:1426: dom0: pirq 0 or irq 51 already mapped
> (XEN) allocated vector for irq:52
> (XEN) irq.c:1426: dom0: pirq 0 or irq 52 already mapped
> (XEN) allocated vector for irq:53
> (XEN) irq.c:1426: dom0: pirq 0 or irq 53 already mapped
> (XEN) allocated vector for irq:54
> (XEN) irq.c:1426: dom0: pirq 0 or irq 54 already mapped
> (XEN) allocated vector for irq:55
> (XEN) irq.c:1426: dom0: pirq 0 or irq 55 already mapped
> (XEN) allocated vector for irq:56
> (XEN) irq.c:1426: dom0: pirq 0 or irq 56 already mapped
> (XEN) allocated vector for irq:57
> (XEN) irq.c:1426: dom0: pirq 0 or irq 57 already mapped
> (XEN) allocated vector for irq:58
> (XEN) irq.c:1426: dom0: pirq 0 or irq 58 already mapped
> (XEN) allocated vector for irq:59
> (XEN) irq.c:1426: dom0: pirq 0 or irq 59 already mapped
> (XEN) allocated vector for irq:60
> (XEN) irq.c:1426: dom0: pirq 0 or irq 60 already mapped
> (XEN) allocated vector for irq:61
> (XEN) irq.c:1426: dom0: pirq 0 or irq 61 already mapped
> (XEN) allocated vector for irq:62
> (XEN) irq.c:1426: dom0: pirq 0 or irq 62 already mapped
> (XEN) allocated vector for irq:63
> (XEN) irq.c:1426: dom0: pirq 0 or irq 63 already mapped
> (XEN) allocated vector for irq:64
> (XEN) irq.c:1426: dom0: pirq 0 or irq 64 already mapped
> (XEN) allocated vector for irq:65
> (XEN) irq.c:1426: dom0: pirq 0 or irq 65 already mapped
> (XEN) allocated vector for irq:66
> (XEN) irq.c:1426: dom0: pirq 0 or irq 66 already mapped
> (XEN) allocated vector for irq:67
> (XEN) irq.c:1426: dom0: pirq 0 or irq 67 already mapped
> (XEN) allocated vector for irq:68
> (XEN) irq.c:1426: dom0: pirq 0 or irq 68 already mapped
> (XEN) allocated vector for irq:69
> (XEN) irq.c:1426: dom0: pirq 0 or irq 69 already mapped
> (XEN) allocated vector for irq:70
> (XEN) irq.c:1426: dom0: pirq 0 or irq 70 already mapped
> (XEN) allocated vector for irq:71
> (XEN) irq.c:1426: dom0: pirq 0 or irq 71 already mapped
> (XEN) io_apic.c:2251:
> (XEN) ioapic_guest_write: apic=0, pin=0, irq=0
> (XEN) ioapic_guest_write: new_entry=00000900
> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ!
> (XEN) io_apic.c:2251:
> (XEN) ioapic_guest_write: apic=0, pin=4, irq=4
> (XEN) ioapic_guest_write: new_entry=00000904
> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ!
>
> <System is completely hung at this point and I have to hit the reset button.>
>
>
>   
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-devel
>   


_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
[More with this subject...]
<Prev in Thread] Current Thread [Next in Thread>
Previous by Date:  Re: [Xen-devel] Crashing DomU, Jeremy Fitzhardinge
Next by Date:  RE: [Xen-devel] Latest pvops hangs on boot, Williams, Mitch A
Previous by Thread:  Re: [Xen-devel] Latest pvops hangs on boot, Konrad Rzeszutek Wilk
Next by Thread:  RE: [Xen-devel] Latest pvops hangs on boot, Williams, Mitch A
Indexes:  [Date] [Thread] [Top] [All Lists]
 
   

Copyright , Citrix Systems Inc. All rights reserved. Legal and Privacy