From gerhardus.geldenhuis at gmail.com  Tue Jan  1 19:12:13 2008
From: gerhardus.geldenhuis at gmail.com (Gerhardus Geldenhuis)
Date: Tue, 1 Jan 2008 19:12:13 +0000
Subject: [Fedora-xen] General confusion
Message-ID: <9c8eb0180801011112s5c5808cfra77407e15536c4da@mail.gmail.com>

Hi
My goal is to create a xen domain using lvm backed storage. It sounds simple
and probably is but I am getting caught down in the details. I am using RH5
which I am hopefull will be similar enough to be able to ask on this list.
Its the only list on https://www.redhat.com/mailman/listinfo with xen in the
name.

Up to now I have been using virt-install to create new domains. It takes
care of a lot of detail but this is a lot like spoon feeding and you learn
nothing plus it is limited in capabilities at the moment.

Confusion one:
When creating a new domain it creates a config file that xm can use:
name = "test03"
uuid = "80bd6bda-c559-3a68-643c-df0f29d672b9"
maxmem = 200
memory = 200
vcpus = 1
bootloader = "/usr/bin/pygrub"
on_poweroff = "destroy"
on_reboot = "restart"
on_crash = "restart"
vfb = [  ]
disk = [ "tap:aio:/root/temppart/test03.img,xvda,w" ]
vif = [ "mac=00:16:3e:24:15:79,bridge=virbr0" ]

When I dump the config using virsh it adds some additinal paramters:

  <os>
    <type>linux</type>
    <kernel>/var/lib/xen/boot_kernel.nNlfNC</kernel>
    <initrd>/var/lib/xen/boot_ramdisk.jV4otH</initrd>
    <cmdline>ro root=/dev/VolGroup00/LogVol00 console=xvc0</cmdline>

This names changes every time you restart the xen domain. What creates this
<random> kernel and initrd and would using the following config be the same
thing:

    <kernel>/boot/vmlinuz-2.6.18-53.el5xen</kernel>
    <initrd>/boot/initrd-2.6.18-53.el5xen.img</initrd>

I am also a bit confused about the <cmdline> value and how it is used and
what it should be. If anybody has a brief explanation of how this fits into
the greater scheme of things it would be really appreciated.

Lastly, I have managed to create a xml config file for virsh which does not
immediatly complain about any errors. However I am still unsure how/where to
specify the installation (http) source. I dont want to copy a existing
installation I want to create a new one, would this just be a kernel
parameter?

The config file I am using:
<domain type='xen' id='3'>
  <name>test-a-01</name>
  <os>
    <type>linux</type>
    <kernel>/boot/vmlinuz-2.6.18-53.el5xen</kernel>
    <initrd>/boot/initrd-2.6.18-53.el5xen.img</initrd>
    <cmdline>ro root=/dev/VolGroup00/LogVol00 console=xvc0</cmdline>
  </os>
  <memory>202144</memory>
  <vcpu>1</vcpu>
  <on_poweroff>destroy</on_poweroff>
  <on_reboot>restart</on_reboot>
  <on_crash>restart</on_crash>
  <devices>
    <interface type='bridge'>
      <source bridge='virbr0'/>
      <script path='vif-bridge'/>
    </interface>
    <disk type='phy' device='disk'>
      <driver name='tap' type='aio'/>
      <source file='/root/parts/test-a-01.img'/>
      <target dev='xvda'/>
    </disk>
    <console tty='/dev/pts/2'/>
  </devices>
</domain>


Regards

-- 
Gerhardus Geldenhuis
Registered Linux User #193352
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/fedora-xen/attachments/20080101/e88e6397/attachment.htm>

From phil at pricom.com.au  Tue Jan  1 20:33:22 2008
From: phil at pricom.com.au (Phil Rhoades)
Date: Wed, 02 Jan 2008 07:33:22 +1100
Subject: [Fedora-xen] Using old F7 guests in F8?
Message-ID: <1199219602.6370.29.camel@prix.pricom.com.au>

People,

It looks like the configuration stuff has changed from F7 to F8? - I
still have the F7 kernel, guest cfg and disk files but I couldn't find
anything about how to use them in F8.  It is not important, I just
thought it would be an interesting exercise . .

Thanks,

Phil.
-- 
Philip Rhoades

Pricom Pty Limited  (ACN 003 252 275  ABN 91 003 252 275)
GPO Box 3411
Sydney NSW      2001
Australia
Fax:     +61:(0)2-8221-9599
E-mail:  phil at pricom.com.au



From Ian.Jackson at eu.citrix.com  Wed Jan  2 15:01:05 2008
From: Ian.Jackson at eu.citrix.com (Ian Jackson)
Date: Wed, 2 Jan 2008 15:01:05 +0000
Subject: [Fedora-xen] Preview Xen 3.2 rc* packages
In-Reply-To: <20071221164547.GA25635@redhat.com>
References: <18283.59948.237498.121335@mariner.uk.xensource.com>
	<20071221172305.GC27601@redhat.com>
	<20071221164547.GA25635@redhat.com>
	<20071221165134.GA27601@redhat.com>
Message-ID: <18299.42801.501835.413811@mariner.uk.xensource.com>

Daniel P. Berrange writes ("Re: [Fedora-xen] Preview Xen 3.2 rc*
packages"):
> [stuff]

Thanks for your helpful comments.

> On Fri, Dec 21, 2007 at 04:30:36PM +0000, Ian Jackson wrote:
> >  xen-qemu-bootmenu.patch 
> >  pygrub-manykernels.patch
> 
> There were both written by Jeremy, so copyright Red Hat. I'll get them
> posted upstream.

I see you've done that now, thanks.  I don't know if they'll make
3.2.0 at this stage but I'll include them in my release packages if
not.

> We are going to be putting the hypervisor in a 'xen-hypervisor' package
> for F9, so it might be work folowing same practice.

Right, yes, I'll see about doing the same.

> > I have not included xen-net-bridge.patch which seemed quite a
> > surprising set of changes to me.
> 
> Most of those, if not all, should be upstream in 3.2.0

I don't think so but if you think so then fine - I'm happiest here
just shipping the upstream code unaltered.

> > I was rather puzzled by the part of xen-initscript.patch which removes
> > most of xend's startup code.  I agree that xend's arrangements are not
> > entirely ideal but is there really much to be gained by making that
> > changes, which obviously makes the patchset much more fragile ?
> 
> The reason for this is that the upstream changset did not play nicely
> with standard Fedora init script good practice. IMHO duplicating stuff
> that is already provided by standard initscript shell functions in 
> python is a bad idea, hence we killed it.  I did post these changes
> upstream for review at the time by they weren't incporated. Should be
> in the archives somewhere....

Hmm.  I have some sympathy with this line of reasoning but there are
some subtleties to do with the lifetimes of the various daemons and of
course it might happen that there would be a reorganisation of of
these daemons (into a different set of processes).

I think it's better to regard these as `parts' of xend, rather than
individual daemons in their own right.  That also means that when Xen
is ported to a new host OS, less work is needed to adapt the daemon
startup to conform to the host's arrangements.

In any case the upstream 3.2.0 won't change in this area at this
stage.  It's probably best of the packages I make for Fedora use your
setup (particularly since otherwise I'd have to tack a hatchet to the
existing FC7 init scripts).

> FYI, you might want to check the rawhide spec file - for pre-release builds 
> we are standardizing on a numbering format of:
>    'xen-3.2.0-0.fc8.rc3.dev16606'

I'll take a look at the rawhide spec file, and your Fedora 9 version,
but mainly for illumination than code.  I think the upstream-provided
packages of 3.2.0 for fc8 ought to be based on the 3.1.x fc8 packages.

> NB, the leading the '0' in the release  number ensures the upgrade path
> to the final official  3.2.0-1.fc9  package.

Right, I'll do that next time.

Daniel P. Berrange writes ("Re: [Fedora-xen] Preview Xen 3.2 rc* packages"):
> FYI, my  3.2.0 RPMs for Fedora 9 are currently in a branch of Fedora
> CVS called  'private-berrange-xen-unstable' viewable here: [...]

Thanks.

> I've not decided yet on wether to name the hypervisor '/boot/xen.gz' or 
> include a full version '/boot/xen-3.2.0.gz', or version + release
> '/boot/xen-3.2.0-1.fc9'. I think i'll probably go for 'xen-3.2.0.gz'

I would definitely include the hypervisor version in future; I'm less
sure about the package version.

Debian have a very nice arrangement which lets you co-install
different hypervisor and tools versions, and then effectively
dual-boot.  Unfortunately their patches are very intrusive so that
won't be in 3.2.0, but I think we certainly want to move in that
direction upstream in the future (probably with different changes to
achieve the same effect, rather than trying to import and redact
Debian's patchset).

Daniel P. Berrange writes ("Re: [Fedora-xen] Preview Xen 3.2 rc* packages"):
> Can I request that you include something in the release number to indicate
> that these are XenSource provided RPMs - just using 'fc8' will lead to
> confusion with the base Fedora provide RPMs. Either add 'xs' after the
> initial release digit, or tag it on after the %dist tag, eg one of
> 
>     xen-3.1.9-0xs.fc8.i386.rpm
>     xen-3.1.9-0.fc8.xs1.i386.rpm

Of course.  I should have done that to start with, really.

> This ensures that if we get Bug reports it'll be clear which RPMs are being
> used.

Right.


Regards,
Ian.



From berrange at redhat.com  Wed Jan  2 15:12:59 2008
From: berrange at redhat.com (Daniel P. Berrange)
Date: Wed, 2 Jan 2008 15:12:59 +0000
Subject: [Fedora-xen] Preview Xen 3.2 rc* packages
In-Reply-To: <18299.42801.501835.413811@mariner.uk.xensource.com>
References: <18283.59948.237498.121335@mariner.uk.xensource.com>
	<20071221172305.GC27601@redhat.com>
	<20071221164547.GA25635@redhat.com>
	<20071221165134.GA27601@redhat.com>
	<18299.42801.501835.413811@mariner.uk.xensource.com>
Message-ID: <20080102151259.GB1237@redhat.com>

On Wed, Jan 02, 2008 at 03:01:05PM +0000, Ian Jackson wrote:
> > I've not decided yet on wether to name the hypervisor '/boot/xen.gz' or 
> > include a full version '/boot/xen-3.2.0.gz', or version + release
> > '/boot/xen-3.2.0-1.fc9'. I think i'll probably go for 'xen-3.2.0.gz'
> 
> I would definitely include the hypervisor version in future; I'm less
> sure about the package version.

Since Kier has said that each bug-fix series 3.1.x and 3.2.x maintain
hypervisor <->  ABI compatability, I reckon we should name the hypervisor
according to this version, so  '/boot/xen-3.1.gz' and '/boot/xen-3.2.gz'.
That way people can update the minor releases 3.2.0, 3.2.1, 3.2.2, etc
and not have to worry about changing grub configs.

> Debian have a very nice arrangement which lets you co-install
> different hypervisor and tools versions, and then effectively
> dual-boot.  Unfortunately their patches are very intrusive so that
> won't be in 3.2.0, but I think we certainly want to move in that
> direction upstream in the future (probably with different changes to
> achieve the same effect, rather than trying to import and redact
> Debian's patchset).

Personally I'd like to see upstream get serious about Hypervisor <-> Tools
ABI compatability. If you look at the changes in ABI from 3.1 to 3.2 trees
it would have been pretty trivial to maintain compatability for new 3.2 
hypervisor against old 3.1 tools. This is an idea that's been rejected
many times before, but I'd still like to see it. cf new Linux releases 
don't break glibc each time. Then we could finally get out of the lock-step 
upgrades..

Regards,
Dan.
-- 
|=- Red Hat, Engineering, Emerging Technologies, Boston.  +1 978 392 2496 -=|
|=-           Perl modules: http://search.cpan.org/~danberr/              -=|
|=-               Projects: http://freshmeat.net/~danielpb/               -=|
|=-  GnuPG: 7D3B9505   F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505  -=| 



From george.refseth at arxi.no  Wed Jan  2 15:34:52 2008
From: george.refseth at arxi.no (George Refseth)
Date: Wed, 02 Jan 2008 16:34:52 +0100
Subject: [Fedora-xen] Are 64bit Intel Core 2 Quad fedora 8 supported?
In-Reply-To: <op.t3x88fq81nf74w@thosha.arxi.no>
References: <op.t3x88fq81nf74w@thosha.arxi.no>
Message-ID: <op.t4a6vdvx1nf74w@thosha.arxi.no>

It seems I got little attention with my original post.
The f8 64bit image hangs when starting X. Prior to that
the visual 'wait' circle keeps running around irregularily
at a lot than normal speed.

I observed the same on multi core AMD running RHEL 4, which
was cured with RHEL 5. So no I am happy on that multi-core
workstation.

But this new server I was trying to set up had definite problems
with the -21 xen kernel. It runs flawlessly with the f8 release
kernel (-23).

For testing, where should I pull down a newer xen-kernel that would
run with a full 64 bit f8 install? I would be happy to be a guinea pig
(as long as I can revert) using this system if I could be pointed to
repositories and forum where I could contribute..

thanks in advance,
George

On Wed, 26 Dec 2007 16:57:32 +0100, George Refseth  
<george.refseth at arxi.no> wrote:

> The 64 bit xen host kernel are unstable (timer/scheduling issue?)
>
> So I wonder if this is supported or not. Another Fedora 8 x86_64
> installation on
> an Intel Core 2 Duo seems to run flawlessly, except it is running on a
> laptop,
> and not meant for server use.
>

> Attached are smolt output.

See original post.

>
> I would be grateful for any input, this was meant to be a system where
> multiple
> services should run (several 64bit F8's) serving dns, web and mail, and
> replace
> at least two current lumps of hardware..
>
> regards,
> George
>



-- 
Using Opera's revolutionary e-mail client: http://www.opera.com/mail/



From berrange at redhat.com  Wed Jan  2 15:39:55 2008
From: berrange at redhat.com (Daniel P. Berrange)
Date: Wed, 2 Jan 2008 15:39:55 +0000
Subject: [Fedora-xen] Are 64bit Intel Core 2 Quad fedora 8 supported?
In-Reply-To: <op.t4a6vdvx1nf74w@thosha.arxi.no>
References: <op.t3x88fq81nf74w@thosha.arxi.no>
	<op.t4a6vdvx1nf74w@thosha.arxi.no>
Message-ID: <20080102153955.GC1237@redhat.com>

On Wed, Jan 02, 2008 at 04:34:52PM +0100, George Refseth wrote:
> It seems I got little attention with my original post.
> The f8 64bit image hangs when starting X. Prior to that
> the visual 'wait' circle keeps running around irregularily
> at a lot than normal speed.
> 
> I observed the same on multi core AMD running RHEL 4, which
> was cured with RHEL 5. So no I am happy on that multi-core
> workstation.
> 
> But this new server I was trying to set up had definite problems
> with the -21 xen kernel. It runs flawlessly with the f8 release
> kernel (-23).
> 
> For testing, where should I pull down a newer xen-kernel that would
> run with a full 64 bit f8 install? I would be happy to be a guinea pig
> (as long as I can revert) using this system if I could be pointed to
> repositories and forum where I could contribute..

I'm afraid the 2.6.21  series of kernel-xen will be the newest
we release for F-8 and earlier - its in bugfix only mode[1]. If there
is an easy bugfix we can do for 2.6.21 to make it work that's a
possiblity but we won't be doing .22 or .23 kernel-xen. I'd recommend
filing a BZ ticket with as many details of the problem you are seeing
as possible:

  http://bugzilla.redhat.com/

Regards,
Dan.

[1] This is because in Fedora-9 we are radically changing the way we 
    approach Xen kernels
    http://fedoraproject.org/wiki/Features/XenPvops


-- 
|=- Red Hat, Engineering, Emerging Technologies, Boston.  +1 978 392 2496 -=|
|=-           Perl modules: http://search.cpan.org/~danberr/              -=|
|=-               Projects: http://freshmeat.net/~danielpb/               -=|
|=-  GnuPG: 7D3B9505   F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505  -=| 



From george.refseth at arxi.no  Wed Jan  2 17:24:27 2008
From: george.refseth at arxi.no (George Refseth)
Date: Wed, 02 Jan 2008 18:24:27 +0100
Subject: [Fedora-xen] Are 64bit Intel Core 2 Quad fedora 8 supported?
In-Reply-To: <20080102153955.GC1237@redhat.com>
References: <op.t3x88fq81nf74w@thosha.arxi.no>
	<op.t4a6vdvx1nf74w@thosha.arxi.no>
	<20080102153955.GC1237@redhat.com>
Message-ID: <op.t4bby1c71nf74w@thosha.arxi.no>

On Wed, 02 Jan 2008 16:39:55 +0100, Daniel P. Berrange  
<berrange at redhat.com> wrote:

> On Wed, Jan 02, 2008 at 04:34:52PM +0100, George Refseth wrote:
>> It seems I got little attention with my original post.
>> The f8 64bit image hangs when starting X. Prior to that
>> the visual 'wait' circle keeps running around irregularily
>> at a lot than normal speed.
>>
>> I observed the same on multi core AMD running RHEL 4, which
>> was cured with RHEL 5. So no I am happy on that multi-core
>> workstation.
>>
>> But this new server I was trying to set up had definite problems
>> with the -21 xen kernel. It runs flawlessly with the f8 release
>> kernel (-23).
>>
>> For testing, where should I pull down a newer xen-kernel that would
>> run with a full 64 bit f8 install? I would be happy to be a guinea pig
>> (as long as I can revert) using this system if I could be pointed to
>> repositories and forum where I could contribute..
>
> I'm afraid the 2.6.21  series of kernel-xen will be the newest
> we release for F-8 and earlier - its in bugfix only mode[1]. If there
> is an easy bugfix we can do for 2.6.21 to make it work that's a
> possiblity but we won't be doing .22 or .23 kernel-xen. I'd recommend
> filing a BZ ticket with as many details of the problem you are seeing
> as possible:

Thanks for a quick response, even if it doesn't really help me.
The system also won't boot in i386 mode with the latest BIOS, so I will
run non-virtualized 64 bit for testing purposes until you have a testable
xen enabled kernel for -25 (?) available and forgo the bug report.

Thanks again,
George


>
>   http://bugzilla.redhat.com/
>
> Regards,
> Dan.
>
> [1] This is because in Fedora-9 we are radically changing the way we
>     approach Xen kernels
>     http://fedoraproject.org/wiki/Features/XenPvops
>
>



-- 
Using Opera's revolutionary e-mail client: http://www.opera.com/mail/



From sa212+fcxen at cyconix.com  Wed Jan  2 17:52:31 2008
From: sa212+fcxen at cyconix.com (Evan Lavelle)
Date: Wed, 02 Jan 2008 17:52:31 +0000
Subject: [Fedora-xen] Are 64bit Intel Core 2 Quad fedora 8 supported?
In-Reply-To: <op.t3x88fq81nf74w@thosha.arxi.no>
References: <op.t3x88fq81nf74w@thosha.arxi.no>
Message-ID: <477BCF5F.9050208@cyconix.com>

George Refseth wrote:
> The 64 bit xen host kernel are unstable (timer/scheduling issue?)
> 
> So I wonder if this is supported or not. Another Fedora 8 x86_64 
> installation on
> an Intel Core 2 Duo seems to run flawlessly, except it is running on a 
> laptop,
> and not meant for server use.

FWIW: I'm running F8 64-bit 2.6.21-2952, for both Dom0 and one DomU, on 
6600/Core 2 Duo, without problems. The DomU is HVM; it was originally PV 
but I gave up on that for complex reasons. Various other (non-Fedora) 
HVM domU's also work without problems.

Maybe it's just an issue with quad core. Can you turn off two cores in 
the BIOS?

Evan



From Dustin.Henning at prd-inc.com  Wed Jan  2 18:44:39 2008
From: Dustin.Henning at prd-inc.com (Dustin Henning)
Date: Wed, 2 Jan 2008 13:44:39 -0500
Subject: [Fedora-xen] Are 64bit Intel Core 2 Quad fedora 8 supported?
In-Reply-To: <477BCF5F.9050208@cyconix.com>
References: <op.t3x88fq81nf74w@thosha.arxi.no> <477BCF5F.9050208@cyconix.com>
Message-ID: <003401c84d6f$88136460$983a2d20$@Henning@prd-inc.com>

	I am not running F8, all of my DomUs are HVM, and I am not running
64-bit OSes on any of them, so I was staying out of this one, but I am
running F7 64-bit with Xen kernel 2.6.21-6 on a Core 2 Quad, and since you
are having problems even with 32-bit PV guests, I thought that this might be
useful information.  Perhaps you have some sort of BIOS configuration issue
or something.
	Dustin

-----Original Message-----
From: fedora-xen-bounces at redhat.com [mailto:fedora-xen-bounces at redhat.com]
On Behalf Of Evan Lavelle
Sent: Wednesday, January 02, 2008 12:53
To: George Refseth
Cc: fedora-xen at redhat.com
Subject: Re: [Fedora-xen] Are 64bit Intel Core 2 Quad fedora 8 supported?

George Refseth wrote:
> The 64 bit xen host kernel are unstable (timer/scheduling issue?)
> 
> So I wonder if this is supported or not. Another Fedora 8 x86_64 
> installation on
> an Intel Core 2 Duo seems to run flawlessly, except it is running on a 
> laptop,
> and not meant for server use.

FWIW: I'm running F8 64-bit 2.6.21-2952, for both Dom0 and one DomU, on 
6600/Core 2 Duo, without problems. The DomU is HVM; it was originally PV 
but I gave up on that for complex reasons. Various other (non-Fedora) 
HVM domU's also work without problems.

Maybe it's just an issue with quad core. Can you turn off two cores in 
the BIOS?

Evan

--
Fedora-xen mailing list
Fedora-xen at redhat.com
https://www.redhat.com/mailman/listinfo/fedora-xen




From felix.schwarz at web.de  Wed Jan  2 20:17:31 2008
From: felix.schwarz at web.de (Felix Schwarz)
Date: Wed, 02 Jan 2008 21:17:31 +0100
Subject: [Fedora-xen] Fedora 8 DomU (i386) does not work on Fedora 8
	(x86_64) host
Message-ID: <477BF15B.1030901@web.de>

Hi,

I'm using Xen since Fedora Core 6. My Dom0 runs the latest version of 
Fedora 8. Currently, I can install a Fedora 8 i386 DomU. The installation 
always hangs after formatting the virtual hard drive. The only message is 
"Please wait... This may take a few minutes" (from memory, translated from 
German). Unfortunately, this message appears not for some minutes but stays 
"forever" (at least 30 minutes).

My computer is reasonably fast (AMD X2) with plenty of RAM (4 GB). With 
Fedora 8 (x86_64) this messages is only visible for some seconds. There is 
no difference if I do install F8 i386 as HVM or PV domain.

One thing I noticed is that I did not manage to install Fedora 8 using QEMU.

Did anyone experience similar issues? I suspect, my local Fedora 
installation repository may be faulty although all packages are fine 
(checked with "rpm --checksig *") and I regenerated the repodata multiple 
times.

Any hints? Thank you very much.
fs
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 3299 bytes
Desc: S/MIME Cryptographic Signature
URL: <http://listman.redhat.com/archives/fedora-xen/attachments/20080102/ddf0ee3f/attachment.bin>

From berrange at redhat.com  Wed Jan  2 20:21:36 2008
From: berrange at redhat.com (Daniel P. Berrange)
Date: Wed, 2 Jan 2008 20:21:36 +0000
Subject: [Fedora-xen] Fedora 8 DomU (i386) does not work on Fedora 8
	(x86_64) host
In-Reply-To: <477BF15B.1030901@web.de>
References: <477BF15B.1030901@web.de>
Message-ID: <20080102202135.GF1237@redhat.com>

On Wed, Jan 02, 2008 at 09:17:31PM +0100, Felix Schwarz wrote:
> Hi,
> 
> I'm using Xen since Fedora Core 6. My Dom0 runs the latest version of 
> Fedora 8. Currently, I can install a Fedora 8 i386 DomU. The installation 
> always hangs after formatting the virtual hard drive. The only message is 
> "Please wait... This may take a few minutes" (from memory, translated from 
> German). Unfortunately, this message appears not for some minutes but stays 
> "forever" (at least 30 minutes).
> 
> My computer is reasonably fast (AMD X2) with plenty of RAM (4 GB). With 
> Fedora 8 (x86_64) this messages is only visible for some seconds. There is 
> no difference if I do install F8 i386 as HVM or PV domain.

Running  paravirt  i386  domU on a x86_64 Dom0 is known to be rather
unreliable. The message you describe about install hanging during the 
formatting stage is definitely a symptom of running i386 domU on a
x86-64 dom0.  You ought to be able to mix- archs if you do HVM instead
though, so I'm rather surprised if you see the same problems with HVM
guests. 

Regards,
Dan.
-- 
|=- Red Hat, Engineering, Emerging Technologies, Boston.  +1 978 392 2496 -=|
|=-           Perl modules: http://search.cpan.org/~danberr/              -=|
|=-               Projects: http://freshmeat.net/~danielpb/               -=|
|=-  GnuPG: 7D3B9505   F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505  -=| 



From felix.schwarz at web.de  Wed Jan  2 20:35:53 2008
From: felix.schwarz at web.de (Felix Schwarz)
Date: Wed, 02 Jan 2008 21:35:53 +0100
Subject: [Fedora-xen] Fedora 8 DomU (i386) does not work on Fedora 8
	(x86_64) host
In-Reply-To: <20080102202135.GF1237@redhat.com>
References: <477BF15B.1030901@web.de> <20080102202135.GF1237@redhat.com>
Message-ID: <477BF5A9.9000600@web.de>


Daniel P. Berrange schrieb:
> Running  paravirt  i386  domU on a x86_64 Dom0 is known to be rather
> unreliable. The message you describe about install hanging during the 
> formatting stage is definitely a symptom of running i386 domU on a
> x86-64 dom0.  You ought to be able to mix- archs if you do HVM instead
> though, so I'm rather surprised if you see the same problems with HVM
> guests. 

Yeah, I tried pv i386 just out of curiosity so I checked HVM/qemu quickly 
thereafter. I can even reproduce the problem (rebooted multiple times etc.).

My setup is quite boring: The DomUs use normal files as "disks" below 
/var/lib/xen/images with preallocated space (4 GB), they get 500 MB RAM for 
the initial install, packages are pulled from a HTTP repository server in 
my local network (shared eth0 bridging, using DHCP/ipv4 only). This setup 
worked/works for every Fedora version since Core 5 so I'm quite puzzled how 
to get further debug information...

fs
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 3299 bytes
Desc: S/MIME Cryptographic Signature
URL: <http://listman.redhat.com/archives/fedora-xen/attachments/20080102/8ee873fb/attachment.bin>

From davidl at matissenetworks.com  Fri Jan  4 01:29:22 2008
From: davidl at matissenetworks.com (David Levinger)
Date: Thu, 3 Jan 2008 17:29:22 -0800
Subject: [Fedora-xen] Fedora Core 8 + Xenbr0 + network bridging?
In-Reply-To: <4757031A.6030004@redhat.com>
References: <F237EFC9919B064C8BF5A44CDA5DA0C2015B23CC@matisse01.matissenetworks.com><4751EBFE.6000100@redhat.com><F237EFC9919B064C8BF5A44CDA5DA0C2015B23CF@matisse01.matissenetworks.com><F237EFC9919B064C8BF5A44CDA5DA0C2016948EA@matisse01.matissenetworks.com>
	<4757031A.6030004@redhat.com>
Message-ID: <F237EFC9919B064C8BF5A44CDA5DA0C20173CECC@matisse01.matissenetworks.com>

Hey all,

I've been meaning to respond to this for quite awhile but work is crazy,
then the holidays etc etc. We were finally able to get this working on
Centos 5.1, though I'd hazard the same would work for Fedora 8 as I have
that running on my desktop and was able to reproduce what I found on
that system.

We now have this going on several bonded NIC machines with a whole bunch
of Xen Virtual machines going and man oh man it's great!

The heart of the issue seemed to be that we were working with a Bonded
nic and for some reason as soon as we bonded them virt-manager no longer
recognized anything.

What I was able to figure out was that as soon as you remove the
"HWADDR=00:00:00:00:00:00" line from your ifcfg-eth0 file virt-manager
no longer recognizes it as a valid bridge device. HOWEVER, if you use
virt-install from the command line you can STILL point it to the bridge
and it will work for the install and function from that point on NP. But
you cannot install through virt-manager.

I'm pretty sure that this is a bug, but it's possible that I'm missing
something so I wanted to pass it onto all you folks that were so helpful
when I was struggling through this the first time.

On my Fedora 8 desktop if I remove that HWADDR line from ifcfg-eth0 then
I can no longer select my bridge, but as soon as I add it back I can
once again select it.

The process that I went through to get this successfully function went
as follows (It was awhile ago, so if anyone tries this and runs into
anything not listed please let me know):

1. Install OS with both nics connected to non-bonded pair of connections
in the switch, both setup to be DHCP to make sure that both pull an
address.

2. After install I virsh net-undefine default and in
/etc/xen/xend-config.sxp comment out the line (network-script
network-bridge) and add the line (network-script /bin/true)

3. In /etc/xen/scripts/network-bridge I comment out the line
netdev=${netdev:-eth${vifnum}} and add the line netdev="bond0"

4. I create the bond normally, reboot and move the network connection to
the bonded pair on the switch and test to make sure the bond is fully
functional.

5. Once the bond is proved working I go back to
/etc/xen/xend-config.sxp, and uncomment (network-script network-bridge)
while commenting out (network-script /bin/true) Then I reboot so that it
can get the Xen bridge configured to use the bond.

6. After reboot you should see bond0, eth0, eth1, pbond0 and xenbr0
letting you know that the bridge is configured and ready to go. If you
try and create through virt-manager you will have NO option for bridged
networking, BUT if you run: virt-install --bridge=xenbr0 you can use the
bridge to setup machine NP!

Thanks for all of your help, there is no way I'd have been able to
figure out everything I did without insights from each of you. I'm
exceptionally satisfied with the end product and Long Live Xen!

David



-----Original Message-----
From: fedora-xen-bounces at redhat.com
[mailto:fedora-xen-bounces at redhat.com] On Behalf Of Mark Nielsen
Sent: Wednesday, December 05, 2007 11:59 AM
To: Christian Lahti
Cc: fedora-xen at redhat.com
Subject: Re: [Fedora-xen] Fedora Core 8 + Xenbr0 + network bridging?

Christian,

Sorry to hear it didn't work out for you. It's not a straight-forward or

simple configuration. The problem is that there are so many possible 
combinations of VLANs, bonds, networks that most of the configuration is

left up to the ability and knowledge of the administrator. It sounds 
like you might've missed a few steps somewhere along the way. I admit 
that my document isn't 100% step-by-step, it takes a pretty good 
understanding of everything that's going on. Your problem could be in 
your step where you "Restart networking". This stuff all needs to happen

in a particular order, and that might not have happened. Unfortunately 
it's nearly impossible to help troubleshoot that in e-mails. I can say 
that I have the configuration I describe (and it sounds like what you 
want) working perfectly, so I know it's possible.

Mark

Christian Lahti wrote:
> Hi Mark:
>
>  
>
> Well, 
>
>  
>
> I carefully went through your PDF document for setting up a bonded
pair
> on RHEL 5.1 and at the end of the day this does not work for me.  This
> is the procedure more or less I have tried:
>
>  
>
> *	Make sure eth0 and eth1 work as normal eth devices without LACP
> *	Edit /etc/modprobe.conf to add the bonding kernel module
> *	Edit /etc/sysconfig/network-scripts/ifcfg-eth0 and ifcfg-eth1 to
> be slave devices with the master as bond0
> *	Create /etc/sysconfig/network-scripts/ifcfg-bond0 with static IP
> info
> *	Plug into LACP enabled ports on switch and reboot the box
> *	At this point bond0 works fine, as expected, we have been doing
> this all day long on non-xen kernels for years
> *	NOW...following your document
> *	Remove the /etc/libvirt/qemu/networks/autostart/* so that the
> pointless 192.168.122.x NAT network does not get created
> *	Grab the network-scripts-bridge-bond-vlan script from the link
> in the message and put into /etc/xen/scripts
> *	Edit /etc/xen/xend-config.sxp and replace (network-script
> network-bridge) with (network-script network-bridge-bond-vlan)
> *	Restart networking
> *	At this point networking for the physical host in invariably
> completely hosed, and there is no xen networking at all
> *	It is noteworthy to add that I did not make any modifications to
> the network-scripts-bridge-bond-vlan script as you suggest since I am
on
> a single vlan (so far) and the default setup in the script seems sane
> for a single NON-VLAN bond0 configuration
>
>  
>
> So in a nutshell the it seems that libvirt interface just does not
seem
> to use the xen scripts...rather it's own (undocumented?) crap.  After
a
> week of head-banging on this we really have no choice but to abandon
> Redhat in favor of Suse 10.3, which incidentally works right out of
the
> box with bridge, NAT, bond, you name it.  I suggest RH staff install a
> copy of this to see how they did it, you don't even have to jump
through
> hoops to configure a bond from the command line, you can do this with
> their stock GUI tools if you so choose.  I am not knocking RedHat, but
> we need something that "just works" and so far for xen + bond + RH has
> been a non-starter for us after much effort.  By the way, to get
> networking un-foobar'ed on the physical machine I have to run
> system-config-network and remove all Ethernet devices, then reboot,
then
> redefine eth0 and eth1 as as normal DHCP devices.  I can then go
> re-setup the bond0 device from the command line.
>
>  
>
> If anyone has step-by-step directions on how to do this with RHEL 5.1
I
> am happy to try again at some future point.  The goals are simple:
>
>  
>
> *	Step one: create a bond0 from eth0 and eth1 that can be used as
> a bridged device by xen on a single VLAN
> *	Step two: create a bond0 (aliases?) that can be assigned
> multiple VLANs, AND have these VLAN devices available to be used by
xen
>
>  
>
> I would settle for item #1 really.
>
>  
>
> /Christian
>
>  
>
>  
>
>  
>
>  
>
>  
>
> ________________________________
>
> From: Christian Lahti 
> Sent: Saturday, December 01, 2007 3:56 PM
> To: mnielsen at redhat.com; fedora-xen at redhat.com
> Subject: RE: [Fedora-xen] Fedora Core 8 + Xenbr0 + network bridging?
>
>  
>
> Hi Mark:
>
>  
>
> Thank you very much for your response, I did indeed read the original
> poster as Dale by mistake :)  So what you are saying makes perfect
sense
> to me and sounds like exactly what we are after, I will have 3 vlans
to
> bridge myself ultimately.  My next question is the relative merits of
> RHEL5.1 as compared to Fedora 8.  Obviously I would prefer the stable
> enterprise release rather than bleeding edge Fedora, but has fully
> virtualized windows performance been fixed in this release?  At any
rate
> I am looking forward to getting this up and running tomorrow!
>
>  
>
> /Christian
>
>  
>
>  
>
> ________________________________
>
> From: Mark Nielsen [mailto:mnielsen at redhat.com]
> Sent: Sat 12/1/2007 3:19 PM
> To: Christian Lahti
> Subject: Re: [Fedora-xen] Fedora Core 8 + Xenbr0 + network bridging?
>
> hmm, did you mean "Hi Mark" ??
>
> I have 8 Dell 2950s running RHEL 5.1 (new libvirt with that funky NAT
> they added). I have 4 NICs in each; 2 copper, 2 fiber. I bond the 2
> copper (eth0 and eth1) and call it bond0. bond0 carries my "private"
IP
> for cluster suite communications on the dom0 (physical) cluster.
>
> Then I bond eth2 and eth3 (fiber) in to bond1. I lay down the public
> network for the dom0 cluster on bond1.100 (for example, that would be
> VLAN 100). I also add many (up to 10 or so now) VLANs on bond1
> (bond1.20, bond1.21, bond1.22, etc). Then I create xen bridges to each
> of these bond/VLAN devices. This allows me to put any particular VM on
> any particular (or combination up to 3) of these xen bridged bonded
VLAN
> device.
>
> My document explains, in detail, how to do all of this :) The only
added
> step is that I have to "undefine" (virsh net-undefine default) the
> default network that the new libvirt creates (virbr0). Even with this
> new NAT thing they added, I've been told (by our devs) that the
> preferred way to do static network configurations is with the method I
> lay out. NAT is more for dynamic networks (cable modems, dial-up,
wifi,
> etc).
>
> I'm pretty sure there weren't any significant changes in Fedora 8
(we've
> dropped the word "core" now, btw) that don't exist in RHEL 5.1 with
> respects to the network. 5.0 -> 5.1 is when that NAT change came down
> the pipe.
>
> Mark
>
> p.s. I'm happy to answer any other questions you may have about my
> document. I'm quite certain that, if you follow it, you'll have what
> you're looking for.
>
> Christian Lahti wrote:
>   
>> Hi Dale:
>>
>> I work with David who posted the original question to the mailing
>> list.  I think we need to give a bit more background info on what we
>> are trying to do.  We are running a mixed environment of mostly
CentOS
>> 3, 4and 5, we do have a few windows servers and XP systems as well. 
>> We are looking to virtualize all these platforms.  Normally we have a
>> bonded pair of NICs for the physical hosts, we were able to get this
>> running using CentOS 5 x86_64 with no problems, the guest machines
use
>> the bonded pair in bridged mode as expected after a bit of tweaking. 
>> The biggest issue we found with EL5 is that windows guest performace
>> is dismal at best, hence our decision to have a look at Fedora Core 8
>> x86_64.  I am happy to report that performance for all of our guest
>> platforms is *very* good with FC8, but it seems that libvirt changed
>> the way networking is setup for Xen.  The default NAT configuration
is
>> pretty useless for production server environment.  Thanks to the
>> mailing list we are now able to bridge a single NIC on FC8 (like eth0
>> for example), but we cannot figure out how to get a bridge for bond0
>> (comprised of eth0 and eth1) defined and available to Xen.  All the
>> tweaks that worked find on EL5 have not worked so far on FC8.  I am
>> going to review your document tomorrow and give it a try, but any
idea
>> on whether your methodology will work on FC8 and libvirt?  I am
>> willing to blow a Sunday to get this worked out once and for all :)
>>
>> Basically we are after good performance on both para and fully
>> virtualized guests using a bonded pair of GB NICs for speed and
>> redundancy.  If this can be achieved with enterprise linux then that
>> would be preferable, but we will go FC8 if the bonding thing can be
>> sorted out.  By the way Xensource 4.x looks to be a respin of RHEL5
>> and has pretty good performance but their free version is limited to
>> 32bit (and hence 4GB ram).  Adding the clustering failover is the
next
>> step of course :)
>>
>> Thanks again for the help so far.
>>
>> /Christian
>>
>>
>>
>>     
>> just FYI for the list, I have a how-to for a bonded and VLAN tagged
>>     
> network.
>   
>> http://www.certifried.com
>>
>> ODT and PDF formats available.
>>
>>  
>> It might not be the best way, but I've sent it out to my colleagues
>> several times and have never received any negative feedback.
>> Mark
>>
>>
>>
>> Dale Bewley wrote:
>>  
>>
>>     I haven't done bonding, but you should be able to bond them and
>>     
> then compose a bridge on top of this bonded device I would think.
>   
>>     --
>>     Dale Bewley - Unix Administrator - Shields Library - UC Davis
>>     GPG: 0xB098A0F3 0D5A 9AEB 43F4 F84C 7EFD  1753 064D 2583 B098
A0F3
>>
>>     --
>>     Fedora-xen mailing list
>>     Fedora-xen redhat com
>>     https://www.redhat.com/mailman/listinfo/fedora-xen
>>        
>>
>>
>>     
>
************************************************************************
> ****
>   
>> Checked by MailWasher server (www.Firetrust.com)
>> WARNING. No FirstAlert account found.
>> To reduce spam further activate FirstAlert.
>> This message can be removed by purchasing a FirstAlert Account.
>>
>>     
>
************************************************************************
> ****
>   
>>     
>
------------------------------------------------------------------------
>   
>> --
>> Fedora-xen mailing list
>> Fedora-xen at redhat.com
>> https://www.redhat.com/mailman/listinfo/fedora-xen
>>  
>>     
>
>   

--
Fedora-xen mailing list
Fedora-xen at redhat.com
https://www.redhat.com/mailman/listinfo/fedora-xen



From Dustin.Henning at prd-inc.com  Fri Jan  4 16:57:09 2008
From: Dustin.Henning at prd-inc.com (Dustin Henning)
Date: Fri, 4 Jan 2008 11:57:09 -0500
Subject: [Fedora-xen] network speed on hvm guests
Message-ID: <005a01c84ef2$d8702720$89507560$@Henning@prd-inc.com>

	I was reading an article about Windows PE 2.0 in virtual
environments, and apparently Windows PE 2.0 is based on Vista, which doesn't
have a driver for the default NIC used by VMWare.  The suggested solution is
to use a different virtual NIC (a gigabit one).  Obviously Xen isn't VMWare,
and on top of that, I am not trying to run Windows PE 2.0, or even Vista.
However, I had long wondered but never asked this question:
	Does Xen have any virtual NICs other than the two mentioned in the
hvm example files in /etc/xen?  More importantly, does it matter, for
instance, will Xen or Windows limit the response time or throughput to
100MB/s levels in an hvm environment if a 100MB/s virtual NIC is used?  I
don't see why it would, but then again, I don't see why SATAII hard drives
running on controllers in IDE mode are slowed to IDE speeds, so I wouldn't
be surprised if it did, and I am hoping someone can tell me.  Thanks,
	Dustin




From pasik at iki.fi  Fri Jan  4 18:49:11 2008
From: pasik at iki.fi (Pasi =?iso-8859-1?Q?K=E4rkk=E4inen?=)
Date: Fri, 4 Jan 2008 20:49:11 +0200
Subject: [Fedora-xen] network speed on hvm guests
Message-ID: <20080104184911.GK17677@edu.joroinen.fi>

On Fri, Jan 04, 2008 at 11:57:09AM -0500, Dustin Henning wrote:
> 	I was reading an article about Windows PE 2.0 in virtual
> environments, and apparently Windows PE 2.0 is based on Vista, which doesn't
> have a driver for the default NIC used by VMWare.  The suggested solution is
> to use a different virtual NIC (a gigabit one).  Obviously Xen isn't VMWare,
> and on top of that, I am not trying to run Windows PE 2.0, or even Vista.
> However, I had long wondered but never asked this question:
> 	Does Xen have any virtual NICs other than the two mentioned in the
> hvm example files in /etc/xen?  More importantly, does it matter, for
> instance, will Xen or Windows limit the response time or throughput to
> 100MB/s levels in an hvm environment if a 100MB/s virtual NIC is used?  I
> don't see why it would, but then again, I don't see why SATAII hard drives
> running on controllers in IDE mode are slowed to IDE speeds, so I wouldn't
> be surprised if it did, and I am hoping someone can tell me.  Thanks,
> 	Dustin
> 

Xen HVM guests see _emulated_ hardware. Emulated NIC, Emulated ide/disk
controller, etc.

Emulation is slow. 

You need to have/install paravirtualized (=optimized) drivers that "bypass"
the whole emulation layer and talk directly to Xen.. this way you can get
good performance. 

Xen includes paravirtualized drivers ("unmodified drivers") for linux HVM
guests.

People are working with free/opensource paravirtualized drivers for Windows
HVM guests atm, but they're not really usable/stable yet.

XenEnterprise, VirtualIron, and Novell SLES have Windows HVM pv drivers
available.. if you buy those products. 

-- Pasi



From debian at herakles.homelinux.org  Sat Jan  5 02:00:52 2008
From: debian at herakles.homelinux.org (John Summerfield)
Date: Sat, 05 Jan 2008 11:00:52 +0900
Subject: [Fedora-xen] network speed on hvm guests
In-Reply-To: <20080104184911.GK17677@edu.joroinen.fi>
References: <20080104184911.GK17677@edu.joroinen.fi>
Message-ID: <477EE4D4.5060609@herakles.homelinux.org>

Pasi ? wrote:
> On Fri, Jan 04, 2008 at 11:57:09AM -0500, Dustin Henning wrote:
>> 	I was reading an article about Windows PE 2.0 in virtual
>> environments, and apparently Windows PE 2.0 is based on Vista, which doesn't
>> have a driver for the default NIC used by VMWare.  The suggested solution is
>> to use a different virtual NIC (a gigabit one).  Obviously Xen isn't VMWare,
>> and on top of that, I am not trying to run Windows PE 2.0, or even Vista.
>> However, I had long wondered but never asked this question:
>> 	Does Xen have any virtual NICs other than the two mentioned in the
>> hvm example files in /etc/xen?  More importantly, does it matter, for
>> instance, will Xen or Windows limit the response time or throughput to
>> 100MB/s levels in an hvm environment if a 100MB/s virtual NIC is used?  I
>> don't see why it would, but then again, I don't see why SATAII hard drives
>> running on controllers in IDE mode are slowed to IDE speeds, so I wouldn't
>> be surprised if it did, and I am hoping someone can tell me.  Thanks,
>> 	Dustin
>>
> 
> Xen HVM guests see _emulated_ hardware. Emulated NIC, Emulated ide/disk
> controller, etc.
> 
> Emulation is slow. 

Compared with hardware, yes. The bit that emulates hardware, yes. Expect 
the Windows driver to run full speed, it's when there's an interrupt to 
switch to the emulator that the rot sets in.

I would expect any emulated network device to go as fast as the hardware 
permits, and not to be constrained to any notion of the emulated 
device's speed. A real device is constrained by its need to talk to 
other hardware (electronic signal timing and such) whereas an emulated 
device is talking to more software.

A more complex device will be harder to emulate and so run slower.

-- 

Cheers
John

-- spambait
1aaaaaaa at coco.merseine.nu  Z1aaaaaaa at coco.merseine.nu
-- Advice
http://webfoot.com/advice/email.top.php
http://www.catb.org/~esr/faqs/smart-questions.html
http://support.microsoft.com/kb/555375

You cannot reply off-list:-)



From debian at herakles.homelinux.org  Sat Jan  5 02:05:33 2008
From: debian at herakles.homelinux.org (John Summerfield)
Date: Sat, 05 Jan 2008 11:05:33 +0900
Subject: [Fedora-xen] Are 64bit Intel Core 2 Quad fedora 8 supported?
In-Reply-To: <op.t4bby1c71nf74w@thosha.arxi.no>
References: <op.t3x88fq81nf74w@thosha.arxi.no>	<op.t4a6vdvx1nf74w@thosha.arxi.no>	<20080102153955.GC1237@redhat.com>
	<op.t4bby1c71nf74w@thosha.arxi.no>
Message-ID: <477EE5ED.4020205@herakles.homelinux.org>

George Refseth wrote:
> On Wed, 02 Jan 2008 16:39:55 +0100, Daniel P. Berrange 


>> I'm afraid the 2.6.21  series of kernel-xen will be the newest
>> we release for F-8 and earlier - its in bugfix only mode[1]. If there
>> is an easy bugfix we can do for 2.6.21 to make it work that's a
>> possiblity but we won't be doing .22 or .23 kernel-xen. I'd recommend
>> filing a BZ ticket with as many details of the problem you are seeing
>> as possible:
> 
> Thanks for a quick response, even if it doesn't really help me.
> The system also won't boot in i386 mode with the latest BIOS, so I will
> run non-virtualized 64 bit for testing purposes until you have a testable
> xen enabled kernel for -25 (?) available and forgo the bug report.

You could always try kvm.


-- 

Cheers
John

-- spambait
1aaaaaaa at coco.merseine.nu  Z1aaaaaaa at coco.merseine.nu
-- Advice
http://webfoot.com/advice/email.top.php
http://www.catb.org/~esr/faqs/smart-questions.html
http://support.microsoft.com/kb/555375

You cannot reply off-list:-)



From felix.schwarz at web.de  Sat Jan  5 13:57:07 2008
From: felix.schwarz at web.de (Felix Schwarz)
Date: Sat, 05 Jan 2008 14:57:07 +0100
Subject: [Fedora-xen] Re: Fedora 8 DomU (i386) does not work on Fedora 8
	(x86_64) host
In-Reply-To: <477BF5A9.9000600@web.de>
References: <477BF15B.1030901@web.de> <20080102202135.GF1237@redhat.com>
	<477BF5A9.9000600@web.de>
Message-ID: <477F8CB3.6040004@web.de>



Felix Schwarz wrote:
> This setup worked/works for every Fedora version since Core 5 so I'm 
> quite puzzled how to get further debug information...

Just a short follow-up: It turned out that my repodata was invalid, my 
baseurl was wrong. After regenerating the repodata (again), everything 
worked fine :-)

fs
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 3299 bytes
Desc: S/MIME Cryptographic Signature
URL: <http://listman.redhat.com/archives/fedora-xen/attachments/20080105/da2a8167/attachment.bin>

From pasik at iki.fi  Mon Jan  7 19:32:08 2008
From: pasik at iki.fi (Pasi =?iso-8859-1?Q?K=E4rkk=E4inen?=)
Date: Mon, 7 Jan 2008 21:32:08 +0200
Subject: [Fedora-xen] BUG: rawhide installer does not autoload xenblk/xennet
	modules
Message-ID: <20080107193208.GO17677@edu.joroinen.fi>

Hello!

I just tried to install rawhide/development to a xen domU with virt-manager,
and it seems current kernel (or xen drivers?) has a bug that prevents
anaconda/installer from autoloading the needed drivers.. 

virt-install -n test -r 512 --vcpus=1 -f /dev/vg0/test_disk1 --vnc -p -b xenbr0
-l "http://mirror/fedora.redhat.com/pub/fedora/linux/development/i386/os"

starts up the console/vnc window, boots up linux and the installer, lets me
choose language and keyboard type, and then says:

"No driver found"
"Unable to find any devices of the type needed for this installation type."
"Would you like to manually select your driver or use a driver disk?"

And at the moment anaconda is broken for manually picking drivers, so
installation doesn't work at all when using xen :) (this is a separate bug)

-- Pasi



From jack.delbert at gmail.com  Tue Jan  8 03:39:46 2008
From: jack.delbert at gmail.com (Jack Smith)
Date: Mon, 7 Jan 2008 22:39:46 -0500
Subject: [Fedora-xen] Routing doesn't work when I boot with the Xen kernel
Message-ID: <ed5bd5f20801071939p6b3af543w71f3bf31944789e2@mail.gmail.com>

I have a choice of kernels to boot with in Grub,
2.6.21-2952.fc8xen
2.6.23.9-85.fc8
2.6.23.1-42.fc8

As far as I can see, I have networking set up the same on all three.
(Besides, wouldn't they use the same configuration files at boot time?)  My
problem is, when I boot with the xen kernel, I can't get out through my
router.  I can ping everything on my eth0 or eth1 networks, just not go
through my eth0 Linksys router.  The only difference I've been able to see
is that something called "peth0" uses the same card as the NIC my router is
on.  Is this getting in the way somehow?

 eth0 Link encap:Ethernet HWaddr 00:17:31:01:C8:A8

inet addr:192.168.1.151 Bcast:192.168.1.255 Mask:255.255.255.0

inet6 addr: fe80::217:31ff:fe01:c8a8/64 Scope:Link

UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1

RX packets:10 errors:0 dropped:0 overruns:0 frame:0

TX packets:47 errors:0 dropped:0 overruns:0 carrier:0

collisions:0 txqueuelen:0

RX bytes:494 (494.0 b) TX bytes:6566 (6.4 KiB)


 eth1 Link encap:Ethernet HWaddr 00:17:31:01:D0:20

inet addr:192.168.0.3 Bcast:192.168.0.255 Mask:255.255.255.0

inet6 addr: fe80::217:31ff:fe01:d020/64 Scope:Link

UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1

RX packets:29 errors:0 dropped:0 overruns:0 frame:0

TX packets:63 errors:0 dropped:0 overruns:0 carrier:0

collisions:0 txqueuelen:1000

RX bytes:2412 (2.3 KiB) TX bytes:8491 (8.2 KiB)

Interrupt:23 Base address:0xe000


 lo Link encap:Local Loopback

inet addr:127.0.0.1 Mask:255.0.0.0

inet6 addr: ::1/128 Scope:Host

UP LOOPBACK RUNNING MTU:16436 Metric:1

RX packets:8504 errors:0 dropped:0 overruns:0 frame:0

TX packets:8504 errors:0 dropped:0 overruns:0 carrier:0

collisions:0 txqueuelen:0

RX bytes:10008668 (9.5 MiB) TX bytes:10008668 (9.5 MiB)


 peth0 Link encap:Ethernet HWaddr 00:17:31:01:C8:A8

inet6 addr: fe80::217:31ff:fe01:c8a8/64 Scope:Link

UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1

RX packets:53 errors:0 dropped:0 overruns:0 frame:0

TX packets:121 errors:0 dropped:0 overruns:0 carrier:0

collisions:0 txqueuelen:1000

RX bytes:5414 (5.2 KiB) TX bytes:14547 (14.2 KiB)

Interrupt:18


 virbr0 Link encap:Ethernet HWaddr 00:00:00:00:00:00

inet addr:192.168.122.1 Bcast:192.168.122.255 Mask:255.255.255.0

inet6 addr: fe80::200:ff:fe00:0/64 Scope:Link

UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1

RX packets:0 errors:0 dropped:0 overruns:0 frame:0

TX packets:32 errors:0 dropped:0 overruns:0 carrier:0

collisions:0 txqueuelen:0

RX bytes:0 (0.0 b) TX bytes:5156 (5.0 KiB)


 Thanks,

-- 
Jack Smith

English doesn't borrow from other languages -- English follows other
languages down dark alleys and takes what it wants.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/fedora-xen/attachments/20080107/4eac948d/attachment.htm>

From debian at herakles.homelinux.org  Tue Jan  8 06:56:30 2008
From: debian at herakles.homelinux.org (John Summerfield)
Date: Tue, 08 Jan 2008 15:56:30 +0900
Subject: [Fedora-xen] Routing doesn't work when I boot with the Xen kernel
In-Reply-To: <ed5bd5f20801071939p6b3af543w71f3bf31944789e2@mail.gmail.com>
References: <ed5bd5f20801071939p6b3af543w71f3bf31944789e2@mail.gmail.com>
Message-ID: <47831E9E.9000205@herakles.homelinux.org>

Jack Smith wrote:
> I have a choice of kernels to boot with in Grub,
> 2.6.21-2952.fc8xen
> 2.6.23.9-85.fc8
> 2.6.23.1-42.fc8
> 
> As far as I can see, I have networking set up the same on all three.
> (Besides, wouldn't they use the same configuration files at boot time?)  My
> problem is, when I boot with the xen kernel, I can't get out through my
> router.  I can ping everything on my eth0 or eth1 networks, just not go
> through my eth0 Linksys router.  The only difference I've been able to see
> is that something called "peth0" uses the same card as the NIC my router is
> on.  Is this getting in the way somehow?
> 
>  eth0 Link encap:Ethernet HWaddr 00:17:31:01:C8:A8
>

Check that the NICs are both connected to the same wire with the 
different kernels. if I read it correctly, they're both the same brand. 
Maybe the kernels detect them differently.

Unplug one, test with ethtool:
sudo ethtool eth0

Find and inspect the configuration files:
[summer at potoroo ~]$ locate ifcfg-eth
/etc/sysconfig/network-scripts/ifcfg-eth0
[summer at potoroo ~]$ cat /etc/sysconfig/network-scripts/ifcfg-eth0
# Intel Corporation 82566DM Gigabit Network Connection
DEVICE=eth0
BOOTPROTO=dhcp
HWADDR=00:18:71:84:A5:9E
ONBOOT=yes
[summer at potoroo ~]$

The HWADDR line ties the MAC address to the interface configuration, but 
I've never had the need to explore how it works, and I can imagine some 
different ways.



-- 

Cheers
John

-- spambait
1aaaaaaa at coco.merseine.nu  Z1aaaaaaa at coco.merseine.nu
-- Advice
http://webfoot.com/advice/email.top.php
http://www.catb.org/~esr/faqs/smart-questions.html
http://support.microsoft.com/kb/555375

You cannot reply off-list:-)



From george.refseth at arxi.no  Tue Jan  8 12:45:34 2008
From: george.refseth at arxi.no (George Refseth)
Date: Tue, 08 Jan 2008 13:45:34 +0100
Subject: [Fedora-xen] Are 64bit Intel Core 2 Quad fedora 8 supported?
In-Reply-To: <477BCF5F.9050208@cyconix.com>
References: <op.t3x88fq81nf74w@thosha.arxi.no> <477BCF5F.9050208@cyconix.com>
Message-ID: <op.t4brgjxb1nf74w@thosha.arxi.no>

On Wed, 02 Jan 2008 18:52:31 +0100, Evan Lavelle <sa212+fcxen at cyconix.com>  
wrote:

> George Refseth wrote:
>> The 64 bit xen host kernel are unstable (timer/scheduling issue?)
>>  So I wonder if this is supported or not. Another Fedora 8 x86_64  
>> installation on
>> an Intel Core 2 Duo seems to run flawlessly, except it is running on a  
>> laptop,
>> and not meant for server use.
>
> FWIW: I'm running F8 64-bit 2.6.21-2952, for both Dom0 and one DomU, on  
> 6600/Core 2 Duo, without problems. The DomU is HVM; it was originally PV  
> but I gave up on that for complex reasons. Various other (non-Fedora)  
> HVM domU's also work without problems.
>
> Maybe it's just an issue with quad core.

Seems to be, or the motherboard and BIOS state at time of boot, except that
I expected the OS to take over not expect any state of the BIOS. I also  
have
no problem running a a new ASUS C90S Laptop with Core 2 Duo, both i386 and  
x86,
  both xen variant (.21-) and non-xen the released and the updated kernels  
(.23.1-42
& 23.9-85). I will continue experimenting on the laptop to prepare for  
virt. on
the server when it can support mother-board and cpu.

> Can you turn off two cores in the BIOS?
>

Not that I can figure out, the BIOS seems to expect the OS to take charge.

George



-- 
Using Opera's revolutionary e-mail client: http://www.opera.com/mail/



From Dustin.Henning at prd-inc.com  Tue Jan  8 13:21:19 2008
From: Dustin.Henning at prd-inc.com (Dustin Henning)
Date: Tue, 8 Jan 2008 08:21:19 -0500
Subject: [Fedora-xen] Routing doesn't work when I boot with the Xen kernel
In-Reply-To: <ed5bd5f20801071939p6b3af543w71f3bf31944789e2@mail.gmail.com>
References: <ed5bd5f20801071939p6b3af543w71f3bf31944789e2@mail.gmail.com>
Message-ID: <002401c851f9$5ae0fd20$10a2f760$@Henning@prd-inc.com>

       When the xend service starts, it creates bridges and virtual
interfaces attached to those bridges.  I am not so familiar with it to tell
you how to correct your problem on a permanent basis, but I can tell you
that perhaps the network script isn?t preserving your routes.  Check your
routes and see if a default route to the Linksys still exists.  It also
seems to me like F8 may use a different default xen network script, so
depending on what you want to do, you many need to change the network script
in xen?s config file.  This advice may be legacy, as I know Fedora?s
implementation gets more and more custom with each release, and I generally
fall back on old xen configuration techniques in spite of that, so this may
not be the route you want to take.
       Dustin

From: fedora-xen-bounces at redhat.com [mailto:fedora-xen-bounces at redhat.com]
On Behalf Of Jack Smith
Sent: Monday, January 07, 2008 22:40
To: fedora-xen at redhat.com
Subject: [Fedora-xen] Routing doesn't work when I boot with the Xen kernel

I have a choice of kernels to boot with in Grub,
2.6.21-2952.fc8xen
2.6.23.9-85.fc8
2.6.23.1-42.fc8

As far as I can see, I have networking set up the same on all three.?
(Besides, wouldn't they use the same configuration files at boot time?)? My
problem is, when I boot with the xen kernel, I can't get out through my
router.? I can ping everything on my eth0 or eth1 networks, just not go
through my eth0 Linksys router.? The only difference I've been able to see
is that something called "peth0" uses the same card as the NIC my router is
on.? Is this getting in the way somehow? 
eth0 Link encap:Ethernet HWaddr 00:17:31:01:C8:A8 
inet addr:192.168.1.151 Bcast:192.168.1.255 Mask:255.255.255.0 
inet6 addr: fe80::217:31ff:fe01:c8a8/64 Scope:Link 
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 
RX packets:10 errors:0 dropped:0 overruns:0 frame:0 
TX packets:47 errors:0 dropped:0 overruns:0 carrier:0 
collisions:0 txqueuelen:0 
RX bytes:494 (494.0 b) TX bytes:6566 (6.4 KiB) 

eth1 Link encap:Ethernet HWaddr 00:17:31:01:D0:20 
inet addr:192.168.0.3 Bcast:192.168.0.255 Mask:255.255.255.0 
inet6 addr: fe80::217:31ff:fe01:d020/64 Scope:Link 
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 
RX packets:29 errors:0 dropped:0 overruns:0 frame:0 
TX packets:63 errors:0 dropped:0 overruns:0 carrier:0 
collisions:0 txqueuelen:1000 
RX bytes:2412 (2.3 KiB) TX bytes:8491 (8.2 KiB) 
Interrupt:23 Base address:0xe000 

lo Link encap:Local Loopback 
inet addr:127.0.0.1 Mask:255.0.0.0 
inet6 addr: ::1/128 Scope:Host 
UP LOOPBACK RUNNING MTU:16436 Metric:1 
RX packets:8504 errors:0 dropped:0 overruns:0 frame:0 
TX packets:8504 errors:0 dropped:0 overruns:0 carrier:0 
collisions:0 txqueuelen:0 
RX bytes:10008668 (9.5 MiB) TX bytes:10008668 (9.5 MiB) 

peth0 Link encap:Ethernet HWaddr 00:17:31:01:C8:A8 
inet6 addr: fe80::217:31ff:fe01:c8a8/64 Scope:Link 
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 
RX packets:53 errors:0 dropped:0 overruns:0 frame:0 
TX packets:121 errors:0 dropped:0 overruns:0 carrier:0 
collisions:0 txqueuelen:1000 
RX bytes:5414 (5.2 KiB) TX bytes:14547 (14.2 KiB) 
Interrupt:18 

virbr0 Link encap:Ethernet HWaddr 00:00:00:00:00:00 
inet addr:192.168.122.1 Bcast:192.168.122.255 Mask:255.255.255.0 
inet6 addr: fe80::200:ff:fe00:0/64 Scope:Link 
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 
RX packets:0 errors:0 dropped:0 overruns:0 frame:0 
TX packets:32 errors:0 dropped:0 overruns:0 carrier:0 
collisions:0 txqueuelen:0 
RX bytes:0 (0.0 b) TX bytes:5156 (5.0 KiB) 

Thanks,

-- 
Jack Smith

English doesn't borrow from other languages -- English follows other
languages down dark alleys and takes what it wants. 





From jack.delbert at gmail.com  Tue Jan  8 14:27:48 2008
From: jack.delbert at gmail.com (Jack Smith)
Date: Tue, 8 Jan 2008 09:27:48 -0500
Subject: [Fedora-xen] Routing doesn't work when I boot with the Xen kernel
In-Reply-To: <-6439599617781698639@unknownmsgid>
References: <ed5bd5f20801071939p6b3af543w71f3bf31944789e2@mail.gmail.com>
	<-6439599617781698639@unknownmsgid>
Message-ID: <ed5bd5f20801080627v2204fad7yd01ce8db10c2924d@mail.gmail.com>

I have no idea why, but the problem corrected itself overnight.  Something,
either in Fedora, the router, Comcast or somewhere must have run and fixed
the problem.  I have no idea how.

On Jan 8, 2008 8:21 AM, Dustin Henning <Dustin.Henning at prd-inc.com> wrote:

>       When the xend service starts, it creates bridges and virtual
> interfaces attached to those bridges.  I am not so familiar with it to
> tell
> you how to correct your problem on a permanent basis, but I can tell you
> that perhaps the network script isn't preserving your routes.  Check your
> routes and see if a default route to the Linksys still exists.  It also
> seems to me like F8 may use a different default xen network script, so
> depending on what you want to do, you many need to change the network
> script
> in xen's config file.  This advice may be legacy, as I know Fedora's
> implementation gets more and more custom with each release, and I
> generally
> fall back on old xen configuration techniques in spite of that, so this
> may
> not be the route you want to take.
>       Dustin
>
> From: fedora-xen-bounces at redhat.com [mailto:fedora-xen-bounces at redhat.com]
> On Behalf Of Jack Smith
> Sent: Monday, January 07, 2008 22:40
> To: fedora-xen at redhat.com
> Subject: [Fedora-xen] Routing doesn't work when I boot with the Xen kernel
>
> I have a choice of kernels to boot with in Grub,
> 2.6.21-2952.fc8xen
> 2.6.23.9-85.fc8
> 2.6.23.1-42.fc8
>
> As far as I can see, I have networking set up the same on all three.
> (Besides, wouldn't they use the same configuration files at boot time?) My
> problem is, when I boot with the xen kernel, I can't get out through my
> router. I can ping everything on my eth0 or eth1 networks, just not go
> through my eth0 Linksys router. The only difference I've been able to see
> is that something called "peth0" uses the same card as the NIC my router
> is
> on. Is this getting in the way somehow?
> eth0 Link encap:Ethernet HWaddr 00:17:31:01:C8:A8
> inet addr:192.168.1.151 Bcast:192.168.1.255 Mask:255.255.255.0
> inet6 addr: fe80::217:31ff:fe01:c8a8/64 Scope:Link
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:10 errors:0 dropped:0 overruns:0 frame:0
> TX packets:47 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:0
> RX bytes:494 (494.0 b) TX bytes:6566 (6.4 KiB)
>
> eth1 Link encap:Ethernet HWaddr 00:17:31:01:D0:20
> inet addr:192.168.0.3 Bcast:192.168.0.255 Mask:255.255.255.0
> inet6 addr: fe80::217:31ff:fe01:d020/64 Scope:Link
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:29 errors:0 dropped:0 overruns:0 frame:0
> TX packets:63 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:1000
> RX bytes:2412 (2.3 KiB) TX bytes:8491 (8.2 KiB)
> Interrupt:23 Base address:0xe000
>
> lo Link encap:Local Loopback
> inet addr:127.0.0.1 Mask:255.0.0.0
> inet6 addr: ::1/128 Scope:Host
> UP LOOPBACK RUNNING MTU:16436 Metric:1
> RX packets:8504 errors:0 dropped:0 overruns:0 frame:0
> TX packets:8504 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:0
> RX bytes:10008668 (9.5 MiB) TX bytes:10008668 (9.5 MiB)
>
> peth0 Link encap:Ethernet HWaddr 00:17:31:01:C8:A8
> inet6 addr: fe80::217:31ff:fe01:c8a8/64 Scope:Link
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:53 errors:0 dropped:0 overruns:0 frame:0
> TX packets:121 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:1000
> RX bytes:5414 (5.2 KiB) TX bytes:14547 (14.2 KiB)
> Interrupt:18
>
> virbr0 Link encap:Ethernet HWaddr 00:00:00:00:00:00
> inet addr:192.168.122.1 Bcast:192.168.122.255 Mask:255.255.255.0
> inet6 addr: fe80::200:ff:fe00:0/64 Scope:Link
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:0 errors:0 dropped:0 overruns:0 frame:0
> TX packets:32 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:0
> RX bytes:0 (0.0 b) TX bytes:5156 (5.0 KiB)
>
> Thanks,
>
> --
> Jack Smith
>
> English doesn't borrow from other languages -- English follows other
> languages down dark alleys and takes what it wants.
>
>
>


-- 
Jack Smith

English doesn't borrow from other languages -- English follows other
languages down dark alleys and takes what it wants.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/fedora-xen/attachments/20080108/12856c6b/attachment.htm>

From jack.delbert at gmail.com  Tue Jan  8 14:34:59 2008
From: jack.delbert at gmail.com (Jack Smith)
Date: Tue, 8 Jan 2008 09:34:59 -0500
Subject: [Fedora-xen] Ignore problem with hypervisor not running
Message-ID: <ed5bd5f20801080634t3857d52u760a4d31d5d2e7ea@mail.gmail.com>

Yesterday I sent a message that the hypervisor wasn't running on my system.
It is; I just get errors when I run "virsh list" without being root.  Sorry.

[kizoku at natsumi ~]$ virsh list
libvir: Xen Daemon error : internal error failed to connect to xend
libvir: Xen Daemon error : got unknown HTTP error code 0
 Id Name                 State
----------------------------------
  0 Domain-0             running

[kizoku at natsumi ~]$ sudo virsh list
Password:
 Id Name                 State
----------------------------------
  0 Domain-0             running



-- 
Jack Smith

English doesn't borrow from other languages -- English follows other
languages down dark alleys and takes what it wants.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/fedora-xen/attachments/20080108/6e64e944/attachment.htm>

From profosslists at gmail.com  Tue Jan  8 15:44:47 2008
From: profosslists at gmail.com (=?ISO-8859-1?Q?Rapha=EBl_Bauduin?=)
Date: Tue, 8 Jan 2008 16:44:47 +0100
Subject: [Fedora-xen] virtualisation conference
Message-ID: <6d9aab700801080744o399fe9a3wca2f5cf3afe50195@mail.gmail.com>

Hi all,

Profoss (http://www.profoss.eu) is organising a European
virtualisation conference on
22 and 23 january in Brussels. Xen will of course be part of the
talks. Speakers related
to Xen directly are Kris Buytaert, co-author of "Virtualization with
Xen", and Frank Kohler,
who will talk of integration of virtualisation in the operating system.

Talks are not commercial but really informative. The first day is
looking at business
aspect of virtualisation, the second day looks at technical aspects.

All info about the event is at http://www.profoss.eu/events/

Participation costs are really affordable, so I hope to see you there!

Raph



From jack.delbert at gmail.com  Tue Jan  8 17:54:41 2008
From: jack.delbert at gmail.com (Jack Smith)
Date: Tue, 8 Jan 2008 12:54:41 -0500
Subject: [Fedora-xen] [kizoku@natsumi ~]$ virsh list libvir: Xen Daemon
	error : internal error failed to connect to xend libvir: Xen
	Daemon error : got unknown HTTP error code 0 Id Name State
	---------------------------------- 0 Domain-0 running
	[kizoku@natsumi ~]$ sudo v
Message-ID: <ed5bd5f20801080954r3c14c45nd9efa16cec94b423@mail.gmail.com>

I'm trying to set up a virtual machine running Windows XP.  I'm running
Fedora 8 version 2.6.21-2952.fc8xen virt-manager.py 0.5.2

Paravirtualized
install media url  is /dev/scd0
my normal disk partition is /dev/VolGroup00/LogVol03
there is no file system on the logical volume and it is not mounted
I chose peth0(bridged) as my physical device
I have two NICs, eth0 and eth1, if it matters
500 MB and 1 virtual CPU
when I click Finish, I get

Unable to complete install '<type 'exceptions.ValueError'> Invalid file
location given: No such file or directory
Traceback (most recent call last):
  File "/usr/share/virt-manager/virtManager/create.py", line 616, in
do_install
    dom = guest.start_install(False, meter = meter)
  File "/usr/lib/python2.5/site-packages/virtinst/Guest.py", line 722, in
start_install
    self._prepare_install(meter)
  File "/usr/lib/python2.5/site-packages/virtinst/ParaVirtGuest.py", line
48, in _prepare_install
    self._installer.prepare(guest = self, meter = meter)
  File "/usr/lib/python2.5/site-packages/virtinst/DistroManager.py", line
681, in prepare
    self._prepare_kernel_and_initrd(guest, distro, meter)
  File "/usr/lib/python2.5/site-packages/virtinst/DistroManager.py", line
651, in _prepare_kernel_and_initrd
    distro = distro)
  File "/usr/lib/python2.5/site-packages/virtinst/DistroManager.py", line
581, in acquireKernel
    progresscb=progresscb, distro=distro, scratchdir=scratchdir)
  File "/usr/lib/python2.5/site-packages/virtinst/DistroManager.py", line
564, in _storeForDistro
    if store.isValidStore(fetcher, progresscb):
  File "/usr/lib/python2.5/site-packages/virtinst/DistroManager.py", line
445, in isValidStore
    ignore = fetcher.acquireFile("directory.yast", progresscb)
  File "/usr/lib/python2.5/site-packages/virtinst/DistroManager.py", line
150, in acquireFile
    raise ValueError, _("Invalid file location given: ") + msg
ValueError: Invalid file location given: No such file or directory
'

Any idea what is going on?  All I can find online is something about this
being a bug in Fedora 7

Thanks,

-- 
Jack Smith

English doesn't borrow from other languages -- English follows other
languages down dark alleys and takes what it wants.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/fedora-xen/attachments/20080108/14d74455/attachment.htm>

From jack.delbert at gmail.com  Tue Jan  8 17:56:36 2008
From: jack.delbert at gmail.com (Jack Smith)
Date: Tue, 8 Jan 2008 12:56:36 -0500
Subject: [Fedora-xen] Invalid file location given
Message-ID: <ed5bd5f20801080956q6dcfc17fw5235c47b310cd49@mail.gmail.com>

I'm trying to set up a virtual machine running Windows XP.  I'm running
Fedora 8 version 2.6.21-2952.fc8xen virt-manager.py 0.5.2

Paravirtualized
install media url  is /dev/scd0
my normal disk partition is /dev/VolGroup00/LogVol03
there is no file system on the logical volume and it is not mounted
I chose peth0(bridged) as my physical device
I have two NICs, eth0 and eth1, if it matters
500 MB and 1 virtual CPU
when I click Finish, I get

Unable to complete install '<type 'exceptions.ValueError'> Invalid file
location given: No such file or directory
Traceback (most recent call last):
  File "/usr/share/virt-manager/virtManager/create.py", line 616, in
do_install
    dom = guest.start_install(False, meter = meter)
  File "/usr/lib/python2.5/site-packages/virtinst/Guest.py", line 722, in
start_install
    self._prepare_install(meter)
  File "/usr/lib/python2.5/site-packages/virtinst/ParaVirtGuest.py", line
48, in _prepare_install
    self._installer.prepare(guest = self, meter = meter)
  File "/usr/lib/python2.5/site-packages/virtinst/DistroManager.py", line
681, in prepare
    self._prepare_kernel_and_initrd(guest, distro, meter)
  File "/usr/lib/python2.5/site-packages/virtinst/DistroManager.py", line
651, in _prepare_kernel_and_initrd
    distro = distro)
  File "/usr/lib/python2.5/site-packages/virtinst/DistroManager.py", line
581, in acquireKernel
    progresscb=progresscb, distro=distro, scratchdir=scratchdir)
  File "/usr/lib/python2.5/site-packages/virtinst/DistroManager.py", line
564, in _storeForDistro
    if store.isValidStore(fetcher, progresscb):
  File "/usr/lib/python2.5/site-packages/virtinst/DistroManager.py", line
445, in isValidStore
    ignore = fetcher.acquireFile("directory.yast", progresscb)
  File "/usr/lib/python2.5/site-packages/virtinst/DistroManager.py", line
150, in acquireFile
    raise ValueError, _("Invalid file location given: ") + msg
ValueError: Invalid file location given: No such file or directory
'

Any idea what is going on?  All I can find online is something about this
being a bug in Fedora 7

Thanks,


-- 
Jack Smith

English doesn't borrow from other languages -- English follows other
languages down dark alleys and takes what it wants.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/fedora-xen/attachments/20080108/36ee24a4/attachment.htm>

From jack.delbert at gmail.com  Tue Jan  8 20:06:21 2008
From: jack.delbert at gmail.com (Jack Smith)
Date: Tue, 8 Jan 2008 15:06:21 -0500
Subject: [Fedora-xen] Re: Invalid file location given
In-Reply-To: <ed5bd5f20801080956q6dcfc17fw5235c47b310cd49@mail.gmail.com>
References: <ed5bd5f20801080956q6dcfc17fw5235c47b310cd49@mail.gmail.com>
Message-ID: <ed5bd5f20801081206u7a925c17hde92c6afa7cfd293@mail.gmail.com>

FYI, I'm running xen 3.1.2-1.fc8.x86_64

On Jan 8, 2008 12:56 PM, Jack Smith <jack.delbert at gmail.com> wrote:

> I'm trying to set up a virtual machine running Windows XP.  I'm running
> Fedora 8 version 2.6.21-2952.fc8xen virt-manager.py 0.5.2
>
> Paravirtualized
> install media url  is /dev/scd0
> my normal disk partition is /dev/VolGroup00/LogVol03
> there is no file system on the logical volume and it is not mounted
> I chose peth0(bridged) as my physical device
> I have two NICs, eth0 and eth1, if it matters
> 500 MB and 1 virtual CPU
> when I click Finish, I get
>
> Unable to complete install '<type 'exceptions.ValueError'> Invalid file
> location given: No such file or directory
> Traceback (most recent call last):
>   File "/usr/share/virt-manager /virtManager/create.py", line 616, in
> do_install
>     dom = guest.start_install(False, meter = meter)
>   File "/usr/lib/python2.5/site-packages/virtinst/Guest.py", line 722, in
> start_install
>     self._prepare_install(meter)
>   File "/usr/lib/python2.5/site-packages/virtinst/ParaVirtGuest.py", line
> 48, in _prepare_install
>     self._installer.prepare(guest = self, meter = meter)
>   File "/usr/lib/python2.5/site-packages/virtinst/DistroManager.py", line
> 681, in prepare
>     self._prepare_kernel_and_initrd(guest, distro, meter)
>   File "/usr/lib/python2.5/site-packages/virtinst/DistroManager.py", line
> 651, in _prepare_kernel_and_initrd
>     distro = distro)
>   File "/usr/lib/python2.5/site-packages/virtinst/DistroManager.py", line
> 581, in acquireKernel
>     progresscb=progresscb, distro=distro, scratchdir=scratchdir)
>   File "/usr/lib/python2.5/site-packages/virtinst/DistroManager.py", line
> 564, in _storeForDistro
>     if store.isValidStore(fetcher, progresscb):
>   File "/usr/lib/python2.5/site-packages/virtinst/DistroManager.py", line
> 445, in isValidStore
>     ignore = fetcher.acquireFile("directory.yast", progresscb)
>   File "/usr/lib/python2.5/site-packages/virtinst/DistroManager.py", line
> 150, in acquireFile
>     raise ValueError, _("Invalid file location given: ") + msg
> ValueError: Invalid file location given: No such file or directory
> '
>
> Any idea what is going on?  All I can find online is something about this
> being a bug in Fedora 7
>
> Thanks,
>
>
> --
> Jack Smith
>
> English doesn't borrow from other languages -- English follows other
> languages down dark alleys and takes what it wants.




-- 
Jack Smith

English doesn't borrow from other languages -- English follows other
languages down dark alleys and takes what it wants.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/fedora-xen/attachments/20080108/9fe31692/attachment.htm>

From jack.delbert at gmail.com  Tue Jan  8 21:52:29 2008
From: jack.delbert at gmail.com (Jack Smith)
Date: Tue, 8 Jan 2008 16:52:29 -0500
Subject: [Fedora-xen] Re: Invalid file location given
In-Reply-To: <ed5bd5f20801081206u7a925c17hde92c6afa7cfd293@mail.gmail.com>
References: <ed5bd5f20801080956q6dcfc17fw5235c47b310cd49@mail.gmail.com>
	<ed5bd5f20801081206u7a925c17hde92c6afa7cfd293@mail.gmail.com>
Message-ID: <ed5bd5f20801081352y7c6b353ax7094e3f68a6330db@mail.gmail.com>

I've also tried copying the install CD to my Apache server in
/var/www/html/XP and giving the install URL as
http://68.42.182.214/XP
http://localhost/XP
http://localhost/XP/
http://localhost/XP/VRMHFPP_EN.iso

All of which work in my Firefox browser and all of which give me
invalid URL location here.

On Jan 8, 2008 3:06 PM, Jack Smith <jack.delbert at gmail.com> wrote:

> FYI, I'm running xen 3.1.2-1.fc8.x86_64
>
>
> On Jan 8, 2008 12:56 PM, Jack Smith <jack.delbert at gmail.com> wrote:
>
> > I'm trying to set up a virtual machine running Windows XP.  I'm running
> > Fedora 8 version 2.6.21-2952.fc8xen virt-manager.py 0.5.2
> >
> > Paravirtualized
> > install media url  is /dev/scd0
> > my normal disk partition is /dev/VolGroup00/LogVol03
> > there is no file system on the logical volume and it is not mounted
> > I chose peth0(bridged) as my physical device
> > I have two NICs, eth0 and eth1, if it matters
> > 500 MB and 1 virtual CPU
> > when I click Finish, I get
> >
> > Unable to complete install '<type 'exceptions.ValueError'> Invalid file
> > location given: No such file or directory
> > Traceback (most recent call last):
> >   File "/usr/share/virt-manager /virtManager/create.py", line 616, in
> > do_install
> >     dom = guest.start_install(False, meter = meter)
> >   File "/usr/lib/python2.5/site-packages/virtinst/Guest.py", line 722,
> > in start_install
> >     self._prepare_install(meter)
> >   File "/usr/lib/python2.5/site-packages/virtinst/ParaVirtGuest.py",
> > line 48, in _prepare_install
> >     self._installer.prepare(guest = self, meter = meter)
> >   File "/usr/lib/python2.5/site-packages/virtinst/DistroManager.py",
> > line 681, in prepare
> >     self._prepare_kernel_and_initrd(guest, distro, meter)
> >   File "/usr/lib/python2.5/site-packages/virtinst/DistroManager.py",
> > line 651, in _prepare_kernel_and_initrd
> >     distro = distro)
> >   File "/usr/lib/python2.5/site-packages/virtinst/DistroManager.py",
> > line 581, in acquireKernel
> >     progresscb=progresscb, distro=distro, scratchdir=scratchdir)
> >   File "/usr/lib/python2.5/site-packages/virtinst/DistroManager.py",
> > line 564, in _storeForDistro
> >     if store.isValidStore(fetcher, progresscb):
> >   File "/usr/lib/python2.5/site-packages/virtinst/DistroManager.py",
> > line 445, in isValidStore
> >     ignore = fetcher.acquireFile("directory.yast", progresscb)
> >   File "/usr/lib/python2.5/site-packages/virtinst/DistroManager.py",
> > line 150, in acquireFile
> >     raise ValueError, _("Invalid file location given: ") + msg
> > ValueError: Invalid file location given: No such file or directory
> > '
> >
> > Any idea what is going on?  All I can find online is something about
> > this being a bug in Fedora 7
> >
> > Thanks,
> >
> >
> > --
> > Jack Smith
> >
> > English doesn't borrow from other languages -- English follows other
> > languages down dark alleys and takes what it wants.
>
>
>
>
> --
> Jack Smith
>
> English doesn't borrow from other languages -- English follows other
> languages down dark alleys and takes what it wants.
>



-- 
Jack Smith

English doesn't borrow from other languages -- English follows other
languages down dark alleys and takes what it wants.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/fedora-xen/attachments/20080108/a3b1a03c/attachment.htm>

From debian at herakles.homelinux.org  Tue Jan  8 23:09:31 2008
From: debian at herakles.homelinux.org (John Summerfield)
Date: Wed, 09 Jan 2008 08:09:31 +0900
Subject: [Fedora-xen] [kizoku@natsumi ~]$ virsh list libvir: Xen Daemon
	error : internal error failed to connect to xend libvir: Xen	Daemon
	error : got unknown HTTP error code 0 Id Name
	State	----------------------------------
	0 Domain-0 running	[kizoku@natsumi ~]$ sudo v
In-Reply-To: <ed5bd5f20801080954r3c14c45nd9efa16cec94b423@mail.gmail.com>
References: <ed5bd5f20801080954r3c14c45nd9efa16cec94b423@mail.gmail.com>
Message-ID: <478402AB.1050505@herakles.homelinux.org>

Jack Smith wrote:
Jack
Please use the subject line for a _short_ summary of what you're talking 
about. That's longer than I can easily see in Seamonkey.

> I'm trying to set up a virtual machine running Windows XP.  I'm running
> Fedora 8 version 2.6.21-2952.fc8xen virt-manager.py 0.5.2
> 
> Paravirtualized

Has to be fully virtualised, xen does not support unmodified kernels 
otherwise.




-- 

Cheers
John

-- spambait
1aaaaaaa at coco.merseine.nu  Z1aaaaaaa at coco.merseine.nu
-- Advice
http://webfoot.com/advice/email.top.php
http://www.catb.org/~esr/faqs/smart-questions.html
http://support.microsoft.com/kb/555375

You cannot reply off-list:-)



From debian at herakles.homelinux.org  Tue Jan  8 23:11:34 2008
From: debian at herakles.homelinux.org (John Summerfield)
Date: Wed, 09 Jan 2008 08:11:34 +0900
Subject: [Fedora-xen] Re: Invalid file location given
In-Reply-To: <ed5bd5f20801081352y7c6b353ax7094e3f68a6330db@mail.gmail.com>
References: <ed5bd5f20801080956q6dcfc17fw5235c47b310cd49@mail.gmail.com>	<ed5bd5f20801081206u7a925c17hde92c6afa7cfd293@mail.gmail.com>
	<ed5bd5f20801081352y7c6b353ax7094e3f68a6330db@mail.gmail.com>
Message-ID: <47840326.8090100@herakles.homelinux.org>

Jack Smith wrote:
> I've also tried copying the install CD to my Apache server in
> /var/www/html/XP and giving the install URL as
> http://68.42.182.214/XP
> http://localhost/XP
> http://localhost/XP/
> http://localhost/XP/VRMHFPP_EN.iso

and none of which Windows supports. Best learn to install Windows on 
real hardware;-)


-- 

Cheers
John

-- spambait
1aaaaaaa at coco.merseine.nu  Z1aaaaaaa at coco.merseine.nu
-- Advice
http://webfoot.com/advice/email.top.php
http://www.catb.org/~esr/faqs/smart-questions.html
http://support.microsoft.com/kb/555375

You cannot reply off-list:-)



From jack.delbert at gmail.com  Tue Jan  8 23:20:08 2008
From: jack.delbert at gmail.com (Jack Smith)
Date: Tue, 8 Jan 2008 18:20:08 -0500
Subject: [Fedora-xen] Re: Invalid file location given
In-Reply-To: <47840326.8090100@herakles.homelinux.org>
References: <ed5bd5f20801080956q6dcfc17fw5235c47b310cd49@mail.gmail.com>
	<ed5bd5f20801081206u7a925c17hde92c6afa7cfd293@mail.gmail.com>
	<ed5bd5f20801081352y7c6b353ax7094e3f68a6330db@mail.gmail.com>
	<47840326.8090100@herakles.homelinux.org>
Message-ID: <ed5bd5f20801081520l26b3f5djc65072c47ce4d6ea@mail.gmail.com>

On Jan 8, 2008 6:11 PM, John Summerfield <debian at herakles.homelinux.org>
wrote:

> Jack Smith wrote:
> > I've also tried copying the install CD to my Apache server in
> > /var/www/html/XP and giving the install URL as
> > http://68.42.182.214/XP
> > http://localhost/XP
> > http://localhost/XP/
> > http://localhost/XP/VRMHFPP_EN.iso
>
> and none of which Windows supports. Best learn to install Windows on
> real hardware;-)
>
>
I don't understand?  Isn't it Linux Fedora that has to understand this
part?  It's a Xen kernel in Fedora 8 that I'm running this on.
-- 
Jack Smith

English doesn't borrow from other languages -- English follows other
languages down dark alleys and takes what it wants.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/fedora-xen/attachments/20080108/0f694737/attachment.htm>

From berrange at redhat.com  Tue Jan  8 23:24:31 2008
From: berrange at redhat.com (Daniel P. Berrange)
Date: Tue, 8 Jan 2008 23:24:31 +0000
Subject: [Fedora-xen] Invalid file location given
In-Reply-To: <ed5bd5f20801080956q6dcfc17fw5235c47b310cd49@mail.gmail.com>
References: <ed5bd5f20801080956q6dcfc17fw5235c47b310cd49@mail.gmail.com>
Message-ID: <20080108232431.GS21294@redhat.com>

On Tue, Jan 08, 2008 at 12:56:36PM -0500, Jack Smith wrote:
> I'm trying to set up a virtual machine running Windows XP.  I'm running
> Fedora 8 version 2.6.21-2952.fc8xen virt-manager.py 0.5.2
> 
> Paravirtualized

^^^^ This is your problem. 

You need to install Windows XP as a fully virtualized guest - make sure
you select 'Full virtualization' at this step of the install wizard
in virt-manager.

  http://virt-manager.org/screenshots/install/wizard-step3.png

NB, if 'fully virtualized' is grayed out as in this screenshot then
your CPUs does not support hardware virtualization and it is not possible
todo Windows under Xen.

> install media url  is /dev/scd0
> my normal disk partition is /dev/VolGroup00/LogVol03
> there is no file system on the logical volume and it is not mounted
> I chose peth0(bridged) as my physical device
> I have two NICs, eth0 and eth1, if it matters
> 500 MB and 1 virtual CPU
> when I click Finish, I get
> 
> Unable to complete install '<type 'exceptions.ValueError'> Invalid file
> location given: No such file or directory

This is because its trying todo a paravirtualized install and looking for
the Linux install media. Make sure you select fullvirt

Dan.
-- 
|=- Red Hat, Engineering, Emerging Technologies, Boston.  +1 978 392 2496 -=|
|=-           Perl modules: http://search.cpan.org/~danberr/              -=|
|=-               Projects: http://freshmeat.net/~danielpb/               -=|
|=-  GnuPG: 7D3B9505   F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505  -=| 



From mnielsen at redhat.com  Wed Jan  9 00:31:20 2008
From: mnielsen at redhat.com (Mark Nielsen)
Date: Tue, 08 Jan 2008 19:31:20 -0500
Subject: [Fedora-xen] Invalid file location given
In-Reply-To: <20080108232431.GS21294@redhat.com>
References: <ed5bd5f20801080956q6dcfc17fw5235c47b310cd49@mail.gmail.com>
	<20080108232431.GS21294@redhat.com>
Message-ID: <478415D8.7080702@redhat.com>



Daniel P. Berrange wrote:
> On Tue, Jan 08, 2008 at 12:56:36PM -0500, Jack Smith wrote:
>   
>> I'm trying to set up a virtual machine running Windows XP.  I'm running
>> Fedora 8 version 2.6.21-2952.fc8xen virt-manager.py 0.5.2
>>
>> Paravirtualized
>>     
>
> ^^^^ This is your problem. 
>
> You need to install Windows XP as a fully virtualized guest - make sure
> you select 'Full virtualization' at this step of the install wizard
> in virt-manager.
>
>   http://virt-manager.org/screenshots/install/wizard-step3.png
>
> NB, if 'fully virtualized' is grayed out as in this screenshot then
> your CPUs does not support hardware virtualization and it is not possible
> todo Windows under Xen.
>
>   
Or... the virtualization technology is turned off in your BIOS, as I 
find is default with Dell servers. I don't know what other systems might 
have this off by default, so check your bios setting to see if VT is an 
option.



From debian at herakles.homelinux.org  Wed Jan  9 01:20:14 2008
From: debian at herakles.homelinux.org (John Summerfield)
Date: Wed, 09 Jan 2008 10:20:14 +0900
Subject: [Fedora-xen] Re: Invalid file location given
In-Reply-To: <ed5bd5f20801081520l26b3f5djc65072c47ce4d6ea@mail.gmail.com>
References: <ed5bd5f20801080956q6dcfc17fw5235c47b310cd49@mail.gmail.com>	<ed5bd5f20801081206u7a925c17hde92c6afa7cfd293@mail.gmail.com>	<ed5bd5f20801081352y7c6b353ax7094e3f68a6330db@mail.gmail.com>	<47840326.8090100@herakles.homelinux.org>
	<ed5bd5f20801081520l26b3f5djc65072c47ce4d6ea@mail.gmail.com>
Message-ID: <4784214E.3050004@herakles.homelinux.org>

Jack Smith wrote:
> On Jan 8, 2008 6:11 PM, John Summerfield <debian at herakles.homelinux.org>
> wrote:
> 
>> Jack Smith wrote:
>>> I've also tried copying the install CD to my Apache server in
>>> /var/www/html/XP and giving the install URL as
>>> http://68.42.182.214/XP
>>> http://localhost/XP
>>> http://localhost/XP/
>>> http://localhost/XP/VRMHFPP_EN.iso
>> and none of which Windows supports. Best learn to install Windows on
>> real hardware;-)
>>
>>
> I don't understand?  Isn't it Linux Fedora that has to understand this
> part?  It's a Xen kernel in Fedora 8 that I'm running this on.

It's a Windows installer that's going to read the Windows files from the 
install media.

Installing direct from the CD (or an ISO image) is fine.

Nothing will work though, unless you use full virtualisation.

If your CPU supports full virtualisation, then you can also use kvm, and 
that's in the standard Fedora kernel.




-

Cheers
John

-- spambait
1aaaaaaa at coco.merseine.nu  Z1aaaaaaa at coco.merseine.nu
-- Advice
http://webfoot.com/advice/email.top.php
http://www.catb.org/~esr/faqs/smart-questions.html
http://support.microsoft.com/kb/555375

You cannot reply off-list:-)



From debian at herakles.homelinux.org  Wed Jan  9 20:07:04 2008
From: debian at herakles.homelinux.org (John Summerfield)
Date: Thu, 10 Jan 2008 05:07:04 +0900
Subject: [Fedora-xen] qemu: could not open hard disk image
Message-ID: <47852968.4040107@herakles.homelinux.org>

What does this mean?
[root at potoroo qemu]# cat recovery.log
/usr/bin/qemu-kvm -M pc -m 128 -smp 1 -monitor pty -boot c -hda 
/var/lib/xen/images/recovery.img -hdb /var/lib/xen/images/rto.img:c -net 
nic,macaddr=00:16:3e:22:5a:10,vlan=0 -net tap,fd=13,script=,vlan=0 -usb 
-vnc 0.0.0.0:0
qemu: could not open hard disk image '/var/lib/xen/images/rto.img:c'
[root at potoroo qemu]#

[root at potoroo qemu]# ls -l /var/lib/xen/images/rto.img:c
-rwx------ 1 root root 11999994368 Jan  9 17:03 
/var/lib/xen/images/rto.img:c
[root at potoroo qemu]# file /var/lib/xen/images/rto.img:c
/var/lib/xen/images/rto.img:c: x86 boot sector, code offset 0x52, OEM-ID 
"NTFS    ", sectors/cluster 8, reserved sectors 0, Media descriptor 
0xf8, heads 255, hidden sectors 63, dos < 4.0 BootSector (0x80)
[root at potoroo qemu]#

No selinux messages.

This filesystem is an image of a Windows partition, backed up with 
ntfsclone, restored, resized, cloned again (trying to eliminate alleged 
bad hardware sectors, a legacy of earlier problems). I expect /dev/hdb 
to be a "superfloppy" format drive which I can then manipulate into a 
partition on another virtual drive.




-- 

Cheers
John

-- spambait
1aaaaaaa at coco.merseine.nu  Z1aaaaaaa at coco.merseine.nu
-- Advice
http://webfoot.com/advice/email.top.php
http://www.catb.org/~esr/faqs/smart-questions.html
http://support.microsoft.com/kb/555375

You cannot reply off-list:-)



From debian at herakles.homelinux.org  Wed Jan  9 20:18:56 2008
From: debian at herakles.homelinux.org (John Summerfield)
Date: Thu, 10 Jan 2008 05:18:56 +0900
Subject: [Fedora-xen] error: failed to connect to the hypervisor
Message-ID: <47852C30.3080406@herakles.homelinux.org>

In my earlier missive I neglected to mention F8.

The following command is straight from the manual:
[root at potoroo summer]# virsh connect qemu:///system
error: failed to connect to the hypervisor

[root at potoroo summer]# man virsh

It seems it should be more like this:

[root at potoroo summer]# virsh connect qemu://system
error: failed to connect to the hypervisor
libvir: Remote error : Cannot access CA certificate 
'/etc/pki/CA/cacert.pem': No such file or directory (2)
error: Failed to connect to the hypervisor

[root at potoroo summer]#

except that doesn't work either. I couldn't find anything in the man 
pages about it, either how to specify a cert to use, or how to create 
one and tell everything that needs to know.

I ran the command under strace, and was not enlightened, but further 
confused with this:
[root at potoroo summer]# grep open /tmp/trace | grep proc
13066 open("/proc/xen/privcmd", O_RDWR) = -1 ENOENT (No such file or 
directory)
13066 open("/proc/xen/privcmd", O_RDWR) = -1 ENOENT (No such file or 
directory)
[root at potoroo summer]#


The connect command was one I used trying to diagnose why I could't find 
the VM to attach a disk to.

I am even more confused to find that virt-manager can attach a drive, 
though not while the system's running. I don't understand why 
virt-manager can connect when virsh cannot.


-- 

Cheers
John

-- spambait
1aaaaaaa at coco.merseine.nu  Z1aaaaaaa at coco.merseine.nu
-- Advice
http://webfoot.com/advice/email.top.php
http://www.catb.org/~esr/faqs/smart-questions.html
http://support.microsoft.com/kb/555375

You cannot reply off-list:-)



From berrange at redhat.com  Wed Jan  9 20:27:14 2008
From: berrange at redhat.com (Daniel P. Berrange)
Date: Wed, 9 Jan 2008 20:27:14 +0000
Subject: [Fedora-xen] error: failed to connect to the hypervisor
In-Reply-To: <47852C30.3080406@herakles.homelinux.org>
References: <47852C30.3080406@herakles.homelinux.org>
Message-ID: <20080109202714.GP8732@redhat.com>

On Thu, Jan 10, 2008 at 05:18:56AM +0900, John Summerfield wrote:
> In my earlier missive I neglected to mention F8.
> 
> The following command is straight from the manual:
> [root at potoroo summer]# virsh connect qemu:///system
> error: failed to connect to the hypervisor

You want  'virsh --connect qemu:///system', not plain 'connect'. The
latter is for changing the current connection when in interative
mode, but you need --connect to set the initial connection, otherwise
it'll try to use Xen.

Dan.
-- 
|=- Red Hat, Engineering, Emerging Technologies, Boston.  +1 978 392 2496 -=|
|=-           Perl modules: http://search.cpan.org/~danberr/              -=|
|=-               Projects: http://freshmeat.net/~danielpb/               -=|
|=-  GnuPG: 7D3B9505   F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505  -=| 



From debian at herakles.homelinux.org  Wed Jan  9 22:59:48 2008
From: debian at herakles.homelinux.org (John Summerfield)
Date: Thu, 10 Jan 2008 07:59:48 +0900
Subject: [Fedora-xen] error: failed to connect to the hypervisor
In-Reply-To: <20080109202714.GP8732@redhat.com>
References: <47852C30.3080406@herakles.homelinux.org>
	<20080109202714.GP8732@redhat.com>
Message-ID: <478551E4.8050007@herakles.homelinux.org>

Daniel P. Berrange wrote:
> On Thu, Jan 10, 2008 at 05:18:56AM +0900, John Summerfield wrote:
>> In my earlier missive I neglected to mention F8.
>>
>> The following command is straight from the manual:
>> [root at potoroo summer]# virsh connect qemu:///system
>> error: failed to connect to the hypervisor
> 
> You want  'virsh --connect qemu:///system', not plain 'connect'. The
> latter is for changing the current connection when in interative
> mode, but you need --connect to set the initial connection, otherwise
> it'll try to use Xen.

Okay, this looks like I'm on the right path:

virsh --connect qemu:///system list --all

Should I file a bug report for this to be clarified in the man page?




-- 

Cheers
John

-- spambait
1aaaaaaa at coco.merseine.nu  Z1aaaaaaa at coco.merseine.nu
-- Advice
http://webfoot.com/advice/email.top.php
http://www.catb.org/~esr/faqs/smart-questions.html
http://support.microsoft.com/kb/555375

You cannot reply off-list:-)



From debian at herakles.homelinux.org  Wed Jan  9 23:06:24 2008
From: debian at herakles.homelinux.org (John Summerfield)
Date: Thu, 10 Jan 2008 08:06:24 +0900
Subject: [Fedora-xen] virt* source
Message-ID: <47855370.90501@herakles.homelinux.org>


I've checked out the source virt*, but I cannot tell that it's newer 
than I have.

The changelog for virt-manager suggests not.

Mercurial doesn't set file times to those on the server, so they reflect 
when I checked it out rather than what's in the repo.

I planned to build from source and install to /usr/local, but this 
suggests my idea is impractical:

virtinst--devel/virtinst/ParaVirtGuest.py:        cmd = 
["/usr/bin/virsh", "console", "%s" %(self.domain.ID(),)]

Surely, the location of executable components should not be hard-coded 
in the source tree. I could live with it, grudgingly, if it was set at 
configure time.


-- 

Cheers
John

-- spambait
1aaaaaaa at coco.merseine.nu  Z1aaaaaaa at coco.merseine.nu
-- Advice
http://webfoot.com/advice/email.top.php
http://www.catb.org/~esr/faqs/smart-questions.html
http://support.microsoft.com/kb/555375

You cannot reply off-list:-)



From Dustin.Henning at prd-inc.com  Thu Jan 10 15:01:28 2008
From: Dustin.Henning at prd-inc.com (Dustin Henning)
Date: Thu, 10 Jan 2008 10:01:28 -0500
Subject: [Fedora-xen] virt* source
In-Reply-To: <47855370.90501@herakles.homelinux.org>
References: <47855370.90501@herakles.homelinux.org>
Message-ID: <000a01c85399$ade1b090$09a511b0$@Henning@prd-inc.com>

	I can't give you any good information on the source and configure options and whatnot, but assuming that there is a hardcoded executable path that doesn't match where you want to build to, wouldn't a hardlink do the trick?  On the other hand, if the install path in the source you want to build is hardcoded, I guess I have no thoughts, but hopefully someone does.
	Dustin

-----Original Message-----
From: fedora-xen-bounces at redhat.com [mailto:fedora-xen-bounces at redhat.com] On Behalf Of John Summerfield
Sent: Wednesday, January 09, 2008 18:06
To: Fedora Xen
Subject: [Fedora-xen] virt* source


I've checked out the source virt*, but I cannot tell that it's newer 
than I have.

The changelog for virt-manager suggests not.

Mercurial doesn't set file times to those on the server, so they reflect 
when I checked it out rather than what's in the repo.

I planned to build from source and install to /usr/local, but this 
suggests my idea is impractical:

virtinst--devel/virtinst/ParaVirtGuest.py:        cmd = 
["/usr/bin/virsh", "console", "%s" %(self.domain.ID(),)]

Surely, the location of executable components should not be hard-coded 
in the source tree. I could live with it, grudgingly, if it was set at 
configure time.


-- 

Cheers
John

-- spambait
1aaaaaaa at coco.merseine.nu  Z1aaaaaaa at coco.merseine.nu
-- Advice
http://webfoot.com/advice/email.top.php
http://www.catb.org/~esr/faqs/smart-questions.html
http://support.microsoft.com/kb/555375

You cannot reply off-list:-)

--
Fedora-xen mailing list
Fedora-xen at redhat.com
https://www.redhat.com/mailman/listinfo/fedora-xen





From crobinso at redhat.com  Thu Jan 10 17:57:33 2008
From: crobinso at redhat.com (Cole Robinson)
Date: Thu, 10 Jan 2008 12:57:33 -0500
Subject: [Fedora-xen] virt* source
In-Reply-To: <47855370.90501@herakles.homelinux.org>
References: <47855370.90501@herakles.homelinux.org>
Message-ID: <47865C8D.7000606@redhat.com>

John Summerfield wrote:
> I've checked out the source virt*, but I cannot tell that it's newer 
> than I have.
> 
> The changelog for virt-manager suggests not.
> 
> Mercurial doesn't set file times to those on the server, so they reflect 
> when I checked it out rather than what's in the repo.

The changelog isn't updated frequently, usually only with releases. To see
actual changes and the times they were made, use the 'hg log' command in the
checked out repo.

> 
> I planned to build from source and install to /usr/local, but this 
> suggests my idea is impractical:
> 
> virtinst--devel/virtinst/ParaVirtGuest.py:        cmd = 
> ["/usr/bin/virsh", "console", "%s" %(self.domain.ID(),)]
> 
> Surely, the location of executable components should not be hard-coded 
> in the source tree. I could live with it, grudgingly, if it was set at 
> configure time.
> 

I don't really know the solution to that. If virt-install pulled 'virsh' from
the shell path, /usr/local would take precedence. But there may be drawbacks
to that which I dont know.

- Cole



From rjones at redhat.com  Fri Jan 11 09:37:54 2008
From: rjones at redhat.com (Richard W.M. Jones)
Date: Fri, 11 Jan 2008 09:37:54 +0000
Subject: [Fedora-xen] virt* source
In-Reply-To: <47855370.90501@herakles.homelinux.org>
References: <47855370.90501@herakles.homelinux.org>
Message-ID: <478738F2.7030306@redhat.com>

John Summerfield wrote:
> virtinst--devel/virtinst/ParaVirtGuest.py:        cmd = 
> ["/usr/bin/virsh", "console", "%s" %(self.domain.ID(),)]
> 
> Surely, the location of executable components should not be hard-coded 
> in the source tree. I could live with it, grudgingly, if it was set at 
> configure time.

Agreed -- this is simply a bug in virt-manager.

Rich.

-- 
Emerging Technologies, Red Hat - http://et.redhat.com/~rjones/
Registered Address: Red Hat UK Ltd, Amberley Place, 107-111 Peascod
Street, Windsor, Berkshire, SL4 1TE, United Kingdom.  Registered in
England and Wales under Company Registration No. 03798903
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 3237 bytes
Desc: S/MIME Cryptographic Signature
URL: <http://listman.redhat.com/archives/fedora-xen/attachments/20080111/84f317cb/attachment.bin>

From debian at herakles.homelinux.org  Fri Jan 11 13:29:19 2008
From: debian at herakles.homelinux.org (John Summerfield)
Date: Fri, 11 Jan 2008 22:29:19 +0900
Subject: [Fedora-xen] virt* source
In-Reply-To: <000a01c85399$ade1b090$09a511b0$@Henning@prd-inc.com>
References: <47855370.90501@herakles.homelinux.org>
	<000a01c85399$ade1b090$09a511b0$@Henning@prd-inc.com>
Message-ID: <47876F2F.8070207@herakles.homelinux.org>

Dustin Henning wrote:
> 	I can't give you any good information on the source and configure options and whatnot, but assuming that there is a hardcoded executable path that doesn't match where you want to build to, wouldn't a hardlink do the trick?  On the other hand, if the install path in the source you want to build is hardcoded, I guess I have no thoughts, but hopefully someone does.
> 	Dustin

/usr/bin belongs to the package manager (rpm here, dpkg on debian). The 
hard-coded path means my self-built version would run the packaged virsh 
instead of the one I built.


-- 

Cheers
John

-- spambait
1aaaaaaa at coco.merseine.nu  Z1aaaaaaa at coco.merseine.nu
-- Advice
http://webfoot.com/advice/email.top.php
http://www.catb.org/~esr/faqs/smart-questions.html
http://support.microsoft.com/kb/555375

You cannot reply off-list:-)



From accarlson at gmail.com  Fri Jan 11 13:39:08 2008
From: accarlson at gmail.com (Augusto Castelan Carlson)
Date: Fri, 11 Jan 2008 11:39:08 -0200
Subject: [Fedora-xen] add 2 lvm to guest with virt-manager
Message-ID: <dee2b60c0801110539k1c170f40kb64cca1f28f5a691@mail.gmail.com>

Hi!

I did some research in the archives and found one message
(https://www.redhat.com/archives/fedora-xen/2007-December/msg00019.html)
related with my doubt, but without answer that I repeat below.

"If, for example, a guest has separate /root, /boot, and swap do you
recommend as best practice a separate logical volume for each or do
you give just one logical volume to the guest for it to dice up into
the various types of file systems? Is there a significant performance
difference between these two solutions?"

If it is a good practice to separate logical volumes, how can I add 2
logical volume to be used by the guest?

Thanks in advance.

Regards,

Augusto



From mnielsen at redhat.com  Fri Jan 11 13:46:17 2008
From: mnielsen at redhat.com (Mark Nielsen)
Date: Fri, 11 Jan 2008 08:46:17 -0500
Subject: [Fedora-xen] add 2 lvm to guest with virt-manager
In-Reply-To: <dee2b60c0801110539k1c170f40kb64cca1f28f5a691@mail.gmail.com>
References: <dee2b60c0801110539k1c170f40kb64cca1f28f5a691@mail.gmail.com>
Message-ID: <47877329.4020208@redhat.com>

Are you trying to use 2 logical volumes to separate / and /boot inside 
the VM, or present 2 logical volumes (which would show up as 2 separate 
disks entirely, xvda and xvdb for instance) to the guest from domain-0?

If all you want to do is have 2 separate logvols for / and /boot, then 
just present 1 logvol to the guest (which would show up inside the guest 
as xvda). Then you just partition that like any other physical disk into 
logical volumes (as many as you want, /, /boot, /var, /home, et cetera)

If you are trying to present 2 logvols to the VM itself, those will show 
up as 2 separate disks inside the VM, as I mentioned (xvda, xvdb, or in 
HVM sda, sdb, .. you get the idea) and I would wonder why you would want 
to do that.

Mark

Augusto Castelan Carlson wrote:
> Hi!
>
> I did some research in the archives and found one message
> (https://www.redhat.com/archives/fedora-xen/2007-December/msg00019.html)
> related with my doubt, but without answer that I repeat below.
>
> "If, for example, a guest has separate /root, /boot, and swap do you
> recommend as best practice a separate logical volume for each or do
> you give just one logical volume to the guest for it to dice up into
> the various types of file systems? Is there a significant performance
> difference between these two solutions?"
>
> If it is a good practice to separate logical volumes, how can I add 2
> logical volume to be used by the guest?
>
> Thanks in advance.
>
> Regards,
>
> Augusto
>
> --
> Fedora-xen mailing list
> Fedora-xen at redhat.com
> https://www.redhat.com/mailman/listinfo/fedora-xen
>   

-------------- next part --------------
A non-text attachment was scrubbed...
Name: mnielsen.vcf
Type: text/x-vcard
Size: 177 bytes
Desc: not available
URL: <http://listman.redhat.com/archives/fedora-xen/attachments/20080111/0e6dd5d9/attachment.vcf>

From debian at herakles.homelinux.org  Fri Jan 11 13:50:36 2008
From: debian at herakles.homelinux.org (John Summerfield)
Date: Fri, 11 Jan 2008 22:50:36 +0900
Subject: [Fedora-xen] virt* source
In-Reply-To: <478738F2.7030306@redhat.com>
References: <47855370.90501@herakles.homelinux.org>
	<478738F2.7030306@redhat.com>
Message-ID: <4787742C.1080306@herakles.homelinux.org>

Richard W.M. Jones wrote:
> John Summerfield wrote:
>> virtinst--devel/virtinst/ParaVirtGuest.py:        cmd = 
>> ["/usr/bin/virsh", "console", "%s" %(self.domain.ID(),)]
>>
>> Surely, the location of executable components should not be hard-coded 
>> in the source tree. I could live with it, grudgingly, if it was set at 
>> configure time.
> 
> Agreed -- this is simply a bug in virt-manager.

There are a few other places the virt* programs have fixed ideas about 
where stuff must be:
[summer at potoroo virt]$ find * -type f -exec grep -HE '/usr/(|s)bin' {} 
\; | grep -Ev '/usr/bin/(perl|python)'
Binary file 
virt-manager--devel/.hg/store/data/src/gnome-virt-manager.in.i matches
virt-manager--devel/autobuild.sh:if [ -f /usr/bin/rpmbuild ]; then
virt-manager--devel/src/virt-manager.py.in:            elif 
os.path.exists("/usr/bin/qemu"):
virt-viewer--devel/autobuild.sh:if [ -f /usr/bin/rpmbuild ]; then
virt-viewer--devel/virt-viewer.spec.in:BuildRequires: /usr/bin/pod2man
virtinst--devel/tests/boot-paravirt-disk-file.xml: 
<bootloader>/usr/bin/pygrub</bootloader>
virtinst--devel/tests/boot-paravirt-many-disks.xml: 
<bootloader>/usr/bin/pygrub</bootloader>
virtinst--devel/tests/boot-paravirt-disk-drv-tap-qcow.xml: 
<bootloader>/usr/bin/pygrub</bootloader>
virtinst--devel/tests/boot-paravirt-disk-drv-phy.xml: 
<bootloader>/usr/bin/pygrub</bootloader>
virtinst--devel/tests/boot-paravirt-disk-drv-file.xml: 
<bootloader>/usr/bin/pygrub</bootloader>
virtinst--devel/tests/boot-paravirt-disk-drv-tap.xml: 
<bootloader>/usr/bin/pygrub</bootloader>
virtinst--devel/tests/capabilities-qemu.xml: 
<emulator>/usr/bin/qemu-system-x86_64</emulator>
virtinst--devel/tests/capabilities-qemu.xml: 
<emulator>/usr/bin/qemu</emulator>
virtinst--devel/tests/capabilities-qemu.xml: 
<emulator>/usr/bin/qemu-system-mips</emulator>
virtinst--devel/tests/capabilities-qemu.xml: 
<emulator>/usr/bin/qemu-system-mipsel</emulator>
virtinst--devel/tests/capabilities-qemu.xml: 
<emulator>/usr/bin/qemu-system-sparc</emulator>
virtinst--devel/tests/capabilities-qemu.xml: 
<emulator>/usr/bin/qemu-system-ppc</emulator>
virtinst--devel/tests/boot-paravirt-disk-block.xml: 
<bootloader>/usr/bin/pygrub</bootloader>
virtinst--devel/autobuild.sh:if [ -f /usr/bin/rpmbuild ]; then
virtinst--devel/virtinst/util.py:    elif os.path.exists("/usr/bin/qemu"):
virtinst--devel/virtinst/util.py:    for dir in ['', '/sbin/', '/usr/sbin']:
virtinst--devel/virtinst/ImageManager.py:            osblob += " 
<bootloader>/usr/bin/pygrub</bootloader>"
virtinst--devel/virtinst/ParaVirtGuest.py:        cmd = 
["/usr/bin/virsh", "console", "%s" %(self.domain.ID(),)]
virtinst--devel/virtinst/DistroManager.py:            osblob += 
"<bootloader>/usr/bin/pygrub</bootloader>"
virtinst--devel/virtinst/DistroManager.py:            osblob += 
"<bootloader>/usr/bin/pygrub</bootloader>"
virtinst--devel/virt-install:    args = ["/usr/bin/virt-viewer"]
virtinst--devel/virt-install:    args = ["/usr/bin/virsh"]
virtinst--devel/ChangeLog:      'distro' Traceback (most recent call 
last): File "/usr/bin/virt-
virtinst--devel/ChangeLog:      install", line 647, in <module> main() 
File "/usr/bin/virt-
virtinst--devel/ChangeLog:      Move virt-install & virt-clone to 
/usr/bin instead of sbin since
[summer at potoroo virt]$





-- 

Cheers
John

-- spambait
1aaaaaaa at coco.merseine.nu  Z1aaaaaaa at coco.merseine.nu
-- Advice
http://webfoot.com/advice/email.top.php
http://www.catb.org/~esr/faqs/smart-questions.html
http://support.microsoft.com/kb/555375

You cannot reply off-list:-)



From debian at herakles.homelinux.org  Fri Jan 11 13:55:51 2008
From: debian at herakles.homelinux.org (John Summerfield)
Date: Fri, 11 Jan 2008 22:55:51 +0900
Subject: [Fedora-xen] virt* source
In-Reply-To: <47865C8D.7000606@redhat.com>
References: <47855370.90501@herakles.homelinux.org>
	<47865C8D.7000606@redhat.com>
Message-ID: <47877567.9090907@herakles.homelinux.org>

Cole Robinson wrote:
> John Summerfield wrote:
>> I've checked out the source virt*, but I cannot tell that it's newer 
>> than I have.
>>
>> The changelog for virt-manager suggests not.
>>
>> Mercurial doesn't set file times to those on the server, so they reflect 
>> when I checked it out rather than what's in the repo.
> 
> The changelog isn't updated frequently, usually only with releases. To see
> actual changes and the times they were made, use the 'hg log' command in the
> checked out repo.


Thanks, looks much better. Several changes I see hit problems I've seen.



> 
>> I planned to build from source and install to /usr/local, but this 
>> suggests my idea is impractical:
>>
>> virtinst--devel/virtinst/ParaVirtGuest.py:        cmd = 
>> ["/usr/bin/virsh", "console", "%s" %(self.domain.ID(),)]
>>
>> Surely, the location of executable components should not be hard-coded 
>> in the source tree. I could live with it, grudgingly, if it was set at 
>> configure time.
>>
> 
> I don't really know the solution to that. If virt-install pulled 'virsh' from
> the shell path, /usr/local would take precedence. But there may be drawbacks
> to that which I dont know.

It should use $PATH, but does not. See my reply to Richard's. I can't 
test bleeding-edge without upsetting standard F8 versions.





-- 

Cheers
John

-- spambait
1aaaaaaa at coco.merseine.nu  Z1aaaaaaa at coco.merseine.nu
-- Advice
http://webfoot.com/advice/email.top.php
http://www.catb.org/~esr/faqs/smart-questions.html
http://support.microsoft.com/kb/555375

You cannot reply off-list:-)



From accarlson at gmail.com  Fri Jan 11 14:05:39 2008
From: accarlson at gmail.com (Augusto Castelan Carlson)
Date: Fri, 11 Jan 2008 12:05:39 -0200
Subject: [Fedora-xen] add 2 lvm to guest with virt-manager
In-Reply-To: <47877329.4020208@redhat.com>
References: <dee2b60c0801110539k1c170f40kb64cca1f28f5a691@mail.gmail.com>
	<47877329.4020208@redhat.com>
Message-ID: <dee2b60c0801110605s6ce4e297x3f45f3d5ad99f76@mail.gmail.com>

Hi!

> Are you trying to use 2 logical volumes to separate / and /boot inside
> the VM, or present 2 logical volumes (which would show up as 2 separate
> disks entirely, xvda and xvdb for instance) to the guest from domain-0?

I'm trying to present 2 logical volumes to the VM.

> If you are trying to present 2 logvols to the VM itself, those will show
> up as 2 separate disks inside the VM, as I mentioned (xvda, xvdb, or in
> HVM sda, sdb, .. you get the idea) and I would wonder why you would want
> to do that.

How can I present 2 logvols to the VM?

I proposed to my "boss" to present one logvols to the VM and then do
the partitioning inside the VM (xvda1 = /home, xvda2 = /groups,...),
but he wants to present 2 logvols, one to be used for /home and the
other for /groups...

Do you believe that is better to present only one logvols? If so,
please tell me, maybe a can convince him about use only one.

Thanks!

Regards,
Augusto



From mnielsen at redhat.com  Fri Jan 11 14:22:53 2008
From: mnielsen at redhat.com (Mark Nielsen)
Date: Fri, 11 Jan 2008 09:22:53 -0500
Subject: [Fedora-xen] add 2 lvm to guest with virt-manager
In-Reply-To: <dee2b60c0801110605s6ce4e297x3f45f3d5ad99f76@mail.gmail.com>
References: <dee2b60c0801110539k1c170f40kb64cca1f28f5a691@mail.gmail.com>	
	<47877329.4020208@redhat.com>
	<dee2b60c0801110605s6ce4e297x3f45f3d5ad99f76@mail.gmail.com>
Message-ID: <47877BBD.1020607@redhat.com>

Augusto Castelan Carlson wrote:
> Hi!
>
>   
>> Are you trying to use 2 logical volumes to separate / and /boot inside
>> the VM, or present 2 logical volumes (which would show up as 2 separate
>> disks entirely, xvda and xvdb for instance) to the guest from domain-0?
>>     
>
> I'm trying to present 2 logical volumes to the VM.
>
>   
>> If you are trying to present 2 logvols to the VM itself, those will show
>> up as 2 separate disks inside the VM, as I mentioned (xvda, xvdb, or in
>> HVM sda, sdb, .. you get the idea) and I would wonder why you would want
>> to do that.
>>     
>
> How can I present 2 logvols to the VM?
>
> I proposed to my "boss" to present one logvols to the VM and then do
> the partitioning inside the VM (xvda1 = /home, xvda2 = /groups,...),
> but he wants to present 2 logvols, one to be used for /home and the
> other for /groups...
>
>   
OK, well I'm not sure what benefit this would provide you honestly. I am 
assuming that both logvols you present to the VM are coming from the 
same storage (be it SAN or local disk). You are lucky (if you insist on 
using virt-manager), however, in that it's /groups you want to partition 
off. You could simply install the system as normal with /, /boot, /home, 
et al, residing on xvda. Then you shut the VM down, edit the config file 
for the VM to add the second logical volume as xvdb, start the VM back 
up and fdisk/partition/format and create your logical volumes as you 
would normally. Think of it as installing a new box, then shutting it 
down to physically add a new hard disk. It makes things a little easier 
it you think of VMs as being just like any other server, the same thing 
you'd do to a physical box you have to pretty much do with a VM (there 
are exceptions, block attach, etc) but the hardware is just "virtual" 
vs. physical.

OR -- simpy use virt-install. It's a cmd line based too, but I find 
faster and simpler to use. The -f flag is used to present a disk, you 
just add -f as many times for as many logical volumes you want to 
present. I would expect that it orders them just as you do on the 
command line.
> Do you believe that is better to present only one logvols? If so,
> please tell me, maybe a can convince him about use only one.
>
>   
I add 2 logical volumes all the time to just about every VM I have, but 
I typically do it because the LV in question is shared among VMs with 
GFS partitions inside the VM in a cluster of virtual systems :) again, 
just add -f as many times as you want using virt-install.
> Thanks!
>
> Regards,
> Augusto
>   

-------------- next part --------------
A non-text attachment was scrubbed...
Name: mnielsen.vcf
Type: text/x-vcard
Size: 177 bytes
Desc: not available
URL: <http://listman.redhat.com/archives/fedora-xen/attachments/20080111/0bf60a22/attachment.vcf>

From Dustin.Henning at prd-inc.com  Fri Jan 11 14:24:08 2008
From: Dustin.Henning at prd-inc.com (Dustin Henning)
Date: Fri, 11 Jan 2008 09:24:08 -0500
Subject: [Fedora-xen] add 2 lvm to guest with virt-manager
In-Reply-To: <dee2b60c0801110605s6ce4e297x3f45f3d5ad99f76@mail.gmail.com>
References: <dee2b60c0801110539k1c170f40kb64cca1f28f5a691@mail.gmail.com>	<47877329.4020208@redhat.com>
	<dee2b60c0801110605s6ce4e297x3f45f3d5ad99f76@mail.gmail.com>
Message-ID: <001801c8545d$a1065e60$e3131b20$@Henning@prd-inc.com>

Augusto,
	What you present to the VM is virtual disks.  I believe what you
want to do is create one logical volume to the VM as a disk (xda), and then
partition that virtual disk using lvm (create a logical group and logical
volumes on that virtual disk).  With partitions, you can do that by fdisking
a partition and providing the partition as the virtual disk.  i.e.: fdisk
/dev/sdb3, partition as you would a disk, provide /dev/sdb3 as xvda.
However, I don't know if it is that simple with lvm.  Alternately, assuming
that you are using hvm, you would just provide your virtual disk (something
like sdb3 or something like loggroup01/logvol03 in the config) to the vm and
install/configure lvm on hda during setup.  If using paravirtualization, I
don't know whether or not you go through the full blown manual install
process, but if you do, it would be the very similar, you would just provide
your virtual disk (something like sdb3 or something like loggroup01/logvol03
in the config) to the vm and install/configure lvm on xvda during setup.  If
you don't go through the full blown manual setup when using pv, hopefully
someone else can tell you how you would configure lvm on the virtual disk.
	Dustin

-----Original Message-----
From: fedora-xen-bounces at redhat.com [mailto:fedora-xen-bounces at redhat.com]
On Behalf Of Augusto Castelan Carlson
Sent: Friday, January 11, 2008 09:06
To: Mark Nielsen
Cc: fedora-xen at redhat.com
Subject: Re: [Fedora-xen] add 2 lvm to guest with virt-manager

Hi!

> Are you trying to use 2 logical volumes to separate / and /boot inside
> the VM, or present 2 logical volumes (which would show up as 2 separate
> disks entirely, xvda and xvdb for instance) to the guest from domain-0?

I'm trying to present 2 logical volumes to the VM.

> If you are trying to present 2 logvols to the VM itself, those will show
> up as 2 separate disks inside the VM, as I mentioned (xvda, xvdb, or in
> HVM sda, sdb, .. you get the idea) and I would wonder why you would want
> to do that.

How can I present 2 logvols to the VM?

I proposed to my "boss" to present one logvols to the VM and then do
the partitioning inside the VM (xvda1 = /home, xvda2 = /groups,...),
but he wants to present 2 logvols, one to be used for /home and the
other for /groups...

Do you believe that is better to present only one logvols? If so,
please tell me, maybe a can convince him about use only one.

Thanks!

Regards,
Augusto

--
Fedora-xen mailing list
Fedora-xen at redhat.com
https://www.redhat.com/mailman/listinfo/fedora-xen




From mnielsen at redhat.com  Fri Jan 11 14:26:07 2008
From: mnielsen at redhat.com (Mark Nielsen)
Date: Fri, 11 Jan 2008 09:26:07 -0500
Subject: [Fedora-xen] add 2 lvm to guest with virt-manager
In-Reply-To: <47877BBD.1020607@redhat.com>
References: <dee2b60c0801110539k1c170f40kb64cca1f28f5a691@mail.gmail.com>		<47877329.4020208@redhat.com>	<dee2b60c0801110605s6ce4e297x3f45f3d5ad99f76@mail.gmail.com>
	<47877BBD.1020607@redhat.com>
Message-ID: <47877C7F.20803@redhat.com>

oops, I was just advised of the limits when adding multiple logical 
volumes to a VM...
"you can have upto 3 for fullvirt (or 4 if you PXE it instead of CDRM), 
or 16 for paravirt" - thanks Dan B.

Mark

Mark Nielsen wrote:
> Augusto Castelan Carlson wrote:
>> Hi!
>>
>>  
>>> Are you trying to use 2 logical volumes to separate / and /boot inside
>>> the VM, or present 2 logical volumes (which would show up as 2 separate
>>> disks entirely, xvda and xvdb for instance) to the guest from domain-0?
>>>     
>>
>> I'm trying to present 2 logical volumes to the VM.
>>
>>  
>>> If you are trying to present 2 logvols to the VM itself, those will 
>>> show
>>> up as 2 separate disks inside the VM, as I mentioned (xvda, xvdb, or in
>>> HVM sda, sdb, .. you get the idea) and I would wonder why you would 
>>> want
>>> to do that.
>>>     
>>
>> How can I present 2 logvols to the VM?
>>
>> I proposed to my "boss" to present one logvols to the VM and then do
>> the partitioning inside the VM (xvda1 = /home, xvda2 = /groups,...),
>> but he wants to present 2 logvols, one to be used for /home and the
>> other for /groups...
>>
>>   
> OK, well I'm not sure what benefit this would provide you honestly. I 
> am assuming that both logvols you present to the VM are coming from 
> the same storage (be it SAN or local disk). You are lucky (if you 
> insist on using virt-manager), however, in that it's /groups you want 
> to partition off. You could simply install the system as normal with 
> /, /boot, /home, et al, residing on xvda. Then you shut the VM down, 
> edit the config file for the VM to add the second logical volume as 
> xvdb, start the VM back up and fdisk/partition/format and create your 
> logical volumes as you would normally. Think of it as installing a new 
> box, then shutting it down to physically add a new hard disk. It makes 
> things a little easier it you think of VMs as being just like any 
> other server, the same thing you'd do to a physical box you have to 
> pretty much do with a VM (there are exceptions, block attach, etc) but 
> the hardware is just "virtual" vs. physical.
>
> OR -- simpy use virt-install. It's a cmd line based too, but I find 
> faster and simpler to use. The -f flag is used to present a disk, you 
> just add -f as many times for as many logical volumes you want to 
> present. I would expect that it orders them just as you do on the 
> command line.
>> Do you believe that is better to present only one logvols? If so,
>> please tell me, maybe a can convince him about use only one.
>>
>>   
> I add 2 logical volumes all the time to just about every VM I have, 
> but I typically do it because the LV in question is shared among VMs 
> with GFS partitions inside the VM in a cluster of virtual systems :) 
> again, just add -f as many times as you want using virt-install.
>> Thanks!
>>
>> Regards,
>> Augusto
>>   
>
> --
> Fedora-xen mailing list
> Fedora-xen at redhat.com
> https://www.redhat.com/mailman/listinfo/fedora-xen
>   

-------------- next part --------------
A non-text attachment was scrubbed...
Name: mnielsen.vcf
Type: text/x-vcard
Size: 177 bytes
Desc: not available
URL: <http://listman.redhat.com/archives/fedora-xen/attachments/20080111/9f395578/attachment.vcf>

From accarlson at gmail.com  Fri Jan 11 16:07:22 2008
From: accarlson at gmail.com (Augusto Castelan Carlson)
Date: Fri, 11 Jan 2008 14:07:22 -0200
Subject: [Fedora-xen] add 2 lvm to guest with virt-manager
In-Reply-To: <47877BBD.1020607@redhat.com>
References: <dee2b60c0801110539k1c170f40kb64cca1f28f5a691@mail.gmail.com>
	<47877329.4020208@redhat.com>
	<dee2b60c0801110605s6ce4e297x3f45f3d5ad99f76@mail.gmail.com>
	<47877BBD.1020607@redhat.com>
Message-ID: <dee2b60c0801110807y64f4f1fdx6e4a01c80a2dbc53@mail.gmail.com>

Hi!

> Then you shut the VM down, edit the config file
> for the VM to add the second logical volume as xvdb, start the VM back
> up and fdisk/partition/format and create your logical volumes as you
> would normally.

Only to be sure, this config file is the one placed in
/var/lib/xend/domains/.../config.sxp?

Regards,

Augusto



From mnielsen at redhat.com  Fri Jan 11 16:09:54 2008
From: mnielsen at redhat.com (Mark Nielsen)
Date: Fri, 11 Jan 2008 11:09:54 -0500
Subject: [Fedora-xen] add 2 lvm to guest with virt-manager
In-Reply-To: <dee2b60c0801110807y64f4f1fdx6e4a01c80a2dbc53@mail.gmail.com>
References: <dee2b60c0801110539k1c170f40kb64cca1f28f5a691@mail.gmail.com>	
	<47877329.4020208@redhat.com>	
	<dee2b60c0801110605s6ce4e297x3f45f3d5ad99f76@mail.gmail.com>	
	<47877BBD.1020607@redhat.com>
	<dee2b60c0801110807y64f4f1fdx6e4a01c80a2dbc53@mail.gmail.com>
Message-ID: <478794D2.4000705@redhat.com>

Augusto Castelan Carlson wrote:
> Hi!
>
>   
>> Then you shut the VM down, edit the config file
>> for the VM to add the second logical volume as xvdb, start the VM back
>> up and fdisk/partition/format and create your logical volumes as you
>> would normally.
>>     
>
> Only to be sure, this config file is the one placed in
> /var/lib/xend/domains/.../config.sxp?
>
>   
someone else needs to verify that :) I've only been working on RHEL 5. I 
know there were changes somewhere in the Fedora line, but I'm not 
familiar with them.
> Regards,
>
> Augusto
>   
Mark
-------------- next part --------------
A non-text attachment was scrubbed...
Name: mnielsen.vcf
Type: text/x-vcard
Size: 177 bytes
Desc: not available
URL: <http://listman.redhat.com/archives/fedora-xen/attachments/20080111/596de112/attachment.vcf>

From berrange at redhat.com  Fri Jan 11 16:10:06 2008
From: berrange at redhat.com (Daniel P. Berrange)
Date: Fri, 11 Jan 2008 16:10:06 +0000
Subject: [Fedora-xen] add 2 lvm to guest with virt-manager
In-Reply-To: <dee2b60c0801110807y64f4f1fdx6e4a01c80a2dbc53@mail.gmail.com>
References: <dee2b60c0801110539k1c170f40kb64cca1f28f5a691@mail.gmail.com>
	<47877329.4020208@redhat.com>
	<dee2b60c0801110605s6ce4e297x3f45f3d5ad99f76@mail.gmail.com>
	<47877BBD.1020607@redhat.com>
	<dee2b60c0801110807y64f4f1fdx6e4a01c80a2dbc53@mail.gmail.com>
Message-ID: <20080111161006.GF9370@redhat.com>

On Fri, Jan 11, 2008 at 02:07:22PM -0200, Augusto Castelan Carlson wrote:
> Hi!
> 
> > Then you shut the VM down, edit the config file
> > for the VM to add the second logical volume as xvdb, start the VM back
> > up and fdisk/partition/format and create your logical volumes as you
> > would normally.
> 
> Only to be sure, this config file is the one placed in
> /var/lib/xend/domains/.../config.sxp?

No, don't edit that unless you want your changes to be thrown away / randomly
overwriten at will.

Either use virt-manager to add/remove devices, or using virsh you can do
the following:

   virsh dumpxml [NAME|UUID|ID of GUEST]  >  NAME.xml
   emacs NAME.xml
   virsh define NAME.xml

That will ensure that the config is loaded into XenD correctly, and will
indirectly modify the files in /var/lib/xend in a safe fashion

Dan.
-- 
|=- Red Hat, Engineering, Emerging Technologies, Boston.  +1 978 392 2496 -=|
|=-           Perl modules: http://search.cpan.org/~danberr/              -=|
|=-               Projects: http://freshmeat.net/~danielpb/               -=|
|=-  GnuPG: 7D3B9505   F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505  -=| 



From dhanks at corp.untd.com  Sat Jan 12 01:51:06 2008
From: dhanks at corp.untd.com (Hanks, Dan)
Date: Fri, 11 Jan 2008 17:51:06 -0800
Subject: [Fedora-xen] Vlan woes
Message-ID: <CC4B7A3A6A28B94DB0B818D920886AA701DFC6E9@LAXEVS01.lax.corp.int.untd.com>

Hi folks,

I have a domU which needs to be able to service DHCP/tftpboot requests
for kickstarting boxes which live in multiple vlans. We also plan on
running several domUs alongside this one, each living within one of the
above vlans. (I assume this is possible?) 

I've found and tried a number of suggested methods for setting up
multiple vlans within a domU, but to no success. 

What is the recommended method of doing this? Do I set up all the vlans
in dom0, and somehow bridge them into corresponding vifs inside of domU?
I've tried to set up the dom0 where ifcfg-eth0 exists and is up, but has
no address configured, along with several ifcfg-eth0.NNN files to
configure addresses in each vlan. This works great for dom0, and I can
talk with hosts on the different vlans, but how do I map this into a
domU running on this dom0? Or is there a better way of going about this?

Thanks for any recommendations,

-- Dan



From mnielsen at redhat.com  Sat Jan 12 01:55:34 2008
From: mnielsen at redhat.com (Mark Nielsen)
Date: Fri, 11 Jan 2008 20:55:34 -0500
Subject: [Fedora-xen] Vlan woes
In-Reply-To: <CC4B7A3A6A28B94DB0B818D920886AA701DFC6E9@LAXEVS01.lax.corp.int.untd.com>
References: <CC4B7A3A6A28B94DB0B818D920886AA701DFC6E9@LAXEVS01.lax.corp.int.untd.com>
Message-ID: <47881E16.80107@redhat.com>

Dan,

Without knowing what you're running, I can't say for sure this will help 
you or not... I do have a document I've written on how to do multiple 
VLANs over bonded interfaces on RHEL 5.

www.certifried.com has the link to my doc (pdf and .odt).

If you're running RHEL 5, this document will probably help you a little.

Mark

Hanks, Dan wrote:
> Hi folks,
>
> I have a domU which needs to be able to service DHCP/tftpboot requests
> for kickstarting boxes which live in multiple vlans. We also plan on
> running several domUs alongside this one, each living within one of the
> above vlans. (I assume this is possible?) 
>
> I've found and tried a number of suggested methods for setting up
> multiple vlans within a domU, but to no success. 
>
> What is the recommended method of doing this? Do I set up all the vlans
> in dom0, and somehow bridge them into corresponding vifs inside of domU?
> I've tried to set up the dom0 where ifcfg-eth0 exists and is up, but has
> no address configured, along with several ifcfg-eth0.NNN files to
> configure addresses in each vlan. This works great for dom0, and I can
> talk with hosts on the different vlans, but how do I map this into a
> domU running on this dom0? Or is there a better way of going about this?
>
> Thanks for any recommendations,
>
> -- Dan
>
> --
> Fedora-xen mailing list
> Fedora-xen at redhat.com
> https://www.redhat.com/mailman/listinfo/fedora-xen
>   



From fbrier at multideck.com  Sun Jan 13 07:44:12 2008
From: fbrier at multideck.com (Frederick N. Brier)
Date: Sun, 13 Jan 2008 02:44:12 -0500
Subject: [Fedora-xen] virt-install
Message-ID: <4789C14C.1020703@multideck.com>

I just installed Fedora 8 and the Fedora Xen packages.  I have been 
trying to get a variety of VMs installed, but the most basic one is just 
a Fedora guest VM.  Please correct me if I am wrong, but the correct 
tool is "virt-install".  It asks a number of questions, but the last is 
"What is the install location?"  I finally found an excerpt from a book 
that had 
"http://download.fedora.redhat.com/pub/fedora/linux/core/6/i386" as the 
answer.  But that is not correct it is actually:
"http://download.fedora.redhat.com/pub/fedora/linux/core/*6*/i386/os", 
but that is for core 6, not 7 or Fedora 8.  And the file tree does not 
have a 
"http://download.fedora.redhat.com/pub/fedora/linux/core/*8*/i386/os".  
Is there no place where fc8's files are posted?  Or are we supposed to 
specify 6?  I would have said okay, except I started getting messages 
like this:

    4gb seg fixup, process beagle-build-in (pid 1793), cs:ip 73:0811cbff
    printk: 5990213 messages suppressed.

So there seems to be a problem.  I found this message thread saying 
there is a problem usiing the fc6 install location.

    http://lists.xensource.com/archives/html/xen-users/2006-11/msg00034.html

If anyone knows where the fc8 location is please respond!  Thank you.

Fred
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/fedora-xen/attachments/20080113/a0e6d5cb/attachment.htm>

From fbrier at multideck.com  Sun Jan 13 08:57:11 2008
From: fbrier at multideck.com (Frederick N. Brier)
Date: Sun, 13 Jan 2008 03:57:11 -0500
Subject: [Fedora-xen] xen-tools and debian on Fedora
Message-ID: <4789D267.4070302@multideck.com>

I am trying to create a DomU Debian guest VM.  I tried a Debian-Etch 
DomU from jailtime.org.  Lots of my own issues, discovering other people 
having the same exact problems, but no solutions.  So I installed 
debootstrap and xen-tools and tried that.  Again like many other people 
I ran into the "VFS: Cannot open root device "hda1" or 
unknown-block(0,0)" issue.  I have not figured out why the cfg file is 
not being generated in /etc/xen, but I have gotten it to generate images 
using the file image and LVM (creating the Logical Volumes).  I just 
hand coded the cfg file.  After they were generated, I mounted both 
images and noticed that neither had hda1 or hda2 device files in /dev.  
That would seem to be a problem.  Please help!  A link to tutorial or 
answer would be fabulous.  The only thing I have not tried yet is using 
pygrub and bundling the kernel and .img files with the guest and not 
using the fc8xen kernel and images in the Dom0's boot folder.  Thank you 
for any help.

Fred



From haan.j.de at gmail.com  Sun Jan 13 09:40:20 2008
From: haan.j.de at gmail.com (Jan de Haan)
Date: Sun, 13 Jan 2008 10:40:20 +0100
Subject: [Fedora-xen] xen-tools and debian on Fedora
In-Reply-To: <4789D267.4070302@multideck.com>
References: <4789D267.4070302@multideck.com>
Message-ID: <852c643e0801130140l4d685acav5db55de55c25dcc8@mail.gmail.com>

Hi Frederick,

   it depends a bit on wether you run a PVM or a HVM, but in latter case I
got very good results with booting from the mini.iso:
http://<repo>/debian/dists/etch/main/installer-i386/current/images/netboot/mini.iso

my domain.cfg:

kernel = "/usr/lib/xen/boot/hvmloader"
builder='hvm'
device_model = '/usr/lib/xen/bin/qemu-dm'
memory = 512
name = "vm1"
vcpus=1
pae=0
acpi=0
apic=0
cpus = ""
vif = [ 'type=ioemu, mac=aa:00:bb:cc:00:d4, bridge=192.168.1.2' ]
disk = [ 'file:/var/lib/xen/vm1-hda.img,ioemu:hda,w',
'file:/var/lib/xen/debian-4.0r1-installer-gtk-netboot-mini.iso,hdc:cdrom,r'
]
on_poweroff = 'destroy'
on_reboot   = 'destroy'
on_crash    = 'destroy'
boot='d'
sdl=0
vnc=1
vncviewer=0
stdvga=0
serial='pty'
ne2000=0
usb=1
usbdevice='tablet'


Sincerely,

Jan.

On Jan 13, 2008 9:57 AM, Frederick N. Brier <fbrier at multideck.com> wrote:

> I am trying to create a DomU Debian guest VM.  I tried a Debian-Etch
> DomU from jailtime.org.  Lots of my own issues, discovering other people
> having the same exact problems, but no solutions.  So I installed
> debootstrap and xen-tools and tried that.  Again like many other people
> I ran into the "VFS: Cannot open root device "hda1" or
> unknown-block(0,0)" issue.  I have not figured out why the cfg file is
> not being generated in /etc/xen, but I have gotten it to generate images
> using the file image and LVM (creating the Logical Volumes).  I just
> hand coded the cfg file.  After they were generated, I mounted both
> images and noticed that neither had hda1 or hda2 device files in /dev.
> That would seem to be a problem.  Please help!  A link to tutorial or
> answer would be fabulous.  The only thing I have not tried yet is using
> pygrub and bundling the kernel and .img files with the guest and not
> using the fc8xen kernel and images in the Dom0's boot folder.  Thank you
> for any help.
>
> Fred
>
> --
> Fedora-xen mailing list
> Fedora-xen at redhat.com
> https://www.redhat.com/mailman/listinfo/fedora-xen
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/fedora-xen/attachments/20080113/291c3ce7/attachment.htm>

From sundaram at fedoraproject.org  Sun Jan 13 09:50:51 2008
From: sundaram at fedoraproject.org (Rahul Sundaram)
Date: Sun, 13 Jan 2008 15:20:51 +0530
Subject: [Fedora-xen] virt-install
In-Reply-To: <4789C14C.1020703@multideck.com>
References: <4789C14C.1020703@multideck.com>
Message-ID: <4789DEFB.6030008@fedoraproject.org>

Frederick N. Brier wrote:
> I just installed Fedora 8 and the Fedora Xen packages.  I have been 
> trying to get a variety of VMs installed, but the most basic one is just 
> a Fedora guest VM.  Please correct me if I am wrong, but the correct 
> tool is "virt-install".  It asks a number of questions, but the last is 
> "What is the install location?"  I finally found an excerpt from a book 
> that had 
> "http://download.fedora.redhat.com/pub/fedora/linux/core/6/i386" as the 
> answer.  But that is not correct it is actually:
> "http://download.fedora.redhat.com/pub/fedora/linux/core/*6*/i386/os", 
> but that is for core 6, not 7 or Fedora 8.  And the file tree does not 
> have a 
> "http://download.fedora.redhat.com/pub/fedora/linux/core/*8*/i386/os".  
> Is there no place where fc8's files are posted?  Or are we supposed to 
> specify 6? 

No. Core and Extras repositories have been merged with the release of 
Fedora 7 and the location has changed to "Releases. An example mirror 
would be

http://gd.tuwien.ac.at/opsys/linux/fedora/linux/releases/8/Everything/i386/os/

Refer

http://fedoraproject.org/wiki/Docs/Fedora8VirtQuickStart

Rahul



From debian at herakles.homelinux.org  Sun Jan 13 10:06:21 2008
From: debian at herakles.homelinux.org (John Summerfield)
Date: Sun, 13 Jan 2008 19:06:21 +0900
Subject: [Fedora-xen] virt-install
In-Reply-To: <4789C14C.1020703@multideck.com>
References: <4789C14C.1020703@multideck.com>
Message-ID: <4789E29D.1060908@herakles.homelinux.org>

Frederick N. Brier wrote:
> I just installed Fedora 8 and the Fedora Xen packages.  I have been 
> trying to get a variety of VMs installed, but the most basic one is just 
> a Fedora guest VM.  Please correct me if I am wrong, but the correct 
> tool is "virt-install".  It asks a number of questions, but the last is 

You can also use virt-manager


> "What is the install location?"  I finally found an excerpt from a book 
> that had 
> "http://download.fedora.redhat.com/pub/fedora/linux/core/6/i386" as the 
> answer.  But that is not correct it is actually:
> "http://download.fedora.redhat.com/pub/fedora/linux/core/*6*/i386/os", 
> but that is for core 6, not 7 or Fedora 8.  And the file tree does not 
> have a 


If F8 will suffice, whatever you already installed from is fine.

btw You need to tell use whether you're using hardware virtualisation 
(hvm) or paravirtualisation. The answers are different.



-- 

Cheers
John

-- spambait
1aaaaaaa at coco.merseine.nu  Z1aaaaaaa at coco.merseine.nu
-- Advice
http://webfoot.com/advice/email.top.php
http://www.catb.org/~esr/faqs/smart-questions.html
http://support.microsoft.com/kb/555375

You cannot reply off-list:-)



From berrange at redhat.com  Sun Jan 13 17:27:34 2008
From: berrange at redhat.com (Daniel P. Berrange)
Date: Sun, 13 Jan 2008 17:27:34 +0000
Subject: [Fedora-xen] virt-install
In-Reply-To: <4789C14C.1020703@multideck.com>
References: <4789C14C.1020703@multideck.com>
Message-ID: <20080113172734.GD23654@redhat.com>

On Sun, Jan 13, 2008 at 02:44:12AM -0500, Frederick N. Brier wrote:
> I just installed Fedora 8 and the Fedora Xen packages.  I have been 
> trying to get a variety of VMs installed, but the most basic one is just 
> a Fedora guest VM.  Please correct me if I am wrong, but the correct 
> tool is "virt-install".  It asks a number of questions, but the last is 
> "What is the install location?"  I finally found an excerpt from a book 
> that had 
> "http://download.fedora.redhat.com/pub/fedora/linux/core/6/i386" as the 
> answer.  But that is not correct it is actually:
> "http://download.fedora.redhat.com/pub/fedora/linux/core/*6*/i386/os", 
> but that is for core 6, not 7 or Fedora 8.  And the file tree does not 
> have a 
> "http://download.fedora.redhat.com/pub/fedora/linux/core/*8*/i386/os".  
> Is there no place where fc8's files are posted?  Or are we supposed to 
> specify 6?  I would have said okay, except I started getting messages 
> like this:

Fedora Core & Extras mered during the F7 release, so the download URLs
changed style slightly

eg, i386 F8

http://download.fedora.redhat.com/pub/fedora/linux/releases/8/Fedora/i386/os/

eg, x86_64 F7

http://download.fedora.redhat.com/pub/fedora/linux/releases/7/Fedora/x86_64/os/

Basically, you always want the URL ending in '/os/' for your release.

You can also use  nfs:// or ftp:// URLs.

Regards,
Dan.
-- 
|=- Red Hat, Engineering, Emerging Technologies, Boston.  +1 978 392 2496 -=|
|=-           Perl modules: http://search.cpan.org/~danberr/              -=|
|=-               Projects: http://freshmeat.net/~danielpb/               -=|
|=-  GnuPG: 7D3B9505   F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505  -=| 



From rjones at redhat.com  Tue Jan 15 11:07:12 2008
From: rjones at redhat.com (Richard W.M. Jones)
Date: Tue, 15 Jan 2008 11:07:12 +0000
Subject: [Fedora-xen] virt* source
In-Reply-To: <4787742C.1080306@herakles.homelinux.org>
References: <47855370.90501@herakles.homelinux.org>	<478738F2.7030306@redhat.com>
	<4787742C.1080306@herakles.homelinux.org>
Message-ID: <478C93E0.90701@redhat.com>

John Summerfield wrote:
> Richard W.M. Jones wrote:
>> John Summerfield wrote:
>>> virtinst--devel/virtinst/ParaVirtGuest.py:        cmd = 
>>> ["/usr/bin/virsh", "console", "%s" %(self.domain.ID(),)]
>>>
>>> Surely, the location of executable components should not be 
>>> hard-coded in the source tree. I could live with it, grudgingly, if 
>>> it was set at configure time.
>>
>> Agreed -- this is simply a bug in virt-manager.
> 
> There are a few other places the virt* programs have fixed ideas about 
> where stuff must be:
> [summer at potoroo virt]$ find * -type f -exec grep -HE '/usr/(|s)bin' {} 
> \; | grep -Ev '/usr/bin/(perl|python)'

By and large these are not bugs.  It would only be a bug if an installed 
program contains a hard-coded path, and the path is not discovered by 
(eg) ./configure, and there is no way around the hard-coded path at 
runtime, and the user could conceivably want to use a different binary.

Rich.

-- 
Emerging Technologies, Red Hat - http://et.redhat.com/~rjones/
Registered Address: Red Hat UK Ltd, Amberley Place, 107-111 Peascod
Street, Windsor, Berkshire, SL4 1TE, United Kingdom.  Registered in
England and Wales under Company Registration No. 03798903
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 3237 bytes
Desc: S/MIME Cryptographic Signature
URL: <http://listman.redhat.com/archives/fedora-xen/attachments/20080115/e005833a/attachment.bin>

From jayeola at gmail.com  Tue Jan 15 11:31:09 2008
From: jayeola at gmail.com (John Maclean)
Date: Tue, 15 Jan 2008 11:31:09 +0000
Subject: [Fedora-xen] virt-install
In-Reply-To: <20080113172734.GD23654@redhat.com>
References: <4789C14C.1020703@multideck.com>
	<20080113172734.GD23654@redhat.com>
Message-ID: <20080115113109.3fc6eb07@mail.gmail.com>

/usr/sbin/virt-install --name fx6foo \
--paravirt \
--ram 256 \
--nographics \
--file-size 10 \
--file /dev/zulu_images/fx6foo \
--location
http://download.fedora.redhat.com/pub/fedora/linux/releases/7/Fedora/i386/os/


^^ That kind of thing. The man page has a few examples right at the end.

On Sun, 13 Jan 2008 17:27:34 +0000 "Daniel P. Berrange"
<berrange at redhat.com> wrote:

> On Sun, Jan 13, 2008 at 02:44:12AM -0500, Frederick N. Brier wrote:
> > I just installed Fedora 8 and the Fedora Xen packages.  I have been 
> > trying to get a variety of VMs installed, but the most basic one is
> > just a Fedora guest VM.  Please correct me if I am wrong, but the
> > correct tool is "virt-install".  It asks a number of questions, but
> > the last is "What is the install location?"  I finally found an
> > excerpt from a book that had 
> > "http://download.fedora.redhat.com/pub/fedora/linux/core/6/i386" as
> > the answer.  But that is not correct it is actually:
> > "http://download.fedora.redhat.com/pub/fedora/linux/core/*6*/i386/os", 
> > but that is for core 6, not 7 or Fedora 8.  And the file tree does
> > not have a 
> > "http://download.fedora.redhat.com/pub/fedora/linux/core/*8*/i386/os".  
> > Is there no place where fc8's files are posted?  Or are we supposed
> > to specify 6?  I would have said okay, except I started getting
> > messages like this:
> 
> Fedora Core & Extras mered during the F7 release, so the download URLs
> changed style slightly
> 
> eg, i386 F8
> 
> http://download.fedora.redhat.com/pub/fedora/linux/releases/8/Fedora/i386/os/
> 
> eg, x86_64 F7
> 
> http://download.fedora.redhat.com/pub/fedora/linux/releases/7/Fedora/x86_64/os/
> 
> Basically, you always want the URL ending in '/os/' for your release.
> 
> You can also use  nfs:// or ftp:// URLs.
> 
> Regards,
> Dan.


-- 

Regards,

John Maclean
MSc (DIC)
+44 7739 171 531



From berrange at redhat.com  Tue Jan 15 14:14:14 2008
From: berrange at redhat.com (Daniel P. Berrange)
Date: Tue, 15 Jan 2008 14:14:14 +0000
Subject: [Fedora-xen] virt* source
In-Reply-To: <4787742C.1080306@herakles.homelinux.org>
References: <47855370.90501@herakles.homelinux.org>
	<478738F2.7030306@redhat.com>
	<4787742C.1080306@herakles.homelinux.org>
Message-ID: <20080115141414.GF17783@redhat.com>

On Fri, Jan 11, 2008 at 10:50:36PM +0900, John Summerfield wrote:
> Richard W.M. Jones wrote:
> >John Summerfield wrote:
> >>virtinst--devel/virtinst/ParaVirtGuest.py:        cmd = 
> >>["/usr/bin/virsh", "console", "%s" %(self.domain.ID(),)]
> >>
> >>Surely, the location of executable components should not be hard-coded 
> >>in the source tree. I could live with it, grudgingly, if it was set at 
> >>configure time.
> >
> >Agreed -- this is simply a bug in virt-manager.
> 
> There are a few other places the virt* programs have fixed ideas about 
> where stuff must be:

Most of these are not bugs because they are testsuites, or because 
these paths are being validated because other apps we call already
expect the paths in those locations - so even if virt-install wished
to use non-absolute paths it couldn't.

There are the only two which could potentially be fixed to use a relative
path, and let the os.execvp/execlp call find the binary. Patches welcomed...

> virtinst--devel/virt-install:    args = ["/usr/bin/virt-viewer"]
> virtinst--devel/virt-install:    args = ["/usr/bin/virsh"]


Dan.
-- 
|=- Red Hat, Engineering, Emerging Technologies, Boston.  +1 978 392 2496 -=|
|=-           Perl modules: http://search.cpan.org/~danberr/              -=|
|=-               Projects: http://freshmeat.net/~danielpb/               -=|
|=-  GnuPG: 7D3B9505   F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505  -=| 



From ukhanlists at hotmail.com  Tue Jan 15 16:14:14 2008
From: ukhanlists at hotmail.com (Ubaidul Khan)
Date: Tue, 15 Jan 2008 11:14:14 -0500
Subject: [Fedora-xen] Guest VM dropping connection.
In-Reply-To: <BAY119-F299C8C4AE3D185AF538A91C7EF0@phx.gbl>
References: <BAY119-F299C8C4AE3D185AF538A91C7EF0@phx.gbl>
Message-ID: <BAY119-W7DA205642E05359EE8F82C7470@phx.gbl>


I am still experiencing the same problems but I am seeing some weird messages in /var/log/messages:

Jan 15 10:48:32 tsubo-dr kernel: device eth0 left promiscuous mode
Jan 15 10:49:50 tsubo-dr kernel: Removing netfilter NETLINK layer.
Jan 15 10:49:50 tsubo-dr kernel: ip_tables: (C) 2000-2006 Netfilter Core Team
Jan 15 10:49:50 tsubo-dr kernel: Netfilter messages via NETLINK v0.30.
Jan 15 10:49:50 tsubo-dr kernel: ip_conntrack version 2.4 (8192 buckets, 65536 max) - 304 bytes per conntrack
Jan 15 10:49:56 tsubo-dr kernel: device eth0 entered promiscuous mode
Jan 15 10:50:25 tsubo-dr kernel: device eth0 left promiscuous mode
Jan 15 10:54:08 tsubo-dr kernel: device eth0 entered promiscuous mode
Jan 15 10:54:37 tsubo-dr kernel: device eth0 left promiscuous mode

The loss of connection is happening during the windows when the interface enters/leaves promiscuious mode.  
----------------------------------------
> From: ukhanlists at hotmail.com
> To: xen-users at lists.xensource.com; fedora-xen at redhat.com
> Date: Mon, 30 Jul 2007 22:04:45 -0400
> CC: 
> Subject: [Fedora-xen] Guest VM dropping connection.
> 
> I am running RHEL5 Guest and Host.  The guest OS is dropping network 
> connections occasionally(I noticed my ssh session suddenly terminated).  The 
> guest is configured with private network interface and a public network 
> interface.  Following are the bridge/network settings for the host:
> 
> bridge name     bridge id               STP enabled     interfaces
> xenbr0          8000.feffffffffff              no                 vif2.0
>                                                                              
> vif1.0
>                                                                              
> peth0
>                                                                              
> vif0.0
> 
> xenbr1          8000.fefffffffffe             no                 vif2.1
>                                                                              
> peth1
>                                                                              
> vif0.3
> 
> xenbr1 is dedicated to provide the private network link for the guest os.  
> Following is the guest OS configuration:
> 
> # Automatically generated xen config file
> name = "saleen_webvm0"
> memory = "1000"
> disk = [ 
> 'tap:aio:/vms/img/redhat/linux/es/5.0/x86_64/saleen_webvm0.img,xvda,w','phy:/dev/sdc,xvdb,w' 
> ]
> vif = [ 'mac=00:16:3e:2e:6f:e1, bridge=xenbr0','mac=00:16:3e:2f:9e:b1, 
> bridge=xenbr1',]
> # vif = [ 'mac=00:16:3e:2e:6f:e1, bridge=xenbr0',]
> vfb = ["type=vnc,vncunused=1"]
> uuid = "122374dc-26a3-cb0d-99f8-3393e2481777"
> bootloader="/usr/bin/pygrub"
> vcpus=2
> on_reboot   = 'restart'
> on_crash    = 'restart'
> 
> Following is the output of ifconfig:
> 
> eth0      Link encap:Ethernet  HWaddr 00:14:4F:40:D8:70
>           inet addr:xxx.xxx.xxx.xxx  Bcast:xxx.xxx.xxx.255  
> Mask:255.255.255.0
>           inet6 addr: fe80::214:4fff:fe40:d870/64 Scope:Link
>           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>           RX packets:79313 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:1167 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0 txqueuelen:0
>           RX bytes:6619719 (6.3 MiB)  TX bytes:115448 (112.7 KiB)
> 
> eth1      Link encap:Ethernet  HWaddr 00:14:4F:40:D8:71
>           inet addr:xxx.xxx.xxx.xxx  Bcast:xxx.xxx.xxx.255  
> Mask:255.255.255.0
>           inet6 addr: fe80::214:4fff:fe40:d871/64 Scope:Link
>           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>           RX packets:0 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:12 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0 txqueuelen:0
>           RX bytes:0 (0.0 b)  TX bytes:720 (720.0 b)
> 
> peth0     Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF
>           inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link
>           UP BROADCAST RUNNING NOARP  MTU:1500  Metric:1
>           RX packets:105404 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:13455 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0 txqueuelen:1000
>           RX bytes:9122426 (8.6 MiB)  TX bytes:1997833 (1.9 MiB)
>           Base address:0x8c00 Memory:fa5e0000-fa600000
> 
> peth1     Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FE
>           inet6 addr: fe80::fcff:ffff:feff:fffe/64 Scope:Link
>           UP BROADCAST RUNNING NOARP  MTU:1500  Metric:1
>           RX packets:9239102 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:5337342 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0 txqueuelen:1000
>           RX bytes:12420212276 (11.5 GiB)  TX bytes:523849820 (499.5 MiB)
>           Base address:0x8800 Memory:fa5c0000-fa5e0000
> 
> vif1.0    Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF
>           inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link
>           UP BROADCAST RUNNING NOARP  MTU:1500  Metric:1
>           RX packets:2174 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:80032 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0 txqueuelen:32
>           RX bytes:446031 (435.5 KiB)  TX bytes:6941997 (6.6 MiB)
> 
> vif2.0    Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF
>           inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link
>           UP BROADCAST RUNNING NOARP  MTU:1500  Metric:1
>           RX packets:10084 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:89284 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0 txqueuelen:32
>           RX bytes:1186096 (1.1 MiB)  TX bytes:7380350 (7.0 MiB)
> 
> vif2.1    Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF
>           inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link
>           UP BROADCAST RUNNING NOARP  MTU:1500  Metric:1
>           RX packets:5337343 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:9239082 errors:0 dropped:20 overruns:0 carrier:0
>           collisions:0 txqueuelen:32
>           RX bytes:403712612 (385.0 MiB)  TX bytes:12383227754 (11.5 GiB)
> 
> Any help is greately appreciated.
> 
> _________________________________________________________________
> http://liveearth.msn.com
> 
> --
> Fedora-xen mailing list
> Fedora-xen at redhat.com
> https://www.redhat.com/mailman/listinfo/fedora-xen

_________________________________________________________________
Share life as it happens with the new Windows Live.
http://www.windowslive.com/share.html?ocid=TXT_TAGHM_Wave2_sharelife_012008



From mnielsen at redhat.com  Tue Jan 15 18:28:17 2008
From: mnielsen at redhat.com (Mark Nielsen)
Date: Tue, 15 Jan 2008 13:28:17 -0500
Subject: [Fedora-xen] Guest VM dropping connection.
In-Reply-To: <BAY119-W7DA205642E05359EE8F82C7470@phx.gbl>
References: <BAY119-F299C8C4AE3D185AF538A91C7EF0@phx.gbl>
	<BAY119-W7DA205642E05359EE8F82C7470@phx.gbl>
Message-ID: <478CFB41.7020501@redhat.com>

are you seeing any messages on the host about the network bouncing?

Ubaidul Khan wrote:
> I am still experiencing the same problems but I am seeing some weird messages in /var/log/messages:
>
> Jan 15 10:48:32 tsubo-dr kernel: device eth0 left promiscuous mode
> Jan 15 10:49:50 tsubo-dr kernel: Removing netfilter NETLINK layer.
> Jan 15 10:49:50 tsubo-dr kernel: ip_tables: (C) 2000-2006 Netfilter Core Team
> Jan 15 10:49:50 tsubo-dr kernel: Netfilter messages via NETLINK v0.30.
> Jan 15 10:49:50 tsubo-dr kernel: ip_conntrack version 2.4 (8192 buckets, 65536 max) - 304 bytes per conntrack
> Jan 15 10:49:56 tsubo-dr kernel: device eth0 entered promiscuous mode
> Jan 15 10:50:25 tsubo-dr kernel: device eth0 left promiscuous mode
> Jan 15 10:54:08 tsubo-dr kernel: device eth0 entered promiscuous mode
> Jan 15 10:54:37 tsubo-dr kernel: device eth0 left promiscuous mode
>
> The loss of connection is happening during the windows when the interface enters/leaves promiscuious mode.  
> ----------------------------------------
>   
>> From: ukhanlists at hotmail.com
>> To: xen-users at lists.xensource.com; fedora-xen at redhat.com
>> Date: Mon, 30 Jul 2007 22:04:45 -0400
>> CC: 
>> Subject: [Fedora-xen] Guest VM dropping connection.
>>
>> I am running RHEL5 Guest and Host.  The guest OS is dropping network 
>> connections occasionally(I noticed my ssh session suddenly terminated).  The 
>> guest is configured with private network interface and a public network 
>> interface.  Following are the bridge/network settings for the host:
>>
>> bridge name     bridge id               STP enabled     interfaces
>> xenbr0          8000.feffffffffff              no                 vif2.0
>>                                                                              
>> vif1.0
>>                                                                              
>> peth0
>>                                                                              
>> vif0.0
>>
>> xenbr1          8000.fefffffffffe             no                 vif2.1
>>                                                                              
>> peth1
>>                                                                              
>> vif0.3
>>
>> xenbr1 is dedicated to provide the private network link for the guest os.  
>> Following is the guest OS configuration:
>>
>> # Automatically generated xen config file
>> name = "saleen_webvm0"
>> memory = "1000"
>> disk = [ 
>> 'tap:aio:/vms/img/redhat/linux/es/5.0/x86_64/saleen_webvm0.img,xvda,w','phy:/dev/sdc,xvdb,w' 
>> ]
>> vif = [ 'mac=00:16:3e:2e:6f:e1, bridge=xenbr0','mac=00:16:3e:2f:9e:b1, 
>> bridge=xenbr1',]
>> # vif = [ 'mac=00:16:3e:2e:6f:e1, bridge=xenbr0',]
>> vfb = ["type=vnc,vncunused=1"]
>> uuid = "122374dc-26a3-cb0d-99f8-3393e2481777"
>> bootloader="/usr/bin/pygrub"
>> vcpus=2
>> on_reboot   = 'restart'
>> on_crash    = 'restart'
>>
>> Following is the output of ifconfig:
>>
>> eth0      Link encap:Ethernet  HWaddr 00:14:4F:40:D8:70
>>           inet addr:xxx.xxx.xxx.xxx  Bcast:xxx.xxx.xxx.255  
>> Mask:255.255.255.0
>>           inet6 addr: fe80::214:4fff:fe40:d870/64 Scope:Link
>>           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>>           RX packets:79313 errors:0 dropped:0 overruns:0 frame:0
>>           TX packets:1167 errors:0 dropped:0 overruns:0 carrier:0
>>           collisions:0 txqueuelen:0
>>           RX bytes:6619719 (6.3 MiB)  TX bytes:115448 (112.7 KiB)
>>
>> eth1      Link encap:Ethernet  HWaddr 00:14:4F:40:D8:71
>>           inet addr:xxx.xxx.xxx.xxx  Bcast:xxx.xxx.xxx.255  
>> Mask:255.255.255.0
>>           inet6 addr: fe80::214:4fff:fe40:d871/64 Scope:Link
>>           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>>           RX packets:0 errors:0 dropped:0 overruns:0 frame:0
>>           TX packets:12 errors:0 dropped:0 overruns:0 carrier:0
>>           collisions:0 txqueuelen:0
>>           RX bytes:0 (0.0 b)  TX bytes:720 (720.0 b)
>>
>> peth0     Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF
>>           inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link
>>           UP BROADCAST RUNNING NOARP  MTU:1500  Metric:1
>>           RX packets:105404 errors:0 dropped:0 overruns:0 frame:0
>>           TX packets:13455 errors:0 dropped:0 overruns:0 carrier:0
>>           collisions:0 txqueuelen:1000
>>           RX bytes:9122426 (8.6 MiB)  TX bytes:1997833 (1.9 MiB)
>>           Base address:0x8c00 Memory:fa5e0000-fa600000
>>
>> peth1     Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FE
>>           inet6 addr: fe80::fcff:ffff:feff:fffe/64 Scope:Link
>>           UP BROADCAST RUNNING NOARP  MTU:1500  Metric:1
>>           RX packets:9239102 errors:0 dropped:0 overruns:0 frame:0
>>           TX packets:5337342 errors:0 dropped:0 overruns:0 carrier:0
>>           collisions:0 txqueuelen:1000
>>           RX bytes:12420212276 (11.5 GiB)  TX bytes:523849820 (499.5 MiB)
>>           Base address:0x8800 Memory:fa5c0000-fa5e0000
>>
>> vif1.0    Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF
>>           inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link
>>           UP BROADCAST RUNNING NOARP  MTU:1500  Metric:1
>>           RX packets:2174 errors:0 dropped:0 overruns:0 frame:0
>>           TX packets:80032 errors:0 dropped:0 overruns:0 carrier:0
>>           collisions:0 txqueuelen:32
>>           RX bytes:446031 (435.5 KiB)  TX bytes:6941997 (6.6 MiB)
>>
>> vif2.0    Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF
>>           inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link
>>           UP BROADCAST RUNNING NOARP  MTU:1500  Metric:1
>>           RX packets:10084 errors:0 dropped:0 overruns:0 frame:0
>>           TX packets:89284 errors:0 dropped:0 overruns:0 carrier:0
>>           collisions:0 txqueuelen:32
>>           RX bytes:1186096 (1.1 MiB)  TX bytes:7380350 (7.0 MiB)
>>
>> vif2.1    Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF
>>           inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link
>>           UP BROADCAST RUNNING NOARP  MTU:1500  Metric:1
>>           RX packets:5337343 errors:0 dropped:0 overruns:0 frame:0
>>           TX packets:9239082 errors:0 dropped:20 overruns:0 carrier:0
>>           collisions:0 txqueuelen:32
>>           RX bytes:403712612 (385.0 MiB)  TX bytes:12383227754 (11.5 GiB)
>>
>> Any help is greately appreciated.
>>
>> _________________________________________________________________
>> http://liveearth.msn.com
>>
>> --
>> Fedora-xen mailing list
>> Fedora-xen at redhat.com
>> https://www.redhat.com/mailman/listinfo/fedora-xen
>>     
>
> _________________________________________________________________
> Share life as it happens with the new Windows Live.
> http://www.windowslive.com/share.html?ocid=TXT_TAGHM_Wave2_sharelife_012008
>
> --
> Fedora-xen mailing list
> Fedora-xen at redhat.com
> https://www.redhat.com/mailman/listinfo/fedora-xen
>   

-------------- next part --------------
A non-text attachment was scrubbed...
Name: mnielsen.vcf
Type: text/x-vcard
Size: 177 bytes
Desc: not available
URL: <http://listman.redhat.com/archives/fedora-xen/attachments/20080115/334c1f26/attachment.vcf>

From debian at herakles.homelinux.org  Tue Jan 15 23:37:24 2008
From: debian at herakles.homelinux.org (John Summerfield)
Date: Wed, 16 Jan 2008 08:37:24 +0900
Subject: [Fedora-xen] virt* source
In-Reply-To: <478C93E0.90701@redhat.com>
References: <47855370.90501@herakles.homelinux.org>	<478738F2.7030306@redhat.com>	<4787742C.1080306@herakles.homelinux.org>
	<478C93E0.90701@redhat.com>
Message-ID: <478D43B4.3020807@herakles.homelinux.org>

Richard W.M. Jones wrote:
> John Summerfield wrote:
>> Richard W.M. Jones wrote:
>>> John Summerfield wrote:
>>>> virtinst--devel/virtinst/ParaVirtGuest.py:        cmd = 
>>>> ["/usr/bin/virsh", "console", "%s" %(self.domain.ID(),)]
>>>>
>>>> Surely, the location of executable components should not be 
>>>> hard-coded in the source tree. I could live with it, grudgingly, if 
>>>> it was set at configure time.
>>>
>>> Agreed -- this is simply a bug in virt-manager.
>>
>> There are a few other places the virt* programs have fixed ideas about 
>> where stuff must be:
>> [summer at potoroo virt]$ find * -type f -exec grep -HE '/usr/(|s)bin' {} 
>> \; | grep -Ev '/usr/bin/(perl|python)'
> 
> By and large these are not bugs.  It would only be a bug if an installed 
> program contains a hard-coded path, and the path is not discovered by 
> (eg) ./configure, and there is no way around the hard-coded path at 
> runtime, and the user could conceivably want to use a different binary.
> 
> Rich.

Thanks Rich.
I am unfamiliar with the tools I need to put that statement to the test. 
INSTALL says to run ./configure, but there is no ./configure to run.

The website does say how to get the source with hg, and how to submit 
changes, but I can't see how to go from the checkout to building and 
installing.

Where is the documentation?

I do want to use alternative binaries (but then again I don't), but I do 
not wish to replace any standard part of F8.


-- 

Cheers
John

-- spambait
1aaaaaaa at coco.merseine.nu  Z1aaaaaaa at coco.merseine.nu
-- Advice
http://webfoot.com/advice/email.top.php
http://www.catb.org/~esr/faqs/smart-questions.html
http://support.microsoft.com/kb/555375

You cannot reply off-list:-)



From debian at herakles.homelinux.org  Wed Jan 16 03:41:41 2008
From: debian at herakles.homelinux.org (John Summerfield)
Date: Wed, 16 Jan 2008 12:41:41 +0900
Subject: [Fedora-xen] qemu: could not open hard disk image
In-Reply-To: <47852968.4040107@herakles.homelinux.org>
References: <47852968.4040107@herakles.homelinux.org>
Message-ID: <478D7CF5.8030704@herakles.homelinux.org>

John Summerfield wrote:
> What does this mean?
> [root at potoroo qemu]# cat recovery.log
> /usr/bin/qemu-kvm -M pc -m 128 -smp 1 -monitor pty -boot c -hda 
> /var/lib/xen/images/recovery.img -hdb /var/lib/xen/images/rto.img:c -net 
> nic,macaddr=00:16:3e:22:5a:10,vlan=0 -net tap,fd=13,script=,vlan=0 -usb 
> -vnc 0.0.0.0:0
> qemu: could not open hard disk image '/var/lib/xen/images/rto.img:c'
> [root at potoroo qemu]#
> 
> [root at potoroo qemu]# ls -l /var/lib/xen/images/rto.img:c
> -rwx------ 1 root root 11999994368 Jan  9 17:03 
> /var/lib/xen/images/rto.img:c
> [root at potoroo qemu]# file /var/lib/xen/images/rto.img:c
> /var/lib/xen/images/rto.img:c: x86 boot sector, code offset 0x52, OEM-ID 
> "NTFS    ", sectors/cluster 8, reserved sectors 0, Media descriptor 
> 0xf8, heads 255, hidden sectors 63, dos < 4.0 BootSector (0x80)
> [root at potoroo qemu]#
> 
> No selinux messages.
> 
> This filesystem is an image of a Windows partition, backed up with 
> ntfsclone, restored, resized, cloned again (trying to eliminate alleged 
> bad hardware sectors, a legacy of earlier problems). I expect /dev/hdb 
> to be a "superfloppy" format drive which I can then manipulate into a 
> partition on another virtual drive.

I have not seen a reply to this; on the basis I really _must_ get 
something moving, I tried using /var/lib/xen/images/rto.img and that 
works fine.

Is something being too clever and misvalidating file names?


-- 

Cheers
John

-- spambait
1aaaaaaa at coco.merseine.nu  Z1aaaaaaa at coco.merseine.nu
-- Advice
http://webfoot.com/advice/email.top.php
http://www.catb.org/~esr/faqs/smart-questions.html
http://support.microsoft.com/kb/555375

You cannot reply off-list:-)



From debian at herakles.homelinux.org  Wed Jan 16 05:12:33 2008
From: debian at herakles.homelinux.org (John Summerfield)
Date: Wed, 16 Jan 2008 14:12:33 +0900
Subject: [Fedora-xen] KVM: unhandled exception
Message-ID: <478D9241.5050401@herakles.homelinux.org>

[root at potoroo ~]# /usr/bin/qemu-kvm -M pc -m 128 -smp 1 -monitor pty 
-no-acpi -boot c -hda /var/lib/xen/images/rto-test.img -net 
nic,macaddr=00:16:3e:31:8a:8f,vlan=0 -net tap,fd=13,script=,vlan=0 -usb 
-usbdevice tablet -vnc 0.0.0.0:0
char device redirected to /dev/pts/35
unhandled vm exit:  0x9
rax 000000000000001f rbx 000000000003f530 rcx 00000000000000ff rdx 
000000000000001f
rsi 0000000000000000 rdi 0000000000000063 rsp 000000000003f40c rbp 
000000000003f458
r8  0000000000000000 r9  0000000000000000 r10 0000000000000000 r11 
0000000000000000
r12 0000000000000000 r13 0000000000000000 r14 0000000000000000 r15 
0000000000000000
rip 000000008051ecc3 rflags 00010246
cs 0008 (00000000/ffffffff p 1 dpl 0 db 1 s 1 type b l 0 g 1 avl 0)
ds 0023 (00000000/ffffffff p 1 dpl 3 db 1 s 1 type 3 l 0 g 1 avl 0)
es 0023 (00000000/ffffffff p 1 dpl 3 db 1 s 1 type 3 l 0 g 1 avl 0)
ss 0010 (00000000/ffffffff p 1 dpl 0 db 1 s 1 type 3 l 0 g 1 avl 0)
fs 0030 (ffdff000/00001fff p 1 dpl 0 db 1 s 1 type 3 l 0 g 1 avl 0)
gs 0000 (00000000/0000ffff p 1 dpl 0 db 0 s 1 type 3 l 0 g 0 avl 0)
tr 0028 (80042000/000020ab p 1 dpl 0 db 0 s 0 type b l 0 g 0 avl 0)
ldt 0000 (00000000/ffffffff p 0 dpl 0 db 0 s 0 type 0 l 0 g 0 avl 0)
gdt 8003f000/3ff
idt 8003f400/7ff
cr0 e0000011 cr2 63 cr3 305000 cr4 20 cr8 0 efer 0
Aborted
[root at potoroo ~]#


I created the file /var/lib/xen/images/rto-test.img by installing 
Windows XP to the point it reboots.

I then attached /var/lib/xen/images/rto-test.img to my Debian rescue 
system, and copied /var/lib/xen/images/rto.img to it using ntfsclone. 
This is the ntfsresize info on the file:

[root at potoroo ~]# ntfsresize --info /var/lib/xen/images/rto.img -f
ntfsresize v1.13.1 (libntfs 9:0:0)
Device name        : /var/lib/xen/images/rto.img
NTFS volume version: 3.1
Cluster size       : 4096 bytes
Current volume size: 11999994368 bytes (12000 MB)
Current device size: 60011606528 bytes (60012 MB)
ERROR: This software has detected that the disk has at least 2 bad sectors.
****************************************************************************
* WARNING: The disk has bad sector. This means physical damage on the disk *
* surface caused by deterioration, manufacturing faults or other reason.   *
* The reliability of the disk may stay stable or degrade fast. We suggest  *
* making a full backup urgently by running 'ntfsclone --rescue ...' then   *
* run 'chkdsk /f /r' on Windows and rebooot it TWICE! Then you can resize  *
* NTFS safely by additionally using the --bad-sectors option of ntfsresize.*
****************************************************************************
[root at potoroo ~]#

Note that the bad sectors are a legacy of the install to the original, 
long deceased drive. I've not found a way to clear it, the system runs 
ine and the bad sectors are not relevant to the problem.


This is the image I'm trying to boot:
[root at potoroo ~]# parted /var/lib/xen/images/rto-test.img print
Model:  (file)
Disk /var/lib/xen/images/rto-test.img: 14.7GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos

Number  Start   End     Size    Type     File system  Flags
  1      32.3kB  14.7GB  14.7GB  primary  ntfs         boot

[root at potoroo ~]#

the MBR is fine:
[root at potoroo ~]# cat /var/lib/xen/images/rto-test.img   | xxd | head -32
0000000: 33c0 8ed0 bc00 7cfb 5007 501f fcbe 1b7c  3.....|.P.P....|
0000010: bf1b 0650 57b9 e501 f3a4 cbbd be07 b104  ...PW...........
0000020: 386e 007c 0975 1383 c510 e2f4 cd18 8bf5  8n.|.u..........
0000030: 83c6 1049 7419 382c 74f6 a0b5 07b4 078b  ...It.8,t.......
0000040: f0ac 3c00 74fc bb07 00b4 0ecd 10eb f288  ..<.t...........
0000050: 4e10 e846 0073 2afe 4610 807e 040b 740b  N..F.s*.F..~..t.
0000060: 807e 040c 7405 a0b6 0775 d280 4602 0683  .~..t....u..F...
0000070: 4608 0683 560a 00e8 2100 7305 a0b6 07eb  F...V...!.s.....
0000080: bc81 3efe 7d55 aa74 0b80 7e10 0074 c8a0  ..>.}U.t..~..t..
0000090: b707 eba9 8bfc 1e57 8bf5 cbbf 0500 8a56  .......W.......V
00000a0: 00b4 08cd 1372 238a c124 3f98 8ade 8afc  .....r#..$?.....
00000b0: 43f7 e38b d186 d6b1 06d2 ee42 f7e2 3956  C..........B..9V
00000c0: 0a77 2372 0539 4608 731c b801 02bb 007c  .w#r.9F.s......|
00000d0: 8b4e 028b 5600 cd13 7351 4f74 4e32 e48a  .N..V...sQOtN2..
00000e0: 5600 cd13 ebe4 8a56 0060 bbaa 55b4 41cd  V......V.`..U.A.
00000f0: 1372 3681 fb55 aa75 30f6 c101 742b 6160  .r6..U.u0...t+a`
0000100: 6a00 6a00 ff76 0aff 7608 6a00 6800 7c6a  j.j..v..v.j.h.|j
0000110: 016a 10b4 428b f4cd 1361 6173 0e4f 740b  .j..B....aas.Ot.
0000120: 32e4 8a56 00cd 13eb d661 f9c3 496e 7661  2..V.....a..Inva
0000130: 6c69 6420 7061 7274 6974 696f 6e20 7461  lid partition ta
0000140: 626c 6500 4572 726f 7220 6c6f 6164 696e  ble.Error loadin
0000150: 6720 6f70 6572 6174 696e 6720 7379 7374  g operating syst
0000160: 656d 004d 6973 7369 6e67 206f 7065 7261  em.Missing opera
0000170: 7469 6e67 2073 7973 7465 6d00 0000 0000  ting system.....
0000180: 0000 0000 0000 0000 0000 0000 0000 0000  ................
0000190: 0000 0000 0000 0000 0000 0000 0000 0000  ................
00001a0: 0000 0000 0000 0000 0000 0000 0000 0000  ................
00001b0: 0000 0000 002c 4463 857a 857a 0000 8001  .....,Dc.z.z....
00001c0: 0100 07fe ffff 3f00 0000 f811 b501 0000  ......?.........
00001d0: 0000 0000 0000 0000 0000 0000 0000 0000  ................
00001e0: 0000 0000 0000 0000 0000 0000 0000 0000  ................
00001f0: 0000 0000 0000 0000 0000 0000 0000 55aa  ..............U.
[root at potoroo ~]#

Oh, in case it matters:
[root at potoroo ~]# cat /proc/cpuinfo
processor       : 0
vendor_id       : GenuineIntel
cpu family      : 6
model           : 15
model name      : Intel(R) Core(TM)2 CPU          6300  @ 1.86GHz
stepping        : 6
cpu MHz         : 1596.000
cache size      : 2048 KB
physical id     : 0
siblings        : 2
core id         : 0
cpu cores       : 2
fpu             : yes
fpu_exception   : yes
cpuid level     : 10
wp              : yes
flags           : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge 
mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe 
syscall nx lm constant_tsc arch_perfmon pebs bts rep_good pni monitor 
ds_cpl vmx est tm2 ssse3 cx16 xtpr lahf_lm
bogomips        : 3725.73
clflush size    : 64
cache_alignment : 64
address sizes   : 36 bits physical, 48 bits virtual
power management:

processor       : 1
etc
and
[root at potoroo ~]# uname -a
Linux potoroo.demo.lan 2.6.23.9-85.fc8 #1 SMP Fri Dec 7 15:49:36 EST 
2007 x86_64 x86_64 x86_64 GNU/Linux



What is wrong, and what do I need to do to fix it?


-- 

Cheers
John

-- spambait
1aaaaaaa at coco.merseine.nu  Z1aaaaaaa at coco.merseine.nu
-- Advice
http://webfoot.com/advice/email.top.php
http://www.catb.org/~esr/faqs/smart-questions.html
http://support.microsoft.com/kb/555375

You cannot reply off-list:-)



From debian at herakles.homelinux.org  Wed Jan 16 06:17:57 2008
From: debian at herakles.homelinux.org (John Summerfield)
Date: Wed, 16 Jan 2008 15:17:57 +0900
Subject: [Fedora-xen] KVM: unhandled exception
In-Reply-To: <478D9241.5050401@herakles.homelinux.org>
References: <478D9241.5050401@herakles.homelinux.org>
Message-ID: <478DA195.6000505@herakles.homelinux.org>

John Summerfield wrote:

> What is wrong, and what do I need to do to fix it?

I rebooted to a xen kernel, created a .hvm configuration file with vim 
and it's booted and currently doing a filesystem check (as expected).

-- 

Cheers
John

-- spambait
1aaaaaaa at coco.merseine.nu  Z1aaaaaaa at coco.merseine.nu
-- Advice
http://webfoot.com/advice/email.top.php
http://www.catb.org/~esr/faqs/smart-questions.html
http://support.microsoft.com/kb/555375

You cannot reply off-list:-)



From avi at qumranet.com  Wed Jan 16 09:37:30 2008
From: avi at qumranet.com (Avi Kivity)
Date: Wed, 16 Jan 2008 11:37:30 +0200
Subject: [Fedora-xen] KVM: unhandled exception
In-Reply-To: <478D9241.5050401@herakles.homelinux.org>
References: <478D9241.5050401@herakles.homelinux.org>
Message-ID: <478DD05A.1080204@qumranet.com>

John Summerfield wrote:
> [root at potoroo ~]# /usr/bin/qemu-kvm -M pc -m 128 -smp 1 -monitor pty 
> -no-acpi -boot c -hda /var/lib/xen/images/rto-test.img -net 
> nic,macaddr=00:16:3e:31:8a:8f,vlan=0 -net tap,fd=13,script=,vlan=0 
> -usb -usbdevice tablet -vnc 0.0.0.0:0
> char device redirected to /dev/pts/35
> unhandled vm exit:  0x9
> rax 000000000000001f rbx 000000000003f530 rcx 00000000000000ff rdx 
> 000000000000001f
> rsi 0000000000000000 rdi 0000000000000063 rsp 000000000003f40c rbp 
> 000000000003f458
> r8  0000000000000000 r9  0000000000000000 r10 0000000000000000 r11 
> 0000000000000000
> r12 0000000000000000 r13 0000000000000000 r14 0000000000000000 r15 
> 0000000000000000
> rip 000000008051ecc3 rflags 00010246
> cs 0008 (00000000/ffffffff p 1 dpl 0 db 1 s 1 type b l 0 g 1 avl 0)
> ds 0023 (00000000/ffffffff p 1 dpl 3 db 1 s 1 type 3 l 0 g 1 avl 0)
> es 0023 (00000000/ffffffff p 1 dpl 3 db 1 s 1 type 3 l 0 g 1 avl 0)
> ss 0010 (00000000/ffffffff p 1 dpl 0 db 1 s 1 type 3 l 0 g 1 avl 0)
> fs 0030 (ffdff000/00001fff p 1 dpl 0 db 1 s 1 type 3 l 0 g 1 avl 0)
> gs 0000 (00000000/0000ffff p 1 dpl 0 db 0 s 1 type 3 l 0 g 0 avl 0)
> tr 0028 (80042000/000020ab p 1 dpl 0 db 0 s 0 type b l 0 g 0 avl 0)
> ldt 0000 (00000000/ffffffff p 0 dpl 0 db 0 s 0 type 0 l 0 g 0 avl 0)
> gdt 8003f000/3ff
> idt 8003f400/7ff
> cr0 e0000011 cr2 63 cr3 305000 cr4 20 cr8 0 efer 0
> Aborted
> [root at potoroo ~]#
>
>
> I created the file /var/lib/xen/images/rto-test.img by installing 
> Windows XP to the point it reboots.
>

Did you also install it with -no-acpi?  What happens if you drop that 
option?

-- 
error compiling committee.c: too many arguments to function



From accarlson at gmail.com  Wed Jan 16 10:51:45 2008
From: accarlson at gmail.com (Augusto Castelan Carlson)
Date: Wed, 16 Jan 2008 08:51:45 -0200
Subject: [Fedora-xen] guest state ---s-d
Message-ID: <dee2b60c0801160251i35798309q985a3ed1b79fca39@mail.gmail.com>

Hi!

One of my guests (guest1) was not accessible today. The state was
---s-d. Looking at the xen docs, for "s" says that the state is
shutdown, but there is no entry for "d".
Every night I save the guest with
# virsh save guest1 /saved/guest1_saved
and mount the guest1 disk to backup user files, umount the disk and
restore the guest:
# virsh restore /saved/guest1_saved
In the xend.log there was no message about the restore.
When I tried to shutdown (with xm ou virsh) the guest , I received
"Error: Domain cannot be shutdown". Below the " xm list" output and
the error from xend.log

Dom0 and DomU are Fedora 7 with 2.6.21-6.fc7xen, xen-3.1.2-1.fc7,
xen-libs-3.1.2-1.fc7 and libvirt-0.3.2-1.fc7.

#xm list
Name                                        ID   Mem VCPUs      State   Time(s)
Domain-0                                     0   493     2     r-----   5039.8
guest1                                13   251     1     ---s-d    440.0
guest2                                14   251     2     ------    219.6

xend.log output:
[2008-01-16 08:09:15 2303] ERROR (SrvBase:88) Request shutdown failed.
Traceback (most recent call last):
  File "/usr/lib/python2.5/site-packages/xen/web/SrvBase.py", line 85, in perfor
m
    return op_method(op, req)
  File "/usr/lib/python2.5/site-packages/xen/xend/server/SrvDomain.py", line 65,
 in op_shutdown
    return self.dom.shutdown(req.args['reason'][0])
  File "/usr/lib/python2.5/site-packages/xen/xend/XendDomainInfo.py", line 453,
in shutdown
    raise XendError('Domain cannot be shutdown')
XendError: Domain cannot be shutdown

What is the meaning of the "---s-d" state and what canbe the cause of
this problem?

Thanks in advance!

Regards,
Augusto



From rjones at redhat.com  Wed Jan 16 13:37:10 2008
From: rjones at redhat.com (Richard W.M. Jones)
Date: Wed, 16 Jan 2008 13:37:10 +0000
Subject: [Fedora-xen] guest state ---s-d
In-Reply-To: <dee2b60c0801160251i35798309q985a3ed1b79fca39@mail.gmail.com>
References: <dee2b60c0801160251i35798309q985a3ed1b79fca39@mail.gmail.com>
Message-ID: <478E0886.9030608@redhat.com>

Augusto Castelan Carlson wrote:
> Hi!
> 
> One of my guests (guest1) was not accessible today. The state was
> ---s-d. Looking at the xen docs, for "s" says that the state is
> shutdown, but there is no entry for "d".
> Every night I save the guest with
> # virsh save guest1 /saved/guest1_saved
> and mount the guest1 disk to backup user files, umount the disk and
> restore the guest:
> # virsh restore /saved/guest1_saved
> In the xend.log there was no message about the restore.
> When I tried to shutdown (with xm ou virsh) the guest , I received
> "Error: Domain cannot be shutdown". Below the " xm list" output and
> the error from xend.log
> 
> Dom0 and DomU are Fedora 7 with 2.6.21-6.fc7xen, xen-3.1.2-1.fc7,
> xen-libs-3.1.2-1.fc7 and libvirt-0.3.2-1.fc7.
> 
> #xm list
> Name                                        ID   Mem VCPUs      State   Time(s)
> Domain-0                                     0   493     2     r-----   5039.8
> guest1                                13   251     1     ---s-d    440.0
> guest2                                14   251     2     ------    219.6
> 
> xend.log output:
> [2008-01-16 08:09:15 2303] ERROR (SrvBase:88) Request shutdown failed.
> Traceback (most recent call last):
>   File "/usr/lib/python2.5/site-packages/xen/web/SrvBase.py", line 85, in perfor
> m
>     return op_method(op, req)
>   File "/usr/lib/python2.5/site-packages/xen/xend/server/SrvDomain.py", line 65,
>  in op_shutdown
>     return self.dom.shutdown(req.args['reason'][0])
>   File "/usr/lib/python2.5/site-packages/xen/xend/XendDomainInfo.py", line 453,
> in shutdown
>     raise XendError('Domain cannot be shutdown')
> XendError: Domain cannot be shutdown
> 
> What is the meaning of the "---s-d" state and what canbe the cause of
> this problem?

I think the 'd' in this case means 'dying'.  Try shutting down the 
domain hard, eg. 'virsh destroy guest1'.

Rich.

-- 
Emerging Technologies, Red Hat - http://et.redhat.com/~rjones/
Registered Address: Red Hat UK Ltd, Amberley Place, 107-111 Peascod
Street, Windsor, Berkshire, SL4 1TE, United Kingdom.  Registered in
England and Wales under Company Registration No. 03798903
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 3237 bytes
Desc: S/MIME Cryptographic Signature
URL: <http://listman.redhat.com/archives/fedora-xen/attachments/20080116/c9fdd636/attachment.bin>

From rjones at redhat.com  Wed Jan 16 13:40:41 2008
From: rjones at redhat.com (Richard W.M. Jones)
Date: Wed, 16 Jan 2008 13:40:41 +0000
Subject: [Fedora-xen] virt* source
In-Reply-To: <478D43B4.3020807@herakles.homelinux.org>
References: <47855370.90501@herakles.homelinux.org>	<478738F2.7030306@redhat.com>	<4787742C.1080306@herakles.homelinux.org>	<478C93E0.90701@redhat.com>
	<478D43B4.3020807@herakles.homelinux.org>
Message-ID: <478E0959.2050603@redhat.com>

John Summerfield wrote:
> I am unfamiliar with the tools I need to put that statement to the test. 
> INSTALL says to run ./configure, but there is no ./configure to run.
> 
> The website does say how to get the source with hg, and how to submit 
> changes, but I can't see how to go from the checkout to building and 
> installing.

I'm not sure which INSTALL file you're reading, but once you've got the 
source for virtinst--devel from hg you need to use the standard python 
way to build it.  Try:

   python setup.py --help

If this is Fedora, another, better route to go down is to build it from 
the .src.rpm using rpmbuild.  Try the first suggestion on this page:

   http://fedoranews.org/tchung/rpmbuild/

Rich.

-- 
Emerging Technologies, Red Hat - http://et.redhat.com/~rjones/
Registered Address: Red Hat UK Ltd, Amberley Place, 107-111 Peascod
Street, Windsor, Berkshire, SL4 1TE, United Kingdom.  Registered in
England and Wales under Company Registration No. 03798903
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 3237 bytes
Desc: S/MIME Cryptographic Signature
URL: <http://listman.redhat.com/archives/fedora-xen/attachments/20080116/0825c9f7/attachment.bin>

From crobinso at redhat.com  Wed Jan 16 15:26:07 2008
From: crobinso at redhat.com (Cole Robinson)
Date: Wed, 16 Jan 2008 10:26:07 -0500
Subject: [Fedora-xen] virt* source
In-Reply-To: <478D43B4.3020807@herakles.homelinux.org>
References: <47855370.90501@herakles.homelinux.org>	<478738F2.7030306@redhat.com>	<4787742C.1080306@herakles.homelinux.org>	<478C93E0.90701@redhat.com>
	<478D43B4.3020807@herakles.homelinux.org>
Message-ID: <478E220F.10609@redhat.com>

John Summerfield wrote:
> Richard W.M. Jones wrote:
>> John Summerfield wrote:
>>> Richard W.M. Jones wrote:
>>>> John Summerfield wrote:
>>>>> virtinst--devel/virtinst/ParaVirtGuest.py:        cmd = 
>>>>> ["/usr/bin/virsh", "console", "%s" %(self.domain.ID(),)]
>>>>>
>>>>> Surely, the location of executable components should not be 
>>>>> hard-coded in the source tree. I could live with it, grudgingly, if 
>>>>> it was set at configure time.
>>>> Agreed -- this is simply a bug in virt-manager.
>>> There are a few other places the virt* programs have fixed ideas about 
>>> where stuff must be:
>>> [summer at potoroo virt]$ find * -type f -exec grep -HE '/usr/(|s)bin' {} 
>>> \; | grep -Ev '/usr/bin/(perl|python)'
>> By and large these are not bugs.  It would only be a bug if an installed 
>> program contains a hard-coded path, and the path is not discovered by 
>> (eg) ./configure, and there is no way around the hard-coded path at 
>> runtime, and the user could conceivably want to use a different binary.
>>
>> Rich.
> 
> Thanks Rich.
> I am unfamiliar with the tools I need to put that statement to the test. 
> INSTALL says to run ./configure, but there is no ./configure to run.
> 
> The website does say how to get the source with hg, and how to submit 
> changes, but I can't see how to go from the checkout to building and 
> installing.
> 
> Where is the documentation?
> 
> I do want to use alternative binaries (but then again I don't), but I do 
> not wish to replace any standard part of F8.
> 
> 

If you are trying to build virt-manager, run ./autogen.sh that comes with the
source: this will build 'configure'. You will probably need to install a few
things in order to build it like intltool and automake.

- Cole



From accarlson at gmail.com  Wed Jan 16 18:03:14 2008
From: accarlson at gmail.com (Augusto Castelan Carlson)
Date: Wed, 16 Jan 2008 16:03:14 -0200
Subject: [Fedora-xen] CPU management
Message-ID: <dee2b60c0801161003q5196635bl714f6217bb41dfbe@mail.gmail.com>

Hi!

I will have servers with different CPU specification:
Quad core, dua core, one core.

Each core appears as one VCPU for xen?

How the management works when there is only one core, dual core and quad core?

Suppose that I have 2 guests and for the quad core processor I give 2
VCPU to the dom0 and one for each domU. How it is managed? If DomU
needs more CPU, it can use idle CPU from Dom0?  If DomU is using idle
CPU from Dom0 and Dom0 starts to need CPU, it will have their slice
back?

Thanks in advance.

Regards,
-- 
Augusto Castelan Carlson



From debian at herakles.homelinux.org  Thu Jan 17 00:30:04 2008
From: debian at herakles.homelinux.org (John Summerfield)
Date: Thu, 17 Jan 2008 09:30:04 +0900
Subject: [Fedora-xen] KVM: unhandled exception
In-Reply-To: <478DD05A.1080204@qumranet.com>
References: <478D9241.5050401@herakles.homelinux.org>
	<478DD05A.1080204@qumranet.com>
Message-ID: <478EA18C.1040701@herakles.homelinux.org>

Avi Kivity wrote:
> John Summerfield wrote:
>> [root at potoroo ~]# /usr/bin/qemu-kvm -M pc -m 128 -smp 1 -monitor pty 
>> -no-acpi -boot c -hda /var/lib/xen/images/rto-test.img -net 
>> nic,macaddr=00:16:3e:31:8a:8f,vlan=0 -net tap,fd=13,script=,vlan=0 
>> -usb -usbdevice tablet -vnc 0.0.0.0:0
>> char device redirected to /dev/pts/35
>> unhandled vm exit:  0x9
>> rax 000000000000001f rbx 000000000003f530 rcx 00000000000000ff rdx 
>> 000000000000001f
>> rsi 0000000000000000 rdi 0000000000000063 rsp 000000000003f40c rbp 
>> 000000000003f458
>> r8  0000000000000000 r9  0000000000000000 r10 0000000000000000 r11 
>> 0000000000000000
>> r12 0000000000000000 r13 0000000000000000 r14 0000000000000000 r15 
>> 0000000000000000
>> rip 000000008051ecc3 rflags 00010246
>> cs 0008 (00000000/ffffffff p 1 dpl 0 db 1 s 1 type b l 0 g 1 avl 0)
>> ds 0023 (00000000/ffffffff p 1 dpl 3 db 1 s 1 type 3 l 0 g 1 avl 0)
>> es 0023 (00000000/ffffffff p 1 dpl 3 db 1 s 1 type 3 l 0 g 1 avl 0)
>> ss 0010 (00000000/ffffffff p 1 dpl 0 db 1 s 1 type 3 l 0 g 1 avl 0)
>> fs 0030 (ffdff000/00001fff p 1 dpl 0 db 1 s 1 type 3 l 0 g 1 avl 0)
>> gs 0000 (00000000/0000ffff p 1 dpl 0 db 0 s 1 type 3 l 0 g 0 avl 0)
>> tr 0028 (80042000/000020ab p 1 dpl 0 db 0 s 0 type b l 0 g 0 avl 0)
>> ldt 0000 (00000000/ffffffff p 0 dpl 0 db 0 s 0 type 0 l 0 g 0 avl 0)
>> gdt 8003f000/3ff
>> idt 8003f400/7ff
>> cr0 e0000011 cr2 63 cr3 305000 cr4 20 cr8 0 efer 0
>> Aborted
>> [root at potoroo ~]#
>>
>>
>> I created the file /var/lib/xen/images/rto-test.img by installing 
>> Windows XP to the point it reboots.
>>
> 
> Did you also install it with -no-acpi?  What happens if you drop that 
> option?
> 

That commandline is copied from virt-manager's log, where it was 
accompanied by similar, maybe exactly the same, registers dump and the 
same error.


What I'm seeking is information about what the error means; without it 
users have almost no chance of fixing the problem themselves.


Without "-no-acpi" it runs at 105% or so CPU. vncviewer::5900 connects 
but does not open a window.
[root at potoroo ~]# lsof -i | grep -E '*:5[0-9]{3}\>'
xinetd    2180    root    5u  IPv6   7547       TCP *:5902 (LISTEN)
Xvnc      2456    root    5u  IPv4   8354       TCP *:5966 (LISTEN)
Xvnc      2456    root    6u  IPv4   8355       TCP *:5866 (LISTEN)
Xvnc      2456    root   48u  IPv4  22337       TCP 
localhost.localdomain:5966->localhost.localdomain:47032 (ESTABLISHED)
Xvnc      2500  summer    5u  IPv4   8473       TCP *:5903 (LISTEN)
Xvnc      2500  summer    6u  IPv4   8474       TCP *:5803 (LISTEN)
vncviewer 5533  summer    4u  IPv4  22336       TCP 
localhost.localdomain:47032->localhost.localdomain:5966 (ESTABLISHED)
qemu-kvm  5604    root    8u  IPv4  22589       TCP *:5900 (LISTEN)
vncviewer 5615    root    4u  IPv4  22608       TCP 
localhost.localdomain:34608->localhost.localdomain:5900 (ESTABLISHED)
[root at potoroo ~]#



-- 

Cheers
John

-- spambait
1aaaaaaa at coco.merseine.nu  Z1aaaaaaa at coco.merseine.nu
-- Advice
http://webfoot.com/advice/email.top.php
http://www.catb.org/~esr/faqs/smart-questions.html
http://support.microsoft.com/kb/555375

You cannot reply off-list:-)



From debian at herakles.homelinux.org  Thu Jan 17 00:50:21 2008
From: debian at herakles.homelinux.org (John Summerfield)
Date: Thu, 17 Jan 2008 09:50:21 +0900
Subject: [Fedora-xen] virt* source
In-Reply-To: <478E0959.2050603@redhat.com>
References: <47855370.90501@herakles.homelinux.org>	<478738F2.7030306@redhat.com>	<4787742C.1080306@herakles.homelinux.org>	<478C93E0.90701@redhat.com>	<478D43B4.3020807@herakles.homelinux.org>
	<478E0959.2050603@redhat.com>
Message-ID: <478EA64D.7090805@herakles.homelinux.org>

Richard W.M. Jones wrote:
> John Summerfield wrote:

Thanks Rich

>> I am unfamiliar with the tools I need to put that statement to the 
>> test. INSTALL says to run ./configure, but there is no ./configure to 
>> run.
>>
>> The website does say how to get the source with hg, and how to submit 
>> changes, but I can't see how to go from the checkout to building and 
>> installing.
> 
> I'm not sure which INSTALL file you're reading, but once you've got the 
> source for virtinst--devel from hg you need to use the standard python 
> way to build it.  Try:

The one checked out in the source tree, one of thse:
virt-manager--devel/INSTALL
virt-viewer--devel/INSTALL


> 
>   python setup.py --help

That seems likely to work for one of the four. I've checked out 
virt-manager-web--devel but not yet looked at it.
> 
> If this is Fedora, another, better route to go down is to build it from 
> the .src.rpm using rpmbuild.  Try the first suggestion on this page:
> 
>   http://fedoranews.org/tchung/rpmbuild/

I do not want to replace the standard F8 software, but I do want to be 
able to build and run the latest from the Hg repo.

You snipped my actual question and its rationale:
<<Z
Where is the documentation?

I do want to use alternative binaries (but then again I don't), but I do 
not wish to replace any standard part of F8.
Z

That precludes the use of rpmbuild (unless the rpm is relocatable).


-- 

Cheers
John

-- spambait
1aaaaaaa at coco.merseine.nu  Z1aaaaaaa at coco.merseine.nu
-- Advice
http://webfoot.com/advice/email.top.php
http://www.catb.org/~esr/faqs/smart-questions.html
http://support.microsoft.com/kb/555375

You cannot reply off-list:-)



From fulko.hew at gmail.com  Thu Jan 17 00:56:02 2008
From: fulko.hew at gmail.com (Fulko Hew)
Date: Wed, 16 Jan 2008 19:56:02 -0500
Subject: [Fedora-xen] where is XEN/VM networking defined?
Message-ID: <8204a4fe0801161656i5fd9e209q283af03fcc458807@mail.gmail.com>

I've just started playing with virtualization on F8
and (amongst other things...) I'm having a hard time
figuring out:

a) what I need to do to get IP networking properly
   working between VMs and the outside world.
b) where/what networking scripts/config files are VM
   related, and that are run at system startup time,
   or even VM startup time???
c) what are my options for VM-to-world networking?
d) what options/techniques does:
   'System->Virtual Machine Manager' choose when
   reconfig'ing the host system and defining how
   the VM is started/connected.

I'm specifically interested in QEMU based VMs, because:
a) I don't have the hardware for KQEMU based VMs,
b) I haven't been able to figure out how to build
   a XEN based VM either.

So when running my QEMU based VMs I'm (currently)
just booting a std kernel, not the XEN based kernel.

I've tried RTFM'ing and I've tried searching back a few
months on this list for clues, and haven't (yet) found
a description of the networking options, or how or what
I need to do to get it to work properly.  Is there a
good HowTo somewhere?

TIA
Fulko
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/fedora-xen/attachments/20080116/25cf087e/attachment.htm>

From dmourati at gmail.com  Thu Jan 17 01:18:31 2008
From: dmourati at gmail.com (Demetri Mouratis)
Date: Wed, 16 Jan 2008 17:18:31 -0800
Subject: [Fedora-xen] where is XEN/VM networking defined?
In-Reply-To: <8204a4fe0801161656i5fd9e209q283af03fcc458807@mail.gmail.com>
References: <8204a4fe0801161656i5fd9e209q283af03fcc458807@mail.gmail.com>
Message-ID: <3cc2cbc40801161718n133a5a2dn804a3eda926cd815@mail.gmail.com>

Seen this:

http://wiki.xensource.com/xenwiki/XenNetworking

-D
On Jan 16, 2008 4:56 PM, Fulko Hew <fulko.hew at gmail.com> wrote:
>
> I've just started playing with virtualization on F8
> and (amongst other things...) I'm having a hard time
> figuring out:
>
> a) what I need to do to get IP networking properly
>    working between VMs and the outside world.
> b) where/what networking scripts/config files are VM
>    related, and that are run at system startup time,
>    or even VM startup time???
>  c) what are my options for VM-to-world networking?
> d) what options/techniques does:
>    'System->Virtual Machine Manager' choose when
>    reconfig'ing the host system and defining how
>    the VM is started/connected.
>
> I'm specifically interested in QEMU based VMs, because:
>  a) I don't have the hardware for KQEMU based VMs,
> b) I haven't been able to figure out how to build
>    a XEN based VM either.
>
> So when running my QEMU based VMs I'm (currently)
> just booting a std kernel, not the XEN based kernel.
>
>  I've tried RTFM'ing and I've tried searching back a few
> months on this list for clues, and haven't (yet) found
> a description of the networking options, or how or what
> I need to do to get it to work properly.  Is there a
> good HowTo somewhere?
>
>  TIA
> Fulko
>
>
> --
> Fedora-xen mailing list
> Fedora-xen at redhat.com
> https://www.redhat.com/mailman/listinfo/fedora-xen
>
>



From fulko.hew at gmail.com  Thu Jan 17 01:49:30 2008
From: fulko.hew at gmail.com (Fulko Hew)
Date: Wed, 16 Jan 2008 20:49:30 -0500
Subject: [Fedora-xen] where is XEN/VM networking defined?
In-Reply-To: <3cc2cbc40801161718n133a5a2dn804a3eda926cd815@mail.gmail.com>
References: <8204a4fe0801161656i5fd9e209q283af03fcc458807@mail.gmail.com>
	<3cc2cbc40801161718n133a5a2dn804a3eda926cd815@mail.gmail.com>
Message-ID: <8204a4fe0801161749s6b665730w773a1ebabf9d35b@mail.gmail.com>

On Jan 16, 2008 8:18 PM, Demetri Mouratis <dmourati at gmail.com> wrote:

> Seen this:
>
> http://wiki.xensource.com/xenwiki/XenNetworking


Yes, but, I guess I need to read it a number of more times
before I'll be able to try to map the techniques and naming
conventions mentioned on that page, to what I see
happening (or not happening in some cases) in F8.

On Jan 16, 2008 4:56 PM, Fulko Hew <fulko.hew at gmail.com> wrote:
> >
> > I've just started playing with virtualization on F8
> > and (amongst other things...) I'm having a hard time
> > figuring out:
> >
> > a) what I need to do to get IP networking properly
> >    working between VMs and the outside world.
> > b) where/what networking scripts/config files are VM
> >    related, and that are run at system startup time,
> >    or even VM startup time???
> >  c) what are my options for VM-to-world networking?
> > d) what options/techniques does:
> >    'System->Virtual Machine Manager' choose when
> >    reconfig'ing the host system and defining how
> >    the VM is started/connected.
> >
> > I'm specifically interested in QEMU based VMs, because:
> >  a) I don't have the hardware for KQEMU based VMs,
> > b) I haven't been able to figure out how to build
> >    a XEN based VM either.
> >
> > So when running my QEMU based VMs I'm (currently)
> > just booting a std kernel, not the XEN based kernel.
> >
> >  I've tried RTFM'ing and I've tried searching back a few
> > months on this list for clues, and haven't (yet) found
> > a description of the networking options, or how or what
> > I need to do to get it to work properly.  Is there a
> > good HowTo somewhere?
> >
> >  TIA
> > Fulko
> <https://www.redhat.com/mailman/listinfo/fedora-xen>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/fedora-xen/attachments/20080116/c785d968/attachment.htm>

From debian at herakles.homelinux.org  Thu Jan 17 03:22:30 2008
From: debian at herakles.homelinux.org (John Summerfield)
Date: Thu, 17 Jan 2008 12:22:30 +0900
Subject: [Fedora-xen] CPU management
In-Reply-To: <dee2b60c0801161003q5196635bl714f6217bb41dfbe@mail.gmail.com>
References: <dee2b60c0801161003q5196635bl714f6217bb41dfbe@mail.gmail.com>
Message-ID: <478EC9F6.2040401@herakles.homelinux.org>

Augusto Castelan Carlson wrote:
> Hi!
> 
> I will have servers with different CPU specification:
> Quad core, dua core, one core.
> 
> Each core appears as one VCPU for xen?
Yes

> 
> How the management works when there is only one core, dual core and quad core?
> 
> Suppose that I have 2 guests and for the quad core processor I give 2
> VCPU to the dom0 and one for each domU. How it is managed? If DomU
> needs more CPU, it can use idle CPU from Dom0?  If DomU is using idle
> CPU from Dom0 and Dom0 starts to need CPU, it will have their slice
> back?

The CPUs are not dedicated. I've not tried specifying more CPUs than I 
have, but I'm sure it's mentioned in the docs. I would expect it to work.

If you give any guest only one CPU, it will only use one CPU at a time, 
but not necessarily the same one all the time. If you want a guest to be 
able to use more than one CPU at a time, you need to specify two (or 
more) CPUs.

I think you can dynamically change the number of CPUs, but you would 
need to check each guest OS to see whether it's supported by that guest.



-- 

Cheers
John

-- spambait
1aaaaaaa at coco.merseine.nu  Z1aaaaaaa at coco.merseine.nu
-- Advice
http://webfoot.com/advice/email.top.php
http://www.catb.org/~esr/faqs/smart-questions.html
http://support.microsoft.com/kb/555375

You cannot reply off-list:-)



From debian at herakles.homelinux.org  Fri Jan 18 01:50:53 2008
From: debian at herakles.homelinux.org (John Summerfield)
Date: Fri, 18 Jan 2008 10:50:53 +0900
Subject: [Fedora-xen] CPU management
In-Reply-To: <478EC9F6.2040401@herakles.homelinux.org>
References: <dee2b60c0801161003q5196635bl714f6217bb41dfbe@mail.gmail.com>
	<478EC9F6.2040401@herakles.homelinux.org>
Message-ID: <200801181050.54178.debian@herakles.homelinux.org>

On Thursday 17 January 2008 12:22:30 pm John Summerfield wrote:
> The CPUs are not dedicated. I've not tried specifying more CPUs than I
> have, but I'm sure it's mentioned in the docs. I would expect it to work.
>
> If you give any guest only one CPU, it will only use one CPU at a time,
> but not necessarily the same one all the time. If you want a guest to be
> able to use more than one CPU at a time, you need to specify two (or
> more) CPUs.
>
> I think you can dynamically change the number of CPUs, but you would
> need to check each guest OS to see whether it's supported by that guest.


There's too much nonsense here; since I wrote that I've been editing some xen 
domain configurations using vim, and I see one _can_ assign a particular 
domain to a particular CPU, and one can specify that a particular domain can 
use specific CPUs.

Whether libvirt supports that's another matter. I've not noticed that it does.



From debian at herakles.homelinux.org  Fri Jan 18 02:21:45 2008
From: debian at herakles.homelinux.org (John Summerfield)
Date: Fri, 18 Jan 2008 11:21:45 +0900
Subject: [Fedora-xen] xm create -c recovery fails
Message-ID: <200801181121.45714.debian@herakles.homelinux.org>

I'm running F8, xen-3.1.2-1.fc8, 2.6.21.7-2890.fc9xen.

I have a xen configuration which contains this stanza:
disk = [ 'file:/var/lib/xen/images/recovery.img,hda,w'
       , 'file:/var/lib/xen/images/WindowsXP.img,hdb,w'
#      , ',hdc:cdrom,r'
       , 'phy:hda,ioemu:hdd,r'
       ]

If I comment out the line containing "'phy:hda,ioemu:hdd,r' then the xm create 
line works and the guest starts up and runs fine. Whether I have "ioemu" 
doesn't make any obvious difference, google suggested it.

With the stanza as above, it fails:
[root at potoroo ~]# time xm create -c recovery
Using config file "/etc/xen/recovery".
Error: Device 5696 (vbd) could not be connected. Hotplug scripts not working.

real    1m44.750s
user    0m0.080s
sys     0m0.067s
[root at potoroo ~]# 

The only other thing I see is the VNC console opens, but it displays with a 
white background.

These are the messages logged to xend.log:
[2008-01-18 11:00:24 2652] INFO (image:129) buildDomain os=hvm dom=27 vcpus=1
[2008-01-18 11:00:24 2652] INFO (XendDomainInfo:1458) createDevice: vfb : 
{'vncunused': 1, 'other_config': {'vncunused': 
1}, 'uuid': '6c9425f6-7800-4325-bcd7-b917ce2f8955'}
[2008-01-18 11:00:24 2652] INFO (XendDomainInfo:1458) createDevice: vbd : 
{'uuid': '0f4b1edf-a164-6b3a-ebd2-395532720861', 'bootable': 
1, 'driver': 'paravirtualised', 'dev': 'hda', 'uname': 'file:/var/lib/xen/images/recovery.img', 'mode': 'w'}
[2008-01-18 11:00:24 2652] INFO (XendDomainInfo:1458) createDevice: vbd : 
{'uuid': '5c84f484-c9df-f60d-ccec-9a4bf7e47e64', 'bootable': 
0, 'driver': 'paravirtualised', 'dev': 'hdb', 'uname': 'file:/var/lib/xen/images/WindowsXP.img', 'mode': 'w'}
[2008-01-18 11:00:24 2652] INFO (XendDomainInfo:1458) createDevice: vbd : 
{'uuid': 'f34d1d46-dd15-7572-6661-26570af507a7', 'bootable': 
0, 'driver': 'ioemu', 'dev': 'ioemu:hdd', 'uname': 'phy:hda', 'mode': 'r'}
[2008-01-18 11:00:24 2652] INFO (XendDomainInfo:1458) createDevice: vif : 
{'bridge': 'xenbr0', 'mac': '00:16:3e:33:b1:83', 'type': 'ioemu', 'uuid': 'b5fca1da-8850-0723-bf2e-edbf7635832e'}
[2008-01-18 11:00:24 2652] INFO (image:454) spawning device 
models: /usr/lib64/xen/bin/qemu-dm 
['/usr/lib64/xen/bin/qemu-dm', '-d', '27', '-vcpus', '1', '-boot', 'cd', '-soundhw', 'sb16', '-localtime', '-serial', 'pty', '-acpi', '-usb', '-usbdevice', 'tablet', '-domain-name', 'recovery', '-net', 'nic,vlan=1,macaddr=00:16:3e:33:b1:83,model=rtl8139', '-net', 'tap,vlan=1,bridge=xenbr0', '-vnc', '127.0.0.1:0', '-vncunused', '-vncviewer']
[2008-01-18 11:00:24 2652] INFO (image:458) device model pid: 29112


"recovery" is a Debian system, I created it under KVM and I've mentioned it 
here before.

Here is the Xen configuration:
[root at potoroo xen]# cat /etc/xen/recovery | grep -Ev '^($|#)'
import os, re
arch = os.uname()[4]
if re.search('64', arch):
    arch_libdir = 'lib64'
else:
    arch_libdir = 'lib'
kernel = "/usr/lib/xen/boot/hvmloader"
builder='hvm'
memory = 128
name = "recovery"
vif = [ 'type=ioemu, bridge=xenbr0' ]
disk = [ 'file:/var/lib/xen/images/recovery.img,hda,w'
       , 'file:/var/lib/xen/images/WindowsXP.img,hdb,w'
       , 'phy:hda,ioemu:hdd,r'
       ]
device_model = '/usr/' + arch_libdir + '/xen/bin/qemu-dm'
boot="cd"
sdl=0
vnc=1
vncconsole=1
vncpasswd=''
stdvga=0
serial='pty'
soundhw='sb16'
localtime=1
usb=1
usbdevice='tablet'
[root at potoroo xen]# 



From accarlson at gmail.com  Fri Jan 18 11:00:41 2008
From: accarlson at gmail.com (Augusto Castelan Carlson)
Date: Fri, 18 Jan 2008 09:00:41 -0200
Subject: [Fedora-xen] CPU management
In-Reply-To: <200801181050.54178.debian@herakles.homelinux.org>
References: <dee2b60c0801161003q5196635bl714f6217bb41dfbe@mail.gmail.com>
	<478EC9F6.2040401@herakles.homelinux.org>
	<200801181050.54178.debian@herakles.homelinux.org>
Message-ID: <dee2b60c0801180300i71f09b4ep1ac4d70a15e10a0a@mail.gmail.com>

> There's too much nonsense here; since I wrote that I've been editing some xen
> domain configurations using vim, and I see one _can_ assign a particular
> domain to a particular CPU, and one can specify that a particular domain can
> use specific CPUs.
>
> Whether libvirt supports that's another matter. I've not noticed that it does.

I would like to be able to give, for example, 33% for dom1 and dom2
and 33% for dom0, but  I know that we can only work with VCPUs.

How can I assign a specif VCPU ou CPU do domU?

How CPU is Managend when I have one core only?

independently of having one o more VCPU/CPU, suppose that Dom0 is
idle, Dom1 is 80% CPU, and Dom2 is idle. Dom0 or Dom2 start to do some
processing, how the CPU is managed?

If there is 4 VCPU, 2 for dom0 and 1 dom1 and the other for dom2?

I hope that you can understand my doubt :-D

Thanks!

Regards,

Augusto



From rjones at redhat.com  Fri Jan 18 11:46:41 2008
From: rjones at redhat.com (Richard W.M. Jones)
Date: Fri, 18 Jan 2008 11:46:41 +0000
Subject: [Fedora-xen] CPU management
In-Reply-To: <dee2b60c0801180300i71f09b4ep1ac4d70a15e10a0a@mail.gmail.com>
References: <dee2b60c0801161003q5196635bl714f6217bb41dfbe@mail.gmail.com>	<478EC9F6.2040401@herakles.homelinux.org>	<200801181050.54178.debian@herakles.homelinux.org>
	<dee2b60c0801180300i71f09b4ep1ac4d70a15e10a0a@mail.gmail.com>
Message-ID: <479091A1.2050302@redhat.com>

> I would like to be able to give, for example, 33% for dom1 and dom2
> and 33% for dom0, but  I know that we can only work with VCPUs.

It doesn't work like this.  Guests don't normally consume CPU 
continuously (well, unless you're running something like numerical 
simulations, which I really wouldn't recommend for virtualization).

First of all, if you do nothing at all then guests' virtual CPUs are 
scheduled to run on physical CPUs at random.  When a guest starts to do 
something, a physical CPU is picked and the guest runs on that for some 
short timeslice.  You can easily have more virtual CPUs than physical 
CPUs.  If your guests are mostly idle, the this is fine.

Now you can also pin a virtual CPU to a subset of physical CPUs (or to 
just a single physical CPU).  Using virsh/libvirt:

   virsh vcpupin guest 0 1

would pin guest's virtual CPU #0 to physical CPU #1.  So now when 
guest's virtual CPU #0 wakes up to do some work, it will only be 
scheduled to run on physical CPU #1, if necessary waiting until physical 
CPU #1 becomes free.

If you had a quad-core machine (4 physical CPUs) and 1 dom0 + 3 guests, 
and each dom0/guest has a single virtual CPU, then you might consider 
pinning the dom0 and each guest to a separate physical CPU.  Whether 
this is a good idea or not depends on what each guest will be doing and 
requires careful analysis and performance monitoring.

Use the command:

   virt-top -1

to show which guests are running on which physical CPUs in real time.

Rich.

-- 
Emerging Technologies, Red Hat - http://et.redhat.com/~rjones/
Registered Address: Red Hat UK Ltd, Amberley Place, 107-111 Peascod
Street, Windsor, Berkshire, SL4 1TE, United Kingdom.  Registered in
England and Wales under Company Registration No. 03798903
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 3237 bytes
Desc: S/MIME Cryptographic Signature
URL: <http://listman.redhat.com/archives/fedora-xen/attachments/20080118/9690463b/attachment.bin>

From Dustin.Henning at prd-inc.com  Fri Jan 18 12:54:47 2008
From: Dustin.Henning at prd-inc.com (Dustin Henning)
Date: Fri, 18 Jan 2008 07:54:47 -0500
Subject: [Fedora-xen] xm create -c recovery fails
In-Reply-To: <200801181121.45714.debian@herakles.homelinux.org>
References: <200801181121.45714.debian@herakles.homelinux.org>
Message-ID: <001001c859d1$4e4c4f80$eae4ee80$@Henning@prd-inc.com>

Try this:
disk = [ 'file:/var/lib/xen/images/recovery.img,hda,w'
       , 'file:/var/lib/xen/images/WindowsXP.img,hdb,w'
#      , ',hdc:cdrom,r'
       , 'phy:/dev/hda,hdd,r'
       ]

Dustin

-----Original Message-----
From: fedora-xen-bounces at redhat.com [mailto:fedora-xen-bounces at redhat.com] On Behalf Of John Summerfield
Sent: Thursday, January 17, 2008 21:22
To: fedora-xen at redhat.com
Subject: [Fedora-xen] xm create -c recovery fails

I'm running F8, xen-3.1.2-1.fc8, 2.6.21.7-2890.fc9xen.

I have a xen configuration which contains this stanza:
disk = [ 'file:/var/lib/xen/images/recovery.img,hda,w'
       , 'file:/var/lib/xen/images/WindowsXP.img,hdb,w'
#      , ',hdc:cdrom,r'
       , 'phy:hda,ioemu:hdd,r'
       ]

If I comment out the line containing "'phy:hda,ioemu:hdd,r' then the xm create 
line works and the guest starts up and runs fine. Whether I have "ioemu" 
doesn't make any obvious difference, google suggested it.

With the stanza as above, it fails:
[root at potoroo ~]# time xm create -c recovery
Using config file "/etc/xen/recovery".
Error: Device 5696 (vbd) could not be connected. Hotplug scripts not working.

real    1m44.750s
user    0m0.080s
sys     0m0.067s
[root at potoroo ~]# 

The only other thing I see is the VNC console opens, but it displays with a 
white background.

These are the messages logged to xend.log:
[2008-01-18 11:00:24 2652] INFO (image:129) buildDomain os=hvm dom=27 vcpus=1
[2008-01-18 11:00:24 2652] INFO (XendDomainInfo:1458) createDevice: vfb : 
{'vncunused': 1, 'other_config': {'vncunused': 
1}, 'uuid': '6c9425f6-7800-4325-bcd7-b917ce2f8955'}
[2008-01-18 11:00:24 2652] INFO (XendDomainInfo:1458) createDevice: vbd : 
{'uuid': '0f4b1edf-a164-6b3a-ebd2-395532720861', 'bootable': 
1, 'driver': 'paravirtualised', 'dev': 'hda', 'uname': 'file:/var/lib/xen/images/recovery.img', 'mode': 'w'}
[2008-01-18 11:00:24 2652] INFO (XendDomainInfo:1458) createDevice: vbd : 
{'uuid': '5c84f484-c9df-f60d-ccec-9a4bf7e47e64', 'bootable': 
0, 'driver': 'paravirtualised', 'dev': 'hdb', 'uname': 'file:/var/lib/xen/images/WindowsXP.img', 'mode': 'w'}
[2008-01-18 11:00:24 2652] INFO (XendDomainInfo:1458) createDevice: vbd : 
{'uuid': 'f34d1d46-dd15-7572-6661-26570af507a7', 'bootable': 
0, 'driver': 'ioemu', 'dev': 'ioemu:hdd', 'uname': 'phy:hda', 'mode': 'r'}
[2008-01-18 11:00:24 2652] INFO (XendDomainInfo:1458) createDevice: vif : 
{'bridge': 'xenbr0', 'mac': '00:16:3e:33:b1:83', 'type': 'ioemu', 'uuid': 'b5fca1da-8850-0723-bf2e-edbf7635832e'}
[2008-01-18 11:00:24 2652] INFO (image:454) spawning device 
models: /usr/lib64/xen/bin/qemu-dm 
['/usr/lib64/xen/bin/qemu-dm', '-d', '27', '-vcpus', '1', '-boot', 'cd', '-soundhw', 'sb16', '-localtime', '-serial', 'pty', '-acpi', '-usb', '-usbdevice', 'tablet', '-domain-name', 'recovery', '-net', 'nic,vlan=1,macaddr=00:16:3e:33:b1:83,model=rtl8139', '-net', 'tap,vlan=1,bridge=xenbr0', '-vnc', '127.0.0.1:0', '-vncunused', '-vncviewer']
[2008-01-18 11:00:24 2652] INFO (image:458) device model pid: 29112


"recovery" is a Debian system, I created it under KVM and I've mentioned it 
here before.

Here is the Xen configuration:
[root at potoroo xen]# cat /etc/xen/recovery | grep -Ev '^($|#)'
import os, re
arch = os.uname()[4]
if re.search('64', arch):
    arch_libdir = 'lib64'
else:
    arch_libdir = 'lib'
kernel = "/usr/lib/xen/boot/hvmloader"
builder='hvm'
memory = 128
name = "recovery"
vif = [ 'type=ioemu, bridge=xenbr0' ]
disk = [ 'file:/var/lib/xen/images/recovery.img,hda,w'
       , 'file:/var/lib/xen/images/WindowsXP.img,hdb,w'
       , 'phy:hda,ioemu:hdd,r'
       ]
device_model = '/usr/' + arch_libdir + '/xen/bin/qemu-dm'
boot="cd"
sdl=0
vnc=1
vncconsole=1
vncpasswd=''
stdvga=0
serial='pty'
soundhw='sb16'
localtime=1
usb=1
usbdevice='tablet'
[root at potoroo xen]# 

--
Fedora-xen mailing list
Fedora-xen at redhat.com
https://www.redhat.com/mailman/listinfo/fedora-xen





From debian at herakles.homelinux.org  Fri Jan 18 13:51:53 2008
From: debian at herakles.homelinux.org (John Summerfield)
Date: Fri, 18 Jan 2008 22:51:53 +0900
Subject: [Fedora-xen] CPU management
In-Reply-To: <479091A1.2050302@redhat.com>
References: <dee2b60c0801161003q5196635bl714f6217bb41dfbe@mail.gmail.com>	<478EC9F6.2040401@herakles.homelinux.org>	<200801181050.54178.debian@herakles.homelinux.org>	<dee2b60c0801180300i71f09b4ep1ac4d70a15e10a0a@mail.gmail.com>
	<479091A1.2050302@redhat.com>
Message-ID: <4790AEF9.9010107@herakles.homelinux.org>

Richard W.M. Jones wrote:
>> I would like to be able to give, for example, 33% for dom1 and dom2
>> and 33% for dom0, but  I know that we can only work with VCPUs.
> 
> It doesn't work like this.  Guests don't normally consume CPU 
> continuously (well, unless you're running something like numerical 
> simulations, which I really wouldn't recommend for virtualization).
> 
> First of all, if you do nothing at all then guests' virtual CPUs are 
> scheduled to run on physical CPUs at random.  When a guest starts to do 
> something, a physical CPU is picked and the guest runs on that for some 
> short timeslice.  You can easily have more virtual CPUs than physical 
> CPUs.  If your guests are mostly idle, the this is fine.

Something that has occurred to me, and which troubled someone else, is 
that if the host is busy running Firefox, OOo and other desktop software 
as well as guest operating systems, those guests probably are not going 
to perform well.

I think Xen will perform better in this sort of environment than KVM.

The virtualisation software I'm most familiar with (from a theoretic 
POV) is IBM's VM which runs on its mainframes. It's a hypervisor only, 
and all users have their own virtual computer, and it's those virtual 
computers that do the real work.

Tuning VM to work best is an intricate job.

VM is now about 40 years old.


-- 

Cheers
John

-- spambait
1aaaaaaa at coco.merseine.nu  Z1aaaaaaa at coco.merseine.nu
-- Advice
http://webfoot.com/advice/email.top.php
http://www.catb.org/~esr/faqs/smart-questions.html
http://support.microsoft.com/kb/555375

You cannot reply off-list:-)



From Dustin.Henning at prd-inc.com  Fri Jan 18 13:57:36 2008
From: Dustin.Henning at prd-inc.com (Dustin Henning)
Date: Fri, 18 Jan 2008 08:57:36 -0500
Subject: [Fedora-xen] CPU management
In-Reply-To: <4790AEF9.9010107@herakles.homelinux.org>
References: <dee2b60c0801161003q5196635bl714f6217bb41dfbe@mail.gmail.com>	<478EC9F6.2040401@herakles.homelinux.org>	<200801181050.54178.debian@herakles.homelinux.org>	<dee2b60c0801180300i71f09b4ep1ac4d70a15e10a0a@mail.gmail.com>	<479091A1.2050302@redhat.com>
	<4790AEF9.9010107@herakles.homelinux.org>
Message-ID: <001801c859da$14fe1e80$3efa5b80$@Henning@prd-inc.com>

That being noted, in Xen, I believe that a CPU is randomly selected and pinned to a VCPU for the entire session of the VM (this may only apply to HVMs), whereas, according to someone, virsh uses any available CPU.  I assign my CPUs to my VMs for that reason.  However, here is some information on scheduling processor usage as well:
http://wiki.xensource.com/xenwiki/Scheduling?highlight=%28scheduling%29
It's not especially detailed, but it may be what you are looking for, and while virsh may have a similar method, I am unfamiliar with virsh.
Dustin

-----Original Message-----
From: fedora-xen-bounces at redhat.com [mailto:fedora-xen-bounces at redhat.com] On Behalf Of John Summerfield
Sent: Friday, January 18, 2008 08:52
To: fedora-xen at redhat.com
Subject: Re: [Fedora-xen] CPU management

Richard W.M. Jones wrote:
>> I would like to be able to give, for example, 33% for dom1 and dom2
>> and 33% for dom0, but  I know that we can only work with VCPUs.
> 
> It doesn't work like this.  Guests don't normally consume CPU 
> continuously (well, unless you're running something like numerical 
> simulations, which I really wouldn't recommend for virtualization).
> 
> First of all, if you do nothing at all then guests' virtual CPUs are 
> scheduled to run on physical CPUs at random.  When a guest starts to do 
> something, a physical CPU is picked and the guest runs on that for some 
> short timeslice.  You can easily have more virtual CPUs than physical 
> CPUs.  If your guests are mostly idle, the this is fine.

Something that has occurred to me, and which troubled someone else, is 
that if the host is busy running Firefox, OOo and other desktop software 
as well as guest operating systems, those guests probably are not going 
to perform well.

I think Xen will perform better in this sort of environment than KVM.

The virtualisation software I'm most familiar with (from a theoretic 
POV) is IBM's VM which runs on its mainframes. It's a hypervisor only, 
and all users have their own virtual computer, and it's those virtual 
computers that do the real work.

Tuning VM to work best is an intricate job.

VM is now about 40 years old.


-- 

Cheers
John

-- spambait
1aaaaaaa at coco.merseine.nu  Z1aaaaaaa at coco.merseine.nu
-- Advice
http://webfoot.com/advice/email.top.php
http://www.catb.org/~esr/faqs/smart-questions.html
http://support.microsoft.com/kb/555375

You cannot reply off-list:-)

--
Fedora-xen mailing list
Fedora-xen at redhat.com
https://www.redhat.com/mailman/listinfo/fedora-xen





From debian at herakles.homelinux.org  Fri Jan 18 14:09:13 2008
From: debian at herakles.homelinux.org (John Summerfield)
Date: Fri, 18 Jan 2008 23:09:13 +0900
Subject: [Fedora-xen] xm create -c recovery fails
In-Reply-To: <001001c859d1$4e4c4f80$eae4ee80$@Henning@prd-inc.com>
References: <200801181121.45714.debian@herakles.homelinux.org>
	<001001c859d1$4e4c4f80$eae4ee80$@Henning@prd-inc.com>
Message-ID: <200801182309.13292.debian@herakles.homelinux.org>

On Friday 18 January 2008 09:54:47 pm Dustin Henning wrote:
> Try this:
> disk = [ 'file:/var/lib/xen/images/recovery.img,hda,w'
>        , 'file:/var/lib/xen/images/WindowsXP.img,hdb,w'
> #      , ',hdc:cdrom,r'
>        , 'phy:/dev/hda,hdd,r'
>        ]
>
> Dustin

Same:
[root at potoroo ~]# time xm create -c recovery
Using config file "/etc/xen/recovery".
Error: Device 5696 (vbd) could not be connected. Hotplug scripts not working.

real    1m44.270s
user    0m0.085s
sys     0m0.046s
[root at potoroo ~]# cat /etc/xen/recovery | grep -Ev '^($|#)'
import os, re
arch = os.uname()[4]
if re.search('64', arch):
    arch_libdir = 'lib64'
else:
    arch_libdir = 'lib'
kernel = "/usr/lib/xen/boot/hvmloader"
builder='hvm'
memory = 128
name = "recovery"
vif = [ 'type=ioemu, bridge=xenbr0' ]
disk = [ 'file:/var/lib/xen/images/recovery.img,hda,w'
       , 'file:/var/lib/xen/images/WindowsXP.img,hdb,w'
       , 'phy:/dev/hda,hdd,r'
       ]

etc
I don't believe /dev/hda has a different meaning from hda, and it seems that 
iomem (which I've not seen documented in this context) specifies "not 
paravirtualised" I/O. I got that from google when trying to solve the problem 
before posting to the list.
>
> -----Original Message-----
> From: fedora-xen-bounces at redhat.com [mailto:fedora-xen-bounces at redhat.com]
> On Behalf Of John Summerfield Sent: Thursday, January 17, 2008 21:22
> To: fedora-xen at redhat.com
> Subject: [Fedora-xen] xm create -c recovery fails
>
> I'm running F8, xen-3.1.2-1.fc8, 2.6.21.7-2890.fc9xen.
>
> I have a xen configuration which contains this stanza:
> disk = [ 'file:/var/lib/xen/images/recovery.img,hda,w'
>        , 'file:/var/lib/xen/images/WindowsXP.img,hdb,w'
> #      , ',hdc:cdrom,r'
>        , 'phy:hda,ioemu:hdd,r'
>        ]
>
> If I comment out the line containing "'phy:hda,ioemu:hdd,r' then the xm
> create line works and the guest starts up and runs fine. Whether I have
> "ioemu" doesn't make any obvious difference, google suggested it.
>
> With the stanza as above, it fails:
> [root at potoroo ~]# time xm create -c recovery
> Using config file "/etc/xen/recovery".
> Error: Device 5696 (vbd) could not be connected. Hotplug scripts not
> working.
>
> real    1m44.750s
> user    0m0.080s
> sys     0m0.067s
> [root at potoroo ~]#
>
> The only other thing I see is the VNC console opens, but it displays with a
> white background.
>
> These are the messages logged to xend.log:
> [2008-01-18 11:00:24 2652] INFO (image:129) buildDomain os=hvm dom=27
> vcpus=1 [2008-01-18 11:00:24 2652] INFO (XendDomainInfo:1458) createDevice:
> vfb : {'vncunused': 1, 'other_config': {'vncunused':
> 1}, 'uuid': '6c9425f6-7800-4325-bcd7-b917ce2f8955'}
> [2008-01-18 11:00:24 2652] INFO (XendDomainInfo:1458) createDevice: vbd :
> {'uuid': '0f4b1edf-a164-6b3a-ebd2-395532720861', 'bootable':
> 1, 'driver': 'paravirtualised', 'dev': 'hda', 'uname':
> 'file:/var/lib/xen/images/recovery.img', 'mode': 'w'} [2008-01-18 11:00:24
> 2652] INFO (XendDomainInfo:1458) createDevice: vbd : {'uuid':
> '5c84f484-c9df-f60d-ccec-9a4bf7e47e64', 'bootable':
> 0, 'driver': 'paravirtualised', 'dev': 'hdb', 'uname':
> 'file:/var/lib/xen/images/WindowsXP.img', 'mode': 'w'} [2008-01-18 11:00:24
> 2652] INFO (XendDomainInfo:1458) createDevice: vbd : {'uuid':
> 'f34d1d46-dd15-7572-6661-26570af507a7', 'bootable':
> 0, 'driver': 'ioemu', 'dev': 'ioemu:hdd', 'uname': 'phy:hda', 'mode': 'r'}
> [2008-01-18 11:00:24 2652] INFO (XendDomainInfo:1458) createDevice: vif :
> {'bridge': 'xenbr0', 'mac': '00:16:3e:33:b1:83', 'type': 'ioemu', 'uuid':
> 'b5fca1da-8850-0723-bf2e-edbf7635832e'} [2008-01-18 11:00:24 2652] INFO
> (image:454) spawning device
> models: /usr/lib64/xen/bin/qemu-dm
> ['/usr/lib64/xen/bin/qemu-dm', '-d', '27', '-vcpus', '1', '-boot', 'cd',
> '-soundhw', 'sb16', '-localtime', '-serial', 'pty', '-acpi', '-usb',
> '-usbdevice', 'tablet', '-domain-name', 'recovery', '-net',
> 'nic,vlan=1,macaddr=00:16:3e:33:b1:83,model=rtl8139', '-net',
> 'tap,vlan=1,bridge=xenbr0', '-vnc', '127.0.0.1:0', '-vncunused',
> '-vncviewer'] [2008-01-18 11:00:24 2652] INFO (image:458) device model pid:
> 29112
>
>
> "recovery" is a Debian system, I created it under KVM and I've mentioned it
> here before.
>
> Here is the Xen configuration:
> [root at potoroo xen]# cat /etc/xen/recovery | grep -Ev '^($|#)'
> import os, re
> arch = os.uname()[4]
> if re.search('64', arch):
>     arch_libdir = 'lib64'
> else:
>     arch_libdir = 'lib'
> kernel = "/usr/lib/xen/boot/hvmloader"
> builder='hvm'
> memory = 128
> name = "recovery"
> vif = [ 'type=ioemu, bridge=xenbr0' ]
> disk = [ 'file:/var/lib/xen/images/recovery.img,hda,w'
>        , 'file:/var/lib/xen/images/WindowsXP.img,hdb,w'
>        , 'phy:hda,ioemu:hdd,r'
>        ]
> device_model = '/usr/' + arch_libdir + '/xen/bin/qemu-dm'
> boot="cd"
> sdl=0
> vnc=1
> vncconsole=1
> vncpasswd=''
> stdvga=0
> serial='pty'
> soundhw='sb16'
> localtime=1
> usb=1
> usbdevice='tablet'
> [root at potoroo xen]#
>
> --
> Fedora-xen mailing list
> Fedora-xen at redhat.com
> https://www.redhat.com/mailman/listinfo/fedora-xen
>
>
>
> --
> Fedora-xen mailing list
> Fedora-xen at redhat.com
> https://www.redhat.com/mailman/listinfo/fedora-xen




From debian at herakles.homelinux.org  Fri Jan 18 14:33:23 2008
From: debian at herakles.homelinux.org (John Summerfield)
Date: Fri, 18 Jan 2008 23:33:23 +0900
Subject: [Fedora-xen] xm create -c recovery fails
In-Reply-To: <200801182309.13292.debian@herakles.homelinux.org>
References: <200801181121.45714.debian@herakles.homelinux.org>
	<001001c859d1$4e4c4f80$eae4ee80$@Henning@prd-inc.com>
	<200801182309.13292.debian@herakles.homelinux.org>
Message-ID: <200801182333.23688.debian@herakles.homelinux.org>

On Friday 18 January 2008 11:09:13 pm John Summerfield wrote:
> On Friday 18 January 2008 09:54:47 pm Dustin Henning wrote:
> > Try this:
> > disk = [ 'file:/var/lib/xen/images/recovery.img,hda,w'
> >        , 'file:/var/lib/xen/images/WindowsXP.img,hdb,w'
> > #      , ',hdc:cdrom,r'
> >        , 'phy:/dev/hda,hdd,r'
> >        ]
> >
> > Dustin
>


I had a bit of a dig around in /etc/xen/scripts, without comprehending a lot, 
but it seems that it's taking care not to use mounted partitions.

Oh.

This is the drive I'm booting the host from. This is F8. The drive's called 
sda, not hda.

There's a squillion kernel messages from the guest about I/O errors.
Jan 18 23:13:44 recovery kernel: or=0x04 { DriveStatusError }
Jan 18 23:13:44 recovery kernel: ide: failed opcode was: unknown
Jan 18 23:13:44 recovery kernel: hdd: task_in_intr: status=0x41 { DriveReady 
Error }
Jan 18 23:13:44 recovery kernel: hdd: task_in_intr: error=0x04 { 
DriveStatusError }
Jan 18 23:13:44 recovery kernel: ide: failed opcode was: unknown
Jan 18 23:13:44 recovery kernel: hdd: task_in_intr: status=0x41 { DriveReady 
Error }
Jan 18 23:13:44 recovery kernel: hdd: task_in_intr: error=0x04 { 
DriveStatusError }
Jan 18 23:13:44 recovery kernel: ide: failed opcode was: unknown
Jan 18 23:13:44 recovery kernel: ide1: reset: success

The kernel buffer's full of them.

It's fairly clear this is not going to work soon.

I want to run ntfsclone against Windows on the drive; I can do that on the 
host.

I see two problems:
1. Those scripts silently fail
2. Xen prevents my reading the drive in the guest.

I _know there are hazards with using the host's boot drive in the guest, but 
so long as I don't change the partition table anywhere, and don't use a 
partition rw in one place and anywhere else, I expect I avoid those hazards.


> Same:
> [root at potoroo ~]# time xm create -c recovery
> Using config file "/etc/xen/recovery".
> Error: Device 5696 (vbd) could not be connected. Hotplug scripts not
> working.
>
> real    1m44.270s
> user    0m0.085s
> sys     0m0.046s
> [root at potoroo ~]# cat /etc/xen/recovery | grep -Ev '^($|#)'
> import os, re
> arch = os.uname()[4]
> if re.search('64', arch):
>     arch_libdir = 'lib64'
> else:
>     arch_libdir = 'lib'
> kernel = "/usr/lib/xen/boot/hvmloader"
> builder='hvm'
> memory = 128
> name = "recovery"
> vif = [ 'type=ioemu, bridge=xenbr0' ]
> disk = [ 'file:/var/lib/xen/images/recovery.img,hda,w'
>        , 'file:/var/lib/xen/images/WindowsXP.img,hdb,w'
>        , 'phy:/dev/hda,hdd,r'
>        ]
>
> etc
> I don't believe /dev/hda has a different meaning from hda, and it seems
> that iomem (which I've not seen documented in this context) specifies "not
> paravirtualised" I/O. I got that from google when trying to solve the
> problem before posting to the list.
>
> > -----Original Message-----
> > From: fedora-xen-bounces at redhat.com
> > [mailto:fedora-xen-bounces at redhat.com] On Behalf Of John Summerfield
> > Sent: Thursday, January 17, 2008 21:22 To: fedora-xen at redhat.com
> > Subject: [Fedora-xen] xm create -c recovery fails
> >
> > I'm running F8, xen-3.1.2-1.fc8, 2.6.21.7-2890.fc9xen.
> >
> > I have a xen configuration which contains this stanza:
> > disk = [ 'file:/var/lib/xen/images/recovery.img,hda,w'
> >        , 'file:/var/lib/xen/images/WindowsXP.img,hdb,w'
> > #      , ',hdc:cdrom,r'
> >        , 'phy:hda,ioemu:hdd,r'
> >        ]
> >
> > If I comment out the line containing "'phy:hda,ioemu:hdd,r' then the xm
> > create line works and the guest starts up and runs fine. Whether I have
> > "ioemu" doesn't make any obvious difference, google suggested it.
> >
> > With the stanza as above, it fails:
> > [root at potoroo ~]# time xm create -c recovery
> > Using config file "/etc/xen/recovery".
> > Error: Device 5696 (vbd) could not be connected. Hotplug scripts not
> > working.
> >
> > real    1m44.750s
> > user    0m0.080s
> > sys     0m0.067s
> > [root at potoroo ~]#
> >
> > The only other thing I see is the VNC console opens, but it displays with
> > a white background.
> >
> > These are the messages logged to xend.log:
> > [2008-01-18 11:00:24 2652] INFO (image:129) buildDomain os=hvm dom=27
> > vcpus=1 [2008-01-18 11:00:24 2652] INFO (XendDomainInfo:1458)
> > createDevice: vfb : {'vncunused': 1, 'other_config': {'vncunused':
> > 1}, 'uuid': '6c9425f6-7800-4325-bcd7-b917ce2f8955'}
> > [2008-01-18 11:00:24 2652] INFO (XendDomainInfo:1458) createDevice: vbd :
> > {'uuid': '0f4b1edf-a164-6b3a-ebd2-395532720861', 'bootable':
> > 1, 'driver': 'paravirtualised', 'dev': 'hda', 'uname':
> > 'file:/var/lib/xen/images/recovery.img', 'mode': 'w'} [2008-01-18
> > 11:00:24 2652] INFO (XendDomainInfo:1458) createDevice: vbd : {'uuid':
> > '5c84f484-c9df-f60d-ccec-9a4bf7e47e64', 'bootable':
> > 0, 'driver': 'paravirtualised', 'dev': 'hdb', 'uname':
> > 'file:/var/lib/xen/images/WindowsXP.img', 'mode': 'w'} [2008-01-18
> > 11:00:24 2652] INFO (XendDomainInfo:1458) createDevice: vbd : {'uuid':
> > 'f34d1d46-dd15-7572-6661-26570af507a7', 'bootable':
> > 0, 'driver': 'ioemu', 'dev': 'ioemu:hdd', 'uname': 'phy:hda', 'mode':
> > 'r'} [2008-01-18 11:00:24 2652] INFO (XendDomainInfo:1458) createDevice:
> > vif : {'bridge': 'xenbr0', 'mac': '00:16:3e:33:b1:83', 'type': 'ioemu',
> > 'uuid': 'b5fca1da-8850-0723-bf2e-edbf7635832e'} [2008-01-18 11:00:24
> > 2652] INFO (image:454) spawning device
> > models: /usr/lib64/xen/bin/qemu-dm
> > ['/usr/lib64/xen/bin/qemu-dm', '-d', '27', '-vcpus', '1', '-boot', 'cd',
> > '-soundhw', 'sb16', '-localtime', '-serial', 'pty', '-acpi', '-usb',
> > '-usbdevice', 'tablet', '-domain-name', 'recovery', '-net',
> > 'nic,vlan=1,macaddr=00:16:3e:33:b1:83,model=rtl8139', '-net',
> > 'tap,vlan=1,bridge=xenbr0', '-vnc', '127.0.0.1:0', '-vncunused',
> > '-vncviewer'] [2008-01-18 11:00:24 2652] INFO (image:458) device model
> > pid: 29112
> >
> >
> > "recovery" is a Debian system, I created it under KVM and I've mentioned
> > it here before.
> >
> > Here is the Xen configuration:
> > [root at potoroo xen]# cat /etc/xen/recovery | grep -Ev '^($|#)'
> > import os, re
> > arch = os.uname()[4]
> > if re.search('64', arch):
> >     arch_libdir = 'lib64'
> > else:
> >     arch_libdir = 'lib'
> > kernel = "/usr/lib/xen/boot/hvmloader"
> > builder='hvm'
> > memory = 128
> > name = "recovery"
> > vif = [ 'type=ioemu, bridge=xenbr0' ]
> > disk = [ 'file:/var/lib/xen/images/recovery.img,hda,w'
> >        , 'file:/var/lib/xen/images/WindowsXP.img,hdb,w'
> >        , 'phy:hda,ioemu:hdd,r'
> >        ]
> > device_model = '/usr/' + arch_libdir + '/xen/bin/qemu-dm'
> > boot="cd"
> > sdl=0
> > vnc=1
> > vncconsole=1
> > vncpasswd=''
> > stdvga=0
> > serial='pty'
> > soundhw='sb16'
> > localtime=1
> > usb=1
> > usbdevice='tablet'
> > [root at potoroo xen]#
> >
> > --
> > Fedora-xen mailing list
> > Fedora-xen at redhat.com
> > https://www.redhat.com/mailman/listinfo/fedora-xen
> >
> >
> >
> > --
> > Fedora-xen mailing list
> > Fedora-xen at redhat.com
> > https://www.redhat.com/mailman/listinfo/fedora-xen
>
> --
> Fedora-xen mailing list
> Fedora-xen at redhat.com
> https://www.redhat.com/mailman/listinfo/fedora-xen




From Dustin.Henning at prd-inc.com  Fri Jan 18 14:53:37 2008
From: Dustin.Henning at prd-inc.com (Dustin Henning)
Date: Fri, 18 Jan 2008 09:53:37 -0500
Subject: [Fedora-xen] xm create -c recovery fails
In-Reply-To: <200801182309.13292.debian@herakles.homelinux.org>
References: <200801181121.45714.debian@herakles.homelinux.org>	<001001c859d1$4e4c4f80$eae4ee80$@Henning@prd-inc.com>
	<200801182309.13292.debian@herakles.homelinux.org>
Message-ID: <001901c859e1$e81e6980$b85b3c80$@Henning@prd-inc.com>

	I had a similar problem, and my suggestion is what solved it, but that was with moonshine, and according to the documentation, the /dev/ shouldn't need to be specified.  I didn't look unto ioemu, as I've never used it and assumed it had to do with using a different method to emulate (input output emulation vs block device emulation) since either method would be not paravirtualised by virtue of the vm being and hvm.  However, all of that (regarding ioemu) is highly presumptious.  I seem to recall something about not being able to have four devices for some reason as well, though, so perhaps you should do some searching on that premise or try calling it hdc since you aren't using the cdrom at the same time.  I'm not a major linux player or anything, so I can't make heads or tails of the more detailed output you provided.  That said, my suggestions are shots in the dark.  Also, as an aside, I'm assuming -c works for you on other HVM configs, as the last time I tried it with an HVM (probably FC6), I don't think it did.  Based on the error, though, I don't think the -c is your problem.  If it is, and assuming that you aren't putting the config file in an auto-start (at boot) location, the hvm config file can have a setting to start up a vnc window.
	Dustin

-----Original Message-----
From: fedora-xen-bounces at redhat.com [mailto:fedora-xen-bounces at redhat.com] On Behalf Of John Summerfield
Sent: Friday, January 18, 2008 09:09
To: fedora-xen at redhat.com
Subject: Re: [Fedora-xen] xm create -c recovery fails

On Friday 18 January 2008 09:54:47 pm Dustin Henning wrote:
> Try this:
> disk = [ 'file:/var/lib/xen/images/recovery.img,hda,w'
>        , 'file:/var/lib/xen/images/WindowsXP.img,hdb,w'
> #      , ',hdc:cdrom,r'
>        , 'phy:/dev/hda,hdd,r'
>        ]
>
> Dustin

Same:
[root at potoroo ~]# time xm create -c recovery
Using config file "/etc/xen/recovery".
Error: Device 5696 (vbd) could not be connected. Hotplug scripts not working.

real    1m44.270s
user    0m0.085s
sys     0m0.046s
[root at potoroo ~]# cat /etc/xen/recovery | grep -Ev '^($|#)'
import os, re
arch = os.uname()[4]
if re.search('64', arch):
    arch_libdir = 'lib64'
else:
    arch_libdir = 'lib'
kernel = "/usr/lib/xen/boot/hvmloader"
builder='hvm'
memory = 128
name = "recovery"
vif = [ 'type=ioemu, bridge=xenbr0' ]
disk = [ 'file:/var/lib/xen/images/recovery.img,hda,w'
       , 'file:/var/lib/xen/images/WindowsXP.img,hdb,w'
       , 'phy:/dev/hda,hdd,r'
       ]

etc
I don't believe /dev/hda has a different meaning from hda, and it seems that 
iomem (which I've not seen documented in this context) specifies "not 
paravirtualised" I/O. I got that from google when trying to solve the problem 
before posting to the list.
>
> -----Original Message-----
> From: fedora-xen-bounces at redhat.com [mailto:fedora-xen-bounces at redhat.com]
> On Behalf Of John Summerfield Sent: Thursday, January 17, 2008 21:22
> To: fedora-xen at redhat.com
> Subject: [Fedora-xen] xm create -c recovery fails
>
> I'm running F8, xen-3.1.2-1.fc8, 2.6.21.7-2890.fc9xen.
>
> I have a xen configuration which contains this stanza:
> disk = [ 'file:/var/lib/xen/images/recovery.img,hda,w'
>        , 'file:/var/lib/xen/images/WindowsXP.img,hdb,w'
> #      , ',hdc:cdrom,r'
>        , 'phy:hda,ioemu:hdd,r'
>        ]
>
> If I comment out the line containing "'phy:hda,ioemu:hdd,r' then the xm
> create line works and the guest starts up and runs fine. Whether I have
> "ioemu" doesn't make any obvious difference, google suggested it.
>
> With the stanza as above, it fails:
> [root at potoroo ~]# time xm create -c recovery
> Using config file "/etc/xen/recovery".
> Error: Device 5696 (vbd) could not be connected. Hotplug scripts not
> working.
>
> real    1m44.750s
> user    0m0.080s
> sys     0m0.067s
> [root at potoroo ~]#
>
> The only other thing I see is the VNC console opens, but it displays with a
> white background.
>
> These are the messages logged to xend.log:
> [2008-01-18 11:00:24 2652] INFO (image:129) buildDomain os=hvm dom=27
> vcpus=1 [2008-01-18 11:00:24 2652] INFO (XendDomainInfo:1458) createDevice:
> vfb : {'vncunused': 1, 'other_config': {'vncunused':
> 1}, 'uuid': '6c9425f6-7800-4325-bcd7-b917ce2f8955'}
> [2008-01-18 11:00:24 2652] INFO (XendDomainInfo:1458) createDevice: vbd :
> {'uuid': '0f4b1edf-a164-6b3a-ebd2-395532720861', 'bootable':
> 1, 'driver': 'paravirtualised', 'dev': 'hda', 'uname':
> 'file:/var/lib/xen/images/recovery.img', 'mode': 'w'} [2008-01-18 11:00:24
> 2652] INFO (XendDomainInfo:1458) createDevice: vbd : {'uuid':
> '5c84f484-c9df-f60d-ccec-9a4bf7e47e64', 'bootable':
> 0, 'driver': 'paravirtualised', 'dev': 'hdb', 'uname':
> 'file:/var/lib/xen/images/WindowsXP.img', 'mode': 'w'} [2008-01-18 11:00:24
> 2652] INFO (XendDomainInfo:1458) createDevice: vbd : {'uuid':
> 'f34d1d46-dd15-7572-6661-26570af507a7', 'bootable':
> 0, 'driver': 'ioemu', 'dev': 'ioemu:hdd', 'uname': 'phy:hda', 'mode': 'r'}
> [2008-01-18 11:00:24 2652] INFO (XendDomainInfo:1458) createDevice: vif :
> {'bridge': 'xenbr0', 'mac': '00:16:3e:33:b1:83', 'type': 'ioemu', 'uuid':
> 'b5fca1da-8850-0723-bf2e-edbf7635832e'} [2008-01-18 11:00:24 2652] INFO
> (image:454) spawning device
> models: /usr/lib64/xen/bin/qemu-dm
> ['/usr/lib64/xen/bin/qemu-dm', '-d', '27', '-vcpus', '1', '-boot', 'cd',
> '-soundhw', 'sb16', '-localtime', '-serial', 'pty', '-acpi', '-usb',
> '-usbdevice', 'tablet', '-domain-name', 'recovery', '-net',
> 'nic,vlan=1,macaddr=00:16:3e:33:b1:83,model=rtl8139', '-net',
> 'tap,vlan=1,bridge=xenbr0', '-vnc', '127.0.0.1:0', '-vncunused',
> '-vncviewer'] [2008-01-18 11:00:24 2652] INFO (image:458) device model pid:
> 29112
>
>
> "recovery" is a Debian system, I created it under KVM and I've mentioned it
> here before.
>
> Here is the Xen configuration:
> [root at potoroo xen]# cat /etc/xen/recovery | grep -Ev '^($|#)'
> import os, re
> arch = os.uname()[4]
> if re.search('64', arch):
>     arch_libdir = 'lib64'
> else:
>     arch_libdir = 'lib'
> kernel = "/usr/lib/xen/boot/hvmloader"
> builder='hvm'
> memory = 128
> name = "recovery"
> vif = [ 'type=ioemu, bridge=xenbr0' ]
> disk = [ 'file:/var/lib/xen/images/recovery.img,hda,w'
>        , 'file:/var/lib/xen/images/WindowsXP.img,hdb,w'
>        , 'phy:hda,ioemu:hdd,r'
>        ]
> device_model = '/usr/' + arch_libdir + '/xen/bin/qemu-dm'
> boot="cd"
> sdl=0
> vnc=1
> vncconsole=1
> vncpasswd=''
> stdvga=0
> serial='pty'
> soundhw='sb16'
> localtime=1
> usb=1
> usbdevice='tablet'
> [root at potoroo xen]#
>
> --
> Fedora-xen mailing list
> Fedora-xen at redhat.com
> https://www.redhat.com/mailman/listinfo/fedora-xen
>
>
>
> --
> Fedora-xen mailing list
> Fedora-xen at redhat.com
> https://www.redhat.com/mailman/listinfo/fedora-xen


--
Fedora-xen mailing list
Fedora-xen at redhat.com
https://www.redhat.com/mailman/listinfo/fedora-xen





From Dustin.Henning at prd-inc.com  Fri Jan 18 14:58:36 2008
From: Dustin.Henning at prd-inc.com (Dustin Henning)
Date: Fri, 18 Jan 2008 09:58:36 -0500
Subject: [Fedora-xen] xm create -c recovery fails
In-Reply-To: <200801182333.23688.debian@herakles.homelinux.org>
References: <200801181121.45714.debian@herakles.homelinux.org>	<001001c859d1$4e4c4f80$eae4ee80$@Henning@prd-inc.com>	<200801182309.13292.debian@herakles.homelinux.org>
	<200801182333.23688.debian@herakles.homelinux.org>
Message-ID: <001a01c859e2$9a183da0$ce48b8e0$@Henning@prd-inc.com>

	Sounds like this needs to fall to someone else.  When I started using Xen (manually installed for PVs on Ubuntu), it seems there were warnings in documentation about not mounting something RW in multiple places, which indicated to me that it was possible (though admittedly, my memory is shot).  That said, Xen may have changed to the point where it isn't possible, or you may be facing an issue specifically tied to the Fedora version, either way, hopefully someone else can help you.  I almost suggested trying sda vs hda as well, but I figured maybe you had your SATA in compatibility mode or an IDE drive running.
	Dustin

-----Original Message-----
From: fedora-xen-bounces at redhat.com [mailto:fedora-xen-bounces at redhat.com] On Behalf Of John Summerfield
Sent: Friday, January 18, 2008 09:33
To: fedora-xen at redhat.com
Subject: Re: [Fedora-xen] xm create -c recovery fails

On Friday 18 January 2008 11:09:13 pm John Summerfield wrote:
> On Friday 18 January 2008 09:54:47 pm Dustin Henning wrote:
> > Try this:
> > disk = [ 'file:/var/lib/xen/images/recovery.img,hda,w'
> >        , 'file:/var/lib/xen/images/WindowsXP.img,hdb,w'
> > #      , ',hdc:cdrom,r'
> >        , 'phy:/dev/hda,hdd,r'
> >        ]
> >
> > Dustin
>


I had a bit of a dig around in /etc/xen/scripts, without comprehending a lot, 
but it seems that it's taking care not to use mounted partitions.

Oh.

This is the drive I'm booting the host from. This is F8. The drive's called 
sda, not hda.

There's a squillion kernel messages from the guest about I/O errors.
Jan 18 23:13:44 recovery kernel: or=0x04 { DriveStatusError }
Jan 18 23:13:44 recovery kernel: ide: failed opcode was: unknown
Jan 18 23:13:44 recovery kernel: hdd: task_in_intr: status=0x41 { DriveReady 
Error }
Jan 18 23:13:44 recovery kernel: hdd: task_in_intr: error=0x04 { 
DriveStatusError }
Jan 18 23:13:44 recovery kernel: ide: failed opcode was: unknown
Jan 18 23:13:44 recovery kernel: hdd: task_in_intr: status=0x41 { DriveReady 
Error }
Jan 18 23:13:44 recovery kernel: hdd: task_in_intr: error=0x04 { 
DriveStatusError }
Jan 18 23:13:44 recovery kernel: ide: failed opcode was: unknown
Jan 18 23:13:44 recovery kernel: ide1: reset: success

The kernel buffer's full of them.

It's fairly clear this is not going to work soon.

I want to run ntfsclone against Windows on the drive; I can do that on the 
host.

I see two problems:
1. Those scripts silently fail
2. Xen prevents my reading the drive in the guest.

I _know there are hazards with using the host's boot drive in the guest, but 
so long as I don't change the partition table anywhere, and don't use a 
partition rw in one place and anywhere else, I expect I avoid those hazards.


> Same:
> [root at potoroo ~]# time xm create -c recovery
> Using config file "/etc/xen/recovery".
> Error: Device 5696 (vbd) could not be connected. Hotplug scripts not
> working.
>
> real    1m44.270s
> user    0m0.085s
> sys     0m0.046s
> [root at potoroo ~]# cat /etc/xen/recovery | grep -Ev '^($|#)'
> import os, re
> arch = os.uname()[4]
> if re.search('64', arch):
>     arch_libdir = 'lib64'
> else:
>     arch_libdir = 'lib'
> kernel = "/usr/lib/xen/boot/hvmloader"
> builder='hvm'
> memory = 128
> name = "recovery"
> vif = [ 'type=ioemu, bridge=xenbr0' ]
> disk = [ 'file:/var/lib/xen/images/recovery.img,hda,w'
>        , 'file:/var/lib/xen/images/WindowsXP.img,hdb,w'
>        , 'phy:/dev/hda,hdd,r'
>        ]
>
> etc
> I don't believe /dev/hda has a different meaning from hda, and it seems
> that iomem (which I've not seen documented in this context) specifies "not
> paravirtualised" I/O. I got that from google when trying to solve the
> problem before posting to the list.
>
> > -----Original Message-----
> > From: fedora-xen-bounces at redhat.com
> > [mailto:fedora-xen-bounces at redhat.com] On Behalf Of John Summerfield
> > Sent: Thursday, January 17, 2008 21:22 To: fedora-xen at redhat.com
> > Subject: [Fedora-xen] xm create -c recovery fails
> >
> > I'm running F8, xen-3.1.2-1.fc8, 2.6.21.7-2890.fc9xen.
> >
> > I have a xen configuration which contains this stanza:
> > disk = [ 'file:/var/lib/xen/images/recovery.img,hda,w'
> >        , 'file:/var/lib/xen/images/WindowsXP.img,hdb,w'
> > #      , ',hdc:cdrom,r'
> >        , 'phy:hda,ioemu:hdd,r'
> >        ]
> >
> > If I comment out the line containing "'phy:hda,ioemu:hdd,r' then the xm
> > create line works and the guest starts up and runs fine. Whether I have
> > "ioemu" doesn't make any obvious difference, google suggested it.
> >
> > With the stanza as above, it fails:
> > [root at potoroo ~]# time xm create -c recovery
> > Using config file "/etc/xen/recovery".
> > Error: Device 5696 (vbd) could not be connected. Hotplug scripts not
> > working.
> >
> > real    1m44.750s
> > user    0m0.080s
> > sys     0m0.067s
> > [root at potoroo ~]#
> >
> > The only other thing I see is the VNC console opens, but it displays with
> > a white background.
> >
> > These are the messages logged to xend.log:
> > [2008-01-18 11:00:24 2652] INFO (image:129) buildDomain os=hvm dom=27
> > vcpus=1 [2008-01-18 11:00:24 2652] INFO (XendDomainInfo:1458)
> > createDevice: vfb : {'vncunused': 1, 'other_config': {'vncunused':
> > 1}, 'uuid': '6c9425f6-7800-4325-bcd7-b917ce2f8955'}
> > [2008-01-18 11:00:24 2652] INFO (XendDomainInfo:1458) createDevice: vbd :
> > {'uuid': '0f4b1edf-a164-6b3a-ebd2-395532720861', 'bootable':
> > 1, 'driver': 'paravirtualised', 'dev': 'hda', 'uname':
> > 'file:/var/lib/xen/images/recovery.img', 'mode': 'w'} [2008-01-18
> > 11:00:24 2652] INFO (XendDomainInfo:1458) createDevice: vbd : {'uuid':
> > '5c84f484-c9df-f60d-ccec-9a4bf7e47e64', 'bootable':
> > 0, 'driver': 'paravirtualised', 'dev': 'hdb', 'uname':
> > 'file:/var/lib/xen/images/WindowsXP.img', 'mode': 'w'} [2008-01-18
> > 11:00:24 2652] INFO (XendDomainInfo:1458) createDevice: vbd : {'uuid':
> > 'f34d1d46-dd15-7572-6661-26570af507a7', 'bootable':
> > 0, 'driver': 'ioemu', 'dev': 'ioemu:hdd', 'uname': 'phy:hda', 'mode':
> > 'r'} [2008-01-18 11:00:24 2652] INFO (XendDomainInfo:1458) createDevice:
> > vif : {'bridge': 'xenbr0', 'mac': '00:16:3e:33:b1:83', 'type': 'ioemu',
> > 'uuid': 'b5fca1da-8850-0723-bf2e-edbf7635832e'} [2008-01-18 11:00:24
> > 2652] INFO (image:454) spawning device
> > models: /usr/lib64/xen/bin/qemu-dm
> > ['/usr/lib64/xen/bin/qemu-dm', '-d', '27', '-vcpus', '1', '-boot', 'cd',
> > '-soundhw', 'sb16', '-localtime', '-serial', 'pty', '-acpi', '-usb',
> > '-usbdevice', 'tablet', '-domain-name', 'recovery', '-net',
> > 'nic,vlan=1,macaddr=00:16:3e:33:b1:83,model=rtl8139', '-net',
> > 'tap,vlan=1,bridge=xenbr0', '-vnc', '127.0.0.1:0', '-vncunused',
> > '-vncviewer'] [2008-01-18 11:00:24 2652] INFO (image:458) device model
> > pid: 29112
> >
> >
> > "recovery" is a Debian system, I created it under KVM and I've mentioned
> > it here before.
> >
> > Here is the Xen configuration:
> > [root at potoroo xen]# cat /etc/xen/recovery | grep -Ev '^($|#)'
> > import os, re
> > arch = os.uname()[4]
> > if re.search('64', arch):
> >     arch_libdir = 'lib64'
> > else:
> >     arch_libdir = 'lib'
> > kernel = "/usr/lib/xen/boot/hvmloader"
> > builder='hvm'
> > memory = 128
> > name = "recovery"
> > vif = [ 'type=ioemu, bridge=xenbr0' ]
> > disk = [ 'file:/var/lib/xen/images/recovery.img,hda,w'
> >        , 'file:/var/lib/xen/images/WindowsXP.img,hdb,w'
> >        , 'phy:hda,ioemu:hdd,r'
> >        ]
> > device_model = '/usr/' + arch_libdir + '/xen/bin/qemu-dm'
> > boot="cd"
> > sdl=0
> > vnc=1
> > vncconsole=1
> > vncpasswd=''
> > stdvga=0
> > serial='pty'
> > soundhw='sb16'
> > localtime=1
> > usb=1
> > usbdevice='tablet'
> > [root at potoroo xen]#
> >
> > --
> > Fedora-xen mailing list
> > Fedora-xen at redhat.com
> > https://www.redhat.com/mailman/listinfo/fedora-xen
> >
> >
> >
> > --
> > Fedora-xen mailing list
> > Fedora-xen at redhat.com
> > https://www.redhat.com/mailman/listinfo/fedora-xen
>
> --
> Fedora-xen mailing list
> Fedora-xen at redhat.com
> https://www.redhat.com/mailman/listinfo/fedora-xen


--
Fedora-xen mailing list
Fedora-xen at redhat.com
https://www.redhat.com/mailman/listinfo/fedora-xen





From debian at herakles.homelinux.org  Fri Jan 18 15:10:19 2008
From: debian at herakles.homelinux.org (John Summerfield)
Date: Sat, 19 Jan 2008 00:10:19 +0900
Subject: [Fedora-xen] xm create -c recovery fails
In-Reply-To: <001901c859e1$e81e6980$b85b3c80$@Henning@prd-inc.com>
References: <200801181121.45714.debian@herakles.homelinux.org>	<001001c859d1$4e4c4f80$eae4ee80$@Henning@prd-inc.com>	<200801182309.13292.debian@herakles.homelinux.org>
	<001901c859e1$e81e6980$b85b3c80$@Henning@prd-inc.com>
Message-ID: <4790C15B.3010703@herakles.homelinux.org>

Dustin Henning wrote:
> 	I had a similar problem, and my suggestion is what solved it, but that was with moonshine, and according to the documentation, the /dev/ shouldn't need to be specified.  I didn't look unto ioemu, as I've never used it and assumed it had to do with using a different method to emulate (input output emulation vs block device emulation) since either method would be not paravirtualised by virtue of the vm being and hvm.  However, all of that (regarding ioemu) is highly presumptious.  I seem to recall something about not being able to have four devices for some reason as well, though, so perhaps you should do some searching on that premise or try calling it hdc since you aren't using the cdrom at the same time.  I'm not a major linux player or anything, so I can't make heads or tails of the more detailed output you provided.  That said, my suggestions are shots in the dark.  Also, as an aside, I'm assuming -c works for you on other HVM configs, as the last time I tried it with a
n 
>  HVM (probably FC6), I don't think it did.  Based on the error, though, I don't think the -c is your problem.  If it is, and assuming that you aren't putting the config file in an auto-start (at boot) location, the hvm config file can have a setting to start up a vnc window.
> 	Dustin
>

I narrowed it down to the disk configuration before I posted. I've seen 
a limit of four drives mentioned; it seems broken to me any I'm likely 
to test it (at one time I had three drives on USB interfaces attached to 
my laptop while I copied back and forth.)


-- 

Cheers
John

-- spambait
1aaaaaaa at coco.merseine.nu  Z1aaaaaaa at coco.merseine.nu
-- Advice
http://webfoot.com/advice/email.top.php
http://www.catb.org/~esr/faqs/smart-questions.html
http://support.microsoft.com/kb/555375

You cannot reply off-list:-)



From debian at herakles.homelinux.org  Fri Jan 18 15:13:41 2008
From: debian at herakles.homelinux.org (John Summerfield)
Date: Sat, 19 Jan 2008 00:13:41 +0900
Subject: [Fedora-xen] xm create -c recovery fails
In-Reply-To: <001a01c859e2$9a183da0$ce48b8e0$@Henning@prd-inc.com>
References: <200801181121.45714.debian@herakles.homelinux.org>	<001001c859d1$4e4c4f80$eae4ee80$@Henning@prd-inc.com>	<200801182309.13292.debian@herakles.homelinux.org>	<200801182333.23688.debian@herakles.homelinux.org>
	<001a01c859e2$9a183da0$ce48b8e0$@Henning@prd-inc.com>
Message-ID: <4790C225.1020500@herakles.homelinux.org>

Dustin Henning wrote:
> 	Sounds like this needs to fall to someone else.  When I started using Xen (manually installed for PVs on Ubuntu), it seems there were warnings in documentation about not mounting something RW in multiple places, which indicated to me that it was possible (though admittedly, my memory is shot).  That said, Xen may have changed to the point where it isn't possible, or you may be facing an issue specifically tied to the Fedora version, either way, hopefully someone else can help you.  I almost suggested trying sda vs hda as well, but I figured maybe you had your SATA in compatibility mode or an IDE drive running.
> 	Dustin
> 

This is F8. Drives hdx are gone, they're all sdx now. Except CDs, 
they're something else.

The only place the drive's mounted rw is the host. That's safe, whether 
xen allows it or not.


-- 

Cheers
John

-- spambait
1aaaaaaa at coco.merseine.nu  Z1aaaaaaa at coco.merseine.nu
-- Advice
http://webfoot.com/advice/email.top.php
http://www.catb.org/~esr/faqs/smart-questions.html
http://support.microsoft.com/kb/555375

You cannot reply off-list:-)



From fbrier at multideck.com  Mon Jan 21 04:33:35 2008
From: fbrier at multideck.com (Frederick N. Brier)
Date: Sun, 20 Jan 2008 23:33:35 -0500
Subject: [Fedora-xen] virt-install
In-Reply-To: <20080115113109.3fc6eb07@mail.gmail.com>
References: <4789C14C.1020703@multideck.com>	<20080113172734.GD23654@redhat.com>
	<20080115113109.3fc6eb07@mail.gmail.com>
Message-ID: <4794209F.30101@multideck.com>

I have continued to experiment creating VMs and blowing them away using 
a variety of storage and other options.  I want to be able to create a 
Fedora 8 Guest VM, install a number of packages, configure them, and 
then save it as a template.  Then copy the template and install it.  The 
file storage options seemed the best, but it apparently has flaws for 
speed and integrity.  I created one using LVM in the guest, but read 
that was unnecessary overhead and made it difficult to mount the 
images.  So I tried to create one by deleting the volumes and that 
seemed to work, but it still created a partition with the file system 
inside and I could not mount it.  The blktap driver was recommended if 
you were not going to use an LVM in the guest or Dom0, but I do not know 
how to invoke virt-install to create a simple blktap driver based ext3 
file system in a file.  What are virt-install parameters do you use to 
specify using the blktap driver to a file?  And if there are any 
misconceptions in my message, please feel free to trounce on them.  If 
there is a wiki or man page, please just give me the URL.  Thank you.

Fred

John Maclean wrote:
> /usr/sbin/virt-install --name fx6foo \
> --paravirt \
> --ram 256 \
> --nographics \
> --file-size 10 \
> --file /dev/zulu_images/fx6foo \
> --location
> http://download.fedora.redhat.com/pub/fedora/linux/releases/7/Fedora/i386/os/
>
>
> ^^ That kind of thing. The man page has a few examples right at the end.
>
> On Sun, 13 Jan 2008 17:27:34 +0000 "Daniel P. Berrange"
> <berrange at redhat.com> wrote:
>
>   
>> On Sun, Jan 13, 2008 at 02:44:12AM -0500, Frederick N. Brier wrote:
>>     
>>> I just installed Fedora 8 and the Fedora Xen packages.  I have been 
>>> trying to get a variety of VMs installed, but the most basic one is
>>> just a Fedora guest VM.  Please correct me if I am wrong, but the
>>> correct tool is "virt-install".  It asks a number of questions, but
>>> the last is "What is the install location?"  I finally found an
>>> excerpt from a book that had 
>>> "http://download.fedora.redhat.com/pub/fedora/linux/core/6/i386" as
>>> the answer.  But that is not correct it is actually:
>>> "http://download.fedora.redhat.com/pub/fedora/linux/core/*6*/i386/os", 
>>> but that is for core 6, not 7 or Fedora 8.  And the file tree does
>>> not have a 
>>> "http://download.fedora.redhat.com/pub/fedora/linux/core/*8*/i386/os".  
>>> Is there no place where fc8's files are posted?  Or are we supposed
>>> to specify 6?  I would have said okay, except I started getting
>>> messages like this:
>>>       
>> Fedora Core & Extras mered during the F7 release, so the download URLs
>> changed style slightly
>>
>> eg, i386 F8
>>
>> http://download.fedora.redhat.com/pub/fedora/linux/releases/8/Fedora/i386/os/
>>
>> eg, x86_64 F7
>>
>> http://download.fedora.redhat.com/pub/fedora/linux/releases/7/Fedora/x86_64/os/
>>
>> Basically, you always want the URL ending in '/os/' for your release.
>>
>> You can also use  nfs:// or ftp:// URLs.
>>
>> Regards,
>> Dan.
>>     
>
>
>   



From reiber at gmail.com  Tue Jan 15 21:14:21 2008
From: reiber at gmail.com (Paul Reiber)
Date: Tue, 15 Jan 2008 13:14:21 -0800
Subject: [Xen-users] Re: [Fedora-xen] Guest VM dropping connection.
In-Reply-To: <478CFB41.7020501@redhat.com>
References: <BAY119-F299C8C4AE3D185AF538A91C7EF0@phx.gbl>
	<BAY119-W7DA205642E05359EE8F82C7470@phx.gbl>
	<478CFB41.7020501@redhat.com>
Message-ID: <e8ca6eea0801151314k4b762003m1a844e361c8cf703@mail.gmail.com>

Ubaidul, you might wanna try this:

SSH into the VM from elsewhere.  Make sure the window SSH is running
in will be able to be left running for a _long_ while, (at least, in
so far as it's still there after the VM's lost its network connection)
... then leave it running a simple makeshift monitor.

Here's an easy makeshift error monitor: go into /var/log, and run a
bunch of backgrounded 'tail -f' commands on various logfiles on the
system, and leave that window up and running somewhere.  Then when the
problem happens again, you can look over and see what errors have been
reported recently.

Not all errors are logged in /var/log/messages... this is a common
misconception, though, so no worries.

Please let me know if this helps!

Regards,
-pbr



On Jan 15, 2008 10:28 AM, Mark Nielsen <mnielsen at redhat.com> wrote:
> are you seeing any messages on the host about the network bouncing?
>
> Ubaidul Khan wrote:
> > I am still experiencing the same problems but I am seeing some weird messages in /var/log/messages:
> >
> > Jan 15 10:48:32 tsubo-dr kernel: device eth0 left promiscuous mode
> > Jan 15 10:49:50 tsubo-dr kernel: Removing netfilter NETLINK layer.
> > Jan 15 10:49:50 tsubo-dr kernel: ip_tables: (C) 2000-2006 Netfilter Core Team
> > Jan 15 10:49:50 tsubo-dr kernel: Netfilter messages via NETLINK v0.30.
> > Jan 15 10:49:50 tsubo-dr kernel: ip_conntrack version 2.4 (8192 buckets, 65536 max) - 304 bytes per conntrack
> > Jan 15 10:49:56 tsubo-dr kernel: device eth0 entered promiscuous mode
> > Jan 15 10:50:25 tsubo-dr kernel: device eth0 left promiscuous mode
> > Jan 15 10:54:08 tsubo-dr kernel: device eth0 entered promiscuous mode
> > Jan 15 10:54:37 tsubo-dr kernel: device eth0 left promiscuous mode
> >
> > The loss of connection is happening during the windows when the interface enters/leaves promiscuious mode.
> > ----------------------------------------
> >
> >> From: ukhanlists at hotmail.com
> >> To: xen-users at lists.xensource.com; fedora-xen at redhat.com
> >> Date: Mon, 30 Jul 2007 22:04:45 -0400
> >> CC:
> >> Subject: [Fedora-xen] Guest VM dropping connection.
> >>
> >> I am running RHEL5 Guest and Host.  The guest OS is dropping network
> >> connections occasionally(I noticed my ssh session suddenly terminated).  The
> >> guest is configured with private network interface and a public network
> >> interface.  Following are the bridge/network settings for the host:
> >>
> >> bridge name     bridge id               STP enabled     interfaces
> >> xenbr0          8000.feffffffffff              no                 vif2.0
> >>
> >> vif1.0
> >>
> >> peth0
> >>
> >> vif0.0
> >>
> >> xenbr1          8000.fefffffffffe             no                 vif2.1
> >>
> >> peth1
> >>
> >> vif0.3
> >>
> >> xenbr1 is dedicated to provide the private network link for the guest os.
> >> Following is the guest OS configuration:
> >>
> >> # Automatically generated xen config file
> >> name = "saleen_webvm0"
> >> memory = "1000"
> >> disk = [
> >> 'tap:aio:/vms/img/redhat/linux/es/5.0/x86_64/saleen_webvm0.img,xvda,w','phy:/dev/sdc,xvdb,w'
> >> ]
> >> vif = [ 'mac=00:16:3e:2e:6f:e1, bridge=xenbr0','mac=00:16:3e:2f:9e:b1,
> >> bridge=xenbr1',]
> >> # vif = [ 'mac=00:16:3e:2e:6f:e1, bridge=xenbr0',]
> >> vfb = ["type=vnc,vncunused=1"]
> >> uuid = "122374dc-26a3-cb0d-99f8-3393e2481777"
> >> bootloader="/usr/bin/pygrub"
> >> vcpus=2
> >> on_reboot   = 'restart'
> >> on_crash    = 'restart'
> >>
> >> Following is the output of ifconfig:
> >>
> >> eth0      Link encap:Ethernet  HWaddr 00:14:4F:40:D8:70
> >>           inet addr:xxx.xxx.xxx.xxx  Bcast:xxx.xxx.xxx.255
> >> Mask:255.255.255.0
> >>           inet6 addr: fe80::214:4fff:fe40:d870/64 Scope:Link
> >>           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
> >>           RX packets:79313 errors:0 dropped:0 overruns:0 frame:0
> >>           TX packets:1167 errors:0 dropped:0 overruns:0 carrier:0
> >>           collisions:0 txqueuelen:0
> >>           RX bytes:6619719 (6.3 MiB)  TX bytes:115448 (112.7 KiB)
> >>
> >> eth1      Link encap:Ethernet  HWaddr 00:14:4F:40:D8:71
> >>           inet addr:xxx.xxx.xxx.xxx  Bcast:xxx.xxx.xxx.255
> >> Mask:255.255.255.0
> >>           inet6 addr: fe80::214:4fff:fe40:d871/64 Scope:Link
> >>           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
> >>           RX packets:0 errors:0 dropped:0 overruns:0 frame:0
> >>           TX packets:12 errors:0 dropped:0 overruns:0 carrier:0
> >>           collisions:0 txqueuelen:0
> >>           RX bytes:0 (0.0 b)  TX bytes:720 (720.0 b)
> >>
> >> peth0     Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF
> >>           inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link
> >>           UP BROADCAST RUNNING NOARP  MTU:1500  Metric:1
> >>           RX packets:105404 errors:0 dropped:0 overruns:0 frame:0
> >>           TX packets:13455 errors:0 dropped:0 overruns:0 carrier:0
> >>           collisions:0 txqueuelen:1000
> >>           RX bytes:9122426 (8.6 MiB)  TX bytes:1997833 (1.9 MiB)
> >>           Base address:0x8c00 Memory:fa5e0000-fa600000
> >>
> >> peth1     Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FE
> >>           inet6 addr: fe80::fcff:ffff:feff:fffe/64 Scope:Link
> >>           UP BROADCAST RUNNING NOARP  MTU:1500  Metric:1
> >>           RX packets:9239102 errors:0 dropped:0 overruns:0 frame:0
> >>           TX packets:5337342 errors:0 dropped:0 overruns:0 carrier:0
> >>           collisions:0 txqueuelen:1000
> >>           RX bytes:12420212276 (11.5 GiB)  TX bytes:523849820 (499.5 MiB)
> >>           Base address:0x8800 Memory:fa5c0000-fa5e0000
> >>
> >> vif1.0    Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF
> >>           inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link
> >>           UP BROADCAST RUNNING NOARP  MTU:1500  Metric:1
> >>           RX packets:2174 errors:0 dropped:0 overruns:0 frame:0
> >>           TX packets:80032 errors:0 dropped:0 overruns:0 carrier:0
> >>           collisions:0 txqueuelen:32
> >>           RX bytes:446031 (435.5 KiB)  TX bytes:6941997 (6.6 MiB)
> >>
> >> vif2.0    Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF
> >>           inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link
> >>           UP BROADCAST RUNNING NOARP  MTU:1500  Metric:1
> >>           RX packets:10084 errors:0 dropped:0 overruns:0 frame:0
> >>           TX packets:89284 errors:0 dropped:0 overruns:0 carrier:0
> >>           collisions:0 txqueuelen:32
> >>           RX bytes:1186096 (1.1 MiB)  TX bytes:7380350 (7.0 MiB)
> >>
> >> vif2.1    Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF
> >>           inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link
> >>           UP BROADCAST RUNNING NOARP  MTU:1500  Metric:1
> >>           RX packets:5337343 errors:0 dropped:0 overruns:0 frame:0
> >>           TX packets:9239082 errors:0 dropped:20 overruns:0 carrier:0
> >>           collisions:0 txqueuelen:32
> >>           RX bytes:403712612 (385.0 MiB)  TX bytes:12383227754 (11.5 GiB)
> >>
> >> Any help is greately appreciated.
> >>
> >> _________________________________________________________________
> >> http://liveearth.msn.com
> >>
> >> --
> >> Fedora-xen mailing list
> >> Fedora-xen at redhat.com
> >> https://www.redhat.com/mailman/listinfo/fedora-xen
> >>
> >
> > _________________________________________________________________
> > Share life as it happens with the new Windows Live.
> > http://www.windowslive.com/share.html?ocid=TXT_TAGHM_Wave2_sharelife_012008
> >
> > --
> > Fedora-xen mailing list
> > Fedora-xen at redhat.com
> > https://www.redhat.com/mailman/listinfo/fedora-xen
> >
>
>
> _______________________________________________
> Xen-users mailing list
> Xen-users at lists.xensource.com
> http://lists.xensource.com/xen-users
>



From rjones at redhat.com  Wed Jan 16 13:45:31 2008
From: rjones at redhat.com (Richard W.M. Jones)
Date: Wed, 16 Jan 2008 13:45:31 +0000
Subject: [Fedora-xen] Installing F9 on F8 under kvm - DHCP segfaults
Message-ID: <478E0A7B.8050106@redhat.com>

Very strange error -- I'm not sure whether it's Fedora rawhide, KVM, 
libvirt or what is causing this.

Host is F8, up to date but with a rather old KVM-36.

Guest is Fedora rawhide (F9) downloaded today, i386 and x86-64.

i386 guest installs OK.

x86-64 guest segfaults early in the install process, as you can see from 
the screenshot below.

# rpm -qf /lib/modules/2.6.23.8-63.fc8/kernel/drivers/kvm/kvm-amd.ko
kernel-2.6.23.8-63.fc8
# rpm -q kvm
kvm-36-7.fc8
# uname -a
Linux amd.home.annexia.org 2.6.23.8-63.fc8 #1 SMP Wed Nov 21 17:56:40 
EST 2007 x86_64 x86_64 x86_64 GNU/Linux

Rich.

-- 
Emerging Technologies, Red Hat - http://et.redhat.com/~rjones/
Registered Address: Red Hat UK Ltd, Amberley Place, 107-111 Peascod
Street, Windsor, Berkshire, SL4 1TE, United Kingdom.  Registered in
England and Wales under Company Registration No. 03798903
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Screenshot-f9x64kvm Virtual Machine Console-1.png
Type: image/png
Size: 21568 bytes
Desc: not available
URL: <http://listman.redhat.com/archives/fedora-xen/attachments/20080116/6d9d6363/attachment.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Screenshot-f9x64kvm Virtual Machine Console.png
Type: image/png
Size: 23738 bytes
Desc: not available
URL: <http://listman.redhat.com/archives/fedora-xen/attachments/20080116/6d9d6363/attachment-0001.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 3237 bytes
Desc: S/MIME Cryptographic Signature
URL: <http://listman.redhat.com/archives/fedora-xen/attachments/20080116/6d9d6363/attachment.bin>

From reiber at gmail.com  Thu Jan 17 02:13:31 2008
From: reiber at gmail.com (Paul Reiber)
Date: Wed, 16 Jan 2008 21:13:31 -0500
Subject: [Fedora-xen] Paul Reiber has invited you to join Friendster
Message-ID: <6eoulp$1o2fft@c300a.gbxsc.friendster.com>

You're invited to join Paul Reiber's network of friends. 

By joining Friendster, you can reconnect with old
friends, meet new friends, start a blog, build a custom
profile, keep track of birthdays, and so
much more!

You can even stay in touch if you move away, switch
email addresses, or lose your mobile phone.

Click below to join Paul's network.

http://www.friendster.com/join.php?inviteref=12133763&amp;invite=0bMBp21TOi1IT7Cum3gwxPvpBbeQ1LUG7vNpcjVDcS8*&amp;lang=en-US

*****************************************************************
If you do not wish to receive notification emails from Friendster, please click below:
http://www.friendster.com/blockemails.php?invite=ZmVkb3JhLXhlbkByZWRoYXQuY29t
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/fedora-xen/attachments/20080116/dc5cd763/attachment.htm>

From dsrinivasmail at yahoo.com  Mon Jan 21 14:07:56 2008
From: dsrinivasmail at yahoo.com (srinivas d)
Date: Mon, 21 Jan 2008 06:07:56 -0800 (PST)
Subject: [Fedora-xen] xen is not able to detect windows cd 
In-Reply-To: <4790EB8A.7000608@kabuco.de>
Message-ID: <190193.74292.qm@web33305.mail.mud.yahoo.com>

Sir,

Subject :{1. Not able to load windows on xen enabled
kernel of RHEL 5 

         2.Able to load windows on xen enabled
kernel ON fedora 8 only on paralvirtulization mode.

         3. Able to load RHEL 5 (DOM 1) on xen enabled
kernel ON  RHEL 5 (DOM 0) on Fullvirtualation mode.}


I am trying to load window 2000 SERVER Enterprise,
choosing Full Virtualized and after detecting hardware
at Windows Setup it is getting stuck.

With following message at the bottom "setup is 
starting windows"

Can you help in this regard.

NOTE WITH RHEL 5 DVD I AM ABLE TO LOAD DOM 1 

regards,


MBOARD IS gigbyte and vt is enabled in bios and 
the processor is inter core 2 due which supports VT.

D.Srinivas



  
 




D.Srinivas


      ____________________________________________________________________________________
Never miss a thing.  Make Yahoo your home page. 
http://www.yahoo.com/r/hs



From mnielsen at redhat.com  Mon Jan 21 15:15:24 2008
From: mnielsen at redhat.com (Mark Nielsen)
Date: Mon, 21 Jan 2008 10:15:24 -0500
Subject: [Fedora-xen] xen is not able to detect windows cd
In-Reply-To: <190193.74292.qm@web33305.mail.mud.yahoo.com>
References: <190193.74292.qm@web33305.mail.mud.yahoo.com>
Message-ID: <4794B70C.2030404@redhat.com>

srinivas d wrote:
> Sir,
>
> Subject :{1. Not able to load windows on xen enabled
> kernel of RHEL 5 
>
>          2.Able to load windows on xen enabled
> kernel ON fedora 8 only on paralvirtulization mode.
>
>          3. Able to load RHEL 5 (DOM 1) on xen enabled
> kernel ON  RHEL 5 (DOM 0) on Fullvirtualation mode.}
>
>
> I am trying to load window 2000 SERVER Enterprise,
> choosing Full Virtualized and after detecting hardware
> at Windows Setup it is getting stuck.
>
>   

are you hitting F5 before it tells you to hit F6 to load additional 
drivers? It's not an option that shows up, but hit it anyways. It will 
bring up a menu to choose hardware types. One is "unknown", the other 
should be something closely resembling your hardware. Typically 
"Unknown" is selected by default and you have to up-arrow to the proper 
hardware and continue on.

> With following message at the bottom "setup is 
> starting windows"
>
> Can you help in this regard.
>
> NOTE WITH RHEL 5 DVD I AM ABLE TO LOAD DOM 1 
>
> regards,
>
>
> MBOARD IS gigbyte and vt is enabled in bios and 
> the processor is inter core 2 due which supports VT.
>
> D.Srinivas
>
>
>
>   
>  
>
>
>
>
> D.Srinivas
>
>
>       ____________________________________________________________________________________
> Never miss a thing.  Make Yahoo your home page. 
> http://www.yahoo.com/r/hs
>
> --
> Fedora-xen mailing list
> Fedora-xen at redhat.com
> https://www.redhat.com/mailman/listinfo/fedora-xen
>   

-------------- next part --------------
A non-text attachment was scrubbed...
Name: mnielsen.vcf
Type: text/x-vcard
Size: 177 bytes
Desc: not available
URL: <http://listman.redhat.com/archives/fedora-xen/attachments/20080121/66025b33/attachment.vcf>

From txtoth at gmail.com  Mon Jan 21 16:30:36 2008
From: txtoth at gmail.com (Ted X Toth)
Date: Mon, 21 Jan 2008 10:30:36 -0600
Subject: [Fedora-xen] FC8 (x86_64) host FC8 new virtual system install hangs
Message-ID: <4794C8AC.9070604@gmail.com>

I'm using the Virtual Machine Manager to create a new virtual system. I 
put the anaconda tree off of the DVD on an ftp server and point to it. I 
allocate 500M of memory and 20G of disk in a file. The anaconda install 
seems to go along fine until it starts to install packages and then it 
hangs. Has anyone else experienced this? Are there any tricks to getting 
this to work?



From markhsa at gmail.com  Mon Jan 21 20:59:04 2008
From: markhsa at gmail.com (Mark Hutchinson)
Date: Mon, 21 Jan 2008 13:59:04 -0700
Subject: [Fedora-xen] How to change resolution above 1024x768 in guess OS?
Message-ID: <b9e7857a0801211259j6d82a433s75acb98e622308d6@mail.gmail.com>

RHEL 5 XEN
Virtualized guest is RHEL 3WS.

I can only get 1024x768 for max resolution in the guest.   I have 1600x1200
for real-estate on the monitor. I am using Virt-manager and getting the
screen for there.  If I crank up the resolution in my guest, it seems to
stop at 10x24x768(24 bit color )
This is using VNC to connect right?  Is there a config for that to set
connection resolution size?
The client is seen to have a cirrus logic video card with 8 Megs of RAM.

Anyone know a way to change this or to force at least 1280x1024 ( I would
prefer 1600x1200 )

Assistance appreciated!
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/fedora-xen/attachments/20080121/abbacad2/attachment.htm>

From annefacq at crpp-bordeaux.cnrs.fr  Mon Jan 21 22:03:39 2008
From: annefacq at crpp-bordeaux.cnrs.fr (Anne Facq)
Date: Mon, 21 Jan 2008 23:03:39 +0100
Subject: [Fedora-xen] How to backup a Domu filesystem (on LVM) from Dom0 on
	Fedora 8 ?
Message-ID: <479516BB.7090701@crpp-bordeaux.cnrs.fr>

Hello

I use XEN on Fedora 8 with Domu on a LVM partition.

Before, on Fedora Core 6, I could backup each Domu by directly mounting 
the filesystem of the Domu (mount /dev/vg00/lvfoo /mnt) and then running 
dump on it.

On Fedora 8, I can't mount directly the filesystem of the Domu, so I 
backup the filesystem of the Domu using the dd command (dd 
if=/dev/vg00/lvfoo of=/var/xen/lvfoo.img)
But the backup with dd is longer and takes more disk space than the 
backup with dump, as dd copies unused blocks.

Is there a better method to backup a Domu filesystem from Dom0 on Fedora 8 ?

Thanks in advance

Anne Facq




From erenoglu at gmail.com  Mon Jan 21 22:10:38 2008
From: erenoglu at gmail.com (Emre Erenoglu)
Date: Mon, 21 Jan 2008 23:10:38 +0100
Subject: [Fedora-xen] How to change resolution above 1024x768 in guess OS?
In-Reply-To: <b9e7857a0801211259j6d82a433s75acb98e622308d6@mail.gmail.com>
References: <b9e7857a0801211259j6d82a433s75acb98e622308d6@mail.gmail.com>
Message-ID: <fe9771a80801211410t71806656obe73fb079f9c9a4b@mail.gmail.com>

Hi Mark,

I don't think you can get a higher resolution with the virtual graphics
adapter. My suggestions:

- Use a vnc based server inside the DomU
- Use Nomachine NX or FreeNX (suggested if you're away from the machine)
- Use XDMCP (suggested if you're on the same machine)

Good luck!

Emre

On Jan 21, 2008 9:59 PM, Mark Hutchinson <markhsa at gmail.com> wrote:

> RHEL 5 XEN
> Virtualized guest is RHEL 3WS.
>
> I can only get 1024x768 for max resolution in the guest.   I have
> 1600x1200 for real-estate on the monitor. I am using Virt-manager and
> getting the screen for there.  If I crank up the resolution in my guest, it
> seems to stop at 10x24x768(24 bit color )
> This is using VNC to connect right?  Is there a config for that to set
> connection resolution size?
> The client is seen to have a cirrus logic video card with 8 Megs of RAM.
>
> Anyone know a way to change this or to force at least 1280x1024 ( I would
> prefer 1600x1200 )
>
> Assistance appreciated!
> --
> Fedora-xen mailing list
> Fedora-xen at redhat.com
> https://www.redhat.com/mailman/listinfo/fedora-xen
>
>


-- 
Emre Erenoglu
erenoglu at gmail.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/fedora-xen/attachments/20080121/b8e81c9c/attachment.htm>

From aclark at digitalfairway.com  Mon Jan 21 22:19:58 2008
From: aclark at digitalfairway.com (Aaron Clark)
Date: Mon, 21 Jan 2008 17:19:58 -0500
Subject: [Fedora-xen] How to backup a Domu filesystem (on LVM) from Dom0
	on	Fedora 8 ?
In-Reply-To: <479516BB.7090701@crpp-bordeaux.cnrs.fr>
References: <479516BB.7090701@crpp-bordeaux.cnrs.fr>
Message-ID: <47951A8E.2050400@digitalfairway.com>

Anne Facq wrote:
> Hello
> 
> I use XEN on Fedora 8 with Domu on a LVM partition.
> 
> Before, on Fedora Core 6, I could backup each Domu by directly mounting 
> the filesystem of the Domu (mount /dev/vg00/lvfoo /mnt) and then running 
> dump on it.
> 
> On Fedora 8, I can't mount directly the filesystem of the Domu, so I 

Pardon if this is a dumb question, but why not?

> backup the filesystem of the Domu using the dd command (dd 
> if=/dev/vg00/lvfoo of=/var/xen/lvfoo.img)
> But the backup with dd is longer and takes more disk space than the 
> backup with dump, as dd copies unused blocks.
> 
> Is there a better method to backup a Domu filesystem from Dom0 on Fedora 
> 8 ?

I suppose you could use the img2qcow tool (possibly directly on 
/dev/vg00/lvfoo) to get a qcow file instead of a raw image.  However, I 
vaguely remember seeing somewhere that the qcow created by the xen tools 
is not necessarily 100% compatible with other qcow tools.

HTH,
Aaron



From debian at herakles.homelinux.org  Tue Jan 22 00:22:15 2008
From: debian at herakles.homelinux.org (John Summerfield)
Date: Tue, 22 Jan 2008 09:22:15 +0900
Subject: [Fedora-xen] Upgrade to development xen on F8?
Message-ID: <200801220922.15116.debian@herakles.homelinux.org>

I'm a bit torn between asking here and asking on the Fedora test list.

I'd like to use the latest xen (that's what I'm testing), but I don't want to 
upgrade to the entire development tree.

I tried this, and was astonished at the number of packages to upgrade!
[root at potoroo ~]# yum install --disablerepo=* --enable=development kernel-xen 
kernel-xen-2.6-doc xen xen-hypervisor xen-libs xenwatch | wc -l
Error: Missing Dependency: kdemultimedia3 >= 3.5.8 is needed by package 
kdemultimedia-extras-nonfree
845
[root at potoroo ~]# 

Those 845 lines represent upgrading pretty much all of KDE and all of Gnome.

The package "xen" alone accounts for much of this:
[root at potoroo ~]# yum install --disablerepo=* --enable=development xen | wc -l
Error: Missing Dependency: kdemultimedia3 >= 3.5.8 is needed by package 
kdemultimedia-extras-nonfree
844
[root at potoroo ~]# 

My idea of an ideal host for virtual machines is one that runs guests and 
precious little else, and certainly not a GUI and all the baggage that 
entails. 

Do these *xen* packages build on f8? What's the easy way to get the source - I 
used to use up2date, but I fear the technolgogy's getting ahead of me.


-- 
John the Bewildered.



From berrange at redhat.com  Tue Jan 22 00:29:12 2008
From: berrange at redhat.com (Daniel P. Berrange)
Date: Tue, 22 Jan 2008 00:29:12 +0000
Subject: [Fedora-xen] Upgrade to development xen on F8?
In-Reply-To: <200801220922.15116.debian@herakles.homelinux.org>
References: <200801220922.15116.debian@herakles.homelinux.org>
Message-ID: <20080122002912.GT12259@redhat.com>

On Tue, Jan 22, 2008 at 09:22:15AM +0900, John Summerfield wrote:
> I'm a bit torn between asking here and asking on the Fedora test list.
> 
> I'd like to use the latest xen (that's what I'm testing), but I don't want to 
> upgrade to the entire development tree.

By latest Xen do you mean '3.2.0' ? 

After discussions with upstream Xen developers we decide that Fedora will
only ever support the version of Xen that ships at the same time as that
Fedora release. eg F8 supports 3.1.x, and F9 support 3.2.x.  Meanwhile
upstream Xen will provide backports of new Xen releases for people who 
wish to try on existing Fedora. eg Xen provides a 3.2.0 RPM for Fedora 8
which you can get from xen.org. We co-operated to ensure the RPMs follow
the same style so it ought to be reasonably painless.

WRT to rawhide, I'd strongly recommend against upgrading to that any time
soon. Its just going to be too unstable to usefully run Xen until we get
the new kernel sorted. The existing kernel-xen in rawhide is known to be
broken wrt to even basic things like X and the 'ip' command.

> I tried this, and was astonished at the number of packages to upgrade!
> [root at potoroo ~]# yum install --disablerepo=* --enable=development kernel-xen 
> kernel-xen-2.6-doc xen xen-hypervisor xen-libs xenwatch | wc -l
> Error: Missing Dependency: kdemultimedia3 >= 3.5.8 is needed by package 
> kdemultimedia-extras-nonfree
> 845
> [root at potoroo ~]# 
> 
> Those 845 lines represent upgrading pretty much all of KDE and all of Gnome.

Hmm, the 'xen' RPM still has a dep on 'python-virtinst' which still has
a dep on 'virt-viewer' which uses GNOME. At very least we need to break
the dep between xen and python-virtinst - its a historical thing to assist
in upgrades from the FC5 days when 'virt-install' was part of the 'xen'
RPM itself. Since FC5 and FC6 are long dead we can kill the dep.



Dan.
-- 
|=- Red Hat, Engineering, Emerging Technologies, Boston.  +1 978 392 2496 -=|
|=-           Perl modules: http://search.cpan.org/~danberr/              -=|
|=-               Projects: http://freshmeat.net/~danielpb/               -=|
|=-  GnuPG: 7D3B9505   F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505  -=| 



From phil at pricom.com.au  Tue Jan 22 05:12:38 2008
From: phil at pricom.com.au (Phil Rhoades)
Date: Tue, 22 Jan 2008 16:12:38 +1100
Subject: [Fedora-xen] kernel-xen, qemu,
	kvm etc summary and speed of virtual machines in F8
Message-ID: <1200978758.31741.51.camel@prix.pricom.com.au>

People,

Is there available a plain summary of how all the different bits of
virtualisation fit together?  The stuff I have found so far is more
confusing than anything . .

I have been toying around with virtual machines on FC6, F7 and now F8
but there seems to have been a big slow-down in performance with F8?

This speed issue is why I have been trying to get a better understanding
of how all the bits fit together, see where the bottlenecks are and what
I can do to improve performance so that I might use the virtual machines
for real work.  

I have installed:

kernel-xen-2.6.21-2952.fc8
xen-libs-3.1.2-1.fc8
xen-3.1.2-1.fc8
qemu-0.9.0-5.fc8
kvm-36-7.fc8

Thanks,

Phil.
-- 
Philip Rhoades

Pricom Pty Limited  (ACN 003 252 275  ABN 91 003 252 275)
GPO Box 3411
Sydney NSW      2001
Australia
Fax:     +61:(0)2-8221-9599
E-mail:  phil at pricom.com.au



From Dustin.Henning at prd-inc.com  Tue Jan 22 13:20:46 2008
From: Dustin.Henning at prd-inc.com (Dustin Henning)
Date: Tue, 22 Jan 2008 08:20:46 -0500
Subject: [Fedora-xen] Upgrade to development xen on F8?
In-Reply-To: <200801220922.15116.debian@herakles.homelinux.org>
References: <200801220922.15116.debian@herakles.homelinux.org>
Message-ID: <000901c85cf9$997b8400$cc728c00$@Henning@prd-inc.com>

	You could download and build the latest stable or test source from xen.org.  This assumes you are familiar with that sort of thing, but if you want to test, you probably are...
	Dustin

-----Original Message-----
From: fedora-xen-bounces at redhat.com [mailto:fedora-xen-bounces at redhat.com] On Behalf Of John Summerfield
Sent: Monday, January 21, 2008 19:22
To: fedora-xen at redhat.com
Subject: [Fedora-xen] Upgrade to development xen on F8?

I'm a bit torn between asking here and asking on the Fedora test list.

I'd like to use the latest xen (that's what I'm testing), but I don't want to 
upgrade to the entire development tree.

I tried this, and was astonished at the number of packages to upgrade!
[root at potoroo ~]# yum install --disablerepo=* --enable=development kernel-xen 
kernel-xen-2.6-doc xen xen-hypervisor xen-libs xenwatch | wc -l
Error: Missing Dependency: kdemultimedia3 >= 3.5.8 is needed by package 
kdemultimedia-extras-nonfree
845
[root at potoroo ~]# 

Those 845 lines represent upgrading pretty much all of KDE and all of Gnome.

The package "xen" alone accounts for much of this:
[root at potoroo ~]# yum install --disablerepo=* --enable=development xen | wc -l
Error: Missing Dependency: kdemultimedia3 >= 3.5.8 is needed by package 
kdemultimedia-extras-nonfree
844
[root at potoroo ~]# 

My idea of an ideal host for virtual machines is one that runs guests and 
precious little else, and certainly not a GUI and all the baggage that 
entails. 

Do these *xen* packages build on f8? What's the easy way to get the source - I 
used to use up2date, but I fear the technolgogy's getting ahead of me.


-- 
John the Bewildered.

--
Fedora-xen mailing list
Fedora-xen at redhat.com
https://www.redhat.com/mailman/listinfo/fedora-xen





From avi at qumranet.com  Tue Jan 22 15:44:26 2008
From: avi at qumranet.com (Avi Kivity)
Date: Tue, 22 Jan 2008 17:44:26 +0200
Subject: [Fedora-xen] KVM: unhandled exception
In-Reply-To: <478EA18C.1040701@herakles.homelinux.org>
References: <478D9241.5050401@herakles.homelinux.org>	<478DD05A.1080204@qumranet.com>
	<478EA18C.1040701@herakles.homelinux.org>
Message-ID: <47960F5A.3080503@qumranet.com>

John Summerfield wrote:
> Avi Kivity wrote:
>> John Summerfield wrote:
>>> [root at potoroo ~]# /usr/bin/qemu-kvm -M pc -m 128 -smp 1 -monitor pty 
>>> -no-acpi -boot c -hda /var/lib/xen/images/rto-test.img -net 
>>> nic,macaddr=00:16:3e:31:8a:8f,vlan=0 -net tap,fd=13,script=,vlan=0 
>>> -usb -usbdevice tablet -vnc 0.0.0.0:0
>>> char device redirected to /dev/pts/35
>>> unhandled vm exit:  0x9
>>> rax 000000000000001f rbx 000000000003f530 rcx 00000000000000ff rdx 
>>> 000000000000001f
>>> rsi 0000000000000000 rdi 0000000000000063 rsp 000000000003f40c rbp 
>>> 000000000003f458
>>> r8  0000000000000000 r9  0000000000000000 r10 0000000000000000 r11 
>>> 0000000000000000
>>> r12 0000000000000000 r13 0000000000000000 r14 0000000000000000 r15 
>>> 0000000000000000
>>> rip 000000008051ecc3 rflags 00010246
>>> cs 0008 (00000000/ffffffff p 1 dpl 0 db 1 s 1 type b l 0 g 1 avl 0)
>>> ds 0023 (00000000/ffffffff p 1 dpl 3 db 1 s 1 type 3 l 0 g 1 avl 0)
>>> es 0023 (00000000/ffffffff p 1 dpl 3 db 1 s 1 type 3 l 0 g 1 avl 0)
>>> ss 0010 (00000000/ffffffff p 1 dpl 0 db 1 s 1 type 3 l 0 g 1 avl 0)
>>> fs 0030 (ffdff000/00001fff p 1 dpl 0 db 1 s 1 type 3 l 0 g 1 avl 0)
>>> gs 0000 (00000000/0000ffff p 1 dpl 0 db 0 s 1 type 3 l 0 g 0 avl 0)
>>> tr 0028 (80042000/000020ab p 1 dpl 0 db 0 s 0 type b l 0 g 0 avl 0)
>>> ldt 0000 (00000000/ffffffff p 0 dpl 0 db 0 s 0 type 0 l 0 g 0 avl 0)
>>> gdt 8003f000/3ff
>>> idt 8003f400/7ff
>>> cr0 e0000011 cr2 63 cr3 305000 cr4 20 cr8 0 efer 0
>>> Aborted
>>> [root at potoroo ~]#
>>>
>>>
>>> I created the file /var/lib/xen/images/rto-test.img by installing 
>>> Windows XP to the point it reboots.
>>>
>>
>> Did you also install it with -no-acpi?  What happens if you drop that 
>> option?
>>
>
> That commandline is copied from virt-manager's log, where it was 
> accompanied by similar, maybe exactly the same, registers dump and the 
> same error.
>
>
> What I'm seeking is information about what the error means; without it 
> users have almost no chance of fixing the problem themselves.
>
>

Well, the guest executed a hardware context switch.  Windows does this 
sometimes on the way to a blue screen as a means to get into a known 
state.  VT (and SVM) don't support hardware context switching, hence the 
dump.


> Without "-no-acpi" it runs at 105% or so CPU. vncviewer::5900 connects 
> but does not open a window.
> [root at potoroo ~]# lsof -i | grep -E '*:5[0-9]{3}\>'
> xinetd    2180    root    5u  IPv6   7547       TCP *:5902 (LISTEN)
> Xvnc      2456    root    5u  IPv4   8354       TCP *:5966 (LISTEN)
> Xvnc      2456    root    6u  IPv4   8355       TCP *:5866 (LISTEN)
> Xvnc      2456    root   48u  IPv4  22337       TCP 
> localhost.localdomain:5966->localhost.localdomain:47032 (ESTABLISHED)
> Xvnc      2500  summer    5u  IPv4   8473       TCP *:5903 (LISTEN)
> Xvnc      2500  summer    6u  IPv4   8474       TCP *:5803 (LISTEN)
> vncviewer 5533  summer    4u  IPv4  22336       TCP 
> localhost.localdomain:47032->localhost.localdomain:5966 (ESTABLISHED)
> qemu-kvm  5604    root    8u  IPv4  22589       TCP *:5900 (LISTEN)
> vncviewer 5615    root    4u  IPv4  22608       TCP 
> localhost.localdomain:34608->localhost.localdomain:5900 (ESTABLISHED)
> [root at potoroo ~]#
>

Can you try with upstream kvm (from kvm.qumranet.com)?  Though I doubt 
it's a problem with F8's kvm as XP is such a widely used guest.

-- 
error compiling committee.c: too many arguments to function



From jahrens at uni-mainz.de  Tue Jan 22 14:54:52 2008
From: jahrens at uni-mainz.de (Jens Ahrens)
Date: Tue, 22 Jan 2008 15:54:52 +0100
Subject: [Fedora-xen] Two nics on HVM
Message-ID: <479603BC.4070903@uni-mainz.de>

Hello everybody,

I'm using FC7 and my server (IntelXeonQuad 64bit) provides 2 NICs. With 
virsh-install I installed a (32bit RHEL3) HVM.
Until here everything runs fine.
When installing FC7, NIC1(eth0) got a public IP and NIC2(eth1) got a 
private one.
When installing the HVM (RHEL3) only one NIC(eth0) exists, which got a 
public IP.
The problem is that I also want the HVM to have a second NIC connected 
to my private network (as in Dom0).

By default only one bridge (virbr0) is created.
brctl show gives:
eth0            8000.003048322dea       no              vif3.0
                                                        tap0
                                                        peth0
virbr0          8000.000000000000       no

How can I create a second one for (p)eth1 ?
By the way where does tap0 come from and what is it good for?

Thanks for any help.
Jens



From txtoth at gmail.com  Tue Jan 22 20:04:07 2008
From: txtoth at gmail.com (Xavier Toth)
Date: Tue, 22 Jan 2008 14:04:07 -0600
Subject: [Fedora-xen] Re: FC8 (x86_64) host FC8 new virtual system install
	hangs
In-Reply-To: <4794C8AC.9070604@gmail.com>
References: <4794C8AC.9070604@gmail.com>
Message-ID: <cadfc0e40801221204s5138e24n959487f0bab062a5@mail.gmail.com>

I ended up unselecting the optional package (Office I think) and then
the install completed. It is both strange and disconcerting that this
fixed the problem.

On Jan 21, 2008 10:30 AM, Ted X Toth <txtoth at gmail.com> wrote:
> I'm using the Virtual Machine Manager to create a new virtual system. I
> put the anaconda tree off of the DVD on an ftp server and point to it. I
> allocate 500M of memory and 20G of disk in a file. The anaconda install
> seems to go along fine until it starts to install packages and then it
> hangs. Has anyone else experienced this? Are there any tricks to getting
> this to work?
>



From txtoth at gmail.com  Tue Jan 22 20:11:55 2008
From: txtoth at gmail.com (Xavier Toth)
Date: Tue, 22 Jan 2008 14:11:55 -0600
Subject: [Fedora-xen] kernel-xen, qemu,
	kvm etc summary and speed of virtual machines in F8
In-Reply-To: <1200978758.31741.51.camel@prix.pricom.com.au>
References: <1200978758.31741.51.camel@prix.pricom.com.au>
Message-ID: <cadfc0e40801221211i17cb4b72k8f28c321f8a75749@mail.gmail.com>

I'm interested in this too as the F8 vm I'm running on an F8 host
seems pretty slow. Also right now I'm using qemu does xen perform
better? Is there any place I can read about the tradeoff between
approaches?

On Jan 21, 2008 11:12 PM, Phil Rhoades <phil at pricom.com.au> wrote:
> People,
>
> Is there available a plain summary of how all the different bits of
> virtualisation fit together?  The stuff I have found so far is more
> confusing than anything . .
>
> I have been toying around with virtual machines on FC6, F7 and now F8
> but there seems to have been a big slow-down in performance with F8?
>
> This speed issue is why I have been trying to get a better understanding
> of how all the bits fit together, see where the bottlenecks are and what
> I can do to improve performance so that I might use the virtual machines
> for real work.
>
> I have installed:
>
> kernel-xen-2.6.21-2952.fc8
> xen-libs-3.1.2-1.fc8
> xen-3.1.2-1.fc8
> qemu-0.9.0-5.fc8
> kvm-36-7.fc8
>
> Thanks,
>
> Phil.
> --
> Philip Rhoades
>
> Pricom Pty Limited  (ACN 003 252 275  ABN 91 003 252 275)
> GPO Box 3411
> Sydney NSW      2001
> Australia
> Fax:     +61:(0)2-8221-9599
> E-mail:  phil at pricom.com.au
>
> --
> Fedora-xen mailing list
> Fedora-xen at redhat.com
> https://www.redhat.com/mailman/listinfo/fedora-xen
>



From annefacq at crpp-bordeaux.cnrs.fr  Wed Jan 23 23:35:24 2008
From: annefacq at crpp-bordeaux.cnrs.fr (Anne Facq)
Date: Thu, 24 Jan 2008 00:35:24 +0100
Subject: [Fedora-xen] How to backup a Domu filesystem (on LVM) from Dom0
	on	Fedora 8 ?
In-Reply-To: <47951A8E.2050400@digitalfairway.com>
References: <479516BB.7090701@crpp-bordeaux.cnrs.fr>
	<47951A8E.2050400@digitalfairway.com>
Message-ID: <4797CF3C.3090709@crpp-bordeaux.cnrs.fr>

Aaron Clark wrote:
> Anne Facq wrote:
>> Hello
>>
>> I use XEN on Fedora 8 with Domu on a LVM partition.
>>
>> Before, on Fedora Core 6, I could backup each Domu by directly 
>> mounting the filesystem of the Domu (mount /dev/vg00/lvfoo /mnt) and 
>> then running dump on it.
>>
>> On Fedora 8, I can't mount directly the filesystem of the Domu, so I 
> 
> Pardon if this is a dumb question, but why not?

Because in Dom0 the device for a paravirt Domu (/dev/vg00/lvfoo in my
case) is mapped to a virtual disk /dev/xvda (I created the Domu with 
virt-install), and the only way I found to mount this Domu filesystem, 
is to :
- get the size of the boot sector of /dev/vg00/lvfoo
	(with fdisk -ul /dev/vg00/lvfoo)
	= 63
- compute the offset (multiply by block size)
- specify this offset to the mount command :
mount -o offset=32256 /dev/vg00/lvfoo /mnt/

As I can't specify an offset to dump, the command "dump 0 -f lvfoo.dump
/mnt" doesn't work.

>> backup the filesystem of the Domu using the dd command (dd 
>> if=/dev/vg00/lvfoo of=/var/xen/lvfoo.img)
>> But the backup with dd is longer and takes more disk space than the 
>> backup with dump, as dd copies unused blocks.
>>
>> Is there a better method to backup a Domu filesystem from Dom0 on 
>> Fedora 8 ?
> 
> I suppose you could use the img2qcow tool (possibly directly on 
> /dev/vg00/lvfoo) to get a qcow file instead of a raw image.  However, I 
> vaguely remember seeing somewhere that the qcow created by the xen tools 
> is not necessarily 100% compatible with other qcow tools.

Thanks for you help, I'm going to have a look at it.

Regards,

Anne Facq




From kraxel at redhat.com  Thu Jan 24 08:58:58 2008
From: kraxel at redhat.com (Gerd Hoffmann)
Date: Thu, 24 Jan 2008 09:58:58 +0100
Subject: [Fedora-xen] How to backup a Domu filesystem (on LVM) from Dom0
	on	Fedora 8 ?
In-Reply-To: <4797CF3C.3090709@crpp-bordeaux.cnrs.fr>
References: <479516BB.7090701@crpp-bordeaux.cnrs.fr>	<47951A8E.2050400@digitalfairway.com>
	<4797CF3C.3090709@crpp-bordeaux.cnrs.fr>
Message-ID: <47985352.3010208@redhat.com>

Anne Facq wrote:
> Because in Dom0 the device for a paravirt Domu (/dev/vg00/lvfoo in my
> case) is mapped to a virtual disk /dev/xvda (I created the Domu with
> virt-install), and the only way I found to mount this Domu filesystem,
> is to :
> - get the size of the boot sector of /dev/vg00/lvfoo
>     (with fdisk -ul /dev/vg00/lvfoo)
>     = 63
> - compute the offset (multiply by block size)
> - specify this offset to the mount command :
> mount -o offset=32256 /dev/vg00/lvfoo /mnt/

Uh, oh, quite complicated and error prone.  Can be done much easier.

Option (1): Use kpartx, it will create device mapper mappings for your
partitions.  Try "kpartx -v -a /dev/vg00/lvfoo", should give you
/dev/vg00/lvfoop[1234].  "kpartx -d ... " removes the mappings.

Option (2): (works only with xen kernel): Configure the device as
virtual disk *in Domain-0*: "xm block-attach 0 phy:/dev/vg00/lvfoo xvda
w".  Gives you /dev/xvda[1234].  "xm block-detach ..." removes it.

HTH,
  Gerd



From armbru at redhat.com  Thu Jan 24 09:18:39 2008
From: armbru at redhat.com (Markus Armbruster)
Date: Thu, 24 Jan 2008 10:18:39 +0100
Subject: [Fedora-xen] How to backup a Domu filesystem (on LVM) from Dom0
	on	Fedora 8 ?
In-Reply-To: <4797CF3C.3090709@crpp-bordeaux.cnrs.fr> (Anne Facq's message of
	"Thu\, 24 Jan 2008 00\:35\:24 +0100")
References: <479516BB.7090701@crpp-bordeaux.cnrs.fr>
	<47951A8E.2050400@digitalfairway.com>
	<4797CF3C.3090709@crpp-bordeaux.cnrs.fr>
Message-ID: <87d4rrlgy8.fsf@pike.pond.sub.org>

Anne Facq <annefacq at crpp-bordeaux.cnrs.fr> writes:

> Aaron Clark wrote:
>> Anne Facq wrote:
>>> Hello
>>>
>>> I use XEN on Fedora 8 with Domu on a LVM partition.
>>>
>>> Before, on Fedora Core 6, I could backup each Domu by directly
>>> mounting the filesystem of the Domu (mount /dev/vg00/lvfoo /mnt)
>>> and then running dump on it.
>>>
>>> On Fedora 8, I can't mount directly the filesystem of the Domu, so
>>> I 
>>
>> Pardon if this is a dumb question, but why not?
>
> Because in Dom0 the device for a paravirt Domu (/dev/vg00/lvfoo in my
> case) is mapped to a virtual disk /dev/xvda (I created the Domu with
> virt-install), and the only way I found to mount this Domu filesystem,
> is to :
> - get the size of the boot sector of /dev/vg00/lvfoo
> 	(with fdisk -ul /dev/vg00/lvfoo)
> 	= 63
> - compute the offset (multiply by block size)
> - specify this offset to the mount command :
> mount -o offset=32256 /dev/vg00/lvfoo /mnt/
>
> As I can't specify an offset to dump, the command "dump 0 -f lvfoo.dump
> /mnt" doesn't work.

Shot from the hip: losetup with the offset?

[...]



From debian at herakles.homelinux.org  Thu Jan 24 14:15:44 2008
From: debian at herakles.homelinux.org (John Summerfield)
Date: Thu, 24 Jan 2008 23:15:44 +0900
Subject: [Fedora-xen] Two nics on HVM
In-Reply-To: <479603BC.4070903@uni-mainz.de>
References: <479603BC.4070903@uni-mainz.de>
Message-ID: <47989D90.1080607@herakles.homelinux.org>

Jens Ahrens wrote:
> Hello everybody,
> 
> I'm using FC7 and my server (IntelXeonQuad 64bit) provides 2 NICs. With 
> virsh-install I installed a (32bit RHEL3) HVM.
> Until here everything runs fine.
> When installing FC7, NIC1(eth0) got a public IP and NIC2(eth1) got a 
> private one.
> When installing the HVM (RHEL3) only one NIC(eth0) exists, which got a 
> public IP.
> The problem is that I also want the HVM to have a second NIC connected 
> to my private network (as in Dom0).

My first thought, Does swapping the wires fix this? Crude maybe, but it 
should work.

Then I thought "oh, you might need to attack ifcfg-eth0 and ifcfg-eth1 
to delete the MAC addresses."

Now, I'm thinking that running system-config-network to swap the 
definitions so that eth1 is the gateway to the world and the other's 
private.

That should work, and continue to work over time.


> 
> By default only one bridge (virbr0) is created.
> brctl show gives:
> eth0            8000.003048322dea       no              vif3.0
>                                                        tap0
>                                                        peth0
> virbr0          8000.000000000000       no
> 
> How can I create a second one for (p)eth1 ?
> By the way where does tap0 come from and what is it good for?
> 
> Thanks for any help.
> Jens
I had  half-hearted fiddle with opensuse 10.2 on my laptop (wireless and 
wire, i want the guest on the wireless) and didn't get anywhere.




-- 

Cheers
John

-- spambait
1aaaaaaa at coco.merseine.nu  Z1aaaaaaa at coco.merseine.nu
-- Advice
http://webfoot.com/advice/email.top.php
http://www.catb.org/~esr/faqs/smart-questions.html
http://support.microsoft.com/kb/555375

You cannot reply off-list:-)



From debian at herakles.homelinux.org  Thu Jan 24 14:20:04 2008
From: debian at herakles.homelinux.org (John Summerfield)
Date: Thu, 24 Jan 2008 23:20:04 +0900
Subject: [Fedora-xen] kernel-xen, qemu,
	kvm etc summary and speed of virtual machines in F8
In-Reply-To: <1200978758.31741.51.camel@prix.pricom.com.au>
References: <1200978758.31741.51.camel@prix.pricom.com.au>
Message-ID: <47989E94.7020002@herakles.homelinux.org>

Phil Rhoades wrote:
> People,
> 
> Is there available a plain summary of how all the different bits of
> virtualisation fit together?  The stuff I have found so far is more
> confusing than anything . .
> 
> I have been toying around with virtual machines on FC6, F7 and now F8
> but there seems to have been a big slow-down in performance with F8?
> 
> This speed issue is why I have been trying to get a better understanding
> of how all the bits fit together, see where the bottlenecks are and what
> I can do to improve performance so that I might use the virtual machines
> for real work.  


I'll throw my "me too" in. I am sure my first guest, Debian an an F8 
beta, could do disk at 148 Mbytes/sec, as measured with hdparm.

This made some kind of sense, I thought, as it would be hitting RAM on 
the host.

No more, disk is about Pentium class or worse.

I've been using hardware virtualisation all the time, and that first 
guest was with Xen.


-- 

Cheers
John

-- spambait
1aaaaaaa at coco.merseine.nu  Z1aaaaaaa at coco.merseine.nu
-- Advice
http://webfoot.com/advice/email.top.php
http://www.catb.org/~esr/faqs/smart-questions.html
http://support.microsoft.com/kb/555375

You cannot reply off-list:-)



From debian at herakles.homelinux.org  Fri Jan 25 09:53:30 2008
From: debian at herakles.homelinux.org (John Summerfield)
Date: Fri, 25 Jan 2008 18:53:30 +0900
Subject: [Fedora-xen] Problem building xen-3.2 on f8
Message-ID: <200801251853.30887.debian@herakles.homelinux.org>

I'm building for AMD-64/EMT64. The build terminates this:
Requires: libflask.so.1.0()(64bit) libfsimage.so.1.0()(64bit) 
libxenctrl.so.3.2()(64bit) libxenguest.so.3.2()(64bit) libxenstore.so.3.0()
(64bit)
Checking for unpackaged 
file(s): /usr/lib/rpm/check-files /var/tmp/xen-3.2.0-2.fc8-root


RPM build errors:
    user mockbuild does not exist - using root
    group mockbuild does not exist - using root
    user mockbuild does not exist - using root
    group mockbuild does not exist - using root
    user mockbuild does not exist - using root
    group mockbuild does not exist - using root
    user mockbuild does not exist - using root
    group mockbuild does not exist - using root
    user mockbuild does not exist - using root
    group mockbuild does not exist - using root
    user mockbuild does not exist - using root
    group mockbuild does not exist - using root
    user mockbuild does not exist - using root
    group mockbuild does not exist - using root
    user mockbuild does not exist - using root
    group mockbuild does not exist - using root
    user mockbuild does not exist - using root
    group mockbuild does not exist - using root
    user mockbuild does not exist - using root
    group mockbuild does not exist - using root
    user mockbuild does not exist - using root
    group mockbuild does not exist - using root
    user mockbuild does not exist - using root
    group mockbuild does not exist - using root
    user mockbuild does not exist - using root
    group mockbuild does not exist - using root
    user mockbuild does not exist - using root
    group mockbuild does not exist - using root
    user mockbuild does not exist - using root
    group mockbuild does not exist - using root
    File not found by 
glob: /var/tmp/xen-3.2.0-2.fc8-root/usr/lib64/python2.5/site-packages/pygrub-*.egg-info
    File not found by 
glob: /var/tmp/xen-3.2.0-2.fc8-root/usr/lib64/python2.5/site-packages/xen-*.egg-info
[root at potoroo ~]# 

I'm using the standard rpm configuration for F8.

It's only the glob messages that concern me.



From berrange at redhat.com  Fri Jan 25 13:59:29 2008
From: berrange at redhat.com (Daniel P. Berrange)
Date: Fri, 25 Jan 2008 13:59:29 +0000
Subject: [Fedora-xen] Problem building xen-3.2 on f8
In-Reply-To: <200801251853.30887.debian@herakles.homelinux.org>
References: <200801251853.30887.debian@herakles.homelinux.org>
Message-ID: <20080125135929.GC7237@redhat.com>

On Fri, Jan 25, 2008 at 06:53:30PM +0900, John Summerfield wrote:
> I'm building for AMD-64/EMT64. The build terminates this:
> Requires: libflask.so.1.0()(64bit) libfsimage.so.1.0()(64bit) 
> libxenctrl.so.3.2()(64bit) libxenguest.so.3.2()(64bit) libxenstore.so.3.0()
> (64bit)
> Checking for unpackaged 
> file(s): /usr/lib/rpm/check-files /var/tmp/xen-3.2.0-2.fc8-root

The way python is handled in F9 change slightly, so F9 RPMs will not
rebuild for F8 without modifications. We don't intend to support 3.20
on Fedora 8 - we're stickin with 3.1.x bug fix tree. Upstream Xen will
however provide 3.2.0 RPMs for Fedora 8  for those who wish to try it
out ahead of official Fedora 9 release

http://xen.org/download/dl_32rhel8.html

Dan.
-- 
|=- Red Hat, Engineering, Emerging Technologies, Boston.  +1 978 392 2496 -=|
|=-           Perl modules: http://search.cpan.org/~danberr/              -=|
|=-               Projects: http://freshmeat.net/~danielpb/               -=|
|=-  GnuPG: 7D3B9505   F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505  -=| 



From Dustin.Henning at prd-inc.com  Fri Jan 25 15:28:37 2008
From: Dustin.Henning at prd-inc.com (Dustin Henning)
Date: Fri, 25 Jan 2008 10:28:37 -0500
Subject: [Fedora-xen] Problem building xen-3.2 on f8
In-Reply-To: <20080125135929.GC7237@redhat.com>
References: <200801251853.30887.debian@herakles.homelinux.org>
	<20080125135929.GC7237@redhat.com>
Message-ID: <000301c85f66$f5711170$e0533450$@Henning@prd-inc.com>

John,
	Are you trying to rebuild an F9 rpm as Dan suggests, or are you
trying to build directly from the source tarball from xen.org?  I didn't
think much of anything would build with the standard rpm configuration for
Fedora (though I haven't run F8), so my first thought would be that you need
to install some other rpms, but I can't really suggest which ones, if any of
those required files don't exist on your system, you may be able to find out
what needs installed to obtain them from a site like rpmfind.net.  If all of
those files do exist, then I can't really tell you what those errors mean,
but assuming you let the group know that you are trying to build from the
xen.org source, then maybe someone else can help.  On the other hand, it may
be that a difference in python versions available from F8 to F9 could still
make a difference leaving you to wit for xen.org rpms for F8 or build a
newer version of python manually as well.  Good luck with whatever you're
trying,
	Dustin

-----Original Message-----
From: fedora-xen-bounces at redhat.com [mailto:fedora-xen-bounces at redhat.com]
On Behalf Of Daniel P. Berrange
Sent: Friday, January 25, 2008 08:59
To: John Summerfield
Cc: fedora-xen at redhat.com
Subject: Re: [Fedora-xen] Problem building xen-3.2 on f8

On Fri, Jan 25, 2008 at 06:53:30PM +0900, John Summerfield wrote:
> I'm building for AMD-64/EMT64. The build terminates this:
> Requires: libflask.so.1.0()(64bit) libfsimage.so.1.0()(64bit) 
> libxenctrl.so.3.2()(64bit) libxenguest.so.3.2()(64bit)
libxenstore.so.3.0()	
> (64bit)
> Checking for unpackaged 
> file(s): /usr/lib/rpm/check-files /var/tmp/xen-3.2.0-2.fc8-root

The way python is handled in F9 change slightly, so F9 RPMs will not
rebuild for F8 without modifications. We don't intend to support 3.20
on Fedora 8 - we're stickin with 3.1.x bug fix tree. Upstream Xen will
however provide 3.2.0 RPMs for Fedora 8  for those who wish to try it
out ahead of official Fedora 9 release

http://xen.org/download/dl_32rhel8.html

Dan.
-- 
|=- Red Hat, Engineering, Emerging Technologies, Boston.  +1 978 392 2496
-=|
|=-           Perl modules: http://search.cpan.org/~danberr/
-=|
|=-               Projects: http://freshmeat.net/~danielpb/
-=|
|=-  GnuPG: 7D3B9505   F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505
-=| 

--
Fedora-xen mailing list
Fedora-xen at redhat.com
https://www.redhat.com/mailman/listinfo/fedora-xen




From debian at herakles.homelinux.org  Sat Jan 26 00:48:30 2008
From: debian at herakles.homelinux.org (John Summerfield)
Date: Sat, 26 Jan 2008 09:48:30 +0900
Subject: [Fedora-xen] Problem building xen-3.2 on f8
In-Reply-To: <000301c85f66$f5711170$e0533450$@Henning@prd-inc.com>
References: <200801251853.30887.debian@herakles.homelinux.org>	<20080125135929.GC7237@redhat.com>
	<000301c85f66$f5711170$e0533450$@Henning@prd-inc.com>
Message-ID: <479A835E.5000903@herakles.homelinux.org>

Dustin Henning wrote:
> John,
> 	Are you trying to rebuild an F9 rpm as Dan suggests, or are you
> trying to build directly from the source tarball from xen.org?  I didn't
> think much of anything would build with the standard rpm configuration for
> Fedora (though I haven't run F8), so my first thought would be that you need
> to install some other rpms, but I can't really suggest which ones, if any of
> those required files don't exist on your system, you may be able to find out
> what needs installed to obtain them from a site like rpmfind.net.  If all of
> those files do exist, then I can't really tell you what those errors mean,
> but assuming you let the group know that you are trying to build from the
> xen.org source, then maybe someone else can help.  On the other hand, it may
> be that a difference in python versions available from F8 to F9 could still
> make a difference leaving you to wit for xen.org rpms for F8 or build a
> newer version of python manually as well.  Good luck with whatever you're
> trying,

I haven't seen Dan's reply yet, and might not if he's replied off-list.

I am trying to build the f9 rpm, the problem is the rpm's trying to 
package files that don't get created (and I can't see any way they could 
get created).


> 	Dustin
> 
> -----Original Message-----
> From: fedora-xen-bounces at redhat.com [mailto:fedora-xen-bounces at redhat.com]
> On Behalf Of Daniel P. Berrange
> Sent: Friday, January 25, 2008 08:59
> To: John Summerfield
> Cc: fedora-xen at redhat.com
> Subject: Re: [Fedora-xen] Problem building xen-3.2 on f8
> 
> On Fri, Jan 25, 2008 at 06:53:30PM +0900, John Summerfield wrote:
>> I'm building for AMD-64/EMT64. The build terminates this:
>> Requires: libflask.so.1.0()(64bit) libfsimage.so.1.0()(64bit) 
>> libxenctrl.so.3.2()(64bit) libxenguest.so.3.2()(64bit)
> libxenstore.so.3.0()	
>> (64bit)
>> Checking for unpackaged 
>> file(s): /usr/lib/rpm/check-files /var/tmp/xen-3.2.0-2.fc8-root
> 
> The way python is handled in F9 change slightly, so F9 RPMs will not
> rebuild for F8 without modifications. We don't intend to support 3.20
> on Fedora 8 - we're stickin with 3.1.x bug fix tree. Upstream Xen will
> however provide 3.2.0 RPMs for Fedora 8  for those who wish to try it
> out ahead of official Fedora 9 release
> 
> http://xen.org/download/dl_32rhel8.html

The packages there are unsuitable, I'm 64-bit. I'm continuing the search.



-- 

Cheers
John

-- spambait
1aaaaaaa at coco.merseine.nu  Z1aaaaaaa at coco.merseine.nu
-- Advice
http://webfoot.com/advice/email.top.php
http://www.catb.org/~esr/faqs/smart-questions.html
http://support.microsoft.com/kb/555375

You cannot reply off-list:-)



From debian at herakles.homelinux.org  Sat Jan 26 08:33:33 2008
From: debian at herakles.homelinux.org (John Summerfield)
Date: Sat, 26 Jan 2008 17:33:33 +0900
Subject: [Fedora-xen] Problem building xen-3.2 on f8
In-Reply-To: <479A835E.5000903@herakles.homelinux.org>
References: <200801251853.30887.debian@herakles.homelinux.org>
	<000301c85f66$f5711170$e0533450$@Henning@prd-inc.com>
	<479A835E.5000903@herakles.homelinux.org>
Message-ID: <200801261733.33997.debian@herakles.homelinux.org>

On Sat, 26 Jan 2008 09:48:30 am John Summerfield wrote:
>
>
> I am trying to build the f9 rpm, the problem is the rpm's trying to
> package files that don't get created (and I can't see any way they could
> get created).

After some finger failures, I have built Ian's xen 3.2.0 src.rpm and installed 
the results, and booted the latest 2.6.21 f9 kernel (which I note is upgraded 
to 3.2).

So far, testing has been limited to "xm list" which works as expected.



From debian at herakles.homelinux.org  Sat Jan 26 12:17:32 2008
From: debian at herakles.homelinux.org (John Summerfield)
Date: Sat, 26 Jan 2008 21:17:32 +0900
Subject: [Fedora-xen] Upgrade to development xen on F8?
In-Reply-To: <000901c85cf9$997b8400$cc728c00$@Henning@prd-inc.com>
References: <200801220922.15116.debian@herakles.homelinux.org>
	<000901c85cf9$997b8400$cc728c00$@Henning@prd-inc.com>
Message-ID: <479B24DC.1090700@herakles.homelinux.org>

Dustin Henning wrote:
> 	You could download and build the latest stable or test source from xen.org.  This assumes you are familiar with that sort of thing, but if you want to test, you probably are...
> 	Dustin
> 

I've downloaded built and installed ian jackson's xen 3.2 src.rpm from xen.

I've downloaded, built and installed these:
libvirt-0.4.0-4.fc9.src.rpm
python-virtinst-0.300.2-2.fc9.src.rpm
virt-manager-0.5.3-1.fc9.src.rpm
virt-viewer-0.0.2-3.fc9.src.rpm
xen-3.2.0-0xs.fc8.src.rpm

I'm using this kernel:
2.6.21.7-2893.fc9xen

When I try to start a guest that worked earlier:

[root at potoroo ~]# virsh start DebianEtch
libvir: Xen Daemon error : POST operation failed: (xend.err "long() 
argument must be a string or a number, not 'NoneType'")
error: Failed to start domain DebianEtch

[root at potoroo ~]# virsh version
Compiled against library: libvir 0.4.0
Using library: libvir 0.4.0
Using API: Xen 3.0.1
Running hypervisor: Xen 3.2.0

[root at potoroo ~]#

the obvious problem to my eyes is the API version, but of course the 
obvious isn't always right.

-- 

Cheers
John

-- spambait
1aaaaaaa at coco.merseine.nu  Z1aaaaaaa at coco.merseine.nu
-- Advice
http://webfoot.com/advice/email.top.php
http://www.catb.org/~esr/faqs/smart-questions.html
http://support.microsoft.com/kb/555375

You cannot reply off-list:-)



From berrange at redhat.com  Sat Jan 26 15:54:27 2008
From: berrange at redhat.com (Daniel P. Berrange)
Date: Sat, 26 Jan 2008 15:54:27 +0000
Subject: [Fedora-xen] Upgrade to development xen on F8?
In-Reply-To: <479B24DC.1090700@herakles.homelinux.org>
References: <200801220922.15116.debian@herakles.homelinux.org>
	<479B24DC.1090700@herakles.homelinux.org>
Message-ID: <20080126155427.GA15278@redhat.com>

On Sat, Jan 26, 2008 at 09:17:32PM +0900, John Summerfield wrote:
> Dustin Henning wrote:
> >	You could download and build the latest stable or test source from 
> >	xen.org.  This assumes you are familiar with that sort of thing, but 
> >	if you want to test, you probably are...
> >	Dustin
> >
> 
> I've downloaded built and installed ian jackson's xen 3.2 src.rpm from xen.
> 
> I've downloaded, built and installed these:
> libvirt-0.4.0-4.fc9.src.rpm
> python-virtinst-0.300.2-2.fc9.src.rpm
> virt-manager-0.5.3-1.fc9.src.rpm
> virt-viewer-0.0.2-3.fc9.src.rpm
> xen-3.2.0-0xs.fc8.src.rpm
> 
> I'm using this kernel:
> 2.6.21.7-2893.fc9xen
> 
> When I try to start a guest that worked earlier:
> 
> [root at potoroo ~]# virsh start DebianEtch
> libvir: Xen Daemon error : POST operation failed: (xend.err "long() 
> argument must be a string or a number, not 'NoneType'")
> error: Failed to start domain DebianEtch


This is a bug in Xen 3.2.0

http://xenbits.xensource.com/xen-3.2-testing.hg?rev/bf534df13095

Dan.
-- 
|=- Red Hat, Engineering, Emerging Technologies, Boston.  +1 978 392 2496 -=|
|=-           Perl modules: http://search.cpan.org/~danberr/              -=|
|=-               Projects: http://freshmeat.net/~danielpb/               -=|
|=-  GnuPG: 7D3B9505   F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505  -=| 



From debian at herakles.homelinux.org  Sat Jan 26 23:36:41 2008
From: debian at herakles.homelinux.org (John Summerfield)
Date: Sun, 27 Jan 2008 08:36:41 +0900
Subject: [Fedora-xen] management of this list
Message-ID: <200801270836.41391.debian@herakles.homelinux.org>

there are some things I don't like about the way this list is implemented, the 
key one being that it's set to default to sending replies off-list.

My preferred email clients (Thunderbird and Seamonkey) do not have any means 
of sending replies only to the list, so I find myself sometimes sending 
replies I intend for the list, off-list.

Worse, I miss replies to some of my queries; I've seen replies in the archives 
that haven't made it to me.

I have visited https://www.redhat.com/mailman/options/fedora-xen and 
turned "Avoid duplicate copies of messages" off, but still miss replies.

The whole issue would be solved, both for incoming and outgoing email, if the 
default list behaviour was changed to send replies to the list; this is 
appropriate for a discussion such as this.

Please, Could this be done?
-- 

John Summerfield



From debian at herakles.homelinux.org  Sat Jan 26 23:58:39 2008
From: debian at herakles.homelinux.org (John Summerfield)
Date: Sun, 27 Jan 2008 08:58:39 +0900
Subject: [Fedora-xen] Upgrade to development xen on F8?
In-Reply-To: <20080126155427.GA15278@redhat.com>
References: <200801220922.15116.debian@herakles.homelinux.org>
	<479B24DC.1090700@herakles.homelinux.org>
	<20080126155427.GA15278@redhat.com>
Message-ID: <200801270858.39508.debian@herakles.homelinux.org>

On Sun, 27 Jan 2008 12:54:27 am Daniel P. Berrange wrote:

>
> This is a bug in Xen 3.2.0
>
> http://xenbits.xensource.com/xen-3.2-testing.hg?rev/bf534df13095


Thanks for that, a little vim goes a long way.

Now, my test system does not connect to the network; it starts, but it cannot 
obtain an IP address by dhcp. I have not yet tried manual configuuration.

I added a second NIC with virt-manager. Here is the resultant XML:

[root at potoroo ~]# virsh dumpxml DebianEtch 
<domain type='xen' id='-1'>
  <name>DebianEtch</name>
  <uuid>deec1a9a-dea6-8de5-d6d0-79eb94be561c</uuid>
  <os>
    <type>hvm</type>
    <loader>/usr/lib/xen/boot/hvmloader</loader>
    <boot dev='hd'/>
  </os>
  <memory>262144</memory>
  <vcpu>1</vcpu>
  <on_poweroff>destroy</on_poweroff>
  <on_reboot>restart</on_reboot>
  <on_crash>restart</on_crash>
  <features>
    <acpi/>
    <apic/>
    <pae/>
  </features>
  <clock offset='utc'/>
  <devices>
    <emulator>/usr/lib64/xen/bin/qemu-dm</emulator>
    <interface type='bridge'>
      <source bridge='eth0'/>
      <target dev='vif-1.0'/>
      <mac address='00:16:3e:54:ba:6f'/>
      <script path='vif-bridge'/>
    </interface>
    <interface type='bridge'>
      <source bridge='peth0 (Bridge eth0)'/>
      <target dev='vif-1.1'/>
      <mac address='00:16:3e:34:89:a2'/>
    </interface>
    <disk type='file' device='disk'>
      <driver name='file'/>
      <source file='/var/lib/xen/images/DebianEtch.img'/>
      <target dev='hda'/>
    </disk>
    <disk device='cdrom'>
      <target dev='hdc'/>
      <readonly/>
    </disk>
    <input type='mouse' bus='ps2'/>
    <graphics type='vnc' port='-1' listen='0.0.0.0'/>
  </devices>
</domain>

[root at potoroo ~]# 

[root at potoroo ~]# virsh start DebianEtch
libvir: Xen Daemon error : POST operation failed: (xend.err 'Device 1 (vif) 
could not be connected. Could not find bridge device peth0 (Bridge eth0)')
error: Failed to start domain DebianEtch

[root at potoroo ~]# 

This is selinux getting in the way (it does it all the time). (sealert popped 
up).

or not:
[root at potoroo ~]# setenforce 0
[root at potoroo ~]# virsh start DebianEtch
libvir: Xen Daemon error : POST operation failed: (xend.err 'Device 1 (vif) 
could not be connected. Could not find bridge device peth0 (Bridge eth0)')
error: Failed to start domain DebianEtch

[root at potoroo ~]# 

Here is the bridge information:
[root at potoroo ~]# /usr/sbin/brctl show
bridge name     bridge id               STP enabled     interfaces
eth0            8000.00187184a59e       no              peth0
virbr0          8000.000000000000       yes
[root at potoroo ~]# /usr/sbin/brctl showmacs eth0
port no mac addr                is local?       ageing timer
  1     00:0d:60:f0:ac:5c       no                 0.42
  1     00:11:5b:e1:d8:5c       no                 0.42
  1     00:11:d8:70:68:15       no               226.66
  1     00:18:71:84:a5:9e       yes                0.00
[root at potoroo ~]# /usr/sbin/brctl showmacs virbr0
port no mac addr                is local?       ageing timer
[root at potoroo ~]# /usr/sbin/brctl showstp eth0
eth0
 bridge id              8000.00187184a59e
 designated root        8000.00187184a59e
 root port                 0                    path cost                  0
 max age                  19.99                 bridge max age            
19.99
 hello time                1.99                 bridge hello time          
1.99
 forward delay             0.00                 bridge forward delay       
0.00
 ageing time             299.95
 hello timer               0.28                 tcn timer                  
0.00
 topology change timer     0.00                 gc timer                   
0.06
 flags


peth0 (0)
 port id                0000                    state                
forwarding
 designated root        8000.00187184a59e       path cost                 19
 designated bridge      8000.00187184a59e       message age timer          
0.00
 designated port        8001                    forward delay timer        
0.00
 designated cost           0                    hold timer                 
0.00
 flags

[root at potoroo ~]# /usr/sbin/brctl showstp virbr0
virbr0
 bridge id              8000.000000000000
 designated root        8000.000000000000
 root port                 0                    path cost                  0
 max age                  19.99                 bridge max age            
19.99
 hello time                1.99                 bridge hello time          
1.99
 forward delay            14.99                 bridge forward delay      
14.99
 ageing time             299.95
 hello timer               0.93                 tcn timer                  
0.00
 topology change timer     0.00                 gc timer                   
0.03
 flags


[root at potoroo ~]# 

and xend's log:
[2008-01-27 08:48:54 2815] INFO (image:139) buildDomain os=hvm dom=4 vcpus=1
[2008-01-27 08:48:54 2815] INFO (XendDomainInfo:1504) createDevice: vkbd : 
{'devid': 0, 'uuid': '82b7a0a0-c238-98d8-36cd-96901eb712d1'}
[2008-01-27 08:48:54 2815] INFO (XendDomainInfo:1504) createDevice: vfb : 
{'vncunused': '1', 'vnclisten': '0.0.0.0', 'uuid': '26d3bc94-7b41-186d-da60-6b4734407ccd', 'devid': 
0, 'other_config': 
{'vncunused': '1', 'vnclisten': '0.0.0.0', 'type': 'vnc'}, 'location': '0.0.0.0:5901', 'type': 'vnc'}
[2008-01-27 08:48:54 2815] INFO (XendDomainInfo:1504) createDevice: console : 
{'location': '3', 'devid': 
0, 'protocol': 'vt100', 'uuid': '0ea8b31a-4693-515a-a3d0-acb6fe4cef79', 'other_config': 
{}}
[2008-01-27 08:48:54 2815] INFO (XendDomainInfo:1504) createDevice: vbd : 
{'uuid': '78d21254-b846-a9d4-f2eb-84b6ccddaf9d', 'bootable': 1, 'devid': 
768, 'driver': 'paravirtualised', 'dev': 'hda:disk', 'uname': 'file:/var/lib/xen/images/DebianEtch.img', 'mode': 'w'}
[2008-01-27 08:48:54 2815] INFO (XendDomainInfo:1504) createDevice: vbd : 
{'uuid': '08faae4e-1f81-e81a-ef71-8658ba92f163', 'bootable': 0, 'devid': 
5632, 'driver': 'paravirtualised', 'dev': 'hdc:cdrom', 'mode': 'r'}
[2008-01-27 08:48:54 2815] INFO (XendDomainInfo:1504) createDevice: vif : 
{'bridge': 'eth0', 'mac': '00:16:3e:54:ba:6f', 'devid': 
0, 'uuid': '51cc67dd-753a-ef22-5e79-b0c021fa0b2e', 'script': 'vif-bridge'}
[2008-01-27 08:48:54 2815] INFO (XendDomainInfo:1504) createDevice: vif : 
{'bridge': 'peth0 (Bridge eth0)', 'mac': '00:16:3e:34:89:a2', 'devid': 
1, 'uuid': 'cc27aac1-7f80-990d-4325-1d151101790e'}
[2008-01-27 08:48:54 2815] INFO (image:283) spawning device 
models: /usr/lib64/xen/bin/qemu-dm 
['/usr/lib64/xen/bin/qemu-dm', '-d', '4', '-domain-name', 'DebianEtch', '-vnc', '0.0.0.0:0', '-vncunused', '-vcpus', '1', '-boot', 'c', '-acpi', '-usb', '-net', 'nic,vlan=1,macaddr=00:16:3e:54:ba:6f,model=rtl8139', '-net', 'tap,vlan=1,bridge=eth0', '-net', 'nic,vlan=2,macaddr=00:16:3e:34:89:a2,model=rtl8139', '-net', 'tap,vlan=2,bridge=peth0 
(Bridge eth0)', '-M', 'xenfv']
[2008-01-27 08:48:54 2815] INFO (image:287) device model pid: 23649
[2008-01-27 08:48:56 2815] WARNING (XendDomain:1035) Failed to setup devices 
for <domain id=4 name=DebianEtch memory=268435456 state=paused>: Device 1 
(vif) could not be connected. Could not find bridge device peth0 (Bridge 
eth0)
[2008-01-27 08:48:57 2815] ERROR (SrvBase:88) Request start failed.
Traceback (most recent call last):
  File "/usr/lib64/python2.5/site-packages/xen/web/SrvBase.py", line 85, in 
perform
    return op_method(op, req)
  File "/usr/lib64/python2.5/site-packages/xen/xend/server/SrvDomain.py", line 
77, in op_start
    return self.xd.domain_start(self.dom.getName(), paused)
  File "/usr/lib64/python2.5/site-packages/xen/xend/XendDomain.py", line 1033, 
in domain_start
    dominfo.waitForDevices()
  File "/usr/lib64/python2.5/site-packages/xen/xend/XendDomainInfo.py", line 
581, in waitForDevices
    self.getDeviceController(devclass).waitForDevices()
  File "/usr/lib64/python2.5/site-packages/xen/xend/server/DevController.py", 
line 151, in waitForDevices
    return map(self.waitForDevice, self.deviceIDs())
  File "/usr/lib64/python2.5/site-packages/xen/xend/server/DevController.py", 
line 176, in waitForDevice
    "%s" % (devid, self.deviceClass, err))
VmError: Device 1 (vif) could not be connected. Could not find bridge device 
peth0 (Bridge eth0)
[root at potoroo ~]# 



From berrange at redhat.com  Sun Jan 27 02:24:37 2008
From: berrange at redhat.com (Daniel P. Berrange)
Date: Sun, 27 Jan 2008 02:24:37 +0000
Subject: [Fedora-xen] management of this list
In-Reply-To: <200801270836.41391.debian@herakles.homelinux.org>
References: <200801270836.41391.debian@herakles.homelinux.org>
Message-ID: <20080127022437.GA1762@redhat.com>

On Sun, Jan 27, 2008 at 08:36:41AM +0900, John Summerfield wrote:
> there are some things I don't like about the way this list is implemented, the 
> key one being that it's set to default to sending replies off-list.
> 
> My preferred email clients (Thunderbird and Seamonkey) do not have any means 
> of sending replies only to the list, so I find myself sometimes sending 
> replies I intend for the list, off-list.
> 
> Worse, I miss replies to some of my queries; I've seen replies in the archives 
> that haven't made it to me.
> 
> I have visited https://www.redhat.com/mailman/options/fedora-xen and 
> turned "Avoid duplicate copies of messages" off, but still miss replies.
> 
> The whole issue would be solved, both for incoming and outgoing email, if the 
> default list behaviour was changed to send replies to the list; this is 
> appropriate for a discussion such as this.

I'm not going to get into this discussion again, other than to refer
you to the previous thread

  http://www.redhat.com/archives/fedora-xen/2007-May/msg00021.html

To quote Markus

 "This just replaces one set of problems with a different set of
  arguably worse problems, shifting the annoyance from one set of people
  (which includes John) to another set (which includes me)."

So no, it won't be changing. 

Dan.
-- 
|=- Red Hat, Engineering, Emerging Technologies, Boston.  +1 978 392 2496 -=|
|=-           Perl modules: http://search.cpan.org/~danberr/              -=|
|=-               Projects: http://freshmeat.net/~danielpb/               -=|
|=-  GnuPG: 7D3B9505   F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505  -=| 



From annefacq at crpp-bordeaux.cnrs.fr  Sun Jan 27 08:00:30 2008
From: annefacq at crpp-bordeaux.cnrs.fr (Anne Facq)
Date: Sun, 27 Jan 2008 09:00:30 +0100
Subject: [Fedora-xen] How to backup a Domu filesystem (on LVM) from Dom0
	on	Fedora 8 ?
In-Reply-To: <47985352.3010208@redhat.com>
References: <479516BB.7090701@crpp-bordeaux.cnrs.fr>	<47951A8E.2050400@digitalfairway.com>
	<4797CF3C.3090709@crpp-bordeaux.cnrs.fr>
	<47985352.3010208@redhat.com>
Message-ID: <479C3A1E.2000504@crpp-bordeaux.cnrs.fr>

Gerd Hoffmann wrote:
> Anne Facq wrote:
>> Because in Dom0 the device for a paravirt Domu (/dev/vg00/lvfoo in my
>> case) is mapped to a virtual disk /dev/xvda (I created the Domu with
>> virt-install), and the only way I found to mount this Domu filesystem,
>> is to :
>> - get the size of the boot sector of /dev/vg00/lvfoo
>>     (with fdisk -ul /dev/vg00/lvfoo)
>>     = 63
>> - compute the offset (multiply by block size)
>> - specify this offset to the mount command :
>> mount -o offset=32256 /dev/vg00/lvfoo /mnt/
> 
> Uh, oh, quite complicated and error prone.  Can be done much easier.
> 
> Option (1): Use kpartx, it will create device mapper mappings for your
> partitions.  Try "kpartx -v -a /dev/vg00/lvfoo", should give you
> /dev/vg00/lvfoop[1234].  "kpartx -d ... " removes the mappings.
> 
> Option (2): (works only with xen kernel): Configure the device as
> virtual disk *in Domain-0*: "xm block-attach 0 phy:/dev/vg00/lvfoo xvda
> w".  Gives you /dev/xvda[1234].  "xm block-detach ..." removes it.

Many thanks for this solution, it helps me a lot.

If this can help someone, here are the steps to backup a Domu 
(filesystem on LVM in backend and on xvda in frontend) with the dump 
command from Dom0 (Fedora 8), using one of the 2 solutions you advised, 
kpartx :

----------------------------------------------------------------

# The DomU named "foo" must be stopped before dump
xm shutdown -w foo

# Creates device mapper mappings /dev/mapper/lvfoop[1234] for 
/dev/vg00/lvfoo
kpartx -v -a /dev/vg00/lvfoo

# Mounts temporarly the filesystem to backup
mount /dev/mapper/lvfoop1 /mnt/lvfoo/

# Launches the dump
/sbin/dump 0 -L FULL_foo -f /BACKUP-XEN/foo.colddump /mnt/lvfoo/

# Umount the filesystem
umount /mnt/lvfoo/

# Removes the mappings
kpartx -d /dev/vg00/lvfoo

# Unmount the filesystem
umount /mnt/lvfoo

# The DomU can now be restarted
xm create --config /var/lib/xend/....

----------------------------------------------------------------

Regards,

Anne Facq



From xiaoyang.liang at 163.com  Mon Jan 28 06:35:18 2008
From: xiaoyang.liang at 163.com (=?GBK?B?z/7R9A==?=)
Date: Mon, 28 Jan 2008 14:35:18 +0800 (CST)
Subject: [Fedora-xen] How can I learn to understand Xen source code
Message-ID: <19303440.384851201502118387.JavaMail.coremail@bj163app39.163.com>

 
 Hi,everyone,
I want to join the development of the Xen,but I don not understand its code.
How can I?do it?
thanks .

 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/fedora-xen/attachments/20080128/7f7dda0c/attachment.htm>

From takebe_akio at jp.fujitsu.com  Mon Jan 28 06:38:51 2008
From: takebe_akio at jp.fujitsu.com (Akio Takebe)
Date: Mon, 28 Jan 2008 15:38:51 +0900
Subject: [Fedora-xen] How can I learn to understand Xen source code
In-Reply-To: <19303440.384851201502118387.JavaMail.coremail@bj163app39.163.com>
References: <19303440.384851201502118387.JavaMail.coremail@bj163app39.163.com>
Message-ID: <82C86178723103takebe_akio@jp.fujitsu.com>

Hi,

> Hi,everyone,
>I want to join the development of the Xen,but I don not understand its code.
>How can I??do it?
>thanks .
See the below.
http://lists.xensource.com/archives/html/xen-users/2008-01/msg00580.html

Best Regards,

Akio Takebe



From Dustin.Henning at prd-inc.com  Mon Jan 28 13:09:21 2008
From: Dustin.Henning at prd-inc.com (Dustin Henning)
Date: Mon, 28 Jan 2008 08:09:21 -0500
Subject: [Fedora-xen] management of this list
In-Reply-To: <200801270836.41391.debian@herakles.homelinux.org>
References: <200801270836.41391.debian@herakles.homelinux.org>
Message-ID: <001501c861ae$ff682c00$fe388400$@Henning@prd-inc.com>

John,
	Hopefully I'm not stepping on any toes here seeing as how you have already received a management reply and apparently there was a previous discussion, but I have a couple of thoughts.  First: seeing as how your reply to can't have mail delivered to it from the outside world, I must ask if it is used for anything other than this list.  If it isn't, you could change your reply to header to fedora-xen at redhat.com and then whether someone replied to you or to all, it would only go to the group and you should get a copy.  Second: as for you missing some copies, said change, if an option, might resolve that as well.  I don't think I ever get duplicates either, and mine is set to receive duplicates as well, so that could be a bug of some sort in the list software.  Finally: regarding missing functionality in your mailer, I think all mailers have a reply to author and reply to all (albeit possibly with different names or hidden within options), but reply to all obviously includes the author, which you don't want to do.  In this scenario, I always reply to all and then delete the author from the to field, which is easier than replying and then replacing the author in the to field with fedora-xen at redhat.com.  However, I am not familiar with your clients, so I can't be certain such manipulation is possible, nor can I tell you how to do it, but it would blow me away if it were in fact impossible (though admittedly it could be cumbersome or annoying).
	Dustin

-----Original Message-----
From: fedora-xen-bounces at redhat.com [mailto:fedora-xen-bounces at redhat.com] On Behalf Of John Summerfield
Sent: Saturday, January 26, 2008 18:37
To: fedora-xen at redhat.com
Subject: [Fedora-xen] management of this list

there are some things I don't like about the way this list is implemented, the 
key one being that it's set to default to sending replies off-list.

My preferred email clients (Thunderbird and Seamonkey) do not have any means 
of sending replies only to the list, so I find myself sometimes sending 
replies I intend for the list, off-list.

Worse, I miss replies to some of my queries; I've seen replies in the archives 
that haven't made it to me.

I have visited https://www.redhat.com/mailman/options/fedora-xen and 
turned "Avoid duplicate copies of messages" off, but still miss replies.

The whole issue would be solved, both for incoming and outgoing email, if the 
default list behaviour was changed to send replies to the list; this is 
appropriate for a discussion such as this.

Please, Could this be done?
-- 

John Summerfield

--
Fedora-xen mailing list
Fedora-xen at redhat.com
https://www.redhat.com/mailman/listinfo/fedora-xen





From accarlson at gmail.com  Mon Jan 28 16:10:05 2008
From: accarlson at gmail.com (Augusto Castelan Carlson)
Date: Mon, 28 Jan 2008 14:10:05 -0200
Subject: [Fedora-xen] problem installing 64 bit domU
Message-ID: <dee2b60c0801280810x16c7e250nd588255b1175db4a@mail.gmail.com>

Hello!

I have Fedora Unity 8 (20071218) x86_64 running in an Athlon 64 (512
RAM) with xen. I'm using the re-spin version because I need kickstart
install to be done from CD/DVD. I'm using this machine with small RAM
for tests only.

When I try to install the domU using virt-manager, it hangs when I
click the first next button after anaconda installer started. The
button stays pressed an nothing happens.

When I try to install the domU using virt-install, it gives a black
screen after starting anaconda installer.
# virt-install -n myguest -r 256 --vnc -l ftp://10.1.121.201/ -x
ks=ftp://10.1.121.201/guest.cfg -f /dev/vgadm/lvadm1

The ftp server is the dom0

xen-libs-3.1.0-13.fc8
kernel-xen-2.6.21-2952.fc8
xen-3.1.0-13.fc8
libvirt-0.3.3-2.fc8
virt-manager-0.5.2-2.fc8
virt-viewer-0.0.2-2.fc8

With Fedora Unitity 8 for i386 everything goes fine.

Thanks in advance,

Regards,
Augusto



From accarlson at gmail.com  Mon Jan 28 16:35:37 2008
From: accarlson at gmail.com (Augusto Castelan Carlson)
Date: Mon, 28 Jan 2008 14:35:37 -0200
Subject: [Fedora-xen] Re: problem installing 64 bit domU
In-Reply-To: <dee2b60c0801280810x16c7e250nd588255b1175db4a@mail.gmail.com>
References: <dee2b60c0801280810x16c7e250nd588255b1175db4a@mail.gmail.com>
Message-ID: <dee2b60c0801280835g768b133crbc8787057d30ff4a@mail.gmail.com>

Some corrections about my problem:

> When I try to install the domU using virt-manager, it hangs when I
> click the first next button after anaconda installer started. The
> button stays pressed an nothing happens.

When I install without kickstart it hangs in the "next" button,
independent of using virt-manager or virt-install.

> When I try to install the domU using virt-install, it gives a black
> screen after starting anaconda installer.

The black screen happens when I use kickstart.

Regards,

Augusto



From debian at herakles.homelinux.org  Tue Jan 29 02:30:24 2008
From: debian at herakles.homelinux.org (John Summerfield)
Date: Tue, 29 Jan 2008 11:30:24 +0900
Subject: [Fedora-xen] management of this list
In-Reply-To: <001501c861ae$ff682c00$fe388400$@Henning@prd-inc.com>
References: <200801270836.41391.debian@herakles.homelinux.org>
	<001501c861ae$ff682c00$fe388400$@Henning@prd-inc.com>
Message-ID: <479E8FC0.7090102@herakles.homelinux.org>

Dustin Henning wrote:
> John,
> 	Hopefully I'm not stepping on any toes here seeing as how you have already received a management reply and apparently there was a previous discussion, but I have a couple of thoughts.  First: seeing as how your reply to can't have mail delivered to it from the outside world, I must ask if it is used for anything other than this list.  If it isn't, you could change your reply to header to fedora-xen at redhat.com and then whether someone replied to you or to all, it would only go to the group and you should get a copy.  Second: as for you missing some copies, said change, if an option, might resolve that as well.  I don't think I ever get duplicates either, and mine is set to receive duplicates as well, so that could be a bug of some sort in the list software.  Finally: regarding missing functionality in your mailer, I think all mailers have a reply to author and reply to all (albeit possibly with different names or hidden within options), but reply to all obviously includes t
he
>   author, which you don't want to do.  In this scenario, I always reply to all and then delete the author from the to field, which is easier than replying and then replacing the author in the to field with fedora-xen at redhat.com.  However, I am not familiar with your clients, so I can't be certain such manipulation is possible, nor can I tell you how to do it, but it would blow me away if it were in fact impossible (though admittedly it could be cumbersome or annoying).
>

I use this email address for several lists.

I do use reply-to-all then edit, but it's tedious and error-prone.

-- 

Cheers
John

-- spambait
1aaaaaaa at coco.merseine.nu  Z1aaaaaaa at coco.merseine.nu
-- Advice
http://webfoot.com/advice/email.top.php
http://www.catb.org/~esr/faqs/smart-questions.html
http://support.microsoft.com/kb/555375

You cannot reply off-list:-)



From debian at herakles.homelinux.org  Tue Jan 29 03:18:00 2008
From: debian at herakles.homelinux.org (John Summerfield)
Date: Tue, 29 Jan 2008 12:18:00 +0900
Subject: [Fedora-xen] management of this list
In-Reply-To: <20080127022437.GA1762@redhat.com>
References: <200801270836.41391.debian@herakles.homelinux.org>
	<20080127022437.GA1762@redhat.com>
Message-ID: <479E9AE8.2030705@herakles.homelinux.org>

Daniel P. Berrange wrote:

> I'm not going to get into this discussion again, other than to refer
> you to the previous thread
> 
>   http://www.redhat.com/archives/fedora-xen/2007-May/msg00021.html

That's one reply I did not see. I have seen the article it links to, and 
I don't agree with some of its basic assumptions.

> 
> To quote Markus
> 
>  "This just replaces one set of problems with a different set of
>   arguably worse problems, shifting the annoyance from one set of people
>   (which includes John) to another set (which includes me)."
> 
> So no, it won't be changing. 

If all email clients shipped by RH and Fedora were "reasonable mailers" 
as assumed by Chip, I really wouldn't care so much.

I could almost cope if the version of mailman Red Hat's using would 
gaily send me so-called duplicates, but it won't. I've checked my 
configuration.

Whatever _I_ do, I miss replies others make. If you, Dan, choose "group 
reply" or "reply to all,"[1] I often don't get it. I've never seen value 
in off-list replies, except for very rare cases where, maybe 
highlighting someone's ignorance might embarrass them, but they need to 
be put straight.

I for one would be happy if my email address never went to email lists; 
the fact it does is the reason I need to apply antispam to this domain.


[1] I don't see the point of those wrt _this_ list. Mutt users might try 
L to reply to the list.

-- 

Cheers
John

-- spambait
1aaaaaaa at coco.merseine.nu  Z1aaaaaaa at coco.merseine.nu
-- Advice
http://webfoot.com/advice/email.top.php
http://www.catb.org/~esr/faqs/smart-questions.html
http://support.microsoft.com/kb/555375

You cannot reply off-list:-)



From debian at herakles.homelinux.org  Tue Jan 29 03:25:43 2008
From: debian at herakles.homelinux.org (John Summerfield)
Date: Tue, 29 Jan 2008 12:25:43 +0900
Subject: [Fedora-xen] How can I learn to understand Xen source code
In-Reply-To: <82C86178723103takebe_akio@jp.fujitsu.com>
References: <19303440.384851201502118387.JavaMail.coremail@bj163app39.163.com>
	<82C86178723103takebe_akio@jp.fujitsu.com>
Message-ID: <479E9CB7.3080405@herakles.homelinux.org>

Akio Takebe wrote:
> Hi,
> 
>> Hi,everyone,
>> I want to join the development of the Xen,but I don not understand its code.
>> How can I。。do it?
>> thanks .
> See the below.
> http://lists.xensource.com/archives/html/xen-users/2008-01/msg00580.html

and find a problem, something that doesn't work to your satisfaction, or 
a reported bug. Examine the code to find a likely place to hack on to 
cure the ill, create a patch.

Join an upstream list, ask for help, maybe ask for a mentor, ask for 
comments on your patch.


Don't expect to understand all of xen before you do something, but 
there's bound to be little bits that you can attack and learn.



-- 

Cheers
John

-- spambait
1aaaaaaa at coco.merseine.nu  Z1aaaaaaa at coco.merseine.nu
-- Advice
http://webfoot.com/advice/email.top.php
http://www.catb.org/~esr/faqs/smart-questions.html
http://support.microsoft.com/kb/555375

You cannot reply off-list:-)



From armbru at redhat.com  Tue Jan 29 08:07:09 2008
From: armbru at redhat.com (Markus Armbruster)
Date: Tue, 29 Jan 2008 09:07:09 +0100
Subject: [Fedora-xen] management of this list
In-Reply-To: <479E9AE8.2030705@herakles.homelinux.org> (John Summerfield's
	message of "Tue\, 29 Jan 2008 12\:18\:00 +0900")
References: <200801270836.41391.debian@herakles.homelinux.org>
	<20080127022437.GA1762@redhat.com>
	<479E9AE8.2030705@herakles.homelinux.org>
Message-ID: <87zlupukb6.fsf@pike.pond.sub.org>

John Summerfield <debian at herakles.homelinux.org> writes:

> Daniel P. Berrange wrote:
>
>> I'm not going to get into this discussion again, other than to refer
>> you to the previous thread
>>
>>   http://www.redhat.com/archives/fedora-xen/2007-May/msg00021.html
>
> That's one reply I did not see. I have seen the article it links to,
> and I don't agree with some of its basic assumptions.

This tired topic has been discussed to death many times over on many
lists, including this one.  I wouldn't expect agreement to jump at us
out of the bushes now.

>> To quote Markus
>>
>>  "This just replaces one set of problems with a different set of
>>   arguably worse problems, shifting the annoyance from one set of people
>>   (which includes John) to another set (which includes me)."
>>
>> So no, it won't be changing. 
>
> If all email clients shipped by RH and Fedora were "reasonable
> mailers" as assumed by Chip, I really wouldn't care so much.
>
> I could almost cope if the version of mailman Red Hat's using would
> gaily send me so-called duplicates, but it won't. I've checked my
> configuration.
>
> Whatever _I_ do, I miss replies others make. If you, Dan, choose
> "group reply" or "reply to all,"[1] I often don't get it. I've never
> seen value in off-list replies, except for very rare cases where,
> maybe highlighting someone's ignorance might embarrass them, but they
> need to be put straight.

I don't understand how you miss replies *often*.  Can you identify the
conditions that make you miss a reply?  If you can, we might be able
to help you fix that.

> I for one would be happy if my email address never went to email
> lists; the fact it does is the reason I need to apply antispam to this
> domain.

Tough.

> [1] I don't see the point of those wrt _this_ list. Mutt users might
> try L to reply to the list.
[...]
> You cannot reply off-list:-)

I consider that bad manners.  Discussion of manners, however, is quite
off-topic on this list.  Feel free to reply to me personally.



From sa212+fcxen at cyconix.com  Tue Jan 29 09:42:37 2008
From: sa212+fcxen at cyconix.com (Evan Lavelle)
Date: Tue, 29 Jan 2008 09:42:37 +0000
Subject: [Fedora-xen] management of this list
In-Reply-To: <479E9AE8.2030705@herakles.homelinux.org>
References: <200801270836.41391.debian@herakles.homelinux.org>	<20080127022437.GA1762@redhat.com>
	<479E9AE8.2030705@herakles.homelinux.org>
Message-ID: <479EF50D.7000401@cyconix.com>

This eventually comes up on most of the mailing lists I'm on (lots of 
them). I was as surprised as you were on finding out that some lists 
were set to reply to sender. Some people like it that way; your only 
choice is to live with it. Always 'reply all', edit the fields, delete 
duplicates, find something else to worry about. I'm not aware that I've 
ever missed a duplicate, though; I don't understand that issue.

John Summerfield wrote:

> I for one would be happy if my email address never went to email lists; 
> the fact it does is the reason I need to apply antispam to this domain.

All the spam I've got over the last few years (a lot) has come from 
address harvesting of mailman lists. There's only one answer, which is 
never to use an important mail address on a mailing list. I use a free 
(exim plussed) address. You get a base name, and can put whatever you 
want on the end of it, with a '+' in between. You create a new address 
for each list, and throw away the address if you get spam on it. The 
only hassle is that Thunderbird makes it difficult to edit the sender 
address in an outgoing mail, so you need to set up a new identity for 
each list. Thunderbird also has problems selecting the correct identity 
when replying to a list message, so you frequently have to manually 
select the correct 'from' address from all your identities.

- Evan



From rjones at redhat.com  Tue Jan 29 11:49:39 2008
From: rjones at redhat.com (Richard W.M. Jones)
Date: Tue, 29 Jan 2008 11:49:39 +0000
Subject: [Fedora-xen] How to change resolution above 1024x768 in guess OS?
In-Reply-To: <b9e7857a0801211259j6d82a433s75acb98e622308d6@mail.gmail.com>
References: <b9e7857a0801211259j6d82a433s75acb98e622308d6@mail.gmail.com>
Message-ID: <479F12D3.3070209@redhat.com>

Mark Hutchinson wrote:
> 1600x1200 for real-estate on the monitor. I am using Virt-manager and 
> getting the screen for there.  If I crank up the resolution in my guest, 
> it seems to stop at 10x24x768(24 bit color )
> This is using VNC to connect right?  Is there a config for that to set 
> connection resolution size?
> The client is seen to have a cirrus logic video card with 8 Megs of RAM.

You can't do it -- the problem is a limitation in the emulated Cirrus 
Logic graphics card.  I think the max you'll ever get is 1280x1024 in 16 
colours:

http://fabrice.bellard.free.fr/qemu/qemu-doc.html#SEC50

As another reply suggested, you could try running a headless X server + 
a VNC server inside the guest.  Or simpler is just to 'ssh -Y ...' into 
the guest and run X programs directly, assuming the guest is running 
some sort of Un*x.

Rich.

-- 
Emerging Technologies, Red Hat - http://et.redhat.com/~rjones/
Registered Address: Red Hat UK Ltd, Amberley Place, 107-111 Peascod
Street, Windsor, Berkshire, SL4 1TE, United Kingdom.  Registered in
England and Wales under Company Registration No. 03798903
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 3237 bytes
Desc: S/MIME Cryptographic Signature
URL: <http://listman.redhat.com/archives/fedora-xen/attachments/20080129/d14641d3/attachment.bin>

From debian at herakles.homelinux.org  Tue Jan 29 23:42:48 2008
From: debian at herakles.homelinux.org (John Summerfield)
Date: Wed, 30 Jan 2008 08:42:48 +0900
Subject: [Fedora-xen] Re: problem installing 64 bit domU
In-Reply-To: <dee2b60c0801280835g768b133crbc8787057d30ff4a@mail.gmail.com>
References: <dee2b60c0801280810x16c7e250nd588255b1175db4a@mail.gmail.com>
	<dee2b60c0801280835g768b133crbc8787057d30ff4a@mail.gmail.com>
Message-ID: <479FB9F8.7090901@herakles.homelinux.org>

Augusto Castelan Carlson wrote:
> Some corrections about my problem:
> 
>> When I try to install the domU using virt-manager, it hangs when I
>> click the first next button after anaconda installer started. The
>> button stays pressed an nothing happens.
> 
> When I install without kickstart it hangs in the "next" button,
> independent of using virt-manager or virt-install.
> 
>> When I try to install the domU using virt-install, it gives a black
>> screen after starting anaconda installer.


You really do not have enough RAM; I think the minimum for F8 is 512 Mbytes.

Since xen and KVM both require real RAM, and since F8 generally doesn't 
perform all that well in 512 Mbytes I suggest you add a bit.

My F8 test box has 2 Gbytes, and I'm contemplating removing half that 
and adding a pair of 2 Gbyte sticks.


-- 

Cheers
John

-- spambait
1aaaaaaa at coco.merseine.nu  Z1aaaaaaa at coco.merseine.nu
-- Advice
http://webfoot.com/advice/email.top.php
http://www.catb.org/~esr/faqs/smart-questions.html
http://support.microsoft.com/kb/555375

You cannot reply off-list:-)



From debian at herakles.homelinux.org  Tue Jan 29 23:37:47 2008
From: debian at herakles.homelinux.org (John Summerfield)
Date: Wed, 30 Jan 2008 08:37:47 +0900
Subject: [Fedora-xen] management of this list
In-Reply-To: <479EF50D.7000401@cyconix.com>
References: <200801270836.41391.debian@herakles.homelinux.org>	<20080127022437.GA1762@redhat.com>	<479E9AE8.2030705@herakles.homelinux.org>
	<479EF50D.7000401@cyconix.com>
Message-ID: <479FB8CB.1000708@herakles.homelinux.org>

Evan Lavelle wrote:
> This eventually comes up on most of the mailing lists I'm on (lots of 
> them). I was as surprised as you were on finding out that some lists 
> were set to reply to sender. Some people like it that way; your only 
> choice is to live with it. Always 'reply all', edit the fields, delete 
> duplicates, find something else to worry about. I'm not aware that I've 
> ever missed a duplicate, though; I don't understand that issue.

Since I tend not to get the help I need, I think I won't be around much 
longer.

> 
> John Summerfield wrote:
> 
>> I for one would be happy if my email address never went to email 
>> lists; the fact it does is the reason I need to apply antispam to this 
>> domain.
> 
> All the spam I've got over the last few years (a lot) has come from 
> address harvesting of mailman lists. There's only one answer, which is 
> never to use an important mail address on a mailing list. I use a free 
> (exim plussed) address. You get a base name, and can put whatever you 
> want on the end of it, with a '+' in between. You create a new address 
> for each list, and throw away the address if you get spam on it. The 
> only hassle is that Thunderbird makes it difficult to edit the sender 
> address in an outgoing mail, so you need to set up a new identity for 
> each list. Thunderbird also has problems selecting the correct identity 
> when replying to a list message, so you frequently have to manually 
> select the correct 'from' address from all your identities.

I have a free domain; traffic from a few servers[1] world wide goes 
directly to an internal server that handles it.

I've gone from getting lots of spam to getting none, for that domain. 
I'm not about to undo that antispam measure. It beats block lists, 
header checking and so on hands down.

[1] It does mean that email from those servers can't reach my regular server

-- 

Cheers
John

-- spambait
1aaaaaaa at coco.merseine.nu  Z1aaaaaaa at coco.merseine.nu
-- Advice
http://webfoot.com/advice/email.top.php
http://www.catb.org/~esr/faqs/smart-questions.html
http://support.microsoft.com/kb/555375

You cannot reply off-list:-)



From robin-lists at robinbowes.com  Thu Jan 31 01:11:00 2008
From: robin-lists at robinbowes.com (Robin Bowes)
Date: Thu, 31 Jan 2008 01:11:00 +0000
Subject: [Fedora-xen] Xen 3.2 on CentOS 5.1
Message-ID: <fnr72n$jb1$1@ger.gmane.org>

Hi,

I'm about to commission a new dom0 host to host multiple dom0 instances 
for testing purposes. I'm currently trying to decide what platform to 
use. I've previously used FC6 and CentOS5 as Dom0 hosts.

I'd like to be able to use Xen 3.2, and I see RPMS are available from 
xen.org for CentOS5.

My current questions:

Do I need to do anything other than install the xen 3.2 RPMS on my 
CentOS 5.1 system? i.e. Do I need to build a new initrd or anything, or 
does the xen RPM install take care of that?

Do I continue to use the CentOS kernel-xen?

Will tools like virt-install work the same with xen 3.2 as with xen 3.1?

Are any other distros more suitable for use with xen 3.2? I prefer 
Redhat/CentOS/Fedora flavours as that's what I'm most comfortable with, 
but I'm not averse to try something else if it is more appropriate.

Thanks for any responses, advice, suggestions, pointers to FAQs, etc.

R.



From robin-lists at robinbowes.com  Thu Jan 31 13:02:20 2008
From: robin-lists at robinbowes.com (Robin Bowes)
Date: Thu, 31 Jan 2008 13:02:20 +0000
Subject: [Fedora-xen] Re: Xen 3.2 on CentOS 5.1
In-Reply-To: <fnr72n$jb1$1@ger.gmane.org>
References: <fnr72n$jb1$1@ger.gmane.org>
Message-ID: <fnsgo9$7ra$1@ger.gmane.org>

Robin Bowes wrote:
> 
> I'd like to be able to use Xen 3.2, and I see RPMS are available from 
> xen.org for CentOS5.

Uh, just noticed: only i386 RPMS available for xen 3.2, plus the src rpm.

Is this just becaise of lack of build platforms, etc? Or does it not 
build on x86_64 ?

Thanks,

R.



From wrb at u.washington.edu  Wed Jan 30 22:41:45 2008
From: wrb at u.washington.edu (William R. Barker)
Date: Wed, 30 Jan 2008 14:41:45 -0800 (Pacific Standard Time)
Subject: [Fedora-xen] Red Hat 5.1, Xen and virt-manager crashes
Message-ID: <alpine.WNT.1.00.0801301130280.2652@purvis>


I've been testing Red Hat 5.1's vm stuff for a couple of weeks and was 
quite happy with the results so far.  But I've run into a bit of an issue 
that I hope someone out there can help me solve.

Since late last week, after a "yum upgrade" that included the newest 
kernel (2.6.18-53.1.6.el5xen), virt-manager dies when started from either 
the command line or from the desktop with a segmentation fault.

/var/log/messages gets the following:
kernel: /usr/share/virt[4369] general protection rip:3b4f8401fa 
rsp:7fff40efad50 error:0

Nothing is written to /var/log/xen/xend.log.

Nothing is written to ~/.virt-manager/virt-manager.log, although it is 
touched.

Returning to the old kernel doesn't help.

The command line utils (xm, virsh, etc) are working fine.

Removing and then reinstalling virt-manager doesn't resolve anything.

The vm's are working fine.

Has anyone else seen (and more importantly, resolved) this 
issue?

A few system specs:

New kernel 2.6.18-53.1.6.el5xen
Old kernel 2.6.18-53.1.4.el5xen
virt-manager.x86_64 0.4.0-3.el5

TIA,

bb
------
William R. Barker
Computer Systems & Networks Administrator
Department of Biological Structure
University of Washington School of Medicine
(206) 543-7315