similar to: Bug#476826: xen-hypervisor-3.2-1-i386: grub not updated correctly when installing xen

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-hypervisor-3.0.2-1-i386 Version: 3.0.2-3+hg9762-1 Severity: wishlist Hello! Shouldn't `update-grub' be run automatically after installing a `xen-hypervisor-*' package? -- System Information: Debian Release: testing/unstable APT prefers testing APT policy: (900, 'testing'), (800, 'unstable') Architecture: i386 (i686) Shell: /bin/sh linked to

On 01/30/2018 04:23 PM, John Naggets wrote: > Hi, > > I installed CentOS 7.4 on a modern Lenovo ThinkSystem SR630 server > which uses UEFI. So far so good CentOS 7.4 works fine so then I went > on to install the Xen hypervisor by following the instructions from > the wiki (https://wiki.centos.org/HowTos/Xen/Xen4QuickStart). > > Unfortunately when I reboot after having

Once upon a time, John Naggets <hostingnuggets at gmail.com> said: > Jonathan brings it exactly to the point: we have to face UEFI because > legacy mode is fading out, if I enable legacy mode I can't even boot > anymore through the network (PXE) as these newer network cards can > only boot PXE with UEFI. UEFI PXE is different than BIOS PXE and needs to download different

Why do you need UEFI? It does not add to security "a lot" but was designed to block booting software like a "hypervisor". I used my Dell notebooks to test our hypervisor identification software (HyperCatcher if you are interested) which is bootable image. However, I was unable to boot it until I disabled UEFI. As I understand it, it will block anything from booting excepting

I checked and secure boot is turned off. Jonathan brings it exactly to the point: we have to face UEFI because legacy mode is fading out, if I enable legacy mode I can't even boot anymore through the network (PXE) as these newer network cards can only boot PXE with UEFI. In the mean time I have installed Ubuntu 17.10 with Xen and I was lucky to see that this combination works with UEFI even

Hi, I installed CentOS 7.4 on a modern Lenovo ThinkSystem SR630 server which uses UEFI. So far so good CentOS 7.4 works fine so then I went on to install the Xen hypervisor by following the instructions from the wiki (https://wiki.centos.org/HowTos/Xen/Xen4QuickStart). Unfortunately when I reboot after having installed the xen package the system does not boot into "CentOS Linux, with Xen

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-i386 Version: 3.2-1 Severity: critical Tags: security Justification: DoS of entire system regardless of privilege When running the exploit listed in bug 464953 [1], Xen's memory state becomes corrupted and the hypervisor eventually crashes, taking all of the domU's with it. As such, this breaks operational behaviour, so I have marked this as critical. [1]

Hi List, I backported the latest hypervisor and utils for etch on x86_64. However, I'm having some problems starting the xend daemon which is packaged in the xen-utils-common package. I'm trying to run this against a dom0 kernel which I downloaded from :-

Your message dated Fri, 06 Sep 2013 09:09:48 +0100 with message-id <1378454988.3057.2.camel at dagon.hellion.org.uk> and subject line Re: [Pkg-xen-devel] Bug#710522: Problem found has caused the Debian Bug report #710522, regarding xen-hypervisor-4.1-amd64: Boot hang with Linux 3.2+Xen, works with linux 2.6.32+Xen or 3.2 raw to be marked as done. This means that you claim that the problem

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)

tag 502123 patch severity 502123 serious thanks Confirmed. This regression was introduced by a copy-and-paste error in debian/patches/tools-python-xen-xm-relative-path.diff (svn://svn.debian.org/pkg-xen -r531). Please apply this fix. --- debian/changelog 2008-12-04 16:50:04.000000000 -0500 +++ debian/changelog 2008-12-04 16:59:09.000000000 -0500 @@ -1,3 +1,10 @@ +xen-unstable

retitle 502123 xen-utils-unstable: Debian patch breaks paravirtualized guest initrd thanks I see that this bug is still present in pkg-xen svn: http://svn.debian.org/wsvn/pkg-xen/trunk/xen-unstable/debian/patches/tools-python-xen-xm-relative-path.diff?op=file Perhaps I wasn?t clear how severe this problem is. Using the current Debianized xen-utils-unstable, it is impossible to boot any

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-i386 Version: 3.2.1-2 Severity: important Hello, 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 at boot. The Exact error message is: A clock interrupt was not received on a secondary processor within the allocated time interval. STOP: 0x00000101

Hi list, i''m running xen 3.2 on an ubuntu hardy 8.04 server installed from repo. My domU are hardy servers too Sometime happens that if a domU crashes i''ve to reboot the entire dom0. Of course it''s quite annoying and seems to frustrate the virtualization concept at all ... My machine isn''t vt-d enabled. (2x XEON 3.0GHz) Is it possible to run PV-Grub?

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-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

let''s try this with a shorter subject, which was originally this, which probably tripped the list-admin-approval triggers.... Xen 3.2 Debian 2.6.18 on Dual Xeon with Remote Serial access - grub.conf config advice needed the subject says it all - anyone who knows the answer can stop reading and hit "send" with a few lines of grub.conf - however, for those people who are bored,