New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fc15-based firewallvm doesn't create PR-QBS net rules #414

Closed
marmarek opened this Issue Mar 8, 2015 · 6 comments

Comments

Projects
None yet
2 participants
@marmarek
Member

marmarek commented Mar 8, 2015

Reported by joanna on 9 Jan 2012 09:15 UTC
... and as a result DNS doesn't work in any other VM using this fvwm. When switching back to fc14 (qvm-pres -s firewallvm template fedora-14-x64) all works fine.

Migrated-From: https://wiki.qubes-os.org/ticket/414

@marmarek

This comment has been minimized.

Show comment
Hide comment
@marmarek

marmarek Mar 8, 2015

Member

Comment by marmarek on 10 Jan 2012 01:12 UTC
There is race between startup scripts, because systemd (init in FC15+) starts scripts with the same priority simultaneously. /var/run/qubes is created too late.

This will be fixed by using proper systemd services with real dependencies (not just numbers for ordering).

Member

marmarek commented Mar 8, 2015

Comment by marmarek on 10 Jan 2012 01:12 UTC
There is race between startup scripts, because systemd (init in FC15+) starts scripts with the same priority simultaneously. /var/run/qubes is created too late.

This will be fixed by using proper systemd services with real dependencies (not just numbers for ordering).

@marmarek

This comment has been minimized.

Show comment
Hide comment
@marmarek

marmarek Mar 8, 2015

Member

Comment by joanna on 10 Jan 2012 09:13 UTC
So, after you add proper systemd support, will qubes-core-vm still work on fc14? I think such backward compatibility would be desirable.

Member

marmarek commented Mar 8, 2015

Comment by joanna on 10 Jan 2012 09:13 UTC
So, after you add proper systemd support, will qubes-core-vm still work on fc14? I think such backward compatibility would be desirable.

@marmarek

This comment has been minimized.

Show comment
Hide comment
@marmarek

marmarek Mar 8, 2015

Member

Comment by marmarek on 10 Jan 2012 10:08 UTC
Yes, this will be (actually is, but uncommited) separate subpackage (core-vm-sysvinit and core-vm-systemd).

Member

marmarek commented Mar 8, 2015

Comment by marmarek on 10 Jan 2012 10:08 UTC
Yes, this will be (actually is, but uncommited) separate subpackage (core-vm-sysvinit and core-vm-systemd).

@marmarek

This comment has been minimized.

Show comment
Hide comment
@marmarek

marmarek Mar 8, 2015

Member

Modified by marmarek on 13 Jan 2012 12:40 UTC

Member

marmarek commented Mar 8, 2015

Modified by marmarek on 13 Jan 2012 12:40 UTC

@marmarek marmarek assigned marmarek and unassigned rootkovska Mar 8, 2015

@marmarek

This comment has been minimized.

Show comment
Hide comment
@marmarek

marmarek Mar 8, 2015

Member

Modified by marmarek on 15 Jan 2012 04:02 UTC

Member

marmarek commented Mar 8, 2015

Modified by marmarek on 15 Jan 2012 04:02 UTC

@marmarek marmarek closed this Mar 8, 2015

@marmarek

This comment has been minimized.

Show comment
Hide comment
@marmarek

marmarek Mar 8, 2015

Member

Comment by marmarek on 15 Jan 2012 04:03 UTC
Update instruction: install qubes-core-vm and qubes-core-vm-systemd. Yum should automatically remove obsoleted packages.

Member

marmarek commented Mar 8, 2015

Comment by marmarek on 15 Jan 2012 04:03 UTC
Update instruction: install qubes-core-vm and qubes-core-vm-systemd. Yum should automatically remove obsoleted packages.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment