From: "Tom Cranbrook" <tcranbrook@australia.edu>
To: Ian Pratt <Ian.Pratt@cl.cam.ac.uk>,
tcranbrook@australia.edu,
xen-devel@lists.sourceforge.netIan.Pratt@cl.cam.ac.uk
Subject: Re: Follow-up
Date: Mon, 27 Sep 2004 18:14:18 -0400 [thread overview]
Message-ID: <41596c0a.6253.0@australia.edu> (raw)
-----
>> Freeing unused kernel memory: 92k freed
>> Warning: unable to open an initial console.
>> ioperm not fully supported - set iopl to 3
>> ------
>
>It looks like you're not getting message sent to /dev/console.
>
>I don't think you need the extra="console=tty0" -- it should be
>the default.
>
>Can you post the output of trying to create the domain with the
>'-n' flag to do a dry run and print the final config.
>
Using config file "/etc/xen/xmdefconfig".
(vm
(name Xserver)
(memory 64)
(image
(linux
(kernel /boot/vmlinuz-2.6.8.1-xenU)
(ip 192.168.1.61:1.2.3.4:192.168.1.254:255.255.255.0::eth0:off)
(root /dev/hdb1)
(args 4)
)
)
(device (vbd (uname phy:hdb1) (dev hdb1) (mode w)))
(device (vif (mac aa:00:00:2f:59:44)))
)
>> The console freezes.
>>
>> The instance shows on the 'xm list'.
>>
>> xm console xxxx results in:
>> Cannot connect to console 12 in domain 1
>
>This might be because the console is still connected on the other
>terminal.
>
after terminating the other frozzed console, I get this on xm console
************ REMOTE CONSOLE: CTRL-] TO QUIT ********
ioperm not fully supported - set iopl to 3
This message is occasionally followed by:
warning: process `update' used the obsolete bdflush system call
Fix your initscripts?
-------------------------------------------------------
This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170
Project Admins to receive an Apple iPod Mini FREE for your judgement on
who ports your project to Linux PPC the best. Sponsored by IBM.
Deadline: Sept. 24. Go here: http://sf.net/ppc_contest.php
next reply other threads:[~2004-09-27 22:14 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-27 22:14 Tom Cranbrook [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-09-28 14:21 Follow-up Tom Cranbrook
2004-09-27 22:59 Follow-up Neugebauer, Rolf
2004-09-27 22:39 Follow-up Tom Cranbrook
2004-09-27 22:46 ` Follow-up Mark A. Williamson
2004-09-27 20:35 Follow-up Tom Cranbrook
2004-09-27 21:11 ` Follow-up Ian Pratt
2004-09-27 21:23 ` Follow-up Keir Fraser
2004-09-27 22:30 ` Follow-up Ian Pratt
2004-09-27 21:58 ` Follow-up Mark A. Williamson
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=41596c0a.6253.0@australia.edu \
--to=tcranbrook@australia.edu \
--cc=Ian.Pratt@cl.cam.ac.uk \
--cc=xen-devel@lists.sourceforge.netIan.Pratt \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.