search for: deviceclass

Displaying 20 results from an estimated 126 matches for "deviceclass".

Did you mean: bdeviceclass
[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
...t; diff -r f42ff98a2cdc tools/python/xen/xend/XendDomainInfo.py --- a/tools/python/xen/xend/XendDomainInfo.py Thu Mar 25 09:32:21 2010 +0000 +++ b/tools/python/xen/xend/XendDomainInfo.py Fri Mar 26 13:27:25 2010 +0800 @@ -1305,8 +1305,15 @@ frontpath = self.getDeviceController(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)...
domU's being killed - strange?
2012 Mar 27
2
domU's being killed - strange?
...3-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 = vkbd, devic...
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]
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.
...8-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 vbd/2050 [20...
program fails to enumerate COM ports
2009 Jul 18
3
program fails to enumerate COM ports
...registry: [HKEY_LOCAL_MACHINE\Hardware\DEVICEMAP\SERIALCOMM] "COM5"="COM5" env WINEDEBUG=+reg wine "C:\Program Files\LGGSM\LGPCSync\LGPCSync.exe" & then open "options" dialog: Code: trace:reg:NtOpenKey (0x28,L"System\\CurrentControlSet\\Control\\DeviceClasses",20019,0x32e1a4) trace:reg:NtOpenKey <- (nil) trace:reg:NtOpenKey (0x28,L"SYSTEM\\CurrentControlSet\\Services\\Modem\\Enum",20019,0x32e51c) trace:reg:NtOpenKey <- (nil) If you create "DeviceClasses" then it scans 2 keys inside: {4D36E978-E325-11CE-BFC1-08002BE10...
Error creating vm xen3.4
2009 Jun 25
0
Error creating vm xen3.4
...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 release failed: y;...
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
...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 vbd/768 [201...
SXCE104, Cannot boot HVM domain
2009 Feb 26
4
SXCE104, Cannot boot HVM domain
...] 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 [2009-02-26 18:...
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
...7 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/0 [2011-01-1...
DomUs don''t shutdown with cpu-pinning configured
2009 Jun 29
0
DomUs don''t shutdown with cpu-pinning configured
...ce 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 [2009-06-30 00:...
vhd format support failed on suse11 x86_64 sp2
2012 Oct 17
0
vhd format support failed on suse11 x86_64 sp2
...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/51728 [2012-10...
[PATCH] [XEND] Remove hard tabs
2006 Sep 20
15
[PATCH] [XEND] Remove hard tabs
...f7d90f962967 tools/python/xen/xend/XendDomainInfo.py --- a/tools/python/xen/xend/XendDomainInfo.py Tue Sep 19 14:26:47 2006 +0100 +++ b/tools/python/xen/xend/XendDomainInfo.py Wed Sep 20 14:20:52 2006 -0500 @@ -1093,15 +1093,15 @@ class XendDomainInfo: ## public: def destroyDevice(self, deviceClass, devid): - if type(devid) is str: - devicePath = ''%s/device/%s'' % (self.dompath, deviceClass) - for entry in xstransact.List(devicePath): - backend = xstransact.Read(''%s/%s'' % (devicePath, entry), "backend") - devName = xstransact.Read(backend...
Stub domains broken in Xen 4.0?
2011 Jan 30
0
Stub domains broken in Xen 4.0?
...011-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_state is None,...
DRBD VBD script not working in squeeze ?
2011 Jan 23
1
DRBD VBD script not working in squeeze ?
...1-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 console/0 [2011-...
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
...2-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 vbd/2054 [20...
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
...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/2050 [2009-07-2...
Error: Device 0 (vif) could notbeconnected. Hotplugscripts not working
2010 May 28
13
Error: Device 0 (vif) could notbeconnected. Hotplugscripts not working
Hi All, I''m having a similar issue as Ian Tobin some weeks ago here: http://lists.xensource.com/archives/html/xen-users/2010-02/msg00645.html I''m using Debian Squeeze amd64, downloaded the experimental debian xen-amd64 kernel with pv_ops support. linux-headers-2.6.32-5-common-xen_2.6.32-13_amd64.deb linux-headers-2.6.32-5-xen-amd64_2.6.32-13_amd64.deb
Bug#706543: xen-hypervisor-4.1-amd64: HVM PCI Passthrough not working any more after last upgrade
2013 May 01
6
Bug#706543: xen-hypervisor-4.1-amd64: HVM PCI Passthrough not working any more after last upgrade
....1/bin/../lib/python/xen/xend/XendDomainInfo.py", line 970, in pci_device_configure devid = self._createDevice('pci', existing_pci_conf) File "/usr/lib/xen-4.1/bin/../lib/python/xen/xend/XendDomainInfo.py", line 2326, in _createDevice return self.getDeviceController(deviceClass).createDevice(devConfig) File "/usr/lib/xen-4.1/bin/../lib/python/xen/xend/server/DevController.py", line 67, in createDevice self.setupDevice(config) File "/usr/lib/xen-4.1/bin/../lib/python/xen/xend/server/pciif.py", line 453, in setupDevice self.setupOneDevice(d)...
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
...> 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-status. ... a...