unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Marius Bakke <marius@gnu.org>
To: david larsson <david.larsson@selfhosted.xyz>, help-guix@gnu.org
Subject: Re: Ganeti with Guix tutorial from the Guix blog post
Date: Sat, 26 Sep 2020 16:23:36 +0200	[thread overview]
Message-ID: <871riowr9z.fsf@gnu.org> (raw)
In-Reply-To: <f1c261fd5f018e01559418ebf76cb0ef@selfhosted.xyz>

[-- Attachment #1: Type: text/plain, Size: 2242 bytes --]

david larsson <david.larsson@selfhosted.xyz> writes:

> Hi!
>
> First of all - thanks for a great post about using Ganeti with Guix!

Thanks.  :-)

> I need some help with the networking setup part since I am stuck at the 
> end stages of the blog post tutorial - I am unable to run "gnt-instance 
> console <someVM>". So, I have things setup enough to create these VM's 
> successfully but I can't ping the hosts or connect to them using 
> gnt-instance console <someVM>. Any ideas what the issue might be?

If the serial console is not responding (i.e. pressing RET does not make
a login screen appear), it is likely the instance has failed to boot.  A
typical cause is lack of bootloader.  In that case the instance will use
100% of a core reading the same virtual disk sector over and over...

You can configure a SPICE server with "gnt-instance modify -H
kvm:spice_bind=0.0.0.0" and connect remotely with 'spicy' (from
spice-gtk) to the host IP and the allocated instance port (gnt-instance
info foo | grep port).  Then you should be able to see what QEMU is up
to.

Clues may also be found in
/var/log/ganeti/os/add_$provider_$instance_$date.

> One thing I noticed was that the arp -n output are giving me 
> "(incomplete)" listings in the "HWaddress" column (arp from the 
> net-tools package), which IMU means that ethernet/layer2 frames are not 
> passed around correctly - usually meaning that bridges aren't setup 
> properly, right? This applies to the 192.168.1.200 lan address and the 
> ip address assigned to the VM hosts which I manually set to 
> 192.168.1.210 instead of ip=pool as in the example. My local network is 
> setup to use 192.168.1.0/24 addresses.

It could be useful to see the relevant system configuration, as well as
output of 'ovs-vsctl show' and 'gnt-instance info the-instance' (and
maybe also 'gnt-network info').

> I think it would be great if blog posts like these had comments enabled, 
> so that people trying to follow a tutorial would be able to discuss and 
> help eachother directly on the blog post page.

That is an interesting suggestion.  The blog is entirely static, but
perhaps we could link in a mailing list or something (no joke!).  :-)

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]

  reply	other threads:[~2020-09-26 14:24 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-25 19:06 Ganeti with Guix tutorial from the Guix blog post david larsson
2020-09-26 14:23 ` Marius Bakke [this message]
2020-09-27 19:28   ` david larsson
2020-10-10 21:57     ` Marius Bakke

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

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=871riowr9z.fsf@gnu.org \
    --to=marius@gnu.org \
    --cc=david.larsson@selfhosted.xyz \
    --cc=help-guix@gnu.org \
    /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 read-only IMAP folder(s) and NNTP newsgroup(s).