Bug 1396017 - unable to install f24 livecd to f25 host machine
Summary: unable to install f24 livecd to f25 host machine
Keywords:
Status: CLOSED DUPLICATE of bug 1337919
Alias: None
Product: Fedora
Classification: Fedora
Component: virt-manager
Version: 25
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Cole Robinson
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-11-17 09:15 UTC by lnie
Modified: 2017-03-30 13:36 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-03-30 13:36:07 UTC
Type: Bug

Attachments (Terms of Use)
hang screenshot (62.78 KB, image/png)
2016-11-17 09:15 UTC, lnie 		no flags Details
journal (23.29 KB, text/x-vhdl)
2016-11-17 09:16 UTC, lnie 		no flags Details
screenshot with qemu-kvm (172.00 KB, image/png)
2016-11-17 09:17 UTC, lnie 		no flags Details
debug output (36.13 KB, text/plain)
2016-12-23 02:55 UTC, lnie 		no flags Details
screenshot (57.13 KB, image/png)
2017-03-13 03:06 UTC, lnie 		no flags Details
screencast (1.60 MB, application/octet-stream)
2017-03-13 03:11 UTC, lnie 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Description lnie 2016-11-17 09:15:35 UTC 
Created attachment 1221505 [details]
hang screenshot

Description of problem:

Try to install Fedora-Workstation-Live-x86_64-24 to the virtual machine on f25 host using virt-manager, system hangs,and failed to boot into Welcome page.
The same installer works fine with qemu-kvm.
Not sure this is the right place to report,please feel free to reassign,thanks. 

Version-Release number of selected component (if applicable):
virt-manager-1.4.0-4.fc25.noarch

How reproducible:
always

Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:
Comment 1 lnie 2016-11-17 09:16:20 UTC 
Created attachment 1221506 [details]
journal
Comment 2 lnie 2016-11-17 09:17:26 UTC 
Created attachment 1221508 [details]
screenshot with qemu-kvm
Comment 3 Cole Robinson 2016-12-21 21:57:59 UTC 
This is working fine with up to date fedora 25. Can you still reproduce? If so, please provide virt-manager --debug output when reproducing
Comment 4 lnie 2016-12-23 02:53:20 UTC 
Haven't seen any change,so I'm going to attach the output with virt-manager-1.4.0-5.fc25.noarch.
Comment 5 lnie 2016-12-23 02:55:15 UTC 
Created attachment 1234944 [details]
debug output
Comment 6 Cole Robinson 2017-03-02 18:57:34 UTC 
Hmm, looking at the guest config, you may need to give it more ram, try 2 gb at least. Booting from the live CD is ram intensive.
Comment 7 lnie 2017-03-13 03:05:55 UTC 
(In reply to Cole Robinson from comment #6)
> Hmm, looking at the guest config, you may need to give it more ram, try 2 gb
> at least. Booting from the live CD is ram intensive.

As shown in the attached screenshot and video,2GB doesn't help.Both f25 and f26 livecd can boot successfully with the same ram size given(1224M).
Comment 8 lnie 2017-03-13 03:06:36 UTC 
Created attachment 1262306 [details]
screenshot
Comment 9 lnie 2017-03-13 03:11:29 UTC 
Created attachment 1262307 [details]
screencast
Comment 10 Cole Robinson 2017-03-16 17:46:42 UTC 
Actually I can reproduce some weirdness on a different machine, not your errors but gnome-shell repeatedly crashes in the VM, see guest dmesg output. Seems related to host CPU, we both have a Skylake, I have an intel 6700 and there's similar non-virt reports elsewhere. So a workaround may be to do CPU->Clear CPU Configuration, install the VM, update the kernel, then switch the CPU to skylake or host-model.

If that's the case, please dupe to bug 1337919
Comment 11 lnie 2017-03-30 13:36:07 UTC 
Clear CPU Confiquration dose works,though after update the kernel of the newly installed system and switch the cpu back to skylake-client,the VM failed to boot with the same symptom as shown in attachment1262307 [details].
Gonna to dupe it and sorry for the delay response:)

*** This bug has been marked as a duplicate of bug 1337919 ***
Note You need to log in before you can comment on or make changes to this bug.