Ticket #2208 (closed defect: fixed)

Opened 10 years ago

Last modified 8 years ago

vboxmanage showvminfo does not show IDE controller type

Reported by: TerryE Owned by:
Priority: minor Component: VM control
Version: VirtualBox 2.0.0 Keywords:
Cc: Guest type: other
Host type: other


When trying to diagnose user problems with configurations, I would thought that showvminfo would allow you to do a full comparison, but it doesn't include the the controller type. I had thought that this should be a 6 line change to VBoxManage.cpp, but looking through the SDK API, I can't find how to get this through the SDK which is probalby why you don't show it.

Perhaps you've missed this in your abstraction model. You don't actually have an IHostIDEInterface (or a IHostiSCSInterface or IHostSATAInterface for that matter). You need to rethink and tidy up your class hierarchy here.

The machine state should be fully browsable and controllable through the SDK API.

Change History

comment:1 Changed 10 years ago by klaus

  • Status changed from new to closed
  • Resolution set to fixed

I don't agree here. Introducing interfaces just for structuring purposes will simply decrease efficiency. Having an API reflect the totally screwed up structural design of a current PC would be from my point of view rather proof that we're not able to abstract properly.

The fact that showvminfo didn't include the IDE controller type was a simple omission. The API always provided this information. Fixed a while back, it's certainly in 2.0.6.

comment:2 Changed 10 years ago by TerryE

  • Status changed from closed to reopened
  • Resolution fixed deleted

I have 2.0.6 on my PC and when I do a showvminfo on one of my VMs, jeosLAMP, which has a PIIX4 controller I get the following:

D:\temp>VBoxManage showvminfo jeosLAMP | find "PII"

(in other words no hits) so your statement that showvminfo was a simple omission that was fixed a while back is not correct. Yes, it lists off VDIs connected to IDE channels, but not what controller is selected (unlike in the case of NICs).

There is no simple mechanism by which a user can script a method to generate the VBoxManage commands to recreate the VM.

The reason than I raised this is that "I've migrated / recreated my VM and the VDI now BSODs" is a pretty common error on the forum (defaulting to PIIX4 with XP). Surely showvminfo should list off sufficient detail to allow you to do this without having to parse the XML?

Sorry, but I don't understand your logic for closing this one.

comment:3 Changed 9 years ago by frank

  • Status changed from reopened to closed
  • Resolution set to fixed

This was a mistake, finally fixed in 2.1.0. Klaus just forgot to backport this change to the 2.0.x branch.

Note: See TracTickets for help on using tickets.
ContactPrivacy policyTerms of Use