similar to: Bug#535150: xen-hypervisor-3.2-1-i386: xen hvm Windows Bluescreen

Package: xen-hypervisor-3.2-1-amd64 Version: 3.2.1-2 Severity: important Tags: patch Hi, I'm having troubles with windows 2008 server with HVM on XEN. When I allocate more than one CPU to the Windows VM, windows crashes after a few minutes with a BSOD. Other people have this problem, too. The Exact error message (BSOD) is: (the unique lines) A clock interrupt was not received on a

Package: xen-hypervisor-3.2-1-amd64 Version: 3.2.1-2 Severity: important I've a Debian Lenny AMD64 as production server, where it has important HVMs that runs correctly. The problem occurs when i try to create a HVM from a Debian Squeeze AMD64 iso file. At first, the VNC display specified shows perfectly the Debian Installer menu, but when I choose an option (Install or Graphical Install),

Package: xen-hypervisor-3.2-1-amd64 Version: 3.2.1-2 Severity: normal *** Please type your report below this line *** Hi, Recently I've experienced some crashes of Xen domU (also debian Lenny, running same kernel as dom0 (linux-image-2.6.26-xen-amd64)). At xm top that domain appears as running, but hogs all CPUs, because this problem has appeared on two identic servers (Supermicro X7SBi,

Package: xen-hypervisor-3.2-1-i386 Version: 3.2.1-2 Severity: important When starting a domU, or bringing up a network connection in a domU, this crash sometimes happens: (XEN) domain_crash_sync called from entry.S (ff188600) (XEN) Domain 0 (vcpu#0) crashed on cpu#0: (XEN) ----[ Xen-3.2-1 x86_32p debug=n Not tainted ]---- (XEN) CPU: 0 (XEN) EIP: 0061:[<c01013a7>] (XEN) EFLAGS:

Package: xen-hypervisor-3.2-1-amd64 Version: 3.2.1-2 Severity: normal Hi, Is the e1000 network card within domU no longer available? With model=e1000 a Xen domain refuses to start while with etch this was possible. There are some Windows guests on which I can not install gplpv, so with lenny they will just get 100mbit ethernet emulated. Cheers, Andreas -- System Information: Debian Release:

Package: xen-hypervisor-3.2-1-amd64 Version: 3.2.1-2 Severity: normal I have a dual-core host. I wanted to give one of my guests use of 2 vcpus and use of both real cpus. I had the following in my config file for the guest: vcpus = 2 cpus = 0,1 This appeared to work correctly and I saw a big difference in the load average (the guest is monitored by munin-node). However after 12 hours or so,

Package: xen-hypervisor-3.2-1-i386 Version: 3.2.1-2 Followup-For: Bug #566012 Just had another crash. I got the output from a serial console. The kernel doesn't say anything though. (XEN) traps.c:1996:d6 Domain attempted WRMSR 00000400 from 00000000:0000ffff to ffffffff:ffffffff. (XEN) traps.c:1996:d6 Domain attempted WRMSR 00000404 from 00000000:00018000 to ffffffff:ffffffff. (XEN)

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 [

Package: xen-utils-3.2-1 Version: 3.2.1-2 Severity: important Hi, I set the severity to important as it seems that current xen tools does not allow to load amd64 Debian kernel in DomU. I also put the debian-kernel ML in CC as I'm not sure the problem comes from xen tools or the kernel itself. Here is my configuration: Hypervisor: xen-hypervisor-3.2-1-amd64 3.2.1-2

Package: xen-hypervisor-3.2-1-amd64 Version: 3.2.1-2 Severity: grave Current xen hypervisor don't support Intel Core 2 Duo T9400 processor. Processor supports Intel (R) Virtualization Technology. -- System Information: Debian Release: 5.0 APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 2.6.28.1 (SMP w/2 CPU cores; PREEMPT) Locale:

Package: xen-hypervisor-4.0-amd64 Version: 4.0.1-2 Severity: important I upgraded today from Lenny to Squeeze. I upgraded via apt-get dist-upgrade and then installed the new xen-packages (including hypervisor and kernel). But I wasn't able to boot the system after the upgrade anymore with Xen enabled: On every boot-attempt, I just get "elf_init: not an ELF binary". I googled a

Hi! Thanks for your report, we'll look into it. Aki On 21.09.2017 14:47, Apollon Oikonomopoulos wrote: > Control: tags -1 + moreinfo upstream > > [Forwarding this to the Dovecot mailing list, just in case someone can help] > > Hi, > > Thanks for the report! See my comments inline. > > On 11:56 Thu 21 Sep , Thurgood Angelou wrote: >> Package:

Package: xen-utils-common Version: 3.2.0-2 Severity: normal When I was trying to migrate (xm migrate) a guest from one host to another, it simply fails. On the source host the virtual machine gets destroyed without any warning message - on the destination host I see the following error message in /var/log/xen/xend.log [2009-03-10 08:01:22 9846] ERROR (XendCheckpoint:52) read_exact: EOF trying

Package: xen-utils-3.2-1 Version: 3.2.1-2 Severity: normal Under this Xen setup, (Linux) HVM guests fail to have network active when running with *routed* networking, as some hosting providers require (in my case, OVH). In this scenario: * the host is a described below * the guest runs as HVM. * the guest runs exclusively with ioemu; virtual network drivers are not available (vanilla lenny

Package: xen-hypervisor-3.2-1-i386 Version: 3.2.1-2 Severity: minor Instead of running GRUB configuration directly, the package should use a trigger for that, to avoid doing it more than once when multiple hypervisor packages are installed (not speaking about other kernels). -- System Information: Debian Release: lenny/sid APT prefers testing APT policy: (990, 'testing'), (502,

Package: xen-utils-3.2-1 Version: 3.2.1-2 Severity: normal Tags: patch Hi, There is a bug xen-3-3.2.1/tools/libfsimage/reiserfs/fsys_reiserfs.c, it is using "unsigned long" which is 64 bits on amd64 arch and 32 bits on i386 arch. This makes pygrub can't work on reiserfs on amd64 arch. You can easily reproduce it. A patch is included for fixing this problem. diff

Package: xen-utils-3.2-1 Version: 3.2.1-2 Severity: important Intel processors have a bug with Vt that causes problems with Xen real-mode emulation. This renders FreeBSD (and possibly other OS'es) unbootable in Xen with HVM. Later versions of Xen 3.2 (and 3.3) emulate real-mode instructions so this problem doesn't exist. I would provide the relevant patches, but I do not have much

Control: tags -1 + moreinfo upstream [Forwarding this to the Dovecot mailing list, just in case someone can help] Hi, Thanks for the report! See my comments inline. On 11:56 Thu 21 Sep , Thurgood Angelou wrote: > Package: dovecot-core > Version: 1:2.2.32-2 > > I've just discovered a bug where the sieve plugin (especially IMAP) > will not work with a virtual mailbox. I

Package: xen-utils-3.2-1 Version: 3.2.1-2 Followup-For: Bug #477525 I have the same problem after updating from etch to lenny. (Thus updating Xen from 3.0 to 3.2) Does anyone know how to fix this? -- System Information: Debian Release: lenny/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 2.6.26-1-xen-amd64 (SMP w/2 CPU cores) Locale:

Package: xen-utils-3.2-1 Version: 3.2.1-2 Severity: normal In xend-config.sxp: (network-script 'network-camp netdev=eth0 bridge=xenbr0') /etc/xen/scripts/network-camp is the following simple script: --------------- begin script ----------- #!/bin/bash dir=$(dirname "$0") . "$dir/xen-script-common.sh" . "$dir/xen-network-common.sh" findCommand