On 12/19/2014 03:52 PM, Dave Stevens wrote:
what you say makes sense, but leaves me with two problems - what to do and how did this happen?
You never mentioned if this is for a dom0 or domu, if it's a domu is it a pv or hvm domain and does it use pvgrub, pygrub or does it boot directly to a kernel on the dom0?
Also paste the output of this command from the affected domain: rpm -q kernel kernel-xen
Peter
On Fri, 2014-12-19 at 16:21 +1300, Peter wrote:
On 12/19/2014 03:52 PM, Dave Stevens wrote:
what you say makes sense, but leaves me with two problems - what to do and how did this happen?
You never mentioned if this is for a dom0 or domu, if it's a domu is it a pv or hvm domain and does it use pvgrub, pygrub or does it boot directly to a kernel on the dom0?
Also paste the output of this command from the affected domain: rpm -q kernel kernel-xen
Peter _______________________________________________ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Check your /etc/modprobe.conf and see if you have a line that specifies xenblk, such as 'alias scsi_hostadapter xenblk'.
I converted a xen vm to kvm and got that error for the above reason.
Bill
On 12/21/2014 05:01 PM, Bill Ferguson wrote:
Check your /etc/modprobe.conf and see if you have a line that specifies xenblk, such as 'alias scsi_hostadapter xenblk'.
Yes, that is what causes the error message, but removing the lines is not the solution here. Those are required for Xen pv domains as well as HVM domains that run the pv drivers.
I converted a xen vm to kvm and got that error for the above reason.
Yes you would remove those when converting to a KVM vm but please do not remove them if you are running a Xen vm.
Peter
-
Bill Ferguson -
Peter