[qubes-users] Help: Restoring from ?auto? backups.

2017-11-02 Thread theo1jaklitsch
I need help to help myself.

The story thus far:
I was in the middle of a >qubes-dom0-update when my computer lost power. (Or, 
rather, got tired of me forgetting to plug it in.)  I plug it back in and press 
the power button while knocking on wood with crossed fingers. Get through disk 
encryption (that was almost certainly going to be fine). Black screen with 
blinking cursor for ~60sec. Something about kernals and bad things happening 
pops up (can't start kernal or something). Try to read through and understand 
what is happening then all of a sudden I'm on the DM's (lightDM?) login screen. 
I type in my password and I get similar screen as before the DM, then dumped to 
login. Try a few more times: same story. 

Shortcut to tty2; login from there. Flail about for a bit, then I think, "Just 
maybe Marek and Johanna made it auto backup. (And every one else. Hey, I know 
it's a community effort.)" Find out the name format of the backup files and 
rack my brain for all that I know about bash. Figure out how I can search with 
list and grep. Find the files and try to restore. 

Errors... Errors everywhere.

Look for other instances of people in my woeful plight.  Find this: 
https://groups.google.com/d/topic/qubes-users/BqfCKvWJrBE/discussion topic. Try 
the fix. That's a nope. Look elsewhere for file. Still nope.

That's where I got to.

If you would like more info or, simply, prefer to read the above story in 
painstakingly transcribed (on a phone no less) bash, see below:


[user@dom0 ~]$ sudo find / | grep 'qubes-2017*’ | uniq
/var/lib/qubes/backup/qubes-2017-11-02-18:20:01.xml
/var/lib/qubes/backup/qubes-2017-11-01-19:40:10.xml

[user@dom0 ~]$ qvm-backup-restore --debug 
/var/llb/qubes/backup/qubes-2017-11-02-18\:28\:01.xml
Please enter the passphrase to verify and (if encrypted) decrypt the backup:
Checking backup content...
Working in temporary dir:/var/tmp/restore_RiqPRi
Extracting data: 1.0 MiB to restore
Run command[u'tar', u'-ixvf", 
'var/lib/qubes/backup/qubes-2017-11-02-18:28:01.xml', u'-C’,   ##cont next 
line##
u'/var/tmp/restore_RiqPRi, u'backup-header’, u’backup-header.hmac’, 
u’qubes.xml.000’, u’qubes.xml.000.hmac’]
Got backup header and hmac: ,
ERROR: Premature end of archive while receiving backup header. Process output:
tar: This does not look like a tar archive
tar: Skipping to next header
tar: backup-header: Not found in archive
tar: backup-header.hmac: Not found in archive
tar: qubes.xml.000: Not found In archive
tar: qubes.xml.000.hmac: Not found in archive
tar: Exiting with failure status due to previous errors


[user@dom0 ~]$ ls -a /etc/qubes-rpc/
. policyqubes.InputKeyboardqubes.NotifyTools  
qubes.ReceiveUpdatesqubes.WindowlconUpdater
..qubes.GetRandomizedTime   qubes.InputMousequbes.NotifyUpdates
qubes.SyncAppMenus

[user@dom0 ~]$ sudo find / | grep "qubes.Restore' || echo "Couldn't find 
anything…”
Couldn't find anything...


I've been a Linux user for about 2 months and I made the jump to Qubes earlier 
this week. And I had barely grazed command line interfaces before that so I'm 
quite proud that I've made it this far without any walkthroughs but I need some 
real deal help now.

Could I just reinstall? Probably. But I want to learn and that isn't going to 
teach me anything.

Pls.
Pls.
Pls.
Pls.
Pls hlp.
I would be ever so grateful.


Steps to reproduce:
Screwup as hard as 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/5be8c335-4073-42b5-b498-e4585e851367%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] Libre motherboard info

2017-11-02 Thread taii...@gmx.com

Sorry I meant to send this to him, copied the list email by mistake.

--
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/6fdccd37-3b4b-6aed-4384-2409b62aaa46%40gmx.com.
For more options, visit https://groups.google.com/d/optout.


Re: AW: [qubes-users] Mainboard buying advice :: Should we still avoid mainboards with Intel vPro ??

2017-11-02 Thread taii...@gmx.com

On 11/02/2017 09:42 PM, '[799]' via qubes-users wrote:

(This one has also the link to the Qubes article addressing the vpro/Intel AMT 
topic)

Additionaly:
https://puri.sm/learn/avoiding-intel-amt/


https://www.reddit.com/r/linux/comments/3anjgm/on_the_librem_laptop_purism_doesnt_believe_in/

Purism isn't worth the money for what you get, their laptops aren't and 
will never be owner controlled - their marketing is quite dishonest as well.


They also fail to mention that they didn't make ME cleaner, and that it 
nerfs ME but doesn't disable it (Don't include any ME binaries and their 
laptops WILL turn off after 30 minutes, physically disconnect the ME 
processor to avoid a hostile mask ROM and their laptops won't even boot)



If vpro/Intel AMT is bothering you, I suggest running Coreboot (you might want 
to check which hardware is compatible:
https://www.coreboot.org/Supported_Motherboards)

Coreboot doesn't do anything about ME/PSP.

If you pick an intel coreboot supporting board that has a 100% open 
source init process (not the binary FSP blob like purism) it offers 
improved security and performance vs the proprietary bios, moving the 
firmware trust layer to you instead of OEM+vendor (default) or OEM (purism)


There are also a few quality x86-64 coreboot boards and a laptop (the 
last free x86 boards FYI) that are owner controlled with an open source 
init and without ME/PSP, such as the KCMA-D8 (workstation) KGPE-D16 
(server) and Lenovo G505S (laptop)



From here the only choice for high performance owner controlled libre 
new hardware is POWER, such as the excellent TALOS 2 (a great price for 
server hardware in its performance class)


--
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/8f897332-597d-1861-5738-eb55220d6934%40gmx.com.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] Libre motherboard info

2017-11-02 Thread taii...@gmx.com

In case you don't notice my email :D

On 11/02/2017 09:32 PM, 'Marek Jenkins' via qubes-users wrote:


It seems that most new mainboards with Intel chipset have support for "Intel 
vPro" technology.

I read in another thread that this can cause issues and should be avoided. Is 
that still correct ?
The issue is Intel ME, a black box supervisor processor that is 
controlled by intel instead of you thus you don't really own your computer.
vPro is simply a software addon to it which runs on the ME processor, it 
enables additional remote management features.


ME is very dangerous for your freedom as it is the worlds greatest 
backdoor present in every computer (btw you should stop using gmail if 
you care about your freedom and not using your job in 20 years to a 
google made robot)

Is "Intel vPro" a real no-go or can Qubes still work with it?
Or can having vPro support even have positive effects ?
It is used in a minority of enterprises for remote admin, but it is full 
of security holes.
If ME/vPro was open source, owner controlled, physically removable and 
better secured then it would be very cool.



I would buy a KCMA-D8 with a 4386 cpu then install coreboot (on this 
board it is fully open source and blob free)

Features:
100% Libre firmware available!
Fully supports Qubes 4.0<
No ME/PSP
Dual socket - supports 8 core cpu's - 16 core cpus available on its 
bigger brother the KGPE-D16 (also libre)

128GB Max RAM
TPM addon (for AEM)
Multiple PCI-e slots (supports crossfire)
IOMMU, with IOMMU for Graphics (attach a gpu to a VM to play games in 
your VM)

Two USB controllers (you need to buy usb headers to use the second)
Supports ECC RAM
Supports OpenBMC, an owner controlled remote management firmware for the 
boards KVM processor (the KGPE-D16/KCMA-D8 OpenBMC port was a great 
example of a successful crowdfunding campaignwhich yours truly 
contributed to)
Can play the latest games at high settings in a VM with a 4386 CPU, 
equivalent to a FX-8310



The board is only $250 for a variety of independent sellers (not 
overpriced/evil newegg/amazon) and you can get a nice cpu for $100 
(4386) or a budget one for $30 (4280)


I offer free tech support for libre motherboard purchasers, I am skilled 
using coreboot and it runs on many of my computers - don't hesitate to 
ask me questions :D


--
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/fe878977-a6a1-36fa-a181-cdf0871b65f5%40gmx.com.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] Mainboard buying advice :: Should we still avoid mainboards with Intel vPro ??

2017-11-02 Thread taii...@gmx.com

On 11/02/2017 09:32 PM, 'Marek Jenkins' via qubes-users wrote:


It seems that most new mainboards with Intel chipset have support for "Intel 
vPro" technology.

I read in another thread that this can cause issues and should be avoided. Is 
that still correct ?
The issue is Intel ME, a black box supervisor processor that is 
controlled by intel instead of you thus you don't really own your computer.
vPro is simply a software addon to it which runs on the ME processor, it 
enables additional remote management features.


ME is very dangerous for your freedom as it is the worlds greatest 
backdoor present in every computer (btw you should stop using gmail if 
you care about your freedom and not using your job in 20 years to a 
google made robot)


Is "Intel vPro" a real no-go or can Qubes still work with it?
Or can having vPro support even have positive effects ?
It is used in a minority of enterprises for remote admin, but it is full 
of security holes.
If ME/vPro was open source, owner controlled, physically removable and 
better secured then it would be very cool.



I would buy a KCMA-D8 with a 4386 cpu then install coreboot (on this 
board it is fully open source and blob free)

Features:
100% Libre firmware available!
Fully supports Qubes 4.0<
No ME/PSP
Dual socket - supports 8 core cpu's - 16 core cpus available on its 
bigger brother the KGPE-D16 (also libre)

128GB Max RAM
TPM addon (for AEM)
Multiple PCI-e slots (supports crossfire)
IOMMU, with IOMMU for Graphics (attach a gpu to a VM to play games in 
your VM)

Two USB controllers (you need to buy usb headers to use the second)
Supports ECC RAM
Supports OpenBMC, an owner controlled remote management firmware for the 
boards KVM processor (the KGPE-D16/KCMA-D8 OpenBMC port was a great 
example of a successful crowdfunding campaignwhich yours truly 
contributed to)
Can play the latest games at high settings in a VM with a 4386 CPU, 
equivalent to a FX-8310



The board is only $250 for a variety of independent sellers (not 
overpriced/evil newegg/amazon) and you can get a nice cpu for $100 
(4386) or a budget one for $30 (4280)


I offer free tech support for libre motherboard purchasers, I am skilled 
using coreboot and it runs on a many of my computers - don't hesitate to 
ask me questions :D


--
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/d0afa94b-cd0c-a76b-8df0-f90332e79fab%40gmx.com.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] Re: [qubes-devel] Qubes R3.2 - Severe graphics issues/glitches ? (HCL Report included)

2017-11-02 Thread Jean-Philippe Ouellet
Moving discussion from qubes-devel to qubes-users:

On Thu, Nov 2, 2017 at 3:47 PM, 'Marek Jenkins' via qubes-devel
 wrote:
> On Thursday, November 2, 2017 at 7:03:12 PM UTC+1, Jean-Philippe Ouellet
> wrote:
>>
>> On Thu, Nov 2, 2017 at 1:13 PM, 'Marek Jenkins' via qubes-devel
>>  wrote:
>> > Dear users and devs,
>> >
>> > I really like Qubes and hope I can make it work.
>> >
>> > I have severe graphics glitches that happen at random intervals.
>> > If they happen I must reboot the system to fix them temporarily
>> > (potential
>> > data loss).
>> > Unfortunately, those issues make Qubes 3.2 unusable for me because I
>> > need
>> > reliability.
>> >
>> > Glitch #1: https://imgur.com/a/fkAjW
>> > Looks like a green screen to me. Happens mostly when the system was idle
>> > /
>> > stand-by and I get back to it.
>> >
>> > Glitch #2: https://www.youtube.com/watch?v=sIaOWpFsdTM
>> > Weird screen glitch - also green but with some kind of flickering.
>> > Appears
>> > randomly.
>> >
>> > HCL REPORT:
>> >
>> > (Also attached the files !)
>> >
>> > ---
>> > layout:
>> >   'hcl'
>> > type:
>> >   'desktop'
>> > hvm:
>> >   'yes'
>> > iommu:
>> >   'no'
>> > slat:
>> >   'yes'
>> > tpm:
>> >   'unknown'
>> > brand: |
>> >   Gigabyte Technology Co., Ltd.
>> > model: |
>> >   Z97X-UD5H
>> > bios: |
>> >   F9
>> > cpu: |
>> >   Intel(R) Core(TM) i7-4770K CPU @ 3.50GHz
>> > cpu-short: |
>> >   FIXME
>> > chipset: |
>> >   Intel Corporation 4th Gen Core Processor DRAM Controller [8086:0c00]
>> > (rev
>> > 06)
>> > chipset-short: |
>> >   FIXME
>> > gpu: |
>> >   Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated
>> > Graphics Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller])
>> > gpu-short: |
>> >   FIXME
>> > network: |
>> >   Intel Corporation Ethernet Connection I217-V
>> >   Qualcomm Atheros Killer E220x Gigabit Ethernet Controller (rev 10)
>> >   Qualcomm Atheros AR93xx Wireless Network Adapter (rev 01)
>> > memory: |
>> >   32550
>> > scsi: |
>> >   Samsung SSD 840  Rev: BB6Q
>> >   DT HyperX 3.0Rev: PMAP
>> >
>> > versions:
>> >
>> > - works:
>> > 'FIXME:yes|no|partial'
>> >   qubes: |
>> > R3.2
>> >   xen: |
>> > 4.6.1
>> >   kernel: |
>> > 4.4.14-11
>> >   remark: |
>> > FIXME
>> >   credit: |
>> > FIXAUTHOR
>> >   link: |
>> > FIXLINK
>>
>> Try updating your kernel in dom0. 4.4.14 is very old and hardware
>> support improves over time.
>>
>> Also, posts like this should probably go on qubes-users instead of
>> qubes-devel.
>>
>> Regards,
>> Jean-Philippe
>
>
>
> Hi Jean-Philippe,
>
> thanks for your advice.
>
> I have read the docs over here regarding kernel updates:
> https://www.qubes-os.org/doc/software-update-dom0/
>
> So should I simply run the following terminal commands in dom0 ?
>
> sudo qubes-dom0-update --enablerepo=qubes-dom0-unstable kernel
> kernel-qubes-vm
>
> Also, do I need to enable / specify a repo (e.g. unstable, current-testing,
> etc) or can I also use the command like this:
>
> sudo qubes-dom0-update kernel kernel-qubes-vm
>
> Thank you for your support !
>
> PS: I posted this also in qubes-devel, because I thought this issue is quite
> difficult for normal users to solve.
> Sorry about that, I have also posted my HCL Report in qubes-users and will
> update there if I find a fix !
>
> Best regards,
> Marek

