Re: 转发: Error when executing virsh command to ESX

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 2012年03月21日 15:49, li_fuqiong wrote:
To Whom It May concern:
I found that the following error is caused by adding a scsi disk to
install the os, I remove the scsi disk and the error remove but still
report 'out of memory':

When trying to ask for help, it's better to tell which hypervisor
driver you are using.

virsh # dumpxml win2003_122
internal error Invalid or not yet handled value '/vmfs/devices/genscsi/mp
x.vmhba0:C0:T1:L0' for VMX entry 'scsi0:1.fileName'

From the source and per the error you got, we can known you are
using VMWare driver though.

VMWare driver parses the disk conf from .vmx file, and it recongnizes
the disk type with the disk file name suffix. Think you will fix
the problem by append ".vmdk" to the scsi disk you use in .vmx.

virsh # list --all
Id Name State
----------------------------------
80 win2003_122 running
- winxp121 shut off
virsh # nodeinfo
error: failed to get node information
error: out of memory

VMWare driver doesn't support nodeinfo, it's expected to see error
lile "this function is not supported by the connection driver". While
you see this, it's a bug. Could you try with libvirt 0.9.10 to see
if the problem is fixed yet?

Regards,
Osier


[Index of Archives]     [Virt Tools]     [Lib OS Info]     [Fedora Users]     [Fedora Desktop]     [Fedora SELinux]     [Yosemite News]     [KDE Users]

  Powered by Linux