search for: libxl__wait_for_device_model

I think it has to be something trivial, but I cannot start 2 windows servers at the same time on the same dom0. If I start server 2008 first I can''t start 2012, if I start 2012, I can''t start 2008. The failure is: libxl: error: libxl_device.c:470:libxl__wait_for_device_model Device Model not ready xl: fatal error: libxl_create.c:535, rc=-1: libxl__confirm_device_model_startup The config files are almost exactly the same with the exception on one using cpu2 and the other using cpu3, and one using a physical disk and the other a virtual one. 2008: kernel = "/...

To remove a pci passthough device from QEMU (upstream). Signed-off-by: Anthony PERARD <anthony.perard@citrix.com> --- tools/libxl/libxl_internal.h | 2 ++ tools/libxl/libxl_qmp.c | 35 +++++++++++++++++++++++++++++++++++ 2 files changed, 37 insertions(+), 0 deletions(-) diff --git a/tools/libxl/libxl_internal.h b/tools/libxl/libxl_internal.h index 1dff211..84da6b1 100644 ---

I''ve just had my first attempt at getting VGA passthrough to work, and it crashed the machine. I''m trying to understand whether this is a problem with my hardware, configuration or a software problem. I''m running Xen 4.1.2 with Linux 3.1.2 The CPU is an Intel Core i5-650 http://ark.intel.com/products/43546/Intel-Core-i5-650-Processor-%284M-Cache-3_20-GHz%29 The Video

Does anyone use xen-4.1.1 + linux-3.0-rc6 (vanilla)? when using "xl create" on pv domUs, it fails with libxl: error: libxl_device.c:476:libxl__wait_for_device_model Device Model not ready xl: fatal error: libxl_create.c:535, rc=-1: libxl__confirm_device_model_startup However, any one of: - using xm - using HVM domU - using a different dom0 kernel (e.g. 2.6.32 from JF''s git) ... will enable domU to start. -- Fajar _________________________________...

...when I try to do the following cmd: I got some errors like below: # xl pci-attach 7 0000:03:10.2 libxl: error: libxl_pci.c:750:libxl_device_pci_reset The kernel doesn''t support reset from sysfs for PCI device 0000:03:10.2 libxl: error: libxl_device.c:470:libxl__wait_for_device_model Device Model not ready what''s wrong? The guest os I''m using is Centos 6.3, hvm type, I have already installed the pv-drivers for it. when I execute lspci in the vm, it looks no problem. what''s wrong, please help, thanks. _________________________...

...      0000000000100000->000000000017b150   TOTAL:         0000000000000000->000000007f800000   ENTRY ADDRESS: 0000000000101580 xc: info: PHYSICAL MEMORY ALLOCATION:   4KB PAGES: 0x0000000000000200   2MB PAGES: 0x00000000000003fb   1GB PAGES: 0x0000000000000000 libxl: error: libxl_device.c:476:libxl__wait_for_device_model Device Model not ready xl: fatal error: libxl_create.c:535, rc=-1: libxl__confirm_device_model_startup _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

...      0000000000100000->000000000017b150   TOTAL:         0000000000000000->000000007f800000   ENTRY ADDRESS: 0000000000101580 xc: info: PHYSICAL MEMORY ALLOCATION:   4KB PAGES: 0x0000000000000200   2MB PAGES: 0x00000000000003fb   1GB PAGES: 0x0000000000000000 libxl: error: libxl_device.c:476:libxl__wait_for_device_model Device Model not ready xl: fatal error: libxl_create.c:535, rc=-1: libxl__confirm_device_model_startup _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

...) 4.1 hypervisor with 2.6.38 kernel, any attempt to create a VM failed (also the ones saved from previous book don't come up either). If I try to use xl : # xl create /etc/xen/lithium.vm.carpediem.sh.cfg Parsing config file /etc/xen/lithium.vm.carpediem.sh.cfg libxl: error: libxl_device.c:476:libxl__wait_for_device_model Device Model not ready xl: fatal error: libxl_create.c:535, rc=-1: libxl__confirm_device_model_startup There's one line into /var/log/xen/qemu-dm-lithium.vm.carpediem.sh.log (which didn't existed before the xl command): libxl: cannot execute /usr/lib/xen-4.1/lib/qemu-dm: No such file or di...

Anthony PERARD (3): libxl_qmp: Use GC instead of CTX as parameter for _initialize. Provide dm_vnc() as a in libxl helper. libxl: Set VNC password through QMP tools/libxl/libxl_create.c | 2 +- tools/libxl/libxl_dm.c | 32 ++++++++++++++---------- tools/libxl/libxl_internal.h | 7 ++++- tools/libxl/libxl_qmp.c | 55 ++++++++++++++++++++++++++++++----------- 4 files

Package: xen-utils-4.1 Version: 4.1.3-2 Severity: important Dear Maintainer, Creating a new HVM domU fails with the following error: map shared IO page returned error 22 I've narrowed it down to qemu-dm which fails to start: # /usr/lib/xen-4.1/bin/qemu-dm [...] qemu_map_cache_init nr_buckets = 10000 size 4194304 errno0 = 2 domid = -1 shared page at pfn 0 errno1 = 3 errno2 = 22 map shared IO

Hi, I build Xen 4.1.1 on a Gentoo base dom0. Everything is working great. I tried one of Joseph Glanville''s PV-HVM image (debian6) and its working as it should. Now l''im trying to build a Gentoo based domU with then same specs as Joseph''s PV-HVM. I used a copy of the .cfg and adapted to my needs to make the gentoo work. when booting the minimal install image using

...c libxl_exec.c: In function ''libxl__spawn_spawn'': libxl_exec.c:224: error: ignoring return value of ''write'', declared with attribute warn_unused_result make[3]: *** [libxl_exec.o] Error 1 cc1: warnings being treated as errors libxl_device.c: In function ''libxl__wait_for_device_model'': libxl_device.c:488: error: ignoring return value of ''read'', declared with attribute warn_unused_result make[3]: *** [libxl_device.o] Error 1 _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com...

Hi, All Intel QA conducted a full validation for xen 4.1 rc1, it includes VT-x, VT-d, SRIOV, RAS, TXT and xl tools testing. 24 issues were exposed. Refer the bug list, please. We already assigned 14 bugs to Intel developers (which has an ''Intel'' tag in the bug title), most of the rest 10 bugs are related xl command. For the these bugs, need community''s help to fix