Qubes Release 2 Beta 2

[Joanna Rutkowska]

Ok, here it goes:

http://theinvisiblethings.blogspot.com/2013/02/qubes-2-beta-2-has-been-released.html

Enjoy!

joanna.

[Outback Dingo]

WOW nice new installer, great update for KDE, clean install, on SSD with BTRFS......... Fedora 18 template base... GREAT WORK!

Im impressed and thats quite difficult to do!....... keep up the great work

[Olivier Médoc]

Hello,

Great work again,

This new KDE looks really nice, I still have to test XFCE now. From now,
everything works except one or two anoying but non blocking thinks (yeah
sorry, looks like I'm good at discovering problems...):

I performed a backup, installed qubes R2B2 and performed a restore. I
discovered that the restore process fails if : the template does not
exists (which is a problem for archlinux template or appvms based on
fedora17). I just had to edit the qubes.xml file to change fedora17 to
fedora18 so that I can restore the template. I have two comments about that:
- It would be interesting to give the user the choice to install the
appvm with no valid template
- It would be interesting to give the user the choice to change the
template on restore (but this means more coding than the previous)

- The keyboard layouts are not propagated to the appvm (I user azerty
keyboard, but when I start a VM, the keyboard is set to qwertz). I did
not investigated this point yet.

- Several icons seems to be missing. For instance, only the blue and the
disposablevm locks are shown in the kde menu.

- The qubes-windows-tools package is not available anymore. By the way,
I never managed to install the qubes agent on Windows XP nor on Windows
7 (only pv drivers worked, but the agent doesn't start).

That's all for now.

Best regards,
Olivier

[Marek Marczykowski]

On 02.03.2013 15:01, Olivier Médoc wrote:
> On 02/28/13 19:29, Joanna Rutkowska wrote:
>> Ok, here it goes:
>>
>> http://theinvisiblethings.blogspot.com/2013/02/qubes-2-beta-2-has-been-released.html
>>
>>
>> Enjoy!
>>
>> joanna.
>>
> Hello,
>
> Great work again,
>
> This new KDE looks really nice, I still have to test XFCE now. From now,
> everything works except one or two anoying but non blocking thinks (yeah
> sorry, looks like I'm good at discovering problems...):
>
> I performed a backup, installed qubes R2B2 and performed a restore. I
> discovered that the restore process fails if : the template does not exists
> (which is a problem for archlinux template or appvms based on fedora17). I
> just had to edit the qubes.xml file to change fedora17 to fedora18 so that I
> can restore the template. I have two comments about that:
> - It would be interesting to give the user the choice to install the appvm
> with no valid template

It will not work b/c many files and settings are used from template.

> - It would be interesting to give the user the choice to change the template
> on restore (but this means more coding than the previous)

This is already done - check qvm-backup-restore options, especially
--replace-template. Unfortunately not possible to do from Qubes Manager for now.

> - The keyboard layouts are not propagated to the appvm (I user azerty
> keyboard, but when I start a VM, the keyboard is set to qwertz). I did not
> investigated this point yet.

I though I've fixed it already... Can you provide some details from
~/.xsession-errors from VM?

> - Several icons seems to be missing. For instance, only the blue and the
> disposablevm locks are shown in the kde menu.

Does it apply to all VMs or only restored from backup?
Changing VM label (even to the same one by qvm-prefs) should "fix" this.

> - The qubes-windows-tools package is not available anymore. By the way, I
> never managed to install the qubes agent on Windows XP nor on Windows 7 (only
> pv drivers worked, but the agent doesn't start).

Joanna, did you regenerated yum metadata after uploading the packages?

--
Best Regards / Pozdrawiam,
Marek Marczykowski
Invisible Things Lab

[Outback Dingo]

I also noticed that it is not possible to set colors in appvm since kde config settings are missing

and i tried to follow the instructions for a torvm which worked under R1 but dont appear to have a

valid repo under R2 since it was all upgraded, and are there plans to integrate the arch template?

or how can i get it integrated myself?? again..... GREAT JOB....... Daily Driver now..... bubye Kubuntu

[Joanna Rutkowska]

On 03/02/13 15:14, Marek Marczykowski wrote:
(...)

>> I performed a backup, installed qubes R2B2 and performed a restore. I
>> discovered that the restore process fails if : the template does not exists
>> (which is a problem for archlinux template or appvms based on fedora17). I
>> just had to edit the qubes.xml file to change fedora17 to fedora18 so that I
>> can restore the template. I have two comments about that:
>> - It would be interesting to give the user the choice to install the appvm
>> with no valid template
>
> It will not work b/c many files and settings are used from template.
>
>> - It would be interesting to give the user the choice to change the template
>> on restore (but this means more coding than the previous)
>
> This is already done - check qvm-backup-restore options, especially
> --replace-template. Unfortunately not possible to do from Qubes Manager for now.
>

I thought that perhaps we could change qvm-backup-restore to always use
the default template in case it could not find the original one. This
might cause problems, however, in the future when we supported more
templates, such as ArchLinux, Ubuntu, etc. But I guess we can always
assume one is the default, and only replace the *default* templates in
the backup with new defaults. What do you think Marek?

(...)

>> - The qubes-windows-tools package is not available anymore. By the way, I
>> never managed to install the qubes agent on Windows XP nor on Windows 7 (only
>> pv drivers worked, but the agent doesn't start).
>
> Joanna, did you regenerated yum metadata after uploading the packages?
>

Should be there now.

Oliver -- when you say you never managed to install it, what it means
what exactly?

joanna.

[inf...@gmail.com]

(delurking) Huge thanks for Qubes OS - it's magnifico :-)

I noticed a few snags doing a clean install of R2 Beta 2, then restoring Beta 1 backups

1. The "Test Media and install" function FAILS (immediately - 0.048%) for my USB key (Corsair Voyager Red), but good gpg check on .iso and then made a dd OK, and subsequent installation went fine? Suspect test function since think USB key fine.

2. sudo qubes-dom0-network-via-netvm up
fails with "unable to find ipconfig".

Solution: F18 no longer has ipconfig (now in package net-tools), so must fetch with sudo qubes-dom0-update net-tools

[I find this useful to backup to an NFS drive pace breaks dom0 isolation etc. (is there safer way); works OK after sudo qubes-dom0-update nfs-ustils]

3. Backup VMs in Qubes VM Manager fails (after a clean install)
[Command line backup works OK, but exclusions easier in GUI and disconcerting!]

Whoops. A critical error has occured. This is most likely a bug in Qubes Manager.

TypeError: C++ type 'list' is not supported as a slot argument type
at line 1567
of file /usr/lib64/python2.7/site-packages/qubesmanager/main.py.

----
line: self.connect(self.select_vms_widget, SIGNAL("items_removed(list)"), self.vms_removed)
func: __init__
line no.: 89
file: /usr/lib64/python2.7/site-packages/qubesmanager/backup.py
----
line: backup_window = BackupVMsWindow(app, self.qvm_collection, self.blk_manager, self.shutdown_vm)
func: action_backup_triggered
line no.: 1567
file: /usr/lib64/python2.7/site-packages/qubesmanager/main.py

4.  Leave | Shutdown very slow or hangs on black screen - have to hard reset after 2 mins

[5. have to disable UEFI mode and Legacy boot from USB else install hangs immediately on a black screen with "Security mode (?from memory not right?) disabled"]

hope helps

CB

Hardware: Lenovo X121e (Intel i3), 8Gb, Crucial M4 SSD 128Gb

[Marek Marczykowski]

On 02.03.2013 16:58, Joanna Rutkowska wrote:
> On 03/02/13 15:14, Marek Marczykowski wrote:
> (...)
>
>>> I performed a backup, installed qubes R2B2 and performed a restore. I
>>> discovered that the restore process fails if : the template does not exists
>>> (which is a problem for archlinux template or appvms based on fedora17). I
>>> just had to edit the qubes.xml file to change fedora17 to fedora18 so that I
>>> can restore the template. I have two comments about that:
>>> - It would be interesting to give the user the choice to install the appvm
>>> with no valid template
>>
>> It will not work b/c many files and settings are used from template.
>>
>>> - It would be interesting to give the user the choice to change the template
>>> on restore (but this means more coding than the previous)
>>
>> This is already done - check qvm-backup-restore options, especially
>> --replace-template. Unfortunately not possible to do from Qubes Manager for now.
>>
>
> I thought that perhaps we could change qvm-backup-restore to always use
> the default template in case it could not find the original one. This
> might cause problems, however, in the future when we supported more
> templates, such as ArchLinux, Ubuntu, etc. But I guess we can always
> assume one is the default, and only replace the *default* templates in
> the backup with new defaults. What do you think Marek?

This approach is already implemented in backup backend, just option not
exposed in any UI (neither Qubes Manager nor cmdline qvm-backup-restore).

[syd bris]

nice upgrde thankyou - qubes manager still says v1.0 in "about" menu though ;)

on a toshiba satellite during first boot, install of the default vms failed at dvm creation (same as r1 on this laptop) due to a qrexec timeout error. can boot into system ok. will create default vms manually as per previous post info:

qvm-create should work from normal user. Installer calls something like:
qvm-create --net --label red netvm
qvm-create --proxy --label green firewallvm
qvm-create-default-dvm --default-template --default-script

qvm-create work --label green
qvm-create banking --label green
qvm-create personal --label yellow
qvm-create untrusted --label red

[Olivier Médoc]

It is currently hard to reproduce because I don't have the windows tools
anymore (no package in the repos). Globally, on windows xp, it seems to
fails because the qubes agent is apparently 64 bits, on windows 7, it
complains that the agent stopped two quickly, but I didn-t investigated
this enough. It makes the installer fail, and all agent files are
deleted during rollback.

But PV drivers are installed correctly, so I have at least USB to
exchange data between VMs.
> joanna.
>

[Joanna Rutkowska]

As I wrote above, it should be there now...

> Globally, on windows xp, it seems to
> fails because the qubes agent is apparently 64 bits, on windows 7, it
> complains that the agent stopped two quickly, but I didn-t investigated
> this enough. It makes the installer fail, and all agent files are
> deleted during rollback.
>

Did you disable Windows signature enforcement, as described in the wiki?

joanna.

[Marek Marczykowski]

On 02.03.2013 18:10, inf...@gmail.com wrote:
> (delurking) Huge thanks for Qubes OS - it's magnifico :-)
>
> I noticed a few snags doing a clean install of R2 Beta 2, then restoring
> Beta 1 backups
>
> 1. The "Test Media and install" function FAILS (immediately - 0.048%) for
> my USB key (Corsair Voyager Red), but good gpg check on .iso and then made
> a dd OK, and subsequent installation went fine? Suspect test function since
> think USB key fine.
>

> 2. sudo qubes-dom0-network-via-netvm<http://qubes-os.org/trac/wiki/Dom0Tools/QubesDom0NetworkViaNetvm>up

> fails with "unable to find ipconfig".
>
> Solution: F18 no longer has ipconfig (now in package net-tools), so must

> fetch with sudo qubes-dom0-update<http://qubes-os.org/trac/wiki/Dom0Tools/QubesDom0Update>net-tools

Thanks, fixed. Anyway using qubes-dom0-network-via-netvm should be the last
resort.

> [I find this useful to backup to an NFS drive *pace* breaks dom0 isolation
> etc. (is there safer way); works OK after sudo qubes-dom0-update<http://qubes-os.org/trac/wiki/Dom0Tools/QubesDom0Update>nfs-ustils]

Backups over nfs? You know that will send all your data in *plain text* over
the network? Better do backups to local attached USB disk, or if you really
need backups over the network, use some encrypted protocol (sshfs?).

We plan to ease backups over the network, check #703 [1]. Any suggestions
appreciated :)

> 3. Backup VMs in Qubes VM Manager fails (after a clean install)
> [Command line backup works OK, but exclusions easier in GUI and
> disconcerting!]
>
> Whoops. A critical error has occured. This is most likely a bug in Qubes
> Manager.
>
> TypeError: C++ type 'list' is not supported as a slot argument type
> at line 1567
> of file /usr/lib64/python2.7/site-packages/qubesmanager/main.py.

This is already fixed in my git repo, will be in next qubes-manager package
release.

> 4. Leave | Shutdown very slow or hangs on black screen - have to hard
> reset after 2 mins

You can press ESC (and perhaps switch to tty1) to check at which stage it is
hanging.

> [5. have to disable UEFI mode and Legacy boot from USB else install hangs
> immediately on a black screen with "Security mode (?from memory not right?)
> disabled"]

Currently UEFI support isn't done. Mostly because I don't have hardware to
test it... If anyone willing to help in this area, patches welcome :) Probably
this will require:
1. For installer: changes in
installer[1]/lorax-templates-qubes/templates/config_files/x86/ (currently only
isolinux.cfg is prepared) and maybe lorax-templates-qubes/templates/x86.tmpl
2. For Qubes itself: changes in /boot/grub2, which would be packaged into
qubes-core-dom0.

[1] http://git.qubes-os.org/gitweb/?p=marmarek/installer.git;a=summary

>
> hope helps
>
> CB
>
> Hardware: Lenovo X121e (Intel i3), 8Gb, Crucial M4 SSD 128Gb
>

[Olivier Médoc]

On 03/02/13 15:14, Marek Marczykowski wrote:

> On 02.03.2013 15:01, Olivier Médoc wrote:
>> On 02/28/13 19:29, Joanna Rutkowska wrote:
>>> Ok, here it goes:
>>>
>>> http://theinvisiblethings.blogspot.com/2013/02/qubes-2-beta-2-has-been-released.html
>>>
>>>
>>> Enjoy!
>>>
>>> joanna.
>>>
>> Hello,
>>
>> Great work again,
>>
>> This new KDE looks really nice, I still have to test XFCE now. From now,
>> everything works except one or two anoying but non blocking thinks (yeah
>> sorry, looks like I'm good at discovering problems...):
>>
>> I performed a backup, installed qubes R2B2 and performed a restore. I
>> discovered that the restore process fails if : the template does not exists
>> (which is a problem for archlinux template or appvms based on fedora17). I
>> just had to edit the qubes.xml file to change fedora17 to fedora18 so that I
>> can restore the template. I have two comments about that:
>> - It would be interesting to give the user the choice to install the appvm
>> with no valid template
> It will not work b/c many files and settings are used from template.
>
>> - It would be interesting to give the user the choice to change the template
>> on restore (but this means more coding than the previous)
> This is already done - check qvm-backup-restore options, especially
> --replace-template. Unfortunately not possible to do from Qubes Manager for now.

Great, I will use that next time for the restore options.

Another interesting/missing feature is the ability to easily (through
the GUI) backup/restore kernels and templates. Especially when one
cloned a template for a specific purpose and installed specific tools
that works with a specific kernel version... Anyway, it is very easy to
do that by hand thanks to /var/lib/qubes being quite easy.

>> - The keyboard layouts are not propagated to the appvm (I user azerty
>> keyboard, but when I start a VM, the keyboard is set to qwertz). I did not
>> investigated this point yet.
> I though I've fixed it already... Can you provide some details from
> ~/.xsession-errors from VM?

You can find the file attached.

>> - Several icons seems to be missing. For instance, only the blue and the
>> disposablevm locks are shown in the kde menu.
> Does it apply to all VMs or only restored from backup?
> Changing VM label (even to the same one by qvm-prefs) should "fix" this.

In fact, if I change the untrusted to unstrustede it will work, but if I
revert to unstrusted, it fails. I don't know if the problem comes from
vms I restored or from default vm names. Creating a new vm called toto,
will show the icon correctly.

[inf...@gmail.com]

On 04/03/13 09:27, Olivier Médoc wrote:
> On 03/02/13 15:14, Marek Marczykowski wrote:
>> On 02.03.2013 15:01, Olivier Médoc wrote:

>> ......

>>> - It would be interesting to give the user the choice to change the
>>> template
>>> on restore (but this means more coding than the previous)
>> This is already done - check qvm-backup-restore options, especially
>> --replace-template. Unfortunately not possible to do from Qubes
>> Manager for now.

I wondered - does this have same effect as just changing the template
manually in Qubes Manager after a restore (or maybe --replace-template
does some extra housekeeping as well) ?.

CB

[inf...@gmail.com]

On 03/03/13 19:17, Marek Marczykowski wrote:

On 02.03.2013 18:10, inf...@gmail.com wrote:

1. The "Test Media and install" function FAILS (immediately - 0.048%) for 
my USB key (Corsair Voyager Red), but good gpg check on .iso and then made 
a dd OK, and subsequent installation went fine? Suspect test function since 
think USB key fine.

Please disregard 1. I ran Test Media on a different USB key and it worked fine (haven't established if Corsair on the fritz or just a glitch). I then clean reinstalled Beta 2 using that media, but everything else reported below still stands :-(

...

[I find this useful to backup to an NFS drive *pace* breaks dom0 isolation 
etc. (is there safer way); works OK after sudo qubes-dom0-update<http://qubes-os.org/trac/wiki/Dom0Tools/QubesDom0Update>nfs-ustils]

Backups over nfs? You know that will send all your data in *plain text* over
the network? 

I know, it's a confined test network, but definitely not acceptable for operational use

Better do backups to local attached USB disk, or if you really
need backups over the network, use some encrypted protocol (sshfs?).

Will look into that - thx

We plan to ease backups over the network, check #703 [1]. Any suggestions
appreciated :)

Aha!

Apropos, I have a really dumb question about the Qubes backup files.

When I look inside an AppVm directory with Nautilus I see a private.img file which is listed as about 30% larger than the size reported by DIsk Usage Analyzer (!)

Similarly when I look inside a vm-template, I see a root.img, root-cow.img, and root-cow.img old which together are 300% larger than the size reported (!!!)

The weird thing is that the backup and restore succeeds to (NFS or USB disks) on the basis of the size reported by the Qubes backup program (which is the same as Disk Usage Analyzer) ~ about 60GB

However if I try and take a copy of that 60Gb backup (with rsync) to another disk it consumes ALL the space suggested by all the individual .img files (around 200Gb in total)

I thought I was past newbie stage in Linux, but I guess there is something fundamental here I don't understand.

So the #703 looks a good plan, but FWIW I tried to compress my 200Gb (or is it 60Gb ?) Qubes backup into a tar.gz and it took 6 hours !

(3) This is already fixed in my git repo, will be in next qubes-manager package release.

thanks!

4.  Leave | Shutdown very slow or hangs on black screen - have to hard 
reset after 2 mins

You can press ESC (and perhaps switch to tty1) to check at which stage it is
hanging.

It hangs at least a couple of minutes at shutting down the Firewall machine, but will eventually shutdown and power-off by itself. No idea why as did not see this in identical configuration with Beta 1

Currently UEFI support isn't done. Mostly because I don't have hardware to test it... If anyone willing to help in this area, patches welcome :)

Afraid vastly beyond my skills to contribute, but happy to test and report (and look forward to testing Evil Maid auto-install when ready)

---

One additional snag noticed. I had TorVM set up fine in Beta 1, and tried to repeat the recipe for Beta 2, but it failed on

	sudo yum install qubes-tor-init

(Could not find qubes-tor-init, maybe not done yet for F18 ? Would like to phase out my F17 templates from Beta 1 to save space)

Another dumb question: "SOCKS Port 9049 should be used by web browsers" - what exactly do I do in my browser to ensure this?

---

cheers

CB
(let me know if any additional tests useful re: any above)

[Olivier Médoc]

On 03/03/13 10:19, Joanna Rutkowska wrote:

Good.

>> Globally, on windows xp, it seems to
>> fails because the qubes agent is apparently 64 bits, on windows 7, it
>> complains that the agent stopped two quickly, but I didn-t investigated
>> this enough. It makes the installer fail, and all agent files are
>> deleted during rollback.
>>
> Did you disable Windows signature enforcement, as described in the wiki?
>
> joanna.
>

Yes, I ran the commands found on the CD README.

The error appears at the end of the setup when the setup try to starts
the qrexec_agent service:
Service 'Qubes RPC Agent (QrexecAgent) failed to start. Verify that you
have sufficient privileges to start system services.'. In windows
application logs, I see the Error 1920.

If I run the setup as administrator, the error message is the same but
the error code is 1923.

[Olivier Médoc]

That's really strange. The problem occurs for appvms (even newly created
one), but if I run the fedora18-template the keyboard layout is
correctly set.

Another point, it seems that for the appvm case xkbcomp is really
started with the correct layout (during xinitrc.d/qubes_keymap.sh). I
don't know if something unset this after qubes_keymap.sh. By the way, if
I run qubes_keymap.sh alone inside a terminal, it will set correctly the
keymaps.

[Olivier Médoc]

I really don't know... Process viewer shows that qrexec_agent.exe exits
just after reading registry keys related to RPC things (some of these
keys do not exist).

[Marek Marczykowski]

On 04.03.2013 11:18, inf...@gmail.com wrote:
> On 03/03/13 19:17, Marek Marczykowski wrote:
>> On 02.03.2013 18:10, inf...@gmail.com wrote:

(...)

>> We plan to ease backups over the network, check #703 [1]. Any suggestions
>> appreciated :)
>
> Aha!
>
> Apropos, I have a really dumb question about the Qubes backup files.
>
> When I look inside an AppVm directory with Nautilus I see a private.img file
> which is listed as about 30% larger than the size reported by DIsk Usage
> Analyzer (!)
>
> Similarly when I look inside a vm-template, I see a root.img, root-cow.img,
> and root-cow.img old which together are 300% larger than the size reported (!!!)
>

> The weird thing is that the backup _and_ restore succeeds to (NFS _or_ USB

> disks) on the basis of the size reported by the Qubes backup program (which is
> the same as Disk Usage Analyzer) ~ about 60GB
>
> However if I try and take a copy of that 60Gb backup (with rsync) to another
> disk it consumes ALL the space suggested by all the individual .img files
> (around 200Gb in total)
>
> I thought I was past newbie stage in Linux, but I guess there is something
> fundamental here I don't understand.

Those are sparse files:
http://en.wikipedia.org/wiki/Sparse_files

> So the #703 looks a good plan, but FWIW I tried to compress my 200Gb (or is it
> 60Gb ?) Qubes backup into a tar.gz and it took 6 hours !
>

>>> 4. Leave | Shutdown very slow or hangs on black screen - have to hard
>>> reset after 2 mins
>> You can press ESC (and perhaps switch to tty1) to check at which stage it is
>> hanging.
>
> It hangs at least a couple of minutes at shutting down the Firewall machine,
> but will eventually shutdown and power-off by itself. No idea why as did not
> see this in identical configuration with Beta 1

It is known that netvm shutdown can take a while (some timeout on pci backend)...

>> Currently UEFI support isn't done. Mostly because I don't have hardware to
>> test it... If anyone willing to help in this area, patches welcome :)
>
> Afraid vastly beyond my skills to contribute, but happy to test and report
> (and look forward to testing Evil Maid auto-install when ready)
>
> ---
>
> One additional snag noticed. I had TorVM set up fine in Beta 1, and tried to

> repeat the recipe <http://wiki.qubes-os.org/trac/wiki/UserDoc/TorVM> for Beta

> 2, but it failed on
>
> | sudo yum install qubes-tor-init|
>
> (Could not find qubes-tor-init, maybe not done yet for F18 ? Would like to
> phase out my F17 templates from Beta 1 to save space)

Torproject.org doesn't released yet packages for Fedora 18, but those
available in Fedora are still too old.

> Another dumb question: "SOCKS Port 9049 should be used by web browsers" - what
> exactly do I do in my browser to ensure this?

Firefox: Preferences->Advanced->Network->Settings->Manual proxy
configuration->SOCKS Host.

[inf...@gmail.com]

On Monday, 4 March 2013 16:40:55 UTC, Marek Marczykowski wrote:

...Those are sparse files:
http://en.wikipedia.org/wiki/Sparse_files

thanks - all explained (rysnc --sparse), and for other answers also

cheers

CB

[Tirus Tylwyth]

Adding to the kudos here, I just made this release my daily. :) Awesome work, I spread the word at every opportunity.

