Xen users - Mar 2012 - Cannot Start Linux Paravirtualized (PV) Guests with Xen 4.2-unstable

Hi,

I cannot start Linux PV guests. "sudo xl create -c" reports that a 
domain has successfully started but "ps -ef | grep qemu" returns no 
output and "sudo xl list" doesn''t show that the PV domain has
started.

Please review the following installation steps which I have written and 
see if there are any mistakes.

*XL****Domain****Configuration****File****for****Fedora****16****x86_64****PV****domU****(Incomplete****Configuration,****Not****Tested,****Do****Not****Use)*


You will need to install apache2 and create a local http mirror.


sudo apt-get install apache2


cd /media

sudo mkdir fedora

cd ~/Downloads

sudo mount -o loop _Fedora-16-x86_64-DVD.iso 
<http://download.fedoraproject.org/pub/fedora/linux/releases/16/Fedora/x86_64/iso/Fedora-16-x86_64-DVD.iso>_
/media/fedora

cd

mkdir -p vms/f16

cd /media/fedora/images/pxeboot

cp vmlinuz initrd.img ~/vms/f16/



sudo nano /etc/xen/Fedora16x86_64


# Kernel image to boot


kernel = "/home/teo-en-ming/vms/f16/vmlinuz"




# Ramdisk (optional)


ramdisk = "/home/teo-en-ming/vms/f16/initrd.img"



#bootloader="/usr/bin/pygrub"


cd /etc/xen/images/

sudo dd if=/dev/zero of=fedora16x86_64.img bs=1024k seek=10000 count=0


To install Fedora 16 x86_64 as a paravirtualized guest domain,


sudo xl create -c Fedora16x86_64


After installing Fedora 16 x86_64 PV domU,


sudo nano /etc/xen/Fedora16x86_64


# Kernel image to boot


#kernel = "/home/teo-en-ming/vms/f16/vmlinuz"




# Ramdisk (optional)


#ramdisk = "/home/teo-en-ming/vms/f16/initrd.img"



bootloader="/usr/bin/pygrub"


# XL domain configuration file for Fedora 16 x86_64 PV domU

# Please refer to "man xl.cfg" for further explanations.

# See also docs/misc/xl-network-configuration.markdown and

# docs/misc/xl-disk-configuration.txt


# Written by Teo En Ming (Zhang Enming)

# Email: teo.en.ming@gmail.com

# Mobile Phone: +65-8369-2618

# Country: Singapore

# Date: 18 Mar 2012 Sun


name="Fedora16x86_64"


builder="generic"


vcpus=2


memory=1024


on_poweroff="destroy"

on_reboot="restart"

on_crash="destroy"


disk=[ ''format=raw, vdev=hda, access=rw, 
target=/etc/xen/images/fedora16x86_64.img'' ]


vif=[ ''bridge=virbr0'' ]


vfb=[ 
''vnc=1,vnclisten=localhost,vncdisplay=2,vncunused=1,vncpasswd=,sdl=0''
]


gfx_passthru=0


# Step 1

# To install Fedora 16 x86_64 PV domU, configure the kernel, ramdisk, 
and extra keys below and comment out bootloader.

# Kernel image to boot

kernel = "/home/teo-en-ming/vms/f16/vmlinuz"


# Ramdisk (optional)

ramdisk = "/home/teo-en-ming/vms/f16/initrd.img"


# Kernel command line options

#extra = "root=/dev/xvda1"


# Step 2

# To boot the already installed Fedora 16 x86_64 PV domU, comment out 
the keys in Step 1 and uncomment bootloader below.


#bootloader="/usr/bin/pygrub"

Please advise.

Thank you very much.

Yours sincerely,

Teo En Ming (Zhang Enming)






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

Hi,

I cannot start Linux PV guests. "sudo xl create -c" reports that a 
domain has successfully started but "ps -ef | grep qemu" returns no 
output and "sudo xl list" doesn''t show that the PV domain has
started.

Please review the following installation steps which I have written and 
see if there are any mistakes.

*XL****Domain****Configuration****File****for****Fedora****16****x86_64****PV****domU****(Incomplete****Configuration,****Not****Tested,****Do****Not****Use)*


You will need to install apache2 and create a local http mirror.


sudo apt-get install apache2


cd /media

sudo mkdir fedora

cd ~/Downloads

sudo mount -o loop _Fedora-16-x86_64-DVD.iso 
<http://download.fedoraproject.org/pub/fedora/linux/releases/16/Fedora/x86_64/iso/Fedora-16-x86_64-DVD.iso>_
/media/fedora

cd

mkdir -p vms/f16

cd /media/fedora/images/pxeboot

cp vmlinuz initrd.img ~/vms/f16/



sudo nano /etc/xen/Fedora16x86_64


# Kernel image to boot


kernel = "/home/teo-en-ming/vms/f16/vmlinuz"




# Ramdisk (optional)


ramdisk = "/home/teo-en-ming/vms/f16/initrd.img"



#bootloader="/usr/bin/pygrub"


cd /etc/xen/images/

sudo dd if=/dev/zero of=fedora16x86_64.img bs=1024k seek=10000 count=0


To install Fedora 16 x86_64 as a paravirtualized guest domain,


sudo xl create -c Fedora16x86_64


After installing Fedora 16 x86_64 PV domU,


sudo nano /etc/xen/Fedora16x86_64


# Kernel image to boot


#kernel = "/home/teo-en-ming/vms/f16/vmlinuz"




# Ramdisk (optional)


#ramdisk = "/home/teo-en-ming/vms/f16/initrd.img"



bootloader="/usr/bin/pygrub"


# XL domain configuration file for Fedora 16 x86_64 PV domU

# Please refer to "man xl.cfg" for further explanations.

# See also docs/misc/xl-network-configuration.markdown and

# docs/misc/xl-disk-configuration.txt


# Written by Teo En Ming (Zhang Enming)

# Email: teo.en.ming@gmail.com

# Mobile Phone: +65-8369-2618

# Country: Singapore

# Date: 18 Mar 2012 Sun


name="Fedora16x86_64"


builder="generic"


vcpus=2


memory=1024


on_poweroff="destroy"

on_reboot="restart"

on_crash="destroy"


disk=[ ''format=raw, vdev=hda, access=rw, 
target=/etc/xen/images/fedora16x86_64.img'' ]


vif=[ ''bridge=virbr0'' ]


vfb=[ 
''vnc=1,vnclisten=localhost,vncdisplay=2,vncunused=1,vncpasswd=,sdl=0''
]


gfx_passthru=0


# Step 1

# To install Fedora 16 x86_64 PV domU, configure the kernel, ramdisk, 
and extra keys below and comment out bootloader.

# Kernel image to boot

kernel = "/home/teo-en-ming/vms/f16/vmlinuz"


# Ramdisk (optional)

ramdisk = "/home/teo-en-ming/vms/f16/initrd.img"


# Kernel command line options

#extra = "root=/dev/xvda1"


# Step 2

# To boot the already installed Fedora 16 x86_64 PV domU, comment out 
the keys in Step 1 and uncomment bootloader below.


#bootloader="/usr/bin/pygrub"

Please advise.

Thank you very much.

Yours sincerely,

Teo En Ming (Zhang Enming)






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

Hi,

I have attached error logs. Please help.

Thank you very much.

Yours sincerely,

Teo En Ming (Zhang Enming)


On 18/03/2012 19:44, Teo En Ming (Zhang Enming) wrote:
> Hi,
>
> I cannot start Linux PV guests. "sudo xl create -c" reports that
a
> domain has successfully started but "ps -ef | grep qemu" returns
no
> output and "sudo xl list" doesn''t show that the PV
domain has started.
>
> Please review the following installation steps which I have written 
> and see if there are any mistakes.
>
>
*XL****Domain****Configuration****File****for****Fedora****16****x86_64****PV****domU****(Incomplete****Configuration,****Not****Tested,****Do****Not****Use)*
>
>
> You will need to install apache2 and create a local http mirror.
>
>
> sudo apt-get install apache2
>
>
> cd /media
>
> sudo mkdir fedora
>
> cd ~/Downloads
>
> sudo mount -o loop _Fedora-16-x86_64-DVD.iso 
>
<http://download.fedoraproject.org/pub/fedora/linux/releases/16/Fedora/x86_64/iso/Fedora-16-x86_64-DVD.iso>_
> /media/fedora
>
> cd
>
> mkdir -p vms/f16
>
> cd /media/fedora/images/pxeboot
>
> cp vmlinuz initrd.img ~/vms/f16/
>
>
>
> sudo nano /etc/xen/Fedora16x86_64
>
>
> # Kernel image to boot
>
>
> kernel = "/home/teo-en-ming/vms/f16/vmlinuz"
>
>
>
>
> # Ramdisk (optional)
>
>
> ramdisk = "/home/teo-en-ming/vms/f16/initrd.img"
>
>
>
> #bootloader="/usr/bin/pygrub"
>
>
> cd /etc/xen/images/
>
> sudo dd if=/dev/zero of=fedora16x86_64.img bs=1024k seek=10000 count=0
>
>
> To install Fedora 16 x86_64 as a paravirtualized guest domain,
>
>
> sudo xl create -c Fedora16x86_64
>
>
> After installing Fedora 16 x86_64 PV domU,
>
>
> sudo nano /etc/xen/Fedora16x86_64
>
>
> # Kernel image to boot
>
>
> #kernel = "/home/teo-en-ming/vms/f16/vmlinuz"
>
>
>
>
> # Ramdisk (optional)
>
>
> #ramdisk = "/home/teo-en-ming/vms/f16/initrd.img"
>
>
>
> bootloader="/usr/bin/pygrub"
>
>
> # XL domain configuration file for Fedora 16 x86_64 PV domU
>
> # Please refer to "man xl.cfg" for further explanations.
>
> # See also docs/misc/xl-network-configuration.markdown and
>
> # docs/misc/xl-disk-configuration.txt
>
>
> # Written by Teo En Ming (Zhang Enming)
>
> # Email: teo.en.ming@gmail.com
>
> # Mobile Phone: +65-8369-2618
>
> # Country: Singapore
>
> # Date: 18 Mar 2012 Sun
>
>
> name="Fedora16x86_64"
>
>
> builder="generic"
>
>
> vcpus=2
>
>
> memory=1024
>
>
> on_poweroff="destroy"
>
> on_reboot="restart"
>
> on_crash="destroy"
>
>
> disk=[ ''format=raw, vdev=hda, access=rw, 
> target=/etc/xen/images/fedora16x86_64.img'' ]
>
>
> vif=[ ''bridge=virbr0'' ]
>
>
> vfb=[ 
>
''vnc=1,vnclisten=localhost,vncdisplay=2,vncunused=1,vncpasswd=,sdl=0''
]
>
>
> gfx_passthru=0
>
>
> # Step 1
>
> # To install Fedora 16 x86_64 PV domU, configure the kernel, ramdisk, 
> and extra keys below and comment out bootloader.
>
> # Kernel image to boot
>
> kernel = "/home/teo-en-ming/vms/f16/vmlinuz"
>
>
> # Ramdisk (optional)
>
> ramdisk = "/home/teo-en-ming/vms/f16/initrd.img"
>
>
> # Kernel command line options
>
> #extra = "root=/dev/xvda1"
>
>
> # Step 2
>
> # To boot the already installed Fedora 16 x86_64 PV domU, comment out 
> the keys in Step 1 and uncomment bootloader below.
>
>
> #bootloader="/usr/bin/pygrub"
>
> Please advise.
>
> Thank you very much.
>
> Yours sincerely,
>
> Teo En Ming (Zhang Enming)
>
>
>
>

















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

Hi,

I have attached error logs. Please help.

Thank you very much.

Yours sincerely,

Teo En Ming (Zhang Enming)


On 18/03/2012 19:44, Teo En Ming (Zhang Enming) wrote:
> Hi,
>
> I cannot start Linux PV guests. "sudo xl create -c" reports that
a
> domain has successfully started but "ps -ef | grep qemu" returns
no
> output and "sudo xl list" doesn''t show that the PV
domain has started.
>
> Please review the following installation steps which I have written 
> and see if there are any mistakes.
>
>
*XL****Domain****Configuration****File****for****Fedora****16****x86_64****PV****domU****(Incomplete****Configuration,****Not****Tested,****Do****Not****Use)*
>
>
> You will need to install apache2 and create a local http mirror.
>
>
> sudo apt-get install apache2
>
>
> cd /media
>
> sudo mkdir fedora
>
> cd ~/Downloads
>
> sudo mount -o loop _Fedora-16-x86_64-DVD.iso 
>
<http://download.fedoraproject.org/pub/fedora/linux/releases/16/Fedora/x86_64/iso/Fedora-16-x86_64-DVD.iso>_
> /media/fedora
>
> cd
>
> mkdir -p vms/f16
>
> cd /media/fedora/images/pxeboot
>
> cp vmlinuz initrd.img ~/vms/f16/
>
>
>
> sudo nano /etc/xen/Fedora16x86_64
>
>
> # Kernel image to boot
>
>
> kernel = "/home/teo-en-ming/vms/f16/vmlinuz"
>
>
>
>
> # Ramdisk (optional)
>
>
> ramdisk = "/home/teo-en-ming/vms/f16/initrd.img"
>
>
>
> #bootloader="/usr/bin/pygrub"
>
>
> cd /etc/xen/images/
>
> sudo dd if=/dev/zero of=fedora16x86_64.img bs=1024k seek=10000 count=0
>
>
> To install Fedora 16 x86_64 as a paravirtualized guest domain,
>
>
> sudo xl create -c Fedora16x86_64
>
>
> After installing Fedora 16 x86_64 PV domU,
>
>
> sudo nano /etc/xen/Fedora16x86_64
>
>
> # Kernel image to boot
>
>
> #kernel = "/home/teo-en-ming/vms/f16/vmlinuz"
>
>
>
>
> # Ramdisk (optional)
>
>
> #ramdisk = "/home/teo-en-ming/vms/f16/initrd.img"
>
>
>
> bootloader="/usr/bin/pygrub"
>
>
> # XL domain configuration file for Fedora 16 x86_64 PV domU
>
> # Please refer to "man xl.cfg" for further explanations.
>
> # See also docs/misc/xl-network-configuration.markdown and
>
> # docs/misc/xl-disk-configuration.txt
>
>
> # Written by Teo En Ming (Zhang Enming)
>
> # Email: teo.en.ming@gmail.com
>
> # Mobile Phone: +65-8369-2618
>
> # Country: Singapore
>
> # Date: 18 Mar 2012 Sun
>
>
> name="Fedora16x86_64"
>
>
> builder="generic"
>
>
> vcpus=2
>
>
> memory=1024
>
>
> on_poweroff="destroy"
>
> on_reboot="restart"
>
> on_crash="destroy"
>
>
> disk=[ ''format=raw, vdev=hda, access=rw, 
> target=/etc/xen/images/fedora16x86_64.img'' ]
>
>
> vif=[ ''bridge=virbr0'' ]
>
>
> vfb=[ 
>
''vnc=1,vnclisten=localhost,vncdisplay=2,vncunused=1,vncpasswd=,sdl=0''
]
>
>
> gfx_passthru=0
>
>
> # Step 1
>
> # To install Fedora 16 x86_64 PV domU, configure the kernel, ramdisk, 
> and extra keys below and comment out bootloader.
>
> # Kernel image to boot
>
> kernel = "/home/teo-en-ming/vms/f16/vmlinuz"
>
>
> # Ramdisk (optional)
>
> ramdisk = "/home/teo-en-ming/vms/f16/initrd.img"
>
>
> # Kernel command line options
>
> #extra = "root=/dev/xvda1"
>
>
> # Step 2
>
> # To boot the already installed Fedora 16 x86_64 PV domU, comment out 
> the keys in Step 1 and uncomment bootloader below.
>
>
> #bootloader="/usr/bin/pygrub"
>
> Please advise.
>
> Thank you very much.
>
> Yours sincerely,
>
> Teo En Ming (Zhang Enming)
>
>
>
>

















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

Any ideas? There has been very few documentation on XL domain 
configuration files on the internet.

Yours sincerely,

Teo En Ming (Zhang Enming)

On 18/03/2012 22:41, Teo En Ming (Zhang Enming) wrote:
> Hi,
>
> I have attached error logs. Please help.
>
> Thank you very much.
>
> Yours sincerely,
>
> Teo En Ming (Zhang Enming)
>
>
> On 18/03/2012 19:44, Teo En Ming (Zhang Enming) wrote:
>> Hi,
>>
>> I cannot start Linux PV guests. "sudo xl create -c" reports
that a
>> domain has successfully started but "ps -ef | grep qemu"
returns no
>> output and "sudo xl list" doesn''t show that the PV
domain has started.
>>
>> Please review the following installation steps which I have written 
>> and see if there are any mistakes.
>>
>>
*XL****Domain****Configuration****File****for****Fedora****16****x86_64****PV****domU****(Incomplete****Configuration,****Not****Tested,****Do****Not****Use)*
>>
>>
>> You will need to install apache2 and create a local http mirror.
>>
>>
>> sudo apt-get install apache2
>>
>>
>> cd /media
>>
>> sudo mkdir fedora
>>
>> cd ~/Downloads
>>
>> sudo mount -o loop _Fedora-16-x86_64-DVD.iso 
>>
<http://download.fedoraproject.org/pub/fedora/linux/releases/16/Fedora/x86_64/iso/Fedora-16-x86_64-DVD.iso>_
>> /media/fedora
>>
>> cd
>>
>> mkdir -p vms/f16
>>
>> cd /media/fedora/images/pxeboot
>>
>> cp vmlinuz initrd.img ~/vms/f16/
>>
>>
>>
>> sudo nano /etc/xen/Fedora16x86_64
>>
>>
>> # Kernel image to boot
>>
>>
>> kernel = "/home/teo-en-ming/vms/f16/vmlinuz"
>>
>>
>>
>>
>> # Ramdisk (optional)
>>
>>
>> ramdisk = "/home/teo-en-ming/vms/f16/initrd.img"
>>
>>
>>
>> #bootloader="/usr/bin/pygrub"
>>
>>
>> cd /etc/xen/images/
>>
>> sudo dd if=/dev/zero of=fedora16x86_64.img bs=1024k seek=10000 count=0
>>
>>
>> To install Fedora 16 x86_64 as a paravirtualized guest domain,
>>
>>
>> sudo xl create -c Fedora16x86_64
>>
>>
>> After installing Fedora 16 x86_64 PV domU,
>>
>>
>> sudo nano /etc/xen/Fedora16x86_64
>>
>>
>> # Kernel image to boot
>>
>>
>> #kernel = "/home/teo-en-ming/vms/f16/vmlinuz"
>>
>>
>>
>>
>> # Ramdisk (optional)
>>
>>
>> #ramdisk = "/home/teo-en-ming/vms/f16/initrd.img"
>>
>>
>>
>> bootloader="/usr/bin/pygrub"
>>
>>
>> # XL domain configuration file for Fedora 16 x86_64 PV domU
>>
>> # Please refer to "man xl.cfg" for further explanations.
>>
>> # See also docs/misc/xl-network-configuration.markdown and
>>
>> # docs/misc/xl-disk-configuration.txt
>>
>>
>> # Written by Teo En Ming (Zhang Enming)
>>
>> # Email: teo.en.ming@gmail.com
>>
>> # Mobile Phone: +65-8369-2618
>>
>> # Country: Singapore
>>
>> # Date: 18 Mar 2012 Sun
>>
>>
>> name="Fedora16x86_64"
>>
>>
>> builder="generic"
>>
>>
>> vcpus=2
>>
>>
>> memory=1024
>>
>>
>> on_poweroff="destroy"
>>
>> on_reboot="restart"
>>
>> on_crash="destroy"
>>
>>
>> disk=[ ''format=raw, vdev=hda, access=rw, 
>> target=/etc/xen/images/fedora16x86_64.img'' ]
>>
>>
>> vif=[ ''bridge=virbr0'' ]
>>
>>
>> vfb=[ 
>>
''vnc=1,vnclisten=localhost,vncdisplay=2,vncunused=1,vncpasswd=,sdl=0''
]
>>
>>
>> gfx_passthru=0
>>
>>
>> # Step 1
>>
>> # To install Fedora 16 x86_64 PV domU, configure the kernel, ramdisk, 
>> and extra keys below and comment out bootloader.
>>
>> # Kernel image to boot
>>
>> kernel = "/home/teo-en-ming/vms/f16/vmlinuz"
>>
>>
>> # Ramdisk (optional)
>>
>> ramdisk = "/home/teo-en-ming/vms/f16/initrd.img"
>>
>>
>> # Kernel command line options
>>
>> #extra = "root=/dev/xvda1"
>>
>>
>> # Step 2
>>
>> # To boot the already installed Fedora 16 x86_64 PV domU, comment out 
>> the keys in Step 1 and uncomment bootloader below.
>>
>>
>> #bootloader="/usr/bin/pygrub"
>>
>> Please advise.
>>
>> Thank you very much.
>>
>> Yours sincerely,
>>
>> Teo En Ming (Zhang Enming)
>>
>>
>>
>>
>


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

Any ideas? There has been very few documentation on XL domain 
configuration files on the internet.

Yours sincerely,

Teo En Ming (Zhang Enming)

On 18/03/2012 22:41, Teo En Ming (Zhang Enming) wrote:
> Hi,
>
> I have attached error logs. Please help.
>
> Thank you very much.
>
> Yours sincerely,
>
> Teo En Ming (Zhang Enming)
>
>
> On 18/03/2012 19:44, Teo En Ming (Zhang Enming) wrote:
>> Hi,
>>
>> I cannot start Linux PV guests. "sudo xl create -c" reports
that a
>> domain has successfully started but "ps -ef | grep qemu"
returns no
>> output and "sudo xl list" doesn''t show that the PV
domain has started.
>>
>> Please review the following installation steps which I have written 
>> and see if there are any mistakes.
>>
>>
*XL****Domain****Configuration****File****for****Fedora****16****x86_64****PV****domU****(Incomplete****Configuration,****Not****Tested,****Do****Not****Use)*
>>
>>
>> You will need to install apache2 and create a local http mirror.
>>
>>
>> sudo apt-get install apache2
>>
>>
>> cd /media
>>
>> sudo mkdir fedora
>>
>> cd ~/Downloads
>>
>> sudo mount -o loop _Fedora-16-x86_64-DVD.iso 
>>
<http://download.fedoraproject.org/pub/fedora/linux/releases/16/Fedora/x86_64/iso/Fedora-16-x86_64-DVD.iso>_
>> /media/fedora
>>
>> cd
>>
>> mkdir -p vms/f16
>>
>> cd /media/fedora/images/pxeboot
>>
>> cp vmlinuz initrd.img ~/vms/f16/
>>
>>
>>
>> sudo nano /etc/xen/Fedora16x86_64
>>
>>
>> # Kernel image to boot
>>
>>
>> kernel = "/home/teo-en-ming/vms/f16/vmlinuz"
>>
>>
>>
>>
>> # Ramdisk (optional)
>>
>>
>> ramdisk = "/home/teo-en-ming/vms/f16/initrd.img"
>>
>>
>>
>> #bootloader="/usr/bin/pygrub"
>>
>>
>> cd /etc/xen/images/
>>
>> sudo dd if=/dev/zero of=fedora16x86_64.img bs=1024k seek=10000 count=0
>>
>>
>> To install Fedora 16 x86_64 as a paravirtualized guest domain,
>>
>>
>> sudo xl create -c Fedora16x86_64
>>
>>
>> After installing Fedora 16 x86_64 PV domU,
>>
>>
>> sudo nano /etc/xen/Fedora16x86_64
>>
>>
>> # Kernel image to boot
>>
>>
>> #kernel = "/home/teo-en-ming/vms/f16/vmlinuz"
>>
>>
>>
>>
>> # Ramdisk (optional)
>>
>>
>> #ramdisk = "/home/teo-en-ming/vms/f16/initrd.img"
>>
>>
>>
>> bootloader="/usr/bin/pygrub"
>>
>>
>> # XL domain configuration file for Fedora 16 x86_64 PV domU
>>
>> # Please refer to "man xl.cfg" for further explanations.
>>
>> # See also docs/misc/xl-network-configuration.markdown and
>>
>> # docs/misc/xl-disk-configuration.txt
>>
>>
>> # Written by Teo En Ming (Zhang Enming)
>>
>> # Email: teo.en.ming@gmail.com
>>
>> # Mobile Phone: +65-8369-2618
>>
>> # Country: Singapore
>>
>> # Date: 18 Mar 2012 Sun
>>
>>
>> name="Fedora16x86_64"
>>
>>
>> builder="generic"
>>
>>
>> vcpus=2
>>
>>
>> memory=1024
>>
>>
>> on_poweroff="destroy"
>>
>> on_reboot="restart"
>>
>> on_crash="destroy"
>>
>>
>> disk=[ ''format=raw, vdev=hda, access=rw, 
>> target=/etc/xen/images/fedora16x86_64.img'' ]
>>
>>
>> vif=[ ''bridge=virbr0'' ]
>>
>>
>> vfb=[ 
>>
''vnc=1,vnclisten=localhost,vncdisplay=2,vncunused=1,vncpasswd=,sdl=0''
]
>>
>>
>> gfx_passthru=0
>>
>>
>> # Step 1
>>
>> # To install Fedora 16 x86_64 PV domU, configure the kernel, ramdisk, 
>> and extra keys below and comment out bootloader.
>>
>> # Kernel image to boot
>>
>> kernel = "/home/teo-en-ming/vms/f16/vmlinuz"
>>
>>
>> # Ramdisk (optional)
>>
>> ramdisk = "/home/teo-en-ming/vms/f16/initrd.img"
>>
>>
>> # Kernel command line options
>>
>> #extra = "root=/dev/xvda1"
>>
>>
>> # Step 2
>>
>> # To boot the already installed Fedora 16 x86_64 PV domU, comment out 
>> the keys in Step 1 and uncomment bootloader below.
>>
>>
>> #bootloader="/usr/bin/pygrub"
>>
>> Please advise.
>>
>> Thank you very much.
>>
>> Yours sincerely,
>>
>> Teo En Ming (Zhang Enming)
>>
>>
>>
>>
>


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

