cat /proc/xen/capabilities gives me control_d /etc/init.d/xend start gives me mount: xenfs already mounted or /proc/xen busy mount: according to mtab, none is already mounted on /proc/xen /etc/init.d/xend: line53: xend: command not found /etc/init.d/xend: line40: xend: command not found /etc/init.d/xend: line45: xend: command not found On Tue, Mar 23, 2010 at 1:16 PM, Pasi Kärkkäinen wrote: > On Tue, Mar 23, 2010 at 01:11:14PM -0700, kishore kumar wrote: > > Yes. I see below in /proc/xen after mount > > > > capabilities > > privcmd > > xenbus > > xsd_kva > > xsd_port. > > > > Looks ok.. What does "cat /proc/xen/capabilities" say ? > > Does "/etc/init.d/xend start" work? > > -- Pasi > > > On Tue, Mar 23, 2010 at 1:05 PM, Pasi Kärkkäinen <[1]pasik@iki.fi> > wrote: > > > > On Tue, Mar 23, 2010 at 01:04:34PM -0700, kishore kumar wrote: > > > attached is the screen shot. > > > > > > I did > > > cd /lib/modules/[1][2]2.6.32.10/kernel/drivers/xen > > > modprobe xen-evtchn > > > > > > and then did > > > > > > mount -t xenfs none /proc/xen. > > > > > > But still the same problem. > > > > > > > Does the mount succeed? Is there anything under /proc/xen? > > > > -- Pasi > > > On Tue, Mar 23, 2010 at 12:51 PM, Pasi Kärkkäinen > > <[2][3]pasik@iki.fi> wrote: > > > > > > On Tue, Mar 23, 2010 at 12:43:16PM -0700, kishore kumar > wrote: > > > > I have the Xen 3.4.3.rc4 installed alone with > > > > > > > > make xen > > > > > > > > make stubdom, > > > > > > > > make tools > > > > > > > > make install-xen > > > > make install-tools > > > > make install-stubdom > > > > > > > > > > > > and pulled dom 0 kernel from > > > > > > > > git clone > > > > > git://[1][3][4] > git.kernel.org/pub/scm/linux/kernel/git/jeremy/xen.git > > > > and compiled the kernel. > > > > > > > > modified the grub.conf as below > > > > > > > > title xen/pvops (2.6.32.10) > > > > root (hd0,0) > > > > kernel /xen.gz loglvl=all guest_loglvl=all > > sync_console > > > > console_to_ring com1=115200,8n1 console=vga,com1 > lapic=debug > > > > apic_verbosity=debug apic=debug iommu=1 msi=1 > > > > module /vmlinuz-2.6.32.10 ro > > root=/dev/VolGroup01/LogVol00 > > > > console=hvc0 earlyprintk=xen nomodeset initcall_debug > debug > > > loglevel=10 > > > > module /initrd-2.6.32.10.img > > > > > > > > and rebooted the machine. I hope this is a Xen+ dom0. > > Please > > > correct me > > > > if I am wrong here. > > > > > > > > After reboot I see > > > > Starting xend: grep: /proc/xen/capabilities: No such > file > > or > > > directory > > > > > > > > I added none /proc/xen xenfs defaults 0 0 in /etc/fstab > > file and > > > > rebooted. still the same problem. > > > > > > > > Is there anything else that needs to be done? > > > > > > > > > > So is that version of xend automatically loading > xen-evtchn.ko > > driver > > > module? > > > Try loading the module with "modprobe xen-evtchn" and then > try > > mounting > > > the /proc/xen. > > > > Am I booted with Xen+dom0 or just the linux kernel? > > > > > > > > > > Most probably to Xen+dom0, if you chose the grub entry you > pasted > > above. > > > > > > -- Pasi > > > > My uname -a is > > > > > > > > Linux localhost.localdomain 2.6.32.10 > > > > > > > > Thanks > > > > > > > > > > > > On Tue, Mar 23, 2010 at 12:23 AM, Pasi Kärkkäinen > > > <[2][4][5]pasik@iki.fi> wrote: > > > > > > > > On Mon, Mar 22, 2010 at 05:00:41PM -0700, kishore > kumar > > wrote: > > > > > Hi all, > > > > > > > > > > I see the below message after I install > xen3.4.3-rc4 > > and > > > pvops dom > > > > 0 > > > > > kernel 2.6.32.10 and reboot the machine. > > > > > > > > > > Starting xend: grep: /proc/xen/capabilities: No > such > > file > > > or > > > > directory > > > > > > > > > > I did below steps too. > > > > > > > > > > step 1: insmod xen-evtchn.ko > > > > > step 2: Added none /proc/xen xenfs defaults 0 0 > in > > > /etc/fstab > > > > file. > > > > > > > > > > Is there something that I am missing here? > > > > > > > > Well then actually mount /proc/xen :) > > > > (or reboot). > > > > > > > > Also did you verify you've actually rebooted to > Xen+dom0? > > > > -- Pasi > > > > > > > > References > > > > > > > > Visible links > > > > 1. > > [5][6]http://git.kernel.org/pub/scm/linux/kernel/git/jeremy/xen.git > > > > 2. mailto:[6][7]pasik@iki.fi > > > > > > References > > > > > > Visible links > > > 1. [8]http://2.6.32.10/kernel/drivers/xen > > > 2. mailto:[9]pasik@iki.fi > > > 3. > > [10]http://git.kernel.org/pub/scm/linux/kernel/git/jeremy/xen.git > > > 4. mailto:[11]pasik@iki.fi > > > 5. > > [12]http://git.kernel.org/pub/scm/linux/kernel/git/jeremy/xen.git > > > 6. mailto:[13]pasik@iki.fi > > > > References > > > > Visible links > > 1. mailto:pasik@iki.fi > > 2. http://2.6.32.10/kernel/drivers/xen > > 3. mailto:pasik@iki.fi > > 4. http://git.kernel.org/pub/scm/linux/kernel/git/jeremy/xen.git > > 5. mailto:pasik@iki.fi > > 6. http://git.kernel.org/pub/scm/linux/kernel/git/jeremy/xen.git > > 7. mailto:pasik@iki.fi > > 8. http://2.6.32.10/kernel/drivers/xen > > 9. mailto:pasik@iki.fi > > 10. http://git.kernel.org/pub/scm/linux/kernel/git/jeremy/xen.git > > 11. mailto:pasik@iki.fi > > 12. http://git.kernel.org/pub/scm/linux/kernel/git/jeremy/xen.git > > 13. mailto:pasik@iki.fi >