Re: [qubes-users] Re: Qubes 4.0-rc2 :: VMs fail to start

[Roy Bernat]

On Thursday, 2 November 2017 09:25:30 UTC-4, cooloutac  wrote:
> On Thursday, November 2, 2017 at 4:21:38 AM UTC-4, [799] wrote:
> > Hello,
> > 
> > >> Did you make it permanently ? 
> > 
> > Yes of course :-) but thank you for the reminder, I edited in once in grub 
> > for the first boot after installation and then applied it in the Grub 
> > configuration.
> > Same results, VMs won't start - it seems only the both sys network VMs work.
> > 
> > >> Dont give up :) 
> > 
> > Of course not ... Don't be afraid, there ist just nothing more I can 
> > contribute to the Devs and I am sure the topic will be solved in the next 
> > Release Candidate.
> > Happy to test then, but it seems that this horse is dead (or I have the 
> > wrong saddle to ride it).
> > 
> > [799]
> 
> Think iommu is nescessary in 4.0,  I could be wrong.  Does  the stock bios on 
> your machine support it maybe?

It is not needed .  for me now after the remove of iommu all worked .  need to 
say that the templates  need to be update in order to work .  so if you are 
update the dom0 you should also update the templates . 

R 

-- 
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/1187bb07-4370-466c-b451-9bc22ca0b418%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Re: Qubes 4.0-rc2 :: VMs fail to start

[cooloutac]

On Thursday, November 2, 2017 at 4:21:38 AM UTC-4, [799] wrote:
> Hello,
> 
> >> Did you make it permanently ? 
> 
> Yes of course :-) but thank you for the reminder, I edited in once in grub 
> for the first boot after installation and then applied it in the Grub 
> configuration.
> Same results, VMs won't start - it seems only the both sys network VMs work.
> 
> >> Dont give up :) 
> 
> Of course not ... Don't be afraid, there ist just nothing more I can 
> contribute to the Devs and I am sure the topic will be solved in the next 
> Release Candidate.
> Happy to test then, but it seems that this horse is dead (or I have the wrong 
> saddle to ride it).
> 
> [799]

Think iommu is nescessary in 4.0,  I could be wrong.  Does  the stock bios on 
your machine support it maybe?

-- 
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/68b14735-bbf7-4c05-93ee-d7160fe47ac5%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

AW: [qubes-users] Re: Qubes 4.0-rc2 :: VMs fail to start

['[799]' via qubes-users]

Hello,

>> Did you make it permanently ?

Yes of course :-) but thank you for the reminder, I edited in once in grub for 
the first boot after installation and then applied it in the Grub configuration.
Same results, VMs won't start - it seems only the both sys network VMs work.

>> Dont give up :)

Of course not ... Don't be afraid, there ist just nothing more I can contribute 
to the Devs and I am sure the topic will be solved in the next Release 
Candidate.
Happy to test then, but it seems that this horse is dead (or I have the wrong 
saddle to ride it).

[799]

-- 
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/2IxLUmJFmspoGKHVjB6035DAcwPVJZ5ryNNKzEGz170zEWn4wr3eAV1H2IDjrm9A5jUN3XDapNRqrGQhd02jduLd4gxZnIDoPG5u_rhDnTU%3D%40protonmail.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Re: Qubes 4.0-rc2 :: VMs fail to start

[Roy Bernat]

On Wednesday, 25 October 2017 13:26:51 UTC-4, [799]  wrote:
> Hello,
> 
> As at least one other Qubes user has the same problem, that VMs won't start, 
> I'll add this as special topic.
> 
> I've made a clean install of Qubes 4-rc2 but ~70% of the time I can't boot 
> the VMs.
> This includes sys-net, sys-firewall, but also others.
> 
> I tried to check the logs but I don't get any valuable information.
> See screenshot.
> 
> I started the following command in dom0:
> 
> watch -n 1 xl list
> 
> When I try to launch a VM I can see that the VMs appears in the xl list 
> output, but the State is -- and the Time(s) is 0.0.
> After ~30sec the start is aborted with error message: Cannot execute 
> qrexec-daemon.
> 
> Questions:
> 1) is anyone running Qubes 4.0-rc2 on a Lenovo X230?
> 2) is someone additionaly running Coreboot?
> 3) I am running the Qubes Installation with the default settings, any options 
> to tweak on the Grub command line
> 
> [799]
> 
> 
> 
> 
> 
> Gesendet von ProtonMail mobile

Did you make it permanently ?  inside the grub ?   

Open a terminal in dom0
Edit /etc/default/grub (e.g. sudo nano /etc/default/grub)
Add to the line GRUB_CMDLINE_XEN_DEFAULT the setting iommu=no-igfx, save and 
quit
Commit the change withsudo grub2-mkconfig --output /boot/grub2/grub.cfg

Dont give up :) 


R 

-- 
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/26a55533-40d9-4e86-83ab-d7f544c4b19b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

AW: Re: [qubes-users] Re: Qubes 4.0-rc2 :: VMs fail to start

['[799]' via qubes-users]

Hello,

I tried the suggestion to remove the iommu line from Grub and did so on the 
first reboot after the installation.

