qemu-xen-3.4-testing: Fix read-only image file handling

[Well, I did send an e-mail to the list using git but it's not here so I'm forwarding the e-mail to the list for sure:]

Hi,
this is the patch for qemu-xen-3.4-testing to fix the read-only image file handling since the image file was always treated as read-write which means that all the HVM guests were able to write to all the disk images available in domain configuration file no matter what the mode of the image was defined. This patch fixes this functionality to honor the O_RDONLY in the BDRV_O_ACCESS flag in block.c and also fixes the IDE and SCSI interfaces that uses it.

It's been tested on RHEL-5 with xen-3.4-testing version of upstream xen with xen-3.4-testing qemu implementation.

For SCSI devices the DATA PROTECT request sense has been added as found at: http://en.wikipedia.org/wiki/SCSI_Request_Sense_Command

file no matter what the mode of the image was defined. This patch fixes this functionality to honor the O_RDONLY in the BDRV_O_ACCESS flag in block.c and also fixes the IDE and SCSI interfaces that uses it.

It's been tested on RHEL-5 with xen-3.4-testing version of Michal

Signed-off-by Michal Novotny <[email protected]>

_______________________________________________
Xen-devel mailing list
[email protected]
http://lists.xensource.com/xen-devel

Oh, just one more thing that should be mentioned:

