Windows 7 VM on Qubes $

[lok...@gmail.com]

After installing Qubes 4rc1 on a new laptop, I took a backup of my Windows 7 VM from my old 3.2 installation and loaded it onto the new laptop. This did not work at all.

After some searching I came across a statement suggesting that Windows not work is a known issue and will be fixed with the final release of Qubes 4.

My question is: Will the Windows 7 support work once rc2 comes out? I don't use the Windows support much, but when I do, it's really important. At the same time I can't stay with Qubes 3.2 since my new laptop is using Kaby Lake, and thus requires Qubes 4.

What is the current status with regards to Windows 7 and Qubes 4?

[Foppe de Haan]

Did the backup restoration process work at all, or did it error and skip the win7 VM?

[lok...@gmail.com]

On Tuesday, 3 October 2017 16:56:24 UTC+8, Foppe de Haan wrote:

> Did the backup restoration process work at all, or did it error and skip the win7 VM?

Thanks for the reply.

Please allow me to do it all from the beginning again and record all the logs. I'll update in a day or so.

[Foppe de Haan]

To clarify: when I try to restore a win7 VM from 3.2, it skips restoring that VM, citing an error, but does create an entry with that name (which doesn't work). I wasn't sure whether that was due to corruption of the backup, or a bug, so I haven't reported it yet.

[Elias Mårtenson]

Thanks. I wasn't in front of the computer when the restoration happened (it was done by someone else). That's why I can't say what kind of errors were displayed. That's why I want to do it again and capture a log.

When trying to start the VM using qvm-start, a window is opened with some diagnostic information scrolling past (too fast to see what's going on), and then the window disappears and the VM is shut down. Trying to go to settings shows a python error.

[Foppe de Haan]

On Tuesday, October 3, 2017 at 12:54:23 PM UTC+2, Elias Mårtenson wrote:
> On 3 October 2017 at 18:48, Foppe de Haan <0spin...@gmail.com> wrote:
> On Tuesday, October 3, 2017 at 11:01:47 AM UTC+2, lok...@gmail.com wrote:
>
> > On Tuesday, 3 October 2017 16:56:24 UTC+8, Foppe de Haan  wrote:
>
> >
>
> > > Did the backup restoration process work at all, or did it error and skip the win7 VM?
>
> >
>
> > Thanks for the reply.
>
> >
>
> > Please allow me to do it all from the beginning again and record all the logs. I'll update in a day or so.
>
>
>
> To clarify: when I try to restore a win7 VM from 3.2, it skips restoring that VM, citing an error, but does create an entry with that name (which doesn't work). I wasn't sure whether that was due to corruption of the backup, or a bug, so I haven't reported it yet.
>
>
>
> Thanks. I wasn't in front of the computer when the restoration happened (it was done by someone else). That's why I can't say what kind of errors were displayed. That's why I want to do it again and capture a log.

ok.

>
> When trying to start the VM using qvm-start, a window is opened with some diagnostic information scrolling past (too fast to see what's going on), and then the window disappears and the VM is shut down. Trying to go to settings shows a python error.

The python error is about mem-writer, presumably?

[One7two99]

Hello,

>> What is the current status with
>> regards to Windows 7 and Qubes 4?

I would also like to know what are the plans for windows 7 (or maybe even 10) support on Qubes 4.

Working on a *nix only system will not work for all users as lots of Enterprise application are windows based (in our case: the ERP/CRM) and of course Outlook/Exchange is the app I spent most of my time.

So the question:
can we see a robust implementation of Windows in Qubes 4 (production release) including seamless mode?

[799]

[lok...@gmail.com]

On Tuesday, 3 October 2017 19:26:29 UTC+8, Foppe de Haan wrote:

> > When trying to start the VM using qvm-start, a window is opened with some diagnostic information scrolling past (too fast to see what's going on), and then the window disappears and the VM is shut down. Trying to go to settings shows a python error.
>
> The python error is about mem-writer, presumably?

Actually no. The error reads:

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

TypeError: setChecked(self, bool): argument 1 has unexpected type 'str'
at line 9
of file /usr/bin/qubes-vm-settings