Since some days I’m trying to install windows into a domU just for fun. All went fine until accessing discs. Sometime partition is not formatable, sometimes files could not read from cdrom. To be sure, it’s not the disc image, I used a fresh one from a MSDN Subscription, but it didn’t help.
Searching around on web, I found that I’m not the only one, with this issue. The common(s) seems to be etch (and AMD CPU).
I found traces of the issue at SP Team Blog, xen-users and xen-forum (german).
Maybe anybody can enlighten me?
Today the RIPE DNS for LIRs Training Course did take place. (some not up to date course material can be found here)
Managing some thousands of zones inclusive nameserver infrastructure behind since several years, I thought it would be neat to provide a secure dns chain to our costumers.
After going deeper into the material within the course, I recognized the following impacts:
- only bind9 (>= 9.3) and NSD privides support (yet)
- bandwidth will be increased 2-3 times with max. key size
- increased memory usage depending on your server software
- operational costs will increasing dramaticaly due significant higher amount of regular work
- more computing power (hardware) needed to generate dnssec ready zones and signing
- unknown influence on resolving nameservers (load/memory/bandwidth)
- chain of trust ends at resolving nameserver and is not provided to enduser
Since the last issue isn’t solved (yet), it doesn’t make any sence for me to invest resources into setting up DNSSec infrastructur, cause the end user would not recognize if the communication with the resolving nameserver or the resolving nameserver itself is taken over.
Any complaints and/or hint? Did I missed something?
Last weekend I got a hardware donation from muempf. It’s a new 1U server with the following specs:
Supermicro P8SCi Systemboard
Intel P4 3.00GHz
2x 512 MB DDR2 533MHz unbuffered ECC Systemmemory
2x 160 GB SATA disk (ST3160812AS)
2x GE Networkcard (BCM95721)
Console Redirection
I ordered additional 2x 1024 MB DDR2 533MHz modules and replaced an old server with this new system.
The system was installed on a Software Raid(1). The system migration was smooth, except problems getting the NICs up and running. They was recognized as eth2 and eth3 (10 MBit and no link). After hours searching around, I was guessing the problem is anywhere related to udev. Daniel told me to wipe ‘/etc/udev/rules.d/z25_persistent-net.rules’ nearly at the same time I saw, this was the only file with different size in ‘/etc/udev/’ compared to a working (etch) system on this hardware. Removing the file did the trick.
As the system is running now very well, sincere thanks are given to muempf!