just start with
$ sudo qubes-dom0-update
in dom0 and reboot

only if that doesn't work then try -testing or -unstable repos.

-- 
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/CABQWM_BTDOk6g3EUEKF%3DRNfMYnzHoBRQ%3D4xhD%3DpHxoQWdotupg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.


AW: [qubes-users] Mainboard buying advice :: Should we still avoid mainboards with Intel vPro ??

2017-11-02 Thread '[799]' via qubes-users
Hello,

> It seems that most new mainboards with Intel
> chipset have support for "Intel vPro"
> technology.

Have you looked here:
https://groups.google.com/forum/m/#!topic/qubes-users/8XrF_CpyEU0

> Is "Intel vPro" a real no-go or can Qubes still
> work with it?

Qubes will work with vpro. But with vpro it is possible to remotly administrate 
a PC.
This is something we are using for some of our customers and is helpful in an 
Enterprise environment but maybe not something you would like to have on your 
private machine.

Here some more details:
https://security.stackexchange.com/questions/128619/what-are-the-privacy-and-security-risks-associated-with-intels-management-engin

(This one has also the link to the Qubes article addressing the vpro/Intel AMT 
topic)

Additionaly:
https://puri.sm/learn/avoiding-intel-amt/

If vpro/Intel AMT is bothering you, I suggest running Coreboot (you might want 
to check which hardware is compatible:
https://www.coreboot.org/Supported_Motherboards)

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


[qubes-users] Mainboard buying advice :: Should we still avoid mainboards with Intel vPro ??

2017-11-02 Thread 'Marek Jenkins' via qubes-users
It seems that most new mainboards with Intel chipset have support for "Intel 
vPro" technology.

I read in another thread that this can cause issues and should be avoided. Is 
that still correct ?

Is "Intel vPro" a real no-go or can Qubes still work with it?
Or can having vPro support even have positive effects ?

Thanks for your advice.

Marek

-- 
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/92acf400-e541-4579-9856-bb9e5ba03c1e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] Re: Unable to Attach ISO to Windows HVM

2017-11-02 Thread Person
I retried the commands.

My Windows 10 HVM actually starts up, but it is stuck on the Windows screen 
with a buffering sign. Then, after a few seconds, it closes and a notification 
appears: “Oops! Something went wrong.”

-- 
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/5469adc4-3f33-4fb4-bc7a-146184116f88%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] Re: Unable to Attach ISO to Windows HVM

2017-11-02 Thread Person
I currently have Qubes 3.2. Some of the advanced boot settings on the HVM 
cannot be found, and I assume it’s because I have 3.4 instead of 4.0.

I’m also quite sure I typed in the ISO path correctly: 
/home/user/Downloads/path-to-iso. 

The problem is that I’m not to sure if backing
up and then installing the ISO will work.

-- 
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/4ab896a3-c522-4563-be7b-10ceafce4617%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] Re: HCL - Gigabyte Z97X_UD5H + Intel Core i7-4770K

2017-11-02 Thread 'Marek Jenkins' via qubes-users
Attached HCL Report

-- 
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/98311697-9147-42b9-8959-54c9649abfdd%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Qubes-HCL-Gigabyte_Technology_Co___Ltd_-Z97X_UD5H-20171101-194315.yml
Description: Binary data


Qubes-HCL-Gigabyte_Technology_Co___Ltd_-Z97X_UD5H-20171102-170224.cpio.gz
Description: Binary data


[qubes-users] HCL - Gigabyte Z97X_UD5H + Intel Core i7-4770K

2017-11-02 Thread 'Marek Jenkins' via qubes-users
Dear users and devs,

I really like Qubes R3.2 and hope I can make it work.

I have severe graphics glitches that happen at random intervals.
If they happen I must reboot the system to fix them temporarily (resulting in 
potential data loss).
Unfortunately, those issues make Qubes 3.2 unusable for me because I need 
reliability.

Glitch #1: https://imgur.com/a/fkAjW
Looks like a green screen to me. Happens mostly when the system was idle / 
stand-by and I get back to it.

Glitch #2: https://www.youtube.com/watch?v=sIaOWpFsdTM
Weird screen glitch - also green but with some kind of flickering. Appears 
randomly.

HCL REPORT:

(Also attached the files)

---
layout:
  'hcl'
type:
  'desktop'
hvm:
  'yes'
iommu:
  'no'
slat:
  'yes'
tpm:
  'unknown'
brand: |
  Gigabyte Technology Co., Ltd.
model: |
  Z97X-UD5H
bios: |
  F9
cpu: |
  Intel(R) Core(TM) i7-4770K CPU @ 3.50GHz
cpu-short: |
  FIXME
chipset: |
  Intel Corporation 4th Gen Core Processor DRAM Controller [8086:0c00] (rev 06)
chipset-short: |
  FIXME
gpu: |
  Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics 
Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller])
gpu-short: |
  FIXME
network: |
  Intel Corporation Ethernet Connection I217-V
  Qualcomm Atheros Killer E220x Gigabit Ethernet Controller (rev 10)
  Qualcomm Atheros AR93xx Wireless Network Adapter (rev 01)
memory: |
  32550
scsi: |
  Samsung SSD 840  Rev: BB6Q
  DT HyperX 3.0Rev: PMAP

versions:

- works:
'FIXME:yes|no|partial'
  qubes: |
R3.2
  xen: |
4.6.1
  kernel: |
4.4.14-11
  remark: |
FIXME
  credit: |
FIXAUTHOR
  link: |
FIXLINK

---

-- 
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/09037626-90bb-4aa5-9490-653865451de5%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] Re: I can't remove VM

2017-11-02 Thread Chris Laprise

On 11/02/17 12:41, Marek Marczykowski-Górecki wrote:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

On Thu, Nov 02, 2017 at 12:31:11PM -0400, Chris Laprise wrote:

On 11/02/17 12:15, Marek Marczykowski-Górecki wrote:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

