search for: ehabkost

This series contain fixes to make the paravirt_ops code compile and boot on x86_64. This is a follow-up for the previous series from Glauber.

This series contain fixes to make the paravirt_ops code compile and boot on x86_64. This is a follow-up for the previous series from Glauber.

Hi All, I found it very difficult to get Xen-3.1 up on a a machine with Intel''s ICH9 family of disk controllers :-(. Is the ICH9 support really there in xen-3.2 ? I tried but was not successful in booting even xen-3.2 from xen.org. Did anyone have a success? Or any help on what extra config options I need to pass while compiling a domain0 from xen sources? Thanks, -- Pradeep Singh

On Mon, Jul 28, 2014 at 12:18:10PM -0700, H. Peter Anvin wrote: > On 07/28/2014 12:04 PM, Eduardo Habkost wrote: > > When CONFIG_PARAVIRT is enabled, the kernel is ignoring exceptions on > > the {rd,wr}msr instructions. This makes serious issues (either on the > > guest kernel, or on the host) be silently ignored, and is different from > > the native MSR code (which does

On Mon, Jul 28, 2014 at 12:18:10PM -0700, H. Peter Anvin wrote: > On 07/28/2014 12:04 PM, Eduardo Habkost wrote: > > When CONFIG_PARAVIRT is enabled, the kernel is ignoring exceptions on > > the {rd,wr}msr instructions. This makes serious issues (either on the > > guest kernel, or on the host) be silently ignored, and is different from > > the native MSR code (which does

...is different from the native MSR code (which does not ignore the exceptions). As paravirt.h already includes linux/bug.h, I don't see what was the original issue preventing BUG_ON from being used. Change rdmsr(), wrmsr(), and rdmsrl() to BUG_ON() on errors. Signed-off-by: Eduardo Habkost <ehabkost at redhat.com> --- * Build-tested using allyesconfig, with no build errors. * Tested by being able to detect the following host bug: https://bugzilla.redhat.com/show_bug.cgi?id=1025868 (#GP exception on wrmsr(0x410, 0xfffffffffffffbff) during MCE initialization) --- arch/x86/include/asm/...

...is different from the native MSR code (which does not ignore the exceptions). As paravirt.h already includes linux/bug.h, I don't see what was the original issue preventing BUG_ON from being used. Change rdmsr(), wrmsr(), and rdmsrl() to BUG_ON() on errors. Signed-off-by: Eduardo Habkost <ehabkost at redhat.com> --- * Build-tested using allyesconfig, with no build errors. * Tested by being able to detect the following host bug: https://bugzilla.redhat.com/show_bug.cgi?id=1025868 (#GP exception on wrmsr(0x410, 0xfffffffffffffbff) during MCE initialization) --- arch/x86/include/asm/...

> > No. And it's exactly what I mean. The ballooned memory is still > > processed during live migration without skipping. The live migration code is > in migration/ram.c. > > So if guest acknowledged VIRTIO_BALLOON_F_MUST_TELL_HOST, we can > teach qemu to skip these pages. > Want to write a patch to do this? > Yes, we really can teach qemu to skip these pages

> > No. And it's exactly what I mean. The ballooned memory is still > > processed during live migration without skipping. The live migration code is > in migration/ram.c. > > So if guest acknowledged VIRTIO_BALLOON_F_MUST_TELL_HOST, we can > teach qemu to skip these pages. > Want to write a patch to do this? > Yes, we really can teach qemu to skip these pages

...oug Goldstein <cardoe@cardoe.com> Dunrong Huang <huangdr@cloud-times.com> Dunrong Huang <riegamaths@gmail.com> Ed Maste <emaste@freebsd.org> Edgar E. Iglesias <edgar.iglesias@gmail.com> Edgar E. Iglesias <edgar.iglesias@xilinx.com> Eduardo Habkost <ehabkost@redhat.com> Eduardo Otubo <otubo@linux.vnet.ibm.com> Eiichi Tsukata <eiichi.tsukata.xh@hitachi.com> Ekaterina Tumanova <tumanova@linux.vnet.ibm.com> Eric Blake <eblake@redhat.com> Eric Johnson <ericj@mips.com> Erlon Cruz <erlon.cruz@br.flextronics.com...

...oug Goldstein <cardoe@cardoe.com> Dunrong Huang <huangdr@cloud-times.com> Dunrong Huang <riegamaths@gmail.com> Ed Maste <emaste@freebsd.org> Edgar E. Iglesias <edgar.iglesias@gmail.com> Edgar E. Iglesias <edgar.iglesias@xilinx.com> Eduardo Habkost <ehabkost@redhat.com> Eduardo Otubo <otubo@linux.vnet.ibm.com> Eiichi Tsukata <eiichi.tsukata.xh@hitachi.com> Ekaterina Tumanova <tumanova@linux.vnet.ibm.com> Eric Blake <eblake@redhat.com> Eric Johnson <ericj@mips.com> Erlon Cruz <erlon.cruz@br.flextronics.com...

...oug Goldstein <cardoe@cardoe.com> Dunrong Huang <huangdr@cloud-times.com> Dunrong Huang <riegamaths@gmail.com> Ed Maste <emaste@freebsd.org> Edgar E. Iglesias <edgar.iglesias@gmail.com> Edgar E. Iglesias <edgar.iglesias@xilinx.com> Eduardo Habkost <ehabkost@redhat.com> Eduardo Otubo <otubo@linux.vnet.ibm.com> Eiichi Tsukata <eiichi.tsukata.xh@hitachi.com> Ekaterina Tumanova <tumanova@linux.vnet.ibm.com> Eric Blake <eblake@redhat.com> Eric Johnson <ericj@mips.com> Erlon Cruz <erlon.cruz@br.flextronics.com...

Hi, all -- I''m in the process of configuring a new machine for use as a Xen server, and am having some rather significant stability issues. The hardware/distro/kernel info is: opensuse 10.3 Linux offxen2 2.6.22.5-31-xen #1 SMP 2007/09/21 22:29:00 UTC x86_64 x86_64 x86_64 GNU/Linux 2 x Dual-Core AMD Opteron(tm) Processor 2212 HE 8 x 2GB PC2-5300 RAM Xen 3.1.0_15042-51 I currently have

This should help us to: - More easily add or remove machine initialization arguments without having to change every single machine init function; - More easily make mechanical changes involving the machine init functions in the future; - Let machine initialization forward the init arguments to other functions more easily. This change was half-mechanical process: first the struct was added