Hi,
i created a domU MAchine (debian Sarge)on an lvm patition under Xen3 with
actual kernel 2.6.12. This worked verry well and fast. I decided to move
this domU to an other machine running Xen 2.0.7. After copying the lvm on
this machine and creating the config file I booted this domU up with Kernle
2.6.11.12 which seems to be the most actual kernel fpr xen2.0.7 in a domU.
My Problem ist that the domU is verrrrry slow it need more than 4 Minutes to
boot into a debian base system. And starting an application is quiete
impossible with this week performance.
To be shure that xen dom0 works fine I created a new domU on this machine
with an lvm drive an a debian base system. This works verry well an fast...
Has someone any idea what causes this problem? Or how I can fix it?
Here are my logfiles:
Greetings Armin
xen-server:~# xm dmesg
ERROR: cannot use unconfigured serial port COM1
__ __ ____ ___ _____
\ \/ /___ _ __ |___ \ / _ \|___ |
\ // _ \ ''_ \ __) || | | | / /
/ \ __/ | | | / __/ | |_| | / /
/_/\_\___|_| |_| |_____(_)___(_)_/
http://www.cl.cam.ac.uk/netos/xen
University of Cambridge Computer Laboratory
Xen version 2.0.7 (root@localdomain) (gcc-Version 3.3.5 (Debian
1:3.3.5-13)) Mo Apr 10 18:14:49 CEST 2006
Latest ChangeSet:
(XEN) Physical RAM map:
(XEN) 0000000000000000 - 000000000009fc00 (usable)
(XEN) 000000000009fc00 - 00000000000a0000 (reserved)
(XEN) 00000000000e0000 - 0000000000100000 (reserved)
(XEN) 0000000000100000 - 000000007fff0000 (usable)
(XEN) 000000007fff0000 - 000000007ffff000 (ACPI data)
(XEN) 000000007ffff000 - 0000000080000000 (ACPI NVS)
(XEN) 00000000ffb80000 - 0000000100000000 (reserved)
(XEN) System RAM: 2047MB (2096700kB)
(XEN) Xen heap: 10MB (10732kB)
(XEN) CPU0: Before vendor init, caps: bfebfbff 00000000 00000000, vendor = 0
(XEN) CPU#0: Physical ID: 0, Logical ID: 0
(XEN) CPU caps: bfebfbff 00000000 00000000 00000000
(XEN) found SMP MP-table at 000ff780
(XEN) ACPI: RSDP (v002 ACPIAM ) @
0x000f6fb0
(XEN) ACPI: XSDT (v001 A M I OEMXSDT 0x04000429 MSFT 0x00000097) @
0x7fff0100
(XEN) ACPI: FADT (v003 A M I OEMFACP 0x04000429 MSFT 0x00000097) @
0x7fff0200
(XEN) ACPI: MADT (v001 A M I OEMAPIC 0x04000429 MSFT 0x00000097) @
0x7fff0300
(XEN) ACPI: OEMB (v001 A M I OEMBIOS 0x04000429 MSFT 0x00000097) @
0x7ffff040
(XEN) ACPI: DSDT (v001 PSCHL PSCHL017 0x00000017 INTL 0x02002026) @
0x00000000
(XEN) ACPI: Local APIC address 0xfee00000
(XEN) ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled)
(XEN) Processor #0 Unknown CPU [15:3] APIC version 20
(XEN) ACPI: LAPIC (acpi_id[0x02] lapic_id[0x01] enabled)
(XEN) Processor #1 Unknown CPU [15:3] APIC version 20
(XEN) ACPI: LAPIC_NMI (acpi_id[0x01] dfl dfl lint[0x1])
(XEN) Using ACPI for processor (LAPIC) configuration information
(XEN) Intel MultiProcessor Specification v1.4
(XEN) Virtual Wire compatibility mode.
(XEN) OEM ID: TEMPLATE Product ID: PSCH-L APIC at: 0xFEE00000
(XEN) I/O APIC #2 Version 32 at 0xFEC00000.
(XEN) I/O APIC #3 Version 32 at 0xFEC10000.
(XEN) Enabling APIC mode: Flat. Using 2 I/O APICs
(XEN) Processors: 2
(XEN) Using scheduler: Borrowed Virtual Time (bvt)
(XEN) Initializing CPU#0
(XEN) Detected 2992.627 MHz processor.
(XEN) CPU0: Before vendor init, caps: bfebfbff 00000000 00000000, vendor = 0
(XEN) CPU#0: Physical ID: 0, Logical ID: 0
(XEN) CPU caps: bfebfbff 00000000 00000000 00000000
(XEN) CPU0 booted
(XEN) enabled ExtINT on CPU#0
(XEN) ESR value before enabling vector: 00000000
(XEN) ESR value after enabling vector: 00000000
(XEN) Booting processor 1/1 eip 90000
(XEN) Initializing CPU#1
(XEN) masked ExtINT on CPU#1
(XEN) ESR value before enabling vector: 00000000
(XEN) ESR value after enabling vector: 00000000
(XEN) CPU1: Before vendor init, caps: bfebfbff 00000000 00000000, vendor = 0
(XEN) CPU#1: Physical ID: 0, Logical ID: 1
(XEN) CPU caps: bfebfbff 00000000 00000000 00000000
(XEN) CPU1 has booted.
(XEN) Total of 2 processors activated.
(XEN) ENABLING IO-APIC IRQs
(XEN) Setting 2 in the phys_id_present_map
(XEN) ...changing IO-APIC physical APIC ID to 2 ... ok.
(XEN) Setting 3 in the phys_id_present_map
(XEN) ...changing IO-APIC physical APIC ID to 3 ... ok.
(XEN) init IO_APIC IRQs
(XEN) ..TIMER: vector=0x41 pin1=2 pin2=0
(XEN) Using local APIC timer interrupts.
(XEN) Calibrating APIC timer for CPU0...
(XEN) ..... CPU speed is 2992.5230 MHz.
(XEN) ..... Bus speed is 199.5014 MHz.
(XEN) ..... bus_scale = 0x0000CC4F
(XEN) checking TSC synchronization across CPUs: passed.
(XEN) Time init:
(XEN) .... System Time: 20001009ns
(XEN) .... cpu_freq: 00000000:B25FDF2C
(XEN) .... scale: 00000001:562C9A1B
(XEN) .... Wall Clock: 1144690464s 130000us
(XEN) PCI: PCI BIOS revision 2.10 entry at 0xf0031, last bus=4
(XEN) PCI: Using configuration type 1
(XEN) PCI: Probing PCI hardware
(XEN) PCI: Probing PCI hardware (bus 00)
(XEN) PCI: Ignoring BAR0-3 of IDE controller 00:1f.1
(XEN) Transparent bridge - PCI device 8086:244e
(XEN) PCI: Using IRQ router default [8086/25a1] at 00:1f.0
(XEN) PCI->APIC IRQ transform: (B0,I29,P0) -> 16
(XEN) PCI->APIC IRQ transform: (B0,I29,P1) -> 19
(XEN) PCI->APIC IRQ transform: (B0,I29,P3) -> 23
(XEN) PCI->APIC IRQ transform: (B0,I31,P0) -> 18
(XEN) PCI->APIC IRQ transform: (B0,I31,P1) -> 17
(XEN) PCI->APIC IRQ transform: (B1,I1,P0) -> 18
(XEN) PCI->APIC IRQ transform: (B2,I3,P0) -> 25
(XEN) PCI->APIC IRQ transform: (B2,I5,P0) -> 27
(XEN) PCI->APIC IRQ transform: (B3,I4,P0) -> 24
(XEN) PCI->APIC IRQ transform: (B3,I4,P1) -> 25
(XEN) PCI->APIC IRQ transform: (B3,I6,P0) -> 26
(XEN) PCI->APIC IRQ transform: (B3,I6,P1) -> 27
(XEN) PCI->APIC IRQ transform: (B4,I4,P0) -> 20
(XEN) mtrr: v2.0 (20020519)
(XEN) *** LOADING DOMAIN 0 ***
(XEN) Xen-ELF header found:
''GUEST_OS=linux,GUEST_VER=2.6,XEN_VER=2.0,VIRT_BASE=0xC0000000,LOADER=generi
c,PT_MODE_WRITABLE''
(XEN) PHYSICAL MEMORY ARRANGEMENT:
(XEN) Kernel image: 00c00000->0104a87c
(XEN) Initrd image: 00000000->00000000
(XEN) Dom0 alloc.: 01400000->11400000
(XEN) VIRTUAL MEMORY ARRANGEMENT:
(XEN) Loaded kernel: c0100000->c057ffc4
(XEN) Init. ramdisk: c0580000->c0580000
(XEN) Phys-Mach map: c0580000->c05c0000
(XEN) Page tables: c05c0000->c05c3000
(XEN) Start info: c05c3000->c05c4000
(XEN) Boot stack: c05c4000->c05c5000
(XEN) TOTAL: c0000000->c0800000
(XEN) ENTRY ADDRESS: c0100000
(XEN) Scrubbing DOM0 RAM: ...done.
(XEN) Scrubbing Free RAM: .....................done.
(XEN) *** Serial input -> DOM0 (type ''CTRL-a'' three times
to switch input to
Xen).
xen-server:/srv/xen# cat bootlog radius1
Linux version 2.6.11.12-xenU (root@xen-server) (gcc-Version 3.3.5 (Debian
1:3.3.
5-13)) #1 Mon Apr 10 17:40:41 CEST 2006
BIOS-provided physical RAM map:
Xen: 0000000000000000 - 0000000019000000 (usable)
400MB LOWMEM available.
DMI not present.
IRQ lockup detection disabled
Allocating PCI resources starting at 19000000 (gap: 19000000:e7000000)
Built 1 zonelists
Kernel command line: root=/dev/sda ro 4
Initializing CPU#0
PID hash table entries: 2048 (order: 11, 32768 bytes)
Xen reported: 2992.627 MHz processor.
Using tsc for high-res timesource
Dentry cache hash table entries: 65536 (order: 6, 262144 bytes)
Inode-cache hash table entries: 32768 (order: 5, 131072 bytes)
vmalloc area: d9800000-fbff9000, maxmem 34000000
Memory: 402560k/409600k available (1631k kernel code, 6756k reserved, 439k
data,
112k init, 0k highmem)
Checking if this processor honours the WP bit even in supervisor mode... Ok.
Mount-cache hash table entries: 512 (order: 0, 4096 bytes)
CPU: Trace cache: 12K uops, L1 D cache: 16K
CPU: L2 cache: 1024K
CPU: Intel(R) Pentium(R) 4 CPU 3.00GHz stepping 04
Enabling fast FPU save and restore... done.
Enabling unmasked SIMD FPU exception support... done.
Checking ''hlt'' instruction... disabled
NET: Registered protocol family 16
xen_mem: Initialising balloon driver.
Initializing Cryptographic API
io scheduler noop registered
io scheduler anticipatory registered
io scheduler deadline registered
io scheduler cfq registered
RAMDISK driver initialized: 16 RAM disks of 4096K size 1024 blocksize
Xen virtual console successfully installed as tty
Event-channel device installed.
xen_blk: Initialising virtual block device driver
sda:<6>xen_net: Initialising virtual ethernet driver.
unknown partition table
NET: Registered protocol family 2
IP: routing cache hash table of 4096 buckets, 32Kbytes
TCP established hash table entries: 16384 (order: 5, 131072 bytes)
TCP bind hash table entries: 16384 (order: 4, 65536 bytes)
TCP: Hash tables configured (established 16384 bind 16384)
NET: Registered protocol family 1
NET: Registered protocol family 17
EXT3-fs: INFO: recovery required on readonly filesystem.
EXT3-fs: write access will be enabled during recovery.
EXT3-fs: recovery complete.
kjournald starting. Commit interval 5 seconds
EXT3-fs: mounted filesystem with ordered data mode.
VFS: Mounted root (ext3 filesystem) readonly.
Freeing unused kernel memory: 112k freed
INIT: version 2.86 booting
Activating swap.
EXT3 FS on sda, internal journal
hwclock is unable to get I/O port access: the iopl(3) call failed.
System time was Mon Apr 10 19:12:48 UTC 2006.
Setting the System Clock using the Hardware Clock as reference...
hwclock is unable to get I/O port access: the iopl(3) call failed.
System Clock set. System local time is now Mon Apr 10 19:12:48 UTC 2006.
Cleaning up ifupdown...done.
Checking all file systems...
fsck 1.37 (21-Mar-2005)
WARNING: Your /etc/fstab does not contain the fsck passno
field. I will kludge around things for you, but you
should fix your /etc/fstab file as soon as you can.
Setting kernel variables ...
... done.
Mounting local filesystems...
Cleaning /tmp /var/run /var/lock.
Running 0dns-down to make sure resolv.conf is ok...done.
Setting up networking...done.
Setting up IP spoofing protection: rp_filter.
Configuring network interfaces...done.
Setting the System Clock using the Hardware Clock as reference...
hwclock is unable to get I/O port access: the iopl(3) call failed.
System Clock set. Local time: Mon Apr 10 21:12:49 CEST 2006
Initializing random number generator...done.
Recovering nvi editor sessions... done.
Setting up X server socket directory /tmp/.X11-unix...done.
Setting up ICE socket directory /tmp/.ICE-unix...done.
INIT: Entering runlevel: 4
Starting system log daemon: syslogd.
Starting kernel log daemon: klogd.
Starting OpenLDAP: running BDB recovery, slapd slurpd.
Starting MTA: ^[[Aexim4.
Starting internet superserver: inetd.
Starting OpenBSD Secure Shell server: sshd.
Starting FreeRADIUS daemon: Mon Apr 10 21:15:51 2006 : Info: Starting -
reading
configuration files ...
freeradius.
Starting deferred execution scheduler: atd.
Starting periodic command scheduler: cron.
Debian GNU/Linux 3.1 radius1 tty1
xen-server:/srv/xen#
xen-server:~# cat /srv/xen/radius1
# -*- mode: python; -*-
#==========================================================================#
Python configuration setup for ''xm create''.
# This script sets the parameters used when a domain is created using
''xm
create''.
# You use a separate script for each domain you want to create, or
# you can set the parameters for the domain on the xm command line.
#==========================================================================
#---------------------------------------------------------------------------
-
# Kernel image file.
kernel = "/boot/vmlinuz-2.6.11.12-xenU"
# Optional ramdisk.
#ramdisk = "/boot/initrd.gz"
# The domain build function. Default is ''linux''.
#builder=''linux''
# Initial memory allocation (in megabytes) for the new domain.
memory = 400
# A name for your domain. All domains must have different names.
name = "radius1"
# Which CPU to start domain on?
#cpu = -1 # leave to Xen to pick
#---------------------------------------------------------------------------
-
# Define network interfaces.
# Number of network interfaces. Default is 1.
nics=1
# Optionally define mac and/or bridge for the network interfaces.
# Random MACs are assigned if not given.
#vif = [ '''']
vif = [ ''mac=aa:00:00:00:1b:11, bridge=xen-br0'' ]
#---------------------------------------------------------------------------
-
# Define the disk devices you want the domain to have access to, and
# what you want them accessible as.
# Each disk entry is of the form phy:UNAME,DEV,MODE
# where UNAME is the device, DEV is the device name the domain will see,
# and MODE is r for read-only, w for read-write.
disk = [ ''phy:volg1/radius1,sda,w'' ]
#---------------------------------------------------------------------------
-
# Set the kernel command line for the new domain.
# You only need to define the IP parameters and hostname if the
domain''s
# IP config doesn''t, e.g. in ifcfg-eth0 or via DHCP.
# You can use ''extra'' to set the runlevel and custom
environment
# variables used by custom rc scripts (e.g. VMID=, usr= ).
# Set if you want dhcp to allocate the IP address.
#dhcp="dhcp"
# Set netmask.
#netmask# Set default gateway.
#gateway# Set the hostname.
#hostname= "vm%d" % vmid
# Set root device.
root = "/dev/sda ro"
# Root device for nfs.
#root = "/dev/nfs"
# The nfs server.
#nfs_server = ''169.254.1.0''
# Root directory on the nfs server.
#nfs_root = ''/full/path/to/root/directory''
# Sets runlevel 4.
extra = "4"
#---------------------------------------------------------------------------
-
# Set according to whether you want the domain restarted when it exits.
# The default is ''onreboot'', which restarts the domain when it
shuts down
# with exit code reboot.
# Other values are ''always'', and ''never''.
#restart = ''onreboot''
#==========================================================================xen-server:~#
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
Hi,
i created a domU MAchine (debian Sarge)on an lvm patition under Xen3 with
actual kernel 2.6.12. This worked verry well and fast. I decided to move
this domU to an other machine running Xen 2.0.7. After copying the lvm on
this machine and creating the config file I booted this domU up with Kernle
2.6.11.12 which seems to be the most actual kernel fpr xen2.0.7 in a domU.
My Problem ist that the domU is verrrrry slow it need more than 4 Minutes to
boot into a debian base system. And starting an application is quiete
impossible with this week performance.
To be shure that xen dom0 works fine I created a new domU on this machine
with an lvm drive an a debian base system. This works verry well an fast...
Has someone any idea what causes this problem? Or how I can fix it?
Here are my logfiles:
Greetings Armin
xen-server:~# xm dmesg
ERROR: cannot use unconfigured serial port COM1
__ __ ____ ___ _____
\ \/ /___ _ __ |___ \ / _ \|___ |
\ // _ \ ''_ \ __) || | | | / /
/ \ __/ | | | / __/ | |_| | / /
/_/\_\___|_| |_| |_____(_)___(_)_/
http://www.cl.cam.ac.uk/netos/xen
University of Cambridge Computer Laboratory
Xen version 2.0.7 (root@localdomain) (gcc-Version 3.3.5 (Debian
1:3.3.5-13)) Mo Apr 10 18:14:49 CEST 2006
Latest ChangeSet:
(XEN) Physical RAM map:
(XEN) 0000000000000000 - 000000000009fc00 (usable)
(XEN) 000000000009fc00 - 00000000000a0000 (reserved)
(XEN) 00000000000e0000 - 0000000000100000 (reserved)
(XEN) 0000000000100000 - 000000007fff0000 (usable)
(XEN) 000000007fff0000 - 000000007ffff000 (ACPI data)
(XEN) 000000007ffff000 - 0000000080000000 (ACPI NVS)
(XEN) 00000000ffb80000 - 0000000100000000 (reserved)
(XEN) System RAM: 2047MB (2096700kB)
(XEN) Xen heap: 10MB (10732kB)
(XEN) CPU0: Before vendor init, caps: bfebfbff 00000000 00000000, vendor = 0
(XEN) CPU#0: Physical ID: 0, Logical ID: 0
(XEN) CPU caps: bfebfbff 00000000 00000000 00000000
(XEN) found SMP MP-table at 000ff780
(XEN) ACPI: RSDP (v002 ACPIAM ) @
0x000f6fb0
(XEN) ACPI: XSDT (v001 A M I OEMXSDT 0x04000429 MSFT 0x00000097) @
0x7fff0100
(XEN) ACPI: FADT (v003 A M I OEMFACP 0x04000429 MSFT 0x00000097) @
0x7fff0200
(XEN) ACPI: MADT (v001 A M I OEMAPIC 0x04000429 MSFT 0x00000097) @
0x7fff0300
(XEN) ACPI: OEMB (v001 A M I OEMBIOS 0x04000429 MSFT 0x00000097) @
0x7ffff040
(XEN) ACPI: DSDT (v001 PSCHL PSCHL017 0x00000017 INTL 0x02002026) @
0x00000000
(XEN) ACPI: Local APIC address 0xfee00000
(XEN) ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled)
(XEN) Processor #0 Unknown CPU [15:3] APIC version 20
(XEN) ACPI: LAPIC (acpi_id[0x02] lapic_id[0x01] enabled)
(XEN) Processor #1 Unknown CPU [15:3] APIC version 20
(XEN) ACPI: LAPIC_NMI (acpi_id[0x01] dfl dfl lint[0x1])
(XEN) Using ACPI for processor (LAPIC) configuration information
(XEN) Intel MultiProcessor Specification v1.4
(XEN) Virtual Wire compatibility mode.
(XEN) OEM ID: TEMPLATE Product ID: PSCH-L APIC at: 0xFEE00000
(XEN) I/O APIC #2 Version 32 at 0xFEC00000.
(XEN) I/O APIC #3 Version 32 at 0xFEC10000.
(XEN) Enabling APIC mode: Flat. Using 2 I/O APICs
(XEN) Processors: 2
(XEN) Using scheduler: Borrowed Virtual Time (bvt)
(XEN) Initializing CPU#0
(XEN) Detected 2992.627 MHz processor.
(XEN) CPU0: Before vendor init, caps: bfebfbff 00000000 00000000, vendor = 0
(XEN) CPU#0: Physical ID: 0, Logical ID: 0
(XEN) CPU caps: bfebfbff 00000000 00000000 00000000
(XEN) CPU0 booted
(XEN) enabled ExtINT on CPU#0
(XEN) ESR value before enabling vector: 00000000
(XEN) ESR value after enabling vector: 00000000
(XEN) Booting processor 1/1 eip 90000
(XEN) Initializing CPU#1
(XEN) masked ExtINT on CPU#1
(XEN) ESR value before enabling vector: 00000000
(XEN) ESR value after enabling vector: 00000000
(XEN) CPU1: Before vendor init, caps: bfebfbff 00000000 00000000, vendor = 0
(XEN) CPU#1: Physical ID: 0, Logical ID: 1
(XEN) CPU caps: bfebfbff 00000000 00000000 00000000
(XEN) CPU1 has booted.
(XEN) Total of 2 processors activated.
(XEN) ENABLING IO-APIC IRQs
(XEN) Setting 2 in the phys_id_present_map
(XEN) ...changing IO-APIC physical APIC ID to 2 ... ok.
(XEN) Setting 3 in the phys_id_present_map
(XEN) ...changing IO-APIC physical APIC ID to 3 ... ok.
(XEN) init IO_APIC IRQs
(XEN) ..TIMER: vector=0x41 pin1=2 pin2=0
(XEN) Using local APIC timer interrupts.
(XEN) Calibrating APIC timer for CPU0...
(XEN) ..... CPU speed is 2992.5230 MHz.
(XEN) ..... Bus speed is 199.5014 MHz.
(XEN) ..... bus_scale = 0x0000CC4F
(XEN) checking TSC synchronization across CPUs: passed.
(XEN) Time init:
(XEN) .... System Time: 20001009ns
(XEN) .... cpu_freq: 00000000:B25FDF2C
(XEN) .... scale: 00000001:562C9A1B
(XEN) .... Wall Clock: 1144690464s 130000us
(XEN) PCI: PCI BIOS revision 2.10 entry at 0xf0031, last bus=4
(XEN) PCI: Using configuration type 1
(XEN) PCI: Probing PCI hardware
(XEN) PCI: Probing PCI hardware (bus 00)
(XEN) PCI: Ignoring BAR0-3 of IDE controller 00:1f.1
(XEN) Transparent bridge - PCI device 8086:244e
(XEN) PCI: Using IRQ router default [8086/25a1] at 00:1f.0
(XEN) PCI->APIC IRQ transform: (B0,I29,P0) -> 16
(XEN) PCI->APIC IRQ transform: (B0,I29,P1) -> 19
(XEN) PCI->APIC IRQ transform: (B0,I29,P3) -> 23
(XEN) PCI->APIC IRQ transform: (B0,I31,P0) -> 18
(XEN) PCI->APIC IRQ transform: (B0,I31,P1) -> 17
(XEN) PCI->APIC IRQ transform: (B1,I1,P0) -> 18
(XEN) PCI->APIC IRQ transform: (B2,I3,P0) -> 25
(XEN) PCI->APIC IRQ transform: (B2,I5,P0) -> 27
(XEN) PCI->APIC IRQ transform: (B3,I4,P0) -> 24
(XEN) PCI->APIC IRQ transform: (B3,I4,P1) -> 25
(XEN) PCI->APIC IRQ transform: (B3,I6,P0) -> 26
(XEN) PCI->APIC IRQ transform: (B3,I6,P1) -> 27
(XEN) PCI->APIC IRQ transform: (B4,I4,P0) -> 20
(XEN) mtrr: v2.0 (20020519)
(XEN) *** LOADING DOMAIN 0 ***
(XEN) Xen-ELF header found:
''GUEST_OS=linux,GUEST_VER=2.6,XEN_VER=2.0,VIRT_BASE=0xC0000000,LOADER=generi
c,PT_MODE_WRITABLE''
(XEN) PHYSICAL MEMORY ARRANGEMENT:
(XEN) Kernel image: 00c00000->0104a87c
(XEN) Initrd image: 00000000->00000000
(XEN) Dom0 alloc.: 01400000->11400000
(XEN) VIRTUAL MEMORY ARRANGEMENT:
(XEN) Loaded kernel: c0100000->c057ffc4
(XEN) Init. ramdisk: c0580000->c0580000
(XEN) Phys-Mach map: c0580000->c05c0000
(XEN) Page tables: c05c0000->c05c3000
(XEN) Start info: c05c3000->c05c4000
(XEN) Boot stack: c05c4000->c05c5000
(XEN) TOTAL: c0000000->c0800000
(XEN) ENTRY ADDRESS: c0100000
(XEN) Scrubbing DOM0 RAM: ...done.
(XEN) Scrubbing Free RAM: .....................done.
(XEN) *** Serial input -> DOM0 (type ''CTRL-a'' three times
to switch input to
Xen).
xen-server:/srv/xen# cat bootlog radius1
Linux version 2.6.11.12-xenU (root@xen-server) (gcc-Version 3.3.5 (Debian
1:3.3.
5-13)) #1 Mon Apr 10 17:40:41 CEST 2006
BIOS-provided physical RAM map:
Xen: 0000000000000000 - 0000000019000000 (usable)
400MB LOWMEM available.
DMI not present.
IRQ lockup detection disabled
Allocating PCI resources starting at 19000000 (gap: 19000000:e7000000)
Built 1 zonelists
Kernel command line: root=/dev/sda ro 4
Initializing CPU#0
PID hash table entries: 2048 (order: 11, 32768 bytes)
Xen reported: 2992.627 MHz processor.
Using tsc for high-res timesource
Dentry cache hash table entries: 65536 (order: 6, 262144 bytes)
Inode-cache hash table entries: 32768 (order: 5, 131072 bytes)
vmalloc area: d9800000-fbff9000, maxmem 34000000
Memory: 402560k/409600k available (1631k kernel code, 6756k reserved, 439k
data,
112k init, 0k highmem)
Checking if this processor honours the WP bit even in supervisor mode... Ok.
Mount-cache hash table entries: 512 (order: 0, 4096 bytes)
CPU: Trace cache: 12K uops, L1 D cache: 16K
CPU: L2 cache: 1024K
CPU: Intel(R) Pentium(R) 4 CPU 3.00GHz stepping 04
Enabling fast FPU save and restore... done.
Enabling unmasked SIMD FPU exception support... done.
Checking ''hlt'' instruction... disabled
NET: Registered protocol family 16
xen_mem: Initialising balloon driver.
Initializing Cryptographic API
io scheduler noop registered
io scheduler anticipatory registered
io scheduler deadline registered
io scheduler cfq registered
RAMDISK driver initialized: 16 RAM disks of 4096K size 1024 blocksize
Xen virtual console successfully installed as tty
Event-channel device installed.
xen_blk: Initialising virtual block device driver
sda:<6>xen_net: Initialising virtual ethernet driver.
unknown partition table
NET: Registered protocol family 2
IP: routing cache hash table of 4096 buckets, 32Kbytes
TCP established hash table entries: 16384 (order: 5, 131072 bytes)
TCP bind hash table entries: 16384 (order: 4, 65536 bytes)
TCP: Hash tables configured (established 16384 bind 16384)
NET: Registered protocol family 1
NET: Registered protocol family 17
EXT3-fs: INFO: recovery required on readonly filesystem.
EXT3-fs: write access will be enabled during recovery.
EXT3-fs: recovery complete.
kjournald starting. Commit interval 5 seconds
EXT3-fs: mounted filesystem with ordered data mode.
VFS: Mounted root (ext3 filesystem) readonly.
Freeing unused kernel memory: 112k freed
INIT: version 2.86 booting
Activating swap.
EXT3 FS on sda, internal journal
hwclock is unable to get I/O port access: the iopl(3) call failed.
System time was Mon Apr 10 19:12:48 UTC 2006.
Setting the System Clock using the Hardware Clock as reference...
hwclock is unable to get I/O port access: the iopl(3) call failed.
System Clock set. System local time is now Mon Apr 10 19:12:48 UTC 2006.
Cleaning up ifupdown...done.
Checking all file systems...
fsck 1.37 (21-Mar-2005)
WARNING: Your /etc/fstab does not contain the fsck passno
field. I will kludge around things for you, but you
should fix your /etc/fstab file as soon as you can.
Setting kernel variables ...
... done.
Mounting local filesystems...
Cleaning /tmp /var/run /var/lock.
Running 0dns-down to make sure resolv.conf is ok...done.
Setting up networking...done.
Setting up IP spoofing protection: rp_filter.
Configuring network interfaces...done.
Setting the System Clock using the Hardware Clock as reference...
hwclock is unable to get I/O port access: the iopl(3) call failed.
System Clock set. Local time: Mon Apr 10 21:12:49 CEST 2006
Initializing random number generator...done.
Recovering nvi editor sessions... done.
Setting up X server socket directory /tmp/.X11-unix...done.
Setting up ICE socket directory /tmp/.ICE-unix...done.
INIT: Entering runlevel: 4
Starting system log daemon: syslogd.
Starting kernel log daemon: klogd.
Starting OpenLDAP: running BDB recovery, slapd slurpd.
Starting MTA: ^[[Aexim4.
Starting internet superserver: inetd.
Starting OpenBSD Secure Shell server: sshd.
Starting FreeRADIUS daemon: Mon Apr 10 21:15:51 2006 : Info: Starting -
reading
configuration files ...
freeradius.
Starting deferred execution scheduler: atd.
Starting periodic command scheduler: cron.
Debian GNU/Linux 3.1 radius1 tty1
xen-server:/srv/xen#
xen-server:~# cat /srv/xen/radius1
# -*- mode: python; -*-
#==========================================================================#
Python configuration setup for ''xm create''.
# This script sets the parameters used when a domain is created using
''xm
create''.
# You use a separate script for each domain you want to create, or
# you can set the parameters for the domain on the xm command line.
#==========================================================================
#---------------------------------------------------------------------------
-
# Kernel image file.
kernel = "/boot/vmlinuz-2.6.11.12-xenU"
# Optional ramdisk.
#ramdisk = "/boot/initrd.gz"
# The domain build function. Default is ''linux''.
#builder=''linux''
# Initial memory allocation (in megabytes) for the new domain.
memory = 400
# A name for your domain. All domains must have different names.
name = "radius1"
# Which CPU to start domain on?
#cpu = -1 # leave to Xen to pick
#---------------------------------------------------------------------------
-
# Define network interfaces.
# Number of network interfaces. Default is 1.
nics=1
# Optionally define mac and/or bridge for the network interfaces.
# Random MACs are assigned if not given.
#vif = [ '''']
vif = [ ''mac=aa:00:00:00:1b:11, bridge=xen-br0'' ]
#---------------------------------------------------------------------------
-
# Define the disk devices you want the domain to have access to, and
# what you want them accessible as.
# Each disk entry is of the form phy:UNAME,DEV,MODE
# where UNAME is the device, DEV is the device name the domain will see,
# and MODE is r for read-only, w for read-write.
disk = [ ''phy:volg1/radius1,sda,w'' ]
#---------------------------------------------------------------------------
-
# Set the kernel command line for the new domain.
# You only need to define the IP parameters and hostname if the
domain''s
# IP config doesn''t, e.g. in ifcfg-eth0 or via DHCP.
# You can use ''extra'' to set the runlevel and custom
environment
# variables used by custom rc scripts (e.g. VMID=, usr= ).
# Set if you want dhcp to allocate the IP address.
#dhcp="dhcp"
# Set netmask.
#netmask# Set default gateway.
#gateway# Set the hostname.
#hostname= "vm%d" % vmid
# Set root device.
root = "/dev/sda ro"
# Root device for nfs.
#root = "/dev/nfs"
# The nfs server.
#nfs_server = ''169.254.1.0''
# Root directory on the nfs server.
#nfs_root = ''/full/path/to/root/directory''
# Sets runlevel 4.
extra = "4"
#---------------------------------------------------------------------------
-
# Set according to whether you want the domain restarted when it exits.
# The default is ''onreboot'', which restarts the domain when it
shuts down
# with exit code reboot.
# Other values are ''always'', and ''never''.
#restart = ''onreboot''
#==========================================================================xen-server:~#
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
Hi,
i created a domU MAchine (debian Sarge)on an lvm patition under Xen3 with
actual kernel 2.6.12. This worked verry well and fast. I decided to move
this domU to an other machine running Xen 2.0.7. After copying the lvm on
this machine and creating the config file I booted this domU up with Kernle
2.6.11.12 which seems to be the most actual kernel fpr xen2.0.7 in a domU.
My Problem ist that the domU is verrrrry slow it need more than 4 Minutes to
boot into a debian base system. And starting an application is quiete
impossible with this week performance.
To be shure that xen dom0 works fine I created a new domU on this machine
with an lvm drive an a debian base system. This works verry well an fast...
Has someone any idea what causes this problem? Or how I can fix it?
Here are my logfiles:
Greetings Armin
xen-server:~# xm dmesg
ERROR: cannot use unconfigured serial port COM1
__ __ ____ ___ _____
\ \/ /___ _ __ |___ \ / _ \|___ |
\ // _ \ ''_ \ __) || | | | / /
/ \ __/ | | | / __/ | |_| | / /
/_/\_\___|_| |_| |_____(_)___(_)_/
http://www.cl.cam.ac.uk/netos/xen
University of Cambridge Computer Laboratory
Xen version 2.0.7 (root@localdomain) (gcc-Version 3.3.5 (Debian
1:3.3.5-13)) Mo Apr 10 18:14:49 CEST 2006
Latest ChangeSet:
(XEN) Physical RAM map:
(XEN) 0000000000000000 - 000000000009fc00 (usable)
(XEN) 000000000009fc00 - 00000000000a0000 (reserved)
(XEN) 00000000000e0000 - 0000000000100000 (reserved)
(XEN) 0000000000100000 - 000000007fff0000 (usable)
(XEN) 000000007fff0000 - 000000007ffff000 (ACPI data)
(XEN) 000000007ffff000 - 0000000080000000 (ACPI NVS)
(XEN) 00000000ffb80000 - 0000000100000000 (reserved)
(XEN) System RAM: 2047MB (2096700kB)
(XEN) Xen heap: 10MB (10732kB)
(XEN) CPU0: Before vendor init, caps: bfebfbff 00000000 00000000, vendor = 0
(XEN) CPU#0: Physical ID: 0, Logical ID: 0
(XEN) CPU caps: bfebfbff 00000000 00000000 00000000
(XEN) found SMP MP-table at 000ff780
(XEN) ACPI: RSDP (v002 ACPIAM ) @
0x000f6fb0
(XEN) ACPI: XSDT (v001 A M I OEMXSDT 0x04000429 MSFT 0x00000097) @
0x7fff0100
(XEN) ACPI: FADT (v003 A M I OEMFACP 0x04000429 MSFT 0x00000097) @
0x7fff0200
(XEN) ACPI: MADT (v001 A M I OEMAPIC 0x04000429 MSFT 0x00000097) @
0x7fff0300
(XEN) ACPI: OEMB (v001 A M I OEMBIOS 0x04000429 MSFT 0x00000097) @
0x7ffff040
(XEN) ACPI: DSDT (v001 PSCHL PSCHL017 0x00000017 INTL 0x02002026) @
0x00000000
(XEN) ACPI: Local APIC address 0xfee00000
(XEN) ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled)
(XEN) Processor #0 Unknown CPU [15:3] APIC version 20
(XEN) ACPI: LAPIC (acpi_id[0x02] lapic_id[0x01] enabled)
(XEN) Processor #1 Unknown CPU [15:3] APIC version 20
(XEN) ACPI: LAPIC_NMI (acpi_id[0x01] dfl dfl lint[0x1])
(XEN) Using ACPI for processor (LAPIC) configuration information
(XEN) Intel MultiProcessor Specification v1.4
(XEN) Virtual Wire compatibility mode.
(XEN) OEM ID: TEMPLATE Product ID: PSCH-L APIC at: 0xFEE00000
(XEN) I/O APIC #2 Version 32 at 0xFEC00000.
(XEN) I/O APIC #3 Version 32 at 0xFEC10000.
(XEN) Enabling APIC mode: Flat. Using 2 I/O APICs
(XEN) Processors: 2
(XEN) Using scheduler: Borrowed Virtual Time (bvt)
(XEN) Initializing CPU#0
(XEN) Detected 2992.627 MHz processor.
(XEN) CPU0: Before vendor init, caps: bfebfbff 00000000 00000000, vendor = 0
(XEN) CPU#0: Physical ID: 0, Logical ID: 0
(XEN) CPU caps: bfebfbff 00000000 00000000 00000000
(XEN) CPU0 booted
(XEN) enabled ExtINT on CPU#0
(XEN) ESR value before enabling vector: 00000000
(XEN) ESR value after enabling vector: 00000000
(XEN) Booting processor 1/1 eip 90000
(XEN) Initializing CPU#1
(XEN) masked ExtINT on CPU#1
(XEN) ESR value before enabling vector: 00000000
(XEN) ESR value after enabling vector: 00000000
(XEN) CPU1: Before vendor init, caps: bfebfbff 00000000 00000000, vendor = 0
(XEN) CPU#1: Physical ID: 0, Logical ID: 1
(XEN) CPU caps: bfebfbff 00000000 00000000 00000000
(XEN) CPU1 has booted.
(XEN) Total of 2 processors activated.
(XEN) ENABLING IO-APIC IRQs
(XEN) Setting 2 in the phys_id_present_map
(XEN) ...changing IO-APIC physical APIC ID to 2 ... ok.
(XEN) Setting 3 in the phys_id_present_map
(XEN) ...changing IO-APIC physical APIC ID to 3 ... ok.
(XEN) init IO_APIC IRQs
(XEN) ..TIMER: vector=0x41 pin1=2 pin2=0
(XEN) Using local APIC timer interrupts.
(XEN) Calibrating APIC timer for CPU0...
(XEN) ..... CPU speed is 2992.5230 MHz.
(XEN) ..... Bus speed is 199.5014 MHz.
(XEN) ..... bus_scale = 0x0000CC4F
(XEN) checking TSC synchronization across CPUs: passed.
(XEN) Time init:
(XEN) .... System Time: 20001009ns
(XEN) .... cpu_freq: 00000000:B25FDF2C
(XEN) .... scale: 00000001:562C9A1B
(XEN) .... Wall Clock: 1144690464s 130000us
(XEN) PCI: PCI BIOS revision 2.10 entry at 0xf0031, last bus=4
(XEN) PCI: Using configuration type 1
(XEN) PCI: Probing PCI hardware
(XEN) PCI: Probing PCI hardware (bus 00)
(XEN) PCI: Ignoring BAR0-3 of IDE controller 00:1f.1
(XEN) Transparent bridge - PCI device 8086:244e
(XEN) PCI: Using IRQ router default [8086/25a1] at 00:1f.0
(XEN) PCI->APIC IRQ transform: (B0,I29,P0) -> 16
(XEN) PCI->APIC IRQ transform: (B0,I29,P1) -> 19
(XEN) PCI->APIC IRQ transform: (B0,I29,P3) -> 23
(XEN) PCI->APIC IRQ transform: (B0,I31,P0) -> 18
(XEN) PCI->APIC IRQ transform: (B0,I31,P1) -> 17
(XEN) PCI->APIC IRQ transform: (B1,I1,P0) -> 18
(XEN) PCI->APIC IRQ transform: (B2,I3,P0) -> 25
(XEN) PCI->APIC IRQ transform: (B2,I5,P0) -> 27
(XEN) PCI->APIC IRQ transform: (B3,I4,P0) -> 24
(XEN) PCI->APIC IRQ transform: (B3,I4,P1) -> 25
(XEN) PCI->APIC IRQ transform: (B3,I6,P0) -> 26
(XEN) PCI->APIC IRQ transform: (B3,I6,P1) -> 27
(XEN) PCI->APIC IRQ transform: (B4,I4,P0) -> 20
(XEN) mtrr: v2.0 (20020519)
(XEN) *** LOADING DOMAIN 0 ***
(XEN) Xen-ELF header found:
''GUEST_OS=linux,GUEST_VER=2.6,XEN_VER=2.0,VIRT_BASE=0xC0000000,LOADER=generi
c,PT_MODE_WRITABLE''
(XEN) PHYSICAL MEMORY ARRANGEMENT:
(XEN) Kernel image: 00c00000->0104a87c
(XEN) Initrd image: 00000000->00000000
(XEN) Dom0 alloc.: 01400000->11400000
(XEN) VIRTUAL MEMORY ARRANGEMENT:
(XEN) Loaded kernel: c0100000->c057ffc4
(XEN) Init. ramdisk: c0580000->c0580000
(XEN) Phys-Mach map: c0580000->c05c0000
(XEN) Page tables: c05c0000->c05c3000
(XEN) Start info: c05c3000->c05c4000
(XEN) Boot stack: c05c4000->c05c5000
(XEN) TOTAL: c0000000->c0800000
(XEN) ENTRY ADDRESS: c0100000
(XEN) Scrubbing DOM0 RAM: ...done.
(XEN) Scrubbing Free RAM: .....................done.
(XEN) *** Serial input -> DOM0 (type ''CTRL-a'' three times
to switch input to
Xen).
xen-server:/srv/xen# cat bootlog radius1
Linux version 2.6.11.12-xenU (root@xen-server) (gcc-Version 3.3.5 (Debian
1:3.3.
5-13)) #1 Mon Apr 10 17:40:41 CEST 2006
BIOS-provided physical RAM map:
Xen: 0000000000000000 - 0000000019000000 (usable)
400MB LOWMEM available.
DMI not present.
IRQ lockup detection disabled
Allocating PCI resources starting at 19000000 (gap: 19000000:e7000000)
Built 1 zonelists
Kernel command line: root=/dev/sda ro 4
Initializing CPU#0
PID hash table entries: 2048 (order: 11, 32768 bytes)
Xen reported: 2992.627 MHz processor.
Using tsc for high-res timesource
Dentry cache hash table entries: 65536 (order: 6, 262144 bytes)
Inode-cache hash table entries: 32768 (order: 5, 131072 bytes)
vmalloc area: d9800000-fbff9000, maxmem 34000000
Memory: 402560k/409600k available (1631k kernel code, 6756k reserved, 439k
data,
112k init, 0k highmem)
Checking if this processor honours the WP bit even in supervisor mode... Ok.
Mount-cache hash table entries: 512 (order: 0, 4096 bytes)
CPU: Trace cache: 12K uops, L1 D cache: 16K
CPU: L2 cache: 1024K
CPU: Intel(R) Pentium(R) 4 CPU 3.00GHz stepping 04
Enabling fast FPU save and restore... done.
Enabling unmasked SIMD FPU exception support... done.
Checking ''hlt'' instruction... disabled
NET: Registered protocol family 16
xen_mem: Initialising balloon driver.
Initializing Cryptographic API
io scheduler noop registered
io scheduler anticipatory registered
io scheduler deadline registered
io scheduler cfq registered
RAMDISK driver initialized: 16 RAM disks of 4096K size 1024 blocksize
Xen virtual console successfully installed as tty
Event-channel device installed.
xen_blk: Initialising virtual block device driver
sda:<6>xen_net: Initialising virtual ethernet driver.
unknown partition table
NET: Registered protocol family 2
IP: routing cache hash table of 4096 buckets, 32Kbytes
TCP established hash table entries: 16384 (order: 5, 131072 bytes)
TCP bind hash table entries: 16384 (order: 4, 65536 bytes)
TCP: Hash tables configured (established 16384 bind 16384)
NET: Registered protocol family 1
NET: Registered protocol family 17
EXT3-fs: INFO: recovery required on readonly filesystem.
EXT3-fs: write access will be enabled during recovery.
EXT3-fs: recovery complete.
kjournald starting. Commit interval 5 seconds
EXT3-fs: mounted filesystem with ordered data mode.
VFS: Mounted root (ext3 filesystem) readonly.
Freeing unused kernel memory: 112k freed
INIT: version 2.86 booting
Activating swap.
EXT3 FS on sda, internal journal
hwclock is unable to get I/O port access: the iopl(3) call failed.
System time was Mon Apr 10 19:12:48 UTC 2006.
Setting the System Clock using the Hardware Clock as reference...
hwclock is unable to get I/O port access: the iopl(3) call failed.
System Clock set. System local time is now Mon Apr 10 19:12:48 UTC 2006.
Cleaning up ifupdown...done.
Checking all file systems...
fsck 1.37 (21-Mar-2005)
WARNING: Your /etc/fstab does not contain the fsck passno
field. I will kludge around things for you, but you
should fix your /etc/fstab file as soon as you can.
Setting kernel variables ...
... done.
Mounting local filesystems...
Cleaning /tmp /var/run /var/lock.
Running 0dns-down to make sure resolv.conf is ok...done.
Setting up networking...done.
Setting up IP spoofing protection: rp_filter.
Configuring network interfaces...done.
Setting the System Clock using the Hardware Clock as reference...
hwclock is unable to get I/O port access: the iopl(3) call failed.
System Clock set. Local time: Mon Apr 10 21:12:49 CEST 2006
Initializing random number generator...done.
Recovering nvi editor sessions... done.
Setting up X server socket directory /tmp/.X11-unix...done.
Setting up ICE socket directory /tmp/.ICE-unix...done.
INIT: Entering runlevel: 4
Starting system log daemon: syslogd.
Starting kernel log daemon: klogd.
Starting OpenLDAP: running BDB recovery, slapd slurpd.
Starting MTA: ^[[Aexim4.
Starting internet superserver: inetd.
Starting OpenBSD Secure Shell server: sshd.
Starting FreeRADIUS daemon: Mon Apr 10 21:15:51 2006 : Info: Starting -
reading
configuration files ...
freeradius.
Starting deferred execution scheduler: atd.
Starting periodic command scheduler: cron.
Debian GNU/Linux 3.1 radius1 tty1
xen-server:/srv/xen#
xen-server:~# cat /srv/xen/radius1
# -*- mode: python; -*-
#==========================================================================#
Python configuration setup for ''xm create''.
# This script sets the parameters used when a domain is created using
''xm
create''.
# You use a separate script for each domain you want to create, or
# you can set the parameters for the domain on the xm command line.
#==========================================================================
#---------------------------------------------------------------------------
-
# Kernel image file.
kernel = "/boot/vmlinuz-2.6.11.12-xenU"
# Optional ramdisk.
#ramdisk = "/boot/initrd.gz"
# The domain build function. Default is ''linux''.
#builder=''linux''
# Initial memory allocation (in megabytes) for the new domain.
memory = 400
# A name for your domain. All domains must have different names.
name = "radius1"
# Which CPU to start domain on?
#cpu = -1 # leave to Xen to pick
#---------------------------------------------------------------------------
-
# Define network interfaces.
# Number of network interfaces. Default is 1.
nics=1
# Optionally define mac and/or bridge for the network interfaces.
# Random MACs are assigned if not given.
#vif = [ '''']
vif = [ ''mac=aa:00:00:00:1b:11, bridge=xen-br0'' ]
#---------------------------------------------------------------------------
-
# Define the disk devices you want the domain to have access to, and
# what you want them accessible as.
# Each disk entry is of the form phy:UNAME,DEV,MODE
# where UNAME is the device, DEV is the device name the domain will see,
# and MODE is r for read-only, w for read-write.
disk = [ ''phy:volg1/radius1,sda,w'' ]
#---------------------------------------------------------------------------
-
# Set the kernel command line for the new domain.
# You only need to define the IP parameters and hostname if the
domain''s
# IP config doesn''t, e.g. in ifcfg-eth0 or via DHCP.
# You can use ''extra'' to set the runlevel and custom
environment
# variables used by custom rc scripts (e.g. VMID=, usr= ).
# Set if you want dhcp to allocate the IP address.
#dhcp="dhcp"
# Set netmask.
#netmask# Set default gateway.
#gateway# Set the hostname.
#hostname= "vm%d" % vmid
# Set root device.
root = "/dev/sda ro"
# Root device for nfs.
#root = "/dev/nfs"
# The nfs server.
#nfs_server = ''169.254.1.0''
# Root directory on the nfs server.
#nfs_root = ''/full/path/to/root/directory''
# Sets runlevel 4.
extra = "4"
#---------------------------------------------------------------------------
-
# Set according to whether you want the domain restarted when it exits.
# The default is ''onreboot'', which restarts the domain when it
shuts down
# with exit code reboot.
# Other values are ''always'', and ''never''.
#restart = ''onreboot''
#==========================================================================xen-server:~#
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
Am Dienstag 11 April 2006 14:19 schrieb Krämer Armin:> <snip>Don''t repost in such short intervals... That doesn''t make it more likely for you to get an answer, but less likely... --- Heiko. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Okay, i found my mistake on my own. The mistake was a wrong configured lo Interface and the wrong defined nameservers In this environment. This causes my DomU running impossible slowly (5 minuttes to open mc :-) ) A correction of this and all works fine now. Greeting Armin Message: 1 Date: Tue, 11 Apr 2006 11:21:27 +0200 From: Kr?mer Armin <Kraemer.Armin@web.de> Subject: [Xen-users] Verry Slow domU performance To: <xen-users@lists.xensource.com> Message-ID: <002f01c65d49$4fcb7f10$152ea8c0@workstationak> Content-Type: text/plain; charset="iso-8859-1" Hi, i created a domU MAchine (debian Sarge)on an lvm patition under Xen3 with actual kernel 2.6.12. This worked verry well and fast. I decided to move this domU to an other machine running Xen 2.0.7. After copying the lvm on this machine and creating the config file I booted this domU up with Kernle 2.6.11.12 which seems to be the most actual kernel fpr xen2.0.7 in a domU. My Problem ist that the domU is verrrrry slow it need more than 4 Minutes to boot into a debian base system. And starting an application is quiete impossible with this week performance. To be shure that xen dom0 works fine I created a new domU on this machine with an lvm drive an a debian base system. This works verry well an fast... Has someone any idea what causes this problem? Or how I can fix it? Here are my logfiles: Greetings Armin _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users