Strangely this seems to work for sys-net and sys-firewall which boot up fine.
I also once been able to launch a disposable VM.
sys-usb and also other VMs which I've created using the same template like 
sys-net sys-firewall.
While sys-usb creates an error message. The other VMs don't give any error 
message, I can see the VMs shortly when I enter "watch -n 1 xl list" in the 
terminal, but that's it.
After a few seconds they fade away.

I have also been unable to start a new disposable on the next reboot.

As I can't give any qualified details why Qubes 4 behaves like this, I'll wait 
for Qubes 4-rc3.

What I would like to see is a information on which Hardware Qubes 4 has been 
successfully installed and launched at least once, including the start of the 
sys-vms and at least one AppVM.
If this basic functionality is given, I am happy to test - currently 4.0-rc2 
doesn't feel like it is ready to be a release candidate yet.

[799]

 Original-Nachricht 
An 1. Nov. 2017, 01:41, Sergio da Matta schrieb:

> Dear Sir,
>
> I think all the people needs feedback, but I know they are just a few people.
> And even that, Qubes are each time better ...
> Let's wait. Good luck.
>
> "7126 52E0 5754 8FEA BA46  9318 A3E7 BA7C 6D76 B8D7
> gmail/hangouts/skype/instagram/twitter/[sip.justvoip.com](http://sip.justvoip.com/)
>  : sergiomatta
>  whatsapp 031998050020, 06140639186" 
>
> 2017-10-31 22:25 GMT-02:00 [799] :
>
>> Hello,
>>
>> Honestly what is bothering me a bit, is that there seem to be lots of 
>> problems with Qubes 4-rc2, which is ok, as it is a testing release - bit I'd 
>> like to see more feedback from the Qubes Dev's, so that we can find out what 
>> is the Root cause.
>>
>> Isn't this how a test release should work? We (normal) users are testing, so 
>> that developers can get a qualified feedback what needs to be fixed.
>>
>> Or am I missing something and there is some action on the developer mailing 
>> list?
>>
>> [799]

-- 
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/ChIerVb-rThYIlazF-SfMoefTQ0psRblc-qQrlH4wzgSYx2bbja0nWJBG-NOTqtHme0DbqDh8tJtjs270Ojf6PouObN9x_UlX9RefOOjtjo%3D%40protonmail.com.
For more options, visit https://groups.google.com/d/optout.

AW: [qubes-users] Re: Qubes 4.0-rc2 :: VMs fail to start

['[799]' via qubes-users]

Hello,

>> Hi all sergio matta mention to remove the
>> iommu=no-igfx. this solve the problem and i
>> think it will solve 90% of you the issue . so
>> the credit is for you sergio . Thanks . R

I've reinstalled Qubes 4rc2 and removed the line "iommu=no-igfx" upon first 
restart (after installing Qubes).

I found a small bug/typo in Grub, where it says that I should press Enter to 
boot, while the correct command is Ctrl+X.

Currently the installer is installing the default AppVMs. I'll keep you updated.
So far it looks good.

[799]

-- 
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/ijUiNaExeZ6NH-dFiY-Hp3ETjjycNLesDTZ8yU7Duhv7FEnnQI5XGyA9wO2x0OHyF2br6ak_hi0DKqqmAdKatWUDEqKv7NqLFAKnrJuyiRI%3D%40protonmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: AW: [qubes-users] Re: Qubes 4.0-rc2 :: VMs fail to start

[Caleb Smith]

Hey y'all, I have found some workarounds for getting VMs to boot. If you
change the virt_mode to pv instead of hvm, usually sys-usb and sys-firewall
will begin to boot regularly. I also increased the qrexec-timeout to 120
per someone's recommendation here, and that seemed to help sys-whonix boot
better. Also running VMs in "debug mode" in the VM Settings UI seems to
help a little bit.

Hope this helps!

- Caleb Smith

On Wed, Nov 1, 2017, 9:19 AM awokd  wrote:

> On Wed, November 1, 2017 00:25, '[799]' via qubes-users wrote:
>
> > Or am I missing something and there is some action on the developer
> > mailing list?
>
> I was looking forward to trying out 4.0rc2 as well. Was a bit disappointed
> to hit a roadblock, but I understand not all issues are going to be
> smoothed out at this early stage. One idea I saw in here that might help
> some test is to install 4.0rc2 directly to another USB stick and boot from
> there for testing, but it could be slow.
>
> I suspect the developers are probably spending most of their time working
> on items in here! https://github.com/QubesOS/qubes-issues/issues .
>
>
>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "qubes-users" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/qubes-users/viQYrFSv48E/unsubscribe.
> To unsubscribe from this group and all its topics, 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/7f892ffac16ea218945b37025d0a20a1%40elude.in
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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/CAO67bxM0A9_tRXzfFYWfamA%3DVz6stpvjR9Vw299a%2BfA3GZ0UfQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: AW: [qubes-users] Re: Qubes 4.0-rc2 :: VMs fail to start

[awokd]

On Wed, November 1, 2017 00:25, '[799]' via qubes-users wrote:

> Or am I missing something and there is some action on the developer
> mailing list?

I was looking forward to trying out 4.0rc2 as well. Was a bit disappointed
to hit a roadblock, but I understand not all issues are going to be
smoothed out at this early stage. One idea I saw in here that might help
some test is to install 4.0rc2 directly to another USB stick and boot from
there for testing, but it could be slow.

I suspect the developers are probably spending most of their time working
on items in here! https://github.com/QubesOS/qubes-issues/issues .



-- 
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/7f892ffac16ea218945b37025d0a20a1%40elude.in.
For more options, visit https://groups.google.com/d/optout.

AW: [qubes-users] Re: Qubes 4.0-rc2 :: VMs fail to start

['[799]' via qubes-users]

Hello,

Honestly what is bothering me a bit, is that there seem to be lots of problems 
with Qubes 4-rc2, which is ok, as it is a testing release - bit I'd like to see 
more feedback from the Qubes Dev's, so that we can find out what is the Root 
cause.

Isn't this how a test release should work? We (normal) users are testing, so 
that developers can get a qualified feedback what needs to be fixed.

Or am I missing something and there is some action on the developer mailing 
list?

[799]

-- 
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/cN0eVl_x2fCMyjKkbEij_kCRXH6Ba5tuKBWwe93gCxehDdXW17GSVDgmVxqhGk6z1bEVnNCEvjBgW8d3P_4k8Uy9IO0QF1WR1RoCkbBTdbQ%3D%40protonmail.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Re: Qubes 4.0-rc2 :: VMs fail to start

[Sergio Matta]

Em terça-feira, 31 de outubro de 2017 11:10:22 UTC-2, Roy Bernat  escreveu:
> On Tuesday, 31 October 2017 14:56:46 UTC+2, Roy Bernat  wrote:
> > On Tuesday, 31 October 2017 14:52:10 UTC+2, Roy Bernat  wrote:
> > > On Wednesday, 25 October 2017 20:26:51 UTC+3, [799]  wrote:
> > > > Hello,
> > > > 
> > > > As at least one other Qubes user has the same problem, that VMs won't 
> > > > start, I'll add this as special topic.
> > > > 
> > > > I've made a clean install of Qubes 4-rc2 but ~70% of the time I can't 
> > > > boot the VMs.
> > > > This includes sys-net, sys-firewall, but also others.
> > > > 
> > > > I tried to check the logs but I don't get any valuable information.
> > > > See screenshot.
> > > > 
> > > > I started the following command in dom0:
> > > > 
> > > > watch -n 1 xl list
> > > > 
> > > > When I try to launch a VM I can see that the VMs appears in the xl list 
> > > > output, but the State is -- and the Time(s) is 0.0.
> > > > After ~30sec the start is aborted with error message: Cannot execute 
> > > > qrexec-daemon.
> > > > 
> > > > Questions:
> > > > 1) is anyone running Qubes 4.0-rc2 on a Lenovo X230?
> > > > 2) is someone additionaly running Coreboot?
> > > > 3) I am running the Qubes Installation with the default settings, any 
> > > > options to tweak on the Grub command line
> > > > 
> > > > [799]
> > > > 
> > > > 
> > > > 
> > > > 
> > > > 
> > > > Gesendet von ProtonMail mobile
> > > 
> > > not worked for me . 
> > > 
> > > until now i dont know what cause this issue ? 
> > > 
> > > this is a huge bug the cause us not to work .  for me 3.2 dont work so i 
> > > have only one option .  By the way rc01 worked ok 
> > 
> > It seems that asomething with the sys-net causing the sys-firewall not 
> > working 
> 
> Someone of the developer know this issue ?   and maybe he will have a 
> workaround until fix . 
> R

