Paul, Short answer: your approach will not work. I mentioned the custom hooks and engine-config/UserDefinedVMProperties for a reason. Please follow my advice first before asking further advice. Longer answer: your changes to the libvirt domains would apply on next domain cold start but that will never happen because vdsm always creates libvirt domains as transient ones so the libvirt domain will disappear on guest OS shutdown. On next start of the same oVirt VM, vdsm will creates a new domain XML that will be used to start a new libvirt transient domain. In order to make this new libvirt domain use your desired parameters, you have to edit the XML before it is used to start the libvirt domain and because we humans are too slow to do that and too annoyed to do that on every VM start, vdsm hooks mechanism was devised and a script in before_vm_start can do that changes for you (with input variables defined in engine-config and set in VM's custom properties). So back to my original suggestion: do you still think that it is wise to try method that is more complicated and less secure than the custom launcher method? Regards, David On Po, 2014-09-22 at 11:11 +0800, PaulCheung wrote:
Dear David:
I am trying figure it out using my way. So I used "virsh edit vm", I change the port the 5980 & 5981, but still not work!!!
I found after virsh edit, there is a xml file here /etc/libvirt/qemu which I edit using "virsh edit vm".
And I also run this command : "virsh define vm.xml"
also not work. Can you tell me where is the file I can fixed the spice port.
Sincerely yours, PaulCheung
tel: 180-8882-7173
Subject: Re: [ovirt-users] Bug: Spice port changed!!!!! From: djasa@redhat.com To: eq2008@msn.com CC: users@ovirt.org Date: Thu, 18 Sep 2014 15:27:50 +0200
Hi,
2) is not a file, it's a key in engine-config 3) is a VDSM custom hook that needs to be in all the hypervisors in DC/Cluster
Follow vdsm custom hook documentation (I don't have a link from top of my head but web or ML archives will surely help).
David
Dear David,
Thank you for your help . Your answer is very professional.
I still can't not find a way to stick with static port assignments For I don't understand you telling me , 2&3, where I can find the file to modify?
However, if you _really_ want to stick with static port assignments, do the following: 1) designate the port range so that it doesn't collide with other ranges in use (e.g. RHEV uses 5900-6023, so 5800-5899 could be safe) 2) add a custom VM properties to the engine for setting of port and tls-port 3) add a vdsm hook to before_vm_start directory on each host
add "port" and "tlsPort" parameters to the graphics element of
will libvirt
domain xml
Sincerely yours, PaulCheung
tel: 180-8882-7173
Subject: Re: [ovirt-users] Bug: Spice port changed!!!!! From: djasa@redhat.com To: eq2008@msn.com CC: users@ovirt.org Date: Wed, 17 Sep 2014 10:40:42 +0200
Hi Paul,
This behaviour is by design. It is a bad idea to override it. A good approach to your problem would be to write a launcher script
On Thu, 2014-09-18 at 14:51 +0800, PaulCheung wrote: that that
1) connect to the REST API 2) get the VM connection details 3) get new VM ticket 4) write this info down to a temporary .vv file [3] 5) launch remote-viewer
Some info how to use REST API is described here [1] and .vv file
would: format
is documented in virt-viewer sources [2]. Please note that [1] is a bit outdated: * you can use HTTP header "filter: true" to be able to log in as non-admin * you only have to use password login once when you use "prefer: persistent-auth" HTTP header and you send the cookie you got in a response to first request. In the future, the steps 2-4 will become a one step of getting a ready-to-use .vv file from the API [3] but we aren't there yet.
[1]
http://www.ovirt.org/How_to_Connect_to_SPICE_Console_Without_Portal
[2]
[3] https://bugzilla.redhat.com/show_bug.cgi?id=1128763
However, if you _really_ want to stick with static port assignments, do the following: 1) designate the port range so that it doesn't collide with other ranges in use (e.g. RHEV uses 5900-6023, so 5800-5899 could be safe) 2) add a custom VM properties to the engine for setting of port and tls-port 3) add a vdsm hook to before_vm_start directory on each host
add "port" and "tlsPort" parameters to the graphics element of
will libvirt
domain xml
Best regards,
David
On St, 2014-09-17 at 10:41 +0800, PaulCheung wrote:
Dear all,
After shutdown the VM, then restart the VM the Vm's spice port is changed!
Because I have 10 terminal ARM-Box running spice client connected to the vm, but after the VM shutdown and start again, the vm not
one
whice the one before.
I wish you can let us have a option, to let the VM with a fixed spice port, like: vm1: spice port : 5900 tls:5901 vm2: 5902 5903
And I have another recommond: have a fuction to do that :
if the vm shutdown by user, it will start the VM automatic. That means the VM can not be shutdown!
I hope you can have this two fuction! That means a lot to
https://git.fedorahosted.org/cgit/virt-viewer.git/tree/src/virt-viewer-file.... that the those
who
are using Terminal box user like me.
I am sorry for my poor English. But I hope you all can understand what I am saying.
Sincerely yours, PaulCheung
tel: 180-8882-7173
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users