Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 885168

Summary: Cannot boot VM system
Product: [Retired] oVirt Reporter: Martin Kralicek <martin.kralicek>
Component: ovirt-engine-coreAssignee: Nobody's working on this, feel free to take it <nobody>
Status: CLOSED WORKSFORME QA Contact:
Severity: high Docs Contact:
Priority: unspecified    
Version: 3.1 RCCC: acathrow, dfediuck, dyasny, iheim, ykaul
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard: virt
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-02-15 18:42:02 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
Engine log from 12.12.2012
none
Server log from 12.12.2012
none
Boot log from 12.12.2012 none

Description Martin Kralicek 2012-12-07 16:28:17 UTC
Description of problem:
OS on VM was Debian 6 and Ubuntu 10.04 with same issue (live CD is ok)
Cannot boot VM system with grub error
error: no suitable mode found
error: unknown command 'terminal'
unaligned pointer 0x.....
Aborted. Press any key to exit

Version-Release number of selected component (if applicable):
storage type iSCSI
display type VNC
run at Dell R720 server
OS Version: Fedora 17_64b
Kernel Version: 3.6.9-2
KVM Version: 1.0.1-2
VDSM Version: 4.10.0.10

Comment 1 Doron Fediuck 2012-12-09 08:58:51 UTC
Martin, 
please take a look in https://bugzilla.redhat.com/show_bug.cgi?id=881579 and let us know if this is the same issue. I've seen similar reports on Debian.

Comment 2 Martin Kralicek 2012-12-12 09:35:40 UTC
I tried to set all configuration what I can, but with same issue. I think that it is different, when I googling it could be fixed with add or change some kvm conf but I don not know how oVirt works yet and if uses this standart kvm conf.

With pure KVM and ProxMox on same machine and similar configuration works well.

Comment 3 Doron Fediuck 2012-12-12 09:53:27 UTC
(In reply to comment #2)
> I tried to set all configuration what I can, but with same issue. I think
> that it is different, when I googling it could be fixed with add or change
> some kvm conf but I don not know how oVirt works yet and if uses this
> standart kvm conf.
> 
> With pure KVM and ProxMox on same machine and similar configuration works
> well.

Martin, 
first of all please do not change the component. Opening a BZ for the configuration tool suggest there's a problem with the tool, and obviously
this is not the case.

Next, can you please provide the exact changes you did?
Also, please attach the relevant engine logs.

Comment 4 Martin Kralicek 2012-12-12 11:39:28 UTC
Created attachment 662293 [details]
Engine log from 12.12.2012

Comment 5 Martin Kralicek 2012-12-12 11:40:25 UTC
Created attachment 662294 [details]
Server log from 12.12.2012

Comment 6 Martin Kralicek 2012-12-12 11:40:57 UTC
Created attachment 662295 [details]
Boot log from 12.12.2012

Comment 7 Martin Kralicek 2012-12-12 11:50:09 UTC
Logs were uploaded from ovirt-engine machine...Will you want it from host machine as well?
I changed only storage type to local, display type and add some kernel boot options.
But now I do not know...when I use legacy grub not grub2 everything works ok.

Comment 8 Doron Fediuck 2012-12-12 14:33:39 UTC
Martin,
thanks for the logs.
The files you submitted do not have any reference for running a VM.
Either way, it looks like an internal guest bios or other issue.
I suggest we discuss it in the mailing list first, to get more people's
opinions on the actual problem. Once we understand the real problem,
we can decide if it's a bug, and if so, which component has a bug.

Comment 9 Martin Kralicek 2013-02-15 18:42:02 UTC
This issue manifests only with grub 2 and can be fix with editing config file and set variable terminal=console, but I don't know if this is clear hotfix or some little trick