I dont even know what driver you are talking about lmao
I dont even know what driver you are talking about lmao
Lthe disk is on the same drive as the OS
Leverything is the same drive
Hvirtiofsd in the guest tools
Hthe thing that handles mounting the folder
Lyou mean the shared folder? or you mean the folder for the guest OS?
Hthe only difference (except alias which will have no performance impact) is that i use a queue size of 1024
Ljust to be clear the shared folder is not the issue, im saying i can only download anything from the internet in the guest OS at 0.1MB a second
Hin the xml i have
instead of
instead of
Hoh well you worded it as if you had horrible performance getting things from the shared folder
Lim glad that confusion is cleared up now
Lso yeah how do I fix that?
Hok in that case should be a lot easier if its actually just downloads that are the issue
Lcorrect
His the guest OS windows or linux?
Llinux
Hmake sure the device model for the nic (network card) in the virtual machine is set to virtio
Lit is
Lalready
Hthats a paravirtualized device, meaning the OS will go "oh this is virtual hardware" and actually communicate directly with the host hardware
Hhmm
Hwhat are the other settings set on it?
Lon what? on the NIC?
Lor you mean other settings for the guest OS?
Llink state active on NIC
Lmemory 4096, shared
L4 VCPU
Lcopy host cpu config
His the nic set to NAT or something else?
LNAT
UHey friends. Running Bazzite on my desktop - I've been on version 39.20231206.0 (2023-12-07T01:17:30Z) for quite a while now. My tag is docker://ghcr.io/ublue-os/bazzite:latest
- is there an issue preventing new builds for this version? I remember we had a recent glibc issue (I think it was glibc) that paused updates for a spell
Hcan you try have it as macvtap and put your network card as the device name (should be something like enpXsY with x and y being numbers)
Hjust want to see if its the NAT causing the issue
LI can try that when the OS finishes updating
Lapparently 16 minutes remaining, and already been like 2 hours lol
Hfailed builds are normal, do not worry about it unless the build is closer to a month old i would say, so that you havent had a new update for about 7 days is nothing to worry about.
as for if there are any issues preventing new builds, usually it is upstream issues which eventually get resolved, it is better the builds fail in github rather than you getting a broken system due to upstream issues
as for if there are any issues preventing new builds, usually it is upstream issues which eventually get resolved, it is better the builds fail in github rather than you getting a broken system due to upstream issues
UAgreed on the "better to let github suffer" piece. I'm new to using an rpm-ostree distro, so I'm just wondering about the typical cadence
Hrip, feel free to just @ me when its done then.
my VM doesnt have any network speed issue so its super weird that yours do
my VM doesnt have any network speed issue so its super weird that yours do
Lwell i did install this: rpm-ostree install virt-install libvirt-daemon-config-network libvirt-daemon-kvm qemu-kvm virt-viewer guestfs-tools pyt
hon3-libguestfs virt-top
hon3-libguestfs virt-top
Lif it has anything to do with it?
Las i could not find any help with it and so i found that online
Hyeah i wouldnt worry about lack of a new build unless its been closer to a month (or there is a severe exploit that just got patched that is actively being exploited in the wild)
Uto be clear, my system is running perfectly well.
Hand we dont want it any other way 
UI appreciate that
PDoes your CPU actually have virtualization support? And enabled in bios?
Lyes
Hnot sure what libvirt-daemon-config-network changes or if its pulled in by the "enable-virtualization" command which installs "edk2-ovmf, qemu and virt-manager"
will have to fire up a fedora VM and check
will have to fire up a fedora VM and check
Hi would believe its pulled in by the other commands but its the only package that would fiddle with anything network related
Live run VMplayer and virtual box just fine in other distros in the past pintocat, with no issues with sharing folders or network speeds
LI first used the just enable-virtualization, then rebooted, then i did the rpm-ostree install virt-install libvirt-daemon-config-network libvirt-daemon-kvm qemu-kvm virt-viewer guestfs-tools pyt
hon3-libguestfs virt-top then rebooted, and then you told me those other commands and i tried those and it finally made virtual manager work
hon3-libguestfs virt-top then rebooted, and then you told me those other commands and i tried those and it finally made virtual manager work
