[libvirt-users] 转发: Error when executing virsh command to ESX
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': 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' 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 virsh # dumpxml win2003_122 error: out of memory li_fuqiong 发件人： li_fuqiong 发送时间： 2012-03-21 15:24 收件人： libvirt-users 主题： Error when executing virsh command to ESX To Whom It May Concern: I use virsh windows 0.9.3 to connect an esx server 4.0 with no_verify=1. The Esx server is intel 2 x 3.19 GHZ CPU, 8G memroy and 2 TB hard disk. following is my execute commands and results. virsh -c esx://xxx.xxx.xxx.x?no_verify=1 virsh # list all Id Name State ---------------------------------- 80 win2003_122 running virsh # nodeinfo error: failed to get node information error: out of memory virsh # dumpxml win2003_122 error: internal error Invalid or not yet handled value '/vmfs/devices/genscsi/mp x.vmhba0:C0:T1:L0' for VMX entry 'scsi0:1.fileName' virsh # edit win2003_122 error: internal error Invalid or not yet handled value '/vmfs/devices/genscsi/mp x.vmhba0:C0:T1:L0' for VMX entry 'scsi0:1.fileName' virsh # destroy win2003_122 Domain win2003_122 destroyed virsh # start win2003_122 Domain win2003_122 started virsh # edit win2003_122 error: internal error Invalid or not yet handled value '/vmfs/devices/genscsi/mp x.vmhba0:C0:T1:L0' for VMX entry 'scsi0:1.fileName' question: 1.Why error when executeing dumpxml and edit command? How to fix it? 2.Why out of memory when nodeinfo. How to fix it? I have only one test vm on my esx server. Thanks in advance. Mark
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
Osier, Thank you very much for your helpful reply. I think I missed some info: 1. I execute nodeinfo, dumpxml command in windows client throw out of memory error, but can get right result in linux client, use the same VMware ESX 4.0 server, and virsh version is both 0.9.3 2. I want to try this with libvirt 0.9.10, but I don't where to download the missing 'libvirt-0.9.10-mingw.patch', could you tell me? Thank you. Mark 发件人： Osier Yang 发送时间： 2012-03-22 13:03 收件人： li_fuqiong 抄送： libvirt-users 主题： Re: [libvirt-users]转发: Error when executing virsh command to ESX 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
On 2012年03月22日 15:36, li_fuqiong wrote:
Osier, Thank you very much for your helpful reply. I think I missed some info: 1. I execute nodeinfo, dumpxml command in windows client throw out of memory error, but can get right result in linux client, use the same VMware ESX 4.0 server, and virsh version is both 0.9.3 2. I want to try this with libvirt 0.9.10, but I don't where to download the missing 'libvirt-0.9.10-mingw.patch', could you tell me?
I don't known what is libvirt-0.9.10-mingw.patch, never tried to make a build with mingw yet, :-) you might want to ask Eric, or Daniel Berrange. Regards, Osier
On 03/23/2012 07:18 PM, Osier Yang wrote:
On 2012年03月22日 15:36, li_fuqiong wrote:
Osier, Thank you very much for your helpful reply. I think I missed some info: 1. I execute nodeinfo, dumpxml command in windows client throw out of memory error, but can get right result in linux client, use the same VMware ESX 4.0 server, and virsh version is both 0.9.3 2. I want to try this with libvirt 0.9.10, but I don't where to download the missing 'libvirt-0.9.10-mingw.patch', could you tell me?
I don't known what is libvirt-0.9.10-mingw.patch, never tried to make a build with mingw yet, :-) you might want to ask Eric, or Daniel Berrange.
Are you talking about the Fedora package mingw32-libvirt? Also, be aware that right now, Fedora is in the middle of transitioning over to the mingw64 toolchain, and we need several patches to the spec file for building libvirt as a 64-bit mingw app. -- Eric Blake eblake@redhat.com +1-919-301-3266 Libvirt virtualization library http://libvirt.org
participants (3)
-
Eric Blake -
li_fuqiong -
Osier Yang