Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I've got a bunch of Xen 3.4 DomUs that are currently running as HVM because of our infrastructure (Kickstart which doesn't handle Xen PVM yet). Both DomU and Dom0 are RHEL5 machines. If I understand the documentation and configuration correctly, it would suffice to install kernel-xen on the DomUs, replace hvm with pvm in the .xsp files and set the correct boot loader. But has anyone tried this, is this really this easy?

share|improve this question
+1 for asking here, I hope to see many of the common questions that hit the xen-users list show up here so the answers can be kept current and appear more prominently in search results. The xen wiki has never been able to accomplish the prior. – Tim Post Oct 26 '09 at 13:03

You'll probably want to be sure that you have the serial console configured correctly (note that it's hvc0 or xvc0 under paravirt instead of ttyS0).

Depending on the kernel version you may also run into issues with your block devices being force-renamed from hda or sda to xvda. (This happens with paravirt_ops-style kernels; usually 2.6.27 and later, or so).

share|improve this answer

Yep, that's pretty much how you do it. Nothing particularly exciting about it, I've done it a few times (Debian machines rather than RHEL, but there's no differences that should matter).

share|improve this answer

Don't forget to add hvc0/xvc0 to the /etc/securetty list, if you hope to console in as root.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.