Re: [Xen-users] Starting xend: grep: /proc/xen/capabilities: No

I disabled network-bridge in /etc/xen/xend-config.sxp file and rebooted the system. Then I did below steps. After starting xen I manually started network-bridge. But the network connection could not be established.

Am I doing something wrong here? Are there any other path that needs to be set ??

Please let me know.

[root@kishore xen]# /etc/init.d/xend start

mount: xenfs already mounted or /proc/xen busy

mount: according to mtab, none is already mounted on /proc/xen

[root@kishore xen]# xm list

Name ID Mem VCPUs State Time(s)

Domain-0 0 1020 12 r----- 91.9

[root@kishore xen]# brctl show

bridge name bridge id STP enabled interfaces

[root@kishore xen]# cd /etc/xen/scripts/

[root@kishore scripts]# ls

blktap block-nbd network-bridge vif-common.sh vtpm vtpm-impl xen-network-common.sh

block external-device-migrate network-nat vif-nat vtpm-common.sh vtpm-migration.sh xen-script-common.sh

block-common.sh locking.sh network-route vif-route vtpm-delete xen-hotplug-cleanup

block-enbd logging.sh vif-bridge vscsi vtpm-hotplug-common.sh xen-hotplug-common.sh

[root@kishore scripts]# ./network-bridge start

Nothing to flush.

Waiting for peth0 to negotiate link...........(link isnt in running state)

Determining IP information for eth0...PING 192.168.1.1 (192.168.1.1) from 192.168.1.14 eth0: 56(84) bytes of data.

--- 192.168.1.1 ping statistics ---

4 packets transmitted, 0 received, +3 errors, 100% packet loss, time 2999ms

, pipe 3

PING 192.168.1.1 (192.168.1.1) from 192.168.1.13 eth0: 56(84) bytes of data.

--- 192.168.1.1 ping statistics ---

4 packets transmitted, 0 received, +3 errors, 100% packet loss, time 2999ms

, pipe 3

failed.

Nothing to flush.

[root@kishore scripts]#

[root@kishore scripts]# ./network-bridge status

============================================================

4: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue

link/ether 00:13:20:f7:83:d4 brd ff:ff:ff:ff:ff:ff

inet 192.168.1.14/24 scope global eth0

inet6 fe80::213:20ff:fef7:83d4/64 scope link

valid_lft forever preferred_lft forever

4: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue

link/ether 00:13:20:f7:83:d4 brd ff:ff:ff:ff:ff:ff

inet 192.168.1.14/24 scope global eth0

inet6 fe80::213:20ff:fef7:83d4/64 scope link

valid_lft forever preferred_lft forever

bridge name bridge id STP enabled interfaces

eth0 8000.001320f783d4 no peth0

192.168.1.0/24 dev eth0 proto kernel scope link src 192.168.1.14

default via 192.168.1.1 dev eth0 proto static

Kernel IP routing table

Destination Gateway Genmask Flags Metric Ref Use Iface

192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0

0.0.0.0 192.168.1.1 0.0.0.0 UG 0 0 0 eth0

============================================================

[root@kishore scripts]# ifconfig

eth0 Link encap:Ethernet HWaddr 00:13:20:F7:83:D4

inet addr:192.168.1.14 Bcast:0.0.0.0 Mask:255.255.255.0

inet6 addr: fe80::213:20ff:fef7:83d4/64 Scope:Link

UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1

RX packets:0 errors:0 dropped:0 overruns:0 frame:0

TX packets:160 errors:0 dropped:0 overruns:0 carrier:0

collisions:0 txqueuelen:0

RX bytes:0 (0.0 b) TX bytes:26953 (26.3 KiB)

eth1 Link encap:Ethernet HWaddr 00:13:20:F7:83:D5

UP BROADCAST MULTICAST MTU:1500 Metric:1

RX packets:0 errors:0 dropped:0 overruns:0 frame:0

TX packets:0 errors:0 dropped:0 overruns:0 carrier:0

collisions:0 txqueuelen:1000

RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)

Memory:b1900000-b1920000

lo Link encap:Local Loopback

inet addr:127.0.0.1 Mask:255.0.0.0

inet6 addr: ::1/128 Scope:Host

UP LOOPBACK RUNNING MTU:16436 Metric:1

RX packets:88 errors:0 dropped:0 overruns:0 frame:0

TX packets:88 errors:0 dropped:0 overruns:0 carrier:0

collisions:0 txqueuelen:0

RX bytes:8604 (8.4 KiB) TX bytes:8604 (8.4 KiB)

peth0 Link encap:Ethernet HWaddr 00:13:20:F7:83:D4

UP BROADCAST MULTICAST MTU:1500 Metric:1

RX packets:85 errors:0 dropped:0 overruns:0 frame:0

TX packets:125 errors:0 dropped:0 overruns:0 carrier:0

