Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

azure-image: remove qemu-220 #25661

Closed

Conversation

puffnfresh
Copy link
Contributor

We don't need this according to #16437

Motivation for this change

Fixing old issues.

Things done
  • Tested using sandboxing
    (nix.useSandbox on NixOS,
    or option build-use-sandbox in nix.conf
    on non-NixOS)
  • Built on platform(s)
    • NixOS
    • macOS
    • Linux
  • Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
  • Tested execution of all binary files (usually in ./result/bin/)
  • Fits CONTRIBUTING.md.

We don't need this according to NixOS#16437
@mention-bot
Copy link

@puffnfresh, thanks for your PR! By analyzing the history of the files in this pull request, we identified @edolstra, @rbvermaa and @Phreedom to be potential reviewers.

@fpletz
Copy link
Member

fpletz commented May 10, 2017

@fadenb Do you have time to test this? 🙂

@fadenb
Copy link
Contributor

fadenb commented May 10, 2017

I believe it is missing the -o force_size option. See #25197 (comment) and the other comments. I can test this later today.

Copy link
Contributor

@fadenb fadenb left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I finally found the time to test this PR. As expected the produced image was not accepted by Azure:

    The VHD for disk 'nixosVMelasticosdisk' with blob https://somename.blob.core.windows.net/graylog-images/nixosVM-elastic-0-osdisk.vhd has an unsupported virtual size of 30720.375 MB. The size must be a whole number in (MBs).

@fadenb
Copy link
Contributor

fadenb commented Mar 9, 2018

(just stumbled on this PR again)
@puffnfresh: Should we close this PR as the initial test I did last year failed to produce usable output?

Copy link
Member

@matthewbauer matthewbauer left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

merge conflict/see @fadenb's concerns

@colemickens
Copy link
Member

colemickens commented Apr 26, 2018

Per this comment, https://bugs.launchpad.net/qemu/+bug/1490611/comments/39, you need to add force_size to the options.

I'm working on some other Azure changes, including this. I'll send some PRs if it all works out. Apologies for not being more detailed in the Issue that triggered this...

edit: Also, for apparently not reading the thread very well. @fadenb Did you happen to try with both force_size and fixed? That's what the qemu-img maintainers tested as working.

@fadenb
Copy link
Contributor

fadenb commented May 13, 2018

@colemickens: Sorry, I can not remember exactly what I did back then. I suspect I tested that combination as I did quite a few tests but I am not sure.

@colemickens
Copy link
Member

@fadenb It's alright. I've been creating and using new images myself using the mainline qemu. I'll try to isolate the qemu change from my other changes and send it as a PR at least.

@Mic92
Copy link
Member

Mic92 commented Jun 12, 2018

we merged #41881 instead.

@Mic92 Mic92 closed this Jun 12, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

7 participants