From: Michal Novotny <minovotn@redhat.com>
To: Keir Fraser <keir.fraser@eu.citrix.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: [PATCH] qemu-xen-3.4-testing: Fix read-only image file handling
Date: Mon, 07 Jun 2010 17:00:31 +0200 [thread overview]
Message-ID: <4C0D098F.9070905@redhat.com> (raw)
In-Reply-To: <C832B6C6.16E61%keir.fraser@eu.citrix.com>
On 06/07/2010 03:46 PM, Keir Fraser wrote:
> On 07/06/2010 14:36, "Michal Novotny"<minovotn@redhat.com> wrote:
>
>
>> 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:
>>
> Try no-tmem on Xen command line.
>
> -- Keir
>
>
>
Keir, I did try:
title Red Hat Enterprise Linux Server (2.6.31.13-xen HV, nolog)
root (hd1,6)
kernel /xen-4.1-unstable.gz no-tmem
module /vmlinuz-2.6.31.13 ro root=LABEL=/rhel2 rhgb quiet selinux=0
module /initrd-2.6.31.13.img
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. Also, the /var/log/xen/xend.log file is
completely empty and I am now unable to see what's going on and I cannot
run `xm list` at all so it was working a little until I restarted but
I'm having many issues here.
Michal
--
Michal Novotny<minovotn@redhat.com>, RHCE
Virtualization Team (xen userspace), Red Hat
next prev parent reply other threads:[~2010-06-07 15:00 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-03 14:04 [PATCH] qemu-xen-3.4-testing: Fix read-only image file handling Michal Novotny
2010-06-03 14:12 ` Michal Novotny
2010-06-04 9:37 ` Michal Novotny
2010-06-04 10:42 ` Pasi Kärkkäinen
2010-06-04 10:57 ` Michal Novotny
2010-06-04 13:00 ` Michal Novotny
2010-06-04 13:11 ` Keir Fraser
2010-06-04 13:12 ` Pasi Kärkkäinen
2010-06-07 11:21 ` Michal Novotny
2010-06-07 11:39 ` Keir Fraser
2010-06-07 13:09 ` Michal Novotny
2010-06-07 13:14 ` Pasi Kärkkäinen
2010-06-07 18:24 ` Jeremy Fitzhardinge
2010-06-07 11:45 ` Pasi Kärkkäinen
2010-06-07 13:10 ` Michal Novotny
2010-06-07 13:14 ` Michal Novotny
2010-06-07 13:19 ` Pasi Kärkkäinen
2010-06-07 13:21 ` Michal Novotny
2010-06-07 13:25 ` Michal Novotny
2010-06-07 13:36 ` Michal Novotny
2010-06-07 13:46 ` Keir Fraser
2010-06-07 15:00 ` Michal Novotny [this message]
2010-06-07 15:17 ` M A Young
2010-06-07 15:28 ` Michal Novotny
2010-06-07 14:56 ` Pasi Kärkkäinen
2010-06-07 15:02 ` Michal Novotny
2010-06-07 16:12 ` Konrad Rzeszutek Wilk
2010-06-07 16:27 ` Michal Novotny
2010-06-07 16:34 ` Keir Fraser
2010-06-07 16:37 ` Michal Novotny
2010-06-07 17:56 ` Keir Fraser
2010-06-08 10:04 ` Michal Novotny
2010-06-08 10:39 ` Michal Novotny
2010-06-08 10:50 ` Keir Fraser
2010-06-08 10:52 ` Michal Novotny
2010-06-08 11:03 ` Keir Fraser
2010-06-08 11:06 ` Michal Novotny
2010-06-08 10:53 ` Keir Fraser
2010-06-08 10:54 ` Michal Novotny
2010-06-08 11:11 ` M A Young
2010-06-08 11:15 ` Michal Novotny
2010-06-07 14:06 ` Pasi Kärkkäinen
2010-06-07 13:25 ` M A Young
[not found] <C82EBB27.16AFC%keir.fraser@eu.citrix.com>
2010-06-04 13:45 ` Michal Novotny
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4C0D098F.9070905@redhat.com \
--to=minovotn@redhat.com \
--cc=keir.fraser@eu.citrix.com \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).