search for: destroydevice

Displaying 20 results from an estimated 60 matches for "destroydevice".

Did you mean: destroy_device
domU's being killed - strange?
2012 Mar 27
2
domU's being killed - strange?
...stB.log [2012-03-27 15:57:52 2225] DEBUG (XendDomainInfo:2452) Destroying device model [2012-03-27 15:57:52 2225] DEBUG (XendDomainInfo:2459) Releasing devices [2012-03-27 15:57:52 2225] DEBUG (XendDomainInfo:2465) Removing vif/0 [2012-03-27 15:57:52 2225] DEBUG (XendDomainInfo:1294) XendDomainInfo.destroyDevice: deviceClass = vif, device = vif/0 [2012-03-27 15:57:52 2225] WARNING (XendDomainInfo:2108) Domain has crashed: name=GuestB id=98. [2012-03-27 15:57:52 2225] DEBUG (XendDomainInfo:2465) Removing vkbd/0 [2012-03-27 15:57:52 2225] DEBUG (XendDomainInfo:1294) XendDomainInfo.destroyDevice: deviceClass...
Bug#636552: xen-hypervisor-4.1-i386: Error: Device 0 (vif) could not be connected. Hotplug scripts not working.
2011 Aug 03
1
Bug#636552: xen-hypervisor-4.1-i386: Error: Device 0 (vif) could not be connected. Hotplug scripts not working.
...domid=2 [2011-08-03 15:58:33 4411] DEBUG (XendDomainInfo:2401) Destroying device model [2011-08-03 15:58:33 4411] DEBUG (XendDomainInfo:2408) Releasing devices [2011-08-03 15:58:33 4411] DEBUG (XendDomainInfo:2414) Removing vif/0 [2011-08-03 15:58:33 4411] DEBUG (XendDomainInfo:1276) XendDomainInfo.destroyDevice: deviceClass = vif, device = vif/0 [2011-08-03 15:58:33 4411] DEBUG (XendDomainInfo:2414) Removing console/0 [2011-08-03 15:58:33 4411] DEBUG (XendDomainInfo:1276) XendDomainInfo.destroyDevice: deviceClass = console, device = console/0 [2011-08-03 15:58:33 4411] DEBUG (XendDomainInfo:2414) Removing...
Error creating vm xen3.4
2009 Jun 25
0
Error creating vm xen3.4
...9;) [2009-06-25 17:59:42 13862] DEBUG (XendDomainInfo:2198) Destroying device model [2009-06-25 17:59:42 13862] DEBUG (XendDomainInfo:2205) Releasing devices [2009-06-25 17:59:42 13862] DEBUG (XendDomainInfo:2218) Removing vif/0 [2009-06-25 17:59:42 13862] DEBUG (XendDomainInfo:1133) XendDomainInfo.destroyDevice: deviceClass = vif, device = vif/0 [2009-06-25 17:59:42 13862] DEBUG (XendDomainInfo:2218) Removing vbd/768 [2009-06-25 17:59:42 13862] DEBUG (XendDomainInfo:1133) XendDomainInfo.destroyDevice: deviceClass = None, device = vbd/768 [2009-06-25 17:59:42 13862] ERROR (XendDomainInfo:2225) Device relea...
Task blocked for more than 120 seconds.
2013 Mar 06
4
Task blocked for more than 120 seconds.
Hi all, Today I got problem below and my domU become unresponsive and I should restart the pc to make it running properly again. [ 240.172092] INFO: task kworker/u:0:5 blocked for more than 120 seconds. [ 240.172110] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 240.172376] INFO: task jbd2/xvda1-8:153 blocked for more than 120 seconds. [ 240.172388]
Error: Device 768 (vbd) could not be connected. Path closed or removed during hotplug add: backend/vbd/9/768 state: 1
2010 Jun 06
3
Error: Device 768 (vbd) could not be connected. Path closed or removed during hotplug add: backend/vbd/9/768 state: 1
...device model [2010-06-07 01:24:06 1573] INFO (image:615) win7 device model terminated [2010-06-07 01:24:06 1573] DEBUG (XendDomainInfo:2418) Releasing devices [2010-06-07 01:24:06 1573] DEBUG (XendDomainInfo:2424) Removing vif/0 [2010-06-07 01:24:06 1573] DEBUG (XendDomainInfo:1286) XendDomainInfo.destroyDevice: deviceClass = vif, device = vif/0 [2010-06-07 01:24:06 1573] DEBUG (XendDomainInfo:2424) Removing console/0 [2010-06-07 01:24:06 1573] DEBUG (XendDomainInfo:1286) XendDomainInfo.destroyDevice: deviceClass = console, device = console/0 [2010-06-07 01:24:06 1573] DEBUG (XendDomainInfo:2424) Removing...
[PATCH] del xend entry when destroy pv usb host controller of a guest os with no pv-frontend driver
2010 Mar 26
0
[PATCH] del xend entry when destroy pv usb host controller of a guest os with no pv-frontend driver
...DeviceController(deviceClass).frontendPath(dev) backpath = xstransact.Read(frontpath, "backend") thread.start_new_thread(self.getDeviceController(deviceClass).finishDeviceCleanup, (backpath, path)) - - rc = self.getDeviceController(deviceClass).destroyDevice(devid, force) + if deviceClass ==''vusb'': + dev = self.getDeviceController(deviceClass).convertToDeviceNumber(devid) + state = self.getDeviceController(deviceClass).readBackend(dev, ''state'') + if state == ...
SXCE104, Cannot boot HVM domain
2009 Feb 26
4
SXCE104, Cannot boot HVM domain
...26 18:02:11 552] DEBUG (XendDomainInfo:1893) XendDomainInfo.destroy: domid=8 [2009-02-26 18:02:11 552] DEBUG (XendDomainInfo:1912) XendDomainInfo.destroyDomain(8) [2009-02-26 18:02:11 552] DEBUG (XendDomainInfo:1542) Removing vif/0 [2009-02-26 18:02:11 552] DEBUG (XendDomainInfo:603) XendDomainInfo.destroyDevice: deviceClass = vif, device = vif/0 [2009-02-26 18:02:11 552] DEBUG (XendDomainInfo:1542) Removing vbd/768 [2009-02-26 18:02:11 552] DEBUG (XendDomainInfo:603) XendDomainInfo.destroyDevice: deviceClass = vbd, device = vbd/768 [2009-02-26 18:02:11 552] DEBUG (XendDomainInfo:1542) Removing vbd/5632 [2...
device model failure: no longer running;
2009 Feb 14
2
device model failure: no longer running;
...st: device model failure: no longer running; see /var/log/xen/qemu-dm-xenXPtest.log [2009-02-13 17:55:44 2952] DEBUG (XendDomainInfo:1946) Releasing devices [2009-02-13 17:55:44 2952] DEBUG (XendDomainInfo:1959) Removing vbd/768 [2009-02-13 17:55:44 2952] DEBUG (XendDomainInfo:910) XendDomainInfo.destroyDevice: deviceClass = None, device = vbd/768 [2009-02-13 17:55:44 2952] ERROR (XendDomainInfo:1966) Device release failed: xenXPtest; None; vbd/768 Traceback (most recent call last): File "//usr/lib64/python/xen/xend/XendDomainInfo.py", line 1960, in _releaseDevices self.destroyDevice(true_dev...
Xen 4.0.1 + 2.6.18-194.32.1.el5xen CentOS Dom0
2011 Jan 17
0
Xen 4.0.1 + 2.6.18-194.32.1.el5xen CentOS Dom0
...d=4 [2011-01-17 15:45:27 3368] DEBUG (XendDomainInfo:2411) Destroying device model [2011-01-17 15:45:27 3368] DEBUG (XendDomainInfo:2418) Releasing devices [2011-01-17 15:45:27 3368] DEBUG (XendDomainInfo:2424) Removing vif/0 [2011-01-17 15:45:27 3368] DEBUG (XendDomainInfo:1286) XendDomainInfo.destroyDevice: deviceClass = vif, device = vif/0 [2011-01-17 15:45:27 3368] DEBUG (XendDomainInfo:2424) Removing vbd/768 [2011-01-17 15:45:27 3368] DEBUG (XendDomainInfo:1286) XendDomainInfo.destroyDevice: deviceClass = vbd, device = vbd/768 [2011-01-17 15:45:27 3368] DEBUG (XendDomainInfo:2424) Removing vfb/...
DomUs don''t shutdown with cpu-pinning configured
2009 Jun 29
0
DomUs don''t shutdown with cpu-pinning configured
...in repair: device model failure: no longer running; see /var/log/xen/qemu-dm-repair.log [2009-06-30 00:27:01 5294] DEBUG (XendDomainInfo:1946) Releasing devices [2009-06-30 00:27:01 5294] DEBUG (XendDomainInfo:1952) Removing vif/0 [2009-06-30 00:27:01 5294] DEBUG (XendDomainInfo:888) XendDomainInfo.destroyDevice: deviceClass = vif, device = vif/0 [2009-06-30 00:27:01 5294] DEBUG (XendDomainInfo:1952) Removing vbd/768 [2009-06-30 00:27:01 5294] DEBUG (XendDomainInfo:888) XendDomainInfo.destroyDevice: deviceClass = vbd, device = vbd/768 [2009-06-30 00:27:01 5294] DEBUG (XendDomainInfo:1952) Removing vfb/0 [2...
Can''t create my seventh xen vm on rhel5
2007 Nov 13
2
Can''t create my seventh xen vm on rhel5
Hi I''m a sysadmin and I''ve installed on my server Red Hat Enterprise Linux 5 to use its xen embedded with six virtual machines just created and running. Now I have a problem: when I attempt to create my seventh virtual machine, xen gives me this error: Error: destroyDevice() takes exactly 3 arguments (2 given) In /var/log/xen/xend.log find this errors: [2007-11-13 11:34:00 xend 3471] ERROR (xmlrpclib2:184) destroyDevice() takes exactly 3 arguments (2 given) Traceback (most recent call last):   File "/usr/lib/python2.4/site-packages/xen/util/xmlrpclib2.py&quo...
vhd format support failed on suse11 x86_64 sp2
2012 Oct 17
0
vhd format support failed on suse11 x86_64 sp2
...model [2012-10-25 17:51:56 6523] INFO (image:615) Windows device model terminated [2012-10-25 17:51:56 6523] DEBUG (XendDomainInfo:2411) Releasing devices [2012-10-25 17:51:56 6523] DEBUG (XendDomainInfo:2417) Removing tap2/51712 [2012-10-25 17:51:56 6523] DEBUG (XendDomainInfo:1277) XendDomainInfo.destroyDevice: deviceClass = tap2, device = tap2/51712 [2012-10-25 17:51:56 6523] DEBUG (XendDomainInfo:2417) Removing vif/0 [2012-10-25 17:51:56 6523] DEBUG (XendDomainInfo:1277) XendDomainInfo.destroyDevice: deviceClass = vif, device = vif/0 [2012-10-25 17:51:56 6523] DEBUG (XendDomainInfo:2417) Removing tap/5...
HVM domain can not boot up with Qcow incremental image
2010 Jul 22
1
HVM domain can not boot up with Qcow incremental image
...domid=16 [2010-07-22 23:31:39 4609] DEBUG (XendDomainInfo:1939) Destroying device model [2010-07-22 23:31:39 4609] DEBUG (XendDomainInfo:1946) Releasing devices [2010-07-22 23:31:39 4609] DEBUG (XendDomainInfo:1959) Removing vif/0 [2010-07-22 23:31:39 4609] DEBUG (XendDomainInfo:910) XendDomainInfo.destroyDevice: deviceClass = vif, device = vif/0 [2010-07-22 23:31:39 4609] WARNING (image:472) domain winXP: device model failure: no longer running; see /var/log/xen/qemu-dm-winXP.log [2010-07-22 23:31:39 4609] DEBUG (XendDomainInfo:1959) Removing vbd/768 [2010-07-22 23:31:39 4609] DEBUG (XendDomainInfo:910)...
Still having problems with xen guest boot
2007 May 30
3
Still having problems with xen guest boot
...1,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 ??? :( ??? __________...
Stub domains broken in Xen 4.0?
2011 Jan 30
0
Stub domains broken in Xen 4.0?
...l terminated [2011-01-30 12:45:23 3430] DEBUG (XendDomainInfo:2459) stopping xenpaging [2011-01-30 12:45:23 3430] DEBUG (XendDomainInfo:2466) Releasing devices [2011-01-30 12:45:23 3430] DEBUG (XendDomainInfo:2472) Removing vif/0 [2011-01-30 12:45:23 3430] DEBUG (XendDomainInfo:1296) XendDomainInfo.destroyDevice: deviceClass = vif, device = vif/0 [2011-01-30 12:45:23 3430] DEBUG (XendDomainInfo:2472) Removing vkbd/0 [2011-01-30 12:45:23 3430] DEBUG (XendDomainInfo:1296) XendDomainInfo.destroyDevice: deviceClass = vkbd, device = vkbd/0 [2011-01-30 12:45:23 3430] DEBUG (image:608) createDeviceModel 1: orig_s...
DRBD VBD script not working in squeeze ?
2011 Jan 23
1
DRBD VBD script not working in squeeze ?
...omid=56 [2011-01-23 09:43:03 2112] DEBUG (XendDomainInfo:2411) Destroying device model [2011-01-23 09:43:03 2112] DEBUG (XendDomainInfo:2418) Releasing devices [2011-01-23 09:43:03 2112] DEBUG (XendDomainInfo:2424) Removing vif/0 [2011-01-23 09:43:03 2112] DEBUG (XendDomainInfo:1286) XendDomainInfo.destroyDevice: deviceClass = vif, device = vif/0 [2011-01-23 09:43:03 2112] DEBUG (XendDomainInfo:2424) Removing vbd/51712 [2011-01-23 09:43:03 2112] DEBUG (XendDomainInfo:1286) XendDomainInfo.destroyDevice: deviceClass = vbd, device = vbd/51712 [2011-01-23 09:43:03 2112] DEBUG (XendDomainInfo:2424) Removing con...
Re: Error: Device 0 (vif) could not be connected.Hotplugscripts not working
2010 Feb 26
1
Re: Error: Device 0 (vif) could not be connected.Hotplugscripts not working
...domid=3 [2010-02-26 09:26:25 2337] DEBUG (XendDomainInfo:2207) Destroying device model [2010-02-26 09:26:25 2337] DEBUG (XendDomainInfo:2214) Releasing devices [2010-02-26 09:26:25 2337] DEBUG (XendDomainInfo:2227) Removing vif/0 [2010-02-26 09:26:25 2337] DEBUG (XendDomainInfo:1134) XendDomainInfo.destroyDevice: deviceClass = vif, device = vif/0 [2010-02-26 09:26:25 2337] DEBUG (XendDomainInfo:2227) Removing console/0 [2010-02-26 09:26:25 2337] DEBUG (XendDomainInfo:1134) XendDomainInfo.destroyDevice: deviceClass = console, device = console/0 [2010-02-26 09:26:25 2337] DEBUG (XendDomainInfo:2227) Removing...
Xen 3.2 @ Debian 5.0 / Debian 4.0 DomU crashes daily
2009 Jul 28
0
Xen 3.2 @ Debian 5.0 / Debian 4.0 DomU crashes daily
...main(90) [2009-07-27 12:24:33 5312] DEBUG (XendDomainInfo:1529) Destroying device model [2009-07-27 12:24:33 5312] DEBUG (XendDomainInfo:1536) Releasing devices [2009-07-27 12:24:33 5312] DEBUG (XendDomainInfo:1542) Removing vif/0 [2009-07-27 12:24:33 5312] DEBUG (XendDomainInfo:590) XendDomainInfo.destroyDevice: deviceClass = vif, device = vif/0 [2009-07-27 12:24:33 5312] DEBUG (XendDomainInfo:1542) Removing vbd/2049 [2009-07-27 12:24:33 5312] DEBUG (XendDomainInfo:590) XendDomainInfo.destroyDevice: deviceClass = vbd, device = vbd/2049 [2009-07-27 12:24:33 5312] DEBUG (XendDomainInfo:1542) Removing vbd/20...
xm create: Error: Device 0 (vif) could not be connected. Hotplug scripts not working.
2009 Nov 19
3
xm create: Error: Device 0 (vif) could not be connected. Hotplug scripts not working.
Hi All, I am new to xen community. I am trying to setup Xen3.4.2 +FC11 Dom0 environs for lennovo T400. I have installed all prerequisite component for running xen and booted it. while I am trying to create DomU I am getting following error. I tried doing googling but none of suggested solution is working for me. Please guide me through my first experience with xen.for more details please see
Hotplug scripts not working
2011 May 31
3
Hotplug scripts not working
...bb:cc:dd:ee:ff > Error: Device 51712 (vbd) could not be connected. Hotplug scripts not working. However xm seems to disregard any output from the block-prefix script. xend.log hangs a few minutes on the following lines: > [2011-05-31 14:28:41 1894] DEBUG (XendDomainInfo:1286) XendDomainInfo.destroyDevice: deviceClass = vbd, device = vbd/51712 > [2011-05-31 14:28:41 1894] DEBUG (DevController:628) hotplugStatusCallback /local/domain/0/backend/vbd/55/51712/hotplug-status. > [2011-05-31 14:28:41 1894] DEBUG (DevController:628) hotplugStatusCallback /local/domain/0/backend/vbd/55/51712/hotplug-st...