Xen users - Apr 2009 - Is LVM really that much slower than Container?

Hi,

I installed Windows XP SP3 to two domU. Only difference between them:  
one is stored in a container (let''s call it domU1), while the other  
one (domU2) is stored on a logical volume made available by the dom0.

I have a tar.gz-file which is 400 MB in size. Copying this file from a  
samba server on the network via LAN to domU1 takes 11 seconds on domU1  
and a little more than 2 minutes on domU2.

Creating a local copy of the file takes 3 seconds on domU1 and 80  
seconds on domU2. Is that a penalty LVM-users have to live with or is  
something wrong with my system?

Tim


Hardware
=======Asus P5Q-EM DO (Intel Q45 Chipset with VT-d)
Intel Core 2 Quad Q9550 (E0), 4x 2.83GHz
8 GB RAM
latest Bios, not overclocked
5 x Western Digital RE3 1000GB, SATA II (WD1002FBYS) connected to  
onbord SATA

domO
====Ubuntu 8.10 with linux-xen0-2.6.27.5 (hg checkout), xfce, convirt
/boot with 500 MB on RAID 1 over all 5 drives
swap with 2 GB on each of the 5 drives
LVM over RAID 5 over the remaining space of the 5 drives, / on logical  
volume

domU1
====import os, re
arch=os.uname()[4]
if re.search(''64'', arch):
     arch_libdir = ''lib64''
else:
     arch_libdir = ''lib''
name=''XP-Test-Container''
kernel=''/usr/lib/xen/boot/hvmloader''
builder=''hvm''
memory=512
shadow_memory=10
#vcpus=1
#cpus = "0"        # all vcpus run on CPU0
pae=1
acpi=0
apic=0
#vif=[''mac=00:16:3e:4d:f5:bc, bridge=xenbr0'']
vif=['''']
disk=[''file:/var/cache/convirt/vm_disks/XP-Test- 
Container.disk.xm,hda,w'', ''file:/var/cache/convirt/vm_disks/ 
winxpprof.iso,hdc:cdrom,r'']
device_model=''/usr/'' + arch_libdir +
''/xen/bin/qemu-dm''

# Boots from CDROM.
# Change to ''c'' after windows installation in order to boot
from disk.
boot=''d''
#boot=''c''

sdl=0
vnc=1
vncunused=1
stdvga=0
extra=''''
on_reboot=''restart''
on_shutdown=''destroy''
ramdisk=''''
image_name=''Windows_CD_Install''
on_crash=''restart''
bootloader=''''
vcpus=1
root=''''
platform=''xen''
network_mode=''user''
usb=1
usbdevice=''tablet''

STORAGE_STATS={''DISK_STATS'':
{''/var/cache/convirt/vm_disks/
winxpprof.iso'': {''DEV_TYPE'':
''FILE'', ''IS_LOCAL'': True,
''DISK_SIZE'':
638042112, ''DISK_NAME'':
''/var/cache/convirt/vm_disks/winxpprof.iso''},
''/var/cache/convirt/vm_disks/XP-Test-Container.disk.xm'':
{''DEV_TYPE'':
''FILE'', ''IS_LOCAL'': True,
''DISK_SIZE'': 20971520001, ''DISK_NAME'':
''/var/
cache/convirt/vm_disks/XP-Test-Container.disk.xm''}},  
''LOCAL_ALLOCATION'': 21609562113,
''SHARED_ALLOCATION'': 0}
image_id=''b7279a971653b0c7d7c5c7cfa6d783d9''
image_conf=''/var/log/convirt/image_store/Windows_CD_Install/ 
Windows_CD_Install_XP-Test-Container_image.conf''
uuid=''80dfff4c-227a-e8bc-432d-2dcf15436304''


domU2
=====# Automtically generated by ConVirt
import os, re
arch=os.uname()[4]
if re.search(''64'', arch):
     arch_libdir = ''lib64''
else:
     arch_libdir = ''lib''


name=''XP-Test-LVM''

kernel=''/usr/lib/xen/boot/hvmloader''
builder=''hvm''


memory=512
shadow_memory=10
#vcpus=1
#cpus = "0"        # all vcpus run on CPU0

pae=1
acpi=0
apic=0
#vif=[''mac=00:16:3e:44:65:6f, bridge=xenbr0'']
vif=['''']
disk=[''phy:/dev/raidvg/XP-Test-LVM.disk.xm,hda,w'',
''file:/var/cache/
convirt/vm_disks/winxpprof.iso,hdc:cdrom,r'']
device_model=''/usr/'' + arch_libdir +
''/xen/bin/qemu-dm''

# Boots from CDROM.
# Change to ''c'' after windows installation in order to boot
from disk.
boot=''d''
#boot=''c''

sdl=0
vnc=1
vncunused=1
stdvga=0
extra=''''
on_reboot=''restart''
on_shutdown=''destroy''
ramdisk=''''
image_name=''Windows_CD_Install_LVM''
on_crash=''restart''
bootloader=''''
vcpus=1
root=''''
platform=''xen''
network_mode=''user''
usb=1
usbdevice=''tablet''

STORAGE_STATS={''DISK_STATS'':
{''/var/cache/convirt/vm_disks/
winxpprof.iso'': {''DEV_TYPE'':
''FILE'', ''IS_LOCAL'': True,
''DISK_SIZE'':
638042112, ''DISK_NAME'':
''/var/cache/convirt/vm_disks/winxpprof.iso''},
''/dev/raidvg/XP-Test-LVM.disk.xm'':
{''DEV_TYPE'': ''BLOCK'',
''IS_LOCAL'':
True, ''DISK_SIZE'': 20971520000, ''DISK_NAME'':
''/dev/raidvg/XP-Test-
LVM.disk.xm''}}, ''LOCAL_ALLOCATION'': 21609562112,
''SHARED_ALLOCATION'': 0}
image_id=''d500a710e92058067521fbe7063de445''
image_conf=''/var/log/convirt/image_store/Windows_CD_Install_LVM/ 
Windows_CD_Install_LVM_XP-Test-LVM_image.conf''
uuid=''7f5b9160-dda6-56e5-1ba0-2071e6ceb778''





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

Tim Kaufmann wrote:
> Hi,
> 
> I installed Windows XP SP3 to two domU. Only difference between them:
> one is stored in a container (let''s call it domU1), while the
other one
> (domU2) is stored on a logical volume made available by the dom0.
> 
> I have a tar.gz-file which is 400 MB in size. Copying this file from a
> samba server on the network via LAN to domU1 takes 11 seconds on domU1
> and a little more than 2 minutes on domU2.
> 
> Creating a local copy of the file takes 3 seconds on domU1 and 80
> seconds on domU2. Is that a penalty LVM-users have to live with or is
> something wrong with my system?
> 
> Tim
No, LVM are actually a lot faster than file loopbacks. I don''t get why
you are having such results. Did you install the GPLPV drivers on both
instance?

Thomas

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

On Mon, Apr 13, 2009 at 8:17 AM, Tim Kaufmann <tim@timkaufmann.de>
wrote:
> Hi,
>
> I installed Windows XP SP3 to two domU. Only difference between them: one
is
> stored in a container (let''s call it domU1), while the other one
(domU2) is
> stored on a logical volume made available by the dom0.
>
> I have a tar.gz-file which is 400 MB in size. Copying this file from a
samba
> server on the network via LAN to domU1 takes 11 seconds on domU1 and a
> little more than 2 minutes on domU2.
>
> Creating a local copy of the file takes 3 seconds on domU1 and 80 seconds
on
> domU2. Is that a penalty LVM-users have to live with or is something wrong
> with my system?
Could be cache effect. Since (when using file:/) the domU storage can
be cached in dom0, it will give the illussion of fast response when in
fact data has not been written yet. Does dom0 uses more than 400MB
memory (try xm list)?

It''s not recommended to use file:/ as it''s possible to cause
data
corruption. Try changing it to tap:aio:/, and you should see that LVM
is faster.

Regards,

Fajar

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

On Mon, Apr 13, 2009 at 7:05 PM, Tim Kaufmann <tim@timkaufmann.de>
wrote:
>
> Am 13.04.2009 um 07:32 schrieb Fajar A. Nugraha:
>
>> Does dom0 uses more than 400MB
>> memory (try xm list)?
>
> Yes, it uses all the RAM which is not used by the domU.
>
>> It''s not recommended to use file:/ as it''s possible
to cause data
>> corruption. Try changing it to tap:aio:/, and you should see that LVM
>> is faster.
>
> Unfortunately trying to boot domU1 from the container with tap:aio:/
totally
> locks up dom0 as the screen with the Windows Logo and the progress bar
> appears. It makes no difference whether I boot with /gplpv or not. The last
> entries from /var/log/syslog:
> Anyhow: If tap:aio:/ is supposed to be even slower than LVM, I fear all
this
> might lead me nowhere. My trusty old server (P4@2,6GHz, 2 GB RAM, Ubuntu
> Hardy LTS, no RAID) runs XP on VirtualBox 2.1. The filecopy over the
network
> takes 3 minutes (2 Minutes on domU2), creating a local copy 2 minutes (80
> seconds on domU2). Hope nobody''s gonna kill me if I dare to ask
where the
> performance gain I expected from the newer hardware and the Xen hypervisor
> went?
I missed the part in your earlier post saying that you use Ubuntu :)
If I remember correctly some version of Ubuntu (maybe it still does?)
have a bug in tap:aio. It''s better to compile xen yourself.

Since your local copy operation is also slow, here''s what I can tell
you :
- I''m using Xen 3.3.1 on top of RHEL 5.3
- on dom0, ext3 on top of LVM :
# time (cp test400M test400M2;sync)

real	0m5.416s
user	0m0.068s
sys	0m0.984s

- on Windows domU + cygwin, GPLPV, on top of LVM
$ time ( cp test400M test400M2;sync )

real    0m14.320s
user    0m0.070s
sys     0m2.042s

"test400M" is a 400-MB zero-filled file created with dd. As you can
see my result is much faster compared to yours.

Try testing dom0 first, maybe your setup is somehow messed up (xen
problem, driver problem, etc.). If that''s good, try on domU with
GPLPV.

Regards,

Fajar

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

Hi Fajar,

thanks a lot for your help!
> I missed the part in your earlier post saying that you use Ubuntu :)
> If I remember correctly some version of Ubuntu (maybe it still does?)
> have a bug in tap:aio. It''s better to compile xen yourself.
Ah ok.

My dom0 is faster than your''s, while my domU1 sucks :-)

Dom0
====root@automatix:~# dd if=/dev/zero of=/root/test400M bs=1024k count=400
400+0 records in
400+0 records out
419430400 bytes (419 MB) copied, 0,749079 s, 560 MB/s

root@automatix:~# time (cp test400M test400M2;sync)
real	0m2.622s
user	0m0.030s
sys	0m0.900s


DomU1
=====root@xplvm:~# dd if=/dev/zero of=/home/Tim/test400M bs=1024k count=400
400+0 records in
400+0 records out
419430400 bytes (419 MB) copied, 85,723 s, 4,9 MB/s

root@xplvm:~# time (cp test400M test400M2;sync)
real	1m21.387s
user	0m0.070s
sys	0m0.991s

Tim


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

With the help of Tom Brown, I''ve started over benchmarking dom0 and  
domU2 for more realistic results. Correct me if I''m wrong, Tom, but  
what you recommended was using a larger testfile (twice the size of  
the RAM) and adding "conv=fsync" to the dd-command to get rid of  
caching effects.

dom0
===dd if=/dev/zero of=./test16384M bs=1024k count=16384 conv=fsync
16384+0 records in
16384+0 records out
17179869184 bytes (17 GB) copied, 82,1605 s, 209 MB/s

time (cp test16384M test16384M2;sync)
real	3m8.108s
user	0m0.660s
sys	0m20.790s


domU2
====dd if=/dev/zero of=./test1024M bs=1024k count=1024 conv=fsync
1024+0 records in
1024+0 records out
1073741824 bytes (1.1 GB) copied, 184.295 s, 5,8 MB/s

time (cp test1024M test1024M2;sync)
real	3m11.915s  (testfile is only 1/16 the size of testfile for dom0!)
user	0m0.100s
sys	0m2.723s

Tim




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

On Mon, 13 Apr 2009, Tim Kaufmann wrote:
> With the help of Tom Brown, I''ve started over benchmarking dom0
and domU2 for
> more realistic results. Correct me if I''m wrong, Tom, but what you
> recommended was using a larger testfile (twice the size of the RAM) and 
> adding "conv=fsync" to the dd-command to get rid of caching
effects.
In theory, either change will work... but using the big files will also 
mitigate things like raid card and on-disk write caches (which fsync might 
not cut through).
>
> dom0
> ===> dd if=/dev/zero of=./test16384M bs=1024k count=16384 conv=fsync
> 16384+0 records in
> 16384+0 records out
> 17179869184 bytes (17 GB) copied, 82,1605 s, 209 MB/s
That is still a pretty impressive number :)
> time (cp test16384M test16384M2;sync)
> real	3m8.108s
> user	0m0.660s
> sys	0m20.790s
And given your FAST write speed, that seems about right for the mixed 
read/write/seek activity that copying big files will represent.
> domU2
> ====> dd if=/dev/zero of=./test1024M bs=1024k count=1024 conv=fsync
> 1024+0 records in
> 1024+0 records out
> 1073741824 bytes (1.1 GB) copied, 184.295 s, 5,8 MB/s
>
> time (cp test1024M test1024M2;sync)
> real	3m11.915s  (testfile is only 1/16 the size of testfile for dom0!)
Depending on how you have the storage for the domU setup, you might still 
be getting caching in the dom0, so it is safest to stick to the full 
system size, but since these numbers are so much drastically slower than 
your dom0 numbers, they clearly demonstrate that there IS a bottleneck 
here that is far slower than your disk subsystem... and using 16 gig would 
take at least 16 times as long which is starting to get unreasonable, 
especially when the "this is SLOW" point has already been made.

