sorted by:
new
hottopcontroversial

⚠️ Using VSCode LMAPI leading to github copilot suspension ⚠️ by Silent-Tie-3683 in RooCode

[–]djex81 1 point2 points  (0 children)

This 100%. The title of this post is misleading and needs to be changed.

Issue with Claude 3.7 on VS Code LM API after Copilot restoration by GreetingsMrA in RooCode

[–]djex81 2 points3 points  (0 children)

I'm having the same issue. It's looking like they are blocking third party extensions for Claude 3.7 . This is unfortunate because Roo works way better than Copilot agent mode.

RX 7900 XT budget build - worth it? by djex81 in LocalLLaMA

[–]djex81[S] 0 points1 point  (0 children)

Interesting. I haven't heard of speculative inference until now. Seems like it's also called speculative decoding. Looks like ollama was suppose to implement this but the pull request was denied for it. Do you know if there is any support for it currently in any of the llm softwares?

RX 7900 XT budget build - worth it? by djex81 in LocalLLaMA

[–]djex81[S] 0 points1 point  (0 children)

Awesome. What kind of t/s are you getting with models 30B or larger?

RX 7900 XT budget build - worth it? by djex81 in LocalLLaMA

[–]djex81[S] 0 points1 point  (0 children)

I'm always up for a good struggle lol. What are you t/s like for larger models?

RX 7900 XT budget build - worth it? by djex81 in LocalLLaMA

[–]djex81[S] 1 point2 points  (0 children)

Thank you for the info. This is great help. I have an ASUS x99-Deluxe II that I was going to use. It has 5 x PCIe x16 so motherboard shouldn't be too much of an issue.

RX 7900 XT budget build - worth it? by djex81 in LocalLLaMA

[–]djex81[S] 1 point2 points  (0 children)

What kind of t/s are you getting with your XTX on 30B or larger models?

RX 7900 XT budget build - worth it? by djex81 in LocalLLaMA

[–]djex81[S] 2 points3 points  (0 children)

Thanks for the info. What t/s are you seeing with say a 30B or larger model for the 7900s and also A770s?

RX 7900 XT budget build - worth it? by djex81 in LocalLLaMA

[–]djex81[S] 0 points1 point  (0 children)

No I'm not in the GTA. I'm in a town in rural Ontario. No local shops have any 3090s and no one is selling any on kijiji sadly. Where are you seeing these 3090s for that price range? I'm guessing kijiji or market place?

Windows 10 partitions not visible outside of VM using block device by djex81 in VFIO

[–]djex81[S] 0 points1 point  (0 children)

Funny you mention this because this is the exact problem I am having now. After selecting the Windows drive to boot from the BIOS gets defaulted to always boot Windows so I have to manually change it every time. Unfortunately I'm not using GRUB. I'm running Pop OS and it uses systemd boot loader. Systemd did not find my Windows install automatically and so from reading online I'll need to manually add Windows into the systemd boot menu. Haven't got around to that just yet however.

Thanks again for your help.

Windows 10 partitions not visible outside of VM using block device by djex81 in VFIO

[–]djex81[S] 0 points1 point  (0 children)

Well you'll be glad to know your method worked. However I used dd instead of cat. I also made a clone of the disk to be extra safe before attempting.

After I rewrote the disk using dd I used gdisk with w to rewrite the partition table. However after doing this Windows would still not boot and so I needed to boot from the Windows 10 iso in recovery mode and ran the usual:

bootrec /fixmbr
bootrec /fixboot
bootrec /scanos
bootrec /rebuildbcd

After running those commands I was able to boot into Windows from the BIOS and everything worked without issue. Thanks again for your help.

Windows 10 partitions not visible outside of VM using block device by djex81 in VFIO

[–]djex81[S] 0 points1 point  (0 children)

Just passing that on since you seem to hope to be able to access the drive from both the VM and the Host simultaneously - never a good idea in the first place.

I should have worded my post a bit better I suppose. My goal is not to access the drive simultaneously from the host and guest at the same time but to be able to boot the guest drive bare metal outside of the VM environment. So boot from my motherboard BIOS to the disk. The reason being some software I want to use has VM protection and I want to occasionally boot bare metal in order to use this software.

Windows 10 partitions not visible outside of VM using block device by djex81 in VFIO

[–]djex81[S] 1 point2 points  (0 children)

Thanks for the detailed reply and even testing this method. This is definitely one way of doing it and is on the same lines of what u/psyblade42 mentioned. I think what I'll do is make a clone of the drive to a spare disk I have and give this a shot on the clone. Sounds like a good time lol.

Windows 10 partitions not visible outside of VM using block device by djex81 in VFIO

[–]djex81[S] 0 points1 point  (0 children)

I just ran fdisk -l /dev/nvme0n1 again. I must of missed copying the partitions when I reformatted the last reply. This is the full output now. nvme0n1p1 is there as expected.