On Thu, Nov 02, 2017 at 11:34:01AM -0400, Chris Laprise wrote:

On 11/02/17 11:28, yuraei...@gmail.com wrote:

On Thursday, November 2, 2017 at 3:11:03 PM UTC, 
bm-2ctrx1tl5lg8cfa...@bitmessage.ch wrote:

Hi, I restore my backup from Qubes OS R3.2 to Qubes OS 4.0 and after
successful restored I tried to delete one VM that was useless but I can't
and I don't know why.

In the picture,"9870361_11.jpg" at the very last line, "domain is in use: 
'disp-sys-net'". As long as there are other templates or AppVM's tied to this disp-sys-net 
AppVM, then you cannot delete it.

I don't know any easier method, but you can run this command
user@dom0: qvm-prefs fedora-25 default_dispvm
to print out in the terminal, which disvm is in use, or if any at all. Just 
replace fedora-25 for all your other templates/AppVM, and you'll eventually 
find all the VM's tied to your disp-sys-net VM. It should take a few minutes, 
depending on how many VM's you have to run through.

If you want to remove it altogether, then use
user@dom0: qvm-prefs fedora-25 default_dispvm False

or if you want to change it to another dispvm, then use
user@dom0: qvm-prefs fedora-25 default_dispvm disp-VM-of-choice

I'm having the same problem with 'disp-no-netvm' and 'disp-no-netvm1' after
restoring R3.2 backups. I've made sure no VMs use those... its easy to do
with 'qvm-ls' command.

Details (including what VM use it where) are logged in dom0 logs (see
journalctl). It is not included in the error message for privacy reasons
(the same message could be also obtained through Admin API from different
VM).

Journal says its used by 'personal.default_dispvm'. My personal vm dispvm
setting is 'default(none)'.

Is the same reported by qvm-prefs?



qvm-prefs is not the same... it shows the 'disp-no-netvm' vm name. I 
reset it with `qvm-prefs -D` on a few vms and was finally able to remove 
the extras.


--

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/20606622-19d3-6fa5-dc0d-9970ede60f54%40posteo.net.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] Re: I can't remove VM

2017-11-02 Thread Marek Marczykowski-Górecki
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

On Thu, Nov 02, 2017 at 12:31:11PM -0400, Chris Laprise wrote:
> On 11/02/17 12:15, Marek Marczykowski-Górecki wrote:
> > -BEGIN PGP SIGNED MESSAGE-
> > Hash: SHA256
> > 
> > On Thu, Nov 02, 2017 at 11:34:01AM -0400, Chris Laprise wrote:
> > > On 11/02/17 11:28, yuraei...@gmail.com wrote:
> > > > On Thursday, November 2, 2017 at 3:11:03 PM UTC, 
> > > > bm-2ctrx1tl5lg8cfa...@bitmessage.ch wrote:
> > > > > Hi, I restore my backup from Qubes OS R3.2 to Qubes OS 4.0 and after
> > > > > successful restored I tried to delete one VM that was useless but I 
> > > > > can't
> > > > > and I don't know why.
> > > > In the picture,"9870361_11.jpg" at the very last line, "domain is in 
> > > > use: 'disp-sys-net'". As long as there are other templates or AppVM's 
> > > > tied to this disp-sys-net AppVM, then you cannot delete it.
> > > > 
> > > > I don't know any easier method, but you can run this command
> > > > user@dom0: qvm-prefs fedora-25 default_dispvm
> > > > to print out in the terminal, which disvm is in use, or if any at all. 
> > > > Just replace fedora-25 for all your other templates/AppVM, and you'll 
> > > > eventually find all the VM's tied to your disp-sys-net VM. It should 
> > > > take a few minutes, depending on how many VM's you have to run through.
> > > > 
> > > > If you want to remove it altogether, then use
> > > > user@dom0: qvm-prefs fedora-25 default_dispvm False
> > > > 
> > > > or if you want to change it to another dispvm, then use
> > > > user@dom0: qvm-prefs fedora-25 default_dispvm disp-VM-of-choice
> > > I'm having the same problem with 'disp-no-netvm' and 'disp-no-netvm1' 
> > > after
> > > restoring R3.2 backups. I've made sure no VMs use those... its easy to do
> > > with 'qvm-ls' command.
> > Details (including what VM use it where) are logged in dom0 logs (see
> > journalctl). It is not included in the error message for privacy reasons
> > (the same message could be also obtained through Admin API from different
> > VM).
> 
> Journal says its used by 'personal.default_dispvm'. My personal vm dispvm
> setting is 'default(none)'.

Is the same reported by qvm-prefs?

- -- 
Best Regards,
Marek Marczykowski-Górecki
Invisible Things Lab
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQEcBAEBCAAGBQJZ+F5mAAoJENuP0xzK19csPhAH/3jwmtUutNtvZjb/ceRlBU6c
A1UvE7km3kvRiwwZQzJDGJ/3QwEUNUQX97psXtAgiALcl1YVa3czNZJmipo4EdkG
vhUfAWOMBqSo7k6TLRb2qe747who5kl0UlbqyrsCk1Y5tKBXJ5c9A9sS19GYcDnw
VIAMrI19/qvsagejiHtwXLlHy9ak0WiXaN9Hg/eYLsBRRMjfJSyE3JQx341TV2oS
qHcdp1m2sJmb1v4KoDxA0qT3xQ0bvbPb8SQHJMFLya//Ks2ueHbcYkXNEH4/vlvf
g8xJ+WozWCRVqJGGMI4Y/pqjhucuM+VSfnzAzKticAsdq+BHmgaUSga6D23eYmo=
=s+hq
-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/20171102164114.GC15871%40mail-itl.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] Re: I can't remove VM

2017-11-02 Thread Chris Laprise

On 11/02/17 12:15, Marek Marczykowski-Górecki wrote:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

On Thu, Nov 02, 2017 at 11:34:01AM -0400, Chris Laprise wrote:

On 11/02/17 11:28, yuraei...@gmail.com wrote:

On Thursday, November 2, 2017 at 3:11:03 PM UTC, 
bm-2ctrx1tl5lg8cfa...@bitmessage.ch wrote:

Hi, I restore my backup from Qubes OS R3.2 to Qubes OS 4.0 and after
successful restored I tried to delete one VM that was useless but I can't
and I don't know why.

In the picture,"9870361_11.jpg" at the very last line, "domain is in use: 
'disp-sys-net'". As long as there are other templates or AppVM's tied to this disp-sys-net 
AppVM, then you cannot delete it.

I don't know any easier method, but you can run this command
user@dom0: qvm-prefs fedora-25 default_dispvm
to print out in the terminal, which disvm is in use, or if any at all. Just 
replace fedora-25 for all your other templates/AppVM, and you'll eventually 
find all the VM's tied to your disp-sys-net VM. It should take a few minutes, 
depending on how many VM's you have to run through.

If you want to remove it altogether, then use
user@dom0: qvm-prefs fedora-25 default_dispvm False

or if you want to change it to another dispvm, then use
user@dom0: qvm-prefs fedora-25 default_dispvm disp-VM-of-choice

I'm having the same problem with 'disp-no-netvm' and 'disp-no-netvm1' after
restoring R3.2 backups. I've made sure no VMs use those... its easy to do
with 'qvm-ls' command.

Details (including what VM use it where) are logged in dom0 logs (see
journalctl). It is not included in the error message for privacy reasons
(the same message could be also obtained through Admin API from different
VM).


Journal says its used by 'personal.default_dispvm'. My personal vm 
dispvm setting is 'default(none)'.


--

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/8d94d825-9173-55e8-0747-8330c8b167b8%40posteo.net.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] Re: I can't remove VM

2017-11-02 Thread Chris Laprise

On 11/02/17 11:56, yuraei...@gmail.com wrote:

On Thursday, November 2, 2017 at 3:34:21 PM UTC, Chris Laprise wrote:

On 11/02/17 11:28, yuraei...@gmail.com wrote:

On Thursday, November 2, 2017 at 3:11:03 PM UTC, 
bm-2ctrx1tl5lg8cfa...@bitmessage.ch wrote:

Hi, I restore my backup from Qubes OS R3.2 to Qubes OS 4.0 and after
successful restored I tried to delete one VM that was useless but I can't
and I don't know why.

In the picture,"9870361_11.jpg" at the very last line, "domain is in use: 
'disp-sys-net'". As long as there are other templates or AppVM's tied to this disp-sys-net 
AppVM, then you cannot delete it.

I don't know any easier method, but you can run this command
user@dom0: qvm-prefs fedora-25 default_dispvm
to print out in the terminal, which disvm is in use, or if any at all. Just 
replace fedora-25 for all your other templates/AppVM, and you'll eventually 
find all the VM's tied to your disp-sys-net VM. It should take a few minutes, 
depending on how many VM's you have to run through.

If you want to remove it altogether, then use
user@dom0: qvm-prefs fedora-25 default_dispvm False

or if you want to change it to another dispvm, then use
user@dom0: qvm-prefs fedora-25 default_dispvm disp-VM-of-choice

I'm having the same problem with 'disp-no-netvm' and 'disp-no-netvm1'
after restoring R3.2 backups. I've made sure no VMs use those... its
easy to do with 'qvm-ls' command.

--

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

Are you sure your qvm-ls command shows the disposible VM's on each VM? Mine only shows "State", "Class", 
"Label", "Template", and "NetVM". It doesn't show any Disp_VM.
Maybe you can't remove it because it doesn't show the disp_vm's?

or is there an option in the qvm-ls that I missed out on that prints disp_vm's 
too? I can't detect any useful ones with 'qvm-ls -h' or 'qvm-ls --help-formats' 
though I may have missed it.

I've tried them all, can't find any disp_vm information.
qvm-ls --format disk
qvm-ls --format full
qvm-ls --format network
qvm-ls --format simple


qvm-ls shows the network, but I went into each VM settings to see what 
the dispVM setting was and they're all 'none'.


Chris

--

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/1f3e937a-a9e7-2a01-d51e-3eb0bd37%40posteo.net.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] Re: I can't remove VM

2017-11-02 Thread Marek Marczykowski-Górecki
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

On Thu, Nov 02, 2017 at 11:34:01AM -0400, Chris Laprise wrote:
> On 11/02/17 11:28, yuraei...@gmail.com wrote:
> > On Thursday, November 2, 2017 at 3:11:03 PM UTC, 
> > bm-2ctrx1tl5lg8cfa...@bitmessage.ch wrote:
> > > Hi, I restore my backup from Qubes OS R3.2 to Qubes OS 4.0 and after
> > > successful restored I tried to delete one VM that was useless but I can't
> > > and I don't know why.
> > In the picture,"9870361_11.jpg" at the very last line, "domain is in use: 
> > 'disp-sys-net'". As long as there are other templates or AppVM's tied to 
> > this disp-sys-net AppVM, then you cannot delete it.
> > 
> > I don't know any easier method, but you can run this command
> > user@dom0: qvm-prefs fedora-25 default_dispvm
> > to print out in the terminal, which disvm is in use, or if any at all. Just 
> > replace fedora-25 for all your other templates/AppVM, and you'll eventually 
> > find all the VM's tied to your disp-sys-net VM. It should take a few 
> > minutes, depending on how many VM's you have to run through.
> > 
> > If you want to remove it altogether, then use
> > user@dom0: qvm-prefs fedora-25 default_dispvm False
> > 
> > or if you want to change it to another dispvm, then use
> > user@dom0: qvm-prefs fedora-25 default_dispvm disp-VM-of-choice
> 
> I'm having the same problem with 'disp-no-netvm' and 'disp-no-netvm1' after
> restoring R3.2 backups. I've made sure no VMs use those... its easy to do
> with 'qvm-ls' command.

Details (including what VM use it where) are logged in dom0 logs (see
journalctl). It is not included in the error message for privacy reasons
(the same message could be also obtained through Admin API from different
VM).

- -- 
Best Regards,
Marek Marczykowski-Górecki
Invisible Things Lab
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQEcBAEBCAAGBQJZ+FhmAAoJENuP0xzK19cs96QH/Rr9TH5RBpec2rkR3urcJhN8
PTCIXsbZCfd3VMLjCYK7ntS19UqAqXJ9ZDZEEe3Pbi1uKHTEWLCx9Zy1lfMi3DIb
FMFoiE5ql0Al/PKlPo8dQ1CntdR2JNq7OJ8d8zY60YP6iqxWA9nv3p+olGAWalyQ
AlIkan9pQfFMgUZ9Qd1rRz9jLzMUmewvoW8Yzl3PmZelKy6AFYU19URahQZirFlK
3Q9nWkJz254IjmhuEMbphXxFcnzsRfbrwHlXglYZmJMS1JVmnmLmrf1NMAi9lvbo
sNpu31SEf4YkNMlHxZkctkRNCVQ1keg5teUDBIM66EevuHYKkhbbUspweVutAAI=
=S/RC
-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/20171102161539.GC4535%40mail-itl.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] Re: bug: qubes vm-manager qubes 3.2 current: Unable to rename VM to "ReactOS-Reference"

2017-11-02 Thread ludwig jaffe
On Thursday, November 2, 2017 at 11:52:29 AM UTC-4, ludwig jaffe wrote:
> bug: qubes vm-manager qubes 3.2 current: Unable to rename VM to 
> "ReactOS-Reference"
> 
> Problem:
> I installed reactos into a new standalone template vm and thought I could 
> derive user vms as in linux based. But this did not work, maybe I dont know 
> howto do.
> So as a work-around I wanted to make a reference reactos and clone it for 
> different tasks.
> So renaming it to "ReactOS-Reference" failed!
> The /var/lib/qubes/vm-templates/ReactOS-Reference folder
> got renamed properly but the Qube VM Manager did not find the VM 
> and threw an error.
> "Errno 2 No such file or directory"
> "
> fill_apps_list line no.:71
> ...appmenu_select.py"
> and some more.
> 
> 
> To get it running again one had to rename the directory 
> var/lib/qubes/vm-templates/ReactOS-Reference to the original name displayed 
> in Qubes VM Manager.
> 
> So the directory listing should be enhanced to parse more complicated 
> directory names, or renaming should be masked in order not to allow "illegal" 
> directory names.
> 
> Cheers,
> 
> Ludwig

