search for: initiate_domain_create

...ord 35 of 72 ==5722== at 0x4026B2D: malloc (vg_replace_malloc.c:299) ==5722== by 0x41739FF: strdup (strdup.c:43) ==5722== by 0x405F38E: libxl__device_disk_local_initiate_attach (libxl.c:2681) ==5722== by 0x408D2A6: libxl__bootloader_run (libxl_bootloader.c:385) ==5722== by 0x406B50C: initiate_domain_create (libxl_create.c:807) ==5722== by 0x406B50C: do_domain_create (libxl_create.c:1354) ==5722== by 0x406B6AF: libxl_domain_create_new (libxl_create.c:1377) ==5722== by 0x8056182: create_domain (xl_cmdimpl.c:2254) ==5722== by 0x8059F27: main_create (xl_cmdimpl.c:4407) ==5722== by 0x804E11...

...lable, use qemu-xen-traditional instead: No such file or directory libxl: debug: libxl_device.c:257:libxl__device_disk_set_backend: Disk vdev=xvda spec.backend=unknown libxl: debug: libxl_device.c:296:libxl__device_disk_set_backend: Disk vdev=xvda, using backend phy libxl: debug: libxl_create.c:675: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:608:libxl__ev_xswatch_deregister: watch w=0x1981588: deregister unregistered libxl: notice: libxl_numa.c:491:libxl__get_numa_candidate: NUMA placement fai...

...= at 0x4026B2D: malloc (vg_replace_malloc.c:299) > ==5722== by 0x41739FF: strdup (strdup.c:43) > ==5722== by 0x405F38E: libxl__device_disk_local_initiate_attach (libxl.c:2681) > ==5722== by 0x408D2A6: libxl__bootloader_run (libxl_bootloader.c:385) > ==5722== by 0x406B50C: initiate_domain_create (libxl_create.c:807) > ==5722== by 0x406B50C: do_domain_create (libxl_create.c:1354) > ==5722== by 0x406B6AF: libxl_domain_create_new (libxl_create.c:1377) > ==5722== by 0x8056182: create_domain (xl_cmdimpl.c:2254) > ==5722== by 0x8059F27: main_create (xl_cmdimpl.c:4407) &gt...

