similar to: Xen 4.2.1-pre DomU create error

Package: xen-utils-4.3 Version: 4.3.0-3 Severity: normal II'm install xen-4.3 from official repository. When i try create virtulal machine got error: xl -vvvv create /etc/xen/xlexample.hvm Parsing config from /etc/xen/xlexample.hvm libxl: debug: libxl_create.c:1230:do_domain_create: ao 0x19811c0: create: how=(nil) callback=(nil) poller=0x1981220 libxl: verbose:

When I try to start hvm qemu-xen I get this error It seems that the path my be off. Can someone point me were in source code path to qemu pid is defined .It seems that qeum-xen points to loacation I don''t see were it is defined. xc: detail: elf_load_binary: phdr 0 at 0x0x7f71cac72000 -> 0x0x7f71cad079d5 libxl: error: libxl_dom.c:612:libxl__build_hvm: hvm building failed libxl: error:

hi, i am trying to create hvm in xen via libvirt but i am facing some error. i installed the packages like bltap-utils, blktap-dkms in my dom0. virsh create tiny_core.xml p11-kit: invalid config filename, will be ignored in the future: /etc/pkcs11/modules/gnome-keyring-module error: Failed to create domain from tiny_core.xml error: internal error: libxenlight failed to create new domain

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

Package: xen-utils-4.3 Version: 4.3.0-3+b1 Severity: normal When I try to create an HVW withDevian/xen, I run into trouble. It used to work, maybe with xen 4.1, but it has never worked since. Bug 688311 was filed, with the same exact problem. That bug was somehow closed and no resolution or explanation was provided. I have seen posts mentioning "traditional" and "upstream"

Source: xen Version: 4.6.0-1 Severity: important Dear Maintainer, I attempted to create a HVM domU - using a config that previously worked on xen 4.4 (on Jessie). When I execute "xl create <vm config>", I get: Parsing config from router.internal.tomjepp.uk xc: error: Could not open kernel image '/usr/lib/xen/boot/hvmloader' (2 = No such file or directory): Internal

Package: xen-hypervisor-4.6-amd64 Version: 4.6.0-1 Severity: normal Dear maintaners, I was using XEN 4.4 on that machine ("unstable") and want to switch to 4.6. All xen stuff was uninstalled (XEN 4.4), the machine restarted before installing 4.6. When I uninstall XEN 4.4 (libxenlight4.4) it deinstall also part of QEMU and when I reinstall QEMU libxenlight-4.4 aws reinstalled. First

Hi All, One of our developers managed to trigger a kernel oops on a 4.4.2 dom0.. Oops text is attached. He was working on setting up network namespaces / bridging inside a centos domU, had activated the bridge and lost networking (probably config error) so he rebooted the VM. On reboot is when we saw the oops, along with various xen procs hanging: root 23388 0.0 1.6 132796 32264 ?

Hi, Centos 7 Xen4CentOS - 4.6.1 Open vSwitch When i specify custom name of the domU NIC than it refues to start vif = [ 'vifname=vNIC1' ] libxl: error: libxl_exec.c:118:libxl_report_child_exitstatus: /etc/xen/scripts/vif-openvswitch online [10168] exited with error status 1 libxl: error: libxl_device.c:1084:device_hotplug_child_death_cb: script: ip link set vif38.0 name vNIC1 failed

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

Package: xen-utils-4.1 Version: 4.1.0-3 Severity: normal After *manually* creating /var/lib/xen xl create <configfile> worked fine. Probably it would be better to have the directory created when installing this package? Error when /var/lib/xen is missing: xl create /etc/xen/domU/sandbox-debian-unstable.cfg -c Parsing config file /etc/xen/domU/sandbox-debian-unstable.cfg xc: info: VIRTUAL

Hello, After saving and restoring a DomU (teste on the same server), doing a reboot to the newly restored domU will cause it to crash. This happens on PV and PVHVM domUs. I am using qemu upstream for the HVM guests, but I don''t really think it matters as long as PV guests behave the same. I want to confirm this if possible, before submitting a bug report and more details. I am using

On Tue, 6 Feb 2018 03:05:18 +0000 Praveen Ghimire via samba <samba at lists.samba.org> wrote: > Hi, > > We migrated from Samba 3 to 4 (4.6.7-Ubuntu) and added promoted a > Server 2008R2 as a Domain Controller. We've come across the following > issues and request some suggestions to resolve them > > > - The migration didn't generate DNS entries for

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

I am having a problem with accessing a Samba share from a Windows 7 system. I think I have the Samba system configured correctly because I can join the Domain. root at ubuntu-server:/home/daved/AddToDCScripts# net rpc join -U Administrator Enter Administrator's password: Joined domain DEMLAND. I can use the smbclient to access the domain controller without a problem: root at

On Tue, 2018-02-06 at 03:05 +0000, Praveen Ghimire via samba wrote: > Hi, > > We migrated from Samba 3 to 4 (4.6.7-Ubuntu) and added promoted a > Server 2008R2 as a Domain Controller. We've come across the following > issues and request some suggestions to resolve them > > > - The migration didn't generate DNS entries for the new > realm. We had to

I was sort of hoping that is was something simple like setting the "do_the_right_thing" flag. The libvirtd kicks out 2014-10-31 11:58:57.111+0000: 8741: error : virRegisterNetworkDriver:549 : driver in virRegisterNetworkDriver must not be NULL 2014-10-31 11:59:29.379+0000: 8840: error : virRegisterNetworkDriver:549 : driver in virRegisterNetworkDriver must not be NULL 2014-10-31

Hi, I am trying to VGA passthrough Intel HD Graphics 4600 IGD with Xen-unstable 4.4 changeset 27214 and Linux kernel 3.10.0 but was not successful. Details are as follows: =============================================================================================== teo-en-ming@intel-core-i5-4430-desktop:~$ sudo xl info [sudo] password for teo-en-ming: host :

Did something had chaqnged with spice code or settings. I just compiled latest git of 4.4 unstable and I get is a black screen all I see is the green boot image from server 2012 but I dont get blue windows logo and window does not resize it stays black. I reverted back to older git revision of 4.4 and everything is working fine with. _______________________________________________ Xen-users

On Fri, Oct 31, 2014 at 08:34:48AM -0400, Alvin Starr wrote: >I was sort of hoping that is was something simple like setting the >"do_the_right_thing" flag. > > >The libvirtd kicks out >2014-10-31 11:58:57.111+0000: 8741: error : virRegisterNetworkDriver:549 >: driver in virRegisterNetworkDriver must not be NULL >2014-10-31 11:59:29.379+0000: 8840: error :