Hi, It seems there's a problem on 2.6.19-1.2895.fc6xen xen kernel and the xm tool: creating a new VM it aborts showing this error:
[root@inf16 ~]# xm create /etc/xen/rata.cfg Using config file "/etc/xen/rata.cfg". Error: destroyDevice() takes exactly 3 arguments (2 given) [root@inf16 ~]#
Anyone knows what is causing this? On the xen-users list there's some other messages related to this isue (one mine). Mats Petersson say that this may be causes by a backport.
There's something broken on the package? There's any easy workarround?
Thank you,
On Tue, Jan 30, 2007 at 10:28:32PM +0100, Jordi Prats wrote:
Hi, It seems there's a problem on 2.6.19-1.2895.fc6xen xen kernel and the xm tool: creating a new VM it aborts showing this error:
[root@inf16 ~]# xm create /etc/xen/rata.cfg Using config file "/etc/xen/rata.cfg". Error: destroyDevice() takes exactly 3 arguments (2 given) [root@inf16 ~]#
Anyone knows what is causing this? On the xen-users list there's some other messages related to this isue (one mine). Mats Petersson say that this may be causes by a backport.
Its a bug in one of the other patches we applied to the Xen RPM. I'll fix it in the next release.
There's something broken on the package? There's any easy workarround?
The error above isn't actually the root cause of your problems. What's happened is that the hotplug scripts for your domain failed to complete for some reason. Then when XenD is cleaning up from that failure, we hit the bug above. So wrt to debugging your actual problems, ignore the error message above. Instead look for a mis-configuration in either your virtual network card or virtual disk config params.
Regards, Dan.
Ok, thank you!
How long will take for the next release?
On the other hand, I can't ignore that error because I can't create any virtual machine, so Xen does nothing. On redhat 5 b2 it happens the same. I've changed my servers to FC6 because of this.
Daniel P. Berrange wrote:
On Tue, Jan 30, 2007 at 10:28:32PM +0100, Jordi Prats wrote:
Hi, It seems there's a problem on 2.6.19-1.2895.fc6xen xen kernel and the xm tool: creating a new VM it aborts showing this error:
[root@inf16 ~]# xm create /etc/xen/rata.cfg Using config file "/etc/xen/rata.cfg". Error: destroyDevice() takes exactly 3 arguments (2 given) [root@inf16 ~]#
Anyone knows what is causing this? On the xen-users list there's some other messages related to this isue (one mine). Mats Petersson say that this may be causes by a backport.
Its a bug in one of the other patches we applied to the Xen RPM. I'll fix it in the next release.
There's something broken on the package? There's any easy workarround?
The error above isn't actually the root cause of your problems. What's happened is that the hotplug scripts for your domain failed to complete for some reason. Then when XenD is cleaning up from that failure, we hit the bug above. So wrt to debugging your actual problems, ignore the error message above. Instead look for a mis-configuration in either your virtual network card or virtual disk config params.
Regards, Dan.
On Tue, Jan 30, 2007 at 11:04:45PM +0100, Jordi Prats wrote:
Ok, thank you!
How long will take for the next release?
Probably a few days before it goes to updates-testing, so don't expect it to go to updates for at least a week
On the other hand, I can't ignore that error because I can't create any virtual machine, so Xen does nothing. On redhat 5 b2 it happens the same. I've changed my servers to FC6 because of this.
Urm - read my explanation below again....
The 'Error: destroyDevice() takes exactly 3 arguments (2 given)' problem is *NOT* what is causing your guest to fail. It is merely obscuring the underlying failure - an updated RPM will remove up the 'destroyDevice' misleading message, but it won't magically make your guest work again.
The fundamental problem is a configuration issue with your guest's virtual disk or networking. Once you fix the config problem, the guest will work just fine, with or without an updated RPM for the 'destroyDevice' issue
Daniel P. Berrange wrote:
On Tue, Jan 30, 2007 at 10:28:32PM +0100, Jordi Prats wrote:
Hi, It seems there's a problem on 2.6.19-1.2895.fc6xen xen kernel and the xm tool: creating a new VM it aborts showing this error:
[root@inf16 ~]# xm create /etc/xen/rata.cfg Using config file "/etc/xen/rata.cfg". Error: destroyDevice() takes exactly 3 arguments (2 given) [root@inf16 ~]#
Anyone knows what is causing this? On the xen-users list there's some other messages related to this isue (one mine). Mats Petersson say that this may be causes by a backport.
Its a bug in one of the other patches we applied to the Xen RPM. I'll fix it in the next release.
There's something broken on the package? There's any easy workarround?
The error above isn't actually the root cause of your problems. What's happened is that the hotplug scripts for your domain failed to complete for some reason. Then when XenD is cleaning up from that failure, we hit the bug above. So wrt to debugging your actual problems, ignore the error message above. Instead look for a mis-configuration in either your virtual network card or virtual disk config params.
Dan.
Hi again, It seems to me that really are a problem here. I've created a new virtual machine, but after shuting down it I can't create it again. The error reported is:
[root@inf16 ssh]# xm create /etc/xen/granit.cfg -c Using config file "/etc/xen/granit.cfg". Error: destroyDevice() takes exactly 3 arguments (2 given)
Thanks, Jordi
Daniel P. Berrange wrote:
On Tue, Jan 30, 2007 at 11:04:45PM +0100, Jordi Prats wrote:
Ok, thank you!
How long will take for the next release?
Probably a few days before it goes to updates-testing, so don't expect it to go to updates for at least a week
On the other hand, I can't ignore that error because I can't create any virtual machine, so Xen does nothing. On redhat 5 b2 it happens the same. I've changed my servers to FC6 because of this.
Urm - read my explanation below again....
The 'Error: destroyDevice() takes exactly 3 arguments (2 given)' problem is *NOT* what is causing your guest to fail. It is merely obscuring the underlying failure - an updated RPM will remove up the 'destroyDevice' misleading message, but it won't magically make your guest work again.
The fundamental problem is a configuration issue with your guest's virtual disk or networking. Once you fix the config problem, the guest will work just fine, with or without an updated RPM for the 'destroyDevice' issue
Daniel P. Berrange wrote:
On Tue, Jan 30, 2007 at 10:28:32PM +0100, Jordi Prats wrote:
Hi, It seems there's a problem on 2.6.19-1.2895.fc6xen xen kernel and the xm tool: creating a new VM it aborts showing this error:
[root@inf16 ~]# xm create /etc/xen/rata.cfg Using config file "/etc/xen/rata.cfg". Error: destroyDevice() takes exactly 3 arguments (2 given) [root@inf16 ~]#
Anyone knows what is causing this? On the xen-users list there's some other messages related to this isue (one mine). Mats Petersson say that this may be causes by a backport.
Its a bug in one of the other patches we applied to the Xen RPM. I'll fix it in the next release.
There's something broken on the package? There's any easy workarround?
The error above isn't actually the root cause of your problems. What's happened is that the hotplug scripts for your domain failed to complete for some reason. Then when XenD is cleaning up from that failure, we hit the bug above. So wrt to debugging your actual problems, ignore the error message above. Instead look for a mis-configuration in either your virtual network card or virtual disk config params.
Dan.
Hi,
I just got the same problem after an update to the last xen & kernel on FC5 system. I had 4 of my 5 virtual machines up but the 5th did not start and gave me this 'destroyDevice()' error. I searched a little to understand I mounted manually the volume disk I use for this machine and that was the problem... Just unmounting it and retry solved my problem.
So if you have mounted manually the disk image of your virtual machine, try to unmount it before starting your virtual machine.
Regards,
Guillaume Bougard.
Le mardi 30 janvier 2007 à 22:05 +0000, Daniel P. Berrange a écrit :
On Tue, Jan 30, 2007 at 11:04:45PM +0100, Jordi Prats wrote:
Ok, thank you!
How long will take for the next release?
Probably a few days before it goes to updates-testing, so don't expect it to go to updates for at least a week
On the other hand, I can't ignore that error because I can't create any virtual machine, so Xen does nothing. On redhat 5 b2 it happens the same. I've changed my servers to FC6 because of this.
Urm - read my explanation below again....
The 'Error: destroyDevice() takes exactly 3 arguments (2 given)' problem is *NOT* what is causing your guest to fail. It is merely obscuring the underlying failure - an updated RPM will remove up the 'destroyDevice' misleading message, but it won't magically make your guest work again.
The fundamental problem is a configuration issue with your guest's virtual disk or networking. Once you fix the config problem, the guest will work just fine, with or without an updated RPM for the 'destroyDevice' issue
Daniel P. Berrange wrote:
On Tue, Jan 30, 2007 at 10:28:32PM +0100, Jordi Prats wrote:
Hi, It seems there's a problem on 2.6.19-1.2895.fc6xen xen kernel and the xm tool: creating a new VM it aborts showing this error:
[root@inf16 ~]# xm create /etc/xen/rata.cfg Using config file "/etc/xen/rata.cfg". Error: destroyDevice() takes exactly 3 arguments (2 given) [root@inf16 ~]#
Anyone knows what is causing this? On the xen-users list there's some other messages related to this isue (one mine). Mats Petersson say that this may be causes by a backport.
Its a bug in one of the other patches we applied to the Xen RPM. I'll fix it in the next release.
There's something broken on the package? There's any easy workarround?
The error above isn't actually the root cause of your problems. What's happened is that the hotplug scripts for your domain failed to complete for some reason. Then when XenD is cleaning up from that failure, we hit the bug above. So wrt to debugging your actual problems, ignore the error message above. Instead look for a mis-configuration in either your virtual network card or virtual disk config params.
Dan.
On Fri, Feb 23, 2007 at 10:36:04AM +0100, Guillaume Bougard wrote:
Hi,
I just got the same problem after an update to the last xen & kernel on FC5 system. I had 4 of my 5 virtual machines up but the 5th did not start and gave me this 'destroyDevice()' error. I searched a little to understand I mounted manually the volume disk I use for this machine and that was the problem... Just unmounting it and retry solved my problem.
For anyone on Fedora Core 6 seeing this destroyDevice() issue, an update is available in updates-testing which addresses it, so you can see the root cause error. The package is xen-3.0.3-6.fc6
I'll look at doing an update for FC5 too.
Dan.
-
Daniel P. Berrange -
Guillaume Bougard -
Jordi Prats