When you want to mount an image that is set as read-only in the domain configuration file but you omit to set mode to read-only it results into I/O errors when processing the requests. Remounting as read-only or unmounting and remounting using the mount /dev/* /path/to/mount -o ro shall do the mounting the correct way, i.e. with no I/O errors, so make sure you mount those disks as read-only otherwise you can be getting errors like:

end_request: I/O error, dev hdb, sector 52

Buffer I/O error on device hdb1, logical block 1

lost page write due to I/O error on hdb1

and for IDE devices you'll be getting several additional DeviceFault errors since mounting the device read-write (default setting) writes some data onto a disk at the mount-time.

Michal

Quoted 33 lines · Michal Novotny

[Well, I did send an e-mail to the list using git but it's not here so I'm forwarding the e-mail to the list for sure:]

Hi,
this is the patch for qemu-xen-3.4-testing to fix the read-only image file handling since the image file was always treated as read-write which means that all the HVM guests were able to write to all the disk images available in domain configuration file no matter what the mode of the image was defined. This patch fixes this functionality to honor the O_RDONLY in the BDRV_O_ACCESS flag in block.c and also fixes the IDE and SCSI interfaces that uses it.

It's been tested on RHEL-5 with xen-3.4-testing version of upstream xen with xen-3.4-testing qemu implementation.

For SCSI devices the DATA PROTECT request sense has been added as found at: http://en.wikipedia.org/wiki/SCSI_Request_Sense_Command

file no matter what the mode of the image was defined. This patch fixes this functionality to honor the O_RDONLY in the BDRV_O_ACCESS flag in block.c and also fixes the IDE and SCSI interfaces that uses it.

It's been tested on RHEL-5 with xen-3.4-testing version of Michal

Signed-off-by Michal Novotny <[email protected]>

_______________________________________________
Xen-devel mailing list
[email protected]
http://lists.xensource.com/xen-devel

Oh, one more thing I've discovered now. Since the codebase for qemu-xen-unstable is looking the same like for qemu-xen-3.4-testing and the patch is applicable without any modifications it could be working for xen-4.1 unstable as well, unfortunately I was not able to boot PVOPS kernel since it always ends up in kernel panic, maybe the missing drivers or something like that.

Quoted 60 lines

Oh, just one more thing that should be mentioned:

When you want to mount an image that is set as read-only in the domain configuration file but you omit to set mode to read-only it results into I/O errors when processing the requests. Remounting as read-only or unmounting and remounting using the mount /dev/* /path/to/mount -o ro shall do the mounting the correct way, i.e. with no I/O errors, so make sure you mount those disks as read-only otherwise you can be getting errors like:

end_request: I/O error, dev hdb, sector 52

Buffer I/O error on device hdb1, logical block 1

lost page write due to I/O error on hdb1

and for IDE devices you'll be getting several additional DeviceFault errors since mounting the device read-write (default setting) writes some data onto a disk at the mount-time.

Michal

Quoted 34 lines · Michal Novotny

[Well, I did send an e-mail to the list using git but it's not here so I'm forwarding the e-mail to the list for sure:]

Hi,
this is the patch for qemu-xen-3.4-testing to fix the read-only image file handling since the image file was always treated as read-write which means that all the HVM guests were able to write to all the disk images available in domain configuration file no matter what the mode of the image was defined. This patch fixes this functionality to honor the O_RDONLY in the BDRV_O_ACCESS flag in block.c and also fixes the IDE and SCSI interfaces that uses it.

It's been tested on RHEL-5 with xen-3.4-testing version of upstream xen with xen-3.4-testing qemu implementation.

For SCSI devices the DATA PROTECT request sense has been added as found at: http://en.wikipedia.org/wiki/SCSI_Request_Sense_Command

file no matter what the mode of the image was defined. This patch fixes this functionality to honor the O_RDONLY in the BDRV_O_ACCESS flag in block.c and also fixes the IDE and SCSI interfaces that uses it.

It's been tested on RHEL-5 with xen-3.4-testing version of Michal

Signed-off-by Michal Novotny <[email protected]>

_______________________________________________
Xen-devel mailing list
[email protected]
http://lists.xensource.com/xen-devel

Signature · 8 lines

Michal Novotny<[email protected]>, RHCE
Virtualization Team (xen userspace), Red Hat


_______________________________________________
Xen-devel mailing list
[email protected]
http://lists.xensource.com/xen-devel

Quoted 8 lines · Michal Novotny

Oh, one more thing I've discovered now. Since the codebase for qemu-xen-unstable is looking the same like for qemu-xen-3.4-testing and the patch is applicable without any modifications it could be working for xen-4.1 unstable as well, unfortunately I was not able to boot PVOPS kernel since it always ends up in kernel panic, maybe the missing drivers or something like that.

What kernel version? Did you use xen/stable-2.6.32.x branch from xen.git?

See my example .config files from:
http://wiki.xensource.com/xenwiki/XenParavirtOps in the "troubleshooting" section.

Works on F12/F13 dom0's.

For el5 dom0 you might need these:
http://wiki.xensource.com/xenwiki/2.6.18-to-2.6.31-and-higher

aka
CONFIG_SYSFS_DEPRECATED=y
CONFIG_SYSFS_DEPRECATED_V2=y

Also atm I think you need CONFIG_XEN_XENBUS_FRONTEND=y in the .config
because of the recently added pv-on-hvm drivers (you'll get build failure without that option), so you need XEN_PCIDEV_FRONTEND XEN_BLKDEV_FRONTEND or XEN_NETDEV_FRONTEND or XEN_FBDEV_FRONTEND needs to be =y.

-- Pasi

Quoted 75 lines · Michal Novotny

Quoted 63 lines

Oh, just one more thing that should be mentioned:

When you want to mount an image that is set as read-only in the domain configuration file but you omit to set mode to read-only it results into I/O errors when processing the requests. Remounting as read-only or unmounting and remounting using the mount /dev/* /path/to/mount -o ro shall do the mounting the correct way, i.e. with no I/O errors, so make sure you mount those disks as read-only otherwise you can be getting errors like:

end_request: I/O error, dev hdb, sector 52

Buffer I/O error on device hdb1, logical block 1

lost page write due to I/O error on hdb1

and for IDE devices you'll be getting several additional DeviceFault errors since mounting the device read-write (default setting) writes some data onto a disk at the mount-time.

Michal

Quoted 35 lines · Michal Novotny

[Well, I did send an e-mail to the list using git but it's not here so I'm forwarding the e-mail to the list for sure:]

Hi,
this is the patch for qemu-xen-3.4-testing to fix the read-only image file handling since the image file was always treated as read-write which means that all the HVM guests were able to write to all the disk images available in domain configuration file no matter what the mode of the image was defined. This patch fixes this functionality to honor the O_RDONLY in the BDRV_O_ACCESS flag in block.c and also fixes the IDE and SCSI interfaces that uses it.

It's been tested on RHEL-5 with xen-3.4-testing version of upstream xen with xen-3.4-testing qemu implementation.

For SCSI devices the DATA PROTECT request sense has been added as found at: http://en.wikipedia.org/wiki/SCSI_Request_Sense_Command

file no matter what the mode of the image was defined. This patch fixes this functionality to honor the O_RDONLY in the BDRV_O_ACCESS flag in block.c and also fixes the IDE and SCSI interfaces that uses it.

It's been tested on RHEL-5 with xen-3.4-testing version of Michal

Signed-off-by Michal Novotny<[email protected]>

_______________________________________________
Xen-devel mailing list
[email protected]
http://lists.xensource.com/xen-devel

Signature · 8 lines

Michal Novotny<[email protected]>, RHCE
Virtualization Team (xen userspace), Red Hat


_______________________________________________
Xen-devel mailing list
[email protected]
http://lists.xensource.com/xen-devel

Quoted 9 lines · Pasi Kärkkäinen

Quoted 7 lines · Michal Novotny

Oh, one more thing I've discovered now. Since the codebase for qemu-xen-unstable is looking the same like for qemu-xen-3.4-testing and the patch is applicable without any modifications it could be working for xen-4.1 unstable as well, unfortunately I was not able to boot PVOPS kernel since it always ends up in kernel panic, maybe the missing drivers or something like that.

What kernel version? Did you use xen/stable-2.6.32.x branch from xen.git?

It's the one that's being automatically downloaded from git as linux-2.6-pvops.git. The URL is git://git.kernel.org/pub/scm/linux/kernel/git/jeremy/xen.git with the "fetch" being set to "+refs/heads/*:refs/remotes/xen/*". This is the .git/config automatically created by make world in xen-unstable tree:

[core]
repositoryformatversion = 0
filemode = true
bare = false
logallrefupdates = true
[remote "xen"]
url = git://git.kernel.org/pub/scm/linux/kernel/git/jeremy/xen.git
fetch = +refs/heads/*:refs/remotes/xen/*
[branch "xen/stable-2.6.31.x"]
remote = xen
merge = refs/heads/xen/stable-2.6.31.x

By default it's using uhci-hcd/ehci-hcd and ohci-hcd as builtins but I needed to change it to be modules since otherwise it's being stuck. I'm trying this on RHEL-5 dom0 (I'm having second partition RHEL-5 with upstream xen).

Quoted 2 lines

See my example .config files from:
http://wiki.xensource.com/xenwiki/XenParavirtOps in the "troubleshooting" section.

I'll have a look, thanks for the link.

Quoted 4 lines

Works on F12/F13 dom0's.

For el5 dom0 you might need these:
http://wiki.xensource.com/xenwiki/2.6.18-to-2.6.31-and-higher

Oh, ok, this may be very useful since I'm trying this on RHEL-5. Thanks!

Quoted 8 lines

aka
CONFIG_SYSFS_DEPRECATED=y
CONFIG_SYSFS_DEPRECATED_V2=y

Also atm I think you need CONFIG_XEN_XENBUS_FRONTEND=y in the .config
because of the recently added pv-on-hvm drivers (you'll get build failure without that option), so you need XEN_PCIDEV_FRONTEND XEN_BLKDEV_FRONTEND or XEN_NETDEV_FRONTEND or XEN_FBDEV_FRONTEND needs to be =y.

Great! Thanks for your help Pasi! If anything I'll let you know.

Michal

Quoted 73 lines

-- Pasi

Quoted 70 lines · Michal Novotny

Quoted 59 lines

Oh, just one more thing that should be mentioned:

When you want to mount an image that is set as read-only in the domain configuration file but you omit to set mode to read-only it results into I/O errors when processing the requests. Remounting as read-only or unmounting and remounting using the mount /dev/* /path/to/mount -o ro shall do the mounting the correct way, i.e. with no I/O errors, so make sure you mount those disks as read-only otherwise you can be getting errors like:

end_request: I/O error, dev hdb, sector 52

Buffer I/O error on device hdb1, logical block 1

lost page write due to I/O error on hdb1

and for IDE devices you'll be getting several additional DeviceFault errors since mounting the device read-write (default setting) writes some data onto a disk at the mount-time.

Michal

Quoted 34 lines · Michal Novotny

[Well, I did send an e-mail to the list using git but it's not here so I'm forwarding the e-mail to the list for sure:]

Hi,
this is the patch for qemu-xen-3.4-testing to fix the read-only image file handling since the image file was always treated as read-write which means that all the HVM guests were able to write to all the disk images available in domain configuration file no matter what the mode of the image was defined. This patch fixes this functionality to honor the O_RDONLY in the BDRV_O_ACCESS flag in block.c and also fixes the IDE and SCSI interfaces that uses it.

It's been tested on RHEL-5 with xen-3.4-testing version of upstream xen with xen-3.4-testing qemu implementation.

For SCSI devices the DATA PROTECT request sense has been added as found at: http://en.wikipedia.org/wiki/SCSI_Request_Sense_Command

file no matter what the mode of the image was defined. This patch fixes this functionality to honor the O_RDONLY in the BDRV_O_ACCESS flag in block.c and also fixes the IDE and SCSI interfaces that uses it.

It's been tested on RHEL-5 with xen-3.4-testing version of Michal

Signed-off-by Michal Novotny<[email protected]>

_______________________________________________
Xen-devel mailing list
[email protected]
http://lists.xensource.com/xen-devel

Signature · 8 lines

Michal Novotny<[email protected]>, RHCE
Virtualization Team (xen userspace), Red Hat


_______________________________________________
Xen-devel mailing list
[email protected]
http://lists.xensource.com/xen-devel

Well, now the kernel is booting but when I'm trying to recompile tools and stubdom images it's not OK returning those errors:

...
qemu successfuly configured for Xen qemu-dm build
make -C ioemu-dir install
=== PCI passthrough capability has been enabled ===
make[3]: Entering directory `/home2/shared/xen-unstable.hg/tools/ioemu-remote'
=== PCI passthrough capability has been enabled ===
=== PCI passthrough capability has been enabled ===
make[4]: Entering directory `/home2/shared/xen-unstable.hg/tools/ioemu-remote/i386-dm' CC i386-dm/vl.o /home2/shared/xen-unstable.hg/tools/ioemu-dir/vl.c: In function Œmain¹:
/home2/shared/xen-unstable.hg/tools/ioemu-dir/vl.c:5729: warning:
implicit declaration of function Œdma_helper_init¹ /home2/shared/xen-unstable.hg/tools/ioemu-dir/vl.c:5731: error: too few arguments to function Œxc_interface_open¹
make[4]: *** [vl.o] Error 1
make[4]: Leaving directory `/home2/shared/xen-unstable.hg/tools/ioemu-remote/i386-dm' make[3]: *** [subdir-i386-dm] Error 2
make[3]: Leaving directory `/home2/shared/xen-unstable.hg/tools/ioemu-remote'
make[2]: *** [subdir-install-ioemu-dir] Error 2
make[2]: Leaving directory `/home2/shared/xen-unstable.hg/tools' make[1]: *** [subdirs-install] Error 2
make[1]: Leaving directory `/home2/shared/xen-unstable.hg/tools'
make: *** [install-tools] Error 2
#

The command I used for compilation is make install-xen && make install-tools && make install-stubdom && make install-docs on the latest updated xen-unstable staging mercurial tree so I need to investigate this further. Nevertheless, the dom0 2.6.31.13 is booting on RHEL-5 which is good. That links you gave me Pasi helped, thanks! Now I need to resolve those tools issues.

Michal

Quoted 138 lines · Michal Novotny

Quoted 11 lines · Pasi Kärkkäinen

Quoted 8 lines · Michal Novotny

Oh, one more thing I've discovered now. Since the codebase for qemu-xen-unstable is looking the same like for qemu-xen-3.4-testing and the patch is applicable without any modifications it could be working for xen-4.1 unstable as well, unfortunately I was not able to boot PVOPS
kernel since it always ends up in kernel panic, maybe the missing drivers or something like that.

What kernel version? Did you use xen/stable-2.6.32.x branch from xen.git?

It's the one that's being automatically downloaded from git as linux-2.6-pvops.git. The URL is
git://git.kernel.org/pub/scm/linux/kernel/git/jeremy/xen.git with the "fetch" being set to "+refs/heads/*:refs/remotes/xen/*". This is the .git/config automatically created by make world in xen-unstable tree:

[core]
repositoryformatversion = 0
filemode = true
bare = false
logallrefupdates = true
[remote "xen"]
url = git://git.kernel.org/pub/scm/linux/kernel/git/jeremy/xen.git
fetch = +refs/heads/*:refs/remotes/xen/*
[branch "xen/stable-2.6.31.x"]
remote = xen
merge = refs/heads/xen/stable-2.6.31.x

By default it's using uhci-hcd/ehci-hcd and ohci-hcd as builtins but I needed to change it to be modules since otherwise it's being stuck. I'm trying this on RHEL-5 dom0 (I'm having second partition RHEL-5 with upstream xen).

Quoted 3 lines

See my example .config files from:
http://wiki.xensource.com/xenwiki/XenParavirtOps in the "troubleshooting" section.

I'll have a look, thanks for the link.

Quoted 4 lines

Works on F12/F13 dom0's.

For el5 dom0 you might need these:
http://wiki.xensource.com/xenwiki/2.6.18-to-2.6.31-and-higher

Oh, ok, this may be very useful since I'm trying this on RHEL-5. Thanks!

Quoted 10 lines

aka
CONFIG_SYSFS_DEPRECATED=y
CONFIG_SYSFS_DEPRECATED_V2=y

Also atm I think you need CONFIG_XEN_XENBUS_FRONTEND=y in the .config because of the recently added pv-on-hvm drivers (you'll get build failure without that option),
so you need XEN_PCIDEV_FRONTEND XEN_BLKDEV_FRONTEND or XEN_NETDEV_FRONTEND or XEN_FBDEV_FRONTEND needs to be =y.

Great! Thanks for your help Pasi! If anything I'll let you know.

Michal

Quoted 73 lines

-- Pasi

Quoted 70 lines · Michal Novotny

Quoted 59 lines

Oh, just one more thing that should be mentioned:

When you want to mount an image that is set as read-only in the domain configuration file but you omit to set mode to read-only it results into I/O errors when processing the requests. Remounting as read-only or unmounting and remounting using the mount /dev/* /path/to/mount -o ro shall do the mounting the correct way, i.e. with no I/O errors, so make sure you mount those disks as read-only otherwise you can be getting errors like:

end_request: I/O error, dev hdb, sector 52

Buffer I/O error on device hdb1, logical block 1

lost page write due to I/O error on hdb1

and for IDE devices you'll be getting several additional DeviceFault errors since mounting the device read-write (default setting) writes some data onto a disk at the mount-time.

Michal

Quoted 34 lines · Michal Novotny

[Well, I did send an e-mail to the list using git but it's not here so I'm forwarding the e-mail to the list for sure:]

Hi,
this is the patch for qemu-xen-3.4-testing to fix the read-only image file handling since the image file was always treated as read-write which means that all the HVM guests were able to write to all the disk images available in domain configuration file no matter what the mode of the image was defined. This patch fixes this functionality to honor the O_RDONLY in the BDRV_O_ACCESS flag in block.c and also fixes the IDE and SCSI interfaces that uses it.

It's been tested on RHEL-5 with xen-3.4-testing version of upstream xen with xen-3.4-testing qemu implementation.

For SCSI devices the DATA PROTECT request sense has been added as found at: http://en.wikipedia.org/wiki/SCSI_Request_Sense_Command

file no matter what the mode of the image was defined. This patch fixes this functionality to honor the O_RDONLY in the BDRV_O_ACCESS flag in block.c and also fixes the IDE and SCSI interfaces that uses it.

It's been tested on RHEL-5 with xen-3.4-testing version of Michal

Signed-off-by Michal Novotny<[email protected]>

_______________________________________________
Xen-devel mailing list
[email protected]
http://lists.xensource.com/xen-devel

Signature · 8 lines

Michal Novotny<[email protected]>, RHCE
Virtualization Team (xen userspace), Red Hat


_______________________________________________
Xen-devel mailing list
[email protected]
http://lists.xensource.com/xen-devel

Well, now the kernel is booting but when I'm trying to recompile tools and stubdom images it's not OK returning those errors:

...
qemu successfuly configured for Xen qemu-dm build
make -C ioemu-dir install
=== PCI passthrough capability has been enabled ===
make[3]: Entering directory `/home2/shared/xen-unstable.hg/tools/ioemu-remote'
=== PCI passthrough capability has been enabled ===
=== PCI passthrough capability has been enabled ===
make[4]: Entering directory `/home2/shared/xen-unstable.hg/tools/ioemu-remote/i386-dm' CC i386-dm/vl.o /home2/shared/xen-unstable.hg/tools/ioemu-dir/vl.c: In function ?main?:
/home2/shared/xen-unstable.hg/tools/ioemu-dir/vl.c:5729: warning:
implicit declaration of function ?dma_helper_init? /home2/shared/xen-unstable.hg/tools/ioemu-dir/vl.c:5731: error: too few arguments to function ?xc_interface_open?
make[4]: *** [vl.o] Error 1
make[4]: Leaving directory `/home2/shared/xen-unstable.hg/tools/ioemu-remote/i386-dm' make[3]: *** [subdir-i386-dm] Error 2
make[3]: Leaving directory `/home2/shared/xen-unstable.hg/tools/ioemu-remote'
make[2]: *** [subdir-install-ioemu-dir] Error 2
make[2]: Leaving directory `/home2/shared/xen-unstable.hg/tools' make[1]: *** [subdirs-install] Error 2
make[1]: Leaving directory `/home2/shared/xen-unstable.hg/tools'
make: *** [install-tools] Error 2
#

The command I used for compilation is make install-xen && make install-tools && make install-stubdom && make install-docs on the latest updated xen-unstable staging mercurial tree so I need to investigate this further. Nevertheless, the dom0 2.6.31.13 is booting on RHEL-5 which is good. That links you gave me Pasi helped, thanks! Now I need to resolve those tools issues.

Michal

Quoted 138 lines · Michal Novotny

Quoted 11 lines · Pasi Kärkkäinen

Quoted 8 lines · Michal Novotny

Oh, one more thing I've discovered now. Since the codebase for qemu-xen-unstable is looking the same like for qemu-xen-3.4-testing and the patch is applicable without any modifications it could be working for xen-4.1 unstable as well, unfortunately I was not able to boot PVOPS
kernel since it always ends up in kernel panic, maybe the missing drivers or something like that.

What kernel version? Did you use xen/stable-2.6.32.x branch from xen.git?

It's the one that's being automatically downloaded from git as linux-2.6-pvops.git. The URL is
git://git.kernel.org/pub/scm/linux/kernel/git/jeremy/xen.git with the "fetch" being set to "+refs/heads/*:refs/remotes/xen/*". This is the .git/config automatically created by make world in xen-unstable tree:

[core]
repositoryformatversion = 0
filemode = true
bare = false
logallrefupdates = true
[remote "xen"]
url = git://git.kernel.org/pub/scm/linux/kernel/git/jeremy/xen.git
fetch = +refs/heads/*:refs/remotes/xen/*
[branch "xen/stable-2.6.31.x"]
remote = xen
merge = refs/heads/xen/stable-2.6.31.x

By default it's using uhci-hcd/ehci-hcd and ohci-hcd as builtins but I needed to change it to be modules since otherwise it's being stuck. I'm trying this on RHEL-5 dom0 (I'm having second partition RHEL-5 with upstream xen).

Quoted 3 lines

See my example .config files from:
http://wiki.xensource.com/xenwiki/XenParavirtOps in the "troubleshooting" section.

I'll have a look, thanks for the link.

Quoted 4 lines

Works on F12/F13 dom0's.

For el5 dom0 you might need these:
http://wiki.xensource.com/xenwiki/2.6.18-to-2.6.31-and-higher

Oh, ok, this may be very useful since I'm trying this on RHEL-5. Thanks!

Quoted 10 lines

aka
CONFIG_SYSFS_DEPRECATED=y
CONFIG_SYSFS_DEPRECATED_V2=y

Also atm I think you need CONFIG_XEN_XENBUS_FRONTEND=y in the .config because of the recently added pv-on-hvm drivers (you'll get build failure without that option),
so you need XEN_PCIDEV_FRONTEND XEN_BLKDEV_FRONTEND or XEN_NETDEV_FRONTEND or XEN_FBDEV_FRONTEND needs to be =y.

Great! Thanks for your help Pasi! If anything I'll let you know.

Michal

Quoted 73 lines

-- Pasi

Quoted 70 lines · Michal Novotny

Quoted 59 lines

Oh, just one more thing that should be mentioned:

When you want to mount an image that is set as read-only in the domain configuration file but you omit to set mode to read-only it results into I/O errors when processing the requests. Remounting as read-only or unmounting and remounting using the mount /dev/* /path/to/mount -o ro shall do the mounting the correct way, i.e. with no I/O errors, so make sure you mount those disks as read-only otherwise you can be getting errors like:

end_request: I/O error, dev hdb, sector 52

Buffer I/O error on device hdb1, logical block 1

lost page write due to I/O error on hdb1

and for IDE devices you'll be getting several additional DeviceFault errors since mounting the device read-write (default setting) writes some data onto a disk at the mount-time.

Michal

Quoted 34 lines · Michal Novotny

[Well, I did send an e-mail to the list using git but it's not here so I'm forwarding the e-mail to the list for sure:]

Hi,
this is the patch for qemu-xen-3.4-testing to fix the read-only image file handling since the image file was always treated as read-write which means that all the HVM guests were able to write to all the disk images available in domain configuration file no matter what the mode of the image was defined. This patch fixes this functionality to honor the O_RDONLY in the BDRV_O_ACCESS flag in block.c and also fixes the IDE and SCSI interfaces that uses it.

It's been tested on RHEL-5 with xen-3.4-testing version of upstream xen with xen-3.4-testing qemu implementation.

For SCSI devices the DATA PROTECT request sense has been added as found at: http://en.wikipedia.org/wiki/SCSI_Request_Sense_Command

file no matter what the mode of the image was defined. This patch fixes this functionality to honor the O_RDONLY in the BDRV_O_ACCESS flag in block.c and also fixes the IDE and SCSI interfaces that uses it.

It's been tested on RHEL-5 with xen-3.4-testing version of Michal

Signed-off-by Michal Novotny<[email protected]>

_______________________________________________
Xen-devel mailing list
[email protected]
http://lists.xensource.com/xen-devel

Signature · 8 lines

Michal Novotny<[email protected]>, RHCE
Virtualization Team (xen userspace), Red Hat


_______________________________________________
Xen-devel mailing list
[email protected]
http://lists.xensource.com/xen-devel

Signature · 2 lines

Michal Novotny<[email protected]>, RHCE
Virtualization Team (xen userspace), Red Hat

Quoted 8 lines · Michal Novotny

Oh, one more thing I've discovered now. Since the codebase for qemu-xen-unstable is looking the same like for qemu-xen-3.4-testing and the patch is applicable without any modifications it could be working for xen-4.1 unstable as well, unfortunately I was not able to boot PVOPS kernel since it always ends up in kernel panic, maybe the missing drivers or something like that.

What kernel version? Did you use xen/stable-2.6.32.x branch from xen.git?

See my example .config files from:
http://wiki.xensource.com/xenwiki/XenParavirtOps in the "troubleshooting" section.

Works on F12/F13 dom0's.

For el5 dom0 you might need these:
http://wiki.xensource.com/xenwiki/2.6.18-to-2.6.31-and-higher

aka
CONFIG_SYSFS_DEPRECATED=y
CONFIG_SYSFS_DEPRECATED_V2=y

Also atm I think you need CONFIG_XEN_XENBUS_FRONTEND=y in the .config
because of the recently added pv-on-hvm drivers (you'll get build failure without that option), so you need XEN_PCIDEV_FRONTEND XEN_BLKDEV_FRONTEND or XEN_NETDEV_FRONTEND or XEN_FBDEV_FRONTEND needs to be =y.

-- Pasi

Quoted 75 lines · Michal Novotny

Quoted 63 lines

Oh, just one more thing that should be mentioned:

When you want to mount an image that is set as read-only in the domain configuration file but you omit to set mode to read-only it results into I/O errors when processing the requests. Remounting as read-only or unmounting and remounting using the mount /dev/* /path/to/mount -o ro shall do the mounting the correct way, i.e. with no I/O errors, so make sure you mount those disks as read-only otherwise you can be getting errors like:

end_request: I/O error, dev hdb, sector 52

Buffer I/O error on device hdb1, logical block 1

lost page write due to I/O error on hdb1

and for IDE devices you'll be getting several additional DeviceFault errors since mounting the device read-write (default setting) writes some data onto a disk at the mount-time.

Michal

Quoted 35 lines · Michal Novotny

[Well, I did send an e-mail to the list using git but it's not here so I'm forwarding the e-mail to the list for sure:]

Hi,
this is the patch for qemu-xen-3.4-testing to fix the read-only image file handling since the image file was always treated as read-write which means that all the HVM guests were able to write to all the disk images available in domain configuration file no matter what the mode of the image was defined. This patch fixes this functionality to honor the O_RDONLY in the BDRV_O_ACCESS flag in block.c and also fixes the IDE and SCSI interfaces that uses it.

It's been tested on RHEL-5 with xen-3.4-testing version of upstream xen with xen-3.4-testing qemu implementation.

For SCSI devices the DATA PROTECT request sense has been added as found at: http://en.wikipedia.org/wiki/SCSI_Request_Sense_Command

file no matter what the mode of the image was defined. This patch fixes this functionality to honor the O_RDONLY in the BDRV_O_ACCESS flag in block.c and also fixes the IDE and SCSI interfaces that uses it.

It's been tested on RHEL-5 with xen-3.4-testing version of Michal

Signed-off-by Michal Novotny<[email protected]>

_______________________________________________
Xen-devel mailing list
[email protected]
http://lists.xensource.com/xen-devel

Signature · 8 lines

Michal Novotny<[email protected]>, RHCE
Virtualization Team (xen userspace), Red Hat


_______________________________________________
Xen-devel mailing list
[email protected]
http://lists.xensource.com/xen-devel

"/usr/lib64/python2.4/site-packages/xen/xend/xenstore/xsutil.py", line 18, in xshandle
xs_handle = xen.lowlevel.xs.xs()
Error: (111, 'Connection refused')

Any guess what may be going wrong?

Quoted 5 lines · Michal Novotny

"/usr/lib64/python2.4/site-packages/xen/xend/xenstore/xsutil.py", line 18, in xshandle
xs_handle = xen.lowlevel.xs.xs()
Error: (111, 'Connection refused')

Quoted 2 lines

Any guess what may be going wrong?

Xenstored not running, or refusing connections for some other reason?

-- Keir

Quoted 10 lines · Keir Fraser

Quoted 7 lines · Michal Novotny

"/usr/lib64/python2.4/site-packages/xen/xend/xenstore/xsutil.py", line 18, in xshandle
xs_handle = xen.lowlevel.xs.xs()
Error: (111, 'Connection refused')

Any guess what may be going wrong?

Quoted 6 lines

Xenstored not running, or refusing connections for some other reason?

-- Keir

Not running and refusing to run: FATAL: Failed to open evtchn device: No such file or directory

Quoted 10 lines · Keir Fraser

Quoted 7 lines · Michal Novotny

"/usr/lib64/python2.4/site-packages/xen/xend/xenstore/xsutil.py", line 18, in xshandle
xs_handle = xen.lowlevel.xs.xs()
Error: (111, 'Connection refused')

Any guess what may be going wrong?

Quoted 6 lines

Xenstored not running, or refusing connections for some other reason?

-- Keir

Not running and refusing to run: FATAL: Failed to open evtchn device:
No such file or directory

Well, I'm still having some tools issues, mainly:

Error: (111, 'Connection refused')

Any guess what may be going wrong? Booted grub entry:

title Red Hat Enterprise Linux Server (2.6.31.13-xen HV, nolog)

        root (hd1,6)
        kernel /xen-4.1-unstable.gz
        module /vmlinuz-2.6.31.13 ro root=LABEL=/rhel2 rhgb quiet selinux=0
        module /initrd-2.6.31.13.img

Mount is having xenfs on /proc/xen type xenfs (rw). Any guess what may be going wrong?

Thanks,
Michal

Quoted 107 lines · Pasi Kärkkäinen

Quoted 8 lines · Michal Novotny

Oh, one more thing I've discovered now. Since the codebase for qemu-xen-unstable is looking the same like for qemu-xen-3.4-testing and the patch is applicable without any modifications it could be working for xen-4.1 unstable as well, unfortunately I was not able to boot PVOPS kernel since it always ends up in kernel panic, maybe the missing drivers or something like that.

What kernel version? Did you use xen/stable-2.6.32.x branch from xen.git?

See my example .config files from:
http://wiki.xensource.com/xenwiki/XenParavirtOps in the "troubleshooting" section.

Works on F12/F13 dom0's.

For el5 dom0 you might need these:
http://wiki.xensource.com/xenwiki/2.6.18-to-2.6.31-and-higher

aka
CONFIG_SYSFS_DEPRECATED=y
CONFIG_SYSFS_DEPRECATED_V2=y

Also atm I think you need CONFIG_XEN_XENBUS_FRONTEND=y in the .config
because of the recently added pv-on-hvm drivers (you'll get build failure without that option), so you need XEN_PCIDEV_FRONTEND XEN_BLKDEV_FRONTEND or XEN_NETDEV_FRONTEND or XEN_FBDEV_FRONTEND needs to be =y.

-- Pasi

Quoted 75 lines · Michal Novotny

Quoted 63 lines

Oh, just one more thing that should be mentioned:

When you want to mount an image that is set as read-only in the domain configuration file but you omit to set mode to read-only it results into I/O errors when processing the requests. Remounting as read-only or unmounting and remounting using the mount /dev/* /path/to/mount -o ro shall do the mounting the correct way, i.e. with no I/O errors, so make sure you mount those disks as read-only otherwise you can be getting errors like:

end_request: I/O error, dev hdb, sector 52

Buffer I/O error on device hdb1, logical block 1

lost page write due to I/O error on hdb1

and for IDE devices you'll be getting several additional DeviceFault errors since mounting the device read-write (default setting) writes some data onto a disk at the mount-time.

Michal

Quoted 35 lines · Michal Novotny

[Well, I did send an e-mail to the list using git but it's not here so I'm forwarding the e-mail to the list for sure:]

Hi,
this is the patch for qemu-xen-3.4-testing to fix the read-only image file handling since the image file was always treated as read-write which means that all the HVM guests were able to write to all the disk images available in domain configuration file no matter what the mode of the image was defined. This patch fixes this functionality to honor the O_RDONLY in the BDRV_O_ACCESS flag in block.c and also fixes the IDE and SCSI interfaces that uses it.

It's been tested on RHEL-5 with xen-3.4-testing version of upstream xen with xen-3.4-testing qemu implementation.

For SCSI devices the DATA PROTECT request sense has been added as found at: http://en.wikipedia.org/wiki/SCSI_Request_Sense_Command

file no matter what the mode of the image was defined. This patch fixes this functionality to honor the O_RDONLY in the BDRV_O_ACCESS flag in block.c and also fixes the IDE and SCSI interfaces that uses it.

It's been tested on RHEL-5 with xen-3.4-testing version of Michal

Signed-off-by Michal Novotny<[email protected]>

_______________________________________________
Xen-devel mailing list
[email protected]
http://lists.xensource.com/xen-devel

Signature · 8 lines

Michal Novotny<[email protected]>, RHCE
Virtualization Team (xen userspace), Red Hat


_______________________________________________
Xen-devel mailing list
[email protected]
http://lists.xensource.com/xen-devel

Signature · 2 lines

Michal Novotny<[email protected]>, RHCE
Virtualization Team (xen userspace), Red Hat

Quoted 6 lines · Michal Novotny

Well, I'm still having some tools issues, mainly:

Error: (111, 'Connection refused')

Any guess what may be going wrong? Booted grub entry:

Quoted 10 lines

title Red Hat Enterprise Linux Server (2.6.31.13-xen HV, nolog)

         root (hd1,6)
         kernel /xen-4.1-unstable.gz
         module /vmlinuz-2.6.31.13 ro root=LABEL=/rhel2 rhgb quiet selinux=0
         module /initrd-2.6.31.13.img

Mount is having xenfs on /proc/xen type xenfs (rw). Any guess what may be going wrong?

Do you have xen-evtchn driver loaded?

-- Pasi

Quoted 113 lines

Thanks,
Michal

Quoted 107 lines · Pasi Kärkkäinen

Quoted 9 lines · Michal Novotny

Oh, one more thing I've discovered now. Since the codebase for qemu-xen-unstable is looking the same like for qemu-xen-3.4-testing and the patch is applicable without any modifications it could be working for xen-4.1 unstable as well, unfortunately I was not able to boot PVOPS kernel since it always ends up in kernel panic, maybe the missing drivers or something like that.

What kernel version? Did you use xen/stable-2.6.32.x branch from xen.git?

See my example .config files from:
http://wiki.xensource.com/xenwiki/XenParavirtOps in the "troubleshooting" section.

Works on F12/F13 dom0's.

For el5 dom0 you might need these:
http://wiki.xensource.com/xenwiki/2.6.18-to-2.6.31-and-higher

aka
CONFIG_SYSFS_DEPRECATED=y
CONFIG_SYSFS_DEPRECATED_V2=y

Also atm I think you need CONFIG_XEN_XENBUS_FRONTEND=y in the .config
because of the recently added pv-on-hvm drivers (you'll get build failure without that option), so you need XEN_PCIDEV_FRONTEND XEN_BLKDEV_FRONTEND or XEN_NETDEV_FRONTEND or XEN_FBDEV_FRONTEND needs to be =y.

-- Pasi

Quoted 72 lines · Michal Novotny

Quoted 66 lines

Oh, just one more thing that should be mentioned:

When you want to mount an image that is set as read-only in the domain configuration file but you omit to set mode to read-only it results into I/O errors when processing the requests. Remounting as read-only or unmounting and remounting using the mount /dev/* /path/to/mount -o ro shall do the mounting the correct way, i.e. with no I/O errors, so make sure you mount those disks as read-only otherwise you can be getting errors like:

end_request: I/O error, dev hdb, sector 52

Buffer I/O error on device hdb1, logical block 1

lost page write due to I/O error on hdb1

and for IDE devices you'll be getting several additional DeviceFault errors since mounting the device read-write (default setting) writes some data onto a disk at the mount-time.

Michal

Quoted 36 lines · Michal Novotny

[Well, I did send an e-mail to the list using git but it's not here so I'm forwarding the e-mail to the list for sure:]

Hi,
this is the patch for qemu-xen-3.4-testing to fix the read-only image file handling since the image file was always treated as read-write which means that all the HVM guests were able to write to all the disk images available in domain configuration file no matter what the mode of the image was defined. This patch fixes this functionality to honor the O_RDONLY in the BDRV_O_ACCESS flag in block.c and also fixes the IDE and SCSI interfaces that uses it.

It's been tested on RHEL-5 with xen-3.4-testing version of upstream xen with xen-3.4-testing qemu implementation.

For SCSI devices the DATA PROTECT request sense has been added as found at: http://en.wikipedia.org/wiki/SCSI_Request_Sense_Command

file no matter what the mode of the image was defined. This patch fixes this functionality to honor the O_RDONLY in the BDRV_O_ACCESS flag in block.c and also fixes the IDE and SCSI interfaces that uses it.

It's been tested on RHEL-5 with xen-3.4-testing version of Michal

Signed-off-by Michal Novotny<[email protected]>

_______________________________________________
Xen-devel mailing list
[email protected]
http://lists.xensource.com/xen-devel

Signature · 2 lines

Michal Novotny<[email protected]>, RHCE
Virtualization Team (xen userspace), Red Hat

Quoted 12 lines

Quoted 6 lines

Quoted 6 lines

_______________________________________________
Xen-devel mailing list
[email protected]
http://lists.xensource.com/xen-devel

Signature · 2 lines

Michal Novotny<[email protected]>, RHCE
Virtualization Team (xen userspace), Red Hat

_______________________________________________
Xen-devel mailing list
[email protected]
http://lists.xensource.com/xen-devel

Quoted 14 lines · Pasi Kärkkäinen

Quoted 13 lines · Michal Novotny

Well, I'm still having some tools issues, mainly:

Error: (111, 'Connection refused')

Any guess what may be going wrong? Booted grub entry:

title Red Hat Enterprise Linux Server (2.6.31.13-xen HV, nolog)

         root (hd1,6)
         kernel /xen-4.1-unstable.gz
         module /vmlinuz-2.6.31.13 ro root=LABEL=/rhel2 rhgb quiet 
selinux=0
         module /initrd-2.6.31.13.img

Quoted 9 lines

Quoted 3 lines

Mount is having xenfs on /proc/xen type xenfs (rw). Any guess what may be going wrong?

Do you have xen-evtchn driver loaded?

-- Pasi

Well, no, and doesn't seem to be installed/probed:

# modprobe xen-evtchn
# lsmod | grep xen-evtchn
#

So there's the problem :(

Michal

Quoted 119 lines

Quoted 105 lines

Thanks,
Michal

Quoted 100 lines · Pasi Kärkkäinen

Quoted 8 lines · Michal Novotny

Oh, one more thing I've discovered now. Since the codebase for qemu-xen-unstable is looking the same like for qemu-xen-3.4-testing and the patch is applicable without any modifications it could be working for xen-4.1 unstable as well, unfortunately I was not able to boot PVOPS kernel since it always ends up in kernel panic, maybe the missing drivers or something like that.

What kernel version? Did you use xen/stable-2.6.32.x branch from xen.git?

See my example .config files from:
http://wiki.xensource.com/xenwiki/XenParavirtOps in the "troubleshooting" section.

Works on F12/F13 dom0's.

For el5 dom0 you might need these:
http://wiki.xensource.com/xenwiki/2.6.18-to-2.6.31-and-higher

aka
CONFIG_SYSFS_DEPRECATED=y
CONFIG_SYSFS_DEPRECATED_V2=y

Also atm I think you need CONFIG_XEN_XENBUS_FRONTEND=y in the .config
because of the recently added pv-on-hvm drivers (you'll get build failure without that option), so you need XEN_PCIDEV_FRONTEND XEN_BLKDEV_FRONTEND or XEN_NETDEV_FRONTEND or XEN_FBDEV_FRONTEND needs to be =y.

-- Pasi

Quoted 68 lines · Michal Novotny

Quoted 62 lines

Oh, just one more thing that should be mentioned:

When you want to mount an image that is set as read-only in the domain configuration file but you omit to set mode to read-only it results into I/O errors when processing the requests. Remounting as read-only or unmounting and remounting using the mount /dev/* /path/to/mount -o ro shall do the mounting the correct way, i.e. with no I/O errors, so make sure you mount those disks as read-only otherwise you can be getting errors like:

end_request: I/O error, dev hdb, sector 52

Buffer I/O error on device hdb1, logical block 1

lost page write due to I/O error on hdb1

and for IDE devices you'll be getting several additional DeviceFault errors since mounting the device read-write (default setting) writes some data onto a disk at the mount-time.

Michal

Quoted 35 lines · Michal Novotny

[Well, I did send an e-mail to the list using git but it's not here so I'm forwarding the e-mail to the list for sure:]

Hi,
this is the patch for qemu-xen-3.4-testing to fix the read-only image file handling since the image file was always treated as read-write which means that all the HVM guests were able to write to all the disk images available in domain configuration file no matter what the mode of the image was defined. This patch fixes this functionality to honor the O_RDONLY in the BDRV_O_ACCESS flag in block.c and also fixes the IDE and SCSI interfaces that uses it.

It's been tested on RHEL-5 with xen-3.4-testing version of upstream xen with xen-3.4-testing qemu implementation.

For SCSI devices the DATA PROTECT request sense has been added as found at: http://en.wikipedia.org/wiki/SCSI_Request_Sense_Command

file no matter what the mode of the image was defined. This patch fixes this functionality to honor the O_RDONLY in the BDRV_O_ACCESS flag in block.c and also fixes the IDE and SCSI interfaces that uses it.

It's been tested on RHEL-5 with xen-3.4-testing version of Michal

Signed-off-by Michal Novotny<[email protected]>

_______________________________________________
Xen-devel mailing list
[email protected]
http://lists.xensource.com/xen-devel

Signature · 2 lines

Michal Novotny<[email protected]>, RHCE
Virtualization Team (xen userspace), Red Hat

Quoted 10 lines

Quoted 5 lines

Quoted 5 lines

_______________________________________________
Xen-devel mailing list
[email protected]
http://lists.xensource.com/xen-devel

Signature · 2 lines

Michal Novotny<[email protected]>, RHCE
Virtualization Team (xen userspace), Red Hat

_______________________________________________
Xen-devel mailing list
[email protected]
http://lists.xensource.com/xen-devel

Quoted 28 lines · Michal Novotny

Quoted 19 lines · Pasi Kärkkäinen

Quoted 13 lines · Michal Novotny

Well, I'm still having some tools issues, mainly:

Error: (111, 'Connection refused')

Any guess what may be going wrong? Booted grub entry:

title Red Hat Enterprise Linux Server (2.6.31.13-xen HV, nolog)

         root (hd1,6)
         kernel /xen-4.1-unstable.gz
         module /vmlinuz-2.6.31.13 ro root=LABEL=/rhel2 rhgb quiet  
selinux=0
         module /initrd-2.6.31.13.img

Quoted 4 lines

Mount is having xenfs on /proc/xen type xenfs (rw). Any guess what may
be going wrong?

Quoted 5 lines

Do you have xen-evtchn driver loaded?

-- Pasi

Well, no, and doesn't seem to be installed/probed:

Quoted 7 lines

# modprobe xen-evtchn
# lsmod | grep xen-evtchn
#

So there's the problem :(

Michal

Oh, I'm taking this back since I found out the module is not xen-evtchn but xen_evtchn. So yeah, I'm having it loaded in the memory now. However, when I do service xend restart the same error is here:

[2010-06-07 17:14:09 5635] INFO (SrvDaemon:227) Xend stopped due to signal 15.
[2010-06-07 17:14:09 6295] INFO (SrvDaemon:332) Xend Daemon started [2010-06-07 17:14:09 6295] INFO (SrvDaemon:336) Xend changeset: Thu May 20 17:22:15 2010 +0100 21442:a7fcf2e35d32.
[2010-06-07 17:14:09 6295] DEBUG (tcp:96) Listening on :8002 [2010-06-07 17:14:09 6295] INFO (XendNetwork:114) Not recreating missing unmanaged network eth0
[2010-06-07 17:14:09 6295] INFO (XendNetwork:114) Not recreating missing unmanaged network eth2
[2010-06-07 17:14:09 6295] INFO (XendNetwork:114) Not recreating missing unmanaged network br0
[2010-06-07 17:14:09 6295] INFO (XendNetwork:114) Not recreating missing unmanaged network xenbr0
[2010-06-07 17:14:10 6295] DEBUG (XendCPUPool:747) recreate_active_pools [2010-06-07 17:14:10 6295] ERROR (SrvDaemon:349) Exception starting xend ((111, 'Connection refused'))
Traceback (most recent call last):
File
"/usr/lib64/python2.4/site-packages/xen/xend/server/SrvDaemon.py", line 341, in run
servers = SrvServer.create()
File
"/usr/lib64/python2.4/site-packages/xen/xend/server/SrvServer.py", line 258, in create
root.putChild('xend', SrvRoot())
File "/usr/lib64/python2.4/site-packages/xen/xend/server/SrvRoot.py",
line 40, in __init__
self.get(name)
File "/usr/lib64/python2.4/site-packages/xen/web/SrvDir.py", line 84,
in get
val = val.getobj()
File "/usr/lib64/python2.4/site-packages/xen/web/SrvDir.py", line 52,
in getobj
self.obj = klassobj()
File "/usr/lib64/python2.4/site-packages/xen/xend/server/SrvNode.py",
line 30, in __init__
self.xn = XendNode.instance()
File "/usr/lib64/python2.4/site-packages/xen/xend/XendNode.py", line
1176, in instance
inst = XendNode()
File "/usr/lib64/python2.4/site-packages/xen/xend/XendNode.py", line
163, in __init__

    self._init_cpu_pools()

File "/usr/lib64/python2.4/site-packages/xen/xend/XendNode.py", line
377, in _init_cpu_pools
XendCPUPool.recreate_active_pools()
File "/usr/lib64/python2.4/site-packages/xen/xend/XendCPUPool.py",
line 754, in recreate_active_pools
uuid = xstransact.Read(path, 'uuid')
File
"/usr/lib64/python2.4/site-packages/xen/xend/xenstore/xstransact.py", line 307, in Read
return complete(path, lambda t: t.read(*args))
File
"/usr/lib64/python2.4/site-packages/xen/xend/xenstore/xstransact.py", line 361, in complete
t = xstransact(path)
File
"/usr/lib64/python2.4/site-packages/xen/xend/xenstore/xstransact.py", line 29, in __init__
self.transaction = xshandle().transaction_start()
File "/usr/lib64/python2.4/site-packages/xen/xend/xenstore/xsutil.py",
line 18, in xshandle
xs_handle = xen.lowlevel.xs.xs()
Error: (111, 'Connection refused')

Any ideas?

Michal

Quoted 132 lines

Quoted 130 lines

Quoted 116 lines

Thanks,
Michal

Quoted 111 lines · Pasi Kärkkäinen

Quoted 10 lines · Michal Novotny

Oh, one more thing I've discovered now. Since the codebase for qemu-xen-unstable is looking the same like for qemu-xen-3.4-testing and
the patch is applicable without any modifications it could be working for xen-4.1 unstable as well, unfortunately I was not able to boot PVOPS
kernel since it always ends up in kernel panic, maybe the missing drivers or something like that.

What kernel version? Did you use xen/stable-2.6.32.x branch from xen.git?

See my example .config files from:
http://wiki.xensource.com/xenwiki/XenParavirtOps in the "troubleshooting" section.

Works on F12/F13 dom0's.

For el5 dom0 you might need these:
http://wiki.xensource.com/xenwiki/2.6.18-to-2.6.31-and-higher

aka
CONFIG_SYSFS_DEPRECATED=y
CONFIG_SYSFS_DEPRECATED_V2=y

Also atm I think you need CONFIG_XEN_XENBUS_FRONTEND=y in the .config because of the recently added pv-on-hvm drivers (you'll get build failure without that option),
so you need XEN_PCIDEV_FRONTEND XEN_BLKDEV_FRONTEND or XEN_NETDEV_FRONTEND or XEN_FBDEV_FRONTEND needs to be =y.

-- Pasi

Quoted 73 lines · Michal Novotny

Quoted 67 lines

Oh, just one more thing that should be mentioned:

When you want to mount an image that is set as read-only in the domain
configuration file but you omit to set mode to read-only it results into I/O errors when processing the requests. Remounting as read-only
or unmounting and remounting using the `mount /dev/* /path/to/mount -o
ro` shall do the mounting the correct way, i.e. with no I/O errors, so
make sure you mount those disks as read-only otherwise you can be getting errors like:

end_request: I/O error, dev hdb, sector 52

Buffer I/O error on device hdb1, logical block 1

lost page write due to I/O error on hdb1

and for IDE devices you'll be getting several additional DeviceFault errors since mounting the device read-write (default setting) writes some data onto a disk at the mount-time.

Michal

Quoted 36 lines · Michal Novotny

[Well, I did send an e-mail to the list using git but it's not here so I'm forwarding the e-mail to the list for sure:]

Hi,
this is the patch for qemu-xen-3.4-testing to fix the read-only image file handling since the image file was always treated as read-write which means that all the HVM guests were able to write to all the disk images available in domain configuration file no matter what the mode of the image was defined. This patch fixes this functionality to honor the O_RDONLY in the BDRV_O_ACCESS flag in block.c and also fixes the IDE and SCSI interfaces that uses it.

It's been tested on RHEL-5 with xen-3.4-testing version of upstream xen with xen-3.4-testing qemu implementation.

For SCSI devices the DATA PROTECT request sense has been added as found at:
http://en.wikipedia.org/wiki/SCSI_Request_Sense_Command

file no matter what the mode of the image was defined. This patch fixes this functionality to honor the O_RDONLY in the BDRV_O_ACCESS flag in block.c and also fixes the IDE and SCSI interfaces that uses it.

It's been tested on RHEL-5 with xen-3.4-testing version of Michal

Signed-off-by Michal Novotny<[email protected]>

_______________________________________________
Xen-devel mailing list
[email protected]
http://lists.xensource.com/xen-devel

Signature · 2 lines

Michal Novotny<[email protected]>, RHCE
Virtualization Team (xen userspace), Red Hat

Quoted 10 lines

Quoted 5 lines

Quoted 5 lines

_______________________________________________
Xen-devel mailing list
[email protected]
http://lists.xensource.com/xen-devel

Signature · 2 lines

Michal Novotny<[email protected]>, RHCE
Virtualization Team (xen userspace), Red Hat

_______________________________________________
Xen-devel mailing list
[email protected]
http://lists.xensource.com/xen-devel

Signature · 2 lines

Michal Novotny<[email protected]>, RHCE
Virtualization Team (xen userspace), Red Hat

Quoted 111 lines · Michal Novotny

Quoted 30 lines · Michal Novotny

Quoted 20 lines · Pasi Kärkkäinen

Quoted 13 lines · Michal Novotny

Well, I'm still having some tools issues, mainly:

Error: (111, 'Connection refused')

Any guess what may be going wrong? Booted grub entry:

title Red Hat Enterprise Linux Server (2.6.31.13-xen HV, nolog)

          root (hd1,6)
          kernel /xen-4.1-unstable.gz
          module /vmlinuz-2.6.31.13 ro root=LABEL=/rhel2 rhgb quiet
selinux=0
          module /initrd-2.6.31.13.img

Quoted 5 lines

Mount is having xenfs on /proc/xen type xenfs (rw). Any guess what may
be going wrong?

Quoted 6 lines

Do you have xen-evtchn driver loaded?

-- Pasi

Well, no, and doesn't seem to be installed/probed:

Quoted 8 lines

# modprobe xen-evtchn
# lsmod | grep xen-evtchn
#

So there's the problem :(

Michal

Oh, I'm taking this back since I found out the module is not xen-evtchn but xen_evtchn. So yeah, I'm having it loaded in the memory now. However, when I do service xend restart the same error is here:

[2010-06-07 17:14:09 5635] INFO (SrvDaemon:227) Xend stopped due to signal 15.
[2010-06-07 17:14:09 6295] INFO (SrvDaemon:332) Xend Daemon started [2010-06-07 17:14:09 6295] INFO (SrvDaemon:336) Xend changeset: Thu May 20 17:22:15 2010 +0100 21442:a7fcf2e35d32.
[2010-06-07 17:14:09 6295] DEBUG (tcp:96) Listening on :8002 [2010-06-07 17:14:09 6295] INFO (XendNetwork:114) Not recreating missing unmanaged network eth0
[2010-06-07 17:14:09 6295] INFO (XendNetwork:114) Not recreating missing unmanaged network eth2
[2010-06-07 17:14:09 6295] INFO (XendNetwork:114) Not recreating missing unmanaged network br0
[2010-06-07 17:14:09 6295] INFO (XendNetwork:114) Not recreating missing unmanaged network xenbr0
[2010-06-07 17:14:10 6295] DEBUG (XendCPUPool:747) recreate_active_pools [2010-06-07 17:14:10 6295] ERROR (SrvDaemon:349) Exception starting xend ((111, 'Connection refused'))
Traceback (most recent call last):
File
"/usr/lib64/python2.4/site-packages/xen/xend/server/SrvDaemon.py", line 341, in run
servers = SrvServer.create()
File
"/usr/lib64/python2.4/site-packages/xen/xend/server/SrvServer.py", line 258, in create
root.putChild('xend', SrvRoot())
File "/usr/lib64/python2.4/site-packages/xen/xend/server/SrvRoot.py",
line 40, in __init__
self.get(name)
File "/usr/lib64/python2.4/site-packages/xen/web/SrvDir.py", line 84,
in get
val = val.getobj()
File "/usr/lib64/python2.4/site-packages/xen/web/SrvDir.py", line 52,
in getobj
self.obj = klassobj()
File "/usr/lib64/python2.4/site-packages/xen/xend/server/SrvNode.py",
line 30, in __init__
self.xn = XendNode.instance()
File "/usr/lib64/python2.4/site-packages/xen/xend/XendNode.py", line
1176, in instance
inst = XendNode()
File "/usr/lib64/python2.4/site-packages/xen/xend/XendNode.py", line
163, in __init__

     self._init_cpu_pools()

File "/usr/lib64/python2.4/site-packages/xen/xend/XendNode.py", line
377, in _init_cpu_pools
XendCPUPool.recreate_active_pools()
File "/usr/lib64/python2.4/site-packages/xen/xend/XendCPUPool.py",
line 754, in recreate_active_pools
uuid = xstransact.Read(path, 'uuid')
File
"/usr/lib64/python2.4/site-packages/xen/xend/xenstore/xstransact.py", line 307, in Read
return complete(path, lambda t: t.read(*args))
File
"/usr/lib64/python2.4/site-packages/xen/xend/xenstore/xstransact.py", line 361, in complete
t = xstransact(path)
File
"/usr/lib64/python2.4/site-packages/xen/xend/xenstore/xstransact.py", line 29, in __init__
self.transaction = xshandle().transaction_start()
File "/usr/lib64/python2.4/site-packages/xen/xend/xenstore/xsutil.py",
line 18, in xshandle
xs_handle = xen.lowlevel.xs.xs()
Error: (111, 'Connection refused')

Quoted 3 lines

Any ideas?

Is xenstore running?

Are there files in /proc/xen ?

-- Pasi

Quoted 137 lines

Michal

Quoted 134 lines

Quoted 134 lines

Quoted 134 lines

Thanks,
Michal

Quoted 123 lines · Pasi Kärkkäinen

Quoted 11 lines · Michal Novotny

Oh, one more thing I've discovered now. Since the codebase for qemu-xen-unstable is looking the same like for qemu-xen-3.4-testing and
the patch is applicable without any modifications it could be working for xen-4.1 unstable as well, unfortunately I was not able to boot PVOPS
kernel since it always ends up in kernel panic, maybe the missing drivers or something like that.

What kernel version? Did you use xen/stable-2.6.32.x branch from xen.git?

See my example .config files from:
http://wiki.xensource.com/xenwiki/XenParavirtOps in the "troubleshooting" section.

Works on F12/F13 dom0's.

For el5 dom0 you might need these:
http://wiki.xensource.com/xenwiki/2.6.18-to-2.6.31-and-higher

aka
CONFIG_SYSFS_DEPRECATED=y
CONFIG_SYSFS_DEPRECATED_V2=y

Also atm I think you need CONFIG_XEN_XENBUS_FRONTEND=y in the .config because of the recently added pv-on-hvm drivers (you'll get build failure without that option),
so you need XEN_PCIDEV_FRONTEND XEN_BLKDEV_FRONTEND or XEN_NETDEV_FRONTEND or XEN_FBDEV_FRONTEND needs to be =y.

-- Pasi

Quoted 82 lines · Michal Novotny

Quoted 70 lines

Oh, just one more thing that should be mentioned:

When you want to mount an image that is set as read-only in the domain
configuration file but you omit to set mode to read-only it results into I/O errors when processing the requests. Remounting as read-only
or unmounting and remounting using the `mount /dev/* /path/to/mount -o
ro` shall do the mounting the correct way, i.e. with no I/O errors, so
make sure you mount those disks as read-only otherwise you can be getting errors like:

end_request: I/O error, dev hdb, sector 52

Buffer I/O error on device hdb1, logical block 1

lost page write due to I/O error on hdb1

and for IDE devices you'll be getting several additional DeviceFault errors since mounting the device read-write (default setting) writes some data onto a disk at the mount-time.

Michal

Quoted 37 lines · Michal Novotny

[Well, I did send an e-mail to the list using git but it's not here so I'm forwarding the e-mail to the list for sure:]

Hi,
this is the patch for qemu-xen-3.4-testing to fix the read-only image file handling since the image file was always treated as read-write which means that all the HVM guests were able to write to all the disk images available in domain configuration file no matter what the mode of the image was defined. This patch fixes this functionality to honor the O_RDONLY in the BDRV_O_ACCESS flag in block.c and also fixes the IDE and SCSI interfaces that uses it.

It's been tested on RHEL-5 with xen-3.4-testing version of upstream xen with xen-3.4-testing qemu implementation.

For SCSI devices the DATA PROTECT request sense has been added as found at:
http://en.wikipedia.org/wiki/SCSI_Request_Sense_Command

file no matter what the mode of the image was defined. This patch fixes this functionality to honor the O_RDONLY in the BDRV_O_ACCESS flag in block.c and also fixes the IDE and SCSI interfaces that uses it.

It's been tested on RHEL-5 with xen-3.4-testing version of Michal

Signed-off-by Michal Novotny<[email protected]>

_______________________________________________
Xen-devel mailing list
[email protected]
http://lists.xensource.com/xen-devel

Signature · 8 lines

Michal Novotny<[email protected]>, RHCE
Virtualization Team (xen userspace), Red Hat


_______________________________________________
Xen-devel mailing list
[email protected]
http://lists.xensource.com/xen-devel

Signature · 2 lines

Michal Novotny<[email protected]>, RHCE
Virtualization Team (xen userspace), Red Hat

Quoted 13 lines

Quoted 7 lines

Quoted 5 lines

_______________________________________________
Xen-devel mailing list
[email protected]
http://lists.xensource.com/xen-devel

Signature · 2 lines

Michal Novotny<[email protected]>, RHCE
Virtualization Team (xen userspace), Red Hat

_______________________________________________
Xen-devel mailing list
[email protected]
http://lists.xensource.com/xen-devel

Quoted 113 lines · Pasi Kärkkäinen

Quoted 112 lines · Michal Novotny

Quoted 26 lines · Michal Novotny

Quoted 14 lines · Pasi Kärkkäinen

Quoted 13 lines · Michal Novotny

Well, I'm still having some tools issues, mainly:

Error: (111, 'Connection refused')

Any guess what may be going wrong? Booted grub entry:

title Red Hat Enterprise Linux Server (2.6.31.13-xen HV, nolog)

          root (hd1,6)
          kernel /xen-4.1-unstable.gz
          module /vmlinuz-2.6.31.13 ro root=LABEL=/rhel2 rhgb quiet
selinux=0
          module /initrd-2.6.31.13.img

Quoted 9 lines

Quoted 4 lines

Mount is having xenfs on /proc/xen type xenfs (rw). Any guess what may
be going wrong?

Do you have xen-evtchn driver loaded?

-- Pasi

Well, no, and doesn't seem to be installed/probed:

Quoted 7 lines

# modprobe xen-evtchn
# lsmod | grep xen-evtchn
#

So there's the problem :(

Michal

Oh, I'm taking this back since I found out the module is not xen-evtchn but xen_evtchn. So yeah, I'm having it loaded in the memory now. However, when I do service xend restart the same error is here:

[2010-06-07 17:14:09 5635] INFO (SrvDaemon:227) Xend stopped due to signal 15.
[2010-06-07 17:14:09 6295] INFO (SrvDaemon:332) Xend Daemon started [2010-06-07 17:14:09 6295] INFO (SrvDaemon:336) Xend changeset: Thu May 20 17:22:15 2010 +0100 21442:a7fcf2e35d32.
[2010-06-07 17:14:09 6295] DEBUG (tcp:96) Listening on :8002 [2010-06-07 17:14:09 6295] INFO (XendNetwork:114) Not recreating missing unmanaged network eth0
[2010-06-07 17:14:09 6295] INFO (XendNetwork:114) Not recreating missing unmanaged network eth2
[2010-06-07 17:14:09 6295] INFO (XendNetwork:114) Not recreating missing unmanaged network br0
[2010-06-07 17:14:09 6295] INFO (XendNetwork:114) Not recreating missing unmanaged network xenbr0
[2010-06-07 17:14:10 6295] DEBUG (XendCPUPool:747) recreate_active_pools [2010-06-07 17:14:10 6295] ERROR (SrvDaemon:349) Exception starting xend ((111, 'Connection refused'))
Traceback (most recent call last):
File
"/usr/lib64/python2.4/site-packages/xen/xend/server/SrvDaemon.py", line 341, in run
servers = SrvServer.create()
File
"/usr/lib64/python2.4/site-packages/xen/xend/server/SrvServer.py", line 258, in create
root.putChild('xend', SrvRoot())
File
"/usr/lib64/python2.4/site-packages/xen/xend/server/SrvRoot.py", line 40, in __init__
self.get(name)
File "/usr/lib64/python2.4/site-packages/xen/web/SrvDir.py", line
84,
in get
val = val.getobj()
File "/usr/lib64/python2.4/site-packages/xen/web/SrvDir.py", line
52,
in getobj
self.obj = klassobj()
File
"/usr/lib64/python2.4/site-packages/xen/xend/server/SrvNode.py", line 30, in __init__
self.xn = XendNode.instance()
File "/usr/lib64/python2.4/site-packages/xen/xend/XendNode.py", line
1176, in instance
inst = XendNode()
File "/usr/lib64/python2.4/site-packages/xen/xend/XendNode.py", line
163, in __init__

     self._init_cpu_pools()

File "/usr/lib64/python2.4/site-packages/xen/xend/XendNode.py", line
377, in _init_cpu_pools
XendCPUPool.recreate_active_pools()
File "/usr/lib64/python2.4/site-packages/xen/xend/XendCPUPool.py",
line 754, in recreate_active_pools
uuid = xstransact.Read(path, 'uuid')
File
"/usr/lib64/python2.4/site-packages/xen/xend/xenstore/xstransact.py", line 307, in Read
return complete(path, lambda t: t.read(*args))
File
"/usr/lib64/python2.4/site-packages/xen/xend/xenstore/xstransact.py", line 361, in complete
t = xstransact(path)
File
"/usr/lib64/python2.4/site-packages/xen/xend/xenstore/xstransact.py", line 29, in __init__
self.transaction = xshandle().transaction_start()
File
"/usr/lib64/python2.4/site-packages/xen/xend/xenstore/xsutil.py", line 18, in xshandle
xs_handle = xen.lowlevel.xs.xs()
Error: (111, 'Connection refused')

Any ideas?

Quoted 4 lines

Is xenstore running?

Are there files in /proc/xen ?

Yes to both questions. Everything seems to be OK. Also, there's option to turn on the debugging of xenstore, right? Do you think it could help? I'm going to try it now.

Michal

Quoted 141 lines

-- Pasi

Quoted 125 lines

Michal

Quoted 123 lines

Quoted 123 lines

Quoted 123 lines

Thanks,
Michal

Quoted 115 lines · Pasi Kärkkäinen

Quoted 10 lines · Michal Novotny

Oh, one more thing I've discovered now. Since the codebase for qemu-xen-unstable is looking the same like for qemu-xen-3.4-testing and
the patch is applicable without any modifications it could be working for xen-4.1 unstable as well, unfortunately I was not able to boot PVOPS
kernel since it always ends up in kernel panic, maybe the missing drivers or something like that.

What kernel version? Did you use xen/stable-2.6.32.x branch from xen.git?

See my example .config files from:
http://wiki.xensource.com/xenwiki/XenParavirtOps in the "troubleshooting" section.

Works on F12/F13 dom0's.

For el5 dom0 you might need these:
http://wiki.xensource.com/xenwiki/2.6.18-to-2.6.31-and-higher

aka
CONFIG_SYSFS_DEPRECATED=y
CONFIG_SYSFS_DEPRECATED_V2=y

Also atm I think you need CONFIG_XEN_XENBUS_FRONTEND=y in the .config because of the recently added pv-on-hvm drivers (you'll get build failure without that option),
so you need XEN_PCIDEV_FRONTEND XEN_BLKDEV_FRONTEND or XEN_NETDEV_FRONTEND or XEN_FBDEV_FRONTEND needs to be =y.

-- Pasi

Quoted 77 lines · Michal Novotny

Quoted 66 lines

Oh, just one more thing that should be mentioned:

When you want to mount an image that is set as read-only in the domain
configuration file but you omit to set mode to read-only it results into I/O errors when processing the requests. Remounting as read-only
or unmounting and remounting using the `mount /dev/* /path/to/mount -o
ro` shall do the mounting the correct way, i.e. with no I/O errors, so
make sure you mount those disks as read-only otherwise you can be getting errors like:

end_request: I/O error, dev hdb, sector 52

Buffer I/O error on device hdb1, logical block 1

lost page write due to I/O error on hdb1

and for IDE devices you'll be getting several additional DeviceFault errors since mounting the device read-write (default setting) writes some data onto a disk at the mount-time.

Michal

Quoted 36 lines · Michal Novotny

[Well, I did send an e-mail to the list using git but it's not here so I'm forwarding the e-mail to the list for sure:]

Hi,
this is the patch for qemu-xen-3.4-testing to fix the read-only image file handling since the image file was always treated as read-write which means that all the HVM guests were able to write to all the disk images available in domain configuration file no matter what the mode of the image was defined. This patch fixes this functionality to honor the O_RDONLY in the BDRV_O_ACCESS flag in block.c and also fixes the IDE and SCSI interfaces that uses it.

It's been tested on RHEL-5 with xen-3.4-testing version of upstream xen with xen-3.4-testing qemu implementation.

For SCSI devices the DATA PROTECT request sense has been added as found at:
http://en.wikipedia.org/wiki/SCSI_Request_Sense_Command

file no matter what the mode of the image was defined. This patch fixes this functionality to honor the O_RDONLY in the BDRV_O_ACCESS flag in block.c and also fixes the IDE and SCSI interfaces that uses it.

It's been tested on RHEL-5 with xen-3.4-testing version of Michal

Signed-off-by Michal Novotny<[email protected]>

_______________________________________________
Xen-devel mailing list
[email protected]
http://lists.xensource.com/xen-devel

Signature · 8 lines

Michal Novotny<[email protected]>, RHCE
Virtualization Team (xen userspace), Red Hat


_______________________________________________
Xen-devel mailing list
[email protected]
http://lists.xensource.com/xen-devel

Signature · 2 lines

Michal Novotny<[email protected]>, RHCE
Virtualization Team (xen userspace), Red Hat

Quoted 10 lines

Quoted 5 lines

Quoted 4 lines

_______________________________________________
Xen-devel mailing list
[email protected]
http://lists.xensource.com/xen-devel

Signature · 2 lines

Michal Novotny<[email protected]>, RHCE
Virtualization Team (xen userspace), Red Hat

_______________________________________________
Xen-devel mailing list
[email protected]
http://lists.xensource.com/xen-devel

For HVM guests it's:

# xm create rhel5-32fv
Using config file "./rhel5-32fv".
Error: Not enough memory is available, and dom0 cannot be shrunk any further

and also the xend.log fragment relevant to the issue:

Quoted 6 lines · Michal Novotny

For HVM guests it's:

# xm create rhel5-32fv
Using config file "./rhel5-32fv".
Error: Not enough memory is available, and dom0 cannot be shrunk any further

Quoted 2 lines

and also the xend.log fragment relevant to the issue:

Try no-tmem on Xen command line.

-- Keir

and I was even unable to do xm list because of the issue with memory and also I found out that it's not working when I reboot the system and even when I put modprobe for xen-evtchn to xend init script so I need to modprobe xen-evtchn manually, then run xenstore daemon and then restart the xen daemon.

Quoted 1 line · Michal Novotny

and I was even unable to do xm list because of the issue with memory and also I found out that it's not working when I reboot the system and even when I put modprobe for xen-evtchn to xend init script so I need to modprobe xen-evtchn manually, then run xenstore daemon and then restart the xen daemon.

Are you running with selinux enabled? I have seen selinux cause startup issues with xen before. If you are it might be worth trying again in permissive mode and see if anything is different.

Michael Young

_______________________________________________
Xen-devel mailing list
[email protected]
http://lists.xensource.com/xen-devel

Well,
it doesn't seem to be that easy because I can't boot any of the guests. No matter whether HVM or PV.

For PV it's connected with the hotplugging:

# xm create rhel5-32pv
Using config file "./rhel5-32pv".
Error: Device 0 (vif) could not be connected. Hotplug scripts not working.

For HVM guests it's:

# xm create rhel5-32fv
Using config file "./rhel5-32fv".
Error: Not enough memory is available, and dom0 cannot be shrunk any further

and also the xend.log fragment relevant to the issue:

For PV guests there was a change of blktap to blktap2. Couldn't this be related? How could I check I'm using the blktap2 ? Also, my test machine is Intel Xeon X5460 @ 3.16 Ghz, quad-core with 8 GiB RAM running on RHEL-5 with upstream 4.1 xen.

Quoted 4 lines · Michal Novotny

Well,
it doesn't seem to be that easy because I can't boot any of the guests. No matter whether HVM or PV.

Quoted 7 lines

For PV it's connected with the hotplugging:

# xm create rhel5-32pv
Using config file "./rhel5-32pv".
Error: Device 0 (vif) could not be connected. Hotplug scripts not working.

Do you have correct bridge= specified for the vif? Does the bridge exist?

Quoted 7 lines

For HVM guests it's:

# xm create rhel5-32fv
Using config file "./rhel5-32fv".
Error: Not enough memory is available, and dom0 cannot be shrunk any further

Do you have dom0_mem=1024M for xen.gz in grub.conf ?
You should limit/dedicate some memory for only dom0 and thus prevent the need for ballooning.

Quoted 9 lines

and also the xend.log fragment relevant to the issue:

For PV guests there was a change of blktap to blktap2. Couldn't this be related? How could I check I'm using the blktap2 ? Also, my test machine is Intel Xeon X5460 @ 3.16 Ghz, quad-core with 8 GiB RAM running on RHEL-5 with upstream 4.1 xen.

Try first using just file:// if using image files, or phy: if using lvm volumes.

-- Pasi

_______________________________________________
Xen-devel mailing list
[email protected]
http://lists.xensource.com/xen-devel

Well,
it doesn't seem to be that easy because I can't boot any of the guests. No matter whether HVM or PV.

For PV it's connected with the hotplugging:

# xm create rhel5-32pv
Using config file "./rhel5-32pv".
Error: Device 0 (vif) could not be connected. Hotplug scripts not working.

For HVM guests it's:

# xm create rhel5-32fv
Using config file "./rhel5-32fv".
Error: Not enough memory is available, and dom0 cannot be shrunk any further

Quoted 10 lines · Michal Novotny

Well,
it doesn't seem to be that easy because I can't boot any of the guests. No matter whether HVM or PV.

For PV it's connected with the hotplugging:

# xm create rhel5-32pv
Using config file "./rhel5-32pv".
Error: Device 0 (vif) could not be connected. Hotplug scripts not working.

Make sure you have your tun module loaded (yeah, no need for it, but the qemu-ifup might be touch it). Also you can take a look at /var/log/xen/xen-hotplug to see what the error is.

Quoted 2 lines

For HVM guests it's:

.. snip..

Quoted 4 lines

# xm create rhel5-32fv
Using config file "./rhel5-32fv".
Error: Not enough memory is available, and dom0 cannot be shrunk any further

Try xm mem-set 0 2048 before the start and see if that makes it work.

Quoted 2 lines

Try xm mem-set 0 2048 before the start and see if that makes it work.

Well, now it changed to:

# xenstored
  FATAL: Failed to initialize dom0 state: Invalid argument

what does it mean and how to fix it?

Quoted 8 lines · Michal Novotny

Quoted 3 lines

Try xm mem-set 0 2048 before the start and see if that makes it work.

Well, now it changed to:

# xenstored
   FATAL: Failed to initialize dom0 state: Invalid argument

Quoted 2 lines

what does it mean and how to fix it?

Do files /proc/xen/xsd_kva and /proc/xen/xsd_port exist? If not you need to configure and/or install the appropriate xenstore-related kernel module (whatever that may be, in pv_ops land).

-- Keir

_______________________________________________
Xen-devel mailing list
[email protected]
http://lists.xensource.com/xen-devel

Quoted 4 lines

Do files /proc/xen/xsd_kva and /proc/xen/xsd_port exist? If not you need to configure and/or install the appropriate xenstore-related kernel module (whatever that may be, in pv_ops land).

Quoted 2 lines

-- Keir

Thanks but I checked it and they exist and it seems to be OK. Also, the strange thing is that even if I put modprobe to /etc/init.d/xend before start the module can't get probed and lsmod is showing only xenfs module but no xen_evtchn loaded. I need to modprobe it manually, run xenstored manually and then after starting xen daemon the error of dom0 state happens.

...
I suggest add some tracing to function dom0_init() in xenstored and see where that function is failing. The two most obvious places were the opening of those two files in /proc. If they exist then I'm not sure what else could be going wrong.

Oh, you should be able to cat /proc/xen/ksd_port and get an integer value. /proc/xen/ksd_kva by contrast gets mmap()ed by xenstored.

_______________________________________________
Xen-devel mailing list
[email protected]
http://lists.xensource.com/xen-devel

Quoted 8 lines · Keir Fraser

...
I suggest add some tracing to function dom0_init() in xenstored and see where that function is failing. The two most obvious places were the opening of those two files in /proc. If they exist then I'm not sure what else could be going wrong.

Oh, you should be able to cat /proc/xen/ksd_port and get an integer value. /proc/xen/ksd_kva by contrast gets mmap()ed by xenstored.

Thank you all, I was able to make it running (using some qemu-dm example in the example) at least for my testing of HVM guest read-only image handling fix (I didn't try it for PV guests yet) and I have to confirm that my patch to fix read-only image file handling (sent to the list as the first e-mail in this thread) is working fine with both xen-3.4-testing and xen-4.1-unstable. The fix is for xen-iommu located in iommu-dir (downloaded from git). Is this the right list to post this patch to? It can't be going to qemu-devel list since this is really closely connected to xenstore which is not a part of qemu at all so this is for the xenstore layer of qemu-dm mainly.

Quoted 11 lines · Michal Novotny

Thank you all, I was able to make it running (using some qemu-dm example in the example) at least for my testing of HVM guest read-only image handling fix (I didn't try it for PV guests yet) and I have to confirm that my patch to fix read-only image file handling (sent to the list as the first e-mail in this thread) is working fine with both xen-3.4-testing and xen-4.1-unstable. The fix is for xen-iommu located in iommu-dir (downloaded from git). Is this the right list to post this patch to? It can't be going to qemu-devel list since this is really closely connected to xenstore which is not a part of qemu at all so this is for the xenstore layer of qemu-dm mainly.

Send it to this list as a patch to our qemu git repository. Cc Ian Jackson who maintains that repo.

-- Keir

_______________________________________________
Xen-devel mailing list
[email protected]
http://lists.xensource.com/xen-devel

Quoted 2 lines

Send it to this list as a patch to our qemu git repository. Cc Ian Jackson who maintains that repo.

I did already sent it to this list as a first e-mail in this thread. Should I repost the same version of the patch and just send it to Ian ?

Quoted 3 lines · Michal Novotny

Quoted 3 lines

Send it to this list as a patch to our qemu git repository. Cc Ian Jackson who maintains that repo.

Quoted 3 lines

I did already sent it to this list as a first e-mail in this thread. Should I repost the same version of the patch and just send it to Ian ?

Yeah just chase him directly.

-- Keir

I also tried to decrease the memory for dom0 as advised on the list (using the xm mem-set 0 2048) but still the same result but I saw something in the qemu-dm log file about -vcpu-avail option is invalid:

# cat /var/log/xen/qemu-dm-rhel5-32fv.log
domid: 1
qemu: the number of cpus is 1
/usr/lib64/xen/bin/qemu-dm: invalid option -- '-vcpu_avail'
#

Quoted 10 lines · Michal Novotny

I also tried to decrease the memory for dom0 as advised on the list (using the xm mem-set 0 2048) but still the same result but I saw something in the qemu-dm log file about -vcpu-avail option is invalid:

# cat /var/log/xen/qemu-dm-rhel5-32fv.log
domid: 1
qemu: the number of cpus is 1
/usr/lib64/xen/bin/qemu-dm: invalid option -- '-vcpu_avail'
#

Stale qemu-dm binary hanging around, perhaps. I find that kind of thing happens when trying out different version sof Xen on a single test system. Either your new qemu-dm binary did not get installed, or it did but in a different location to the stale one, and it happens that the stale one dominates.

In particular, Xen 3.4 qemu does not support the -vcpu_avail cmdline option, but 4.0 and 4.1 (unstable) do. And 4.0/4.1 xend depends on that.

-- Keir

Quoted 9 lines · Michal Novotny

I also tried to decrease the memory for dom0 as advised on the list (using the xm mem-set 0 2048) but still the same result but I saw something in the qemu-dm log file about -vcpu-avail option is invalid:

# cat /var/log/xen/qemu-dm-rhel5-32fv.log
domid: 1
qemu: the number of cpus is 1
/usr/lib64/xen/bin/qemu-dm: invalid option -- '-vcpu_avail'
#

Stale qemu-dm binary hanging around, perhaps. I find that kind of thing happens when trying out different version sof Xen on a single test system. Either your new qemu-dm binary did not get installed, or it did but in a different location to the stale one, and it happens that the stale one dominates.

In particular, Xen 3.4 qemu does not support the -vcpu_avail cmdline option, but 4.0 and 4.1 (unstable) do. And 4.0/4.1 xend depends on that.

Quoted 18 lines · Keir Fraser

Quoted 9 lines · Michal Novotny

I also tried to decrease the memory for dom0 as advised on the list (using the xm mem-set 0 2048) but still the same result but I saw something in the qemu-dm log file about -vcpu-avail option is invalid:

# cat /var/log/xen/qemu-dm-rhel5-32fv.log
domid: 1
qemu: the number of cpus is 1
/usr/lib64/xen/bin/qemu-dm: invalid option -- '-vcpu_avail'
#

Stale qemu-dm binary hanging around, perhaps. I find that kind of thing happens when trying out different version sof Xen on a single test system. Either your new qemu-dm binary did not get installed, or it did but in a different location to the stale one, and it happens that the stale one dominates.

Quoted 2 lines

In particular, Xen 3.4 qemu does not support the -vcpu_avail cmdline option, but 4.0 and 4.1 (unstable) do. And 4.0/4.1 xend depends on that.

qemu-dm was at /usr/lib64/xen/bin/qemu-dm in 3.4 on 64-bit builds but for some reason it moved to /usr/lib/xen/bin/qemu-dm in 4.0 and presumably 4.1.

Michael Young

Quoted 108 lines

Quoted 97 lines

Quoted 97 lines

Quoted 8 lines

Quoted 6 lines

Quoted 1 line

Do you have xen-evtchn driver loaded?

-- Pasi

Well, no, and doesn't seem to be installed/probed:

Quoted 7 lines

# modprobe xen-evtchn
# lsmod | grep xen-evtchn
#

So there's the problem :(

Michal

Oh, I'm taking this back since I found out the module is not xen-evtchn but xen_evtchn. So yeah, I'm having it loaded in the memory now. However, when I do service xend restart the same error is here:

[2010-06-07 17:14:09 5635] INFO (SrvDaemon:227) Xend stopped due to signal 15.
[2010-06-07 17:14:09 6295] INFO (SrvDaemon:332) Xend Daemon started [2010-06-07 17:14:09 6295] INFO (SrvDaemon:336) Xend changeset: Thu May 20 17:22:15 2010 +0100 21442:a7fcf2e35d32.
[2010-06-07 17:14:09 6295] DEBUG (tcp:96) Listening on :8002 [2010-06-07 17:14:09 6295] INFO (XendNetwork:114) Not recreating missing
unmanaged network eth0
[2010-06-07 17:14:09 6295] INFO (XendNetwork:114) Not recreating missing
unmanaged network eth2
[2010-06-07 17:14:09 6295] INFO (XendNetwork:114) Not recreating missing
unmanaged network br0
[2010-06-07 17:14:09 6295] INFO (XendNetwork:114) Not recreating missing
unmanaged network xenbr0
[2010-06-07 17:14:10 6295] DEBUG (XendCPUPool:747) recreate_active_pools
[2010-06-07 17:14:10 6295] ERROR (SrvDaemon:349) Exception starting xend
((111, 'Connection refused'))
Traceback (most recent call last):
File
"/usr/lib64/python2.4/site-packages/xen/xend/server/SrvDaemon.py", line 341, in run
servers = SrvServer.create()
File
"/usr/lib64/python2.4/site-packages/xen/xend/server/SrvServer.py", line 258, in create
root.putChild('xend', SrvRoot())
File
"/usr/lib64/python2.4/site-packages/xen/xend/server/SrvRoot.py", line 40, in __init__
self.get(name)
File "/usr/lib64/python2.4/site-packages/xen/web/SrvDir.py",
line 84,
in get
val = val.getobj()
File "/usr/lib64/python2.4/site-packages/xen/web/SrvDir.py",
line 52,
in getobj
self.obj = klassobj()
File
"/usr/lib64/python2.4/site-packages/xen/xend/server/SrvNode.py", line 30, in __init__
self.xn = XendNode.instance()
File "/usr/lib64/python2.4/site-packages/xen/xend/XendNode.py", line
1176, in instance
inst = XendNode()
File "/usr/lib64/python2.4/site-packages/xen/xend/XendNode.py", line
163, in __init__

     self._init_cpu_pools()

File "/usr/lib64/python2.4/site-packages/xen/xend/XendNode.py", line
377, in _init_cpu_pools
XendCPUPool.recreate_active_pools()
File "/usr/lib64/python2.4/site-packages/xen/xend/XendCPUPool.py",
line 754, in recreate_active_pools
uuid = xstransact.Read(path, 'uuid')
File
"/usr/lib64/python2.4/site-packages/xen/xend/xenstore/xstransact.py", line 307, in Read
return complete(path, lambda t: t.read(*args))
File
"/usr/lib64/python2.4/site-packages/xen/xend/xenstore/xstransact.py", line 361, in complete
t = xstransact(path)
File
"/usr/lib64/python2.4/site-packages/xen/xend/xenstore/xstransact.py", line 29, in __init__
self.transaction = xshandle().transaction_start()
File
"/usr/lib64/python2.4/site-packages/xen/xend/xenstore/xsutil.py", line 18, in xshandle
xs_handle = xen.lowlevel.xs.xs()
Error: (111, 'Connection refused')

Quoted 6 lines

Quoted 2 lines

Any ideas?

Is xenstore running?

Are there files in /proc/xen ?

Yes to both questions. Everything seems to be OK. Also, there's option to turn on the debugging of xenstore, right? Do you think it could help? I'm going to try it now.

Quoted 1 line

Michal

Well, I don't know what was wrong but when I turned on the debugging it was finally working fine to run xen daemon and also when I killed xenstore and turned off the debugging. xm list was working fine but I don't know why so it's a kind of magic to me. Nevertheless, it appears to be working fine by now.

# modprobe xen-evtchn
# lsmod | grep xen-evtchn