Griminal

I have not. I suppose I could try that.

Disk2 decided it wanted to be corrupt too. I haven't fixed that one yet. Questioning my hardware at this point. I will respond back when I figure out what to do. Thank you.

I appreciate the help. Attached diagnostics. I'll hold off on a "new config" until I hear if you all have any concerns. hyde-diagnostics-20240326-1218.zip

Hello. So I had a HBA die out on me. Disk3 became disabled. I removed Disk3 from the array, attempted to mount it, and it failed. I performed a check on it and everything repaired successfully. I'm able to mount and browse the disk now. My concern, if I add the drive back to the array, will it overwrite all the files on it? If a parity check happens, will it consider all the files currently on the drive? Right now, my shares are missing a lot of files... because they were stored on Disk3. I had to do a lot of reboots diagnosing the HBA issue. Sorry for my vague questions. The old brain isn't working like it used to.

I ended up downgrading to Version: 6.12.4 after the file check. No more problems so far.

So I moved Disk2 to a mobo SATA port, away from the LSI controller. Parity is at ~20% at this time. I'm keeping an active browser window up to capture the logs. I'm seeing this thus far. Its been rebuilding for 5 hours. Feb 1 18:26:50 hyde kernel: mpt2sas_cm0: log_info(0x31080000): originator(PL), code(0x08), sub_code(0x0000) Feb 1 18:26:50 hyde kernel: mpt2sas_cm0: log_info(0x31080000): originator(PL), code(0x08), sub_code(0x0000) Feb 1 18:26:50 hyde kernel: mpt2sas_cm0: log_info(0x31080000): originator(PL), code(0x08), sub_code(0x0000) Feb 1 18:26:55 hyde kernel: mpt2sas_cm0: log_info(0x31110d01): originator(PL), code(0x11), sub_code(0x0d01) Feb 1 18:26:55 hyde kernel: mpt2sas_cm0: log_info(0x31110d01): originator(PL), code(0x11), sub_code(0x0d01) Feb 1 18:26:55 hyde kernel: mpt2sas_cm0: log_info(0x31110d01): originator(PL), code(0x11), sub_code(0x0d01) Feb 1 18:26:55 hyde kernel: mpt2sas_cm0: log_info(0x31110d01): originator(PL), code(0x11), sub_code(0x0d01) Feb 1 18:26:55 hyde kernel: mpt2sas_cm0: log_info(0x31110d01): originator(PL), code(0x11), sub_code(0x0d01) Feb 1 18:26:55 hyde kernel: mpt2sas_cm0: log_info(0x31110d01): originator(PL), code(0x11), sub_code(0x0d01) Feb 1 18:26:55 hyde kernel: mpt2sas_cm0: log_info(0x31110d01): originator(PL), code(0x11), sub_code(0x0d01) Feb 1 18:26:55 hyde kernel: mpt2sas_cm0: log_info(0x31110d01): originator(PL), code(0x11), sub_code(0x0d01) Feb 1 18:26:55 hyde kernel: mpt2sas_cm0: log_info(0x31110d01): originator(PL), code(0x11), sub_code(0x0d01) Feb 1 18:26:55 hyde kernel: mpt2sas_cm0: log_info(0x31110d01): originator(PL), code(0x11), sub_code(0x0d01) Feb 1 18:26:55 hyde kernel: mpt2sas_cm0: log_info(0x31110d01): originator(PL), code(0x11), sub_code(0x0d01) Feb 1 18:26:55 hyde kernel: mpt2sas_cm0: log_info(0x31110d01): originator(PL), code(0x11), sub_code(0x0d01) Feb 1 18:26:55 hyde kernel: sd 9:0:4:0: Power-on or device reset occurred Feb 1 18:26:56 hyde kernel: sd 9:0:4:0: Power-on or device reset occurred

What would have filled up the logs in a 12 hour period? Maybe my LSI card is having issues? Maybe the breakout cable is going? What recommendations do you have for me to go forward after I reboot?

