I'm seeing this now as well. It may be a new regression. Next time a
changeset is hit where this config works without any issues let me know
- I'm not having much luck.
-bash-3.00# xm create -f builddomain.cfg -c
Using config file "builddomain.cfg".
Error: Error creating domain: int argument required
# unremarkable config that worked yesterday
-bash-3.00# cat builddomain.cfg
kernel = "vmlinuz"
memory = 512
name = "test"
vcpus = 4
vif = [ 'mac=aa:00:00:00:00:00, bridge=xen-br0' ]
#disk = [ 'file:newfs.00.vbd,hda,w' ]
disk = [ 'phy:loop2,hda1,w' ]
dhcp="dhcp"
root = "/dev/hda1 ro"
# the device is setup
-bash-3.00# losetup /dev/loop2
/dev/loop2: [000c]:4383807 (newfs.01.vbd), offset 16384
# the device node name is readily available
-bash-3.00# ls -l /dev/hda1
brw-rw-r-- 1 root root 3, 1 Sep 21 16:46 /dev/hda1
The backtrace from xend-debug.log:
raceback (most recent call last):
File "/usr/lib/python/xen/xend/server/SrvDomainDir.py", line 78, in op_create
dominfo = self.xd.domain_create(config)
File "/usr/lib/python/xen/xend/XendDomain.py", line 273, in domain_create
dominfo = XendDomainInfo.create(self.dbmap.getPath(), config)
File "/usr/lib/python/xen/xend/XendDomainInfo.py", line 146, in create
vm.construct()
File "/usr/lib/python/xen/xend/XendDomainInfo.py", line 719, in construct
self.info['bootloader']))
File "/usr/lib/python/xen/xend/image.py", line 158, in initDomain
log.debug("initDomain: cpu=%d mem_kb=%d ssidref=%d dom=%d", cpu, mem_kb, ssidref, dom)
File "/usr/lib/python2.3/logging/__init__.py", line 879, in debug
apply(self._log, (DEBUG, msg, args), kwargs)
File "/usr/lib/python2.3/logging/__init__.py", line 994, in _log
self.handle(record)
File "/usr/lib/python2.3/logging/__init__.py", line 1004, in handle
self.callHandlers(record)
File "/usr/lib/python2.3/logging/__init__.py", line 1037, in callHandlers
hdlr.handle(record)
File "/usr/lib/python2.3/logging/__init__.py", line 592, in handle
self.emit(record)
File "/usr/lib/python2.3/logging/handlers.py", line 102, in emit
msg = "%s\n" % self.format(record)
File "/usr/lib/python2.3/logging/__init__.py", line 567, in format
return fmt.format(record)
File "/usr/lib/python2.3/logging/__init__.py", line 362, in format
record.message = record.getMessage()
File "/usr/lib/python2.3/logging/__init__.py", line 233, in getMessage
msg = msg % self.args
TypeError: int argument required
On 9/21/05, Ewan Mellor <ewan@xxxxxxxxxxxxx> wrote:
On Wed, Sep 21, 2005 at 02:54:27PM -0500, David F Barrera wrote:
> On Wed, 2005-09-21 at 12:14 -0700, Ignatia Suwarna wrote: > > Here is my domU config: > > kernel="/boot/vmlinuz-2.6.12-1.1447_FC4xenU
" > > memory=64 > > name="rawhide" > > nics=1 > > disk=['file:/root/fedora.img, sda1, w'] > > root="/dev/sda1" > > extra="rp selinux=0 3"
> > > > I also started over with hda1, since there is /dev/hda1, but it gave > > the same error: > > Error creating domain, int required. > > > > Is this a known issue? Or something wrong with my config??
> > I think it is a bug. I am seeing this problem, too, using the latest hg > pull, changeset 6987. I have opened up a bugzilla report on it, #246. > >
http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=246 > > x335b:/tmp/xen # xm create -c vm1.cfg > Using config file "vm1.cfg". > Error: Error creating domain: int argument required
> x335b:/tmp/xen #
Do you have anything useful in /var/log/xend-debug.log? Type errors like this usually appear there.
Ewan.
_______________________________________________ Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx http://lists.xensource.com/xen-devel
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|