search for: dater

...> x86_64 GNU/Linux > > domU "working" "uname -a": > Linux working 3.16.0-4-amd64 #1 SMP Debian 3.16.7-ckt20-1+deb8u2 > (2016-01-02) x86_64 GNU/Linux > > So same version? What was the earlier version of the hypervisor? > I forgot to mention that I use apt-dater to upgrade both dom0 and domUs at the same time. domU "bug" was created for debugging purposes just a couple of hours after I used apt-dater and realized that there's something wrong with the pci passthrough. domU "bug" and domU "working" should have relatively sim...

I have read a couple old threads here on updates for servers, and I am looking for some mechanics to getting the actual updates done. I don't want automatic updates; I want to control when and what gets updated. First I have to determine that a particular server needs updates. I suppose a daily script that would run "yum check-updates' and emails me the results could work, but

How can I install a lot (more than 800) of APT packages using an easy way in puppet? I mean, using some file.txt where I put there the packages I want to install and my package resource get the list . Is it possible? Or do I have to put all packages in the package resource? regards, Israel. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed

Hello, I have an odd problem on a dual processor, dual core Opteron system. Obviosously it is x86_64 so should have no problem with large amounts of RAM. The system has 4 GB installed (2GB on each processor). If I boot the system with a fresh install of Debian Etch it sees all the memory fine. dmesg reports: Memory: 4107008k/5242880k available (1929k kernel code, 86836k reserved, 864k data, 176k

...0007fffe040 (XEN) ACPI: HPET (v001 A M I OEMHPET0 0x12000614 MSFT 0x00000097) @ 0x000000007fff54d0 (XEN) ACPI: SRAT (v001 AMD HAMMER 0x00000001 AMD 0x00000001) @ 0x000000007fff5510 (XEN) ACPI: SSDT (v001 A M I POWERNOW 0x00000001 AMD 0x00000001) @ 0x000000007fff5600 (XEN) ACPI: DSDT (v001 DATER DATER111 0x00000111 INTL 0x20051117) @ 0x0000000000000000 (XEN) (XEN) **************************************** (XEN) Panic on CPU 0: (XEN) Early fatal page fault at e010:ffff830000170890 (cr2=ffff83007fff04c4, ec=0000) (XEN) **************************************** (XEN) (XEN) Reboot in five second...