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

RE: [Xen-devel] Xen cannot boot with pvops dom0

To: 'Jeremy Fitzhardinge' <jeremy@xxxxxxxx>
Subject: RE: [Xen-devel] Xen cannot boot with pvops dom0
From: "Han, Weidong" <weidong.han@xxxxxxxxx>
Date: Wed, 1 Jul 2009 10:43:20 +0800
Accept-language: en-US
Acceptlanguage: en-US
Cc: "'xen-devel@xxxxxxxxxxxxxxxxxxx'" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Tue, 30 Jun 2009 19:44:15 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <4A4A2B03.80602@xxxxxxxx>
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: <715D42877B251141A38726ABF5CABF2C0545A1F383@xxxxxxxxxxxxxxxxxxxxxxxxxxxx> <4A4A2B03.80602@xxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: Acn5lQBMB2Q4D+0NS2Sd2v6KaJ5bFQAXYzMw
Thread-topic: [Xen-devel] Xen cannot boot with pvops dom0
Jeremy Fitzhardinge wrote:
> On 06/25/09 02:20, Han, Weidong wrote:
>> I tried with latest Xen unstable (c/s 19833) with latest pvops dom0
>> (commit 384a55c0). Booting will hang, following is the serial
>> console output:  
>> 
>> (XEN) *** Serial input -> DOM0 (type 'CTRL-a' three times to switch
>> input to Xen ) (XEN) Freed 128kB init memory.
>> mapping kernel into physical memory
>> Xen: setup ISA identity maps
>> about to get started...
>> (XEN) ioapic_guest_write: apic=0, pin=2, old_irq=0, new_irq=-1
>> (XEN) ioapic_guest_write: old_entry=000009f0, new_entry=00010900
>> (XEN) ioapic_guest_write: Attempt to remove IO-APIC pin of in-use
>> IRQ! (XEN) ioapic_guest_write: apic=0, pin=4, old_irq=4, new_irq=-1
>> (XEN) ioapic_guest_write: old_entry=000009f1, new_entry=00010900
>> (XEN) ioapic_guest_write: Attempt to remove IO-APIC pin of in-use
>> IRQ! (XEN) ioapic_guest_write: apic=0, pin=0, old_irq=-1, new_irq=0
>> (XEN) ioapic_guest_write: old_entry=00010900, new_entry=000009f0
>> (XEN) ioapic_guest_write: Attempt to add IO-APIC pin for in-use IRQ!
>> (XEN) ioapic_guest_write: apic=0, pin=19, old_irq=19, new_irq=19
>> (XEN) ioapic_guest_write: old_entry=0000a9c0, new_entry=0001a9c0
>> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use
>> IRQ! (XEN) ioapic_guest_write: apic=0, pin=19, old_irq=19, new_irq=19
>> (XEN) ioapic_guest_write: old_entry=0000a9c0, new_entry=0001a9c0
>> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use
>> IRQ! (XEN) ioapic_guest_write: apic=0, pin=23, old_irq=23, new_irq=23
>> (XEN) ioapic_guest_write: old_entry=0000a9d0, new_entry=0001a9d0
>> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use
>> IRQ! (XEN) ioapic_guest_write: apic=0, pin=19, old_irq=19, new_irq=19
>> (XEN) ioapic_guest_write: old_entry=0000a9c0, new_entry=0001a9c0
>> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use
>> IRQ! (XEN) ioapic_guest_write: apic=0, pin=16, old_irq=16, new_irq=16
>> (XEN) ioapic_guest_write: old_entry=0000a9b8, new_entry=0001a9b8
>> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use
>> IRQ! (XEN) ioapic_guest_write: apic=0, pin=18, old_irq=18, new_irq=18
>> (XEN) ioapic_guest_write: old_entry=0000a921, new_entry=0001a921
>> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use
>> IRQ! 
>> 
> 
> The ioapic_guest_write messages are just noise, and have no bearing on
> the problem.  Are there no more messages from the kernel after "about
> to get started"?  The ioapic messages at least tell us it is getting
> quite a distance into the boot and discovering devices.

Actually, pv-ops dom0 boot successfully. I remotely access my machine via 
serial console. Normally after dom0 boot, it display "login:" line. But serial 
console stops at ioapic_guest_write messages when boot pv_ops, I thought it's 
hung. 

But I found xend still cannot be started. I got the following messages when I 
start it:

[root@vt-randy ~]# xend start
ERROR Internal error: Could not obtain handle on privileged command interface 
(2 = No such file or directory)
Traceback (most recent call last):
  File "/usr/sbin/xend", line 36, in ?
    from xen.xend.server import SrvDaemon
  File "usr/lib64/python2.4/site-packages/xen/xend/server/SrvDaemon.py", line 
26, in ?
  File "usr/lib64/python2.4/site-packages/xen/xend/server/relocate.py", line 
28, in ?
  File "usr/lib64/python2.4/site-packages/xen/xend/XendDomain.py", line 35, in ?
  File "usr/lib64/python2.4/site-packages/xen/xend/XendCheckpoint.py", line 20, 
in ?
  File "usr/lib64/python2.4/site-packages/xen/xend/image.py", line 46, in ?
xen.lowlevel.xc.Error: (1, 'Internal error', 'Could not obtain handle on 
privileged command interface (2 = No such file or directory)')


> 
>> Did anyone meet this issue? Is there any difference on build and
>> installation between pvops dom0 and 2.6.18 dom0? Following is my
>> instructions, pls correct me if something is wrong. Appreciate in
>> advance.   
>> 
>> My build and installation instructions:
>>      - cd xen-unstable.hg
>>      - make world (linux-2.6-pvops.git will be cloned)
>>      - make install
>> 
>> My grub entry:
>>      title Xen - pvops
>>              root (hd0,2)
>>              kernel /boot/xen.gz dom0_mem=512m
>>              module /boot/vmlinuz-2.6-30.rc3-tip ro root=/dev/sda3
>> console=tty0 console=ttyS0 
>> 
> 
> What happens if you have "console=hvc0 earlyprintk=xen
> ignore_loglevel" on the "module" line?  You should get more output
> from the kernel.  You might also want "console=com1,vga" on the Xen
> line. 
> 
>     J


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