similar to: RE: correction... cannot create 2GB (not 2MB) domU

Using 3.1.2 c/s 15492 on Unisys ES7000 configured with 32 processors and 128 gb memory, I attempted to start a 160 gb domU. The xm create command hangs, as well as any other xm commands that are issued. If I do ctl-c of the hanging xm create command, I am able to terminate it and then xm commands are once again functional. I expected to get an error that there was not enough memory available

The host server halts upon shutdown of 126000mb domU (64-bit SLES10). It booted fine and was able to run kernbench. However, during shutdown the host crashes. Host is Unisys ES7000 host with 32 processors and 128gb memory using x86_64 SLES10 with xen-unstable c/s 15080. Reducing the memory allocation for the domU to 124000mb works fine. My guess is that specifying 126000 does not leave

Hello, this is my scenario: 1)I've created a Pacemaker cluster with the following ocfs package on opensuse 11.3 64bit ocfs2console-1.8.0-2.1.x86_64 ocfs2-tools-o2cb-1.8.0-2.1.x86_64 ocfs2-tools-1.8.0-2.1.x86_64 2)I've configured the cluster as usual : <resources> <clone id="dlm-clone"> <meta_attributes id="dlm-clone-meta_attributes">

I am getting the following error when I try to bring up Mini-OS on x86_64 Xen (unstable: 9994). It is dying in xc_linux_build() causing xend to fault and restart. Any clue why this happening? Has something changed in the builder that Mini-OS needs to be aware of? PS: I tried reverting changeset 9993 (Allow linking of mini-os with application-specific object code), but still got the same error

I am seeing a strange issue while running Mini-OS on the changeset 9906:a95e677073c1. This is on both i386 and x86_64. The only difference being on i386 if I stop printing to the console, this issue is not manifested. But with x86_64 it happens all the time. Bringing up Mini-OS for the first time causes xm to hang on certain commands like "list, destroy". Other commands like

Hi! Say I export an LVM logical volume from dom0 as /dev/xvda to the domU: disk = [ ''phy:xenimages/stan,xvda,w'' ] No I can lvresize xenimages/stan in dom0, but the domU stays ignorant of this change. How could I propagate the resize to the domU without rebooting or temporarily breaking its connection to /dev/xvda? Sort of a SCSI rescan, perhaps? -- Thanks, Feri.

Once last night and the night before a XenU go into a Zombie state, requiring a reboot. I''m not quite sure what is happening, and am looking for advise on how to diagnose the problem. .. While writing this email, it crashed again. This time I had an ''xm console calcutta'' capturing the output. I read a suggestion in these archives suggesting that I can just

Hi, I''ve tried to do "xm save" on my Windows XP guest, which runs by ioemu. When I did this, #xm save 6 /xenimages/snapshot1 Error: /usr/lib/xen/bin/xc_save 10 19 6 0 0 0 failed xend.log: [2006-10-06 16:34:22 xend] DEBUG (XendCheckpoint:80) [xc_save]: /usr/lib/xen/bin/xc_save 10 19 6 0 0 0 [2006-10-06 16:34:23 xend] ERROR (XendCheckpoint:227) Couldn''t map

Package: xen-hypervisor-3.0-i386 Version: 3.0.2+hg9681-1 Severity: important Have been trying to get NetBSD to run under debian unstable with the debian supplied hypervisor. Using the 3.0.2-2 hypervisor supplied by XenSource, it works just fine. Because the install process overrides other things, reverified with debian hypervisor afterwards and symptom continues. Attaching the netbsd.cfg and the

----- Forwarded message from pakrat <pakrat@private.neotoma.org> ----- Forwarding to list without attachments. From: pakrat <pakrat@private.neotoma.org> To: Debian Bug Tracking System <submit@bugs.debian.org> Subject: xen-hypervisor-3.0-i386: cannot start NetBSD-HEAD X-Neotoma-Consulting-MailScanner: Found to be clean X-Neotoma-Consulting-MailScanner-From:

All. I am running Xen on an ES7000 system with 4 procs and 4 GB memory. I am running Suse Sles-9 (32-bit) on the machine. I have compiled Xen (the tip on the unstable tree : 6552) with PAE enabled (XEN_TARGET_X86_PAE=y). The system boots fine. I started xend and when I tried to bring up a virtual machine, the system gave me the following error on the command line. On the serial port, I saw an

Hello, We''re running Xen Unstable changeset 15468 with SLES10 on a Unisys ES7000/one 56x cpu and 160GB memory. Xen is built with NR_DYNIRQS=1024 and max_phys_cpus=64, and booted with dom0_mem=1024 and xenheap_megabytes=64. We have 320 para-virtualized SLES10 VMs on external storage. Our script starts a VM, waits for the start to complete, then starts the next: "for i in *.cfg;

Hello, on my xen host, Debian 5.0 I have few domU''s running, most of them are Lenny''s, a couple is running at Etch (Debian 4.0). All domU''s are running stable except of one (Etch / Debian 4.0). This one crashes almost daily and I wasn''t able figure out the reason why. Inside the domU there is nothing installed except of base system and Zimbra ZCS 5.0 and its

Hello, yesterday a coworker had to reboot one VM, the Vm did shutdown but never came back up. We are USing CentOS 5.1 and XEN xen-3.0-x86_64. What can be the reason of this behavior? Here ist the part of the logfile: [2008-07-02 15:04:18 xend.XendDomainInfo 31150] INFO (XendDomainInfo:947) Domain has shutdown: name=auto-input-vm1 id=26 reason=reboot. [2008-07-02 15:04:18 xend.XendDomainInfo

Hi, I have Xen (unstable) on two Debian Sarge 2.4.27 systems, one of which is an nfs server and the other the nfs client. I am trying to set up NFS root so that I can live migrate my domains from one to another. My /etc/exports on N1(10.5.144.29) /myfs1/foo 10.5.144.27(rw,sync,no_root_squash) 10.5.144.29(rw,sync,no_root_squash) 10.5.144.30(rw,sync,no_root_squash) My /hosts.allow on N1

Hi all, after upgrading from xen 3.0 to xen 3.2 I cannot start my domUs: I get: VmError: Boot loader didn''t return any data! Suggestions? This is the log [2008-06-25 11:24:53 2755] DEBUG (XendDomainInfo:84) XendDomainInfo.create([''vm'', [''name'', ''engtest3.infolan''], [''memory'', ''2048''],

Hello, I''m trying to get a freebsd virtual machine running following : http://www.yuanjue.net/xen/howto.html But I get : # xm create freebsd_xen_INSTALL -c Using config file "./freebsd_xen_INSTALL". Error: (14, ''Bad address'') Am I missing something? I am using xen 3.0.4. Thanks and regards, Sergi .... log output from xend.log: [2007-02-27 12:46:59

Hi all, when i try to create a new virtual machine in a new instalation of xen3.4 ( compiled from source) i get this error: xm create windows2.hvm Using config file "./windows2.hvm". Error: Domain ''y'' does not exist. And this is the log: [2009-06-25 17:59:42 13862] TRACE (XendDomainInfo:291) domain_getinfo(2) failed, ignoring: (3, ''No such process'')

When I try to use stubdom-dm in lieu of qemu-dm, the guest domain crashes almost immediately if I specify an emulated NIC (''vif='') in the guest configuration file. If I don''t specify a vif, it works fine. If I use the same configuration with qemu-dm instead of sutbdom-dm, it works fine. Is there some reason QEMU emulated networking doesn''t work with stub domains

Hi, this is a repost of a previous question - since then I have tried rebuilding my Xen0 kernel numerous times and trying different configurations, but I haven''t yet ever got a single DomU to boot so I really don''t even know what is supposed to happen, let alone how to start debugging it... Can someone please speculate on how to debug this further? It''s a gentoo