I am not a developer. Sorry if I get wrong you problem. Are you sure it is not 
a iommu problem? Did you tested (qubes-hcl-report on dom0 terminal)? Mine has 
no iommu and is working with PV until next oct-10, when arrives my 990fx 
chipset motherboard to my old AM3 cpu. See  
https://groups.google.com/forum/#!searchin/qubes-users/iommu/qubes-users/QZIWyQVFYp4/vfeC58rhAgAJ

-- 
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/0044c7d0-a7dd-4d9b-82cf-4e0c3f12a6ae%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Re: Qubes 4.0-rc2 :: VMs fail to start

[William Bormann]

I had this problem as well.  However, the problem vanished when I adjusted the 
qrexec_timeout setting to 120 via qvm-prefs for the desired VMs.

This kind of makes sense, since I'm doing my RC2 testing from a usb stick 
(color me cautious).

-- 
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/227ac3ab-6c00-40ae-a2e0-e82f2e5bc35f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Re: Qubes 4.0-rc2 :: VMs fail to start

[belac1000]

On Wednesday, October 25, 2017 at 11:26:51 AM UTC-6, [799] wrote:
> Hello,
> 
> As at least one other Qubes user has the same problem, that VMs won't start, 
> I'll add this as special topic.
> 
> I've made a clean install of Qubes 4-rc2 but ~70% of the time I can't boot 
> the VMs.
> This includes sys-net, sys-firewall, but also others.
> 
> I tried to check the logs but I don't get any valuable information.
> See screenshot.
> 
> I started the following command in dom0:
> 
> watch -n 1 xl list
> 
> When I try to launch a VM I can see that the VMs appears in the xl list 
> output, but the State is -- and the Time(s) is 0.0.
> After ~30sec the start is aborted with error message: Cannot execute 
> qrexec-daemon.
> 
> Questions:
> 1) is anyone running Qubes 4.0-rc2 on a Lenovo X230?
> 2) is someone additionaly running Coreboot?
> 3) I am running the Qubes Installation with the default settings, any options 
> to tweak on the Grub command line
> 
> [799]
> 
> 
> 

For what it's worth, I'm having the same issues on a stock-BIOS X220. Sometimes 
a random reboot will give me both sys-net and sys-firewall, but the other two 
never come up, it's very problematic and very finnicky. If you do find a 
solution/workaround, please let me know.

-- 
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/2f4e5352-f832-4508-936a-88e292c9d048%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Re: Qubes 4.0-rc2 :: VMs fail to start

[Roy Bernat]

Not working 

Found that with debug it’s starting but then the appvm not...

-- 
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/6ecb46ca-9cf7-4c4d-802a-2d0ec36573e0%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Re: Qubes 4.0-rc2 :: VMs fail to start

[Foppe de Haan]

On Tuesday, October 31, 2017 at 1:56:46 PM UTC+1, Roy Bernat wrote:
> On Tuesday, 31 October 2017 14:52:10 UTC+2, Roy Bernat  wrote:
> > On Wednesday, 25 October 2017 20:26:51 UTC+3, [799]  wrote:
> > > Hello,
> > > 
> > > As at least one other Qubes user has the same problem, that VMs won't 
> > > start, I'll add this as special topic.
> > > 
> > > I've made a clean install of Qubes 4-rc2 but ~70% of the time I can't 
> > > boot the VMs.
> > > This includes sys-net, sys-firewall, but also others.
> > > 
> > > I tried to check the logs but I don't get any valuable information.
> > > See screenshot.
> > > 
> > > I started the following command in dom0:
> > > 
> > > watch -n 1 xl list
> > > 
> > > When I try to launch a VM I can see that the VMs appears in the xl list 
> > > output, but the State is -- and the Time(s) is 0.0.
> > > After ~30sec the start is aborted with error message: Cannot execute 
> > > qrexec-daemon.
> > > 
> > > Questions:
> > > 1) is anyone running Qubes 4.0-rc2 on a Lenovo X230?
> > > 2) is someone additionaly running Coreboot?
> > > 3) I am running the Qubes Installation with the default settings, any 
> > > options to tweak on the Grub command line
> > > 
> > > [799]
> > > 
> > > 
> > > 
> > > 
> > > 
> > > Gesendet von ProtonMail mobile
> > 
> > not worked for me . 
> > 
> > until now i dont know what cause this issue ? 
> > 
> > this is a huge bug the cause us not to work .  for me 3.2 dont work so i 
> > have only one option .  By the way rc01 worked ok 
> 
> It seems that asomething with the sys-net causing the sys-firewall not 
> working 

try changing the sys-net template to debian?

-- 
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/83a385b5-bd13-4ea7-8054-736e5887da22%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Re: Qubes 4.0-rc2 :: VMs fail to start

[Roy Bernat]

On Tuesday, 31 October 2017 14:56:46 UTC+2, Roy Bernat  wrote:
> On Tuesday, 31 October 2017 14:52:10 UTC+2, Roy Bernat  wrote:
> > On Wednesday, 25 October 2017 20:26:51 UTC+3, [799]  wrote:
> > > Hello,
> > > 
> > > As at least one other Qubes user has the same problem, that VMs won't 
> > > start, I'll add this as special topic.
> > > 
> > > I've made a clean install of Qubes 4-rc2 but ~70% of the time I can't 
> > > boot the VMs.
> > > This includes sys-net, sys-firewall, but also others.
> > > 
> > > I tried to check the logs but I don't get any valuable information.
> > > See screenshot.
> > > 
> > > I started the following command in dom0:
> > > 
> > > watch -n 1 xl list
> > > 
> > > When I try to launch a VM I can see that the VMs appears in the xl list 
> > > output, but the State is -- and the Time(s) is 0.0.
> > > After ~30sec the start is aborted with error message: Cannot execute 
> > > qrexec-daemon.
> > > 
> > > Questions:
> > > 1) is anyone running Qubes 4.0-rc2 on a Lenovo X230?
> > > 2) is someone additionaly running Coreboot?
> > > 3) I am running the Qubes Installation with the default settings, any 
> > > options to tweak on the Grub command line
> > > 
> > > [799]
> > > 
> > > 
> > > 
> > > 
> > > 
> > > Gesendet von ProtonMail mobile
> > 
> > not worked for me . 
> > 
> > until now i dont know what cause this issue ? 
> > 
> > this is a huge bug the cause us not to work .  for me 3.2 dont work so i 
> > have only one option .  By the way rc01 worked ok 
> 
> It seems that asomething with the sys-net causing the sys-firewall not 
> working 

Someone of the developer know this issue ?   and maybe he will have a 
workaround until fix . 
R