On Mon, Mar 19, 2012 at 7:09 AM, Teo En Ming (Zhang Enming)
<singapore.mr.teo.en.ming@gmail.com> wrote:
>
> Any ideas? There has been very few documentation on XL domain
> configuration files on the internet.
Does xm work (using the same config file)?

If yes, xen-devel will be a good place to submit bug report, with the
emphasis on xl bug.

-- 
Fajar

On Mon, Mar 19, 2012 at 7:09 AM, Teo En Ming (Zhang Enming)
<singapore.mr.teo.en.ming@gmail.com> wrote:
>
> Any ideas? There has been very few documentation on XL domain
> configuration files on the internet.
Does xm work (using the same config file)?

If yes, xen-devel will be a good place to submit bug report, with the
emphasis on xl bug.

-- 
Fajar

Dear Fajar,

xm has been deprecated in Xen 4.2-unstable changeset 25070. It doesn''t 
work in xen 4.2-unstable.

Yours sincerely,

Teo En Ming (Zhang Enming)

On 19/03/2012 09:33, Fajar A. Nugraha wrote:
> On Mon, Mar 19, 2012 at 7:09 AM, Teo En Ming (Zhang Enming)
> <singapore.mr.teo.en.ming@gmail.com>  wrote:
>> Any ideas? There has been very few documentation on XL domain
>> configuration files on the internet.
> Does xm work (using the same config file)?
>
> If yes, xen-devel will be a good place to submit bug report, with the
> emphasis on xl bug.
>

Dear Fajar,

xm has been deprecated in Xen 4.2-unstable changeset 25070. It doesn''t 
work in xen 4.2-unstable.

Yours sincerely,

Teo En Ming (Zhang Enming)

On 19/03/2012 09:33, Fajar A. Nugraha wrote:
> On Mon, Mar 19, 2012 at 7:09 AM, Teo En Ming (Zhang Enming)
> <singapore.mr.teo.en.ming@gmail.com>  wrote:
>> Any ideas? There has been very few documentation on XL domain
>> configuration files on the internet.
> Does xm work (using the same config file)?
>
> If yes, xen-devel will be a good place to submit bug report, with the
> emphasis on xl bug.
>

On Mon, Mar 19, 2012 at 9:17 AM, Teo En Ming (Zhang Enming)
<singapore.mr.teo.en.ming@gmail.com> wrote:
> Dear Fajar,
>
> xm has been deprecated in Xen 4.2-unstable changeset 25070.
Ouch :)
> It doesn''t work
> in xen 4.2-unstable.
Still, I recommend you try it. Possibly by installing old version of
xen userland tools (which might work).

That would help pinpoint the source of problem (is it xl? or is it
kernel/initrd combination? or is it something else?).

You might get better response from developers if you have a concise,
complete bug report instead of simply saying "it doesn''t work.
help!".

-- 
Fajar

On Mon, Mar 19, 2012 at 9:17 AM, Teo En Ming (Zhang Enming)
<singapore.mr.teo.en.ming@gmail.com> wrote:
> Dear Fajar,
>
> xm has been deprecated in Xen 4.2-unstable changeset 25070.
Ouch :)
> It doesn''t work
> in xen 4.2-unstable.
Still, I recommend you try it. Possibly by installing old version of
xen userland tools (which might work).

That would help pinpoint the source of problem (is it xl? or is it
kernel/initrd combination? or is it something else?).

You might get better response from developers if you have a concise,
complete bug report instead of simply saying "it doesn''t work.
help!".

-- 
Fajar

I have moved xen-devel@ to bcc. Please for this and all future postings
you make pick an appropriate list and stop cross posting as you have
done with every post you have made over the last couple of days. If you
are unsure then please start with xen-users@.

On Mon, 2012-03-19 at 02:17 +0000, Teo En Ming (Zhang Enming)
wrote:
> Dear Fajar,
> 
> xm has been deprecated in Xen 4.2-unstable changeset 25070. It
doesn''t
> work in xen 4.2-unstable.
deprecated != doesn''t work. Please do as Fajar suggests and try it. If
it works with xm but not xl then this is a useful data point.
> >> Any ideas? There has been very few documentation on XL domain
There is documentation in the Xen tree which is published online at:
http://xenbits.xen.org/docs/unstable/man/xl.conf.5.html
http://xenbits.xen.org/docs/unstable/man/xl.cfg.5.html
http://xenbits.xen.org/docs/unstable/man/xl.1.html

These are linked to from the very first google hit from "xen xl
documentation" ( http://xen.org/support/generated.html ).

There are also several xlexample configurations provided in the Xen
source tree.

Ian.
> >> configuration files on the internet.
> > Does xm work (using the same config file)?
> >
> > If yes, xen-devel will be a good place to submit bug report, with the
> > emphasis on xl bug.
> >
> 
> 
> _______________________________________________
> Xen-users mailing list
> Xen-users@lists.xen.org
> http://lists.xen.org/xen-users

>>> On 19.03.12 at 03:25, "Fajar A. Nugraha"
<list@fajar.net> wrote:
> You might get better response from developers if you have a concise,
> complete bug report instead of simply saying "it doesn''t
work. help!".
Indeed, specifically if you post on xen-devel. And please stop cross
posting (moving xen-devel to BCC); the majority of your mails belong
(at most) onto xen-users.

Jan

On 19/03/2012 15:23, Ian Campbell wrote:
> I have moved xen-devel@ to bcc. Please for this and all future postings
> you make pick an appropriate list and stop cross posting as you have
> done with every post you have made over the last couple of days. If you
> are unsure then please start with xen-users@.
>
> On Mon, 2012-03-19 at 02:17 +0000, Teo En Ming (Zhang Enming) wrote:
>> Dear Fajar,
>>
>> xm has been deprecated in Xen 4.2-unstable changeset 25070. It
doesn''t
>> work in xen 4.2-unstable.
> deprecated != doesn''t work. Please do as Fajar suggests and try
it. If
> it works with xm but not xl then this is a useful data point.
>
>>>> Any ideas? There has been very few documentation on XL domain
> There is documentation in the Xen tree which is published online at:
> http://xenbits.xen.org/docs/unstable/man/xl.conf.5.html
> http://xenbits.xen.org/docs/unstable/man/xl.cfg.5.html
> http://xenbits.xen.org/docs/unstable/man/xl.1.html
>
> These are linked to from the very first google hit from "xen xl
> documentation" ( http://xen.org/support/generated.html ).
>
> There are also several xlexample configurations provided in the Xen
> source tree.
>
> Ian.
>
>>>> configuration files on the internet.
>>> Does xm work (using the same config file)?
>>>
>>> If yes, xen-devel will be a good place to submit bug report, with
the
>>> emphasis on xl bug.
>>>
>>
>> _______________________________________________
>> Xen-users mailing list
>> Xen-users@lists.xen.org
>> http://lists.xen.org/xen-users
>
>
Hi,

I have found a bug with xl in Xen 4.2-unstable changeset 25070.

When I try to start Linux paravirtualized guests in Xen 4.2-unstable, 
they CANNOT start at all and exit IMMEDIATELY.

When I switched to Xen 4.1.3-rc1-pre, Linux PV guests start 
successfully, albeit with a change to the disk parameter in the xl 
configuration file.

I have managed to install Fedora 16 amd64 in Xen 4.1.3-rc1-pre with xl, 
although the pxeboot installation takes a VERY LONG TIME, lasting 
numerous hours.

This is a bug with xl in Xen 4.2-unstable.

Please help to copy to xen-devel.

Thank you very much.

Yours sincerely,

Teo En Ming (Zhang Enming)

On 19/03/2012 16:48, Jan Beulich wrote:
>>>> On 19.03.12 at 03:25, "Fajar A.
Nugraha"<list@fajar.net>  wrote:
>> You might get better response from developers if you have a concise,
>> complete bug report instead of simply saying "it doesn''t
work. help!".
> Indeed, specifically if you post on xen-devel. And please stop cross
> posting (moving xen-devel to BCC); the majority of your mails belong
> (at most) onto xen-users.
>
> Jan
>
>
Hi,

I have already provided my installation steps, configuration files and 
error logs in /var/log/xen.

Have you missed them? Please check my earlier emails.

Thank you very much.

Yours sincerely,

Teo En Ming (Zhang Enming)

On Mon, 2012-03-19 at 10:09 +0000, Teo En Ming (Zhang Enming)
wrote:
> I have found a bug with xl in Xen 4.2-unstable changeset 25070.
> 
> When I try to start Linux paravirtualized guests in Xen 4.2-unstable, 
> they CANNOT start at all and exit IMMEDIATELY.
I have looked at your original mails and there are many different
configuration snippets and so it is not 100% clear to me what you are
actually running to provoke this error. Also you provided all of the
logs from under /var/log/xen but it is not clear which ones correspond
to the occasion when you saw the failure (many of those logs are rotated
logs from previous xl invocations).

Please can you provide a single guest configuration file which
demonstrates the issue which you are seeing and the output of running
"xl -vvv create -c <cfg>" for that precisely that <cfg>
file. Please
also attach exactly the /var/log/xen/qemu-dm-<name>.log
and /var/log/xen/xl-<name>.log produced by exactly that invocation of
xl.
> When I switched to Xen 4.1.3-rc1-pre, Linux PV guests start 
> successfully, albeit with a change to the disk parameter in the xl 
> configuration file.
What change did you have to make?

Ian.

On 19/03/2012 21:59, Ian Campbell wrote:
> On Mon, 2012-03-19 at 10:09 +0000, Teo En Ming (Zhang Enming) wrote:
>> I have found a bug with xl in Xen 4.2-unstable changeset 25070.
>>
>> When I try to start Linux paravirtualized guests in Xen 4.2-unstable,
>> they CANNOT start at all and exit IMMEDIATELY.
> I have looked at your original mails and there are many different
> configuration snippets and so it is not 100% clear to me what you are
> actually running to provoke this error. Also you provided all of the
> logs from under /var/log/xen but it is not clear which ones correspond
> to the occasion when you saw the failure (many of those logs are rotated
> logs from previous xl invocations).
>
> Please can you provide a single guest configuration file which
> demonstrates the issue which you are seeing and the output of running
> "xl -vvv create -c<cfg>" for that precisely that<cfg>
file. Please
> also attach exactly the /var/log/xen/qemu-dm-<name>.log
> and /var/log/xen/xl-<name>.log produced by exactly that invocation of
> xl.
>
>> When I switched to Xen 4.1.3-rc1-pre, Linux PV guests start
>> successfully, albeit with a change to the disk parameter in the xl
>> configuration file.
> What change did you have to make?
>
> Ian.
>
>
>
Dear Ian,

This is a bug with xl in Xen 4.2-unstable.

1. Linux PV guests cannot start in Xen 4.2-unstable changeset 25070 at all.

2. When I switch over to Xen 4.1.3-rc1-pre, Linux PV guests start 
successfully. I merely changed the disk = [ '' '' ] parameter
because the
configuration syntax is slightly different between Xen 4.1.x and Xen 
4.2-unstable.

