Shutting the VM down worked perfectly. thanks
Gary ------------------------------------------------------------------------ Gary Pedretty [email protected] <mailto:[email protected]> Systems Manager www.flyravn.com <http://www.flyravn.com/> Ravn Alaska /\ 907-450-7251 5245 Airport Industrial Road / \/\ 907-450-7238 fax Fairbanks, Alaska 99709 /\ / \ \ Second greatest commandment Serving All of Alaska / \/ /\ \ \/\ “Love your neighbor as Really loving the record green up date! Summmer!! yourself” Matt 22:39 ------------------------------------------------------------------------ > On Jan 2, 2017, at 2:32 PM, Gary Pedretty <[email protected]> wrote: > > I will try it with the vm shutdown. > > thanks > > gary > > > ------------------------------------------------------------------------ > Gary Pedretty [email protected] > <mailto:[email protected]> > Systems Manager www.flyravn.com > <http://www.flyravn.com/> > Ravn Alaska /\ 907-450-7251 > 5245 Airport Industrial Road / \/\ 907-450-7238 fax > Fairbanks, Alaska 99709 /\ / \ \ Second greatest commandment > Serving Alaska's Interior / \/ /\ \ \/\ "Love your neighbor as > Having a heatwave, its summer yourself” Matt 22:39 > ------------------------------------------------------------------------ > > > > > >> On Jan 1, 2017, at 5:18 AM, Doron Fediuck <[email protected] >> <mailto:[email protected]>> wrote: >> >> Hi Gary, >> this is a known issue we're working on. if the VM is down it should >> work as expected (edit the VM and close the dialog). >> Please try and let me know. Another option is to do this until the bug >> is resolved is using the REST API. >> >> Note that this is currently working on on Linux guests (there are no >> updated Windows drivers). You will need to configure >> the device in the guest as explained by the docs. >> >> Doron
_______________________________________________ Users mailing list [email protected] http://lists.ovirt.org/mailman/listinfo/users
