Xen users - Aug 2010 - Did anyone succeeded in installing xen 4.0.0 on Debian Lenny?

There are not too many howtos regarding xen 4.0 on Debian lenny, so I tried them
all and all failed.

Starting with the "official" howto:

1. I ran
"apt-get install bcc bin86 gawk bridge-utils iproute libcurl3 
libcurl4-openssl-dev bzip2 module-init-tools transfig tgif texinfo 
texlive-latex-base texlive-latex-recommended texlive-fonts-extra 
texlive-fonts-recommended pciutils-dev mercurial build-essential make gcc 
libc6-dev zlib1g-dev python python-dev python-twisted libncurses5-dev patch 
libvncserver-dev libsdl-dev libjpeg62-dev iasl libbz2-dev e2fslibs-dev git-core 
uuid-dev ocaml libx11-dev"

2. I downloaded the source code for xen 4.0.0, untared it, did "make
world",
"make install"

3. "mkinitramfs -o /boot/initrd.img-2.6.31.13 2.6.31.13",
"update-grub",
"update-rc.d xend defaults 20 2", "update-rc.d xendomains
defaults 21 20"

The System starts with the xen kernel, but then:

Xend does not start "ERROR (SrvDaemon:349) Exception starting xend ((111, 
''Connection refused'')

I added "-x" to the init.d script file and ran /etc/init.d/xend again:

debian:~# /etc/init.d/xend start
+ shopt -s extglob
+ test -f /etc/default/xend
+ . /etc/default/xend
+ test xstart = xstart
+ test -d /proc/xen
+ test -d /proc/xen/capabilities
+ grep ''        xenfs$'' /proc/filesystems
+ grep ''^xenfs '' /proc/mounts
+ grep -q control_d /proc/xen/capabilities
+ case "$1" in
+ mkdir -p /var/lock/subsys
+ touch /var/lock/subsys/xend
+ test -z ''''
+ test -z ''''
+ [[ '''' == @(yes|on|1) ]]
+ [[ '''' == @(yes|on|1) ]]
+ xend start
+ await_daemons_up
+ i=1
+ rets=10
+ xend status
+ ''['' 3 -ne 0 -a 1 -lt 10 '']''
+ sleep 1
+ echo -n .
.+ i=2
+ xend status
+ ''['' 3 -ne 0 -a 2 -lt 10 '']''
+ sleep 1
+ echo -n .
.+ i=3
+ xend status
+ ''['' 3 -ne 0 -a 3 -lt 10 '']''
+ sleep 1
+ echo -n .
.+ i=4
+ xend status
+ ''['' 3 -ne 0 -a 4 -lt 10 '']''
+ sleep 1
+ echo -n .
.+ i=5
+ xend status
+ ''['' 3 -ne 0 -a 5 -lt 10 '']''
+ sleep 1
+ echo -n .
.+ i=6
+ xend status
+ ''['' 3 -ne 0 -a 6 -lt 10 '']''
+ sleep 1
+ echo -n .
.+ i=7
+ xend status
+ ''['' 3 -ne 0 -a 7 -lt 10 '']''
+ sleep 1
+ echo -n .
.+ i=8
+ xend status
+ ''['' 3 -ne 0 -a 8 -lt 10 '']''
+ sleep 1
+ echo -n .
.+ i=9
+ xend status
+ ''['' 3 -ne 0 -a 9 -lt 10 '']''
+ sleep 1
+ echo -n .
.+ i=10
+ xend status
+ ''['' 3 -ne 0 -a 10 -lt 10 '']''
+ exit 3

Any ideas? Any working howto?




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

Hi!
> There are not too many howtos regarding xen 4.0 on Debian lenny, so I tried
> them all and all failed.
I am using Xen 4 on Lenny for quite some time. At that time no official
Xen4 packages were available so I forward ported the Xen 3.4 debian dir and
patches to Xen 4.0 which worked fine.
I''d suggest you get the source of the Xen packages from unstable and
try to
compile them on Lenny. There are probably some dependencies you might need
to resolve but it should work just fine.
2.6.32 pvops kernels are available from backports and work just fine.

[SNIP]
> + xend status
> + ''['' 3 -ne 0 -a 9 -lt 10 '']''
> + sleep 1
> + echo -n .
> .+ i=10
> + xend status
> + ''['' 3 -ne 0 -a 10 -lt 10 '']''
> + exit 3
> Any ideas? Any working howto?
xend status is checking for a running daemon and therefor tries to connect
to the daemon for 10 seconds (or 10 times with 1 second sleep inbetween)
A return code of 0 means the daemon is running; exit code 3 means the
daemon is not running -- for whatever reason.

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

i use on some production server domO lenny with xen 4, kernel 2.6.32 from
jeremy git and xen from xen-4.0-testing.hg, installation mainly base on wiki
xen 4 howto, i have also try kernel 2.6.31 and xen 4.0.0 in past but with
problem

Meister Schieber wrote:
> 
> There are not too many howtos regarding xen 4.0 on Debian lenny, so I
> tried them 
> all and all failed.
> 
> Starting with the "official" howto:
> 
> 1. I ran
> "apt-get install bcc bin86 gawk bridge-utils iproute libcurl3 
> libcurl4-openssl-dev bzip2 module-init-tools transfig tgif texinfo 
> texlive-latex-base texlive-latex-recommended texlive-fonts-extra 
> texlive-fonts-recommended pciutils-dev mercurial build-essential make gcc 
> libc6-dev zlib1g-dev python python-dev python-twisted libncurses5-dev
> patch 
> libvncserver-dev libsdl-dev libjpeg62-dev iasl libbz2-dev e2fslibs-dev
> git-core 
> uuid-dev ocaml libx11-dev"
> 
> 2. I downloaded the source code for xen 4.0.0, untared it, did "make
> world", 
> "make install"
> 
> 3. "mkinitramfs -o /boot/initrd.img-2.6.31.13 2.6.31.13",
"update-grub",
> "update-rc.d xend defaults 20 2", "update-rc.d xendomains
defaults 21 20"
> 
> The System starts with the xen kernel, but then:
> 
> Xend does not start "ERROR (SrvDaemon:349) Exception starting xend
((111,
> ''Connection refused'')
> 
> I added "-x" to the init.d script file and ran /etc/init.d/xend
again:
> 
> debian:~# /etc/init.d/xend start
> + shopt -s extglob
> + test -f /etc/default/xend
> + . /etc/default/xend
> + test xstart = xstart
> + test -d /proc/xen
> + test -d /proc/xen/capabilities
> + grep ''        xenfs$'' /proc/filesystems
> + grep ''^xenfs '' /proc/mounts
> + grep -q control_d /proc/xen/capabilities
> + case "$1" in
> + mkdir -p /var/lock/subsys
> + touch /var/lock/subsys/xend
> + test -z ''''
> + test -z ''''
> + [[ '''' == @(yes|on|1) ]]
> + [[ '''' == @(yes|on|1) ]]
> + xend start
> + await_daemons_up
> + i=1
> + rets=10
> + xend status
> + ''['' 3 -ne 0 -a 1 -lt 10 '']''
> + sleep 1
> + echo -n .
> .+ i=2
> + xend status
> + ''['' 3 -ne 0 -a 2 -lt 10 '']''
> + sleep 1
> + echo -n .
> .+ i=3
> + xend status
> + ''['' 3 -ne 0 -a 3 -lt 10 '']''
> + sleep 1
> + echo -n .
> .+ i=4
> + xend status
> + ''['' 3 -ne 0 -a 4 -lt 10 '']''
> + sleep 1
> + echo -n .
> .+ i=5
> + xend status
> + ''['' 3 -ne 0 -a 5 -lt 10 '']''
> + sleep 1
> + echo -n .
> .+ i=6
> + xend status
> + ''['' 3 -ne 0 -a 6 -lt 10 '']''
> + sleep 1
> + echo -n .
> .+ i=7
> + xend status
> + ''['' 3 -ne 0 -a 7 -lt 10 '']''
> + sleep 1
> + echo -n .
> .+ i=8
> + xend status
> + ''['' 3 -ne 0 -a 8 -lt 10 '']''
> + sleep 1
> + echo -n .
> .+ i=9
> + xend status
> + ''['' 3 -ne 0 -a 9 -lt 10 '']''
> + sleep 1
> + echo -n .
> .+ i=10
> + xend status
> + ''['' 3 -ne 0 -a 10 -lt 10 '']''
> + exit 3
> 
> Any ideas? Any working howto?
> 
> 
> 
> _______________________________________________
> Xen-users mailing list
> Xen-users@lists.xensource.com
> http://lists.xensource.com/xen-users
> 
-- 
View this message in context:
http://old.nabble.com/Did-anyone-succeeded-in-installing-xen-4.0.0-on-Debian-Lenny--tp29405821p29406421.html
Sent from the Xen - User mailing list archive at Nabble.com.


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

2010/8/11 Adi Kriegisch <adi@cg.tuwien.ac.at>:
> Hi!
>
>> There are not too many howtos regarding xen 4.0 on Debian lenny, so I
tried
>> them all and all failed.
> I am using Xen 4 on Lenny for quite some time. At that time no official
> Xen4 packages were available so I forward ported the Xen 3.4 debian dir and
> patches to Xen 4.0 which worked fine.
> I''d suggest you get the source of the Xen packages from unstable
and try to
> compile them on Lenny. There are probably some dependencies you might need
> to resolve but it should work just fine.
> 2.6.32 pvops kernels are available from backports and work just fine.
Thanks, I will try that.

I just cannot believe that there is so much trouble with xen and one of the most
common linux distributions (debian / ubuntu). The "official"
lenny-xen-packages
(3.2.1) are total crap (try to get a domu (bridged or via PCI pass thru) runnig 
as a router for more than 3 reboots) and the "source code howto" does
not work
properly either. I really don''t know, how many days I have wasted
trying to get
this sh**t working. We are talking about two so called "stables" for
God''s sake!

Manfred Müller



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

On 11/08/2010, at 10:59 PM, Meister Schieber wrote:
> 2010/8/11 Adi Kriegisch <adi@cg.tuwien.ac.at>:
> > Hi!
> >
> >> There are not too many howtos regarding xen 4.0 on Debian lenny,
so I tried
> >> them all and all failed.
> > I am using Xen 4 on Lenny for quite some time. At that time no
official
> > Xen4 packages were available so I forward ported the Xen 3.4 debian
dir and
> > patches to Xen 4.0 which worked fine.
> > I''d suggest you get the source of the Xen packages from
unstable and try to
> > compile them on Lenny. There are probably some dependencies you might
need
> > to resolve but it should work just fine.
> > 2.6.32 pvops kernels are available from backports and work just fine.
> 
> Thanks, I will try that.
> 
> I just cannot believe that there is so much trouble with xen and one of the
most common linux distributions (debian / ubuntu). The "official"
lenny-xen-packages (3.2.1) are total crap (try to get a domu (bridged or via PCI
pass thru) runnig as a router for more than 3 reboots) and the "source code
howto" does not work properly either. I really don''t know, how
many days I have wasted trying to get this sh**t working. We are talking about
two so called "stables" for God''s sake!
> 
It would be absolutely fantastic if there were binary packages available to set
up a dom0 of the latest xen on debian and ubuntu. I don''t know enough
about it, but are there technical issues which stop this from happening?

Jeff



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

there are 4.0 pkgs in sid and sqeeze, you can use them for lenny with 
some deps from sid/sqeeze or recompile them...

I use the same pkgs for last ubuntu... have changed the deps for ubuntu

Am 11.08.2010 17:39, schrieb Jeff Williams:
>
> On 11/08/2010, at 10:59 PM, Meister Schieber wrote:
>
>> 2010/8/11 Adi Kriegisch <adi@cg.tuwien.ac.at
>> <mailto:adi@cg.tuwien.ac.at>>:
>> > Hi!
>> >
>> >> There are not too many howtos regarding xen 4.0 on Debian
lenny, so
>> I tried
>> >> them all and all failed.
>> > I am using Xen 4 on Lenny for quite some time. At that time no
official
>> > Xen4 packages were available so I forward ported the Xen 3.4
debian
>> dir and
>> > patches to Xen 4.0 which worked fine.
>> > I''d suggest you get the source of the Xen packages from
unstable and
>> try to
>> > compile them on Lenny. There are probably some dependencies you
might
>> need
>> > to resolve but it should work just fine.
>> > 2.6.32 pvops kernels are available from backports and work just
fine.
>>
>> Thanks, I will try that.
>>
>> I just cannot believe that there is so much trouble with xen and one
>> of the most common linux distributions (debian / ubuntu). The
>> "official" lenny-xen-packages (3.2.1) are total crap (try to
get a
>> domu (bridged or via PCI pass thru) runnig as a router for more than 3
>> reboots) and the "source code howto" does not work properly
either. I
>> really don''t know, how many days I have wasted trying to get
this
>> sh**t working. We are talking about two so called "stables"
for God''s
>> sake!
>>
>
> It would be absolutely fantastic if there were binary packages available
> to set up a dom0 of the latest xen on debian and ubuntu. I don''t
know
> enough about it, but are there technical issues which stop this from
> happening?
>
> Jeff
>
>
>
> _______________________________________________
> Xen-users mailing list
> Xen-users@lists.xensource.com
> http://lists.xensource.com/xen-users
-- 

Greetz

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

Hello,
Some weeks/month ago, I would have say no because Xen4 for Debian
Squeeze was packaged without HVM support.
But now, I just checked that while writing, you also have the
xen-qemu-dm-4.0 package thanks to Thomas Goirand. Wasn''t sure this had
been accepted in Squeeze before freeze, but it seems yes ;-)

If you prefer keeping Lenny, you can either backport Xen4 for lenny, or
compile it by hand.
I''ve done it successfully and documented here:
http://publications.jbfavre.org/virtualisation/migration_form_xen3_to_xen4_lvm_drbd_debian.en

Be carefull that this is not package so that you''ll have to kepp it
updated manually, but this work pretty well, even with HVM domU.

Regards,
JB

On 11/08/2010 19:42, Morbid Angel wrote:
> there are 4.0 pkgs in sid and sqeeze, you can use them for lenny with
> some deps from sid/sqeeze or recompile them...
> 
> I use the same pkgs for last ubuntu... have changed the deps for ubuntu
> 
> Am 11.08.2010 17:39, schrieb Jeff Williams:
>>
>> On 11/08/2010, at 10:59 PM, Meister Schieber wrote:
>>
>>> 2010/8/11 Adi Kriegisch <adi@cg.tuwien.ac.at
>>> <mailto:adi@cg.tuwien.ac.at>>:
>>> > Hi!
>>> >
>>> >> There are not too many howtos regarding xen 4.0 on Debian
lenny, so
>>> I tried
>>> >> them all and all failed.
>>> > I am using Xen 4 on Lenny for quite some time. At that time no
>>> official
>>> > Xen4 packages were available so I forward ported the Xen 3.4
debian
>>> dir and
>>> > patches to Xen 4.0 which worked fine.
>>> > I''d suggest you get the source of the Xen packages
from unstable and
>>> try to
>>> > compile them on Lenny. There are probably some dependencies
you might
>>> need
>>> > to resolve but it should work just fine.
>>> > 2.6.32 pvops kernels are available from backports and work
just fine.
>>>
>>> Thanks, I will try that.
>>>
>>> I just cannot believe that there is so much trouble with xen and
one
>>> of the most common linux distributions (debian / ubuntu). The
>>> "official" lenny-xen-packages (3.2.1) are total crap (try
to get a
>>> domu (bridged or via PCI pass thru) runnig as a router for more
than 3
>>> reboots) and the "source code howto" does not work
properly either. I
>>> really don''t know, how many days I have wasted trying to
get this
>>> sh**t working. We are talking about two so called
"stables" for God''s
>>> sake!
>>>
>>
>> It would be absolutely fantastic if there were binary packages
available
>> to set up a dom0 of the latest xen on debian and ubuntu. I
don''t know
>> enough about it, but are there technical issues which stop this from
>> happening?
>>
>> Jeff
>>
>>
>>
>> _______________________________________________
>> Xen-users mailing list
>> Xen-users@lists.xensource.com
>> http://lists.xensource.com/xen-users
> 

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

On 11 Aug 2010, at 15:59, Meister Schieber <meisterschieber@ymail.com>
wrote:
> 2010/8/11 Adi Kriegisch <adi@cg.tuwien.ac.at>:
> > Hi!
> >
> >> There are not too many howtos regarding xen 4.0 on Debian lenny,
so I tried
> >> them all and all failed.
> > I am using Xen 4 on Lenny for quite some time. At that time no
official
> > Xen4 packages were available so I forward ported the Xen 3.4 debian
dir and
> > patches to Xen 4.0 which worked fine.
> > I''d suggest you get the source of the Xen packages from
unstable and try to
> > compile them on Lenny. There are probably some dependencies you might
need
> > to resolve but it should work just fine.
> > 2.6.32 pvops kernels are available from backports and work just fine.
> 
> Thanks, I will try that.
> 
> I just cannot believe that there is so much trouble with xen and one of the
most common linux distributions (debian / ubuntu). The "official"
lenny-xen-packages (3.2.1) are total crap (try to get a domu (bridged or via PCI
pass thru) runnig as a router for more than 3 reboots) and the "source code
howto" does not work properly either. I really don''t know, how
many days I have wasted trying to get this sh**t working. We are talking about
two so called "stables" for God''s sake!
> 
If you are so upset about this, maybe you should help in the development.

There is no such thing as a free lunch.

> Manfred Müller
> 
> _______________________________________________
> Xen-users mailing list
> Xen-users@lists.xensource.com
> http://lists.xensource.com/xen-users

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

> From: Mark Adams <mark@campbell-lange.net>
> If you are so upset about this, maybe you should help in the development.
> There is no such thing as a free lunch.
I wouldn''t go so far and call it a "free lunch", if someone
has to cook by
himself, given the wrong recipe and old ingredients. 

But thanks for you help anyway.

Manfred




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

2010/8/11 Jean Baptiste FAVRE
<xen-users@jbfavre.org>:
> Hello,
> Some weeks/month ago, I would have say no because Xen4 for Debian
> Squeeze was packaged without HVM support.
> But now, I just checked that while writing, you also have the
> xen-qemu-dm-4.0 package thanks to Thomas Goirand. Wasn''t sure this
had
> been accepted in Squeeze before freeze, but it seems yes ;-)
>
> If you prefer keeping Lenny, you can either backport Xen4 for lenny, or
> compile it by hand.
> I''ve done it successfully and documented here:
>http://publications.jbfavre.org/virtualisation/migration_form_xen3_to_xen4_lvm_drbd_debian.en
>n
>
> Be carefull that this is not package so that you''ll have to kepp
it
> updated manually, but this work pretty well, even with HVM domU.
>
> Regards,
> JB
Your documentation looks fantastic! Thank you very much, I''ll try that 
immediatly.

Manfred



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

Hello Manfred,
Thanks for compliment ;-)
Do not hesitate to report any way of improvement you could think about.

Regards,
JB

Le 12/08/2010 08:06, Meister Schieber a écrit :
> 2010/8/11 Jean Baptiste FAVRE <xen-users@jbfavre.org>:
>  > Hello,
>  > Some weeks/month ago, I would have say no because Xen4 for Debian
>  > Squeeze was packaged without HVM support.
>  > But now, I just checked that while writing, you also have the
>  > xen-qemu-dm-4.0 package thanks to Thomas Goirand. Wasn''t
sure this had
>  > been accepted in Squeeze before freeze, but it seems yes ;-)
>  >
>  > If you prefer keeping Lenny, you can either backport Xen4 for lenny,
or
>  > compile it by hand.
>  > I''ve done it successfully and documented here:
>>
>
http://publications.jbfavre.org/virtualisation/migration_form_xen3_to_xen4_lvm_drbd_debian.en
>  >
>  > Be carefull that this is not package so that you''ll have to
kepp it
>  > updated manually, but this work pretty well, even with HVM domU.
>  >
>  > Regards,
>  > JB
>
> Your documentation looks fantastic! Thank you very much, I''ll try
that
> immediatly.
>
> Manfred
>
>

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

Od 9 do 20 sierpnia jestem na urlopie.
W sprawach pilnych proszę kontaktować się z sekretariatem (+48) 22 227 77 88.
Dziękuję.




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

2010/8/11 Jean Baptiste FAVRE <xen-users@jbfavre.org>:
> If you prefer keeping Lenny, you can either backport Xen4 for lenny, or
> compile it by hand.
> I''ve done it successfully and documented here:
>http://publications.jbfavre.org/virtualisation/migration_form_xen3_to_xen4_lvm_drbd_debian.en
>n
I am trying to follow the steps in your howto, but: Is there a reason why you 
install both images?

"aptitude install linux-image-2.6.32-bpo.4-amd64 
linux-image-2.6.32-bpo.4-xen-amd64"When I do that and restart the system,
the
systems hangs. Shouldn''t xen 4.0.0 be installed before rebooting the
system?



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

Hi Meister,

here''s a link to a tutorial I wrote for myself... It''s in
Catalan but the code section is pretty straight forward.

http://www.osconfig.org/2010/04/26/xen-4-0-sobre-debian-lenny-5-0/

Hope it helps a bit on getting Xen 4 working on Debian Lenny.

If you need anymore help don''t hesitate to ask.

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

Le 12/08/2010 16:03, Meister Schieber a écrit :
> 2010/8/11 Jean Baptiste FAVRE <xen-users@jbfavre.org
> <mailto:xen-users@jbfavre.org>>:
>
>  > If you prefer keeping Lenny, you can either backport Xen4 for lenny,
or
>  > compile it by hand.
>  > I''ve done it successfully and documented here:
>>
>
http://publications.jbfavre.org/virtualisation/migration_form_xen3_to_xen4_lvm_drbd_debian.en
>
<http://publications.jbfavre.org/virtualisation/migration_form_xen3_to_xen4_lvm_drbd_debian.en>
>
> I am trying to follow the steps in your howto, but: Is there a reason
> why you install both images?
Yes, this allow you to get a working system in case of Xen failure ;-)
> |"aptitude install linux-image-2.6.32-bpo.4-amd64
linux-image-2.6.32-bpo.4-xen-amd64"|
>
> When I do that and restart the system, the systems hangs.
Shouldn''t xen
> 4.0.0 be installed before rebooting the system?
Not if you choose to work from the non-Xen kernel.