-- 
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/5acb43ad-f051-4060-a27a-4e942c6c3913%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Re: Qubes 4.0-rc2 :: VMs fail to start

[Roy Bernat]

On Tuesday, 31 October 2017 14:52:10 UTC+2, Roy Bernat  wrote:
> On Wednesday, 25 October 2017 20:26:51 UTC+3, [799]  wrote:
> > Hello,
> > 
> > As at least one other Qubes user has the same problem, that VMs won't 
> > start, I'll add this as special topic.
> > 
> > I've made a clean install of Qubes 4-rc2 but ~70% of the time I can't boot 
> > the VMs.
> > This includes sys-net, sys-firewall, but also others.
> > 
> > I tried to check the logs but I don't get any valuable information.
> > See screenshot.
> > 
> > I started the following command in dom0:
> > 
> > watch -n 1 xl list
> > 
> > When I try to launch a VM I can see that the VMs appears in the xl list 
> > output, but the State is -- and the Time(s) is 0.0.
> > After ~30sec the start is aborted with error message: Cannot execute 
> > qrexec-daemon.
> > 
> > Questions:
> > 1) is anyone running Qubes 4.0-rc2 on a Lenovo X230?
> > 2) is someone additionaly running Coreboot?
> > 3) I am running the Qubes Installation with the default settings, any 
> > options to tweak on the Grub command line
> > 
> > [799]
> > 
> > 
> > 
> > 
> > 
> > Gesendet von ProtonMail mobile
> 
> not worked for me . 
> 
> until now i dont know what cause this issue ? 
> 
> this is a huge bug the cause us not to work .  for me 3.2 dont work so i have 
> only one option .  By the way rc01 worked ok 

It seems that asomething with the sys-net causing the sys-firewall not working 


-- 
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/fe760441-9082-42d9-bdbf-3843f875b495%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Re: Qubes 4.0-rc2 :: VMs fail to start

[Roy Bernat]

On Wednesday, 25 October 2017 20:26:51 UTC+3, [799]  wrote:
> Hello,
> 
> As at least one other Qubes user has the same problem, that VMs won't start, 
> I'll add this as special topic.
> 
> I've made a clean install of Qubes 4-rc2 but ~70% of the time I can't boot 
> the VMs.
> This includes sys-net, sys-firewall, but also others.
> 
> I tried to check the logs but I don't get any valuable information.
> See screenshot.
> 
> I started the following command in dom0:
> 
> watch -n 1 xl list
> 
> When I try to launch a VM I can see that the VMs appears in the xl list 
> output, but the State is -- and the Time(s) is 0.0.
> After ~30sec the start is aborted with error message: Cannot execute 
> qrexec-daemon.
> 
> Questions:
> 1) is anyone running Qubes 4.0-rc2 on a Lenovo X230?
> 2) is someone additionaly running Coreboot?
> 3) I am running the Qubes Installation with the default settings, any options 
> to tweak on the Grub command line
> 
> [799]
> 
> 
> 
> 
> 
> Gesendet von ProtonMail mobile

not worked for me . 

until now i dont know what cause this issue ? 

this is a huge bug the cause us not to work .  for me 3.2 dont work so i have 
only one option .  By the way rc01 worked ok  

-- 
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/4db91507-6b35-4f04-b378-f4adf0e50495%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Re: Qubes 4.0-rc2 :: VMs fail to start

[Chris Laprise]

On 10/31/17 05:21, RSS wrote:

I see I am not alone here.


Having the information on which laptops Qubes 4 "should" run or even
more where it is running (Dev Users?) would help. The HCL
https://www.qubes-os.org/hcl/ does not help me, as it has no
information if 4.x is ok for the X230.

It looks to me like a bigger problem, not necessarily device specific:
https://github.com/QubesOS/qubes-issues/issues/3221

Remember this is not a public release, this is RC2. Release CANDIDATE 2.
That means it is a version meant for TESTING, not necessarily ready for
anything more.

TEST_FAILED


As mentioned before I am running Coreboot, should I go back to stock
ROM?

In fact I have an x230 without Coreboot, and I too cannot reliably even
get sys-net to run, let alone sys-firewall, which I do not think I have
seen running once.


FYI the internal ethernet controller seems to give RC2 sys-net big 
problems. I had to remove it from my sys-net Devices list, so there is 
only wifi. So my sys-net will usually start, but not the other VMs 
following it.




Personally I am going to close the lid and wait for the next release.
(Unless anyone would like to collect some debug information from me.)




--

Chris Laprise, tas...@posteo.net
https://github.com/tasket
https://twitter.com/ttaskett
PGP: BEE2 20C5 356E 764A 73EB  4AB3 1DC4 D106 F07F 1886

--
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/5655a465-7622-9a2b-11a1-e19704e144be%40posteo.net.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Re: Qubes 4.0-rc2 :: VMs fail to start

[RSS]

I see I am not alone here.

> Having the information on which laptops Qubes 4 "should" run or even
> more where it is running (Dev Users?) would help. The HCL
> https://www.qubes-os.org/hcl/ does not help me, as it has no
> information if 4.x is ok for the X230.

It looks to me like a bigger problem, not necessarily device specific:
https://github.com/QubesOS/qubes-issues/issues/3221

