F20 beta virt-manager cannot create bridged network interface

classic Classic list List threaded Threaded
20 messages Options
Reply | Threaded
Open this post in threaded view
|

F20 beta virt-manager cannot create bridged network interface

Richard Michael
Hello,

I've just installed F20 beta x64 and applied all updates.

I'm attempting to create a bridge network interface in virt-manager
(0.10.0).  I complete the "Configure network interface" dialog, and
when I click "Finish" I receive an "Input Error" with message:

'str' object has no attribute 'XMLDesc'


A very similar error (when creating a bonded interface) is mentioned
in comments #1 and #2 in a bug related to "system-config-services"
here ...

https://bugzilla.redhat.com/show_bug.cgi?id=1028833#c2

 ... with the suggestion to file a bug against virt-manager.  I can't
find a virt-manager bug related to this however.


1/ I'll open one unless anyone has other suggestions or comments?


2/ I'm new to virt-manager and wondering about a work-around; should I
investigate using virsh to create the interface hoping virt-manager
will detect it?

Regards,
Richard
--
test mailing list
[hidden email]
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test
Reply | Threaded
Open this post in threaded view
|

Re: F20 beta virt-manager cannot create bridged network interface

Mateusz Marzantowicz
On 19.11.2013 01:13, Richard Michael wrote:

> Hello,
>
> I've just installed F20 beta x64 and applied all updates.
>
> I'm attempting to create a bridge network interface in virt-manager
> (0.10.0).  I complete the "Configure network interface" dialog, and
> when I click "Finish" I receive an "Input Error" with message:
>
> 'str' object has no attribute 'XMLDesc'
>
>
> A very similar error (when creating a bonded interface) is mentioned
> in comments #1 and #2 in a bug related to "system-config-services"
> here ...
>
> https://bugzilla.redhat.com/show_bug.cgi?id=1028833#c2
>
>  ... with the suggestion to file a bug against virt-manager.  I can't
> find a virt-manager bug related to this however.
>
>
> 1/ I'll open one unless anyone has other suggestions or comments?
>
>
> 2/ I'm new to virt-manager and wondering about a work-around; should I
> investigate using virsh to create the interface hoping virt-manager
> will detect it?
>

My work-around: Create bridge in NetworkManager (or directly edit config
files) and then add it to virt-manager. I always wondered what is this
whole bridge management in virt-manager for.



Mateusz Marzantowicz

--
test mailing list
[hidden email]
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test
Reply | Threaded
Open this post in threaded view
|

Re: F20 beta virt-manager cannot create bridged network interface

Richard Michael



On Mon, Nov 18, 2013 at 7:18 PM, Mateusz Marzantowicz <[hidden email]> wrote:
On 19.11.2013 01:13, Richard Michael wrote:
> Hello,
>
> I've just installed F20 beta x64 and applied all updates.
>
> I'm attempting to create a bridge network interface in virt-manager
> (0.10.0).  I complete the "Configure network interface" dialog, and
> when I click "Finish" I receive an "Input Error" with message:
>
> 'str' object has no attribute 'XMLDesc'
>
>
> A very similar error (when creating a bonded interface) is mentioned
> in comments #1 and #2 in a bug related to "system-config-services"
> here ...
>
> https://bugzilla.redhat.com/show_bug.cgi?id=1028833#c2
>
>  ... with the suggestion to file a bug against virt-manager.  I can't
> find a virt-manager bug related to this however.
>
>
> 1/ I'll open one unless anyone has other suggestions or comments?
>
>
> 2/ I'm new to virt-manager and wondering about a work-around; should I
> investigate using virsh to create the interface hoping virt-manager
> will detect it?
>

My work-around: Create bridge in NetworkManager (or directly edit config
files) and then add it to virt-manager. I always wondered what is this
whole bridge management in virt-manager for.


Thank you for the suggestion.  I looked at this, and interface creation using NetworkManager is quite different than in virt-manager.  Also, I'm unsure what you mean by "add it to virt-manager".  In virt-manager, I am only able to create a new interface, I can't find anything to allow adding an existing bridge.

I'll open a bug, as this problem renders virt-manager nearly unusable.  (It's impossible to create network interfaces.)

Regards,
Richard


Mateusz Marzantowicz

--
test mailing list
[hidden email]
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test


--
test mailing list
[hidden email]
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test
Reply | Threaded
Open this post in threaded view
|

Re: F20 beta virt-manager cannot create bridged network interface

Adam Williamson-3
On Mon, 2013-11-18 at 22:52 -0500, Richard Michael wrote:

>
>
>
> On Mon, Nov 18, 2013 at 7:18 PM, Mateusz Marzantowicz
> <[hidden email]> wrote:
>         On 19.11.2013 01:13, Richard Michael wrote:
>         > Hello,
>         >
>         > I've just installed F20 beta x64 and applied all updates.
>         >
>         > I'm attempting to create a bridge network interface in
>         virt-manager
>         > (0.10.0).  I complete the "Configure network interface"
>         dialog, and
>         > when I click "Finish" I receive an "Input Error" with
>         message:
>         >
>         > 'str' object has no attribute 'XMLDesc'
>         >
>         >
>         > A very similar error (when creating a bonded interface) is
>         mentioned
>         > in comments #1 and #2 in a bug related to
>         "system-config-services"
>         > here ...
>         >
>         > https://bugzilla.redhat.com/show_bug.cgi?id=1028833#c2
>         >
>         >  ... with the suggestion to file a bug against
>         virt-manager.  I can't
>         > find a virt-manager bug related to this however.
>         >
>         >
>         > 1/ I'll open one unless anyone has other suggestions or
>         comments?
>         >
>         >
>         > 2/ I'm new to virt-manager and wondering about a
>         work-around; should I
>         > investigate using virsh to create the interface hoping
>         virt-manager
>         > will detect it?
>         >
>        
>        
>         My work-around: Create bridge in NetworkManager (or directly
>         edit config
>         files) and then add it to virt-manager. I always wondered what
>         is this
>         whole bridge management in virt-manager for.
>        
>
>
> Thank you for the suggestion.  I looked at this, and interface
> creation using NetworkManager is quite different than in
> virt-manager.  Also, I'm unsure what you mean by "add it to
> virt-manager".  In virt-manager, I am only able to create a new
> interface, I can't find anything to allow adding an existing bridge.
>
>
> I'll open a bug, as this problem renders virt-manager nearly
> unusable.  (It's impossible to create network interfaces.)

I'm not entirely clear what you're trying to do here, but I'm still
using
http://www.linux-kvm.com/content/using-bridged-networking-virt-manager
as my basic set of instructions for setting up a bridged config for KVM.
If you just want your VMs to have internet access you don't need to do
anything special at all - you only need to fiddle with networking
configuration if you want them bridged rather than NAT'ed (so they
appear on your local network as if they were 'real' machines connected
to the router).
--
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net
http://www.happyassassin.net

--
test mailing list
[hidden email]
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test
Reply | Threaded
Open this post in threaded view
|

Re: F20 beta virt-manager cannot create bridged network interface

Mateusz Marzantowicz
In reply to this post by Richard Michael
On 19.11.2013 04:52, Richard Michael wrote:

