ANNOUNCE: Forthcoming changes to libvirt mailing list hosting
by Daniel P. Berrangé
Hello Libvirt Community,
For the last 18(!) years, libvirt community mailing lists have been kindly
hosted by Red Hat Corporate IT on the redhat.com Mailman installation.
In retrospect this wasn't the ideal home for community mailing lists but
that decision is ancient history.
Unfortunately as a consequence of infrastructure changes, the redhat.com
Mailman service is scheduled to be decomissioned, and in the very near
future ($low weeks) will cease to be able to send/receive mail for
libvirt lists.
As a result, all the libvirt mailing lists will need to move to a new
Mailman installation, managed on our behalf by the Red Hat Open Source
Community Infrastructure team[1], who provide services for a variety
of OSS projects.
It is intended that this new service will be dedicated for our community
and thus located somewhere under the libvirt.org domain. It should go
without saying that all existing mail archives will be migrated over to
the new server. None of the historical record should be lost.
It is not considered appropriate netiquette, however, to bulk-resubscribe
all current list members under a new domain. Thus anyone who wants to
remain on the community lists will soon be requested to take action
to enroll on the new mailman service.
The new service is not quite ready for use yet.
This mail serves as a heads up that the changes will be coming in the
next couple of weeks that will require action. A further announcement
will be sent when the new mailman is ready to accept subscriptions,
as well as warnings before the old lists stop accepting messages.
With regards,
Daniel
[1] https://www.osci.io/
--
|: https://berrange.com -o- https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o- https://fstop138.berrange.com :|
|: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
1 year
Problem starting Windows 11 EE
by Rahul S
Hi,
I configured a W11EE VM using virt-manager and joined it to my work
domain. Everything was fine for a while. Later when I tried to reboot,
I got the "Preparing Automatic Repair" message and when I selected
"Startup Repair", I got the error "Startup repair couldn't repair your
PC". I then went to command prompt, started 'diskpart' and ran "list
disk" and got the error "there are no fixed disks to show". I have
tried re-installing several times - it always ends up in this state.
A few details of my system:
host OS: OpenSUSE 15.5
libvirt version: 9.0.0-150500.4.3
virtio drivers:
https://fedorapeople.org/groups/virt/virtio-win/direct-downloads/archive-...
Disk device type: virtio
bitlocker is enabled in VM
I am able to configure and use W11-professional without joining my
work domain. The above problem isn't seen there.
I booted the broken VM using my linux rescue disk image and examined
the partition table. Everything seems to be proper. But windows isn't
able to find the disk as I explained above.
Can anybody provide any pointers for troubleshooting this ?
Thanks,
-Rahul
1 year
any advantage to using pool type glusterfs if no GFAPI
by W Kern
I have used fuse mounted gluster with 'dir' for years. Works great,
aside from having to use the --unsafe flag on migrations.
I am building up a new system and wondering if using the glusterfs type
would be a better/safer choice.
I'm not concerned about gfapi (host is U22LTS so I'm not even sure if it
has it).
I'm not concerned about the automount feature as that happens on start
up anyway.
I'm more interested if there is any technical or performance reasons to
prefer 'glusterfs' pool type over 'dir'
of course not having the --unsafe flag would be nice, but thats all
scripted in anyway.
-wk
1 year
Issue accidentally creating a '--type' defined pool
by Joshua Blake
Hello,
I seem to have accidentally created a pool called "--type", but it
doesn't appear in 'virsh pool-list'. See below.
[root@vh01 /]# virsh pool-define-as --name --type dir --target
/data/storage/
Pool --type defined
[root@vh01 /]# virsh pool-list
Name State Autostart
------------------------------
isos active yes
jblake active yes
[root@vh01 /]# virsh pool-destroy '--type'
error: command 'pool-destroy' doesn't support option --type
I can't also create a new "default" type because the directory exists
for this defined '--type'
[root@vh01 /]# virsh pool-define-as --name default --type dir --target
/data/storage/
error: Failed to define pool default
error: operation failed: Storage source conflict with pool: '--type'
[root@vh01 /]# virsh pool-delete "--type"
error: command 'pool-delete' doesn't support option --type
Any help would be greatly appreciated.
1 year
