Mailing List Archive: Xen: Users

xm console command doesn't work

Index | Next | Previous | View Threaded

jefranca at gmail

Aug 1, 2012, 10:40 AM

Post #1 of 11 (1411 views)
Permalink

xm console command doesn't work

Hi Guys,

I'm working with xen 4.1, dom0 ubuntu kernel 3.2 and domU-PV ubuntu-precise.
Well... xm console command doesn't work. I read <
http://wiki.xen.org/wiki/Xen_Common_Problems> and I can't resolve.

How can I fix this problem?
Thanks

MY guest.cfg in /etc/xen/ubuntu.cfg
name = "ubuntu-pv"

memory = 256

disk = ['phy:/dev/labprog/ubuntu-pv,xvda,w']
vif = [' ']

bootloader = "pygrub"

#kernel = "/var/lib/xen/images/ubuntu-netboot/vmlinuz"
#ramdisk = "/var/lib/xen/images/ubuntu-netboot/initrd.gz"
#extra = "debian-installer/exit/always_halt=true -- console=hvc0"

MY dom0 /etc/init/hvc0.conf
# hvc0 - getty
#
# This service maintains a getty on hvc0 from the point the system is
# started until it is shut down again.

start on stopped rc RUNLEVEL=[2345] and (
not-container or
container CONTAINER=lxc or
container CONTAINER=lxc-libvirt)

stop on runlevel [!2345]

respawn exec /sbin/getty -L hvc0 9600 linux

itobin at tidyhosts

Aug 1, 2012, 12:30 PM

Post #2 of 11 (1376 views)
Permalink

Re: xm console command doesn't work [In reply to]

Hi,

Why don't you xl console instead? Xm is being phased out.

Thanks

Ian

From: xen-users-bounces [at] lists [mailto:xen-users-bounces [at] lists] On Behalf Of José Eduardo França
Sent: 01 August 2012 18:41
To: xen-users [at] lists
Subject: [Xen-users] xm console command doesn't work

Hi Guys,

I'm working with xen 4.1, dom0 ubuntu kernel 3.2 and domU-PV ubuntu-precise.
Well... xm console command doesn't work. I read <http://wiki.xen.org/wiki/Xen_Common_Problems> and I can't resolve.

How can I fix this problem?
Thanks

MY guest.cfg in /etc/xen/ubuntu.cfg
name = "ubuntu-pv"

memory = 256

disk = ['phy:/dev/labprog/ubuntu-pv,xvda,w']
vif = [' ']

bootloader = "pygrub"

#kernel = "/var/lib/xen/images/ubuntu-netboot/vmlinuz"
#ramdisk = "/var/lib/xen/images/ubuntu-netboot/initrd.gz"
#extra = "debian-installer/exit/always_halt=true -- console=hvc0"

MY dom0 /etc/init/hvc0.conf
# hvc0 - getty
#
# This service maintains a getty on hvc0 from the point the system is
# started until it is shut down again.

start on stopped rc RUNLEVEL=[2345] and (
not-container or
container CONTAINER=lxc or
container CONTAINER=lxc-libvirt)

stop on runlevel [!2345]

respawn exec /sbin/getty -L hvc0 9600 linux

lukas at laukamp

Aug 1, 2012, 12:59 PM

Post #3 of 11 (1375 views)
Permalink

Re: xm console command doesn't work [In reply to]