>
>
>
> On Mon, Nov 18, 2013 at 7:18 PM, Mateusz Marzantowicz
> <[hidden email] <mailto:[hidden email]>> wrote:
>
>     On 19.11.2013 01:13, Richard Michael wrote:
>     > Hello,
>     >
>     > I've just installed F20 beta x64 and applied all updates.
>     >
>     > I'm attempting to create a bridge network interface in virt-manager
>     > (0.10.0).  I complete the "Configure network interface" dialog, and
>     > when I click "Finish" I receive an "Input Error" with message:
>     >
>     > 'str' object has no attribute 'XMLDesc'
>     >
>     >
>     > A very similar error (when creating a bonded interface) is mentioned
>     > in comments #1 and #2 in a bug related to "system-config-services"
>     > here ...
>     >
>     > https://bugzilla.redhat.com/show_bug.cgi?id=1028833#c2
>     >
>     >  ... with the suggestion to file a bug against virt-manager.  I can't
>     > find a virt-manager bug related to this however.
>     >
>     >
>     > 1/ I'll open one unless anyone has other suggestions or comments?
>     >
>     >
>     > 2/ I'm new to virt-manager and wondering about a work-around; should I
>     > investigate using virsh to create the interface hoping virt-manager
>     > will detect it?
>     >
>
>     My work-around: Create bridge in NetworkManager (or directly edit config
>     files) and then add it to virt-manager. I always wondered what is this
>     whole bridge management in virt-manager for.
>
>
> Thank you for the suggestion.  I looked at this, and interface creation
> using NetworkManager is quite different than in virt-manager.  Also, I'm
> unsure what you mean by "add it to virt-manager".  In virt-manager, I am
> only able to create a new interface, I can't find anything to allow
> adding an existing bridge.
>

I've found that creating new bridge and specifying existing bridge name
(like br0) has the same effect as "adding existing" one. I think that
virt-manager lacks auto-detect mechanism for configured system
connections. As a result, when you create new bridge but give the name
of existing one virt-manager starts to recognize it.

I agree that GUI support for bridging in NM is a bit rough but I'm
compensating this with text editor.



Mateusz Marzantowicz
--
test mailing list
[hidden email]
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test
Reply | Threaded
Open this post in threaded view
|

Re: F20 beta virt-manager cannot create bridged network interface

Chris Murphy
In reply to this post by Adam Williamson-3
A possible related problem is that 'yum groupinstall Virtualization' doesn't install everything that's needed. I had to manually install some qemu and libvirt packages including libvirt-daemon-driver-network before things were working correctly including bridged network interface.

Chris Murphy
--
test mailing list
[hidden email]
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test
Reply | Threaded
Open this post in threaded view
|

Re: F20 beta virt-manager cannot create bridged network interface

Adam Williamson-3
On Tue, 2013-11-19 at 10:26 -0700, Chris Murphy wrote:
> A possible related problem is that 'yum groupinstall Virtualization'
> doesn't install everything that's needed. I had to manually install
> some qemu and libvirt packages including libvirt-daemon-driver-network
> before things were working correctly including bridged network
> interface.

Have you filed a bug on this? I think they were trying to streamline the
deps so it didn't pull in a bunch of unnecessary stuff any more, but
sounds like maybe they went too far.
--
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net
http://www.happyassassin.net

--
test mailing list
[hidden email]
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test
Reply | Threaded
Open this post in threaded view
|

Re: F20 beta virt-manager cannot create bridged network interface

Richard Michael
In reply to this post by Adam Williamson-3
On Mon, Nov 18, 2013 at 11:05 PM, Adam Williamson <[hidden email]> wrote:

> On Mon, 2013-11-18 at 22:52 -0500, Richard Michael wrote:
>>
>>
>>
>> On Mon, Nov 18, 2013 at 7:18 PM, Mateusz Marzantowicz
>> <[hidden email]> wrote:
>>         On 19.11.2013 01:13, Richard Michael wrote:
>>         > Hello,
>>         >
>>         > I've just installed F20 beta x64 and applied all updates.
>>         >
>>         > I'm attempting to create a bridge network interface in
>>         virt-manager
>>         > (0.10.0).  I complete the "Configure network interface"
>>         dialog, and
>>         > when I click "Finish" I receive an "Input Error" with
>>         message:
>>         >
>>         > 'str' object has no attribute 'XMLDesc'
>>         >
>>         >
>>         > A very similar error (when creating a bonded interface) is
>>         mentioned
>>         > in comments #1 and #2 in a bug related to
>>         "system-config-services"
>>         > here ...
>>         >
>>         > https://bugzilla.redhat.com/show_bug.cgi?id=1028833#c2
>>         >
>>         >  ... with the suggestion to file a bug against
>>         virt-manager.  I can't
>>         > find a virt-manager bug related to this however.
>>         >
>>         >
>>         > 1/ I'll open one unless anyone has other suggestions or
>>         comments?
>>         >
>>         >
>>         > 2/ I'm new to virt-manager and wondering about a
>>         work-around; should I
>>         > investigate using virsh to create the interface hoping
>>         virt-manager
>>         > will detect it?
>>         >
>>
>>
>>         My work-around: Create bridge in NetworkManager (or directly
>>         edit config
>>         files) and then add it to virt-manager. I always wondered what
>>         is this
>>         whole bridge management in virt-manager for.
>>
>>
>>
>> Thank you for the suggestion.  I looked at this, and interface
>> creation using NetworkManager is quite different than in
>> virt-manager.  Also, I'm unsure what you mean by "add it to
>> virt-manager".  In virt-manager, I am only able to create a new
>> interface, I can't find anything to allow adding an existing bridge.
>>
>>
>> I'll open a bug, as this problem renders virt-manager nearly
>> unusable.  (It's impossible to create network interfaces.)
>
> I'm not entirely clear what you're trying to do here, but I'm still
> using
> http://www.linux-kvm.com/content/using-bridged-networking-virt-manager
> as my basic set of instructions for setting up a bridged config for KVM.
> If you just want your VMs to have internet access you don't need to do
> anything special at all - you only need to fiddle with networking
> configuration if you want them bridged rather than NAT'ed (so they
> appear on your local network as if they were 'real' machines connected
> to the router).

Thanks for your reply Adam.

Ah indeed, I should have thought of creating the bridge manually, as
discussed in the link you posted.  Following those instructions has
helped, virt-manager sees the manually bridge as a shareable physical
device.

Aside, I'm wondering if F20 should have already created a bridge for
libvirt (e.g., should I need to create it myself?).  I selected the
'Virtualization' group.  Perhaps this is related to Chris' down-thread
comment that not all required packages are in the group?

Thanks again!

Regards,
Richard

> --
> Adam Williamson
> Fedora QA Community Monkey
> IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net
> http://www.happyassassin.net
>
> --
> test mailing list
> [hidden email]
> To unsubscribe:
> https://admin.fedoraproject.org/mailman/listinfo/test
--
test mailing list
[hidden email]
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test
Reply | Threaded
Open this post in threaded view
|

Re: F20 beta virt-manager cannot create bridged network interface

Richard Michael
In reply to this post by Mateusz Marzantowicz
On Tue, Nov 19, 2013 at 4:21 AM, Mateusz Marzantowicz
<[hidden email]> wrote:

