|
Bugzilla – Full Text Bug Listing |
Created attachment 648805 [details]
XEN boot 2 of 2
Created attachment 648806 [details]
Default boot 1 of 2
Created attachment 648807 [details]
Default boot 2 of 2
Created attachment 648808 [details]
Xen boot 1 of 2
Created attachment 648809 [details]
XEN boot 2 of 2
Created attachment 648810 [details]
Yast logs
Created attachment 648812 [details]
Second PC tested same scenario 1 of 2
Second PC tested same scenario 1 of 2
Created attachment 648813 [details]
Second PC tested same scenario 1 of 2
Second PC tested same scenario 1 of 2
Thanks for the report, Scott. (In reply to Scott Couston from comment #0) > Installed pattern group from Yast VM and verified that 'libvirtd' was > installed - no Yast conflicts - Create Virtual Machines from wither a XEN > boot or normal default - Create Virtual Machines fails completely. > > See attached error responses and yast Logs...who tests this? openSUSE does get extensive testing, but there is always a chance for some variation in environment to cause a significant issue (which seems to be the case here). I'd like to determine exactly what went wrong, so we can both fix the issue, and make sure your use case is covered by our testing. I am looking through the logs now, but would appreciate a few more bits of data: - Is this a fresh installation on bare metal, or an upgrade? If an upgrade, what version did you upgrade from? - When you received the initial "unable to connect to libvirt" error, did you ensure the libvirtd daemon was running (systemctl status libvirtd)? - Was the machine unpatched, fully patched or somewhere in between prior to installing the Virtualization pattern? - The error on the second machine is a bit different. Was it installed any differently? I'll set this up from scratch and see if I can duplicate your errors here. All of the screenshots and logs through comment 6 are due to libvirtd not running. Virtualization components are contained in the following two installation patterns: Xen Virtual Machine Host Server KVM Host Server Using Software Management to install the components in this way is similar to simply installing the required RPMs. No additional configuration (such as setting up a bridge, or enabling the daemons) is performed. This was an intentional choice by the openSUSE community, who did not want the daemons enabled by default. After installing the virtualization components using this method, the following commands must be used to enable libvirtd: systemctl start libvirtd (to start the daemon) systemctl enable libvirtd (to enable the daemon on subsequent server restarts) Rather than installing the components through Software Management patterns, the recommended method is to use the YaST | Virtualization | Install Hypervisor and Tools module. This module allows you to select and install the required components. After the packages are installed, additional configuration (including the creation of a bridge, and enabling the libvirt daemon) is performed. The screenshot from comment 7 appear to show bug 933242, and the y2logs from comment 8 show that virt-manager version 1.0.1-14.4.1 is in use. Updating to the latest version in the openSUSE 13.2 update channel should resolve this issue. Created attachment 648985 [details]
After software upgrade as discussed prior
Created attachment 648986 [details]
conficts reports
All the conflicts seem to be related to the new version of libvert daemon....Ive provided the full conflict txt file 4 u
I can understand the convenience of having installing virtualisation from menu rather than Yast, however as a product, we duplicate so many things. We have Apper and Yast Online Update....Apper cant always resolve dependency issues. We have the KDE control Module AND Yast rather than one cohesive force and Ive unfortunately been around sine v9.0 It just seems to me that our product become more fractured and dispersed rather than one cohesive package. (yes understand the amalgamation of KDE/Gnome >> Opensuse Let me know if you need further info (In reply to Scott Couston from comment #12) > Created attachment 648985 [details] > After software upgrade as discussed prior Isn't this the issue you reported in bug 947242? If so, I'd prefer to keep the conflicts issue separate from the daemon not starting automatically. (In reply to Scott Couston from comment #14) > I can understand the convenience of having installing virtualisation from > menu rather than Yast, however as a product, we duplicate so many things. > We have Apper and Yast Online Update....Apper cant always resolve dependency > issues. > > We have the KDE control Module AND Yast rather than one cohesive force and > Ive unfortunately been around sine v9.0 > > It just seems to me that our product become more fractured and dispersed > rather than one cohesive package. (yes understand the amalgamation of > KDE/Gnome >> Opensuse (As above, I'll leave the conflict resolution/dependency question for the other bug.) Your points are valid, but the Virtualization section in YaST does much more than just install RPMs. Likewise, the Software Manager tool should not be involved with bridge creation, etc... Obviously you are concerned about fragmentation more than just on the virt side. However, Bugzilla is not a great place for this discussion as the participants are very limited. If you'd like to continue this discussion with the rest of the community, I'd recommend using the openSUSE mailing lists. (In reply to Scott Couston from comment #13) > Created attachment 648986 [details] > conficts reports > > All the conflicts seem to be related to the new version of libvert > daemon....Ive provided the full conflict txt file 4 u I didn't get a chance to go through this today, but will tomorrow (in bug 947242). Are the issues raised in this specific bug resolved? Mike me comments about the necessary separation of things like apper and yast online update were just part of the conversation as it would appear to me that the conflicts could all be resolved if the menu usage to adding software was part of the pattern group in Yast...but no matter. As far as bug 947242 goes I've added it as a dependency as it would appear that once we resolve the conflict in libvert the condition as tested still was present. I only had to open the bug in respect to libvert after using the menu and not Yast to install other tools etc. Yes I understand the menu software does other things like creating a network bridge...cheers and regards from OZ Created attachment 649141 [details]
PC2 Part sucessfull Installation - Eronious error as DVD IS readable
Please request any further other syupporting files for test PC2...were getting closer.
If its any consolation Virtual Box as installed from 13.2 doesnt work either but thats another bug
Created attachment 649161 [details]
New Installation. No VM software installed from Yast - onlu menu system - Issue is libvert version conflict
Created attachment 649164 [details]
error in brand new fresh kde install on test pc3 1 of 2
Created attachment 649165 [details]
error in brand new fresh kde install on test pc3 2 of 2
(In reply to Scott Couston from comment #19) > Created attachment 649161 [details] > New Installation. No VM software installed from Yast - onlu menu system - > Issue is libvert version conflict I can't yet explain why you are seeing this. I've done several installations of 13.2 and have not seen this problem. I may just be performing different steps than you. Can you provide the answers to the following questions? - Are you installing the x86_64 bit version of 13.2? - Are you performing a CD or network based installation? If network based, are you using the public mirrors, or a local source? - During the installation, are you selecting to use the update repo during the install? - After the installation, are you going directly to YaST|Virtualization|Install Hypervisor and Tools? If so, what options are you selecting in that screen? I'll try to reproduce this again as soon as I have more details. I performed the 64bit installation. Firstly I installed Hypervision from Software Management and then from menu. There was an update to libvert via online update Sorry the default install wa 64 bit from DVD (In reply to Scott Couston from comment #24) > Sorry the default install wa 64 bit from DVD I still cannot duplicate this. I just installed from DVD and installing the hypervisor does not result any conflicts. However, this bug is confusing. (In reply to Scott Couston from comment #19) > Created attachment 649161 [details] > New Installation. No VM software installed from Yast - onlu menu system - > Issue is libvert version conflict In the above attachment, the error is: libvirt-daemon-lxc-1.2.9-23.1.x86_64 requires libvirt-daemon = 1.2.9-23.1.x86_64 uninstallable providers: libvirt-daemon-1.2.9-23.1.i586[repo-update] libvirt-daemon-1.2.9-23.1.x86_64[repo-update] This is the issue I'd like to resolve first. Once we explain this, I'll look further into the second problem, which is the 'permission denied' issue when attempting to use the CD-ROM. Can you please provide exact details on how to see the above error? Sure Mike. Go to Yast>Software Management>View>Patterns and select both Zen and Kvm>Install. Try and see of hypervision create Virtual Machine works. Next from the Menu Install Zen or KVM> Install All Options The error should be then evident...arnt their many details in the yast logs I sent you that indicate order of installation or do you need other log files Thanks Mike Mike you may need t do a online update as I think their was an update to livert Scott (In reply to Scott Couston from comment #21) > Created attachment 649165 [details] > error in brand new fresh kde install on test pc3 2 of 2 These y2logs do not show the conflict problem I just explained in bug 947242, so I am assuming that conflicts were not seen and you only have the CD-ROM permissions issue here? (In reply to Scott Couston from comment #19) > Created attachment 649161 [details] > New Installation. No VM software installed from Yast - onlu menu system - > Issue is libvert version conflict As far as I can tell, I don't have YaST logs from this screenshot - although it seems to be the same issue as bug 947242, so please follow the advice there. I'll focus only on the CD-ROM permission issue in this bug. I just did a fresh default KDE Installation on another X_86 PC and instead 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. 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. 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. 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 Scott (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. (In reply to Scott Couston from comment #20) > Created attachment 649164 [details] > error in brand new fresh kde install on test pc3 1 of 2 The error in this screenshot is referring to being unable to access KVM kernel modules due to "permission denied". I have been unable to duplicate this, but it could have been due to the some mismatch of packages. (In reply to Scott Couston from comment #18) > Created attachment 649141 [details] > PC2 Part sucessfull Installation - Eronious error as DVD IS readable > > Please request any further other syupporting files for test PC2...were > getting closer. > If its any consolation Virtual Box as installed from 13.2 doesnt work either > but thats another bug This is a different error: "permission denied" for /var/media/server/GSP1RMCHPXFRE0_EN_DVD/autorun.inf. It is not clear if this is under Xen or KVM. It is also not clear if virt-manager is being ran as a normal user or as the root user. In either case, the referenced /var/media/server... device could have been in use by another user. In order to investigate either of the above errors, we need the ~/.cache/virt-manager/virt-manager.log file. It should tell us what virt-manager encountered. In addition to this, an `rpm -qa` output, and `cat /proc/mounts` will also help answer some of the questions we have. Closing due to no response. (I believe all the issues were resolved through configuration changes and bug 947242.) (Clearing needinfo) |
Created attachment 648804 [details] VM Boot 1 of 2 Installed pattern group from Yast VM and verified that 'libvirtd' was installed - no Yast conflicts - Create Virtual Machines from wither a XEN boot or normal default - Create Virtual Machines fails completely. See attached error responses and yast Logs...who tests this?