Xen users - Jul 2006 - AFS support in Xen

Dear all,

Does Xen-3.0 have support for AFS?
If yes, is it enabled by default, or do I
have to configure the source with some option
and then compile it?

Thank you in advance,
Arsen.

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

On Mon, Jul 31, 2006 at 11:48:32AM +0200, Arsen Hayrapetyan
wrote:
> Dear all,
> 
> Does Xen-3.0 have support for AFS?
I suppose, you mean "Andrew File System"...

It doesn''t need to have. You''ll have to compile your libafs
(the afs module)
sources against the dom(u|0)-kernel - everything else should work out of the
box.

I''ve got some xen-3.0.2 machines here. All DomUs are afs-clients, half
of them are AFS-servers, too. Dom0s can be AFS-clients, too but I don''t
like the idea of having such a big third-party-kernelmodule in a dom0''s
kernel permanently.

I built kernel and module debian-package for xen-domains. Deb-source is

 deb ftp://instantafs.cbs.mpg.de/instantafs/debian/sarge/ /

package names are:

 linux-xen0-2.6.16.13-f4ee
 openafs-modules-2.6.16.13-f4ee

Regards,

Frank

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

Hello,

I get the following warnings while I am installing
xen-kernel-2.6.16-xen3_86.1_rhel4.1.i686.rpm

=======================================WARNING: 
/lib/modules/2.6.16-xen3_86.1_rhel4.1/kernel/drivers/serial/8250.ko needs 
unknown symbol uart_get_baud_rate
WARNING: 
/lib/modules/2.6.16-xen3_86.1_rhel4.1/kernel/drivers/serial/8250.ko needs 
unknown symbol uart_resume_port
WARNING: 
/lib/modules/2.6.16-xen3_86.1_rhel4.1/kernel/drivers/serial/8250.ko needs 
unknown symbol uart_register_driver
WARNING: 
/lib/modules/2.6.16-xen3_86.1_rhel4.1/kernel/drivers/serial/8250.ko needs 
unknown symbol uart_suspend_port
WARNING: 
/lib/modules/2.6.16-xen3_86.1_rhel4.1/kernel/drivers/serial/8250.ko needs 
unknown symbol uart_remove_one_port
WARNING: 
/lib/modules/2.6.16-xen3_86.1_rhel4.1/kernel/drivers/serial/8250.ko needs 
unknown symbol uart_update_timeout
WARNING: 
/lib/modules/2.6.16-xen3_86.1_rhel4.1/kernel/drivers/serial/8250.ko needs 
unknown symbol uart_unregister_driver
WARNING: 
/lib/modules/2.6.16-xen3_86.1_rhel4.1/kernel/drivers/serial/8250.ko needs 
unknown symbol uart_get_divisor
WARNING: 
/lib/modules/2.6.16-xen3_86.1_rhel4.1/kernel/drivers/serial/8250.ko needs 
unknown symbol uart_match_port
WARNING: 
/lib/modules/2.6.16-xen3_86.1_rhel4.1/kernel/drivers/serial/8250.ko needs 
unknown symbol uart_add_one_port
WARNING: 
/lib/modules/2.6.16-xen3_86.1_rhel4.1/kernel/drivers/serial/8250.ko needs 
unknown symbol uart_write_wakeup
=======================================================
Is it OK?

Arsen.

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

On Mon, 2006-31-07 at 12:58 +0200, Arsen Hayrapetyan
wrote:
> Is it OK?
No: kiss ttyS0 goodbye.  The xen kernel from xensource is compiled with
serial support turned off.  That''s okay if you use different kernels
for
dom0 and domU, but if use the same kernel, it''s bad.  You
won''t
have /dev/ttyS0 in dom0, which is necessary for some things (e.g. serial
UPS).

I suggest you build dom0 and domU kernels. Turn on serial support in
dom0, but leave it off for domU.

BTW, search this list for a thread titled "modem on serial port in
Dom0"
for more information.

Regards,

Ranbir

-- 
Kanwar Ranbir Sandhu
Linux 2.6.17-1.2141_FC4 i686 GNU/Linux 
08:19:48 up 1:49, 2 users, load average: 0.51, 0.60, 0.53 



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

Hello,

I have the RHEL4.1 Linux as dom0 and want to intstall
Fedora 5 Core Linux as domU...
I have created the ext3 filesystem in vm1disk file:

===============================================dd if=/dev/zero  of=vm1disk bs=1k
seek=16384k count=1
mkfs -t ext3 vm1disk
===============================================
Then I created a logical volume:

===============================================mount -o loop vm1disk /mnt
losetup /dev/loop0 vm1disk
pvcreate /dev/loop0
vgcreate vg /dev/loop0
lvcreate -L14G -n compnode vg
lvcreate -L1G -n compswap vg
===============================================
Now I want to install Fedora 5 Core Linux as the guest domain
on that volume. 

Can anyone point me to the documentation of how can I do that?

Thank you in advance,
Arsen.

P.S. If there are clear documentation how to do that with the Linux, other 
than Fedora 5 Core, please, give me a link also


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

> -----Original Message-----
> From: xen-users-bounces@lists.xensource.com 
> [mailto:xen-users-bounces@lists.xensource.com] On Behalf Of 
> Arsen Hayrapetyan
> Sent: 02 August 2006 14:15
> To: xen-users@lists.xensource.com
> Subject: [Xen-users] Installing Fedora 5 as the guest domain...
> 
> Hello,
> 
> I have the RHEL4.1 Linux as dom0 and want to intstall
> Fedora 5 Core Linux as domU...
> I have created the ext3 filesystem in vm1disk file:
> 
> ===============================================> dd if=/dev/zero 
of=vm1disk bs=1k seek=16384k count=1
> mkfs -t ext3 vm1disk
> ===============================================> 
> Then I created a logical volume:
> 
> ===============================================> mount -o loop vm1disk
/mnt
> losetup /dev/loop0 vm1disk
> pvcreate /dev/loop0
> vgcreate vg /dev/loop0
> lvcreate -L14G -n compnode vg
> lvcreate -L1G -n compswap vg
> ===============================================> 
> Now I want to install Fedora 5 Core Linux as the guest domain
> on that volume. 
> 
> Can anyone point me to the documentation of how can I do that?
The easiest way (that I know of) is to use the CDROM/DVD image(s) to
install the OS directly into the device, using a CD-boot as the way to
tell the HVM domain what to do... Of course, this doesn''t work if you
don''t have VT/SVM  - in that case you''re probably best off
creating a
separate partition and if you must have a file-base installation, create
a file by using dd from the partition to the file... 

Here''s a HVM congiguration to boot CDROM I posted earlier:
import os, re
arch = os.uname()[4]
if re.search(''64'', arch):
    arch_libdir = ''lib64''
else:
    arch_libdir = ''lib''
kernel = "/usr/lib/xen/boot/hvmloader"
builder=''hvm''
memory = 1024
name = "CDROM-boot"
vif = [ ''type=ioemu, bridge=xenbr0'' ]
disk = [ ''file:/root/disk.img,ioemu:hda,w'' ]
device_model = ''/usr/'' + arch_libdir +
''/xen/bin/qemu-dm''
cdrom=''/root/isoguest.iso''
boot=''d''
sdl=0
vnc=1
vncviewer=1
serial=''pty''
ne2000=0


--
Mats



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

Petersson, Mats wrote:
>  
> 
>> -----Original Message-----
>> From: xen-users-bounces@lists.xensource.com 
>> [mailto:xen-users-bounces@lists.xensource.com] On Behalf Of 
>> Arsen Hayrapetyan
>> Sent: 02 August 2006 14:15
>> To: xen-users@lists.xensource.com
>> Subject: [Xen-users] Installing Fedora 5 as the guest domain...
>>
>> Hello,
>>
>> I have the RHEL4.1 Linux as dom0 and want to intstall
>> Fedora 5 Core Linux as domU...
>> I have created the ext3 filesystem in vm1disk file:
>>
>> ===============================================>> dd if=/dev/zero
of=vm1disk bs=1k seek=16384k count=1
>> mkfs -t ext3 vm1disk
>> ===============================================>>
>> Then I created a logical volume:
>>
>> ===============================================>> mount -o loop
vm1disk /mnt
>> losetup /dev/loop0 vm1disk
>> pvcreate /dev/loop0
>> vgcreate vg /dev/loop0
>> lvcreate -L14G -n compnode vg
>> lvcreate -L1G -n compswap vg
>> ===============================================>>
>> Now I want to install Fedora 5 Core Linux as the guest domain
>> on that volume. 
>>
>> Can anyone point me to the documentation of how can I do that?
> 
> The easiest way (that I know of) is to use the CDROM/DVD image(s) to
> install the OS directly into the device, using a CD-boot as the way to
> tell the HVM domain what to do... Of course, this doesn''t work if
you
> don''t have VT/SVM  - in that case you''re probably best
off creating a
> separate partition and if you must have a file-base installation, create
> a file by using dd from the partition to the file... 
> 
> Here''s a HVM congiguration to boot CDROM I posted earlier:
> import os, re
> arch = os.uname()[4]
> if re.search(''64'', arch):
>     arch_libdir = ''lib64''
> else:
>     arch_libdir = ''lib''
> kernel = "/usr/lib/xen/boot/hvmloader"
> builder=''hvm''
> memory = 1024
> name = "CDROM-boot"
> vif = [ ''type=ioemu, bridge=xenbr0'' ]
> disk = [ ''file:/root/disk.img,ioemu:hda,w'' ]
> device_model = ''/usr/'' + arch_libdir +
''/xen/bin/qemu-dm''
> cdrom=''/root/isoguest.iso''
> boot=''d''
> sdl=0
> vnc=1
> vncviewer=1
> serial=''pty''
> ne2000=0
> 
An alternative, if you''re not using VT/SVM, is to follow these
instructions:

http://www.fedoraproject.org/wiki/FedoraXenQuickstart

I found it necessary to revise the yum.conf file.


-- 
John R. Shannon, CISSP
Chief Scientist
DSCI, Information Assurance Division
jshannon@dsci-usa.com
john.r.shannon@us.army.mil
shannonjr@NetBSD.org
(208)522-4506

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