similar to: Bug#737613: xen-hypervisor-4.3-amd: Xen not loading dom0 on Jessie - FATAL error on running /etc/init.d/xen

Package: xen-hypervisor-4.3-amd64 Version: 4.3.0-3+b1 Severity: critical File: xen-hypervisor-4.3-amd Justification: breaks the whole system Dear Maintainer, Installation is a minimal system designed only to get dom0 working. The following are the uncommented GRUB commands GRUB_DEFAULT=0 GRUB_TIMEOUT=5 GRUB_DISTRIBUTOR=`lsb_release -i -s 2> /dev/null || echo Debian`

Hi Thanks for that. I'm not sure exactly what I was running that was incorrect. I set up the system with a apt-get install xen-system-amd64 with a source file pointing at jessie. Therefore all the xen packages came via this route. What do I need to change to get 64 bit userspace? I would like to run 64/64/64. The documentation on line is a bit thin. Cheers On 24/11/14 17:41, Ian

Control: forcemerge 503287 737613 (making $subjet a bit more helpful this time too) On Mon, Nov 24, 2014 at 05:28:59PM +0000, Ian Campbell wrote: > Before investigating any further can either of you confirm whether > this still happens with the version of Xen currently in Jessie, which > is 4.4.1-3 (and the current kernel too). That was a major version > bump, so it is worth

Processing commands for control at bugs.debian.org: > retitle 773561 /etc/init.d/xen fails when run in a nested L1 hypervisor dom0 (Xen on Xen) Bug #773561 [xen-utils-common] /etc/init.d/xen fails when run in a guest, causing postinst to fail. Changed Bug title to '/etc/init.d/xen fails when run in a nested L1 hypervisor dom0 (Xen on Xen)' from '/etc/init.d/xen fails when run in a

Package: xen-hypervisor-4.3-amd64 Version: 4.3.0-3+b1 Severity: normal Dear Maintainer, After booting into kernel 3.13 dom0, the keyboard no longer works. All other aspects work, ssh is needed to login to the system to start working with the domU's. They keyboard works at the grub menu just fine, and works normal when booting into the non xen kernel. -- System Information: Debian Release:

Package: xen-hypervisor-4.4-amd64 Version: 4.4.1-9 Severity: critical Justification: breaks the whole system Dear Maintainer, After upgrading the R610 server from Debian 7 to Debian 8, the dom0 becomes unresponsive via ssh after an hour or so, although the domUs still remain accessible. Initially we thought it may be a disk space issue on / or /boot so action was taken to increase those

On Sun, Apr 26, 2015 at 10:50:16AM +0200, Daniel Pocock wrote: > On 26/04/15 10:45, Bastian Blank wrote: > > Well, if you can pursuade the release team. We have grub2 for Xen > > in Jessie now and it can be used on Wheezy as well. > Can you be more specific? If somebody is running a wheezy dom0 and > they install grub2 in their domU before rebooting it the first time, >

Hi Daniel On Sun, Apr 26, 2015 at 10:35:01AM +0200, Daniel Pocock wrote: > This should probably be released in an update to wheezy. Well, if you can pursuade the release team. We have grub2 for Xen in Jessie now and it can be used on Wheezy as well. Bastian -- Beam me up, Scotty, there's no intelligent life down here! -------------- next part -------------- A non-text attachment was

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 26/04/15 10:45, Bastian Blank wrote: > Hi Daniel > > On Sun, Apr 26, 2015 at 10:35:01AM +0200, Daniel Pocock wrote: >> This should probably be released in an update to wheezy. > > Well, if you can pursuade the release team. We have grub2 for Xen > in Jessie now and it can be used on Wheezy as well. > Can you be

Package: xen-utils-common Version: 4.3.0-3 Severity: normal Dear Maintainer, * What led up to the situation? I upgraded my server from squeeze to wheezy and then to jessie. Server is Intel S3200SHV m/b with Intel(R) Core(TM)2 Quad CPU. I'm pretty sure that before that it was running whatever came before squeeze, I forget the name. I was trying to get xen_pciback to work, so I

