I actually ran into a problem very similar to this myself this morning - it came from the fact that the init scripts were reordered at some point, and I still had the old init script ordering.
I sorted it temporarily by starting the scripts by hand - the normal order is: 20: xcp-fe, xend, xcp-v6d 22: xcp-squeezed 23: xcp-xapi If you manually start the scripts in this order does it work? It's interesting that your /proc/xen isn't mounted though - that should happen in the xend init script, and that should have worked. Jon On 16 Jan 2012, at 16:46, Ritesh Raj Sarraf wrote: > On 01/13/2012 07:12 AM, Jon Ludlam wrote: >> That log looks to me like you weren't running on xen - the 'failed to >> open xenctrl interface' almost always means that - could you please >> double check? > > > This is the kernel running. > > lnx200-39:~# uname -a > Linux lnx200-39 3.1.0-1-amd64 #1 SMP Tue Jan 10 05:01:58 UTC 2012 x86_64 > GNU/Linux > > > Interestingly there's nothing under /proc/xen. > > > The xm interface is disabled because xcp conflicts xend. > > > dmesg does report successful xen msgs. > > > Is there anything you want me to verify? The machine is up and hasn't > been rebooted yet. > > lnx200-39:~# uptime > 06:13:30 up 4 days, 9:15, 1 user, load average: 0.00, 0.01, 0.05 > > > -- > Ritesh Raj Sarraf | http://people.debian.org/~rrs > Debian - The Universal Operating System > -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
