Re: [EXTERNAL]Re: Qemu image broken?

Re: [EXTERNAL]Re: Qemu image broken?

[Josh Marshall]

Indeed, it is actually not just 2 major releases behind, but does not have any progression from 2.0.0 and was built in 2008.
```
QEMU emulator version 2.0.0, Copyright (c) 2003-2008 Fabrice Bellard
```
referencing
https://guix.gnu.org/manual/en/html_node/Running-Guix-in-a-VM.html
these details are not included.  Should there be a system requirements listed more obviously?  I have a recorded boot process uploaded at https://youtu.be/p9xdtQwZFtI .

________________________________________
From: Tobias Geerinckx-Rice
Sent: Saturday, February 8, 2020 11:44 AM
To: Josh Marshall
Cc: Leo Famulari; help-guix; Josh Marshall
Subject: [EXTERNAL]Re: Qemu image broken?


Josh,

Josh Marshall 写道：
> Finally getting back to this.  Instructions don't work either. 
> The `-nic`
> param is unsupported, and the `virtio-net-pci` is an unsupported 
> nic model.
>
> CC'ing my work email where I'm seeing this.  Host OS is CentOS 
> 7.7.

CentOS's whole deal is shipping very old software with some 
security fixes.

Leo Famulari 写道：
> I can't reproduce these issues. What version of QEMU are you 
> using? In
> Guix we are based on QEMU 4.

If this[0] random Web site is to be believed, your qemu package is 
2(!) whole releases behind what's current.

Kind regards,

T G-R

[0]: https://pkgs.org/download/qemu


---

The information in this email, including attachments, may be confidential and is intended solely for the addressee(s). If you believe you received this email by mistake, please notify the sender by return email as soon as possible.

Qemu image is broken

[Josh Marshall]

Hey guys,

Starting up the Qemu image off the website immediately results in a kernel
panic and can't run.  This should be fixed quickly.

Re: Qemu image broken?

[Tobias Geerinckx-Rice]

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

Josh,

Josh Marshall 写道：
> Starting up the Qemu image off the website immediately results 
> in a kernel
> panic and can't run.  This should be fixed quickly.

I agree that any bugs should be promptly fixed.  However, I'm not 
yet convinced there's anything wrong with the image.  We'll need 
more information to help you.

The Qemu image on <https://guix.gnu.org/download/> hasn't been 
touched since May 2019 and still works for me today:

  λ curl -LI 
  https://ftp.gnu.org/gnu/guix/guix-system-vm-image-1.0.1.x86_64-linux.xz
  λ unxz guix-system-vm-image-1.0.1.x86_64-linux.xz
  λ qemu-system-x86_64 \
     -net user -net nic,model=virtio \
     -enable-kvm -m 512 \
     -device virtio-blk,drive=myhd \
     -drive 
     if=none,file=$PWD/guix-system-vm-image-1.0.1.x86_64-linux.xz,id=myhd
     # …and be greeted by a happy XFCE mouse.

How, exactly, are you trying to run it, and which error(s) do you 
get?

Kind regards,

T G-R

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

Re: Qemu image broken?

[Tobias Geerinckx-Rice]

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

Tobias Geerinckx-Rice 写道：
> if=none,file=$PWD/guix-system-vm-image-1.0.1.x86_64-linux.xz,id=myhd

Paste-o.  Of course I didn't add .xz here.

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

Re: Qemu image broken?

[Josh Marshall]

`qemu-system-x86_64 <image path>`. Just the naive default starting point.

On Wed, Jan 22, 2020, 12:22 Tobias Geerinckx-Rice <me@tobias.gr> wrote:

> Tobias Geerinckx-Rice 写道：
> > if=none,file=$PWD/guix-system-vm-image-1.0.1.x86_64-linux.xz,id=myhd
>
> Paste-o.  Of course I didn't add .xz here.
>

Re: Qemu image broken?

[Leo Famulari]

On Wed, Jan 22, 2020 at 12:41:18PM -0500, Josh Marshall wrote:
> `qemu-system-x86_64 <image path>`. Just the naive default starting point.

At the very least you will need to allocate some more RAM, for example
with '-m 4096'; that will provide 4 GB RAM to the virtual machine. The
default of 128 megabytes is not enough.

But I agree with the other responders, you should copy the instructions
in our manual unless you need to do something specific.

I hope that helps!

Re: Qemu image broken?

[Josh Marshall]

Finally getting back to this.  Instructions don't work either.  The `-nic`
param is unsupported, and the `virtio-net-pci` is an unsupported nic model.

CC'ing my work email where I'm seeing this.  Host OS is CentOS 7.7.

On Wed, Jan 22, 2020, 14:13 Leo Famulari <leo@famulari.name> wrote:

> On Wed, Jan 22, 2020 at 12:41:18PM -0500, Josh Marshall wrote:
> > `qemu-system-x86_64 <image path>`. Just the naive default starting point.
>
> At the very least you will need to allocate some more RAM, for example
> with '-m 4096'; that will provide 4 GB RAM to the virtual machine. The
> default of 128 megabytes is not enough.
>
> But I agree with the other responders, you should copy the instructions
> in our manual unless you need to do something specific.
>
> I hope that helps!
>

Re: [EXTERNAL]Re: Qemu image broken?

[Josh Marshall]

Omitting the model gets it to boot.  However, Xorg fails and logind fails.  I can't log into the system.

________________________________________
From: Josh Marshall <joshua.r.marshall.1991@gmail.com>
Sent: Friday, February 7, 2020 3:43 PM
To: Leo Famulari
Cc: Tobias Geerinckx-Rice; help-guix; Josh Marshall
Subject: [EXTERNAL]Re: Qemu image broken?

Finally getting back to this.  Instructions don't work either.  The `-nic` param is unsupported, and the `virtio-net-pci` is an unsupported nic model.

CC'ing my work email where I'm seeing this.  Host OS is CentOS 7.7.

On Wed, Jan 22, 2020, 14:13 Leo Famulari <leo@famulari.name<mailto:leo@famulari.name>> wrote:
On Wed, Jan 22, 2020 at 12:41:18PM -0500, Josh Marshall wrote:
> `qemu-system-x86_64 <image path>`. Just the naive default starting point.

At the very least you will need to allocate some more RAM, for example
with '-m 4096'; that will provide 4 GB RAM to the virtual machine. The
default of 128 megabytes is not enough.

But I agree with the other responders, you should copy the instructions
in our manual unless you need to do something specific.

I hope that helps!
---

The information in this email, including attachments, may be confidential and is intended solely for the addressee(s). If you believe you received this email by mistake, please notify the sender by return email as soon as possible.