|
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
|