Am 01.08.2012 21:30, schrieb Ian Tobin:
>
> Hi,
>
> Why don't you xl console instead? Xm is being phased out.
>
> Thanks
>
> Ian
>
> *From:*xen-users-bounces [at] lists
> [mailto:xen-users-bounces [at] lists] *On Behalf Of *José Eduardo
> França
> *Sent:* 01 August 2012 18:41
> *To:* xen-users [at] lists
> *Subject:* [Xen-users] xm console command doesn't work
>
> Hi Guys,
>
> I'm working with xen 4.1, dom0 ubuntu kernel 3.2 and domU-PV
> ubuntu-precise.
> Well... xm console command doesn't work. I read
> <http://wiki.xen.org/wiki/Xen_Common_Problems> and I can't resolve.
>
> How can I fix this problem?
> Thanks
>
> MY guest.cfg in /etc/xen/ubuntu.cfg
> name = "ubuntu-pv"
>
> memory = 256
>
> disk = ['phy:/dev/labprog/ubuntu-pv,xvda,w']
> vif = [' ']
>
> bootloader = "pygrub"
>
> #kernel = "/var/lib/xen/images/ubuntu-netboot/vmlinuz"
> #ramdisk = "/var/lib/xen/images/ubuntu-netboot/initrd.gz"
> #extra = "debian-installer/exit/always_halt=true -- console=hvc0"
>
>
> MY dom0 /etc/init/hvc0.conf
> # hvc0 - getty
> #
> # This service maintains a getty on hvc0 from the point the system is
> # started until it is shut down again.
>
> start on stopped rc RUNLEVEL=[2345] and (
> not-container or
> container CONTAINER=lxc or
> container CONTAINER=lxc-libvirt)
>
> stop on runlevel [!2345]
>
> respawn exec /sbin/getty -L hvc0 9600 linux
>
>
>
> _______________________________________________
> Xen-users mailing list
> Xen-users [at] lists
> http://lists.xen.org/xen-users

Hey all,

he could also use the xl toolstack but the simple misstake is that the
hvc0.conf isn't needed in Dom0. The hvc0.conf is needed inside of the
DomU and in the config file must be set extra = 'console=hvc0' so that
the console kernel option for hvc0 is set. So the DomU can boot into a
hvc0 console and than xm and xl can use the console.

Best Regards

Ian.Campbell at citrix

Aug 2, 2012, 12:16 AM

Post #4 of 11 (1370 views)
Permalink

Re: xm console command doesn't work [In reply to]

On Wed, 2012-08-01 at 20:59 +0100, Lukas Laukamp wrote:
>
> he could also use the xl toolstack but the simple misstake is that the
> hvc0.conf isn't needed in Dom0. The hvc0.conf is needed inside of the
> DomU and in the config file must be set extra = 'console=hvc0' so that
> the console kernel option for hvc0 is set. So the DomU can boot into a
> hvc0 console and than xm and xl can use the console.

pygrub should be getting the console=hvc0 from the grub cfg and
hvc0.conf ought to already exist.

If Ubuntu isn't setting these up by default during install when running
under Xen then this should be reported as a bug to Ubuntu.

I'm not familiar with current Ubuntu so I don't know if these are
expected to be there i.e. I don't know if this is a wishlist/new-feature
bug or just a bug in functionality which is expected to Just Work
already.

Ian.

_______________________________________________
Xen-users mailing list
Xen-users [at] lists
http://lists.xen.org/xen-users

s.seitz at netzhaut

Aug 2, 2012, 12:57 AM

Post #5 of 11 (1363 views)
Permalink

Re: xm console command doesn't work [In reply to]

Am Donnerstag, den 02.08.2012, 08:16 +0100 schrieb Ian Campbell:

> On Wed, 2012-08-01 at 20:59 +0100, Lukas Laukamp wrote:
> >
> > he could also use the xl toolstack but the simple misstake is that the
> > hvc0.conf isn't needed in Dom0. The hvc0.conf is needed inside of the
> > DomU and in the config file must be set extra = 'console=hvc0' so that
> > the console kernel option for hvc0 is set. So the DomU can boot into a
> > hvc0 console and than xm and xl can use the console.
>
> pygrub should be getting the console=hvc0 from the grub cfg and
> hvc0.conf ought to already exist.
>
> If Ubuntu isn't setting these up by default during install when running
> under Xen then this should be reported as a bug to Ubuntu.
>
> I'm not familiar with current Ubuntu so I don't know if these are
> expected to be there i.e. I don't know if this is a wishlist/new-feature
> bug or just a bug in functionality which is expected to Just Work
> already.
>
> Ian.
>