too quick: rename did not help, as there are uuids which are double and some
xml based config files.
So make a new vm and copy over the images as editing xml with vim is a pain.

-- 
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/06301bb5-7bd9-4eab-b360-a45aa48f30fd%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] Re: I can't remove VM

2017-11-02 Thread yuraeitha
On Thursday, November 2, 2017 at 3:34:21 PM UTC, Chris Laprise wrote:
> On 11/02/17 11:28, yuraei...@gmail.com wrote:
> > On Thursday, November 2, 2017 at 3:11:03 PM UTC, 
> > bm-2ctrx1tl5lg8cfa...@bitmessage.ch wrote:
> >> Hi, I restore my backup from Qubes OS R3.2 to Qubes OS 4.0 and after
> >> successful restored I tried to delete one VM that was useless but I can't
> >> and I don't know why.
> > In the picture,"9870361_11.jpg" at the very last line, "domain is in use: 
> > 'disp-sys-net'". As long as there are other templates or AppVM's tied to 
> > this disp-sys-net AppVM, then you cannot delete it.
> >
> > I don't know any easier method, but you can run this command
> > user@dom0: qvm-prefs fedora-25 default_dispvm
> > to print out in the terminal, which disvm is in use, or if any at all. Just 
> > replace fedora-25 for all your other templates/AppVM, and you'll eventually 
> > find all the VM's tied to your disp-sys-net VM. It should take a few 
> > minutes, depending on how many VM's you have to run through.
> >
> > If you want to remove it altogether, then use
> > user@dom0: qvm-prefs fedora-25 default_dispvm False
> >
> > or if you want to change it to another dispvm, then use
> > user@dom0: qvm-prefs fedora-25 default_dispvm disp-VM-of-choice
> 
> I'm having the same problem with 'disp-no-netvm' and 'disp-no-netvm1' 
> after restoring R3.2 backups. I've made sure no VMs use those... its 
> easy to do with 'qvm-ls' command.
> 
> -- 
> 
> Chris Laprise, tas...@posteo.net
> https://github.com/tasket
> https://twitter.com/ttaskett
> PGP: BEE2 20C5 356E 764A 73EB  4AB3 1DC4 D106 F07F 1886

Are you sure your qvm-ls command shows the disposible VM's on each VM? Mine 
only shows "State", "Class", "Label", "Template", and "NetVM". It doesn't show 
any Disp_VM. 
Maybe you can't remove it because it doesn't show the disp_vm's? 

or is there an option in the qvm-ls that I missed out on that prints disp_vm's 
too? I can't detect any useful ones with 'qvm-ls -h' or 'qvm-ls --help-formats' 
though I may have missed it.

I've tried them all, can't find any disp_vm information.
qvm-ls --format disk
qvm-ls --format full
qvm-ls --format network
qvm-ls --format simple

-- 
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/c5c18a71-181e-4a69-9180-c95b9f3c1780%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] bug: qubes vm-manager qubes 3.2 current: Unable to rename VM to "ReactOS-Reference"

2017-11-02 Thread ludwig jaffe
bug: qubes vm-manager qubes 3.2 current: Unable to rename VM to 
"ReactOS-Reference"

Problem:
I installed reactos into a new standalone template vm and thought I could 
derive user vms as in linux based. But this did not work, maybe I dont know 
howto do.
So as a work-around I wanted to make a reference reactos and clone it for 
different tasks.
So renaming it to "ReactOS-Reference" failed!
The /var/lib/qubes/vm-templates/ReactOS-Reference folder
got renamed properly but the Qube VM Manager did not find the VM 
and threw an error.
"Errno 2 No such file or directory"
"
fill_apps_list line no.:71
...appmenu_select.py"
and some more.


To get it running again one had to rename the directory 
var/lib/qubes/vm-templates/ReactOS-Reference to the original name displayed in 
Qubes VM Manager.

So the directory listing should be enhanced to parse more complicated directory 
names, or renaming should be masked in order not to allow "illegal" directory 
names.

Cheers,

Ludwig

-- 
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/f3d25028-5403-43cf-9001-3816b8e6f7ad%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] Re: Debian 9 running on R4rc2 (was: How to qvm-attach...)

2017-11-02 Thread Marek Marczykowski-Górecki
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

On Thu, Nov 02, 2017 at 05:33:42AM -0400, Chris Laprise wrote:
> On 11/02/17 03:33, Marek Marczykowski-Górecki wrote:
> > -BEGIN PGP SIGNED MESSAGE-
> > Hash: SHA256
> > 
> > On Wed, Nov 01, 2017 at 10:39:36PM -0400, Chris Laprise wrote:
> > > I'm trying to repair a debian-9 root volume by first attaching it to an
> > > appVM, but the new syntax doesn't seem to allow it. I tried the following 
> > > so
> > > far:
> > > 
> > > qvm-block attach tempvm lvm:qubes_dom0/vm-debian-9-root
> > > qvm-block attach tempvm dom0:qubes_dom0/vm-debian-9-root
> > > qvm-block attach tempvm dom0:/dev/mapper/qubes_dom0-vm--debian--9--root
> > qvm-block generally allow to attach only devices listed by it (qvm-block
> > ls). VM volumes are specifically excluded there.
> > 
> > I'd propose alternative approach for fixing debian-9: enable debug mode,
> > boot it, login (you'll have VGA console), then remove
> > xserver-xorg-legacy package. It should fix the GUI there.
> 
> Already had it in debug mode; Just discovered you have to wait several
> minutes for the console. But I removed xserver-xorg-legacy and its still not
> right. After waiting a minute I can get xterm to run but Gnome stuff
> (gnome-terminal) is broken:
> 
> > Error constructing proxy for
> org.gnome.Terminal:/org/gnome/Terminal/Factory0: Failed to execute child
> process "dbus-launch" (No such file or directory)

Oh, indeed. You need to install dbus-x11 package for that (dbus-launch
is missing).
I hope to upload fixed template this week, if time allows...

> FWIW, I did an upgrade of a debian-8 template and that seems good so far.

- -- 
Best Regards,
Marek Marczykowski-Górecki
Invisible Things Lab
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQEcBAEBCAAGBQJZ+FGRAAoJENuP0xzK19csp0YIAI9L3b82oE8IrW0S3tU8zk8x
+Ap+8praevtYNyRfjNuUO/45x6UmNz8nXH/V03V5bhvqJmpKhiGsKffFQcjVlOOS
Fz4xO9vPKEmjEu8z30tN3K1bi0sN/dYWzm2uqGMfmsj9x/K8elKUiiJ6tihppd3g
5ylA1opOGUqbxcv2hv/UOOvaJjnyYSSNr5eebjo4VI+EX+T31YmWunhrE0EdBdQs
W4IfGsUAT5PH7KLuKyAR/GVEIpxKl4mKYGVFWhpFjIauDMFI4HTFhppeZisEN+pP
DR2GxB5dx3i89PIu90cwI/Cr07qPrSyNHk+/bMXFQqgQ8BfwY396kblwRO21JaE=
=kcx4
-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/20171102154626.GQ1045%40mail-itl.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] Re: I can't update menu in VM

2017-11-02 Thread yuraeitha
On Thursday, November 2, 2017 at 3:10:55 PM UTC, 
bm-2ctrx1tl5lg8cfa...@bitmessage.ch wrote:
> Hi, I restored my backup from Qubes OS R3.2 to Qubes OS R4.0 and after
> this I tried to run one of VM to do update but when I click in menu on
> this position I see only "start" I haven't any terminal in menu and I
> wanted scan VM to update menu list but VM don't start and don't update
> menu.

When you use it with the terminal, qvm-sync-appmenus, like you did in the 
picture, then you'll need to have the TemplateVM started beforehand. It won't 
start on its own. Once its fully booted, then run the dom0 command again. 

There is also a graphical method, there should be a VM Settings, next to the 
"Start" in the menu's that you mentioned. If you can find the VM Settings, then 
you can go to the Applications tab, and then click on the "Refresh 
Applications" button at the top of the window. This will automatically start 
the Template the AppVM is based on, execute the sync commands, and then 
automatically shut down again. You'll have to wait till its done and closed 
itself before trying to manage any of its menu or shortcuts.

I'm sure you know, but just in case, remember to restart any AppVM's that is 
based on the template.

-- 
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/9f541e59-4984-48f9-b39d-ff2c573e70bc%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] Re: I can't remove VM

2017-11-02 Thread Chris Laprise

On 11/02/17 11:28, yuraei...@gmail.com wrote:

On Thursday, November 2, 2017 at 3:11:03 PM UTC, 
bm-2ctrx1tl5lg8cfa...@bitmessage.ch wrote:

Hi, I restore my backup from Qubes OS R3.2 to Qubes OS 4.0 and after
successful restored I tried to delete one VM that was useless but I can't
and I don't know why.

In the picture,"9870361_11.jpg" at the very last line, "domain is in use: 
'disp-sys-net'". As long as there are other templates or AppVM's tied to this disp-sys-net 
AppVM, then you cannot delete it.

I don't know any easier method, but you can run this command
user@dom0: qvm-prefs fedora-25 default_dispvm
to print out in the terminal, which disvm is in use, or if any at all. Just 
replace fedora-25 for all your other templates/AppVM, and you'll eventually 
find all the VM's tied to your disp-sys-net VM. It should take a few minutes, 
depending on how many VM's you have to run through.

If you want to remove it altogether, then use
user@dom0: qvm-prefs fedora-25 default_dispvm False

or if you want to change it to another dispvm, then use
user@dom0: qvm-prefs fedora-25 default_dispvm disp-VM-of-choice


I'm having the same problem with 'disp-no-netvm' and 'disp-no-netvm1' 
after restoring R3.2 backups. I've made sure no VMs use those... its 
easy to do with 'qvm-ls' command.


--

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/250f5146-70ff-6eea-fe6a-782eeef47fa4%40posteo.net.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] Re: I can't remove VM

2017-11-02 Thread yuraeitha
On Thursday, November 2, 2017 at 3:11:03 PM UTC, 
bm-2ctrx1tl5lg8cfa...@bitmessage.ch wrote:
> Hi, I restore my backup from Qubes OS R3.2 to Qubes OS 4.0 and after
> successful restored I tried to delete one VM that was useless but I can't
> and I don't know why.

In the picture,"9870361_11.jpg" at the very last line, "domain is in use: 
'disp-sys-net'". As long as there are other templates or AppVM's tied to this 
disp-sys-net AppVM, then you cannot delete it.

I don't know any easier method, but you can run this command
user@dom0: qvm-prefs fedora-25 default_dispvm
to print out in the terminal, which disvm is in use, or if any at all. Just 
replace fedora-25 for all your other templates/AppVM, and you'll eventually 
find all the VM's tied to your disp-sys-net VM. It should take a few minutes, 
depending on how many VM's you have to run through.

If you want to remove it altogether, then use
user@dom0: qvm-prefs fedora-25 default_dispvm False

or if you want to change it to another dispvm, then use
user@dom0: qvm-prefs fedora-25 default_dispvm disp-VM-of-choice

-- 
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/bcdb38c5-6ce9-4144-9150-f4f66f390867%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] Re: Unable to Attach ISO to Windows HVM

2017-11-02 Thread yuraeitha
On Wednesday, November 1, 2017 at 1:05:41 AM UTC, Person wrote:
> I created a Windows 10 HVM on Qubes (I know Windows 10 isn’t supported, but I 
> know some people succeeded with it, so I’m trying it), and when I attached 
> the ISO to the HVM, I get an error message: “libvirt.libvirtError: internal 
> error: libxenlight failed to create new domain ‘windows-10’”.
> 
> I don’t believe that there is anything wrong with the ISO, because it was a 
> download directly from Microsoft; and I don’t believe that I messed up the 
> command, because it worked previously. It booted up a picture of the Windows 
> logo and then suddenly crashed.
> 
> One of the solutions I found online was to use “systemctl start 
> xendriverdomain”, but I don’t seem to have this service and I don’t know how 
> to install it.

It did not work on my system either, It appears to be a python code issue that 
prevents Qubes from booting the iso files. 
I suppose the best solution would be to install Windows 10 from Qubes 3.2, then 
back it up to a Qubes-backup, and then restore Windows 10 in Qubes 10 from the 
backup. This has worked with Windows 7. Just be sure to give it enough RAM 
since it won't start easily without plenty of RAM, when without the 
qubes-windows-tools to dynamically sort out the RAM management. 


Thoughts on the details: It seems to be appearing within the Qubes tools, 
specifically the --cdrom= part, and its associated python code. I'm not a 
programmer, or an expert, but from what I can see, this won't work until the 
Qubes team fix the python error, from either a new python library or the python 
code someone from the Qubes team wrote, whichever it is. If the former, then 
we'll have to wait for other developers to fix it before anything happens, I 
suppose?

There were some python dom0 updates today, I tried to install Windows 10 both 
before and after updating, including restarting Qubes just to be 100% sure. 
None worked, same python error is still around. 

It appears that the graphical method runs into same python errors, but without 
logs I can't be sure. 

Also I've tried installed from both AppVM's and from Dom0. Given that backups 
are bugged/slow from dom0, apparently due to python also. So I thought it might 
make a difference here too, but sadly it did not.

