Hi!
I will explain that a bit further...
dom0: Ubuntu 10.04-2 (amd64) kernel 2.6.32.39 running Xen 4.0.1
(amd64)
-> could easily compile and start dom0_working
domU: Ubuntu 10.04 (i386)
-> downloading kernel sources of kernel 2.6.32.11
-> patching with "pvdrivers-0.01/xenify.sh
xen-patches-2.6.32-1.tar.bz2" (works perfect)
-> copy the existing /boot/config-2.6.38.8 to this kernel
sources (thats correct?)
-> make menuconfig and just save & exit
If I now look at the .config of the 2.6.32.11 kernel, there is no
CONFIG_XEN_PVDRIVER option
-> make localmodconfig
-> make -j 9
-> cd pvdrivers-0.01 and ./build.sh (works)
Then I install the new compiled kernel with "make install
modules_install" and I restart.
Now I have booted the kernel 2.6.32.11 in a HVM guest machine
including additionally the pv modules, is that true?
Finally, the problem ist, that I cannot compile the domU_working,
because there are no pvxendrivers header files on the system.
I think I forgot one step or I have a general problem understanding
the whole process.
Where can I get the xen header Files?
It tried it also with kernel 2.6.38 and Ubuntu 11.04, but I cloud
not ./built the pvdrivers
because the compilation process termintated with
"Cannot compile, Error: linux-2.6.38.8/include/linux/autoconf.h:
missing".
Thank you!
Se
Am 29.06.2011 13:20, schrieb veerasena reddy:
I too used the same link (Linux
PV drivers for Xen HVM – building normally within an arbitrary
kernel tree)
Coulple of questions:
Could you please check whether your sources have
include/xenpvdrivers after applying the patch.
Have you disabled CONFIG_XEN and enabled CONFIG_XEN_PVDRIVERS as
module (CONFIG_XEN_PVDRIVERS=m)
Also, could you please share the error log.
Thanks & Regards,
VSR.
On Wed, Jun 29, 2011 at 3:41 PM,
Sebastian Biedermann
<biedermann@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
wrote:
Awesome, thank you very
much!
dom0 source compiles without problems!
domU source cannot find the xen headers:
#include <xenpvdrivers/evtchn.h>
#include <xenpvdrivers/xenbus.h>
#include <xenpvdrivers/interface/io/netif.h>
#include <xenpvdrivers/interface/memory.h>
#include <xenpvdrivers/balloon.h>
#include <xenpvdrivers/asm/maddr.h>
I compiled in the PV HVM modules using this tutorial:
http://blog.alex.org.uk/?s=xen
And built them into the guest kernel, it runs fine, but I
dont have the right headers.
Can you tell me which xenpvdrivers headers you are using and
where they come from?
Because e.g. I cannot find the asm/maddr.h in the xen
sources.. or anywhere else
Tank you !
Am 28.06.2011 15:24, schrieb veerasena reddy:
Hi,
I tried the same links but had to make some changes to
get it working.
Please find attached the sample working files for
sharing a domU HVM page to dom0.
It has been tested xen-4.0.1 and HVM guest running
ubuntu 10.10 with kernel version 2.6.35.9 (from kernel.org) compiled with
CONFIG_XEN disabled and PVHVM drivers compiled in as
modules.
Procedure:
1. Set LINUX_ROOT appropriately in Makefiles of dom0
and domU.
2. Set remote domain in dom0 appropriately
"info.remoteDomain = <domU_domain_id>"
3. Compile modules dom0 and domU respectively on dom0
and domU guest.
4. Load module on domU first.
# insmod ./domu_share.ko
5. do "dmesg" on domU and note down the grant
reference number
[ 1293.316240] gref = 770 <<<--- this
is the grant reference number
6. now load the module on dom0 by passing grant
reference number as module param
# insmod ./dom0_share.ko gref=770
7. do dmesg on dom0
======== dmesg on dom0 =====
xen: dom0: init_module with gref = 770
xen: dom0: shared_page = 269f4000, handle = 9, status
= 0
Bytes in page aseem sethi
XEN: dom: end init_module
======
Thanks & Regards,
VSR.
--
Sebastian Biedermann
Security Engineering Group
Technische Universität Darmstadt
This email and any files transmitted with it are confidential
and intended solely for the use of the individual or entity
to whom they are addressed. If you have received this email
in error please notify the sender.
--
Sebastian Biedermann
Security Engineering Group
Technische Universität Darmstadt
biedermann@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
This email and any files transmitted with it are confidential
and intended solely for the use of the individual or entity
to whom they are addressed. If you have received this email
in error please notify the sender.