RE: [Fedora-xen] virt-manager gives "The console is currentlyunavailable" in FC6
by Ranganathan, Shobha
# virsh dumpxml xenbox_G1FC5 | grep graphics
<graphics type='vnc' port='5900'/>
# netstat -t -a -n -p | grep qemu
tcp 0 0 127.0.0.1:5900 0.0.0.0:*
LISTEN 4517/qemu-dm
# ps -axuww | grep qemu
root 4517 0.3 0.4 32452 3324 ? Sl 17:53 0:01
/usr/lib64/xen/bin/qemu-dm -d 1 -m 256 -boot d -acpi -domain-name
xenbox_G1FC5 -net nic,vlan=1,macaddr=00:16:3e:4a:0d:50,model=rtl8139
-net tap,vlan=1,bridge=xenbr0 -vncunused -k en-us -vnclisten 127.0.0.1
I did try commenting the ::1 entry in /etc/hosts file. I still see this
issue.
Regards
Shobha Ranganathan
"The significant challenges we face cannot be resolved at the same level
of thinking we were at when we created them." Albert Einstein
-----Original Message-----
From: Daniel P. Berrange [mailto:berrange@redhat.com]
Sent: Tuesday, November 14, 2006 5:51 PM
To: Ranganathan, Shobha
Cc: Robert Thiem; fedora-xen(a)redhat.com
Subject: Re: [Fedora-xen] virt-manager gives "The console is
currentlyunavailable" in FC6
On Tue, Nov 14, 2006 at 05:45:17PM -0800, Ranganathan, Shobha wrote:
> Anyway I'd suggest:
> - Check that you can ping localhost
> I could ping the localhost
>
> - Check there's a localhost entry in /etc/hosts associated with
> 127.0.0.1
> (and not with ::1)
> I have two entries one with 127.0.0.1 and ::1. I went ahead and
> commented out ::1 entry
> - Run "netstat -antp" to see what ports programs are listening on
> I see various services on IP address of the local host 172.xx.xx.xx
and
> 127.0.0.1 and ::22 and ::1 and 0.0.0.0
>
> I see sshd, cupsd and hpiod running with local address as ::22, ::1
and
> 0.0.0.0.
For fully-virt / HVM guests you should see a 'qemu-dm' process
listening
on the port associated with VNC (something around 5900+). If you don't
then this is the primary problem to address - the qemu-dm*log file may
be useful. Also grabbing the command line for qemu-dm active process
should indicate what port it tried to start on. In my case:
# virsh dumpxml rhel4i386 | grep graphics
<graphics type='vnc' port='5900'/>
# ps -axuww | grep qemu
root 4005 0.0 0.1 64616 5132 ? Sl 20:05 0:00
/usr/lib64/xen/bin/qemu-dm -d 2 -m 500 -boot c -serial pty -vcpus 4
-acpi -domain-name rhel4i386 -net
nic,vlan=1,macaddr=00:16:3e:39:f9:76,model=rtl8139 -net
tap,vlan=1,bridge=xenbr0 -vncunused -k en-us -vnclisten 127.0.0.1
# netstat -t -a -n -p | grep qemu
tcp 0 0 127.0.0.1:5900 0.0.0.0:*
LISTEN 4005/qemu-dm
# virsh dumpxml rhel4i386 | grep graphics
<graphics type='vnc' port='5900'/>
Regards,
Dan.
--
|=- Red Hat, Engineering, Emerging Technologies, Boston. +1 978 392
2496 -=|
|=- Perl modules: http://search.cpan.org/~danberr/
-=|
|=- Projects: http://freshmeat.net/~danielpb/
-=|
|=- GnuPG: 7D3B9505 F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505
-=|
17 years, 5 months
RE: [Fedora-xen] virt-manager gives "The console is currentlyunavailable" in FC6
by Ranganathan, Shobha
Anyway I'd suggest:
- Check that you can ping localhost
I could ping the localhost
- Check there's a localhost entry in /etc/hosts associated with
127.0.0.1
(and not with ::1)
I have two entries one with 127.0.0.1 and ::1. I went ahead and
commented out ::1 entry
- Run "netstat -antp" to see what ports programs are listening on
I see various services on IP address of the local host 172.xx.xx.xx and
127.0.0.1 and ::22 and ::1 and 0.0.0.0
I see sshd, cupsd and hpiod running with local address as ::22, ::1 and
0.0.0.0.
Regards
Shobha Ranganathan
"The significant challenges we face cannot be resolved at the same level
of thinking we were at when we created them." Albert Einstein
-----Original Message-----
From: fedora-xen-bounces(a)redhat.com
[mailto:fedora-xen-bounces@redhat.com] On Behalf Of Daniel P. Berrange
Sent: Tuesday, November 14, 2006 5:28 PM
To: Robert Thiem
Cc: fedora-xen(a)redhat.com
Subject: Re: [Fedora-xen] virt-manager gives "The console is
currentlyunavailable" in FC6
On Wed, Nov 15, 2006 at 11:23:20AM +1000, Robert Thiem wrote:
> When first setting up FC6 I had an issue where I could start an FC6
Xen
> guest install but couldn't connect with VNC.
>
> I don't know if it's the same (I can't remember the exact messages I
was
> getting), but it ended up being that "localhost" wouldn't resolve to
an
> IPv4 address. This was due to a nasty combination of anaconda putting
IPv4
> and v6 entries in /etc/hosts and system-config-network trimming the
> "extra" v4 entry when run.
>
> Anyway I'd suggest:
> - Check that you can ping localhost
> - Check there's a localhost entry in /etc/hosts associated with
127.0.0.1
> (and not with ::1)
> - Run "netstat -antp" to see what ports programs are listening on
Ahhh, that would certainly make sense - virt-manager explicitly connects
to 'localhost' when opening the VNC connection. Since the VNC server
doesn't support IPv6, I think it'd be fairly safe for me to switch
virt-manager to explicitly use '127.0.0.1' which would eliminate this
particularly /etc/hosts issue.
Thanks for the info about the issue.
Regards,
Dan.
--
|=- Red Hat, Engineering, Emerging Technologies, Boston. +1 978 392
2496 -=|
|=- Perl modules: http://search.cpan.org/~danberr/
-=|
|=- Projects: http://freshmeat.net/~danielpb/
-=|
|=- GnuPG: 7D3B9505 F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505
-=|
--
Fedora-xen mailing list
Fedora-xen(a)redhat.com
https://www.redhat.com/mailman/listinfo/fedora-xen
17 years, 5 months
Building and booting Dom0 in FC6
by Eduri, Eswar M
Hello there,
I am trying to build Xen0 image based on FC6 release. I have copied
kernel-2.6.18-i686-xen.config into a local directory and was able to
build Linux kernel with this configuration file. This gave me vmlinuz
file ready for Xen0 execution.
Now, I believe I would need an initrd to go with this image so that Xen0
boots up. What should I do? I don't want to run 'make install
module_install' and overwrite my existing configuration.
This seems like basic stuff - is there some obvious documentation I am
missing I should refer to?
Thanks a lot for your help.
17 years, 5 months
RE: [Fedora-xen] virt-manager gives "The console is currently unavailable" in FC6
by Ranganathan, Shobha
I built Xen the way the README specifies. So although FC6 is 2.6.18, I
get it built against 2.6.16.29
So uname -a yields 2.6.16.29-xen. I have kernel-xen version as this
My xen version is xen-3.0.3-rc3 src rpm that comes with FC6.
I installed libvirt-0.1.7-2.i386.rpm (again this comes with FC6).
Virt-manager version is 0.2.3 from the About button of the GUI.
I always login as root in these machines.
When I tried it again this time , I still get same results.
Regards
Shobha Ranganathan
"The significant challenges we face cannot be resolved at the same level
of thinking we were at when we created them." Albert Einstein
-----Original Message-----
From: Daniel P. Berrange [mailto:berrange@redhat.com]
Sent: Tuesday, November 14, 2006 3:57 PM
To: Ranganathan, Shobha
Cc: fedora-xen(a)redhat.com
Subject: Re: [Fedora-xen] virt-manager gives "The console is currently
unavailable" in FC6
On Tue, Nov 14, 2006 at 10:53:59AM -0800, Ranganathan, Shobha wrote:
> Yes there is qemu-dm process running.
Great.
> I see a line in "virsh dumpxml xen_FC5G1"
> <graphics type='vnc' port='5900'/>
>
> From the log file of virt-manager I have
>
> DEBUG Graphics vnc://localhost:5902
> ERROR Unable to activate console socket.error(111,'Connection
refused')
Ok, that's a very odd situation - virsh is saying port 5900 is where the
VNC server is (which sounds plausible), but virt-manager is trying to
connect to 5902 (which sounds like old, hardcoded port behaviour).
Could you tell me what version of kernel-xen, xen, libvirt &
virt-manager
RPMs you have installed in the host.
If you close the console window & re-open it, I assume it still fails
to connect again, with same error message in the logs ?
> In the /etc/xen/xen_FC5G1, I do have vnc=1 and vncunused=1.
Ok, that's good - so port 5900 is definitely the desired port.
Oh, are you running 'virsh' and 'virt-manager' as root, or a normal user
?
Regards,
Dan.
--
|=- Red Hat, Engineering, Emerging Technologies, Boston. +1 978 392
2496 -=|
|=- Perl modules: http://search.cpan.org/~danberr/
-=|
|=- Projects: http://freshmeat.net/~danielpb/
-=|
|=- GnuPG: 7D3B9505 F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505
-=|
17 years, 5 months
RE: [Fedora-xen] virt-manager gives "The console is currently unavailable" in FC6
by Ranganathan, Shobha
I had a typo in my previous message.
I see no errors in xend.log and xend-debug.log.
But I do have qemu*log messages. For my last problem, I only see the
following
Domid: 2
Shared page at pfn:ffff, mfn:34cd5
Buffered io page at pfn:fffd, mfn:34cd7
Regards
Shobha Ranganathan
"The significant challenges we face cannot be resolved at the same level
of thinking we were at when we created them." Albert Einstein
-----Original Message-----
From: Daniel P. Berrange [mailto:berrange@redhat.com]
Sent: Monday, November 13, 2006 5:24 PM
To: Ranganathan, Shobha
Cc: fedora-xen(a)redhat.com
Subject: Re: [Fedora-xen] virt-manager gives "The console is currently
unavailable" in FC6
On Mon, Nov 13, 2006 at 05:08:48PM -0800, Ranganathan, Shobha wrote:
> I am trying to install unmodified guest FC5 in host Os FC6.
>
> I am using virt-manager and upon gathering all information, when I
click
> finish, the GUI shows me "The console is currently unavailable".
This basically means that virt-manager was unable to successfully
connect
to the VNC server which exports the guest framebuffer / console. Since
you say this is with fully virt, it probably means that the qemu-dm
process
failed to startup correctly - since VNC itself rarely fails I imagine
some
other bit of the guest config broke - network / disk setup being most
likely
>
> What is wrong ? xm list shows the guest as blocked. I see error
messages
> in xend-debug.log and xend.log
What are the errors you see - they may well help diagnose the problem
you are encountering ? Also check for /var/log/xen/qemu-dm*.log for
info about the fully-virt device model startup
Regards,
Dan.
--
|=- Red Hat, Engineering, Emerging Technologies, Boston. +1 978 392
2496 -=|
|=- Perl modules: http://search.cpan.org/~danberr/
-=|
|=- Projects: http://freshmeat.net/~danielpb/
-=|
|=- GnuPG: 7D3B9505 F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505
-=|
17 years, 5 months
RE: [Fedora-xen] virt-manager gives "The console is currently unavailable" in FC6
by Ranganathan, Shobha
Yes there is qemu-dm process running.
I see a line in "virsh dumpxml xen_FC5G1"
<graphics type='vnc' port='5900'/>
>From the log file of virt-manager I have
DEBUG Graphics vnc://localhost:5902
ERROR Unable to activate console socket.error(111,'Connection refused')
In the /etc/xen/xen_FC5G1, I do have vnc=1 and vncunused=1.
Regards
Shobha Ranganathan
"The significant challenges we face cannot be resolved at the same level
of thinking we were at when we created them." Albert Einstein
-----Original Message-----
From: Daniel P. Berrange [mailto:berrange@redhat.com]
Sent: Monday, November 13, 2006 8:04 PM
To: Ranganathan, Shobha
Cc: fedora-xen(a)redhat.com
Subject: Re: [Fedora-xen] virt-manager gives "The console is currently
unavailable" in FC6
On Mon, Nov 13, 2006 at 06:03:17PM -0800, Ranganathan, Shobha wrote:
> I had a typo in my previous message.
>
> I see no errors in xend.log and xend-debug.log.
Ok, that's good - can you see if there is a qemu-dm process running,
eg
ps -auxfww | grep qemu-dm
> But I do have qemu*log messages. For my last problem, I only see the
> following
> Domid: 2
> Shared page at pfn:ffff, mfn:34cd5
> Buffered io page at pfn:fffd, mfn:34cd7
Looks reasonable. Can you see if there is a '<graphics>' block
in the XML when you run
'virsh dumpxml <domain name>'
For the domain that you failed to get a console on. Also make sure that
in the /etc/xen/<domain name> there is a 'vnc=1' config option. Finally,
take a look at /root/.virt-manager/virt-manager.log to see if there's
any errors reported.
> -----Original Message-----
> From: Daniel P. Berrange [mailto:berrange@redhat.com]
> Sent: Monday, November 13, 2006 5:24 PM
> To: Ranganathan, Shobha
> Cc: fedora-xen(a)redhat.com
> Subject: Re: [Fedora-xen] virt-manager gives "The console is currently
> unavailable" in FC6
>
> On Mon, Nov 13, 2006 at 05:08:48PM -0800, Ranganathan, Shobha wrote:
> > I am trying to install unmodified guest FC5 in host Os FC6.
> >
> > I am using virt-manager and upon gathering all information, when I
> click
> > finish, the GUI shows me "The console is currently unavailable".
>
> This basically means that virt-manager was unable to successfully
> connect
> to the VNC server which exports the guest framebuffer / console. Since
> you say this is with fully virt, it probably means that the qemu-dm
> process
> failed to startup correctly - since VNC itself rarely fails I imagine
> some
> other bit of the guest config broke - network / disk setup being most
> likely
>
> >
> > What is wrong ? xm list shows the guest as blocked. I see error
> messages
> > in xend-debug.log and xend.log
>
> What are the errors you see - they may well help diagnose the problem
> you are encountering ? Also check for /var/log/xen/qemu-dm*.log for
> info about the fully-virt device model startup
Regards,
Dan.
--
|=- Red Hat, Engineering, Emerging Technologies, Boston. +1 978 392
2496 -=|
|=- Perl modules: http://search.cpan.org/~danberr/
-=|
|=- Projects: http://freshmeat.net/~danielpb/
-=|
|=- GnuPG: 7D3B9505 F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505
-=|
17 years, 5 months
RE: [Fedora-xen] virt-manager gives "The console is currently unavailable" in FC6
by Ranganathan, Shobha
This means that this is FC6 specific.
I have had successful installations on FC6 Test2 .
Any suggestions/workarounds possible to install unmodified guest ?
I am in dire need for a solution.
Regards
Shobha Ranganathan
"The significant challenges we face cannot be resolved at the same level
of thinking we were at when we created them." Albert Einstein
-----Original Message-----
From: fedora-xen-bounces(a)redhat.com
[mailto:fedora-xen-bounces@redhat.com] On Behalf Of Laurent Flesch
Sent: Tuesday, November 14, 2006 12:45 PM
To: fedora-xen(a)redhat.com
Subject: Re: [Fedora-xen] virt-manager gives "The console is
currentlyunavailable" in FC6
Hi,
After a new check, it looks like I have exactly the same problem than
your with the same logs.
I found no solution for the moment as making a new FC6 installation.
Best Regards
2006/11/14, Ranganathan, Shobha <shobha.ranganathan(a)intel.com>:
Yes there is qemu-dm process running.
I see a line in "virsh dumpxml xen_FC5G1"
<graphics type='vnc' port='5900'/>
>From the log file of virt-manager I have
DEBUG Graphics vnc://localhost:5902
ERROR Unable to activate console socket.error(111,'Connection refused')
In the /etc/xen/xen_FC5G1, I do have vnc=1 and vncunused=1.
Regards
Shobha Ranganathan
"The significant challenges we face cannot be resolved at the same level
of thinking we were at when we created them." Albert Einstein
-----Original Message-----
From: Daniel P. Berrange [mailto:berrange@redhat.com]
Sent: Monday, November 13, 2006 8:04 PM
To: Ranganathan, Shobha
Cc: fedora-xen(a)redhat.com
Subject: Re: [Fedora-xen] virt-manager gives "The console is currently
unavailable" in FC6
On Mon, Nov 13, 2006 at 06:03:17PM -0800, Ranganathan, Shobha wrote:
> I had a typo in my previous message.
>
> I see no errors in xend.log and xend-debug.log.
Ok, that's good - can you see if there is a qemu-dm process running,
eg
ps -auxfww | grep qemu-dm
> But I do have qemu*log messages. For my last problem, I only see the
> following
> Domid: 2
> Shared page at pfn:ffff, mfn:34cd5
> Buffered io page at pfn:fffd, mfn:34cd7
Looks reasonable. Can you see if there is a '<graphics>' block
in the XML when you run
'virsh dumpxml <domain name>'
For the domain that you failed to get a console on. Also make sure that
in the /etc/xen/<domain name> there is a 'vnc=1' config option. Finally,
take a look at /root/.virt-manager/virt-manager.log to see if there's
any errors reported.
> -----Original Message-----
> From: Daniel P. Berrange [mailto:berrange@redhat.com ]
> Sent: Monday, November 13, 2006 5:24 PM
> To: Ranganathan, Shobha
> Cc: fedora-xen(a)redhat.com
> Subject: Re: [Fedora-xen] virt-manager gives "The console is currently
> unavailable" in FC6
>
> On Mon, Nov 13, 2006 at 05:08:48PM -0800, Ranganathan, Shobha wrote:
> > I am trying to install unmodified guest FC5 in host Os FC6.
> >
> > I am using virt-manager and upon gathering all information, when I
> click
> > finish, the GUI shows me "The console is currently unavailable".
>
> This basically means that virt-manager was unable to successfully
> connect
> to the VNC server which exports the guest framebuffer / console. Since
> you say this is with fully virt, it probably means that the qemu-dm
> process
> failed to startup correctly - since VNC itself rarely fails I imagine
> some
> other bit of the guest config broke - network / disk setup being most
> likely
>
> >
> > What is wrong ? xm list shows the guest as blocked. I see error
> messages
> > in xend-debug.log and xend.log
>
> What are the errors you see - they may well help diagnose the problem
> you are encountering ? Also check for /var/log/xen/qemu-dm*.log for
> info about the fully-virt device model startup
Regards,
Dan.
--
|=- Red Hat, Engineering, Emerging Technologies, Boston. +1 978 392
2496 -=|
|=- Perl modules: http://search.cpan.org/~danberr/
-=|
|=- Projects: http://freshmeat.net/~danielpb/
-=|
|=- GnuPG: 7D3B9505 F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505
-=|
--
Fedora-xen mailing list
Fedora-xen(a)redhat.com
https://www.redhat.com/mailman/listinfo/fedora-xen
17 years, 5 months
Win Xp 32 bit as guest in
by Denis Forveille
Q:
- is it possible to run an instance of Win XP SP2 32bits as a guest on a
x86_64 FC6 fully updated dom0? (CPU = AMD x2 4600 with pacifica...)
I successfully installed Win XP in an lvm logical volume. Everything
worked fine and at the end, I got the request from XP asking to remove
the CD and reboot...
Then, when I try to start the guest (after changing the line from boot=d
to boot=c in the config file), the only thing I see is a black screen.
(the windows resize itself and then a black screen...)
"xm top" shows that the guest consumes 0% CPU...
I think I've tried almost every combination of parameters in the config
files (pae, acpi,sdl...) during installation and after...
Also, I've seen that others have post similar problems in this forum,
but none of them have answers/workarounds to my problem.
Does anyone succeeded in running such a combination (ie XP SP2 32 bits
in a 64bit FC6)?
Or maybe the problems comes from the fcat that I installed windows in an
lvm instead of in a file?
Thx in advance
17 years, 5 months
"KBD: unsupported int 16h function 03" -- is the keyboard in Intel Mac system not supported in FC6 Xen ?
by Ranganathan, Shobha
I am trying to install FC5 guest in FC6 host in x86 mode.
I am using virt-manager to install fully virt guest.
I get in "xm dmesg", that "KBD: unsupported int 16h function 03".
Does this mean that my keyboard is not getting recognized properly ?
Regards
Shobha Ranganathan
"The significant challenges we face cannot be resolved at the same level
of thinking we were at when we created them." Albert Einstein
17 years, 5 months
virt-manager gives "The console is currently unavailable" in FC6
by Ranganathan, Shobha
I am trying to install unmodified guest FC5 in host Os FC6.
I am using virt-manager and upon gathering all information, when I click
finish, the GUI shows me "The console is currently unavailable".
What is wrong ? xm list shows the guest as blocked. I see error messages
in xend-debug.log and xend.log
Regards
Shobha Ranganathan
"The significant challenges we face cannot be resolved at the same level
of thinking we were at when we created them." Albert Einstein
17 years, 5 months
