similar to: [help] why `xl restore` always return error for `xc: error: do_evtchn_op: HYPERVISOR_event_channel_op failed: -1: Internal error`

What are the possible cases (I hope there are not many:)) that this Hypercall might fail, HYPERVISOR_event_channel_op(EVTCHNOP_send, &op)???,With an error value of "-ENOSYS (-38)" on a "HVM"? Thx, Venkat _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

Hi all, In xen-4.1.2/tools/libxl/xl_cmdimpl.c : create_domain(), it starts up a child daemon process waiting for the domain death, there are several lines echo the child pid as follows: 1592 if (child1) { /*it''s in the parent*/ 1593 printf("Daemon running with PID %d\n", child1); /**it''s in the child/ 1643

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

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

Dom0: Wheezy 64 bit with kernel from package linux-image-3.2.0-2-amd64 version 3.2.12-1, package blktap-dkms and all dependency packages for xen, spice and usb redirection. ------------------------- /etc/modules ------------ loop max_loop=64 xenfs xen-evtchn blktap ------------------------- hg clone http://xenbits.xen.org/xen-unstable.hg (in this build changeset is 25194:6b72eb3b40cf) # Qemu

Hello all, after XEN 4.3.0 with Kernel 3.10.9 has restored suspended (saved) Domains there are still some processes around which from my point of view should have disappeared after restoring. This entries are still in the Process list: root 3347 1 0 09:30 ? 00:00:00 /usr/local/sbin/xl restore /var/lib/xen/save/frntsrv01-v7 root 3737 1 0 09:30 ? 00:00:00

Hardware: blade HS20 on RHEL4 U1 base kernel. # hg tip changeset: 6811:a8edb2655c5d220b1bbf2b8d8415aae0ac136da3 tag: tip user: cl349@firebug.cl.cam.ac.uk date: Wed Sep 14 10:47:48 2005 summary: Add methods to read/write Vm/Domain store entries. I created domU and got the messages: # xm create -c vm2.cfg Using config file "vm2.cfg". Started domain

# HG changeset patch # User George Dunlap <george.dunlap@eu.citrix.com> # Date 1345022863 -3600 # Node ID 0982bad392e4f96fb39a025d6528c33be32c6c04 # Parent dc56a9defa30312a46cfb6ddb578e64cfbc6bc8b xl: Suppress spurious warning message for cpupool-list libxl_cpupool_list() enumerates the cpupools by "probing": calling cpupool_info, starting at 0 and stopping when it gets an error.

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

libxenlight exports a function libxl_uuid2string which is used internally in several places but has one external caller in xl. The function mainly implements policy so should not be part of the libxenlight API. The extent to which it can be considered mechanism it is not a xen mechanism since UUID''s are not a concept exlusive to xen. The one caller in xl seems to be an

Hi As we will use xl in xen 4.1. I had try use xl to do something. And I find some command is fails. For config file, when give "disk=" too args, it will show segment fault if we use xl create to start guest. Is there any change for xl''s config file? Following command can not work: xl migrate: when I use xl migrate domain localhost to do migrate, it shows error:

Package: xen-utils-common Version: 4.1.2-1 Severity: normal Hi, I was doing some experiments today with XL TOOLSTACK, and found few problems when trying to do PV domU boot. I was trying to run kfreebsd9 or linux-3.2 kernel in qemu using PV i386, and with simple configuration without any disks, nics or virtual framebuffer, kernel boots (and then kernel itselfs correctly fails with information

Just out of annoyance more than curiosity, but ever since I started using Xen 4.2-unstable rev-25467, every time I try to run "sudo xl create <domu_config_file>", or "sudo xl reboot", or "sudo xl destroy", it always gives me this message: "*xend is running, which prevents xl from working correctly. If you still want to force the execution of xl please

A pv guest will not reboot after migration, the guest itself does everything right, including the shutdown, but xl does not recreate the guest, it just shuts it down. This goes for 2.6.39 and 3.0.4 guest kernels, havent tried different ones. I also haven tried different xen versions. Dont know if this would affect hvm, probably not since qemu leaves the guest running and does a

Thanks, I'll take a look at this. Mike On Sat, Jun 1, 2013 at 12:28 AM, David Su?rez <david.sephirot at gmail.com>wrote: > Source: xen-api > Version: 1.3.2-15 > Severity: serious > Tags: jessie sid > User: debian-qa at lists.debian.org > Usertags: qa-ftbfs-20130529 qa-ftbfs > Justification: FTBFS on amd64 > > Hi, > > During a rebuild of all packages

From: David Vrabel <david.vrabel@citrix.com> autoballoon=1 is not recommened if dom0_mem was used to reduce the amount of dom0 memory. Instead of requiring users to change xl.conf if they do this, extend the autoballoon option with a new choice: "auto". With autoballoon="auto", autoballooning will be disabled if dom0_mem was used on the Xen command line. For

I''m using FC5 with its Xen 3.0.2-2 package and 2.6.16-1.2118_FC5xen0 kernel. I''ve got a Pentium 9xx chip with virtualization enabled in the BIOS; it appears to be VT-enabled, since xm dmesg includes "(XEN) VMXON is done". I base my config file on example.hvm and on previous emails to this list. Unfortunately, I don''t get very far. xm create winxp.conf

On 31.10.13 04:34, Miguel Clara wrote: > I was trying to get a core-dump for a domU with xl and got this error: > > # xl dump-core 20 test.core > Memory fault > > GDB shows this: > > a# gdb xl xl.core > GNU gdb (GDB) 7.3.1 > Copyright (C) 2011 Free Software Foundation, Inc. > License GPLv3+: GNU GPL version 3 or later<http://gnu.org/licenses/gpl.html> >

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

# HG changeset patch # User Ian Campbell <ijc@hellion.org.uk> # Date 1354011148 0 # Node ID 3174dc24e3efb0c5b964c244dbfb0218a03a38cf # Parent 541b0e1a36c86db5df04988dd4ade5430776a7f2 xl: xl.conf(5): correct advice re autoballooning vs. dom0_mem. The advice was backwards, you should really disable autoballoon if you use dom0_mem. Also add a reference to the command-line docs.