Xen users - May 2007 - Still having problems with xen guest boot

I don''t know what has happened because know I can''t even get
this guest
booting. The guest conf I think is correct:
kernel = "/boot/vmlinuz-2.6.18-8.1.4.el5xen"
builder=''linux''


memory = 384
name = "ns1"
vcpus = 1


#vif = [ ''mac=FE:FF:FF:FF:FF:FF , ip=139.185.48.214,
''bridge=xenbr1'' ]
vif = [ '''', ''bridge=xenbr1'' ]
disk = [ ''phy:/dev/VGvhosts/root.test.ns1,sda1,w'',
         ''phy:/dev/VGvhosts/swap.ns1,sda2,w'' ]

#dhcp="dhcp"

# Set root device.
root = "/dev/sda1 ro"
#bootloader="/usr/bin/pygrub"

And I always get:
[root@santos xen]# xm create ns1 -c
Using config file "./ns1".
Error: destroyDevice() takes exactly 3 arguments (2 given)

I run out of ideas. Tried with to use the ramdisk I allready had:
initrd-2.6.18-8.1.4.el5xen.img, and the same. Can''t make another one
since
I tried to find a kernel src, and the only thing I get is kernel rpm.

Anyone any idea ??? :( ???


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

> -----Original Message-----
> From: xen-users-bounces@lists.xensource.com 
> [mailto:xen-users-bounces@lists.xensource.com] On Behalf Of 
> Octavian Teodorescu
> Sent: 30 May 2007 14:37
> To: xen-users@lists.xensource.com
> Subject: [Xen-users] Still having problems with xen guest boot
> 
> I don''t know what has happened because know I can''t even
get
> this guest
> booting. The guest conf I think is correct:
> kernel = "/boot/vmlinuz-2.6.18-8.1.4.el5xen"
> builder=''linux''
> 
> 
> memory = 384
> name = "ns1"
> vcpus = 1
> 
> 
> #vif = [ ''mac=FE:FF:FF:FF:FF:FF , ip=139.185.48.214,
''bridge=xenbr1'' ]
> vif = [ '''', ''bridge=xenbr1'' ]
> disk = [ ''phy:/dev/VGvhosts/root.test.ns1,sda1,w'',
>          ''phy:/dev/VGvhosts/swap.ns1,sda2,w'' ]
> 
> #dhcp="dhcp"
> 
> # Set root device.
> root = "/dev/sda1 ro"
> #bootloader="/usr/bin/pygrub"
> 
> And I always get:
> [root@santos xen]# xm create ns1 -c
> Using config file "./ns1".
> Error: destroyDevice() takes exactly 3 arguments (2 given)
This indicates to me that you''ve got some sort of mixup. Which of the
three or four "destroyDevice()" functions is it? There should be a
calltrace in /var/log/xen/xend.log... Not that it will really help much
to know that, but at least it''s some help. [And it''s really a
consequence of the guest dying anyways, so it''s not particuarly helpful
to fix it]. 
> 
> I run out of ideas. Tried with to use the ramdisk I allready had:
> initrd-2.6.18-8.1.4.el5xen.img, and the same. Can''t make 
> another one since
> I tried to find a kernel src, and the only thing I get is kernel rpm.
You don''t need kernel SOURCES to build the initrd, just kernel
installation files (in particular the modules from the kernel). 

If you search for "mkinitrd xen guest" or some such in google, you
should be able to find the right command to add the necessary modules
for the guest setup. 

--
Mats
> 
> Anyone any idea ??? :( ???
> 
> 
> _______________________________________________
> 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

> -----Original Message-----
> From: Octavian Teodorescu [mailto:octav@inetsolutions.ro] 
> Sent: 30 May 2007 15:19
> To: Petersson, Mats
> Subject: RE: [Xen-users] Still having problems with xen guest boot
> 
> Ok. Sorry for sending mails not so well detailed.
> So:
> about lomount, it''s the first time I have heard of it :)
> I always used mount. From what I''ve seen so far it seems to me
that
> lomount just mounts images not logical volumes.
Yes, that''s correct. I''m not particuarly familiar with volume
groups, so
you may find better advice than mine from searching the Xen Users list
looking for how to set up volume groups - but as far as I understand it,
the volume group stuff is all hidden from the guest under normal
circumstances, and you should be able to mount the guest''s filesystem
in
your Dom0 in one way or another (assuming of course the guests
filesystem is supported in Dom0, which isn''t necessary at all - they
all
appear like block-devices from Dom0''s standpoint, and DomU is
responsible for deciding what the content of the blocks actually mean,
e.g. directory structures, free-block-lists, etc, etc). 
> 
> Because I''ve tried earlier to mount it manually and received 
> errors. Know
> it is not mounted when I''m doing xm create -c ns1. It just 
> has an entry in
> /etc/fstab:
> /dev/VGvhosts/root.ns1 /vhosts/ns1             ext3    
> defaults        0 0
> /dev/VGvhosts/swap.ns1 swap                    swap    
> defaults        0 0
So this is the devices for your guest, listed in Dom0''s fstab, yes? You
shouldn''t need to have any information for the guest within Dom0
outside
of the guest configuration file. Although the case where the guest
filesystem is mounted to Dom0 should be detected by the create-script,
so that''s unlikely to be your problem. 

I''m not that familiar with the setup for para-virtual, so if
I''m not
helping very directly, I''m sorry. I''m just trying to guide you
as best
as I can. There are others who have more experience than me on setting
up paravirtual domains - anyone who thinks they have better advice,
please pipe in. 

--
Mats
> 
> 
> >>
> >>
> >>> -----Original Message-----
> >>> From: Octavian Teodorescu [mailto:octav@inetsolutions.ro]
> >>> Sent: 30 May 2007 15:04
> >>> To: Petersson, Mats
> >>> Subject: RE: [Xen-users] Still having problems with xen guest
boot
> >>>
> >>> Ok, made what you said, and the same. In the ns1 config file
> >>> I have added:
> >>> ramdisk = "/boot/initrd-2.6.18-8.1.4.el5xen.img"
> >>> Which I have made with:
> >>> mkinitrd -v -f --with=ext3 --with=xenblk
> >>> /boot/initrd-2.6.18-8.1.4.el5xen.img 2.6.18-8.1.4.el5xen
> >>>
> >>> And the same error:
> >>> xm create ns1 -c
> >>> Using config file "./ns1".
> >>> Error: destroyDevice() takes exactly 3 arguments (2 given)
> >>
> >> This error is caused by the guest being killed, most 
> likely because you
> >> don''t have the right drivers in your initrd.
It''s no point
> in posting
> >> more xend-logs. A log of the console of the guest may be 
> more useful.
> >> Although if it''s still the same as your previously posted
> ones, then it
> >> may not help much.
> >>
> >> By the way, is your guest-filesystem mountable on your Dom0 using
> >> something like "lomount"?
> >>
> >> --
> >> Mats
> >>
> >>
> >>
> 
> 
> 
> 
> 


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

> #vif = [ ''mac=FE:FF:FF:FF:FF:FF , ip=139.185.48.214,
''bridge=xenbr1'' ]
> vif = [ '''', ''bridge=xenbr1'' ]
> disk = [ ''phy:/dev/VGvhosts/root.test.ns1,sda1,w'',
>          ''phy:/dev/VGvhosts/swap.ns1,sda2,w'' ]
Try xvda1 and xvda2 instead of sda*

The sd* IDs are a legacy thing which are being phased out, I believe.

Cheers,
Mark
> #dhcp="dhcp"
>
> # Set root device.
> root = "/dev/sda1 ro"
> #bootloader="/usr/bin/pygrub"
>
> And I always get:
> [root@santos xen]# xm create ns1 -c
> Using config file "./ns1".
> Error: destroyDevice() takes exactly 3 arguments (2 given)
>
> I run out of ideas. Tried with to use the ramdisk I allready had:
> initrd-2.6.18-8.1.4.el5xen.img, and the same. Can''t make another
one since
> I tried to find a kernel src, and the only thing I get is kernel rpm.
>
> Anyone any idea ??? :( ???
>
>
> _______________________________________________
> 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