Comment # 31 on bug 947229 from Mike Latimer

(In reply to Scott Couston from comment #30)
> I just did a fresh default KDE Installation on another X_86 PC and instead

Do you mean x86_64? (There are some places where x86 could be 586/686.)

> of going anywhere near software management, I only installed from menu.
> After installation a message said to reboot using the XEN option from the
> bootloader.
> 
> There was no XEN option in this installation as it did not change the
> bootloader menu at all.

As there was no XEN option, does that mean you are running a -default kernel
and just using KVM?

> None the less I was able to create a Virtual Machine without issue and
> installed Windows 7. Normally I dont let the software create a Network
> Bridge as there are no DHCP Services on my lan so at that part of the
> Installation I would normally say NO.
> 
> This time I did let it create a Network Bridge and the install was perfectly.
> The bug MUST have something to do with installing VM from Software
> Management AND then from Menu or visa versa..One of the installation types
> must install a different version of libvert.

The only conflicts I have found in your logs are related to the priority of the
local repo. With a high priority install repo, installing the patterns through
Software Management should work, but it will install the older libvirt
components. (LXC is not part of those patterns.) Using the Install Hypervisor
and Tools module would then try to install LXC (if selected) and bad things
could happen. Until we have other proof, I think all weird conflict issues were
due to this setup.

> I do have a local directory with the whole opensuse DVD contents configured
> in my software repos so the files for this install came from the DVD and not
> downloaded.

That's fine, as long as the priority is not higher than the update repo.

> Hope this helps.....The only BUG in this install IS THAT NO CHANGES WERE
> MADE TO THE BOOTLOADER FOR ZEN so give me a shout if you want the logs

Can you please create a new bug for this issue with the yast logs attached? (I
am not seeing this problem here.) I'd like to keep this bug specific to the
CD-ROM permissions issue.