Re: [Xen-devel] Xen HVM Guest fails (errors) to launch on Opensuse 12.2's Xen 4.2 + 'xl' toolstack

[ar16@xxxxxxxxxxxx]

hi

On Sat, Sep 29, 2012, at 07:32 PM, Joseph Glanville wrote:
> Does changing the guest disk specification to hda/hdb/hdc/hdd syntax
> correct the problem?

no, it does not.

with config --

        ...
        disk  = [       'phy:/dev/VG0/boot,hda,w',
                                'phy:/dev/VG0/swap,hdb,w',
                                'phy:/dev/VG0/root,hdc,w',
                                'phy:/dev/cdrom,hdd:cdrom,r',
        ...

executing

        xl -vvv create -c /home/ar/test.cfg

still returns,

        Parsing config from /home/ar/test.cfg
        libxl: debug: libxl_create.c:1173:do_domain_create: ao 0xd278e0:
        create: how=(nil) callback=(nil) poller=0xd281f0
        libxl: debug: libxl_device.c:229:libxl__device_disk_set_backend:
        Disk vdev=hda spec.backend=unknown
        libxl: debug: libxl_device.c:265:libxl__device_disk_set_backend:
        Disk vdev=hda, using backend phy
        libxl: debug: libxl_device.c:229:libxl__device_disk_set_backend:
        Disk vdev=hdb spec.backend=unknown
        libxl: debug: libxl_device.c:265:libxl__device_disk_set_backend:
        Disk vdev=hdb, using backend phy
        libxl: debug: libxl_device.c:229:libxl__device_disk_set_backend:
        Disk vdev=hdc spec.backend=unknown
        libxl: debug: libxl_device.c:265:libxl__device_disk_set_backend:
        Disk vdev=hdc, using backend phy
        libxl: debug: libxl_device.c:229:libxl__device_disk_set_backend:
        Disk vdev=hdd spec.backend=unknown
        libxl: debug: libxl_device.c:265:libxl__device_disk_set_backend:
        Disk vdev=hdd, using backend phy
        libxl: debug: libxl_create.c:677:initiate_domain_create: running
        bootloader
        libxl: debug: libxl_bootloader.c:321:libxl__bootloader_run: not
        a PV domain, skipping bootloader
        libxl: debug: libxl_event.c:561:libxl__ev_xswatch_deregister:
        watch w=0xd28790: deregister unregistered
        libxl: debug: libxl_numa.c:435:libxl__get_numa_candidate: New
        best NUMA placement candidate found: nr_nodes=1, nr_cpus=4,
        nr_vcpus=5, free_memkb=6841
        libxl: detail: libxl_dom.c:192:numa_place_domain: NUMA placement
        candidate with 1 nodes, 4 cpus and 6841 KB free selected
        xc: detail: elf_parse_binary: phdr: paddr=0x100000 memsz=0x9e028
        xc: detail: elf_parse_binary: memory: 0x100000 -> 0x19e028
        xc: info: VIRTUAL MEMORY ARRANGEMENT:
          Loader:        0000000000100000->000000000019e028
          TOTAL:         0000000000000000->000000003f000000
          ENTRY ADDRESS: 0000000000100000
        xc: info: PHYSICAL MEMORY ALLOCATION:
          4KB PAGES: 0x0000000000000200
          2MB PAGES: 0x00000000000001f7
          1GB PAGES: 0x0000000000000000
        xc: detail: elf_load_binary: phdr 0 at 0x0x7f9da35c1000 ->
        0x0x7f9da3655eb5
        libxl: error: libxl_create.c:901:domcreate_rebuild_done: cannot
        (re-)build domain: -3
        libxl: error: libxl_dm.c:1251:libxl__destroy_device_model: could
        not find device-model's pid for dom 70
        libxl: error: libxl.c:1429:libxl__destroy_domid:
        libxl__destroy_device_model failed for 70
        libxl: debug: libxl_event.c:1497:libxl__ao_complete: ao
        0xd278e0: complete, rc=-3
        libxl: debug: libxl_create.c:1186:do_domain_create: ao 0xd278e0:
        inprogress: poller=0xd281f0, flags=ic
        libxl: debug: libxl_event.c:1469:libxl__ao__destroy: ao
        0xd278e0: destroy
        xc: debug: hypercall buffer: total allocations:482 total
        releases:482
        xc: debug: hypercall buffer: current allocations:0 maximum
        allocations:4
        xc: debug: hypercall buffer: cache current size:4
        xc: debug: hypercall buffer: cache hits:474 misses:4 toobig:4

> Also, can you post the qemu-dm logs for that domain? (usually in
> /var/log/xen/qemu-dm-*)

cat /var/log/xen/qemu-dm-test.log
        domid: 69
        Using file /dev/VG0/boot in read-write mode
        Using file /dev/VG0/swap in read-write mode
        Using file /dev/VG0/root in read-write mode
        Using file /dev/cdrom in read-only mode
        Watching /local/domain/0/device-model/69/logdirty/cmd
        Watching /local/domain/0/device-model/69/command
        Watching /local/domain/69/cpu
        char device redirected to /dev/pts/2
        qemu_map_cache_init nr_buckets = 10000 size 4194304
        shared page at pfn feffd
        buffered io page at pfn feffb
        Guest uuid = 4c29586f-89bd-8c01-e00a-5af6a7ce8267
        Time offset set 0
        char device redirected to /dev/pts/3
        xen be: console-0: xen be: console-0: initialise() failed
        initialise() failed
        populating video RAM at ff000000
        mapping video RAM from ff000000
        Register xen platform.
        Done register platform.
        platform_fixed_ioport: changed ro/rw state of ROM memory area.
        now is rw state.
        xs_read(/local/domain/0/device-model/69/xen_extended_power_mgmt):
        read error
        xs_read(): vncpasswd get error.
        /vm/4c29586f-89bd-8c01-e00a-5af6a7ce8267/vncpasswd.
        medium change watch on `hdd' (index: 3): /dev/cdrom
        I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0,
        size: 0
        Log-dirty: no command yet.
        xen be: console-0: xen be: console-0: initialise() failed
        initialise() failed
        vcpu-set: watch node error.
        xen be: console-0: xen be: console-0: initialise() failed
        initialise() failed
        xs_read(/local/domain/69/log-throttling): read error
        qemu: ignoring not-understood drive
        `/local/domain/69/log-throttling'
        medium change watch on `/local/domain/69/log-throttling' -
        unknown device, ignored
        xen be: console-0: xen be: console-0: initialise() failed
        initialise() failed

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel