similar to: Possible bug in Xen 4.2.1 when rebooting domU after save/restore

Displaying 20 results from an estimated 500 matches similar to: "Possible bug in Xen 4.2.1 when rebooting domU after save/restore"

2019 Jan 07
2
Bug#776450: Xen PVH support for grub-xen in Buster
On Mon, Jan 07, 2019 at 08:44:50AM +0000, Colin Watson wrote: > On Mon, Jan 07, 2019 at 01:58:19AM +0100, Hans van Kranenburg wrote: > > Ok great. Since I'm not using (and probably not going to use) the > > multi-stage multiboot things, this is harder for me to help with. > > With any luck I should be able to work that bit out myself, since I > think stable's Xen
2013 Feb 21
4
help please - running a guest from an iSCSI disk ? getting more diagnostics than "cannot make domain: -3" ? how to make domain0 "privileged" ?
Good day - This is my first post to this list , and I''m new to Xen - any help on this issue would be much appreciated . I downloaded, built and installed xen-4.2.1 (hypervisor and tools) on an x86_64 ArchLinux box updated to latest software as of today. I am trying to bring up a Linux guest from a remote iSCSI disk. The iSCSI-initiator (open-iscsi) logs in to the remote target OK and
2013 Feb 24
1
xen hvm fails to start
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:
2012 Sep 21
6
xl create bug on first-attempt with passthrough
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
2016 Apr 05
1
Xen custom vifname
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
2012 Nov 23
1
[PATCH] libxl - fix a variable underflow in libxl_wait_for_free_memory
When xl is called to create a domU and there is not enough memory available, then the autoballooning is called to extract memory from dom0. During the ballooning a loop in libxl_wait_for_free_memory() waits unless enough memory is available to create the domU. But because of a variable-underflow the loop can finish too soon and xl finally aborts with the message: xc: error: panic:
2015 Nov 18
4
Bug#805508: xen: Unable to create HVM domUs
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
2013 Apr 24
15
Bare-metal Xen on ARM boot
Hi, I was wondering if there is any documentation on how to write a bare metal application for Xen. I don''t need to parse the device tree and such yet, a simple booting "Hello World" would be fine :-) We wrote one and when trying to boot we get ( this was an uncompressed binary, no image): libxl: notice: libxl_numa.c:451:libxl__get_numa_candidate: NUMA placement failed,
2013 Dec 01
1
Bug#731038: xen-utils-4.3: cannot create hwm
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:
2015 Oct 01
5
xen and spice problem
Hi it is possible to use xen and spice already? If yes is there any howto or doc how? If I turn on spice in cfg of a hvm domU, I get this error: Parsing config from /etc/xen/marax.cfg libxl: detail: libxl_dom.c:238:hvm_set_viridian_features: base group enabled libxl: detail: libxl_dom.c:238:hvm_set_viridian_features: freq group enabled libxl: detail:
2013 Oct 14
14
spice issue
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
2018 May 27
1
Using libvirt to access Ceph RBDs with Xen
Hi everybody, my background: I'm doing Xen since 10++ years, many years with DRBD for high availability, since some time I'm using preferable GlusterFS with FUSE as replicated storage, where I place the image-files for the vms. In my current project we started (successfully) with Xen/GlusterFS too, but because the provider, where we placed the servers, uses widely CEPH, we decided to
2023 Jul 20
3
Bug#1041533: xen-system-amd64: Xen fails to start hvm type VMs when a vncpasswd is set
Package: xen-system-amd64 Version: 4.17.1+2-gb773c48e36-1 Severity: important Dear Maintainer, after upgrading my bullseye server to bookworm I ran into the issue that all VMs of type hvm are not starting anymore. xl throws an error: libxl: error: libxl_qmp.c:1399:qmp_ev_fd_callback: Domain 8:error on QMP socket: Connection reset by peer libxl: error: libxl_qmp.c:1438:qmp_ev_fd_callback: Domain
2019 Jan 07
2
Bug#776450: Xen PVH support for grub-xen in Buster
On 1/6/19 11:21 AM, Colin Watson wrote: > On Sat, Jan 05, 2019 at 10:51:13PM +0100, Hans van Kranenburg wrote: >> On 1/5/19 8:04 PM, Colin Watson wrote: >>> I think I'm OK with cherry-picking the relevant patch stack. Presumably >>> this would need to be in new grub-xen-pvh-bin / grub-xen-pvh binary >>> packages, as is usual for separate platform builds?
2015 Nov 25
3
Bug#806226: xen-hypervisor-4.6-amd64: Can't start a VM
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
2012 Nov 02
2
Remus: Xen 4.2.1 with Debian 6.0 does not work
_______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users
2012 Nov 02
2
Remus: Xen 4.2.1 with Debian 6.0 does not work
_______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users
2015 Oct 01
0
xen and spice problem
On Thu, Oct 1, 2015 at 10:06 AM, Christoph <mangel at gmx.de> wrote: > Hi > > it is possible to use xen and spice already? If yes is there any howto or > doc how? Fabio has been the one working on getting spice working. Fabio, any ideas? > > If I turn on spice in cfg of a hvm domU, I get this error: > > Parsing config from /etc/xen/marax.cfg > libxl: detail:
2014 Oct 13
0
Arch linux PV guest won't boot
Hi, I have Xen installed and running several (win 7) HVMs. I've setup an Arch linux PV guest but I am having a problem booting it. (The install image booted fine.) After each failed attempt to boot I try to view the /var/log/xen/bootloader.XX.log file but all of these files are zero bytes. So, I'm having some trouble troubleshooting this. I followed the instructions from
2012 Sep 29
0
Xen 4.2.1-pre DomU create error
Parsing config from server2008.cfg xc: info: VIRTUAL MEMORY ARRANGEMENT: Loader: 0000000000100000->000000000019ddf0 TOTAL: 0000000000000000->000000001f800000 ENTRY ADDRESS: 0000000000100000 xc: info: PHYSICAL MEMORY ALLOCATION: 4KB PAGES: 0x0000000000000200 2MB PAGES: 0x00000000000000fb 1GB PAGES: 0x0000000000000000 libxl: error: