Xen users - Mar 2008 - how to use prebuilt images from jailtime.org?

Hi

Does anyone know how to use the images from http://www.jailtime.org/? 
I''ve downloaded the CentOS 5.1 
(http://www.jailtime.org/download:centos:v5.1) to my CentOS 5.1 x64 Xen 
3.1 server, and unpacked it to my /home folder.

Then I took the included config file, centos.5-1.xen3.cfg and copied it 
to /xen - and modified to my needs:

[root@gimbli home]# more /etc/xen/centos5-1
kernel = "/boot/vmlinuz-2.6.18-53.1.13.el5xen"
memory = 256
name = "centos5-1"
vif = [ '''' ]
dhcp = "dhcp"
#disk = [''file:/home/vm/centos.5-1.img,sda1,w'', 
''file:/home/centos.swap,sda2,w'']
#root = "/dev/xvda1 ro"

disk = [ "tap:aio:/home/vm/centos.5-1.img,xvda,w" ]
root = "/dev/xvda ro"


Yet, when I try and use it, I get the following error:
VFS: Cannot open root device "xvda" or unknown-block(0,0)
Please append a correct "root=" boot option
Kernel panic - not syncing: VFS: Unable to mount root fs on 
unknown-block(0,0)


Any ideas on how to get these images to work?

-- 

Kind Regards
Rudi Ahlers
CEO, SoftDux

Web:   http://www.SoftDux.com
Check out my technical blog, http://blog.softdux.com for Linux or other
technical stuff, or visit http://www.WebHostingTalk.co.za for Web Hosting stugg


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

Rudi Ahlers wrote:
> Hi
>
> Does anyone know how to use the images from http://www.jailtime.org/? 
> I''ve downloaded the CentOS 5.1 
> (http://www.jailtime.org/download:centos:v5.1) to my CentOS 5.1 x64 
> Xen 3.1 server, and unpacked it to my /home folder.
>
> Then I took the included config file, centos.5-1.xen3.cfg and copied 
> it to /xen - and modified to my needs:
>
> [root@gimbli home]# more /etc/xen/centos5-1
> kernel = "/boot/vmlinuz-2.6.18-53.1.13.el5xen"
> memory = 256
> name = "centos5-1"
> vif = [ '''' ]
> dhcp = "dhcp"
> #disk = [''file:/home/vm/centos.5-1.img,sda1,w'', 
> ''file:/home/centos.swap,sda2,w'']
> #root = "/dev/xvda1 ro"
>
> disk = [ "tap:aio:/home/vm/centos.5-1.img,xvda,w" ]
> root = "/dev/xvda ro"
>
>
> Yet, when I try and use it, I get the following error:
> VFS: Cannot open root device "xvda" or unknown-block(0,0)
> Please append a correct "root=" boot option
> Kernel panic - not syncing: VFS: Unable to mount root fs on 
> unknown-block(0,0)
I gave up on the jailtime images a while ago: they''re useful, but I
find
a fast virt-install to be similarly useful and to cooperate with the 
CentOS/RHEL ideas about where things go. In particular, the /etc/fstab 
of the Jailtime image expects partitions to be on /dev/sda, while the 
current Xen installers and kernels put them in /dev/xvda.

Check the /etc/fstab of your image (which should be mountable with 
kpartx and loopback mounts, and look at its /etc/fstab. Or simply mount 
the partitions as /dev/sda the same way that the Jailtime author did.

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

Rudi Ahlers wrote:
> Hi
>
> Does anyone know how to use the images from http://www.jailtime.org/? 
> I''ve downloaded the CentOS 5.1 
> (http://www.jailtime.org/download:centos:v5.1) to my CentOS 5.1 x64 
> Xen 3.1 server, and unpacked it to my /home folder.
>
> Then I took the included config file, centos.5-1.xen3.cfg and copied 
> it to /xen - and modified to my needs:
>
> [root@gimbli home]# more /etc/xen/centos5-1
> kernel = "/boot/vmlinuz-2.6.18-53.1.13.el5xen"
> memory = 256
> name = "centos5-1"
> vif = [ '''' ]
> dhcp = "dhcp"
> #disk = [''file:/home/vm/centos.5-1.img,sda1,w'', 
> ''file:/home/centos.swap,sda2,w'']
> #root = "/dev/xvda1 ro"
>
> disk = [ "tap:aio:/home/vm/centos.5-1.img,xvda,w" ]
> root = "/dev/xvda ro"
Probably you need a initrd image built using --with=xennet 
--preload=xenblk and specify that as ramdisk= in the guest configuration 
file and change the /etc/fstab references in your image to xvda after 
loopback mounting that in dom0.

--Sadique
> Yet, when I try and use it, I get the following error:
> VFS: Cannot open root device "xvda" or unknown-block(0,0)
> Please append a correct "root=" boot option
> Kernel panic - not syncing: VFS: Unable to mount root fs on 
> unknown-block(0,0)
>
>
> Any ideas on how to get these images to work?
>

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

Nico Kadel-Garcia wrote:
> I gave up on the jailtime images a while ago: they''re useful, but
I find
> a fast virt-install to be similarly useful and to cooperate with the 
> CentOS/RHEL ideas about where things go. 
Have you had any success with using virt-install with a distribution 
which is not the same as your Dom0? The FC7 docs imply that you can only 
install FC7 guests, so I haven''t tried it.

Moving the jailtime image to LVM is a pain, so I''d prefer virt-install 
if it does the job.

Thanks

Evan

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

Evan Lavelle wrote:
> Nico Kadel-Garcia wrote:
>
>> I gave up on the jailtime images a while ago: they''re useful,
but I
>> find a fast virt-install to be similarly useful and to cooperate with 
>> the CentOS/RHEL ideas about where things go. 
>
> Have you had any success with using virt-install with a distribution 
> which is not the same as your Dom0? The FC7 docs imply that you can 
> only install FC7 guests, so I haven''t tried it.
It''s not true. For paravirtualized guests, you can use virt-install to 
install any guests which follow the packaging method followed by RHEL 
for its distribution. By this I mean, there should be a xenified kernel 
and initrd image for the virt-install to kick off the booting at 
xen/images in the installation tree. So any versions of RHEL (4.5 and 
above), Centos (4.5 and above), Fedora (fc5 and above) should work fine 
without any problems.

For fully virtualized guests, I have so far been successful to install 
debian, ubuntu and windows, so far tested, using virt-install/virt-manager.

--Sadique
>
> Moving the jailtime image to LVM is a pain, so I''d prefer
virt-install
> if it does the job.
>
> Thanks
>
> Evan
>
> _______________________________________________
> 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

Nico Kadel-Garcia wrote:
> Rudi Ahlers wrote:
>> Hi
>>
>> Does anyone know how to use the images from http://www.jailtime.org/? 
>> I''ve downloaded the CentOS 5.1 
>> (http://www.jailtime.org/download:centos:v5.1) to my CentOS 5.1 x64 
>> Xen 3.1 server, and unpacked it to my /home folder.
>>
>> Then I took the included config file, centos.5-1.xen3.cfg and copied 
>> it to /xen - and modified to my needs:
>>
>> [root@gimbli home]# more /etc/xen/centos5-1
>> kernel = "/boot/vmlinuz-2.6.18-53.1.13.el5xen"
>> memory = 256
>> name = "centos5-1"
>> vif = [ '''' ]
>> dhcp = "dhcp"
>> #disk = [''file:/home/vm/centos.5-1.img,sda1,w'', 
>> ''file:/home/centos.swap,sda2,w'']
>> #root = "/dev/xvda1 ro"
>>
>> disk = [ "tap:aio:/home/vm/centos.5-1.img,xvda,w" ]
>> root = "/dev/xvda ro"
>>
>>
>> Yet, when I try and use it, I get the following error:
>> VFS: Cannot open root device "xvda" or unknown-block(0,0)
>> Please append a correct "root=" boot option
>> Kernel panic - not syncing: VFS: Unable to mount root fs on 
>> unknown-block(0,0)
> I gave up on the jailtime images a while ago: they''re useful, but
I
> find a fast virt-install to be similarly useful and to cooperate with 
> the CentOS/RHEL ideas about where things go. In particular, the 
> /etc/fstab of the Jailtime image expects partitions to be on /dev/sda, 
> while the current Xen installers and kernels put them in /dev/xvda.
>
> Check the /etc/fstab of your image (which should be mountable with 
> kpartx and loopback mounts, and look at its /etc/fstab. Or simply 
> mount the partitions as /dev/sda the same way that the Jailtime author 
> did.
>
> _______________________________________________
> Xen-users mailing list
> Xen-users@lists.xensource.com
> http://lists.xensource.com/xen-users
>
That didn''t work, I''ve tried it already. Changing the
/dev/sda1 line in
/mnt/centos5.1/etc/fstab (image mounted with look device) to /dev/xvda1 
gave me the same error, except for pointing to a different block device.

Looking at /mnt/centos5.1/dev - there is no xvdX devices, so this is a 
problem.

-- 

Kind Regards
Rudi Ahlers
CEO, SoftDux

Web:   http://www.SoftDux.com
Check out my technical blog, http://blog.softdux.com for Linux or other
technical stuff, or visit http://www.WebHostingTalk.co.za for Web Hosting stugg


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

Sadique Puthen wrote:
> Rudi Ahlers wrote:
>> Hi
>>
>> Does anyone know how to use the images from http://www.jailtime.org/? 
>> I''ve downloaded the CentOS 5.1 
>> (http://www.jailtime.org/download:centos:v5.1) to my CentOS 5.1 x64 
>> Xen 3.1 server, and unpacked it to my /home folder.
>>
>> Then I took the included config file, centos.5-1.xen3.cfg and copied 
>> it to /xen - and modified to my needs:
>>
>> [root@gimbli home]# more /etc/xen/centos5-1
>> kernel = "/boot/vmlinuz-2.6.18-53.1.13.el5xen"
>> memory = 256
>> name = "centos5-1"
>> vif = [ '''' ]
>> dhcp = "dhcp"
>> #disk = [''file:/home/vm/centos.5-1.img,sda1,w'', 
>> ''file:/home/centos.swap,sda2,w'']
>> #root = "/dev/xvda1 ro"
>>
>> disk = [ "tap:aio:/home/vm/centos.5-1.img,xvda,w" ]
>> root = "/dev/xvda ro"
>
> Probably you need a initrd image built using --with=xennet 
> --preload=xenblk and specify that as ramdisk= in the guest 
> configuration file and change the /etc/fstab references in your image 
> to xvda after loopback mounting that in dom0.
>
> --Sadique
Hi Sadique

I''m going to attempt this again. I''ve installed Xen 3.2 on my
CentOS 5.1
machine, and want to try use this jailtime image again.

I''ve mounted /home/centos.5-1.img on /mnt/vm, edited /mnt/vm/etc/fstab
&
changed it to use /dev/xvda1

# This file is edited by fstab-sync - see ''man fstab-sync'' for
details
/dev/xvda1               /                       ext3    defaults 1 1


 From this, I realize there''s no /dev/xvda on the image:

[root@temp01 ~]# ll /mnt/vm/dev/x*
crw-rw---- 1 root root  10, 179 Mar 25  2001 /mnt/vm/dev/xsvc
crw-r--r-- 1 root root 204, 191 Mar 21  2007 /mnt/vm/dev/xvc0


So, how do I get it?

I''m trying to understand what you mean with the --with-xennet 
--preload=xenblk stuff, but I don''t understand how / where to put it. 
Please elaborate?
>
>> Yet, when I try and use it, I get the following error:
>> VFS: Cannot open root device "xvda" or unknown-block(0,0)
>> Please append a correct "root=" boot option
>> Kernel panic - not syncing: VFS: Unable to mount root fs on 
>> unknown-block(0,0)
>>
>>
>> Any ideas on how to get these images to work?
-- 

Kind Regards
Rudi Ahlers
CEO, SoftDux

Web:   http://www.SoftDux.com
Check out my technical blog, http://blog.softdux.com for Linux or other
technical stuff, or visit http://www.WebHostingTalk.co.za for Web Hosting stuff


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

I can''t comment on some of the fancier images offered by jailtime, but
for something like Centos (or rhel), I recommend you roll your own
image.  I created a local mirror of the Centos 5.1 files, and it takes
about 8 min to do a kickstart installation.
>From what I''ve learned so far, xvda is provided by the xen block
device driver, which is either in the kernel image, or part of the
initial ramdisk (initrd).  I see in your config file you are booting a
special kernel, but without special initrd.  Usually they go hand in
hand.

Here is my centos 5.1 xen config file.  You''ll note I am using an lvm
logical volume as the block device, instead of a loopback file.

# cat netserver
# uncomment the kernel, ramdisk and extra lines for a kickstart install
# make sure to comment the bootloader line
# after the install, comment kernel, ramdisk and extra, uncomment bootloader
#kernel = "/root/xen/centos64-xen-vmlinuz"
#ramdisk = "/root/xen/centos64-xen-initrd.img"
#extra = "text ks=http://192.168.2.8/centos64-2.ks"
bootloader = "/usr/bin/pygrub"
name = "netserver"
memory = "256"
disk = [ ''phy:vg0/xen_netserver,xvda,w'', ]
vif = [ ''bridge=xenbr0'', ]
vcpus=1
on_reboot = ''restart''
on_crash = ''restart''
on_poweroff = ''restart''
#on_reboot = ''destroy''
#on_crash = ''destroy''
#on_poweroff = ''destroy''

This is the site that taught me how to do a centos domu via kickstart:

http://wiki.centos.org/HowTos/Xen/InstallingCentOSDomU

Gordon

On Mon, Apr 7, 2008 at 11:58 AM, Rudi Ahlers <Rudi@softdux.com>
wrote:
> Sadique Puthen wrote:
>
> > Rudi Ahlers wrote:
> >
> > > Hi
> > >
> > > Does anyone know how to use the images from
http://www.jailtime.org/?
> I''ve downloaded the CentOS 5.1
> (http://www.jailtime.org/download:centos:v5.1) to my CentOS 5.1 x64 Xen 3.1
> server, and unpacked it to my /home folder.
> > >
> > > Then I took the included config file, centos.5-1.xen3.cfg and
copied it
> to /xen - and modified to my needs:
> > >
> > > [root@gimbli home]# more /etc/xen/centos5-1
> > > kernel = "/boot/vmlinuz-2.6.18-53.1.13.el5xen"
> > > memory = 256
> > > name = "centos5-1"
> > > vif = [ '''' ]
> > > dhcp = "dhcp"
> > > #disk = [''file:/home/vm/centos.5-1.img,sda1,w'',
> ''file:/home/centos.swap,sda2,w'']
> > > #root = "/dev/xvda1 ro"
> > >
> > > disk = [ "tap:aio:/home/vm/centos.5-1.img,xvda,w" ]
> > > root = "/dev/xvda ro"
> > >
> >
> > Probably you need a initrd image built using --with=xennet
> --preload=xenblk and specify that as ramdisk= in the guest configuration
> file and change the /etc/fstab references in your image to xvda after
> loopback mounting that in dom0.
> >
> > --Sadique
> >
>  Hi Sadique
>
>  I''m going to attempt this again. I''ve installed Xen 3.2
on my CentOS 5.1
> machine, and want to try use this jailtime image again.
>
>  I''ve mounted /home/centos.5-1.img on /mnt/vm, edited
/mnt/vm/etc/fstab &
> changed it to use /dev/xvda1
>
>  # This file is edited by fstab-sync - see ''man
fstab-sync'' for details
>  /dev/xvda1               /                       ext3    defaults 1 1
>
>
>  From this, I realize there''s no /dev/xvda on the image:
>
>  [root@temp01 ~]# ll /mnt/vm/dev/x*
>  crw-rw---- 1 root root  10, 179 Mar 25  2001 /mnt/vm/dev/xsvc
>  crw-r--r-- 1 root root 204, 191 Mar 21  2007 /mnt/vm/dev/xvc0
>
>
>  So, how do I get it?
>
>  I''m trying to understand what you mean with the --with-xennet
> --preload=xenblk stuff, but I don''t understand how / where to put
it. Please
> elaborate?
>
> >
> >
> > > Yet, when I try and use it, I get the following error:
> > > VFS: Cannot open root device "xvda" or
unknown-block(0,0)
> > > Please append a correct "root=" boot option
> > > Kernel panic - not syncing: VFS: Unable to mount root fs on
> unknown-block(0,0)
> > >
> > >
> > > Any ideas on how to get these images to work?
> > >
> >
>
>  --
>
>  Kind Regards
>  Rudi Ahlers
>  CEO, SoftDux
>
>  Web:   http://www.SoftDux.com
>  Check out my technical blog, http://blog.softdux.com for Linux or other
> technical stuff, or visit http://www.WebHostingTalk.co.za for Web Hosting
> stuff
>
>
>  _______________________________________________
>  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

Gordon McLellan wrote:
> I can''t comment on some of the fancier images offered by jailtime,
but
> for something like Centos (or rhel), I recommend you roll your own
> image.  I created a local mirror of the Centos 5.1 files, and it takes
> about 8 min to do a kickstart installation.
>
> >From what I''ve learned so far, xvda is provided by the xen
block
> device driver, which is either in the kernel image, or part of the
> initial ramdisk (initrd).  I see in your config file you are booting a
> special kernel, but without special initrd.  Usually they go hand in
> hand.
>
> Here is my centos 5.1 xen config file.  You''ll note I am using an
lvm
> logical volume as the block device, instead of a loopback file.
>
> # cat netserver
> # uncomment the kernel, ramdisk and extra lines for a kickstart install
> # make sure to comment the bootloader line
> # after the install, comment kernel, ramdisk and extra, uncomment
bootloader
> #kernel = "/root/xen/centos64-xen-vmlinuz"
> #ramdisk = "/root/xen/centos64-xen-initrd.img"
> #extra = "text ks=http://192.168.2.8/centos64-2.ks"
> bootloader = "/usr/bin/pygrub"
> name = "netserver"
> memory = "256"
> disk = [ ''phy:vg0/xen_netserver,xvda,w'', ]
> vif = [ ''bridge=xenbr0'', ]
> vcpus=1
> on_reboot = ''restart''
> on_crash = ''restart''
> on_poweroff = ''restart''
> #on_reboot = ''destroy''
> #on_crash = ''destroy''
> #on_poweroff = ''destroy''
>
> This is the site that taught me how to do a centos domu via kickstart:
>
> http://wiki.centos.org/HowTos/Xen/InstallingCentOSDomU
>
> Gordon
>   
Hi Gordon

I actually want to get FreeBSD & Windows working on my CentOS 5.1 x64 
server as well, so the jailtime images seem ideal.

I''ve modied the /etc/xen/centos.5-1.cfg file a bit, and the VPS is 
starting up, but haning at the sshd service:

INIT: version 2.86 booting
                Welcome to  CentOS release 5 (Final)
                Press ''I'' to enter interactive startup.
Setting clock : Mon Apr  7 13:02:55 EDT 2008 [  OK  ]
Starting udev: [  OK  ]
Setting hostname centos_pristine:  [  OK  ]
Checking filesystems
Checking all file systems.
[/sbin/fsck.ext3 (1) -- /] fsck.ext3 -a /dev/xvda1
/dev/xvda1: clean, 25465/128256 files, 96182/256256 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:
Determining IP information for eth0... failed.
[FAILED]
Starting system logger: [  OK  ]
Starting kernel logger: [  OK  ]
Mounting other filesystems:  [  OK  ]
Starting sshd: [  OK  ]

This is my config:

[root@temp01 ~]# more /etc/xen/centos.5-1.xen3.cfg
kernel = "/boot/vmlinuz-2.6.18-53.1.14.el5xen"
ramdisk = "/boot/xen-guest-initrd"
memory = 512
name = "centos.5-1"
vif = [ '''' ]
dhcp = "dhcp"
disk = [''file:/home/centos.5-1.img,xvda1,w'',
''file://centos.swap,xvda2,w'']
root = "/dev/xvda1 ro"
> On Mon, Apr 7, 2008 at 11:58 AM, Rudi Ahlers <Rudi@softdux.com>
wrote:
>   
>> Sadique Puthen wrote:
>>
>>     
>>> Rudi Ahlers wrote:
>>>
>>>       
>>>> Hi
>>>>
>>>> Does anyone know how to use the images from
http://www.jailtime.org/?
>>>>         
>> I''ve downloaded the CentOS 5.1
>> (http://www.jailtime.org/download:centos:v5.1) to my CentOS 5.1 x64 Xen
3.1
>> server, and unpacked it to my /home folder.
>>     
>>>> Then I took the included config file, centos.5-1.xen3.cfg and
copied it
>>>>         
>> to /xen - and modified to my needs:
>>     
>>>> [root@gimbli home]# more /etc/xen/centos5-1
>>>> kernel = "/boot/vmlinuz-2.6.18-53.1.13.el5xen"
>>>> memory = 256
>>>> name = "centos5-1"
>>>> vif = [ '''' ]
>>>> dhcp = "dhcp"
>>>> #disk =
[''file:/home/vm/centos.5-1.img,sda1,w'',
>>>>         
>> ''file:/home/centos.swap,sda2,w'']
>>     
>>>> #root = "/dev/xvda1 ro"
>>>>
>>>> disk = [ "tap:aio:/home/vm/centos.5-1.img,xvda,w" ]
>>>> root = "/dev/xvda ro"
>>>>
>>>>         
>>> Probably you need a initrd image built using --with=xennet
>>>       
>> --preload=xenblk and specify that as ramdisk= in the guest
configuration
>> file and change the /etc/fstab references in your image to xvda after
>> loopback mounting that in dom0.
>>     
>>> --Sadique
>>>
>>>       
>>  Hi Sadique
>>
>>  I''m going to attempt this again. I''ve installed Xen
3.2 on my CentOS 5.1
>> machine, and want to try use this jailtime image again.
>>
>>  I''ve mounted /home/centos.5-1.img on /mnt/vm, edited
/mnt/vm/etc/fstab &
>> changed it to use /dev/xvda1
>>
>>  # This file is edited by fstab-sync - see ''man
fstab-sync'' for details
>>  /dev/xvda1               /                       ext3    defaults 1 1
>>
>>
>>  From this, I realize there''s no /dev/xvda on the image:
>>
>>  [root@temp01 ~]# ll /mnt/vm/dev/x*
>>  crw-rw---- 1 root root  10, 179 Mar 25  2001 /mnt/vm/dev/xsvc
>>  crw-r--r-- 1 root root 204, 191 Mar 21  2007 /mnt/vm/dev/xvc0
>>
>>
>>  So, how do I get it?
>>
>>  I''m trying to understand what you mean with the --with-xennet
>> --preload=xenblk stuff, but I don''t understand how / where to
put it. Please
>> elaborate?
>>     

-- 

Kind Regards
Rudi Ahlers
CEO, SoftDux

Web:   http://www.SoftDux.com
Check out my technical blog, http://blog.softdux.com for Linux or other
technical stuff, or visit http://www.WebHostingTalk.co.za for Web Hosting stuff


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

Hello Rudi,
>From that output, it looks like it has hung after the ssh service
starts.  I wonder about the VIF line in your xen config file.  Why is
it empty? Is vif = [ '''' ] the same as accepting whatever
default
adapter xen is configured to provide?  How long do you let it sit
there when it appears hung.  Depending on what it''s trying to do, it
could take several minutes to time out, before moving onto the next
service.

You could try pressing "i" when prompted, and go through your services
one at a time, to see which one is hanging things up.

In regards to Windows, I have one hvm image of windows server 2003
which was configured using the virt-manager gui.  The install was
pretty straight forward, except that Windows was unable to detect my
PC type.  When I was prompted to press F6 to load additional drivers,
I pressed F5 instead, and selected "Standard PC".  As I understand it,
this tells windows which HAL to use for interfacing the NT kernel with
the underlying hardware.

Gordon

On Mon, Apr 7, 2008 at 1:14 PM, Rudi Ahlers <Rudi@softdux.com>
wrote:
>
> Gordon McLellan wrote:
>
> > I can''t comment on some of the fancier images offered by
jailtime, but
> > for something like Centos (or rhel), I recommend you roll your own
> > image.  I created a local mirror of the Centos 5.1 files, and it takes
> > about 8 min to do a kickstart installation.
> >
> > >From what I''ve learned so far, xvda is provided by the
xen block
> > device driver, which is either in the kernel image, or part of the
> > initial ramdisk (initrd).  I see in your config file you are booting a
> > special kernel, but without special initrd.  Usually they go hand in
> > hand.
> >
> > Here is my centos 5.1 xen config file.  You''ll note I am
using an lvm
> > logical volume as the block device, instead of a loopback file.
> >
> > # cat netserver
> > # uncomment the kernel, ramdisk and extra lines for a kickstart
install
> > # make sure to comment the bootloader line
> > # after the install, comment kernel, ramdisk and extra, uncomment
> bootloader
> > #kernel = "/root/xen/centos64-xen-vmlinuz"
> > #ramdisk = "/root/xen/centos64-xen-initrd.img"
> > #extra = "text ks=http://192.168.2.8/centos64-2.ks"
> > bootloader = "/usr/bin/pygrub"
> > name = "netserver"
> > memory = "256"
> > disk = [ ''phy:vg0/xen_netserver,xvda,w'', ]
> > vif = [ ''bridge=xenbr0'', ]
> > vcpus=1
> > on_reboot = ''restart''
> > on_crash = ''restart''
> > on_poweroff = ''restart''
> > #on_reboot = ''destroy''
> > #on_crash = ''destroy''
> > #on_poweroff = ''destroy''
> >
> > This is the site that taught me how to do a centos domu via kickstart:
> >
> > http://wiki.centos.org/HowTos/Xen/InstallingCentOSDomU
> >
> > Gordon
> >
> >
>  Hi Gordon
>
>  I actually want to get FreeBSD & Windows working on my CentOS 5.1 x64
> server as well, so the jailtime images seem ideal.
>
>  I''ve modied the /etc/xen/centos.5-1.cfg file a bit, and the VPS
is starting
> up, but haning at the sshd service:
>
>  INIT: version 2.86 booting
>                Welcome to  CentOS release 5 (Final)
>                Press ''I'' to enter interactive startup.
>  Setting clock : Mon Apr  7 13:02:55 EDT 2008 [  OK  ]
>  Starting udev: [  OK  ]
>  Setting hostname centos_pristine:  [  OK  ]
>  Checking filesystems
>  Checking all file systems.
>  [/sbin/fsck.ext3 (1) -- /] fsck.ext3 -a /dev/xvda1
>  /dev/xvda1: clean, 25465/128256 files, 96182/256256 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:
>  Determining IP information for eth0... failed.
>  [FAILED]
>  Starting system logger: [  OK  ]
>  Starting kernel logger: [  OK  ]
>  Mounting other filesystems:  [  OK  ]
>  Starting sshd: [  OK  ]
>
>  This is my config:
>
>  [root@temp01 ~]# more /etc/xen/centos.5-1.xen3.cfg
>  kernel = "/boot/vmlinuz-2.6.18-53.1.14.el5xen"
>  ramdisk = "/boot/xen-guest-initrd"
>  memory = 512
>  name = "centos.5-1"
>  vif = [ '''' ]
>  dhcp = "dhcp"
>  disk = [''file:/home/centos.5-1.img,xvda1,w'',
''file://centos.swap,xvda2,w'']
>
>
>  root = "/dev/xvda1 ro"
>
>
> > On Mon, Apr 7, 2008 at 11:58 AM, Rudi Ahlers <Rudi@softdux.com>
wrote:
> >
> >
> > > Sadique Puthen wrote:
> > >
> > >
> > >
> > > > Rudi Ahlers wrote:
> > > >
> > > >
> > > >
> > > > > Hi
> > > > >
> > > > > Does anyone know how to use the images from
> http://www.jailtime.org/?
> > > > >
> > > > >
> > > >
> > > I''ve downloaded the CentOS 5.1
> > > (http://www.jailtime.org/download:centos:v5.1) to my CentOS 5.1
x64 Xen
> 3.1
> > > server, and unpacked it to my /home folder.
> > >
> > >
> > > >
> > > > > Then I took the included config file,
centos.5-1.xen3.cfg and copied
> it
> > > > >
> > > > >
> > > >
> > > to /xen - and modified to my needs:
> > >
> > >
> > > >
> > > > > [root@gimbli home]# more /etc/xen/centos5-1
> > > > > kernel =
"/boot/vmlinuz-2.6.18-53.1.13.el5xen"
> > > > > memory = 256
> > > > > name = "centos5-1"
> > > > > vif = [ '''' ]
> > > > > dhcp = "dhcp"
> > > > > #disk =
[''file:/home/vm/centos.5-1.img,sda1,w'',
> > > > >
> > > > >
> > > >
> > > ''file:/home/centos.swap,sda2,w'']
> > >
> > >
> > > >
> > > > > #root = "/dev/xvda1 ro"
> > > > >
> > > > > disk = [
"tap:aio:/home/vm/centos.5-1.img,xvda,w" ]
> > > > > root = "/dev/xvda ro"
> > > > >
> > > > >
> > > > >
> > > > Probably you need a initrd image built using --with=xennet
> > > >
> > > >
> > > --preload=xenblk and specify that as ramdisk= in the guest
configuration
> > > file and change the /etc/fstab references in your image to xvda
after
> > > loopback mounting that in dom0.
> > >
> > >
> > > > --Sadique
> > > >
> > > >
> > > >
> > >  Hi Sadique
> > >
> > >  I''m going to attempt this again. I''ve
installed Xen 3.2 on my CentOS
> 5.1
> > > machine, and want to try use this jailtime image again.
> > >
> > >  I''ve mounted /home/centos.5-1.img on /mnt/vm, edited
/mnt/vm/etc/fstab
> &
> > > changed it to use /dev/xvda1
> > >
> > >  # This file is edited by fstab-sync - see ''man
fstab-sync'' for details
> > >  /dev/xvda1               /                       ext3   
defaults 1 1
> > >
> > >
> > >  From this, I realize there''s no /dev/xvda on the image:
> > >
> > >  [root@temp01 ~]# ll /mnt/vm/dev/x*
> > >  crw-rw---- 1 root root  10, 179 Mar 25  2001 /mnt/vm/dev/xsvc
> > >  crw-r--r-- 1 root root 204, 191 Mar 21  2007 /mnt/vm/dev/xvc0
> > >
> > >
> > >  So, how do I get it?
> > >
> > >  I''m trying to understand what you mean with the
--with-xennet
> > > --preload=xenblk stuff, but I don''t understand how /
where to put it.
> Please
> > > elaborate?
> > >
> > >
> >
>
>
>  --
>
>
>  Kind Regards
>  Rudi Ahlers
>  CEO, SoftDux
>
>  Web:   http://www.SoftDux.com
>  Check out my technical blog, http://blog.softdux.com for Linux or other
> technical stuff, or visit http://www.WebHostingTalk.co.za for Web Hosting
> stuff
>
>
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

Gordon McLellan wrote:
> I can''t comment on some of the fancier images offered by jailtime,
but
> for something like Centos (or rhel), I recommend you roll your own
> image.  I created a local mirror of the Centos 5.1 files, and it takes
> about 8 min to do a kickstart installation.
>
> >From what I''ve learned so far, xvda is provided by the xen
block
> device driver, which is either in the kernel image, or part of the
> initial ramdisk (initrd).  I see in your config file you are booting a
> special kernel, but without special initrd.  Usually they go hand in
> hand.
>
> Here is my centos 5.1 xen config file.  You''ll note I am using an
lvm
> logical volume as the block device, instead of a loopback file.
>
> # cat netserver
> # uncomment the kernel, ramdisk and extra lines for a kickstart install
> # make sure to comment the bootloader line
> # after the install, comment kernel, ramdisk and extra, uncomment
bootloader
> #kernel = "/root/xen/centos64-xen-vmlinuz"
> #ramdisk = "/root/xen/centos64-xen-initrd.img"
> #extra = "text ks=http://192.168.2.8/centos64-2.ks"
> bootloader = "/usr/bin/pygrub"
> name = "netserver"
> memory = "256"
> disk = [ ''phy:vg0/xen_netserver,xvda,w'', ]
> vif = [ ''bridge=xenbr0'', ]
> vcpus=1
> on_reboot = ''restart''
> on_crash = ''restart''
> on_poweroff = ''restart''
> #on_reboot = ''destroy''
> #on_crash = ''destroy''
> #on_poweroff = ''destroy''
>
> This is the site that taught me how to do a centos domu via kickstart:
>
> http://wiki.centos.org/HowTos/Xen/InstallingCentOSDomU
>
> Gordon
>
> On Mon, Apr 7, 2008 at 11:58 AM, Rudi Ahlers <Rudi@softdux.com>
wrote:
>   
Gordon

As matter of interest, what Server OS are you using, and what VPS OS are 
you using?

I''m trying to get 32bit VPS OS''s work on CentOS 5.1 x64. This
is
something I can''t get working. On a previous server, I have CentOS 5.1 
x64 with the default Xen3.1 from the CentOS repositories, and the only 
other OS I could get installed was CentOS 5.1 x64 from a local CentOS 
5.1 x64 repository.

-- 

Kind Regards
Rudi Ahlers
CEO, SoftDux

Web:   http://www.SoftDux.com
Check out my technical blog, http://blog.softdux.com for Linux or other
technical stuff, or visit http://www.WebHostingTalk.co.za for Web Hosting stuff


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

Rudi,

I''m running Centos 5.1 x64 as the base server OS (Dom0), with several
centos 5.1 x64 pv-machines and one windows server 2003 32bit fully
virt. machine (DomU''s).

My hardware is a single xeon 5405 (quad core) with 8g of ram and a
small sata soft-raid array which I''ve setup with LVM.   I might as
well add that I love using LVM with XEN, it is ten times better than
VMware Server''s loopback filesystem.  It''s very easy to create
new
space for a vm, and the disk responsiveness seems very much improved
as well.   My only drawback at this time is soft-raid doesn''t handle
multi user IO requests very well, the disk array gets swamped pretty
easy when multiple VMs are trying to read/write at the same time.

Gordon


On Mon, Apr 7, 2008 at 1:40 PM, Rudi Ahlers <Rudi@softdux.com>
wrote:
>  Gordon
>
>  As matter of interest, what Server OS are you using, and what VPS OS are
> you using?
>
>  I''m trying to get 32bit VPS OS''s work on CentOS 5.1 x64.
This is something
> I can''t get working. On a previous server, I have CentOS 5.1 x64
with the
> default Xen3.1 from the CentOS repositories, and the only other OS I could
> get installed was CentOS 5.1 x64 from a local CentOS 5.1 x64 repository.
>
>  --
>
>
>  Kind Regards
>  Rudi Ahlers
>  CEO, SoftDux
>
>  Web:   http://www.SoftDux.com
>  Check out my technical blog, http://blog.softdux.com for Linux or other
> technical stuff, or visit http://www.WebHostingTalk.co.za for Web Hosting
> stuff
>
>
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

Gordon McLellan wrote:
> Rudi,
>
> I''m running Centos 5.1 x64 as the base server OS (Dom0), with
several
> centos 5.1 x64 pv-machines and one windows server 2003 32bit fully
> virt. machine (DomU''s).
>
> My hardware is a single xeon 5405 (quad core) with 8g of ram and a
> small sata soft-raid array which I''ve setup with LVM.   I might as
> well add that I love using LVM with XEN, it is ten times better than
> VMware Server''s loopback filesystem.  It''s very easy to
create new
> space for a vm, and the disk responsiveness seems very much improved
> as well.   My only drawback at this time is soft-raid doesn''t
handle
> multi user IO requests very well, the disk array gets swamped pretty
> easy when multiple VMs are trying to read/write at the same time.
>
> Gordon
>
>
> On Mon, Apr 7, 2008 at 1:40 PM, Rudi Ahlers <Rudi@softdux.com> wrote:
>   
>>  Gordon
>>
>>  As matter of interest, what Server OS are you using, and what VPS OS
are
>> you using?
>>
>>  I''m trying to get 32bit VPS OS''s work on CentOS 5.1
x64. This is something
>> I can''t get working. On a previous server, I have CentOS 5.1
x64 with the
>> default Xen3.1 from the CentOS repositories, and the only other OS I
could
>> get installed was CentOS 5.1 x64 from a local CentOS 5.1 x64
repository.
>>
>>  --
>>
>>     
May I ask how you got the Windows 32bit installed? I only have a Windows 
XP 32bit CD right now, but would love to get a Windows server running.

-- 

Kind Regards
Rudi Ahlers
CEO, SoftDux

Web:   http://www.SoftDux.com
Check out my technical blog, http://blog.softdux.com for Linux or other
technical stuff, or visit http://www.WebHostingTalk.co.za for Web Hosting stuff


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

Gordon McLellan wrote:
> Hello Rudi,
>
> >From that output, it looks like it has hung after the ssh service
> starts.  I wonder about the VIF line in your xen config file.  Why is
> it empty? Is vif = [ '''' ] the same as accepting whatever
default
> adapter xen is configured to provide?  How long do you let it sit
> there when it appears hung.  Depending on what it''s trying to do,
it
> could take several minutes to time out, before moving onto the next
> service.
>
> You could try pressing "i" when prompted, and go through your
services
> one at a time, to see which one is hanging things up.
>   
Ok, this is where it freezes:

Start service sshd (Y)es/(N)o/(C)ontinue? [Y] y
Starting sshd: [  OK  ]
Start service local (Y)es/(N)o/(C)ontinue? [Y] y


I just leave it, and nothing happens.
> In regards to Windows, I have one hvm image of windows server 2003
> which was configured using the virt-manager gui.  The install was
> pretty straight forward, except that Windows was unable to detect my
> PC type.  When I was prompted to press F6 to load additional drivers,
> I pressed F5 instead, and selected "Standard PC".  As I
understand it,
> this tells windows which HAL to use for interfacing the NT kernel with
> the underlying hardware.
>
> Gordon
>
> On Mon, Apr 7, 2008 at 1:14 PM, Rudi Ahlers <Rudi@softdux.com> wrote:
>   
>> Gordon McLellan wrote:
>>
>>     
>>> I can''t comment on some of the fancier images offered by
jailtime, but
>>> for something like Centos (or rhel), I recommend you roll your own
>>> image.  I created a local mirror of the Centos 5.1 files, and it
takes
>>> about 8 min to do a kickstart installation.
>>>
>>> >From what I''ve learned so far, xvda is provided by the
xen block
>>> device driver, which is either in the kernel image, or part of the
>>> initial ramdisk (initrd).  I see in your config file you are
booting a
>>> special kernel, but without special initrd.  Usually they go hand
in
>>> hand.
>>>
>>> Here is my centos 5.1 xen config file.  You''ll note I am
using an lvm
>>> logical volume as the block device, instead of a loopback file.
>>>
>>> # cat netserver
>>> # uncomment the kernel, ramdisk and extra lines for a kickstart
install
>>> # make sure to comment the bootloader line
>>> # after the install, comment kernel, ramdisk and extra, uncomment
>>>       
>> bootloader
>>     
>>> #kernel = "/root/xen/centos64-xen-vmlinuz"
>>> #ramdisk = "/root/xen/centos64-xen-initrd.img"
>>> #extra = "text ks=http://192.168.2.8/centos64-2.ks"
>>> bootloader = "/usr/bin/pygrub"
>>> name = "netserver"
>>> memory = "256"
>>> disk = [ ''phy:vg0/xen_netserver,xvda,w'', ]
>>> vif = [ ''bridge=xenbr0'', ]
>>> vcpus=1
>>> on_reboot = ''restart''
>>> on_crash = ''restart''
>>> on_poweroff = ''restart''
>>> #on_reboot = ''destroy''
>>> #on_crash = ''destroy''
>>> #on_poweroff = ''destroy''
>>>
>>> This is the site that taught me how to do a centos domu via
kickstart:
>>>
>>> http://wiki.centos.org/HowTos/Xen/InstallingCentOSDomU
>>>
>>> Gordon
>>>
>>>
>>>       
>>  Hi Gordon
>>
>>  I actually want to get FreeBSD & Windows working on my CentOS 5.1
x64
>> server as well, so the jailtime images seem ideal.
>>
>>  I''ve modied the /etc/xen/centos.5-1.cfg file a bit, and the
VPS is starting
>> up, but haning at the sshd service:
>>
>>  INIT: version 2.86 booting
>>                Welcome to  CentOS release 5 (Final)
>>                Press ''I'' to enter interactive
startup.
>>  Setting clock : Mon Apr  7 13:02:55 EDT 2008 [  OK  ]
>>  Starting udev: [  OK  ]
>>  Setting hostname centos_pristine:  [  OK  ]
>>  Checking filesystems
>>  Checking all file systems.
>>  [/sbin/fsck.ext3 (1) -- /] fsck.ext3 -a /dev/xvda1
>>  /dev/xvda1: clean, 25465/128256 files, 96182/256256 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:
>>  Determining IP information for eth0... failed.
>>  [FAILED]
>>  Starting system logger: [  OK  ]
>>  Starting kernel logger: [  OK  ]
>>  Mounting other filesystems:  [  OK  ]
>>  Starting sshd: [  OK  ]
>>
>>  This is my config:
>>
>>  [root@temp01 ~]# more /etc/xen/centos.5-1.xen3.cfg
>>  kernel = "/boot/vmlinuz-2.6.18-53.1.14.el5xen"
>>  ramdisk = "/boot/xen-guest-initrd"
>>  memory = 512
>>  name = "centos.5-1"
>>  vif = [ '''' ]
>>  dhcp = "dhcp"
>>  disk = [''file:/home/centos.5-1.img,xvda1,w'',
''file://centos.swap,xvda2,w'']
>>
>>
>>  root = "/dev/xvda1 ro"
>>
>>
>>     

-- 

Kind Regards
Rudi Ahlers
CEO, SoftDux

Web:   http://www.SoftDux.com
Check out my technical blog, http://blog.softdux.com for Linux or other
technical stuff, or visit http://www.WebHostingTalk.co.za for Web Hosting stuff


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

Service "local" refers to /etc/rc.local ... that is the end of
startup, nothing else will be printed after that.

Try pressing enter a few times, and you will get a login prompt.

In regards to loading windows ... installation of XP shouldn''t be any
different than Windows 2003.   When you''re in the blue screen portion
of setup, you''ll see a prompt at the bottom of the screen that says
something like Press F6 to load additional drivers.  Press F5 when you
see that prompt, and choose "Standard PC".

The rest of the install is 100% the same as installing it on a physical PC.

If you''re running Centos 5.1 as Dom0, you can use the virtualization
manager.  Tell it you want to create a fully virtual machine, make
sure you choose OS Type = Windows and OS Variant = Microsoft Windows
2003

Gordon


On Mon, Apr 7, 2008 at 2:43 PM, Rudi Ahlers <Rudi@softdux.com>
wrote:
> Gordon McLellan wrote:
>
> > Hello Rudi,
> >
> > >From that output, it looks like it has hung after the ssh service
> > starts.  I wonder about the VIF line in your xen config file.  Why is
> > it empty? Is vif = [ '''' ] the same as accepting
whatever default
> > adapter xen is configured to provide?  How long do you let it sit
> > there when it appears hung.  Depending on what it''s trying to
do, it
> > could take several minutes to time out, before moving onto the next
> > service.
> >
> > You could try pressing "i" when prompted, and go through
your services
> > one at a time, to see which one is hanging things up.
> >
> >
>  Ok, this is where it freezes:
>
>  Start service sshd (Y)es/(N)o/(C)ontinue? [Y] y
>  Starting sshd: [  OK  ]
>  Start service local (Y)es/(N)o/(C)ontinue? [Y] y
>
>
>  I just leave it, and nothing happens.
>
>
>
> > In regards to Windows, I have one hvm image of windows server 2003
> > which was configured using the virt-manager gui.  The install was
> > pretty straight forward, except that Windows was unable to detect my
> > PC type.  When I was prompted to press F6 to load additional drivers,
> > I pressed F5 instead, and selected "Standard PC".  As I
understand it,
> > this tells windows which HAL to use for interfacing the NT kernel with
> > the underlying hardware.
> >
> > Gordon
> >
> > On Mon, Apr 7, 2008 at 1:14 PM, Rudi Ahlers <Rudi@softdux.com>
wrote:
> >
> >
> > > Gordon McLellan wrote:
> > >
> > >
> > >
> > > > I can''t comment on some of the fancier images
offered by jailtime, but
> > > > for something like Centos (or rhel), I recommend you roll
your own
> > > > image.  I created a local mirror of the Centos 5.1 files,
and it takes
> > > > about 8 min to do a kickstart installation.
> > > >
> > > > >From what I''ve learned so far, xvda is provided
by the xen block
> > > > device driver, which is either in the kernel image, or part
of the
> > > > initial ramdisk (initrd).  I see in your config file you are
booting a
> > > > special kernel, but without special initrd.  Usually they go
hand in
> > > > hand.
> > > >
> > > > Here is my centos 5.1 xen config file.  You''ll note
I am using an lvm
> > > > logical volume as the block device, instead of a loopback
file.
> > > >
> > > > # cat netserver
> > > > # uncomment the kernel, ramdisk and extra lines for a
kickstart
> install
> > > > # make sure to comment the bootloader line
> > > > # after the install, comment kernel, ramdisk and extra,
uncomment
> > > >
> > > >
> > > bootloader
> > >
> > >
> > > > #kernel = "/root/xen/centos64-xen-vmlinuz"
> > > > #ramdisk = "/root/xen/centos64-xen-initrd.img"
> > > > #extra = "text
ks=http://192.168.2.8/centos64-2.ks"
> > > > bootloader = "/usr/bin/pygrub"
> > > > name = "netserver"
> > > > memory = "256"
> > > > disk = [ ''phy:vg0/xen_netserver,xvda,w'', ]
> > > > vif = [ ''bridge=xenbr0'', ]
> > > > vcpus=1
> > > > on_reboot = ''restart''
> > > > on_crash = ''restart''
> > > > on_poweroff = ''restart''
> > > > #on_reboot = ''destroy''
> > > > #on_crash = ''destroy''
> > > > #on_poweroff = ''destroy''
> > > >
> > > > This is the site that taught me how to do a centos domu via
kickstart:
> > > >
> > > > http://wiki.centos.org/HowTos/Xen/InstallingCentOSDomU
> > > >
> > > > Gordon
> > > >
> > > >
> > > >
> > > >
> > >  Hi Gordon
> > >
> > >  I actually want to get FreeBSD & Windows working on my
CentOS 5.1 x64
> > > server as well, so the jailtime images seem ideal.
> > >
> > >  I''ve modied the /etc/xen/centos.5-1.cfg file a bit, and
the VPS is
> starting
> > > up, but haning at the sshd service:
> > >
> > >  INIT: version 2.86 booting
> > >               Welcome to  CentOS release 5 (Final)
> > >               Press ''I'' to enter interactive
startup.
> > >  Setting clock : Mon Apr  7 13:02:55 EDT 2008 [  OK  ]
> > >  Starting udev: [  OK  ]
> > >  Setting hostname centos_pristine:  [  OK  ]
> > >  Checking filesystems
> > >  Checking all file systems.
> > >  [/sbin/fsck.ext3 (1) -- /] fsck.ext3 -a /dev/xvda1
> > >  /dev/xvda1: clean, 25465/128256 files, 96182/256256 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:
> > >  Determining IP information for eth0... failed.
> > >  [FAILED]
> > >  Starting system logger: [  OK  ]
> > >  Starting kernel logger: [  OK  ]
> > >  Mounting other filesystems:  [  OK  ]
> > >  Starting sshd: [  OK  ]
> > >
> > >  This is my config:
> > >
> > >  [root@temp01 ~]# more /etc/xen/centos.5-1.xen3.cfg
> > >  kernel = "/boot/vmlinuz-2.6.18-53.1.14.el5xen"
> > >  ramdisk = "/boot/xen-guest-initrd"
> > >  memory = 512
> > >  name = "centos.5-1"
> > >  vif = [ '''' ]
> > >  dhcp = "dhcp"
> > >  disk = [''file:/home/centos.5-1.img,xvda1,w'',
> ''file://centos.swap,xvda2,w'']
> > >
> > >
> > >  root = "/dev/xvda1 ro"
> > >
> > >
> > >
> > >
> >
>
>
>  --
>
>
>  Kind Regards
>  Rudi Ahlers
>  CEO, SoftDux
>
>  Web:   http://www.SoftDux.com
>  Check out my technical blog, http://blog.softdux.com for Linux or other
> technical stuff, or visit http://www.WebHostingTalk.co.za for Web Hosting
> stuff
>
>
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

Gordon McLellan wrote:
> Service "local" refers to /etc/rc.local ... that is the end of
> startup, nothing else will be printed after that.
>
> Try pressing enter a few times, and you will get a login prompt.
>
> In regards to loading windows ... installation of XP shouldn''t be
any
> different than Windows 2003.   When you''re in the blue screen
portion
> of setup, you''ll see a prompt at the bottom of the screen that
says
> something like Press F6 to load additional drivers.  Press F5 when you
> see that prompt, and choose "Standard PC".
>
> The rest of the install is 100% the same as installing it on a physical PC.
>
> If you''re running Centos 5.1 as Dom0, you can use the
virtualization
> manager.  Tell it you want to create a fully virtual machine, make
> sure you choose OS Type = Windows and OS Variant = Microsoft Windows
> 2003
>
> Gordon
>
>
> On Mon, Apr 7, 2008 at 2:43 PM, Rudi Ahlers <Rudi@softdux.com> wrote:
>   
>> Gordon McLellan wrote:
>>
>>     
>>> Hello Rudi,
>>>
>>> >From that output, it looks like it has hung after the ssh
service
>>> starts.  I wonder about the VIF line in your xen config file.  Why
is
>>> it empty? Is vif = [ '''' ] the same as accepting
whatever default
>>> adapter xen is configured to provide?  How long do you let it sit
>>> there when it appears hung.  Depending on what it''s trying
to do, it
>>> could take several minutes to time out, before moving onto the next
>>> service.
>>>
>>> You could try pressing "i" when prompted, and go through
your services
>>> one at a time, to see which one is hanging things up.
>>>
>>>
>>>       
>>  Ok, this is where it freezes:
>>
>>  Start service sshd (Y)es/(N)o/(C)ontinue? [Y] y
>>  Starting sshd: [  OK  ]
>>  Start service local (Y)es/(N)o/(C)ontinue? [Y] y
>>
>>
>>  I just leave it, and nothing happens.
>>
>>
>>
>>     
>>> In regards to Windows, I have one hvm image of windows server 2003
>>> which was configured using the virt-manager gui.  The install was
>>> pretty straight forward, except that Windows was unable to detect
my
>>> PC type.  When I was prompted to press F6 to load additional
drivers,
>>> I pressed F5 instead, and selected "Standard PC".  As I
understand it,
>>> this tells windows which HAL to use for interfacing the NT kernel
with
>>> the underlying hardware.
>>>
>>> Gordon
>>>
>>> On Mon, Apr 7, 2008 at 1:14 PM, Rudi Ahlers
<Rudi@softdux.com> wrote:
>>>
>>>
>>>       
>>>> Gordon McLellan wrote:
>>>>
>>>>
>>>>
>>>>         
>>>>> I can''t comment on some of the fancier images
offered by jailtime, but
>>>>> for something like Centos (or rhel), I recommend you roll
your own
>>>>> image.  I created a local mirror of the Centos 5.1 files,
and it takes
>>>>> about 8 min to do a kickstart installation.
>>>>>
>>>>> >From what I''ve learned so far, xvda is
provided by the xen block
>>>>> device driver, which is either in the kernel image, or part
of the
>>>>> initial ramdisk (initrd).  I see in your config file you
are booting a
>>>>> special kernel, but without special initrd.  Usually they
go hand in
>>>>> hand.
>>>>>
>>>>> Here is my centos 5.1 xen config file.  You''ll
note I am using an lvm
>>>>> logical volume as the block device, instead of a loopback
file.
>>>>>
>>>>> # cat netserver
>>>>> # uncomment the kernel, ramdisk and extra lines for a
kickstart
>>>>>           
>> install
>>     
>>>>> # make sure to comment the bootloader line
>>>>> # after the install, comment kernel, ramdisk and extra,
uncomment
>>>>>
>>>>>
>>>>>           
>>>> bootloader
>>>>
>>>>
>>>>         
>>>>> #kernel = "/root/xen/centos64-xen-vmlinuz"
>>>>> #ramdisk = "/root/xen/centos64-xen-initrd.img"
>>>>> #extra = "text
ks=http://192.168.2.8/centos64-2.ks"
>>>>> bootloader = "/usr/bin/pygrub"
>>>>> name = "netserver"
>>>>> memory = "256"
>>>>> disk = [ ''phy:vg0/xen_netserver,xvda,w'',
]
>>>>> vif = [ ''bridge=xenbr0'', ]
>>>>> vcpus=1
>>>>> on_reboot = ''restart''
>>>>> on_crash = ''restart''
>>>>> on_poweroff = ''restart''
>>>>> #on_reboot = ''destroy''
>>>>> #on_crash = ''destroy''
>>>>> #on_poweroff = ''destroy''
>>>>>
>>>>> This is the site that taught me how to do a centos domu via
kickstart:
>>>>>
>>>>> http://wiki.centos.org/HowTos/Xen/InstallingCentOSDomU
>>>>>
>>>>> Gordon
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>           
>>>>  Hi Gordon
>>>>
>>>>  I actually want to get FreeBSD & Windows working on my
CentOS 5.1 x64
>>>> server as well, so the jailtime images seem ideal.
>>>>
>>>>  I''ve modied the /etc/xen/centos.5-1.cfg file a bit,
and the VPS is
>>>>         
>> starting
>>     
>>>> up, but haning at the sshd service:
>>>>
>>>>  INIT: version 2.86 booting
>>>>               Welcome to  CentOS release 5 (Final)
>>>>               Press ''I'' to enter interactive
startup.
>>>>  Setting clock : Mon Apr  7 13:02:55 EDT 2008 [  OK  ]
>>>>  Starting udev: [  OK  ]
>>>>  Setting hostname centos_pristine:  [  OK  ]
>>>>  Checking filesystems
>>>>  Checking all file systems.
>>>>  [/sbin/fsck.ext3 (1) -- /] fsck.ext3 -a /dev/xvda1
>>>>  /dev/xvda1: clean, 25465/128256 files, 96182/256256 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:
>>>>  Determining IP information for eth0... failed.
>>>>  [FAILED]
>>>>  Starting system logger: [  OK  ]
>>>>  Starting kernel logger: [  OK  ]
>>>>  Mounting other filesystems:  [  OK  ]
>>>>  Starting sshd: [  OK  ]
>>>>
>>>>  This is my config:
>>>>
>>>>  [root@temp01 ~]# more /etc/xen/centos.5-1.xen3.cfg
>>>>  kernel = "/boot/vmlinuz-2.6.18-53.1.14.el5xen"
>>>>  ramdisk = "/boot/xen-guest-initrd"
>>>>  memory = 512
>>>>  name = "centos.5-1"
>>>>  vif = [ '''' ]
>>>>  dhcp = "dhcp"
>>>>  disk = [''file:/home/centos.5-1.img,xvda1,w'',
>>>>         
>> ''file://centos.swap,xvda2,w'']
>>     
>>>>  root = "/dev/xvda1 ro"
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>         
Pressing enter doesn''t so anything. What am I doing wrong?

Would you mind telling me how you got the Windows CD installed?

-- 

Kind Regards
Rudi Ahlers
CEO, SoftDux

Web:   http://www.SoftDux.com
Check out my technical blog, http://blog.softdux.com for Linux or other
technical stuff, or visit http://www.WebHostingTalk.co.za for Web Hosting stuff


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

Gordon McLellan wrote on Mon, 7 Apr 2008 14:00:31 -0400:
> My only drawback at this time is soft-raid doesn''t handle
> multi user IO requests very well, the disk array gets swamped pretty
> easy when multiple VMs are trying to read/write at the same time.
So, for a high I/O DomUs you wouldn''t recommend it?

Kai

-- 
Kai Schätzl, Berlin, Germany
Get your web at Conactive Internet Services: http://www.conactive.com




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

Kai Schaetzl wrote:
> Gordon McLellan wrote on Mon, 7 Apr 2008 14:00:31 -0400:
> 
> > My only drawback at this time is soft-raid doesn''t handle
> > multi user IO requests very well, the disk array gets swamped pretty
> > easy when multiple VMs are trying to read/write at the same time.
> 
> So, for a high I/O DomUs you wouldn''t recommend it?
The soft-raid that you talk about wouldn''t happen to be a
raid5 or raid6?

In my tests of running a large number of VMs on top of RAID
is that you should use RAID10 as the io appears as a lot of
extremely random io traffic as each VM grabs a little data
from here or there all the time. The random io shouldn''t
be so high to require SAS unless you put a LARGE number of
VMs on 1 array, but 2 6 disk SATA RAID10s should handle up
to 20 VMs nicely.

This analysis is irrespective of whether you run hardware
RAID or software RAID.


-Ross

______________________________________________________________________
This e-mail, and any attachments thereto, is intended only for use by
the addressee(s) named herein and may contain legally privileged
and/or confidential information. If you are not the intended recipient
of this e-mail, you are hereby notified that any dissemination,
distribution or copying of this e-mail, and any attachments thereto,
is strictly prohibited. If you have received this e-mail in error,
please immediately notify the sender and permanently delete the
original and any copy or printout thereof.


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

Ross S. W. Walker wrote on Tue, 8 Apr 2008 10:15:48 -0400:
> The soft-raid that you talk about wouldn''t happen to be a
> raid5 or raid6?
No. I''m thinking of maximum 5 VMs in RAID1. Maximum 2 of them might
have
heavy I/O.
Do you just RAID the whole disk (except for Dom0 /boot) and then put LVM 
on top or do you use several RAID partitions and put the LVM on these (at 
least one partition for Dom0 and one for the DomUs)?

Kai

-- 
Kai Schätzl, Berlin, Germany
Get your web at Conactive Internet Services: http://www.conactive.com




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

Kai Schaetzl wrote:
> Ross S. W. Walker wrote on Tue, 8 Apr 2008 10:15:48 -0400:
> > The soft-raid that you talk about wouldn''t happen to be a
> > raid5 or raid6?
> 
> No. I''m thinking of maximum 5 VMs in RAID1. Maximum 2 of them
might have
> heavy I/O.
> 
> Do you just RAID the whole disk (except for Dom0 /boot) and then put LVM 
> on top or do you use several RAID partitions and put the LVM on these (at 
> least one partition for Dom0 and one for the DomUs)?
1 RAID1 for 5 VMs should be fine if they are good disks, nice size
buffer, NCQ capable, reputable manufacturer. For SATA I like the
Seagate 7200.10 series.

No, do RAID over whole disks if possible (normally for dom0 system disk
it needs to be split between /boot and the rest of the disk though, so
that gives 2 raid1s /dev/md0 and /dev/md1). RAID is really meant for
whole disk and the performance is measured in whole spindles, if you
mix RAIDs across the same spindles then performance will suffer in an
unpredictable fashion.

For this setup I suggest 2 disk raid1 for system, and separate 2 disk
raid1 for VMs.

-Ross

______________________________________________________________________
This e-mail, and any attachments thereto, is intended only for use by
the addressee(s) named herein and may contain legally privileged
and/or confidential information. If you are not the intended recipient
of this e-mail, you are hereby notified that any dissemination,
distribution or copying of this e-mail, and any attachments thereto,
is strictly prohibited. If you have received this e-mail in error,
please immediately notify the sender and permanently delete the
original and any copy or printout thereof.


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

Ross S. W. Walker wrote on Tue, 8 Apr 2008 12:12:00 -0400:
> No, do RAID over whole disks if possible (normally for dom0 system disk
> it needs to be split between /boot and the rest of the disk though, so
> that gives 2 raid1s /dev/md0 and /dev/md1). RAID is really meant for
> whole disk and the performance is measured in whole spindles, if you
> mix RAIDs across the same spindles then performance will suffer in an
> unpredictable fashion.
Ok, thanks for the info.
> 
> For this setup I suggest 2 disk raid1 for system, and separate 2 disk
> raid1 for VMs.
Not enough space in there. But I just ordered a cheap RAID controller 
which seems to be well supported on CentOS, I''ll try that first before
I
stay with software RAID.

Kai

-- 
Kai Schätzl, Berlin, Germany
Get your web at Conactive Internet Services: http://www.conactive.com




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