Remember this is not a public release, this is RC2. Release CANDIDATE 2.
That means it is a version meant for TESTING, not necessarily ready for
anything more.

TEST_FAILED

> As mentioned before I am running Coreboot, should I go back to stock
> ROM?

In fact I have an x230 without Coreboot, and I too cannot reliably even
get sys-net to run, let alone sys-firewall, which I do not think I have
seen running once.

Personally I am going to close the lid and wait for the next release.
(Unless anyone would like to collect some debug information from me.)

-- 
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/20171031172103.7d8826c0%40x220i.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Re: Qubes 4.0-rc2 :: VMs fail to start

[Chris Laprise]

On 10/30/17 16:29, Roy Bernat wrote:

On Wednesday, 25 October 2017 13:26:51 UTC-4, [799]  wrote:

Hello,

As at least one other Qubes user has the same problem, that VMs won't start, 
I'll add this as special topic.

I've made a clean install of Qubes 4-rc2 but ~70% of the time I can't boot the 
VMs.
This includes sys-net, sys-firewall, but also others.

I tried to check the logs but I don't get any valuable information.
See screenshot.

I started the following command in dom0:

watch -n 1 xl list

When I try to launch a VM I can see that the VMs appears in the xl list output, 
but the State is -- and the Time(s) is 0.0.
After ~30sec the start is aborted with error message: Cannot execute 
qrexec-daemon.

Questions:
1) is anyone running Qubes 4.0-rc2 on a Lenovo X230?
2) is someone additionaly running Coreboot?
3) I am running the Qubes Installation with the default settings, any options 
to tweak on the Grub command line

[799]





Gesendet von ProtonMail mobile

no one has any idea ?  i tried to look for some logs with no solution .

what i have found that it happen mpre if i update the dom0 before i am updating 
the templates .

maybe 

Roy



Over the past couple days, this has usually worked:

1. Close any appVMs that appear to be using lots of RAM and are not 
giving it back.


2. Start an isolated (network setting is "none") appVM... it should 
start up. Leave it running...


3. Start the VMs you intend to use; they should also start now.

--

Chris Laprise, tas...@posteo.net
https://github.com/tasket
https://twitter.com/ttaskett
PGP: BEE2 20C5 356E 764A 73EB  4AB3 1DC4 D106 F07F 1886

--
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/c17cfc69-9019-9cff-30ae-5b1584af2ba1%40posteo.net.
For more options, visit https://groups.google.com/d/optout.

AW: [qubes-users] Re: Qubes 4.0-rc2 :: VMs fail to start

['[799]' via qubes-users]

Hello Rob,

>> So what is the solution ? Every reboot I am
>> struggle to Start the vm’s

As I haven't seen any good solution for this yet, I recommend going back to 
Qubes 3.2 until 4.0 has been updated to fix this or until we know what is 
causing the problems (hardware?).

[799]

-- 
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/Dwat7n5DGrJThbSI2WeZFbsHWLlTkZLyvGcayi_3Dg7R81imem3LgVx9NhX4f1XVFelLKKTA95Pz4wP2jNojYAkXUTV79sP8SRhmLNCoVtc%3D%40protonmail.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Re: Qubes 4.0-rc2 :: VMs fail to start

[Roy Bernat]

And now the sys firewall don’t start anymore .  Someone 

Hel

-- 
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/e0f6f2dc-c470-4ceb-be7d-fd4156f6bcd6%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Re: Qubes 4.0-rc2 :: VMs fail to start

[Roy Bernat]

So what is the solution ? Every reboot I am struggle to 
Start the vm’s 

-- 
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/9c5485d4-bbde-4fc4-936a-ad046ff5fe44%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Re: Qubes 4.0-rc2 :: VMs fail to start

[aphidfarmer]

On Wednesday, October 25, 2017 at 10:26:51 AM UTC-7, [799] wrote:
> Hello,
> 
> As at least one other Qubes user has the same problem, that VMs won't start, 
> I'll add this as special topic.
> 
> I've made a clean install of Qubes 4-rc2 but ~70% of the time I can't boot 
> the VMs.
> This includes sys-net, sys-firewall, but also others.
> 
> I tried to check the logs but I don't get any valuable information.
> See screenshot.
> 
> I started the following command in dom0:
> 
> watch -n 1 xl list
> 
> When I try to launch a VM I can see that the VMs appears in the xl list 
> output, but the State is -- and the Time(s) is 0.0.
> After ~30sec the start is aborted with error message: Cannot execute 
> qrexec-daemon.
> 
> Questions:
> 1) is anyone running Qubes 4.0-rc2 on a Lenovo X230?
> 2) is someone additionaly running Coreboot?
> 3) I am running the Qubes Installation with the default settings, any options 
> to tweak on the Grub command line
> 
> [799]
> 
> 
> 
> 
> 
> Gesendet von ProtonMail mobile

I'm testing Qubes 4.0rc2 on an X230 with SeaBIOS+Coreboot.

I can start sys-net always but cannot start sys-firewall and other VMs 
consistently ("Cannot execute qrexec-daemon").

One difference between our setups may be, I am not using the stock Intel wifi 
card but an Atheros one instead.

-- 
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/e83d6b06-1ea7-4343-aef2-c1f7cc2bf8ae%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Re: Qubes 4.0-rc2 :: VMs fail to start

[mouerto]

i think you are not alone having this problem why not post the problem here 
https://github.com/QubesOS/qubes-issues/issues?utf8=%E2%9C%93=is%3Aopen%20no%3Amilestone%20

-- 
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/11744811-f498-4758-9e00-ca15ac4ce86f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Re: Qubes 4.0-rc2 :: VMs fail to start

[Sean Hunter]

On the move.  Sorry if I'm terse. 

On 26 Oct 2017, at 07:11, Sean Hunter  wrote:

> 
> One thing is that during the install it gave the attached message about ioMMU 
> so perhaps something related to that has changed?  I’m going to look at that 
> next.
> 
> It all worked on 4.0 rc 1 for whatever that’s worth.

It does indeed seem like the version of coreboot I’m running doesn’t support 
VT-d so isn’t compatible with 4.0 rc 2.  This is annoying as qubes 3.2 also 
doesn’t work (won’t install) so I think I’m stuck with downgrading to 4.0 rc 1 
(which worked fine) :(

https://forums.puri.sm/t/vt-d-not-enabled-in-bios-coreboot/1225

Sean

-- 
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/6FEBBC97-C6D1-43E9-B138-5014F583072E%40uncarved.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Re: Qubes 4.0-rc2 :: VMs fail to start

[derpytorp]

On Wednesday, October 25, 2017 at 1:26:51 PM UTC-4, [799] wrote:
> Hello,
> 
> As at least one other Qubes user has the same problem, that VMs won't start, 
> I'll add this as special topic.
> 
> I've made a clean install of Qubes 4-rc2 but ~70% of the time I can't boot 
> the VMs.
> This includes sys-net, sys-firewall, but also others.
> 
> I tried to check the logs but I don't get any valuable information.
> See screenshot.
> 
> I started the following command in dom0:
> 
> watch -n 1 xl list
> 
> When I try to launch a VM I can see that the VMs appears in the xl list 
> output, but the State is -- and the Time(s) is 0.0.
> After ~30sec the start is aborted with error message: Cannot execute 
> qrexec-daemon.
> 
> Questions:
> 1) is anyone running Qubes 4.0-rc2 on a Lenovo X230?
> 2) is someone additionaly running Coreboot?
> 3) I am running the Qubes Installation with the default settings, any options 
> to tweak on the Grub command line
> 
> [799]
> 
> 
> 
> 
> 
> Gesendet von ProtonMail mobile



I just tried extending the qrexec-daemon timeout by another 60 seconds and that 
worked for me.

For me, it was my vault that refused to run.

qvm-prefs -s vault qrexec_timeout 120

and that worked.

-- 
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/3d6eafc5-e19a-4c45-ac25-6f2c084a174a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Re: Qubes 4.0-rc2 :: VMs fail to start

[mouerta]

can you see if this can help : 
https://github.com/QubesOS/qubes-issues/issues/3133

-- 
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/e9da6e33-071b-4c54-bd0b-91dab78d6047%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

AW: [qubes-users] Re: Qubes 4.0-rc2 :: VMs fail to start

['[799]' via qubes-users]

>> I've made a clean install of Qubes 4-rc2
>> but ~70% of the time I can't boot the VMs

After 2h troubleshooting I deleted my whole setup and reinstalled, again 
running into problems when trying to create new VMs.
... Ahrk. I. Hate. Linux. (From time to time).

Seriously, I burned now ~2h trying to get Qubes 4 running. Can't be that hard 
for a user who is running Qubes for ~2y.

Question:
Can we get an information on which laptops/Modells Qubes 4-rc2 has been tested?
Currently I don't know if I just to dumb to get things up and running or if my 
hardware has a problem.
As I have already invested lots of time in Qubes 4 rc1 before abandoning it and 
go back to 3.2, I just don't want to burn any time in case that my hardware is 
a dead horse.

Having the information on which laptops Qubes 4 "should" run or even more where 
it is running (Dev Users?) would help.
The HCL https://www.qubes-os.org/hcl/ does not help me, as it has no 
information if 4.x is ok for the X230.

As mentioned before I am running Coreboot, should I go back to stock ROM?

[799]
I need to

. > > This includes sys-net, sys-firewall, but also . > > > > I tried to check 
the logs but I don't get any valuable information. > > See screenshot. > > > > 
I started the following command in dom0: > > > > watch -n 1 xl list > > > > 
When I try to launch a VM I can see that the VMs appears in the xl list output, 
but the State is -- and the Time(s) is 0.0. > > After ~30sec the start is 
aborted with error message: Cannot execute qrexec-daemon. > > > > Questions: > 
> 1) is anyone running Qubes 4.0-rc2 on a Lenovo X230? > > 2) is someone 
additionaly running Coreboot? > > 3) I am running the Qubes Installation with 
the default settings, any options to tweak on the Grub command line > > > > 
[799] > > > > > > > > > > > > Gesendet von ProtonMail mobile > Set pci strict 
reset on sys-net and sys-usb to false and try again. If that doesn't help set 
virt_mode to pv. If that helps it means your laptop does not meet minimum 
system requirements Same for me. It worked after a lot of restarting and 
changing settings. Sys-firewall started after I set initial ram higher. The 
others on debug mode with no network-vm set in settings. Not immediately 
though, try it, even change templates, and restart the templates a few times. I 
didn't get the qrexec logs from the qubes-applet and didn't bother to check 
further since it worked after several retries. -- 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/0326dd36-a12e-45f3-ad4e-ce89ad688772%40googlegroups.com.
 For more options, visit https://groups.google.com/d/optout.

-- 
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/-eRgdQDQFTTwNdHXLhB497Flh6HWeMHUfuTBAA87lVz-poaDrd2zQ03XH6EDMtIkEogtZwdx9nU07fLR3bmdjeM7oBjZui01iRGyQAZ7WCA%3D%40protonmail.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Re: Qubes 4.0-rc2 :: VMs fail to start

[mikihonzero]

On Wednesday, October 25, 2017 at 5:48:38 PM UTC, Yethal wrote:
> W dniu środa, 25 października 2017 19:26:51 UTC+2 użytkownik [799] napisał:
> > Hello,
> > 
> > As at least one other Qubes user has the same problem, that VMs won't 
> > start, I'll add this as special topic.
> > 
> > I've made a clean install of Qubes 4-rc2 but ~70% of the time I can't boot 
> > the VMs.
> > This includes sys-net, sys-firewall, but also others.
> > 
> > I tried to check the logs but I don't get any valuable information.
> > See screenshot.
> > 
> > I started the following command in dom0:
> > 
> > watch -n 1 xl list
> > 
> > When I try to launch a VM I can see that the VMs appears in the xl list 
> > output, but the State is -- and the Time(s) is 0.0.
> > After ~30sec the start is aborted with error message: Cannot execute 
> > qrexec-daemon.
> > 
> > Questions:
> > 1) is anyone running Qubes 4.0-rc2 on a Lenovo X230?
> > 2) is someone additionaly running Coreboot?
> > 3) I am running the Qubes Installation with the default settings, any 
> > options to tweak on the Grub command line
> > 
> > [799]
> > 
> > 
> > 
> > 
> > 
> > Gesendet von ProtonMail mobile
> Set pci strict reset on sys-net and sys-usb to false and try again. If that 
> doesn't help set virt_mode to pv. If that helps it means your laptop does not 
> meet minimum system requirements

Same for me. It worked after a lot of restarting and changing settings.
Sys-firewall started after I set initial ram higher. The others on debug mode 
with no network-vm set in settings. Not immediately though, try it, even change 
templates, and restart the templates a few times.
I didn't get the qrexec logs from the qubes-applet and didn't bother to check 
further since it worked after several retries.

-- 
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/0326dd36-a12e-45f3-ad4e-ce89ad688772%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

AW: [qubes-users] Re: Qubes 4.0-rc2 :: VMs fail to start

['[799]' via qubes-users]

Hello,

>> Set pci strict reset on sys-net and sys-usb to
>> false and try again. If that doesn't help set
>> virt_mode to pv

qvm-prefs -s sys-usb pci_strictreset false

Results in:

qvm-prefs: error: no such property: 'pci_strictreset'

Has the setting be changed in Qubes 4? Same question has been asked by me for 
the internal setting, which hides VM from the menu.

[799]

-- 
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/9xauEp9fAThnlIDOtfnH7OJUBjhrIT3yaFh_ICk5vN8BtRZP0rLLQ3SicgLoKw9O0gRYZw_e1ZJnxESd6cshQlynsclsTJqCVCRkRzz2Awk%3D%40protonmail.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Re: Qubes 4.0-rc2 :: VMs fail to start

[Yethal]

W dniu środa, 25 października 2017 19:26:51 UTC+2 użytkownik [799] napisał:
> Hello,
> 
> As at least one other Qubes user has the same problem, that VMs won't start, 
> I'll add this as special topic.
> 
> I've made a clean install of Qubes 4-rc2 but ~70% of the time I can't boot 
> the VMs.
> This includes sys-net, sys-firewall, but also others.
> 
> I tried to check the logs but I don't get any valuable information.
> See screenshot.
> 
> I started the following command in dom0:
> 
> watch -n 1 xl list
> 
> When I try to launch a VM I can see that the VMs appears in the xl list 
> output, but the State is -- and the Time(s) is 0.0.
> After ~30sec the start is aborted with error message: Cannot execute 
> qrexec-daemon.
> 
> Questions:
> 1) is anyone running Qubes 4.0-rc2 on a Lenovo X230?
> 2) is someone additionaly running Coreboot?
> 3) I am running the Qubes Installation with the default settings, any options 
> to tweak on the Grub command line
> 
> [799]
> 
> 
> 
> 
> 
> Gesendet von ProtonMail mobile
Set pci strict reset on sys-net and sys-usb to false and try again. If that 
doesn't help set virt_mode to pv. If that helps it means your laptop does not 
meet minimum system requirements

-- 
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/fd020f3a-7eae-4c5f-84e4-b2f0055d41d0%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.