similar to: Bug#385934: Fixed by using xen-hypervisor-3.0-unstable-1-i386

Package: xen-hypervisor-3.0-unstable-1-i386 Version: 3.0-unstable+hg11561-1 Severity: important I've installed xen-linux-system-2.6.17-2-xen-k7 (version 2.6.17-9) on a server, and planned to run 3 Xen domUs on it. Creating the domUs was no problem, and running two of them works well. Starting the third one however will crash the dom0 and forces it to reboot. The machine is a Athlon64 3800+

Package: xen-hypervisor-3.0.2-1-i386 Version: 3.0.2-3+hg9762-1 Followup-For: Bug #385934 Hello! For me, the new upload of xen-hypervisor-3.0.2-1-i386, version 3.0.2-3+hg9762-1, does _not_ fix this issue. I'm still seeing the same problem as it was originally reported in this very bug report. -- System Information: Debian Release: testing/unstable APT prefers testing APT policy: (900,

Package: xen-hypervisor-3.0-i386 Version: 3.0.2+hg9697-2 Severity: grave Justification: renders package unusable Hypervisor reboots system after printing: (XEN) Xen trace buffers: disabled >From what I've found online, Xen should start booting the linux kernel at this point, but never does so. I've booted the hypervisor with the options 'noreboot' and 'sync_console' -

Package: xen-hypervisor-3.0-unstable-1-amd64 Version: 3.0-unstable+hg11292-2 Severity: important My server is a dell 2950 server. Before the dom0 rebooting bug ocurred, xen was well even for hvm domU. By now i have tried xen-hypervisor-3.0-amd64 (3.0.2+hg9697-2) and xen-hypervisor-3.0-unstable-1-amd64 (3.0-unstable+hg11292-2), but both of them are unusable for me. for

I am using Xen 4.6.0-8.el7 on CentOS 7 with 3 Linux DomUs. I did have Xen 4.? on CentOS 6.5 on my previous system. I installed using yum install centos-release-xen. On shutting down the Hypervisor it used to wait for the DomUs to shut down gracefully (one can take a minute or more), then on starting up again it would restart the DomUs, all nice and controlled. For some reason the DomUs (CentOS

So, let's get started! One of the first changes we might want to do is move away /etc/sysconfig/xendomains... We should put it either in /etc/default/xendomains (since it's an init script configuration) or /etc/xen/xendomains (since it's xen related)... Which one do you prefer? As for the way to do it I propose a dpatch file that changes the two files in the upstream tarball that

after upgrading to 3.0.2+hg9697-2 I experience the same problem! I switched to xen-hypervisor-3.0-amd64, but it shows the same effect! AMD Athlon64 3800+ machine - was running fine with 3.0.2+hg9697-1 until last saturday... MfG Sebastian Rieger

Author: ultrotter Date: 2006-03-21 16:54:07 +0000 (Tue, 21 Mar 2006) New Revision: 127 Modified: trunk/xen-3.0/debian/xen-utils-3.0.postrm Log: Stop xend & xendomains on remove, and call update-rc.d on purge... Modified: trunk/xen-3.0/debian/xen-utils-3.0.postrm =================================================================== --- trunk/xen-3.0/debian/xen-utils-3.0.postrm 2006-03-21

Package: xen-hypervisor-3.0.2-1-i386 Version: 3.0.2-3+hg9762-1 Severity: grave Justification: renders package unusable When booting Xen Dom0 on my Dell 2950, the kernel panics. I have been unable to get the serial console working under xen (works under normal kernels), so the best debugging info I can provide is a screenshot of the console when it dies. I will attach that after the bug is

Hello, in the last days I switched from Xen 4.2.1 to Xen 4.2.2 (source from git repository tag 4.2.2) commit a125ec6a4a2f028f97f0bdd8946d347a36dbe76b Author: Jan Beulich <jbeulich@suse.com> Date: Tue Apr 23 18:42:55 2013 +0200 update Xen version to 4.2.2 My "base system" is a debian squeeze. For Xen I use the xl toolstack. Since updating to 4.2.2 the autosave and

On Wed, 2015-02-18 at 14:53 +0100, Stefan Bader wrote: > So given that for above reasons moving between xen versions installed in > parallel is not as straight forward as one would hope and maintaining the > patches to get the versioned packages is some effort, what are/were the reasons > to do this? Might be a dumb question but I guess I have to ask anyway. Apart from parallel

Hello, Im reading Data out of a Database. #v+ rs <- dbGetQuery(con,"SELECT * ... ) attach(rs) #v- There ist a colum I convert into "Time". #v+ > zeit<-strptime(datum,format="%Y-%m-%d %H:%M:%S"); > class(zeit) [1] "POSIXt" "POSIXlt" #v- 1. A plot(zeit,money) plots the Data. All i see on the x-achis are the Days. I would like to see the

Hallo, Following the tips found at https://calomel.org/nut_ups.html I was trying to make NUT operate "APC Back UPS CS-350". The device introduces itself as: #v+ ugen0 at uhub0 port 1 "American Power Conversion Back-UPS CS 350 FW:807.q7.I USB FW:q7" rev 1.10/0.06 addr 2 #v- My config: #v+ [apc] driver = usbhid-ups port = /dev/ugen0.00 pollfreq =

Hallo, Following the tips found at https://calomel.org/nut_ups.html I was trying to make NUT operate "APC Back UPS CS-350". The device introduces itself as: #v+ ugen0 at uhub0 port 1 "American Power Conversion Back-UPS CS 350 FW:807.q7.I USB FW:q7" rev 1.10/0.06 addr 2 #v- My config: #v+ [apc] driver = usbhid-ups port = /dev/ugen0.00 pollfreq =

Hi, Ever since xl become the preferred toolstack, I have had problems using the xendomains startup/shutdown script. Having retested today, it seems that the issues are now reduced down to xendomains being unable to restart previously saved domains. Here is a typical session using xl running Xen 4.2.2 on Ubuntu 64 12.04 bit server, using stock Dom0 kernel (3.2.0-43-generic)

I''ve migrated my Dom0 host to Xen 4.2.0 + xl toolstack. With ''xm'' toolstack, configs in /etc/xen/auto are autostarted, assuming xend/xendomains services are started. IIUC, when using xl toolstack, those services are not to be started; and, afaict, the installation process for 4.2 has them disabled by default. Now, the configs in /etc/xen/auto are simply ignored. I

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

Hello all I''ve just installed xen 4.1.1 on my server and was tryoing to tweak xendomains script to work with new xl schema but I can´t get it to save domains. It does start them with some changes I made to it but when I issue service xendomains stop I just get [ OK ] but domains stay running. Has xendomains script been ported to work with 4.1.1 or is there another alternative to it.

Hey, I thought there was supposed to be an ability for domU''s to be put into a hibernated state (E.g. current running tasks and memory) when dom0 is shutdown or rebooted. When I look in my /etc/default/xendomains file, I have the variable''s "XENDOMAINS_SAVE=/var/lib/xen/save" and "XENDOMAINS_RESTORE=true". However, when I reboot, I always have to restart my

I''m running xen 3.1.2 as bastardized by RedHat on a redhat clone operating system. I''m using the xendomains script as it came out of the box to start my domU''s at boot and stop them at shutdown. There are three problems right now: 1) left to its own devices, service xendomains stop attempts to do "xm save" on each of the domU''s. that takes quite a