Ubuntu

Unable to complete Canonical Desktop Ubuntu 14.04 installation in Hyper-V for Windows 10

Asked by Dave Gonsalves

I've reviewed similar problems previously posted on the Ubuntu Community Forums, but none of the answers seemed pertinent/helpful to my situation. I also posted my request for help on Ask Ubuntu (UserID: DaveG) on 10/5/15 (as copied below) ... so far, I've received no answers. Can someone at Canonical please help?

Trying to install Canonical Desktop Ubuntu 14.04.3 O/S as virtual machine under Hyper-V on Windows Pro 10 (64 bit). Stuck on the "Creating ext4 file system ..." step. Command line feedback indicates installation process is at a point where avahi-daemon has "received an invalid response packet from host at 192.168.1.77." Not sure if this "invalid response ...", itself, is the show stopper?

Tried to temporarily stop the avahi-daemon on the command line as follows: Service avahi-daemon stop.
No success. I've reviewed similar Q&A by others but, so far, haven't found the exchanges helpful. Any recommendations on how to resolve this stall?

Tags: 14.04 ; software-installation ; windows-10 ; hyper-v

Question information

Language:
English Edit question
Status:
Solved
For:
Ubuntu Edit question
Assignee:
No assignee Edit question
Solved by:
Dave Gonsalves
Solved:
Last query:
Last reply:
Revision history for this message
actionparsnip (andrew-woodhead666) said : 		#1

Have you checked guides on YouTube?
Did you MD5 test the ISO you downloaded?

Revision history for this message
Dave Gonsalves (dpgonsalves) said : 		#2

Thanks for the helpful suggestions! I downloaded the .iso from the Canonical site. Nevertheless, the MD5 checksum for the downloaded .iso does not match the checksum published on Ask Ubuntu, so it appears that the file may have got corrupted during download. I'll do some further cross-verification, perhaps using SHA1, then try downloading again. Then, I'll update this Question.

Revision history for this message
actionparsnip (andrew-woodhead666) said : 		#3

I suggest using torrents. Just because you get it from Ubuntu's official website doesn't mean it won't transfer without issue. Why did you not test the ISO before you used it?

Revision history for this message
Dave Gonsalves (dpgonsalves) said : 		#4

I've now verified that the wubi.exe file checksums (MD5 & SHA1) for my copy MATCH the checksum values for the 14.04.3 wubi published on Ask Ubuntu, so there was no corruption there. I suspect that the earlier checksum mismatches for my copy of the .iso may stem from differences between the Canonical distribution and whatever distribution was used to generate the checksum values published on Ask Ubuntu.
Q272124.2 Is there any way to specifically obtain the Canonical .iso distribution checksums? (I could download again & then compare checksums for the initial .iso copy with the 2nd copy? (however the initial .iso download took several hours, so this approach could be very unproductive!)
While I wait for any further recommendations on validating the .iso MD5 checksum value, I'll review the YouTube guides - as you suggested.
Also, while writing the above I saw your recommendation to try alternative (u)Torrent download ... in process. Thanks!

Revision history for this message
actionparsnip (andrew-woodhead666) said : 		#5

https://help.ubuntu.com/community/UbuntuHashes

Revision history for this message
actionparsnip (andrew-woodhead666) said : 		#6

The torrent protocol adds a lot of data checks so MD5 isn't really needed but doesn't hurt to test.

Revision history for this message
Dave Gonsalves (dpgonsalves) said : 		#7

I really appreciate your prompt suggestions! I'll keep Q272124 open until I'm able to resolve the primary issue: a successful O/S install ... you've helped me make progress!

Revision history for this message
Dave Gonsalves (dpgonsalves) said : 		#8

I'm happy to report that I was able to install Ubuntu Desktop successfully under Hyper-V! There was no problem with my downloaded .iso file. After viewing similar installations on YouTube I concluded that my installation process was sound. During the OS installation phase the Hyper-V processor activity indicator remains at 0% for very long periods ... most likely that made me too impatient. Thanks for your help!