similar to: Fw: Re: Problems with load the most recent 2.6.29-rc6 & Xen unstable on ASUS P5K Premium

Hi All, I am not able to boot Xen . My "/boot/grub/menu.lst" has this entry title Xen 3.3.2-rc5 / Debian GNU/Linux, kernel 2.6.18.8-xen root (hd0,0) kernel /boot/xen-3.3.2-rc5.gz module /boot/vmlinuz-2.6.18.8-xen root=/dev/sda1 ro console=tty0 module /boot/initrd.img-2.6.18.8-xen savedefault I am getting following error : ERROR

Hi All, I am not able to boot Xen . My "/boot/grub/menu.lst" has this entry title Xen 3.3.2-rc5 / Debian GNU/Linux, kernel 2.6.18.8-xen root (hd0,0) kernel /boot/xen-3.3.2-rc5.gz module /boot/vmlinuz-2.6.18.8-xen root=/dev/sda1 ro console=tty0 module /boot/initrd.img-2.6.18.8-xen savedefault I am getting following error : ERROR

Hi All, I am not able to boot Xen . My "/boot/grub/menu.lst" has this entry title Xen 3.3.2-rc5 / Debian GNU/Linux, kernel 2.6.18.8-xen root (hd0,0) kernel /boot/xen-3.3.2-rc5.gz module /boot/vmlinuz-2.6.18.8-xen root=/dev/sda1 ro console=tty0 module /boot/initrd.img-2.6.18.8-xen savedefault I am getting following error : ERROR

Hello. log of the crashing boot process: http://pasik.reaktio.net/xen/pv_ops-dom0-debug/pv_ops-dom0-bootlog-14-xen331-linux-2.6.29-rc6-crash.txt 2.6.29-rc5 based pv_ops dom0 works on the same computer.. with the same Xen version. I tried with and without pci=nomsi. adding ''noapic'' doesn''t seem to help (I need that with 2.6.29-rc5 to make it work). Any ideas

Did a ''git pull'' a few minutes ago and tried to rebuild my kernel and was given this error: make CHK include/linux/version.h CHK include/linux/utsrelease.h SYMLINK include/asm -> include/asm-x86 CALL scripts/checksyscalls.sh CHK include/linux/compile.h CC drivers/acpi/acpica/hwsleep.o drivers/acpi/acpica/hwsleep.c: In function

I have 2 new boxes that I cannot use yet because of problems supporting these newer chipsets in 5.1. Does anyone know when the CD version of 5.0 x86-64 that has support for these chipsets be available on any on a Centos mirror? Has the support for these chipsets been added to yum yet? Here are my latest results with these chipsets and Centos 5.1 1. Asus P5K, E6850, P35 Chipset: Does not

=================================================================== "There can't be a crisis next week. My schedule is already full." Henry A. Kissinger ================================================================== Release Announcements ===================== This is the latest stable release of Samba 3.5. Major enhancements in Samba 3.5.9 include: o Sgid bit

=================================================================== "There can't be a crisis next week. My schedule is already full." Henry A. Kissinger ================================================================== Release Announcements ===================== This is the latest stable release of Samba 3.5. Major enhancements in Samba 3.5.9 include: o Sgid bit

Seems to work OK for native and Xen. I had to play a bit with the paravirt-sched-clock patch to deal with the VMI changes. Zach, can you check that it still works? Thanks, J

Seems to work OK for native and Xen. I had to play a bit with the paravirt-sched-clock patch to deal with the VMI changes. Zach, can you check that it still works? Thanks, J

Hi everyone, I am very excited to see that dom0 pvops is finally coming close to working, so I wanted to give it a try. >From the description it was not clear to me which kernel to chose as base for the patches.hg, so I took the latest (that was ~ 2 weeks ago) kernel on git.kernel.org I could find (post-2.6.28 git tip at that point). I managed to more or less apply all of the patches in the

Hello, I'm trying to complete a minimal install of Centos 5.1 x86_64 on a Core 2 Duo 2.2Ghz running on an Asus P5K-VM motherboard - yes, this means it's the G33 chipset. (you can stop laughing now) I'm installing to two SATA-disks setup with Software Raid-1. I've installed an Intel NIC that is detected during install and I'm able to complete the install itself - mind you I

Hello list I have a shutdown problem. I have a machine with gigabyte GA-G33M-DS2R motherboard. Integrated network card is Realtek 8111B. I can not wake the computer after I shutdown it from FreeBSD. It is a dualboot system - windows xp and freebsd. If I shutdown the computer from windows - later I can wake it up with magic packet. Even if i shutdown the machine on the boot menu with the power

My system is: Intel CC820 motherboard (which supports PME# wake up for wake on LAN) 3com 3C905C which also supports wake on LAN via PME# Linux 5.5 The motherboard BIOS is later than one that reports an issue with WOL and this particular network card was fixed. But when I turn off the PC (shutdown or poweroff commands or front panel button), it cannot be restarted via WOL. The network light on

Some switch hardware can generate the packets directly, negating the need for a box on every VLAN. Meraki hardware can do it, but you have to go through the dashboard so automating it isn't currently possible. Here is some documentation on forwarding WoL on catalyst 3750 switches from Cisco:

Has anyone experience with WOL under Centos (5.3).? If so, how exactly do you put the machine to sleep, and how exactly do you wake it up remotely? -- Timothy Murphy e-mail: gayleard /at/ eircom.net tel: +353-86-2336090, +353-1-2842366 s-mail: School of Mathematics, Trinity College Dublin

On Sun, 2020-05-17 at 20:25 -0600, R C wrote: > Ok, I get that, found it before; "typically sent as a UDP datagram to > port 0, 7 or 9, or directly over Ethernet as EtherType 0x0842" > > > The keyword being 'typically', but what is it that ether-wake actually > uses/does? (I need to forward a WOL packet to a different > > vlan on some Cisco

Many thanks to those that responded to my original posting with information about Network UPS Tools and commercial UPS products. In our planning a path forward to implement UPS-based power fail protection, we have come across what appears to be an issue with the state of the CentOS 6 machines being UPS protected.? Most of these machines are desktop/deskside machines that are likely to be idle

Now that x86-64 has directly accessible percpu variables, it can also implement the direct versions of these operations, which operate on a vcpu_info structure directly embedded in the percpu area. In fact, the 64-bit versions are more or less identical, and so can be shared. The only two differences are: 1. xen_restore_fl_direct takes its argument in eax on 32-bit, and rdi on 64-bit.

The WoL magic packet is only scanned for the string above, and not actually parsed by a full protocol stack, it could be sent as any network- and transport-layer protocol, although it is typically sent as a UDP <https://en.m.wikipedia.org/wiki/User_Datagram_Protocol> datagram <https://en.m.wikipedia.org/wiki/Datagram> to port <https://en.m.wikipedia.org/wiki/TCP_and_UDP_port> 0,]