Xen configuration file?

_______________________________________________
Xen-users mailing list
Xen-users <at> lists.xensource.com
http://lists.xensource.com/xen-users

Re: Getting fuse/coda devices working on Xen-based VM

On Tue, Jun 30, 2009 at 10:52 PM, Kelly
Jones<kelly.terry.jones <at> gmail.com> wrote:
> I sort of understand this: the VM doesn't have direct access to /dev devices?

Each domU has its own /dev that it has full access to.

>
> Can I fix myself by downloading and "insmod"'ing?

First you should look at your configuration. What kind of domU is it,
PV or HVM? Where is the kernel located, dom0 or domU? Do you have
access to the kernel's dev files (i.e. to build modules)?

A standard PV domU Xen installation on RHEL should have the kernel on
domU, booted with pygrub. In this case adding fuse support is simply a
matter of installing dkms-fuse (from dag repository).

If you use a hosted Xen environment where your provider uses kernel on
dom0 and disable module loading, there's not much you can do other
than to switch to a new provider.

--

-- 
Fajar

Re: Xen configuration file?

On Wed, Jul 1, 2009 at 8:00 AM, Travis Bell<travisbell <at> me.com> wrote:
> In most blog posts, and even Steven's PDF here (
> http://www.xen.org/files/Support/XenConfigurationDetails.pdf ) everyone
> references these config files, where do those get created in 3.4?
>
> I have a file here:
>
> /var/lib/xend/domains/a90f2411-6047-1589-ff79-da0c3046d607/config.sxp
>
> But it's syntax is WAY different than anything like in that PDF so I figured
> it is a different file.

http://books.google.com/books?id=XS-Jj7s2nhYC&pg=PA178&dq=running+xen+sxp+sample+configuration+file

Config files (usually on /etc/xen) can use either format. When using
sxp format, you need to add "-F" to "xm create" or "xm new".

> Do I indeed edit the config.sxp file? If so, what does the syntax look like
> to add another vif device?

When the config file is located there, it means the domain is managed
by xend. That's what would happen if you use "xm new", or use
virt-install on newer xen versions. To change the configuration you
should either:
- use commands that can edit configuration online, like "xm
network-attach" (see "man xm" for details), OR
- shutdown the domU, export it's config file (or copy the config.sxp
somewhere else), delete the domU (xm delete), edit config file, import
the domU (xm new), OR
- shutdown domU, edit config.sxp, restart xend, start domU (not recommended)

--

-- 
Fajar

RE: Xen-bridge throughput

_______________________________________________
Xen-users mailing list
Xen-users <at> lists.xensource.com
http://lists.xensource.com/xen-users

Re: GPLPV 7E Error during update

Hi Andrew,

> I've had exactly the same problem, I think it may be fixed in a newer
> version that James gave me to test but I cannot be sure of that until
> he releases some more new versions and I can test upgrading again, to
> avoid the problem I remove the drives using James's batch file and
> then install the new version, it takes a bit longer and requires more
> reboots but I've had no problems using that method.
> 
> You can get the batch file from
> http://www.meadowcourt.org/downloads/gplpv_uninstall_bat.zip
> 
> Uninstall, reboot, install, reboot, success :).

The recipe did work, but I had to disable the On demand Viruscheck's of 
Sophos. Otherwise I will get a blue screen. There will be a second mail 
about the Sophos Problem, I can provoke a blue Screen with Sophos.

Sincerly,
Klaus

_______________________________________________
Xen-users mailing list
Xen-users <at> lists.xensource.com
http://lists.xensource.com/xen-users

GPLPV Crash with Sophos

Hi James,

with an installed Sophos Virusscanner I can always provoke a blue 
screen. This happens both with 0.10.0.55 and 0.10.0.69. The blue 
definitly do not happen with /NOGPLPV

How to reproduce the problem:

Login as Admin
Right klick for example on the paper tray
Klick "Check with Sophos"

You get the blue screen. (is appended)

Sincerly,
Klaus

_______________________________________________
Xen-users mailing list
Xen-users <at> lists.xensource.com
http://lists.xensource.com/xen-users

Re: paravirtualization or not ?

Thanks,

William.

Nick Couchman wrote:
> 
> 
> In your domU (guest VM), look for /sys/hypervisor/type and cat that 
> file.  If it's a fully-virtualized machine, you probably won't see these 
> files and the O/S probably doesn't know about the hypervisor.  If it's 
> paravirtualized, these files should be there and you should see "xen" in 
> the hypervisor type.
> 
> 
> -Nick
> 
>  >>> On 2009/06/30 at 10:01, William <xen-mailinglist <at> voxtel.com> wrote:
> 
> Hi,
> 
> I installed xen-hypervisor-3.2 on ubuntu hardy, I used xen-tools to
> create VM and it works !
> But how I know if my xen solution is using paravirtualization or
> complete virtualization ??
> Is it automatically or is there an option in configuration file ?
> 
> details about my dom0:
> kernel : 2.6.24-24-xen
> cpuinfo proc : Quad-Core AMD Opteron(tm) Processor 2382
> cpuinfo flags : pae and svm
> 
> Thanks.
> 
> 
> ------------------------------------------------------------------------
> <br><hr>
> This e-mail may contain confidential and privileged material for the 
> sole use of the intended recipient. If this email is not intended for 
> you, or you are not responsible for the delivery of this message to the 
> intended recipient, please note that this message may contain SEAKR 
> Engineering (SEAKR) Privileged/Proprietary Information. In such a case, 
> you are strictly prohibited from downloading, photocopying, distributing 
> or otherwise using this message, its contents or attachments in any way. 
> If you have received this message in error, please notify us immediately 
> by replying to this e-mail and delete the message from your mailbox. 
> Information contained in this message that does not relate to the 
> business of SEAKR is neither endorsed by nor attributable to SEAKR.
> 
> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> Xen-users mailing list
> Xen-users <at> lists.xensource.com
> http://lists.xensource.com/xen-users

