Re: [qubes-users] Unable to start any VM. Getting: error starting vm: internal error: unable to reset PCI device 0000:

2017-01-28 Thread raahelps
On Thursday, January 26, 2017 at 7:07:10 PM UTC-5, Pietro Speroni di Fenizio 
wrote:
> On Thursday, January 26, 2017 at 2:43:41 AM UTC+1, Andrew David Wong wrote:
> > -BEGIN PGP SIGNED MESSAGE-
> > Hash: SHA512
> > 
> > On 2017-01-25 14:22, Pietro Speroni di Fenizio wrote:
> > > On Wednesday, January 25, 2017 at 11:13:54 PM UTC+1, Andrew David Wong 
> > > wrote:
> > > On 2017-01-25 13:27, Pietro Speroni di Fenizio wrote:
> >  Hello, we just installed a Qubes in a linux machine I had.
> > 
> >  Unfortunately the system seem to be unable to start any VM.
> > 
> >  I always get the same error: ERROR: internal error: unable to reset
> >  PCI device :03:00.2 internal error: Active :03:00.0 devices
> >  on bus with 000:03:00.2, not doing bus reset
> > 
> >  Can someone point me to the right direction? I seem stuck as
> >  anything requires me first to start a VM, but no VM seem to be able
> >  to start. In fact when the computer turns on at the beginning only
> >  dom0 is active and even sys-net and sys-firewall are inactive.
> > 
> >  Many thanks, Pietro
> > 
> > > 
> > > It sounds like you have this device assigned to more than one VM.
> > > Check the "Devices" tab in the VM Settings for each VM that has any
> > > devices assigned to it.
> > > 
> > > 
> > > Thanks,
> > > I just checked. Nothing is assigned in the other VM. Only sys-net had 2 
> > > of the three PCI assigned. Once I assigned the third it started working. 
> > > But now it gives me a Device not Managed next to the red network icon 
> > > above.
> > > 
> > > Thank you very much
> > > 
> > 
> > Have you tried setting pci_strictreset to false? (Make sure you understand 
> > the security implications first.)
> > 
> > https://www.qubes-os.org/doc/user-faq/#i-created-a-usbvm-and-assigned-usb-controllers-to-it-now-the-usbvm-wont-boot
> > 
> > - -- 
> > Andrew David Wong (Axon)
> > Community Manager, Qubes OS
> > https://www.qubes-os.org
> > -BEGIN PGP SIGNATURE-
> > 
> > iQIcBAEBCgAGBQJYiVQ5AAoJENtN07w5UDAwXRsP/1miXII9AR/4fTQ5rHQGMGUs
> > /zDhB098GKLgfP+x415tV376HjcGVuLM2wD61BTx+6etJdljwjwvuQ9YSzCYX4Uy
> > AMzIPlwmC/H7/Mqi0L2Dv95paNepKQnOin+W3uFWqejhOInMSR7mwYm5Nb0HBbRu
> > omsMQ9hsGwjpE6FErbT6H15D9mVYlDSGI8+pHqTciTMZgRQORXz8vUUJB1b6lQ+0
> > BRoflHllYKILVmQd4QL9nzO3fBEApgSPf4Psmvzl+V4wxt2seL27hux5lqgzay9l
> > VgPeNkMfmUqWXQodfy/9NP0Vb1YwZpTumCiDNDDxO20ju8cwgn6bMe1rd3CMsDB8
> > lSJZRnJ93tYh12IXbxd1vkaORH47HtZhfXEHSsuBNic8kazHhIDjQhawYfVFQnXd
> > S4waYC/cdE2NlJqRNrCyjbyUJxD4i1Wq+MvVjm7u4WnAwlJAcMw1vGR8RsxUg9VD
> > W8jkyCLTNk3JTC1sydTHH++uZ4z6RZ77WaPgVmsB2Wnw/63iiHbqiomLniPJLsrS
> > FI2r2YgNm+SE/LsM4hVzug7cKnlrL2dwBmEOcRhDn1qHLe+66rxxrAWGT9lsjxh7
> > Vni+SR40kAkgP/PZAbiAoI+7o3UXnUVoKKRH7eC4GwzQ2B9q6nWMj21uY0W79Njc
> > 84Ko8UGtCu0PNezI/5jr
> > =YE9m
> > -END PGP SIGNATURE
> 
> Update:
> I restarted the sys-net and now it just says:
> Ethernet Network
>disconnected
> 
> And under VPN connections >
> 
> So far I seem to be unable to run the wifi, but maybe it will be explained 
> later.
> 
> Thanks to all. I will now set this as complete.

wifi's are very sketchy in linux.  might need specific driver.  might want to 
google how to install your specific model wifi on fedora.

-- 
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/6ff1a8d9-2c11-4cce-8e5c-837369718fa0%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] Unable to start any VM. Getting: error starting vm: internal error: unable to reset PCI device 0000:

2017-01-26 Thread Pietro Speroni di Fenizio
On Thursday, January 26, 2017 at 2:43:41 AM UTC+1, Andrew David Wong wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA512
> 
> On 2017-01-25 14:22, Pietro Speroni di Fenizio wrote:
> > On Wednesday, January 25, 2017 at 11:13:54 PM UTC+1, Andrew David Wong 
> > wrote:
> > On 2017-01-25 13:27, Pietro Speroni di Fenizio wrote:
>  Hello, we just installed a Qubes in a linux machine I had.
> 
>  Unfortunately the system seem to be unable to start any VM.
> 
>  I always get the same error: ERROR: internal error: unable to reset
>  PCI device :03:00.2 internal error: Active :03:00.0 devices
>  on bus with 000:03:00.2, not doing bus reset
> 
>  Can someone point me to the right direction? I seem stuck as
>  anything requires me first to start a VM, but no VM seem to be able
>  to start. In fact when the computer turns on at the beginning only
>  dom0 is active and even sys-net and sys-firewall are inactive.
> 
>  Many thanks, Pietro
> 
> > 
> > It sounds like you have this device assigned to more than one VM.
> > Check the "Devices" tab in the VM Settings for each VM that has any
> > devices assigned to it.
> > 
> > 
> > Thanks,
> > I just checked. Nothing is assigned in the other VM. Only sys-net had 2 of 
> > the three PCI assigned. Once I assigned the third it started working. But 
> > now it gives me a Device not Managed next to the red network icon above.
> > 
> > Thank you very much
> > 
> 
> Have you tried setting pci_strictreset to false? (Make sure you understand 
> the security implications first.)
> 
> https://www.qubes-os.org/doc/user-faq/#i-created-a-usbvm-and-assigned-usb-controllers-to-it-now-the-usbvm-wont-boot
> 
> - -- 
> Andrew David Wong (Axon)
> Community Manager, Qubes OS
> https://www.qubes-os.org
> -BEGIN PGP SIGNATURE-
> 
> iQIcBAEBCgAGBQJYiVQ5AAoJENtN07w5UDAwXRsP/1miXII9AR/4fTQ5rHQGMGUs
> /zDhB098GKLgfP+x415tV376HjcGVuLM2wD61BTx+6etJdljwjwvuQ9YSzCYX4Uy
> AMzIPlwmC/H7/Mqi0L2Dv95paNepKQnOin+W3uFWqejhOInMSR7mwYm5Nb0HBbRu
> omsMQ9hsGwjpE6FErbT6H15D9mVYlDSGI8+pHqTciTMZgRQORXz8vUUJB1b6lQ+0
> BRoflHllYKILVmQd4QL9nzO3fBEApgSPf4Psmvzl+V4wxt2seL27hux5lqgzay9l
> VgPeNkMfmUqWXQodfy/9NP0Vb1YwZpTumCiDNDDxO20ju8cwgn6bMe1rd3CMsDB8
> lSJZRnJ93tYh12IXbxd1vkaORH47HtZhfXEHSsuBNic8kazHhIDjQhawYfVFQnXd
> S4waYC/cdE2NlJqRNrCyjbyUJxD4i1Wq+MvVjm7u4WnAwlJAcMw1vGR8RsxUg9VD
> W8jkyCLTNk3JTC1sydTHH++uZ4z6RZ77WaPgVmsB2Wnw/63iiHbqiomLniPJLsrS
> FI2r2YgNm+SE/LsM4hVzug7cKnlrL2dwBmEOcRhDn1qHLe+66rxxrAWGT9lsjxh7
> Vni+SR40kAkgP/PZAbiAoI+7o3UXnUVoKKRH7eC4GwzQ2B9q6nWMj21uY0W79Njc
> 84Ko8UGtCu0PNezI/5jr
> =YE9m
> -END PGP SIGNATURE

Update:
I restarted the sys-net and now it just says:
Ethernet Network
   disconnected

And under VPN connections >

So far I seem to be unable to run the wifi, but maybe it will be explained 
later.

Thanks to all. I will now set this as complete.

-- 
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/b63d9eb4-388b-458d-b853-24c9a3e8e461%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] Unable to start any VM. Getting: error starting vm: internal error: unable to reset PCI device 0000:

2017-01-25 Thread Andrew David Wong
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

On 2017-01-25 14:22, Pietro Speroni di Fenizio wrote:
> On Wednesday, January 25, 2017 at 11:13:54 PM UTC+1, Andrew David Wong wrote:
> On 2017-01-25 13:27, Pietro Speroni di Fenizio wrote:
 Hello, we just installed a Qubes in a linux machine I had.

 Unfortunately the system seem to be unable to start any VM.

 I always get the same error: ERROR: internal error: unable to reset
 PCI device :03:00.2 internal error: Active :03:00.0 devices
 on bus with 000:03:00.2, not doing bus reset

 Can someone point me to the right direction? I seem stuck as
 anything requires me first to start a VM, but no VM seem to be able
 to start. In fact when the computer turns on at the beginning only
 dom0 is active and even sys-net and sys-firewall are inactive.

 Many thanks, Pietro

> 
> It sounds like you have this device assigned to more than one VM.
> Check the "Devices" tab in the VM Settings for each VM that has any
> devices assigned to it.
> 
> 
> Thanks,
> I just checked. Nothing is assigned in the other VM. Only sys-net had 2 of 
> the three PCI assigned. Once I assigned the third it started working. But now 
> it gives me a Device not Managed next to the red network icon above.
> 
> Thank you very much
> 

Have you tried setting pci_strictreset to false? (Make sure you understand the 
security implications first.)

https://www.qubes-os.org/doc/user-faq/#i-created-a-usbvm-and-assigned-usb-controllers-to-it-now-the-usbvm-wont-boot

- -- 
Andrew David Wong (Axon)
Community Manager, Qubes OS
https://www.qubes-os.org
-BEGIN PGP SIGNATURE-

iQIcBAEBCgAGBQJYiVQ5AAoJENtN07w5UDAwXRsP/1miXII9AR/4fTQ5rHQGMGUs
/zDhB098GKLgfP+x415tV376HjcGVuLM2wD61BTx+6etJdljwjwvuQ9YSzCYX4Uy
AMzIPlwmC/H7/Mqi0L2Dv95paNepKQnOin+W3uFWqejhOInMSR7mwYm5Nb0HBbRu
omsMQ9hsGwjpE6FErbT6H15D9mVYlDSGI8+pHqTciTMZgRQORXz8vUUJB1b6lQ+0
BRoflHllYKILVmQd4QL9nzO3fBEApgSPf4Psmvzl+V4wxt2seL27hux5lqgzay9l
VgPeNkMfmUqWXQodfy/9NP0Vb1YwZpTumCiDNDDxO20ju8cwgn6bMe1rd3CMsDB8
lSJZRnJ93tYh12IXbxd1vkaORH47HtZhfXEHSsuBNic8kazHhIDjQhawYfVFQnXd
S4waYC/cdE2NlJqRNrCyjbyUJxD4i1Wq+MvVjm7u4WnAwlJAcMw1vGR8RsxUg9VD
W8jkyCLTNk3JTC1sydTHH++uZ4z6RZ77WaPgVmsB2Wnw/63iiHbqiomLniPJLsrS
FI2r2YgNm+SE/LsM4hVzug7cKnlrL2dwBmEOcRhDn1qHLe+66rxxrAWGT9lsjxh7
Vni+SR40kAkgP/PZAbiAoI+7o3UXnUVoKKRH7eC4GwzQ2B9q6nWMj21uY0W79Njc
84Ko8UGtCu0PNezI/5jr
=YE9m
-END PGP SIGNATURE-

-- 
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/f03031a3-fb7e-a077-9339-b3341e2632f8%40qubes-os.org.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] Unable to start any VM. Getting: error starting vm: internal error: unable to reset PCI device 0000:

2017-01-25 Thread Pietro Speroni di Fenizio
On Wednesday, January 25, 2017 at 11:13:54 PM UTC+1, Andrew David Wong wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA512
> 
> On 2017-01-25 13:27, Pietro Speroni di Fenizio wrote:
> > Hello, we just installed a Qubes in a linux machine I had.
> > 
> > Unfortunately the system seem to be unable to start any VM.
> > 
> > I always get the same error: ERROR: internal error: unable to reset
> > PCI device :03:00.2 internal error: Active :03:00.0 devices
> > on bus with 000:03:00.2, not doing bus reset
> > 
> > Can someone point me to the right direction? I seem stuck as
> > anything requires me first to start a VM, but no VM seem to be able
> > to start. In fact when the computer turns on at the beginning only
> > dom0 is active and even sys-net and sys-firewall are inactive.
> > 
> > Many thanks, Pietro
> > 
> 
> It sounds like you have this device assigned to more than one VM.
> Check the "Devices" tab in the VM Settings for each VM that has any
> devices assigned to it.
> 
> - -- 
> Andrew David Wong (Axon)
> Community Manager, Qubes OS
> https://www.qubes-os.org
> -BEGIN PGP SIGNATURE-
> 
> iQIcBAEBCgAGBQJYiSMSAAoJENtN07w5UDAw7P4P+wYMA1LsNPhGqKLKZuGLICgk
> MfxYtldPdbhlLRC1RFx6bKTdZxpUVpSVtfNszKS56/0dZERonfKwMcGREvZxdHvu
> lMxSVvfsPqPG436MH8mEDNU9iMBttNzPKC5tuoxhLGJBz+GPvi708nDRvAXWFylY
> IbaU7cih0/7IF8JgQ7/qgE5g4xbGY8nStsJby6aPxumtcrXzt6NHTnFE31KeVDEh
> Rw4nARrOc2wrTH6PrEF6AEMjORQbXJau9pzsmQSSFMyLTIpiLIa9LBrEtaRwC6fM
> PXJ+NvYtu8YDVT7sli7mdhsdpN0sS83W2ao78yKyfjLHjtPt72o+xLC5a2Y0jg2L
> 537EROJpCRpjiwgH5myDSBtGfbfHXzU0d3D9Va6mClxWDPnZ6eThc0/R4ds0CcnN
> F2SQsq3LZrXEN1HO2Ec3rUL/AnR2LSuQBRIwznOg+5Q7y9InUcpdO9vQyQPyVl2Q
> mWgxc+13nl0DweCNpugbrOa8DXyEKYjt93IuW2/83wG7wQykCDZwkGM2y7sFdBFh
> r1bgNpQU2NnN0r6IFHMCcjOV//X54cWYUWVFEHw/AZk86FybclyIhsX/0qFeCvj5
> dgzOD1HLQyOfVH6YKPzglB1GEPelqaEDTri2Jpwx+fR47zyr3UbdM2yrTVOU99WP
> 3R04DPOH5UV2m/jUxzYP
> =6Ai6
> -END PGP SIGNATURE-

