Re: [Xen-devel] VGA passthrough with USB passthrough
Hi, I have removed (00:02.0) from the grub argument line and been using: xen-pciback.hide=(00:14.0) modprobe.blacklist=i915,xhci_pci,xhci_hcd with DomU.cfg containing: gfx_passthru=1pci=['00:02.0','00:14.0'] Now I am seeing the VGA passthrough working, but the Windows DomU is stuck at 100% CPU utilization in the kernel. Any ideas why? I have PVDrivers installed, so I have added the pv list to this mail also. Neil On Mon, Oct 30, 2017 at 7:59 PM, Neil Sikka wrote: > Hello, I am trying to passthrough 2 physical devices to a DomU: my > integrated GPU that’s integrated into my CPU and my USB controller. These 2 > devices are shown in lspci as follows: > > > 00:02.0 VGA compatible controller: Intel Corporation Haswell Integrated > Graphics Controller (rev 06) > > … > > 00:14.0 USB controller: Intel Corporation Lynx Point USB xHCI Host > Controller (rev 04) > > > My Setup: > > xen_pciback compiled and loading as a module > > Dom0 has the necessary backend drivers, so I’m assuming its pvops, which > the docs say should be using “xen-pciback” rather than “pciback” in classic > kernels. > > Appended to my grub line: xen-pciback.hide=(00:02.0)(00:14.0) > modprobe.blacklist=i915,xhci_pci,xhci_hcd > > i915.ko is renamed to _i915.ko because it gets loaded despite > modprobe.blacklist argument, and I think i915 is competing with > xen-pciback.ko for (00:02.0) > > DomU.cfg has: gfx_passthru=1pci=['00:02.0','00:14.0'] > > Before starting DomU, I run xl pci-assignable-add 00:02.0 && xl > pci-assignable-add 00:14.0 > > > I have gotten each passthrough to independently work correctly on my > computer in the past, so I know the hardware supports it. When combining > the USB and GPU passthrough, I am seeing different things online and am > confused about the correct way to configure my Dom0/DomUs. Here: > > > https://wiki.xenproject.org/wiki/Xen_VGA_Passthrough > > > it says nothing about passing the BDF of the iGPU to xen-pciback.hide= > argument in grub. However that page links to a document, here: > > > https://wiki.xenproject.org/wiki/File:Xen_VGA_Passthrough_ > to_Windows_8_Consumer_Preview_64-bit_English_HVM_domU_and_ > Windows_XP_Home_Edition_SP3_HVM_domU_with_Xen_4.2- > unstable_Changeset_25070_and_Linux_Kernel_3.3.0_in_Ubuntu_ > 11.10_oneiric_ocelot_amd64_Final_Release_Dom0.pdf > > > which says to pass the BDF of the discrete GPU 01:00.0 to the grub > xen-pciback.hide parameter. When I use xen-pciback.hide=(00.02.0)(00:14.0), > I see 23 "vgaarb: this pci device is not a vga device" errors when I boot > Dom0 (which might be related to the fact that lspci reports 23 devices?). > When I remove (00:02.0), I dont see the vgaarb errors, but in both cases, > when I create the DomU, the VGA passthrough works. > > > When I use xen-pciback.hide=(00.02.0)(00:14.0) and try to passthrough > both together, I also get SATA write errors. > > > How can correctly I passthrough both the iGPU and the USB controller to > avoid SATA errors leading to disk corruption and vgaarb errors? > > > Thank You. > Neil > -- My Blog: http://www.neilscomputerblog.blogspot.com/ Twitter: @neilsikka ___ Xen-devel mailing list Xen-devel@lists.xen.org https://lists.xen.org/xen-devel
Re: [Xen-devel] Payed Xen Admin
Usually, I've seen (null) domains are not running but their Qemu DMs are running. You could probably remove the (null) from the list by using "kill -9" on the qemu pids. On Nov 27, 2016 11:55 PM, "Michael Schinzel" wrote: > Good Morning, > > > > we have some issues with our Xen Hosts. It seems it is a xen bug but we do > not find the solution. > > > > NameID Mem VCPUs State > Time(s) > > Domain-0 0 16192 4 r- > 147102.5 > > (null) 2 1 1 --p--d > 1273.2 > > vmanager2268 4 1024 1 -b > 34798.8 > > vmanager2340 5 1024 1 -b > 5983.8 > > vmanager261912 512 1 -b > 1067.0 > > vmanager261813 1024 4 -b > 1448.7 > > vmanager255714 1024 1 -b > 2783.5 > > vmanager187116 512 1 -b > 3772.1 > > vmanager259217 512 1 -b > 19744.5 > > vmanager256618 2048 1 -b > 3068.4 > > vmanager222819 512 1 -b > 837.6 > > vmanager224120 512 1 -b > 997.0 > > vmanager224421 2048 1 -b > 1457.9 > > vmanager227222 2048 1 -b > 1924.5 > > vmanager222623 1024 1 -b > 1454.0 > > vmanager224524 512 1 -b > 692.5 > > vmanager224925 512 1 -b > 22857.7 > > vmanager226526 2048 1 -b > 1388.1 > > vmanager227027 512 1 -b > 1250.6 > > vmanager227128 2048 3 -b > 2060.8 > > vmanager227329 1024 1 -b > 34089.4 > > vmanager227430 2048 1 -b > 8585.1 > > vmanager228131 2048 2 -b > 1848.9 > > vmanager228232 512 1 -b > 755.1 > > vmanager228833 1024 1 -b > 543.6 > > vmanager229234 512 1 -b > 3004.9 > > vmanager204135 512 1 -b > 4246.2 > > vmanager221636 1536 1 -b > 47508.3 > > vmanager229537 512 1 -b > 1414.9 > > vmanager259938 1024 4 -b > 7523.0 > > vmanager229639 1536 1 -b > 7142.0 > > vmanager229740 512 1 -b > 536.7 > > vmanager213642 1024 1 -b > 6162.9 > > vmanager229843 512 1 -b > 441.7 > > vmanager229944 512 1 -b > 368.7 > > (null) 45 4 1 --p--d > 1296.3 > > vmanager230346 512 1 -b > 1437.0 > > vmanager230847 512 1 -b > 619.3 > > vmanager231848 512 1 -b > 976.8 > > vmanager232549 512 1 -b > 480.2 > > vmanager262053 512 1 -b > 346.2 > > (null) 56 0 1 > --p--d 8.8 > > vmanager233457 512 1 -b > 255.5 > > vmanager223558 512 1 -b > 1724.2 > > vmanager987 59 512 1 -b > 647.1 > > vmanager230260 512 1 -b > 171.4 > > vmanager233561 512 1 > -b 31.3 > > vmanager233662 512 1 > -b 45.1 > > vmanager233863 512 1 > -b 22.6 > > vmanager234664 512 1 > -b 20.9 > > vmanager234965 2048 1 > -b 14.4 > > vmanager235066 512 1 -b > 324.8 > > vmanager235367 512 1 > -b 7.6 > > > > > > HVM VMs change sometimes in the state (null). > > > > We still upgraded xen from 4.1.1 to 4.8, we upgraded the System Kernel – > > > > root@v8:~# uname -a > > Linux v8
Re: [Xen-devel] Payed Xen Admin
My technique has been to look through top or ps on Dom0 for the QEMU processes and correlate those PIDs with what I see in /proc/PID. The proc/PID/cmdline file specifies which domid the QEMU process is doing the device emulation for. If QEMU instances are running, try killing the QEMU processes that are running for Domains that are destroyed. On Mon, Nov 28, 2016 at 1:27 PM, Thomas Toka wrote: > Hello, > > > > thanks for answering Neil. I think Neil means the block devices ? > > > > Neil can you show us how to verify if those devices are still running for > the null domain ids? > > > > I also think its maybe just a timing problem, maybe they do not shut down > always as they should.. > > > > We can give you surely access to such u box and you could have a look.. > > > > Mit freundlichen Grüßen > > > > Thomas Toka > > > > - Second Level Support - > > > > [image: logo_mail] > > IP-Projects GmbH & Co. KG > Am Vogelherd 14 > D - 97295 Waldbrunn > > Telefon: 09306 - 76499-0 > FAX: 09306 - 76499-15 > E-Mail: i...@ip-projects.de > > Geschäftsführer: Michael Schinzel > Registergericht Würzburg: HRA 6798 > Komplementär: IP-Projects Verwaltungs GmbH > > > > > > *Von:* Michael Schinzel > *Gesendet:* Montag, 28. November 2016 18:20 > *An:* Neil Sikka > *Cc:* Xen-devel ; Thomas Toka < > t...@ip-projects.de> > *Betreff:* AW: [Xen-devel] Payed Xen Admin > > > > Hello, > > > > thank you for your response. There are no quemu prozesses which we can > identify with the ID of the failed guest. > > > > > > Mit freundlichen Grüßen > > > > Michael Schinzel > > - Geschäftsführer - > > > > [image: https://www.ip-projects.de/logo_mail.png] > <https://www.ip-projects.de/> > > IP-Projects GmbH & Co. KG > Am Vogelherd 14 > D - 97295 Waldbrunn > > Telefon: 09306 - 76499-0 > FAX: 09306 - 76499-15 > E-Mail: i...@ip-projects.de > > Geschäftsführer: Michael Schinzel > Registergericht Würzburg: HRA 6798 > Komplementär: IP-Projects Verwaltungs GmbH > > > > > > *Von:* Neil Sikka [mailto:neilsi...@gmail.com ] > *Gesendet:* Montag, 28. November 2016 14:30 > *An:* Michael Schinzel > *Cc:* Xen-devel > *Betreff:* Re: [Xen-devel] Payed Xen Admin > > > > Usually, I've seen (null) domains are not running but their Qemu DMs are > running. You could probably remove the (null) from the list by using "kill > -9" on the qemu pids. > > > > On Nov 27, 2016 11:55 PM, "Michael Schinzel" > wrote: > > Good Morning, > > > > we have some issues with our Xen Hosts. It seems it is a xen bug but we do > not find the solution. > > > > NameID Mem VCPUs State > Time(s) > > Domain-0 0 16192 4 r- > 147102.5 > > (null) 2 1 1 --p--d > 1273.2 > > vmanager2268 4 1024 1 -b > 34798.8 > > vmanager2340 5 1024 1 -b > 5983.8 > > vmanager261912 512 1 -b > 1067.0 > > vmanager261813 1024 4 -b > 1448.7 > > vmanager255714 1024 1 -b > 2783.5 > > vmanager187116 512 1 -b > 3772.1 > > vmanager259217 512 1 -b > 19744.5 > > vmanager256618 2048 1 -b > 3068.4 > > vmanager222819 512 1 -b > 837.6 > > vmanager224120 512 1 -b > 997.0 > > vmanager224421 2048 1 -b > 1457.9 > > vmanager227222 2048 1 -b > 1924.5 > > vmanager222623 1024 1 -b > 1454.0 > > vmanager224524 512 1 -b > 692.5 > > vmanager224925 512 1 -b > 22857.7 > > vmanager226526 2048 1 -b > 1388.1 > > vmanager227027 512 1 -b > 1250.6 > > vmanager227128 2048 3 -b > 2060.8 > > vmanager227329 1024 1 -b > 34089.4 > > vmanager227
[Xen-devel] Xen Wiki Write permissions
Hello, how can i get write permission to update documentation on the Xen Wiki? -- My Blog: http://www.neilscomputerblog.blogspot.com/ Twitter: @neilsikka ___ Xen-devel mailing list Xen-devel@lists.xen.org https://lists.xen.org/xen-devel
Re: [Xen-devel] Do people want a Developer Meeting on Aug 24th (before Dev Summit)
Hey guys, is anything happening today regarding a meeting or going out for lunch if people arrive a day early? On Thu, Jun 23, 2016 at 8:43 AM, Lars Kurth wrote: > > > On 23 Jun 2016, at 12:39, George Dunlap > wrote: > > > > On 23/06/16 12:33, Lars Kurth wrote: > >> Folks, > >> > >> do you guys want to hold a Developer Meeting on Aug 24th (before Dev > Summit). I do have space to do this, but last year's was very poorly > attended. If you could get back to me with an opinion, that would help > hugely. Alternatively it would also be possible to use the space for more > focused meetings with fewer people. In that case, I would need a number of > suggestions for meetings including meeting leaders. > >> > >> Please have a look at the schedule http://events.linuxfoundation. > org/events/xen-project-developer-summit/program/schedule ... note that on > the 26th, I kept the 2nd room free and was planning to use the Hackathon > format in parallel to the talks in the main program. rather than having > BoFs interspersed with talks. Some of the slots could be used to host the > developer meeting, of desired. > > > > So to a large degree, the actual nuts-and-bolts planning which that > > meeting was meant to cover happens now at the "hackathons" instead. > > It's important I think, however, for the XenSummit to have a venue for > > people in the industry who may not know about the Hackathons (or for > > whatever reason can't come to them) to raise issues with the core > > developers and have them discussed. > > > > If the parallel track could actually fulfill that role, then I think it > > would be enough; the key would be making sure that the appropriate > > attention could be attracted. > > That's why I asked. Maybe we can come up with a short list of topics that > need to be discussed and are worthwhile for the developer meetings. > > The idea behind using the Hackathon scheduling methodology for the > parallel track is an experiment to make assigning of topics to space mor > effective than in the past. > > I don't have an opinion one way or another. We can have a developer > meeting as well. Just shout and I will set it up. > > Lars > ___ > Xen-devel mailing list > Xen-devel@lists.xen.org > http://lists.xen.org/xen-devel > -- My Blog: http://www.neilscomputerblog.blogspot.com/ Twitter: @neilsikka ___ Xen-devel mailing list Xen-devel@lists.xen.org https://lists.xen.org/xen-devel
Re: [Xen-devel] 9p file system for xen
How does Linda's work relate to Wei's patches available here (I didnt see them in Xen-4.6.0): http://downloads.xen.org/Wiki/VirtioOnXen/qemu-01-xenpv-exec.patch http://downloads.xen.org/Wiki/VirtioOnXen/qemu-02-virtio-for-pv.patch Also, since 9p is being worked on, which is a filesystem that should be implemented in a kernel rather than a hypervisor, are you looking to contribute this driver to the Linux kernel? On Mon, Nov 16, 2015 at 10:02 PM, Linda wrote: > Hi Wei, > > On 11/16/2015 10:35 AM, Wei Liu wrote: > >> On Mon, Nov 16, 2015 at 10:22:41AM -0700, Linda wrote: >> > ... > >> >>> The bug is a timing issue: During virtio's probe step, on the front >>> end, it >>> initialized the mount path. Since at that time, the front end doesn't >>> have >>> access to the back end's entries in xenstore (AFIACT), I either need to >>> put >>> it in xenstore prior to starting, or move the access to this information >>> to >>> later in the initialization. >>> >>> Note, I used the past tense on what virtio did, as of last summer: when I >>> looked at it last week, it appears to have changed since I first used it >>> as >>> a template.I need to investigate this further. >>> >>> OK. >> >> Finally, I've made no provision for how to mount more than one file system >>> for the same guest. This is a feature that virtio provides for in the >>> front-end code (as do I), but I am unclear about how this works in the >>> back-end or at the user level. This is what I suspect will be different >>> in >>> xen, and I'd like some input on what it should look like. >>> >> I think this comes down to how your design the xenstore protocol to >> represent different mount points. >> > And just reading this gave me the answer I need. > >> >> The code freeze for next release is going to be end of March next year. As software engineer often overestimates the progress he or she can make, I would say we shall aim for getting something working as soon as possible. Get the design straight and something clean by the end of this year would be good. >>> Sounds good to me. I'm happy to keep working on this. I just didn't >>> want >>> to find myself in a position where I needed to pass this on to someone >>> else, >>> but I didn't give that person enough time to finish what I'd done. >>> >> Depending on the situation, I can take over the code. You've done enough >> for this project and we don't really want you to work on it for free -- >> we don't have provision for more funding at the moment. >> > Understood. > >> If we end up taking over the project, we will still attribute the >> initial implementation to you. >> > Thanks. Julien said essentially the same thing. Right now, I'm > working on average, less than 10 hours/week, so it's enough to keep my mind > engaged, but it doesn't interfere with anything else. > I will be working for pay, in some capacity (TBD), after the first of > the year. Right now, I'm working to line things up. > Unless something changes drastically, I'll continue to work on this > until the end of the year. I'll start by cleaning things up, and keep it > that way, so no matter what happens, you, or Julien, can take it over. > > Linda > > >> Wei. >> >> > > ___ > Xen-devel mailing list > Xen-devel@lists.xen.org > http://lists.xen.org/xen-devel > -- My Blog: http://www.neilscomputerblog.blogspot.com/ Twitter: @neilsikka ___ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel
Re: [Xen-devel] 9p file system for xen
Is there any documentation about planned interfaces and API contracts for people building around the virtio/9pfs layers? For example, while this is still getting debugged/checked in, in order to build DomU support for these devices, the expected API contracts/interfaces would need to be known. On Wed, Nov 18, 2015 at 4:56 AM, Wei Liu wrote: > On Tue, Nov 17, 2015 at 12:50:29PM -0700, Linda wrote: > > > > > > On 11/17/2015 11:35 AM, Neil Sikka wrote: > > >How does Linda's work relate to Wei's patches available here (I didnt > see > > >them in Xen-4.6.0): > > > > > >http://downloads.xen.org/Wiki/VirtioOnXen/qemu-01-xenpv-exec.patch > > >http://downloads.xen.org/Wiki/VirtioOnXen/qemu-02-virtio-for-pv.patch > > I'll let Wei answer this. > > That wasn't upstreamed at all. Admittedly that was done when I didn't > know much about Xen. I would have done that project differently > nowadays. > > And to clarify things: virtio on Xen is a different project than 9pfs on > Xen. 9pfs is not tied to virtio in any way. Just that there is currently > only virtio-9pfs available. > > So to make 9pfs work on Xen, there are at least two ways. One is to make > virtio work on Xen so that we subsequently get virtio-9pfs (along with > all other virtio devices); the other is to implement xen-9pfs (I made up > this name). > > I'm not sure whether you're interested in virtio on Xen or just 9pfs. > > > > > > >Also, since 9p is being worked on, which is a filesystem that should be > > >implemented in a kernel rather than a hypervisor, are you looking to > > >contribute this driver to the Linux kernel? > > What I did was write new kernel routines and new Qemu routines, as well > as > > I think Neil was talking about the "new kernel routines". Yes, that > would need to be upstreamed eventually. > > Wei. > > > modifying a few existing Qemu files. The initialization is currently > done > > manually by modifying xenstore. This is the only code that properly > belongs > > in the hypervisor. > > > > I hope this clarifies things. > > > > Linda > -- My Blog: http://www.neilscomputerblog.blogspot.com/ Twitter: @neilsikka ___ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel
Re: [Xen-devel] 9p file system for xen
Wei, based on our discussions, you will review as much as possible before leaving for vacation, and have started last Wednesday. Could you please share what you are reviewing so I (and anyone else interested) can also assist in reviewing it? As you said, the front/back end negotiation protocols need to be designed and agreed upon, and we can start that now in parallel with the code review. On Thu, Nov 19, 2015 at 11:23 AM, Linda wrote: > Hi Wei, > > On 11/19/2015 8:03 AM, Wei Liu wrote: > >> On Thu, Nov 19, 2015 at 09:55:00AM -0500, Neil Sikka wrote: >> >>> Is there any documentation about planned interfaces and API contracts for >>> people building around the virtio/9pfs layers? For example, while this is >>> >> I assume that you're interested in getting 9pfs to work but don't care >> much about how it is made to work? I ask because I'm a bit confused by >> the notion of "virtio/9pfs" because what Linda did wasn't based on >> virtio transport. >> > A clarification: If you mean the virtio 9pfs transport, my code is based > on that, and sits on top of it. > > >> still getting debugged/checked in, in order to build DomU support for >>> these >>> devices, the expected API contracts/interfaces would need to be known. >>> >>> I'm not sure I get your question. What do you mean by "build DomU >> support"? What kind of DomU support needs insider knowledge of how 9pfs >> is setup? Are you talking about your own management stack that starts >> VM? >> >> Wei. >> >> > -- My Blog: http://www.neilscomputerblog.blogspot.com/ Twitter: @neilsikka ___ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel
Re: [Xen-devel] 9p file system for xen
Hi Wei, could you please explain why/how you would have done the project differently now and why these patches are not "good"? From my conversation with Linda, I understood that her code is "Independent of virtio except the 9pvirtio specific code, which is used extensively." On Wed, Nov 18, 2015 at 4:56 AM, Wei Liu wrote: > On Tue, Nov 17, 2015 at 12:50:29PM -0700, Linda wrote: > > > > > > On 11/17/2015 11:35 AM, Neil Sikka wrote: > > >How does Linda's work relate to Wei's patches available here (I didnt > see > > >them in Xen-4.6.0): > > > > > >http://downloads.xen.org/Wiki/VirtioOnXen/qemu-01-xenpv-exec.patch > > >http://downloads.xen.org/Wiki/VirtioOnXen/qemu-02-virtio-for-pv.patch > > I'll let Wei answer this. > > That wasn't upstreamed at all. Admittedly that was done when I didn't > know much about Xen. I would have done that project differently > nowadays. > > And to clarify things: virtio on Xen is a different project than 9pfs on > Xen. 9pfs is not tied to virtio in any way. Just that there is currently > only virtio-9pfs available. > > So to make 9pfs work on Xen, there are at least two ways. One is to make > virtio work on Xen so that we subsequently get virtio-9pfs (along with > all other virtio devices); the other is to implement xen-9pfs (I made up > this name). > > I'm not sure whether you're interested in virtio on Xen or just 9pfs. > > > > > > >Also, since 9p is being worked on, which is a filesystem that should be > > >implemented in a kernel rather than a hypervisor, are you looking to > > >contribute this driver to the Linux kernel? > > What I did was write new kernel routines and new Qemu routines, as well > as > > I think Neil was talking about the "new kernel routines". Yes, that > would need to be upstreamed eventually. > > Wei. > > > modifying a few existing Qemu files. The initialization is currently > done > > manually by modifying xenstore. This is the only code that properly > belongs > > in the hypervisor. > > > > I hope this clarifies things. > > > > Linda > -- My Blog: http://www.neilscomputerblog.blogspot.com/ Twitter: @neilsikka ___ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel
