New KVM Instance on samba mounted local directory won't start

S

smcan

New Member
Apr 14, 2011
4
0
1
New to proxmox and testing all the ways of doing things I can find. I am currently trying to run a new KVM instance stored on a NAS appliance and mounted via Samba as a local directory. The creation of the KVM instance is fine but it won't start. I'm not getting any real good error information either.

Here is the syslog output after an attempted start:
Code: 
Apr 14 10:54:18 proxmox pvedaemon[18313]: starting VM 101 on node 0 (localhost)
Apr 14 10:54:19 proxmox qm[18314]: VM 101 start
Apr 14 10:54:19 proxmox kernel: device tap101i0d0 entered promiscuous mode
Apr 14 10:54:19 proxmox kernel: vmbr0: port 2(tap101i0d0) entering forwarding state
Apr 14 10:54:19 proxmox qm[18314]: VM 101 start failed: command '/usr/bin/kvm -monitor unix:/var/run/qemu-server/101.mon,server,nowait -vnc unix:/var/run/qemu-server/101.vnc,password -pidfile /var/run/qemu-server/101.pid -daemonize -usbdevice tablet -name confkeeper -smp sockets=1,cores=1 -nodefaults -boot menu=on -vga cirrus -tdf -k en-us -drive file=/mnt/PROXVM/images/101/vm-101-disk-1.raw,if=ide,index=0,cache=none,boot=on -drive file=/var/lib/vz/template/iso/ubuntu-10.04.2-server-i386.iso,if=ide,index=2,media=cdrom -m 512 -netdev type=tap,id=vlan0d0,ifname=tap101i0d0,script=/var/lib/qemu-server/bridge-vlan -device rtl8139,mac=EA:45:57:5D:B0:02,netdev=vlan0d0 -id 101 -cpuunits 1000' failed with exit code 1
Apr 14 10:54:19 proxmox pvedaemon[18313]: VM 101 start failed -
Apr 14 10:54:19 proxmox kernel: vmbr0: port 2(tap101i0d0) entering disabled state
Apr 14 10:54:19 proxmox kernel: vmbr0: port 2(tap101i0d0) entering disabled state

I'm inclined to think it's has to do with the samba mounted directory just because everything I've created on the local disk works fine. However, the samba mount seems to be working fine as well. I have full read/write ability tested and working from the proxmox server.

Any ideas?

System info if needed:

-CPU(s) 4 x AMD Athlon(tm) II X4 620 Processor
-Version (package/version/build) pve-manager/1.8/5754
-Kernel Version Linux 2.6.32-4-pve #1 SMP Tue Mar 29 09:08:37 CEST 2011
 
try with cache=writethrough for your VM disk (edit /etc/qemu-server/VMID.conf directly).
 
Hi,
i never heard that someone tried an samba-share... suported is nfs, and fc/iscsi-san...

if you copy the raw-disk-file to local (/var/lib/vz/images/101/) and change the disk-location in /etc/qemu-server/101.conf (or gui with remove disk + apply unused disk) boot the vm then without trouble?

Udo
 
tom said:
try with cache=writethrough for your VM disk (edit /etc/qemu-server/VMID.conf directly).
Click to expand...

Thanks for the reply. Sorry, but where in the config should I put the cache=writethrough. I tried just adding it as a new line in the 101.conf but that didn't make a difference. Should it be a continuation of an existing line?

Thanks!
 
udo said:
Hi,
i never heard that someone tried an samba-share... suported is nfs, and fc/iscsi-san...

if you copy the raw-disk-file to local (/var/lib/vz/images/101/) and change the disk-location in /etc/qemu-server/101.conf (or gui with remove disk + apply unused disk) boot the vm then without trouble?

Udo
Click to expand...

From the PROXMOX Storage Model document:

HowTo mount a Windows (SaMBa) share on Proxmox VE via /etc/fstab

In this scenario, the VM storage functions identically to the directory method. The SMB/CIFS share is mounted as a local mountpoint and appears to Proxmox VE as local storage. To mount a remote samba share, just follow this (adapt it according to your setup):
First, create a target dir, e.g.:
mkdir /mnt/samba1 nano /etc/fstab //windows-or-samba-server-name/sharename /mnt/samba1 cifs username=yourusername,password=yoursecretpassword,domain=yourdomainname 0 0 Next you can activate it with:
mount //windows-or-samba-server-name/sharename Then define a 'Directory' based storage on the web interface using the newly created directory '/mnt/samba1', for example to store backups.
 
tom said:
try with cache=writethrough for your VM disk (edit /etc/qemu-server/VMID.conf directly).
Click to expand...

Disregard my last post. I just kept moving that line around and got it working. Outstanding - thanks for the support!

For anyone else finding this, here's where I put it:

Code: 
name: confkeeper
ide2: local:iso/ubuntu-10.04.2-server-i386.iso,media=cdrom
vlan0: rtl8139=EA:45:57:5D:B0:02
bootdisk: ide0
ostype: l26
ide0: PROXVM:101/vm-101-disk-1.raw,[B]cache=writethrough[/B]
memory: 512
sockets: 1
onboot: 0
cores: 1
 
udo said:
...
... Perhaps a pulldown in the gui for cache-modi was nice?!
Udo
Click to expand...

yes, but I am pretty sure that you will expect the answer. in 2.x :-)
 
You must log in or register to reply here.
Top Bottom