Query on Pointing Device.
What will happen when the input tag of the xml has the following format ? <input type != 'mouse/tablet' bus != 'xen/usb/ps2'/> For ein on Xen_PointingDevice Should the caption be "Unknown bus Unknown device type" ?? Though I tried creating a guest with invalid values in the input tags using the xml file, the guest was always created with the <input type='mouse' bus='xen'/> tag when I saw the dumpxml of the guest. Is there a way to supply invalid values to the input tag ? Thanks and Regards, Deepti.
Deepti B Kalakeri wrote:
What will happen when the input tag of the xml has the following format ? <input type != 'mouse/tablet' bus != 'xen/usb/ps2'/> For ein on Xen_PointingDevice Should the caption be "Unknown bus Unknown device type" ??
Though I tried creating a guest with invalid values in the input tags using the xml file, the guest was always created with the <input type='mouse' bus='xen'/> tag when I saw the dumpxml of the guest. Is there a way to supply invalid values to the input tag ?
If you try to create a guest with an invalid type or bus, you'll see something like the following error: <input type='invalid' bus='ps2'/> libvir: Domain Config error : internal error unknown input device type 'invalid' error: Failed to define domain from test --------------- <input type='mouse' bus='invalid'/> libvir: Domain Config error : internal error unknown input bus type 'invalid' error: Failed to define domain from test ------------ If we're unable to get the expected values from the guest, then some kind of error in libvirt has occurred. So setting the caption to "Unknown bus Unknown device type" is a fall back in that case. -- Kaitlin Rupert IBM Linux Technology Center kaitlin@linux.vnet.ibm.com
Deepti B Kalakeri wrote:
What will happen when the input tag of the xml has the following format ? <input type != 'mouse/tablet' bus != 'xen/usb/ps2'/> For ein on Xen_PointingDevice Should the caption be "Unknown bus Unknown device type" ??
Though I tried creating a guest with invalid values in the input tags using the xml file, the guest was always created with the <input type='mouse' bus='xen'/> tag when I saw the dumpxml of the guest. Is there a way to supply invalid values to the input tag ?
If you try to create a guest with an invalid type or bus, you'll see something like the following error:
<input type='invalid' bus='ps2'/>
libvir: Domain Config error : internal error unknown input device type 'invalid' error: Failed to define domain from test
---------------
<input type='mouse' bus='invalid'/>
libvir: Domain Config error : internal error unknown input bus type 'invalid' error: Failed to define domain from test
------------
If we're unable to get the expected values from the guest, then some kind of error in libvirt has occurred. So setting the caption to "Unknown bus Unknown device type" is a fall back in that case. Does the <input type='mouse' bus='xen'/> get assigned by default ? Because, for Xen PV the values are getting assigned by default even
Kaitlin Rupert wrote: though the tc did not supply them . Ex: check the vsxml output from the tc 41_cs_to_settingdefinestate.py. The default values are not getting assigned for KVM though. Thanks and Regards, Deepti.
Deepti B Kalakeri wrote:
Deepti B Kalakeri wrote:
What will happen when the input tag of the xml has the following format ? <input type != 'mouse/tablet' bus != 'xen/usb/ps2'/> For ein on Xen_PointingDevice Should the caption be "Unknown bus Unknown device type" ??
Though I tried creating a guest with invalid values in the input tags using the xml file, the guest was always created with the <input type='mouse' bus='xen'/> tag when I saw the dumpxml of the guest. Is there a way to supply invalid values to the input tag ?
If you try to create a guest with an invalid type or bus, you'll see something like the following error:
<input type='invalid' bus='ps2'/>
libvir: Domain Config error : internal error unknown input device type 'invalid' error: Failed to define domain from test
---------------
<input type='mouse' bus='invalid'/>
libvir: Domain Config error : internal error unknown input bus type 'invalid' error: Failed to define domain from test
------------
If we're unable to get the expected values from the guest, then some kind of error in libvirt has occurred. So setting the caption to "Unknown bus Unknown device type" is a fall back in that case. Does the <input type='mouse' bus='xen'/> get assigned by default ? Because, for Xen PV the values are getting assigned by default even
Kaitlin Rupert wrote: though the tc did not supply them . Ex: check the vsxml output from the tc 41_cs_to_settingdefinestate.py. The default values are not getting assigned for KVM though.
The use of cim_define is adding the input tags .
Thanks and Regards, Deepti.
Kaitlin Rupert wrote:
Deepti B Kalakeri wrote:
What will happen when the input tag of the xml has the following format ? <input type != 'mouse/tablet' bus != 'xen/usb/ps2'/> For ein on Xen_PointingDevice Should the caption be "Unknown bus Unknown device type" ??
Though I tried creating a guest with invalid values in the input tags using the xml file, the guest was always created with the <input type='mouse' bus='xen'/> tag when I saw the dumpxml of the guest. Is there a way to supply invalid values to the input tag ?
If you try to create a guest with an invalid type or bus, you'll see something like the following error:
<input type='invalid' bus='ps2'/>
libvir: Domain Config error : internal error unknown input device type 'invalid' error: Failed to define domain from test
---------------
<input type='mouse' bus='invalid'/>
libvir: Domain Config error : internal error unknown input bus type 'invalid' error: Failed to define domain from test
------------
If we're unable to get the expected values from the guest, then some kind of error in libvirt has occurred. So setting the caption to "Unknown bus Unknown device type" is a fall back in that case. What should be the values for Xen, XenFV, KVM and LXC for input type and bus tags ? Should we supply input type='mouse' bus='xen' for XenPV by default? when to supply type=tablet and bus=ps2/usb ?
Thanks and Regards, Deepti.
If we're unable to get the expected values from the guest, then some kind of error in libvirt has occurred. So setting the caption to "Unknown bus Unknown device type" is a fall back in that case. What should be the values for Xen, XenFV, KVM and LXC for input type and bus tags ? Should we supply input type='mouse' bus='xen' for XenPV by default? when to supply type=tablet and bus=ps2/usb ?
Yes - this is my mistake that I haven't covered the 'xen' bus type in the input device. I'll submit a patch that fixes this. I haven't submitted patches for this yet, but here's what I'm planning. The template RASDs returned by the SDC association will return the possible values for the input devices. The DefineSystem() call in VSMS will set default values if an input device isn't specified. These are the possible values one can set: Xen PV: type: mouse bus: xen (libvirt creates this by default) Xen FV type: mouse bus: ps2 (libvirt creates this by default) type: mouse bus: usb KVM: type: mouse bus: ps2 type: mouse bus: usb type: tablet bus: usb LXC: type: mouse bus: usb -- Kaitlin Rupert IBM Linux Technology Center kaitlin@linux.vnet.ibm.com
KR> LXC: type: mouse bus: usb Eh? Does libvirt put a mouse device into the LXC config? If it does, it's a bug. -- Dan Smith IBM Linux Technology Center Open Hypervisor Team email: danms@us.ibm.com
participants (3)
-
Dan Smith -
Deepti B Kalakeri -
Kaitlin Rupert