Current (12.04 LTS) Ubuntu, respectively the 3.2.0 linux-virtual Kernel
as well as the grub-legacy-ec2 are
aware of hvc0.

I think the source of these console problems are the configurable
different presets. One could use tty0
as well as tty1, maybe hvc0 or xvc0 or both of them. The domU I'm
currently peeking into spawns tty0
and hvc0 with tty0 connected to the "serial" xl console and hvc0
connected to vfb/vnc setting. But that
can't be predicted, it's easy to configure it the opposite way.

From my point of view, the definition of virtualization namespaces
(hvcN, xvcN, xvdMN) jumped in far to late.
There have been huge clusters build before one was even thinking about
hvc0.

Just my 2 cents, and I'm sorry that this won't help the OP to solve his
issue easily.

Cheers,

Stephan

Attachments:

signature.asc (0.48 KB)

jefranca at gmail

Aug 3, 2012, 1:41 PM

Post #6 of 11 (1371 views)
Permalink

Re: xm console command doesn't work [In reply to]

Hi all,

I can't still resolve.
How Ian Campbell said the xl console command didn't work.

Well... I tried the script /etc/init/hvc0.conf that Lukas suggested and my
guest.cfg was changed to:
name = "ubuntu-pv"

memory = 256
disk = ['phy:/dev/labprog/ubuntu-pv,xvda,w']
vif = [' ']

bootloader = "pygrub"
*extra = "console=hvc0"*

But, I can't run xm console command. Is there other idea?
Thanks

2012/8/2 Stephan Seitz <s.seitz [at] netzhaut>

> **
>
>
> Am Donnerstag, den 02.08.2012, 08:16 +0100 schrieb Ian Campbell:
>
> On Wed, 2012-08-01 at 20:59 +0100, Lukas Laukamp wrote:
> >
> > he could also use the xl toolstack but the simple misstake is that the
> > hvc0.conf isn't needed in Dom0. The hvc0.conf is needed inside of the
> > DomU and in the config file must be set extra = 'console=hvc0' so that
> > the console kernel option for hvc0 is set. So the DomU can boot into a
> > hvc0 console and than xm and xl can use the console.
>
> pygrub should be getting the console=hvc0 from the grub cfg and
> hvc0.conf ought to already exist.
>
> If Ubuntu isn't setting these up by default during install when running
> under Xen then this should be reported as a bug to Ubuntu.
>
> I'm not familiar with current Ubuntu so I don't know if these are
> expected to be there i.e. I don't know if this is a wishlist/new-feature
> bug or just a bug in functionality which is expected to Just Work
> already.
>
> Ian.
>
>
> Current (12.04 LTS) Ubuntu, respectively the 3.2.0 linux-virtual Kernel
> as well as the grub-legacy-ec2 are
> aware of hvc0.
>
> I think the source of these console problems are the configurable
> different presets. One could use tty0
> as well as tty1, maybe hvc0 or xvc0 or both of them. The domU I'm
> currently peeking into spawns tty0
> and hvc0 with tty0 connected to the "serial" xl console and hvc0 connected
> to vfb/vnc setting. But that
> can't be predicted, it's easy to configure it the opposite way.
>
> From my point of view, the definition of virtualization namespaces (hvcN,
> xvcN, xvdMN) jumped in far to late.
> There have been huge clusters build before one was even thinking about
> hvc0.
>
> Just my 2 cents, and I'm sorry that this won't help the OP to solve his
> issue easily.
>
> Cheers,
>
> Stephan
>
>
>

itobin at tidyhosts

Aug 3, 2012, 2:34 PM

Post #7 of 11 (1362 views)
Permalink

Re: xm console command doesn't work [In reply to]

Hello,

When you say it doesn't work, what isn't working, errors?

Ian

From: José Eduardo França [mailto:jefranca [at] gmail]
Sent: 03 August 2012 21:41
To: Stephan Seitz
Cc: Ian Campbell; Lukas Laukamp; xen-users [at] lists; Ian Tobin
Subject: Re: [Xen-users] xm console command doesn't work

Hi all,

I can't still resolve.
How Ian Campbell said the xl console command didn't work.

Well... I tried the script /etc/init/hvc0.conf that Lukas suggested and my guest.cfg was changed to:
name = "ubuntu-pv"

memory = 256
disk = ['phy:/dev/labprog/ubuntu-pv,xvda,w']

vif = [' ']

bootloader = "pygrub"
extra = "console=hvc0"

But, I can't run xm console command. Is there other idea?
Thanks

2012/8/2 Stephan Seitz <s.seitz [at] netzhaut>

Am Donnerstag, den 02.08.2012, 08:16 +0100 schrieb Ian Campbell:

On Wed, 2012-08-01 at 20:59 +0100, Lukas Laukamp wrote:
>
> he could also use the xl toolstack but the simple misstake is that the
> hvc0.conf isn't needed in Dom0. The hvc0.conf is needed inside of the
> DomU and in the config file must be set extra = 'console=hvc0' so that
> the console kernel option for hvc0 is set. So the DomU can boot into a
> hvc0 console and than xm and xl can use the console.

pygrub should be getting the console=hvc0 from the grub cfg and
hvc0.conf ought to already exist.

If Ubuntu isn't setting these up by default during install when running
under Xen then this should be reported as a bug to Ubuntu.

I'm not familiar with current Ubuntu so I don't know if these are
expected to be there i.e. I don't know if this is a wishlist/new-feature
bug or just a bug in functionality which is expected to Just Work
already.

Ian.

Current (12.04 LTS) Ubuntu, respectively the 3.2.0 linux-virtual Kernel as well as the grub-legacy-ec2 are
aware of hvc0.

I think the source of these console problems are the configurable different presets. One could use tty0
as well as tty1, maybe hvc0 or xvc0 or both of them. The domU I'm currently peeking into spawns tty0
and hvc0 with tty0 connected to the "serial" xl console and hvc0 connected to vfb/vnc setting. But that
can't be predicted, it's easy to configure it the opposite way.

From my point of view, the definition of virtualization namespaces (hvcN, xvcN, xvdMN) jumped in far to late.
There have been huge clusters build before one was even thinking about hvc0.

Just my 2 cents, and I'm sorry that this won't help the OP to solve his issue easily.

Cheers,

Stephan

jefranca at gmail

Aug 5, 2012, 8:15 AM

Post #8 of 11 (1362 views)
Permalink

Re: xm console command doesn't work [In reply to]

Ok

first: when I do command "xm create guest.cfg -c" I can run console
enviroment. Then when I do command "xm console guest" the terminal doesn't
shown nothing. No Errors and I can't run others commands.

2012/8/3 Ian Tobin <itobin [at] tidyhosts>