Which kernel do you choose on boot ?
The normal one, the xen enable one, or the old Xen hypervisor ?
If system hangs with normal one, you''ve got a problem. normally, you 
should never boot on Xen enable one. Finally, maybe booting Xen 
hypervisor 3.2 with 2.6.32 xen kernel cause some troubles I''m not aware
of.

Do you have any console message to provide ?

Regards,
JB

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

Od 9 do 20 sierpnia jestem na urlopie.
W sprawach pilnych proszę kontaktować się z sekretariatem (+48) 22 227 77 88.
Dziękuję.




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

From: Jean Baptiste FAVRE <xen-users@jbfavre.org>
Subject: Re: [Xen-users] Did anyone succeeded in installing xen 4.0.0 on Debian 
Lenny?
> I''ve done it successfully and documented here:
>
>http://publications.jbfavre.org/virtualisation/migration_form_xen3_to_xen4_lvm_drbd_debian.en
>n
><http://publications.jbfavre.org/virtualisation/migration_form_xen3_to_xen4_lvm_drbd_debian.en>
>>
>
> I am trying to follow the steps in your howto, but: Is there a reason
> why you install both images?
Yes, this allow you to get a working system in case of Xen failure ;-)


I started from the beginning with a fresh debian system and now it seems to 
work, thank you very much!

