I need your help.

[rainmaker]

Hello, My name is Daniel.

Thank you for this great project progress.

I've tried spice4xen to my server(CentOS 5.6).

My goal is to connect windows7 on Xen with SPICE Client.

I read README_spice on Wiki, and install "spice4xen on Xen4.0.1 with old Qemu".

$make install-xen => OK

$make install-kernels => OK

$make install-tools => Fail 

Fail message is

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

checking for XRANDR... no

configure: error: Package requirements (xrandr) were not met:

Package xrender was not found in the pkg-config search path.

Perhaps you should add the directory containing `xrender.pc'

to the PKG_CONFIG_PATH environment variable

Package 'xrender', required by 'Xrandr', not found

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

I've installed all related library(libXrandr-devel, libX11, libXrender, libXrandr, xrendr), but message is same.

I've search a lot of article on web, and try and failed.

Please let me know how to solve this problem and how to install spice4xen completely.

Thank you in advance.

[Zhou Peng]

Hi Daniel,

Where is the xrender.pc pls.
Could export PKG_CONFIG_PATH=$PKG_CONFIG_PATH:path-to-libxrender
solve the problem?

What's the building period, does it reaching building spice.
We built spice4xen on fc8-x64, and didn't encounter this problem.

Best,

--
Zhou Peng

[rainmaker]

Hi, thank for your reply.

I tried it again on Fedora 8(64bit) like your environment.

But I encounter another problem.

The error message is

make[4]: Entering directory `/usr/src/spice4xen.0.1/tools/ioemu-qemu-xen/i386-dm'

  LINK  i386-dm/qemu-dm

../libqemu_common.a(spice-core.o): In function `qemu_spice_add_interface':

/usr/src/spice4xen.0.1/tools/ioemu-qemu-xen/ui/spice-core.c:569: undefined reference to `spice_server_new'

/usr/src/spice4xen.0.1/tools/ioemu-qemu-xen/ui/spice-core.c:570: undefined reference to `spice_server_init'

../libqemu_common.a(spice-core.o): In function `qemu_spice_init':

/usr/src/spice4xen.0.1/tools/ioemu-qemu-xen/ui/spice-core.c:460: undefined reference to `spice_server_new'

/usr/src/spice4xen.0.1/tools/ioemu-qemu-xen/ui/spice-core.c:461: undefined reference to `spice_server_set_addr'

... 

I've tried to find the same issue on web, but few articles.

Do you happen to know this issue?

And I tried it on CentOS 6.3(64bit). The build process seems like success. :)

I read wiki on spice4xen web. 

"1. Build and install" process was successful on CentOS 6.3

But after build, I don't know how to use it.

I used SPICE on KVM with virt-manager. It's simple to use. 

Does spice4xen also use with virt-manager like KVM-SPICE?

If it is possible, how should I do? 

Please let me know detail reference or method to work spice4xen builded. 

Compiled spice4xen kernel also doesn't show on /etc/grub.conf.

I'm not professional about this. Please help me.

Thank you in advance.

[Zhou Peng]

On Tue, Oct 30, 2012 at 4:50 PM, rainmaker <hch...@gmail.com> wrote:
> Hi, thank for your reply.
> I tried it again on Fedora 8(64bit) like your environment.
> But I encounter another problem.
> The error message is
>
> make[4]: Entering directory
> `/usr/src/spice4xen.0.1/tools/ioemu-qemu-xen/i386-dm'
> LINK i386-dm/qemu-dm
> ../libqemu_common.a(spice-core.o): In function `qemu_spice_add_interface':
> /usr/src/spice4xen.0.1/tools/ioemu-qemu-xen/ui/spice-core.c:569: undefined
> reference to `spice_server_new'
> /usr/src/spice4xen.0.1/tools/ioemu-qemu-xen/ui/spice-core.c:570: undefined
> reference to `spice_server_init'
> ../libqemu_common.a(spice-core.o): In function `qemu_spice_init':
> /usr/src/spice4xen.0.1/tools/ioemu-qemu-xen/ui/spice-core.c:460: undefined
> reference to `spice_server_new'
> /usr/src/spice4xen.0.1/tools/ioemu-qemu-xen/ui/spice-core.c:461: undefined
> reference to `spice_server_set_addr'
> ...
>
> I've tried to find the same issue on web, but few articles.
> Do you happen to know this issue?

It seems, the linker didn't find the libspice-server, it should exists
in "/usr/local/spice-xen/lib"

> And I tried it on CentOS 6.3(64bit). The build process seems like success.
> :)
>
> I read wiki on spice4xen web.
> "1. Build and install" process was successful on CentOS 6.3
> But after build, I don't know how to use it.
> I used SPICE on KVM with virt-manager. It's simple to use.
> Does spice4xen also use with virt-manager like KVM-SPICE?

Use xm, which is Xen's tool, but will be replaced by xl.

> If it is possible, how should I do?
> Please let me know detail reference or method to work spice4xen builded.
> Compiled spice4xen kernel also doesn't show on /etc/grub.conf.
> I'm not professional about this. Please help me.
>
> Thank you in advance.
>
>
>> Hi Daniel,

It should work on CentOS, we tested on centos 5.6 before.

Steps:
* mkinitrd an initrd-2.6.18-xen.img

* Add a boot option for Xen in /etc/grub.conf
You can refer to your centos 6.3 boot option.

title Xen 4.0.1
root (hd0,x)
kernel /xen-4.0.1.gz
module /vmlinuz-2.6.18-xen ro root=LABEL=/ rhgb quiet
module /initrd-2.6.18-xen.img

* xend start

* Then you can refer wiki/README_spice to create a VM, and access it
with spice client.
Before access the VM, you can run 'xm list' to check if the vm exists.

The network driver of Linux 2.6.18 may not support your NIC,
if so, you need to find and build the driver from the source.

At last, I suggest to use Xen 4.2, which supports Spice now.

--
Zhou Peng

[rainmaker]

Dear Zhou Peng,

Thank you again for your help.

I'll try with the method you taught me.

You suggest to use Xen 4.2 at last to me, right?

I found some articles about that.

http://wiki.xen.org/wiki/QEMU_Upstream

http://wiki.xen.org/wiki/XL

I'll try it with article above on CentOS 6.3 and 5.6

1. Could you recommend Linux OS type to test above?

2. If you use Xen 4.2 and SPICE, could you let me know your experience.

Thank you in advance.

Daniel.

[Zhou Peng]

On Wed, Oct 31, 2012 at 9:01 AM, rainmaker <hch...@gmail.com> wrote:
> Dear Zhou Peng,
>
> Thank you again for your help.
> I'll try with the method you taught me.
>
> You suggest to use Xen 4.2 at last to me, right?

Yes, in the long run, this will be the standard spice support for Xen.

> I found some articles about that.
> http://wiki.xen.org/wiki/QEMU_Upstream
> http://wiki.xen.org/wiki/XL

You can also get info about vm's configuration options quickly from
http://xenbits.xen.org/docs/unstable/man/xl.cfg.5.html

>
> I'll try it with article above on CentOS 6.3 and 5.6
> 1. Could you recommend Linux OS type to test above?

I think CentOS and many other Linux are ok for Xen, although my dev
environment is fc8.
But spice needs 64bit Linux.

Some people from Xen-ML gived their dev environment.
http://xen.markmail.org/search/?q=zhoupeng+Panic+on+cpu0#query:zhoupeng%20Panic%20on%20cpu0+page:1+mid:ulavymt57e7vdvar+state:results

> 2. If you use Xen 4.2 and SPICE, could you let me know your experience.

For Xen 4.2 or Xen-unstable, you may need to run
`/etc/init.d/xencommon start` before running xl

You can also refer this topic on Xen-ML:
http://xen.markmail.org/search/?q=Unable+to+get+QXL+vga+working#query:Unable%20to%20get%20QXL%20vga%20working%20from%3A%22ZhouPeng%22+page:1+mid:ij7blunvo5m7vyh7+state:results
In this topic, you can ignore anything of qxl* related.

If some time later, you want to test qxl(which has not been committed
by Xen), you can refer:
http://xen.markmail.org/search/?q=zhoupeng#query:zhoupeng%20from%3AZhouPeng%20order%3Adate-backward+page:1+mid:rvagyujo466d7so6+state:results

--
Zhou Peng

[rainmaker]

Dear Zhou Peng,

Hello,

I always thank you for your kindness.

I've tried Xen 4.2.0 after you suggest to use xen newest version.

It's best way for me because Xen 4.2.0 support SPICE basically.

I refer wiki.xen.org. It has a lot of articles about xen concept, installation, etc.

I've tried to install Xen 4.2.0 on CentOS 5.6 installed old xen.

Fortunately, Xen 4.2.0 build process is success.

[Step]

./configure

make xen

make tools

make stubdom

make install-xen

make install-tools

make install-stubdom

[/etc/grub.conf]

title CentOS (2.6.18-308.16.1.el5xen)

        root (hd0,0)

        kernel /xen-4.2.0.gz dom0_mem=1024M loglvl=all guest_loglvl=all

        module /vmlinuz-2.6.18-308.16.1.el5xen ro root=/dev/VolGroup00/LogVol00 rhgb quiet

        module /initrd-2.6.18-308.16.1.el5xen.img

After reboot,

1. I tried

/etc/init.d/xencommons start

2. But failed with this error message.

[root@localhost init.d]# /etc/init.d/xencommons start

Starting C xenstored.................................

Could not start xenstored

3. And I tried

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

xencommons should be started first.

[root@localhost init.d]# xl info

host                   : localhost.localdomain

release                : 2.6.18-308.16.1.el5xen

version                : #1 SMP Tue Oct 2 22:50:05 EDT 2012

machine                : x86_64

nr_cpus                : 4

max_cpu_id             : 31

nr_nodes               : 1

cores_per_socket       : 4

threads_per_core       : 1

cpu_mhz                : 2133

hw_caps                : bfebfbff:2c100800:00000000:00003f40:029ee3ff:00000000:00000001:00000000

virt_caps              : hvm hvm_directio

total_memory           : 12277

free_memory            : 11087

sharing_freed_memory   : 0

sharing_used_memory    : 0

free_cpus              : 0

xen_major              : 4

xen_minor              : 2

xen_extra              : .0

xen_caps               : xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32 hvm-3.0-x86_32p hvm-3.0-x86_64 

xen_scheduler          : credit

xen_pagesize           : 4096

platform_params        : virt_start=0xffff800000000000

xen_changeset          : unavailable

xen_commandline        : dom0_mem=1024M loglvl=all guest_loglvl=all

cc_compiler            : gcc (GCC) 4.1.2 20080704 (Red Hat 4.1.2-52)

cc_compile_by          : root

cc_compile_domain      : localdomain

cc_compile_date        : Thu Nov  1 16:38:34 KST 2012

xend_config_format     : 4

[root@localhost init.d]# xl list

Name                                        ID   Mem VCPUs State Time(s)

(null)                                       0  1024     4     r-----      34.1

4. I've reinstall Xen 4.2.0 and tried a lot of things refer to this article(http://borken.me/cswiki/doku.php?id=xen_installation)

Please give some advice if you know something.

[Zhou Peng]

On Thu, Nov 1, 2012 at 4:23 PM, rainmaker <hch...@gmail.com> wrote:
> Dear Zhou Peng,
>

I don't know the exact reason, pls check /var/log/messages to
see what happened to xenstore.

This seems be a general problem for Xen, I suggest you can also ask on
Xen Mainling List.

I somewhat guess it may be compatibility problem,
you can have a try to use newer xen-dom0-kernel for xen4.2, eg. branch
xen/master
from git://git.kernel.org/pub/scm/linux/kernel/git/jeremy/xen.git
IIRC, if set KERNELS ?= linux-2.6-pvops in config/Linux.mk, then
make install-kernels will git clone it automatically

But you can ask this problem on Xen ML, then you may don't
need to try to rebuild dom0 kernel.

> Thank you in advance.
>
> Daniel.
>
>

> 2012년 10월 31일 수요일 오후 1시 57분 26초 UTC+9, zhoupeng 님의 말:

--
Zhou Peng

[rainmaker]

Dear Zhou Peng,

Thanks for your reply.

I have some questions.

1. I've try to use newer xen-dom-kernel from git://git.kernel.org/pub/scm/linux/kernel/git/jeremy/xen.git 

And I found the article how to install this kernel.

( git://git.kernel.org/pub/scm/linux/kernel/git/jeremy/xen.git ) 

But  "git checkout -b xen/stable-2.6.32.x origin/xen/stable-2.6.32.x " step is not working.

I don't have xen directory in kernel source I've downloaded.

I guess newer kernel was change, right? 

How should I do?

2. You said, "But you can ask this problem on Xen ML, then you may don't need to try to rebuild dom0 kernel."

Where is Xen ML? And how should I do to change to xen dom0 kernel without kernel compiling / building.

3. If you have experiences about using SPICE on Xen 4.2, please let me know the environment and method.

I think I'd better to try it on working environment first, and try it again on my different environment.

ex) If you use Fedora 17, I'll try it on Fedora 17.

Always thank you.

Sincerely

Daniel.

2012년 11월 1일 목요일 오후 7시 51분 19초 UTC+9, zhoupeng 님의 말:

[Zhou Peng]

On Tue, Nov 6, 2012 at 10:56 AM, rainmaker <hch...@gmail.com> wrote:
> Dear Zhou Peng,
>

> Thanks for your reply.
> I have some questions.
>
> 1. I've try to use newer xen-dom-kernel from
> git://git.kernel.org/pub/scm/linux/kernel/git/jeremy/xen.git
> And I found the article how to install this kernel.
> ( git://git.kernel.org/pub/scm/linux/kernel/git/jeremy/xen.git )
> But "git checkout -b xen/stable-2.6.32.x origin/xen/stable-2.6.32.x " step
> is not working.
> I don't have xen directory in kernel source I've downloaded.
> I guess newer kernel was change, right?
> How should I do?

git branch -a will show all the branches
If changed, I think you can try the master branch, which should be the default.

make install-kernels will git clone the kernel for you, which will be
stored in path-to-xen-root/
if the kernel dir cloned is empty, you can try,
`git branch -a` to show all the branches
`git check somebranch` to switch to the branch.

>
> 2. You said, "But you can ask this problem on Xen ML, then you may don't
> need to try to rebuild dom0 kernel."
> Where is Xen ML? And how should I do to change to xen dom0 kernel without
> kernel compiling / building.

google xen mailing list

> 3. If you have experiences about using SPICE on Xen 4.2, please let me know
> the environment and method.

pls refer the links to you before.
You can first let Xen run properly, then consider the spice.

pls feel free, build xen from the source at first time is really not
an so easy work.

--
Zhou Peng

[Zhou Peng]

On Wed, Nov 7, 2012 at 2:47 PM, Zhou Peng <ailvp...@gmail.com> wrote:
> On Tue, Nov 6, 2012 at 10:56 AM, rainmaker <hch...@gmail.com> wrote:
>> Dear Zhou Peng,
>>
>> Thanks for your reply.
>> I have some questions.
>>
>> 1. I've try to use newer xen-dom-kernel from
>> git://git.kernel.org/pub/scm/linux/kernel/git/jeremy/xen.git
>> And I found the article how to install this kernel.
>> ( git://git.kernel.org/pub/scm/linux/kernel/git/jeremy/xen.git )
>> But "git checkout -b xen/stable-2.6.32.x origin/xen/stable-2.6.32.x " step
>> is not working.
>> I don't have xen directory in kernel source I've downloaded.
>> I guess newer kernel was change, right?
>> How should I do?
> git branch -a will show all the branches
> If changed, I think you can try the master branch, which should be the default.
>
> make install-kernels will git clone the kernel for you, which will be
> stored in path-to-xen-root/
> if the kernel dir cloned is empty, you can try,
> `git branch -a` to show all the branches
> `git check somebranch` to switch to the branch.

`git checkout somebranch` to switch to the branch.

--
Zhou Peng

[rainmaker]

Dear Zhou Peng,

Always thank you for your kindness.

I installed Xen 4.2 on CentOS 6.3 successfully. Thank you again your help.

I have some problems using XL and virt-manager, I will ask these problems to Xen ML. :)

I've also tried to install spice4xen on Fedora 8 64bit / CentOS 6.3 64bit

Almost build errors are solved using your answer. But I have a problem too hard to solve for me.

I remember I asked before about same error.

Error message are here,

make[4]: Entering directory `/usr/src/spice4xen.0.1/tools/ioemu-qemu-xen/i386-dm'

  LINK  i386-dm/qemu-dm

../libqemu_common.a(spice-core.o): In function `qemu_spice_add_interface':

/usr/src/spice4xen.0.1/tools/ioemu-qemu-xen/ui/spice-core.c:569: undefined reference to `spice_server_new'

/usr/src/spice4xen.0.1/tools/ioemu-qemu-xen/ui/spice-core.c:570: undefined reference to `spice_server_init'

../libqemu_common.a(spice-core.o): In function `qemu_spice_init':

/usr/src/spice4xen.0.1/tools/ioemu-qemu-xen/ui/spice-core.c:460: undefined reference to `spice_server_new'

/usr/src/spice4xen.0.1/tools/ioemu-qemu-xen/ui/spice-core.c:461: undefined reference to `spice_server_set_addr'

... 

You said,

It seems, the linker didn't find the libspice-server, it should exists 
in "/usr/local/spice-xen/lib" 

So,

I've export the path to LD_LIBRARY_PATH like this,

export LD_LIBRARY_PATH=/usr/local/spice-xen/lib:$LD_LIBRARY_PATH

But error message is same.

Any idea or how to solve it?