> Hello,****
>
> ** **
>
> When you say it doesn’t work, what isn’t working, errors?****
>
> ** **
>
> Ian****
>
> ** **
>
> *From:* José Eduardo França [mailto:jefranca [at] gmail]
> *Sent:* 03 August 2012 21:41
> *To:* Stephan Seitz
> *Cc:* Ian Campbell; Lukas Laukamp; xen-users [at] lists; Ian Tobin
> *Subject:* Re: [Xen-users] xm console command doesn't work****
>
> ** **
>
> Hi all,
>
> I can't still resolve.
> How Ian Campbell said the xl console command didn't work.
>
> Well... I tried the script /etc/init/hvc0.conf that Lukas suggested and my
> guest.cfg was changed to:
> name = "ubuntu-pv"
>
> memory = 256
> disk = ['phy:/dev/labprog/ubuntu-pv,xvda,w']****
>
> vif = [' ']
>
> bootloader = "pygrub"
> *extra = "console=hvc0"*****
>
>
> But, I can't run xm console command. Is there other idea?
> Thanks****
>
> 2012/8/2 Stephan Seitz <s.seitz [at] netzhaut>****
>
> Am Donnerstag, den 02.08.2012, 08:16 +0100 schrieb Ian Campbell: ****
>
> On Wed, 2012-08-01 at 20:59 +0100, Lukas Laukamp wrote:****
>
> > ****
>
> > he could also use the xl toolstack but the simple misstake is that the****
>
> > hvc0.conf isn't needed in Dom0. The hvc0.conf is needed inside of the****
>
> > DomU and in the config file must be set extra = 'console=hvc0' so that****
>
> > the console kernel option for hvc0 is set. So the DomU can boot into a****
>
> > hvc0 console and than xm and xl can use the console.****
>
> ** **
>
> pygrub should be getting the console=hvc0 from the grub cfg and****
>
> hvc0.conf ought to already exist.****
>
> ** **
>
> If Ubuntu isn't setting these up by default during install when running****
>
> under Xen then this should be reported as a bug to Ubuntu.****
>
> ** **
>
> I'm not familiar with current Ubuntu so I don't know if these are****
>
> expected to be there i.e. I don't know if this is a wishlist/new-feature****
>
> bug or just a bug in functionality which is expected to Just Work****
>
> already.****
>
> ** **
>
> Ian.****
>
> ** **
>
> Current (12.04 LTS) Ubuntu, respectively the 3.2.0 linux-virtual Kernel as
> well as the grub-legacy-ec2 are
> aware of hvc0.
>
> I think the source of these console problems are the configurable
> different presets. One could use tty0
> as well as tty1, maybe hvc0 or xvc0 or both of them. The domU I'm
> currently peeking into spawns tty0
> and hvc0 with tty0 connected to the "serial" xl console and hvc0 connected
> to vfb/vnc setting. But that
> can't be predicted, it's easy to configure it the opposite way.
>
> From my point of view, the definition of virtualization namespaces (hvcN,
> xvcN, xvdMN) jumped in far to late.
> There have been huge clusters build before one was even thinking about
> hvc0.
>
> Just my 2 cents, and I'm sorry that this won't help the OP to solve his
> issue easily.
>
> Cheers,
>
> Stephan
>
> ****
>
> ** **
>

lukas at laukamp

Aug 5, 2012, 11:32 AM

Post #9 of 11 (1355 views)
Permalink

Re: xm console command doesn't work [In reply to]

