On 14.04.20 19:32, sean darcy wrote:
...
The virt io tab shows storage format as "dir". I can't figure out the
location of the actual xml file that VMM creates. Sigh.
I'm not sure, but I guess somewhere in your home dir under
~/.config/ or
~/.local/
?!
--
sixpack13
__
On 4/14/20 10:32 AM, sean darcy wrote:
The virt io tab shows storage format as "dir". I can't figure out the
location of the actual xml file that VMM creates. Sigh.
/etc/libvirt/qemu
___
users mailing list -- users@lists.fedoraproject.org
To unsubscri
I'm trying to create a small virtual guest for debian using Virtual
Machine Manager. I accept all the defaults, but:
Unable to complete install: 'unsupported configuration: 'directory'
storage format is not directly supported by QEMU, use 'dir' disk type
inst
On Thu, 2019-01-03 at 16:13 -0800, Gordon Messmer wrote:
> On 12/31/18 6:31 AM, Patrick O'Callaghan wrote:
> > When it happened before I edited the XML file to remove the .osxsave
> > flag and that solved the problem. However now it's happening with a
> > fresh VM so there's no XML file to edit.
>
On 12/31/18 6:31 AM, Patrick O'Callaghan wrote:
When it happened before I edited the XML file to remove the .osxsave
flag and that solved the problem. However now it's happening with a
fresh VM so there's no XML file to edit.
Try commenting out that feature in /usr/share/libvirt/cpu_map.xml
__
I currently run a couple of VMs (one Windows 10 and one Fedora Server)
under QEMU/KVM. I wanted to create a new one and got this:
Unable to complete install: 'internal error: process exited while connecting
to monitor: 2018-12-31T14:23:14.816147Z qemu-system-x86_64: can't apply global
IvyBrid
On 07/31/17 10:12, Tom Horsley wrote:
Should be simple to move unless something has
become incompatible. Just copy the /etc/libvirt/qemu
xml files from old system to new as well as either
copying the virtual disk images or simply editing
the xml to point to the locations of the virtual disks
on t
On Mon, 31 Jul 2017 09:23:59 -0400
Bob Goodwin wrote:
> VM on Fedora 25 has Windows 10 running
> on it. How do I move that to
> virt-manager on the Fedora 26 system? Or
> is it simpler to make a new installation?
Should be simple to move unless something has
become incompatible. Just copy the
This computer runs Fedora 25 on /dev/sdb
and Fedora 26 on /dev/sda. I use the
boot menu to select the drive and system
I want, it defaults to Fedora 26.
VM on Fedora 25 has Windows 10 running
on it. How do I move that to
virt-manager on the Fedora 26 system? Or
is it simpler to make a new
On Fri, Oct 7, 2011 at 3:32 PM, suvayu ali wrote:
> On Wed, Oct 5, 2011 at 6:56 PM, Daniel J Walsh wrote:
> > Sanjay you might want to ask on the libvirt list...
>
> Maybe try Daniel's suggestion about asking on the libvirt list? There
> is a dedicated fedora libvirt list, I believe that might be
On Wed, Oct 5, 2011 at 6:56 PM, Daniel J Walsh wrote:
> Sanjay you might want to ask on the libvirt list...
Maybe try Daniel's suggestion about asking on the libvirt list? There
is a dedicated fedora libvirt list, I believe that might be more
appropriate.
--
Suvayu
Open source is the future. I
On Wed, Oct 5, 2011 at 9:43 PM, Rick Stevens wrote:
>
> I'd try again with SELinux disabled (edit /etc/selinux/config, change
> the mode to disabled and reboot). If things work then, I'd re-enable
> SELinux, "touch /.autorelabel", reboot and try again.
Changed selinux to disabled...output from
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 10/05/2011 12:13 PM, Rick Stevens wrote:
> On 10/05/2011 06:18 AM, Daniel J Walsh wrote:
>
> [snip]
>> You are also running in permissive mode, which should not block
>> any thing via SELinux.
>
> That's not necessarily true. Even in permissive m
On 10/05/2011 06:18 AM, Daniel J Walsh wrote:
[snip]
> You are also running in permissive mode, which should not block any
> thing via SELinux.
That's not necessarily true. Even in permissive mode, SELinux has some
stuff it does in the kernel. I've seen things STILL not work with
SELinux in per
Results same on freshly started systemnormal user not being asked
authentication by vmm & vmm connection failing...
libvirtd is running as daemon on system start...vmm fails here
[root@acct] Wed, 05 October, 2011. 07:39:44 PM, IST.
[~] ps aux |grep -e "libvirtd"
root 1696 0.0 0.1
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 10/05/2011 07:54 AM, suvayu ali wrote:
> Hi Sanjay,
>
> On Wed, Oct 5, 2011 at 1:25 PM, Sanjay Arora
> wrote:
>> Running VMM as normal user still not connecting to
>> libvirtdnot showing messagebox for password to enable correct
>> permissions
Hi Sanjay,
On Wed, Oct 5, 2011 at 1:25 PM, Sanjay Arora wrote:
> Running VMM as normal user still not connecting to libvirtdnot showing
> messagebox for password to enable correct permissionstested login from
> root cli...works fine...so its a permissions issue...due to gui not getting
>
Running VMM as normal user still not connecting to libvirtdnot showing
messagebox for password to enable correct permissionstested login from
root cli...works fine...so its a permissions issue...due to gui not getting
pass from user...
libvirtd output:
[root@acct] Wed, 05 October, 2011. 0
Hi Sanjay,
On Tue, Oct 4, 2011 at 8:00 PM, Sanjay Arora wrote:
> assumed the same on f15, so took that shortcut temporarily.
>
>>
>> On F14 something like
>> this should resolve the error,
>>
>> # chkconfig --level 35 libvirtd on # libvirtd on for runlevel 3 & 5
>> # service libvirtd start # star
Suvayu
On Tue, Oct 4, 2011 at 10:40 PM, suvayu ali wrote:
>
> No it is not a bug. You need to run the libvirtd daemon before you can
> use hardware virtualised machines. I would also advise against your
> current workaround of running GUI apps as root.
Agree with you on not running gui apps as r
Hi Sanjay,
On Tue, Oct 4, 2011 at 6:48 PM, Sanjay Arora wrote:
> seems its a bug
No it is not a bug. You need to run the libvirtd daemon before you can
use hardware virtualised machines. I would also advise against your
current workaround of running GUI apps as root. On F14 something like
this s
Ahh...got it...seems its a buglaunched from cli as root and no probs
anymore...sorry to bother you all ;-)
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.
I am running fedora 15. Trying to do first VM install. Getting the following
error while libvirtd running. Restarted it and still same error...
Error: Virtual Machine Manager Connection Failure
Unable to open a connection to the libvirt management daemon.
Libvirt URI is: qemu:///system
Verify
FC13/KDE
Trying to start virt-manager And I get this Error Message below, What
now ??
The network is running okay on br0 .
I tried to run gconf-cleaner, but I get the same Error Message.
Error Message:
Error starting Virtual Machine Manager: Failed to contact configuration
server; some
24 matches
Mail list logo
