similar to: Error connecting USB-device to DomU, kernel 2.6.32-5-xen-amd64, Xen 4.0.1

Displaying 20 results from an estimated 200 matches similar to: "Error connecting USB-device to DomU, kernel 2.6.32-5-xen-amd64, Xen 4.0.1"

2012 Nov 23
1
Bug?
root@graff:~# xm usb-list-assignable-devices 1-6 : ID 14dd:0002 Peppercon AG Multidevice 2-2 : ID 051d:0002 American Power Conversion Smart-UPS 3000 RM XL FW:691.16.I USB FW:7.3 root@graff:~# xm usb-hc-create bosch-w2k3-pv 1 1 root@graff:~# xm usb-list bosch-w2k3-pv Idx BE state usb-ver BE-path 0 0 1 USB1.1 /local/domain/0/backend/vusb/55/0
2011 Jan 18
3
xm usb-add syntax
Hi all, Do any of you know what the syntax would be is I wanted to add the first device listed using lsusb on my dom0 to my domU? lsusb; Bus 002 Device 004: ID 064f:0bd8 Some-Systems AB ABC/DE xm usb-add; Usage: xm usb-add <domain> <[host:bus.addr] [host:vendor_id:product_id]> Unsure what combo works, other then what doesn''t work. - Brian
2011 Jul 27
3
USB at domU PV domain & PVUSB
Good Evenight I try to do working usb''s into domU xen guest, SO of xen server is Debian Squenze 6.0, into HVM guest usb works and can make use but with ParaVirtual guest PV can find this devices with lsusb or into /dev/ directory. Kernel load into xend and guest is the same and is the kernel provided by this package: ii linux-image-2.6.32-5-xen-amd64 2.6.32-35
2012 Jun 28
8
GPLPV, clock drift and PVUSB in Windows XP HVM
1. Shouldn''t the GPLPV drivers take care of the (bad) clock drift I''m experiencing in my Windows XP HVM? Or is there some other way around this problem that I haven''t been able to find on Google? How can I tell if the GPLPV drivers are active? I''ve added the /gplpv switch to the boot.ini file and the virtual NIC is definitely using the GPLPV version but other
2011 Sep 06
0
can''t passthrough usb devices to domU (Unexpected error: <class ''xen.util.vusb_util.UsbDeviceParseError''>)
Hello, I try to passthrough an usb 1.1 device (floppy drive) to a domU. Dom0 and domU are based on opensuse11.4. I did the follwowing in dom0 --snip-- xenserver:~ # xm usb-list-assignable-devices 3-1 : ID 0644:0000 TEAC TEAC FD-05PUB 3-2 : ID 0644:0000 TEAC TEAC FD-05PUB xenserver:~ # xm usb-hc-create vdrserver 1 2 xenserver:~ # xm usb-list vdrserver Idx BE
2011 Oct 19
8
Centos 5.7 Xen 4.1 AMD 64 from gitco cannot attach usb port to domU windows 7
Hi. Just wondering is someone have been able to connect usb memory sticks in xen 4.1-gitco running hvm windows 7? I use xen 4.1 from gitco, is working without any issue, I need support for a usb memory stick, but I had not been able to make this works. Reading xm commands and process, first my MB Biostar A780L3L v6 wont support IOMMU. Now exist a doc from xen wiki from someone from Fujitso
2012 Aug 15
5
PV USB Use Case for Xen 4.x
Good Afternoon. My colleague Stefan (sstan) was asked on the IRC channel to provide our use case for PV USB in our environment. This is possible with the current xm stack but not available with the xl stack. Currently we use PVUSB to attach a USB Smartcard reader through our dom0 (SLES 11 SP1) running on an HP Blade Server with the Token mounted on an internal USB Port to our domU CA server
2010 Aug 06
1
[PATCH]add usb-ver format check to avoid usb-list error and incorrect usb-ver saved into config file
Add usb-ver format check to "usb-hc-create". In original file, "usb-hc-create" allows usb-ver parameter as "2/2.0/2.0aaa". In low level hc create, it only uses the integer part (that is "2"), so there is no problem. But 2/2.0/2.0aaa will be saved into VM config. After that, while doing "usb-list", it cannot handle "2.0/2.0aaa" and will
2010 Jul 04
1
Ubuntu DomU does not finish booting up.
Hi there guys. I''m trying to setup an Ubuntu 9.04 DomU, it boot fine, but does finishes to load completelly, this is what I get. I''m using xen 4 Linux netwarrior 2.6.31.13 #7 SMP Wed Jun 30 18:09:49 ART 2010 x86_64 AMD Athlon(tm) II X4 630 Processor AuthenticAMD GNU/Linu * Skip starting firewall: ufw (not enabled)... [ OK ] * Configuring network
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]
2009 Sep 08
2
Can't configure wine anymore
When I type winecfg, I get all this > err:menubuilder:WinMain unknown option -a > err:menubuilder:WinMain unknown option -r > fixme:advapi:RegisterEventSourceW ((null),L"Print"): stub > fixme:winsock:convert_af_w2u unhandled Windows address family 26 > fixme:winsock:convert_af_w2u unhandled Windows address family 26 > fixme:winsock:convert_af_w2u unhandled Windows
2016 Dec 23
2
Cannot connect to Samab
jserinki7 jserink # netstat -lnptu Active Internet connections (only servers) Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name tcp 0 0 0.0.0.0:53 0.0.0.0:* LISTEN 3711/dnsmasq tcp 0 0 127.0.0.1:631 0.0.0.0:* LISTEN 2849/cupsd tcp 0 0 192.168.100.1:445
2011 Feb 07
4
XEN live migration: cannot console or ssh to the migrated guest VM (domU)
I am now testing XEN live migration on two physical hosts with XEN 4.0.1 pvops Ubuntu 10.10 (2.6.35-22). Host A also acts as a NFS server, and Host B acts as a NFS client. When I migrate a guest domain from B to A. The ssh connection experiences a downtime of about 1 minute (the terminal does not react to the keyboard input till about 1 minute later). However, the "sudo xm console" does
2011 Sep 25
1
Please report to - xm new
I installed the beta version of oneiric and got this error: root@g4-01:~# xm new Unexpected error: <type ''exceptions.ImportError''> Please report to xen-devel@lists.xensource.com Traceback (most recent call last): File "/usr/lib/xen-4.1/bin/xm", line 8, in <module> main.main(sys.argv) File
2010 May 04
1
xen-4.0.0: Could not connect to DomU console
Hi. I use xen-4.0.0 My domU successfully started, but when i tried to connect to DomU console i get error: root@debian-office:/opt/src/NexetaStor# xm console NexentaStor-EVAL-2.2.0 Unexpected error: <type ''exceptions.TypeError''> Please report to xen-devel@lists.xensource.com Traceback (most recent call last): File "/usr/sbin/xm", line 7, in <module>
2010 May 04
1
xen-4.0.0: Could not connect to DomU console
Hi. I use xen-4.0.0 My domU successfully started, but when i tried to connect to DomU console i get error: root@debian-office:/opt/src/NexetaStor# xm console NexentaStor-EVAL-2.2.0 Unexpected error: <type ''exceptions.TypeError''> Please report to xen-devel@lists.xensource.com Traceback (most recent call last): File "/usr/sbin/xm", line 7, in <module>
2008 May 16
1
xm new
Hello, i have Centos5.1 64bit, with xen3.2, using centos xen kernel, xen3.2 builded from source rpm for centos. Virtual machines work fine trough xm create configname ,but when i am trying to add them to xen source : xm new configname, this is what i get : [root at xen-prod xen]# xm new test01.hvm Unexpected error: exceptions.ImportError Please report to xen-devel at lists.xensource.com
2008 May 18
1
xen source (xm new machinename)
Hi, i am running Centos5.1 i386, with xen3.2.0 compiled from source rpms provided on xen.org. As dom0 kernel i am using centos-xen kernels. When i am trying to add new machine to xen source using xm new, this is what i get : [root@xxx /]# xm new centos01 Unexpected error: exceptions.ImportError Please report to xen-devel@lists.xensource.com Traceback (most recent call last): File
2012 Jul 01
1
xm crash
Ok, it says to send this so here it is: [root@xen lharold]# xm create xm_fedora.cfg Using config file "/etc/xen/xm_fedora.cfg". Started domain Fedora (id=2) [root@xen lharold]# xm new Fedora Unexpected error: <type ''exceptions.ImportError''> Please report to xen-devel@lists.xensource.com Traceback (most recent call last): File "/sbin/xm", line 7, in
2008 Oct 08
6
pci pass-through failure on xen 3.3.0
Hi all, I downloaded the xen 3.3.0 and now testing the pci pass-through with the NIC. Using late binding, the pci slot 0000:08:01.0 is assigned to pciback. But pci related xm commands are not working. For eg: linux-242:/home/xen-3.3.0 # xm pci-list-assignable-devices Unexpected error: <type ''exceptions.OSError''> Please report to