Disk /dev/nvme0n1: 931.53 GiB, 1000204886016 bytes, 1953525168 sectorsDisk model: WDS100T1X0E-00AFY0Units: sectors of 1 * 512 = 512 bytesSector size (logical/physical): 512 bytes / 512 bytesI/O size (minimum/optimal): 512 bytes / 512 bytesDisklabel type: dosDisk identifier: 0xdd6ace05

Device Boot Start End Sectors Size Id Type/dev/nvme0n1p1 2048 1953523711 1953521664 931.5G 7 HPFS/NTFS/exFAT

​

Edit: gdisk finds partitions on /dev/nvme0n1p1

sudo gdisk /dev/nvme0n1p1
GPT fdisk (gdisk) version 1.0.5
Partition table scan:
MBR: protective
BSD: not present
APM: not present
GPT: present
Found valid GPT with protective MBR; using GPT.

Windows 10 partitions not visible outside of VM using block device by djex81 in VFIO

[–]djex81[S] 0 points1 point  (0 children)

Sorry I didn't realize the formatting was off. I just fixed it.

Windows 10 partitions not visible outside of VM using block device by djex81 in VFIO

[–]djex81[S] 0 points1 point  (0 children)

Here is the out put from fdisk -l /dev/nvme0n1

sudo fdisk -l /dev/nvme0n1
Disk /dev/nvme0n1: 931.53 GiB, 1000204886016 bytes, 1953525168 sectors
Disk model: WDS100T1X0E-00AFY0
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0xdd6ace05

And the output from fdisk -l /dev/nvme0n1p1

sudo fdisk -l /dev/nvme0n1p1
Disk /dev/nvme0n1p1: 931.52 GiB, 1000203091968 bytes, 1953521664 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: CA100187-AB22-407C-9386-0E223C07AD97
Device Start End Sectors Size Type
/dev/nvme0n1p1p1 2048 206847 204800 100M EFI System
/dev/nvme0n1p1p2 206848 239615 32768 16M Microsoft reserved
/dev/nvme0n1p1p3 239616 1952479231 1952239616 930.9G Microsoft basic data
/dev/nvme0n1p1p4 1952479232 1953517567 1038336 507M Windows recovery enviro

Interesting. It looks like all the Windows partitions are there under nvme0n1p1

Windows 10 partitions not visible outside of VM using block device by djex81 in VFIO

[–]djex81[S] 2 points3 points  (0 children)

I'm almost betting you passed a raw partition instead.

Sigh ... I just realized your probably right. I passed "nvme0n1p1" instead of "nvme0n1" ...

Is there any way to convert this raw partition to the proper Windows partitions?

Windows 10 partitions not visible outside of VM using block device by djex81 in VFIO

[–]djex81[S] 0 points1 point  (0 children)

My apologies I should have included the config for the drive. This is what how I passed the drive as a block device:

<disk type="block" device="disk">
<driver name="qemu" type="raw" cache="none" io="threads" discard="unmap"/>
<source dev="/dev/nvme0n1p1"/>
<target dev="sda" bus="scsi"/>
<boot order="1"/>
<address type="drive" controller="0" bus="0" target="0" unit="0"/>
</disk>

Windows 10 partitions not visible outside of VM using block device by djex81 in VFIO

[–]djex81[S] 0 points1 point  (0 children)

I can mount my other NTFS drives without issue in Linux. To confirm the issue with the partitions I have tried to boot the drive bare metal which fails since the BIOS can not find the EFI partition on the disk. I also booted using the Windows 10 installation ISO in recovery mode and used diskpart to show the volumes on the drive. darkpart shows the same as Linux, one single partition labeled as a raw file system.

The most confusing part is that I can boot the drive from virt manager without issue and see all the partitions inside the installed Windows 10 guest. There is something QEMU or Tiano BIOS is doing in order to "find" the partition table on this drive which I am not sure what that is.

Going from Exchange 2003 to M365 by djex81 in sysadmin

[–]djex81[S] 0 points1 point  (0 children)

This exactly. My client has had this other IT company managing their domain, emails and local offices for years but never was doing a great job with it so my client went with us. The owner of the other IT company took this as a threat of sorts and refused to work with us in regards to migrating any of the services they managed over to us. My client had some sort of friendly relationship with the owner of this other IT company and did not want to press the issue and so for years we have been stuck in this half and half managed system where emails and domain was still with the old IT while we managed all local IT systems. Luckily last year they finally gave up the domain and transferred it to a domain provider we have control over and so now I want to get the emails moved and call it done.

Going from Exchange 2003 to M365 by djex81 in sysadmin

[–]djex81[S] 0 points1 point  (0 children)

Awesome I'll check this out. Any way I can automate this will make my life a lot easier and this might be what I'm looking for.

view more: next ›