On 7/31/24 4:29 AM, Ian Laurie via test wrote:
On 7/31/24 1:26 PM, Robert McBroom wrote:
On 6/15/24 1:02 AM, Robert McBroom wrote:
Following the development of fc41 on a QEMU/KVM virtual machine.
After a few days away, updated to the latest rpms. Booting the
6.10.0-0.rc3.32.fc41 kernel that
On 7/31/24 1:26 PM, Robert McBroom wrote:
On 6/15/24 1:02 AM, Robert McBroom wrote:
Following the development of fc41 on a QEMU/KVM virtual machine.
After a few days away, updated to the latest rpms. Booting the
6.10.0-0.rc3.32.fc41 kernel that came with the updates fails with a
black screen
On 6/15/24 1:02 AM, Robert McBroom wrote:
Following the development of fc41 on a QEMU/KVM virtual machine. After
a few days away, updated to the latest rpms. Booting the
6.10.0-0.rc3.32.fc41 kernel that came with the updates fails with a
black screen with a cursor and some characters in the
Following the development of fc41 on a QEMU/KVM virtual machine. After a
few days away, updated to the latest rpms. Booting the
6.10.0-0.rc3.32.fc41 kernel that came with the updates fails with a
black screen with a cursor and some characters in the center of the
screen that differ with each
On 8/19/23 00:49, Adam Williamson wrote:
Can you file a bug against libvirt on this, with details of how you
upgraded? Can you also check the DNF logs and see if there's any
relevant-looking output during the upgrade indicating that maybe a
scriptlet went wrong?
OK done:
https://bugzilla.redha
On Fri, 2023-08-18 at 18:29 +1000, Ian Laurie wrote:
> On 8/18/23 15:38, Ian Laurie wrote:
> > On 8/18/23 11:40, Ian Laurie wrote:
> > > I upgraded a 38 workstation/server from 38 to 39. The only casualty so
> > > far seems to be that virt-manager can no longer launch VMs.
> > >
> > > Trying to d
On 8/18/23 15:38, Ian Laurie wrote:
On 8/18/23 11:40, Ian Laurie wrote:
I upgraded a 38 workstation/server from 38 to 39. The only casualty so
far seems to be that virt-manager can no longer launch VMs.
Trying to do so results in this:
Error starti
On 8/18/23 11:40, Ian Laurie wrote:
I upgraded a 38 workstation/server from 38 to 39. The only casualty so
far seems to be that virt-manager can no longer launch VMs.
Trying to do so results in this:
Error starting domain: Failed to connect socket t
I upgraded a 38 workstation/server from 38 to 39. The only casualty so
far seems to be that virt-manager can no longer launch VMs.
Trying to do so results in this:
Error starting domain: Failed to connect socket to
'/var/run/libvirt/virtnetworkd-sock
I just installed the F36 Workstation Beta.
Everything seems to be working just fine. I worked on some other stuff. After
a while I returned to the
F36Beta.
The screen was blank (black) with only a cursor in the display.
So, I could find no way to resume my session. Have others seen this iss
seen something like that. qemu will be slow if
kvm isn't enabled, but that's all. And I've never heard anything about
it being deprecated. libvirtd is the underlying management system and I
don't know of any other graphical interface for it other
On 1/26/21 4:03 PM, George R Goffe via test wrote:
I'm having some trouble with qemu and it's console for the vm. This was working fine and
then along came the later versions of the 5.10 kernels. The "new" behavior
makes a console that is about 75% bigger than the ph
Howdy,
I'm having some trouble with qemu and it's console for the vm. This was working
fine and then along came the later versions of the 5.10 kernels. The "new"
behavior makes a console that is about 75% bigger than the physical monitor.
It's effectively unusable.
On Tue, Aug 18, 2020 at 3:06 PM George R Goffe via test
wrote:
>
> Hi,
>
> Sorry to bother you with this (wrong group for this question?). Is there a
> recommended qemu mailing list?
>
> I did a "systemctl status libvirtd" and got back the following: I'm n
Hi,
Sorry to bother you with this (wrong group for this question?). Is there a
recommended qemu mailing list?
I did a "systemctl status libvirtd" and got back the following: I'm not sure
it's a bug or a UFU (User Foul Up).
Please help.
Best regards,
George...
On 11/2/19 5:01 PM, ToddAndMargo via test wrote:
Hi All,
Fedora 30, attempting to upgrade to Fedora 31
# dnf system-upgrade download --refresh --releasever=31 --allowerasing
--best --skip-broken
Error:
Problem: cannot install the best update candidate for package
qemu-system-x86-core-2
Problem: cannot install the best update candidate for package
> qemu-system-x86-core-2:4.1.0-4.fc30.x86_64
>- problem with installed package
> qemu-system-x86-core-2:4.1.0-4.fc30.x86_64
>- package qemu-system-x86-core-2:4.1.0-5.fc31.x86_64 requires
> libvirglrenderer
On 11/2/19 5:01 PM, ToddAndMargo via test wrote:
Hi All,
Fedora 30, attempting to upgrade to Fedora 31
# dnf system-upgrade download --refresh --releasever=31 --allowerasing
--best --skip-broken
Error:
Problem: cannot install the best update candidate for package
qemu-system-x86-core-2
Hi All,
Fedora 30, attempting to upgrade to Fedora 31
# dnf system-upgrade download --refresh --releasever=31 --allowerasing
--best --skip-broken
Error:
Problem: cannot install the best update candidate for package
qemu-system-x86-core-2:4.1.0-4.fc30.x86_64
- problem with installed
On 4/1/19 11:07 AM, pmkel...@frontier.com wrote:
I got curious about qemu today. I read a little about it at the qemu
website. Then I checked to see if their was any qemu on my fedora
workstation. I found that there are many qemu items installed. From the
names of the installed items and what
On Mon, 2019-04-01 at 14:07 -0400, pmkel...@frontier.com wrote:
> I got curious about qemu today. I read a little about it at the qemu
> website. Then I checked to see if their was any qemu on my fedora
> workstation. I found that there are many qemu items installed. From the
>
I got curious about qemu today. I read a little about it at the qemu
website. Then I checked to see if their was any qemu on my fedora
workstation. I found that there are many qemu items installed. From the
names of the installed items and what I read at the website, I started
guessing that
Hi folks! Just wanted to send out a roll-up mail with some specific
requests for testing related to the Fedora 26 release.
1. There's a new qemu build which should fix the proposed blocker
#1467599 . It would be great if anyone who runs F26 and uses virt-
manager, Boxes or qemu in any othe
On Fri, 2015-05-22 at 14:29 -0600, Chris Murphy wrote:
> This has been working this whole test cycle until today and now I'm
> stumped that it's not working.
>
> On the host:
> [root@f22m]# ip addr
> 1: lo: mtu 65536 qdisc noqueue state UNKNOWN
> group default
> link/loopback 00:00:00:00:00:0
This has been working this whole test cycle until today and now I'm
stumped that it's not working.
Host = Fedora 22 up to date, x86_64
Guest = managed by virt-manager, also Fedora 22
1. Install Fedora 22 on the host
2. dnf group install virtualization
3. reboot [1] to get the NAT option for the V
aying with virtualization
>>>> for the first time in a while, installed what i think are all the
>>>> necessary packages, and just want to test virt-manager, so i run
>>>>
>>>> $ virt-manager
>>>>
>>>> am prompted for password,
while, installed what i think are all the
> >> necessary packages, and just want to test virt-manager, so i run
> >>
> >> $ virt-manager
> >>
> >> am prompted for password, then:
> >>
> >> "Unable to connect to libvirt.
> >>
es, and just want to test virt-manager, so i run
> >
> > $ virt-manager
> >
> > am prompted for password, then:
> >
> > "Unable to connect to libvirt.
> >no connection driver available for qemu:///system"
> >
> > and the VMM wind
es, and just want to test virt-manager, so i run
>>
>> $ virt-manager
>>
>> am prompted for password, then:
>>
>> "Unable to connect to libvirt.
>>no connection driver available for qemu:///system"
>>
>> and the VMM window displays:
>
irt-manager
>
> am prompted for password, then:
>
> "Unable to connect to libvirt.
> no connection driver available for qemu:///system"
>
> and the VMM window displays:
>
> "localhost (QEMU) - Not Connected"
>
> is this a permission problem? have
On Fri, 2014-09-12 at 05:18 -0400, Robert P. J. Day wrote:
> what embarrassingly obvious step have i overlooked? thanks.
Well, asking on the right list would be a start. Unless this is a test
version of KVM (you don't give the version so I'm guessing it's not) you
should ask on the Users list.
no connection driver available for qemu:///system"
and the VMM window displays:
"localhost (QEMU) - Not Connected"
is this a permission problem? have i not started the appropriate
system unit?
i've already done a group install of "virtualization", i can see the
app
firewalld in the VM
and on the host and get the same results.
The baremetal host I can ssh to/from without there ever being a problem: ssh
chris@f20s.local
The qemu/kvm guest, I can ssh to/from intermittently: ssh chris@f20sv.local
If I constantly log out and login, it always works, for 3-4 m
>
>
> for qemu, i've opened a bug:
> https://bugzilla.redhat.com/show_bug.cgi?id=814814
>
>
Just a side note: you may also want to subscribe to Fedora Virt list, where
more Virt devs
hanging out.
v...@lists.fedoraproject.org
/kashyap
--
test mailing list
test@lis
On Fri, Apr 20, 2012 at 3:48 PM, cornel panceac wrote:
> for qemu, i've opened a bug:
> https://bugzilla.redhat.com/show_bug.cgi?id=814814
The package is actually qemu-kvm.
--
Lucas
--
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
https://admin.fedoraproject.
cd (tiny core linux) in gnome-boxes,
>> failed (nothing in
>> > journal). I've figured that i can try this also in qemu and so i
>> discovered qemu is not
>> > installed. After installing, attempts to run qemu failed. rpm -ql qemu
>> shows (no installed
>&g
> > journal). I've figured that i can try this also in qemu and so i
> discovered qemu is not
> > installed. After installing, attempts to run qemu failed. rpm -ql qemu
> shows (no installed
> > files). What is going on here? Is the qemu spec broken? Things have
> chang
On 04/20/2012 10:46 AM, cornel panceac wrote:
> One of the things that sounds interesting in the new fedora is gnome-boxes.
> However, every
> attempt i've made to boot a live cd (tiny core linux) in gnome-boxes, failed
> (nothing in
> journal). I've figured that i can
journal). I've figured that i can try this
> also in qemu and so i discovered qemu is not
> installed. After installing, attempts to run
> qemu failed. rpm -ql qemu shows (no installed
> files). W
core
>>> linux) in gnome-boxes, failed (nothing in journal). I've figured that i can
>>> try this also in qemu and so i discovered qemu is not installed. After
>>> installing, attempts to run qemu failed. rpm -ql qemu shows (no installed
>>> files). What i
I've figured that i can
>> try this also in qemu and so i discovered qemu is not installed. After
>> installing, attempts to run qemu failed. rpm -ql qemu shows (no installed
>> files). What is going on here? Is the qemu spec broken? Things have changed
>> and i jus
2012/4/20 cornel panceac
> One of the things that sounds interesting in the new fedora is
> gnome-boxes. However, every attempt i've made to boot a live cd (tiny core
> linux) in gnome-boxes, failed (nothing in journal). I've figured that i can
> try this also in qemu and s
One of the things that sounds interesting in the new fedora is gnome-boxes.
However, every attempt i've made to boot a live cd (tiny core linux) in
gnome-boxes, failed (nothing in journal). I've figured that i can try this
also in qemu and so i discovered qemu is not installed. After
On Thu, 2011-06-23 at 14:30 +0200, Karel Volný wrote:
> (640 MiB just to copy a few files & do a few initial settings?
> seriously?!)
Yes. A lot of this is simply down to loading the default initramfs into
memory; a lot of the rest comes from selinux operations in package
install transactions. T
On Thu, 2011-06-23 at 14:54 +0200, Karel Volný wrote:
> ha! - there is genuine bug
> https://bugzilla.redhat.com/show_bug.cgi?id=715584
That should have been corrected already
(https://bugzilla.redhat.com/show_bug.cgi?id=699770). I've DUP'd your
bug, and reopened the original as it doesn't appea
PM, Karel Volný wrote:
> > > Hi,
> > >
> > > I'm unable to install a testing system ... has anyone else
> > > met https://bugzilla.redhat.com/show_bug.cgi?id=715572 ?
> >
> > Fedora 15 require 640M+ RAM, try with:
> >
> > qemu-kvm
On Thursday 23 of June 2011 14:01:29 Athmane Madjoudj wrote:
> On 06/23/2011 12:53 PM, Karel Volný wrote:
> > Hi,
> >
> > I'm unable to install a testing system ... has anyone else
> > met https://bugzilla.redhat.com/show_bug.cgi?id=715572 ?
>
> Fedora 15
On 06/23/2011 12:53 PM, Karel Volný wrote:
>
> Hi,
>
> I'm unable to install a testing system ... has anyone else met
> https://bugzilla.redhat.com/show_bug.cgi?id=715572 ?
Fedora 15 require 640M+ RAM, try with:
qemu-kvm -m 640 -cdrom Fedora-15-x86_64-DVD.iso F15.qcow2
Hi,
I'm unable to install a testing system ... has anyone else met
https://bugzilla.redhat.com/show_bug.cgi?id=715572 ?
K.
--
Karel Volný
QE BaseOs/Daemons Team
Red Hat Czech, Brno
tel. +420 532294274
(RH: +420 532294111 ext. 8262074)
xmpp ka...@jabber.cz
:: "Never attribute to malice what can
Adam,
On 2011-05-07 13:40, Adam Williamson wrote:
> On Sat, 2011-05-07 at 13:02 +1000, Philip Rhoades wrote:
>> People,
>>
>> As well as the other problems I reported, using this command:
>>
>> qemu-kvm -m 512 -net nic,model=ne2k_pci -net user -cdrom
>>
On Sat, 2011-05-07 at 13:02 +1000, Philip Rhoades wrote:
> People,
>
> As well as the other problems I reported, using this command:
>
> qemu-kvm -m 512 -net nic,model=ne2k_pci -net user -cdrom
> /backup/arch/Fedora-15-i386-netinst.iso
>
> hangs at the line:
>
>
People,
As well as the other problems I reported, using this command:
qemu-kvm -m 512 -net nic,model=ne2k_pci -net user -cdrom
/backup/arch/Fedora-15-i386-netinst.iso
hangs at the line:
"Trying to unpack rootfs image as initramfs. . . "
Thanks,
Phil.
--
Philip Rhoades
GPO Box 3
On Mon, Feb 14, 2011 at 08:26, Ian Pilcher wrote:
> Is anyone able to run a SPICE guest with qemu-kvm 0.14.0?
>
> qemu-kvm-0.14.0-0.1.201102107aa8c46.fc15.x86_64 crashes hard (see
> https://bugzilla.redhat.com/show_bug.cgi?id=677169). I'd expect a bit
> more screaming if ever
Is anyone able to run a SPICE guest with qemu-kvm 0.14.0?
qemu-kvm-0.14.0-0.1.201102107aa8c46.fc15.x86_64 crashes hard (see
https://bugzilla.redhat.com/show_bug.cgi?id=677169). I'd expect a bit
more screaming if everyone was seeing this, though, so posting here to
see if anyone is success
Eric Blake wrote:
> On 08/29/2010 02:16 PM, Matt McCutchen wrote:
>> I am eager to play with systemd, so I tried to install F14 Alpha x86_64
>> on a QEMU virtual machine. The host is my Dell Latitude D620 running
>> F13 x86_64, fully updated with updates-testing enabled. I s
rk. I suggest to append "-m 512" to the start-up
>>> options in order to enable 512 MB of system memory. QEMU default value
>>> is 128 MB of system memory.
>> That was the problem. Thanks.
>>
> Hum if this is a case perhaps it's best to file a bug report
;>
> >> This is unlikely to work. I suggest to append "-m 512" to
> >> the start-up options in order to enable 512 MB of system
> >> memory. QEMU default value is 128 MB of system memory.
> >
> > That was the problem. Thanks.
>
> Hum
On 08/29/2010 02:16 PM, Matt McCutchen wrote:
> I am eager to play with systemd, so I tried to install F14 Alpha x86_64
> on a QEMU virtual machine. The host is my Dell Latitude D620 running
> F13 x86_64, fully updated with updates-testing enabled. I started the
> VM with this comman
>> options in order to enable 512 MB of system memory. QEMU default value
>> is 128 MB of system memory.
> That was the problem. Thanks.
>
Hum if this is a case perhaps it's best to file a bug report and ask for
the default value to be increased to 512 MB
JBG
--
test m
On Mon, 2010-08-30 at 17:20 +0200, Christoph Frieben wrote:
> 2010/8/29 Matt McCutchen wrote:
>
> > Memory: 68088k/131060k available
>
> This is unlikely to work. I suggest to append "-m 512" to the start-up
> options in order to enable 512 MB of system memory. QE
2010/8/29 Matt McCutchen wrote:
> Memory: 68088k/131060k available
This is unlikely to work. I suggest to append "-m 512" to the start-up
options in order to enable 512 MB of system memory. QEMU default value
is 128 MB of system memory.
~Christoph
--
test mail
On Sun, 2010-08-29 at 14:24 -0600, Kevin Fenzi wrote:
> Perhaps it's a bad download? What does sha256sum say about the iso
> against the CHECKSUM file?
I verified the checksum against Fedora-14-Alpha-x86_64-CHECKSUM .
> This is a 64 bit machine right? :)
The host is running an x86_64 kernel, so
On Sun, 29 Aug 2010 16:16:21 -0400
Matt McCutchen wrote:
> I am eager to play with systemd, so I tried to install F14 Alpha
> x86_64 on a QEMU virtual machine. The host is my Dell Latitude D620
> running F13 x86_64, fully updated with updates-testing enabled. I
> started the
I am eager to play with systemd, so I tried to install F14 Alpha x86_64
on a QEMU virtual machine. The host is my Dell Latitude D620 running
F13 x86_64, fully updated with updates-testing enabled. I started the
VM with this command (f14.qcow2 is a blank 4GiB disk image created with
qemu-img
64 matches
Mail list logo
