Kernel ioremap error - 3.2.60-71.art.x86_64

[DarkF@der]

Hello,

I got this error when i boot in the asl kernel:

Code: Select all

Jul 24 18:53:37 server24 kernel: ioremap error for 0xdffff000-0xe0000000, requested 0x10, got 0x0

Code: Select all

uname -r
3.2.60-71.art.x86_64

Code: Select all

cat /etc/redhat-release
CentOS release 6.5 (Final)

This is a KVM VM.

Greetz

[scott]

Are you using El5 or EL6?

[DarkF@der]

hi scott i'm using EL6

[scott]

Ok, I think I might have an idea there. It could be related to the kernexec protections with kvm, are you by any chance using the vscsi controller on your image?

[DarkF@der]

Hello Scott,

We using SolusVM.
And the Virtio drivers are loaded here my conf:

Code: Select all

<domain type='kvm'>
 <name>kvm102</name>
 <uuid>51dafddf-a2a3-4ec0-87a8-96573e84cbf3</uuid>
 <memory>8388608</memory>
 <currentMemory>8388608</currentMemory>
  <memtune>
   <hard_limit>8439808</hard_limit>
  </memtune>
 <vcpu>8</vcpu>
<cpu match='exact' mode='host-passthrough'>
 </cpu>
  <os>
   <type machine='pc'>hvm</type>
   <boot dev='hd'/>
   <boot dev='cdrom'/>
  </os>
 <clock sync='localtime'/>
  <devices>
   <emulator>/usr/libexec/qemu-kvm</emulator>
    <graphics type='vnc' port='5902' passwd='xxxxxxx' listen='0.0.0.0'/>
    <disk type='file' device='disk'>
     <source file='/dev/vol_grp1/kvm102_img'/>
     [color=#BF0000]<target dev='hda' bus='virtio'/>[/color]
    </disk>
    <disk type='file' device='cdrom'>
     <target dev='hdc'/>
     <readonly/>
    </disk>
    <interface type='bridge'>
     <model type='e1000' />
     <source bridge='br0'/>
     <target dev='kvm102.0'/>
     <mac address='00:16:3c:45:43:83'/>
    </interface>
    <input type='tablet'/>
    <input type='mouse'/>
    </devices>
    <features>
    <acpi/>
    <apic/>
    </features>
    <on_poweroff>destroy</on_poweroff>
    <on_reboot>restart</on_reboot>
    </domain>

Can you tell me how to to that?

Greetz

[scott]

Well Im not familiar with that one, on ours I use virt-manager and then look at the controller for the disk.

[DarkF@der]

But what's the impact off this error?... What this error means?
Will i lose performance because of this because it can't load my scsi driver?
I have contacted SolusVM:

Code: Select all

HI,

I've just go through the link. But I can't find where do you need vscsi controller and why do you need vscsi controller instead of virtio from your link.

You should explain something here to assist you. 

--
Regards,
Harsha @ SolusLabs L3 Support 

Can you explain it?

Thanks in advanced

[scott]

I'm just speculating right now, since thats an error message related to the I/O system. It helps to get info on the configuration above it since its so indeterminate. The vscsi driver for example is the really fast (with awesome sauce) driver redhat put together. We only added support for it a few revs ago, so its something we're still monitoring for issues.

[DarkF@der]

I just get a reply:

Code: Select all

Hi,

There is no such thing "vscsi controller" in KVM virtualization and vscsi controller driver is related to Vmware.

KVM supports VIRTIO and IDE disk driver.

--
Regards,
Harsha @ SolusLabs L3 Support 

[scott]

So its not a redhat / fedora platform and they dont have that particular option. Its full name btw is "VirtIO SCSI", which is not to be confused with "VirtIO" hence, vscsi. While that exists in vmware, they are incorrect as the vscsi linux driver exists in KVM as well as both are para-virt style controllers.

https://fedoraproject.org/wiki/Features/virtio-scsi