Am 05.08.2012 17:15, schrieb José Eduardo França:
> Ok
>
> first: when I do command "xm create guest.cfg -c" I can run console
> enviroment. Then when I do command "xm console guest" the terminal
> doesn't shown nothing. No Errors and I can't run others commands.
>
>
> 2012/8/3 Ian Tobin <itobin [at] tidyhosts <mailto:itobin [at] tidyhosts>>
>
> Hello,
>
> When you say it doesn't work, what isn't working, errors?
>
> Ian
>
> *From:*José Eduardo França [mailto:jefranca [at] gmail
> <mailto:jefranca [at] gmail>]
> *Sent:* 03 August 2012 21:41
> *To:* Stephan Seitz
> *Cc:* Ian Campbell; Lukas Laukamp; xen-users [at] lists
> <mailto:xen-users [at] lists>; Ian Tobin
> *Subject:* Re: [Xen-users] xm console command doesn't work
>
> Hi all,
>
> I can't still resolve.
> How Ian Campbell said the xl console command didn't work.
>
> Well... I tried the script /etc/init/hvc0.conf that Lukas
> suggested and my guest.cfg was changed to:
> name = "ubuntu-pv"
>
> memory = 256
> disk = ['phy:/dev/labprog/ubuntu-pv,xvda,w']
>
> vif = [' ']
>
> bootloader = "pygrub"
> *extra = "console=hvc0"*
>
>
> But, I can't run xm console command. Is there other idea?
> Thanks
>
> 2012/8/2 Stephan Seitz <s.seitz [at] netzhaut
> <mailto:s.seitz [at] netzhaut>>
>
>
> Am Donnerstag, den 02.08.2012, 08:16 +0100 schrieb Ian Campbell:
>
> On Wed, 2012-08-01 at 20:59 +0100, Lukas Laukamp wrote:
>
> >
>
> > he could also use the xl toolstack but the simple misstake is that the
>
> > hvc0.conf isn't needed in Dom0. The hvc0.conf is needed inside of the
>
> > DomU and in the config file must be set extra = 'console=hvc0' so that
>
> > the console kernel option for hvc0 is set. So the DomU can boot into a
>
> > hvc0 console and than xm and xl can use the console.
>
>
>
> pygrub should be getting the console=hvc0 from the grub cfg and
>
> hvc0.conf ought to already exist.
>
>
>
> If Ubuntu isn't setting these up by default during install when running
>
> under Xen then this should be reported as a bug to Ubuntu.
>
>
>
> I'm not familiar with current Ubuntu so I don't know if these are
>
> expected to be there i.e. I don't know if this is a wishlist/new-feature
>
> bug or just a bug in functionality which is expected to Just Work
>
> already.
>
>
>
> Ian.
>
>
>
> Current (12.04 LTS) Ubuntu, respectively the 3.2.0 linux-virtual
> Kernel as well as the grub-legacy-ec2 are
> aware of hvc0.
>
> I think the source of these console problems are the configurable
> different presets. One could use tty0
> as well as tty1, maybe hvc0 or xvc0 or both of them. The domU I'm
> currently peeking into spawns tty0
> and hvc0 with tty0 connected to the "serial" xl console and hvc0
> connected to vfb/vnc setting. But that
> can't be predicted, it's easy to configure it the opposite way.
>
> From my point of view, the definition of virtualization namespaces
> (hvcN, xvcN, xvdMN) jumped in far to late.
> There have been huge clusters build before one was even thinking
> about hvc0.
>
> Just my 2 cents, and I'm sorry that this won't help the OP to
> solve his issue easily.
>
> Cheers,
>
> Stephan
>
>
>
>
> _______________________________________________
> Xen-users mailing list
> Xen-users [at] lists
> http://lists.xen.org/xen-users

Hello,

so on the Debain and Ubuntu distros there is a strange bug which often
appear when the guest was installed with xen-tools. Normally when you do
xm console guest the console should switch. In the case of Ubuntu/Debian
guests often the prompt stands simply on the left side of the display
and shows nothing. You can simply type for example root and press return
than you should see the string Password: where you can type the password
an so login to the guest.

