> On Jun 7, 2016, at 11:13 PM, Pavel Gashev wrote:
>
> It seems guest tools installer is broken at least for Windows 2012 R2. It
> installs files into Program Files, but doesn't actually install drivers and
> QEMU guest tools. No errors, it reports that everything is ok, but
I have found that playing video is not fluent in the virtual machine. So I
thought maybe too small video memory in virtual machines led to this. Some
parameters have been found when I was trying to check some information. So I
wonder where to modify them and if it works to do this.
-device
The "-r" arg to virsh makes all the difference :) (much to learn...)
[root@ovirt-node-03 ~]# virsh -r list
IdName State
6 proxmox-01 running
7 proxmox-02 running
It seems guest tools installer is broken at least for Windows 2012 R2. It
installs files into Program Files, but doesn't actually install drivers and
QEMU guest tools. No errors, it reports that everything is ok, but it's not.
oVirt guest tools is installed and work properly.
Workarounds are
On Tue, Jun 7, 2016 at 8:43 PM, Anantha Raghava <
rag...@exzatechconsulting.com> wrote:
> Hello Michal,
>
> Guest tools are working and getting all details about guest vm as needed.
>
> But one thing I didn't understand. What is the relationship between
> virtioserial driver and oVirt Guest
Hello Michal,
Guest tools are working and getting all details about guest vm as needed.
But one thing I didn't understand. What is the relationship between
virtioserial driver and oVirt Guest Service? Without virtio serial
driver, guest services does not start.
Also, how do we install
Hi i'm coworker of Mr Chapelle,
Thank you for your reply.
so if i understand we need to "downgrade" our ovirt engine which is in version
3.6.6.x to version 3.6.5?
But how can we do that?
Lionel Caignec.
- Mail original -
De: "Martin Polednik"
À: "chapelle"
On 07/06/16 16:50 +0200, Jérôme Chapelle wrote:
We are no more able to give a pci device to one VM.
Here is the process we used to assign one device to one VM:
- Click on the VM, and then on the tab "Host devices"
- In the tab, click on "pin to host" and select the host that will give the pci
We are no more able to give a pci device to one VM.
Here is the process we used to assign one device to one VM:
- Click on the VM, and then on the tab "Host devices"
- In the tab, click on "pin to host" and select the host that will give the pci
device
- Click on "add device", in the window
Oops, missed that comment...
When I try an operation with virsh, it asks me for credentials that it doesn't
accept...
[root@ovirt-node-03 ~]# virsh list
Please enter your authentication name: root
Please enter your password:
error: failed to connect to the hypervisor
error: no valid connection
Hi,
I'm looking for a way to change the duration of all tickets from all VMs. How
can I do this ? I'd like to change it to 5 min instead of 2 min.
It seems it is possible to change these parameters using the RestAPI, with
"action.grace_period.expiry" or "action.ticket.value"...
Anyway, these
On Tue, Jun 7, 2016 at 12:04 AM, Will Dennis wrote:
> Sorry, got away from this for a while attending to other work, but back at it
> now... Anyone have any ideas on how I may further troubleshoot this issue?
Edward later asked you to post the domxml.
You can find it with
12 matches
Mail list logo