Done. I paused the re-build. Shares, docker, and VMs are back. I'm scared to touch anything.... Diagnostics posted. hyde-diagnostics-20240201-1104.zip

Phase 1 - find and verify superblock... Phase 2 - using internal log - zero log... ALERT: The filesystem has valuable metadata changes in a log which is being destroyed because the -L option was used. - scan filesystem freespace and inode maps... clearing needsrepair flag and regenerating metadata sb_fdblocks 1771110769, counted 1775009412 - found root inode chunk Phase 3 - for each AG... - scan and clear agi unlinked lists... - process known inodes and perform inode discovery... - agno = 0 - agno = 1 - agno = 2 - agno = 3 - agno = 4 - agno = 5 - agno = 6 - agno = 7 - agno = 8 - agno = 9 - agno = 10 - agno = 11 - agno = 12 - agno = 13 - agno = 14 - agno = 15 - process newly discovered inodes... Phase 4 - check for duplicate blocks... - setting up duplicate extent list... - check for inodes claiming duplicate blocks... - agno = 0 - agno = 4 - agno = 7 - agno = 2 - agno = 6 - agno = 8 - agno = 9 - agno = 5 - agno = 10 - agno = 11 - agno = 12 - agno = 13 - agno = 1 - agno = 15 - agno = 14 - agno = 3 Phase 5 - rebuild AG headers and trees... - reset superblock... Phase 6 - check inode connectivity... - resetting contents of realtime bitmap and summary inodes - traversing filesystem ... - traversal finished ... - moving disconnected inodes to lost+found ... Phase 7 - verify and correct link counts... Maximum metadata LSN (694513559:307199) is ahead of log (1:2). Format log to cycle 694513562. done

Phase 1 - find and verify superblock... Phase 2 - using internal log - zero log... ERROR: The filesystem has valuable metadata changes in a log which needs to be replayed. Mount the filesystem to replay the log, and unmount it before re-running xfs_repair. If you are unable to mount the filesystem, then use the -L option to destroy the log and attempt a repair. Note that destroying the log may cause corruption -- please attempt a mount of the filesystem before doing this.

I posted a few days ago. (link below) I ran in emulated mode for a few days. The new drive arrived, I shut down the system and inserted the new drives and selected one of them as DISK1. Started up the array and the re-build was in process like I expected. I even started throwing some of my backup-ed files back on the array as the parity check was going. I went to bed. I check it this AM, all my shares are missing.... I browse DISK1 and DISK2 now, and it looks like the root of a *nix system! (see screenshot) I'm beside myself. I replaced a dozen drives in the same way and I just don't understand. I just don't know what to do anymore. I've stop the array rebuild and won't touch the system until someone gives me some more guidance. I have 3 non-array members. I have two internal drives in the system, a brand new one ZR5F463E that I haven't formatted yet. ZL2LCCS2 was the original drive with CRC errors that I don't have mounted, but left in the slot. Z84109XN is one of the backup drives I had mounted to copy some data back to the array. I don't know what's happening. I'm quickly losing faith in my build. Here's my previous post: hyde-diagnostics-20240201-0813.zip

Yep. Ordered a replacement drive so I could do just that. I learned a lot of lessons this time. Thanks for the help.

Mounted ZL2LCCS2 has lost+found. Some data is there. Doing a search for files larger than 2GB yields no results. I have a few ISOs that went missing. Phase 1 - find and verify superblock... Phase 2 - using internal log - zero log... - scan filesystem freespace and inode maps... - found root inode chunk Phase 3 - for each AG... - scan and clear agi unlinked lists... - process known inodes and perform inode discovery... - agno = 0 - agno = 1 - agno = 2 - agno = 3 - agno = 4 - agno = 5 - agno = 6 - agno = 7 - agno = 8 - agno = 9 - agno = 10 - agno = 11 - agno = 12 - agno = 13 - agno = 14 - agno = 15 - process newly discovered inodes... Phase 4 - check for duplicate blocks... - setting up duplicate extent list... - check for inodes claiming duplicate blocks... - agno = 0 - agno = 5 - agno = 11 - agno = 2 - agno = 4 - agno = 1 - agno = 8 - agno = 7 - agno = 10 - agno = 6 - agno = 12 - agno = 9 - agno = 13 - agno = 14 - agno = 15 - agno = 3 Phase 5 - rebuild AG headers and trees... - reset superblock... Phase 6 - check inode connectivity... - resetting contents of realtime bitmap and summary inodes - traversing filesystem ... - traversal finished ... - moving disconnected inodes to lost+found ... Phase 7 - verify and correct link counts... done

