xen-devel
Re: [Xen-devel] GPLPV memory ballooning and x32
On 24/05/2010 23:23, "Aravindh Puthiyaparambil" <aravindh@xxxxxxxxxx> wrote:
> I tried the Xen3.4.2 from the Gitco repo. I am unable to bring up any domain
> if I specify the memmax option to be greater that memory. The respective
> qemu-dm processes for the domains are at 95-100% CPU utilization. I tried this
> with x64 Linux and Windows domains. The Linux-centos domains stayed at
> "Booting 'CentOS'" screen. The windows domain died with a GPF that was
> displayed in the VNC window. I have attached the screen shots. I did not find
> anything of note in the xend.log. The qemu logs are shown below. The last line
> in "xm dmesg" is:
>
> (XEN) io.c:199:d5 MMIO emulation failed @ 0008:4013c8: 90 a6 9f 2d 08 83
>
> Any idea why this is occurring?
Perhaps a bug in populate-on-demand, which I guess is what gets enabled when
you specify maxmem parameter for an HVM domain. It gets allocated its basic
memory parameter initially, and extra memory gets allocated when the HVM
guest first writes to it, up to maxmem limit. Or that's the intent anyway.
This is not a regression from 3.1 presumably (3.1 does not implement
populate-on-demand at all)?
-- Keir
> Thanks,
> Aravindh
>
>
> CentOS-x64
> ----------
> domid: 4
> qemu: the number of cpus is 1
> config qemu network with xen bridge for tap4.0 xenbr0
> Watching /local/domain/0/device-model/4/logdirty/next-active
> Watching /local/domain/0/device-model/4/command
> char device redirected to /dev/pts/3
> qemu_map_cache_init nr_buckets = 10000 size 4194304
> shared page at pfn feffd
> buffered io page at pfn feffb
> Guest uuid = a2ae0d0e-380c-d3a1-bec4-01980c986d66
> Time offset set 0
> populating video RAM at ff000000
> mapping video RAM from ff000000
> Register xen platform.
> Done register platform.
> xs_read(/vm/a2ae0d0e-380c-d3a1-bec4-01980c986d66/log-throttling): read error
> platform_fixed_ioport: changed ro/rw state of ROM memory area. now is rw
> state.
> xs_read(/local/domain/0/device-model/4/xen_extended_power_mgmt): read error
> xs_read(): vncpasswd get error.
> /vm/a2ae0d0e-380c-d3a1-bec4-01980c986d66/vncpasswd.
> medium change watch on `hdc' (index: 1):
> /home/gold/isos/CentOS-5.3-x86_64-bin-DVD_ks_floppy.iso
> I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0
> cirrus vga map change while on lfb mode
> mapping vram to f0000000 - f0400000
> platform_fixed_ioport: changed ro/rw state of ROM memory area. now is rw
> state.
> platform_fixed_ioport: changed ro/rw state of ROM memory area. now is ro
> state.
>
> W2k3-x64
> --------
> domid: 5
> qemu: the number of cpus is 2
> config qemu network with xen bridge for tap5.0 xenbr0
> Watching /local/domain/0/device-model/5/logdirty/next-active
> Watching /local/domain/0/device-model/5/command
> qemu_map_cache_init nr_buckets = 10000 size 4194304
> shared page at pfn feffd
> buffered io page at pfn feffb
> Guest uuid = 41de22fc-a638-4d34-5237-1a111d81e263
> Time offset set 0
> populating video RAM at ff000000
> mapping video RAM from ff000000
> Register xen platform.
> Done register platform.
> xs_read(/vm/41de22fc-a638-4d34-5237-1a111d81e263/log-throttling): read error
> platform_fixed_ioport: changed ro/rw state of ROM memory area. now is rw
> state.
> xs_read(/local/domain/0/device-model/5/xen_extended_power_mgmt): read error
> xs_read(): vncpasswd get error.
> /vm/41de22fc-a638-4d34-5237-1a111d81e263/vncpasswd.
> medium change watch on `hdc' (index: 1): /home/gold/isos/WindowsPVJH.iso
> I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0
> I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0
> cirrus vga map change while on lfb mode
> mapping vram to f0000000 - f0400000
> platform_fixed_ioport: changed ro/rw state of ROM memory area. now is rw
> state.
> platform_fixed_ioport: changed ro/rw state of ROM memory area. now is ro
> state.
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
<Prev in Thread] |
Current Thread |
[Next in Thread>
|
- [Xen-devel] GPLPV memory ballooning and x32, James Harper
- Re: [Xen-devel] GPLPV memory ballooning and x32, Keir Fraser
- RE: [Xen-devel] GPLPV memory ballooning and x32, James Harper
- RE: [Xen-devel] GPLPV memory ballooning and x32, Aravindh Puthiyaparambil
- Re: [Xen-devel] GPLPV memory ballooning and x32, Pasi Kärkkäinen
- RE: [Xen-devel] GPLPV memory ballooning and x32, Aravindh Puthiyaparambil
- Re: [Xen-devel] GPLPV memory ballooning and x32,
Keir Fraser <=
- RE: [Xen-devel] GPLPV memory ballooning and x32, James Harper
- Re: [Xen-devel] GPLPV memory ballooning and x32, Keir Fraser
- RE: [Xen-devel] GPLPV memory ballooning and x32, Jan Beulich
- RE: [Xen-devel] GPLPV memory ballooning and x32, Paul Durrant
- RE: [Xen-devel] GPLPV memory ballooning and x32, James Harper
- RE: [Xen-devel] GPLPV memory ballooning and x32, Aravindh Puthiyaparambil
- Re: [Xen-devel] GPLPV memory ballooning and x32, Keir Fraser
|
|
|