> On 19.11.2013 04:52, Richard Michael wrote:
>>
>>
>>
>> On Mon, Nov 18, 2013 at 7:18 PM, Mateusz Marzantowicz
>> <[hidden email] <mailto:[hidden email]>> wrote:
>>
>>     On 19.11.2013 01:13, Richard Michael wrote:
>>     > Hello,
>>     >
>>     > I've just installed F20 beta x64 and applied all updates.
>>     >
>>     > I'm attempting to create a bridge network interface in virt-manager
>>     > (0.10.0).  I complete the "Configure network interface" dialog, and
>>     > when I click "Finish" I receive an "Input Error" with message:
>>     >
>>     > 'str' object has no attribute 'XMLDesc'
>>     >
>>     >
>>     > A very similar error (when creating a bonded interface) is mentioned
>>     > in comments #1 and #2 in a bug related to "system-config-services"
>>     > here ...
>>     >
>>     > https://bugzilla.redhat.com/show_bug.cgi?id=1028833#c2
>>     >
>>     >  ... with the suggestion to file a bug against virt-manager.  I can't
>>     > find a virt-manager bug related to this however.
>>     >
>>     >
>>     > 1/ I'll open one unless anyone has other suggestions or comments?
>>     >
>>     >
>>     > 2/ I'm new to virt-manager and wondering about a work-around; should I
>>     > investigate using virsh to create the interface hoping virt-manager
>>     > will detect it?
>>     >
>>
>>     My work-around: Create bridge in NetworkManager (or directly edit config
>>     files) and then add it to virt-manager. I always wondered what is this
>>     whole bridge management in virt-manager for.
>>
>>
>> Thank you for the suggestion.  I looked at this, and interface creation
>> using NetworkManager is quite different than in virt-manager.  Also, I'm
>> unsure what you mean by "add it to virt-manager".  In virt-manager, I am
>> only able to create a new interface, I can't find anything to allow
>> adding an existing bridge.
>>
>
> I've found that creating new bridge and specifying existing bridge name
> (like br0) has the same effect as "adding existing" one. I think that
> virt-manager lacks auto-detect mechanism for configured system
> connections. As a result, when you create new bridge but give the name
> of existing one virt-manager starts to recognize it.

Yes, once I followed Adam's suggestion and created the bridge, it
appeared automatically (via detection) - both as a shareable device
during the steps of guest VM creation and also in the "Connection
details" / "Network interfaces" tab.

Thanks Mateusz!

Regards,
Richard


>
> I agree that GUI support for bridging in NM is a bit rough but I'm
> compensating this with text editor.
>
>
>
> Mateusz Marzantowicz
> --
> test mailing list
> [hidden email]
> To unsubscribe:
> https://admin.fedoraproject.org/mailman/listinfo/test
--
test mailing list
[hidden email]
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test
Reply | Threaded
Open this post in threaded view
|

Re: F20 beta virt-manager cannot create bridged network interface

Richard Michael
In reply to this post by Chris Murphy
On Tue, Nov 19, 2013 at 12:26 PM, Chris Murphy <[hidden email]> wrote:
> A possible related problem is that 'yum groupinstall Virtualization' doesn't install everything that's needed. I had to manually install some qemu and libvirt packages including libvirt-daemon-driver-network before things were working correctly including bridged network interface.

Thanks for your reply Chris.

Perhaps this explains why I don't have a bridge already and needed to
create one.  I do have 'libvirt-daemon-driver-network' installed
though.

Could you please post the names of the other RPMs you needed to
install?  Perhaps the output of 'rpm -qa | grep -E
"(kernel|qemu|virt-)"' would cover them.

Regards,
Richard

>
> Chris Murphy
> --
> test mailing list
> [hidden email]
> To unsubscribe:
> https://admin.fedoraproject.org/mailman/listinfo/test
--
test mailing list
[hidden email]
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test
Reply | Threaded
Open this post in threaded view
|

Re: F20 beta virt-manager cannot create bridged network interface

Chris Murphy
In reply to this post by Adam Williamson-3

On Nov 19, 2013, at 11:30 AM, Adam Williamson <[hidden email]> wrote:

> On Tue, 2013-11-19 at 10:26 -0700, Chris Murphy wrote:
>> A possible related problem is that 'yum groupinstall Virtualization'
>> doesn't install everything that's needed. I had to manually install
>> some qemu and libvirt packages including libvirt-daemon-driver-network
>> before things were working correctly including bridged network
>> interface.
>
> Have you filed a bug on this? I think they were trying to streamline the
> deps so it didn't pull in a bunch of unnecessary stuff any more, but
> sounds like maybe they went too far.

I haven't. I've been too lazy to find out exactly what packages are needed to get networking to work, so I've been brute forcing it by installing everything with qemu and libvirt in the name.


Chris Murphy
--
test mailing list
[hidden email]
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test
Reply | Threaded
Open this post in threaded view
|

Re: F20 beta virt-manager cannot create bridged network interface

Cole Robinson
In reply to this post by Chris Murphy
On 11/19/2013 12:26 PM, Chris Murphy wrote:
> A possible related problem is that 'yum groupinstall Virtualization' doesn't install everything that's needed. I had to manually install some qemu and libvirt packages including libvirt-daemon-driver-network before things were working correctly including bridged network interface.
>
> Chris Murphy
>

I fixed this in comps for f20+ in October, so this shouldn't be an issue anymore.

- Cole
--
test mailing list
[hidden email]
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test
Reply | Threaded
Open this post in threaded view
|

Re: F20 beta virt-manager cannot create bridged network interface

Cole Robinson
In reply to this post by Richard Michael
On 11/18/2013 07:13 PM, Richard Michael wrote:

> Hello,
>
> I've just installed F20 beta x64 and applied all updates.
>
> I'm attempting to create a bridge network interface in virt-manager
> (0.10.0).  I complete the "Configure network interface" dialog, and
> when I click "Finish" I receive an "Input Error" with message:
>
> 'str' object has no attribute 'XMLDesc'
>

Please file a virt-manager bug about this. Reproduce with virt-manager --debug
and attach the entire output.

Thanks,
Cole
--
test mailing list
[hidden email]
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test
Reply | Threaded
Open this post in threaded view
|

Re: F20 beta virt-manager cannot create bridged network interface

Adam Williamson-3
In reply to this post by Richard Michael
On Tue, 2013-11-19 at 13:35 -0500, Richard Michael wrote:

> Aside, I'm wondering if F20 should have already created a bridge for
> libvirt (e.g., should I need to create it myself?).  I selected the
> 'Virtualization' group.  Perhaps this is related to Chris' down-thread
> comment that not all required packages are in the group?

No, AIUI, it does not and would never do that out of the box: it
wouldn't really be appropriate for a package to go around screwing with
your network config to that extent. It is not safe to assume anyone
setting up 'virtualization' wants bridged networking; people who just
want to use virt-manager as a VirtualBox-alike are probably happy with
NATed networking.
--
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net
http://www.happyassassin.net

--
test mailing list
[hidden email]
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test
Reply | Threaded
Open this post in threaded view
|

Re: F20 beta virt-manager cannot create bridged network interface

Richard Michael
On Tue, Nov 19, 2013 at 4:11 PM, Adam Williamson <[hidden email]> wrote:

> On Tue, 2013-11-19 at 13:35 -0500, Richard Michael wrote:
>
>> Aside, I'm wondering if F20 should have already created a bridge for
>> libvirt (e.g., should I need to create it myself?).  I selected the
>> 'Virtualization' group.  Perhaps this is related to Chris' down-thread
>> comment that not all required packages are in the group?
>
> No, AIUI, it does not and would never do that out of the box: it
> wouldn't really be appropriate for a package to go around screwing with
> your network config to that extent. It is not safe to assume anyone
> setting up 'virtualization' wants bridged networking; people who just
> want to use virt-manager as a VirtualBox-alike are probably happy with
> NATed networking.

Yes, agreed ; although --

My installation did was missing the default local NAT network.
Reading the libvirt.org wiki just now, this should be "out of the
box".  I followed the instructions to create it and get NAT working.

Does the Fedora team expect this default network to be created?  If
yes, I wonder if:

a/ there is a missing a package from the "Virtualization" group
(probably not, given remarks elsewhere in the thread)

or

b/ a post-install script failure from an installed package failed to
import the default.xml file to initialize the virtual network

Aside, I don't want to hijack the Fedora test list for
libvirt/virt-manager issues.  Should I move this to another list?

Regards,
Richard


> --
> Adam Williamson
> Fedora QA Community Monkey
> IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net
> http://www.happyassassin.net
>
> --
> test mailing list
> [hidden email]
> To unsubscribe:
> https://admin.fedoraproject.org/mailman/listinfo/test
--
test mailing list
[hidden email]
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test
Reply | Threaded
Open this post in threaded view
|

Re: F20 beta virt-manager cannot create bridged network interface

Mateusz Marzantowicz
On 19.11.2013 22:25, Richard Michael wrote:

> On Tue, Nov 19, 2013 at 4:11 PM, Adam Williamson <[hidden email]> wrote:
>> On Tue, 2013-11-19 at 13:35 -0500, Richard Michael wrote:
>>
>>> Aside, I'm wondering if F20 should have already created a bridge for
>>> libvirt (e.g., should I need to create it myself?).  I selected the
>>> 'Virtualization' group.  Perhaps this is related to Chris' down-thread
>>> comment that not all required packages are in the group?
>>
>> No, AIUI, it does not and would never do that out of the box: it
>> wouldn't really be appropriate for a package to go around screwing with
>> your network config to that extent. It is not safe to assume anyone
>> setting up 'virtualization' wants bridged networking; people who just
>> want to use virt-manager as a VirtualBox-alike are probably happy with
>> NATed networking.
>
> Yes, agreed ; although --
>
> My installation did was missing the default local NAT network.
> Reading the libvirt.org wiki just now, this should be "out of the
> box".  I followed the instructions to create it and get NAT working.
>
> Does the Fedora team expect this default network to be created?  If
> yes, I wonder if:
>
> a/ there is a missing a package from the "Virtualization" group
> (probably not, given remarks elsewhere in the thread)
>
> or
>
> b/ a post-install script failure from an installed package failed to
> import the default.xml file to initialize the virtual network
>
> Aside, I don't want to hijack the Fedora test list for
> libvirt/virt-manager issues.  Should I move this to another list?
>


Something went wrong in your installation. NATed networking is created
and enabled on F20 by default. Personally I hate this, I don't use it
and always disable it but as Adam mentioned there are a lot of different
use cases and user's needs.

I don't thing there are any missing packages related to virtualization
now in Fedora 20. This is a false trail.



Mateusz Marzantowicz
--
test mailing list
[hidden email]
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test
Reply | Threaded
Open this post in threaded view
|

Re: F20 beta virt-manager cannot create bridged network interface

Eric Blake
On 11/19/2013 02:39 PM, Mateusz Marzantowicz wrote:

> Something went wrong in your installation. NATed networking is created
> and enabled on F20 by default. Personally I hate this, I don't use it
> and always disable it but as Adam mentioned there are a lot of different
> use cases and user's needs.

Actually, NATed networking is created ONLY if you install
libvirt-daemon-config-network.  If you don't want it installed by
default, then don't install that package.

--
Eric Blake   eblake redhat com    +1-919-301-3266
Libvirt virtualization library http://libvirt.org


--
test mailing list
[hidden email]
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test

signature.asc (634 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: F20 beta virt-manager cannot create bridged network interface

Richard Michael
On Tue, Nov 19, 2013 at 4:46 PM, Eric Blake <[hidden email]> wrote:

> On 11/19/2013 02:39 PM, Mateusz Marzantowicz wrote:
>
>> Something went wrong in your installation. NATed networking is created
>> and enabled on F20 by default. Personally I hate this, I don't use it
>> and always disable it but as Adam mentioned there are a lot of different
>> use cases and user's needs.
>
> Actually, NATed networking is created ONLY if you install
> libvirt-daemon-config-network.  If you don't want it installed by
> default, then don't install that package.

Ah ; yes, I see I do not have that package.

What is the expected user experience for virtual networking out of the
box on Fedora 20?  [Given they select the "Virtualization" group
during install.]

Regards,
Richard

>
> --
> Eric Blake   eblake redhat com    +1-919-301-3266
> Libvirt virtualization library http://libvirt.org
>
>
> --
> test mailing list
> [hidden email]
> To unsubscribe:
> https://admin.fedoraproject.org/mailman/listinfo/test
--
test mailing list
[hidden email]
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test
Reply | Threaded
Open this post in threaded view
|

Re: F20 beta virt-manager cannot create bridged network interface

Adam Williamson-3
On Tue, 2013-11-19 at 16:52 -0500, Richard Michael wrote:

> On Tue, Nov 19, 2013 at 4:46 PM, Eric Blake <[hidden email]> wrote:
> > On 11/19/2013 02:39 PM, Mateusz Marzantowicz wrote:
> >
> >> Something went wrong in your installation. NATed networking is created
> >> and enabled on F20 by default. Personally I hate this, I don't use it
> >> and always disable it but as Adam mentioned there are a lot of different
> >> use cases and user's needs.
> >
> > Actually, NATed networking is created ONLY if you install
> > libvirt-daemon-config-network.  If you don't want it installed by
> > default, then don't install that package.
>
> Ah ; yes, I see I do not have that package.
>
> What is the expected user experience for virtual networking out of the
> box on Fedora 20?  [Given they select the "Virtualization" group
> during install.]

I think this is the problem Chris Murphy wrote about as "a possible
related problem" and that Cole replied that he "fixed this in comps for
f20+ in October, so this shouldn't be an issue anymore" - that package
was not getting pulled in when you installed the Virtualization group,
but it was actually supposed to.
--
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net
http://www.happyassassin.net

--
test mailing list
[hidden email]
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test
Reply | Threaded
Open this post in threaded view
|

Re: F20 beta virt-manager cannot create bridged network interface

Richard Michael
On Tue, Nov 19, 2013 at 4:59 PM, Adam Williamson <[hidden email]> wrote:

> On Tue, 2013-11-19 at 16:52 -0500, Richard Michael wrote:
>> On Tue, Nov 19, 2013 at 4:46 PM, Eric Blake <[hidden email]> wrote:
>> > On 11/19/2013 02:39 PM, Mateusz Marzantowicz wrote:
>> >
>> >> Something went wrong in your installation. NATed networking is created
>> >> and enabled on F20 by default. Personally I hate this, I don't use it
>> >> and always disable it but as Adam mentioned there are a lot of different
>> >> use cases and user's needs.
>> >
>> > Actually, NATed networking is created ONLY if you install
>> > libvirt-daemon-config-network.  If you don't want it installed by
>> > default, then don't install that package.
>>
>> Ah ; yes, I see I do not have that package.
>>
>> What is the expected user experience for virtual networking out of the
>> box on Fedora 20?  [Given they select the "Virtualization" group
>> during install.]
>
> I think this is the problem Chris Murphy wrote about as "a possible
> related problem" and that Cole replied that he "fixed this in comps for
> f20+ in October, so this shouldn't be an issue anymore" - that package
> was not getting pulled in when you installed the Virtualization group,
> but it was actually supposed to.

I reviewed the /root/anaconda.cfg file and I didn't see a
@virtualization (or similar named) group in the %packages section ;
nor is there a "virtualization" group in "yum group list" output.  (I
notice as well that anaconda.cfg listed groups aren't one-to-one with
yum's groups, ex. '@firefox' in anaconda.cfg, but not in yum.)

Though, I do recall seeing an option related to virtualization during
install, and am fairly sure I selected it (I was installing
specifically to virtualize).

How can I confirm my installation choices?  How I can install the
"virtualization" group (if yum doesn't know about it)?

[I'm trying to check if the missing default virtual network is my
fault, not an F20 problem.]

Regards,
Richard

> --
> Adam Williamson
> Fedora QA Community Monkey
> IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net
> http://www.happyassassin.net
>
> --
> test mailing list
> [hidden email]
> To unsubscribe:
> https://admin.fedoraproject.org/mailman/listinfo/test
--
test mailing list
[hidden email]
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test