> Check what netvm is set for those VMs. I guess currently you have two of
> them: sys-net and (just restored) sys-net1. Choose which one you want to
> use and remove the other.
>
Thanks a lot Marek and Andrew for your help and patience. I now have access to
all my AppVMs.
--
You received
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Thu, Dec 22, 2016 at 08:40:02AM -0800, jasonwalshismyn...@gmail.com wrote:
> I was able to restore all VMs with this command :
>
> "qvm-backup-restore -d sys-net --rename-conflicting /run/media/user/New\
>
> > Just one thing : I want to use my backed up "debian-8" TemplateVM, how can
> > I replace the original "debian-8" ? I'm not able to delete it and as long
> > as its there I won't be able to retore my backed up "debian-8" Template VM.
>
> Command line version of restore tool
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Thu, Dec 22, 2016 at 06:03:06AM -0800, jasonwalshismyn...@gmail.com wrote:
> On Tuesday, December 20, 2016 at 5:56:40 PM UTC-5, raah...@gmail.com wrote:
> > On Tuesday, December 20, 2016 at 9:11:58 AM UTC-5, jasonwals...@gmail.com
> > wrote:
> >
On Tuesday, December 20, 2016 at 5:56:40 PM UTC-5, raah...@gmail.com wrote:
> On Tuesday, December 20, 2016 at 9:11:58 AM UTC-5, jasonwals...@gmail.com
> wrote:
> > There is a typo in my last message but it was written as "journald-dev-log"
> > rather than "journal-dev-log".
> >
> > Is there
There is a typo in my last message but it was written as "journald-dev-log"
rather than "journal-dev-log".
Is there something to do with my problems with dom0 ? At the bare minimum I
would like at least to recover my files from my VMs.
Thanks
--
You received this message because you are
> > > It isn't a command, it should be a socket. But apparently it doesn't
> > > exist. Check status of systemd unit providing it:
> > >
> > > systemctl status systemd-journcald-dev-log.socket
>
> A typo here, should be systemd-journald-dev-log.socket
[user@dom0 ~]$ systemctl status
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Fri, Dec 16, 2016 at 07:59:34AM -0800, ve2...@gmail.com wrote:
>
> > It isn't a command, it should be a socket. But apparently it doesn't
> > exist. Check status of systemd unit providing it:
> >
> > systemctl status
> It isn't a command, it should be a socket. But apparently it doesn't
> exist. Check status of systemd unit providing it:
>
> systemctl status systemd-journcald-dev-log.socket
>
> You may want to remove /dev/log and restart above unit (sudo systemctl
> restart
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Fri, Dec 16, 2016 at 04:58:35AM -0800, jasonwalshismyn...@gmail.com wrote:
>
> > This looks like a problem with connecting to syslog. Do you have
> > /dev/log in place? It should be something like this:
> >
> > [marmarek@dom0 ~]$ ls -l
> This looks like a problem with connecting to syslog. Do you have
> /dev/log in place? It should be something like this:
>
> [marmarek@dom0 ~]$ ls -l /dev/log
> lrwxrwxrwx 1 root root 28 Dec 13 23:57 /dev/log ->
> /run/systemd/journal/dev-log
[user@dom0 ~]$ ls -l /dev/log
srw-rw-rw-
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Thu, Dec 15, 2016 at 07:10:12AM -0800, jasonwalshismyn...@gmail.com wrote:
>
> > - From this thread:
> >
> > https://groups.google.com/d/topic/qubes-users/s3FJWqKw6Ps/discussion
> >
> > 'Please check "sudo systemctl status qubes-qmemman", or
> And what happens when you restart qubes-qmemman?
this :
Job for qubes-qmemman.service failed because the control process exited with
error code. See "systemctl status qubes-qmemman.service" and "journalctl -xe"
for details.
"sudo systemctl status qubes-qmemman.service" returns the same
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 12/15/16 07:10, jasonwalshismyn...@gmail.com wrote:
>
>> - From this thread:
>>
>> https://groups.google.com/d/topic/qubes-users/s3FJWqKw6Ps/discussion
>>
>> 'Please check "sudo systemctl status qubes-qmemman", or better "sudo
>> journalctl -u
> - From this thread:
>
> https://groups.google.com/d/topic/qubes-users/s3FJWqKw6Ps/discussion
>
> 'Please check "sudo systemctl status qubes-qmemman", or better "sudo
> journalctl -u qubes-qmemman" for error messages. Then you can restart
> the service with "sudo systemctl restart
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 2016-12-15 05:35, jasonwalshismyn...@gmail.com wrote:
>
>> Yes, I see the problem. It sounds like your ServiceVMs are based
>> on debian-8. Have you tried basing them on the default Fedora
>> template instead?
>
> Ok, I have now assign sys-net
> Yes, I see the problem. It sounds like your ServiceVMs are based on
> debian-8. Have you tried basing them on the default Fedora template
> instead?
Ok, I have now assign sys-net & sys-firewall to fedora-23 TemplateVM, I still
have the same qmemman error.
Is it normal that when I start my
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 2016-12-14 07:08, jasonwalshismyn...@gmail.com wrote:
> After running this process a couple times :
>
> https://www.qubes-os.org/doc/upgrade-to-r3.2/
>
> I think I was able to upgrade to 3.2, but with new problems
>
> Here's the results for
After running this process a couple times :
https://www.qubes-os.org/doc/upgrade-to-r3.2/
I think I was able to upgrade to 3.2, but with new problems
Here's the results for "yum info qubes-core-dom0" :
Redirecting to '/usr/bin/dnf info qubes-core-dom0' (see 'man yum2dnf')
Failed to synchonize
> Is your sys-firewall based on Debian template? If so, there is
> additional step in the upgrade procedure.
this is what I've done :
sudo qubes-dom0-update systemd-compat-libs perl-libwww-perl perl-Term-ANSIColor
perl-Term-Cap gdk-pixbuf2-xlib speexdsp qubes-mgmt-salt-admin-tools lvm2
--> n
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Mon, Dec 12, 2016 at 07:52:53AM -0800, jasonwalshismyn...@gmail.com wrote:
>
> > If updates are already downloaded (it looks so), you can try running
> > "sudo dnf update" in dom0 - maybe it will be better at resolving
> > dependencies.
>
>
> If updates are already downloaded (it looks so), you can try running
> "sudo dnf update" in dom0 - maybe it will be better at resolving
> dependencies.
[user@dom0 ~]$ sudo dnf update
sudo: dnf: command not found
--
You received this message because you are subscribed to the Google Groups
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Mon, Dec 12, 2016 at 06:23:40AM -0800, jasonwalshismyn...@gmail.com wrote:
> I'm trying to update dom0, (419 Updates Selected).
>
> After searching for infos on qubesOS website and from google, after various
> attempt, I'm still getting this
23 matches
Mail list logo