[libvirt-users] libvirt-sandbox on Fedora 21
It sure would be nice if someone who knows what they are doing took a look at this problem: https://bugzilla.redhat.com/show_bug.cgi?id=1135762 The current situation on Fedora 21 is that virt-sandbox and virt-sandbox-service simply do not work if a network is defined (e.g., -N address-192.168.1.1/34). I would give dhcp as an example but to work, that needs to patch I submitted in another BZ report. Since both virt-sandbox -c lxc:/// -N <network>,source=default and doing systemctl start <sandbox> result in the same error and since I am running the fedora-virt-preview rpms and the failure *does not* occur on Fedora 20 but *does* occur on Fedora 21, I have to assume that the problem is not directly in libvirt. However, determining what/where the problem really is, is stretching my abilities a bit too far ... help!! Gene
On Wed, 24 Sep 2014, Gene Czarcinski wrote:
It sure would be nice if someone who knows what they are doing took a look at this problem:
The current situation on Fedora 21 is that virt-sandbox and virt-sandbox-service simply do not work if a network is defined (e.g., -N address-192.168.1.1/34)
Your example in the bug mentioned uses a /24 and a last octet not .1 This email with a: /34 is clearly a bad CIDR mask, but I cannot find an online instance of the man page to confirm that this is not an end to a range. It seems unlikely, though We have sub-netted off 'little' CIDR ranges for our libvirt work. /29's and such Can you make sure a range is 'clean' and make it smaller than a /24 (as in the bug) -- Russ herrold
On 09/24/2014 05:15 PM, R P Herrold wrote:
On Wed, 24 Sep 2014, Gene Czarcinski wrote:
It sure would be nice if someone who knows what they are doing took a look at this problem:
The current situation on Fedora 21 is that virt-sandbox and virt-sandbox-service simply do not work if a network is defined (e.g., -N address-192.168.1.1/34)
Your example in the bug mentioned uses a /24 and a last octet not .1
This email with a: /34 is clearly a bad CIDR mask, but I cannot find an online instance of the man page to confirm that this is not an end to a range. It seems unlikely, though
We have sub-netted off 'little' CIDR ranges for our libvirt work. /29's and such
Can you make sure a range is 'clean' and make it smaller than a /24 (as in the bug)
My typing skills are clearly lacking!!! 34 -> 24 Anyway, with my patch so that dhcp does work, you can specify "-N dhcp,source=default" where "dhcp" caln also be any valid "address=<ip>/<mask>". This point is *read the damn bugzilla repoort* for the problem specifics but this works on Feddora 20 but *not on Fedora 21*,
On 09/24/2014 02:43 PM, Gene Czarcinski wrote: > It sure would be nice if someone who knows what they are doing took a > look at this problem: > https://bugzilla.redhat.com/show_bug.cgi?id=1135762 > > The current situation on Fedora 21 is that virt-sandbox and > virt-sandbox-service simply do not work if a network is defined (e.g., > -N address-192.168.1.1/34). I would give dhcp as an example but to > work, that needs to patch I submitted in another BZ report. > > Since both virt-sandbox -c lxc:/// -N <network>,source=default and > doing systemctl start <sandbox> result in the same error and since I > am running the fedora-virt-preview rpms and the failure *does not* > occur on Fedora 20 but *does* occur on Fedora 21, I have to assume > that the problem is not directly in libvirt. However, determining > what/where the problem really is, is stretching my abilities a bit too > far ... help!! The problem is now fixed by iproute-3.16.0-3: * Sat Oct 04 2014 Lubomir Rintel <lkundrak@v3.sk> - 3.16.0-3 - Backport fix for ip link add name regression that broke libvirt Gene
participants (2)
-
Gene Czarcinski -
R P Herrold