On 6 February 2012 17:01, Andrew Dunlop <ajdunlop(a)gmail.com> wrote:
On 6 February 2012 16:05, Keith Robertson <kroberts(a)redhat.com>
wrote:
> On 02/06/2012 09:55 AM, Andrew Dunlop wrote:
>>
>> On 3 February 2012 13:41, Keith Robertson<kroberts(a)redhat.com> wrote:
>>>
>>>
> <snip>
>>
>> I have managed to get my existing KVM onto my node by converting it
>> from qcow to raw (using qemu-img convert) then I created a libxml file
>> from the arguements I have been using to start the VM with KVM. I then
>> used virt-v2v to do the conversion for oVirt and this put everything
>> in the correct places in the nfs export storage on my node. This then
>> appears without any problems in the VM Import tab for my Export
>> storage. I then restored this which was successful.
>> However when I run my VM I get past the GRUB OS selection screen then I
>> get:
>> Loading Linux ...
>>
>> Aborted.
>>
>> Any idea why this might be? Could it be a sparce problem? It must be
>> something to do with how oVIrt is running the VM as I have checked
>> that I can still run my VM using KVM from the nfs_export directory.
>> Does oVirt do something strange to the file system? Could it be an IDE
>> / VirtIO problem?
>
>
> I'm not familiar with this error and I honestly have no idea what it could
> mean. However, a search of the big brain (google) seems to indicate that it
> could be related to a malformed grub.cfg.
>
I have come to the conclusion it is a problem with my guest not being
set up for VirtIO. Will report back once I give it another try.
It would appear
that there is a problem with some versions of GRUB2
where a VM will fail to boot when KVM is using a non standard -vga
argument. See:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=616487