[Bug 893269] New: Yast>Install Hyper vision and Tool Selection of KVM /XEN Fails and Renders the PC with No Internet Connection
https://bugzilla.novell.com/show_bug.cgi?id=893269 https://bugzilla.novell.com/show_bug.cgi?id=893269#c0 Summary: Yast>Install Hyper vision and Tool Selection of KVM /XEN Fails and Renders the PC with No Internet Connection Classification: openSUSE Product: openSUSE 13.1 Version: Final Platform: x86-64 OS/Version: openSUSE 13.1 Status: NEW Severity: Major Priority: P5 - None Component: YaST2 AssignedTo: yast2-maintainers@suse.de ReportedBy: secure@aphofis.com QAContact: jsrain@suse.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Firefox/31.0 Yast>Install Hypervision and Tools>Next Select KVM starts to asks to create a Network Bridge then installs a few packages and asks the user to reboot to both finish and set user guest etc. Rebooted the PC manually and came back and repeated the above and asked again to reboot to install...PC now on and endless request/reboot. Yast>Install Hyervision and Tools>Next Select XEN and a network Bridge was created that moved the single static IP assignment to be the Bridge and nothing on the eth0...so the PC had no access to the Internet to install files from any repository leaving the user to reinstate a valid network connection to do anything more. Reverted to Yast>Software Management> Select the Group Hypervision for both XEN and KVM and proceeded. Reproducible: Always Steps to Reproduce: 1. 2. 3. Actual Results: Failed Expected Results: It should install the packages and create the Network connection for the actual VM when the selection is made to create the 1st VM as in 12.3 and as a short cut to simply using a package group if fails appallingly! Creation of a Network bridge that was the PC's static IP and leave the eth0 with nothing more than 0.0.0.0 -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=893269 https://bugzilla.novell.com/show_bug.cgi?id=893269#c Steffen Winterfeldt <snwint@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|yast2-maintainers@suse.de |carnold@suse.com -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=893269 https://bugzilla.novell.com/show_bug.cgi?id=893269#c1 Charles Arnold <carnold@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO CC| |carnold@suse.com InfoProvider| |secure@aphofis.com AssignedTo|carnold@suse.com |mfilka@suse.com --- Comment #1 from Charles Arnold <carnold@suse.com> 2014-09-11 21:52:13 UTC --- ((In reply to comment #0)
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Firefox/31.0
Yast>Install Hypervision and Tools>Next
Select KVM starts to asks to create a Network Bridge then installs a few packages and asks the user to reboot to both finish and set user guest etc.
Rebooted the PC manually and came back and repeated the above and asked again to reboot to install...PC now on and endless request/reboot.
Running 'Install Hypervision and Tools' subsequent times does prompt you to reboot even when everything is installed (it doesn't reinstall anything). This could be considered a bug, but it is harmless given that admins would already know if they have installed the necessary packages and rebooted. In 13.2, 'Install Hypervisior and Tools' has been rewritten and a reboot isn't required for KVM (it still is for Xen).
Yast>Install Hyervision and Tools>Next
Select XEN and a network Bridge was created that moved the single static IP assignment to be the Bridge and nothing on the eth0...so the PC had no access to the Internet to install files from any repository leaving the user to reinstate a valid network connection to do anything more.
The network bridge shouldn't need to be created (nor prompted to do so) if it was already properly created when KVM was added to the system. This may be the root of the problem although I don't see it in my testing. I wonder if manually stopping and starting the network makes a difference for you? The reassignment of the IP to the bridge should not have stopped you from accessing the outside network - assuming it was done correctly.
Expected Results: It should install the packages and create the Network connection for the actual VM when the selection is made to create the 1st VM as in 12.3 and as a short cut to simply using a package group if fails appallingly!
A virtual nic is created when a VM is started. The bridge is expected to be there before any VM is created. This is the same as 12.3. Setting up a bridge is best left to the admin of the host and not to the VM creation tools.
Creation of a Network bridge that was the PC's static IP and leave the eth0 with nothing more than 0.0.0.0
This is the way the underlying yast network code sets up a bridge (which yast2-vm calls). I'm not sure there is a bug here with regards to what happens to eth0 when setting up a bridge but passing this to the yast-network maintainer to respond. You will likely need to attach your y2logs to this bug. save_y2logs /tmp/y2logs.tgz -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=893269 https://bugzilla.novell.com/show_bug.cgi?id=893269#c2 Scott Couston <secure@aphofis.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |secure@aphofis.com --- Comment #2 from Scott Couston <secure@aphofis.com> 2014-09-12 10:55:58 EST --- (In reply to comment #1)
((In reply to comment #0)
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Firefox/31.0
Yast>Install Hypervision and Tools>Next
Select KVM starts to asks to create a Network Bridge then installs a few packages and asks the user to reboot to both finish and set user guest etc.
Rebooted the PC manually and came back and repeated the above and asked again to reboot to install...PC now on and endless request/reboot.
Running 'Install Hypervision and Tools' subsequent times does prompt you to reboot even when everything is installed (it doesn't reinstall anything). This could be considered a bug, but it is harmless given that admins would already know if they have installed the necessary packages and rebooted. In 13.2, 'Install Hypervisior and Tools' has been rewritten and a reboot isn't required for KVM (it still is for Xen).
That's the issue. Many Packages were installed/changed/modified..
Yast>Install Hyervision and Tools>Next
Select XEN and a network Bridge was created that moved the single static IP assignment to be the Bridge and nothing on the eth0...so the PC had no access to the Internet to install files from any repository leaving the user to reinstate a valid network connection to do anything more.
The network bridge shouldn't need to be created (nor prompted to do so) if it was already properly created when KVM was added to the system. This may be the root of the problem although I don't see it in my testing. I wonder if manually stopping and starting the network makes a difference for you?
The reassignment of the IP to the bridge should not have stopped you from accessing the outside network - assuming it was done correctly.
Expected Results: It should install the packages and create the Network connection for the actual
If there was network connectivity. I wouldn’t worry. After the Network bridge was installed the PC had neither Network nor Internet connectivity. Nothing!
VM when the selection is made to create the 1st VM as in 12.3 and as a short cut to simply using a package group if fails appallingly!
A virtual nic is created when a VM is started. The bridge is expected to be there before any VM is created. This is the same as 12.3. Setting up a bridge is best left to the admin of the host and not to the VM creation tools.
Creation of a Network bridge that was the PC's static IP and leave the eth0 with nothing more than 0.0.0.0
This is the way the underlying yast network code sets up a bridge (which yast2-vm calls). I'm not sure there is a bug here with regards to what happens to eth0 when setting up a bridge but passing this to the yast-network maintainer to respond.
You will likely need to attach your y2logs to this bug. save_y2logs /tmp/y2logs.tgz s
Sure. Any other Logs only too happy to provide. Can repeat the above on test LAN at any time. Logs in following updates to this -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠novell.com