Hi, I''ve got XEN kernel(2.6.18-5) running nicely on my debian etch box but I''ve got a problem when adding a new vps client. After running xm create /etc/xen/xen1.domain.com.cfg I get this error Error: int argument required My xen1.domain.com.conf is here: http://paste.servut.us/lnv At the moment I''ve got no domains related to this server, I hope this is not the cause. I googled this error and noticed that there has been some bug which caused this error. Here is my xen_tools.conf: http://paste.servut.us/qfr I''ve been following this howto http://www.howtoforge.com/debian_etch_xen_3.1_p3 Can anyone help me to fix this problem? _________________________________________________________________ Lataa 30 ILMAISTA hymiötä Windows Live Messengeriisi! http://www.livemessenger-emoticons.com/fi-fi _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Jarkko Ypäjä wrote:> Hi, > > I''ve got XEN kernel(2.6.18-5) running nicely on my debian etch box but > I''ve got a problem when adding a new vps client. > > After running xm create /etc/xen/xen1.domain.com.cfg I get this error > Error: int argument required > > My xen1.domain.com.conf is here: http://paste.servut.us/lnv >I believe that here is the problem: root = ''/dev/md1 ro'' disk = [ ''file:/vserver/domains/xen1.xxxx.com/disk.img,md1,w'', ''file:/vserver/domains/xen1.xxxx.com/swap.img,md2,w'' ] First of all, try to use other devices than md1. I think more appropriate is hda, hdb, hdd, hdc,..., sda, sdb, sdd,... Or you can try to load the image disk by mda. And I don''t understand why do you need to load root filesystem with ''ro'' parametar? In my configurations I use hd{a..z} and it is working. Maybe you can also solve your problem if you specify the parametar: device_model Regards. Note: The disk.img and swap.img will be recognized as two separate disks, and not like a part of one disk. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
I think the problem might be with your memory line. change it from: memory = ''32'' to: memory = 32 Regards, Todd On Feb 12, 2008 12:51 PM, Jarkko Ypäjä <jarkko.ypaja@hotmail.com> wrote:> > Hi, > > I''ve got XEN kernel(2.6.18-5) running nicely on my debian etch box but I''ve > got a problem when adding a new vps client. > > After running xm create /etc/xen/xen1.domain.com.cfg I get this error > Error: int argument required > > My xen1.domain.com.conf is here: http://paste.servut.us/lnv > > At the moment I''ve got no domains related to this server, I hope this is not > the cause. I googled this error and noticed that there has been some bug > which caused this error. > > Here is my xen_tools.conf: http://paste.servut.us/qfr > > I''ve been following this howto > http://www.howtoforge.com/debian_etch_xen_3.1_p3 > > Can anyone help me to fix this problem? > > ________________________________ > Ota nyt käyttöösi uuden sukupolven Windows Live palvelut! Klikkaa! > _______________________________________________ > 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
Jarkko Ypäjä wrote:> I think Pesov gave me the right direction. > > I checked dev/ and there wasn''t even md2, so basicly that config is > totally wrong. > > The problem is that I''ve no idea where I could find out > what(sda,sda2,sdb,sdb1,md etc) to put in those settings :/If you read xen documentation about disk parametar, it says: Defines the disk devices you want the domain to have access to, and what you want them accessible as. If using a physical device as the VMX guest''s disk, each disk entry is of the form phy:UNAME,ioemu:DEV,MODE, where UNAME is the device, DEV is the device name the domain will see, and MODE is r for read-only, w for read-write. ioemu means the disk will use ioemu to virtualize the VMX disk. If not adding ioemu, it uses vbd like paravirtualized guests. If using disk image file, its form should be like file:FILEPATH,ioemu:DEV,MODE If using more than one disk, there should be a comma between each disk entry. For example: disk = [''file:/var/images/image1.img,ioemu:hda,w'', ''file:/var/images/image2.img,ioemu:hdb,w''] You see that you don''t have to have these devices on your Dom0, those devices are sent to the host machine. I had problems about this also. The following configuration was not working: disk = [''file:/storage/xen/dom1/vm-base.img,ioemu:sda1,w''] I suppose because sdX devices are SCSI, SATA, devices so the the loader couldn''t map them in that way. After specifying: ramdisk = ''/boot/initrd.img-2.6.18-5-xen-amd64'' kernel = ''/usr/lib/xen-3.0.3-1/boot/hvmloader'' builder=''hvm'' device_model=''/usr/lib/xen-3.0.3-1/bin/qemu-dm'' The configuration with using file based virtual disk was working with hdX declaration of DEV option. Also I have read that file-based VBDs are deprecated with use of loopback driver and using blktap driver and using tap:aio insead of file: will solve problems. For using logical volume as disk, I had to add ioemu option. Try removing ''ro'' from the declarations for the root parametar and try adding ioemu option. Todd''s suggestion about the problem is also correct. You should specify the amount of memory in the way: memory = 32 Regards, Vlado _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users