Processing commands for control at bugs.debian.org: > reassign 737613 src:xen 4.3.0-3 Bug #737613 [xen-hypervisor-4.3-amd64] xen-hypervisor-4.3-amd: Xen not loading dom0 on Jessie - FATAL error on running /etc/init.d/xen Warning: Unknown package 'xen-hypervisor-4.3-amd64' Bug reassigned from package 'xen-hypervisor-4.3-amd64' to 'src:xen'. No longer marked as found in

Dear XEN-Team I've set up a complete new VM, tested copying and backuping with following error again: [ 1920.052129] INFO: task jbd2/xvda2-8:98 blocked for more than 120 seconds. [ 1920.052143] Not tainted 3.16.0-4-amd64 #1 [ 1920.052147] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 1920.052153] jbd2/xvda2-8 D ffff880004986e78 0 98

Package: xen-utils-4.1 Version: 4.1.4-3+deb7u4 Severity: serious Tags: patch dom0 running wheezy domU upgraded from wheezy to jessie. The domU doesn't boot any more, errors: Error code: Using <class 'grub.GrubConf.Grub2ConfigFile'> to parse /grub/grub.cfg Error parameters: Traceback (most recent call last):, File "/usr/lib/xcp/lib/pygrub.xcp", line 853, in

Package: xen-utils-common Version: 3.4.2-1 Severity: important File: /etc/init.d/xend Tags: patch Hello, /etc/init.d/xend assume xenfs is present and doesn't start xend if not. This dirty patch makes xend start and XEN being operationnal with old flavour xen kernels. I use 2.6.31.5 with forwarded ported Xen 2.6.18 dom0 kernel patch but it should work with debian's 2.6.26 ---

Package: xen-hypervisor-amd64 Version: 4.4.1-3 On a 32 bits computer with debian jessie 3.16.0-4-686-pae, "apt-get install xen-hypervisor" fetch the xen-hypervisor-amd64 package. When I try to boot on the Xen kernel : ERR: Not a 64-bit CPU! Please let me know if you need more. Regards, Xavier Chotard -------------- next part -------------- An HTML attachment was scrubbed... URL:

Package: xen-hypervisor-3.0.3-1-i386 Version: 3.0.3-0-1 Severity: normal -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, When you have a HVM domain running, if you try to boot a regular paravirtualized domain, dom0 (or maybe the hypervisor) crashes immediately (reboot). The opposite (trying to boot a HVM domain while a regular paravirtualized domain is running) crashes the system as well. I

> This bug was already reported as #763102 and was brushed off because maintainer > says it implicates xend which is not there in 4.4 anymore. Quoting the explanation sent when closing #763102: If you think a bug has been associated with xend in error please check if it still reproduces with the packages in Jessie (currently 4.4.1-3) and reopen. I'm sorry you felt this was

Package: xen-utils-common Version: 3.0.3-0-2 Severity: minor Here's an excerpt from /etc/init.d/xend: *) N=/etc/init.d/xen-utils echo "Usage: $N {start|stop|restart|force-reload}" >&2 exit 1 ;; This will obviously display a wrong path when the script is called with unknown arguments. Regards, -- J?r?my -------------- next part

Dear Debian-Bugteam Unfortunately this problem still exists. I want to use the server in production environment, but can't by reason of this error. Installed XEN-Versions: ii xen-hypervisor-4.4-amd64 4.4.1-9+deb8u5 amd64 Xen Hypervisor on AMD64 ii xen-linux-system-3.16.0-4-amd64 3.16.7-ckt25-2 amd64

Package: xen-hypervisor-3.2-1-amd64 Version: 3.2.0-5 Severity: important The hypervisor loads OK but then fails to load my dom0 kernel. I get an erorr message "not an ELF binary" followed after 5s by a hypervisor reboot. /boot/grub/grub.cfg contains: menuentry "Debian GNU/Linux, Xen 3.2-1-amd64, Linux 2.6.22-3-vserver-amd64 (single-user mode)" { set root=(hd0,1)