For now, it seems the only solution is to install Windows 10 somewhere else, 
for example in Qubes 3.2, and then back it up and transfer it to Qubes 4. At 
least to my knowledge.

-- 
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/edfd79d2-2f07-41f9-afb3-723b77c73a23%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


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

2017-11-02 Thread 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.


Re: [qubes-users] Rc2 hangs on install -- Dell Inspiron i5759-8835SLV

2017-11-02 Thread Mike Keehan
On Wed, 1 Nov 2017 16:32:24 -0700 (PDT)
billol...@gmail.com wrote:

> Yeah, I'll do that.  On the other hand, it may be a Fedora thing.
> Just for giggles, I downloaded F26, and it won't install, either --
> it times out, though it gives a different error when it does.
> 
> I use these cheap flash drives I buy in bulk off ebay.  I'll go get a
> pricey one and see if it makes a difference.  But I gotta say, these
> same drives work fine for ubuntu and KDE neon.
> 

I've been having similar 'stuck' problems on my laptop.  And trying to
install Fedora 26 got stuck too.

I found that in my case it is the nouveau driver that gets stuck - the
driver can't handle the newest nvidia chips yet.

I managed to get Fedora to install by adding the option 
'modprobe.blacklist=nouveau' to the kernel boot command line (at the
Fedora install boot use 'e' to edit the command line).

However I haven't yet figured out how to do that for Qubes bootup.

Mike.

-- 
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/20171102115429.453879ff.mike%40keehan.net.
For more options, visit https://groups.google.com/d/optout.


Re: Re: [qubes-users] Rc2 hangs on install -- Dell Inspiron i5759-8835SLV

2017-11-02 Thread billollib
On Wednesday, November 1, 2017 at 7:43:42 PM UTC-4, [799] wrote:

> I've migrated my USB drives to only one Modell:
> SanDisk 
> https://www.amazon.com/gp/aw/d/B01NARBPI7/
> 
> It has a good performance (I have installed Qubes on of those to showcase it 
> to friends and colleques.
> 
> [799]

Just ordered it.  I'll see if it works.

-- 
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/3df009fc-d756-4174-beaa-ae20825574d3%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] Re: How to qvm-attach VM volume to another VM?

2017-11-02 Thread Chris Laprise

On 11/02/17 00:13, aphidfar...@gmail.com wrote:

On Wednesday, November 1, 2017 at 7:40:01 PM UTC-7, Chris Laprise wrote:

I'm trying to repair a debian-9 root volume by first attaching it to an
appVM, but the new syntax doesn't seem to allow it. I tried the
following so far:

qvm-block attach tempvm lvm:qubes_dom0/vm-debian-9-root
qvm-block attach tempvm dom0:qubes_dom0/vm-debian-9-root
qvm-block attach tempvm dom0:/dev/mapper/qubes_dom0-vm--debian--9--root


I'm also interested in a replacement for the old qvm-block -A functionality.

In the meantime I use losetup to get a block device for use with the new 
qvm-block, works for me but it's messier.



That's good to know because even with private volumes you occasionally 
need to attach one to an appVM for fixes/inspection without mounting it 
as /home.


--

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/effde288-6143-7de5-19f2-f90c584cd04a%40posteo.net.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] Debian 9 running on R4rc2 (was: How to qvm-attach...)

2017-11-02 Thread Chris Laprise

On 11/02/17 03:33, Marek Marczykowski-Górecki wrote:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

On Wed, Nov 01, 2017 at 10:39:36PM -0400, Chris Laprise wrote:

I'm trying to repair a debian-9 root volume by first attaching it to an
appVM, but the new syntax doesn't seem to allow it. I tried the following so
far:

qvm-block attach tempvm lvm:qubes_dom0/vm-debian-9-root
qvm-block attach tempvm dom0:qubes_dom0/vm-debian-9-root
qvm-block attach tempvm dom0:/dev/mapper/qubes_dom0-vm--debian--9--root

qvm-block generally allow to attach only devices listed by it (qvm-block
ls). VM volumes are specifically excluded there.

I'd propose alternative approach for fixing debian-9: enable debug mode,
boot it, login (you'll have VGA console), then remove
xserver-xorg-legacy package. It should fix the GUI there.


Already had it in debug mode; Just discovered you have to wait several 
minutes for the console. But I removed xserver-xorg-legacy and its still 
not right. After waiting a minute I can get xterm to run but Gnome stuff 
(gnome-terminal) is broken:


> Error constructing proxy for 
org.gnome.Terminal:/org/gnome/Terminal/Factory0: Failed to execute child 
process "dbus-launch" (No such file or directory)


FWIW, I did an upgrade of a debian-8 template and that seems good so far.

--

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/8e9f6d62-328c-4900-bd72-12819d2a9fe7%40posteo.net.
For more options, visit https://groups.google.com/d/optout.


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

2017-11-02 Thread '[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

2017-11-02 Thread 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.


[qubes-users] Re: How to qvm-attach VM volume to another VM?

2017-11-02 Thread Marek Marczykowski-Górecki
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

On Wed, Nov 01, 2017 at 10:39:36PM -0400, Chris Laprise wrote:
> I'm trying to repair a debian-9 root volume by first attaching it to an
> appVM, but the new syntax doesn't seem to allow it. I tried the following so
> far:
> 
> qvm-block attach tempvm lvm:qubes_dom0/vm-debian-9-root
> qvm-block attach tempvm dom0:qubes_dom0/vm-debian-9-root
> qvm-block attach tempvm dom0:/dev/mapper/qubes_dom0-vm--debian--9--root

qvm-block generally allow to attach only devices listed by it (qvm-block
ls). VM volumes are specifically excluded there.

I'd propose alternative approach for fixing debian-9: enable debug mode,
boot it, login (you'll have VGA console), then remove
xserver-xorg-legacy package. It should fix the GUI there.

- -- 
Best Regards,
Marek Marczykowski-Górecki
Invisible Things Lab
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQEcBAEBCAAGBQJZ+EvfAAoJENuP0xzK19csHYQH/1lUUQley2Fxd30dgscyX21q
HfnHd6w7wfsAi1+LD1gpHN2ykHaI38c4/fxI8H7uQFH6xgFB2UmRHN1cl8CSB7YA
2yIXc3ATaG1dXSqvBC7s+ApRJHAK67DvnZtJ5PJF7QJo4yVhfbgHdRqGFMlc/Huk
yHLYoB8c4teITjtU5i2oS3pH/HfqZv5a9TMRKO+edtFZadaBJKdOLetZfUCU8V5G
zYGNGaHqRHIDE7g7qt+3bw9Nszj2tllnfY+4SkxPwobhQ1FRePCEcCBS1zxsZ8HJ
ycq0c+uCPSRQ/T8rhdf4MUNRJN6lE/b0VlM7znNCm34t+M8Ja6zVYThotyyqGB8=
=ij5H
-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/20171102073340.GP1045%40mail-itl.
For more options, visit https://groups.google.com/d/optout.


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

2017-11-02 Thread '[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.