CoreOS on HyperV

[Bradley Sickles]

I am trying to create a CoreOS HyperV VM.

I downloaded a vhd from https://stable.release.core-os.net/amd64-usr/current/coreos_production_hyperv_image.vhd.bz2.

I used this vhd as the main disk on a newly created VM.

The VM boots successfully; however, I have no way of logging into the box.

I tried using core/core credentials.

Does anybody know with what default credentials this VHD is configured?

[Alex Crawford]

Container Linux doesn't have default credentials due to the security
concern. Normally, credentials are added via our provisioning utility,
Ignition (more info can be found in our docs [1]). Unfortunately,
Ignition doesn't support Hyper-V, so you'll need to instead activate
autologin which won't prompt for a password when using the serial
console. You can activate it by stopping the boot during GRUB (press any
key) and editing the default entry, adding `coreos.autologin`. This will
take effect only on this boot, but you can use the opportunity to set a
password or SSH key.

-Alex

[1]: https://coreos.com/os/docs/latest/provisioning.html

[Bradley Sickles]

Alex,

Thanks, that was very helpful!

Do you know if there are intentions of ignition supporting HyperV?

Is this a technical limitation or just a priority issue?

Brad

[Bradley Sickles]

I am trying to extend this box to a vagrant box.

When I try to boot, vagrant waits (until timeout) to acquire the coreos guest ip address to no avail.

I am able to SSH into the box just knowing the IP Address.

Also, I confirmed that HyperV incorrectly reports a lack of IP Address.

```

PS> Get-VM | ? { $_.Name -eq "coreos-1465.7.0" } | Get-VMNetworkAdapter | ft VMName, IPAddresses, switchName

VMName          IPAddresses SwitchName

------          ----------- ----------

coreos-1465.7.0 {}          packer-hyperv-iso

```

Is this a known deficiency with coreos?

Any way to fix this?

Brad

[Alex Crawford]

On 09/20, Bradley Sickles wrote:
> I am trying to extend this box to a vagrant box.
> When I try to boot, vagrant waits (until timeout) to acquire the coreos
> guest ip address to no avail.
>
> I am able to SSH into the box just knowing the IP Address.
> Also, I confirmed that HyperV incorrectly reports a lack of IP Address.
>
> ```
> PS> Get-VM | ? { $_.Name -eq "coreos-1465.7.0" } | Get-VMNetworkAdapter |
> ft VMName, IPAddresses, switchName
>
> VMName IPAddresses SwitchName
> ------ ----------- ----------
> coreos-1465.7.0 {} packer-hyperv-iso
> ```
>
> Is this a known deficiency with coreos?
> Any way to fix this?

That's interesting. If the IP address works but Hyper-V doesn't know
about it, that implies that the guest is expected to report that
information to the hypervisor. We don't ship any guest tools
specifically for Hyper-V in Container Linux. Do you know if guest OSs
are expected to have a set of tools installed?

> On Wednesday, September 20, 2017 at 3:26:37 PM UTC-4, Bradley Sickles wrote:
> > Do you know if there are intentions of ignition supporting HyperV?
> > Is this a technical limitation or just a priority issue?

It's a bit of both. Ignition needs to know where it can find the
configuration that should be used. VMware, for example, has a Guest
Variable mechanism (implemented as an intercepted hyper-call from the
guest to the hypervisor). I'm unsure of the preferred mechanism that
Hyper-V uses (or if there is one). The Hyper-V support fell out of Azure
support (which also uses Hyper-V).

-Alex

[Bradley Sickles]

> Do you know if guest OSs are expected to have a set of tools installed?

I'm not sure.  Previously, I thought that the IP Addresses would be lifted from DHCP registration of the VM's mac.

I'm also not sure where I could discover this information.

Brad

[Alex Crawford]

On 09/21, Bradley Sickles wrote:
> > Do you know if guest OSs are expected to have a set of tools installed?
>
> I'm not sure. Previously, I thought that the IP Addresses would be lifted
> from DHCP registration of the VM's mac.
>
> I'm also not sure where I could discover this information.

Sounds like there are integration services which are needed:
https://technet.microsoft.com/en-us/library/dn798297(v=ws.11).aspx

I can ask my contacts at Microsoft to figure out exactly what we need to
ship.

-Alex

[Alex Crawford]

On 09/21, Alex Crawford wrote:
> On 09/21, Bradley Sickles wrote:
> > > Do you know if guest OSs are expected to have a set of tools installed?
> >
> > I'm not sure. Previously, I thought that the IP Addresses would be lifted
> > from DHCP registration of the VM's mac.
> >
> > I'm also not sure where I could discover this information.
>
> Sounds like there are integration services which are needed:
> https://technet.microsoft.com/en-us/library/dn798297(v=ws.11).aspx

I've filed two issues where we can track this further:

https://github.com/coreos/bugs/issues/2161
https://github.com/coreos/bugs/issues/2162

We'll follow up there.

-Alex

[Bradley Sickles]

Alex,

Great stuff!

Thanks so much!

Brad