mailing@securitylabs.it
2010-Mar-15 14:37 UTC
[Xen-users] Could not obtain handle on privileged command interface
Hello, when I try to start xend I receive this error: root@xenized:~# 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 <module> from xen.xend.server import SrvDaemon File "usr/lib/python2.5/site-packages/xen/xend/server/SrvDaemon.py", line 26, in <module> File "usr/lib/python2.5/site-packages/xen/xend/server/relocate.py", line 28, in <module> File "usr/lib/python2.5/site-packages/xen/xend/XendDomain.py", line 35, in <module> File "usr/lib/python2.5/site-packages/xen/xend/XendCheckpoint.py", line 20, in <module> File "usr/lib/python2.5/site-packages/xen/xend/image.py", line 46, in <module> xen.lowlevel.xc.Error: (1, ''Internal error'', ''Could not obtain handle on privileged command interface (2 = No such file or directory)'') Googling seems that I''ve not booted with the Xen kernel, but It''s not my case: uname -a Linux xenized 2.6.31.12-custom #1 SMP Mon Mar 15 15:00:37 CET 2010 x86_64 GNU/Linux dmesg | grep -i xen [ 0.000000] Linux version 2.6.31.12-custom (root@xenized) (gcc version 4.4.3 20100108 (prerelease) (Debian 4.4.2-9) ) #1 SMP Mon Mar 15 15:00:37 CET 2010 [ 0.000000] xen_release_chunk: looking at area pfn 9d-a0 [ 0.000000] xen_release_chunk: looking at area pfn c0000-e0000 [ 0.000000] xen_release_chunk: looking at area pfn f0000-fe000 [ 0.000000] Xen: 0000000000000000 - 000000000009d000 (usable) [ 0.000000] Xen: 00000000000a0000 - 0000000000100000 (reserved) [ 0.000000] Xen: 0000000000100000 - 00000000bf699000 (usable) [ 0.000000] Xen: 00000000bf699000 - 00000000bf6af000 (reserved) [ 0.000000] Xen: 00000000bf6af000 - 00000000bf6ce000 (ACPI data) [ 0.000000] Xen: 00000000bf6ce000 - 00000000c0000000 (reserved) [ 0.000000] Xen: 00000000e0000000 - 00000000f0000000 (reserved) [ 0.000000] Xen: 00000000fe000000 - 0000000100000000 (reserved) [ 0.000000] #1 [0001fea000 - 0001fff000] XEN PAGETABLES ==> [0001fea000 - 0001fff000] [ 0.000000] #4 [000184b000 - 0001fea000] XEN START INFO ==> [000184b000 - 0001fea000] [ 0.124571] Xen: using vcpu_info placement [ 0.124967] PCI-DMA: Using Xen software bounce buffering for IO (Xen-SWIOTLB) [ 0.131397] xen_swiotlb_fixup: buf=ffff880004e17000 size=67108864 [ 0.146553] xen_swiotlb_fixup: buf=ffff880008e77000 size=32768 [ 0.146621] Placing 64MB Xen software IO TLB between ffff880004e17000 - ffff880008e17000 [ 0.146623] Xen software IO TLB at phys 0x4e17000 - 0x8e17000 [ 0.158797] xen: registering gsi 0 triggering 1 polarity 0 [ 0.158804] xen: --> irq=0 [ 0.158806] xen_set_ioapic_routing: irq 0 gsi 0 vector 240 ioapic 0 pin 0 triggering 0 polarity 0 [ 0.158818] xen: registering gsi 1 triggering 1 polarity 0 [ 0.158821] xen: --> irq=1 [ 0.158823] xen_set_ioapic_routing: irq 1 gsi 1 vector 32 ioapic 0 pin 1 triggering 0 polarity 0 [ 0.158828] xen: registering gsi 3 triggering 1 polarity 0 [ 0.158831] xen: --> irq=3 [ 0.158833] xen_set_ioapic_routing: irq 3 gsi 3 vector 40 ioapic 0 pin 3 triggering 0 polarity 0 [ 0.158838] xen: registering gsi 4 triggering 1 polarity 0 [ 0.158841] xen: --> irq=4 [ 0.158843] xen_set_ioapic_routing: irq 4 gsi 4 vector 48 ioapic 0 pin 4 triggering 0 polarity 0 [ 0.158848] xen: registering gsi 5 triggering 1 polarity 0 [ 0.158851] xen: --> irq=5 [ 0.158853] xen_set_ioapic_routing: irq 5 gsi 5 vector 56 ioapic 0 pin 5 triggering 0 polarity 0 [ 0.158857] xen: registering gsi 6 triggering 1 polarity 0 [ 0.158860] xen: --> irq=6 [ 0.158862] xen_set_ioapic_routing: irq 6 gsi 6 vector 64 ioapic 0 pin 6 triggering 0 polarity 0 [ 0.158867] xen: registering gsi 7 triggering 1 polarity 0 [ 0.158870] xen: --> irq=7 [ 0.158872] xen_set_ioapic_routing: irq 7 gsi 7 vector 72 ioapic 0 pin 7 triggering 0 polarity 0 [ 0.158877] xen: registering gsi 8 triggering 1 polarity 0 [ 0.158880] xen: --> irq=8 [ 0.158882] xen_set_ioapic_routing: irq 8 gsi 8 vector 80 ioapic 0 pin 8 triggering 0 polarity 0 [ 0.158886] xen: registering gsi 9 triggering 0 polarity 0 [ 0.158889] xen: --> irq=9 [ 0.158891] xen_set_ioapic_routing: irq 9 gsi 9 vector 88 ioapic 0 pin 9 triggering 1 polarity 0 [ 0.158896] xen: registering gsi 10 triggering 1 polarity 0 [ 0.158899] xen: --> irq=10 [ 0.158901] xen_set_ioapic_routing: irq 10 gsi 10 vector 96 ioapic 0 pin 10 triggering 0 polarity 0 [ 0.158906] xen: registering gsi 11 triggering 1 polarity 0 [ 0.158909] xen: --> irq=11 [ 0.158911] xen_set_ioapic_routing: irq 11 gsi 11 vector 104 ioapic 0 pin 11 triggering 0 polarity 0 [ 0.158915] xen: registering gsi 12 triggering 1 polarity 0 [ 0.158918] xen: --> irq=12 [ 0.158921] xen_set_ioapic_routing: irq 12 gsi 12 vector 112 ioapic 0 pin 12 triggering 0 polarity 0 [ 0.158925] xen: registering gsi 13 triggering 1 polarity 0 [ 0.158928] xen: --> irq=13 [ 0.158930] xen_set_ioapic_routing: irq 13 gsi 13 vector 120 ioapic 0 pin 13 triggering 0 polarity 0 [ 0.158935] xen: registering gsi 14 triggering 1 polarity 0 [ 0.158938] xen: --> irq=14 [ 0.158940] xen_set_ioapic_routing: irq 14 gsi 14 vector 136 ioapic 0 pin 14 triggering 0 polarity 0 [ 0.158945] xen: registering gsi 15 triggering 1 polarity 0 [ 0.158948] xen: --> irq=15 [ 0.158950] xen_set_ioapic_routing: irq 15 gsi 15 vector 144 ioapic 0 pin 15 triggering 0 polarity 0 [ 0.172927] Xen: using vcpuop timer interface [ 0.172927] installing Xen timer for CPU 0 [ 0.172997] xen: vcpu_time_info placement not supported [ 0.218319] installing Xen timer for CPU 1 [ 0.248551] installing Xen timer for CPU 2 [ 0.249239] installing Xen timer for CPU 3 [ 0.250784] Booting paravirtualized kernel on Xen [ 0.250840] Xen version: 3.4.2 (preserve-AD) (dom0) [ 0.269000] xenbus_probe_init ok [ 0.334534] xenbus_probe_backend_init bus registered ok [ 0.334620] xenbus_probe_frontend_init bus registered ok [ 0.334677] xen_balloon: Initialising balloon driver with page order 0. [ 0.890440] xen: registering gsi 13 triggering 1 polarity 0 [ 0.890443] xen_allocate_pirq: returning irq 13 for gsi 13 [ 0.890500] xen: --> irq=13 [ 0.890503] xen_set_ioapic_routing: irq 13 gsi 13 vector 120 ioapic 0 pin 13 triggering 0 polarity 0 [ 0.890821] xen: registering gsi 8 triggering 1 polarity 0 [ 0.890824] xen_allocate_pirq: returning irq 8 for gsi 8 [ 0.890880] xen: --> irq=8 [ 0.890882] xen_set_ioapic_routing: irq 8 gsi 8 vector 80 ioapic 0 pin 8 triggering 0 polarity 0 [ 0.891352] xen: registering gsi 4 triggering 1 polarity 0 [ 0.891354] xen_allocate_pirq: returning irq 4 for gsi 4 [ 0.891410] xen: --> irq=4 [ 0.891413] xen_set_ioapic_routing: irq 4 gsi 4 vector 48 ioapic 0 pin 4 triggering 0 polarity 0 [ 0.891940] xen: registering gsi 3 triggering 1 polarity 0 [ 0.891942] xen_allocate_pirq: returning irq 3 for gsi 3 [ 0.891998] xen: --> irq=3 [ 0.892000] xen_set_ioapic_routing: irq 3 gsi 3 vector 40 ioapic 0 pin 3 triggering 0 polarity 0 [ 0.901840] xen: registering gsi 16 triggering 0 polarity 1 [ 0.901855] xen: --> irq=16 [ 0.901858] xen_set_ioapic_routing: irq 16 gsi 16 vector 184 ioapic 0 pin 16 triggering 1 polarity 1 [ 0.954879] xen: registering gsi 20 triggering 0 polarity 1 [ 0.954889] xen: --> irq=20 [ 0.954892] xen_set_ioapic_routing: irq 20 gsi 20 vector 208 ioapic 0 pin 20 triggering 1 polarity 1 [ 2.943976] xen: registering gsi 22 triggering 0 polarity 1 [ 2.944008] xen: --> irq=22 [ 2.944014] xen_set_ioapic_routing: irq 22 gsi 22 vector 33 ioapic 0 pin 22 triggering 1 polarity 1 [ 2.963011] xen: registering gsi 16 triggering 0 polarity 1 [ 2.963016] xen_allocate_pirq: returning irq 16 for gsi 16 [ 2.963107] xen: --> irq=16 [ 2.963113] xen_set_ioapic_routing: irq 16 gsi 16 vector 184 ioapic 0 pin 16 triggering 1 polarity 1 [ 2.970498] xen: registering gsi 22 triggering 0 polarity 1 [ 2.970504] xen_allocate_pirq: returning irq 22 for gsi 22 [ 2.970578] xen: --> irq=22 [ 2.970583] xen_set_ioapic_routing: irq 22 gsi 22 vector 33 ioapic 0 pin 22 triggering 1 polarity 1 [ 3.070823] xen: registering gsi 17 triggering 0 polarity 1 [ 3.070843] xen: --> irq=17 [ 3.070848] xen_set_ioapic_routing: irq 17 gsi 17 vector 41 ioapic 0 pin 17 triggering 1 polarity 1 root@xenized:~# ls -l /sys/hypervisor/ total 0 drwxr-xr-x 2 root root 0 2010-03-15 15:26 compilation drwxr-xr-x 2 root root 0 2010-03-15 15:26 properties -r--r--r-- 1 root root 4096 2010-03-15 15:26 type -r--r--r-- 1 root root 4096 2010-03-15 15:26 uuid drwxr-xr-x 2 root root 0 2010-03-15 15:26 version _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
mailing@securitylabs.it
2010-Mar-16 10:37 UTC
[Xen-users] Re: [SOLVED] Could not obtain handle on privileged command interface
On 15/03/2010 15:37, mailing@securitylabs.it wrote:> Hello, > > when I try to start xend I receive this error: > > root@xenized:~# 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 <module> > from xen.xend.server import SrvDaemon > File "usr/lib/python2.5/site-packages/xen/xend/server/SrvDaemon.py", > line 26, in <module> > File "usr/lib/python2.5/site-packages/xen/xend/server/relocate.py", > line 28, in <module> > File "usr/lib/python2.5/site-packages/xen/xend/XendDomain.py", line > 35, in <module> > File "usr/lib/python2.5/site-packages/xen/xend/XendCheckpoint.py", > line 20, in <module> > File "usr/lib/python2.5/site-packages/xen/xend/image.py", line 46, > in <module> > xen.lowlevel.xc.Error: (1, ''Internal error'', ''Could not obtain handle > on privileged command interface (2 = No such file or directory)'') > > Googling seems that I''ve not booted with the Xen kernel, but It''s not > my case: >Solved by adding: none /proc/xen xenfs defaults 0 0 in /etc/fstab _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Seemingly Similar Threads
- pv_ops kernel 2.6.29-rc6 boot failure
- Cannot boot Dom0: Thread overran stack, or stack corrupted
- Bug#659642: xen-hypervisor-4.0-amd64: outl segfaults when restoring monitor from sleep with DPMS
- Bug#603727: xen-hypervisor-4.0-amd64: i386 Dom0 crashes after doing some I/O on local storage (software Raid1 on SAS-drives with mpt2sas driver)
- Failure to boot, Debian squeeze with 4.0.1 hypervisor, timer problems?