I reinstalled Qubes R4.0.1, and during the reboot-and-setup phase I left
all options unchecked. Qubes installed some template VM's, but didn't add
sys-net/sys-usb/sys-firewall as desired.
This time I started with a small number of VM's and it worked - I am trying
more and I don't get the original error.
I should summarize what I tried:
- fresh install, accepted setup default vms, setup net vm, usb vm: - got
errors during restore
- fresh install, no checkboxes ticked except for last - 'dont set anything
up' - got errors during restore
- fresh install, no checkboxes ticked at all - backups working!
I'm wondering could I have clicked 'Dont set anything up' the first time
around.. I didn't record logs from that session, but guessing sys-net /
sys-usb having their devices attached may conflict with the restore of
similar VM's from an old machine?
On Mon, Mar 25, 2019 at 10:19 PM wrote:
> I installed a new SSD in my laptop, so I created a backup of my old one
> and tried to restore it into a fresh install of Qubes R4.0.1 (the old
> system was Qubes R4.0).
>
> I'm receiving errors when I try to restore from the backup - 'Error
> restoring VM: empty response from qubesd - check journalctl for details'. I
> first tried restoring all VM's in the backup, before trying just 'sys-net'
> and 'fedora-29'
>
> I have run the restore in 'verify only' mode and it passes.
>
> I checked journalctl, and I can see some python tracebacks:
>
> The first error is regarding sys-net:
> "AttributeError: 'TemplateVM' object has no attribute '_qubesprop_kernel'"
> followed by:
> 'TemplateVM' object has no attribute: '_qubesprop_kernel'
> followed by:
> 'Qubes' object has no attribute 'qubesprop_default_kernel'
> followed by:
> property 'default_kernel' have no default
>
> I checked out the global system settings, which at indicates my new
> systems default kernel is '4.14.74-1'.
>
> There was another error also, while processing fedora-29:
> "'Template VM' object has no attribute '_qubesprop_kernel'"
> followed by:
> "'Template VM' object has no attribute 'template'"
> followed by
> "'Qubes' object has no attribute: 'qubesprop_default_kernel'"
>
> I'm not sure where to begin with fixing this, but I'm really glad I still
> have the original drive :)
>
> One thing to note is in the reboot-and-setup phase I and clicked "Don't
> configure anything". Could my new system be missing configuration settings,
> or are the python errors related to the contents of the backup? I checked
> this because first time, I accepted the defaults and found it hard to
> remove the colliding VM's.
>
> I think I'll try installing again and letting qubes do some of that
> configuration and see how that goes.
>
> I notice the other similar sounding report seems to be due to the
> passphrase, and perhaps is not related to my issue.
>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "qubes-users" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/qubes-users/mQGxtWCbS0k/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> qubes-users+unsubscr...@googlegroups.com.
> To post to this group, send email to qubes-users@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/qubes-users/b851e9be-fc19-4307-afff-3b55950c7aed%40googlegroups.com
> .
> For more options, visit https://groups.google.com/d/optout.
>
--
You received this message because you are subscribed to the Google Groups
"qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to qubes-users+unsubscr...@googlegroups.com.
To post to this group, send email to qubes-users@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/qubes-users/CAHv%2Btb5F11hSyxv1yKmNs6g57e6Oac%2BgYGUBmFtBuFbNyRXsww%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
