search for: libxl__device_disk_set_backend

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

...t was the same regardless of what OS I attempted to use). Any suggestions would be appreciated. Thanks, Casey Parsing config from /etc/xen/win8.cfg libxl: debug: libxl_create.c:1173:do_domain_create: ao 0x9cc890: create: how=(nil) callback=(nil) poller=0x9cc920 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=hdc spec.backend=unknown libxl: debug: libxl_device.c:175:disk_try_backend: Disk vdev=hdc,...

...2'/> <graphics type='vnc' port='-1' autoport='yes'/> </devices> </domain> Error.log libxl: debug: libxl_create.c:1342:do_domain_create: ao 0x7ff010003e00: create: how=(nil) callback=(nil) poller=0x7ff01000cb70 libxl: debug: libxl_device.c:251:libxl__device_disk_set_backend: Disk vdev=hda spec.backend=tap libxl: debug: libxl_device.c:210:disk_try_backend: Disk vdev=hda, backend tap unsuitable because blktap not available libxl: error: libxl_device.c:289:libxl__device_disk_set_backend: no suitable backend for disk hda libxl: error: libxl_dm.c:1467:kill_device_model: un...

...debug: libxl_create.c:1230:do_domain_create: ao 0x19811c0: create: how=(nil) callback=(nil) poller=0x1981220 libxl: verbose: libxl_create.c:130:libxl__domain_build_info_setdefault: qemu- xen is unavailable, 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 b...

...=============================== teo-en-ming@intel-core-i5-4430-desktop:~$ sudo xl -vvv create /etc/xen/windows8 Parsing config from /etc/xen/windows8 libxl: debug: libxl_create.c:1230:do_domain_create: ao 0xf8fda0: create: how=(nil) callback=(nil) poller=0xf8f5e0 libxl: debug: libxl_device.c:257:libxl__device_disk_set_backend: 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:212:disk_try_backend: Disk vdev=hda, backend tap unsuitable because blktap not available libxl: debug: libxl_d...

...t;pygrub" extra = "debian-installer/exit/always_halt=true -- console=hvc0" cpu_weight=256 vif=[''bridge=xenbr0''] When I try to boot the VM with the above configuration I get the following error: Parsing config file debian-blktap2.cfg libxl: debug: libxl_device.c:183:libxl__device_disk_set_backend: Disk vdev=xvda spec.backend=unknown libxl: debug: libxl_device.c:137:disk_try_backend: Disk vdev=xvda, backend phy unsuitable as phys path not a block device libxl: debug: libxl_device.c:144:disk_try_backend: Disk vdev=xvda, backend tap unsuitable because blktap not available libxl: debug: libxl_d...

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)

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

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

...xxxfd</serial> </disk> But there is no way to attach the device to running machine, I only see this error on libxl : libxl: debug: libxl.c:3538:libxl_device_disk_add: ao 0x7fe248006080: create: how=(nil) callback=(nil) poller=0x7fe24000ce20 libxl: debug: libxl_device.c:251:libxl__device_disk_set_backend: Disk vdev=xvdd spec.backend=qdisk libxl: debug: libxl_event.c:618:libxl__ev_xswatch_deregister: watch w=0x7fe248001780: deregister unregistered libxl: debug: libxl_event.c:1591:libxl__ao_complete: ao 0x7fe248006080: complete, rc=0 libxl: debug: libxl.c:3538:libxl_device_disk_add: ao 0x7fe248006080...

Hi, List, I''m trying xl create a pv guest with qcow/qcow2 image, it always fails at libxl_device_disk_local_attach. #xl create pv_config_file libxl: error: libxl.c:1119:libxl_device_disk_local_attach: cannot locally attach a qdisk image if the format is not raw libxl: error: libxl_create.c:467:do_domain_create: failed to run bootloader: -3 disk configuration is: disk=[

...-vvv create /etc/xen/FEDORA19.cfg ------------------------------------------------------------------------ Parsing config from /etc/xen/FEDORA19.cfg libxl: debug: libxl_create.c:1252:do_domain_create: ao 0x193a970: create: how=(nil) callback=(nil) poller=0x193b630 libxl: debug: libxl_device.c:257:libxl__device_disk_set_backend: 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:initia...

...gt;uuid); } - return 0; + return libxl__resolve_domid(gc, vtpm->backend_domname, &vtpm->backend_domid); } static int libxl__device_from_vtpm(libxl__gc *gc, uint32_t domid, @@ -1968,6 +1976,7 @@ int libxl__device_disk_setdefault(libxl__gc *gc, libxl_device_disk *disk) rc = libxl__device_disk_set_backend(gc, disk); if (rc) return rc; + rc = libxl__resolve_domid(gc, disk->backend_domname, &disk->backend_domid); return rc; } @@ -2799,7 +2808,7 @@ int libxl__device_nic_setdefault(libxl__gc *gc, libxl_device_nic *nic, abort(); } - return 0; + return lib...

*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