Hi,
I’m looking for the gateway router IP
I created the internal VRnetw but not
getting a host reply.
Cheers,
Stephen
___
virt-tools-list mailing list
virt-tools-list@redhat.com
https://www.redhat.com/mailman/listinfo/virt-tools-list
On Thu, Mar 26, 2015 at 11:26:57PM +0100, Fabiano Fidêncio wrote:
Remove all the dialogs used to report errors on extract_connect_info()
and just propagate the errors we got from the it.
from it
The only exception is virt_viewer_domain_event(), that is a callback
that doesn't have GError as
On Thu, Mar 26, 2015 at 11:27:00PM +0100, Fabiano Fidêncio wrote:
---
src/virt-viewer.c | 6 ++
1 file changed, 2 insertions(+), 4 deletions(-)
diff --git a/src/virt-viewer.c b/src/virt-viewer.c
index e94b897..123c7d2 100644
--- a/src/virt-viewer.c
+++ b/src/virt-viewer.c
@@ -526,10
On Thu, Mar 26, 2015 at 11:26:59PM +0100, Fabiano Fidêncio wrote:
All the situations where virt_viewer_update_display() can fail are
those when we won't be able to connect regardless of what changes on the
remote host. So, propagate the error instead of keep waiting.
I'd say instead of waiting
Hey,
On Thu, Mar 26, 2015 at 11:26:54PM +0100, Fabiano Fidêncio wrote:
This is part of a small re-factoring that will have all connection
errors, when we won't be able to connect regardless of what changes on
the remote host, being treated by virt_viewer_app_initial_connect(),
avoiding weird
On Thu, Mar 26, 2015 at 11:26:55PM +0100, Fabiano Fidêncio wrote:
This is part of a small re-factoring that will have all connection
errors, when we won't be able to connect regardless of what changes on
the remote host, being treated by virt_viewer_app_initial_connect(),
avoiding weird
Please reply on-list.
On 03/27/2015 09:41 AM, Stephen wrote:
Hi Cole,
When the nodes boot to PXE, they just
hang. But I’ve ping the connections be-
tween all the hosts and where successful.
You've provided no details of your config so it's default to provide useful
feedback.
- Cole
On 03/27/2015 02:42 AM, Stephen wrote:
Hi,
I’m looking for the gateway router IP
I created the internal VRnetw but not
getting a host reply.
Check ifconfig -a output from the host
- Cole
___
virt-tools-list mailing list
On Thu, 2015-03-26 at 23:26 +0100, Fabiano Fidêncio wrote:
This is part of a small re-factoring that will have all connection
errors, when we won't be able to connect regardless of what changes on
the remote host, being treated by virt_viewer_app_initial_connect(),
avoiding weird behaviors as
On Fri, 2015-03-27 at 17:21 +0100, Fabiano Fidêncio wrote:
Changes since v3:
* Address Christophe's comments about:
** Do not create a local err variable
** Improve commit messages
** Simplyfing the update_display logic
* Address Jonathon's comments about:
** Chaning the return type
Remove all the dialogs used to report errors on extract_connect_info()
and just propagate the errors we got from it.
The only exception is virt_viewer_domain_event(), that is a callback
that doesn't have GError as argument. In this specific case, we show the
error dialog instead of propagating it.
Changes since v3:
* Address Christophe's comments about:
** Do not create a local err variable
** Improve commit messages
** Simplyfing the update_display logic
* Address Jonathon's comments about:
** Chaning the return type of _create_session()
to boolean, as by convention the
This is part of a small re-factoring that will have all connection
errors, when we won't be able to connect regardless of what changes on
the remote host, being treated by virt_viewer_app_initial_connect(),
avoiding weird behaviors as we have nowadays (like more than one error
dialog being shown
By convention functions that take GError parameters should return FALSE
(or NULL) or error.
Related: rhbz#1085216
---
src/remote-viewer.c | 6 +++---
src/virt-viewer-app.c | 12 ++--
src/virt-viewer-app.h | 2 +-
src/virt-viewer.c | 2 +-
4 files changed, 11 insertions(+), 11
---
src/virt-viewer.c | 8 +++-
1 file changed, 3 insertions(+), 5 deletions(-)
diff --git a/src/virt-viewer.c b/src/virt-viewer.c
index e297757..2f047f0 100644
--- a/src/virt-viewer.c
+++ b/src/virt-viewer.c
@@ -522,12 +522,10 @@ virt_viewer_update_display(VirtViewer *self, virDomainPtr
All the situations where virt_viewer_update_display() can fail are
those when we won't be able to connect regardless of what changes on the
remote host. So, propagate the error instead of waiting for the guest to
start.
Related: rhbz#1085216
---
src/virt-viewer.c | 2 +-
1 file changed, 1
This is part of a small re-factoring that will have all connection
errors, when we won't be able to connect regardless of what changes on
the remote host, being treated by virt_viewer_app_initial_connect(),
avoiding weird behaviors as we have nowadays (like more than one error
dialog being shown
Remove the dialog used to report errors when create_session() fails,
propagating the error is enough and it is already done.
Related: rhbz#1085216
---
src/remote-viewer.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/src/remote-viewer.c b/src/remote-viewer.c
index
On 03/25/2015 11:23 PM, Stephen wrote:
Hi,
I have disk pool with 3 partitions with plenty space left over
but cannot add anymore partitions. Any idea how to
work through this.
I'm guessing your disk is partitioned using older MBR records (typical
of BIOS) and not newer GPT records (typical
This series adds support for LKVM detection with the first patch,
and running in ARM guests with the second - initially only detecting
lkvm, qemu/kvm, and xen. Here's a table of the new support with its
testing status. You'll see that not much has been tested, thus the
RFT. It does pass 'make
Currently only detects LKVM, QEMU/KVM, and Xen. Also only works if
the guest is booted with DT (which is the only way that currently
exists).
Signed-off-by: Andrew Jones drjo...@redhat.com
---
Makefile.am| 21
tests/lkvm-arm/proc/cpuinfo
Signed-off-by: Andrew Jones drjo...@redhat.com
---
Makefile.am| 6 ++
tests/lkvm/proc/cpuinfo| 19 +
tests/lkvm/proc/self/status| 39 ++
tests/lkvm/sbin/dmidecode | 2 ++
Hi,
I restarted my computer, then tried to create a new machine.
Usually virt-manager asks if I want to fix the permission to
allow the storage pool to be accessed.
Now this process returns a error [Errno 1] Operation not
permitted.
As root I have already gave permission to the drive but
now
Thanks Drew - I pushed the patch series upstream.
You'll probably want to send something similar to systemd (ie. for
systemd-detect-virt), since we are using a mix of both programs for
virt detection in different places.
Rich.
--
Richard Jones, Virtualization Group, Red Hat
[Sorry - I didn't see this email until now as virt-rescue is part of
the http://libguestfs.org project and so normally uses a different
mailing list]
On Tue, Mar 17, 2015 at 11:29:29AM +, Keith Roberts wrote:
Hi all.
I’d like to create a statically-linked version of virt-rescue that I
can
Disk with extended partition but I cannot create a directory. Where
is /dev/sda2 stored so I can create directory?
Cheers,
Stephen
On Mar 27, 2015, at 11:23 AM, Eric Blake ebl...@redhat.com wrote:
On 03/25/2015 11:23 PM, Stephen wrote:
Hi,
I have disk pool with 3 partitions with
26 matches
Mail list logo
