Andrey Dmitriev
2007-Jun-25 00:13 UTC
[Xen-users] can''t start RH4 domU on RH5 dom0 Error: (22, ''Invalid argument'')
Someone help.... what am I missing.. has to be something simple. [root@mt-mail1 ~]# xm create /dev/null ramdisk=/mnt/software/initrd-2.6.9-55.ELxenU.img kernel=/mnt/software/vmlinuz-2.6.9-55.ELxenU name=ramdisk vcpus=2 memory=412 root=/dev/ram Using config file "/dev/null". Error: (22, ''Invalid argument'') [root@mt-mail1 ~]# xm create scalix2 Using config file "/etc/xen/scalix2". Error: (22, ''Invalid argument'') more /etc/xen/scalix2 kernel = "/mnt/software/vmlinuz-2.6.9-55.ELxenU" memory = 512 name = "hating-xen" vif = [''ip = "10.0.1.150", bridge=xen-br0''] disk = [''file:/mnt/software/RHEL4-U5-x86_64-ES-disc1.iso,cdrom,r'', ''phy:XEN/XEN-scalixroot ,sda1,w'' ,''phy:XEN/XEN-scalixvar,sda3,w'' ,''phy:XEN/swap.dokeos,sda2,w'' ] cdrom = "/mnt/software/RHEL4-U5-x86_64-ES-disc1.iso" root = "/dev/sda1 " _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Nico Kadel-Garcia
2007-Jun-25 04:21 UTC
Re: [Xen-users] can''t start RH4 domU on RH5 dom0 Error: (22, ''Invalid argument'')
Andrey Dmitriev wrote:> Someone help.... what am I missing.. has to be something simple. > > > [root@mt-mail1 ~]# xm create /dev/null > ramdisk=/mnt/software/initrd-2.6.9-55.ELxenU.img > kernel=/mnt/software/vmlinuz-2.6.9-55.ELxenU name=ramdisk vcpus=2 > memory=412 root=/dev/ram > Using config file "/dev/null". > Error: (22, ''Invalid argument'') > > > [root@mt-mail1 ~]# xm create scalix2 > Using config file "/etc/xen/scalix2". > Error: (22, ''Invalid argument'') > > more /etc/xen/scalix2 > kernel = "/mnt/software/vmlinuz-2.6.9-55.ELxenU" > memory = 512 > name = "hating-xen" > > vif = [''ip = "10.0.1.150", bridge=xen-br0''] > > disk = [''file:/mnt/software/RHEL4-U5-x86_64-ES-disc1.iso,cdrom,r'', > ''phy:XEN/XEN-scalixroot ,sda1,w'' > ,''phy:XEN/XEN-scalixvar,sda3,w'' > ,''phy:XEN/swap.dokeos,sda2,w'' > ] > > cdrom = "/mnt/software/RHEL4-U5-x86_64-ES-disc1.iso" > root = "/dev/sda1 " > >Why are your phy devices not full names? Like /dev/XEN/XEN-scalixroot? _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Mark Williamson
2007-Jun-27 00:12 UTC
Re: [Xen-users] can''t start RH4 domU on RH5 dom0 Error: (22, ''Invalid argument'')
> Someone help.... what am I missing.. has to be something simple.Hi, Please post the contents of your /var/log/xen/xend.log Cheers, Mark> [root@mt-mail1 ~]# xm create /dev/null > ramdisk=/mnt/software/initrd-2.6.9-55.ELxenU.img > kernel=/mnt/software/vmlinuz-2.6.9-55.ELxenU name=ramdisk vcpus=2 > memory=412 root=/dev/ram > Using config file "/dev/null". > Error: (22, ''Invalid argument'') > > > [root@mt-mail1 ~]# xm create scalix2 > Using config file "/etc/xen/scalix2". > Error: (22, ''Invalid argument'') > > more /etc/xen/scalix2 > kernel = "/mnt/software/vmlinuz-2.6.9-55.ELxenU" > memory = 512 > name = "hating-xen" > > vif = [''ip = "10.0.1.150", bridge=xen-br0''] > > disk = [''file:/mnt/software/RHEL4-U5-x86_64-ES-disc1.iso,cdrom,r'', > ''phy:XEN/XEN-scalixroot ,sda1,w'' > ,''phy:XEN/XEN-scalixvar,sda3,w'' > ,''phy:XEN/swap.dokeos,sda2,w'' > ] > > cdrom = "/mnt/software/RHEL4-U5-x86_64-ES-disc1.iso" > root = "/dev/sda1 " > > > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users-- Dave: Just a question. What use is a unicyle with no seat? And no pedals! Mark: To answer a question with a question: What use is a skateboard? Dave: Skateboards have wheels. Mark: My wheel has a wheel! _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Andrey Dmitriev
2007-Jul-17 04:07 UTC
RE: [Xen-users] can''t start RH4 domU on RH5 dom0 Error: (22, ''Invalid argument'')
Modified my config file as [root@mt-mail1 xen]# more /etc/xen/scalix2 #kernel = "/boot/vmlinuz" #ramdisk = "/boot/initrd.img" kernel="/mnt/software/vmlinuz-2.6.9-55.ELxenU" memory = 512 name = "hating-xen" vif = [''ip = "10.0.1.150", bridge=xenbr0''] disk = [ ''/dev/XEN/scalixroot,sda1,w'', ''/dev/XEN/scalixvar,sda3,w'', ''/dev/XEN/scalixswap,sda2,w'' ] BTW, it boots fine with vmlinuz, which is a CentOS xen kernel. However, it goes right into some installation, which I can''t seem to get out of. Does it really matter which kernel I run? And how can I avoid the installation menus. I also just discovered that I boot fine with vmlinuz-2.6.18-8.1.6.el5xen, but it pukes on mounting file systems. [root@mt-mail1 xen]# more xend.log [2007-07-16 23:59:37 xend.XendDomainInfo 3202] DEBUG (XendDomainInfo:190) XendDomainInfo.create([''vm'', [''name'', ''hating-xen''], [''memory'', 512 ], [''vcpus'', 1], [''image'', [''linux'', [''kernel'', ''/mnt/software/vmlinuz-2.6.9-55.ELxenU'']]], [''device'', [''vbd'', [''uname'', ''/dev/XEN/scalixroot ''], [''dev'', ''sda1''], [''mode'', ''w'']]], [''device'', [''vbd'', [''uname'', ''/dev/XEN/scalixvar''], [''dev'', ''sda3''], [''mode'', ''w'']]], [''device'', [''vbd'' , [''uname'', ''/dev/XEN/scalixswap''], [''dev'', ''sda2''], [''mode'', ''w'']]], [''device'', [''vif'', [''ip'', ''"10.0.1.150"''], [''bridge'', ''xenbr0'']]]]) [2007-07-16 23:59:37 xend.XendDomainInfo 3202] DEBUG (XendDomainInfo:296) parseConfig: config is [''vm'', [''name'', ''hating-xen''], [''memory'', 51 2], [''vcpus'', 1], [''image'', [''linux'', [''kernel'', ''/mnt/software/vmlinuz-2.6.9-55.ELxenU'']]], [''device'', [''vbd'', [''uname'', ''/dev/XEN/scalixroo t''], [''dev'', ''sda1''], [''mode'', ''w'']]], [''device'', [''vbd'', [''uname'', ''/dev/XEN/scalixvar''], [''dev'', ''sda3''], [''mode'', ''w'']]], [''device'', [''vbd '', [''uname'', ''/dev/XEN/scalixswap''], [''dev'', ''sda2''], [''mode'', ''w'']]], [''device'', [''vif'', [''ip'', ''"10.0.1.150"''], [''bridge'', ''xenbr0'']]]] [2007-07-16 23:59:37 xend.XendDomainInfo 3202] DEBUG (XendDomainInfo:397) parseConfig: result is {''shadow_memory'': None, ''start_time'': None, ''uuid'': None, ''on_crash'': None, ''on_reboot'': None, ''localtime'': None, ''image'': [''linux'', [''kernel'', ''/mnt/software/vmlinuz-2.6.9-55.ELxenU'']] , ''on_poweroff'': None, ''bootloader_args'': None, ''cpus'': None, ''name'': ''hating-xen'', ''backend'': [], ''vcpus'': 1, ''cpu_weight'': None, ''features'' : None, ''vcpu_avail'': None, ''memory'': 512, ''device'': [(''vbd'', [''vbd'', [''uname'', ''/dev/XEN/scalixroot''], [''dev'', ''sda1''], [''mode'', ''w'']]), (''v bd'', [''vbd'', [''uname'', ''/dev/XEN/scalixvar''], [''dev'', ''sda3''], [''mode'', ''w'']]), (''vbd'', [''vbd'', [''uname'', ''/dev/XEN/scalixswap''], [''dev'', ''sd a2''], [''mode'', ''w'']]), (''vif'', [''vif'', [''ip'', ''"10.0.1.150"''], [''bridge'', ''xenbr0'']])], ''bootloader'': None, ''cpu'': None, ''maxmem'': None} [2007-07-16 23:59:37 xend.XendDomainInfo 3202] DEBUG (XendDomainInfo:1264) XendDomainInfo.construct: None [2007-07-16 23:59:37 xend.XendDomainInfo 3202] DEBUG (XendDomainInfo:1296) XendDomainInfo.initDomain: 7 1.0 [2007-07-16 23:59:37 xend 3202] DEBUG (balloon:127) Balloon: 524528 KiB free; need 524288; done. [2007-07-16 23:59:37 xend 3202] INFO (image:136) buildDomain os=linux dom=7 vcpus=1 [2007-07-16 23:59:37 xend 3202] DEBUG (image:199) dom = 7 [2007-07-16 23:59:37 xend 3202] DEBUG (image:200) image = /mnt/software/vmlinuz-2.6.9-55.ELxenU [2007-07-16 23:59:37 xend 3202] DEBUG (image:201) store_evtchn = 1 [2007-07-16 23:59:37 xend 3202] DEBUG (image:202) console_evtchn = 2 [2007-07-16 23:59:37 xend 3202] DEBUG (image:203) cmdline [2007-07-16 23:59:37 xend 3202] DEBUG (image:204) ramdisk [2007-07-16 23:59:37 xend 3202] DEBUG (image:205) vcpus = 1 [2007-07-16 23:59:37 xend 3202] DEBUG (image:206) features [2007-07-16 23:59:37 xend.XendDomainInfo 3202] ERROR (XendDomainInfo:202) Domain construction failed Traceback (most recent call last): File "/usr/lib64/python2.4/site-packages/xen/xend/XendDomainInfo.py", line 195, in create vm.initDomain() File "/usr/lib64/python2.4/site-packages/xen/xend/XendDomainInfo.py", line 1377, in initDomain raise VmError(str(exn)) VmError: (22, ''Invalid argument'') [2007-07-16 23:59:37 xend.XendDomainInfo 3202] DEBUG (XendDomainInfo:1463) XendDomainInfo.destroy: domid=7 [2007-07-16 23:59:37 xend.XendDomainInfo 3202] DEBUG (XendDomainInfo:1471) XendDomainInfo.destroyDomain(7) -----Original Message----- From: Mark Williamson [mailto:mark.williamson@cl.cam.ac.uk] Sent: Tuesday, June 26, 2007 8:13 PM To: xen-users@lists.xensource.com Cc: Andrey Dmitriev Subject: Re: [Xen-users] can''t start RH4 domU on RH5 dom0 Error: (22, ''Invalid argument'')> Someone help.... what am I missing.. has to be something simple.Hi, Please post the contents of your /var/log/xen/xend.log Cheers, Mark> [root@mt-mail1 ~]# xm create /dev/null > ramdisk=/mnt/software/initrd-2.6.9-55.ELxenU.img > kernel=/mnt/software/vmlinuz-2.6.9-55.ELxenU name=ramdisk vcpus=2 > memory=412 root=/dev/ram > Using config file "/dev/null". > Error: (22, ''Invalid argument'') > > > [root@mt-mail1 ~]# xm create scalix2 > Using config file "/etc/xen/scalix2". > Error: (22, ''Invalid argument'') > > more /etc/xen/scalix2 > kernel = "/mnt/software/vmlinuz-2.6.9-55.ELxenU" > memory = 512 > name = "hating-xen" > > vif = [''ip = "10.0.1.150", bridge=xen-br0''] > > disk = [''file:/mnt/software/RHEL4-U5-x86_64-ES-disc1.iso,cdrom,r'', > ''phy:XEN/XEN-scalixroot ,sda1,w'' > ,''phy:XEN/XEN-scalixvar,sda3,w'' > ,''phy:XEN/swap.dokeos,sda2,w'' > ] > > cdrom = "/mnt/software/RHEL4-U5-x86_64-ES-disc1.iso" > root = "/dev/sda1 " > > > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users-- Dave: Just a question. What use is a unicyle with no seat? And no pedals! Mark: To answer a question with a question: What use is a skateboard? Dave: Skateboards have wheels. Mark: My wheel has a wheel! _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Nico Kadel-Garcia
2007-Jul-17 11:17 UTC
Re: [Xen-users] can''t start RH4 domU on RH5 dom0 Error: (22, ''Invalid argument'')
Andrey Dmitriev wrote:> Modified my config file as > > > [root@mt-mail1 xen]# more /etc/xen/scalix2 > #kernel = "/boot/vmlinuz" > #ramdisk = "/boot/initrd.img" > kernel="/mnt/software/vmlinuz-2.6.9-55.ELxenU" > > memory = 512 > name = "hating-xen" > > vif = [''ip = "10.0.1.150", bridge=xenbr0''] > > disk = [ > ''/dev/XEN/scalixroot,sda1,w'', > ''/dev/XEN/scalixvar,sda3,w'', > ''/dev/XEN/scalixswap,sda2,w'' > ] > > > BTW, it boots fine with vmlinuz, which is a CentOS xen kernel. However, > it goes right into some installation, which I can''t seem to get out of. > Does it really matter which kernel I run? And how can I avoid the > installation menus. > > I also just discovered that I boot fine with > vmlinuz-2.6.18-8.1.6.el5xen, but it pukes on mounting file systems. > > > [root@mt-mail1 xen]# more xend.log > [2007-07-16 23:59:37 xend.XendDomainInfo 3202] DEBUG > (XendDomainInfo:190) XendDomainInfo.create([''vm'', [''name'', > ''hating-xen''], [''memory'', 512 > ], [''vcpus'', 1], [''image'', [''linux'', [''kernel'', > ''/mnt/software/vmlinuz-2.6.9-55.ELxenU'']]], [''device'', [''vbd'', [''uname'', > ''/dev/XEN/scalixroot > ''], [''dev'', ''sda1''], [''mode'', ''w'']]], [''device'', [''vbd'', [''uname'', > ''/dev/XEN/scalixvar''], [''dev'', ''sda3''], [''mode'', ''w'']]], [''device'', > [''vbd'' > , [''uname'', ''/dev/XEN/scalixswap''], [''dev'', ''sda2''], [''mode'', ''w'']]], > [''device'', [''vif'', [''ip'', ''"10.0.1.150"''], [''bridge'', ''xenbr0'']]]]) > [2007-07-16 23:59:37 xend.XendDomainInfo 3202] DEBUG > (XendDomainInfo:296) parseConfig: config is [''vm'', [''name'', > ''hating-xen''], [''memory'', 51 > 2], [''vcpus'', 1], [''image'', [''linux'', [''kernel'', > ''/mnt/software/vmlinuz-2.6.9-55.ELxenU'']]], [''device'', [''vbd'', [''uname'', > ''/dev/XEN/scalixroo > t''], [''dev'', ''sda1''], [''mode'', ''w'']]], [''device'', [''vbd'', [''uname'', > ''/dev/XEN/scalixvar''], [''dev'', ''sda3''], [''mode'', ''w'']]], [''device'', > [''vbd > '', [''uname'', ''/dev/XEN/scalixswap''], [''dev'', ''sda2''], [''mode'', ''w'']]], > [''device'', [''vif'', [''ip'', ''"10.0.1.150"''], [''bridge'', ''xenbr0'']]]] > [2007-07-16 23:59:37 xend.XendDomainInfo 3202] DEBUG > (XendDomainInfo:397) parseConfig: result is {''shadow_memory'': None, > ''start_time'': None, > ''uuid'': None, ''on_crash'': None, ''on_reboot'': None, ''localtime'': None, > ''image'': [''linux'', [''kernel'', ''/mnt/software/vmlinuz-2.6.9-55.ELxenU'']] > , ''on_poweroff'': None, ''bootloader_args'': None, ''cpus'': None, ''name'': > ''hating-xen'', ''backend'': [], ''vcpus'': 1, ''cpu_weight'': None, ''features'' > : None, ''vcpu_avail'': None, ''memory'': 512, ''device'': [(''vbd'', [''vbd'', > [''uname'', ''/dev/XEN/scalixroot''], [''dev'', ''sda1''], [''mode'', ''w'']]), (''v > bd'', [''vbd'', [''uname'', ''/dev/XEN/scalixvar''], [''dev'', ''sda3''], [''mode'', > ''w'']]), (''vbd'', [''vbd'', [''uname'', ''/dev/XEN/scalixswap''], [''dev'', ''sd > a2''], [''mode'', ''w'']]), (''vif'', [''vif'', [''ip'', ''"10.0.1.150"''], > [''bridge'', ''xenbr0'']])], ''bootloader'': None, ''cpu'': None, ''maxmem'': > None} > [2007-07-16 23:59:37 xend.XendDomainInfo 3202] DEBUG > (XendDomainInfo:1264) XendDomainInfo.construct: None > [2007-07-16 23:59:37 xend.XendDomainInfo 3202] DEBUG > (XendDomainInfo:1296) XendDomainInfo.initDomain: 7 1.0 > [2007-07-16 23:59:37 xend 3202] DEBUG (balloon:127) Balloon: 524528 KiB > free; need 524288; done. > [2007-07-16 23:59:37 xend 3202] INFO (image:136) buildDomain os=linux > dom=7 vcpus=1 > [2007-07-16 23:59:37 xend 3202] DEBUG (image:199) dom = 7 > [2007-07-16 23:59:37 xend 3202] DEBUG (image:200) image = > /mnt/software/vmlinuz-2.6.9-55.ELxenU > [2007-07-16 23:59:37 xend 3202] DEBUG (image:201) store_evtchn = 1 > [2007-07-16 23:59:37 xend 3202] DEBUG (image:202) console_evtchn = 2 > [2007-07-16 23:59:37 xend 3202] DEBUG (image:203) cmdline > [2007-07-16 23:59:37 xend 3202] DEBUG (image:204) ramdisk > [2007-07-16 23:59:37 xend 3202] DEBUG (image:205) vcpus = 1 > [2007-07-16 23:59:37 xend 3202] DEBUG (image:206) features > [2007-07-16 23:59:37 xend.XendDomainInfo 3202] ERROR > (XendDomainInfo:202) Domain construction failed > Traceback (most recent call last): > File "/usr/lib64/python2.4/site-packages/xen/xend/XendDomainInfo.py", > line 195, in create > vm.initDomain() > File "/usr/lib64/python2.4/site-packages/xen/xend/XendDomainInfo.py", > line 1377, in initDomain > raise VmError(str(exn)) > VmError: (22, ''Invalid argument'') > [2007-07-16 23:59:37 xend.XendDomainInfo 3202] DEBUG > (XendDomainInfo:1463) XendDomainInfo.destroy: domid=7 > [2007-07-16 23:59:37 xend.XendDomainInfo 3202] DEBUG > (XendDomainInfo:1471) XendDomainInfo.destroyDomain(7) > > -----Original Message----- > From: Mark Williamson [mailto:mark.williamson@cl.cam.ac.uk] > Sent: Tuesday, June 26, 2007 8:13 PM > To: xen-users@lists.xensource.com > Cc: Andrey Dmitriev > Subject: Re: [Xen-users] can''t start RH4 domU on RH5 dom0 Error: (22, > ''Invalid argument'') > > >> Someone help.... what am I missing.. has to be something simple. >> > > Hi, > > Please post the contents of your /var/log/xen/xend.log > > Cheers, > Mark > > >> [root@mt-mail1 ~]# xm create /dev/null >> ramdisk=/mnt/software/initrd-2.6.9-55.ELxenU.img >> kernel=/mnt/software/vmlinuz-2.6.9-55.ELxenU name=ramdisk vcpus=2 >> memory=412 root=/dev/ram >> Using config file "/dev/null". >> Error: (22, ''Invalid argument'') >> >> >> [root@mt-mail1 ~]# xm create scalix2 >> Using config file "/etc/xen/scalix2". >> Error: (22, ''Invalid argument'') >> >> more /etc/xen/scalix2 >> kernel = "/mnt/software/vmlinuz-2.6.9-55.ELxenU" >> memory = 512 >> name = "hating-xen" >> >> vif = [''ip = "10.0.1.150", bridge=xen-br0''] >> >> disk = [''file:/mnt/software/RHEL4-U5-x86_64-ES-disc1.iso,cdrom,r'', >> ''phy:XEN/XEN-scalixroot ,sda1,w'' >> ,''phy:XEN/XEN-scalixvar,sda3,w'' >> ,''phy:XEN/swap.dokeos,sda2,w'' >> ] >> >> cdrom = "/mnt/software/RHEL4-U5-x86_64-ES-disc1.iso" >> root = "/dev/sda1 " >> >>Can you use virt-install to get pygrub set up, and that way you use a grub and kernel from the Xen guest domain itself? I''ve moved away from doiing that sort of "sda1", "sda2", "sda3" filesystem allocation: I use "xvda" or "sda" so I can do more synchronous snapshots, and use kpartx to get access to individual file systems from Dom0. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Scott Serr
2007-Jul-18 02:06 UTC
Re: [Xen-users] can''t start RH4 domU on RH5 dom0 Error: (22, ''Invalid argument'')
I went through the process of getting CentOS 4.5 installed in the last 2 days, it''s fresh on my mind what you need to do. Comments below. Nico Kadel-Garcia wrote:> Andrey Dmitriev wrote: >> Modified my config file as >> >> >> [root@mt-mail1 xen]# more /etc/xen/scalix2 >> #kernel = "/boot/vmlinuz" >> #ramdisk = "/boot/initrd.img" >> kernel="/mnt/software/vmlinuz-2.6.9-55.ELxenU" >> >> memory = 512 >> name = "hating-xen" >> >> vif = [''ip = "10.0.1.150", bridge=xenbr0''] >> >> disk = [ >> ''/dev/XEN/scalixroot,sda1,w'', >> ''/dev/XEN/scalixvar,sda3,w'', >> ''/dev/XEN/scalixswap,sda2,w'' >> ] >> >> >> BTW, it boots fine with vmlinuz, which is a CentOS xen kernel. >> However, it goes right into some installation, which I can''t seem to >> get out of. Does it really matter which kernel I run? And how can I >> avoid the installation menus.You are using an initrd image to match the CentOS xen kernel? The initrd image that I am using (for install) is SPECIFIC to installation, i.e. it has different stuff than the initrd that is installed. The vmlinuz kernel here http://mirror.centos.org/centos/4.5/os/i386/images/xen/ is identical to what is installed once CentOS 4.5 is installed.>> >> I also just discovered that I boot fine with >> vmlinuz-2.6.18-8.1.6.el5xen, but it pukes on mounting file systems.What initrd are you using at that point? This could be the problem. You will want kernel modules to match your kernel... and you get that by matching the initrd.img to the vmlinuz. <snip> I can''t sort out what you are doing below because the replies where a mess and not properly threaded.>>> [root@mt-mail1 ~]# xm create /dev/null >>> ramdisk=/mnt/software/initrd-2.6.9-55.ELxenU.img >>> kernel=/mnt/software/vmlinuz-2.6.9-55.ELxenU name=ramdisk vcpus=2 >>> memory=412 root=/dev/ram<snip>>>> disk = [''file:/mnt/software/RHEL4-U5-x86_64-ES-disc1.iso,cdrom,r'', >>> ''phy:XEN/XEN-scalixroot ,sda1,w'' >>> ,''phy:XEN/XEN-scalixvar,sda3,w'' >>> ,''phy:XEN/swap.dokeos,sda2,w'' >>> ] >>> >>> cdrom = "/mnt/software/RHEL4-U5-x86_64-ES-disc1.iso" >>> root = "/dev/sda1 "no CD You need to read XenSource User Guide even if you only use the open source stuff possibly from your dom0 distro. The reason is, it tells you that RHEL4/CentOS4 can NOT be installed off of a CD or iso image. You must install from the network, NFS worked for me. no sda image I found that The CentOS 4.5 kernel (and I''m sure the RHEL4u5 kernel) would not work with "sda" style front end names. You seem to have to use "xvda." no xvda1 image Also the CentOS 4.5 kernel does not understand an "xvda1" partition popping up without the stuff that an entire disk would give it like a partition table. So you have to have a full disk image. (I could be wrong, you might have found something there that works.) This page is good for reference, but assumes you have pygrub which I don''t with a dom0 of SLES10SP1: http://wiki.centos.org/HowTos/Xen/InstallingCentOSDomU Here is my config for INSTALL purposes: name = "centos" memory = "256" disk = [ ''file:/root/cent/cent-xvda.img,xvda,w'' ] vif = [ ''bridge=xenbr1,mac=00:16:3E:0A:95:28'' ] vcpus=1 on_reboot = ''destroy'' on_crash = ''destroy'' vfb = [ ''type=vnc'' ] kernel = "/root/cent/vmlinuz-boot" ramdisk = "/root/cent/initrd-boot" After the install I modify the config (so I don''t get taken into the install again!): name = "centos" memory = "256" disk = [ ''file:/root/cent/cent-xvda.img,xvda,w'' ] vif = [ ''bridge=xenbr1,mac=00:16:3E:0A:95:28'' ] vcpus=1 on_reboot = ''restart'' on_crash = ''destroy'' vfb = [ ''type=vnc'' ] kernel = "/root/cent/vmlinuz" ramdisk = "/root/cent/initrd" extra = "ro root=/dev/xvda1" I''m now using the extra parameter and an initrd from INSIDE the installed image (in xvda1:/boot/). This was tricky to grab from outside the image, and I had to without pygrub. SLES/SLED have stopped shipping pygrub because it is broken on their platform, they use domUloader for now. So I got it out by booting like I was going to install CentOS again, but then I used this in my ''install'' config for one more boot: extra = "rescue" This allowed me to go into "rescue mode" and with networking and I did something like this: cd /mnt/sysimage/boot rsync vmlinuz-2.6.9-55.ELxenU initrd-2.6.9-55.ELxenU.img root@dom0:. All this cleverness because. 1... pygrub is not there on SLES. 2.... I couldn''t find a boot loader that would work without completely upgrading to xensource''s xen. 3... I didn''t know how to loop back mount the partition since it was buried in an entire disk image. 4. I couldn''t use individual images per partition, because the kernel seems old and not understanding partitions without a parition table. Hope this helps you... and maybe others. -Scott Serr _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users