Timeline for Create virbr0 for virsh
Current License: CC BY-SA 3.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jan 30, 2017 at 1:08 | history | edited | dyasny | CC BY-SA 3.0 | added 361 characters in body |
| Jan 30, 2017 at 1:06 | comment | added | dyasny | This is probably a bug in your build of libvirt. I am adding an example of a working interface definition you can try yourself. The brctl output seems to be in good order | |
| Jan 29, 2017 at 8:24 | comment | added | Igor Artamonov | not sure what you mean by attach it to br0. I've tried to create simple VM without networking, but if I edit its xml and add bridge network (there's example in the question) it failed to run. I don't know about other way to attach it to br0. I'll try virt-builder, thanks | |
| Jan 28, 2017 at 15:46 | comment | added | dyasny | try to simply create a VM with virt-manager and attach it to br0, see if that works. If it does, I'd simply stick to the manual creation way, or if you really need automation, use virt-builder instead of virt-install. It's way less buggy, especially and that's important on non-RH distros that don't really do any quality testing like Debian | |
| Jan 28, 2017 at 5:56 | comment | added | Igor Artamonov | Do you know any way to debug it? virsh logs/output are non-informative, and Transport endpoint is not connected doesn't give any clue. -d 0 doesn't provide additional log to that error message | |
| Jan 27, 2017 at 19:05 | comment | added | dyasny | I use this all the time on RHEL, you might be running into a Debian specific bug. | |
| Jan 27, 2017 at 17:36 | comment | added | Igor Artamonov | Tried, same result, same error. So maybe it's not because of non-existing virbr0, but something else related to that bridge? because it works without specifying --network option. Something is wrong there, but Transport endpoint is not connected doesn't make it clear | |
| Jan 27, 2017 at 17:09 | history | answered | dyasny | CC BY-SA 3.0 |