xen cluster with heartbeat and resource fencing (SFEX)

Here is my (very experimental) setup:

- an heartbeat cluster with 2 nodes, with the standard RA provided for Xen.
- Xen kernel and hypervisor on every node, installed on local disks
- a SAN shared disk (with ocfs2) for domU's disk images (sparse files).
- Resource fencing with SFEX.

All with standard Debian Lenny packages.

My choice for SFEX (compared to STONITH) for fencing is due to this  
fact: the only shared data are the domU disk images, an the only way  
they can be corrupted in a split-brain scenario is when 2 domUs are  
started on both nodes at the same time. THis can be elegantly avoided  
using sfex, with the check of a shared disk, that works even if every  
communication between the two nodes is broken.

to obtain this, I've grouped every Xen resource with a correspondent sfex one.

Everything works fine, until I try to live-migrate a domU resource  
from node A to B: it seems that sfex causes the domU shutdown on node  
A, and restart to the B (instead of live migrate from A to B).

If I use only standard RA for Xen instead (without sfex), the domU is  
correctly live-migrated from node A to B, without shutdown.

Any suggestion (or any working cluster setup to recommend)?

Massimiliano De Ruosi

----------------------------------------------------------------------
SEMEL (SErvizio di Messaging ELettronico) - CSIT -Universita' di Udine

strange error

Hi , I am getting the following errors on xen  the dom0 is Centos and 
the xen is
Compiled against library: libvir 0.3.3
Using library: libvir 0.3.3
Using API: Xen 3.0.1
Running hypervisor: Xen 3.1.0

the error is
---------
[Wed, 01 Jul 2009 14:54:24 virt-install 21784] ERROR (virt-install:506) 
virDomainCreateLinux() failed POST operation failed: (xend.err 'Device 0 
(vif) could not be connected. Hotplug scripts not working.')
Traceback (most recent call last):
  File "/usr/bin/virt-install", line 502, in ?
    main()
  File "/usr/bin/virt-install", line 462, in main
    dom = guest.start_install(conscb,progresscb)
  File "/usr/lib/python2.4/site-packages/virtinst/Guest.py", line 813, 
in start_install
    return self._do_install(consolecb, meter)
  File "/usr/lib/python2.4/site-packages/virtinst/Guest.py", line 834, 
in _do_install
    self.domain = self.conn.createLinux(install_xml, 0)
  File "/usr/lib64/python2.4/site-packages/libvirt.py", line 573, in 
createLinux
    if ret is None:raise libvirtError('virDomainCreateLinux() failed', 
conn=self)
libvirtError: virDomainCreateLinux() failed POST operation failed: 
(xend.err 'Device 0 (vif) could not be connected. Hotplug scripts not 
working.')
--------------

any suggestion ?

BR

Zeeshan

2.6.30.1-rc1 dom0 tarball

Andrew Lyon wrote:
> I have rebased the xen-patches from opensuse
> kernel-source-2.6.30-50.1.src.rpm so that they can be applied to
> vanilla 2.6.30, the usual patches tarball and gentoo ebuild are
> available at http://code.google.com/p/gentoo-xen-kernel/downloads/list
> , if you are not using Gentoo simply apply the patches in numeric
> order.
> 
> Some notes:
> 
> both dom0 and domU require CONFIG_SPARSE_IRQ=y and CONFIG_HOTPLUG=y
> 64 bit dom0/domU requires CONFIG_IA32_EMULATION=y
> 
> Andy

hello Andy,

many thanks for your work.
I have taken your patch set and applied it on top of vanilla
2.6.30.1-rc1 and applied this patch for gcc4.3 bug:

http://xenbits.xen.org/gitweb?p=xenclient/linux-2.6.27-pq.git;a=blob_plain;f=master/clobber-induction-variable.patch;hb=HEAD

for the lazy people out there, here is the distclean tarball:

http://x17.eu/linux-2.6.30.1-rc1-xen.aka.suse-xenified-2.6.30-50.1-rebased.patches.by.andrew.lyon.tar.gz
http://x17.eu/linux-2.6.30.1-rc1-xen.aka.suse-xenified-2.6.30-50.1-rebased.patches.by.andrew.lyon.tar.gz.md5

--
daniel