Bastian Blank schreef:
> On Fri, Aug 01, 2008 at 11:05:16AM +0200, Paul van der Vlis wrote:
>> A 32-bit Etch dom0 is for me not OK, because it has not PAE so I cannot
>> use my 8 GB RAM in this way.
>
> Please explain? There is no non-PAE Xen kernel in Etch.
I have always heard that the 32-bit Xen in Debian is non-PAE, but maybe
this is wrong... Googling I found this article:
http://www.howtoforge.com/make-your-xen-pae-kernel-work-with-more-than-4gb-ram-debian-etch-grub
>> But... So far I know, a 64-bits Etch dom0 has no support for 32-bits
>> domU's...
>
> No, this is correct.
OK, important information for me. So I have to switch to a 32-bits dom0
to make it work with Lenny.
Are you sure a 64-bits Lenny with Etch kernel does also not support
32-bits domU's?
>> Did you you create this with only Debian packages?
>
> There exists other Debian packages like my new kernel packages with Xen
> 3.1 patch.
I like Debian packages because of the security-support.
What are the advantages of your package over the Debian packages?
With regards,
Paul van der Vlis.
--
http://www.vandervlis.nl/
--
To UNSUBSCRIBE, email to debian-isp-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
08-01-2008, 06:03 PM
Teodor
Xen advice requested
On Fri, Aug 1, 2008 at 3:08 PM, Paul van der Vlis <paul@vandervlis.nl> wrote:
> Bastian Blank schreef:
>> On Fri, Aug 01, 2008 at 11:05:16AM +0200, Paul van der Vlis wrote:
>>> A 32-bit Etch dom0 is for me not OK, because it has not PAE so I cannot
>>> use my 8 GB RAM in this way.
>>
>> Please explain? There is no non-PAE Xen kernel in Etch.
True. This is why the 32-bit dom0 it only works with
xen-hypervisor-3.0.3-1-i386-pae (with xen-hypervisor-3.0.3-1-i386 will
panic at boot) and the package is simply useless.
>>> But... So far I know, a 64-bits Etch dom0 has no support for 32-bits
>>> domU's...
>>
>> No, this is correct.
I think the only reason to mix a 64-bit dom0 with a 32-bit domU is the
lack of a 64-bit domU in lenny. I hope I won't have to do that since I
have the option of using the -openvz flavour (and maybe -vserver but
these images seem to be disabled in 2.6.26).
Thanks
--
To UNSUBSCRIBE, email to debian-isp-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
08-05-2008, 08:20 AM
Thomas Goirand
Xen advice requested
Paul van der Vlis wrote:
> Thomas Goirand schreef:
>> Hi,
>>
>> I DON'T want to hurt anybody here, so please, pkg-xen-devel team, do not
>> take what I'm writing here badly, you guys are doing a very hard work,
>> and I don't think I'd be able to manage it as good as you did.
>>
>> However, I really think that the Xen kernels from Debian are not so
>> usable in production
>
> Can you tell us more about the problems you have seen?
>
> With regards,
> Paul van der Vlis.
First problem: Etch packaged version 3.0.3. To me it's a pretty bad
choice, this version (in my experience) is not stable and causes problems.
Second thing (maybe the most important): the bindings of python for the
Xen API are not properly setup, it's set with a version number. If I'm
remembering well, its all about /usr/lib/python/xen that is under the
packaged version of Xen called something like
/usr/lib/python/xen-VERSION, with no symlink provided for that folder.
Then anything that wants to includes it FAILS to do so, and there is no
predictable way of knowing how to fix when you are a package using the
bindings. I give you a simple example in python, that intend to find the
name of the virtual interface the VPS is using, and that we are using in
our code:
sys.path.append( '/usr/lib/python' )
import xen.xm.main as xenxm
id = int(xenxm.sxp.child_value(info, 'id', '-1'))
networkDeviceName="vif%s" % id
As /usr/lib/python/xen doesn't exist, but instead there is a
/usr/lib/python/xen-VERSION, the import fails if using the Debian package...
Thomas
--
To UNSUBSCRIBE, email to debian-isp-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
08-05-2008, 08:38 AM
Paul van der Vlis
Xen advice requested
Thomas Goirand schreef:
> Paul van der Vlis wrote:
>> Thomas Goirand schreef:
>>> Hi,
>>>
>>> I DON'T want to hurt anybody here, so please, pkg-xen-devel team, do not
>>> take what I'm writing here badly, you guys are doing a very hard work,
>>> and I don't think I'd be able to manage it as good as you did.
>>>
>>> However, I really think that the Xen kernels from Debian are not so
>>> usable in production
>> Can you tell us more about the problems you have seen?
>>
>> With regards,
>> Paul van der Vlis.
>
> First problem: Etch packaged version 3.0.3. To me it's a pretty bad
> choice, this version (in my experience) is not stable and causes problems.
I have a 3.0.3 64-bit test-setup for a few month with not much load and
a filesystem on LVM. I did not see any problems.
> Second thing (maybe the most important): the bindings of python for the
> Xen API are not properly setup, it's set with a version number. If I'm
> remembering well, its all about /usr/lib/python/xen that is under the
> packaged version of Xen called something like
> /usr/lib/python/xen-VERSION, with no symlink provided for that folder.
>
> Then anything that wants to includes it FAILS to do so, and there is no
> predictable way of knowing how to fix when you are a package using the
> bindings. I give you a simple example in python, that intend to find the
> name of the virtual interface the VPS is using, and that we are using in
> our code:
>
> sys.path.append( '/usr/lib/python' )
> import xen.xm.main as xenxm
> id = int(xenxm.sxp.child_value(info, 'id', '-1'))
> networkDeviceName="vif%s" % id
>
> As /usr/lib/python/xen doesn't exist, but instead there is a
> /usr/lib/python/xen-VERSION, the import fails if using the Debian package...
For me it worked out of the box. Maybe the problems were corrected
later? I use tools like xen-create-image and xm without problems.
BTW: I had problems with the 64bit xen-vserver kernel package, but not
with the xen-only kernel package.
With regards,
Paul van der Vlis.
--
http://www.vandervlis.nl/
--
To UNSUBSCRIBE, email to debian-isp-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
08-05-2008, 04:28 PM
Thomas Goirand
Xen advice requested
Paul van der Vlis wrote:
>> sys.path.append( '/usr/lib/python' )
>> import xen.xm.main as xenxm
>> id = int(xenxm.sxp.child_value(info, 'id', '-1'))
>> networkDeviceName="vif%s" % id
>>
>> As /usr/lib/python/xen doesn't exist, but instead there is a
>> /usr/lib/python/xen-VERSION, the import fails if using the Debian package...
>
> For me it worked out of the box. Maybe the problems were corrected
> later? I use tools like xen-create-image and xm without problems.
Can you do "ls -lah /usr/lib/python" in your setup, and show me the
result? Talking about the fact that "xm" and "xen-create-image" are
working is irrelevance in this case.
Thomas
--
To UNSUBSCRIBE, email to debian-isp-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
08-05-2008, 05:04 PM
Paul van der Vlis
Xen advice requested
Thomas Goirand schreef:
> Paul van der Vlis wrote:
>>> sys.path.append( '/usr/lib/python' )
>>> import xen.xm.main as xenxm
>>> id = int(xenxm.sxp.child_value(info, 'id', '-1'))
>>> networkDeviceName="vif%s" % id
>>>
>>> As /usr/lib/python/xen doesn't exist, but instead there is a
>>> /usr/lib/python/xen-VERSION, the import fails if using the Debian package...
>> For me it worked out of the box. Maybe the problems were corrected
>> later? I use tools like xen-create-image and xm without problems.
>
> Can you do "ls -lah /usr/lib/python" in your setup, and show me the
> result?
--
To UNSUBSCRIBE, email to debian-isp-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
08-06-2008, 03:40 AM
Thomas Goirand
Xen advice requested
Paul van der Vlis wrote:
> Thomas Goirand schreef:
>> Paul van der Vlis wrote:
>>>> sys.path.append( '/usr/lib/python' )
>>>> import xen.xm.main as xenxm
>>>> id = int(xenxm.sxp.child_value(info, 'id', '-1'))
>>>> networkDeviceName="vif%s" % id
>>>>
>>>> As /usr/lib/python/xen doesn't exist, but instead there is a
>>>> /usr/lib/python/xen-VERSION, the import fails if using the Debian package...
>>> For me it worked out of the box. Maybe the problems were corrected
>>> later? I use tools like xen-create-image and xm without problems.
>> Can you do "ls -lah /usr/lib/python" in your setup, and show me the
>> result?
>
> xen:~# ls -lah /usr/lib/python
> ls: /usr/lib/python: No such file or directory
> xen:~# ls -ld /usr/lib/python*
> drwxr-xr-x 3 root root 80 2008-03-29 18:42 /usr/lib/python2.3
> drwxr-xr-x 19 root root 12072 2008-04-29 17:05 /usr/lib/python2.4
> drwxr-xr-x 3 root root 80 2008-03-29 18:47 /usr/lib/python2.5
> drwxr-xr-x 5 root root 136 2008-03-29 18:47 /usr/lib/python-support
> xen:~# ls -lah /usr/lib/python2.4
> [...]
Hi,
That's exactly what I said, I didn't remember in details, by hart... I
love Debian, and the fact that it sets things where they should be (conf
files in /etc, etc.), but in that case, it just messes everything. How
can I then include things that are supposed to be in /usr/lib/python/xen
in a "normal" system? What's the Debian way, or the pkg-xen-devel way?
Where's located the "xm" python source code in the Debian package?
Thomas
--
To UNSUBSCRIBE, email to debian-isp-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
08-06-2008, 08:58 AM
Paul van der Vlis
Xen advice requested
Thomas Goirand schreef:
> Paul van der Vlis wrote:
>> Thomas Goirand schreef:
>>> Paul van der Vlis wrote:
>>>>> sys.path.append( '/usr/lib/python' )
>>>>> import xen.xm.main as xenxm
>>>>> id = int(xenxm.sxp.child_value(info, 'id', '-1'))
>>>>> networkDeviceName="vif%s" % id
>>>>>
>>>>> As /usr/lib/python/xen doesn't exist, but instead there is a
>>>>> /usr/lib/python/xen-VERSION, the import fails if using the Debian package...
>>>> For me it worked out of the box. Maybe the problems were corrected
>>>> later? I use tools like xen-create-image and xm without problems.
>>> Can you do "ls -lah /usr/lib/python" in your setup, and show me the
>>> result?
>> xen:~# ls -lah /usr/lib/python
>> ls: /usr/lib/python: No such file or directory
>> xen:~# ls -ld /usr/lib/python*
>> drwxr-xr-x 3 root root 80 2008-03-29 18:42 /usr/lib/python2.3
>> drwxr-xr-x 19 root root 12072 2008-04-29 17:05 /usr/lib/python2.4
>> drwxr-xr-x 3 root root 80 2008-03-29 18:47 /usr/lib/python2.5
>> drwxr-xr-x 5 root root 136 2008-03-29 18:47 /usr/lib/python-support
>> xen:~# ls -lah /usr/lib/python2.4
>> [...]
>
> Hi,
>
> That's exactly what I said, I didn't remember in details, by hart... I
> love Debian, and the fact that it sets things where they should be (conf
> files in /etc, etc.), but in that case, it just messes everything. How
> can I then include things that are supposed to be in /usr/lib/python/xen
> in a "normal" system?
I don't know. Take a look at the filelist:
http://packages.debian.org/etch/i386/xen-utils-3.0.3-1/filelist
> What's the Debian way, or the pkg-xen-devel way?
> Where's located the "xm" python source code in the Debian package?