Re: access VMX config on esxi with virsh

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

 



Hi,

...
> 
> However, it sounds like that's not working for you.
> 
> That could be a bug. Would you be ok with trying it again, then pasting 
> the error message here for us to see?
> 

- virsh -c esx://esx1.local/?no_verify=1 dominfo vmtest.local --> works OK
- virsh -c esx://esx1.local/?no_verify=1 dumpxml vmtest.local 

gives the error message:
error memory conf:90: expecting an assignment (+ debug logs attached to this mail)

regards, frank
-- 
GMX DSL SOMMER-SPECIAL: Surf & Phone Flat 16.000 für nur 19,99 Euro/mtl.!*
http://portal.gmx.net/de/go/dsl
18:36:23.186: debug : virInitialize:339 : register drivers
18:36:23.187: debug : virRegisterDriver:927 : registering Test as driver 0
18:36:23.187: debug : virRegisterNetworkDriver:733 : registering Test as network driver 0
18:36:23.187: debug : virRegisterInterfaceDriver:764 : registering Test as interface driver 0
18:36:23.187: debug : virRegisterStorageDriver:795 : registering Test as storage driver 0
18:36:23.187: debug : virRegisterDeviceMonitor:826 : registering Test as device driver 0
18:36:23.187: debug : virRegisterSecretDriver:857 : registering Test as secret driver 0
18:36:23.187: debug : virRegisterNWFilterDriver:888 : registering Test as network filter driver 0
18:36:23.189: debug : virRegisterDriver:927 : registering Xen as driver 1
18:36:23.189: debug : virRegisterDriver:927 : registering OPENVZ as driver 2
18:36:23.189: debug : virRegisterDriver:927 : registering PHYP as driver 3
18:36:23.189: debug : virRegisterStorageDriver:795 : registering PHYP as storage driver 1
18:36:23.189: debug : virRegisterNetworkDriver:733 : registering PHYP as network driver 1
18:36:23.189: debug : virRegisterDriver:927 : registering ESX as driver 4
18:36:23.189: debug : virRegisterInterfaceDriver:764 : registering ESX as interface driver 1
18:36:23.189: debug : virRegisterNetworkDriver:733 : registering ESX as network driver 2
18:36:23.189: debug : virRegisterStorageDriver:795 : registering ESX as storage driver 2
18:36:23.189: debug : virRegisterDeviceMonitor:826 : registering ESX as device driver 1
18:36:23.189: debug : virRegisterSecretDriver:857 : registering ESX as secret driver 1
18:36:23.189: debug : virRegisterNWFilterDriver:888 : registering ESX as network filter driver 1
18:36:23.189: debug : virRegisterDriver:927 : registering remote as driver 5
18:36:23.189: debug : virRegisterNetworkDriver:733 : registering remote as network driver 3
18:36:23.189: debug : virRegisterInterfaceDriver:764 : registering remote as interface driver 2
18:36:23.189: debug : virRegisterStorageDriver:795 : registering remote as storage driver 3
18:36:23.189: debug : virRegisterDeviceMonitor:826 : registering remote as device driver 2
18:36:23.189: debug : virRegisterSecretDriver:857 : registering remote as secret driver 2
18:36:23.189: debug : virRegisterNWFilterDriver:888 : registering remote as network filter driver 2
18:36:23.189: debug : virConnectOpenAuth:1498 : name=esx://esx1.local/?no_verify=1, auth=0x7f32ea639de0, flags=0
18:36:23.190: debug : do_open:1204 : name "esx://esx1.local/?no_verify=1" to URI components:
  scheme esx
  opaque (null)
  authority (null)
  server esx1.local
  user (null)
  port 0
  path /

18:36:23.190: debug : do_open:1243 : trying driver 0 (Test) ...
18:36:23.190: debug : do_open:1249 : driver 0 Test returned DECLINED
18:36:23.190: debug : do_open:1243 : trying driver 1 (Xen) ...
18:36:23.190: debug : do_open:1249 : driver 1 Xen returned DECLINED
18:36:23.190: debug : do_open:1243 : trying driver 2 (OPENVZ) ...
18:36:23.190: debug : do_open:1249 : driver 2 OPENVZ returned DECLINED
18:36:23.190: debug : do_open:1243 : trying driver 3 (PHYP) ...
18:36:23.190: debug : do_open:1249 : driver 3 PHYP returned DECLINED
18:36:23.190: debug : do_open:1243 : trying driver 4 (ESX) ...
18:36:30.571: debug : do_open:1249 : driver 4 ESX returned SUCCESS
18:36:30.571: debug : do_open:1269 : network driver 0 Test returned DECLINED
18:36:30.571: debug : do_open:1269 : network driver 1 PHYP returned DECLINED
18:36:30.571: debug : do_open:1269 : network driver 2 ESX returned SUCCESS
18:36:30.571: debug : do_open:1288 : interface driver 0 Test returned DECLINED
18:36:30.571: debug : do_open:1288 : interface driver 1 ESX returned SUCCESS
18:36:30.571: debug : do_open:1308 : storage driver 0 Test returned DECLINED
18:36:30.571: debug : do_open:1308 : storage driver 1 PHYP returned DECLINED
18:36:30.571: debug : do_open:1308 : storage driver 2 ESX returned SUCCESS
18:36:30.571: debug : do_open:1328 : node driver 0 Test returned DECLINED
18:36:30.571: debug : do_open:1328 : node driver 1 ESX returned SUCCESS
18:36:30.571: debug : do_open:1355 : secret driver 0 Test returned DECLINED
18:36:30.571: debug : do_open:1355 : secret driver 1 ESX returned SUCCESS
18:36:30.571: debug : do_open:1375 : nwfilter driver 0 Test returned DECLINED
18:36:30.571: debug : do_open:1375 : nwfilter driver 1 ESX returned SUCCESS
18:36:30.571: debug : virDomainLookupByName:2154 : conn=0x202dab0, name=vmtest.local
18:36:30.617: debug : virGetDomain:382 : New hash entry 0x20dd6d0
18:36:30.617: debug : virDomainGetXMLDesc:3065 : domain=0x20dd6d0, flags=0
18:36:30.754: error : virConfError:105 : memory conf:90: expecting an assignment
18:36:30.755: debug : virDomainFree:2242 : domain=0x20dd6d0
18:36:30.755: debug : virUnrefDomain:463 : unref domain 0x20dd6d0 vmtest.local 1
18:36:30.755: debug : virReleaseDomain:416 : release domain 0x20dd6d0 vmtest.local 423e94a9-a1c7-b31d-7161-76c7586c830e
18:36:30.755: debug : virReleaseDomain:433 : unref connection 0x202dab0 2
18:36:30.755: debug : virConnectClose:1524 : conn=0x202dab0
18:36:30.755: debug : virUnrefConnect:294 : unref connection 0x202dab0 1
18:36:30.765: debug : virReleaseConnect:249 : release connection 0x202dab0

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

  Powered by Linux