Will do. Thanks for the help. No changes to diagnostics. I ordered a few new 16TB and I'll wait for those before I make massive file changes. Disk1 emulated: Phase 1 - find and verify superblock... Phase 2 - using internal log - zero log... - scan filesystem freespace and inode maps... - found root inode chunk Phase 3 - for each AG... - scan (but don't clear) agi unlinked lists... - process known inodes and perform inode discovery... - agno = 0 - agno = 1 - agno = 2 - agno = 3 - agno = 4 - agno = 5 - agno = 6 - agno = 7 - agno = 8 - agno = 9 - agno = 10 - agno = 11 - agno = 12 - agno = 13 - agno = 14 - agno = 15 - process newly discovered inodes... Phase 4 - check for duplicate blocks... - setting up duplicate extent list... - check for inodes claiming duplicate blocks... - agno = 0 - agno = 5 - agno = 7 - agno = 13 - agno = 4 - agno = 6 - agno = 8 - agno = 11 - agno = 1 - agno = 9 - agno = 10 - agno = 12 - agno = 15 - agno = 14 - agno = 2 - agno = 3 No modify flag set, skipping phase 5 Phase 6 - check inode connectivity... - traversing filesystem ... - traversal finished ... - moving disconnected inodes to lost+found ... Phase 7 - verify link counts... No modify flag set, skipping filesystem flush and exiting. Non-member: FS: xfs Executing file system check: /sbin/xfs_repair -n '/dev/sdg1' 2>&1 Phase 1 - find and verify superblock... Phase 2 - using internal log - zero log... - scan filesystem freespace and inode maps... - found root inode chunk Phase 3 - for each AG... - scan (but don't clear) agi unlinked lists... - process known inodes and perform inode discovery... - agno = 0 - agno = 1 - agno = 2 - agno = 3 - agno = 4 - agno = 5 - agno = 6 - agno = 7 - agno = 8 - agno = 9 - agno = 10 - agno = 11 - agno = 12 - agno = 13 - agno = 14 - agno = 15 - process newly discovered inodes... Phase 4 - check for duplicate blocks... - setting up duplicate extent list... - check for inodes claiming duplicate blocks... - agno = 0 - agno = 5 - agno = 9 - agno = 12 - agno = 15 - agno = 4 - agno = 7 - agno = 6 - agno = 8 - agno = 10 - agno = 11 - agno = 13 - agno = 14 - agno = 2 - agno = 1 - agno = 3 No modify flag set, skipping phase 5 Phase 6 - check inode connectivity... - traversing filesystem ... - traversal finished ... - moving disconnected inodes to lost+found ... Phase 7 - verify link counts... No modify flag set, skipping filesystem flush and exiting. No file system corruption detected!

Trurl... thannks for the responses. Unfortunately, I think I screwed up at step 4. The instructions don't say explicitly say "allow the array to rebuild"... I stopped it at like .3% and moved on to step 4. So I think I'm hosed. Oddly, Plex hasn't reflected some of these files being removed. Normally, as soon as the file system is changed, it reflects it. Any options for me or am I out of luck? I don't see the missing files in emulated or on the mounted, non-member data disk. 1. Stop array 2. Un-assign disabled disk 3. Start array so the missing disk is registered 4. Important: If the drive to be rebuilt is a data drive then check that the emulated drive is showing the content you expect to be there as the rebuild process simply makes the physical drive match the emulated one. If this is not the case then you may want to ask in forums for advice on the best way to proceed. 5. Stop array 6. Reassign disabled disk

I had a disk become disabled so I did the procedure to remove it from the array and add it back. SMART data was good. I rebooted the server and saw the screenshot I have attached. So I removed the offending drive again, rebooted, and did an XFS_repair while the disk was out of the array. I left the drive out and am going to purchase a replacement drive, just to have a spare. I then noticed a lot of data missing. I see a lot of data in my lost+found. It seems like my emulated data must have been wrong. I'm not sure. Files and folders I've added for the past month or so seem to be missing data. Maybe I have BTRFS issues? I hope?? hyde-diagnostics-20240127-2321.zip

I had to contact support for a new key file... automated key recovery did not work for me. I followed the doc JorgeB posted to ease my concerns. I'm back up. Sorry for freaking out.

Hey all. I've been running UnRAID for years now. I recently upgraded to a MSI B760 motherboard and an i5-13500 on my main rig. I took a backup of my flash before I changed equipment. I got the system to boot with the new hardware... as it should, perfect! I added two 8TB drives to my already existing four 16TB drives. Everything good so far... keep going. I upgraded from 6.9.2 to 6.12.4. Then I started having stability issues. Freezes, etc. Disabled c-states, changed over to ipvlan. I thought I had her licked. Get up this AM, can't ping the system again. Hit the power button on the system and it immediately turns off. I try to reboot, the system kept going into the BIOS. I put the Kingston 8GB flash drive into a Windows system.... nothing on it nor can it be formatted. "No Media" D.O.A. Here's my problem: with all my troubleshooting for freezes and such, I forgot to take a backup of the flash after I added the two 8TB drives! Stupid!! I've restored my 6.9.2 to another USB drive. Issue 1: I've never transferred a key from one drive to another, so I need to figure that out. ( I do have my 6.9.2 flash backup ) Issue 2: I don't know what the 8TB drive slot allocations were. (either Disk 4 or Disk 5)... and I'm scared to start the array with them out of order in fear of corrupting the array. Can they be out of order? Issue 3: Should I just create a new USB with 6.12.4? I do know the parity and cache drive allocations... I just don't have where the 8TBs were. I'm hard down here, I'm a little frazzled, frustrated with the hardware issues and stability problems I'm having. I can't believe the perfect storm with the flash drive exploding. I've been in I.T. for over 20 years so of course my wife is giving me the business because I should know what I'm doing.... "Why aren't the security cameras up? Why isn't Plex working?" Can anyone give me some advice? 64TB array in jeopardy!!

Just wanted to give another option as I just did it. Option #1: From a Linux machine, go to their tool site: amdrewards.com/pvt. Download and you should be prompted to save pvt.sh. Throw it into a directory in UnRaid, open a shell, chmod 777 pvt.sh, then sh pvt.sh. Follow the instructions. Option #2: (What I did.) From a Windows machine, install a user agent addon to change the browser's user agent to a Linux signature. When you click the download button, you'll be prompted to save the pvt.sh file. Throw it into a directory in UnRaid, open a shell, chmod 777 pvt.sh, then sh pvt.sh. Follow the instructions. I believe the pvt.sh file is built on the fly when you download it as I didn't have to sign into the tool. So I'm sure the installer can't be past around to just any Tom, Dick, or Harry. At that point you can log into https://www.amdrewards.com/my-rewards. You should be able to complete your reward at this point.

Got the USB passed through. Device Manager was showing "usb xhci compliant host controller" and it couldn't load it into memory. I removed the controller and rebooted the VM. Turned it back off, added it again, and it was there and working. I still don't have audio though... Anybody? Maybe it is pushing through and windows isn't seeing it correct? Unknown device is ACPI\APP0005\3&2411E6FE&1.

Hi all. Sorry for the long, first post but I had to vent out so I don't blow my brain out. Running 6.8.3. I've been running a first gen Ryzen 5 1600 server. A Win10 VM is my daily driver, pushing 3 displays through a GTX 1070, audio flowing out of the motherboard's 1/8 audio jack to my speakers, and passing through USB ports. Add a few dockers and a linux VM here and there. Life was great! I need more power I tell myself... so I bought a Ryzen 9 3900x. I kept my same motherboard (Gigabyte B450 Aorus M) and RAM (2-32 GB sticks of G.Skill RipJaws DDR4@3000). I flashed my BIOS to the latest and greatest, installed the CPU, removed my Win10 VM, added it back in. All was going great. The 1070 passed through... but I could only get sound out of the DisplayPort. I also couldn't get ANY of the USB ports to pass through on the motherboard. I even have an add-on USB 3.0 card (Sabrent CP-4PTU) and I can't pass that through either. (It appears as the add-on card rides on the motherboard's bus.) I'm damn near there. I've been struggling with this for 3 days now. I've watched Space Invader One videos, used VFIO-PIC Config, messed with rcu_nocbs=0-23, tried out multifunction and downstream..... Every time I try to share something, the network doesn't come up or the system hangs. I'm assuming I've passied through stuff that needs to be not passed through. Then I found the thread about the custom kernel from Leoyzen where I can use append pcie_no_flr=1022:149c,1022:1487. I got the USB ports ([AMD] Matisse USB 3.0 Host Controller) passed through and working but every time I tried to add the sound card ([AMD] Starship/Matisse HD Audio Controller), it locks up UnRaid. What upsets me is... after messing with it, I can't get the USB to work again. If I had the USB working, I could get a USB sound card to get me by. Is there anything I can share that will hopefully give someone insight that could help me? Here's what I have in my sysconfig: append pcie_no_flr=1022:149c,1022:1487 vfio-pci.ids=1022:149c,1022:1487 initrd=/bzroot Here's my VM: <?xml version='1.0' encoding='UTF-8'?> <domain type='kvm' id='1'> <name>Windows 10</name> <uuid>4babd643-2762-4e91-2ee1-cb2b5be98406</uuid> <metadata> <vmtemplate xmlns="unraid" name="Windows 10" icon="windows.png" os="windows10"/> </metadata> <memory unit='KiB'>16777216</memory> <currentMemory unit='KiB'>16777216</currentMemory> <memoryBacking> <nosharepages/> </memoryBacking> <vcpu placement='static'>8</vcpu> <cputune> <vcpupin vcpu='0' cpuset='8'/> <vcpupin vcpu='1' cpuset='20'/> <vcpupin vcpu='2' cpuset='9'/> <vcpupin vcpu='3' cpuset='21'/> <vcpupin vcpu='4' cpuset='10'/> <vcpupin vcpu='5' cpuset='22'/> <vcpupin vcpu='6' cpuset='11'/> <vcpupin vcpu='7' cpuset='23'/> </cputune> <resource> <partition>/machine</partition> </resource> <os> <type arch='x86_64' machine='pc-q35-4.2'>hvm</type> </os> <features> <acpi/> <apic/> <hyperv> <relaxed state='on'/> <vapic state='on'/> <spinlocks state='on' retries='8191'/> <vendor_id state='on' value='none'/> </hyperv> </features> <cpu mode='custom' match='exact' check='full'> <model fallback='forbid'>qemu64</model> <topology sockets='1' cores='8' threads='1'/> <feature policy='require' name='x2apic'/> <feature policy='require' name='hypervisor'/> <feature policy='require' name='lahf_lm'/> <feature policy='disable' name='svm'/> </cpu> <clock offset='localtime'> <timer name='hypervclock' present='yes'/> <timer name='hpet' present='no'/> </clock> <on_poweroff>destroy</on_poweroff> <on_reboot>restart</on_reboot> <on_crash>restart</on_crash> <devices> <emulator>/usr/local/sbin/qemu</emulator> <disk type='file' device='disk'> <driver name='qemu' type='raw' cache='writeback'/> <source file='/mnt/user/domains/Windows 10/vdisk1.img' index='2'/> <backingStore/> <target dev='hdc' bus='virtio'/> <boot order='1'/> <alias name='virtio-disk2'/> <address type='pci' domain='0x0000' bus='0x03' slot='0x00' function='0x0'/> </disk> <disk type='file' device='cdrom'> <driver name='qemu' type='raw'/> <source file='/mnt/user/isos/virtio-win-0.1.173-2.iso' index='1'/> <backingStore/> <target dev='hdb' bus='sata'/> <readonly/> <alias name='sata0-0-1'/> <address type='drive' controller='0' bus='0' target='0' unit='1'/> </disk> <controller type='usb' index='0' model='ich9-ehci1'> <alias name='usb'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x7'/> </controller> <controller type='usb' index='0' model='ich9-uhci1'> <alias name='usb'/> <master startport='0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x0' multifunction='on'/> </controller> <controller type='usb' index='0' model='ich9-uhci2'> <alias name='usb'/> <master startport='2'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x1'/> </controller> <controller type='usb' index='0' model='ich9-uhci3'> <alias name='usb'/> <master startport='4'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x2'/> </controller> <controller type='sata' index='0'> <alias name='ide'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x1f' function='0x2'/> </controller> <controller type='pci' index='0' model='pcie-root'> <alias name='pcie.0'/> </controller> <controller type='pci' index='1' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='1' port='0x8'/> <alias name='pci.1'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x0' multifunction='on'/> </controller> <controller type='pci' index='2' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='2' port='0x9'/> <alias name='pci.2'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x1'/> </controller> <controller type='pci' index='3' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='3' port='0xa'/> <alias name='pci.3'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x2'/> </controller> <controller type='pci' index='4' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='4' port='0xb'/> <alias name='pci.4'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x3'/> </controller> <controller type='pci' index='5' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='5' port='0xc'/> <alias name='pci.5'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x4'/> </controller> <controller type='pci' index='6' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='6' port='0xd'/> <alias name='pci.6'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x5'/> </controller> <controller type='pci' index='7' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='7' port='0xe'/> <alias name='pci.7'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x6'/> </controller> <controller type='virtio-serial' index='0'> <alias name='virtio-serial0'/> <address type='pci' domain='0x0000' bus='0x02' slot='0x00' function='0x0'/> </controller> <interface type='bridge'> <mac address='52:54:00:1b:4f:1d'/> <source bridge='br0'/> <target dev='vnet0'/> <model type='virtio'/> <alias name='net0'/> <address type='pci' domain='0x0000' bus='0x01' slot='0x00' function='0x0'/> </interface> <serial type='pty'> <source path='/dev/pts/0'/> <target type='isa-serial' port='0'> <model name='isa-serial'/> </target> <alias name='serial0'/> </serial> <console type='pty' tty='/dev/pts/0'> <source path='/dev/pts/0'/> <target type='serial' port='0'/> <alias name='serial0'/> </console> <channel type='unix'> <source mode='bind' path='/var/lib/libvirt/qemu/channel/target/domain-1-Windows 10/org.qemu.guest_agent.0'/> <target type='virtio' name='org.qemu.guest_agent.0' state='disconnected'/> <alias name='channel0'/> <address type='virtio-serial' controller='0' bus='0' port='1'/> </channel> <input type='mouse' bus='ps2'> <alias name='input0'/> </input> <input type='keyboard' bus='ps2'> <alias name='input1'/> </input> <hostdev mode='subsystem' type='pci' managed='yes' xvga='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x06' slot='0x00' function='0x0'/> </source> <alias name='hostdev0'/> <rom file='/mnt/disk1/isos/vbios/MSI.GTX1070.8192.161024.rom'/> <address type='pci' domain='0x0000' bus='0x04' slot='0x00' function='0x0'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x06' slot='0x00' function='0x1'/> </source> <alias name='hostdev1'/> <address type='pci' domain='0x0000' bus='0x05' slot='0x00' function='0x0'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x08' slot='0x00' function='0x3'/> </source> <alias name='hostdev2'/> <address type='pci' domain='0x0000' bus='0x06' slot='0x00' function='0x0'/> </hostdev> <memballoon model='none'/> </devices> <seclabel type='dynamic' model='dac' relabel='yes'> <label>+0:+100</label> <imagelabel>+0:+100</imagelabel> </seclabel> </domain>