Re: [one-users] Migration Problem
As suggested by Oliver in this case is better to save disk.0 and re-register it again. You could boot it at kvm2 with virsh deploy deployment.0 but this is only recommended if OpenNebula expects the VM to be in kvm2, if not it is better to recover kvm1 and recover (virsh deploy) it there. Cheers On Thu, Jul 4, 2013 at 3:00 PM, Umar Draz wrote: > Hi olivier > > I had installed that vm through .iso and used VD hd during installation, > here is my template of vm > > CPU="2" > DISK=[ > DEV_PREFIX="vd", > FORMAT="ext4", > SIZE="102400", > TYPE="fs" ] > DISK=[ > IMAGE_ID="2" ] > GRAPHICS=[ > LISTEN="0.0.0.0", > TYPE="VNC" ] > MEMORY="1024" > NIC=[ > MODEL="virtio", > NETWORK_ID="2" ] > OS=[ > ARCH="x86_64" ] > > The virtual machine is saved here /vms/cloud/datastores/0/26/ > > -rw-r--r-- 1 oneadmin cloud 906 Jul 4 07:09 deployment.0 > -rw-r--r-- 1 oneadmin cloud 107374182401 Jul 4 07:30 disk.0 > -rw-r--r-- 1 oneadmin cloud735051776 Jul 4 07:09 disk.1 > lrwxrwxrwx 1 oneadmin cloud 41 Jul 4 07:09 disk.1.iso -> > /var/cloud/one/var/datastores/0/26/disk.1 > > > and /vms/cloud/datastores/ is also available on kvm2, now please help me > how I can boot this vm on kvm2 > > Br. > > Umar > > > On Thu, Jul 4, 2013 at 5:52 PM, Olivier Sallou wrote: > >> >> On 07/04/2013 02:43 PM, Umar Draz wrote: >> >> Hi, >> >> I have 2 compute nodes (kvm1 and kvm2), both have connected with shared >> storage. I have 2 virtual machines running. >> >> 1 virtual machine on kvm1 and 1 virtual machine on kvm2 >> >> now my kvm1 machine has been crashed, how I can boot kvm1's virtual >> machine on kvm2, I had tried alot using Migrate, Migrate-Live but its not >> working. >> >> If your server crashed, you can't migrate a VM as far as I know. Open >> Nebula will fails to "stop" the process on crashed server. >> Usually, a crashed server leads to a VM lost. Your disk may even be >> corrupted. >> >> If what you need is high availability, you would need a high availability >> supported app with load balancing or failover mechanisms. >> >> IF you really need to restore this VM, I suppose you can copy the saved >> state of the VM disk and use it as a new image. >> >> Olivier >> >> >> >> Please anybody help me how I can do this? >> >> Br. >> >> Umar >> >> >> ___ >> Users mailing >> listUsers@lists.opennebula.orghttp://lists.opennebula.org/listinfo.cgi/users-opennebula.org >> >> >> -- >> Olivier Sallou >> IRISA / University of Rennes 1 >> Campus de Beaulieu, 35000 RENNES - FRANCE >> Tel: 02.99.84.71.95 >> >> gpg key id: 4096R/326D8438 (keyring.debian.org) >> Key fingerprint = 5FB4 6F83 D3B9 5204 6335 D26D 78DC 68DB 326D 8438 >> >> >> > > ___ > Users mailing list > Users@lists.opennebula.org > http://lists.opennebula.org/listinfo.cgi/users-opennebula.org > > -- -- Join us at OpenNebulaConf2013 in Berlin, 24-26 September, 2013 -- Ruben S. Montero, PhD Project co-Lead and Chief Architect OpenNebula - The Open Source Solution for Data Center Virtualization www.OpenNebula.org | rsmont...@opennebula.org | @OpenNebula ___ Users mailing list Users@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
Re: [one-users] Migration Problem
Hi olivier I had installed that vm through .iso and used VD hd during installation, here is my template of vm CPU="2" DISK=[ DEV_PREFIX="vd", FORMAT="ext4", SIZE="102400", TYPE="fs" ] DISK=[ IMAGE_ID="2" ] GRAPHICS=[ LISTEN="0.0.0.0", TYPE="VNC" ] MEMORY="1024" NIC=[ MODEL="virtio", NETWORK_ID="2" ] OS=[ ARCH="x86_64" ] The virtual machine is saved here /vms/cloud/datastores/0/26/ -rw-r--r-- 1 oneadmin cloud 906 Jul 4 07:09 deployment.0 -rw-r--r-- 1 oneadmin cloud 107374182401 Jul 4 07:30 disk.0 -rw-r--r-- 1 oneadmin cloud735051776 Jul 4 07:09 disk.1 lrwxrwxrwx 1 oneadmin cloud 41 Jul 4 07:09 disk.1.iso -> /var/cloud/one/var/datastores/0/26/disk.1 and /vms/cloud/datastores/ is also available on kvm2, now please help me how I can boot this vm on kvm2 Br. Umar On Thu, Jul 4, 2013 at 5:52 PM, Olivier Sallou wrote: > > On 07/04/2013 02:43 PM, Umar Draz wrote: > > Hi, > > I have 2 compute nodes (kvm1 and kvm2), both have connected with shared > storage. I have 2 virtual machines running. > > 1 virtual machine on kvm1 and 1 virtual machine on kvm2 > > now my kvm1 machine has been crashed, how I can boot kvm1's virtual > machine on kvm2, I had tried alot using Migrate, Migrate-Live but its not > working. > > If your server crashed, you can't migrate a VM as far as I know. Open > Nebula will fails to "stop" the process on crashed server. > Usually, a crashed server leads to a VM lost. Your disk may even be > corrupted. > > If what you need is high availability, you would need a high availability > supported app with load balancing or failover mechanisms. > > IF you really need to restore this VM, I suppose you can copy the saved > state of the VM disk and use it as a new image. > > Olivier > > > > Please anybody help me how I can do this? > > Br. > > Umar > > > ___ > Users mailing > listUsers@lists.opennebula.orghttp://lists.opennebula.org/listinfo.cgi/users-opennebula.org > > > -- > Olivier Sallou > IRISA / University of Rennes 1 > Campus de Beaulieu, 35000 RENNES - FRANCE > Tel: 02.99.84.71.95 > > gpg key id: 4096R/326D8438 (keyring.debian.org) > Key fingerprint = 5FB4 6F83 D3B9 5204 6335 D26D 78DC 68DB 326D 8438 > > > ___ Users mailing list Users@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
Re: [one-users] Migration Problem
On 07/04/2013 02:43 PM, Umar Draz wrote: > Hi, > > I have 2 compute nodes (kvm1 and kvm2), both have connected with > shared storage. I have 2 virtual machines running. > > 1 virtual machine on kvm1 and 1 virtual machine on kvm2 > > now my kvm1 machine has been crashed, how I can boot kvm1's virtual > machine on kvm2, I had tried alot using Migrate, Migrate-Live but its > not working. If your server crashed, you can't migrate a VM as far as I know. Open Nebula will fails to "stop" the process on crashed server. Usually, a crashed server leads to a VM lost. Your disk may even be corrupted. If what you need is high availability, you would need a high availability supported app with load balancing or failover mechanisms. IF you really need to restore this VM, I suppose you can copy the saved state of the VM disk and use it as a new image. Olivier > > Please anybody help me how I can do this? > > Br. > > Umar > > > ___ > Users mailing list > Users@lists.opennebula.org > http://lists.opennebula.org/listinfo.cgi/users-opennebula.org -- Olivier Sallou IRISA / University of Rennes 1 Campus de Beaulieu, 35000 RENNES - FRANCE Tel: 02.99.84.71.95 gpg key id: 4096R/326D8438 (keyring.debian.org) Key fingerprint = 5FB4 6F83 D3B9 5204 6335 D26D 78DC 68DB 326D 8438 ___ Users mailing list Users@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
[one-users] Migration Problem
Hi, I have 2 compute nodes (kvm1 and kvm2), both have connected with shared storage. I have 2 virtual machines running. 1 virtual machine on kvm1 and 1 virtual machine on kvm2 now my kvm1 machine has been crashed, how I can boot kvm1's virtual machine on kvm2, I had tried alot using Migrate, Migrate-Live but its not working. Please anybody help me how I can do this? Br. Umar ___ Users mailing list Users@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
Re: [one-users] Migration problem
Hello , I faced this scenario a few days back and this is due to the fact that there are 2 versions of qemu that you have . The machine='pc' part will not appear if you use the qemu that is installed in /usr/libexec/qemu-kvm instead of the other one. You can create a soft link as follows : ls -l /usr/bin/kvm lrwxrwxrwx 1 root root 21 Mar 22 00:44 /usr/bin/kvm -> /usr/libexec/qemu-kvm Hope that helps. Copy pasting from another thread: By default, libvirt will use rhel5.4.0 machine type, which is supported by kvm-83-164.el5_5.12 but not supported by upstream qemu (you can see the supported machine types in the log above). So you have two options: - either use /usr/libexec/qemu-kvm as the emulator - or explicitly change machine type to something which is supported by /usr/bin/qemu-system-x86_64 (e.g., pc-0.12) --- >* this supports your "machine = pc" part.* cheers Ranjan -- Forwarded message -- From: Date: Fri, Mar 25, 2011 at 4:40 PM Subject: Users Digest, Vol 37, Issue 74 To: users@lists.opennebula.org Send Users mailing list submissions to users@lists.opennebula.org To subscribe or unsubscribe via the World Wide Web, visit http://lists.opennebula.org/listinfo.cgi/users-opennebula.org or, via email, send a message with subject or body 'help' to users-requ...@lists.opennebula.org You can reach the person managing the list at users-ow...@lists.opennebula.org When replying, please edit your Subject line so it is more specific than "Re: Contents of Users digest..." Today's Topics: 1. Re: Migration problem (George L. Emigh) 2. libvirt unstalbe with open nebula (christophe bonnaud) 3. Re: force to update cluster nodes info (kna...@gmail.com) 4. VM config template (kna...@gmail.com) 5. Re: Permission libvirt/qemu driver (Guillaume GENS) -- Message: 1 Date: Thu, 24 Mar 2011 16:08:03 -0400 From: "George L. Emigh" To: users@lists.opennebula.org Subject: Re: [one-users] Migration problem Message-ID: <201103241608.03152.geo...@podglobal.com> Content-Type: Text/Plain; charset="iso-8859-1" How can I change the machine type from the default of rhel5.4.0 to pc from within the VM template? if I add to the vm template: OS = [ ARCH = "x86_64", MACHINE = "pc" ] and even though onevm show reveals: OS=[ ARCH=x86_64, MACHINE=pc ] deployment.0 still only shows: hvm as opposed to the expected: hvm On Thursday March 17 2011, George L. Emigh wrote: > Seems I have missed some key detail, when I attempt to migrate a vm it > fails. > > I can run a vm on the other host with libvirt / virt manager fine. > > Any ideas come to mind or a suggestion on where to look? > > Before attempted migration the image was owned by oneadmin:cloud > The image file becomes owned by root > s -l /var/lib/one/images/229ec3e88658934ce75dac63633b83a60ac48cf2 > -rw-rw 1 root root 8589934592 Mar 17 15:08 > /var/lib/one/images/229ec3e88658934ce75dac63633b83a60ac48cf2 > > > The VM log file shows > > Thu Mar 17 15:08:31 2011 [LCM][I]: New VM state is BOOT > Thu Mar 17 15:08:31 2011 [VMM][I]: Generating deployment file: > /var/lib/one/49/deployment.0 Thu Mar 17 15:08:32 2011 [LCM][I]: New VM > state is RUNNING > Thu Mar 17 15:09:01 2011 [LCM][I]: New VM state is SAVE_MIGRATE > Thu Mar 17 15:09:09 2011 [LCM][I]: New VM state is PROLOG_MIGRATE > Thu Mar 17 15:09:09 2011 [TM][I]: tm_mv.sh: Will not move, source and > destination are equal Thu Mar 17 15:09:09 2011 [LCM][I]: New VM state is > BOOT > Thu Mar 17 15:09:12 2011 [VMM][I]: Command execution fail: 'if [ -x > "/var/tmp/one/vmm/kvm/restore" ]; then /var/tmp/one/vmm/kvm/restore > /var/lib/one//49/images/checkpoint; else > exit 42; fi' Thu Mar 17 15:09:12 2011 [VMM][I]: STDERR follows. > Thu Mar 17 15:09:12 2011 [VMM][I]: error: Failed to restore domain from > /var/lib/one//49/images/checkpoint Thu Mar 17 15:09:12 2011 [VMM][I]: > error: cannot close file: Bad file descriptor Thu Mar 17 15:09:12 2011 > [VMM][I]: ExitCode: 1 > Thu Mar 17 15:09:12 2011 [VMM][E]: Error restoring VM, error: Failed to > restore domain from /var/lib/one//49/images/checkpoint Thu Mar 17 > 15:09:13 2011 [DiM][I]: New VM state is FAILED > Thu Mar 17 15:09:13 2011 [TM][W]: Ignored: LOG - 49 tm_delete.sh: > Deleting /var/lib/one//49/images > > Thu Mar 17 15:09:13 2011 [TM][W]: Ignored: LOG - 49 tm_delete.sh: > Executed "rm -rf /var/lib/one//49/images". > > Thu Mar 17 15:09:13 2011 [TM][W]: Ignored: TRANSFER SUCCESS 49 - > > > The other host seems ok > onehost list > ID NAME CLUSTER RVM TCPU FCPU ACPUTMEMFMEM > STAT 0 shag
Re: [one-users] Migration problem
How can I change the machine type from the default of rhel5.4.0 to pc from within the VM template? if I add to the vm template: OS = [ ARCH = "x86_64", MACHINE = "pc" ] and even though onevm show reveals: OS=[ ARCH=x86_64, MACHINE=pc ] deployment.0 still only shows: hvm as opposed to the expected: hvm On Thursday March 17 2011, George L. Emigh wrote: > Seems I have missed some key detail, when I attempt to migrate a vm it > fails. > > I can run a vm on the other host with libvirt / virt manager fine. > > Any ideas come to mind or a suggestion on where to look? > > Before attempted migration the image was owned by oneadmin:cloud > The image file becomes owned by root > s -l /var/lib/one/images/229ec3e88658934ce75dac63633b83a60ac48cf2 > -rw-rw 1 root root 8589934592 Mar 17 15:08 > /var/lib/one/images/229ec3e88658934ce75dac63633b83a60ac48cf2 > > > The VM log file shows > > Thu Mar 17 15:08:31 2011 [LCM][I]: New VM state is BOOT > Thu Mar 17 15:08:31 2011 [VMM][I]: Generating deployment file: > /var/lib/one/49/deployment.0 Thu Mar 17 15:08:32 2011 [LCM][I]: New VM > state is RUNNING > Thu Mar 17 15:09:01 2011 [LCM][I]: New VM state is SAVE_MIGRATE > Thu Mar 17 15:09:09 2011 [LCM][I]: New VM state is PROLOG_MIGRATE > Thu Mar 17 15:09:09 2011 [TM][I]: tm_mv.sh: Will not move, source and > destination are equal Thu Mar 17 15:09:09 2011 [LCM][I]: New VM state is > BOOT > Thu Mar 17 15:09:12 2011 [VMM][I]: Command execution fail: 'if [ -x > "/var/tmp/one/vmm/kvm/restore" ]; then /var/tmp/one/vmm/kvm/restore > /var/lib/one//49/images/checkpoint; else > exit 42; fi' Thu Mar 17 15:09:12 2011 [VMM][I]: STDERR follows. > Thu Mar 17 15:09:12 2011 [VMM][I]: error: Failed to restore domain from > /var/lib/one//49/images/checkpoint Thu Mar 17 15:09:12 2011 [VMM][I]: > error: cannot close file: Bad file descriptor Thu Mar 17 15:09:12 2011 > [VMM][I]: ExitCode: 1 > Thu Mar 17 15:09:12 2011 [VMM][E]: Error restoring VM, error: Failed to > restore domain from /var/lib/one//49/images/checkpoint Thu Mar 17 > 15:09:13 2011 [DiM][I]: New VM state is FAILED > Thu Mar 17 15:09:13 2011 [TM][W]: Ignored: LOG - 49 tm_delete.sh: > Deleting /var/lib/one//49/images > > Thu Mar 17 15:09:13 2011 [TM][W]: Ignored: LOG - 49 tm_delete.sh: > Executed "rm -rf /var/lib/one//49/images". > > Thu Mar 17 15:09:13 2011 [TM][W]: Ignored: TRANSFER SUCCESS 49 - > > > The other host seems ok > onehost list > ID NAME CLUSTER RVM TCPU FCPU ACPUTMEMFMEM > STAT 0 shag default04004004007.6G > 6.8G on 1 klingon default14004003007.6G > 7G on > > > From the libvirt log on the other host > cat one-49.log > 2011-03-17 15:09:09.857: starting up > LC_ALL=C > PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin HOME=/ > USER=root QEMU_AUDIO_DRV=none /usr/bin/kvm -S -M rhel5.4.0 -enable-kvm > -m 2048 -smp 2,sockets=2,cores=1,threads=1 -name one-49 -uuid > 7b18a07e-bcc4-ceed-6ace-c31ecf90378a -nodefconfig -nodefaults -chardev > socket,id=monitor,path=/var/lib/libvirt/qemu/one-49.monitor,server,nowai > t -mon chardev=monitor,mode=control -rtc base=utc -no-acpi -boot c -drive > file=/var/lib/one//49/images/disk.0,if=none,id=drive-virtio-disk0,boot=o > n,format=raw -device > virtio-blk-pci,bus=pci.0,addr=0x4,drive=drive-virtio-disk0,id=virtio-dis > k0 -drive > file=/var/lib/one//49/images/disk.1,if=none,id=drive-virtio-disk1,format > =raw -device > virtio-blk-pci,bus=pci.0,addr=0x5,drive=drive-virtio-disk1,id=virtio-dis > k1 -drive > file=/var/lib/one//49/images/disk.2,if=none,media=cdrom,id=drive-ide0-1- > 0,readonly=on,format=raw -device > ide-drive,bus=ide.1,unit=0,drive=drive-ide0-1-0,id=ide0-1-0 - netdev > tap,fd=44,id=hostnet0 -device > virtio-net-pci,netdev=hostnet0,id=net0,mac=02:00:c0:a8:45:03,bus=pci.0,a > ddr=0x3 -usb -vnc 127.0.0.1:49 -vga cirrus -incoming exec:cat -device > virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x6 Supported machines > are: > pc Standard PC (alias of pc-0.13) > pc-0.13Standard PC (default) > pc-0.12Standard PC > pc-0.11Standard PC, qemu 0.11 > pc-0.10Standard PC, qemu 0.10 > isapc ISA-only PC > 2011-03-17 15:09:12.859: shutting down > > > > From top of oned.log > > DB=BACKEND=sqlite > DEBUG_LEVEL=3 > DEFAULT_DEVICE_PREFIX=hd > DEFAULT_IMAGE_TYPE=OS > HM_MAD=EXECUTABLE=one_hm > HOST_MONITORING_INTERVAL=60 > IMAGE_REPOSITORY_PATH=/var/lib/one//images > IM_MAD=ARGUMENTS=kvm,EXECUTABLE=one_im_ssh,NAME=im_kvm > MAC_PREFIX=02:00 > MANAGER_TIMER=15 > NETWORK_SIZE=254 > PORT=2633 > SCRIPTS_REMOTE_DIR=/var/tmp/one > TM_MAD=ARGUMENTS=tm_nfs/tm_nfs.conf,EXECUTABLE=one_tm,NAME=tm_nfs > VM_DIR=/var/lib/one/ > VM_HOOK=ARGUMENTS=$VMID,COMM
[one-users] Migration problem
Seems I have missed some key detail, when I attempt to migrate a vm it fails. I can run a vm on the other host with libvirt / virt manager fine. Any ideas come to mind or a suggestion on where to look? Before attempted migration the image was owned by oneadmin:cloud The image file becomes owned by root s -l /var/lib/one/images/229ec3e88658934ce75dac63633b83a60ac48cf2 -rw-rw 1 root root 8589934592 Mar 17 15:08 /var/lib/one/images/229ec3e88658934ce75dac63633b83a60ac48cf2 The VM log file shows Thu Mar 17 15:08:31 2011 [LCM][I]: New VM state is BOOT Thu Mar 17 15:08:31 2011 [VMM][I]: Generating deployment file: /var/lib/one/49/deployment.0 Thu Mar 17 15:08:32 2011 [LCM][I]: New VM state is RUNNING Thu Mar 17 15:09:01 2011 [LCM][I]: New VM state is SAVE_MIGRATE Thu Mar 17 15:09:09 2011 [LCM][I]: New VM state is PROLOG_MIGRATE Thu Mar 17 15:09:09 2011 [TM][I]: tm_mv.sh: Will not move, source and destination are equal Thu Mar 17 15:09:09 2011 [LCM][I]: New VM state is BOOT Thu Mar 17 15:09:12 2011 [VMM][I]: Command execution fail: 'if [ -x "/var/tmp/one/vmm/kvm/restore" ]; then /var/tmp/one/vmm/kvm/restore /var/lib/one//49/images/checkpoint; else exit 42; fi' Thu Mar 17 15:09:12 2011 [VMM][I]: STDERR follows. Thu Mar 17 15:09:12 2011 [VMM][I]: error: Failed to restore domain from /var/lib/one//49/images/checkpoint Thu Mar 17 15:09:12 2011 [VMM][I]: error: cannot close file: Bad file descriptor Thu Mar 17 15:09:12 2011 [VMM][I]: ExitCode: 1 Thu Mar 17 15:09:12 2011 [VMM][E]: Error restoring VM, error: Failed to restore domain from /var/lib/one//49/images/checkpoint Thu Mar 17 15:09:13 2011 [DiM][I]: New VM state is FAILED Thu Mar 17 15:09:13 2011 [TM][W]: Ignored: LOG - 49 tm_delete.sh: Deleting /var/lib/one//49/images Thu Mar 17 15:09:13 2011 [TM][W]: Ignored: LOG - 49 tm_delete.sh: Executed "rm -rf /var/lib/one//49/images". Thu Mar 17 15:09:13 2011 [TM][W]: Ignored: TRANSFER SUCCESS 49 - The other host seems ok onehost list ID NAME CLUSTER RVM TCPU FCPU ACPUTMEMFMEM STAT 0 shag default04004004007.6G6.8G on 1 klingon default14004003007.6G 7G on >From the libvirt log on the other host cat one-49.log 2011-03-17 15:09:09.857: starting up LC_ALL=C PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin HOME=/ USER=root QEMU_AUDIO_DRV=none /usr/bin/kvm -S -M rhel5.4.0 -enable-kvm -m 2048 -smp 2,sockets=2,cores=1,threads=1 -name one-49 -uuid 7b18a07e-bcc4-ceed-6ace-c31ecf90378a -nodefconfig -nodefaults -chardev socket,id=monitor,path=/var/lib/libvirt/qemu/one-49.monitor,server,nowait -mon chardev=monitor,mode=control -rtc base=utc -no-acpi -boot c -drive file=/var/lib/one//49/images/disk.0,if=none,id=drive-virtio-disk0,boot=on,format=raw -device virtio-blk-pci,bus=pci.0,addr=0x4,drive=drive-virtio-disk0,id=virtio-disk0 -drive file=/var/lib/one//49/images/disk.1,if=none,id=drive-virtio-disk1,format=raw -device virtio-blk-pci,bus=pci.0,addr=0x5,drive=drive-virtio-disk1,id=virtio-disk1 -drive file=/var/lib/one//49/images/disk.2,if=none,media=cdrom,id=drive-ide0-1-0,readonly=on,format=raw -device ide-drive,bus=ide.1,unit=0,drive=drive-ide0-1-0,id=ide0-1-0 - netdev tap,fd=44,id=hostnet0 -device virtio-net-pci,netdev=hostnet0,id=net0,mac=02:00:c0:a8:45:03,bus=pci.0,addr=0x3 -usb -vnc 127.0.0.1:49 -vga cirrus -incoming exec:cat -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x6 Supported machines are: pc Standard PC (alias of pc-0.13) pc-0.13Standard PC (default) pc-0.12Standard PC pc-0.11Standard PC, qemu 0.11 pc-0.10Standard PC, qemu 0.10 isapc ISA-only PC 2011-03-17 15:09:12.859: shutting down >From top of oned.log DB=BACKEND=sqlite DEBUG_LEVEL=3 DEFAULT_DEVICE_PREFIX=hd DEFAULT_IMAGE_TYPE=OS HM_MAD=EXECUTABLE=one_hm HOST_MONITORING_INTERVAL=60 IMAGE_R
