Xen project Mailing List

On Sat, Aug 4, 2012 at 2:00 PM, <xen-users-request@xxxxxxxxxxxxx> wrote:

Send Xen-users mailing list submissions to
xen-users@xxxxxxxxxxxxx

To subscribe or unsubscribe via the World Wide Web, visit
http://lists.xen.org/cgi-bin/mailman/listinfo/xen-users
or, via email, send a message with subject or body 'help' to
xen-users-request@xxxxxxxxxxxxx

You can reach the person managing the list at
xen-users-owner@xxxxxxxxxxxxx

When replying, please edit your Subject line so it is more specific
than "Re: Contents of Xen-users digest..."

Today's Topics:

1. Re: any opensource controllers to recommand? (David Erickson)
2. Re: settinjg dom0 memory, where did I go wrong?
(Alexandre Kouznetsov)
3. Re: settinjg dom0 memory, where did I go wrong?
(Michael Egglestone)
4. Re: settinjg dom0 memory, where did I go wrong?
(Alexandre Kouznetsov)
5. Re: xm console command doesn't work (Jos? Eduardo Fran?a)
6. Re: xm console command doesn't work (Ian Tobin)
7. How can I boot using pv-grub? (Joe Julian)
8. Re: [Xen-devel] PCI passthrough for domU allocated with more
than 4G memory (Konrad Rzeszutek Wilk)

----------------------------------------------------------------------

Message: 1
Date: Fri, 3 Aug 2012 08:51:32 -0700
From: David Erickson <halcyon1981@xxxxxxxxx>
To: Jonathon Royle <jonathon@xxxxxxxxxxxxxxxx>
Cc: yue wang <heuye.wang@xxxxxxxxx>, Joseph Glanville
<joseph.glanville@xxxxxxxxxxxxxx>, "xen-users@xxxxxxxxxxxxx"
<xen-users@xxxxxxxxxxxxx>
Subject: Re: [Xen-users] any opensource controllers to recommand?
Message-ID:
<CANKx4w-7gyMuWNC9dXgS0bPu68F94E=SmNxQTvGEw9ObnXknUQ@xxxxxxxxxxxxxx>
Content-Type: text/plain; charset="utf-8"

Hi Jon-
There are 'binaries' available, see
https://openflow.stanford.edu/display/Beacon/Releases
I encourage you to make sure you are running the latest Oracle JDK/JRE 6
release. If you have any questions feel free to post on the forum:
https://openflow.stanford.edu/forums/forum/4-beacon-general/

-David

On Fri, Aug 3, 2012 at 5:31 AM, Jonathon Royle <jonathon@xxxxxxxxxxxxxxxx>wrote:

> I have also been looking for a good opensource controller so I was
> interested in this thread. Is there a binary version for Centos 5/6
> available. The link I followed just provided source code and instructions
> for building within the eclipse IDE.****
>
> ** **
>
> Thanks,****
>
> ** **
>
> Jon****
>
> ** **
>
> ** **
>
> *From:* Joseph Glanville [mailto:joseph.glanville@xxxxxxxxxxxxxx]
> *Sent:* 03 August 2012 01:08
> *To:* David Erickson
> *Cc:* yue wang; xen-users@xxxxxxxxxxxxx
> *Subject:* Re: [Xen-users] any opensource controllers to recommand?****
>
> ** **
>
> ** **
>
> On 2 August 2012 10:39, David Erickson <halcyon1981@xxxxxxxxx> wrote:****
>
> I am biased as the author of Beacon (http://www.beaconcontroller.net/),
> but I have been using it with a cluster of 80 XenServer machines running
> OVS, interconnected by physical OpenFlow switches for over a year.****
>
> ** **
>
> I'll second Beacon as a good choice. Great performance and probably the
> most featureful of the open-source controllers.****
>
> ** **
>
> If you want to get hacking on stuff really fast then there is NOX which
> though not as tanky as Beacon lets you write extensions in Python, which is
> imo a big plus.****
>
> ** **
>
> There is also this project which I am yet to try out but it looks
> interesting:****
>
> ** **
>
> https://github.com/trema****
>
> ** **
>
> It seems to be the remnants of the NEC Helios controller. (which to my
> knowledge was never available anywhere).****
>
> ****
>
> ** **
>
> On Tue, Jul 31, 2012 at 7:57 PM, yue wang <heuye.wang@xxxxxxxxx> wrote:***
> *
>
> Hi, All****
>
> ** **
>
> do you have any opensource controllers to recommand?****
>
> since XCP don't have a controller to control OVS centrally,i need a
> controller like vswitch controller for xenserver.****
>
> there are so many open source openflow controller, i really don't know
> which one to choose.****
>
> ** **
>
> thanks in advance****
>
> ** **
>
> _______________________________________________
> Xen-users mailing list
> Xen-users@xxxxxxxxxxxxx
> http://lists.xen.org/xen-users****
>
>
>
> _______________________________________________
> Xen-users mailing list
> Xen-users@xxxxxxxxxxxxx
> http://lists.xen.org/xen-users****
>
>
>
> ****
>
> ** **
>
> --
> CTO | Orion Virtualisation Solutions | www.orionvm.com.au
> Phone: 1300 56 99 52 | Mobile: 0428 754 846****
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.xen.org/archives/html/xen-users/attachments/20120803/03d6a681/attachment.html>

------------------------------

Message: 2
Date: Fri, 03 Aug 2012 11:02:09 -0500
From: Alexandre Kouznetsov <alk@xxxxxxxxxx>
To: xen-users@xxxxxxxxxxxxx
Subject: Re: [Xen-users] settinjg dom0 memory, where did I go wrong?
Message-ID: <501BF601.7090306@xxxxxxxxxx>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed

Hello.

El 02/08/12 23:48, Michael Egglestone escribi?:
> Here is my /etc/default/grub
>
> /GRUB_CMDLINE_XEN_DEFAULT="dom0_mem=4096M dom0_vcpus_pin"/
> [...]
> I've updated grub to populate /boot/grub/grub.cfg and then rebooted.
This two stepas are the only relevant ones to achieve the Dom0 memory
restriction.

While booting, you should have interacted with Grub, checking if the
parameter dom0_mem is really present in the right place. There you would
probably find that it is not.

The variable used to set Dom0 memory is slightly different:
GRUB_CMDLINE_XEN="dom0_mem=4032"

Piece of advice: don't set dom0_mem as "round" n*2^10. Subtract at least
64MB from it. Hypervisor itself need some RAM, some bit less than 64MB
in Xen 4.0 case.

So, after you assign, let's say, 4032MB to Dom0 and another 64MB was
eaten by hypervisor, you may consider you have "(your total RAM) - 4GB"
free, available for DomU's, round 28GB in your case. Otherwise, you
would have available "(your total RAM) - 4GB - (little more piece)",
which will left with a "not round" amount of available RAM, near 27.94
GB in your case.

This is far from being mandatory, but brings simplicity to estimations
and some bit of esthetics.

--
Alexandre Kouznetsov

------------------------------

Message: 3
Date: Fri, 03 Aug 2012 10:40:07 -0700
From: "Michael Egglestone" <mike@xxxxxxxxx>
To: xen-users@xxxxxxxxxxxxx
Subject: Re: [Xen-users] settinjg dom0 memory, where did I go wrong?
Message-ID: <fc.00000001e6690c5000000001e6690c0f.e6690c53@xxxxxxxxx>
Content-Type: text/plain; charset="utf-8"

Alexandre Kouznetsov <alk@xxxxxxxxxx> writes:
#El 02/08/12 23:48, Michael Egglestone escribi?:
#> Here is my /etc/default/grub
#>
#> /GRUB_CMDLINE_XEN_DEFAULT="dom0_mem=4096M dom0_vcpus_pin"/
#> [...]
#> I've updated grub to populate /boot/grub/grub.cfg and then rebooted.
#This two stepas are the only relevant ones to achieve the Dom0 memory
#restriction.
#
#While booting, you should have interacted with Grub, checking if the
#parameter dom0_mem is really present in the right place. There you would
#probably find that it is not.
#
#The variable used to set Dom0 memory is slightly different:
#GRUB_CMDLINE_XEN="dom0_mem=4032"

It appears my system could fall into this link:

http://blog.xen.org/index.php/2012/04/30/do%EF%BB%BFm0-memory-where-it-has-not-gone/

If I set my system to around 2G or lower, it appears correct, but if I start going above 2G, even
up into the teens of Gigabytes, I see lost RAM.
So, until Wheezy becomes stable, I'll stick with Dom0 at 2G.
Thanks!

Cheers,
Mike

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.xen.org/archives/html/xen-users/attachments/20120803/0bd44d94/attachment.html>

------------------------------

Message: 4
Date: Fri, 03 Aug 2012 15:36:42 -0500
From: Alexandre Kouznetsov <alk@xxxxxxxxxx>
To: xen-users@xxxxxxxxxxxxx
Subject: Re: [Xen-users] settinjg dom0 memory, where did I go wrong?
Message-ID: <501C365A.1060102@xxxxxxxxxx>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed

Hi.

El 03/08/12 12:40, Michael Egglestone escribi?:
> It appears my system could fall into this link:
>
> http://blog.xen.org/index.php/2012/04/30/do%EF%BB%BFm0-memory-where-it-has-not-gone/

Silly me, I have not payed enough attention to the description of the
problem you made, sorry.

That's new for me that GRUB_CMDLINE_XEN_DEFAULT and GRUB_CMDLINE_XEN
turned to be synonyms. Checked the scripts, they are.

--
Alexandre Kouznetsov

------------------------------

Message: 5
Date: Fri, 3 Aug 2012 17:41:13 -0300
From: Jos? Eduardo Fran?a <jefranca@xxxxxxxxx>
To: Stephan Seitz <s.seitz@xxxxxxxxxxx>
Cc: "xen-users@xxxxxxxxxxxxx" <xen-users@xxxxxxxxxxxxx>, Ian Tobin
<itobin@xxxxxxxxxxxxx>, Ian Campbell <Ian.Campbell@xxxxxxxxxx>, Lukas
Laukamp <lukas@xxxxxxxxxx>
Subject: Re: [Xen-users] xm console command doesn't work
Message-ID:
<CAJP76_DU=soSwZG4cHbRvKagjQSet3CMebz5t8w04L9eOUQEag@xxxxxxxxxxxxxx>
Content-Type: text/plain; charset="iso-8859-1"

Hi all,

I can't still resolve.
How Ian Campbell said the xl console command didn't work.

Well... I tried the script /etc/init/hvc0.conf that Lukas suggested and my
guest.cfg was changed to:
name = "ubuntu-pv"

memory = 256
disk = ['phy:/dev/labprog/ubuntu-pv,xvda,w']
vif = [' ']

bootloader = "pygrub"
*extra = "console=hvc0"*

But, I can't run xm console command. Is there other idea?
Thanks

2012/8/2 Stephan Seitz <s.seitz@xxxxxxxxxxx>

> **
>
>
> Am Donnerstag, den 02.08.2012, 08:16 +0100 schrieb Ian Campbell:
>
> On Wed, 2012-08-01 at 20:59 +0100, Lukas Laukamp wrote:
> >
> > he could also use the xl toolstack but the simple misstake is that the
> > hvc0.conf isn't needed in Dom0. The hvc0.conf is needed inside of the
> > DomU and in the config file must be set extra = 'console=hvc0' so that
> > the console kernel option for hvc0 is set. So the DomU can boot into a
> > hvc0 console and than xm and xl can use the console.
>
> pygrub should be getting the console=hvc0 from the grub cfg and
> hvc0.conf ought to already exist.
>
> If Ubuntu isn't setting these up by default during install when running
> under Xen then this should be reported as a bug to Ubuntu.
>
> I'm not familiar with current Ubuntu so I don't know if these are
> expected to be there i.e. I don't know if this is a wishlist/new-feature
> bug or just a bug in functionality which is expected to Just Work
> already.
>
> Ian.
>
>
> Current (12.04 LTS) Ubuntu, respectively the 3.2.0 linux-virtual Kernel
> as well as the grub-legacy-ec2 are
> aware of hvc0.
>
> I think the source of these console problems are the configurable
> different presets. One could use tty0
> as well as tty1, maybe hvc0 or xvc0 or both of them. The domU I'm
> currently peeking into spawns tty0
> and hvc0 with tty0 connected to the "serial" xl console and hvc0 connected
> to vfb/vnc setting. But that
> can't be predicted, it's easy to configure it the opposite way.
>
> From my point of view, the definition of virtualization namespaces (hvcN,
> xvcN, xvdMN) jumped in far to late.
> There have been huge clusters build before one was even thinking about
> hvc0.
>
> Just my 2 cents, and I'm sorry that this won't help the OP to solve his
> issue easily.
>
> Cheers,
>
> Stephan
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.xen.org/archives/html/xen-users/attachments/20120803/007ebc81/attachment.html>

------------------------------

Message: 6
Date: Fri, 3 Aug 2012 22:34:34 +0100
From: "Ian Tobin" <itobin@xxxxxxxxxxxxx>
To: Jos? Eduardo Fran?a <jefranca@xxxxxxxxx>, "Stephan Seitz"
<s.seitz@xxxxxxxxxxx>
Cc: xen-users@xxxxxxxxxxxxx, Ian Campbell <Ian.Campbell@xxxxxxxxxx>,
Lukas Laukamp <lukas@xxxxxxxxxx>
Subject: Re: [Xen-users] xm console command doesn't work
Message-ID:
<039E0B4AA9103344A80DA55DDDC76A936A6754@xxxxxxxxxxxxxxxxxxxxxx>
Content-Type: text/plain; charset="iso-8859-1"

Hello,

When you say it doesn't work, what isn't working, errors?

Ian

From: Jos? Eduardo Fran?a [mailto:jefranca@xxxxxxxxx]
Sent: 03 August 2012 21:41
To: Stephan Seitz
Cc: Ian Campbell; Lukas Laukamp; xen-users@xxxxxxxxxxxxx; Ian Tobin
Subject: Re: [Xen-users] xm console command doesn't work

Hi all,

I can't still resolve.
How Ian Campbell said the xl console command didn't work.

Well... I tried the script /etc/init/hvc0.conf that Lukas suggested and my guest.cfg was changed to:
name = "ubuntu-pv"

memory = 256
disk = ['phy:/dev/labprog/ubuntu-pv,xvda,w']

vif = [' ']

bootloader = "pygrub"
extra = "console=hvc0"

But, I can't run xm console command. Is there other idea?
Thanks

2012/8/2 Stephan Seitz <s.seitz@xxxxxxxxxxx>

Am Donnerstag, den 02.08.2012, 08:16 +0100 schrieb Ian Campbell:

On Wed, 2012-08-01 at 20:59 +0100, Lukas Laukamp wrote:
>
> he could also use the xl toolstack but the simple misstake is that the
> hvc0.conf isn't needed in Dom0. The hvc0.conf is needed inside of the
> DomU and in the config file must be set extra = 'console=hvc0' so that
> the console kernel option for hvc0 is set. So the DomU can boot into a
> hvc0 console and than xm and xl can use the console.

pygrub should be getting the console=hvc0 from the grub cfg and
hvc0.conf ought to already exist.

If Ubuntu isn't setting these up by default during install when running
under Xen then this should be reported as a bug to Ubuntu.

I'm not familiar with current Ubuntu so I don't know if these are
expected to be there i.e. I don't know if this is a wishlist/new-feature
bug or just a bug in functionality which is expected to Just Work
already.

Ian.

Current (12.04 LTS) Ubuntu, respectively the 3.2.0 linux-virtual Kernel as well as the grub-legacy-ec2 are
aware of hvc0.

I think the source of these console problems are the configurable different presets. One could use tty0
as well as tty1, maybe hvc0 or xvc0 or both of them. The domU I'm currently peeking into spawns tty0
and hvc0 with tty0 connected to the "serial" xl console and hvc0 connected to vfb/vnc setting. But that
can't be predicted, it's easy to configure it the opposite way.

>From my point of view, the definition of virtualization namespaces (hvcN, xvcN, xvdMN) jumped in far to late.
There have been huge clusters build before one was even thinking about hvc0.

Just my 2 cents, and I'm sorry that this won't help the OP to solve his issue easily.

Cheers,

Stephan

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.xen.org/archives/html/xen-users/attachments/20120803/7ac32044/attachment.html>

------------------------------

Message: 7
Date: Fri, 03 Aug 2012 18:27:00 -0700
From: Joe Julian <joe@xxxxxxxxxxxxxxxx>
To: xen-users@xxxxxxxxxxxxx
Subject: [Xen-users] How can I boot using pv-grub?
Message-ID: <501C7A64.3080101@xxxxxxxxxxxxxxxx>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed

I'm trying to figure out how to get pv-grub to work in OpenStack on
Fedora 17's xen-4.1.2 packaging. I added pv-grub-x86_64.gz from the
package as a kernel in glance (becoming
/var/lib/nova/instances/instance-0000001b/kernel in this example).
OpenStack created this vm definition:

<domain type='xen' id='21'>
<name>instance-0000001b</name>
<uuid>8a5231bc-6535-468e-8585-60a55c9073d9</uuid>
<memory unit='KiB'>2097152</memory>
<currentMemory unit='KiB'>2097152</currentMemory>
<vcpu>1</vcpu>
<bootloader></bootloader>
<os>
<type>linux</type>
<kernel>/var/lib/nova/instances/instance-0000001b/kernel</kernel>
<cmdline>root=/dev/xvda ro</cmdline>
</os>
<clock offset='utc' adjustment='reset'/>
<on_poweroff>destroy</on_poweroff>
<on_reboot>restart</on_reboot>
<on_crash>destroy</on_crash>
<devices>
<emulator>/usr/lib/xen/bin/qemu-dm</emulator>
<disk type='file' device='disk'>
<driver name='file'/>
<source file='/var/lib/nova/instances/instance-0000001b/disk'/>
<target dev='sda' bus='scsi'/>
</disk>
<disk type='file' device='disk'>
<driver name='file'/>
<source file='/var/lib/nova/instances/instance-0000001b/disk.local'/>
<target dev='sdb' bus='scsi'/>
</disk>
<interface type='bridge'>
<mac address='fa:16:3e:30:64:90'/>
<source bridge='br_private'/>
<script path='/etc/xen/scripts/vif-bridge'/>
<target dev='vif21.0'/>
</interface>
<console type='pty' tty='/dev/pts/5'>
<source path='/dev/pts/5'/>
<target type='xen' port='0'/>
</console>
<input type='mouse' bus='xen'/>
<graphics type='vnc' port='5901' autoport='yes' listen='127.0.0.1'
keymap='en-us'>
<listen type='address' address='127.0.0.1'/>
</graphics>
</devices>
</domain>

I boot to the console and see grub, but it doesn't recognize the
partition table on (hd0): "Error 5: Partition table invalid or corrupt",
nor the filesystem on (hd1): "Filesystem type unknown, using whole disk".

The files are qcow2 images with raw backing files. The first disk has
two msdos partitions, the first partition is the ext3 /boot partition
that I'm trying to use.

I also noticed that qemu-dm doesn't show either of the files open in lsof.

------------------------------

Message: 8
Date: Sat, 4 Aug 2012 07:12:29 -0400
From: Konrad Rzeszutek Wilk <konrad@xxxxxxxxxx>
To: "Fan, Huaxiang" <hufan@xxxxxxxxxxxx>
Cc: "xen-users@xxxxxxxxxxxxx" <xen-users@xxxxxxxxxxxxx>,
"xen-devel@xxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxx>, "Konrad Rzeszutek
Wilk \(konrad.wilk@xxxxxxxxxx\)" <konrad.wilk@xxxxxxxxxx>
Subject: Re: [Xen-users] [Xen-devel] PCI passthrough for domU
allocated with more than 4G memory
Message-ID: <20120804111229.GB17640@xxxxxxxxxxxxxxxxxxx>
Content-Type: text/plain; charset=us-ascii

On Wed, Aug 01, 2012 at 05:57:13AM +0000, Fan, Huaxiang wrote:
> Hi,
>
> I have encountered some strange problems when I was trying to PCI passthrough Broadcom 5709/5716 NICs to domUs allocated with more than 4G memory. Please see below for details.
>
> My environment is:
> Hardware Platform: DELL R210 with 2 Broadcom 5709 NICs and 2 Broadcom 5716 NICs
> Xen: xen 4.2 unstable (64bits for hypervisor and 32bit for tools)
> Kernel for both dom0 and domUs: xenified kernel 2.6.32.57 (32bit)
> OS: CentOS 6.2 (32bit)
>
> The general info regarding to xen can be get via below command
>
> # xl info
>
> host : 7.8
>
> release : 2.6.32.57
>
> version : #1 SMP Fri Jul 6 18:44:16 CST 2012
>
> machine : i686
>
> nr_cpus : 8
>
> max_cpu_id : 31
>
> nr_nodes : 1
>
> cores_per_socket : 4
>
> threads_per_core : 2
>
> cpu_mhz : 2660
>
> hw_caps : bfebfbff:28100800:00000000:00003b40:0098e3fd:00000000:00000001:00000000
>
> virt_caps : hvm hvm_directio
>
> total_memory : 8182
>
> free_memory : 7046
>
> sharing_freed_memory : 0
>
> sharing_used_memory : 0
>
> free_cpus : 0
>
> xen_major : 4
>
> xen_minor : 2
>
> xen_extra : -unstable
>
> xen_caps : xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32 hvm-3.0-x86_32p hvm-3.0-x86_64
>
> xen_scheduler : credit
>
> xen_pagesize : 4096
>
> platform_params : virt_start=0xff400000
>
> xen_changeset : unavailable
>
> xen_commandline : dom0_mem=1024M dom0_max_vcpus=2 dom0_vcpus_pin
>
> cc_compiler : gcc version 4.4.6 20110731 (Red Hat 4.4.6-3) (GCC)
>
> cc_compile_by : root
>
> cc_compile_domain :
>
> cc_compile_date : Thu Jul 12 11:20:56 CST 2012
>
> xend_config_format : 4
>
> case 1> I specified PV-domU config as below
>
> memory=3072
>
> maxmem=6144
>
> name="bs"
>
> vif=['ip=169.254.254.1,script=vif-nat',]
>
> disk=['file:/root/bs.img,xvda1,w']
>
> kernel='/root/vmlinuz'
>
> extra="iommu=soft console=hvc0"
>
> ramdisk='/root/initrd.img'
>
> root="/dev/xvda1 ro"
>
> pci=['01:00.0','01:00.1']
>
> and then start domU. After that I executed below command
>
> # xl list
>
> Name ID Mem VCPUs State Time(s)
>
> Domain-0 0 1024 2 r----- 88.7
>
> bs 2 3072 1 -b---- 1.1
>
> It seemed normal to me. But when I logon bs domU, and executed below command
>
> # cat /proc/meminfo | head
>
> MemTotal: 6158940 kB
>
> MemFree: 2944776 kB

So that is the right amount. It has around 3GB of free kernel space.

>
> Buffers: 5108 kB
>
> Cached: 32292 kB
>
> SwapCached: 0 kB
>
> Active: 21456 kB
>
> Inactive: 22936 kB
>
> Active(anon): 7000 kB
>
> Inactive(anon): 108 kB
>
> Active(file): 14456 kB
>
> It indicated the total memory was 6G, why?

I wish you also included the DirectMap number. Irregardless of
what /proc/meminfo says, what did your dmesg say in 'Memory' section?

> When I back to dom0, I executed below command
>
> # xl mem-set bs 6144
>
> # xl list
>
> Name ID Mem VCPUs State Time(s)
>
> Domain-0 0 1024 2 r----- 93.5
>
> bs 2 6144 1 -b---- 10.5
> It seemed normal to me. But when I logon bs domU again and executed below command
>
> # cat /proc/meminfo | head
>
> MemTotal: 9304668 kB
>
> MemFree: 6087540 kB

So that is right. 6GB of free space.
>
> Buffers: 5168 kB
>
> Cached: 32464 kB
>
> SwapCached: 0 kB
>
> Active: 22300 kB
>
> Inactive: 22408 kB
>
> Active(anon): 7080 kB
>
> Inactive(anon): 108 kB
>
> Active(file): 15220 kB
>
>
>
> It indicated total memory was 9G (6G + 3G). It was wired. Any idea about this?

Presumarily b/c '3G' of it is the E820_UNUSUABLE or the big gap in the
E820. But irregardless of that - do you have 6GB of ram in your guest?

> Case 2> I specified PV-domU config as below
>
> memory=6144
>
> maxmem=6144
>
> name="bs"
>
> vif=['ip=169.254.254.1,script=vif-nat',]
>
> disk=['file:/root/bs.img,xvda1,w']
>
> kernel='/root/vmlinuz'
>
> extra="iommu=soft console=hvc0"
>
> ramdisk='/root/initrd.img'
>
> root="/dev/xvda1 ro"
>
> pci=['01:00.0','01:00.1']
>
> and then start domU. After that I executed below command
>
> # xl list
>
> Name ID Mem VCPUs State Time(s)
>
> Domain-0 0 648 2 r----- 120.5
>
> bs 3 3360 1 -b---- 7.0
>
> the output was very confusing. Why dom0 memory had been shrank to 648M and only 3360M assigned to bs domU?

I think you are seeing a bug in the xl with the autoballoon. Smoebody
mentioned this on the xen-devel.
>
> My own analysis:
> I extracted the bios e820 memory map on bs domU as below
>
> [ 0.000000] BIOS-provided physical RAM map:
>
> [ 0.000000] Xen: 0000000000000000 - 00000000000a0000 (usable)
>
> [ 0.000000] Xen: 00000000000a0000 - 0000000000100000 (reserved)
>
> [ 0.000000] Xen: 0000000000100000 - 00000000bf699000 (usable)
>
> [ 0.000000] Xen: 00000000bf699000 - 00000000bf6af000 (reserved)
>
> [ 0.000000] Xen: 00000000bf6af000 - 00000000bf6ce000 (ACPI data)
>
> [ 0.000000] Xen: 00000000bf6ce000 - 00000000c0000000 (reserved)
>
> [ 0.000000] Xen: 00000000e0000000 - 00000000f0000000 (reserved)
>
> [ 0.000000] Xen: 00000000fe000000 - 0000000100000000 (reserved)
>
> [ 0.000000] Xen: 0000000180000000 - 00000001c33ec000 (usable)
>
> I think the root cause might be related to the holes between c0000000 and e0000000 and between f0000000 and fe000000 and between 100000000 and 180000000. And I think the e820_host option set according to my tracking.

Not sure what you mean by 'my tracking'.

The holes are there to provide the PCI subsystem the space to stick the
MMIO BARs of your PCI device. The memory that was "taken" out of those
areas is then appended to the next E820_RAM region. It should have
gone to 0x1000000, not to 0x18000000 though.

Ohh, you are using the ancient 2.6.32 domU! Well, that is ancient -
and it probably has bugs. Have you considered using something more
recent?
>
> Thanks in advance
> HUAXIANG FAN
> Software Engineer II
>
> WEBSENSE NETWORK SECURITY TECHNOLOGY R&D (BEIJING) CO. LTD.
> ph: +8610.5884.4327
> fax: +8610.5884.4727
> www.websense.cn<http://www.websense.cn>
>
> Websense TRITON(tm)
> For Essential Information Protection(tm)
> Web Security<http://www.websense.com/content/Regional/SCH/WebSecurityOverview.aspx> | Data Security<http://www.websense.com/content/Regional/SCH/DataSecurity.aspx> | Email Security<http://www.websense.com/content/Regional/SCH/MessagingSecurity.aspx>
>
>
>
> Protected by Websense Hosted Email Security -- www.websense.com

> _______________________________________________
> Xen-devel mailing list
> Xen-devel@xxxxxxxxxxxxx
> http://lists.xen.org/xen-devel

------------------------------

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxx
http://lists.xen.org/xen-users

End of Xen-users Digest, Vol 90, Issue 6
****************************************

Re: [Xen-users] Xen-users Digest, Vol 90, Issue 6