collisions:0 txqueuelen:1000

RX bytes:8413 (8.2 KiB) TX bytes:16922 (16.5 KiB)

Memory:b1920000-b1940000

[root@kishore scripts]# ping www.google.com

ping: unknown host www.google.com

[root@kishore scripts]#

On Sat, Mar 27, 2010 at 2:59 AM, Pasi Kärkkäinen <pasik@xxxxxx> wrote:

On Fri, Mar 26, 2010 at 03:04:36PM -0700, kishore kumar wrote:
> Sure.
> I think I have iproute but the path is not set.
>
> I did PATH=$PATH:/sbin
>
> then I did /etc/init.d/xend restart
> It worked. It did not give me any error messages.
>
> Is my xen up and running??

Run "xm info" to check Xen information, and "xm list" to verify running domains/guests.

> But the problem is my network is down after I ran /etc/init.d/xend
> restart.
>

When xend is started it executes network-script defined in /etc/xen/xend-config.sxp.
As a default it's 'network-bridge', which does all kinds of magic and sets up
a bridge for you, so you can attach guests to it and share the network connection with them.

Maybe something goes wrong with that.

You can try disabling (comment out) the network-script line from xend-config.sxp and
reboot.

Then set up the bridges manually, using the methods provided by your dom0 distribution.

-- Pasi

>
> On Fri, Mar 26, 2010 at 2:37 PM, Pasi Kärkkäinen <[1]pasik@xxxxxx> wrote:
>
> On Fri, Mar 26, 2010 at 02:04:12PM -0700, kishore kumar wrote:
> >
> > OK.Now its giving me another problem. I did below steps.
> >
>
> Ok, this thread doesn't belong to xen-devel at all.
> Please continue only on xen-users after this.
>
> You're missing "ip" command, meaning you don't have iproute installed.
>
> -- Pasi
>
> > [root@localhost kishore]# mount -t xenfs none /proc/xen
> >
> > [root@localhost kishore]# mount
> >
> > /dev/mapper/VolGroup00-LogVol00 on / type ext3 (rw)
> >
> > proc on /proc type proc (rw)
> >
> > sysfs on /sys type sysfs (rw)
> >
> > devpts on /dev/pts type devpts (rw,gid=5,mode=620)
> >
> > /dev/sda1 on /boot type ext3 (rw)
> >
> > tmpfs on /dev/shm type tmpfs (rw)
> >
> > none on /proc/sys/fs/binfmt_misc type binfmt_misc (rw)
> >
> > sunrpc on /var/lib/nfs/rpc_pipefs type rpc_pipefs (rw)
> >
> > none on /proc/xen type xenfs (rw)
> >
> >
> >
> > [root@localhost xen]# /sbin/modprobe xen-evtchn
> >
> > [root@localhost kishore]# PATH=$PATH:/usr/sbin
> >
> > [root@localhost kishore]# /etc/init.d/xend start
> >
> > mount: xenfs already mounted or /proc/xen busy
> >
> > mount: according to mtab, none is already mounted on /proc/xen
> >
> > /etc/xen/scripts/network-bridge: line 87: ip: command not found
> >
> > /etc/xen/scripts/network-bridge: line 126: ip: command not found
> >
> > /etc/xen/scripts/network-bridge: line 132: ip: command not found
> >
> > /etc/xen/scripts/network-bridge: line 139: ip: command not found
> >
> > /etc/xen/scripts/network-bridge: line 104: ip: command not found
> >
> > /etc/xen/scripts/network-bridge: line 105: ip: command not found
> >
> > /etc/xen/scripts/network-bridge: line 233: ip: command not found
> >
> > /etc/xen/scripts/network-bridge: line 87: ip: command not found
> >
> > /etc/xen/scripts/network-bridge: line 126: ip: command not found
> >
> > /etc/xen/scripts/network-bridge: line 132: ip: command not found
> >
> > /etc/xen/scripts/network-bridge: line 139: ip: command not found
> >
> > /etc/xen/scripts/network-bridge: line 104: ip: command not found
> >
> > /etc/xen/scripts/network-bridge: line 105: ip: command not found
> >
> > /etc/xen/scripts/network-bridge: line 233: ip: command not found
> >
> >
> >
> > On Fri, Mar 26, 2010 at 11:17 AM, Pasi Kärkkäinen
> <[1][2]pasik@xxxxxx> wrote:
> >
> > On Fri, Mar 26, 2010 at 11:12:24AM -0700, kishore kumar wrote:
> > > my SELINUX and Firewall both are disabled.
> > >
> > > I dont have /usr/sbin in my PATH.
> >
> > And that's the problem here.
> > > should I add it in my $HOME/.bashrc??
> > >
> > > or do we need to edit /etc/bashrc or /etc/profile??
> > >
> >
> > It's all up to you.
> >
> > -- Pasi
> > > Please let me know.
> > > Thanks
> > >
> > >
> > >
> > > On Fri, Mar 26, 2010 at 10:26 AM, Pasi Kärkkäinen
> > <[1][2][3]pasik@xxxxxx> wrote:
> > >
> > > On Fri, Mar 26, 2010 at 09:46:55AM -0700, kishore kumar
> wrote:
> > > > Does it means the Xen did not get installed
> properly??
> > > >
> > > > I pulled 3.4-testing.hg and did
> > > > make xen
> > > > make tools
> > > > make stubdom
> > > > make install-xen
> > > > make install-tools
> > > > make install-stubdom
> > > > Is there something that I am missing in compiling and
> > installing
> > > xen?
> > > > where will the xend daemon binary be installed?
> > > >
> > > > I see it in /etc/init.d/xend
> > > > and
> > > > /usr/sbin/xend.
> > > >
> > >
> > > Is /usr/sbin/ on your PATH?
> > > /etc/init.d/xend was complaining that it can't find "xend"
> > binary..
> > >
> > > Do you have selinux? Try turning it off and rebooting?
> > >
> > > -- Pasi
> > > >
> > > > On Thu, Mar 25, 2010 at 11:58 PM, Pasi Kärkkäinen
> > > <[1][2][3][4]pasik@xxxxxx> wrote:
> > > >
> > > > On Thu, Mar 25, 2010 at 07:38:31PM -0700, kishore
> kumar
> > wrote:
> > > > > I could not get anything out of it. Attached
> is the
> > xend
> > > file.
> > > > >
> > > > > can you please let me know?
> > > > >
> > > >
> > > > Based on the errors and the xend you sent it looks
> like
> > you don't
> > > > have the actual 'xend' daemon binary installed on
> your
> > system
> > > path.
> > > >
> > > > -- Pasi
> > > >
> > > > > Thanks
> > > > >
> > > > >
> > > > > On Wed, Mar 24, 2010 at 12:29 AM, Pasi
> Kärkkäinen
> > > > <[1][2][3][4][5]pasik@xxxxxx> wrote:
> > > > >
> > > > > On Tue, Mar 23, 2010 at 03:46:15PM -0700,
> kishore
> > kumar
> > > wrote:
> > > > > > which init-script?
> > > > > >
> > > > >
> > > > > /etc/init.d/xend
> > > > >
> > > > > -- Pasi
> > > > > > On Tue, Mar 23, 2010 at 3:11 PM, Pasi
> > Kärkkäinen
> > > > > <[1][2][3][4][5][6]pasik@xxxxxx> wrote:
> > > > > >
> > > > > > On Tue, Mar 23, 2010 at 02:42:32PM
> -0700,
> > kishore
> > > kumar
> > > > wrote:
> > > > > > > Any suggestions on this please??
> > > > > > >
> > > > > >
> > > > > > "xend: command not found" sounds like
> > there's
> > > something
> > > > wrong
> > > > > > with your xen tools installation.
> > > > > >
> > > > > > Do you actually have xend installed?
> > > > > >
> > > > > > Also please read the lines 53, 40,
> and 45
> > from the
> > > > init-script
> > > > > > to see what's on those lines.
> > > > > >
> > > > > > -- Pasi
> > > > > >
> > > > > > > On Tue, Mar 23, 2010 at 1:30 PM,
> > kishore kumar
> > > > > >
> <[1][2][3][4][5][6][7]bodkekumar@xxxxxxxxx>
> > > > > > > wrote:
> > > > > > >
> > > > > > > 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
> > > > > > <[2][3][4][5][6][7][8]pasik@xxxxxx>
> > > > > > > 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][3][4][5][6][7][8][9]pasik@xxxxxx>
> > 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][4][5][6][7][8][9][10]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][5][6][7][8][9][10][11]pasik@xxxxxx>
> > > 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][6][7][8][9][10][11][12]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][7][8][9][10][11][12][13]pasik@xxxxxx>
> 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][8][9][10][11][12][13][14]http://git.kernel.org/pub/scm/linux/kernel/git/jeremy/xen.git
> > > > > > > > > > 2.
> > > > >
> mailto:[6][7][9][10][11][12][13][14][15]pasik@xxxxxx
> > > > > > > > >
> > > > > > > > > References
> > > > > > > > >
> > > > > > > > > Visible links
> > > > > > > > > 1.
> > > > >
> >
> [8][10][11][12][13][14][15][16]http://2.6.32.10/kernel/drivers/xen
> > > > > > > > > 2.
> > > > mailto:[9][11][12][13][14][15][16][17]pasik@xxxxxx
> > > > > > > > > 3.
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
> [10][12][13][14][15][16][17][18]http://git.kernel.org/pub/scm/linux/kernel/git/jeremy/xen.git
> > > > > > > > > 4.
> > > > mailto:[11][13][14][15][16][17][18][19]pasik@xxxxxx
> > > > > > > > > 5.
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
> [12][14][15][16][17][18][19][20]http://git.kernel.org/pub/scm/linux/kernel/git/jeremy/xen.git
> > > > > > > > > 6.
> > > > mailto:[13][15][16][17][18][19][20][21]pasik@xxxxxx
> > > > > > > >
> > > > > > > > References
> > > > > > > >
> > > > > > > > Visible links
> > > > > > > > 1.
> > > mailto:[16][17][18][19][20][21][22]pasik@xxxxxx
> > > > > > > > 2.
> > > >
> > [17][18][19][20][21][22][23]http://2.6.32.10/kernel/drivers/xen
> > > > > > > > 3.
> > > mailto:[18][19][20][21][22][23][24]pasik@xxxxxx
> > > > > > > > 4.
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
> [19][20][21][22][23][24][25]http://git.kernel.org/pub/scm/linux/kernel/git/jeremy/xen.git
> > > > > > > > 5.
> > > mailto:[20][21][22][23][24][25][26]pasik@xxxxxx
> > > > > > > > 6.
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
> [21][22][23][24][25][26][27]http://git.kernel.org/pub/scm/linux/kernel/git/jeremy/xen.git
> > > > > > > > 7.
> > > mailto:[22][23][24][25][26][27][28]pasik@xxxxxx
> > > > > > > > 8.
> > > >
> > [23][24][25][26][27][28][29]http://2.6.32.10/kernel/drivers/xen
> > > > > > > > 9.
> > > mailto:[24][25][26][27][28][29][30]pasik@xxxxxx
> > > > > > > > 10.
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
> [25][26][27][28][29][30][31]http://git.kernel.org/pub/scm/linux/kernel/git/jeremy/xen.git
> > > > > > > > 11.
> > > mailto:[26][27][28][29][30][31][32]pasik@xxxxxx
> > > > > > > > 12.
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
> [27][28][29][30][31][32][33]http://git.kernel.org/pub/scm/linux/kernel/git/jeremy/xen.git
> > > > > > > > 13.
> > > mailto:[28][29][30][31][32][33][34]pasik@xxxxxx
> > > > > > >
> > > > > > > References
> > > > > > >
> > > > > > > Visible links
> > > > > > > 1.
> > mailto:[30][31][32][33][34][35]bodkekumar@xxxxxxxxx
> > > > > > > 2.
> > mailto:[31][32][33][34][35][36]pasik@xxxxxx
> > > > > > > 3.
> > mailto:[32][33][34][35][36][37]pasik@xxxxxx
> > > > > > > 4.
> > >
> [33][34][35][36][37][38]http://2.6.32.10/kernel/drivers/xen
> > > > > > > 5.
> > mailto:[34][35][36][37][38][39]pasik@xxxxxx
> > > > > > > 6.
> > > > > >
> > > > >
> > > >
> > >
> >
> [35][36][37][38][39][40]http://git.kernel.org/pub/scm/linux/kernel/git/jeremy/xen.git
> > > > > > > 7.
> > mailto:[36][37][38][39][40][41]pasik@xxxxxx
> > > > > > > 8.
> > > > > >
> > > > >
> > > >
> > >
> >
> [37][38][39][40][41][42]http://git.kernel.org/pub/scm/linux/kernel/git/jeremy/xen.git
> > > > > > > 9.
> > mailto:[38][39][40][41][42][43]pasik@xxxxxx
> > > > > > > 10.
> > >
> [39][40][41][42][43][44]http://2.6.32.10/kernel/drivers/xen
> > > > > > > 11.
> > mailto:[40][41][42][43][44][45]pasik@xxxxxx
> > > > > > > 12.
> > > > > >
> > > > >
> > > >
> > >
> >
> [41][42][43][44][45][46]http://git.kernel.org/pub/scm/linux/kernel/git/jeremy/xen.git
> > > > > > > 13.
> > mailto:[42][43][44][45][46][47]pasik@xxxxxx
> > > > > > > 14.
> > > > > >
> > > > >
> > > >
> > >
> >
> [43][44][45][46][47][48]http://git.kernel.org/pub/scm/linux/kernel/git/jeremy/xen.git
> > > > > > > 15.
> > mailto:[44][45][46][47][48][49]pasik@xxxxxx
> > > > > > > 16.
> > mailto:[45][46][47][48][49][50]pasik@xxxxxx
> > > > > > > 17.
> > >
> [46][47][48][49][50][51]http://2.6.32.10/kernel/drivers/xen
> > > > > > > 18.
> > mailto:[47][48][49][50][51][52]pasik@xxxxxx
> > > > > > > 19.
> > > > > >
> > > > >
> > > >
> > >
> >
> [48][49][50][51][52][53]http://git.kernel.org/pub/scm/linux/kernel/git/jeremy/xen.git
> > > > > > > 20.
> > mailto:[49][50][51][52][53][54]pasik@xxxxxx
> > > > > > > 21.
> > > > > >
> > > > >
> > > >
> > >
> >
> [50][51][52][53][54][55]http://git.kernel.org/pub/scm/linux/kernel/git/jeremy/xen.git
> > > > > > > 22.
> > mailto:[51][52][53][54][55][56]pasik@xxxxxx
> > > > > > > 23.
> > >
> [52][53][54][55][56][57]http://2.6.32.10/kernel/drivers/xen
> > > > > > > 24.
> > mailto:[53][54][55][56][57][58]pasik@xxxxxx
> > > > > > > 25.
> > > > > >
> > > > >
> > > >
> > >
> >
> [54][55][56][57][58][59]http://git.kernel.org/pub/scm/linux/kernel/git/jeremy/xen.git
> > > > > > > 26.
> > mailto:[55][56][57][58][59][60]pasik@xxxxxx
> > > > > > > 27.
> > > > > >
> > > > >
> > > >
> > >
> >
> [56][57][58][59][60][61]http://git.kernel.org/pub/scm/linux/kernel/git/jeremy/xen.git
> > > > > > > 28.
> > mailto:[57][58][59][60][61][62]pasik@xxxxxx
> > > > > >
> > > > > > References
> > > > > >
> > > > > > Visible links
> > > > > > 1.
> mailto:[59][60][61][62][63]pasik@xxxxxx
> > > > > > 2.
> mailto:[60][61][62][63][64]bodkekumar@xxxxxxxxx
> > > > > > 3.
> mailto:[61][62][63][64][65]pasik@xxxxxx
> > > > > > 4.
> mailto:[62][63][64][65][66]pasik@xxxxxx
> > > > > > 5.
> > [63][64][65][66][67]http://2.6.32.10/kernel/drivers/xen
> > > > > > 6.
> mailto:[64][65][66][67][68]pasik@xxxxxx
> > > > > > 7.
> > > > >
> > > >
> > >
> >
> [65][66][67][68][69]http://git.kernel.org/pub/scm/linux/kernel/git/jeremy/xen.git
> > > > > > 8.
> mailto:[66][67][68][69][70]pasik@xxxxxx
> > > > > > 9.
> > > > >
> > > >
> > >
> >
> [67][68][69][70][71]http://git.kernel.org/pub/scm/linux/kernel/git/jeremy/xen.git
> > > > > > 10.
> mailto:[68][69][70][71][72]pasik@xxxxxx
> > > > > > 11.
> > [69][70][71][72][73]http://2.6.32.10/kernel/drivers/xen
> > > > > > 12.
> mailto:[70][71][72][73][74]pasik@xxxxxx
> > > > > > 13.
> > > > >
> > > >
> > >
> >
> [71][72][73][74][75]http://git.kernel.org/pub/scm/linux/kernel/git/jeremy/xen.git
> > > > > > 14.
> mailto:[72][73][74][75][76]pasik@xxxxxx
> > > > > > 15.
> > > > >
> > > >
> > >
> >
> [73][74][75][76][77]http://git.kernel.org/pub/scm/linux/kernel/git/jeremy/xen.git
> > > > > > 16.
> mailto:[74][75][76][77][78]pasik@xxxxxx
> > > > > > 17.
> mailto:[75][76][77][78][79]pasik@xxxxxx
> > > > > > 18.
> > [76][77][78][79][80]http://2.6.32.10/kernel/drivers/xen
> > > > > > 19.
> mailto:[77][78][79][80][81]pasik@xxxxxx
> > > > > > 20.
> > > > >
> > > >
> > >
> >
> [78][79][80][81][82]http://git.kernel.org/pub/scm/linux/kernel/git/jeremy/xen.git
> > > > > > 21.
> mailto:[79][80][81][82][83]pasik@xxxxxx
> > > > > > 22.
> > > > >
> > > >
> > >
> >
> [80][81][82][83][84]http://git.kernel.org/pub/scm/linux/kernel/git/jeremy/xen.git
> > > > > > 23.
> mailto:[81][82][83][84][85]pasik@xxxxxx
> > > > > > 24.
> > [82][83][84][85][86]http://2.6.32.10/kernel/drivers/xen
> > > > > > 25.
> mailto:[83][84][85][86][87]pasik@xxxxxx
> > > > > > 26.
> > > > >
> > > >
> > >
> >
> [84][85][86][87][88]http://git.kernel.org/pub/scm/linux/kernel/git/jeremy/xen.git
> > > > > > 27.
> mailto:[85][86][87][88][89]pasik@xxxxxx
> > > > > > 28.
> > > > >
> > > >
> > >
> >
> [86][87][88][89][90]http://git.kernel.org/pub/scm/linux/kernel/git/jeremy/xen.git
> > > > > > 29.
> mailto:[87][88][89][90][91]pasik@xxxxxx
> > > > > > 30.
> mailto:[88][89][90][91][92]bodkekumar@xxxxxxxxx
> > > > > > 31.
> mailto:[89][90][91][92][93]pasik@xxxxxx
> > > > > > 32.
> mailto:[90][91][92][93][94]pasik@xxxxxx
> > > > > > 33.
> > [91][92][93][94][95]http://2.6.32.10/kernel/drivers/xen
> > > > > > 34.
> mailto:[92][93][94][95][96]pasik@xxxxxx
> > > > > > 35.
> > > > >
> > > >
> > >
> >
> [93][94][95][96][97]http://git.kernel.org/pub/scm/linux/kernel/git/jeremy/xen.git
> > > > > > 36.
> mailto:[94][95][96][97][98]pasik@xxxxxx
> > > > > > 37.
> > > > >
> > > >
> > >
> >
> [95][96][97][98][99]http://git.kernel.org/pub/scm/linux/kernel/git/jeremy/xen.git
> > > > > > 38.
> mailto:[96][97][98][99][100]pasik@xxxxxx
> > > > > > 39.
> > [97][98][99][100][101]http://2.6.32.10/kernel/drivers/xen
> > > > > > 40.
> mailto:[98][99][100][101][102]pasik@xxxxxx
> > > > > > 41.
> > > > >
> > > >
> > >
> >
> [99][100][101][102][103]http://git.kernel.org/pub/scm/linux/kernel/git/jeremy/xen.git
> > > > > > 42.
> mailto:[100][101][102][103][104]pasik@xxxxxx
> > > > > > 43.
> > > > >
> > > >
> > >
> >
> [101][102][103][104][105]http://git.kernel.org/pub/scm/linux/kernel/git/jeremy/xen.git
> > > > > > 44.
> mailto:[102][103][104][105][106]pasik@xxxxxx
> > > > > > 45.
> mailto:[103][104][105][106][107]pasik@xxxxxx
> > > > > > 46.
> > [104][105][106][107][108]http://2.6.32.10/kernel/drivers/xen
> > > > > > 47.
> mailto:[105][106][107][108][109]pasik@xxxxxx
> > > > > > 48.
> > > > >
> > > >
> > >
> >
> [106][107][108][109][110]http://git.kernel.org/pub/scm/linux/kernel/git/jeremy/xen.git
> > > > > > 49.
> mailto:[107][108][109][110][111]pasik@xxxxxx
> > > > > > 50.
> > > > >
> > > >
> > >
> >
> [108][109][110][111][112]http://git.kernel.org/pub/scm/linux/kernel/git/jeremy/xen.git
> > > > > > 51.
> mailto:[109][110][111][112][113]pasik@xxxxxx
> > > > > > 52.
> > [110][111][112][113][114]http://2.6.32.10/kernel/drivers/xen
> > > > > > 53.
> mailto:[111][112][113][114][115]pasik@xxxxxx
> > > > > > 54.
> > > > >
> > > >
> > >
> >
> [112][113][114][115][116]http://git.kernel.org/pub/scm/linux/kernel/git/jeremy/xen.git
> > > > > > 55.
> mailto:[113][114][115][116][117]pasik@xxxxxx
> > > > > > 56.
> > > > >
> > > >
> > >
> >
> [114][115][116][117][118]http://git.kernel.org/pub/scm/linux/kernel/git/jeremy/xen.git
> > > > > > 57.
> mailto:[115][116][117][118][119]pasik@xxxxxx
> > > > >
> > > > > References
> > > > >
> > > > > Visible links
> > > > > 1. mailto:[117][118][119][120]pasik@xxxxxx
> > > > > 2. mailto:[118][119][120][121]pasik@xxxxxx
> > > > > 3.
> mailto:[119][120][121][122]bodkekumar@xxxxxxxxx
> > > > > 4. mailto:[120][121][122][123]pasik@xxxxxx
> > > > > 5. mailto:[121][122][123][124]pasik@xxxxxx
> > > > > 6.
> [122][123][124][125]http://2.6.32.10/kernel/drivers/xen
> > > > > 7. mailto:[123][124][125][126]pasik@xxxxxx
> > > > > 8.
> > > >
> > >
> >
> [124][125][126][127]http://git.kernel.org/pub/scm/linux/kernel/git/jeremy/xen.git
> > > > > 9. mailto:[125][126][127][128]pasik@xxxxxx
> > > > > 10.
> > > >
> > >
> >
> [126][127][128][129]http://git.kernel.org/pub/scm/linux/kernel/git/jeremy/xen.git
> > > > > 11. mailto:[127][128][129][130]pasik@xxxxxx
> > > > > 12.
> [128][129][130][131]http://2.6.32.10/kernel/drivers/xen
> > > > > 13. mailto:[129][130][131][132]pasik@xxxxxx
> > > > > 14.
> > > >
> > >
> >
> [130][131][132][133]http://git.kernel.org/pub/scm/linux/kernel/git/jeremy/xen.git
> > > > > 15. mailto:[131][132][133][134]pasik@xxxxxx
> > > > > 16.
> > > >
> > >
> >
> [132][133][134][135]http://git.kernel.org/pub/scm/linux/kernel/git/jeremy/xen.git
> > > > > 17. mailto:[133][134][135][136]pasik@xxxxxx
> > > > > 18. mailto:[134][135][136][137]pasik@xxxxxx
> > > > > 19.
> [135][136][137][138]http://2.6.32.10/kernel/drivers/xen
> > > > > 20. mailto:[136][137][138][139]pasik@xxxxxx
> > > > > 21.
> > > >
> > >
> >
> [137][138][139][140]http://git.kernel.org/pub/scm/linux/kernel/git/jeremy/xen.git
> > > > > 22. mailto:[138][139][140][141]pasik@xxxxxx
> > > > > 23.
> > > >
> > >
> >
> [139][140][141][142]http://git.kernel.org/pub/scm/linux/kernel/git/jeremy/xen.git
> > > > > 24. mailto:[140][141][142][143]pasik@xxxxxx
> > > > > 25.
> [141][142][143][144]http://2.6.32.10/kernel/drivers/xen
> > > > > 26. mailto:[142][143][144][145]pasik@xxxxxx
> > > > > 27.
> > > >
> > >
> >
> [143][144][145][146]http://git.kernel.org/pub/scm/linux/kernel/git/jeremy/xen.git
> > > > > 28. mailto:[144][145][146][147]pasik@xxxxxx
> > > > > 29.
> > > >
> > >
> >
> [145][146][147][148]http://git.kernel.org/pub/scm/linux/kernel/git/jeremy/xen.git
> > > > > 30. mailto:[146][147][148][149]pasik@xxxxxx
> > > > > 31.
> mailto:[147][148][149][150]bodkekumar@xxxxxxxxx
> > > > > 32. mailto:[148][149][150][151]pasik@xxxxxx
> > > > > 33. mailto:[149][150][151][152]pasik@xxxxxx
> > > > > 34.
> [150][151][152][153]http://2.6.32.10/kernel/drivers/xen
> > > > > 35. mailto:[151][152][153][154]pasik@xxxxxx
> > > > > 36.
> > > >
> > >
> >
> [152][153][154][155]http://git.kernel.org/pub/scm/linux/kernel/git/jeremy/xen.git
> > > > > 37. mailto:[153][154][155][156]pasik@xxxxxx
> > > > > 38.
> > > >
> > >
> >
> [154][155][156][157]http://git.kernel.org/pub/scm/linux/kernel/git/jeremy/xen.git
> > > > > 39. mailto:[155][156][157][158]pasik@xxxxxx
> > > > > 40.
> [156][157][158][159]http://2.6.32.10/kernel/drivers/xen
> > > > > 41. mailto:[157][158][159][160]pasik@xxxxxx
> > > > > 42.
> > > >
> > >
> >
> [158][159][160][161]http://git.kernel.org/pub/scm/linux/kernel/git/jeremy/xen.git
> > > > > 43. mailto:[159][160][161][162]pasik@xxxxxx
> > > > > 44.
> > > >
> > >
> >
> [160][161][162][163]http://git.kernel.org/pub/scm/linux/kernel/git/jeremy/xen.git
> > > > > 45. mailto:[161][162][163][164]pasik@xxxxxx
> > > > > 46. mailto:[162][163][164][165]pasik@xxxxxx
> > > > > 47.
> [163][164][165][166]http://2.6.32.10/kernel/drivers/xen
> > > > > 48. mailto:[164][165][166][167]pasik@xxxxxx
> > > > > 49.
> > > >
> > >
> >
> [165][166][167][168]http://git.kernel.org/pub/scm/linux/kernel/git/jeremy/xen.git
> > > > > 50. mailto:[166][167][168][169]pasik@xxxxxx
> > > > > 51.
> > > >
> > >
> >
> [167][168][169][170]http://git.kernel.org/pub/scm/linux/kernel/git/jeremy/xen.git
> > > > > 52. mailto:[168][169][170][171]pasik@xxxxxx
> > > > > 53.
> [169][170][171][172]http://2.6.32.10/kernel/drivers/xen
> > > > > 54. mailto:[170][171][172][173]pasik@xxxxxx
> > > > > 55.
> > > >
> > >
> >
> [171][172][173][174]http://git.kernel.org/pub/scm/linux/kernel/git/jeremy/xen.git
> > > > > 56. mailto:[172][173][174][175]pasik@xxxxxx
> > > > > 57.
> > > >
> > >
> >
> [173][174][175][176]http://git.kernel.org/pub/scm/linux/kernel/git/jeremy/xen.git
> > > > > 58. mailto:[174][175][176][177]pasik@xxxxxx
> > > > > 59. mailto:[175][176][177][178]pasik@xxxxxx
> > > > > 60.
> mailto:[176][177][178][179]bodkekumar@xxxxxxxxx
> > > > > 61. mailto:[177][178][179][180]pasik@xxxxxx
> > > > > 62. mailto:[178][179][180][181]pasik@xxxxxx
> > > > > 63.
> [179][180][181][182]http://2.6.32.10/kernel/drivers/xen
> > > > > 64. mailto:[180][181][182][183]pasik@xxxxxx
> > > > > 65.
> > > >
> > >
> >
> [181][182][183][184]http://git.kernel.org/pub/scm/linux/kernel/git/jeremy/xen.git
> > > > > 66. mailto:[182][183][184][185]pasik@xxxxxx
> > > > > 67.
> > > >
> > >
> >
> [183][184][185][186]http://git.kernel.org/pub/scm/linux/kernel/git/jeremy/xen.git
> > > > > 68. mailto:[184][185][186][187]pasik@xxxxxx
> > > > > 69.
> [185][186][187][188]http://2.6.32.10/kernel/drivers/xen
> > > > > 70. mailto:[186][187][188][189]pasik@xxxxxx
> > > > > 71.
> > > >
> > >
> >
> [187][188][189][190]http://git.kernel.org/pub/scm/linux/kernel/git/jeremy/xen.git
> > > > > 72. mailto:[188][189][190][191]pasik@xxxxxx
> > > > > 73.
> > > >
> > >
> >
> [189][190][191][192]http://git.kernel.org/pub/scm/linux/kernel/git/jeremy/xen.git
> > > > > 74. mailto:[190][191][192][193]pasik@xxxxxx
> > > > > 75. mailto:[191][192][193][194]pasik@xxxxxx
> > > > > 76.
> [192][193][194][195]http://2.6.32.10/kernel/drivers/xen
> > > > > 77. mailto:[193][194][195][196]pasik@xxxxxx
> > > > > 78.
> > > >
> > >
> >
> [194][195][196][197]http://git.kernel.org/pub/scm/linux/kernel/git/jeremy/xen.git
> > > > > 79. mailto:[195][196][197][198]pasik@xxxxxx
> > > > > 80.
> > > >
> > >
> >
> [196][197][198][199]http://git.kernel.org/pub/scm/linux/kernel/git/jeremy/xen.git
> > > > > 81. mailto:[197][198][199][200]pasik@xxxxxx
> > > > > 82.
> [198][199][200][201]http://2.6.32.10/kernel/drivers/xen
> > > > > 83. mailto:[199][200][201][202]pasik@xxxxxx
> > > > > 84.
> > > >
> > >
> >
> [200][201][202][203]http://git.kernel.org/pub/scm/linux/kernel/git/jeremy/xen.git
> > > > > 85. mailto:[201][202][203][204]pasik@xxxxxx
> > > > > 86.
> > > >
> > >
> >
> [202][203][204][205]http://git.kernel.org/pub/scm/linux/kernel/git/jeremy/xen.git
> > > > > 87. mailto:[203][204][205][206]pasik@xxxxxx
> > > > > 88.
> mailto:[204][205][206][207]bodkekumar@xxxxxxxxx
> > > > > 89. mailto:[205][206][207][208]pasik@xxxxxx
> > > > > 90. mailto:[206][207][208][209]pasik@xxxxxx
> > > > > 91.
> [207][208][209][210]http://2.6.32.10/kernel/drivers/xen
> > > > > 92. mailto:[208][209][210][211]pasik@xxxxxx
> > > > > 93.
> > > >
> > >
> >
> [209][210][211][212]http://git.kernel.org/pub/scm/linux/kernel/git/jeremy/xen.git
> > > > > 94. mailto:[210][211][212][213]pasik@xxxxxx
> > > > > 95.
> > > >
> > >
> >
> [211][212][213][214]http://git.kernel.org/pub/scm/linux/kernel/git/jeremy/xen.git
> > > > > 96. mailto:[212][213][214][215]pasik@xxxxxx
> > > > > 97.
> [213][214][215][216]http://2.6.32.10/kernel/drivers/xen
> > > > > 98. mailto:[214][215][216][217]pasik@xxxxxx
> > > > > 99.
> > > >
> > >
> >
> [215][216][217][218]http://git.kernel.org/pub/scm/linux/kernel/git/jeremy/xen.git
> > > > > 100. mailto:[216][217][218][219]pasik@xxxxxx
> > > > > 101.
> > > >
> > >
> >
> [217][218][219][220]http://git.kernel.org/pub/scm/linux/kernel/git/jeremy/xen.git

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

WARNING - OLD ARCHIVES

xen-devel

Re: [Xen-users] Starting xend: grep: /proc/xen/capabilities: No such fi