|
Bugzilla – Full Text Bug Listing |
| Summary: | uml installation via yast module broken | ||
|---|---|---|---|
| Product: | [openSUSE] SUSE LINUX 10.0 | Reporter: | Thomas Blume <thomas.blume> |
| Component: | YaST2 | Assignee: | Ladislav Slezák <lslezak> |
| Status: | RESOLVED WONTFIX | QA Contact: | Klaus Kämpf <kkaempf> |
| Severity: | Normal | ||
| Priority: | P5 - None | ||
| Version: | Beta 1 | ||
| Target Milestone: | --- | ||
| Hardware: | Other | ||
| OS: | All | ||
| Whiteboard: | |||
| Found By: | Other | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
Issues still exists in beta2. Gerd, do you know about this? #1: This is Ladislav's ;) #2: Yep, the network setup is a bit hackish. To make that work reliable we'll need support to setup bridge devices in the network start scripts (which isn't there yet, at least it wasn't in 9.3). Xen has the same issue btw. Not sure why it broke though, IMHO "ifup eth0" should work just fine with eth0 being a bridge device ... #3: This probably is hwinfo, I'd suspect the vmware test again :-/ UML support has been dropped => WONTFIX |
uml installation via yast module fails for several reasons: 1. For uml the system want's to instal xf86tools. In 10.0 this has been replaced by x11-tools. 2. The uml network setup seems to kill the normal network configuration after changing eth0 to hweth0 eth0 is not set up anymore and the logs say: ifup: No configuration found for eth0 The host system is then cut from the network. 3. The xterm for the uml kernel starts but hangs then on: Starting hardware detection.... > sys.1: cpu Probably some or all of the problems are connected. I just report them all for completeness.