Paravirtualized Guest Error

Hello i have the following issue.
I have created a paravirtualized guest ... and i cannot start it :(
when issuing the xm create command ... i get Error :(uid,'VM_METRICS)
i have searched the logs and i found that boot loader did not load.
here is the error:
ERROR (XendBootloader:171) Boot loader didn't return any data!
ERROR (XendDomainInfo:430) VM start failed
can anyone help ? :P

user8100624 wrote:
I have created a paravirtualized guest ... and i cannot start it :(Can you give us more detail on how you created this guest?

Similar Messages

  • Paravirtualized Guest Machine from an OEL 6 GA Install Media iso?

    Is it possible to create a paravirtualized guest from an Oracle Linux 6 GA iso?l
    I would prefer a jeos image but I have not been able to find one.
    I have tried this using the vm server as the nfs server with no success.
    vm server 2.20
    cp oel6.iso /OVS/ios_pool/
    cd /OVS/iso_pool/
    mkdir /OVS/iso_pool/iso
    mount -o loop oel6.iso iso
    vi /etc/exports
    /OVS/iso_pool/iso *(rw)
    service nfs restart
    When creating the guest machine I choose paravirtualiezed and enter the following nfs entry:
    nfs:server-name/OVS/ios_pool/iso
    or
    nfs:server-ip-address/OVS/ios_pool/iso
    I receive the following in the log:
    =============================================================================
    Check memory, mac address and networktype
    Register virtual machine img
    Register virtual machine geninfo
    Register virtual machine networks
    Register virtual machine disks
    Create PVM
    Failed. Result -failed:<Exception: failed:<Exception: ['virt-install', '--paravirt', '--name=2971_oel6', '--ram=1024', '--vcpus=2', '--vnc', '--vnclisten=0.0.0.0', '--vncpasswd=/tmp/tmpcz2RA3', '--noautoconsole', '--location=nfs:10.0.6.177:/OVS/iso_pool/iso', '--keymap=en-us', '--mac=00:16:3E:42:AF:50', '--bridge=vlan10', '--file=/var/ovs/mount/D684E789EFE44A1181C387168A518F9A/running_pool/2971_oel6/System.img', '--file-size=5.0'] => ERROR: Invalid NFS location given: [Errno 2] No such file or directory: '/var/lib/xen/xennfs.Njoyex/images/xen/vmlinuz'
    >
    StackTrace:
    File "/opt/ovs-agent-2.3/OVSXXenVMInstall.py", line 317, in xen_install_vm_para
    run_cmd(args=cmdlist)
    File "/opt/ovs-agent-2.3/OVSCommons.py", line 69, in run_cmd
    raise Exception('%s => %s' % (cmdlist, p.childerr.read()))
    >
    StackTrace:
    File "/opt/ovs-agent-2.3/OVSSiteVMInstall.py", line 197, in install_vm_para
    else: raise Exception(rs)
    =============================================================================

    I've got a few OL6 guests up and running on my OVS 2.2.2 servers now. I managed to convert one of them to a PV guest by hacking together a vm.cfg.
    The dmesg|grep -i xen shows me that the guest kernel is running in paravirt mode.
    My problem is the OVM Manager is still showing this guest as a fully virtualized guest. Is there a better/proper way to convert an HVM guest to PV guest?
    Here is the dmesg output:
    h4. [root@prdjboss01 ~]# dmesg|grep -i xen
    Xen: 0000000000000000 - 00000000000a0000 (usable)
    Xen: 00000000000a0000 - 0000000000100000 (reserved)
    Xen: 0000000000100000 - 00000001f4000000 (usable)
    #1 [00050e7000 - 0005114000] XEN PAGETABLES ==> [00050e7000 - 0005114000]
    #5 [0004144000 - 00050e7000] XEN START INFO ==> [0004144000 - 00050e7000]
    Booting paravirtualized kernel on Xen
    Xen version: 3.4.0 (preserve-AD)
    Xen: using vcpu_info placement
    Xen: using vcpuop timer interface
    installing Xen timer for CPU 0
    installing Xen timer for CPU 1
    xen_balloon: Initialising balloon driver.
    Switching to clocksource xen
    input: Xen Virtual Keyboard as /devices/virtual/input/input1
    input: Xen Virtual Pointer as /devices/virtual/input/input2
    XENBUS: Device with no driver: device/vbd/768
    XENBUS: Device with no driver: device/vbd/832
    XENBUS: Device with no driver: device/vbd/5632
    XENBUS: Device with no driver: device/vif/0
    XENBUS: Device with no driver: device/console/0
    Initialising Xen virtual ethernet driver.

  • No paravirtualized guest systems are running on OVM Server

    Hello all,
    i have some problems to run a opensuse11 oder SLES10 same as debian4 as paravirtualized system on Oracle VM Server. (fullvirtualized systems run nicely)
    if i try creating paravirt. guest with VM manager the same error is printed as trying virt-install.
    ERROR: Invalid NFS location given: [Errno 2] No such file or directory: '/var/lib/xen/xennfs.cMuPG9/images/xen/vmlinuz'
    i don't know what can be wrong. I checked in vm server the location
    /var/lib/xen/xennfs.cMuPG9/images/xen/vmlinuz but i can't found the folders.
    on nfs-share (an original iso file from SLES10-DVD) the as explained above. Nothing to find.
    the questions i have are:
    can oracle vm server use SLSE10 as paravirt-guest? (Oracle Docu didn't say somesthing about SLES10)
    How i can find a solution to fix this problem? Because i neeed SLES in these VM's as paravirtualized (howtos wikis i need)
    greets anirde

    Hello,
    # cat /proc/cpuinfo | grep flags
    flags          : fpu tsc msr pae mce cx8 apic mtrr mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe nx lm constant_tsc pni monitor ds_cpl vmx tm2 cx16 xtpr lahf_lm
    hardwarevirtualising are no problem. but i dont like to use hardwarevirtualising. for more performence i need paravirtualising. so i try to install suse11/SLES10 with vm manager but it dosn't work. :(
    greets anirde

  • OracleVM and paravirtualized guest - "Boot loader didn't return any data!"

    Hi folks,
    we're having a problem here: We have installed the latest version of Oracle VM Server on a machine that does not provide hardware virtualization support (i.e., no Intel VT or similar). As a result, we will not be able to make use of hardware virtualized VMs, but according to the Oracle docs, we should be able to set up virtual machines of the paravirtualized domain type. So far, so good.
    Also according to the docs, when setting up a PVM, one cannot use an ISO image located in a storage repository in order to start the installation, but instead one would have the mount the installation ISO somewhere, make available it's contents via NFS (or HTTP / FTP), and then set up the newly created virtual machine to attempt a PXE boot, specifying the location where the contents of the ISO have been placed (i.e.: nfs:host:/path/to/mounted/iso). All of this is decribed very well in the Oracle VM Server docs (chapter 8), but somehow it still doesn't seem to work for us.
    What happens is this: When we attempt to boot our PVM via PXE, specifying the NFS location where we've made the contents of the ISO available, we always get this:
    Job Construction Phase
    begin()
    Appended operation 'Virtual Machine Start' to object '0004fb0000060000ab1b8caa045cc7a8 (VMOEL6)'.
    commit()
    Completed Step: COMMIT
    Objects and Operations
    Object (IN_USE): [VirtualMachine] 0004fb0000060000ab1b8caa045cc7a8 (VMOEL6)
    Operation: Virtual Machine Start
    Object (IN_USE): [Vnic] 0004fb0000070000797b4c17ae1154dd (00:21:f6:00:00:0a)
    Object (IN_USE): [StorageElement] 0004fb0000180000eb569988de92923e (SATA_WDC_WD5001ABYS-_WD-WCAS86231834)
    Object (IN_USE): [VirtualDisk] 0004fb0000120000cdbce172d90322c3.img (VMOEL6Disk1)
    Object (IN_USE): [VmDiskMapping] 0004fb0000130000aaa3f5eb57705a5b
    Object (IN_USE): [VmDiskMapping] 0004fb0000130000f1438eedcfee01de
    Job Running Phase at 18:11 on Fri, Oct 14, 2011
    Job Participants: [44:45:4c:4c:37:00:10:46:80:4b:b8:c0:4f:59:31:4a (ORAVM1)]
    Actioner
    Starting operation 'Virtual Machine Start' on object '0004fb0000060000ab1b8caa045cc7a8 (VMOEL6)'
    Job Internal Error (Operation)com.oracle.ovm.mgr.api.exception.FailedOperationException: OVMAPI_4010E Attempt to send command: dispatch to server: ORAVM1 failed. OVMAPI_4004E Server Failed Command: dispatch https://?uname?:[email protected]:8899/api/1 start_vm 0004fb00000300001d1619c621b16838 0004fb0000060000ab1b8caa045cc7a8, Status: org.apache.xmlrpc.XmlRpcException: exceptions.RuntimeError:Command: ['xm', 'create', '/OVS/Repositories/0004fb00000300001d1619c621b16838/VirtualMachines/0004fb0000060000ab1b8caa045cc7a8/vm.cfg'] failed (1): Error: Boot loader didn't return any data!
    We've used multiple different ISOs in order to test this, including Oracle Enterprise Linux (just like the example in the docs does), however, we never get any further than this error message.
    Any ideas what we might be doing wrong?
    Greetings,
    Nils

    Hi Avi,
    thanks for your reply! Actually, I believe I checked the NFS reachability already. Here's what I can do on the VM server:
    [root@ORAVM1 ~]# ls /mnt/test
    [root@ORAVM1 ~]# mount.nfs 10.0.0.220:/mnt/iso /mnt/test
    [root@ORAVM1 ~]# ls /mnt/test
    EFI eula.py images media.repo README-en.html RELEASE-NOTES-x86_64-en RELEASE-NOTES-x86-en.html RPM-GPG-KEY Server
    EULA GPL isolinux Packages RELEASE-NOTES-en RELEASE-NOTES-x86_64-en.html repodata RPM-GPG-KEY-oracle supportinfo
    eula.en_US HighAvailability LoadBalancer README-en RELEASE-NOTES-en.html RELEASE-NOTES-x86-en ResilientStorage ScalableFileSystem TRANS.TBL
    [root@ORAVM1 ~]#
    So, I seem to be able to mount the NFS export correctly (what we're seeing are the contents of an Oracle Enterprise Linux ISO). And when setting up the VM, I specify "nfs:10.0.0.220:/mnt/iso" as the PXE boot path. Still it doesn't seem to work. :-(
    ovs-agent.log doesn't seem to contain too many additinal information of value either. Here's a snippet of what seems to happen when I power up my VM, but I guess there's nothing really new in there:
    [2011-10-20 12:56:37 22423] ERROR (OVSServices:61) dispatch error: start_vm: <Fault 1: "exceptions.RuntimeError:Command: ['xm', 'create', '/OVS/Repositories/0004fb00000300001d1619c621b16838/VirtualMachines/0004fb0000060000ab1b8caa045cc7a8/vm.cfg'] failed (1): Error: Boot loader didn't return any data!\n ">
    [2011-10-20 12:56:37 22423] ERROR (OVSCommons:142) catch_error: <Fault 1: "exceptions.RuntimeError:Command: ['xm', 'create', '/OVS/Repositories/0004fb00000300001d1619c621b16838/VirtualMachines/0004fb0000060000ab1b8caa045cc7a8/vm.cfg'] failed (1): Error: Boot loader didn't return any data!\n ">
    Traceback (most recent call last):
    File "/opt/ovs-agent-3.0/OVSCommons.py", line 140, in wrapper
    return func(*args)
    File "/opt/ovs-agent-3.0/OVSServices.py", line 59, in dispatch
    return getattr(sp, func)(*args)
    File "/opt/ovs-agent-3.0/utils/xmlrpclib.py", line 1099, in __call__
    return self.__send(self.__name, args)
    File "/opt/ovs-agent-3.0/utils/xmlrpclib.py", line 1386, in __request
    verbose=self.__verbose
    File "/opt/ovs-agent-3.0/utils/xmlrpclib.py", line 1150, in request
    return self._parse_response(h.getfile(), sock)
    File "/opt/ovs-agent-3.0/utils/xmlrpclib.py", line 1289, in parseresponse
    return u.close()
    File "/opt/ovs-agent-3.0/utils/xmlrpclib.py", line 746, in close
    raise Fault(**self._stack[0])
    Fault: <Fault 1: "exceptions.RuntimeError:Command: ['xm', 'create', '/OVS/Repositories/0004fb00000300001d1619c621b16838/VirtualMachines/0004fb0000060000ab1b8caa045cc7a8/vm.cfg'] failed (1): Error: Boot loader didn't return any data!\n ">
    So, any further ideas where to look?
    Edited by: BadForGood on 21.10.2011 04:38

  • Using archlinux as paravirtualized guest

    Hello.
    I have a ArchLinux virtual machine running on top of qemu-kvm. Now thaht the kernel has some of the virtio modules (virtio_blk and virtio_net), I'm now trying to use this guest with some paravirtualized devices (qemu-kvm -drive file=my_disk.img,if-virtio,boot=on -net nic,model=virtio ...)
    I've added those modules to the mkinitcpio.conf and /ec/rc.conf of the guest. But I still can't boot when using the if=virtio for the -drive option, as there is no dev created for the disk.
    Any hints on how to boot arch with this paravirtualized disk ?
    EDIT: I'm using the kernel26 package from testing
    Last edited by slubman (2008-08-10 19:27:22)

    Todd_Z wrote:Then how do I get a url to be directed to my ip?  Can i go straight to the DNS, or do I have to use a service like goDaddy?
    something like no-ip.com or dyndns.com is what you need. but it needs to be mapped to your network IP obviously, not your local IP. as dusty said, you might need to change the port if it's not working externally on 80. if it is, you're set, and you shouldn't need to add anything to /etc/hosts unless you want to use a name instead of a local IP.

  • How to boot from cd a paravirtualized guest in OVM2 ?

    Hi all,
    I did not find how to boot a pv guest (OEL %.x) from an iso .
    Should I convert it to hvm, boot it from iso, and then convert it back to pv? If so, what is the right mothod to convert a pv guest to hvm?
    I know I cannot use the iso file with a pv guest, but I would expect it should be possible to export the content of the iso over nfs or ftp... just like a pv guest install... but I couldn't find any info neither I was ablo to do it.
    Thanks,
    Andrea

    Hi,
    with the Vista CD inserted reboot your Mac and hold down the 'Option/Alt'-key.
    In the following Selection Screen farthest to the right should be an icon of a CD labelled "Windows".
    Click on it and your Mac should boot from the CD.
    If the CD-icon is not shown, then most likely the Vista CD isn't bootable for whatever reason.
    Regards
    Stefan

  • WLC 5508 centrally switched client errors

    Hello,
    I am having trouble with a newly configured install.  Basically it seems that my centrally switched guest SSID is not functioning.  As you change AP groups, which should change the interface associated with the SSID and also the dhcp client address, the client is retaining the original dhcp address from whichever AP group they first associated with. 
    I also have a locally switch WPA2 SSID at each location which is working fine.  Clients are able to change dhcp address correctly as they move between AP groups.  It just doesn't seem to be working on the guest network, which is odd because it was working earlier in the install.  It has only started having issues yesteday afternoon. 
    It does not always coincide with the guest errors but I am generating these logging errors:
    *DHCP Socket Task: Aug 17 15:09:23.526: %SIM-3-DHCP_SERVER_NO_REPLY: sim_interface.c:1039 Failed to get DHCP response on interface 'may89-guest_vb_122'. Marking interface dirty.
    The interface above is assigned to the guest SSID in one of the AP group.  I assume this has something to do with it but I've been over my DHCP assignments on the core switch, local switch, controller, and dhcp server and can find no issue with the configuration.....Also the fact that it was working earlier this week.
    I also seem to be generating a high amount of:
    *dot1xMsgTask: Aug 17 14:46:22.844: %DOT1X-3-MAX_EAPOL_KEY_RETRANS: 1x_ptsm.c:456 Max EAPOL-key M1 retransmissions exceeded for client xx:xx:xx:xx:xx:xx
    I am not sure why as I am not using DOT1X at all.  The guest is a pass-thru and the WPA2 network is just WPA + WPA2 with TKIP and AES.  No DOT1X anywhere on the controller...

    I think I might know what to do.  Could I just create an interface group for each controller and place all of my individual guest interfaces within that group.  Then I could just assign that interface group to each of my AP groups so every AP group would have access to all of the guest interfaces on the controller.  I think the reason it is not currently working is because the AP group at my location is set to a specific interface and the ip addresses when I roam are from different interfaces not set for the AP group.  I am basically being blocked by the AP group/guest interface because my ip address belongs to the wrong interface. 
    I think an interface group would solve that problem.  The only other issue would what if I roam to an AP group on the other controller.  Could I just set up a mobility group and place both controllers in that group?  If they both have the UP status in the same mobility group would that allow inter-controller roaming?

  • Changing system date in Paravirtualized  Oracle VM

    Hi ,
    I need 3 guest on 1 oracle VM server. Each of them has own different system date. For example while first one is working on 2041 , second one works on 2001 and last one works on 2014.
    I have set "xen.independent_wallclock = 1" in "/etc/sysctl.cfg" in each Guest and I am able to change system date as independently from host system. Until here , everything is ok.
    But when I restart the Guest system , the system date is resetting to host system's system date .
    Please could you give your ideas how to solve this problem .
    Rgds.
    Leo-

    Hi, for paravirtualized guests do like this:
    As user root
    vi /etc/sysctl.confsearch "independent_wallclock" and set it "=0" (NOT "=1")
    Save and exit
    Set the correct Time Zone creating an appropriate symbolic link, for example:
    ln -sf ../usr/share/zoneinfo/Europe/Rome /etc/localtimeThen:
    vi /etc/sysconfig/clockSet it as you like, but following this schema:
    ZONE="Europe/Rome"
    UTC=false
    ARC=false("ZONE" refers to the Time Zone, "UTC=false" indicates that LOCAL TIME will be used)
    Finally, deactivate the ntpd service on your VM guest, as with the above settings system time will be bound to the Hardware Clock on Dom0, therefore we don't need ntpd:
    chkconfig --del ntpd
    service ntpd stopTry a reboot and check all is ok.
    All this, I repeat, is true for Paravirtualized guests only. Fully Virtualized guests do need ntpd service for system tyme sync.
    HTH

  • How to manage guests clocks?

    Hi all!
    I have a one physical server with 4 paravirtualized guest Linux OS.
    And after a while I've found that all guests clocks have a different values for system clocks. And the root OS with the hypervisor has a different value for it's clock.
    As per "Oracle® VM Server User’s Guide" "E.6 Setting the Guest’s Clock " - "... If you want to set the hypervisor to manage paravirtualized guest system clocks, set xen.independent_wallclock to 0. Any attempts to set or modify the time in a guest will fail...."
    But how in this case to synchronize guests clocks with a hypervizor clock?
    Best regards,
    Anton.

    Seems like, setting xen.independent_wallclock to 0 would not do the trick atleast in this version of xen 3.1.3(google for xen clock) . May be we will have to use ntp in all the guests to keep all the domUs' date iin sync.

  • Problem when creating a new Linux VM

    Hi,
    When I create a new Ubuntu linux from ISO, I received error messages blow. But it's ok for me to create a Windows XP/2K host.
    I search the forum. My xen_caps are: xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32 hvm-3.0-x86_32p hvm-3.0-x86_64
    Updates: I found I can run CentoOS without any problem. Is this means OVS don't support ubuntu? Anyone have the same problem?
    Thanks
    >
    Start - /OVS/running_pool/34_ubuntest
    PowerOn successfully.
    Update server -192.168.0.226
    Update Port - 0.0
    Update VM Status - Running
    Configure CPU Cap
    Set CPU Cap: failed:<Exception: failed:<Exception: ['xm', 'sched-credit', '-d', '34_ubuntest', '-c', '0'] => Error: Domain '34_ubuntest' does not exist.
    >
    StackTrace:
    File "/opt/ovs-agent-2.3/OVSXXenVMConfig.py", line 2500, in xen_set_cpu_cap
    run_cmd(args=['xm',
    File "/opt/ovs-agent-2.3/OVSCommons.py", line 85, in run_cmd
    raise Exception('%s => %s' % (cmdlist, p.childerr.read()))
    >
    StackTrace:
    File "/opt/ovs-agent-2.3/OVSSiteVMConfig.py", line 1110, in set_vm_cpu_cap
    if not rs.startswith("success"): raise Exception(rs)
    >
    Error log in xend.log
    [2011-01-07 12:29:05 2892] DEBUG (XendDomainInfo:95) XendDomainInfo.create(['vm', ['name', '34_ubuntest'], ['memory', '512'], ['maxmem', '512'], ['vcpus', '1'], ['uuid', '6492f5f8-9924-3e97-de9b-b0ecefe7a391'], ['on_poweroff', 'destroy'], ['on_reboot', 'destroy'], ['on_crash', 'destroy'], ['image', ['hvm', ['kernel', '/usr/lib/xen/boot/hvmloader'], ['device_model', '/usr/lib/xen/bin/qemu-dm'], ['boot', 'd'], ['acpi', '1'], ['apic', '1'], ['pae', '1'], ['vnc', '1'], ['vncunused', '1'], ['vnclisten', '0.0.0.0'], ['vncpasswd', 'XXXXXXXX']]], ['device', ['vbd', ['dev', 'hda:disk'], ['uname', 'file:/var/ovs/mount/28E0F7E7FF4A4D15BD483AF079D97194/running_pool/34_ubuntest/System.img'], ['mode', 'w']]], ['device', ['vbd', ['dev', 'hdc:cdrom'], ['uname', 'file:/var/ovs/mount/28E0F7E7FF4A4D15BD483AF079D97194/iso_pool/linux/ubuntu1010d.iso'], ['mode', 'r']]], ['device', ['vif', ['mac', '00:16:3E:55:EA:4B'], ['bridge', 'xenbr0'], ['script', '/etc/xen/scripts/vif-bridge'], ['type', 'ioemu']]]])
    [2011-01-07 12:29:05 2892] DEBUG (XendDomainInfo:2327) XendDomainInfo.constructDomain
    [2011-01-07 12:29:05 2892] DEBUG (balloon:181) Balloon: 981528 KiB free; need 4096; done.
    [2011-01-07 12:29:05 2892] DEBUG (XendDomain:452) Adding Domain: 12
    [2011-01-07 12:29:05 2892] DEBUG (XendDomainInfo:2528) XendDomainInfo.initDomain: 12 256
    [2011-01-07 12:29:05 2892] DEBUG (image:317) Stored a VNC password for vfb access
    [2011-01-07 12:29:05 2892] DEBUG (image:809) args: boot, val: d
    [2011-01-07 12:29:05 2892] DEBUG (image:809) args: fda, val: None
    [2011-01-07 12:29:05 2892] DEBUG (image:809) args: fdb, val: None
    [2011-01-07 12:29:05 2892] DEBUG (image:809) args: soundhw, val: None
    [2011-01-07 12:29:05 2892] DEBUG (image:809) args: localtime, val: None
    [2011-01-07 12:29:05 2892] DEBUG (image:809) args: serial, val: None
    [2011-01-07 12:29:05 2892] DEBUG (image:809) args: std-vga, val: None
    [2011-01-07 12:29:05 2892] DEBUG (image:809) args: isa, val: None
    [2011-01-07 12:29:05 2892] DEBUG (image:809) args: acpi, val: 1
    [2011-01-07 12:29:05 2892] DEBUG (image:809) args: usb, val: None
    [2011-01-07 12:29:05 2892] DEBUG (image:809) args: usbdevice, val: None
    [2011-01-07 12:29:05 2892] INFO (image:745) Need to create platform device.[domid:12]
    [2011-01-07 12:29:05 2892] DEBUG (XendDomainInfo:2552) initDomain:shadowmemory=0x0, memory_static_max=0x20000000, memory_static_min=0x0.
    [2011-01-07 12:29:05 2892] DEBUG (balloon:181) Balloon: 980116 KiB free; need 535552; done.
    [2011-01-07 12:29:05 2892] INFO (image:170) buildDomain os=hvm dom=12 vcpus=1
    [2011-01-07 12:29:05 2892] DEBUG (image:862) domid = 12
    [2011-01-07 12:29:05 2892] DEBUG (image:863) image = /usr/lib/xen/boot/hvmloader
    [2011-01-07 12:29:05 2892] DEBUG (image:864) store_evtchn = 2
    [2011-01-07 12:29:05 2892] DEBUG (image:865) memsize = 512
    [2011-01-07 12:29:05 2892] DEBUG (image:866) target = 512
    [2011-01-07 12:29:06 2892] DEBUG (image:867) vcpus = 1
    [2011-01-07 12:29:06 2892] DEBUG (image:868) acpi = 1
    [2011-01-07 12:29:06 2892] DEBUG (image:869) apic = 1
    [2011-01-07 12:29:06 2892] INFO (XendDomainInfo:2189) createDevice: vfb : {'vncunused': '1', 'other_config': {'vncunused': '1', 'vncpasswd': 'XXXXXXXX', 'vnclisten': '0.0.0.0', 'vnc': '1'}, 'vnc': '1', 'uuid': '2f93d706-c2d1-e638-d2eb-1a5b7aab70a0', 'vnclisten': '0.0.0.0', 'vncpasswd': 'XXXXXXXX'}
    [2011-01-07 12:29:06 2892] DEBUG (DevController:95) DevController: writing {'state': '1', 'backend-id': '0', 'backend': '/local/domain/0/backend/vfb/12/0'} to /local/domain/12/device/vfb/0.
    [2011-01-07 12:29:06 2892] DEBUG (DevController:97) DevController: writing {'vncunused': '1', 'domain': '34_ubuntest', 'frontend': '/local/domain/12/device/vfb/0', 'uuid': '2f93d706-c2d1-e638-d2eb-1a5b7aab70a0', 'frontend-id': '12', 'vnclisten': '0.0.0.0', 'vncpasswd': 'XXXXXXXX', 'state': '1', 'online': '1', 'vnc': '1'} to /local/domain/0/backend/vfb/12/0.
    [2011-01-07 12:29:06 2892] INFO (XendDomainInfo:2189) createDevice: vbd : {'uuid': '6848014f-eb0d-4028-765d-8c2a423f12eb', 'bootable': 1, 'driver': 'paravirtualised', 'dev': 'hda:disk', 'uname': 'file:/var/ovs/mount/28E0F7E7FF4A4D15BD483AF079D97194/running_pool/34_ubuntest/System.img', 'mode': 'w'}
    [2011-01-07 12:29:06 2892] DEBUG (DevController:95) DevController: writing {'backend-id': '0', 'virtual-device': '768', 'device-type': 'disk', 'state': '1', 'backend': '/local/domain/0/backend/vbd/12/768'} to /local/domain/12/device/vbd/768.
    [2011-01-07 12:29:06 2892] DEBUG (DevController:97) DevController: writing {'domain': '34_ubuntest', 'frontend': '/local/domain/12/device/vbd/768', 'uuid': '6848014f-eb0d-4028-765d-8c2a423f12eb', 'bootable': '1', 'dev': 'hda', 'state': '1', 'params': '/var/ovs/mount/28E0F7E7FF4A4D15BD483AF079D97194/running_pool/34_ubuntest/System.img', 'mode': 'w', 'online': '1', 'frontend-id': '12', 'type': 'file'} to /local/domain/0/backend/vbd/12/768.
    [2011-01-07 12:29:06 2892] INFO (XendDomainInfo:2189) createDevice: vbd : {'uuid': 'a17d2f5d-c2ff-8ae4-2529-d3736866d4db', 'bootable': 0, 'driver': 'paravirtualised', 'dev': 'hdc:cdrom', 'uname': 'file:/var/ovs/mount/28E0F7E7FF4A4D15BD483AF079D97194/iso_pool/linux/ubuntu1010d.iso', 'mode': 'r'}
    [2011-01-07 12:29:06 2892] DEBUG (DevController:95) DevController: writing {'backend-id': '0', 'virtual-device': '5632', 'device-type': 'cdrom', 'state': '1', 'backend': '/local/domain/0/backend/vbd/12/5632'} to /local/domain/12/device/vbd/5632.
    [2011-01-07 12:29:06 2892] DEBUG (DevController:97) DevController: writing {'domain': '34_ubuntest', 'frontend': '/local/domain/12/device/vbd/5632', 'uuid': 'a17d2f5d-c2ff-8ae4-2529-d3736866d4db', 'bootable': '0', 'dev': 'hdc', 'state': '1', 'params': '/var/ovs/mount/28E0F7E7FF4A4D15BD483AF079D97194/iso_pool/linux/ubuntu1010d.iso', 'mode': 'r', 'online': '1', 'frontend-id': '12', 'type': 'file'} to /local/domain/0/backend/vbd/12/5632.
    [2011-01-07 12:29:06 2892] INFO (XendDomainInfo:2189) createDevice: vif : {'bridge': 'xenbr0', 'mac': '00:16:3E:55:EA:4B', 'type': 'ioemu', 'uuid': '7ed50e95-a9b4-6b3a-c325-56645c7b43d3', 'script': '/etc/xen/scripts/vif-bridge'}
    [2011-01-07 12:29:06 2892] DEBUG (DevController:95) DevController: writing {'state': '1', 'backend-id': '0', 'backend': '/local/domain/0/backend/vif/12/0'} to /local/domain/12/device/vif/0.
    [2011-01-07 12:29:06 2892] DEBUG (DevController:97) DevController: writing {'bridge': 'xenbr0', 'domain': '34_ubuntest', 'handle': '0', 'uuid': '7ed50e95-a9b4-6b3a-c325-56645c7b43d3', 'script': '/etc/xen/scripts/vif-bridge', 'mac': '00:16:3E:55:EA:4B', 'frontend-id': '12', 'state': '1', 'online': '1', 'frontend': '/local/domain/12/device/vif/0', 'type': 'ioemu'} to /local/domain/0/backend/vif/12/0.
    [2011-01-07 12:29:06 2892] INFO (image:391) spawning device models: /usr/lib/xen/bin/qemu-dm ['/usr/lib/xen/bin/qemu-dm', '-d', '12', '-domain-name', '34_ubuntest', '-videoram', '4', '-vnc', '0.0.0.0:0,password', '-vncunused', '-vcpus', '1', '-boot', 'd', '-acpi', '-net', 'nic,vlan=1,macaddr=00:16:3E:55:EA:4B,model=rtl8139', '-net', 'tap,vlan=1,ifname=tap12.0,bridge=xenbr0', '-M', 'xenfv']
    [2011-01-07 12:29:06 2892] INFO (image:440) device model pid: 3761
    [2011-01-07 12:29:06 2892] DEBUG (XendDomainInfo:3089) Storing VM details: {'on_xend_stop': 'ignore', 'shadow_memory': '5', 'uuid': '6492f5f8-9924-3e97-de9b-b0ecefe7a391', 'on_reboot': 'destroy', 'start_time': '1294374546.09', 'on_poweroff': 'destroy', 'bootloader_args': '', 'on_xend_start': 'ignore', 'on_crash': 'destroy', 'xend/restart_count': '0', 'vcpus': '1', 'vcpu_avail': '1', 'bootloader': '', 'image': '(hvm (kernel ) (superpages 0) (hpet 0) (vnclisten 0.0.0.0) (loader /usr/lib/xen/boot/hvmloader) (vncunused 1) (xen_platform_pci 1) (boot d) (rtc_timeoffset 0) (vncpasswd XXXXXX) (pae 1) (vpt_align 1) (viridian 0) (acpi 1) (timer_mode 1) (vnc 1) (apic 1) (device_model /usr/lib/xen/bin/qemu-dm) (notes (SUSPEND_CANCEL 1)))', 'name': '34_ubuntest'}
    [2011-01-07 12:29:06 2892] DEBUG (XendDomainInfo:1640) Storing domain details: {'console/port': '3', 'name': '34_ubuntest', 'console/limit': '1048576', 'store/port': '2', 'vm': '/vm/6492f5f8-9924-3e97-de9b-b0ecefe7a391', 'domid': '12', 'image/suspend-cancel': '1', 'cpu/0/availability': 'online', 'memory/target': '524288', 'control/platform-feature-multiprocessor-suspend': '1', 'store/ring-ref': '1044476', 'console/type': 'ioemu'}
    [2011-01-07 12:29:06 2892] INFO (image:528) waiting for sentinel_fifo
    [2011-01-07 12:29:06 2892] DEBUG (DevController:95) DevController: writing {'state': '1', 'backend-id': '0', 'backend': '/local/domain/0/backend/console/12/0'} to /local/domain/12/device/console/0.
    [2011-01-07 12:29:06 2892] DEBUG (DevController:97) DevController: writing {'domain': '34_ubuntest', 'frontend': '/local/domain/12/device/console/0', 'uuid': '4f7921bb-f508-f6b9-b08b-4b94d8309ba2', 'frontend-id': '12', 'state': '1', 'location': '3', 'online': '1', 'protocol': 'vt100'} to /local/domain/0/backend/console/12/0.
    [2011-01-07 12:29:06 2892] DEBUG (XendDomainInfo:1727) XendDomainInfo.handleShutdownWatch
    [2011-01-07 12:29:06 2892] DEBUG (DevController:139) Waiting for devices vif.
    [2011-01-07 12:29:06 2892] DEBUG (DevController:144) Waiting for 0.
    [2011-01-07 12:29:06 2892] DEBUG (DevController:629) hotplugStatusCallback /local/domain/0/backend/vif/12/0/hotplug-status.
    [2011-01-07 12:29:06 2892] DEBUG (DevController:643) hotplugStatusCallback 1.
    [2011-01-07 12:29:06 2892] DEBUG (DevController:139) Waiting for devices vscsi.
    [2011-01-07 12:29:06 2892] DEBUG (DevController:139) Waiting for devices vbd.
    [2011-01-07 12:29:06 2892] DEBUG (DevController:144) Waiting for 768.
    [2011-01-07 12:29:06 2892] DEBUG (DevController:629) hotplugStatusCallback /local/domain/0/backend/vbd/12/768/hotplug-status.
    [2011-01-07 12:29:06 2892] DEBUG (DevController:629) hotplugStatusCallback /local/domain/0/backend/vbd/12/768/hotplug-status.
    [2011-01-07 12:29:06 2892] DEBUG (DevController:643) hotplugStatusCallback 1.
    [2011-01-07 12:29:06 2892] DEBUG (DevController:144) Waiting for 5632.
    [2011-01-07 12:29:06 2892] DEBUG (DevController:629) hotplugStatusCallback /local/domain/0/backend/vbd/12/5632/hotplug-status.
    [2011-01-07 12:29:07 2892] DEBUG (DevController:629) hotplugStatusCallback /local/domain/0/backend/vbd/12/5632/hotplug-status.
    [2011-01-07 12:29:07 2892] DEBUG (DevController:643) hotplugStatusCallback 1.
    [2011-01-07 12:29:07 2892] DEBUG (DevController:139) Waiting for devices irq.
    [2011-01-07 12:29:07 2892] DEBUG (DevController:139) Waiting for devices vkbd.
    [2011-01-07 12:29:07 2892] DEBUG (DevController:139) Waiting for devices vfb.
    [2011-01-07 12:29:07 2892] DEBUG (DevController:139) Waiting for devices console.
    [2011-01-07 12:29:07 2892] DEBUG (DevController:144) Waiting for 0.
    [2011-01-07 12:29:07 2892] DEBUG (DevController:139) Waiting for devices pci.
    [2011-01-07 12:29:07 2892] DEBUG (DevController:139) Waiting for devices ioports.
    [2011-01-07 12:29:07 2892] DEBUG (DevController:139) Waiting for devices tap.
    [2011-01-07 12:29:07 2892] DEBUG (DevController:139) Waiting for devices vtpm.
    [2011-01-07 12:29:07 2892] INFO (XendDomain:1180) Domain 34_ubuntest (12) unpaused.
    [2011-01-07 12:29:09 2892] WARNING (XendDomainInfo:1907) Domain has crashed: name=34_ubuntest id=12.
    [2011-01-07 12:29:09 2892] DEBUG (XendDomainInfo:2757) XendDomainInfo.destroy: domid=12
    [2011-01-07 12:29:09 2892] DEBUG (XendDomainInfo:2230) Destroying device model
    [2011-01-07 12:29:09 2892] INFO (image:553) 34_ubuntest device model terminated
    [2011-01-07 12:29:09 2892] DEBUG (XendDomainInfo:2237) Releasing devices
    [2011-01-07 12:29:09 2892] DEBUG (XendDomainInfo:2250) Removing vif/0
    [2011-01-07 12:29:09 2892] DEBUG (XendDomainInfo:1144) XendDomainInfo.destroyDevice: deviceClass = vif, device = vif/0
    [2011-01-07 12:29:09 2892] DEBUG (XendDomainInfo:2250) Removing vbd/768
    [2011-01-07 12:29:09 2892] DEBUG (XendDomainInfo:1144) XendDomainInfo.destroyDevice: deviceClass = vbd, device = vbd/768
    [2011-01-07 12:29:09 2892] DEBUG (XendDomainInfo:2250) Removing vbd/5632
    [2011-01-07 12:29:09 2892] DEBUG (XendDomainInfo:1144) XendDomainInfo.destroyDevice: deviceClass = vbd, device = vbd/5632
    [2011-01-07 12:29:09 2892] DEBUG (XendDomainInfo:2250) Removing vfb/0
    [2011-01-07 12:29:09 2892] DEBUG (XendDomainInfo:1144) XendDomainInfo.destroyDevice: deviceClass = vfb, device = vfb/0
    [2011-01-07 12:29:09 2892] DEBUG (XendDomainInfo:2250) Removing console/0
    [2011-01-07 12:29:09 2892] DEBUG (XendDomainInfo:1144) XendDomainInfo.destroyDevice: deviceClass = console, device = console/0
    [2011-01-07 12:29:09 2892] DEBUG (XendDomainInfo:2235) No device model
    [2011-01-07 12:29:09 2892] DEBUG (XendDomainInfo:2237) Releasing devices
    [2011-01-07 12:33:41 2892] DEBUG (XendDomainInfo:95) XendDomainInfo.create(['vm', ['name', '34_ubuntest'], ['memory', '512'], ['on_reboot', 'restart'], ['on_crash', 'restart'], ['vcpus', 1], ['on_xend_start', 'ignore'], ['on_xend_stop', 'ignore'], ['uuid', '6492f5f8-9924-3e97-de9b-b0ecefe7a391'], ['image', ['hvm', ['kernel', '/usr/lib/xen/boot/hvmloader'], ['videoram', 4], ['device_model', '/usr/lib/xen/bin/qemu-dm'], ['pae', 1], ['vcpus', 1], ['boot', 'c'], ['fda', ''], ['fdb', ''], ['timer_mode', 0], ['localtime', 0], ['serial', 'pty'], ['stdvga', 0], ['isa', 0], ['nographic', 0], ['soundhw', ''], ['vnc', 1], ['vncunused', 1], ['vncconsole', 1], ['vnclisten', '0.0.0.0'], ['xauthority', '//.Xauthority'], ['rtc_timeoffset', 0], ['monitor', 0], ['acpi', 1], ['apic', 1], ['usb', 0], ['usbdevice', ''], ['keymap', 'en-us'], ['pci', []], ['hpet', 0], ['guest_os_type', 'default'], ['hap', 1], ['cpuid', []], ['cpuid_check', []], ['viridian', 0], ['pci_msitranslate', 1], ['vpt_align', 1], ['pci_power_mgmt', 0], ['xen_platform_pci', 1], ['vncpasswd', 'XXXXXXXX']]], ['s3_integrity', 1], ['device', ['vbd', ['uname', 'file:/var/ovs/mount/28E0F7E7FF4A4D15BD483AF079D97194/running_pool/34_ubuntest/System.img'], ['dev', 'hda'], ['mode', 'w']]], ['device', ['vbd', ['uname', 'file:/var/ovs/mount/28E0F7E7FF4A4D15BD483AF079D97194/iso_pool/linux/ubuntu1010d.iso'], ['dev', 'hdc:cdrom'], ['mode', 'r']]], ['device', ['vif', ['bridge', 'xenbr0'], ['mac', '00:16:3E:55:EA:4B'], ['type', 'ioemu']]]])
    [2011-01-07 12:33:41 2892] DEBUG (XendDomainInfo:2327) XendDomainInfo.constructDomain
    [2011-01-07 12:33:41 2892] DEBUG (balloon:181) Balloon: 981528 KiB free; need 4096; done.
    [2011-01-07 12:33:41 2892] DEBUG (XendDomain:452) Adding Domain: 13
    [2011-01-07 12:33:41 2892] DEBUG (XendDomainInfo:2528) XendDomainInfo.initDomain: 13 256
    [2011-01-07 12:33:41 2892] DEBUG (image:317) Stored a VNC password for vfb access
    [2011-01-07 12:33:41 2892] DEBUG (image:809) args: boot, val: c
    [2011-01-07 12:33:41 2892] DEBUG (image:809) args: fda, val: None
    [2011-01-07 12:33:41 2892] DEBUG (image:809) args: fdb, val: None
    [2011-01-07 12:33:41 2892] DEBUG (image:809) args: soundhw, val: None
    [2011-01-07 12:33:41 2892] DEBUG (image:809) args: localtime, val: 0
    [2011-01-07 12:33:41 2892] DEBUG (image:809) args: serial, val: ['pty']
    [2011-01-07 12:33:41 2892] DEBUG (image:809) args: std-vga, val: 0
    [2011-01-07 12:33:41 2892] DEBUG (image:809) args: isa, val: 0
    [2011-01-07 12:33:41 2892] DEBUG (image:809) args: acpi, val: 1
    [2011-01-07 12:33:41 2892] DEBUG (image:809) args: usb, val: 0
    [2011-01-07 12:33:41 2892] DEBUG (image:809) args: usbdevice, val: None
    [2011-01-07 12:33:41 2892] INFO (image:745) Need to create platform device.[domid:13]
    [2011-01-07 12:33:41 2892] DEBUG (XendDomainInfo:2552) initDomain:shadowmemory=0x0, memory_static_max=0x20000000, memory_static_min=0x0.
    [2011-01-07 12:33:41 2892] DEBUG (balloon:181) Balloon: 980116 KiB free; need 535552; done.
    [2011-01-07 12:33:41 2892] INFO (image:170) buildDomain os=hvm dom=13 vcpus=1
    [2011-01-07 12:33:41 2892] DEBUG (image:862) domid = 13
    [2011-01-07 12:33:41 2892] DEBUG (image:863) image = /usr/lib/xen/boot/hvmloader
    [2011-01-07 12:33:41 2892] DEBUG (image:864) store_evtchn = 2
    [2011-01-07 12:33:41 2892] DEBUG (image:865) memsize = 512
    [2011-01-07 12:33:41 2892] DEBUG (image:866) target = 512
    [2011-01-07 12:33:41 2892] DEBUG (image:867) vcpus = 1
    [2011-01-07 12:33:41 2892] DEBUG (image:868) acpi = 1
    [2011-01-07 12:33:41 2892] DEBUG (image:869) apic = 1
    [2011-01-07 12:33:41 2892] INFO (XendDomainInfo:2189) createDevice: vfb : {'vncunused': 1, 'other_config': {'vncunused': 1, 'vncpasswd': 'XXXXXXXX', 'vnclisten': '0.0.0.0', 'vnc': '1'}, 'vnc': '1', 'uuid': '4f92dca8-af4b-a2e6-01e7-ad824af0231a', 'vnclisten': '0.0.0.0', 'vncpasswd': 'XXXXXXXX'}
    [2011-01-07 12:33:41 2892] DEBUG (DevController:95) DevController: writing {'state': '1', 'backend-id': '0', 'backend': '/local/domain/0/backend/vfb/13/0'} to /local/domain/13/device/vfb/0.
    [2011-01-07 12:33:41 2892] DEBUG (DevController:97) DevController: writing {'vncunused': '1', 'domain': '34_ubuntest', 'frontend': '/local/domain/13/device/vfb/0', 'uuid': '4f92dca8-af4b-a2e6-01e7-ad824af0231a', 'frontend-id': '13', 'vnclisten': '0.0.0.0', 'vncpasswd': 'XXXXXXXX', 'state': '1', 'online': '1', 'vnc': '1'} to /local/domain/0/backend/vfb/13/0.
    [2011-01-07 12:33:41 2892] INFO (XendDomainInfo:2189) createDevice: vbd : {'uuid': '5228a931-a5c1-af1f-debb-177193e27142', 'bootable': 1, 'driver': 'paravirtualised', 'dev': 'hda', 'uname': 'file:/var/ovs/mount/28E0F7E7FF4A4D15BD483AF079D97194/running_pool/34_ubuntest/System.img', 'mode': 'w'}
    [2011-01-07 12:33:41 2892] DEBUG (DevController:95) DevController: writing {'backend-id': '0', 'virtual-device': '768', 'device-type': 'disk', 'state': '1', 'backend': '/local/domain/0/backend/vbd/13/768'} to /local/domain/13/device/vbd/768.
    [2011-01-07 12:33:41 2892] DEBUG (DevController:97) DevController: writing {'domain': '34_ubuntest', 'frontend': '/local/domain/13/device/vbd/768', 'uuid': '5228a931-a5c1-af1f-debb-177193e27142', 'bootable': '1', 'dev': 'hda', 'state': '1', 'params': '/var/ovs/mount/28E0F7E7FF4A4D15BD483AF079D97194/running_pool/34_ubuntest/System.img', 'mode': 'w', 'online': '1', 'frontend-id': '13', 'type': 'file'} to /local/domain/0/backend/vbd/13/768.
    [2011-01-07 12:33:41 2892] INFO (XendDomainInfo:2189) createDevice: vbd : {'uuid': '91e7374f-3645-8a80-9fdb-18a8aec9087a', 'bootable': 0, 'driver': 'paravirtualised', 'dev': 'hdc:cdrom', 'uname': 'file:/var/ovs/mount/28E0F7E7FF4A4D15BD483AF079D97194/iso_pool/linux/ubuntu1010d.iso', 'mode': 'r'}
    [2011-01-07 12:33:41 2892] DEBUG (DevController:95) DevController: writing {'backend-id': '0', 'virtual-device': '5632', 'device-type': 'cdrom', 'state': '1', 'backend': '/local/domain/0/backend/vbd/13/5632'} to /local/domain/13/device/vbd/5632.
    [2011-01-07 12:33:41 2892] DEBUG (DevController:97) DevController: writing {'domain': '34_ubuntest', 'frontend': '/local/domain/13/device/vbd/5632', 'uuid': '91e7374f-3645-8a80-9fdb-18a8aec9087a', 'bootable': '0', 'dev': 'hdc', 'state': '1', 'params': '/var/ovs/mount/28E0F7E7FF4A4D15BD483AF079D97194/iso_pool/linux/ubuntu1010d.iso', 'mode': 'r', 'online': '1', 'frontend-id': '13', 'type': 'file'} to /local/domain/0/backend/vbd/13/5632.
    [2011-01-07 12:33:41 2892] INFO (XendDomainInfo:2189) createDevice: vif : {'bridge': 'xenbr0', 'mac': '00:16:3E:55:EA:4B', 'type': 'ioemu', 'uuid': '7dee33df-7468-e35b-0640-3b1acb155312'}
    [2011-01-07 12:33:41 2892] DEBUG (DevController:95) DevController: writing {'state': '1', 'backend-id': '0', 'backend': '/local/domain/0/backend/vif/13/0'} to /local/domain/13/device/vif/0.
    [2011-01-07 12:33:41 2892] DEBUG (DevController:97) DevController: writing {'bridge': 'xenbr0', 'domain': '34_ubuntest', 'handle': '0', 'uuid': '7dee33df-7468-e35b-0640-3b1acb155312', 'script': '/etc/xen/scripts/vif-bridge', 'mac': '00:16:3E:55:EA:4B', 'frontend-id': '13', 'state': '1', 'online': '1', 'frontend': '/local/domain/13/device/vif/0', 'type': 'ioemu'} to /local/domain/0/backend/vif/13/0.
    [2011-01-07 12:33:41 2892] INFO (image:391) spawning device models: /usr/lib/xen/bin/qemu-dm ['/usr/lib/xen/bin/qemu-dm', '-d', '13', '-domain-name', '34_ubuntest', '-videoram', '4', '-k', 'en-us', '-vnc', '0.0.0.0:0,password', '-vncunused', '-vcpus', '1', '-boot', 'c', '-serial', 'pty', '-acpi', '-net', 'nic,vlan=1,macaddr=00:16:3E:55:EA:4B,model=rtl8139', '-net', 'tap,vlan=1,ifname=tap13.0,bridge=xenbr0', '-M', 'xenfv']
    [2011-01-07 12:33:41 2892] INFO (image:440) device model pid: 5712
    [2011-01-07 12:33:41 2892] DEBUG (XendDomainInfo:3089) Storing VM details: {'on_xend_stop': 'ignore', 'shadow_memory': '5', 'uuid': '6492f5f8-9924-3e97-de9b-b0ecefe7a391', 'on_reboot': 'restart', 'start_time': '1294374821.85', 'on_poweroff': 'destroy', 'bootloader_args': '', 'on_xend_start': 'ignore', 'on_crash': 'restart', 'xend/restart_count': '0', 'vcpus': '1', 'vcpu_avail': '1', 'bootloader': '', 'image': '(hvm (kernel ) (superpages 0) (videoram 4) (hpet 0) (stdvga 0) (vnclisten 0.0.0.0) (loader /usr/lib/xen/boot/hvmloader) (vncconsole 1) (serial pty) (vncunused 1) (xen_platform_pci 1) (boot c) (rtc_timeoffset 0) (vncpasswd XXXXXX) (pci ()) (pae 1) (vpt_align 1) (hap 1) (viridian 0) (acpi 1) (localtime 0) (timer_mode 0) (vnc 1) (nographic 0) (guest_os_type default) (pci_msitranslate 1) (apic 1) (monitor 0) (device_model /usr/lib/xen/bin/qemu-dm) (keymap en-us) (pci_power_mgmt 0) (usb 0) (xauthority //.Xauthority) (isa 0) (notes (SUSPEND_CANCEL 1)))', 'name': '34_ubuntest'}
    [2011-01-07 12:33:41 2892] INFO (image:528) waiting for sentinel_fifo
    [2011-01-07 12:33:41 2892] DEBUG (XendDomainInfo:1640) Storing domain details: {'console/port': '3', 'name': '34_ubuntest', 'console/limit': '1048576', 'store/port': '2', 'vm': '/vm/6492f5f8-9924-3e97-de9b-b0ecefe7a391', 'domid': '13', 'image/suspend-cancel': '1', 'cpu/0/availability': 'online', 'memory/target': '524288', 'control/platform-feature-multiprocessor-suspend': '1', 'store/ring-ref': '1044476', 'console/type': 'ioemu'}
    [2011-01-07 12:33:41 2892] DEBUG (DevController:95) DevController: writing {'state': '1', 'backend-id': '0', 'backend': '/local/domain/0/backend/console/13/0'} to /local/domain/13/device/console/0.
    [2011-01-07 12:33:41 2892] DEBUG (DevController:97) DevController: writing {'domain': '34_ubuntest', 'frontend': '/local/domain/13/device/console/0', 'uuid': '09bfaba7-4a64-c238-10f6-e475413d4474', 'frontend-id': '13', 'state': '1', 'location': '3', 'online': '1', 'protocol': 'vt100'} to /local/domain/0/backend/console/13/0.
    [2011-01-07 12:33:41 2892] DEBUG (XendDomainInfo:1727) XendDomainInfo.handleShutdownWatch
    [2011-01-07 12:33:41 2892] DEBUG (DevController:139) Waiting for devices vif.
    [2011-01-07 12:33:41 2892] DEBUG (DevController:144) Waiting for 0.
    [2011-01-07 12:33:41 2892] DEBUG (DevController:629) hotplugStatusCallback /local/domain/0/backend/vif/13/0/hotplug-status.
    [2011-01-07 12:33:42 2892] DEBUG (DevController:629) hotplugStatusCallback /local/domain/0/backend/vif/13/0/hotplug-status.
    [2011-01-07 12:33:42 2892] DEBUG (DevController:643) hotplugStatusCallback 1.
    [2011-01-07 12:33:42 2892] DEBUG (DevController:139) Waiting for devices vscsi.
    [2011-01-07 12:33:42 2892] DEBUG (DevController:139) Waiting for devices vbd.
    [2011-01-07 12:33:42 2892] DEBUG (DevController:144) Waiting for 768.
    [2011-01-07 12:33:42 2892] DEBUG (DevController:629) hotplugStatusCallback /local/domain/0/backend/vbd/13/768/hotplug-status.
    [2011-01-07 12:33:43 2892] DEBUG (DevController:629) hotplugStatusCallback /local/domain/0/backend/vbd/13/768/hotplug-status.
    [2011-01-07 12:33:43 2892] DEBUG (DevController:643) hotplugStatusCallback 1.
    [2011-01-07 12:33:43 2892] DEBUG (DevController:144) Waiting for 5632.
    [2011-01-07 12:33:43 2892] DEBUG (DevController:629) hotplugStatusCallback /local/domain/0/backend/vbd/13/5632/hotplug-status.
    [2011-01-07 12:33:43 2892] DEBUG (DevController:643) hotplugStatusCallback 1.
    [2011-01-07 12:33:43 2892] DEBUG (DevController:139) Waiting for devices irq.
    [2011-01-07 12:33:43 2892] DEBUG (DevController:139) Waiting for devices vkbd.
    [2011-01-07 12:33:43 2892] DEBUG (DevController:139) Waiting for devices vfb.
    [2011-01-07 12:33:43 2892] DEBUG (DevController:139) Waiting for devices console.
    [2011-01-07 12:33:43 2892] DEBUG (DevController:144) Waiting for 0.
    [2011-01-07 12:33:43 2892] DEBUG (DevController:139) Waiting for devices pci.
    [2011-01-07 12:33:43 2892] DEBUG (DevController:139) Waiting for devices ioports.
    [2011-01-07 12:33:43 2892] DEBUG (DevController:139) Waiting for devices tap.
    [2011-01-07 12:33:43 2892] DEBUG (DevController:139) Waiting for devices vtpm.
    [2011-01-07 12:33:43 2892] INFO (XendDomain:1180) Domain 34_ubuntest (13) unpaused.
    [2011-01-07 12:33:45 2892] INFO (XendDomainInfo:1924) Domain has shutdown: name=34_ubuntest id=13 reason=poweroff.
    [2011-01-07 12:33:45 2892] DEBUG (XendDomainInfo:2757) XendDomainInfo.destroy: domid=13
    [2011-01-07 12:33:45 2892] DEBUG (XendDomainInfo:2230) Destroying device model
    [2011-01-07 12:33:45 2892] INFO (image:553) 34_ubuntest device model terminated
    [2011-01-07 12:33:45 2892] DEBUG (XendDomainInfo:2237) Releasing devices
    [2011-01-07 12:33:45 2892] DEBUG (XendDomainInfo:2250) Removing vif/0
    [2011-01-07 12:33:45 2892] DEBUG (XendDomainInfo:1144) XendDomainInfo.destroyDevice: deviceClass = vif, device = vif/0
    [2011-01-07 12:33:45 2892] DEBUG (XendDomainInfo:2250) Removing vbd/768
    [2011-01-07 12:33:45 2892] DEBUG (XendDomainInfo:1144) XendDomainInfo.destroyDevice: deviceClass = vbd, device = vbd/768
    [2011-01-07 12:33:45 2892] DEBUG (XendDomainInfo:2250) Removing vbd/5632
    [2011-01-07 12:33:45 2892] DEBUG (XendDomainInfo:1144) XendDomainInfo.destroyDevice: deviceClass = vbd, device = vbd/5632
    [2011-01-07 12:33:45 2892] DEBUG (XendDomainInfo:2250) Removing vfb/0
    [2011-01-07 12:33:45 2892] DEBUG (XendDomainInfo:1144) XendDomainInfo.destroyDevice: deviceClass = vfb, device = vfb/0
    [2011-01-07 12:33:45 2892] DEBUG (XendDomainInfo:2250) Removing console/0
    [2011-01-07 12:33:45 2892] DEBUG (XendDomainInfo:1144) XendDomainInfo.destroyDevice: deviceClass = console, device = console/0
    Edited by: user3835659 on 2011-1-7 上午2:45
    Edited by: user3835659 on 2011-1-9 下午9:58

    In the past I've been successfully deploying a few Ubuntu guest VMs, Hardware Virtualized (never succeeded to put up a Paravirtualized guest though) for testing purposes.
    The latest version (10.4 maybe? Can't remember right now) worked without any sort of fixes or workarounds and was stable right away.
    Previous versions needed a fix in the "grub.conf" file, and I had to put in a "NOAPIC" option to tell the kernel to inhibit some kind of interrupt events, I'm sorry I cannot be more specific but I can't remember exactly the real reasons behind the fix, I just know that without it I was getting a "processor stuck" error on the guest's console after a while, resulting in an unresponsive VM.
    I see from your logfile that you have "APIC=1" and "ACPI=1", so maybe you'd want to play a bit with those settings and see the results.
    My processors are Intel Xeon 5450.
    HTH

  • OVS 2.2 :: Unable to install RHEL HVM on physical disk from command line

    [root@ovs2 xen]# /usr/sbin/virt-install hvm name=test2 ram=1024 vcpus=1 bridge=xenbr0 file /dev/sdc --nographics
    What would you like to use for the virtual CD image? /var/ovs/mount/1FB2E6B36D21418792A1DD30B62C689F/iso_pool/rhel-server-5.6-x86_64-dvd.iso
    Starting install...
    Guest installation complete... restarting guest.
    exception was: Domain named test2 already exists!
    Domain installation may not have been
    successful. If it was, you can restart your domain
    by running 'xm create -c test2'; otherwise, please
    restart your installation.
    [root@ovs2 xen]# more test2
    # Automatically generated xen config file
    name = "test2"
    builder = "hvm"
    memory = "1024"
    disk = [ 'phy:/dev/sdc,hda,w', ]
    vif = [ 'type=ioemu, mac=00:16:3e:3d:d0:5c, bridge=xenbr0', ]
    uuid = "f99f6a07-6d03-a0ae-8f2f-a7a0e1af5e31"
    device_model = "/usr/lib/xen/bin/qemu-dm"
    kernel = "/usr/lib/xen/boot/hvmloader"
    nographic=1
    timer_mode=0
    apic=1
    acpi=1
    pae=1
    vcpus=1
    serial = "pty" # enable serial console
    on_reboot = 'restart'
    on_crash = 'restart'
    [root@ovs2 xen]# xm console test2
    xenconsole: Could not read tty from store: No such file or directory
    [root@ovs2 xen]#
    + No errors in xend.log or qemu-*.log
    + hypervisor inittab is default .. co:2345:respawn:/sbin/agetty xvc0 9600 vt100-nav
    Using similar syntax, and installing paravirtualized guest to physical disk works fine.
    [root@ovs2 xen]# /usr/sbin/virt-install paravirt name=demo3 ram=1024 vcpus=2 bridge=xenbr0 file=/dev/sdc nographics location=http://192.168.229.74/RHEL5764bit
    Starting install...
    Bootdata ok (command line is method=http://192.168.229.74/RHEL5764bit )
    Linux version 2.6.18-238.el5xen ([email protected]) (gcc version 4.1.2 20080704 (Red Hat 4.1.2-50)) #1 SMP Sun Dec 19 14:42:02 EST 2010
    BIOS-provided physical RAM map:
    Xen: 0000000000000000 - 0000000040800000 (usable)
    No mptable found.
    Built 1 zonelists. Total pages: 264192
    Kernel command line: method=http://192.168.229.74/RHEL5764bit ...................................
    Any suggestions ??

    and i go to the temp mountpoint that the script will mount on
    Starting install...
    ERROR: Invalid NFS location given: [Errno 2] No such file or directory: '/var/lib/xen/xennfs.7x4Rf4/boot/x86_64/vmlinuz-xen'
    [root@ovs2 opt1]# df
    Filesystem 1K-blocks Used Available Use% Mounted on
    /dev/cciss/c0d0p2 3050092 3033308 0 100% /
    /dev/cciss/c0d0p1 101086 47114 48753 50% /boot
    tmpfs 288856 0 288856 0% /dev/shm
    none 288768 40 288728 1% /var/lib/xenstored
    /dev/cciss/c0d0p3 288623616 301056 288322560 1% /var/ovs/mount/A52CB661C1CF41D198D50F6379822694
    /var/isos/OracleLinux-R5-U7-Server-x86_64-dvd.iso
    3755446 3755446 0 100% /el/EL5-x86
    192.168.229.110:/el/EL5-x86
    3755456 3755456 0 100% /opt1
    192.168.229.110:/el/EL5-x86/
    3755456 3755456 0 100% /var/lib/xen/xennfs.NnE54I
    [root@ovs2 opt1]# cd /var/lib/xen/xen
    xend-db/ xennfs.7jHT0q/ xennfs.fQNnQD/ xennfs.LR6hDx/ xennfs.QnxyeH/
    xennfs.5Pr0vm/ xennfs.8aMSAA/ xennfs.fRhXiN/ xennfs.NnE54I/ xennfs.yEw4KL/
    [root@ovs2 opt1]# cd /var/lib/xen/xen
    xend-db/ xennfs.7jHT0q/ xennfs.fQNnQD/ xennfs.LR6hDx/ xennfs.QnxyeH/
    xennfs.5Pr0vm/ xennfs.8aMSAA/ xennfs.fRhXiN/ xennfs.NnE54I/ xennfs.yEw4KL/
    [root@ovs2 opt1]# cd /var/lib/xen/xennfs.NnE54I/
    [root@ovs2 xennfs.NnE54I]# ls
    blafdoc.css EULA GPL README-en RELEASE-NOTES-en.html Server VT
    Cluster eula.en_US images README-en.html RPM-GPG-KEY supportinfo
    ClusterStorage eula.py isolinux RELEASE-NOTES-en RPM-GPG-KEY-oracle TRANS.TBL
    [root@ovs2 xennfs.NnE54I]# find . -name vmlinuz\*
    ./images/pxeboot/vmlinuz
    ./images/xen/vmlinuz
    ./isolinux/vmlinuz
    [root@ovs2 xennfs.NnE54I]#

  • PVM - Boot loader didn't return any data!

    Hi Everyone,
    This is my first post in Oracle Forums, so I hope doing right questions to the experts who read my issue.
    I´m working on a virtualized environment. I created and configured my "base environment" without any problem:
    - Server 1: Oracle VM Server 3.2.2 (Clustered Server Pool: "POOL HA")
    - Server 2: Oracle VM Server 3.2.2 (Clustered Server Pool: "POOL HA")
    - Server 3: Red Hat Enterprise Linux 6 (Oracle VM Manager 3.2.2)
    The next step is create several Paravirtualized Guests (Solaris 11 & RHEL 6). I'm able to create the VMs, but the problem is when I try to start them to install the OS...simply I can´t.
    The error is as follows:
    "Server error message: Command: ['xm', 'create', '/OVS/Repositories/0004fb000003000057155a18cb654250/VirtualMachines/0004fb0000060000fe3a960fd05eb708/vm.cfg'] failed (1): stderr: *Error: Boot loader didn't return any data!*
    stdout: Using config file "/OVS/Repositories/0004fb000003000057155a18cb654250/VirtualMachines/0004fb0000060000fe3a960fd05eb708/vm.cfg"."
    I´m trying to start them as shown in the Oracle's documentation (Using mounted ISO in http, ftp or NFS). I chose the http option:
    In Server 3:
    # cd /var/www/html
    # mkdir EL5u6-x86_64
    # mount -o ro,loop /path/RHEL6.iso EL5u6-x86_64
    Network Boot Path = http://localhost/RHEL6.iso
    - http Server is working ok
    - localhost= Server3_IP
    What am I doing wrong?, some kind of parameter in default vm.cfg file is missing?
    Thanx in advance for your help!

    Hi budachst,
    Thank you very much for reply, maybe I misunderstood but according to next link, RHEL6 and Solaris 11 x86_64 can be a PVM guest on OVM Serverx86 (My OVM Servers run on 64 bits):
    +"By default, Solaris 10 or Solaris 11 OS already has the required paravirtualized (PV) drivers installed as part of the OS"+ -Don't know if RHEL6 too.
    +" Oracle Solaris 11 supports x86 64-bit architecture only. "+
    http://docs.oracle.com/cd/E35328_01/E35329/html/vmrns-guest-os.html am I right?
    The thing now is, I can start and seeing in "running" state my VMs. But I want to install the OS and VNC screen appears in black, I would expect to see the SO screen instead. Any idea?

  • Is paravirtualization worth the hassle?

    I've been experimenting with both fully virtualized and paravirtualized guests (OEL 5.4 64-bits with Database 11g and user apps) under VM Server 2.2 to see how I want to make my final live production decisions, and have run into some strange issues with paravirtualization.
    I've read that a paravirtualized guest can be faster than a fully-virtualized guest and wanted to test it for myself with my database and apps.
    Creating a fully virtualized guest using the install-from-media method is straightforward and seems to give no problems and runs quite well.
    Creating a paravirtualized guest the same method has been giving me problems, but I finally got one running.
    First of all, it seems like only about one out of three paravirtualized guests created will actually start up and run. I've followed the exact same steps each time, but most times, after completing the Anaconda installer phases all the way to the point where you reboot the guest for the first time, it failed to start with an error something like: VmError: (1, 'Internal error', 'xc_dom_do_gunzip: inflate failed (rc=-3)\n'). I blew away the virtual machine and started over, and after the third attempt, it finally started up, but failed to mount the /boot filesystem, so I dropped into single user mode and ran fsck on /boot. After another restart, I finally was able to get a paravirtualized guest up and running.
    I've gone thru this ordeal over a dozen times now creating a paravirtualized guest, and only successfully been able to make three of them start and run. All these numerous failures to start with the gunzip error and having to manually fsck the /boot filesystems has made my confidence level in paravirtualized guests pretty much zero. I doubt if I could put my faith in running one as a production VM now. Even when I get one running, it still gives one boot error message of unable to update the Intel cpu microcode, but I understand what's going on there and that step of the boot process could be deleted. The install process probably should've detected that it was running in a paravirtualized VM and not included that script to begin with.
    Anyway, I've got my database and apps installed into a paravirtualized guest now, and have begun testing performance. I did run into the issue that the whole jvm subsystem of the database had to be ripped out and reinstalled under the paravirtualized guest, and also the dbconsole had to be removed and re-installed as well. I'm using tarballs of my database and application filesystems that were built within a fully virtualized guest, and even though they work fine when untarred into another freshly-created fully-virtualized guest without any repairs or modifications, these two issues arose when simply unloading the tarballs into a paravirtualized guest that was otherwise identical to the fully-virtualized guest.
    I seem to be getting slightly better query times on the paravirtualized guest, and it might be worth the effort put into making a paravirtualized guest run, but I'm now worried that paravirtualized guests will be flakey and unstable.
    Anybody else run into these kinds of issues with paravirtualization?
    The fully-virtualized guests seem to be rock-solid and very straightforward to build, configure and run.
    Is sticking with fully virtualized guests the safer choice?
    My VM Server is a brand new HP Proliant DL370 with dual quad-core 2.9GHz Nehalem-core Xeons and 64GB ram, and does seem to have ample horsepower to get the speed I need with fully-virtualized guests running my database and apps.

    I haven't heard of anyone running into the issues you mention with paravirt guests. We have extensively tested it in-house, and have also provided pre-built templates for paravirt database guests. Maybe you could give one of those a try, and see if they're more stable. There is a small chance that a guest OS configuration issue is causing the instability.

  • CSM problem when discovering a device

    Dears,
    i have CSM 4.2, i am facing a problem when i am adding one firewall, there is an asa 5580 between the CSM and that firewall 5510. there is the command fragment chain 1 INTERFACE where the 5510 is connected, when i remove this command from the 5580, the discovery works fine, in the logs it is saying that the packets are dropped due to fragment packets.. Any idea?
    Regards,

    In the past I've been successfully deploying a few Ubuntu guest VMs, Hardware Virtualized (never succeeded to put up a Paravirtualized guest though) for testing purposes.
    The latest version (10.4 maybe? Can't remember right now) worked without any sort of fixes or workarounds and was stable right away.
    Previous versions needed a fix in the "grub.conf" file, and I had to put in a "NOAPIC" option to tell the kernel to inhibit some kind of interrupt events, I'm sorry I cannot be more specific but I can't remember exactly the real reasons behind the fix, I just know that without it I was getting a "processor stuck" error on the guest's console after a while, resulting in an unresponsive VM.
    I see from your logfile that you have "APIC=1" and "ACPI=1", so maybe you'd want to play a bit with those settings and see the results.
    My processors are Intel Xeon 5450.
    HTH

  • PI 7.3 AEX - XI 3.0 message protocol in the SOAP adapter.

    Hello,
    My client's landscape is on SAP PI 7.3 AEX(Java only installation) and SAP ECC 6.0 EhP4.
    I have configured a HTTP-Proxy scenario. For the proxy messages to go into the SAP ECC system, I have configured a SOAP Receiver adapter in PI 7.3 AEX.
    I have created a service interface in ESR in PI 7.3 and generated the proxy in the SAP ECC system.
    I have configured the SOAP receiver to use the XI 3.0 protocol and by using the Addressing Type as 'URL Address'. The URL that I am using is " http://<SAP_ECC_server>:PORT/sap/xi/engine?type=entry  ".
    When I try to test the scenario, the messages are not reaching the target ECC destination and in the SOAP Receiver communication channel, I am getting the following error:
    Information:                Delivering to channel: SOAP_RECEIVER
    Information:                MP: processing local module localejbs/sap.com/com.sap.aii.af.soapadapter/XISOAPAdapterBean
    Information:                SOAP: request message entering the adapter with user Guest
    Error:                          SOAP: call failed: java.io.IOException: unable to create a socket Information                 SOAP: sending a delivery error ack ...
    Now, in my client estate there is also a SAP PI 7.11 system, I have replicated the service interface in the ESR on 7.11 and regenerated the proxy in SAP ECC. When I now run the scenario, it works.
    Just stressing here on the point that, the abap proxy generated from SAP PI 7.3 ESR did not work(but worked when I generated the abap proxy from SAP PI 7.11 ESR) when configured using the XI protocol on the SOAP adapter.
    ALso, I have gone through the 'Note 1247043 - Release Restrictions for EHP 1 for SAP NetWeaver PI 7.1'.
    Is the behaviour I am facing a release restriction on SAP PI 7.3
    Need suggestions from anyone who has tried configuring this scenario, is there anything that I have missed?
    I am happy to share more info if required...
    Thanks in advance,
    Best Regards,
    Karthik

    HI Karthik,
    Did you able to resolve this in PI 7.3??
    Even i am also facing the same issue in receiver soap adapter for abap server proxy:
    SOAP: error occured: com.sap.engine.interfaces.messaging.api.exception.MessagingException: java.io.IOException: unable to create a socket
    MP: exception caught with cause com.sap.engine.interfaces.messaging.api.exception.MessagingException: java.io.IOException: unable to create a socket
    Transmitting the message to endpoint <local> using connection File_http://sap.com/xi/XI/System failed, due to: com.sap.engine.interfaces.messaging.api.exception.MessagingException: java.io.IOException: unable to create a socket
    Please let me know how did u resolve this?
    Thanks,
    Prasanthi

Maybe you are looking for