"Tim Woodall" writes:
> Don't know about systemd-nspawn but I do something like this using
> unshare, binfmt-support and qemu-user-static.
>
> I don't have to do anything at all other than create the file system
> with the emulated architecture and then chroot into it with those
> packages instal
On Wed, 21 Aug 2024, Steve Keller wrote:
Can I run a container for a different CPU architecture using
systemd-nspawn? I can easily install on my amd64 host a Debian
container of the same architecture and run that:
Don't know about systemd-nspawn but I do something like this using
unshare, bi
"Markus Schönhaber" writes:
> No. systemd-nspawn does indeed simply run a container. You can think of
> that as a chroot on steroids. This means, everything inside the
> container is run using the host kernel. Or to put it the other way
> round: what the host kernel can't execute won't run.
Actua
21.08.24, 16:56 +0200, Steve Keller:
> Can I run a container for a different CPU architecture using
> systemd-nspawn?
No. systemd-nspawn does indeed simply run a container. You can think of
that as a chroot on steroids. This means, everything inside the
container is run using the host kernel. Or
On Thu 02/05/2024 at 20:14, Gareth Evans wrote:
> On Thu 02/05/2024 at 19:57, Stephen P. Molnar wrote:
>> On 05/02/2024 12:54 PM, Gareth Evans wrote:
>>>
>>>
On 2 May 2024, at 17:47, Gareth Evans wrote:
> On 2 May 2024, at 15:43, Stephen P. Molnar
> wrote:
>
>
On Thu 02/05/2024 at 19:57, Stephen P. Molnar wrote:
> On 05/02/2024 12:54 PM, Gareth Evans wrote:
>>
>>
>>> On 2 May 2024, at 17:47, Gareth Evans wrote:
>>>
>>>
>>>
On 2 May 2024, at 15:43, Stephen P. Molnar
wrote:
I am running Bookworm and have implemented QEMU/KVM virt
On 05/02/2024 12:54 PM, Gareth Evans wrote:
On 2 May 2024, at 17:47, Gareth Evans wrote:
On 2 May 2024, at 15:43, Stephen P. Molnar
wrote:
I am running Bookworm and have implemented QEMU/KVM virt-manager.
When I install a client I have been using virt-manager --> View
-->Scale D
> On 2 May 2024, at 17:47, Gareth Evans wrote:
>
>
>
>> On 2 May 2024, at 15:43, Stephen P. Molnar wrote:
>>
>> I am running Bookworm and have implemented QEMU/KVM virt-manager. When I
>> install a client I have been using virt-manager --> View -->Scale Display
>> --> Always. However, n
> On 2 May 2024, at 15:43, Stephen P. Molnar wrote:
>
> I am running Bookworm and have implemented QEMU/KVM virt-manager. When I
> install a client I have been using virt-manager --> View -->Scale Display -->
> Always. However, now the 'Always ', the only option available is the default
>
On 2024-05-02, Stephen P. Molnar wrote:
> I am running Bookworm and have implemented QEMU/KVM virt-manager. When I
> install a client I have been using virt-manager --> View -->Scale
> Display --> Always. However, now the 'Always ', the only option
> available is the default 'Only when Fullscre
About the time I post this someone on the Proxmox forums posted the link to the
Debian merge request. See
https://salsa.debian.org/qemu-team/qemu/-/merge_requests/37
Thanks
Shawn
On Jul 26, 2023, at 8:39 AM, Shawn Weeks wrote:
I’ve been tracking down an issue where my Debian 12 instances on P
Alain Williams wrote:
>So: it seems that the state of the Num Lock key is not picked up by
>qemu.
In the virtualized environment I use:
setxkbmap -option numpad:mac
On Wed, Jun 21, 2023 at 05:42:30PM +0100, Alain Williams wrote:
> I have an issue with virtual machines under qemu.
Caps Lock is also affected the same way.
> Sequence as follows:
>
> I press Numeric Lock (or Num Lock) so that the keyboard indicator lights up.
>
> I then switch to the workspace
Hi
did you solve this? i got this problem, too with qemu 7 and ubuntu 22.04.1
--
--
cordially
Charlie Schindler
+66 9 1083 7897
Am Thu, 31 Mar 2022 15:42:43 +0100
schrieb Gareth Evans :
>A different invocation method, but does this help, or give a clue to something
>equivalent?
>
>https://lists.debian.org/debian-user/2021/09/msg00691.html
The link was the path to the solution. For gtk output in a newly created
window I h
> On 31 Mar 2022, at 09:44, Dieter Rohlfing wrote:
>
> Hi,
>
> I'm just about to install Debian11/Bullseye on a host. There are several
> VMs running under QEMU/KVM to set up.
>
> With Debian9/Stretch I created a new VM via command line:
>
> /usr/bin/kvm -drive
> file=/qemu/win-70/win-70.jes
Hello Dieter,
unfortunately I have no answer for this specific problem, but I can
strongly recommend the virt-manager solution which utilizes qemu (and
kvm if available).
Regards,
Christian
On 2022-03-31 10:44 UTC+0200, Dieter Rohlfing wrote:
> Hi,
>
> I'm just about to install Debian11/Bullsey
On 03.12.2021 20:26, daggs wrote:
Greetings Alexander,
thank you for the explenation, is there a place where I can see when
libvirt might arrive to bullseye-backports?
https://backports.debian.org/
You will find there the list of all packages uploaded to
bullseye-backports¹ and the list of pa
Greetings Alexander,
thank you for the explenation, is there a place where I can see when libvirt might arrive to bullseye-backports?
Sent: Friday, December 03, 2021 at 4:42 PM
From: "Alexander V. Makartsev"
To: debian-user@lists.debian.org
Subject: Re: qemu from backports and li
On 03.12.2021 18:14, daggs wrote:
Greetings,
I'm trying to install qemu from bullseye-backports on a system with libvirt
from bullseye, when inspecting the output I notice this:
The following packages will be REMOVED:
libvirt-daemon libvirt-daemon-system
why is that? is there a way to make
Am Montag, 20. September 2021 schrieb Thomas Schmitt:
> Hi,
>
> Stefan Krusche wrote:
> > When I start qemu with the following command the VM seemingly gets
> > started but no window whatsoever shows up. AFAIR it always has
> > worked like that before.
>
> That's my memory too. The script for my Si
Hi,
Stefan Krusche wrote:
> When I start qemu with the following command the VM seemingly gets
> started but no window whatsoever shows up. AFAIR it always has worked
> like that before.
That's my memory too. The script for my Sid VM has option -nographic
to prevent such a qemu window from showin
Stefan Krusche wrote:
> Am Montag, 20. September 2021 schrieb Dan Ritter:
> > Stefan Krusche wrote:
> >
> > I don't expect an invocation of qemu to open a window, I expect
> > it to run the VM.
>
> Well, not sure what you mean. Does the VM not run in a window?!
No. The VM is a process. The VM ma
Am Montag, 20. September 2021 schrieb Dan Ritter:
> Stefan Krusche wrote:
> > Good Day All,
> >
> > Problem description:
> >
> > When I start qemu with the following command the VM seemingly gets
> > started but no window whatsoever shows up. AFAIR it always has
> > worked like that before.
> >
> >
Stefan Krusche wrote:
> Good Day All,
>
> Problem description:
>
> When I start qemu with the following command the VM seemingly gets
> started but no window whatsoever shows up. AFAIR it always has worked
> like that before.
>
> $ qemu-system-x86_64 -m 1024M -name "Devuan GNU/Linux
> Beowulf"
On Sat, 04 Sep 2021 18:08:18 -0500
"David Palacio" wrote:
> I have compared my previous install nft ruleset and installed
> packages list with the current install and found that firewalld
> wasn't installed in the working system but ufw was. The nft ruleset
> was nearly identical save for the mis
I have compared my previous install nft ruleset and installed packages list
with the current install and found that firewalld wasn't installed in the
working system but ufw was. The nft ruleset was nearly identical save for the
missing firewalld rules.
And so after purging firewalld, plasma-fir
On Thu, 02 Sep 2021 16:09:23 -0500
"David Palacio" wrote:
> Hi,
>
> > If you copied a disk image (.qcow2 extension) over, but not the
> > setup files that Virtual Machine Manager (VMM) uses
> > (in /etc/libvirt), then Windows is on a new machine, and can have
> > conniptions over it. Go into Win
On Thu, Sep 2, 2021, at 2:09 PM, Charles Curley wrote:
> On Thu, 02 Sep 2021 12:43:41 -0500
> "David Palacio" wrote:
>
> > Good day,
> >
> > I have recently installed Debian testing around its alpha release
> > state. Previously I had a working Windows 10 QEMU guest with access
> > to the host S
On Thu, 02 Sep 2021 12:43:41 -0500
"David Palacio" wrote:
> Good day,
>
> I have recently installed Debian testing around its alpha release
> state. Previously I had a working Windows 10 QEMU guest with access
> to the host Samba shares in a previous Debian testing install. I
> copied the Window
On 1/6/21 5:33 AM, buz.hr...@seznam.cz wrote:
From: Nicholas Geovanis
George Shuklin's comment may have intended this question too: Are backups
running
somewhere when the VMs "randomly" hang? Not necessarily on the VM that hangs,
but somewhere touching a related filesystem, disk or network de
From: Nicholas Geovanis
> George Shuklin's comment may have intended this question too: Are backups
> running
> somewhere when the VMs "randomly" hang? Not necessarily on the VM that hangs,
> but somewhere touching a related filesystem, disk or network device?
Hi Nicholas,
Thank you for asking
George Shuklin's comment may have intended this question too: Are backups
running somewhere when the VMs "randomly" hang? Not necessarily on the VM
that hangs, but somewhere touching a related filesystem, disk or network
device?
On Sun, Dec 27, 2020, 4:33 AM wrote:
> From: Dan Ritter
>
> > You
From: Dan Ritter
> You probably want to change that to 1 minute or so.
Btw. could you please tell me how to do that?
I know how to modify (=> override) systemd unit files but I have no idea how to
change default timeout for mounted block devices that I didn't manually create
in /etc/systemd/s
On 12/24/20 8:34 PM, buz.hr...@seznam.cz wrote:
Hi Debian people ;-),
After having some issues with Fedora last year I decided to reinstall all my
servers to Debian 10. I'm supper happy with Debian except one repeating issue I
have with QEMU-KVM hosts that is very difficult to reproduce so I w
From: Dan Ritter
Hi Dan, Thank you for answering ;-)
> First question: when they are just a few minutes old, does the
> serial console work?
Yes, 100%. I always configure serial console for all VMs both on QEMU (libvirt)
and OS side.
> Second question: when the VMs are a few minutes old, does
buz.hr...@seznam.cz wrote:
> Hi Debian people ;-),
>
> After having some issues with Fedora last year I decided to reinstall all my
> servers to Debian 10. I'm supper happy with Debian except one repeating issue
> I have with QEMU-KVM hosts that is very difficult to reproduce so I would
> like
On 10/28/2020 8:00 PM, john doe wrote:
On 10/28/2020 7:50 PM, Markus Schönhaber wrote:
28.10.20, 19:19 +0100 john doe:
On 10/28/2020 6:51 PM, Markus Schönhaber wrote:
28.10.20, 18:30 +0100 john doe:
$ ls -dl /srv/sftp/9p
drwx-- 8 root root ... /srv/sftp/9p
Isn't "9p" supposed to be t
On 10/28/2020 7:50 PM, Markus Schönhaber wrote:
28.10.20, 19:19 +0100 john doe:
On 10/28/2020 6:51 PM, Markus Schönhaber wrote:
28.10.20, 18:30 +0100 john doe:
$ ls -dl /srv/sftp/9p
drwx-- 8 root root ... /srv/sftp/9p
Isn't "9p" supposed to be the share directory? If it is, why is it
28.10.20, 19:19 +0100 john doe:
> On 10/28/2020 6:51 PM, Markus Schönhaber wrote:
>> 28.10.20, 18:30 +0100 john doe:
>
>>> $ ls -dl /srv/sftp/9p
>>> drwx-- 8 root root ... /srv/sftp/9p
>>
>> Isn't "9p" supposed to be the share directory? If it is, why is it owned
>> by root and has these rest
On 10/28/2020 6:51 PM, Markus Schönhaber wrote:
28.10.20, 18:30 +0100 john doe:
On 10/21/2020 11:02 PM, Markus Schönhaber wrote:
21.10.20, 19:11 +0200, john doe:
On 10/20/2020 7:59 PM, Markus Schönhaber wrote:
How about moving the 9pshare to a root-owned directory and pointing the
ChrootD
28.10.20, 18:30 +0100 john doe:
> On 10/21/2020 11:02 PM, Markus Schönhaber wrote:
>> 21.10.20, 19:11 +0200, john doe:
>>
>>> On 10/20/2020 7:59 PM, Markus Schönhaber wrote:
>>
How about moving the 9pshare to a root-owned directory and pointing the
ChrootDirectory there, for example:
>>>
On 10/21/2020 11:02 PM, Markus Schönhaber wrote:
21.10.20, 19:11 +0200, john doe:
On 10/20/2020 7:59 PM, Markus Schönhaber wrote:
How about moving the 9pshare to a root-owned directory and pointing the
ChrootDirectory there, for example:
share -> /all/owned/by/root/9pshare
ChrootDirectory ->
21.10.20, 19:11 +0200, john doe:
> On 10/20/2020 7:59 PM, Markus Schönhaber wrote:
>> How about moving the 9pshare to a root-owned directory and pointing the
>> ChrootDirectory there, for example:
>> share -> /all/owned/by/root/9pshare
>> ChrootDirectory -> /all/owned/by/root
>>
>
> Thank you fo
On 10/20/2020 7:59 PM, Markus Schönhaber wrote:
20.10.20, 18:49 +0200, john doe:
Debians,
According to (1):
"ChrootDirectory
Specifies a path to chroot(2) to after authentication. This path, and
all its components, must be root-owned directories that are not writable
by any other user or grou
20.10.20, 18:49 +0200, john doe:
> Debians,
>
> According to (1):
>
> "ChrootDirectory
> Specifies a path to chroot(2) to after authentication. This path, and
> all its components, must be root-owned directories that are not writable
> by any other user or group. After the chroot, sshd(8)"
>
>
On Thu, Sep 17, 2020 at 5:20 AM Thomas Pircher wrote:
> Kenneth Parker wrote:
> > When I try to install qemu-kvm, I get: "Note, selecting
> > 'qemu-system-x86' instead of qemu-kvm"
>
> The 'qemu-kvm' package does no longer exist. It is a virtual package and
> is being replaced by qemu-system-x86
Kenneth Parker wrote:
> When I try to install qemu-kvm, I get: "Note, selecting
> 'qemu-system-x86' instead of qemu-kvm"
The 'qemu-kvm' package does no longer exist. It is a virtual package and
is being replaced by qemu-system-x86.
> And then, when I try to Define the Guest, using the file I had
Reco writes:
> Hi.
>
> On Fri, Sep 11, 2020 at 09:46:54PM +0200, Kamil Jońca wrote:
>> Dan Ritter writes:
>>
>> > Kamil Jo?ca wrote:
>> >> Dan Ritter writes:
>> >>
>> >>
>> >> Sorry, I do not understand.
>> >> If LSI 53c810 / 53c895a is not supported, how output
>> >> "qemu-system-x8
Hi.
On Fri, Sep 11, 2020 at 09:46:54PM +0200, Kamil Jońca wrote:
> Dan Ritter writes:
>
> > Kamil Jo?ca wrote:
> >> Dan Ritter writes:
> >>
> >>
> >> Sorry, I do not understand.
> >> If LSI 53c810 / 53c895a is not supported, how output
> >> "qemu-system-x86_64 -device help" should b
Dan Ritter writes:
> Kamil Jo?ca wrote:
>> Dan Ritter writes:
>>
>>
>> Sorry, I do not understand.
>> If LSI 53c810 / 53c895a is not supported, how output
>> "qemu-system-x86_64 -device help" should be interpreted?
>>
>> KJ
>
> Read Reco's message.
Sorry, still does not understand that: "L
Kamil Jo?ca wrote:
> Dan Ritter writes:
>
>
> Sorry, I do not understand.
> If LSI 53c810 / 53c895a is not supported, how output
> "qemu-system-x86_64 -device help" should be interpreted?
>
> KJ
Read Reco's message.
-dsr-
Dan Ritter writes:
> Kamil Jo?ca wrote:
>>
>> I try to migrate some my ancient virutal machines from virtualbox to
>> qemu, and some things are unclear for me.
>> 1. scsi devices:
>>
>> --8<---cut here---start->8---
>> %qemu-system-x86_64 -device help|grep l
Hi.
On Fri, Sep 11, 2020 at 11:10:28AM +0200, Kamil Jońca wrote:
>
> I try to migrate some my ancient virutal machines from virtualbox to
> qemu, and some things are unclear for me.
> 1. scsi devices:
>
> --8<---cut here---start->8---
> %qemu-system-x8
Kamil Jo?ca wrote:
>
> I try to migrate some my ancient virutal machines from virtualbox to
> qemu, and some things are unclear for me.
> 1. scsi devices:
>
> --8<---cut here---start->8---
> %qemu-system-x86_64 -device help|grep lsi
> name "lsi53c810", b
On 5/15/20 11:17 PM, Thomas Schmitt wrote:
Hi,
Gary L. Roach wrote:
I burned a CD off of the .iso file and used it to install the
system.
I wonder why you need to burn a real CD (or DVD ?) for a virtual machine.
Virtualization can work with the .iso file directly and make it appear
in the gu
Hi,
Gary L. Roach wrote:
> I burned a CD off of the .iso file and used it to install the
> system.
I wonder why you need to burn a real CD (or DVD ?) for a virtual machine.
Virtualization can work with the .iso file directly and make it appear
in the guest as CD-ROM drive with medium.
> Dummy m
On 5/15/20 3:19 AM, Thomas Schmitt wrote:
Hi,
Gary L. Roach wrote:
I load the software from an .iso file in my Download directory.
I wonder what this means in detail.
The normal procedure with an .iso image file and a qemu VM is
to start qemu with the .iso file as -cdrom and the (empty) virt
Hi,
Gary L. Roach wrote:
> I load the software from an .iso file in my Download directory.
I wonder what this means in detail.
The normal procedure with an .iso image file and a qemu VM is
to start qemu with the .iso file as -cdrom and the (empty) virtual
hard disk image file as -hda.
Then one w
On Thu, May 14, 2020 at 01:13:10PM -0700, Gary L. Roach wrote:
> Hi all,
>
> System: Debian Buster host
>
> qemu/kvm virtual machine
>
> CAELinux Guest
>
> I load the software from an .iso file in my Download directory. The
> guest files seem to be loading and workin
On 5/14/20, Gary L. Roach wrote:
> Hi all,
>
> System: Debian Buster host
>
>qemu/kvm virtual machine
>
>CAELinux Guest
>
> I load the software from an .iso file in my Download directory. The
> guest files seem to be loading and working fine until I try to reboot
>
Hi,
On 10/28/2018 6:37 PM, Reco wrote:
> Hi.
>
>
> On Sun, Oct 28, 2018 at 05:51:13PM +0100, john doe wrote:
>> On 10/26/2018 4:44 PM, Reco wrote:
>>> Nah, we don't do Windows here. Way too many quirks for my personal
>>> taste.
>>> What you can try is to replace stdio with telnet:
>>>
>>>
Hi.
On Sun, Oct 28, 2018 at 05:51:13PM +0100, john doe wrote:
> On 10/26/2018 4:44 PM, Reco wrote:
> > Nah, we don't do Windows here. Way too many quirks for my personal
> > taste.
> > What you can try is to replace stdio with telnet:
> >
> > qemu -hda debian.img -m 1024 \
> > -chard
On 10/26/2018 4:44 PM, Reco wrote:
> Hi.
>
> On Fri, Oct 26, 2018 at 03:34:55PM +0200, john doe wrote:
Run QEMU this way:
qemu -hda debian.img -m 1024 -nographic \
-kernel vmlinux -append 'console=ttyS0,115200n8' \
-initrd initrd.gz
Replace -kernel, -
Hi.
On Fri, Oct 26, 2018 at 03:34:55PM +0200, john doe wrote:
> >> Run QEMU this way:
> >>
> >> qemu -hda debian.img -m 1024 -nographic \
> >>-kernel vmlinux -append 'console=ttyS0,115200n8' \
> >>-initrd initrd.gz
> >>
> >> Replace -kernel, -initrd and -append with '-boot c' after
On 10/26/2018 9:16 AM, john doe wrote:
> On 10/25/2018 8:55 PM, Reco wrote:
>> Hi.
>>
>> On Thu, Oct 25, 2018 at 05:20:46PM +0200, john doe wrote:
>>> Hi,
>>>
>>> I'm trying to install Debian, it works if I do use the below command:
>>>
>>> qemu -hda debian.img -cdrom debian-9.5.0-amd64-netins
On 10/25/2018 8:55 PM, Reco wrote:
> Hi.
>
> On Thu, Oct 25, 2018 at 05:20:46PM +0200, john doe wrote:
>> Hi,
>>
>> I'm trying to install Debian, it works if I do use the below command:
>>
>> qemu -hda debian.img -cdrom debian-9.5.0-amd64-netinst.iso -boot d -m 1024
>>
>> I'd like to redirec
Hi.
On Thu, Oct 25, 2018 at 05:20:46PM +0200, john doe wrote:
> Hi,
>
> I'm trying to install Debian, it works if I do use the below command:
>
> qemu -hda debian.img -cdrom debian-9.5.0-amd64-netinst.iso -boot d -m 1024
>
> I'd like to redirect the output of the guest (Debian) to the t
On 2017-12-28 04:01 PM, Celejar wrote:
On Wed, 27 Dec 2017 23:14:31 -0500
Gary Dale wrote:
When I try to start a virtual machine, I get the error:
Error connecting to graphical console:
Error opening Spice console, SpiceClientGtk missing
on whichever VM I try to start.
The Virtual Machine M
On 2017-12-28 01:57 AM, john doe wrote:
On 12/28/2017 5:14 AM, Gary Dale wrote:
When I try to start a virtual machine, I get the error:
Error connecting to graphical console:
Error opening Spice console, SpiceClientGtk missing
on whichever VM I try to start.
The Virtual Machine Manager shows
On Thu, 28 Dec 2017 22:23:05 +0100
Zoltán Herman wrote:
> If started in terminal as root?
I'm not sure what you're asking, but the graphical console works here
even when I launch virt-manager as my regular user (although that user
is a member of groups libvirt, kvm, and adm).
Also, I should not
If started in terminal as root?
2017. dec. 28. 10:01 du. ezt írta ("Celejar" ):
> On Wed, 27 Dec 2017 23:14:31 -0500
> Gary Dale wrote:
>
> > When I try to start a virtual machine, I get the error:
> >
> > Error connecting to graphical console:
> > Error opening Spice console, SpiceClientGtk mis
On Wed, 27 Dec 2017 23:14:31 -0500
Gary Dale wrote:
> When I try to start a virtual machine, I get the error:
>
> Error connecting to graphical console:
> Error opening Spice console, SpiceClientGtk missing
>
> on whichever VM I try to start.
>
> The Virtual Machine Manager shows the VM is run
On 12/28/2017 5:14 AM, Gary Dale wrote:
When I try to start a virtual machine, I get the error:
Error connecting to graphical console:
Error opening Spice console, SpiceClientGtk missing
on whichever VM I try to start.
The Virtual Machine Manager shows the VM is running but I can't connect.
T
Thanks a lot. I blindly followed instructions at first try, which only
mentioned qemu. I found the binary now. Thanks, -Matyas
On Wed, Oct 26, 2016 at 4:52 PM, Thomas Schmitt wrote:
> Hi,
>
> Matyas A. Sustik wrote:
> > the qemu command is not found.
>
> Did you try qemu-system-x86_64 or qemu
On Wed, 26 Oct 2016 16:00:08 +
"Matyas A. Sustik" wrote:
> I installed qemu with apt-get. However the qemu command is not found. What
> am I missing? Can anyone point me in the right direction?
There are individual commands for each architecture. For example to
start qemu for x86_64 you woul
On Wed, 26 Oct 2016 18:20:07 +0200, Matyas A. Sustik wrote:
> I installed qemu with apt-get. However the qemu command is not found. What
> am I missing? Can anyone point me in the right direction?
>
> Thanks!
> -Matyas
I'm not sure what you've got. If it's only the qemu package, and not one
of
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wed, Oct 26, 2016 at 04:00:08PM +, Matyas A. Sustik wrote:
> I installed qemu with apt-get. However the qemu command is not found. What
> am I missing? Can anyone point me in the right direction?
I'm assuming you installed "plain qemu", i.e. no
On 10/26/2016 12:00 PM, Matyas A. Sustik wrote:
I installed qemu with apt-get. However the qemu command is not found. What am I
missing? Can anyone point me in the right direction?
The qemu command does not exist, but qemu- command is there.
mudongliang@debian:~$ qemu-
qemu-aarch64
Hi,
Matyas A. Sustik wrote:
> the qemu command is not found.
Did you try qemu-system-x86_64 or qemu-system-i386 ?
I get a long list of emulated processors by:
ls /usr/bin/qemu-system-*
Have a nice day :)
Thomas
On 12 Aug 2016 1:46 am, "Dan Ritter" wrote:
>
> On Thu, Aug 11, 2016 at 04:08:35PM +0100, Andrew Wood wrote:
> >
> >
> > On 11/08/16 13:47, Igor Cicimov wrote:
> > >
> > > >
> > > What type of network card did you create the vm with? You need to use
> > > the virtio virtual network interface in yo
On 12 Aug 2016 1:08 am, "Andrew Wood" wrote:
>
>
>
> On 11/08/16 13:47, Igor Cicimov wrote:
>>
>>
>> >
>> What type of network card did you create the vm with? You need to use
the virtio virtual network interface in your vm configuration.
>>
> Thanks for your reply. I wondered about that but the
On Thu, Aug 11, 2016 at 04:08:35PM +0100, Andrew Wood wrote:
>
>
> On 11/08/16 13:47, Igor Cicimov wrote:
> >
> > >
> > What type of network card did you create the vm with? You need to use
> > the virtio virtual network interface in your vm configuration.
> >
> Thanks for your reply. I wonder
On 11/08/16 13:47, Igor Cicimov wrote:
>
What type of network card did you create the vm with? You need to use
the virtio virtual network interface in your vm configuration.
Thanks for your reply. I wondered about that but the QEMU wiki doesnt
seem to detail how to configure it to to what
On 11 Aug 2016 1:56 am, "Andrew Wood" wrote:
>
> I've got a host with some QEMU virtual machines on it, the host did have
just one IP address (untagged VLAN) on eth0, Ive now added a second IP on
VLAN 2 (eth0.2). The host machine is working fine but a QEMU VM is not able
to access anything on VLAN
Dear Christian,
Thanks for your replay, I found the root cause. Need use -M malata
parameter.
Regards,
Yanfei
2016-05-27 22:38 GMT+08:00 Christian Seiler :
> On 05/27/2016 06:23 AM, 飞颜 wrote:
> > QEMU start command below:
> > qemu-system-mips -M mips -kernel vmlinux-3.16.0-4-4kc-malta -in
On 05/27/2016 06:23 AM, 飞颜 wrote:
> QEMU start command below:
> qemu-system-mips -M mips -kernel vmlinux-3.16.0-4-4kc-malta -initrd
> initrd.gz -hda hda.img -append "root=/dev/ram console=ttyS0" -nographice
>
> Only show message below, can not run.
> qemu: Warning, could not load MIPS bios 'm
Hi.
On Tue, 29 Dec 2015 21:05:20 +
Andrew Wood wrote:
> On 30/10/15 09:36, Reco wrote:
> > Specifing $SOME_IP instead of 0.0.0.0 should be possible, although I
> > have to admit that I've never tried it (127.0.0.1 does not count). But
> > 'refused to start' lacks some specific deta
On 30/10/15 09:36, Reco wrote:
Specifing $SOME_IP instead of 0.0.0.0 should be possible, although I
have to admit that I've never tried it (127.0.0.1 does not count). But
'refused to start' lacks some specific details: 1) What vnc stanza
have you use? 2) What's the list of IPs on the host tha
Hi.
On Thu, Oct 29, 2015 at 08:47:51PM +, Andrew Wood wrote:
>
>
> On 24/10/15 22:56, Reco wrote:
> >Currently you have three ways of doing it (all do not require X): 1)
> >Universal one, but slow. Adding something like "-vnc 0.0.0.0:0" to qemu
> >commandline will force qemu to provi
On 24/10/15 22:56, Reco wrote:
Currently you have three ways of doing it (all do not require X): 1)
Universal one, but slow. Adding something like "-vnc 0.0.0.0:0" to
qemu commandline will force qemu to provide a VNC server on customary
tcp:5900, and guest OS will draw to VNC server only.
Th
Hi.
On Sat, 24 Oct 2015 22:30:55 +0100
Andrew Wood wrote:
> One other question. Is it possible to run it on a non GUI host ie a
> Debian system without X installed but run guest operating systems which
> do require a GUI such as MS Windows or Haiku?
Sure, that's exactly what big kids
On 24/10/15 17:19, Reco wrote:
I assume you meant https://wiki.debian.org/QEMU. So, for example:
qemu -hda debian.img -cdrom debian-testing-i386-businesscard.iso -boot
d -m 256
translated to the language of current stable, means:
qemu-system-x86_64 -hda debian.img -cdrom \
debian-testing-i3
El 24/10/15 a las 10:13, Andrew Wood escribió:
Can someone please help me configure QEMU on Jessie as the instructions
on the Wiki seem to not apply. The qemu command does not exist in
/usr/bin there are dozens of platform specific ones like /usr/bin/qemu-i386
but these dont seem to accept the
On Sat, 24 Oct 2015 16:13:50 +0100
Andrew Wood wrote:
> Can someone please help me configure QEMU on Jessie as the instructions
> on the Wiki seem to not apply. The qemu command does not exist in
> /usr/bin there are dozens of platform specific ones like /usr/bin/qemu-i386
> but these dont se
Hi,
Andrew Wood wrote:
> there are dozens of platform specific ones like /usr/bin/qemu-i386
> but these dont seem to accept the same args.
I use for a virtual Debian this script "start_debian_amd64":
#!/bin/sh
qemu-system-x86_64 \
-enable-kvm \
-m 512 \
-net nic \
-net us
Hello there,
On Fri, Apr 24, 2015 at 07:50:59AM +0300, Risto Paavola wrote:
> In Debian Jessie, why qemu-kvm has been compiled without glusterfs network
> disk type support?
"""Until glusterfs packaging
is sane I think it's not a good idea to introduce glusterfs support.
Also this is not really
On Fri, 27 Mar 2015 10:04:16 +0200
Martin T wrote:
> Hi,
>
> I need to virtualize few dozen virtual-machines for production
> environment under Debian host-machine. I like the KISS principle
> provided by qemu with KVM support where each utility has its own
> specific purpose. For example I set
* On 2014 20 Nov 23:57 -0600, pe...@easthope.ca wrote:
> A bug report is warranted.
I agree with you. Perhaps someone on the Qemu lists can assist in
debugging:
http://wiki.qemu.org/MailingLists
> Thanks for the help, ... Peter E.
You're welcome.
- Nate
--
"The optimist proclai
From: Nate Bargmann
Date: Thu, 20 Nov 2014 06:15:18 -0600
> I'm curious if you can read the floppy directory contents using the
> 'mdir' command from the mtools package? If you can do that as peter,
> then that may point to a problem with qemu. Just a thought.
This is for a MS-DOS 5.0
1 - 100 of 203 matches
Mail list logo
