August 1, 201610 yr Author Disregard, when ever I work with VM's I always have to boot before and after (mostly after) if I make a change to something. I did nothing else but a reboot and it is installing now.
August 2, 201610 yr Author Disregard, when ever I work with VM's I always have to boot before and after (mostly after) if I make a change to something. I did nothing else but a reboot and it is installing now. I've given up on everything except unraid telling I do not have any space available. I have deleted the partition and re-created it again. Maybe a incompatible drive? There's only so many times you can re-format an SSD and blank it it all out.
August 2, 201610 yr It's not clear from your post if you're trying to pass through the entire ssd or use the ssd for the vdisk?
August 3, 201610 yr Author It's not clear from your post if you're trying to pass through the entire ssd or use the ssd for the vdisk? Just plop in an SSD, partition and format it....then install. I'm still unable to move forward since the drive still indicates it is not formatted. mkfs.xfs /dev/sdb1 is what normally works.
August 3, 201610 yr So then you are trying to pass through the disk if I understand you correctly. Could you post your XML? If you pass through the disk, you should not mount it in UD. Try turning off automount.
August 3, 201610 yr Author Still getting this after a fresh re-format. Racking my brain. Steps I've been using. fdisk /dev/sdc enter 'n' to list partitions select 1 enter "p", shows 128 SSD drive now - /dev/sdc1 enter "w" to write table and then the format itself - mkfs.xfs -f /dev/sdc1 Then I can mount the SSD in unraid using unassigned devices and start the ubuntu install, until I click in "install ubuntu".
August 3, 201610 yr Author So then you are trying to pass through the disk if I understand you correctly. Could you post your XML? If you pass through the disk, you should not mount it in UD. Try turning off automount. Sure: <domain type='kvm' id='1'> <name>unraidcrash</name> <uuid>48f19328-996d-ace9-5836-c12aa7331170</uuid> <description>unraidcrash</description> <metadata> <vmtemplate name="Custom" icon="linux.png" os="linux"/> </metadata> <memory unit='KiB'>4194304</memory> <currentMemory unit='KiB'>4194304</currentMemory> <memoryBacking> <nosharepages/> <locked/> </memoryBacking> <vcpu placement='static'>6</vcpu> <cputune> <vcpupin vcpu='0' cpuset='0'/> <vcpupin vcpu='1' cpuset='1'/> <vcpupin vcpu='2' cpuset='2'/> <vcpupin vcpu='3' cpuset='3'/> <vcpupin vcpu='4' cpuset='4'/> <vcpupin vcpu='5' cpuset='5'/> </cputune> <resource> <partition>/machine</partition> </resource> <os> <type arch='x86_64' machine='pc-q35-2.3'>hvm</type> </os> <features> <acpi/> <apic/> </features> <cpu mode='host-passthrough'> <topology sockets='1' cores='6' threads='1'/> </cpu> <clock offset='utc'> <timer name='rtc' tickpolicy='catchup'/> <timer name='pit' tickpolicy='delay'/> <timer name='hpet' present='no'/> </clock> <on_poweroff>destroy</on_poweroff> <on_reboot>restart</on_reboot> <on_crash>restart</on_crash> <devices> <emulator>/usr/bin/qemu-system-x86_64</emulator> <disk type='file' device='cdrom'> <driver name='qemu' type='raw'/> <source file='mnt/disks/files/isoinstalls/ubuntu-16.04.1-desktop-amd64.iso'/> <backingStore/> <target dev='hda' bus='sata'/> <readonly/> <boot order='2'/> <alias name='sata0-0-0'/> <address type='drive' controller='0' bus='0' target='0' unit='0'/> </disk> <controller type='usb' index='0' model='ich9-ehci1'> <alias name='usb'/> <address type='pci' domain='0x0000' bus='0x02' slot='0x03' function='0x7'/> </controller> <controller type='usb' index='0' model='ich9-uhci1'> <alias name='usb'/> <master startport='0'/> <address type='pci' domain='0x0000' bus='0x02' slot='0x03' function='0x0' multifunction='on'/> </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='dmi-to-pci-bridge'> <alias name='pci.1'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x1e' function='0x0'/> </controller> <controller type='pci' index='2' model='pci-bridge'> <alias name='pci.2'/> <address type='pci' domain='0x0000' bus='0x01' slot='0x01' function='0x0'/> </controller> <controller type='virtio-serial' index='0'> <alias name='virtio-serial0'/> <address type='pci' domain='0x0000' bus='0x02' slot='0x04' function='0x0'/> </controller> <filesystem type='mount' accessmode='passthrough'> <source dir='/mnt/user/'/> <target dir='unraid'/> <alias name='fs0'/> <address type='pci' domain='0x0000' bus='0x02' slot='0x01' function='0x0'/> </filesystem> <interface type='bridge'> <mac address='52:54:00:9a:28:7a'/> <source bridge='virbr0'/> <target dev='vnet0'/> <model type='virtio'/> <alias name='net0'/> <address type='pci' domain='0x0000' bus='0x02' slot='0x02' function='0x0'/> </interface> <serial type='pty'> <source path='/dev/pts/2'/> <target port='0'/> <alias name='serial0'/> </serial> <console type='pty' tty='/dev/pts/2'> <source path='/dev/pts/2'/> <target type='serial' port='0'/> <alias name='serial0'/> </console> <channel type='unix'> <source mode='bind' path='/var/lib/libvirt/qemu/channel/target/unraidcrash.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='tablet' bus='usb'> <alias name='input0'/> </input> <input type='mouse' bus='ps2'/> <input type='keyboard' bus='ps2'/> <graphics type='vnc' port='5900' autoport='yes' websocket='5700' listen='0.0.0.0' keymap='en-us'> <listen type='address' address='0.0.0.0'/> </graphics> <video> <model type='vmvga' vram='16384' heads='1'/> <alias name='video0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x0'/> </video> <memballoon model='virtio'> <alias name='balloon0'/> <address type='pci' domain='0x0000' bus='0x02' slot='0x05' function='0x0'/> </memballoon> </devices> </domain>
August 3, 201610 yr If you want to use the whole ssd for the VM passing it through, you just have to find the disk ID in the below path and add the whole path including the disk ID in the vdisk location in the VM template. After starting the VM you should be able to use the entire disk. Before passing the disk through, be sure to disable mounting in UD, as that will most likely cause issues.
August 3, 201610 yr Author You haven't added any disks to you VM. No wonder it says not enough space. How in the world they kept disappearing is making me a little nuts and a little embarrassed about it. I mean that's the whole idea behind a VM. I was even moving the vdisks around to another location , one I wanted to finalize the location of where all my vdisks will be. Now that's settled, Ubuntu installs! Wooo hoooo. I get to log in once, then after the first boot I get a message about low graphics mode and can't go any further. I'm strictly connecting to this VM remotely, so I don't need a graphics card. Is there a safe mode type login for Ubuntu? I must have installed 15 Ubuntu VM's playing around on my server, I have no idea on why I'm having such odd issues. I Google the "low graphics mode" and see where I'm at. I think I might be losing my MOJO!
August 3, 201610 yr Have you tried changing the graphics to qxl in the template? I think you have to go into advanced mode to find it.
Archived
This topic is now archived and is closed to further replies.