Only one more question: I replaced "/etc/sysconfig" with
"/etc/default" in xend
and xendomains as suggested in your howto. As there are serveral other files 
with "/etc/sysconfig" in the source code: Is there really no need to
change
these files too?




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

Hello,

Le 17/08/2010 14:32, Meister Schieber a écrit :
> From: Jean Baptiste FAVRE <xen-users@jbfavre.org>
> Subject: Re: [Xen-users] Did anyone succeeded in installing xen 4.0.0 on
> Debian Lenny?
>
>  > I''ve done it successfully and documented here:
>  >
>>
>
http://publications.jbfavre.org/virtualisation/migration_form_xen3_to_xen4_lvm_drbd_debian.en
>>
>
<http://publications.jbfavre.org/virtualisation/migration_form_xen3_to_xen4_lvm_drbd_debian.en>
>  >
>  > I am trying to follow the steps in your howto, but: Is there a reason
>  > why you install both images?
> Yes, this allow you to get a working system in case of Xen failure ;-)
>
>
> I started from the beginning with a fresh debian system and now it seems
> to work, thank you very much!
>
> Only one more question: I replaced "/etc/sysconfig" with
"/etc/default"
> in xend and xendomains as suggested in your howto. As there are serveral
> other files with "/etc/sysconfig" in the source code: Is there
really no
> need to change these files too?
Which files do you talk about ?
Changing /etc/sysconfig to /etc/default is mandatory because 
/etc/sysconfig does not exist on Debian.

But you should only change that to something relevant. "xend" and 
"xendomains" should be stored in /etc/default on Debian because these 
files are used to set default config values.

When I performed my tests, I was not aware of any other files impacted 
by these changes.

Regards,
JB

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

Od 9 do 20 sierpnia jestem na urlopie.
W sprawach pilnych proszę kontaktować się z sekretariatem (+48) 22 227 77 88.
Dziękuję.




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

> 2010/8/18 Jean Baptiste FAVRE <xen-users@jbfavre.org>:
>> Only one more question: I replaced "/etc/sysconfig" with
"/etc/default"
>> in xend and xendomains as suggested in your howto. As there are
serveral
>> other files with "/etc/sysconfig" in the source code: Is
there really no
>> need to change these files too?
>
> Which files do you talk about ?
> Changing /etc/sysconfig to /etc/default is mandatory because /etc/sysconfig
> does not exist on Debian.
I just ran "grep -iR "/etc/sysconfig" in /usr/src/xen-4.0.0 and
there were
several files containing that path:

/usr/src/xen-4.0.0# grep -iR "/etc/sysconfig" *
dist/install/etc/xen/scripts/xen-network-common.sh:  first_file -f 
/etc/sysconfig/dhcpd /etc/defaults/dhcp /etc/default/dhcp3-server
docs/src/user.tex:\path{/etc/sysconfig/mouse} to contain the lines:
docs/src/user.tex:\texttt{/etc/sysconfig/networking}. Vnets work anyway, but 
performance can be reduced
docs/misc/network_setup.txt:In the /etc/sysconfig/network-scripts directory it 
is necccessary to create
docs/misc/network_setup.txt:# echo "-I FORWARD -m physdev
--physdev-is-bridged
-j ACCEPT" > /etc/sysconfig/iptables-forward-bridged
docs/misc/network_setup.txt:# lokkit 
--custom-rules=ipv4:filter:/etc/sysconfig/iptables-forward-bridged
(...)


Another "last question": The Kernel 2.6.32-bpo.4-xen-686 does not seem
to have
the pci backend drivers compiled in, so I am not able to pass the pci devices 
"thru". Do you now of any precompiled debian kernels which work with
xen 4.0?



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

