CentOS 6.5 and Hyper-V - Video Corruption During LiveCD Boot

Notice: Page may contain affiliate links for which we may earn a small commission through services like Amazon Affiliates or Skimlinks.

Patrick

Administrator
Staff member
Dec 21, 2010
12,512
5,800
113
Trying to build a test platform for the STHbench.sh script and as part of it decided to fire up CentOS 6.5 LiveCD and LiveDVD. Did all of the major items such as giving the system more than 2048MB of RAM and etc. The boot process starts out fine then I am getting video corruption prior to entering the desktop. Here is a quick video:

[video=youtube_share;p8C22p3EKKw]http://youtu.be/p8C22p3EKKw[/video]

Any thoughts/ ideas on how to fix?

Update: Tried in text only mode:
Kernel panic - not syncing: Fatal exception
Pid: 151, comm: plymouthd Tainted: G D ------------ 2.6.32-431.el6.x86_64 #1
Potential workaround: In the 10 second boot countdown hit a key and instead of booting to the LiveCD or LiveDVD, select "Install". You can install CentOS 6.5 and it runs without issue in Windows 8.1 Hyper-V.
 

PigLover

Moderator
Jan 26, 2011
3,185
1,545
113
Very interesting! I just gave it a shot and got the same results. Odd...

6.3 works quite well on Hyper-V. Never tried 6.4.
 

Patrick

Administrator
Staff member
Dec 21, 2010
12,512
5,800
113
Had the CentOS 6.4 LiveDVD ISO on the network. Booted right up. Very interesting.
 

Jeggs101

Well-Known Member
Dec 29, 2010
1,529
241
63
I tried it also. CentOS 6.5 LiveCD and LiveDVD on a Xeon E5 processor Windows 8.1 Pro host. Same result.

Should mention - I tried one at 2048MB and 1 processor and one at 4096MB and 4 processors. Neither worked
 

Patrick

Administrator
Staff member
Dec 21, 2010
12,512
5,800
113
Posted a workaround. You can use the LiveCD and LiveDVD to install, then boot from the installed CentOS 6.5 version
 

DolphinsDan

Member
Sep 17, 2013
90
6
8
That's really odd. I just fired one up. The Gen2 Hyper-V machine didn't even get past the post screen without errors. The Gen1 did the exact same thing but I could get to the installer like you mentioned.

Did you file a bug?