I will be attaching my How To / tutorial / documentation shortly.

Please take note of this bug in xen-unstable.hg.

Thank you very much.

Yours sincerely,

Teo En Ming (Zhang Enming)

On Tue, 2012-03-20 at 01:11 +0000, Teo En Ming (Zhang Enming) wrote:
[...]
> > Please can you provide a single guest configuration file which
> > demonstrates the issue which you are seeing and the output of running
> > "xl -vvv create -c<cfg>" for that precisely
that<cfg>  file. Please
> > also attach exactly the /var/log/xen/qemu-dm-<name>.log
> > and /var/log/xen/xl-<name>.log produced by exactly that
invocation of
> > xl.
[...]
> I will be attaching my How To / tutorial / documentation shortly.
Please provide exactly and only the information I asked for in my
previous mail (quoted above). Otherwise I cannot help you. I am not
going to try and infer the answers to those questions from a How To.

Ian.

On 20/03/2012 15:12, Ian Campbell wrote:
> On Tue, 2012-03-20 at 01:11 +0000, Teo En Ming (Zhang Enming) wrote:
> [...]
>>> Please can you provide a single guest configuration file which
>>> demonstrates the issue which you are seeing and the output of
running
>>> "xl -vvv create -c<cfg>" for that precisely
that<cfg>   file. Please
>>> also attach exactly the /var/log/xen/qemu-dm-<name>.log
>>> and /var/log/xen/xl-<name>.log produced by exactly that
invocation of
>>> xl.
> [...]
>> I will be attaching my How To / tutorial / documentation shortly.
> Please provide exactly and only the information I asked for in my
> previous mail (quoted above). Otherwise I cannot help you. I am not
> going to try and infer the answers to those questions from a How To.
>
> Ian.
>
>
>
Dear Ian,

As I told you before, I cannot start Linux PV guests in Xen 
4.2-unstable. There is a bug with xl in Xen 4.2-unstable. However, I am 
able to start Fedora 16 amd64 PV domU in Xen 4.1.3-rc1-pre.

My F16 Linux PV guest configuration file is as follows:

======================================================================================================================
# NOTE: Paravirtualized guests will only work with Xen 4.1.3-rc1-pre
# and NOT Xen 4.2-unstable changeset 25070.
#
# XL domain configuration file for Fedora 16 x86_64 PV domU
# Please refer to "man xl.cfg" for further explanations.
# See also docs/misc/xl-network-configuration.markdown and
# docs/misc/xl-disk-configuration.txt
# Written by Teo En Ming (Zhang Enming)
# Email #1: teo.en.ming@gmail.com
# Email #2: teo-en-ming@teo-en-ming.com
# Mobile Phone: +65-8369-2618
# Country: Singapore
# Date: 19 Mar 2012 Mon
name="Fedora16x86_64"
builder="generic"
vcpus=2
# Minimum memory of 768 MB is required to install Fedora 16 x86_64
#memory=768
memory=512
on_poweroff="destroy"
on_reboot="restart"
on_crash="destroy"
# Format compatible with Xen 4.2-unstable
#disk=[ 'format=raw, vdev=hda, access=rw, 
target=/etc/xen/images/fedora16x86_64.img' ]
# Format compatible with Xen 4.1.3-rc1-pre
disk=[ 'file:/etc/xen/images/fedora16x86_64.img,hda,w' ]
# Keywords type and model are reserved for HVM guests and NOT valid for 
PV guests
vif=[ 'bridge=virbr0' ]
# Virtual frame buffer parameter is for paravirtualized guests only.
vfb=[ 
'vnc=1,vnclisten=localhost,vncdisplay=2,vncunused=1,vncpasswd=,sdl=0' ]
gfx_passthru=0
# Step 1
# To install Fedora 16 x86_64 PV domU, configure the kernel, ramdisk, 
and extra keys below and
comment out bootloader.
# Kernel image to boot
#kernel = "/home/teo-en-ming/vms/f16/vmlinuz"
# Ramdisk (optional)
#ramdisk = "/home/teo-en-ming/vms/f16/initrd.img"
# Kernel command line options
#extra = "root=/dev/xvda1"
# Step 2
# To boot the already installed Fedora 16 x86_64 PV domU, comment out 
the parameters in Step 1
and uncomment bootloader below.
bootloader="pygrub"

============================================================================
The output of "sudo xl -vvv create -c Fedora16x86_64" is as follows:

============================================================================
pyGRUB version 0.6
┌────────────────────────────────────────────────────────────────────────┐
│ Fedora Linux, with Linux 3.2.10-3.fc16.x86_64 │
│ Fedora Linux, with Linux 3.2.10-3.fc16.x86_64 (recovery mode) │
│ │
│ │
│ │
│ │
│ │
│ │
└────────────────────────────────────────────────────────────────────────┘
Use the ^ and v keys to select which entry is highlighted.
Press enter to boot the selected OS, 'e' to edit the
commands before booting, 'a' to modify the kernel arguments
before booting, or 'c' for a command line.




Will boot selected entry in 1 seconds


domainbuilder: detail: xc_dom_allocate: 
cmdline="root=/dev/mapper/vg_fedora16x8664-lv_root ro 
rd.lvm.lv=vg_fedora16x8664/lv_swap rd.dm=0 
rd.lvm.lv=vg_fedora16x8664/lv_root KEYTABLE=us quiet 
SYSFONT=latarcyrheb-sun16 rhgb rd.md=0 rd.luks=0 LANG=en_US.UTF-8 ", 
features="(null)"
domainbuilder: detail: xc_dom_kernel_mem: called
domainbuilder: detail: xc_dom_ramdisk_mem: called
domainbuilder: detail: xc_dom_boot_xen_init: ver 4.1, 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
domainbuilder: detail: xc_dom_parse_image: called
domainbuilder: detail: xc_dom_find_loader: trying multiboot-binary 
loader ...
domainbuilder: detail: loader probe failed
domainbuilder: detail: xc_dom_find_loader: trying Linux bzImage loader ...
domainbuilder: detail: xc_dom_malloc : 16818 kB
domainbuilder: detail: xc_dom_do_gunzip: unzip ok, 0x45dc95 -> 0x106c970
domainbuilder: detail: loader probe OK
xc: detail: elf_parse_binary: phdr: paddr=0x1000000 memsz=0x87e000
xc: detail: elf_parse_binary: phdr: paddr=0x1a00000 memsz=0xd50e0
xc: detail: elf_parse_binary: phdr: paddr=0x1ad6000 memsz=0x14480
xc: detail: elf_parse_binary: phdr: paddr=0x1aeb000 memsz=0x40b000
xc: detail: elf_parse_binary: memory: 0x1000000 -> 0x1ef6000
xc: detail: elf_xen_parse_note: GUEST_OS = "linux"
xc: detail: elf_xen_parse_note: GUEST_VERSION = "2.6"
xc: detail: elf_xen_parse_note: XEN_VERSION = "xen-3.0"
xc: detail: elf_xen_parse_note: VIRT_BASE = 0xffffffff80000000
xc: detail: elf_xen_parse_note: ENTRY = 0xffffffff81aeb200
xc: detail: elf_xen_parse_note: HYPERCALL_PAGE = 0xffffffff81001000
xc: detail: elf_xen_parse_note: FEATURES = 
"!writable_page_tables|pae_pgdir_above_4gb"
xc: detail: elf_xen_parse_note: PAE_MODE = "yes"
xc: detail: elf_xen_parse_note: LOADER = "generic"
xc: detail: elf_xen_parse_note: unknown xen elf note (0xd)
xc: detail: elf_xen_parse_note: SUSPEND_CANCEL = 0x1
xc: detail: elf_xen_parse_note: HV_START_LOW = 0xffff800000000000
xc: detail: elf_xen_parse_note: PADDR_OFFSET = 0x0
xc: detail: elf_xen_addr_calc_check: addresses:
xc: detail: virt_base = 0xffffffff80000000
xc: detail: elf_paddr_offset = 0x0
xc: detail: virt_offset = 0xffffffff80000000
xc: detail: virt_kstart = 0xffffffff81000000
xc: detail: virt_kend = 0xffffffff81ef6000
xc: detail: virt_entry = 0xffffffff81aeb200
xc: detail: p2m_base = 0xffffffffffffffff
domainbuilder: detail: xc_dom_parse_elf_kernel: xen-3.0-x86_64: 
0xffffffff81000000 -> 0xffffffff81ef6000
domainbuilder: detail: xc_dom_mem_init: mem 512 MB, pages 0x20000 pages, 
4k each
domainbuilder: detail: xc_dom_mem_init: 0x20000 pages
domainbuilder: detail: xc_dom_boot_mem_init: called
domainbuilder: detail: x86_compat: guest xen-3.0-x86_64, address size 64
domainbuilder: detail: xc_dom_malloc : 1024 kB
domainbuilder: detail: xc_dom_build_image: called
domainbuilder: detail: xc_dom_alloc_segment: kernel : 0xffffffff81000000 
-> 0xffffffff81ef6000 (pfn 0x1000 + 0xef6 pages)
domainbuilder: detail: xc_dom_pfn_to_ptr: domU mapping: pfn 0x1000+0xef6 
at 0x7f0808ebc000
xc: detail: elf_load_binary: phdr 0 at 0x0x7f0808ebc000 -> 0x0x7f080973a000
xc: detail: elf_load_binary: phdr 1 at 0x0x7f08098bc000 -> 0x0x7f08099910e0
xc: detail: elf_load_binary: phdr 2 at 0x0x7f0809992000 -> 0x0x7f08099a6480
xc: detail: elf_load_binary: phdr 3 at 0x0x7f08099a7000 -> 0x0x7f0809b28000
domainbuilder: detail: xc_dom_alloc_segment: ramdisk : 
0xffffffff81ef6000 -> 0xffffffff84bef000 (pfn 0x1ef6 + 0x2cf9 pages)
domainbuilder: detail: xc_dom_malloc : 269 kB
domainbuilder: detail: xc_dom_pfn_to_ptr: domU mapping: pfn 
0x1ef6+0x2cf9 at 0x7f08061c3000
domainbuilder: detail: xc_dom_do_gunzip: unzip ok, 0x1089152 -> 0x2cf8810
domainbuilder: detail: xc_dom_alloc_segment: phys2mach : 
0xffffffff84bef000 -> 0xffffffff84cef000 (pfn 0x4bef + 0x100 pages)
domainbuilder: detail: xc_dom_pfn_to_ptr: domU mapping: pfn 0x4bef+0x100 
at 0x7f08060c3000
domainbuilder: detail: xc_dom_alloc_page : start info : 
0xffffffff84cef000 (pfn 0x4cef)
domainbuilder: detail: xc_dom_alloc_page : xenstore : 0xffffffff84cf0000 
(pfn 0x4cf0)
domainbuilder: detail: xc_dom_alloc_page : console : 0xffffffff84cf1000 
(pfn 0x4cf1)
domainbuilder: detail: nr_page_tables: 0x0000ffffffffffff/48: 
0xffff000000000000 -> 0xffffffffffffffff, 1 table(s)
domainbuilder: detail: nr_page_tables: 0x0000007fffffffff/39: 
0xffffff8000000000 -> 0xffffffffffffffff, 1 table(s)
domainbuilder: detail: nr_page_tables: 0x000000003fffffff/30: 
0xffffffff80000000 -> 0xffffffffbfffffff, 1 table(s)
domainbuilder: detail: nr_page_tables: 0x00000000001fffff/21: 
0xffffffff80000000 -> 0xffffffff84ffffff, 40 table(s)
domainbuilder: detail: xc_dom_alloc_segment: page tables : 
0xffffffff84cf2000 -> 0xffffffff84d1d000 (pfn 0x4cf2 + 0x2b pages)
domainbuilder: detail: xc_dom_pfn_to_ptr: domU mapping: pfn 0x4cf2+0x2b 
at 0x7f080e89f000
domainbuilder: detail: xc_dom_alloc_page : boot stack : 
0xffffffff84d1d000 (pfn 0x4d1d)
domainbuilder: detail: xc_dom_build_image : virt_alloc_end : 
0xffffffff84d1e000
domainbuilder: detail: xc_dom_build_image : virt_pgtab_end : 
0xffffffff85000000
domainbuilder: detail: xc_dom_boot_image: called
domainbuilder: detail: arch_setup_bootearly: doing nothing
domainbuilder: detail: xc_dom_compat_check: supported guest type: 
xen-3.0-x86_64 <= matches
domainbuilder: detail: xc_dom_compat_check: supported guest type: 
xen-3.0-x86_32p
domainbuilder: detail: xc_dom_compat_check: supported guest type: 
hvm-3.0-x86_32
domainbuilder: detail: xc_dom_compat_check: supported guest type: 
hvm-3.0-x86_32p
domainbuilder: detail: xc_dom_compat_check: supported guest type: 
hvm-3.0-x86_64
domainbuilder: detail: xc_dom_update_guest_p2m: dst 64bit, pages 0x20000
domainbuilder: detail: clear_page: pfn 0x4cf1, mfn 0x18bd93
domainbuilder: detail: clear_page: pfn 0x4cf0, mfn 0x18bd94
domainbuilder: detail: xc_dom_pfn_to_ptr: domU mapping: pfn 0x4cef+0x1 
at 0x7f080e89e000
domainbuilder: detail: start_info_x86_64: called
domainbuilder: detail: setup_hypercall_page: vaddr=0xffffffff81001000 
pfn=0x1001

Fedora release 16 (Verne)
Kernel 3.2.10-3.fc16.x86_64 on an x86_64 (hvc0)

fedora16-x86-64 login:

=============================================================================================================
Please look at the screenshot of Fedora 16 x86-64 PV domU as follows:

http://i.imgur.com/a2FVr.png

Thank you very much.

Yours sincerely,

Teo En Ming (Zhang Enming)




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

On Tue, 2012-03-20 at 08:01 +0000, Teo En Ming (Zhang Enming)
wrote:
> On 20/03/2012 15:12, Ian Campbell wrote:
> > On Tue, 2012-03-20 at 01:11 +0000, Teo En Ming (Zhang Enming) wrote:
> > [...]
> >>> Please can you provide a single guest configuration file which
> >>> demonstrates the issue which you are seeing and the output of
running
> >>> "xl -vvv create -c<cfg>" for that precisely
that<cfg>   file. Please
> >>> also attach exactly the /var/log/xen/qemu-dm-<name>.log
> >>> and /var/log/xen/xl-<name>.log produced by exactly that
invocation of
> >>> xl.
> > [...]
> >> I will be attaching my How To / tutorial / documentation shortly.
> > Please provide exactly and only the information I asked for in my
> > previous mail (quoted above). Otherwise I cannot help you. I am not
> > going to try and infer the answers to those questions from a How To.
> >
> > Ian.
> >
> >
> >
> Dear Ian,
> 
> As I told you before, I cannot start Linux PV guests in Xen
> 4.2-unstable. There is a bug with xl in Xen 4.2-unstable. However, I am
> able to start Fedora 16 amd64 PV domU in Xen 4.1.3-rc1-pre.
> 
> My F16 Linux PV guest configuration file is as follows:
[...]

Thank you.
> The output of "sudo xl -vvv create -c Fedora16x86_64" is as
follows:
[...]
> Fedora release 16 (Verne)
> Kernel 3.2.10-3.fc16.x86_64 on an x86_64 (hvc0)
> 
> fedora16-x86-64 login:
> 
>
=============================================================================================================>
> Please look at the screenshot of Fedora 16 x86-64 PV domU as follows:
> 
> http://i.imgur.com/a2FVr.png
Both this image and the console output appear to show a guest which has
booted just fine (e.g. I have quoted the login prompt from your console
log above). What exactly do you think has not worked?

Ian.

On 20/03/2012 16:36, Ian Campbell wrote:
> On Tue, 2012-03-20 at 08:01 +0000, Teo En Ming (Zhang Enming) wrote:
>> On 20/03/2012 15:12, Ian Campbell wrote:
>>> On Tue, 2012-03-20 at 01:11 +0000, Teo En Ming (Zhang Enming)
wrote:
>>> [...]
>>>>> Please can you provide a single guest configuration file
which
>>>>> demonstrates the issue which you are seeing and the output
of running
>>>>> "xl -vvv create -c<cfg>" for that precisely
that<cfg>    file. Please
>>>>> also attach exactly the
/var/log/xen/qemu-dm-<name>.log
>>>>> and /var/log/xen/xl-<name>.log produced by exactly
that invocation of
>>>>> xl.
>>> [...]
>>>> I will be attaching my How To / tutorial / documentation
shortly.
>>> Please provide exactly and only the information I asked for in my
>>> previous mail (quoted above). Otherwise I cannot help you. I am not
>>> going to try and infer the answers to those questions from a How
To.
>>>
>>> Ian.
>>>
>>>
>>>
>> Dear Ian,
>>
>> As I told you before, I cannot start Linux PV guests in Xen
>> 4.2-unstable. There is a bug with xl in Xen 4.2-unstable. However, I am
>> able to start Fedora 16 amd64 PV domU in Xen 4.1.3-rc1-pre.
>>
>> My F16 Linux PV guest configuration file is as follows:
> [...]
>
> Thank you.
>
>> The output of "sudo xl -vvv create -c Fedora16x86_64" is as
follows:
> [...]
>> Fedora release 16 (Verne)
>> Kernel 3.2.10-3.fc16.x86_64 on an x86_64 (hvc0)
>>
>> fedora16-x86-64 login:
>>
>>
=============================================================================================================>>
>> Please look at the screenshot of Fedora 16 x86-64 PV domU as follows:
>>
>> http://i.imgur.com/a2FVr.png
> Both this image and the console output appear to show a guest which has
> booted just fine (e.g. I have quoted the login prompt from your console
> log above). What exactly do you think has not worked?
>
> Ian.
>
>
>
>
Dear Ian,

I want to make 2 points.

1) Linux PV guests cannot start in Xen 4.2-unstable with XL. Linux PV 
guests can only successfully start in Xen 4.1.3-rc1-pre.

2) The performance of Fedora 16 x86-64 PV guest in Xen 4.1.3-rc1-pre is 
really very poor and sluggish. Do you want to watch a video of it?

Thank you for your understanding.

Yours sincerely,

Teo En Ming (Zhang Enming)

On Tue, 2012-03-20 at 14:42 +0000, Teo En Ming (Zhang Enming) wrote:
> I want to make 2 points.
[snip]

Once again you have not answered my direct questions nor provided the
information I asked for about this bug.

If you do not start answering my requests for information directly with
answers to the actual questions which I ask then I am going to stop
responding to you altogether.
> 1) Linux PV guests cannot start in Xen 4.2-unstable with XL. Linux PV 
> guests can only successfully start in Xen 4.1.3-rc1-pre.
Obviously it is not failing for me (or indeed others) so I need you to
explain, clearly & precisely, what you are actual seeing. "Linux PV
guests cannot start in Xen 4.2-unstable with XL" is not sufficient
information for me to go on and is not going to result in this bug
getting fixed.

I recommend you read http://wiki.xen.org/wiki/Reporting_Bugs_against_Xen
and in particular the document "How to report bugs effectively" which
is
linked to from that page.

So, for the last time: Please describe exactly how things fail on
xen-unstable for you and provide the command output and logs which I
requested. I mean the command output and logs which demonstrates the bug
with PV guests failing to start on 4.2-unstable and not some other bug.

At this point in time I am not interested in the output of any other
command or any information/logs relating to another bug.
> 2) The performance of Fedora 16 x86-64 PV guest in Xen 4.1.3-rc1-pre
> is really very poor and sluggish. Do you want to watch a video of it?
Lets deal with one thing at a time. i.e. lets concentrate on the PV
guests not working on 4.2-unstable first. You are simply confusing
matters and reducing the chances of either bug getting fixed by
conflating the two problems.

Ian.

On 20/03/2012 23:51, Dario Faggioli wrote:
> On Tue, 2012-03-20 at 14:55 +0000, Ian Campbell wrote:
>>> 1) Linux PV guests cannot start in Xen 4.2-unstable with XL. Linux
PV
>>> guests can only successfully start in Xen 4.1.3-rc1-pre.
>> Obviously it is not failing for me (or indeed others) so I need you to
>> explain, clearly&  precisely, what you are actual seeing.
>>
> Indeed
>
>> "Linux PV
>> guests cannot start in Xen 4.2-unstable with XL" is not sufficient
>> information for me to go on and is not going to result in this bug
>> getting fixed.
>>
> I''m running some benchmarks since a couple of weeks, and they
involved
> _a_lot_ of PV-guest boot and shutdown cycles, and all my PV-guests are
> going up and down just fine. And yes, I''m on xen-unstable (I pull
from
> the hg repo every day).
>
> Regards,
> Dario
>
Dear Dario,

I simply don''t know why I cannot start Linux PV guests in Xen 
4.2-unstable with XL. _*I have already provided all of the required 
information (configuration and error logs) as required by Xen developers 
in my earlier emails. Please don''t ask me this question again.*_

Thank you very much.

Yours sincerely,

Teo En Ming (Zhang Enming)


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

On 20/03/2012 22:55, Ian Campbell wrote:
> On Tue, 2012-03-20 at 14:42 +0000, Teo En Ming (Zhang Enming) wrote:
>
>> I want to make 2 points.
> [snip]
>
> Once again you have not answered my direct questions nor provided the
> information I asked for about this bug.
>
> If you do not start answering my requests for information directly with
> answers to the actual questions which I ask then I am going to stop
> responding to you altogether.
>
>> 1) Linux PV guests cannot start in Xen 4.2-unstable with XL. Linux PV
>> guests can only successfully start in Xen 4.1.3-rc1-pre.
> Obviously it is not failing for me (or indeed others) so I need you to
> explain, clearly&  precisely, what you are actual seeing. "Linux
PV
> guests cannot start in Xen 4.2-unstable with XL" is not sufficient
> information for me to go on and is not going to result in this bug
> getting fixed.
>
> I recommend you read http://wiki.xen.org/wiki/Reporting_Bugs_against_Xen
> and in particular the document "How to report bugs effectively"
which is
> linked to from that page.
>
> So, for the last time: Please describe exactly how things fail on
> xen-unstable for you and provide the command output and logs which I
> requested. I mean the command output and logs which demonstrates the bug
> with PV guests failing to start on 4.2-unstable and not some other bug.
>
> At this point in time I am not interested in the output of any other
> command or any information/logs relating to another bug.
>
>> 2) The performance of Fedora 16 x86-64 PV guest in Xen 4.1.3-rc1-pre
>> is really very poor and sluggish. Do you want to watch a video of it?
> Lets deal with one thing at a time. i.e. lets concentrate on the PV
> guests not working on 4.2-unstable first. You are simply confusing
> matters and reducing the chances of either bug getting fixed by
> conflating the two problems.
>
> Ian.
>
>
>
Dear Ian,

I think you should watch my Youtube video which I have just uploaded.

Title: Bug: Fedora 16 PV domU cannot start in Xen 4.2-unstable Changeset 
25099 with xl
Youtube link: http://www.youtube.com/watch?v=XgHMpG9ayQQ&hd=1

*_My Youtube video provides ALL of the information you have requested_*, 
ie. Xen 4.2-unstable changeset 25099, Fedora 16 x86-64 PV domU 
configuration file, ps -ef | grep qemu, sudo xl list, and error logs, 
all in one video. The video clip is ONLY 3 minutes, so please take your 
time to watch it.

This video clip saves me the hassle of describing the bug in words.

Thank you very much.

Yours sincerely,

Teo En Ming (Zhang Enming)


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

On 25/03/2012 22:38, Teo En Ming (Zhang Enming) wrote:
> On 20/03/2012 22:55, Ian Campbell wrote:
>> On Tue, 2012-03-20 at 14:42 +0000, Teo En Ming (Zhang Enming) wrote:
>>
>>> I want to make 2 points.
>> [snip]
>>
>> Once again you have not answered my direct questions nor provided the
>> information I asked for about this bug.
>>
>> If you do not start answering my requests for information directly with
>> answers to the actual questions which I ask then I am going to stop
>> responding to you altogether.
>>
>>> 1) Linux PV guests cannot start in Xen 4.2-unstable with XL. Linux
PV
>>> guests can only successfully start in Xen 4.1.3-rc1-pre.
>> Obviously it is not failing for me (or indeed others) so I need you to
>> explain, clearly&  precisely, what you are actual seeing.
"Linux PV
>> guests cannot start in Xen 4.2-unstable with XL" is not sufficient
>> information for me to go on and is not going to result in this bug
>> getting fixed.
>>
>> I recommend you readhttp://wiki.xen.org/wiki/Reporting_Bugs_against_Xen
>> and in particular the document "How to report bugs
effectively" which is
>> linked to from that page.
>>
>> So, for the last time: Please describe exactly how things fail on
>> xen-unstable for you and provide the command output and logs which I
>> requested. I mean the command output and logs which demonstrates the
bug
>> with PV guests failing to start on 4.2-unstable and not some other bug.
>>
>> At this point in time I am not interested in the output of any other
>> command or any information/logs relating to another bug.
>>
>>> 2) The performance of Fedora 16 x86-64 PV guest in Xen
4.1.3-rc1-pre
>>> is really very poor and sluggish. Do you want to watch a video of
it?
>> Lets deal with one thing at a time. i.e. lets concentrate on the PV
>> guests not working on 4.2-unstable first. You are simply confusing
>> matters and reducing the chances of either bug getting fixed by
>> conflating the two problems.
>>
>> Ian.
>>
>>
>>
> Dear Ian,
>
> I think you should watch my Youtube video which I have just uploaded.
>
> Title: Bug: Fedora 16 PV domU cannot start in Xen 4.2-unstable 
> Changeset 25099 with xl
> Youtube link: http://www.youtube.com/watch?v=XgHMpG9ayQQ&hd=1
>
> *_My Youtube video provides ALL of the information you have 
> requested_*, ie. Xen 4.2-unstable changeset 25099, Fedora 16 x86-64 PV 
> domU configuration file, ps -ef | grep qemu, sudo xl list, and error 
> logs, all in one video. The video clip is ONLY 3 minutes, so please 
> take your time to watch it.
>
> This video clip saves me the hassle of describing the bug in words.
>
> Thank you very much.
>
> Yours sincerely,
>
> Teo En Ming (Zhang Enming)
Dear Ian Campbell and Konrad Wilk,

This is what I have found so far. I will make a summary of important points.

1) I was able to start Debian 6.0 Squeeze amd64 Paravirtualized domU in 
Xen 4.2-unstable with xl. Very Good.
2) I was NOT able to start Fedora 16 x86-64 Paravirtualized domU in Xen 
4.2-unstable with xl. The above Youtube video demonstrates it. But I was 
able to start Fedora 16 x86-64 PV domU in Xen 4.1.3-rc1-pre with xl. 
This is clearly a bug.
3) When I was installing Ubuntu 12.04 Beta 1 Precise Pangolin amd64 as a 
HVM domU in either Xen 4.1.3-rc1-pre or Xen 4.2-unstable, it hanged at 
COPYING FILES during installation. Hence I have to abort the HVM domU 
installation. Disk I/O performance is very poor.
4) Disk I/O performance is very poor with Debian 6.0 Squeeze PV domU in 
Xen 4.2-unstable and with Fedora 16 x86-64 PV domU in Xen 4.1.3-rc1-pre. 
The mouse cursor movement in both Fedora 16 and Debian 6.0 Squeeze PV 
domU is very sluggish and unresponsive. It also takes a long time to 
format filesystems and install packages in PV domU during OS 
installation. What causes the performance penalty in disk I/O?
5) Disk I/O performance is also very poor with Ubuntu 12.04 Beta 1 HVM 
domU installation. Formatting filesystems and copying files during 
installation take a long time. Mouse cursor movement is also very 
unresponsive.

I have already provided all the information you guys have requested in 
my previous emails. So why won''t you reply to me? *_Am I too dumb and 
stupid and technically incompetent?_*

I also need help with Xen 4.2-unstable VGA Passthrough. I am taking on 
multiple problems simultaneously.

Thank you very much for your kind assistance. Please help me.

-- 
Yours sincerely,

Mr. Teo En Ming (Zhang Enming)
Singapore



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

> 3) When I was installing Ubuntu 12.04 Beta 1 Precise Pangolin amd64 as
> a HVM domU in either Xen 4.1.3-rc1-pre or Xen 4.2-unstable, it hanged
> at COPYING FILES during installation. Hence I have to abort the HVM
> domU installation. Disk I/O performance is very poor.
> 4) Disk I/O performance is very poor with Debian 6.0 Squeeze PV domU
> in Xen 4.2-unstable and with Fedora 16 x86-64 PV domU in Xen
> 4.1.3-rc1-pre. The mouse cursor movement in both Fedora 16 and Debian
> 6.0 Squeeze PV domU is very sluggish and unresponsive. It also takes a
> long time to format filesystems and install packages in PV domU during
> OS installation. What causes the performance penalty in disk I/O?
> 5) Disk I/O performance is also very poor with Ubuntu 12.04 Beta 1 HVM
> domU installation. Formatting filesystems and copying files during
> installation take a long time. Mouse cursor movement is also very
> unresponsive.
I installed Ubuntu 12.04 beta server (AMD 64) and xen hypervisor from
ubuntu xen packages (v4.1). 
Then I installed Ubuntu 10.04 server as PV DomU and Ubuntu 10.04 desktop
as HVM DomU.
I could not enable IO virtualization, because iommu=1 and iommu=verbose
parameters seem to be not working.

When I run tests for my specific software I found, that in Ubuntu 10.04
HVM DomU there are too many interrupts when dealing with network.
Processor took about 50%si. I did not test disk IO, but think the
picture should be the same.

But I found solution, which works perfect for me. I installed Ubuntu
12.04 desktop beta (i386) as PVHVM DomU. It installed without hangs and
it works very fast with network and disk. 

Only one thing looks ugly: I can''t change maximal resolution of the
desktop more than 1024x768 (despite of settings stdvga=1 and
videoram=16)  

Also, I would like to know, how to enable verbose logs for iommu,
because xm dmesg does not show me any information about VT-d. I have the
line 
(XEN) Command line: placeholder iommu=verbose
in the dmesg logs, but still not got verbose logs...

Sergey Zhukov

On 30/03/2012 05:09, Sergey Zhukov wrote:
>> 3) When I was installing Ubuntu 12.04 Beta 1 Precise Pangolin amd64 as
>> a HVM domU in either Xen 4.1.3-rc1-pre or Xen 4.2-unstable, it hanged
>> at COPYING FILES during installation. Hence I have to abort the HVM
>> domU installation. Disk I/O performance is very poor.
>> 4) Disk I/O performance is very poor with Debian 6.0 Squeeze PV domU
>> in Xen 4.2-unstable and with Fedora 16 x86-64 PV domU in Xen
>> 4.1.3-rc1-pre. The mouse cursor movement in both Fedora 16 and Debian
>> 6.0 Squeeze PV domU is very sluggish and unresponsive. It also takes a
>> long time to format filesystems and install packages in PV domU during
>> OS installation. What causes the performance penalty in disk I/O?
>> 5) Disk I/O performance is also very poor with Ubuntu 12.04 Beta 1 HVM
>> domU installation. Formatting filesystems and copying files during
>> installation take a long time. Mouse cursor movement is also very
>> unresponsive.
> I installed Ubuntu 12.04 beta server (AMD 64) and xen hypervisor from
> ubuntu xen packages (v4.1).
> Then I installed Ubuntu 10.04 server as PV DomU and Ubuntu 10.04 desktop
> as HVM DomU.
> I could not enable IO virtualization, because iommu=1 and iommu=verbose
> parameters seem to be not working.
Dear Sergey Zhukou,

Thank you very much for your reply.

I did not have to specify IOMMU=1 and IOMMU=verbose in my multiboot 
xen.gz command line in GRUB2. IOMMU is enabled by default in Xen 
4.2-unstable.

sudo xl dmesg | grep ''I/O Virtualisation''

(XEN) I/O Virtualisation Enabled
>
> When I run tests for my specific software I found, that in Ubuntu 10.04
> HVM DomU there are too many interrupts when dealing with network.
> Processor took about 50%si. I did not test disk IO, but think the
> picture should be the same.
When I am installing Ubuntu 12.04 Beta 1 HVM domU, the network 
connection gets disconnected and re-connected many times. Did your 
installation hanged at copying files while installing Ubuntu 10.04 HVM domU?
>
> But I found solution, which works perfect for me. I installed Ubuntu
> 12.04 desktop beta (i386) as PVHVM DomU. It installed without hangs and
> it works very fast with network and disk.
I do not know what is PVHVM, I only know PV domU and HVM domU separately.
>
> Only one thing looks ugly: I can''t change maximal resolution of
the
> desktop more than 1024x768 (despite of settings stdvga=1 and
> videoram=16)
>
> Also, I would like to know, how to enable verbose logs for iommu,
> because xm dmesg does not show me any information about VT-d. I have the
> line
> (XEN) Command line: placeholder iommu=verbose
> in the dmesg logs, but still not got verbose logs...
I do not know how to enable verbose logs for IOMMU.

Have you tried "sudo xl dmesg | grep VT-d"?
>
> Sergey Zhukov
>
>

-- 
Yours sincerely,

Mr. Teo En Ming (Zhang Enming)
Singapore

On Fri, 2012-03-30 at 13:07 +0800, Teo En Ming (Zhang Enming)
wrote:
> On 30/03/2012 05:09, Sergey Zhukov wrote:
> >> 3) When I was installing Ubuntu 12.04 Beta 1 Precise Pangolin
amd64 as
> >> a HVM domU in either Xen 4.1.3-rc1-pre or Xen 4.2-unstable, it
hanged
> >> at COPYING FILES during installation. Hence I have to abort the
HVM
> >> domU installation. Disk I/O performance is very poor.
> >> 4) Disk I/O performance is very poor with Debian 6.0 Squeeze PV
domU
> >> in Xen 4.2-unstable and with Fedora 16 x86-64 PV domU in Xen
> >> 4.1.3-rc1-pre. The mouse cursor movement in both Fedora 16 and
Debian
> >> 6.0 Squeeze PV domU is very sluggish and unresponsive. It also
takes a
> >> long time to format filesystems and install packages in PV domU
during
> >> OS installation. What causes the performance penalty in disk I/O?
> >> 5) Disk I/O performance is also very poor with Ubuntu 12.04 Beta 1
HVM
> >> domU installation. Formatting filesystems and copying files during
> >> installation take a long time. Mouse cursor movement is also very
> >> unresponsive.
> > I installed Ubuntu 12.04 beta server (AMD 64) and xen hypervisor from
> > ubuntu xen packages (v4.1).
> > Then I installed Ubuntu 10.04 server as PV DomU and Ubuntu 10.04
desktop
> > as HVM DomU.
> > I could not enable IO virtualization, because iommu=1 and
iommu=verbose
> > parameters seem to be not working.
> Dear Sergey Zhukou,
> 
> Thank you very much for your reply.
> 
> I did not have to specify IOMMU=1 and IOMMU=verbose in my multiboot 
> xen.gz command line in GRUB2. IOMMU is enabled by default in Xen 
> 4.2-unstable.
> 
> sudo xl dmesg | grep ''I/O Virtualisation''
> 
> (XEN) I/O Virtualisation Enabled
> 
> >
> > When I run tests for my specific software I found, that in Ubuntu
10.04
> > HVM DomU there are too many interrupts when dealing with network.
> > Processor took about 50%si. I did not test disk IO, but think the
> > picture should be the same.
> 
> When I am installing Ubuntu 12.04 Beta 1 HVM domU, the network 
> connection gets disconnected and re-connected many times. Did your 
> installation hanged at copying files while installing Ubuntu 10.04 HVM
domU?
> 
No, installation has processed smoothly, after 15 minutes I had the
system installed.  
> >
> > But I found solution, which works perfect for me. I installed Ubuntu
> > 12.04 desktop beta (i386) as PVHVM DomU. It installed without hangs
and
> > it works very fast with network and disk.
> 
> I do not know what is PVHVM, I only know PV domU and HVM domU separately.
> 
Just an option xen_platform_pci=''1'' in HVM config file before
installation of distributive. There is a wiki 
http://wiki.xen.org/wiki/Xen_Linux_PV_on_HVM_drivers
> > Also, I would like to know, how to enable verbose logs for iommu,
> > because xm dmesg does not show me any information about VT-d. I have
the
> > line
> > (XEN) Command line: placeholder iommu=verbose
> > in the dmesg logs, but still not got verbose logs...
> 
> I do not know how to enable verbose logs for IOMMU.
> 
> Have you tried "sudo xl dmesg | grep VT-d"?
Yes, that the thing I told about, that I don''t have any lines about
VT-d. This is my full log

(XEN) Bootloader: GRUB 1.99-18ubuntu1
(XEN) Command line: placeholder iommu=verbose
(XEN) Video information:
(XEN)  VGA is text mode 80x25, font 8x16
(XEN)  VBE/DDC methods: none; EDID transfer time: 0 seconds
(XEN)  EDID info not retrieved because no DDC retrieval method detected
(XEN) Disc information:
(XEN)  Found 1 MBR signatures
(XEN)  Found 1 EDD information structures
(XEN) Xen-e820 RAM map:
(XEN)  0000000000000000 - 000000000009ec00 (usable)
(XEN)  000000000009ec00 - 00000000000a0000 (reserved)
(XEN)  00000000000e0000 - 0000000000100000 (reserved)
(XEN)  0000000000100000 - 0000000020000000 (usable)
(XEN)  0000000020000000 - 0000000020200000 (reserved)
(XEN)  0000000020200000 - 0000000040000000 (usable)
(XEN)  0000000040000000 - 0000000040200000 (reserved)
(XEN)  0000000040200000 - 00000000babc3000 (usable)
(XEN)  00000000babc3000 - 00000000bac0c000 (ACPI NVS)
(XEN)  00000000bac0c000 - 00000000bacc4000 (reserved)
(XEN)  00000000bacc4000 - 00000000baccc000 (ACPI data)
(XEN)  00000000baccc000 - 00000000bacf3000 (reserved)
(XEN)  00000000bacf3000 - 00000000bacf5000 (usable)
(XEN)  00000000bacf5000 - 00000000bad05000 (reserved)
(XEN)  00000000bad05000 - 00000000bad13000 (ACPI NVS)
(XEN)  00000000bad13000 - 00000000bad38000 (reserved)
(XEN)  00000000bad38000 - 00000000bad7b000 (ACPI NVS)
(XEN)  00000000bad7b000 - 00000000bb000000 (usable)
(XEN)  00000000bb800000 - 00000000bfa00000 (reserved)
(XEN)  00000000fed1c000 - 00000000fed40000 (reserved)
(XEN)  00000000ff000000 - 0000000100000000 (reserved)
(XEN)  0000000100000000 - 000000043fe00000 (usable)
(XEN) ACPI: RSDP 000F0450, 0024 (r2 ALASKA)
(XEN) ACPI: XSDT BACC4070, 005C (r1 ALASKA    A M I  1072009 AMI
10013)
(XEN) ACPI: FACP BACCB4A0, 00F4 (r4 ALASKA    A M I  1072009 AMI
10013)
(XEN) ACPI: DSDT BACC4158, 7348 (r2 ALASKA    A M I       15 INTL
20051117)
(XEN) ACPI: FACS BAD0AF80, 0040
(XEN) ACPI: APIC BACCB598, 0072 (r3 ALASKA    A M I  1072009 AMI
10013)
(XEN) ACPI: SSDT BACCB610, 0102 (r1 AMICPU     PROC        1 MSFT
3000001)
(XEN) ACPI: MCFG BACCB718, 003C (r1 ALASKA    A M I  1072009 MSFT
97)
(XEN) ACPI: HPET BACCB758, 0038 (r1 ALASKA    A M I  1072009 AMI.
4)
(XEN) ACPI: ASF! BACCB790, 00A0 (r32 INTEL       HCG        1 TFSM
F4240)
(XEN) ACPI: BGRT BACCB830, 003C (r0 ALASKA    A M I  1072009 AMI
10013)
(XEN) System RAM: 16295MB (16687008kB)
(XEN) Domain heap initialised
(XEN) ACPI: 32/64X FACS address mismatch in FADT -
bad0af80/0000000000000000, using 32
(XEN) Processor #0 6:10 APIC version 21
(XEN) Processor #2 6:10 APIC version 21
(XEN) Processor #4 6:10 APIC version 21
(XEN) Processor #6 6:10 APIC version 21
(XEN) IOAPIC[0]: apic_id 0, version 32, address 0xfec00000, GSI 0-23
(XEN) Enabling APIC mode:  Flat.  Using 1 I/O APICs
(XEN) Table is not found!
(XEN) Not enabling x2APIC: depends on iommu_supports_eim.
(XEN) Using scheduler: SMP Credit Scheduler (credit)
(XEN) Detected 3292.655 MHz processor.
(XEN) Initing memory sharing.
(XEN) I/O virtualisation disabled
(XEN) Enabled directed EOI with ioapic_ack_old on!
(XEN) ENABLING IO-APIC IRQs
(XEN)  -> Using old ACK method
(XEN) Platform timer is 14.318MHz HPET
(XEN) Allocated console ring of 16 KiB.
(XEN) VMX: Supported advanced features:
(XEN)  - APIC MMIO access virtualisation
(XEN)  - APIC TPR shadow
(XEN)  - Extended Page Tables (EPT)
(XEN)  - Virtual-Processor Identifiers (VPID)
(XEN)  - Virtual NMI
(XEN)  - MSR direct-access bitmap
(XEN)  - Unrestricted Guest
(XEN) EPT supports 2MB super page.
(XEN) HVM: ASIDs enabled.
(XEN) HVM: VMX enabled
(XEN) HVM: Hardware Assisted Paging detected.
(XEN) Brought up 4 CPUs
(XEN) *** LOADING DOMAIN 0 ***
(XEN)  Xen  kernel: 64-bit, lsb, compat32
(XEN)  Dom0 kernel: 64-bit, PAE, lsb, paddr 0x1000000 -> 0x2060000
(XEN) PHYSICAL MEMORY ARRANGEMENT:
(XEN)  Dom0 alloc.:   0000000428000000->0000000430000000 (4049834 pages
to be allocated)
(XEN)  Init. ramdisk: 000000043d6e6000->000000043fdff800
(XEN) VIRTUAL MEMORY ARRANGEMENT:
(XEN)  Loaded kernel: ffffffff81000000->ffffffff82060000
(XEN)  Init. ramdisk: ffffffff82060000->ffffffff84779800
(XEN)  Phys-Mach map: ffffffff8477a000->ffffffff866b3620
(XEN)  Start info:    ffffffff866b4000->ffffffff866b44b4
(XEN)  Page tables:   ffffffff866b5000->ffffffff866ec000
(XEN)  Boot stack:    ffffffff866ec000->ffffffff866ed000
(XEN)  TOTAL:         ffffffff80000000->ffffffff86800000
(XEN)  ENTRY ADDRESS: ffffffff81cfc200
(XEN) Dom0 has maximum 4 VCPUs
(XEN) Scrubbing Free RAM: .done.
(XEN) Xen trace buffers: disabled
(XEN) Std. Loglevel: Errors and warnings
(XEN) Guest Loglevel: Nothing (Rate-limited: Errors and warnings)
(XEN) Xen is relinquishing VGA console.
(XEN) *** Serial input -> DOM0 (type ''CTRL-a'' three times
to switch
input to Xen)
(XEN) Freed 220kB init memory.
(XEN) physdev.c:155: dom0: wrong map_pirq type 3
(XEN) irq.c:1828: dom4: pirq 55 or emuirq 23 already mapped
(XEN) irq.c:1828: dom5: pirq 55 or emuirq 23 already mapped


Sergey Zhukov