[Outback Dingo]

I also concur, it is now very capable of being a daily driver, even with wifi, today i bought my laptop on a clients site, when i launched qubes, and a torvm and a security vm, and my regular personal vm ... their techs were in awe when i explained the security feature sets, and segregation. And to top it, they were liking how i could launch consoles and apps from different vms and have them appear on a kde desktop.

--
You received this message because you are subscribed to the Google Groups "qubes-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email to qubes-devel...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

[Olivier Médoc]

On 03/04/13 14:25, Olivier M�doc wrote:

> On 03/04/13 10:27, Olivier M�doc wrote:
>> On 03/02/13 15:14, Marek Marczykowski wrote:

I still didn't managed to solve this point..

>>>> - Several icons seems to be missing. For instance, only the blue
>>>> and the
>>>> disposablevm locks are shown in the kde menu.
>>> Does it apply to all VMs or only restored from backup?
>>> Changing VM label (even to the same one by qvm-prefs) should "fix"
>>> this.
>> In fact, if I change the untrusted to unstrustede it will work, but
>> if I revert to unstrusted, it fails. I don't know if the problem
>> comes from vms I restored or from default vm names. Creating a new vm
>> called toto, will show the icon correctly.

I noticed that the icons are displayed correctly using XFCE. So I'm now
using XFCE :). I tried to remove the KDE config files from my home, but
the problem is still there for KDE...