This problem often can be solved by setting the xencons and TERM boot
option in the extra line in the Xen configuration. In the past (don't
know if it's a the moment a problem) there are also wrong symlinks for
upstart/init after debootstraping a Debian/Ubuntu system.

Best Regards

s.seitz at netzhaut

Aug 5, 2012, 12:42 PM

Post #10 of 11 (1366 views)
Permalink

Re: xm console command doesn't work [In reply to]

Hi,

if "running console environment" means, you can see the kernel booting
and/or services starting, your domU just doesn't spawn a tty on hvc0.

ssh into your domU (or mount the domU root filesystem), navigate to your
domU /etc/init/
and
cat tty1.conf | sed 's,tty1,hvc0,g' > hvc0.conf
reboot your domU and you'll see a login prompt.

Am Sonntag, den 05.08.2012, 12:15 -0300 schrieb JosÃ© Eduardo FranÃ§a:

> Ok
>
> first: when I do command "xm create guest.cfg -c" I can run console
> enviroment. Then when I do command "xm console guest" the terminal
> doesn't shown nothing. No Errors and I can't run others commands.
>
>
>
> 2012/8/3 Ian Tobin <itobin [at] tidyhosts>
>
> Hello,
>

>
>
>
> When you say it doesnâ€™t work, what isnâ€™t working, errors?
>
>
>
> Ian
>
>
>
> From: JosÃ© Eduardo FranÃ§a [mailto:jefranca [at] gmail]
> Sent: 03 August 2012 21:41
> To: Stephan Seitz
> Cc: Ian Campbell; Lukas Laukamp; xen-users [at] lists; Ian
> Tobin
> Subject: Re: [Xen-users] xm console command doesn't work
>
>
>
>
> Hi all,
>
> I can't still resolve.
> How Ian Campbell said the xl console command didn't work.
>
> Well... I tried the script /etc/init/hvc0.conf that Lukas
> suggested and my guest.cfg was changed to:
> name = "ubuntu-pv"
>
> memory = 256
> disk = ['phy:/dev/labprog/ubuntu-pv,xvda,w']
>
>
> vif = [' ']
>
> bootloader = "pygrub"
> extra = "console=hvc0"
>
>
>
>
> But, I can't run xm console command. Is there other idea?
> Thanks
>
>
> 2012/8/2 Stephan Seitz <s.seitz [at] netzhaut>
>
>
>
>
> Am Donnerstag, den 02.08.2012, 08:16 +0100 schrieb Ian
> Campbell:
>
>
> On Wed, 2012-08-01 at 20:59 +0100, Lukas Laukamp wrote:
> >
> > he could also use the xl toolstack but the simple misstake is that the
> > hvc0.conf isn't needed in Dom0. The hvc0.conf is needed inside of the
> > DomU and in the config file must be set extra = 'console=hvc0' so that
> > the console kernel option for hvc0 is set. So the DomU can boot into a
> > hvc0 console and than xm and xl can use the console.
>
> pygrub should be getting the console=hvc0 from the grub cfg and
> hvc0.conf ought to already exist.
>
> If Ubuntu isn't setting these up by default during install when running
> under Xen then this should be reported as a bug to Ubuntu.
>
> I'm not familiar with current Ubuntu so I don't know if these are
> expected to be there i.e. I don't know if this is a wishlist/new-feature
> bug or just a bug in functionality which is expected to Just Work
> already.
>
> Ian.
>
>
> Current (12.04 LTS) Ubuntu, respectively the 3.2.0
> linux-virtual Kernel as well as the grub-legacy-ec2 are
> aware of hvc0.
>
> I think the source of these console problems are the
> configurable different presets. One could use tty0
> as well as tty1, maybe hvc0 or xvc0 or both of them. The domU
> I'm currently peeking into spawns tty0
> and hvc0 with tty0 connected to the "serial" xl console and
> hvc0 connected to vfb/vnc setting. But that
> can't be predicted, it's easy to configure it the opposite
> way.
>
> From my point of view, the definition of virtualization
> namespaces (hvcN, xvcN, xvdMN) jumped in far to late.
> There have been huge clusters build before one was even
> thinking about hvc0.
>
> Just my 2 cents, and I'm sorry that this won't help the OP to
> solve his issue easily.
>
> Cheers,
>
> Stephan
>
>
>
>
>
>
>
>
>
>
>
> _______________________________________________
> Xen-users mailing list
> Xen-users [at] lists
> http://lists.xen.org/xen-users

Attachments:

signature.asc (0.48 KB)

jefranca at gmail

Aug 9, 2012, 10:29 AM

Post #11 of 11 (1298 views)
Permalink

Re: xm console command doesn't work [In reply to]

[RESOLVED] Hi guys,

Lukas is right. I thought there was a error. But I type root and showed
"Password"

Thanks all

2012/8/5 Stephan Seitz <s.seitz [at] netzhaut>

> **
> Hi,
>
> if "running console environment" means, you can see the kernel booting
> and/or services starting, your domU just doesn't spawn a tty on hvc0.
>
> ssh into your domU (or mount the domU root filesystem), navigate to your
> domU /etc/init/
> and
> cat tty1.conf | sed 's,tty1,hvc0,g' > hvc0.conf
> reboot your domU and you'll see a login prompt.
>
>
> Am Sonntag, den 05.08.2012, 12:15 -0300 schrieb José Eduardo França:
>
> Ok
>
> first: when I do command "xm create guest.cfg -c" I can run console
> enviroment. Then when I do command "xm console guest" the terminal doesn't
> shown nothing. No Errors and I can't run others commands.
>
>
> 2012/8/3 Ian Tobin <itobin [at] tidyhosts>
>
> Hello,
>
>
>
>
>
> When you say it doesn’t work, what isn’t working, errors?
>
>
>
> Ian
>
>
>
> *From:* José Eduardo França [mailto:jefranca [at] gmail]
> *Sent:* 03 August 2012 21:41
> *To:* Stephan Seitz
> *Cc:* Ian Campbell; Lukas Laukamp; xen-users [at] lists; Ian Tobin
> *Subject:* Re: [Xen-users] xm console command doesn't work
>
>
>
> Hi all,
>
> I can't still resolve.
> How Ian Campbell said the xl console command didn't work.
>
> Well... I tried the script /etc/init/hvc0.conf that Lukas suggested and my
> guest.cfg was changed to:
> name = "ubuntu-pv"
>
> memory = 256
> disk = ['phy:/dev/labprog/ubuntu-pv,xvda,w']
>
> vif = [' ']
>
> bootloader = "pygrub"
> *extra = "console=hvc0"*
>
>
>
> But, I can't run xm console command. Is there other idea?
> Thanks
>
> 2012/8/2 Stephan Seitz <s.seitz [at] netzhaut>
>
>
>
> Am Donnerstag, den 02.08.2012, 08:16 +0100 schrieb Ian Campbell:
>
> On Wed, 2012-08-01 at 20:59 +0100, Lukas Laukamp wrote:
> >
> > he could also use the xl toolstack but the simple misstake is that the
> > hvc0.conf isn't needed in Dom0. The hvc0.conf is needed inside of the
> > DomU and in the config file must be set extra = 'console=hvc0' so that
> > the console kernel option for hvc0 is set. So the DomU can boot into a
> > hvc0 console and than xm and xl can use the console.
>
> pygrub should be getting the console=hvc0 from the grub cfg and
> hvc0.conf ought to already exist.
>
> If Ubuntu isn't setting these up by default during install when running
> under Xen then this should be reported as a bug to Ubuntu.
>
> I'm not familiar with current Ubuntu so I don't know if these are
> expected to be there i.e. I don't know if this is a wishlist/new-feature
> bug or just a bug in functionality which is expected to Just Work
> already.
>
> Ian.
>
>
> Current (12.04 LTS) Ubuntu, respectively the 3.2.0 linux-virtual
> Kernel as well as the grub-legacy-ec2 are
> aware of hvc0.
>
> I think the source of these console problems are the configurable
> different presets. One could use tty0
> as well as tty1, maybe hvc0 or xvc0 or both of them. The domU I'm
> currently peeking into spawns tty0
> and hvc0 with tty0 connected to the "serial" xl console and hvc0 connected
> to vfb/vnc setting. But that
> can't be predicted, it's easy to configure it the opposite way.
>
> From my point of view, the definition of virtualization namespaces (hvcN,
> xvcN, xvdMN) jumped in far to late.
> There have been huge clusters build before one was even thinking about
> hvc0.
>
> Just my 2 cents, and I'm sorry that this won't help the OP to solve his
> issue easily.
>
> Cheers,
>
> Stephan
>
>
>
>
>
>
>
>
> _______________________________________________
> Xen-users mailing listXen-users [at] listshttp://lists.xen.org/xen-users
>
>

Index | Next | Previous | View Threaded

Interested in having your list archived? Contact Gossamer Threads