I found the "problem".
It seems that the code of the systemd script that detects virtualization
(systemd-detect-virt) has changed between fedora-23 and fedora-24.
The one in fedora-24 is confused by the fact I use QubesOS insed a KVM
VM and is not able to detect xen on top of the VM (it detects KVM
instead). As a consequence, the service xendriverdomain.service was not
started (ConditionVirtualization not met), causing networking to not
work on the AppVM (as the backend network was not correctly configured
on the NetVM side).
To workaround this "problem" I overwritten the systemd-detect-virt in
fedora-24 by the one in fedora-23.
Everything works fine again :)


On 11/25/2016 12:01 PM, BePe wrote:
> I suspect that the script vif-route-qubes is not called at all?
> What triggers this script? Where is it configured?
>
> On 11/24/2016 04:09 PM, Opal Raava wrote:
>> On Thursday, November 24, 2016 at 3:03:01 PM UTC+1, BePe wrote:
>>> Hi Opal,
>>> Thanks.
>>> But I don't know all the actions that should be realized. For sur there
>>> will be IP configuration, routing and probably iptables rules.
>>> BePe
>>>
>>> On 11/24/2016 01:22 PM, Opal Raava wrote:
>>>> On Thursday, November 24, 2016 at 8:33:14 AM UTC+1, BePe wrote:
>>>>> Hi All,
>>>>>
>>>>>         I have an installation of QubeOS 3.2  inside a KVM VM (I know
>>>>>         that it's not recommended but it's very practical for testing)
>>>>>         that was working without any major issue since last week when I
>>>>>         decided to upgrade to the fedora-24 template and have migrated
>>>>>         the net-vm et the firewall-vm to use the new template.
>>>>>
>>>>>         Since then, the networking (e.g. internet access) is no longer
>>>>>         working on all the AppVM except on the net-vm.
>>>>>
>>>>>         I noted that when an AppVM is started there is no vif interface
>>>>>         that is brought up in its configured NetVM as it used be the
>>>>>         case when fedora-23 template was used for the NetVM.
>>>>>
>>>>>         Does somebody have the same issue? How could I fix/workaround
>>>>>         the problem?
>>>>>
>>>>>         Is there a way to manually and properply bring up the vif.XX
>>>>>         interface to establish the connection between a VM and its
>>>>>         configured NetVM?
>>>>>
>>>>>         Thanks for your help.
>>>>>
>>>>>         Regards,
>>>>>
>>>>>       
>>>>>     -- 
>>>>> BePe
>>>> Hi BePe, I don't have the same issue, but maybe you can manually put the 
>>>> required ifconfig orso commands in your /rw/config/rc.local file? (and 
>>>> make that file executable.)
>>>>
>>> -- 
>>> BePe
>> Hmm there should be an easier way, but I dont know how... I'm still a noob :/
>>

-- 
BePe

-- 
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/3aa66b77-9a06-83d8-d965-6583ef10d2a9%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to