Thanks,
I just checked. Nothing is assigned in the other VM. Only sys-net had 2 of the 
three PCI assigned. Once I assigned the third it started working. But now it 
gives me a Device not Managed next to the red network icon above.

Thank you very much

-- 
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/2129ba99-cd38-4f01-bba3-35491642d482%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] Unable to start any VM. Getting: error starting vm: internal error: unable to reset PCI device 0000:

2017-01-25 Thread Andrew David Wong
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

On 2017-01-25 13:27, Pietro Speroni di Fenizio wrote:
> Hello, we just installed a Qubes in a linux machine I had.
> 
> Unfortunately the system seem to be unable to start any VM.
> 
> I always get the same error: ERROR: internal error: unable to reset
> PCI device :03:00.2 internal error: Active :03:00.0 devices
> on bus with 000:03:00.2, not doing bus reset
> 
> Can someone point me to the right direction? I seem stuck as
> anything requires me first to start a VM, but no VM seem to be able
> to start. In fact when the computer turns on at the beginning only
> dom0 is active and even sys-net and sys-firewall are inactive.
> 
> Many thanks, Pietro
> 

It sounds like you have this device assigned to more than one VM.
Check the "Devices" tab in the VM Settings for each VM that has any
devices assigned to it.

- -- 
Andrew David Wong (Axon)
Community Manager, Qubes OS
https://www.qubes-os.org
-BEGIN PGP SIGNATURE-

iQIcBAEBCgAGBQJYiSMSAAoJENtN07w5UDAw7P4P+wYMA1LsNPhGqKLKZuGLICgk
MfxYtldPdbhlLRC1RFx6bKTdZxpUVpSVtfNszKS56/0dZERonfKwMcGREvZxdHvu
lMxSVvfsPqPG436MH8mEDNU9iMBttNzPKC5tuoxhLGJBz+GPvi708nDRvAXWFylY
IbaU7cih0/7IF8JgQ7/qgE5g4xbGY8nStsJby6aPxumtcrXzt6NHTnFE31KeVDEh
Rw4nARrOc2wrTH6PrEF6AEMjORQbXJau9pzsmQSSFMyLTIpiLIa9LBrEtaRwC6fM
PXJ+NvYtu8YDVT7sli7mdhsdpN0sS83W2ao78yKyfjLHjtPt72o+xLC5a2Y0jg2L
537EROJpCRpjiwgH5myDSBtGfbfHXzU0d3D9Va6mClxWDPnZ6eThc0/R4ds0CcnN
F2SQsq3LZrXEN1HO2Ec3rUL/AnR2LSuQBRIwznOg+5Q7y9InUcpdO9vQyQPyVl2Q
mWgxc+13nl0DweCNpugbrOa8DXyEKYjt93IuW2/83wG7wQykCDZwkGM2y7sFdBFh
r1bgNpQU2NnN0r6IFHMCcjOV//X54cWYUWVFEHw/AZk86FybclyIhsX/0qFeCvj5
dgzOD1HLQyOfVH6YKPzglB1GEPelqaEDTri2Jpwx+fR47zyr3UbdM2yrTVOU99WP
3R04DPOH5UV2m/jUxzYP
=6Ai6
-END PGP SIGNATURE-

-- 
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/b0271ec1-59d1-61d0-4c9c-7c1271cf3e9d%40qubes-os.org.
For more options, visit https://groups.google.com/d/optout.