I would suggest that you contact redhat that supplied you with this
package. It may be that it's a bug in 3.0.4-1 standard, but it could
also be a bug created by redhat themselves.
I don't know what's going on here, as I said, I work on the several
hundred changes different unstable tree (because that's where I can add
new features such as SVM save/restore).
--
Mats
> -----Original Message-----
> From: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
> [mailto:xen-users-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of
> ggerber@xxxxxxxxxxxxx
> Sent: 30 January 2007 15:58
> To: Petersson, Mats; ggerber@xxxxxxxxxxxxx;
> xen-users@xxxxxxxxxxxxxxxxxxx
> Subject: RE: [Xen-users] Xen noob and a destroyDevice error
>
> Hi Mats
>
> Thanks for this and so you know DevController.py does come up
> in /etc/xen/xend.log, you can see below. On opening up
> DevController.py, this is the first time i have opened a
> python script b.t.w., i can see in fact there is a force flag...
>
> So where to from here, can I do something like "yum remove
> xen" and then "yum install xen-previous-version"?
>
> Many thanks
> G
>
>
> File
> "/usr/lib/python2.4/site-packages/xen/xend/server/DevControlle
> r.py", line 145, in waitForDevices
> return map(self.waitForDevice, self.deviceIDs())
> File
> "/usr/lib/python2.4/site-packages/xen/xend/server/DevControlle
> r.py", line 154, in waitForDevice
> self.destroyDevice(devid)
> TypeError: destroyDevice() takes exactly 3 arguments (2 given)
>
>
>
>
>
> ----- Original Message ------
> From:Petersson, Mats
> Sent:Tuesday, January 30, 2007 16:20
> To: ggerber@xxxxxxxxxxxxx; xen-users@xxxxxxxxxxxxxxxxxxx;
> Subject:RE: [Xen-users] Xen noob and a destroyDevice error
>
>
>
> > -----Original Message-----
> > From: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
> > [mailto:xen-users-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of
> > ggerber@xxxxxxxxxxxxx
> > Sent: 30 January 2007 14:57
> > To: xen-users@xxxxxxxxxxxxxxxxxxx
> > Subject: [Xen-users] Xen noob and a destroyDevice error
> >
> > Hello all
> >
> > The chaps at XenServer directed me to this mailing list and
> > to my surprise found 2 very recent hits on the error I am
> > receiving. Is it a bug perhaps?
> >
> > Jordi logged this:
> > http://lists.xensource.com/archives/html/xen-users/2007-01/msg
> > 01270.html
> >
> > and Shawn logged this one:
> > http://lists.xensource.com/archives/html/xen-users/2007-01/msg
> > 00892.html
> >
> > Here is more detail on my problem, please let me know if you
> > have found anything to date.
> >
> > On following the "Concise instructions for installing a
> > CentOS VM on Xen"
> > http://mark.foster.cc/wiki/index.php/Centos-4_on_Xen
> > using a FC6 host and Oracle EL4 guest I am able to create the
> > LVM partition,
> > bootstrap etc. without any errors however when I attempt to
> > create the VM a
> > destroyDevice error is given.
> >
> > So you know I have attempted to boot with the FC6 xen kernel first
> > (2.6.19-1.2895.fc6xen) and then installed the Red Hat xen kernel
> > vmlinuz-2.6.16.33-xen_3.0.4.1 by chroot and then rpm -ivh
> > kernel-xen...
> > I wonder if the kernel is correct!?!
> >
> > # xm create -c el4-1
> >
> > gives...
> >
> > "Using config file "/etc/xen/el4-1".
> > Error: destroyDevice() takes exactly 3 arguments (2 given)"
>
> The KERNEL is most likely entirely correct. This is an error message
> generated by xm, which (as I explained in a previous post) has several
> functions called destroyDevice.
>
> It's very likely that your build of the Xen packages is
> broken. My guess
> (and it is REALLY JUST A GUESS) is that 3.0.4-1 is somehow
> got broken.
>
> I work on Xen-unstable, so I don't follow that well what's going on in
> the Xen 3.0.4 tree. I tried having a look at the Xen 3.0.4 Mercurial
> release, but there doesn't appear to be anything in there that's got
> destroyDevice in it [although I only spent a minute or so
> looking at the
> patches].
>
> It is also possible that RedHat has messed up - they may have
> "backported" some changes and in the process lost some part
> of a change
> that affects the number of arguments someplace.
>
> There is a suspicious[1] patch in unstable, from the 15 Dec 2006 that
> adds a "Force flag" to calls to destroyDevice in DevController.py. If
> someone at RedHat grabbed this patch by mistake or not realizing the
> consequences in some other way, it may well have caused problems.
>
> I'm sorry if this is not really that helpful.
>
> If the other posters with the same problem have also been using RedHat
> builds of Xen, that would be a good key to work from. If not, then
> that's probably also a useful knowledge.
>
> [1]Nothing WRONG with the patch itself, it's just that it happens to
> change the code in a way that could cause the error message reported.
>
> --
> Mats
> >
> > "xm list" while "xm create" is running
> > --------------------------------------
> > # xm list
> > Name ID Mem(MiB) VCPUs State Time(s)
> > Domain-0 0 1892 2 r----- 2100.2
> > el4-1 24 96 1 --p--- 0.0
> >
> >
> > /etc/xen/el4-1 config file:
> > ------------------
> > [root@localhost mnt]# cat /etc/xen/el4-1
> > kernel = "/root/boot/vmlinuz-2.6.16.33-xen_3.0.4.1"
> > # also used FC6: kernel = "/boot/vmlinuz-2.6.19-1.2895.fc6xen"
> > memory = 96
> > name = "el4-1"
> > disk = [
> > 'phy:/dev/VolGroup01/LogVol01,sdb1,w','phy:/dev/VolGroup01/Log
> > Vol02,sdb2,w' ]
> > dhcp="dhcp"
> > root = "/dev/sdb1 ro"
> >
> > guest fstab:
> > ------------
> > [root@localhost mnt]# cat fstab
> > /dev/sdb1 / ext3 defaults 1 1
> > none /dev/pts devpts gid=5,mode=620 0 0
> > none /dev/shm tmpfs defaults 0 0
> > proc /proc proc defaults 0 0
> > /dev/sdb2 swap swap defaults 0 0
> >
> >
> >
> >
> >
> >
> >
> >
>
>
>
> _______________________________________________
> Xen-users mailing list
> Xen-users@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-users
>
>
>
>
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
|
Home