> >
> > Which files do you talk about ?
> > Changing /etc/sysconfig to /etc/default is mandatory because
/etc/sysconfig
> > does not exist on Debian.
> 
> I just ran "grep -iR "/etc/sysconfig" in /usr/src/xen-4.0.0
and there were
> several files containing that path:
> 
> /usr/src/xen-4.0.0# grep -iR "/etc/sysconfig" *
> dist/install/etc/xen/scripts/xen-network-common.sh:  first_file -f 
> /etc/sysconfig/dhcpd /etc/defaults/dhcp /etc/default/dhcp3-server
> docs/src/user.tex:\path{/etc/sysconfig/mouse} to contain the lines:
> docs/src/user.tex:\texttt{/etc/sysconfig/networking}. Vnets work anyway,
but
> performance can be reduced
> docs/misc/network_setup.txt:In the /etc/sysconfig/network-scripts directory
it
> is necccessary to create
> docs/misc/network_setup.txt:# echo "-I FORWARD -m physdev
--physdev-is-bridged
> -j ACCEPT" > /etc/sysconfig/iptables-forward-bridged
> docs/misc/network_setup.txt:# lokkit 
> --custom-rules=ipv4:filter:/etc/sysconfig/iptables-forward-bridged
> (...)
> 
> 
> Another "last question": The Kernel 2.6.32-bpo.4-xen-686 does not
seem to have
> the pci backend drivers compiled in, so I am not able to pass the pci
devices
> "thru". Do you now of any precompiled debian kernels which work
with xen 4.0?
> 
You should just use Squeeze (which is frozen now so on it''s way to
being the new stable). It works well simply by installing the
xen-linux-system and xen-qemu-dm packages. It includes pciback.

If you are so far into setup now that you want to stick with it, you
could try the linux-image-2.6.32-5-xen-amd64 kernel from the debian
repos.

Regards,
Mark

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

Hello,

Le 18/08/2010 16:37, Meister Schieber a écrit :
>  > 2010/8/18 Jean Baptiste FAVRE <xen-users@jbfavre.org>:
>  >> Only one more question: I replaced "/etc/sysconfig"
with "/etc/default"
>  >> in xend and xendomains as suggested in your howto. As there are
serveral
>  >> other files with "/etc/sysconfig" in the source code:
Is there really no
>  >> need to change these files too?
>  >
>  > Which files do you talk about ?
>  > Changing /etc/sysconfig to /etc/default is mandatory because
> /etc/sysconfig
>  > does not exist on Debian.
>
> I just ran "grep -iR "/etc/sysconfig" in /usr/src/xen-4.0.0
and there
> were several files containing that path:
>
> /usr/src/xen-4.0.0# grep -iR "/etc/sysconfig" *
> dist/install/etc/xen/scripts/xen-network-common.sh: first_file -f
> /etc/sysconfig/dhcpd /etc/defaults/dhcp /etc/default/dhcp3-server
> docs/src/user.tex:\path{/etc/sysconfig/mouse} to contain the lines:
> docs/src/user.tex:\texttt{/etc/sysconfig/networking}. Vnets work anyway,
> but performance can be reduced
> docs/misc/network_setup.txt:In the /etc/sysconfig/network-scripts
> directory it is necccessary to create
> docs/misc/network_setup.txt:# echo "-I FORWARD -m physdev
> --physdev-is-bridged -j ACCEPT" >
/etc/sysconfig/iptables-forward-bridged
> docs/misc/network_setup.txt:# lokkit
> --custom-rules=ipv4:filter:/etc/sysconfig/iptables-forward-bridged
> (...)
As far as I remember, once you modified the 2 init scripts xend and 
xendomains, you''re done: only these 2 scripts try to find
/etc/sysconfig
only.

For example, xen-network-common.sh you also mentionned will use the 
first file (function first_file) that can be found in various locations, 
including /etc/default.

Finally, if you''re installing a production-ready dom0, I don''t
think you
want to install documentation ;-)
> Another "last question": The Kernel 2.6.32-bpo.4-xen-686 does not
seem
> to have the pci backend drivers compiled in, so I am not able to pass
> the pci devices "thru". Do you now of any precompiled debian
kernels
> which work with xen 4.0?
I don''t exactly know as I do not use PCI passtrough. But I just saw 
Mark''s answer.

That make me think I''ll have to upgrade to Squeeze ;-)

Regards,
JB

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

Od 9 do 20 sierpnia jestem na urlopie.
W sprawach pilnych proszę kontaktować się z sekretariatem (+48) 22 227 77 88.
Dziękuję.




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

From: Mark Adams <mark@campbell-lange.net>
>You should just use Squeeze (which is frozen now so on it''s way to
>being the new stable). It works well simply by installing the
>xen-linux-system and xen-qemu-dm packages. It includes pciback.
Tried that for the last days, did not work either. The installation of squeeze 
and xen 4.0 was very easy indeed, only the pci-passthru does not work (tried 3 
different computers with different hardware).

Regarding to http://wiki.xensource.com/xenwiki/XenPCIpassthrough I used the 
options:
xen-pciback.hide=(09:00.0)
and
pciback.permissive pciback.hide=(09:00.0) pci=resource_alignment=09:00.0
and
xen-pciback.permissive xen-pciback.hide=(09:00.0) 
pci=resource_alignment=(09:00.0)

combined with "swiotlb=force" and "iommu=soft swiotlb=force"
in the DomU
(the "official" wiki has no special entries for the current release
4.0, so I
tried every combination...)

It just does not work, either the domU does not even start with some of the 
options, or the domU starts but the nic does not come up.
>If you are so far into setup now that you want to stick with it, you
>could try the linux-image-2.6.32-5-xen-amd64 kernel from the debian
>repos.
I am so far into several setups (plural) that I just does not want to give up 
and switch to vmware, so I desperately ask again: Did anyone succeeded in 
installing xen 4 on _any_ Debian version _and_ got a passed through NIC working 
in the DomU?



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

On Tue, Sep 07, 2010 at 12:22:24PM +0000, Meister Schieber
wrote:
>    From: Mark Adams <mark@campbell-lange.net>
>    >You should just use Squeeze (which is frozen now so on it''s
way to
>    >being the new stable). It works well simply by installing the
>    >xen-linux-system and xen-qemu-dm packages. It includes pciback.
> 
>    Tried that for the last days, did not work either. The installation of
>    squeeze and xen 4.0 was very easy indeed, only the pci-passthru does not
>    work (tried 3 different computers with different hardware).
> 
>    Regarding to [1]http://wiki.xensource.com/xenwiki/XenPCIpassthrough I
used
>    the options:
>    xen-pciback.hide=(09:00.0)
>    and
>    pciback.permissive pciback.hide=(09:00.0) pci=resource_alignment=09:00.0
>    and
>    xen-pciback.permissive xen-pciback.hide=(09:00.0)
>    pci=resource_alignment=(09:00.0)
> 
>    combined with "swiotlb=force" and "iommu=soft
swiotlb=force" in the DomU
>    (the "official" wiki has no special entries for the current
release 4.0,
>    so I tried every combination...)
> 
>    It just does not work, either the domU does not even start with some of
>    the options, or the domU starts but the nic does not come up.
> 
>    >If you are so far into setup now that you want to stick with it, you
>    >could try the linux-image-2.6.32-5-xen-amd64 kernel from the debian
>    >repos.
> 
>    I am so far into several setups (plural) that I just does not want to
give
>    up and switch to vmware, so I desperately ask again: Did anyone
succeeded
>    in installing xen 4 on _any_ Debian version _and_ got a passed through
NIC
>    working in the DomU?
> 
Yeah just yesterday someone was doing it.. and writing to ##xen on irc.

What domU kernel are you using? Does it have xen-pcifront? 
What does "lspci" show in the domU?

What pci related do you have in the domU dmesg? 

-- Pasi


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

As Pasi says it does work, I am using it to passthrough a nic. Out of your
options only the xen-pciback.hide on the kernel command line was required for
me, plus of course the config in the vm.cfg file.

In your xm dmesg does it show that the device was successfully hidden? What do
you get from xm list-pci-assignable-devices? (sorry that may not be 100%
accurate command it''s something like that)

I did have issues with 1 quad port Gb pci-e card. It would hide correctly but
the domU would not load it as an interface (I think now maybe because the domU
was Lenny not tested that theory though).

Can give you some more detailed config tomorrow if required.
 
Regards,
Mark

On 7 Sep 2010, at 18:19, Pasi Kärkkäinen <pasik@iki.fi> wrote:
> On Tue, Sep 07, 2010 at 12:22:24PM +0000, Meister Schieber wrote:
>>   From: Mark Adams <mark@campbell-lange.net>
>>> You should just use Squeeze (which is frozen now so on
it''s way to
>>> being the new stable). It works well simply by installing the
>>> xen-linux-system and xen-qemu-dm packages. It includes pciback.
>> 
>>   Tried that for the last days, did not work either. The installation
of
>>   squeeze and xen 4.0 was very easy indeed, only the pci-passthru does
not
>>   work (tried 3 different computers with different hardware).
>> 
>>   Regarding to [1]http://wiki.xensource.com/xenwiki/XenPCIpassthrough I
used
>>   the options:
>>   xen-pciback.hide=(09:00.0)
>>   and
>>   pciback.permissive pciback.hide=(09:00.0)
pci=resource_alignment=09:00.0
>>   and
>>   xen-pciback.permissive xen-pciback.hide=(09:00.0)
>>   pci=resource_alignment=(09:00.0)
>> 
>>   combined with "swiotlb=force" and "iommu=soft
swiotlb=force" in the DomU
>>   (the "official" wiki has no special entries for the current
release 4.0,
>>   so I tried every combination...)
>> 
>>   It just does not work, either the domU does not even start with some
of
>>   the options, or the domU starts but the nic does not come up.
>> 
>>> If you are so far into setup now that you want to stick with it,
you
>>> could try the linux-image-2.6.32-5-xen-amd64 kernel from the debian
>>> repos.
>> 
>>   I am so far into several setups (plural) that I just does not want to
give
>>   up and switch to vmware, so I desperately ask again: Did anyone
succeeded
>>   in installing xen 4 on _any_ Debian version _and_ got a passed
through NIC
>>   working in the DomU?
>> 
> 
> Yeah just yesterday someone was doing it.. and writing to ##xen on irc.
> 
> What domU kernel are you using? Does it have xen-pcifront? 
> What does "lspci" show in the domU?
> 
> What pci related do you have in the domU dmesg? 
> 
> -- Pasi
> 
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

From: Pasi Kärkkäinen <pasik@iki.fi>
> What domU kernel are you using? Does it have xen-pcifront? 
I first used not a own domU kernel (dom0 Kernel: 2.6.32-5-xen-amd64). This did 
not wirk, the netowrk came up and got down immediately:
[  260.736409] e1000: eth1 NIC Link is Up 100 Mbps Full Duplex, Flow Control: 
RX/TX
DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 5
[  261.552116] e1000: eth1 NIC Link is Down
[  264.768408] e1000: eth1 NIC Link is Up 100 Mbps Full Duplex, Flow Control: 
RX/TX
[  265.580116] e1000: eth1 NIC Link is Down
DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 8
[  267.200418] e1000: eth1 NIC Link is Up 100 Mbps Full Duplex, Flow Control: 
RX/TX
[  268.012111] e1000: eth1 NIC Link is Down
[  269.632409] e1000: eth1 NIC Link is Up 100 Mbps Full Duplex, Flow Control: 
RX/TX
[  270.444115] e1000: eth1 NIC Link is Down

I then followd the instructions on http://wiki.debian.org/PyGrub and used the 
2.6.18 kernel, but this did not change anything.
> What does "lspci" show in the domU?
domU:~# lspci
00:00.0 Ethernet controller: Intel Corporation 82541PI Gigabit Ethernet 
Controller (rev 05)
> What pci related do you have in the domU dmesg? 
domU:~# dmesg | grep -i pci
[    0.000000] Allocating PCI resources starting at 8000000 (gap: 
8000000:f8000000)
[    0.013875] PCI: setting up Xen PCI frontend stub
[    0.185563] pcifront pci-0: Installing PCI frontend
[    0.185826] pcifront pci-0: Creating PCI Frontend Bus 0000:00
[    0.189811] pci 0000:00:00.0: reg 10 32bit mmio: [0xfeac0000-0xfeadffff]
[    0.189811] pci 0000:00:00.0: reg 14 32bit mmio: [0xfeaa0000-0xfeabffff]
[    0.189811] pci 0000:00:00.0: reg 18 io port: [0xb400-0xb43f]
[    0.189811] pci 0000:00:00.0: reg 30 32bit mmio pref: [0xfea80000-0xfea9ffff]
[    0.189811] pcifront pci-0: claiming resource 0000:00:00.0/0
[    0.189811] pcifront pci-0: claiming resource 0000:00:00.0/1
[    0.189811] pcifront pci-0: claiming resource 0000:00:00.0/2
[    0.189811] pcifront pci-0: claiming resource 0000:00:00.0/6
[    0.234504] sysfs: cannot create duplicate filename 
''/devices/pci-0/pci0000:00/0000:00:00.0/config''
[    0.236132]  [<ffffffff811a5303>] ?
pci_create_sysfs_dev_files+0x46/0x356
[    0.236132]  [<ffffffff8119e702>] ? pci_bus_add_device+0x32/0x39
[    0.236132]  [<ffffffff8119e733>] ? pci_bus_add_devices+0x2a/0x11e
[    0.236132]  [<ffffffff812fbdc1>] ? pcifront_scan_root+0x19f/0x1c4
[    0.236132]  [<ffffffff812f8e84>] ?
pcifront_backend_changed+0x176/0x4e3
[    0.732604] e1000 0000:00:00.0: Xen PCI enabling IRQ: 17
[    0.998732] e1000: 0000:00:00.0: e1000_probe: (PCI:33MHz:32-bit) 
00:0e:0c:b9:9b:4a




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

