similar to: [PATCH] introduce option to always PXE-boot a VM

Previously, a pxe-booted vm would always boot to HD at next startup. Signed-off-by: Nicolas Ochem <nicolas.ochem at alcatel-lucent.com> --- src/app/controllers/vm_controller.rb | 1 + src/app/models/vm.rb | 15 +++++++++++---- src/app/views/vm/_form.rhtml | 2 +- src/task-omatic/taskomatic.rb | 13 +++++++++++-- 4 files changed, 24 insertions(+), 7

There was no release since virtio support was introduced, so a proper migration is not necessary. Signed-off-by: Nicolas Ochem <nicolas.ochem at gmail.com> --- src/app/controllers/vm_controller.rb | 6 ++- src/app/models/nic.rb | 2 + src/app/views/vm/_form.rhtml | 25 +++++++++------- src/db/migrate/046_add_model_to_nic.rb | 29 ++++++++++++++++++

Signed-off-by: Nicolas Ochem <nicolas.ochem at alcatel-lucent.com> --- src/config/initializers/mongrel_patch.rb | 11 +++++++++++ 1 files changed, 11 insertions(+), 0 deletions(-) create mode 100644 src/config/initializers/mongrel_patch.rb diff --git a/src/config/initializers/mongrel_patch.rb b/src/config/initializers/mongrel_patch.rb new file mode 100644 index 0000000..ae2bcf4 ---

----- "Nicolas Ochem" <nicolas.ochem at alcatel-lucent.com> wrote: > > However for this to work you need to add runtime_mode=ovirt in > pxelinux.cfg/default in the kernel boot options. > Fantastic! Thanks Nicolas, that's done the trick. The node now boots and sets up it's interfaces. The host now appears in the management server user interface and

--- src/app/models/vm.rb | 2 ++ src/app/views/vm/_form.rhtml | 23 +++++++++++++++++++++++ 2 files changed, 25 insertions(+), 0 deletions(-) diff --git a/src/app/models/vm.rb b/src/app/models/vm.rb index 3e0a6fa..9d326ac 100644 --- a/src/app/models/vm.rb +++ b/src/app/models/vm.rb @@ -464,6 +464,8 @@ class Vm < ActiveRecord::Base

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:

I know this has been discussed many moons ago, but my search attempts on the mailing list archive and Google have not yielded any more information. Here's my situation: Currently all clients boot a generic "boot menu" which allows them to choose different images. However I now have a PPC client that can not load the x86 complied pxelinux boot menu image. So I now want to have

Hi all, i have trouble to PXE boot KVM-based (network of Linux-bridge) Virtual Machines: very slow transfer pxelinux.cfg. ====== tcpdump on KVM host system ==== [root at kvm-test01 ~]# tcpdump -i virbr1 | grep -v ssh | grep 10.0.5.187 tcpdump: verbose output suppressed, use -v or -vv for full protocol decode listening on virbr1, link-type EN10MB (Ethernet), capture size 96 bytes 17:57:29.809278

I will try to explain problem as good as possible. I just finished building my ovirt server from the git repo. Added a vm in cobbler. But when i install a vm it will install on breth0 on my managed node(this is my admin network(199.1.10.*)). Now it is not reachable on the quest network. Isn't this suppose to be breth1(guest network(192.168.50.*))? The management server has ip

By default it's 120 ms, but can be changed through command line arguments. Signed-off-by: Darryl L. Pierce <dpierce at redhat.com> --- autotest.sh | 16 ++++++++++------ 1 files changed, 10 insertions(+), 6 deletions(-) diff --git a/autotest.sh b/autotest.sh index c67931a..bcd9bd5 100755 --- a/autotest.sh +++ b/autotest.sh @@ -62,6 +62,7 @@ Usage: $ME [-n test_name] [LOGFILE] -i:

From: root <root at chappy.(none)> Use ovirt-config-logging in /etc/init.d/ovirt --- scripts/ovirt | 19 ++++--------------- scripts/ovirt-config-logging | 2 +- scripts/ovirt-functions | 4 ++++ 3 files changed, 9 insertions(+), 16 deletions(-) diff --git a/scripts/ovirt b/scripts/ovirt index 4ff03f2..0c5e3be 100755 --- a/scripts/ovirt +++ b/scripts/ovirt @@

Hello, I got in a situation where pxelinux 3.7 (or 3.6) reboots constantly after loading the configuration file and displaying the 'display' option file, but never showing 'boot:' prompt. config file is following: # PXE SYSLINUX config file - look at # http://syslinux.zytor.com/faq.php for syntax # # ---------- This is gate configure file ------- timeout 20 prompt 1 display

Hello, I have set up 2 PXE servers, on Linux Debian Sarge and Etch, on which I use syslinux + ISC dhcp3 + tftp-hpa for booting. The older one, on Sarge, has been working fine for more than a year, great :-) The new one, on Etch, with the exact same config files, does not : the DHCP part seems to work, but at the end pxelinux seems to lose the server's IP address; this what I see on the

Hallo I have a kvm vm that I am attempting to boot from pxe. The dhcp works perfectly and I can see the VM in the pxe server arp. but the tftp just times out. I don't see any tftp traffic on either the physical host or on the pie server. I am using a bridged interface. I have tried using several virtual nic drivers, several different mac addresses and several different ips. on the physical

There were two javascript functions with the same name, and the wrong one was being called. I renamed one to avoid conflicts. Signed-off-by: Scott Seago <sseago at redhat.com> --- src/app/views/vm/add_to_smart_pool.rhtml | 3 ++- src/public/javascripts/ovirt.js | 2 +- 2 files changed, 3 insertions(+), 2 deletions(-) diff --git a/src/app/views/vm/add_to_smart_pool.rhtml

Is there anyway to set dynamically set dhcp options when chain loading another pxe boot loader? I'm setting up a pxelinux network install server and one operating system I want to support is freebsd. Freebsd has its own pxe loader called pxeboot that you can use. You just have to boot it from tftp and set the root-path dhcp option (option 17) to the location of your nfs server with the

When I try to pxe boot a new VM through lvm and libxl I find about 1 in 10 times the pxe requests will be acknlwledged but if I go into the interacive ipxe screens it will boot every time. Is it possible that the network configuration is not built when the VM starts trying to get its pxe address? -- Alvin Starr || voice: (905)513-7688 Netvel Inc. ||

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 ---

All, (This may be a Gene question, see http://www.syslinux.org/wiki/index.php/Development/Testing). I'd like to find a virtualization env to test and demo the new UEFI-based PXE boot in pxelinux. I've tried Virtualbox (BIOS-based PXE boot only). And I've tried VMWare workstation 20 (ditto). I know VMWare ESXi will now do UEFI PXE boot, I've seen it as work. But for home or

Hi. I try to create VM in oVirt interface. New VM failed to start In oVirt interface Tasks log: Error creating virtual machine: Error: Error creating new domain (virDomainCreate). Subsystem qemu: internal error unable to start guest: bind(unix:/var/lib/libvirt/qemu/test.monitor): Permission denied qemu: could not open monitor device 'unix:/var/lib/libvirt/qemu/