Re: [Xen-devel] [XEN][ARM64] PV DRM failing to convert virtual to physical address
Hello Oleksandr, Please find the attached log file. Could please provide some pointers on how test DomU display. On Tue, Dec 18, 2018 at 12:06 PM Oleksandr Andrushchenko wrote: Hello, Vikram! > * We are using 64 bit arm platform. > * Linux 4.20 Kernel in DomU with PV DRM front-end drivers. > >> Do you have [1] enabled in your DomD kernel? Earlier this configuration was not enabled. Enabled it now. > > * Xen-4.12 unstable version. > >> We never tested PV DRM with 4.12 so far, did you try with 4.10 for example? Xen-4.8 is working on our platform. Xen-4.9 to Xen-4.11 version fails while initializing CPU on our platform. Recently we received patch from Julien for Xen-4.12 unstable version, which has fix. Tried to apply patch on Xen-4.10 stable facing build issue. This is where we are at the moment and have all PV drivers running smoothly > * Able to build displ_be application and also its dependencies. > > Added below configuration in Domain-U config file.*| > |* > *|vdispl = [ 'backend=Domain-0,be-alloc=0,connectors=HDMI-A-1:1920x1080']|* > >> Do you really have DomD as your configuration says? Sorry it not DomD it is Domain-0. >> Not Dom0 running the backend? Domain-0 is running in Dom0 and debian is running as DomU. > Before launching the DomU ran the displ_be application in the > background. > $ displ_be -m DRM -v *:Debug & Please add display back-end logs > > Started Domain-U. > $ xl create -c debian.cfg > >> Could you please build the PV DRM driver as module, >> Built as module. then run the following commands: echo 0xff > /sys/module/drm/parameters/debug echo 8 > /proc/sys/kernel/printk >> and get back with DRM logs in DomU? Please find the attached log file -- Thanks & Regards Vikram KS -- This message contains confidential information and is intended only for the individual(s) named. If you are not the intended recipient, you are notified that disclosing, copying, distributing or taking any action in reliance on the contents of this mail and attached file/s is strictly prohibited. Please notify the sender immediately and delete this e-mail from your system. E-mail transmission cannot be guaranteed to be secured or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. The sender therefore does not accept liability for any errors or omissions in the contents of this message, which arise as a result of e-mail transmission. === $ displ_be -m DRM -v *:Debug & 19.12.18 05:13:11.447 | Main | INF - backend version: v0.2.1-5-g7fc0-dirty 19.12.18 05:13:11.454 | Main | INF - libxenbe version: v0.2.1-2-g6769-dirty 19.12.18 05:13:11.461 | Drm | DBG - Create Drm card: /dev/dri/card0, FD: 3 19.12.18 05:13:11.476 | Drm | DBG - Connector id: 30, name: HDMI-A-1, connected: 1 19.12.18 05:13:11.485 | XenStore | DBG - Create xen store 19.12.18 05:13:11.490 | XenStore | DBG - Read string domid : 0 19.12.18 05:13:11.496 | XenStore | DBG - Read int domid : 0 19.12.18 05:13:11.501 | DisplBackend | DBG - Create backend, device: vdispl, dom Id: 0 19.12.18 05:13:11.509 | Drm | DBG - Start 19.12.18 05:13:11.514 | XenStore | DBG - Start 19.12.18 05:13:11.518 | XenStore | DBG - Set watch: /local/domain/0/backend/vdispl 19.12.18 05:13:11.527 | XenStore | DBG - Watch triggered: /local/domain/0/backend/vdispl === $ create_domu_debian DomU boot logs: root@hikey960:~# create_domu_debian Parsing config from /debian/debian.cfg 19.12.18 05:21:42.465 | XenStore| DBG - Watch triggered: /local/domain/0/backend/vdispl 19.12.18 05:21:42.474 | XenStore| DBG - Set watch: /local/domain/0/backend/vdispl/2 19.12.18 05:21:42.483 | XenStore| DBG - Watch triggered: /local/domain/0/backend/vdispl 19.12.18 05:21:42.492 | XenStore| DBG - Watch triggered: /local/domain/0/backend/vdispl 19.12.18 05:21:42.501 | XenStore| DBG - Watch triggered: /local/domain/0/backend/vdispl 19.12.18 05:21:42.510 | XenStore| DBG - Watch triggered: /local/domain/0/backend/vdispl 19.12.18 05:21:42.519 | XenStore| DBG - Watch triggered: /local/domain/0/backend/vdispl 19.12.18 05:21:42.528 | XenStore| DBG - Watch triggered: /local/domain/0/backend/vdispl 19.12.18 05:21:42.536 | XenStore| DBG - Watch triggered: /local/domain/0/backend/vdispl/2 19.12.18 05:21:42.546 | DisplBackend| DBG - New frontend found, domid: 2, devid: 0 19.12.18 05:21:42.554 | XenStore| DBG - Create xen store 19.12.18 05:21:42.559 | DisplFrontend | DBG - Dom(2/0) Create frontend handler 19.12.18 05:21:42.567 | XenStore| DBG - Read string
[Xen-devel] [XEN][ARM64] PV DRM failing to convert virtual to physical address
Hello, When PV DRM is enabled and Domain-U is started xen is not able to converted virtual address to physical. Please provide input on resolving this issue. Please find the details below. - We are using 64 bit arm platform. - Linux 4.20 Kernel in DomU with PV DRM front-end drivers. - Xen-4.12 unstable version. - Able to build displ_be application and also its dependencies. Added below configuration in Domain-U config file. *vdispl = [ 'backend=DomD,be-alloc=0,connectors=HDMI-A-1:1920x1080']* Before launching the application ran the displ_be application in the background. $ displ_be -m DRM -v *:Debug Started Domain-U. $ xl create -c debian.cfg Getting below logs. Welcome to Debian GNU/Linux 9 (stretch)! (XEN) p2m.c:1456: d2v2: gvirt_to_maddr failed va=0x80003df6c050 flags=0x1 par=0x809 [2.601162] systemd[1]: Set hostname to . [2.613526] random: systemd: uninitialized urandom read (16 bytes re(XEN) p2m.c:1456: d2v2: gvirt_to_maddr failed va=0x80003df6c05f flags=0x1 par=0x809 ad) (XEN) p2m.c:1456: d2v2: gvirt_to_maddr failed va=0x80003df6c05f flags=0x1 par=0x809 (XEN) p2m.c:1456: d2v2: gvirt_to_maddr failed va=0x80003df6c050 flags=0x1 par=0x809 (XEN) p2m.c:1456: d2v2: gvirt_to_maddr failed va=0x80003df6c05f flags=0x1 par=0x809 (XEN) p2m.c:1456: d2v2: gvirt_to_maddr failed va=0x80003df6c05f flags=0x1 par=0x809 (XEN) p2m.c:1456: d2v2: gvirt_to_maddr failed va=0x80003df6c050 flags=0x1 par=0x809 (XEN) p2m.c:1456: d2v2: gvirt_to_maddr failed va=0x80003df6c05f flags=0x1 par=0x809 (XEN) p2m.c:1456: d2v2: gvirt_to_maddr failed va=0x80003df6c05f flags=0x1 par=0x809 (XEN) p2m.c:1456: d2v2: gvirt_to_maddr failed va=0x80003df6c050 flags=0x1 par=0x809 (XEN) p2m.c:1456: d2v2: gvirt_to_maddr failed va=0x80003df6c05f flags=0x1 par=0x809 (XEN) p2m.c:1456: d2v2: gvirt_to_maddr failed va=0x80003df6c05f flags=0x1 par=0x809 (XEN) p2m.c:1456: d2v2: gvirt_to_maddr failed va=0x80003df6c050 flags=0x1 par=0x809 (XEN) p2m.c:1456: d2v2: gvirt_to_maddr failed va=0x80003df6c05f flags=0x1 par=0x809 (XEN) p2m.c:1456: d2v2: gvirt_to_maddr failed va=0x80003df6c05f flags=0x1 par=0x809 (XEN) p2m.c:1456: d2v2: gvirt_to_maddr failed va=0x80003df6c050 flags=0x1 par=0x809 (XEN) p2m.c:1456: d2v2: gvirt_to_maddr failed va=0x80003df6c05f flags=0x1 par=0x809 (XEN) p2m.c:1456: d2v2: gvirt_to_maddr failed va=0x80003df6c05f flags=0x1 par=0x809 (XEN) p2m.c:1456: d2v2: gvirt_to_maddr failed va=0x80003df6c050 flags=0x1 par=0x809 (XEN) p2m.c:1456: d2v2: gvirt_to_maddr failed va=0x80003df6c05f flags=0x1 par=0x809 (XEN) p2m.c:1456: d2v2: gvirt_to_maddr failed va=0x80003df6c05f flags=0x1 par=0x809 (XEN) p2m.c:1456: d2v2: gvirt_to_maddr failed va=0x80003df6c050 flags=0x1 par=0x809 (XEN) p2m.c:1456: d2v2: gvirt_to_maddr failed va=0x80003df6c05f flags=0x1 par=0x809 (XEN) p2m.c:1456: d2v2: gvirt_to_maddr failed va=0x80003df6c05f flags=0x1 par=0x809 (XEN) p2m.c:1456: d2v2: gvirt_to_maddr failed va=0x80003df6c050 flags=0x1 par=0x809 (XEN) p2m.c:1456: d2v2: gvirt_to_maddr failed va=0x80003df6c05f flags=0x1 par=0x809 (XEN) p2m.c:1456: d2v2: gvirt_to_maddr failed va=0x80003df6c05f flags=0x1 par=0x809 (XEN) p2m.c:1456: d2v2: gvirt_to_maddr failed va=0x80003df6c050 flags=0x1 par=0x809 (XEN) p2m.c:1456: d2v2: gvirt_to_maddr failed va=0x80003df6c05f flags=0x1 par=0x809 [3.006492] systemd[1]: Reached target Remote File Systems. [ OK ] Reached target Remote File Systems. [3.007179] systemd[1]: Started Dispatch Password Requests to Console Directory Watch. [ OK ] Started Dispatch Password Requests to Console Directory Watch. [3.007477] systemd[1]: Listening on Journal Socket. [ OK ] Listening on Journal Socket. [3.007742] systemd[1]: Listening on LVM2 metadata daemon socket. [ OK ] Listening on LVM2 metadata daemon socket. [3.007966] systemd[1]: Listening on Device-mapper event daemon FIFOs. [ OK ] Listening on Device-mapper event daemon FIFOs. [3.008161] systemd[1]: Listening on Syslog Socket. [ OK ] Listening on Syslog Socket. [ OK ] Listening on Journal Audit Socket. [ OK ] Listening on /dev/initctl Compatibility Named Pipe. [ OK ] Created slice System Slice. Starting Remount Root and Kernel File Systems... Starting Monitoring of LVM2 mirrors…ng dmeventd or progress polling... [(XEN) p2m.c:1456: d2v3: gvirt_to_maddr failed va=0x80003df8305f flags=0x1 par=0x809 (XEN) p2m.c:1456: d2v3: gvirt_to_maddr failed va=0x80003df83050 flags=0x1 par=0x809 OK ] Created slice system-serial\x2dgetty.slice. Mounting Huge Pages File System... Starting Uncomplic(XEN) p2m.c:1456: d2v3: gvirt_to_maddr failed va=0x80003df8305f flags=0x1 par=0x809 ated firewall... [ OK ] Listening on LVM2 poll daemon socket. Starting Create Static Device Nodes in /d(XEN) p2m.c:1456: d2v3: gvirt_to_maddr failed va=0x80003df8305f flags=0x1 par=0x809 ev(XEN)
[Xen-devel] How to create interface for wireless network
Hello, In case of Ethernet a bridge interface is created between Dom0 and DomU, so that DomU has the internet access bridge interface. We have only wireless chip in our board and how to create interface in case of wireless? Bridging doesn't work in case of wireless network. If we want use NAT, then through interface DomU will have access to internet? -- This message contains confidential information and is intended only for the individual(s) named. If you are not the intended recipient, you are notified that disclosing, copying, distributing or taking any action in reliance on the contents of this mail and attached file/s is strictly prohibited. Please notify the sender immediately and delete this e-mail from your system. E-mail transmission cannot be guaranteed to be secured or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. The sender therefore does not accept liability for any errors or omissions in the contents of this message, which arise as a result of e-mail transmission. ___ Xen-devel mailing list Xen-devel@lists.xenproject.org https://lists.xenproject.org/mailman/listinfo/xen-devel
Re: [Xen-devel] [XEN][ARM64] PVUSB device attach causing DomU hang
Hello, Please provide inputs on how to debug this issue. Is this due to some wrong configuration provide in the config file? -- This message contains confidential information and is intended only for the individual(s) named. If you are not the intended recipient, you are notified that disclosing, copying, distributing or taking any action in reliance on the contents of this mail and attached file/s is strictly prohibited. Please notify the sender immediately and delete this e-mail from your system. E-mail transmission cannot be guaranteed to be secured or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. The sender therefore does not accept liability for any errors or omissions in the contents of this message, which arise as a result of e-mail transmission. ___ Xen-devel mailing list Xen-devel@lists.xenproject.org https://lists.xenproject.org/mailman/listinfo/xen-devel
[Xen-devel] [XEN][ARM64] PVUSB device attach causing DomU hang
Hi, We are using xen-4.8 stable version. Our board has only USB-3.0. We trying to achieve PVUSB. Added following in the DomU config file. Applied the attached patch for USB front-end driver. Using qemu as back-end. domu.cfg *usbctrl=['version=2, ports=8', ]* *usb=['1.6, controller=0, port=1']* Attached the USB device(mouse and keyboard) using below commands. * xl usbdev-attach domU hostbus=1 hostaddr=6 controller=0 port=1 (Mouse)* * xl usbdev-attach debian hostbus=1 hostaddr=7 controller=0 port=1 (Keyboard)* After executing above getting below logs. [2.986905] synth uevent: /devices/virtual/input/input0: failed to send uevent [2.986919] input input0: uevent: failed to send synthetic uevent [ 25.689516] usb 1-1: new low-speed USB device number 2 using vusb [ 25.689664] CPU: 0 PID: 282 Comm: kworker/0:2 Not tainted 4.14.0-rc7-linaro-hikey960 #54 [ 25.689683] Hardware name: XENVM-4.8 (DT) [ 25.689706] Workqueue: usb_hub_wq hub_event [ 25.689721] task: 80001cd69c00 task.stack: 0954 [ 25.689743] PC is at xenhcd_gnttab_map.isra.3+0xc/0x18 [ 25.689762] LR is at xenhcd_do_request+0xe8/0x330 [ 25.689778] pc : [] lr : [] pstate: 21c5 [ 25.689800] sp : 09543950 [ 25.689811] x29: 09543950 x28: 8f8d1200 [ 25.689831] x27: 0001 x26: 0001 [ 25.689847] x25: x24: 80001da7a000 [ 25.689864] x23: x22: [ 25.689880] x21: 80001c70b1b8 x20: [ 25.689900] x19: 80001db64228 x18: 0010 [ 25.689918] x17: af33bb60 x16: 0020 [ 25.689935] x15: x14: 8919537f [ 25.689954] x13: 0919538d x12: 09069df0 [ 25.689973] x11: 0858afc8 x10: 09543890 [ 25.689990] x9 : 0914a000 x8 : 80001c70b1e0 [ 25.690009] x7 : x6 : 0040 [ 25.690027] x5 : 0001 x4 : 00ce [ 25.690043] x3 : 80001d941000 x2 : 0017 [ 25.690059] x1 : 0001 x0 : 0040 [ 25.690078] Process kworker/0:2 (pid: 282, stack limit = 0x0954) [ 25.690100] Call trace: [ 25.690110] Exception stack(0x09543810 to 0x09543950) [ 25.690130] 3800: 0040 0001 [ 25.690151] 3820: 0017 80001d941000 00ce 0001 [ 25.690172] 3840: 0040 80001c70b1e0 0914a000 [ 25.690194] 3860: 09543890 0858afc8 09069df0 0919538d [ 25.690218] 3880: 8919537f 0020 af33bb60 [ 25.690243] 38a0: 0010 80001db64228 80001c70b1b8 [ 25.690267] 38c0: 80001da7a000 [ 25.690288] 38e0: 0001 0001 8f8d1200 09543950 [ 25.690312] 3900: 0883b1f0 09543950 0883b0fc 21c5 [ 25.690333] 3920: 095439a0 081154c8 0883b1dc [ 25.690354] 3940: 09543950 0883b0fc [ 25.690371] [] xenhcd_gnttab_map.isra.3+0xc/0x18 [ 25.690391] [] xenhcd_urb_enqueue+0xe4/0x138 [ 25.690411] [] usb_hcd_submit_urb+0xa0/0x920 [ 25.690431] [] usb_submit_urb+0x31c/0x518 [ 25.690447] [] usb_start_wait_urb+0x54/0xd8 [ 25.690466] [] usb_control_msg+0xa4/0xf0 [ 25.690482] [] hub_port_init+0x1ec/0xa28 [ 25.690497] [] hub_event+0x7a4/0xf78 [ 25.690517] [] process_one_work+0x1cc/0x338 [ 25.690535] [] worker_thread+0x44/0x470 [ 25.690553] [] kthread+0x12c/0x130 [ 25.690571] [] ret_from_fork+0x10/0x18 Able to see that front-end is able attached these devices. But the problem is DomU hangs. -- Thanks & Regards Vikram KS -- This message contains confidential information and is intended only for the individual(s) named. If you are not the intended recipient, you are notified that disclosing, copying, distributing or taking any action in reliance on the contents of this mail and attached file/s is strictly prohibited. Please notify the sender immediately and delete this e-mail from your system. E-mail transmission cannot be guaranteed to be secured or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. The sender therefore does not accept liability for any errors or omissions in the contents of this message, which arise as a result of e-mail transmission. From e8a71989a8188f9f420b58e23d723d6818e794d7 Mon Sep 17 00:00:00 2001 From: Juergen Gross Date: Mon, 13 Jun 2016 15:53:57 +0200 Subject: [PATCH 1/2] usb: Add Xen pvUSB protocol description Patch-Mainline: Not yet, work in progress References: fate#315712 Add the definition of pvUSB protocol used between the pvUSB frontend in a Xen domU and the pvUSB backend
Re: [Xen-devel] [Xen-users] [XEN][ARM] WiFi bridge creation
Thanks Vladimir. Can some one provide pointer/reference on how to use NAT to share WiFi between Dom0 and DomU. Followed the instruction provided in the below link, but no success. https://wiki.debian.org/BridgeNetworkConnections#Bridging_with_a_wireless_NIC On Tue, Oct 30, 2018 at 4:04 PM Vladimir Botka wrote: > > On Tue, Oct 30, 2018 at 12:39 PM Vladimir Botka > wrote: > > > On Tue, 30 Oct 2018 10:03:22 +0530 > > > Vikram K wrote: > > > > Hello, > > > > We are using Hikey960 with Debian as Dom0 and DomU. This board has > only > > > > WiFi interface. We want to create bridge between Dom0 and DomU so > that > > > > DomU > > > > has internet access. We tried to create bridge using brtcl command, > but > > > > it > > > > is not working. Please provide pointers. > > > > AFAIK, it's not working > > > https://marc.info/?l=linux-wireless=136743495526905=2 > > > "There is a proposed fix that is included in OpenWrt" > > > https://marc.info/?l=linux-wireless=145591129008322=2 > > > More details are avilable in OpenWrt WiKi > > > https://wiki.openwrt.org/doc/recipes/relayclient > > > -vlado > > On Tue, 30 Oct 2018 15:01:39 +0530 > Vikram K wrote: > > Hi, > > As per below link, it is possible to share Internet via WiFi between Dom0 > > and DomU,. > > https://wiki.xenproject.org/wiki/Xen_in_WiFi_networks > > Tried the suggested solution using ebtables, but it did not work. > > * ebtables -t nat -A POSTROUTING -s 00:60:00:00:00:01 \ > > -j snat --to-source 00:60:aa:bb:cc:dd* > > In the configurations file we have added below configuration in DomU > > config file. > > * vif = ['mac=00:16:3e:64:b8:40']* > > Apart from that do we need to add any addition configuration? > > NAT is a different story. Worked for me with Armbian(no XEN) and Atheros > 9280 > couple of years ago. I used Ansible to configure it. > > https://github.com/vbotka/ansible-linux-postinstall/blob/master/templates/router1-iptables.j2 > > HTH, > > - vlado > -- Thanks & Regards Vikram KS -- This message contains confidential information and is intended only for the individual(s) named. If you are not the intended recipient, you are notified that disclosing, copying, distributing or taking any action in reliance on the contents of this mail and attached file/s is strictly prohibited. Please notify the sender immediately and delete this e-mail from your system. E-mail transmission cannot be guaranteed to be secured or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. The sender therefore does not accept liability for any errors or omissions in the contents of this message, which arise as a result of e-mail transmission. ___ Xen-devel mailing list Xen-devel@lists.xenproject.org https://lists.xenproject.org/mailman/listinfo/xen-devel
Re: [Xen-devel] [Xen-users] [XEN][ARM] WiFi bridge creation
Hi, As per below link, it is possible to share Internet via WiFi between Dom0 and DomU,. https://wiki.xenproject.org/wiki/Xen_in_WiFi_networks Tried the suggested solution using ebtables, but it did not work. * ebtables -t nat -A POSTROUTING -s 00:60:00:00:00:01 \ -j snat --to-source 00:60:aa:bb:cc:dd* In the configurations file we have added below configuration in DomU config file. * vif = ['mac=00:16:3e:64:b8:40']* Apart from that do we need to add any addition configuration? On Tue, Oct 30, 2018 at 12:39 PM Vladimir Botka wrote: > On Tue, 30 Oct 2018 10:03:22 +0530 > Vikram K wrote: > > > Hello, > > We are using Hikey960 with Debian as Dom0 and DomU. This board has only > > WiFi interface. We want to create bridge between Dom0 and DomU so that > DomU > > has internet access. We tried to create bridge using brtcl command, but > it > > is not working. Please provide pointers. > > AFAIK, it's not working > https://marc.info/?l=linux-wireless=136743495526905=2 > "There is a proposed fix that is included in OpenWrt" > https://marc.info/?l=linux-wireless=145591129008322=2 > More details are avilable in OpenWrt WiKi > https://wiki.openwrt.org/doc/recipes/relayclient > > HTH, > > -vlado > -- Thanks & Regards Vikram KS -- This message contains confidential information and is intended only for the individual(s) named. If you are not the intended recipient, you are notified that disclosing, copying, distributing or taking any action in reliance on the contents of this mail and attached file/s is strictly prohibited. Please notify the sender immediately and delete this e-mail from your system. E-mail transmission cannot be guaranteed to be secured or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. The sender therefore does not accept liability for any errors or omissions in the contents of this message, which arise as a result of e-mail transmission. ___ Xen-devel mailing list Xen-devel@lists.xenproject.org https://lists.xenproject.org/mailman/listinfo/xen-devel
[Xen-devel] [XEN][ARM] WiFi bridge creation
Hello, We are using Hikey960 with Debian as Dom0 and DomU. This board has only WiFi interface. We want to create bridge between Dom0 and DomU so that DomU has internet access. We tried to create bridge using brtcl command, but it is not working. Please provide pointers. -- This message contains confidential information and is intended only for the individual(s) named. If you are not the intended recipient, you are notified that disclosing, copying, distributing or taking any action in reliance on the contents of this mail and attached file/s is strictly prohibited. Please notify the sender immediately and delete this e-mail from your system. E-mail transmission cannot be guaranteed to be secured or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. The sender therefore does not accept liability for any errors or omissions in the contents of this message, which arise as a result of e-mail transmission. ___ Xen-devel mailing list Xen-devel@lists.xenproject.org https://lists.xenproject.org/mailman/listinfo/xen-devel
[Xen-devel] [ARM] Display passthrough
Hi, We want to passthrough the display to the guest OS.We are using Xen-4.8 and Hikey960. Is it possible to do pass through of display?If yes please provide reference. -- This message contains confidential information and is intended only for the individual(s) named. If you are not the intended recipient, you are notified that disclosing, copying, distributing or taking any action in reliance on the contents of this mail and attached file/s is strictly prohibited. Please notify the sender immediately and delete this e-mail from your system. E-mail transmission cannot be guaranteed to be secured or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. The sender therefore does not accept liability for any errors or omissions in the contents of this message, which arise as a result of e-mail transmission. ___ Xen-devel mailing list Xen-devel@lists.xenproject.org https://lists.xenproject.org/mailman/listinfo/xen-devel
[Xen-devel] USB pass-through and WiFi access
Hi, 1. We are using Hikey960 board. 2. Xen version is 4.8 3. Linux kernel version is 4.14 We want to add/pass-through USB devices to DomU. From the below link I understood that there is no USB back and front driver support in latest kernel. But PVUSB support is added to *xl* tools since Xen 4.7. Please provide pointers on to achieve USB pass-through and hotplug. https://wiki.xenproject.org/wiki/Xen_USB_Passthrough Also we want share wireless internet between Dom0 and DomU. To achieve this what configuration we need to? -- Thanks & Regards VKS#436 -- This message contains confidential information and is intended only for the individual(s) named. If you are not the intended recipient, you are notified that disclosing, copying, distributing or taking any action in reliance on the contents of this mail and attached file/s is strictly prohibited. Please notify the sender immediately and delete this e-mail from your system. E-mail transmission cannot be guaranteed to be secured or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. The sender therefore does not accept liability for any errors or omissions in the contents of this message, which arise as a result of e-mail transmission. ___ Xen-devel mailing list Xen-devel@lists.xenproject.org https://lists.xenproject.org/mailman/listinfo/xen-devel
