>
> On Tue, Mar 31, 2015 at 3:03 PM, Pavel Grunt
> wrote:
> > Do not allow to zoom out if it is not possible due to the width of
> > the top menu. It avoids emitting size allocation events that will
> > change the display resolution of the spice guest.
> >
> > Resolves: https://bugzilla.redhat.c
On Tue, Mar 31, 2015 at 3:03 PM, Pavel Grunt wrote:
> Do not allow to zoom out if it is not possible due to the width of
> the top menu. It avoids emitting size allocation events that will
> change the display resolution of the spice guest.
>
> Resolves: https://bugzilla.redhat.com/show_bug.cgi?id
Hi,
I’ve tried to understand from the online docs
but I can’t get a single VM to route to a public
IP as a web server.
I’ve tried adding networks, bridging interfaces,
using NAT vs Routed, VLANS.
My env:
VM = 192.168
Eth0Host = 200.200
Router = Public IP
I use the default IP which uses NAT an
Tomorrow i will try to backtrace.
If can help,when i try to connect via "virsh -c virtualmachinename" i have 2
errors:
"error: failed to connect to the hypervisor"
"error: no connection driver available for virtualmachinename"
But "virsh -c qemu:///system list" is working fine.
I'm on ubuntu 14.
On 03/31/2015 12:00 PM, Giuseppe Scrivano wrote:
> Signed-off-by: Giuseppe Scrivano
> ---
> virtinst/cloner.py | 6 --
> virtinst/storage.py | 8 +---
> 2 files changed, 9 insertions(+), 5 deletions(-)
>
> diff --git a/virtinst/cloner.py b/virtinst/cloner.py
> index 68a5786..c533e7e 100
Signed-off-by: Giuseppe Scrivano
---
virtinst/cloner.py | 6 --
virtinst/storage.py | 8 +---
2 files changed, 9 insertions(+), 5 deletions(-)
diff --git a/virtinst/cloner.py b/virtinst/cloner.py
index 68a5786..c533e7e 100644
--- a/virtinst/cloner.py
+++ b/virtinst/cloner.py
@@ -1,5 +1,
On 03/31/2015 10:04 AM, Mirko Galimberti wrote:
> Hi guys,
> I’m experiencing this issue:
>
> Traceback (most recent call last):
>
> File "/usr/share/virt-manager/virtManager/engine.py", line 296, in _tick
>
> conn.tick()
>
> File "/usr/share/virt-manager/virtManager/connection.py", lin
On 03/31/2015 07:12 AM, Satya Prasad Nemana wrote:
> Gurus,
>
> I need clarity on what each item means and how it maps to the info we find on
> dmidecod or lscpu on the host when creating a guest from the virt-manager.
>
> My question:
>
> 1) Under CPUs , we have Logical Host CPUs: What number d
Hi guys,
I'm experiencing this issue:
Traceback (most recent call last):
File "/usr/share/virt-manager/virtManager/engine.py", line 296, in _tick
conn.tick()
File "/usr/share/virt-manager/virtManager/connection.py", line 1311, in
tick
self._tick(noStatsUpdate)
File "/usr/share/v
Do not allow to zoom out if it is not possible due to the width of
the top menu. It avoids emitting size allocation events that will
change the display resolution of the spice guest.
Resolves: https://bugzilla.redhat.com/show_bug.cgi?id=1206460
---
v3:
- return when zoom level doesn't change
- m
Gurus,
I need clarity on what each item means and how it maps to the info we find
on dmidecod or lscpu on the host when creating a guest from the
virt-manager.
My question:
1) Under CPUs , we have Logical Host CPUs: What number does it indicate? Is
the max value that can be configured here the C
On Mon, Mar 30, 2015 at 11:28 PM, Fabiano Fidêncio wrote:
> On Mon, Mar 30, 2015 at 10:17 PM, Pavel Grunt wrote:
>> Do not allow to zoom out if it is not possible due to the width of
>> the top menu. It avoids emitting size allocation events that will
>> change the display resolution of the spice
12 matches
Mail list logo