Package: xen-utils-common Version: 4.4.1-6 Severity: normal Dear Maintainer, (There appear to be several reports on the BTS with concerns relating to this report. Some unarchiving/merging may be necessary. Reassignment may be needed as well since I'm not sure which package this problem would fall under. Ultimately decided to file with xen-utils-common with 'xl' being the frontend

...d phy unsuitable as phys path not a block device libxl: debug: libxl_device.c:184:disk_try_backend: Disk vdev=hdc, backend tap unsuitable because blktap not available libxl: debug: libxl_device.c:265:libxl__device_disk_set_backend: Disk vdev=hdc, using backend qdisk 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=0x9cdb40: deregister unregistered libxl: debug: libxl_numa.c:435:libxl__get_numa_candidate: New best NUMA placem...

...# xl -vvv create -c /etc/xen/${domain}.cfg Parsing config from ${domain}.cfg libxl: debug: libxl_create.c:1174:do_domain_create: ao 0x119c890: create: how=(nil) callback=(nil) poller=0x119c920 libxl: error: libxl_create.c:420:libxl__domain_make: domain creation fail libxl: error: libxl_create.c:646:initiate_domain_create: cannot make domain: -3 libxl: error: libxl.c:1394:libxl__destroy_domid: non-existant domain -1 libxl: error: libxl.c:1358:domain_destroy_callback: unable to destroy guest with domid 4294967295 libxl: error: libxl_create.c:1153:domcreate_destruction_cb: unable to destroy domain 4294967295 following...

Package: xen-utils-4.4 Version: 4.4.1-3 When booting domU's running amd64 jessie, I notice some memory problems with xl. root at xen:~# pmap -x 4121 4121: /usr/lib/xen-4.4/bin/xl create --quiet --defconfig /etc/xen/auto/mail_deb80.cfg Address Kbytes RSS Dirty Mode Mapping 0000000000400000 144 128 0 r-x-- xl 0000000000623000 4 4 4 r---- xl

Hello, I recently swapped some components, and rebuilt my system. Changes to the configuration: - Wheezy Beta 1 > Wheezy Beta 2 - Kernel 3.4.9 > Kernel 3.4.11 I have tested the new Xen 4.2 stable, and Xen unstable revision 25777, both are giving me the same error so I do not believe it is related to a change in Xen. The first attempt to pass a PCI device after booting the system

Hi, Here is a little patch that attempt to fix the issue regarding xen_platform_pci=0 not been handled. There is one patch left from the previous version. The patch that was adding qemu_machine_override have been removed as it is unnecessary. If someone wants to change the -machine, it can always add it to device_model_args_hvm, as QEMU appear to use the last one. Regards, Anthony PERARD (1):

Hi, everyone! We google a lot, but can''t find how to config the pvscsi on our ubuntu13.04 PV on HVM.There are some links http://wiki.xen.org/wiki/Paravirtualized_SCSI http://wiki.xen.org/wiki/Xen_Configuration_File_Options And we use the config option above Configure PVSCSI devices vscsi = [ ''/dev/sdc, 0:0:0:0'' ] I pass sdc to the hvm, but in our pvhvm (ubuntu13.04)

...ference_unmap(&info->u.pv.kernel); - libxl__file_reference_unmap(&info->u.pv.ramdisk); + libxl__file_reference_unmap(&state->pv_kernel); + libxl__file_reference_unmap(&state->pv_ramdisk); } esave = errno; @@ -625,16 +627,21 @@ static void initiate_domain_create(libxl libxl_device_disk *bootdisk = d_config->num_disks > 0 ? &d_config->disks[0] : NULL; - if (restore_fd < 0 && bootdisk) { + if (restore_fd >= 0) { + LOG(DEBUG, "restoring, not running bootloader\n"); + domcreate_bootloader...

...dev=hdc, backend phy unsuitable as phys path not a block device libxl: debug: libxl_device.c:206:disk_try_backend: Disk vdev=hdc, backend tap unsuitable for cdroms libxl: debug: libxl_device.c:296:libxl__device_disk_set_backend: Disk vdev=hdc, using backend qdisk libxl: debug: libxl_create.c:675: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:608:libxl__ev_xswatch_deregister: watch w=0xf90128: deregister unregistered libxl: debug: libxl_numa.c:475:libxl__get_numa_candidate: New best NUMA pla...

I''m unable to start xl console on latest xen-unstable (build with commit 8e0da8c07f4f80e14314977a11f738bd74a5b62b). > xl -vvv console sid > xenconsole: Could not read tty from store: No such file or directory I also tried "xl create -c", and it shows console from pygrub but when the "xl create" reaches the end I got the same error: > xenconsole: Could not

...ackend: Disk vdev=hda spec.backend=unknown libxl: debug: libxl_device.c:197:disk_try_backend: Disk vdev=hda, backend phy unsuitable as phys path not a block device libxl: debug: libxl_device.c:296:libxl__device_disk_set_backend: Disk vdev=hda, using backend qdisk libxl: debug: libxl_create.c:697: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:608:libxl__ev_xswatch_deregister: watch w=0x193b998: deregister unregistered libxl: debug: libxl_numa.c:475:libxl__get_numa_candidate: New best NUMA pl...

*RESEND* due to exceeding the mailinglists limit for attachment size. Hi, I''m trying to get secondary vga-passthrough on a HVM guest to work with a AMD HD6570 and the native kernel radeon driver and kernel modesetting. So the guest still gets the emulated stdvga or cirrus device(used in my case here) as primary/boot vga adapter. - When i don''t passthrough the radeon card, the

Hello, Third version of the NUMA placement series Xen 4.2. All the comments received during v2''s review have been addressed (more details in single changelogs). The most notable changes are the following: - the libxl_cpumap --> libxl_bitmap renaming has been rebased on top of the recent patches that allows us to allocate bitmaps of different sizes; - the heuristics for deciding