From: Mark Adams <mark@campbell-lange.net>
> In your xm dmesg does it show that the device was successfully hidden?
xm dmesg does not say anything about the device. 
> What do you get from xm list-pci-assignable-devices? (sorry that may not be
>100% accurate command it''s something like that)
"xm pci-list-assignable-devices" does not say anything, either, but
"xm
pci-list"works:

domU:/# xm pci-list domU
domain bus  slot func
0x0000 0x00 0x09 0x0

domU:/# xm pci-list-assignable-devices
domU:/#



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

On Wed, Sep 08, 2010 at 08:11:50AM +0000, Meister Schieber
wrote:
> From: Mark Adams <mark@campbell-lange.net>
> 
> > In your xm dmesg does it show that the device was successfully hidden?
> 
> xm dmesg does not say anything about the device. 
> 
> > What do you get from xm list-pci-assignable-devices? (sorry that may
not be
> >100% accurate command it''s something like that)
> 
> "xm pci-list-assignable-devices" does not say anything, either,
but "xm
> pci-list"works:
> 
> domU:/# xm pci-list domU
> domain bus  slot func
> 0x0000 0x00 0x09 0x0
> 
> domU:/# xm pci-list-assignable-devices
> domU:/#
Yes, Won''t show here if your domU is running and has it assigned. It
looks like it''s passing through as per your mail to Pasi... 1 last
thing, the only change I needed to grub to get it to work for me (on
stock squeeze install) was the following at the end of the module
/vmlinuz.. line xen-pciback.hide=(03:00.0)


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

From: Mark Adams <mark@campbell-lange.net>
> 1 last
>thing, the only change I needed to grub to get it to work for me (on
>stock squeeze install) was the following at the end of the module
>/vmlinuz.. line xen-pciback.hide=(03:00.0)
I did the same.

/boot/grub/grub.cfg (dom0):
module  /vmlinuz-2.6.32-5-xen-amd64 (...) xen-pciback.hide=(09:00.0)

/boot/grub/menu.lst (domU):
kernel          /boot/vmlinuz-2.6.26-2-xen-amd64 (...) swiotlb=force

/etc/xen/domu.cfg:
pci         = [ ''09:00.0'' ]

I changed the nic, I changed the pci-slot, I tried with and without a own 
domU-Kernel...



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

On Wed, Sep 08, 2010 at 10:08:55AM +0000, Meister Schieber
wrote:
> From: Mark Adams <mark@campbell-lange.net>
> 
> > 1 last
> >thing, the only change I needed to grub to get it to work for me (on
> >stock squeeze install) was the following at the end of the module
> >/vmlinuz.. line xen-pciback.hide=(03:00.0)
> 
> I did the same.
> 
> /boot/grub/grub.cfg (dom0):
> module  /vmlinuz-2.6.32-5-xen-amd64 (...) xen-pciback.hide=(09:00.0)
> 
> /boot/grub/menu.lst (domU):
> kernel          /boot/vmlinuz-2.6.26-2-xen-amd64 (...) swiotlb=force
I didn''t need to change the domU config, mine is working as PV running
Lenny. Are you sure whatever kernel you are using has support for the
NIC you are passing through?

> 
> /etc/xen/domu.cfg:
> pci         = [ ''09:00.0'' ]
> 
> I changed the nic, I changed the pci-slot, I tried with and without a own 
> domU-Kernel...
> 
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

On Wed, Sep 08, 2010 at 08:03:46AM +0000, Meister Schieber
wrote:
>    From: Pasi Kärkkäinen <pasik@iki.fi>
>    > What domU kernel are you using? Does it have xen-pcifront?
> 
>    I first used not a own domU kernel (dom0 Kernel: 2.6.32-5-xen-amd64).
This
>    did not wirk, the netowrk came up and got down immediately:
>    [  260.736409] e1000: eth1 NIC Link is Up 100 Mbps Full Duplex, Flow
>    Control: RX/TX
>    DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 5
>    [  261.552116] e1000: eth1 NIC Link is Down
>    [  264.768408] e1000: eth1 NIC Link is Up 100 Mbps Full Duplex, Flow
>    Control: RX/TX
>    [  265.580116] e1000: eth1 NIC Link is Down
>    DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 8
>    [  267.200418] e1000: eth1 NIC Link is Up 100 Mbps Full Duplex, Flow
>    Control: RX/TX
>    [  268.012111] e1000: eth1 NIC Link is Down
>    [  269.632409] e1000: eth1 NIC Link is Up 100 Mbps Full Duplex, Flow
>    Control: RX/TX
>    [  270.444115] e1000: eth1 NIC Link is Down
> 
>    I then followd the instructions on [1]http://wiki.debian.org/PyGrub and
>    used the 2.6.18 kernel, but this did not change anything.
>
How much memory does your domU have? If more than 3 GB, try with 2GB or less.


 
>    > What does "lspci" show in the domU?
> 
>    domU:~# lspci
>    00:00.0 Ethernet controller: Intel Corporation 82541PI Gigabit Ethernet
>    Controller (rev 05)
> 
>    > What pci related do you have in the domU dmesg?
>    domU:~# dmesg | grep -i pci
>    [    0.000000] Allocating PCI resources starting at 8000000 (gap:
>    8000000:f8000000)
>    [    0.013875] PCI: setting up Xen PCI frontend stub
>    [    0.185563] pcifront pci-0: Installing PCI frontend
>    [    0.185826] pcifront pci-0: Creating PCI Frontend Bus 0000:00
>    [    0.189811] pci 0000:00:00.0: reg 10 32bit mmio:
>    [0xfeac0000-0xfeadffff]
>    [    0.189811] pci 0000:00:00.0: reg 14 32bit mmio:
>    [0xfeaa0000-0xfeabffff]
>    [    0.189811] pci 0000:00:00.0: reg 18 io port: [0xb400-0xb43f]
>    [    0.189811] pci 0000:00:00.0: reg 30 32bit mmio pref:
>    [0xfea80000-0xfea9ffff]
>    [    0.189811] pcifront pci-0: claiming resource 0000:00:00.0/0
>    [    0.189811] pcifront pci-0: claiming resource 0000:00:00.0/1
>    [    0.189811] pcifront pci-0: claiming resource 0000:00:00.0/2
>    [    0.189811] pcifront pci-0: claiming resource 0000:00:00.0/6
>    [    0.234504] sysfs: cannot create duplicate filename
>    ''/devices/pci-0/pci0000:00/0000:00:00.0/config''
>    [    0.236132]  [<ffffffff811a5303>] ?
>    pci_create_sysfs_dev_files+0x46/0x356
>    [    0.236132]  [<ffffffff8119e702>] ?
pci_bus_add_device+0x32/0x39
>    [    0.236132]  [<ffffffff8119e733>] ?
pci_bus_add_devices+0x2a/0x11e
>    [    0.236132]  [<ffffffff812fbdc1>] ?
pcifront_scan_root+0x19f/0x1c4
>    [    0.236132]  [<ffffffff812f8e84>] ?
>    pcifront_backend_changed+0x176/0x4e3
>    [    0.732604] e1000 0000:00:00.0: Xen PCI enabling IRQ: 17
>    [    0.998732] e1000: 0000:00:00.0: e1000_probe: (PCI:33MHz:32-bit)
>    00:0e:0c:b9:9b:4a
> 
What''s the mode you''re using for xen pci backend driver in
dom0 kernel?