[7v5w7go9ub0o]

On 03/05/13 22:35, Outback Dingo wrote:
> I also concur, it is now very capable of being a daily driver, even
> with wifi, today i bought my laptop on a clients site, when i
> launched qubes, and a torvm and a security vm, and my regular
> personal vm ... their techs were in awe when i explained the security
> feature sets, and segregation. And to top it, they were liking how i
> could launch consoles and apps from different vms and have them
> appear on a kde desktop.
>
>
> On Tue, Mar 5, 2013 at 10:27 PM, Tirus Tylwyth
> <tirust...@gmail.com>wrote:
>
>> Adding to the kudos here, I just made this release my daily. :)
>> Awesome work, I spread the word at every opportunity.

This "word spreading" seems a very good thing to do - puts ITL on the
map when businesses look to upgrade their equipment.

Would be particularly impressive, were you two to open up a Windows vm
(and then, of course, shut it back down as being unnecessary :-) ).

Dingo, have you become comfortable with Arch? (Arch seems to have much
in common with Gentoo - my favorite.)

[Marek Marczykowski]

On 06.03.2013 09:10, Olivier Médoc wrote:
> On 03/04/13 14:25, Olivier Médoc wrote:

>> On 03/04/13 10:27, Olivier Médoc wrote:
>>> On 03/02/13 15:14, Marek Marczykowski wrote:

>>>> On 02.03.2013 15:01, Olivier Médoc wrote:
>>>>> - Several icons seems to be missing. For instance, only the blue and the
>>>>> disposablevm locks are shown in the kde menu.
>>>> Does it apply to all VMs or only restored from backup?
>>>> Changing VM label (even to the same one by qvm-prefs) should "fix" this.
>>> In fact, if I change the untrusted to unstrustede it will work, but if I
>>> revert to unstrusted, it fails. I don't know if the problem comes from vms
>>> I restored or from default vm names. Creating a new vm called toto, will
>>> show the icon correctly.
> I noticed that the icons are displayed correctly using XFCE. So I'm now using
> XFCE :). I tried to remove the KDE config files from my home, but the problem
> is still there for KDE...

Perhaps there is some broken symlink for untrusted VM, try something like:
find /var/lib/qubes /home -follow -type l

[Marek Marczykowski]

This is the same. In fact --replace-template option makes possible to restore
VM without matching template in system.

[inf...@gmail.com]

On Sunday, 3 March 2013 19:17:59 UTC, Marek Marczykowski wrote:

On 02.03.2013 18:10, inf...@gmail.com wrote:
>
> 2. sudo qubes-dom0-network-via-netvm<http://qubes-os.org/trac/wiki/Dom0Tools/QubesDom0NetworkViaNetvm>up
> fails with "unable to find ipconfig".
>
> Solution: F18 no longer has ipconfig (now in package net-tools), so must
> fetch with sudo qubes-dom0-update<http://qubes-os.org/trac/wiki/Dom0Tools/QubesDom0Update>net-tools

Thanks, fixed. Anyway using qubes-dom0-network-via-netvm should be the last
resort

BTW - I noticed this still seems to be there. Did fresh install R2B2 yesterday, updated Dom0, and saw script error still there

(pace cautions of using networking in Dom0)

> 3. Backup VMs in Qubes VM Manager fails (after a clean install)
> [Command line backup works OK, but exclusions easier in GUI and
> disconcerting!]
>
> Whoops. A critical error has occured. This is most likely a bug in Qubes
> Manager.
>
> TypeError: C++ type 'list' is not supported as a slot argument type
> at line 1567
> of file /usr/lib64/python2.7/site-packages/qubesmanager/main.py.

This is already fixed in my git repo, will be in next qubes-manager package
release.

and FYI to confirm this is fixed, worked fine now, many thanks

CB

[robert....@gmail.com]

I'm having exactly the same issue with my Qubes R2 install.  Was a solution ever identified?  What information/logs do you need to help me address this issue?

Robert