Re: [Xen-users] Not enough memory available

[Peter Braun <xenware@xxxxxxxxx>]

Is that direct paste?

You have typo here:

memroy = 2048

should be

memory = 2048

Peter

2012/8/19 Sandi Romih <romihs.forums@xxxxxxxxx>:
> Hello,
>
> I have encountered a rather strange issue with memory allocation to the
> domU.
>
> I am trying to run FreeBSD in a HVM, my config file is:
>
> [root@xen-srv sandi]# cat /etc/xen/vm/freebsd.cfg
> builder = "hvm"
>
> vcpus = 1
> memroy = 2048
> disk = [
> 'phy:/dev/xen-dom0/freebsd,hda,w'
> ]
> name = "freebsd"
> #vif = ['bridge=xenbr0,mac=00:16:3e:00:af:d8']
> serial = 'pty'
>
>
>  vnc=1
>  vnclisten="0.0.0.0"
>  vncconsole=1
>  vncpasswd=''"
>
> The domU stops at boot with a kernel panic that it has run out of memory.
> The OS only sees 1M or RAM.
>
> Has anyone encountered this, and if so, how does one solve it?
>
> I have tried installing the OS from the install media and using a
> xen-enabled FreeBSD disk image, the result is always the same.
>
> Here are some of the logs:
>
> [root@xen-srv xen]# cat qemu-dm-freebsd.log
> domid: 8
> -videoram option does not work with cirrus vga device model. Videoram set to
> 4M.
> Using file /dev/xen-dom0/freebsd in read-write mode
> Watching /local/domain/0/device-model/8/logdirty/cmd
> Watching /local/domain/0/device-model/8/command
> Watching /local/domain/8/cpu
> char device redirected to /dev/pts/5
> qemu_map_cache_init nr_buckets = 10000 size 4194304
> shared page at pfn feffd
> buffered io page at pfn feffb
> Guest uuid = 00375416-b9c4-433e-9126-50823a1f1047
> populating video RAM at ff000000
> mapping video RAM from ff000000
> Register xen platform.
> Done register platform.
> platform_fixed_ioport: changed ro/rw state of ROM memory area. now is rw
> state.
> xs_read(/local/domain/0/device-model/8/xen_extended_power_mgmt): read error
> Log-dirty: no command yet.
> I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0
> vcpu-set: watch node error.
> xs_read(/local/domain/8/log-throttling): read error
> qemu: ignoring not-understood drive `/local/domain/8/log-throttling'
> medium change watch on `/local/domain/8/log-throttling' - unknown device,
> ignored
> 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.
>
>
>
> Here are the last two entries on the xl-freebsd.log
>
> [root@xen-srv xen]# cat xl-freebsd.log
> xc: info: VIRTUAL MEMORY ARRANGEMENT:
>   Loader:        0000000000100000->00000000001ab4a8
>   TOTAL:         0000000000000000->0000000001800000
>   ENTRY ADDRESS: 0000000000100000
> xc: info: PHYSICAL MEMORY ALLOCATION:
>   4KB PAGES: 0x0000000000000200
>   2MB PAGES: 0x000000000000000b
>   1GB PAGES: 0x0000000000000000
> Waiting for domain freebsd (domid 24) to die [pid 3655]
> Domain 24 has shut down, reason code 1 0x1
> Action for shutdown reason code 1 is restart
> Domain 24 needs to be cleaned up: destroying the domain
> Done. Rebooting now
> xc: info: VIRTUAL MEMORY ARRANGEMENT:
>   Loader:        0000000000100000->00000000001ab4a8
>   TOTAL:         0000000000000000->0000000001800000
>   ENTRY ADDRESS: 0000000000100000
> xc: info: PHYSICAL MEMORY ALLOCATION:
>   4KB PAGES: 0x0000000000000200
>   2MB PAGES: 0x000000000000000b
>   1GB PAGES: 0x0000000000000000
> Waiting for domain freebsd (domid 25) to die [pid 3655]
>
>
> Regards
>
> Sandi
>
> _______________________________________________
> Xen-users mailing list
> Xen-users@xxxxxxxxxxxxx
> http://lists.xen.org/xen-users

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