Migrating CentOS to Hyper-V fails to boot GNOME
up vote
0
down vote
favorite
Centos Version: 7.5.1804 Kernel: 3.10.0-862.14.4.el7.x86_64
I have prepared a CentOS VM using virtual box on an internet connected machine and imported it onto a network without internet connectivity. Apologies that the log messages that I’m writing out are manually typed so they might not be as explicit I’d like. Please ask if you need any more info.
The new network uses Hyper-V on Windows Server 2012. When I initially booted the machine I received the Dracut prompt so I booted from the rescue disk and re-initialised the initramfs image for the current kernel.
Dracut –f –v /boot/initramfs-3.10.0-862.14.4.el7.x86_64.img 3.10.0-862.14.4.el7.x86_64 --add-drivers "hv_vmbus hv_storvsc hv_netvsc hv_utils hv_balloon hyperv-keyboard hyperv_fb hid-hyperv
(Found on Centos Forums)
After this the boot sequence got a lot further but seems to hang when initialising the UI.
I am able to press Ctrl-Alt F2 to get to a console log in and sign in as my user or as root. If I try to run startx the screen flicker and returns with information about xorg. Looking in the logs it appear that the machine can’t find a display.
<EE> open /dev/dri/card0 no such file or directory
Falling back on old probe method
<EE> screen 0 deleted because of no matching config section
I’ve done a little googling, most of which seems to point towards the .Xauthority and .xinitrc files, both of which are empty under my user home.
I’m feeling a little out of my depth on this one, I’ve not used hyper-v before and I’ve not had these kind of issue when migrating an image before, granted that experience is fairly limited.
Apologies if the information is a little scarce, but I can’t copy the logs back off the other machine. If I can provide any more information that would be helpful, please just ask.
UPDATE:
Running X --configure gives the following error
<EE> Backtrace
0: X (xorg_backtrace=0x55) <ram address>
1: <ram address> <ram address>
2. /lib64/libpthread.so.0 <ram address>
Segmentation fault at address 0x0
Fatal Server error
Caught signal 11 Segmentation fault. Server Aborting
virtual-machine xorg gnome hyper-v centos-7
asked Nov 20 at 9:28
Sam Brett
12
New contributor
Sam Brett is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
up vote
0
down vote
favorite
Centos Version: 7.5.1804 Kernel: 3.10.0-862.14.4.el7.x86_64
I have prepared a CentOS VM using virtual box on an internet connected machine and imported it onto a network without internet connectivity. Apologies that the log messages that I’m writing out are manually typed so they might not be as explicit I’d like. Please ask if you need any more info.
The new network uses Hyper-V on Windows Server 2012. When I initially booted the machine I received the Dracut prompt so I booted from the rescue disk and re-initialised the initramfs image for the current kernel.
Dracut –f –v /boot/initramfs-3.10.0-862.14.4.el7.x86_64.img 3.10.0-862.14.4.el7.x86_64 --add-drivers "hv_vmbus hv_storvsc hv_netvsc hv_utils hv_balloon hyperv-keyboard hyperv_fb hid-hyperv
(Found on Centos Forums)
After this the boot sequence got a lot further but seems to hang when initialising the UI.
I am able to press Ctrl-Alt F2 to get to a console log in and sign in as my user or as root. If I try to run startx the screen flicker and returns with information about xorg. Looking in the logs it appear that the machine can’t find a display.
<EE> open /dev/dri/card0 no such file or directory
Falling back on old probe method
<EE> screen 0 deleted because of no matching config section
I’ve done a little googling, most of which seems to point towards the .Xauthority and .xinitrc files, both of which are empty under my user home.
I’m feeling a little out of my depth on this one, I’ve not used hyper-v before and I’ve not had these kind of issue when migrating an image before, granted that experience is fairly limited.
Apologies if the information is a little scarce, but I can’t copy the logs back off the other machine. If I can provide any more information that would be helpful, please just ask.
UPDATE:
Running X --configure gives the following error
<EE> Backtrace
0: X (xorg_backtrace=0x55) <ram address>
1: <ram address> <ram address>
2. /lib64/libpthread.so.0 <ram address>
Segmentation fault at address 0x0
Fatal Server error
Caught signal 11 Segmentation fault. Server Aborting
virtual-machine xorg gnome hyper-v centos-7
asked Nov 20 at 9:28
Sam Brett
12
New contributor
Sam Brett is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
Centos Version: 7.5.1804 Kernel: 3.10.0-862.14.4.el7.x86_64
I have prepared a CentOS VM using virtual box on an internet connected machine and imported it onto a network without internet connectivity. Apologies that the log messages that I’m writing out are manually typed so they might not be as explicit I’d like. Please ask if you need any more info.
The new network uses Hyper-V on Windows Server 2012. When I initially booted the machine I received the Dracut prompt so I booted from the rescue disk and re-initialised the initramfs image for the current kernel.
Dracut –f –v /boot/initramfs-3.10.0-862.14.4.el7.x86_64.img 3.10.0-862.14.4.el7.x86_64 --add-drivers "hv_vmbus hv_storvsc hv_netvsc hv_utils hv_balloon hyperv-keyboard hyperv_fb hid-hyperv
(Found on Centos Forums)
After this the boot sequence got a lot further but seems to hang when initialising the UI.
I am able to press Ctrl-Alt F2 to get to a console log in and sign in as my user or as root. If I try to run startx the screen flicker and returns with information about xorg. Looking in the logs it appear that the machine can’t find a display.
<EE> open /dev/dri/card0 no such file or directory
Falling back on old probe method
<EE> screen 0 deleted because of no matching config section
I’ve done a little googling, most of which seems to point towards the .Xauthority and .xinitrc files, both of which are empty under my user home.
I’m feeling a little out of my depth on this one, I’ve not used hyper-v before and I’ve not had these kind of issue when migrating an image before, granted that experience is fairly limited.
Apologies if the information is a little scarce, but I can’t copy the logs back off the other machine. If I can provide any more information that would be helpful, please just ask.
UPDATE:
Running X --configure gives the following error
<EE> Backtrace
0: X (xorg_backtrace=0x55) <ram address>
1: <ram address> <ram address>
2. /lib64/libpthread.so.0 <ram address>
Segmentation fault at address 0x0
Fatal Server error
Caught signal 11 Segmentation fault. Server Aborting
virtual-machine xorg gnome hyper-v centos-7
asked Nov 20 at 9:28
Sam Brett
12
New contributor
Sam Brett is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
Centos Version: 7.5.1804 Kernel: 3.10.0-862.14.4.el7.x86_64
I have prepared a CentOS VM using virtual box on an internet connected machine and imported it onto a network without internet connectivity. Apologies that the log messages that I’m writing out are manually typed so they might not be as explicit I’d like. Please ask if you need any more info.
The new network uses Hyper-V on Windows Server 2012. When I initially booted the machine I received the Dracut prompt so I booted from the rescue disk and re-initialised the initramfs image for the current kernel.
Dracut –f –v /boot/initramfs-3.10.0-862.14.4.el7.x86_64.img 3.10.0-862.14.4.el7.x86_64 --add-drivers "hv_vmbus hv_storvsc hv_netvsc hv_utils hv_balloon hyperv-keyboard hyperv_fb hid-hyperv
(Found on Centos Forums)
After this the boot sequence got a lot further but seems to hang when initialising the UI.
I am able to press Ctrl-Alt F2 to get to a console log in and sign in as my user or as root. If I try to run startx the screen flicker and returns with information about xorg. Looking in the logs it appear that the machine can’t find a display.
<EE> open /dev/dri/card0 no such file or directory
Falling back on old probe method
<EE> screen 0 deleted because of no matching config section
I’ve done a little googling, most of which seems to point towards the .Xauthority and .xinitrc files, both of which are empty under my user home.
I’m feeling a little out of my depth on this one, I’ve not used hyper-v before and I’ve not had these kind of issue when migrating an image before, granted that experience is fairly limited.
Apologies if the information is a little scarce, but I can’t copy the logs back off the other machine. If I can provide any more information that would be helpful, please just ask.
UPDATE:
Running X --configure gives the following error
<EE> Backtrace
0: X (xorg_backtrace=0x55) <ram address>
1: <ram address> <ram address>
2. /lib64/libpthread.so.0 <ram address>
Segmentation fault at address 0x0
Fatal Server error
Caught signal 11 Segmentation fault. Server Aborting
virtual-machine xorg gnome hyper-v centos-7
virtual-machine xorg gnome hyper-v centos-7
asked Nov 20 at 9:28
Sam Brett
12
New contributor
Sam Brett is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
asked Nov 20 at 9:28
Sam Brett
12
New contributor
Sam Brett is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
edited yesterday
asked Nov 20 at 9:28
Sam Brett
12
New contributor
Sam Brett is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
asked Nov 20 at 9:28
Sam Brett
12
asked Nov 20 at 9:28
Sam Brett
12
12
New contributor
Sam Brett is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
New contributor
Sam Brett is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
Sam Brett is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
add a comment |
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
Sam Brett is a new contributor. Be nice, and check out our Code of Conduct.
Sam Brett is a new contributor. Be nice, and check out our Code of Conduct.
Sam Brett is a new contributor. Be nice, and check out our Code of Conduct.
Sam Brett is a new contributor. Be nice, and check out our Code of Conduct.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1376914%2fmigrating-centos-to-hyper-v-fails-to-boot-gnome%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
