similar to: Bug#657014: please can you try the latest kernel and hypervisor from Wheezy

There's a couple of patches in 4.1 which might plausibly be the fix for this. changeset: 23246:8f927378135a user: Jan Beulich <jbeulich at suse.com> date: Wed Mar 07 08:35:58 2012 +0000 files: xen/arch/ia64/xen/domain.c xen/arch/x86/domain.c xen/arch/x86/domctl.c description: passthrough: release assigned PCI devices

On 18 February 2013 16:32, Ian Campbell <ijc at hellion.org.uk> wrote: > On Mon, 2013-02-18 at 13:51 +0000, Gavin wrote: > > > <stumped! /> > > If the kernel hasn't changed and you are 100% sure the network > configuration before and after the reboot is the same then so am I. > > All I can suggest is to reinstall the previous version of Xen. > Thanks

Hi Juergen, I've had a trawl through the SuSE update but it's not clear which patch might impact this issue. However SuSE are usually very good about upstreaming their fixes so I think there is a very good chance this will be fixed in the 4.1 packages in Wheezy. Are you able to give it a try? Thanks, Ian.

Package: src:xen Severity: important Version: 4.1.3~rc1+hg-20120614.a9c0a89c08f2-2 I recently upgrade from Squeeze to Wheezy on a system which had the xen-linux-system-686-pae metapackage (one of two which Provides: xen-linux-system). After dist-upgrade I had the new xen-utils-common and xenstore-utils (and a few others) but not the xen-utils-4.1 or xen-hypervisor-4.1-i386 or xen-hypervisor-amd64

Package: xen-hypervisor-4.1-amd64 Version: 4.1.2-2 When installing xen-linux-system on a new Dell R810 server, Wheezy, Squeeze and Ubuntu server 11.10 all boot fine when booted directly into the standard kernel, but when booting through Xen (after installing the package xen-linux-system) the boot process hangs as soon as Xen passes control to the Dom0 kernel: "Gave up waiting for root

I'm afraid I don't know what may or may not have happened to your installation, just that this fake-start-stop-daemon thing is very likely interfering with the operation of Xen by not actually starting daemons. I suggest you try asking somewhere like the debian-users list to see if anyone there knows what this thing is or what to do about it. Ian. On Tue, 2015-06-02 at 15:22 +0200,

Control: tag -1 +moreinfo Hi Marco, Thanks for your report. Unfortunately the logs you've provided are from a system booted without Xen, and due to the nature of the bug it is unlikely that any relevant logs made it onto the disk in order to survive the resulting reboot. Please could you try setting up a serial console and collect the full boot log.

Ian Campbell <ijc at hellion.org.uk> writes: #Was that with the Jessie or Wheezy dom0 kernel? Actually tried both kernels. 3.13 on Jessie and 3.2 on Wheezy. The keyboard failed on any xen 4.3 boot. If it was nonxen, or xen 4.1 on any kernel the keyboard worked normal. Thanks for your help troubleshooting. Cheers, Mike -------------- next part -------------- An HTML attachment was

Package: xen-hypervisor-4.1-amd64 Version: 4.1.1-3 Severity: important Whenever I try to start a domU, xm create failed for 'Boot loader didn't return any data!'. % sudo xm create -c squeeze.cfg Using config file "/etc/xen/squeeze.cfg". Error: Boot loader didn't return any data! It seems related to the following error in dmesg [1440.163935] pygrub[3654] trap invalid

Hi, Thanks for your answer. During the Debian jessie installation, I had a problem at grub step. The os-prober part was stuck : grub was at 66 % (os-prober tried to browse all the VM on LVM partitions) After more than 15 minutes, os-prober seems to be stuck, so I rebooted the server. I had to boot in rescue mode, then, reinstalled grub and modified it to add

Hi, Firstly I apologise for the cross-post, however I don't expect to get as quick a response from the package maintainers as I do from the Debian community, and this issue affects a service that I've got scheduled to go live at midnight this evening. :( A recent update from xen-hypervisor-4.1-amd64 version 4.1.3-7, to version 4.1.3-8 on Debian Wheezy has caused all vm's on this host

Hi, Firstly I apologise for the cross-post, however I don't expect to get as quick a response from the package maintainers as I do from the Debian community, and this issue affects a service that I've got scheduled to go live at midnight this evening. :( A recent update from xen-hypervisor-4.1-amd64 version 4.1.3-7, to version 4.1.3-8 on Debian Wheezy has caused all vm's on this host

On Feb 18, 2015, at 7:56 PM, Gene Heskett <gheskett at wdtv.com> wrote: > Even though I installed nut-doc, there are no man pages so I am running in > the dark again. They seem to be in the file list: https://packages.debian.org/wheezy/amd64/nut-client/filelist Is $MANPATH set to something strange? > > Where is the initial config and startup procedure to be found? ISTR it

Package: xen-hypervisor-4.1-amd64 Version: 4.1.4-3+deb7u1 Severity: important Dear Maintainer, We are having a problem on several Supermicro servers (I'll include more details on the configuration later) : when booting Linux 3.2 linux-image-3.2.0-4-amd64 (Wheezy) as a DOM0 on Xen 4.1 (xen-hypervisor-4.1-amd64 from Wheezy), the system hangs after : [ 3.716174] scsi1 : ata_piix [

On Thu, 2014-05-15 at 12:44 -0700, Mike Egglestone wrote: > FWIW, > I also tried a fresh wheezy install. > Dist-upgraded to Jessie, and installed the xen-hypervisor package. > Then rebooted into the XEN 3.2 kernel that comes with wheezy. > Keyboard still doesn't work. Was that with the Jessie or Wheezy dom0 kernel? Ian.

Hi, "Ian Campbell" <ijc at hellion.org.uk> ?rta 2013-10-22 11:17-kor: > On Tue, 2013-10-22 at 11:52 +0200, PASZTOR Gyorgy wrote: > > When you use xl toolstack, you can't reboot domUs. > > When you switch back to xm toolstack, than reboot works again. > > I think the problem with the debian packaged version is the same as in > > this thread: > >

Hi, First of all, thanks for your help. I have made some test with this results debian testing with xen 4.4 can run if we add mmcfg=0 as boot options to kernel boot parameters !!! Remember that with xen kernel <=4.0 works perfect without to add mmcfg=0 I have tried to install citrix xenserver 5.6 and works perfect (remember that this is xen 3 branch) Also we have tried to install xenserver

On 14/05/16 19:35, Adam D. Barratt wrote: > Control: tags -1 + moreinfo > > On Sat, 2016-05-14 at 19:10 +0200, Daniel Pocock wrote: >> If somebody is still running wheezy for their dom0 (host) environment >> and they are using jessie or other systems with grub2 in their VMs, they >> can't boot their VM. >> >> A rather trivial 1-line fix in the dom0

Dropping users and adding pkg-xen-devel and debian-kernel. On Tue, 2012-11-06 at 15:43 +0100, Stephan Seitz wrote: > On Mon, Nov 05, 2012 at 06:12:53PM -0200, Henrique de Moraes Holschuh wrote: > >I would like to bring to your attention the improved support for system > >processor (CPU) microcode updates, for x86/i686/x86-64/amd64 systems > >that was recently added to

Greetings Charles; I eventually gave up making it work on ubuntu-10.04.4 LTS, and that drive is slowly curling up its toes, so I am running wheezy on a fresher drive now. I have installed all the nut stuffs from the repo, and now have two more scripts in /etc/init.d called nut-client and nut-server. dmesg |grep Belkin - : root at coyote:/etc/nut# dmesg|grep Belkin [ 4.242066] usb 2-3: