So, um, yeah...it's April now, this bug has been open for nearly two months, and Hardy is going to be officially released soon. Considering KVM support is one of the touted new features, I would hope this bug is fixed before it is released. Not holding my breath... I'm on a fresh up-to-date Hardy install and this bug is still around. From my understanding, it is because of a newer version of dbus. Looking at the patch mentioned above, it doesn't look like it would be too complicated to fix. I'm assuming dbus is also the cause of me not being able to select an installation media when creating a new VM. That's a pretty big deal! Am I supposed to convert everything to an ISO? That's not very user friendly. It's unfortunate that CentOS and Fedora 8 both suffer from this (well, they work until you run all the updates) and I had high hopes that Hardy would fix this. I mean, it's kind of a hard bug to miss... and it doesn't seem that hard to fix. It kind of makes me feel like the people putting these packages out do no more than click on the app and say "Yep, it opened. That means it works". I'd fix it if I new enough about how dbus works.
Sorry if this came across as a rant, but it's just frustrating when my company is trying to move towards virtualizing as much as they can and not a single Linux distro can get virt-manager running properly. Yes, I understand there's a command line, but we NEED a GUI since not everyone here is a Linux expert. -- virt-manager does not detect bridge br0 https://bugs.launchpad.net/bugs/192605 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
