Valtteri Kiviniemi
2009-May-05 05:55 UTC
[Xen-devel] Latest pv_ops (2.6.30-rc3) and xen-unstable
Hi, I am testing the latest pv_ops kernel with xen-unstable. With a quick test run I got everything working except xentop (all the domUs start up with no problem.) xentop gives this warning: root@sm:/# xentop Failed to retrieve statistics from libxenstat and dmesg: xenbus_probe wake_waiting xenbus_probe wake_waiting XENBUS: Unable to read cpu state XENBUS: Unable to read cpu state XENBUS: Unable to read cpu state XENBUS: Unable to read cpu state XENBUS: Unable to read cpu state XENBUS: Unable to read cpu state XENBUS: Unable to read cpu state XENBUS: Unable to read cpu state xenbus_probe_devices backend xenbus_probe_devices failed xenbus_directory backend_probe_and_watch devices probed ok backend_probe_and_watch watch add ok ok backend_probe_and_watch all done xenbus_probe_devices device xenbus_probe_devices failed xenbus_directory frontend_probe_and_watch devices probed ok frontend_probe_and_watch watch add ok ok frontend_probe_and_watch all done /proc/xen is mounted. What could be the problem? - Valtteri Kiviniemi _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Jeremy Fitzhardinge
2009-May-05 21:17 UTC
Re: [Xen-devel] Latest pv_ops (2.6.30-rc3) and xen-unstable
Valtteri Kiviniemi wrote:> Hi, > > I am testing the latest pv_ops kernel with xen-unstable. With a quick > test run I got everything working except xentop (all the domUs start > up with no problem.) > > xentop gives this warning: > > root@sm:/# xentop > Failed to retrieve statistics from libxenstat > > and dmesg: > > xenbus_probe wake_waiting > xenbus_probe wake_waiting > XENBUS: Unable to read cpu state > XENBUS: Unable to read cpu state > XENBUS: Unable to read cpu state > XENBUS: Unable to read cpu state > XENBUS: Unable to read cpu state > XENBUS: Unable to read cpu state > XENBUS: Unable to read cpu state > XENBUS: Unable to read cpu state > xenbus_probe_devices backend > xenbus_probe_devices failed xenbus_directory > backend_probe_and_watch devices probed ok > backend_probe_and_watch watch add ok ok > backend_probe_and_watch all done > xenbus_probe_devices device > xenbus_probe_devices failed xenbus_directory > frontend_probe_and_watch devices probed ok > frontend_probe_and_watch watch add ok ok > frontend_probe_and_watch all done > > /proc/xen is mounted. > > What could be the problem?I''m guessing that whatever file it uses for statistics hasn''t been implemented yet. Could you have a look at tracking down what files it wants to use (strace might be a good start). J _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Boris Derzhavets
2009-May-06 16:50 UTC
[Xen-devel] Backport ZFS support and pygrub from Xen 3.4-rc4-pre to xen-3.3.1-11.fc11.src.rpm
I believe that , xen-backport-hg18782.patch from ./rpmbuild/SOURCES is
exactly raw content of change set 18782 from xen-unstable.hg
I am not sure would be adding
xen-backport-hg19322.patch (libfsimage: Support for zfs version 14.)
xen-backport-hg19323.patch (pygrub: Workaround for Solaris CR 1143256)
sufficient to to get properly ZFS support and pygrub backported to Xen 3.3.1
for Fedora.
I may be missing some more cs''s to complete the task.
Please, advise.
Boris.
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
Boris Derzhavets
2009-May-06 19:39 UTC
Re: [Xen-devel] Backport ZFS support and pygrub from Xen 3.4-rc4-pre to xen-3.3.1-11.fc11.src.rpm
Yes , i was able to add ZFS support and manage OpenSolaris DomUs.
I was still able to manage Linux DomUs , using two pygrub profiles :-
first one to install DomU , second one to load and run. Same way as in case of
building Xen Unstable Dom0 with pvops kernel on Ubuntu 8.10 server.
But, reinstalled libvirt,libvirt-python,python-virtinst,virt-manager and
virt-viewer
i was unable to reconnect to xend via both tools..
In meantime I am not sure was it an accident or it was supposed to happen.
In second case direct port Xen Unstable to F10 ( without libvirt, there is
xen-lib package dependency what prevents proper porting ) is obviously a
preferable solution.
Boris.
--- On Wed, 5/6/09, Boris Derzhavets <bderzhavets@yahoo.com> wrote:
From: Boris Derzhavets <bderzhavets@yahoo.com>
Subject: [Xen-devel] Backport ZFS support and pygrub from Xen 3.4-rc4-pre to
xen-3.3.1-11.fc11.src.rpm
To: xen-devel@lists.xensource.com
Date: Wednesday, May 6, 2009, 12:50 PM
I believe that , xen-backport-hg18782.patch from ./rpmbuild/SOURCES is
exactly raw content of change set 18782 from xen-unstable.hg
I am not sure would be adding
xen-backport-hg19322.patch (libfsimage: Support for zfs version 14.)
xen-backport-hg19323.patch (pygrub: Workaround for Solaris CR 1143256)
sufficient to to get properly ZFS support and pygrub backported to Xen 3.3.1
for Fedora.
I may be missing some more cs''s to complete the task.
Please, advise.
Boris.
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
Boris Derzhavets
2009-May-07 09:49 UTC
Re: [Xen-devel] Backport ZFS support and pygrub from Xen 3.4-rc4-pre to xen-3.3.1-11.fc11.src.rpm
Everything has been done from scratch and seems to be working. ZFS support
patches added to src.rpm and installed, libvirt packages installed . Xen 3.3.1
F10 Dom0 ( 2.6.30-rc3-tip) does have ZFS support and virt-install (
virt-manager) connects to xend and may be used for DomUs management.
Boris.
--- On Wed, 5/6/09, Boris Derzhavets <bderzhavets@yahoo.com> wrote:
From: Boris Derzhavets <bderzhavets@yahoo.com>
Subject: Re: [Xen-devel] Backport ZFS support and pygrub from Xen 3.4-rc4-pre to
xen-3.3.1-11.fc11.src.rpm
To: xen-devel@lists.xensource.com
Date: Wednesday, May 6, 2009, 3:39 PM
Yes , i was able to add ZFS support and manage OpenSolaris DomUs.
I was still able to manage Linux DomUs , using two pygrub profiles :-
first one to install DomU , second one to load and run. Same way as in case of
building Xen Unstable Dom0 with pvops kernel on Ubuntu 8.10 server.
But, reinstalled libvirt,libvirt-python,python-virtinst,virt-manager and
virt-viewer
i was unable to reconnect to xend via both tools..
In meantime I am not sure was it an accident or it was supposed to happen.
In second case direct port Xen Unstable to F10 ( without libvirt, there is
xen-lib package dependency what prevents proper porting ) is obviously a
preferable solution.
Boris.
--- On Wed, 5/6/09, Boris Derzhavets <bderzhavets@yahoo.com> wrote:
From: Boris Derzhavets <bderzhavets@yahoo.com>
Subject: [Xen-devel] Backport ZFS support and pygrub from Xen 3.4-rc4-pre to
xen-3.3.1-11.fc11.src.rpm
To: xen-devel@lists.xensource.com
Date: Wednesday, May 6, 2009, 12:50 PM
I believe that , xen-backport-hg18782.patch from ./rpmbuild/SOURCES is
exactly raw content of change set 18782 from xen-unstable.hg
I am not sure would be adding
xen-backport-hg19322.patch (libfsimage: Support for zfs version 14.)
xen-backport-hg19323.patch (pygrub: Workaround for Solaris CR 1143256)
sufficient to to get properly ZFS support and pygrub
backported to Xen 3.3.1 for Fedora.
I may be missing some more cs''s to complete the task.
Please, advise.
Boris.
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
Boris Derzhavets
2009-May-07 17:21 UTC
Re: [Xen-devel] Backport ZFS support and pygrub from Xen 3.4-rc4-pre to xen-3.3.1-11.fc11.src.rpm
I believe , backport ZFS support to Xen 3.3.1. on Fedora''s is done.
http://bderzhavets.wordpress.com/2009/05/07/backport-zfs-support-to-xen-331-f10-dom0-kernel-2630-rc3-tip/
Boris.
--- On Thu, 5/7/09, Boris Derzhavets <bderzhavets@yahoo.com> wrote:
From: Boris Derzhavets <bderzhavets@yahoo.com>
Subject: Re: [Xen-devel] Backport ZFS support and pygrub from Xen 3.4-rc4-pre to
xen-3.3.1-11.fc11.src.rpm
To: xen-devel@lists.xensource.com
Date: Thursday, May 7, 2009, 5:49 AM
Everything has been done from scratch and seems to be working. ZFS support
patches added to src.rpm and installed, libvirt packages installed . Xen 3.3.1
F10 Dom0 ( 2.6.30-rc3-tip) does have ZFS support and virt-install (
virt-manager) connects to xend and may be used for DomUs management.
Boris.
--- On Wed, 5/6/09, Boris Derzhavets <bderzhavets@yahoo.com> wrote:
From: Boris Derzhavets <bderzhavets@yahoo.com>
Subject: Re: [Xen-devel] Backport ZFS support and pygrub from Xen 3.4-rc4-pre to
xen-3.3.1-11.fc11.src.rpm
To: xen-devel@lists.xensource.com
Date: Wednesday, May 6, 2009, 3:39 PM
Yes , i was able to add ZFS support and manage OpenSolaris DomUs.
I was still able to manage Linux DomUs , using two pygrub profiles :-
first one to install DomU , second one to load and run. Same way as in case of
building Xen Unstable Dom0 with pvops kernel on Ubuntu 8.10 server.
But, reinstalled libvirt,libvirt-python,python-virtinst,virt-manager and
virt-viewer
i was unable to reconnect to xend via both tools..
In meantime I am not sure was it an accident or it was supposed to happen.
In second case direct port Xen Unstable to F10 ( without libvirt, there is
xen-lib package dependency what prevents proper porting ) is obviously a
preferable solution.
Boris.
--- On Wed, 5/6/09, Boris Derzhavets
<bderzhavets@yahoo.com> wrote:
From: Boris Derzhavets <bderzhavets@yahoo.com>
Subject: [Xen-devel] Backport ZFS support and pygrub from Xen 3.4-rc4-pre to
xen-3.3.1-11.fc11.src.rpm
To: xen-devel@lists.xensource.com
Date: Wednesday, May 6, 2009, 12:50 PM
I believe that , xen-backport-hg18782.patch from ./rpmbuild/SOURCES is
exactly raw content of change set 18782 from xen-unstable.hg
I am not sure would be adding
xen-backport-hg19322.patch (libfsimage: Support for zfs version 14.)
xen-backport-hg19323.patch (pygrub:
Workaround for Solaris CR 1143256)
sufficient to to get properly ZFS support and pygrub
backported to Xen 3.3.1 for Fedora.
I may be missing some more cs''s to complete the task.
Please, advise.
Boris.
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
Valtteri Kiviniemi
2009-May-07 18:47 UTC
Re: [Xen-devel] Latest pv_ops (2.6.30-rc3) and xen-unstable
Hi,
Yeah, so it seems to be:
root@sm:/# strace xentop
execve("/usr/sbin/xentop", ["xentop"], [/* 19 vars */]) = 0
brk(0) = 0x608000
mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0)
= 0x7f956d680000
access("/etc/ld.so.nohwcap", F_OK) = -1 ENOENT (No such file or
directory)
mmap(NULL, 8192, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0)
= 0x7f956d67e000
access("/etc/ld.so.preload", R_OK) = -1 ENOENT (No such file or
directory)
open("/etc/ld.so.cache", O_RDONLY) = 3
fstat(3, {st_mode=S_IFREG|0644, st_size=29661, ...}) = 0
mmap(NULL, 29661, PROT_READ, MAP_PRIVATE, 3, 0) = 0x7f956d676000
close(3) = 0
access("/etc/ld.so.nohwcap", F_OK) = -1 ENOENT (No such file or
directory)
open("/lib/tls/x86_64/libxenstore.so.3.0", O_RDONLY) = -1 ENOENT (No
such file or directory)
stat("/lib/tls/x86_64", 0x7fff75681320) = -1 ENOENT (No such file or
directory)
open("/lib/tls/libxenstore.so.3.0", O_RDONLY) = -1 ENOENT (No such
file
or directory)
stat("/lib/tls", 0x7fff75681320) = -1 ENOENT (No such file or
directory)
open("/lib/x86_64/libxenstore.so.3.0", O_RDONLY) = -1 ENOENT (No such
file or directory)
stat("/lib/x86_64", 0x7fff75681320) = -1 ENOENT (No such file or
directory)
open("/lib/libxenstore.so.3.0", O_RDONLY) = -1 ENOENT (No such file or
directory)
stat("/lib", {st_mode=S_IFDIR|0755, st_size=4096, ...}) = 0
open("/usr/lib/tls/x86_64/libxenstore.so.3.0", O_RDONLY) = -1 ENOENT
(No
such file or directory)
stat("/usr/lib/tls/x86_64", 0x7fff75681320) = -1 ENOENT (No such file
or
directory)
open("/usr/lib/tls/libxenstore.so.3.0", O_RDONLY) = -1 ENOENT (No such
file or directory)
stat("/usr/lib/tls", 0x7fff75681320) = -1 ENOENT (No such file or
directory)
open("/usr/lib/x86_64/libxenstore.so.3.0", O_RDONLY) = -1 ENOENT (No
such file or directory)
stat("/usr/lib/x86_64", 0x7fff75681320) = -1 ENOENT (No such file or
directory)
open("/usr/lib/libxenstore.so.3.0", O_RDONLY) = 3
read(3,
"\177ELF\2\1\1\0\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0@\34\0\0\0\0\0\0@"...,
832) = 832
fstat(3, {st_mode=S_IFREG|0755, st_size=28504, ...}) = 0
mmap(NULL, 2128584, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3,
0) = 0x7f956d25e000
mprotect(0x7f956d263000, 2093056, PROT_NONE) = 0
mmap(0x7f956d462000, 4096, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x4000) = 0x7f956d462000
mmap(0x7f956d463000, 10952, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0x7f956d463000
close(3) = 0
access("/etc/ld.so.nohwcap", F_OK) = -1 ENOENT (No such file or
directory)
open("/lib/libxenctrl.so.3.4", O_RDONLY) = -1 ENOENT (No such file or
directory)
open("/usr/lib/libxenctrl.so.3.4", O_RDONLY) = 3
read(3,
"\177ELF\2\1\1\0\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0PI\0\0\0\0\0\0@"...,
832)
= 832
fstat(3, {st_mode=S_IFREG|0755, st_size=107351, ...}) = 0
mmap(NULL, 2354144, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3,
0) = 0x7f956d01f000
mprotect(0x7f956d034000, 2097152, PROT_NONE) = 0
mmap(0x7f956d234000, 4096, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x15000) = 0x7f956d234000
mmap(0x7f956d235000, 166880, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0x7f956d235000
close(3) = 0
access("/etc/ld.so.nohwcap", F_OK) = -1 ENOENT (No such file or
directory)
open("/lib/libncurses.so.5", O_RDONLY) = 3
read(3,
"\177ELF\2\1\1\0\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0\320%\1\0\0\0\0\0@"...,
832) = 832
fstat(3, {st_mode=S_IFREG|0644, st_size=256288, ...}) = 0
mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0)
= 0x7f956d675000
mmap(NULL, 2353152, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3,
0) = 0x7f956cde0000
mprotect(0x7f956ce1b000, 2093056, PROT_NONE) = 0
mmap(0x7f956d01a000, 20480, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x3a000) = 0x7f956d01a000
close(3) = 0
access("/etc/ld.so.nohwcap", F_OK) = -1 ENOENT (No such file or
directory)
open("/lib/libc.so.6", O_RDONLY) = 3
read(3,
"\177ELF\2\1\1\0\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0\300\342\1\0\0\0\0\0@"...,
832) = 832
fstat(3, {st_mode=S_IFREG|0755, st_size=1375536, ...}) = 0
mmap(NULL, 3482232, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3,
0) = 0x7f956ca8d000
mprotect(0x7f956cbd7000, 2093056, PROT_NONE) = 0
mmap(0x7f956cdd6000, 20480, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x149000) = 0x7f956cdd6000
mmap(0x7f956cddb000, 17016, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0x7f956cddb000
close(3) = 0
access("/etc/ld.so.nohwcap", F_OK) = -1 ENOENT (No such file or
directory)
open("/lib/libpthread.so.0", O_RDONLY) = 3
read(3,
"\177ELF\2\1\1\0\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0\320W\0\0\0\0\0\0@"...,
832) = 832
fstat(3, {st_mode=S_IFREG|0755, st_size=130114, ...}) = 0
mmap(NULL, 2208624, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3,
0) = 0x7f956c871000
mprotect(0x7f956c887000, 2097152, PROT_NONE) = 0
mmap(0x7f956ca87000, 8192, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x16000) = 0x7f956ca87000
mmap(0x7f956ca89000, 13168, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0x7f956ca89000
close(3) = 0
access("/etc/ld.so.nohwcap", F_OK) = -1 ENOENT (No such file or
directory)
open("/lib/libdl.so.2", O_RDONLY) = 3
read(3,
"\177ELF\2\1\1\0\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0\20\16\0\0\0\0\0\0@"...,
832) = 832
fstat(3, {st_mode=S_IFREG|0644, st_size=14616, ...}) = 0
mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0)
= 0x7f956d674000
mmap(NULL, 2109728, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3,
0) = 0x7f956c66d000
mprotect(0x7f956c66f000, 2097152, PROT_NONE) = 0
mmap(0x7f956c86f000, 8192, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x2000) = 0x7f956c86f000
close(3) = 0
mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0)
= 0x7f956d673000
mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0)
= 0x7f956d672000
arch_prctl(ARCH_SET_FS, 0x7f956d6726e0) = 0
mprotect(0x7f956cdd6000, 12288, PROT_READ) = 0
munmap(0x7f956d676000, 29661) = 0
set_tid_address(0x7f956d672770) = 4096
set_robust_list(0x7f956d672780, 0x18) = 0
futex(0x7fff75681e0c, FUTEX_WAKE_PRIVATE, 1) = 0
rt_sigaction(SIGRTMIN, {0x7f956c876660, [], SA_RESTORER|SA_SIGINFO,
0x7f956c87fa80}, NULL, 8) = 0
rt_sigaction(SIGRT_1, {0x7f956c8766f0, [],
SA_RESTORER|SA_RESTART|SA_SIGINFO, 0x7f956c87fa80}, NULL, 8) = 0
rt_sigprocmask(SIG_UNBLOCK, [RTMIN RT_1], NULL, 8) = 0
getrlimit(RLIMIT_STACK, {rlim_cur=8192*1024, rlim_max=RLIM_INFINITY}) = 0
brk(0) = 0x608000
brk(0x629000) = 0x629000
open("/proc/xen/privcmd", O_RDWR) = 3
fcntl(3, F_GETFD) = 0
fcntl(3, F_SETFD, FD_CLOEXEC) = 0
stat("/var/run/xenstored/socket_ro", {st_mode=S_IFSOCK|0660,
st_size=0,
...}) = 0
socket(PF_FILE, SOCK_STREAM, 0) = 4
fcntl(4, F_GETFD) = 0
fcntl(4, F_SETFD, FD_CLOEXEC) = 0
connect(4, {sa_family=AF_FILE,
path="/var/run/xenstored/socket_ro"...},
110) = 0
ioctl(1, SNDCTL_TMR_TIMEBASE or TCGETS, {B38400 opost isig icanon echo
...}) = 0
stat("/home/toor/.terminfo", 0x7fff75680a40) = -1 ENOENT (No such file
or directory)
stat("/etc/terminfo", {st_mode=S_IFDIR|0755, st_size=4096, ...}) = 0
access("/etc/terminfo/x/xterm", R_OK) = -1 ENOENT (No such file or
directory)
stat("/lib/terminfo", {st_mode=S_IFDIR|0755, st_size=4096, ...}) = 0
access("/lib/terminfo/x/xterm", R_OK) = 0
open("/lib/terminfo/x/xterm", O_RDONLY) = 5
read(5, "\32\1\34\0\35\0\17\0\235\1&\5xterm|X11 terminal em"...,
4097) =
2244
close(5) = 0
ioctl(1, SNDCTL_TMR_TIMEBASE or TCGETS, {B38400 opost isig icanon echo
...}) = 0
ioctl(1, SNDCTL_TMR_TIMEBASE or TCGETS, {B38400 opost isig icanon echo
...}) = 0
ioctl(1, SNDCTL_TMR_TIMEBASE or TCGETS, {B38400 opost isig icanon echo
...}) = 0
ioctl(1, TIOCGWINSZ, {ws_row=61, ws_col=158, ws_xpixel=0, ws_ypixel=0}) = 0
ioctl(1, SNDCTL_TMR_TIMEBASE or TCGETS, {B38400 opost isig icanon echo
...}) = 0
ioctl(1, TIOCGWINSZ, {ws_row=61, ws_col=158, ws_xpixel=0, ws_ypixel=0}) = 0
brk(0x64a000) = 0x64a000
ioctl(1, SNDCTL_TMR_TIMEBASE or TCGETS, {B38400 opost isig icanon echo
...}) = 0
ioctl(1, SNDCTL_TMR_TIMEBASE or TCGETS, {B38400 opost isig icanon echo
...}) = 0
ioctl(1, SNDCTL_TMR_TIMEBASE or TCGETS, {B38400 opost isig icanon echo
...}) = 0
ioctl(1, SNDCTL_TMR_TIMEBASE or TCGETS, {B38400 opost isig icanon echo
...}) = 0
ioctl(1, SNDCTL_TMR_STOP or TCSETSW, {B38400 opost isig -icanon echo
...}) = 0
ioctl(1, SNDCTL_TMR_TIMEBASE or TCGETS, {B38400 opost isig -icanon echo
...}) = 0
ioctl(1, SNDCTL_TMR_TIMEBASE or TCGETS, {B38400 opost isig -icanon echo
...}) = 0
ioctl(1, SNDCTL_TMR_STOP or TCSETSW, {B38400 opost isig -icanon -echo
...}) = 0
ioctl(1, SNDCTL_TMR_TIMEBASE or TCGETS, {B38400 opost isig
-icanon -echo ...}) = 0
rt_sigaction(SIGTSTP, NULL, {SIG_DFL}, 8) = 0
rt_sigaction(SIGTSTP,
{0x7f956ce001f0, [], SA_RESTORER|SA_RESTART, 0x7f956cabef60}, NULL, 8) = 0
rt_sigaction(SIGINT, NULL, {SIG_DFL}, 8) = 0
rt_sigaction(SIGINT, {0x7f956ce00100, [],
SA_RESTORER|SA_RESTART, 0x7f956cabef60}, NULL, 8) = 0
rt_sigaction(SIGTERM, NULL, {SIG_DFL}, 8) = 0
rt_sigaction(SIGTERM, {0x7f956ce00100, [],
SA_RESTORER|SA_RESTART, 0x7f956cabef60}, NULL, 8) = 0
rt_sigaction(SIGWINCH, NULL,
{SIG_DFL}, 8) = 0
rt_sigaction(SIGWINCH, {0x7f956cdffef0, [], SA_RESTORER,
0x7f956cabef60}, NULL, 8) = 0
ioctl(1, SNDCTL_TMR_TIMEBASE or TCGETS, {B38400 opost isig
-icanon -echo ...}) = 0
ioctl(1, SNDCTL_TMR_TIMEBASE or TCGETS, {B38400 opost isig
-icanon -echo ...}) = 0
ioctl(1, SNDCTL_TMR_STOP or TCSETSW, {B38400 opost
isig -icanon -echo ...}) = 0
ioctl(1, SNDCTL_TMR_TIMEBASE or TCGETS, {B38400 opost isig
-icanon -echo ...}) = 0
) = 37
write(1,
"\33[?1049h\33[1;61r\33[m\33(B\33[4l\33[?7h\33[3"..., 45
ioctl(1, SNDCTL_TMR_TIMEBASE or TCGETS, {B38400 opost isig
-icanon -echo ...}) = 0
ioctl(1, SNDCTL_TMR_STOP or TCSETSW, {B38400 opost
isig icanon echo ...}) = 0
ioctl(1, SNDCTL_TMR_TIMEBASE or TCGETS, {B38400 opost isig icanon echo
...}) = 0
write(2, "Failed to retrieve statistics fro"..., 46Failed to retrieve
statistics from libxenstat
) = 46
close(5) = 0
munmap(0x7f956d67d000, 4096) = 0
close(3) = 0
close(4) = 0
exit_group(1) = ?
- Valtteri Kiviniemi
Jeremy Fitzhardinge kirjoitti:> Valtteri Kiviniemi wrote:
>> Hi,
>>
>> I am testing the latest pv_ops kernel with xen-unstable. With a quick
>> test run I got everything working except xentop (all the domUs start
>> up with no problem.)
>>
>> xentop gives this warning:
>>
>> root@sm:/# xentop
>> Failed to retrieve statistics from libxenstat
>>
>> and dmesg:
>>
>> xenbus_probe wake_waiting
>> xenbus_probe wake_waiting
>> XENBUS: Unable to read cpu state
>> XENBUS: Unable to read cpu state
>> XENBUS: Unable to read cpu state
>> XENBUS: Unable to read cpu state
>> XENBUS: Unable to read cpu state
>> XENBUS: Unable to read cpu state
>> XENBUS: Unable to read cpu state
>> XENBUS: Unable to read cpu state
>> xenbus_probe_devices backend
>> xenbus_probe_devices failed xenbus_directory
>> backend_probe_and_watch devices probed ok
>> backend_probe_and_watch watch add ok ok
>> backend_probe_and_watch all done
>> xenbus_probe_devices device
>> xenbus_probe_devices failed xenbus_directory
>> frontend_probe_and_watch devices probed ok
>> frontend_probe_and_watch watch add ok ok
>> frontend_probe_and_watch all done
>>
>> /proc/xen is mounted.
>>
>> What could be the problem?
>
> I''m guessing that whatever file it uses for statistics
hasn''t been
> implemented yet. Could you have a look at tracking down what files it
> wants to use (strace might be a good start).
>
> J
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
Ian Campbell
2009-May-08 09:03 UTC
Re: [Xen-devel] Latest pv_ops (2.6.30-rc3) and xen-unstable
On Thu, 2009-05-07 at 14:47 -0400, Valtteri Kiviniemi wrote:> Hi, > > Yeah, so it seems to be:The switch to/from curses has hidden most of the interesting stuff (including a useful error message :-(), if you redirect to a file you get: open("/sys/devices/xen-backend/", O_RDONLY|O_NONBLOCK|O_LARGEFILE|O_DIRECTORY) = -1 ENOENT (No such file or directory) dup(2) = 6 fcntl64(6, F_GETFL) = 0x8001 (flags O_WRONLY|O_LARGEFILE) close(6) = 0 write(2, "Error opening /sys/devices/xen-b"..., 67Error opening /sys/devices/xen-backend/: No such file or directory ) = 67 This path doesn''t exist in the pvops kernel. Looks like /sys/bus/xen-backend/devices is just as good and exists in both pvops and 2.6.18 kernels. Subject: xenstat: Use backend path which is compatible with pvops and 2.6.18-xen kernels. Signed-off-by: Ian Campbell <ian.campbell@citrix.com> diff -r 07812e857e67 tools/xenstat/libxenstat/src/xenstat_linux.c --- a/tools/xenstat/libxenstat/src/xenstat_linux.c Thu Apr 09 12:09:14 2009 +0100 +++ b/tools/xenstat/libxenstat/src/xenstat_linux.c Fri May 08 09:40:45 2009 +0100 @@ -31,7 +31,7 @@ #include "xenstat_priv.h" -#define SYSFS_VBD_PATH "/sys/devices/xen-backend/" +#define SYSFS_VBD_PATH "/sys/bus/xen-backend/devices" struct priv_data { FILE *procnetdev; _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Valtteri Kiviniemi
2009-May-08 18:48 UTC
Re: [Xen-devel] Latest pv_ops (2.6.30-rc3) and xen-unstable
Hi, Ok, with that patch I got it working. I''m still seeing these two error messages in dmesg: XENBUS: Unable to read cpu state and xenbus_probe_devices failed xenbus_directory are those something to worry about? - Valtteri Kiviniemi Ian Campbell kirjoitti:> On Thu, 2009-05-07 at 14:47 -0400, Valtteri Kiviniemi wrote: >> Hi, >> >> Yeah, so it seems to be: > > The switch to/from curses has hidden most of the interesting stuff > (including a useful error message :-(), if you redirect to a file you > get: > open("/sys/devices/xen-backend/", O_RDONLY|O_NONBLOCK|O_LARGEFILE|O_DIRECTORY) = -1 ENOENT (No such file or directory) > dup(2) = 6 > fcntl64(6, F_GETFL) = 0x8001 (flags O_WRONLY|O_LARGEFILE) > close(6) = 0 > write(2, "Error opening /sys/devices/xen-b"..., 67Error opening /sys/devices/xen-backend/: No such file or directory > ) = 67 > > This path doesn''t exist in the pvops kernel. Looks > like /sys/bus/xen-backend/devices is just as good and exists in both > pvops and 2.6.18 kernels. > > Subject: xenstat: Use backend path which is compatible with pvops and 2.6.18-xen kernels. > > Signed-off-by: Ian Campbell <ian.campbell@citrix.com> > > diff -r 07812e857e67 tools/xenstat/libxenstat/src/xenstat_linux.c > --- a/tools/xenstat/libxenstat/src/xenstat_linux.c Thu Apr 09 12:09:14 2009 +0100 > +++ b/tools/xenstat/libxenstat/src/xenstat_linux.c Fri May 08 09:40:45 2009 +0100 > @@ -31,7 +31,7 @@ > > #include "xenstat_priv.h" > > -#define SYSFS_VBD_PATH "/sys/devices/xen-backend/" > +#define SYSFS_VBD_PATH "/sys/bus/xen-backend/devices" > > struct priv_data { > FILE *procnetdev; > > > > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xensource.com > http://lists.xensource.com/xen-devel_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Daniel Schroeder
2009-May-25 09:24 UTC
[Xen-devel] [xenstat] Use backend path which is compatible with pvops -- status request
Ian Campbell wrote:> On Thu, 2009-05-07 at 14:47 -0400, Valtteri Kiviniemi wrote: >> Hi, >> >> Yeah, so it seems to be: > > The switch to/from curses has hidden most of the interesting stuff > (including a useful error message :-(), if you redirect to a file you > get: > open("/sys/devices/xen-backend/", O_RDONLY|O_NONBLOCK|O_LARGEFILE|O_DIRECTORY) = -1 ENOENT (No such file or directory) > dup(2) = 6 > fcntl64(6, F_GETFL) = 0x8001 (flags O_WRONLY|O_LARGEFILE) > close(6) = 0 > write(2, "Error opening /sys/devices/xen-b"..., 67Error opening /sys/devices/xen-backend/: No such file or directory > ) = 67 > > This path doesn''t exist in the pvops kernel. Looks > like /sys/bus/xen-backend/devices is just as good and exists in both > pvops and 2.6.18 kernels. > > Subject: xenstat: Use backend path which is compatible with pvops and 2.6.18-xen kernels. > > Signed-off-by: Ian Campbell <ian.campbell@citrix.com> > > diff -r 07812e857e67 tools/xenstat/libxenstat/src/xenstat_linux.c > --- a/tools/xenstat/libxenstat/src/xenstat_linux.c Thu Apr 09 12:09:14 2009 +0100 > +++ b/tools/xenstat/libxenstat/src/xenstat_linux.c Fri May 08 09:40:45 2009 +0100 > @@ -31,7 +31,7 @@ > > #include "xenstat_priv.h" > > -#define SYSFS_VBD_PATH "/sys/devices/xen-backend/" > +#define SYSFS_VBD_PATH "/sys/bus/xen-backend/devices" > > struct priv_data { > FILE *procnetdev; > >ping whats the status of this patch? Will it hit xen-unstable repo anytime soon? daniel _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel