Xen users - Apr 2008 - I finally got Xen working on paravirtual as well

I found out that I couldn''t get the network device to bridge because I
was
selecting virtual network instead of bridge network on the xen setup screen. 
Anyhow, it works great.  I noticed that my xen fedora version and my regular
non xen fedora version run side by side.  For example, if I install
something or make a change on one version it makes that change on the other
version.  Is there any way to separate them?  Cause I want to install the
nvidia driver on the non xen one and leave it blacklisted in the xen one.
-- 
View this message in context:
http://www.nabble.com/I-finally-got-Xen-working-on-paravirtual-as-well-tp16600838p16600838.html
Sent from the Xen - User mailing list archive at Nabble.com.


_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

On Wednesday April 09 2008 10:24:59 pm trist007 wrote:
> I found out that I couldn''t get the network device to bridge
because I was
> selecting virtual network instead of bridge network on the xen setup
> screen. Anyhow, it works great.  I noticed that my xen fedora version and
> my regular non xen fedora version run side by side.  For example, if I
> install something or make a change on one version it makes that change on
> the other version.  Is there any way to separate them?  Cause I want to
> install the nvidia driver on the non xen one and leave it blacklisted in
> the xen one.
I handle that by having two xorg.conf''s that solely differ in 
the ''Driver "nv"'' or ''Driver
"nvidia"'' statement. On Fedora, I would put that
early in the boot sequence, probably in the udev scripts 
in /etc/sysconfig/modules. Name it so it ends in .modules, and it would look 
something like (untested):

if [ -f /proc/xen/capabilities ]; then
if `grep -q "control_d" /proc/xen/capabilities`; then
  cp /etc/X11/xorg.conf.nv /etc/X11/xorg.conf
  exit 0; fi; fi
cp /etc/X11/xorg.conf.nvidia /etc/xorg.conf

Then you just have to watch for system updates that might change xorg.conf, 
and change your other two .conf files to match, except for the video driver.

_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

Could be be more specific.  I just started using linux, could you give me a
step my step procedure.
-- 
View this message in context:
http://www.nabble.com/I-finally-got-Xen-working-on-paravirtual-as-well-tp16600838p16667243.html
Sent from the Xen - User mailing list archive at Nabble.com.


_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

On Sunday April 13 2008 03:49:55 pm trist007 wrote:
> Could you be more specific.  I just started using linux, could you give me
> a step my step procedure.
That was the step by step procedure :-)

cp -p /etc/X11/xorg.conf /etc/X11/xorg.conf.bak
if [ -f /proc/xen/capabilities ]; then
if `grep -q "control_d" /proc/xen/capabilities`; then
  cp -p /etc/X11/xorg.conf.nv /etc/X11/xorg.conf
  exit 0; fi; fi
cp -p /etc/X11/xorg.conf.nvidia /etc/xorg.conf

Put the above lines into a file called /etc/sysconfig/modules/video.modules. 
Change to your X11 config directory (cd /etc/X11). copy the xorg.conf file 
there to your two variant versions:

cp xorg.conf xorg.conf.nv
cp xorg.conf xorg.conf.nvidia

Go into an editor on each of the two new files, and look for the section that 
looks like:

Section "Device"
  BoardName    "GeForce4 MX 420"
  BusID        "1:0:0"
  Driver       "nvidia"
  Identifier   "Device[0]"
  VendorName   "NVidia"
EndSection

Yeah, my card is old :-) Your BoardName and BusID will more closely match your 
card. What you want to change is the Driver clause. The above is correct for 
the xorg.conf.nvidia file. For the xorg.conf.nv file, in the same section, 
just change ''Driver "nvidia"'' to ''Driver
"nv"'' and save the file. ''nv'' is the
nvidia dummy driver that ships with xorg that doesn''t do 3d
acceleration, but
works fine under xen.

Then the next time you reboot, the correct driver will be used whether you are 
in xen or non-xen kernel. The only caveat is some xorg updates you get 
from ''yum update'', etc. might change the current
/etc/X11/xorg.conf, and the
next time you reboot, you will overwrite those changes with the copies you do 
in the /etc/sysconfig/modules/video.modules file. You will have to be 
vigilant in watching your update logs/mails if you do updates automatically 
by enabling the ''yum-cron'' service. By default, Fedora only
advises you of
updates that are available, and expects you to manually initiate an update, 
in which case watch for xorg updates.

If you see that xorg.conf and xorg.conf.bak are different after an update 
(other than the trivial difference in the video Driver), then repeat the 
above procedure for creating your xorg.conf.{nv,nvidia} files. Just remember 
to use the newer of the two files xorg.conf and xorg.conf.bak to copy to 
xorg.conf.{nv,nvidia}. (The ''-p'' option to
''cp'' in the video.modules script
above preserves the time/date stamp, so if you have just gotten an update 
that changes xorg.conf, xorg.conf will have a newer time/date stamp than 
xorg.conf.bak. If you have already rebooted, xorg.conf.bak will probably be 
newer than xorg.conf. If you unfamiliar with getting time/date stamps from a 
directory listing, use eg - ''ls -alF /etc/X11''.)

Hope that was clearer.

_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

I tried that but during udev it says it can''t copy because
it''s only in a
read-only state.  I think the filesystem is remounted shortly after during
bootup to read and write.
-- 
View this message in context:
http://www.nabble.com/I-finally-got-Xen-working-on-paravirtual-as-well-tp16600838p16668617.html
Sent from the Xen - User mailing list archive at Nabble.com.


_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

On Sunday April 13 2008 05:47:56 pm trist007 wrote:
> I tried that but during udev it says it can''t copy because
it''s only in a
> read-only state.  I think the filesystem is remounted shortly after during
> bootup to read and write.
Ouch, right! I forgot about that. (I''ve only done this on SuSE, 
in /etc/init.d/boot.local, which doesn''t exist on Fedora.)

You *can* mount ''/'' rw in that script *if* you had a clean
shutdown previous
to that reboot. I''ve done it with ''/boot''. You could
try making the first
statement in /etc/sysconfig/modules/video.modules:

mount -vn -o remount,rw / || exit 1

If it fails because the volume is dirty, you exit, wait for fsck to do its 
thing repairing the volume, then reboot again. The -n is necessary when 
working with ro filesystems (see ''man mount''). The -v
(verbose) can be
removed once you are sure it is working. Then, to preserve what Fedora thinks 
should be a ro system in the next steps of the boot process, the rest of the 
script *could* be:

cp -p /etc/X11/xorg.conf /etc/X11/xorg.conf.bak
if [ -f /proc/xen/capabilities ]; then
if `grep -q "control_d" /proc/xen/capabilities`; then
  cp -p /etc/X11/xorg.conf.nv /etc/X11/xorg.conf
fi; else
  cp -p /etc/X11/xorg.conf.nvidia /etc/xorg.conf
fi
umount -n -o remount,ro /

Let me know if that works better for you.

_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users