On 30/03/2012 13:56, Sergey Zhukov wrote:
> On Fri, 2012-03-30 at 13:07 +0800, Teo En Ming (Zhang Enming) wrote:
>> On 30/03/2012 05:09, Sergey Zhukov wrote:
>>>> 3) When I was installing Ubuntu 12.04 Beta 1 Precise Pangolin
amd64 as
>>>> a HVM domU in either Xen 4.1.3-rc1-pre or Xen 4.2-unstable, it
hanged
>>>> at COPYING FILES during installation. Hence I have to abort the
HVM
>>>> domU installation. Disk I/O performance is very poor.
>>>> 4) Disk I/O performance is very poor with Debian 6.0 Squeeze PV
domU
>>>> in Xen 4.2-unstable and with Fedora 16 x86-64 PV domU in Xen
>>>> 4.1.3-rc1-pre. The mouse cursor movement in both Fedora 16 and
Debian
>>>> 6.0 Squeeze PV domU is very sluggish and unresponsive. It also
takes a
>>>> long time to format filesystems and install packages in PV domU
during
>>>> OS installation. What causes the performance penalty in disk
I/O?
>>>> 5) Disk I/O performance is also very poor with Ubuntu 12.04
Beta 1 HVM
>>>> domU installation. Formatting filesystems and copying files
during
>>>> installation take a long time. Mouse cursor movement is also
very
>>>> unresponsive.
>>> I installed Ubuntu 12.04 beta server (AMD 64) and xen hypervisor
from
>>> ubuntu xen packages (v4.1).
>>> Then I installed Ubuntu 10.04 server as PV DomU and Ubuntu 10.04
desktop
>>> as HVM DomU.
>>> I could not enable IO virtualization, because iommu=1 and
iommu=verbose
>>> parameters seem to be not working.
>> Dear Sergey Zhukou,
>>
>> Thank you very much for your reply.
>>
>> I did not have to specify IOMMU=1 and IOMMU=verbose in my multiboot
>> xen.gz command line in GRUB2. IOMMU is enabled by default in Xen
>> 4.2-unstable.
>>
>> sudo xl dmesg | grep ''I/O Virtualisation''
>>
>> (XEN) I/O Virtualisation Enabled
>>
>>> When I run tests for my specific software I found, that in Ubuntu
10.04
>>> HVM DomU there are too many interrupts when dealing with network.
>>> Processor took about 50%si. I did not test disk IO, but think the
>>> picture should be the same.
>> When I am installing Ubuntu 12.04 Beta 1 HVM domU, the network
>> connection gets disconnected and re-connected many times. Did your
>> installation hanged at copying files while installing Ubuntu 10.04 HVM
domU?
>>
> No, installation has processed smoothly, after 15 minutes I had the
> system installed.
>
>>> But I found solution, which works perfect for me. I installed
Ubuntu
>>> 12.04 desktop beta (i386) as PVHVM DomU. It installed without hangs
and
>>> it works very fast with network and disk.
>> I do not know what is PVHVM, I only know PV domU and HVM domU
separately.
>>
> Just an option xen_platform_pci=''1'' in HVM config file
before
> installation of distributive. There is a wiki
> http://wiki.xen.org/wiki/Xen_Linux_PV_on_HVM_drivers
>
>>> Also, I would like to know, how to enable verbose logs for iommu,
>>> because xm dmesg does not show me any information about VT-d. I
have the
>>> line
>>> (XEN) Command line: placeholder iommu=verbose
>>> in the dmesg logs, but still not got verbose logs...
>> I do not know how to enable verbose logs for IOMMU.
>>
>> Have you tried "sudo xl dmesg | grep VT-d"?
> Yes, that the thing I told about, that I don''t have any lines
about
> VT-d. This is my full log
>
> (XEN) Bootloader: GRUB 1.99-18ubuntu1
> (XEN) Command line: placeholder iommu=verbose
> (XEN) Video information:
> (XEN)  VGA is text mode 80x25, font 8x16
> (XEN)  VBE/DDC methods: none; EDID transfer time: 0 seconds
> (XEN)  EDID info not retrieved because no DDC retrieval method detected
> (XEN) Disc information:
> (XEN)  Found 1 MBR signatures
> (XEN)  Found 1 EDD information structures
> (XEN) Xen-e820 RAM map:
> (XEN)  0000000000000000 - 000000000009ec00 (usable)
> (XEN)  000000000009ec00 - 00000000000a0000 (reserved)
> (XEN)  00000000000e0000 - 0000000000100000 (reserved)
> (XEN)  0000000000100000 - 0000000020000000 (usable)
> (XEN)  0000000020000000 - 0000000020200000 (reserved)
> (XEN)  0000000020200000 - 0000000040000000 (usable)
> (XEN)  0000000040000000 - 0000000040200000 (reserved)
> (XEN)  0000000040200000 - 00000000babc3000 (usable)
> (XEN)  00000000babc3000 - 00000000bac0c000 (ACPI NVS)
> (XEN)  00000000bac0c000 - 00000000bacc4000 (reserved)
> (XEN)  00000000bacc4000 - 00000000baccc000 (ACPI data)
> (XEN)  00000000baccc000 - 00000000bacf3000 (reserved)
> (XEN)  00000000bacf3000 - 00000000bacf5000 (usable)
> (XEN)  00000000bacf5000 - 00000000bad05000 (reserved)
> (XEN)  00000000bad05000 - 00000000bad13000 (ACPI NVS)
> (XEN)  00000000bad13000 - 00000000bad38000 (reserved)
> (XEN)  00000000bad38000 - 00000000bad7b000 (ACPI NVS)
> (XEN)  00000000bad7b000 - 00000000bb000000 (usable)
> (XEN)  00000000bb800000 - 00000000bfa00000 (reserved)
> (XEN)  00000000fed1c000 - 00000000fed40000 (reserved)
> (XEN)  00000000ff000000 - 0000000100000000 (reserved)
> (XEN)  0000000100000000 - 000000043fe00000 (usable)
> (XEN) ACPI: RSDP 000F0450, 0024 (r2 ALASKA)
> (XEN) ACPI: XSDT BACC4070, 005C (r1 ALASKA    A M I  1072009 AMI
> 10013)
> (XEN) ACPI: FACP BACCB4A0, 00F4 (r4 ALASKA    A M I  1072009 AMI
> 10013)
> (XEN) ACPI: DSDT BACC4158, 7348 (r2 ALASKA    A M I       15 INTL
> 20051117)
> (XEN) ACPI: FACS BAD0AF80, 0040
> (XEN) ACPI: APIC BACCB598, 0072 (r3 ALASKA    A M I  1072009 AMI
> 10013)
> (XEN) ACPI: SSDT BACCB610, 0102 (r1 AMICPU     PROC        1 MSFT
> 3000001)
> (XEN) ACPI: MCFG BACCB718, 003C (r1 ALASKA    A M I  1072009 MSFT
> 97)
> (XEN) ACPI: HPET BACCB758, 0038 (r1 ALASKA    A M I  1072009 AMI.
> 4)
> (XEN) ACPI: ASF! BACCB790, 00A0 (r32 INTEL       HCG        1 TFSM
> F4240)
> (XEN) ACPI: BGRT BACCB830, 003C (r0 ALASKA    A M I  1072009 AMI
> 10013)
> (XEN) System RAM: 16295MB (16687008kB)
> (XEN) Domain heap initialised
> (XEN) ACPI: 32/64X FACS address mismatch in FADT -
> bad0af80/0000000000000000, using 32
> (XEN) Processor #0 6:10 APIC version 21
> (XEN) Processor #2 6:10 APIC version 21
> (XEN) Processor #4 6:10 APIC version 21
> (XEN) Processor #6 6:10 APIC version 21
> (XEN) IOAPIC[0]: apic_id 0, version 32, address 0xfec00000, GSI 0-23
> (XEN) Enabling APIC mode:  Flat.  Using 1 I/O APICs
> (XEN) Table is not found!
> (XEN) Not enabling x2APIC: depends on iommu_supports_eim.
> (XEN) Using scheduler: SMP Credit Scheduler (credit)
> (XEN) Detected 3292.655 MHz processor.
> (XEN) Initing memory sharing.
> (XEN) I/O virtualisation disabled
> (XEN) Enabled directed EOI with ioapic_ack_old on!
> (XEN) ENABLING IO-APIC IRQs
> (XEN)  ->  Using old ACK method
> (XEN) Platform timer is 14.318MHz HPET
> (XEN) Allocated console ring of 16 KiB.
> (XEN) VMX: Supported advanced features:
> (XEN)  - APIC MMIO access virtualisation
> (XEN)  - APIC TPR shadow
> (XEN)  - Extended Page Tables (EPT)
> (XEN)  - Virtual-Processor Identifiers (VPID)
> (XEN)  - Virtual NMI
> (XEN)  - MSR direct-access bitmap
> (XEN)  - Unrestricted Guest
> (XEN) EPT supports 2MB super page.
> (XEN) HVM: ASIDs enabled.
> (XEN) HVM: VMX enabled
> (XEN) HVM: Hardware Assisted Paging detected.
> (XEN) Brought up 4 CPUs
> (XEN) *** LOADING DOMAIN 0 ***
> (XEN)  Xen  kernel: 64-bit, lsb, compat32
> (XEN)  Dom0 kernel: 64-bit, PAE, lsb, paddr 0x1000000 ->  0x2060000
> (XEN) PHYSICAL MEMORY ARRANGEMENT:
> (XEN)  Dom0 alloc.:   0000000428000000->0000000430000000 (4049834 pages
> to be allocated)
> (XEN)  Init. ramdisk: 000000043d6e6000->000000043fdff800
> (XEN) VIRTUAL MEMORY ARRANGEMENT:
> (XEN)  Loaded kernel: ffffffff81000000->ffffffff82060000
> (XEN)  Init. ramdisk: ffffffff82060000->ffffffff84779800
> (XEN)  Phys-Mach map: ffffffff8477a000->ffffffff866b3620
> (XEN)  Start info:    ffffffff866b4000->ffffffff866b44b4
> (XEN)  Page tables:   ffffffff866b5000->ffffffff866ec000
> (XEN)  Boot stack:    ffffffff866ec000->ffffffff866ed000
> (XEN)  TOTAL:         ffffffff80000000->ffffffff86800000
> (XEN)  ENTRY ADDRESS: ffffffff81cfc200
> (XEN) Dom0 has maximum 4 VCPUs
> (XEN) Scrubbing Free RAM: .done.
> (XEN) Xen trace buffers: disabled
> (XEN) Std. Loglevel: Errors and warnings
> (XEN) Guest Loglevel: Nothing (Rate-limited: Errors and warnings)
> (XEN) Xen is relinquishing VGA console.
> (XEN) *** Serial input ->  DOM0 (type ''CTRL-a'' three
times to switch
> input to Xen)
> (XEN) Freed 220kB init memory.
> (XEN) physdev.c:155: dom0: wrong map_pirq type 3
> (XEN) irq.c:1828: dom4: pirq 55 or emuirq 23 already mapped
> (XEN) irq.c:1828: dom5: pirq 55 or emuirq 23 already mapped
>
>
> Sergey Zhukov
>
>
>
Dear Sergey Zhukov,

 From the above Xen kernel message logs, it appears that your computer 
hardware does not support VT-d or VT-d was not enabled in your Xen 
installation.

Thank you very much.

-- 
Yours sincerely,

Mr. Teo En Ming (Zhang Enming)
Singapore

On Thu, 2012-03-29 at 18:05 +0100, Teo En Ming (Zhang Enming)
wrote:
> 2) I was NOT able to start Fedora 16 x86-64 Paravirtualized domU in
> Xen 4.2-unstable with xl. The above Youtube video demonstrates it. But
> I was able to start Fedora 16 x86-64 PV domU in Xen 4.1.3-rc1-pre with
> xl. This is clearly a bug. 
I am only going to consider this bug for the time being. We can get to
the others later on. Considering multiple bugs in a single thread simply
leads to confusion.

I''m afraid that I am not going to watch youtube videos in order to find
out the details of a bug though. Please stick to plain text emails.
> I have already provided all the information you guys have requested in
> my previous emails. So why won''t you reply to me?
Often when a user reports a bug it is necessary for a developer to ask
follow up questions in order to get it straight in their head what the
issue is and to ensure that everyone is on the same page with respect to
what the symptoms observed are and what the relevant information about
the bug is. This dialogue is often far more important than the original
bug report in order for a developer to be able to properly understand an
issue and is an important part of the mechanism by which bugs are
understood and fixed.

However this will sometimes mean that a bug reporter is being asked to
repeat information which they have already provided. Sometimes it may
even become necessary to reset the whole process and start again from
first principles, starting from a more specific set of initial
questions. This should not be construed as a criticism of the original
bug report, it is simply sometimes necessary in order for developers to
make progress on a bug.

If a developer asks a follow up question to a bug report then that is
because they are asking for your help because they feel that the answer
to the question will help them to make progress on understanding the bug
and work towards a fix.

Now, with regard to this bug. I read your original email and went
through all the logs which you provided. I was not able to spot anything
which gave me a clue as to what the bug which you described was or to
correlate the contents of the logs which you provided with the
occurrence of that bug. I also tried to reproduce the issue and was
unable to do so. I explained this in
<1332165544.9223.85.camel@zakaz.uk.xensource.com>, and asked you to
please provide a targeted set of logs and the output of the commands
which were failing with some extra debug enabled (which may well repeat
some information already provided) which would help me to better
understand the issue and hopefully provide me with the insight necessary
to understand the bug. Here is what I asked for in that mail:

        Please can you provide a single guest configuration file which
        demonstrates the issue which you are seeing and the output of
        running "xl -vvv create -c <cfg>" for that precisely
that <cfg>
        file. Please also attach exactly
        the /var/log/xen/qemu-dm-<name>.log
        and /var/log/xen/xl-<name>.log produced by exactly that
        invocation of xl.

I am not asking these questions to be difficult or to somehow avoid
fixing the bug, nor am I criticising your original bug report. You can
be sure that if I were able to understand and fix the bug based on the
information you have already provided or by reproducing it myself I
would have done so immediately. I''m afraid that I cannot make any more
progress on this bug without help from someone such as yourself who is
experiencing the issue. I hope you will be willing to provide that
information (yes, this may well mean repeating information which you
have provided before, I am sorry about that).

Ian.

On Fri, 2012-03-30 at 17:03 +0800, Teo En Ming (Zhang Enming)
wrote:
> Dear Sergey Zhukov,
> 
>  From the above Xen kernel message logs, it appears that your computer 
> hardware does not support VT-d or VT-d was not enabled in your Xen 
> installation.
> 
> Thank you very much.
> 

I understand, that something wrong with my installation (hardware or
software). What I want is just to see logs from mmu, to localize the
issue and than resolve it. But I could not enable mmu logs with passing
iommu=verbose as suggested in Xen documentation and don''t know other
ways how to enable them.

I suppose iommu enabled by default in Xen 4.1, so it should write at
least something after I''ve passed iommu=verbose to boot options.

(XEN) Command line: placeholder iommu=verbose

Below are my kernel config options related to MMU and XEN. In my opinion
MMU options are enabled in the kernel, but I am not sure about it.
 
cat /boot/config-3.2.0-19-generic | egrep -i ''xen|mmu''

CONFIG_MMU=y
CONFIG_XEN=y
CONFIG_XEN_DOM0=y
CONFIG_XEN_PRIVILEGED_GUEST=y
CONFIG_XEN_PVHVM=y
CONFIG_XEN_MAX_DOMAIN_MEMORY=128
CONFIG_XEN_SAVE_RESTORE=y
# CONFIG_XEN_DEBUG_FS is not set
CONFIG_GART_IOMMU=y
CONFIG_CALGARY_IOMMU=y
CONFIG_CALGARY_IOMMU_ENABLED_BY_DEFAULT=y
CONFIG_IOMMU_HELPER=y
CONFIG_MMU_NOTIFIER=y
CONFIG_PCI_XEN=y
CONFIG_XEN_PCIDEV_FRONTEND=m
# Near Field Communication (NFC) devices
CONFIG_XEN_BLKDEV_FRONTEND=y
CONFIG_XEN_BLKDEV_BACKEND=m
CONFIG_NETXEN_NIC=m
CONFIG_XEN_NETDEV_FRONTEND=y
CONFIG_XEN_NETDEV_BACKEND=m
CONFIG_INPUT_XEN_KBDDEV_FRONTEND=m
CONFIG_HVC_XEN=y
CONFIG_XEN_WDT=m
CONFIG_XEN_FBDEV_FRONTEND=m
# Xen driver support
CONFIG_XEN_BALLOON=y
CONFIG_XEN_SELFBALLOONING=y
CONFIG_XEN_BALLOON_MEMORY_HOTPLUG=y
CONFIG_XEN_SCRUB_PAGES=y
CONFIG_XEN_DEV_EVTCHN=m
CONFIG_XEN_BACKEND=y
CONFIG_XENFS=m
CONFIG_XEN_COMPAT_XENFS=y
CONFIG_XEN_SYS_HYPERVISOR=y
CONFIG_XEN_XENBUS_FRONTEND=y
CONFIG_XEN_GNTDEV=m
CONFIG_XEN_GRANT_DEV_ALLOC=m
CONFIG_SWIOTLB_XEN=y
CONFIG_XEN_TMEM=y
CONFIG_XEN_PCIDEV_BACKEND=m
CONFIG_IOMMU_API=y
CONFIG_IOMMU_SUPPORT=y
CONFIG_AMD_IOMMU=y
CONFIG_AMD_IOMMU_STATS=y
CONFIG_INTEL_IOMMU=y
# CONFIG_INTEL_IOMMU_DEFAULT_ON is not set
CONFIG_INTEL_IOMMU_FLOPPY_WA=y
# CONFIG_IOMMU_DEBUG is not set
# CONFIG_IOMMU_STRESS is not set
# CONFIG_KVM_MMU_AUDIT is not set


Sergey Zhukov