Anyhow, sorry for the digression. I can''t remember what the numbers
were
supposed to demonstrate. :)


-Tom

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

Am 13.04.2009 um 21:52 schrieb Tom Brown:
> Anyhow, sorry for the digression. I can''t remember what the
numbers
> were supposed to demonstrate. :)
We were trying to find out whether it''s the dom0 or the domU2 (LVM- 
stored XP SP3) that underperforms. Now that we know that dom0 is ok,  
what''s next?

Tim


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

Hi,

I did some more testing:

1) Reinstalled Windows XP (from XP SP1a disc as before), but upgraded  
to SP2 instead of SP3, no gplpv:

Five tests with dd if=/dev/zero of=./test1024M bs=1024k count=1024  
conv=fsync resulted in various speeds between 45 and 61 MB/s.

Copying from samba share to local disc via GBit-Ethernet: 10 MB/s

2) #1 with gplpv_fre_wxp_x86_0.10.0.50.msi

dd: 5.3 MB/s

Instead of copying from samba to local hd (where speed would be  
limited by the underperforming hd), I copied from one samba share to  
another, reading and writing 400 MB in 25 seconds.

3) #1 with only the pci and network driver from  
gplpv_fre_wxp_x86_0.10.0.50.msi

Copying from samba share to local disc via GBit-Ethernet: 28,5 MB/s


Conclusion: There''s a problem in the gplpv scsi and/or vbd drivers and/
or in the combination of those with my Xen-Setup. What can I do now?

Tim



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

On Tue, Apr 14, 2009 at 4:32 AM, Tim Kaufmann <tim@timkaufmann.de>
wrote:
>
> Am 13.04.2009 um 21:52 schrieb Tom Brown:
>
>> Anyhow, sorry for the digression. I can''t remember what the
numbers were
>> supposed to demonstrate. :)
>
> We were trying to find out whether it''s the dom0 or the domU2
(LVM-stored XP
> SP3) that underperforms. Now that we know that dom0 is ok, what''s
next?
>From that result my guess is that your Xen installation is somehow messed up
:)
If you have time, I suggest you try Centos 5.3, with either bundled
Xen (3.1 plus redhat-specific changes) or Xen 3.3.1 from Gitco. It
shows good results on my system.

Regards,

Fajar

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

On Tue, Apr 14, 2009 at 7:05 AM, Tim Kaufmann <tim@timkaufmann.de>
wrote:
> Conclusion: There''s a problem in the gplpv scsi and/or vbd drivers
and/or in
> the combination of those with my Xen-Setup. What can I do now?
It IS possible that the new GPLPV version has new bugs in them. In
that case James usually wants to know:
- What OS and Xen version, installed from packaged or self-compiled
(this is a new thread, so you should also post the info here)
- did you try Linux HVM with PV drivers? How is disk and network
performance there?

Worth to try:
- try older version :
http://meadowcourt.org/downloads/Xen%20PV%20Drivers%200.9.12-pre13.exe
- try /PATCHTPR :
http://www.nabble.com/New-version-of-GPL-PV-drivers-for-Windows-0.10.0.47-td22867090.html
- testing Windows2003

I''m still using 0.9.12-pre13 with both Windows 2003 and XP, both worked
great.

Regards,

Fajar

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

> It IS possible that the new GPLPV version has new bugs in them. In
> that case James usually wants to know:
> - What OS
Ubuntu 8.10 64 Bit
> and Xen version
root@automatix:~# dpkg -l | grep xen
ii  libxen3                               
3.3.0-1ubuntu7                          library interface for Xen, a  
Virtual Machine Monitor
ii  linux-xen0-2.6.27.5                   
2.6.27.5-10.00.Custom                   Linux xen kernel binary image  
for version 2.6.27.5
ii  python-xen-3.3                        
3.3.0-1ubuntu7                          python bindings for Xen, a  
Virtual Machine Monitor
ii  ubuntu-xen-server                     
0.0.1-2ubuntu10                         Xen software for running on  
servers
ii  xen-docs-3.3                          
3.3.0-1ubuntu7                          documentation for XEN, a  
Virtual Machine Monitor
ii  xen-hypervisor-3.3                    
3.3.0-1ubuntu7                          The Xen Hypervisor for i386  
and amd64.
ii  xen-shell                             
1.8-3                                   Console based Xen  
administration utility
ii  xen-tools                             
3.9-3                                   Tools to manage Debian XEN  
virtual servers
ii  xen-utils-3.3                         
3.3.0-1ubuntu7                          XEN administrative tools
> , installed from packaged
yes
> - did you try Linux HVM with PV drivers? How is disk and network
> performance there?
not yet
> Worth to try:
> - try older version :
> http://meadowcourt.org/downloads/Xen%20PV%20Drivers%200.9.12-pre13.exe
Even slower, dd with 3.1 MB/s
> - try /PATCHTPR :
>
http://www.nabble.com/New-version-of-GPL-PV-drivers-for-Windows-0.10.0.47-td22867090.html
Bluescreen on boot
> - testing Windows2003
n.a.

I need to make up my mind on where to go from here (try another  
distribution, compiling XEN myself, abandon Xen ...).

Tim



Hardware
=======Asus P5Q-EM DO (Intel Q45 Chipset with VT-d)
Intel Core 2 Quad Q9550 (E0), 4x 2.83GHz
8 GB RAM
latest Bios, not overclocked
5 x Western Digital RE3 1000GB, SATA II (WD1002FBYS) connected to  
onbord SATA

domO
====Ubuntu 8.10 with linux-xen0-2.6.27.5 (hg checkout), xfce, convirt
/boot with 500 MB on RAID 1 over all 5 drives
swap with 2 GB on each of the 5 drives
LVM over RAID 5 over the remaining space of the 5 drives, / on logical  
volume

domU
====root@automatix:~# cat /var/cache/convirt/vm_configs/XP-Test-LVM
# Automtically generated by ConVirt
import os, re
arch=os.uname()[4]
if re.search(''64'', arch):
    arch_libdir = ''lib64''
else:
    arch_libdir = ''lib''


name=''XP-Test-LVM''

kernel=''/usr/lib/xen/boot/hvmloader''
builder=''hvm''


memory=512
shadow_memory=10
#vcpus=1
#cpus = "0"        # all vcpus run on CPU0

pae=1
acpi=0
apic=0

vif=[''mac=00:16:3e:44:65:6f, bridge=xenbr0'']
#vif=['''']
disk=[''phy:raidvg/XP-Test-LVM.disk.xm,hda,w'',
''file:/var/cache/convirt/
vm_disks/winxpprof.iso,hdc:cdrom,r'']
device_model=''/usr/'' + arch_libdir +
''/xen/bin/qemu-dm''

# Boots from CDROM.
# Change to ''c'' after windows installation in order to boot
from disk.
boot=''d''
#boot=''c''

sdl=0
vnc=1
vncunused=1
stdvga=0
extra=''''
on_reboot=''restart''
on_shutdown=''destroy''
ramdisk=''''
image_name=''Windows_CD_Install_LVM''
on_crash=''restart''
bootloader=''''
vcpus=1
root=''''
platform=''xen''
network_mode=''user''
usb=1
usbdevice=''tablet''

STORAGE_STATS={''DISK_STATS'':
{''/var/cache/convirt/vm_disks/
winxpprof.iso'': {''DEV_TYPE'':
''FILE'', ''IS_LOCAL'': True,
''DISK_SIZE'':
638042112, ''DISK_NAME'':
''/var/cache/convirt/vm_disks/winxpprof.iso''},
''/dev/raidvg/XP-Test-LVM.disk.xm'':
{''DEV_TYPE'': ''BLOCK'',
''IS_LOCAL'':
True, ''DISK_SIZE'': 20971520000, ''DISK_NAME'':
''/dev/raidvg/XP-Test-
LVM.disk.xm''}}, ''LOCAL_ALLOCATION'': 21609562112,
''SHARED_ALLOCATION'': 0}
image_id=''d500a710e92058067521fbe7063de445''
image_conf=''/var/log/convirt/image_store/Windows_CD_Install_LVM/ 
Windows_CD_Install_LVM_XP-Test-LVM_image.conf''
uuid=''7f5b9160-dda6-56e5-1ba0-2071e6ceb778''

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

On Sun, Apr 19, 2009 at 8:37 AM, Tim Kaufmann <tim@timkaufmann.de>
wrote:
>> - did you try Linux HVM with PV drivers? How is disk and network
>> performance there?
>
> not yet
Is there a particular purpose for you to resend your email without any
additional info?
IMHO testing Linux HVM with PV driver is one way to determine where
the problem is.

If Linux HVM with PV drivers doesn''t work or have low performance,
then it''s unlilkely GPLPV will perform better. If this is the case
then most likely your setup (or Ubuntu packages) is at fault.

If Linux HVM with PV drivers work well but GPLPV does not work or have
low performance, then possibly the bug is in GPLPV. From my experince
so far this is unlikely to happen though (at least not with Windows XP
and 2003 32bit domU).

Sorry I can''t help you more. If you''re still stuck you might
have
better luck with other distro (like RHEL/Centos) or other
virtualization products (preferably one with commercial support, so
you can complain to their tech support and receive immediate response
:) )

Regards,

Fajar

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

hello! can u advise where to find those linux pv drivers for hvm domu?

19 апр. 2009, в 11:34, Fajar A. Nugraha написал(а):
> On Sun, Apr 19, 2009 at 8:37 AM, Tim Kaufmann <tim@timkaufmann.de>  
> wrote:
>>> - did you try Linux HVM with PV drivers? How is disk and network
>>> performance there?
>>
>> not yet
>
> Is there a particular purpose for you to resend your email without any
> additional info?
> IMHO testing Linux HVM with PV driver is one way to determine where
> the problem is.
>
> If Linux HVM with PV drivers doesn''t work or have low performance,
> then it''s unlilkely GPLPV will perform better. If this is the case
> then most likely your setup (or Ubuntu packages) is at fault.
>
> If Linux HVM with PV drivers work well but GPLPV does not work or have
> low performance, then possibly the bug is in GPLPV. From my experince
> so far this is unlikely to happen though (at least not with Windows XP
> and 2003 32bit domU).
>
> Sorry I can''t help you more. If you''re still stuck you
might have
> better luck with other distro (like RHEL/Centos) or other
> virtualization products (preferably one with commercial support, so
> you can complain to their tech support and receive immediate response
> :) )
>
> Regards,
>
> Fajar
>
> _______________________________________________
> 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

2009/4/19 Vladislav Karpenko
<vladislav@karpenko.od.ua>:
> hello! can u advise where to find those linux pv drivers for hvm domu?
Depends on your distro.
RHEL/Centos 5.3 has it built in. The module name is usually xen-vbd
(for disk) and xen-net or xen-vnif for network.

Regards,

Fajar

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

but for suse and debian lenny where to find?

19 ÁÐÒ. 2009, × 11:50, Fajar A. Nugraha ÎÁÐÉÓÁÌ(Á):
> 2009/4/19 Vladislav Karpenko <vladislav@karpenko.od.ua>:
>> hello! can u advise where to find those linux pv drivers for hvm  
>> domu?
>
> Depends on your distro.
> RHEL/Centos 5.3 has it built in. The module name is usually xen-vbd
> (for disk) and xen-net or xen-vnif for network.
>
> Regards,
>
> Fajar
>
> _______________________________________________
> 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 Sun, Apr 19, 2009 at 4:06 PM, Vladislav Karpenko
<vladislav@karpenko.od.ua> wrote:
> but for suse and debian lenny where to find?
Well, the source is on xen source tarball
http://www.nabble.com/How-to-use-the-PV-driver-for-Linux-HVM-domU--td20220170.html

If you''re looking for a compiled ready-to-use version, you might have
more luck from suse or debian users.

Regards,

Fajar

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

On Sun, Apr 19, 2009 at 7:14 PM, Tim Kaufmann <tk@taquiri.de>
wrote:
>
> Am 19.04.2009 um 10:34 schrieb Fajar A. Nugraha:
>
>> Is there a particular purpose for you to resend your email without any
>> additional info?
>
> Yes - only you received that mail as my reply to the list got killed
because
> I sent it from the wrong account.
Ah, I see.
Note that you sent this mail from tk@taquiri.de, which is the same
account you used when you said "sent it from the wrong account". A
mistake, or have you subscribe this account as well?
> Testing XP on LVM (with and without the latest gplpv driver) gave the same
> results I had with Ubuntu.
>
> So I installed CentOS 5.3 to a HVM (1 vCPU, 512 MB RAM, LVM with 20 GB). It
> came up with the pv drivers right after installation - nice. But the
results
> of the dd-test (with a 16 GB File) were rather disappointing. Two tests
> showed 86 and 91 MB/s.
86 MB/s from the original almost 200 MB/s is actually quite good for a
HVM domU. My results so far seems to indicate that PV disk performance
is close to dom0, while HVM with PV drivers about half of it.

I don''t understand why your Windows numbers is so low though.
I''m out of ideas.

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

Am 19.04.2009 um 10:34 schrieb Fajar A. Nugraha:
> Is there a particular purpose for you to resend your email without any
> additional info?
Yes - only you received that mail as my reply to the list got killed  
because I sent it from the wrong account.

In the meantime, I tried CentOS 5.3, but it locked up the pc when  
starting X. So I setup OpenSuse 11.1 with the packaged Xen 3.3.1.  
Tests with dd gave more or less the same results as in Ubuntu, 196 MB/ 
s instead of a little more than 200 in Ubuntu.

Testing XP on LVM (with and without the latest gplpv driver) gave the  
same results I had with Ubuntu.

So I installed CentOS 5.3 to a HVM (1 vCPU, 512 MB RAM, LVM with 20  
GB). It came up with the pv drivers right after installation - nice.  
But the results of the dd-test (with a 16 GB File) were rather  
disappointing. Two tests showed 86 and 91 MB/s.

Tim


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

Dear All, 

I am facing an issue while the startup of a domU centos5-2 image obtained
from jailtime.org on RHEL dom0 system. 
Initially there were problems locating the root file system and then I did a
mkinitrd with xennet and xenblk option and changed the ramdisk in xen config
file. With this addition I was able to get rid of the kernel panic error,
but now the system freezes after initializing service ''sshd'',
below is the
log at the boot time:

Using config file "./centos.5-2.xen3.cfg".
Started domain centos.5-2
Bootdata ok (command line is  root=/dev/sda1 ro)
Linux version 2.6.18-128.1.6.el5xen (mockbuild@ls20-bc2-14.build.redhat.com)
(gcc version 4.1.2 20080704 (Red Hat 4.1.2-44)) #1 SMP Tue Mar 24 12:28:27
EDT 2009
BIOS-provided physical RAM map:
 Xen: 0000000000000000 - 0000000010800000 (usable)
No mptable found.
Built 1 zonelists.  Total pages: 67584
Kernel command line:  root=/dev/sda1 ro
Initializing CPU#0
PID hash table entries: 2048 (order: 11, 16384 bytes)
Xen reported: 2613.392 MHz processor.
Console: colour dummy device 80x25
Dentry cache hash table entries: 65536 (order: 7, 524288 bytes)
Inode-cache hash table entries: 32768 (order: 6, 262144 bytes)
Software IO TLB disabled
Memory: 242476k/270336k available (2447k kernel code, 19356k reserved, 1366k
data, 180k init)
Calibrating delay using timer specific routine.. 6536.43 BogoMIPS
(lpj=13072865)
Security Framework v1.0.0 initialized
SELinux:  Initializing.
selinux_register_security:  Registering secondary module capability
Capability LSM initialized as secondary
Mount-cache hash table entries: 256
CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line)
CPU: L2 Cache: 1024K (64 bytes/line)
(SMP-)alternatives turned off
Brought up 1 CPUs
checking if image is initramfs... it is
Grant table initialized
NET: Registered protocol family 16
ACPI Exception (utmutex-0262): AE_BAD_PARAMETER, Thread 1F7A0 could not
acquire Mutex [2] [20060707]
No dock devices found.
ACPI Exception (utmutex-0262): AE_BAD_PARAMETER, Thread 1F7A0 could not
acquire Mutex [2] [20060707]
Brought up 1 CPUs
PCI: setting up Xen PCI frontend stub
ACPI: Interpreter disabled.
Linux Plug and Play Support v0.97 (c) Adam Belay
pnp: PnP ACPI: disabled
xen_mem: Initialising balloon driver.
usbcore: registered new driver usbfs
usbcore: registered new driver hub
PCI: System does not support PCI
PCI: System does not support PCI
NetLabel: Initializing
NetLabel:  domain hash size = 128
NetLabel:  protocols = UNLABELED CIPSOv4
NetLabel:  unlabeled traffic allowed by default
NET: Registered protocol family 2
IP route cache hash table entries: 4096 (order: 3, 32768 bytes)
TCP established hash table entries: 16384 (order: 6, 262144 bytes)
TCP bind hash table entries: 8192 (order: 5, 131072 bytes)
TCP: Hash tables configured (established 16384 bind 8192)
TCP reno registered
audit: initializing netlink socket (disabled)
type=2000 audit(1240189270.002:1): initialized
VFS: Disk quotas dquot_6.5.1
Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
Initializing Cryptographic API
alga: No test for crc32c (crc32c-generic)
ksign: Installing public key data
Loading keyring
- Added public key 369DB9F7335D033D
- User ID: Red Hat, Inc. (Kernel Module GPG key)
io scheduler noop registered
io scheduler anticipatory registered
io scheduler deadline registered
io scheduler cfq registered (default)
pci_hotplug: PCI Hot Plug PCI Core version: 0.5
rtc: IRQ 8 is not free.
Non-volatile memory driver v1.2
Linux agpgart interface v0.101 (c) Dave Jones
RAMDISK driver initialized: 16 RAM disks of 16384K size 4096 blocksize
Xen virtual console successfully installed as xvc0
Bootdata ok (command line is  root=/dev/sda1 ro)
Linux version 2.6.18-128.1.6.el5xen (mockbuild@ls20-bc2-14.build.redhat.com)
(gcc version 4.1.2 20080704 (Red Hat 4.1.2-44)) #1 SMP Tue Mar 24 12:28:27
EDT 2009
BIOS-provided physical RAM map:
 Xen: 0000000000000000 - 0000000010800000 (usable)
No mptable found.
Built 1 zonelists.  Total pages: 67584
Kernel command line:  root=/dev/sda1 ro
Initializing CPU#0
PID hash table entries: 2048 (order: 11, 16384 bytes)
Xen reported: 2613.392 MHz processor.
Console: colour dummy device 80x25
Dentry cache hash table entries: 65536 (order: 7, 524288 bytes)
Inode-cache hash table entries: 32768 (order: 6, 262144 bytes)
Software IO TLB disabled
Memory: 242476k/270336k available (2447k kernel code, 19356k reserved, 1366k
data, 180k init)
Calibrating delay using timer specific routine.. 6536.43 BogoMIPS
(lpj=13072865)
Security Framework v1.0.0 initialized
SELinux:  Initializing.
selinux_register_security:  Registering secondary module capability
Capability LSM initialized as secondary
Mount-cache hash table entries: 256
CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line)
CPU: L2 Cache: 1024K (64 bytes/line)
(SMP-)alternatives turned off
Brought up 1 CPUs
checking if image is initramfs... it is
Grant table initialized
NET: Registered protocol family 16
ACPI Exception (utmutex-0262): AE_BAD_PARAMETER, Thread 1F7A0 could not
acquire Mutex [2] [20060707]
No dock devices found.
ACPI Exception (utmutex-0262): AE_BAD_PARAMETER, Thread 1F7A0 could not
acquire Mutex [2] [20060707]
Brought up 1 CPUs
PCI: setting up Xen PCI frontend stub
ACPI: Interpreter disabled.
Linux Plug and Play Support v0.97 (c) Adam Belay
pnp: PnP ACPI: disabled
xen_mem: Initialising balloon driver.
usbcore: registered new driver usbfs
usbcore: registered new driver hub
PCI: System does not support PCI
PCI: System does not support PCI
NetLabel: Initializing
NetLabel:  domain hash size = 128
NetLabel:  protocols = UNLABELED CIPSOv4
NetLabel:  unlabeled traffic allowed by default
NET: Registered protocol family 2
IP route cache hash table entries: 4096 (order: 3, 32768 bytes)
TCP established hash table entries: 16384 (order: 6, 262144 bytes)
TCP bind hash table entries: 8192 (order: 5, 131072 bytes)
TCP: Hash tables configured (established 16384 bind 8192)
TCP reno registered
audit: initializing netlink socket (disabled)
type=2000 audit(1240189270.002:1): initialized
VFS: Disk quotas dquot_6.5.1
Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
Initializing Cryptographic API
alg: No test for crc32c (crc32c-generic)
ksign: Installing public key data
Loading keyring
- Added public key 369DB9F7335D033D
- User ID: Red Hat, Inc. (Kernel Module GPG key)
io scheduler noop registered
io scheduler anticipatory registered
io scheduler deadline registered
io scheduler cfq registered (default)
pci_hotplug: PCI Hot Plug PCI Core version: 0.5
rtc: IRQ 8 is not free.
Non-volatile memory driver v1.2
Linux agpgart interface v0.101 (c) Dave Jones
RAMDISK driver initialized: 16 RAM disks of 16384K size 4096 blocksize
Xen virtual console successfully installed as xvc0
Event-channel device installed.
Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
ide: Assuming 50MHz system bus speed for PIO modes; override with idebus=xx
ide-floppy driver 0.99.newide
usbcore: registered new driver hiddev
usbcore: registered new driver usbhid
drivers/usb/input/hid-core.c: v2.6:USB HID core driver
PNP: No PS/2 controller found. Probing ports directly.
i8042.c: No controller found.
mice: PS/2 mouse device common for all mice
md: md driver 0.90.3 MAX_MD_DEVS=256, MD_SB_DISKS=27
md: bitmap version 4.39
TCP bic registered
Initializing IPsec netlink socket
NET: Registered protocol family 1
NET: Registered protocol family 17
XENBUS: Device with no driver: device/vbd/2049
XENBUS: Device with no driver: device/vif/0
Write protecting the kernel read-only data: 467k
Red Hat nash version 5.1.19.6 starting
Mounting proc filesystem
Mounting sysfs filesystem
Creating /dev
Creating initial device nodes
Setting up hotplug.
Creating block device nodes.
Loading xenblk.ko module
Registering block device major 8
Loading ehci-hcd.ko module
Loading ohci-hcd.ko module
Loading uhci-hcd.ko module
USB Universal Host Controller Interface driver v3.0
Loading jbd.ko module
Loading ext3.ko module
Loading scsi_mod.ko module
SCSI subsystem initialized
Loading sd_mod.ko module
register_blkdev: cannot get major 8 for sd
Loading libata.ko module
Loading sata_nv.ko module
Loading dm-mod.ko module
device-mapper: uevent: version 1.0.3
device-mapper: ioctl: 4.11.5-ioctl (2007-12-12) initialised:
dm-devel@redhat.com
Loading dm-log.ko module
Loading dm-mirror.ko module
Loading dm-zero.ko module
Loading dm-snapshot.ko module
Loading dm-mem-cache.ko module
Loading dm-region_hash.ko module
Loading dm-message.ko module
Loading dm-raid45.ko module
device-mapper: dm-raid45: initialized v0.2429
Loading xennet.ko module
netfront: Initialising virtual ethernet driver.
netfront: device eth0 has flipping receive path.
Waiting for driver initialization.
Scanning and configuring dmraid supported devices
Scanning logical volumes
  Reading all physical volumes.  This may take a while...
Activating logical volumes
  Volume group "VolGroup00" not found
Creating root device.
Mounting root filesystem.
EXT3-fs: INFO: recovery required on readonly filesystem.
EXT3-fs: write access will be enabled during recovery.
kjournald starting.  Commit interval 5 seconds
EXT3-fs: recovery complete.
EXT3-fs: mounted filesystem with ordered data mode.
Setting up other filesystems.
Setting up new root fs
no fstab.sys, mounting internal defaults
Switching to new root and running init.
unmounting old /dev
unmounting old /proc
unmounting old /sys
INIT: version 2.86 booting
                Welcome to  CentOS release 5.2 (Final)
                Press ''I'' to enter interactive startup.
Setting clock : Sun Apr 19 21:01:37 EDT 2009 [  OK  ]
Starting udev: [  OK  ]
Setting hostname localhost.localdomain:  [  OK  ]
Checking filesystems
Checking all file systems.
[/sbin/fsck.ext3 (1) -- /] fsck.ext3 -a /dev/sda1 
/dev/sda1: clean, 14930/256512 files, 94797/512256 blocks
[  OK  ]
Remounting root filesystem in read-write mode:  [  OK  ]
Mounting local filesystems:  [  OK  ]
Enabling /etc/fstab swaps:  [  OK  ]
INIT: Entering runlevel: 3
Entering non-interactive startup
Bringing up loopback interface:  [  OK  ]
Bringing up interface eth0:  [  OK  ]
Starting system logger: [  OK  ]
Starting kernel logger: [  OK  ]
Starting sshd: [  OK  ]

My xen configuration file is as below:
kernel = "/boot/vmlinuz-2.6.18-128.1.6.el5xen"
ramdisk = "../initrd-2.6.18-128.1.6.el5xen.img"
memory = 256
name = "centos.5-2"
vif = [ ''bridge=xenbr0'' ]
dhcp = "off"
disk = [''file:/root/images/centos/centos.5-2.img,sda1,w'']
root = "/dev/sda1 ro"

I have tried to google solution for this problem, but no luck till this
moment. Please suggest me what can be done to boot up by domU kernel.


Thanks for your support!

Regards,
Ata




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

On Mon, Apr 20, 2009 at 11:08 AM, Ata E Husain Bohra
<aehusain@buffalo.edu> wrote:
> Dear All,
>
> I am facing an issue while the startup of a domU centos5-2 image obtained
> from jailtime.org on RHEL dom0 system.
> Initially there were problems locating the root file system and then I did
a
> mkinitrd with xennet and xenblk option and changed the ramdisk in xen
config
> file. With this addition I was able to get rid of the kernel panic error,
> but now the system freezes after initializing service
''sshd'', below is the
> log at the boot time:
> Starting sshd: [  OK  ]
My guess is domU is already started. You just didn''t see the login
screen.
>
> My xen configuration file is as below:
> kernel = "/boot/vmlinuz-2.6.18-128.1.6.el5xen"
> ramdisk = "../initrd-2.6.18-128.1.6.el5xen.img"
> memory = 256
> name = "centos.5-2"
> vif = [ ''bridge=xenbr0'' ]
> dhcp = "off"
> disk = [''file:/root/images/centos/centos.5-2.img,sda1,w'']
> root = "/dev/sda1 ro"
>
> I have tried to google solution for this problem, but no luck till this
> moment. Please suggest me what can be done to boot up by domU kernel.
There are some alternatives to fix it. My perefered method would be to
setup domU correctly to display login screen an allow root to login
from xvc0 (which is where the console is. See the boot log). It
requires some modifications to several files.

Other people like to simply add
extra ="3 xencons=tty"
to domU config line.

See the list archive: http://www.nabble.com/xm-console-hanging-td22906416.html

Regards,

Fajar

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

Dear Fajar, 

I tried your suggestion, but there are more interesting observations. If I
edit my config file to include extra ="3 xencons=tty", the domU still
hangs
and this time the debug messages are:
-------------------------------------------------
Using config file "./centos.5-2.xen3.cfg".
Started domain centos.5-2
Bootdata ok (command line is  root=/dev/sda1 ro 3 xencons=tty)
Linux version 2.6.18-128.1.6.el5xen (mockbuild@ls20-bc2-14.build.redhat.com)
(gcc version 4.1.2 20080704 (Red Hat 4.1.2-44)) #1 SMP Tue Mar 24 12:28:27
EDT 2009
BIOS-provided physical RAM map:
 Xen: 0000000000000000 - 0000000010800000 (usable)
No mptable found.
Built 1 zonelists.  Total pages: 67584
Kernel command line:  root=/dev/sda1 ro 3 xencons=tty
Initializing CPU#0
PID hash table entries: 2048 (order: 11, 16384 bytes)
Xen reported: 2613.388 MHz processor.
Console: colour dummy device 80x25
Dentry cache hash table entries: 65536 (order: 7, 524288 bytes)
Inode-cache hash table entries: 32768 (order: 6, 262144 bytes)
Software IO TLB disabled
Memory: 242476k/270336k available (2447k kernel code, 19356k reserved, 1366k
data, 180k init)
Calibrating delay using timer specific routine.. 6536.19 BogoMIPS
(lpj=13072393)
Security Framework v1.0.0 initialized
SELinux:  Initializing.
selinux_register_security:  Registering secondary module capability
Capability LSM initialized as secondary
Mount-cache hash table entries: 256
CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line)
CPU: L2 Cache: 1024K (64 bytes/line)
(SMP-)alternatives turned off
Brought up 1 CPUs
checking if image is initramfs... it is
Grant table initialized
NET: Registered protocol family 16
ACPI Exception (utmutex-0262): AE_BAD_PARAMETER, Thread 1F7A0 could not
acquire Mutex [2] [20060707]
No dock devices found.
ACPI Exception (utmutex-0262): AE_BAD_PARAMETER, Thread 1F7A0 could not
acquire Mutex [2] [20060707]
Brought up 1 CPUs
PCI: setting up Xen PCI frontend stub
ACPI: Interpreter disabled.
Linux Plug and Play Support v0.97 (c) Adam Belay
pnp: PnP ACPI: disabled
xen_mem: Initialising balloon driver.
usbcore: registered new driver usbfs
usbcore: registered new driver hub
PCI: System does not support PCI
PCI: System does not support PCI
NetLabel: Initializing
NetLabel:  domain hash size = 128
NetLabel:  protocols = UNLABELED CIPSOv4
NetLabel:  unlabeled traffic allowed by default
NET: Registered protocol family 2
IP route cache hash table entries: 4096 (order: 3, 32768 bytes)
TCP established hash table entries: 16384 (order: 6, 262144 bytes)
TCP bind hash table entries: 8192 (order: 5, 131072 bytes)
TCP: Hash tables configured (established 16384 bind 8192)
TCP reno registered
audit: initializing netlink socket (disabled)
type=2000 audit(1240248153.098:1): initialized
VFS: Disk quotas dquot_6.5.1
Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
Initializing Cryptographic API
alg: No test for crc32c (crc32c-generic)
ksign: Installing public key data
Loading keyring
- Added public key 369DB9F7335D033D
- User ID: Red Hat, Inc. (Kernel Module GPG key)
io scheduler noop registered
io scheduler anticipatory registered
io scheduler deadline registered
io scheduler cfq registered (default)
pci_hotplug: PCI Hot Plug PCI Core version: 0.5
rtc: IRQ 8 is not free.
Non-volatile memory driver v1.2
Linux agpgart interface v0.101 (c) Dave Jones
RAMDISK driver initialized: 16 RAM disks of 16384K size 4096 blocksize
WARNING: Failed to register Xen virtual console driver as
''tty1''
Event-channel device installed.
Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
ide: Assuming 50MHz system bus speed for PIO modes; override with idebus=xx
ide-floppy driver 0.99.newide
usbcore: registered new driver hiddev
usbcore: registered new driver usbhid
drivers/usb/input/hid-core.c: v2.6:USB HID core driver
PNP: No PS/2 controller found. Probing ports directly.
i8042.c: No controller found.
mice: PS/2 mouse device common for all mice
md: md driver 0.90.3 MAX_MD_DEVS=256, MD_SB_DISKS=27
md: bitmap version 4.39
TCP bic registered
Initializing IPsec netlink socket
NET: Registered protocol family 1
NET: Registered protocol family 17
XENBUS: Device with no driver: device/vbd/2049
XENBUS: Device with no driver: device/vbd/2050
XENBUS: Device with no driver: device/vif/0
Write protecting the kernel read-only data: 467k
Registering block device major 8
USB Universal Host Controller Interface driver v3.0
SCSI subsystem initialized
register_blkdev: cannot get major 8 for sd
device-mapper: uevent: version 1.0.3
device-mapper: ioctl: 4.11.5-ioctl (2007-12-12) initialised:
dm-devel@redhat.com
device-mapper: dm-raid45: initialized v0.2429
netfront: Initialising virtual ethernet driver.
netfront: device eth0 has flipping receive path.
kjournald starting.  Commit interval 5 seconds
EXT3-fs: mounted filesystem with ordered data mode.
md: stopping all md devices.
System halted.
[root@steelbug centos]# mount -o loop centos.5-2.img /tmp/
[root@steelbug centos]# vi /tmp/etc/inittab 
[root@steelbug centos]# 
[root@steelbug centos]# umount /tmp/
[root@steelbug centos]# xm create -c centos.5-2.xen3.cfg vmid=1
Using config file "./centos.5-2.xen3.cfg".
Started domain centos.5-2
Bootdata ok (command line is  root=/dev/sda1 ro 3 xencons=tty)
Linux version 2.6.18-128.1.6.el5xen (mockbuild@ls20-bc2-14.build.redhat.com)
(gcc version 4.1.2 20080704 (Red Hat 4.1.2-44)) #1 SMP Tue Mar 24 12:28:27
EDT 2009
BIOS-provided physical RAM map:
 Xen: 0000000000000000 - 0000000010800000 (usable)
No mptable found.
Built 1 zonelists.  Total pages: 67584
Kernel command line:  root=/dev/sda1 ro 3 xencons=tty
Initializing CPU#0
PID hash table entries: 2048 (order: 11, 16384 bytes)
Xen reported: 2613.388 MHz processor.
Console: colour dummy device 80x25
Dentry cache hash table entries: 65536 (order: 7, 524288 bytes)
Inode-cache hash table entries: 32768 (order: 6, 262144 bytes)
Software IO TLB disabled
Memory: 242476k/270336k available (2447k kernel code, 19356k reserved, 1366k
data, 180k init)
Calibrating delay using timer specific routine.. 6536.22 BogoMIPS
(lpj=13072456)
Security Framework v1.0.0 initialized
SELinux:  Initializing.
selinux_register_security:  Registering secondary module capability
Capability LSM initialized as secondary
Mount-cache hash table entries: 256
CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line)
CPU: L2 Cache: 1024K (64 bytes/line)
(SMP-)alternatives turned off
Brought up 1 CPUs
checking if image is initramfs... it is
Grant table initialized
NET: Registered protocol family 16
ACPI Exception (utmutex-0262): AE_BAD_PARAMETER, Thread 1F7A0 could not
acquire Mutex [2] [20060707]
No dock devices found.
ACPI Exception (utmutex-0262): AE_BAD_PARAMETER, Thread 1F7A0 could not
acquire Mutex [2] [20060707]
Brought up 1 CPUs
PCI: setting up Xen PCI frontend stub
ACPI: Interpreter disabled.
Linux Plug and Play Support v0.97 (c) Adam Belay
pnp: PnP ACPI: disabled
xen_mem: Initialising balloon driver.
usbcore: registered new driver usbfs
usbcore: registered new driver hub
PCI: System does not support PCI
PCI: System does not support PCI
NetLabel: Initializing
NetLabel:  domain hash size = 128
NetLabel:  protocols = UNLABELED CIPSOv4
NetLabel:  unlabeled traffic allowed by default
NET: Registered protocol family 2
IP route cache hash table entries: 4096 (order: 3, 32768 bytes)
TCP established hash table entries: 16384 (order: 6, 262144 bytes)
TCP bind hash table entries: 8192 (order: 5, 131072 bytes)
TCP: Hash tables configured (established 16384 bind 8192)
TCP reno registered
audit: initializing netlink socket (disabled)
type=2000 audit(1240248370.103:1): initialized
VFS: Disk quotas dquot_6.5.1
Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
Initializing Cryptographic API
alg: No test for crc32c (crc32c-generic)
ksign: Installing public key data
Loading keyring
- Added public key 369DB9F7335D033D
- User ID: Red Hat, Inc. (Kernel Module GPG key)
io scheduler noop registered
io scheduler anticipatory registered
io scheduler deadline registered
io scheduler cfq registered (default)
pci_hotplug: PCI Hot Plug PCI Core version: 0.5
rtc: IRQ 8 is not free.
Non-volatile memory driver v1.2
Linux agpgart interface v0.101 (c) Dave Jones
RAMDISK driver initialized: 16 RAM disks of 16384K size 4096 blocksize
WARNING: Failed to register Xen virtual console driver as
''tty1''
Event-channel device installed.
Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
ide: Assuming 50MHz system bus speed for PIO modes; override with idebus=xx
ide-floppy driver 0.99.newide
usbcore: registered new driver hiddev
usbcore: registered new driver usbhid
drivers/usb/input/hid-core.c: v2.6:USB HID core driver
PNP: No PS/2 controller found. Probing ports directly.
i8042.c: No controller found.
mice: PS/2 mouse device common for all mice
md: md driver 0.90.3 MAX_MD_DEVS=256, MD_SB_DISKS=27
md: bitmap version 4.39
TCP bic registered
Initializing IPsec netlink socket
NET: Registered protocol family 1
NET: Registered protocol family 17
XENBUS: Device with no driver: device/vbd/2049
XENBUS: Device with no driver: device/vbd/2050
XENBUS: Device with no driver: device/vif/0
Write protecting the kernel read-only data: 467k
Registering block device major 8
USB Universal Host Controller Interface driver v3.0
SCSI subsystem initialized
register_blkdev: cannot get major 8 for sd
device-mapper: uevent: version 1.0.3
device-mapper: ioctl: 4.11.5-ioctl (2007-12-12) initialised:
dm-devel@redhat.com
device-mapper: dm-raid45: initialized v0.2429
netfront: Initialising virtual ethernet driver.
netfront: device eth0 has flipping receive path.
kjournald starting.  Commit interval 5 seconds
EXT3-fs: mounted filesystem with ordered data mode.
------------------------------------------------------

Then I tried to google more and found a web link which was about centos (but
worked for ubuntu too), 

http://www.howtoforge.com/create-centos5.2-domu-on-ubuntu-hardy-dom0 

It instructs to edit the initab (event.d/tty1 in ubuntu) to make runlevel1
thread to respwan with argument as "console" than "tty1". I
also had to
remove 
"extra" argument from the xen config file. With these two changes I am
able
to get to the login prompt. 

Please share if there is a reason for this behavior.

Thanks!
Ata 

-----Original Message-----
From: xen-users-bounces@lists.xensource.com
[mailto:xen-users-bounces@lists.xensource.com] On Behalf Of Fajar A. Nugraha
Sent: Sunday, April 19, 2009 11:19 PM
To: Xen Users
Subject: Re: [Xen-users] Dom U stuck at boot time- centos.5-2 domU image on
RHEL5 dom0!

On Mon, Apr 20, 2009 at 11:08 AM, Ata E Husain Bohra
<aehusain@buffalo.edu> wrote:
> Dear All,
>
> I am facing an issue while the startup of a domU centos5-2 image obtained
> from jailtime.org on RHEL dom0 system.
> Initially there were problems locating the root file system and then I did
a
> mkinitrd with xennet and xenblk option and changed the ramdisk in xen
config
> file. With this addition I was able to get rid of the kernel panic error,
> but now the system freezes after initializing service
''sshd'', below is the
> log at the boot time:
> Starting sshd: [  OK  ]
My guess is domU is already started. You just didn''t see the login
screen.
>
> My xen configuration file is as below:
> kernel = "/boot/vmlinuz-2.6.18-128.1.6.el5xen"
> ramdisk = "../initrd-2.6.18-128.1.6.el5xen.img"
> memory = 256
> name = "centos.5-2"
> vif = [ ''bridge=xenbr0'' ]
> dhcp = "off"
> disk = [''file:/root/images/centos/centos.5-2.img,sda1,w'']
> root = "/dev/sda1 ro"
>
> I have tried to google solution for this problem, but no luck till this
> moment. Please suggest me what can be done to boot up by domU kernel.
There are some alternatives to fix it. My perefered method would be to
setup domU correctly to display login screen an allow root to login
from xvc0 (which is where the console is. See the boot log). It
requires some modifications to several files.

Other people like to simply add
extra ="3 xencons=tty"
to domU config line.

See the list archive:
http://www.nabble.com/xm-console-hanging-td22906416.html

Regards,

Fajar

_______________________________________________
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 Tue, Apr 21, 2009 at 4:20 AM, Ata E Husain Bohra
<aehusain@buffalo.edu> wrote:
> Dear Fajar,
>
> I tried your suggestion, but there are more interesting observations. If I
> edit my config file to include extra ="3 xencons=tty", the domU
still hangs
probably because of this
> WARNING: Failed to register Xen virtual console driver as
''tty1''
> Then I tried to google more and found a web link which was about centos
(but
> worked for ubuntu too),
>
> http://www.howtoforge.com/create-centos5.2-domu-on-ubuntu-hardy-dom0
>
> It instructs to edit the initab (event.d/tty1 in ubuntu) to make runlevel1
> thread to respwan with argument as "console" than
"tty1". I also had to
> remove
> "extra" argument from the xen config file. With these two changes
I am able
> to get to the login prompt.
>
> Please share if there is a reason for this behavior.
Had you read the link I set you thoroughly, you''d have seen my
suggestion on that thread. This message in particular should answer
your question

http://www.nabble.com/Re%3A-xm-console-hanging-p22909793.html

It seems that you can replace "xvc0" with "console" and get
the same
result (at least on Centos).
In Ian''s case, he prefer to add "xencons=tty" (which worked
for him),
while in your case editing xencons didn''t work. Probably
distro-specific issue (suse vs RHEL/Centos).

Regards,

Fajar

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