-- Pasi


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

From: Pasi Kärkkäinen <pasik@iki.fi>
>How much memory does your domU have? If more than 3 GB, try with 2GB or
less.
Dom0 has 2 GB total, domU has 128 MB reserved and "ballooning" is
activated.
> What''s the mode you''re using for xen pci backend driver
in dom0 kernel?
To be honest, I do not really understand your question. I just installed and 
used the kernel which comes with the xen-system  (2.6.32-5). I was told it 
supports pcihide out of the box. I just added the line 
xen-pciback.hide=(09:00.0) to the grub-config.




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

From: Mark Adams <mark@campbell-lange.net>

>I didn''t need to change the domU config, mine is working as PV
running
>Lenny. Are you sure whatever kernel you are using has support for the
>NIC you are passing through?
Well, I am not sure about anything anymore, but at least the right module is 
loaded in domu, so I take it that the kernel supports the NIC:

domU:~# lspci
00:00.0 Ethernet controller: Intel Corporation 82541PI Gigabit Ethernet 
Controller (rev 05)

domU:~# lsmod | grep e1000
e1000                 117312  0

domU:~# uname -r
2.6.26-2-xen-amd64



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

On Wed, Sep 08, 2010 at 11:34:33AM +0000, Meister Schieber
wrote:
>    From: Pasi Kärkkäinen <pasik@iki.fi>
>    >How much memory does your domU have? If more than 3 GB, try with 2GB
or
>    less.
> 
>    Dom0 has 2 GB total, domU has 128 MB reserved and "ballooning"
is
>    activated.
> 
>    > What''s the mode you''re using for xen pci backend
driver in dom0 kernel?
> 
>    To be honest, I do not really understand your question. I just installed
>    and used the kernel which comes with the xen-system  (2.6.32-5). I was
>    told it supports pcihide out of the box. I just added the line
>    xen-pciback.hide=(09:00.0) to the grub-config.
>
That mode is set compile-time. Try grepping from /boot/config-kernelversion.

grep CONFIG_XEN_PCIDEV_BACKEND configfile

Also did you try with a self-compiled dom0 kernel?:
http://wiki.xensource.com/xenwiki/XenParavirtOps
http://wiki.xensource.com/xenwiki/XenPCIpassthrough

-- Pasi


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

From: Pasi Kärkkäinen <pasik@iki.fi>
> That mode is set compile-time. Try grepping from
/boot/config-kernelversion.
> grep CONFIG_XEN_PCIDEV_BACKEND configfile
Seems to be set:

root@domU:~# grep CONFIG_XEN_PCIDEV_BACKEND /boot/config-2.6.32-5-xen-amd64
CONFIG_XEN_PCIDEV_BACKEND=y
CONFIG_XEN_PCIDEV_BACKEND_VPCI=y
# CONFIG_XEN_PCIDEV_BACKEND_PASS is not set
# CONFIG_XEN_PCIDEV_BACKEND_SLOT is not set
# CONFIG_XEN_PCIDEV_BACKEND_CONTROLLER is not set

>Also did you try with a self-compiled dom0 kernel?:
>http://wiki.xensource.com/xenwiki/XenParavirtOps
>http://wiki.xensource.com/xenwiki/XenPCIpassthrough
Not yet, as I am not too firm with kernel compiling and the "official xen
wiki"
states that kernel 2.6.32-5-xen-amd64 contains the PCI -BACKEND DRIVER:

"Here''s a list of the kernels that have the Xen pcifront driver
included.
(...)
Debian squeeze 2.6.32-xen. "




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

On Thu, Sep 09, 2010 at 11:08:52AM +0000, Meister Schieber
wrote:
>    From: Pasi Kärkkäinen <pasik@iki.fi>
>    > That mode is set compile-time. Try grepping from
>    /boot/config-kernelversion.
>    > grep CONFIG_XEN_PCIDEV_BACKEND configfile
> 
>    Seems to be set:
> 
>    root@domU:~# grep CONFIG_XEN_PCIDEV_BACKEND
>    /boot/config-2.6.32-5-xen-amd64
>    CONFIG_XEN_PCIDEV_BACKEND=y
>    CONFIG_XEN_PCIDEV_BACKEND_VPCI=y
>    # CONFIG_XEN_PCIDEV_BACKEND_PASS is not set
>    # CONFIG_XEN_PCIDEV_BACKEND_SLOT is not set
>    # CONFIG_XEN_PCIDEV_BACKEND_CONTROLLER is not set
> 
Ok, so BACKEND_VPCI means devices in the domU will have different PCI ID than in
dom0
BACKEND_PASS means they''ll have the same PCI ID in the domU as in dom0.
>    >Also did you try with a self-compiled dom0 kernel?:
>    [1]>http://wiki.xensource.com/xenwiki/XenParavirtOps
>    [2]>http://wiki.xensource.com/xenwiki/XenPCIpassthrough
> 
>    Not yet, as I am not too firm with kernel compiling and the
"official xen
>    wiki" states that kernel 2.6.32-5-xen-amd64 contains the PCI
-BACKEND
>    DRIVER:
> 
>    "Here''s a list of the kernels that have the Xen pcifront
driver included.
>    (...)
>    Debian squeeze 2.6.32-xen. "
> 
Yeah, so it should work.

Did you get the device hiding working in dom0? That''s the first
required step.

-- Pasi


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

From: Pasi Kärkkäinen <pasik@iki.fi>
> Did you get the device hiding working in dom0? That''s the first
required step.
Yes, i detached the nic from the domU, restarted dom0 and the network comes up 
immediately. 


I will try now with a customized kernel




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

On Fri, Sep 10, 2010 at 09:42:02AM +0000, Meister Schieber
wrote:
>    From: Pasi Kärkkäinen <pasik@iki.fi>
>    > Did you get the device hiding working in dom0? That''s the
first required
>    step.
> 
>    Yes, i detached the nic from the domU, restarted dom0 and the network
>    comes up immediately.
> 
>    I will try now with a customized kernel
>
Ok, so "xm pci-list-assignable-devices" shows the device properly
before assigning it.

Please try with the latest kernel from xen.git xen/stable-2.6.32.x branch
(2.6.32.21).
http://wiki.xensource.com/xenwiki/XenParavirtOps

-- Pasi


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