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

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

[Teo En Ming (Zhang Enming)]

[-- Attachment #1.1: Type: text/plain, Size: 2864 bytes --]

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)





[-- Attachment #1.2: Type: text/html, Size: 14115 bytes --]

[-- Attachment #2: Type: text/plain, Size: 126 bytes --]

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

Re: Cannot Start Linux Paravirtualized (PV) Guests with Xen 4.2-unstable

[Teo En Ming (Zhang Enming)]

[-- Attachment #1.1: Type: text/plain, Size: 3297 bytes --]

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)
>
>
>
>


[-- Attachment #1.2: Type: text/html, Size: 15052 bytes --]

[-- Attachment #2: qemu-dm-Fedora16x86_64.log --]
[-- Type: text/x-log, Size: 404 bytes --]

domid: 20
Warning: vlan 0 is not connected to host network
-videoram option does not work with cirrus vga device model. Videoram set to 4M.
/home/teo-en-ming/xen-unstable.hg/tools/qemu-xen-traditional-dir/hw/xen_blktap.c:628: Init blktap pipes
Could not open /var/run/tap/qemu-read-20
char device redirected to /dev/pts/0
xs_read(): target get error. /local/domain/20/target.
Could not parse VNC address

[-- Attachment #3: qemu-dm-Fedora16x86_64.log.1 --]
[-- Type: text/plain, Size: 376 bytes --]

domid: 19
Warning: vlan 0 is not connected to host network
-videoram option does not work with cirrus vga device model. Videoram set to 4M.
/home/teo-en-ming/xen-unstable.hg/tools/qemu-xen-traditional-dir/hw/xen_blktap.c:628: Init blktap pipes
Could not open /var/run/tap/qemu-read-19
char device redirected to /dev/pts/0
xs_read(): target get error. /local/domain/19/target.

[-- Attachment #4: qemu-dm-Fedora16x86_64.log.2 --]
[-- Type: text/plain, Size: 376 bytes --]

domid: 18
Warning: vlan 0 is not connected to host network
-videoram option does not work with cirrus vga device model. Videoram set to 4M.
/home/teo-en-ming/xen-unstable.hg/tools/qemu-xen-traditional-dir/hw/xen_blktap.c:628: Init blktap pipes
Could not open /var/run/tap/qemu-read-18
char device redirected to /dev/pts/0
xs_read(): target get error. /local/domain/18/target.

[-- Attachment #5: qemu-dm-Fedora16x86_64.log.3 --]
[-- Type: text/plain, Size: 376 bytes --]

domid: 17
Warning: vlan 0 is not connected to host network
-videoram option does not work with cirrus vga device model. Videoram set to 4M.
/home/teo-en-ming/xen-unstable.hg/tools/qemu-xen-traditional-dir/hw/xen_blktap.c:628: Init blktap pipes
Could not open /var/run/tap/qemu-read-17
char device redirected to /dev/pts/0
xs_read(): target get error. /local/domain/17/target.

[-- Attachment #6: qemu-dm-Fedora16x86_64.log.4 --]
[-- Type: text/plain, Size: 376 bytes --]

domid: 16
Warning: vlan 0 is not connected to host network
-videoram option does not work with cirrus vga device model. Videoram set to 4M.
/home/teo-en-ming/xen-unstable.hg/tools/qemu-xen-traditional-dir/hw/xen_blktap.c:628: Init blktap pipes
Could not open /var/run/tap/qemu-read-16
char device redirected to /dev/pts/0
xs_read(): target get error. /local/domain/16/target.

[-- Attachment #7: qemu-dm-Fedora16x86_64.log.5 --]
[-- Type: text/plain, Size: 376 bytes --]

domid: 15
Warning: vlan 0 is not connected to host network
-videoram option does not work with cirrus vga device model. Videoram set to 4M.
/home/teo-en-ming/xen-unstable.hg/tools/qemu-xen-traditional-dir/hw/xen_blktap.c:628: Init blktap pipes
Could not open /var/run/tap/qemu-read-15
char device redirected to /dev/pts/0
xs_read(): target get error. /local/domain/15/target.

[-- Attachment #8: qemu-dm-Fedora16x86_64.log.6 --]
[-- Type: text/plain, Size: 376 bytes --]

domid: 14
Warning: vlan 0 is not connected to host network
-videoram option does not work with cirrus vga device model. Videoram set to 4M.
/home/teo-en-ming/xen-unstable.hg/tools/qemu-xen-traditional-dir/hw/xen_blktap.c:628: Init blktap pipes
Could not open /var/run/tap/qemu-read-14
char device redirected to /dev/pts/0
xs_read(): target get error. /local/domain/14/target.

[-- Attachment #9: qemu-dm-Fedora16x86_64.log.7 --]
[-- Type: text/plain, Size: 376 bytes --]

domid: 13
Warning: vlan 0 is not connected to host network
-videoram option does not work with cirrus vga device model. Videoram set to 4M.
/home/teo-en-ming/xen-unstable.hg/tools/qemu-xen-traditional-dir/hw/xen_blktap.c:628: Init blktap pipes
Could not open /var/run/tap/qemu-read-13
char device redirected to /dev/pts/2
xs_read(): target get error. /local/domain/13/target.

[-- Attachment #10: xl-Fedora16x86_64.log --]
[-- Type: text/x-log, Size: 226 bytes --]

Waiting for domain Fedora16x86_64 (domid 19) to die [pid 10176]
Domain 19 has shut down, reason code 3 0x3
Action for shutdown reason code 3 is destroy
Domain 19 needs to be cleaned up: destroying the domain
Done. Exiting now

[-- Attachment #11: xl-Fedora16x86_64.log.1 --]
[-- Type: text/plain, Size: 225 bytes --]

Waiting for domain Fedora16x86_64 (domid 18) to die [pid 9794]
Domain 18 has shut down, reason code 3 0x3
Action for shutdown reason code 3 is destroy
Domain 18 needs to be cleaned up: destroying the domain
Done. Exiting now

[-- Attachment #12: xl-Fedora16x86_64.log.2 --]
[-- Type: text/plain, Size: 225 bytes --]

Waiting for domain Fedora16x86_64 (domid 17) to die [pid 9476]
Domain 17 has shut down, reason code 3 0x3
Action for shutdown reason code 3 is destroy
Domain 17 needs to be cleaned up: destroying the domain
Done. Exiting now

[-- Attachment #13: xl-Fedora16x86_64.log.3 --]
[-- Type: text/plain, Size: 225 bytes --]

Waiting for domain Fedora16x86_64 (domid 16) to die [pid 9079]
Domain 16 has shut down, reason code 3 0x3
Action for shutdown reason code 3 is destroy
Domain 16 needs to be cleaned up: destroying the domain
Done. Exiting now

[-- Attachment #14: xl-Fedora16x86_64.log.4 --]
[-- Type: text/plain, Size: 225 bytes --]

Waiting for domain Fedora16x86_64 (domid 15) to die [pid 1385]
Domain 15 has shut down, reason code 3 0x3
Action for shutdown reason code 3 is destroy
Domain 15 needs to be cleaned up: destroying the domain
Done. Exiting now

[-- Attachment #15: xl-Fedora16x86_64.log.5 --]
[-- Type: text/plain, Size: 224 bytes --]

Waiting for domain Fedora16x86_64 (domid 14) to die [pid 940]
Domain 14 has shut down, reason code 3 0x3
Action for shutdown reason code 3 is destroy
Domain 14 needs to be cleaned up: destroying the domain
Done. Exiting now

[-- Attachment #16: xl-Fedora16x86_64.log.6 --]
[-- Type: text/plain, Size: 224 bytes --]

Waiting for domain Fedora16x86_64 (domid 13) to die [pid 498]
Domain 13 has shut down, reason code 3 0x3
Action for shutdown reason code 3 is destroy
Domain 13 needs to be cleaned up: destroying the domain
Done. Exiting now

[-- Attachment #17: Type: text/plain, Size: 126 bytes --]

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

Re: Cannot Start Linux Paravirtualized (PV) Guests with Xen 4.2-unstable

[Teo En Ming (Zhang Enming)]

[-- Attachment #1.1: Type: text/plain, Size: 3705 bytes --]

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)
>>
>>
>>
>>
>


[-- Attachment #1.2: Type: text/html, Size: 16178 bytes --]

[-- Attachment #2: Type: text/plain, Size: 126 bytes --]

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

Re: Cannot Start Linux Paravirtualized (PV) Guests with Xen 4.2-unstable

[Fajar A. Nugraha]

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

Re: Cannot Start Linux Paravirtualized (PV) Guests with Xen 4.2-unstable

[Teo En Ming (Zhang Enming)]

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.
>

Re: Cannot Start Linux Paravirtualized (PV) Guests with Xen 4.2-unstable

[Fajar A. Nugraha]

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