Re: [qubes-users] Can't assign LTE USB Modem (Non-endpoint PCI devices cannot be assigned to guests)
OP has the mouse on sys-usb, so connecting it to the network would be very bad. -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/fdf178da-a5b6-4ac3-818a-aa9a05019c18%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Can't assign LTE USB Modem (Non-endpoint PCI devices cannot be assigned to guests)
On Sat, August 25, 2018 9:32 pm, awokd wrote: > On Sat, August 25, 2018 8:20 pm, Daniil .Travnikov wrote: > >> On Saturday, August 25, 2018 at 12:06:49 PM UTC-4, awokd wrote: >> >> >>> On Sat, August 25, 2018 3:27 pm, Daniil .Travnikov wrote: >>> >>> On Saturday, August 25, 2018 at 10:59:22 AM UTC-4, awokd wrote: >>> > > OK, then I guess your only option is to do what you were doing > and keep the USB controller in sys-net. This isn't necessarily a > bad thing; there's an option on Qubes install to configure it like > that, but it lessens separation of devices. Maybe do you know how can I install this Qubes option about you said? Or maybe in some point from docs? >>> >>> Manually assigning the USB controller to sys-net accomplishes the >>> exact same thing as the setup option. >> >> It means that I have not any solution for this modem in Qubes. Because >> I >> can't assign this device to sys-net without all devices which I already >> using (for example usb mouse and usb flash drives). > > That's correct, all USB devices would also be on sys-net, but like I > wrote above that's not necessarily a bad thing. Another option might be to configure your sys-usb with "qvm-prefs sys-usb provides_network true". Not sure if there is more to it than that. -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/c09bfd45aa09c9ac250e7f50af1630d8.squirrel%40tt3j2x4k5ycaa5zt.onion. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Can't assign LTE USB Modem (Non-endpoint PCI devices cannot be assigned to guests)
On Sat, August 25, 2018 8:20 pm, Daniil .Travnikov wrote: > On Saturday, August 25, 2018 at 12:06:49 PM UTC-4, awokd wrote: > >> On Sat, August 25, 2018 3:27 pm, Daniil .Travnikov wrote: >> >>> On Saturday, August 25, 2018 at 10:59:22 AM UTC-4, awokd wrote: >>> >>> >> OK, then I guess your only option is to do what you were doing and keep the USB controller in sys-net. This isn't necessarily a bad thing; there's an option on Qubes install to configure it like that, but it lessens separation of devices. >>> >>> Maybe do you know how can I install this Qubes option about you said? >>> Or >>> maybe in some point from docs? >> >> Manually assigning the USB controller to sys-net accomplishes the exact >> same thing as the setup option. > > It means that I have not any solution for this modem in Qubes. Because I > can't assign this device to sys-net without all devices which I already > using (for example usb mouse and usb flash drives). That's correct, all USB devices would also be on sys-net, but like I wrote above that's not necessarily a bad thing. -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/5ac816a503735de81c87e38534ce9b5f.squirrel%40tt3j2x4k5ycaa5zt.onion. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Can't assign LTE USB Modem (Non-endpoint PCI devices cannot be assigned to guests)
On Saturday, August 25, 2018 at 12:06:49 PM UTC-4, awokd wrote: > On Sat, August 25, 2018 3:27 pm, Daniil .Travnikov wrote: > > On Saturday, August 25, 2018 at 10:59:22 AM UTC-4, awokd wrote: > > > > >> > >> OK, then I guess your only option is to do what you were doing and keep > >> the USB controller in sys-net. This isn't necessarily a bad thing; > >> there's an option on Qubes install to configure it like that, but it > >> lessens separation of devices. > > > > Maybe do you know how can I install this Qubes option about you said? Or > > maybe in some point from docs? > > Manually assigning the USB controller to sys-net accomplishes the exact > same thing as the setup option. It means that I have not any solution for this modem in Qubes. Because I can't assign this device to sys-net without all devices which I already using (for example usb mouse and usb flash drives). -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/985c607b-9d0c-4742-81bc-b9d35836b891%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Can't assign LTE USB Modem (Non-endpoint PCI devices cannot be assigned to guests)
On Saturday, August 25, 2018 at 12:06:49 PM UTC-4, awokd wrote: > On Sat, August 25, 2018 3:27 pm, Daniil .Travnikov wrote: > > On Saturday, August 25, 2018 at 10:59:22 AM UTC-4, awokd wrote: > > > > >> > >> OK, then I guess your only option is to do what you were doing and keep > >> the USB controller in sys-net. This isn't necessarily a bad thing; > >> there's an option on Qubes install to configure it like that, but it > >> lessens separation of devices. > > > > Maybe do you know how can I install this Qubes option about you said? Or > > maybe in some point from docs? > > Manually assigning the USB controller to sys-net accomplishes the exact > same thing as the setup option. It means that I have not any solution if I want to use this modem for example for another VM? Only in sys-net? -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/6cab9fb2-146a-45db-820b-699133b210c0%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Can't assign LTE USB Modem (Non-endpoint PCI devices cannot be assigned to guests)
On Sat, August 25, 2018 3:27 pm, Daniil .Travnikov wrote: > On Saturday, August 25, 2018 at 10:59:22 AM UTC-4, awokd wrote: > >> >> OK, then I guess your only option is to do what you were doing and keep >> the USB controller in sys-net. This isn't necessarily a bad thing; >> there's an option on Qubes install to configure it like that, but it >> lessens separation of devices. > > Maybe do you know how can I install this Qubes option about you said? Or > maybe in some point from docs? Manually assigning the USB controller to sys-net accomplishes the exact same thing as the setup option. -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/3c5f320e3c2b011a4395ca60b297aaba.squirrel%40tt3j2x4k5ycaa5zt.onion. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Can't assign LTE USB Modem (Non-endpoint PCI devices cannot be assigned to guests)
On Saturday, August 25, 2018 at 10:59:22 AM UTC-4, awokd wrote: > On Sat, August 25, 2018 2:45 pm, Daniil .Travnikov wrote: > > On Saturday, August 25, 2018 at 10:20:02 AM UTC-4, awokd wrote: > > > >> On Fri, August 24, 2018 2:23 pm, Daniil .Travnikov wrote: > >> > >> > >>> When I am choosing this device: > >>> '00:14.0 USB controller: Intel Corporation Device a36d (rev 10)' > >>> > >>> > >>> > >>> and start VM, I see that all usb controllers going to work from this > >>> started new VM. > >>> > >>> > >>> Like you already saw in the list of pci above I have only 1 USB > >>> controller in the list (when I run the command 'lspci'). But in my > >>> laptop I have 3× USB 3.1 Type-A and they all going to started with VM. > >>> > >> > >> Missed seeing that, actually! > >> > >> > >>> Maybe existing some way, when I can connect only those usb ports > >>> which has include devices at the time? > >> > >> Can you leave the USB controller in sys-usb, then use qvm-usb to attach > >> just the modem to sys-net? Not sure that would actually work. Is that > >> what you did in 3.2? > > > > Actually when I used Qubes 3.2 it was been the server which was have the > > several usb controllers. And I assume that my laptop have only 1 > > controller which connected to 5 usb ports. Maybe that's why I see only > > one usb controller in Devices tab. > > > > > > When I put in my any usb flash card I can see it when I write command > > 'qvm-block', but when i put in my usb modem this command do not show my > > device. > > > > I checked modem, he is still working on another laptop. > > > > > > When I write this commands now: > > 'qvm-block' > > 'qvm-usb' > > > > > > I see empty results: > > 'BACKEND:DEVID DESCRIPTION USED BY' > > OK, then I guess your only option is to do what you were doing and keep > the USB controller in sys-net. This isn't necessarily a bad thing; there's > an option on Qubes install to configure it like that, but it lessens > separation of devices. Maybe do you know how can I install this Qubes option about you said? Or maybe in some point from docs? -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/3f321979-89eb-491a-8687-bb7c2b55a341%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Can't assign LTE USB Modem (Non-endpoint PCI devices cannot be assigned to guests)
On Sat, August 25, 2018 2:45 pm, Daniil .Travnikov wrote: > On Saturday, August 25, 2018 at 10:20:02 AM UTC-4, awokd wrote: > >> On Fri, August 24, 2018 2:23 pm, Daniil .Travnikov wrote: >> >> >>> When I am choosing this device: >>> '00:14.0 USB controller: Intel Corporation Device a36d (rev 10)' >>> >>> >>> >>> and start VM, I see that all usb controllers going to work from this >>> started new VM. >>> >>> >>> Like you already saw in the list of pci above I have only 1 USB >>> controller in the list (when I run the command 'lspci'). But in my >>> laptop I have 3× USB 3.1 Type-A and they all going to started with VM. >>> >> >> Missed seeing that, actually! >> >> >>> Maybe existing some way, when I can connect only those usb ports >>> which has include devices at the time? >> >> Can you leave the USB controller in sys-usb, then use qvm-usb to attach >> just the modem to sys-net? Not sure that would actually work. Is that >> what you did in 3.2? > > Actually when I used Qubes 3.2 it was been the server which was have the > several usb controllers. And I assume that my laptop have only 1 > controller which connected to 5 usb ports. Maybe that's why I see only > one usb controller in Devices tab. > > > When I put in my any usb flash card I can see it when I write command > 'qvm-block', but when i put in my usb modem this command do not show my > device. > > I checked modem, he is still working on another laptop. > > > When I write this commands now: > 'qvm-block' > 'qvm-usb' > > > I see empty results: > 'BACKEND:DEVID DESCRIPTION USED BY' OK, then I guess your only option is to do what you were doing and keep the USB controller in sys-net. This isn't necessarily a bad thing; there's an option on Qubes install to configure it like that, but it lessens separation of devices. -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/5e44b33d468db5fda901a554713eb0dd.squirrel%40tt3j2x4k5ycaa5zt.onion. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Can't assign LTE USB Modem (Non-endpoint PCI devices cannot be assigned to guests)
On Saturday, August 25, 2018 at 10:20:02 AM UTC-4, awokd wrote: > On Fri, August 24, 2018 2:23 pm, Daniil .Travnikov wrote: > > > When I am choosing this device: > > '00:14.0 USB controller: Intel Corporation Device a36d (rev 10)' > > > > > > and start VM, I see that all usb controllers going to work from this > > started new VM. > > > > > > Like you already saw in the list of pci above I have only 1 USB > > controller in the list (when I run the command 'lspci'). But in my laptop > > I have 3× USB 3.1 Type-A and they all going to started with VM. > > Missed seeing that, actually! > > > Maybe existing some way, when I can connect only those usb ports which > > has include devices at the time? > > Can you leave the USB controller in sys-usb, then use qvm-usb to attach > just the modem to sys-net? Not sure that would actually work. Is that what > you did in 3.2? Actually when I used Qubes 3.2 it was been the server which was have the several usb controllers. And I assume that my laptop have only 1 controller which connected to 5 usb ports. Maybe that's why I see only one usb controller in Devices tab. When I put in my any usb flash card I can see it when I write command 'qvm-block', but when i put in my usb modem this command do not show my device. I checked modem, he is still working on another laptop. When I write this commands now: 'qvm-block' 'qvm-usb' I see empty results: 'BACKEND:DEVID DESCRIPTION USED BY' -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/1e3e4497-2ce6-4a23-8194-a297c54c6bf4%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Can't assign LTE USB Modem (Non-endpoint PCI devices cannot be assigned to guests)
On Fri, August 24, 2018 2:23 pm, Daniil .Travnikov wrote: > When I am choosing this device: > '00:14.0 USB controller: Intel Corporation Device a36d (rev 10)' > > > and start VM, I see that all usb controllers going to work from this > started new VM. > > > Like you already saw in the list of pci above I have only 1 USB > controller in the list (when I run the command 'lspci'). But in my laptop > I have 3× USB 3.1 Type-A and they all going to started with VM. Missed seeing that, actually! > Maybe existing some way, when I can connect only those usb ports which > has include devices at the time? Can you leave the USB controller in sys-usb, then use qvm-usb to attach just the modem to sys-net? Not sure that would actually work. Is that what you did in 3.2? -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/b68a62d4c0fc5a0296af46e11aebae6a.squirrel%40tt3j2x4k5ycaa5zt.onion. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Can't assign LTE USB Modem (Non-endpoint PCI devices cannot be assigned to guests)
On Friday, August 24, 2018 at 8:31:07 AM UTC-4, awokd wrote:
> On Fri, August 24, 2018 12:03 pm, Daniil .Travnikov wrote:
> > On Friday, August 24, 2018 at 6:08:54 AM UTC-4, awokd wrote:
> >
> >> On Fri, August 24, 2018 9:53 am, Daniil .Travnikov wrote:
> >>
> >>> I have an LTE USB Modem which I used in Qubes 3.2 very well, but in
> >>> Qubes
> >>> 4.0 I have some issues.
> >>>
> >>>
> >>>
> >>>
> >>> First of all in Qubes Manager I can attach this usb modem only in HVM
> >>> mode ('ERROR: devices tab: Can't attach PCI device to VM in pvh
> >>> mode').
> >>>
> >>>
> >>> So I changed in VM on HVM mode and attached just usb slot.
> >>>
> >>>
> >>>
> >>>
> >>>
> >>> Then I tried to turn on my VM but I got 2 same error messages (first
> >>> one in windows and the second one on the top right corner):
> >>>
> >>> 'ERROR: Start failed: internal error: Non-endpoint PCI devices cannot
> >>> be assigned to guests, see /var/lob/libvirt/libxl/libxl-driver.log'
> >>>
> >>> 'Qube Status: usb
> >>> Domain usb has failed to start: Internal error: Non-endpoint PCI
> >>> devices cannot be assigned to guests'.
> >>>
> >>>
> >>> Tell me please what am I missing in Qubes 4.0?
> >>>
> >>
> >> Do an "lspci" and "lspci -t" in dom0, and try attaching the leaf device
> >> instead. Sounds like you are trying to attach some type of bridge.
> >
> > Thank you for your answer.
> >
> >
> >
> > Before your message I tried to attach this device:
> > '00:1d.0 PCI bridge: Intel Corporation Device a330 (rev f0)'
> > and you saw which error I got.
> >
> > After your message I thought maybe I am choosing not correct device and
> > now I am choosing this device: '00:14.0 USB controller: Intel Corporation
> > Device a36d (rev 10)'
>
> Yes, this one should work better.
>
> > and got another error messages:
> >
> > 'ERROR: Start failed: internal error: Unable to reset PCI device
> > :00:14.0: no FLR, PM reset or bus reset available, see
> > /var/log/libvirt/libxl/libxl-driver.log for details'
> >
> >
> > 'Qube Status: usb
> > Domain usb has failed to start: internal error: Unable to reset PCI device
> > :00:14.0: no FLR, PM reset or bus reset available'.
>
> Disable the strict reset requirement on that device, either in the GUI or
> CLI.
Thank you very much again. It works for me.
When I am choosing this device:
'00:14.0 USB controller: Intel Corporation Device a36d (rev 10)'
and start VM, I see that all usb controllers going to work from this started
new VM.
Like you already saw in the list of pci above I have only 1 USB controller in
the list (when I run the command 'lspci').
But in my laptop I have 3× USB 3.1 Type-A and they all going to started with VM.
Maybe existing some way, when I can connect only those usb ports which has
include devices at the time?
--
You received this message because you are subscribed to the Google Groups
"qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to qubes-users+unsubscr...@googlegroups.com.
To post to this group, send email to qubes-users@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/qubes-users/d0fde295-5c44-45e7-809b-a0da2913fe37%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Can't assign LTE USB Modem (Non-endpoint PCI devices cannot be assigned to guests)
On Fri, August 24, 2018 12:03 pm, Daniil .Travnikov wrote:
> On Friday, August 24, 2018 at 6:08:54 AM UTC-4, awokd wrote:
>
>> On Fri, August 24, 2018 9:53 am, Daniil .Travnikov wrote:
>>
>>> I have an LTE USB Modem which I used in Qubes 3.2 very well, but in
>>> Qubes
>>> 4.0 I have some issues.
>>>
>>>
>>>
>>>
>>> First of all in Qubes Manager I can attach this usb modem only in HVM
>>> mode ('ERROR: devices tab: Can't attach PCI device to VM in pvh
>>> mode').
>>>
>>>
>>> So I changed in VM on HVM mode and attached just usb slot.
>>>
>>>
>>>
>>>
>>>
>>> Then I tried to turn on my VM but I got 2 same error messages (first
>>> one in windows and the second one on the top right corner):
>>>
>>> 'ERROR: Start failed: internal error: Non-endpoint PCI devices cannot
>>> be assigned to guests, see /var/lob/libvirt/libxl/libxl-driver.log'
>>>
>>> 'Qube Status: usb
>>> Domain usb has failed to start: Internal error: Non-endpoint PCI
>>> devices cannot be assigned to guests'.
>>>
>>>
>>> Tell me please what am I missing in Qubes 4.0?
>>>
>>
>> Do an "lspci" and "lspci -t" in dom0, and try attaching the leaf device
>> instead. Sounds like you are trying to attach some type of bridge.
>
> Thank you for your answer.
>
>
>
> Before your message I tried to attach this device:
> '00:1d.0 PCI bridge: Intel Corporation Device a330 (rev f0)'
> and you saw which error I got.
>
> After your message I thought maybe I am choosing not correct device and
> now I am choosing this device: '00:14.0 USB controller: Intel Corporation
> Device a36d (rev 10)'
Yes, this one should work better.
> and got another error messages:
>
> 'ERROR: Start failed: internal error: Unable to reset PCI device
> :00:14.0: no FLR, PM reset or bus reset available, see
> /var/log/libvirt/libxl/libxl-driver.log for details'
>
>
> 'Qube Status: usb
> Domain usb has failed to start: internal error: Unable to reset PCI device
> :00:14.0: no FLR, PM reset or bus reset available'.
Disable the strict reset requirement on that device, either in the GUI or
CLI.
--
You received this message because you are subscribed to the Google Groups
"qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to qubes-users+unsubscr...@googlegroups.com.
To post to this group, send email to qubes-users@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/qubes-users/1447110fa3d2cfcdbfd3a2ea2b9f6fe2.squirrel%40tt3j2x4k5ycaa5zt.onion.
For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Can't assign LTE USB Modem (Non-endpoint PCI devices cannot be assigned to guests)
On Friday, August 24, 2018 at 6:08:54 AM UTC-4, awokd wrote: > Do an "lspci" and "lspci -t" in dom0, and try attaching the leaf device > instead. Sounds like you are trying to attach some type of bridge. This is what I got when run this 2 commands: [user@dom0 ~]$ lspci 00:00.0 Host bridge: Intel Corporation Device 3ec4 (rev 07) 00:01.0 PCI bridge: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor PCIe Controller (x16) (rev 07) 00:02.0 VGA compatible controller: Intel Corporation Device 3e9b 00:08.0 System peripheral: Intel Corporation Xeon E3-1200 v5/v6 / E3-1500 v5 / 6th/7th Gen Core Processor Gaussian Mixture Model 00:12.0 Signal processing controller: Intel Corporation Device a379 (rev 10) 00:14.0 USB controller: Intel Corporation Device a36d (rev 10) 00:14.2 RAM memory: Intel Corporation Device a36f (rev 10) 00:16.0 Communication controller: Intel Corporation Device a360 (rev 10) 00:17.0 SATA controller: Intel Corporation Device a353 (rev 10) 00:1d.0 PCI bridge: Intel Corporation Device a330 (rev f0) 00:1d.5 PCI bridge: Intel Corporation Device a335 (rev f0) 00:1d.6 PCI bridge: Intel Corporation Device a336 (rev f0) 00:1d.7 PCI bridge: Intel Corporation Device a337 (rev f0) 00:1f.0 ISA bridge: Intel Corporation Device a30d (rev 10) 00:1f.3 Audio device: Intel Corporation Device a348 (rev 10) 00:1f.4 SMBus: Intel Corporation Device a323 (rev 10) 00:1f.5 Serial bus controller [0c80]: Intel Corporation Device a324 (rev 10) 01:00.0 VGA compatible controller: NVIDIA Corporation GP104M [GeForce GTX 1070 Mobile] (rev a1) 02:00.0 Non-Volatile memory controller: Samsung Electronics Co Ltd Device a808 03:00.0 Network controller: Intel Corporation Wireless 8265 / 8275 (rev 78) 04:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 0c) 05:00.0 SD Host controller: Realtek Semiconductor Co., Ltd. RTS5250 PCI Express Card Reader (rev 01) [user@dom0 Desktop]$ lspci -t -[:00]-+-00.0 +-01.0-[01]00.0 +-02.0 +-08.0 +-12.0 +-14.0 +-14.2 +-16.0 +-17.0 +-1d.0-[02]00.0 +-1d.5-[03]00.0 +-1d.6-[04]00.0 +-1d.7-[05]00.0 +-1f.0 +-1f.3 +-1f.4 \-1f.5 What do you mean when you say "leaf device"? -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/b10af1d2-5955-4939-9a2c-f84eab40ec1e%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Can't assign LTE USB Modem (Non-endpoint PCI devices cannot be assigned to guests)
On Friday, August 24, 2018 at 6:08:54 AM UTC-4, awokd wrote:
> On Fri, August 24, 2018 9:53 am, Daniil .Travnikov wrote:
> > I have an LTE USB Modem which I used in Qubes 3.2 very well, but in Qubes
> > 4.0 I have some issues.
> >
> >
> >
> > First of all in Qubes Manager I can attach this usb modem only in HVM
> > mode ('ERROR: devices tab: Can't attach PCI device to VM in pvh mode').
> >
> >
> > So I changed in VM on HVM mode and attached just usb slot.
> >
> >
> >
> >
> > Then I tried to turn on my VM but I got 2 same error messages (first one
> > in windows and the second one on the top right corner):
> >
> > 'ERROR: Start failed: internal error: Non-endpoint PCI devices cannot be
> > assigned to guests, see /var/lob/libvirt/libxl/libxl-driver.log'
> >
> > 'Qube Status: usb
> > Domain usb has failed to start: Internal error: Non-endpoint PCI devices
> > cannot be assigned to guests'.
> >
> >
> > Tell me please what am I missing in Qubes 4.0?
>
> Do an "lspci" and "lspci -t" in dom0, and try attaching the leaf device
> instead. Sounds like you are trying to attach some type of bridge.
Thank you for your answer.
Before your message I tried to attach this device:
'00:1d.0 PCI bridge: Intel Corporation Device a330 (rev f0)'
and you saw which error I got.
After your message I thought maybe I am choosing not correct device and now I
am choosing this device:
'00:14.0 USB controller: Intel Corporation Device a36d (rev 10)'
and got another error messages:
'ERROR: Start failed: internal error: Unable to reset PCI device :00:14.0:
no FLR, PM reset or bus reset available, see
/var/log/libvirt/libxl/libxl-driver.log for details'
'Qube Status: usb
Domain usb has failed to start: internal error: Unable to reset PCI device
:00:14.0: no FLR, PM reset or bus reset available'.
--
You received this message because you are subscribed to the Google Groups
"qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to qubes-users+unsubscr...@googlegroups.com.
To post to this group, send email to qubes-users@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/qubes-users/a3345a68-8f5c-4a49-b727-c542c50c414a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Can't assign LTE USB Modem (Non-endpoint PCI devices cannot be assigned to guests)
On Friday, August 24, 2018 at 6:08:54 AM UTC-4, awokd wrote:
> On Fri, August 24, 2018 9:53 am, Daniil .Travnikov wrote:
> > I have an LTE USB Modem which I used in Qubes 3.2 very well, but in Qubes
> > 4.0 I have some issues.
> >
> >
> >
> > First of all in Qubes Manager I can attach this usb modem only in HVM
> > mode ('ERROR: devices tab: Can't attach PCI device to VM in pvh mode').
> >
> >
> > So I changed in VM on HVM mode and attached just usb slot.
> >
> >
> >
> >
> > Then I tried to turn on my VM but I got 2 same error messages (first one
> > in windows and the second one on the top right corner):
> >
> > 'ERROR: Start failed: internal error: Non-endpoint PCI devices cannot be
> > assigned to guests, see /var/lob/libvirt/libxl/libxl-driver.log'
> >
> > 'Qube Status: usb
> > Domain usb has failed to start: Internal error: Non-endpoint PCI devices
> > cannot be assigned to guests'.
> >
> >
> > Tell me please what am I missing in Qubes 4.0?
>
> Do an "lspci" and "lspci -t" in dom0, and try attaching the leaf device
> instead. Sounds like you are trying to attach some type of bridge.
Thank you for your answer.
Before your message I tried to attach this device:
'00:1d.0 PCI bridge: Intel Corporation Device a330 (rev f0)'
and you saw which error I got.
After your message I thought maybe I am choosing not correct device and now I
am choosing this device:
'00:14.0 USB controller: Intel Corporation Device a36d (rev 10)'
and got another error messages:
'ERROR: Start failed: internal error: Unable to reset PCI device :00:14.0:
no FLR, PM reset or bus reset available, see
/var/log/libvirt/libxl/libxl-driver.log for details'
'Qube Status: usb
Domain usb has failed to start: internal error: Unable to reset PCI device
:00:14.0: no FLR, PM reset or bus reset available'.
--
You received this message because you are subscribed to the Google Groups
"qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to qubes-users+unsubscr...@googlegroups.com.
To post to this group, send email to qubes-users@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/qubes-users/87c3d0d3-afe8-4a2c-af7a-5ed07b459b56%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Can't assign LTE USB Modem (Non-endpoint PCI devices cannot be assigned to guests)
On Fri, August 24, 2018 9:53 am, Daniil .Travnikov wrote:
> I have an LTE USB Modem which I used in Qubes 3.2 very well, but in Qubes
> 4.0 I have some issues.
>
>
>
> First of all in Qubes Manager I can attach this usb modem only in HVM
> mode ('ERROR: devices tab: Can't attach PCI device to VM in pvh mode').
>
>
> So I changed in VM on HVM mode and attached just usb slot.
>
>
>
>
> Then I tried to turn on my VM but I got 2 same error messages (first one
> in windows and the second one on the top right corner):
>
> 'ERROR: Start failed: internal error: Non-endpoint PCI devices cannot be
> assigned to guests, see /var/lob/libvirt/libxl/libxl-driver.log'
>
> 'Qube Status: usb
> Domain usb has failed to start: Internal error: Non-endpoint PCI devices
> cannot be assigned to guests'.
>
>
> Tell me please what am I missing in Qubes 4.0?
Do an "lspci" and "lspci -t" in dom0, and try attaching the leaf device
instead. Sounds like you are trying to attach some type of bridge.
--
You received this message because you are subscribed to the Google Groups
"qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to qubes-users+unsubscr...@googlegroups.com.
To post to this group, send email to qubes-users@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/qubes-users/641085ee8e1e00ea9f33132a97b13472.squirrel%40tt3j2x4k5ycaa5zt.onion.
For more options, visit https://groups.google.com/d/optout.
[qubes-users] Can't assign LTE USB Modem (Non-endpoint PCI devices cannot be assigned to guests)
I have an LTE USB Modem which I used in Qubes 3.2 very well, but in Qubes 4.0 I
have some issues.
First of all in Qubes Manager I can attach this usb modem only in HVM mode
('ERROR: devices tab: Can't attach PCI device to VM in pvh mode').
So I changed in VM on HVM mode and attached just usb slot.
Then I tried to turn on my VM but I got 2 same error messages (first one in
windows and the second one on the top right corner):
'ERROR: Start failed: internal error: Non-endpoint PCI devices cannot be
assigned to guests, see /var/lob/libvirt/libxl/libxl-driver.log'
'Qube Status: usb
Domain usb has failed to start: Internal error: Non-endpoint PCI devices cannot
be assigned to guests'.
Tell me please what am I missing in Qubes 4.0?
P.S. In Qubes 3.2 (when I had some xenlight error) I just used this command:
'qvm-prefs -s vmname pci_strictreset false'. But here I suppose it's another
problem.
--
You received this message because you are subscribed to the Google Groups
"qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to qubes-users+unsubscr...@googlegroups.com.
To post to this group, send email to qubes-users@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/qubes-users/0f1058bc-4897-4b5c-a43f-290297f0b28f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
