similar to: vnc oddness

If I ssh to a vm running Centos and then execute "poweroff" from within the vm, the vm shuts down as expected but the host in the admin ui becomes unavailable. Is anyone else experiencing this? I haven't checked to see if other guest OS's do the same thing yet. The painful thing is that then I have to shutdown all the VMs and reboot both the host and the management server

The VMs just boot up with the default network interface model which is 100Mb, is there a way to set it to a 1Gb model? Cheers, Justin.

Hi, I have set up a 40GB iscsi target on my san and when I add it in to the storage pool and it shows up as 40GB. When I try to create a 40GB volume in the ovirt UI it tries to but fails. The error message is that the volume will not fit. If I create one smaller than 40GB it works. Is anyone else experiencing this? Also, if I then start a virtual machine up to install on the newly

After running for a while the node becomes "unavailable" in the server UI. All VMs running on that node also become unavailable. The node is still running fine as are all the VMs, they're just no longer manageable. I looked on the node and everything appeared to be running fine. Looked on the server and ovirt-taskomatic was stopped (this seems to happen quite a bit).

since the introduction of ovirt-vnc-proxy and the updating of ovirt-viewer to user it the forward vnc functionality is no longer necessary / and incompatable w/ the current system. --- src/app/controllers/vm_controller.rb | 2 - src/app/models/host.rb | 9 - src/app/models/vm.rb | 36 ----

----- "Justin Clacherty" <justin at redfish-group.com> wrote: > > I ran ipa-server-install from the command line and the error it's > getting is this: > > Traceback (most recent call last): > File "/usr/sbin/ipa-server-install", line 41, in <module> > import ipaserver.krbinstance > File

run on startup by default like the other ovirt services --- conf/ovirt-vnc-proxy | 49 ++++++++ installer/modules/ovirt/manifests/ovirt.pp | 1 + ovirt-server.spec.in | 5 + src/vnc-proxy/vnc-proxy.rb | 167 ++++++++++++++++++++++++++++ 4 files changed, 222 insertions(+), 0 deletions(-) create mode 100755 conf/ovirt-vnc-proxy

I created a new VM today and it ran for a while before mysteriously disappearing. I logged in to the node it was running on to take a look at the logs and it looks as though the VM was shut down because the node ran out of memory. This particular node has 8GB in it and was running 4 VMs (including the crashed one). The memory assigned to each VM was 4G, 1.5G, 512M, 256M. It was the 256M VM

I did a yum update on my management server and now the ovirt gui is no longer accessable. Is it supposed to just work or do I need to do something after the yum update? Justin.

Are the build instructions out of date? I've been following them but when I get to "make update-app" I get make: *** No rule to make target `update-app'. Stop. I took a look in the Makefile and sure enough there's no updated-app target or update-host for that matter... What's the procedure now? Cheers, Justin.

After build from "next" git the ovirt-vnc-proxy init script won't start.The daemon line is set as "DAEMON=src/vnc-proxy/vnc-proxy.rb" This has to be "DAEMON=/usr/share/ovirt-server/vnc-proxy/vnc-proxy.rb" wright? -------------- next part -------------- An HTML attachment was scrubbed... URL:

Announcing oVirt 0.99 ===================== We are pleased to announce the release of oVirt 0.99, a significant step forward in stability and feature set for oVirt project users. Some highlights from the change log: * Improved installer, oVirt Server will now install with an existing FreeIPA setup present rather than insisting on installing FreeIPA from scratch * Anyterm console support --

--- internal.h | 3 +++ main.c | 3 +++ tunnel.c | 7 ++----- 3 files changed, 8 insertions(+), 5 deletions(-) diff --git a/internal.h b/internal.h index 80e675e..bd65922 100644 --- a/internal.h +++ b/internal.h @@ -71,6 +71,9 @@ extern gboolean check_cert; /* server we're connecting to */ extern const char* hostname; +/* port which to connect to the server via vnc */

virt-viewer-plugin is deprecated and will be replaced w/ ovirt-viewer-plugin, vm details pane uri indicates ovirt-viewer should be used with the specified hostname --- src/app/views/vm/show.rhtml | 18 ++++-------------- 1 files changed, 4 insertions(+), 14 deletions(-) diff --git a/src/app/views/vm/show.rhtml b/src/app/views/vm/show.rhtml index ffe5055..30b17cb 100644 ---

Hi, I had to reboot my management server today and when it comes back up the node machine has a status of "unavailable (enabled)". I saw this the last time I rebooted the management server and rebooting the node fixed the problem. What is the expected behaviour in this instance? My expectation would be that when the management server is reset, the nodes keep running (which they

The new merged qemu no longer has the ability to spawn a vnc viewer process in the bowels of the xend/qemu stack. In this patch we provide support for this use case in a different manner - one more akin to the mechanism used for `xm console'' and `xm create -c''. We introduce new xm options: xm create --vncviewer [--vncviewer-autopass] xm vncviewer [--vncviewer-autopass]

Hi, I'm having some problems building ovirt. The build fails during the final ovirt build stage in the instructions. The failure is because it can't find "/usr/share/ovirt-node-tools/ovirt-node-recipe.ks". I've checked and sure enough it's not there. Has anyone else come across this problem? Building on FC13 using the instructions found here:

Hi, When I click on "Edit Network" on my managed node in the hosts tab of the oVirt UI I only see one NIC. My managed node has 2 NICs, one on the guest network and one on the admin network. The NIC on the admin network is not listed in the network editor. Is this normal? I'm trying to create a VM and boot the cobbler profile I created for Fedora 10 but I can only boot the VM

Has anyone tried using glusterfs to handle live sysvol replication? Cheers, Justin.

I've uploaded a new libvirtd based on the latest release into F12 but it requires a selinux config which we do not have on the node. This is a temporary hack to make it work until we go to an F11 node. Must remember to remove this for F11!! Signed-off-by: Ian Main <imain at redhat.com> --- scripts/ovirt-functions | 5 +++++ 1 files changed, 5 insertions(+), 0 deletions(-) diff